PowerShell snap segfaults on Ubuntu 18.04 Azure VM

Steps to reproduce
Does not repro if you disable telemetry

Expected behavior

Actual behavior

Environment data

7.0.0-preview.4

Thread 25 "pwsh" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 32283]
0x00007ffff7de375c in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
(gdb) backtrace
#0  0x00007ffff7de375c in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#1  0x00007ffff7dec861 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#2  0x00007ffff7de7574 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#3  0x00007ffff7debdb9 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#4  0x00007ffff79b6f09 in ?? () from /snap/core/current/lib/x86_64-linux-gnu/libdl.so.2
#5  0x00007ffff7de7574 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#6  0x00007ffff79b7571 in ?? () from /snap/core/current/lib/x86_64-linux-gnu/libdl.so.2
#7  0x00007ffff79b6fa1 in dlopen () from /snap/core/current/lib/x86_64-linux-gnu/libdl.so.2
#8  0x00007ffff6586ec5 in PAL_LoadLibraryDirect () from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#9  0x00007ffff63c48a2 in NDirect::LoadLibraryModuleBySearch(Assembly*, int, unsigned int, LoadLibErrorTracker*, char16_t const*) () from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#10 0x00007ffff63c5c27 in NDirect::LoadLibraryModule(NDirectMethodDesc*, LoadLibErrorTracker*) ()
   from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#11 0x00007ffff63c3df9 in NDirect::NDirectLink(NDirectMethodDesc*) ()
   from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#12 0x00007ffff63c3d11 in NDirect::GetStubForILStub(NDirectMethodDesc*, MethodDesc**, unsigned int) ()
   from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#13 0x00007ffff63c408f in GetStubForInteropMethod(MethodDesc*, unsigned int, MethodDesc**) ()
   from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#14 0x00007ffff62582b5 in MethodDesc::DoPrestub(MethodTable*) ()
   from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#15 0x00007ffff6257c24 in PreStubWorker () from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#16 0x00007ffff637b95c in ThePreStub () from /snap/powershell-preview/32/opt/powershell/libcoreclr.so
#17 0x00007fff8294a3e6 in ?? ()
#18 0x0000000000000000 in ?? ()

I think this only tell us it failed loading a library... We probably need to know what library.


Add the 'Framework :: Celery' trove classifier

Request to add a new Trove classifier.
Fixes #16.
The name of the classifier(s) you would like to add:

Framework :: Celery

Why do you want to add this classifier?

We'd like to create a community of projects for Celery and present related projects in our documentation automatically just like pytest does.

Thanks!

Is there an ETA on when can I start using it?

Should be available in about 5-10 minutes.


add ethereum plugin

Why are we adding the old ethereum JS plugin here, when the wasm wrapper should replace it? Should we just publish 1 last version of the plugin to NPM saying it's "deprecated" and point users to this repository to find out how to include Ethereum in their app using Polywrap?

Why are we adding the old ethereum JS plugin here, when the wasm wrapper should replace it? Should we just publish 1 last version of the plugin to NPM saying it's "deprecated" and point users to this repository to find out how to include Ethereum in their app using Polywrap?

Yes, sure, that's a good idea. I added it here because i was working on the PR in the toolchain repo to replace it and i didn't want to just delete it. I didn't mean to imply that we should maintain it.

Ah okay, sounds good, I suppose we can update it in this repo & republish with the deprecation / migration information.


feat(bullmq): allow settings custom job ids from within job class

Information

Type
Breaking change

Feature
No

Make it easier for jobs to declare their own job ids. Giving them access to the payload and injected services.
This also streamlines the job id creation when the job is dispatched in several places.
The added method is optional and therefore should not be a breaking change.
import {JobController, JobMethods} from "@tsed/bullmq";

@JobController("example-with-custom-id")
class ExampleJobWithCustomId implements JobMethods {
  public handle(payload: {num: number}) {
    console.info("look at my awesome number: ", payload.num);
  }

  public jobId(payload: {num: number}): string {
    return `very realistic job id #${payload.num}`;
  }
}

Todos

[X] Tests
[X] Coverage
[X] Example
[X] Documentation

@abenerd  Merged ;)

Thanks!


Power App does not handle when you add more than 20 members

The graph call fails with more than 20 members so the Power App needs to enforce a max of 20.

20 links exceeded actually includes members AND owners so members should be limited to 18

Service account also gets added so should restrict to 17

@alexc-MSFT Which Graph call are you referring to?
This one can handle up to 200 members according to the docs: https://docs.microsoft.com/en-us/graph/api/conversationmembers-add?view=graph-rest-1.0&tabs=http
(Just asking because I have a similar use case and this ticket with a limit of 20 members popped up.)

@heinrich-ulbricht Thanks, we are actually adding the members when we create the Team. We actually create a group first and then create the team.
I'll add this to the roadmap to update the logic to add the members after using the endpoint you pointed out above 😀


[TASK] Add blog post about using DDEV in GitLab CI

The Issue

People have been asking about this for years and it would be lovely for them to know about it. Anywhere would be great,
but how about a guest blog on ddev.com? It's just markdown and super easy,

https://github.com/ochorocho/ddev-gitlab-ci/issues/11
How This PR Solves The Issue
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Thanks!

Well, the featuredImage was ignored by my global .gitignore 🤦 it should be displayed now.
Added/changed the text according to your suggestions.
Thank you.

Could you just say a bit about how testing is done or enabled in gitlab? Since I've never done that, I'm kind of lost at the very beginning here (and also in the project README).

Which testing are your talking about? The bats tests for the container or actual e2e (end to end) tests?
Well, i'm not sure if it makes sense to explain how to install ddev addons and set up playwright.
It feels a bit out of scope.

This and the README can be dramatically improved with a specific example. (I spent some time wondering if the build.sh was important to me, it obviously isn't. But it's the most prominent thing in the README.) So an example might be... "If you have a TYPO3 project checked into Gitlab and want to add testing that uses DDEV, ..."

I've extended and restructured the README to be more clear what the important sections are.

Important projects sometimes have a hard time living on in a personal repository like ochorocho. I invite you to move this to the ddev org if you're open to that. Alternately, move it into a TYPO3 org or b13 ? If you're interested in moving it, it could move sooner rather than later and then the article wouldn't need updating at that time.

I'm happy to move it to the ddev org.

FYI, i've moved the project to the ddev org :-)

Sorry forgot to answer this one:

Shouldn't the default be current DDEV stable version? Why all the references to really old DDEV versions, and why should one have to specify a version?

So you're saying the image should have a latest tag too?

You sure move fast!!!! Thanks!

Which testing are your talking about? The bats tests for the container or actual e2e (end to end) tests?

I was talking about using DDEV in other tests, not the tests for this add-on. People like me would just like to understand in context how this will be used.

So you're saying the image should have a latest tag too?

No, I'm probably saying that it should automatically use the current stable, unless another version is specified.
This is all so great, I'll follow up with issues in the repo, will take one more look at the article here and we'll get it moving along. I imagine you already changed the article to change the URL and such.

I imagine you already changed the article to change the URL and such.

Not just yet. Will do later today or early tomorrow. :-)

Instead of going back-and-forth I pushed one small commit and will pull it now. Thanks so much for this contribution and for maintaining it!

@rfay thanks for all the support you provided on the way!


echo: abstract VMIMage to VMDistro

fixes https://github.com/istio/istio/issues/31427

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test lint_istio

gencheck_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test lint_istio

gencheck_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test gencheck_istio

analyze-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test lint_istio

gencheck_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test gencheck_istio

analyze-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test lint_istio

gencheck_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test gencheck_istio

analyze-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test integ-pilot-k8s-tests_istio

integ-pilot-multicluster-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test lint_istio

analyze-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test analyze-tests_istio

integ-pilot-k8s-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test integ-pilot-k8s-tests_istio

integ-pilot-multicluster-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
9ccfbb8bac5fd1dd180729fdcf9acbab3e55c823
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
09244782e9d2ea7f33b350fada30ee63d07cb045
link
/test integ-pilot-k8s-tests_istio

integ-pilot-multicluster-tests_istio
427282defd2979a418f60ddcd0619cbc86557eb0
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e3314b8bb6ff80619631ee022507c65515215013
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e3314b8bb6ff80619631ee022507c65515215013
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e3314b8bb6ff80619631ee022507c65515215013
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test analyze-tests_istio

lint_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e3314b8bb6ff80619631ee022507c65515215013
link
/test integ-pilot-multicluster-tests_istio

analyze-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test analyze-tests_istio

lint_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test lint_istio

integ-pilot-k8s-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test analyze-tests_istio

lint_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test lint_istio

integ-pilot-k8s-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test integ-pilot-k8s-tests_istio

integ-pilot-multicluster-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test integ-pilot-k8s-tests_istio

integ-pilot-multicluster-tests_istio
fe471a4512a3c8e98e444528d457e506e955e507
link
/test integ-pilot-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
377c556db1c8e5ede631c7aa6de9b36d5e7d9077
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

In response to a cherrypick label: new pull request created: #32177

In response to a cherrypick label: #32151 failed to apply on top of branch "release-1.9":
Applying: echo: abstract VMIMage to VMDistro
Using index info to reconstruct a base tree...
M	pkg/test/framework/components/echo/kube/deployment.go
M	tests/integration/pilot/vm_test.go
Falling back to patching base and 3-way merge...
Auto-merging tests/integration/pilot/vm_test.go
CONFLICT (content): Merge conflict in tests/integration/pilot/vm_test.go
Auto-merging pkg/test/framework/components/echo/kube/deployment.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 echo: abstract VMIMage to VMDistro
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #32178


Use markdown for some of About Research page

Markdown is more editable than pug, and it is possible to see
a preview without running the server.

Pull Request Test Coverage Report for Build 323

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 54.114%

Totals

Change from base Build 322:
0.0%

Covered Lines:
4250

Relevant Lines:
7281

💛  - Coveralls


