translation is missing plural form 2 which is required by the locale "ro"

Steps to reproduce
When compiling:
==> timex
Compiling 57 files (.ex)
warning: String.strip/2 is deprecated, use String.trim/2 with a binary second argument
  lib/timezone/timezone_local.ex:82

warning: String.strip/2 is deprecated, use String.trim/2 with a binary second argument
  lib/timezone/timezone_local.ex:194

14:21:25.170 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:72: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:78: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:84: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:90: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:96: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:102: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:108: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:114: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:120: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:126: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:132: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.171 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:138: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.173 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:144: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.173 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/relative_time.po:150: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:24: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:30: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:36: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:42: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:48: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:54: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.176 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:60: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.177 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:66: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.177 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:72: translation is missing plural form 2 which is required by the locale "ro"

14:21:25.177 [error] /data/_build/test/lib/timex/priv/translations/ro/LC_MESSAGES/units.po:78: translation is missing plural form 2 which is required by the locale "ro"
Generated timex app

Elixir 1.5.2
Erlang/OTP 20.1

The problem appeared after the release of the new version (0.14.1) in lib gettext.

I'm looking into fixing this right now.


supportsRunInTerminalRequest

There is a new feature to run the debugger in the vscode integrated console in vscode 1.5

Hey, this is a great ideal to support the VSCode integrated terminal, which is of vital importance to debug programs with standard input. I think I need this feature badly.
But do we have any plans for this?


Pass request headers to receive_web_request

For some web services (like one I'm writing to receive Twilio text messages and will send a pull for) info in the headers is important in order to verify or understand the request.
This adds a fourth options headers={} to receive_web_request. For any custom agents people might have that aren't committed here, it does an arity check to not send headers if the method doesn't support them.
I also wonder if we should just pass the entire request object http://guides.rubyonrails.org/action_controller_overview.html#the-request-object instead of splitting it across method, format and headers arguments.

Good idea! Maybe you could pass the request object as a fifth argument for agents that need access to everything, but keep the simplicity for the other agents?

Good idea. Added the request object as a fifth argument. The thought for keeping the arity check was kind of in case anyone is using agents that haven't been merged upstream here or for future agents to be able to write receive_web_request in a simpler manner. But could go either way on that, happy to just have it always support 5 arguments.

Good idea!  We'll need to update the wiki too.

Ok, so I've rebased the branch off latest master. Everything look ok to merge now? After merging I can update the documentation on that wiki page.

I am still not a huge fan of the arity check as it introduces complexity that we probably never be able to remove afterwards. If we go with it couldn't the receive_web_request method definition of existing agents stay the same as before?

I don't feel strongly about the arity check either way. Thought it could be nice to preserve some agents with the simpler syntax. Happy to take it out and just update every receive_web_hook call to take 5 arguments if everyone agrees that's the way to go. @cantino thoughts on that?

I'd consider five arguments as way too many.  Given the fact that the request object should include everything including params, method, format and headers, I'd go with receive_web_request(request).

I think retaining compatibility by checking the arity is preferable here, because one with an in-house/personal agent wouldn't even know it got broken by the method signature change until it received the first request after upgrading and then found a failure in the application log afterwards.
As for @dsander's concern, we could probably add a check in Agent loader and show a banner to admins after login that urges them to update their agents if the check fails.  After a certain amount of time (grace period) it'd be fine to lift it and remove the arity check.

I'd probably do this:
if method(:receive_web_request).arity == 3
  handled_request = receive_web_request(params, method, format)
else
  handled_request = receive_web_request(request)
end

Maybe not worry about the banner for now, though?

I think retaining compatibility by checking the arity is preferable here, because one with an in-house/personal agent wouldn't even know it got broken by the method signature change until it received the first request after upgrading and then found a failure in the application log afterwards.

I would assume the in house agent had specs which would run and fail before the Huginn instance is updated :)

As for @dsander's concern, we could probably add a check in Agent loader and show a banner to admins after login that urges them to update their agents if the check fails. After a certain amount of time (grace period) it'd be fine to lift it and remove the arity check.

That would still break for users that update very infrequently. If we really want to maintain backwards compatibility we can never remove it.
Since we do not support external Agents yet I consider our Concern an internal API and thus not worry about breaking something external. If we go with it I would prefer @cantino approach without modifying the existing agents.

I would assume the in house agent had specs which would run and fail before the Huginn instance is updated :)

I'd really hope so, but even the fact that many users are running Huginn in development was beyond my expectation, and I wouldn't dare to assume much. ;D

That would still break for users that update very infrequently. If we really want to maintain backwards compatibility we can never remove it.

I mean after a grace period backward compatibility code should be removed and the arity check in Agent loader be turned into part of sanity check, refusing to boot on failure instead of relying on backward compatibility code and showing a banner.  I hopefully think it is not asking too much that infrequent updates sometimes fail and require admins to take action.
One problem we have is we do not really have a channel for announcing breaking changes to users/admins.  I first thought we could add a migration to perform the arity check for existing agents, but it turned out that it'd be unrealistic to load all agents in a migration process.  So, I thought it could be an option to take a grace period and show a prewarning, if not this time.

Ok. I've modified it to take either 1 argument (request) or 3 arguments (same signature as before) and left the existing agents using 3 arguments.
I wonder if for now we just keep this as a non-breaking change but that at some point in the future we can batch together a whole bunch of breaking changes at once and push them as a versioned release or something, once there is a method for announcing breaking changes and the like.

I agree, we should bundle some breaking stuff into a versioned update sometime soon.  (How does one version a Rails application?)
Is this ready to go?

Other than whether or not to leave that comment in, I believe this is ready to go

Closing/re-opening to trigger a travis re-build to hopefully clear up a transient bundler install failure

Looks good to me, I don't feel strongly about the comment.

Looks good to me!

Great, thanks!


recent_topics: Disable filters in Recent topics for logged out users.

In "click_handlers.js", disable function calls on clicking filter buttons
when the user is logged out.
In "recent_topics_ui.js/load_filters", assign "null" to filters in
local storage. This is to prevent the user from manually adding filters
to the local storage.
In "recent_topics_ui.js/show_selected_filters", disable the filter buttons
and change the cursor to "not-allowed" when the user is logged out.
Fixes: #21279
GIFs or screenshots:
https://user-images.githubusercontent.com/85362194/156302583-7e34cf14-24f4-4afb-b1f3-89ffa5a5e5e7.mov

The goal isn't primarily to make clicking them not work, it's to display them as disabled elements. It may make sense for @amanagr to just take this issue, since he has a lot of context for it.

Thanks, @NerdyLucifer, for your effort closing this, since this doesn't fix the complete issue.


Transmission Line Creation

Please be as descriptive as possible, including: what is expected, why is this feature needed, what is the objective, etc.
What is the feature being requested?
While adding component using the drag and drop feature in the future, we can click on any of the pads and a transluscent transmission line will appear, we can then long-press the shift key to get a straight line, otherwise, the TL will follow a meandering path to the pad on the other qubit. We can also press the left mouse button along the route to add anchor points along the route. After placing the TL, we can right click on it to change the feature like asymmetry and fillet.
What are use cases for this feature?
This will help reduce the lengthy process of coding the TLs. It will be an enhancement for the GUI and user friendly.

Thanks, that's a good request


[deps] upgrade ureq

Motivation
Upgrade ureq, remove restriction on dependabot upgrading ureq and the now unused rustls.
Have you read the [Contributing Guidelines on pull requests]
Y
Test Plan
CI
Related PRs

/ureq

:exclamation: Invalid command

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/land


KAFKA-9387: Use non JNI LZ4 Hashing for header checksums,

since they are just a few bytes and the Java Version outperforms the native version
see: https://lz4.github.io/lz4-java/1.3.0/xxhash-benchmark/
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks for the PR. Do these changes have any impact on kafka-producer-perf or kafka-consumer-perf?


Upgrade eventuo11y to 0.9

Future work to include:

Switching to MonadEvent instead of explicit backend passing
Making it easier to derive MonadWith for newtypes (ideally fixing deriving newtype, if not perhaps some TH)

Trying to merge main locally now.

Removed materialization after confirming that it wasn't winning anything because I kept having to go through materialization updates as I was trying to update the index state.


Implement a 16 x 16 monochromatic grid

Here's a 16 x 16 grid.
Use the primary mouse button to draw, and the secondary one to erase.
Gravação de tela de 2023-12-18 23-49-19.webm
Note that you can click and drag to either draw or erase.
No need to be clicking every single cell.

Could be optimized, though.
The app completely redraws the canvas instead of changing just the single modified cell.

It also crashes when dragging outside the drawing area:
Gravação de tela de 2023-12-19 11-09-59.webm

index out of bounds: the len is 16 but the index is 16

I fixed it:
Gravação de tela de 2023-12-19 11-24-35.webm

In light mode, it's a little bit hard to tell the boundary of the canvas.
Adding a border would be make it way better.

Fixed!
Old

New

I'll optimize it later if needed or if it's trivial enough, since it's not a deal-breaker now.


feat: add order to pack upg supported targets

Add order option to add the supported targets in the specified order for pack builder

I would like to propose an alternative solution. Instead of adding the 'order' property per-target, why not add an overall option that enforces the order of specification?
This would enable the library to throw a meaningful exception when the order is broken.
application::SupportedTargets::Create().InOrder().AddHex("hextarget").AddBin("bintarget");


[Proposal] Use mujoco bindings from deepmind instead of mujoco_py

Since mujoco_py is no longer maintained, and gym has also already updated its other mujoco envs to use deepmind's python bindings, gym-robotics needs to be updated as well.

Hello is there any update on this?  Due to the current dependency to mujoco_py, gym-robotics environments (e.g., FetchSlide-v1) cannot be used when a recent setup is used (mujoco 2.2+, gym 0.25.1, etc.). Looking forward to it, thanks!

Hi @wookayin, thanks for your interest. A PR will be made soon with new versions of the environments using the latest mujoco bindings and compatibility with gym API. If you want to follow the work the forked repo I'm working on is this one: https://github.com/rodrigodelazcano/Gym-Robotics/tree/mujoco-bindings.
Currently I'm performing some training benchmarks of the new environment versions against the old ones.

