URL in Event Label

Hi Dan,
Is there a way to modify the code so that the full URL is pulled into GA as the Event Label? I'm seeing a truncated URL - only the end is displayed as the Event Label.
Thanks for this plugin! We've installed many ga scroll plugins and tags, and this is the only one that has displayed data in GA.
Thanks,
Sarah

Hi Sarah,
If you're using GTM, you can just change the GA Event Tag - if you're using hard-coded Analytics, there's a config value for that:
https://github.com/lunametrics/gascroll#label
Dan


CU-86a0xmx9x - Include IBls12381 interface to interact with ZeroKnowl…

Task linked: CU-86a0xmx9x Include IBls12381 interface to interact with ZeroKnowledge CryptoLib methods

Task linked: CU-86a0xmx9x Include IBls12381 interface to interact with ZeroKnowledge CryptoLib methods

coverage: 90.907% (+0.01%) from 90.893% when pulling ae2adf54f3906d12e8370f6670736563e297ddf2 on CU-86a0xmx9x into d29b770cfa5535d4e47c572a2ff54850545e1a84 on development.


How to make signals trigger subscriptions across multiple dynos/schedulers

First of, I LOVE your library and have been able to perfectly implement it in my project.  I have been planning on scaling up though and am having some thoughts on signals originating from multiple cpus/dynos or perhaps even firing them from a scheduler.  Is there a way to have signals trigger subscriptions as per the aforementioned requirements?  I was thinking of firing them across channels, but it seems rather complicated and I am still fairly new to python.
What are your thoughts?  Help is greatly appreciated.  Thank you in advance!

Hey @mukluk! Awesome, glad you like it 😊
graphene-subscriptions actually handles sending events to multiple app instances using Channel Layers automatically. If you use the built-in post_save_subscription and post_delete_subscription signals, an event will be sent via Channel Layers so that all instances with active Subscription connections receive it and send the data to the client. If you're using Custom Events this is also handled automatically.
Does that help?

Thank you so much for the quick response.
That's good to know.  I was running a Heroku Scheduler to run some updating tasks and the signals weren't triggering graphene-subscriptions, so I assumed that they weren't being sent over channels, but this may be a separate issue.


fix: Removed Copyright from generated code

#minor
https://github.com/microsoft/BotBuilder-Samples/issues/2625

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 84.124%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
20332

Relevant Lines:
22880

💛  - Coveralls


Apparent off-by-one error for extract method rename

See extract-method14.ts.
Ref: https://github.com/Microsoft/TypeScript/pull/18050#discussion_r137904326

@mhegazy Since this was just a problem with our tests I don't think it needs a release-2.5 port.

it should be fine to not port it.


Set elevation of Riders

As an Improvement on #27, it would be cool if the module would also set the actual elevation of the rider to that height

I am not quite sure what you mean. Currently the module should set the riders elevation to the ridden tokens elevation + the ridden tokens riding height (if set the one configured in the token settings). Or do you mean the Wall-Height/Levels elevation?

Those are the same elevation, and it seems like it doesnt set it, until you mount another token, then the previously mounted tokens get their elevation set, but as soon as the mount moves, the elevation gets reset back to 0

So when you set a Custom riding height, the mounted tokens elevation gets set to zero once you move the mount? If so, that is bug, probably caused by an incompatibility with another module. Does it also happen when no other modules are active? If not, what other modules are you using?

Ok, i did two find the culprit, both came out with blaming incorrect modules, but i did some manual testing, and it seems it elevated vision setting the tokens back to ground height

Thanks for informing me, i will look into it and see if i can find a solution, could take a while tho since this bug will probably have to be solve by both Rideable and elevated vision

I can no longer reproduce the bug. I will therefore assume this issue to be solved unless i hear otherwise and will probably close this issue soon.

I can still, as long as the terrain elevation is different from 0

Which version of Elevated vision are you using?

Which version of Elevated vision are you using?

0.5.9


What's file tracking got to do with msbuild?

It's entirely unclear how this relates to msbuild or how to use it when writing msbuild files. The examples are in C++.

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

ID: 401f8953-3165-194b-3706-92336a5a93e1
Version Independent ID: 1b4ee143-9b5e-58fe-f82e-6614f36b8113
Content: File Tracking - Visual Studio
Content Source: docs/msbuild/file-tracking.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

https://stackoverflow.com/questions/27960893/how-to-implement-msbuild-file-tracking-feature-tracker-exe-for-a-not-native-vc - related StackOverflow question

Well this is not fixed as such. The link from @ghogen shed some light on it, but I still think the page I linked to, which is named "File Tracking - Overview", could contain at least one or two sentences to explain why or when it is useful.


Stop recording/streaming when disabled

wyoming-satellite continuous recording and streaming, even when it is disabled by the satellite_enabled HA switch (it seems to me that the satellite is not even aware of the flag, although I only had a quick look at the code). It would be preferable to stop recording and remain completely idle, to save network/CPU resources, but also free the sound devices for other uses (in case of ALSA).
A simple solution could be to just disconnect from the satellite. But it might be useful to always maintain a connection for other features, in which case we could add a StopSatellite event or something like that.
PS. wyoming-satellite seems awesome, I like the modular design.

Thanks! HA should disconnect now, but I have to test this more. I agree that streaming satellites could conserve resources when no server is connected, but I'd expect most people to use VAD or local wake word detection so it may not get used much.
One option is to do for microphone services what I already do for sound services: send AudioStart and AudioStop messages. So for mic services, AudioStop would tell the service to stop recording but keep the connection alive. And AudioStart would resume it.
P.S. Thanks again for all the great work you did on HA satellite! I think we could move a lot of the pulseaudio code into a combined mic/snd service that does ducking and echo cancellation. What do you think?


Write to log file instead in case backendless cannot be reached

https://github.com/aeternity/token-burn-listener/blob/eb171d8d7ed6f1c09053a140c4ed858359509e34/server.js#L157
If this is the production code, we should definitely add a logfile write at this point, or else the missed event will will go completely unnoticed.

A file for logging is of no use because of our deployment setup. We would have no convenient way to gather it.
I propose to use Sentry.io. I just set up an account, send you an invite and create a PR soon for the integration.

fixed by #10


Why is nebula-client in this repo inconsistent with crates.io?

General Question

I tried to run code in demos/tokio/src/v3_graph_client.rs in my new project, and I wrote Cargo.toml as follows:
[package]
name = "test-nebula-rust"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
# non-pool
fbthrift-transport = { version = "0.9", features = ["impl_tokio"] }
nebula-client = { version = "0.7.3", features = ["graph", "storage", "meta"] }

# bb8
bb8 = { version = "0.8" }
bb8-nebula = { version = "0.9", features = ["graph"] }

# common
tokio = { version = "1", features = ["macros", "rt-multi-thread"] }

When I run cargo run <IP_ADDRESS> 9669 root 'password', it raised an error: Error: DataDeserializeError(DataDeserializeError { field: None, kind: Custom("missing field HTTP port") }).
I found that in this repo, the code in nebula-client/src/v3/graph/client.rs is written like this:
const STMT_SHOW_HOSTS: &[u8] = b"SHOW HOSTS;";
#[derive(Deserialize, Debug)]
pub struct Host {
    #[serde(rename(deserialize = "Host"))]
    pub host: String,
    #[serde(rename(deserialize = "Port"))]
    pub port: u16,
    // #[serde(rename(deserialize = "HTTP port"))]
    // pub http_port: u16,
    #[serde(rename(deserialize = "Status"))]
    pub status: String,
    #[serde(rename(deserialize = "Leader count"))]
    pub leader_count: u64,
    #[serde(rename(deserialize = "Leader distribution"))]
    pub leader_distribution: String,
    #[serde(rename(deserialize = "Partition distribution"))]
    pub partition_distribution: String,
    #[serde(rename(deserialize = "Version"))]
    pub version: String,
}

And in crates.io code is like this:
const STMT_SHOW_HOSTS: &[u8] = b"SHOW HOSTS;";
#[derive(Deserialize, Debug)]
pub struct Host {
    #[serde(rename(deserialize = "Host"))]
    pub host: String,
    #[serde(rename(deserialize = "Port"))]
    pub port: u16,
    #[serde(rename(deserialize = "HTTP port"))]
    pub http_port: u16,
    #[serde(rename(deserialize = "Status"))]
    pub status: String,
    #[serde(rename(deserialize = "Leader count"))]
    pub leader_count: u64,
    #[serde(rename(deserialize = "Leader distribution"))]
    pub leader_distribution: String,
    #[serde(rename(deserialize = "Partition distribution"))]
    pub partition_distribution: String,
    #[serde(rename(deserialize = "Version"))]
    pub version: String,
}

After I commented http_port, the code can run successfully.
So why is the code in this repo inconsistent with crates.io? What is this http_port used for? Can it be deleted?

I noticed nebula-client in crates.io was published by vkill, what's the relationship between github.com/bk-rs/nebula-rs and this repo? I wanna do some work for nebula-client, what should I do?

I believe the correct one is nebula-client/src/v3/graph/client.rs, because it is the same with result of "show hosts".

the http port looks like useless, you can delete it.

the http port looks like useless, you can delete it. For nebula client in crates.io, maybe there's a extra useless field http port in old version.

Thanks for your reply. I got it. So do you know which repo should I contribute for?
I wanna add result set for nebula-client, just like nebula-go and nebula-python do. If I contribute for vesoft-inc/nebula-rust, will these changes be updated in crates.io?

You can submit some pull requests for repo https://github.com/vesoft-inc/nebula-rust, It's very welcome~~~
When we deploy the nebula-rust with new version, the changes will be updated to crates.io.

It's good.


