qt3: remove

Not used by any other package, and has vulnerabilities.
Close #99841 , Close #96827, Close #90955.

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Not used by any other package, and has vulnerabilities.

anonymous function at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-2/pkgs/tools/graphics/lprof/default.nix:1:1 called without required argument 'qt3', at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-2/lib/customisation.nix:69:16

Not used by any other package, and has vulnerabilities.

anonymous function at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-2/pkgs/tools/graphics/lprof/default.nix:1:1 called without required argument 'qt3', at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/ofborg-evaluator-2/lib/customisation.nix:69:16

Thanks. Removed lprof as well, it was broken since a while now.

But I see now that taskjuggler also needs qt3... Not sure if to remove it as well, there's a newer version of taskjuggler that doesn't need qt3.

But I see now that taskjuggler also needs qt3... Not sure if to remove it as well, there's a newer version of taskjuggler that doesn't need qt3.

I take my words back. The nix files of taskjuggler 2 were not used at all and they only showed up in git grep but had no usage from all-packages.nix.


Uploading multiple tracks with same flavor when event is created does not work anymore

Describe the bug
We upload video assist files that consist of several parts when creating an event. We then concatenate them using our workflow.
This is not working anymore. The configuration multiple=true available in etc/listproviders/event.upload.asset.options.properties has no effect.
To Reproduce
Steps to reproduce the behavior:

In etc/listproviders/event.upload.asset.options.properties, add a source track with multiple=true e.g. EVENTS.EVENTS.NEW.SOURCE.UPLOAD.MULTIPLE_PARTS={"id": "track_parts","type":"track", "flavorType": "presenter","flavorSubType": "source", "multiple":true, "displayOrder":11, "accept": ".avi,.flv,.m4v,.mkv,.mov,.mp4,.mpeg,.mpg,.ogv,.webm,.wmv,.flac,.m4a,.mp3,.ogg,.wav,.wma"}
Select multiple files when uploading presenter
Only the last track is added to the media package.

Environment Information

Opencast 11

@rute-santos this is fixed right?

Yes, the fix has already been merged.


Authenticate with transmitter every time

Seems to fix #55; with this change I can consistently get readings from the transmitter with passiveMode set to false.
Still some interesting issues:

the first time the transmitter connects it seems to timeout in auth somewhere
every session with the transmitter the final disconnect tx message seems to be timing out
every session with the transmitter I see [CoreBluetooth] WARNING: Unknown error: 913 in the console

I also wonder if auth-ing every time with the transmitter could reduce transmitter battery life. So use at your own risk!

I've been authenticating each time for the life of my current transmitter, and I'm currently on day  103. We'll see if it makes it 5 more days, but so far it would seem battery life is not reduced in any significant way.

Awesome, I was worried I'd have to argue with my insurance company when my transmitter died after 45 days haha.


You can open a drawer 2 times

When clicking fast enough the drawer will open multiple times which in turn breaks the drawer.

Disable clicking of the element while a drawer is opening or open


Problem copying / rewriting objects via Storage API.

Struggled a bit trying to copy/rename an object with the existing elixir API.
 GoogleApi.Storage.V1.Api.Objects.storage_objects_rewrite(conn, src_bkt, src_obj, dest_bucket, dest_obj)
 GoogleApi.Storage.V1.Api.Objects.storage_objects_copy(conn, src_bkt, src_obj, dest_bucket, dest_obj)

Calling them as shown above always resulted in the following error:
{
  "error": {
    "code": 400,
    "message": "Unsupported content with type: application/octet-stream",
    "errors": [
      {
        "message": "Unsupported content with type: application/octet-stream",
        "domain": "global",
        "reason": "badContent"
      }
    ]
  }
}

I was able to work around by issuing a raw Tesla call:
    Tesla.post(
      "https://storage.googleapis.com/storage/v1/b/#{bucket}/o/#{URI.encode_www_form(old_key)}/rewriteTo/b/#{
        bucket
      }/o/#{URI.encode_www_form(new_key)}",
      "",
      headers: [
        {"authorization", "Bearer #{token}"},
        {"content-type", "application/json; charset=UTF-8"}
      ]
    )

The only difference between the manual call - and the library call is the inclusion of the content-type header in my own request.
Anyone else experience this? Am I misssing something?
Think because the body is empty, Tesla cannot infer content type - so it has to be manually included...

Have not been able to reproduce this. It's possible a change to Tesla (I am using 1.4.0), or a change to the backend behavior, has fixed this in the meantime. Are you still observing this issue?

It doesn't work for me either. It happens when I'm coping jpg.
google_api_storage v0.29.0
tesla 1.4.2
Another issue related to copy: https://github.com/googleapis/elixir-google-api/issues/8009

I'm also getting this when configuring with:
config :tesla, adapter: Tesla.Adapter.Hackney

Works fine with the default tesla adapter.


Fuzz new text parser

The old text parser was fuzzed which knocked out a bug or two, we should do similarly with the new one once #2852 is resolved.

Closed in #2915


force:org:create ignores apiVersion config value when deploying settings

Summary
force:org:create ignores apiVersion config value so it always default to the max api version supported by the org for the settings deployment.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc

Set apiVersion: sfdx config:set apiVersion=47.0 --global
run  DEBUG=sf:deploySettingsViaFolder sfdx force:org:create -s -f config/project-scratch-def.json -a dreamhouse
See output:

WARNING: apiVersion configuration overridden at "47.0"
  sf:deploySettingsViaFolder DEBUG deploying to apiVersion: 56.0 +0ms

Expected result
Respect apiVersion value
Actual result
The code always gets undefined so it defaults to the max api supported by the org.
System Information
sfdx version --verbose --json
{
  "cliVersion": "sfdx-cli/7.169.1",
  "architecture": "darwin-x64",
  "nodeVersion": "node-v16.16.0",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 1.3.0 (core)",
    "@oclif/plugin-commands 2.2.0 (core)",
    "@oclif/plugin-help 5.1.12 (core)",
    "@oclif/plugin-not-found 2.3.1 (core)",
    "@oclif/plugin-plugins 2.1.0 (core)",
    "@oclif/plugin-update 3.0.0 (core)",
    "@oclif/plugin-version 1.1.2 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.4 (core)",
    "@oclif/plugin-which 2.1.0 (core)",
    "alias 2.1.0 (core)",
    "apex 1.2.0 (core)",
    "auth 2.2.5 (core)",
    "community 2.0.1 (core)",
    "config 1.4.19 (core)",
    "custom-metadata 2.0.0 (core)",
    "data 2.1.2 (core)",
    "generator 2.0.2 (core)",
    "info 2.1.0 (core)",
    "limits 2.0.1 (core)",
    "org 2.2.3 (core)",
    "packaging 1.9.1 (core)",
    "schema 2.1.3 (core)",
    "signups 1.2.0 (core)",
    "source 2.0.13 (core)",
    "telemetry 2.0.0 (core)",
    "templates 55.1.0 (core)",
    "trust 2.0.4 (core)",
    "user 2.1.2 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "salesforce-alm 54.8.1 (core)"
  ],
  "osVersion": "Darwin 20.6.0",
  "shell": "zsh",
  "rootPath": "/Users/cdominguez/.nvm/versions/node/v16.16.0/lib/node_modules/sfdx-cli"
}

Hi,
I am also facing this issue while creating scratch orgs. I have made changes in sfdx-project.json but it was of no use.
error running force:org:create: a scratch org was created with username<EMAIL_ADDRESS>but the settings failed to deploy due to: not available for deploy for this api version
Can you please help?

@sharad272 you can try using the force:org:legacy:create which should respect the apiVersion config. We might have this fixed for the current force:org:create command in the RC next week.

force:org:legacy:creat

@cristiand391  Thanks! This is working for now.

Fixed in CLI version 7.171.0


New saturation and contrast configs

This adds new Range configs to saturation and contrast like the brightness config i added in #96
The default value is the same and it converts the old config to the new values.
I tested it multiple times and everything works.
The min and max values are about the same as previously, a bit lower and higher to the point where they still look good.

I do miss the original brightness control setting as its easier to change. But I guess if we can resolve the 'too dark & too bright' areas. I guess would resolve that issue.

I do miss the original brightness control setting as its easier to change. But I guess if we can resolve the 'too dark & too bright' areas. I guess would resolve that issue.

Right, I kinda just want a few options. instead of spending time tweaking all these numbers we are adding. I have a feeling if we keep adding it will have too many options and configs lol. I do know somebody was working on defaults for site locations, so you'd probably just need to configure these settings in there so you can have consistency in places instead of always constantly tweaking these numbers.

I think a better option for this kind of 'fine' tuning would have the original default set that 117 made, and have a little (edit) button beside each config to allow different configurations. But also having the original drop down for easy access.

For someone who is looking for a vanilla+ experience, the default settings pushed with the plugin make the game look a little over saturated with too much contrast so more options to lower it would be welcomed.

I kinda just want a few options. instead of spending time tweaking all these numbers we are adding. I have a feeling if we keep adding it will have too many options and configs lol.

The plugin already allows users different scaling options for how they want the game to look - someone uninterested or overwhelmed by changing from the default settings will already have the problem of seeing too many options and configs. If the plan is to make the options easier to users, then I would go with presets, as someone suggested in the Discord. Otherwise, brightness and contrast sliders are already present in most modern game's graphics settings, so it isn't out of place to give the user a similar experience here.

I do know somebody was working on defaults for site locations, so you'd probably just need to configure these settings in there so you can have consistency in places instead of always constantly tweaking these numbers.

I see the brightness, saturation and contrast setting being the default settings that work alongside specific site location settings, not replacing it. Set the base contrast for you client and then each location modifies the lighting and brightness depending on their individual settings and whether Atmospheric Light is enabled.
Brightness, contrast and saturation are all important settings for accessibility; their inputs being a range like Draw Distance is a good change imo.

@bebeli555 If you rebase this I'd be glad to review it. Sorry it was ignored initially that was before my time here.


WavefrontTracer doesn't correctly implement opentracing.Tracer API (issue with tags)

