Creating contact list

When I create a contact list, vmail searches for the Sent Mail folder, in my case it doesn't find it, I see the request on my browser as sent, I don't know if the folder was re-named or what is the issue.

Running vmail v2.9.11
I have the same issue, but I have gmail.com in English (US).
I have a "Sent" inbox which is named "Sent Mail" in the title header, and a "Trash" which is named "Bin" in the title header. But I am still getting this error message:
Unknown Mailbox: [Gmail]/["Sent Mail"] (Failure) (Net::IMAP::NoResponseError)
I have tried to set it manually in the .vmailrc to no avail.
mailbox_aliases:
  sent: ['Sent Mail']
  trash: [Bin]

Any idea how I can solve this issue? Clearly the "Sent Mail" isn't there even though in my gmail.com it is.
Is there a good way to find out about the labels my gmail is using, so that I can know for sure where the problem is coming from. The error message I suppose is the response from gmail API right? In that case it would mean the "Send Mail" just really does not exist, but when I look in gmail.com > Settings > [Labels] it shows me a inbox named "Sent" (under column System Labels). I have tried to set this in mailbox_aliases but still not working:
Unknown Mailbox: [Gmail]/["Sent"] (Failure) (Net::IMAP::NoResponseError)
Thanks.

I found the problem after digging into the code itself and debugging a little.
For some reason the contacts_extractor.rb file retrieves either the mailbox aliases from the .vmailrc file or it will use the one from vmail/defaults.rb. And this file causes the error because the IMAP doesn't like the value being parsed as ["Sent Mail"] instead it should be send as plain string like so: Sent Mail.
According to this (Wiki page) the .vmailrc should contain the following format:
mailbox_aliases:
  all: ['Alle Nachrichten']
  drafts: [Entwürfe]
  sent: [Gesendet]

Now the thing here is that I don't use german language in gmail I am using English (US).
So what should have worked for me would be:
mailbox_aliases:
  sent: ['Sent Mail']

However that was not the case, instead I have to fill it in like so:
mailbox_aliases:
  sent: Sent Mail

This solves the problem :+1:
I couldn't find anybody else with the same issue except for this created Issue, so I am wondering if I am the only one having this problem? If not then I think both the Wiki page and the code should be changed?


No results in company network with TLS interception

In our company we have a TLS interception.
Therefore mcs can't connect to the backend as of a certificate issue.
The result is just empty result, but no error is displayed.
How can the certificate truststore can be configured?
Setting it via -Djavax.net.ssl.trustStrore=company-ca.jks seems not to work.

Hi @frimtec, thanks for reporting this!

The result is just empty result, but no error is displayed.

Oh, that's not nice. It should at least give you a clue as to why it didn't work.

How can the certificate truststore can be configured?

I'll have to investigate. I distribute MCS as a native executable - it probably requires some fiddling to pass a custom truststore.

The latest early-access build should have this problem addressed - at least MCS should show you what went wrong. @frimtec, could you please verify that you get a meaningful error message with that build?

Hi @mthmulders
Thanks, not I see a error message:
frim@:/c/Develop/tools/mcs-0.3.2-SNAPSHOT-windows-x86_64/bin> ./mcs.exe search jpse
Searching for jpse...
java.net.ConnectException

Thanks for confirming, @frimtec. I've enhanced the display of the error message a bit.
For now, I will close this issue, as #199 at least ensures you'll get some kind of error message. In the meantime, I'll figure out how to work with custom trust stores - that work is tracked in #195. That will probably take a bit more time. I'll make sure to ship a release with this improvement in error handling shortly!

@all-contributors please add @frimtec for bug.


make docker-ci: improvements

[ ] 2. at times, there will be platform-dependent dependencies, and then it doesn't make sense to mount the whole repo (you'll need to make nuke deps build inside docker, and then once again outside docker, when finished). You might be good to go mounting the repo/.git folder instead of running git checkout . inside docker. This way, still have access to the whole git history, but you have a separate checkout instance
[ ] 3. proxy variables likes AWS_* or GH_TOKEN from the host to the docker container
[ ] 4. make docker-ci needs to be followed by a ./.ci.sh before_install to install required system dependencies, plus it can take a long time to create GIDs and do recursive chown, etc so ideally there would be a make docker-ci/scratch and make docker-ci where the latter would actually make use of an existing local image based on SF_DOCKER_CI_IMAGE + GIDs/etc + ./.ci.sh before_install

proxying variables and/or folders like ~/.aws and ~/.ssh shouldn't be done lightly, not automatically anyways

bootstrapping should also be left to the user

proxying variables and/or folders like ~/.aws and ~/.ssh shouldn't be done lightly, not automatically anyways

bootstrapping should also be left to the user


Rare Item search is item base specific

The searches for rare items aren't accurate in pricing for the mods. The problems stem from the cause that when you do search an item for pricing it includes the base type in the search criteria which restricts a wider search result.
Example:
I have a ring I want to price check (stats):
Paul Ring Base
+66 to Maximum Life
+56 to Total Resistance
+4-9 added fire damage
+20 to Maximum Mana
Now if I tried to search rings for 66 max life and 56 total resistance, the app will try to either search for those stats for all the items, in any slot, with those stats or higher or search for Paul Ring base in specific with those stats or higher. This makes that the result will not include other base types in rings and thus the predicted pricing would be inaccurate.

Hi, thanks for creating an issue. The item type (Paul Ring, Unset Ring, etc...) can be disabled but it will still search with the base item type (ring, gloves, etc..)

Item type active.

Item type not active by clicking on the item type.

item type settings to disable auto select.

I'll close this issue for now. Feel free to re-open if needed.


x/tools/gopls: remove double space in "func" snippets

I don't feel comfortable with this "func" snippet. it has 2 spaces before the opening curly brace

Maybe the "go" creators can change this🙏🏿🙏🏿

Thanks, this is a bug. We'll fix in the next patch release.

Sorry, looking at your screenshot again, I'm not sure this is a bug. It looks like there's a tabstop to write the result type.
Also, I don't think this is a gopls snippet. Looks like it may be a VS Code snippet?

Closing this as WAI, since this isn't actionable for gopls.

yes, it's in vscode. sorry, looks like it's a go extension error in vscode


Fix debian cri o install

Pull Request (PR) description

Remove obsolete path fixes that don't exist in any version of crio packages I can find
Remove conditionals around long-obsolete/unsupported versions
Allow use of the deprecated kubic repos, default to official k8s packages

This Pull Request (PR) fixes the following issues
Fixes #77
Fixes #47 (for Ubuntu)
Some comments
I included the ability to use the kubic repos for existing implementations (with a value change) based on this comment https://github.com/voxpupuli/puppet-k8s/issues/77#issuecomment-1902675050 however given the number of changes around k8s repos since 1.28 I personally think it would be better to make a major version cut and simply say that it drops support for the kubic repos which are deprecated IMHO YMMV
Obviously this PR only addresses Debian. I didn't want to invest the time until we have some consensus on the approach, at which time I'll update the PR to fix the repos for all platforms.

thanks for the PR, can you add some unit tests to verify the new behaviour?

The k8s::install::cni_plugins code will probably need updating as well, the k8s repo looks to be calling the package kubernetes-cni

Superseded by #103


Default content-type being set with 'json: true' breaks code

With 2.63.0 and https://github.com/request/request/pull/1772, request re-introduces subtle breaking behavior. It is considered bad HTTP to send content-types with requests without a body. For example, I just had breaking behavior where I use HMAC authentication to sign API requests and then send that signature with request. Since the content-type is included in the signature and now I get a content-type that wasn't expected, I get signatures that don't match and everything goes kaboom... I can code around it, but I don't think I should have too.
I also am pretty sure this is actually a regression. I don't have time to do the bug search right now, but years ago, I remember this broke against things like express (in like the 2.x days) where a content-type that was sent without a body would result in an error. While it was also an express bug, it was determined that setting a content-type without a body was bad form. If you need that behavior, it should be opt in, not the default where these headers matter. While the docs seem to imply it, it  seems much more like a doc bug than anything.
Either way, changes to the default behavior or headers is a big enough change that it needs to done with a bit more caution, perhaps even a major version bump. I would vote for reverting that change, as I think it will probably break for a lot more people.

I also dealt with this issue today. 2.63.0 is marked as compatible with 2.44.0. In my case, not true, this broke for me.

If this is the preferred behavior, we might want a test to ensure there is no content-type when a request has no body.

I can't find anywhere in the spec explicitly stated that requests without body, are not allowed to have a content-type set. On the other hand I can agree that it doesn't make sense to have a content-type without having a body.
The problem here comes from the json option itself. Either @jzaefferer should set its content-type header, or @addisonj should set the accept header and parse the response instead of using the json option.
Since this happens to be a breaking change, I'm more on the reverting it side + fixing the docs and adding a test. @jzaefferer thoughts?

I'm okay with a revert; I'll just revert my project's upgrade commit as well. As long as the docs are more clear about this than before.

+1 to the list of people who had their code broken :)

Fixed here https://github.com/request/request/pull/1785 I wasn't able to fix the docs though.
In fact they are totally correct as they are, except that the json:true case is completely missing. If you can figure out a good and short way to explain the behavior contained in the json function let me know in the other issue.

2.64 is published :tada:


gitignored build directory

Fixes #168
This will ensure that the build folder is no more included in this github repository

Thanks for the contribution ^_^ . Do check out other issues as well !