[DOCFIX] update inline snippets in docs/cn/Running-Alluxio-on-GCE.md

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/19244/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/19384/
Test PASSed.


Install conflict with ember-cli-list-view

Reference #7 for an install conflict with ember-cli-list-view.

Unable to reproduce issue. closing for now.


Refactor: Sets instead of arrays

#250 but for the right base branch. Refactor useProps.ts to utilize Set and its .has() method over array with its .includes() method. Set has a better time complexity, make this a small performance gain.

Awesome, thanks!


blank white screen in android demo

Describe the bug
running the demo brings a blank white screen on android studio
To Reproduce
Steps to reproduce the behavior:
1Just Follow the setup from the README
Expected behavior
Maybe a demo on the the video recording works

@undextrois Please try version 5.0.2 or above

@undextrois, I think the demo app does not take care of requesting video permissions, you'll need to manually enable these permissions by going into the settings for the app and enabling camera and mic permissions.
Please feel free to add this functionality to the demo app and PR back here :)


API protection messing with array splice

See #1459 over on CodeCombat.

Fixed with @basicer's new Esper interpreter.


Support browsers option

Autoprefixer Rails supports a browsers option.
Would be great if we could add something like this is _config.xml:
autoprefixer:
  flexbox: no-2009
  browsers:
    - "> 1%"
    - "last 2 versions"
    - "IE > 8"

seconded!

would love to see this option

I just released 2.0.1; Now autoprefixer from _config.yml will pass options to the processor. 🍻

amazing! thanks @imathis


mvcc: Introduce sample step for MVCC scanner

Signed-off-by: iosmanthus<EMAIL_ADDRESS>What problem does this PR solve?
This pull request enables MVCC scanner to take a sample from keys/values while bypassing sample_step - 1 keys between two continuous keys and ignore all locks (i.e. applies a read committed isolation). If sample_step is 0, sampling is disabled.
Problem Summary:
What's Changed:
Check List
Tests

Unit test
Integration test

Release note

Introduce sample step for MVCC scanner

@breeswish @MyonKeminta PTAL

Could you add a unit test for scanning with sample_step?

Done

@sticnarf PTAL

/merge


DBT parser support macro-bsed DBT projects for column-level lineage

https://openmetadata.slack.com/archives/C02B6955S4S/p1669367705377959?thread_ts=1669221137.283589&cid=C02B6955S4S
Neither compiled_sql or compiled_code is present only macro_sql

@geoHeil what version of DBT are you using?

1.3.1

done in https://github.com/reata/sqllineage/pull/397


Custom Layout Keys

An extra option to allow another key than 'layout' for the layouts.
May be handy in some contexts.
Fot exmaple: When you use handlebars-layouts, the term 'layout' gets confusing in your files...

Hi @vale981, thanks for the pr and the work, but I'm not willing to implement this. I understand what you're trying to do here, but I think that this usecase isn't common enough for me to want to support it.
However, the changes outlined for v2 (custom engines) should allow you to easily implement this yourself without having to submit a pr for this lib. Apologies for the late reply, and hope you understand!


Rewrite tests, add CI, Coverage and create UMD for browser

Hi @Sembiance . I am willing to rewrite tests for this library with mocha, and travis ci and create Universal Module Definition for consuming this module in browser. Just want to confirm if i can work as there is not changes made in this module since aug 2017.
Thanks :).

CC : @Sembiance  I have updated the tests. refer #25

So I don't have much time now a days to maintain this module.
Would you like to take it over? I could transfer the github repo to you and also make you the owner of the NPM package.
If so, shoot me an e-mail<EMAIL_ADDRESS>with what NPM username you want me to assign the the module to.


Removed the http4client.retain_max_body_size property mentions

Description
I've removed the http4client.retain_max_body_size  property mentions from documentation and jmeter.properties file.
Motivation and Context
The property is not used anymore and just confuses users.
How Has This Been Tested?
No need to test, only text files modified`
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the [code style][style-guide] of this project.
[x] I have updated the documentation accordingly.

@pmouawad , I see the property was removed in 97cc6f440b0698d360708218f847ea792ff9ff24
Do you think it should be completely removed or should it be re-implemented somehow?

@pmouawad , I see the property was removed in 97cc6f4
Do you think it should be completely removed or should it be re-implemented somehow?

I would prefer to have it re-implemented somehow


Multiline XML Comments are not represented ok

Describe the bug
I Have my API with some xml documentation:

But while generating the .html file, some comments are not commented:

Generating a send request where it should not be any.
These XML documentation is a must have because it explains the endpoint in the docs.

@blogcraft This should be trivial to fix. Thanks for reporting this. I haven't gotten around to hunting for edge cases as I mostly focused on my own needs for the tool


Doc.lineOrSep?

I've been using this library to pretty print ASTs for a little toy programming language and it's great! Thanks for your work on this.
However, I was wondering if there is a way to use an optional separator character other than a single space when a doc is flattened.
e.g.
val imps = Doc.intercalate(Doc.char(';') + Doc.line, imports.map {
  case ImportModule(pkg, name) =>
    Doc.text("import ") + Doc.text((pkg :+ name).mkString("."))
  case ImportSymbols(pkg, name, syms) =>
    val impPrefix = Doc.text("import ") + Doc.text((pkg :+ name).mkString(".")) + Doc.char('.') + Doc.char('{')
    val impSuffix = Doc.char('}')
    val impBody = Doc.intercalate(Doc.comma + Doc.line, syms.map(Doc.text))
    impBody.bracketBy(impPrefix, impSuffix)
})

results in:
  import mpj6.{ dM };
  import oz4.nckur.ctsq.me5.lgG.cn;
  import kmF1.vu.ehy.yplf

I only really want the semicolon to be added when the Doc is flattened. Is there a good way to do that already that I have missed?

It's not possible on master at this time.  However, we have some PRs in the works that would allow that.  For example, #117's FlatAlt constructor is how the feature you are looking for is supported in the Haskell implementation.  It's not actually exposed to callers in #117, but we could easily do so now that there's a feature request!
We don't expose it now because some data-structure invariants we maintain will be broken by arbitrary flattened-alternatives, but since it's used in other libraries, I would think it's definitely something we can support.

That'd be great, I'll keep an eye out for #117 landing in master 👍

I have not used flatten for anything yet so so far, no :)


Website is down: https://www.react-toolbox.io/

I just checked this out and it seems the deployment wasn't successful Please have a look. Thanks

Website is down again today


NineSlice.size returns null

There does not seem to be a getter for NineSlice size property. This feels like its inconsistent with the rest of the Visual stuff in Luxe.

Visual.size is a misnomer in general, it should be on the Sprite level, and will find it's way down there. NineSlice could have a getter though, as it does fit it's purpose and already has the setter.


New billing structure backend followup

Closed in favor of https://github.com/zulip/zulip/pull/9931


pragha: 1.3.4 -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/pragha-music-player/pragha/releases.
meta.description for pragha is: "A lightweight GTK+ music manager - fork of Consonance Music Manager"
meta.homepage for pragha is: "https://pragha-music-player.github.io/"
meta.changelog for pragha is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found <IP_ADDRESS> with grep in /nix/store/isp3ca6n83s313lwmv023y8rdqdq0lmm-pragha-<IP_ADDRESS>

directory tree listing: https://gist.github.com/247767497bcff9a013887217e67aa681

du listing: https://gist.github.com/6c3f25ae7659b1bdf82410354dfda56d

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
pragha

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/isp3ca6n83s313lwmv023y8rdqdq0lmm-pragha-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pragha https://github.com/r-ryantm/nixpkgs/archive/73494c7c9f168a1304c23b2c9625acba6364d021.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/isp3ca6n83s313lwmv023y8rdqdq0lmm-pragha-<IP_ADDRESS>
ls -la /nix/store/isp3ca6n83s313lwmv023y8rdqdq0lmm-pragha-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pragha

Maintainer pings
cc @mbaeten for testing.

@mbaeten the version number looks suspicious. Is it a development release?

@ryantm It's a release candidate (RC2). Since the player doesn't seem to be in active development anymore, I think this is as far as we can get. Tested it on my computer and it works well. No crashes or anything.


ReadBoolean encountered non-boolean value

I'm having some issues decompiling a bytecode file, if anyone could have a look into why this happens :-)
[11:08:43 DBG] Reading 22 strings from the string table
[11:08:43 DBG] Reading 4 functions from main bytecode pool
[11:08:43 DBG] Reading basic function prototype information
[11:08:43 DBG] Reading 2 instructions from function prototype body
[11:08:43 WRN] Encountered unexpected NOP instruction.
[11:08:43 DBG] Reading 0 constants from function prototype body
[11:08:43 FTL] Unexpected error; please report here: https://github.com/atrexus/unluau/issues
System.IO.InvalidDataException: ReadBoolean encountered non-boolean value: 0x02
   at Unluau.BytecodeReader.ReadBoolean() in C:\tmp\unluau\src\Unluau\Deserializer\Reader\BytecodeReader.cs:line 61
   at Unluau.Deserializer.ReadLineInfo(Int32 instructions) in C:\tmp\unluau\src\Unluau\Deserializer\Deserializer.cs:line 252
   at Unluau.Deserializer.ReadFunction(IList`1 functions, IList`1 strings) in C:\tmp\unluau\src\Unluau\Deserializer\Deserializer.cs:line 138
   at Unluau.Deserializer.ReadFunctions(IList`1 strings) in C:\tmp\unluau\src\Unluau\Deserializer\Deserializer.cs:line 94
   at Unluau.Deserializer.Deserialize() in C:\tmp\unluau\src\Unluau\Deserializer\Deserializer.cs:line 42
   at Unluau.Decompiler..ctor(Stream stream, DecompilerOptions options) in C:\tmp\unluau\src\Unluau\Decompiler.cs:line 39
   at Unluau.CLI.Program.RunOptions(Options options) in C:\tmp\unluau\src\Unluau.CLI\Program.cs:line 114

