[5pt] Incorrect geometries in CatFIM merged layer

Additionally, there appears to be another issue with some sites/thresholds not appearing in correct location/having incorrect (and incomplete) geometry when compared to the grids. For example, id8s2 -record threshold-huc 10160009 and sfrw4-record-threshold-14040107.
The CatFIM process was run 2 times and the same issue remained.

@TrevorGrout-NOAA @BrianAvant-NOAA Is this still an issue?


remove typing_extension dependency

Reference Issues/PRs

What does this implement/fix? Explain your changes
Remove typing_extension as a dependency since we now only support Python >=3.8 and Literal is included in typing there. Use try catch block to still use typing_extension if user has Python3.7 and manually installs it
What testing did you do to verify the changes in this PR?
Ran pytests.
Pull Request Checklist

[x] Added a note about the modification or contribution to the ./CHANGELOG.md file (if applicable)
[ ] Added appropriate unit test functions in the ./graphein/tests/* directories (if applicable)
[ ] Modify documentation in the corresponding Jupyter Notebook under ./notebooks/ (if applicable)
[ ] Ran python -m py.test tests/ and make sure that all unit tests pass (for small modifications, it might be sufficient to only run the specific test file, e.g., python -m py.test tests/protein/test_graphs.py)
[ ] Checked for style issues by running black . and isort .

Could you run black just for the sake of the formatting check?

done


 See: https://github.com/golang/go/blob/4847c47cb8a93b56e1df8c249700e25f527d4ba3/src/runtime/proc.go#L3669-L3683

syscall.SYS_EXIT is nice but does not exist on Windows.

Due to the comments above, there is nothing to fix. Close

thanks for you help, I saw the comments.


docs: Video Object Detection & Tracking template + docs

@niklub @makseq @deppp @nicholasrq this PR is ready for your review/approval.

@nicholasrq @makseq could you review/approve this PR for tomorrow's release.

https://heartex.slack.com/archives/C01HGFXA7KR/p1664212720200169


[BUG] registerProvider doesn't respect Request scope if provider token is a string

Problem description
I'm attempting to restructure an app to allow dynamic selection of DB connection based on request domain (for a multi-tenant SaaS project.  My initial thought was to use the "request" scope feature of the DI system.   While experimenting with registering dependencies, I found some odd behavior.  To demonstrate this, I created a controller  with two dependencies:  dummy and CONNECTION.  Dummy is a class which is also request scoped, and CONNECTION is a constant which is a stand-in for my DB connection.
Expected behavior:
Both factory functions for Dummy and CONNECTION are invoked on every request, and not before during app startup.
Actual behavior:
The factory function for CONNECTION is invoked only once at app startup, not at the time of request.  Dummy's factory function is invoked per-request.
Example
// ================ services.ts =======================
// for registering 3rd party deps and some stuff that's not easily made into a class

export const CONNECTION = 'tenant_db_connection';

registerProvider({
    provide: CONNECTION,
    scope: ProviderScope.REQUEST,
    type: ProviderType.FACTORY,
    useFactory () {
        console.log('creating connection');
        return 'garbage';
    },
});

registerProvider({
    provide: Dummy,
    scope: ProviderScope.REQUEST,
    useFactory() {
        console.log('constructing new dummy');
        return new Dummy();
    }
})

// ================ TestController.ts =======================
@Controller('/test')
@Scope(ProviderScope.REQUEST)
export class TestController {

    constructor(private dummy: Dummy,
                @Inject(CONNECTION) private connString: string
    ) {

        console.log('constructing TestController');
        console.log(`connection string is: ${connString}`);
    }

    @Get('/random')
    async getConnectionName() {
        return {value: this.dummy.randValue};
    }
}

Investigation
At first I assumed that the request scoping was completely broken when using registerProvider, so I created the second class based dependency Dummy and used the @Scope('request') decorator. This worked as expected.
Next, I registered Dummy using registerProvider as shown in the example. To my surprise that also worked, which made me think that it wasn't a problem with registerProvider per se.
After some tinkering, I discovered that changing CONNECTION from a string value to a symbol like Symbol('tenant_db_connection') makes everything work as expected.
Outstanding questions
I have a working solution using Symbols, so I can proceed that way.  Is there some reason that using a string as a provider token causes the request scope to be ignored?  If so, can we get that documented so that other people don't have to struggle with that quirk?
Information

Version: 6.126.1
Packages:

        "@hubspot/api-client": "^0.8.0",
        "@sendgrid/mail": "^7.0.0",
        "@slynova/flydrive": "^1.0.3",
        "@slynova/flydrive-s3": "^1.0.3",
        "@tsed/common": "^6.126.1",
        "@tsed/core": "^6.126.1",
        "@tsed/di": "^6.126.1",
        "@tsed/exceptions": "^6.126.1",
        "@tsed/json-mapper": "^6.126.1",
        "@tsed/passport": "^6.126.1",
        "@tsed/platform-express": "^6.126.1",
        "@tsed/schema": "^6.126.1",
        "@tsed/swagger": "^6.126.1",
        "@tsed/typeorm": "^6.126.1",
        "@types/cookie-parser": "^1.4.2",
        "@types/passport-jwt": "^3.0.6",
        "axios": "^0.21.4",
        "bcryptjs": "^2.4.3",
        "body-parser": "^1.19.0",
        "class-transformer": "^0.4.0",
        "cookie-parser": "^1.4.5",
        "cors": "^2.8.5",
        "dotenv": "^8.2.0",
        "express": "^4.17.1",
        "express-session": "^1.17.0",
        "form-data": "^2.5.1",
        "jsonwebtoken": "^8.5.1",
        "lodash": "^4.17.21",
        "moment": "^2.24.0",
        "multer": "^1.4.2",
        "passport": "^0.4.1",
        "passport-http-bearer": "^1.0.1",
        "passport-jwt": "^4.0.0",
        "passport-local": "^1.0.0",
        "pdf-fill-form": "^5.0.1",
        "pg": "^8.5.1",
        "pg-hstore": "^2.3.3",
        "reflect-metadata": "^0.1.13",
        "typeorm": "^0.2.29",
        "uuid": "^8.3.2"

hello @supercoffee
Thanks for the detailed example!
I'm not sure why String is not considered like a symbol. I'll investigate when I have a time.
Isn't a really priority until you have a solution with Symbol :)
See you
Romain


Labeling and styling of form fields

Update form labels so that they aren't so redundant. Example: the labels for the add gig form all include the word "gig" which isn't really necessary. The styling of these labels and input fields should be standardized and the styling documented so that it can be applied to all forms moving forward (such as the add profile and add venue forms, which will be implemented AFTER the MVP has been finished).

My pull request: https://github.com/gig-central/gig-repo-1/pull/216 completes this issue

Can't find the pull request for this, and a physical examination shows the work has been done.
Closing.


delete the dumy content

Thanks for your effort on this template, my question please how could I delete the dummy contentful content like Iceland, Spain due to when I deleted from contentful or the json file it shows an error so could you please tell me how can I deleted it.
Thanks.

Thanks,
It was indeed required to have at least 1 item in Contentful added, but I've just fixed it in today's commits:
https://github.com/wkocjan/gatsby-contentful-portfolio/commit/e5ba24f3e40a37a2686f3d8714ea085bf14ab2b2
https://github.com/wkocjan/gatsby-contentful-portfolio/commit/22a9238401c04a96b0dc799869554b72d1949e33
Please get the latest changes from the repo and it should help.

Thanks for spotting it. I've just pushed a fix: https://github.com/wkocjan/gatsby-contentful-portfolio/commit/790e3ec190edc920e0e69bc793809527ce8adc30
Can you please confirm it helps?

Yes thanks, it works finde now

Great, thanks! Closing the issue then.


"getting started" button does not hide away

The button is quite large for some screen resolutions and there is no way to hide it.

I believe this is fixed now that the button moves into the toolbar and disappears in mobile.

Still an issue in tablet mode on small screens that are at the edge of the résiliation breakpoint.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Richard Knoll<EMAIL_ADDRESS>Sent: Thursday, January 26, 2017 1:40:31 AM
To: Microsoft/pxt
Cc: Peli de Halleux; Author
Subject: Re: [Microsoft/pxt] "getting started" button does not hide away (#1044)
I believe this is fixed now that the button moves into the toolbar and disappears in mobile.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fissues%2F1044%23issuecomment-275287128&data=02|01|jhalleux%40microsoft.com|8456b1cffc184b453dd408d4458c514c|72f988bf86f141af91ab2d7cd011db47|1|0|636209916338831630&sdata=n2rSMqhAU2rcKhqpYshW4W9tXqNRj0V3ItDooLVcEkI%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KanNEkmcil5ILeGsiqm-FHUUtU0wks5rV_mPgaJpZM4Lcy73&data=02|01|jhalleux%40microsoft.com|8456b1cffc184b453dd408d4458c514c|72f988bf86f141af91ab2d7cd011db47|1|0|636209916338831630&sdata=vHsbh57q%2F4cC7W%2F3Ol0nsF%2BWFxwzrtJ4yzAEld6sv7o%3D&reserved=0.


🧑💻 : Adding Footer to Website

:red_circle: Title : Adding footer
:red_circle: Enhancement Aim : Their will a footer at the end of the page , which contains social links with feedback option.
:red_circle: Changes : Adding footer which matches the theme of website.
Screenshots 📷

✅ Details to Include When Taking the Issue:
Name : Satyam rai
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.):
GSSOC

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

someone working on it,Do not get demotivated and raise new issue


Textfield long press word select it

A double-tap does the trick here. I don't think we need to implement a long press on it. Closing.


Loading any dataset fills up the entire GPU memory

Loading any dataset causes the entire GPU memory to be filled up (e.g. 0MiB / 49140MiB -> 47149MiB / 49140MiB). If I force it to load on CPU (with tf.device('/CPU:0')), it will be fine until I start to iterate over the dataset, at which point it will fill up the GPU memory again.
Minimal example:
import sunds
ds = sunds.load('kubric:nerf_synthetic/lego', split='train', task=sunds.tasks.Nerf())

Output:
2023-02-06 23:02:15.160292: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1613] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 46653 MB memory:  -> device: 0, name: NVIDIA RTX A6000, pci bus id: 0000:3b:00.0, compute capability: 8.6
WARNING:tensorflow:From /data/vision/polina/users/clintonw/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/tensorflow/python/autograph/pyct/static_analysis/liveness.py:83: Analyzer.lamba_check (from tensorflow.python.autograph.pyct.static_analysis.liveness) is deprecated and will be removed after 2023-09-23.
Instructions for updating:
Lambda fuctions will be no more assumed to be used in the statement where they are used, or at least in the same block. https://github.com/tensorflow/tensorflow/issues/56089

Not a hardware issue (it occurs on different machines).
Environment: packages.txt

Did you resolve this issue?


Incorrect documentation links

Describe the bug
bandit CLI generates incorrect links
To Reproduce

Write code with lxml.etree.fromstring call and run bandit CLI
Verify that the output link/reference in command line is not correct (using a browser). Check output below:

>> Issue: [B320:blacklist] Using lxml.etree.fromstring to parse untrusted XML data is known to be vulnerable to XML attacks. Replace lxml.etree.fromstring with its defusedxml equivalent function.
   Severity: Medium   Confidence: High
   Location: <location of file>
   More Info: https://bandit.readthedocs.io/en/latest/blacklists/blacklist_imports.html#b313-b320-xml-bad-etree

Expected behavior
Should generate links to https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html#b313-b320-xml instead of still linking to imports https://bandit.readthedocs.io/en/latest/blacklists/blacklist_imports.html#b313-b320-xml-bad-etree
Bandit version

bandit 1.6.2
  python version = 3.7.6 (default, Mar  3 2020, 09:46:53) [Clang 11.0.0 (clang-1<IP_ADDRESS>)]

I'm unable to recreate this. In fact I don't see how this was ever possible, even on version 1.6.2.
As you can see here, kind is set to "calls" also with id of "b313-b320". How is it possible
to set "b313-b320" and go to the else statement where kind is "imports"
https://github.com/PyCQA/bandit/blob/1.6.2/bandit/core/docs_utils.py#L44

If you have handy a complete example I can test with, that would be great. I used one of the existing samples and see no recreation of the bad link.

Can confirm regression with 1.7.4
Test results:

Issue: [B410:blacklist] Using etree to parse untrusted XML data is known to be vulnerable to XML attacks. Replace etree with the equivalent defusedxml package.
Severity: Low   Confidence: High
CWE: CWE-20 (https://cwe.mitre.org/data/definitions/20.html)
Location: scripts/bump_mri_versions/main.py:14:0
More Info: https://bandit.readthedocs.io/en/0.0.0/blacklists/blacklist_imports.html#b410-import-lxml


perf_data_converter: update fixed derivation hash.

No change in version, but fixing the fixed derivation hash.
The bazel fixed derviation seems to be changing depending on some other environmental factors that are picked up by the fixed derivation assuming a certain context.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This will be fixed and superseded with the solution to #369091
Closing without merge.


ValueError: Field default cannot be set in Annotated for discriminated unions

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.9.0
            pydantic compiled: True
                 install path: /Users/*****/Library/Caches/pypoetry/virtualenvs/mei-imf-z9_q_NMv-py3.10/lib/python3.10/site-packages/pydantic
               python version: 3.10.2 (main, Feb  2 2022, 08:42:42) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
                     platform: macOS-11.6.5-x86_64-i386-64bit
     optional deps. installed: ['typing-extensions']

