Andstatus crashes when I try to add a Twitter account

I've been trying to add a Twitter account a several times but I only get a "AndStatus has crashed"

Please more details,  when this occurs...

I'm trying to add a new account, right now:
Setting / add a new account / Twitter / add this account / crash :(

I cannot reproduce this. Tried with Android 4.1.2. - added Twitter account without errors (to the fresh installation.

I've got this error:

Unfortunately, the process org.andstatus.app has stopped.

If you connect your device to PC with Android IDE (Eclipse...) you should be able to see a full log including a stack trace, showing statements, where the exception occurred.

@moshpirit Any news on this using the latest build?

No, I think you can close this issue :)

Closing as no evidence now...

Nope, the problem is that AS doesn't let me enter my username and password because it doesn't show these fields.

This is how it works: you type username and password after pressing "Add this account" in AndStatus, at Twitter web site.

But I can't type it, there's no place to write :\

Does Twitter Web site open?
Post screenshot, please!

Nope, nothing, ok I'll share you one

I need a screenshot, which opens after you press "Add this account" button in AndStatus
What's your Android version?
Did you change SSL Security settings?

Screenshot: https://my.owndrive.com/public.php?service=files&t=f9f245d025849d2d1afc7b86493a1be4
When I push "Add this account", AS crashes.
Using Android 4.3
No changes in SSL (safe mode and SSL it's enabled by default on Tw)

I see this on Android 4.3. emulator after pressing "Add Account" button:
Please provide a a stacktrace to figure out where the problem is...

What's a stacktrace?

A stacktrace is a list of Java code components, which called each other in a sequence to produce some exception. In our case - the crash.
See this crash stacktrace, which I easily fixed, receiving it:

As you can see, the stacktrace shows line members and module names, where execution passed...

Getting this issue too, but it only occurs when trying to add a second Twitter account.
As soon as you click on the field to enter your username, the whole app crashes. Clicking and entering text in the password field has no effect.


Fix release pipeline

This commit fixes the syntax of the release pipeline task refs. We don't allow taskref.name along with taskref.resolver. Running into https://github.com/tektoncd/pipeline/issues/5673.
In addition, it downgrades the version of the git-clone catalog task to 0.7, as the version 0.9 requires setting a security context on the pipelinerun, and our current release process, which uses tkn, doesn't provide a good way to set the security context for a single pipeline task.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

n/a Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
n/a Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/lgtm

We can add back remote resolution for the clone task in the future, but this will unblock releases for now.

@lbernick looks like we can remove this part of the PR description now, right? feel free to unhold after resolving this

whoops thanks! fixed
/hold cancel

@afrittoli if i remember correctly, you preferred that we retained the name in the remote resolution so wanted to flag this if would you consider it a bug

I've opened https://github.com/tektoncd/pipeline/pull/6854 to use the same validation for taskrefs in pipeline tasks as taskrefs in taskruns. (I consider it a bug that they differ.) We could instead change the validation that's being done for taskruns. But probably makes more sense to discuss on that PR.


How to make a state prop shared between connected components ?

Hi guys !
I am working under a dynamic react  - redux - thunk  async app ,
I want to make the loading prop state shared between all the connected components ,
So how to make that loading prop as Global for all reducers ?
I mean How to be able to change that loading prop under multiple reducers ?
Kind regards !

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out - you'll probably get a better answer faster. Thanks!


Custom Rules for TypeScript and ES6

Add and modify rules for TypeScript/ES6 specific code.
The following rules were added or modified:

no-multiline-var-declarations - Fixes #25

Added the ability to override each individual declaration type (let, var, const)
Added the ability to allow multiline declarations when the variable being declared is the only one in the declaration block.

no-arrow-for-class-properties - Fixes #26

Rule to disallow class properties that are arrow functions

module-files-only - Fixes #27

Rule to force all files to have either an import or export statement, ensuring that they are modules.

block-scope-case - Fixes #28

Rule to force declaring block scope for all case statements.

There is also a commit to prepare for TypeScript rules. This commit removes changes the node dependency to > v6 and adds a rule tester configuration that can be used for TypeScript rule tests.

Coverage increased (+1.3%) to 83.448% when pulling 08fcfee74a5679a856ed9601e826c743659b5aac on jimjenkins5:typescript_rules into 26d1befd01f40ac7b1be12bb252b87d675a20bfa on silvermine:master.

Looks good.


Add funcionality, doc, and test

Ok, nice work, this is looking good. My main concern is with the path: I think /convert is probably too generic for our API, though I'm not sure what would be better :grinning:. What do you think? I'd like it if we could be consistently RESTful, but maybe it's not worth it here..


Table select query provide inconsistent results when constraint type is closed

Description:
Table select query fails when the record type of the result table is open.
Steps to reproduce:
Please refer below ballerina code.

import ballerina/io;
import ballerina/runtime;
import ballerinax/jdbc;

//This is the record that holds item details in the stockTable.
type Item record {
    string name;
    float price;
    int stockAmount;
    !...
};

//This is the record that holds order events from customer.
type Order record {
    string itemName;
    int orderingAmount;
    !...
};

//This is the record that holds alert events.
type OutOfStockAlert record {
    string itemName;
    int stockAmount;
    !...
};

// This is the input stream that uses `Order` as the constraint type.
stream<Order> orderStream = new;

jdbc:Client testDB = new({
        url: "jdbc:mysql://localhost:3306/testdb",
        username: "root",
        password: "root",
        poolOptions: { maximumPoolSize: 5 },
        dbOptions: { useSSL: false }
    });

// This is the output stream that contains the events/alerts that are generated based on streaming logic.
stream<OutOfStockAlert> oredrAlertStream = new;

function initOutOfStockAlert() {
    // Whenever an order event is published to `orderStream`, it is matched against the `itemStockTable` through
    //the `queryItemTable` function. If there is a match, an alert event is published to `oredrAlertStream`.
    forever {
        from orderStream window lengthWindow(1) as itemOrder
        join queryItemTable(itemOrder.itemName, itemOrder.orderingAmount) as item
        select item.name as itemName, item.stockAmount
        => (OutOfStockAlert[] alerts) {
            foreach var alert in alerts {
                oredrAlertStream.publish(alert);
            }
        }
    }
}

//`queryItemTable` function returns a table of items whose stock is not enough to satisfy the order.
public function queryItemTable(string itemName, int orderingAmount)
        returns table<Item> {

    var selectRet = testDB->select("SELECT * FROM itemStockTable where name = ? and stockAmount < ?", Item, itemName, orderingAmount);
    if (selectRet is table<Item>) {
	return selectRet;
    } else if (selectRet is error) {
        io:println("Select data from itemStockTable table failed: "
                + <string>selectRet.detail().message);
    }
	table<Item> result = table {
        { name, price, stockAmount }, []
    		};
    return result;

}

public function main() {
    initOutOfStockAlert();

    Order order1 = { itemName: "Pen", orderingAmount: 50};
    Order order2 = { itemName: "Book", orderingAmount: 2};

    // Whenever the `oredrAlertStream` stream receives an event from the streaming rules defined in the `forever`
    // block, the `printOutOfStocksAlert` function is invoked.
    oredrAlertStream.subscribe(printOutOfStocksAlert);

    orderStream.publish(order1);
    runtime:sleep(500);
    orderStream.publish(order2);
    runtime:sleep(500);
}

function printOutOfStocksAlert(OutOfStockAlert a) {
    io:println("Alert! : " + a.itemName + " stock is not enough to satisfy the order.");
}

This should be fixed once https://github.com/ballerina-platform/ballerina-lang/issues/12667 is fixed

Closing since this is tracked by https://github.com/ballerina-platform/ballerina-lang/issues/12667


Mergeback

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (383ece1) to head (33c2319).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##           develop       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          116       116
=========================================
  Hits           116       116

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cannot use ? params in scope where clause

Code example (inline, gist, or repo)
class Person
    include Neo4j::ActiveNode
    property :name
    has_many :out, :friends, type: :friend, model_class: 'Person'
    scope :has_friends ->(count) { where("SIZE((#{identity}-[:friend]-()) = ?", count)  }
end

Person.all.has_friends(3)

Runtime information:
raises the error: gems/neo4j-c2680108df1e/lib/neo4j/active_node/scope.rb:114:in `where': wrong number of arguments (given 2, expected 0..1) (ArgumentError)
Looks like the problem is  at this line:
https://github.com/neo4jrb/neo4j/blob/39456bf782f5a4fdb58f2108110e64837750c1ac/lib/neo4j/active_node/scope.rb#L109

I think you can replace the ? with a parameter, like this:
scope :has_friends ->(count) { where("SIZE((#{identity}-[:friend]-()) = {identity_size}").param(identity_size: count) }

@ProGM I thought about that, but then if the scope is used twice in one query it will break, correct? I'm under the impression that ? params can be used multiple times in the same query (maybe I'm wrong about that!).
eg Person.all.has_friends(2).friends.has_friends(5)
Obviously that's a bit convoluted, but you get the drift.
As far as using a named parameter, it could be a helpful workaround for some cases, but I think that the methods in a scope context should behave the same as the methods on a query proxy.

I was trying to reproduce this for a while and then realized that you're running off master.  That's actually a bad idea at the moment and I'm working on fixing master currently.  Can you reproduce on 7.0.11?
You should be able to use multiple question mark params in the query (definitely let us know if not), but it should translate those as Neo4j parameters with names like question_mark_param_1

@cheerfulstoic First of all, sorry that I took up your time like that! I actually am running from master but did not realize it. Sorry :(
I modified the example to not use identity (which exists on master but not in 7.0.11). and tried it again on 7.0.11. It seems the problem exists there too.
class Person
    include Neo4j::ActiveNode
    has_many :out, :friends, type: :friend, model_class: 'Person'
    scope :has_friends, ->(count) { where("SIZE((p)-[:friend]-()) = ?", count)  }
end

Person.all(:p).has_friends(3)

raises
gems/neo4j-7.0.11/lib/neo4j/active_node/scope.rb:110:in `where': wrong number of arguments (given 2, expected 0..1) (ArgumentError)
From the code that I linked, it looks like the problem could be solved by using parameter splatting?
The dynamic naming of question mark params is the feature I want to take advantage of, instead of using a regular old named parameter, which is subject to naming collisions.

I think that this is a bug in scope.  In general I think we need to fix the way that we do scopes because that sometimes work a bit funny like this.  What if you try this?
class Person
  include Neo4j::ActiveNode
  has_many :out, :friends, type: :friend, model_class: 'Person'
  def self.has_friends(count, var = :p)
    all(var).where("SIZE((#{var})-[:friend]-()) = ?", count)
  end
end

@cheerfulstoic Yes, that would work. I was hoping to use scopes because the composability makes it very easy to write readable, DRY queries.
It should work to splat the params given to scope into the lambda, right?
eg.
      Neo4j::ActiveNode::Query::QueryProxy::METHODS.each do |method|
        module_eval(%{
            def #{method}(*params)
              @target.all.scoping do
                (@query_proxy || @target).#{method}(*params)
              end
            end}, __FILE__, __LINE__)
      end

@yourpalal I had a similar issues the first times I used Neo4j gem.
Even if it's not documented, Neo4j::ActiveNode class methods, as opposed to
ActiveRecord, are composable exactly like scopes in ActiveRecord.
So you can write:
class Person
  include Neo4j::ActiveNode
  has_many :out, :friends, type: :friend, model_class: 'Person'
  def self.has_friends(count, var = :p)
    all(var).where("SIZE((#{var})-[:friend]-()) = ?", count)
  end
end

And then call:
Person.has_friends(2).friends.has_friends(5)

And it works!

About that, @cheerfulstoic , an hot fix for scopes could be to replace the current implementation with a something like:
def scope(name, lambda)
  define_singleton_method(name, &lambda)
end

Just an idea ;)

Thanks @ProGM
Definitely class methods work just as well as scope (perhaps better, as you've found).  If you use the all (which takes an argument for the node variable), you should be able to chain class methods together.
And yes, just having scope define class methods could certainly be a good fix.  Perhaps even a permanent one


termux.android.execute('termux-dialog confirm -t 'Hello world!') results in error + unexpected behavior

Hello!
Calling

results in

The execute() function cannot handle strings with spaces as arguments (such as "Hello world!"). This does not happen when there are no spaces in the string.
What I would expect is the same as when calling the API outside of python:

results in:

One unexpected behavior I have noticed is that any string argument that gets passed through the execute() function (such as title, hint and maybe more, i haven't tried all) will be quoted when displayed:

Expected behavior would be:

I think this is due to the the "fSplit = func.split()" in android.py on line 24. May I suggest using built-in shlex.split() instead of string.split() ? shlex.split() can preserve quoted substring. Looking at the code, that might solve the unexpected behavior with the quotes as well i think.

Thanks.. will fix
On Tue, 23 Nov, 2021, 9:26 pm MartyX98, @.***> wrote:

I think this is due to the the "fSplit = func.split()" in android.py on
line 24. May I suggest using built-in shlex.split() instead of
string.split() ? shlex.split() can preserve quoted substring. Looking at
the code, that might solve the unexpected behavior with the quotes as well
i think.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shajul/termux-api/issues/4#issuecomment-976759406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD6PUBAT7UAEKZ55GHHURTUNO2SLANCNFSM5ITZ5MXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Link to the PackageIcon documentation

It's really hard to find the documentation on how to create a package with an icon. We should really consider adding a dedicated page for the new package icon feature... For example, googling for PackageIcon nuget results in:

Docs Build status updates of commit 7d12bd8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/creating-a-package-dotnet-cli.md
:white_check_mark:Succeeded
View

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

@karann-msft Why is the PackageIcon element a path in the nupkg? The current syntax is quite verbose:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
      ...
      <PackageIcon>icon.png</PackageIcon>
      ...
  </PropertyGroup>

  <ItemGroup>
      ...
      <None Include="images\icon.png" Pack="true" PackagePath=""/>
      ...
  </ItemGroup>
</Project>

Would it be possible to simplify this syntax? What if the PackageIcon property could automagically handle paths at pack time? Example:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
      ...
      <PackageIcon>images\icon.png</PackageIcon>
      ...
  </PropertyGroup>
</Project>


Update dependencies

Controller-runtime has been updated to v0.9.0, K8s dependencies to
v0.21.1, and all fluxcd/pkg and other dependencies to the versions
that have matching dependencies and/or build constraints.
This includes an update of Helm to v3.6.0, and an update of the
Kustomize API to match v4.1.x.
Ref: https://github.com/fluxcd/flux2/issues/1486

Please update Go to 1.16 in Dockerfile, go.mod and GH Actions


How Can I Access to Screen Size? (Fixed)

How can i access to screen width and height for frame?

Hi @kadir-ince, thank you for reporting this issue! Unfortunately, UIKit is a closed-source framework, so no parts of it can run in browsers to get the size of your browser screen. You could try GeometryReader, but it isn't supported in SwiftWebUI as far as I'm aware. We do support it in Tokamak which runs purely in the browser.

Right, Geometry Reader is not supported.
Not quite sure what the expectation is when setting the frame. Do you expect the browser window to resize?

like as:
.frame(width: screen.width / 2)
I expect access to any item width and height size.
Text("Hello")
     .frame(width: screen.width / 2)

👇🏼👇🏼
p {
  width: 50%;
}


Issue 14371 - [CTFE] Binary assignment expression makes wrong result in compile-time

https://issues.dlang.org/show_bug.cgi?id=14371

This makes much more sense!

Auto-merge toggled on

The win32 error is definitely unrelated.


Not compatible with version 25+

Expected Behavior
Should work like it did with version 24.X.
Current Behavior
Error:
 [creator]     ERROR: failed to initialize detector: open /cnb/buildpacks/paketo-buildpacks_new-relic/8.15.0/buildpack.toml: no such file or directory
When running this command:
./gradlew build -x test bootBuildImage -Pversion=preview --cleanCache
Here is the code in the build.gradle file:
bootBuildImage {
    imageName = String.format("%s:%s", System.getenv("DOCKER_IMAGE_NAME") ?: "acrcoreglobal.azurecr.io/cpo.whatever", version)
    buildpacks = ["urn:cnb:builder:paketo-buildpacks/java", "gcr.io/paketo-buildpacks/new-relic"]
    bindings = ["${projectDir}/new-relic:/platform/bindings/new-relic"]
}

Started to happen on Github Action this morning when they updated their base ubuntu image with docker version 26 instead of version 24 (they skipped 25)
Reproduced on all the local machines on my team. Everyone with version 24.X was ok but everyone with latest version (25 or 26) receive the aforementioned error.
When I remove this buildpack from the list, everything works perfectly (but I don't have a new relic agent)
Possible Solution
No idea.
Steps to Reproduce
Use this configuration and run it with docker version 25 or latest.
Motivations
This is blocking our entire project to use New Relic.

We've seen this issue come up a number of times and the culprit has been https://github.com/spring-projects/spring-boot/issues/39347
Can you confirm that you have this fix? Thanks

@dmikusa We upgraded and it fixes the problem (but breaks other thing like all update in spring boot).
Thanks for the quick answer!


Can't stop TF from printing probabilities

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Using the tutorial code
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Arch Linux
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): 1.5.0
Python version:  3.6.4
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce: python cnn_mnist.py

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
I can't stop TF from printing the "INFO:tensorflow:probabilities = []" part, where in the angle brackets is a list that spans for several hundred lines. Trying to suppress the verbosity either does nothing or causes lines like "INFO:tensorflow:loss = 2.314889, step = 2" to stop appearing as well.
Source code / logs
I used the source code from this page: https://www.tensorflow.org/tutorials/layers

How about using tf.logging.set_verbosity(tf.logging.ERROR)?

If I do that, it doesn't give me any output on the accuracy or results of the classifier.


Does not work correctly on iOS

I'm using DialogHost.Avalonia 0.7.7 for an app project targeting both Android and iOS.
Avalonia framework version is 11.0.6 and .NET version is 7.
Please check the attached sample project. It simply opens a message dialog (MessageDialog.xaml) when clicking the Button.
Running in Debug mode, it works as expected on Android 11. Instead on iOS (different devices from version 15.8 to 16.2) the popup does not open, or it takes a very long time.
Sorry but I cannot test in Release mode as for now, so I cannot tell you if this is related to a particular Configuration.
PopupTest.zip

Hello, @alessandrofrancesconi
I'll try to debug this, but I don't own physical iOS device, so only emulator available. If you find any details - please let me know.

I'm testing on multiple iOS Simulators, and 1 real device. The issue is present in both conditions.

Just tested in Release mode and the issue remains. It seems that, only on iOS, it is necessary to start tapping at the center of the screen to let the popup appear.
To add more details, I'm using the following version of Microsoft.iOS: 16.2.2054 / 7.0.100. I am not able to upgrade to a more recent version because I'm using Xcode 14.2 and cannot upgrade.
To test it with this very same version, add the following files to the root of the sample project:
global.json
{
  "sdk": {
    "version": "7.0.100",
    "rollForward": "disable",
    "allowPrerelease": false
  }
}

rollback.json
{
  "microsoft.net.sdk.ios": "16.2.2054/7.0.100"
}

Before compiling, run this:
dotnet workload uninstall ios
dotnet workload install ios --from-rollback-file rollback.json

Let me know if you can reproduce it, thanks!

Can you also try to disabling animations from DialogHost. May be it will help?

Already tried with no improvements

I tried to begin to determine the cause of the error, downloaded your project, and suddenly realized that the rider could not run it.
After a quick search on the Internet, I realized that without having any Apple device (Mac or iPhone), I cannot somehow launch the application. As I understand it, it is impossible to run an iPhone emulator (or some similarity) if you only have Linux/Windows/Android devices.
Perhaps I missed something and this is not true?

Also, one of Avalonia maintainers suggesting you to try latest nightly avalonia build. I think than they fix something continuously, and this bug probably on Avalonia side (since it works everywhere except iOS).

You're probably not going to gift me an Apple machine to debug this bug 😄...
So, probably not. I'll try to set aside time on the weekends to install and configure macos on a virtual machine, but I think it will take a while.
If you really want to - you can look how the library works, try to recreate a minimal working library and figure out the point at which it stops working. At least I think that's the way I would pick to figure out what's going wrong. But I also think that you don't have the time and/or desire to look into it.
So, keep me informed if you can find out anything.

It might also be worth trying to create dialogue content that manually sets changing Height/Width using a timer. Thus, Avalonia will have to redraw its contents - then, perhaps, the dialog will appear automatically after Avalonia redraws it. If so, maybe we'll get closer to understanding what the problem might be.

After upgrading to Avalonia 11.0.7 (released 32 minutes ago!) it worked! I don't know why the nightly did not solve...

Wow, that's wonderful!


Standardize textual definition transmembrane transport

Hello,
Looking at the noted from the transport group http://wiki.geneontology.org/index.php/Transmembrane_transporters
We should update all definitions to 'The process in which [x] is transported from one side of a membrane to the other.'' Now it's a mix of that and what the groups had decided on for the top level class transport,

The definition of transport ; GO:0006810 is: The directed movement of substances (such as macromolecules, small molecules, ions) into, out of, within or between cells, or within a multicellular organism by means of some external agent such as a transporter or pore.

I suppose that this also needs to match the DOS design patterns. The incorrect definitions seem to all come from TG.
Thanks, Pascale

Hi @pgaudet ,
These definitions are for different granularities of transport. The first one is for transmembrane transport, the second is for general transport. I would go with the experts definitions whenever possible. We need to have the more general transport terms to describe the complexities of transport in anatomical structures like kidneys and digestive systems.

Hi all,
I standardizing the definitions and equivalence axioms of transmembrane transport as indicated in
https://github.com/geneontology/go-ontology/blob/master/src/design_patterns/transmembrane_transport.yaml
ie:
Equivalence axiom:
transport
and ('transports or maintains localization of' some %s)
and ('results in transport across' some membrane)
Textual definition: "The process in which a x is transported across a membrane."
If anyone has feedback on this please let me know soon.
@ValWood maybe ?

I think that's OK.
I did wonder why it was "transports or maintains localization of" rather than just "transports"
but  it might not  need to be so specific because if it "results in transport across a membrane" it must be transport rather than localization?

right... that's a while different issue. I had asked for that relation but I cannot see it yet. At the same time we'd have
transport
and transports some x
which sounds OK. I thought 'has input' might also be appropriate. Anyway for now I just want to standardize.
Thanks, Pascale

OK sounds good. Easy to restandardize if  necessary if  they are already standardized ;)

That's what I thought !


adds system codes for status view

fixes: https://github.com/Shippable/admiral/issues/2743

Please move all of this to the bottom of the file. We should not introduce new migrations in between.


Explicitly omit argument label for GArray.append

Third time is the charm!
Fixes #483 by adding omittedFirstArgLabelList and checking for any explicitly omitted labels in BuiltinGen and MethodGen.
Also deprecated GArray.append(value: Variant) and updated internal usages.

Glorious!   Thank you!


'value' is unavailable: introduced in iOS 12.0

Description
'value' is unavailable: introduced in iOS 12.0
Version
0.69.0
Output of npx react-native info
System:
OS: macOS 10.15.7
CPU: (4) x64 Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
Memory: 27.26 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
Yarn: 1.22.10 - ~/.nvm/versions/node/v14.17.0/bin/yarn
npm: 8.4.1 - ~/.nvm/versions/node/v14.17.0/bin/npm
Watchman: 4.7.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /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, 25, 26, 27, 28, 29, 30
Build Tools: 26.0.2, 26.0.3, 28.0.3, 29.0.2, 29.0.3, 30.0.3
System Images: android-25 | Google APIs ARM EABI v7a, android-29 | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.2 AI-202.76<IP_ADDRESS>51085
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_152 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.0.0 => 18.0.0
react-native: 0.69.0 => 0.69.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
npx react-native init example --template react-native-template-typescript
yarn start
open xcode run
Snack, code example, screenshot, or link to a repository

Same issue here. I'm also using Xcode 12.4 - Could that be the reason?

+1

My system：
macOS Catalina （10.15.7）
MacBook Pro (13-inch, Mid 2012)
Xcode Version：12.4 (12D4e)
The latest system cannot be upgraded，Could that be the reason?

same issue, please give me solution when u have. tks

+1

I have the same problem. I think the error is that the app runs iOS 14.4

Here's how I fixed it:

Open node_modules/react-native/scripts/react_native_pods.rb
Go to line no 401 >>> 'ios' => '11.0',
Change 11.0 to 12.0
Use patch-package to make a patch.
Run yarn
Run pod install
Go to ios/build/generated/ios/React-Codegen.podspec.json and confirm "platforms": { "ios": "12.0" }

That's all.

this worked, can you please explain your line of thinking/workflow that made you come to this solution?

4. Use patch-package to make a patch.

npx patch-package react-native

@craspadotcom You have to add the postinstall script in package.json so it patches the files when you install/update packages.
"scripts": {
    "postinstall": "patch-package",

  },

The error occurs because React Native 0.69 targets ios 12.4 in Podfile but the Codegen generated podspec still targets ios 11.0 while using ios 12+ apis. I think there should be a patch release that fixes this issue.

This fix worked for me

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

this was helpful my issue was resolved using this

you

Thanks for this. After so many tries on how to resolve this issue, this is the one that worked. 🍻

Update for version 0.70.3:
If you want to follow advice from @ammarahm-ed , the property is in a different file now:
diff --git a/node_modules/react-native/scripts/cocoapods/codegen_utils.rb b/node_modules/react-native/scripts/cocoapods/codegen_utils.rb
index 6fcbb15..7e457b9 100644
--- a/node_modules/react-native/scripts/cocoapods/codegen_utils.rb
+++ b/node_modules/react-native/scripts/cocoapods/codegen_utils.rb
@@ -84,7 +84,7 @@ class CodegenUtils
           'source' => { :git => '' },
           'header_mappings_dir' => './',
           'platforms' => {
-            'ios' => '11.0',
+            'ios' => '12.0',
           },
           'source_files' => "**/*.{h,mm,cpp}",
           'pod_target_xcconfig' => { "HEADER_SEARCH_PATHS" =>

+1

I had the same issue. Advice from @sesm worked for me

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

You saved my job man! I know this is because our old macs are not updating to the latest ios. Now i hope i earn enough to buy the new mac :)

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

You saved my job man! I know this is because our old macs are not updating to the latest ios. Now i hope i earn enough to buy the new mac :)

I'm glad this solution worked for you, Best of luck for your future endeavours :)

@ammarahm-ed 's and @sesm 's solution helped me as well. Thank you!

@OmarUsman777
I think If you set like this in Podfile, you don't have to change them manually everytime.
  ...
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    # NOTE: Change IPHONEOS_DEPLOYMENT_TARGET to 12.4.
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
      end
    end
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

Thank you so much. You saved my day.

Thank you very much. The below fix worked for me too, I am still in the old XCode Version 12.4.
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.

This is happening to me on XCode 14.2 as well since 2 days ago

This solution worked for me with Xcode 14.3RC
https://stackoverflow.com/a/74487309

To anyone that keeps having these issues and is using XcodeCloud, make sure to go to the workflow settings and choose the correct environment. In my case it was using the latest environment (14.3RC at the moment) and that was breaking everything. I selected spewcifically 14.2 and multiple things got fixed.

Can confirm this happens in Xcode 14.3. I downloaded RC2 today and this issue started. I was able to solve it by the following:
1. In your Xcode project navigator, select `Pods`.

2. Under Targets, select`React-Codegen` and set the window to `Build Settings`.

3. Under Deployment, set `iOS Deployment Target` to `12.4`.

4. Clean project and rebuild.

This almost worked for me.
I also had to update the build targets for react-native-quick-crypto and react-native-quick-base64

Thanks

Can confirm this happens in Xcode 14.3. I downloaded RC2 today and this issue started. I was able to solve it by the following:
1. In your Xcode project navigator, select `Pods`.

2. Under Targets, select`React-Codegen` and set the window to `Build Settings`.

3. Under Deployment, set `iOS Deployment Target` to `12.4`.

4. Clean project and rebuild.

This almost worked for me. I also had to update the build targets for react-native-quick-crypto and react-native-quick-base64. So if anyone relies on these dependencies as well, those need to be bumped.

Thanks man, you saved my day!

Do you know how this can be solved in Expo Managed Workflow? I added expo-build-properties plugin to increase the iOS Deployment Target to 13.0 but it didn't solve the issue. Still getting the 'value' is unavailable: introduced in iOS 12.0 issue.
[       'expo-build-properties',       {         ios: {           deploymentTarget: '13.0',         },       },     ],

Why was this issue closed? @orzhtml can you please reopen since it isn't fixed

This solution worked for me with Xcode 14.3RC
https://stackoverflow.com/a/74487309

This work for me

Do you know how this can be solved in Expo Managed Workflow? I added expo-build-properties plugin to increase the iOS Deployment Target to 13.0 but it didn't solve the issue. Still getting the 'value' is unavailable: introduced in iOS 12.0 issue. [ 'expo-build-properties', { ios: { deploymentTarget: '13.0', }, }, ],

That's cool if you use Expo. Our project doesn't however, so other workarounds are needed.

Can confirm this happens in Xcode 14.3. I downloaded RC2 today and this issue started. I was able to solve it by the following:
1. In your Xcode project navigator, select `Pods`.

2. Under Targets, select`React-Codegen` and set the window to `Build Settings`.

3. Under Deployment, set `iOS Deployment Target` to `12.4`.

4. Clean project and rebuild.

This almost worked for me. I also had to update the build targets for react-native-quick-crypto and react-native-quick-base64. So if anyone relies on these dependencies as well, those need to be bumped.

Thank you this worked perfectly!

Can confirm this happens in Xcode 14.3. I downloaded RC2 today and this issue started. I was able to solve it by the following:

In your Xcode project navigator, select Pods.
Under Targets, selectReact-Codegen and set the window to Build Settings.
Under Deployment, set iOS Deployment Target to 12.4.
Clean project and rebuild.

Thank you this worked perfectly!

Here's an expo config plugin that worked for me for managed Expo workflow (it updates the deployment target for all pods to 13.0)
/* eslint-disable @typescript-eslint/no-var-requires */
const { withDangerousMod, withPlugins } = require("@expo/config-plugins");
const {
  mergeContents,
} = require("@expo/config-plugins/build/utils/generateCode");
const fs = require("fs");
const path = require("path");

async function readFileAsync(path) {
  return fs.promises.readFile(path, "utf8");
}

async function saveFileAsync(path, content) {
  return fs.promises.writeFile(path, content, "utf8");
}

const withFixedDeploymentTarget = (c) => {
  return withDangerousMod(c, [
    "ios",
    async (config) => {
      const file = path.join(config.modRequest.platformProjectRoot, "Podfile");
      const contents = await readFileAsync(file);
      await saveFileAsync(file, fixDeploymentTarget(contents));
      return config;
    },
  ]);
};

function fixDeploymentTarget(src) {
  return mergeContents({
    tag: `rn-fix-deployment-target`,
    src,
    newSrc: `
   installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
               config.build_settings['SWIFT_VERSION'] = '5.0'
               config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
    end
  end
`,
    anchor: /post_install/,
    offset: 1,
    comment: "#",
  }).contents;
}

module.exports = (config) => withPlugins(config, [withFixedDeploymentTarget]);

Put this in "<project_root>/config-plugins/deployment-targets.js"
Then add to your app.json:
{
  "plugins": ["./config-plugins/deployment-targets"]
}

Then rm -rf ios => expo run:ios
Working for me! I like the fix

Do you have a edit that will only update the react-native codegen package, updating all of them seems a error prone?

@shoopapa I haven't tried to do it just with the one package but maybe can add an if statement in there to check for the package name? I'm not really well versed in pod file syntax. probably better to do it that for just react native codegen but doing it this way seems to be fine so far

Can confirm this happens in Xcode 14.3. I downloaded RC2 today and this issue started. I was able to solve it by the following:

In your Xcode project navigator, select Pods.
Under Targets, selectReact-Codegen and set the window to Build Settings.
Under Deployment, set iOS Deployment Target to 12.4.
Clean project and rebuild.

Thank you, it works perfectly for me.

Here's how I fixed it:

Open node_modules/react-native/scripts/react_native_pods.rb
Go to line no 401 >>> 'ios' => '11.0',
Change 11.0 to 12.0
Use patch-package to make a patch.
Run yarn
Run pod install
Go to ios/build/generated/ios/React-Codegen.podspec.json and confirm "platforms": { "ios": "12.0" }

That's all.
diff --git a/node_modules/react-native/scripts/react_native_pods.rb b/node_modules/react-native/scripts/react_native_pods.rb
index 7f6ebab..cea0fef 100644
--- a/node_modules/react-native/scripts/react_native_pods.rb
+++ b/node_modules/react-native/scripts/react_native_pods.rb
@@ -398,7 +398,7 @@ def get_react_codegen_spec(options={})
     'source' => { :git => '' },
     'header_mappings_dir' => './',
     'platforms' => {
-      'ios' => '11.0',
+      'ios' => '12.0',
     },
     'source_files' => "**/*.{h,mm,cpp}",
     'pod_target_xcconfig' => { "HEADER_SEARCH_PATHS" =>

The same issue happened to me in new Xcode 14.3. That's save me! Thanks! ❤

![image](https://user-images.githubusercontent.com/5866002/229302367-fb09c4cf-11f9-4f01-b85f-d08ea12e3df3.png)

@iway1 This works for me, updating all the pods isn't necessary
const { withDangerousMod, withPlugins } = require("@expo/config-plugins");
const { ExpoConfig } = require("@expo/config-types");
const {
  mergeContents,
} = require("@expo/config-plugins/build/utils/generateCode");
const { readFileSync, writeFileSync } = require("fs");
const { resolve } = require("path");

const withFixedDeploymentTarget = (c) => {
  return withDangerousMod(c, [
    "ios",
    async (config) => {
      const file = resolve(config.modRequest.platformProjectRoot, "Podfile");
      const contents = readFileSync(file, { encoding: "utf-8" });
      writeFileSync(file, fixDeploymentTarget(contents));
      return config;
    },
  ]);
};

function fixDeploymentTarget(src) {
  return mergeContents({
    tag: `rn-fix-deployment-target`,
    src,
    newSrc: `
  installer.pods_project.targets.each do |target|
    if target.to_s === 'React-Codegen'
      target.build_configurations.each do |config|
        config.build_settings['SWIFT_VERSION'] = '5.0'
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
      end
    end
  end
`,
    anchor: /post_install/,
    offset: 1,
    comment: "#",
  }).contents;
}

module.exports = (config) => withPlugins(config, [withFixedDeploymentTarget]);

Here is edit for only patching React-Codegen
At least temporarily, I recommend this solution if using expo, manually editing the podfile isn't optimal in the expo workflow

@shoopapa nice - I also strongly recommend not manually editing any native files at all with expo managed workflow, it's a really big advantage to be able to not care about the ios/android folders and to be able to regenerate them easily.

I have this problem after updating xcode from version 14.2 to 14.3. The above solution does the trick, but it's very annoying to have to do this every time you run pod-install. Has anyone found a permanent solution to this problem?

This solution worked for me with Xcode 14.3RC
https://stackoverflow.com/a/74487309

This worked like magic.

test your fix on build with hermes and fabric enabled

This solution worked for me with Xcode 14.3RC
https://stackoverflow.com/a/74487309

This worked like magic.

This is happening with Xcode Cloud when you have Xcode set to 14.3RC, if you change it to 14.2 you are good to go.
I wonder if this is due to changes in Swift 5.8.

How to change this? Steps?

Hey folks, just an headsup: we already landed the change that fixes this correctly in 36759 and we are about to release the supported versions of React Native with their right fixes:

0.69: #36767
0.70: #36768
0.71: #36769

Expect them to land later this week.

Hi! This solution helped me a lot!

👋 everyone!
We have just now finished rolling out new patch releases for the versions in the release support window to address this problem, check them out:

https://github.com/facebook/react-native/releases/tag/v0.71.6
https://github.com/facebook/react-native/releases/tag/v0.70.8
https://github.com/facebook/react-native/releases/tag/v0.69.9

They should address this problem fully.

I upgraded from v0.70.5 -> v0.70.8 and I'm still getting the error :(
For instance, in (ios/build/generated/ios/FBReactNativeSpec/FBReactNativeSpec.h:2598:110):
d[@"DEFAULT_BACKGROUND_COLOR"] = DEFAULT_BACKGROUND_COLOR.has_value() ? @((double)DEFAULT_BACKGROUND_COLOR.value()) : nil;
       |                                                                                ^ 'value' is unavailable: introduced in iOS 12.0

Just don't install new versions of Xcode in the early days)) What are you hoping for?

I upgraded from v0.70.5 -> v0.70.8 and I'm still getting the error :(
For instance, in (ios/build/generated/ios/FBReactNativeSpec/FBReactNativeSpec.h:2598:110):
d[@"DEFAULT_BACKGROUND_COLOR"] = DEFAULT_BACKGROUND_COLOR.has_value() ? @((double)DEFAULT_BACKGROUND_COLOR.value()) : nil;
       |                                                                                ^ 'value' is unavailable: introduced in iOS 12.0

I had the same issue, applied the same fix (upgrade from v0.70.6 to v0.70.8) and still have the issue again as well. I'm not all that familiar with the Expo build environment yet but I tried to reset/clean everything as much as possible. I fully removed the ios build directory, then ran npx expo prebuild --clean followed by npx expo run:ios and get the exact same error still. Tried running pod install in the ios directory too, that works without error. I confirmed that react-native package is now at 0.70.8 version. Any ideas? Thanks.

👋 everyone!
We have just finished rolling out new patch releases for the versions in the release support window to address this problem, check them out:
* https://github.com/facebook/react-native/releases/tag/v0.71.6

* https://github.com/facebook/react-native/releases/tag/v0.70.8

* https://github.com/facebook/react-native/releases/tag/v0.69.9

They should address this problem fully.

This worked for me, after npm install, bundle install and pod install. Thanks kelset!

Just had this issue and applying the change to all the pods didn't cut it for me. So instead that's what worked for me.
# Fix for use_frameworks! :linkage => :static
      react_native_post_install(installer)
      installer.pods_project.targets.each do |target|
        if target.name == 'RCT-Folly'
          target.build_configurations.each do |config|
            config.build_settings['HEADER_SEARCH_PATHS'] = "$(inherited) ${PODS_ROOT}/fmt/include"
          end
        end
      # Change the deployment target to 12.4 for React-Codegen
        if target.name == 'React-Codegen'
          target.build_configurations.each do |config|
            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
          end
        end
      end
      # __apply_Xcode_12_5_M1_post_install_workaround(installer)
      installer.pods_project.build_configurations.each do |config|
      config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
    end

downgrading to xcode 14.2 also working.

Yup. Upgrading from 0.71.4 to 0.71.6 fixes this issue.

Here's how I fixed it:

Open node_modules/react-native/scripts/react_native_pods.rb
Go to line no 401 >>> 'ios' => '11.0',
Change 11.0 to 12.0
Use patch-package to make a patch.
Run yarn
Run pod install
Go to ios/build/generated/ios/React-Codegen.podspec.json and confirm "platforms": { "ios": "12.0" }

That's all.
diff --git a/node_modules/react-native/scripts/react_native_pods.rb b/node_modules/react-native/scripts/react_native_pods.rb
index 7f6ebab..cea0fef 100644
--- a/node_modules/react-native/scripts/react_native_pods.rb
+++ b/node_modules/react-native/scripts/react_native_pods.rb
@@ -398,7 +398,7 @@ def get_react_codegen_spec(options={})
     'source' => { :git => '' },
     'header_mappings_dir' => './',
     'platforms' => {
-      'ios' => '11.0',
+      'ios' => '12.0',
     },
     'source_files' => "**/*.{h,mm,cpp}",
     'pod_target_xcconfig' => { "HEADER_SEARCH_PATHS" =>

Thank you very much; this was super helpful.

👋 everyone!
We have just finished rolling out new patch releases for the versions in the release support window to address this problem, check them out:
* https://github.com/facebook/react-native/releases/tag/v0.71.6

* https://github.com/facebook/react-native/releases/tag/v0.70.8

* https://github.com/facebook/react-native/releases/tag/v0.69.9

They should address this problem fully.

This worked for me, after npm install, bundle install and pod install. Thanks kelset!

Unfortunately this only fixed things for me for the React Native stuff.
I guess I'll have to make an issue on Quick Crypto to get them to fix the same issue.

https://stackoverflow.com/a/75915794/12105742
This solution works for me

https://stackoverflow.com/a/75915794/12105742
This solution works for me

thank you, it worked for me

https://stackoverflow.com/a/75915794/12105742
This solution works for me

Thank's, it worked

if anybody with with react native 0.70 still facing this issue please  upgrade to latest react native version
1.npx react-native upgrade
2. cd ios
3. pod install
4. Reopen xcode and build

https://mrdevgeek.com/xcode-14-3-simulator-16-4-build-failure-how-to-fix-value-is-unavailable-introduced-in-ios-12-0-error-with-react-native-0-71-5/
work for me

@eliot-ye is great works like a charm believe

@OmarUsman777
I think If you set like this in Podfile, you don't have to change them manually everytime.
  ...
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    # NOTE: Change IPHONEOS_DEPLOYMENT_TARGET to 12.4.
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
      end
    end
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

@kouhot 's solution worked for me. Had to add this to Podfile and then Clean and run pod install again, and everything worked without error. Thanks kouhot!

Guys, don't do anything fancy, just update to the latest minor version, delete pods, Podfile.lock, reinstall the pods with pod install --repo-update, and everything should work.

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

is there a better way to do this? an automated way via cmd line? I have over 100 instances where this happens and doing it by hand is insane.

In iOS Folder go to Pods/Pods.xcodeproj/xcuserdata/project.pbxproj
Change all the 'IPHONEOS_DEPLOYMENT_TARGET = 11.0' to 'IPHONEOS_DEPLOYMENT_TARGET = 12.4'. save and run.
Note: every time you pod install it will change so again you have to do it. If there is better approach please do mention.

is there a better way to do this? an automated way via cmd line? I have over 100 instances where this happens and doing it by hand is insane.

Update to a version that already fixed it.

Here's how I fixed it:

Open node_modules/react-native/scripts/react_native_pods.rb
Go to line no 401 >>> 'ios' => '11.0',
Change 11.0 to 12.0
Use patch-package to make a patch.
Run yarn
Run pod install
Go to ios/build/generated/ios/React-Codegen.podspec.json and confirm "platforms": { "ios": "12.0" }

That's all.
diff --git a/node_modules/react-native/scripts/react_native_pods.rb b/node_modules/react-native/scripts/react_native_pods.rb
index 7f6ebab..cea0fef 100644
--- a/node_modules/react-native/scripts/react_native_pods.rb
+++ b/node_modules/react-native/scripts/react_native_pods.rb
@@ -398,7 +398,7 @@ def get_react_codegen_spec(options={})
     'source' => { :git => '' },
     'header_mappings_dir' => './',
     'platforms' => {
-      'ios' => '11.0',
+      'ios' => '12.0',
     },
     'source_files' => "**/*.{h,mm,cpp}",
     'pod_target_xcconfig' => { "HEADER_SEARCH_PATHS" =>

When i i have try this soultion then i am getting this error lol now do i fixed this issues i think your solution does't work for me it is creating another problem, i guess everyone getting the same issues after trying your solutions like this  i am totally fed -up with your solution pls someone suggest me another solution accepting this one

isn't this solved already, i am facing the same issue?

👋 everyone!
We have just finished rolling out new patch releases for the versions in the release support window to address this problem, check them out:

https://github.com/facebook/react-native/releases/tag/v0.71.6
https://github.com/facebook/react-native/releases/tag/v0.70.8
https://github.com/facebook/react-native/releases/tag/v0.69.9

They should address this problem fully.

I tried to build RN 71.10 on XCode 14.3.1 and got this error again.
I checked Codegen_utils.rb and it uses min_ios_version_supported definition which returns 12.4 already in react_native_pods.rb.

@efecantekin try cleaning the build using CMD/CRTL+SHIFT+K on xcode and try add the pods again npx pod-install - this worked for me

diff --git a/node_modules/react-native/scripts/cocoapods/codegen_utils.rb b/node_modules/react-native/scripts/cocoapods/codegen_utils.rb
index 3694e68..caa9794 100644
--- a/node_modules/react-native/scripts/cocoapods/codegen_utils.rb
+++ b/node_modules/react-native/scripts/cocoapods/codegen_utils.rb
@@ -85,7 +85,7 @@ class CodegenUtils
           'source' => { :git => '' },
           'header_mappings_dir' => './',
           'platforms' => {
-            'ios' => '11.0',
+            'ios' => '12.4',
           },
           'source_files' => "**/*.{h,mm,cpp}",
           'pod_target_xcconfig' => { "HEADER_SEARCH_PATHS" =>

in  "react-native": "0.71.2"
npx patch-package react-native
this works!
try this

It still happens with XCode 14.3.1 and RN 0.71.8 on several modules like : react-native-simple-toast, react-native-svg, react-native-permissions...
The problem started to pop in my project after updating XCode from 14.1 to 14.3.1.

I fixed this by upgrading react-native from 0.71.4 to  0.71.11

This issue was fixed for me by bumping react-native from 0.70.6 to 0.70.10, in order to get this fix: https://github.com/facebook/react-native/commit/c5e549e694607cd576be8fcb5ed909fec2ed6dce
So if you're still on react-native 0.70.x, you can still get support for Xcode 14.3 using minor version 10.

I just remove pods folder under ios

@OmarUsman777
I think If you set like this in Podfile, you don't have to change them manually everytime.
  ...
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    # NOTE: Change IPHONEOS_DEPLOYMENT_TARGET to 12.4.
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
      end
    end
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

thanks this work for me

Still having the issue after performing these steps:
1 - upgrade react-native from 0.71.8 to 0.71.12
2 - Deleted Pods and Podfile.lock
3 - run RCT_NEW_ARCH_ENABLED=1 bundle exec pod install in /ios folder
4  - clean build in XCode and build...

@OmarUsman777
I think If you set like this in Podfile, you don't have to change them manually everytime.
  ...
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    # NOTE: Change IPHONEOS_DEPLOYMENT_TARGET to 12.4.
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
      end
    end
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

@kouhot 's solution worked for me. Had to add this to Podfile and then Clean and run pod install again, and everything worked without error. Thanks kouhot!

Thank you, This worked for me

The second solution is:

In the Xcode Project select "Pods"
Select target that throws errors
Select Build Settings
Bump iOS Target to required version

But you should do this every time when project is updates

You've saved my life.  Hours upon hours of trying to fix it, and this did the trick.

@OmarUsman777
I think If you set like this in Podfile, you don't have to change them manually everytime.
  ...
  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    # NOTE: Change IPHONEOS_DEPLOYMENT_TARGET to 12.4.
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
      end
    end
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

This worked on my project:
"react": "18.1.0",
"react-native": "0.70.6",
XCode Version 14.3
MacBookAir M1 - MacOS Ventura 13.0

just upgrade react native version to 0.72.3 and pod install fix it for me

The second solution is:

In the Xcode Project select "Pods"
Select target that throws errors
Select Build Settings
Bump iOS Target to required version

But you should do this every time when project is updates

You've saved my life. Hours upon hours of trying to fix it, and this did the trick.

Today, what is the required version? ios12? or 16?

Today, what is the required version? ios12? or 16?

@holicstudio depends on your RN version. For the current version, 0.72.4, it's 12.4: https://github.com/facebook/react-native/blob/v0.72.4/packages/react-native/scripts/react_native_pods.rb#L41
You shouldn't need to manually change the version in the Pods project settings with recent RN versions though, the template Podfile references the above-linked code dynamically (see https://github.com/facebook/react-native/blob/v0.72.4/packages/react-native/scripts/react_native_pods.rb#L41). So, as RN updates, it'll change the version the Pods project is looking for (as long as you remember to pod install after upgrading).
Also, you may have other dependencies that pull up this min required version (for example I believe Expo currently needs 13+ if you're using that in your RN project)

min_ios_version_supported

How to configure only once since the project is updated :-?

I have an Apple Macbook Pro M3 with Xcode 15.3.
If anyone out there is unable to solve it, try this version:
The IPHONEOS_DEPLOYMENT_TARGET should be 13.0. It should be more than 12.4.s

target.build_configurations.each do |config|
  config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
  if target.name == 'react-native-config'
    config.build_settings['ENVFILE'] = ENVFILES[config.name]
  end
  config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = "arm64"
end


encode() raises an RSA lib error when using a small RSA PSS key

When calling JWT.encode() using an RSA PSS key of length 1024, exponent of 3, and digest of 512, the following error is raised:

/Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt/jwa/ps.rb:18:in "sign_pss": RSA lib (OpenSSL::PKey::RSAError)
from /Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt/jwa/ps.rb:18:in "sign"
from /Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt/encode.rb:48:in "signature"
from /Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt/encode.rb:58:in "encode_signature"
from /Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt/encode.rb:32:in "encoded_signature"
from /Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt/encode.rb:18:in "segments"
from /Users/bsrna/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/jwt-2.9.3/lib/jwt.rb:30:in "encode"

This is the code block used for testing it:
require 'openssl'
require 'jwt'

key = OpenSSL::PKey::RSA.new(1024, 3)
key.sign_pss("SHA-512", "test", salt_length: 62, mgf1_hash: "SHA-512")
JWT.encode("test", key, 'PS512')

It was able to run key.sign_pss successfully, but JWT.encode hit the error.
The installed versions are jwt 2.9.3 and openssl 3.2.

When using :digest for the salt_length, this error occurs with digest 512 on smaller keys. I think :digest sets the salt length to 64 but the actual acceptable maximum from sign_pss is 62.

Think your observations are correct.
Smaller keys will not work. To be noted the JWA RFC states that key length of 2048 MUST be used ref
Think we could add a validation to the keys to give a more user-friendly message, but think the constraint needs to go into 3.0 because shorter keys could have worked before.


Crash during optional key path access

Description
I have code that appends key paths that is crashing at runtime when passing the key path to a value's key path subscript.
Reproduction
struct Foo {
  var bar: Bar?
}
struct Bar {
  var baz: Int?
}
extension Optional {
  subscript(default default: Wrapped) -> Wrapped {
    self ?? `default`
  }
}

let foo = Foo()
let kp1 = \Foo.bar
let kp2 = kp1.appending(path: \.?.baz)
let kp3 = kp2.appending(path: \.[default: 5])
foo[keyPath: kp3]  // 💥

💥 Could not cast value of type 'Swift.Optional<()>' (0x1df122378) to 'Swift.Int' (0x1df11e138).

Stack dump
N/A

Expected behavior
I expect this code not to crash, and ideally return the default 5.
Environment
swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-<IP_ADDRESS>.56 clang-15<IP_ADDRESS>.5)
Target: arm64-apple-macosx14.0
Additional information
No response

/cc @Azoy, @xedin: I think you've both been in key path land recently.

This must be something in implementation of KeyPath itself, foo[keyPath: kp3] seems correct to me, it takes KeyPath<Foo, Int> and produces Int. Not sure whether Optional<()> even comes from since it not there in any of the solutions.

i've looked into the cause of this behavior a bit (associated swift forums thread here), and have some thoughts & questions on the issue, and what can potentially be done about it.
what i believe is happening is that the logic for keypath projection contains a built-in assumption that the presence of an optionally-chained component implies that the keypath must end in an optional value. this is explicitly enforced by an internal invariant (only enabled in internal builds), and the runtime cast failure leading to the crash is due to this nearby force-cast which assumes the invariant held.
now, brainstorming ideas for how to fix this – it seems to address the issue we will likely need a change to how optional-chains which result in nil 'break' out of the projection loop. currently they 'jump' to the end, but they instead probably should only advance to the next component that was explicitly appended. i think this information could probably be stored in the component header when an append operation is performed.
does that seem like a reasonable approach to take?

@jamieQ Thanks for looking into this! @Azoy may be able to steer you in the right direction, as he's working on #70451 and briefly looked at this issue.


Add kazoo dependency for running under docker

dd-agent (now?) requires kazoo by way of the config backends for service discovery under docker. Tests were failing, this makes them pass.
R? @cory-stripe

👍

self-approving because of cibot not picking this up


Redmine #7301 Provide word-break opportunity for dynamic DNS host names

This can later also be extended very easily to places like firewall_aliases.php etc that show full host/domain FQDN names in a column.
And it is easily modified in 1 place if we want to also break on any other characters that might be convenient.

Would prefer the break before dot rather than after so it does like this.
somereallylonghosthame
.somereallylongdomainname
.com
Rather than like this.
somereallylonghosthame.
somereallylongdomainname.
com
Host/domain names just seem more natural as.
host
dot this
dot that
dot com
I know kinda picky isn't it.

Not picky - I had not thought about it, and what you say is true.

Maybe a generic function that accepts string, break opportunity character, and fore/aft break position.
function word_break_opportunity ($str, $chr, $fore_aft)

A function like that will be good if we refactor the other places that put word break opportunities in other types of potentially long strings. Then this insert_word_breaks_in_domain_name() would call it, and it would also be called by other new functions like insert_word_breaks_in_alias_name() insert_word_breaks_in_myspecialtypeofstring() and so on, which would specify for different "types" of string, what is the preferred set of wbr-related chars.

@sbeaver-netgate @rbgarga @jim-p this is another little one that would be easy to review.


feat(devicepreferences): initial suppport for i18n

add create and get endpoints for now
unit test DevicePreferencesEndpoint without client proxy
bump axios to resolve vulnerability

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project (npm run lint produces no warnings/errors)
[x] Any required documentation has been added
[x] I have added tests to cover my changes

:tada: This PR is included in version 1.12.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add time to results.json data structure

Consider adding time field HH24:MI:SS to the results data structure so that it is easier to show productivity ( processing rates ) during after-the-fact performance analysis.

Done see https://github.com/LukePrior/nbn-upgrade-map/blob/main/results/combined-suburbs.json


run build.py get error AttributeError: module 'argparse' has no attribute 'BooleanOptionalAction'

hi i want update to 0.51 from 0.50
i run  python build.py build --desktop cpu -v and python build.py build --help get same error 👇
Traceback (most recent call last):
  File "build.py", line 341, in <module>
    Argument().command().run()
  File "build.py", line 310, in __init__
    build_command_parser.add_argument('--resources', action=argparse.BooleanOptionalAction, default=True)
AttributeError: module 'argparse' has no attribute 'BooleanOptionalAction'

this my console

I think this project is amazing
I want to contribute code but i will only unity
so i can help what (●'◡'●)

i can play 0.5.0 in UnityEditor
i git clone 0.5.1 buil fail

we ae getting some python build error (on Mac OS), the previous build script was working for us.

we ae getting some python build error (on Mac OS), the previous build script was working for us.

so i Should be use make cpu and make install to build 0.5.1 right ?

ah no sorry we are not able to build 0.5.1 at all, 0.5 was building for us.

ah no sorry we are not able to build 0.5.1 at all, 0.5 was building for us.

ok i back 0.5.0
wait next perfect version
thank you

I overlooked that Python 3.9 is required to use argparse.BooleanOptionalAction.
As a workaround, will you upgrade python and try again?

thanks @homuler using python 3.9 fixed that build issue, but we did now hit the compilation error
"In file included from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/gl_errors.cc:23:
external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/portable_egl.h:19:10: fatal error: 'EGL/egl.h' file not found
#include <EGL/egl.h>"
but I can start a new issue for that now.

That egl.h issue is triggered by building 'gpu' for desktop - when I built for cpu it worked

use python3.9 all ok
and set not work in powershell ,use cmd in windows

Using pyenv / Python 3.9.0 worked for me, as well.
I highly suggest using pyenv to manage python versions, rather than installing multiple versions and crossing one's fingers :)

I updated README and also introduced Docker environments.

I put the library with BooleanOptionalAction in the same path as build.py. The build went without a problem.
wget --no-clobber https://raw.githubusercontent.com/python/cpython/master/Lib/argparse.py


Wrong architecture being detected in Steam.Init() method.

Python 3.4, the expression on line 37:
if sys.maxsize > 2**32 is False:
always returns false, because 2**32 is False has greater precedence than sys.maxsize > 2**32.
You should surround the comparison with parentheses to fix it. I.e.
if (sys.maxsize > 2**32) is False:

Hmm, good call.  Though I feel like this was always a bad way to find the system bit size.  Will update this now though!  Cheers.


Can't copy from Lora Loader's Trained Words field

Recently I cannot copy from the Trained Words field of the Lora info dialog. Neither Ctrl+C nor rightclick+copy do anything.
The pasted content seems to be just   empty space.
"Copy selected" works fine, but that is not for Trained Words.

Checkpoint Info dialog seems to have the same issue - I can't copy any text from it. So it is not only the "text field" of Trained Words.

I also cannot copy from node Property Panel dialogs. So it is likely not an issue with pythongosssss.
Copying from node text areas works fine though.
Weird.

It's a problem even on a fresh install without any custom nodes. I guess I'll close this, since it seems to be a problem with Comfy itself.


Move LocalChange.kt to entities package and rename to LocalChangeEntity.kt

Approved but there's a spotless failure (line length) in DatabaseImplTest.kt. Please fix before merging.

Thanks @deepankarb !


client Closing session with error: Application error 0x100

Hello, I ran the example code of quic-go. I turned on the server with main.go (/example/main.go) and sent a request to the server turned on with main.go (/example/client/main.go).
The request was received to the server, and the result was returned, but the result is returned and the following error occurs: "server Peer closed session with error: Application error 0x100" The following error occurs and the server is disconnected. ??
[client log]
server Peer closed session with error: Applicaiotn error 0x100
server Connection 0x....... closed.
thank you.

Not sure why you think this is a bug. This is the NO_ERROR code:
https://github.com/lucas-clemente/quic-go/blob/85c19fbb5ae34fd81238c424fe1e11cd30646f72/http3/error_codes.go#L12

Wouldn't it make more sense if the message was more descriptive?
Saying that "peer closed session with error" could make people assume that there was an error.


Obscure password on and off functionality in android app

Additional Context:
I am a GSSOC'24 contributor and would like to work on the issue.

If this issue is not resolved yet please assign it to me.

Is this issue solved?
if not assign it to me


socket error on client when payload bigger than 4096 esp32

Hello,
I'm currently facing the issue that I'm getting the error "Socket error on client xxxxxx, disconnecting" from my broker.
But this is only the case when i publish data that is bigger than 4096 Bytes.
I have already set the buffer size a little bit bigger, but that does not seem to be the problem.
#include "WiFi.h"
#include <PubSubClient.h>
#include <WiFiClientSecure.h>

WiFiClientSecure clientMqtt;
PubSubClient mqttClient(clientMqtt);

mqttClient.setBufferSize(8192);
mqttClient.setKeepAlive(60);
mqttClient.setSocketTimeout(60);´

Funny thing is the broker gets this message. Until 432 everything is correct, but then the message starts again.
{"deviceID":"243bd1a3c9c8","data": {"0":1,"1":1,"2":4,"3":4,"4":4,"5":4,"6":4,"7":4,"8":4,"9":7,"10":1,"11":0,"12":0,"13":32766,"14":32766,"15":32766,"16":32766,"17":32766,"18":32766,"19":101,"20":2,"21":0,"22":0,"23":0,"24":0,"25":10,"26":30,"27":1,"28":25,"29":65531,"30":0,"31":20,"32":42,"33":1,"34":5,"35":3,"36":32766,"37":32766,"38":32766,"39":32766,"40":70,"41":100,"42":60,"43":50,"44":99,"45":15,"46":3,"47":3,"48":120,"49":3,"50":3,"51":99,"52":5,"53":1,"54":32766,"55":32766,"56":32766,"57":32766,"58":32766,"59":32766,"60":1,"61":0,"62":4,"63":100,"64":0,"65":8,"66":0,"67":0,"68":20,"69":44,"70":0,"71":0,"72":1,"73":1,"74":1,"75":9,"76":1,"77":1,"78":0,"79":0,"80":55,"81":45,"82":99,"83":65,"84":65,"85":0,"86":3,"87":0,"88":0,"89":1,"90":32766,"91":32766,"92":32766,"93":32766,"94":32766,"95":32766,"96":32766,"97":32766,"98":32766,"99":32766,"100":18,"101":10,"102":32766,"103":20,"104":35,"105":50,"106":65,"107":0,"108":1,"109":15,"110":3,"111":32766,"112":32766,"113":0,"114":18,"115":10,"116":220,"117":20,"118":35,"119":50,"120":65,"121":0,"122":1,"123":15,"124":3,"125":50,"126":3,"127":0,"128":18,"129":10,"130":200,"131":20,"132":35,"133":50,"134":65,"135":0,"136":1,"137":15,"138":3,"139":50,"140":3,"141":0,"142":18,"143":10,"144":280,"145":20,"146":35,"147":50,"148":65,"149":0,"150":1,"151":15,"152":3,"153":50,"154":3,"155":0,"156":18,"157":10,"158":208,"159":20,"160":35,"161":50,"162":65,"163":0,"164":1,"165":15,"166":3,"167":50,"168":3,"169":0,"170":18,"171":10,"172":200,"173":20,"174":35,"175":50,"176":65,"177":0,"178":1,"179":15,"180":3,"181":50,"182":3,"183":0,"184":18,"185":10,"186":200,"187":20,"188":35,"189":50,"190":65,"191":0,"192":1,"193":15,"194":3,"195":50,"196":3,"197":0,"198":18,"199":10,"200":200,"201":20,"202":35,"203":50,"204":65,"205":0,"206":1,"207":15,"208":3,"209":50,"210":3,"211":0,"212":0,"213":65534,"214":65496,"215":3,"216":24,"217":12,"218":2018,"219":26,"220":12,"221":2022,"222":1200,"223":1200,"224":1200,"225":1200,"226":1200,"227":1200,"228":32766,"229":32766,"230":32766,"231":32766,"232":32766,"233":32766,"234":1200,"235":1200,"236":1200,"237":1200,"238":1200,"239":1200,"240":5,"241":5,"242":5,"243":5,"244":5,"245":5,"246":5,"247":5,"248":0,"249":0,"250":0,"251":0,"252":0,"253":0,"254":0,"255":0,"256":0,"257":0,"258":0,"259":0,"260":0,"261":0,"262":0,"263":0,"264":15,"265":0,"266":0,"267":0,"268":0,"269":0,"270":0,"271":0,"272":0,"273":0,"274":1200,"275":1200,"276":15,"277":0,"278":0,"279":0,"280":0,"281":0,"282":0,"283":0,"284":0,"285":0,"286":1200,"287":1200,"288":15,"289":0,"290":0,"291":0,"292":0,"293":0,"294":0,"295":0,"296":0,"297":0,"298":1200,"299":1200,"300":15,"301":0,"302":0,"303":0,"304":0,"305":0,"306":600,"307":2200,"308":1200,"309":1200,"310":1200,"311":1200,"312":600,"313":2200,"314":1200,"315":1200,"316":1200,"317":1200,"318":600,"319":2200,"320":1200,"321":1200,"322":1200,"323":1200,"324":600,"325":2200,"326":1200,"327":1200,"328":1200,"329":1200,"330":600,"331":2200,"332":1200,"333":1200,"334":1200,"335":1200,"336":600,"337":2200,"338":1200,"339":1200,"340":1200,"341":1200,"342":600,"343":2200,"344":1200,"345":1200,"346":1200,"347":1200,"348":600,"349":2200,"350":1200,"351":1200,"352":1200,"353":1200,"354":600,"355":2200,"356":1200,"357":1200,"358":1200,"359":1200,"360":600,"361":2200,"362":1200,"363":1200,"364":1200,"365":1200,"366":600,"367":2200,"368":1200,"369":1200,"370":1200,"371":1200,"372":600,"373":2200,"374":1200,"375":1200,"376":1200,"377":1200,"378":600,"379":2200,"380":1200,"381":1200,"382":1200,"383":1200,"384":600,"385":2200,"386":1200,"387":1200,"388":1200,"389":1200,"390":600,"391":2200,"392":1200,"393":1200,"394":1200,"395":1200,"396":600,"397":2200,"398":1200,"399":1200,"400":1200,"401":1200,"402":600,"403":2200,"404":1200,"405":1200,"406":1200,"407":1200,"408":600,"409":2200,"410":1200,"411":1200,"412":1200,"413":1200,"414":600,"415":2200,"416":1200,"417":1200,"418":1200,"419":1200,"420":600,"421":2200,"422":1200,"423":1200,"424":1200,"425":1200,"426":600,"427":2200,"428":1200,"429":1200,"430":1200,"431":1200,"432"0�. device/243bd1a3c9c8/data{"deviceID":"243bd1a3c9c8","data": {"0":1,"1":1,"2":4,"3":4,"4":4,"5":4,"6":4,"7":4,"8":4,"9":7,"10":1,"11":0,"12":0,"13":32766,"14":32766,"15":32766,"16":32766,"17":32766,"18":32766,"19":101,"20":2,"21":0,"22":0,"23":0,"24":0,"25":10,"26":30,"27":1,"28":25,"29":65531,"30":0,"31":20,"32":42,"33":1,"34":5,"35":3,"36":32766,"37":32766,"38":32766,"39":32766,"40":70,"41":100,"42":60,"43":50,"44":99,"45":15,"46":3,"47":3,"48":120,"49":3,"50":3,"51":99,"52":5,"53":1,"54":32766,"55":32766,"56":32766,"57":32766,"58":32766,"59":32766,"60":1,"61":0,"62":4,"63":100,"64":0,"65":8,"66":0,"67":0,"68":20,"69":44,"70":0,"71":0,"72":1,"73":1,"74":1,"75":9,"76":1,"77":1,"78":0,"79":0,"80":55,"81":45,"82":99,"83":65,"84":65,"85":0,"86":3,"87":0,"88":0,"89":1,"90":32766,"91":32766,"92":32766,"93":32766,"94":32766,"95":32766,"96":32766,"97":32766,"98":32766,"99":32766,"100":18,"101":10,"102":32766,"103":20,"104":35,"105":50,"106":65,"107":0,"108":1,"109":15,"110":3,"111":32766,"112":32766,"113":0,"114":18,"115":10,"116":220,"117":20,"118":35,"119":50,"120":65,"121":0,"122":1,"123":15,"124":3,"125":50,"126":3,"127":0,"128":18,"129":10,"130":200,"131":20,"132":35,"133":50,"134":65,"135":0,"136":1,"137":15,"138":3,"139":50,"140":3,"141":0,"142":18,"143":10,"144":280,"145":20,"146":35,"147":50,"148":65,"149":0,"150":1,"151":15,"152":3,"153":50,"154":3,"155":0,"156":18,"157":10,"158":208,"159":20,"160":35,"161":50,"162":65,"163":0,"164":1,"165":15,"166":3,"167":50,"168":3,"169":0,"170":18,"171":10,"172":200,"173":20,"174":35,"175":50,"176":65,"177":0,"178":1,"179":15,"180":3,"181":50,"182":3,"183":0,"184":18,"185":10,"186":200,"187":20,"188":35,"189":50,"190":65,"191":0,"192":1,"193":15,"194":3,"195":50,"196":3,"197":0,"198":18,"199":10,"200":200,"201":20,"202":35,"203":50,"204":65,"

This looks like my string has an overflow.
"431":1200,"432"0�. device/243bd1a3c9c8/data{"deviceID":"243bd1a3c9c8","data": {"0":1,"1":1,"2":4,"3":4,"4":4,"

 String publishTopic = "";
  String socketString = "{\"deviceID\":\"";
  socketString += macString;
  socketString += "\",\"data\": {";

  for (int i = 0; i < 600; i++)
  {
    socketString += "\"";
    socketString += i;
    socketString += "\":";
    socketString += getValue(i);
    if (i < 599)
    {
      socketString += ",";
    }
  }
  socketString += " }}";

  publishTopic = "device/";
  publishTopic += macString;
  publishTopic += "/data";
  mqttClient.publish(publishTopic.c_str(), socketString.c_str());
  Serial.println("send mqtt");

Edit: I'm using Arduino as Component

Update:
I'm now using the .print() function to send data. First that seemed to fix the problem but then i recognized that this function is extremly slow (~5 Seconds to send the data).
Now I'm using a combination of both approaches. But i'm not really happy with that.
Maybe anyone could help me?
void sendDeviceData()
{
  int sendLength = 0;
  String publishTopic = "";
  String socketString = "{\"deviceID\":\"";
  socketString += macString;
  socketString += "\",\"data\": {";
  socketString += " }}";

  sendLength = socketString.length();

  for (int i = 0; i < 1200; i++)
  {
    socketString = "\"";
    socketString += i;
    socketString += "\":";
    socketString += getValue(i);
    if (i < 1199)
    {
      socketString += ",";
    }
    sendLength += socketString.length();
  }

  Serial.println(sendLength);

  publishTopic = "device/";
  publishTopic += macString;
  publishTopic += "/data";

  mqttClient.beginPublish(publishTopic.c_str(), (sendLength-1), false);
  mqttClient.print("{\"deviceID\":\"");
  mqttClient.print(macString);
  mqttClient.print("\",\"data\": {");
  for(int j = 0; j < 6; j++) {

    socketString = "";
    for (int i = 0; i < 200; i++)
    {
      socketString += "\"";
      socketString += i+(j*200);
      socketString += "\":";
      socketString += getValue(i+(j*200));
      if (i+(j*200) < 1199)
      {
        socketString += ",";
      }
    }
     mqttClient.print(socketString);
  }
  mqttClient.print("}}");

  mqttClient.endPublish();

  //mqttClient.publish(publishTopic.c_str(), socketString.c_str());
  Serial.println("send mqtt");
}

@fsommer1968 thanks for your help, i will try this.


Use proper signals

Description:
We finally were using the aiohttp signals correctly since 3.4.4, we can move the work around now.
We were also using a deprecated way of running a HTTP server in emulated Hue.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

For the IP ban, the proper solution would be for it to be migrated to the storage helper.

I also realized that auth being a middleware means it's also being run for static resource requests 🤷♂  I guess in a perfect world NGINX would sit in front of the static endpoint and serve that.


downgrade Play dependency to 2.8.0

Fixes #6

Why downgrade the dependencies?
I would prefer to keep dependencies up to date to latest.

It's not really downgrading but rather expressing the minimum supported version.
If your project uses Play 2.8.8, and this plugin depends on Play 2.8.0, your project's dependency will resolve to 2.8.8. But, if your project uses Play 2.8.2, and this plugin depends on 2.8.7, your project's dependency will be upgraded to 2.8.7, which is not good.


*: cleanup go.mod and Makefile

What problem does this PR solve?

What is changed and how it works?

cleanup go.mod and Makefile
update golangci-lint and fix some issues of lint

Check List

Tests

Manual test (add detailed scripts or steps below)
No code

Release note

Codecov Report

Merging #2519 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2519      +/-   ##
==========================================
- Coverage   77.10%   77.05%   -0.05%
==========================================
  Files         204      204
  Lines       22022    22044      +22
==========================================
+ Hits        16979    16985       +6
- Misses       3752     3775      +23
+ Partials     1291     1284       -7

Impacted Files
Coverage Δ

server/api/operator.go
45.40% <ø> (ø)

server/schedulers/shuffle_hot_region.go
63.47% <0.00%> (-11.31%)
:arrow_down:

server/schedulers/random_merge.go
61.19% <0.00%> (-2.99%)
:arrow_down:

server/kv/etcd_kv.go
75.32% <0.00%> (-2.60%)
:arrow_down:

server/schedule/operator_controller.go
78.50% <0.00%> (-2.34%)
:arrow_down:

server/member/leader.go
72.37% <0.00%> (-1.17%)
:arrow_down:

server/grpc_service.go
59.18% <0.00%> (-0.97%)
:arrow_down:

server/server.go
77.53% <0.00%> (-0.32%)
:arrow_down:

server/cluster/cluster.go
80.06% <0.00%> (-0.09%)
:arrow_down:

server/schedule/metrics.go
100.00% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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

According to the cmd of staticcheck, we can see that stylecheck is also used. After adding stylecheck to the golangci-lint configuration file, staticcheck can be removed safely.

/merge

/merge

/run-cherry-picker


Docs: Quickstart Guide on Getting Started with Novu Ruby

We currently have quickstart guides in different languages.
We need a Ruby Quickstart. There's a template to follow below:
Get Started with PHP

@amansaini0003 Is this something you will like to work on? 👀  Opening it up to the community but wanted to see if it's something you'll want first dibs on 😄

@unicodeveloper can i take this one?

Yes please, you can. Assigning this issue to you now @Eazybright

Please let me know if you need any help. This is how to get the docs up and running locally.

Clone the Novu repo, https://github.com/novuhq/novu
cd into docs
Run npm install
Run npm run start

Alright.

@unicodeveloper can you please help with fixing this lint errors? I'm trying to make a commit to make a PR

I am seeing “unclosed string” in the get started with Ruby file. Can you
check the markdown file to be sure something isn’t off there?
On Thu, Jul 6, 2023 at 11:40 PM Kolawole Ezekiel @.***>
wrote:

[image: Screenshot 2023-07-06 at 11 39 07 PM]
https://user-images.githubusercontent.com/30163347/251589991-1513b4d7-fe9c-40b5-8f59-f9a995a3a4fe.png
@unicodeveloper https://github.com/unicodeveloper can you please help
with fixing this lint errors? I'm trying to make a commit to make a PR
—
Reply to this email directly, view it on GitHub
https://github.com/novuhq/novu-ruby/issues/27#issuecomment-1624397068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWPNUN76INPCUYQQ4EQLYTXO45FNANCNFSM6AAAAAAZ42QRYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best Regards,
Prosper Otemuyiwa
Co-founder, Eden
@unicodeveloper https://twitter.com/unicodeveloper | prosper.otemuyiwa1
( Skype )

I've checked again, there's no open string

Before you added the ruby quickstart, did you encounter any error while running the docs locally?

no

One way to know where the error is coming from is to delete everything you have in the getting started ruby file and start adding them back paragraph by paragraph.
Run the docs for each paragraph you add to know where the error is coming from.
Another question for you: Does it give error when you run it locally with the getting started ruby file or does the lint error only happen when you want to commit?

Okay i will try to add them paragraph by paragraph.
i saw an error on the console

Module not found. So for some reasons it can’t find that file, you need to
check how you added that file again and run it again.
On Fri, Jul 7, 2023 at 12:08 AM Kolawole Ezekiel @.***>
wrote:

Okay i will try to add them paragraph by paragraph.
i saw an error on the console
[image: Screenshot 2023-07-07 at 12 07 07 AM]
https://user-images.githubusercontent.com/30163347/251594346-5b01e0b0-00fd-4697-84c3-e3a02ae55749.png
—
Reply to this email directly, view it on GitHub
https://github.com/novuhq/novu-ruby/issues/27#issuecomment-1624416507,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWPNUIYOZBTG7PMRHE4OG3XO5AOPANCNFSM6AAAAAAZ42QRYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best Regards,
Prosper Otemuyiwa
Co-founder, Eden
@unicodeveloper https://twitter.com/unicodeveloper | prosper.otemuyiwa1
( Skype )

Ops! Is there a specific way to add the file?
I just created the file casually.

Check the other QuickStart files to be sure it follows the pattern they
follow.
On Fri, Jul 7, 2023 at 12:17 AM Kolawole Ezekiel @.***>
wrote:

Ops! Is there a specific way to add the file?
I just created the file casually.
—
Reply to this email directly, view it on GitHub
https://github.com/novuhq/novu-ruby/issues/27#issuecomment-1624422552,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWPNUOR7ZQP2TOTNYFGUADXO5BRVANCNFSM6AAAAAAZ42QRYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best Regards,
Prosper Otemuyiwa
Co-founder, Eden
@unicodeveloper https://twitter.com/unicodeveloper | prosper.otemuyiwa1
( Skype )

Issue resolved.
It was a linting + vscode problem.

That’s great news
On Fri, Jul 7, 2023 at 12:33 AM Kolawole Ezekiel @.***>
wrote:

Issue resolved.
It was a linting + vscode problem.
—
Reply to this email directly, view it on GitHub
https://github.com/novuhq/novu-ruby/issues/27#issuecomment-1624432634,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWPNULDS5AKPJU2I5BDP2DXO5DLTANCNFSM6AAAAAAZ42QRYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best Regards,
Prosper Otemuyiwa
Co-founder, Eden
@unicodeveloper https://twitter.com/unicodeveloper | prosper.otemuyiwa1
( Skype )

PR raised: https://github.com/novuhq/novu/pull/3738

Thanks @Eazybright . Will check it out today

@Eazybright Please one more thing. Can you resubmit the PR against the main branch?

done
https://github.com/novuhq/novu/pull/3739

Dropped a comment on the PR @Eazybright

@unicodeveloper new PR raised.
https://github.com/novuhq/novu/pull/3742

Hey @Eazybright there's a part that needs to be checked again the quickstart guide you wrote.
This part:

In PHP,  the metadata has to be an array. In Ruby, what will be the equivalent?

It should be object of metadata.

I guessed as much. Please can you submit a PR to correct it? 🙏
On Sun, Jul 9, 2023 at 7:30 PM Kolawole Ezekiel @.***>
wrote:

It should be object of metadata.
—
Reply to this email directly, view it on GitHub
https://github.com/novuhq/novu-ruby/issues/27#issuecomment-1627790671,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWPNUPK2OH2MFJSN6JQ5BTXPL2DPANCNFSM6AAAAAAZ42QRYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best Regards,
Prosper Otemuyiwa
Co-founder, Eden
@unicodeveloper https://twitter.com/unicodeveloper | prosper.otemuyiwa1
( Skype )

PR submitted. https://github.com/novuhq/novu/pull/3751

Issue resolved.
It was a linting + vscode problem.

Please how did you resolve this issue? I just got someone else experiencing the same issue.

add "--no-verify" argument to the git commit command.
On Mon, Jul 10, 2023 at 9:39 PM Prosper Otemuyiwa @.***>
wrote:

Issue resolved.
It was a linting + vscode problem.
Please how did you resolve this issue? I just got someone else
experiencing the same issue.
—
Reply to this email directly, view it on GitHub
https://github.com/novuhq/novu-ruby/issues/27#issuecomment-1629698385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHGEDE7BRNGI5F7X4OBU6FDXPRSBFANCNFSM6AAAAAAZ42QRYA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Failed to generate select script for the selected object.

Issue Type: Bug
Right click on Azure data Studio. Right click on Table script to slelect top 1000 rows and it throws error " "Failed to generate select script for the selected object.""
Azure Data Studio version: azuredatastudio 1.43.0 (b790d700898b1095d83e62f0de14678a58222520, 2023-04-10T23:14:27.236Z)
OS version: Windows_NT x64 10.0.19045
Restricted Mode: No
Preview Features: Enabled

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.73GB (14.70GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

agent
Mic
0.49.0

import
Mic
1.5.4

kusto
Mic
0.5.8

profiler
Mic
0.12.2

schema-compare
Mic
1.18.0

azdata-sanddance
msr
4.0.3

Hi @tanmoycuat
Can you capture 'Verbose' logs (MSSQL) when this error occurs and upload them here for investigation?

If it helps others: in my case I fixed it by adding my external IP address to whitelist.

ERR Scripting failed. error: An error occurred while scripting the objects. Failed to connect to server synw-xxx-xxxdwh-dev-ondemand.sql.azuresynapse.net.

@SaschaProdware This seems like an issue you're facing where server connection could not be made. With support of connection pooling (enabled by default), this should not occur now. I will close this issue, and if it occurs again, let us know.


How to dynamically change Authentication mode

Hi Team,
We have a requirement where we want to run our httpYac http files with OAurh2.0 client credentials flow.
For local testing we want to test the APIs using Basic Authentication mode.  Is there a way to switch the authentication mode dynamically.
Also how can we access environment variables in scripts
Regards,
Vaibhav

Also how can we access environment variables in scripts

all variables (env + generated at runtime) are used the same way. just use the variableName (example)

For local testing we want to test the APIs using Basic Authentication mode. Is there a way to switch the authentication mode dynamically.

Some ideas:

use a variable in your env file which defines the correct Authorziation Header. Variables are replaced before detecting which Authorization Mode is used.

// prod.env
@auth=oauth2 client
// dev.env
@auth=oauth2 basic

GET https://httpbin.org/anything
Authorization: {{auth2}}

you could create a custom plugin and switch variables in this plugin and automatically add correct Authorization Header


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1634

Questions ?
Please refer to the Backport tool documentation


Fix release push race condition

Currently the docker image build triggers when a new github tag is added, but docker pulls the pypi packages so if the tag gets applied before pypi is pushed, then the docker image will actually contain the previous release.  This is easily worked around by just pushing to pypi first, but it would be nice to not have to worry about this race condition happening.
I think the basic options are either to force docker to use the tagged version or we could also just automate the process similar to what libcloudforensics does (https://github.com/google/cloud-forensics-utils/blob/master/.github/workflows/pypi_push.yml).   One thing to keep in mind if we go down the route of making docker used the tagged version is that we currently also have other builds that aren't triggered by a tag being added (e.g. -test which builds on new pushes to the master branch, or -release-test which builds on new pushes to the release branch).

Or we build the docker images from the github branch instead of the pypi packages.


Add a disclaimer with unblocking checkbox if one of AG ministries umbrella is chosen.

Description:
Add a disclaimer with unblocking checkbox if one of AG ministries umbrella is chosen.

Now if you choose (both in Public or Private Cloud) one of AG ministries (Attorney General, Public Safety and Solicitor General, Ministry of Housing, Emergency Management) the blocking checkbox shows up. It blocks Submit button until checked.
If the checkbox was marked in the Create Request, the Edit Request would have it checked.
If the user changes the ministry to one of these 4 in Edit Request from any other the checkbox would appear and block Submit button until checked.


Remove reg grad filtering to see performance diff

Proposed changes:

Check the effect of reverting https://github.com/RasaHQ/rasa/pull/5669

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tczekajlo:x: DakshDaksh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Ability to show single provider on map

should look somewhat like this https://211ontario.ca/23802-0_toronto-west-seventh-day-adventist-church-food-bank-food-bank/

Permalink should have a map, user should be able to click on map icon, popup contains to permalink.


Patch com.amazon.aws.ec2/instance_identity_document/jsonschema/1-0-0

Amazon has rolled out longer IDs for all of their services which means that the imageId is no longer a valid length and needs to be bumped from 12 to 21:

https://github.com/snowplow/iglu-central/blob/master/schemas/com.amazon.aws.ec2/instance_identity_document/jsonschema/1-0-0#L52-L55

Error message from Kibana:

{
"level": "error",
"message": "error: string "ami-xxx" is too long (length: 21, maximum allowed: 12)\n    level: "error"\n    schema: {"loadingURI":"#","pointer":"/properties/imageId"}\n    instance: {"pointer":"/imageId"}\n    domain: "validation"\n    keyword: "maxLength"\n    value: "ami-xxx"\n    found: 21\n    maxLength: 12\n"
}

cc/ @chuwy

Scheduling.

No, that was just an oversight. Fixing it. Thanks.


how do I remove "loyal" item drop?

please tell me the command :)

Since 1.0.1 you can use this command:
/kill @e[type=item, tag=protected_from_despawn]

If you used Loyal Items 1.0.0 previously in your world, you should use this instead:
/kill @e[type=item, nbt={Age:-32768}]

Keep in mind that this command filters items by age, which hypothetically may remove custom items from other mods or datapacks if they use the same protection metod as in Loyal Items.