@wookayin @arjun-kg the latest environment versions have the new mujoco bindings. This PR has also the benchmarks #18


Restarting Homebridge removes it from the room in HomeKit

Anytime I restart homebridge, both my B-Hyve Hose Timer and irrigation System Accessory with zones are moved out of the assigned room and into the default room.

What version are you running?
I just did the IOS upgrade yesterday, restarted the plugin just now and saw what you described, I moved them back to the room I want them in and they are staying after both a child bridge restart and homebridge restart.
I'll keep looking

I was able to reproduce this again, not sure how but also see the same on another plugin so maybe tied to the IOS update.

Seems corrected in v1.2.22


Rendering too many categories

Hi @arun1595,
Thanks so much for taking the tech challenge! We like your approach and have checked it out (thanks for making the token an ENV hence not exposing it to the public :).
However, we found one issue: E.g. with python categories.py --render 99 we get over 8000 (!) categories but expect only ~417. Could you please check your insertion / retrieval logic there?
Also please double check our requirements for displayed data (e.g. BestOfferEnabled etc).
Thanks!

@leomelzer Thanks for reporting!
Let me have a look.

Also please double check our requirements for displayed data (e.g. BestOfferEnabled etc).
Will do.

@leomelzer I had a look at the issue.
The root category has a lft value of 1 and a rgt value of 834.
select *
from Categories
where CategoryID = 99;

CategoryID
CategoryName
CategoryParentID
CategoryLevel
BestOfferEnabled
lft
rgt

99
Everything Else
99
1
0
1
834

To fetch the category tree rooted at the category 'Everything Else', I just have to make a range query looking for categories with lft value which lies between 1 and 834.
select count(*) as total_nodes
from Categories
where lft between 1 and 834;

total_nodes

8644

So, it looks like something's wrong with the way I compute lft and rgt values. I'll have a deeper look and get back to you.

Hi @arun1595 - how's it going? Did you have time to have a look?

@leomelzer Hi! No luck yet. Will update when I diagnose and fix the issue.
Thanks!


FIX: returning correct DeleteMarkerVersionId when deleteObjects

Fixing ceph test:
ERROR: s3tests.functional.test_s3.test_versioning_multi_object_delete_with_marker_create
DeleteMarkerVersionId should be a versionId not a boolean.

Also check that multi-object delete has ‘isDeleteMarker’ in result in both cases deleting delete marker and new delete marker (according to AWS)

@ironman-machine try

Hello @nicolas2bert
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "fx/multideleteversioning"}
Please follow http://ci.ironmann.io/gh/scality/Integration/11782 for CI status.

@ironman-machine try

Hello @nicolas2bert
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "fx/multideleteversioning"}
Please follow http://ci.ironmann.io/gh/scality/Integration/11875 for CI status.


:construction_worker: make gitops secrets optional

Type of Change

[x] Bugfix
[ ] Enhancement / new feature
[ ] Refactoring
[ ] Documentation

Description

make gitops secret optional - docker or gitops is disabled

Checklist

[x] Add relevant labels (for example type of change or patch/minor/major)
[x] Make sure not to introduce some mistakes
[x] Update documentation
[x] Review the Contributing Guideline and sign CLA
[ ] Reference relevant issue(s) and close them after merging

I would close this pr until it is not possible to ignore the credentials in the action.


"Edit this cell" box not opening when double-clicking an empty cell

Context
In the table view, you can edit cells by double-clicking on them but when the cell is empty, it doesn't work.
Current Result

Expected result
The "Edit this cell" box should always appear on double-clicks.

Fixed thanks to https://github.com/CartoDB/cartodb/pull/11691.


Crosscompiling with PortAudio fails

I want to compile librespot-org from my Fedora 27 to my Raspberry Pi Model B Rev 2 with the PortAudio backend using this command:
docker run -v /tmp/librespot-build:/build:Z librespot-cross cargo build --release --target arm-unknown-linux-gnueabi --no-default-features --features portaudio-backend
But it fails with this error:
error: failed to run custom build command for `portaudio-sys v0.1.1`
process didn't exit successfully: `/build/release/build/portaudio-sys-ec384f39d055f1f8/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Cross compilation detected. Use PKG_CONFIG_ALLOW_CROSS=1 to override', /build/cache/registry/src/github.com-1ecc6299db9ec823/portaudio-sys-0.1.1/build.rs:8:19
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Full output: https://pastebin.com/Y3C5GQ3c
How can I set PKG_CONFIG_ALLOW_CROSS to 1?
Can anyone help me fix this?
(If I set --features to alsa-backend, it compiles and runs on the Raspberry Pi, although there is no sound just weird beeps. Full output: https://pastebin.com/ezi5B76e)

Run the docker command like this:
docker run -v /tmp/librespot-build:/build:Z librespot-cross PKG_CONFIG_ALLOW_CROSS=1 cargo build --release --target arm-unknown-linux-gnueabi --no-default-features --features portaudio-backend


AlamofireObjectMapper need compatible with ObjectMapper 2.2.0

ObjectMapper (= 2.1.0) required by Podfile.lock
ObjectMapper (~> 2.0) required by AlamofireObjectMapper (4.0.0)
ObjectMapper (= 2.2.0) required by Moya-ObjectMapper/Core (2.0.1)

ObjectMapper (~> 2.0) required by AlamofireObjectMapper (4.0.0)
If you run a pod update, cocoapods should fetch the latest version of ObjectMapper (v2.2.1). Cocoapods is locked on 2.1.0 as you can see from your Podfile.lock file. pod update should resolve that

Having this issue again, can we have another release to fix the version incompatibility? Thanks! 👍

I am also having the same issue with all suggested combinations for ObjectMapper and AlamofireObjectMapper.  Appreciate your help here. #

I am having same error:

My Cartfile

Term debug it's fine

Same error when launch test app

Could you help me thank you


unit test architecture/queue.go

https://github.com/vimukthi-git/beanstalkg/blob/master/architecture/queue.go needs to have unit tests.

Will do.

@stephenwithav I will complete this as I have some time now.


Text-To-Speech

issue #4

issue #4

You have to open an Issue then you will be assigned after that only you can make a PR.
Create a issue first then open a PR.


Add Holoscan Package

This MR adds support for the Holoscan SDK python runtime. This is enables the core functionality of the SDK for the Python module, please see the support matrix to understand the differences between various install methods.
This is just the first step to enable full Holoscan support, where I plan on subsequent MRs to support much more complex HoloHub applications.

Thanks @NigelNelson !  This is great 👍


Support keyExtractor on ScrollView

All child elements with ScrollView is given key scrollview-item-{$index}.
When the source data elements index positions change, due to sort / pop; the rendered item gets re-created. This patch enables keyExtractor prop to apply keys for ScrollView as well.

Hey @bd-arc,
Sounds good. Just pushed commit 993cc6e5a533926a418590b1ddcd0e6f69d1edca.
Good catch, I hadn't tried looked further into FlatList, just getting started with React Native
Thanks :)

And merged! Thanks for your responsiveness ;-)


Bug: *transientslice do not give the same results across OSes

Please tell us what you were doing! You can include code and files by drag and dropping them into the text area.
I am running a simple transient extraction. In MacOS, Max, Pd and SC give the same values. In Windows, again the same values between CCEs... but not between OSes!  In Linux (arm) again another set of values.
What was the expected result?
Since I cannot see any random seed in the extraction code (the randomSampling function seems not in use), and that I get the save values between CCEs within an OS, I was expecting the same values between OSes.
What was the actual result?
different slices points after the first few ones. the first 2 or 3 indices are the same, then they diverge.
What operating system were you using?
Mac
Operating system version
macos 15 Ubuntu 24lts win11
FluCoMa Version
pre-release 1.0.8

example code in SC for readability:
(
~refBasic = [146, 19189, 34710, 47225, 49466, 58303, 68190, 86944, 105695, 106754, 117448, 122139, 139530, 150492, 152884, 161525, 167575, 186297, 223797, 250361, 256305, 280173, 306507, 310674, 312509, 319116, 327659, 335219, 346779, 364673, 384784, 413937, 429154, 431229, 434504, 439537, 441625, 452032, 453392, 465470, 481516, 494517, 496122, 514126];
~refAdvanced = [667, 19184, 34706, 47229, 58300, 68183, 86942, 106752, 117438, 122135, 150487, 161523, 167572, 179048, 186294, 205050, 220493];

~src = Buffer.read(s,FluidFilesPath("Tremblay-AaS-SynthTwoVoices-M.wav"));
~indices = Buffer(s);
)

FluidBufTransientSlice.processBlocking(s,~src,indices:~indices,action:{~indices.loadToFloatArray(action: {|x|~basic = x})});

FluidBufTransientSlice.processBlocking(s,~src,indices:~indices, numFrames: 220500, order: 200, blockSize: 2048, padSize: 1024, skew: 1, threshFwd: 3, threshBack: 1, windowSize: 15, clumpLength: 30, minSliceLength: 4410, action:{~indices.loadToFloatArray(action: {|x|~advanced = x;\done.postln;})});

~refBasic == ~basic
~refBasic.size == ~basic.size
~refBasic.do{arg v,i; if (v != ~basic[i], {"% (%) ".postf(i, v - ~basic[i])}) };

~refAdvanced == ~advanced
~refAdvanced.size == ~advanced.size
~refAdvanced.do{arg v,i; if (v != ~advanced[i.min(~advanced.size - 1)], {"% (%) ".postf(i, v - ~advanced[i.min(~advanced.size - 1)])}) };

actually, in Linux I don't even get the same values between Pd and SC...

@AlexHarker might confirm there is no randomisation used - or that I'm wrong, and that would make this a non-bug...


HttpUrl initial API.

This is very early and subject to change. I'd like to evaluate the API first
because it's difficult to do properly and because if it's done right, the
implementation should be mostly mechanical once this is set.

Right now I'm missing a public API to do general encoding & decoding of application/x-www-form-urlencoded.
You can accomplish the same thing via hacks:
HttpUrl url = HttpUrl.parse("http://foo/").newBuilder()
    .addQueryParameter("toppings", "lettuce, tomato")
    .addQueryParameter("cheese", "shredded mozzarella & cheddar")
    .build();
String requestBody = url.encodedQuery();

