ci: update to husky 8.0.3 and reactivate hook

This PR resolves issue https://github.com/cypress-io/github-action/issues/743 "Inactive git pre-commit Husky hook" by reactivating the husky hook.
It should also resolve an issue with Renovate. If dependencies which are used in the action are bumped by Renovate and they need to be compiled, Renovate does not know about this step and a PR it produces may be incomplete and fail the CI test .github/workflows/check-dist.yml.
Changes

husky is updated to the latest version husky v8.0.3.
The inactive hook "pre-commit": "npm run format && npm run build && git add index.js dist" is migrated to .husky for v8 usage.

The scripts

npm run format
npm run build

are executed to determine if changes to the core of the action located in

index.js
dist/

need to be committed.
When running on Ubuntu the following will be observed:
Incomplete change made
If index.js was changed and the format and build scripts were not manually run, then a user would see the following as an example when committing through git. The following log output informs of the actions taken:
changes to action source code were detected
action source code changes are added to this commit

The full log is as follows:
git commit -a -m "demo change to index.js source"
action source code is being reformatted and rebuilt

><EMAIL_ADDRESS>format
> prettier --write index.js

index.js 180ms

><EMAIL_ADDRESS>build
> ncc build -o dist index.js

ncc: Version 0.36.1
ncc: Compiling file index.js into CJS
   1kB  dist/thread.js
2820kB  dist/index.js
2821kB  [2850ms] - ncc 0.36.1

changes to action source code were detected
action source code changes are added to this commit
[test/reactivate-husky 2a79b52] demo change to index.js source
 2 files changed, 2 insertions(+)

Complete change made
If index.js was changed and the format and build scripts were manually run by the user, then they would see the following as an example when committing through git:
git commit -a -m "demo change to index.js source"
action source code is being reformatted and rebuilt

><EMAIL_ADDRESS>format
> prettier --write index.js

index.js 184ms

><EMAIL_ADDRESS>build
> ncc build -o dist index.js

ncc: Version 0.36.1
ncc: Compiling file index.js into CJS
   1kB  dist/thread.js
2820kB  dist/index.js
2821kB  [2717ms] - ncc 0.36.1
[test/reactivate-husky 3576b0f] demo change to index.js source
 2 files changed, 2 insertions(+)

Similar output is shown also if files other than index.js are committed. The test is always done and the commit is only modified if necessary.
Windows
When committing on Microsoft Windows there will be additional warnings from git such as
"warning: in the working copy of 'index.js', LF will be replaced by CRLF the next time Git touches it" if the user has modified index.js and has not previously manually executed npm run format and npm run build.
Husky with GitHub Desktop on Windows
There have been multiple issues reported when attempting to use GitHub Desktop with Husky hooks enabled.
Workaround
Create an environment variable
Windows Settings > About > Advanced system settings > Environment Variables
HUSKY=0

to disable Husky if you are using GitHub Desktop on Microsoft Windows.

This PR requires PR https://github.com/cypress-io/github-action/pull/836 to work correctly on Microsoft Windows, so I will leave it in draft status for the time being.

cc: @jaffrepaul

Logs are correctly showing
"husky - Git hooks installed"
Run bahmutov/npm-install@v1
running npm-install GitHub Action
trying to restore cached NPM modules
npm cache hit undefined
installing NPM dependencies
npm at "/opt/hostedtoolcache/node/16.16.0/x64/bin/npm"
/opt/hostedtoolcache/node/16.16.0/x64/bin/npm ci
npm WARN deprecated uuid@[3](https://github.com/cypress-io/github-action/actions/runs/4446206985/jobs/7806242399#step:4:4).[4](https://github.com/cypress-io/github-action/actions/runs/4446206985/jobs/7806242399#step:4:5).0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

><EMAIL_ADDRESS>prepare
> husky install

husky - Git hooks installed

added 1[5](https://github.com/cypress-io/github-action/actions/runs/4446206985/jobs/7806242399#step:4:6)4 packages, and audited [15](https://github.com/cypress-io/github-action/actions/runs/4446206985/jobs/7806242399#step:4:16)5 packages in 4s

31 packages are looking for funding
  run `npm fund` for details

The prerequisite PR https://github.com/cypress-io/github-action/pull/836 is now merged, so this PR is now ready for review.


Graph  Collaborative Filtering implementation

Please Review
@J-Fid
@seenusuvarna

I need to fix the syntax

:+1:


... detected the scraping. Aborting.

Any fix for the following error?
....
at Object.scrape_google_pup (//se-scraper/se-scraper/src/modules/google.js:65:15) name: 'TimeoutError' }
Google detected the scraping. Aborting.
$

By passing it to the scraping configuration:
event = {
	// the user agent to scrape with
	user_agent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36',
	// if random_user_agent is set to True, a random user agent is chosen
	random_user_agent: true,
	// use a proxy for all connections
	// example: 'socks5://<IP_ADDRESS>:1080'
	// example: 'http://<IP_ADDRESS>:48400'
	proxy: 'socks5://<IP_ADDRESS>:1080',
};

It doesn't work even when I set proxy. Is it me, or google change something ?
The proxy works just fine for other browsers (ie. bing, duckduckgo).


Support for bevy::math::Vec3 in addition to nalgebra vectors

I think it would be fitting for a bevy plugin to accept bevy's vector type.
Currently I do the following to use RapierConfiguration:
use bevy::prelude::*;
use bevy_rapier3d::physics::{RapierPhysicsPlugin, RapierConfiguration};
use bevy_rapier3d::rapier::na::Vector;

fn main() {
    App::build()
        .add_plugins(DefaultPlugins)
        .add_plugin(RapierPhysicsPlugin)
        .add_resource(RapierConfiguration {
            gravity: Vector::y(),
            ..Default::default()
        })
        .run();
}

It would be nice if there was a way to use Bevy's Vec3 type rather than having to import nalgebra's vector.
Ultimately, I don't think anything can implement From or Into for this besides nalgebra (which shouldn't depend/care about Bevy of course), but functions in bevy_rapier could be made generic to accept Bevy's Vec3:
        .add_resource(RapierConfiguration {
            gravity: Vec3::unit_y(),
            ..Default::default()
        })

The Bevy's Vec3 is actually the vector from glam. So implementing From or Into requires either glam or nalgebra to (optionally) depend on the other. nalgebra will never have a dependency to bevy, but having an optional dependency to glam could make sense to add this conversions.
Regarding using Bevy's math types as part of the bevy_rapier API: I am not sure whether this is a good thing or not. First, it would be impossible to completely remove the need for the user to use nalgebra types because that's what rapier uses everywhere. So we could make some types like the RapierConfiguration use Bevy's vector, and leave the types coming from rapier as-is, requiring the end user to use nalgebra types at some point anyways. Or we could keep using nalgebra types in RapierConfiguration and say that nalgebra is used for everything in bevy_rapier. This second options sounds more coherent to me.

The Bevy's Vec3 is actually the vector from glam. So implementing From or Into requires either glam or nalgebra to (optionally) depend on the other. nalgebra will never have a dependency to bevy, but having an optional dependency to glam could make sense to add this conversions.
Regarding using Bevy's math types as part of the bevy_rapier API: I am not sure whether this is a good thing or not. First, it would be impossible to completely remove the need for the user to use nalgebra types because that's what rapier uses everywhere. So we could make some types like the RapierConfiguration use Bevy's vector, and leave the types coming from rapier as-is, requiring the end user to use nalgebra types at some point anyways. Or we could keep using nalgebra types in RapierConfiguration and say that nalgebra is used for everything in bevy_rapier. This second options sounds more coherent to me.

What about a supertrait that implements From?
This is new to me but it might look like this:
trait FromVec: std::convert::From<Vec3> {
    fn from_vec(&self);
}

impl FromVec for Vector3<f32> {
    fn from_vec(&self, vec: Vec3) -> Vector3<f32> {
        Vector3::new(vec.x, vec.y, vec.z)
    }
}

I know you can't implement foreign traits on foreign types, but implementing an extension trait should be possible.
Perhaps Into would be better? I'm not super familiar with either of the two.
I think this would allow users to supply either type and bevy_rapier to only care about the nalgebra one.

What about a supertrait that implements From?
This is new to me but it might look like this:
trait FromVec: std::convert::From<Vec3> {
    fn from_vec(&self);
}

impl FromVec for Vector3<f32> {
    fn from_vec(&self, vec: Vec3) -> Vector3<f32> {
        Vector3::new(vec.x, vec.y, vec.z)
    }
}

I know you can't implement foreign traits on foreign types, but implementing an extension trait should be possible.
Perhaps Into would be better? I'm not super familiar with either of the two.
I think this would allow users to supply either type and bevy_rapier to only care about the nalgebra one.

struct MutualVec {
    x: f32,
    y: f32,
    z: f32,
}

impl From<Vec3> for MutualVec {
    fn from(vec: Vec3) -> Self {
        MutualVec {
            x: vec.x,
            y: vec.y,
            z: vec.z
        }
    }
}

impl Into<Vector3<f32>> for MutualVec {
    fn into(self) -> Vector3<f32> {
        Vector3::new(self.x, self.y, self.z)
    }
}

// ...
        .add_resource(RapierConfiguration {
            // The conversion could be done behind the scenes
            gravity: MutualVec::from(-Vec3::unit_y()).into(),
            ..Default::default()
        })

This would work, whether it's advisable or worth it... 🤷

struct MutualVec {
    x: f32,
    y: f32,
    z: f32,
}

impl From<Vec3> for MutualVec {
    fn from(vec: Vec3) -> Self {
        MutualVec {
            x: vec.x,
            y: vec.y,
            z: vec.z
        }
    }
}

impl Into<Vector3<f32>> for MutualVec {
    fn into(self) -> Vector3<f32> {
        Vector3::new(self.x, self.y, self.z)
    }
}

// ...
        .add_resource(RapierConfiguration {
            // The conversion could be done behind the scenes
            gravity: MutualVec::from(-Vec3::unit_y()).into(),
            ..Default::default()
        })

This would work, whether it's advisable or worth it... 🤷

This MutualVec solution you are mentioning here is actually very similar to what the mint crate allows you to do. And it turns out that nalgebra implements the traits from mint if you enable the mint feature of nalgebra.

This MutualVec solution you are mentioning here is actually very similar to what the mint crate allows you to do. And it turns out that nalgebra implements the traits from mint if you enable the mint feature of nalgebra.

Bevy's Vec3 can be turned directly .into() nalgebra's vector by adding the following to your Cargo.toml:
nalgebra = {version = "0.25", features = ["convert-glam"]}

bevy_rapier should probably turn on this feature by default

I'm closing this since the enabling the nalgebra feature convert-glam013 (for glam 0.13/bevy 0.5) or the convert-glam015 (for glam 0.15/bevy master) allows easy conversions between nalgebra and glam. See that page of the user-guide.


Ruby: Modify LRO client creation to follow new service path pattern

What
Ruby GAPICs now support modifying the service path by subclassing and overriding the path attribute on the service object. Passing a service path directly to the service object constructor is deprecated. We should follow our own recommended pattern in GAPICs that instantiate LRO clients; currently, we pass the service path to the constructor, which is not recommended.
Context
https://github.com/googleapis/gax-ruby/issues/102

This was done in #1702.


Bugfix: on language without preposition, ingredients with container_size rule will throw ArgumentError

On language without preposition, ingredients with container_size rule will throw ArgumentError:
ArgumentError: wrong number of arguments (1 for 0)
/gems/parslet-1.7.0/lib/parslet/atoms/sequence.rb:43 in to_s
/gems/parslet-1.7.0/lib/parslet/atoms/sequence.rb:43 in block in to_s_inner
/gems/parslet-1.7.0/lib/parslet/atoms/sequence.rb:43 in map
/gems/parslet-1.7.0/lib/parslet/atoms/sequence.rb:43 in to_s_inner
/gems/parslet-1.7.0/lib/parslet/atoms/base.rb:140 in to_s
/gems/parslet-1.7.0/lib/parslet/atoms/base.rb:148 in inspect
/gems/parslet-1.7.0/lib/parslet/atoms/sequence.rb:14 in initialize
/gems/parslet-1.7.0/lib/parslet/atoms/dsl.rb:44 in new
/gems/parslet-1.7.0/lib/parslet/atoms/dsl.rb:44 in >>
[GEM_ROOT]/bundler/gems/ingreedy-79fdaa151008/lib/ingreedy/ingreedy_parser.rb:48 in block in <class:Parser>

Thanks @firewalker06! And sorry for the delay, was knee-deep in German/French wine for the past weeks :sweat_smile:
Made a tweak after merging: https://github.com/balvig/ingreedy/commit/68437582b374e29e08cde7b4a657ebfc42ef747e I'm no parslet expert but seems breaking out things into smaller rules is the way to go!

Ah, that is simpler :+1: Thanks :bow:


Support casting in LIMIT clauses for compatibility with postgres_fdw (12+)

Problem Statement
In certain circumstances (requested in the Community) it can be useful to use a FOREIGN DATA WRAPPER in a PostgreSQL instance to have FOREIGN TABLEs from a CrateDB instance.
Starting on PostgreSQL 12, postgres_fdw will pass LIMIT clauses with a cast like:
LIMIT 1::bigint

This is currently not supported by CrateDB and it fails with:
mismatched input '::' expecting {<EOF>, ';'}

Possible Solutions
Use PostgreSQL 11.19 which is still supported.
Considered Alternatives
There are workarounds when the client/input query can be controlled, but in the case mentioned in the Community there was a 3rd party tool involved.

@hlcianfagna Thx for reporting this improvement, It's been implemented and will be included in the next release.


Add make command for previewing API docs

Much easier than the previous method of copying over to the docs
repository and generating the docs.
And, as @cpuguy83 pointed out, that actually didn't work
because the PR that adds Swagger docs isn't merged yet. Oopsy.
Signed-off-by: Ben Firshman<EMAIL_ADDRESS>

@cpuguy83 Fixed!

Thanks @bfirsh this should get reviewers going
do you think we can add some basic skinning from the docs.docker.com site, or would that be difficult?

@thaJeztah It doesn't have the docs.docker.com skin - that's how it looks. The only thing broken is the colour missing in the top-left.
I can add that when I get time, but I don't think it's critical. If this gets merged before I'll get to it I'll open a follow-up to fix it. :)

Merging since tests won't do anything for this PR.


data render script

Nice work!
Can you also share your render script? Are you using the same one as zero123?

Hi, the rendering script is blender_script.py.


Off-Chain Pages - v1.0

Support for the following pages is needed for v1.0:
off-chain
off-chain/data
off-chain/file-explorer
off-chain/datatypes


pipenv update --outdated crashes with IndexError in Git repo

When I run pipenv update --outdated, it crashes with an IndexError, but only if a package is installed in editable mode where the package is also a Git repository.
This looks kind of like pypa/pip#4759? I don't know if you would be willing to merge the PR that apparently fixes it into Pipenv's vendored Pip; alternatively, ignoring lines from Pip that start with # might work, since apparently requirements files are allowed to contain comments, and I guess Pipenv is probably parsing the output of pip freeze.
$ python -m pipenv.help output
Pipenv version: '11.9.0'
Pipenv location: '/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv'
Python location: '/home/josh/.local/venvs/pipenv/bin/python'
Other Python installations in PATH:

2.7: /usr/bin/python2.7

2.7: /usr/bin/python2.7

3.5: /usr/bin/python3.5m

3.5: /usr/bin/python3.5

3.6: /usr/bin/python3.6m

3.6: /usr/bin/python3.6

2.7.12: /usr/bin/python

2.7.12: /usr/bin/python2

3.5.2: /usr/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.3',
 'os_name': 'posix',
 'platform_machine': 'armv7l',
 'platform_python_implementation': 'CPython',
 'platform_release': '3.10.18',
 'platform_system': 'Linux',
 'platform_version': '#1 SMP Sat Feb 24 13:21:23 PST 2018',
 'python_full_version': '3.6.3',
 'python_version': '3.6',
 'sys_platform': 'linux'}

