fix: reverse cards render order to align element hierarchy with z-index

After migrating my app from JS-based navigation (@react-navigation/stack) to native navigation (@react-navigation/native-stack) I encountered the following visual glitch when navigating backwards on Android:
RN-Swiper Android zIndex Issue.webm
There seems to be an issue where the zIndex is disregarded in favor of the element render order during the animation.
I even found a similar bug in this open issue for react-native-screens:
https://github.com/software-mansion/react-native-screens/issues/1546
The only known "solution" is to align the element hierarchy with the zIndex by putting the last rendered/highest component at the bottom and vice-versa.
This PR simply reverses the mapped SwiperCards to render them in the correct hierarchy inside of the element tree without altering any indexes, animation or logic. Everything works the same and has no user- or developer-facing impact, besides fixing this visual glitch under the hood. I did not find any way to fix this outside of the library in the app's scope.
I believe this is not a niche issue, because it occurs in minimal setups with @react-navigation/native-stack. It maybe also affects apps using expo-router, because their default Stack navigator wraps that.
At the end, it seems pretty logical to me to have the cards in the same order inside the element tree as they are rendered on top of each other.

@bastiandev Can you attach a video of before and after the fix so I can debug the bug in detail?


Go documentation and readme

Fixes #10

We should have a better way for handling this generated HTML. A disjoint branch prehaps?

We could also just link to the HTML hosted at https://pkg.go.dev/

Sure, that would work as a temporary solution. Would you like to do another CL of would you like to update this one?


[vcpkg upgrade] When a upgrading process is interrupted, installed packages may be purged and must be manually reinstalled.

https://github.com/Microsoft/vcpkg/issues/4360

Duplicated to https://github.com/microsoft/vcpkg/issues/4360.

Duplicated to https://github.com/microsoft/vcpkg/issues/4360.


Xvideos. Unable to download - error 404

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

PASTE VERBOSE LOG HERE

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.xvideos.com/video55996109/runsammya_furry_antro_bunny_porno_with_sound_?pl=64479171&plname=furry', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 2022-10-10-git-f3b5277057-full_build-www.gyan.dev, ffprobe 2022-10-10-git-f3b5277057-full_build-www.gyan.dev
[debug] Proxy map: {}
[XVideos] 55996109: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\common.py", line 634, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\YoutubeDL.py", line 2288, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
Description

WRITE DESCRIPTION HERE
A video on the adult website, Xvideos, failed to fetch the video link. There are other times it may spew out error

Duplicate of #30271, fixed in git master. See also #30707.

Duplicate of #30271, fixed in git master. See also #30707.

I got it under control. Thanks


Add wait for deploy()

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

!verified


Use HttpAbstractions StreamCopy

Part 2 of https://github.com/aspnet/HttpAbstractions/issues/528
@Tratcher

:shipit:

Wait for coherence?

I could, but why for?

@BrennanConroy mere mortals trying to build, reduce our breakages. It should be quick anyways. We should optimize for not breaking our repos. There's no need to rush this in, coherence should pass very quickly.

Should I push part 1 though?

Yes


feat: add upcoming events page that displays all the upcoming events

This PR resolves #92 by displaying all the upcoming events in a single dedicated page.
Output:

It's look better. I have done for #98  as well.


feat: Add a loom implementation for event-listener

The loom tests aren't particularly useful yet, but the crate compiles and runs under loom now.
Note: This crate does not currently compile under loom without std because concurrent-queue does not compile with that combination (can't find spin_loop).
closes #23

I added Loom to the CI in https://github.com/smol-rs/concurrent-queue/pull/62. It looks like it works. Maybe it's the optional feature flag that's gumming it up.

I think crossbeam does this right. See here:
https://github.com/crossbeam-rs/crossbeam/blob/9e8596105bc9a6b343918b6ad1c9656dc24dc4f9/crossbeam-epoch/Cargo.toml#L30-L34
and here:
https://github.com/crossbeam-rs/crossbeam/blob/9e8596105bc9a6b343918b6ad1c9656dc24dc4f9/crossbeam-epoch/Cargo.toml#L39-L44

I'm surprised concurrent-queue Loom tests are failing, but I guess that's due to loom not being checked in CI there.

To be clear, it's not that the concurrent-queue loom tests are failing, or even that concurrent-queue can't build under loom. This PR for event listener correctly builds concurrent-queue under loom and runs tests against concurrent-queue loom.
The issue is this specific scenario for concurrent-queue, which may or may not even matter: RUSTFLAGS="--cfg=loom" cargo build --no-default-features --features loom (in concurrent-queue)


Can you add a screenshot of the state machine emulator GUI?

This emulator: https://github.com/GitJer/Some_RPI-Pico_stuff/tree/main/state_machine_emulator
Thanks in advance!

Very good advice! Done :)

Wow, thanks for the quick reply. It looks very complex!


DateTimeOffset support

Todos

[ ] test IsEqualTo With OFFset varying on ignored fields ? Matters mostly for minutes ... India has different half hour time zones
[ ] test IsMatch With OFFset varying on ignored fields
[ ] Fix examples and descriptions
[ ] Fix .ComparingTo(other, "same time minute", "different minute") with "Same time ignoring xxx"


Ubuntu Versions

Morning all
I'm building a production server for a wagtail application.  It's easier all round for us if the development machine that we install via vagrant on our local machines, is the same as the production server.
I'm starting to build the server now and noticed this at the top of the screen when I logged in.
"Your current Hardware Enablement Stack (HWE) is going out of support
on 08/07/14.  After this date security updates for critical parts (kernel
and graphics stack) of your system will no longer be available."
I'm using the same version that your using in the wagtaildemo system.
ubuntu12.04LTS 32 bit
config.vm.box_url = "http://downloads.torchbox.com/wagtail-base-v0.1.box"
So, I can't use that in production.
I've tried using ubuntu14.04LTS in Development, but the python modules you need to run wagtaildemo on that version of ubuntu don't all load, and we went through a process of adding them into our requirements.txt, but it seemed to be a never ending process so in the end we gave up, and went back to the proscribed ubuntu12 version.
Is there any chance you could create a vm.box_url using Ubuntu14LTS 64 bit so we can use that in development, and in production?
I'm happy to assist in any way if I can.
If there already is one and I'm being a doughnut sincere apologies.

We've updated the Wagtail base box to Ubuntu 14.04 32 bit.
Closing ticket as this looks like a support query (these have been moved to the Google group)


libopae: add Metrics api

Changes:
- Added metrics API
- Added test cases
- Support MCP/ DCP cards

Unit tests for the sample app?


Support screen connect and disconnect

If a screen is connected, a new grid+mode should be added to it. If a screen is disconnected, the grid on it should be destroyed and the panes in that grid should be stashed.

Since this will most likely require display stashing/applying (what are we going to do with windows when their screen is disconnected?) I think we can live with the MVP not supporting this.


& doesn't work after a block

See https://github.com/styled-components/babel-plugin-styled-components/issues/207 - I think
.foo{width:5em}&.bar{width:3em}

should be equivalent to
.foo{
  width:5em;
}
&.bar{
  width:3em;
}

but it seems that that's not the case

This works for me on stylis.js.org. Can you replicate this outside of styled-components.

Hmm I'll go deeper. In any case I can't test on stylis.js.org because unpkg's CloudFlare returns 500 for<EMAIL_ADDRESS>

I'll close for now.


Internal Server Error returned from GET 1.5/servers/{{ID}}/configfiles/ats

I'm submitting a ...

[x] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[x] Traffic Ops
[ ] Traffic Ops ORT
[x] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

Perform a /GET 1.5/servers/170/configfiles/ats
ERROR: api.go:201: 2020-06-15T21:03:15.365421062Z: <IP_ADDRESS>:35220 GetConfigMetaData getting server info: querying server info: sql: Scan error on column index 7, name "tcp_port": converting NULL to int is unsupported
Expected / new behavior:

User should able to view Config Files of the Servers
Minimal reproduction of the problem with instructions:

Anything else:

Getting configs from the API is close to being phased out, so this might not get fixed and the functionality could just be removed instead.

actually, I take that back. The dsId issue has a different root cause.

this works fine in TC 4.1 and this endpoint has been removed in TC 5.0 so closing this...


[Bug]: Jest leaks memory in ESM mode

Version
29.7.0
Steps to reproduce
clone the repository at: https://github.com/Havunen/jest-memory-leak
run npm install
run npm test
You should see the heap memory increasing over time until the nodejs process crashes.
Expected behavior
The nodejs process should be able to clean the memory and preferably allocate as little as possible
Actual behavior
The node js process crashes
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7018A3CEF node::SetCppgcReference+15695
 2: 00007FF70181E606 EVP_MD_meth_get_input_blocksize+78566
 3: 00007FF7018203F1 EVP_MD_meth_get_input_blocksize+86225
 4: 00007FF70228A191 v8::Isolate::ReportExternalAllocationLimitReached+65
 5: 00007FF702273928 v8::Function::Experimental_IsNopFunction+1336
 6: 00007FF7020D5190 v8::Platform::SystemClockTimeMillis+659552
 7: 00007FF7020D2218 v8::Platform::SystemClockTimeMillis+647400
 8: 00007FF7020E752A v8::Platform::SystemClockTimeMillis+734202
 9: 00007FF7020E7DA7 v8::Platform::SystemClockTimeMillis+736375
10: 00007FF7020F09DE v8::Platform::SystemClockTimeMillis+772270
11: 00007FF702101356 v8::Platform::SystemClockTimeMillis+840230
12: 00007FF702105F28 v8::Platform::SystemClockTimeMillis+859640
13: 00007FF701E7D67A v8::base::Thread::StartSynchronously+372122
14: 00007FF701FC15B0 v8::ObjectTemplate::IsImmutableProto+13152
15: 00007FF7021EA0C9 v8::SharedValueConveyor::SharedValueConveyor+62825
16: 00007FF7021EA3C8 v8::SharedValueConveyor::SharedValueConveyor+63592
17: 00007FF7021E4624 v8::SharedValueConveyor::SharedValueConveyor+39620
18: 00007FF7021E455A v8::SharedValueConveyor::SharedValueConveyor+39418
19: 00007FF70226E84D v8::ScriptCompiler::CompileUnboundInternal+1069
20: 00007FF70226EB21 v8::ScriptCompiler::CompileUnboundScript+161
21: 00007FF70182E54B node::OnFatalError+57675
22: 00007FF70224056E v8::SharedValueConveyor::SharedValueConveyor+416270
23: 00007FF70223FE17 v8::SharedValueConveyor::SharedValueConveyor+414391
24: 00007FF702240444 v8::SharedValueConveyor::SharedValueConveyor+415972
25: 00007FF7022402A0 v8::SharedValueConveyor::SharedValueConveyor+415552
26: 00007FF70233AC3E v8::PropertyDescriptor::writable+674286
27: 00007FF7022A99B3 v8::PropertyDescriptor::writable+79715
28: 00007FF682572942