Thank you! And sure, I will :)


[SPARK-38687][SQL] Use error classes in the compilation errors of generators

What changes were proposed in this pull request?
Migrate the following errors in QueryCompilationErrors onto use error classes:

nestedGeneratorError => UNSUPPORTED_GENERATOR.NESTED_IN_EXPRESSIONS
moreThanOneGeneratorError => UNSUPPORTED_GENERATOR.MULTI_GENERATOR
generatorOutsideSelectError => UNSUPPORTED_GENERATOR.OUTSIDE_SELECT
generatorNotExpectedError => UNSUPPORTED_GENERATOR.NOT_GENERATOR

Why are the changes needed?
Porting compilation errors of generator to new error framework, improve test coverage, and document expected error messages in tests.
Does this PR introduce any user-facing change?
No
How was this patch tested?
By running new test:
$ build/sbt "sql/testOnly *QueryCompilationErrorsSuite*"

Can one of the admins verify this patch?

ping @MaxGekk

@panbingkun Could you backport the changes to branch-3.3, please.

@panbingkun Could you backport the changes to branch-3.3, please.

ok, i will do it.


Update version in setup.py

Codecov Report

Merging #67 (cb56c7a) into dev/main (79de586) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           dev/main      #67   +/-   ##
=========================================
  Coverage     85.29%   85.29%
=========================================
  Files            54       54
  Lines          1489     1489
=========================================
  Hits           1270     1270
  Misses          219      219

Flag
Coverage Δ

cpu
85.29% <ø> (ø)

pytest
85.29% <ø> (ø)

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

Continue to review full report at Codecov.

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


Make sure workers retry deadline errors, and retry forever generally

What was changed
Workers should really just retry everything (retryable) forever, where right now they'd error out after 10 seconds of being disconnected. Now I apply a special retry config for workers so they'll retry forever, and are allowed to retry gRPC deadline problems. They still set a deadline to avoid getting hung on one call indefinitely.
Why?
Robustness
Checklist

Closes

How was this tested:
New UT. Can't test specific scenario user reported b/c of Tonic internals, but it's not exactly complex.

Any docs updates needed?

Will take a different approach - makes more sense to just drop these rather than retrying forever.


Issue: Refactor API Errors

Overview
Related Issue: #112
This PR simply refactors the response error handling logic contained in wallet/api_errors.
It introduces the Coinbase::Wallet::StatusHandler, which is responsible for checking and handling API errors based on the response status as well as the Coinbase::Wallet::APILogger  which houses logging logic.
The Client and Server error classes along with their respective subclasses are defined in wallet/api_errors

Hey @mufudzimasaire, thanks for the pull request!
One small question about your CLIENT_ERRORS hash, but otherwise this looks great.


Schnorr signatures spec and reference code

This PR adds a spec for our schnorr signature scheme and a reference python implementation.

Documentation and RFCs should be separate, RFCs correspond to a proposal
and are often different from what the code actually does, documentation
should reflect the protocol as actually implemented.
On Thu, May 9, 2019, 1:24 PM rebekah mercer<EMAIL_ADDRESS>wrote:

@rbkhmrcr commented on this pull request.
In docs/specs/signatures/description.markdown
https://github.com/CodaProtocol/coda/pull/2364#discussion_r282650941:

+-   Let R = sG - eP.

+-   Fail if infinite(R) or y(R) is not even or x(R) ≠ r.

+#### Signing

+Input:

+-   The secret key d: an integer in the range 1..n-1.
+-   The message m: an arbitrary length tryte array.

+To sign m for public key dG:

+-   Let k' = int(blake2s(bytes(d) || m)) mod n[^8].
+-   Fail if k' = 0.
+-   Let R = k'G.
+-   Let ''k = k' '' if y(R) is even 1, otherwise let ''k = n - k'
is is even 1 a typo? if not I'm not sure what you mean here
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CodaProtocol/coda/pull/2364#pullrequestreview-235805083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPATPJ5UJRTF4SEDCBMADPUSB6VANCNFSM4HJZWXUA
.


Feature request: configure fixint at the container level

Maybe this is possible already and my weak Rust is the only thing stopping me, but I'm wanting to basically always use the fixint option, and the with attribute is going to be half my codebase at this point :<
If the other side of my service wasn't a completely different language I'd prefer varint, but for now I'd rather opt out altogether if possible.

I gave it a shot :)
https://github.com/jamesmunns/postcard/pull/96

This would be a great feature, I'm also in a scenario where I need to apply fixint to every single int type for a particular struct that I'm serializing. It would be so much easier if you could either apply the with at the struct level, or just at the container level. I hope they get to this, or accept your feature PR :)

Need this exact feature :(


xcode 9 install

Changes
Adds Xcode 9 in provision-osx role.
Verification steps

Run  the installer targeting a mac machine using the "osx_install_xcode" tag
Ssh into the machine and check the /Applications folder, it should contain a Xcode-9.app application folder

Good thing that default version is handled automatically :)

xcode_default_version: "{{ xcode_versions[0] }}"


Comparing two selected files should not open in "preview" mode

When you select two files in the explorer and compare them to each other, it shouldn't be so easy to lose that comparison view.  Comparing is an explicit action and the editor should open in non-preview mode so it doesn't get closed, forcing the user to go reselect the same files and compare them again.

This has been implemented in our current release.

@bpasero, is there setting to bring preview back for comparing files?


How to increase the output throughput for inserting the records

Currently i am inserting 191277 records in database. My source is csv
I am using 12 workers and 6000 batch size.
My input completes in 2-3 minutes and filter operation get stuck, and event after 1 hr the output is as below. ( 2158)
How can i make sure i increase my output throughput. Any suggestion
I have tried various options like below, but no improvement
max_pool_size => 50
connection_timeout => 100000
This below i get from monitoring API
"events" : {
    "in" : 191277,
    "filtered" : 68630,
    "out" : 2158,
    "duration_in_millis" : 5406886,
    "queue_push_duration_in_millis" : 79073
  }

Check your logs to see if you’re getting backed up because of an sql exception being retried.
Bear in mind your connection timeout should not exceed the sql servers timeout.

Thanks for your reply. I tried this.
But i didnt see any warning /error or anything like sql exception in the log.
It just that it get choked at output level.
On connection timeout i kept less that the sql server timeout. With this slight improvement but not drastic
Earlier every second it was loading in batches of 11, now it is loading in batches of 20 and sometime 30-35. So thats the improvement i see.
But here i am trying to load in batches of 6000, which is not going through
Do you have any benchmarks for uploading huge dataset/ some numbers as how much time it takes to flush the output data.
If benchmarks on performance are available, that will give me confidence to invest more time to come up with right configuration for this plugin
Thanks

I’ve found performance varies between drivers, java versions, the work being done, logstash version, etc.
I have no benchmark numbers available specifically for MySQL, but I can tell you anecdotally I’ve had it running reading input from
files and syslog and outputting to MSSQL for months at a time, dealing with millions of rows with no backlog. I have done large batch jobs of many tens of thousands of rows to back fill data again with no backlog. But again it’s MSSQL and I know my environment and it’s tweaked accordingly. I have not tested it with logstash 6.2 or newer as I am in the process of retiring the system and reason this plugin was written for in the first place.
Sent from my iPhone

On 3 Jul 2019, at 19:56, rkhapre<EMAIL_ADDRESS>wrote:
Thanks for your reply. I tried this.
But i didnt see any warning /error or anything like sql exception in the log.
It just that it get choked at output level.
On connection timeout i kept less that the sql server timeout. With this slight improvement but not drastic
Earlier every second it was loading in batches of 11, now it is loading in batches of 20 and sometime 30-35. So thats the improvement i see.
But here i am trying to load in batches of 6000, which is not going through
Do you have any benchmarks for uploading huge dataset/ some numbers as how much time it takes to flush the output data.
If benchmarks on performance are available, that will give me confidence to invest more time to come up with right configuration for this plugin
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I am using 6.8, you mean you will not be continuing to maintain this plugin going forward.?
That's very sad.
I think there is a possibility that it is slow because of 6.8 version

