[BUG] Update Xamarin Forms Samples to work with latest Xamarin

Update Xamarin Forms Samples to work with latest Xamarin
Build Errors
Project "/Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj" (Build target(s)):

Target WinUICheckTargetPlatformVersion:
    /Users/pchopra/.nuget/packages/xamarin.forms/<IP_ADDRESS>1250/build/Xamarin.Forms.targets(189,5): warning : Xamarin.Forms recommends TargetPlatformMinVersion >= 10.0.14393.0 (current project is -1)
    /Users/pchopra/.nuget/packages/xamarin.forms/<IP_ADDRESS>1250/build/Xamarin.Forms.targets(195,5): warning : Xamarin.Forms recommends TargetPlatformVersion >= 10.0.17763.0 (current project is -1)
Done building target "WinUICheckTargetPlatformVersion" in project "MasterDetail.csproj".
Target ResolvePackageAssets:
    /Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj : error NU1605: Detected package downgrade: Xamarin.Forms from <IP_ADDRESS>1 to <IP_ADDRESS>1250. Reference the package directly from the project to select a different version.
    /Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj : error NU1605:  MasterDetail -> ReactiveUI.XamForms 12.1.5 -> Xamarin.Forms (>= <IP_ADDRESS>1)
    /Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj : error NU1605:  MasterDetail -> Xamarin.Forms (>= 4.3.0)
Done building target "ResolvePackageAssets" in project "MasterDetail.csproj" -- FAILED.

Done building project "MasterDetail.csproj" -- FAILED.

Build FAILED.

/Users/pchopra/.nuget/packages/xamarin.forms/<IP_ADDRESS>1250/build/Xamarin.Forms.targets(189,5): warning : Xamarin.Forms recommends TargetPlatformMinVersion >= 10.0.14393.0 (current project is -1)
/Users/pchopra/.nuget/packages/xamarin.forms/<IP_ADDRESS>1250/build/Xamarin.Forms.targets(195,5): warning : Xamarin.Forms recommends TargetPlatformVersion >= 10.0.17763.0 (current project is -1)
/Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj : error NU1605: Detected package downgrade: Xamarin.Forms from <IP_ADDRESS>1 to <IP_ADDRESS>1250. Reference the package directly from the project to select a different version.
/Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj : error NU1605:  MasterDetail -> ReactiveUI.XamForms 12.1.5 -> Xamarin.Forms (>= <IP_ADDRESS>1)
/Users/pchopra/Projects/ReactiveUI.Samples/xamarin-forms/MasterDetail/MasterDetail/MasterDetail.csproj : error NU1605:  MasterDetail -> Xamarin.Forms (>= 4.3.0)
    2 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.09

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Cloned the repo and tried to build main branch but fails with the below errors

Environment
VS Mac version: 8.8.5 (build 18)
Mono <IP_ADDRESS>
Xamarin.iOS Version: <IP_ADDRESS>
Xamarin.Android Version: <IP_ADDRESS>

I can update the solutions and create a PR

I can update the solutions and create a PR

PR will be appreciated thanks

PR will be appreciated thanks

Closing this PR, fixed by #289

Closing this PR, fixed by #289


[Feature Request]: i would like to improve the footer section

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
i want to imrove the footer section of the page from this

to something like this

please allow me to work on this issue under gsoc ext
Use Case
Enhanced User Experience
Improved Site Navigation
Benefits
No response
Priority
Medium
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

plz assign me this issue under gsoc extended

done 👍

#164  plz assign points to me for it

@mansiruhil13 it seems like i was not awarded points for this contribution

@mansiruhil13 it seems like i was not awarded points for this contribution

yes may ne due to labels. but now labels correction sorted out. and the faq page assigned now for better ui improvement

Ok

@mansiruhil13 it seems like i was not awarded points for this contribution

yes may ne due to labels. but now labels correction sorted out. and the faq page assigned now for better ui improvement

What labels ??

@mansiruhil13 it seems like i was not awarded points for this contribution

yes may ne due to labels. but now labels correction sorted out. and the faq page assigned now for better ui improvement

What labels ??

label1,2,3 and gssoc-ext

ok


Queation: how do I get mesh struct from the model IntPtr?

Hello,
Thank you for this wonderful bind!
I have a loaded model that I want to extract meshes from to use with the DrawMesh() APIs. However, I could not find any way to convert the meshes IntPtr that the model holds into the c# Mesh struct required for the DrawMesh() calls.
Did I miss something?
Thanks

Nevermind I just realized you could marshel the IntPtr directly to the struct and it works. I assume you're planning to keep the structs compatible with the C++ side so it won't break in the future.


Moved to using an Environment Variable rather than polling the DescribeStacks API

The DescribeStacks API is rate limited and in large deployments you will run into rate limiting that will prevent events from being pushed to Kibana. As the endpoint for ES is static we can instead pass the endpoint via an environment variable.
Also had to made some other dependencies in order to fix some possible timing issues with creating resources.

centralized logging solution has been updated, the issue has been addressed in v2

Closing pull request as issue has been fixed.


Opening file from Recents or Favorites

Expected Behavior
Opening a file in Editor from Recent or Favorites should treat the file as a previously saved file rather than a brand-new file that needs to be manually saved again.
Actual Behavior
The file from Recent or Favorites is treated like a new file where the Save or Discard dialogue box appears when trying to start a new file. If Discard is chosen, the text disappears and any attempt to reload the file still shows a blank Editor as if the file contents have been lost. Switching to the Console and back to the Editor suddenly reveals the file contents.
Steps to Reproduce the Problem

Switch to Editor
Choose Open… from the menu bar and select a file from Recent or Favorites
Choose New from the menu bar
Notice the dialogue box that prompts you to Save or Discard, as if the previously opened file had never been saved before.
Choose Discard
Notice the Editor is now clear of text
Open the file once again by any method, such as selecting from Recent Files in the menu bar
Notice the Editor remains blank as if the file contents have been lost
Switch to Console and back to Editor
Notice the file contents have reappeared

https://github.com/objecthub/swift-lisppad-ios/assets/68421539/e7296aff-b4c1-4967-8eec-fc567b4527b9
Specifications

Version: 2.0
Platform: iOS 17.3

Wow, this is a pretty serious issue. Thanks for reporting it. It has been fixed with commit 566685e.

This has been fixed with release 2.0.1.


Valid encoding names

Hi there!
We have this line in our sdp data:
a=rtpmap:99 image.svg.data/90000
This lib uses a regex that only parses image as the encoding name (and fails to parse the clock rate).
Do you have any specification regarding if image.svg.data is a valid encoding name, or if the regex should be updated to allow dots in the encoding name?

Hello!
That should be valid, I think. The rfc, basically only says to treat slashes or spaces special for this a= line, so it should be safe to extend the regex.

Implemented in sdp-transform 1.6.2 thanks to @alexanderklintstrom :)


[Support] How I can pass variable by URL?

I am having this in my admin.php
CRUD::resource('xmlfile', 'XmlfileCrudController');
and I changed to this:
CRUD::get('xmlfile/{filetype?}', 'XmlfileCrudController');
but it will collapse the login process...
and some routes with duplicate variable will be created.
|        | DELETE                         | admin/xmlfile/{filetype}/{{filetype}}                        | crud.xmlfile/{filetype}.destroy         | App\Http\Controllers\Admin\XmlfileCrudController@destroy                             | web,admin,Closure |
Please advise!

That is because by using the CRUD::resource() it automatically defines all of those routes, my best recommendation would be to pick a new URL as you can't really overwrite it unless you disable the automatic URL generation.
My recommendation would be:
CRUD::resource('xmlfile', 'XmlfileCrudController')->with(function() {
    Route::post('export/{type}', 'XmlfileCrudController@export');
});


[APIC-273] Add Table Columns Parameter

JIRA Ticket:
APIC-273
Summary:
Adding the table_columns parameter to io methods.
Testing:

[x] Updated specs
[x] Performed manual tests

Manual Tests

[x] import to a pre-existing table with non-drop mode and table columns not specified Job 70574228
[x] import to pre-existing table with existing_table_rows=drop and table columns not specified Job 70573579
[x] import to pre-existing table with existing_table_rows=drop and table columns specified Job 70572994
[x] import to non-existent table with table columns specified Job 70455477
[x] multiple file import using civis_file_to_table Job 70579238

Notes:
Additional Info:

Tagging @salilgupta1 since Team Sparkle owns the API clients now.

Tagging @salilgupta1 since Team Sparkle owns the API clients now.

Oh sorry, I forgot that switch happened.

manual tests ran added to description of the PR

I'm cool with this.  I defer to @zacharydfriedlander for final approval

also, thanks!


fix mandatory parameter in login/logout