Make LEAP dask workers be not pre-emptible

Possible way to reduce confounding factors for
https://github.com/2i2c-org/infrastructure/issues/2396

Btw they may very well need a cloud quota increase for on-demand CPU now. pre-emptible/spot CPU quotas are separate from on-demand I believe, so they may run out on on-demand now that its the only kind of CPU used.

Am also going to wait for the LEAP credits issue to be resolved before deploying this.

Leap credits are done now


Express filing unit count in million rounded to one decimal place

After reviewing the dropq documentation and code, it seems clear that part of our IRS-SOI PUF privacy-protection strategy is to show dollar amounts in billions rounded to one decimal point.  However, the distribution and difference tables show the number of filing units in a bin in whole thousands.  This seems like much more precision than is scientifically reasonable and excessive precision when considering privacy-protection issues.
I suggest that all the filing unit count columns have units Millions (instead of Thousands) and that the entries in those columns be rounded to one decimal place.
So, for example, a table entry that currently says 17,005 in a column labeled Thousands would be shown as 17.0 and the column unit label would be changed to Millions.
This change has the added advantage of making it easier (at least for me) to do mental arithmetic to get the average dollar amount in each bin.  For me it is easier to divide billions by millions to get an average that is expressed in thousands of dollars.
But even if others don't find that mental arithmetic argument compelling, the privacy-protection argument is very important.
@MattHJensen @feenberg @GoFroggyRun @hdoupe @brittainhard

On Fri, 1 Sep 2017, Martin Holmer wrote:

After reviewing the dropq documentation and code, it seems clear that part
of our IRS-SOI PUF privacy-protection strategy is to show dollar amounts in
billions rounded to one decimal point. However, the distribution and
difference tables show the number of filing units in a bin in whole
thousands. This seems like much more precision than is scientifically
reasonable and excessive precision when considering privacy-protection
issues.
I suggest that all the filing unit count columns have units Millions
(instead of Thousands) and that the entries in those columns be rounded to
one decimal place.
So, for example, a table entry that currently says 17,005 in a column
labeled Thousands would be shown as 17.0 and the column unit label would be
changed to Millions.
This change has the added advantage of making it easier (at least for me) to
do mental arithmetic to get the average dollar amount in each bin. For me it
is easier to divide billions by millions to get an average that is expressed
in thousands of dollars.
But even if others don't find that mental arithmetic argument compelling,
the privacy-protection argument is very important.

Recall that between drop-q and the fact that the base file is already a
public use file, I don't think we should be worrying about privacy. Also,
the privacy aspect depends on the number of records, not the weighted
count.
It looks like our smallest category by AGI only would go from "715" to
".7". That is just a single digit of precision. The tax-increase and
tax-decrease cells would show even more loss of precision. I can certainly
see a congressperson not wanting to see 400 thousand rounded down to zero.
There is a tradition going back nearly a hundred years of showing
returns in thousands, and it is to our advantage to respect this
tradition.
dan

@MattHJensen @feenberg @GoFroggyRun @hdoupe @brittainhard
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the
thread.[AHvQVSFhDgvLRaJ8M0Z1_AvFALELjBTrks5seFMNgaJpZM4PKg4A.gif]

@feenberg said:

I can certainly see a congressperson not wanting to see 400 thousand rounded down to zero.

You didn't read or understand my proposal, I'm not sure which.
I'm suggesting that 400 thousand be represented as 0.4 million.
Or, at the greatest loss of precision, 449 thousand being represented as 0.4 million.
Will "congresspeople" really think it is important to know whether 449 thousand are affected, rather than being told about 0.4 million will be affected?

@feenberg said in issue #647:

There is a tradition going back nearly a hundred years of showing returns in thousands, and it is to our advantage to respect this tradition.

I'm not sure what "hundred year" "tradition" you're referring to here.  Certainly when IRS has all the tax returns, IRS can in complete confidence show the number of filing units in a table cell in thousands.  But in our simulation work, we have only a small sample of tax returns (very roughly a one-in-a-thousand sample).  And we are also trying to simulate the effects of tax reforms (not just tabulate returns under current law).  Also we are projecting to future years with uncertain growth projections.  All these things imply to me that it is not scientifically prudent to express the number of tax returns in a table cell in thousands.  Why aren't we expressing dollar amount in whole millions of dollars?

I am sympathetic to the concern that expressing returns in thousands is overly precise and better suited for an agency like SOI with a larger dataset than what we have. However, it also feels misleading to round 49,000 to 0.0. Having those situations expressed as 0+ or similar seems nice, but implementing it doesn't.

@MattHJensen said:

I am sympathetic to the concern that expressing returns in thousands is overly precise and better suited for an agency like SOI with a larger dataset than what we have. However, it also feels misleading to round 49,000 to 0.0. Having those situations expressed as 0+ or similar seems nice, but implementing it doesn't.

OK, if you honestly think the TaxBrain decile bin filing-unit counts have standard errors small enough to detect the difference between 49 thousand units and zero units, then maintain the current practice of showing unit-count results in the whole number of thousands.

On Wed, 6 Sep 2017, Martin Holmer wrote:

@MattHJensen said:
  I am sympathetic to the concern that expressing returns in thousands is overly precise and
  better suited for an agency like SOI with a larger dataset than what we have. However, it
  also feels misleading to round 49,000 to 0.0. Having those situations expressed as 0+ or
  similar seems nice, but implementing it doesn't.

OK, if you honestly think the TaxBrain decile bin filing-unit counts have standard errors small enough
to detect the difference between 49 thousand units and zero units, then maintain the current practice
of showing unit-count results in the whole number of thousands.

At high incomes, 49 thousand units could be several thousand records.
Please don't even consider anything non-numeric such as "0+" - a nightmare
for anyone who expects machine readable output.
dan

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the
thread.[AHvQVVXGL32-drlOnch8VIIdqardFrPuks5sfvCSgaJpZM4PKg4A.gif]


Update Spectra-VibrantSunsets.netkan

Add Scatterer as dependent mod as it is required as well to make this work

Thanks for the update!
(Prepare to read that sentence several more times... :raised_eyebrow:)


Package Manifest - Auto Install/Upgrade & More

A detailed description of the proposed feature
I'd love to see a brew.json or brew manifest file option of some sort available for brew.  This would be very similar to the package.json file for npm.
I know that brew installs are usually global for the system, however having a file like this would be amazing for the following use case:
As a developer creating programs in tracked repositories, there are a large amount of dependencies that are required to be installed by brew for the app to work and function properly. I'd like to be able to run "brew install" in the same directory as the manifest file and have brew do the following: A) Check if each package is installed already B) update/skip/install the package per the manifest C) Get a convenient summary at the end - this is helpful over writing a script because I can have a once-over visual if everything worked, or if anything failed and scrolling back over all of the output is required.
I'd also like warnings if there are newer packages available but the manifest isn't configured to upgrade to that version.
Possible options:

compact (least amount of output -> shows console loading bars instead of detailed brew output (unless there are errors or warnings))

version specification with common operators (~, >, <, etc..)

auto-upgrade: <true/false> (auto - upgrade the package if a new one is available - default to true.)

stop-on-fail: stop installing packages if there is any failure  (harder to script in bash, but very useful).  (also stop-on-warning might be useful)

logfile: Will also output the result to a log along with any errors or warnings.

manifestDescription: "This manifest is for installing dependencies for the  development environment"    - I.E. required brew packages documentation is the manifest!

The motivation for the feature
Having setup scripts with friendly output can be much larger than scripts just installing brew packages. If you want to fail on error or anything this requires more scripting and it is harder to maintain across teams with varying levels of scripting skills.
Furthermore, separate scripts are needed to upgrade packages or check for upgrades to all packages.
large lists of brew installs in a script results in a lot of output parsing to even know if everything was successful, unless you've manually coded up a fail on error so the script stops installing on the first brew install failure.
Always writing up brew dependencies on wikis - this is cumbersome and a manifest file would be sooo much better 👍

How the feature would be relevant to at least 90% of Homebrew users

Developers could more easily scale setup of local macs.
Normal users could share a manifest to help their friend install required packages.
Could be used as a troubleshooting mechanism - can post log output, and manifest.
Users or companies could template manifests for different purposes in public template docs - install all of the dependencies for a certain purpose.

This already exists as Homebrew Bundle.

Thanks!


db for student details and marks

Resolve the conflict..

Resolve the conflict..

Done

Resolve remaining conflicts..


Installation script needs to be fixed for ARM64

Mistake is here:
https://github.com/Azure/azure-cli/blob/c92d0d0048d3f4f1435a4263bcf6583c34880cee/scripts/release/debian/deb_install.sh#L84
It should not be hardcoded for amd64

ARM64 related

Fixed in https://github.com/Azure/azure-cli/pull/24180


fixing duplication of ecdsa-koblitz-pubkey in batch creation

Before:
"recipientProfile": {
        "publicKey": "ecdsa-koblitz-pubkey:ecdsa-koblitz pubkey:msBCHdwaQ7N2ypBYupkp6uNxtr9Pg76imj",
        "type": [
            "RecipientProfile",
            "Extension"
        ],
        "name": "Tim Chen"
    }

After:
"recipientProfile": {
        "publicKey": "ecdsa-koblitz pubkey:msBCHdwaQ7N2ypBYupkp6uNxtr9Pg76imj",
        "type": [
            "RecipientProfile",
            "Extension"
        ],
        "name": "Tim Chen"
    }

Thanks @timlichen!
Note on above -- it should beecdsa-koblitz-pubkey:<bitcoin_address>. This change requires that you put the prefix in the roster, which is reasonable and allows more variations in the future.

 Happy to help.
Ah, I see, looks good, thanks for including some roster templates!


Revamp of unit tests