Looks like WavefrontTracer (v 2.1.0) doesn't follow the opentracing.Tracer API (version >= 2.0).
In particular: opentracing.Tracer requires the tags parameter of the methods start_span and start_active_span to be a dict
    def start_active_span(self,
                          operation_name,
                          child_of=None,
                          references=None,
                          tags=None,
                          start_time=None,
                          ignore_active_span=False,
                          finish_on_close=True):
        """Returns a newly started and activated :class:`Scope`.

        :param tags: an optional dictionary of :class:`Span` tags. The caller
            gives up ownership of that dictionary, because the :class:`Tracer`
            may use it as-is to avoid extra data copying.
        :type tags: dict
        """
         ....

    def start_span(self,
                   operation_name=None,
                   child_of=None,
                   references=None,
                   tags=None,
                   start_time=None,
                   ignore_active_span=False):
        """Starts and returns a new :class:`Span` representing a unit of work.

        :param tags: an optional dictionary of :class:`Span` tags. The caller
            gives up ownership of that dictionary, because the :class:`Tracer`
            may use it as-is to avoid extra data copying.
        :type tags: dict
        """
         ....

While  wavefront_opentracing_sdk.WaveFrontTracer accepts a list of pairs
    def start_span(self, operation_name=None, child_of=None, references=None,
                   tags=None, start_time=None, ignore_active_span=False):
        r"""
        Start and return a new :class:`Span` representing a unit of work.

        :param tags: an optional list of tags.
        :type tags: list of pair
        """
        parents = []
        follows = []
        baggage = {}
        tags = tags or []
        ...

@kulinskyvs the reason our WavefrontTracer is using the list here is that we want to support multi-value tags.

@kulinskyvs the reason our WavefrontTracer is using the list here is that we want to support multi-value tags.

@haosong , wouldn't it be better to accept the dictionary for tags and introspect the type of dictionary values in this case (detect iterables to support multi-value tags) ?
I mean something like:

def start_span(self, operation_name=None, child_of=None, references=None,
                   tags=None, start_time=None, ignore_active_span=False):
        r"""
        Start and return a new :class:`Span` representing a unit of work.

        :param tags: an optional list of tags.
        :type tags: list of pair
        """
        parents = []
        follows = []
        baggage = {}
       for key, value in tags.items():
         if isinstance(e, Iterable):
            # do the magic with multi values per one key
         else:
            self.set_tag(.....)

This is really strange to see WavefrontTracer implementing opentracing.Tracer and breaking te API contract.

@haosong , wouldn't it be better to accept the dictionary for tags and introspect the type of dictionary values in this case (detect iterables to support multi-value tags) ?
I mean something like:

def start_span(self, operation_name=None, child_of=None, references=None,
                   tags=None, start_time=None, ignore_active_span=False):
        r"""
        Start and return a new :class:`Span` representing a unit of work.

        :param tags: an optional list of tags.
        :type tags: list of pair
        """
        parents = []
        follows = []
        baggage = {}
       for key, value in tags.items():
         if isinstance(e, Iterable):
            # do the magic with multi values per one key
         else:
            self.set_tag(.....)

This is really strange to see WavefrontTracer implementing opentracing.Tracer and breaking te API contract.

@kulinskyvs thanks for the suggestion. Feel free to submit a PR and we will review your change accordingly.

@kulinskyvs thanks for the suggestion. Feel free to submit a PR and we will review your change accordingly.

merged, and relesed: https://pypi.org/project/wavefront-opentracing-sdk-python/2.2.2/

merged, and relesed: https://pypi.org/project/wavefront-opentracing-sdk-python/2.2.2/


Large Profit - FP