Additional context
This is continuation from here: https://github.com/jestjs/jest/pull/12205#issuecomment-1749127216
Environment
node v20.8.0
windows 11 ver. 2261
npm 9.6.4
Jest 29.7

Here is a log:
><EMAIL_ADDRESS>test
> cross-env NODE_OPTIONS=--max-old-space-size=128 node --experimental-vm-modules ./node_modules/jest/bin/jest.js --config=jest.config.js --runInBand --logHeapUsage --no-watchman --ci

(node:28376) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 PASS  tests/test (9).spec.spec.js (37 MB heap size)
 PASS  tests/test (80).spec.spec.js (42 MB heap size)
 PASS  tests/test (8).spec.spec.js (35 MB heap size)
 PASS  tests/test (79).spec.spec.js (45 MB heap size)
 PASS  tests/test (78).spec.spec.js (44 MB heap size)
 PASS  tests/test (77).spec.spec.js (46 MB heap size)
 PASS  tests/test (76).spec.spec.js (46 MB heap size)
 PASS  tests/test (75).spec.spec.js (55 MB heap size)
 PASS  tests/test (74).spec.spec.js (55 MB heap size)
 PASS  tests/test (73).spec.spec.js (59 MB heap size)
 PASS  tests/test (72).spec.spec.js (56 MB heap size)
 PASS  tests/test (71).spec.spec.js (65 MB heap size)
 PASS  tests/test (70).spec.spec.js (65 MB heap size)
 PASS  tests/test (7).spec.spec.js (69 MB heap size)
 PASS  tests/test (69).spec.spec.js (70 MB heap size)
 PASS  tests/test (68).spec.spec.js (68 MB heap size)
 PASS  tests/test (66).spec.spec.js (77 MB heap size)
 PASS  tests/test (67).spec.spec.js (77 MB heap size)
 PASS  tests/test (65).spec.spec.js (80 MB heap size)
 PASS  tests/test (64).spec.spec.js (81 MB heap size)
 PASS  tests/test (63).spec.spec.js (90 MB heap size)
 PASS  tests/test (43).spec.spec.js (82 MB heap size)
 PASS  tests/test (61).spec.spec.js (91 MB heap size)
 PASS  tests/test (62).spec.spec.js (91 MB heap size)
 PASS  tests/test (60).spec.spec.js (95 MB heap size)
 PASS  tests/test (6).spec.spec.js (91 MB heap size)
 PASS  tests/test (59).spec.spec.js (100 MB heap size)
 PASS  tests/test (58).spec.spec.js (101 MB heap size)
 PASS  tests/test (57).spec.spec.js (104 MB heap size)
 PASS  tests/test (56).spec.spec.js (99 MB heap size)
 PASS  tests/test (55).spec.spec.js (100 MB heap size)
 PASS  tests/test (54).spec.spec.js (95 MB heap size)
 PASS  tests/test (53).spec.spec.js (102 MB heap size)
 PASS  tests/test (52).spec.spec.js (99 MB heap size)
 PASS  tests/test (50).spec.spec.js (103 MB heap size)
 PASS  tests/test (51).spec.spec.js (101 MB heap size)
 PASS  tests/test (5).spec.spec.js (107 MB heap size)
 PASS  tests/test (49).spec.spec.js (106 MB heap size)
 PASS  tests/test (48).spec.spec.js (111 MB heap size)
 PASS  tests/test (47).spec.spec.js (111 MB heap size)
 PASS  tests/test (45).spec.spec.js (113 MB heap size)
 PASS  tests/test (46).spec.spec.js (118 MB heap size)
 PASS  tests/test (44).spec.spec.js (116 MB heap size)
 PASS  tests/test (42).spec.spec.js (117 MB heap size)

 RUNS  tests/test (41).spec.spec.js

<--- Last few GCs --->

[28376:000001E017CEF240]     6150 ms: Mark-Compact (reduce) 117.4 (130.8) -> 116.8 (131.3) MB, 25.51 / 0.00 ms  (average mu = 0.609, current mu = 0.567) allocation failure; scavenge might not succeed
[28376:000001E017CEF240]     6189 ms: Mark-Compact (reduce) 118.0 (131.3) -> 116.8 (131.8) MB, 24.29 / 0.01 ms  (average mu = 0.526, current mu = 0.375) allocation failure; scavenge might not succeed

tested with nodejs v21.0.0-nightly202310041a839f388e (06-Oct-2023 11:00) and it is still an issue.