"""Bug: ValueError: `Field` default cannot be set in `Annotated` for similar classes"""

from typing import Literal, Annotated, Union, List, Optional
from uuid import UUID

from pydantic import BaseModel, Extra, Field

class BaseResource(BaseModel, extra=Extra.forbid):
    """BaseResourceType as defined by SMPTE ST 2067-3:2016"""
    id: UUID

class TrackFileResource(BaseResource):
    """TrackFileResourceType as defined by SMPTE ST 2067-3:2016"""
    type: Literal["TrackFileResourceType"]
    sourceEncoding: UUID

class MarkerResource(BaseResource):
    """MarkerResourceType as defined by SMPTE ST 2067-3:2016"""
    type: Literal["MarkerResourceType"]
    label: str

Resource = Annotated[Union[TrackFileResource, MarkerResource], Field(discriminator='type')]

class SequenceType(BaseModel, extra=Extra.forbid):
    """Sequence as defined in SMPTE ST 2067-3:2016"""
    id: UUID
    trackId: UUID
    resourceList: List[Resource]

class CDPSequenceType(BaseModel, extra=Extra.forbid):
    """CDPSequence as defined in SMPTE ST 2067-2:2020"""
    id: UUID
    trackId: UUID
    parentTrackID: UUID
    resourceList: List[Resource]

class Sequence(BaseModel, extra=Extra.forbid):
    """Sequence including SMPTE ST 2067-3:2016 and SMPTE ST 2067-2:2020"""
    mainImageSequence: Optional[SequenceType]
    cdpSequence: Optional[CDPSequenceType]

With the above code when I try to import I get
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/*****/amazon/git/mei/mei_imf/mei_imf/model/test_bug.py", line 35, in <module>
    class CDPSequenceType(BaseModel, extra=Extra.forbid):
  File "pydantic/main.py", line 204, in pydantic.main.ModelMetaclass.__new__
  File "pydantic/fields.py", line 488, in pydantic.fields.ModelField.infer
  File "pydantic/fields.py", line 419, in pydantic.fields.ModelField.__init__
  File "pydantic/fields.py", line 534, in pydantic.fields.ModelField.prepare
  File "pydantic/fields.py", line 728, in pydantic.fields.ModelField._type_analysis
  File "pydantic/fields.py", line 776, in pydantic.fields.ModelField._create_sub_type
  File "pydantic/fields.py", line 451, in pydantic.fields.ModelField._get_field_info
ValueError: `Field` default cannot be set in `Annotated` for '_resourceList'

If I change CDPSequenceType to use SequenceType as a base it works
class CDPSequenceType(SequenceType):
    """CDPSequence as defined in SMPTE ST 2067-2:2020"""
    parentTrackID: UUID

Hmm this might have something to do with how the types are handled internally. Curiously this works:
Resource = Annotated[Union[TrackFileResource, MarkerResource], Field(discriminator='type')]
Resource2 = Annotated[Union[TrackFileResource, MarkerResource], Field(discriminator='type')]

class SequenceType(BaseModel, extra=Extra.forbid):
    """Sequence as defined in SMPTE ST 2067-3:2016"""
    id: UUID
    trackId: UUID
    resourceList: List[Resource]

class CDPSequenceType(BaseModel, extra=Extra.forbid):
    """CDPSequence as defined in SMPTE ST 2067-2:2020"""
    id: UUID
    trackId: UUID
    parentTrackID: UUID
    resourceList: List[Resource2]

This was going to be in a library.  I'll just have to document the problem out of existence.  It would be nice to somehow have a discriminated union with having to use a Field.  Field seems to be a catchall for everything right now.  Actually have some sort of DiscrimatedUnion type that you could use to annotate the union instead of a Field.  The Field(discriminator='foo') could be kept for backwards compatibility.

If your intention is to retain a public "type hint" for the Union I reckon this serves your purpose:
Resource = Union[TrackFileResource, MarkerResource]

class SequenceType(BaseModel, extra=Extra.forbid):
    """Sequence as defined in SMPTE ST 2067-3:2016"""
    id: UUID
    trackId: UUID
    resourceList: List[Annotated[Resource, Field(discriminator='type')]]