Attacker -  0xb616aab729a17d325fe221ad7875ae6a9caefc12
AD alert - https://app.forta.network/alerts/0x3f63acb23fc2feaa8a627458e09285634f5e52dbdff13f14a6214d4850e8fd7c
Base bots - Unusual Native Swaps and Large Profit Bot
Potential cause - No profit was made by tx initiator(going by the prices here and here
These are the large profit alerts
https://app.forta.network/alerts/0xe978460656db3f5bf92a2d59a10831f4ae376fde476dff57766827552ea6e3b1
https://app.forta.network/alerts/0x06272b33b5402115b50fc8cec3d0fdd1e2e7203dd67b42b59c9468d013b599bb

SHIDO token was migrated at around that time to the new contract.
I believe the FP happened because a stale price was fetched, which wasn't 0 at the time (otherwise it would have been filtered out), but still low enough to consider that there was a profit in ETH after the swap


Clap 4

I'm working on porting everything to clap 4. I figured I should put up a draft PR, because I can't finish it all at once. Most of it is just annoying but easy work, but there were a few harder cases. Let's hope the tests cover enough to ensure the behaviour stays the same :)
I'm about halfway through this now (doing it alphabetically, now at mkdir).
Note: this will require a bump to MSRV 1.60.
Blocked by: https://github.com/uutils/coreutils/pull/3994

One consideration. I believe that you can make the changes OTHER than the change to the Cargo.toml to change the version of clap from 3.2 to 4.0. If you do that, then you should be able to merge these individual commits in first and then just change all the versions at once.
I haven't verified this, but might be worth trying.

I believe that you can make the changes OTHER than the change to the Cargo.toml to change the version of clap from 3.2 to 4.0

Most of them, yes, but sadly not all of them. Arg::num_args is not defined in 3.2 for example.

uudoc is broken. Reverting to draft until that's fixed

merging now to make sure it doesn't bit rot


Not converging.

Your work is excellent, but I made some modifications to certain parameters, such as total_iters, and proportionally adjusted others like warmup_steps, save_every_iters, and base_learning_rate. However, my training results are not converging. I used the COCO dataset; could this issue be related to my total_iters being too few?

I am a beginner in deep learning, and your answers will be very helpful for my work. I look forward to your response.


Connect-PnPOnline: Could not load file or assembly 'Microsoft.IdentityModel.Tokens, Version=<IP_ADDRESS>

Trying to use PnP.PowerShell 1.11.0 together with Az 8.0.1 module in PowerShell 7 on Windows 10:
Import-Module Az -Version 8.1.0
Import-Module PnP.PowerShell -Version 1.11.0
Connect-PnPOnline -Url https://{tenant}.sharepoint.com

Expected behavior
Successful connect to the target tenant
Actual behavior
The following error is shown:
Connect-PnPOnline: Could not load file or assembly 'Microsoft.IdentityModel.Tokens, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Could not find or load a specific file. (0x80131621)
NOTE: if import PnP.PowerShell with "-UseWindowsPowerShell" param it starts to work.
What is the version of the Cmdlet module you are running?
PnP.PowerShell 1.11.0 / Az 8.0.1
the same behavior is reproduced with
PnP.PowerShell 1.9.0 / Az 7.3.0
Which operating system/environment are you running PnP PowerShell on?

[ x] Windows

Mixing different PowerShell modules in 1 session never works well due to version dependencies. There's not a whole lot we can do about it. Erwin van Hunen has once created an article on how to work around this with scriptblocks. Far from ideal, but one of the few options you have if you need to combine two modules in one PowerShell session. Let me see if I can find it back.

Ok, if you may send link to this page please. Note also that in PowerShell 5.1 the same code works

The construct can be found in this article: https://pnp.github.io/powershell/articles/azurefunctions.html
Read the important information box at the top, samples are available throughout the article.

This is a huge pain since ThreadJobs introduce some limitations such as, you cannot share variables, you cannot do any user user interactions so any command with MFA such as Register-PnPAzureApp or Connect-PnPOnline -Interactive. Say you are writing a script for provisioning related Office 365 and Azure resources using PnP.PowerShell and Az.


Fix compilation errors (x86_64-unknown-linux-musl)

Such as libc::DCCP_SOCKOPT_SERVICE is only available for linux gnu.

x86_64-fuchsia CI check failed, needs #423  to be merged first.

The compilation errors on musl should be fixed when the next version of libc crate is released: https://github.com/rust-lang/libc/pull/3136

See @taiki-e answer.


Uncaught SyntaxError: Unexpected token 'null' after compiling code to js

This tracker is for issues related to dart2js.
Version:
Flutter 3.0.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision fb57da5f94 (5 weeks ago) • 2022-05-19 15:50:29 -0700
Engine • revision caaafc5604
Tools • Dart 2.17.1 • DevTools 2.12.2

Problem
Wrong parsing dart code to js code.
There is unknown reason, that the null.dart file has been parser as: var null = Object.create(dart.library);. The null keyword is reversed for js. Renaming this file to something else allow to run compiled application fine.
Error: Uncaught SyntaxError: Unexpected token 'null' (at header_formatter.dart.lib.js:229:7)
Compiled code in js:
  var byte = Object.create(dart.library);
  var expression_meta_data = Object.create(dart.library);
  var bool_value_builder_widget = Object.create(dart.library);
  var bool = Object.create(dart.library);
  var list_value_actions = Object.create(dart.library);
  var list_value_builder_widget = Object.create(dart.library);
  var list = Object.create(dart.library);
  var null_value_builder_widget = Object.create(dart.library);
  var null = Object.create(dart.library); // <---------- Uncaught SyntaxError: Unexpected token 'null'
  var int_value_builder_widget = Object.create(dart.library);
  var int = Object.create(dart.library);
  var conditional_wrapper_value_builder_widget = Object.create(dart.library);
  var conditional_wrapper = Object.create(dart.library);
  var conditional_value_builder_widget = Object.create(dart.library);
  var conditional = Object.create(dart.library);
  var hex_value_builder_widget = Object.create(dart.library);

Step to reproduce

Clone https://github.com/Solana-Playground-Labs/solana-playground-app
Checkout 6120406 commit.
Run flutter pub get
Start application in Chrome.
(Optional) Rename lib/scene/editor_v2/solana_playground/expression_builder/value/basic_value/null/null.dart to something else to make application work.

Duplicate of https://github.com/dart-lang/sdk/issues/39595.


System.IO.IOException: Too many open files

:ulimit -n 204800
:ulimit -n
204800

Centos 7.2 以上设置好了，但还是会报下面的错误
Centos 7.2 above set up, but still reported the following error
System.IO.IOException: Too many open files
at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at Microsoft.Extensions.FileProviders.Physical.PhysicalFileInfo.CreateReadStream()
at Microsoft.AspNetCore.StaticFiles.StaticFileContext.d__49.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.ResponseCaching.ResponseCachingMiddleware.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.d__6.MoveNext()

These all are the same issue:

https://github.com/aspnet/Mvc/issues/7576
https://github.com/aspnet/Mvc/issues/7623
https://github.com/aspnet/Mvc/issues/7737

Hi @qibucloud. To better assist you we will need to have a repro project as well as details about what is your scenario. What are you trying to do and where you're hitting the failure.

Hi. We're closing this issue as no response or updates have been provided in a timely manner and we have been unable to reproduce it. If you have more details and are encountering this issue please add a new reply and re-open the issue.


Big data dense points (about 7000 points are piled up in a small area) line graph, double image after scrolling zoom

Version
5.1.2
Reproduction link
https://www.makeapie.com/editor.html?c=xdjG0kwpvu&v=1
Steps to reproduce
After opening the link, move the mouse to the data point and zoom in
What is expected?
Zoom in without ghosting
What is actually happening?
Double image after scroll wheel zoom in

Version 4.9.0 does not have this problem, it has been there since 5.0.0


yogakit/yogakit.modulemap' not found React Native

Description
I create a new app using react native. When I try to run the app within an iOS emulator using Xcode I get the following error and the app doesn't run.
fatal error: module map file '/Users/rebekah/Library/Developer/Xcode/DerivedData/example-feduelzeswwgfqdrghxcxxfxavuz/Build/Products/Debug-iphonesimulator/YogaKit/YogaKit.modulemap' not found
I have tried to google this but have been unable to find a way to fix it, is there any way this can be fixed?
React Native version:
System:
OS: macOS 10.15.6
CPU: (4) x64 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz
Memory: 23.01 MB / 4.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 13.7.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.5 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 29
Build Tools: 29.0.2
Android NDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 11.6/11E708 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_45 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found

I have already come across this but it did not fix my problem

Xcode 12， + 1

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

Xcode 12， + 1

Having the same issue. working with .xcworkspace there is no issue on real device, release scheme and archive. This issue only persist on debug run simulators

In Xcode under build settings search for a variable that is called "Excluded Architectures" and add: x86_64, i386 and arm64.
For x86_64, i386 I think the error has to do with the fact that in iOS 14 and MacOs BigSur apps will be supported cross platform so Xcode is trying to build for the other architectures with which the source code is not compatible, and arm64 I think is an older architecture that when building for target iOS 10.0 and newer also fails

Xcode 12， + 1

I had the same issue when I upgraded to Xcode 12. I just deleted podfile.lock  in the ios folder and rebuilt the project with cd ios && pod install && cd .. . This fixed the issue.

I had the same issue when I upgraded to Xcode 12. I just deleted podfile.lock in the ios folder and rebuilt the project with cd ios && pod install && cd ... This fixed the issue.

Xcode 12， + 1

Having the same issue. working with .xcworkspace there is no issue on real device, release scheme and archive. This issue only persist on debug run simulators

Quick update downgrading xcode from 12 to 11.7 did the trick. Seems releated with Xcode for me.

 This might be helpful for your issue

This problem might be related to the fact that Xcode 12 is building universal apps which builds the core for more architectures.
I did not figure out yet how to run any other Schema apart from "Debug". To run Debug in "Build Settings" -> "Excluded Architectures" I've added "arm64", however since "Build Active Architecture Only" is set to "yes" for "Debug" and "no" for all the other schemas when I try to build for any other schemas my build fails with: yogakit/yogakit.modulemap not found React Native.

This problem might be related to the fact that Xcode 12 is building universal apps which builds the core for more architectures.
I did not figure out yet how to run any other Schema apart from "Debug". To run Debug in "Build Settings" -> "Excluded Architectures" I've added "arm64", however since "Build Active Architecture Only" is set to "yes" for "Debug" and "no" for all the other schemas when I try to build for any other schemas my build fails with: yogakit/yogakit.modulemap not found React Native.

Already tried, same results. Build Failed.

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

This was the difference maker for me. Plus downgraded version.

Did anyone solve this? I still cannot run on simulator devices but it works fine on the real one. However, real devices do not show my images as well as icons

I am having the same issue when trying to build for a production release

xcode 12, react-native 0.63.2
Solved issue by change ios target from to 11.0 in Podfile and in General xcode tab
https://stackoverflow.com/a/56183691/5662244

xcode 12, react-native 0.63.2
Solved issue by change ios target to 11.0 in Podfile and in General xcode tab
https://stackoverflow.com/a/56183691/5662244

Nah still not working with me. I tried all of the above solutions and nothing works

I'm currently on Xcode 12.2 beta and there you can just build it out of the box. Had issues too with Xcode 12 from AppStore. If you have a Apple Development Account, I would recommend to download Xcode 12.2 beta until its free for public access, otherwise you should use Xcode 11

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

This works for me 👍

Do check IPHONEOS_DEPLOYMENT_TARGET should be 11.0
This works for me

Neither downgrading Xcode to 11.7 nor upgrading deployment target to 11.0 is a valid solution.
These are just hacks which will likely pop up at some time at a different place.
When I start a new RN (bare) project everything works fine with Xcode 12 and deployment target 10.0 - which is actually suggested in RN diff.
Unfortunately I am stuck here after upgrading RN from 61.5 to 63.3. Any other suggestions are welcomed.

Neither downgrading Xcode to 11.7 nor upgrading deployment target to 11.0 is a valid solution. Same for arm64 exclusion. These are just hacks which will most likely pop up at some time in a different place.
When I start a new RN (bare) project everything works fine with Xcode 12 and deployment target 10.0 - which is actually suggested in RN diff. Unfortunately I am stuck here after upgrading RN from 61.5 to 63.3. Any other suggestions are welcomed.

https://github.com/facebook/react-native/issues/29605#issuecomment-705418622

Do check IPHONEOS_DEPLOYMENT_TARGET should be 11.0
This works for me

Open <Project>/ios/<Project Name>.xcodeproj/project.pbxproj in any IDE and search for IPHONEOS_DEPLOYMENT_TARGET there will be 2 of them and both should be at-least 11.0
In my every project this worked.

but react-native upgrade helper's Podfile
contains [platform :ios, '10.0']

Do check IPHONEOS_DEPLOYMENT_TARGET should be 11.0
This works for me

Open <Project>/ios/<Project Name>.xcodeproj/project.pbxproj in any IDE and search for IPHONEOS_DEPLOYMENT_TARGET there will be 2 of them and both should be at-least 11.0
In my every project this worked.

Most likely it worked for you because you had different versions in your Podfile and your project settings. However, this general issue is not related to iOS 11 as a deployment target. As @kofsiwon mentioned, official docs contain iOS 10 as minimum target.

Let me show you.
delete all the pod files
Leave this alone.
config = use_native_modules!   use_react_native! (: path => config ["reactNativePath"])
pod install again and it will work well.

For projects that use pods ( which it did for me because I'm using RN63 ) I found that I had to set the version of IPHONEOS_DEPLOYMENT_TARGET for all the pods installed in the app, the version had to be consistent with what the version specified in platform :ios and with the version specified in Xcode. Making the version consistent across the whole project solved the issue.
To set IPHONEOS_DEPLOYMENT_TARGET for all the pods you need to add:
  post_install do |installer| 	installer.pods_project.targets.each do |target| 		target.build_configurations.each do |config| 		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0' 		end 	end   end
and then run pod install

None of them work

cd ios
pod deintegrate
pod install

cd ios
pod deintegrate
pod install

You should try to explain does it work or not

cd ios
pod deintegrate
pod install

Still not working

I solved the error by disabling the flipper like this.
use_flipper!
post_install do |installer|
# flipper_post_install(installer)

end
In my case, I don't know about flipper and don't need it

cd ios
pod deintegrate
pod install
No luck for me either

I'm using xcode 12.1 (12A7403) and ios 14.1 simulator, ios deployment target is 9.0 with the legacy build system
I don't remember exactly what I did so let's try around

Pod update & pod repo update
Add this to your Podfile
if target.name.start_with?('Flipper')    target.build_configurations.each do |config|      config.build_settings['VALID_ARCHS'] = 'arm64 arm64e armv7 armv7s x86_64'    end  end
Clean project and run pod install
Rebuild

I had such a statement in my podfile where i've forgotten to remove the last comma, therefore receiving same error. I removed last comma and everything continued smoothly
project 'dadhesab', 'Sibapp.Debug' => :debug, 'Sibapp.Release' => :release,

As of Xcode 12.1, this issue only seen on real device and solved by changing iOS deployment target in Xcode(general tab) to match the pod file (11.0).

I changed the iOS version on the pod file to match with xcode project's. But it's still the same error.

I am also facing the same error can anyone help, please.

I also have a similar error, it works good on Debug build, but fail on Release build.
And finally solved by removing some dependencies related to Flipper for release build setting
My Case

Upgrade react-native from 0.61.5 to 0.63.3
OS target change from 9.0 to 10.0
Update Podfile referenced by react-native 0.63.3 template
Apply Flipper code to Appdelegate.m also referenced by react-native 0.63.3 template
Other setting follow react-native upgrade helper instruction

At first, I found Flipper is built in Release App, which  increase App size by a lot,
then i create another Podfile without Flipper setting for Release.
#NO NEED FOR RELEASE BUILD
#use_flipper!
#post_install do |installer|
#    flipper_post_install(installer)
#end

But No luck with error message
ld: library not found for -lYogaKit
clang: error: linker command failed with exit code 1 (use -v to see invocation)

After some try-and-error i found there are some dependencies installed by Flipper
CoCoaLibEvent
Filpper
Flipper-DoubleConversion
Flipper-Folly
Flipper-Glog
Flipper-PeerTalk
Flipper-RSocket
Flipperkit
OpenSSL-Universal
Yogakit

So i checked Header Search Paths and Other Linker Flags and found there are some possible Flipper dependencies setting on Release Setting
For Header Search Paths
"${PODS_ROOT}/Headers/Public/Flipper"
"${PODS_ROOT}/Headers/Public/Flipper-DoubleConversion"
"${PODS_ROOT}/Headers/Public/Flipper-Folly"
"${PODS_ROOT}/Headers/Public/Flipper-Glog"
"${PODS_ROOT}/Headers/Public/Flipper-PeerTalk"
"${PODS_ROOT}/Headers/Public/Flipper-RSocket"
"${PODS_ROOT}/Headers/Public/FlipperKit"
"${PODS_ROOT}/Headers/Public/OpenSSL-Universal"
"${PODS_ROOT}/Headers/Public/YogaKit"

For Other Linker Flags
"-l\"YogaKit\"",
"-l\"crypto\"",
"-l\"event\"",
"-l\"event_core\"",
"-l\"event_extra\"",
"-l\"event_pthreads\"",
"-l\"ssl\"",

"\"AudioToolbox\"",
"-framework",

By removing them, my release build success and works fine.
Hope this info can help.

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

I've seen a few people mention this.. but I'm not sure what you mean? When I open the xcworkspace project, I'm not able to archive or create a build. Are you using command line to build or the Xcode GUI?
Thanks for your assistance. This is an annoying issue I'm happy to get past!

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

I've seen a few people mention this.. but I'm not sure what you mean? When I open the xcworkspace project, I'm not able to archive or create a build. Are you using command line to build or the Xcode GUI?
Thanks for your assistance. This is an annoying issue I'm happy to get past!

When opening your project using xcode, use the .workspace file in your folder, not the .xcodeproj one. This solved the issue for me.

There are some who think that using a workspace is the solution to the problem. They do not know the cause of the problem in the first place. The project will work well in debug, but when it tries to extract the release, it will not be able to do anything

Tried everything in this thread and nothing worked. When I finally removed Flipper and reinstalled pods the yogakit issue was gone, naturally, but I got the same modulemap not found error for another dependency.
This answer from a CocoaPods issue saved me: https://github.com/CocoaPods/CocoaPods/issues/10059#issuecomment-695876995!

add x86_64 to VALID_ARCHS if need to run app on simulator, e.g., x86_64 arm64 arm64e

The app is now running fine (in Debug mode on a simulator, haven't investigated further yet), even for iOS deployment target 10.0. Don't know if this will help those of you with Release build issues – but hope it will be useful to some!

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

Its working thanks

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

THIS AND

Do check IPHONEOS_DEPLOYMENT_TARGET should be 11.0
This works for me

Open <Project>/ios/<Project Name>.xcodeproj/project.pbxproj in any IDE and search for IPHONEOS_DEPLOYMENT_TARGET there will be 2 of them and both should be at-least 11.0
In my every project this worked.

THIS.
Do those two things in a fresh RN63 project and might help like it did for me

I encounted a similar problem when trying to build app in RELEASE mode, there is no problem when building in DEBUG mode.
The problem can be fixed by changing "iOS deployment target" to 11.0 from 10.0, just as what @softmastx described above.

In your terminal go to :

cd ./ios
Type :  pod deintegratecd
Finally : pod install --repo-update

Good luck !!

I tried to solve this problem during 2 days but nothing helped. I tried to open xxx.xcworkspace instead of xxx. xcodeproj, change target ios version, pod install, pod update... But it hadn't given me any result.
The solution was the following: remove xcode with 12 and higher version from mac and then install xcode 11.5 version: https://developer.apple.com/download/more/
I recommend to try the solutions above first and if nothing helps you can try my solution.

Xcode to 11.7 nor upgrading deployment target to 11.0 is a valid solution. Same for arm64 exclusion. These are just hacks which will most likely p

@pawelsas, did you find a solution?

XCode 9.4.1 running the  xcworkspace file solved my problems .

As of Xcode 12.1, this issue only seen on real device and solved by changing iOS deployment target in Xcode(general tab) to match the pod file (11.0).

make sure to close xCode for some strange reason this worked for me

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

Thanks！

Thanks @whalemare and @holyxiaoxin for your responses.
First I need to change the target in Podfile and xcode General Tab, then I execute pod deintegrate && pod install and finally I need to close the xcode and open again but the .xcodeworkspace not the xcodeproj.

Okay, I just had to open the project in XCode like this:

And not like this

Using the .workspace as says @hongmaoxiao it works

Using the .workspace as says @hongmaoxiao it works

Any solution to this problem ? 😓  I've tried everything and I can't find the solution

Any solution to this problem ? 😓  I've tried everything and I can't find the solution

+1

+1

I have solved this issue by following below instructions

All this changes on both "Build Settings", project and target. And if you want to build for simulator do the inverse path:

Add arm64 to "Excluded Architectures"
Delete arm64 from VALID_ARCHS
Add x86_64 to VALID_ARCHS

Build for "Any iOS Device" (for example, "Archive" because you want to upload to AppStore):

Delete arm64 from "Excluded Architectures"
Delete x86_64 from VALID_ARCHS
Add arm64 to VALID_ARCHS

I have solved this issue by following below instructions

All this changes on both "Build Settings", project and target. And if you want to build for simulator do the inverse path:

Add arm64 to "Excluded Architectures"
Delete arm64 from VALID_ARCHS
Add x86_64 to VALID_ARCHS

Build for "Any iOS Device" (for example, "Archive" because you want to upload to AppStore):

Delete arm64 from "Excluded Architectures"
Delete x86_64 from VALID_ARCHS
Add arm64 to VALID_ARCHS

at Project -> Build Settings -> User-Defined -> VALID_ARCHS add the architecture x86_64 to enable compilation for simulators

at Project -> Build Settings -> User-Defined -> VALID_ARCHS add the architecture x86_64 to enable compilation for simulators

I actually had to re-enable Find implicit dependencies within Edit scheme. I did variety of other things before this as well:

Adding this below Podfile:

post_install do |installer|
	installer.pods_project.targets.each do |target|
		target.build_configurations.each do |config|
		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
		end
	end
  end

Ensuring both pods and project are targeting 11.0.
I right clicked XCode > Get Info + Open with Rosetta (on arm mac)
Excluded archs "arm64" on pods and main project
Build active arch only true on both

I actually had to re-enable Find implicit dependencies within Edit scheme. I did variety of other things before this as well:

Adding this below Podfile:

post_install do |installer|
	installer.pods_project.targets.each do |target|
		target.build_configurations.each do |config|
		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
		end
	end
  end

Ensuring both pods and project are targeting 11.0.
I right clicked XCode > Get Info + Open with Rosetta (on arm mac)
Excluded archs "arm64" on pods and main project
Build active arch only true on both

Hope that solution could help you !
Step 1
on Your terminal go to cd ./ios
Step 2
Delete current Pod  : pod deintegrate
Step 3
Reinstall library pods with update :  pod install --repo-update

Hope that solution could help you !
Step 1
on Your terminal go to cd ./ios
Step 2
Delete current Pod  : pod deintegrate
Step 3
Reinstall library pods with update :  pod install --repo-update

What you have to do is to open workspace (not project) in xcode and wait until indexing of files will end. You should check if your pods has been copied to ~/Library/Developer/Xcode/DerivedData/YourAppName-somelonghash/Build/Products/Debug-iphoneos/. If there are not there, quit xcode, delete whole DerivedData/YourAppName... and open workspace in xcode again. Worked for me.

What you have to do is to open workspace (not project) in xcode and wait until indexing of files will end. You should check if your pods has been copied to ~/Library/Developer/Xcode/DerivedData/YourAppName-somelonghash/Build/Products/Debug-iphoneos/. If there are not there, quit xcode, delete whole DerivedData/YourAppName... and open workspace in xcode again. Worked for me.

After update of XCode to version 12.3 i've encountered this issue.
I tried all of those suggestions for about a day long but finally the solution was (for me) to replace all VALID_ARCHS and VALID_ARCHS[sdk=*] from project.pbxproj from "arm64 arm64e armv7s" to "arm64 arm64e armv7s x86_64".
Hope it helps someone in the future.

After update of XCode to version 12.3 i've encountered this issue.
I tried all of those suggestions for about a day long but finally the solution was (for me) to replace all VALID_ARCHS and VALID_ARCHS[sdk=*] from project.pbxproj from "arm64 arm64e armv7s" to "arm64 arm64e armv7s x86_64".
Hope it helps someone in the future.

I actually had to re-enable Find implicit dependencies within Edit scheme. I did variety of other things before this as well:

Adding this below Podfile:

post_install do |installer|
	installer.pods_project.targets.each do |target|
		target.build_configurations.each do |config|
		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
		end
	end
  end

Ensuring both pods and project are targeting 11.0.
I right clicked XCode > Get Info + Open with Rosetta (on arm mac)
Excluded archs "arm64" on pods and main project
Build active arch only true on both

Helped to fix on Mac Mini M1. If someone with Apple Silicon is facing this issue - try to do that. The most important part is to open Xcode with Rosetta

I actually had to re-enable Find implicit dependencies within Edit scheme. I did variety of other things before this as well:

Adding this below Podfile:

post_install do |installer|
	installer.pods_project.targets.each do |target|
		target.build_configurations.each do |config|
		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
		end
	end
  end

Ensuring both pods and project are targeting 11.0.
I right clicked XCode > Get Info + Open with Rosetta (on arm mac)
Excluded archs "arm64" on pods and main project
Build active arch only true on both

Helped to fix on Mac Mini M1. If someone with Apple Silicon is facing this issue - try to do that. The most important part is to open Xcode with Rosetta

https://developer.apple.com/forums/thread/670006?answerId=659286022#659286022
worked to me

https://developer.apple.com/forums/thread/670006?answerId=659286022#659286022
worked to me

I have the same problem. I tried everything but couldn't figure it out.
My problem is all about getting the archive.
Even when I try to create and archive a project with react-native-init, I get this error.
Help.
macOS version: Big Sur 11.1
Xcode version: 12.4

I have the same problem. I tried everything but couldn't figure it out.
My problem is all about getting the archive.
Even when I try to create and archive a project with react-native-init, I get this error.
Help.
macOS version: Big Sur 11.1
Xcode version: 12.4

@kubilaytural have you tried my suggestion?

@kubilaytural have you tried my suggestion?

@cretumarius
Unfortunately, as you explained, there is no "arm64 arm64e armv7s" in my project.pbxproj file.
I only have

"EXCLUDED_ARCHS [sdk = iphonesimulator *]" = arm64;
"EXCLUDED_ARCHS [sdk = iphonesimulator14.4]" = arm64;
there are these.

What is your suggestion?

@cretumarius
Unfortunately, as you explained, there is no "arm64 arm64e armv7s" in my project.pbxproj file.
I only have

"EXCLUDED_ARCHS [sdk = iphonesimulator *]" = arm64;
"EXCLUDED_ARCHS [sdk = iphonesimulator14.4]" = arm64;
there are these.

What is your suggestion?

There are no VALID_ARCHS finds in project.pbxproj?

There are no VALID_ARCHS finds in project.pbxproj?

@cretumarius Unfortunately

@cretumarius Unfortunately

Oh, I see 😔. Maybe you can try to add those configs from XCode?

Oh, I see 😔. Maybe you can try to add those configs from XCode?

@cretumarius I did what you said.
Then

deleted the derived data.
reinstall pods.
clean build project
and I did archive.

However, the situation is still the same.

@cretumarius I did what you said.
Then

deleted the derived data.
reinstall pods.
clean build project
and I did archive.

However, the situation is still the same.

Add x86_64 for Release too. The Archive will run in Release scheme.

Add x86_64 for Release too. The Archive will run in Release scheme.

@cretumarius I tried but it didn't work.

@cretumarius I tried but it didn't work.

The recommended solution worked for me in an old react native project. I've created now a new react native project with rn 0.63.4 as you, using
npx react-native init <project_name> --template react-native-template-typescript.

This is now generated for User-Defined. I can build with Xcode 12.3 in both schemes and also I can do archive. I don't know what else to recommand 😔😔

The recommended solution worked for me in an old react native project. I've created now a new react native project with rn 0.63.4 as you, using
npx react-native init <project_name> --template react-native-template-typescript.

This is now generated for User-Defined. I can build with Xcode 12.3 in both schemes and also I can do archive. I don't know what else to recommand 😔😔

@cretumarius thx for your help :)

@cretumarius thx for your help :)

I faced the same issue after upgrading to an m1 MacBook pro, adding the following to the pods build setting and project build setting solved it for me.

Make sure the iOS Deployment target in the Podfile and in the Project Settings on Xcode are the same. This caused the issue for me as it ran on Simulator but not when built.

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

thank god, it' works

I faced the same issue after upgrading to an m1 MacBook pro, adding the following to the pods build setting and project build setting solved it for me.

@JoeyAlpha5 you saved me with this. I'd been chasing my tail for hours when I saw your note to update not just my project's build setting but also the Pods build settings.  Forehead-slapper but made all the difference.

Why is this issue closed anyway?

Yes, this is not a closed issue. There is not even a consensus about how to patch this

WHO CLOSED THIS ISSUE?

Nothing in this thread has fixed the issue for me either, unsure why it's closed..

1-close xcode
2-remove derived data
3-pod install
4-open the xcodeworkspace
5-in the build settings search for Excluded Architectures in the target and project
6-add arm64
7-Build and run

Had the same issue and none of the above solutions worked for me.
It works for me by using xcode rosetta. Application Folder -> Right click on Xcode ->  Get Info -> set Open with Rosetta to true
Now open xxx.xcworkspace,  clean build folder and build.
For me it was a successful build and I could use the react-native run-ios command.
Good luck

Hi all,
Is it possible at least to drop a message in the logs about why this f****g file is missing?
It seems to be hundreds of reasons why it may occur, and there is no way to figure out what happened.

This problem might be related to the fact that Xcode 12 is building universal apps which builds the core for more architectures.
I did not figure out yet how to run any other Schema apart from "Debug". To run Debug in "Build Settings" -> "Excluded Architectures" I've added "arm64", however since "Build Active Architecture Only" is set to "yes" for "Debug" and "no" for all the other schemas when I try to build for any other schemas my build fails with: yogakit/yogakit.modulemap not found React Native.

This did fix the missing module map issue but it created another error and I'm now stuck with:
Undefined symbol: __swift_FORCE_LOAD_$_swiftUniformTypeIdentifiers
Undefined symbol: __swift_FORCE_LOAD_$_swiftCoreMIDI

I couldn't find anything useful about this error, anyone else having this issue?

I tried to locate the YogaKit/YogaKit.modulemap file, and it appears that it actually exists, in the Pods/Headers/Public dir.
A Yoga/Yoga.modulemap file can also be found in this dir.
The compiler command which fails is passed the path to the Yoga/Yoga.modulemap in this Pods/Headers/Public dir as a parameter with the -fmodule-map-file option, while it is passed the YogaKit/YogaKit.modulemap file as a parameter with the same option, but in some kind of temporary dir where it cannot be found.
Why are the paths to  YogaKit/YogaKit.modulemap and Yoga/Yoga.modulemap files in the compile command different?

xcode 12, react-native 0.63.2
Solved issue by change ios target to 11.0 in Podfile and in General xcode tab
https://stackoverflow.com/a/56183691/5662244

This fixed it for me, BUT it wasn't as simple as just changing it in those two places. I had to go through the build settings (for the project and the individual targets) and make sure each "iOS deployment target" also matches that version. Unfortunately, changing the overall iOS Deployment Target doesn't trickle down through the rest of the build settings.

Had the same issue and none of the above solutions worked for me. (macbook pro M1)
It works for me by using xcode rosetta. Application Folder -> Right click on Xcode -> Get Info -> set Open with Rosetta to true
Now open xxx.xcworkspace, clean build folder and build.
For me it was a successful build and I could use the react-native run-ios command.
Good luck

This was the only solution that worked for me .Thanks for this !

what worked for me updating to the latest version of flipper: https://fbflipper.com/docs/getting-started/react-native/

I actually had to re-enable Find implicit dependencies within Edit scheme. I did variety of other things before this as well:

Adding this below Podfile:

post_install do |installer|
	installer.pods_project.targets.each do |target|
		target.build_configurations.each do |config|
		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
		end
	end
  end

Ensuring both pods and project are targeting 11.0.
I right clicked XCode > Get Info + Open with Rosetta (on arm mac)
Excluded archs "arm64" on pods and main project
Build active arch only true on both

Helped to fix on Mac Mini M1. If someone with Apple Silicon is facing this issue - try to do that. The most important part is to open Xcode with Rosetta

Helped me, thanx a lot, @Vadko ! Didn't even have to modify Podfile, just running Xcode with Rosetta solved the issue.

Running Xcode in Rosetta patched the issue. But that's not a long term fix.
Does anyone understand what the core issue is and what library needs to be updated?

Running Xcode in Rosetta patched the issue. But that's not a long term fix.
Does anyone understand what the core issue is and what library needs to be updated?

Really and I noted the performance to build got down

I am also having issues with no resolution from any of these suggestions. Really would love to figure this out!

I am also having issues with no resolution from any of these suggestions. Really would love to figure this out!

What version of Xcode are you using?

@hanoisteve Xcode 12.4
I started having issues when I linked rn-vector-icons

I found the solution here it was a version mismatch (pods and targets)

I found the solution here it was a version mismatch (pods and targets)

save my life, tks bro <3

I have solved the issue by following below instructions

All this changes on both "Build Settings", project and target. And if you want to build for simulator do the inverse path:

Add arm64 to "Excluded Architectures"
Delete arm64 from VALID_ARCHS
Add x86_64 to VALID_ARCHS

Build for "Any iOS Device" (for example, "Archive" because you want to upload to AppStore):

Delete arm64 from "Excluded Architectures"
Delete x86_64 from VALID_ARCHS
Add arm64 to VALID_ARCHS

praise the lord - just as I was beginning to give up hope, this comment pulled through. no longer getting the error!

I solved this issue for xcode 12.3 by adding arm64 to Excluded Architectures.

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

This works for me

May be worth mentioning --  as @JoeyAlpha5 said you need to add arm64 to Excluded Architectures in project AND Pods build settings, but here's what got me (seems kinda funny now): I didn't realize that when you run pod install the Pods build settings get reset back to their default values. So I spent about a day going down a rabbit hole when really I could have just double checked the Pods build settings :|

Turns out mine was a version mismatch between podfile and xcode. https://stackoverflow.com/a/66788848/1834127

Just run
cd ios && pod install

May be worth mentioning -- as @JoeyAlpha5 said you need to add arm64 to Excluded Architectures in project AND Pods build settings, but here's what got me (seems kinda funny now): I didn't realize that when you run pod install the Pods build settings get reset back to their default values. So I spent about a day going down a rabbit hole when really I could have just double checked the Pods build settings :|

worked for me!

I faced the same issue after upgrading to an m1 MacBook pro, adding the following to the pods build setting and project build setting solved it for me.

This works for me!. but not just adding arm64 in Pods file you need to replicate the same inside the project file.

"react-native": "0.64.0"
in Info.plist change armv7 to arm64
<key>UIRequiredDeviceCapabilities</key>
<array>
  <string>armv64</string>
</array>

I've opened the project with xed -b ios instead of opening it via xcode and it worked properly

I'm using m1 macbook air.
In my case, these solutions are not working when running the "react native run-ios" command, but after a successful build by pressing the play icon in xcode, the "react native run-ios" command is now successful.

I faced the same issue after upgrading to an m1 MacBook pro, adding the following to the pods build setting and project build setting solved it for me.

This works for me!. but not just adding arm64 in Pods file you need to replicate the same inside the project file.

I am on M1 Macbook pro and this seems my problem and this helped me to resolve the issue, thanks

IF YOU'RE ON M1 CHIP ONLY
after spending hours on different github issues and reading everything, got lucky and managed to find a way to make it work.
what I did:

clone the project in a different folder from scratch (it's important that the folder path is different because xcode caches build details)
set terminal (iterm in my case) to run with rosetta, (I have cocoapods installed with rosetta)
set xcode to run with rosetta
yarn install all packages and pod install all pods from the rosetta terminal
run the project from the rosetta terminal

Described solution will work 100% on Apple silicon and while running Xcode without rosetta.
Please try necessary steps only but if still not work than Please try everything including necessary and unnecessary steps.
1 - Not important(Package.json)
"dependencies": {
 "react": "17.0.1",
 "react-native": "0.64.2"
}

2 - necessary
  use_flipper!()
  post_install do |installer|
    react_native_post_install(installer)
        installer.pods_project.build_configurations.each do |config| config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] =  "arm64"
        end
  end

OR
  use_flipper!()

  post_install do |installer|
    react_native_post_install(installer)
      installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
            config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
          end
      end
  end

3 - Add arm64 under Architectures->Excluded Architectures

Thank you @rf1804  it worked for me!
Solution:
In Xcode, search for IPHONEOS_DEPLOYMENT_TARGET
All of them for your project (and targets) should be at least 11.0

For those coming to this issue trying to get react-native to run on Apple Silicon (M1) hardware, you may be interested in the steps I took to get this to work:
https://github.com/aiba/react-native-m1/blob/main/README.md

TLDR: I removed all references to YogaKit.modulemap from build settings, but left all references to Yoga.modulemap in place.
Okay, I've had this problem since upgrading to .63/.64. This problem seems to have multiple issues, but I've not seen the solution that worked for me (I tried all listed here). However, @feuzeu ranted about the difference between Yoga.modulemap and YogaKit.modulemap, and that got me searching.
Old builds did have a YogaKit folder under the DerivedData/.../Build/Products/ folder. Newer builds did not. A brief search through the build settings revealed that YogaKit was only mentioned in OTHER_SWIFT_FLAGS, whereas Yoga (without the 'Kit') is mentioned in multiple places. So I removed the Yogakit reference and I can now build and run without any issues.
-Xcc -fmodule-map-file="${PODS_CONFIGURATION_BUILD_DIR}/YogaKit/YogaKit.modulemap"

My suspicion is YogaKit was renamed/replaced/migrated/whatever to simply Yoga when upgrading. It seems build settings were upgraded in all places except OTHER_SWIFT_FLAGS.
Hope this helps anyone else having this problem.

This actually help me after upgrade to 0.64.1

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

This was the difference maker for me. Plus downgraded version.

Did you downgrade Xcode, React Native, or something else?

YogaKit/YogaKit.modulemap

Can you give more information? Are you just searching for "YogaKit.modulemap" then commenting out every line that matches? I'm not sure what command takes -Xcc as a flag.

I had this happen when I renamed my project...basically the scheme was still using the old one...I think xcode stores that outside the project so I had to create a new scheme with the same name I renamed to and then it worked. I also used the workspace.
I was able to find the exact error in react native by running the xcodebuild command manually.

Using workspace works for me, however I cannot run the project by running react-native run-ios which is a bit annoying

very simple solution just set in terminal and Xcode and try again...

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

I need to get a build from xcproj facing this issue when Product -> Archhieve

having the same issue on NOT m1 macbook on react native 0.65.
Have anyone fixed it there ?

https://github.com/facebook/react-native/issues/29605#issuecomment-810689920 - This worked for me.

Xcode 12， + 1

Maybe u can open xxx.xcworkspace instead of xxx. xcodeproj

This works. As stated in the docs, if you're using Cocoa pods, .xcworkspace should be used.

xcode 12, react-native 0.63.2
Solved issue by change ios target to 11.0 in Podfile and in General xcode tab
https://stackoverflow.com/a/56183691/5662244

Work for me!


update to  latest OGGM version

Problems that I'm aware of at the moment are:

add cfg.PARAMS['store_model_geometry'] = True to make sure that the run_geometry files are created
rename model_run<...>.nc to model_geometry<...>

update notebooks and make sure the preprocessed directories are used

ts_section doesn't exists anymore
l. 299 in core.py:  for val in np.linspace(df.ts_section.min(), df.ts_section.max(), n):


Fix object flags propagation

Fixes #30942.

@RyanCavanaugh If #30856 is going into 3.4.4 then this should go in too.


Add module fix

Fixes a corner case tested for in https://github.com/runtimeverification/pyk/pull/871 where

we send module M1 with the name "m<hash of M2>" and "name-as-id": true
we send M2

In this case, the server should reject M2, but currently both requests succeed, with M1 being overridden by M2

Code LGTM Does it pass the new tests in pyk? (Maybe we could add 1-2 tests on our own turf for good measure)

Yes, the new tests are passing on this branch. I don't think adding more tests here is very useful, since the rpc testing infrastructure here is somewhat cumbersome. Perhaps I can add some more tests to the booster PR instead.


[incubator/redis-cache] bump redis to 4.0-alpine

What this PR does / why we need it:
bump redis to 4.0-alpine
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @davidkarlsen

/lgtm

/lgtm


Added Romanian lang

Added Romanian language.
I don't have so much experience doing translations but I do a lot of writing in my free time, both En and Ro.
Would definitely like it if someone more experienced will join. Keeping this PR open until then.

Will wait a few days in case someone wants to join.

Will help @RaulTsc with Romanian language.

@nikiciv could you say a little bit about your experience?

@tesseralis I'm a Front End dev, I don't have too much experience with open source, but I am willing to make.Related to translating experience: I write a lot in En & Ro in my free time too, so this should not be a concern.

@RaulTsc Okay seems that we have two maintainers. @RaulTsc say the word and I'll start up your repo for you :)

let's wait a few more days in case someone more experienced wants to join

@RaulTsc it's been a few days, so I'll merge your repo in for now and we can add more people later!

@RaulTsc @nikiciv here's your repo!
https://github.com/reactjs/ro.reactjs.org/issues/1
Please use this issue to track your progress.

thanks @tesseralis
sure, I would really love for more people to join!


Fixed a bug in retrieving the DKIM public key

Description
For some emails, the DKIM public key is not stored TXT record directly in selector._domainkey.domain, but instead points to a CNAME.
For example, when retrieving the DKIM public key for the following domain: protonmail._domainkey.proton.me, we first need to resolve the CNAME for this domain: protonmail.domainkey.drfeyjwh4gwlal4e2rhajsytrp6auv2nhenecpzigu7muak6lw6ya.domains.proton.ch.
However, using the "dns" npm package, the CNAME cannot be resolved.
With this update, all DNS resolutions will be performed using google DNS-over-HTTPS (DoH).
Type of Change
Please delete options that are not relevant.

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have discussed with the team prior to submitting this PR
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] New and existing unit tests pass locally with my changes