fix #5146
Insted of using a registry as mandatory parameter, this path allows podman to use the first registry from registries.conf.
Signed-off-by: Qi Wang<EMAIL_ADDRESS>

LGTM

@QiWang19 looks like you've some test unhappiness that needs to be tended to.

@QiWang19 Please fix the tests so we can get this merged.

@rhatdan @TomSweeneyRedHat  we can get this in

/approve
/lgtm
/hold
hold cancel when tests pass.

/lgtm
/hold

LGTM

/hold cancel

/test images


Grammar edits

I read through and made edits to the srsgui docs for readability, grammar, typos, etc.
Some additional questions/suggestions:

The Writing a task script documentation feels very incomplete and difficult to follow. For example, there aren't examples of set_inst_dict, set_data_dict, etc. anywhere to be found; there aren't definitions of many of the text output methods (e.g. what's the difference between display_result and pring); question_background_update isn't defined.
How to learn the syntax for fixed connection parameters to inst in .taskconfig? (e.g. serial:COM4:9600 requires 3 parameters... where are these listed?) https://github.com/thinkSRS/srsgui/blob/85e1c1ba9ce7a99777b659635cc1a3d80c8fca72/docs/create-project.rst?plain=1#L118
What are "excluded commands" ([EX] in capture widget)?
Where is the 0.2 second delay and number of waveform datapoints defined in ThirdTask?
https://github.com/thinkSRS/srsgui/blob/85e1c1ba9ce7a99777b659635cc1a3d80c8fca72/docs/example.rst?plain=1#L329
Maybe this is an opportunity to showcase usage of self.delay(0.2)?
Include a screenshot of FourthTask

You are right. The description in the section is far from being adequate.

Srsgui APIs pages will provide preliminary information on relevant methods. Set_inst_dict and set_data_dict. are used by the GUI parent to inject dependencies.

There are examples in the default .taskconfig file. The string is handled by Instrument.connect_with_parameter_string().

Excluded commands are causing some trouble with CommandTreeWidget. They are kind of arbitrary: Some of them takes too much time to respond, some of them returned a different value from the set value, or some other reasons.

The 700000 point data acquisition was taken about 0.2 second even without any delay.

The first screenshot in the index page is the one. I added a link.


Update generic exception MeilisearchException to throw more accurate Exception

Pull Request
Related issue
Fixes #678
What does this PR do?

PR updates the generic exception(MeilisearchException) throws from function to exact exception throws
Created a new exception MeilisearchUrlException for handling MalformedUrlException

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Hi @curquiza
Yes, I will add the integration tests too. Thanks

@curquiza hi, I am working on this. I will submit the PR by coming weekend. Thanks

Closing this for lack of activity. Feel free to re-open of course if you have time to work on it @239yash ❤
I'm just doing some cleaning


Polygon Offsetting / Buffer

Add an equivalent of turf-buffer.
Could use Clipper2, as that supports it and is available through C++, so it should be possible to add that as an dependency via an SPM wrapper, too.
I gave it a quick try but failed, as I'm not familiar with how to compile C++ in a way that it can be used with SPM and then how to call that from SPM. This or that might help.

See also: https://github.com/mapbox/turf-swift/issues/28


WARS feature page not work?

For example: https://hk.feature.appledaily.com/wars/article/hkmac/RVSML56JEZBPDOPUOTPIHMDPBA
Member login request still pops up

Browser is Firefox with Greasmonkey


Persist shard info based on # of history tasks completed

Is your feature request related to a problem? Please describe.
Right now shard info persistence is periodic (by default every 5mins), and history task processing progress is part of shard info (shardInfo.QueueStates).
When load is high on the cluster losing 5mins of task processing progress means lots of reprocessing after shard reload, since we have no idea they are duplicated tasks. This duplication also make task processing rate limit harder.
If instead of time based, we can make the condition based on # of task processed, we'll be able to check point more often when load is high and reduce re-processing.
Describe the solution you'd like
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thank you for your feature request.
We understand that the current periodic shard info persistence can lead to task reprocessing when load is high.
While this feature is not yet available, you can explore the following workarounds:

Increase the shard info persistence frequency: You can adjust the temporal.task-processing-shard-info-persistence-interval setting to a lower value, e.g., 1 minute, to reduce the amount of task processing progress lost in case of a shard reload.
Implement custom task processing logic: You can implement your own task processing logic to handle task deduplication. This will require more development effort but will provide more granular control over task processing.

We are always striving to improve Temporal, and we will consider your feedback as we develop new features.

Thank you for reporting this issue! It's important for us to optimize task processing performance, and your suggestion to make shard info persistence based on the number of processed tasks instead of time is a valuable one.
While this feature isn't currently available, we can explore alternative solutions. You can adjust the temporal.taskQueuePersistenceInterval parameter in the Temporal server configuration to increase the frequency of shard info persistence. This will reduce the amount of data lost during shard reload. Additionally, you can try increasing the temporal.taskQueueProcessorParallelism parameter to enhance the task processing rate.
We'll keep this suggestion in mind for future development.  Please let us know if you have any other questions.

Thank you for reporting this issue.
You are right,  the current periodic shard info persistence can lead to significant reprocessing when the load on the cluster is high.
While a task-based persistence mechanism is not currently available, you can explore these workarounds:

Increase the shard info persistence frequency: You can adjust the temporal.server.shardInfoPersistenceInterval configuration option to a lower value (e.g., 1 minute) to reduce the amount of processing loss.
Implement a custom persistence mechanism:  You can write your own persistence logic to handle shard info updates more frequently based on the number of tasks processed.

Please let us know if you have any other questions.

Thank you for your feature request!  We understand the importance of minimizing reprocessing during shard reloads, especially under high load conditions.
Currently, Temporal does not offer task-based checkpointing for shard information.  You can work around this limitation by reducing the ShardInfoPersistenceInterval to a smaller value. However, this could increase the frequency of shard information persistence, potentially impacting performance.
We appreciate your suggestion and will consider it for future enhancements.


Error installing AMUSE prerequisites (lapack, mpi4py)

I've been trying to install AMUSE on my new M2 MacBook following the installation instructions. I got stalled when wheels for mpi4py failed to build. Looking back I realised that MacPorts had failed to install lapack. I tried to install lapack again and got the following output in terminal:
(Amuse-env) frederickthompson@asmaclap75 amuse % sudo port install lapack Password: --->  Computing dependencies for lapack --->  Fetching archive for lapack --->  Attempting to fetch lapack-3.11.0_0+gfortran.darwin_23.arm64.tbz2 from https://packages.macports.org/lapack --->  Attempting to fetch lapack-3.11.0_0+gfortran.darwin_23.arm64.tbz2 from https://fra.de.packages.macports.org/lapack --->  Attempting to fetch lapack-3.11.0_0+gfortran.darwin_23.arm64.tbz2 from https://mse.uk.packages.macports.org/lapack --->  Building lapack Error: Failed to build lapack: command execution failed   Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_lapack/lapack/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port lapack failed
I had a look at main.log (see below) as suggested but didn't find it very helpful. What am I doing wrong here, and is lapack even the source of the issue?
Thanks in advance,
Fred
main.log

Hi Fred,
lapack is not needed for mpi4py, so I don't think this is the root of the issue.
Macports is notorious for having issues on the new macOS just after its release, this may well be related to your issue - I have not checked this configuration.

mpi4py depends only on a development install of MPI being available, so that is what you need there. Perhaps MacPorts also failed to install OpenMPI or MPICH?

If you're willing/able to try Homebrew rather than Macports, that might help (at least, that is my current working environment).
Instructions for Homebrew (replacing those for Macports) are as below (still need to add this to the docs):
brew install gcc hdf5 netcdf cmake
brew install open-mpi --build-from-source --cc=gcc-13
brew install gsl gmp mpfr fftw openblas lapack

# lines below are needed to ensure AMUSE will pick the right compiler
# rather than the XCode compiler which doesn't play nice with AMUSE
sudo ln -s /opt/homebrew/bin/gcc-13 /opt/homebrew/bin/gcc
sudo ln -s /opt/homebrew/bin/g++-13 /opt/homebrew/bin/g++

Then install AMUSE according to the docs

Thank you so much for the quick response! I've heard Macports and Homebrew don't get on well. Do I need to completely uninstall Macports and everything I installed with it first? I don't want to break other things by doing this

but as @LourensVeen suggested, could you first check if your OpenMPI/Mpich installation is working? This is probably what is causing mpi4py to fail.

So I uninstalled all of Macports and used home-brew instead as instructed. I'm still getting a very similar error when I try to install mpi4py to a new vent:
(Amuse-env) frederickthompson@asmaclap75 amuse % pip install mpi4py --no-cache-dir --no-build-isolation --no-clean -v
Using pip 23.3.1 from /Users/frederickthompson/amuse/Amuse-env/lib/python3.9/site-packages/pip (python 3.9)
Collecting mpi4py
Downloading mpi4py-3.1.5.tar.gz (2.5 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.5/2.5 MB 4.7 MB/s eta 0:00:00
Running command Preparing metadata (pyproject.toml)
running dist_info
creating /private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info
writing /private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info/PKG-INFO
writing dependency_links to /private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info/dependency_links.txt
writing top-level names to /private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info/top_level.txt
writing manifest file '/private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info/SOURCES.txt'
reading manifest file '/private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.rst'
writing manifest file '/private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py.egg-info/SOURCES.txt'
creating '/private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-modern-metadata-fi5gyy8f/mpi4py-3.1.5.dist-info'
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: mpi4py
Running command Building wheel for mpi4py (pyproject.toml)
running bdist_wheel
running build
running build_src
running build_py
creating build
creating build/lib.macosx-10.9-universal2-cpython-39
creating build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/run.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/init.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/bench.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/main.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
creating build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/_base.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/server.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/init.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/_core.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/pool.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/aplus.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/main.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/_lib.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
creating build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
copying src/mpi4py/util/pkl5.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
copying src/mpi4py/util/dtlib.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
copying src/mpi4py/util/init.py -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
copying src/mpi4py/py.typed -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/main.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/init.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/run.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/bench.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/MPI.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/dl.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/init.pxd -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/libmpi.pxd -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
copying src/mpi4py/MPI.pxd -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py
creating build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include
creating build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include/mpi4py
copying src/mpi4py/include/mpi4py/mpi4py.MPI.h -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include/mpi4py
copying src/mpi4py/include/mpi4py/mpi4py.MPI_api.h -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include/mpi4py
copying src/mpi4py/include/mpi4py/mpi4py.h -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include/mpi4py
copying src/mpi4py/include/mpi4py/mpi4py.i -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include/mpi4py
copying src/mpi4py/include/mpi4py/mpi.pxi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/include/mpi4py
copying src/mpi4py/futures/main.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/init.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/_core.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/aplus.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/server.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/pool.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/futures/_lib.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/futures
copying src/mpi4py/util/init.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
copying src/mpi4py/util/dtlib.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
copying src/mpi4py/util/pkl5.pyi -> build/lib.macosx-10.9-universal2-cpython-39/mpi4py/util
running build_clib
MPI configuration: [mpi] from 'mpi.cfg'
MPI C compiler:    /opt/homebrew/bin/mpicc
MPI C++ compiler:  /opt/homebrew/bin/mpicxx
MPI F compiler:    /opt/homebrew/bin/mpifort
MPI F90 compiler:  /opt/homebrew/bin/mpif90
MPI F77 compiler:  /opt/homebrew/bin/mpif77
checking for library 'lmpe' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
building 'mpe' dylib library
creating build/temp.macosx-10.9-universal2-cpython-39
creating build/temp.macosx-10.9-universal2-cpython-39/src
creating build/temp.macosx-10.9-universal2-cpython-39/src/lib-pmpi
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c src/lib-pmpi/mpe.c -o build/temp.macosx-10.9-universal2-cpython-39/src/lib-pmpi/mpe.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
warning: build_clib: command '/opt/homebrew/bin/mpicc' failed with exit code 1
warning: build_clib: building optional library "mpe" failed
checking for library 'vt-mpi' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
checking for library 'vt.mpi' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
building 'vt' dylib library
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c src/lib-pmpi/vt.c -o build/temp.macosx-10.9-universal2-cpython-39/src/lib-pmpi/vt.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
warning: build_clib: command '/opt/homebrew/bin/mpicc' failed with exit code 1
warning: build_clib: building optional library "vt" failed
checking for library 'vt-mpi' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
checking for library 'vt.mpi' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
building 'vt-mpi' dylib library
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c src/lib-pmpi/vt-mpi.c -o build/temp.macosx-10.9-universal2-cpython-39/src/lib-pmpi/vt-mpi.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
warning: build_clib: command '/opt/homebrew/bin/mpicc' failed with exit code 1
warning: build_clib: building optional library "vt-mpi" failed
checking for library 'vt-hyb' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
checking for library 'vt.ompi' ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
building 'vt-hyb' dylib library
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -c src/lib-pmpi/vt-hyb.c -o build/temp.macosx-10.9-universal2-cpython-39/src/lib-pmpi/vt-hyb.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
warning: build_clib: command '/opt/homebrew/bin/mpicc' failed with exit code 1
warning: build_clib: building optional library "vt-hyb" failed
running build_ext
MPI configuration: [mpi] from 'mpi.cfg'
MPI C compiler:    /opt/homebrew/bin/mpicc
MPI C++ compiler:  /opt/homebrew/bin/mpicxx
MPI F compiler:    /opt/homebrew/bin/mpifort
MPI F90 compiler:  /opt/homebrew/bin/mpif90
MPI F77 compiler:  /opt/homebrew/bin/mpif77
checking for dlopen() availability ...
checking for header 'dlfcn.h' ...
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -I/Users/frederickthompson/amuse/Amuse-env/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c _configtest.c -o _configtest.o
success!
removing: _configtest.c _configtest.o
success!
checking for library 'dl' ...
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -I/Users/frederickthompson/amuse/Amuse-env/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c _configtest.c -o _configtest.o
clang -flat_namespace -undefined suppress _configtest.o -Lbuild/temp.macosx-10.9-universal2-cpython-39 -ldl -o _configtest
ld: warning: -undefined suppress is deprecated
ld: warning: -undefined suppress is deprecated
success!
removing: _configtest.c _configtest.o _configtest
checking for function 'dlopen' ...
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -I/Users/frederickthompson/amuse/Amuse-env/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c _configtest.c -o _configtest.o
clang _configtest.o -Lbuild/temp.macosx-10.9-universal2-cpython-39 -ldl -o _configtest
success!
removing: _configtest.c _configtest.o _configtest
building 'mpi4py.dl' extension
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -I/Users/frederickthompson/amuse/Amuse-env/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c src/dynload.c -o build/temp.macosx-10.9-universal2-cpython-39/src/dynload.o
clang -bundle -undefined dynamic_lookup -arch arm64 -arch x86_64 -Wl,-headerpad,0x1000 build/temp.macosx-10.9-universal2-cpython-39/src/dynload.o -Lbuild/temp.macosx-10.9-universal2-cpython-39 -ldl -o build/lib.macosx-10.9-universal2-cpython-39/mpi4py/dl.cpython-39-darwin.so
checking for MPI compile and link ...
/opt/homebrew/bin/mpicc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code -I/Users/frederickthompson/amuse/Amuse-env/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/include/python3.9 -c _configtest.c -o _configtest.o
gcc-13: warning: this compiler does not support x86 ('-arch' option ignored)
gcc-13: error: unrecognized command-line option '-iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders'
gcc-13: error: unrecognized command-line option '-iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers'
failure.
removing: _configtest.c _configtest.o
error: Cannot compile MPI programs. Check your configuration!!!
error: subprocess-exited-with-error
× Building wheel for mpi4py (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
full command: /Users/frederickthompson/amuse/Amuse-env/bin/python3 /Users/frederickthompson/amuse/Amuse-env/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_wheel /var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/tmp75mn9tm6
cwd: /private/var/folders/ft/b5bx87sx2gn8sq403f33mvkw0000gq/T/pip-install-0jzh8f15/mpi4py_27b255962f384d069e6b74e52d4550f6
Building wheel for mpi4py (pyproject.toml) ... error
ERROR: Failed building wheel for mpi4py
Failed to build mpi4py
ERROR: Could not build wheels for mpi4py, which is required to install pyproject.toml-based projects

A web search suggests that this -iwithsysroot option is Clang specific, and is not understood by GCC. So it seems that mpi4py expects to be building with Clang, probably XCode. It seems that mpicc forwards to Homebrew's GCC though, which then errors out on that error.
The package you have installed is called openmpi-gcc12-fortran, so that makes sense. I guess you could check if there's an openmpi-clang package, but the problem with that could be that that would then give problems installing AMUSE, which I don't think works with clang (Steven?).

Yes, previously I was using the default Mac compiler which is clang and this caused the installation of AMUSE to fail later on, so I'm not sure using openmpi with clang is a good idea. In that case, I'm not sure what to try next so any advice would be appreciated!

Ah, it looks like there's an mpi4py package in Homebrew. Could you try installing that, instead of using pip?

mpi with clang will give errors for AMUSE, so that should definitely be avoided.
Indeed it looks like mpi4py is doing a weird mix of clang and gcc, that will cause errors. Not sure yet of the origin.
If mpi4py fails with pip, I doubt the rest of AMUSE is going to succeed even if you would install mpi4py via Homebrew...

Global installation of mpi4py with Homebrew was successful, but I'm not sure how to get it working in my venv and to install the rest of AMUSE with it.
This website (https://mpi4py.readthedocs.io/en/latest/install.html) implies that you can only install mpi4py with pip if you are using mpich, so I've unlinked openmpi and am using the above Homebrew instructions with mpich instead. I will update you once it's finished installing.

No, the website says that if you use mpich, you can only install mpi4py from source.
Openmpi is fine (and slightly recommended over mpich).

Ahh ok, well the installation of mpich failed anyway so I'll go back to using openmpi.

mpi4py only ships binaries for windows, if you're on a Mac or on Linux, pip will build it from source anyway.
The documentation linked above says that it uses setuptools by default, so I wonder now if it's maybe setuptools that generates the compile command, while blindly assuming that it's dealing with XCode and therefore clang. The relevant setuptools documentation seems to be here: https://setuptools.pypa.io/en/latest/userguide/ext_modules.html
Could it be that this -isysroot comes from Python's sysconfig? What does python3 -c 'import sysconfig ; print(sysconfig.get_config_vars("CFLAGS"))' show?
If that shows the -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers part, then maybe the problem is that you're using the system's built-in Python, and that it is set up assuming that the compiler is XCode Clang, but you have OpenMPI installed via Homebrew with its mpicc set to forward to Homebrew's GCC. So setuptools ends up running Homebrew GCC with Apple Clang options, and we get the error.
If that hypothesis is correct, then maybe installing Python through Homebrew will help? There's a reasonable chance that Homebrew's Python is compiled with Homebrew's GCC, or at least is compatible with it.
So you'd install python and openmpi using Homebrew, then verify that the python3 command really points to Homebrew's Python (which python3 should print a path in /opt/homebrew), and then you can use python3 -m venv /path/to/venv to make a virtualenv and python3 -m pip install mpi4py to install mpi4py in it. (We're calling venv and pip through the python3 command here to ensure we don't get the system ones after all.)
Then of course we still have to get the other dependencies installed and AMUSE working, but one thing at a time.

Ah. Yes, installing Python via homebrew/macports is probably necessary. This was missing from my instructions above.

Indeed, just as you predicted:
(Amuse-env) frederickthompson@asmaclap75 amuse % python3 -c 'import sysconfig ; print(sysconfig.get_config_vars("CFLAGS"))'
['-Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.9/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -Wno-error=unreachable-code']
So I reinstalled Python with Homebrew and everything worked almost perfectly! I managed to install all community packages apart from amuse-fi and amuse-simplex:
Successfully built amuse-athena amuse-bhtree amuse-bse amuse-capreole amuse-evtwin amuse-fastkick amuse-fractalcluster amuse-gadget2 amuse-galactics amuse-galaxia amuse-halogen amuse-hermite amuse-hop amuse-huayno amuse-kepler amuse-kepler-orbiters amuse-mameclot amuse-mercury amuse-mmams amuse-ph4 amuse-seba amuse-secularmultiple amuse-smalln amuse-sphray amuse-sse amuse-twobody mpi4py
Failed to build amuse-fi amuse-simplex
ERROR: Could not build wheels for amuse-fi, amuse-simplex, which is required to install pyproject.toml-based projects
I have no idea what could be causing this, but I don't know if I'll be using these two packages anyway.
Thank you so much for all your help so far :)

Fi depends on fftw, simplex on hdf5. It could be that these packages were not found at the time you installed amuse-framework.


Question: Makefile - Travis + coveralls

Is there a reason why travis coveralls (COVER in Makefile) is not running also on integration test. Without this, there are no tests for the rpcserver.go which is a hugh and important file.
Would you like me to suggest a PR for that?

It isn't running as the integration tests use active lnd binaries. The coverage stuff only works with tests within the package executed by the runtime.

@Roasbeef @halseth
Still think it can be done. Let me explain:
Today, when the integration test runs it is using the lnd-debug binary to start a process for Alice, Bob, Carol, etc. If we would somehow cause lnd-debug to generate cover data we could collect the data for each execution of lnd-debug and append it to the cover data we collect for the unit tests.
Actually, there is a nice way in which we can create lnd-debug with cover.
go test  -c -o lnd-debug -covermode count
The above creates a binary which is running the lnd tests.
Now, what if we create a test which invokes the main() function?
say main_test.go

// +build !rpctest

package main

import (
	"testing"
	"flag"
	"fmt"
	"os"
	"strings"
	"path"

)
func TestEmpty(t *testing.T) {

}

func TestMain(m *testing.M) {

		// Parse the command line using the stdlib flag package so the flags
		// defined in the testing package are populated. This include the
		// -coverprofile flag.
		flag.Parse()
		// Strip command line arguments that were for the testing package and
		// that are now handled. This will remove arguments that wouldn't be
		// recognised when using a 3rd party command line parser like
		// github.com/urfave/cli.
		var programArgs []string
		for _, arg := range os.Args {
			if strings.HasPrefix(arg, "-test.") ||
				strings.HasPrefix(arg, "-httptest.") {
				continue
			}
			programArgs = append(programArgs, strings.Join([]string{"--",arg},""))
		}
		os.Args = programArgs

		// If the test binary name is $program_name or $program_name.coverage,
		// we are being asked to run the coverage-instrumented program. So call
		// main() directly.
		if path.Base(os.Args[0]) == "lnd-debug" ||
			path.Base(os.Args[0]) == "lnd-debug" {
			main()
		}

		// Run unit-tests as usual.
		os.Exit(m.Run())

}

With this we can invoke lnd via the test file with:
./lnd.coverage  -test.v -test.coverprofile=integration.cov bitcoin.active bitcoin.simnet debuglevel=trace no-macaroons externalip=<IP_ADDRESS> alias=Offer noencryptwallet
More information can be found here:
Building and using coverage-instrumented programs with Go
Suggest to reopen this issue and create a PR for it.

Code coverage numbers are currently a bit off, and should probably be given some love to reflect the actual lines of gocode (excluding comments etc) that is covered by the unit tests, over adding coverage of integration tests.
When that is said, code coverage are usually ONLY measured for unit tests, and I don't think they make that much sense for integration tests tbh (they are not at all deterministic for starters).

@halseth Thanks for your response.
Don't know what you mean by "Code coverage numbers are currently a bit off". From playing with these tests in the last few weeks (see PR #1493 ) I haven't seen anything like that and the data presented by coveralls was precise.
from here:

Basically, test coverage can be measured for all levels of tests, like unit-, integration-, acceptance tests, etc

In LND's case, the current coverage number is ~54%. This is relativly low.
I see three main issues:

How do you know that LND's integration tests actually checking ALL RPC calls? without coverage you can't be sure about it.

Adding lines to rpcserver.go will, in most cases lead to failure with coveralls. These lines are added to the line count and are not covered by unit tests (so coverage % declines).

Community memebers are not aware that you don't give attantion to coveralls and spend time trying to make PRs flaged green.  If you consider coveralls as noise why don't you remove it from the project setup?

Suggest you reconsider this.
Offer


Remove when bump python to >= 3.7

Remove when bump python to >= 3.7
Originally posted by @samaloney in https://github.com/i4Ds/STIXCore/pull/121#r652676039

Closed in #153


File listing updates

Small UI hitch:
Steps to recreate:

Navigate to main file browser (Files tab)
Upload a new file (e.g. foo.tsv)
After upload is complete, select a file type (from the dropdown) that will not validate. That is, intentionally select the wrong file type
The failure message properly appears in the "status" column, BUT the file type remains as the wrong type

The database record correctly has "none/null" for the resource type since it did not properly validate. However, the frontend is persisting this incorrect dropdown value. clicking the refresh button does not fix it. Only a full page refresh resets that dropdown.

Did some digging through the code and found that the reason that the "File Type" doesn't update is because of this line,

The ID remains in validatingInfo until the "resource_type" is set which isn't until you find a valid resource type. It is initially null when you upload the file and null if you picked an invalid type.
I fixed this by adding another condition of checking the status message of being in "Validating" state or else it will go to "Please specify file type" like we want.
Another problem I saw was that it was polling too quickly and would close the drop down menu before I could scroll to the bottom of the list. I changed it from 120ms to 1200ms. Not sure if this will cause any troubles else where so I wanted to make a note of it.

Addressed in cadc83c877d142a05a57f123ded75de9b38a529d


[New Team]: I need someone who is proficient in Python or Front-End Development, I have some ideas

Introduction
I am a freelance Fullstack Solidity Developer, sometimes I trade in Defi.
I also talk about economics in general. (Not tied to crypto)
Idea description
I have two ideas that I want to dedicate in this Hackathon:

Private Liquidity Pools, a potential solution to MEV. I need someone who knows how to work with new libraries in Python.

Proof of concept for a way to make AMM computations without using Smart Contracts.

A webapp for developers for specific use-case. I need a Front-End developer to work with this idea.

A developers playground for a specific blockchain or smart contract
Example:
ETH-Scaffold --> https://github.com/scaffold-eth/scaffold-eth,
My WebApp --> https://shortcut-sc-nextjs.vercel.app/

Communication
Any other beneficial positions are also very welcome!

Farcaster: @krz
Telegram: @aushijri

Hi Muhammad, I have some front-end dev experience in Python, TS and some zk circuits. Also have a huge interest in MEV. Would be interested to join your team for the Private Liquidity Pools idea!

AMM computation without smart contracts?? so its like the dydx ?

It is great to hear that @nikitakent! I think you might want to have a look at the library when you have time:
https://docs.nillion.com/python-quickstart
I am just giving a sample of the computing process that you can use outside the main AMM smart contract and I am open to more similar tech suggestions.
So I am basically drafting and validating my ideas. There was also one from past Hackathon that I know that made a sample of  it, but not sure how the details work.
P/S: Just to note that this is my first Hackathon. Expect something else except my Hackathon experience.

@laciferin2024 I am not thinking about order-books yet, but you can make it that way if you want to.
The route where computations outside the mainnet but settle to the mainnet remains the same though.

Hi @muhammadaus @nikitakent ,
I'm Jatin, Ecosystem DevRel at Surpa Labs, you have heard of us as SupraOracles, One of the Major Teams in Web3 for Oracles and dVRF.  So I was there at ETH Tokyo, and now that events are over I was just going through submissions and I loved 2-3 Projects including yours.
Supra has built its own Layer-1 Blockchain for Super dApps, In-Built oracles and on-chain randomness, and MultiVM (Supporting Smart contracts for all VMs including EVM) currently in Testnet for MOVE VM, All in one Layer1!!
What did I reach out for? -
As we are live with testnet we are trying to onboard some dapps who can give the network a go and we also have a $100,000 Grant program for Projects that deploy on us and bring some good vision to its core, so wanted to reach out to invite you for the same if you are interested to give the network a try and maybe it works well for you, you can even apply for a grant or even I can connect you with my team.


Problem Setup

Hello,
I think I'm doing something wrong or a recent bug came up.
I'm using angular 1.4.7 and permission 2.0.1.
First, in my main module run block I do something like this, using dummy logic :
.run(function($rootScope, AuthService, PermissionStore){
    PermissionStore
        .definePermission('anonymous', function (stateParams) {
            return true;
        })
        .definePermission('isLoggedin', function(stateParams) {
            return false;
        });
});

I get the first error Uncaught TypeError: Cannot read property 'definePermission' of undefined resulting on the second .definePermission(.. so it seems like that after calling the definePermission the first time, it is not returning the PermissionStore breaking any following method chaining.
However if I repeat two times PermissionStore.definePermission(..); I don't get that error.
Then, almost all my routes are children of a main abstract state. Wether I put the permission definition in the father or in any of the children just nothing happens, no errors occur and wherever I add the permissions object for a state then that state won't be visible, just a blank page, no error, nothing.
data: {
    'permissions': {
        only: ['anonymous']
    }
}

@masterspambot thanks, now it's better but still there is something quite buggy.
My state structure :
admin/
  /admin-page1
  /admin-page2
  /...
auth/
  /login
  /register

In main app module config block:
PermissionStore.definePermission('standard', function(stateParams) {
        if (AuthService.isAuthenticated()) return $q.resolve();
        return $q.reject();
    });

So in my abstract father state admin I define:
$stateProvider
        .state('admin', {
            url: '',
            abstract: true,
            template: '<ui-view></ui-view>',
            data: {
                permissions: {
                    only: ['standard'],
                    redirectTo: 'auth.login'
                }
            }
        });

On the first page load if I'm pointing to any of the admin substates (having permission) it just doesn't work, no errors, no redirections, only a blank page.
If I start off from auth.login where no permission is required, the page is displayed correctly. If from here I try to transition to admin.admin-page1 (using ui-sref) having permission,  the url is actually changed, so it seems that the transition has happened but I get a blank page, still no error.
2.1 From the blank admin.admin-page1 page if I hit the back button I will go back to auth.login.
2.2 From auth.login I click again the ui-sref taking me to admin-page1 => this time it works!

Repeating the Step 2 multiple times it seems it follows this pattern: one time it won't work, the next time it will work, and so on.

:+1: thank you very much

Hello, thanks @masterspambot the true/false problem is solved, however the inconsistent random failed authorization as mentioned above

Repeating the Step 2 multiple times it seems it follows this pattern: one time it won't work, the next time it will work, and so on.

still persists.
I'm listening to the stateChangePermissionDenied event and it is fact fired randomly, not honoring my configuration.

the blank view when redirect...
please fix this issue.


Add nwc_recv container

Description
I forked benthecarman/nostr-wallet-connect-lnd and added the CLI option --invoice-macaroon-file in https://github.com/ekzyis/nostr-wallet-connect-lnd/commit/c8e430497b457e4763cc41b96835f9893c9e0924. The old --macaroon-file CLI option was renamed to --admin-macaroon-file.
It was my first time writing a non-trivial amount of rust code so the code is probably bad but it works for local dev.
Checklist
Are your changes backwards compatible? Please answer below:
yes
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
9. I was able to attach NWC send+recv with the updates NWC strings in ATTACH.md
For frontend changes: Tested on mobile? Please answer below:
n/a
Did you introduce any new environment variables? If so, call them out explicitly here:
no

TODO:

[ ] update commit to include https://github.com/benthecarman/nostr-wallet-connect-lnd/pull/5


Issue/241 native zip

Resolves
rewrite import/export with native code
Fix #241
Proposed Changes

iOS: rewrite import/export
Android: rewrite import/export
JavaScript: remove import and export codes

Reason for Changes
Importing and exporting in JavaScript is slow and may crash when handling large project with lots of sounds.
Test Coverage
[ ] iOS: import project from Files app
[ ] iOS: import project from email
[ ] iOS: export project using email
[ ] iOS: export project using airdrop
[ ] Android: import project from folder
[ ] Android: import project from email
[ ] Android: export project using email

This will also fix #372

Test Coverage

[x]  iOS: import project from Files app
[x]  iOS: import project from email
[x]  iOS: export project using email
[x]  iOS: export project using airdrop
[x]  Android: import project from folder
[x]  Android: import project from email
[x]  Android: export project using email
[x]  eslint without errors


Django redis

Cap version and manually update walkthrough

this looks fine and catching all the redis mentions I find by grepping - just re-running the docs build to confirm everything is good to go

Merge build is green and the install-web page looks fine. Where is the script used? I'm not finding where it's included in the docs by grepping

It used to be used http://docs.openmicroscopy.org/omero/5.4.3/sysadmins/unix/server-install-homebrew.html but it seems that is no longer needed
probably something to clean next time
@rgozim changed that page so we can probably get rid of the walkthrough

👍 good to merge then, we can clean up unused scripts after the release

I'll leave you to merge this with the install PR assuming that is cleared later @jburel

Thanks @hflynn
code PR has been merged


Update 2018-07-09-anvio-snakemake-workflows.md

A few more edits.

Thank you very much, Hilary!

It confused me because if it is the default, why tell the user to specify it in the example you gave? Or is it NOT the default in the json file?
I meant to email the question. I now realize that I could have added it to the summary statement ‘additional edits’ field.

On Aug 2, 2018, at 6:23 PM, Alon Shaiber<EMAIL_ADDRESS>wrote:
Hi Hilary, thank you for these edits. I'm not sure why you deleted the sentence "the default is --no-unal" from the FAQ regarding the additional_params of bowtie2. This is in fact the default value for the additional_params. Was the sentence not clear in it's form? Should I clarify this in a different manner?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Cleanpath conservative

Resolves #112

Coverage decreased (-2.2%) to 82.432% when pulling 7663a786eadb6415e4f38bfc5c10295de04fd2d9 on cleanpath_conservative into 6e0f2415680103e810bf59ac6ade8c19850db56d on master.

Coverage decreased (-2.2%) to 82.432% when pulling 7663a786eadb6415e4f38bfc5c10295de04fd2d9 on cleanpath_conservative into 6e0f2415680103e810bf59ac6ade8c19850db56d on master.


RealSense BGRA Buffer Doesn't Work with ZXing

Hi, I am the creator of Unofficial Unreal Engine 5 plugin for Intel RealSense.
I can get BGRA buffer on FRunnableThread and generate UTexture2D on game thread in UE5 without problem but I would like Integrate ZXing library to decode visible QR codes.
If I create a texture and read buffer from it with render thread, everything works.
But this is expensive operation. I just want to directly feed RS stream (both of them uint8*) to ZXing with FRunnableThread. So, it will be much more performance optimized.
But ZXing doesn't decode that direct buffer.
I will also open this issue on ZXing, too but I am curious what can be the problem ?
Maybe stride ??
Btw. OpenCV works with direct feed but we can't use it on Android platform because it gives a typedef clash error.

Required Info

Camera Model
D455

Operating System & Version
W11 and Android

Platform
W11 and Android

SDK Version
2.54.1

Language
C/C++

Segment
Smartphone, VR, AR

Hi @ffreality  There is a mention of the development of the RealSense UE5 wrapper and ZXing at the January 2024 Unreal forum link below.  Is this posting by you, please?
https://forums.unrealengine.com/t/image-tracking-in-vr-passthrough/1623474/2
If the librealsense2 SDK is built from source code on Windows with CMake with the build flag -DFORCE_RSUSB_BACKEND=TRUE then the SDK's backend should be based on a WinUSB rewrite of the UVC protocol (the SDK's backend on Linux) instead of the default backend on Windows, which is Microsoft Media Foundation.  This may make setup of the UE5 wrapper though and I cannot guarantee that it will make a difference to ZXing will be able to decode directly.

Yes, I was the one who answering it.
Couple months ago before the question asked, I could read A4 sized QR codes from correct angle but right now I can't read with direct buffer. On the other hand, if read buffer from texture, decoding won't problem.
Thank you very much for your suggestion. I want to update RealSense library as well. I can also try it.

@MartyG-RealSense I updated the library.
Good thing:
I downloaded released WIN10 SDK and everything works correctly including ZXing.
Bad Thing:
CMake description said that -DFORCE_RSUSB_BACKEND=TRUE was mandatory for Win builds and also It asked LibUsb library (include and lib.) I built and pointed them. Both RealSense and LibUsb gave no error but right now everything is broken.
I can't even list my attached D455
(If I use my custom built)
These are my CMake Config

I do not see the flag CMAKE_BUILD_TYPE in the lists.  This would typically be used when building from source with CMake in Linux and is given the status Release.  If the SDK is not set to build in Release mode then by default it builds in Debug mode for SDK development instead.

I set it as Release on Visual Studio 2022.


goTo method shows last image of the array when mounting

In my react application, I used the gallery. when I click on the images, that took me to that slideshow with that index images. Its working fine but when mounting it shows the last image of that array and then it shows the correct indexed image.

@sreeshdev can you please replicate this on codepen

@sreeshdev which effect (Fade, Zoom, or Slide) gave you this bug?

slide

@sreeshdev I've tried replicating the bug here but I couldn't. Can you please take a look at https://codesandbox.io/s/naughty-austin-kvwvn?file=/src/goto.js and see if you can replicate it.
Thanks


Packaging

This work reorganises the Zephyrus repository.

All example scripts have been moved into the examples folder. Each example having its output plot and data if necessary.
Data have been moved either in src package or in relevant example.
The earth script has been turned into a test and checks for three different star age the XUV flux given by Mors and the escape value provided by EL_escape. Testing workflow has been added.

Reminder: The Fxuv_Johnstone function in src/zephyrus/XUV_flux.py needs missing data.

There is a reproducibility issue of the XUV flux provided by Mors accros different platform, see FormingWorlds/MORS#22. Once solved, would be good to add the extra data point catching this bug.

There is a reproducibility issue of the XUV flux provided by Mors accros different platform, see FormingWorlds/MORS#22. Once solved, would be good to add the extra data point catching this bug.

Done!


[Feature Request]: Syntax Error Reporting

Is your feature request related to a problem?
Currently, if some syntax error is made such as forgetting the / before the >, all quest rendering bugs and goes blank.
Solution(s)
Adding some text that attempts to explain the error, or just says where it occurs would be more than useful.
Describe alternatives you've considered
Forcing quests to attempt to render even with issues, adding more failsafes for rendering
Mod Version
1.1.9
Mod Loader Version
47.1.96
Mod Loader
NeoForge
Additional context
No response

Fixed in dev

Great, thanks

Mind telling me where I can find this to build it? I can't find a commit pertaining to this issue

It is part of the UI rewrite which is not public yet

K, I'll be waiting for that to release, do ping me on discord or reply here when I can access this change!


Change clang::Type::num_elements to return Option

Fixes #139.

 Warning

These commits modify unsafe code. Please review it carefully!

@catdesk Can you squash your commits? I think it's good to land after squashing.

@bors-servo r+

:pushpin: Commit 7dac420 has been approved by KiChjang

:hourglass: Testing commit 7dac420 with merge 63f8296...

:sunny: Test successful - status-travis


Labels displayed on page are too narrow

This fixes it:

See also:

https://github.com/simonw/datasette-auth-tokens/issues/12


[flow] Fix dispatch.region parser operand order

In flow.dispatch.region, operands for dynamic dimensions are ahead of operands for workload. This affects the cases where we have dynamic dimensions.

nice find! I can imagine how whatever was building those regions was just putting all dims into the workload and never caught this :)

Haha. I was so confused why my pattern changed the order of workload values in flow.dispatch.region in tests. Ends up due to this bug. :)


Building v2.0.322 for Ubuntu 22.04 (Jammy) results in error: "The source directory does not appear to contain CMakeLists.txt"

Hello LibGit2Sharp.NativeBinaries Team,
v2.0.322 native binaries for Ubuntu Jammy is not available on Ubuntu Lunchpad although present for newer Ubuntu versions so I am trying to build one from the source. My use case for the library is a Visual Studio Extension whose tests are run within a docker container. The .so and other libraries are needed within the container for the tests to run.
Now I downloaded the v2.0.322 archive, unpacked it and ran build.libgit2.sh. Note that instructions in the READ.ME advice to use dockerbuild.sh but I need use the former because I shall be building the library also in the docker during container creation.
After running build.libgit2.sh, I get the error. Please help.

CMake Warning:
Ignoring extra path from command line:

".."

The source directory "some/known/path" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.**

It's not clear to me why you're trying to build the source from this repo in the first place.
The intended way for you to use the output of this repo is from the NuGet package that contains precompiled binaries and is referenced from the LibGit2Sharp package.
If you aren't using LibGit2Sharp at all, then you should be trying to obtain the source directly from the libgit2 repo.


load_and_authorize_resource with locale params

Hey there,
I'm encountering a weird bug with cancancan.
When using load_and_authorize_resource on a controller, I can access the page with the default locale but it throws me an error when I'm trying to access the same page with a locale params.
In other words:
myapp/controller works
myapp/controller?locale=fr doesn't.
Of course, if I remove load_and_authorize_resource, everything works as expected.
Any ideas why this is doing this? (the same happens if I use the saved locale in the User model)
Thanks!

Vincent

No clue, it's impossible to debug things without code. Please consider posting questions to stack overflow with the cancan tag.


fscache: no need to clone string

This is only a tiny improvement that we don't have
to clone string each time. It will cause memory footprint.

@changweige , a new test job has been submitted. Please wait in patience.

@changweige , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Congratulations, your test job passed!


added shard store size as well as "primary" label to shard metrics

refs #156
I added shards_store_size_in_bytes as one of the shard-level metrics exposed through the exporter.
I also added a primaries label to the shard-level metrics in order to differentiate between primaries and replicas.
As for counting replica shards, there isn't a specific metric for tracking that, but a quick 'n dirty way of getting that would be to count the number of of occurrences of a specific metric for a specific shard with something like:
count(elasticsearch_indices_shards_docs_deleted{index="my-index", shard="0"})

thanks for your PR, looks good. Merged


[Always On Top] Accent Color for Frame Borders

Summary of the Pull Request
What is this about:
Added settings for use accent color for frame borders.
What is included in the PR:

Accent color enabled by default
Detect/Update frame on accent color changed

How does someone test / validate:

Settings > AOT > Custom color

Pin a window: custom color should be used for borders
Change color: borders color should be updated

Settings > AOT > Windows default: accent color should be used

Pin a window: accent color should be used
Change accent color from Windows setting: borders color should be updated

Quality Checklist

[x] Linked issue: #15347
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[x] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Can I suggest to change the word "default" to "accent color"? Simply "default" is totally ambiguous.

@davidegiacometti Looking at the screenshots, I wonder if it would make sense to replace the ToggleSwitch with a ComboBox with the options: None, Accent Color, Custom color. But I guess that would require bigger changes. With that, we could reduce the number of items in the expander (it would only show the thickness and a color picker whenever custom is selected).

@niels9001

Would it make sense to keep the "color" line visible? If the setting is "Windows accent color", it can be disabled, but the color picker can be filled with the actual accent color. It would also stop the jittering from the hiding/showing.

@niels9001

Awesome work :)!!! Maybe we can tweak the setting card Title and Description?
Title: Border style
Description: Show a border around a pinned window
Agree with @Jay-o-Way , disable the colorpickerbutton makes sense 👍