The intention is to maintain the plugin as best as I can, but I cannot keep up with elastic's release schedule. I will have the system I'm using it for in place for at least another year, but it's marked as legacy. It's not something I can dedicate enough time in the evenings or weekends at the moment.
I'm happy for others to step in as co-maintainers. Plenty of people fork the repo, some add features, but very few send any PRs. The majority of the work is helping people with their specific setup via email, and very often it's simply configuration mistakes (which could probably be solved by better documentation and tests, but again I'm finding it hard to make time for it).

I just imported 500,000 rows  from one mysql instance to another , which took around 55 minutes, which seems not bad as compare with the result of @rkhapre.
I am just use the default performance settings, while the logstash version is 6.8 as well,  and the mysql version is 8.0. just for your reference.


DO NOT MERGE! Fast Forward stable to 569423d24e2d0cb1c6db812297fec5cf88088bf2.

This PR will be merged automatically once checks are successful.

This change is

Jenkins job mixer/postsubmit passed


Enhancements needed for the Diagnostic page

Is your feature request related to a problem? Please describe.
Enhancements needed for the Diagnostic page

Title - Diagnostics is vague and from users' pov, it isn't clear what is this page for. Could we add in something more appropriate since its for UI diagnostics?

Download data button --> It isn't intuitive, what data is going to get downloaded. Everything from the page? or just the log?

Logs and Resource Counts --> These sections must have more info on what logs (Rancher logs or downstream clusters' logs or in this case logs from the browser ) are these and what resources are there (local cluster? or downstream cluster?)

There are resources that have 0 count. can we not display these ?

Additional context
Related to this feature - https://github.com/rancher/dashboard/issues/6544

@kwwii can we take a look at this when we adjust the styling of this page and the about page? Thanks 🙏

Here's a mockup:

Hi @jordojordo , as discussed with @nwmac I am passing this one you. Thanks! 🙏 🙇

@jordojordo We can discuss

Specifically:

Move the latest logs to the bottom
Compact the System Information table into 3 groups, use name/values with the table for each group

Browser
System
Javascript Memory

Resource counts - should collapsed by default when more than one cluster

Label - Resource counts by cluster
Ignore counts when they are 0
When collapsed show the following info in the bar - Total resource, Total number of nodes,

Allow timings to be shown on screen and for each cluster

Add a button 'Generate Diagnostic Data' which will go through each cluster, capture timing and add it to the table add another column, use '-' for those we did not time

Add dialog when users downloads if they have not run the timings against to let them know if they want them, they should use the other button first.

Validated this issue on v2.7-9f1e0435bb45e104ba897c5c329e1f23735843d9-head
Browsers : Chrome and Firefox
Observation 1: On Diagnostic page : The button name should be 'Generate Diagnostic Data' from the requirement?
Steps :

Login to rancher
Navigate to 'About' Page
Click on Diagnostics page
Check for the button with name  'Generate Diagnostic Data'

Actual:

Not seeing the button with name : 'Generate Diagnostic Data'; User seeing the button name as 'Generate Response Times'

Observation 2: Cluster Name is NOT showing for all cluster types (Displaying the cluster ID)
Steps:

Login to rancher
Navigate to 'About' Page
Click on Diagnostics page
Check for the Clusters Name associated to the user

Actual:

Clusters list is displaying properly but the cluster name is not displaying properly (It is displaying the cluster ID) for some of the clusters and some of the cluster types it is displaying correct name
Only RKE2 clusters are showing  the correct cluster names
RKE, EKS, GKE, AKS clusters are NOT showing the cluster names (Displaying cluster IDs)

Note :
a. I am seeing same information is displaying with v2.6.8

Observation 3: Firefox browser: System Information is not populating all the information
Steps:

Login to rancher
Navigate to 'About' Page
Click on Diagnostics page
Check for the System Information

Actual:

System Information table missing below fields
a. System :  OS: macOS, Device Memory: 8
b. Complete row : 'Javascript Memory Heap Size limit:<PHONE_NUMBER>, Total Heap Size: 77133756, Used Heap Size: 70122148'
Seeing this information on Chrome
Screens attached from Chrome and FireFox

Note :
a. I checked the Javascript enabled flag set to true on my firefox but the full information is not displaying on Firefox
b. I am seeing same information is displaying with v2.6.8

Missing JavaScript and Memory details on FireFox.

Validations Completed and looks good.
Rancher Ver:  v2.7-9f1e0435bb45e104ba897c5c329e1f23735843d9-head
Validated this card:

Admin & Standard user
Chrome & Firfox
All cluster types
Standard and Dark mode view


Add Wraith tests to travis-ci

We should be able to setup wraith to this repo to verify changes.

Instead of generating a snapshot for the large visual-index.html page, it would be cool if you could generate a separate snapshots for each component/feature from the KSS documentation. This would make it so that image diffs are a lot more useful since they would pinpoint which component was changed.
That would keep the KSS commnets, image snapshots, and the generated documentation all in step.
THIS IS THE HOLY GRAIL.


It's possible integrate remark auth with existing website users (django)?

I have some simple django site with existing users. Can't understand how integrate remark42 with existing django auth. It's possible? And I ask advice for best way to do it.
Продублирую по русски, чтобы более понятно. Есть сайт на django с авторизацией с неким кол-вом пользователей. Возможно ли как то использовать remark в качестве комментов, чтобы уже залогиненные пользователи уже автоматически логинились и в ремарке?

remark42 authentication is "social" only, i.e. oauth2 with google, fb, github and yandex. There is no support for custom auth.
Theoretically, it should be possible to write auth implementation on top of anything as long as this "anything" acts as oauth2 server.
Another way is to implement special case (custom) auth, in the way similar to basic authentication it's doing now in dev mode.

That's already work in progress. I'm dealing with externalizing auth module and this change would help to add more auth providers much easier.

@umputun Great!

re: #363


Integrate new PT routing algorithm

Encompasses all changes involved in integrating the new transit routing algorithm Michael has been working on. High-level breakdown of changes:

Point our GH dependency to the latest commit in the branch Michael's created for developing the new algo
Updates test configs to include new necessary fields for "turning on" the new algo, and updates unit tests accordingly, as the new algo results in slightly different transit route responses
Updates several spots in custom Replica-specific code to use the new PtRouterTripBasedImpl, necessary for the new algo to actually get used in route responses
Many small changes (especially in CustomOsmReader) simply to catch up code we've copy/pasted from GH master with the newer GH master version Michael's built his branch off of

This is the main branch we've been testing off of, so the conclusions about performance/quality we've laid out in the #prj-new-transit-algorithm slack channel cover the basics of how this new algo performs in production settings.

Thanks for the quick review @bryanwilliams1025 , and great questions!

No changes yet on the status of Michael's branch, but it's not something we're going to wait long on. I just pushed the issue here so hopefully we get clarity soon; a fast-follow PR will be put up right away once Michael's main branch has been merged
Yes, the model-side PR is almost ready, I'm just finishing cleanup there. Good point that staggering the merges too much could lead to trouble; I'm happy to get them both to ✅ and then merging in fast succession to minimize issues! I should have the other PR ready for review ~EOD today

One other side note - I had a realization that the new GTFS validator image I created doesn't actually use the new PT algo, because we hadn't set the proper flag + set up a mechanism for exact GTFS schedule days to be passed into the GH config used for validation. I just pushed the fix with db65db1, and will build a new validator image + add/test the matching model repo-side logic before I merge this PR

Phew, at long last, I figured out the weird java update/guice/etc issue! At the end of the day, all that was needed was:

bumping guice to the latest version, 7.0.0
adding a new dep for jakarta.inject-api (the error I had after bumping guice was related to jakarta classes not being found)
bumping guava to the latest version, so it didn't clash with the bumped versions of ^

I built a MNC router via arti using the image resulting from the latest commit on this branch, and spun it up for testing - the GUI worked as-expected and there were no errors in the logs 🎉


Aligned the all-in-one with the production template

Split from #8 . Change to the example: https://github.com/objectiser/opentracing-prometheus-example/pull/8


Add support for simple "ping" (root resource)

This PR adds support for fetching the Elasticsearch root resource (with node name, cluster name, and version information) as a sort of "ping" request, which always succeeds (unless the Elasticsearch node is unavailable).

Changes Unknown when pulling f267dab9439f5abae5961b64544818521f597e35 on graylog-labs:ping into ** on searchbox-io:master**.

@ferhatsb Is anything missing or has to be changed before this can be merged?

too busy I guess, well merged.


librealsense: 2.54.2 -> 2.55.1

Description of changes
Diff: https://github.com/IntelRealSense/librealsense/compare/v2.54.2...v2.55.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 335488 run on x86_64-linux 1

17 packages built:

envision
librealsense (librealsenseWithoutCuda)
librealsense-gui
librealsense-gui.dev
librealsense.dev (librealsenseWithoutCuda.dev)
librealsenseWithCuda
librealsenseWithCuda.dev
monado
opencomposite-helper
python311Packages.pyrealsense2 (python311Packages.pyrealsense2WithoutCuda)
python311Packages.pyrealsense2.dev (python311Packages.pyrealsense2WithoutCuda.dev)
python311Packages.pyrealsense2WithCuda
python311Packages.pyrealsense2WithCuda.dev
python312Packages.pyrealsense2 (python312Packages.pyrealsense2WithoutCuda)
python312Packages.pyrealsense2.dev (python312Packages.pyrealsense2WithoutCuda.dev)
python312Packages.pyrealsense2WithCuda
python312Packages.pyrealsense2WithCuda.dev


Hostpath should work for bare metal providers.

The official solution is using Local PV. https://kubernetes.io/docs/concepts/storage/volumes/#local. Based on my conversation with msau42 in Slack:

When is this going beta? We can't use alpha features.
Beta will be 1.10 at the earliest
I am working on the missing scheduler piece for 1.9
so depending if I can get it in time, then 1.10 would be the earliest for beta

Does Local PV work with host paths like HostPath PV? or Do we need to pre-mount disks?
You can create a Local PV as a shared directory
but the capacity reporting won't be accurate, and you won't get capacity isolation

Can this be used with SS as a VolumeClaimTemplate?
Yes
it does not support dynamic provisioning yet though
so you need to precreate your PVs with the same storageclass name that you specify in the volume claim template

When is that support planned?
I'm guessing 1.11

This issue was moved to kubedb/project#63


must anchor the transcript to video timestamps

Now the output just shows something like this
<Transcript text="Hello, this is Jim Lehrer with the NewsHour on PBS."/>

And for full Kaldi output we also get a bunch of timeframes:
<TimeFrame start="12920" end="13010" frameType="speech"/>
<TimeFrame start="13010" end="14760" frameType="speech"/>
<TimeFrame start="19860" end="20040" frameType="speech"/>

But these timeframes are not connected to any text sequences (basically because they were found for the wrong reason and the script assumes they are significant like the output of the segmenter).
Instead, we need something like
<Transcript>

</Transcript>

Want to introduce an option that governs the granularity at which we link, above it is sentences, but if we have no information on that we degrade to the token level (if we have no results from fastpunct and spaCy), and we we don't have that either we cannot give any alignments and we end up with
<Transcript>

</Transcript>

For the JSON default we want to make it look like this
"transcript": [
    [
      "Hello, this is Jim Lehrer with the NewsHour on PBS.",
      5500,
      11467
    ],
    [
      "We have exciting news about the tomato & Florida.",
      12345,
      18987
    ]
  ]

Much of this is done in e02c422, but:

more testing is needed
there is no fallback in case there are no alignments
the code is not explicitly set up to deal with results of forced alignment


add support for knock command

Description
Add new command for knocking
Summary:
Jane (large prospect) is having some issues with their patients not realizing they need to Knock to gain entry to a room.
We've added this command as a method for them to "auto knock" on behalf of the local user.
Note: This is on the surface the same as user clicking the knock button, however it does not take a screenshot of the user.
Related Issue:
Dependent on PWA PR here:
https://github.com/whereby/pwa/pull/4187
Testing
In the pre-built UI stories, add this button to the code that is returned:
<button onClick={() => { elmRef.current?.knock()}}>Knock</button>
Screenshots/GIFs (if applicable)

Checklist

[ ] My code follows the project's coding standards.
[ ] Prefixed the PR title and commit messages with the service or package name
[ ] I have written unit tests (if applicable).
[ ] I have updated the documentation (if applicable).
[ ] By submitting this pull request, I confirm that my contribution is made
under the terms of the MIT license.

Additional Information

Nice. Should probably add a changeset for this though


Switch position of two headings in README.

"Defining flat menus in the CMS" is now the second entry in the "Using wagtailmenus" section, while "Using the {% main_menu %} tag" is now the third.

@marty thank you! Apologies for the slow response. Busy with lots of client work on at the moment.

You're welcome


Is there any way to disable collisions from ros?

Hi @JenniferBuehler
I have been looking for a way to disable collisions or physics in gazebo in order to simulate drilling holes in a piece. I would like to be able to do this from python. But I haven't seen a solution.
Do you know if there is a way for do this?
Regards
David

Hi David,
You could always create models without collision shapes, e.g. a wooden plank without a collision shape (only visual shape). However this has to be a static object then, otherwise it will just fall through the ground. Also, other obstacles which you may put on it will fall through then. Unless you make a hole into the collision shape where the robot is expected to drill (if that's a fixed spot). If I remember correctly, simulated laser scanners will also only see the collision shapes, but of that I'm currently not sure, would have to look it up / try out.
A dirty trick would be to make the object part of the robot with disabled self collisions.
So it depends on your setup. What exactly are you trying to do?

Hi, thanks for answering so fast.
I have tried to use an STL with the hole for the collision object and it seems to work. But the grasping plugin now fails a lot and it doesn't attach the piece to the gripper (sometimes It works, but only a few). Can it be related to using a mesh?

Hm, it could be related, was it a cube/sphere before? Mesh mesh collisions are generally a bit trickier/bugger, but it shouldn't be sooo bad as to fail that often.
If it's a cube you're talking about, you could build the collision shape out of 4 cubes (leaving space in the middle) maybe? Would be worth a try at least to find out if that was the issue

The piece is a cube. I have been changing values in the plugin, hopping to improve the results, but I haven't reached anything.
Hmm, you give me an idea. Maybe creating a thin cover for the mesh it should work. I'm gonna try it

Well, making a sandwich works jajaj. It's a dirty trick, but I don't see any other solution. Here is the result

Thank you very much Jen

Awesome, glad it worked!
I'll close this, if you have other questions please feel free to open a new issue or reopen this.
Good luck with your project!


Add latest firmware 1.3.254 [Spark/Runner2]

Signed-off-by: Stefan Naewe<EMAIL_ADDRESS>

Thanks Stefan!


[FEA] GpuFilterExec should report gpuOpTime not totalTime

Is your feature request related to a problem? Please describe.
See #2334 for the motivation for this. This issue is to update GpuFilterExec to report its current metric as gpuOpTime instead of totalTime, since the current metric is purely the cost of applying the filter on the GPU and does not include any costs of executing or fetching data from child operators.
Describe the solution you'd like
Report gpuOpTime instead of totalTime.
Describe alternatives you've considered
None
Additional context
None

Merged with https://github.com/NVIDIA/spark-rapids/issues/2461


feat: librarySearch

This adds a simple version of the librarySearch tactic from mathlib.

The implementation uses discrimination trees, with the hope of better scalability.
A new cache data structure is introduced to simplify the caching of such indexing data structures.

Some todos:

There is no "try this" yet.  I'm waiting for code actions to land in Lean 4.
It only does reducible matching for now.  I hope that I'll be able to abuse the discrimination trees to do indexing for semireducible matching as well.
Iff.mp, etc. projections are not implemented yet.

A question --- when we're porting tactics across from mathlib3, what should we do with tests?

You're probably right and in general we should copy them to mathlib4.  At least for the port it's important that the tactics do roughly the same thing as in Lean 3.  librarySearch is a bit of a special case though since it isn't used in mathlib, so it doesn't matter if the Lean 4 version does something different.  Though it shouldn't become less powerful of course.
I've now copied over the library_search/basic.lean file from mathlib.  Some failures:

There are some lemmas which we don't have in mathlib4 yet.
Projections (Iff.mp, And.left, etc.) are not implemented yet.
There are some differences with how intro is applied.


[Request] No Network Connection Notification

Also, I think a new feature to add a notification if network errors occur would be a good idea. It would help others figure out if the wallet is not loading balance for that reason.
Originally posted by @mteam88 in https://github.com/PIVX-Labs/MyPIVXWallet/issues/14#issuecomment-1019294452

Pull request


No such module 'VisualRecognitionV3'

mac:visual-recognition-coreml ydh$ carthage update --platform iOS
*** Fetching swift-sdk
*** Checking out Starscream at "31f522155a4d6323cd1aaefb8dbc140ced7be1ca"
*** Checking out swift-sdk at "v0.23.3"
*** xcodebuild output can be found in /var/folders/l7/d1pnsddn4wd3z6qry0tp5rvh0000gn/T/carthage-xcodebuild.qn8wTM.log
*** Downloading swift-sdk.framework binary at "v0.23.3"
*** Building scheme "Starscream" in Starscream.xcodeproj
mac:visual-recognition-coreml ydh$
Is the above update result wrong?
https://github.com/watson-developer-cloud/swift-sdk/blob/master/docs/quickstart.md
According to this tutorial, but this result has appeared
import VisualRecognitionV3
No such module 'VisualRecognitionV3'

I solved this problem. I did not follow the tutorial. According to the tutorial, I always failed.
My solution:
I put the VisualRecognitionV3.framework in the project root and add it to the project


feat: allow deployment of development builds

Closes CLM-10089
This change allows users to pass a -d/-debug flag when running helium deploy/npm run deploy in order to deploy a development build to assist troubleshooting efforts.
In order to do so, users will need to a .env.development file with NODE_ENV='development'.

@chrisvariety This is the only one. At the moment, I've left the NODE_ENV for the CF worker as 'production'
https://github.com/thoughtindustries/iron-workers/blob/8cbc4a0cee7f1e6a50d691777a2ad8cacf493254/helium-deployer/entrypoint.sh#L78
As that affects whether or not we include the persisted query link w/ GraphQL requests:
https://github.com/thoughtindustries/helium/blob/888ed632165665c2dc72ba265811c0ca12b83b78/tooling/helium-server/worker/init-page-context.js#L52-L58


[v2-rc9] $inc for nested key doesn't work

The below code was working fine before I upgraded to rc9, I had a cloned copy from rc8. Any idea why it stopped working in the latest rc?
SomeCollection.update({_id: this.userId}, {$inc: {'stats.some_count': 1}});

Hmm strange. I haven't been playing with this at all. Maybe you have changed something in your code? If not then please create simple reproduction.

If you try incrementing any nested key using the Astro Class .update it returns 1 but doesn't actually make any update in the db. It works fine if the same query is performed using Meteor.collection.

Hmm I don't know if it has anything to do with Minimongo but I will have to check it. I know there was a problem with @inc operator but I've fixed it but using some internal Minimongo methods. So maybe in the update they removed something. I will try to check it today or tomorrow.

In deed it's a bug, but I'm 100% sure that it used to work. I will try fixing it

Ok bug fixed, 2.0 is very very close :)


Question: Interactive Transition?

Does this router support interactive transitions?
Successfully presenting the next view controller always works of course, but is there a way to handle cancelling the transition so the router won't think it's made it to the next routable when it really has not?

@kevinfez Currently there's no support for cancellation. Though in theory it shouldn't be too hard to implement. We already have a completionHandler that is passed in order to asynchronously update the router once an animated transition is completed. What is missing is an equivalent cancellation handler.
I can't make any promises on whether this will be implemented or not, but I'll keep this issue open since it's a good suggestions. PRs are also always welcome!


Use same auth for Dataproc + GCS

resolves CT-861 (just opened)
Try using the same authentication methods for Dataproc + GCS that we're using for BigQuery, so we don't need to rely on the GOOGLE_APPLICATION_CREDENTIALS env var being set.
I still haven't been able to get this running on my local machine, unfortunately. job_client.submit_job_as_operation returns:
501 Received http2 header with status: 404

@jtcohen6  I updated the code a bit and tested locally, everything works well


Implement JsonParserGenerator using smithy-json

More progress towards #161. This PR implements JSON deserialization codegen using the new smithy-json token streaming parser. Cleaning up the old Serde implementation is going to be a separate PR as it's going to require more refactoring.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

And seems like deserializeFunctionName is generating an extra _ when called on lists which is causing CI to fail

It looks like this is actually because MediaPackage has names such as com.amazonaws.mediapackage#__mapOf__string. I think we just need to suppress this warning.

Did some crude benchmarking to get a rough idea of how these changes impact performance. Note: this isn't a completely fair comparison right now because the smithy-json version is still using serde to parse errors (that part hasn't been refactored as part of this PR).
Repeating json-rpc10, json-rpc11, rest-json, and rest-json-extras protocol tests 100x in release mode (wall-clock time):
smithy-json: 42.354 seconds
serde-json:  44.656 seconds

Dynamo release build time including dependencies (wall-clock time):
smithy-json: 1m 36s
serde-json:  1m 29s

Running cargo llvm-lines:
smithy-json: 528,876
serde-json:  760,254

I want to see the same comparisons after refactoring the error parsing, and also want to add a real-world Dynamo GetItem comparison.

big +1 to both of those! I would make the integration test gradle job slightly smarter and allow us to add a benches folder. We can eventually even run these benchmarks in CI. I'd also be curious about absolute numbers for serialization

Added a DynamoDB benchmark in #507. I went ahead and ran it against both main and this PR (after running ./gradlew :aws:sdk:assemble for each), and the results are not that different:
main:
ser_deser_bench         time:   [224.39 us 226.10 us 228.14 us]
Found 5 outliers among 100 measurements (5.00%)
  3 (3.00%) high mild
  2 (2.00%) high severe

PR:
ser_deser_bench         time:   [226.49 us 227.60 us 228.89 us]
                        change: [-0.2383% +0.5420% +1.3489%] (p = 0.19 > 0.05)
                        No change in performance detected.
Found 6 outliers among 100 measurements (6.00%)
  4 (4.00%) high mild
  2 (2.00%) high severe

I'm not fully convinced this benchmark is giving me the information I want, but it does corroborate the earlier wall-clock time that wasn't really showing much of a difference.
If we want to add benches to CI later, we probably want to use lai instead of criterion since that will measure instructions and memory accesses rather than time.

Did some more benchmarking since simplifying the benchmarks in #507. It looks like performance is in the same ball park after this PR.
main:
deserialization_bench   time:   [12.200 us 12.701 us 13.262 us]
deserialization_bench   time:   [10.637 us 11.046 us 11.456 us]
deserialization_bench   time:   [8.4684 us 8.5261 us 8.5913 us]
deserialization_bench   time:   [8.1389 us 8.2168 us 8.3122 us]

PR:
deserialization_bench   time:   [11.877 us 11.980 us 12.097 us]
deserialization_bench   time:   [11.694 us 11.765 us 11.846 us]
deserialization_bench   time:   [11.302 us 11.402 us 11.516 us]
deserialization_bench   time:   [11.235 us 11.299 us 11.369 us]

It looks like there may be some opportunity for improvement, but we're on the order of a 0-4 microsecond difference. The consistency of measurements of the PR version vs. what's in main is interesting.


Doc types

Documentation of Vertex, Edge and Point added.
They can be linked using :obj:`pyrigi.data_type.Vertex` in general, but setting
autodoc_type_aliases = {
    "Vertex": ":obj:`pyrigi.data_type.Vertex`",
    "Edge": "Edge",
    "Point": "Point",
    }

in conf.py does not create the link correctly. So I propose we just keep it without linking.

wrong branch... sorry


Do not fail if tag already exists

Useful when multiple charts are released manually at once one of which has already been released before.

We should not force push tags actually. Release tags are required to be immutable.


SYNTH-4156 Fix NPE during QUIT

Occasionally driver.quit encounters an error but the logic that
constructs the error message in turn encounters an NPE and as a result
we are unable to know what exactly went wrong. This commit fixes the bug
in the error message construction and hopefully help us identify the
underlying issue.
Testing notes:

Ran @sanity on Chrome with these changes.

This looks good but is it necessary to have the intelliJ project files in the commit?

@skilcoin my bad. I accidentally added the .idea files. Have fixed by doing a force push. Please take another look


add/append file to exiting packaged meta

This allows to add files and dirs (packed as tarfile)  to a packaged environment.
The workflow is:

# pack the env itself
empack pack env \
     --env-prefix /some/env  \
     --outdir outdir

# pack directory
empack pack dir \
    --host-dir /the/extra/dir \
    --mount-dir /dir/in/virtual/filesystem \
    --outname extra_dir.tar.gz \
    --outdir outdir

# include the extra directory in the packed env
empack pack append \
   --env-meta outdir    \
   --tarfile outdir/extra_dir.tar.gz

# pack an extra file
empack pack file \
    --host-file /the/extra/file.png \
    --mount-dir /dir/in/virtual/filesystem \
    --outname file_png.tar.gz \
    --outdir outdir

# include the extra dir in the packed env
empack pack append \
   --env-meta outdir    \
   --tarfile outdir/file_png.tar.gz

this is related to https://github.com/voila-dashboards/voici/issues/104

There might be a problem when the prefix is not mounted at the root (/) but we should disable this anyhow.

Nice thanks!
How do you envision using this in the xeus-lite kernels?
Should we automatically untar the files in the front-end world so that users can use them?

this is already done for you =)
So we add the tarball to the list of packages (ie package like numpy) and these are auto extracted when the kernel is initalized