System environment variables:

GIT_PS1_SHOWDIRTYSTATE
SSH_AGENT_PID
XDG_DATA_HOME
PYENV_ROOT
SHELL
TERM
PIPENV_VENV_IN_PROJECT
RIPGREP_CONFIG_PATH
TMUX_VERSION
NVM_DIR
USER
LS_COLORS
DEBEMAIL
SSH_AUTH_SOCK
TMUX
MAIL
PATH
PWD
EDITOR
LANG
TMUX_PANE
GIT_PS1_SHOWUNTRACKEDFILES
GPG_TTY
HOME
MANPAGER
SHLVL
XDG_CONFIG_HOME
GIT_PS1_SHOWSTASHSTATE
PIPENV_SHELL_FANCY
XDG_CACHE_HOME
LOGNAME
GIT_PS1_SHOWUPSTREAM
VISUAL
TMUX_PLUGIN_MANAGER_PATH
DEBFULLNAME
GOPATH
LESSOPEN
LESSCLOSE
_
OLDPWD
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
PYTHONUNBUFFERED

Pipenv–specific environment variables:

PIPENV_VENV_IN_PROJECT: 1
PIPENV_SHELL_FANCY: 1

Debug–specific environment variables:

PATH: /home/josh/go/bin:/home/josh/.pyenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/josh/.cargo/bin:/home/josh/.cabal/bin:/home/josh/bin:/home/josh/.local/bin
SHELL: /bin/bash
EDITOR: vim
LANG: en_GB.UTF-8
PWD: /home/josh/pipenv_test

Contents of Pipfile ('/home/josh/pipenv_test/Pipfile'):
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]
"e1839a8" = {path = ".", editable = true}

[dev-packages]

[requires]
python_version = "3.6"

Contents of Pipfile.lock ('/home/josh/pipenv_test/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "0e120892e832e8b76faa321dfe89c434016f9d29056cb6f8ecd1cf2dae86895b"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.6"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.python.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "e1839a8": {
            "editable": true,
            "path": "."
        }
    },
    "develop": {}
}

Expected result
The outdated packages should be displayed? (I've actually never used this command before, but I guess it probably shouldn't just crash 😃)
Actual result
$ pipenv update --outdated
Traceback (most recent call last):
  File "/home/josh/.local/bin/pipenv", line 11, in <module>
    sys.exit(cli())
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/vendor/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/cli.py", line 731, in update
    core.do_outdated()
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/core.py", line 1698, in do_outdated
    packages.update(convert_deps_from_pip(result))
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/utils.py", line 520, in convert_deps_from_pip
    req = get_requirement(dep)
  File "/home/josh/.local/venvs/pipenv/lib/python3.6/site-packages/pipenv/utils.py", line 127, in get_requirement
    req = [r for r in requirements.parse(dep)][0]
IndexError: list index out of range

I inserted some debugging, and in the final stack frame, the value of dep is "## !! Could not determine repository location"; a couple of frames up in pipenv.core.do_outdated, the value of results is ['## !! Could not determine repository location', 'foo==0.1'].
Steps to replicate
Run in an empty directory:
cat > setup.py << EOF
from setuptools import setup

setup(
    name="foo",
    version="0.1",
)
EOF
pipenv --python 3.6
pipenv install -e .
pipenv update --outdated  # works fine, no output
git init
pipenv update --outdated  # now everything explodes

I think this is kind of complicated to be honest mainly due to the VCS involvement. I’ve been sitting on a significant refactor of the requirement parser and this is one of the pieces I am considering. If I put the branch up, maybe you can grab it and see how it works for you. Probably related: #1690

Sure, I'm happy to test whatever.
As a quick fix, pipenv.core.do_outdated could remove results from Pip that start with #, via something like:
results = filter(lambda r: not r.startswith("#"), results)

before passing them to convert_deps_from_pip.
Really it should remove comments from within lines as well, but I would be surprised if pip freeze ever emitted those.

@anowlcalledjosh sorry for dropping the ball on this, was working through a big datacenter migration this weekend.  I looked over that PR, seems like a good idea.  I I have time I can bring it in, but feel free to PR it if you like as well.  I think we keep commented lines for some reason, would have to dig to find out why


Set valid device types for application endpoints

Problem
Several samples are using the root node device type for application
endpoints. This prevents proper identification of the device and is
not compliant with the specification:
From the spec, "Endpoint Composition" section: There SHALL be only
one root node endpoint for the node.
Change overview
Add types to all non-root endpoints in examples/.
all-clusters-app does not correspond well with any single device type.
This sets it to on/off light. It may be useful to reorganize this
sample into additional endpoints each with a coherent device type.
Testing
Built & commissioned each app, read descriptor cluster.