class CDPSequenceType(BaseModel, extra=Extra.forbid):
    """CDPSequence as defined in SMPTE ST 2067-2:2020"""
    id: UUID
    trackId: UUID
    parentTrackID: UUID
    resourceList: List[Annotated[Resource, Field(discriminator='type')]]

Realistically the Annotated[..., Field(discriminator=...)] is only for telling pydantic how to differentiate the two unions to avoid type coercion from UUID to str in your specific example.

I've also been struggling with this problem. In particular, the problem is even worse when working with nested discriminated unions. Toy example:
import typing as t
import pydantic

class SpringerSpaniel(pydantic.BaseModel):
    animal_type: t.Literal["dog"] = "dog"
    dog_type: t.Literal["springer_spaniel"] = "springer_spaniel"

class GoldenRetriever(pydantic.BaseModel):
    animal_type: t.Literal["dog"] = "dog"
    dog_type: t.Literal["golden_retriever"] = "golden_retriever"

Dog = t.Annotated[t.Union[SpringerSpaniel, GoldenRetriever], pydantic.Field(discriminator="dog_type")]

class Tabby(pydantic.BaseModel):
    animal_type: t.Literal["cat"] = "cat"
    cat_type: t.Literal["tabby"] = "tabby"

class Bengal(pydantic.BaseModel):
    animal_type: t.Literal["cat"] = "cat"
    cat_type: t.Literal["bengal"] = "bengal"

Cat = t.Annotated[t.Union[Tabby, Bengal], pydantic.Field(discriminator="cat_type")]

Animal = t.Annotated[t.Union[Dog, Cat], pydantic.Field(discriminator="animal_type")]

#

class User(pydantic.BaseModel):
    pet: Animal

class Mating(pydantic.BaseModel):
    a1: Animal
    a2: Animal

In this case it is not possible to just use Annotated inline as suggested here https://github.com/samuelcolvin/pydantic/issues/3991#issuecomment-1099852863, since we want to use the final union Animal and the intermediate unions Dog, Cat in other parts of the code.

I don't think this is really a bug per-say.

I agree that is expected, given how Field works. But, I would probably say it is still a bug. Unless I misunderstand it, this makes it pretty impossible to reuse intermediate unions in nested discriminated unions.

It would be nice to somehow have a discriminated union with[out] having to use a Field. Field seems to be a catchall for everything right now. Actually have some sort of DiscrimatedUnion type that you could use to annotate the union instead of a Field. The Field(discriminator='foo') could be kept for backwards compatibility.

nice idea i think, maybe an API change like that can help.

pretty sure this is the same issue as https://github.com/samuelcolvin/pydantic/issues/3714?

I'd like to point out that this limitation prevents useful annotate types from being reused.
Say I want to have a type like:
NonNegativeFloat = Annotated[float, Field(ge=0)]

I can't actually use it unless I stick just the part after the equals on the type of a field, and copy-paste it on any other field that needs it instead of reusing just the NonNegativeFloat reference, as is otherwise usual to do with any other complex type hint.
You might argue that I could just use confloat(ge=0) but:

Say my annotation doesn't just need ge but a custom metadata, I can only apply that with an Annotated Field.
Mypy can't deal with functions as type hints, so I have to use Annotated.

More easily (re-)usable type hints means more type-hinted code, which means better code everywhere. this issue makes the difference between having just int and having more accurate information, especially on large and complex codebases.
I realise the fix to this might not be easy but I think the matter needs to at the very least be considered something to be changed eventually and not a closed issue.

In https://github.com/jaraco/inflect/issues/169, a user reports having encountered a similar error message. I'm unsure if it's the same issue. I can't replicate the issue locally using the same code. Can someone take a peek and help me understand if I should file a separate issue and if there is anything the inflect project can do to address the issue for users that encounter it? I'd also appreciate any advice on how I can replicate the user's experience.

This will be fixed in v2, very much doubt we are brave enough to try and fix this in v1.10.


sh command with cocoapods

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
error when trying run sh with pods
Command executed
sh "pod repo add test_frmwrk https://github.com/Disconnecter/framework_src.git"
Complete output when running fastlane, including the stack trace and command used

 fastlane CI_pod_repo_init                                                                     zsh   100  11:53:25 
[✔] 🚀
[11:53:28]: fastlane detected a Gemfile in the current directory
[11:53:28]: However, it seems like you didn't use `bundle exec`
[11:53:28]: To launch fastlane faster, please use
[11:53:28]:
[11:53:28]: $ bundle exec fastlane CI_pod_repo_init
[11:53:28]:
[11:53:28]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
objc[15800]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x2114a6b90) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x103da02c8). One of the two will be used. Which one is undefined.
objc[15800]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x2114a6be0) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x103da0318). One of the two will be used. Which one is undefined.
[11:53:29]: ------------------------------
[11:53:29]: --- Step: default_platform ---
[11:53:29]: ------------------------------
[11:53:29]: Driving the lane 'ios CI_pod_repo_init' 🚀
[11:53:29]: ----------------------------------------------------------------------------------------
[11:53:29]: --- Step: pod repo add test_frmwrk https://github.com/Disconnecter/framework_src.git ---
[11:53:29]: ----------------------------------------------------------------------------------------
[11:53:29]: $ pod repo add test_frmwrk https://github.com/Disconnecter/framework_src.git
[11:53:29]: ▸ /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1402:in `rescue in block in activate_dependencies': Could not find 'minitest' (>= 5.1) among 190 total gem(s) (Gem::MissingSpecError)
[11:53:29]: ▸ Checked in 'GEM_PATH=/opt/homebrew/Cellar/fastlane/2.204.2/libexec:/opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec' at: /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/specifications/activesupport-<IP_ADDRESS>.gemspec, execute `gem env` for more information
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1399:in `block in activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:299:in `block in activate_bin_path'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `synchronize'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `activate_bin_path'
[11:53:29]: ▸ from /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/bin/pod:23:in `'
[11:53:29]: ▸ /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/dependency.rb:311:in `to_specs': Could not find 'minitest' (>= 5.1) among 190 total gem(s) (Gem::MissingSpecError)
[11:53:29]: ▸ Checked in 'GEM_PATH=/opt/homebrew/Cellar/fastlane/2.204.2/libexec:/opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec' , execute `gem env` for more information
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1400:in `block in activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:299:in `block in activate_bin_path'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `synchronize'
[11:53:29]: ▸ from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `activate_bin_path'
[11:53:29]: ▸ from /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/bin/pod:23:in `'
+------------------+----------------------+
|              Lane Context               |
+------------------+----------------------+
| DEFAULT_PLATFORM | ios                  |
| PLATFORM_NAME    | ios                  |
| LANE_NAME        | ios CI_pod_repo_init |
+------------------+----------------------+
[11:53:29]: Exit status of command 'pod repo add test_frmwrk https://github.com/Disconnecter/framework_src.git' was 1 instead of 0.
/opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1402:in `rescue in block in activate_dependencies': Could not find 'minitest' (>= 5.1) among 190 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/opt/homebrew/Cellar/fastlane/2.204.2/libexec:/opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec' at: /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/specifications/activesupport-<IP_ADDRESS>.gemspec, execute `gem env` for more information
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1399:in `block in activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:299:in `block in activate_bin_path'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `synchronize'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `activate_bin_path'
	from /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/bin/pod:23:in `'
/opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/dependency.rb:311:in `to_specs': Could not find 'minitest' (>= 5.1) among 190 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/opt/homebrew/Cellar/fastlane/2.204.2/libexec:/opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec' , execute `gem env` for more information
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1400:in `block in activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in `block in activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `each'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in `activate'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:299:in `block in activate_bin_path'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `synchronize'
	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in `activate_bin_path'
	from /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/bin/pod:23:in `'
+------+--------------------------------------+-------------+
|                     fastlane summary                      |
+------+--------------------------------------+-------------+
| Step | Action                               | Time (in s) |
+------+--------------------------------------+-------------+
| 1    | default_platform                     | 0           |
| 💥   | pod repo add test_frmwrk             | 0           |
|      | https://github.com/Disconnecter/fram |             |
+------+--------------------------------------+-------------+
[11:53:29]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
/opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in shell_error!': \e[31m[!] Exit status of command 'pod repo add test_frmwrk https://github.com/Disconnecter/framework_src.git' was 1 instead of 0. (FastlaneCore::Interface::FastlaneShellError) /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1402:in rescue in block in activate_dependencies': Could not find 'minitest' (>= 5.1) among 190 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/opt/homebrew/Cellar/fastlane/2.204.2/libexec:/opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec' at: /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/specifications/activesupport-<IP_ADDRESS>.gemspec, execute gem env for more information
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1399:in block in activate_dependencies' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in each'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in activate_dependencies' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in activate'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in block in activate_dependencies' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in each'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in activate_dependencies' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in activate'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in block in activate_dependencies' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in each'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in activate_dependencies' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in activate'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:299:in block in activate_bin_path' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in synchronize'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in activate_bin_path' 	from /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/bin/pod:23:in '
/opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/dependency.rb:311:in to_specs': Could not find 'minitest' (>= 5.1) among 190 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/opt/homebrew/Cellar/fastlane/2.204.2/libexec:/opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec' , execute gem envfor more information 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1400:inblock in activate_dependencies'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in each' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in activate_dependencies'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in activate' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in block in activate_dependencies'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in each' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in activate_dependencies'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in activate' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1406:in block in activate_dependencies'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in each' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1388:in activate_dependencies'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems/specification.rb:1370:in activate' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:299:in block in activate_bin_path'
from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in synchronize' 	from /opt/homebrew/Cellar/ruby/3.0.3/lib/ruby/3.0.0/rubygems.rb:298:in activate_bin_path'
from /opt/homebrew/Cellar/cocoapods/1.11.2_1/libexec/bin/pod:23:in <main>' \e[0m 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/helper/sh_helper.rb:80:in sh_control_output' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/helper/sh_helper.rb:16:in sh_no_action'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/fast_file.rb:223:in block in sh' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/fast_file.rb:222:in sh' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/fast_file.rb:216:in sh'
from Fastfile:43:in block (2 levels) in parsing_binding' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/lane.rb:33:in call'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/runner.rb:45:in chdir'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/runner.rb:45:in execute' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/commands_generator.rb:109:in block (2 levels) in run'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/commander-4.6.0/lib/commander/command.rb:187:in call' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/commander-4.6.0/lib/commander/command.rb:157:in run'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/commands_generator.rb:353:in run'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/commands_generator.rb:42:in start' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/gems/fastlane-2.204.2/bin/fastlane:23:in <top (required)>' 	from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/bin/fastlane:25:in load'
from /opt/homebrew/Cellar/fastlane/2.204.2/libexec/bin/fastlane:25:in `'

