use iconOrder when editing/stating desired icon order

I needed to set iconOrder when I wanted to edit the order of social icons. I think this example is clearer.

Going to ping @kentnek since he implemented this feature. What do you think @kentnek ? Looks fine to me.

Oh I don't mind the change but this might cause problems to existing users hmm

this is just a change in the docs rather than a code tinker, so shouldn't affect users. I found myself fiddling with iconTitles to reorder icons based on the current readme, which didn't work. This feels clearer to me, unless I misunderstand the use of iconTitles and iconOrder.

@kentnek I don't believe it would affect existing users unless they update the git submodule. If they never do then they won't receive any of these changes. On that note, I've been thinking a lot about how to manage "releases" via GitHub. It's been a while since we've cut a new release, and there have been a number of changes since. I think it's time to consider a proper release workflow and document changes in the release itself, as well as add documentation in the README about the proper steps to receive updates if you're already using the theme. Of course it's on us to make sure any breaking changes get documented as such.
@ewenme I think this might be why your adjustments to iconTitles aren't be taken by the theme:
<!-- layouts/partials/social-icons.html -->

{{ $icons := .Site.Params.iconOrder | default (slice "Twitter" "GitHub" "Email" "Facebook" "GitLab" "Instagram" "LinkedIn" "YouTube") }}

It looks like the partial is trying to locate .Site.Params.iconOrder, which doesn't exist. Instead it should be looking for .Site.Params.iconTitles. Is that the case @kentnek ?
If so, then a truly backwards compatible change would be to fix that instead of renaming the param from iconTitles to iconOrder. We could definitely accept that change and then have a larger discussion about how to make defining social icons more ergonomic. Maybe the name of the param itself could be used as the icon title, rather than define it inside of an array. From there a user could just rearrange the order that the social urls are defined in order to adjust the order in which the icons render. Just a thought 😄
What do you all think?

I think this might be why your adjustments to iconTitles aren't be taken by the theme:

That's the reason why I said this change might be problematic for people who want to keep their theme submodules up-to-date. I'd avoid this kind of changes to the config file to keep backward compatibility, unless something major needs to be fixed.

Right, I gotcha. So if we updated:
$icons := .Site.Params.iconOrder

to:
$icons := .Site.Params.iconTitles

This would respect the ordering of the iconTitles array without adjusting the config itself.  I didn't catch it earlier because my personal site was using iconOrder in the config.
So this is actually a bug, and @ewenme makes sense to me now.

lol yup! It definitely makes sense. The way I see it, we can handle this in 1 of 2 ways:

Rename to .Site.params.iconTitles in the partial
Rename to iconOrder in the config

I prefer the semantics of the latter, as @ewenme has described. It just makes more sense as to what this is doing. But I also think the former is valuable because it doesn't directly adjust the config. I'm open to either, and if I had to vote I'd say go with the latter. But I wanted to present both options.
And also a third option would be to remove the array altogether and deduce the icon order from how the urls are defined in the .Site.params (if that's possible).

Your 3rd option is not possible because we can't guarantee the key order in a JSON object. So yeah I'm okay with updating the config+docs to use iconOrder instead.

Sounds good to me!

@all-contributors please add @ewenme for code

Thanks for this @ewenme !!

thanks! love the theme, have just started using it personally so I'll try and contribute some more as I dig into it...


Add additional error handling to Purchase function

closes #189

Coverage decreased (-0.03%) to 26.006% when pulling 2ca4f0520cb2212a5affd6186abf12ac9d6ca20e on errors into 0f6e1312661e082fbf389cc9dd6712784149ff9b on master.


Tests for loading groups pipeline.

Tests for #62

Coverage increased (+2.2%) to 68.326% when pulling 9a5f1fd34b0c50cc9c03733e31bc7162a16a058a on grouptests into 009f57dbd55a3c9aacb8373d441774f1f0244453 on master.

Coverage increased (+2.2%) to 68.326% when pulling 62d09cbaf9abd2670bfb301d3fe7991dd9ee939f on grouptests into 009f57dbd55a3c9aacb8373d441774f1f0244453 on master.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


Export cesium context

A little modification in context definition to export React.createContext result.
This way, we can import the whole context and use the React contextType inside a component to easily access cesium objects without using Consumer.
See: https://reactjs.org/docs/context.html#classcontexttype

Great PR! Thank you.


Should there be a version of X-IC-Script that executes after the element is replaced?

I've been trying to find a way to re-bind an element after it has been updated by Intercooler. The element is tagged using another package, but I need to re-bind it once it's been updated to restore the functionality.
I can include JS in the partial processed by Intercooler, but I run into problems when executing it during the initial page load. I found the X-IC-Script response header and thought this would be a good way to execute the re-bind code after the page has been updated.
However, it turns out that X-IC-Script is executed BEFORE the page is updated. How useful is this? Would it be possible to provide an alternative version that runs after the page update?

I've been trying to find a way to re-bind an element after it has been updated by Intercooler. The element is tagged using another package, but I need to re-bind it once it's been updated to restore the functionality.
I can include JS in the partial processed by Intercooler, but I run into problems when executing it during the initial page load. I found the X-IC-Script response header and thought this would be a good way to execute the re-bind code after the page has been updated.
However, it turns out that X-IC-Script is executed BEFORE the page is updated. How useful is this? Would it be possible to provide an alternative version that runs after the page update?

Since swapping and re-binding takes some milliseconds to apply, you probably will need to use setTimeout after headers are processed or when Intercooler is ready. You can do like this:
Intercooler.ready(function() {
  setTimeout(function() {
    yourReloadFunc();
  }, 25);
});

... or give your X-IC-Script executing function some timeout. X-IC-Script executes when response headers are parsed, but there is no guarantee that old content was swapped by new and Intercooler is ready on a new content. So that's why you need that tiny delay. At least that's how I manage to handle such cases as you described.
Quoting developer's word from gitter:

We have a 20 millisecond delay after the completion of the request before we do the swap. IIRC this was to allow CSS transitions to function correctly.

Ah, excellent! The Intercooler.ready function solves the problem nicely. Thanks for the feedback.


Unbound 1.17.1 module python failed

Describe the bug
Unbound 1.17.1 Successfully build with python 3.6 but failed after start.
unbound: [7930:0] error: pythonmod: can't parse Python script script.py
unbound: [7930:0] error: pythonmod: python error: NoneType: None
unbound: [7930:0] error: module init for module python failed
unbound: [7930:0] fatal error: failed to setup modules

Expected behavior
Working fine until Unbound 1.17.0
System:

Unbound version:
OS: Ubuntu 18.04
unbound -V output:

Version 1.17.1

Configure line: --prefix=/usr/local --disable-maintainer-mode --disable-dependency-tracking --disable-rpath --sysconfdir=/etc --with-pidfile=/run/unbound.pid
--with-libevent --with-pythonmodule --with-pyunbound --enable-subnet --enable-dnstap --enable-systemd --with-dnstap-socket-path=/run/dnstap.sock --disable-flto --enable-tfo-client --enable-tfo-server
Linked libs: libevent 2.1.8-stable (it uses epoll), OpenSSL 1.1.1  11 Sep 2018
Linked modules: dns64 python subnetcache respip validator iterator
TCP Fastopen feature available

There has been a bug fix, slated for upcoming releases, that is in the code repository. https://github.com/NLnetLabs/unbound/commit/4517dcd439562cb1df07e77738153c0c906bb069 could solve the issue, perhaps.
This fix deals with install paths. Different python component can report different install paths. And the fix picks the ones that seem most relevant given the python version.
Does that fix the issue for you, the version from the code repository?

Thanks @wcawijngaards Unbound 1.17.1 with patch from https://github.com/NLnetLabs/unbound/commit/4517dcd439562cb1df07e77738153c0c906bb069 working fine.

I'm experiencing this on 1.17.1_2
2023-02-20T14:25:24-07:00 | Critical | unbound | [89033:0] fatal error: failed to setup modules |
-- | -- | -- | -- | --
2023-02-20T14:25:24-07:00 | Error | unbound | [89033:0] error: module init for module python failed |
2023-02-20T14:25:24-07:00 | Error | unbound | [89033:0] error: pythonmod: python error: NoneType: None |
2023-02-20T14:25:24-07:00 | Error | unbound | [89033:0] error: pythonmod: can't parse Python script dnsbl_module.py


Move embed files to a separate package

The basic design of ipywidgets is that the core widgets are in jupyter-js-widgets, while the adapters that actually put them on the page are in other packages. I think we should move the adapters that support embedded widgets (the embed-* files) to a separate package. This will clean up the dependencies for jupyter-js-widgets a lot.
Thoughts, @SylvainCorlay?

We decided to leave the embed files in the package, but in a separate directory from jupyter-js-widgets.


Migrate soda-bigquery to use newer google-cloud-bigquery

Google Cloud Bigquery client library has been updated to version 3 for over a year now, yet soda-bigquery is still pinning an older version: google-cloud-bigquery>=2.25.0, <3.0.
Maybe, it's time to update.

SODA-1752

Thanks.
Just saw that version 3.0.42 was released yesterday.


Change in Cache implementation

Pull Request Test Coverage Report for Build 1118

5 of 7 (71.43%)  changed or added relevant lines in 3 files are covered.
15 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.04%) to 63.203%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

control/archaius/transfer.go
2
4
50.0%

Files with Coverage Reduction
New Missed Lines
%

core/handler/transport_handler.go
3
21.95%

core/registry/discovery.go
3
69.23%