@mspang - please update the generated files - I think you picked up the 'unstable run' version of zap output :(


Add documentation for API's

Documentation for all the API's to be added

Do you want documentation with swagger ui?

Could you please post an example, I haven't used swagger.

there are examples with code and screen shots
https://www.baeldung.com/swagger-2-documentation-for-spring-rest-api

Thank you for sharing, for now i had simple text based docs in mind. Just basic stuff.


Fixed layout issue caused by the new Public Preview card in Lexical

refs https://github.com/TryGhost/Team/issues/2914

with mobiledoc, the Public Preview card would render a  html comment. This comment is then transformed into either a CTA to upgrade (= the user doesn't have full access to the post), or left untouched (= the user has full access to the post)
now with Lexical, a HTML element wrapper is necessary around the html comment: . This change hides the extra  wrapper when necessary, so that the final layout is not affected

Update: not a good idea. Closing PR


[FR] add something to store voteskip votes

add a new thing (in the guildqueue) to store how many votes there have been to skip a song

o wait i can use costum song data


New splash screen for 3.4

Hmm, if it is all possible, I would prefer not to have the version number in the resources/splashscreen/updatersplash.gif. It didn't use to have one. Just to ease the maintenance burden :D

Hi @tonihele , can you check if this is better?
I check in a fix for the updatersplash.

Awesome thanks! Let's merge after 24h to wait for any other comments


How to reproduce the result of MixStyle?

Hi!
Thanks for providing this great repo! I have one question about the result of MixStyle result. In Table 1 and Table 2 of your paper, the results of MixStyle are seen to be conflicting. The performances of MixStyle on PACS are  85.2 and 83.9, respectively. I have noticed that the MixStyle results in Table 1 copy from SWAD. Is that mean you produce the performance in Table 2 by your code?  How can we reproduce the result of MixStyle in Table 2?
I have made some efforts to reproduce your MixStyle result, but all of them come to fail. The result is five percent under your report.
Could you release your command or code of ERM+Mixstyle? That will be very helpful to me.
Thanks in advance.

Hi, thanks for your interest in our work.
Note that the results of Mixstyle in Table 1 and Table 2 are not contradictory. For the results in Table 1, we directly used the results of SWAD (at this time, 80% of the data was used for training). And in Table 2,  we split datasets into
training (60%), validation (20%), and test (20%) splits, i.e., 60% of the data was used for training. Therefore, the discrepancy between the two results is due to the difference in the experimental settings.
The result of MixStyle in Table 2 is easy to obtain; you can follow the command on SWAD to reproduce the MixStyle result: set indomain_test option to True. You can refer to SWAD for more details.

Thanks for your quick reply!
I take your suggestions and finally reproduce the results.


Analysis refactor gui part3

Depends on #2077 so review merge that one first.
This PR partially fixes the artifact pages so they work both in the study pipeline and in the analysis pipeline. I still need to fix a couple of functions and handlers but I want to keep the PRs small.
I've moved the artifact handlers out from the study_handlers folder and created a new artifact_handlers folder, since now it doesn't make sense to have them under the study specific list.
I haven't deleted the old code (will do in another PR).
The functionalities changed here are: (1) being able to load the page, (2) modify the artifact name, and (3) being able to submit the artifact summary.
I've done some minor modifications to the artifact interface, which in my opinion improves it: (1) I moved the visibility information next to the name and ID and I put all the buttons next to each other in the same row.
Here is a GIF which shows the functionality and the GUI changes:

@antgonza ready for review -this PR end up being a bit bigger than I expected - although one reason for that is because I moved the handlers from one file to the other (I haven't removed them from the original location in here)


Telegram plugin

First development of a plugin that allows OpenCharacters to integrate with Telegram via the bot API. I plan to support multiple chats and characters soon but for now this is the first pass that proves the concept is possible.

Awesome, thanks for sharing this! If I understand correctly: You need to keep your browser tab open for this to work, and you need to add await import("./plugins/telegram/custom.js") to your characters custom code? (I've only skimmed the code - might be misunderstanding, but if that's correct then it might be a good idea to add that to the usage part of the readme)
If you end up improving on this, then it would also be great to have a Replit/Glitch demo so someone without much dev experience can spin up fast by just remixing/forking, and adding their token. Would also be cool to see a little video demo of it working!


Support Structured Streaming

Hi guys,
Any intentions to support Spark Structured Streaming API? I couldn't find any issue.
Thanks!

FYI - https://github.com/datastax/spark-cassandra-connector/issues/546

Sorry. I recommend adding this notification to the Issue template :)

Recreated here:
https://datastax-oss.atlassian.net/browse/SPARKC-510

I don’t maintain this project just happen to notice your issue as I was browsing.


Trading in Euros

Hi! I have now 76.87 EUR. I started with 79.01 EUR (12 days ago). Every time this bot makes mistakes.
Should I change something config for this currency? (maybe default_logic.js)
Does anyone trading in this currency?

You need to change the strategy for EURO otherwise you will make a loss.
On Sun, Oct 2, 2016, 18:05 itsMichael<EMAIL_ADDRESS>wrote:

I have now 76.87 EUR. I started with 79.01 EUR (12 days ago). Every time
this bot makes mistakes.
Should I change something config for this currency? (maybe
default_logic.js)
Does anyone trading in this currency?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/carlos8f/zenbot/issues/76, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHMwQwTJlo8eBYxdRwvKDHMfOiR-hgXcks5qv9ZYgaJpZM4KMCyl
.

Have you got any checked settings?

Simply change RSi High and Low and run in backtest mode till you got some
nice values in ROI.
On Sun, Oct 2, 2016, 18:11 itsMichael<EMAIL_ADDRESS>wrote:

Have you got any checked settings?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/carlos8f/zenbot/issues/76#issuecomment-250979175, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHMwQ19v9ITO6XRg9YWwI-dKwrX5gyO0ks5qv9fFgaJpZM4KMCyl
.

You may want to also play with the rs.min_performance variable. I have found it can make a big difference with some pairs.

I'm having the same issue. Simulation with default parameters gets me 0.96 ROI. If anyone has good values for default_config for trading BTC<>EUR on GDAX, please share.

I set rsi_up = 70 and rsi_down = 30, but it get worsed.

Try 46 low 68 high
On Mon, Oct 3, 2016, 16:05 itsMichael<EMAIL_ADDRESS>wrote:

I set rsi_up = 70 and rsi_down = 30, but it get worsed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/carlos8f/zenbot/issues/76#issuecomment-251114329, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHMwQ4BlxU6WP0UJgqgv5jv7y6GPK4kiks5qwQuMgaJpZM4KMCyl
.

I too am having very low ROI on simulations, has you can see on issue [https://github.com/carlos8f/zenbot/issues/62] , but I thought it was from bad/corrupted historical data and was waiting for the repair tool to clear this out.
I've noticed that EUR trading has far less data than USD, never the less, the bot should use machine learning to adjust trading strategy instead of setting manual parameters and hopping for the best.

Same here, trading in EURO results in negative ROI

@RDash21 These settings also don't work good :/

I am not here to configure your bot for you... you have to tweak/try and
see which gives the best ROI for you. This changes and varies per situation.
On Wed, Oct 5, 2016 at 7:51 PM itsMichael<EMAIL_ADDRESS>wrote:

@RDash21 https://github.com/RDash21 These settings also don't work good
:/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/carlos8f/zenbot/issues/76#issuecomment-251748585, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHMwQ5cDgZ8NcRRM5fuLPluttpxFuykrks5qw-O2gaJpZM4KMCyl
.

I guess this is resolved...


Problems with JDK9?

Ionic version:
[ ] 2.x
[ x ] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[ x ] bug report
[ ] feature request
Current behavior:
Recentemente atualizei o JDK para a versão 9 e desde então a criação de apk retorna o erro:
Requirements check failed for JDK 1.8 or greater.

Retorno do java -version:
java version "9"
Java(TM) SE Runtime Environment (build 9+181)
Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)

Expected behavior:
APK creation
SIfteps to reproduce:
The command:
ionic cordova build android --prod --release

Other information:
It's real problem from the ionic? Other softwares doesn't any problem with the new version.
Ionic info:
cli packages:

    @ionic/cli-utils  : 1.12.0
    ionic (Ionic CLI) : 3.12.0

global packages:

    cordova (Cordova CLI) : 7.0.1

local packages:

    @ionic/app-scripts : 2.1.4
    Cordova Platforms  : android 6.2.3 ios 4.5.0
    Ionic Framework    : ionic-angular 3.6.1

System:

    Android SDK Tools : 26.0.2
    Node              : v8.5.0
    npm               : 5.4.2
    OS                : Linux 4.12

Misc:

    backend : legacy

Hello! Thank you for opening an issue with us!
As this appears to be an issue with Ionic App Scripts and not with the Ionic Framework, I will move this issue to https://github.com/ionic-team/ionic-app-scripts. Please follow the issue over and provide any further feedback or information over there.
Thank you for using Ionic

This issue was moved to ionic-team/ionic-app-scripts#1237


NYT Paywall

New York Times

Paywall appears after a certain number of articles

https://www.nytimes.com/2019/10/19/business/economy/workers-strike-economy.html

Thanks for reporting. Will look into this soon, I wonder if they have changed their JS engine.

Thanks for reporting. Will look into this soon, I wonder if they have changed their JS engine.

Looks like the ?mod=rsswn method was patched directly or indirectly..
I noticed some other devs tinkering with Google Bot as a user agent to bypass WSJ, NYT etc., could be possible to integrate it here

8b87467 fixes this problem.


Rudimentary CUDA support infrastructure

Build-time check for Cuda toolkit as optional dependency.  This can be explicitly disabled with OIIO_USE_CUDA=OFF (though currently, it defaults to off, you have to turn it on at build time because this is all still experimental).  When this is enabled at build time, C++ preprocessor symbol OIIO_USE_CUDA will be defined within the OIIO codebase.
OIIO global attribute("gpu:device", "CUDA") can be used to enable CUDA functionality, which at this point doesn't do anything other than initialize the CUDA device and find out information about it.  Several global getattribute("cuda:*") queries let you find out some information about any device found.
I'm trying to keep a lot of the approaches fairly generic, so that the interface won't need to change much to allow OpenCL or Metal or whatever else comes along, though for now I'm trying to flesh out the implementation mostly with CUDA.
oiiotool adds a new --cuda option, reserved for enabling CUDA functionality. Currently the only way this is used is to print information about the CUDA device in the oiiotool --help messages. An example of that is:
$ oiiotool --cuda --help
oiiotool -- simple image processing operations
...

OIIO <IP_ADDRESS>spi | Linux/x86_64
    Build compiler: gcc 9.3 | C++17/201703
    HW features enabled at build: sse2,sse3,ssse3,sse41,sse42
    CUDA 11.6.0 support enabled at build time
...
Running on 32 cores 187.3GB sse2,sse3,ssse3,sse41,sse42,avx,avx2,avx512f,
    avx512dq,avx512cd,avx512bw,avx512vl,fma,f16c,popcnt,rdrand
Compute hardware available: CUDA on Quadro RTX 6000, driver 12020,
    runtime 11060, compat 705, memory 23.6 GB

Note that at this point, we aren't actually using CUDA for anything. This is just setting up some basics for future expansion. It's all hidden in the pvt namespace for internal use only, and any of the functions or nomenclature may change as we continue to add functionality. I want to iterate on it a bit before it's in any way exposed in public headers or interfaces.
I'm a big fan of introducing even big strategic changes in the form of a series of MVP easy to review discrete steps. This step's only goals are: (a) allowing the build system to find and link against the CUDA Toolkit; (b) allowing runtime initialization and querying of a few basic facts about the device found; (c) start noodling around just a bit with function and attribute interfaces to gain a little experience that will guide what we eventually want.
LONG TERM goals of this initiative include:

A full TextureSystem work-alike that can be used from CUDA (and possibly other compute device APIs) based renderers and with OSL's OptiX back and, having an analogous (ideally identical) interface and as close as possible to feature parity with CPU TextureSystem.

Augment ImageBuf with the ability to store its images in GPU (or unified) memory and for IBA functions to be able to operate on those GPU-side buffers with GPU compute kernels, somewhat analogously to how libraries like PyTorch provides optional GPU support for tensor operations. (The hope is that this improves impage processing performance, though it's possible that it'll turn out that typical OIIO image processing workflows are so I/O dominated that there's not a lot of potential upside.  I think we'll have to try before we really find out if it's going to be worth it.)

Allow image reading/writing plugins (or other parts of OIIO functionality) to leverage a GPU if available, and if there is something productive they can do with it.

Do any of the existing CI runners have CUDA installed?

Yes, all of the ones using ASWF containers have CUDA, so they're building against it.
They're not finding GPUs at runtime, though, so by the time we're executing CUDA code, we'll want to get set up using the paid runners with GPUs. I'm long overdue getting that set up for OSL, as well, so will probably kill two birds with one stone there.

Does this seem ok to everybody as a first step, and then we'll keep building on top of it?


How to implemen server-side in Lumen?

I need example how to set filter search, and pagination in back end?

This is not related to the package. Please ask somewhere else

This is not related to the package. Please ask somewhere else

So I have to setting like (search, pagination, etc) in vue?


TEPHRA-94 Drop support for HBase 0.94

Removes the HBase 0.94 compatibility module and the supporting docs.

There is an HDFSUtil class that is a fork of an HBase 0.94 class. Perhaps it does not matter, but should that be updated, too?

It seems that some of the methods in the compat modules can now be moved back to the core, because they are identical for .96 and .98

There is an HDFSUtil class that is a fork of an HBase 0.94 class. Perhaps it does not matter, but should that be updated, too?

That is only used in the WAL recovery process, so it's not directly tied to the HBase 0.94 compatibility.  We could potentially replace that with use of the actual HBase class, but that will require plugging in to the compatibility layer.  I think it should be handled in a separate issue.

It seems that some of the methods in the compat modules can now be moved back to the core, because they are identical for .96 and .98

It would be really nice to eliminate some of the code duplication between the modules, now that we don't have the KeyValue/Cell differences to deal with.  However, I think we should keep core clear of any HBase dependencies.  We could potentially have a parent hbase-compat module where common bits could go.  There is still no guarantee of binary compatibility, though, so this should still be compiled against the correct HBase version.  And there will be more client-side API changes coming in with HBase 1.0.  I think refining this structure will be an ongoing effort.

Makes sense. LGTM


feat: update expat to 2.6.1

XML parsing C library - example application
Issue: https://github.com/linuxdeepin/developer-center/issues/7284
Log: update repo

/integrate


Adding desktop and getDevice method

Also adding some test in order to cover these new feature.

See inline comment. Thank you for taking the time to suggest this change, but I would like to leave desktop assertions out of isMobile.


Intermittent driver crash

Info

Camera Model
D415

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Platform
PC

SDK Version
2.22.0

Language
C++

Issue Description
We are using a setup of 12 D415 cameras connected to a PC (i7/16GB RAM). We are using high quality USB3 cables and connecting the cameras through powered USB3 hubs. We had an exisitng setup with different depth cameras(non- Intel) which was working fine. Currently we are using the driver built with the OpenNI2 wrapper enabled(from librealsense2 2.22 code). While running our application, we are observing intermittent driver crash. I have attached 2 screenshots of the call stack(one for release version of the driver and other with the debug version with symbols). Can you help us out as to what might be causing this?

@bugviz, merging this ticket to the Zendesk ticket. Let's continue the discussion and debugging through Zendesk.
I will go ahead and close this ticket now. Thank you.


Minor refactoring

Remove unneeded newlines. Fix type for consts BackupStarting, BackupRunning, BackupFailed, BackupSucceeded from string to PXCBackupState. The same for list of const with type BcpRestoreStates. Changed fmt.Errorf("%v", err) to fmt.Errorf("%w", err) to wrap errors. Used more idiomatic errors.Is instead of switch err == AnotherErr. Formatted imports with Goimport.
Signed-off-by: Serhii Mariiekha<EMAIL_ADDRESS>

Test name
Status

big-data
passed

upgrade-haproxy
passed

scaling
passed

recreate
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

smart-update
passed

security-context
passed

demand-backup
passed

pitr
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
failed

scheduled-backup
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/788/commits/714170f0108866467e3998c897c11c25c64dccdb
image: perconalab/percona-xtradb-cluster-operator:PR-788-714170f0

Test name
Status

upgrade-haproxy
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/788/commits/714170f0108866467e3998c897c11c25c64dccdb
image: perconalab/percona-xtradb-cluster-operator:PR-788-714170f0

Test name
Status

haproxy
passed

storage
passed

big-data
passed

upgrade-haproxy
passed

recreate
passed

restore-to-encrypted-cluster
passed

scaling
passed

demand-backup
passed

scaling-proxysql
passed

pitr
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

upgrade-proxysql
passed

self-healing
passed

smart-update
passed

upgrade-consistency
passed

init-deploy
passed

self-healing-advanced
passed

limits
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/788/commits/714170f0108866467e3998c897c11c25c64dccdb
image: perconalab/percona-xtradb-cluster-operator:PR-788-714170f0


xrepo search vcpkg::flashlight-cuda gives no results

Note: If you use the fuzzy expressions such as 'can't use/no effect/problem/error', but don't give any relevant auxiliary information according to the template below, this issue will be not replied.

Describe the bug
A clear and concise description of what the bug is.
xrepo search vcpkg::flashlight-cuda doesn't return a result for the flashlight-cuda package on vcpkg.
Expected behavior
A clear and concise description of what you expected to happen.
It should return some result, as the package actually exists on vcpkg.
Error output
If applicable, please add verbose the errors output to help us analyze your problem.

If it is a xmake related compilation problem, please add the -v -D parameter and give the detailed compilation output information.

Related Environment
Please provide compiling and running environment information:

xmake version: xmake v2.5.3+202104301933,
os: ArchLinux
target platform: Linux

Additional context
Add any other context about the problem here.

xrepo does not yet support searching for packages in third-party package management. Currently, only packages in xmake-repo can be searched.

I'll leave it open as feature request.

I have support it on xmake/dev. see https://github.com/xmake-io/xmake/issues/1422

Nice, thanks. Waiting for a new release so I can give it a try.


⚠ PrivateHD has degraded performance

In 15ab1c0, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2607 ms

Resolved: PrivateHD performance has improved in f88e6a6.


skip __main__.py in package scan

A module's __main__.py file should probably not be executed as part of the slots scan. It almost always executes unwanted code.

fixed in version 0.1.2


Add inplace methods to Zero and One

Adds the following default implemented methods to Zero and One:
fn set_zero(&mut self) {
    *self = Zero::zero();
}

fn set_one(&mut self) {
    *self = One::one();
}

This allows for reuse of BigNums.

@cuviper I looked at the guidelines and think that set or make should both be fine even if they sound somewhat odd. Changed it to set?  :thinking:

I also changed the functions to not return &mut Self. I now believe doing so is  a somewhat bad practice as it adds uncertainty about what exactly this method is doing.

bors r+


Module Annotation Warning

From
dependencies {
    implementation("io.github.androidpoet.countrypicker:0.1.1")
}

TO
[Version]
countrycode-picker = "0.1.1"

[libraries]
countrycode-picker = {module = "io.github.androidpoet:countrypicker", version.ref = "countrycode-picker"}

[dependencies]
implementation(libs.countrycode.picker)

This personal preference for user unrelated to the project.


Fix tut dependency, bump to 0.3.1

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #66   +/-   ##
=======================================
  Coverage   67.71%   67.71%
=======================================
  Files           8        8
  Lines         254      254
  Branches        3        3
=======================================
  Hits          172      172
  Misses         82       82

Continue to review full report at Codecov.

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

Thanks @ilya-murzinov!


[Feature] Backup Job (Cron)

General

[X] My feature does not exist in the latest version of Nexterm.
[X] I have checked that my feature has not been suggested by anyone else.

Your Idea
A backup function that allows you to create a backup via SMB, FTP or Local.
This should be configurable on the web interface

+1 on this, and It would be great to have Google Drive and/or WebDAV options too


RootTrustManager not found on Kindle Fire devices

Changes introduced with #461 don't work on Kindle Fire devices. android/security/net/config/RootTrustManager is not found causing cert chain verification to fail. The code works as expected on non amazon devices. A similar issue in cpprestsdk has an alternate solution that may work for Kindle devices as well but I haven't tested it

Feel free to PR fix, or talk to us on private channels to coordinate plan.


merge after bioccheck()

@zhiiiyang I just ran BiocCheck() - I had to change things a little bit to make it work (just a bit of syntax in my code, nothing major).

I am tagging @yangleicq to review this issue.

@rvitancol @NicoleEO, could you tell Ned what other changes are needed on specs and reqs per our discussion on standup today?

@ned-procogia Can you also update the Reqs and Specs and corresponding unit tests for the changes that you made? One way to check what these are is to check the following: 1. functions where Inputs and outputs were changed. 2. Functions where the calculations were changed. 3. And also add additional unit test when necessary for the code you added.  Thanks.

@rvitancol I will update the reqs and specs then send another pull request

@ned-procogia, a quick reminder, you don't have to close the PR every time we have any new requests. You can just keep pushing the changes in the same PR and make a comment about your changes.

@zhiiiyang I didn't know that. Will bear that in mind, thanks!


Fix warmup for diffusers when batch size < throughput_warmup_steps

What does this PR do?
Fixes throughput calculation for diffusers when batch size < throughput_warmup_steps

LGTM

@regisss thanks for review, updated PR with all of your suggested fixes

@dsocek Will just need to run make style and then I merge this one :slightly_smiling_face:

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@dsocek Will just need to run make style and then I merge this one 🙂

@regisss Sounds good, done!

@dsocek The CI failed with this error:
UnboundLocalError: local variable 't1_inf' referenced before assignment

There must be a case in CI where num_inference_steps is smaller than throughput_warmup_steps.

@dsocek The CI failed with this error:
UnboundLocalError: local variable 't1_inf' referenced before assignment

There must be a case in CI where num_inference_steps is smaller than throughput_warmup_steps.

hmm possibly for turbo case.  I will check an fix this


[BUG] As user, I want the progress bar to show the number of answered questions  for the selected question catalog

As user, I want the progress bar to show the number of answered questions for the selected question catalog.
Actual status

the progress bar display the number of answers for the project
the numbers in the progress bar are not readable for large and small numbers of answered questions

Accepted status

[ ] the progress bar displays the number of answers only for the chosen catalog
[ ] the numbers in the progress bar are displayed in the center of the bar

Reference
https://github.com/rdmorganiser/rdmo/releases/tag/1.4

Thanks for reporting, we will look into this.

This was fixed in RDMO 1.5.


Introduce linter and type checker

Partially resolve #5
Depend on #6
Motivations
This PR aims to introduce the linter and type checker to improve the code readability and reliability. I use pre-commit, ruff, and mypy. The change looks huge, but almost changes are obvious (some parts are automatically generated).
Description of changes

Add .pre-commit-config.yaml for the config file of linter and type checker.
Add dependencies in the pyproject.toml.
Apply linters and type checker on whole codebase.

thanks @HideakiImamura ! Sorry for the long delay. I'll take a look at the PR in the coming few days and get back to you.

Thank you for the comment. I fixed the conflicts. Could you review and merge this PR?

Again apologies for the delay :/ The PR looks good to me actually. @Neeratyoy ?


gym error on macOS Ventura 13.0, Xcode 14.0.1 & Xcode 14.1

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Command executed
lane :buildIpa do
    gym(
      scheme: "xxx",
      output_name: "#{outputName}",
      workspace: "xxx.xcworkspace",
      export_method: "#{exportMethod}", # app-store、ad-hoc、development、enterprise
      include_bitcode: false,
      include_symbols: true,
      silent: true,
      clean: true,
      configuration: "#{configurationType}",
      xcargs: "#{xcargs}",
      toolchain: "#{toolchain}",
      skip_profile_detection: true,
      export_options: {
        compileBitcode: false,
        provisioningProfiles: {
         ... ...
        }
      },
      output_directory: "#{exportDir}",
    )
  end

Complete output when running fastlane, including the stack trace and command used
** ARCHIVE FAILED **
[09:48:17]: Exit status: 65
[09:48:17]:
[09:48:17]: Maybe the error shown is caused by using the wrong version of Xcode
[09:48:17]: Found multiple versions of Xcode in '/Applications/'
[09:48:17]: Make sure you selected the right version for your project
[09:48:17]: This build process was executed using '/Applications/Xcode.app'
[09:48:17]: If you want to update your Xcode path, either
[09:48:17]:
[09:48:17]: - Specify the Xcode version in your Fastfile
[09:48:17]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[09:48:17]:
[09:48:17]: - Specify an absolute path to your Xcode installation in your Fastfile
[09:48:17]: ▸ xcode_select "/Applications/Xcode8.app"
[09:48:17]:
[09:48:17]: - Manually update the path using
[09:48:17]: ▸ sudo xcode-select -s /Applications/Xcode.app
+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.210.1                 |
| export_method | development             |
| sdk           | iPhoneOS16.0.sdk        |
+---------------+-------------------------+
[09:48:17]: ⬆  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
[09:48:17]: 📋  For the complete and more detailed error log, check the full log at:
[09:48:17]: 📋  /Users/xxx/Library/Logs/gym/xxxx-xxxxx.log
[09:48:17]:
[09:48:17]: Your `export_method` in gym is defined as `development`
[09:48:17]: which might cause problems when signing your application
[09:48:17]: Are you sure want to build and export for development?
[09:48:17]: Please make sure to define the correct export methods when calling
[09:48:17]: gym in your Fastfile or from the command line
[09:48:17]:
[09:48:17]:
[09:48:17]: Looks like fastlane ran into a build/archive error with your project
[09:48:17]: It's hard to tell what's causing the error, so we wrote some guides on how
[09:48:17]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[09:48:17]: Before submitting an issue on GitHub, please follow the guide above and make
[09:48:17]: sure your project is set up correctly.
[09:48:17]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
[09:48:17]: the full commands printed out in yellow in the above log.
[09:48:17]: Make sure to inspect the output above, as usually you'll find more error information there

Environment
✅ fastlane environment ✅

### Stack

| Key                         | Value                                       |
| --------------------------- | ------------------------------------------- |
| OS                          | 13.0                                        |
| Ruby                        | 3.0.0                                       |
| Bundler?                    | false                                       |
| Git                         | git version 2.37.0 (Apple Git-136)          |
| Installation Source         | /usr/local/bin/fastlane                     |
| Host                        | macOS 13.0 (22A380)                         |
| Ruby Lib Dir                | ~/.rvm/rubies/ruby-3.0.0/lib                |
| OpenSSL Version             | OpenSSL 1.1.1q  5 Jul 2022                  |
| Is contained                | false                                       |
| Is homebrew                 | false                                       |
| Is installed via Fabric.app | false                                       |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version               | 14.0.1                                      |
| Swift Version               | 5.7                                         |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | zh_CN.UTF-8 | ✅ |
| LC_ALL   |             |   |
| LANGUAGE |             |   |

### fastlane gems

| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.210.1 | ✅ Up-To-Date  |

### Loaded fastlane plugins:

| Plugin                | Version | Update-Status |
| --------------------- | ------- | ------------- |
| fastlane-plugin-pgyer | 0.2.4   | ✅ Up-To-Date  |
| fastlane-plugin-badge | 1.5.0   | ✅ Up-To-Date  |

Loaded gems

| Gem                             | Version      |
| ------------------------------- | ------------ |
| did_you_mean                    | 1.5.0        |
| atomos                          | 0.1.3        |
| CFPropertyList                  | 3.0.5        |
| claide                          | 1.1.0        |
| colored2                        | 3.1.2        |
| nanaimo                         | 0.3.0        |
| xcodeproj                       | 1.22.0       |
| rouge                           | 2.0.7        |
| xcpretty                        | 0.3.0        |
| terminal-notifier               | 2.0.0        |
| unicode-display_width           | 1.8.0        |
| terminal-table                  | 1.8.0        |
| plist                           | 3.6.0        |
| public_suffix                   | 4.0.7        |
| addressable                     | 2.8.1        |
| multipart-post                  | 2.0.0        |
| word_wrap                       | 1.0.0        |
| optparse                        | 0.1.1        |
| tty-screen                      | 0.8.1        |
| tty-cursor                      | 0.7.1        |
| tty-spinner                     | 0.9.3        |
| artifactory                     | 3.0.15       |
| babosa                          | 1.0.4        |
| colored                         | 1.2          |
| highline                        | 2.0.3        |
| commander                       | 4.6.0        |
| excon                           | 0.93.1       |
| faraday-em_http                 | 1.0.0        |
| faraday-em_synchrony            | 1.0.0        |
| faraday-excon                   | 1.1.0        |
| faraday-httpclient              | 1.0.1        |
| faraday-multipart               | 1.0.4        |
| faraday-net_http                | 1.0.1        |
| faraday-net_http_persistent     | 1.2.0        |
| faraday-patron                  | 1.0.0        |
| faraday-rack                    | 1.0.0        |
| faraday-retry                   | 1.0.3        |
| ruby2_keywords                  | 0.0.5        |
| faraday                         | 1.10.2       |
| unf_ext                         | <IP_ADDRESS>      |
| unf                             | 0.1.4        |
| domain_name                     | 0.5.20190701 |
| http-cookie                     | 1.0.5        |
| faraday-cookie_jar              | 0.0.7        |
| faraday_middleware              | 1.2.0        |
| fastimage                       | 2.2.6        |
| gh_inspector                    | 1.1.3        |
| mini_magick                     | 4.11.0       |
| naturally                       | 2.2.1        |
| rubyzip                         | 2.3.2        |
| security                        | 0.1.3        |
| xcpretty-travis-formatter       | 1.0.1        |
| dotenv                          | 2.8.1        |
| bundler                         | 2.2.3        |
| simctl                          | 1.6.8        |
| jwt                             | 2.5.0        |
| uber                            | 0.1.0        |
| declarative                     | 0.0.20       |
| trailblazer-option              | 0.1.2        |
| representable                   | 3.2.0        |
| retriable                       | 3.1.2        |
| mini_mime                       | 1.1.2        |
| memoist                         | 0.16.2       |
| multi_json                      | 1.15.0       |
| os                              | 1.1.4        |
| signet                          | 0.17.0       |
| googleauth                      | 1.3.0        |
| httpclient                      | 2.8.3        |
| webrick                         | 1.7.0        |
| google-apis-core                | 0.9.1        |
| google-apis-playcustomapp_v1    | 0.12.0       |
| google-apis-androidpublisher_v3 | 0.29.0       |
| google-cloud-env                | 1.6.0        |
| google-cloud-errors             | 1.3.0        |
| google-cloud-core               | 1.6.0        |
| google-apis-iamcredentials_v1   | 0.15.0       |
| google-apis-storage_v1          | 0.19.0       |
| digest-crc                      | 0.6.4        |
| google-cloud-storage            | 1.43.0       |
| emoji_regex                     | 3.2.3        |
| jmespath                        | 1.6.1        |
| aws-partitions                  | 1.651.0      |
| aws-eventstream                 | 1.2.0        |
| aws-sigv4                       | 1.5.2        |
| aws-sdk-core                    | 3.166.0      |
| aws-sdk-kms                     | 1.59.0       |
| aws-sdk-s3                      | 1.117.1      |
| tsort                           | 0.1.0        |
| set                             | 1.0.1        |
| uri                             | 0.10.1       |
| rexml                           | 3.2.5        |
| json                            | 2.6.2        |
| rake                            | 13.0.6       |
| forwardable                     | 1.3.2        |
| logger                          | 1.4.3        |
| pathname                        | 0.1.0        |
| shellwords                      | 0.1.0        |
| cgi                             | 0.2.0        |
| date                            | 3.1.0        |
| timeout                         | 0.1.1        |
| stringio                        | 3.0.0        |
| securerandom                    | 0.1.0        |
| openssl                         | 2.2.0        |
| io-nonblock                     | 0.1.0        |
| ipaddr                          | 1.2.2        |
| io-wait                         | 0.1.0        |
| zlib                            | 1.1.0        |
| resolv                          | 0.2.0        |
| digest                          | 3.0.0        |
| time                            | 0.1.0        |
| open-uri                        | 0.1.0        |
| mutex_m                         | 0.1.1        |
| net-protocol                    | 0.1.0        |
| net-smtp                        | 0.2.1        |
| ostruct                         | 0.3.1        |
| english                         | 0.7.1        |
| erb                             | 2.2.0        |
| strscan                         | 3.0.0        |
| abbrev                          | 0.1.0        |
| io-console                      | 0.5.6        |
| tempfile                        | 0.1.1        |
| delegate                        | 0.2.0        |
| fileutils                       | 1.5.0        |
| tmpdir                          | 0.1.1        |
| base64                          | 0.1.0        |
| singleton                       | 0.1.1        |
| open3                           | 0.1.1        |
| nkf                             | 0.1.0        |
| prettyprint                     | 0.1.0        |
| pp                              | 0.1.0        |
| find                            | 0.1.0        |
| yaml                            | 0.1.1        |
| psych                           | 3.3.0        |
| fastlane-plugin-pgyer           | 0.2.4        |
| badge                           | 0.13.0       |
| fastlane-plugin-badge           | 1.5.0        |

*generated on:* **2022-11-02**

I encounter this problem after I upgrade my mac os to Ventura 13.0. But It works with Xcode14.0.1 on macOS 12.6.1.
It works for about a few minutes on my project till it fails. I can't find any useful error message that told me where is the error. It seems that gym fails before the 'code sign' action I suppose.

@Daemonson as written in the logs - seems that you have multiple versions of Xcode on your machine and for fastlane it's not clear which one should be used. Can this be the case? Also plenty of other hints in the logs have you checked all the warnings?

@fbaumgart  I only have one Xcode on my mac. This is not the case. As I described above, it works before I upgrade my mac os to Ventura 13.0. And my colleagues also encounter the same case.

Having same issue here after upgrade fastlane to 2.210.1, but I could finally work by export path of my ruby and run bundle update, still don't know why. However, it still could not build success in my CircleCI with xcode: 13.4.1 when build a development ipa by showing:
error: No profile for team '${team_id}' matching 'match AppStore ${app_identifier}' found: Xcode couldn't find any provisioning profiles matching '${team_id}/match AppStore ${app_identifier}'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the Signing & Capabilities tab of the target editor. (in target 'Runner' from project 'Runner').
And my fastlane is:
platform :ios do
  before_all do
    setup_circle_ci
  end

  desc "Run iOS debug build"
  lane :debug_build do
    match(
      type: "development",
      readonly: true
    )
    Dir.chdir "../.." do
      sh("flutter", "packages", "get")
      sh("flutter", "clean")
      sh("flutter", "build", "ios", "--debug")
    end
  end

  desc "Build a new iOS debug App"
  lane :dev_deploy do
    debug_build
    commit = last_git_commit
    short_hash = commit[:abbreviated_commit_hash]
    current_time = Time.new.strftime("%Y%m%d")
    file_name = "#{current_time}_#{short_hash}"
    build_ios_app(
      export_method: 'development',
      output_name: "#{file_name}.ipa",
    )
  end
end

I'm pretty sure match download development cert and profile for me also install to machine. Having this issue for days and still don't know why. Any idea?

It seems like some message mentioned on issue #20784 is useful for you.

It seems like some message mentioned on issue #20784 is useful for you.

I suppose something went wrong when it executed the code sign action. Maybe permission error on macOS 13.0 or something else.

@Daemonson Tks, I will dig in this problem by the issue you mention, but it still have problem when use xcode: 14.x on CircleCI, I could only local build development recently.

@Daemonson Tks, I will dig in this problem by the issue you mention, but it still have problem when use xcode: 14.x on CircleCI, I could only local build development recently.

After some info mention before, I try to add match appstore before match development, then CircleCI is success! It's because we need to install all provision profile and certs in build machine and let the actual need profile at the below or it will have error? Not sure the conclusion is correct or not, but it seems total different from others samples and notes on the internet.

After some info mention above, I try to add match appstore before match development, then CircleCI is success! It's because we need to install all provision profile and certs in build machine and let the actual need profile at the below or it will have error? Not sure the conclusion is correct or not, but it seems total different from others samples and notes on the internet.
platform :ios do
  before_all do
    setup_circle_ci
  end

  desc "Run iOS debug build"
  lane :debug_build do
    match(
      type: "appstore",
      readonly: true
    )
    match(
      type: "development",
      readonly: true
    )
    Dir.chdir "../.." do
      sh("flutter", "packages", "get")
      sh("flutter", "clean")
      sh("flutter", "build", "ios", "--debug")
    end
  end

  desc "Build a new iOS debug App"
  lane :dev_deploy do
    debug_build
    commit = last_git_commit
    short_hash = commit[:abbreviated_commit_hash]
    current_time = Time.new.strftime("%Y%m%d")
    file_name = "#{current_time}_#{short_hash}"
    build_ios_app(
      export_method: 'development',
      output_name: "#{file_name}.ipa",
    )
  end
end

Thanks for your information. I found that it works when I build with ad-hoc or appstore environment. It only failed with the development environment. I don't use match action in our project. I'll continue to dig into what causes this error.

Maybe something changed about the toolchain by the system on Ventura 13.0. I build success for all export_method with another toolchain, not the system toolchain com.apple.dt.toolchain.

This issue might be the reason why it fails. https://github.com/apple/swift/issues/61104

Finally, I've resolved this error by changing some SDKs from framework to xcframework as mentioned below this issue https://github.com/apple/swift/issues/61104.
Those SDKs showed error info with SwiftDriver compilation error: com.apple.xcode.tools.swift.compiler is not absolute in the build log.
If the SDK you linked in your project doesn't offer xcframework. You can use the framework file to generate the xcframework file with lipo and xcodebuild -create-xcframework  tools.

@Daemonson I'm using Flutter right now so I'm not sure the solution of flutter environment. So I need to have additional job setting before flutter build ios --debug? Or this is just gym's issue?

@Daemonson I'm using Flutter right now so I'm not sure the solution of flutter environment. So I need to have additional job setting before flutter build ios --debug? Or this is just gym's issue?

Sorry, I don't use Flutter in my project. I'm not sure if it's the gyms issue.  I can only make sure that if you have this error message SwiftDriver compilation error: com.apple.xcode.tools.swift.compiler in the build log as shown below image, the gym may output an Archive Failed message and exit.

This is the case that I encountered. And I can fix it with the solution I mentioned above.

I was also facing the same Exit status: 65 problem with Bitrise's "Xcode 14.1.x, on macOS Monterey 12.5" stack.
However, I was able to work around it by specifying "CODE_SIGN_STYLE='Manual'" in the xcargs of the gym.

any update? same issue

+1 monterey 12.6.1 keep fail too on Bitrise "Xcode 14.1.x, on macOS Monterey 12.5" stack

anyone can help? my company is waiting my build at least 1 week. Thank you so much.

I was getting the archive failed exit code 65 with no helpful logging after updating to xcode 14 on CI.
It was a code signing issue. I needed to change my Fastfile's gym command to include codesigning_identity and xcargs with CODE_SIGN_STYLE as Manual along with specifying the DEVELOPMENT_TEAM and PROVISIONING_PROFILE_SPECIFIER.

Hello, could you please expand what should I do?
Currently I have script in ruby
                fastlane(Fastlane::Actions::GymAction, {                     buildlog_path: "#{ENV["BITRISE_DEPLOY_DIR"]}",                     scheme: app.schemeNameResolver.schemeName(variant: variant, production: true),                     output_name: app.name,                     destination: 'generic/platform=iOS',                     export_options: {                         compileBitcode: false                     },                     skip_profile_detection: true                 })
It is working allright for Xcode 13.4 on bitrise. But same build is crashing (Exit status: 65) when I try increase stack to any version of Xcode 14.
Same fastlane lane working OK locally.

@SwiftyMike are you using any swift packages that include bundled resources? There is an issue noted issue with the Xcode command line utilities attempting to sign resource bundles when it shouldn't: https://forums.swift.org/t/xcode-14-beta-code-signing-issues-when-spm-targets-include-resources/59685
Several other related issues:
https://github.com/fastlane/fastlane/issues/20701, https://github.com/fastlane/fastlane/discussions/20788, https://github.com/fastlane/fastlane/issues/20789, https://github.com/fastlane/fastlane/issues/20800, https://github.com/fastlane/fastlane/issues/20804, https://github.com/fastlane/fastlane/issues/20825

i confirm, this solution worked for me.
You need to add some xcargs to the Gym command (either in your Gymfile, or in the gym() command in your lane).
Here's what I added:
 gym(     [...],     xcargs: "CODE_SIGN_STYLE=Manual DEVELOPMENT_TEAM=XXX" )

Unfortunately didn't work for me :(

Hi,
Not working too with Xcode 14.2, any update?
Thanks

Hi,
any update on this problem?
Thanks.

I <3 U @tjbenton

Not working on Xcode 14.3. Facing same issue.

I have the same issue, I cannot build ipa via gym
xCode Version 14.3 (14E222b)
MacOS Ventura 13.3
latest version of pods, ruby and fastlane

This one might help
https://stackoverflow.com/a/75979879/1314468

I cannot build ipa via gym but able to build via XCODE
xCode Version 14.2
MacOS Ventura 13.3
latest version of pods, ruby and fastlane

Hi,
Could someone from Fastlane team give us any updates?
I try all suggested workarounds without success from 6 months on my CI... It is really a major problem to me for now on 🙏
My last error trace
[10:56:40]: All required keys, certificates and provisioning profiles are installed 🙌
[10:56:40]: Setting Provisioning Profile type to 'app-store'
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
[10:56:40]: -----------------
[10:56:40]: --- Step: gym ---
[10:56:40]: -----------------
[10:56:40]: Skipped Swift Package Manager dependencies resolution.
[10:56:40]: $ xcodebuild -showBuildSettings -workspace Liberty\ Rider.xcworkspace -scheme Release -configuration Release
[10:56:43]: Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
[10:56:49]: Command timed out after 6 seconds on try 2 of 4, trying again with a 12 second timeout...
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:63FF07F4-83BA-48CC-A7AB-6F6D7770DE1C, OS:15.5, name:iPhone 13 }
{ platform:iOS Simulator, id:2BF445C5-B223-4C5B-ABFB-B343FA686C00, OS:15.5, name:iPhone 13 Pro }
{ platform:iOS Simulator, id:8A4CFB1C-484A-459E-A08F-AA80A1BE72D8, OS:15.5, name:iPhone 13 Pro Max }
{ platform:iOS Simulator, id:9EF015E0-26E3-4CF0-8338-F4EB8E83C0BE, OS:15.5, name:iPhone 13 mini }
{ platform:iOS Simulator, id:56AE6AAE-7385-4453-AD41-112C369322A6, OS:16.2, name:iPhone 14 }
{ platform:iOS Simulator, id:21452B8C-7170-4BDF-ABDC-CC69123BC461, OS:16.2, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:309CE2B6-45C8-4FE5-9B43-87A0A93C72E1, OS:16.2, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:AFF1A48C-D8FA-4F9D-84F0-382F2FB9F1B0, OS:16.2, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:27B987A2-631B-494C-B82B-9250DAB548B4, OS:15.5, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:3AEDBC8B-C49E-48B4-9854-8096FA7D5595, OS:16.2, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:CF49EB86-AA50-45D7-8D46-D9DC3AE53211, OS:15.5, name:iPod touch (7th generation) }
{ platform:iOS Simulator, id:89572413-4FB7-4048-9205-8F533B1DC2D0, OS:15.5, name:iPad (9th generation) }
{ platform:iOS Simulator, id:BE3B5223-D9AF-412F-9A73-95F6CA5B5198, OS:16.2, name:iPad (10th generation) }
{ platform:iOS Simulator, id:81A624CA-10EF-4E7D-AF81-558CB315087F, OS:15.5, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:1096D066-4531-4174-9AF4-99AF5B10F814, OS:16.2, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:F5348267-FAD8-40E8-8D12-DE13971B63D6, OS:15.5, name:iPad Pro (9.7-inch) }
{ platform:iOS Simulator, id:69A11FF3-D102-48B1-9A95-2CF77F8F69AE, OS:15.5, name:iPad Pro (11-inch) (3rd generation) }
{ platform:iOS Simulator, id:3D01F8CE-F519-4295-83E8-D690358D829B, OS:16.2, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:BB354921-4E7B-4691-82FD-491C8EDE4A4D, OS:15.5, name:iPad Pro (12.9-inch) (5th generation) }
{ platform:iOS Simulator, id:AAECFEEF-83B9-4964-896F-9DFA5D15647D, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:909D94E5-18C7-44FC-A68B-8C1543F2FFD8, OS:15.5, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:362D1B0F-D1DF-4337-9CC5-96570437E88B, OS:16.2, name:iPad mini (6th generation) }
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:63FF07F4-83BA-48CC-A7AB-6F6D7770DE1C, OS:15.5, name:iPhone 13 }
{ platform:iOS Simulator, id:2BF445C5-B223-4C5B-ABFB-B343FA686C00, OS:15.5, name:iPhone 13 Pro }
{ platform:iOS Simulator, id:8A4CFB1C-484A-459E-A08F-AA80A1BE72D8, OS:15.5, name:iPhone 13 Pro Max }
{ platform:iOS Simulator, id:9EF015E0-26E3-4CF0-8338-F4EB8E83C0BE, OS:15.5, name:iPhone 13 mini }
{ platform:iOS Simulator, id:56AE6AAE-7385-4453-AD41-112C369322A6, OS:16.2, name:iPhone 14 }
{ platform:iOS Simulator, id:21452B8C-7170-4BDF-ABDC-CC69123BC461, OS:16.2, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:309CE2B6-45C8-4FE5-9B43-87A0A93C72E1, OS:16.2, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:AFF1A48C-D8FA-4F9D-84F0-382F2FB9F1B0, OS:16.2, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:27B987A2-631B-494C-B82B-9250DAB548B4, OS:15.5, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:3AEDBC8B-C49E-48B4-9854-8096FA7D5595, OS:16.2, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:CF49EB86-AA50-45D7-8D46-D9DC3AE53211, OS:15.5, name:iPod touch (7th generation) }
{ platform:iOS Simulator, id:89572413-4FB7-4048-9205-8F533B1DC2D0, OS:15.5, name:iPad (9th generation) }
{ platform:iOS Simulator, id:BE3B5223-D9AF-412F-9A73-95F6CA5B5198, OS:16.2, name:iPad (10th generation) }
{ platform:iOS Simulator, id:81A624CA-10EF-4E7D-AF81-558CB315087F, OS:15.5, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:1096D066-4531-4174-9AF4-99AF5B10F814, OS:16.2, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:F5348267-FAD8-40E8-8D12-DE13971B63D6, OS:15.5, name:iPad Pro (9.7-inch) }
{ platform:iOS Simulator, id:69A11FF3-D102-48B1-9A95-2CF77F8F69AE, OS:15.5, name:iPad Pro (11-inch) (3rd generation) }
{ platform:iOS Simulator, id:3D01F8CE-F519-4295-83E8-D690358D829B, OS:16.2, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:BB354921-4E7B-4691-82FD-491C8EDE4A4D, OS:15.5, name:iPad Pro (12.9-inch) (5th generation) }
{ platform:iOS Simulator, id:AAECFEEF-83B9-4964-896F-9DFA5D15647D, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:909D94E5-18C7-44FC-A68B-8C1543F2FFD8, OS:15.5, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:362D1B0F-D1DF-4337-9CC5-96570437E88B, OS:16.2, name:iPad mini (6th generation) }
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:63FF07F4-83BA-48CC-A7AB-6F6D7770DE1C, OS:15.5, name:iPhone 13 }
{ platform:iOS Simulator, id:2BF445C5-B223-4C5B-ABFB-B343FA686C00, OS:15.5, name:iPhone 13 Pro }
{ platform:iOS Simulator, id:8A4CFB1C-484A-459E-A08F-AA80A1BE72D8, OS:15.5, name:iPhone 13 Pro Max }
{ platform:iOS Simulator, id:9EF015E0-26E3-4CF0-8338-F4EB8E83C0BE, OS:15.5, name:iPhone 13 mini }
{ platform:iOS Simulator, id:56AE6AAE-7385-4453-AD41-112C369322A6, OS:16.2, name:iPhone 14 }
{ platform:iOS Simulator, id:21452B8C-7170-4BDF-ABDC-CC69123BC461, OS:16.2, name:iPhone 14 Plus }
{ platform:iOS Simulator, id:309CE2B6-45C8-4FE5-9B43-87A0A93C72E1, OS:16.2, name:iPhone 14 Pro }
{ platform:iOS Simulator, id:AFF1A48C-D8FA-4F9D-84F0-382F2FB9F1B0, OS:16.2, name:iPhone 14 Pro Max }
{ platform:iOS Simulator, id:27B987A2-631B-494C-B82B-9250DAB548B4, OS:15.5, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:3AEDBC8B-C49E-48B4-9854-8096FA7D5595, OS:16.2, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:CF49EB86-AA50-45D7-8D46-D9DC3AE53211, OS:15.5, name:iPod touch (7th generation) }
{ platform:iOS Simulator, id:89572413-4FB7-4048-9205-8F533B1DC2D0, OS:15.5, name:iPad (9th generation) }
{ platform:iOS Simulator, id:BE3B5223-D9AF-412F-9A73-95F6CA5B5198, OS:16.2, name:iPad (10th generation) }
{ platform:iOS Simulator, id:81A624CA-10EF-4E7D-AF81-558CB315087F, OS:15.5, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:1096D066-4531-4174-9AF4-99AF5B10F814, OS:16.2, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:F5348267-FAD8-40E8-8D12-DE13971B63D6, OS:15.5, name:iPad Pro (9.7-inch) }
{ platform:iOS Simulator, id:69A11FF3-D102-48B1-9A95-2CF77F8F69AE, OS:15.5, name:iPad Pro (11-inch) (3rd generation) }
{ platform:iOS Simulator, id:3D01F8CE-F519-4295-83E8-D690358D829B, OS:16.2, name:iPad Pro (11-inch) (4th generation) }
{ platform:iOS Simulator, id:BB354921-4E7B-4691-82FD-491C8EDE4A4D, OS:15.5, name:iPad Pro (12.9-inch) (5th generation) }
{ platform:iOS Simulator, id:AAECFEEF-83B9-4964-896F-9DFA5D15647D, OS:16.2, name:iPad Pro (12.9-inch) (6th generation) }
{ platform:iOS Simulator, id:909D94E5-18C7-44FC-A68B-8C1543F2FFD8, OS:15.5, name:iPad mini (6th generation) }
{ platform:iOS Simulator, id:362D1B0F-D1DF-4337-9CC5-96570437E88B, OS:16.2, name:iPad mini (6th generation) }
2023-05-18 10:56:54.033 xcodebuild[7802:21124] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition
2023-05-18 10:56:54.034 xcodebuild[7816:21119] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition
2023-05-18 10:56:54.034 xcodebuild[7826:21127] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition
[10:56:54]: Detected provisioning profile mapping: {:"com.xxx"=>"match AppStore com.xxx", :"com.xxx"=>"match AppStore com.xxx.watchkitapp", :"com.xxx"=>"match AppStore com.xxx.watchkitextension"}