Environment

 🚫 fastlane environment 🚫
Stack

Key
Value

OS
12.1

Ruby
3.0.3

Bundler?
false

Git
git version 2.32.0 (Apple Git-132)

Installation Source
/opt/homebrew/Cellar/fastlane/2.204.2/libexec/bin/fastlane

Host
macOS 12.1 (21C52)

Ruby Lib Dir
/opt/homebrew/Cellar/ruby/3.0.3/lib

OpenSSL Version
OpenSSL 1.1.1l  24 Aug 2021

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
13.2.1

Swift Version
5.5.2

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)
POD_FRMW_NAME = "test_frmwrk"

platform :ios do

  desc "Bump podspec version options bump_type patch, minor, major. patch by default. then run add_tag automaticaly"
  lane :pod_spec_bump do |options|
	version_bump_podspec(bump_type: options[:bump_type])
	add_tag
  end

  desc "Adding tag related podspec version and push to repo. then run push_spec automaticaly"
  lane :add_tag do
	add_git_tag(tag: lane_context[SharedValues::PODSPEC_VERSION_NUMBER])
	push_git_tags
	push_spec
  end

  desc "Commit and push podspec to repo + pod repo push"
  lane :push_spec do
	git_commit(path: "./POD_FRMW_NAME.podspec", message: "Podspec Version Bump")
	push_to_git_remote
	sh "pod repo push POD_FRMW_NAME --allow-warnings"
  end

	desc "Init pod repo"
  lane :CI_pod_repo_init do
  sh "pod repo add test_frmwrk https://github.com/Disconnecter/framework_src.git"
  end

end

`./fastlane/Appfile`
# app_identifier("[[APP_IDENTIFIER]]") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.204.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.5.0

atomos
0.1.3

rexml
3.2.5

CFPropertyList
3.0.5

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.21.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.6

addressable
2.8.0

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.91.0

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.3

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.9.3

unf_ext
0.0.8

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.4

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

json
2.5.1

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.7.6

bundler
2.2.32

simctl
1.6.8

jwt
2.3.0

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.1.1

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.16.0

googleauth
1.1.0

httpclient
2.8.3

webrick
1.7.0

google-apis-core
0.4.2

google-apis-playcustomapp_v1
0.7.0

google-apis-androidpublisher_v3
0.16.0

google-cloud-env
1.5.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.10.0

google-apis-storage_v1
0.11.0

rake
13.0.6

digest-crc
0.6.4

google-cloud-storage
1.36.0

emoji_regex
3.2.3

jmespath
1.5.0

aws-partitions
1.552.0

aws-eventstream
1.2.0

aws-sigv4
1.4.0

aws-sdk-core
3.126.0

aws-sdk-kms
1.54.0

aws-sdk-s3
1.112.0

set
1.0.1

forwardable
1.3.2

logger
1.4.3

pathname
0.1.0

shellwords
0.1.0

cgi
0.2.1

date
3.1.3

timeout
0.1.1

stringio
3.0.1

securerandom
0.1.0

uri
0.10.1

ipaddr
1.2.2

openssl
2.2.1

digest
3.0.0

io-nonblock
0.1.0

io-wait
0.2.0

zlib
2.0.0

resolv
0.2.1

time
0.1.0

open-uri
0.1.0

mutex_m
0.1.1

net-protocol
0.1.1

ostruct
0.3.1

english
0.7.1

erb
2.2.0

strscan
3.0.1

abbrev
0.1.0

io-console
0.5.7

tempfile
0.1.1

delegate
0.2.0

fileutils
1.5.0

tmpdir
0.1.2

base64
0.1.0

singleton
0.1.1

net-http
0.1.1

open3
0.1.1

nkf
0.1.0

prettyprint
0.1.1

pp
0.2.1

find
0.1.0

yaml
0.1.1

psych
3.3.2

generated on: 2022-02-07

it's not related to fastlane at all: auth is required to access this repo as it's private.
either add credentials to keychain beforehand like cocoapods do (check on local machine) or use SSH with proper key.


Fixes errors in README

Let me know if this is the wrong base branch to be merging into.

Removed the typo, good catch!

@ramonaharrison @tiwiz Can I merge this?

Cc @wdziemia


Refactor custom components to be render functions

Reasons for changes

Adding custom components by just passing a component as a prop (like customCloseComponent) is almost useless because then the only way to close the story is by swiping down from the top
This way uses a system such like react-native-tab-view's renderTabBar function
This allows passing the current item and onPress or profileName as props to the render functions so they can have access to the onClosePress function
This is useful in situations where you want to add another button component next to the close/swipe button which has it's own onPress prop. For example adding a share story button next to the close button like so:
adding customProps to the IUserStoryItem enables users to add their own props, which is then useful for rendering a custom text component, for example, say adding the age of a instagram story which can be rendered underneath the users profile name (like instagram)

Summary of changes

[x] add:

renderSwipeUpComponent
renderCloseComponent
renderTextComponent

[x] add IUserStoryItem.customProps

Important ⚠

This is a breaking change and should incur a major release versioning update

@caglardurmus please let me know if you would like this not to be a breaking change - I can add the previous props back in and account for them and throw some developer errors if both props are passed, or create something like a CSS cascading order of priority.
Cascading example: oldProp > new renderProp -> defaultPackageComponent

@IB3N Are these changes already added?

@lucasdzuc I don't think so, this is the PR to merge them right?


[ README ] change the url of nntrainer

This patch changes the url of nntrainer from nnstreamer.mooo.com to
ci.nnstreamer.ai
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

Close due to #1885


build: only search for ICU if building the stdlib/sdk overlay

When building just the tools, the ICU search is not needed as the compiler and
the tools do not use ICU themselves.  This enables cross-compiling just the
swift compiler.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @gottesmm @Rostepher

@swift-ci please test

As long as there aren't any other variables for triggering the stdlib/runtime to build, this LGTM.

@gottesmm - I'm able to get through a cross-compiling configure with this change.  There is another change needed for the component installation.


[PROCS-4208] Prevent use of process_config.run_in_core_agent.enabled config in unsupported environments.

What does this PR do?
This PR wraps the use of the process_config.run_in_core_agent.enabled config behind a helper function with different implementations across linux and non-linux builds. The aim is to ensure that the actual config value will not be used in unsupported environments (not linux) to prevent any misconfigurations which can break functionality. For example, before this change, a windows agent user could enable this config and no Processes-related checks would run on the process or core agent due to existing logic respecting the value no matter the environment. Now, the checks would run on the process agent, ignoring the config.
Motivation
PROCS-4208
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Unit and e2e tests were added to validate this.

/merge

/merge


how can i revert all code of all open files to the previous state?

Hopefully you have initialized a git repository in your working directory.
git reset --hard will revert to last committed state

thats like rocketscience what u said