Example file:
bytecode_file.zip

I see we are trying to do the same thing and are running into the same issue :D . Honestly, I think there might already be an issue with the proper string decoding. Sadly this is not as advanced as LuaJIT was.

A bit of progress, if you remove the first byte in this file it works :-)
However some files produce errors, e.g from file attached:
...
[10:32:20 DBG] Reading 64 constants from function prototype body
[10:32:20 DBG] Line information is enabled, reading.
[10:32:20 DBG] Debug information is enabled, reading.
[10:32:20 WRN] Encountered unhandled code FASTCALL1, skipping
[10:32:20 WRN] Encountered unhandled code FASTCALL2, skipping
[10:32:20 WRN] Encountered unhandled code FASTCALL1, skipping
[10:32:20 FTL] Unexpected error; please report here: https://github.com/atrexus/unluau/issues
System.NullReferenceException: Object reference not set to an instance of an object.
   at Unluau.NameIndex.GetNames() in C:\tmp\unluau\src\Unluau\Lifter\Expressions\NameIndex.cs:line 33
   at Unluau.LocalExpression.GetNames() in C:\tmp\unluau\src\Unluau\Lifter\Expressions\LocalExpression.cs:line 43
   at Unluau.NameIndex.GetNames() in C:\tmp\unluau\src\Unluau\Lifter\Expressions\NameIndex.cs:line 33
   at Unluau.FunctionCall.GetNames() in C:\tmp\unluau\src\Unluau\Lifter\Expressions\FunctionCall.cs:line 58
   at Unluau.Namer.getName(Expression expression) in C:\tmp\unluau\src\Unluau\Lifter\Namer.cs:line 82
   at Unluau.Namer.createNamedDecleration(Int32 register, Expression expression, Block block, DeclerationType type) in C:\tmp\unluau\src\Unluau\Lifter\Namer.cs:line 65
   at Unluau.Namer.CreateDecleration(Int32 register, Expression expression, Block block, DeclerationType type, Boolean isRegular) in C:\tmp\unluau\src\Unluau\Lifter\Namer.cs:line 34
   at Unluau.Registers.LoadTempRegister(Int32 register, Expression expression, Block block, DeclerationType type) in C:\tmp\unluau\src\Unluau\Lifter\Registers.cs:line 62
   at Unluau.Lifter.LiftBlock(Function function, Registers registers, Int32 pcStart, Int32 pcStop) in C:\tmp\unluau\src\Unluau\Lifter\Lifter.cs:line 203
   at Unluau.Lifter.LiftBlock(Function function, Registers registers, Int32 pcStart, Int32 pcStop) in C:\tmp\unluau\src\Unluau\Lifter\Lifter.cs:line 552
   at Unluau.Lifter.LiftProgram() in C:\tmp\unluau\src\Unluau\Lifter\Lifter.cs:line 38
   at Unluau.Decompiler.Decompile() in C:\tmp\unluau\src\Unluau\Decompiler.cs:line 48
   at Unluau.CLI.Program.RunOptions(Options options) in C:\tmp\unluau\src\Unluau.CLI\Program.cs:line 119

bytecode_file_2.zip

But you have seen that the first byte in the file will tell you the version of the luau, so remove is a little bit useless, or?

The game .exe uses both first and second byte to deduce bytecode version, the decompiler does only need the 2nd byte

As a side note, the v2.0.0-beta branch does successfully disassemble the files I've tested with so far without any errors :-)
Though it does not generate any Luau code (yet)

The game .exe uses both first and second byte to deduce bytecode version, the decompiler does only need the 2nd byte

The decompiler in source code use definetly the first byte to make sure it is a min version 3.
This is checked in the first read operation ;)

Yes, I'm not talking about the decompiler .exe but the .exe that actually uses these files :-)

I get it with the 2 to work with a small change, but I assume there is not create of readably lua code yet. Perhaps @atrexus could give the answer there, because I only can use it with disassemble option currently

When I check the docs both bytes should be there. V4 just has that additional byte for TypeVersion.
I think that the handling for the typeversion in the "old" compiler breaks some offset or something.
I'm gonna check the 2.0.0 beta as well, I think using an AST is how ljd did it as well, so maybe adding a decompiler onto the AST can learn from that.

As a side note, the v2.0.0-beta branch does successfully disassemble the files I've tested with so far without any errors :-) Though it does not generate any Luau code (yet)

I had to disable the TypedVersion check on the 2.0.0 as well to get anything useful? I don't really understand why though.

Okay, so these are error messages from the GAME .exe when modifying the 2 first bytes of unencoded bytecode:
0x02 0xEE = "bytecode version mismatch (expected [3..4], got 2)"
0x02 0xEF = 3
0x02 0xF0 = 4
0x02 0xF1 = "bytecode version mismatch (expected [3..4], got 5)"

0x01 0xEF = "bytecode version mismatch (expected [3..4], got 239)"
0x03 0xEF = "bytecode version mismatch (expected [3..4], got 245)"

Alright, I got the disassembly working now when skipping the user type evaluation and after adding proper handling for loops so the graph logic didn't die, but I can see where the loop loops.
Next I will try to make the graph load/show referenced values instead of the addresses. I think that's a sensible step towards generating a code output.

recompile it and see if it works. Tampering with the bytecode is not a great solution.


make it possible to pass additional options to create_engine

I needed to pass in an isolation_level parameters to the create_engine call. I did it like this:
https://github.com/gromgull/flask-sqlalchemy/commit/689c90c48949dc4c020f16550576c517d2fb5230
(on top of the 1.0 tag since that's what we used, but I can make a pull-request with it applied to HEAD if you want)

@immunda any update on this? we need to pass in a custom json json_serializer and need a way to specify/override engine_options, https://github.com/mitsuhiko/flask-sqlalchemy/pull/67/files looks good to me, any reason not to use that patch?

This isn't going to be in the release 2.1 (very soon). However, it should definitely be addressed in v3.
@jayzeng It's not a problem with that commit per se, but there's a lot of details to sort out around documentation changes, tests and then managing the deprecation of options which such a solution would essentially override/render redundant.

Completely understood. It is a pressing issue for us and I think we will just go for the subclass route.
@immunda any rough estimate when v3 will be released?

Also let me know what I can help to get it released asap

I'm also interested in some way to do this.  I need to pass a custom connection function, and right now have to do some monkey patching around to get there.
Is there any value in working on or submitting a proposed fix at this point?

+1 here too, in order to pass a custom json_serializer.

This really needs to be fixed.  It could be easily done by accepting a SQLALCHEMY_ENGINE_OPTS config value that is a dict and that would be merged into the options before being sent to create_engine().  That seems preferable to the implementation in #431 IMO.
This could literally be a two line change:
            options = {'convert_unicode': True}
            self._sa.apply_pool_defaults(self._app, options)
            self._sa.apply_driver_hacks(self._app, info, options)
            if echo:
                options['echo'] = echo

            # next two lines are new
            config_engine_opts = self._app.config.get('SQLALCHEMY_ENGINE_OPTS', {})
            options.update(config_engine_opts)

            self._engine = rv = sqlalchemy.create_engine(info, **options)

Or, go slightly more customizable, and put those two lines in a new method SQLAlchemy.apply_engine_defaults() so that it can be easily overridden.
@davidism or @immunda would you accept a PR with this approach?

@davidism @immunda - Bump.
A response would be great re: whether or not a PR with @rsyring's approach would be accepted.
My particular use-case has to do with disconnect handling.

There's already a PR open: #487. We will get to it when we have time available. No need to ping us, we're still aware of open issues.

FWIW, SQLAlchemy 1.2 is coming out with a new method of detecting connections in the pool that are no longer valid:
https://docs.sqlalchemy.org/en/latest/core/pooling.html#pool-disconnects-pessimistic
We really want to use that and without this issue getting resolved, it is going to be much harder to do so.
This can be a two line change, as demonstrated above.  I'll write the PR, I just want someone to tell me before I make the effort that my approach will work.

I second this. I need it for using sqlite in memory databases with unittesting, i.e.: http://www.sameratiani.com/2013/09/17/flask-unittests-with-in-memory-sqlite.html

I'll third this. This functionality would be super useful.

Please use the reaction buttons to vote on issues.

If anyone working on this project is a consultant, I'd be happy to hire you to get this issue resolved.  Please contact me directly regarding.  Thanks.

I would like to see @rsyring's solution implemented. In the meantime, we've opted to move forward with the following approach: https://github.com/mitsuhiko/flask-sqlalchemy/issues/589#issuecomment-361075700
The subclassing approach is the same solution that @gilbsgilbs has referred to when closing the following related Issue: https://github.com/mitsuhiko/flask-sqlalchemy/pull/577

You cannot love enough open source.
Adding two lines of code high demand issue sits idle for several years.
And the only comment made by the author is: "We will get to it when we have time available".
If you don't have the available time, maybe it's time to pass the torch to someone else.
(Appreciate the initial contribution, really! but this is just painful to watch)

@gdoron The problem is not that people don't want to pass the torch. The problem is that there are not enough people available for maintenance.
As an Open Source maintainer myself (not on this one), I can assure you that there are almost no people consistently contributing to projects over years. Most people do one or two pull requests and then leave. Adding additional maintainers is therefore not a question of giving up responsibility, but rather finding the right people.
The only person that actually tried to solve something here was @rsyring, because he offered to pay something.
If you actually cared about this project enough, you would either solve this problem with a new competing project that cleans up a lot of the issues that are part of this one or start to work with the issue tracker/pull requests of this one and lend a helping hand until you become a maintainer yourself. That is how it works and how everyone benefits from Open Source. You are also a part of this world and you can help to improve it :)