Neat!!


Dashboard Page Development for Admin/Team Lead

Develop the dashboard for Admin/Team Lead.
We can utilize the existing user dashboard. Just add the additional features based on the role
Integrate necessary API's

Using Django admin site instead.


website: Go 1.9 not listed in bucket contents at https://storage.googleapis.com/golang

What version of Go are you using (go version)?
1.9
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
amd64
What did you do?
curl https://storage.googleapis.com/golang | grep 'go1.9'
What did you expect to see?
Metadata about available go 1.9 downloads, such as https://storage.googleapis.com/golang/go1.9.darwin-amd64.pkg.
What did you see instead?
No matches for 1.9.

Note that the asdf go installer relies on the bucket contents here. More on that here.

I believe this is intentional. We changed how and where downloads are hosted starting at Go 1.9.
This is not an interface we ever guaranteed as stable.

/cc @broady @andybons

@joshwlewis your link is linking to the darwin 1.9 download instead of what, I think, you intended to link to.

I believe this is intentional. We changed how and where downloads are hosted starting at Go 1.9.
This is not an interface we ever guaranteed as stable.

Understandable. Is there a more stable reference to get a list of available versions?

It's there. It's just paginated.
$ curl -s https://storage.googleapis.com/golang | sed -e 's/></'\\n'/g' | grep IsTruncated
IsTruncated>true</IsTruncated