With changes to YouTube that break pytube, it will sometimes be necessary to generate new mock files for the test suite. This adds that functionality to the helpers.py file, and also creates unit testing for that new function.
As part of this pull request, the previous mock file that references Gangnam Style has been replaced with a mock file that references YouTube Rewind 2019. Additionally, existing unit tests have been updated to reflect this new mock file.
Finally, there is another fix to make another existing unit test os-agnostic.

Coverage decreased (-0.7%) to 93.972% when pulling 6a9b159fc77a9d7381eaac0593fe1dc6cc753fea on tfdahlin:feature-create-mockfiles into eec6f6481e6b68840142c94d464d00cbacfcd6aa on nficano:master.

cc: @RONNCC

Technically this functionality sorta exists in the cli, but lacks unit-tests and doesn't save the result to the mock folder. This simplifies the process of creating these files and includes unit test coverage

Looks like the travis CI is failing due to youtube rate limiting. I'll figure out a way to create a mock instead so we can avoid that.

This one's a bit of a doozie.
Firstly, it gets rid of the unit tests against gangnam style, in favor of unit tests against YouTube Rewind 2019, as requested as a follow-up to https://github.com/nficano/pytube/pull/767.
In doing this, I discovered that the mock json files were generated kind of weird, and were sort of a partial serialization of a YouTube object. At first, I tried to create a function that replicated this (without realizing one existed), but while writing unit tests to make sure that it worked correctly, I ran into problems with Travis CI. Notably, I ran into HTTP 429 responses from YouTube, so I had to work out how to use mock to get around that. As a result of this, I discovered I needed to create a cache of different webpages to test against, so I ended up reworking some of the unit tests to use pure HTML responses from a mock file, instead of using a partial serialization. Travis CI should no longer have rate limiting issues while running the unit test that I wrote for my serialization function.
I also included another minor fix to unit tests where it was using platform-specific separators, rather than platform-agnostic.
Finally, I also attempted to follow up on #743 and I believe the way that I refactored main will fix this problem.
cc: @RONNCC

@tfdahlin  one nit -- but otherwise looks good

see response in conversation

@tfdahlin  responded

Good point on those tests, changed according to your suggestions @RONNCC

this is a giant set of changes -- thank you @tfdahlin  😄


How do I import modules? (JS.import not working for me)

Freaking love this project; I appreciate your ambition :).
I'm playing with the frontend boilerplate, and I've been trying:
JS.import React, "react"

But get
** (UndefinedFunctionError) function JS.import/2 is undefined or private

I imagine I am missing a step, but can't quite figure it out.

To use a javascript module, you have to configure them ahead of time. There are some instructions here

Sweet! Totally missed that. Thanks for the quick response :)


Feat/update prices logic & fix hasura migrations

Fix hasura migrations
What does this PR do?

Resolve #386

Steps to test

make start

CheckList

[ ] Follow proper Markdown format
[ ] The content is adequate
[ ] The content is available in both english and spanish
[ ] I Ran a spell check

@JustinCast  please check conflicts

@xavier506 @adriexnet please take a look at the latest changes!

@adriexnet @xavier506


Fixed the navigation toc

Do you have an example hosted in the blob storage somewhere I can look at?

@weshaggard
E.g. https://azuresdkdocs.blob.core.windows.net/$web/dotnet/Azure.Core/1.6.0/index.html
You can check github.io or blob storage link for all other sdks


enigmaOpen error: {}

Hello,
First of all, thanks so much for this work, it's very helpful.  I am running into an issue shown in the attached image.  Basically, when an app is scheduled to run, at every specified time it runs, there is an enigmaOpen error, but with no message:
error: enigmaOpen error: {}
Can you help me or at least explain to me why this is happening / if you've seen this before?  The error is thrown at line 56:
 try {
        g = await s.open();
    } catch (err) {
        globals.logger.log('error', `enigmaOpen error: ${JSON.stringify(err)}`);
        return;
    }

The strange thing is that if doInitialLoad is set to "true" - it runs the first time successfully, but everything on the scheduler does not with the above message.
I have tried running natively as well as in docker, but the same issue happens.

I debugged through index.js at that line that calls "await s.open".  Looking closer at the err object, i found:
getaddrinfo ENOTFOUND - which led me to the "server" attribute in the apps.yaml.  I'll mark this closed, but wanted to leave this here in case someone runs into this.  This was difficult to find since the start-up ran correctly, but the schedule didn't work, so not sure what happened there.

Thanks for reporting it and good that you solved it.
Do I understand you correctly that the errors were caused by some incorrect value in the apps.yaml file?
I am sure we could add better error checking to Butler CW in general... Having good, descriptive error messages is always good of course.
On the roadmap is also to create standalone binaries of Butler CW. That would make it simpler to deploy (no need to install Node.js first), easier to run as a Windows service etc.
This has been done for some of the other Butler tools with excellent results, so it just might be coming to Butler CW too...

I appreciate the quick response, thanks for your work on this project, it's going to be a big help to us.
Yes, I debugged through VS Code and I found that it was the "server" value that was incorrect.  The strange thing is that it worked on startup, so I'm not sure why it's different.
Anyway I originally had:
https://server.mycompany.com
Where I actually just needed:
server.mycompany.com
Once I saw the actual underlying error message that helped direct me.

Ah yes... that field in the config apps.yaml file expects a host name or IP address, rather than a URL.
I looked at the README at https://github.com/ptarmiganlabs/butler-cw and it does mention that the server field should be an IP or Fully Qualified Domain Name (FQDN):
...
# Fields for each app:
# server: IP or FQDN of the Sense server where the app should be loaded
# appId: Id of app to load
# appDescription: Free text description of the app. Can be anything - no check is done Sense APIs using this text
# appStepThroughSheets: Set to true to have Butler CW step through all sheets of the app, triggering all charts etc to calculate in all sheets
# doInitialLoad: Set to true to do an initial load of this app when Butler CW is started.
# freq: Text value representation of how often the app should be loaded
...

Anyway - good that you got it working - well done!


Boss timer is off

The boss tracker lists Dracola on Vunira as "no chance (expected in 1 day)", but my team just found and killed it anyway.
I think the boss tracker should update twice per 24 hours:

once when the kill stats update (to update "recently killed")
once when server save takes place (to update the boss countdowns)

For the record, Tibia.com kill stats update daily around 04:00 CE(S)T. So you might want to schedule the task to pull in new kill stats data for 04:30 CE(S)T. That’s 03:30 UTC during CET, and 02:30 UTC during CEST.
Then there’s server save, which happens at 10:00 CE(ST). Thus, you might want to schedule the task to update the boss countdowns at 10:30 CET or so, which is 09:30 UTC during CET and 08:30 UTC during CEST.

I'm double checking everything and indeed Dracola should have a ~6% spawn chance yesterday on Vunira. What time (UTC plz) was it when the page displayed "no chance" for Dracola for you?
I believe the page revalidation hook failed for some reason (it happened before) and it had stale data instead
I'll add measures to make sure it revalidates correctly in the future

by the way, your automations check every 10 minutes for kill statistics updates (I swear this is not overkill, Tibia.com is often very unreliable and the best way to get around it is to always try to be on sync with it 😅)

I'm double checking everything and indeed Dracola should have a ~6% spawn chance yesterday on Vunira. What time (UTC plz) was it when the page displayed "no chance" for Dracola for you?

I posted this thread ~40 minutes after Dracola was found — so Exevo Pan was showing the wrong snapshot that day at 18:23 CET (17:23 UTC, or 2022-12-19T17:23:19Z) at least.

by the way, our automations check every 10 minutes for kill statistics updates (I swear this is not overkill, Tibia.com is often very unreliable and the best way to get around it is to always try to be on sync with it 😅)

Oofff, that sounds wasteful :P Have you considered only retrying if something goes wrong? Have you considered using the TibiaData API to work around the rate limiting (and to avoid the need to parse the HTML response yourself)? Anecdotally, I’m using TibiaData to pull in daily kill stats for https://github.com/tibiamaps/tibia-kill-stats just once per day and I haven’t had any issues.

For some reason, sometimes a few kill statistics pages will take longer to update:

My scripts were not dealing correctly with this, and would sometimes use stale data to calculate the next day's estimates. I just released a fix for this, so hopefully it wont happen again 😅


feat: Ability to configure cornerstone tools via extension configuration

@dannyrb I'll stop here :star:, let's discuss what we have in this branch. I'll avoid getting this pr too big so we can have a human reviewable pr. :ok_woman:

Let's put a bow on this:

Identify "wontfix" items for this PR that should result in new issues and follow-up items.
Create "User Cases" that tell the story of the features/functionality that are added here.

As a developer, I can now add custom tools by changing the cornerstone extension's configuration
As a user, I can do fancy new thing.

Anything breaking? Let's list those so we can draft a tiny statement.

Let's put a bow on this:

Identify "wontfix" items for this PR that should result in new issues and follow-up items.
Create "User Cases" that tell the story of the features/functionality that are added here.

As a developer, I can now add custom tools by changing the cornerstone extension's configuration
As a user, I can do fancy new thing.

Anything breaking? Let's list those so we can draft a tiny statement.

Won't fix:

Make a more generic context menu with customizable options and actions when calling show.
Refactor LabellingFlow to DialogService with DialogContent passed from this extension. (Maybe LabellingFlow doesn't need to an independent provider).
Pass the ServicesManager the "factory function" instead of the plain object.(reducing chances of accidental service use in core app)
Services should all have a 'common through all services' .create() method instead of a .createUIModalService() method.
Remove brushTool from our default tools. Include this by default in the seg specific extension.
UIContextMenuService and UILabelingFlowService look similar to Dialog. We should find a smarter way to say these a flavoured version of UIDialogService.
Simplify LabellingFlow by absorving LabellingManager logic.
Pass in rootConfig or applicationConfig to preInit/getModule.

User Cases:

As a developer, I can configure cornerstone tools via extension configuration.
As a developer, I can use a supported context menu provider and service which allows me to use or control the context menu dialog through a UI service in my extensions.
As a developer, I can use a supported labelling flow provider and service which allows me to control the labelling flow dialog through a UI service in my extensions.
As a developer, I can now use function type configuration which allows me to inject dependencies and have access to ServicesManager and CommandsManager.
As a developer, I can now have CommandsManager available to my extensions.
As a developer, I can now use LabellingFlow component independently of ToolContextMenu through a supported UI service.
As a developer, I can now use a new cornerstone command to get nearby tool data.

The closest thing to QA we have for user stories that impact developers are unit tests. I think we can forego the normal @mirnasilva approved process until we have a better way to run integration/e2e tests for extension and service changes.
It's interesting how much of this work hopefully has no impact on current functionality, but also improves the experience for others trying to tweak the viewer.
I think the only things we have to make sure we do before this can be merged are:

[ ] Update any documentation and code around the updated <App /> component props
[ ] Verify the cornerstone extension config changes work

[ ] Update the default config for a single commit, and share the Deploy Preview for it (then revert in next commit)?
[ ] Draft at least example schema for the cornerstone extension in it's readme

[ ] Make sure we note the breaking change

The closest thing to QA we have for user stories that impact developers are unit tests. I think we can forego the normal @mirnasilva approved process until we have a better way to run integration/e2e tests for extension and service changes.
It's interesting how much of this work hopefully has no impact on current functionality, but also improves the experience for others trying to tweak the viewer.
I think the only things we have to make sure we do before this can be merged are:

[ ]  Update any documentation and code around the updated <App /> component props

[ ]  Verify the cornerstone extension config changes work

[ ]  Update the default config for a single commit, and share the Deploy Preview for it (then revert in next commit)?
[ ]  Draft at least example schema for the cornerstone extension in it's readme

[ ]  Make sure we note the breaking change

@igoroctaviano, feel free to push back on, or add to, this list.

https://5dee6d5c04b544000807e9db--ohif.netlify.com/pwa/viewer/1.2.826.0.13854362241694438965858641723883466450351448


Bundle the hyperclick package

This will allow 3rd parties to start creating packages to allow users to perform actions by clicking on text.
Note the BSD-3-Clause license and patent grants.

@oclbdk Thanks for starting up this discussion in an issue. We like what you've done with hyperclick so far, but we aren't ready to bundle it with Atom yet.
Here are some we would need you to do:

[ ] Extract the ctags logic from symbols-view into a new package (called hyperclick-ctags or something) that provides a hyperclick.provider service. Our team uses this ctags functionality every day while developing Atom. This will allow us to start using hyperclick instead, so that we can start to find any bugs, missing features or performance issues with the package.
[ ] Show us some other of your open-source packages that use hyperclick.

Some things that your team and the @atom/core team need to discuss together:

[ ] Consider moving the ability to define mouse event handlers into Atom core, so that other packages besides hyperclick can do things like this using Atom's command system.
[ ] Add a way of selecting a suggestion when there are multiple suggestions for the same symbol. This should work like Atom's other select lists.

And some for the Atom team to do:

[ ] Discuss with our legal team whether we can bundle a package w/ hyperclick's license and patent grants.
[ ] Discuss if we have any issues w/ bundling a package that uses Flow and Babel.

These lists are a work in progress. @atom/core please feel free to add or adjust items.

I added a list item for moving the package repo into @atom.

Thanks for the comments! I'll get working on the features (i.e. ctags provider, selection for multiple suggestions).
If this code gets moved into @atom, we could probably use the MIT license. @jamesgpearce @bolinfest

After talking with a legal representative from Facebook, we should be able to use the MIT license.

Closing this out for now, will reopen once this is closer to a shippable state.


Improve font configurations for global and headings

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines.
[ ] Tests for the changes have been added (for bug fixes / features).
[x] Docs have been added / updated (for bug fixes / features).

PR Type
What kind of change does this PR introduce?

[ ] Bugfix.
[x] Feature.
[x] Code style update (formatting, local variables).
[ ] Refactoring (no functional changes, no api changes).
[ ] Build related changes.
[ ] CI related changes.
[x] Documentation content changes.
[ ] Other... Please describe:

What is the current behavior?
At the current status, generic font-sizes can't be configured by just editing the .yml configuration file. A fork of the theme is required, and an edit of some files is required.
What is the new behavior?
The new approach goes towards an easier configuration of font-size throught the yml file:

Add a possibility to configure them via the _config.yml file ( or data file )
Reflect the configuration in base.styl
Remove hardcoded font-sizes for headings inside post-title.styl
Improve documentation around font customization inside the _config.yml file

How to use?
In NexT _config.yml:
See _config.yml inside this PR
Does this PR introduce a breaking change?

[ ] Yes.
[x] No.

What about if user want to define not in px but in em?

Related to the em: I'm totally open to it. I just followed the existing piece of configurations in the _config.yml. I'm totally open to support it, but will just differ from the goal of this single PR.

Yep, need to think about em and px sizes selection. Because, mobiles and other devices for now became with different resolutions and NexT support mobile style adaptivity.

Totally agree! Thanks for the comprehension :)


Minor change in readme about non-required parameters

I think "non-named" word was ill-placed here (at least I did not understand what it meant). I tried to clarify this better and propose a solution to not get a exception.
Changes proposed in this pull request:
Slightly changed wording in README

Coverage remained the same at 99.775% when pulling bef6798711e6c332564617d0416e83760ce5fa4b on positron96:patch-1 into 0c352cd4da16f2105609463b55c69f0705b1b196 on zalando:master.

Coverage remained the same at 99.775% when pulling bef6798711e6c332564617d0416e83760ce5fa4b on positron96:patch-1 into 0c352cd4da16f2105609463b55c69f0705b1b196 on zalando:master.

:+1:


File extension not appending

Hi,
When I receive the uploaded file using .upload, the file extension is not appended to the file.fd.
Here is my code:
    this.req.file('photo').upload({
      dirname: require('path').resolve(sails.config.appPath, 'assets/images')
    }, async (err, [file]) => {
      if (err) {
        return exits.serverError(err);
      }
      console.log(file);
    });

According to the docs, it should append the extension by default. Is it something that I do wrong? Or is it some problem with the Skipper?

Hi @masious,
Just wanted to let you know we are moving all open Sails issue into one repo.
~Cheers!

Hi @masious thank you for bring this issue to light. Have you been able to find a solution to this issue? Also could you point me to the section in the Docs you are referring to?
Was it in the uploads section?

Hi @raqem.
I was not able to find a solution. I ended up hard-coding the extension!
No, I was referring to this. In saveAs description, it's said that:

By default, Skipper decides an "at-rest" filename for your uploaded files (called the fd) by generating a UUID and combining it with the file's original file extension when it was uploaded


Android Manifest not found during linking with rnpm phase

I ran ignite new app and got the following error:
`✔ Linking with rnpm
fs.js:584
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT: no such file or directory, open 'dmx-native-mobile-redux/android/app/src/main/AndroidManifest.xml'
at Error (native)
at Object.fs.openSync (fs.js:584:18)
at Object.fs.readFileSync (fs.js:431:33)
at Object.insertInFile (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/utilities.js:21:27)
at performInserts (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/app/index.js:60:13)
at AppGenerator._updateAndroidManifest (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/app/index.js:328:7)
at ChildProcess. (/Users/erose2/.nvm/versions/node/v5.4.0/lib/node_modules/generator-react-native-ignite/app/index.js:378:18)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)`

Checking on this now

I can't recreate this.  Can you verify you have the latest rnpm?

Also, verify you have the latest released ignite.  0.3.1

Additionally, can you verify that your AndroidManifest file exists or does not exist in the directory it is looking?

Running into the same with:
rnpm 1.8.0
ignite 0.4.0

Hrmmm odd!   @evanmrose - did you try re-installing ignite?
@hknd, what version was Ignite when you first installed it?  Maybe this is an upgrade issue?

@GantMan my first version was prolly 0.3.x. I did an upgrade to 0.4.0 and then I encountered that error. (then I resolved it via uninstall+install)

thanks!  It must have been some kind of upgrade limbo.  I'll close this ticket for now.   We'll revisit if we get anyone with this issue again.

I'm having the same problem.
Tried reinstalling, didn't help.
✔ Linking with rnpm
⠋ Linking with rnpmfs.js:549
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'my-app/android/app/src/main/AndroidManifest.xml'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)
    at Object.insertInFile (/usr/local/lib/node_modules/generator-react-native-ignite/utilities.js:21:27)
    at performInserts (/usr/local/lib/node_modules/generator-react-native-ignite/app/index.js:60:13)
    at AppGenerator._updateAndroidManifest (/usr/local/lib/node_modules/generator-react-native-ignite/app/index.js:328:7)
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/generator-react-native-ignite/app/index.js:378:18)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:821:16)

MuadDib:~ cihanbebek$ rnpm -V 1.8.0
'MuadDib:~ cihanbebek$ npm --version
3.9.5'

can you verify that the identified file exists? and at that path?  my-app/android/app/src/main/AndroidManifest.xml

Exact same issue here, the android folder does not exist.

awesome!   Thanks so much!  We're on it.

released 1.0.1 -> https://github.com/infinitered/ignite/releases/tag/1.0.1

Hi. I updated to the 1.0.1 version, and have rnpm at 1.8.0, but still getting the same error, even sticking to just alphanumeric characters in my project name. The file isn't present, nor are the dirs above it.
Thanks.

Hi @amrangaye  So, you checked and the file/folders don't exist?  There's our problem, so now we need to figure out why.
Can you please paste the path it's looking for, and also paste the path to your generated manifest file?   You must have a manifest file generated somewhere under the android folder.   I think identifying the difference here, we'll have the crux of the problem.

Sure. This is the path/error message:
Error: ENOENT: no such file or directory, open 'MyApp/android/app/src/main/AndroidManifest.xml
The android folder doesn't exist at all. Here is a list of dirs actually present in MyApp top level folder:
App			Tests			index.android.js	npm-debug.log
README.md		git_hooks		index.ios.js		package.json
Thanks.