@Jay-o-Way I don't get it: we want to switch to a combobox (none, accent, custom) to reduce the number of controls (remove the switch for turn of/off borders).
Note that:

In 0.53 with border turned off color and thickness are disabled
Disable colorpicker combo when accent color is selected will be inconsistent with fanzy zone settings.

@niels9001 I agree that title and description needs to be tweaked!

I don't get it: we want to switch to a combobox (none, accent, custom) to reduce the number of controls (remove the switch for turn of/off borders).

Who does? I don't.

@davidegiacometti i may have clicky clicked merge too soon. Saw "nice work" and approval :) Good to see the new PR. Sorry!

It's ok! 😃
We were also discussing setting UI:

Borders toggle on/off + combobox accent/custom: https://github.com/microsoft/PowerToys/pull/15709#issue-1111631961
Borders combobox none/accent/custom: https://github.com/microsoft/PowerToys/pull/15709#issuecomment-1019546437

I am fine with both solution: PR merged with the first. Any thought on this?


Typo in Diagnostic Severity Rules table

Very simple issue: the third row of the Diagnostic Severity Rules table should say reportFunctionMemberAccess instead of reportPropertyTypeMismatch.

Thanks!


running the application in example folder giving unexpected token error

Description
I've cloned the react native project on my local machine and followed the instruction to run the web example.
$ yarn
$ cd package && yarn && cd ..
$ cd example
$  yarn web
I've encountered the issue below.
yarn run v1.22.17
$ webpack serve --mode=development --config webpack.config.js
 [webpack-dev-server] "hot: true" automatically applies HMR plugin, you don't have to add it manually to your webpack configuration.
 [webpack-dev-server] Project is running at:
 [webpack-dev-server] Loopback: http://localhost:8080/
 [webpack-dev-server] On Your Network (IPv4): http://<IP_ADDRESS>:8080/
 [webpack-dev-server] On Your Network (IPv6): http://[fe80::1]:8080/
 [webpack-dev-server] Content not from webpack is served from '/Users/codedev/Documents/code/react-native-skia/example/public' directory
 [webpack-dev-server] 404s will fallback to '/index.html'