Use gsutil, or the actual GCS API:
$ gsutil ls gs://golang/go1.9.* | wc -l
40

your link is linking to the darwin 1.9 download instead of what, I think, you intended to link to.

Thanks, fixed. I meant to link here.

XML API:
https://cloud.google.com/storage/docs/xml-api/get-bucket-list
See the part about NextMarker and IsTruncated.
But yes, as @bradfitz says, there's no guarantees for this.

It's there. It's just paginated.

Oops, thanks!


Cleanup invalid resource directories on startup

Issue #1191 (fixed in v2.3) may have left behind invalid resource directories (directories without a resource configuration file) inside the IPT's data directory.
These invalid resource directories should be removed, to avoid cluttering the logs with errors such as:
ERROR Cannot read resource configuration for {resource_shortname}
java.io.FileNotFoundException: $ipt-data/resources/{resource_shortname}/resource.xml (No such file or directory)

Issue verified.


Could --help and version be added?

It would be great to add the two standard parameters to get help about the currently installed CLI

thanks for the feedback! currently there is codeflare version (no dashes). i agree that the standard -v/--version would be nice.

this should be improved in codeflare 2.9.1
ref: https://github.com/guidebooks/madwizard/pull/655 https://github.com/guidebooks/madwizard/pull/656
ref: https://github.com/kubernetes-sigs/kui/pull/9311 https://github.com/kubernetes-sigs/kui/pull/9312 https://github.com/kubernetes-sigs/kui/pull/9313


Remove zoom on scroll

I often accidentally scroll while the mouse is in the Plant preview area. Scrolling is directly linked to zooming, and zooming in or out does not improve the readability
would prefer scrolling behaves in the same way as notepad itself,
scroll = vertical scroll
ALT-scroll = horizontal scroll
SHIFT-scroll = zoom

Hi  @thijsvanderkraan ,
thanks for the feedback. Indeed the zoom and scrolling behaviour is not really the common way. The specific proposal you've made looks not very common and also not implemented in Notepad++ for me. I think the following should be the most intuitive / common solution (also in Notepad++ by default):

zoom Ctrl + mouse wheel
mouse wheel to scroll vertically
Shift + mouse wheel horizontally

