Connecting scatter points

Feature Proposal
Hi hivemind,
I'm looking to create a connected scatter graph - two data sets with all points of each set connected together. Due to the way x-values are stacked, it isn't possible in MPAndroid, Vico or others and after review, I don't think this is possible with the standard Chart.js API?
Am I right in thinking that although Chart-plugin-annotation can draw boxes, lines and polygons - none have the required features for this use case?

Possible Implementation
A simple function to draw lines between two points,
an extension of line
e.g. path (from, to) = ( {x1, y1}, {x2, y2} )

You could if you order the scatter points in the right way put the showLine prop to true or write a custom plugin.
But it is not a supported use case since scatter charts are mostly used for random data

thanks for your input. Using chart type scatter, do you know why the showLine is not available?
(property) datasets: {
    label: string;
    data: {
        x: number;
        y: number;
    }[];
    backgroundColor: string;
}[]

new Chart(
    document.getElementById('test'),
    {
      type: 'scatter',
      options: {
        aspectRatio: 1,
        scales: {
          x: {
            min: 1900,
            max: 2150
          },
          y: {
            min: 450,
            max: 750
          }
        }
      },
      data: data
    }
  );

it is available
https://jsfiddle.net/s6tc8xhv/3/

Closing as this is possible/available


[Impeller] Add functionality to convert texture format and size.

This is likely going to be backend specific. Will be useful for implementing image resizing on the GPU, as well as for readback to specific pixel formats.
On Metal backends, this can likely just use MPSImageConversion  and MPSImageScale - though we need to double check the availability.
For Vulkan, I think the blit pass itself is capable of converting pixel formats but I'm not smart enough to understand the spec for vkCmdBlitImage . If it can't do resizing, the we can create a render pass and draw the mipped texture - or do software resizing.
For OpenGL, we could probably just do sofware resizing/conversion. So we'd likely need a fallback regardless.
Needed for Texture readback APIs, as these currently bounce all of our pixel data through Skia.

Even on OpenGL, we could render to (smaller) texture right? Or, is there a case where we need to perform resizes when there is no graphics context present?
In the case of the former, we don't need a software resizer. If the case of the latter, we should begin with a software resizer first.

We can resize via rendering but I don't think we can always convert texture format/alpha behavior? (this is for Image.toByteData and friends)

Bumping down to P3. We dont need these for now as we can use the Software resizer.


Full size plugins