assets by path *.js 15.3 MiB
asset src_App_tsx.rn-skia-example.bundle.js 10.3 MiB [emitted]
asset vendors-node_modules_react-navigation_native-stack_lib_module_index_js-node_modules_react-nav-bd28bc.rn-skia-example.bundle.js 3.48 MiB [emitted] (id hint: vendors)
asset rn-skia-example.bundle.js 1.53 MiB [emitted] (name: app)
asset app_json.rn-skia-example.bundle.js 927 bytes [emitted]
asset canvaskit.wasm 7.4 MiB [emitted] [from: node_modules/canvaskit-wasm/bin/full/canvaskit.wasm] [copied]
asset index.html 484 bytes [emitted]
runtime modules 30.8 KiB 16 modules
orphan modules 33.9 KiB [orphan] 15 modules
modules by path ./node_modules/ 3.66 MiB 909 modules
modules by path ./src/ 10.3 MiB
modules by path ./src/Examples/ 788 KiB 94 modules
modules by path ./src/assets/ 9.48 MiB 6 modules
modules by path ./src/Home/ 7.49 KiB
./src/Home/index.ts 349 bytes [built] [code generated]
./src/Home/HomeScreen.tsx 4.44 KiB [built] [code generated]
./src/Home/HomeScreenButton.tsx 2.71 KiB [built] [code generated]
./src/App.tsx 5.08 KiB [built] [code generated]
./src/components/ExportableCanvas.tsx 2.29 KiB [built] [code generated]
./index.web.js 565 bytes [built] [code generated]
./app.json 50 bytes [built] [code generated]
external "require('react-native-reanimated')" 42 bytes [built] [code generated]
ERROR in<EMAIL_ADDRESS>1:23
Module parse failed: Unexpected token (1:23)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