control/archaius/transfer.go
3
93.51%

server/restful/context.go
3
83.02%

core/config/route_config.go
3
0.0%

Totals

Change from base Build 1106:
-0.04%

Covered Lines:
5000

Relevant Lines:
7911

💛  - Coveralls


New Command for feature flags

          To track as a separate issue, I think we should add a different `dab` command that helps to enable or disable a feature, should not be only possible through the `init` command - which is the case today.

Originally posted by @Aniruddh25 in https://github.com/Azure/data-api-builder/pull/1983#discussion_r1468255119
Create a new command to create/update feature flags in the config file.

@severussundar can you elaborate on how this is different from feature introduced in #1983?

let's keep in mind per our discussion of feature flags, that there would be a global feature flag section that holds true flags (--enable-feature1) and a separate notion of new configuration properties exclusive to a feature (e.g. cache, nested-mutations).
Is this particular work item applicable to nested mutations/inserts? #1983 implements nested mutations as an exclusive property within the global GraphQL config property -> --graphql.nested-create.enabled.

Let's keep in mind our discussion of feature flags: there will exist both:

global feature flag section that holds true flags (--enable-feature1)

This work-item applies to this bullet.

a separate notion of new configuration properties exclusive to a feature (e.g. cache, nested-mutations).     - This workitem is unrelated to nestedmutations/inserts becuase Feature Flag for Nested Mutations: CLI changes #1983 implements nested mutations as an exclusive property within the global GraphQL config property -> --graphql.nested-create.enabled.

Right now, the feature flag values (setting enabled:true/false, etc.) is possible only through init command. Also, this section of the config file cannot be updated using a CLI command as dab update is for updating fields under entities section only. This would mean that to update the feature flag values, users have to hand-edit the config file.
The goal is to come up with a new command that facilitates updating the feature flag related options. Having a global section in the config file will make it intuitive and also easy to implement.
Note: Although introducing a new Verb/Option will make the experience better, IMHO, shouldn't be a blocker for GA as users still have a way to enable/disable the feature (as well as configure feature specific properties).

Not nested mutation specific, but need to revisit in 1.1 to determine whether this is required immediately.

we need task to add new config field here for behavioral feature flags before this is implemented


Update readme.md

Adds Reactivesearch https://github.com/appbaseio/reactivesearch, it's a set of styled React UI components for use with Elasticsearch.

Don't create a pull request to add a library, instead use devarchy.com/react.
Only create a pull request to change the categorization.
Open an issue if you are not sure how to change the categorization to fit a library you want to add.

Is there a reason you didn't use devarchy?

@brillout Just added to devarchy, closing this pull request.


Black dashes for HTTPs calls

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

Greetings,
We seem to have black dashes for our HTTPs calls and we aren't quite sure what they're supposed to mean. We found nothing resembling in the doc nor in any screenshoot we've had the chance to look at. Here's an exemple :

In browser, the call seems to persist past the black dash but in a node environment it stops at it.
Any answer as to what those black dashes mean / stand for  would be greatly appreciated 🙏

Have you tried to ask the tool authors about this? OTel JS doesn't come with a UI like that one above.

No, we haven't yet. The tool we're using is Jaeger UI.

Would be nice if they can tell in which condition black dashes like this are shown. Once we have this information it's by far easier to look into Oel-JS to check what causes this trigger to occur and if this is problematic/wrong or perfectly fine.
Another option is that you export the spans effected spans into the console and try by yourself to find something suspicious there.

Thank you for your quick answers. We'll ask the question in Jaeger UI and come back to you. 👍


Debugging Event

I didn't initially intend to debug Login, but the system developed a 500 CORS error while I was working on it which I needed to address.

Start backend using Debugging

(Backend window opened with Debug; missing module error discovered. I resolved this by having Python run in the file path of the folder, though it was not entirely necessary)

Set break point at the beginning of endpoint code

(Login endpoint is in /api/authenticate as designated here)

Start in frontend with split screen loading source for an API fetch using GET.

(Left: Login after sending request | Right: Backend with 500 error)

Set break point on fetch, inside .then, inside .fetch

(Breakpoints on fetch command as well as all error catches inside)

Run frontend, screen capture break at fetch while examining Body

(Breakpoint paused at reporting for additional error types)

Press play on frontend, observe stop inside of backend

Here the bug I introduced is caught (report for bad request in api/authenticate), so I fix it

Press step over on backend until you have obtained data from database, screen capture Python Object

Press play button to end backend debugging session.

Return to frontend debug session

Step in until you see data, screen capture capturing break point and Data.

1.9 - The login page was done again but other then that the debugging throughout the backend and frontend with the fetch requests are done properly.

1.9/2 - The debugging is done on the login, not the Cpt. Overall, the debugging is highlighted well.

Start screen is peculiar as it errors when running user.py.   Need to set breakpoint there and then run main.py.  Last few steps are omitted.  Not sure I saw data being examined in backend.


v1.5 backports 2019-04-23

#7818 -- k8s: fix panic of closed channel (@aanm)
#7820 -- contrib: Install modprobe to cilium-runtime image (@brb)
#7814 -- Fix compile complaint in k8s package (@joestringer)
#7828 -- iptables: Correctly remove Cilium chains when IPv6 is disabled (@tgraf)

Once this PR is merged, you can update the PR labels via:
$ for pr in 7818 7820 7814 7828; do contrib/backporting/set-labels.py $pr done 1.5; done

This change is

test-me-please

test-missed-k8s

test-docs-please

test-missed-k8s

Updated to include the latest PRs for backport.

test-me-please

test-missed-k8s

test-docs-please

Both builds failed due to hang in preflight checks, #7796:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/1938/execution/node/60/log/
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/11829/execution/node/83/log/

Failed due to:
[2019-04-24T00:40:51.906Z] Cancelling nested steps due to timeout
[2019-04-24T00:40:51.983Z] Sending interrupt signal to process
[2019-04-24T00:41:06.397Z] cleaning up VMs started for k8s tests
[2019-04-24T00:41:06.397Z]
[2019-04-24T00:41:06.397Z] ---------------------------------------------------------
[2019-04-24T00:41:06.397Z] Received interrupt.  Running AfterSuite...
[2019-04-24T00:41:06.397Z] ^C again to terminate immediately

test-me-please

test-missed-k8s

test-missed-k8s

Failed due to:
12:20:04      Check connectivity with Geneve encapsulation [It]
12:20:04      /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-K8s/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:410
12:20:04
12:20:04      Pods are not ready after timeout
[2019-04-24T10:20:04.549Z]     Expected
[2019-04-24T10:20:04.549Z]         <*errors.errorString | 0xc4219e9d50>: {
[2019-04-24T10:20:04.549Z]             s: "Timeout reached: timed out waiting for pods with filter  to be ready",
[2019-04-24T10:20:04.549Z]         }
[2019-04-24T10:20:04.549Z]     to be nil

#7373


feat(vue-model-api): add a library to use models from Vue.js

Users can use the exported functions useModelsFromJson to read models from exported JSON files.
To connect to a server, users must use useModelClient and useRootNode.
The returned objects also work with Vue.js reactivity system and the typed classes generated by
model-api-gen.

Rewrite test to follow Arrange-Act-Assert
Enable caching for all tasks

do not run prettier in check, it is already run by pre commit checks

Mark as @alpha instead of @experimental

The dependency tracking of read/write access to nodes is something we need also when not using vue.js. I implemented something similar for the text-editor that also integrates with modelix.incremental:
https://github.com/modelix/modelix.text-editor/blob/main/projectional-editor/src/commonMain/kotlin/org/modelix/editor/IncrementalBranch.kt
https://github.com/modelix/modelix.core/pull/273/files
We should reuse that for the vue.js integration.

:tada: This PR is included in version 3.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


vue props variable name does not support camelCase, undefined returned

Vue.js version
2.0.1
Reproduction Link
Steps to reproduce
What is Expected?
should be return the right value
What is actually happening?
vue props variable name does not support camelCase, "undefined" returned.
For example, if I use camelCase as the props variable name, "undefined" returned, however, if I change it to camelcase, everything works as expetected

Thanks for filing the issue. Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or JSBin containing a set of reproducible steps that can lead to the behavior you described.

I was using laravel 5.3 with Vue 2.0.1
However, it looks like the issue will happen only if I use laravel to pass data from laravel controller to blade template to vue components

I was using laravel 5.3 with Vue 2.0.1
However, it looks like the issue will happen only if I use laravel to pass data from laravel controller to blade template to vue components


Mixed case validation notice schema is incomplete

Describe the problem
Mixed case validation was introduced in #1340.
In the validation report, we don't see the record values that trigger this notice, only the number of the row (see image below).
Seeing the actual value here would encourage the user to fix the issue because they would see what the rider would see.
Additionally, the filename name doesn't follow our naming conventions, it should be fileName.

Proposed solution
I recommend adding a FieldValue in the schema that displays the value of the faulty record, and changing filename to fileName to follow our naming conventions.
Alternatives you've considered
Status quo
Additional context
No response

@briandonahue, would you be able to fix this issue? :)

@isabelle-dr I've started #1393, but there is an issue in master (#1394) blocking me at the moment.
Also, I believe @bdferris-v2 confirmed this in another conversation, but all notices and documentation are currently using filename, all lower-case, at the moment, so I'm leaving that field name as-is for now and we discuss whether this convention should be changed globally.


Add Metric Prometheus Reporter IT

Add Metric Prometheus Reporter