Please could you add the ability for Plugins to be able to run in a tab, like Ace editor does for each file. This would provide greater capability for Plugins, to make them easier to refer to, for example with the DocHub plugin, this could be very helpful. (Could be helpful for #486 )

@daeks Is this feature supported now? At least I cannot find that in the master branch. Unless I am missing something.

no there is currently no further process


Enigma M4 gives wrong encryption for some rotor settings

When the Enigma M4 is set to use reflector UKW B thin and 4th rotor Beta in position A, ring A, the encryption should be identical to that of the M3 set to reflector UKW B. See https://www.cryptomuseum.com/crypto/enigma/m4/index.htm in section "Zusatzwalze Beta (β) and Gamma (γ)".
Cryptii works correctly in this setting for some rotor combinations. By accident, I discovered that it fails to work with certain combinations. I did not notice any particular pattern. In the examples below, I merely changed Rotor 2 from II to I.
Steps to reproduce the bug

See correct behavior: https://cryptii.com/pipes/D3cegA
See incorrect behavior: https://cryptii.com/pipes/PYzXOQ

Describe what you expected to happen
Output text in the 2nd example should be the same as the input.
Version, environment and state
Tried with Chrome and Firefox, same behavior on both.
Inside the web app press Ctrl+I, copy the presented alert text and paste it into the block below.
{"version":"4.0.8+master.8ae346e","env":{"name":"firefox","version":"81.0.0","os":"Linux","type":"browser"},"pipe":{"id":1032640313,"url":"https://cryptii.com/pipes/PYzXOQ","title":"The Enigma machine: Encrypt and decrypt online","description":"The Enigma cipher machine is well known for the vital role it played during WWII. Alan Turing and his attempts to crack the Enigma machine code changed history. Nevertheless, many messages could not be decrypted until today.","items":[{"name":"text","title":"Plaintext"},{"name":"enigma","settings":{"model":"M4","reflector":"UKW-B-thin","rotor1":"beta","position1":1,"ring1":1,"rotor2":"I","position2":17,"ring2":3,"rotor3":"III","position3":12,"ring3":5,"rotor4":"I","position4":2,"ring4":2,"plugboard":"bq cr di ej kw mt os px uz gh","includeForeignChars":false}},{"name":"enigma","settings":{"model":"M3","reflector":"UKW-B","rotor1":"I","position1":17,"ring1":3,"rotor2":"III","position2":12,"ring2":5,"rotor3":"I","position3":2,"ring3":2,"plugboard":"bq cr di ej kw mt os px uz gh","includeForeignChars":false}},{"name":"text"}],"content":{"data":"intel ligen cepoi ntsto attac konth eeast wallo fthec astle atdaw n"}}}

I don't know javascript but I found a fix by setting a breakpoint in Chrome Dev Tools. On line 735 of Enigma.js it compares the string rotor.turnovers with undefined. I looked up the javascript rules regarding equality and found that triple equal returns false when comparing strings with undefined. On lines 267 and 268 you assign the turnovers for Beta and Gamma rotors to empty string. So I changed the comparison to empty string and it fixed the issue.
Proof:

Sorry, I don't have a fork set up, so I can do a proper test.

I can confirm there is something wrong here. Changing the rotorAtTurnover method did not fix the issue on my side, though. I will investigate further. Thank you very much for your detailed report!

I see that in my last test I accidently used M3 twice. Oops, sorry. It was late (⌒_⌒;)

I identified an issue with the wheel-turnover mechanism in the Enigma M4. I refactored it and got it resolved. Would you verify and report back if the issue has been resolved for you? Thank you!

It's resolved on my end. Thanks.

Again, thank you for taking the time to report this issue. This was a very interesting edge case bringing the Enigma machine simulation closer to its physical counterpart.


added swarm-router by @flavioaiello

Signed-off-by: Brian Christner<EMAIL_ADDRESS>https://github.com/flavioaiello/swarm-router
A «zero config» service name based router for docker swarm mode with a fresh and more secure approach
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines

The project submitted conforms to the quality standards outlined in the contribution guidelines

Go to the contribution guidelines and read it again.

RULES (because you probably didn't read the guidelines):
Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of README.md file.

FORMAT

Use the following format: [Name](Link) - Description.
[Name] should be the title of the project
(Link) should be pointing to a GitHub repository, not to a website
Description. should end with a full stop/period
For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like By [@author](GitHub account)

ORDER: The entries are in lexical order (English letter order)
LABEL (Optional): Add one of the following icons next to the project name like [Name](Link) :icon: - Description.

:heavy_dollar_sign: indicates if one needs a paying subscription to use the project.
:construction: indicates that the project is a work in progress/beta release.
:skull: indicates that the project is obsolete, but still worth mentioning it.

@vegasbrianc there is  a conflict... did you pull master before making the PR ?

oops, closing and creating new


Serve not found

No command 'serve' found, did you mean:
 Command 'pserve' from package 'python-pyramid' (universe)
 Command 'server' from package 'rsplib-legacy-wrappers' (universe)
serve: command not found

This is what is get when I run serve -s build .
I have installed it globally.

the same thing happened to me

@imbarbudiman
I got it fixed by closing the terminal and reopening again. And then I installed it globally. Also make sure to create your builds. :laughing:

Find it with yarn global bin.

heemmm ... I don't really remember why I asked here, haha


[Task]: App Theming Stylesheet Refactor

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
Theme Stylesheets config has become really hard to manage. Need a way to make it simpler and move to the frontend.

Here is my callout mentioned in PR Link

Tested this and LGTM


LGTM.com - false positive This use of variable always evaluates to true.

Description of the false positive
The use of the variable does not always evaluate to true:
 ( !vrDisplay || (vrDisplay && !vrDisplay.isPresenting) )

In the function, vrDisplay can be either undefined or an object.
If it is undefined, !vrDisplay is true and the whole expression always evaluates to true.
If it is an object, !vrDisplay is false and the whole expression evaluates to !vrDisplay.isPresenting which can be true or false.
So I am not sure where is alert is coming from. Perhaps LGTM assumes vrDisplay must be an object.
URL to the alert on the project page on LGTM.com
https://lgtm.com/projects/g/x3dom/x3dom/snapshot/b492cfedcc33a57880ce87b95e90925fae9ec710/files/src/util/VRControllerManager.js?sort=name&dir=ASC&mode=heatmap#V240

The variable use that the alert refers to is the second vrDisplay of that line. It is highlighted if you hover the alert message:

The alert specifically does not warn about the first use of vrDisplay or the entire condition expression.
So your condition expression can be simplified to:
 ( !vrDisplay || !vrDisplay.isPresenting)

Thanks. I could not rediscover the hover functionality ( though I had in the past ).
The second use could evaluate to false if it would be evaluated. It just never is evaluated in that case. So the message is technically correct but requires an unexpected interpretation of 'This use'.
So there some usability aspects but I do not have concrete suggestions.

I agree.
We track such LGTM UI issues internally, do you mind if I close this ticket?


The path is at location.pathname

location.path is undefined.  This is a real bug.
Most browsers just default to the current URL when undefined is passed as
the third argument to history.pushstate, which masks the bug (makes it
irrelevant, actually).
IE11 replaces the last path element with the string "undefined".
Example: "/navigation/playground" becomes "/navigation/undefined".

https://developer.mozilla.org/en-US/docs/Web/API/HTMLHyperlinkElementUtils/pathname
checks out
👍


⚠ Samsung has degraded performance

In 18b7938, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2781 ms

Resolved: Samsung performance has improved in 4c2fd20.


[fix]: Close previous es.Client when creating new one on password fil…

It was observed that the last logged request to the server used a Basic Auth string that resembled the old password, even after a new password was set. This could potentially happen if the es.Client object continued sending pings to the server without being properly closed.
This commit addresses the issue by ensuring that the es.Client object is correctly closed when needed, preventing any further requests with outdated passwords.
Resolves https://github.com/jaegertracing/jaeger/issues/4743

please rebase on recent main branch

addressed in #4863


Bind url config to crowdcop.io domain

The urls only show crowdcop.io, however, we need to bind these urls properly to the domain.

I'm struggling because the masking link doesn't seem to work but the unmasked version refers just fine


feat: Add account_code helper function to AccountProvider

fixes #1132

Codecov Report

Merging #1169 (bdb2dcf) into main (774f158) will increase coverage by 0.07%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1169      +/-   ##
==========================================
+ Coverage   75.19%   75.26%   +0.07%
==========================================
  Files         335      335
  Lines       36350    36444      +94
==========================================
+ Hits        27334    27431      +97
+ Misses       9016     9013       -3

Flag
Coverage Δ

unit-tests
75.26% <0.00%> (+0.07%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/storage/provider/src/providers/latest.rs
66.66% <ø> (ø)

crates/storage/provider/src/test_utils/mock.rs
41.41% <ø> (ø)

crates/storage/provider/src/traits/state.rs
0.00% <0.00%> (ø)

crates/net/network/src/session/handle.rs
35.71% <0.00%> (-14.29%)
:arrow_down:

crates/stages/src/test_utils/test_db.rs
72.02% <0.00%> (-1.00%)
:arrow_down:

crates/primitives/src/net.rs
94.14% <0.00%> (-0.54%)
:arrow_down:

bin/reth/src/node/mod.rs
0.00% <0.00%> (ø)

crates/rpc/rpc/src/eth/error.rs
0.00% <0.00%> (ø)

crates/primitives/src/transaction/util.rs
100.00% <0.00%> (ø)

crates/net/network/src/session/active.rs
86.22% <0.00%> (+0.32%)
:arrow_up:

... and 12 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Automated OCP-69145 @OCP-69146 @OCP-69144 OCP-69143

What I have done in this PR:

Automated OCP-69145 @OCP-69146 @OCP-69144 OCP-69143

for disk size day1 and day2

for security groups day1 and day2

Introduced plan command for some of the testing

Introduced apply command. Need to update others in future

/retest

/retest

/lgtm

/retest

/retest

/lgtm

/approve


[Bug]: Completion not working for my repo due to company policy, and an update to the API is required.

Before Reporting

[X] I have checked FAQ, and there is no solution to my issue
[X] I have searched the existing issues, and there is no existing issue for my issue

What happened?
If we are using 1st party extensions, they must be updated to a newer version to allow Copilot completion to work. Here's a reference:

How to reproduce the bug.
It just happened!
Relevant log output
No response
macOS version
No response
Xcode version
No response
Copilot for Xcode version
No response

It won't be release immediately.
But the latest language server is compatible with the current code so you can simply download the https://github.com/github/copilot.vim/tree/release/dist and replace the folder ~/Library/Application\ Support/dev.com.intii.CopilotForXcode/GitHub\ Copilot/executable/copilot/dist

Released in 0.34.0 beta 3

Released in 0.34.0


Cmake and spec tests

@soundandform with the latest commit, I've passed i32 and i64 spec tests:

Ok, now after running those tests:

I get:

Almost there with integers and floats! ;)


KeyError: 'LOGIN'

Running docker container on Ubunutu, I get the following error:
Starting X virtual framebuffer (Xvfb) in background...

HANDLE_DRIVER:
Starting Bing Rewards Bot...
Traceback (most recent call last):
  File "/app/main.py", line 30, in <module>
    if not os.environ["LOGIN"]:
  File "/usr/lib/python3.10/os.py", line 679, in __getitem__
    raise KeyError(key) from None
KeyError: 'LOGIN'

Not quite sure where to go from here?

Appears to be a similar issue to #60 - I do not have any strange characters in my login password.

Appears to be a similar issue to #60 - I do not have any strange characters in my login password.

Refer to #60 make sure you change the original url provided in .env to microsoft login. Im not sure why it is not originally placed there in the source code...


Large number of UrlTiles cause out of memory error in android

Summary
Many UrlTiles (above 30) cause the android app to get stuck. It seems to be a memory issue, as the logs show frequent memory garbage collection, and after ~30 sec, it gets stuck. The IOS app works OK. Removing the tiles while keeping other objects, such as polygons and markers (in the same order of magnitude as the number of tiles) solves the problem.
Reproducible sample code
mapTiles = nextProps.tileURLs.map((tileURL, index) => {
    if (tileURL) return <UrlTile key={tileURL} urlTemplate={tileURL} />;
    else return null;
 });

 <MapView
           ref={this.setMapRef}
           key={"map"}
           provider={PROVIDER_GOOGLE}
           mapType={"hybrid"}
 >
              {mapTile}
</MapView>

Steps to reproduce
Read above code
Expected result
App should works smoothly with any number of tiles.
Actual result
App gets stuck.
React Native Maps Version
1.3.2
What platforms are you seeing the problem on?
Android
React Native Version
0.69.2
What version of Expo are you using?
Not using Expo
Device(s)
at least Android 12
Additional information
No response

Here is a stack of the out-of-memory crash:
Exception java.lang.OutOfMemoryError: pthread_create (1040KB stack) failed: Try again
at java.lang.Thread.nativeCreate (Thread.java)
at java.lang.Thread.start (Thread.java:884)
at com.google.maps.api.android.lib6.drd.r.g (r.java:13)
at com.google.maps.api.android.lib6.drd.r.i (r.java:3)
at com.google.maps.api.android.lib6.gmm6.store.k.j (k.java:1)
at com.google.maps.api.android.lib6.gmm6.store.f.handleMessage (f.java:75)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at com.google.maps.api.android.lib6.gmm6.store.k.run (k.java:14)

Still relevant


Exceptions are not catched

If I run a functional test and some error occur (a route not defined, for example) no feedback is given. After digging the code I figure out that L4 exceptions when in testing environment were rethrowed (https://github.com/laravel/framework/blob/4.2/src/Illuminate/Foundation/Application.php#L749) but in L5 are catched by application's exception handler. I tried to make the L5 module act also as a handler and worked but is right this approach?

How you handle exceptions in your application is your own decision. If you like to re-throw them in the testing environment you can do that, but I would not do that myself. Your application should handle exceptions gracefully and you should test this. If an exception occurs because you have not yet implemented any code for a specific test, the test fails and you can check the output in the _output directory in your tests directory. This directory contains HTML files with the output for failed tests. If you use the default error handling for Laravel 5 these files will contain output for the exceptions in case an exception is thrown which causes your test to fail.

Yes, I understand your point. I just wanted that exceptions were displayed in console like what happens using Laravel 4.

Above the test fails at step 2 while Laravel 5 just stops at step 3 giving the idea that everything before was correct.

I agree that it is nicer too see the exception in the console. However, the problem is that the default Laravel 5 installation handles all exceptions, so they  cannot be catched by Codeception if you do not change this behavior yourself.

I tried a quickfix making Codeception\Module\Laravel5 implement Illuminate\Contracts\Debug\ExceptionHandler but that solution duplicates code and give too much responsibility to the module. I will treat testing exceptions myself to solve that issue, thanks for the help!


Don't run integration tests on official builds

This has been discussed a few times, thought i'd have a crack at it.
@jaredpar PTAL
Fixes https://github.com/dotnet/razor/issues/8809

/azp run

What was the reasoning on this?

What was the reasoning on this?

If you search for an email in your mailbox called "Proposed Validation matrix" you hopefully can refresh your memory, but I believe this is "the Roslyn way"

Gotcha, thanks. Do we already have the daily integration test run leg that mentioned? I don't want to see this merged without that having been set up.

We have had https://devdiv.visualstudio.com/DevDiv/_build?definitionId=15591&_a=summary for a long time. Did the email mention anything about the daily run needing to be green? 🙈

I'd say lets get that off the floor before merging this.

@Cosifne fixed the integration tests 🎉🎉🎉 https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7792212&view=results 🎉🎉🎉
Will leave things for a week to make sure its stable, and then merge this.

i.e. the build that kicks off on the public queue after merging a PR

If I'm understanding you correctly, no, that would be this pipeline: https://devdiv.visualstudio.com/DevDiv/_build?definitionId=15591&_a=summary
That runs integration tests against main every 6 hours. We'd also still run them in PRs.

We resolved in the weekly tooling sync that we would review the rolling test pipeline, so I'm going to merge this.

Thanks David!


Add a processor to remove all stacktraces from reported exceptions

Q
A

Branch?
master

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Tests pass?
yes

This PR implements a processor that removes all stacktraces from reported exceptions. Its code is a direct porting of the processor added to the Ruby client with getsentry/raven-ruby#233

tbh im not sure why we allowed this in ruby -- this basically breaks any good behavior within Sentry, and probably was accepted because someone kept complaining that they "needed" it. I'd rather just say "dont use Sentry if you just want shitty logs", rather than pretending the app is at all usable without stacktraces. I do think we can support "dont store source code", but we sitll need filenames, function names, and line numbers.

While I agree with you, as specified above this is just a porting of a feature that's available on the Ruby client. It seems that that SDK is the most maintained, so I think until this processor is there it should also be here. Also, I think a user should still be able to do whatever he wants, including not sending stacktraces to Sentry

@ste93cry except then that user emails support and asks why nothing works. I dont disagree that users should have choice, but you can use Sentry, or you can use logs. To use Sentry you need stacks. I'm also going to talk internally about deprecating/removing this from the Ruby SDK since it will cause the same concerns. In general filenames/etc should not be sensitive, and I'd bet the original reason for it was to remove source code (and it was the easiest way).

except then that user emails support and asks why nothing works

I don't understand if this means that you're support team would then receive a lot of emails from people that complain that your product doesn't work because it doesn't show stacktraces, but as this processor is not enabled by default and won't be anyway even in a 2.x version of this package I don't see any reason to not include it.

It seems that that SDK is the most maintained

yyeeeeee boiiii thx :)

please take a look at this article about why this processor could not be so useless in the end.

"To the user" being the operative words in that question. Events are transmitted over SSL to Sentry, there is no information leak.

Also, I think a user should still be able to do whatever he wants, including not sending stacktraces to Sentry

Then they can write their own processor. It's super easy, at least in the Ruby SDK.

I do think we can support "dont store source code", but we sitll need filenames, function names, and line numbers.

I can modify the Ruby processor to do this.
Here's a recap of the arguments in favor of this feature: https://github.com/getsentry/raven-ruby/issues/130
"You're okay with sharing your source code with 3rd party services?" we said, on GitHub.
IMO we might be better off just documenting how to write your own processors (it's trivial) and letting security e-peen-measurers take care of themselves.

+1 on making this a processor included in the repo, but not on by default.

This is what you voted on getsentry/raven-ruby#130. I agree with that phrase, there is no disadvantage in having this processor available to users of your SDK, mostly because it's anyway turned off by default

It's what I said 3 years ago to try and close an issue that was dragging on too long, raised by people who are probably not even Sentry users.
As I also said at the end of that issue, it's unclear to me exactly what data people think is a security concern. The current processor is like a flamethrower - it indiscriminately wipes out all data relating to the source. @dcramer has already proposed a processor which only wipes the actual source code but keeps line numbers/everything else intact.
I'll re-paste the data we're talking about here for clarity:
{"abs_path"=>"/Users/nateberkopec/Documents/code/raven-ruby/spec/raven/processors/removestacktrace_spec.rb",
        "function"=>"block (2 levels) in <top (required)>",
        "pre_context"=>["  end\n", "\n", "  it 'should remove stacktraces' do\n"],
        "post_context"=>
         ["    binding.pry\n", "    expect(data['exception']['stacktrace']).to_not eq(nil)\n", "    result = @processor.process(data)\n"],
        "context_line"=>"    data = Raven::Event.capture_exception(build_exception).to_hash\n",
        "lineno"=>12,
        "in_app"=>false,
        "filename"=>"raven/processors/removestacktrace_spec.rb"}

So, instead of removing all of this, we could remove pre_, post_, and context_line.

As I also said at the end of that issue, it's unclear to me exactly what data people think is a security concern.

According to the article and according to the people that were complaining about security on that issue I think their concern is that showing anything that include source code to third-parties is an information leak. While I agree with this statement, I also agree on that a product like Sentry is totally useless without that informations.

So, instead of removing all of this, we could remove pre_, post_, and context_line

If everyone agree on this, I can make the changes to do it and rename this processor to something like SanitizeStacktraceProcessor. To make everyone happy, we could even make it configurable, so users can decide whether they want to remove everything or only those parts of the stacktrace.

I'd agree that both here (and eventually as a standard), we should provide a way to strip the source code context, but not the entire stacktrace (for the reasons stated).

Should I make it configurable, so that users can choose whether to strip just pre_context, post_context or context_line or should the processor just remove all of them when enabled? Honestly, I think there should be no need to just remove only one of them, but asking is always better 😄

I'd say remove all three with no configuration and we describe it as "removing source code from stack traces". It will still weaken our grouping algorithm but I'm fine with the compromise.
On Fri, Mar 24, 2017 at 5:02 AM -0700, "Stefano Arlandini"<EMAIL_ADDRESS>wrote:
Should I make it configurable, so that users can choose whether to strip just pre_context, post_context or context_line or should the processor just remove all of them when enabled? Honestly, I think there should be no need to just remove only one of them, but asking is always better 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Then PR is ready and tests are green

Thanks!


Fix possible leak in StompSubframeDecoder when a frame not ending with the NULL octet

Motivation:
Currently if a frame not ending with the NULL octet we throws an exception and not release lastContent frame if it present.
Modification:
Release lastContent if it present in exceptional case.
Result:
Fixed possible leak.

one nit.
Done

@amizurov thanks a lot!


Unexpected segmentation fault in pd.read_csv C-engine

Dear developers,
I am using pandas in an application where I need to process large csv files (around 1Gb each) which have approximately 800k records and 400+ columns of mixed type. That is why I decided to use data iterator functionality of pd.read_csv(). When experimenting with chunksize my application seems to crash somewhere inside TextReader__string_convert call.
Here is an archive with a sample CSV data file that seems to cause the crash (it also includes crash dump reports, a copy of the example, and a snapshot of versions of installed python packages).
read_csv_crash.tar.gz
Code Sample
To run this example you would have to extract dataset.csv from the supplied archive.
import pandas as pd
for n_lines in range(82, 87):
    filelike = open("dataset.csv", "r")
    iterator_ = pd.read_csv(filelike, header=None, engine="c",
                            dtype=object, chunksize=n_lines)
    for chunk_ in iterator_:
        print n_lines, chunk_.iloc[0, 0], chunk_.iloc[-1, 0]
    filelike.close()

Please, note that this crash does not seem to occur when the file is less than 260Kib. Also note that playing with low_memory setting did not alleviate the problem.
Expected Output
This code sample outputs this:
82 9999-9 9999-9
82 9999-9 9999-9
82 9999-9 9999-9
83 9999-9 9999-9
83 9999-9 9999-9
83 9999-9 9999-9
84 9999-9 9999-9
84 9999-9 9999-9
Segmentation fault: 11

output of pd.show_versions()
The output of this call is attached to this issue.
pd_show_versions.txt
Python greetings string
Python 2.7.10 (v2.7.10:15c95b7d81dc, May 23 2015, 09:33:12)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin

OSX version
OS Version:            Mac OS X 10.11.5 (15F34)
Model: Macmini6,2, BootROM MM61.0106.B0A, 4 processors, Intel Core i7, 2,6 GHz, 16 GB, SMC 2.8f

For the expected output section, put what you're actually expecting to see, not what you actually saw.  Underneath that, you should then put what you saw.

Can you try your code sample again with the master branch?

While I cannot reproduce this (either with 0.18.1 or master) on Linux (sorry, no access to Mac ATM), the fact that it's crashing with string and object dtype bares resemblance to an earlier segfault we were seeing in a different part of the code.

If the issue persists on master, in parser.pyx, you can find the string_convert function here.  Judging from your versions output, I suspect the segfault is occurring in this function here in fact.  If my suspicion is correct, can you further specify which method call is causing the crash?

Hello,  @gfyoung !
I cloned the master branch, but still the problem persisted.
I've managed to trace the source to a read access beyond the allocated large memory block in either kh_get_str or kh_get_strbox (defined in src/klib/khash.h) in _string_box_factorize (from parser.pyx) called from the very last branch in _string_convert for the remaining 5 lines of the text input. The particular function depends on the na_filter setting.
I debug-patched COLITER_NEXT in tokenizer.h with:
#define COLITER_NEXT(iter, word) do { \
    const int i = *iter.line_start++ + iter.col; \
    word = i < *iter.line_start ? iter.words[i]: ""; \
    printf("%d, %p\n", i, (const void*) iter.words[i]); \
    } while(0)

-- to print out the last address just before the crash. It printed 0 and the address at which the EXC_BAD_ACCESS happens. Any attempt to print the word returned by COLITER_NEXT results in segfault.
I also added this to tokenizer.c:
void _dump(const void *addr, size_t len)
{
    size_t i;
    unsigned char buff[17];
    unsigned char *pc = (unsigned char*)addr;

    printf("%p:\n", addr);
    for (i = 0; i < len; i++) {
        if ((i % 16) == 0) {
            if (i != 0)
                printf("  %s\n", buff);
            printf("  %04x ", i);
        }
        printf(" %02x", pc[i]);
        if ((pc[i] < 0x20) || (pc[i] > 0x7e)) {
            buff[i % 16] = '.';
        } else {
            buff[i % 16] = pc[i];
        }
        buff[(i % 16) + 1] = '\0';
    }
    while ((i % 16) != 0) {
        printf("   ");
        i++;
    }
    printf("  %s\n", buff);
}

I borrowed it with simplifications from this gist to dump memory contents of parser->words and parser->stream in a call to _string_box_factorize. It turns out that just before the crash the pointers in parser->words point to a memory region starting with the address that causes the crash.
I strongly suspect that this problem is specific to OS X memory allocation.
PS: Here is a snippet which does not use the dataset.csv file, and instead uses StringIO, but still crashes with segfault.
import pandas as pd
from cStringIO import StringIO
record_ = """9999-9,99:99,,,,ZZ,ZZ,,,ZZZ-ZZZZ,.Z-ZZZZ,-9.99,,,9.99,ZZZZZ,,-99,9,ZZZ-ZZZZ,ZZ-ZZZZ,,9.99,ZZZ-ZZZZZ,ZZZ-ZZZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,999,ZZZ-ZZZZ,,ZZ-ZZZZ,,,,,ZZZZ,ZZZ-ZZZZZ,ZZZ-ZZZZ,,,9,9,9,9,99,99,999,999,ZZZZZ,ZZZ-ZZZZZ,ZZZ-ZZZZ,9,ZZ-ZZZZ,9.99,ZZ-ZZZZ,ZZ-ZZZZ,,,,ZZZZ,,,ZZ,ZZ,,,,,,,,,,,,,9,,,999.99,999.99,,,ZZZZZ,,,Z9,,,,,,,ZZZ,ZZZ,,,,,,,,,,,ZZZZZ,ZZZZZ,ZZZ-ZZZZZZ,ZZZ-ZZZZZZ,ZZ-ZZZZ,ZZ-ZZZZ,ZZ-ZZZZ,ZZ-ZZZZ,,,999999,999999,ZZZ,ZZZ,,,ZZZ,ZZZ,999.99,999.99,,,,ZZZ-ZZZ,ZZZ-ZZZ,-9.99,-9.99,9,9,,99,,9.99,9.99,9,9,9.99,9.99,,,,9.99,9.99,,99,,99,9.99,9.99,,,ZZZ,ZZZ,,999.99,,999.99,ZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,,,ZZZZZ,ZZZZZ,ZZZ,ZZZ,9,9,,,,,,ZZZ-ZZZZ,ZZZ999Z,,,999.99,,999.99,ZZZ-ZZZZ,,,9.999,9.999,9.999,9.999,-9.999,-9.999,-9.999,-9.999,9.999,9.999,9.999,9.999,9.999,9.999,9.999,9.999,99999,ZZZ-ZZZZ,,9.99,ZZZ,,,,,,,,ZZZ,,,,,9,,,,9,,,,,,,,,,ZZZ-ZZZZ,ZZZ-ZZZZ,,ZZZZZ,ZZZZZ,ZZZZZ,ZZZZZ,,,9.99,,ZZ-ZZZZ,ZZ-ZZZZ,ZZ,999,,,,ZZ-ZZZZ,ZZZ,ZZZ,ZZZ-ZZZZ,ZZZ-ZZZZ,,,99.99,99.99,,,9.99,9.99,9.99,9.99,ZZZ-ZZZZ,,,ZZZ-ZZZZZ,,,,,-9.99,-9.99,-9.99,-9.99,,,,,,,,,ZZZ-ZZZZ,,9,9.99,9.99,99ZZ,,-9.99,-9.99,ZZZ-ZZZZ,,,,,,,ZZZ-ZZZZ,9.99,9.99,9999,,,,,,,,,,-9.9,Z/Z-ZZZZ,999.99,9.99,,999.99,ZZ-ZZZZ,ZZ-ZZZZ,9.99,9.99,9.99,9.99,9.99,9.99,,ZZZ-ZZZZZ,ZZZ-ZZZZZ,ZZZ-ZZZZZ,ZZZ-ZZZZZ,ZZZ-ZZZZZ,ZZZ,ZZZ,ZZZ,ZZZ,9.99,,,-9.99,ZZ-ZZZZ,-999.99,,-9999,,999.99,,,,999.99,99.99,,,ZZ-ZZZZZZZZ,ZZ-ZZZZ-ZZZZZZZ,,,,ZZ-ZZ-ZZZZZZZZ,ZZZZZZZZ,ZZZ-ZZZZ,9999,999.99,ZZZ-ZZZZ,-9.99,-9.99,ZZZ-ZZZZ,99:99:99,,99,99,,9.99,,-99.99,,,,,,9.99,ZZZ-ZZZZ,-9.99,-9.99,9.99,9.99,,ZZZ,,,,,,,ZZZ,ZZZ,,,,,"""
csv_data = "\n".join([record_]*173) + "\n"

for _ in range(2):
    iterator_ = pd.read_csv(StringIO(csv_data), header=None, engine="c",
                            dtype=object, chunksize=84, na_filter=False)
    for chunk_ in iterator_:
        print chunk_.iloc[0, 0], chunk_.iloc[-1, 0]
    print ">>>NEXT"

The problems seems to be in the parser_trim_buffers as it appears not to move word pointers.
If I swap blocks L1224 -- L1237 (/* trim stream */) and L1239 -- L1256(/* trim words, word_starts */) and then copy the initialization of parser->words from make_stream_space to the trim words block (as shown in the snippet below), the problem goes away.
Here is a new version of parser_trim_buffers

int parser_trim_buffers(parser_t *self) {
    /*
      Free memory
     */
    size_t new_cap;
    void *newptr;

    int i;

    /* trim words, word_starts */
    new_cap = _next_pow2(self->words_len) + 1;
    if (new_cap < self->words_cap) {
        TRACE(("parser_trim_buffers: new_cap < self->words_cap\n"));
        newptr = safe_realloc((void*) self->words, new_cap * sizeof(char*));
        if (newptr == NULL) {
            return PARSER_OUT_OF_MEMORY;
        } else {
            self->words = (char**) newptr;
        }
        newptr = safe_realloc((void*) self->word_starts, new_cap * sizeof(int));
        if (newptr == NULL) {
            return PARSER_OUT_OF_MEMORY;
        } else {
            self->word_starts = (int*) newptr;
            self->words_cap = new_cap;
        }
    }

    /* trim stream */
    new_cap = _next_pow2(self->stream_len) + 1;
    TRACE(("parser_trim_buffers: new_cap = %zu, stream_cap = %zu, lines_cap = %zu\n",
           new_cap, self->stream_cap, self->lines_cap));
    if (new_cap < self->stream_cap) {
        TRACE(("parser_trim_buffers: new_cap < self->stream_cap, calling safe_realloc\n"));
        newptr = safe_realloc((void*) self->stream, new_cap);
        if (newptr == NULL) {
            return PARSER_OUT_OF_MEMORY;
        } else {
            // realloc sets errno when moving buffer?
            if (self->stream != newptr) {
                // uff
                /* TRACE(("Moving word pointers\n")) */

                self->pword_start = newptr + self->word_start;

                for (i = 0; i < self->words_len; ++i)
                {
                    self->words[i] = newptr + self->word_starts[i];
                }
            }

            self->stream = newptr;
            self->stream_cap = new_cap;

        }
    }

...

    return 0;
}

Awesome that you were able to fix your segfault!  Here's what I would do now:

run all of the unit tests to see if your changes break any existing functionality

if they don't, then submit this as a PR so that all of us can have a look!

if they do cause failures, then I'll leave it up to you whether you want to investigate the failure causes. Feel free to provide a patch that we can clone and figure out.

I issued a pull request (#13788), however there was one failed test and several deprecation warnings:
FAIL: test_round_trip_frame_sep (pandas.io.tests.test_clipboard.TestClipboard)

that test is ok, its not currently engaged on travis and fails on linux/macosx (and already has an outstanding issue).
deprecation warnings are ok (though I do try to eliminate them periodically).


feat: add node type

add cert for access by HTTPS
use mkcert.

ref
https://dev.classmethod.jp/articles/vite-https-localhost/


Browser configuration

I'm trying to set things like user agent, encoding, accept=text and so on for the engine.
Should I  use IResourceProvider?  I cannot find any documentation on how to do this.

I added the sample to the documentation:
var engine = EngineBuilder.New().ConfigureResourceProvider(x => x.Notify(
    request => { /*modify request here */},
    response => { /*handle response */}
)).Build();

Request handler function passed to the Notify method called before the request is sent. The request object is mutable, so you can modify it adding headers.
Another way is to implement own ResourceProvider that inherits IResourceProvider and pass it to EngineBuilder:
var engine = EngineBuilder.New().SetResourceProvider(yourResourceProvider).Build();

Thanks.  I'm using vb.net so I'm having to translate this stuff.  Enginebuilder does not seem to exist in the nuget package (v2.2.6).  I am trying to use the resourceprovider approach:
Dim iRP As IResourceProvider = New ResourceProviderBuilder().Http().Notify('what goes here for request and response?)
Thanks again.

Dim iRP As IResourceProvider = New ResourceProviderBuilder().Http().Notify(
            Sub(request As Request)
                rem; do something with request
            End Sub,
            Sub(response As ReceivedEventArguments)
                rem; do something with response
            End Sub)
`


FIX - adjust get trades endpoint

Description
This PR makes a few small changes to the getTrades endpoint to allow the endpoint to function consistently with other RPCs. We've added functionality that was specific to ccxt, that is now removed in this PR including:

removes info from the getTrades rpc
removes millisecond timestamps from a trades response and instead opts to use nanoseconds

CCXT will handle info and the millisecond timestamps on its own as we expect the daemon to work in nanoseconds
Related PRs
List related PRs if applicable
Todos

[x] Tests
[x] Documentation
[x] Link to Trello

 add fetchTrades to ccxt implementation


Disable CORD transform until URL issue is sorted

#83 didn't work unfortunately, unclear why. Apparently this isn't the "good" version of that file.
This PR temporarily disables CORD transform until #79 is fixed, so we can output RDF (#80) .

Closing this - James says the original URL is fixed

Per convo with @deepakunni3, reopening and merging this to temporarily disable CORD19 ingest, to get Jenkins pipeline running to completion. Will re-enable this with Deepak's forthcoming PR to update CORD19 ingest to deal with new updated data file.


#291 Updated codegen and templates for relations

Added support of path:
/e3/{id}/e2/{tid}
/e2/{id}/e3s
for GET, POST, PUT, DELETE operations

It was implemented in scope of #321 and #318


Hi there.. looking for update to support jupyter lab 4.0

Title says it all :)
Nice theme!

Please, please, update the theme


Updating layers or styles in WMSTileLayer does not have any effect

I've been trying to implement a simple dash script where a select control will change the displayed layer in a WMSTileLayer. However, changing layers or styles in the callback doesn't seem to have any effect.
Here is a sample code of my attemp. This code only changes the layers property for sample puporses, but the same behaviour is observed when trying to change styles.
from dash import Dash, html, dcc, callback, Output, Input, State

import dash_bootstrap_components as dbc
import dash_leaflet as dl

# Initialize the app with a Dash Bootstrap theme
external_stylesheets = [dbc.themes.CERULEAN]
app = Dash(__name__, external_stylesheets=external_stylesheets)

# App layout
app.layout = dbc.Container([
    dbc.Navbar(  # Header
        dbc.Container(
            [
                dbc.Row(
                    [
                        dbc.Col(dbc.NavbarBrand("WMS Test", href="#")),
                    ],
                    align="center",
                    className="g-0",  # Remove gutters between columns
                ),
                dbc.NavbarToggler(id="navbar-toggler"),
                dbc.Nav(
                    [
                        dbc.NavItem(dbc.NavLink("Home", href="#")),
                        dbc.NavItem(dbc.NavLink("Help", href="#")),
                    ],
                    className="ms-auto",  # Move navigation links to the right
                    navbar=True,
                ),
            ]
        ),
        color="primary",
        dark=True,
        style={'margin-bottom': '10px'}
    ),

    dbc.Row([
        dbc.Col([
            dbc.Accordion(
                [
                    dbc.AccordionItem(
                        [

                            dbc.Label("Layer"),
                            dbc.Select(
                                id="layerId",
                                options=[
                                    {"label": "Fondo", "value": "fondo"},
                                    {"label": "Mosaico", "value": "Mosaico"},
                                    {"label": "OI.OrthoimageCoverage", "value": "OI.OrthoimageCoverage"},
                                    {"label": "OI.MosaicElement", "value": "OI.MosaicElement"},
                                ],
                                value="fondo",
                                style={'margin-bottom': '10px'}
                            ),
                        ],
                        title="Enter data"
                    ),
                ],
                start_collapsed=False,
            ),
        ], width=3),

        dbc.Col([
            dl.Map([
                dl.TileLayer(),
                dl.WMSTileLayer(
                    url="https://www.ign.es/wms-inspire/pnoa-ma",
                    layers="fondo",
                    format="image/png",
                    transparent=True,
                    id='wms_map'
                ),

            ], center=[37.5, -4], zoom=14, style={'height': '94vh'})
        ], width=9),
    ]),

], fluid=True)

# Callback to update the selected layer in WMSTileLayer
@callback(
    Output('wms_map', 'layers'),
    Input('layerId', 'value'),
    State("wms_map", "layers"),
    #prevent_initial_call=True
)
def changeLayer(selected_layer, current_layer):
    print("new: ", selected_layer)
    print("current: ", current_layer)

    return selected_layer

# Run the app
if __name__ == '__main__':
    app.run(debug=True)

Hey @jajberni, the documentation is a bit obscure on how to change the layers prop but you should be able to use params to do it:
# Callback to update the selected layer in WMSTileLayer
@callback(
    Output('wms_map', 'params'),
    Input('layerId', 'value'),
    State('wms_map', 'params'),
    #prevent_initial_call=True
)
def changeLayer(selected_layer, current_layer):
    print("new: ", selected_layer)
    print("current: ", current_layer)

    return dict(layers=selected_layer)

Thank you @prl900! You are completely right. Using the params instead of the property worked perfectly. It would be good to fix the documentation as it's very confusing now.
Closing the issue.


resource ID has an invalid format Dockerfile

terrascan version: v1.15.2 (via Docker Image Tag Latest)
Operating System: Docker Container

Description
{"level":"error","time":"2022-07-27T22:40:57.851Z","file":"opa/engine.go:419","msg":"resource ID has an invalid format Dockerfile"}

opa/engine.go:419
What I Did

Checked issues in terrascan repo (none)
Checked Dockerfiles, all are correct format

Is it possible to have a Flag to skip errors during the engine's FindAllResourcesByID error check?

Hi @nhalstead
Could you please share a sample docker file code where you see these errors?
Thanks

Hi @gaurav-gogia I was able to bypass the exit code error BUT the output JSON is messed up with error values when it should come out on Standard Error, not Standard Output.
Command:
terrascan scan --output json --log-type console --use-colors false > report.json 2> error.txt || true

error.txt
Unable to find image 'tenable/terrascan:latest' locally
latest: Pulling from tenable/terrascan
2408cc74d12b: Already exists
...
6eb609282c41: Pull complete
Digest: sha256:e36aed65df132ffb722b6b524f703eb819cbf17efb7ba5a9397a4b908e87e30e
Status: Downloaded newer image for tenable/terrascan:latest
2022-08-29T20:56:55.100Z	error	opa/engine.go:419	resource ID has an invalid format Dockerfile

report.json:
ERROR: json: cannot unmarshal number into Go struct field Function_Environment.Properties.Environment.Variables of type string
{
  "results": {
    "scan_errors": [
      {
...

@nhalstead
I see. That might be a separate issue. Might require some design changes around how errors are being handled. Currently all logs are written to Standard Output, AFAIK.
Could you please open a separate issue for this?

Closed in favour of 1378

Hi @gaurav-gogia are you able to get a release of the changes?


Firebase iOS Initialization Crash, mostly on ios 12.1

Hi,
I am not sure why this problem occurs but there is a wierd crash on ios side. I am saying wierd because I haven't been able to reproduce myself. It doesn't crash on Editor, and most of the devices. I am getting crash reports from iTunes and that shows around 10% of the devices are crashes. Most of the IOS 12.1 devices are effected by this. I have even tried to update my test devices to get this crash but I couldn't. I even tried to putting try-catch the all firebase Initialization, not to make app to crash, but it seems it is still happening.
Is there any other one who have this problem?
He is how it looks like in Xcode Crashes side

Here is the Crash Stack info below. This log looks similar App Initialization on editor but I am not 100% sure is this really happening because of this.
InterfaceFuncInvoker0<int>::Invoke(unsigned int, Il2CppClass*, Il2CppObject*) + 76
FirebaseLogger_LogMessage_m2677119794
ReversePInvokeWrapper_FirebaseApp_LogMessage_m43..
firebase::ApplogCallback(firebase:LogLevel, char const..
firebase::LogMessaageWithCallbackV(firebase::LogLevel,
firebase::LogWarning(char const*,
firebase::CppInstanceManager<firebase::App>:::~CppIns...

Firebase SKD: 5.4.3
Bitcode enabled : false;
Used Firebase Components,
Auth
Database,
Cloud Messaging,
Remote Config,
Functions
InstanceID
Analytics

@ozbra this is a dupe of #271 we're working on it.


bot.on('messageCreate', async msg => {

Hey, please update Node.js to version 8 or above and try again.

Is the bot already running in a different terminal?

@LegitEzra no @Dragory I did, I think it fixed


Build Fails with "useRichPush": true

EAS build fails with useRichPush set to true. Only works with   "useRichPush": false,
xCode log -
xcode-build-dc17f042-d9e6-4363-9fc6-13b0562634d6.log
"expo": "~48.0.18",
"react-native": "0.71.8",
"customerio-expo-plugin": "^1.0.0-beta.12",
"customerio-reactnative": "3.1.3",
Plugin
    "customerio-expo-plugin",
                {
                    "android": {
                        "googleServicesFile": "./google-services-staging.json"
                    },
                    "ios": {
                        "push notification": {
                            "useRichPush": true,
                            "env": {
                                "siteId": "{SECRET_ID}",
                                "apiKey": "{SECRET_KEY}",
                                "region": "US"
                            }
                        }
                    }
                }

iOS specifc
    [
                "expo-build-properties",
                {
                    "ios": {
                        "deploymentTarget": "13.0"
                    }
                }
            ]

iOS Rich Push
     "build": {
            "experimental": {
                "ios": {
                    "appExtensions": [
                        {
                            "targetName": "NotificationService",
                            "bundleIdentifier": "${appIdentifier}.richpush"
                        }
                    ]
                }
            }
        },

Init
const env = new CustomerIOEnv();
env.siteId = Constants.expoConfig?.extra?.CUSTOMER_IO_SITE_ID;
env.apiKey = Constants.expoConfig?.extra?.CUSTOMER_IO_API_KEY;
env.region = Region.US;

const data = new CustomerioConfig();
data.logLevel = __DEV__ ? CioLogLevel.debug : CioLogLevel.error;
data.autoTrackDeviceAttributes = true;
data.autoTrackPushEvents = true;
data.enableInApp = true;

CustomerIO.initialize(env, data);

Build fails at "Run Fastline" step. Log:
Creating Gymfile

Gymfile created

Successfully loaded '/Users/expo/workingdir/build/apps/native/ios/Gymfile' 📄

+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

|                                                                  Detected Values from './Gymfile'                                                                   |

+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

| suppress_xcode_output | true                                                                                |

| clean                 | false                                                                                |

| scheme                | JockMKTStaging                                                                                |

| configuration         | Release                                                                                |

| export_options        |                                                                                |

| export_xcargs         | OTHER_CODE_SIGN_FLAGS="--keychain /var/folders/rp/_x4mwf8x2f52ml0n3qt65jw80000gn/T/turtle-v2-4719714f-aa9b-4a01-b9ee-5d991d1640ac.keychain" |

| disable_xcpretty      | true                                                                                |

| buildlog_path         | /Users/expo/workingdir/logs                                                                                |

| output_directory      | ./build                                                                                |

+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

Resolving Swift Package Manager dependencies...

$ xcodebuild -resolvePackageDependencies -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release

▸ Command line invocation:

▸     /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release

▸ User defaults from command line:

▸     IDEPackageSupportUseBuiltinSCM = YES

▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:

▸ { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:0000FE00-66D45333AEB93EDA }

▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }

▸ { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }

▸ { platform:iOS Simulator, id:94EE5B62-6A73-4410-8C64-A56FBFD9C55D, OS:16.2, name:iPad (10th generation) }

▸ { platform:iOS Simulator, id:537FF0C8-8B14-4E2E-9828-0ED246BE9E38, OS:16.2, name:iPad Air (5th generation) }

▸ { platform:iOS Simulator, id:777A520C-1C1B-484A-99C6-35943FA97067, OS:16.2, name:iPad Pro (11-inch) (4th generation) }

▸ { platform:iOS Simulator, id:A5447295-3264-4816-9C78-50E5F35C1122, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }

▸ { platform:iOS Simulator, id:067F74D9-EEC3-4066-B8A8-B3EAD0EE5649, OS:16.2, name:iPad mini (6th generation) }

▸ { platform:iOS Simulator, id:3A1FD6BA-A84C-4728-A0AA-E7D9DF147BA7, OS:16.2, name:iPhone 14 }

▸ { platform:iOS Simulator, id:5D252FD0-2816-4FAE-B85D-C29DC8D2C73C, OS:16.2, name:iPhone 14 Plus }

▸ { platform:iOS Simulator, id:AA475350-BBB4-4568-A722-4528CF187FA8, OS:16.2, name:iPhone 14 Pro }

▸ { platform:iOS Simulator, id:01B24393-FC59-4FEC-87FD-338E47BABDAE, OS:16.2, name:iPhone 14 Pro Max }

▸ { platform:iOS Simulator, id:88B2387A-FF6D-4979-9155-B06611A97148, OS:16.2, name:iPhone SE (3rd generation) }

▸ resolved source packages:

$ xcodebuild -showBuildSettings -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release

[stderr]
--- xcodebuild: WARNING: Using the first of multiple matching destinations:

[stderr]
{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:0000FE00-66D45333AEB93EDA }

[stderr]
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }

[stderr]
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }

[stderr]
{ platform:iOS Simulator, id:94EE5B62-6A73-4410-8C64-A56FBFD9C55D, OS:16.2, name:iPad (10th generation) }

[stderr]
{ platform:iOS Simulator, id:537FF0C8-8B14-4E2E-9828-0ED246BE9E38, OS:16.2, name:iPad Air (5th generation) }

[stderr]
{ platform:iOS Simulator, id:777A520C-1C1B-484A-99C6-35943FA97067, OS:16.2, name:iPad Pro (11-inch) (4th generation) }

[stderr]
{ platform:iOS Simulator, id:A5447295-3264-4816-9C78-50E5F35C1122, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }

[stderr]
{ platform:iOS Simulator, id:067F74D9-EEC3-4066-B8A8-B3EAD0EE5649, OS:16.2, name:iPad mini (6th generation) }

[stderr]
{ platform:iOS Simulator, id:3A1FD6BA-A84C-4728-A0AA-E7D9DF147BA7, OS:16.2, name:iPhone 14 }

[stderr]
{ platform:iOS Simulator, id:5D252FD0-2816-4FAE-B85D-C29DC8D2C73C, OS:16.2, name:iPhone 14 Plus }

[stderr]
{ platform:iOS Simulator, id:AA475350-BBB4-4568-A722-4528CF187FA8, OS:16.2, name:iPhone 14 Pro }

[stderr]
{ platform:iOS Simulator, id:01B24393-FC59-4FEC-87FD-338E47BABDAE, OS:16.2, name:iPhone 14 Pro Max }

[stderr]
{ platform:iOS Simulator, id:88B2387A-FF6D-4979-9155-B06611A97148, OS:16.2, name:iPhone SE (3rd generation) }

Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...

[stderr]
2023-07-20 11:25:22.263 xcodebuild[11574:26861] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition

[stderr]
--- xcodebuild: WARNING: Using the first of multiple matching destinations:

[stderr]
{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:0000FE00-66D45333AEB93EDA }

[stderr]
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }

[stderr]
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }

[stderr]
{ platform:iOS Simulator, id:94EE5B62-6A73-4410-8C64-A56FBFD9C55D, OS:16.2, name:iPad (10th generation) }

[stderr]
{ platform:iOS Simulator, id:537FF0C8-8B14-4E2E-9828-0ED246BE9E38, OS:16.2, name:iPad Air (5th generation) }

[stderr]
{ platform:iOS Simulator, id:777A520C-1C1B-484A-99C6-35943FA97067, OS:16.2, name:iPad Pro (11-inch) (4th generation) }

[stderr]
{ platform:iOS Simulator, id:A5447295-3264-4816-9C78-50E5F35C1122, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }

[stderr]
{ platform:iOS Simulator, id:067F74D9-EEC3-4066-B8A8-B3EAD0EE5649, OS:16.2, name:iPad mini (6th generation) }

[stderr]
{ platform:iOS Simulator, id:3A1FD6BA-A84C-4728-A0AA-E7D9DF147BA7, OS:16.2, name:iPhone 14 }

[stderr]
{ platform:iOS Simulator, id:5D252FD0-2816-4FAE-B85D-C29DC8D2C73C, OS:16.2, name:iPhone 14 Plus }

[stderr]
{ platform:iOS Simulator, id:AA475350-BBB4-4568-A722-4528CF187FA8, OS:16.2, name:iPhone 14 Pro }

[stderr]
{ platform:iOS Simulator, id:01B24393-FC59-4FEC-87FD-338E47BABDAE, OS:16.2, name:iPhone 14 Pro Max }

[stderr]
{ platform:iOS Simulator, id:88B2387A-FF6D-4979-9155-B06611A97148, OS:16.2, name:iPhone SE (3rd generation) }

[stderr]
2023-07-20 11:25:23.094 xcodebuild[11589:26971] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition

Detected provisioning profile mapping: {:"com.jockmkt.staging.eas"=>"57226549-1ffe-42c5-8a18-17667b4411b7"}

+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

|                                                                                Summary for gym 2.211.0                                                                                |

+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

| workspace                                                   | ./JockMKTStaging.xcworkspace                                                                                |

| scheme                                                      | JockMKTStaging                                                                                |

| clean                                                       | false                                                                                |

| output_directory                                            | ./build                                                                                |

| output_name                                                 | JockMKTStaging                                                                                |

| configuration                                               | Release                                                                                |

| silent                                                      | false                                                                                |

| skip_package_ipa                                            | false                                                                                |

| skip_package_pkg                                            | false                                                                                |

| export_options.method                                       | app-store                                                                                |

| export_options.provisioningProfiles.com.jockmkt.staging.eas | 57226549-1ffe-42c5-8a18-17667b4411b7                                                                                |

| export_xcargs                                               | OTHER_CODE_SIGN_FLAGS="--keychain /var/folders/rp/_x4mwf8x2f52ml0n3qt65jw80000gn/T/turtle-v2-4719714f-aa9b-4a01-b9ee-5d991d1640ac.keychain" |

| build_path                                                  | /Users/expo/Library/Developer/Xcode/Archives/2023-07-20                                                                                |

| result_bundle                                               | false                                                                                |

| buildlog_path                                               | /Users/expo/workingdir/logs                                                                                |

| destination                                                 | generic/platform=iOS                                                                                |

| suppress_xcode_output                                       | true                                                                                |

| xcodebuild_formatter                                        | xcpretty                                                                                |

| disable_xcpretty                                            | true                                                                                |

| skip_profile_detection                                      | false                                                                                |

| xcodebuild_command                                          | xcodebuild                                                                                |

| skip_package_dependencies_resolution                        | false                                                                                |

| disable_package_automatic_updates                           | false                                                                                |

| use_system_scm                                              | false                                                                                |

| xcode_path                                                  | /Applications/Xcode.app                                                                                |

+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

$ set -o pipefail && xcodebuild -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release -destination 'generic/platform=iOS' -archivePath /Users/expo/Library/Developer/Xcode/Archives/2023-07-20/JockMKTStaging\ 2023-07-20\ 11.25.23.xcarchive archive | tee /Users/expo/workingdir/logs/JockMKTStaging-JockMKTStaging.log > /dev/null

    Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

    Run script build phase '[CP-User] Generate app.manifest for expo-updates' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXUpdates' from project 'Pods')

    Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')

    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')

    Run script build phase 'Upload Debug Symbols to Sentry' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')

▸ ** ARCHIVE FAILED **

** ARCHIVE FAILED **

Exit status: 65

+-------------+-------------------------+

|           Build environment           |

+-------------+-------------------------+

| xcode_path  | /Applications/Xcode.app |

| gym_version | 2.211.0                 |

| sdk         | iPhoneOS16.2.sdk        |

+-------------+-------------------------+

Looks like fastlane ran into a build/archive error with your project

It's hard to tell what's causing the error, so we wrote some guides on how

to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/

Before submitting an issue on GitHub, please follow the guide above and make

sure your project is set up correctly.

fastlane uses `xcodebuild` commands to generate your binary, you can see the

the full commands printed out in yellow in the above log.

Make sure to inspect the output above, as usually you'll find more error information there

[stderr]
[!] Error building the application - see the log above

Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.

Hi @sergey-king
Thank you for reaching out. I apologize for any inconvenience this may have caused.
To help resolve the issue, please confirm that you are able to run the expo prebuild --clean command when trying to prebuild locally. I am also trying to reproduce the issue so that I can assist you better.
Thank you for your patience.

Hi @ami-aman
Thank you for looking at this! Yes, I confirm I'm able to run expo prebuild --clean. I'm experiencing this build error after a successful prebuild

Thanks for confirming @sergey-king !
I haven't been able to reproduce the issue myself, but I think it might be related to the target name. Our plugin creates an extension named CIONotificationService, but you're setting the targetName property to NotificationService in the app extension configuration. Based on the logs you shared, it looks like the issue is with the target name.
   "build": {
            "experimental": {
                "ios": {
                    "appExtensions": [
                        {
                            "targetName": "NotificationService",
                            "bundleIdentifier": "${appIdentifier}.richpush"
                        }
                    ]
                }
            }
        },

Would you mind trying to change the target name to CIONotificationService and creating a build? This might resolve the issue.
Let me know if you have any other questions.

@ami-aman I've followed the official docs here - https://customer.io/docs/sdk/expo/getting-started/#ios-specific-instructions
It does state "targetName": "NotificationService",.
I'll try to update it to CIONotificationService and report back. Thanks

iOS build failed with  "targetName": "CIONotificationService", and  "useRichPush": true,
Xcode logs -
xcode-build-ac24fbc3-4cef-46a9-a696-ed00617d98ce.log
FastLine log
Creating Gymfile

Gymfile created

Successfully loaded '/Users/expo/workingdir/build/apps/native/ios/Gymfile' 📄

+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

|                                                                  Detected Values from './Gymfile'                                                                   |

+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

| suppress_xcode_output | true                                                                                |

| clean                 | false                                                                                |

| scheme                | JockMKTStaging                                                                                |

| configuration         | Release                                                                                |

| export_options        |                                                                                |

| export_xcargs         | OTHER_CODE_SIGN_FLAGS="--keychain /var/folders/rp/_x4mwf8x2f52ml0n3qt65jw80000gn/T/turtle-v2-54ce9a92-c4f8-4c08-bcc0-5a0bd1f51f56.keychain" |

| disable_xcpretty      | true                                                                                |

| buildlog_path         | /Users/expo/workingdir/logs                                                                                |

| output_directory      | ./build                                                                                |

+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

Resolving Swift Package Manager dependencies...

$ xcodebuild -resolvePackageDependencies -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release

▸ Command line invocation:

▸     /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release

▸ User defaults from command line:

▸     IDEPackageSupportUseBuiltinSCM = YES

▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:

▸ { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:0000FE00-66D45333AEB93EDA }

▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }

▸ { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }

▸ { platform:iOS Simulator, id:94EE5B62-6A73-4410-8C64-A56FBFD9C55D, OS:16.2, name:iPad (10th generation) }

▸ { platform:iOS Simulator, id:537FF0C8-8B14-4E2E-9828-0ED246BE9E38, OS:16.2, name:iPad Air (5th generation) }

▸ { platform:iOS Simulator, id:777A520C-1C1B-484A-99C6-35943FA97067, OS:16.2, name:iPad Pro (11-inch) (4th generation) }

▸ { platform:iOS Simulator, id:A5447295-3264-4816-9C78-50E5F35C1122, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }

▸ { platform:iOS Simulator, id:067F74D9-EEC3-4066-B8A8-B3EAD0EE5649, OS:16.2, name:iPad mini (6th generation) }

▸ { platform:iOS Simulator, id:3A1FD6BA-A84C-4728-A0AA-E7D9DF147BA7, OS:16.2, name:iPhone 14 }

▸ { platform:iOS Simulator, id:5D252FD0-2816-4FAE-B85D-C29DC8D2C73C, OS:16.2, name:iPhone 14 Plus }

▸ { platform:iOS Simulator, id:AA475350-BBB4-4568-A722-4528CF187FA8, OS:16.2, name:iPhone 14 Pro }

▸ { platform:iOS Simulator, id:01B24393-FC59-4FEC-87FD-338E47BABDAE, OS:16.2, name:iPhone 14 Pro Max }

▸ { platform:iOS Simulator, id:88B2387A-FF6D-4979-9155-B06611A97148, OS:16.2, name:iPhone SE (3rd generation) }

▸ resolved source packages:

$ xcodebuild -showBuildSettings -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release

[stderr]
--- xcodebuild: WARNING: Using the first of multiple matching destinations:

[stderr]
{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:0000FE00-66D45333AEB93EDA }

[stderr]
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }

[stderr]
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }

[stderr]
{ platform:iOS Simulator, id:94EE5B62-6A73-4410-8C64-A56FBFD9C55D, OS:16.2, name:iPad (10th generation) }

[stderr]
{ platform:iOS Simulator, id:537FF0C8-8B14-4E2E-9828-0ED246BE9E38, OS:16.2, name:iPad Air (5th generation) }

[stderr]
{ platform:iOS Simulator, id:777A520C-1C1B-484A-99C6-35943FA97067, OS:16.2, name:iPad Pro (11-inch) (4th generation) }

[stderr]
{ platform:iOS Simulator, id:A5447295-3264-4816-9C78-50E5F35C1122, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }

[stderr]
{ platform:iOS Simulator, id:067F74D9-EEC3-4066-B8A8-B3EAD0EE5649, OS:16.2, name:iPad mini (6th generation) }

[stderr]
{ platform:iOS Simulator, id:3A1FD6BA-A84C-4728-A0AA-E7D9DF147BA7, OS:16.2, name:iPhone 14 }

[stderr]
{ platform:iOS Simulator, id:5D252FD0-2816-4FAE-B85D-C29DC8D2C73C, OS:16.2, name:iPhone 14 Plus }

[stderr]
{ platform:iOS Simulator, id:AA475350-BBB4-4568-A722-4528CF187FA8, OS:16.2, name:iPhone 14 Pro }

[stderr]
{ platform:iOS Simulator, id:01B24393-FC59-4FEC-87FD-338E47BABDAE, OS:16.2, name:iPhone 14 Pro Max }

[stderr]
{ platform:iOS Simulator, id:88B2387A-FF6D-4979-9155-B06611A97148, OS:16.2, name:iPhone SE (3rd generation) }

Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...

[stderr]
2023-07-21 11:24:51.095 xcodebuild[11551:26789] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition

[stderr]
--- xcodebuild: WARNING: Using the first of multiple matching destinations:

[stderr]
{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:0000FE00-66D45333AEB93EDA }

[stderr]
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }

[stderr]
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }

[stderr]
{ platform:iOS Simulator, id:94EE5B62-6A73-4410-8C64-A56FBFD9C55D, OS:16.2, name:iPad (10th generation) }

[stderr]
{ platform:iOS Simulator, id:537FF0C8-8B14-4E2E-9828-0ED246BE9E38, OS:16.2, name:iPad Air (5th generation) }

[stderr]
{ platform:iOS Simulator, id:777A520C-1C1B-484A-99C6-35943FA97067, OS:16.2, name:iPad Pro (11-inch) (4th generation) }

[stderr]
{ platform:iOS Simulator, id:A5447295-3264-4816-9C78-50E5F35C1122, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }

[stderr]
{ platform:iOS Simulator, id:067F74D9-EEC3-4066-B8A8-B3EAD0EE5649, OS:16.2, name:iPad mini (6th generation) }

[stderr]
{ platform:iOS Simulator, id:3A1FD6BA-A84C-4728-A0AA-E7D9DF147BA7, OS:16.2, name:iPhone 14 }

[stderr]
{ platform:iOS Simulator, id:5D252FD0-2816-4FAE-B85D-C29DC8D2C73C, OS:16.2, name:iPhone 14 Plus }

[stderr]
{ platform:iOS Simulator, id:AA475350-BBB4-4568-A722-4528CF187FA8, OS:16.2, name:iPhone 14 Pro }

[stderr]
{ platform:iOS Simulator, id:01B24393-FC59-4FEC-87FD-338E47BABDAE, OS:16.2, name:iPhone 14 Pro Max }

[stderr]
{ platform:iOS Simulator, id:88B2387A-FF6D-4979-9155-B06611A97148, OS:16.2, name:iPhone SE (3rd generation) }

[stderr]
2023-07-21 11:24:51.814 xcodebuild[11569:26906] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition

Detected provisioning profile mapping: {:"com.jockmkt.staging.eas"=>"ba5edd92-63eb-4da1-852c-305ba0bd7219"}

+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

|                                                                                Summary for gym 2.211.0                                                                                |

+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

| workspace                                                   | ./JockMKTStaging.xcworkspace                                                                                |

| scheme                                                      | JockMKTStaging                                                                                |

| clean                                                       | false                                                                                |

| output_directory                                            | ./build                                                                                |

| output_name                                                 | JockMKTStaging                                                                                |

| configuration                                               | Release                                                                                |

| silent                                                      | false                                                                                |

| skip_package_ipa                                            | false                                                                                |

| skip_package_pkg                                            | false                                                                                |

| export_options.method                                       | app-store                                                                                |

| export_options.provisioningProfiles.com.jockmkt.staging.eas | ba5edd92-63eb-4da1-852c-305ba0bd7219                                                                                |

| export_xcargs                                               | OTHER_CODE_SIGN_FLAGS="--keychain /var/folders/rp/_x4mwf8x2f52ml0n3qt65jw80000gn/T/turtle-v2-54ce9a92-c4f8-4c08-bcc0-5a0bd1f51f56.keychain" |

| build_path                                                  | /Users/expo/Library/Developer/Xcode/Archives/2023-07-21                                                                                |

| result_bundle                                               | false                                                                                |

| buildlog_path                                               | /Users/expo/workingdir/logs                                                                                |

| destination                                                 | generic/platform=iOS                                                                                |

| suppress_xcode_output                                       | true                                                                                |

| xcodebuild_formatter                                        | xcpretty                                                                                |

| disable_xcpretty                                            | true                                                                                |

| skip_profile_detection                                      | false                                                                                |

| xcodebuild_command                                          | xcodebuild                                                                                |

| skip_package_dependencies_resolution                        | false                                                                                |

| disable_package_automatic_updates                           | false                                                                                |

| use_system_scm                                              | false                                                                                |

| xcode_path                                                  | /Applications/Xcode.app                                                                                |

+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+

$ set -o pipefail && xcodebuild -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release -destination 'generic/platform=iOS' -archivePath /Users/expo/Library/Developer/Xcode/Archives/2023-07-21/JockMKTStaging\ 2023-07-21\ 11.24.51.xcarchive archive | tee /Users/expo/workingdir/logs/JockMKTStaging-JockMKTStaging.log > /dev/null

    Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

    Run script build phase '[CP-User] Generate app.manifest for expo-updates' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXUpdates' from project 'Pods')

    Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')

    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')

    Run script build phase 'Upload Debug Symbols to Sentry' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')

▸ ** ARCHIVE FAILED **

** ARCHIVE FAILED **

Exit status: 65

+-------------+-------------------------+

|           Build environment           |

+-------------+-------------------------+

| xcode_path  | /Applications/Xcode.app |

| gym_version | 2.211.0                 |

| sdk         | iPhoneOS16.2.sdk        |

+-------------+-------------------------+

Looks like fastlane ran into a build/archive error with your project

It's hard to tell what's causing the error, so we wrote some guides on how

to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/

Before submitting an issue on GitHub, please follow the guide above and make

sure your project is set up correctly.

fastlane uses `xcodebuild` commands to generate your binary, you can see the

the full commands printed out in yellow in the above log.

Make sure to inspect the output above, as usually you'll find more error information there

[stderr]
[!] Error building the application - see the log above

Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.

cc: @szt217

Thanks for confirming @sergey-king and sharing logs with us. I am not able to reproduce the issue on my end that makes it hard to debug the issue but I will still try to help you solve this issue.
Before I proceed with assistance, could you kindly respond to a few additional inquiries:

Have you attempted to run the command expo prebuild --clean without using any experimental configurations? If so, did the error still occur in this scenario?
Have you checked the related Github issue to see if there are any solutions or insights provided there?
Could you specify the file in which you added the appExtension configuration? It seems that we are not mentioning in our documentation that these configurations should be added to either app.json or app.plugin.js.
Lastly, could you confirm whether the "push notification" referring to your initial description, is pushNotification in your file and not "push notification" ?

 "customerio-expo-plugin",
               {
                   "android": {
                       "googleServicesFile": "./google-services-staging.json"
                   },
                   "ios": {
                       "push notification": {
                           "useRichPush": true,
                           "env": {
                               "siteId": "{SECRET_ID}",
                               "apiKey": "{SECRET_KEY}",
                               "region": "US"
                           }
                       }
                   }
               }

Hi @ami-aman,
3 & 4 - the "push notification" is just a typo here sorry. This is the actual config we have in our app.json with pushNotification as a single word
"ios": {
                        "pushNotification": {
                            "useRichPush": true,
                            "env": {
                                "siteId": "{SECRET_ID}",
                                "apiKey": "{SECRET_KEY}",
                                "region": "US"
                            }
                        }
                    }

prebuild command finishes regardless of the changes, it's the build step we have issues with.
Let me check the related issue and I will get back to you later today. Thanks!

Build error with "useRichPush": true" @ami-aman
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace ./JockMKTStaging.xcworkspace -scheme JockMKTStaging -configuration Release -destination generic/platform=iOS -archivePath "/Users/expo/Library/Developer/Xcode/Archives/2023-07-31/JockMKTStaging 2023-07-31 12.45.48.xcarchive" archive

User defaults from command line:
    IDEArchivePathOverride = /Users/expo/Library/Developer/Xcode/Archives/2023-07-31/JockMKTStaging 2023-07-31 12.45.48.xcarchive
    IDEPackageSupportUseBuiltinSCM = YES

Prepare packages

Computing target dependency graph and provisioning inputs

Create build description
Build description signature: 47ebdf43e2881cf76673e97229faaa2a
Build description path: /Users/expo/Library/Developer/Xcode/DerivedData/JockMKTStaging-dkrrutkpgqohdjfwuerrbwzpyvym/Build/Intermediates.noindex/ArchiveIntermediates/JockMKTStaging/IntermediateBuildFilesPath/XCBuildData/47ebdf43e2881cf76673e97229faaa2a-desc.xcbuild

note: Building targets in dependency order
/Users/expo/workingdir/build/apps/native/ios/JockMKTStaging.xcodeproj: error: No profiles for 'com.jockmkt.staging.eas.richpush' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.jockmkt.staging.eas.richpush'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'NotificationService' from project 'JockMKTStaging')
warning: Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')
warning: Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')
warning: Run script build phase 'Upload Debug Symbols to Sentry' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'JockMKTStaging' from project 'JockMKTStaging')
warning: Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')
warning: Run script build phase '[CP-User] Generate app.manifest for expo-updates' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXUpdates' from project 'Pods')

@ami-aman any updates on this?

@sergey-king
I want to do a quick check. Is the bundle identifier for the NotificationService target set to com.jockmkt.staging.eas.richpush match the identifier you've established in your Apple Developer account?
It appears that when useRichPush is set to true, our plugin generates a default bundle identifier labeled as bundle_identifer_of_parent_target.richpush and EAS is not able to find a matching Bundle id in the Apple Developer account. Your confirmation will help us make sure that we are on the right track.
We will do our best to help you.

Hey @ami-aman thanks for getting back to me!
Per our app.json the ios bundleIdentifier is set to "bundleIdentifier": "com.jockmkt.staging.eas".
At developer.apple.com in Certificates, Identifiers & Profiles I can see both identifiers  com.jockmkt.staging.eas and com.jockmkt.staging.eas.richpush

I've been seing com.jockmkt.staging.eas.richpush notification target generated and added by EAS build while using the older 2.4.X customerio-reactnative package. However, once we updated to the latest customerio-reactnative.3.1.7 - I've stopped seeing com.jockmkt.staging.eas.richpush notification tagert being added by EAS build process anymore

Hi @sergey-king
Thank you for sharing the details; they are indeed quite valuable!
We've investigated the issue and believe it may be caused by an outdated eas-cli version. We're not sure yet, but I wanted to give you a heads up as we continue to investigate. The latest eas-cli version is 3.18.3. Can you check on your end to see if whether you have updated version of eas-cli and make an attempt with latest eas-cli? Note that we haven't been able to reproduce the issue yet, which makes it difficult to debug.
The issue may also be related to EAS not being able to fetch the required provisioning profiles and certificates for NotificationServiceExtension from your Apple account. If that's the case, you could try creating eas build with local credentials as mentioned in Expo docs.
Rest assured, we're actively investigating this issue and will keep you well-informed of any developments.
I sincerely apologize for any inconvenience, and I greatly appreciate you for your understanding and patience. Do let us know if you have any queries with the update.

@ami-aman after updating to the latest eas-cli eas-cli/3.18.3 darwin-arm64 node-v18.16.1 the prebuild command fails with the following error
✔ Config synced
⚠  Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: Invalid `Podfile` file:
[!] Invalid `customerio-reactnative.podspec` file: [!] Unsupported version requirements. [nil] is not valid..

 #  from /Users/king.sergey/Documents/GitHub/ts-frontend/node_modules/customerio-reactnative/customerio-reactnative.podspec:23
 #  -------------------------------------------
 #    # Reference: https://guides.cocoapods.org/syntax/podfile.html#pod
 >    s.dependency "CustomerIO/Tracking", package["cioNativeiOSSdkVersion"]
 #    s.dependency "CustomerIO/MessagingInApp", package["cioNativeiOSSdkVersion"]
 #  -------------------------------------------
.

 #  from /Users/king.sergey/Documents/GitHub/ts-frontend/apps/native/ios/Podfile:46
 #  -------------------------------------------
 #    use_expo_modules!
 >    config = use_native_modules!
 #
 #  -------------------------------------------

I would also like to confirm that we're using M1/M2 Macs running both prebuild and build commands

This error is related to customerio-reactnative version. Are you using the latest version ?
@sergey-king I sincerely apologise for the inconvenience this is causing you. I am checking with the team how we can support you further in fixing this issue. Again, since we have not been able to reproduce the issue so it becomes hard to debug & fix the problem. I highly appreciate your patience.
Is there anything you'd like to add that could help us reproduce the issue ? Please feel free to put in more detail, in case that helps.

@sergey-king
After discussing the issue further with the team, I have a few suggestions for you. Please check the following:

Make sure that the credentials stored on EAS match the bundle ID for rich push. You can refer to the screenshot below for reference.
Validate that the credentials on EAS have the correct certificates and profiles for the bundle ID of NotificationServiceExtension.
Manual credentials. As I mentioned in my previous comment, did you try creating a build with manual credentials? Here is a link to the official Expo docs that may help you with the instructions.

I hope this is helpful! Let me know if you have any other questions.

Closing due to inactivity. Feel free to reopen if needed.


feat(camunda-platform): add in & out mapping props

Closes #89
We have a change here for the existing in & out mapping implementation: The all type is gone from the list items. Instead, there are new propagation groups that handle these cases.
Note that the wording of the groups is a proposal from my side to better distinguish the to-be-implemented Inputs & Outputs groups.

In mappings

In mapping propagation

Note that the configuration of "local" for the "all mapping" is only possible if the first checkbox is toggled (otherwise the mapping does not exist). The same goes for out mapping propagation.

Out mappings

Out mapping propagation

@andreasgeier thanks for mentioning the ordering of the input/output groups 👍
I've opened an issue to start the discussion around it: https://github.com/bpmn-io/bpmn-properties-panel/issues/95

I've found an issue that I suspect might only affect Windows.

It seems to be the same issue as https://github.com/camunda/camunda-modeler/issues/2364 which only affects Windows. The issue seems to be about the available space on the screen. As shown above, disabling height: 100% on the bio-properties-panel-container fixes the issue.
I will create a separate issue for this and merge this pull request regardless.


feat: chinese page in go-api/loading

@verdverm It's ready to merge!

Thanks again @chivalryq & @h1z3y3


Users without permission showing as updating group membership in audit logs

We are seeing audit entries for users being removed as a member of a [AzDoOrgName]\DirectoryServiceAddMember-Group. However the user specified in ActorDisplayName did not perform these tasks and also does not have the permission to perform this task.
Any idea on why this is happening?

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

ID: 52f60b32-5c3c-f01a-cbbf-f4e9bd17a3fc
Version Independent ID: 94753ea7-b465-f92e-10c2-8b17d995e4ff
Content: Access, export, filter audit logs for Azure DevOps - Azure DevOps
Content Source: docs/organizations/settings/azure-devops-auditing.md
Product: devops
Technology: devops-settings
GitHub Login: @chcomley
Microsoft Alias: chcomley

HI @huntleyh, Sorry to hear you're having difficulties. Please contact Technical Support, they ay want to look at specific data related to your organization. Thank you.