@davidhalter

If you actually cared about this project enough, you would either solve this problem with a new competing project that cleans up a lot of the issues that are part of this one or start to work with the issue tracker/pull requests of this one and lend a helping hand until you become a maintainer yourself.

There are already too many PRs opened, creating new ones won't help.
I think finding other maintainers to join is harder when you let their issues and Pull-Requests sit idle for years.
I don't actually care enough about this project, I'm only using it in a private project to learn Flask.
I know I don't have the right to complain, but as I wrote, it's just painful to watch.

Per (https://github.com/pallets/flask-sqlalchemy/pull/540#issuecomment-470643872), I'll be opening a PR shortly (unless someone beats me to it) that:

Let's you configure the engine from config options: SQLALCHEMY_ENGINE_OPTIONS
Lets you configure the engine from engine_options in: https://github.com/pallets/flask-sqlalchemy/blob/500e732dd1b975a56ab06a46bd1a20a21e682262/flask_sqlalchemy/init.py#L675

After some additional though, I'm also think it would make sense to Adjust _EngineConnector https://github.com/pallets/flask-sqlalchemy/blob/500e732dd1b975a56ab06a46bd1a20a21e682262/flask_sqlalchemy/__init__.py#L532 to have a def get_options() and def create_engine() so that if the options above are insufficient for some reason, it's relatively easy to create the engine however you want it created.  In this case, I also think we should drop _ from EngineConnector so signal it's ok to inherit and customize.  It make sense to me to do it this way, but I guess we can see if that flies during the PR review.


Build wheels as py3-none-{platform}.

Fixes https://github.com/pyocd/libusb-package/issues/18
Based on https://github.com/joerick/python-ctypes-package-sample
CI job from my fork: https://github.com/carlosperate/libusb-package/actions/runs/6981684546

Seems to be working, but I would need to test it. Same question as https://github.com/pyocd/libusb-package/pull/17#issuecomment-1825023697, what would be the best way to test the wheels? Installing them in a virtual environemnt and running the test.py file?

A nice benefit is that it only needs to build the wheel once (cibuildwheel starts at the lowest Python version, so 3.7) and then skips building it for the next environments. This reduces the Ubuntu build time from 1h to 10min.
Once we have something like PR https://github.com/pyocd/libusb-package/pull/21 set up, the test step wouldl still run on each environment, always using the wheel built on the first one.


Add tags to tasks

Allows the user to add tags to the tasks.
The user can add whatever tags they like. These tags allow the user to identify tasks that are similar.
Tags will be optional, similar to how due dates work.

[ ] create new method add_tag
[ ] modify the choice list

I love this feature!


Scan kubernetes/kubernetes with govulncheck

Background: Today we have scanning implemented using snyk. It has worked quite well with addition of some smart optimization to reduce false positives.
Go team recently released https://go.dev/blog/govulncheck v1.0.0. It promises to provide prioritized vulnerability scanning for CVEs that affect the functions that the code is calling. This is promising in terms of having a really really low false positive since most vulnerability scan reports are in general notoriously hard to wrangle.
Usecases: We have three real workflows for injecting this type of scanning:

On k/k PRs: Create a diff between vulnerability scan report run on master branch and the one run on HEAD (current) branch. If the diff is non-zero, fail the pre-merge test. This can be run on symbol and module level depending on context of the PR
On k/k master periodically: Run every few hours to get a sense of vulnerability impact for tip of the contributions
On k/k release branches: Run every few hours to get a sense of vulnerability impact for release branches so cherry-picks can be created as needed

Tasklist

[x] https://github.com/kubernetes/sig-security/issues/99
[ ] https://github.com/kubernetes/sig-security/issues/100

How it works
Example output on August 4 2023
demo$ govulncheck ./...
Using go1.20.6 and<EMAIL_ADDRESS>with vulnerability data from https://vuln.go.dev (last modified 2023-08-02 20:33:39 +0000 UTC).

Scanning your code and 1968 packages across 204 dependent modules for known vulnerabilities...

Vulnerability #1: GO-2023-1987
    Large RSA keys can cause high CPU usage in crypto/tls
  More info: https://pkg.go.dev/vuln/GO-2023-1987
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>    Example traces found:
      #1: pkg/kubelet/server/server.go:234:24: server.ListenAndServePodResources calls grpc.Server.Serve, which eventually calls tls.Conn.Handshake
      #2: pkg/proxy/healthcheck/proxier_health.go:179:24: healthcheck.proxierHealthServer.Run calls http.Server.Serve, which eventually calls tls.Conn.HandshakeContext
      #3: test/e2e/framework/network/utils.go:1026:25: network.PokeHTTP calls io.ReadAll, which calls tls.Conn.Read
      #4: cmd/kubeadm/app/preflight/checks.go:544:13: preflight.SystemVerificationCheck.Check calls bufio.Writer.Flush, which calls tls.Conn.Write
      #5: test/utils/apiserver/testapiserver.go:73:59: apiserver.writeKubeConfigForWardleServerToKASConnection calls cert.GetServingCertificatesForURL, which eventually calls tls.Dial
      #6: test/e2e/framework/websocket/websocket_util.go:61:29: websocket.OpenWebSocketForURL calls websocket.DialConfig, which eventually calls tls.DialWithDialer
      #7: test/images/agnhost/inclusterclient/main.go:100:24: inclusterclient.debugRt.RoundTrip calls spdy.SpdyRoundTripper.RoundTrip, which eventually calls tls.Dialer.DialContext

=== Informational ===

Found 1 vulnerability in packages that you import, but there are no call
stacks leading to the use of this vulnerability. You may not need to
take any action. See https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
for details.

Some more examples from @liggitt https://gist.github.com/liggitt/4674c7eb194738989183abf08feb333f
Open Questions:
These questions need to be discussed and reached a consensus on amongst K8s SRC, SIG Architecture, Release and Security

Do we make the scan results available in the CI output of the tests assuming the publicly available tool can not provide any new info than what is available in the CI script ?
Do we create two separates tests one for triaged but not yet merged fixes & one for triaged and merged fixes (Triaged issues refer to CVE IDs which have been mentioned in GitHub Issues in k/k)
How often does the vulnerability database gets updated?
Does it have any differences in refresh cycles for vulnerabilities in go standard libraries (e.g. crypto/tls) v/s go packages in https://pkg.go.dev/ (e.g. golang.org/x/net v0.12.0)
Is there a definitive GOOS and GOARCH support we need to adhere to for scanning as the scanning can give different results based on the values for these env vars?

Post-script
In case there is anyone worried about the above output:
GO-2023-1987 fixed in:

https://github.com/kubernetes/release/pull/3189
https://github.com/kubernetes/k8s.io/pull/5679
https://github.com/kubernetes/k8s.io/pull/5680
https://github.com/kubernetes/k8s.io/pull/5681

GO-2023-1988 fixed in:

https://github.com/kubernetes/kubernetes/pull/119725

Previous discussions:

v1.0.0 blog post,
slack,
sig-security discussion on 2023-07-27

/sig security architecture release
/committee security-response

/remove-lifecycle stale

/remove-lifecycle rotten

/remove-lifecycle stale


Database attach flow fixed.

Threading model fixed in order to have all queries executed in the same order. android-native plugin fixed.
@itinance please check this change locally. Your initial change doesn't even compile in android-native. Also it has hard to figure out race condition. So if you have this code running in production I have a bad news for you.
Though I didn't test this as well.
We don't rely on this feature, I just see that it's implemented the way it could cause weird crashes.

Wow! Thank you very much! Will test in upcoming days. One of our applications is using ATTACH DATABASE very heavily.
But we never used android-native plugin. Maybe this is the reason that we never noticed issues with that. How did you activate it? What do i have to do to active the native-plugin against the other one.
I was quiet lost those days with the android-part (i am iOS-native-developer and this was my first JAVA-contribution). You can read all this in all these comments on my pull request then ;), also my question why there are two different implementations for android because they are looking quiet the same ^^

@itinance, one implementation is using system SQLite (android).
And another one uses separately built distribution.
I think it's there historically probably someone experienced some weird issues with system library on Cordova. And it also easier to support your application if you have the same version of SQLite among all existing devices.
to test it just replace android by android-native in settings.gradle of your project.

@itinance can you double check these changes please?

Confirmed.


allowFontScaling Not Working

Hello. I found that when passing allowFontScaling and set it to false, there will be a glitch. When allowFontScaling prop is passed, the fontsize should be like the top form

Hey man, could you provide a code sample?

Closing due inactivity


[Component] Badge outline color

We change the outline color by Base/surface by default
Spec: url

I've used the on-surface token when the intent is surface, because otherwise we end up with something like this (see picture below),
what are your thoughts on this, @Bibisirius ?

ariane link = https://spark-28xkda7bi-spark-team.vercel.app/?path=/docs/components-badge--docs

Hi !
The outline badge must be surface by defaut
Here's the link to the topic: here

👋 @Bibisirius , ok, so I'll go with B then 👍

Perfect!  This corresponds to the update on Figma
Thanks @acd02 🙏


Support for 1.21

Suggestion Type
Other
Suggestion
Adding support for 1.21.x, it's really important to me, please!
Assets
No response
Implementation Details and References
No response

Please be patient as there's only a very limited of amount working on this mod.
Duplicate of #934


Versioned & tagged release?

Thanks!

Second that.

@ekg could you please do the needful?
I need this for another dependency and tagged release would be great!

I've tagged v0.1. Sorry for the wait.


Remove dates from copyright notice

These are some files I believe would be affected:

[ ] https://github.com/jquery/globalize/blob/master/LICENSE.txt