However, using the "dns" npm package, the CNAME cannot be resolved.

Are you sure this is the case? I thought the dns package resolve CNAME records as well 🤔
Moving to HTTP DNS can solve another problem though: NextJS users were facing issues around this code due to conflicts in server-side vs frontend rendering. Was thinking of making this change to fix that.
We add a trust assumption on Google DNS HTTPS service when generating proofs (even for server side now), but the verifier is free to validate the "pubkey" by their own means.
@Divide-By-0  what do you think?
@jayden-sudo Btw, we should also remove the import of dns package if we are doing this. And maybe some refactoring since we dont have two cases now (Call let list = await resolveDNSHTTP(name, "TXT"); directly?)

We add a trust assumption on Google DNS HTTPS service when generating proofs (even for server side now), but the verifier is free to validate the "pubkey" by their own means.

This is fine for most cases but not ideal; in the ideal scenario, we default to this Google key, but also try to fetch the key directly via a DNS query if we can -- if that fails, fine we go with google, if it succeeds then we verify that both keys are the same and output a scary warning if they aren't (but still proceed with Google as a default). Basically, we want a user to be able to tell if something is going wrong i.e. Google is censoring that key for whatever reason. IMO, we can add this as a future feature request, and merge this in for now in order to unblock and immediately resolve SSR rendering issues. Do you agree?