This is exactly what I've implemented in the latest commit. Please have a look at the latest build, try it out and give some feedback if it works for you:
Build for c42a80b

Dear Philip,
You are absolutely right, I didn't write it down correctly. With scroll I meant the mouse wheel scroll button and I got the shift  and alt mixed up. I tested c42a80b and it works like a charm, thank you!
Best regards,
Thijs


Ng morph tree

:tada: This pull request is included in version<EMAIL_ADDRESS>:tada:
The release is available on GitHub release


Linux support

Any plans to implement this product into Linux by using the new VS 2015 tools?
MongoDB supports Mono 3.x, so it is feasible.

There are no plans to do this right now, although we are thinking about changing to ASP 5, MCV 6 and the dotnet core. I'll put this question on hold for now.

Any movement on this front? Is this still something you are looking to do?

Update: We intend to have at least a beta version of Spark on .Net Core by the end of the year (2016). And it will probably not be just a port of the current codebase, but instead in a structure leveraging the benefits that (ASP).Net Core brings us.

Does this mean a beta version on .net core by end of the year is not expected and the time line around it is unknown?


fastlane match enterprise giving an error for new generated certificate "Could not find the newly generated certificate installed"

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

I can't find newly generated certificate and profile when I used "fastlane match enterprise"
though I've set MATCH_KEYCHAIN_NAME=flipdish.keychain I don't see the private key and cert generated in that key chain. What else I see in the log is that it tries to search login.keychain-db dough flipdish.keychain is set.
Let me know if you want to add something more. Thank you
Command executed

fastlane match enterprise --verbose
Complete output when running fastlane, including the stack trace and command used

export MATCH_GIT_BASIC_AUTHORIZATION=auth_token
export MATCH_PASSWORD=password
export MATCH_KEYCHAIN_NAME=flipdish.keychain
export MATCH_KEYCHAIN_PASSWORD=keychainPass
export FASTLANE_SESSION = appleToken
fastlane match enterprise --verbose
[✔] 🚀
[17:47:49]: fastlane detected a Gemfile in the current directory
[17:47:49]: However, it seems like you didn't use `bundle exec`
[17:47:49]: To launch fastlane faster, please use
[17:47:49]:
[17:47:49]: $ bundle exec fastlane match enterprise --verbose
[17:47:49]:
[17:47:49]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
-------
INFO [2020-09-30 17:48:02.91]: Successfully loaded '/Users/macbookair/Desktop/Code/ios/fastlane/Matchfile' 📄
+--------------+-------------------------------------------------+
|          Detected Values from './fastlane/Matchfile'           |
+--------------+-------------------------------------------------+
| git_url      | https://github.com/flipdishbytes/appsigning.git |
| storage_mode | git                                             |
| type         | development                                     |
+--------------+-------------------------------------------------+
+--------------------------------+-------------------------------------------------+
|                            Summary for match 2.161.0                             |
+--------------------------------+-------------------------------------------------+
| verbose                        | true                                            |
| type                           | enterprise                                      |
| readonly                       | false                                           |
| generate_apple_certs           | true                                            |
| skip_provisioning_profiles     | false                                           |
| storage_mode                   | git                                             |
| git_url                        | https://github.com/flipdishbytes/appsigning.git |
| git_branch                     | master                                          |
| shallow_clone                  | false                                           |
| clone_branch_directly          | false                                           |
| git_basic_authorization        | ********                                        |
| keychain_name                  | flipdish.keychain                               |
| keychain_password              | ********                                        |
| force                          | false                                           |
| force_for_new_devices          | false                                           |
| skip_confirmation              | false                                           |
| skip_docs                      | false                                           |
| platform                       | ios                                             |
| derive_catalyst_app_identifier | false                                           |
| fail_on_name_taken             | false                                           |
+--------------------------------+-------------------------------------------------+
WARN [2020-09-30 17:48:02.93]: To not be asked about this value, you can specify it using 'username'
/usr/local/Cellar/fastlane/2.161.0/libexec/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
[2020-09-30 17:48:02.93]: Your Apple ID Username<EMAIL_ADDRESS>INFO [2020-09-30 17:48:22.00]: Cloning remote git repo...
INFO [2020-09-30 17:48:22.00]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
INFO [2020-09-30 17:48:22.00]: $ git clone https://github.com/flipdishbytes/appsigning.git /var/folders/t7/pjy501d53hzg38d68vdnyyrh0000gn/T/d20200930-11040-1548rs4 -c http.extraheader='Authorization: Basic auth_token'
INFO [2020-09-30 17:48:22.14]: ▸ Cloning into '/var/folders/t7/pjy501d53hzg38d68vdnyyrh0000gn/T/d20200930-11040-1548rs4'...
INFO [2020-09-30 17:48:23.29]: ▸ remote: Enumerating objects: 11, done.
INFO [2020-09-30 17:48:23.29]: ▸ remote: Counting objects: 100% (11/11), done.
INFO [2020-09-30 17:48:23.34]: ▸ remote: Compressing objects: 100% (7/7), done.
INFO [2020-09-30 17:48:23.34]: ▸ remote: Total 11 (delta 0), reused 8 (delta 0), pack-reused 0
INFO [2020-09-30 17:48:23.37]: ▸ Unpacking objects: 100% (11/11), done.
INFO [2020-09-30 17:48:23.41]: $ git --no-pager branch --list origin/master --no-color -r
INFO [2020-09-30 17:48:23.43]: ▸   origin/master
INFO [2020-09-30 17:48:23.43]: Checking out branch master...
INFO [2020-09-30 17:48:23.43]: $ git checkout master
INFO [2020-09-30 17:48:23.46]: ▸ Already on 'master'
INFO [2020-09-30 17:48:23.46]: ▸ Your branch is up to date with 'origin/master'.
INFO [2020-09-30 17:48:23.47]: 🔓  Decrypted '5WX395C8CZ.p12'
INFO [2020-09-30 17:48:23.47]: 🔓  Decrypted '5WX395C8CZ.cer'
INFO [2020-09-30 17:48:23.47]: 🔓  Successfully decrypted certificates repo
INFO [2020-09-30 17:48:23.55]: Verifying that the certificate and profile are still valid on the Dev Portal...
Reading keychain entry, because either user or password were empty
Loading session from<EMAIL_ADDRESS>Available session is not valid any more. Continuing with normal login.
Multiple teams found on the Developer Portal, please enter the number of the team you want to use:

D3FG4... "Prandium Limited" (Company/Organization)
D8FM... "Prandium Limited Ent" (In-House)
2
WARN [2020-09-30 17:48:30.92]: To not be asked about this value, you can specify it using 'app_identifier'
/usr/local/Cellar/fastlane/2.161.0/libexec/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
[2020-09-30 17:48:30.92]: The bundle identifier(s) of your app (comma-separated):
WARN [2020-09-30 17:48:33.29]: Couldn't find a valid code signing identity for enterprise... creating one for you now
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'

Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
Successfully loaded Appfile at path '/Users/macbookair/Desktop/Code/ios/fastlane/Appfile'
+----------------------+----------------------------------------------------------+
|                            Summary for cert 2.161.0                             |
+----------------------+----------------------------------------------------------+
| platform             | ios                                                      |
| development          | false                                                    |
| generate_apple_certs | true                                                     |
| force                | true                                                     |
| username             |<EMAIL_ADDRESS>                                      |
| keychain_path        | /Users/macbookair/Library/Keychains/flipdish.keychain-db |
| keychain_password    | ********                                                 |
+----------------------+----------------------------------------------------------+
INFO [2020-09-30 17:48:33.40]: Starting login with user<EMAIL_ADDRESS>Reading keychain entry, because either user or password were empty
Loading session from<EMAIL_ADDRESS>Available session is not valid any more. Continuing with normal login.
Multiple teams found on the Developer Portal, please enter the number of the team you want to use:

D3FG4... "Prandium Limited" (Company/Organization)
D8FM... "Prandium Limited Ent" (In-House)
2
INFO [2020-09-30 17:48:48.24]: Successfully logged in
INFO [2020-09-30 17:48:50.02]: $ security import /var/folders/t7/pjy501d53hzg38d68vdnyyrh0000gn/T/d20200930-11040-1548rs4/certs/enterprise/4ZHVMCWM55.p12 -k '/Users/macbookair/Library/Keychains/flipdish.keychain-db' -P '' -T /usr/bin/codesign -T /usr/bin/security -T /usr/bin/productbuild
INFO [2020-09-30 17:48:59.75]: ▸ 1 key imported.
[⠋] Setting key partition list... (this can take a minute if there are a lot of keys installed) INFO [2020-09-30 17:48:59.77]: $ security set-key-partition-list -S apple-tool:,apple: -s -k flipdish /Users/macbookair/Library/Keychains/flipdish.keychain-db 1> /dev/null
[✔] Setting key partition list... (this can take a minute if there are a lot of keys installed)
INFO [2020-09-30 17:48:59.96]: $ security import /var/folders/t7/pjy501d53hzg38d68vdnyyrh0000gn/T/d20200930-11040-1548rs4/certs/enterprise/4ZHVMCWM55.cer -k '/Users/macbookair/Library/Keychains/flipdish.keychain-db' -P '' -T /usr/bin/codesign -T /usr/bin/security -T /usr/bin/productbuild
INFO [2020-09-30 17:49:00.04]: ▸ 1 certificate imported.
[⠋] Setting key partition list... (this can take a minute if there are a lot of keys installed) INFO [2020-09-30 17:49:00.07]: $ security set-key-partition-list -S apple-tool:,apple: -s -k flipdish /Users/macbookair/Library/Keychains/flipdish.keychain-db 1> /dev/null
[✔] Setting key partition list... (this can take a minute if there are a lot of keys installed)
INFO [2020-09-30 17:49:00.44]: Successfully generated 4ZHVMCWM55 which was imported to the local machine.
INFO [2020-09-30 17:49:00.44]: $ security list-keychains -d user
INFO [2020-09-30 17:49:00.46]: ▸     "/Users/macbookair/Library/Keychains/login.keychain-db"
INFO [2020-09-30 17:49:00.46]: ▸     "/Users/macbookair/Library/Keychains/flipdish.keychain-db"
INFO [2020-09-30 17:49:00.46]: $ security find-certificate -c 'Apple Worldwide Developer Relations Certification Authority' /Users/macbookair/Library/Keychains/login.keychain-db
INFO [2020-09-30 17:49:00.50]: ▸ keychain: "/Users/macbookair/Library/Keychains/login.keychain-db"
INFO [2020-09-30 17:49:00.50]: ▸ version: 512
INFO [2020-09-30 17:49:00.50]: ▸ class: 0x80001000
INFO [2020-09-30 17:49:00.50]: ▸ attributes:
INFO [2020-09-30 17:49:00.50]: ▸     "alis"="Apple Worldwide Developer Relations Certification Authority"
INFO [2020-09-30 17:49:00.50]: ▸     "cenc"=0x00000003
INFO [2020-09-30 17:49:00.51]: ▸     "ctyp"=0x00000001
INFO [2020-09-30 17:49:00.51]: ▸     "hpky"=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030\213\354\353\272\366GY\305RT\243\267" INFO [2020-09-30 17:49:00.51]: ▸     "issu"<blob>=0x3062310B300906035504061302555331133011060355040A130A4150504C4520494E432E31263024060355040B131D4150504C452043455254494649434154494F4E20415554484F52495459311630140603550403130D4150504C4520524F4F54204341  "0b1\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\023\012APPLE INC.1&0$\006\003U\004\013\023\035APPLE CERTIFICATION AUTHORITY1\0260\024\006\003U\004\003\023\015APPLE ROOT CA" INFO [2020-09-30 17:49:00.51]: ▸     "labl"<blob>="Apple Worldwide Developer Relations Certification Authority" INFO [2020-09-30 17:49:00.51]: ▸     "skid"<blob>=0x88271709A9B618608BECEBBAF64759C55254A3B7  "\210'\027\011\251\266\030\213\354\353\272\366GY\305RT\243\267"
INFO [2020-09-30 17:49:00.51]: ▸     "snbr"=0x01DEBCC4396DA010  "\001\336\274\3049m\240\020"
INFO [2020-09-30 17:49:00.51]: ▸     "subj"=0x308196310B300906035504061302555331133011060355040A0C0A4170706C6520496E632E312C302A060355040B0C234170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E733144304206035504030C3B4170706C6520576F726C647769646520446576656C6F7065722052656C6174696F6E732043657274696669636174696F6E20417574686F72697479  "0\201\2261\0130\011\006\003U\004\006\023\002US1\0230\021\006\003U\004\012\014\012Apple Inc.1,0*\006\003U\004\013\014#Apple Worldwide Developer Relations1D0B\006\003U\004\003\014;Apple Worldwide Developer Relations Certification Authority"
INFO [2020-09-30 17:49:03.82]: Verifying the certificate is properly installed locally...
/usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/errors/fastlane_error.rb:9: warning: The called method `initialize' is defined here

Looking for related GitHub issues on fastlane/fastlane...
Search query: Could not find the newly generated certificate installed
URL: https://api.github.com/search/issues?q=Could not find the newly generated certificate installed+repo:fastlane/fastlane
➡  [deliver] Spaceship::UnexpectedResponse: An attribute value is not acceptable for the current resource state.
https://github.com/fastlane/fastlane/issues/17307 [open] 5 💬
2 hours ago
➡  fastlane does not search the specified keychain for a new certificate
https://github.com/fastlane/fastlane/issues/16321 [closed] 2 💬
27 Jul 2020
➡  [match] Generate profiles with new Xcode 11 certificates attached
https://github.com/fastlane/fastlane/issues/15031 [closed] 44 💬
20 May 2020
and 32 more at: https://github.com/fastlane/fastlane/search?q=Could not find the newly generated certificate installed&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
17: from /usr/local/Cellar/fastlane/2.161.0/libexec/bin/fastlane:23:in <main>' 	16: from /usr/local/Cellar/fastlane/2.161.0/libexec/bin/fastlane:23:in load'
15: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/bin/fastlane:23:in <top (required)>' 	14: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in take_off'
13: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/commands_generator.rb:25:in start' 	12: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/commands_generator.rb:187:in run'
11: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	10: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
9: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	 8: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
7: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	 6: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/commands_generator.rb:68:in block (3 levels) in run'
5: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/runner.rb:94:in run' 	 4: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/runner.rb:161:in fetch_certificate'
3: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/generator.rb:39:in generate_certificate' 	 2: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/cert/lib/cert/runner.rb:17:in launch'
1: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': Could not find the newly generated certificate installed (FastlaneCore::Interface::FastlaneError)
17: from /usr/local/Cellar/fastlane/2.161.0/libexec/bin/fastlane:23:in <main>' 	16: from /usr/local/Cellar/fastlane/2.161.0/libexec/bin/fastlane:23:in load'
15: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/bin/fastlane:23:in <top (required)>' 	14: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in take_off'
13: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/commands_generator.rb:25:in start' 	12: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/commands_generator.rb:187:in run'
11: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	10: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
9: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	 8: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
7: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	 6: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/commands_generator.rb:68:in block (3 levels) in run'
5: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/runner.rb:94:in run' 	 4: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/runner.rb:161:in fetch_certificate'
3: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/match/lib/match/generator.rb:39:in generate_certificate' 	 2: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/cert/lib/cert/runner.rb:17:in launch'
1: from /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' /usr/local/Cellar/fastlane/2.161.0/libexec/gems/fastlane-2.161.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': \e[31m[!] Could not find the newly generated certificate installed\e[0m (FastlaneCore::Interface::FastlaneError)

Environment

 [✔] 🚀
[18:07:18]: fastlane detected a Gemfile in the current directory
[18:07:18]: However, it seems like you didn't use `bundle exec`
[18:07:18]: To launch fastlane faster, please use
[18:07:18]:
[18:07:18]: $ bundle exec fastlane env
[18:07:18]:
[18:07:18]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[18:07:24]: Generating fastlane environment output, this might take a few seconds...
Your Gemfile lists the gem fastlane-plugin-sentry (>= 0) more than once.
You should probably keep only one of them.
Remove any duplicate entries and specify the gem only once.
While it's not a problem now, it could cause errors if you change the version of one of them later.
[18:07:26]: Installing Ruby gem 'fastlane-plugin-sentry'...
[18:07:34]: Successfully installed 'fastlane-plugin-sentry'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_upload_dsym'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_set_commits'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_upload_sourcemap'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_finalize_release'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_upload_file'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_upload_proguard'
[18:07:34]: Plugin 'Sentry' overwrites already loaded action 'sentry_create_release'
✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.6

Ruby
2.7.1

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/Cellar/fastlane/2.161.0/libexec/bin/fastlane

Host
Mac OS X 10.15.6 (19G2021)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.7.1_2/lib

OpenSSL Version
OpenSSL 1.1.1f  31 Mar 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
12.0.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.161.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-sentry
1.6.0
✅ Up-To-Date

fastlane-plugin-sentry
1.6.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.4.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.2

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.18.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.76.0

faraday
1.0.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.0

gh_inspector
1.1.3

json
2.3.0

mini_magick
4.10.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.6

bundler
2.1.2

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

memoist
0.16.2

os
1.1.1

googleauth
0.13.1

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.3.3

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

rake
13.0.1

digest-crc
0.6.1

google-cloud-storage
1.29.0

emoji_regex
3.0.0

jmespath
1.4.0

aws-partitions
1.376.0

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-sdk-core
3.108.0

aws-sdk-kms
1.38.0

aws-sdk-s3
1.81.1

uri
0.10.0

forwardable
1.3.1

logger
1.4.2

cgi
0.1.0

timeout
0.1.0

stringio
0.1.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.2.0

strscan
1.0.3

date
3.0.0

delegate
0.1.0

fileutils
1.4.1

io-console
0.5.6

zlib
1.1.0

singleton
0.1.0

rexml
3.2.3

open3
0.1.0

yaml
0.1.0

psych
3.1.0

mutex_m
0.1.0

webrick
1.6.0

etc
1.1.0

fastlane-plugin-sentry
1.6.0

generated on: 2020-09-30

[18:07:35]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
/usr/local/Cellar/fastlane/2.161.0/libexec/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
[18:07:35]: 🙄  Wow, that's a lot of markdown text... should fastlane put it into your clipboard, so you can easily paste it on GitHub? (y/n)
/usr/local/Cellar/fastlane/2.161.0/libexec/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
 y
[18:07:46]: Successfully copied markdown into your clipboard 🎨
[18:07:46]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅

I have the same problem, in my keychain the certificate appears as "certificate is not trusted" but i see that the certificate is created in the apple dashboard and seems to be ok. Fastlane doen't push anything to the repository.

I solve the issue reinstalling apple intermediate certificates. You can download it here:
https://developer.apple.com/certificationauthority/AppleWWDRCA.cer
https://www.apple.com/certificateauthority/AppleWWDRCAG3.cer
Hope it helps!

Oh thank you! Will try this too.

@arsolisGen Thank you soo much you are a life saver!!  That solved the problem

Thanks @arsolisGen for the solution. This also works if you get the error that I got:
Warning: unable to build chain to self-signed root for signer "iPhone Developer: name (xxxxxxxxxx)"

I just found this https://developer.apple.com/support/expiration/
Maybe you guys had the certificates that were issued before September 1st 2020, and thus got expired when these new ones came out (maybe?)
Could anyone share what the process of "reinstalling apple intermediate certificates" looks like? Is it just downloading those 2 certs and putting them into your keychain? I'm asking because we could improve this process by creating a new feature in match that will reinstall those for you 😊

@rogerluan Hey, that would be awesome. Yes that was the solution for me. On the CI I just use few commands to add it in the keychain.

yes, that would be great, thank you!

I have added the certificate to the repository and adding it to the keychain on CI builds like this:
# Importing Apples intermediate WWDR certificate to ensure a trusted chain
# for enterprise distribution certificates can be established

import_certificate(
  certificate_path: './fastlane/certs/WWDRCA.cer',
  keychain_name: ENV["CI_KEYCHAIN_NAME"],
  keychain_password: ENV["CI_KEYCHAIN_PASSWORD"]
)

this way you can make sure you always have the certificates needed to build up the chain. I hope this helps.

Awesome, thanks for the input everyone! And thanks for the snippet @taschik 🤗
I'll add this to my list, with a low priority. If anyone feel like contributing, all PRs are welcome! Please tag me in your PR if you end up opening one 😊

AFAICT this was fixed here https://github.com/fastlane/fastlane/pull/17538 and just released as part of 2.167.0 🚀
Closing this - let me know if the latest version of fastlane doesn't fix this issue for any of you 🤗


Homepage, Debt Overview and User Improvements

Description
Please provide a brief summary of the changes made in this pull request.
Fixes # (issue reference, if applicable)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

[ ] Locally tested the according endpoints
[ ] Ran E2E-Tests

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Also der Code ist inzwischen wirklich alles (wirklich alles) andere als schön, aber er funktioniert und erfüllt seinen Zweck. Hab leider keine Zeit mehr schönen, gut aufgebrochenen Code zu schreiben 🥲


Added runway AGL as a configurable value

Added in a AGL variable to the config.json file so that the AGL of the selected icao can be taken into consideration when determining the cloud layer base.

Looks good; fixed a couple issues. Summary of changes for information:
**config.json, **

Renamed parameter runwayAGL to runway-elevation to follow convention and to remove confusion that the runway/airport elevation should be in MSL.

miz.go

Changed location of using configured runway elevation from updateClouds() to checkClouds(). This is to ensure a preset is selected that's compatible with increase base height.

util.go

Parameter name change to match config.json

README.md

Config parameter change to match config.json

Decided to leave opening until non beta build released

This pull request has been merged. 245b903 is the new commit hash and it was merged into the dev branch. Changes have since been included in the v1.11.0 release.


Installation for M.2 Accelerator on RockPI 4 fails .....

Description
Hello,
I have (as also under the RaspBerry) problems with the installation of the drivers /software and would be very pleased if I am helped here.
I have proceeded according to your installation instructions:
                           https://coral.ai/docs/m2/get-started/

and up to this step 6 everything worked fine, also verify that the PCIe driver is loaded.
Here I get a message from the system that "NO" device or file is present.
Under "lspci -v" I get the following message:
01:00.0 System peripheral: Global Unichip Corp. Coral Edge TPU (prog-if ff)
Subsystem: Global Unichip Corp. Coral Edge TPU
Under the command "lspci -vv | grep -i MSI-X" I get the following displayed:
    Capabilities: [b0] MSI-X: Enable- Count=1 Masked+.
    Capabilities: [d0] MSI-X: Enable- Count=128 Masked-.

Here is another output from: lspci -nn | grep 089a
01:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]
This is an ARM64 - Debian system.
It would be very helpful if I could get some help here, because I would very much like to start using my investment.
Best regards
Z. Matthias
Click to expand!
Issue Type
Build/Install
Operating System
Linux
Coral Device
M.2 Accelerator B+M
Other Devices
No response
Programming Language
Other
Relevant Log Output
No response

Were there any installation errors? Is DKMS module loaded into kernel?

I had do that an now, I´ve got an Error - Message:
Error! Bad return status for module build on kernel: 5.10.63-rockchip64 (aarch64)
Consult /var/lib/dkms/gasket/1.0/build/make.log for more information.
dpkg: error processing package gasket-dkms (--configure):
installed gasket-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
gasket-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
On LOG-File:
DKMS make.log for gasket-1.0 for kernel 5.10.63-rockchip64 (aarch64)
Thu Oct 21 10:24:37 AM UTC 2021
make: Entering directory '/usr/src/linux-headers-5.10.63-rockchip64'
Makefile:682: arch//Makefile: No such file or directory
make: *** No rule to make target 'arch//Makefile'.  Stop.
make: Leaving directory '/usr/src/linux-headers-5.10.63-rockchip64'

try as root:
cd /usr/src/linux-headers-$(uname -r)
make scripts
then reinstall dkms module again


statement`