Plus similar hacks to do decoding. Or we could have a Query class that looks & works a lot like our Headers class.

Right now I'm missing a public API to do general encoding & decoding of application/x-www-form-urlencoded.

Also potentially something that could be omitted and just duplicated. I don't think there's any value in exposing something like a Query type in the public API.

lovin' it. :shipit:


docs: add pug to "in the wild"

Pug is a task manager for terraform: https://github.com/leg100/pug
It's been refreshing working with bubbletea, thank you for all your hard work.

This looks so fun. Thanks for the PR!


fix(openresty) cjson.empty_array is nil when run on Apple M1/aarch64

When I am testing on Apple M1 + VMware + ubuntu 22.04,
I found cjson.empty_array can not work as expect,
I debug the cjson's code, then find the reason,
but we can not wait the openresty's release,
so I did this patch, If openresty's bundle fix this bug later,
then we must remove this patch.

Tests passed with this patch on my Mac M1, great!

©chronolaw, all our current patches are sorted. Can you please rename:
lua-cjson-<IP_ADDRESS>-empty_array.patch

to
lua-cjson-<IP_ADDRESS>_01-empty_array.patch

Otherwise this is great, and ready to be merged. Thank you.


ERROR tendermint/go-wire/data

Help. An error occurs when using the library.
../github.com/tendermint/go-crypto/priv_key.go:10:2: cannot find package "github.com/tendermint/go-wire/data" in any of:
/opt/go/src/github.com/tendermint/go-wire/data (from $GOROOT)
/home/ubuntu/workspace/src/github.com/tendermint/go-wire/data (from $GOPATH)
How to fix it?

Which version of the library are you using and with what other pieces of our ecosystem (tmlibs, tendermint, ...)?
If you have an overall go project could you post your Gopkg.toml or glide.yaml file.

Thank you very much for the answer. But I solved this problem.


Make HUBLiveService independent from HUBViewController

Instead of the HUBLiveService creating a view controller, have it emit a content operation and let the implementor setup and push the view controller. It makes the live service independent of the view controller and leaves the user in charge of what should be done (for example, add more content operations to the chain.
NOTE: This introduces a small API break in that it changes the HUBLiveServiceDelegate protocol. Given that this change makes sense even without the changes I'm making to the feature registry I deemed it made sense to clean this up on master even if we'll need to update the client when bumping this.
@cerihughes @spotify/objc-dev @rastersize @mumme

Codecov Report

Merging #318 into master will increase coverage by 0.22%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #318      +/-   ##
==========================================
+ Coverage   80.29%   80.51%   +0.22%
==========================================
  Files          76       76
  Lines        6058     6042      -16
==========================================
+ Hits         4864     4865       +1
+ Misses       1194     1177      -17

Impacted Files
Coverage Δ

sources/HUBManager.m
100% <100%> (ø)
:arrow_up:

sources/HUBLiveServiceImplementation.m
86.2% <100%> (-2.99%)
:arrow_down:

sources/HUBUtilities.h
87.5% <0%> (+17.7%)
:arrow_up:

Continue to review full report at Codecov.

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

👍

This was merged as part of #306.


Utility script to calculate distance between two sentences.

Utility script to calculate distance between two sentences.
Extracted from https://github.com/openshift/lightspeed-service/blob/main/tests/scripts/validate_response.py

@syedriko: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/images 	4a72a7b link 	true 	/test images
Full PR test history. Your PR dashboard.

Fix is in https://github.com/openshift/lightspeed-rag-content/pull/21

/retest

/approve

/retest

/retest

/retest


Ila_sim

A class to generate systemC simulator code from ILA.

close #33
This is addressing the ILA-based co-simulation model generation.


Add fcitx related packages for some languages.

Related pull request: #5 https://github.com/trueos/trueos-desktop/pull/5
Note: this commit is not enough.
Change /usr/local/share/truos/xstartup script.

Upon merging this change the port build failed.  I will update the plist to fix this morning.


Fix Location Data table formatting.

Docs Build status updates of commit b627938:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingMaps/rest-services/locations/location-data.md
:white_check_mark:Succeeded

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

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

Docs Build status updates of commit f5512e9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

BingMaps/rest-services/locations/location-data.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 8923f3f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

BingMaps/rest-services/locations/location-data.md
:white_check_mark:Succeeded

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


loading picturefill with Browserify

I have issues loading picturefill with browserify.
for example i require it:
require('picturefill');
or
var picturefill =  require('picturefill');
or
window.picturefill = require('picturefill');
i'm getting error message
Safari: TypeError: undefined is not a constructor (evaluating 'new this.Image()')
Firefox: TypeError: this.Image is not a constructor
Chrome: Uncaught TypeError: undefined is not a function
all fail on last line:  } )( this, this.document, new this.Image() );
if i change 'this' to 'window'. it works. I don't want to modify original library.
how i can properly pass a scope to this script?

Hey @mromanoff, this actually has been fixed in master ( 9f5279a7bb49a84aafb7cdb535ef12d15f963eb4 ), and will be released in 2.3.0. In the meantime, you can either manually edit the picturefill file in your node_modules folder, or grab a copy from the master branch to use. Until then, I'm going to work with the core PF team to see if we can't get a patch up to npm to fix it. Thanks!

@mike-engel thank you for quick response.

@mike-engel thanks for the solution. When do we think the NPM registry will be updated?

@nicholasjohn Hopefully soon. Once #420 is done, we can move super fast with this one.

@nicholasjohn @mromanoff Picturefill on npm should be updated now to 2.2.1 with this fix!
https://www.npmjs.com/package/picturefill


Allow building type for ./rs features

Currently the only supported option is parking, which is incompatible with inputs trained on buildings.
root@3d58a7d0d5c3:/app# ./rs features --type building --dataset config/dataset-building-middlebury.toml vt/rutland/masks/ vt/rutland/features/buildings-out.geojson
usage: ./rs features [-h] --type {parking} --dataset DATASET masks out
./rs features: error: argument --type: invalid choice: 'building' (choose from 'parking')

root@3d58a7d0d5c3:/app# ./rs features --dataset config/dataset-building-middlebury.toml vt/rutland/masks/ vt/rutland/features/buildings-out.geojson
usage: ./rs features [-h] --type {parking} --dataset DATASET masks out
./rs features: error: the following arguments are required: --type
root@3d58a7d0d5c3:/app# ./rs features --type parking --dataset config/dataset-building-middlebury.toml vt/rutland/masks/ vt/rutland/features/buildings-out.geojson
Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/app/robosat/tools/__main__.py", line 60, in <module>
    args.func(args)
  File "/app/robosat/tools/features.py", line 38, in main
    assert set(labels).issuperset(set(handlers.keys())), "handlers have a class label"
AssertionError: handlers have a class label

Am I correct that this will require another well-thought-out postprocessing handler?

The parking handler right now really works for any polygons. What we need to do is

create a generic polygon handler
make the handlers work across zoom levels
building and parking lot handler can use its functionality

A generic polygon post-processing handler works as long as we don't want to do e.g. special case post-processing for buildings. Also for the zoom level generalization check https://github.com/mapbox/robosat/issues/51 and https://github.com/mapbox/robosat/pull/88.
What you can do for now is

check the parking lot thresholds and adapt them to your zoom level; see https://github.com/mapbox/robosat/blob/b7f6ebf79ddac7fc4c04a4f3698b1deae16cd7d1/robosat/features/parking.py#L12-L14
remove the filter for z18 (for which the thresholds were tuned) here https://github.com/mapbox/robosat/blob/b7f6ebf79ddac7fc4c04a4f3698b1deae16cd7d1/robosat/features/parking.py#L20-L21
run with --type parking

Or better give https://github.com/mapbox/robosat/pull/88 a try and see if it works for you.

@daniel-j-h I ran it as faux-parking per your suggestion above (I did not run the linked branch), and it threw this:
root@3d58a7d0d5c3:/app# ./rs features --type parking --dataset config/dataset-parking-middlebury.toml vt/rutland/masks/ vt/rutland/features/buildings-out.geojson
Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/app/robosat/tools/__main__.py", line 60, in <module>
    args.func(args)
  File "/app/robosat/tools/features.py", line 41, in main
    handler = handlers[args.type]()
  File "/app/robosat/features/parking.py", line 26, in __init__
    denoised = denoise(mask, self.kernel_size_denoise)
NameError: name 'mask' is not defined

Indeed, I don't see that param being handed in.

The mask is passed in here
https://github.com/mapbox/robosat/blob/b7f6ebf79ddac7fc4c04a4f3698b1deae16cd7d1/robosat/features/parking.py#L19
from the callsite here
https://github.com/mapbox/robosat/blob/b7f6ebf79ddac7fc4c04a4f3698b1deae16cd7d1/robosat/tools/features.py#L49
Are you sure you didn't accidentally delete it or change something when removing the tile check?

I may well have. Also using a several-days-old, cpu-specific image at this point. Lemme update and try again.

@daniel-j-h Pulling the updates did the trick! Thanks!
I'd definitely love to see the generic polygon handler though; I'll be trying any number of feature types that are neither parking nor buildings.

Wish we can set  type ,instead of updating code. Can you update features command please?

@wucangeo see the branch in
https://github.com/mapbox/robosat/pull/88
then it should be easy to re-use the existing handler.

@daniel-j-h How rs features should work with roads detection? I am blocked on the pipeline here. Could you advice please?

You'd have to implement the featurization for roads first. I'm no longer with Mapbox or actively developing or maintaining this project; please talk to Mapbox folks if you have questions.
On May 13, 2020 1:46:44 PM UTC, Grifel79<EMAIL_ADDRESS>wrote:

@daniel-j-h How rs features should work with roads detection? I am
blocked on the pipeline here. Could you advice please?


Add support for the old lua formatted ease of use conventions and the numeric log rolling values

… numeric
log rolling values
Addresses issue #5080
(cherry picked from commit a105fd3d177c7c4223609b09014bff372f0c7d0e)
(cherry picked from commit 52f2c4c61899a3200138566103491157f0295fad)

This was originally backported to 8.1.x which is defunct, so this got missed in 8.0

[approve ci clang-format]

[approve ci clang-format]

It's trailing whitespace (this is probably the first PR since that check when in):
Error: Trailing whitespaces are not allowed!