[ ] https://github.com/jquery/globalize/blob/master/src/build/intro-core.js

[ ] https://github.com/jquery/globalize/blob/master/src/build/intro-date.js

[ ] https://github.com/jquery/globalize/blob/master/src/build/intro-message.js

[ ] https://github.com/jquery/globalize/blob/master/src/build/intro-number.js

[ ] https://github.com/jquery/globalize/blob/master/src/build/intro-plural.js

[ ] https://github.com/jquery/globalize/blob/master/src/build/node-main.js

There may be more...

[ ] src/build/intro-currency.js

But, yeap this is it.

Also remove "Inc."  according to https://github.com/jquery/jquery/commit/66e1b6b8d49812239b5712d65922ff94c60f7b02.


[WC] Azure: use external cloud controller manager

See https://github.com/giantswarm/giantswarm/issues/20965
And do the same for WCs

Blocked until https://github.com/giantswarm/giantswarm/issues/20965 is out and we're confident it works reliably

I guess it works just fine @whites11 ?

I didn't notice any big problems in MCs, yes

I wonder if we should have a ticket to do the same thing on AWS WCs as well @T-Kukawka

@whites11 i don't see a 'representation' of same stuff on AWS upstream

@whites11 i don't see a 'representation' of same stuff on AWS upstream

what do you mean?

implemented in azure operator 6.0.0 that will be part of release 18.0.0


A one-click pool creation in Daedalus?

This could be incredibly difficult to build, but at the same time, it could be incredibly successful. The pool creation right from within the Daedalus.

@RajaMBZ Daedalus is not designed for stake pool operators. There are specialized tools you should use to set up your stake pool.


Use thread pool for DeleteDanglingObjectStorageFilesStep

CPU intensive steps running in the main thread block all async operations.
This include other concurrent requests, leaving astacus completely unresponsive.
Start moving some steps entirely in a thread pool to avoid that.
We were already using the thread pool a lot anyway, since our object storage library
is sync, but now instead of entering/leaving the pool for every small operation, we
run an entire step as a single task.
[DDB-951]

since our object storage library is sync

This seems quite a shortcoming and I wonder whether this should be addressed somehow.

It's also true of the zookeeper client, cassandra client, etc. Approximately everything except astacus client/server HTTP is sync code wrapped in threads and async awaited.
Given than "doing CPU-intensive work" happens in many place and is hard to diagnose (problems only happens with large backups), I'm leaning towards addressing it by progressively moving everything to threads and getting rid of async in all of astacus, not by trying to find async libraries for everything. We don't really need the theoretical efficiency of an astacus able to answer to thousand of concurrent queries.
(By "moving to threads", I mean "one query per thread" + "a few pools for things that are worth parallelizing and currently handled with asyncio.gather", not total chaos and tons of locks.)

I'm leaning towards addressing it by progressively moving everything to threads and getting rid of async in all of astacus,

+1 on this. Async applications are usually efficient when everything is async, with only the occasional reliance on threads. If it's "oh my God it's full of threads" it's probably just easier to do everything in sync, rather than wasting time on making the two "colors" interoperate.


Add profile pictures to posts

[x] add profile pictures to posts
[ ] move profile pictures in the top left of the image
[ ] move username to the right of the image

Add profile pictures to post in #19


Document too complex to read and hard to understand

Missing:

Overview of the whole selection mechanism and how does it work
What are the different features and when are they used? example:
withCapabilities, withSeries, withMeasures (etc.)
In what cases should one use them? Does it make sense to use them together? Or does each one of them work for a
different usecase?
Is it required to execute "createSelectionIdBuilder()" for each new selectionId? or can this object be reused? (and why)

Maybe if there was somewhere to read about general structure (series, category, measure) and their relationship, things would be clearer here, but I cannot find any such document.

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

ID: 75effaec-3c6e-83c9-c26e-8e58046cb347
Version Independent ID: 971d9758-f10b-cddb-f6fa-c007e193e457
Content: Power BI visual data point selections - Power BI
Content Source: powerbi-docs/developer/visuals/selection-api.md
Service: powerbi
Sub-service: powerbi-custom-visuals
GitHub Login: @zBritva
Microsoft Alias: v-ilgali

Thanks for your comment, @tomer-agam.
I've assigned this issue to the Power BI visual support team for review.

Both of withSeries and withMeasures are used, it will create appropriate selectionId based on data a user passed into the visual.
createSelectionIdBuilder() is used for every datapoint, you can't reuse it.

#please-close @kfollis


[WIP] backend: Load config schema when backend starts (and optionally validate config)

Related to https://github.com/backstage/backstage/issues/3920
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Too draft this one. Will close this :)
Ref: https://github.com/backstage/backstage/pull/7156
cc @HHogg @ainhoaL


'FBReactNativeSpec/FBReactNativeSpec.h' file not found

Description
Hello, i'm getting this error 'FBReactNativeSpec/FBReactNativeSpec.h' file not foundwith the stacktrace below.
Podfile
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