@Havunen this does not reproduce if I remove the importModuleDynamically option from createScriptFromCode in jest-runtime. So I'm guessing it's still related to the broken code caching (i.e. nr 4 here https://github.com/jestjs/jest/pull/12205#issuecomment-1749113564)

I commented out all importModuleDynamically callbacks it still does not work using node v21.0.0-nightly20231008fce8fbadcd.
I added more tests and bigger JSON to the example so its more obvious now

log:
cross-env NODE_OPTIONS=--max-old-space-size=128 node --experimental-vm-modules ./node_modules/jest/bin/jest.js --config=jest.config.js --runInBand --logHeapUsage --no-watchman --ci

(node:17340) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 PASS  tests/test (94).spec.js (34 MB heap size)
 PASS  tests/test (90).spec.js (50 MB heap size)
 PASS  tests/test (234).spec.js (53 MB heap size)
 PASS  tests/test (89).spec.js (61 MB heap size)
 PASS  tests/test (9).spec.js (61 MB heap size)
 PASS  tests/test (92).spec.js (69 MB heap size)
 PASS  tests/test (91).spec.js (78 MB heap size)
 PASS  tests/test (87).spec.js (74 MB heap size)
 PASS  tests/test (98).spec.js (82 MB heap size)
 PASS  tests/test (97).spec.js (91 MB heap size)
 PASS  tests/test (50).spec.js (87 MB heap size)
 PASS  tests/test (93).spec.js (95 MB heap size)
 PASS  tests/test (192).spec.js (95 MB heap size)
 PASS  tests/test (96).spec.js (103 MB heap size)
 PASS  tests/test (86).spec.js (100 MB heap size)
 PASS  tests/test (129).spec.js (107 MB heap size)
 PASS  tests/test (21).spec.js (111 MB heap size)
 PASS  tests/test (77).spec.js (116 MB heap size)
 PASS  tests/test (186).spec.js (116 MB heap size)
 PASS  tests/test (209).spec.js (121 MB heap size)
 PASS  tests/test (57).spec.js (125 MB heap size)

 RUNS  tests/test (56).spec.js

<--- Last few GCs --->

[17340:0000022DDED70080]     2645 ms: Mark-Compact (reduce) 126.9 (130.3) -> 126.9 (131.1) MB, 52.91 / 0.00 ms  (average mu = 0.347, current mu = 0.071) allocation failure; scavenge might not succeed
[17340:0000022DDED70080]     2694 ms: Mark-Compact (reduce) 127.9 (131.1) -> 127.9 (132.1) MB, 44.15 / 0.00 ms  (average mu = 0.235, current mu = 0.088) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF61DFA9A7F node::SetCppgcReference+13775
 2: 00007FF61DF23B06 DSA_meth_get_flags+76070
 3: 00007FF61DF25941 DSA_meth_get_flags+83809
 4: 00007FF61E984111 v8::Isolate::ReportExternalAllocationLimitReached+65
 5: 00007FF61E96D9B8 v8::Function::Experimental_IsNopFunction+1336
 6: 00007FF61E7D5F90 v8::StackTrace::GetFrameCount+74720
 7: 00007FF61E7D2D8D v8::StackTrace::GetFrameCount+61917
 8: 00007FF61E7E800D v8::StackTrace::GetFrameCount+148573
 9: 00007FF61E7E8892 v8::StackTrace::GetFrameCount+150754
10: 00007FF61E7F166E v8::StackTrace::GetFrameCount+187070
11: 00007FF61E7F976A v8::StackTrace::GetFrameCount+220090
12: 00007FF61E700A5A v8::base::time_internal::TimeBase<v8::base::ThreadTicks>::operator!=+53770
13: 00007FF61E6FD5AD v8::base::time_internal::TimeBase<v8::base::ThreadTicks>::operator!=+40285
14: 00007FF61E702C0F v8::base::time_internal::TimeBase<v8::base::ThreadTicks>::operator!=+62399
15: 00007FF61E913AD8 v8::SharedValueConveyor::SharedValueConveyor+256680
16: 00007FF61E913CF0 v8::SharedValueConveyor::SharedValueConveyor+257216
17: 00007FF61EA355BE v8::PropertyDescriptor::writable+676814
18: 0000022DDF0633E5

All importModuleDynamically removed from the whole code base

I also removed all initializeImportMeta callbacks and it still reproduces

I have reproduced the issue using nodejs and javascript only, and also found a work around.
Having a shared context between the modules seems to leak the memory. However setting the shared context null manually after function execution it fixes the memory leak. Setting the variable null in JS is non-sense (ref: https://github.com/Havunen/nodejs-memory-leak/blob/main/test.js#L45-L46 ) because it goes out of scope and should be GC'd but it does not seem to happen. So its definetly a nodejs / v8 bug
https://github.com/Havunen/nodejs-memory-leak

We do set it to null manually in the node environment, FWIW.
https://github.com/jestjs/jest/blob/00ef0ed0a03764f24ff568bc87dcc1c203d28625/packages/jest-environment-node/src/index.ts#L200
Not so in the JSDOM env, but the reproduction in this issue uses the Node env.
Might be we keep a reference without meaning to within the runtime of course

yeah but it is not set null in the call site not sure if it needs to be nulled everywhere or how it works in low level

After testing a bit more it seems setting the context to null does not really fix the issue :/

Just curious, but does removing cross-env and using node directly resolve the leak? Also does cross-env inject variables/flags into node?
Noticed it's in maintenance only mode so I'm curious if nodejs 20 is supported.

Workaround for this is to do the following. Whatever your --max-old-space-size=128 value is...add the same value following to jest.config.js or as a flag --workerIdleMemoryLimit=128MB.
jest.config.js that works with your repo
diff --git a/jest.config.js b/jest.config.js
index 99cbe34..6f28936 100644
--- a/jest.config.js
+++ b/jest.config.js
@@ -10,6 +10,7 @@ export default {
   transformIgnorePatterns: [
     '/node_modules/',
   ],
+  workerIdleMemoryLimit: '128MB',
   collectCoverage: false,
   coverageReporters: [],
   moduleDirectories: ['node_modules']

Regarding workerIdleMemoryLimit, I'm curious if jest should be capping itself directly with that workerIdleMemoryLimit so it can never exceed v8 heap size. Is there a reason to let it exceed the max-old-space-size provided to nodejs?
CC: @SimenB thoughts?


Chorby Soul's Soulscream

Chorby Soul has a soul value of 1777, which breaks the code for soulscream generation. This is because the equation for soulscream attempts to calculate 10^-x with increasing x up to the soul value. This causes all kinds of problems with floating point numbers, since even with double precision you only have ~15 bits of precision.
To top this off, Javascript doesn't really have a standard for float rounding or precision. The Soulscream displays differently on the blaseball site depending on browser, OS, and device.
I've got 2 potential fixes in my head:

Catch the divide-by-zero Exception when it gets too big and insert undefined like the javascript does. This scream will be different than what's on the site but at least it wont crash when trying to generate it.
Limit the length of the soulscream. Testing shows the data matches for soul iterations of 23 and lower (or 253 characters). This scream will be much different than the site, but any additional characters we generate would be incorrect.

i like matching the javascript with the undefined
it's kinda funny how the soul scream is different everywhere


When new Xcode build system is used, Xcode build fails to download third-party dependencies

Workaround (edit by @hramos)
You may work around this by manually installing third party dependencies into your project. The following steps are based on the workaround provided by @lyon007 in #14382.

 rm -rf node_modules/ && yarn cache clean && yarn install  and  rm -rf ~/.rncache
 cd node_modules/react-native/scripts
./ios-install-third-party.sh
If your network is slow, you can download the packages separately and move them to the rncache  folder
1. folly-2<IP_ADDRESS>
2.  double-conversion-1.1.5
3.  glog-0.3.5
4.  boost_1_63_0
cd <Your-Project-Folder>/node_modules/react-native/third-party/glog-0.3.5
 ../../scripts/ios-configure-glog.sh
Xcode Clean & Build

Original issue

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 103.23 MB / 4.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.9.0 - ~/.nvm/versions/node/v10.9.0/bin/node
npm: 6.4.0 - ~/.nvm/versions/node/v10.9.0/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
IDEs:
Xcode: 10.0/10L221o - /usr/bin/xcodebuild
npmPackages:
react: 16.4.1 => 16.4.1
react-native: 0.56.0 => 0.56.0
npmGlobalPackages:
react-native-cli: 2.0.1
Description
First build request after yarn or npm install does not succeed due to apparent timing of download, extract, and compile actions. Subsequent builds succeed until node_modules removed and yarn or npm install run again.
Similar to this closed issue:
https://github.com/facebook/react-native/issues/18982
This is not a problem in the local development environment as the work around is to simply rerun the build command. However, with remote build environments (Buddybuild, App Center, etc)  this becomes problematic.
Reproducible Demo
Follow these steps:
0 - configure environment as per react-native info above
1 - from shell - react-native init DoubleTrouble
2 - from shell - cd DoubleTrouble
3 - from shell - react-native run-ios
Here is the tail end of output I received:
** BUILD FAILED **
The following build commands failed:
CompileC /Users/mcclen/Developer/DoubleTrouble/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/double-conversion.build/Objects-normal/x86_64/strtod.o /Users/mcclen/Developer/DoubleTrouble/node_modules/react-native/third-party/double-conversion-1.1.5/src/strtod.cc normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler

(1 failure)
Installing build/Build/Products/Debug-iphonesimulator/DoubleTrouble.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/DoubleTrouble.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

I'm having the same problem when trying to build on Bitrise using Xcode 10.0.x stack.

@rodrigopk were you able to fix it?

Same issue here. Any update?

None. Have to admit some confusion as the reproducible nature would seem to apply to everyone.
I have not had time to dig into it, I suspect that the caching and copying activities for these assets is performed asynchronously with the compile step. Perhaps some sort of synchronization between the activities has broken or doesn't exist.

I'm giving up on trying to get Xcode 10 to work…third party dependencies (double-conversion…) cause build errors on BuddyBuild. This seems to be a recurring theme with these massively-dependent open source platforms. 😑

I got the same issue

same issue in Xcode 10

I'm also experiencing this. I have tried many of the posts with high upvotes on this issue (https://github.com/facebook/react-native/issues/14382) and have still not reached a solution. Going to try re-install old XCode version and copy iOS 12 support files from beta.

Ok, I think I have a temporary fix to get React Native to work with Xcode 10—change the shared project settings (or shared workspace settings if you're also using Cocoapods) to use the "Legacy Build System". File->Project/Workspace Settings->Build System: Legacy Build System.
It's (not really) surprising that Facebook hasn't fixed in the months that have passed since WWDC18. Good luck, everyone.

FWIW, I just upgraded a rather complicated old React Native project to 0.57.0 and set it up using CocoaPods and everything builds fine with Xcode 10. See below for my environment details...

  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
      Memory: 717.64 MB / 32.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.9.0 - ~/.nvm/versions/node/v10.9.0/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v10.9.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
    IDEs:
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.5.0 => 16.5.0
      react-native: 0.57.0 => 0.57.0
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1

Curious. I followed Alex’s suggestion about changing the Workspace setting Build System to Legacy Build System and that worked for me. I’m now looking at my React Native Environment Info to compare with Paul’s for differences. The first I note is node and npm as well as I did not use CRNA.

On Sep 18, 2018, at 6:00 PM, Paul Mestemaker<EMAIL_ADDRESS>wrote:
FWIW, I just upgraded a rather complicated old React Native project to 0.57.0 and set it up using CocoaPods and everything builds fine with Xcode 10. See below for my environment details...
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 717.64 MB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.9.0 - ~/.nvm/versions/node/v10.9.0/bin/node
Yarn: 1.9.4 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.9.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
IDEs:
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: 16.5.0 => 16.5.0
react-native: 0.57.0 => 0.57.0
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/20774#issuecomment-422609420, or mute the thread https://github.com/notifications/unsubscribe-auth/AAP7XwBfK9WORikYIKhbTdfqkVl-223wks5ucZcVgaJpZM4WGsiv.

I have create-react-native-app installed, but I did not use it for this project. I used react-native init to create the project and then manually migrated the source files from a much older version of RN.
I'm curious if you upgrade from 0.56.0 to 0.57.0, if that will solve your problem without the Legacy Build System workaround.

I failed to note that between the initial report of the issue and now I have upgraded to 0.57.0 and that did not solve the problem. I’ve also upgrade node and npm and that has not resolved the issue either. So far for me it is the Legacy Build System setting that seems to fix the build issue. Makes sense as I had no problem with Xcode 9.4.1.
My question now is what is the difference between the two build systems and is the difference material?

On Sep 19, 2018, at 12:19 AM, Paul Mestemaker<EMAIL_ADDRESS>wrote:
I have create-react-native-app installed, but I did not use it for this project. I used react-native init to create the project and then manually migrated the source files from a much older version of RN.
I'm curious if you upgrade from 0.56.0 to 0.57.0, if that will solve your problem without the Legacy Build System workaround.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/20774#issuecomment-422684998, or mute the thread https://github.com/notifications/unsubscribe-auth/AAP7X9JOhep39fDihiJ0GK2WBINqhoQFks5uce_mgaJpZM4WGsiv.

I also tried to upgrade to react-native 0.57.0 but that didnt solve this issue. I ended up downgrading Xcode to 9.4.1 and installing the iOS 12 device support files that you can find on this repo:
https://github.com/Yatko/iOS-device-support-files

The build failure I’m getting is related to the third-party libraries upon which react-native is dependent. As near as I can tell the build steps for these require the download via curl into a cache directory (~/.rncache ?), unpacking and copying into the RN projects’s node modules subdirectory for react-native and finally compilation.
It appears the “new” build system in Xcode does not have information to properly sequence the dependent steps, such that the compile step is attempted before the files are moved into node modules. On a local machine, on subsequent builds, this “race” condition does not occur again and the compilation succeeds as the “state” of the download, unpack and copy seems to be preserved. On remote build systems, the state of the download, unpack and copy are not preserved and the compilation fails every time.
Two questions I have: is there a material difference between the new and legacy build system (performance, parallelism, what ???) and where in the build configuration can the new build system be told how to properly sequence the build steps for these libraries?

On Sep 19, 2018, at 8:37 AM, Pedro Gomes<EMAIL_ADDRESS>wrote:
I also tried to upgrade to react-native 0.57.0 but that didnt solve this issue. I ended up downgrading Xcode to 9.4.1 and installing the iOS 12 device support files that you can find on this repo:
https://github.com/Yatko/iOS-device-support-files https://github.com/Yatko/iOS-device-support-files
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/20774#issuecomment-422849301, or mute the thread https://github.com/notifications/unsubscribe-auth/AAP7Xz-2Sz0dMtVuOaiessNZ0gwuolbqks5ucmTUgaJpZM4WGsiv.

We ran into the same problem and fixed it by adding this as a postinstall step to our package.json:
cd node_modules/react-native/React/..; exec ./scripts/ios-install-third-party.sh

This will run the script in the correct directory which will make it pass later in the build process.

Only viable solution that persists across ci builds seems to be using legacy build system

@hramos
Do you have any timeline when React native will be fully supporting xcode 10? Lots off issues are happening. Clients are just waiting for apps to be shipped and we are sitting fingers crossed to get updates :(

There's no single fix that will provide full support for Xcode 10. We are tracking all known issues so far in https://github.com/facebook/react-native/issues/19573. For each of those, the community will need to provide a pull request with a fix. Ideally, we'd get PRs to fix all of these in time for the 0.58 release cut.
If you're blocked by Xcode 10 issues, the best course of action is to make sure the issue is logged in https://github.com/facebook/react-native/issues/19573, followed by sending a PR to fix the issue.

My post tracking Xcode 10 related issues was created on June 5, the day of the WWDC 2018 Keynote: https://github.com/facebook/react-native/issues/19573, by the way. That's still a year too late, as the new build system was introduced during WWDC 2017, but it's hardly a new issue in this tracker. As the developer tooling is updated every year, we depend on volunteers using the betas to surface any issues and fixes in time for the general release.

use rhdeck/react-native-fix-xcode-10 and link libfishhook.a can make it working, but when i rebuild, crash again.

Workaround in OP worked for me but with some little adjustments in steps 2 and 3:
2. cd node_modules/react-native
3. ./scripts/ios-install-third-party.sh
Oherwise, it would create the third-party folder inside scripts folder, not in react-native (which is the right one).
Also, I had to follow this to correctly link to libfishhook.a file in RCTWebSocket library.
And a final thing (couldn't verify this is required, maybe my dependencies were outdated) was running a pod install inside ios folder to update dependencies.

iOS Build Issues?
Try these:
rm -rf node_modules
npm install
Close Xcode.
Open Terminal, go to your project's root folder and do:
cd node_modules/react-native/third-party/glog-0.3.4/
Run the configure script:
./configure
Fix reference to libfishhook.a in RCTWebSocket
https://github.com/facebook/react-native/issues/19569#issuecomment-394869470
Still not working?
Try this: https://github.com/facebook/react-native/issues/21168#issuecomment-422525950

Android problems?
Try these:
rm -rf android/.gradle
rm -rf android/build
rm -rf $TMPDIR/react-* && watchman watch-del-all && npm cache verify
rm -rf $TMPDIR/haste-map-react-native-packager-*

In fact, you only need to make sure that there is a third-party folder in node_modules/react-native, and that there are four unpacked packages in the third-party.

This worked for me
$ cd node_modules/react-native/scripts && ./ios-install-third-party.sh && cd ../../../
$ cd node_modules/react-native/third-party/glog-0.3.5/ && ../../scripts/ios-configure-glog.sh && cd ../../../../

https://github.com/facebook/react-native/issues/21168#issuecomment-422431294

This worked for me
$ cd node_modules/react-native/scripts && ./ios-install-third-party.sh && cd ../../../
$ cd node_modules/react-native/third-party/glog-0.3.5/ && ../../scripts/ios-configure-glog.sh && cd ../../../../

#21168 (comment)

This does fix it however it breaks my Android build. Now to update my app I first have to do fastlane android beta then execute these commands. Not an ideal solution.

@nbokmans true
But since i want my app on latest version of React Native, i am installing node_modules twice ti build for iOS and Android with above hack

No matter what I do, I haven't been able to get Android to work. Constantly getting:
org.gradle.api.UncheckedIOException: Failed to capture snapshot of input files for task ':app:bundleReleaseJsAndAssets' property '$1' during up-to-date check. Caused by: org.gradle.api.GradleException: Could not list contents of '/Users/.../.../.../.../third-party/glog-0.3.5/test-driver'. Couldn't follow symbolic link.
I have tried cleaning, rm -rf node_modules, running ios-install-third-party.sh. I even found the "missing" symbolic link to be test-driver so I downloaded autoconf and automake so that I could link it manually. Literally NOTHING is working. Anyone have any other ideas for me?

@zsaraf I've been working around this by removing the symbolic link completely which at least gets the Android build working

No matter what I do, I haven't been able to get Android to work. Constantly getting:
org.gradle.api.UncheckedIOException: Failed to capture snapshot of input files for task ':app:bundleReleaseJsAndAssets' property '$1' during up-to-date check. Caused by: org.gradle.api.GradleException: Could not list contents of '/Users/.../.../.../.../third-party/glog-0.3.5/test-driver'. Couldn't follow symbolic link.
I have tried cleaning, rm -rf node_modules, running ios-install-third-party.sh. I even found the "missing" symbolic link to be test-driver so I edited autoconf and automake so that I could link it manually. Literally NOTHING is working. Anyone have any other ideas for me?

@zsaraf
Did you try these:
rm -rf android/.gradle
rm -rf android/build
rm -rf $TMPDIR/react-* && watchman watch-del-all && npm cache verify
rm -rf $TMPDIR/haste-map-react-native-packager-*

rm -rf node_modules
npm cache verify
npm install
rm -rf ~/.rncache
cd node_modules/react-native
./scripts/ios-install-third-party.sh
cd -
cd node_modules/react-native/third-party/glog-0.3.4 # brittle as fudge
./configure
cd -
npm run ios:release

did not work for me, building on Bitrise. upgrading to 0.57 isn't an option for my team

Dropping my Xcode to Legacy Build did the trick for me. Both Android and iOS build fine.

Okay much to the chagrin of my team I convinced them that there were no breaking changes in 0.57 and bumped.
rm -rf node_modules
npm cache verify
npm install
rm -rf ~/.rncache
cd node_modules/react-native
./scripts/ios-install-third-party.sh
cd -
cd node_modules/react-native/third-party/glog-0.3.5
./configure
cd -
npm run ios:release

still results in
Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Release-iphonesimulator/MyCool.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

@chaim1221 did you try using the legacy build system in Xcode?

I'd say that would help but I'm trying to build outside of XCode.

here's what I get with that. I'm not 100% certain it's related, in fact I think this means it takes care of the CFBundleIdentifier issue.

Nevertheless it has no effect on trying to build from the command line. Running that script in the scripts directory remains the only way to make that work. I am considering adding a post-build step per 0ff.

Running the postinstall script to unpack and configure the third party packages and using the new build system also works for me. In fact, I have switched to that workaround.

Yes. For both 0.56.1 and 0.57.1 that gets me around the error. I modified it a bit:
    "postinstall": "cd node_modules/react-native; exec ./scripts/ios-install-third-party.sh; cd third-party/glog-0.3.4; exec ./configure; cd ../../../.."

Clearly, if you're using the Heinz 57 variety, you want the glog-0.3.5 directory.

Yeah, unfortunately, this broke my build for a physical device since glog configure.h is now geared for x86 and not arm. There is yet another workaround for this, but it requires more monkey patching. I just decided to drop back to the legacy build system which works for both simulator and device through Xcode

repost from: https://github.com/facebook/react-native/issues/19529#issuecomment-427209573
I wrote something a bit cleaner for my purposes and installed the fix within the node_modules/react-native package. Normally I would prefer not to modify a node_module directly, but under this circumsance I felt that it was worth it and allowed us to add a simple script in our yarn start script and we get a clean run from a fresh clone.
npm install or yarn - install packages
cd node_modules/react-native - go to node modules directory
scripts/ios-install-third-party.sh- install @ node_modules/react-native/third-party
cd third-party - go to newly created third party directory
cd glog-0.3.x   - ls -la to find your directory version number or just use tab to auto-complete)
./configure - run setup
cd ../../../../- change back to your project directory
react-native run-ios or react-native run-android - deploy
(maybe its even better inside the node_modules/react-native/node_modules directory?)

I also get this issue which started happening after running the solution in #21490, but instead of messing with Xcode or any third party packages, I'll run react-native run-ios again and it works fine.
So, repeating my steps (after removing node_modules folder):

yarn install
yarn run-ios = react-native run-ios --simulator \"iPhone XS\"
Get errors described in original issue
yarn run-ios = react-native run-ios --simulator \"iPhone XS\"
APP RUNS!

So strange to me, but I have yet to figure out why this work for me.

@mathewmorris, I think this was described as a workaround, if not here, at least somewhere else. Yes, running compile a second time works most of the time since the third party packages would have been downloaded and configured. The first run fails due to Xcode's new build system which I think parallizes things a lot and might not catch the third party packages in time. Reverting to the legacy build system also works.

@ujwal-setlur Changing back to legacy build system is not an option for people who rely on Fastlane or other automatic build tools which don't care about your XCode settings. It's not a solution.

@nbokmans fair enough, but then none of workarounds suggested is a solution. Some work for some, others don't. This has to be fixed in the react-native build system.

@ujwal-setlur Agreed. Just need to let FB take care of it. Expected with all the new things coming out right now.

The original issue mentions a command failing when accessing the app's Info.plist. In the new build system, if you need to access Info.plist in a build script, it must be listed as an input dependency.
I have a script that modifies the app's plist and I had to add Info.plist file as an "input file" for the script's build phase so it would run in the right order (see https://openradar.appspot.com/44422906 for more details):

I'm still getting errors like "Build input file cannot be found: '/.../myapp/node_modules/react-native/third-party/double-conversion-1.1.6/src/strtod.cc'" but I wonder if something similar is required.

We have the same problem here, and doesn't seems to be related with the version of the Xcode, because it's failing also in a machine with 9.2
Tested in a Mac with High Sierra
Xcode: 10.0 10A255
And also tested in a Mac with Sierra
Xcode: Version 9.2 (9C40b)
When I run the iOS app I get
** BUILD SUCCEEDED **

Installing build/Build/Products/Debug-iphonesimulator/myapp.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/myapp.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

My workaround was working until Friday. No idea what happened but it's not working anymore.

There are additional solutions here (apparently this has been cropping up for awhile); one is xcode-related, one is workspace-related. There also seems to be some confusion about where info.plist should land, but I checked info.plist and it does reference CFBundleIdentifier, and the build works sometimes, so I think the error message is just misleading.
works with workaround (described multiple times above):
repo (master ✔) ᐅ xcodebuild -version
Xcode 10.0
Build version 10A255

and
    "react": "^16.5.2",
    "react-native": "^0.56.1"

react-native-cli: 2.0.1
and Simulator set to iPhone 8, iOS 12.
What wasn't working (until the second I almost pressed "Comment", then a build worked):
Xcode 10.0.x, on macOS 10.13 (High Sierra) on app.bitrise.io
Here's what's installed:
https://github.com/bitrise-io/bitrise.io/blob/master/system_reports/osx-xcode-10.0.x.log
This is so weird.
It's working again, and all I did was put things back the way they were when it was failing.

I was able to use the workaround suggested by @NNaidoo, however replacing the "./configure" part with the following:
../../scripts/ios-configure-glog.sh

What did the trick for me, close Xcode and then:
$ rm -rf node_modules
$ yarn install
$ cd node_modules/react_native/scripts
$ ./ios-install-third-party.sh
$  cd /third-party/glog*
$ sudo ./configure

For those using automatic/command-line build tools (i.e. fastlane, ci), attach to -UseModernBuildSystem=NO or -UseModernBuildSystem=N to the xcodebuild command to switch to the Legacy Build System.
https://github.com/facebook/react-native/issues/19573
https://github.com/facebook/react-native/issues/20492#issuecomment-423181560

Update, what solved for us was:

@NNaidoo workaround
Remove the library https://github.com/crazycodeboy/react-native-splash-screen from the ios project.
Ensure the build configuration in the scheme

Here is what worked for me:
$ cd node_modules/react-native
$ scripts/ios-install-third-party.sh
$ cd third-party/glog-0.3.5/
$ ../../scripts/ios-configure-glog.sh

Have you guys tried rm ~/.rncache/* ?

I've written a script and posted it to a gist which makes this a one-line fix:
curl -L https://git.io/rn-57-third-party | bash

I had the same issue: Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Release-iphonesimulator/MyCool.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist....
I found a quick and very simple solution for myself, hope it will help others!
Try this:
react-native init projectname
cd projectname
react-native start (this does the trick, leave this running in terminal)
...then, in a new terminal: cd projectname
react-native run-ios
It will take a while, don't do ctrl-c, the project will build!
:-)

https://github.com/facebook/react-native/issues/20774#issuecomment-430659700 not work for me.

../../scripts/ios-configure-glog.sh

so funny story as I kept upgrade react-native-cli and trying to stay up to date. I did indeed need to switch back to this script instead of .configure and everything worked on my Travis-ci matrix build just fine=

@geminiyellow the original script I posted only worked for RN 0.57, I've updated it now and it should work with other (older) versions too, for example 0.55.4 which is used by the create-react-native-web-app.
curl -L https://git.io/fix-rn-xcode10 | bash

Update, I had added this cd node_modules/react-native && scripts/ios-install-third-party.sh && cd third-party && cd glog-0.3.4 && ./configure && cd ../../../../ workaround to my postinstall.
That worked fine until I attempted to build in Release mode, this commands breaks something in third-part library build related.
This discussion helped me https://github.com/facebook/react-native/issues/19839#issuecomment-422381866

Any updates?
Is this going to be fixed soon?

I just checked and although my fix has been merged into the master branch, it has not been released.  There was a release 0.57.4 about 12 days ago but it contains older scripts.  I'm trying to figure out the release process.  CONTRIBUTING says I just need to patch master and then it gets moved into FB's internal repository.  How do things go from master to release?  Do I need to submit a PR against 0.57-stable also?

The release process is coordinated in the https://github.com/react-native-community/react-native-releases repository. https://github.com/react-native-community/react-native-releases/issues/54 looks like a good issue to discuss adding this to a 0.57.5 release.

Looks like @kelset is on top of it - he mentions he'll try to include @mmccartney's fix in 0.57.5 :https://github.com/react-native-community/react-native-releases/issues/54#issuecomment-436273232

good news

@hramos , still getting Xcode 10 errors on react-native 0.57.5

Similar, seeing same issues as before (after removing node modules, cleaning cached and reinstalling everything with latest versions)

My understanding is that the fix will only work for new projects - for existing projects probably the only ways are:

re-apply the workaround described in the first comment
manually apply the PR to your project - I use Pods on my projects so I was never actually affected, so can't really test this road. Potentially using the git-upgrade command may do it for this. But I don't know tbh 😔

Can anyone try and comment here?

@kelset I will try to apply PR manually in a bit. Also wanted to ask, do you have example / reference to somewhere that shows how to use react as a pod? Sounds like it is more stable / easier way to implement it.

@IljaDaderko there are a few articles out there, but it seems that they are a bit outdated: probably we should have a section in the docs for integrating:

https://shift.infinite.red/beginner-s-guide-to-using-cocoapods-with-react-native-46cb4d372995
https://medium.com/golee-engineering/my-experience-of-integration-between-react-native-and-ios-f1b9848f292a
https://medium.com/@Baconbrix/using-cocoapods-in-ios-12-e4dc95a11b15

@kelset Thank you for the links, so I assume what you meant is that you use React Native through pods like documented here: https://facebook.github.io/react-native/docs/integration-with-existing-apps
And you don't experience any issues with third party scripts? I am refactoring to use pods right now, to check if it solves issues on my end, is this peace of documentation up to date?

Yeah the docs should be up to date :) If not, can you open an issue on the website repo so that we can work it out?

@kelset refactored to use CocoaPods, everything is working 👌 with new build. I think I actually prefer this way of using react native.
I got few follow up questions for you if you have a minute?

I removed react related content in XCode from "Libraries" folder, and Build Phases. I edited my schema to use React from pods. Everything is working fine, but any chance I missed something else here?

Previously when I built through XCode, it auto started react native cli which was handy, with pods it doesn't. Is there a way to add cli start script to XCode somehow?

@NichAga @IljaDaderko Did you try deleting third-party (as in rm -rf node_modules/react-native/third-party) and then performing the build?

@mmccartney But that would be a temporary solution until package is re-installed right? I tried completely fresh setup with old node_modules deleted prior and it was failing :/

You are right, @IljaDaderko.  I'm having trouble reproducing the failure consistently but I do believe there is a problem with existing projects.  I have a feeling that the following commands will eliminate the problem but I can't be sure at this time:
rm -rf ios/{YourProjectName}.xcodeproj/project.xcworkspace
rm -rf ios/build

This what works for me, I have 2 versions of XCode on my MAC (XCode 9.4.1 & XCode 10.1):

Open XCode 9.4.1 and clean the build
yarn cache clean
yarn install
Build project on XCode (with General iOS Device)
Close XCode 9.4.1 and Open XCode 10.1
Build the project with XCode 10.1
Sometime the build fails, because of libfishhook.a issues.
7.1 I remove and add libfishhook.a which is located in RCTWebSocket.xcodeproj

It works for me always.
One point to mention, when I am adding a new package (yarn add [packgeName]) the entire process should start over. I prefer to install it when I am using XCode 9.4.1.

Delete the folder project
Reinstall it, react-native init rnapp
Open ios project file
Go to file -> project settings -> in build system choose Legacy Build System
Go to console react-native run-ios
That did the trick for me

For me, running pod install inside ios folder is what fixed it

Workaround in OP worked for me but with some little adjustments in steps 2 and 3:
2. cd node_modules/react-native
3. ./scripts/ios-install-third-party.sh
Oherwise, it would create the third-party folder inside scripts folder, not in react-native (which is the right one).
Also, I had to follow this to correctly link to libfishhook.a file in RCTWebSocket library.
And a final thing (couldn't verify this is required, maybe my dependencies were outdated) was running a pod install inside ios folder to update dependencies.

saved my day. RN 0.57.7, xcode 10.1

Is this expexted to happen on a newly initialized project when using xcode 10.1?

Hmm, with RN-0.57.7 and Xcode 10.1 using the NEW build system, everything just works. I don't need any workarounds.

I have done everything mentioned above but to no success. Is the new build system still not supported in 0.57.7?

this workaround worked for me
1- cd ios
2- pod install

@adiahuja07

I have done everything mentioned above but to no success. Is the new build system still not supported in 0.57.5?

Do you have both third-party/ and third-party-podspecs/ in node_modules/react-native/?

This almost gave me an aneurysm. @laurent22 solution actually worked for me, first time though. I was using Yarn, but same thing pretty much:

rm yarn.lock && rm -rf ios/build/ && rm -rf node_modules/ && yarn install && react-native run-ios

Had this issue when checking out a clean version of my repo.
Tried once installing with yarn and got the third party errors. Doing the same thing with checking out the repo and ensuring all caches' are clean and then installing dependencies with npm and i didn't receive the error anymore.
Using legacy build option.

@joshuakelly 0.55.4 was cut before the Xcode 10 beta became available, and lacks some of the updates we've made related to this issue.

Including navigation, maps, and video players in the core library is a non-goal. We're working on slimming down the core library in order to increase stability. See https://github.com/react-native-community/discussions-and-proposals/issues/6.

I understand your point @hramos. But sometimes when we introduce projects with clients and their requirements, we always cross our fingers with React-native that we told the client that yes we can make a video player with these above features or we can make a push notification type apps. But when we are going to build the app, then only we know the fact that we are fully dependent on third-party libraries. And at that time we can't deliver the app in correct time.
Even just because we can't be sure about that with RN what's the limitations in some areas, we lose a project and it goes to native development.
If we can't take projects then we can't make RN useful.

Its deff a virus big time .. billy
On 12/18/18, Prashen Jeet Roy<EMAIL_ADDRESS>wrote:

I understand your point @hramos. But sometimes when we introduce projects
with clients and their requirements, we always cross our fingers with
React-native that we told the client that yes we can make a video player
with these above features or we can make a push notification type apps. But
when we are going to build the app, then only we know the fact that we are
fully dependent on third-party libraries. And at that time we can't deliver
the app in correct time.
Even just because we can't be sure about that with RN what's the limitations
in some areas, we lose a project and it goes to native development.
If we can't take projects then we can't make RN useful.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/issues/20774#issuecomment-448485628

I changed my email , seem to work
On Tue, Dec 18, 2018, 11:40 PM Billy Dwyer<EMAIL_ADDRESS>wrote:

Its deff a virus big time .. billy
On 12/18/18, Prashen Jeet Roy<EMAIL_ADDRESS>wrote:

I understand your point @hramos. But sometimes when we introduce projects
with clients and their requirements, we always cross our fingers with
React-native that we told the client that yes we can make a video
player
with these above features or we can make a push notification type apps.
But
when we are going to build the app, then only we know the fact that we
are
fully dependent on third-party libraries. And at that time we can't
deliver
the app in correct time.
Even just because we can't be sure about that with RN what's the
limitations
in some areas, we lose a project and it goes to native development.
If we can't take projects then we can't make RN useful.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

https://github.com/facebook/react-native/issues/20774#issuecomment-448485628

I encountered a lot of problems surrounding this issue after upgrading my react-native to the latest version.
In the end for me the issue was solved by fixing the path of glogs in the ios-install-third-party.sh script to: "\"../../$SCRIPTDIR/ios-configure-glog.sh\""
In the original file the path is "\"$SCRIPTDIR/ios-configure-glog.sh\"", causing an error during running of the script, and later also errors of 'glog/logging.h' file not found later on; Presumably because the files are not findable by the other third-party libraries, as those are installed without the glog configuration script having ran.
So after running npm/yarn, change the ios-install-third-party.sh script, then run it while in the node_modules/react-native directory. Xcode is on the new build system, changing it did not do anything for me so I left it on the new.
Hope this helps others, I spent quite some hours working my way through this. If someone has any idea of what the underlying issue might be, please inform us all. I encountered this problem while upgrading my project from an older react-native version, so that may be the cause somehow, at least in my case.

We are running into similar issues. We set up a project with React Native 0.57.7 on CI and everything works when we don't cache the Yarn dependencies. The problem comes when we enable the Yarn dependencies caching. We get the aforementioned issue with the config.h.
I've tried running the the following script in a post install Yarn script:
cd ./node_modules/react-native && scripts/ios-install-third-party.sh && cd third-party && cd $(ls | grep 'glog' | awk '{print $1}') && ./configure

But I keep getting the same error. Who is running the ios-install-third-party.sh? Is it run when the dependencies are installed and nothing exists in the cache directory (.rncache)? If so, do you think caching the files in that directory would help?

I had the same problem, I solved it by doing what @abaart suggested. Though after that, I got an error regarding React/RCTBridgeModule. Any ideas?

I have the same issue running a build on Bitrise. Any ideas?

@dale-french In bitrise I have a bash script that uses the code that fiznool created in his gist.
I run it after installing all node_modules but before building the archive.

I got this error while archiving. Did everything mentioned... but nothing worked. The error was at signalhandler.cc > GetPC method.
replaced return (void*)context->PC_FROM_UCONTEXT;
with        return NULL;

I'm having trouble with this as well. Trying to follow the last step of the top post's workaround instructions fails for me:
$ ../../scripts/ios-configure-glog.sh

checking sys/ucontext.h presence... yes
checking for sys/ucontext.h... yes
checking how to access the program counter from a struct ucontext... cat: conftest.er1: No such file or directory
mv: rename conftest.er1 to conftest.err: No such file or directory
cat: conftest.er1: No such file or directory
mv: rename conftest.er1 to conftest.err: No such file or directory
configure: WARNING: Could not find the PC.  Will not output failed addresses...
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/glog/logging.h
sed: ./confywoJNz/out: No such file or directory
mv: rename ./confywoJNz/out to src/glog/logging.h: No such file or directory
config.status: error: could not create src/glog/logging.h

IT IS STILL NOT WORKING ON REACT-NATIVE 0.59.1
$ react-native run-ios
info Found Xcode project test4.xcodeproj
info Building using "xcodebuild -project test4.xcodeproj -configuration Debug -scheme test4 -destination id=564347E4-D73D-4AE3-892F-F7F8FDD5F51C -derivedDataPath build/test4"
▸ Running script 'Install Third Party'
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 test4.xcodeproj

** BUILD FAILED **

The following build commands failed:
	PhaseScriptExecution Install\ Third\ Party /Users/hiepnm/workspace/temp/test4/ios/build/test4/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/double-conversion.build/Script-190EE32F1E6A43DE00A8543A.sh
(1 failure)

OMG! I found the solution:
Fix issue with gawk depending on a bad readline.
It causes
dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.7.dylib
Referenced from: /usr/local/bin/awk
Reason: image not found
Solution:
brew uninstall gawk
brew uninstall readline
brew install readline
brew install gawk

Xcode build fails to download third-party dependencies
WD=$(pwd)
cd node_modules/react-native
rm -fr third-party
$WD/node_modules/react-native/scripts/ios-install-third-party.sh

Hello @hiepnm 👋!
By using the repro / the list of steps to reproduce, we can't actually see the reported bug on RN 0.59 so we'll close this issue. It may have something to do with your local setup, please double check that you are using the correct version of Android Studio / XCode / Android NDK / Yarn / etc.

I'm having this issue on RN 0.59.1. This happens after running react-native run-ios from a freshly initialized project.
It appears that the scripts/ios-install-third-party.sh script is failing on MacOS.
Unknown option: p
Type shasum -h for help
Unpacking /Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/glog-0.3.5.tar.gz...
./scripts/ios-install-third-party.sh: line 64: ./scripts/ios-configure-glog.sh: No such file or directory
Unknown option: p
Type shasum -h for help
Unpacking /Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/double-conversion-1.1.6.tar.gz...
Unknown option: p
Type shasum -h for help
Unpacking /Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/boost_1_63_0.tar.gz...
boost_1_63_0/boost/log/detail/format.hpp: (Empty error message)
tar: Error exit delayed from previous errors.
Unpacking '/Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/boost_1_63_0.tar.gz' failed. Debug info:
-rw-r--r--  1 kevin  staff  7049801 Mar 21 21:37 /Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/boost_1_63_0.tar.gz
e57f86fe1b3fc5b54e73a11ea9b29b14c0ee140e  /Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/boost_1_63_0.tar.gz
Unknown option: p
Type shasum -h for help
Unpacking /Users/kevin/Library/Caches/com.facebook.ReactNativeBuild/folly-2<IP_ADDRESS>.tar.gz...

OK, this seems to be solved in #24036.

OMG! I found the solution:
Fix issue with gawk depending on a bad readline.
It causes
dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.7.dylib
  Referenced from: /usr/local/bin/awk
  Reason: image not found

Solution:
brew uninstall gawk
brew uninstall readline
brew install readline
brew install gawk

Xcode build fails to download third-party dependencies
WD=$(pwd)
cd node_modules/react-native
rm -fr third-party
$WD/node_modules/react-native/scripts/ios-install-third-party.sh

I met same issue. Can someone help me?

I'm still encountering this issue as of 0.59.3 after following the React Native CLI getting started on macOS and iOS latest version of Xcode

My very whacky workaround (maybe it helps someone else): when I build the app from scratch in Xcode 10 using react-native 0.59.3, I get the mentioned errors; however, when I first build it in Xcode 9 (9.4.1 to be precise) and then (without clearing the project of course) build it again in Xcode 10.1 it works. Apparently Xcode 9 generates some build artefacts that are reused by Xcode 10. I don't see this as a "solution" of course, it just keeps my project alive 🤕

OMG! I found the solution:
Fix issue with gawk depending on a bad readline.
It causes
dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.7.dylib
  Referenced from: /usr/local/bin/awk
  Reason: image not found

Solution:
brew uninstall gawk
brew uninstall readline
brew install readline
brew install gawk

Xcode build fails to download third-party dependencies
WD=$(pwd)
cd node_modules/react-native
rm -fr third-party
$WD/node_modules/react-native/scripts/ios-install-third-party.sh

This worked for me 🙌

[RN 0.59.4 / Xcode 10.2]
I am using cocoapods.
If I use legacy build system, Xcode builds target 'React' first and other library Later. Build is success.
But if i use new build system, Xcode builds third-party-library first instead of 'React'.
Build error message is "'React/RCT~Modul.h' file not found....
And If i use Xcode 10.1, Using new build system is fine. Build is success....
How can i set build target Order?

RN 0.57.1 and XCode 10.2

if I'm trying to run the app into 12.2 version simulators or devices, then app got crashed with
Thread 1: signal SIGABRT
ISSUE LINE -> 0x102eda2f8<+8>:  b.lo   0x102eda310               ; <+32>

if I'm trying to run into 12.1 version simulators or devices, it works fine.

With this (RN 0.57.1 and XCode 10.2) configuration, if I generate IPA, it's only working in 12.1 devices and when it comes to 12.2 devices, app getting the crash on the launch screen with  Thread 1: signal SIGABRT.

Any suggestions or workarounds to solve this issue?
Thanks for that savior.

I don't think anything below 0.59.2 works with Xcode 10.2, bacause of some changes with the load methods.

@0ff thank you! could you explain how to apply your solution please? not sure what to do

Is the new xcode build system supported on RN 0.59+? Im using xcode 10.2 and have tried using the new build system but it errors saying there is an issue with my carthage libs.

It works just fine for me, but I don't use any Carthage libraries...

clang: error: no such file or directory: '/Users/pavelkuzmin/D/RC/DA/node_modules/react-native/third-party/double-conversion-1.1.6/src/cached-powers.cc'
clang: error: no input files
:(

I am facing a little different issue
when i run ./ios-install-third-party.sh
Unpacking /Users/shayana/Library/Caches/com.facebook.ReactNativeBuild/glog-0.3.5.tar.gz...
./ios-install-third-party.sh: line 66: ./ios-configure-glog.sh: No such file or directory
Unpacking /Users/shayana/Library/Caches/com.facebook.ReactNativeBuild/double-conversion-1.1.6.tar.gz...
Unpacking /Users/shayana/Library/Caches/com.facebook.ReactNativeBuild/boost_1_63_0.tar.gz...

I do have the same problem.
I'm on a Mac 10.14
XCode 11.0
react-native-cli: 2.0.1
react-native: 0.60.5
Can't build after basic init from react-native init mytestingapp.

It finally worked.
What I did is use npx react-native init awesomeproject. And I was able to build the project.

I had to remove the node_modules folder and then run npm install again to get mine working. I tried everything but it didn't work.

when i run my project on terminal for react-native i faced this issuue. is there any solution?
"Failed to build iOS project. We ran "xcodebuild" command but it exited with error code null. To debug build logs further, consider building your app with Xcode.app, by opening demo.xcworkspace "


Fixed format files

I need to finish updating the fixed-format grammar, and then we will be able to handle fixed-format files as well.
We'll also need a setting to map file extensions to free- or fixed-format. For example, c2pk uses .F, gs2 uses .fpp, and other projects use .f90 for free-form preprocessor files.

Will we have to add tags to mark rules as fixed/free-format? Or will we just recommend that fixed-format be converted to free-format, and use the same lints?
Also, will this need a new tree-sitter extension, or is the plan to have tree-sitter-fortran handle both?

There's a separate grammar for fixed format, as there are a couple of
important syntax differences.
Might need tags for different rules. Definitely good to have a rule to
recommend converting to free form. There are some tools out there to do
this automatically, but if there's nothing suitable, it would make a good
subcommand. The ASTs should be pretty similar between the two forms, so
rewriting shouldn't be too difficult -- hackathon project?
Currently we (mostly) do string comparison for node minds, which should be
fine between the two formats, but if we wanted to switch to kind IDs, then
they might be different and require more careful handling.
On Wed, 9 Oct 2024, 13:57 LiamPattinson, @.***> wrote:

Will we have to add tags to mark rules as fixed/free-format? Or will we
just recommend that fixed-format be converted to free-format, and use the
same lints?
Also, will this need a new tree-sitter extension, or is the plan to have
tree-sitter-fortran handle both?
—
Reply to this email directly, view it on GitHub
https://github.com/PlasmaFAIR/fortitude/issues/78#issuecomment-2402248769,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALLAXUTEX2EYLCICQNMU2LZ2UR3BAVCNFSM6AAAAABPUKOHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBSGI2DQNZWHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add YieldNexus documentation page

This adds documentation to the YieldNexus bidder adapter, in relation to prebid/Prebid.js#2855.

Hi @jsnellbaker, thanks so much for merging the Yield Nexus adapter in prebid/Prebid.js#2855. This is the corresponding documentation PR.
I wanted to make sure whether the added link in index.md will indeed add Yield Nexus to the download page correctly? Will the link text "Yield Nexus" automatically & correctly map to the yieldnexus adapter?

Hi @ericyld
The addition you made on the index.md page merely adds your adapter name to the list/table of Prebid partners.  The addition of your adapter to the download download page is actually based on the presence of the bidder page you created.  The scripts we use on the download page read through the bidder pages and creates the various check-boxes/labels.
To note though, the download page update process is semi-automated and it may be a few days after a release before you see your adapter's name listed.  Please let me know if you any additional questions on this topic, I'll be happy to help.

@mmoses FYI.

@ericyld - would just make this change myself but don't have write access to your fork.

Hi @bretg - thank you just added the type param with string value.


Build error after upgrading to Xcode 7.0 (SOLVED: xcode-select --install)

I got the following error after upgrading to Xcode 7.0
==> Building third-party dependencies.
==> cmake ../third-party -DUSE_BUNDLED_BUSTED=OFF -DUSE_EXISTING_SRC_DIR=ON -DCMAKE_C_FLAGS_RELEASE= -DCMAKE_CXX_FLAGS_RELEASE= -DCMAKE_INSTALL_PREFIX=/usr/local/Cellar/neovim/HEAD -DCMAKE_BU
==> make VERBOSE=1
If you meant to cross compile, use `--host'.
See `config.log' for more details
make[2]: *** [build/src/jemalloc-stamp/jemalloc-configure] Error 1
make[1]: *** [CMakeFiles/jemalloc.dir/all] Error 2
make: *** [all] Error 2

https://gist.github.com/0d285094ba0995072953

Never mind, xcode-select --install fixed this issue.

When was faced with the same issue - reinstall helped.

Trashed and purged 'Xcode.app'
Ran sudo rm -rf /Library/Developer/CommandLineTools
Followed by sudo xcode-select --install

Lo and behold, build succeeded!


It's unclear how to handle a '.' in an environment variable configuration value.

In the "environment variables" setting, it's stated clearly that ':' is not always valid and can be replaced with double underscore. However, it's very common for .NET Core configuration to reference a namespace like MyNamespace.MyClass. In that situation, I believe .NET Core lets us use a single underscore since the dot is illegal for environment variable names in most systems. A very close read of the section, including the code, lets us infer that single underscore will work. But it was not clear to me at all, and I think it should be explicitly stated just as substituting double underscore for a colon is.

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

ID: 0eb4d762-3910-2c57-8741-3306c15537b6
Version Independent ID: ba2254a0-ea8e-9b28-e94b-edd0fc58c043
Content: Configuration in ASP.NET Core
Content Source: aspnetcore/fundamentals/configuration/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@jbmadscience  when would you need a fully qualified name that required a . ?
@serpent5  please review.

"Logging": {
"LogLevel": {
"MyNamespace.MyClass": "Trace"
}
}
On Thu, Mar 19, 2020, 3:55 PM Rick Anderson<EMAIL_ADDRESS>wrote:

@jbmadscience https://github.com/jbmadscience when would you need a
fully qualified name that required a . ?
@serpent5 https://github.com/serpent5 please review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/issues/17378#issuecomment-601412169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJNJQTWAC6247CKU4PTV2DRIKBDFANCNFSM4LPT5TJQ
.

@jbmadscience  why not write it as
"Logging": {
    "LogLevel": {
        "MyNamespace_MyClass": "Trace"
    }
}

Then config file and environment are the same.

@jbmadscience  this is in thhe default appsettings.json file:
  "LogLevel": {
    "Default": "Information",
    "Microsoft": "Warning",
    "Microsoft.Hosting.Lifetime": "Information"
  },

You're right.

C:\keep\ConfigSample>set Logging__LogLevel__Microsoft_Hosting_Lifetime=EnvironmentLoggingMShosting

C:\keep\ConfigSample>dotnet run
Unhandled exception. System.InvalidOperationException: Configuration value 'EnvironmentLoggingMShosting' is not supported.

I had the idea that underscore would work because of the samples in the
topic we're discussing. But if that doesn't work that would explain an
issue I'm having.
Any idea what does work for setting a variable with a namespace dot in it?
On Thu, Mar 19, 2020, 5:49 PM Rick Anderson<EMAIL_ADDRESS>wrote:

C:\keep\ConfigSample>set Logging__LogLevel__Microsoft_Hosting_Lifetime=EnvironmentLoggingMShosting
C:\keep\ConfigSample>dotnet run
Unhandled exception. System.InvalidOperationException: Configuration value 'EnvironmentLoggingMShosting' is not supported.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/issues/17378#issuecomment-601452218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJNJQXQDE2N2O4KB37BN63RIKON7ANCNFSM4LPT5TJQ
.

I'll find out - or more likely @serpent5
C:\keep\ConfigSample>set Logging__LogLevel__Microsoft.Hosting.Lifetime="MyKey val"

C:\keep\ConfigSample>dotnet run
Unhandled exception. System.InvalidOperationException: Configuration value '"MyKey val"' is not supported.

OOPs, I had that wrong. The following 3 approaches don't throw, but they don't work either:
set LogLevel__Microsoft_Hosting_Lifetime=EnvironmentLoggingMShosting
cd C:\keep\ConfigSample
set LogLevel__Microsoft.Hosting.Lifetime=MyEnvironmentLoggingMShosting
set LogLevel__Microsoft__Hosting__Lifetime=MyEnvironmentLoggingMShosting
dotnet run

The exception was because I had Logging before the actual key.

BINGO
This works
set LogLevel__Microsoft__Hosting__Lifetime=MyEnvironmentLoggingMShosting3
using double underscore for dot

@jbmadscience  see https://github.com/dotnet/extensions/issues/3095

Thanks Rick!
That turns out to be a more complex issue than I had realized - I
definitely hadn't caught on that it needed only 2 nesting levels!
On Thu, Mar 19, 2020 at 7:04 PM Rick Anderson<EMAIL_ADDRESS>wrote:

@jbmadscience https://github.com/jbmadscience see dotnet/extensions#3095
https://github.com/dotnet/extensions/issues/3095
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/issues/17378#issuecomment-601471232,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJNJQU6RBWHCDTQMWYFRZ3RIKXJ7ANCNFSM4LPT5TJQ
.

@jbmadscience Is your problem specific to logging? As far as I know, there's no conversion from _ or __ to . in either the env provider or the logging system.

No, the problem is in the environment variable configuration provider.
Logging is an easily reproducible and common scenario where the issue would
be visible. I'm not aware of any logging specific issue affecting the
behavior.
The env configuration provider documentation clearly discusses the
conversion between ':' and '__' because some OS's don't allow ':' in a
variable name.
The issue here is that I don't see any  documentation for handling a dot in
the name, despite that being necessary for common cases such as logging.
I'm a little confused whether that's because there is no support for it, or
whether it's just not documented. Several blog posts for earlier versions
of .NET Core appear to suggest it was supported, but is now broken.

Joshua

On Mon, Mar 23, 2020, 5:12 PM Kirk Larkin<EMAIL_ADDRESS>wrote:

@jbmadscience https://github.com/jbmadscience Is your problem specific
to logging? As far as I know, there's no conversion from _ or __ to . in
either the env provider or the logging system.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/issues/17378#issuecomment-602884058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJNJQU3F3KPEE5N6Y65KIDRI7NDZANCNFSM4LPT5TJQ
.

This issue was closed neither with an explanation nor a link to how the bug is being handled.

@Rick-Anderson
Is it possible improve the doc that explain what to do if the dot or colon appear in the environment variable?

Any update for this? @mnmadscience @Rick-Anderson

I'm not sure if this is the right place to add this, but dots are not valid in IoT Edge config:
ERROR: {
  "validationErrors":[
    {
      "description":"'Logging__LogLevel__Example.Nested.Namespace' does not match any of the regexes: '^[^\\\\+#$\\\\s\\\\.]+$'",
      "contentPath":"$edgeAgent.properties.desired.modules.example-nested-namespace.env",
      "schemaPath":"properties.$edgeAgent.properties.properties.desired.properties.modules.patternProperties.^[a-zA-Z0-9_-]+$.properties.env.additionalProperties"
    }
  ]

I'm unable to use the workaround of setting env var for Logging__LogLevel__Example as this namespace contains my whole app.

How are you supposed to do this?! Still no explanation and no hint in the docs!

This should be reopened. There are places where dots cannot be added, such as systemd units or the other deployment methods mentioned in the comments.
Similar issue that was also closed: https://github.com/dotnet/docs/issues/22817

Its clear that you cannot do this at present. Its not a supported thing. The only option currently is to create your own configuration provider (just decompile EnvironmentVariablesConfigurationProvider) and modify to support some custom character substitution.


Add xref_query_tags to resolve xref in docfx v3 build

In v2, xrefservice can be defined in docfx.json then the user can query uid universally, which will be removed during the migration to v3 and related tags should be added to .openpublishing.publish.config.json.
We created this pull request to make the repository ready to migrate to docfx v3. This PR will not change any published pages.

Hello @v-pegao ...

query uid universally

Can you point me to or tell me what the new cross-repo xref syntax will be? I haven't been brought up to speed yet.

Hi @guardrex
Docfx v3 supports same docfx v2 xref syntax, but xref_query_tags needs to be defined in .openpublishing.publish.config.json. xref_query_tags is list of base_path where cross referenced articles are published to(no need add base_path of current docset).
You can use one of the following syntax to cross reference a topic with UID defined(find more details here):

Markdown link: link_text
Auto link: xref:uid_of_the_topic
Shorthand form: @"uid_of_the_topic"

To learn more on xref of docfx v3, ref here
Involve @mingwli to check if anything need add.

Thanks for explaining.
The first doc that you linked isn't available to me, and the second doc doesn't seem to indicate any practical changes. We already use the xref link formats that you listed.
May I ask a couple of perhaps unrelated questions ...

I noticed that this change lists /dotnet, but explicit UIDs (uid: topic_uid in metadata) isn't used in the .NET Core doc set. We use relative links to their docs (e.g., [link text](/dotnet/core/index)). Are there implicit UIDs for their topics that could be used in xref cross-links from our docs?

We aren't able to use xref links to a particular version of a doc in our doc set. Query strings aren't preserved. [Note that we don't use version-by-file.]
For example, the following links assume ...

The UID of the topic to link is fundamentals/servers/kestrel.
The link should specify the aspnetcore-2.2 version of the topic.
The live topic today (default version) is at: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-3.0

We can't use ...
[link text](xref:fundamentals/servers/kestrel?view=aspnetcore-2.2)

We must use the relative link in this scenario ...
[link text](/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-2.2)

Does DocFx 3 address this scenario and allow the use of an xref link to the 2.2 version of the topic?

Hi @guardrex
For the first question, we haven't found UIDs in repository dotnet/docs are used as xref in current repository(aspnet/AspNetCore.Docs). Listed all base_path that needed for master branch of current repository(aspnet/AspNetCore.Docs) for your reference.

base_path
source repository url
sample article from current repository(implicit UID)

/dotnet
https://github.com/dotnet/dotnet-api-docs
blazor/call-web-api.md(<xref:system.net.http.httprequestmessage>)

/dotnet
https://github.com/aspnet/ApiDocs
blazor/call-web-api.md(<xref:microsoft.aspnetcore.cors.infrastructure.corspolicybuilder.withheaders*>)

/dotnet
https://github.com/Azure/azure-docs-sdk-dotnet
mvc/models/file-uploads(<xref:microsoft.azure.storage.file.cloudfile.uploadfromfileasync*>)

/dotnet
https://github.com/aspnet/EntityFramework.ApiDocs
test/razor-pages-tests.md(<xref:microsoft.entityframeworkcore.dbcontextoptions>)

/aspnet
https://github.com/aspnet/AspNetDocs
fundamentals/app-state.md(xref:signalr/index)

For the second question, yes, Docfx V3 handles that, just add the query link to UID:

[link text](xref:fundamentals/servers/kestrel?view=aspnetcore-2.2)
Here is a test for your reference:

The article defines the UID: test-moniker-range/test-moniker-range and with moniker range >= aspnetcore-2.1
The article are published to version aspnetcore-2.1, aspnetcore-2.2, aspnetcore-3.0
Another article in same docset references the UID: test-moniker-range/test-moniker-range with specific moniker version in query string
The xref works as expected on published page

Thanks @v-pegao.
AFAIK, there isn't an online public tool (a website) that produces xref API doc links for us to use in topics.
I had to create a rather badly programmed site to create these links, but it works fairly well. It seems like an app like this would be useful for everyone ... an app like this except with 🐞 fewer bugs 🐞 in it :smile:.
https://xrefgen.azurewebsites.net/
... it hits the same web API that the MS API Browser site uses at ...
https://docs.microsoft.com/api/apibrowser/dotnet/search?api-version=0.2&search={searchText}
As far as you know, there's nothing official like that, correct? Anything in design? If there is something in design, please make sure that they make it public. Those who don't have credentials, such as myself, need access to a public app.

@v-pegao When can xrefService be removed from our docfx.json file? I want to make sure we don't forget to remove it if it serves no purpose once docfx v3 goes live.

Hi @guardrex, I don't know if there is similar official tool to produce xref API doc links or not, but I had a try on your tool, that's really nice, thanks for sharing!

Hi @scottaddie, as I know,  the xrefService can be safely removed from docfx.json file after Docfx V3 build is enabled for the repository.
cc @mingwli in case anything needs to be added


Slight bugs in running first tutorial

The jupyterlab has to be installed. Right now the user is not told to do so anywhere it would seem.
The pylatexenc is not automatically installed and the user directly runs into this error as they attempt to run the tutorial 01_introduction.
The ipywidgets is not automatically installed.

Both seem fixable through the setup.py file and through documentation no ?

Another question that came up:
Is the first input really appropiate ?

from qiskit import QuantumCircuit

qc = QuantumCircuit(4)  # Create a quantum circuit describing four fermionic modes.

qc.load_fermions([1, 2])  # Load fermions into modes 1 and 2.

qc.draw(output='mpl')

It somehow seems to set up another kind of circuits than afterwards as all the wires are labelled as fer_mod instead of q afterwards.

To your first point, these can all be installed through the requirements-dev via
pip install -r requirements-dev.txt

at the project root. Maybe it would make sense to just add it to the normal requirements which the setup.py installs under the hood..

Both are fine (the second option bloats the installation slightly more, but allows to come with batteries included).
If the requirement-dev.txt is used, it should be mentionned somewhere in the readme or something like that right ?

Good point, I added a sentence in the Readme. The reason I don't want this in the standard installation is that people have different preferences how to execute .ipynb files.


Hookup faq to api, update deps

looks like...

Codecov Report

Merging #10 into master will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master     #10   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          14      14
  Lines          80      84    +4
  Branches        3       3
======================================
- Misses         77      81    +4
  Partials        3       3

Impacted Files
Coverage Δ

src/Components/Tabs/FAQ.js
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Wiki plugin to handle UTF-8 characters solves #127

@JohnMaguire, Please review these changes and see if they are okay for merging.
The unicode chars in url have to be preserved till the final stage in urlopen (wikipedia/plugin:53), where the unicode string is encoded.

Looks great, thank you! 👍


(PDB-2004) Alter tests to fix Travis jdk_switcher

Let Travis handle the jdk selection.  Right now jdk_switcher doesn't
actually exist.  This means Travis generates the test matrix more
implicitly, so use exclusions to make sure we only test ruby on one
db/jdk combination.
Add "set -ueo pipefail" to catch errors.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/111/
Test FAILed.

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/114/
Test PASSed.


Enum states not working

Some Enums are not provided by bluetti_mqtt, so they will be displayed as raw Enum


Implement a Double Ended Queue

Self Explainatory

Kindly assign me this issue! I want to contribute it in java.


Space typo

Looks like there is a space missing:

Link: https://react-hook-form.com/api/useform/register/

thanks


See Duplicate Contacts feature failing to display Duplicate Record Sets for Contact/Contact Match

Issue:
Even when Contact/Contact Duplicate Record Sets (DRS) exist for two matching Contact records, the "See Duplicate Contacts" option on Contact Merge doesn't show the option to merge the Contacts.
Steps to reproduce:

In an org that doesn't have a Contact Duplicate Rule assigned to the NPSP Matching Rule, manually create duplicate Contact records so that they will match based on fuzzy FN, exact LN and Personal Email field. (Mike and Michael; Steve and Stephen; Rob and Robin work for the FN fields)
Activate a Contact Duplicate Rule that is assigned to the NPSP Matching Rule; and has "Allow" and "Report" selected in the "Action on Edit" and "Action on Create" fields.
Click on one of the Contacts, Run a Duplicate Job (if Unlimited Edition org. or if Data Integrity license is present in EE org.), or Edit one of the Contact records created in step one.
Navigate to the Contact Merge tab from NPSP
Click Show Duplicate Contacts button
Expected behavior: Duplicate Record Set records should be displayed after clicking the Show Duplicate Contacts button.
Actual behavior: No Duplicate Record Set records are displayed

Workaround: Ensure the Duplicate Rule is Active PRIOR to creating the duplicate Contact records in step one.

**lurch: attach W-042174

Tracking W-042174

W-7721484


Subscription – Annual subscription and Pay-per-use options are not displayed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.12-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/46126
Action Performed:

Go to staging.new.expensify.com
Create a new expensifail account
Create a workspace
Go to More features
Toggle on Report fields
Click Upgrade to upgrade to Control
Go back to Account settings
Click Subscriptions
Scroll to Subscription details
Change subscription to "Pay-per-use"
Note that the page opens without issue
Now delete the Control workspace
Go back to Account settings
Verify that subscription is not shown anymore

Expected Result:
"Annual subscription" and "Pay-per-use" options should be present in Subscription details section
Actual Result:
"Annual subscription" and "Pay-per-use" options are missing in Subscription details section
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/8cf3555d-4b21-45d5-ad70-4f3ab5778815
View all open jobs on GitHub

Sorry for the confusion, dupe https://github.com/Expensify/App/issues/46245


Finding changes

I have finished implementing all of the new code that @jiajunshen wrote for the update process. The one thing that we need to still work out is calculating the changes in the incoming data (vs what's already stored in the dat table) for a given dataset.
The assumption we made previously was that all of the duplicates would be eliminated so that when you run the join between the src table and the dat table, the keys that it returns are unique. That is no longer true because we are keeping all of the duplicate versions and just numbering them.
@svetlozarn How would you recommend comparing the incoming source data with what's already in the database given the new update strategy?

No longer relevant with new ETL


Amberv2 jeremy merge

@yetti
There is one unit test still failing but I'm making this pull request in case you don't want to wait for it.

@jrixon Thanks, I've checked out your branch locally. I'll just leave this here until you've fixed up that last test.

Build finished.

@yetti
Unit test is working now


Allow participation in 'whale rounds'

Users frequently request that they be allowed to choose their own minimum output size from coinjoins (a feature available in BTCPay's implementation) https://github.com/WalletWasabi/WalletWasabi/issues/12674 to avoid creating coins that they think will be unspendable at future fee rates.
There are two ways for clients to handle the leftover sats below the minimum output size when decomposing their funds:

Forfeit any leftover sats that can't be split into standard denominations to the coordinator/mining fee
Add any leftover sats to some standard sized output you would have chosen, creating "change" instead

@turbolay mentioned in the community call that option 2 is almost always the worst option according to the client because of the way anonymity scores are measured. Also, each additional user who sets a custom output size preference will marginally degrade the ability of every other user in the coinjoin to choose common sized outputs with each other. Because of this, Wasabi's decomposition strategy aggressively attempts to avoid creation of uneven change outputs, following option 1.
As a safeguard to limit potential losses from this mechanism, Wasabi clients will not register to coinjoin rounds that require a minimum output amount higher than 0.00009999 BTC. Due to this, coordinators do not have much flexibility to specialize their services to create rounds that optimize for medium or large sized 'whales', which increases the incentive for participants in the coinjoin to 'backstab' each other by screwing up one another's decomposition attempts by using their own custom denomination limits.
This safeguard can be made more flexible by combining strategies 1 & 2:
-If decomposition results in <9999 sats lost, then forfeit sats
-If decomposition results in >9999 sats lost, then create change
By having a sanity check that falls back to creating change, that would allow clients to safely participate with coordinators that increased the minimum output size of their rounds. Ideally, each user would be able to specify this forfeit limit in their client so they can balance the tradeoff themselves and not pay any "hidden fees" (and improve privacy by making this calculation harder for observers to undo).

This also improves coordinator DoS protection since it requires the attacker to deploy more capital.

Closing, 'Number go up' eventually solves this.

Ideally, each user would be able to specify this forfeit limit in their client so they can balance the tradeoff themselves and not pay any "hidden fees" (and improve privacy by making this calculation harder for observers to undo).

This would still be a good config setting, although it's a possible footgun.


enable hibernate-regions-compatible by default

Signed-off-by: qupeng<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tiflow/issues/4461
What is changed and how it works?
Check List
Tests

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

Code changes
Side effects
Related changes
Release note
None

Codecov Report

Merging #4583 (e1691fb) into master (9607554) will decrease coverage by 0.0271%.
The diff coverage is 62.1148%.

Flag
Coverage Δ

cdc
60.3402% <59.3750%> (+0.4180%)
:arrow_up:

dm
51.5645% <63.1317%> (-0.4644%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4583        +/-   ##
================================================
- Coverage   55.6402%   55.6131%   -0.0272%
================================================
  Files           494        504        +10
  Lines         61283      62176       +893
================================================
+ Hits          34098      34578       +480
- Misses        23750      24145       +395
- Partials       3435       3453        +18

/run-integration-test

/run-integration-test

/run-integration-test

/run-integration-test

/merge