@zwoop says to ignore the error and just merge. I 👍

alright good for now, would be nice to go through and fix these up since you know this wont be the last 8.0 pr ;)


How to send a message to the terminal?

Hi, I want to send messages to terminal from code like console.log('message') but without showing it in application console

this might help:
  const printInTerminal = (content) => {
    terminalRef.current.state.instances[0].instance.updater.enqueueSetState(
      terminalRef.current.state.instances[0].instance,
      {
        summary: [
          ...terminalRef.current.state.instances[0].instance.state.summary,
          ...(Array.isArray(content) ? content.map((c) => [c]) : [content]),
        ],
      }
    );
  };

To print one line just do printInTerminal('Hello world!')
To print multiple lines do printInTerminal(['Hello world!', 'Foo bar'])


Add fuzz testing with Forge to the SQF Strategy

Strategy Folder: https://github.com/streaming-funding/allo-v2/tree/main/contracts/strategies/_poc/sqf-superfluid
Tool: Foundy - Forge
Testing Condition Exclusion: The total GDA units (derived from donations & quadratic matching formula) must always be less than the wei/sec allocated through the GDA (matching pool flow rate). This is a known limitation and we implemented a unit scale reduction for production that will prevent this from happening under normal round conditions. We don't need fuzz tests where the GDA units exceed the wei/sec allocated.
See: https://v2.docs.superfluid.finance/docs/protocol/distributions/guides/pools#examples. In fuzz testing, we can exclude scenarios where the units exceed flow.

Created this in the wrong repo


Delete bibid 12346805

@christinach commented on Mon Mar 22 2021
This was deleted from voyager on 03-19-2021. I couldn't see it in the delete_ids for 03-19-2021 or 03-20-2021.

Also delete bibid '11562111'. I can't find it in voyager and it appears in the catalog as a duplicate of another record.

we are moving to alma


Any chance to use ESP8266 as multiple lamps or strips without the emulated bridge ?

I was wondering, as I already own a HUE Bridge 2.0, can we extract part of the code to build simple "lamps" or "strips" that are detectable on an original philips bridge ?
As I own a bridge, I'd love to be able to add my own RGB Lamps (That I don't have as they are too expensive), built with an ESP.
Using the new Razer Synapse 3 software, it could be nice to use an ESP8266 to drive 3 or 4 generic RGB leds or RGB  led strips and use it as some kind of ambilight. And that could be much easier to do, right ?

I know that this is a github for development but I found this: https://www.amazon.com/Wireless-electronic-ballast-interface-certified/dp/B00NMSQ4QQ
Maybe if someone can buy it an reverse engineering that....

Hue bridge communicate just with ZigBee lights,. Esp8266 work with wifi protocol.w

The biggest concern with multiple bridges are the imposed limitations on some of the hue software.
eg. the official philips hue android can only handle one bridge.
then there is "all 4 hue" on android also.. it supports multiple bridges just fine.

I'm not sure but from what I've seen, the Razer application for Windows does not allow either, cause it can only see my original Bridge, not the emulated one.


[BACKPORT/22.2.x] .buildkite: Switch CI jobs to using /dev/sgx_enclave devices

Backport of #5255.

I did not backport artifact caching #5251, I hope this does not cause the stable branch CI pipelines to timeout too much. Sometimes it takes 8+ minutes just to download artifacts, probably because Buildkite agents are in another region.


B站comfy UI整合open-sora-plan视频

B站地址: https://www.bilibili.com/video/BV1Uz421k7hL/

This is awesome, thanks for sharing!


Example 1H / 15N is broken

@lpatiny @jobo322
this example added by Michale in this ticket
https://github.com/cheminfo/nmr-displayer/issues/779
and I informed you that z array returns empty....

@lpatiny @jobo322
this example added by Michale in this ticket
https://github.com/cheminfo/nmr-displayer/issues/779
and I informed you that z array returns empty....

Duplicate of https://github.com/cheminfo/nmr-displayer/issues/779

Duplicate of https://github.com/cheminfo/nmr-displayer/issues/779


unable to run bcbio-nextgen

Hi all,
a bit of a beginner here
I have installed bcbio-nextgen using a conda environment on a HPC.I am trying to do variant calling for a patient tumor/normal sample but get the following error:
run info config: /home/svu/phaei/bcbio-nextgen/patient_zero.yaml Traceback (most recent call last):   File "/home/svu/phaei/.conda/miniconda/4.9/envs/bcbio/bin/bcbio_nextgen.py", line 245, in <module>     main(**kwargs)   File "/home/svu/phaei/.conda/miniconda/4.9/envs/bcbio/bin/bcbio_nextgen.py", line 46, in main     run_main(**kwargs)   File "/home/svu/phaei/.conda/miniconda/4.9/envs/bcbio/lib/python3.8/site-packages/bcbio/pipeline/main.py", line 40, in run_main     config, config_file = config_utils.load_system_config(config_file, workdir)   File "/home/svu/phaei/.conda/miniconda/4.9/envs/bcbio/lib/python3.8/site-packages/bcbio/pipeline/config_utils.py", line 68, in load_system_config     raise ValueError("Could not find input system configuration file %s, " ValueError: Could not find input system configuration file bcbio_system.yaml, including inside standard directory /home/svu/phaei/.conda/miniconda/4.9/envs/galaxy
Help would be greatly appreciated.
thank you

Hi @iichelhadi !
So you have installed bcbio-nextgen python package?
It is more than that: https://bcbio-nextgen.readthedocs.io/en/latest/contents/installation.html
As a result you should get an isolated conda with several enviroments, tools, and data installation.
Sergey

Hi @iichelhadi !
So you have installed bcbio-nextgen python package?
It is more than that: https://bcbio-nextgen.readthedocs.io/en/latest/contents/installation.html
As a result you should get an isolated conda with several enviroments, tools, and data installation.
Sergey

Hi Sergey,
I believe the issue is the missing reference data, etc. I tried running this install command after installing bcbio
bcbio_nextgen.py upgrade -u skip --genomes hg38 --aligners bwa
But it wouldn't work likely due to lack of admin priveleges but I am not sure.
I installed bcbio-nextgen using the following command in a conda env
conda install -c bioconda bcbio-nextgen
I still cannot get it to work.
regards
EL

Hi @iichelhadi !
Unfortunately, this is not the way bcbio works. It is not enough to install one package via conda.
You need to run the installer script, etc, as described in the installation guide:
https://bcbio-nextgen.readthedocs.io/en/latest/contents/installation.html
bcbio is a heavy package ~50G + data with its own conda etc
Sergey

Hi @iichelhadi !
Unfortunately, this is not the way bcbio works. It is not enough to install one package via conda.
You need to run the installer script, etc, as described in the installation guide:
https://bcbio-nextgen.readthedocs.io/en/latest/contents/installation.html
bcbio is a heavy package ~50G + data with its own conda etc
Sergey

Thanks for the reply. I contacted IT to help me install it. Hope that will resolve this issue


upgrade to travis containers with sudo: false

See: http://docs.travis-ci.com/user/migrating-from-legacy/

Ok closing this if it's not needed


chore: speed up replica creation/destruction

Improve the performance of replica creation/destruction by:

Increasing the size of the buffer used to wipe the superblock from 4K to 64K.
Wiping the superblock on creation only.

bors try

I have a general question: is it ok to leave the data after deleting the LVOL ? Is wiping out all data upon volume removal not what we are supposed to do in the first place ?
Shall we have a tuneable option to allow data removal once an LVOL is removed ?

I have a general question: is it ok to leave the data after deleting the LVOL ? Is wiping out all data upon volume removal not what we are supposed to do in the first place ?
Shall we have a tuneable option to allow data removal once an LVOL is removed ?
From the discussion that were had, it seemed ok to remove the wiping of the data from the destruction. Wiping out all the data on volume removal would be good but it takes a long time and things tend to time out. We had code previously that attempted to do this (implementation of unmap) but there were problems with this.

I definitely think this is something that needs revisting and that we can improve on.

bors merge


Commit interface error

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.72.0
OS Version: Windows 10

Steps to Reproduce:

The problem is this duration when I open the part to make a new commit for my projects, not directly harming the result but interfering with the experience

@TylerLeonhardt, any idea what went wrong here? Is this just a localization bug?

@lszomoru this looks ok to me:

And the string seems ok:
https://github.com/microsoft/vscode-loc/blob/main/i18n/vscode-language-pack-pt-BR/translations/extensions/git.i18n.json#L230-L234
@Jose-Vinicius couple of questions:

do those buttons do different things? You can see in my screenshot that they normally have different behaviors.
Could you uninstall and reinstall the Portuguese language pack just in case something messed up in the installation?
Can you try in the VS Code Insiders build to see if this is fixed there?: http://code.visualstudio.com/insiders

@TylerLeonhardt,
I did what you said I installed the language pack, and now it works correctly again, thanks a lot for the help.

Thanks! Glad you're unblocked. I'll go ahead and close this but will investigate further if more folks chime in saying they had the same issue.


boards: arm: Add mcuboot flash partitions to mimxrt1020_evk

Adds flash partitions and chosen nodes to the mimxrt1020_evk device tree
to support mcuboot on the internal QSPI flash.
Also enables FlexSPI flash driver XIP mode support on this board to
support mcuboot.
Signed-off-by: Xabier Marquiegui<EMAIL_ADDRESS>

Thanks for the patch, it looks good. Will you please also update the board documentation page (boards/arm/mimxrt1020_evk/doc/index.rst) to reflect that a flash driver is now supported?

No problem. I have already pushed the documentation change. I have taken the liberty of including the mimxrt1024_evk documentation file too. Flash support for this board was added on this commit:
commit e12e126f3262ffcac90572a6be4dffe12f17a30f
Author: Mikkel Jakobsen<EMAIL_ADDRESS>

@nashif , thoughts on this PR?

Commit a50a16e7104924f126b668953fdfc804ee99006d says that @MaureenHelm is no longer working in NXP, and @nashif seems to be unresponsive.
Maybe Assignees and Reviewers need to be updated?


Node 16.17.0 not supported to<EMAIL_ADDRESS>

My angular application was working fine for node version 14.15.0.
I upgrade my node version to 16.17.0 and deleted the node_modules folder and package-lock.json.
Now I'm trying to do npm install but I'm getting the below error.

Do you have a direct dependency on node-sass, if so remove it.
You can check by running he below command.
npm ls node-sass

Can you please share the contents of your package.json please? Thanks.

@alan-agius4 The above issue is coming due to node-sass since node-sass incompatibility with Node 16.
It works fine after setting the below flag
CXXFLAGS="--std=c++14" npm install worked for me as well on M14 Mac


Overwriting of stepDefinitions is not working

Current behavior
We want to overwrite the stepDefinitions like this:
{
  "stepDefinitions": [
    "src/[filepath]/**/*.ts",
    "src/[filepath].ts",
<EMAIL_ADDRESS>  ]
}

In the package.json it has no effect. If we add a .cypress-cucumber-preprocessorrc.json file this error will be thrown:

In the json-parser an empty space is appended as first sign to the json string, what causes the error.
Desired behavior
No error should be thrown
Test code to reproduce
https://github.com/simon-ittmann/cypress-cucumber-global-steps
Versions
See github repo below
Checklist

[x] I've read the FAQ.
[x] I've read Instructions for logging issues.
[x] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

Your file contains a byte order mark.

Solves the problem, thank you :)