+---------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+
|                                                                             Summary for gym 2.212.2                                                                              |
+---------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+
| workspace                                                                                | Liberty Rider.xcworkspace                                                    |
| scheme                                                                                | Release                                                                      |
| configuration                                                                                | Release                                                                      |
| export_method                                                                                | app-store                                                                    |
| include_bitcode                                                                                | false                                                                        |
| include_symbols                                                                                | true                                                                         |
| output_directory                                                                                | ./artifacts/                                                                 |
| output_name                                                                                | LibertyRider                                                                 |
| skip_package_dependencies_resolution                                                              | true                                                                         |
| xcargs                                                                                | -UseModernBuildSystem=YES CODE_SIGN_STYLE=Manual DEVELOPMENT_TEAM=XXXXXXXXXX |
| export_options.provisioningProfiles.com.xxx                               | match AppStore com.xxx                              |
| export_options.provisioningProfiles.com.xxx.watchkitapp                   | match AppStore com.xxx                  |
| export_options.provisioningProfiles.com.xxx.watchkitextension | match AppStore com.xxx |
| clean                                                                                | false                                                                        |
| silent                                                                                | false                                                                        |
| skip_package_ipa                                                                                | false                                                                        |
| skip_package_pkg                                                                                | false                                                                        |
| build_path                                                                                | /Users/distiller/Library/Developer/Xcode/Archives/2023-05-18                 |
| result_bundle                                                                                | false                                                                        |
| buildlog_path                                                                                | ~/Library/Logs/gym                                                           |
| destination                                                                                | generic/platform=iOS                                                         |
| xcodebuild_formatter                                                                              | xcpretty                                                                     |
| build_timing_summary                                                                              | false                                                                        |
| skip_profile_detection                                                                            | false                                                                        |
| xcodebuild_command                                                                                | xcodebuild                                                                   |
| disable_package_automatic_updates                                                                 | false                                                                        |
| use_system_scm                                                                                | false                                                                        |
| xcode_path                                                                                | /Applications/Xcode-14.2.app                                                 |
+---------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+