ok, so something failed inside of generating the react native project at all.   So the follow-up steps will fail.
Can you provide the contents of npm-debug.log as that file is only generated when an npm failure happens.
Additionally, can you attempt to build a new react-native project and verify that works?
react-native init MyApp2  if it fails, please let us know what the error was.

OK so I looked in npm-debug.log, and it seems the initial set of problems were wrong permissions in my ~/.npm dir. I corrected those, and the script makes it a lot further, before failing. However now when I look in the MyApp dir there is no npm-debug.log file - is there another way of checking the error logs? Yes, react-native init MyApp2 works fine. Below is the error log for ignite:
⠋ Linking with rnpmfs.js:584
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'MyApp/android/app/src/main/AndroidManifest.xml'
    at Error (native)
    at Object.fs.openSync (fs.js:584:18)
    at Object.fs.readFileSync (fs.js:431:33)
    at Object.insertInFile (/usr/local/Cellar/node/6.2.0/libexec/npm/lib/node_modules/generator-react-native-ignite/utilities.js:21:27)
    at performInserts (/usr/local/Cellar/node/6.2.0/libexec/npm/lib/node_modules/generator-react-native-ignite/app/index.js:60:13)
    at AppGenerator._updateAndroidManifest (/usr/local/Cellar/node/6.2.0/libexec/npm/lib/node_modules/generator-react-native-ignite/app/index.js:328:7)
    at ChildProcess.<anonymous> (/usr/local/Cellar/node/6.2.0/libexec/npm/lib/node_modules/generator-react-native-ignite/app/index.js:378:18)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:827:16)`
```

So, that file not existing is key.   And the only way that file can not exist is if the react-native init MyApp is failing.   My guess is that we're somehow swallowing that error, but until we find out how/what it is I can't really identify how to stop it.
The line that runs that inside ignite is this:  https://github.com/infinitered/ignite/blob/master/ignite-generator/src/app/index.es#L193
As you can see we have stdio ignore for now, but in your personal node_module folder, you can turn int on, and see the feedback.   I know that this goes pretty deep, but whatever is affecting ignite, might be affecting any React Native project you build.

Btw, I am having this problem on OSX El Capitan. I was wondering if this might be an OSX specific problem?

I am using El Capitan
Hitting the same issue
✔ Found react-native
✔ Found git
✔ Found rnpm
✔ Getting ready for guests
✔ Running React Native setup (~ 1 minute)
✔ Downloading latest Ignite files
✔ Copying Ignite goodies
create IgniteTest/README.md
create IgniteTest/package.json
create IgniteTest/index.ios.js
create IgniteTest/index.android.js
create IgniteTest/git_hooks/pre-commit/lint.sh
create IgniteTest/Tests/Compiler.js
create IgniteTest/Tests/mocha.opts
create IgniteTest/Tests/Reducers/LoginReducerTest.js
create IgniteTest/Tests/Sagas/LoginSagaTest.js
create IgniteTest/Tests/Sagas/StartupSagaTest.js
create IgniteTest/Tests/Setup.js
create IgniteTest/App/Actions/Creators.js
create IgniteTest/App/Actions/README.md
create IgniteTest/App/Actions/Types.js
create IgniteTest/App/Components/AlertMessageComponent.js
create IgniteTest/App/Components/FullButton.js
create IgniteTest/App/Components/ProgressiveImage.js
create IgniteTest/App/Components/README.md
create IgniteTest/App/Components/RoundedButton.js
create IgniteTest/App/Components/Styles/AlertMessageComponentStyle.js
create IgniteTest/App/Components/Styles/FullButtonStyle.js
create IgniteTest/App/Components/Styles/ProgressiveImageStyle.js
create IgniteTest/App/Components/Styles/README.md
create IgniteTest/App/Components/Styles/RoundedButtonStyle.js
create IgniteTest/App/Config/DebugSettings.js
create IgniteTest/App/Config/PushConfig.js
create IgniteTest/App/Config/ReactotronConfig.js
create IgniteTest/App/Config/README.md
create IgniteTest/App/Containers/AllComponentsScreen.js
create IgniteTest/App/Containers/APITestingScreen.js
create IgniteTest/App/Containers/DeviceInfoScreen.js
create IgniteTest/App/Containers/ListviewExample.js
create IgniteTest/App/Containers/LoginScreen.js
create IgniteTest/App/Containers/PresentationScreen.js
create IgniteTest/App/Containers/README.md
create IgniteTest/App/Containers/Styles/AllComponentsScreenStyle.js
create IgniteTest/App/Containers/Styles/APITestingScreenStyle.js
create IgniteTest/App/Containers/Styles/DeviceInfoScreenStyle.js
create IgniteTest/App/Containers/Styles/ListviewExampleStyle.js
create IgniteTest/App/Containers/Styles/LoginScreenStyle.js
create IgniteTest/App/Containers/Styles/PresentationScreenStyle.js
create IgniteTest/App/Containers/Styles/README.md
create IgniteTest/App/Containers/Styles/RootStyle.js
create IgniteTest/App/Containers/Styles/ThemeScreenStyle.js
create IgniteTest/App/Containers/Styles/UsageExamplesScreenStyle.js
create IgniteTest/App/Containers/ThemeScreen.js
create IgniteTest/App/Containers/UsageExamplesScreen.js
create IgniteTest/App/Fixtures/boise.json
create IgniteTest/App/Fixtures/README.md
create IgniteTest/App/Fixtures/toronto.json
create IgniteTest/App/I18n/I18n.js
create IgniteTest/App/Images/BG.png
create IgniteTest/App/Images/ignite_logo.png
create IgniteTest/App/Images/ir.png
create IgniteTest/App/Images/tile_bg.png
create IgniteTest/App/Images/top_logo.png
create<EMAIL_ADDRESS>create<EMAIL_ADDRESS>create IgniteTest/App/Lib/Utilities.js
create IgniteTest/App/Navigation/index.js
create IgniteTest/App/Navigation/NavButtons.js
create IgniteTest/App/Navigation/NavigationBar.js
create IgniteTest/App/Navigation/NavigationBarRouteMapper.js
create IgniteTest/App/Navigation/README.md
create IgniteTest/App/Navigation/Router.js
create IgniteTest/App/Navigation/Routes.js
create IgniteTest/App/Navigation/Styles/NavigationStyle.js
create IgniteTest/App/Reducers/index.js
create IgniteTest/App/Reducers/LoginReducer.js
create IgniteTest/App/Reducers/README.md
create IgniteTest/App/Reducers/WeatherReducer.js
create IgniteTest/App/Root.js
create IgniteTest/App/Sagas/GetCityWeatherSaga.js
create IgniteTest/App/Sagas/index.js
create IgniteTest/App/Sagas/LoginSaga.js
create IgniteTest/App/Sagas/StartupSaga.js
create IgniteTest/App/Services/Api.js
create IgniteTest/App/Services/ExamplesRegistry.js
create IgniteTest/App/Services/FixtureApi.js
create IgniteTest/App/Store/ImmutablePersistenceTransform.js
create IgniteTest/App/Store/Store.js
create IgniteTest/App/Themes/ApplicationStyles.js
create IgniteTest/App/Themes/Colors.js
create IgniteTest/App/Themes/Fonts.js
create IgniteTest/App/Themes/Images.js
create IgniteTest/App/Themes/index.js
create IgniteTest/App/Themes/Metrics.js
create IgniteTest/App/Themes/README.md
create IgniteTest/App/Themes/Transitions.js
✔ Installing Ignite dependencies (~30 seconds-ish)
✔ Linking with rnpm
⠋ Linking with rnpmfs.js:549
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT: no such file or directory, open 'IgniteTest/android/app/src/main/AndroidManifest.xml'
at Error (native)
at Object.fs.openSync (fs.js:549:18)
at Object.fs.readFileSync (fs.js:397:15)
at Object.insertInFile (/usr/local/lib/node_modules/generator-react-native-ignite/utilities.js:21:27)
at performInserts (/usr/local/lib/node_modules/generator-react-native-ignite/app/index.js:60:13)
at AppGenerator._updateAndroidManifest (/usr/local/lib/node_modules/generator-react-native-ignite/app/index.js:328:7)
at ChildProcess. (/usr/local/lib/node_modules/generator-react-native-ignite/app/index.js:378:18)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:818:16)

Does the file get created at all?  Can you check for it now?
Also, can you do a normal react-native init SomeProject just fine?

the file does not get created at all
but I ran react-native init Project is fine

this happens every time?   @skellock  thoughts on how to best track this down?
@VansonLeung  - we can help create a branch version perhaps, that would be verbose in each step, rather than swallowing output.   Maybe then, it would identify the problem.

make sure you have latest ignite npm i react-native-ignite -g and try again.   If this fails, would you be open to a screen pairing session?

I can reproduce like this:
mkdir -p ~/tmp
cd ~/tmp
ignite new Test
cd Test
ignite new Boom

When it can't find AndroidManifest.xml, it doesn't even have an ios or android directory.
react-native init fails, but we still put the ignite bootstrap files in there.
Should be able to fix this pretty easily.
Sorry for the inconvenience.   This was a bit goofy to track down.

I was running into this issue on Win10 with cmder. There was no npm debug log. Running react-native init myapp gave me:
λ react-native init AppRN
   Looks like you installed react-native globally, maybe you meant react-native-cli?
   To fix the issue, run:
   npm uninstall -g react-native
   npm install -g react-native-cli

Doing this let ignite new run without error.

@will-hart - That's awesome info!   @skellock I'm thinking of building this check into our CLI, thoughts on best way?
https://github.com/facebook/react-native/blob/8295d27a906f850cefd86321d212162cba7ef296/local-cli/wrong-react-native.js

hey @GantMan any movement on this? I ran into another wonky issue:
__fbBatchedBridge is undefined
This led me to try to re-scaffold the app and start from scratch but I ran into this issue again.