require Pod::Executable.execute_command('node', ['-p',
  'require.resolve(
    "react-native/scripts/react_native_pods.rb",
    {paths: [process.argv[1]]},
  )', __dir__]).strip

platform :ios, min_ios_version_supported
prepare_react_native_project!

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

# flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

def fix_library_search_paths(installer)
  def fix_config(config)
    lib_search_paths = config.build_settings["LIBRARY_SEARCH_PATHS"]
    if lib_search_paths
      if lib_search_paths.include?("$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)") || lib_search_paths.include?("\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)\"")
        # $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) causes problem with Xcode 12.5 + arm64 (Apple M1)
        # since the libraries there are only built for x86_64 and i386.
        lib_search_paths.delete("$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)")
        lib_search_paths.delete("\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)\"")
        if !(lib_search_paths.include?("$(SDKROOT)/usr/lib/swift") || lib_search_paths.include?("\"$(SDKROOT)/usr/lib/swift\""))
          # however, $(SDKROOT)/usr/lib/swift is required, at least if user is not running CocoaPods 1.11
          lib_search_paths.insert(0, "$(SDKROOT)/usr/lib/swift")
        end
      end
    end
  end

  def _apply_Xcode_14_3_RC_post_install_workaround(installer)
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        current_target = config.build_settings['IPHONEOS_DEPLOYMENT_TARGET']
        minimum_target = '13.0'
        if current_target.to_f < minimum_target.to_f
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
        end
      end
    end
  end

  projects = installer.aggregate_targets
    .map{ |t| t.user_project }
    .uniq{ |p| p.path }
    .push(installer.pods_project)

  projects.each do |project|
    project.build_configurations.each do |config|
      fix_config(config)
    end
    project.native_targets.each do |target|
      target.build_configurations.each do |config|
        fix_config(config)
      end
    end
    project.save()
  end
end

target 'Equitazone' do
  config = use_native_modules!

  use_frameworks! :linkage => :static
  $RNFirebaseAsStaticFramework = true

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    :hermes_enabled => false,
    :fabric_enabled => flags[:fabric_enabled],
    :flipper_configuration => FlipperConfiguration.disabled,
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  pod 'react-native-config/Extension', :path => '../node_modules/react-native-config'

  # pod 'RNFBFunctions', :path => '../node_modules/@react-native-firebase/functions'

  # pod 'Firebase', :modular_headers => true
  # pod 'Firebase/Storage', :modular_headers => true
  # pod 'FirebaseCore', :modular_headers => true
  # pod 'FirebaseCoreInternal', :modular_headers => true
  # pod 'GoogleUtilities', :modular_headers => true
  # pod 'FirebaseAppCheckInterop', :modular_headers => true
  # pod 'FirebaseAuthInterop', :modular_headers => true
  # pod 'FirebaseCoreExtension', :modular_headers => true
  # pod 'GTMSessionFetcher', :modular_headers => true

  target 'EquitazoneTests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable these next few lines.
  # use_flipper!
  post_install do |installer|
    # __apply_Xcode_12_5_M1_post_install_workaround(installer)
    installer.pods_project.build_configuration_list.build_configurations.each do |configuration|
      configuration.build_settings['CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES'] = 'YES'
    end
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
        config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
        config.build_settings['CODE_SIGN_IDENTITY'] = ''
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
      end
    end
    react_native_post_install(
      installer,
      config[:reactNativePath],
      :mac_catalyst_enabled => false
    )
    fix_library_search_paths(installer)
    # _apply_Xcode_14_3_RC_post_install_workaround(installer)
  end
end

target 'Equitazone-tvOS' do
  # Pods for Equitazone-tvOS

  target 'Equitazone-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end
end

workspace 'Equitazone.xcworkspace'

And these are the dependencies I'm using in my package.json:
"dependencies": {
<EMAIL_ADDRESS>"^3.0.5",
    "@notifee/react-native": "^5.6.0",
    "@react-native-async-storage/async-storage": "^1.21.0",
    "@react-native-clipboard/clipboard": "^1.10.0",
    "@react-native-community/datetimepicker": "^7.6.2",
    "@react-native-firebase/analytics": "17.3.0",
    "@react-native-firebase/app": "17.3.0",
    "@react-native-firebase/auth": "17.3.0",
    "@react-native-firebase/firestore": "17.3.0",
    "@react-native-firebase/functions": "17.3.0",
    "@react-native-firebase/messaging": "17.3.0",
    "@react-native-firebase/storage": "17.3.0",
    "@react-native-picker/picker": "^2.2.1",
    "@react-navigation/bottom-tabs": "^6.5.11",
    "@react-navigation/native": "^6.1.9",
    "@react-navigation/stack": "^6.3.20",
    "@sentry/react-native": "^4.14.0",
    "@stripe/stripe-react-native": "^0.33.0",
    "@tanstack/query-async-storage-persister": "^4.29.5",
    "@tanstack/react-query": "^4.29.5",
    "@tanstack/react-query-persist-client": "^4.29.5",
    "AsyncStorage": "^0.1.5",
    "dayjs": "^1.11.8",
    "firebase": "^8.2.2",
    "i18next": "^21.3.3",
    "moment": "^2.29.1",
    "numeral": "^2.0.6",
    "prettier": "^2.8.8",
    "qs": "^6.10.4",
    "react": "18.2.0",
    "react-i18next": "^11.13.0",
    "react-native": "^0.73.0",
    "react-native-app-intro-slider": "^4.0.4",
    "react-native-calendars": "^1.1284.0",
    "react-native-chart-kit": "^6.12.0",
    "react-native-config": "^1.4.5",
    "react-native-document-picker": "^8.1.3",
    "react-native-gesture-handler": "^2.14.0",
    "react-native-google-places-autocomplete": "^2.2.0",
    "react-native-image-crop-picker": "^0.39.0",
    "react-native-image-viewing": "^0.2.2",
    "react-native-localize": "^2.1.5",
    "react-native-maps": "^0.27.1",
    "react-native-modal-datetime-picker": "^13.1.2",
    "react-native-push-notification": "^8.1.1",
    "react-native-safe-area": "^0.5.1",
    "react-native-safe-area-context": "^4.8.2",
    "react-native-screens": "^3.21.0",
    "react-native-splash-screen": "^3.3.0",
    "react-native-svg": "^14.0.0",
    "react-native-swipe-gestures": "^1.0.5",
    "react-native-vector-icons": "^9.0.0",
    "react-native-web": "0.19.4",
    "react-native-webview": "^13.6.1"
  },
  "devDependencies": {
    "@babel/core": "7.12.9",
    "@babel/runtime": "7.12.5",
    "@react-native-community/eslint-config": "1.1.0",
    "@types/jest": "^27.5.1",
    "@types/react": "^17.0.2",
    "@types/react-native": "0.71.6",
    "@types/react-test-renderer": "18.0.0",
    "babel-jest": "25.5.1",
    "eslint": "6.8.0",
    "jest": "^29.2.1",
    "metro-react-native-babel-preset": "0.59.0",
    "react-test-renderer": "18.2.0",
    "typescript": "^4.6.4"
  },

This does not work with RN version 0.71.7 or latest version 0.73.0.
This works correctly on Android though.
Sorry I'm not sure if this is what was expected from the reproducer, let me know if I need to update anything
Do you have any idea why I got this error and how to fix it? Thanks in advance for your help 🙏🏻
Steps to reproduce

npm i
pod install
press run from Xcode

React Native Version
0.73.0
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 14.1.1
  CPU: (8) arm64 Apple M1 Pro
  Memory: 151.02 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.2.0
    path: /usr/local/bin/node
  Yarn: Not Found
  npm:
    version: 9.6.6
    path: /usr/local/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.3
    path: /opt/homebrew/lib/ruby/gems/3.2.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - watchOS 10.2
  Android SDK:
    API Levels:
      - "28"
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
    Build Tools:
      - 29.0.2
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 32.0.0
      - 33.0.0
      - 34.0.0
    System Images:
      - android-28 | Google APIs ARM 64 v8a
      - android-28 | Google ARM64-V8a Play ARM 64 v8a
      - android-29 | Google APIs ARM 64 v8a
      - android-29 | Google Play ARM 64 v8a
      - android-30 | Google APIs ARM 64 v8a
      - android-31 | Google Play ARM 64 v8a
      - android-32 | Google APIs ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
      - android-33 | Google Play ARM 64 v8a
    Android NDK: 22.1.7171670
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.11090377
  Xcode:
    version: 15.1/15C65
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.1
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Stacktrace or Logs
CompileC /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/Objects-normal/x86_64/RCTVibration.o /Users/marion/Documents/Equitazone-app/node_modules/react-native/Libraries/Vibration/RCTVibration.mm normal x86_64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'React-RCTVibration' from project 'Pods')
    cd /Users/marion/Documents/Equitazone-app/ios/Pods
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c++ -ivfsstatcache /Users/marion/Documents/Equitazone-app/ios/DerivedData/SDKStatCaches.noindex/iphonesimulator17.2-21C52-4f2951bfe8f3cd53c99228b0131e163e.sdkstatcache -target x86_64-apple-ios13.4-simulator -fmessage-length\=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit\=0 -fno-color-diagnostics -std\=c++20 -stdlib\=libc++ -fobjc-arc -fmodules -gmodules -fmodules-cache-path\=/Users/marion/Documents/Equitazone-app/ios/DerivedData/ModuleCache.noindex -fmodules-prune-interval\=86400 -fmodules-prune-after\=345600 -fbuild-session-file\=/Users/marion/Documents/Equitazone-app/ios/DerivedData/ModuleCache.noindex/Session.modulevalidation -fmodules-validate-once-per-build-session -fmodule-name\=RCTVibration -Wno-trigraphs -fpascal-strings -O0 -fno-common -Wno-missing-field-initializers -Wno-missing-prototypes -Werror\=return-type -Wdocumentation -Wunreachable-code -Wno-implicit-atomic-properties -Werror\=deprecated-objc-isa-usage -Wno-objc-interface-ivars -Werror\=objc-root-class -Wno-arc-repeated-use-of-weak -Wimplicit-retain-self -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wconditional-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-float-conversion -Wnon-literal-null-conversion -Wobjc-literal-conversion -Wshorten-64-to-32 -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wdeprecated-implementations -Wno-c++11-extensions -Wno-implicit-fallthrough -DPOD_CONFIGURATION_DEBUG\=1 -DDEBUG\=1 -DCOCOAPODS\=1 -D_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION -DOBJC_OLD_DISPATCH_PROTOTYPES\=0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator17.2.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -Winvalid-offsetof -g -fvisibility-inlines-hidden -Wno-sign-conversion -Winfinite-recursion -Wmove -Wcomma -Wblock-capture-autoreleasing -Wstrict-prototypes -Wrange-loop-analysis -Wno-semicolon-before-method-body -Wunguarded-availability -fobjc-abi-version\=2 -fobjc-legacy-dispatch -index-store-path /Users/marion/Documents/Equitazone-app/ios/DerivedData/Equitazone/Index.noindex/DataStore -iquote /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/RCTVibration-generated-files.hmap -I/Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/RCTVibration-own-target-headers.hmap -I/Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/RCTVibration-all-non-framework-target-headers.hmap -ivfsoverlay /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/all-product-headers.yaml -iquote /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/RCTVibration-project-headers.hmap -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-RCTVibration/include -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon/ReactCommon.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon/ReactCommon.framework/Headers/react/nativemodule/core -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon-Samples/ReactCommon_Samples.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon-Samples/ReactCommon_Samples.framework/Headers/platform/ios -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-NativeModulesApple/React_NativeModulesApple.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-graphics/React_graphics.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-graphics/React_graphics.framework/Headers/react/renderer/graphics/platform/ios -I/Users/marion/Documents/Equitazone-app/ios/Pods/Headers/Public -I/Users/marion/Documents/Equitazone-app/ios/Pods/Headers/Public/FBLazyVector -I/Users/marion/Documents/Equitazone-app/ios/Pods/Headers/Public/RCTRequired -I/Users/marion/Documents/Equitazone-app/ios/Pods/Headers/Public/React-callinvoker -I/Users/marion/Documents/Equitazone-app/ios/Pods/Headers/Public/React-runtimeexecutor -I/Users/marion/Documents/Equitazone-app/ios/Pods/RCT-Folly -I/Users/marion/Documents/Equitazone-app/ios/Pods/Headers/Public/React-Codegen/react/renderer/components -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-Codegen/React_Codegen.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-Codegen/React_Codegen.framework/Headers/build/generated/ios -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon/ReactCommon.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon/ReactCommon.framework/Headers/react/nativemodule/core -I/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-NativeModulesApple/React_NativeModulesApple.framework/Headers -I/Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/DerivedSources-normal/x86_64 -I/Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/DerivedSources/x86_64 -I/Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/DerivedSources -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-RCTVibration -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/DoubleConversion -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/RCT-Folly -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/RCTTypeSafety -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-Codegen -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-Core -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-NativeModulesApple -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-cxxreact -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-debug -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-jsc -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-jsi -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-jsiexecutor -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-jsinspector -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-logger -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-perflogger -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-rendererdebug -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-runtimescheduler -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/React-utils -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/ReactCommon -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/SocketRocket -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/Yoga -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/fmt -F/Users/marion/Documents/Equitazone-app/ios/Build/Products/Debug-iphonesimulator/glog -DFOLLY_NO_CONFIG -DFOLLY_MOBILE\=1 -DFOLLY_USE_LIBCPP\=1 -DFOLLY_CFG_NO_COROUTINES\=1 -Wno-comma -Wno-shorten-64-to-32 -Wno-nullability-completeness -include /Users/marion/Documents/Equitazone-app/ios/Pods/Target\ Support\ Files/React-RCTVibration/React-RCTVibration-prefix.pch -MMD -MT dependencies -MF /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/Objects-normal/x86_64/RCTVibration.d --serialize-diagnostics /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/Objects-normal/x86_64/RCTVibration.dia -c /Users/marion/Documents/Equitazone-app/node_modules/react-native/Libraries/Vibration/RCTVibration.mm -o /Users/marion/Documents/Equitazone-app/ios/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-RCTVibration.build/Objects-normal/x86_64/RCTVibration.o -index-unit-output-path /Pods.build/Debug-iphonesimulator/React-RCTVibration.build/Objects-normal/x86_64/RCTVibration.o