Bad translation in Portuguese from Portugal

Windows Terminal version (or Windows build number)
1.8.1444.0
Other Software
No response
Steps to reproduce
Open settings in Windows Terminal settings.
Also right-click in any folder.
Expected Behavior
No response
Actual Behavior
The settings menu is using a mix of portuguese from Portugal and Brazil:

Also, the context menu option is not translated, as shown in the picture below:

Thanks @jorgemieec for the feedback!  It would be very helpful if you could compose a table like https://github.com/microsoft/terminal/issues/9238#issuecomment-783777519 & https://github.com/microsoft/terminal/issues/9328#issue-819602260 for the localization team. See https://github.com/microsoft/terminal/issues/10043#issuecomment-833473347 if you're wondering where to find the string keys.


Widedit

Wrap Bangle.loadWidgets instead of overriding it
Allow all areas to be set (bottom and top widget bar)

Looks great - thanks!


readlink -f added in XCode < 14.3 causes archiving error

Is there an existing issue for this?

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

Steps to reproduce
Unfortunately the fix with readlink -f (https://github.com/flutter/flutter/issues/123890) doesn't work for older Xcode/MacOS reporting error: readlink: illegal option -- f when trying to flutter build ipa. My env is:
[✓] Flutter (Channel stable, 3.7.12, on macOS 12.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
It started to happen when I did flutter upgrade to the latest (from 3.7.7 or so).
To reproduce:

Test on the platform as above
Call flutter clean
Call flutter build ipa or precede it with flutter pub get (doesn't matter in fact)
After some time you get Encountered error while archiving for device. and a few rows above there's error message:

mkdir -p
/Users/rocket/Library/Developer/Xcode/DerivedData/Runner-bvkptabgpblonedyoijtfiqcpvjk/Build/Intermediates.noindex/A
rchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/Runner.app/Frameworks
Symlinked...
readlink: illegal option -- f
usage: readlink [-n] [file ...]
Command PhaseScriptExecution failed with a nonzero exit code

Expected results
No errors when building archives. No -f flag added on XCode version < 14.3
Actual results
Building archive is broken with error message Encountered error while archiving for device. caused by the -f flag.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[...]
mkdir -p
    /Users/rocket/Library/Developer/Xcode/DerivedData/Runner-bvkptabgpblonedyoijtfiqcpvjk/Build/Intermediates.noindex/A
    rchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/Runner.app/Frameworks
    Symlinked...
    readlink: illegal option -- f
    usage: readlink [-n] [file ...]
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in dependency order

    Result bundle written to path:
        /var/folders/vr/480fjlkx2p35rdk07lgmc4z80000gn/T/flutter_tools.PAAjsj/flutter_ios_build_temp_dirsR80Xg/temporary_x
        cresult_bundle

Encountered error while archiving for device.

Flutter Doctor output
Doctor output
I don't have Android and Chrome installed on this machine so not included in the doctor log.

[✓] Flutter (Channel stable, 3.7.12, on macOS 12.0 21A5248p darwin-x64, locale en-PL)
    • Flutter version 3.7.12 on channel stable at /Users/rocket/Desktop/flutter/SDK/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (3 days ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.12.1

[✓] VS Code (version 1.76.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (2 available)
    • iPhone 12 (mobile) • E8A448FD-2C4D-4A3E-BBFE-0A0D1B38FAB6 • ios        •
      com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)    • macos                                • darwin-x64 • macOS 12.0 21A5248p
      darwin-x64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Hi @rafaellop, please provide the full verbose output of flutter build ipa -v. The output may be huge, so kindly put it into a .txt/.log file or upload it to a service like pastebin so that we can trace the logs.
Thank

Here's the log from the flutter --verbose build ipa
https://www.dropbox.com/s/071sivciqffzhgd/log.txt?dl=0

Thanks for the logs.
Can you also share your podfile, podfile.lock & pubspec.yaml files?
Thank you

This isn't coming from Flutter, which explicitly doesn't add the flag unless you're running > Xcode 14.3
https://github.com/flutter/flutter/blob/5d3c1ca870a11248ca3df944ce337078a3d15738/packages/flutter_tools/lib/src/migrations/cocoapods_script_symlink.dart#L36-L40
This is coming from CocoaPods:
https://github.com/CocoaPods/CocoaPods/releases/tag/1.12.1
Essentially CocoaPods 1.12.1 isn't compatible with Xcode 13.x if that doesn't understand the -f flag.

@rafaellop I strongly suggest filing an issue with CocoaPods with reproduction steps.
The workaround from Flutter would be to figure out which Xcode version understands this flag and bump the minimum required to that.

I archived and flutter build ipa successfully on Xcode 14 and 13.4 on CocoaPods 1.12.1.
Pods-Runner-frameworks.sh contains the -f flag.
    source="$(readlink -f "${source}")"

@rafaellop can you give very specific reproduction steps?  I don't see it.

@jmagman I also think it's from cocoapods. Regarding the reproduction steps, I've given them in my issue:
To reproduce:

1. Test on the platform as above
2. Call `flutter clean`
3. Call `flutter build ipa` or precede it with `flutter pub get` (doesn't matter in fact)
4. After some time you get `Encountered error while archiving for device`

I can reproduce that each time I try them. To be more sure you can also clean build in Xcode.
However I can successfully build my archive if I remove the -f flag by hand from the .sh script where it's added.
@danagbemava-nc Are the podfile, podfile.lock & pubspec.yaml files still needed after @jmagman discoveries?

I believe it might help us reproduce the issue. I also tried to repro with a few of the plugins I saw in your logs with Xcode 13.4.1 and cocoapods 1.12.1 on codemagic and I could not reproduce the bug.

OK, attached below.
I'd like to mention one thing specific to my project if that may matter. Some of my project files in the lib directory are symlinked from a directory outside the project main directory. Something like this:
myapp/
     lib/
         shared/
             localization # this is a symlink the folder shown below

shared/
     localization/

In the file system it looks this way:
lrwxr-xr-x  1 rocket  staff   28 Feb 26 19:38 localization -> ../../../shared/localization
Now the files you asked:
podfile
# Uncomment this line to define a global platform for your project
platform :ios, '13.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

podfile.lock
PODS:
  - app_tracking_transparency (0.0.1):
    - Flutter
  - connectivity_plus (0.0.1):
    - Flutter
    - ReachabilitySwift
  - device_info_plus (0.0.1):
    - Flutter
  - Flutter (1.0.0)
  - flutter_app_badger (1.3.0):
    - Flutter
  - flutter_email_sender (0.0.1):
    - Flutter
  - flutter_local_notifications (0.0.1):
    - Flutter
  - flutter_native_timezone (0.0.1):
    - Flutter
  - fluttertoast (0.0.2):
    - Flutter
    - Toast
  - FMDB (2.7.5):
    - FMDB/standard (= 2.7.5)
  - FMDB/standard (2.7.5)
  - Google-Mobile-Ads-SDK (9.14.0):
    - GoogleAppMeasurement (< 11.0, >= 7.0)
    - GoogleUserMessagingPlatform (>= 1.1)
  - google_mobile_ads (1.0.0):
    - Flutter
    - Google-Mobile-Ads-SDK (~> 9.13)
  - GoogleAppMeasurement (10.8.0):
    - GoogleAppMeasurement/AdIdSupport (= 10.8.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.8)
    - GoogleUtilities/MethodSwizzler (~> 7.8)
    - GoogleUtilities/Network (~> 7.8)
    - "GoogleUtilities/NSData+zlib (~> 7.8)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - GoogleAppMeasurement/AdIdSupport (10.8.0):
    - GoogleAppMeasurement/WithoutAdIdSupport (= 10.8.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.8)
    - GoogleUtilities/MethodSwizzler (~> 7.8)
    - GoogleUtilities/Network (~> 7.8)
    - "GoogleUtilities/NSData+zlib (~> 7.8)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - GoogleAppMeasurement/WithoutAdIdSupport (10.8.0):
    - GoogleUtilities/AppDelegateSwizzler (~> 7.8)
    - GoogleUtilities/MethodSwizzler (~> 7.8)
    - GoogleUtilities/Network (~> 7.8)
    - "GoogleUtilities/NSData+zlib (~> 7.8)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - GoogleUserMessagingPlatform (2.0.1)
  - GoogleUtilities/AppDelegateSwizzler (7.11.1):
    - GoogleUtilities/Environment
    - GoogleUtilities/Logger
    - GoogleUtilities/Network
  - GoogleUtilities/Environment (7.11.1):
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleUtilities/Logger (7.11.1):
    - GoogleUtilities/Environment
  - GoogleUtilities/MethodSwizzler (7.11.1):
    - GoogleUtilities/Logger
  - GoogleUtilities/Network (7.11.1):
    - GoogleUtilities/Logger
    - "GoogleUtilities/NSData+zlib"
    - GoogleUtilities/Reachability
  - "GoogleUtilities/NSData+zlib (7.11.1)"
  - GoogleUtilities/Reachability (7.11.1):
    - GoogleUtilities/Logger
  - health (1.0.4):
    - Flutter
  - in_app_review (0.2.0):
    - Flutter
  - nanopb (2.30909.0):
    - nanopb/decode (= 2.30909.0)
    - nanopb/encode (= 2.30909.0)
  - nanopb/decode (2.30909.0)
  - nanopb/encode (2.30909.0)
  - notification_permissions (0.4.4):
    - Flutter
  - path_provider_foundation (0.0.1):
    - Flutter
    - FlutterMacOS
  - permission_handler_apple (9.0.4):
    - Flutter
  - PromisesObjC (2.2.0)
  - purchases_flutter (4.11.2):
    - Flutter
    - PurchasesHybridCommon (= 4.14.2)
  - PurchasesHybridCommon (4.14.2):
    - RevenueCat (= 4.17.9)
  - ReachabilitySwift (5.0.0)
  - RevenueCat (4.17.9)
  - share_plus (0.0.1):
    - Flutter
  - sqflite (0.0.2):
    - Flutter
    - FMDB (>= 2.7.5)
  - Toast (4.0.0)
  - url_launcher_ios (0.0.1):
    - Flutter

DEPENDENCIES:
  - app_tracking_transparency (from `.symlinks/plugins/app_tracking_transparency/ios`)
  - connectivity_plus (from `.symlinks/plugins/connectivity_plus/ios`)
  - device_info_plus (from `.symlinks/plugins/device_info_plus/ios`)
  - Flutter (from `Flutter`)
  - flutter_app_badger (from `.symlinks/plugins/flutter_app_badger/ios`)
  - flutter_email_sender (from `.symlinks/plugins/flutter_email_sender/ios`)
  - flutter_local_notifications (from `.symlinks/plugins/flutter_local_notifications/ios`)
  - flutter_native_timezone (from `.symlinks/plugins/flutter_native_timezone/ios`)
  - fluttertoast (from `.symlinks/plugins/fluttertoast/ios`)
  - google_mobile_ads (from `.symlinks/plugins/google_mobile_ads/ios`)
  - health (from `.symlinks/plugins/health/ios`)
  - in_app_review (from `.symlinks/plugins/in_app_review/ios`)
  - notification_permissions (from `.symlinks/plugins/notification_permissions/ios`)
  - path_provider_foundation (from `.symlinks/plugins/path_provider_foundation/ios`)
  - permission_handler_apple (from `.symlinks/plugins/permission_handler_apple/ios`)
  - purchases_flutter (from `.symlinks/plugins/purchases_flutter/ios`)
  - share_plus (from `.symlinks/plugins/share_plus/ios`)
  - sqflite (from `.symlinks/plugins/sqflite/ios`)
  - url_launcher_ios (from `.symlinks/plugins/url_launcher_ios/ios`)

SPEC REPOS:
  trunk:
    - FMDB
    - Google-Mobile-Ads-SDK
    - GoogleAppMeasurement
    - GoogleUserMessagingPlatform
    - GoogleUtilities
    - nanopb
    - PromisesObjC
    - PurchasesHybridCommon
    - ReachabilitySwift
    - RevenueCat
    - Toast

EXTERNAL SOURCES:
  app_tracking_transparency:
    :path: ".symlinks/plugins/app_tracking_transparency/ios"
  connectivity_plus:
    :path: ".symlinks/plugins/connectivity_plus/ios"
  device_info_plus:
    :path: ".symlinks/plugins/device_info_plus/ios"
  Flutter:
    :path: Flutter
  flutter_app_badger:
    :path: ".symlinks/plugins/flutter_app_badger/ios"
  flutter_email_sender:
    :path: ".symlinks/plugins/flutter_email_sender/ios"
  flutter_local_notifications:
    :path: ".symlinks/plugins/flutter_local_notifications/ios"
  flutter_native_timezone:
    :path: ".symlinks/plugins/flutter_native_timezone/ios"
  fluttertoast:
    :path: ".symlinks/plugins/fluttertoast/ios"
  google_mobile_ads:
    :path: ".symlinks/plugins/google_mobile_ads/ios"
  health:
    :path: ".symlinks/plugins/health/ios"
  in_app_review:
    :path: ".symlinks/plugins/in_app_review/ios"
  notification_permissions:
    :path: ".symlinks/plugins/notification_permissions/ios"
  path_provider_foundation:
    :path: ".symlinks/plugins/path_provider_foundation/ios"
  permission_handler_apple:
    :path: ".symlinks/plugins/permission_handler_apple/ios"
  purchases_flutter:
    :path: ".symlinks/plugins/purchases_flutter/ios"
  share_plus:
    :path: ".symlinks/plugins/share_plus/ios"
  sqflite:
    :path: ".symlinks/plugins/sqflite/ios"
  url_launcher_ios:
    :path: ".symlinks/plugins/url_launcher_ios/ios"

SPEC CHECKSUMS:
  app_tracking_transparency: 5b1745ef9ade815f7455cb6a0848349589afb7c5
  connectivity_plus: 413a8857dd5d9f1c399a39130850d02fe0feaf7e
  device_info_plus: e5c5da33f982a436e103237c0c85f9031142abed
  Flutter: f04841e97a9d0b0a8025694d0796dd46242b2854
  flutter_app_badger: b87fc231847b03b92ce1412aa351842e7e97932f
  flutter_email_sender: 02d7443217d8c41483223627972bfdc09f74276b
  flutter_local_notifications: 0c0b1ae97e741e1521e4c1629a459d04b9aec743
  flutter_native_timezone: 5f05b2de06c9776b4cc70e1839f03de178394d22
  fluttertoast: eb263d302cc92e04176c053d2385237e9f43fad0
  FMDB: 2ce00b547f966261cd18927a3ddb07cb6f3db82a
  Google-Mobile-Ads-SDK: 4fe6304b771f8467d29978cb790ec1e56e646946
  google_mobile_ads: 528ab4673c5b5fd36321b7e90fc585064cdbaf2b
  GoogleAppMeasurement: 0ba93018e916f7badf915c2337d43cc1fa96b3f9
  GoogleUserMessagingPlatform: 5f8b30daf181805317b6b985bb51c1ff3beca054
  GoogleUtilities: 9aa0ad5a7bc171f8bae016300bfcfa3fb8425749
  health: 5a380c0f6c4f619535845992993964293962e99e
  in_app_review: 318597b3a06c22bb46dc454d56828c85f444f99d
  nanopb: b552cce312b6c8484180ef47159bc0f65a1f0431
  notification_permissions: 825ea1bf2a52ab585c53fd7b5e8e96876d735d4b
  path_provider_foundation: c68054786f1b4f3343858c1e1d0caaded73f0be9
  permission_handler_apple: 44366e37eaf29454a1e7b1b7d736c2cceaeb17ce
  PromisesObjC: 09985d6d70fbe7878040aa746d78236e6946d2ef
  purchases_flutter: fd864f53a8242162edd4a76f8726f0de52b30dd2
  PurchasesHybridCommon: 05e767205a460e564ec1bf3ee6057c5ac9068be1
  ReachabilitySwift: 985039c6f7b23a1da463388634119492ff86c825
  RevenueCat: 8cc3e93a5e29a5bac443d38a0973a317e841f3f1
  share_plus: 056a1e8ac890df3e33cb503afffaf1e9b4fbae68
  sqflite: 6d358c025f5b867b29ed92fc697fd34924e11904
  Toast: 91b396c56ee72a5790816f40d3a94dd357abc196
  url_launcher_ios: 08a3dfac5fb39e8759aeb0abbd5d9480f30fc8b4

PODFILE CHECKSUM: cc1f88378b4bfcf93a6ce00d2c587857c6008d3b

COCOAPODS: 1.12.1

pubspec.yaml
name: myapp
description: App description

publish_to: 'none'

version: 1.0.0+1000000

environment:
  sdk: '>=2.18.2 <3.0.0'

dependencies:
  flutter:
    sdk: flutter
  google_fonts: ^4.0.3
  url_launcher: ^6.1.7
  flutter_localizations:
    sdk: flutter
  ionicons: ^0.2.1
  styled_text: ^7.0.0
  get: ^4.6.5
  get_storage: ^2.0.3
  flutter_animate: ^4.1.0
  easy_debounce: ^2.0.2+1
  flutter_email_sender: ^5.2.0
  path_provider: ^2.0.11
  flutter_native_timezone: ^2.0.0
  timezone: ^0.9.0
  intl: ^0.17.0
  sqflite: ^2.2.2
  path: ^1.8.2
  flutter_slidable: ^3.0.0
  fl_chart: ^0.61.0
  share_plus: ^6.3.0
  in_app_review: ^2.0.6
  restart_app: ^1.1.1
  health: ^6.0.0
  permission_handler: ^10.2.0
  flutter_local_notifications: ^13.0.0
  google_mobile_ads: ^2.3.0
  connectivity_plus: ^3.0.2
  app_tracking_transparency: ^2.0.3
  purchases_flutter: ^4.9.0
  device_info_plus: ^8.0.0
  http: ^0.13.5
  flutter_carousel_widget: ^2.0.2
  smooth_page_indicator: ^1.0.1
  fluttertoast: ^8.2.1
  dart_openai: ^1.9.1
  crypto: ^3.0.2
  lottie: ^2.2.0
  flutter_app_badger: ^1.5.0
  notification_permissions: ^0.6.1

flutter_icons:
  image_path_android: "assets/images/icon.png"
  image_path_ios: "assets/images/icon.png"
  android: true
  ios: true
  adaptive_icon_foreground: "assets/images/icon_adaptive.png" # only available for Android 8.0 devices and above
  adaptive_icon_background: "#19B3F5"
  min_sdk_android: 21
  remove_alpha_ios: true
  web:
    generate: true
    image_path: "assets/images/icon.png"
    background_color: "#19B3F5"
    theme_color: "#19B3F5"
  windows:
    generate: true
    image_path: "assets/images/icon.png"
    icon_size: 48 # min:48, max:256, default: 48
  macos:
    generate: true
    image_path: "assets/images/icon.png"

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_launcher_icons: ^0.13.0
  very_good_analysis: ^4.0.0+1
  flutter_oss_licenses: ^2.0.1
  flutter_lints: ^2.0.0
  dart_code_metrics: ^5.1.0

flutter:
  uses-material-design: true
  assets:
    - assets/images/
    - assets/images/shared/
    - assets/localization/
    - assets/localization/products/

Regarding the reproduction steps, I've given them in my issue:
To reproduce:

1. Test on the platform as above
2. Call `flutter clean`
3. Call `flutter build ipa` or precede it with `flutter pub get` (doesn't matter in fact)
4. After some time you get `Encountered error while archiving for device`

Yeah I saw that, I'm asking for actually specific steps starting with a flutter create and adding the plugins, etc, I'm not sure what "Test on the platform as above" exactly means.  I am unable to reproduce the archive issue on Xcode 13.4 or CocoaPods 1.12.1.   The -f flag was in the script but it archived successfully.

Platform "as above" are the information about Flutter, MacOS, XCode, versions. I didn't tested on other. It's the platform I use.
OK, now I get what you mean as "steps". I'll try to go all the way starting from flutter create.

So I did a test on a clean project in the same environment:

flutter create test
Added google_fonts: ^4.0.3 to the pubspec.yaml
Called flutter build ipa
Called open ios/Runner.xcworkspace

Finally checked in the XCode the Project Navigator -> Pods -> Targets Support Files -> Pods Runner -> Pods-Runner-frameworks file and it now contains readlink -f in the row 44. I suppose the -f shouldn't be there.

I have same question😢.
MacOS big sur 11.7.6 with xcode 13.2.1.
mkdir -p /Users/Apple/Library/Developer/Xcode/DerivedData/Runner-cvmzclsfhrthrpcxtfbbfpvtascf/Build/Intermediates.noindex/ArchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/Runner.app/Frameworks
Symlinked...
readlink: illegal option -- f
usage: readlink [-n] [file ...]
Command PhaseScriptExecution failed with a nonzero exit code

So I did a test on a clean project in the same environment:

flutter create test
Added google_fonts: ^4.0.3 to the pubspec.yaml
Called flutter build ipa
Called open ios/Runner.xcworkspace

Finally checked in the XCode the Project Navigator -> Pods -> Targets Support Files -> Pods Runner -> Pods-Runner-frameworks file and it now contains readlink -f in the row 44. I suppose the -f shouldn't be there.
I also did another test and instead of the google_fonts package I added some random package (url_launcher) to the pubspec.yaml and the effect is exactly the same. After flutter build ipa the -f flag appears. flutter pub get before flutter build ipa has no effect on the flag appearance (the Pods section of the project is not yet created in the XCode).

Nice job. It work.

flutter create test
Added google_fonts: ^4.0.3 to the pubspec.yaml
Called flutter build ipa
Called open ios/Runner.xcworkspace

Finally checked in the XCode the Project Navigator -> Pods -> Targets Support Files -> Pods Runner -> Pods-Runner-frameworks file and it now contains readlink -f in the row 44. I suppose the -f shouldn't be there.

The -f is coming from CocoaPods, not Flutter. @rafaellop did you file an issue with them? I don't see one.

flutter create test
Added google_fonts: ^4.0.3 to the pubspec.yaml
I am on macOS 13.3.1 so I wasn't able to open Xcode 13.4, but I am using its toolchain on the command line to flutter build ipa.  I ran flutter build ipa --export-method development (because I don't have the bundle ID set up for the App Store) and it archived correctly.

I'm not sure what else we could do here other than bump the minimum Xcode version to 14.

I am going to bump the Flutter-enforced minimum version to Xcode 14.  If you're seeing this:

I strongly suggest filing an issue with CocoaPods with reproduction steps.

Ideally they would add a workaround to this on their side but I don't see a single issue actually reporting it, so they may not even know.


Cleanup useless files in top level

All are years behind current OpenBLAS, functional replacement is "just type make in top dir of source tree.

Not sure I see the point of removing the tiny quickbuild scripts, even if they do little more than invoke make (for some inexperienced user) ?

That inexperienced user would not want other bit-ness library on their system. GCC is not the ultimate build tool for windows, something usable of clang-cl/icl/ifort kind is better fit. Maybe cross-building paragraph could be enhanced with cross-building openblas.dll on linux, or then again Makefile.rule or both.

My preference would be to add to both documentation files.

I think quickbuild.32bit and quickbuild.64bit can be deleted, they are just clutter. Telling an user to run them is no easier than to tell them to run the single line command in those files. Also why does quickbuild.32bit have "-j 2" in it, when quickbuild.64bit does not have that? Seems inconsistent and pointless.
quickbuild.win32/64 could probably stay, as they have a link to the wiki in them.

That -j2 is plainly overridden (see Makefile.rule around MAKE_NB_JOBS)
Might be it hints to 2 threads for 1-core CPUs typical at times of gotoblas?

Patch is not used downstream https://src.fedoraproject.org/cgit/rpms/openblas.git/tree/openblas.spec

As noted above the patch is only needed on old Linux kernels from around ten years ago. It is linked in the FAQ and I think I saw it mentioned in issue tickets of at least one other project (cannot check now as my query "triggered an anti-abuse measure" on github for some reason).

Probably better off to some directory next to scavenged downstream patches one day.


Refactor needed to new client communication code

There's a problem with the communication model most recently adopted that limits the amount of information that can be given to a client for no good reason. The channel buffer size was placed in the code as an experimental placeholder but needs to be changed after analysis of typical loads, maximum anticipated loads, and also provide a better way to handle the channel getting full if possible.

Implemented a new strategy for handling slow clients that prevents needlessly dropping them but still makes most communications fast and efficient. Now, we send communication to the client's buffered channel whenever possible. If the channel fills up, we check to see if the client hasn't been responsive to pings for a cutoff number of seconds, and if so, we give up and abandon it to avoid infinite resource consumption on the server for a client that isn't able to keep up. However, if the client seems responsive but the channel is full, we fall back to a backup strategy of queuing up messages in the client's data structure. This is slower and more expensive, so we don't do this until needed. As soon as the channel drains, we fill it from the backlogged messages. When that drains out again, we're back to only using the buffered channel directly.
Initial testing indicates this works but will test a bit more before merging that fix into the main branch.


build: fix char signed vs unsigned warning

char defaults to signed on most x86 platforms, but unsigned on arm64. When targeting linux arm64 this produced a warning because character was always >= 0. This change circumvents this warning without changing behavior even though it seems pretty unreasonable to have a character less than 0 in this use case. Theoretically we could disable a warning flag instead but that differs between clang and gcc.
Fixes https://github.com/envoyproxy/envoy/issues/23569
Signed-off-by: Keith Smiley<EMAIL_ADDRESS>

The riskier approach would just be to drop the 0x00 comparison all together, I don't feel educated enough in the practical implications of that to make that without someone else who thinks that's safe 🙃

/retest


fix(gux-modal): added space around content slot

Closes https://inindca.atlassian.net/browse/COMUI-2690
I added 5px of padding to the right and left of the content slot. Doing this allows focusable elements to not be cut off on the left and right sides. I realize we could also ask the client to add spacing on their end instead of doing it inside the gux-modal component. Thoughts on adding spacing like I did and if so what kind of value makes sense? I feel like 5px is arbitrary. Should we use a token?

@jason-evans-genesys your change was changing the design (adding extra padding) so I had a quick look at how we could fix the issue without changing the design. It ended up easier to commit what I found than commenting it in the PR.

@jason-evans-genesys your change was changing the design (adding extra padding) so I had a quick look at how we could fix the issue without changing the design. It ended up easier to commit what I found than commenting it in the PR.

Thanks for your help! Your change works great. Tested it and seems to work.

@daragh-king-genesys Is this PR good to be approved now?


[GCP FileShare Support]  Implement Create Fileshare API for GCP Fileshare Driver

What type of PR is this?

/kind new feature

What this PR does / why we need it: This PR is needed to support File Share Creation for GCP cloud backend.
Which issue(s) this PR fixes:

Fixes #1076
Test Report Added?:

/kind TESTED

Test Report:

The following testing is done for Create File Share API for GCP cloud backend:

[x] Register Backend

[x] List Backend

[x] Create FileShare for GCP Backend

Register a Backend
Example 1: Registering an Azure Backend for File Share
POST http://<IP_ADDRESS>:8089/v1/94b280022d0c4401bcf3b0ea85870519/backends
Request:
{
  "name": "gcp-backend-file",
  "type": "gcp-file",
  "Region": "<project_id>",
  "Access": "<access_key>",
  "Security": "<secret_key>"
}

Response:
{
    "id": "5f66397740852a0001bcc3f7",
    "tenantId": "94b280022d0c4401bcf3b0ea85870519",
    "userId": "558057c4256545bd8a307c37464003c9",
    "name": "gcp-backend-file",
    "type": "gcp-file",
    "region": "<project_id>",
    "access": "<access_key>",
    "security": "<secret_key>"
}

List Backend:
GET http://<IP_ADDRESS>:8089/v1/94b280022d0c4401bcf3b0ea85870519/backends
Response:
{
    "backends": [
        {
            "id": "5f66397740852a0001bcc3f7",
            "tenantId": "94b280022d0c4401bcf3b0ea85870519",
            "userId": "558057c4256545bd8a307c37464003c9",
            "name": "gcp-backend-file",
            "type": "gcp-file",
            "region": "<project_id>"
        }
    ],
    "next": 1
}

Create a File share
Example 1: Creating File Share for AWS Backend
POST http://<IP_ADDRESS>:8089/v1/94b280022d0c4401bcf3b0ea85870519/file/shares
Request:
{
    "name": "gcpfshim",
    "description": "GCP FileShare",
    "backendId": "5f66397740852a0001bcc3f7",
    "availabilityZone": "asia-east1-a",
    "size":<PHONE_NUMBER>776,
    "type": "cloudFS",
    "tags": [
      {
        "key": "creator",
        "value": "himanshu"
      }
    ],
    "metadata": {
      "Tier": "STANDARD"
    }
}

Response:
{
    "id": "5f663ac22c7bc100019d2cd6",
    "createdAt": "2020-09-19T22:37:14",
    "updatedAt": "2020-09-19T22:37:14",
    "name": "gcpfshim",
    "description": "GCP FileShare",
    "tenantId": "94b280022d0c4401bcf3b0ea85870519",
    "userId": "558057c4256545bd8a307c37464003c9",
    "backendId": "5f66397740852a0001bcc3f7",
    "backend": "gcp-backend-file",
    "size":<PHONE_NUMBER>776,
    "type": "cloudFS",
    "region": "<project_id>",
    "availabilityZone": "asia-east1-a",
    "status": "creating",
    "tags": [
        {
            "key": "creator",
            "value": "himanshu"
        }
    ],
    "metadata": {
        "fields": {
            "Tier": {
                "Kind": {
                    "StringValue": "STANDARD"
                }
            }
        }
    }
}

Special notes for your reviewer:
Since GET Fileshare API for GCP implementation is not included in this PR. Sync Metadata from cloud to DB will break.

Please fix fs naming conventions

If we needs to take the instance name from User input. I can add instance id to metadata. What do you say?


Freeze when using recursive data annotations

I'm using a structure akin to, my code is of course a bit more involved but this is the basic idea
class Item extends Data {
  public function __construct(
    public int $item_id,
    public int $quantity,
    #[DataCollectionOf(Item::class)]
    public ?DataCollection $subItems) {}
}

As you can see, my Item optionally nests a collection of Items, but this freezes. The request simply times out.
Is it possible there's an accidental infinite loop in the code due to this annotation?

class Item extends Data {
  public function __construct(
    public int $item_id,
    public int $quantity,
    public ?Item $subItem) {}
}

This is also giving the same timeout. Looks like nesting same class gives you a timeout.

This is impossible because we cannot know how deep we should generate validation rules, I've added a section in the docs describing it: https://github.com/spatie/laravel-data/blob/b8a0efd9263fbff1da2466bdca9e50e346ba6e44/docs/as-a-data-transfer-object/request-to-data-object.md#L575

@rubenvanassche is this also impossible for a many to many relationship? I have an InvoiceData class which has a DataCollectionOf(TransactionData::class), and the TransactionData class also has a DataCollectionOf(InvoiceData::class).


Arrivals rotation issues

Since https://github.com/space-wizards/space-station-14/pull/17189 I think, pendingclockin isn't removed so your camera autorotates every time you walk off the shuttle instead of once which is very disorienting.

Trying to replicate this but getting very inconsistent results, haven't seen the rotation bug as you described but I can see PendingClockInComponent and AutoOrientComponent sometimes don't get removed when the shuttle departs if you walked off, but only sometimes. Is this still occurring?

AutoOrient is really bad and disorienting still a year on.


The whole tree is always parsed

In the function https://github.com/saalfeldlab/n5-universe/blob/b68a997a98abe9d88ca13c688cbbb6a826a0844b/src/main/java/org/janelia/saalfeldlab/n5/universe/N5MetadataUtils.java#L109 the argument parseWholeTree is ignored and the whole tree is always parsed.

https://github.com/saalfeldlab/n5-universe/commit/75a5866577c6f020b2fe2648f991fad336095bcb

closing since this is now released


RegularCachingInterpolant failing

I didn't find the reopen button for the old issue so I open a new issue here in case @ColmTalbot misses that.
Refer to https://github.com/ColmTalbot/cached_interpolation/issues/21#issuecomment-2394957382

In fact, I encountered this issue when doing joint cosmology fit when the source frame mass values depend on the cosmological parameters, that is, the evaluation points of interpolant vary during sampling process.

I don't currently guarantee that JAX compilation will work in this case. If you have an idea of how to make this work, I'm happy to see a PR.

I may not realize the real problem. Can I ask what the issue is for the jax compilation in this case? As I said, I did a quick test and the likelihood evaluation using cupy as backend (commit 2e38d87a43207625c1cb968215d25fed06220acf) and jit_likelihood using jax (commit 12fec0069dcdc3fcaaf6978e9c428c7857bf1210) seemed to return the same value. So I originally thought commit 12fec0069dcdc3fcaaf6978e9c428c7857bf1210 should be safe for jax implementation.


Username undefined in catalogue view

Latest develop in catalogue view might give "username" undefined.
It seems to work as "admin" user but normal user OR not logged in user gets empty catalogue page and client console log "username undefined.
Apologies, this is caused by my helper with insufficient error handling: https://github.com/apinf/api-umbrella-dashboard/blob/develop/apis/collection/backend.js#L781
TypeError: Cannot read property 'username' of undefined
    at http://localhost:3000/app/app.js?hash=1bab8dd88c2d06a5ae5f223f17745bd4afe72b1d:5596:42
    at Array.map (native)
    at Function._.map._.collect (http://localhost:3000/packages/underscore.js?hash=27b3d669b418de8577518760446467e6ff429b1e:167:56)
    at Document.getApiManagersByName (http://localhost:3000/app/app.js?hash=1bab8dd88c2d06a5ae5f223f17745bd4afe72b1d:5593:27)
    at http://localhost:3000/packages/spacebars.js?hash=65db8b6a8e3fca189b416de702967b1cb83d57d5:245:19
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?hash=65db8b6a8e3fca189b416de702967b1cb83d57d5:172:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?hash=65db8b6a8e3fca189b416de702967b1cb83d57d5:106:25)
    at Object.Spacebars.mustache (http://localhost:3000/packages/spacebars.js?hash=65db8b6a8e3fca189b416de702967b1cb83d57d5:110:39)
    at ._render (http://localhost:3000/app/app.js?hash=1bab8dd88c2d06a5ae5f223f17745bd4afe72b1d:32643:24)
    at doRender (http://localhost:3000/packages/blaze.js?hash=ef41aed769a8945fc99ac4954e8c9ec157a88cea:2027:25)

Update: did not occur with normal user in nightly as I checked out this morning. To be verified and checked later whether this was wrong call..

@jykae , verified on nightly.apinf.io : Sign in as anonymous user/regular user /API owner shows empty catalog page.

ok, thanks @saralavanip
Taking a look.

As part of this I may have found reason why @saralavanip Managed APIs disappear on nightly. I am getting on adding API backend: "insert failed: Access denied. No allow validators set on restricted collection for method 'insert'." Anyway, that somehow succeeds on the client minimongo and is visible on the client but on the server side Mongo allow/deny rules restrict the addition to persistent storage.

@saralavanip, please confirm.

Verified this resolved issue.
Findings:
@jykae , Info text for all APIs shown as 'added by admin' by default.


New look and feel, CSS framework, labels, checkboxes, example with saving custom parameters to flash memory

What's in this pull request:

Configuration portal got new look and feel. Works well on both small screen mobile devices and large screen laptops
Added a very small CSS framework based on mincss
Added the possibility of using labels. A labels will receive the text of the corresponding placeholder
Added option for label placement. WFM_NO_LABEL - label not displayed, WFM_LABEL_BEFORE - label displayed before field (default), WFM_LABEL_AFTER - label displayed after field. Latter is useful for checkboxes
Scan link was moved to the top, next to the SSID text so it will take less screen estate
All HTML description list elements were replaced by tables (eg. WiFi info page)
Removed break before each form parameter, CSS will take care of the spacing and custom HTML injection will be more useable
Renamed main menu options: Configure WiFi -> Configuration as WiFi is not the only option that can be configured, Info -> WiFi Information as the original text was too short and looked strange, Close configuration portal option -> Exit Portal as it was too long and was displayed in two lines on smaller devices
Added a working example that uses flash memory for storing custom parameters. String, integer and bool (checkbox) fields are demonstrated in the example

It's not my example but
kentaylor/WiFiManager/examples/AutoConnectWithFSParameters/AutoConnectWithFSParameters.ino
that fails Travis. Please consider removing it as we are not supposed to be using AutoConnect any longer.

Few screenshots:

Please fix the travis-ci failure.

Those screenshots look good. How about adding them to Readme.md

I really like the changed layout. The extra example is great too. Thanks for contributing these changes.

CSS looks nice and has minor Issues! Thanks for sharing and contributing

Hello @babacs, please let me know what issues you can see with the CSS. It is based on mincss with few small changes made. Thanks.

@kentaylor removed unnecessary example files and Travis is not failing anymore. Also made the changes you suggested. Let me if I should do anything else before the PR gets accepted. Thank you.


[feat] About the Dataset

Hello, thank you for your excellent contribution. Could you please upload the organized dataset used in the paper? This would make it easier to load the data in the code.

Hi @lixiang007666! thanks for reaching out! SaLIP performs adaptation entirely during inference, so there’s no specific organization to follow. Each of the respective dataset papers has been cited in the paper (go through those for details). You’ll need to download the datasets, select the official test set, and update thedata_path key in the config file with your local path to the dataset. I’m also including the links to each dataset here and in the repository for convenience.

CC359: https://www.ccdataset.com/download
Chest Xray Masks and Labels: https://www.kaggle.com/datasets/nikhilpandey360/chest-xray-masks-and-labels/data
HC https://zenodo.org/records/1327317


unexpected operator in preinstall.sh

./node_modules/sharp/preinstall.sh: 130: [: x86_64: unexpected operator

Hello, the preinstall script is no longer required on most 64-bit systems when using sharp v0.12.0+.
Is this Linux? Which flavour/version?

Ubuntu 14.10 here
On 03/04/16 19:56, Lovell Fuller wrote:

Hello, the preinstall script is no longer required on most 64-bit
systems when using sharp v0.12.0+.
Is this Linux? Which flavour/version?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/lovell/sharp/issues/392#issuecomment-204905230

--
Binary Kitchen
Michael Heuberger
1/33 Parrish Road
Sandringham
Auckland 1025
(New Zealand)
Mobile (text only) ...  +64 21 261 89 81
Email<EMAIL_ADDRESS>Website ..............  http://www.binarykitchen.com

Thanks, assuming you're using sharp v0.12.0 or later, you won't need to run the preinstall script. We should probably stop publishing it to npm.

yep using latest sharp here. but beware that i install it with the --ignore-scripts option, check in all node modules except the binaries into my private repo and call npm rebuild upon deployment.

sharp does not run preinstall.sh at install or rebuild time (and has never done so due to the sudo/root privilege requirement). Could something else be attempt to run it on your system/app?

i see ... and suddenly i cannot reproduce the above anymore. very weird. feel free to close this ticket then.
but i had to run that bash script manually because my libvips version was outdated before (was v7) and sharp didn't complain!