Unable to Launch <IP_ADDRESS>

<IP_ADDRESS> Launches correctly (However has the transport bug) attempting to launch <IP_ADDRESS> results in a grey screen and no splash.

Bepin loader logs stop after:
[Message:   BepInEx] BepInEx <IP_ADDRESS> - DSPGAME
[Info   :   BepInEx] Running under Unity v2<IP_ADDRESS>89476
[Info   :   BepInEx] CLR runtime version: 4.0.30319.17020
[Info   :   BepInEx] Supports SRE: False
[Info   :   BepInEx] System platform: Bits64, Windows
[Message:   BepInEx] Preloader started
[Info   :   BepInEx] 1 patcher plugin loaded
[Info   :   BepInEx] Patching [UnityEngine.CoreModule] with [BepInEx.Chainloader]
[Message:   BepInEx] Preloader finished
[Message:   BepInEx] Chainloader ready
[Message:   BepInEx] Chainloader started
[Info   :   BepInEx] 3 plugins to load
[Warning:   BepInEx] Plugin [NebulaMultiplayerModApi <IP_ADDRESS>] targets a wrong version of BepInEx (<IP_ADDRESS>) and might not work until you update
[Info   :   BepInEx] Loading [Galactic Scale 2 Plug-In <IP_ADDRESS>]
[Message:       GS2]
[Message:       GS2] .─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─_─.
[Message:       GS2] │  ╔═╗┌─┐┬  ┌─┐┌─┐┌┬┐┬┌─┐  ╔═╗┌─┐┌─┐┬  ┌─┐                                │
[Message:       GS2] │  ║ ╦├─┤│  ├─┤│   │ ││    ╚═╗│  ├─┤│  ├┤                                 │
[Message:       GS2] │  ╚═╝┴ ┴┴─┘┴ ┴└─┘ ┴ ┴└─┘  ╚═╝└─┘┴ ┴┴─┘└─┘ Version <IP_ADDRESS> Initializing   │
[Message:       GS2] └──────https://discord.gg/NbpBn6gM6d──────────────────────────────────────┘

Tried manually installing Bepin 5.4.16 with no change

GalacticScale.zip
Try this rebuild?

also try updating nebula api to 1.1.1
https://dsp.thunderstore.io/package/download/nebula/NebulaMultiplayerModApi/1.1.1/

Somewhat better, Updating Nebula didn't do anything but the rebuild allows the game to  launch if I let it sit for long enough.
In 2.2.05 when I would launch the game it would goto a black screen for 2-5 seconds then the DSP logo would show and it would switch to the GSM splash screens with the loading bar before going to the main menu.  And when I quit the game it would goto the "Safe Exiting" screen for 5-10 seconds and then go back to the main menu (or desktop depending on the selected choice)
In <IP_ADDRESS> when I launch the game I don't get a DSP logo but a grey screen with the windows "Waiting" cursor and with the rebuild if I let it sit on that screen for 1 minute and 38 seconds it will then goto a black screen with the Dyson Sphere mouse icon and sit on that screen for another 32 s seconds before loading the GSM splash screen and loading the game.   When I exit the game it would goto the "Safe exiting" splash and sit there for longer then I have patience to find out... (At least 3 minutes before I just end up force quiting it)
This only occurs when <IP_ADDRESS> is loaded (With other mods or alone  (minus dependencies for GSM) and <IP_ADDRESS> doesn't act that way.
The following two lines are the next in the log after the splash starts to show:

[Info   :   BepInEx] Loading [NebulaMultiplayerModApi <IP_ADDRESS>]
[Info   :   BepInEx] Loading [Galactic Scale 2 Nebula Compatibility Plug-In <IP_ADDRESS>]
[Message:GS2DepCheck] Loaded

So it would appear to be taking place between GSM and before Nebula, I'm not sure of the mod structure but is there any initialization routines that could be looping or recusing?

Try deleting the nebula api dll and see if that fixes it?
GS2 should be able to run fine without it

if you have discord, easier to sort it out there
https://discord.gg/JNFKjzGhMK

Same thing with Nebula deleted, I've responded to your comment in discord in general but if another channel or PM is better let me know username in discord is Corello

Fixed in <IP_ADDRESS>


fingers_crossed logs everything when a warning is logged

I use the 'fingers_crossed' type in combination with the 'error' as level but still all the logs are dumped the moment a warning is added.
$this->logger->warning("Message")
I would only expect this to happen when an error is set.
when I remove the line it works perfect, there are also a number of info messages logged but they don't show up in the logs anymore.
I have the following configuration in my project:
        adsolut:
            type: fingers_crossed
            level: error
            handler: adsolut_file_log
            channels: ['adsolut']
            buffer_size: 50
        adsolut_file_log:
            type: rotating_file
            path: "%kernel.logs_dir%/adsolut-%kernel.environment%.log"
            max_files: 10

Am I doing something wrong?

You need to use action_level, not level:
        adsolut:
            type: fingers_crossed
-           level: error
+           action_level: error
            handler: adsolut_file_log
            channels: ['adsolut']
            buffer_size: 50


How to do command ban as gaver.io?

How to do command ban as gaver.io?

What, to ban someone from the game? Duplicate.

Use the ban command. If you don't know the syntax of the command use the help.


Stopped working with latest update.

First of all, thanks a lot for this great extension! I use it a lot.
However, It seams like it has stopped working after your latest updates. The icon is completely gone and icon for capturing the ticket name is gone from the URL-field.
I have version 5.0.2 which is the latest commit from today here on GitHub. I use Chrome version 48.0.2564.97 (64-bit) (the latest version) on Mac OSX El Capitan.
Any ideas? Any steps I should take to debug?

@pelmered Thank you for reporting.
Could you please try the following steps:

Restart chrome.
Go to  options page chrome-extension://kjofpimpbjninggehnclcgkgniacejha/options.html
Click 'add rule'  and then 'save'
Go to https://issues.apache.org/jira/browse/HADOOP-3629

As result you should see the icon in the address bar.
Does it work for you?

@mshytikov: Yes, works good now. Thank you!

@pelmered  :+1:  Thanks, sorry for inconvenience.
Do you need more help with it? Or I can consider the issue as closed?

No problem @mshytikov, thank you for a great extension!
Yes, it works for me now at least so I'll close this issue.


Fixed missing run_id in test workflow

#681  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


⚠ Fortnite has degraded performance

In 6bcd208, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1580 ms

Resolved: Fortnite performance has improved in 5b219dc.


jaxrs2 TracingClientFilter not called if RestEasy ExceptionMapping is present

Describe the Bug
I'm on Brave 9.5.9 and using RestEasy MicroProfile REST Client (v4.3.1).
During its build it registers an ExceptionMapping client response filter with priority 1.
The brave.jaxrs2.TracingClientFilter has priority 0.
On a response the org.jboss.resteasy.core.interception.jaxrs.ClientResponseFilterRegistryImpl#sort ensures the "correct" order of response filters.
Sadly, the trace filter comes after the exception filter (also see: org.jboss.resteasy.client.jaxrs.internal.ClientInvocation#filterResponse).
The trace never gets logged/reported in such an important scenario.

Steps to Reproduce

Use RestEasy MicroProfile client
Register the TracingClientFilter: javax.ws.rs.core.Configurable#register(java.lang.Object)
Make a bad request, i.e. one that returns HTTP 400 for instance.

Expected Behaviour
The trace is logged/reported

can you do us a favor and make a microprofile example similar to this? I don't have experience with this microprofile framework and want to make sure I fully understand.

@svenhaag are you just asking to remove
@Priority(0) // to make the span in scope visible to other filters

if this is not overridable in the underlying container, I'd suggest a few options:

do not use this, and instead instrument whatever the actual http client is, as that's better anyway
make a wrapper which you control order of and add the order annotation you want

meanwhile if you can make a sample project, I might be able to help how to find configuration available that could override the order. remember, jax-rs has no means to register exceptions anyway, so that's why I suggest instrumenting whatever's underneath, ex apachehc.

Thanks @adriancole, I'll do a PR with an example ASAP. I think the culprit is @Priority(0), but I'm not sure if the solution would be as easy as removing it or changing its number. Also, the class is marked final which makes it impossible to inherit from it.
What do you mean by "overridable in the underlying container"?
I could do client.register(TracingClientFilter.class, 666); // 666 = Priority, but as the class implements both, ClientRequestFilter, ClientResponseFilter interfaces I'm not so sure if that works. The priorities for the filters should be different in order to be processed first in the chain.
Cheers

@svenhaag sorry what I said isn't intuitive. I mean this
@Provider
@ConstrainedTo(CLIENT)
@Priority(1) // or whatever you want
public class MyTracingClientFilter implements ClientRequestFilter, ClientResponseFilter {
  final TracingClientFilter delegate;

  @Inject MyTracingClientFilter(HttpTracing httpTracing) {
    delegate = TracingClientFilter.create(httpTracing);
  }
  @Override public void filter(ClientRequestContext request) {
    delegate.filter(request);
  }

  @Override public void filter(ClientRequestContext request, ClientResponseContext response) {
    delegate.filter(request, response);
  }
}

can you do us a favor and make a microprofile example similar to this? I don't have experience with this microprofile framework and want to make sure I fully understand.
I've created a unit test demonstrating this. Please see: https://github.com/openzipkin/brave-webmvc-example/pull/39


Convert approx_distinct to UDAF

Which issue does this PR close?

Closes #10837
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

I have resolved all the reviews, plz merge this first to avoid an extra conflicts solve, Thanks for your review @goldmedal

Thanks @Lordworms and @goldmedal


Add XCompose language and highlighter

Hopefully this is considered a language? I find 39k results searching for files which are XCompose:
https://github.com/search?p=10&q=<Multi_key>&ref=searchresults&type=Code&utf8=✓
Not all of them would catch in this filter, but most are named so they would match.

The search engine doesn't consider < and >, so this is actually searching for Multi_key only. What are the usual file extensions for this language? Are there other keywords we could use?
It looks like we could add Compose, .XCompose, and XCompose as filenames for this language.

Yeah, I've already added all of those extensions/filenames
https://github.com/github/linguist/pull/3402/files#diff-3552b1a64ad2071983c4d91349075c75R4590

Hm, right. Don't know why I though this was an issue, even though the two commits were starring right at me :/

I should probably remove xmodmap though. Not all of them are XCompose type (about split between that and another config type). Or I could add heuristics, but there are not enough of them to matter I think.

Not all of them are XCompose type (about split between that and another config type).

What's the other config type? Any way to detect it?

Or I could add heuristics, but there are not enough of them to matter I think.

I found only about 767 .xmodmap files so if half of them aren't actually XCompose, I'm afraid it won't be enough.
I found only 33 .XCompose files. That won't be enough to add this extension.
I found 186 files with name .XCompose and 160 files with name XCompose, but they're well distributed among users and repositories (1 per repository) and the risk of conflict is very low, so that might be enough to add it as a filename.

@pchaigno done


Auto-cast from float to integer

Hello, it could be useful to be able to use a float without decimals as an integer in two cases :

modulo -> Error with 5.0 % 2
Dictionary keys -> my_dict[5] != my_dict[5.0]

These errors are hard to find/avoid in a top-level language.

Have you tried using the round(5.0) function? It seems to be that comparing 5 to 5.0 should never be automated with conversions. If it is being done so, a warning should be thrown like most compilers do.
Just my five cents, since essentially we are truly entering 2 diff values. Being a bit rusty on floating point math I also recall even if you enter 5.0, the exponential values will probably not be 0 after the first 0.
Maybe this answers your question, or not at all.

Not sure to understand, may be that in some cases it would be a problem but not in all i suppose. The functions round(), floor() and ceil() could equally return an integer. The return's type of min() and max() correspond to their arguments, thus it should be possible.

Well the point is simply that strictly speaking you are entering different values. So this feature request, to me, seems like possibly something that would break the language, in a sense it makes the rules diff vs most languages.
Other than that, your example is speaking about user input. And as such, you can just enter 5 yourself. If you are speaking about real variables, as such, my_dict[my_float_var] then you can indeed, round/ceil/floor it :)
I'm not trying to hate, but it seems rather useless to me from a programmer POV.

These functions return a float, so if the type of the keys is int, two values can be created for the "same" (semantically) key. The result must be converted to int before. In python 5 and 5.0 are the same keys. When this behavior is in mind, it is easy to avoid an error of course, but it is easy to forget it too between multiple other things.
Thank you for the comments.

I think the documentation is mistaken with the float, actually using round(float_variable) does return an int, in fact it states:
"round
float round ( float s )
Round to nearest integer."
Simply put, having tested it, it actually makes comparing floats with integers possible. So it's actually noteworthy now that you mentioned it.

@WatIsDeze :
You're wrong.
round() returns float. "To the nearest integer" just mean the decimal part is removed.
round(3.14) will return 3.0
If you want to convert float to int, then use int(3.14) that will return 3

@UsernameIsAReservedWord that's quite an interesting difference versus most languages, but I appreciate you clearing it up.
I've never seen floating point comparison work out of the box, aka 3.0 never is strictly 3.0.
Any specific reasons as to why this is?

@WatIsDeze : to get a better understanding, you can read the C++ source code of Godot.

I don't see anything to implement here, adding a hack so that 5.0 is interpreted as 5 would only lead to confusion and weird bugs. For the two cases mentioned in the OP, you should use int(5.0).


math.mMin causes serious performance degradations

In issue 20459 it was said that math.mMin had bad performance. So I removed math.mMin and math.mMax from fluxFunctions.ts file and added simple min_two_num and max_two_num functions instead. Those removed functions were not used in the project anywhere and no test was implemented for them.

In issue 20459 it was said that math.mMin had bad performance. So I removed math.mMin and math.mMax from fluxFunctions.ts file and added simple min_two_num and max_two_num functions instead. Those removed functions were not used in the project anywhere and no test was implemented for them.

I don't know where to implement my two functions!!?

I don't know where to implement my two functions!!?

addresses #20459

Since the UI code this PR refers to is no longer in the influxdb repository and the underlying issue has been transferred to Flux repo (see: https://github.com/influxdata/flux/issues/3508), I'm going to close this PR out since we won't be able to merge it here.


CSS Styling

Portfolio must include a photo/avatar, name, and links to sections about them. See Acceptance Criteria for more details.

Photo/avatar included with name and links to sections.


Display impl for Error eats all the useful information

The Display impl for Error passes through to std::error::Error::description(), which is pretty-much useless. For example, all I/O errors become simply "os error" through this lens.

Fair point. A nice fix here would be to use the description for hyper errors, but delegate to fmt of errors from other crates.
Example:
impl fmt::Display for Error {
    fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
        match *self {
            Io(ref e) | Uri(ref e) | Ssl(ref e) | Http2(ref e) | Utf8(ref e) => fmt::Display::fmt(e, f),
            e => f.write_str(e.description())
        }
    }
}

Yeah, I'd be happy with that.

I tend to go with something like
impl fmt::Display for Error {
    fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
        try!(f.write_str(self.description())
        match *self {
            AllThingsWithInnerErrors(ref e) => write!(f, "{}", e),
            ....
        }
    }
}

With https://github.com/rust-lang/rust/pull/30312 being merged, at this should state something more than os error in Rust 1.7, which is an improvement...

I'm getting conflicting messages from this thread. If the problem is that os error isn't useful, that's coming from fmt of a non-hyper IO error. So handing off error formatting of non-hyper errors (such as IO) to fmt wouldn't actually address the initial example. Right?

@xaviershay the problem is that a Display impl is calling description on the std error instead of Display::fmt, so no useful information is propagated, even though it's accessible from the std error.

@xaviershay it's because the description of io::Error before Rust 1.7 simply says "os error". Instead of printing the description, we could print the full fmt::Debug message of io::Error (or, in 1.7, the description will match the Debug output anyways).

 Apologies, I'm still getting used to Rust and would like to help if I can.

@josephpd3 I'm sure that PR improved things. We could make it a little better in hyper by doing as I suggest in the 2nd comment.


Store question admin names as key format, instead of rewriting them at every callsite

Currently the question admin name is written as a string with spaces, but then everywhere(?) we use it we use the key form, which has everything stripped and spaces converted to underscores.
What if we just enforce this format on creation instead of rewriting every time we want to use it?
See getNameKey() for the current re-writing
https://github.com/civiform/civiform/blob/e34a393dfebab8b889a1afe5e2d3fa67ca8e3e18/server/app/services/question/types/QuestionDefinition.java#L98
Question:

Is there anywhere that admin see the admin name as they typed it? Maybe the CSV?
Doing this migration might be kind of tricky, since we couldn't change old applications very easily? unless it's done as a durable job.
The job should get a lock on the DB to prevent it from running at the same time as an API or CSV export

Also:

Currently the name can have capital letters, but we lowercase everything before using it in a path. Will lowercasing it right away and storing it as lower-cased cause any problems?

I've never understood why we don't have a slug saved on the questions table like we do with programs. Would make life much easier than having to compute it all the time.

a starting point from @gwendolyngoetz, would also need to lowercase the identifier
# --- !Ups
alter table if exists questions
add column if not exists admin_name varchar null

update questions
set admin_name = regexp_replace(regexp_replace(name, '[^a-zA-Z ]', '', 'g'), '\s', '_' , 'g')

alter table if exists questions
alter column admin_name set not null;

# --- !Downs
alter table if exists questions
drop column if exists admin_name;


iOS - Error: /usr/bin/xcodebuild failed with return code: 65

##[section]Starting: Xcode build
==============================================================================
Task         : Xcode
Description  : Build, test, or archive an Xcode workspace on macOS. Optionally package an app.
Version      : 5.150.0
Author       : Microsoft Corporation
Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613730)
==============================================================================
[command]/usr/bin/xcodebuild -version
Xcode 10.1
Build version 10B61
[command]/usr/bin/xcodebuild -sdk iphoneos -configuration Release -workspace /Users/vsts/agent/2.150.3/work/1/s/Haulio.xcodeproj/project.xcworkspace -scheme Haulio Staging build CODE_SIGNING_ALLOWED=NO | /usr/local/lib/ruby/gems/2.6.0/bin/xcpretty -r junit --no-color