I just use to ask to do so: REVERT TO THE INITIAL STATE ALL THE EDITS MADE IN THIS SESSION
hope this helps

I think you can also focus on each file and press undo or ctrl+z.

If you want better version control I sugest adding this to Custom Instructions (in settings) to keep git history as Claude works:
"After completing a task or making significant changes, automatically run git add . && git commit -m with a message summarizing the recent updates."
This way you can keep track of his work in git and easily revert the changes he makes.


404 Error on CRUD pages /admin/page

Bug report
Try to access the CRUD pages at site.com/admin/crudpage, but they all return a 404 page.
What I did:
Uploading files from working local dev environment to live environment.
What I expected to happen:
I expect to see the CRUD pages that show me the contents of the database and allow me to add/edit.
What happened:
Going to the page gives me a 404 error.
I am able to access default routs from Backpack (login, dashboard, logout).
What I've already tried to fix it:
Looking through route files, controller files, etc
Backpack, Laravel, PHP, DB version:
Laravel 5.4
PHP 5.6
Backpack CRUD: 3.2

@cvassios-ekko  I feel this has something to so with the way the routes were added. Can you post the question on stack overflow and add some code for reference?


Empty key triggers error in decode-uri-component

When you have a query like ?foo=bar&baz, baz won't have a value.
When the values get decoded with decode-uri-component, an error will be thrown:

TypeError: Expected encodedURI to be of type string, got undefined

I think a check should be performed before decoding the value the prevent this error.

We already have a test for this: https://github.com/sindresorhus/query-string/blob/cca729511b8ee4244caab51b7fce2c2a39775dc7/test/parse.js#L59-L62
Submit a pull request with a failing test and I'll take a closer look.


more e2e tests for encryption

needs https://github.com/openshift/cluster-kube-apiserver-operator/pull/615

/assign @sttts

e2e-aws-operator-encryption step is not triggered when the files didn't change https://github.com/openshift/cluster-kube-apiserver-operator/pull/617

/test e2e-aws-operator-encryption
make sure the tests are stable

decided to merge https://github.com/openshift/cluster-kube-apiserver-operator/pull/618


[SPARK-16872][ML] Gaussian Naive Bayes Classifier

What changes were proposed in this pull request?
implement Gaussian NB in ML
How was this patch tested?
local test in spark-shell, comparing to Scikit-Learn
added unit tests

Test build #66235 has started for PR 15324 at commit 4d8a025.

Test build #66235 has finished for PR 15324 at commit 4d8a025.

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

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

Merged build finished. Test FAILed.

Test build #66236 has started for PR 15324 at commit 08b0baf.

Test build #66236 has finished for PR 15324 at commit 08b0baf.

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

Merged build finished. Test FAILed.

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

Test build #66237 has started for PR 15324 at commit 52a974d.

Test build #66237 has finished for PR 15324 at commit 52a974d.

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

Merged build finished. Test PASSed.

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

cc @yanboliang @MLnick Can you please review this in spare time?

Was there some discussion as to whether GaussianNB should be part of the NaiveBayes estimator or its own estimator? It seems the semantics are different enough between multinomial NB and Gaussian NB to at least warrant discussion. The meaning theta matrix in Gaussian NB vs multinomial is very different in this patch - one is matrix of Gaussian distribution paramters, and the other is a matrix of class conditional probabilities. Also, some params only apply to one and not the other. My apologies if I have missed this conversation somewhere. Thanks!

I tend to agree with Seth on this - the gaussian case is different enough that it could be separate.
Though in terms of the estimator, from a public-facing API perspective it is one param that is unused, so it it's not that big a deal to be unified.
However in terms of the model, I really, really don't like the hack of putting the theta and sigma into one matrix. That leaves us with either creating a new estimator/model combo (let's see how much code duplication that involves), or having a def getSigma or a new val sigma that is only used for Gaussian. Not super pretty...

@yanboliang  what is your opioion?

@MLnick @sethah Thanks for your review. This PR now is just like what I am using in work. I agree that it will bring some inconvenience to merge theta and sigma together. I will change it to another estimator if needed.

I'm against to merge theta and sigma together, it should be two individual variables of model. To the question that whether GaussianNB should be part of the NaiveBayes estimator, I'm ambivalent between these two opinions but I'm more prefer to add another variable sigma to the model. When it's a gaussian NB model, both theta and sigma are effective; otherwise, only theta is valid. We keep private constructor for all models, so add another variable is not a big issue. I'm open to hear others' thoughts. cc @jkbradley

I tend to make GaussianNB as a special modelType option in current NB.
However, there are significant differences:
1, 'theta' matrix is used to store means
2, extra sigma matrix needed to store variance
3, param smoothing has no effert, according to sklearn's implementation.
To keep current NB design, I think there are two methods to include GaussianNB:
1, merge theta and sigma together (you are all against this)
2, update NaiveBayesModel and include sigma as a extra matrix, and sigma is only meaningful when using GaussianNB
I'm open on this issue, and I will update this PR when we come to a conclusion.

Test build #66604 has started for PR 15324 at commit c6ad342.

Test build #66604 has finished for PR 15324 at commit c6ad342.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Jenkins, retest this please.

Test build #66727 has started for PR 15324 at commit c6ad342.

Test build #66727 has finished for PR 15324 at commit c6ad342.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

@sethah @MLnick @yanboliang Thanks for your comments, and  I will work to make GNB a separated classifier.

Test build #70747 has started for PR 15324 at commit c644f66.

Test build #70747 has finished for PR 15324 at commit c644f66.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class GaussianNaiveBayes @Since(\"2.2.0\") (

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

Merged build finished. Test FAILed.

Test build #70791 has started for PR 15324 at commit a59c558.

Test build #70791 has finished for PR 15324 at commit a59c558.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #70794 has started for PR 15324 at commit cd4e68e.

Test build #70794 has finished for PR 15324 at commit cd4e68e.

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

Merged build finished. Test FAILed.

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

Test build #70799 has started for PR 15324 at commit 6e2d066.

Test build #70802 has started for PR 15324 at commit 8e0de62.

Test build #70799 has finished for PR 15324 at commit 6e2d066.

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

Merged build finished. Test FAILed.

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

Test build #70803 has started for PR 15324 at commit df29d10.

Merged build finished. Test FAILed.

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

Merged build finished. Test FAILed.

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

Jenkins, retest this please

Test build #70811 has started for PR 15324 at commit df29d10.

Test build #70811 has finished for PR 15324 at commit df29d10.

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

Merged build finished. Test PASSed.

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

@jkbradley What's your opinion about whether GNB should be a separated Classifier or a modeltype in existing NB?


Build container structure

Build container structure and environment variables to local and remote setups.

[x] Create .env.default
[x] Create .Dockerfile
[x] Create MakeFile
[ ] Deploy to Heroku

Created new cluster at Google Cloud Kubernetes


Change stat name to heal.triggered in docs

Update monitoring docs to reflect the change in stat name.

LGTM, maybe mention uber/ringpop-node#273 in the description when merging?

Looks good!


Reconnect DRPC client with server

Hello everyone, I ran into the problem of reconnecting the drpc client with the server, if the server crashes in a panic and recovers, the client via tcp, of course, cannot reach it, except for creating a new client, I did not find a way to solve the problem. Maybe someone has a ready-made reconnect practice in the background?

Hi @spacecodewor, the specific semantics and behavior for the reconnection scenario you mentioned tend to be "application specific". For example, there are a number of possible ways you might wanna/need to handle it:
If the server is down/unreachable and the client is trying to send a new request you can:

Drop the request and report the issue (via logging, telemetry, etc)
Queue the request and retry automatically once the server is back again
Re-route the request to another server
Treat the issue as transient and irrelevant and simply ignore it (for example if this was merely a Ping request)
Use a "circuit breaker" component to avoid propagating the issue to other services
...many others...

Neither of these is particularly right or wrong, the most suitable solution will depend on your specific application requirements. As such, low level libraries only provide the required primitives for you to build the best solution for you and your particular needs.
For example, to handle automatic reconnections you could create a MonitoredConnection type that wraps together a Client instance and a Ticker to periodically check if the client has active connections to the server using the IsActive method. If the server is down you can try to start a new client connection.
A simpler approach could be to simply use the Retry client middleware included with this module. https://github.com/bryk-io/pkg/blob/master/net/drpc/middleware/client/retry.go#L16
// Retry failed requests up to the `max` number of attempts specified. Retried
// errors will be logged as warnings along with details about the specific
// attempt. Multiple tries introduce an increasingly longer backoff delay to
// account for transient failures on the remote. The specific delay for each
// attempt is calculated (in ms) as: `delay * (factor * attempt_number)`

You can find an example of how this client middleware can be used here: https://github.com/bryk-io/pkg/blob/master/net/drpc/server_test.go#L436-L465


Moar sonar

Type of change

Refactoring