/node_modules/react-native/Libraries/Vibration/RCTVibration.mm:11:9: fatal error: 'FBReactNativeSpec/FBReactNativeSpec.h' file not found
#import <FBReactNativeSpec/FBReactNativeSpec.h>

### Reproducer

https://github.com/toscalivia83/Equitazone-repro

### Screenshots and Videos

<img width="1134" alt="Capture d’écran 2024-01-08 à 20 08 00" src="https://github.com/facebook/react-native/assets/19326704/7a9f6a1b-8e54-4ec2-889d-13113ec6b142">

This is happening  on our CI environment as well when we  updated to xcode15, locally it works however we get the exact same error in our CI building the app

I think this happened to me as well after updating to xcode 15. I tried updating to Xcode 15.2, I'll see if it works, otherwise, I'll try downgrading Xcode maybe.
If you find any fix let me know
However I keep having this error I logged here

Tried downgrading to Xcode 14.3.1 but it's not compatible with MacOS Sonoma 14.1.1. I upgraded MacOS to 14.2.1, it did not change anything.
However it doesn't work either if I run with react-native run-ios for me, with the exact same error.
Were you saying it works for you locally @Alcoholic-Obelix ?
@cipolleschi do you have any idea what to do to fix this error ? 🙏

@toscalivia83 sorry to hear that you are having troubles.
The problem is in your podfile.
1st, remove these chunks. Our react_native_post_install does that for you already:
def fix_library_search_paths(installer)
  def fix_config(config)
    lib_search_paths = config.build_settings["LIBRARY_SEARCH_PATHS"]
    if lib_search_paths
      if lib_search_paths.include?("$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)") || lib_search_paths.include?("\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)\"")
        # $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) causes problem with Xcode 12.5 + arm64 (Apple M1)
        # since the libraries there are only built for x86_64 and i386.
        lib_search_paths.delete("$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)")
        lib_search_paths.delete("\"$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)\"")
        if !(lib_search_paths.include?("$(SDKROOT)/usr/lib/swift") || lib_search_paths.include?("\"$(SDKROOT)/usr/lib/swift\""))
          # however, $(SDKROOT)/usr/lib/swift is required, at least if user is not running CocoaPods 1.11
          lib_search_paths.insert(0, "$(SDKROOT)/usr/lib/swift")
        end
      end
    end
  end

  def _apply_Xcode_14_3_RC_post_install_workaround(installer)
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        current_target = config.build_settings['IPHONEOS_DEPLOYMENT_TARGET']
        minimum_target = '13.0'
        if current_target.to_f < minimum_target.to_f
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
        end
      end
    end
  end

  projects = installer.aggregate_targets
    .map{ |t| t.user_project }
    .uniq{ |p| p.path }
    .push(installer.pods_project)

  projects.each do |project|
    project.build_configurations.each do |config|
      fix_config(config)
    end
    project.native_targets.each do |target|
      target.build_configurations.each do |config|
        fix_config(config)
      end
    end
    project.save()
  end
end

Then, remove these chunks. Either our react_native_post_install does that for you already or they are not required anymore:
installer.pods_project.build_configuration_list.build_configurations.each do |configuration|
      configuration.build_settings['CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES'] = 'YES'
    end
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
        config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
        config.build_settings['CODE_SIGN_IDENTITY'] = ''
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
      end

If the problem persists, it means that one of your 3rd party dependency is not properly configured.
My suggestion, in this case, is to try and isolate what it is.
So, let's start from a clean 0.73 project and let's add one dependency at a time to see what make the build stop working.
Once we identify the dependency, we can try to understand why and work on a solution! :D

Tried downgrading to Xcode 14.3.1 but it's not compatible with MacOS Sonoma 14.1.1. I upgraded MacOS to 14.2.1, it did not change anything except that it now complains with error from RCTSettingsManager file:
.../node_modules/react-native/Libraries/Settings/RCTSettingsManager.mm:10:9: fatal error: 'FBReactNativeSpec/FBReactNativeSpec.h' file not found
#import <FBReactNativeSpec/FBReactNativeSpec.h>

I also tried downgrading to RN 0.71.7 as it worked with this version before but it didn't do the job.
It doesn't work either if I run with react-native run-ios for me, with the exact same error. Were you saying it works for you locally @Alcoholic-Obelix ?
@cipolleschi do you have any idea what to do to fix this error ? 🙏

Yes, i have no problems running directly in xcode 15. Only in our CI environment. @cipolleschi my podfile is pretty barebones any guesses on why this could be happening and not with other xcode versions?

@Alcoholic-Obelix if you can run your app locally but it fails on CI, can you try to point out the differences between the two? Perhaps you are building with different versions of Xcode, macOS or with different machines...
It's really hard to help out not having logs or further details.
Can you set up a job in your CI to create and build a new React Native app from scratch?

Thanks for your answer @cipolleschi !
I tried updating the Podfile to this version above and running it on my real device but it still gives me this error 'FBReactNativeSpec/FBReactNativeSpec.h' file not found in React-RCTVibration 🤯
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '13.0'
prepare_react_native_project!

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'Equitazone' do
  config = use_native_modules!

  use_frameworks! :linkage => :static
  $RNFirebaseAsStaticFramework = true

  use_react_native!(:path => config[:reactNativePath], :hermes_enabled => false)

  pod 'react-native-config/Extension', :path => '../node_modules/react-native-config'

  # pod 'RNFBFunctions', :path => '../node_modules/@react-native-firebase/functions'

  # pod 'Firebase', :modular_headers => true
  # pod 'Firebase/Storage', :modular_headers => true
  # pod 'FirebaseCore', :modular_headers => true
  # pod 'FirebaseCoreInternal', :modular_headers => true
  # pod 'GoogleUtilities', :modular_headers => true
  # pod 'FirebaseAppCheckInterop', :modular_headers => true
  # pod 'FirebaseAuthInterop', :modular_headers => true
  # pod 'FirebaseCoreExtension', :modular_headers => true
  # pod 'GTMSessionFetcher', :modular_headers => true

  target 'EquitazoneTests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable these next few lines.
  # use_flipper!
  post_install do |installer|
    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
    react_native_post_install(
      installer,
      config[:reactNativePath],
      :mac_catalyst_enabled => false,
      # :ccache_enabled => true
    )
  end
end

target 'Equitazone-tvOS' do
  # Pods for Equitazone-tvOS

  target 'Equitazone-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end
end

workspace 'Equitazone.xcworkspace'

Can you please:

Build the app (⌘+B)
Open the Xcode Issue Navigator (⌘+5)
Filter for error only
Take a screenshot and share it here?

I don't think that the problem is with React-RCTVibration...

@cipolleschi unfortunately it really is the only error

@toscalivia83 go to Report Navigator (last icon) and check the errors of that build pls

@Alcoholic-Obelix if you can run your app locally but it fails on CI, can you try to point out the differences between the two? Perhaps you are building with different versions of Xcode, macOS or with different machines... It's really hard to help out not having logs or further details.
Can you set up a job in your CI to create and build a new React Native app from scratch?

The versions all match, that's gonna be tough inside my organization but i'll try.
Thank you!

@Alcoholic-Obelix the error of that build is the one mentioned at the top in "Stacktrace or Logs". It did not change

Actually I made a mistake at some point and was running my project with the .xcodeproject.
Now that I'm running it with .xcworkspace it displays the error 'React/RCTBridgeDelegate.h' file not found in AppDelegate

@cipolleschi I'm trying to create a new RN project and it seems there are problems with some of the dependencies from react-native-firebase. Starting by @react-native-firebase/app which was complaining about
[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `FirebaseCoreInternal` depends upon `GoogleUtilities`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

I added:

pod 'Firebase', :modular_headers => true
  pod 'FirebaseCoreInternal', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true

and it fixed it.
Then for @react-native-firebase/auth I'm getting this error I don't know how to fix yet

### Command

/opt/homebrew/lib/ruby/gems/3.2.0/bin/pod install

### Report

* What did you do?

* What did you expect to happen?

* What happened instead?

### Stack

CocoaPods : 1.12.1
Ruby : ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]
RubyGems : 3.4.10
Host : macOS 14.2.1 (23C71)
Xcode : 15.2 (15C500b)
Git : git version 2.39.3 (Apple Git-145)
Ruby lib dir : /opt/homebrew/Cellar/ruby/3.2.2/lib
Repositories : trunk - CDN - https://cdn.cocoapods.org/

### Plugins

cocoapods-deintegrate : 1.0.5
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.1
cocoapods-trunk       : 1.6.0
cocoapods-try         : 1.2.0

### Podfile