❌  error: /Users/vsts/agent/2.150.3/work/1/s/Pods/Target Support Files/Pods-Haulio/Pods-Haulio.release staging.xcconfig: unable to open file (in target "Haulio" in project "Haulio") (in target 'Haulio')

❌  error: /Users/vsts/agent/2.150.3/work/1/s/Pods/Target Support Files/Pods-Haulio/Pods-Haulio.release staging.xcconfig: unable to open file (in target "Haulio" in project "Haulio") (in target 'Haulio')

** BUILD FAILED **

❌  error: /Users/vsts/agent/2.150.3/work/1/s/Pods/Target Support Files/Pods-Haulio/Pods-Haulio.release staging.xcconfig: unable to open file (in target "Haulio" in project "Haulio") (in target 'Haulio')

##[error]Error: /usr/bin/xcodebuild failed with return code: 65
##[section]Finishing: Xcode build

2019-05-02T06:35:28.9317160Z ##[section]Starting: Job
2019-05-02T06:35:29.2096420Z ##[section]Starting: Initialize job
2019-05-02T06:35:29.2096650Z Current agent version: '2.150.3'
2019-05-02T06:35:29.2342320Z Prepare build directory.
2019-05-02T06:35:29.2648260Z Set build variables.
2019-05-02T06:35:29.2702390Z Download all required tasks.
2019-05-02T06:35:29.2908950Z Downloading task: Xcode
2019-05-02T06:35:29.6806890Z Downloading task: CopyFiles
2019-05-02T06:35:29.8665450Z Downloading task: PublishBuildArtifacts
2019-05-02T06:35:30.1681210Z Start tracking orphan processes.
2019-05-02T06:35:30.1840020Z ##[section]Finishing: Initialize job
2019-05-02T06:35:30.2426130Z ##[section]Starting: Checkout
2019-05-02T06:35:30.2748870Z ==============================================================================
2019-05-02T06:35:30.2749020Z Task         : Get sources
2019-05-02T06:35:30.2749080Z Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
2019-05-02T06:35:30.2749120Z Version      : 1.0.0
2019-05-02T06:35:30.2749200Z Author       : Microsoft
2019-05-02T06:35:30.2749230Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
2019-05-02T06:35:30.2749270Z ==============================================================================
2019-05-02T06:35:31.1069800Z Syncing repository: ios (Git)
2019-05-02T06:35:31.2181140Z ##[command]git version
2019-05-02T06:35:31.2882200Z git version 2.21.0
2019-05-02T06:35:31.3068290Z ##[command]git lfs version
2019-05-02T06:35:31.4923220Z git-lfs/2.7.2 (GitHub; darwin amd64; go 1.12.4)
2019-05-02T06:35:31.5420970Z ##[command]git init "/Users/vsts/agent/2.150.3/work/1/s"
2019-05-02T06:35:31.5804900Z Initialized empty Git repository in /Users/vsts/agent/2.150.3/work/1/s/.git/
2019-05-02T06:35:31.5876970Z ##[command]git remote add origin https://hauliov1.visualstudio.com/Haulio%20Communicator%20Driver%20App/_git/ios
2019-05-02T06:35:31.6042820Z ##[command]git config gc.auto 0
2019-05-02T06:35:31.6262850Z ##[command]git config --get-all http.https://hauliov1.visualstudio.com/Haulio%20Communicator%20Driver%20App/_git/ios.extraheader
2019-05-02T06:35:31.6324620Z ##[command]git config --get-all http.proxy
2019-05-02T06:35:31.6551070Z ##[command]git -c http.extraheader="AUTHORIZATION: bearer ***" fetch --tags --prune --progress --no-recurse-submodules origin
2019-05-02T06:35:31.9953530Z remote: Azure Repos
2019-05-02T06:35:32.0064960Z remote:
2019-05-02T06:35:32.0065130Z remote: Found 10334 objects to send. (11 ms)
2019-05-02T06:35:32.3281470Z Receiving objects:   0% (1/10334)
2019-05-02T06:35:32.3508420Z Receiving objects:   1% (104/10334)
2019-05-02T06:35:32.3545150Z Receiving objects:   2% (207/10334)
2019-05-02T06:35:32.3659930Z Receiving objects:   3% (311/10334)
2019-05-02T06:35:32.3688530Z Receiving objects:   4% (414/10334)
2019-05-02T06:35:32.3707620Z Receiving objects:   5% (517/10334)
2019-05-02T06:35:32.3723490Z Receiving objects:   6% (621/10334)
2019-05-02T06:35:32.3747870Z Receiving objects:   7% (724/10334)
2019-05-02T06:35:32.3774920Z Receiving objects:   8% (827/10334)
2019-05-02T06:35:32.3795360Z Receiving objects:   9% (931/10334)
2019-05-02T06:35:32.3819990Z Receiving objects:  10% (1034/10334)
2019-05-02T06:35:32.3840800Z Receiving objects:  11% (1137/10334)
2019-05-02T06:35:32.3864860Z Receiving objects:  12% (1241/10334)
2019-05-02T06:35:32.3895900Z Receiving objects:  13% (1344/10334)
2019-05-02T06:35:32.3913790Z Receiving objects:  14% (1447/10334)
2019-05-02T06:35:32.3930020Z Receiving objects:  15% (1551/10334)
2019-05-02T06:35:32.4182150Z Receiving objects:  16% (1654/10334)
2019-05-02T06:35:32.4788110Z Receiving objects:  17% (1757/10334)
2019-05-02T06:35:32.4818780Z Receiving objects:  18% (1861/10334)
2019-05-02T06:35:32.4832170Z Receiving objects:  19% (1964/10334)
2019-05-02T06:35:32.5361290Z Receiving objects:  20% (2067/10334)
2019-05-02T06:35:32.5398070Z Receiving objects:  21% (2171/10334)
2019-05-02T06:35:32.5447510Z Receiving objects:  22% (2274/10334)
2019-05-02T06:35:32.5458300Z Receiving objects:  23% (2377/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.5578430Z Receiving objects:  24% (2481/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.5619850Z Receiving objects:  25% (2584/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.5652710Z Receiving objects:  26% (2687/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.5705580Z Receiving objects:  27% (2791/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6258230Z Receiving objects:  28% (2894/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6352710Z Receiving objects:  29% (2997/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6382690Z Receiving objects:  30% (3101/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6428710Z Receiving objects:  31% (3204/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6460070Z Receiving objects:  32% (3307/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6465940Z Receiving objects:  33% (3411/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6471110Z Receiving objects:  34% (3514/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6527620Z Receiving objects:  35% (3617/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6533810Z Receiving objects:  36% (3721/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6541030Z Receiving objects:  37% (3824/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6547700Z Receiving objects:  38% (3927/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6553470Z Receiving objects:  39% (4031/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6559460Z Receiving objects:  40% (4134/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6566450Z Receiving objects:  41% (4237/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6570840Z Receiving objects:  42% (4341/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6574520Z Receiving objects:  43% (4444/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6578920Z Receiving objects:  44% (4547/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6583280Z Receiving objects:  45% (4651/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6587700Z Receiving objects:  46% (4754/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6602270Z Receiving objects:  47% (4857/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6606940Z Receiving objects:  48% (4961/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6610930Z Receiving objects:  49% (5064/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6615540Z Receiving objects:  50% (5167/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6620020Z Receiving objects:  51% (5271/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6625010Z Receiving objects:  52% (5374/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6634430Z Receiving objects:  53% (5478/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6645800Z Receiving objects:  54% (5581/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6650160Z Receiving objects:  55% (5684/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6653950Z Receiving objects:  56% (5788/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6658770Z Receiving objects:  57% (5891/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6663940Z Receiving objects:  58% (5994/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6670060Z Receiving objects:  59% (6098/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6674210Z Receiving objects:  60% (6201/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6678670Z Receiving objects:  61% (6304/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6683380Z Receiving objects:  62% (6408/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6688740Z Receiving objects:  63% (6511/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6710260Z Receiving objects:  64% (6614/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6721490Z Receiving objects:  65% (6718/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6722350Z Receiving objects:  66% (6821/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6723230Z Receiving objects:  67% (6924/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6730430Z Receiving objects:  68% (7028/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6736680Z Receiving objects:  69% (7131/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6739990Z Receiving objects:  70% (7234/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6755770Z Receiving objects:  71% (7338/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6760740Z Receiving objects:  72% (7441/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6765480Z Receiving objects:  73% (7544/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6770780Z Receiving objects:  74% (7648/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6776740Z Receiving objects:  75% (7751/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6781010Z Receiving objects:  76% (7854/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6785610Z Receiving objects:  77% (7958/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6789940Z Receiving objects:  78% (8061/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6796440Z Receiving objects:  79% (8164/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6800170Z Receiving objects:  80% (8268/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6817350Z Receiving objects:  81% (8371/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6828090Z Receiving objects:  82% (8474/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6839960Z Receiving objects:  83% (8578/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6852060Z Receiving objects:  84% (8681/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6880310Z Receiving objects:  85% (8784/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6889050Z Receiving objects:  86% (8888/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6899160Z Receiving objects:  87% (8991/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6909700Z Receiving objects:  88% (9094/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6925610Z Receiving objects:  89% (9198/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6939230Z Receiving objects:  90% (9301/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6948320Z Receiving objects:  91% (9404/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6971660Z Receiving objects:  92% (9508/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.6986170Z Receiving objects:  93% (9611/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7002350Z Receiving objects:  94% (9714/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7015290Z Receiving objects:  95% (9818/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7036240Z Receiving objects:  96% (9921/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7083660Z Receiving objects:  97% (10024/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7100520Z Receiving objects:  98% (10128/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7107140Z Receiving objects:  99% (10231/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7107600Z Receiving objects: 100% (10334/10334), 11.63 MiB | 23.25 MiB/s
2019-05-02T06:35:32.7107730Z Receiving objects: 100% (10334/10334), 15.00 MiB | 22.52 MiB/s, done.
2019-05-02T06:35:32.7133010Z Resolving deltas:   0% (0/6845)
2019-05-02T06:35:32.7141780Z Resolving deltas:   1% (79/6845)
2019-05-02T06:35:32.7152370Z Resolving deltas:   2% (157/6845)
2019-05-02T06:35:32.7159860Z Resolving deltas:   3% (228/6845)
2019-05-02T06:35:32.7169160Z Resolving deltas:   4% (286/6845)
2019-05-02T06:35:32.7188250Z Resolving deltas:   5% (349/6845)
2019-05-02T06:35:32.7197790Z Resolving deltas:   6% (446/6845)
2019-05-02T06:35:32.7214830Z Resolving deltas:   7% (485/6845)
2019-05-02T06:35:32.7229310Z Resolving deltas:   8% (548/6845)
2019-05-02T06:35:32.7254380Z Resolving deltas:   9% (620/6845)
2019-05-02T06:35:32.7265790Z Resolving deltas:  10% (688/6845)
2019-05-02T06:35:32.7276040Z Resolving deltas:  11% (763/6845)
2019-05-02T06:35:32.7286520Z Resolving deltas:  12% (823/6845)
2019-05-02T06:35:32.7304060Z Resolving deltas:  13% (890/6845)
2019-05-02T06:35:32.7316080Z Resolving deltas:  14% (981/6845)
2019-05-02T06:35:32.7324460Z Resolving deltas:  15% (1029/6845)
2019-05-02T06:35:32.7342110Z Resolving deltas:  16% (1098/6845)
2019-05-02T06:35:32.7356640Z Resolving deltas:  17% (1184/6845)
2019-05-02T06:35:32.7395730Z Resolving deltas:  18% (1245/6845)
2019-05-02T06:35:32.7397840Z Resolving deltas:  19% (1364/6845)
2019-05-02T06:35:32.7408580Z Resolving deltas:  20% (1374/6845)
2019-05-02T06:35:32.7444970Z Resolving deltas:  21% (1440/6845)
2019-05-02T06:35:32.7487020Z Resolving deltas:  22% (1512/6845)
2019-05-02T06:35:32.7488860Z Resolving deltas:  23% (1576/6845)
2019-05-02T06:35:32.7490930Z Resolving deltas:  24% (1646/6845)
2019-05-02T06:35:32.7492730Z Resolving deltas:  25% (1712/6845)
2019-05-02T06:35:32.7494770Z Resolving deltas:  26% (1780/6845)
2019-05-02T06:35:32.7518340Z Resolving deltas:  27% (1857/6845)
2019-05-02T06:35:32.7557840Z Resolving deltas:  28% (1937/6845)
2019-05-02T06:35:32.7616760Z Resolving deltas:  29% (2006/6845)
2019-05-02T06:35:32.7663000Z Resolving deltas:  30% (2095/6845)
2019-05-02T06:35:32.7691770Z Resolving deltas:  31% (2141/6845)
2019-05-02T06:35:32.7693940Z Resolving deltas:  32% (2192/6845)
2019-05-02T06:35:32.7695720Z Resolving deltas:  33% (2260/6845)
2019-05-02T06:35:32.7707750Z Resolving deltas:  34% (2350/6845)
2019-05-02T06:35:32.7739420Z Resolving deltas:  35% (2396/6845)
2019-05-02T06:35:32.7775450Z Resolving deltas:  36% (2467/6845)
2019-05-02T06:35:32.7808880Z Resolving deltas:  37% (2533/6845)
2019-05-02T06:35:32.7820100Z Resolving deltas:  38% (2636/6845)
2019-05-02T06:35:32.7823450Z Resolving deltas:  39% (2703/6845)
2019-05-02T06:35:32.7827400Z Resolving deltas:  40% (2754/6845)
2019-05-02T06:35:32.7835580Z Resolving deltas:  41% (2808/6845)
2019-05-02T06:35:32.7867900Z Resolving deltas:  42% (2886/6845)
2019-05-02T06:35:32.7883400Z Resolving deltas:  43% (2945/6845)
2019-05-02T06:35:32.7884500Z Resolving deltas:  44% (3012/6845)
2019-05-02T06:35:32.7887030Z Resolving deltas:  45% (3081/6845)
2019-05-02T06:35:32.7887500Z Resolving deltas:  46% (3151/6845)
2019-05-02T06:35:32.7896580Z Resolving deltas:  47% (3220/6845)
2019-05-02T06:35:32.7903280Z Resolving deltas:  49% (3369/6845)
2019-05-02T06:35:32.7905090Z Resolving deltas:  50% (3426/6845)
2019-05-02T06:35:32.7911690Z Resolving deltas:  51% (3491/6845)
2019-05-02T06:35:32.7916530Z Resolving deltas:  52% (3563/6845)
2019-05-02T06:35:32.7921190Z Resolving deltas:  53% (3631/6845)
2019-05-02T06:35:32.7926940Z Resolving deltas:  54% (3704/6845)
2019-05-02T06:35:32.7933980Z Resolving deltas:  55% (3766/6845)
2019-05-02T06:35:32.7959150Z Resolving deltas:  56% (3863/6845)
2019-05-02T06:35:32.7959660Z Resolving deltas:  57% (3908/6845)
2019-05-02T06:35:32.7963040Z Resolving deltas:  58% (3971/6845)
2019-05-02T06:35:32.7963590Z Resolving deltas:  60% (4131/6845)
2019-05-02T06:35:32.7970290Z Resolving deltas:  61% (4214/6845)
2019-05-02T06:35:32.7974710Z Resolving deltas:  62% (4244/6845)
2019-05-02T06:35:32.7975980Z Resolving deltas:  63% (4351/6845)
2019-05-02T06:35:32.7979490Z Resolving deltas:  64% (4413/6845)
2019-05-02T06:35:32.7988160Z Resolving deltas:  65% (4451/6845)
2019-05-02T06:35:32.7992580Z Resolving deltas:  66% (4560/6845)
2019-05-02T06:35:32.7999880Z Resolving deltas:  67% (4587/6845)
2019-05-02T06:35:32.8005020Z Resolving deltas:  68% (4656/6845)
2019-05-02T06:35:32.8059630Z Resolving deltas:  69% (4724/6845)
2019-05-02T06:35:32.8062700Z Resolving deltas:  70% (4807/6845)
2019-05-02T06:35:32.8064420Z Resolving deltas:  71% (4883/6845)
2019-05-02T06:35:32.8066170Z Resolving deltas:  72% (4932/6845)
2019-05-02T06:35:32.8068280Z Resolving deltas:  73% (5013/6845)
2019-05-02T06:35:32.8068830Z Resolving deltas:  74% (5073/6845)
2019-05-02T06:35:32.8069910Z Resolving deltas:  75% (5161/6845)
2019-05-02T06:35:32.8071260Z Resolving deltas:  76% (5232/6845)
2019-05-02T06:35:32.8073750Z Resolving deltas:  77% (5281/6845)
2019-05-02T06:35:32.8079410Z Resolving deltas:  78% (5340/6845)
2019-05-02T06:35:32.8085250Z Resolving deltas:  79% (5431/6845)
2019-05-02T06:35:32.8089810Z Resolving deltas:  80% (5513/6845)
2019-05-02T06:35:32.8097550Z Resolving deltas:  81% (5549/6845)
2019-05-02T06:35:32.8101460Z Resolving deltas:  82% (5636/6845)
2019-05-02T06:35:32.8114230Z Resolving deltas:  83% (5684/6845)
2019-05-02T06:35:32.8119990Z Resolving deltas:  85% (5839/6845)
2019-05-02T06:35:32.8122880Z Resolving deltas:  86% (5894/6845)
2019-05-02T06:35:32.8128660Z Resolving deltas:  87% (5957/6845)
2019-05-02T06:35:32.8145970Z Resolving deltas:  88% (6028/6845)
2019-05-02T06:35:32.8149680Z Resolving deltas:  91% (6252/6845)
2019-05-02T06:35:32.8160780Z Resolving deltas:  92% (6301/6845)
2019-05-02T06:35:32.8161700Z Resolving deltas:  93% (6368/6845)
2019-05-02T06:35:32.8166890Z Resolving deltas:  94% (6442/6845)
2019-05-02T06:35:32.8176180Z Resolving deltas:  95% (6511/6845)
2019-05-02T06:35:32.8199740Z Resolving deltas:  96% (6574/6845)
2019-05-02T06:35:32.8210900Z Resolving deltas:  97% (6640/6845)
2019-05-02T06:35:32.8216380Z Resolving deltas:  98% (6709/6845)
2019-05-02T06:35:32.8217030Z Resolving deltas:  99% (6777/6845)
2019-05-02T06:35:32.8218070Z Resolving deltas: 100% (6845/6845)
2019-05-02T06:35:32.8218650Z Resolving deltas: 100% (6845/6845), done.
2019-05-02T06:35:32.9165130Z From https://hauliov1.visualstudio.com/Haulio%20Communicator%20Driver%20App/_git/ios
2019-05-02T06:35:32.9166570Z  * [new branch]      AppStore_BgLocationService -> origin/AppStore_BgLocationService
2019-05-02T06:35:32.9339660Z  * [new branch]      AppStore_NoBgLocationService -> origin/AppStore_NoBgLocationService
2019-05-02T06:35:32.9394480Z  * [new branch]      Derick              -> origin/Derick
2019-05-02T06:35:32.9399430Z  * [new branch]      DerickNextSprint    -> origin/DerickNextSprint
2019-05-02T06:35:32.9404130Z  * [new branch]      DerickRefactoring   -> origin/DerickRefactoring
2019-05-02T06:35:32.9409880Z  * [new branch]      DerickSprint106     -> origin/DerickSprint106
2019-05-02T06:35:32.9416910Z  * [new branch]      DerickSprint107     -> origin/DerickSprint107
2019-05-02T06:35:32.9423960Z  * [new branch]      DerickSupportRevamp -> origin/DerickSupportRevamp
2019-05-02T06:35:32.9430350Z  * [new branch]      HCSMVVMRevamp       -> origin/HCSMVVMRevamp
2019-05-02T06:35:32.9437220Z  * [new branch]      HCSRevamp           -> origin/HCSRevamp
2019-05-02T06:35:32.9443140Z  * [new branch]      NEHCSRevamp         -> origin/NEHCSRevamp
2019-05-02T06:35:32.9447480Z  * [new branch]      develop             -> origin/develop
2019-05-02T06:35:32.9451780Z  * [new branch]      fixingConflict      -> origin/fixingConflict
2019-05-02T06:35:32.9456420Z  * [new branch]      master              -> origin/master
2019-05-02T06:35:32.9460860Z  * [new branch]      neDevelop           -> origin/neDevelop
2019-05-02T06:35:32.9465900Z  * [new branch]      sawDevelop          -> origin/sawDevelop
2019-05-02T06:35:32.9470980Z  * [new branch]      separateTargets     -> origin/separateTargets
2019-05-02T06:35:32.9653900Z ##[command]git checkout --progress --force 552252ab5777960a85c735121e456498befe23dc
2019-05-02T06:35:33.3951830Z HEAD is now at 552252a Merge branch 'neDevelop' of vs-ssh.visualstudio.com:v3/hauliov1/Haulio%20Communicator%20Driver%20App/ios into neDevelop
2019-05-02T06:35:33.4173100Z ##[section]Finishing: Checkout
2019-05-02T06:35:33.4202240Z ##[section]Starting: Xcode build
2019-05-02T06:35:33.4211480Z ==============================================================================
2019-05-02T06:35:33.4211570Z Task         : Xcode
2019-05-02T06:35:33.4211640Z Description  : Build, test, or archive an Xcode workspace on macOS. Optionally package an app.
2019-05-02T06:35:33.4212100Z Version      : 5.150.0
2019-05-02T06:35:33.4212180Z Author       : Microsoft Corporation
2019-05-02T06:35:33.4212250Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613730)
2019-05-02T06:35:33.4212340Z ==============================================================================
2019-05-02T06:35:34.3466020Z [command]/usr/bin/xcodebuild -version
2019-05-02T06:35:34.5182630Z Xcode 10.1
2019-05-02T06:35:34.5297250Z Build version 10B61
2019-05-02T06:35:34.5569550Z [command]/usr/bin/xcodebuild -sdk iphoneos -configuration Release -workspace /Users/vsts/agent/2.150.3/work/1/s/Haulio.xcodeproj/project.xcworkspace -scheme Haulio Staging build CODE_SIGNING_ALLOWED=NO | /usr/local/lib/ruby/gems/2.6.0/bin/xcpretty -r junit --no-color
2019-05-02T06:35:40.5627190Z
2019-05-02T06:35:40.5630500Z ❌  error: /Users/vsts/agent/2.150.3/work/1/s/Pods/Target Support Files/Pods-Haulio/Pods-Haulio.release staging.xcconfig: unable to open file (in target "Haulio" in project "Haulio") (in target 'Haulio')
2019-05-02T06:35:40.5638190Z
2019-05-02T06:35:40.5638540Z
2019-05-02T06:35:40.5638910Z
2019-05-02T06:35:40.5640270Z ❌  error: /Users/vsts/agent/2.150.3/work/1/s/Pods/Target Support Files/Pods-Haulio/Pods-Haulio.release staging.xcconfig: unable to open file (in target "Haulio" in project "Haulio") (in target 'Haulio')
2019-05-02T06:35:40.5640350Z
2019-05-02T06:35:40.5640480Z
2019-05-02T06:35:40.5677020Z ** BUILD FAILED **
2019-05-02T06:35:40.5677350Z
2019-05-02T06:35:40.5718580Z
2019-05-02T06:35:40.5720380Z ❌  error: /Users/vsts/agent/2.150.3/work/1/s/Pods/Target Support Files/Pods-Haulio/Pods-Haulio.release staging.xcconfig: unable to open file (in target "Haulio" in project "Haulio") (in target 'Haulio')
2019-05-02T06:35:40.5720590Z
2019-05-02T06:35:40.5720660Z
2019-05-02T06:35:40.6230940Z ##[error]Error: /usr/bin/xcodebuild failed with return code: 65
2019-05-02T06:35:40.6871630Z ##[section]Finishing: Xcode build
2019-05-02T06:35:40.6885680Z ##[section]Starting: Copy Files to: $(build.artifactstagingdirectory)
2019-05-02T06:35:40.6889190Z ==============================================================================
2019-05-02T06:35:40.6889230Z Task         : Copy Files
2019-05-02T06:35:40.6889280Z Description  : Copy files from source folder to target folder using match patterns (The match patterns will only match file paths, not folder paths)
2019-05-02T06:35:40.6889320Z Version      : 2.117.2
2019-05-02T06:35:40.6889350Z Author       : Microsoft Corporation
2019-05-02T06:35:40.6889390Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=708389)
2019-05-02T06:35:40.6889430Z ==============================================================================
2019-05-02T06:35:41.0634970Z found 0 files
2019-05-02T06:35:41.0692570Z ##[section]Finishing: Copy Files to: $(build.artifactstagingdirectory)
2019-05-02T06:35:41.0709080Z ##[section]Starting: Publish Artifact: drop
2019-05-02T06:35:41.0712990Z ==============================================================================
2019-05-02T06:35:41.0713150Z Task         : Publish Build Artifacts
2019-05-02T06:35:41.0713200Z Description  : Publish build artifacts to Azure Pipelines/TFS or a file share
2019-05-02T06:35:41.0713240Z Version      : 1.142.2
2019-05-02T06:35:41.0713270Z Author       : Microsoft Corporation
2019-05-02T06:35:41.0713300Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=708390)
2019-05-02T06:35:41.0713410Z ==============================================================================
2019-05-02T06:35:41.3111480Z ##[warning]Directory '/Users/vsts/agent/2.150.3/work/1/a' is empty. Nothing will be added to build artifact 'drop'.
2019-05-02T06:35:41.3113330Z ##[section]Finishing: Publish Artifact: drop
2019-05-02T06:35:41.3124940Z ##[section]Starting: Xcode build
2019-05-02T06:35:41.3131620Z ==============================================================================
2019-05-02T06:35:41.3131670Z Task         : Xcode
2019-05-02T06:35:41.3131700Z Description  : Build, test, or archive an Xcode workspace on macOS. Optionally package an app.
2019-05-02T06:35:41.3132120Z Version      : 5.150.0
2019-05-02T06:35:41.3132170Z Author       : Microsoft Corporation
2019-05-02T06:35:41.3132200Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613730)
2019-05-02T06:35:41.3132230Z ==============================================================================
2019-05-02T06:35:41.5231880Z ##[section]Finishing: Xcode build
2019-05-02T06:35:41.5245520Z ##[section]Starting: Checkout
2019-05-02T06:35:41.5248250Z ==============================================================================
2019-05-02T06:35:41.5248390Z Task         : Get sources
2019-05-02T06:35:41.5248520Z Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
2019-05-02T06:35:41.5248550Z Version      : 1.0.0
2019-05-02T06:35:41.5248650Z Author       : Microsoft
2019-05-02T06:35:41.5248710Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
2019-05-02T06:35:41.5248840Z ==============================================================================
2019-05-02T06:35:42.1436110Z Cleaning any cached credential from repository: ios (Git)
2019-05-02T06:35:42.1528180Z ##[section]Finishing: Checkout
2019-05-02T06:35:42.1668520Z ##[section]Starting: Finalize Job
2019-05-02T06:35:42.1724600Z Start cleaning up orphan processes.
2019-05-02T06:35:42.2248020Z ##[section]Finishing: Finalize Job
2019-05-02T06:35:42.2414950Z ##[section]Finishing: Job

Hi All,
I currently fail with the Error return code: 65 by using Azure DevOps with current Agent Pools MacOS High Sierra,
but don't know what is the issue and to solve it.
Hope can get helping hand from here.

I'm also encountering this issue. The Visual Studio App Center team seems to have a workaround - one of their scripts includes the following snippet:

# Use sed to quote filepaths which may contain spaces.
BROKEN_POD_FILES=$(grep -l -r 'NO_SIGNING/' --include '*.pbxproj' . | sed -e 's/^/"/g' -e 's/$/"/g')

if [[ ! -z "$BROKEN_POD_FILES" ]];
then
 echo 'Fixing CocoaPods projects with "NO_SIGNING/" provisioning profiles. See https://github.com/CocoaPods/CocoaPods/issues/7038'
 echo $BROKEN_POD_FILES | xargs perl -pi -e 's/PROVISIONING_PROFILE_SPECIFIER = NO_SIGNING\//CODE_SIGNING_ALLOWED = NO/g'
fi

I haven't been able to get this script to work, but seeing as their backend is all Azure Pipelines tasks there's certainly a workaround somewhere in their code. I believe it has something to do with an old version of CocoaPods that the task is using.

Here is a related MSDN discussion:
https://developercommunity.visualstudio.com/content/problem/508973/xcode-builds-suddenly-failing-with-message-error-d.html
Looks like specifying an older version, not a newer one fixes this.

This relates to an ionic cordova project but I got the same error in my pipeline and could fixed it with the following bash script which changes the permissions to the file system.

- bash: |
   # Fixing permissions issues, otherwise xcode build will fail with a failed 'PhaseScriptExecution Copy ...' command
   # See: https://stackoverflow.com/questions/38465217/cordova-error-code-65-for-command-xcodebuild-with-args

   chmod -R +x $(System.DefaultWorkingDirectory)

  displayName: 'Fix permission issues'

Maybe that'll help you too.

try to install pod dependency before build, I cost 3 weeks for this
packages.json
"scripts": {
...
"postinstall": "cd ios && pod install"
}

set legacy build and try to install pod dependencies before build, hope that helps you guys, I cost 3 weeks for this :(
packages.json
"scripts": {
...
"postinstall": "cd ios && pod install"
}

how i can set legacy for iOS project?

set legacy build and try to install pod dependencies before build, hope that helps you guys, I cost 3 weeks for this :(
packages.json
"scripts": {
...
"postinstall": "cd ios && pod install"
}

how i can set legacy for iOS project?

In Build configuration

set legacy build and try to install pod dependencies before build, hope that helps you guys, I cost 3 weeks for this :(
packages.json
"scripts": {
...
"postinstall": "cd ios && pod install"
}

how i can set legacy for iOS project?

In Build configuration

UPDATED:
you can use my post-clone script to do this, no need to write pod install script in package.json
here

I still get error. :))

1_Build.txt

It works.

Please check your
configuration: '$(configuration)'
scheme: '$(scheme)'
Most of example tell you "configuration" as "Release" if you have custom configuration please use particular name.

hi @chathurka  I didn't understand exactly what you mean here. can you explain more in detail.
Where is the;
configuration: '$(configuration)'
scheme: '$(scheme)'
I have a .env file and and defined in this way CONFIGURATION="Release"

I had a similar issue, I set legacy option ON, and it worked, however, would there any possible issue with the new generated build?

I'm still having this issue even after turning legacy option on. anything else I can do?

Been pulling my hair out with this error. I'm using xcode 12.1 selected and node 10 in Appcenter. Using the legacy build system is greyed out for this version of Appcenter. Any hints would be appreciated.

Same here. Legacy Build is turned off and greyed out.

Legacy build is available with Xcode version  : 10.3

Legacy build is available with Xcode version: 10.0  to 11.7

Did this issue get resolved? See that it is Closed but i am still seeing this issue in Azure Pipeline with Xcode 12

yes it solved.
Regards,
Harsh Shah
On Sat, Sep 25, 2021 at 4:39 PM Yusuf @.***> wrote:

Did this issue get resolved? See that it is Closed but i am still seeing
this issue in Azure Pipeline with Xcode 12
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azure-pipelines-tasks/issues/10302#issuecomment-927179994,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2Z3UNVUIJOKDM25UTWSCDUDYXQBANCNFSM4HKQPIKQ
.

I have this issue with AppCenter, Xcode 13.0 and node 14.x . Legacy build system is greyed out for this version of AppCenter.

Did you solved?

I have this issue with AppCenter, Xcode 13.0 and node 14.x . Legacy build system is greyed out for this version of AppCenter.

Did you solved?

i added react-native-codegen to package.json


change interval counter display

on long processes the counter dots are not wrapped and make huge horizontal scrolling to see exit status
adding space fixes this and atom can properly wrap text (and i think it looks nicer :)

Seems like the better solution would just be to use the word-break: break-all CSS property. I'm not a fan of the spaces.

using css is fine with me

Tagged as 2.7.1. Thanks for reporting!


Added GIF code block to readme

I noticed that the GIF uses SuperstaQProvider instead of the recently updated SupertaqProvider, so if it’s not too much extra work, maybe worth updating that.
(Also, a nice bonus later on could be to have the GIF loop alternative between cirq-superstaq & qiskit-superstaq)

I noticed that the GIF uses SuperstaQProvider instead of the recently updated SupertaqProvider, so if it’s not too much extra work, maybe worth updating that.
(Also, a nice bonus later on could be to have the GIF loop alternative between cirq-superstaq & qiskit-superstaq)

@bharat-thotakura Oh good catch - Just opened a new PR for the Q --> q change


Using the router completely breaks HMR.

Describe the bug
HMR seems to completely break if using solid-router.
I don't know if I'm doing anything weird here, but I've created a very minimal reproduction example.
Your Example Website or App
https://github.com/utrolig/solid-router-hmr-bug
Steps to Reproduce the Bug or Issue

Try to edit file in src/pages/spaces/SpacesOverview.tsx
HMR doesn't work.
Restart app
Page is now correct

Expected behavior
I expected HMR to work and update my page when I edit the file.
Screenshots or Videos
No response
Platform

OS: [Windows 11]
Browser: [Chrome]
Version: [107.0.5304.107]

Additional context
No response

So, this wasn't related to the router at all, but rather how folder/filenames on windows filesystems work.
So the import comes from import { SpacesOverview } from "./Spaces/SpacesOverview"; but the folder name is actually spaces.
On windows the import still works, but HMR breaks.
When I tried to run it on my WSL, I got an error message instantly, changed the import, and everything works.


Re-Configure IR Self Hosted

I can't find option to re-configure IR Self-hosted.
Can you please advice how can I reconfigure IR so It linked to Data factory recourse created for the day.

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

ID: d1a34b3c-a9b8-29ce-1eca-86f7f42981a1
Version Independent ID: 61d6e6b3-ec54-552d-1bef-86bbcbfea8ff
Content: Integration runtime in Azure Data Factory
Content Source: articles/data-factory/concepts-integration-runtime.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@ranarah Have you looked here:
https://docs.microsoft.com/en-US/azure/data-factory/create-self-hosted-integration-runtime
If you don't see what you are looking for in that document, could you clarify what you are trying to reconfigure?  Thanks!

@ranarah we are closing this issue for now, please feel free to add comments as needed.

Use the power shell script to link Data Factory to existing IR on your machine
."Program Files""Microsoft Integration Runtime"\3.0\PowerShellScript\RegisterIntegrationRuntime.ps1
This require access Key to re-register .


feat: wait for all GCP resources and more helpful error message

Part of https://github.com/kubeflow/gcp-blueprints/issues/139
Most of the issues raised here were related to errors deploying GCP resources,
so I improved the script to verify those resources are ready.
changes:

verify all google cloud resources are ready
show an error message for how to troubleshoot when sth times out

/assign @subodh101 @chensun

I'll self lgtm to start testing for release. Feel free to raise more comments later.


Adding documentation for WPF's Binding issue

Also, the known issues TOC should be updated to link to this topic, @miguep.

@rpetrusha I've added the suggestions and added a link in the 4.8 Known issues document

Thanks for the additional changes, @miguep. I'll merge your PR now.


Downloading a backblaze snapshot yields ciphertext verification fails

Here's my setup:
version: "3.3"

services:
  backup:
    image: mazzolino/restic
    hostname: docker
    restart: unless-stopped
    environment:
      RUN_ON_STARTUP: "true"
      BACKUP_CRON: "0 0 3 * * *"
      RESTIC_REPOSITORY: b2:rpi-homelab-backup:/restic-repo
      RESTIC_PASSWORD: [redacted]
      RESTIC_BACKUP_SOURCES: /mnt/volumes
      RESTIC_BACKUP_ARGS: --tag docker-volumes
      RESTIC_FORGET_ARGS: --keep-daily 7 --keep-weekly 4
      B2_ACCOUNT_ID: [redacted]
      B2_ACCOUNT_KEY: [redacted]
    volumes:
      - /var/lib/docker/volumes:/mnt/volumes:ro

  check:
    image: mazzolino/restic
    hostname: docker
    restart: unless-stopped
    environment:
      RUN_ON_STARTUP: "false"
      CHECK_CRON: "0 15 5 * * *"
      RESTIC_CHECK_ARGS: >-
        --read-data-subset=10%
      RESTIC_REPOSITORY: b2:rpi-homelab-backup:/restic-repo
      RESTIC_PASSWORD: [redacted]
      B2_ACCOUNT_ID: [redacted]
      B2_ACCOUNT_KEY: [redacted]

Backup task logs:
Checking configured repository 'b2:rpi-homelab-backup:/restic-repo' ...
Fatal: unable to open config file: Stat: b2_download_file_by_name: 404:
Is there a repository at the following location?
b2:rpi-homelab-backup:/restic-repo
Could not access the configured repository. Trying to initialize (in case it has not been initialized yet) ...
created restic repository d724a9802c at b2:rpi-homelab-backup:/restic-repo
Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.
Repository successfully initialized.
Executing backup on startup ...
Starting Backup at 2023-07-22 02:40:41
no parent snapshot found, will read all files
Files:       43857 new,     0 changed,     0 unmodified
Dirs:        13599 new,     0 changed,     0 unmodified
Added to the repository: 17.466 GiB (16.668 GiB stored)
processed 43857 files, 29.772 GiB in 30:39
snapshot f7487f77 saved
Backup successful
Forget about old snapshots based on RESTIC_FORGET_ARGS = --keep-daily 7 --keep-weekly 4
Applying Policy: keep 7 daily, 4 weekly snapshots
keep 1 snapshots:
ID        Time                 Host        Tags            Reasons          Paths
----------------------------------------------------------------------------------------
f7487f77  2023-07-22 02:40:41  docker      docker-volumes  daily snapshot   /mnt/volumes
                                                           weekly snapshot
----------------------------------------------------------------------------------------
1 snapshots
Finished backup at 2023-07-22 03:11:27 after 1846 seconds
Scheduling backup job according to cron expression.
new cron: 0 0 3 * * *

Check logs:
Checking configured repository 'b2:rpi-homelab-backup:/restic-repo' ...
Fatal: unable to open config file: Stat: b2_download_file_by_name: 404:
Is there a repository at the following location?
b2:rpi-homelab-backup:/restic-repo
Could not access the configured repository. Trying to initialize (in case it has not been initialized yet) ...
created restic repository c3bef4a1ac at b2:rpi-homelab-backup:/restic-repo
Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.
Repository successfully initialized.
Scheduling check job according to cron expression.
new cron: 0 15 5 * * *
executing: /usr/local/bin/check
Starting check at 2023-07-22 05:15:00
using temporary cache in /tmp/restic-check-cache-960397027
create exclusive lock for repository
load indexes
check all packs
[0:02] 100.00%  1 / 1 snapshots
check snapshots, trees and blobs
read 10.0% of data packs
[1:19] 100.00%  101 / 101 packs
no errors were found
Check successful
Finished check at 2023-07-22 05:16:32 after 92 seconds

I  see the restic repo folder in my Backblaze bucket.
So, I created a snapshot (which is how you download files from backblaze), and downloaded/extracted it. Here's what I see:
❯ restic -r restic-repo snapshots
enter password for repository:
Fatal: config or key f704f3952dd1d9fd3c8e35e4c4feed5797e3237608e60a1c564a4ab242c0f7aa is damaged: ciphertext verification failed. Try again

I am not sure what to do. I have already tried deleting the repo from the cloud and restarting the resticker containers to rebuild the repo from scratch. Both times I get this exact error and am unable to open the vault. I know the password I'm entering is correct because the error changes when I enter something wrong.
I also am not sure this is a drive issue since the check job states no errors. Does the check job run locally, though? Or does it run on the files in the cloud? That may affect my opinion about it being a drive issue.
Any help would be greatly appreciated, thanks!

Please let me know if I need to transfer this issue to restic, too. I really want to get to the bottom of this.

I don't know what changed, but I deleted everything, started over, and now I'm able to open the repo downloaded from backblaze. I wonder what the issue may have been...

Just updating: I still get this issue spontaneously :(

Hi, in a previous versions there was a bug when starting more then one service in a compose file.
Both services tried to init the repo.
Maybe this could be the reason for the first issue. Since there is no start time in the log it's a little bit complicated to debug.
Regarding your second issue with the B2 bucket....
I'm not an B2 expert. But why do you download a snapshot?
 Since restic uses incremental backup you need to download all files in the bucket.
Could you create a extra "restore" container and mount this to your B2 bucket on the source side and to a restore volume on the other side. And try to restore some files?


Replace Google Charts

they deprecated the image charts service a few years ago so we're quite lucky it still works. since it's also simple enough to draw svg charts i decided to ditch the dependency. also removes the necessity to configure csp and doesn't pump data into google. i kept the style the same so nobody will notice.

oh, and i bumped the version number. please cut a new release after merge if you'll merge ;)

LGTM @glaszig, thank you for this — a solid improvement 🥇

1.1.0 has been released to rubygems, and a tag has also been cut 👍


article restriction in voucher module

the minimum ordernumber length is four characters (see http://wiki.shopware.com/Artikelnummern-in-Shopware_detail_642.html). the voucher module required six characters minimum string length. this is wrong

hi @bcremer
can you have a short look on this bugfix?

Dear Contributor,
Thank you for your contribution to Shopware. We value your engagement.
Unfortunately we have to close all existing Pull Requests.
This is due to the new Shopware 5 Major Release and a restructuring of the branch names.
If your contribution is still relevant for Shopware 5, a new pull request is highly appreciated.
We are very sorry for this inconvenience.
Greetings from the Shopware Team.


Add optional monitoring solution (Prometheus, Datadog ...)

Hello there !
I thought it would be a nice complement to add one or multiple services to be able to monitor the code, the calls, the performances.
I know that a lot of people use Prometheus, so I thought it could be nice. But I also know that DataDog also provides methods to monitor the code.
What do you think ?

Hi. This is a great idea. I know about prometheus and personally work with it all the time, but I haven't heard about datadog, so I don't have sufficient experience to add this integration.

This issue is complex, and I've decided to split it into multiple smaller ones.
Currently is want to add:

Prometheus
Jaeger
Datadog
Digma

I'll keep this thread open in case someone wants to suggest a new integration.

As I found out. Jaeger, Datadog and Digma can be used with OpenTelemetry collector.
You can deploy an opentelemetry collector and add exporters to different systems.
So basically I want to setup an integration with OpenTelemetry and you will have an option to export any tracing information you want in desired systems.
But I have to admit, though opentelemetry collector have an integration with sentry, I have to add this integration manually, since I want to have more information that it sends to collector.
So new scheme would be something like this:

So now this issue is all about opentelemetry integration. This is the best solution I came up with.

Amazing, and if you complete this feat, then please do add a sponsorship option.

I've added prometheus and Sentry integrations.
I'm almost ready to add opentelemetry integration, but I have a question.
Would it be useful to add an option to generate docker-compose.otlp.yml for the opentelemetry collector and Jaeger containers near with main docker-compose.yml?
What do you guys think about it?

Maybe adding those containers in docker-compose.dev.yml would be a better idea. Since in production you'll have collector, jaeger and datadog running on separate machines and you want to have only one instance of Jaeger for all projects.
I can add opentelemetry collector in main docker-compose.yml, since it collects spans per project, but I'll place Jaeger  in a separate one.
Is this ok?

Opentelemetry support along with prometheus and sentry was released in 3.3.5. I leave this issue open for a while. Here we can discuss if we need to change something.

Closed due to inactivity.


Add sudo for mkfs.ext4

mkfs.ext4 is in /sbin/ and this directory is not usually in the PATH of a normal user. Therefore we need to perform sudo in order to reach /sbin/mkfs.*

@xairy please check if it works on your machine

It works.

@xairy then please merge it

thanks ;)


fix(material-experimental/mdc-list): don't access class before initialization

Moves the MatListBase class up so that it isn't being referenced before it is used which seems to cause issues with Jest.
Fixes #25008.

Not sure why we don't catch this, likely because of how Jest transforms the ESM


Issue Title "function GetInstallBitness is not returning Bitness"

The function GetInstallBitness in CheckMSIOverride.ps1 does not return Bitness if it is found.
The only return Value is $false in case of an error.

Thanks for reporting this, it should be fixed in this latest release.


App home page/route

Populate the client home route with summary of app and navigation to main app features
get Idea how we are using this page...
for a tutorial on this look to section 3 of this Udacity course

Can you assign me to this please?

@motosharpley @redragonx what is left for this? Currently we have a home screen. We still need a splash screen I believe. Is that all or am I missing something? If so, we should probably close this ticket a create a more specific issue for what remains. Thanks.

Sorry for the late reply, but I had unexpected real life problems popped up. That's why there was no response.


Add cleanup workflows to actions

None of the three composite actions have cleanup workflows.  That'll be creating a mess!  Fix before this gets worse.

oc cleanup for deployer
https://github.com/bcgov-nr/action-deployer-openshift/pull/7


[Feature] Add an indicator called errorRowsAfterResumed to distinguish between …

…totalErrorRows(called errorRows) and errorRowsAfterResumed.
Proposed changes
When an routine load job's currentErrorRows is greater than maxErrorNum, the job will be paused. Users can use resume routine load for xxx; to make the job be running again.
Then, there will be a problem, the indicator called errorRows won't be reset to 0. But as totalErrorRows, it is useful. So we need to add an indicator called  errorRowsAfterResumed to distinguish  between totalErrorRows(called errorRows) and errorRowsAfterResumed. We can get useful infomation through errorRowsAfterResumed , and determine whether some Propterties are reasonable or not.
errorRowsAfterResumed can directly show current errorRows, also at the time of the job's state is changed to Paused.  It can't just use the variable called currentErrorRows, cuz currentErrorRows will be reset to 0 after the job's state changed.
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality) #6091
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[x ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

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

The new added errorRowsAfterResumed is not persisted.
So If FE restart, this info is lost and will be reset to 0, is it acceptable?

Made errorRowsAfterResumed be persisted. Thx for your reminding.

Better refactor the statistic

Better refactor the statistic

Done.


Java upgrade 15->16

So far the build fails because of old (and it seems unmaintained) jaxb plugin used in tests to generate java classes from xsd.
We should decide what to do with that - one option is to migrate to maintained and developed: https://github.com/mojohaus/jaxb2-maven-plugin
Or maybe even: http://cxf.apache.org/cxf-xjc-plugin.html

Additional info - JDK16 broke Lombok: https://github.com/rzwitserloot/lombok/issues/2681

Lombok 1.18.20 is out, which works fine with JDK16 :)

Lombok now works like a charm 👍
But it seems we have a very similar problem with spock/groovy now - I will try to update to latest one and try once more...

Updated spock to latest version did not solve the issue, it seems like there is some issue with unboxing, eg:
new LocalDate(2005, 5, 20)
returns
groovy.lang.GroovyRuntimeException: Could not find matching constructor for: java.time.LocalDate(Integer, Integer, Integer)

I bypassed the groovy errors with couple of syntax changes regarding primitives and unit tests now pass, sadly Integration tests wont pass since it seems we might have hit end of life for CRaSH..
Exception in thread "CRaSH" BUG! exception in phase 'semantic analysis' in source unit 'login' Unsupported class file major version 60
	at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:969)
	at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:642)
	at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:591)
	at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:401)
	at groovy.lang.GroovyClassLoader.access$300(GroovyClassLoader.java:89)
	at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:341)
	at groovy.lang.GroovyClassLoader$5.provide(GroovyClassLoader.java:338)
	at org.codehaus.groovy.runtime.memoize.ConcurrentCommonCache.getAndPut(ConcurrentCommonCache.java:147)
	at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:336)
	at org.crsh.lang.impl.groovy.GroovyClassFactory.parse(GroovyClassFactory.java:59)

I will try to force CRaSH on Groovy 3, otherwise we might need to finish migration to test containers first...

Probably the last update - forcing newer groovy seems to make CRaSH somehow working again, but this time I probably hit a final wall for now, which will need to be solved by Apache commons or JBehave:
at org.jbehavesupport.runner.JUnitRunner$1.evaluate(JUnitRunner.java:95)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:220)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:53)
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private final byte[] java.lang.String.value accessible: module java.base does not "opens java.lang" to unnamed module @3d82c5f3
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:177)
	at java.base/java.lang.reflect.AccessibleObject.setAccessible(AccessibleObject.java:130)
	at org.apache.commons.lang3.builder.CompareToBuilder.reflectionAppend(CompareToBuilder.java:321)
	at org.apache.commons.lang3.builder.CompareToBuilder.reflectionCompare(CompareToBuilder.java:293)
	at org.apache.commons.lang3.builder.CompareToBuilder.reflectionCompare(CompareToBuilder.java:142)
	at org.jbehave.core.reporters.TemplateableViewGenerator$Report.compareTo(TemplateableViewGenerator.java:462)

We could probably solve this with add-opens , but I don't think we should force users to do this in their code.

Created JBEHAVE-1479

I added add-opens to CI and note about this workaround to the main readme - so now it should be "somehow" working and mergable.

Replaced jaxb2-maven-plugin with cxf-xjc-plugin that currently supports fluent api (though who knows for how long since it uses the same undeveloped extension as the plugin before)


list: raise NoSuchKegError if formula exists but isn't installed

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Show a more accurate error message when running brew list <formula> with a non-installed formula.
Before:
$ brew list zorba
Error: No available formula or cask with the name "zorba". Did you mean zork?

After:
$ brew list zorba
Error: No such keg: /usr/local/Cellar/zorba
$ brew list does-not-exist
Error: No available formula with the name "does-not-exist".

Review period will end on 2021-11-12 at 22:45:19 UTC.

Nice tweak, thanks again @EricFromCanada!

Review period skipped due to critical label.


Feature Request: Save & download world endpoint

An endpoint like /v1/worlds/:uuid/download or /v1/worlds/download to save & download worlds as a compressed file. Brotli would be preferred, but ZIP is good.

8x13b from discord is working on this https://discord.com/channels/919982507271802890/920026454207643688/920341302065905714

Closes with #110

Closed by #110


Correct message keys for async batching mode

There're some possible changes relative to #325.
As create_message_set() method is called only from base Producer class and from _send_upstream(), I've changed it a little bit, so messages sent as a list of (msg, key) tuples. I've added some basic tests also.
Take a look please, probably it can be improved.

I need to fix it with other branch, will create a new one.


MIDI input support

osu!framework should support taking input from MIDI devices such as digital pianos.
ManagedBass seems to have support for taking MIDI input, but this isn't included in its NuGet package since it is not compatible with some platforms. NAudio supports taking MIDI input (which I have previously implemented in a fork here) but I don't know if this is cross-platform.
See also ppy/osu#4328 and ManagedBass/ManagedBass#54.

bass add ons are fulfilled by optional nuget packages, so there will be a matching one (https://www.nuget.org/packages/ManagedBass.Midi/)

The ManagedBass.Midi package does not have support for taking MIDI input, which is why I opened ManagedBass/ManagedBass#54. It is filtered out in the NuGet builds using compiler directives.


Correct Typo in QuickStarts Template

Hi @adamgoodbar, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (agoodb). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@adamgoodbar : Thanks for your contribution to the Azure documentation! The author, @davidmu1, has been notified to review your proposed change.

@adamgoodbar: Thank you very much for caring about the quality of the documentation and taking the time to make the change. @tysonn: Please merge the change.


Standardize on circuit tag names

An implementation of https://github.com/cep21/circuit/blob/master/v3/metrics/statsdmetrics/statsd.go in another repository with standardized tag names and platform independent. I think datadog style statsd tags will allow us to solve this in a generalized way

Will resolve as part of v4 impl


Zenzumai patch 1

Fix %2F url encoding

@Zenzumai I have to refuse this pr because the "/" correspond to what Apigility really returns. However in a separate PR I fixed the hosts to api.continuousphp.com.
Thanks!
Pascal


Don't set default bindings for "Switch" (they're already built into Windows!)

I suggest not setting the Switch shortcut by default.
As a power user of Chromium, my workflow got immediately interrupted as I found I couldn't use the Alt + Arrow shortcuts any more. There are other apps that can probably be listed that use Alt + Arrow also. which makes me think that the default isn't sensible. I see things this way: most people who are power users will find this default a clash with current flow, and most people who haven't used virtual desktops before probably won't have a reason to deviate from the normal Ctrl + Win + Arrow shortcut. Opinionated users (like those who favor Linux key bindings and Ctrl + Alt + Arrow) will probably be happy enough to change things themselves, since config is so simple.
Thoughts?

Another example of somebody who's done something similar with a project that's very similar to this one: https://github.com/m0ngr31/VirtualDesktopManager/issues/15

meh

Thanks for the input.
Keyboard shortcuts for the switch action are only partially built into Windows. You can use Ctrl + Win + Arrow to switch to the previous/next desktops, but that is about it. You can't go to a specific desktop using the number keys, or move windows at all between desktops. A better solution would be to change the default for that setting to be Switch=Win, Ctrl, which would make it so the default windows kb shortcuts would still work, and the new shortcuts would be coherent with them since they would use the same modifiers.
I use Switch=LAlt, since it is what I find easiest and the most accessible. That is why it is the default. When I come across programs that require the use of Alt, I use RAlt instead, which isn't assigned to this app.
I definitely see your point though. I'm conflicted. I'll leave this open for feedback. If enough people want it changed, I'll change it.

The program is very helpful! However it must give an opportunity to set up hotkeys. Currently the program allows to switch between the desktops with ALT+CTRL+Number. However these shortcuts are using in many other programs, e.g. in MS Word for switching styles to H1-H3. It drives me crazy when I suddenly switch to another desktop trying simply to set Header2 style.

@zhekaus Hi. Thanks. You don't have to use the default hotkeys, you can change them under the settings.ini file. Please see the README for details.

I stumbled to the exact same problem with chrome and switched my 'switch' modified to 'Ctrl'. Now I can't use Ctrl + A to select all text.  Why does the program hijack shortcuts that it doesn't even use?

@sdias I would vote for your idea of using Ctrl+Win as the default modifiers. The Win key makes it feel like you're operating at the desktop/shell level, and the pair is consistent with the built in (and not muscle-memorised) keys for switching desktops.
Right alt is not always an option in other programs. On my keyboard it's Alt Gr which doesn't  behave like an alt key.

@drewnoakes I agree. Having a drop-in replacement with the keyboard shortcuts actually sounds really interesting for flow.

Ok, it seems that changing the defaults to something that resembles the default Windows keyboard shortcuts is the preferred option. I'll change the default switch combo to Win+Ctrl. What about moving windows across desktops? I'm thinking about setting move only to Win+Shift and move and shift to Win+Shift+Ctrl, which should be intuitive. What do you think?

Win+Shift+Ctrl sounds pretty intuitive to me. That's my vote!

@oskari It does not do that to me. I think you have something else going on

@sdias @meffect Doesn't seem to do it always but there was definitely something going on as I didn't experience the issue anymore after I immediately closed virtual-desktop-enhancer.exe from taskbar.

@oskari AutoHotkey can bind keys in a lot of different ways. Maybe the one I'm using is not the most appropriate. I have noticed, for example, that when I switch desktops using Alt+<Number> into a desktop with a game running in windowed mode, my character crouches in the game, as if I had pressed Ctrl, which I don't think it makes a lot of sense and should not be happening, there may be something wrong with the implementation. I need to look into it.

I just published a new release with the keyboard shortcuts that were suggested as defaults.
Unfortunately, there is a bug (that as far as I can tell I can't fix since it is due to an interaction between AutoHotkey and Windows) in that if certain keyboard shortcuts that use the Windows key are used, after using them the start menu opens. Due to that, the "move window and switch to desktop" action is now not set by default (since Win + Shift triggers this issue).

MoveWindowAndSwitchToDesktop=Win, Shift is working good for me. Start menu doesnt pop up. I'm on build 15025 though.. maybe ms fixed something.  Love this update very cool ty all

@meffect Good to know, I might re-enable it in the future. Thanks.


Use display name as name in app

@jeffmaher would you be able to redeploy this?

@cdhs-bha-data-services-sys redeployed, should appear on the PR within a few moments


Python interface for cone search

Includes some other improvements to the docs

Coverage increased (+0.2%) to 98.469% when pulling 70c086a78477d649e5e55245b4c3fc5e710261b2 on astrofrog:cone-search-python into 81200962baf6476ff455a8c6d6a43acb74f33c0b on cdeil:master.

Coverage increased (+0.2%) to 98.469% when pulling 2cabaffb06ef353e1a1f6027f9ac881c8b0410ab on astrofrog:cone-search-python into 81200962baf6476ff455a8c6d6a43acb74f33c0b on cdeil:master.

Coverage increased (+0.2%) to 98.469% when pulling b8287a064ce21bf16265543db5c76dc8daaf82d7 on astrofrog:cone-search-python into 81200962baf6476ff455a8c6d6a43acb74f33c0b on cdeil:master.


[trimming] TrimMode=full in debug mode, should enable analyzers

For NativeAOT scenarios, projects would set:
<PublishAot>true</PublishAot>

For both Debug and Release, this allows you to get the same set of analyzers in both configurations. You'd want to see the same warnings for both.
For Android, the project template is currently doing:
<PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <TrimMode>Full</TrimMode>
</PropertyGroup>

But this would result in a different set of warnings between Debug and Release mode!
Instead, we can do:
<PropertyGroup>
    <TrimMode>Full</TrimMode>
</PropertyGroup>

And then add a new default, such as:
<EnableTrimAnalyzer Condition="'$(EnableTrimAnalyzer)' == '' and '$(TrimMode)' == 'full'">true</EnableTrimAnalyzer>

TrimMode=Full does not enable the trimmer, so other defaults in Debug should remain unchanged.
So, the new behavior is:

Configuration=Debug
PublishTrimmed=false (default, no trimmer)
TrimMode=Full (project template)
EnableTrimAnalyzer=true (new default)
You get the same warnings in Debug and Release mode.

I also reworded the commend in the project template slightly, to mention it enables analyzers.

The BuildAppCheckDebugSymbols() seems to also be failing w/ main:

https://github.com/dotnet/android/pull/9322

It failed here, because this PR is from a fork.

Draft commit message:
For AOT scenarios, projects would set:

	<PublishAot>true</PublishAot>

For both `Debug` and `Release`, this allows you to get the same set
of analyzers in both configurations.  You'd want to see the same
warnings for both.

For Android, the project template is currently doing:

	<PropertyGroup Condition="'$(Configuration)' == 'Release'">
	  <TrimMode>Full</TrimMode>
	</PropertyGroup>

but this would result in a *different* set of warnings between
`Debug` and `Release` configuration builds!

Instead, we can do:

	<PropertyGroup>
	  <TrimMode>Full</TrimMode>
	</PropertyGroup>

And then add a new default, such as:

	<EnableTrimAnalyzer
	    Condition=" '$(EnableTrimAnalyzer)' == '' and '$(TrimMode)' == 'full' "
	>true</EnableTrimAnalyzer>

`$(TrimMode)=Full` does *not* enable the trimmer, so other defaults
in the `Debug` configuration build should remain unchanged.

So, the new behavior is:

  * `$(Configuration)=Debug`
  * `$(PublishTrimmed)=false` (default, no trimmer)
  * `$(TrimMode)=Full` (project template)
  * `$(EnableTrimAnalyzer)=true` (new default)
  * You get the same set of warnings in `Debug` and `Release`
    configuration builds.

I also reworded the comment in the project template slightly, to
mention it enables analyzers.

@jonathanpeppers : one question about that commit message: you say:

So, the new behavior is:

$(Configuration)=Debug`

"new behavior" implies a change in behavior.  The default $(Configuration) hasn't changed.  Am I misinterpreting?

I think I just missed the word “for” like: For Configuration=Debug


BrokenPipeError: [Errno 32] Broken pipe

After several hours ws is crashing:
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/home/azat/modbus_online/web.py", line 81, in update_load
    turbo.push(turbo.replace(render_template('loadme.html'), 'load'))
  File "/home/azat/modbus_online/venv/lib/python3.8/site-packages/turbo_flask/turbo.py", line 180, in push
    ws.send(stream)
  File "/home/azat/modbus_online/venv/lib/python3.8/site-packages/simple_websocket/ws.py", line 60, in send
    self.sock.send(out_data)
BrokenPipeError: [Errno 32] Broken pipe

turbo-flask is used according to load example
@app.context_processor
def inject_load():
    ...
    return {'data': response,}

@app.before_first_request
def before_first_request():
    threading.Thread(target=update_load).start()

def update_load():
    with app.app_context():
        while True:
            time.sleep(0.5)
            turbo.push(turbo.replace(render_template('loadme.html'), 'load'))

How to avoid this problem?

This occurs when the client abruptly closes their side of the connection. I have to add special handling for this situation so that the error is suppressed and the client removed from the active connection list.

@azat385 Can I ask you to try the main branch of this repository to see if the fix addresses your problem? Thanks.

try the main branch..

@miguelgrinberg i'd like to try. But could you explain please how to use this repository instead pip version in virtual env?

Use this command:
pip install https://github.com/miguelgrinberg/turbo-flask/archive/main.zip

(venv) azat@334783-azat385vds:~/modbus_online$ pip freeze
attrs==21.2.0
click==8.0.1
Flask==2.0.1
flask-sock==0.4.0
gunicorn==20.1.0
h11==0.12.0
iniconfig==1.1.1
itsdangerous==2.0.1
Jinja2==3.0.1
MarkupSafe==2.0.1
packaging==21.0
pluggy==0.13.1
py==1.10.0
pyparsing==2.4.7
pyserial==3.5
pytest==6.2.4
python-dotenv==0.19.0
simple-websocket==0.2.0
toml==0.10.2
Turbo-Flask==0.6.1.dev0
uModbus==1.0.4
Werkzeug==2.0.1
wsproto==1.0.0

While directly running app throug flask Turbo-Flask==0.6.1.dev0 works great!
But with gunicorn get some error messages and turbo is stopping refreshing after a while (approx ~30sec)
(venv) azat@334783-azat385vds:~/modbus_online$ gunicorn -b <IP_ADDRESS>:5000 web:app
[2021-08-04 13:24:24 +0300] [98694] [INFO] Starting gunicorn 20.1.0
[2021-08-04 13:24:24 +0300] [98694] [INFO] Listening at: http://<IP_ADDRESS>:5000 (98694)
[2021-08-04 13:24:24 +0300] [98694] [INFO] Using worker: sync
[2021-08-04 13:24:24 +0300] [98696] [INFO] Booting worker with pid: 98696
[2021-08-04 13:25:02 +0300] [98694] [CRITICAL] WORKER TIMEOUT (pid:98696)
[2021-08-04 13:25:02 +0300] [98696] [INFO] Worker exiting (pid: 98696)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/home/azat/modbus_online/web.py", line 103, in update_load
    turbo.push(turbo.replace(render_template('loadme.html'), 'load'))
  File "/home/azat/modbus_online/venv/lib/python3.8/site-packages/turbo_flask/turbo.py", line 182, in push
    ws.send(stream)
  File "/home/azat/modbus_online/venv/lib/python3.8/site-packages/simple_websocket/ws.py", line 60, in send
    self.sock.send(out_data)
OSError: [Errno 9] Bad file descriptor
[2021-08-04 13:25:03 +0300] [98694] [WARNING] Worker with pid 98696 was terminated due to signal 9

@azat385 your Gunicorn worker is timing out and restarting. Do you have any long running requests? Gunicorn has a 30 second timeout by default, your routes need to return before that time or else the worker is assumed to be hung and it is killed and restarted.

def update_load():
    with app.app_context():
        while True:
            time.sleep(0.5)
            turbo.push(turbo.replace(render_template('loadme.html'), 'load'))

I have an infinite update cycle every second!
you can have a look on http://modbus.online/

reg 6 updates every sec

How are you running Gunicorn? You need to either use threads, or an async server such as gevent or eventlet. See https://flask-sock.readthedocs.io/en/latest/web_servers.html for instructions on how to deploy Flask-Sock (the WebSocket extension used by Turbo-Flask).


Handle scene UIDs in MultiplayerSpawner

Fixes #99116
The spawn issue occurred, because spawner will compare scene_file_path of a node with spawnable paths. Thus we either need to make sure that every path is a path, or convert scene path to UID for comparison.
When SpawnableScenes are created, they get paths assigned, but they need to saved as UID. I'm keeping both values to avoid repeated conversions.

@Faless still needs to review this a bit more closely, but we agreed to merge this as a stopgap solution for 4.4-dev5, and let Fabio re-review later to see if he'd prefer a different approach.

Thanks!


Remove python unlinking in travis config

Part of https://github.com/gtk-rs/gtk/issues/717

Thanks!


The implementation uses most of the test harness from integration.rs,
and handles args and environment variables in the same way as Wasmtime.
Future commits should handle directory mapping as well.

This is now built on top of #65.
Once that is merged, I'll rebase and merge this as well.


Migrate We Are Able activity so it's all on one campaign

Current Behavior
Multiple campaigns were created for We Are Able and both have signups and reportbacks.
Desired Behavior
All of the activity on node 2931 should be migrated over to 5438. We'll need to associate the runs of 2931 to 5438 as well.
Why This Matters
Because we shouldn't have two of the same campaign

@mikefantini which run should signups on 2931 be migrated to?
update signups
where nid = 2931
set nid = 5438
and run_nid = X

@angaither I was thinking we would just keep the signups on the same run but just associate the runs with 5438 instead of 2931. Does that make sense?

:+1:

So 5438 would have 4 runs instead of 2

instead of doing the change in the db, then those campaign runs will need to be updated to point to 5438

@angaither let's coordinate this then because I don't want 2931 is unpublished and not closed. Should I just move those over now and create a placeholder run for 2931?
Also you still need to update the campaign nid for the signups no?

@mikefantini does it matter at all that this campaign is being reopened for a celeb partnership right now?

@namimody @mikefantini should this be done before #6258?

I think #6258 makes sense to do first, great idea @chloealee!

@angaither let's chat about this one IRL to make sure we're on the same page on what needs to be done.


Being prompted multiple times to restart for the insiders build

Environment data

VS Code version: 1.36.1
Extension version (available under the Extensions sidebar): 2019.9.28475-dev
OS and version: macOS
Python version (& distribution if applicable, e.g. Anaconda): XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
Relevant/affected Python packages and their versions: XXX
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Language server

Expected behaviour
To be asked to restart only once for the insiders build
Actual behaviour
Had to reload VS Code 3 times before I stopped being prompted.
Steps to reproduce:

Start with 2019.6.24221
Install 2019.9.28475-dev via .vsix
Reload via the notification
Extension loads
Starts downloading language server
Get notification that “We encountered an issue extracting the Language Server”.
Shortly thereafter get prompted to “Please reload Visual Studio Code to use the insiders build of the extension” (missing a period and why are we saying “Visual Studio Code”?)
Reload via the notification
Get the language server failure message again
Get prompted to reload yet again to use the insiders build
Finally stopped prompting

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
XXX

I'm unable to replicate this at my end.
Lets pair program when you (@brettcannon) get back.


Package request: Shopify-cli 3.x

Project description
Cli to initialize, build, dev, and deploy Shopify apps
Note that shopify-cli 2.x is already in nixpkgs, but 3.x is not.
Metadata

homepage URL: https://shopify.dev/docs/apps/tools/cli
source URL: https://github.com/Shopify/cli
license: mit
platforms: linux, darwin

+1 vote
Was just about to put in a request myself. I am eager to start contributing to Nix, so if no one else takes this before the weekend I'll try to knock out a PR for it.

Seems I've bitten off more than I can chew with this one. If anyone else feels more eager or qualified don't let me hold you back. I'll perhaps keep trying to peck away at this but no idea if or when I'll get it.

I've started work on having a go packaging this up. Hopefully will share a CR within the week.
The change moves it from Ruby to Node so it needs some work to repackage it.

I started repackaging it but the realised that nodePackages already includes @shopify/cli. It was added end of April here: https://github.com/NixOS/nixpkgs/pull/228894
You can run it now using:  nix shell nixpkgs#nodePackages."@shopify/cli"
The current version of shopify-cli in nixpkgs  is officially EOL: https://shopify.dev/changelog/cli-2-x-is-deprecated
So 3 potential options for the existing package:

Deprecate and remove it. Update the top level alias to instruct users to install it via nodePackages.
Update the current package to depend on the node version, and essentially duplicate the nodePackage one
Rename the current package to shopify-cli-2 to indicate its version 2. But given its EOL seems not the best approach.

My recommendation would be 1 (remove it) as the current version is not supported. However discoverability seems harder. Using both the web and CLI search for shopify the nodePackage one does not appear. I can see other packages, e.g. nodePackages.eslint if I search for eslint. Is it something with the @ symbol that impacts the search?
CC @onny who is listed as a maintainer for input.

The Node package nixpkgs#nodePackages."@shopify/cli" is non-functional. It was never tested past just a basic version command. Attempting to spin up a theme or do anything else isn't possible because the Ruby dependencies and the theme dependency aren't there either.

Ah you are right, apologies. I installed it but didn't attempt to setup any themes yet. Looks like it needs @shopify/theme for the actual theme commands.
Ok let me go back to repackaging it and just upgrade it with all its dependencies.

We packaged the v3 shopify cli as a flake. You can find at mrhenry/nix-shopify-cli. Suggestions are very welcome.

https://github.com/NixOS/nixpkgs/pull/324811 adds v3 to nixpkgs. It will be available in nixos-unstable soon.