Are you sure this is the case? I thought the dns package resolve CNAME records as well 🤔

The dns package can resolve the CNAME in some cases, but the example ‘protonmail._domainkey.proton.me’, which I provided above, can't resolve the CNAME through the dns package. (After my testing, I found that there are many CNAME that can't be resolved by the dns package, and I can't resolve the CNAME by using dig and nslookup in the shell, but I can resolve it by using google public DNS).

We add a trust assumption on Google DNS HTTPS service when generating proofs (even for server side now), but the verifier is free to validate the "pubkey" by their own means.

This is fine for most cases but not ideal; in the ideal scenario, we default to this Google key, but also try to fetch the key directly via a DNS query if we can -- if that fails, fine we go with google, if it succeeds then we verify that both keys are the same and output a scary warning if they aren't (but still proceed with Google as a default). Basically, we want a user to be able to tell if something is going wrong i.e. Google is censoring that key for whatever reason. IMO, we can add this as a future feature request, and merge this in for now in order to unblock and immediately resolve SSR rendering issues. Do you agree?

I think we can use google & cloudflare at the same time to make sure DNS is accurate (both via DNS over HTTPS)

IMO, we can add this as a future feature request

Yes, that make sense. DNS from local ISPs sometimes get attacked (or maybe even prone to censoring) and many people tend to use public DNS like Google/Cloudflare. But its good to have multiple options/fallbacks - maybe even multiple http dns.
We can merge this for now. We can remove dns import (as its not needed until we do the above feature) in this case so it fix NextJS rendering issues as well.