[10:56:54]: $ set -o pipefail && xcodebuild -workspace Liberty\ Rider.xcworkspace -scheme Release -configuration Release -destination 'generic/platform=iOS' -archivePath /Users/distiller/Library/Developer/Xcode/Archives/2023-05-18/LibertyRider\ 2023-05-18\ 10.56.54.xcarchive -UseModernBuildSystem=YES CODE_SIGN_STYLE=Manual DEVELOPMENT_TEAM=XXXXXXXXXX archive | tee /Users/distiller/Library/Logs/gym/Liberty\ Rider-Release.log | xcpretty
[10:57:04]: ▸     no rule to process file '/Users/distiller/project/Pods/lottie-ios/Sources/Private/Model/DotLottie/ZipFoundation/README.md' of type 'net.daringfireball.markdown' for architecture 'arm64' (in target 'lottie-ios' from project 'Pods')
[10:57:04]: ▸ ** ARCHIVE FAILED **
    no rule to process file '/Users/distiller/project/Pods/lottie-ios/Sources/Private/Model/DotLottie/ZipFoundation/README.md' of type 'net.daringfireball.markdown' for architecture 'arm64' (in target 'lottie-ios' from project 'Pods')
** ARCHIVE FAILED **
[10:57:04]: Exit status: 65
[10:57:05]:
[10:57:05]: Maybe the error shown is caused by using the wrong version of Xcode
[10:57:05]: Found multiple versions of Xcode in '/Applications/'
[10:57:05]: Make sure you selected the right version for your project
[10:57:05]: This build process was executed using '/Applications/Xcode-14.2.app'
[10:57:05]: If you want to update your Xcode path, either
[10:57:05]:
[10:57:05]: - Specify the Xcode version in your Fastfile
[10:57:05]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[10:57:05]:
[10:57:05]: - Specify an absolute path to your Xcode installation in your Fastfile
[10:57:05]: ▸ xcode_select "/Applications/Xcode8.app"
[10:57:05]:
[10:57:05]: - Manually update the path using
[10:57:05]: ▸ sudo xcode-select -s /Applications/Xcode.app
[10:57:05]:

+---------------+------------------------------+
|              Build environment               |
+---------------+------------------------------+
| xcode_path    | /Applications/Xcode-14.2.app |
| gym_version   | 2.212.2                      |
| export_method | app-store                    |
| sdk           | iPhoneOS16.2.sdk             |
+---------------+------------------------------+

[10:57:05]: ▸ note: Run script build phase 'Clear git hash' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Liberty Rider' from project 'Liberty Rider')
[10:57:05]: ▸ note: Run script build phase 'Crashlytics' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Liberty Rider' from project 'Liberty Rider')
[10:57:05]: ▸ /Users/distiller/project/Liberty Rider.xcodeproj: error: No profile for team 'XXXXXXXXXX' matching 'match Development com.xxx.watchkitapp.watchkitextension' found: Xcode couldn't find any provisioning profiles matching 'XXXXXXXXXX/match Development com.xxx.watchkitextension'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the Signing & Capabilities tab of the target editor. (in target 'LRWatch Extension' from project 'Liberty Rider')
[10:57:05]: ▸ /Users/distiller/project/Liberty Rider.xcodeproj: error: No profile for team 'XXXXXXXXXX' matching 'match Development com.xxx.watchkitapp' found: Xcode couldn't find any provisioning profiles matching 'XXXXXXXXXX/match Development com.xxx'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the Signing & Capabilities tab of the target editor. (in target 'LRWatch' from project 'Liberty Rider')
[10:57:05]: ▸ warning: no rule to process file '/Users/distiller/project/Pods/lottie-ios/Sources/Private/Model/DotLottie/ZipFoundation/README.md' of type 'net.daringfireball.markdown' for architecture 'arm64' (in target 'lottie-ios' from project 'Pods')
[10:57:05]:
[10:57:05]: ⬆  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
[10:57:05]: 📋  For the complete and more detailed error log, check the full log at:
[10:57:05]: 📋  /Users/distiller/Library/Logs/gym/Liberty Rider-Release.log
[10:57:05]:
[10:57:05]: Looks like fastlane ran into a build/archive error with your project
[10:57:05]: It's hard to tell what's causing the error, so we wrote some guides on how
[10:57:05]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[10:57:05]: Before submitting an issue on GitHub, please follow the guide above and make
[10:57:05]: sure your project is set up correctly.
[10:57:05]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
[10:57:05]: the full commands printed out in yellow in the above log.
[10:57:05]: Make sure to inspect the output above, as usually you'll find more error information there
[10:57:05]:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
[10:57:05]: -------------------
[10:57:05]: --- Step: slack ---
[10:57:05]: -------------------
[10:57:05]: Successfully sent Slack notification
+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                                Lane Context                                                                                |
+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                                                                |
| PLATFORM_NAME                      | ios                                                                                |
| LANE_NAME                          | ios deployTestFlight                                                                                |
| KEYCHAIN_PATH                      | ~/Library/Keychains/fastlane_tmp_keychain                                                                                |
| ORIGINAL_DEFAULT_KEYCHAIN          | "/Users/distiller/Library/Keychains/login.keychain-db"                                                                                |
| SIGH_PROFILE_TYPE                  | app-store                                                                                |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.xxx"=>"match AppStore com.xxx", "com.xxx"=>"match AppStore com.xxx", "com.xxx"=>"match AppStore com.xxx"} |
+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
[10:57:05]: Error building the application - see the log above