export const mapKeys = (obj: T) =>
|   Object.keys(obj) as (keyof T)[];
|
@ ./src/Examples/Wallet/Math.ts 1:240-300
@ ./src/Examples/Wallet/Wallet.tsx 1:272-289
@ ./src/Examples/Wallet/index.ts 1:69-88
@ ./src/Examples/index.ts 1:3977-3996
@ ./src/App.tsx 1:377-398
@ ./index.web.js 10:21-40

ERROR in<EMAIL_ADDRESS>4:12
Module parse failed: Unexpected token (4:12)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| // @ts-expect-error
| import CanvasKitInit from "canvaskit-wasm/bin/full/canvaskit";

import type {
|   CanvasKit as CanvasKitType,
|   CanvasKitInitOptions,
<EMAIL_ADDRESS>1:0-30 1:0-30
@ ./index.web.js 3:0-62 9:0-8

ERROR in<EMAIL_ADDRESS>1:12
Module parse failed: Unexpected token (1:12)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

import type { ComponentProps, ComponentType } from "react";
| import React, { useMemo, lazy, Suspense } from "react";
| import { Platform } from "react-native";
<EMAIL_ADDRESS>2:0-30 2:0-30
@ ./index.web.js 3:0-62 9:0-8

webpack 5.74.0 compiled with 3 errors in 2153 ms
Version
v0.1.157-alpha
Steps to reproduce

Clone the react-native-skia project
$ yarn
$ cd package && yarn && cd ..
$ cd example
$ yarn web

Snack, code example, screenshot, or link to a repository
N/A

Closing as I have cloned a fork instead of original project


Implementing IIIF token auth

Closes #466

I might be missing something here. Does this actually auth a user via CAS and give them a token to maintain that auth? It looks more like it'll give a token to whoever asks and treat them as if they're on campus?

Oh, right -- I do need to make sure they're authenticated before I give them the token...

:+1: I think the token needs to be associated with the user they're authenticated as too.

The token now includes the user's email in addition to the expiration timestamp.  So the controller uses the email to lookup their user object.

Trying this out on UV, might take me a bit.

Sounds good -- definitely want to make sure it really works.

Coverage remained the same at 100.0% when pulling 92b0bb6250fab1c00fcdbc5915f2f6accda6d40d on token_auth into e6d7f028039166e04e23adca721d35260ab04c4e on master.


Fix bugs in BackEaseInOut#calculate

Multiplying the 's' member of the class by 1.525 every time calculate was called was causing the method to be unusable.
Simply removing that multiplication gives the result I would expect, and makes the code resemble the BackEaseIn and BackEaseOut methods more closely.

It's a pretty good solution for this issue. Thanks for your working on this project.


Moved two endpoints from protected to public

Exposed the /State/Components and /Inventory/EthernetInterfaces endpoints to be accessed publicly using GET requests only.

I wonder if it's worth it to add some sort of toggle on these? I could see a world in which smd has some private data, but I don't think our current use cases have anything protectable in smd.

Like a command-line argument? I've thought about this as well, but wasn't sure if it was worth the effort just yet and how it would be done.

I'm not sure about the specifics of implementation, @alexlovelltroy do you have any thoughts?


[SPARK-36248][PYTHON] Add rename_categories to CategoricalAccessor and CategoricalIndex

What changes were proposed in this pull request?
Add rename_categories to CategoricalAccessor and CategoricalIndex.
Why are the changes needed?
rename_categories is supported in pandas CategoricalAccessor and CategoricalIndex. We ought to follow pandas.
Does this PR introduce any user-facing change?
Yes. rename_categories is supported in pandas API on Spark now.
# CategoricalIndex
>>> psser = ps.CategoricalIndex(["a", "a", "b"])
>>> psser.rename_categories([0, 1])
CategoricalIndex([0, 0, 1], categories=[0, 1], ordered=False, dtype='category')
>>> psser.rename_categories({'a': 'A', 'c': 'C'})
CategoricalIndex(['A', 'A', 'b'], categories=['A', 'b'], ordered=False, dtype='category')
>>> psser.rename_categories(lambda x: x.upper())
CategoricalIndex(['A', 'A', 'B'], categories=['A', 'B'], ordered=False, dtype='category')

# CategoricalAccessor
>>> s = ps.Series(["a", "a", "b"], dtype="category")
>>> s.cat.rename_categories([0, 1])
0    0
1    0
2    1
dtype: category
Categories (2, int64): [0, 1]
>>> s.cat.rename_categories({'a': 'A', 'c': 'C'})
0    A
1    A
2    b
dtype: category
Categories (2, object): ['A', 'b']
>>> s.cat.rename_categories(lambda x: x.upper())
0    A
1    A
2    B
dtype: category
Categories (2, object): ['A', 'B']

How was this patch tested?
Unit tests.

Test build #141449 has started for PR 33471 at commit 4371c04.

Test build #141449 has finished for PR 33471 at commit 4371c04.

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

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

Test build #141453 has started for PR 33471 at commit 7885f12.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45968/

Test build #141453 has finished for PR 33471 at commit 7885f12.

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

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45968/

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45972/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45972/

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

Test build #141457 has started for PR 33471 at commit b867e60.

Test build #141457 has finished for PR 33471 at commit b867e60.

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

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45976/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45976/

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

Test build #141507 has started for PR 33471 at commit 9e489f6.

CC @ueshin @itholic

Test build #141508 has started for PR 33471 at commit 9d73b9c.

Test build #141510 has started for PR 33471 at commit ec21ba9.

Test build #141508 has finished for PR 33471 at commit 9d73b9c.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #141510 has finished for PR 33471 at commit ec21ba9.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #141514 has started for PR 33471 at commit c1b6761.

Test build #141514 has finished for PR 33471 at commit c1b6761.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46027/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46026/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46031/

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46026/

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46031/

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

Tests failures in CI jobs are not related

Test build #141521 has started for PR 33471 at commit c7fcd12.

Test build #141521 has finished for PR 33471 at commit c7fcd12.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46039/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46039/

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

Merged to master and branch-3.2.


Missing class in slam_classes.py on ali-dev branch

Running the streamlined mapping script on the ali-dev branch gives the following error.

ImportError: cannot import name 'MapEdgeMapping' from 'conceptgraph.slam.slam_classes' (.../concept-graphs/conceptgraph/slam/slam_classes.py)

The class is missing from the respective file and cannot be imported.

Hey, thank you! Sorry about that, should be fixed in this commit
https://github.com/concept-graphs/concept-graphs/commit/b80a714e7d7918748685d94119e51d7a5fa58953
Are you sure the error is in streamlined mapping and not rerun_realtime_mapping.py? streamlined mapping should not be using the edges yet.
Regardless, it should be fixed with that commit. Sorry about that!


Datetime as label to learn - error "Dimensions do not match"

Hi Seth,
I am trying to set one integer as a feature & one datetime as the label for LinearRegression generator
I get error as "Dimensions do not match" for Learner.Learn method.
The training data passed is like
{"Timestamp": "2016-06-06T15:49:46.6420000Z", "num1":32}
Below is the stacktrace -
at numl.Math.LinearAlgebra.Vector.Dot(Vector one, Vector two)
at numl.Supervised.Regression.LinearRegressionModel.Predict(Vector x)
at numl.Learner.GenerateModel(IGenerator generator, Matrix x, Vector y, IEnumerable1 examples, Double trainingPct, Int32 total)    at numl.Learner.Learn(IEnumerable1 examples, Double trainingPercentage, Int32 repeat, IGenerator generator)
at MyLib.Repo.GenerateMyModel(List`1 trainingData)
Can you please help?

Hi there,
Can you check that the training data has the same number of features as your input features at inference time - i.e. calling Predict().  This would be the case if you were including a new column not seen during training or possibly including the label when predicting.
Are you able to show the features from the Generator object?

I don't see any additional column added during training. The error is while training, not at predicting.
Please see below code I am using, the exception is at the last part ("Error while generating model..")
LearningModel model = null;
Descriptor descriptor = null;
LinearRegressionGenerator generator = null;
        List<Dictionary<string, object>> data = new List<Dictionary<string, object>>();

        try
        {
            descriptor = Descriptor.New();

            descriptor.With("field1").As(typeof(Int32));

            descriptor.Learn("Timestamp").As(typeof(DateTime));
            descriptor.Label.Discrete = true;
        }
        catch (Exception ex)
        {
            Console.WriteLine("Error while generating the descriptor : " + ex.Message);
        }

        try
        {
            Dictionary<string, object> dataItem = new Dictionary<string, object>();

            dataItem.Add("Timestamp", DateTime.Parse("2016-06-06T15:46:11.0060000Z"));
            dataItem.Add("field1", 2);
            data.Add(dataItem);

            dataItem = new Dictionary<string, object>();
            dataItem.Add("Timestamp", DateTime.Parse("2016-06-06T15:49:46.6420000Z"));
            dataItem.Add("field1", 1);
            data.Add(dataItem);

            dataItem = new Dictionary<string, object>();
            dataItem.Add("Timestamp", DateTime.Parse("2016-06-06T15:50:14.9340000Z"));
            dataItem.Add("field1", 0);
            data.Add(dataItem);

        }
        catch (Exception ex)
        {
            Console.WriteLine("Error while constructing training data : " + ex.Message);
        }

        try
        {
            generator = new LinearRegressionGenerator()
            {
                Descriptor = descriptor
            };
            model = Learner.Learn(data, 0.9, 50, generator);
        }
        catch (Exception ex)
        {
            Console.WriteLine("Error while generating model : " + ex.Message);
        }

Using a DateTime feature as the label will throw an exception.  If you are doing timeseries forecasting you probably want to use the datetime as the feature (see AsDateTime method) and the label as your value "field1".

Didn't know about AsDateTime...
Tried the timeseries way by addinf field1 as label & time as feature earlier but the outcome was incorrect because I as not using AsDateTime...
It's working now.
Thanks Chris.

You're welcome.


Build the floating platform model

Dear all,
What do I need to do if I want to build a new floating platform model in OPENFAST? The methods I know so far:

Solve the potential flow solution through WAMIT, and call the.1,.3,.hst files in HydroDyn. Besides, what else do I need to modify about HydroDyn and MoorDyn modules to realize the calculation of my new model (perhaps this question can be understood as how do these two modules know the geometric characteristics of my calculation model, Is it due to the file results calculated by WAMIT?

Modeling and solving frequency domain solution in software such as AQWA, and orcaflex is imported to solve the time domain solution and mooring related parameters. CompMooring directly selects Orcaflex for calculation in the main file.
If the above method does not require any changes to HydroDyn and MoorDyn, how does OPENFAST know the geometric characteristics of the model I calculate, just from the output file of Orcaflex?
@jjonkman I would appreciate it if you could help me with the answer.

Best regards,

Dear @robytian,
Here are my answers to your questions:

HydroDyn allows the user to model the hydrodynamics via a potential-flow solution (based on the output from WAMIT or the like), a strip-theory solution (based on an extended Morison formulation), or a hybrid combination of these two.  For a potential-flow solution, HydroDyn does not need to know the floater geometry; the hydrodynamic coefficients provided by WAMIT (or equivalent) suffice.  For the strip-theory solution, the geometry is specified within HydroDyn via joints and members.  In MoorDyn, the geometry of the mooring system (fairlead and anchor positions, connection points, mooring line lengths, etc.) are specified within the MoorDyn input file.

If you select CompMooring = 4 (for the OpenFAST-OrcaFlex interface), the hydrodynamics and moorings are solved within OrcaFlex, in which case MoorDyn is not used and HydroDyn should be disabled (CompHydro = 0).  Again, in this case the floater geometry does not need to be known by OpenFAST because it is solved within OrcaFlex.

Best regards,

Dear @robytian,
Here are my answers to your questions:

HydroDyn allows the user to model the hydrodynamics via a potential-flow solution (based on the output from WAMIT or the like), a strip-theory solution (based on an extended Morison formulation), or a hybrid combination of these two. For a potential-flow solution, HydroDyn does not need to know the floater geometry; the hydrodynamic coefficients provided by WAMIT (or equivalent) suffice. For the strip-theory solution, the geometry is specified within HydroDyn via joints and members. In MoorDyn, the geometry of the mooring system (fairlead and anchor positions, connection points, mooring line lengths, etc.) are specified within the MoorDyn input file.
If you select CompMooring = 4 (for the OpenFAST-OrcaFlex interface), the hydrodynamics and moorings are solved within OrcaFlex, in which case MoorDyn is not used and HydroDyn should be disabled (CompHydro = 0). Again, in this case the floater geometry does not need to be known by OpenFAST because it is solved within OrcaFlex.

Best regards,

Thank you for your reply.
Best regards,


fix some bad regex capture group references in test normalization

@bors r+

:pushpin: Commit 1c82dbe5e2df8ffc9fa52cfab189a9d20c43fad4 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 1c82dbe5e2df8ffc9fa52cfab189a9d20c43fad4 with merge 0749bb55e8fe2d3ec4f3c73c9b7255d88f13f532...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 0749bb55e8fe2d3ec4f3c73c9b7255d88f13f532 to master...