What is it statement` in example?

I'm also wondering this. Did you find out?

@stolinski Couldn't get this package to work, but this one works at stackoverflow: https://stackoverflow.com/questions/46021203/how-to-use-jscodeshift-to-insert-a-line-in-the-beginning-of-the-file

@stolinski Couldn't get this package to work, but this one works at stackoverflow: https://stackoverflow.com/questions/46021203/how-to-use-jscodeshift-to-insert-a-line-in-the-beginning-of-the-file

Oops sorry I missed this.  It is j.template.statement, where j is the jscodeshift instance.  I'll update the example

Oops sorry I missed this.  It is j.template.statement, where j is the jscodeshift instance.  I'll update the example

:tada: This issue has been resolved in version 1.0.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix(forms): Update select arrows to not overlap option text

When the text on the option tag is big, the arrow was overlapping it.
Preview
Before

After

Codecov Report

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

@@          Coverage Diff          @@
##           master   #207   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     20
  Lines         379    379
=====================================
  Hits          379    379

Continue to review full report at Codecov.

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

@leandrogrillo :question:


V10

Version 10
git branch -m v10-scs-astary v10
git fetch origin
git branch -u origin/v10 v10
git remote set-head origin -a

Hopefully this branch is deployed under v10.schedule-personalizer.pages.dev

Hopefully

Mobile still looks a little weird but it works?

This latest commit should prevent the font from being times new Roman while the other font is loading


Consider using @storybook/addon-info

We currently use storybook-readme to show the readme files for components within storybook.
This was proposed in #212 and implemented in #300.
This is great, but has a flaw in that it is applied to the "default" story for a component.  Additionally the use of the component is illustrated solely via examples written in-line in comments in the component source and written out into the readme files when docs are generated.
The @storybook/addon-info plugin has an advantage over our current approach in that it can display the source code for any/all of our examples.
We should consider adopting addon-info for our stories.  As part of that we should consider a few things:

should this apply to "example" stories only, i.e. leave the "Component Default" stories as-is using readme?
do we want this info documentation in-line on the page, or (as per their default) or click-to-view
can it provide full documentation as per our current readme files?
if yes, should we remove our existing readme files?

The docs for addon-info imply that @storybook/addon-info will show documentation in react-docgen format, which is how we are documenting components, however in experiments I've not been able to make this work.  (This included ensuring that babel-plugin-react-docgen had been added to the babel configuration.)

https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#deprecated-addon-info-addon-notes
replaced with addon-docs

yup - addon-docs is good - I've used it in another component library - used MDX format docs, which allowed documentation to form part of the storybook stories, and props got automatically documented from their typescript types.
definitely worth investigating moving to use addon-docs.  we may want to consider how the rest of our documentation works too and move away from our custom scripting, given the potential advantages it brings

Fixed in #856


Add a command to set the channel topic

Such as /topic.

Since the MM parlance is "purpose", I'll use that instead.


fix setup file

when i install setup.py , my computer not found package , so i rewrite setup file , and reinstall again , it's work

Thanks for the fix!


Support entity class return type extension from entity storage methods

Closing #238

Thanks @brambaud !!! I will give this a more in-depth look over. I love the tests.

In order to avoid the solution based on the storage mapping, it introduced 3 new types:

EntityStorageType: to store the entity type id in order to reuse it for the mapping.
ConfigEntityStorageType: to identify config entity storage and then config entity.
ContentEntityStorageType: to identify content entity storage and then content entity.

More tests have been added too.
Not sure all cases are covered though 🤔
And I don't really found them readable. Maybe grouping cases using function could allow easier reading and understanding. 🤔
Need some sleep to think about it 😅

Also, I think the test coverage is top-notch. I appreciate taking the time to add some custom entity definitions, as we'll be able to leverage those more later on.

I'm going to merge this, today, and work on follow ups :)

Sorry for the late reply :/
I'm totally ok for the EntityDataRepository! Great idea!