+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
| 2    | setup_circle_ci  | 0           |
| 3    | match            | 2           |
| 💥   | gym              | 24          |
| 5    | slack            | 0           |
+------+------------------+-------------+

[10:57:05]: fastlane finished with errors

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

Exited with code exit status 1
CircleCI received exit code 1

Same here! Any update....

I have read in several threads about the same issue, corresponding with rsync (since the copy can't find the files I guess) because I am running into the same issue.
Therefore I can confirm that Xcode 14.3.1 does not work with fastlane

This one might help
https://stackoverflow.com/a/75979879/1314468

This worked out fine for me. Adding the -f to the framework pods did the trick! Thank you very much for sharing.

Hi @IJustDev,
It is not an option to me because my relative Pods.xcodeproj is not versioned :/
My CI recreated it at each job, basing on Podfile and Podfile.lock files (versioned) and using pod caches...

Hi,
Always the same error with Xcode 15.1.0 beta 3 on CircleCI...

I have the same issue trying Unity Build Automation for an ios deploy. Is this in general just what happens when fastlane updates and xcode isn't keeping up?
I can choose between xcode 15.0, 15.1, or 15.2. Do I need a specific fastlane version for any of them?

Hello @Narayane Did you manage to fix?

Hi @barcellosfilippo
I did not, my CI is still broken for the relative lane... :|
Hopefully, it works locally.


HDDS-10437. Rename method to getContainersPendingReplication

What changes were proposed in this pull request?
DatanodeAdminMonitor#getContainersReplicatedOnNode() is renamed to something more appropriate i.e., getContainersPendingReplication() as the method only returns a list of under-replicated and unclosed containers, and not all containers like the current name would suggest. Some other minor improvements are also done for the output of ozone admin datanode status decommission command to make output match up with the design doc attached the the parent Jira HDDS-9324
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10437
How was this patch tested?
As it is minor code refactoring, existing tests cover the cases.

LGTM +1