I think we can use google & cloudflare at the same time to make sure DNS is accurate (both via DNS over HTTPS)

Yea 👍 Will add an issue for that.

#212
I just modified the code to use both Google and Cloudflare DoH server. If the DKIM public key data does not match, it will log: console.error("DKIM record mismatch!");.


Server 2022 update history went missing

https://support.microsoft.com/en-gb/topic/windows-server-2022-update-history-e1caa597-00c5-4ab9-9f3e-8212fe80b2ee
Sorry, the page you’re looking for can’t be found.
You may have clicked an old link or the page may have moved.
Please try browsing from our main page .
Request ID: 8af604e8f9c48048

@DSPatrick which article are you referring

Its this page here
https://support.microsoft.com/en-gb/topic/windows-server-2022-update-history-e1caa597-00c5-4ab9-9f3e-8212fe80b2ee

This is a duplicate of part of #6107 and the team are investigating. I will close this as it's a duplicate, information will be updated in #6107. Thank you!
#please-close


Add luis-hsantos.json

My branch is add-luis-fernandes.  Thank you  😊🎉✨

Hello, hacktoberfest reported that my merge was invalid, could you put the "hacktoberfest-accepted" tag on my merge?
Please. just missing this 🤞.


Flags for GPM - go binary, the file to parse and disable -u on go get

Warning: This does break backward compatibility with of specifying the Godep file in $2, but this should be far more flexible in the long run, so I think this is worth it.
There are 3 new options, primarily to make working with GAE much easier.

-f The file to parse. Was required, simply because otherwise $2 could be a flag or the file, made things trickier.
-g What go binary to use. If you are using GAE, you will want to use the goapp command from your local GAE dev install.
-u Be able to manually turn off the -u option on the go get operation. This is just because GAE has libraries in it's GOROOT, and sometimes they conflict. It sucks, but this is a nicer workaround.

Keen to hear feedback, and let me know how I can help test / improve this.  It working for me locally in my project.

While I still think there is merit to the ideas here this pull request is too far removed from the current master for it to be merged.
I'm closing it based on that, but anyone reading can feel free to open an issue with the issues here.
Thanks for the contribution!


Use new Metrics.NET nuget?

Currently https://www.nuget.org/packages/GuaranteedRate.Metric.DatadogPlugin/ depends on https://www.nuget.org/packages/Metrics/ . That implementation seems to be unmaintained, being last updated on 27/12/2014 and the last commit on https://github.com/danielcrenna/metrics-net was almost a year ago.
A more recent, actively maintained port is https://www.nuget.org/packages/Metrics.NET . Perhaps this project should switch to this port.

