XML documentation

Hi there,
This is more of a question than an issue, likely.
I'd like to include my XML documentation comments with my swagger documentation. What's the right way to do this with asp.net vnext?
I have a line like this:
c.IncludeXmlComments(".xml");
But I get a FileNotFoundException, because I'm not actually producing any build outputs.
I'm trying to build my code into a Docker image and deploy it to Rancher. Everything works great, except I don't have the nice XML documentation comments I added to my Controller and Model.
Your project is awesome. Thank you!
Ranj

Hi,
In ASP.NET 5 you cannot set the output file name and location for your XML documentation, at least not yet. Thus I would not use that option but rather I would use an operation filter as shown in this pull request (https://github.com/domaindrivendev/Ahoy/pull/11).
However, you can still get XML docs if you produce outputs on build, This is explained here  at SO
The task will be to find where the result XML document output is, and get the absolute path before passing it into the Swagger method/function.

The problem I've found with this, in our ASP.NET 5 project, is there's an XML file generated per project/assembly.  When we deploy the API App to Azure, there's an XML for every package:
In this folder, there is {package-name}.xml:
/site/approot/packages/{package-name}/{version}/lib/dnx46
It looks like we'd need to collect up all the relevant XMLs from our packages into one file, and deploy to wwwroot, to make it easier for Swagger/Swashbuckle to find it.  The current working directory for that XML path below is /site/wwwroot.
            options.OperationFilter<ApplyXmlActionComments>(new ApplyXmlActionComments("{xml path}"));

Otherwise, we just can get the comments from the controllers in that main package, and none of the referenced classes in referenced packages.

You can use ILibraryManager to get the path of a given assembly and ultimately grab the XML documentation asset. If you have multiple assemblies that represent your APIs, then you'll need to manually combine them at the moment.
            var localServiceProvider = services.BuildServiceProvider();
            var libraryManager = ActivatorUtilities.GetServiceOrCreateInstance<ILibraryManager>(localServiceProvider);
            var energyCapApi = libraryManager.GetLibrary("EnergyCap.Api");
            var energyCapApiDirectory = Directory.GetParent(energyCapApi.Path);
            var apiXmlDocs = energyCapApiDirectory.GetFiles("EnergyCap.Api.xml", SearchOption.AllDirectories).FirstOrDefault();

            services.AddSwagger(options =>
            {
                options.SwaggerGeneratorOptions.SingleApiVersion(new Info
                {
                    Version = "v3",
                    Title = "EnergyCAP v3 API",
                    Description = "",
                    TermsOfService = ""

                });
                options.SwaggerGeneratorOptions.SecurityDefinitions.Add("api_key", new ApiKeyScheme() { In = "header", Name = "api_key", Type = "apiKey" });
                options.SwaggerGeneratorOptions.Host = "";
                options.SwaggerGeneratorOptions.BasePath = "";
                options.SchemaGeneratorOptions.UseFullTypeNameInSchemaIds = true;

                if (apiXmlDocs != null)
                {
                    options.IncludeXmlComments(apiXmlDocs.FullName);
                }
            });

@choudeshell Great, thanks, that's really useful information.

@choudeshell - yep that's awesome!

@choudeshell - to clean things up a little further, you can create a constructor in your Startup class that takes an ILibraryManager. The framework will ensure it gets injected and so you won't have to build a local service provider

See https://github.com/domaindrivendev/Ahoy/blob/master/test/WebSites/Basic/Startup.cs for an example which uses IApplicationEnvironment to find the xml doc.
If you need to find Xml files within Nugets, you can inject ILibraryManager into your startup and follow the steps outlined above by @choudeshell

The following code can be used to get the documentation XML file path if you are using Azure:
options.OperationFilter(new ApplyXmlActionComments(GetXmlCommentPath()));

private string GetXmlCommentPath()
{
    var applicationName = this.applicationEnvironment.ApplicationName;
    var applicationVersion = this.applicationEnvironment.ApplicationVersion;
    var basePath = GetSolutionBasePath();
    var configuration = this.applicationEnvironment.Configuration;
    var runtimeIdentifier = this.applicationEnvironment.RuntimeFramework.Identifier;
    var runtimeVersion = this.applicationEnvironment.RuntimeFramework.Version.ToString().Replace(".", string.Empty);

    if (this.hostingEnvironment.IsDevelopment())
    {
        return<EMAIL_ADDRESS>    }

    // Azure file path
    return<EMAIL_ADDRESS>}

private string GetSolutionBasePath()
{
    var directory = Directory.CreateDirectory(this.applicationEnvironment.ApplicationBasePath);

    while (directory.Parent != null)
    {
        if (directory.GetFiles("global.json").Any())
        {
            return directory.FullName;
        }

        directory = directory.Parent;
    }

    throw new InvalidOperationException("Failed to detect solution base path - global.json not found.");
}

This does not work in Azure with Asp.Net Core RC 1. I get a 500 error and the app can't start - we should reopen this issue and fix it when Asp.Net is released.

I have mine working right now on Azure very well; I just checked. Are you using Swashbuckle 6.0.0-rc1-final? Could you share a snippet or some sought of extra information on how you wired up Swashbuckle?

@RehanSaeed  Same problem here on azure web app... 500 error and app can't start.
My setup is:
			services.AddSwaggerGen();

			services.ConfigureSwaggerDocument(options =>
			{
				options.SingleApiVersion(new Swashbuckle.SwaggerGen.Info
				{
					Version = "v1",
					Title = "MyApi API"
				});

				options.OperationFilter(new ApplyXmlActionComments(GetXmlCommentPath()));
			});
			services.ConfigureSwaggerSchema(options =>
			{
				options.DescribeAllEnumsAsStrings = true;
			});

@MaurGi
I've found the problem. As you see GetXmlCommentPath on Azure expects to find your application inside the packages folder. This is deployed only if you select an option in VS Publish.
Check "settings -> File publish options" and enable "Compile source files into NuGet packages".


Update SharePoint-OneDrive-interact.md

Added clarifying language and external link for "document library" scenario

@RomanMSFT - thanks for this PR and making the docs better. It looks like there are some notes in here for the author so I won't merge this. Please go ahead and make any changes you would want to make and I can merge it in. Anything in a PR will show up in the document though. You could also ping the author (shown as the writer in the metadata, look at 'raw' article to see metadata). Ping me with any questions.


Feature Request: expose logged in user in loginSucceeded

Is it possible to propagate the logged in user to
def loginSucceeded(request: RequestHeader)(implicit ctx: ExecutionContext): Future[Result]

this seems like the ideal integration point for firing external events (audit logging for instance) but needs the applicable user to be useful. Or do you suggest another approach?

+1

Sorry my late reply.
I agree this motivation.
However, I consider removing the loginSucceeded and logoutSuceeded method from AuthConfig in future release.
In essence, play2-auth should be only provide a Result => Result function what it call in Login action when the login is succeeded.
I think it is better that these procedure (that use User info, ex. logging) are defined in Login Action directly.

I think I also need this in order to redirect every user to the appropriate top page (for that group of users) after login. Current workaround is to have a single controller for all that just dispatches based on group, but it would be nice to not need the extra level of indirection.


Allow custom formatting for --help, --version, --trace options

From @gabemc on October 22, 2010 18:2
You hard code the text strings for the default global options.  It is often necessary to manually reset those, to support things like internationalization.
Copied from original issue: tj/commander#23

From @tejasmanohar on November 23, 2014 22:27
Yeah, only option now is to dig through code and find things like never_trace! then override above your CLI's code :(

From @gretel on November 13, 2014 12:39
:+1:


Grid options don't return default values

In the snippet below the grid's row height and column header height are not returned even though the corresponding flag in getOptions(true) is set to true
const view = grok.shell.addTableView(grok.data.demo.molecules());
const options = view.grid.getOptions(true);
const nRH =  options.look.rowHeight;
const nCH = options.look.colHeaderHeight;
Is there an alternative way to retrieve those values?

Fixed in v0.153

Row height is fixed, but colHeaderHeight still returns null


Feature/xml format

Added XML formatting and moved getContentType() to Util Common for reuse.

Nice! Merged.
Thanks @Cibico99 !!


Dependency On FlutterMap 3.1.0 and 4.0.0-dev

Are there any plans to upgrade the dependency on flutter_map to 4.0.0-dev.2 at least on a dev channel ?

Same as v4.0.0-dev.1, see previous reply.


Problem with pagination & limit

Hi Steven!
Thank you for this plugin. You saved my life :)
I have a problem with pagination. The code I use is this:

$('#load-more').on('click', function() {
feed.next();
});

The console doesn't give me any error, but the button (at the bottom of the page) doesn't work :(
Also the limit option seems not to work. I would like to have 60 images at a time, but it only shows 20.
Can someone tell me what is wrong?
The website is the following: http://www.milanoeveryday.it/
Thank you all.
Much love, Nathalie

Hi nathinah  ,
How do u make the "load more" button work?
When I click my load more button it works, but it will start from the beginning. it doesn't go to the bottom like yours. Can you help me?

I'm also trying to figure out how to load more without it going back to the top of the page

@asegari Use event.preventDefault(); or return false at the end of the click handler function


Split the Random class

Seems like Random should be split into Random and RandomR. Somethings may not have bounds.

I thought so too and updated it.
Thank you for letting me know.

Thanks!


Div/rem instruction handelling just before ecall

How div/rem instruction is handled in quasar core when it comes just before ecall (for test finishing)?
while no div_wren or cancel signal is raised for the correct result/data of these instructions

@saqibsaeed-lm  I suggest adding a filler of 34 nop cycles to flush out the div/rem result before ending the test cc: @haroon-shafique


Baseline for references

Originally we choose the baseline for benchmarks as "1 p100 week." How do we want to define our baseline runtimes for references?

We feel this has a temporary solution for v0.6; we can re-open for the next submission.

No action in rules


Use constant-time comparison functions when checking signatures

This limits the likeliness of timing attacks against the API.
See http://codahale.com/a-lesson-in-timing-attacks/ for the
full rationale.

LGTM, let me test it. I can help backport it to 4.3/4.4, it's a good fix.

Tested locally on master, works for me. Thanks for your contribution @pyr

thanks @bhaisaab


⚠ Fortnite has degraded performance

In baa9984, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1344 ms

Resolved: Fortnite performance has improved in 434bee0.


Validate Monitoring Plan Data

Feature Benefit
Validate monitoring plan data using form validation and existing EPA check engine to ensure the data complies with EPA regulations.
Note: will need to define process to keep ERG's check engine and our check engine synched while both engines exist. ERG will be making updates such as refining error messages. At a certain point (maybe 12/15/2020), the check engine will be "locked" for no new changes by ERG.
Action item: need separate meeting to discuss check engine sync w/ ERG
Action item: Chris will ask ERG to document front-end validation rules
Importing: file schema validation (correct file structure)
Then imported file goes through additional checks
Formatting checks, range checks, completeness checks, data type checks
UI validation
Database / S3 file storage
Technical analysis / architectural design
UI design discussions (information architecture work, draft wireframes, high-fidelity UI designs)
Usability / user acceptance testing (test user experience with real users using wireframes/workflows/prototypes)
Testing (unit, integration, functional, accessibility)
Validation reports + error messages for users (leverage current check engine)
Integrate error message response into new UI
Business analysis
Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Monitoring Plan Requirements Package

Split feature Epic:
Emissioners UI design
Form validation
Import validation
Check engine validation (Most work)

Build test harness for check engine
Dwayne is verifying that .NET core check engine is valid


classpath functionality is broken on Windows 10

The startServer function attempts to concatenate the given classpath to the tika jar path with a colon. This is appropriate for Linux, but not for Windows where the correct character is the semicolon.
the problem lies (in part) on line 639 of tika.py:
    if classpath:
        classpath += ":" + tikaServerJar

should instead be:
    if classpath:
        if Windows:
            classpath += ";" + tikaServerJar
        else:
            classpath += ":" + tikaServerJar

The second half of this issue is that including a naked semicolon causes CLI parsing errors, so the whole classpath variable must be wrapped in quotes.

Fixed in https://github.com/chrismattmann/tika-python/commit/47aebcbe1c7d3f3a697d27fc64953f81eba0e4fa


fix(styles): LGCY-16 remove break all from notify

not sure how this got in for legacy only, removing it in any case
Closes LGCY-16

👍

@cy: this can be merged. Thanks!

@cy: this can get merged when you are ready. Thanks!


Fix issue where SliverPersistentHeader that is both floating and pinned would scroll down when scrolling past the beginning of the ScrollView

When SliverPersistentHeader is both floating and pinned, scrolling past the start of a scroll view would scroll the header down. When either option is false, the header would stick to the top. This PR fixes that issue.

@spkersten Thanks for the contribution. From the description alone I am not 100% sure I understand what you're trying to fix. A test that shows the erroneous behavior (or a reproducible code example, but test preferred) would be helpful.
The PersistentHeaders are tested via the sliver app bar tests. You can find them here:
https://github.com/flutter/flutter/blob/master/packages/flutter/test/widgets/slivers_appbar_floating_pinned_test.dart (and in the other sliver_appbar_*.dart files in the same location). Can you add a test with that information?

@goderbauer Maybe a video shows it best:
Bug:

With this PR:

@goderbauer I've been unable to reproduce the issue in a test. Using controller.jumpTo(-100.0); doesn't result in paintOrigin != 0, neither does this:
final TestGesture gesture = await tester.press(find.byType(Container));
await gesture.moveBy(const Offset(0, 20));

await tester.pumpAndSettle();
expect(render.geometry.paintOrigin, 0.0);

@spkersten I see. Can you post the (runnable) code you used in the videos posted above?

@spkersten In the test sample you posted in your comment above you probably just want to call pump instead of pumpAndSettle.
pumpAndSettle repeatedly calls pump until there are no longer any frames scheduled (see [1] https://mystuff.corp.google.com/stuff/items/1867). In your case, when it returns, the scrollable has already returned to its stable position (scrolled all the way to the top).
When you call pump it should just trigger one frame, so after that pump you should be in the state you want to be in, where the list is still slightly scrolled down.

This is the simplest example that shows the bug:
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) => MaterialApp(
        title: 'Flutter Demo',
        home: MyHomePage(),
      );
}

class MyHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) => CustomScrollView(
        slivers: <Widget>[
          SliverAppBar(
            pinned: true,
            floating: true,
          ),
          SliverToBoxAdapter(
            child: Container(
              height: 20,
              color: Colors.red,
            ),
          ),
        ],
      );
}

@goderbauer I finally managed to make the tests. (Using LiveWidgetController to put the tests in an app helped a lot to understand what was going on.) I've added them for the other flavours of SliverAppBar as well (pinned xor floating).


Compile Error on Download + Clean Build with Xcode 8.1

With Xcode 8.1
Download latest master
Build MongoKitten

Expected -
Builds.
Actual -
Two compiler errors (see attached).
Error text:  /MongoKitten-master 2/Sources/MongoKitten/Cursor.swift:70:32: Cannot convert value of type 'Int64' to expected dictionary value type 'Value'

I had that issue in another spot on another version of xcode but it appears to be happening in other spots as well, it seems to be a compile bug. In this case, change it to Value.int64(self.cursorID) or .int64(self.cursorID). The ~ is supposed to tell compiler it is a Value type but its not picking it up in certain situations. Make sure to remove ~ when you change it to .int64.

@wpccolorblind we ( @JustinM1 and I ) found the solution. Working on it!

Latest release should've fixed your problem

Confirmed fix with latest release.  Works great, you guys are amazing!

I'm closing the issue since it's fixed. Feel free to open this/another issue when you have a question/problem.


Major update and fixes

hot loading functionality fixed
updated dependencies
project structure changed for better fit with official docs: https://webpack.js.org/guides/hmr-react/#webpack-configuration

Was checking out this change locally, and I can't seem to load anything. Not sure if it's related to the removal of the index.html file just yet, I'll have more time to check it out tomorrow. Are you experiencing this locally as well?

@Trendy It works really fine for mine. What is actually the problem?

Responds with a 404 for me.
Here's my setup, not sure if it matters:
Node - 6.9.1
NPM - 3.10.10
WebPack - 2.6.1
TypeScript 2.3.3

This is what I see:

I've made a new PR with some changes, including updating dependencies and improving the build process (allow for builds which can be served statically, without webpack-dev-server). Please take a look and let me know if it is good for merging: https://github.com/Glavin001/react-hot-ts/pull/8
Thanks!

fixed! dist folder should not be ignored

The dist/ folder, should be ignored 😛 . I think there is still something wrong.
We should be able to delete the dist/ folder at any time and rebuild from scratch.

Depends how much you want to be consistent with official documentation, up to you.

The official documentation recommends committing the dist/ folder, including generated files, to Git? Well then... looks like we will have to deviate 😛 . I appreciate you looking into this and clarifying/

