Build fails on Ubuntu 20.04

Describe the bug
The build fails with errors in several files.
Expected behavior
Should be able to compile with cmake --build build.
Environment:

OS: Ubuntu 20.04
Compiler/IDE: Clang 12.0.1, GCC 9.3.0, Intel oneAPI 2021.3.0
Version: commit 223084c

Additional context
> CC=clang CXX=clang++ cmake ..
-- The C compiler identification is Clang 12.0.1
-- The CXX compiler identification is Clang 12.0.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- ORC third-party: creating target 'stlab::stlab'...
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Warning (dev) at build/_deps/stlab-src/stlab/concurrency/CMakeLists.txt:1 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "stlab" has a relative path.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- stlab: Task System: header
-- ORC third-party: creating target 'tomlplusplus::tomlplusplus'...
-- ORC third-party: creating target 'TBB::tbb'...
CMake Warning (dev) at build/_deps/tbb-src/CMakeLists.txt:95 (option):
  Policy CMP0077 is not set: option() honors normal variables.  Run "cmake
  --help-policy CMP0077" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

  For compatibility with older versions of CMake, option is clearing the
  normal variable 'TBB_TEST'.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- CMAKE_BUILD_TYPE is not specified. Using default: RelWithDebInfo
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Checking for one of the modules 'hwloc'
-- The tbbbind_2_0 target will be configured using the HWLOC 2.1.0
-- Configuring done
-- Generating done
-- Build files have been written to: $HOME/Projects/orc/build
> make
[  0%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/address_waiter.cpp.o
[  1%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/allocator.cpp.o
[  1%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/arena.cpp.o
[  1%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/arena_slot.cpp.o
[  2%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/concurrent_bounded_queue.cpp.o
[  2%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/dynamic_link.cpp.o
[  2%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/exception.cpp.o
[  3%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/governor.cpp.o
[  3%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/global_control.cpp.o
[  3%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/itt_notify.cpp.o
[  3%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/main.cpp.o
[  4%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/market.cpp.o
[  4%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/misc.cpp.o
[  4%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/misc_ex.cpp.o
[  5%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/observer_proxy.cpp.o
[  5%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/parallel_pipeline.cpp.o
[  5%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/private_server.cpp.o
[  5%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/profiling.cpp.o
[  6%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/rml_tbb.cpp.o
[  6%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/rtm_mutex.cpp.o
[  6%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/rtm_rw_mutex.cpp.o
[  7%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/semaphore.cpp.o
[  7%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/small_object_pool.cpp.o
[  7%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/task.cpp.o
[  8%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/task_dispatcher.cpp.o
[  8%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/task_group_context.cpp.o
[  8%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/version.cpp.o
[  8%] Building CXX object _deps/tbb-build/src/tbb/CMakeFiles/tbb.dir/queuing_rw_mutex.cpp.o
[  9%] Linking CXX shared library ../../../../clang_12.0_cxx11_64_relwithdebinfo/libtbb.so
[  9%] Built target tbb
[  9%] Building CXX object CMakeFiles/orc_orc.dir/src/ar.cpp.o
In file included from $HOME/Projects/orc/src/ar.cpp:8:
In file included from $HOME/Projects/orc/include/orc/ar.hpp:13:
$HOME/Projects/orc/include/orc/parse_file.hpp:78:17: error: enumeration value '_S_ios_seekdir_end' not handled in switch [-Werror,-Wswitch]
        switch (dir) {
                ^
$HOME/Projects/orc/include/orc/parse_file.hpp:93:14: error: no member named 'memcpy' in namespace 'std'
        std::memcpy(p, _p, n);
        ~~~~~^
$HOME/Projects/orc/include/orc/parse_file.hpp:211:37: error: no template named 'function' in namespace 'std'
using register_dies_callback = std::function<void(dies)>;
                               ~~~~~^
$HOME/Projects/orc/include/orc/parse_file.hpp:212:31: error: no template named 'function' in namespace 'std'
using do_work_callback = std::function<void(std::function<void()>)>;
                         ~~~~~^
$HOME/Projects/orc/include/orc/parse_file.hpp:212:50: error: no member named 'function' in namespace 'std'
using do_work_callback = std::function<void(std::function<void()>)>;
                                            ~~~~~^
$HOME/Projects/orc/include/orc/parse_file.hpp:212:66: error: expected expression
using do_work_callback = std::function<void(std::function<void()>)>;
                                                                 ^
$HOME/Projects/orc/include/orc/parse_file.hpp:213:30: error: no template named 'function' in namespace 'std'
using empool_callback = std::function<pool_string(std::string_view)>;
                        ~~~~~^
$HOME/Projects/orc/include/orc/parse_file.hpp:216:5: error: unknown type name 'register_dies_callback'
    register_dies_callback _register_die;
    ^
$HOME/Projects/orc/include/orc/parse_file.hpp:217:5: error: unknown type name 'do_work_callback'
    do_work_callback _do_work;
    ^
$HOME/Projects/orc/include/orc/parse_file.hpp:218:5: error: unknown type name 'empool_callback'
    empool_callback _empool;
    ^
10 errors generated.
make[2]: *** [CMakeFiles/orc_orc.dir/build.make:76: CMakeFiles/orc_orc.dir/src/ar.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:665: CMakeFiles/orc_orc.dir/all] Error 2
make: *** [Makefile:156: all] Error 2

Thank you for this report - I'm working through these build issues now, but am bumping up against the Mach-O headers being missing. Given that this tool was originally intended for use with Mac OS X, it assumes the DWARF data will be embedded within object files formatted as Mach-O. Ubuntu doesn't use Mach-O as its object file format, so there would have to be some work required to get this tool working on that platform. Would you be able to help in this effort?

Please see the above-mentioned PR. The code will now compile under Ubuntu, however there is more work to be done to enable the tool for Ubuntu's object file format. It would be amazing if this could get lit up, however I'm not sure how much time I can dedicate to such an effort currently.

@fosterbrereton would Agner Fog's object converter be a short-term solution? https://www.agner.org/optimize/#objconv

@kc9jud That would certainly allow for ORC to rely on it's current Mach-O underpinnings. The one task that remains there would be to port the Mach-O structures to platforms that do not have them. This should be straightforward, but again, not something I can dedicate time to currently.

PR #21 adds the necessary mach-o types to the project. There's something not building right with the TBB dependency that I cannot figure out. Other than that, the tool should work on Ubuntu now (though still requires Mach-O object files.)


[SPARK-15094][SQL][WIP] Avoid extra Project when DeserializeToObject at top of logical plan

What changes were proposed in this pull request?
We will eliminate the pair of DeserializeToObject and SerializeFromObject in optimizer and add extra Project. However, when DeserializeToObject's outputObjectType is ObjectType and its cls can't be processed by unsafe project, the projection will be failed.
As the extra Project is used to preserve output expr id, if the DeserializeToObject is at the top, we can avoid this extra Project.
How was this patch tested?
DatasetSuite.

Test build #57761 has started for PR 12898 at commit 697679e.

oh. this is not a correct fix. marked as WIP.

Test build #57764 has started for PR 12898 at commit 7108c3a.

Test build #57761 has finished for PR 12898 at commit 697679e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57761/
Test FAILed.

Test build #57764 has finished for PR 12898 at commit 7108c3a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57764/
Test FAILed.

Merged build finished. Test FAILed.

Test build #57837 has started for PR 12898 at commit 94cad73.

Test build #57837 has finished for PR 12898 at commit 94cad73.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57837/
Test FAILed.

Test build #57850 has started for PR 12898 at commit 039a717.

Test build #57850 has finished for PR 12898 at commit 039a717.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57850/
Test PASSed.

Merged build finished. Test PASSed.

Test build #57954 has started for PR 12898 at commit 08c614a.

Test build #57954 has finished for PR 12898 at commit 08c614a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57954/
Test PASSed.

Merged build finished. Test PASSed.

cc @cloud-fan @yhuai @rxin


Getting events propagation to work for static image map, need some help

Hi all,
1st, thanks for the wonderful directive :+1:
I'm trying to tweak the example http://tombatossals.github.io/angular-openlayers-directive/examples/080-events-propagation-example.html to work for static image map but no event is firing ("openlayers.map.singleclick").
Tried also to change "openlayers.map.singleclick" to "openlayers.layers.singleclick" (since my static image is on a layer) but still getting no event.
Can shed some light on this?

Hi @style-x7 , you're totally right, the events functionality is not finished yet. I have added the pixel projection (static image layer) propagation of events, so you can now listen for "pointermove" or "singleclick" in an static image. I have added this example too:
http://tombatossals.github.io/angular-openlayers-directive/examples/083-events-static-image-layer-example.html

Hi @tombatossals,
You're so cool :) I didn't expect to get response and a fix so fast!
I've updated to the master branch and verified the fix, all's good.


Added netty.Channel getter to ServiceRequestHandler and it's impl to …

Added netty.Channel getter to ServiceRequestHandler and it's impl to acquire address of remote client from request.
So I can handle request foir each client differently.

Thanks for your contribution!


Unable to generate deps.json, it may have been already generated.  You can specify the "-d" option before the tool name for diagnostic output (for example, "dotnet -d ": C:\Program Files\dotnet\sdk\2.2.104\Sdks\Microsoft.NET.Sdk\targets\GenerateDeps\GenerateDeps.proj

I am getting following error when I try to execute dotnet svcutil --help/url/wsdl file or anyting.
Unable to generate deps.json, it may have been already generated. You can specify the "-d" option before the tool name for diagnostic output (for example, "dotnet -d ": C:\Program Files\dotnet\sdk\2.2.104\Sdks\Microsoft.NET.Sdk\targets\GenerateDeps\GenerateDeps.proj

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

ID: 3d0bd854-fec8-fc4a-760a-42dc22e07f99
Version Independent ID: f04e9f8b-24d2-79fb-7521-6222c434e80f
Content: WCF svcutil tool overview - .NET Core
Content Source: docs/core/additional-tools/dotnet-svcutil-guide.md
Product: dotnet-core
GitHub Login: @mlacouture
Microsoft Alias: mairaw

I can't seem to replicate this. Can you uninstall and install the tool again?

Closing due to lack of response. Feel free to reopen when you get a chance to respond.

I suddenly faced the problem during working on the project
I already added some web services earlier but now I can't add any and getting the same error
I updated my sdk to latest (I'm using .net core 2.1)
.NET Core SDK (reflecting any global.json):
Version:   2.2.104
Commit:    73f036d4ac
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.17134
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.2.104\
Host (useful for support):
Version: 2.2.2
Commit:  a4fd7b2c84
.NET Core SDKs installed:
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.403 [C:\Program Files\dotnet\sdk]
2.1.508 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.104 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
I tried checking my %temp% path for any semicolons to be removed but still facing the issue
help me please

@3bdulra7eem I discovered the team that made this tool has a repository at https://github.com/dotnet/wcf/issues where you could get help about this tool.


New tlog & sct insecure CLI options - are they really insecure ?

Hello,
Throughout cosign version 1.x.x it was possible to verify images by just providing a public key file and an image reference alone, without integration with transparency log (which was experimental, if i'm not mistaken)
With 2.0.0, transparency log verification enforcement is on by default and, in order to opt out, we have to use the flag insecure-ignore-tlog.
About that insecure part there: If one did not rely on a transparency log up to this point (as it was an experimental feature), is this practice necessarily considered "insecure" from this point? Checks backed by a transparency log adds security, but does it deem working without it as totally bad practice?
Otherwise, this option could just be named as --ignore-tlog?
Same goes for insecure-ignore-sct I suppose.
Also, when running with these flags, the program outputs:
**Warning** Skipping tlog verification is an insecure practice that lacks of transparency and auditability verification for the signature.

Maybe, word it like:
**Warning**, Skipping tlog - signature will not be checked against public transparency logs

Thanks

Cosign as a client is opinionated on what should be required, and we view transparency as a core part of Sigstore. In 1.x, since the transparency service was not yet fully productionized, the defaults were to not use the log. Now that the service is productionized, the default has flipped to leveraging transparency for both key-based and identity-based signing, with the option to opt out.
For private deployments of Sigstore, transparency might not be necessary. We're aware of this and open to suggestions on how to improve the UX.

Hey @haydentherapper totally get your point. Makes sense (as its part of the whole Sigstore ecosystem). Perfect.
However, it is still a valid use-case like you said yourself - for private deployments (full Sigstore or parts of it, e.g. using purely cosign) - and not necessarily insecure.
As a suggestion, I would take the "insecure" wording out of those options and from the program output. It can be potentially misleading and raise user questions. Why is it suddenly insecure?
Thanks

Even in private deployments, it is “insecure” in that you lose out on immutable auditability, which can defend against insider risk. I would encourage private deployments to still leverage transparency logs, unless they understand the impact of removing them.
We may end up creating separate commands for private deployments, there’s a few other issues we’d like to fix with custom PKI. For most users though, it makes sense to leave this as-is to inform them of the lack of transparency when verifying.

See https://github.com/sigstore/cosign/issues/2648 for proposed alternate UX (specifically, it would look more like --transparency-log-validation=none-insecure).
I'm inclined to continue to call deployments that don't have the security features of the public instance "insecure" by default.
Correspondingly, I'm hesitant to take away the warnings unless presented with positive evidence that omitting transparency logs is an acceptable risk. So, we could hide the warning if somehow we told cosign that we were in "private deployment mode." Or we could have users opt to hide specific messages by saying cosign i-promise-i-understand-what-the-tlog-does --force.

Maybe I am missing something, but so far (until 1.13.1) unintentionally missing transparency log integration (except for experimental) was not explicitly stated as being a critical insecure or declared bad practice.
That being the case, since 1.0.0 cosign, this should be labeled as an insecure singing / verification tool - except if you opt-in to experimental features (e.g. so do not use in your production solutions).
I'm strongly against continuing to use "insecure" label here - both on program flag AND in output warnings.
Whoever has been using cosign and distributing contractually their public keys, both images and corresponding signatures to their private registries and advising consumers to use those for verification will be now forcefully having to advise those same consumers to use "insecure" features, highlighting insecure practices (which in fact are not really). I believe you can see this is not nice.
Besides, verifying signature artifacts against known public keys are not necessarily an insecure practice, is it? Maybe - tlogs, and whatnot are extra layer there, tying things up, but this layer does not mean the first use alone is bad practice. Unless of course, I am missing big part of the link here, and so perhaps does the documentation: If such practices are so insecure, as you say, that threat model should be very clear and stated widely in docs - first page material.
Without taking into the fact that the "buy-in" usability and convenience of having zero infrastructure around signature and verification process (besides having your OCI registry) was widely preached since cosign became mainstream - without preaching in the insecurity that came along with not having that transparency log feature on.
Plus - using cosign without a transparency log backing it should be taken into deprecation and removed in future, if so insecure.
But thats just my opinion of course. Please ignore, and feel free to close this comment if invalid.
Thank you


Update dependencies

Updated axios and yargs lib.
Updating yargs required some changes in tests as jest.mock("fs") changed default behavior of fs when readSync error was thrown on which exact message one of the yargs dependency based its logic.

As discussed - we need to remove node v10 and v15 from our build matrix, and add up-to-date current & LTS versions


create plants model

const plantSchema = new Schema({
plantname: [
{
type: String,
},
],
description: {
type: String,
required: true,
},
// saved plant id
plantId: {
type: String,
required: true,
},
image: {
type: String,
},
link: {
type: String,
},
});


Watchdog file list in a table

I have a use case which may require functionaltiy added. I want to use scriptedforms to capture a list of images saved during an experiment run. I will use a form to enter the experiment parameters (in my case camera exposure time etc) and I want the form to display a list of all the .jpg images saved in a folder. At the and of the experiment run I will post the paths of all saved .jpg to an external database. Thereore my request is: live updating table of all .jpg files in a folder. Is this possible?

Yup. Can definitely be done with the current set up.
Something like the following should work. I haven't tested it, just wrote it in here. But it should be close.

<section-start>

```python
import os
from glob import glob
from IPython.display import display, Markdown

path_to_watch = '/a/path/here'
glob_string = os.path.join(path_to_watch, '*.jpg')
```

</section-start>

<section-filechange paths="[path_to_watch]">

```python
file_list = glob(glob_string)
markdown_string = '\n'.join([
    "* {}".format(file)
    for file in file_list
])
display(Markdown(markdown_string))
```

</section-filechange>

With the same application in mind, is it possible to programatically display input text fields, in this case using the column headers from a database?

Yup, programmatically create a pandas dataframe and use the table variable. Would that work?

Your example works nicely

Good to hear :)


typo Add a guide to using SQL for the jdbc catalog

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


How to override default configuration for formatters?

it's not a bug report, it's a question
Conform help don't say anything about overriding the default configuration or rules of any formatter.
How can this be achieved? Does conform pickup config files inside a project? is there a way to add global configuration to where the formatters are installed? I am using Mason to install the formatters.

@C0deBr3ak3r is correct, the formatters table is the correct place to override. Note that setting inherit = false means that we will use the exact configuration you supply. If you instead want to merge your configuration with the built-in config, set inherit = true or just leave it out altogether (true is the default).

Hey guys, question about this:
I have my formatters_by_ft explicitly set up to use formatters. But seems like taplo as an LSP also does formatting (even if I don't have toml = { 'taplo' } in my formatters_by_ft, my buffer is still auto-formatted).
Now, if I do add toml = { 'taplo' } in my conform config, I don't seem to be able to configure it properly.
Let's say I want to pass --option align_entries=true; I tried doing this:
formatters_by_ft = {
  toml = { 'taplo' },
},
formatters = {
  taplo = {
    prepend_args = { '--option', 'align_entries=true' }
  }
}

This complains saying Found argument '--option' which wasn't expected, which makes sense looking at taplo.lua in the formatters.
So, I tried this:
formatters = {
  taplo = {
    args = { 'format', '--option', 'align_entries=true' },
  }
}

And, with this, whenever I save, I get the message: WARNING: The file has been changed since reading it
Next, I tried to completely override it (needed to install the taplo binary separately):
formatters = {
  taplo = {
    inherit = false,
    command = 'taplo',
    args = { 'format', '--option', 'align_entries=true' },
  }
}

With this also I'm getting the "file has been changed" warning message.
Any help is appreciated. Thank you!

My guess is you need
args = { 'format', '--option', 'align_entries=true', '-' },

As that final - in the arguments tells the command to use stdin/stdout for formatting. In general, I will direct you to the docs on debugging which should be helpful for figuring out what could be going wrong.

Thank you so much @stevearc for the quick answer; as you pointed out, the missing part was the - arg at the end.
I did some troubleshooting using ConformInfo (that's where I got those error messages), but didn't know about that debugging doc; will definitely take a look at that!


SimpleHttpOperator tests are reaching out to google.com

Dear Airflow Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Version of Airflow (e.g. a release version, running your own fork, running off master -- provide a git log snippet) : master

Example code to reproduce the bug (as a code snippet in markdown)
https://travis-ci.org/airbnb/airflow/jobs/118566538

Screen shots of your DAG's graph and tree views:

Stack trace if applicable:
root: INFO: Sending 'GET' to url: https://www.google.com//search
root: ERROR: HTTP error: Service Unavailable
root: ERROR: 503:Service Unavailable
Traceback (most recent call last):
File "/home/travis/build/airbnb/airflow/airflow/models.py", line 1077, in run
result = task_copy.execute(context=context)
File "/home/travis/build/airbnb/airflow/airflow/operators/http_operator.py", line 61, in execute
self.extra_options)
File "/home/travis/build/airbnb/airflow/airflow/hooks/http_hook.py", line 64, in run
return self.run_and_check(session, prepped_request, extra_options)
File "/home/travis/build/airbnb/airflow/airflow/hooks/http_hook.py", line 95, in run_and_check
raise AirflowException(str(response.status_code)+":"+response.reason)
AirflowException: 503:Service Unavailable

Operating System: (Windows Version or $ uname -a)
Travis

Python Version: $ python --version
All

(Optional) Python packages: $ pip freeze or $ conda list

Now that you know a little about me, let me tell you about the issue I am having:
Description of Issue

What did you expect to happen?
I expect tests not to reach out to Google.com

What happened instead?
Tests are reaching out to Google.com. This causes occasional failures (timeout, 500 error, etc). This is non-deterministic, and causes unit tests to fail sporadically.

Here is how you can reproduce this issue on your machine:

Reproduction Steps

This was fixed.


csolution convert adds *.base configuration files to RTE folder

Describe the bug
When a *.base file is missing in the RTE folder the csolution convert without further options adds the *.base file of the current software pack. As the project might have been used an older version of the pack (with an older version of the *.base file, this might create incorrect information.
To Reproduce
Delete the *.base file of a RTE configuration file and run csolution convert.
Expected behavior
The missing *.base file should be reported as error as proposed under #1694
This relates to #1484
Environment:

csolution: 2.5.0+p43-gca002acf
OS: Windows

Please note, contrary to cbuild, csolution uses --update-rte by default.
After removing the base file you should call csolution with --no-update-rte to get the warning precisely as proposed in https://github.com/Open-CMSIS-Pack/devtools/issues/1694
$ csolution convert USB_Device.csolution.yml --no-update-rte
warning csolution: file 'D:/examples/USBD/HID/RTE/USB/USB_Debug.h.base' not found; base version unknown

The copy of the base file when using --update-rte was already discussed in the past, please see https://github.com/Open-CMSIS-Pack/devtools/issues/773

The question for me remains, whether or not the --udpate-rte should have created the *.base file.
Would it be okay to copy the *.base configuration file if it is not present and the configuration file that is present is identical with the default config file located in the selected pack?

I believe the current behavior is OK. We should just enable that cbuild setup outputs warning messages (#1767).


CDH/eHSM: add features for eHSM support

Both Ehsm and ehsm should be supported when a sealed secret indicates the kms type
added ehsm feature to confidential data hub binary build to leaverage the ability.

cc @1570005763

verified unseal secrets with eHSM, thanks a lot! @Xynnn007 @1570005763


Flipped

@demseyk congratulations on winning first place for the design contest! Please reach out to us via<EMAIL_ADDRESS>or DM us on Twitter with your contact info so you can collect your prize!


Dual white lights not working properly on a Milight V6 bridge

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.60.0
Python release (python3 --version):
3.5
Component/platform:
Limitlessled
Description of problem:
The Milight dual white lights were working properly when I had the Milight V5 bridge. I am now using a Milight V6 bridge and it comes with a new app (Milight 3.0). You can only link the dual white lights to a remote control that Home Assistant not uses for controlling the "white" lights.
Expected:
Controlling the dual white lights should also be working on a Milight V6 bridge.
Problem-relevant configuration.yaml entries and steps to reproduce:

light:
  platform: limitlessled
  bridges:
    - host: !secret
      groups:
        - number: 1
          type: rgbw
          name: light living room
        - number: 2
          type: rgbw
          name: light restroom
        - number: 1
          type: white
          name: light bedroom
        - number: 2
          type: white
          name: light hall
        - number: 3
          type: white
          name: light kitchen

**Traceback (if applicable):**
```bash

Additional info:
JustinP made a temporary fix to solve the issue locally (only on/off is working, brightness and colour temperature is not working). It is described here:
https://community.home-assistant.io/t/update-limitlessled-milight-component-v6-bridge-ibox/6248/203

The linked fix was done in the limitlessled library. So that library probably needs to add support, release a new version, then we can upgrade home assistant to use the new version.

I saw that their code is already updated. They put it online 14 days ago:
https://github.com/happyleavesaoc/python-limitlessled/blob/master/limitlessled/group/commands/v6.py

That's good. We still need them to release a new version to pypi though, since that's how we pull the requirements into home assistant. Then we usually want someone that owns the device in question to make a PR to home assistant upgrading the library version, so that the user can verify that the new version works.

When will home-assistant use the 1.0.9 version of python-Limitlessled ?
My white only (1ch) dimmer is not working and i'm hoping it is with 1.0.9

When someone that owns a limitless light and can test the new version makes a PR to home assistant with a version bump.


asdf compatiblity

Is there a reason you didn't create an asdf system? If you're not familiar I could assist with that.

Hi Kilian!
Thanks, I didn't get enough time last year to finish up this project, but if you're interested - feel free to create a branch. I was thinking of investing more time in the project this year - there's a lot to polish up. I see I haven't included any testing for the proxy as well.

Where you got cl-cache from? I can not find it in Quicklisp / Ultralisp / Git ...

I used an in-house/proprietary library, which means I need to either re-implement it or use an adequate package for common lisp to use out of the box. I seem to have forgotten to commit it from my dev environment.


Implement loot tracking for MLM

IMO this seems out of scope for the loottracker since this is essentially a skilling resource and isn't really "loot".

IMO this seems out of scope for the loottracker since this is essentially a skilling resource and isn't really "loot".

There isn't currently a way to track the ores received in terms of currency. How about adding the profit into the MLM Plugin Overlay?

There already is an overlay which shows what ores you found. I guess you could add price to that.

Per Adam's comment, this can be implemented as a price line added to the MLM ores overlay.


Added method call support in DI and Yii::configure

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Cannot leave Yii::configure() untouched to have consistent behavior for all objects.

Merged. Thank you very much!


:white_check_mark: check goat coordinates

Is your feature request related to a problem? Please describe.
Check goat coordinates as described by email
Describe the solution you'd like
Check and fix chromosome names accordingly http://www.goatgenome.org/data/capri4dbsnp-base-CHI-ARS-OAR-UMD.csv and http://www.goatgenome.org/data/Goat_IGGC_65K_v2_A2_chr_mapinfo_Aux_file.txt
Describe alternatives you've considered
The data which comes from manifest seems to be almost correct, however there are SNPs which are annotated on X chromosomes while they are in a scaffold
Additional context
The probes have been mapped on ARS1 assembly with the following naming of chromosomes/scaffolds:

    1 to 29
    MT
    X.1 X.2 for scaffold assigned to X in the auxiliary and csv files, X in the bpm file
    Y.1 to Y.11 for scaffolds assigned to Y in the auxiliary and csv files, Y in the bpm file
    0.scaffold_name…for unplaced scaffold (example: 0.NW_017191871.1) in the auxiliary and csv files, 0.NW_scaffold in the bpm file.

For probes either unlocalized or with multiple localizations or not confirmed as belonging to X or Y scaffolds (after studying the genotypes), localization was set to null.

[ ] check goat chromosomes with aux file
[ ] check chromosomes in Variants locations: mind to scaffold, null, and   non-autosomal

This issue could be superseded by uploading alignments as a new Location evidence


Starting Rails Server fails on Raspberry PI 3 B+

I´ve been trying to install rbenv, ruby and rails in my Raspberry Pi 3 B+ in the past couple of days and after some issues here and there I've managed to get everything installed with no errors
With rbenv I installed both Ruby 2.6.3 and Ruby 2.5.5
Using Rails 5.2.3
and with both ruby versions I am getting the same problem when I execute the command:
rails server

Steps to reproduce

On a Raspberry Pi install rbenv using brew

brew install rbenv

Then use the following command to install ruby

rbenv install 2.6.3

Then install rails:

gem install rails -v 5.2.3

Create a new folder to hold your application and go to that folder:

$ cd                  # Change to the home directory.
$ mkdir environment     # Make a environment directory.
$ cd environment/       # Change into the environment directory.

Use rails to create the application inside the previous folder:

rails _5.2.3_ new hello_app

Go to the recently created 'hello_app' folder

cd hello_app

Start the rails server

rails server

Expected behavior
pi@raspberrypi:~/environment/hello_app $ rails server
=> Booting Puma
=> Rails application starting on http://localhost:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server

And then it should just stay there to be able to access the web app on the address indicated
Actual behavior
First, the output shows this:
pi@raspberrypi:~/environment/hello_app $ rails server
=> Booting Puma
=> Rails 5.2.3 application starting in development
=> Run `rails server -h` for more startup options

And then the contents of the text file in the next link are shown.
Here is a link with the whole output:
https://www.dropbox.com/s/gjgo81zqeekfnvt/railsservererror.txt?dl=0
System configuration
Ruby version: I´ve tried with both 2.6.3 and Ruby 2.5.5
Rails version: I've tried with 6.0.0.rc1 and with 5.2.3
Puma version: I've tried with 3.12.1 and a previous one too
Workaround
User @dannyfallon  helped me with a workaround and explanation as follows from the Puma github site because I thought this was an issue with the Puma web server, but I was wrong:

According to your segfault's Control frame information you never even reached Puma. I would think that since Puma was never reached if you swapped puma in your gemfile for thin or webrick you still wouldn't be able to run rails server.
When you run rails server the application does a bunch of stuff before actually passing off the Rails::Application to a Rack server to run. In development Rails creates an EventedFileWatcher to watch for file changes so it can reload your app without you having to stop/start your server all the time. This uses the listen gem, which under the hood uses some OS-specific file events so it doesn't have to keep polling. In trying to create a watch (which listen does through rb-inotify for Linux), Ruby encountered a segmentation fault:
/home/pi/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/rb-inotify-0.10.0/lib/rb-inotify/notifier.rb:57: [BUG] Segmentation fault at 0xe92d000e
ruby 2.5.5p157 (2019-03-15 revision 67260) [armv7l-linux-eabihf]

-- Control frame information -----------------------------------------------
c:0095 p:---- s:0527 e:000526 CFUNC  :inotify_init
c:0094 p:0041 s:0523 e:000522 METHOD /home/pi/.rbenv/versions/2.5.5/lib/ruby/gems/2.5.0/gems/rb-inotify-0.10.0/lib/rb-inotify/notifier.rb:57 [FINISH]

Because rb-inotify is using FFI and some C functions, when things go wrong it does tend to blow up badly with segmentation faults.
There's lots of stuff you can do if you want to go deeper like report a bug over at FFI, attempt to recompile Ruby from source, test inotify on your distro outside of Ruby but you probably just want to get on with some development given you've been at it a few days.
I believe to fix this you can open config/development.rb and replace this:
  # Use an evented file watcher to asynchronously detect changes in source code,
  # routes, locales, etc. This feature depends on the listen gem.
  config.file_watcher = ActiveSupport::EventedFileUpdateChecker

with
  # Use a simple file watcher to detect changes in source code
  config.file_watcher = ActiveSupport::FileUpdateChecker

Caveat: The EventedFileWatcher is supposed to use OS events to detect file changes. The
FileWatcher will poll for changes. This may slow down reloads or cause higher system load.

Originally posted by @dannyfallon in https://github.com/puma/puma/issues/1797#issuecomment-493190148
The solution proposed by @dannyfallon  actually allowed me to start the Web Server, but I was wondering if the people here at rb-inotify could give me a hand to try to figure out what went wrong and if there is anything I can do to fix this problem and be able to use
config.file_watcher = ActiveSupport::EventedFileUpdateChecker

Sorry for the long post...
Awaiting your comments.
P.S.: by the way, I get the same segmentation fault when I try to create a new rails app with rails version 6.0.0.rc1:
rails _6.0.0.rc1_ new hello_app

but if I use version 5.2.3 I don´t get the error
rails _5.2.3_ new hello_app

Thanks,

I am following a tutorial to learn Ruby on Rails and I am also getting the same error when I try to run the following Rails command:
rails generate scaffold User name:string email:string

Now I am basically stucked

Hi there,
I have the exact same issue on Rpi3 with Rails 5.2.3 and Ruby 2.3.3p222.
I just reported the issue here : https://bugs.ruby-lang.org/issues/15898

So, now you know it still happens with a later ruby version :(, let's wait and see if someone has found a solution for this

I thinks ways to solve this issue is

to add armv7l (ARM 32-bit) case to Travis CI with multiarch docker container.
Example to add the case to Travis CI. https://github.com/jts/nanopolish/blob/master/.travis.yml#L46-L75
to start to use ARM 32-bit providing CI such as Shippable CI, Drone CI.

Shippalbe CI: https://app.shippable.com/
Example: https://github.com/junaruga/ci-multi-arch-test/blob/master/shippable.yml
Drone CI: https://drone.io/

Then people can reproduce the issue to fix it.

@ultrasam
Well it just worked by installing Ruby 2.6.3 with this script (https://gist.github.com/blacktm/8302741 from the answer on ruby bug tracker).

@johhnry so the Rails server is now working for you?

@ultrasam
Yes it's working fine. I just had to change the Ruby version in the Gemfile and the .ruby-version file.

Closing as seems fixed. Please let me know if this is not the case.

I do get the same issue with ruby 2.7.1, 2.7.2 on a Pi 4 unless i change
config.file_watcher = ActiveSupport::EventedFileUpdateChecker

to
config.file_watcher = ActiveSupport::FileUpdateChecker

Even then, i can boot the application and use it (haven't tested everything yet)
Still
rails console results in Segfault
/home/pi/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/rb-inotify-0.10.1/lib/rb-inotify/notifier.rb:62: [BUG] Segmentation fault at 0xe92d000e ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [armv7l-linux-eabihf]
Full Output
https://pastebin.com/raw/WDe8aAXf

I do get the same issue with ruby 2.7.1, 2.7.2 on a Pi 4 unless i change
config.file_watcher = ActiveSupport::EventedFileUpdateChecker

to
config.file_watcher = ActiveSupport::FileUpdateChecker

Even then, i can boot the application and use it (haven't tested everything yet)
Still
rails console results in Segfault
/home/pi/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/rb-inotify-0.10.1/lib/rb-inotify/notifier.rb:62: [BUG] Segmentation fault at 0xe92d000e ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [armv7l-linux-eabihf]
Full Output
https://pastebin.com/raw/WDe8aAXf

For anyone encountering the same Problem : Upgrade your Pi(4) to use USB 3.0 Sticks on the Boot Medium instead of USB 2.0 Sticks. Not only did it fix the Issue for me, it also improved the Performance of my Rails Application atleast 8 Fold.


Exponents Operation

The question made for the agent goes to the examples/exponents/ directory.

I think it might be a good idea to copy and commit my custom operators here? so that custom_operations.py in the al_core repo wouldn't be polluted.
Also, I just found a problem with training on batch_training_10.json, which I originally wanted to train 10 agents, but now just 4, it is very likely to throw an exception during training. But I haven't looked into details of the bug.


Update deps

This is a WIP on updating the dependencies for ooni/run.
It proved to be much more time intensive and painful than I was expecting it to be.
What is currently broken/missing is the following:

[ ] Testing that the redirects for the /nettests path works as expected in all browsers
[ ] Fixing the styling of the Hero components (it's unclear if something changed in ooni-components or if it's related to the styled-components update)
[ ] Loading of fonts is currently broken as it seems like the paths exposed by next.js have changed between 9->12

This is superseeded by https://github.com/ooni/run/pull/125


Circular links should be supported

So I'm having the following use case:
app_test:
  image: myapp
  links:
    - selenium
    - selenium_firefox

selenium:
  image: selenium/hub

selenium_firefox:
  image: selenium/node-firefox
  links:
    - selenium:hub
    - app_test

So when using the official Selenium images you need to create a container for the "hub" and then create containers for each node and link them to the hub. The link direction has to be node->hub. Now my app needs to be linked to the selenium hub to be able to run selenium tests. It does not need to know about the selenium node (selenium_firefox) but it is linked anyway because links govern which containers will be started.... However, the selenium node does need to know about my app container in order for it to run tests against it. I'm stuck now because with this configuration jet complains:
services file error: Circular loop between services app_test and selenium_firefox

Unless I'm missing something I understand that links are used as hints to tell jets which services have to be launched along with each service. Apparently this doesn't work for all cases. Also, a potential bug: if I give app_test an alias in the links array (app_test:app for example) then the circular loop is not detected and jet happily runs and ends up in an infinite loop :)

Hey @kreisys -- you have the right idea, but link is more than just a hint; it's a dependency. This doesn't come from Jet but rather from Docker itself: https://docs.docker.com/engine/userguide/networking/default_network/dockerlinks/
Since the link designates a dependency, circular dependencies are not allowed, and you've already discovered why: an infinite loop. It's not that the linked services are launched along with each service, but before each service.
For more info on running Selenium with Docker, check out http://www.conductor.com/nightlight/running-selenium-grid-using-docker-compose/.

We are still restricted by the behaviour of docker-compose. We intend to match compose closely, and your issue should be resolve when we adopt the v2 syntax. A good rubric is if the services work with docker compose, then they should work with jet also. If they don't we treat it as a bug.
docker-compose up myapp
Circular import between app_test and selenium_firefox and selenium

In the meantime you may need to set up some kind of stub leaf service to let you break out of the circular dependency loop.

I'm trying to get around this exact issue. What version of docker-compose is supported by Codeship?

@kreisys I am facing the exact same issue, while using docker-compose v3. Any work around or alternate way for this issue?

Links are deprecated, and Codeship supports depends_on. Read more about it here: https://blog.codeship.com/announcing-depends_on-support/


Introduction to unit testing

Yes, I should've checked what I copied and pasted from the above method, I will be more careful in the future.


rcss3d_nao: 1.1.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository rcss3d_nao to 1.1.0-1:

upstream repository: https://github.com/ros-sports/rcss3d_nao.git
release repository: https://github.com/ros2-gbp/rcss3d_nao-release.git
distro file: rolling/distribution.yaml
bloom version: 0.11.2
previous version for package: 1.0.0-1

rcss3d_nao
* Add x,y,theta parameters to easily set initial position of robot
* Contributors: Kenji Brameld, ijnek

Holding for the upcoming Rolling sync.

Thanks @emersonknapp


Declare multiple drivers in config

Added a driver validator.  Will error if a subcommand is used with
a different driver than the one used to create the instances.
Added back missing exception classes from basedriver.
Added proper exception handling for invalid platform/provider.
Added ability to support multiple drivers in the config at the same
time.


Visual Studio: ignore 'ncrunchproject' and 'ncrunchsolution' files

Reasons for making this change:
When using the gitignore template prior to this commit and when NCrunch is added to a solution, 'ncrunchproject' and 'ncrunchsolution' files are tracked - I don't believe these files should be in source.
This commit fixes the issue by using the following pattern:

*ncrunch*

Note: Using the pattern above means that _NCrunch_* and nCrunchTemp_* were no longer required, hence me removing them in this commit.

Thanks, but the official guidance suggests these should not be ignored:

It's recommended that the last two files listed in the above table (.v3.ncrunchsolution and .v3.ncrunchproject) be stored inside a source control system to be shared with team members.

See https://github.com/github/gitignore/pull/2056 has some other details


checkpoint: make run func generic

Make run func generic. Preparing for adding etcd checkpoint support.

If this approach looks good to you, I will continue to clean up the manifest file part.

@derekparker I will continue to make the manifest part more generic.

@derekparker @aaronlevy
All fixed. And I changed manifest part to be generic too. PTAL. I do not have setup to test checkpointer yet. It would be great, if you can help me to do a quick test. Thank you in advance.

@pbx0 this would be a good candidate for your destructive tests. Testing this will be a little wonky though - we would likely need to build a checkpoint image from this commit, then use that image in the checkpoint manifest in this PR.

@aaronlevy: LGTM I tested it against the basic destructive test here: https://github.com/kubernetes-incubator/bootkube/pull/201


feat(turbopack): support importmapping extension

Description
This PR attempts to expand importmapping to have Extension, to create import from the source code string. Importmapping will create virtualasset per each mapping.
Also it includes a runtime fn to create a proxy to throw certain error at runtime, which will be used edge runtime's alias to create mappings.
Closes PACK-2629

Per discussion, we'll going to approach without expanding importmapping enum but try to use existing mechanism.


[macOS] [AndroidTV]: Can't connect to bundler. Try restarting it.

aftre updating renative to 0.37.2
trying to run androidTv with command npx rnv run -p androidtv -s debug
I get this error

node v16.0.0
MAC OS

To give an update running the command "rnv start -p androidtv"
get this error

@BitaShmsfr hello, sorry for late reply, I see you are using very old version of template-blank, could you please try 0.37.3 version of both template-starter and rnv?

@BitaShmsfr sorry for late reply, we need to do some investigation for this, will get back to you asap

@BitaShmsfr we are still working on this issue, sorry it's taking so long.  Could you add tslib to the project and try to run it again?

@ElenaDiachenko Thanks for taking care of that , I am waiting for your final response then.
I did so, and bundler seems running now but now it can not connect to emulator on any platform.

@BitaShamsafar Could you please provide the full text of the error?

@ElenaDiachenko
sure Here is the error which stops on android

and this one is for AppleTv
`
│ [ error ] [run] COMMAND:
node /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/local-cli/cli.js run-ios --project-path platformBuilds/sport1_tvos --scheme RNVAppTVOS --configuration Debug --simulator Apple\ TV --allowProvisioningUpdates
FAILED with ERROR:
error Could not find "Podfile.lock" at /Users/bshamsaf/Projects/prj-sport1-app/appConfigs/sport1/builds/tvos/Podfile.lock. Did you run "pod install" in iOS directory?
info Found Xcode workspace "RNVAppTVOS.xcworkspace"
info Building (using "xcodebuild -workspace RNVAppTVOS.xcworkspace -configuration Debug -scheme RNVAppTVOS -destination id=C60BC67D-3E45-40D7-9295-742A07920374 -derivedDataPath build/RNVAppTVOS -allowProvisioningUpdates")

Building the app.........
Building the app.
Building the app........
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening RNVAppTVOS.xcworkspace.
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace RNVAppTVOS.xcworkspace -configuration Debug -scheme RNVAppTVOS -destination id=C60BC67D-3E45-40D7-9295-742A07920374 -derivedDataPath build/RNVAppTVOS -allowProvisioningUpdates
User defaults from command line:
IDEDerivedDataPathOverride = /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS
IDEPackageSupportUseBuiltinSCM = YES

Command failed with exit code 1: node /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/local-cli/cli.js run-ios --project-path platformBuilds/sport1_tvos --scheme RNVAppTVOS --configuration Debug --simulator Apple TV --allowProvisioningUpdates
warn Package markdown-to-jsx has been ignored because it contains invalid configuration. Reason: Package subpath './package.json' is not defined by "exports" in /Users/bshamsaf/Projects/prj-sport1-app/node_modules/markdown-to-jsx/package.json
error Could not find "Podfile.lock" at /Users/bshamsaf/Projects/prj-sport1-app/appConfigs/sport1/builds/tvos/Podfile.lock. Did you run "pod install" in iOS directory?
error Could not find the following native modules: react-native-blur, RNCMaskedView, react-native-statusbar, react-native-viewpager, RNFBAnalytics, RNFBApp, RNFBAuth, RNFBCrashlytics, RNFBDynamicLinks, RNFBFirestore, RNFBInAppMessaging, RNFBMessaging, react-native-snap-scrollview, react-native-sourcepoint-cmp, react-native-at-internet, RNDefaultPreference, RNDeviceInfo, RNExitApp, react-native-fast-image, RNFirebase, RNFS, RNGestureHandler, react-native-get-random-values, react-native-google-cast, react-native-home-indicator, react-native-keep-awake, BVLinearGradient, react-native-orientation-locker, RNReanimated, react-native-safe-area-context, RNScreens, react-native-sourcepoint-cmp, react-native-splash-screen, RCTSystemSetting, react-native-tv-remote-handler, RNTVOSController, RNVectorIcons, react-native-video, react-native-video, RNZendeskChat. Did you forget to run "pod install" ?

Building the app.........
Building the app.
Building the app........
Building the app.........
Building the app.......
Building the app........
Building the app...
Building the app.....
Building the app
Building the app...
Building the app...
Building the app.......
Building the app........
Building the app.......
Building the app.........
Building the app
Building the app..
Building the app...
Building the app.....
Building the app..
Building the app.....
Building the app........
Building the app.
Building the app........
Building the app.........
Building the app........
Building the app
Building the app.....
Building the app.
Building the app..
Building the app.........
Building the app.......
Building the app....
Building the app.
Building the app.....
Building the app......
Building the app.......
Building the app.....
Building the app....
Building the app......
Building the app.....
Building the app.....
Building the app.
Building the app.......
Building the app.....
Building the app.
Building the app......
Building the app..
Building the app.
Building the app..
Building the app....
Building the app....
Building the app...
Building the app........
Building the app.........
Building the app.......
Building the app........
Building the app
Building the app......
Building the app.........
Building the app
Building the app......
Building the app..
Building the app
Building the app.....
Building the app....
Building the app...
Building the app........
Building the app........
Building the app...
Building the app.........
Building the app.
Building the app....
Building the app...
Building the app.......
Building the app
Building the app..
Building the app..
Building the app.......
Building the app.........
Building the app...
Building the app
Building the app..
Building the app.
Building the app........
Building the app......
Building the app........
Building the app.
Building the app
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening RNVAppTVOS.xcworkspace.
info Found Xcode workspace "RNVAppTVOS.xcworkspace"
info Building (using "xcodebuild -workspace RNVAppTVOS.xcworkspace -configuration Debug -scheme RNVAppTVOS -destination id=C60BC67D-3E45-40D7-9295-742A07920374 -derivedDataPath build/RNVAppTVOS -allowProvisioningUpdates")
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace RNVAppTVOS.xcworkspace -configuration Debug -scheme RNVAppTVOS -destination id=C60BC67D-3E45-40D7-9295-742A07920374 -derivedDataPath build/RNVAppTVOS -allowProvisioningUpdates

User defaults from command line:
IDEDerivedDataPathOverride = /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS
IDEPackageSupportUseBuiltinSCM = YES
Prepare packages
Computing target dependency graph and provisioning inputs
Create build description
Build description signature: f7c04d9d0c96970995447f915b52bd57
Build description path: /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/XCBuildData/f7c04d9d0c96970995447f915b52bd57-desc.xcbuild
note: Building targets in dependency order
/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods/Pods.xcodeproj: warning: The tvOS Simulator deployment target 'TVOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'DoubleConversion' from project 'Pods')
WriteAuxiliaryFile /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/DoubleConversion.build/DoubleConversion-all-target-headers.hmap (in target 'DoubleConversion' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
write-file /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/DoubleConversion.build/DoubleConversion-all-target-headers.hmap
/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods/Pods.xcodeproj: warning: The tvOS Simulator deployment target 'TVOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'Folly' from project 'Pods')
Ld /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly/folly.framework/folly normal (in target 'Folly' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -target x86_64-apple-tvos10.0-simulator -dynamiclib -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVSimulator.platform/Developer/SDKs/AppleTVSimulator16.1.sdk -L/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/EagerLinkingTBDs -L/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/EagerLinkingTBDs -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/DoubleConversion -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/glog -filelist /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/Folly.build/Objects-normal/x86_64/folly.LinkFileList -install_name @rpath/folly.framework/folly -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/Folly.build/Objects-normal/x86_64/folly_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -stdlib=libc++ -fobjc-arc -fobjc-link-runtime -lstdc++ -framework DoubleConversion -framework glog -framework Foundation -compatibility_version 1 -current_version 1 -Xlinker -dependency_info -Xlinker /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/Folly.build/Objects-normal/x86_64/folly_dependency_info.dat -o /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly/folly.framework/folly
WriteAuxiliaryFile /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-jsinspector.build/jsinspector-all-target-headers.hmap (in target 'React-jsinspector' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
write-file /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-jsinspector.build/jsinspector-all-target-headers.hmap
WriteAuxiliaryFile /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-cxxreact.build/cxxreact-all-target-headers.hmap (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
write-file /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-cxxreact.build/cxxreact-all-target-headers.hmap
CpHeader /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers/JsArgumentHelpers.h /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JsArgumentHelpers.h (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JsArgumentHelpers.h /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers
CpHeader /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers/MessageQueueThread.h /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/MessageQueueThread.h (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/MessageQueueThread.h /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers
CpHeader /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers/JSModulesUnbundle.h /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JSModulesUnbundle.h (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JSModulesUnbundle.h /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-ap
warn Package markdown-to-jsx has been ignored because it contains invalid configuration. Reason: Package subpath './package.json' is not defined by "exports" in /Users/bshamsaf/Projects/prj-sport1-app/node_modules/markdown-to-jsx/package.json
error Could not find "Podfile.lock" at /Users/bshamsaf/Projects/prj-sport1-app/appConfigs/sport1/builds/tvos/Podfile.lock. Did you run "pod install" in iOS directory?
error Could not find the following native modules: react-native-blur, RNCMaskedView, react-native-statusbar, react-native-viewpager, RNFBAnalytics, RNFBApp, RNFBAuth, RNFBCrashlytics, RNFBDynamicLinks, RNFBFirestore, RNFBInAppMessaging, RNFBMessaging, react-native-snap-scrollview, react-native-sourcepoint-cmp, react-native-at-internet, RNDefaultPreference, RNDeviceInfo, RNExitApp, react-native-fast-image, RNFirebase, RNFS, RNGestureHandler, react-native-get-random-values, react-native-google-cast, react-native-home-indicator, react-native-keep-awake, BVLinearGradient, react-native-orientation-locker, RNReanimated, react-native-safe-area-context, RNScreens, react-native-sourcepoint-cmp, react-native-splash-screen, RCTSystemSetting, react-native-tv-remote-handler, RNTVOSController, RNVectorIcons, react-native-video, react-native-video, RNZendeskChat. Did you forget to run "pod install" ?

Building the app.........
Building the app.
Building the app........
Building the app.........
Building the app.......
Building the app........
Building the app...
Building the app.....
Building the app
Building the app...
Building the app...
Building the app.......
Building the app........
Building the app.......
Building the app.........
Building the app
Building the app..
Building the app...
Building the app.....
Building the app..
Building the app.....
Building the app........
Building the app.
Building the app........
Building the app.........
Building the app........
Building the app
Building the app.....
Building the app.
Building the app..
Building the app.........
Building the app.......
Building the app....
Building the app.
Building the app.....
Building the app......
Building the app.......
Building the app.....
Building the app....
Building the app......
Building the app.....
Building the app.....
Building the app.
Building the app.......
Building the app.....
Building the app.
Building the app......
Building the app..
Building the app.
Building the app..
Building the app....
Building the app....
Building the app...
Building the app........
Building the app.........
Building the app.......
Building the app........
Building the app
Building the app......
Building the app.........
Building the app
Building the app......
Building the app..
Building the app
Building the app.....
Building the app....
Building the app...
Building the app........
Building the app........
Building the app...
Building the app.........
Building the app.
Building the app....
Building the app...
Building the app.......
Building the app
Building the app..
Building the app..
Building the app.......
Building the app.........
Building the app...
Building the app
Building the app..
Building the app.
Building the app........
Building the app......
Building the app........
Building the app.
Building the app
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening RNVAppTVOS.xcworkspace.

Error: Command failed with exit code 1: node /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/local-cli/cli.js run-ios --project-path platformBuilds/sport1_tvos --scheme RNVAppTVOS --configuration Debug --simulator Apple TV --allowProvisioningUpdates
warn Package markdown-to-jsx has been ignored because it contains invalid configuration. Reason: Package subpath './package.json' is not defined by "exports" in /Users/bshamsaf/Projects/prj-sport1-app/node_modules/markdown-to-jsx/package.json
error Could not find "Podfile.lock" at /Users/bshamsaf/Projects/prj-sport1-app/appConfigs/sport1/builds/tvos/Podfile.lock. Did you run "pod install" in iOS directory?
error Could not find the following native modules: react-native-blur, RNCMaskedView, react-native-statusbar, react-native-viewpager, RNFBAnalytics, RNFBApp, RNFBAuth, RNFBCrashlytics, RNFBDynamicLinks, RNFBFirestore, RNFBInAppMessaging, RNFBMessaging, react-native-snap-scrollview, react-native-sourcepoint-cmp, react-native-at-internet, RNDefaultPreference, RNDeviceInfo, RNExitApp, react-native-fast-image, RNFirebase, RNFS, RNGestureHandler, react-native-get-random-values, react-native-google-cast, react-native-home-indicator, react-native-keep-awake, BVLinearGradient, react-native-orientation-locker, RNReanimated, react-native-safe-area-context, RNScreens, react-native-sourcepoint-cmp, react-native-splash-screen, RCTSystemSetting, react-native-tv-remote-handler, RNTVOSController, RNVectorIcons, react-native-video, react-native-video, RNZendeskChat. Did you forget to run "pod install" ?

Building the app.........
Building the app.
Building the app........
Building the app.........
Building the app.......
Building the app........
Building the app...
Building the app.....
Building the app
Building the app...
Building the app...
Building the app.......
Building the app........
Building the app.......
Building the app.........
Building the app
Building the app..
Building the app...
Building the app.....
Building the app..
Building the app.....
Building the app........
Building the app.
Building the app........
Building the app.........
Building the app........
Building the app
Building the app.....
Building the app.
Building the app..
Building the app.........
Building the app.......
Building the app....
Building the app.
Building the app.....
Building the app......
Building the app.......
Building the app.....
Building the app....
Building the app......
Building the app.....
Building the app.....
Building the app.
Building the app.......
Building the app.....
Building the app.
Building the app......
Building the app..
Building the app.
Building the app..
Building the app....
Building the app....
Building the app...
Building the app........
Building the app.........
Building the app.......
Building the app........
Building the app
Building the app......
Building the app.........
Building the app
Building the app......
Building the app..
Building the app
Building the app.....
Building the app....
Building the app...
Building the app........
Building the app........
Building the app...
Building the app.........
Building the app.
Building the app....
Building the app...
Building the app.......
Building the app
Building the app..
Building the app..
Building the app.......
Building the app.........
Building the app...
Building the app
Building the app..
Building the app.
Building the app........
Building the app......
Building the app........
Building the app.
Building the app
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening RNVAppTVOS.xcworkspace.
info Found Xcode workspace "RNVAppTVOS.xcworkspace"
info Building (using "xcodebuild -workspace RNVAppTVOS.xcworkspace -configuration Debug -scheme RNVAppTVOS -destination id=C60BC67D-3E45-40D7-9295-742A07920374 -derivedDataPath build/RNVAppTVOS -allowProvisioningUpdates")
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace RNVAppTVOS.xcworkspace -configuration Debug -scheme RNVAppTVOS -destination id=C60BC67D-3E45-40D7-9295-742A07920374 -derivedDataPath build/RNVAppTVOS -allowProvisioningUpdates

User defaults from command line:
IDEDerivedDataPathOverride = /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS
IDEPackageSupportUseBuiltinSCM = YES
Prepare packages
Computing target dependency graph and provisioning inputs
Create build description
Build description signature: f7c04d9d0c96970995447f915b52bd57
Build description path: /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/XCBuildData/f7c04d9d0c96970995447f915b52bd57-desc.xcbuild
note: Building targets in dependency order
/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods/Pods.xcodeproj: warning: The tvOS Simulator deployment target 'TVOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'DoubleConversion' from project 'Pods')
WriteAuxiliaryFile /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/DoubleConversion.build/DoubleConversion-all-target-headers.hmap (in target 'DoubleConversion' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
write-file /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/DoubleConversion.build/DoubleConversion-all-target-headers.hmap
/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods/Pods.xcodeproj: warning: The tvOS Simulator deployment target 'TVOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.1.99. (in target 'Folly' from project 'Pods')
Ld /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly/folly.framework/folly normal (in target 'Folly' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -target x86_64-apple-tvos10.0-simulator -dynamiclib -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVSimulator.platform/Developer/SDKs/AppleTVSimulator16.1.sdk -L/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/EagerLinkingTBDs -L/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/EagerLinkingTBDs -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/DoubleConversion -F/Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/glog -filelist /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/Folly.build/Objects-normal/x86_64/folly.LinkFileList -install_name @rpath/folly.framework/folly -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/Folly.build/Objects-normal/x86_64/folly_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -stdlib=libc++ -fobjc-arc -fobjc-link-runtime -lstdc++ -framework DoubleConversion -framework glog -framework Foundation -compatibility_version 1 -current_version 1 -Xlinker -dependency_info -Xlinker /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/Folly.build/Objects-normal/x86_64/folly_dependency_info.dat -o /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/Folly/folly.framework/folly
WriteAuxiliaryFile /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-jsinspector.build/jsinspector-all-target-headers.hmap (in target 'React-jsinspector' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
write-file /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-jsinspector.build/jsinspector-all-target-headers.hmap
WriteAuxiliaryFile /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-cxxreact.build/cxxreact-all-target-headers.hmap (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
write-file /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Intermediates.noindex/Pods.build/Debug-appletvsimulator/React-cxxreact.build/cxxreact-all-target-headers.hmap
CpHeader /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers/JsArgumentHelpers.h /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JsArgumentHelpers.h (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JsArgumentHelpers.h /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers
CpHeader /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers/MessageQueueThread.h /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/MessageQueueThread.h (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/MessageQueueThread.h /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers
CpHeader /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-appletvsimulator/React-cxxreact/cxxreact.framework/Headers/JSModulesUnbundle.h /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JSModulesUnbundle.h (in target 'React-cxxreact' from project 'Pods')
cd /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/Pods
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshamsaf/Projects/prj-sport1-app/node_modules/react-native-tvos/ReactCommon/cxxreact/JSModulesUnbundle.h /Users/bshamsaf/Projects/prj-sport1-app/platformBuilds/sport1_tvos/build/RNVAppTVOS/Build/Products/Debug-ap
at makeError (/Users/bshamsaf/Projects/prj-sport1-app/node_modules/rnv/node_modules/execa/lib/error.js:60:11)
at handlePromise (/Users/bshamsaf/Projects/prj-sport1-app/node_modules/rnv/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
`

@BitaShamsafar I am able to run androidtv just fine, in the main branch. The only differences that I see are the fact that you;re using node 16 and i'm using 16.20.2 and that main has rnv 0.32.0-alpha.49, not 37 like in your error. Did you try to update to 37 and that's when it started failing?

@mihaiblaga89
Thanks for checking and following up, yes I want to update react / reactNative. and this is when the problem pops up

Duplicate to https://github.com/flexn-io/renative/issues/1083

his issue has been fixed in 1.0.0-rc.18.


Fix build for Xcode 7.3

Use StaticString for assertion
Removed device agnostic tests
Updated travis to Xcode 7.3

w00t

:+1:


Added render all menu item

I added a menu item that will allow regenerating all templates at once.
I'm new to this codebase (and vs plugin's!), any feedback would be greatly appreciated.

Hi @Michael-Tajmajer-Emrsn, thanks for contributing!