I created a fresh project about an hour ago.  Can you give it a go?  I had no issue.
make sure you have everything upgraded/updated

Sorry, just going through issues and I've missed this one.
@GantMan We could put that check into the cli if you wanted ya.
Something like this might do the trick:
const cmd = 'npm -s -g ls --depth=0' // lists top level global installed packages
const ohCrap = Shell.exec(cmd, { silent: true }).stdout.indexOf('react-native@') >= 0

I mean, we'll only present the same error that react-native does anyway... but sooner.  I guess that's a little better though.

yeah, there's a good bit of checks/balances we can work in to try to help people with borked installs etc.   Would be cool to get other team members to maybe PR that.

Upgraded to #276.  Thanks all.


Add user-documentation to S4

Explain what set_class is, and give guidance to r-package authors.

Can we add an example here? Perhaps recreate something super simple like:
person_class <- setClass(
  "person",
  slots = c(name = "character", age = "integer")
)

person_class(name = "Lubo", age = 74L)
#> An object of class "person"
#> Slot "name":
#> [1] "Lubo"
#>
#> Slot "age":
#> [1] 74

Created on 2023-12-12 with reprex v2.0.2

This looks great. @CGMossa do we need to include an integer for Fred in the example since the s4 class requires it?

Ah, I think the doc examples are what are tripping me up. I think that they can be simplified. For example something like this would be handy to illustrate it.
I want to give this more thorough docs. But I think the addition alone is sufficient.
library(rextendr)

rust_function(r"{
fn tst() -> S4 {
    // instantiate the s4 class
    let class = S4::set_class("fred", pairlist!(x="numeric"), r!(())).unwrap();
    let mut fred = S4::new("fred").unwrap();
    fred.set_slot("x", 0.1);
    fred
}
}")


Not working when deployed (heroku)

This is not working for me when I deploy the app on heroku but working fine in local.
Is that the same for you?

Wanna use this package because a collection can have different categories of NFT and OpeanSea's API don't provide to filter by  trait

Deploying scrapers to heroku or other providers (google cloud, AWS) is always trickier than running from local environment, because opensea might be able to detect IP addresses of those providers.
I use google cloud (firebase functions) and it seems to work well with puppeteer, I will quickly test my setup and let you know.

Thank you for the fast answer!
Your package is just amazing and would love to work with it! if you have a solution I will be happy

I could not make it work on firebase cloud function as well (for now). What is weird is that I have a setup that is deployed and working, but could not reproduce. Sorry I can't give a more helpful answer as of now, maybe with a fresh mind I will be able to figure out and will post here.
If you find out something else please share, might be interesting for folks using heroku too.

Where is your working setup deployed? Cause I've just tried heroku but if I can use something else...

tried to put a node server to a dedicated NAS with your solution and I got this as error. My local my and this server got the same project (from git)

related to this:
https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-puppeteer-on-heroku

How can I add this on your package?