Description
Get rid of Sonar warnings about declaring JUnit 5 methods public.
Additional Context
Checklist
Please go through this checklist and make sure all applicable tasks have been done

[ ] Write tests
[x] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonar-Lint warnings are addressed or are justifiably ignored.
[ ] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

I'll talk to @robobario about it, I'm in no rush and agree this is largely mechanical so easier to deal with here but I don't want to leave this hanging around waiting.


fix copy in place for S3 bucket with encryption

This PR would fix #6300
With S3 new default encryption for bucket, I've overlooked one case where the bucket would have a manually set encryption configuration. In that case, S3 will allow copying in place. For now, it is rather simple to fix, we just need to check if the bucket has encryption, but this will become a bit more complicated when we implement the default encryption with our bucket has well.
I've also sneaked a little fix regarding BucketKeyEnabled header, as it should not be returned when the encryption is not aws:kms (verified with AWS as well).

Hi @bblommers, I'm not sure my changes are related to the test failures?
 Did I do something wrong? 😅

The tests are a bit flaky @bentsku - I've restarted the build, and now they all pass

The tests are a bit flaky @bentsku - I've restarted the build, and now they all pass

Awesome, thanks a lot!


Compatibility with React 0.13

Somehow I don't think this is all that will need to be changed.

Hi @dcousens, this was the bare minimum to run under react 0.13, but I agree there are more things that need to change to fully work with idiomatic React 0.13 (e.g. mixins)

@JedWatson can you look over this?  I'll test/merge it later, but just a once over would be greatly appreciated.

Thanks @cassiozen, I'm going to manually merge this (due to conflicts) and make sure everything works now, high time we got over the 0.13 hurdle.


chore: upgrade gradle to v8.5

Description

Solution

Current dependencies on/for this PR:

master

PR #37

PR #36

PR #38   👈

This stack of pull requests is managed by Graphite.


Update Cargo.toml

library target names cannot contain hyphens: vorbis-sys. @pcwalton Please merge ASAP

Actually, #1 is better :)


mssql - use official Microsoft driver

Microsoft has created an official fork of https://github.com/denisenkom/go-mssqldb at https://github.com/microsoft/go-mssqldb in agreement with the original project maintainers https://github.com/denisenkom/go-mssqldb/issues/729
Since then, there have been plenty of fixes and enhancement delivered under the new Microsoft umbrella and many official versioned releases.
The original project is receiving the minimum maintenance effort.
xk6-sql should adopt the new fork of go-mssqldb in favor of the legacy driver.

@cwegener thank you for raising this issue! We'll get that updated.


Knex without await doesn't execute query

Questions about knex
I'm trying to understand how the await keyword works in KNEX. Take the following example:
knex.schema.createTable( ... );

It will not execute the create table query in the database. However if I stick and await in front of it.
await knex.schema.createTable( ... );

This will now execute the create query in the database.
My understanding is that await is used to wait for a promise resolution but in this case it feels like something else is going on because not awaiting the function doesn't return a promise.
Should the code that isn't using await still be executing the query?
PS: sorry if this is not the most appropriate to ask here but I've have no luck asking anywhere else 😇

knex chain returns thenable. then method call starts query. await is just a syntax sugar on top of promises/thenables.
knex.schema.createTable( ... ).then(() => {})

@TrySound is correct. knex.schema.createTable( ... ); returns a Promise-like, that can be either await'ed or consumed within then chain.

Thanks for your replies. Hmm that makes sense. I guess it's the implementation that I can get my head around. Is there a place in the code you could link me to to see this in more detail? I've looked at the createTable method for the MySQL dialect and it just seems to push items into sequence and doesn't actually return anything?
When we use the await keyword is it calling the then method defined in interface.js?
This is what has confused me 😂😇

Is there a place in the code you could link me to to see this in more detail?
Sure, for an example: https://github.com/knex/knex/blob/master/test/integration/schema/foreign-keys.js
When we use the await keyword is it calling the then method defined in interface.js?
This is correct.


Revert Text/MText Linking of Rotation and AlignmentPoint

While testing these changes in production, it was found that since the MText.Rotation set the AlignmentPoint and vice versa, the former would break the correct alignment points which are required for correct text placement.
This PR reverts part of the changes relating to the linking of Rotation and AlignmentPoint for both TextEntity and MText.
We need to review how to handle this properly.  Right now, I think the best course of action would be to unlink the two and allow for the library consumer to determine how to properly handle the values.  I am not even sure that it is actually possible to convert from a Rotation radian to a 3D AlignmentPoint.

Side note, do you have any more direct contact you use?  Email, Discord, etc.?  I'd love to be able to talk about certain parts of this project more in a conversational environment if you would be willing.

I've opened the discussions in Github


add race option in unit test

Signed-off-by: Sam Yuan<EMAIL_ADDRESS>

LGTM
And for other people wondering what is race test for golang, see in https://www.cnblogs.com/yjf512/p/5144211.html

Wonder what is the Expected — Waiting for status to be reported

@ryjones Do you know why there is a stale and pending check above
Hyperledger-TWGC.tape Expected — Waiting for status to be reported?

@davidkhala I removed the check.


Allow user to specify list of HDI's in plot_posterior_predictive

At the moment plot_posterior_predictive has hard-wired HDI's. Plots look like this (taken from MMM docs page):

This is the relevant line:
https://github.com/pymc-labs/pymc-marketing/blob/aa5fa1d280eae270a7a992dbc82f77586a02f237/pymc_marketing/mmm/base.py#L414
Can we provide a kwarg, called something like hdi where the user provides a scalar (or list or scalars). That way, we can decide if we just want one or multiple HDI's and what values they are.
Maybe also expose the alphas, or maybe automatically compute them from the provided hdi value(s).

I saw in #1072  the plotting options are specified but the list/scalar or hdi and alphas is missing. Are you still keen to add this on. Feels like couple of revisions made already to plot_posterior_predictive

I saw in #1072 the plotting options are specified but the list/scalar or hdi and alphas is missing. Are you still keen to add this on. Feels like couple of revisions made already to plot_posterior_predictive

I think I'll just try to do this now. Good Monday morning warm-up exercise :)

Yep! easy enough to add!


Open VMD Overlay outside parent div?

I am trying to use the VMD (which is awesome) to animate elements on my page that are draggable. Problem is that when the overlay is added, it is a child element of the draggable div which will not allow me to type into the input fields, or move sliders as all of that is considered to be a handle of the parent div. Is there a way to attach it to the right side of the element, or outside?
I can make the modal window draggable with only the title being the handle with this:
VMD.js line 5526:
o.css({
position: "absolute",
left: "50%",
marginLeft: "-6rem",
width: "300px",
minHeight: "150px",
backgroundColor: "white",
borderRadius: "3px",
boxShadow: "0px 0px 3px 0px rgba(50, 50, 65, 0.5)",
padding: "0.6rem 0.5rem 0.5rem 0.5rem",
opacity: "0.975"
}).addClass("draggableModal");
then later:
$(".draggableModal").draggable({handle:"div"});
But as long as it is a child of a draggable element, I can't input anything.

I made some progress, but the designer clears the style info of the target when it applies the effects, and when you hover over the element you previously clicked on, the modal doesn't appear, you have to go to the target div. Also if you click again, it adds another instance of the modal.
http://jsfiddle.net/moLxhod3/

+1

Sounds like a StackOverflow question (if still relevant) - but I'd look at classes and z-index / transform to see if something is messing with the display context.


Document middleware function names.

Suppose I had the following middleware
const middleware = store => next => action => state;

Conceptually, it is a single thing, middleware.  But when I rewrote it as
function middleware(store) {
  return function(next) {
    return function(action) {
      return state;
    }
  }
}

I realized that the functions that make up middleware don't seem to have a name.
It's nitpicky, but I feel silly naming them middlerware and middlestware.

Well, if you look at the Middleware docs page, the last example that uses full function syntax looks like this:
function logger(store) {
  return function wrapDispatchToAddLogging(next) {
    return function dispatchAndLog(action) {
      console.log('dispatching', action)
      let result = next(action)
      console.log('next state', store.getState())
      return result
    }
  }
}

logger is middleware, but what are wrapDispatchToAddLogging and dispatchAndLog?  Do they have official names?

They don't.  If anything, it's kinda like wrapDispatchToAddThingThisMiddlewareDoes, and dispatchAndDoTheThing :)

Alright, thank you.


Gasinfrastructure cost

Hereby a gist of average gasnetwork cost in Gist. The cost of refrubishing will follow soon

Mmm cannot upload a gist. I will send it to Chael
https://gist.github.com/bb6331ea52a0a386c6fc.git

https://gist.github.com/JeroenvdLogt/bb6331ea52a0a386c6fc

@JeroenvdLogt can you put this is a table please?
This works basically as follows:

Connection type
Tariff