Codecov Report

Merging #11443 (b8f1dbd) into master (1dd5a20) will increase coverage by 0.09%.
Report is 16 commits behind head on master.
The diff coverage is 49.48%.

@@             Coverage Diff              @@
##             master   #11443      +/-   ##
============================================
+ Coverage     49.06%   49.15%   +0.09%
- Complexity    24464    24560      +96
============================================
  Files          2774     2768       -6
  Lines        171574   172197     +623
  Branches      20507    20603      +96
============================================
+ Hits          84183    84645     +462
- Misses        87391    87552     +161

Files
Coverage Δ

...protocol/thrift/sync/IoTDBThriftSyncConnector.java
10.50% <100.00%> (+6.75%)
:arrow_up:

...gion/compaction/execute/utils/CompactionUtils.java
91.78% <ø> (+2.21%)
:arrow_up:

...a/org/apache/iotdb/commons/conf/IoTDBConstant.java
87.09% <ø> (ø)

...he/iotdb/consensus/ratis/metrics/CounterProxy.java
58.33% <0.00%> (ø)

...ctor/protocol/legacy/IoTDBLegacyPipeConnector.java
22.60% <86.66%> (+12.92%)
:arrow_up:

...ol/thrift/impl/DataNodeInternalRPCServiceImpl.java
3.44% <0.00%> (ø)

...tdb/db/pipe/connector/protocol/IoTDBConnector.java
64.44% <11.11%> (+28.08%)
:arrow_up:

...onnector/protocol/airgap/IoTDBAirGapConnector.java
0.00% <0.00%> (ø)

...he/iotdb/commons/service/metric/MetricService.java
21.11% <38.46%> (+7.04%)
:arrow_up:

... and 219 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

There are some problems in CI which is not related the edition of this pr


[BUG] TypeError: llama_index.core.ingestion.pipeline.run_transformations() got multiple values for keyword argument 'show_progress'

Pre-check

[X] I have searched the existing issues and none cover this bug.