Thanks for reporting, it seems to be hard to deploy on any cloud infrastructure currently, also google cloud (see #40 )


fix: Update limit price on refresh

https://emurgo.atlassian.net/browse/YOMO-799?focusedCommentId=18108

@jorbuedo have tried locally and something seems of as is not updating the price 🤔 have added more logic on this issue in #2722

@SorinC6 @jorbuedo I've brought the changes

@SorinC6 @stackchain pretty sure https://github.com/Emurgo/yoroi/pull/2722 is wrong
asQuantity(formattedValue)

Is not ok. Formatted value can't be passed to asQuantity.
<AmountInput onChange={onChange} value={createOrder.limitPrice} editable={!disabled} />

createOrder.limitPrice is not directly assignable to the input
And
    {
      onSuccess: (poolList: Swap.Pool[]) => {
        const bestPool: Swap.Pool | undefined = poolList
          .sort((a: Swap.Pool, b: Swap.Pool) => a.price - b.price)
          .find(() => true)
        if (bestPool !== undefined) {
          const defaultPrice = createOrder.marketPrice
          const formattedValue = BigNumber(defaultPrice).decimalPlaces(PRECISION).toFormat(numberLocale)
          selectedPoolChanged(bestPool)
          limitPriceChanged(asQuantity(formattedValue))
        }
      },
    },
    ```
None of that should be modified from here. The pool change is already done on createOrder, and again limitPriceChanged can't receive that.

@stackchain now it should work

Passing tests, the ultimate frontier

fixes https://emurgo.atlassian.net/browse/YOMO-811 as well


update version and source sha256

Checklist

[ x] Used a personal fork of the feedstock to propose changes
[ na] Bumped the build number (if the version is unchanged)
[ na] Reset the build number to 0 (if the version changed)
[ x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


ft_printf not testing in Ubuntu

Hi and thank you for your work. I tried to run francinette on Ubuntu Budgie 22.10, but there is a problem when testing ft_printf.

execution.log

No probs. I'm done with this project anyway, just bringing out the issue !
Thanks again for your reply and for this nice tool :)

Hello, I had the same problem a few weeks ago and managed to fix it, so I'll just post it here if anyone needs it.
cd francinette/tests/printf/printfTester
open the makefile and search those lines
$(MANDATORY): %: mandatory_start $(UTILS_O)
	@$(CC) $(CFLAGS) -D TIMEOUT_US=$(TIMEOUT_US) $(UTILS_O) $(TESTS_PATH)$*_test.cpp -L.. -lftprintf -o $*_test && $(VALGRIND) ./$*_test $(TEST_NUMBER) && rm -f $*_test

$(BONUS): %: bonus_start $(UTILS_O)
	@$(CC) $(CFLAGS) -D TIMEOUT_US=$(TIMEOUT_US) $(UTILS_O) $(TESTS_PATH)$*_test.cpp -L.. -lftprintf -o $*_test && (VALGRIND) ./$*_test $(TEST_NUMBER) && rm -f $*_test

I don't remember why I deleted the $(UTILS_O) but to fix the issue you would need to add the flag -gdwarf-4
$(MANDATORY): %: mandatory_start
	@$(CC) $(CFLAGS) -gdwarf-4 -D TIMEOUT_US=$(TIMEOUT_US) $(UTILS) $(TESTS_PATH)$*_test.cpp -L.. -lftprintf -o $*_test && $(VALGRIND) ./$*_test $(TEST_NUMBER) && rm -f $*_test

$(BONUS): %: bonus_start
	@$(CC) $(CFLAGS) -gdwarf-4 -D TIMEOUT_US=$(TIMEOUT_US) $(UTILS) $(TESTS_PATH)$*_test.cpp -L.. -lftprintf -o $*_test && $(VALGRIND) ./$*_test $(TEST_NUMBER) && rm -f $*_test

Hello, I had the same problem and it vanished as soon as I upgraded valgrind to 3.20 version.
Now Tripouille's test runs OK.
But the test of fsoares does not show information and exits as it was ok but performs no tests at all (no OK, KO showing). I don't know if it's related to the valgrind upgrade...

@llevasse's fix didn't work for me, but @mrsourcerer's did. I had to update manually, as apt-get claims "valgrind is already the newest version (1:3.18.1-1ubuntu2)."
I followed these steps:
wget https://sourceware.org/pub/valgrind/valgrind-3.20.0.tar.bz2 (In the folder where you want to install Valgrind)
tar -xjf valgrind-3.20.0.tar.bz2 (If you get an error message, run sudo apt-get install tar)
cd valgrind-3.20.0
./configure --prefix=/usr/local
make
sudo make install

@llevasse's fix didn't work for me, but @mrsourcerer's did. I had to update manually, as apt-get claims "valgrind is already the newest version (1:3.18.1-1ubuntu2)." I followed these steps: wget https://sourceware.org/pub/valgrind/valgrind-3.20.0.tar.bz2 (In the folder where you want to install Valgrind) tar -xjf valgrind-3.20.0.tar.bz2 (If you get an error message, run sudo apt-get install tar) cd valgrind-3.20.0 ./configure --prefix=/usr/local make sudo make install

Just adding: Valgrind already has a newer version. Check https://valgrind.org/downloads/current.html or https://sourceware.org/pub/valgrind/?C=M;O=D for the most recent one.

Just upgrade Valgrind to version  3.22 and it will work


SSM Managed Instance tile includes system manager's instance name

We need an operator friendly name for a SSM managed Instance.
Please include AWS System Manager's "instance name" in the tile for a SSM Managed Instance.

Machine name now displays for managed instances. Support also added for EC2 instances.


Binding tools

need to deicide what to do about 'antibody' (and add 'nanobody')
other binding tools from #43 added

There are some conflicts now; maybe we should merge these kinds of issues a bit faster. How do you usually do with with FBBT? is anyone reviewing anything or are you just merging stuff yourself?

I will do it. This one is going into the 'tools' branch, which I will merge when the rearrangement is done.
'tools' branch has same issue as 'micropub' branch with moving relationships and stuff around.

No worries, did not want to rush anything. I would never merge anything edit file related in any case :P Just saw that this was open for a while.


Start documenting the code

When the very basics are in place, it's time to finally start documenting the code. Document the functions/structs/enums/modules that are already in the code at that point, and make sure to keep the docs updated in the future.

https://github.com/Oleksii-Kshenskyi/btagsil/issues/27 and https://github.com/Oleksii-Kshenskyi/btagsil/issues/28 have made a complete switch in the trajectory of the project. It's a different project being implemented with a completely different set of technologies now. I'll have to start everything from scratch. Until the prototype is implemented at least to the level of the Language Feast prototype, this issue is blocked.


Can't download model checkpoints and data

Can't download model checkpoints and data by this links: https://people.eecs.berkeley.edu/~jathushan/projects/4dhumans/hmr2_data.tar.gz
https://people.eecs.berkeley.edu/~jathushan/projects/4dhumans/hmr2a_model.tar.gz

You should be able to download the data by running wget <link>.


Only expire on full metaspace if GC rate is high

The metaspace expiration strategy expired daemons too eagerly.
It only looked at the space, but not whether the GC was busy.
A full metaspace alone is no big problem and happens very easily
with Gradle due to the many soft reference caches. These soft refs
are only cleaned up when the JVM runs out of memory.
The strategy will now only expire the daemon if metaspace is full
and the GC fails to free up memory (i.e. there is a real leak).
I noticed this when switching tasks to the worker API with classloader
isolation. Information about the classes is saved in the cross build cache
and only cleaned up when the JVM is about to run out of memory. This
lead to perfectly healthy daemons being expired because metaspace went
over the 80% threshold. After this fix, Gradle lets the JVM do the soft ref GC
and metaspace is freed up.
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test this please

OK, I've already triggered ReadyForMerge build for you.

@oehme looks like the 'expires daemon when metaspace leaks' tests are failing

@JLLeitschuh so the problem with that integration test is that it doesn't actually test garbage collection. It only pushes events directly into the GC monitoring service, essentially repeating what the unit test already covers. I've adjusted it to the events that the class expects, but that doesn't actually test whether a real leak will lead to the desired expiration.
I also noticed that my logic was wrong, since I was testing for gcRate on the non-heap space, but the collection would actually take place on the heap. This wouldn't have been caught by the test above, since it just mirrors the production logic.

Alright, I found and fixed DaemonPerformanceMonitoringSoakTest and added a metaspace test case to it. More comments inline.

@oehme :architecture-test:checkBinaryCompatibility test is failing
https://travis-ci.org/github/gradle/gradle/builds/744627669#L6527

It passes for me locally, is there anything special going on on CI?

@Mergifyio rebase

I think this issue is because we just split to the release branch and we're having issues comparing the wrong versions. A rebase should fix this issue.

@oehme can you rebase?

@bot-gradle test this please

OK, I've already triggered ReadyForMerge build for you.

Sorry I had pushed an unused import, please try again.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

Well, seems this is already proving useful - There seems to be a memory leak in the Android plugin, which was previously ignored because the daemon would just silently restart when metaspace reaches 80%. Now it waits till there is pressure, which means the metaspace errors sometimes become visible to the user. We should find and fix that leak.

@bot-gradle test this please

OK, I've already triggered ReadyForMerge build for you.

Seems that it fails even with more recent Android versions, so I'll have to dig deeper :/

I'm afraid this test can only be fixed with the nuclear option (one daemon per plugin combination), because the Kotlin plugin keeps a connection to its compiler daemon open. This open connection prevents the Kotlin plugin classloader from ever being garbage collected. Maybe someone from JetBrains could comment on this and propose solutions, but it's a very uncommon use case. We're switching between dozens of combinations of Kotlin/AGP, which no normal user would do.

All green now, is this good to go from your side or would you like me to change anything else?

@wolfs @blindpirate I'm going to leave this for you.

Ping :)

Ping :)

@oehme FYI, this was reverted on master because it exposed a new problem. We actually do have a metaspace leak (tied to the Kotlin compiler) and our eager expiration of the daemon was masking that.
This may get put back once the underlying metaspace problem gets fixed.

I see, can you point me to the Kotlin issue?

I'm not sure it has been reported to JetBrains yet but the root cause seems to be JDK-8260621 which is triggered by the following code in the Kotlin compiler:
https://github.com/jetbrains/kotlin/blob/2d875a9cb47a3d0be1dcf85f3fbeb48619671b11/compiler/cli/src/org/jetbrains/kotlin/cli/jvm/modules/CoreJrtFileSystem.kt#L40


gestalt-framework 1.0.0 launcher release

added eula to licenses and requirement in config
removed mesos config from gestalt launcher
added lambda.scale-down-timeout config for gestalt-framework launcher
updated docker images
added config for laser min/max port range, injected into launcher payload
added database.num-secondaries config
removed defunct config for framework launcher

@pyronicide , anything else that i need to do here?

@cgbaker looks good to me, did you test install it?

Many, many times :)
I've been running it from https://universe.galacticfog.com for a few weeks
for internal and customer use.
On Tue, Feb 7, 2017, 20:45 Joerg Schad<EMAIL_ADDRESS>wrote:

@cgbaker https://github.com/cgbaker looks good to me, did you test
install it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mesosphere/universe/pull/944#issuecomment-278203775,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmPTwDdHGU_sjmMdMTbpgisA4Edwv0Aks5raR49gaJpZM4L4wb2
.

LGTM


Restrict version of tenacity

A bug was discovered when the related code was in the CLI repo. We
need to restrict the version of tenacity pulled in by
langhchain-text-splitters.
Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

This is a trivial dependency update that has no functional impact in practice since it's identical to what instructlab has in its requirements.txt, so I'm going to merge


Update the use_certificate docs

Note that calling the use_certificate functions will replace any existing
certificate of the same type. The same thing applies for private keys.
Fixes #2147

Pushed. Thanks.


Missing RoleBinding for Group and User

Is your feature request related to a problem? Please describe.
When we perform a kubectl rolesum -k Group or kubectl rolesum -K User, the RoleBindings in the current namespace are not returned.
Describe the solution you'd like

When -n <namespace> is specified or the current context has a namespace, the command should return the ClusterRoleBindings and the RoleBindings.
When a namespace is not set, only ClusterRoleBindings are returned.

Describe alternatives you've considered

A flag could be added to ignore namespace --ignore-namespace | --cluster-only in case we cannot know if a namespace is set or not.

Additional context
We were trying to use the extension to summarize the permission of an user or AD group. Most of the permissions are given at the namespace level.
Problem started after fix for https://github.com/Ladicle/kubectl-rolesum/issues/29

I'm seeing the same issue, where I have a clusterrole, a service account in one namespace, and rolebindings in other namespaces binding the two. Pretty much the setup described here


Address issues with revert in Edit Data and also add trim to string data from cells.

This is to fix an issue with edit data upon revert for an invalid edit causing the current Cell to become reset when it should only be done for manual revert. (This results in additional edits after the revert on the cell not working until you move to a different row or refresh the edit session entirely).
Additionally, this PR addresses a bug where empty spaces at the end are a part of the value retrieved from the cell and that failure to delete those or overwrite them causes a "exceeded length" error, this PR adds trimming to values from the cell (and it still registers as being unchanged by the editor).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.002%) to 41.571%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
52.03%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
30785

Relevant Lines:
69355

💛  - Coveralls

Issue has been linked


Respond to presence subscriptions

Some clients send presence subscriptions. Reply to them as the RFC requires. I'm not yet entirety sure what semantics we should use here since SMS doesn't have a native notion of presence.

Reply to them as the RFC requires

Here's a sample of the relevant communications:
<!-- from client to component -->
<presence
    type='subscribe'
<EMAIL_ADDRESS><EMAIL_ADDRESS>/>

<!-- reply from component back to client -->
<presence
<EMAIL_ADDRESS>    id='xk3h1v69'
<EMAIL_ADDRESS>    type='subscribed' />

There are some important rules about JID validation, etc, but that's the gist of it.

In response to a subscribe request, we should also send a presence stanza indicating that the client is available. That should make it clear to users that one can send an SMS at any time.


Fix BCDC Datasets out of sync

Feature branch: https://api-services-portal-feature-bcdc-sync-fix.apps.silver.devops.gov.bc.ca/signout

Fixes #810


Can use fabio to deal HTTP2.0 request

can use Fabio to deal HTTP2.0 traffic , that means Fabio can support HTTP2.0 Agreement ?

Fabio acts as an HTTP/2 server but will not make HTTP/2 requests to the backend servers. Since the backend servers are usually physically close to fabio this isn't too much of a problem.
Internet - HTTP/1.1 or HTTP/2 -> fabio - HTTP/1.1 -> server

Does that answer your question?

I'll close this for now. Feel free to comment or re-open.


Class 'Dompdf\Exception' not found

Hey, I'm Getting an error in my callback url!
Controller Code:
    $transaction = PaytmWallet::with('receive');
    $response = $transaction->response();
    $order_id = $transaction->getOrderId();
    if($transaction->isSuccessful()) {
        Order::where('order_id', $order_id)->update(['payment_status'=>'success','transaction_id'=>$transaction->getTransactionId()]);
        dd('Successfully paid!');
    } else if($transaction->isFailed()) {
        Order::where('order_id', $order_id)->update(['payment_status'=>'failed','transaction_id'=>$transaction->getTransactionId()]);
        dd('Payment Failed!');
    }

My Route is a post route with CSRF Protection disabled.
Error ->
(1/1) FatalThrowableError
Class 'Dompdf\Exception' not found
in PaytmWalletProvider.php (line 50)
at PaytmWalletProvider->response()
in OrderController.php (line 186)
at OrderController->paymentCallback(object(Request))
at call_user_func_array(array(object(OrderController), 'paymentCallback'), array(object(Request)))
in Controller.php (line 55)

Hi @farazappy
This issue is not related to this package. Dompdf is not used in this package.
In case if you are using Dompdf in your application verify its installation.
If this answer helps please close the issue or attach the screenshots of your error page.

I'm not using Dompdf, It's in your source  file :
<?php
namespace Anand\LaravelPaytmWallet\Providers;
use Dompdf\Exception;
use Illuminate\Http\Request;
require __DIR__.'/../../lib/encdec_paytm.php';
class PaytmWalletProvider{
To throw checksum did not match exception, I guess.

Hi @farazappy
My bad.
Released a patch  https://github.com/anandsiddharth/laravel-paytm-wallet/releases/tag/v1.0.6


chore: upgrade argo-ui v2.5.0

mainly upgrade rxjs 6.x.
@types/react-form/react-helmet/react-autocomplete are deleted from argo-ui, but argo-workflows uses them.
yarn upgrade argo-ui@"https://github.com/argoproj/argo-ui.git#v2.5.0"
yarn add -D '<EMAIL_ADDRESS>'<EMAIL_ADDRESS>'<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is required for https://github.com/argoproj/argo-workflows/pull/7387

autocomplete

logs
https://user-images.githubusercontent.com/915731/150431541-8eb11c6e-a32a-4576-bb2a-b17d22ae12a6.mov

dropdown

timeline
https://user-images.githubusercontent.com/915731/150432310-9ea2f48a-50a3-4d5e-976f-325a2cfd2e88.mov

Fixed on master. Please sync with master to get working.

Can I ask for screenshots to demonstrate this is working ok please? Sometimes dep changes break stuff.

yep, I'm working to do it and paste in this PR description. Now WIP.

@alexec Now argo-ui v2.5.0 upgrade ready for review. Evidence screenshots are put on this PR description.


[bug] open cl rendering constantly crashes.

Build 2.3b2. System. 1700x, 2x vega 56, 56gb of ram.
Issues. Upon building open cl kernel, on any file. There is a near 90% chance it will crash during the build or mid render. These crashes havent happened on cpu. Its on any file. Even the luxcore demo files have crashed/hung.

It sounds like  a driver related problem. What operating system are you using ?
You should try to run LuxMark few times and check if it happens with LuxMark too.

Windows 10, and so far, changing drivers hasnt done much. Is there a version of luxmark that uses the 2.3b2 compiliers? 2.2 is crash free.
Sent from my iPhone

On Feb 29, 2020, at 5:52 AM, David Bucciarelli<EMAIL_ADDRESS>wrote:

It sounds like a driver related problem. What operating system are you using ?
You should try to run LuxMark few times and check if it happens with LuxMark too.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I assume the problem is something in your setup, software (likely the drivers) or hardware related. LuxMark has been tested for years and it is known to work. If it doesn;t work, the problem is in OS/Drivers/Hardware.
Anyway, the v2.2 works but v2.3b2 crashes, it is a bit different. However there must be something specific of your setup triggering the problem: does it happen even if you use a single GPU ?

Yeah. 2.2 has no issues what so ever. The 2.3b2 though. Single gpu, 20.2.2, 20.2.1, 19.5.1, all hang at “compiling blender kernals” systems remains responsive and doesnt crash. I dont think its the drivers
Sent from my iPhone

On Mar 1, 2020, at 3:27 AM, David Bucciarelli<EMAIL_ADDRESS>wrote:

I assume the problem is something in your setup, software (likely the drivers) or hardware related. LuxMark has been tested for years and it is known to work. If it doesn;t work, the problem is in OS/Drivers/Hardware.
Anyway, the v2.2 works but v2.3b2 crashes, it is a bit different. However there must be something specific of your setup triggering the problem: does it happen even if you use a single GPU ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeah. 2.2 has no issues what so ever. The 2.3b2 though. Single gpu, 20.2.2, 20.2.1, 19.5.1, all hang at “compiling blender kernals” systems remains responsive and doesnt crash. I dont think its the drivers

Are you sure it doesn't hang but takes a very long time to compile (something like 10 minutes) ? Is it the same with any scene ? Including a simple one, like the startup scene with just a cube ?

Any progress with the latest version ?

With the full release it has improved even more, however i tend to have issues with super high poly scenes. (9+mil face things, aka baking stuff) sometimes when rendering that High poly of a scene, it sometimes crashes. it always gets through building open cl kernels now, All crashes I've had have been mid render. I want to say 90%-95% of my renders go through.
Btw, stay safe and healthy.
Sent from my iPhone

On Mar 23, 2020, at 3:43 AM, David Bucciarelli<EMAIL_ADDRESS>wrote:

Any progress with the latest version ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Going to close this one because I doubt we can do anything else.


Remote test Project.toml, update ClimaCore compat

This PR removes the test Project, so that we can test with ClimaTimeSteppers>test, and widens the ClimaCore compat, which seems to be needed to merge #248.

CI takes a while, so I'm going to add this to the merge-queue. If any of the reviewers see an issue, please feel free to stop

There is a import MPI missing

I think that this might be running into https://github.com/JuliaLang/Pkg.jl/issues/3389. Also, I've now realized / remembered that we can no longer run test tests with julia --project test/runtests.jl due to https://github.com/JuliaLang/Pkg.jl/issues/1233.

I think that this might be running into JuliaLang/Pkg.jl#3389. Also, I've now realized / remembered that we can no longer run test tests with julia --project test/runtests.jl due to JuliaLang/Pkg.jl#1233.

What issue are you seeing specifically?

Maybe https://github.com/JuliaTesting/TestEnv.jl is a good temporary workaround, but it's not recommended to add to CI. Maybe we can fix the mpi-Test specific issue separately.

The way I approached this problem in the other repos where I use a Pkg.test workflow is to define and use a .buildkite environment. This also helps in reducing instantiation time because the buildkite env is only instantiated once.
See, e.g., ClimaDiagnostics

Also, if you want to run with MPI, you have to use mpiexec/srun/MPITRAMPOLINE_EXEC

Yeah, that sounds fine to me. I think I'd rather tackle this in parts and fix one piece at a time. Going to split this PR up a bit.

Closes #331.


Karma pod labels and annotations

What this PR does / why we need it:
Allows to set up pod labels and annotations
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @davidkarlsen

/assign @davidkarlsen

/assign
/lgtm

/ok-to-test


Roll Engine from 59b01e0e5a3f to 08cc9e71145b (11 revisions)

https://github.com/flutter/engine/compare/59b01e0e5a3f...08cc9e71145b
2020-11-04<EMAIL_ADDRESS>[web] Put the paragraph painting logic in the Paragraph class (flutter/engine#22239)
2020-11-04<EMAIL_ADDRESS>Fix Linux handling of window exposure events (flutter/engine#22268)
2020-11-04<EMAIL_ADDRESS>Roll Dart SDK from a4fbabcd73dc to 57bb12dc24d2 (1 revision) (flutter/engine#22283)
2020-11-04<EMAIL_ADDRESS>Roll Skia from 6e7cfaff1817 to 0e54309477ac (2 revisions) (flutter/engine#22281)
2020-11-03<EMAIL_ADDRESS>Roll Skia from dffd20efe95c to 6e7cfaff1817 (37 revisions) (flutter/engine#22277)
2020-11-03<EMAIL_ADDRESS>Switch Windows embedding to proc table embedder API (flutter/engine#22211)
2020-11-03<EMAIL_ADDRESS>Make some errors more idiomatic (flutter/engine#22261)
2020-11-03<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from oLF1FW-gC... to Esyuo1am1... (flutter/engine#22276)
2020-11-03<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 6yEx5GNGG... to o45EAhxJZ... (flutter/engine#22271)
2020-11-03<EMAIL_ADDRESS>Roll Dart SDK from b43baaaa477d to a4fbabcd73dc (1 revision) (flutter/engine#22269)
2020-11-03<EMAIL_ADDRESS>[web] Canoncalize font family on input fields (flutter/engine#22215)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from oLF1FW-gCLh0 to Esyuo1am1BKs
fuchsia/sdk/core/mac-amd64 from 6yEx5GNGGI2Y to o45EAhxJZa8d
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


Update scala3-library to 3.1.2

Updates org.scala-lang:scala3-library from 3.1.1 to 3.1.2.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (3.1.1).
You might want to review and update them manually.
src/main/scala/scala-cli-conf.scala
website/yarn.lock

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #462.


Wrapper missing in production build

Bug Report
In gatsby-theme-docz you can redefine wrapper.js file which should be applied to every page. This is very convenient for example to put styled-components'  there.
It works in dev mode just fine, but generates errors during docz build and when you try to run production build, there is no theme.
To Reproduce

Create src/gatsby-theme-docz/wrapper.js with component, that returns, say, <h1>Hello world </h1>
Run dev mode
It's there
Run docz build && docz serve
It's not there

Expected behavior
5. It's still there :)
Env
<EMAIL_ADDRESS>Additional context/Screenshots
My wrapper:
// src/gatsby-theme-docz/wrapper.js
import React from "react";
import { theme } from "somewhere"
import { ThemeProvider } from "styled-components";

export default ({ children }) => {
  return (
    <ThemeProvider theme={theme}>
      <>{children}</>
    </ThemeProvider>
  );
};

Could you give 2.0.0-rc.28 a try ?
I wasn't able to reproduce the issue with it.

Closing this for inactivity.
Feel free to re-open if the issue reoccurs.


Update to Apache Lucene 9.11.0

Description
Update to Apache Lucene 9.11.0
Related Issues
N/A

Check List

[X] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌ Gradle check result for 38fe0b1: FAILURE

https://github.com/opensearch-project/OpenSearch/pull/14039

@msfroh please, whenever you have time (I will make sure 2.x would have all related changes after 2.15.0 cut)

@reta manual backport sadly, please


cilium, signal: trigger gc when needed upon upsert service

This change is

Coverage increased (+0.03%) to 45.587% when pulling fc070d3fa59b87b4b21101cb0a666e6df4423359 on pr/gc-on-svc-update into 6d583fddff183b81b3a03400011d89bed31c503e on master.


modify default version for rke2-capi-provider

capi_suse_rke2_bootstrap_control_plane_provider_version should be 0.2.2 which contains the patch for slemicro and rke2 installation @hardys

Solved in
https://github.com/suse-edge/metal3-demo/pull/37


DOC: Fix a name of option

[ ] closes #xxxx
[ ] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[ ] whatsnew entry

[Current coverage][cc-pull] is 84.38%

Merging [#13686][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master     #13686   diff @@
==========================================
  Files           142        142
  Lines         51223      51223
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits          43224      43224
  Misses         7999       7999
  Partials          0          0

Powered by Codecov. Last updated by [043879f...be9ec3f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/pydata/pandas/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/pydata/pandas/compare/043879fbb7de71605eed87991eb037c1917bace1...be9ec3fecf179129fc7400d276cf9eed23feeabe?src=pr
[cc-pull]: https://codecov.io/gh/pydata/pandas/pull/13686?src=pr

@yui-knk Thanks!