```ruby
# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
  'require.resolve(
    "react-native/scripts/react_native_pods.rb",
    {paths: [process.argv[1]]},
  )', __dir__]).strip

platform :ios, min_ios_version_supported
prepare_react_native_project!

# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'AwesomeWORKINGProject' do
  config = use_native_modules!

  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCoreInternal', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true

  use_react_native!(
    :path => config[:reactNativePath],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    :flipper_configuration => flipper_config,
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  target 'AwesomeWORKINGProjectTests' do
    inherit! :complete
    # Pods for testing
  end

  post_install do |installer|
    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
    react_native_post_install(
      installer,
      config[:reactNativePath],
      :mac_catalyst_enabled => false
    )
  end
end

Error
LoadError - dlopen(/opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi_c.bundle, 0x0009): tried: '/opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi_c.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi_c.bundle' (no such file), '/opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi_c.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')) - /opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi_c.bundle
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi.rb:5:in `rescue in <top (required)>'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/ffi-1.16.3/lib/ffi.rb:2:in `<top (required)>'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/ethon-0.16.0/lib/ethon.rb:3:in `<top (required)>'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/typhoeus-1.4.1/lib/typhoeus.rb:2:in `<top (required)>'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
<internal:/opt/homebrew/Cellar/ruby/3.2.2/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/cdn_source.rb:440:in `download_typhoeus_impl_async'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/cdn_source.rb:372:in `download_and_save_with_retries_async'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/cdn_source.rb:365:in `download_file_async'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/cdn_source.rb:338:in `download_file'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/cdn_source.rb:284:in `ensure_versions_file_loaded'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/cdn_source.rb:208:in `search'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/source/aggregate.rb:83:in `block in search'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/source/aggregate.rb:83:in `select'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-core-1.12.1/lib/cocoapods-core/source/aggregate.rb:83:in `search'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:416:in `create_set_from_sources'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:385:in `find_cached_set'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:360:in `specifications_for_dependency'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:165:in `search_for'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:274:in `block in sort_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:267:in `each'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:267:in `sort_by'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:267:in `sort_by!'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:267:in `sort_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/delegates/specification_provider.rb:60:in `block in sort_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/delegates/specification_provider.rb:77:in `with_no_such_dependency_error_handling'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/delegates/specification_provider.rb:59:in `sort_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:754:in `push_state_for_requirements'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:744:in `require_nested_dependencies_for'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:727:in `activate_new_spec'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:684:in `attempt_to_activate'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:254:in `process_topmost_state'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:182:in `resolve'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/molinillo-0.8.0/lib/molinillo/resolver.rb:43:in `resolve'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/resolver.rb:94:in `resolve'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer/analyzer.rb:1082:in `block in resolve_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/user_interface.rb:64:in `section'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer/analyzer.rb:1080:in `resolve_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer/analyzer.rb:125:in `analyze'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:422:in `analyze'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:244:in `block in resolve_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/user_interface.rb:64:in `section'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:243:in `resolve_dependencies'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/installer.rb:162:in `install!'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/command/install.rb:52:in `run'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/lib/cocoapods/command.rb:52:in `run'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/cocoapods-1.12.1/bin/pod:55:in `<top (required)>'
/opt/homebrew/lib/ruby/gems/3.2.0/bin/pod:25:in `load'
/opt/homebrew/lib/ruby/gems/3.2.0/bin/pod:25:in `<main>'

――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
[!] Oh no, an error occurred.
Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=dlopen(%2Fopt%2Fhomebrew%2Flib%2Fruby%2Fgems%2F3.2.0%2Fgems%2Fffi-1.16.3%2Flib%2Fffi_c.bundle%2C+0x0009)%3A+tried%3A+'%2Fopt%2Fhomebrew%2Flib%2Fruby%2Fgems%2F3.2.0%2Fgems%2Fffi-1.16.3%2Flib%2Fffi_c.bundle'+(mach-o+file%2C+but+is+an+incompatible+architecture+(have+'x86_64'%2C+need+'arm64'))%2C+'%2FSystem%2FVolumes%2FPreboot%2FCryptexes%2FOS%2Fopt%2Fhomebrew%2Flib%2Fruby%2Fgems%2F3.2.0%2Fgems%2Fffi-1.16.3%2Flib%2Fffi_c.bundle'+(no+such+file)%2C+'%2Fopt%2Fhomebrew%2Flib%2Fruby%2Fgems%2F3.2.0%2Fgems%2Fffi-1.16.3%2Flib%2Fffi_c.bundle'+(mach-o+file%2C+but+is+an+incompatible+architecture+(have+'x86_64'%2C+need+'arm64'))+-+%2Fopt%2Fhomebrew%2Flib%2Fruby%2Fgems%2F3.2.0%2Fgems%2Fffi-1.16.3%2Flib%2Fffi_c.bundle&type=Issues
If none exists, create a ticket, with the template displayed above, on:
https://github.com/CocoaPods/CocoaPods/issues/new
Be sure to first read the contributing guide for details on how to properly submit a ticket:
https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md
Don't forget to anonymize any private data!
Looking for related issues on cocoapods/cocoapods...
Searching for inspections failed: undefined method `map' for nil:NilClass

Any idea how to fix this?

Then I'll have these dependencies to add and I'll be done:
@react-native-firebase/firestore @react-native-firebase/analytics @react-native-firebase/functions @react-native-firebase/messaging @react-native-firebase/storage

If it gives you any idea on what I can do to make it work let me know!

I created a new repo and had to update a lot of dependencies on ios and android. The ones which were creating problemes were the ones from firebase (auth, messaging, firestore), I had to upgrade react-native-vector-icons in ios, and I had problems with the version of stripe in ios and Android, and reinstall as normal dependency @babel/runtime.
These are the versions I use now:
"dependencies": {
    "@babel/runtime": "^7.23.8",
<EMAIL_ADDRESS>"^3.0.7",
    "@notifee/react-native": "^7.8.2",
    "@react-native-async-storage/async-storage": "^1.15.9",
    "@react-native-clipboard/clipboard": "^1.11.2",
    "@react-native-community/datetimepicker": "6.7.3",
    "@react-native-firebase/analytics": "^18.7.3",
    "@react-native-firebase/app": "^18.7.3",
    "@react-native-firebase/auth": "^18.7.3",
    "@react-native-firebase/firestore": "^18.7.3",
    "@react-native-firebase/functions": "^18.7.3",
    "@react-native-firebase/messaging": "^18.7.3",
    "@react-native-firebase/storage": "^18.7.3",
    "@react-native-picker/picker": "^2.6.1",
    "@stripe/stripe-react-native": "^0.35.0",
    "firebase": "^10.7.1",
    "react": "18.2.0",
    "react-native": "0.73.2",
    "react-native-app-intro-slider": "^4.0.4",
    "react-native-calendars": "^1.1284.0",
    "react-native-chart-kit": "^6.12.0",
    "react-native-config": "^1.4.5",
    "react-native-document-picker": "^8.1.3",
    "react-native-gesture-handler": "^1.10.3",
    "react-native-google-places-autocomplete": "^2.2.0",
    "react-native-image-crop-picker": "^0.40.2",
    "react-native-vector-icons": "^10.0.3"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@babel/preset-env": "^7.20.0",
    "@react-native-picker/picker": "^2.2.1",
    "@react-native/babel-preset": "0.73.19",
    "@react-native/eslint-config": "0.73.2",
    "@react-native/metro-config": "0.73.3",
    "@react-native/typescript-config": "0.73.1",
    "@react-navigation/bottom-tabs": "^5.11.15",
    "@react-navigation/native": "^5.9.8",
    "@react-navigation/stack": "^5.12.8",
    "@sentry/react-native": "^4.15.2",
    "@tanstack/query-async-storage-persister": "^4.29.5",
    "@tanstack/react-query": "^4.29.5",
    "@tanstack/react-query-persist-client": "^4.29.5",
    "@types/react": "^18.2.6",
    "@types/react-test-renderer": "^18.0.0",
    "AsyncStorage": "^0.1.5",
    "babel-jest": "^29.6.3",
    "dayjs": "^1.11.8",
    "eslint": "^8.19.0",
    "i18next": "^21.3.3",
    "jest": "^29.6.3",
    "moment": "^2.29.1",
    "numeral": "^2.0.6",
    "prettier": "2.8.8",
    "qs": "^6.10.4",
    "react-i18next": "^11.13.0",
    "react-native-image-crop-picker": "^0.39.0",
    "react-native-image-viewing": "^0.2.2",
    "react-native-localize": "^2.1.5",
    "react-native-maps": "^0.27.1",
    "react-native-modal-datetime-picker": "^13.1.2",
    "react-native-push-notification": "^8.1.1",
    "react-native-safe-area": "^0.5.1",
    "react-native-safe-area-context": "^3.3.2",
    "react-native-screens": "^2.18.1",
    "react-native-svg": "^13.9.0",
    "react-native-swipe-gestures": "^1.0.5",
    "react-native-web": "0.19.4",
    "react-native-webview": "^13.6.2",
    "react-test-renderer": "18.2.0",
    "typescript": "5.0.4"
  },
  "engines": {
    "node": ">=18"
  }

Good luck if you're stuck with this!

to understand @toscalivia83, did creating a new repo fixed the problem or is it still there?

Removing the build folder works for me

remove in ios folder:
/build
/Pods
/Podfile.lock
then run - cd ios && pod install --repo-update
and run the project with Xcode again

Getting this error with RCTVibration
RN's version: 0.75.3
Xcode: 16


Update tracing-in-aspnet-web-api.md

Cleaned up first sentence in "How Web API Tracing Works".

@scout208 Thank you for fixing this. Your change will go live later today.


Draining energy

Issue description:
It seems like the energy gets drained from your machines.
Suggestion:
Make BaseEnergyStorage#canExtract returns false and/or BaseEnergyStorage#maxExtract to 0
Version:

Minecraft: 1.14.4
Forge: 28.1.96
Refined Storage: 1.7.1

Does this issue occur on a server? [yes/no]
Both Sides

Please be more clear in future reports :)
From what I understand it's possible to extract energy from the Controller and the suggestion is to prevent that from happening?

Yes exactly. :)


Revert PR-7825 snapshot changes

Tests got broken after https://github.com/facebook/react-native/pull/7825, reverting changes
Test Plan:
./scritps/objc-test.sh

Locally tests are passing, merging now

@facebook-github-bot shipit

By analyzing the blame information on this pull request, we identified @nicklockwood and @feichngr to be potential reviewers.

Thanks for importing. If you are an FB employee go to Phabricator to review.


Make multiplayer work with HTTPS

When you use Batwaves on a web browser, multiplayer does not work unless you use HTTP. Using HTTPS doesn't work with multiplayer.

ok, we need some way to set a certificate here so that it will use https for the websocket
https://github.com/MarkSort/batwaves/blob/bc7f13b27b90e8d543c8168e782b89fe5cc4f8c5/godot/Networking/Server.gd#L18