Actually, it is only dist/index.html not all of dist/, which is what this PR currently suggests. I would expect to see the following in the .gitignore instead:
dist/*
dist/index.html

See https://stackoverflow.com/a/16318111/2578205 for details.
This would be something I could accept. However, I have already opted to use html-webpack-plugin instead since it provides more flexibility in long run. This has since been merged.
Take a look at the current state of this repository and see what changes you still would like to make. I tried to update some things you did, such as dependencies.
Thank you for contributing! 😃

@Dharmoslap The official documentation for HMR/React mentions them choosing to include the index.html file in the /dist folder, so that things would run properly. I don't think that it was meant to be a requirement of code folder structure.
Personally, I'd include index.html outside of the /dist folder, which could potentially include files built with modifications not relevant to this project. I think that @Glavin001 did this in #8 and in the original project.

@Trendy Of course I got that, but that means that anybody who starts with official documentation and later would move to TS will have to change folder structure just to try to follow this demo, which is dumb. As I  understood the purpose of this repo was not to give you the ideal folder structure for your project (neither to make you switch to use https://github.com/jantimon/html-webpack-plugin), but rather to be the fastest way to get react hot reload working with TS. I'm closing this, thanks.


Replaced azure-pipelines-tasks-azurermdeploycommon with arm-rest-v2

Task name: AzureWebAppContainerV1
Description: Replaced azure-pipelines-tasks-azurermdeploycommon with arm-rest-v2
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) N
Checklist:

[x] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

/azp run

/azp run


Any plan to release the collected dataset?

Dear Dr. Abbasloo. Firstly, thank you for this really fantastic work. I was wondering if you have any plan to release the collected pool of policies with 60 million data points. It will greatly advance this research field. Thanks!

Hi @mrbeann, thx for ur kind words.
We've already released the tools to generate the dataset here. That said, currently there is no plan to release the dataset itself.


⚠ Bofrost.lu has degraded performance

In b990afa, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1119 ms

Resolved: Bofrost.lu performance has improved in 39ba6b9.


[FR] Commands to apply format options to selected text

Currently one can say "quote that" to add quotes to selected text.
I propose commands like 'snake that' to apply formatting to selected text (there could be one command per formatter).

We've got this one already, try out 'title smash that' for example. The code in question is misc/formatters.talon:8

Ah, my bad, I tried it earlier, but you're totally right, it's working for me.
Cheers @splondike


Revert "KEB resumes update operations"

Reverts kyma-project/control-plane#1105

Reverting as this probably introduces memory leak in KEB:
kubectl top pod -n kcp-system kcp-kyma-environment-broker-5694bbc7f-ms2cl
NAME                                          CPU(cores)   MEMORY(bytes)
kcp-kyma-environment-broker-5694bbc7f-ms2cl   1010m        3944Mi

/test pre-main-control-plane-reconciler-e2e


Search Contributions page added

Description
feat: Enhance Search Contributions Page with Advanced Filtering & Code View
This update brings significant enhancements to the Search Contributions Page, aimed at enriching user interaction and functionality:

Introduced a comprehensive contributions table displaying contributor names, images, and essential metrics such as week, year, and month of contribution, alongside the programming languages used (e.g., Python, JavaScript).
Implemented a 'viewCode' functionality, enabling users to inspect a contributor's code through a modal/pop-up, offering a deeper dive into individual contributions.
Advanced filtering capabilities have been developed, allowing users to effectively sort and filter contributors based on various criteria, including weekly, yearly, and monthly contributions, as well as by programming languages.
The introduction of a dynamic filtering system, termed the search fielding pattern, permits users to customize searches across different columns, thus enhancing the flexibility and usability of the page for exploring contributions.

These improvements are designed to make the Search Contributions Page a more dynamic and insightful platform for recognizing and exploring the valuable contributions within our community, thereby increasing engagement and visibility for our contributors' efforts.
Type of Change

[ x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Changes

Please which part of the project your changes affect ?

[ x] Frontend (Templates, CSS, JS)
[ ] Backend (Dancer2, api-docs, Dockerfile)

Thanks for your contributions. @fahad-albasrawie


Single-sided mods

Hello, I'm the developer and maintainer of a mod called Fabric Console. I'm currently bringing the project up to date, which means I've updated Mod Menu to the latest 1.16 version (for now), 1.16.22.
It seems that the mod now lacks the option to specify a mod as client-side-only if it also supports the server, which does make sense. However, Fabric Console is purely a single-sided mod - it adds no new content, and simply allows for color in the console (dedicated server or client alike). In this case I still feel it's important to be able to articulate the fact that it is not required for both server & client to have this mod installed.
I propose a new custom field (name TBD) to specify that a mod requires no interaction between client & server. This would replace the "modmenu:clientsideOnly" field that is being deprecated & removed soon.

I'm not a dev and I might be wrong but according to the wiki ModMenu now uses https://github.com/TerraformersMC/ModMenu/blob/1.17/src/main/resources/fabric.mod.json#L6

There are more badges, such as the Client badge, but this is automatically determined by the environment defined in the official fabric.mod.json metadata. Only the ones above can be manually assigned in the badges array.

I'm not a dev and I might be wrong but according to the wiki ModMenu now uses https://github.com/TerraformersMC/ModMenu/blob/1.17/src/main/resources/fabric.mod.json#L6

There are more badges, such as the Client badge, but this is automatically determined by the environment defined in the official fabric.mod.json metadata. Only the ones above can be manually assigned in the badges array.

Yes, I am pointing this out and saying that it is not adequate in this case. Fabric Console can run on either client or server, and it is completely independant that way. I'm asking for a badge or something that I can use to specify this. I used modmenu:clientsideOnly in the past, but that's deprecated.

This is a valid use case and should be supported. Thank you for raising this issue!
It might be possible to achieve this by specifying the environment as client and server instead of * and checking that the environment is client (current behavior) or contains client. I'll look into it.

The fabric.mod.json v1 spec allows a string or an array of strings but Fabric Loader 0.14.8 does not support an array of strings, it only supports *, client, and server (see here and here).


Add more error logs for sync controller & kubefedcluster controller

What this PR does / why we need it:
Add more error logs for sync controller & kubefedcluster controller, which can be useful to debug.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1407

/cc @hectorj2f

@irfanurrehman could you take a look at this pr when you are free?

Thanks for doing this @yuswift
/lgtm

/approve


Refactoring plan standard compile

Prior to work on incremental compilation, refactor planStandardCompile in order to clarify causality chains.
Does change the order of planned jobs in jobs, but I believe that isn't the scheduled order, anyway.
Passing some mutable state around via "add" functions to clarify that the callee is only adding to the collections in question.

@swift-ci please test

@DougGregor This is the same thing you already reviewed. It seems that I had to redo the PR after the master-main switch. Thanks!


Update README.md File

Along with editing some features in css, I completely updated the README.md file. It was not descriptive before now it is more personalized.

🏮 I'm sorry, there was a mistake in the review 🙏 and I didn't point out this 👇
Please kindly update the font style of I'm Hasenet to match the font in the Figma template as mentioned in the project requirement
Your design 👇

Figma 👇


Sans JSON Serialization

First steps to completely remove the out-of-the-box JSON serialization support.
I added an example how to achieve the same old API functionality.
This should close #12
Thanks to @ThomasSevestre  and @christophersansone for helping with this!

@stas Is this good to be merged?

@oyeanuj yep, I should merge it, was trying to orchestrate it a bit together with other updates...

Merged into the wrong branch, so I updated it manually... :see_no_evil:

Was hit by the Deprecation warning today, tried to follow changes in README and hit some issues. I left comments on the PR commit code where things are amiss.

Thanks @nicbet, but this is long ago fixed on master. In future, could you please open a separate issue, it's a bit hard to follow the conversations after the PRs are merged. :bow:


Creating Workspaces using API do not create roles

Summary
When I create a workspace using the Admin portal, the default four roles gets created as mentioned here.
But the four roles and corresponding permissions do not get created when I create using the rest API. Am I missing something?
Steps To Reproduce

Spin up Kong 1.3 with RBAC on

enforce_rbac = on
admin_gui_auth = basic-auth
admin_gui_session_conf = { "cookie_secure": false }
admin_gui_auth_conf = { "hide_credentials": true }
admin_gui_url = http://localhost:8002

Create a new workspace using Admin Portal. The default four roles (workspace-admin, workspace-portal-admin, workspace-super-admin, workspace-read-only) gets created automatically

Create a new workspace using a API. This just creates a workspaces, not the default roles.

$ curl -X POST \
  -H "Kong-Admin-Token: <some_password>" \
  --url http://localhost:8001/workspaces \
  --data 'name=<workspace_name>'

This is not a huge blocker, since I can still use Rest API to create roles and add permissions to it, but it would be nice to have the same behaviour using GUI and API.
Additional Details & Logs

Kong version: 1.3.1
Operating system: CentOS 7

Hi @vikas027, thanks for reporting. GitHub issues are reserved for Kong open-source bug tracking. For Kong Enterprise, please direct your questions to<EMAIL_ADDRESS>Thank you!


Prevent "Go to next Page" till condition is fulfilled?

Hi,
is there any way to prevent swiping to next page, till some condition (e.g. list size > 0) is fulfilled?
Any help would be appreciated! Thanks!

I think you can manage it in your mobile app directly, through these props:

onNextBtnClick -> check the condition if is fulfilled
scrollEnabled  -> in this case maybe better to disable the scroll

I close the issue, in case there are problems open again


Remove Bintray and jcenter

[x] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] This pull request is on the dev branch.
[x] I used gofmt for formatting the code before submitting the pull request.

Reminder -
Let's make sure not merge this into the master branch for jfrog-cli-core, so that it doesn't impact jfrog-cli v1.


Add Three-point arc tool

Add a sketch tool that generates an arbitrary arc for the user.
User flow

In sketch mode, click the Arc tool

After this issue is complete, the Three-point arc should be the default Arc tool, with tangential arc in a dropdown per #1645

Click anywhere on the sketch plane to lay your first point
Move the mouse around to find the place for the second point

During this, a sensible radius is set for the user, the center of the circle implied by the arc is shown as a draft dot, and a draft arc spans between the first point and the mouse's location

Move the mouse around to find the place for the final point

During this, we draw a draft arc that passes through the two previous points and the mouse's location (along with another dot representing the center of this implied circle), updating as the mouse moves.

Code generation
We don't have a stdlib function in kcl that takes three points and constructs an arc that passes through them, which is fine because users don't actually want the relationship to be defined by 3 cartesian points in almost all cases. They want an arc with a starting point, a radius, and sweep angle. Unfortunately, I don't think we have a variation of the arc() function that takes these parameters. Maybe someone else knows how we can use the user flow described above to derive one of the arc functions we have available before I request a new function?
Additional resources

The existing Arc icon is already in-use in the app and is available in Figma here.
Calculating a circle from three points in Math StackExchange

Being able to use the line tool like in figma to click and create an arc, would be a win

Related to https://github.com/KittyCAD/engine/issues/2756


[🐞] Qwik is slow when used first time

Which component is affected?
Qwik Runtime
Describe the bug
When you visit qwik website first time every action (button click, menu open) has a delay from 0.1-1 sec. Which makes qwik a slow website from user perspective.
Reproduction
https://qwikui.com/docs/styled/introduction/
Steps to reproduce
Open qwik-ui website anc click around on menu or any component, you will feel a delay. This will work only if you not visited it previously. You can try phone or tablet.
System Info
-

Additional Information
No response

"Feels" qwik to me ;)
Can you share what device or devices you are using? iOS, PC, Tablet, Android... ?
Have you checked your network? That might be the issue 😅

@wanjohiryan it's android tablet, phone, windows linux pc. I have no problem with internet, it's super fast.  In my opinion it's a major flaw in qwik architecture.
What options do we have to solve this?

Prefetch component on hover
Give user ability to define if component should be prefetched (on page load, when it's in view and so on)
Bundle components data together so that one click on menu button will not trigger 20+ requests to load every single part of it like function separately.

I tried it and it was VERY slow on my Android via Chrome. On my Windows PC via Chrome it was fast.

Having the same issues.
The Qwik site itself is a good example: usually the first thing I want to do is search the docs, but there are 2-3 seconds where nothing happens at all. (This is on a fresh load only, after a Cmd+Shift+R refresh it's 300ms to download those JS files.)
Our app users have the same issues and it's frustrating for them.
When I'm looking at the network requests, it looks like all the q-data.json for the <Link>ed pages are being fetched, but not all the modules, resulting in a waterfall on the first click. In this case I looked at it's fetching 80 JS files.
(Admittedly, my ~200ms server latency isn't helping, but still. SSR page loads feel instant.)
Did I set up something wrong? Can I signal to the prefetcher that it can basically keep prefetching anything it notices?
Would it make sense for the optimizer to bundle some of these tiny modules? That would probably be a decent trade-off with the potential extra code being downloaded.
I added Insights but it looks like that's being refactored and the site is down, I'm assuming that's being reworked for Qwik 2.0.
For now, I've added a qsymbol event listener that pops up a little loading spinner in the corner for half a second, hopefully that helps users a bit 😊 (Ideally buttons would get disabled during symbol load of their onClick$ / navigation handling, but I don't know if I can do that.)
Loving the framework overall! Would be amazing if there was a great solution to this.

I dug around a little.
On the docs side, it looks like the prefetching is disabled (which actually is the case by default on all apps, if I'm reading the code correctly):
https://github.com/QwikDev/qwik/blob/b183a8b30c96c19eabf7fd65ab1ba7f837f81410/packages/docs/src/entry.ssr.tsx#L24-L27
Sooo @maiieul how's the experiment been going?
Adding this to my root.tsx seems to help a lot! Though I don't know what I'm doing and I have no idea if this is okay, or interfering with the "normal" service worker or something.
        {!isDev && <PrefetchServiceWorker />}
        {!isDev && <PrefetchGraph />}

By the way, that qwikPrefetchServiceWorker render setting—does it do anything? I'm just rummaging through the code here on GitHub but couldn't find any place where it's used.
Even without the option, my app was emitting a qwikPrefetchSW array in the HTML.
I any case, if it's true that the prefetching (which IMO is a key element of making Qwik apps nicely responsive) is disabled by default, we should document that.


[Icon Request] ai

Icon Type

[x] Folder
[x] File

Folder Names

ai
AI
Ai

File Names

ai
AI
Ai

Graphic ideas

Brain
Robot

Ai folder might make sense, but I'm wondering where you're having files called "ai", or is there an "ai" file extension? Do you know files which are like "myFile.ai"?

If the suggestion is to add an icon for the .ai extension, we should keep in mind that the .ai is also used by Adobe Illustrator for their native vector file format.

Hi guys, in fact as a frontend engineer who uses AI in the project, I get used to separating the AI related stuff in different folder:

configuration.
Model tools
Model Schema
...

Example: sdk.vercel.ai

What would be the contents of such a file? Is there a library that needs such extensions? Because ai is usually used by AdobeIllustrator.


web/api: cant update settings

also applies to updating a persons name

fixed in latest api/web release.


Add temporary backwards-compatible endpoints

This is a temporary feature that will help consumers of the API to migrate to the new trailing slash endpoints.

@BryonLewis I took another shot at this and got it to work - I propose that we merge this and do a deploy, then let everyone know about the breaking change, and then we can remove them in the next deployment.


CC and BCC Not Working

Given the following code:
$client = new SendGrid('user', 'password');

$email = new SendGrid\Email();
$email->setFrom('example@example.com');
$email->setFromName('Example');
<EMAIL_ADDRESS>'Name');
$email->setText('Hello, world');
$email->setSubject('Test Subject');
$email->addCc('foo@example.com');

var_dump($client->send($email));

I get the following exception:
ErrorException in SendGrid.php line 51:
Array to string conversion

This also happens when trying to use BCC.
I'm using the following in my composer.json:
{
    "require": {
        "sendgrid/sendgrid": "~2.2"
    }
}

How do I fix this?

No reply to this yet? This seems like a pretty important feature for an e-mail provider and their associated client library...

Thanks for the report. We are aware of the problem and are working on it.

I have a pre-release up of v3.0.0 that should fix all of these issues. Would love some testers to provide feedback.
I need to write up the changes and a better README, but here's a primer.
"sendgrid/sendgrid": "3.0.0-RC1" in composer.
https://github.com/sendgrid/sendgrid-php/releases/tag/v3.0.0-RC1


#ask examples in README do not contain any examples with prompts

See also https://github.com/adhearsion/adhearsion-website/pull/35/files#diff-bb0353700dbb627ef623b00b6497300cL221, which is where these docs are moving to for Adhearsion 3.


transfrag [sf#119]

Reported by eilbeck on 2008-09-10 18:41 UTC
The modencode group have requested a term to describe translated fragments.
This would be a kind of experimental region probably.
Email:
> The use case in "transfrags: from tiling array experiments.  There are
> tiny regions we know are transcribed based on experimental evidence,
> but not necessarily anything about the entire transcript(s) from which
> they are derived.  They may   correspond to known or unknown exons,
> UTRs, ncRNAs, etc but the nature of the experiment is such that they
> are a class of evidence for the thing, not the thing itself.
Just to clarify a bit, the "transfrags" are computed features based on
significantly overrepresented probes on a tiling array.   Each
transfrag would typically have > 1 probe represented but the fidelity
of edges, when compared to actual transcriptss, is limited by the
resolution and the array.

Commented by eilbeck on 2008-09-18 16:55 UTC
I have added this as a child of experimental_output_artefact.
I called it transcribed_fragment and left transfrag as the synonym. If you want me to switch this around, let me know.
--Karen

Updated by eilbeck on 2008-09-18 16:55 UTC

status: open --> closed-accepted


Fixed example in README.md

I just fixed the example in the README.md with the correct name for the GITHUB_TOKEN env variable plus I suggest to give a name to the workflow in order to do not visualize .github/workflows/scala-steward.yml as the action name

Hi @TonioGela! Thank you very much :)
I agree with the name change, but the secret is intended to be REPOSITORY_GITHUB_TOKEN (or any other PAT), instead of the default GITHUB_TOKEN since using the default token doesn't trigger new workflows. This is further explained in the Github Token section of the README.

My bad about the token, I haven't fully read the README, I'm sorry :(
I'll fix the PR with a new commit, thanks!


Limit maximum number of redis connections

Right now, there is no limit maximum connection to redis. We should keep this number small enough, otherwise, it will throw error when we set number of workers is large:
Err max number of clients reached

I set default maximum active connection to 20.

Look at this PR that has been merged: https://github.com/gocelery/gocelery/pull/128


Apple Rejects build with Hermes on

Description
I have upgraded RN up to 0.67.3, then build archive for App Store Connect with Hermes enabled in Podfile, Archive was build successfully but apple still reject the build.
Here is apple's response:
We identified one or more issues with a recent delivery for your app, "APP" 3.2.2 (2). Please correct the following issues, then upload again.
ITMS-90338: Non-public API usage - The app references non-public selectors in APP: addStream:, dataChanged, initWithBuffer:rotation:timeStampNs:, initWithURLStrings:, isBinary, isPassthrough, localDescription, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, removeValuesForKeys:completion:, sdp, sendData:, setChannelId:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, stringForType:, typeForString:, videoSource,The app contains one or more corrupted binaries. Rebuild the app and resubmit.. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Then I tried without Hermes and build was accepted.
here is my podfile:
PODS:
  - boost (1.76.0)
  - CocoaAsyncSocket (7.6.5)
  - DoubleConversion (1.1.6)
  - FBLazyVector (0.67.3)
  - FBReactNativeSpec (0.67.3):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTRequired (= 0.67.3)
    - RCTTypeSafety (= 0.67.3)
    - React-Core (= 0.67.3)
    - React-jsi (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - FBSDKCoreKit (9.3.0):
    - FBSDKCoreKit/Basics (= 9.3.0)
    - FBSDKCoreKit/Core (= 9.3.0)
  - FBSDKCoreKit/Basics (9.3.0)
  - FBSDKCoreKit/Core (9.3.0):
    - FBSDKCoreKit/Basics
  - FBSDKLoginKit (9.3.0):
    - FBSDKLoginKit/Login (= 9.3.0)
  - FBSDKLoginKit/Login (9.3.0):
    - FBSDKCoreKit (~> 9.3.0)
  - FBSDKShareKit (9.3.0):
    - FBSDKShareKit/Share (= 9.3.0)
  - FBSDKShareKit/Share (9.3.0):
    - FBSDKCoreKit (~> 9.3.0)
  - Firebase/AnalyticsWithoutAdIdSupport (8.12.1):
    - Firebase/CoreOnly
    - FirebaseAnalytics/WithoutAdIdSupport (~> 8.12.0)
  - Firebase/CoreOnly (8.12.1):
    - FirebaseCore (= 8.12.1)
  - Firebase/Crashlytics (8.12.1):
    - Firebase/CoreOnly
    - FirebaseCrashlytics (~> 8.12.0)
  - Firebase/DynamicLinks (8.12.1):
    - Firebase/CoreOnly
    - FirebaseDynamicLinks (~> 8.12.0)
  - Firebase/InAppMessaging (8.12.1):
    - Firebase/CoreOnly
    - FirebaseInAppMessaging (~> 8.12.0-beta)
  - Firebase/Messaging (8.12.1):
    - Firebase/CoreOnly
    - FirebaseMessaging (~> 8.12.0)
  - FirebaseABTesting (8.12.0):
    - FirebaseCore (~> 8.0)
  - FirebaseAnalytics/WithoutAdIdSupport (8.12.0):
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleAppMeasurement/WithoutAdIdSupport (= 8.12.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (~> 2.30908.0)
  - FirebaseCore (8.12.1):
    - FirebaseCoreDiagnostics (~> 8.0)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Logger (~> 7.7)
  - FirebaseCoreDiagnostics (8.12.0):
    - GoogleDataTransport (~> 9.1)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Logger (~> 7.7)
    - nanopb (~> 2.30908.0)
  - FirebaseCrashlytics (8.12.0):
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleDataTransport (~> 9.1)
    - GoogleUtilities/Environment (~> 7.7)
    - nanopb (~> 2.30908.0)
    - PromisesObjC (< 3.0, >= 1.2)
  - FirebaseDynamicLinks (8.12.0):
    - FirebaseCore (~> 8.0)
  - FirebaseInAppMessaging (8.12.0-beta):
    - FirebaseABTesting (~> 8.0)
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleUtilities/Environment (~> 7.7)
    - nanopb (~> 2.30908.0)
  - FirebaseInstallations (8.12.0):
    - FirebaseCore (~> 8.0)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/UserDefaults (~> 7.7)
    - PromisesObjC (< 3.0, >= 1.2)
  - FirebaseMessaging (8.12.0):
    - FirebaseCore (~> 8.0)
    - FirebaseInstallations (~> 8.0)
    - GoogleDataTransport (~> 9.1)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Reachability (~> 7.7)
    - GoogleUtilities/UserDefaults (~> 7.7)
    - nanopb (~> 2.30908.0)
  - Flipper (0.99.0):
    - Flipper-Folly (~> 2.6)
    - Flipper-RSocket (~> 1.4)
  - Flipper-Boost-iOSX (<IP_ADDRESS>.11)
  - Flipper-DoubleConversion (3.1.7)
  - Flipper-Fmt (7.1.7)
  - Flipper-Folly (2.6.7):
    - Flipper-Boost-iOSX
    - Flipper-DoubleConversion
    - Flipper-Fmt (= 7.1.7)
    - Flipper-Glog
    - libevent (~> 2.1.12)
    - OpenSSL-Universal (= 1.1.180)
  - Flipper-Glog (0.3.6)
  - Flipper-PeerTalk (0.0.4)
  - Flipper-RSocket (1.4.3):
    - Flipper-Folly (~> 2.6)
  - FlipperKit (0.99.0):
    - FlipperKit/Core (= 0.99.0)
  - FlipperKit/Core (0.99.0):
    - Flipper (~> 0.99.0)
    - FlipperKit/CppBridge
    - FlipperKit/FBCxxFollyDynamicConvert
    - FlipperKit/FBDefines
    - FlipperKit/FKPortForwarding
  - FlipperKit/CppBridge (0.99.0):
    - Flipper (~> 0.99.0)
  - FlipperKit/FBCxxFollyDynamicConvert (0.99.0):
    - Flipper-Folly (~> 2.6)
  - FlipperKit/FBDefines (0.99.0)
  - FlipperKit/FKPortForwarding (0.99.0):
    - CocoaAsyncSocket (~> 7.6)
    - Flipper-PeerTalk (~> 0.0.4)
  - FlipperKit/FlipperKitHighlightOverlay (0.99.0)
  - FlipperKit/FlipperKitLayoutHelpers (0.99.0):
    - FlipperKit/Core
    - FlipperKit/FlipperKitHighlightOverlay
    - FlipperKit/FlipperKitLayoutTextSearchable
  - FlipperKit/FlipperKitLayoutIOSDescriptors (0.99.0):
    - FlipperKit/Core
    - FlipperKit/FlipperKitHighlightOverlay
    - FlipperKit/FlipperKitLayoutHelpers
    - YogaKit (~> 1.18)
  - FlipperKit/FlipperKitLayoutPlugin (0.99.0):
    - FlipperKit/Core
    - FlipperKit/FlipperKitHighlightOverlay
    - FlipperKit/FlipperKitLayoutHelpers
    - FlipperKit/FlipperKitLayoutIOSDescriptors
    - FlipperKit/FlipperKitLayoutTextSearchable
    - YogaKit (~> 1.18)
  - FlipperKit/FlipperKitLayoutTextSearchable (0.99.0)
  - FlipperKit/FlipperKitNetworkPlugin (0.99.0):
    - FlipperKit/Core
  - FlipperKit/FlipperKitReactPlugin (0.99.0):
    - FlipperKit/Core
  - FlipperKit/FlipperKitUserDefaultsPlugin (0.99.0):
    - FlipperKit/Core
  - FlipperKit/SKIOSNetworkPlugin (0.99.0):
    - FlipperKit/Core
    - FlipperKit/FlipperKitNetworkPlugin
  - fmt (6.2.1)
  - glog (0.3.5)
  - Google-Maps-iOS-Utils (2.1.0):
    - Google-Maps-iOS-Utils/Clustering (= 2.1.0)
    - Google-Maps-iOS-Utils/Geometry (= 2.1.0)
    - Google-Maps-iOS-Utils/Heatmap (= 2.1.0)
    - Google-Maps-iOS-Utils/QuadTree (= 2.1.0)
    - GoogleMaps
  - Google-Maps-iOS-Utils/Clustering (2.1.0):
    - Google-Maps-iOS-Utils/QuadTree
    - GoogleMaps
  - Google-Maps-iOS-Utils/Geometry (2.1.0):
    - GoogleMaps
  - Google-Maps-iOS-Utils/Heatmap (2.1.0):
    - Google-Maps-iOS-Utils/QuadTree
    - GoogleMaps
  - Google-Maps-iOS-Utils/QuadTree (2.1.0):
    - GoogleMaps
  - GoogleAppMeasurement/WithoutAdIdSupport (8.12.0):
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (~> 2.30908.0)
  - GoogleDataTransport (9.1.2):
    - GoogleUtilities/Environment (~> 7.2)
    - nanopb (~> 2.30908.0)
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleMaps (3.5.0):
    - GoogleMaps/Maps (= 3.5.0)
  - GoogleMaps/Base (3.5.0)
  - GoogleMaps/Maps (3.5.0):
    - GoogleMaps/Base
  - GoogleUtilities/AppDelegateSwizzler (7.7.0):
    - GoogleUtilities/Environment
    - GoogleUtilities/Logger
    - GoogleUtilities/Network
  - GoogleUtilities/Environment (7.7.0):
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleUtilities/Logger (7.7.0):
    - GoogleUtilities/Environment
  - GoogleUtilities/MethodSwizzler (7.7.0):
    - GoogleUtilities/Logger
  - GoogleUtilities/Network (7.7.0):
    - GoogleUtilities/Logger
    - "GoogleUtilities/NSData+zlib"
    - GoogleUtilities/Reachability
  - "GoogleUtilities/NSData+zlib (7.7.0)"
  - GoogleUtilities/Reachability (7.7.0):
    - GoogleUtilities/Logger
  - GoogleUtilities/UserDefaults (7.7.0):
    - GoogleUtilities/Logger
  - libevent (2.1.12)
  - libwebp (1.2.1):
    - libwebp/demux (= 1.2.1)
    - libwebp/mux (= 1.2.1)
    - libwebp/webp (= 1.2.1)
  - libwebp/demux (1.2.1):
    - libwebp/webp
  - libwebp/mux (1.2.1):
    - libwebp/demux
  - libwebp/webp (1.2.1)
  - nanopb (2.30908.0):
    - nanopb/decode (= 2.30908.0)
    - nanopb/encode (= 2.30908.0)
  - nanopb/decode (2.30908.0)
  - nanopb/encode (2.30908.0)
  - OpenSSL-Universal (1.1.180)
  - Permission-AppTrackingTransparency (3.0.4):
    - RNPermissions
  - Permission-Camera (3.0.4):
    - RNPermissions
  - Permission-Microphone (3.0.4):
    - RNPermissions
  - PromisesObjC (2.0.0)
  - RCT-Folly (2<IP_ADDRESS>-v2):
    - boost
    - DoubleConversion
    - fmt (~> 6.2.1)
    - glog
    - RCT-Folly/Default (= 2<IP_ADDRESS>-v2)
  - RCT-Folly/Default (2<IP_ADDRESS>-v2):
    - boost
    - DoubleConversion
    - fmt (~> 6.2.1)
    - glog
  - RCTRequired (0.67.3)
  - RCTTypeSafety (0.67.3):
    - FBLazyVector (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTRequired (= 0.67.3)
    - React-Core (= 0.67.3)
  - React (0.67.3):
    - React-Core (= 0.67.3)
    - React-Core/DevSupport (= 0.67.3)
    - React-Core/RCTWebSocket (= 0.67.3)
    - React-RCTActionSheet (= 0.67.3)
    - React-RCTAnimation (= 0.67.3)
    - React-RCTBlob (= 0.67.3)
    - React-RCTImage (= 0.67.3)
    - React-RCTLinking (= 0.67.3)
    - React-RCTNetwork (= 0.67.3)
    - React-RCTSettings (= 0.67.3)
    - React-RCTText (= 0.67.3)
    - React-RCTVibration (= 0.67.3)
  - React-callinvoker (0.67.3)
  - React-Core (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default (= 0.67.3)
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/CoreModulesHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/Default (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/DevSupport (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default (= 0.67.3)
    - React-Core/RCTWebSocket (= 0.67.3)
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-jsinspector (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTActionSheetHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTAnimationHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTBlobHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTImageHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTLinkingHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTNetworkHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTSettingsHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTTextHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTVibrationHeaders (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-Core/RCTWebSocket (0.67.3):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default (= 0.67.3)
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsiexecutor (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - Yoga
  - React-CoreModules (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.67.3)
    - React-Core/CoreModulesHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-RCTImage (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-cxxreact (0.67.3):
    - boost (= 1.76.0)
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-callinvoker (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-jsinspector (= 0.67.3)
    - React-logger (= 0.67.3)
    - React-perflogger (= 0.67.3)
    - React-runtimeexecutor (= 0.67.3)
  - React-jsi (0.67.3):
    - boost (= 1.76.0)
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-jsi/Default (= 0.67.3)
  - React-jsi/Default (0.67.3):
    - boost (= 1.76.0)
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
  - React-jsiexecutor (0.67.3):
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-perflogger (= 0.67.3)
  - React-jsinspector (0.67.3)
  - React-logger (0.67.3):
    - glog
  - react-native-document-picker (3.5.4):
    - React
  - react-native-fbsdk-next (4.6.0):
    - React-Core
    - react-native-fbsdk-next/Core (= 4.6.0)
    - react-native-fbsdk-next/Login (= 4.6.0)
    - react-native-fbsdk-next/Share (= 4.6.0)
  - react-native-fbsdk-next/Core (4.6.0):
    - FBSDKCoreKit (~> 9.3)
    - React-Core
  - react-native-fbsdk-next/Login (4.6.0):
    - FBSDKLoginKit (~> 9.3)
    - React-Core
  - react-native-fbsdk-next/Share (4.6.0):
    - FBSDKShareKit (~> 9.3)
    - React-Core
  - react-native-geolocation (2.0.2):
    - React
  - react-native-google-maps (0.27.1):
    - Google-Maps-iOS-Utils (= 2.1.0)
    - GoogleMaps (= 3.5.0)
    - React
  - react-native-html-to-pdf-lite (0.9.1):
    - React
  - react-native-image-picker (1.1.0):
    - React
  - react-native-maps (0.27.1):
    - React
  - react-native-netinfo (5.9.7):
    - React-Core
  - react-native-pdf (6.3.0):
    - React-Core
  - react-native-progress-bar-android (1.0.4):
    - React
  - react-native-progress-view (1.2.4):
    - React
  - react-native-rsa-native (1.1.4):
    - React
  - react-native-safe-area-context (3.1.7):
    - React
  - react-native-splash-screen (3.2.0):
    - React
  - react-native-webrtc (1.98.0):
    - React-Core
  - react-native-webview (11.17.2):
    - React-Core
  - React-perflogger (0.67.3)
  - React-RCTActionSheet (0.67.3):
    - React-Core/RCTActionSheetHeaders (= 0.67.3)
  - React-RCTAnimation (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.67.3)
    - React-Core/RCTAnimationHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-RCTBlob (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/RCTBlobHeaders (= 0.67.3)
    - React-Core/RCTWebSocket (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-RCTNetwork (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-RCTImage (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.67.3)
    - React-Core/RCTImageHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-RCTNetwork (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-RCTLinking (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - React-Core/RCTLinkingHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-RCTNetwork (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.67.3)
    - React-Core/RCTNetworkHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-RCTSettings (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.67.3)
    - React-Core/RCTSettingsHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-RCTText (0.67.3):
    - React-Core/RCTTextHeaders (= 0.67.3)
  - React-RCTVibration (0.67.3):
    - FBReactNativeSpec (= 0.67.3)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/RCTVibrationHeaders (= 0.67.3)
    - React-jsi (= 0.67.3)
    - ReactCommon/turbomodule/core (= 0.67.3)
  - React-runtimeexecutor (0.67.3):
    - React-jsi (= 0.67.3)
  - ReactCommon/turbomodule/core (0.67.3):
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-callinvoker (= 0.67.3)
    - React-Core (= 0.67.3)
    - React-cxxreact (= 0.67.3)
    - React-jsi (= 0.67.3)
    - React-logger (= 0.67.3)
    - React-perflogger (= 0.67.3)
  - ReactNativeART (1.2.0):
    - React
  - ReactNativeIncallManager (3.3.0):
    - React
  - rn-fetch-blob (0.12.0):
    - React-Core
  - RNCAsyncStorage (1.12.0):
    - React
  - RNCClipboard (1.5.1):
    - React-Core
  - RNCMaskedView (0.1.10):
    - React
  - RNCPicker (2.3.1):
    - React-Core
  - RNDateTimePicker (3.0.2):
    - React
  - RNDeviceInfo (5.6.5):
    - React
  - RNFastImage (8.3.2):
    - React
    - SDWebImage (~> 5.8)
    - SDWebImageWebPCoder (~> 0.6.1)
  - RNFBAnalytics (14.5.1):
    - Firebase/AnalyticsWithoutAdIdSupport (= 8.12.1)
    - React-Core
    - RNFBApp
  - RNFBApp (14.5.1):
    - Firebase/CoreOnly (= 8.12.1)
    - React-Core
  - RNFBCrashlytics (14.5.1):
    - Firebase/Crashlytics (= 8.12.1)
    - React-Core
    - RNFBApp
  - RNFBDynamicLinks (14.5.1):
    - Firebase/DynamicLinks (= 8.12.1)
    - GoogleUtilities/AppDelegateSwizzler
    - React-Core
    - RNFBApp
  - RNFBInAppMessaging (14.5.1):
    - Firebase/InAppMessaging (= 8.12.1)
    - React-Core
    - RNFBApp
  - RNFBMessaging (14.5.1):
    - Firebase/Messaging (= 8.12.1)
    - React-Core
    - RNFBApp
  - RNFS (2.16.6):
    - React
  - RNGestureHandler (1.8.0):
    - React
  - RNKeychain (4.0.5):
    - React
  - RNLocalize (1.4.1):
    - React
  - RNPermissions (3.0.4):
    - React-Core
  - RNReanimated (1.13.4):
    - React-Core
  - RNScreens (3.13.1):
    - React-Core
    - React-RCTImage
  - RNSVG (9.4.0):
    - React
  - SDWebImage (5.12.3):
    - SDWebImage/Core (= 5.12.3)
  - SDWebImage/Core (5.12.3)
  - SDWebImageWebPCoder (0.6.1):
    - libwebp (~> 1.0)
    - SDWebImage/Core (~> 5.7)
  - Smartlook (1.8.5)
  - smartlook-react-native-bridge (1.2.3):
    - React
    - Smartlook (~> 1.8.3)
  - TouchID (4.4.1):
    - React
  - Yoga (1.14.0)
  - YogaKit (1.18.1):
    - Yoga (~> 1.14)

DEPENDENCIES:
  - boost (from `../node_modules/react-native/third-party-podspecs/boost.podspec`)
  - DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`)
  - FBLazyVector (from `../node_modules/react-native/Libraries/FBLazyVector`)
  - FBReactNativeSpec (from `../node_modules/react-native/React/FBReactNativeSpec`)
  - Flipper (= 0.99.0)
  - Flipper-Boost-iOSX (= <IP_ADDRESS>.11)
  - Flipper-DoubleConversion (= 3.1.7)
  - Flipper-Fmt (= 7.1.7)
  - Flipper-Folly (= 2.6.7)
  - Flipper-Glog (= 0.3.6)
  - Flipper-PeerTalk (= 0.0.4)
  - Flipper-RSocket (= 1.4.3)
  - FlipperKit (= 0.99.0)
  - FlipperKit/Core (= 0.99.0)
  - FlipperKit/CppBridge (= 0.99.0)
  - FlipperKit/FBCxxFollyDynamicConvert (= 0.99.0)
  - FlipperKit/FBDefines (= 0.99.0)
  - FlipperKit/FKPortForwarding (= 0.99.0)
  - FlipperKit/FlipperKitHighlightOverlay (= 0.99.0)
  - FlipperKit/FlipperKitLayoutPlugin (= 0.99.0)
  - FlipperKit/FlipperKitLayoutTextSearchable (= 0.99.0)
  - FlipperKit/FlipperKitNetworkPlugin (= 0.99.0)
  - FlipperKit/FlipperKitReactPlugin (= 0.99.0)
  - FlipperKit/FlipperKitUserDefaultsPlugin (= 0.99.0)
  - FlipperKit/SKIOSNetworkPlugin (= 0.99.0)
  - glog (from `../node_modules/react-native/third-party-podspecs/glog.podspec`)
  - Google-Maps-iOS-Utils
  - GoogleMaps
  - OpenSSL-Universal (= 1.1.180)
  - Permission-AppTrackingTransparency (from `../node_modules/react-native-permissions/ios/AppTrackingTransparency`)
  - Permission-Camera (from `../node_modules/react-native-permissions/ios/Camera`)
  - Permission-Microphone (from `../node_modules/react-native-permissions/ios/Microphone`)
  - RCT-Folly (from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`)
  - RCTRequired (from `../node_modules/react-native/Libraries/RCTRequired`)
  - RCTTypeSafety (from `../node_modules/react-native/Libraries/TypeSafety`)
  - React (from `../node_modules/react-native/`)
  - React-callinvoker (from `../node_modules/react-native/ReactCommon/callinvoker`)
  - React-Core (from `../node_modules/react-native/`)
  - React-Core/DevSupport (from `../node_modules/react-native/`)
  - React-Core/RCTWebSocket (from `../node_modules/react-native/`)
  - React-CoreModules (from `../node_modules/react-native/React/CoreModules`)
  - React-cxxreact (from `../node_modules/react-native/ReactCommon/cxxreact`)
  - React-jsi (from `../node_modules/react-native/ReactCommon/jsi`)
  - React-jsiexecutor (from `../node_modules/react-native/ReactCommon/jsiexecutor`)
  - React-jsinspector (from `../node_modules/react-native/ReactCommon/jsinspector`)
  - React-logger (from `../node_modules/react-native/ReactCommon/logger`)
  - react-native-document-picker (from `../node_modules/react-native-document-picker`)
  - react-native-fbsdk-next (from `../node_modules/react-native-fbsdk-next`)
  - "react-native-geolocation (from `../node_modules/@react-native-community/geolocation`)"
  - react-native-google-maps (from `../node_modules/react-native-maps`)
  - react-native-html-to-pdf-lite (from `../node_modules/react-native-html-to-pdf-lite`)
  - react-native-image-picker (from `../node_modules/react-native-image-picker`)
  - react-native-maps (from `../node_modules/react-native-maps`)
  - "react-native-netinfo (from `../node_modules/@react-native-community/netinfo`)"
  - react-native-pdf (from `../node_modules/react-native-pdf`)
  - "react-native-progress-bar-android (from `../node_modules/@react-native-community/progress-bar-android`)"
  - "react-native-progress-view (from `../node_modules/@react-native-community/progress-view`)"
  - react-native-rsa-native (from `../node_modules/react-native-rsa-native`)
  - react-native-safe-area-context (from `../node_modules/react-native-safe-area-context`)
  - react-native-splash-screen (from `../node_modules/react-native-splash-screen`)
  - react-native-webrtc (from `../node_modules/react-native-webrtc`)
  - react-native-webview (from `../node_modules/react-native-webview`)
  - React-perflogger (from `../node_modules/react-native/ReactCommon/reactperflogger`)
  - React-RCTActionSheet (from `../node_modules/react-native/Libraries/ActionSheetIOS`)
  - React-RCTAnimation (from `../node_modules/react-native/Libraries/NativeAnimation`)
  - React-RCTBlob (from `../node_modules/react-native/Libraries/Blob`)
  - React-RCTImage (from `../node_modules/react-native/Libraries/Image`)
  - React-RCTLinking (from `../node_modules/react-native/Libraries/LinkingIOS`)
  - React-RCTNetwork (from `../node_modules/react-native/Libraries/Network`)
  - React-RCTSettings (from `../node_modules/react-native/Libraries/Settings`)
  - React-RCTText (from `../node_modules/react-native/Libraries/Text`)
  - React-RCTVibration (from `../node_modules/react-native/Libraries/Vibration`)
  - React-runtimeexecutor (from `../node_modules/react-native/ReactCommon/runtimeexecutor`)
  - ReactCommon/turbomodule/core (from `../node_modules/react-native/ReactCommon`)
  - "ReactNativeART (from `../node_modules/@react-native-community/art`)"
  - ReactNativeIncallManager (from `../node_modules/react-native-incall-manager`)
  - rn-fetch-blob (from `../node_modules/rn-fetch-blob`)
  - "RNCAsyncStorage (from `../node_modules/@react-native-community/async-storage`)"
  - "RNCClipboard (from `../node_modules/@react-native-community/clipboard`)"
  - "RNCMaskedView (from `../node_modules/@react-native-community/masked-view`)"
  - "RNCPicker (from `../node_modules/@react-native-picker/picker`)"
  - "RNDateTimePicker (from `../node_modules/@react-native-community/datetimepicker`)"
  - RNDeviceInfo (from `../node_modules/react-native-device-info`)
  - RNFastImage (from `../node_modules/react-native-fast-image`)
  - "RNFBAnalytics (from `../node_modules/@react-native-firebase/analytics`)"
  - "RNFBApp (from `../node_modules/@react-native-firebase/app`)"
  - "RNFBCrashlytics (from `../node_modules/@react-native-firebase/crashlytics`)"
  - "RNFBDynamicLinks (from `../node_modules/@react-native-firebase/dynamic-links`)"
  - "RNFBInAppMessaging (from `../node_modules/@react-native-firebase/in-app-messaging`)"
  - "RNFBMessaging (from `../node_modules/@react-native-firebase/messaging`)"
  - RNFS (from `../node_modules/react-native-fs`)
  - RNGestureHandler (from `../node_modules/react-native-gesture-handler`)
  - RNKeychain (from `../node_modules/react-native-keychain`)
  - RNLocalize (from `../node_modules/react-native-localize`)
  - RNPermissions (from `../node_modules/react-native-permissions`)
  - RNReanimated (from `../node_modules/react-native-reanimated`)
  - RNScreens (from `../node_modules/react-native-screens`)
  - RNSVG (from `../node_modules/react-native-svg`)
  - smartlook-react-native-bridge (from `../node_modules/smartlook-react-native-wrapper`)
  - TouchID (from `../node_modules/react-native-touch-id`)
  - Yoga (from `../node_modules/react-native/ReactCommon/yoga`)

SPEC REPOS:
  trunk:
    - CocoaAsyncSocket
    - FBSDKCoreKit
    - FBSDKLoginKit
    - FBSDKShareKit
    - Firebase
    - FirebaseABTesting
    - FirebaseAnalytics
    - FirebaseCore
    - FirebaseCoreDiagnostics
    - FirebaseCrashlytics
    - FirebaseDynamicLinks
    - FirebaseInAppMessaging
    - FirebaseInstallations
    - FirebaseMessaging
    - Flipper
    - Flipper-Boost-iOSX
    - Flipper-DoubleConversion
    - Flipper-Fmt
    - Flipper-Folly
    - Flipper-Glog
    - Flipper-PeerTalk
    - Flipper-RSocket
    - FlipperKit
    - fmt
    - Google-Maps-iOS-Utils
    - GoogleAppMeasurement
    - GoogleDataTransport
    - GoogleMaps
    - GoogleUtilities
    - libevent
    - libwebp
    - nanopb
    - OpenSSL-Universal
    - PromisesObjC
    - SDWebImage
    - SDWebImageWebPCoder
    - Smartlook
    - YogaKit

EXTERNAL SOURCES:
  boost:
    :podspec: "../node_modules/react-native/third-party-podspecs/boost.podspec"
  DoubleConversion:
    :podspec: "../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec"
  FBLazyVector:
    :path: "../node_modules/react-native/Libraries/FBLazyVector"
  FBReactNativeSpec:
    :path: "../node_modules/react-native/React/FBReactNativeSpec"
  glog:
    :podspec: "../node_modules/react-native/third-party-podspecs/glog.podspec"
  Permission-AppTrackingTransparency:
    :path: "../node_modules/react-native-permissions/ios/AppTrackingTransparency"
  Permission-Camera:
    :path: "../node_modules/react-native-permissions/ios/Camera"
  Permission-Microphone:
    :path: "../node_modules/react-native-permissions/ios/Microphone"
  RCT-Folly:
    :podspec: "../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec"
  RCTRequired:
    :path: "../node_modules/react-native/Libraries/RCTRequired"
  RCTTypeSafety:
    :path: "../node_modules/react-native/Libraries/TypeSafety"
  React:
    :path: "../node_modules/react-native/"
  React-callinvoker:
    :path: "../node_modules/react-native/ReactCommon/callinvoker"
  React-Core:
    :path: "../node_modules/react-native/"
  React-CoreModules:
    :path: "../node_modules/react-native/React/CoreModules"
  React-cxxreact:
    :path: "../node_modules/react-native/ReactCommon/cxxreact"
  React-jsi:
    :path: "../node_modules/react-native/ReactCommon/jsi"
  React-jsiexecutor:
    :path: "../node_modules/react-native/ReactCommon/jsiexecutor"
  React-jsinspector:
    :path: "../node_modules/react-native/ReactCommon/jsinspector"
  React-logger:
    :path: "../node_modules/react-native/ReactCommon/logger"
  react-native-document-picker:
    :path: "../node_modules/react-native-document-picker"
  react-native-fbsdk-next:
    :path: "../node_modules/react-native-fbsdk-next"
  react-native-geolocation:
    :path: "../node_modules/@react-native-community/geolocation"
  react-native-google-maps:
    :path: "../node_modules/react-native-maps"
  react-native-html-to-pdf-lite:
    :path: "../node_modules/react-native-html-to-pdf-lite"
  react-native-image-picker:
    :path: "../node_modules/react-native-image-picker"
  react-native-maps:
    :path: "../node_modules/react-native-maps"
  react-native-netinfo:
    :path: "../node_modules/@react-native-community/netinfo"
  react-native-pdf:
    :path: "../node_modules/react-native-pdf"
  react-native-progress-bar-android:
    :path: "../node_modules/@react-native-community/progress-bar-android"
  react-native-progress-view:
    :path: "../node_modules/@react-native-community/progress-view"
  react-native-rsa-native:
    :path: "../node_modules/react-native-rsa-native"
  react-native-safe-area-context:
    :path: "../node_modules/react-native-safe-area-context"
  react-native-splash-screen:
    :path: "../node_modules/react-native-splash-screen"
  react-native-webrtc:
    :path: "../node_modules/react-native-webrtc"
  react-native-webview:
    :path: "../node_modules/react-native-webview"
  React-perflogger:
    :path: "../node_modules/react-native/ReactCommon/reactperflogger"
  React-RCTActionSheet:
    :path: "../node_modules/react-native/Libraries/ActionSheetIOS"
  React-RCTAnimation:
    :path: "../node_modules/react-native/Libraries/NativeAnimation"
  React-RCTBlob:
    :path: "../node_modules/react-native/Libraries/Blob"
  React-RCTImage:
    :path: "../node_modules/react-native/Libraries/Image"
  React-RCTLinking:
    :path: "../node_modules/react-native/Libraries/LinkingIOS"
  React-RCTNetwork:
    :path: "../node_modules/react-native/Libraries/Network"
  React-RCTSettings:
    :path: "../node_modules/react-native/Libraries/Settings"
  React-RCTText:
    :path: "../node_modules/react-native/Libraries/Text"
  React-RCTVibration:
    :path: "../node_modules/react-native/Libraries/Vibration"
  React-runtimeexecutor:
    :path: "../node_modules/react-native/ReactCommon/runtimeexecutor"
  ReactCommon:
    :path: "../node_modules/react-native/ReactCommon"
  ReactNativeART:
    :path: "../node_modules/@react-native-community/art"
  ReactNativeIncallManager:
    :path: "../node_modules/react-native-incall-manager"
  rn-fetch-blob:
    :path: "../node_modules/rn-fetch-blob"
  RNCAsyncStorage:
    :path: "../node_modules/@react-native-community/async-storage"
  RNCClipboard:
    :path: "../node_modules/@react-native-community/clipboard"
  RNCMaskedView:
    :path: "../node_modules/@react-native-community/masked-view"
  RNCPicker:
    :path: "../node_modules/@react-native-picker/picker"
  RNDateTimePicker:
    :path: "../node_modules/@react-native-community/datetimepicker"
  RNDeviceInfo:
    :path: "../node_modules/react-native-device-info"
  RNFastImage:
    :path: "../node_modules/react-native-fast-image"
  RNFBAnalytics:
    :path: "../node_modules/@react-native-firebase/analytics"
  RNFBApp:
    :path: "../node_modules/@react-native-firebase/app"
  RNFBCrashlytics:
    :path: "../node_modules/@react-native-firebase/crashlytics"
  RNFBDynamicLinks:
    :path: "../node_modules/@react-native-firebase/dynamic-links"
  RNFBInAppMessaging:
    :path: "../node_modules/@react-native-firebase/in-app-messaging"
  RNFBMessaging:
    :path: "../node_modules/@react-native-firebase/messaging"
  RNFS:
    :path: "../node_modules/react-native-fs"
  RNGestureHandler:
    :path: "../node_modules/react-native-gesture-handler"
  RNKeychain:
    :path: "../node_modules/react-native-keychain"
  RNLocalize:
    :path: "../node_modules/react-native-localize"
  RNPermissions:
    :path: "../node_modules/react-native-permissions"
  RNReanimated:
    :path: "../node_modules/react-native-reanimated"
  RNScreens:
    :path: "../node_modules/react-native-screens"
  RNSVG:
    :path: "../node_modules/react-native-svg"
  smartlook-react-native-bridge:
    :path: "../node_modules/smartlook-react-native-wrapper"
  TouchID:
    :path: "../node_modules/react-native-touch-id"
  Yoga:
    :path: "../node_modules/react-native/ReactCommon/yoga"

SPEC CHECKSUMS:
  boost: a7c83b31436843459a1961bfd74b96033dc77234
  CocoaAsyncSocket: 065fd1e645c7abab64f7a6a2007a48038fdc6a99
  DoubleConversion: 831926d9b8bf8166fd87886c4abab286c2422662
  FBLazyVector: 808f741ddb0896a20e5b98cc665f5b3413b072e2
  FBReactNativeSpec: 94473205b8741b61402e8c51716dea34aa3f5b2f
  FBSDKCoreKit: 0d1ae58388a458b8222f72025804cdc84eb5d0c3
  FBSDKLoginKit: aea68df6121c5e165ccae2fabfdc83c4644ee40f
  FBSDKShareKit: 70889c97c62f0c6b3ccb8b999e73a85f19024001
  Firebase: 580d09e8edafc3073ebf09c03fd42e4d80d35fe9
  FirebaseABTesting: 1b05c92327b3f0a9545cea3bab4d93e82550e29b
  FirebaseAnalytics: bd10d7706ba8d6e01ea2816f8fe9e9b881cb0918
  FirebaseCore: 8138de860a90ca7eec5e324da5788fb0ebf1d93c
  FirebaseCoreDiagnostics: 3b40dfadef5b90433a60ae01f01e90fe87aa76aa
  FirebaseCrashlytics: 7952ffd988006128325510664b99dc8ca5851dff
  FirebaseDynamicLinks: 98a5f0fe542245a89ec55f646d2581298c29219d
  FirebaseInAppMessaging: 871e8d04ed0d1ca77c9c0e4c246c13d010d7a8de
  FirebaseInstallations: 25764cf322e77f99449395870a65b2bef88e1545
  FirebaseMessaging: 23db8bf05585e929ada8af0f0968933c25252808
  Flipper: 30e8eeeed6abdc98edaf32af0cda2f198be4b733
  Flipper-Boost-iOSX: fd1e2b8cbef7e662a122412d7ac5f5bea715403c
  Flipper-DoubleConversion: 57ffbe81ef95306cc9e69c4aa3aeeeeb58a6a28c
  Flipper-Fmt: 60cbdd92fc254826e61d669a5d87ef7015396a9b
  Flipper-Folly: 83af37379faa69497529e414bd43fbfc7cae259a
  Flipper-Glog: 1dfd6abf1e922806c52ceb8701a3599a79a200a6
  Flipper-PeerTalk: 116d8f857dc6ef55c7a5a75ea3ceaafe878aadc9
  Flipper-RSocket: d9d9ade67cbecf6ac10730304bf5607266dd2541
  FlipperKit: d8d346844eca5d9120c17d441a2f38596e8ed2b9
  fmt: ff9d55029c625d3757ed641535fd4a75fedc7ce9
  glog: 85ecdd10ee8d8ec362ef519a6a45ff9aa27b2e85
  Google-Maps-iOS-Utils: c32891ff472eaaa1fca032beedafa1a013af7875
  GoogleAppMeasurement: ae033c3aad67e68294369373056b4d74cc8ae0d6
  GoogleDataTransport: 629c20a4d363167143f30ea78320d5a7eb8bd940
  GoogleMaps: 32ca02de09de357a10ac773f2c70f1986751392d
  GoogleUtilities: e0913149f6b0625b553d70dae12b49fc62914fd1
  libevent: 4049cae6c81cdb3654a443be001fb9bdceff7913
  libwebp: 98a37e597e40bfdb4c911fc98f2c53d0b12d05fc
  nanopb: a0ba3315591a9ae0a16a309ee504766e90db0c96
  OpenSSL-Universal: 1aa4f6a6ee7256b83db99ec1ccdaa80d10f9af9b
  Permission-AppTrackingTransparency: 797438d0d6c6ea4528cb60b53f13488684f14fff
  Permission-Camera: 74dc395c37a06ebe915069c5dca954c7a2a5a2e3
  Permission-Microphone: 450ff628a7146c415cfb98025e518810d9fa76ad
  PromisesObjC: 68159ce6952d93e17b2dfe273b8c40907db5ba58
  RCT-Folly: 803a9cfd78114b2ec0f140cfa6fa2a6bafb2d685
  RCTRequired: 3c77b683474faf23920fbefc71c4e13af21470c0
  RCTTypeSafety: 720b1841260dac692444c2822b27403178da8b28
  React: 25970dd74abbdac449ca66dec4107652cacc606d
  React-callinvoker: 2d158700bc27b3d49c3c95721d288ed6c1a489ef
  React-Core: 306cfdc1393bcf9481cc5de9807608db7661817b
  React-CoreModules: 2576a88d630899f3fcdf2cb79fcc0454d7b2a8bb
  React-cxxreact: a492f0de07d875419dcb9f463c63c22fe51c433b
  React-jsi: bca092b0c38d5e3fd60bb491d4994ab4a8ac2ad3
  React-jsiexecutor: 15ea57ead631a11fad57634ff69f78e797113a39
  React-jsinspector: 1e1e03345cf6d47779e2061d679d0a87d9ae73d8
  React-logger: 1e10789cb84f99288479ba5f20822ce43ced6ffe
  react-native-document-picker: 4921045c5c6c78243010f784eae0a3f4b2af7799
  react-native-fbsdk-next: a0dd8905af573ec4d21b7bc398423ccaa2ce2b07
  react-native-geolocation: c956aeb136625c23e0dce0467664af2c437888c9
  react-native-google-maps: 0a989abda71059db2caa98b9dacca7a8f38a47d0
  react-native-html-to-pdf-lite: 21bfb169bf4cbcd7bec9f736975ee1b3f5292d4a
  react-native-image-picker: 7a85cf7b0a53845f03ae52fb4592a2748ded069b
  react-native-maps: f4b89da81626ad7f151a8bfcb79733295d31ce5c
  react-native-netinfo: 250dc0ca126512f618a8a2ca6a936577e1f66586
  react-native-pdf: ef641e79a6d550cfabe5d7ec1916799726514c43
  react-native-progress-bar-android: be43138ab7da30d51fc038bafa98e9ed594d0c40
  react-native-progress-view: 5e9560b491a149035b869d63603d4fc7f9258cb1
  react-native-rsa-native: 348b5057073920db0e154724c3a49e6b34e1da6b
  react-native-safe-area-context: 955ecfce672683b495d9294d2f154a9ad1d9796b
  react-native-splash-screen: 200d11d188e2e78cea3ad319964f6142b6384865
  react-native-webrtc: 83e3360d31a88809db308b20a4243244646d4250
  react-native-webview: 380c1a03ec94b7ed764dac8db1e7c9952d08c93a
  React-perflogger: 93d3f142d6d9a46e635f09ba0518027215a41098
  React-RCTActionSheet: 87327c3722203cc79cf79d02fb83e7332aeedd18
  React-RCTAnimation: 009c87c018d50e0b38692699405ebe631ff4872d
  React-RCTBlob: 9e30308cc1b127af11c8f858514d2d8638ce36d7
  React-RCTImage: b9460cb8e3acc51410735a234a9dffbf4964f540
  React-RCTLinking: 73ecf0b87b515383a08ebbf07f558c48de1f0027
  React-RCTNetwork: 8f63119f2da99a94515ad0e0d0a13f9b3f6fe89d
  React-RCTSettings: b827282b1ac2bd98515c0c09f5cbc5062ebd83b0
  React-RCTText: 6d09140f514e1f60aff255e0acdf16e3b486ba4c
  React-RCTVibration: d0361f15ea978958fab7ffb6960f475b5063d83f
  React-runtimeexecutor: af1946623656f9c5fd64ca6f36f3863516193446
  ReactCommon: 650e33cde4fb7d36781cd3143f5276da0abb2f96
  ReactNativeART: 78edc68dd4a1e675338cd0cd113319cf3a65f2ab
  ReactNativeIncallManager: a840ef75640518065742a893e6c6ff98ee820039
  rn-fetch-blob: f065bb7ab7fb48dd002629f8bdcb0336602d3cba
  RNCAsyncStorage: 2a692bcb9b69b76a2f1a95f33db057129700af64
  RNCClipboard: 41d8d918092ae8e676f18adada19104fa3e68495
  RNCMaskedView: 5a8ec07677aa885546a0d98da336457e2bea557f
  RNCPicker: f6c760d4b314585ff35165d8640d7917ae30afb1
  RNDateTimePicker: a84d2b439666c9243d42a8396c588d4d1d36e3f3
  RNDeviceInfo: c5f8f3a456adcbba405ace475254b08febc4c095
  RNFastImage: e19ba191922e7dab9d932a4d59d62d76660aa222
  RNFBAnalytics: c9c0893b1387bfa238442db83e7eab7fede71505
  RNFBApp: 5bae3002117e55f3c9aa0fb38175dd16c8046c90
  RNFBCrashlytics: 33615211c6c6c4039ae71849091f6ac38ab65aba
  RNFBDynamicLinks: af1099d827079101afece32aba470ae50d519217
  RNFBInAppMessaging: 35d740fb11d8eb81a14e8839812756b7c668dcb5
  RNFBMessaging: ae6c40883868cd01fa802395174ec7d61cfa0920
  RNFS: 2bd9eb49dc82fa9676382f0585b992c424cd59df
  RNGestureHandler: 7a5833d0f788dbd107fbb913e09aa0c1ff333c39
  RNKeychain: 840f8e6f13be0576202aefcdffd26a4f54bfe7b5
  RNLocalize: 49634a6a605dcdeb319e9c42a5c2f1aec508694b
  RNPermissions: c46788f4cd402287425983e04a4c9bb4356036eb
  RNReanimated: c1b56d030d1616239861534d9adb531f8cffab68
  RNScreens: 40a2cb40a02a609938137a1e0acfbf8fc9eebf19
  RNSVG: 9cb6e958c4b6a1f58185ac72a350b148947d6fed
  SDWebImage: 53179a2dba77246efa8a9b85f5c5b21f8f43e38f
  SDWebImageWebPCoder: d0dac55073088d24b2ac1b191a71a8f8d0adac21
  Smartlook: 6ff002c5bef2210f4ed8a4da87e123f8f45d72fb
  smartlook-react-native-bridge: 6ce52f310d6af454f6bb4748a42ae17497b006a3
  TouchID: ba4c656d849cceabc2e4eef722dea5e55959ecf4
  Yoga: 90dcd029e45d8a7c1ff059e8b3c6612ff409061a
  YogaKit: f782866e155069a2cca2517aafea43200b01fd5a

PODFILE CHECKSUM: e4188a5cc7d1b61245b632dc37a66c3697f85284

COCOAPODS: 1.11.2

Here is my package.json
{
  "name": "APP",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint .",
    "postinstall": "sh ./postinstall.sh"
  },
  "dependencies": {
    "@react-native-community/art": "^1.0.2",
    "@react-native-community/async-storage": "^1.6.2",
    "@react-native-community/clipboard": "^1.5.1",
    "@react-native-community/datetimepicker": "^3.0.0",
    "@react-native-community/geolocation": "^2.0.2",
    "@react-native-community/masked-view": "^0.1.10",
    "@react-native-community/netinfo": "^5.9.7",
    "@react-native-community/progress-bar-android": "^1.0.4",
    "@react-native-community/progress-view": "^1.2.3",
    "@react-native-firebase/analytics": "^14.5.1",
    "@react-native-firebase/app": "^14.5.1",
    "@react-native-firebase/crashlytics": "^14.5.1",
    "@react-native-firebase/dynamic-links": "^14.5.1",
    "@react-native-firebase/in-app-messaging": "^14.5.1",
    "@react-native-firebase/messaging": "^14.5.1",
    "@react-navigation/bottom-tabs": "5.8.0",
    "@react-navigation/compat": "^5.2.7",
    "@react-navigation/drawer": "5.9.0",
    "@react-navigation/native": "5.7.3",
    "@react-navigation/stack": "5.9.0",
    "@seznam/compose-react-refs": "^1.0.6",
    "@voximplant/react-native-foreground-service": "^2.0.0",
    "abortcontroller-polyfill": "^1.5.0",
    "axios": "^0.20.0",
    "cross-fetch": "^3.0.4",
    "dhp-mobile-app-state": "^0.0.1",
    "dhp-mobile-components": "^0.0.1",
    "dhp-mobile-configuration": "^1.0.0",
    "dhp-navigation-service": "^1.0.0",
    "formik": "^2.2.1",
    "i18n-js": "^3.3.0",
    "lodash": "^4.17.15",
    "query-string": "^6.13.1",
    "react": "17.0.2",
    "react-native": "0.67.3",
    "react-native-app-link": "^1.0.1",
    "react-native-autoheight-webview": "^1.3.2",
    "react-native-barcode-builder": "^2.0.0",
    "react-native-check-app-install": "0.0.5",
    "react-native-confirmation-code-field": "^7.2.0",
    "react-native-device-info": "^5.3.0",
    "react-native-document-picker": "^3.5.2",
    "react-native-fast-image": "^8.3.2",
    "react-native-fbsdk-next": "^4.6.0",
    "react-native-fs": "^2.16.6",
    "react-native-geolocation-service": "^3.1.0",
    "react-native-gesture-handler": "^1.7.0",
    "react-native-html-to-pdf-lite": "^0.9.1",
    "react-native-image-picker": "^1.1.0",
    "react-native-incall-manager": "^3.2.7",
    "react-native-keyboard-accessory": "^0.1.9",
    "react-native-keyboard-aware-scroll-view": "^0.9.1",
    "react-native-keychain": "^4.0.1",
    "react-native-localize": "^1.3.3",
    "react-native-maps": "0.27.1",
    "react-native-modal": "^11.5.3",
    "react-native-modalize": "1.3.7-rc.5",
    "react-native-otp-verify": "^1.0.4",
    "react-native-pdf": "^6.2.2",
    "react-native-permissions": "^3.0.4",
    "react-native-popup-dialog": "^0.18.3",
    "react-native-qrcode-svg": "^5.2.0",
    "react-native-reanimated": "^1.13.4",
    "react-native-redash": "^16.0.8",
    "react-native-rsa-native": "^1.1.2",
    "react-native-safe-area-context": "^3.1.7",
    "react-native-screens": "^3.13.1",
    "react-native-sms-retriever": "^1.1.1",
    "react-native-splash-screen": "^3.2.0",
    "react-native-status-bar-height": "^2.6.0",
    "react-native-svg": "9.4.0",
    "react-native-svg-transformer": "^0.14.3",
    "react-native-touch-id": "^4.4.1",
    "react-native-webrtc": "1.98.0",
    "react-native-webview": "^11.17.2",
    "react-navigation": "^4.0.10",
    "react-redux": "^5.0.7",
    "redux": "^4.0.0",
    "redux-api-middleware": "^3.0.1",
    "redux-form": "^7.4.2",
    "redux-saga": "^1.1.3",
    "redux-thunk": "^2.3.0",
    "rn-fetch-blob": "^0.12.0",
    "smartlook-react-native-wrapper": "^1.2.3",
    "urijs": "^1.19.2",
    "vbc-backend-error-handler": "^1.0.0",
    "vbc-date-range-picker": "^1.0.0",
    "vbc-datepicker": "^1.0.0",
    "vbc-mobile-lib": "^1.0.0",
    "vbc-mobile-theme": "^1.0.0",
    "vbc-react-native-redux-form-field": "^0.0.1",
    "@react-native-picker/picker": "^2.3.1"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/plugin-proposal-decorators": "^7.10.5",
    "@babel/plugin-proposal-optional-chaining": "^7.6.0",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "@types/react": "^16.9.4",
    "@types/react-native": "^0.60.17",
    "babel-jest": "^26.6.3",
    "babel-plugin-module-resolver": "^4.0.0",
    "babel-plugin-transform-remove-console": "^6.9.4",
    "eslint": "^7.14.0",
    "jest": "^26.6.3",
    "metro-react-native-babel-preset": "^0.66.2",
    "react-native-typescript-transformer": "^1.2.13",
    "react-test-renderer": "17.0.2",
    "redux-devtools-extension": "^2.13.8",
    "typescript": "3.8.3"
  },
  "jest": {
    "preset": "react-native"
  }
}

Version
0.67.3
Output of npx react-native info
System:
OS: macOS 10.15.7
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 2.95 GB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.22.10 - /usr/local/opt/node@12/bin/node
Yarn: Not Found
npm: 6.14.16 - /usr/local/opt/node@12/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 23, 26, 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2
System Images: android-26 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.3 => 0.67.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

Upgrade RN up to 0.67.3 (In my case from 0.63.3 to 0.67.3)
Build Archive with herems on
Apple Rejects build cause of corrupted binaries

Snack, code example, screenshot, or link to a repository
No response

Thanks for your report @PrimulaX

here is my podfile:

I can't see hermes-engine in your podfile, so that's hard to even debug. Is this the podfile after your remove Hermes? Which version of Hermes have you been using?

@cortinico Hi, thanks for you reply.
Yes, sorry for that, it's podfile after I delete hermes-engine. I just edit the description.

@cortinico Ah I see, Thanks, I'll try that.

Awesome, please keep us posted

@cortinico Actually I'm unable to update Hermes, Is there any specific way to update it?

Ideally, if you're on RN 0.67.3 and you do pod install, you should automatically get the correct Hermes version. I would suggest you remove the Podfile.lock and run pod install again.

@cortinico Yes I did try that, but it always install same version Installing React-hermes (0.67.3)

Actually the recommended Hermes version for React native 0.67.3 is 0.9.0.
It was supposed to be Hermes 0.10.0 but that was to be rolled back  to 0.9.0 (which has been stable for  a year or more)  for something exactly similar to the bug you describe.
You may possibly still somehow be trapped on an incorrect version of Hermes 10 as it was on a Release Candidate, otherwise this looks like a major problem that requires further investigation.
Try flushing your watchman and node modules, IOS/Xcode cache etc see stack overflow, and check with the react native upgrade helper.

@joe-sam I did possibly everything but no luck.

Guessing there may be some incompatible framework like a testing framework in this case.
Try to find one of the offending  API like this stackoverflow

@joe-sam If so, its all about Hermes, It was accepted successfully without it. I'll keep searching tho.

It came out that the problem was "react-native-webrtc": "1.98.0". I did build with "react-native-webrtc": "1.94.2" and Hermes, Apple accept the build


add openai/whisper as a speech to text engine

https://github.com/openai/whisper
there is some discussion here: https://community.rhasspy.org/t/whisper-by-openai/3920

I created a custom integration relying on the Remote HTTP method. You can find it here https://github.com/seifane/whisper-rhasspy-http


Improper AST parsing

Dear Team,
We are currently developing a static tool for handlebars. we are extracting necessary contents using HANDLEBARS AST. The AST generated(using Handlebars.parse method) is not up to the mark.
The Handlebars Template with {{if}}{{else}}{{/if}} is not parsed correctly.
We are using Handlebars 2.0.0 version.
Example:

  {{#if author}}

{{firstName}} {{lastName}}

  {{else}}

{{Unknown Author}}

  {{/if}}

Here, no object is rendered for {{else}} block. It is getting skipped. Is there any other way to parse it correctly. Please update Us as soon as possible. Very Urgent.
Regards
Gokul

Please provide an example of the AST and explain how that differs from your expectations.


odpic: init at 2.3.2

Motivation for this change
Adds Oracle Database Programming Interface for C (ODPI-C) library.
Should also allow to fix build of odpic-raw (Haskell bindings) which is currently failing due to missing dependency:
Setup: Missing dependency on a foreign library:
  * Missing C library: odpic

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@pesterhazy @flokli As maintainers of oracle-instantclient you may also be interested in this.

@mulderr funny thing, odpi also comes as a submodule of cx_python (IIRC). Maybe you want to apply the patch from there here as well, or even use this separate odpi drv for everything.

This one right?
Documentation says that ODPI-C can be used in two different ways. As a shared library or by including the source directly in another project. I think cx_Oracle does the latter while odpic-raw currently expects the former.
I think the patch is just fixing the path to libclntsh? I decided to override RPATH instead. The net effect should be identical but browsing through nixpkgs patchelf seems to be the goto solution.
Hm, while I don't have immediate use for it (other than to make odpic-raw work), it makes sense to me that this should be offered as a separate library in case anyone wants to use it from C/C++ etc.
Luckily, correct me if I'm wrong, this shouldn't break cx_Oracle in any way? So any project that was using odpic directly can keep using a version independent of the one in nixpkgs - for example via git submodules as cx_Oracle does.

Overriding rpath is also possible, and probably cleaner than maintaining a patch in nixpkgs. Agreed :-)
Since https://github.com/oracle/python-cx_Oracle/commit/9baa55b3bffaa1d79c443dd0f7db16162a22cb93, it's possible to build cx_oracle with an external odpic library, so I updated my drv accordingly to use the new odpi drv:
https://github.com/flokli/nixpkgs/commit/cx_oracle-odpi-c
Could you git am that on top of your PR?

@mulderr patches for odpic were upstreamed (https://github.com/oracle/odpi/issues/65),
I updated my oracle-instantclient-darwin branch to include the patch.
Would you mind cherry-picking my commits in here?

@flokli Done.
Fair warning though, I don't use Macs or have one handy to test so it's impossible for me to verify. If it works for you then cool. Might as well take care of this right away.

Umm, forgot to drop 0001-Makefile-fix-dylib-names.patch from my commit, sorry :-/
If you want to test, you can try the AndrewDryga vagrant-box-osx.

No worries. Patch removed.

LGTM. @matthewbauer, @FRidh, merge?

Thanks for all the input and for merging! Awesome.


[ENH] Scale data to start with a given value

I want to scale a series or several to start with 1. Tried to do it with TabularToSeriesAdaptor(MinMaxScaler(feature_range=(1, 10))) but didnt work as expected. We might need a separate transformer for this?
from sktime.datasets import load_airline
y = load_airline()
TabularToSeriesAdaptor(MinMaxScaler(feature_range=(1, 10))).fit_transform(y)

Out[41]: Period
1949-01     1.138996
1949-02     1.243243
1949-03     1.486486
1949-04     1.434363
1949-05     1.295367
1949-06     1.538610

my custom implementation:
# Calculate the scaling factor
scaling_factor = 1 / y.iloc[0]

# Scale the column by multiplying with the scaling factor
y = y * scaling_factor
y.head()

Out[42]: Period
1949-01    1.000000
1949-02    1.053571
1949-03    1.178571
1949-04    1.151786
1949-05    1.080357

closing this with the big refactor, could I guess have a transformer for this if there is demand, feel free to reopen


Add Path Version Specifier and some bugfixes from integration

Closes JITX-7201

This refactors the repl and build commands to make it easier to pass arguments instead of using an EnvVar. I didn't realize there was a flag for capture all remaining args when I did the initial refactor. This setup is easier to integrate cleanly into JITX
Changed the slm.toml parsing to not use env-var substitution during the add and remove commands. This was causing problems where the {JITX_ROOT} references were converted to literal paths on subsequent adds.
Adds a new -cfg option for add and remove to avoid unnecessary change directory.
Adds a version optional parameter for PathDependency so that we can spec a specific path dependency as needed.

I'm confused about why we need the -cfg flag -- can you elaborate? Shouldn't it always just extend slm.toml?

I'm confused about why we need the -cfg flag -- can you elaborate? Shouldn't it always just extend slm.toml?

When we run create-project in JITX, we haven't created the directory where the new project is going to be yet. We're creating the directory from some other starting point. So we create the project with the template, and then I'm running slm init ./that/new/path.
After that - I want to run slm add -git some-dep - but to do that I have to change directories into the ./that/new/path directory to find the slm.toml file. The -cfg option lets me do: slm add -cfg ./that/new/path/slm.toml -git some-dep without changing directories.


Docs > Updated Docs for Steps and Cli for Samples for All Languages and All Versions

Completed in earlier PR 45


Improve Hubble decoding performance

https://github.com/cilium/cilium/pull/24162 introduced specialized functions to decode TraceNotify events, replacing the generic but "slow" binary.Read. There are other event types that could benefit from the same optimization:

[ ] DropNotify https://github.com/cilium/cilium/blob/82a6396d59f5b52cbbb8a3787803cd2317ffdaf0/pkg/hubble/parser/threefour/parser.go#L112
[ ] PolicyVerdictNotify https://github.com/cilium/cilium/blob/82a6396d59f5b52cbbb8a3787803cd2317ffdaf0/pkg/hubble/parser/threefour/parser.go#L134
[ ] DebugCapture https://github.com/cilium/cilium/blob/82a6396d59f5b52cbbb8a3787803cd2317ffdaf0/pkg/hubble/parser/threefour/parser.go#L141
[ ] DebugMsg https://github.com/cilium/cilium/blob/82a6396d59f5b52cbbb8a3787803cd2317ffdaf0/pkg/hubble/parser/debug/parser.go#L50
[ ] TraceSockNotify https://github.com/cilium/cilium/blob/82a6396d59f5b52cbbb8a3787803cd2317ffdaf0/pkg/hubble/parser/sock/parser.go#L77

@kaworu - I would like to work on this.

/assign

@kaworu - I would like to work on this issue. Can you please assign this to me?