Description
Hi,
I get this error, and couldn't resolve it,
Can you help me?
file_name: image__vector_store.json, extension: .json, reader_cls: <class 'llama_index.core.readers.json.JSONReader'>
Traceback (most recent call last):
File "/Users/user/AI/private-gpt/scripts/ingest_folder.py", line 122, in
worker.ingest_folder(root_path, args.ignored)
File "/Users/user/AI/private-gpt/scripts/ingest_folder.py", line 58, in ingest_folder
self._ingest_all(self._files_under_root_folder)
File "/Users/user/AI/private-gpt/scripts/ingest_folder.py", line 62, in _ingest_all
self.ingest_service.bulk_ingest([(str(p.name), p) for p in files_to_ingest])
File "/Users/user/AI/private-gpt/private_gpt/server/ingest/ingest_service.py", line 87, in bulk_ingest
documents = self.ingest_component.bulk_ingest(files)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/user/AI/private-gpt/private_gpt/components/ingest/ingest_component.py", line 135, in bulk_ingest
saved_documents.extend(self._save_docs(documents))
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/user/AI/private-gpt/private_gpt/components/ingest/ingest_component.py", line 143, in _save_docs
self._index.insert(document, show_progress=True)
File "/Users/user/AI/private-gpt/.venv/lib/python3.11/site-packages/llama_index/core/indices/base.py", line 209, in insert
nodes = run_transformations(
^^^^^^^^^^^^^^^^^^^^
TypeError: llama_index.core.ingestion.pipeline.run_transformations() got multiple values for keyword argument 'show_progress'
make: *** [ingest] Error 1
Steps to Reproduce
PGPT_PROFILES=ollama make ingest ../ING -- --watch --log-file ../LOGS/privategpt_ingest.log
Ctrl+c after a while
Then try again
Expected Behavior
ingest documents
Actual Behavior
error
Environment
Mac ARM cpu and gpu with python 3.11
Additional Information
No response
Version
No response
Setup Checklist

[X] Confirm that you have followed the installation instructions in the project’s documentation.
[X] Check that you are using the latest version of the project.
[X] Verify disk space availability for model storage and data processing.
[X] Ensure that you have the necessary permissions to run the project.

NVIDIA GPU Setup Checklist

[ ] Check that the all CUDA dependencies are installed and are compatible with your GPU (refer to CUDA's documentation)
[ ] Ensure an NVIDIA GPU is installed and recognized by the system (run nvidia-smi to verify).
[X] Ensure proper permissions are set for accessing GPU resources.
[ ] Docker users - Verify that the NVIDIA Container Toolkit is configured correctly (e.g. run sudo docker run --rm --gpus all nvidia/cuda:11.0.3-base-ubuntu20.04 nvidia-smi)

Llama index has been bumped... I will update Llama Index to fix all dependencies issues.

same error here. Please fix


Is there a Swift version?

Hi everyone.
I am new to iOS programming and I am solely using Swift2. So, I am not familiar with Objective C at all. I've been successfully translated objective c code to swift for some other easier APIs. But I am having some trouble on this. Could someone who have implemented this using Swift2 provide a guide for this? I will really appreciate!! :D
Thank you!

There is currently a Swift version being planned, but this SDK will remain our official SDK for some time. Others have integrated with this SDK in Swift, you can see #63, #64 and a variety of other issues on this repo to learn how others have integrated.


add array To Json

Q
A

Branch?
1.x

Bug fix?
no

New feature?
yes

Deprecations?
no

Tickets
Fix #73

License
MIT

Thank you @Moemen-Gaballah for your work. I have some notes:

Please update the Q/A table in the PR description, and mention the related issue #73  in the ticket field.
Fix the CI errors.
Resolve the code review comments.

You can run the static code analysis tool on your local machine:
composer psalm

You can fix the coding style by:
composer format

Thank you 🙌  @Moemen-Gaballah


EBL test data: Provide cargo item to an SI

Signed-off-by: Niels Thykier<EMAIL_ADDRESS>

Please make your own shipping instructions, shipment_equipment and so on instead of re-using the existing ones. This messes up the shipping-instruction-summaries.


Implements IntroSort

In case you're unaware IntroSort (aka Introspective Sort) is a hybrid sorting algorithm that is always at least as fast as QuickSort. It is the algorithm used by Array.Sort and several implementations of the C++ Standard Library.
The algorithm works like this:

If the partition size is < 16 use insertion sort
If the recursion depth is > 2 * log2(n) use heapsort
Otherwise use quicksort (in this case a randomized quicksort)

I have not touched Sorting.SortAll because I think the most elegant way to write that function is to sort on the secondary comparer, followed by the primary comparer (similar to RadixSort). However, this requires a stable sorting algorithm, which IntroSort is not (by virtue of using QuickSort and HeapSort, which are both unstable). Choosing a stable sort like MergeSort would mildly degrade performance, but it would also allow a user to pass in a long list of comparers without requiring a long list of overloads.

I don't know why it didn't work, but it looks like it could be the pipeline:

I don't know why it didn't work, but it looks like it could be the pipeline:

This overload (and some like it) seem have an unclear behaviour. The original implementation passed tests where count was actually a right bound, i.e. index + count. I think I'm misunderstanding what this overload is intended to do, as some linear algebra tests fail when introsort is used (with either count or index + count).
I reverted it to use the QuickSort implementation so as to pass tests until I see the intention with more clarity.

This overload (and some like it) seem have an unclear behaviour. The original implementation passed tests where count was actually a right bound, i.e. index + count. I think I'm misunderstanding what this overload is intended to do, as some linear algebra tests fail when introsort is used (with either count or index + count).
I reverted it to use the QuickSort implementation so as to pass tests until I see the intention with more clarity.

Shouldn't a benchmark prove that this faster than the current implementation?

Shouldn't a benchmark prove that this faster than the current implementation?

Probably. But since it's been a year and a half without activity, and I've completely forgotten about this PR, I'm not very interested in putting more work into a PR that might well be in vain.
There are problems with this PR that I'm not likely to end up fixing, so I think the best thing to do is probably close this, if someone later wants to make a similar change they can start from here if they want. If not, well this isn't exactly huge or too difficult, so even starting from scratch isn't a big loss.


Crash on 1.9.0: Precondition Failure in HTTP2IdleHandler

I've experienced this crash multiple times on my server:
Received signal 4. Backtrace:
0x55b7c15c82c2, Backtrace.(printBacktrace in _B82A8C0ED7C904841114FDF244F9E58E)(signal: Swift.Int32) -> () at /swift-backtrace/Sources/Backtrace/Backtrace.swift:66
0x7faebbae37df
0x55b7c143256f, Swift runtime failure: precondition failure at /async-http-client/Sources/AsyncHTTPClient/ConnectionPool/HTTP2/HTTP2IdleHandler.swift:0
0x55b7c143256f, AsyncHTTPClient.HTTP2IdleHandler.StateMachine.goAwayReceived() -> AsyncHTTPClient.HTTP2IdleHandler<A>.StateMachine.Action at /async-http-client/Sources/AsyncHTTPClient/ConnectionPool/HTTP2/HTTP2IdleHandler.swift:197
0x55b7c143256f, AsyncHTTPClient.HTTP2IdleHandler.channelRead(context: NIOCore.ChannelHandlerContext, data: NIOCore.NIOAny) -> () at /async-http-client/Sources/AsyncHTTPClient/ConnectionPool/HTTP2/HTTP2IdleHandler.swift:66
0x55b7c1aa2772, NIOCore.ChannelHandlerContext.(invokeChannelRead in _F5AC316541457BD146E3694279514AA3)(NIOCore.NIOAny) -> () at /swift-nio/Sources/NIOCore/ChannelPipeline.swift:1688
0x55b7c1aa026f, NIOCore.ChannelHandlerContext.fireChannelRead(NIOCore.NIOAny) -> () at /swift-nio/Sources/NIOCore/ChannelPipeline.swift:1501
0x55b7c1b8bbb0, NIOHTTP2.NIOHTTP2Handler.(processFrame in _57CB3A28E3B2E42C5D0799905DE90E42)(_: NIOHTTP2.HTTP2Frame, flowControlledLength: Swift.Int, context: NIOCore.ChannelHandlerContext) -> NIOHTTP2.NIOHTTP2Handler.FrameProcessResult at /swift-nio-http2/Sources/NIOHTTP2/HTTP2ChannelHandler.swift:304
0x55b7c1b88ece, NIOHTTP2.NIOHTTP2Handler.(frameDecodeLoop in _57CB3A28E3B2E42C5D0799905DE90E42)(context: NIOCore.ChannelHandlerContext) -> () at /swift-nio-http2/Sources/NIOHTTP2/HTTP2ChannelHandler.swift:199
0x55b7c1b88ece, NIOHTTP2.NIOHTTP2Handler.channelRead(context: NIOCore.ChannelHandlerContext, data: NIOCore.NIOAny) -> () at /swift-nio-http2/Sources/NIOHTTP2/HTTP2ChannelHandler.swift:163
0x55b7c1aa2772, NIOCore.ChannelHandlerContext.(invokeChannelRead in _F5AC316541457BD146E3694279514AA3)(NIOCore.NIOAny) -> () at /swift-nio/Sources/NIOCore/ChannelPipeline.swift:1688
0x55b7c1aa026f, NIOCore.ChannelHandlerContext.fireChannelRead(NIOCore.NIOAny) -> () at /swift-nio/Sources/NIOCore/ChannelPipeline.swift:1501
0x55b7c1c474e4, NIOSSL.NIOSSLHandler.(doFlushReadData in _4C55B9A85907C0CB3F4E7FBD2C1C5493)(context: NIOCore.ChannelHandlerContext, receiveBuffer: NIOCore.ByteBuffer, readOnEmptyBuffer: Swift.Bool) -> () at /swift-nio-ssl/Sources/NIOSSL/NIOSSLHandler.swift:436
0x55b7c1c45f1a, NIOSSL.NIOSSLHandler.channelReadComplete(context: NIOCore.ChannelHandlerContext) -> () at /swift-nio-ssl/Sources/NIOSSL/NIOSSLHandler.swift:165
0x55b7c1aa27ca, NIOCore.ChannelHandlerContext.(invokeChannelReadComplete in _F5AC316541457BD146E3694279514AA3)() -> () at /swift-nio/Sources/NIOCore/ChannelPipeline.swift:1698
0x55b7c1aa3462
0x55b7c1c1869a
0x55b7c1c1f7c7, generic specialization <NIOPosix.Socket> of NIOPosix.BaseSocketChannel.readEOF0() -> () at .build/checkouts/swift-nio/Sources/NIOPosix/BaseSocketChannel.swift:988
0x55b7c1c1f7c7, generic specialization <NIOPosix.Socket> of NIOPosix.BaseSocketChannel.readEOF() -> () at .build/checkouts/swift-nio/Sources/NIOPosix/BaseSocketChannel.swift:974
0x55b7c1c1f7c7, generic specialization <NIOPosix.Socket> of protocol witness for NIOPosix.SelectableChannel.readEOF() -> () in conformance NIOPosix.BaseSocketChannel<A> : NIOPosix.SelectableChannel in NIOPosix at /root/<compiler-generated>:965
0x55b7c1c1f7c7, function signature specialization <Arg[2] = Dead> of generic specialization <NIOPosix.SocketChannel> of NIOPosix.SelectableEventLoop.handleEvent<A where A: NIOPosix.SelectableChannel>(_: NIOPosix.SelectorEventSet, channel: A) -> () at /swift-nio/Sources/NIOPosix/SelectableEventLoop.swift:392
0x55b7c1c1f242, reabstraction thunk helper from @callee_guaranteed (@guaranteed NIOPosix.SelectorEvent<NIOPosix.NIORegistration>) -> (@error @owned Swift.Error) to @escaping @callee_guaranteed (@in_guaranteed NIOPosix.SelectorEvent<NIOPosix.NIORegistration>) -> (@error @owned Swift.Error) at /root/<compiler-generated>:0
0x55b7c1c1f242, partial apply forwarder for reabstraction thunk helper from @callee_guaranteed (@guaranteed NIOPosix.SelectorEvent<NIOPosix.NIORegistration>) -> (@error @owned Swift.Error) to @escaping @callee_guaranteed (@in_guaranteed NIOPosix.SelectorEvent<NIOPosix.NIORegistration>) -> (@error @owned Swift.Error) at /root/<compiler-generated>:0
0x55b7c1c1b37c, generic specialization <NIOPosix.NIORegistration> of NIOPosix.Selector.whenReady0(strategy: NIOPosix.SelectorStrategy, onLoopBegin: () -> (), _: (NIOPosix.SelectorEvent<A>) throws -> ()) throws -> () at .build/checkouts/swift-nio/Sources/NIOPosix/SelectorEpoll.swift:252
0x55b7c1c18abf, generic specialization <NIOPosix.NIORegistration> of NIOPosix.Selector.whenReady(strategy: NIOPosix.SelectorStrategy, onLoopBegin: () -> (), _: (NIOPosix.SelectorEvent<A>) throws -> ()) throws -> () at .build/checkouts/swift-nio/Sources/NIOPosix/SelectorGeneric.swift:286
0x55b7c1c18abf, closure #2 () throws -> () in NIOPosix.SelectableEventLoop.run() throws -> () at /swift-nio/Sources/NIOPosix/SelectableEventLoop.swift:461
0x55b7c1c18abf, reabstraction thunk helper from @callee_guaranteed () -> (@error @owned Swift.Error) to @escaping @callee_guaranteed () -> (@out (), @error @owned Swift.Error) at /root/<compiler-generated>:0
0x55b7c1c18abf, generic specialization <()> of NIOPosix.withAutoReleasePool<A>(() throws -> A) throws -> A at /swift-nio/Sources/NIOPosix/SelectableEventLoop.swift:28
0x55b7c1c18abf, NIOPosix.SelectableEventLoop.run() throws -> () at /swift-nio/Sources/NIOPosix/SelectableEventLoop.swift:460
0x55b7c1c04084, static NIOPosix.MultiThreadedEventLoopGroup.(runTheLoop in _C2B1528F4FBA68A3DBFA89DBAEBE9D4D)(thread: NIOPosix.NIOThread, parentGroup: Swift.Optional<NIOPosix.MultiThreadedEventLoopGroup>, canEventLoopBeShutdownIndividually: Swift.Bool, selectorFactory: () throws -> NIOPosix.Selector<NIOPosix.NIORegistration>, initializer: (NIOPosix.NIOThread) -> (), _: (NIOPosix.SelectableEventLoop) -> ()) -> () at /swift-nio/Sources/NIOPosix/MultiThreadedEventLoopGroup.swift:89
0x55b7c1c04084, closure #1 (NIOPosix.NIOThread) -> () in static NIOPosix.MultiThreadedEventLoopGroup.(setupThreadAndEventLoop in _C2B1528F4FBA68A3DBFA89DBAEBE9D4D)(name: Swift.String, parentGroup: NIOPosix.MultiThreadedEventLoopGroup, selectorFactory: () throws -> NIOPosix.Selector<NIOPosix.NIORegistration>, initializer: (NIOPosix.NIOThread) -> ()) -> NIOPosix.SelectableEventLoop at /swift-nio/Sources/NIOPosix/MultiThreadedEventLoopGroup.swift:110
0x55b7c1c06bce, partial apply forwarder for closure #1 (NIOPosix.NIOThread) -> () in static NIOPosix.MultiThreadedEventLoopGroup.(setupThreadAndEventLoop in _C2B1528F4FBA68A3DBFA89DBAEBE9D4D)(name: Swift.String, parentGroup: NIOPosix.MultiThreadedEventLoopGroup, selectorFactory: () throws -> NIOPosix.Selector<NIOPosix.NIORegistration>, initializer: (NIOPosix.NIOThread) -> ()) -> NIOPosix.SelectableEventLoop at /root/<compiler-generated>:0
0x55b7c1c06ec9, reabstraction thunk helper from @escaping @callee_guaranteed (@guaranteed NIOPosix.NIOThread) -> () to @escaping @callee_guaranteed (@in_guaranteed NIOPosix.NIOThread) -> (@out ()) at /root/<compiler-generated>:0
0x55b7c1c06bed, partial apply forwarder for reabstraction thunk helper from @escaping @callee_guaranteed (@guaranteed NIOPosix.NIOThread) -> () to @escaping @callee_guaranteed (@in_guaranteed NIOPosix.NIOThread) -> (@out ()) at /root/<compiler-generated>:0
0x55b7c1c335e5, closure #1 (Swift.Optional<Swift.UnsafeMutableRawPointer>) -> Swift.Optional<Swift.UnsafeMutableRawPointer> in static NIOPosix.ThreadOpsPosix.run(handle: inout Swift.Optional<Swift.UInt>, args: NIOPosix.Box<(body: (NIOPosix.NIOThread) -> (), name: Swift.Optional<Swift.String>)>, detachThread: Swift.Bool) -> () at /swift-nio/Sources/NIOPosix/ThreadPosix.swift:105
0x7faebbad940a
0x7faeb99a440e
0xffffffffffffffff

Thanks for this! I think this is a straightforward bug, but we're a little short-staffed at the moment so we probably won't get a look at this until next week.

Great, thanks!

We are also encountering this issue. @qusc have you been able to figure out how this crash gets triggered? If I can pinpoint that I might just turn off the feature that's leading to the crash.

On closer inspection we've actually got a different crash than this. Issue filed here: https://github.com/swift-server/async-http-client/issues/576.


Allow to compare 2 files and remove duplicates

I was wondering if it would be possible to have duprule run between 2 files and remove the duplicates that are already contained within the target file.
So, something along the lines of:
duprule new_rule.rule main_rules.rule > new_rules_not_in_main_rules.rule
new_rule.rule = source file
main_rules.rule = file you want to compare new_rule.rule against
new_rules_not_in_main_rules.rule = file that contains the records only found in new_rule.rule and not found in main_rules.rule
Although the syntax and 'how it does it' doesn't really matter that much as long as a person is able to remove rules that you already had in your 'main list'.

Hmm would you be able to achieve this by:
1- cat main_rules.rule new_rule.rule > combined.rule the order of combining is relevant.
2- duprule < combined.rule > combined-uniq.rule: keep first precedence or rule.
3- remove rules that are in combined-uniq.rule & main_rules and thus you'd have rules that are in new rule but not in main_rules.


STAC Data Ingestion

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@5f35f6c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage        ?   72.12%
=======================================
  Files           ?       34
  Lines           ?      653
  Branches        ?        0
=======================================
  Hits            ?      471
  Misses          ?      182
  Partials        ?        0

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 5f35f6c...fa58746. Read the comment docs.


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=399774403
https://github.com/Azure/azure-cli-extensions/commit/86720dc12c21ad9bedb27c9f8381a06c154c76a1

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Warden and Hoglin Posses

Possessed Warden drops (from ancienty city chest):

100% Echo Shard
20% Silence/Ward Smithing Template
50% Music/Fragment disc otherside/5
[Will despawn like normal warden]

Possessed Hoglin drops (only one from the list):

Netherite upgrade/Snout Smithing Template
Return netherite scrap from recipe
Nothing
[if not spawned in the nether will transform in Zoglin (after 15 seconds) and drop only rotten flesh]

Smithing Templates drops from existing possessions:

Eye <- Enderman
Rib <- Wild Hunt
Coast <- Elder Guardian
Spire <- Shulker

Tag changes:

"occultism:fishs" now is "forge:fishs"
Add "mooshroom" to "forge:cows"

Nerfed Wild Hunt:

Each wither skeleton as 1/3 to don't drop the skull

Another great update!
The wild hunt nerf is a good point,
I will merge, but I think we probably need to use forge:fish instead of fishs, I missed that when it was still an occultism tag


More obvious name for upper limit/threshold

Threshold feels like it's the delta, whereas we need an absolute amount, max size?

@siddharthkp I'd like to take this

Ideas on name?

Ideas on name

maxSize makes total sense in this case.

cool, go for it!
please keep backward compatibility in code but remove it from docs :)


Remove restrictions on the MPI library while keeping MPICH as the preferred option

Hi @bsrunnels,
I've removed the fixes for the bending test from this PR and hopefully addressed the issues you raised in #58 regarding MPICH and its alternatives.
Cheers,
-Nuno

@nmnobre Please merge into the development branch - we do not merge incremental changes into master directly.

@nmnobre Please merge into the development branch - we do not merge incremental changes into master directly.

Understood, I've rebased on top of development to clean the commit history.

Hi @bsrunnels,
I have rebased this PR so that only the changes regarding the MPI libraries remain.
No metadata is lost, no information is lost and all build tests are passing.
This is, I believe, a unified solution that doesn't deprive the user from choosing a different MPI library, while still recommending the usage of M(VA)PICH and forcing the user to explicitly allow the usage of a different MPI library.

I agree with @bsrunnels. Please keep the default behavior of the configure script exactly the same. While it is not perfect, our workflow depends on the default behavior.

The default output should now be unmodified.

Under MPI Library it is still printing the output from mpiexec, which is not really relevant to the compile time.

I've kept this since it's as relevant as mpichversion, unless you're telling me you'll be removing mpichversion at some point in the future too.

@nmnobre This PR still changes the default behavior of the configure script. Specifically, in ./.make/Makefile.pre.conf the output should be
MPI_LIB = -lgfortran -lmpich

but is instead
MPI_LIB = -lgfortran

Please modify so that Makefile.pre.conf is unchanged in the default configuration from the development branch.

Does this have to be verbatim or does the latest commit suffice?


Completed Homepage Features, closes #3

Completed Homepage Features tutorial (Link: http://comp4711.jlparry.com/display/tutorial/ci-todo02)
Updated changelog.md

Approved!


Extend ExecutionPayload type with cancun fields

Describe the feature
ref
https://github.com/ethereum/execution-apis/blob/main/src/engine/cancun.md#executionpayloadv3
two additional fields:

dataGasUsed: QUANTITY, 64 Bits
excessDataGas: QUANTITY, 64 Bits

ensure fields are present/missing for v1,v2,v3
ref #2894
blocked by #4186
Additional context
No response

Fixed by #4010


Puppet crashing with segfault

resolution_fixed   |    by<EMAIL_ADDRESS>
I am getting the following error as of changelog:80ef830a2d8e5f155122b8ef2941bf8216c93954/puppet :
$ sudo /usr/local/sbin/puppet-update
+ cd /puppet
+ git pull
Already up-to-date.
+ git submodule update --init
+ puppet apply /puppet/manifests/site.pp
/usr/lib/ruby/1.8/pathname.rb:287: [BUG] Segmentation fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

/usr/local/sbin/puppet-update: line 8: 30427 Aborted                 puppet apply /puppet/manifests/site.pp

I don't think this is related to that change in particular, saw a similar error doing a 'puppet apply --noop' a few commits ago.
It appears that this is an issue with Ruby 1.8 and Puppet 3.4 - http://projects.theforeman.org/issues/4455, http://projects.theforeman.org/issues/4244

Issue migrated from trac:129 at 2024-01-31 17:36:48 +1100

<EMAIL_ADDRESS>commented

This just happened to me as well when trying to run the puppet-update on accessdev

<EMAIL_ADDRESS>commented

Fault appears to be intermittent, Puppet is now running. Maybe there was low memory or something like that?

ibc599 commented

Happen to me as well a couple of days ago on accessdev.nci.org.au

<EMAIL_ADDRESS>commented

Which VM instance are you seeing this on?

<EMAIL_ADDRESS>commented

OK, I'll see if I can reproduce it in the test environment.

<EMAIL_ADDRESS>commented

After 308 test runs over night hasn't failed so far.  Due to the intermittent nature of the bug we can't ever be 100% sure that it's resolved, but looking promising so far.

ibc599 commented

Hi Chris,
Thanks alot. Can you let us know what needs to be done on accessdev?

<EMAIL_ADDRESS>commented

Finally managed to reproduce it in a test VM.  Similar to the Foreman bug report, the problem is occurring when Ruby's GC is attempting to mark active objects and it dereferences an invalid pointer.
Program received signal SIGSEGV, Segmentation fault.
gc_mark (ptr=7021806046636302704, lev=1) at gc.c:804
804         if (obj->as.basic.flags == 0) return;       /* free cell */
(gdb) info line 804
Line 804 of "gc.c" starts at address 0x2aaaaad1e1e0 <gc_mark+32>
   and ends at 0x2aaaaad1e1e8 <gc_mark+40>.
(gdb) disas 0x2aaaaad1e1e0,0x2aaaaad1e1e8
Dump of assembler code from 0x2aaaaad1e1e0 to 0x2aaaaad1e1e8:
=> 0x00002aaaaad1e1e0 <gc_mark+32>:     mov    rax,QWORD PTR [rdi]
   0x00002aaaaad1e1e3 <gc_mark+35>:     test   rax,rax
   0x00002aaaaad1e1e6 <gc_mark+38>:     je     0x2aaaaad1e1d3 <gc_mark+19>
End of assembler dump.
(gdb) x $rdi
0x6172776573726170:     Cannot access memory at address 0x6172776573726170
(gdb) where
#0  gc_mark (ptr=7021806046636302704, lev=1) at gc.c:804
#1  0x00002aaaaad1e162 in gc_mark_children (ptr=<value optimized out>, lev=1)
    at gc.c:1063
#2  0x00002aaaaad1dd0f in mark_locations_array (x=<value optimized out>,
    n=33885) at gc.c:690
#3  0x00002aaaaad1e5b7 in garbage_collect () at gc.c:1493

There is also another GC related bug open on RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=876686
I'll see if Ruby 1.9 makes a difference.

<EMAIL_ADDRESS>commented

Sure, I just need to do some more testing first.  Should be ready later today.

<EMAIL_ADDRESS>commented

Thanks Chris for the quick work on this !
Can you say a little more on what the fix contains ?
Is there likely to be any impact on the Accessdev setup seen by users ?
Or does it just affect the puppet infrastructure for installing Accessdev and otherwise transparent ?
Robin

<EMAIL_ADDRESS>commented

Off topic- I had a look at that foreman project where those bug reports came from. It's a combined web interface that can boot Openstack nodes then configure them with Puppet, sort of an amalgamation of the Openstack and Puppet dashboards. Might be useful to have something like this for the NCI cloud someday.

<EMAIL_ADDRESS>commented

I've committed a fix to my branch now, so whomever is wearing the master branch hat today should run:
git checkout master
git pull
git cherry-pick 3081d32
git push origin HEAD

Then on accessdev-test.nci.org.au:
cd /puppet
sudo git pull
sudo ./tools/install-puppet

Providing that it reports successful completion, do a trial Puppet run and check for any errors:
sudo puppet apply --noop /puppet/manifests/site.pp

If it all looks good, then you can repeat the steps on accessdev.nci.org.au

<EMAIL_ADDRESS>commented

That's still using Ruby 1.8.  Try running hash -r in your shell first to remove any cached paths.

<EMAIL_ADDRESS>commented

uh, not so good :(
[I] Installation complete
[pfu599@accessdev-test puppet]$ sudo puppet apply --noop /puppet/manifests/site.pp
/usr/lib/ruby/site_ruby/1.8/puppet/parser/type_loader.rb:121: [BUG] rb_gc_mark(): unknown data type 0x20(0x7f6994b5bed8) non object
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

<EMAIL_ADDRESS>commented

The patch changes how Ruby and Puppet are installed.  It uses a newer version of Ruby (1.9.3 vs. 1.8.7) from the CentOS software collections repo.  Exactly the same version of Puppet is installed as before, just using a different installation method.  There are no changes to any of our Puppet modules.  You shouldn't notice any difference in terms of the outcomes of running Puppet.  Obviously since the underlying Ruby has changed, there is a small risk that some code in Puppet changes behaviour so that's why it's still a good idea to test it first.

<EMAIL_ADDRESS>commented

OK, I'll have a go at putting these changes through and test them on accessdev-test. Thanks Chris!

<EMAIL_ADDRESS>commented

Actually you'll need to specify the full path because sudo is resetting PATH:
$ sudo /usr/local/bin/puppet apply --noop /puppet/manifests/site.pp

(A wrapper script is needed to invoke Puppet with the newer Ruby)

<EMAIL_ADDRESS>changed _comment1 which not transferred by tractive

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>commented

Ok, that looks better!
So from now on we can't use the "puppet" command by itself, but have to call the wrapper script explicitly?
When I update puppet I often use this command:
sudo /usr/local/sbin/puppet-update

This seems to run fine, but doesn't use the wrapper as above. Do you think this could also cause problems?

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>commented

Right yes, in that case use the -i option so that the path is set correctly:
sudo -i puppet apply --noop /puppet/manifests/site.pp
sudo -i puppet-update

We may add /usr/local/(s)bin to the sudo path by default in future.

<EMAIL_ADDRESS>commented

Milestone Future deleted

<EMAIL_ADDRESS>commented

Alright. So we have a work around that works now anyway.

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>changed status from new to closed


Update custom-page.mdx

https://github.com/web-infra-dev/rspress/blob/main/packages/core/src/theme-default/styles/vars.css is 404 --->>>
https://github.com/web-infra-dev/rspress/blob/main/packages/theme-default/src/styles/vars.css
Summary
Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Feature Request]: Option to make Hold and Roll windows independent of the Judge Setting

Is there an existing issue for the feature?

[X] I have searched the existing feature requests

Describe the Feature
Similar issue to #650 but the other way around.
Could we get either

a boolean Option that fixes the Hold and Roll windows to be the same as J4 regardless of the Judge in use
or
a separate Judge Setting for Hold and Roll windows

How Does The Feature Add To The Game?
Judges should not make the game harder but instead provide additional feedback for Acc Play. However having the Hold and Roll windows tied to the Judge Setting breaks this "Rule". Adding this option would make higher judges more accessible for files that utilizes these note types.
Additional Context
No response

rendered void by 37e56a80e8d4a2a9a87a5b8ee7c6b7c485549490 04f30d0ff209c24d78637e3e588537f2f89585a2


Adding onEnter to frost-text to trigger actions using the enter key

#fix#
CHANGELOG
Added onEnter to frost-text so that actions can be triggered using the enter key when the input is in focus

Approved


build error due to missing urldecode from download.c

master branch openwrt, failed to build oui as urldecode is not defined in the repo.
Description:
download.c:77:5: error: implicit declaration of function 'urldecode' [-Werror=implicit-function-declaration]
     urldecode(params->path, sizeof(params->path), params->path, strlen(params->path));

master branch openwrt, failed to build oui as urldecode is not defined in the repo.
Description:
download.c:77:5: error: implicit declaration of function 'urldecode' [-Werror=implicit-function-declaration]
     urldecode(params->path, sizeof(params->path), params->path, strlen(params->path));

I had this problem too,how to solve this?

https://github.com/openwrt/packages/pull/14789


Hugo 0.11 can't see config file with non-default name

I've separated my sites into a few separate repositories. The repository in charge of rendering and publishing my sites has all my config files, named after the site they configure. These config files point to the other repositories which contain the markup/templates and content. Up until now (0.11) I've used the --config flag to point to the correct config file but it's not working anymore:
$ hugo_0.11 server --config=my-site.yaml
ERROR: 2014/06/09 Config not found... using only defaults, stuff may not work
...

Renaming the config file to config.yaml makes it work again but this appears to be a breaking change from 0.10.

When I use hugo server it gives me the error Config not found... using only defaults, stuff may not work. I'm using version 0.13. Do you need anymore information about this?

You need to run hugo in a folder with a config.{yaml, toml, json} file

I did but I updated my comment with the second error. Did you see that?

Weird hugo is looking into a path for hugo that isn't in my path variable. Now I'm just confused. Any idea's on how to troubleshoot?

are you missing the static directory in your project?

No it's there. But why is hugo using the wrong version? How do I tell Hugo to use the current version. I've tried updating my environmental variable.

I updated the old path with the new Hugo binary 0.13 and now I get a different error when I use hugo server Failed to read data from desktop.ini/desktop.ini: Data not supported for extension 'ini'

Inside /content, probably.

Aha I found it. It was hidden from me. This file was created by Google drive sync. @spf13 What should I do about this?


Code separation for storage location and storage format

@axtimwalde
@joshmoore and I were thinking whether it would be possible (and make sense) to separate the code in terms of storage location and storage format.
So for example, one could have something like
new N5Reader( StorageLocation storageLocation, StorageFormat storageFormat )

with, e.g.,
enum StorageLocation {
   FileSystem
   AWSS3,
   GoogleCloud
}

enum StorageFormat {
   N5,
   Zarr
}

This would of course mainly make sense if one would manage within the N5Reader class to be able to mix and match the two things, thereby avoiding code duplication.
Not sure I am making sense?
Maybe @joshmoore can formulate this more professionally?

@axtimwalde and I talked about this recently.
This would involve big changes, and so won't happen soon, but I agree its desirable and should be on the roadmap.

@bogovicj : do you have any idea of a workaround? Our hope was to be able to access IDR data in OME-Zarr on S3 via the N5 stack for I2K? (Wow. The acronyms abound!) My best guess would be to make a copy/fork of n5-aws-s3, add a dependency on n5-zarr, and migrate the N5ZarrReader use of DType etc. into https://github.com/saalfeldlab/n5-aws-s3/blob/master/src/main/java/org/janelia/saalfeldlab/n5/s3/N5AmazonS3Reader.java (or a subclass).

Wow. The acronyms abound!

:joy:

make a copy/fork of n5-aws-s3, add a dependency on n5-zarr,

Either that or the reverse - fork n5-zarr and depend on n5-aws-s3.  Not sure which would be less work in the end...
Were I to try to hack something together quickly, I think I might start with N5ZarrReader, rip out any filesystem calls, and try to replace with the appropriate stuff in N5AmazonS3Reader

Gotcha. The only other suggestion that has also been discussed on the Zarr side (https://github.com/zarr-developers/zarr-python/issues/540) would be a wrapper strategy roughly of the form:
n5 = new N5ZarrWrapper(new N5AmazonS3Reader())

I think the most mature path forward is to introduce a separate interface for KeyValueStores implement the N5Reader and N5Writer interfaces for various dialects (N5, Zarr, BrainMaps, Boss, ...) on top of this.  This could capture file-system and cloud storage but would not be appropriate for HDF5 which is fine but noteworthy.  Also, while this sounds trivial at first glance it becomes a bit icky when considering the differences in how the various backends lock (or don't lock), i.e. the currently straight forward file-system logic will become clunkier.  This is mainly why I haven't touched it yet.  Sipping file-system and doing it only for cloud-storage interfaces defeats the purpose...

@axtimwalde : hmmm.... could you sketch out a bit of the inheritance hierarchy that you'd see?  Or is the design of that hierarchy part of the problem and therefore needs more time?
Is there any short-term path forward that you wouldn't consider monsterous?

As a short term hack, I would plug the AWS S3 access logic into a copy of n5-zarr as @bogovicj sugested, and add alternative readers and writers to the n5-zarr repo. It's not too much work and will be consistent with people using N5 through the N5Reader and N5Writer interfaces which they should.  This would also cover all practical use cases that we currently have.

I've opened https://github.com/saalfeldlab/n5-zarr/pull/5 as a draft. It's possible that this should never be merged and instead should exist in a separate branch and/or repository.

Closing this issue now that AmazonS3KeyValueAccess exists for the purpose of achieving this separation.


Autobuyer gone on Chrome Extension

The auto buyer is still gone for the Chrome Extension. Has an update been released for that yet?

try reinstalling the filter by deleting the old one. if that still didn't fix then try reinstalling tampermonkey. and make sure your web app page size is 100


SDK 25 framework.jar

Taken from CM14.1, not a very good source but useable.
https://drive.google.com/open?id=0Bxhk8H_5bn54d1dUR2xrYWZuT2s

Any updates? I'd be great to have android.jar for API 25.

Use this version of mine
https://goo.gl/08ZeXy

@minhdangoz There's only one folder named android-24. I'm looking for version 25.

@jakubturcovsky I'm facing heavy tasks from my lecturer. I hope you can be patient until this Friday for the new version of hidden API.
Thanks.

I can send it if you wish. Where to look for it?

We just released hidden API v25. Check it out!


top args cause to error

Description
i'm trying to use top command with ps args. while the args working with ps command, it cause to error in the top command.
Steps to reproduce the issue:

docker run tomcat:8.0
docker top [container_id] -e -o pid,lstart,pcpu,pmem,sz,ni,stat,cmd

Describe the results you received:
Error response from daemon: Error running ps: exit status 1
Describe the results you expected:
the same as the output of the command (without the info of the ps command itself):
docker exec [container_id] ps -e -o pid,lstart,pcpu,pmem,sz,ni,stat,cmd
PID                            STARTED  %CPU  %MEM        SZ  NI STAT  CMD
1 Sun Feb 19 07:20:26 2017       0.3      7.4     530522   0    Ssl   /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Djava.endorsed.dirs=/usr/local/tomcat/endorsed -classpath /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.io.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start
128 Sun Feb 19 07:55:42 2017  0.0  0.1  2694   0 Rs   ps -e -o pid,lstart,pcpu,pmem,sz,ni,stat,cmd
Output of docker version:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 14
 Running: 1
 Paused: 0
 Stopped: 13
Images: 6
Server Version: 1.13.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 101
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.8-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.941 GiB
Name: moby
ID: KBZQ:5QHB:AZ3R:YD3F:C75G:OGQA:6YIT:D46Z:CDSI:D2N5:7MZT:MYTH
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 20
 Goroutines: 31
 System Time: 2017-02-19T07:57:39.1496673Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
working on windows 10

Hi, unfortunately the flags for docker top are not defined. Docker just shells out to whatever ps binary is installed on the machine passing the flags (not one in the container). Unfortunately at present Docker for Mac and Windows do not have the same version of ps as the one installed in your container. Can you open an issue on https://github.com/docker/for-win/issues and I will see if this can be changed to be more "standard", but it really should be fixed in Docker too...

@justincormack
Can we install some "standard" ps as docker-ps?  (for avoiding confusion with docker ps, maybe it should be installed under $PREFIX/libexec rather than $PREFIX/bin)


Error when compiling fil_backend

Triton-Inference-Server is seeing an error when attempting to compile the fil_backend. Below is the error given by cmake:
[build-stage 3/4] RUN source /conda/dev/bin/activate  && cmake       --log-level=VERBOSE       -GNinja       -DCMAKE_BUILD_TYPE="Release"       -DBUILD_TESTS=""       -DTRITON_CORE_REPO_TAG="main"       -DTRITON_COMMON_REPO_TAG="main"       -DTRITON_BACKEND_REPO_TAG="main"       -DTRITON_ENABLE_GPU="ON"       -DTRITON_ENABLE_STATS="ON"       -DRAPIDS_DEPENDENCIES_VERSION="24.04"       -DTRITON_FIL_USE_TREELITE_STATIC="ON"       -DCMAKE_INSTALL_PREFIX=/rapids_triton/install       ..  && cd _deps/treelite-src  && git apply /rapids_triton/0001-Allow-predicting-with-FP32-input-and-FP64-models.patch  && cd ../..:

...

#32 43.85 CMake Error at build/_deps/raft-src/cpp/CMakeLists.txt:667 (target_link_libraries):
#32 43.85   The link interface of target "raft_distributed" contains:
#32 43.85
#32 43.85     ucx::ucp
#32 43.85
#32 43.85   but the target was not found.  Possible reasons include:
#32 43.85
#32 43.85     * There is a typo in the target name.
#32 43.85     * A find_package call is missing for an IMPORTED target.
#32 43.85     * An ALIAS target is missing.
#32 43.85
#32 43.85
#32 43.85
#32 43.85 CMake Generate step failed.  Build files cannot be regenerated correctly.

This failed our nightly build and looks to be related to the following change: https://github.com/triton-inference-server/fil_backend/pull/394
Let us know of any more information you need to troubleshoot, and thanks in advance for the help!

Can you post the Docker command I can use to reproduce the error?

Hi @hcho3, we use the below steps to build FIL backend:
git clone --recursive --single-branch --depth=1 -b main https://github.com/triton-inference-server/fil_backend.git fil

cd fil

mkdir build && cd build

cmake -DTRT_VERSION=<IP_ADDRESS>+cuda<IP_ADDRESS> -DCMAKE_TOOLCHAIN_FILE= -DVCPKG_TARGET_TRIPLET= -DTRITON_FIL_DOCKER_BUILD:BOOL=ON -DTRITON_BUILD_CONTAINER=nvcr.io/nvidia/tritonserver:24.06-py3-min -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=`pwd`/install -DTRITON_REPO_ORGANIZATION:STRING=https://github.com/triton-inference-server -DTRITON_COMMON_REPO_TAG:STRING=main -DTRITON_CORE_REPO_TAG:STRING=main -DTRITON_BACKEND_REPO_TAG:STRING=main -DTRITON_ENABLE_GPU:BOOL=ON -DTRITON_ENABLE_MALI_GPU:BOOL=OFF -DTRITON_ENABLE_STATS:BOOL=ON -DTRITON_ENABLE_METRICS:BOOL=ON -DTRITON_ENABLE_MEMORY_TRACKER:BOOL=ON ..

cmake --build . --config Release -j256 -v -t install

@krishung5 Did you apply the patch 0001-Allow-predicting-with-FP32-input-and-FP64-models.patch to _deps/treelite-src ?

I don't think we did. Is the patch required to build on main or r24.07 branch? Let me try that meanwhile.

Yes. The patch is required. Does your build system not use https://github.com/triton-inference-server/fil_backend/blob/main/build.sh from this repo?

Running this command
cmake -DTRT_VERSION=<IP_ADDRESS>+cuda<IP_ADDRESS> -DCMAKE_TOOLCHAIN_FILE= -DVCPKG_TARGET_TRIPLET= -DTRITON_FIL_DOCKER_BUILD:BOOL=ON -DTRITON_BUILD_CONTAINER=nvcr.io/nvidia/tritonserver:24.06-py3-min -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=`pwd`/install -DTRITON_REPO_ORGANIZATION:STRING=https://github.com/triton-inference-server -DTRITON_COMMON_REPO_TAG:STRING=main -DTRITON_CORE_REPO_TAG:STRING=main -DTRITON_BACKEND_REPO_TAG:STRING=main -DTRITON_ENABLE_GPU:BOOL=ON -DTRITON_ENABLE_MALI_GPU:BOOL=OFF -DTRITON_ENABLE_STATS:BOOL=ON -DTRITON_ENABLE_METRICS:BOOL=ON -DTRITON_ENABLE_MEMORY_TRACKER:BOOL=ON ..

invokes the Docker build with ops/Dockerfile, which already applies the patch automatically.

Just tried the build command (cmake -DTRT_VERSION=...) on my end. I can't reproduce the error at all. Let me clean the Docker cache and try again.

@krishung5 Can you try this fix? https://github.com/triton-inference-server/fil_backend/pull/396

@hcho3 Confirmed that I was able to build fil_backend with the fix. Thanks for the quick fix!

Sure, let me bring it to the release branch.


Full screen navigation with nested beamers?

I have a main beamer that handles navigation between onboarding, login and the main screen.
The main screen has a bottom navigation bar where each tab has it's own beamer, I have some detail views where I want to break out of the nested beamer and display the page full screen, how can I accomplish this?

Hey @sprite2005 :wave:
Thanks for creating an issue!
As your Beamers in bottom navigation are nested within the body portion of the Scaffold, they cannot "break out" to full screen. Any page that should be put full-screen, i.e. pushed above the bottom navigation part, should be handled within the root Beamer.
You can see this in bottom_navigation_2 example. Although it is not using nested Beamers in the body, the main idea is there.
Let me know if this helped

Thanks.


Request for a standalone version of the Anki Addon

Hello,
I really appreciate the functionality of the Anki addon that you have created. However, I was wondering if it would be possible to have a standalone version of the application. This would allow me to use the application without having to always keep Anki open.
I understand that the addon was designed specifically for Anki and may have dependencies that require it to be integrated with the Anki platform.
Would it be possible to consider creating a standalone version of the application? I believe this would be a great addition to your project and would provide more options for users.
Thank you for your consideration.

Hey,
Thanks for the suggestion! There was actually a minor internal issue that originally prevented me from implementing this, but I believe it should be fixed now. Before today, the following __init__.py file was always importing anki modules, but this if statement should hopefully solve it so it only gets imported if it was ran by Anki:
https://github.com/Aquafina-water-bottle/local-audio-yomichan/blob/2ba3bc7c4d102062f2cbba2607dff611143bcf42/plugin/__init__.py#L5-L10
With all that being said, you should be able to run the server without Anki now. I added some instructions on how to run it here. Please let me know if it works!

With all that being said, you should be able to run the server without Anki now. I added some instructions on how to run it here. Please let me know if it works!

Wow, you're lightning fast! I did what you said and it is working like a charm. Thanks a ton for your help, it's seriously appreciated!


Stringify JSON we send to Google Analytics

Google Analytics expects labels to be Strings instead of JSON
objects. Stringiy the data we send them otherwise the values will be
converted to null values.
Docs: https://developers.google.com/analytics/devguides/collection/analyticsjs/events

:+1:


Site : Allow changing the color of downloaded PNGs

It's a bit unconvenient to download a PNG icon without being able to choose its color, you have to manually recolor the picture afterwards.
Please add a color picker, to change the color of the downloadable PNGs.

Maybe we can add a global color adjuster, like the feather site.

Can I give this one a try?

Sure!


Implement robust error handling

There's barely any error handling in the code right now. Investigate the code and implement error handling where necessary.

Incorporate Enclose/Confirm

[ ] #41


CHAOS-5505 Cleanup

Content cleanup

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6648f750abb34a0dfcc6e477--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664d82b1f8af839cde3248b0--harness-developer.netlify.app


oneDNN: 2.3.2 -> 2.5.2

Description of changes

Changelog: https://github.com/oneapi-src/oneDNN/releases/tag/v2.5.2
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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/)
22.11 Release Notes (or backporting 22.05 Release notes)

[x] (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.

Sorry, I zoned out, saw all the CI was green, and clicked the merge button without thinking!  You need to bump the sha256 in the fetchFromGithub to update the fixed output derivation.  Change it to something like sha256 = "sha256-HHHHHHHHH/6UkAxz/KDFb/gyX2SI1S2GwgXAXSTU/c=";, try a build, and it'll tell you the answer.

Sorry for the delay and the oversight on the sha256.  Now I'm wondering why this isn't picked up by the CI!
Does this PR need to be reopened or should I make a new one?

Result of nixpkgs-review pr 200665 run on x86_64-linux 1

6 packages built:

aitrack
obs-studio-plugins.obs-backgroundremoval
oneDNN
onnxruntime
python310Packages.onnxruntime
python39Packages.onnxruntime


Convert to ESM

To unblock #206 in this and the equivalents in all the other repos, upgrade the whole thing to use ESM instead of CJS.

This seems to cause some problems related to the non-top-level requires, and ones that need dynamic dependency names. Need to see what to use for those.


Impossible to debug situations with flutter web

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
How are we supposed to debug web application when we have a stack traces like this that don't contain any hints of the source code?
I can't even post the whole stack trace because "There was an error creating your Issue: body is too long (maximum is 65536 characters)."
Expected results
file name and line number where the issue is
Actual results
useless stack trace, see logs
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration

Logs
see for full log https://pastebin.com/0WVDYXka
Logs
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown while applying parent data.:
Incorrect use of ParentDataWidget.
The ParentDataWidget Expanded(flex: 1) wants to apply ParentData of type FlexParentData to a
RenderObject, which has been set up to accept ParentData of incompatible type
_OverflowBarParentData.
Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically,
Expanded widgets are placed directly inside Flex widgets.
The offending Expanded is currently placed inside a OverflowBar widget.
The ownership chain for the RenderObject that received the incompatible parent data was:
  SizedBox.shrink ← Expanded ← Spacer ← OverflowBar ← Align ← Padding ← Container ← IntrinsicHeight
← MediaQuery ← Padding ← ⋯
When the exception was thrown, this was the stack:
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 266:49  throw_
packages/flutter/src/widgets/framework.dart 6119:11                                                                        <fn>
packages/flutter/src/widgets/framework.dart 6135:14                                                                        [_updateParentData]
packages/flutter/src/widgets/framework.dart 6159:7                                                                         attachRenderObject
packages/flutter/src/widgets/framework.dart 5828:5                                                                         mount
packages/flutter/src/widgets/framework.dart 6376:11                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 6512:36                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 6524:32                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        mount
<snip>
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 5124:11                                                                        [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 5133:11                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 5124:11                                                                        [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 6377:14                                                                        mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 5133:11                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 5124:11                                                                        [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 5133:11                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 5124:11                                                                        [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/framework.dart 4993:16                                                                        performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                                                                         rebuild
packages/flutter/src/widgets/framework.dart 4950:5                                                                         [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                                                                         mount
packages/flutter/src/widgets/framework.dart 3953:15                                                                        inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                                                                        updateChild
packages/flutter/src/widgets/binding.dart 1176:16                                                                          [_rebuild]
packages/flutter/src/widgets/binding.dart 1145:5                                                                           mount
packages/flutter/src/widgets/binding.dart 1092:16                                                                          <fn>
packages/flutter/src/widgets/framework.dart 2682:19                                                                        buildScope
packages/flutter/src/widgets/binding.dart 1091:12                                                                          attachToRenderTree
packages/flutter/src/widgets/binding.dart 925:24                                                                           attachRootWidget
packages/flutter/src/widgets/binding.dart 906:7                                                                            <fn>
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/isolate_helper.dart 48:19       internalCallback
════════════════════════════════════════════════════════════════════════════════════════════════════

Flutter Doctor output
Doctor output
 Flutter (Channel unknown, 3.7.3, on Microsoft Windows [Version 10.0.19045.2311], locale en-150)

Hi @ristiisa. Thanks for filing this issue. From your logs
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown while applying parent data.:
Incorrect use of ParentDataWidget.
The ParentDataWidget Expanded(flex: 1) wants to apply ParentData of type FlexParentData to a
RenderObject, which has been set up to accept ParentData of incompatible type
_OverflowBarParentData.
Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically,
Expanded widgets are placed directly inside Flex widgets.
The offending Expanded is currently placed inside a OverflowBar widget.
The ownership chain for the RenderObject that received the incompatible parent data was:
  SizedBox.shrink ← Expanded ← Spacer ← OverflowBar ← Align ← Padding ← Container ← IntrinsicHeight
← MediaQuery ← Padding ← ⋯

The issue seems to be with your code implementation and the main issue is dues to Incorrect use of ParentDataWidget.. The logs also hint on how to solve this, kindly look into the above.
Closing this as this doesn't seem to be an issue with Flutter itself, if you disagree kindly write in the comments and I'd reopen this.

please understand that the issue was not what is wrong but seeing that the web version of flutter produces stack traces that are not usable.

logs also hint on how to solve this
I have several number of widgets, the hint as as useful as saying "ERROR"

Hi @ristiisa. Thanks for explaining further. I understand this now. I'm trying to reproduce a similar error log on my end, Please can you share a completed and minimal reproducible code sample that reproduces this issue? Also, I see you are on an older version of flutter, can you upgrade to the latest version to confirm the error logs are similar?

This also happens with flutter 3.10.3. Here is the minimal code that produces the unusable stack trace:
import 'package:flutter/material.dart';

void main() async {
  runApp(MaterialApp(home: MyHomePage()));
}

class MyHomePage extends StatefulWidget {
  MyHomePage({super.key});

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  void initState() => super.initState();

  @override
  Widget build(BuildContext context) => Scaffold(
    appBar: AppBar(title: Text("title")),
    persistentFooterButtons: [
      TextButton(onPressed: () {}, child: Text("button1")),
      Spacer()
    ],
    body: Container(height: MediaQuery.of(context).size.height)
  );
}

Error: Incorrect use of ParentDataWidget.
The ParentDataWidget Expanded(flex: 1) wants to apply ParentData of type FlexParentData to a RenderObject, which has been set up to accept ParentData of incompatible type _OverflowBarParentData.
Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically, Expanded widgets are placed directly inside Flex widgets.
The offending Expanded is currently placed inside a OverflowBar widget.
 Thanks for responding. I can see the same error message on mobile as well, hence this might not be an issue with it being on web and be the expected behaviour for this exact kind of error message.


Few enchances

1.It would be great to support pabot and parallel test recording based on window
2. It would be really helpful to add option to reflect currrent executed kewyords as subtitles

Hello @extr3mal
ScreenCapLibrary currently works well with pabot taking into consideration that you refer to

based on window

as recording different monitors at once. Below is a simple example that will work with pabot
*** Settings ***
Library  ScreenCapLibrary

*** Test Cases ***
Foo
	Start Video Recording  1  monitor=1
	# do what you want to be recorded on monitor 1
	Stop Video Recording  1
Bar
	Start Video Recording  2  monitor=2
	# record what you do on monitor 2
	Stop Video Recording  2

The above code could be run using pabot --testlevelsplit <path to testfile>
If you think about window as an application window this is not possible because currently ScreenCapLibrary works by selecting monitors.
Please tell us if you had something else in mind or if the above code helps you.
Best regards,
Andrei.

Hello @extr3mal
ScreenCapLibrary currently works well with pabot taking into consideration that you refer to

based on window

as recording different monitors at once. Below is a simple example that will work with pabot
*** Settings ***
Library  ScreenCapLibrary

*** Test Cases ***
Foo
	Start Video Recording  1  monitor=1
	# do what you want to be recorded on monitor 1
	Stop Video Recording  1
Bar
	Start Video Recording  2  monitor=2
	# record what you do on monitor 2
	Stop Video Recording  2

The above code could be run using pabot --testlevelsplit <path to testfile>
If you think about window as an application window this is not possible because currently ScreenCapLibrary works by selecting monitors.
Please tell us if you had something else in mind or if the above code helps you.
Best regards,
Andrei.