Hi Mauricio, thanks for the heads up.
Can't give you a timeline for making a switch, but I will investigate it next week.

FYI, I've made a separate library for the newer Metrics.NET
https://github.com/danzel/Metrics.NET.Datadog
It only supports the HTTP API currently.

Cool :+1:
You may need to add UDP/statsd support (perhaps as a sub package or a separate package - to keep dependencies down).
I haven't laid out the code well for adding this, but there isn't too much code, so refactoring it all shouldn't be too tough hopefully :)


Log all PX4 info messages to the PX4Log as well

Describe problem solved by the proposed pull request
We have noticed a lack of information being displayed in the "Logged Messages" console on PX4 Flight Review. It currently only displays WARN level messages.
Test data / coverage
https://review.px4.io/plot_app?log=153160ed-f8a0-4510-954d-4f77b224fa06
Here is a log showing this implemented on a fixed wing vehicle. If you look at the console at the bottom it is now spitting out INFO messages as well.
Describe your preferred solution
I lowered the log level allowed for logging messages in the code.
FYI
@Antiheavy

I'm in favor of logging all these message, but at the same time I want to encourage capturing the relevant data in something structured that could be sent to the ground.
@Kjkinney CI is failing due to code style. http://ci.px4.io:8080/blue/organizations/jenkins/PX4%2FFirmware/detail/PR-12954/1/pipeline

If you install astyle locally you can run make check_format.

Code style fixed.

Merged to master. Thanks @Kjkinney!


process not defined

What version of Remix are you using?
1.3.5
Steps to Reproduce
use process inside a component like below:
function Component() {
    return (
        <div>
            {process.env.DOMAIN === "example.com" ? "Is main domain" : "Not main domain"}
        </div>
    )
}

Expected Behavior
Should be work as it work before
Actual Behavior
Somehow it start throwing process is not defined

What was solution to this? Facing the same issue