bla
bla

And could you translate all text into English as well?

I changed it to table form. I still have to add cost of refurbishing.
https://gist.github.com/JeroenvdLogt/bb6331ea52a0a386c6fc

Can I upload excel files or csv. I made the tables manually now but this takes a lot of time.

@JeroenvdLogt I have corrected some errors in the syntax of the Markdown (you can check how your Markdown document formats by using a dedicated editor such as http://markdownpad.com/.
Can you check that I did not introduce any mistakes? The updated file

@JeroenvdLogt what is the status of this ticket?

Only the headers of the first table is in dutch. The rest of the gist is okay.

OK, thanks @JeroenvdLogt. Closing.


Add context menus to the floating menu system

Comeplexity: 2
Involves: Frontend (JS)

We'll eventually want to add radial menus also.

Well I might as well be The Menu Guy and take this on. Anything special you had in mind or just a bog standard context menu? Assuming radial menus come later


Conflicting Integrations causing hinderance in development workflow

Describe the bug
As of now, multiple services are being used for code review, namely Hound, CodeCliamte, AccessLint.  These serivices were added to serve for segments of the application, i.e. the rails part, the frontend javascript engine etc, but are not configured properly, and therefore started reviewing all code changes.
The problem at hand is that these services have different configurations and hence contradict each other. This fails the auto PR review a significant number of times. Following the conventions of one service breaks the rules of the other.
To Reproduce
Steps to reproduce the behavior:

Edit some code for javascript
Make a pull request
OR refer #906

Expected behavior
Only one service should be used for auto-code analysis.
Screenshots
Code Climate says

Hound says

Desktop (please complete the following information):

OS: [Ubuntu 19.10]
Browser [80.0.3987.106 (Official Build) (64-bit)]

Are you working on this issue? (Yes/No)
No.

Solution
Configure hound to not check any files other than erb

@tachyons in the hound.yml file , it is only configured for  erblint:  enabled: true and others as false so then where should we look to fix this ?

get other engines which are tru by default and disable this


Remove virtual device support

This is currently not working as expected
closes #110

Can you also add a patch version bump 0.16.1 to avoid creating a separate PR for that? Then I'll cut a release for it.


Add null check for required body parameter - openapi 3

Given the swagger at the bottom of this post, I would like to generate the following C# code.
But the check for body == null is not generated. The body is marked as required, and as far as I know, there is no nullable option, so a required body should be null-checked.
        public async System.Threading.Tasks.Task<int> FooAsync(string itemId, FooRequest body, System.Threading.CancellationToken cancellationToken)
        {
            if (itemId == null)
                throw new System.ArgumentNullException("itemId");

            if (body == null)
                throw new System.ArgumentNullException("body");

    "/api/Data/{itemId}/Foo": {
      "post": {
        "tags": [
          "Data"
        ],
        "summary": "Foo the item.",
        "operationId": "FooAsync",
        "parameters": [
          {
            "name": "itemId",
            "in": "path",
            "description": "The Id",
            "required": true,
            "schema": {
              "type": "string",
              "additionalProperties": false,
              "description": "The Id",
            }
          }
        ],
        "requestBody": {
          "description": "The foo request",
          "content": {
            "application/json": {
              "schema": {
                "$ref": "#/components/schemas/FooRequest"
              }
            }
          },
          "required": true
        },
...

I think inserting this at line 126 of Client.Class.liquid would fix it. (Got a 403 trying to push a branch for a pull request.)
{%     if operation.HasContent -%}
{%         if operation.ContentParameter.IsRequired -%}
        if ({{ operation.ContentParameter.VariableName }} == null)
            throw new System.ArgumentNullException("{{ operation.ContentParameter.VariableName }}");

{%         endif -%}
{%     endif -%}

I think it is already released. Please retest

Sorry this took so long. I got dragged onto another project.
I just tested with release 3111 / toolchain <IP_ADDRESS>, and it looks good.
@melnikvitaly
If you change the test in Client.Class.liquid to this:
{%     if operation.HasContent and operation.ContentParameter.IsRequired and operation.ContentParameter.IsNullableRaw != true -%}
does that make it work for you? In my situation is doesn't hurt anything, but that doesn't mean it helps you.

Looks like IsNullableRaw property is missing on ParameterModel, so it is always "false".
But  ParameterModel has IsNullable property, which is actually calculated based on IsNullableRaw
IsNullableRaw property is calculated based on x-nullable from schema.
x-nullable  in schema is caclulated based on AllowNullableBodyParameters  and typeDescription.IsNullable
AllowNullableBodyParameters is assigned during schema generation based on AllowEmptyInputInBodyModelBinding.
I've created PR
{% if operation.HasContent and operation.ContentParameter.IsNullable != true -%}
When AllowEmptyInputInBodyModelBinding is true and body type is nullable then ParameterModel.IsNullable is true,
When AllowEmptyInputInBodyModelBinding is false and body type is nullable then ParameterModel.IsNullable is false.
@TimothyByrd, hope this will work for you well even without checking IsRequired property and check only IsNullable from schema

Hello, this commit looks like a breaking change
https://github.com/RicoSuter/NSwag/commit/e5d6903edd0b82044dccbdf84d86adeb4ee53829
Previously, a null check for body would not be generated unless it was marked with required: true.
Now it is generated unless the body is marked with nullable: true.
Isn't body supposed to be optional by default?

What is the status for this issue?
I am still facing same issue with .NET60 in NSwagStudio v13.15.10


Bug with category add

Laravel Version: 5.4
Voyager Version: 11.6
PHP Version: 5.6
Database Driver & Version: MySql 5.5

Description:
i found bug with categories, when you add first category, you need to add parent category, but its not exist and you get the error
Steps To Reproduce:

Add new category
http://joxi.ru/MAj9jDRIPgbY2e
Fill all fields
http://joxi.ru/Vm6RVEkia5MNmZ
If you dont have any categories and dont choose parent category, you will get an error
http://joxi.ru/V2VgjJGH5zyQAv

I created a PR https://github.com/the-control-group/voyager/pull/916

Thank you)


Font glyph widths must be an array of numbers

... so assert that when we read it out of the PDF. This should mean we
catch invalid/corrupt PDFs early and raise a MalformedPDFError, rather
than pass around an Array of god knows what.

oops, the W array can contain numbers and other arrays.


建议加入横向滚动功能

OS
macOS 版本14.2.1（版号23C71）
LinearMouse
v0.9.5
Is your feature request related to a problem?
横向滚动
Describe the solution you'd like
比如按住command或shift等可以切换成横向滚动
Describe alternatives you've considered
No response
Additional context
No response

你好，可以在滚动->修饰键中进行设置。


Tests run before bindings on page are complete

I have a test that fails when run from the command line or by launching the browser but succeeds if I reload the page. It looks like the tests are failing because they run before the bindings fire.
Is there some way to defer the test from running?
<!doctype html>
<html>
<head>
    <meta charset="utf-8">
    <script src="../../bower_components/webcomponentsjs/webcomponents.min.js"></script>
    <script src="../../bower_components/web-component-tester/browser.js"></script>
    <link rel="import" href="./cbw-projector.html">
    <link rel="import" href="../../bower_components/iron-ajax/iron-ajax.html">
</head>
<body>
<template is="dom-bind">
    <iron-ajax id="goalsQuery" url="./goals.json" last-response="{{savings}}"
           auto></iron-ajax>
    <cbw-projector balance="{{savings.balance}}" total-monthly-pledge="{{savings.totalMonthlyPledge}}" goals="{{savings.goals}}" id="projector"></cbw-projector>
</template>
<script>
    suite('<cbw-projector>',function(){
        test('binding',function(){
            var node=document.getElementById('projector');
            assert.equal(node.balance, 7000);
            assert.equal(node.totalMonthlyPledge,1500);
            assert.equal(node.goals.length,6,);
        });
    });
</script>
</body>
</html>

Maybe you can try to use fixture element, with it you can have more control when things are stamped and also... clean your element state - link
Or it can be failing for the first time because first load should take some more time... try to delay its execution with done callback... so your test should look like this:
test('binding',function(done){
    setTimeout(function(){
            var node=document.getElementById('projector');
            assert.equal(node.balance, 7000);
            assert.equal(node.totalMonthlyPledge,1500);
            assert.equal(node.goals.length,6);
            done();
    }, 5000); //Delays 5s
});

You can defer when a test completes by using the callback argument to the test function, or returning a Promise. From there you need to defer the start of real test work yourself by waiting on what resources you need.
I also second @MartinsThiago's suggestion of using <text-fixture>, which is automatically imported now.


Improve RAM usage when loading screen

Discussion: #6
New issue report: Improve RAM usage when loading screen
When in loading team to game, loading data take ~ 500 MB!!
Note: I turn off MSVC compiler flags and linker flags for debugging sessions

Interesting so much: Generate pitch take too much space

Well, the function manipulate (pixel x pixel) the overlay and the pitch file, with the lattest that has a really big resolution (4096*2048), maybe there is a way to blend the two texture together (shaders?), the perlin generation, I think, is more CPU intensive than RAM intensive...

Hi Antonio. I found this is interesting idea for generate grass terrain but a disaster for performance. Generate yard lengthen 10 seconds but it is increase more than ~350MB suddenly, as normal game just need ~150MB in gameplay. I am thinking use Flyweight pattern may be better to generate terrain.
We also can improve Perlin algorithm to improve performance: Implementing Improved Perlin Noise
And one more thing, a shader is different from a texture:

A shader is a type used for shading, the production of appropriate levels of light, darkness, and color in a rendered image.
A texture is an image, can be applied as a sort of "decal" to any polygon.

I mean to use a shader to calculate the final texture between pitch and overlay without ciclying the two textures pixel by pixel and moving that to GPU instead of CPU.
About the rest I'll check the solution you provide, they look very good.

Yep, your idea move Perlin algorithm to shader is great idea.
I will note here some reference:
[https://gist.github.com/patriciogonzalezvivo/670c22f3966e662d2f83](patriciogonzalezvivo GLSL)
[https://www.csee.umbc.edu/~olano/s2001c24/ch10c.pdf](University of Illinois)

Yep, your idea move Perlin algorithm to shader is great idea. I will note here some reference: patriciogonzalezvivo GLSL Perlin Noise University of Illinois Pixel Shader Perlin Noise

Hey there, i had a doubt regarding this game:
So, if i want to create a player, for example a football player with an overall rating of 999 or 1 million ovr, such that he scores from goal to goal and cannot be tackled and is incredibly fast, how would i do that in the game's sources code? How to change the player overall in the game's source code? Please tell me how do i do this, because this has always been my dream modification in a football game, sadly fifa does not allow me to make 1 million ovr players, but i hope this game allows me? Please help me out?


Instantiate instance when this is undefined

Fix #14

Coverage decreased (-1.0%) to 99.029% when pulling f81dfe305da26ce108f41ac8304e46d4f408f4e7 on feature/auto-instantiate into bc05cff6dd3d8592adfa566068a023c75ca0c07e on master.


reusing same sharp instance and differente options to toBuffer do not…

Reusing same sharp instance and differente options to toBuffer do not produce the same output.
Resolves this issue : https://github.com/lovell/sharp/issues/1855

Coverage increased (+0.0006%) to 99.756% when pulling f0fb2d40c9c2e95b4a2f0ce5fa21fcfbbd43208d on RaboliotTheGrey:fix/toBuffer/reuse-of-sharp-instance into 69fe21a7ec45df526461c4bf308332344112169a on lovell:master.

Merveilleux!


Would love to see your gcn code be part of the main repository. :)

Feel free to create pull-requests if you get a chance, and I can review and merge them.

Hi, great that this project spiked your interest. But this repo is ditched and not actively under maintenance now. We have a new repo: https://github.com/Xtra-Computing/G3. Please redirect the issue there so that my teammates can take a look as well.


Remove Sentry tracking on palomaswap localhost

Background
Describe the problem that we are trying to solve with this feature.
If a path to a solution is known, feel free to write it down, but have an open mind
We're sending errors from palomaswap localhost to Sentry which causes a lot of noise. For example this one https://volume-x3.sentry.io/issues/4020183998/?project=4504816371236864&query=is%3Aunresolved&referrer=issue-stream
Done when

[ ] we're no longer getting errors from locahost UI testing

told sentry server not to process.


it copys .git directory to remote when i use  sync local -> remote

Do you read the FAQ?
Yes.
Describe the bug
it copys .git directory to remote when i use  sync local -> remote, although i have set ignore,but other files or directories are ignored rightly.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Run command '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
just dont copy .git directory to remote
and by the way,i think it is very possiable clicking sync local ->remote and sync remote->local. Because i will edit code file both on local and remote.If i clicked wrongly,oh,it is horrible
Screenshots
If applicable, add screenshots to help explain your problem.

as you can see,it copyed .git, and build and asd.txt was not copied
Desktop (please complete the following information):

OS: [e.g. Mac, Win, Linux] win10
VSCode Version [e.g. 1.27.0] 1.56.2
Extension Version [e.g. 1.7.0] 1.12.9

Extension Logs from Startup - required

Open User Settings.

On Windows/Linux - File > Preferences > Settings
On macOS - Code > Preferences > Settings

Set sftp.debug to true and reload vscode.

Reproduce the problem, get the logs from View > Output > sftp.

my bad.it should be ".git",not ".git/".
but another thing,i suppose it will be solved.
i think it is very possiable clicking sync local ->remote and sync remote->local. Because i will edit code file both on local and remote.If i clicked wrongly,oh,it is horrible.
Thanks.


Add Intel eSPI protocol decode

Seems modern stuff is moving away from LPC to a quad SPI like protocol.

I think this is everything? Decodes my current test waveforms fully.


Remove docs to reduce image size

Resolves https://github.com/datagovsg/airflow-pipeline/issues/51

doesn't work, because as long as the docs are present in an intermediate image the docker tarball is still very large. I'm working on it. give me 5 mins to build and test


COMP 396 Fall 2016 - Othniel Cundangan - Course Work

Key additions:

Ace fix/patched Ace build
Popover
Saving
Codepen example

I could replicate your demo when reinstalling McLab-Web from scratch. However, the current version removes all other buttons for Mc2For and McVM.js. It was fine for the purpose of experimentation during the course but it is bad to ensure continuity of the project after you. Could you add back the other buttons so that the resulting project consist of everything that was there before plus your addition to the kind analysis?

Closing since another pull request was made


Feature/form validations

Add basic form validations for preprint form basics using ember-cp-validations.
These validations are:

Title: required, maximum length validator of 300 characters
Abstract: required, maximum length validator of 5000 characters
DOI: optional, but if entered, uses a regex to check if the DOI is valid

One thing to change in the future is only show the validation messages after the user has focused on the input field. That was something I had trouble with.

This PR has merge conflicts that will need to be addressed before it could be considered for inclusion.

Resolved merge conflicts

Just a few small comments to address, then this will be cleared for merge. Should be pretty quick to do in the AM.

Don't bake validations into the general validation component
Make a note of licensing terms where appropriate
The validation rules here are different from the OSF. If they are driven by our requirements that's ok, but if they're numbers picked out of a hit, please match them to rules used elsewhere.

Also, alas, travis is still failing. You can run tests locally using:
npm run check-style && ember test

Just one thing to tweak and then good to go.


[Feature] Redesign the Biography category page

Description
The category page for Biography does not look good and the components are not arranged properly.
I want to redesign the whole page by styling the components in appropriate way.
Also animations would be added to make the page visually appealing.
Please assign me the issue under gssoc.
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hey @rohansx I wanted to work on this issue..... please assign me this


Default to filtering out Webpack build artifacts

Adapted from @anilanar's comment at https://github.com/GoogleChrome/workbox/pull/808#discussion_r144999358:

I guess source-maps can be filtered out by default. However I'm not sure how that would affect development experience when testing offline caching. Need to test it.
This problem is similar to how loaders handle file inclusion/exclusion using three properties: {test, include, exclude} and the code for that is in https://github.com/webpack/webpack/blob/master/lib/ModuleFilenameHelpers.js, look for matchObject. That's what uglifyjs-webpack-plugin is also using in  https://github.com/webpack-contrib/uglifyjs-webpack-plugin/blob/master/src/index.js.
BTW the same can be used to filter chunks, that would allow a unified API for all kind of filtering and webpack users know how to use {test, include, exclude}.

Additional comments from @goldhand:

So considering we filter both chunkname and filename what should the api look like?
We could provide explicit chunk / filename filtering eg:
WorkboxPlugin({
  ...
  filterChunks: {
    test: /\.js($|\?)/i,
  },
  filterFilenames: {
    exclude: /\/excludes/,
  },
});

Or we can just filter both using the same properties, eg:
WorkboxPlugin({
  ...
  test: /\.js($|\?)/i,
  exclude: /\/excludes/,
});

and just filter both chunknames and filenames by those provided values?
Something else to consider is html-webpack-plugin's config the {chunks, excludeChunks} options are very nice. Maybe use those and apply the {test, include, exclude} options only to filenames (chunknames are handled by the chunks option...

Also need to be able to filter by file size based on the maximumFileSizeToCacheInBytes config option. Webpack assets have a size property so this should be pretty straight forward.

FYI, I've asked https://stackoverflow.com/questions/47658134 about whether it's possible/advisable to infer some sort of "how was this asset created/named" data from inside the plugin, as I think that would help a lot when it came to safely answering the "should this be versioned/cached?" question by default.
We'd still want to allow folks to override those default decisions, though.