@brightpixels process.env only works server-side (it's a Node thing) with the exception of process.env.NODE_ENV which is hardcoded on build, for any other env variable use the loader to read the value and return it.
This is documented here https://remix.run/docs/en/v1/guides/envvars

@sergiodxa I have followed https://remix.run/docs/en/v1/guides/envvars and there are several probelms:

console.log(window) results in ReferenceError: window is not defined in the terminal and browser BUT console.log(global.window) log in the browser console and undefined in the terminal.
When I take this further and try to console.log(global.window.ENV) it results in this error: Cannot read property 'ENV' of undefined both in the terminal and browser.

@sergiodxa I have followed https://remix.run/docs/en/v1/guides/envvars and there are several probelms:

console.log(window) results in ReferenceError: window is not defined in the terminal and browser BUT console.log(global.window) log in the browser console and undefined in the terminal.
When I take this further and try to console.log(global.window.ENV) it results in this error: Cannot read property 'ENV' of undefined both in the terminal and browser. However console.log(global.window?.ENV) works. Is it possible to prevent the rest of the code running till window object has the ENV object?

You should access window only inside useEffects or .client files because window is only available in the browser.

If you need the value of an env variable inside the render of the function return it from the loader access it from there.

I have a app/config.ts file that looks like this:
const CONFIG = {
  MAIN_URL: process.env.MAIN_URL,
};

I am trying to access it inside the config file first. Then components or helper functions are importing this file and access the values.

If you're going to import your config, you need to make sure to add .server to the filename. Otherwise, it'll end up in your client bundle and break, because process only exists on the server.
// config.server.ts
export const CONFIG = {
  MAIN_URL: process.env.MAIN_URL,
} as const

export type Config = typeof CONFIG

declare global {
  interface Window {
    CONFIG: Config
  }
}

// root.tsx
<body>
  <Outlet />
  <ScrollRestoration />
  <script dangerouslySetInnerHTML={{__html: `window.CONFIG=${JSON.stringify(CONFIG);}`}></script>
  <Scripts />
  <LiveReload />
</body>

You can now access your config from window.CONFIG.MAIN_URL

i get this problem when trying to import another package.
for example
import { PaperSDKProvider, LoginWithPaper } from "@paperxyz/react-client-sdk";

this is a package that uses process in its code. and it's breaking when using npm run dev with remix
any ideas on how to workaround this? can be put a process into global vars for the client side?


Unclear position for settings

We've just had some fun time debugging some issues on AWS, so please excuse any sarcasm. ;)
What happened:
We have an AWS host configured via Chef and with a custom JSON file:
    "logrotate": {
        "ourproject": {
            "path": "/var/log/ourproject/*log",
            "missingok": true,
            "dateext": true,
            "dateyesterday": true,
            "rotate": 9999,
            "frequency": "daily",
            "sharedscripts": true
        }
    }

This almost worked, it only occurred us very late that the dateext was completely ignored! Da fuq? As it turned out, dateext (and probably some more parameters) must be specified like this:
    "logrotate": {
        "ourproject": {
            "path": "/var/log/ourproject/*log",
            "options": [
                "missingok",
                "dateext",
                "dateyesterday",
                "sharedscripts"
            ],
            "rotate": 9999,
            "frequency": "daily"
        }
    }

While this structure in and of itself isn't surprising, the ugly part is that e.g. sharedscripts can appear in multiple positions. However, when I have dateext under options, then sharedscripts must appear there, too, which presents another pitfall with confusing error messages.
My wishes:

Provide one and only one True Way to place parameters.
Allow any number of less true ways for backward compatibility. Those should generate warnings when used.
Fail with meaningful errors when some misguided soul uses the wrong parameter. Consider that some users don't actually understand Ruby!
Document the meaning of DIRECTIVES and VALUES (I believe those correspond to settings with and without values). Even without knowing Ruby, I might have figured out earlier what to do then.
The best to you for writing and sharing this code!

Thanks for this detailed bug report.  Apologies that I didn't respond to it earlier.
It appears that while the logrotate_app resource has s deprecation:
https://github.com/stevendanna/logrotate/blob/master/resources/app.rb#L112
I failed to add a similar notification to the use of the same option during "global" configuration.  Overall the "global" config generation has definitely received less attention.


feat: update verifier reference

Description
What this PR does / why we need it:

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #1066
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

@junczhu Thanks for taking this issue up. It's critical for user flexibility.
I'm a little confused on the implementation. Maybe I'm not understanding #1066. My understanding is that we need to introduce a verifier name and a verifier type to the existing VerifierConfig? This way we can support multiple of the same verifier type. I see that in the verifier controller, the Name field in the VerifierConfig has been set to the objectName which I assume is the spec.metadata.name field (this is the unique verifier identifier and different from the verifier type). The Name field in the VerifierConfig is used to determine whether to run a particular verifier or not on an artifact. Almost closer to a verifier type than the individual verifier spec.metadata.name field. Is there a plan to add some sort of verifiertype field and update the verifier invocation logic to use that?
^^ lot of alphabet soup in that explanation :). I'm happy to clarify offline my confusion too. thanks.

@junczhu I have updated the e2e tests required based on k8s bump and gk bump. Please merge main when you have a chance. Thanks


fix(sensors): only set FDC register once on startup

The capacitive sensor on the pipettes worked fine with recent changes, but the gripper sensors would lock up from time to time. We theorized that the issue was that our poller doesn't check the ready flag for the measurements, but I set up a branch to test that and it didn't help at all - one of the sensors still locked up from time to time.
The code for the capacitive sensors originally wrote to the FDC register every time the offset changed. This is necessary on startup (to configure the sample rate and measurement channel), but it is unnecessary after initial startup. Modifying the code so that the FDC register does not get written after initialization fixed the issue - running the code on a gripper and touching the sensors quickly used to cause them to lock up eventually, but now they work indefinitely.
Note: It's likely that this was the original cause of the capsense issues on the pipettes as well, but other "fixes" were able to obfuscate the issue due to the lower range of those sensors.

Sweet! It's still a good idea to add the check for data ready even though it wasn't the cause of this problem.


Connecting database via ssh

Hi!
I'm trying to connect to wocker running container's db via Sequel Pro. SSH is succeeded but connection is refused to connect
How can I connect to running container's db? ports? ip?
I tried:
docker inspect --format='{{.NetworkSettings.IPAddress}}' "truevgd"wich gives me an IP address but I can't connect...
Best: Balint.

Now, you can connect to MySQL from outside the container in version 0.5.0, so GUI tools like Sequel Pro or Workbench are available. Please update Wocker.
Update Wocker
$ vagrant ssh

core@wocker ~ $ wocker update

Note: you can only connect to the container created by v0.5.0 or later.
Information of database
Host: wocker.dev (or <IP_ADDRESS>)
User: wordpress
Password: wordpress
Database: wordpress
Port: 3306
Before v0.5.0, you couldn't connect to MySQL from outside the container, so GUI tools like Sequel Pro or Workbench were not available.


ci: Jaffle shop test action

Further fixes for jaffle shop test action
Checklist

[x] I have run this code in development and it appears to resolve the stated issue.
[x] This PR includes tests, or tests are not required/relevant for this PR.
[ ] I have updated CHANGELOG.md and added information about my change.
[ ] If this PR requires a new PyPI release I have bumped the version number.
[x] I have pulled/merged from the main branch if there are merge conflicts.
[x] I have verified that this PR contains only code changes relevant to this PR.

lgtm


GetAsync fails when specifying a null index.

We have some generic code that runs and trys to specify an index for getbyid but if it can't be found it returns null. This worked in <2.0 of the client I believe this is a bug.
Fails:
var response = await elasticClient.GetAsync<T>(id, s => s.Index(null));

System.ArgumentException

Dispatching Get() from NEST into to Elasticsearch.NET failed
Received a request marked as GET
This endpoint accepts GET
The request might not have enough information provided to make any of these endpoints:
  - /{index=<NULL>}/{type=employee}/{id=56fed5baae14593188842ee5}

   at Nest.LowLevelDispatch.GetDispatchAsync[T](IRequest`1 p) in C:\users\russ\source\elasticsearch-net\src\Nest\_Generated\_LowLevelDispatch.generated.cs:line 932
   at Nest.ElasticClient.<Nest-IHighLevelToLowLevelDispatcher-DispatchAsync>d__24`4.MoveNext() in C:\users\russ\source\elasticsearch-net\src\Nest\ElasticClient.cs:line 75
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Foundatio.Elasticsearch.Repositories.ElasticReadOnlyRepositoryBase`1.<GetByIdAsync>d__15.MoveNext() in C:\Code\Foundatio.Repositories\src\Elasticsearch\Repositories\ElasticReadOnlyRepositoryBase.cs:line 196

Works:
var response = await elasticClient.GetAsync<T>(id);

If you pull down foundatio repositories project and run the tests you'll run into this.

You need to specify an index when getting a document.  This exception is telling you exactly that.  If it worked in 1.x then it was wrong :).

If I pass null to the index that's the same as not specifying one.. They should work the same

I feel pretty strongly that this is a bug in the client

When you don't specify an index, it's being inferred from T.  Passing null explicitly is overriding the inferred index.

I get this but what use case would you ever pass null in here and get a valid query?

And if you'd never get a valid query then, should we throw a argumentnullexception? This difference really threw me off guard. As a lot of tests started failing.

I get this but what use case would you ever pass null in here and get a valid query?

Exactly.  This is why we throw the exception when you pass it null.
I get your point as well, but we try to generalize this logic for all API calls within LowLevelDispatch, so if any required part of the path is missing we throw.  For some calls it's valid to override the inferred index and set it to null (_search for instance).

The stack trace is terrible due to how its executed :(

But
System.ArgumentException

Dispatching Get() from NEST into to Elasticsearch.NET failed
Received a request marked as GET
This endpoint accepts GET
The request might not have enough information provided to make any of these endpoints:
  - /{index=<NULL>}/{type=employee}/{id=56fed5baae14593188842ee5}

Is pretty descriptive :)

Yes, it's much better than what it is but kinda of misleading until your used to all the new stack traces. I was expecting a request to be made and failed so I was looking in fiddler first ready to grab the request json.

Gotcha.  Going to close this.  Please do keep opening issues though as you run into things. :+1:

@niemyjski I stand corrected here :)
Discussed this further with @Mpdreamz  and @forloop and it makes sense for .Index(null) to behave as if it was never called.  This is a general rule the fluent API should follow everywhere.

Closed via #2030


Postgresql plugins fixes

Found some failures: https://hydra.nixos.org/eval/1536115?filter=postgresqlPackages&compare=1536056&full=1#tabs-still-fail

fix extension target dir for some plugins (cc @matthewbauer @ehamberg )
build PG11 plugins on Hydra
mark tds_fdw broken for newer PGs (cc @steve-chavez )
check-meta: teach about ${pname}-${version}, because I've got "name-missing" in:error: Package ‘«name-missing»’ in /home/ubuntu/danylo/nixpkgs/pkgs/servers/sql/postgresql/ext/tds_fdw.nix:23 is marked as broken, refusing to evaluate.

(cc @copumpkin @Synthetica9 @FRidh )

replace some throws with meta.broken. This is debatable, because packages are broken only for specific PG versions, and users don't know about this from new error message. But I still think it is a better option than throw (cc @marsam , related https://github.com/NixOS/nixpkgs/issues/36229)

I've built all with
$ nix-build -E 'with import ./.{}; with lib; flip filterAttrs postgresqlPackages (n: v: !v.meta.broken or false)'
$ nix-build -E 'with import ./.{}; with lib; flip filterAttrs postgresql11Packages (n: v: !v.meta.broken or false)'

@danbst Thanks for the notice. Seems tds_fdw does have some issues for pg >= 11: https://github.com/tds-fdw/tds_fdw/issues/181 and https://github.com/tds-fdw/tds_fdw/issues/205,
So marking it as broken for now is good for me. I'll investigate a fix and submit it in another PR.

@steve-chavez according to https://github.com/tds-fdw/tds_fdw/releases, they have an alpha version compatible with PG11, but I don't know if it is good to replace stable old one with fresh alpha release.


PubSub subscriber closes connection but remains running when messages are not acked/nacked

I have a suscriber which receives messages and uses the data to call an api. I had an issue with my api which left the connection hanging, and as such the subscription never acked/nacked the message. At this point, after a couple of minutes, the subscriber eventually closes its connection and the backlog begins to climb - when I patched the api to resolve the issue, the subscriber didn't process any old or new messages; however, when I restarted the application and create a new subscriber than the entire backlog is processed.
I can solve the issue in my api, and add some timeout logic to my receiver to stop this from occurring in the first place - but I am more interested in figuring out how to fail gracefully in an event like this where the subscriber is hanging. I have some logic in my application which periodically polls the subscriber to check that it is in a running state and restarts (stopAsync() + create a new subscription) if not. I can easily recreate this locally by adding a long delay to my API, and when I do so I notice again that the subscriber stops receiving any messages (I also checked the netstats and saw that there were no open connections to pubsub) - yet it still claims to be in a running state. Ideally my program would be able to identify that its not running and create a new subscriber (perhaps with some backoff), such that if I remove the delay in the api it would be automatically resolved without requiring me to manually restart the application.
Is there some way to detect that the subscriber is hanging? Is that the intended behavior for a subscriber when acks/nacks are delayed?

Michael, can you take a look @pongad ?

@gil-naamani Can you provide any more detail about how long this problem take to happen? The Subscriber will keep extending the message deadline for one hour. At that point it will assume that the message is lost and give up.
There was a bug where the Subscriber didn't release resource properly when giving up, preventing it from pulling more messages. #3633 fixes this.
If the problem occur on the horizon of an hour or more, you might just need to wait a couple days for us to cut a new release.

Version 1.43.0 is released. It should contain the bug fix. I'll close this for the time being, but please let us know if you still run into the problem.


notification plugin not working with cap project with cds =>8.0.0

notification plugin not working with cap project with cds =>8.0.0

In particular build script should be updated:
[2024-09-30 11:47:45]  INFO executing the "npx cds build --production" command... The cds build plugin 'notifications' is not compatible with this @sap/cds-dk version. Update the npm package '@cap-js/notifications/lib/build' to the latest version. [2024-09-30 11:47:46] ERROR the "before-all"" build failed: could not execute the "npx cds build --production" command: exit status 1

I am getting the same error
.[2024-09-30 16:12:04]  INFO executing the "npx cds build --production" command...
.....The cds build plugin 'notifications' is not compatible with this @sap/cds-dk version. Update the npm package '@cap-js/notifications/lib/build' to the latest version.
[2024-09-30 16:12:10] ERROR the "before-all"" build failed: could not execute the "npx cds build --production" command: exit status 1
make: *** [Makefile_20240930161130.mta:28: pre_build] Error 1
[2024-09-30 16:12:10] ERROR could not build the MTA project: could not execute the "make -f Makefile_20240930161130.mta p=cf mtar= strict=true mode=" command: exit status 2
Error: could not build the MTA project: could not execute the "make -f Makefile_20240930161130.mta p=cf mtar= strict=true mode=" command: exit status 2
cds -v output:
@cap-js/asyncapi: 1.0.2
@cap-js/cds-types: 0.6.5
@cap-js/notifications: 0.2.1
@cap-js/openapi: 1.0.5
@cap-js/sqlite: 1.7.3
@sap/cds: 8.2.3
@sap/cds-compiler: 5.2.0
@sap/cds-dk: 8.2.3
@sap/cds-dk (global): 8.0.2
@sap/cds-fiori: 1.2.7
@sap/cds-foss: 5.0.1
@sap/cds-mtxs: 2.1.0
@sap/eslint-plugin-cds: 3.0.5
Node.js: v18.18.0
home: C:\Node\test_import_alert\node_modules@sap\cds
test_import_alert: 1.0.0

Build comman is fixed now however cds w --profile hybrid doesn't and provides the following output:
❗ ERROR on server start: ❗

 TypeError: Cannot read properties of undefined (reading 'Plugin')
    at Object.<anonymous> (/home/user/projects/freshairmanager/node_modules/@cap-js/notifications/lib/build.js:5:67)
`
During plugin initialization with `cds.build` is `undefined`.


Did not linkify text with below format

I was trying to detect & linkify all present &valid links but came across below scenario where link was not detected, it might not be a common use case but having a portal where it automates social media & counts heavily on links, not being able to preview the same creates problems & gives a gateway for bugs.
<a href=www.apple.com did not result in links.
<a href= www.apple.com OR <a href="www.apple.com OR <a href='www.apple.com seems to work fine.
Any help will be appreciated.

Hi @vaishali-shm, are you trying to parse text that contains valid HTML and should be rendered that way? Or does the text happen to look like a bit like HTML? Have you tried linkify-html?

Hi @vaishali-shm, are you trying to parse text that contains valid HTML and should be rendered that way? Or does the text happen to look like a bit like HTML? Have you tried linkify-html?

what happened to linkify-html? Page is 404 and is missing in npmjs

@wobsoriano linkify-html is now back on NPM (due to a publish issue I had to wait 24 hours before re-publishing). Docs are here: https://linkify.js.org/docs/linkify-html.html apologies for the confusion!


[Suggestion] Twitch VOD implementation

Is there any plans to implement TCO so that it could be used for viewing Twitch VODs as well as live streams?

I think your feature request is already covered by #6, and it was previously added to the "TODO" list, so I suppose there are plans to implement this. However, as far as I know, adding a VOD chat functionality is much harder to implement than a livestream chat, since the livestream chat is easily accessible via the following link: https://www.twitch.tv/popout/<streamer_name>/chat, while the VOD chat isn't.


Capture exit code in model status

Signed-off-by: Suresh-Nakkeran<EMAIL_ADDRESS>This PR is to capture container exit code in model status.
Issue #2260

@Suresh-Nakkeran testing with this example by reducing the memory to 500Mi which can reproduce the OOM error.
NAME                                                            READY   STATUS             RESTARTS   AGE
bert-v2-predictor-default-00002-deployment-75bcb4bbf-9gtp7      2/2     Running            0          35m
bert-v2-predictor-default-00003-deployment-7d97bb994c-mvllp     0/2     CrashLoopBackOff   6          10m
bert-v2-transformer-default-00001-deployment-64fd7c6765-bpccb   2/2     Running            0          38m

/lgtm
/approve


Why do dispute fund releases have 0 transaction fee?

What line of code are you referring to specifically?

Apologies: Both MultiSign and CreateMultisigSignature in disputes.go have a '0' as their feeperbyte argument

Oh. I've calculated the fee prior to passing into that function and don't need it to take an additional fee off of it.

Thanks, I should have noticed that!