text:
Remove the build options that enable advanced POM support and Gradle metadata support

These options should be enabled in the model of the build, that is via the DSL or APIs, and not injected from the environment. We want to try very hard to avoid a situation where something that affects the meaning of the build is not defined in the build itself. Both of these features fit into this category, as they affect how Gradle interprets the inputs of the build and how consumers interpret the output of the build.
Expected Behavior
Builds are self contained and describe their requirements wrt dependency resolution.
Current Behavior
If someone needs a build option to enable one or both of these features, then their build is not self contained.

If we keep this only as a property, we should at least remove it from the public StartParameter API:
https://github.com/gradle/gradle/blob/master/subprojects/core-api/src/main/java/org/gradle/StartParameter.java#L870-L908

We do gradle.enableFeaturePreview(NAME)

Oh, of course... the native plugin for one.

After discussions, the idea would be to add the public api to Settings instead of Gradle thus narrowing the applicability. And leave core plugins needing to interact with it use internal APIs.

I'm going to throw a "spanner in the works" here and suggest that we consider ditching the entire 'feature preview' idea. Since I was the one who originally proposed it, I wonder now if it wasn't a great idea after all.
When we came up with the 'feature preview' idea originally, it had the following benefits:

Make it easy for people to try out the new features from the command line, to gather feedback
Avoid a matrix of options that need to be tested together
Allow us to make cross-cutting changes that only make sense for the entire build

However, 1) is being explicitly removed and in the end 3) didn't turn out to be required (now that pending dependencies are always enabled for resolution).
In the end, we've added 4 things:

The ability to publish gradle-metadata using maven-publish and ivy-publish
Looking for 'gradle-metadata' in a repository before falling back to ivy/pom files
Automatically mapping Maven scopes to variants
Constructing dependency constraints for POM files. This has 2 parts:
i) Creating a constraint for every 'optional' dependency
ii) Creating a constraint for every 'dependencyManagement' in a BOM

I think all of these features make sense on a per-repository basis, and I would like to suggest that instead of a separate featurePreview "feature", we add these as incubating properties on the repositories (where required).
So here's what I would propose:

We already have a metadataSources DSL that allows for 2), and we could easily honour that same DSL in publishing to determine if gradle-metadata should be published or not. That would solve 1).
We keep 3) and 4) bundled together under 'improved POM support', and we add that as an option to MavenArtifactRepository. (Or we could make them separate features on a repository, but we'd have to come up with decent names!)

Doing this would make the new dependency management features just like all of the other features we add to Gradle.

Add a new feature that changes behaviour, allow users to opt-in to the feature
At some stage, enable the feature by default, allowing users to opt-out of the feature if they really need to
Once the feature is stable, deprecate the opt-out option

Note that this is just a suggestion. I just went back and read the original email where this idea was proposed, and it sounds kind of compelling :).

authors: adammurdoch bigdaz jjohannes ljacomet melix


text:
storage OOM not proper handled by gradle

in memmory of  https://github.com/oehme

when we have storage OOM gradle doesn't sygnalize that, instead proper info we have a bullshit :)
$ gradle clean

FAILURE: Build failed with an exception.

What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at >https://docs.gradle.org/4.7/userguide/gradle_daemon.html
Please read the following process output to find out more:`

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log >output. Run with --scan to get full insights.

Unable to start the daemon process... when explicity run with false flag in props file
the next try maybe gradle didn't read the prop file proper .. so explicity set no deamon arg
$ gradle --info --no-daemon clean

Initialized native services in: /opt/gradle/ceph3us/native
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/4.7/userguide/gradle_daemon.html.
Starting process 'Gradle build daemon'. Working directory: /opt/gradle/ceph3us/daemon/4.7 Command: /opt/jdk1.8/bin/java -XX:+AggressiveOpts -XX:+UseG1GC -Xmn512m -XX:MaxMetaspaceSize=1g -XX:SurvivorRatio=40 -XX:+UseCompressedOops -XX:+UseCompressedClassPointers -XX:-OmitStackTraceInFastThrow -XX:SoftRefLRUPolicyMSPerMB=100 -XX:-HeapDumpOnOutOfMemoryError -Xms512m -Xmx3g -Dfile.encoding=UTF-8 -Duser.country=PL -Duser.language=pl -Duser.variant -cp /opt/gradle/lib/gradle-launcher-4.7.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.7
Successfully started process 'Gradle build daemon'
An attempt to start the daemon took 1.005 secs.

FAILURE: Build failed with an exception.

What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.7/userguide/gradle_daemon.html
Please read the following process output to find out more:

Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

still some daemon shit WTF ??? one more try brings same results of bulshit doeasnt reveal the TRUE CAUSE for BUILD FAILED
'$ gradle --debug --no-daemon clean'

{ unrelated sensitive data cut}
16:50:14.639 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
16:50:14.640 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: Gradle build daemon.
16:50:14.655 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTED
16:50:14.656 [INFO] [org.gradle.process.internal.DefaultExecHandle] Successfully started process 'Gradle build daemon'
16:50:14.656 [DEBUG] [org.gradle.launcher.daemon.client.DefaultDaemonStarter] Gradle daemon process is starting. Waiting for the daemon to detach...
16:50:14.657 [DEBUG] [org.gradle.process.internal.ExecHandleRunner] waiting until streams are handled...
16:50:14.659 [DEBUG] [org.gradle.launcher.daemon.bootstrap.DaemonOutputConsumer] Starting consuming the daemon process output.
16:50:15.611 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: DETACHED
16:50:15.611 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'Gradle build daemon' finished with exit value 0 (state: DETACHED)
16:50:15.611 [DEBUG] [org.gradle.launcher.daemon.client.DefaultDaemonStarter] Gradle daemon process is now detached.
16:50:15.613 [INFO] [org.gradle.launcher.daemon.client.DefaultDaemonStarter] An attempt to start the daemon took 0.982 secs.
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Unable to start the daemon process.
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] This problem might be caused by incorrect configuration of the daemon.
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] For example, an unrecognized jvm option is used.
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.7/userguide/gradle_daemon.html
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Please read the following process output to find out more:
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] -----------------------
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try:
16:50:15.620 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Run with --stacktrace option to get the stack trace.  Run with --scan to get full insights.
16:50:15.621 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
16:50:15.621 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Get more help at https://help.gradle.org

pleaes add OOM storage watcher during task execution that will throw some sort of StorageOOM exception
distracts from the fact that there was no memory left at the start of the gradle .. which should be signalized apriori any taskl start / evaluate
tneet to consider the SPACE
-- WHERE PROJECT IS EXECUTED (build output)
-- WHEN GRADLE WRITES  (cache, etc)
those places should be checked during start gradle (LOW MEM WARNING) and monitored as mentioned above
i have wasted 5 min befor i did to know the real cause..

@c3ph3us We meant it the first time. Please read our code of conduct and open an issue using appropriate language.

source: gharchive/issue

repo: gradle/gradle

license_type: permissive

license_source: github-api


text:
Revert changes to internal handling of JavaExec.classpath

This suffers from: https://github.com/gradle/gradle/issues/8755
The revert fixes:  https://github.com/gradle/gradle/issues/12832

@bot-gradle test this

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

source: gharchive/pull-request

authors: bot-gradle jjohannes


text:
Use less memory for the perf test JVM

5G seems to be too much. Let's see what happens if we run with 1G.

Seems to work just fine: https://builds.gradle.org/viewLog.html?buildId=38538082&buildTypeId=Gradle_Check_PerformanceTestTestLinux_Trigger

Looks like the flamegraph generation code needs a lot of memory: https://builds.gradle.org/buildConfiguration/Gradle_Util_Performance_AdHocPerformanceScenarioLinux/38579122
Maybe we could only increase the memory when capturing JFR profiles?

We decided to document the reasons why we use 5G memory for performance tests instead of reducing the memory for tests which run without profiler: https://github.com/gradle/gradle/pull/14794


text:
Include base branch in GitHubMergeQueueCheckPass's trigger rules

In this way, the GitHubMergeQueueCheckPass build will run on base branch (master/release etc.) so that we can see correct "X changes" message in branch builds.

The merge queue build has started. Click here to see all failures if any.

@blindpirate should we add this to release7x and release as well?

The merge queue build has started. Click here to see all failures if any.

I have cherry-picked to PR #27771.

authors: blindpirate bot-gradle cobexer


text:
Chore: upgrades rxjs resolution to 7.3.0

Opened this PR because of this comment.

@jackw seems like the build step plugin_workflow is stuck?

Not sure why this is stuck, might be because we stopped using the GitHub actions from https://github.com/grafana/plugin-workflows. I'm going ahead and merging this anyway because the Drone build is green.

@hugohaggmark - Can all the existing plugins use this resolution? will that cause any conflicting issues when using older versions of grafana with latest rxjs resolution?  Some plugin depends on @grafana/{ui/data/runtime/toolkit} packages with version 7.x

@hugohaggmark - Can all the existing plugins use this resolution? will that cause any conflicting issues when using older versions of grafana with latest rxjs resolution? Some plugin depends on @grafana/{ui/data/runtime/toolkit} packages with version 7.x

I think that is another issue that needs to be addressed in the future. I think right now we always target the latest version of Grafana. Please correct me if I'm wrong @jackw @mckn

@hugohaggmark - Can all the existing plugins use this resolution? will that cause any conflicting issues when using older versions of grafana with latest rxjs resolution? Some plugin depends on @grafana/{ui/data/runtime/toolkit} packages with version 7.x

I think that is another issue that needs to be addressed in the future. I think right now we always target the latest version of Grafana. Please correct me if I'm wrong @jackw @mckn

That is correct but we are planning on improving the toolkit in v8.3 to make it use template depending on its current version. It will resolve issues like this.

FYI. All the Grafana enterprise plugins are using @grafana/{ui/data/runtime/toolkit}:7.5.0 and performing rxjs resolution to 6.6.3.  They will stick with it atleast until next few months.  Wondering what impact they will have when customer uses latest grafana having this PR. Are they backward compatible?

authors: hugohaggmark mckn yesoreyeram


text:
Intellij version

Not sure if this is the right place for it, but I would love to see an Intellij verison of this plugin!

Great idea, unfortunately we don't have any bandwidth for it at the moment :(
Closing this issue as this repository is focused on the VSCode extension.

repo: grafana/grafana-vs-code-extension


text:
bzlmod support

Create bzlmod module extensions and submit an entry to https://github.com/bazelbuild/bazel-central-registry

Opened https://github.com/bazelbuild/bazel-central-registry/pull/923.

So sorry I did not notice it in the review. What's the best way to forward all the attributes rather than copy/pasting?

I'm not exactly sure; there are a lot of attributes that need to be forwarded but so you would want to do the equivalent of (**tag_class.attrs) on the call to the rule. I'm not sure if that works though? Can give it a try..

Resolved by #218. When you are done testing, I can cut a new patch release.

Also please feel free to send PRs as you are testing. Will make the whole process much easier. I no longer use this project in any major codebase, so the unit tests here are the only things I run.

The release notes for 0.10.2 have instructions on how to use  Bzlmod but how do we do that if https://github.com/bazelbuild/bazel-central-registry/pull/923 has not yet landed in the central registry?
From looking at your commit history you have an override like this, do still need something similar:
git_override(module_name = "com_grail_bazel_toolchain", remote = "https://github.com/grailbio/bazel-toolchain", commit = "cf915e5c7cfcd19a3e71de54e385e01240b865dc")

Yes, I had hoped that the inclusion into BCR would be quick but it has taken some time. git_override would be a good way to do this. You can keep the module_name to be "toolchains_llvm". I will add this detail to the release notes.

https://github.com/grailbio/bazel-toolchain/releases/tag/0.10.3

authors: jlisee jsharpe siddharthab

repo: grailbio/bazel-toolchain


text:
🛑 Grambling State University is down

In ec3bf97, Grambling State University (https://www.gram.edu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grambling State University is back up in c5ee342 after 15 minutes.

repo: gramblingstatewebmaster/upptime

license: MIT


text:
XMLWriter : have choice to only display the best solution

Currently it writes as much solution as there is room in memory + 1.
But in some case only the best one is needed.

Super! Thanks 👍

authors: braktar oblonski

repo: graphhopper/jsprit

license_source: bigquery


text:
whisper-merge.py fails

Using the latest release of whisper, whisper-merge.py fails with:
Traceback (most recent call last):
  File "/usr/local/bin/whisper-merge.py", line 32, in <module>
    whisper.merge(path_from, path_to)
  File "/usr/local/lib/python2.7/dist-packages/whisper.py", line 835, in merge
    (timeInfo, values) = fetch(path_from, fromTime, untilTime)
TypeError: 'NoneType' object is not iterable

http://stackoverflow.com/questions/25030467/getting-the-error-typeerror-nonetype-object-is-not-iterable-when-trying-to

Looks like we need to include that fix in 0.9.x and master...

I have tried implementing the second solution in that Stack Overflow link in attempt to fix this issue in my environment:
for archive in archives: # this line already exists   fromTime = int(time.time()) - archive['retention'] # add this line
While the exception is no longer an issue, my "to_path" file does not contain the data from my "from_path".
I suspect it is not that easy to fix this issue. Has anyone got whisper-merge to work as intended?

Looks like it's fixed on a master branch - https://github.com/graphite-project/whisper/blob/master/whisper.py#L925-L938

authors: NoMotion deniszh errodr sw0x2A

repo: graphite-project/whisper


text:
Add graph test command

This adds a new graph test command that can be used to run test commands against a (customizable) test environment (by default: Graph Node, Postgres, IPFS and Ganache in Docker Compose).
This provides a rough framework for writing integration tests where a subgraph is indexed against a fresh Graph node and tests can wait for it to be synced, run queries at specific blocks etc. It is a bit rough around the edges, so I'm tempted to move it into a beta subcommand, to be invoked as graph beta test [options] <test-command>.
Usage
graph test [options] <test-command>

Options:

  -h, --help                    Show usage information
      --compose-file <file>     Custom Docker Compose file for additional services (optional)
      --node-image <image>      Custom Graph Node image to test against (default: graphprotocol/graph-node:latest)
      --node-logs               Print the Graph Node logs (optional)

The <test-command> could be anything: it could be a shell script that builds and deploys a subgraph, it could be a JS test suite run with jest or it could be a Truffle test suite, run with truffle test.
Overriding the --node-image allows to use a custom build of Graph Node, which would be useful for running integration tests for every commit of Graph Node itself.
Overriding the --compose-file allows to e.g. use a different Ethereum provider than the default Ganache, making it possible to test subgraphs against mainnet for instance.
Example usage
Inside subgraph repository with contracts, Truffle migrations and Truffle tests:
graph test "truffle test"

Such an example setup can be found in https://github.com/graphprotocol/graph-cli/blob/jannis/graph-test/examples/basic-event-handlers/.

Subgraph: https://github.com/graphprotocol/graph-cli/blob/jannis/graph-test/examples/basic-event-handlers/subgraph.yaml
Truffle migrations: https://github.com/graphprotocol/graph-cli/tree/jannis/graph-test/examples/basic-event-handlers/migrations
Truffle config: https://github.com/graphprotocol/graph-cli/blob/jannis/graph-test/examples/basic-event-handlers/truffle.js
Tests: https://github.com/graphprotocol/graph-cli/blob/jannis/graph-test/examples/basic-event-handlers/test/handlers.js.

What graph test "truffle test --network test" in this example does is:

Start up the test environment (Graph Node, Ganache etc.)
Deploy the contracts to Ganache
Patch the subgraph manifest with the right addresses
Deploy the subgraph
Wait for it to be indexed
Run queries and verify their results
Tear down the test environment again

Steps 1 and 7 are provided by graph test. Step 2 is handled by Truffle. Steps 3-6 have to be implemented by the users themselves; we could provide more tooling for this over time.
Testing graph test itself
The above basic-event-handlers example is included in the Travis pipeline of graph-cli. The output from one of the previous test runs can be seen here: https://travis-ci.org/graphprotocol/graph-cli/jobs/633258441#L536-L568

I've added the following CLI flags:
--standalone-node to run tests using a Graph node on the host
--standalone-node-args to replace the default arguments passed to the standalone Graph node
--skip-wait-for-ipfs to skip waiting for IPFS to become available on localhost:5001
--skip-wait-for-ethereum to skip waiting for Ethereum to become available on localhost:8545
--skip-wait-for-postgres to skip waiting for Postgres to become available on localhost:5432

@davekaj All updated.

repo: graphprotocol/graph-cli


text:
/graphql endpoints should return a Content-Type header

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
/graphql endpoints do not return a Content-Type header; this leads to some proxies (i.e. Traefik) to 'auto-detect' the MIME type as text/plain causing the browser to not render the page.
The /graphql endpoint emitting a correct Content-Type header would mean that all content is rendered as expected, and not left to the behest of proxies.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
N/A
What is the expected behavior?
Header is emitted Content-Type: text/html

This is not only problem for /graphql but for any endpoint. Anything which doesn't return Content-Type header gets text/plain inserted by Traefik.
In other words, Content-Type header should be generated by http://127.0.0.1:8030 (index-node) and http://127.0.0.1:8000 (graph-node-http). I didn't see problem with http://127.0.0.1:8001 (graph-node-ws) but I imagine it may be also affected.

This affects anything, html, css, javascript.

authors: joe-bowman kucharskim

repo: graphprotocol/graph-node


text:
How to create user in hello world example? I have problem with DateTime type?

I am trying
mutation {
  createOneUser(data: {
    id: "1",
    email: "test@mail.com",
    birthDate: "2007-12-03"
  }) {
    id
    email
  }
}

But have error
Argument birthDate: Got invalid value '2007-12-03' on prisma.createOneUser. Provided String, expected DateTime.

I am trying
mutation {
  createOneUser(data: {
    id: "1",
    email: "test@mail.com",
    birthDate: { year: 2007, month: 12, day: 3}
  }) {
    id
    email
  }
}

But have error
Argument birthDate: Got invalid value
{
  year: 2007,
  month: 12,
  day: 3
}
on prisma.createOneUser. Provided Json, expected DateTime.

This is also invalid
Argument birthDate: Got invalid value
{
  date: '2018-06-29',
  dateTime: '14:30:00.000Z'
}
on prisma.createOneUser. Provided Json, expected DateTime.

Source:
https://medium.com/open-graphql/top-5-graphql-scalars-3f8a38965b53

From:
https://graphql.org/learn/schema/
In most GraphQL service implementations, there is also a way to specify custom scalar types. For example, we could define a Date type:

scalar Date

Then it's up to our implementation to define how that type should be serialized, deserialized, and validated. For example, you could specify that the Date type should always be serialized into an integer timestamp, and your client should know to expect that format for any date fields.

But I can't find any documentation about DateTime used in prisma


text:
🛑 GrauNeko.com is down

In 4b07ccd, GrauNeko.com (https://graueneko.com) was down:

HTTP code: 403
Response time: 1318 ms

Resolved: GrauNeko.com is back up in bdf95ae after 18 minutes.

repo: graueneko/status-page


text:
[BUG] Build Failures from Newsletter tests

:bug: Bug report
Current Behavior
See the build failures in #476
Expected Behavior
No build failure.
Minimal reproduction of the problem with instructions
See #476
What is the motivation / use case for changing the behavior?
Passing builds.
Environment

Daffodil version: X.Y.Z
Angular version: X.Y.Z

For Tooling issues:
- Node version: XX
- Platform:

Others:

@Nolan-Arnold #476  is causing a build failure as a result of a test in newsletter, can you take a look?

repo: graycoreio/daffodil


text:
Generic product package

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

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?
[x] Yes
[ ] No

Other information
I updated the category package and the demo app with the generic changes too. The next PR will be to remove the DaffProductUnion as well.

Why is product modification being removed? It should probably be in its own PR unless it causes problems with the generic stuff.

It was originally there as a stop-gap solution, because we couldn't figure out how to get the generic stuff to work. But yea, I remember trying to do the generic changes with the modification files, and something about it was annoying to deal with, so I just removed it. I can put it back though if you'd like

I can put it back though if you'd like

No I just wanted to know why it was being removed since it wasn't immediately obvious how it was related to the generics changes.

@griest024 I see what you mean with the adapter usage simplification too. I made that change

@lderrickable this needs a rebase, but otherwise, LGTM.

authors: damienwebdev griest024 lderrickable


text:
制作 Chrome App 版本的 Gmail

目前那个 Windowed Gmail 实在是太难用了。
Windowed Gmail 没有消除外层框架的外补，而且 Gmal 快捷键经常失灵，非常不爽。
我希望可以单独 Dock 到托盘，而且能够通过 badge 显示未读邮件数量。

Chrome 已经支持 Add to Applications..

repo: greatghoul/naodong

license: mit


text:
use in kotlin bug

this version doesn`t regist onStart(), it should be onCreate() regist

Sorry, I do not follow. Do you have a code example of what does not work?
Keep in mind that you can register(Object) wherever you want. Using onStart() is just a reasonable suggestion. -ut

repo: greenrobot/EventBus


text:
library "libjsc.so" not found

Hi author, thanks for this awesome library as an alternative to async storage.
I encountered this issue after upgrading from 1.1.0 to 1.4.0 on android. Build was succeeded but app crashed after launching in Release mode.
05-31 18:41:31.804 30033 30160 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libjsc.so" not found
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at java.lang.Runtime.loadLibrary0(Runtime.java:1016)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at java.lang.System.loadLibrary(System.java:1672)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.reactnativeleveldb.LeveldbModule.<clinit>(LeveldbModule.java:11)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.reactnativeleveldb.LeveldbPackage.createNativeModules(LeveldbPackage.java:19)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.ReactPackageHelper.getNativeModuleIterator(ReactPackageHelper.java:42)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.NativeModuleRegistryBuilder.processPackage(NativeModuleRegistryBuilder.java:42)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.ReactInstanceManager.processPackage(ReactInstanceManager.java:1347)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.ReactInstanceManager.processPackages(ReactInstanceManager.java:1318)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1240)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:131)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1023)
05-31 18:41:31.804 30033 30160 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:784)

I guess it has to do with this commit https://github.com/greentriangle/react-native-leveldb/commit/a2658307c2813ef8901e695a30c9c3697dd64d0e#diff-59c313fb0dfe322996885368a5a90d8f8400c2576bb64acc60467c2e79ecd2e9R42 (since version 1.3.0)
Any feedback on the issue is appreciated.
    react: 17.0.1 => 17.0.1
    react-native: 0.64.0 => 0.64.0
    enableHermes: true

You don't do any runtime specific stuff, do you? In that case it should build fine even if you didn't mention anything about hermes in your buildfile. @chinloongtan can you make sure that this is actually the error? There might be some other error some lines above or below the one you sent.

Hi @chinloongtan , did you find a solution to this issue, by any chance? I am now faced with the same issue, and would like to address fix it.

authors: chinloongtan mrousavy savv

repo: greentriangle/react-native-leveldb


text:
CSS prop doesnt have access to the theme

Seems like the last css prop in the object does not work properly 🤷🏻♂

A small repo with the reproduction can be found here https://github.com/ivanbanov/xstyled-single-css-prop-bug

Actually I double checked and it seems to be happening with all the last cssprops in the style object

Ok one more update, it seems to be connected to the importMap configuration as well https://github.com/gregberge/xstyled/issues/286
I removed it and things started working properly, the only limitation that I can see of not adding the importMap is that this bug https://github.com/gregberge/xstyled/issues/77 will still not be fixed even using Emotion11

I removed it and things started partially work, the styles are generated but inject in the wrong order

This was a misunderstanding of how styled wrappers work, as explained in #287 (now closed)

Actually I double checked and it seems to be happening with all the last cssprops in the style object

I agree, it only affects the last pair in the style object, and it's only broken with the macro.
Unfortunately I don't know anything about the macro (or very much about emotion since I don't use it). Perhaps you can debug more to figure out what needs to be fixed?

Ok, this seems to fix the problem:
cssPropOptimization: false

in the babel plugin configuration, from here: https://github.com/emotion-js/emotion/tree/main/packages/babel-plugin#csspropoptimization
I don't really know what that does, it just seemed suspicious :man_shrugging:
Maybe it deserves a change in the upstream, maybe in xstyled, maybe just in documentation. Pull request would be welcome if you're able to figure it out.
However that doesn't fix #286

Unfortunately, it didn't seem to work for me, I will research a bit more to understand what is going on, I post it here if I find a solution

authors: agriffis ivanbanov

repo: gregberge/xstyled


text:
Add a short cooldown for jumping

Solves the multiple frame jump problem I mentioned in #46, though there might be a more elegant solution.

I have some more changes from the same branch (change file organization of entity code and add basic AI) that i can make a PR for when this is closed.

repo: gregcman/sucle


text:
请问Python3在安装requirements.txt依赖时报错怎么办

下面是我的操作方法：
我通过如下方式创建虚拟环境并激活

然后安装 requirements.txt 时出错，如图

试了很久没找到解决方法，是什么原因呢，应该怎么操作才能安装好依赖。非常感谢哦！
环境:CentOS 7，Python 3.6.8

我又在win10(Python3.8)上试了，还是相同的问题呢，请问是什么原因呢

出现这个导入报错是因为 setuptools 46.0.0 版本删掉了弃用的 Feature。解决方法有三种，你可以任选一种：

激活虚拟环境后回退到旧版本，然后重新执行安装依赖：

(venv) $ pip install setuptools==39.2.0
(venv) $ pip install -r requirements.txt

改用 venv 模块来创建虚拟环境，默认会使用旧版本的 setuptools：

$ python3 -m venv venv

升级 MarkupSafe 到最新版本（因为你是从依赖文件安装，所以需要在 requirements.txt 里找到 MarkupSafe 这一行，然后把版本改成 1.1.1）：

MarkupSafe==1.1.1

https://discuss.helloflask.com/t/topic/458/3?u=greyli

已解决，谢谢！

很抱歉我遇到类似的问题

很抱歉我遇到类似的问题

很抱歉我遇到类似的问题
环境：MacOS  pyenv创建的pyenv-virtuals  3.6env

问题1:当我使用 pip install -r requirements.txt

当我输入： flask forge
提示：pyenv: flask: command not found

注意到： Error: pg_config executable not found.
尝试解决方法：
1.安装postgresq
brew install postgresql

2.找到相应的路径
我的路径:/usr/local/Cellar/postgresql/12.2/bin
尝试：
export PATH=/usr/local/Cellar/postgresql/12.2/bin:$PATH

3.解决问题
使用
pip install -r requirements.txt

安装成功

authors: Cyberbolt greyli pangzi499

repo: greyli/bluelog


text:
Question : usage / configuration per gpu

Hi,
Thank you for your work and the GPU sharing solution you provide here, which is right now, for me, the most elegant and practical way to solve the GPU pooling challenge.
I've began to use it on a server with 4 gpus, in a setup in which only GPU 0, at this time, is shared via nvshare.
For this, I compiled and installed nvshare, following your recommendations in the README.
Some of our users (Team A) are automatically affected to GPU 0, with CUDA_VISIBLE_DEVICES=0 and LD_PRELOAD=:/usr/local/lib/libnvshare.so
And everything works fine, they don't have to change anything in their code, and accommodate without difficulty the, sometimes, longer computation delays.
The other users (not so privileged ones) can set manually CUDA_VISIBLE_DEVICES to 1, 2 or 3, with LD_PRELOAD unset, but need to communicate with each over in order to avoid collisions.
Now I would like to create a team B whose users would be affected to GPU 1, over nvshare. These users would stick to the GPU 1 and the nvshare algorithm would not interfere with the loads on shared GPU 0.
For this, what should be done ? Ideally, the TQ should also be configurable per GPU.

Hi @t-arsicaud-catie ,
I'm really glad you and your team found nvshare useful!
What you describe in your question affects any nvshare deployment on a multi-GPU node.
Due to a lack of time, I hadn't been able to tackle this.
Here's what I have in mind. It seems to be quite straightforward:
Background
Communication
nvshare's communication protocol and scheduling mechanism is GPU-agnostic:

The only thing that nvshare-scheduler needs to know is  its socket path.

The only thing that libnvshare needs to know is the scheduler's socket path.

The only thing that nvsharectl needs to know is the scheduler's socket path.

All of the above obtain that path by calling nvshare_get_scheduler_path() from src/comm.c. This function currently appends the fixed string "scheduler.sock" to NVSHARE_SOCK_DIR.
What does "GPU 0" mean and where is it hardcoded?
"GPU 0", in the context of nvshare, refers to the GPU with index 0 when calling nvmlDeviceGetHandleByIndex() [1].

This ordering that NVML does is inconsistent with itself (from one reboot to another) as well as inconsistent with nvidia-smi. We will change to nvmlDeviceGetHandleByPciBusId() [2].

The only place where I've hardcoded a specific GPU index is at the idleness check of the early-release thread:
https://github.com/grgalex/nvshare/blob/9504cdcdcd21c6935f54877da677272e1493f081/src/client.c#L385
[1] https://docs.nvidia.com/deploy/nvml-api/group__nvmlDeviceQueries.html#group__nvmlDeviceQueries_1g4cc7ff5253d53cc97b1afb606d614888
[2] https://docs.nvidia.com/deploy/nvml-api/group__nvmlDeviceQueries.html#group__nvmlDeviceQueries_1gea7484bb9eac412c28e8a73842254c05
Changes we must make
Given the above, we should do the following:

Parse CUDA_VISIBLE_DEVICES during initialization of {client, scheduler, cli}, ensure it holds a single integer number. Default to 0 if missing. Fatal error if malformed.
Append the parsed value of CUDA_VISIBLE_DEVICES as the suffix to the scheduler socket in nvshare_get_scheduler_path(). The value will be /var/run/nvshare/scheduler_X.sock when CUDA_VISIBLE_DEVICES=X.
Ensure CUDA_DEVICE_ORDER=PCI_BUS_ID is set in the client's environment if CUDA_VISIBLE_DEVICES is also set. We need this for (4). In this way, we have consistent GPU indexing.
Replace nvmlDeviceGetHandleByIndex(0, ...) with nvmlDeviceGetHandleByPciBusId(X, ...) in the early-release thread initialization, where X is the parsed value from CUDA_VISIBLE_DEVICES.

New usage after merging changes

Make sure to also update the README in the PR.

For each GPU you want nvshare to manage, start an nvshare-scheduler instance in the following way:
sudo bash -c 'CUDA_VISIBLE_DEVICES=X nvshare-scheduler'

In the client application environment, export CUDA_VISIBLE_DEVICES=X in order to specify which GPU to use according to PCI order. If not specified, defaults to 0.

In the client application environment, export CUDA_DEVICE_ORDER=PCI_BUS_ID if you also exported CUDA_VISIBLE_DEVICES.

In the nvsharectl environment, export CUDA_VISIBLE_DEVICES=X to specify the GPU for which you want to configure the nvshare-scheduler instance.

@t-arsicaud-catie
Do you (or someone from your team) want to take this on and prepare a PR?
Otherwise, I can do it in my spare time, on a best-effort basis, unless you have any other suggestion.
Feel free to drop me an e-mail if you want to discuss something in private.

authors: grgalex t-arsicaud-catie

repo: grgalex/nvshare


text:
Remove beacon sponsorship

This is an old "addbeacon" command which allows users to ask other nodes to act as a proxy for advertising their own beacon in case they don't have enough funds. This function has to be enabled by proxy.
Funds are easy to come by today and since this is a potentially dangerous and has been used to DDoS testnet we should consider removing it.

I support the removal of the 'addbeacon' command, the majority of nodes online do not have this functionality enabled (has to be enabled within the config file) & it was indeed used to ddos the testnet a year ago.

I support this as well. The chain needs to be actively secured and functions that can be removed to do so without affecting the chain in a negative way should be considered. As for the DDoS risk it should be eliminated in this case or protective measures put in place to reduce that risk. Advertising beacons are now easier and if users need GRC there is active faucets to accommodate them so I don't see a need for this

Me too, more secure, no point mining this gold if we store it outside in view.

authors: Foggyx420 denravonska grctest philipswift

repo: gridcoin/Gridcoin-Research


text:
How to create text files?

I need to generate some text files as a part of our static file generation but I can't seem to find any option to do so.
The Page API needs a vuejs component as its template which in turn needs a root element.
I looked into server api and specifically afterBuild hook but that one doesn't provide access to graphql.
I would be able to do this if there was a way to access the output directory's path inside api.createPages but I can't find anything for that either.

If you just want to output text files as part of your static build, you can do that in the afterBuild hook.  All you need to do is to assign a variable that is scoped in your module.export function, then run your GQL query in the createPages hook to populate the variable, and then use the afterBuild hook to output it.  Something like this in your gridsome.server.js:
const fs = require('fs-extra')

module.exports = function (api) {

  let fileoutput

  api.createPages(async ({ graphql, createPage }) => {
    fileoutput = await graphql(`{
      yourGQLquery {}
    }`)
  })

  api.afterBuild(async ({ queue, config }) => {
    await fs.outputFile(path.join('./dist','sometextfile', fileoutput)
  })
}

authors: rezaalavi thinkflo

repo: gridsome/gridsome


text:
Nico

Se agregan las alertas de cuando no se puede canjear 3 tarjetas y el informe de un ataque.
Agrego la excepción del que un jugador no posee la tarjeta de cierto pais.

Agregue las alertas de cuando un jugador no puede realizar un canje multiple de tarjetas y de los resultados de un ataque


text:
Package fails to build on Xcode 14.3 beta.

When opening the package in Xcode 14.3 beta (14E5197f), the build fails with error 'StateObject' is only available in [macOS 11.0 | iOS 14.0] or newer.
Culprits are EnvironmentStateObject.swift line 253 and Query.swift line 172.
This StackOverflow thread seems to indicate that in runtime, accessing StateObject in iOS 13 would cause a exception to be raised, but I have not tested it myself.
Apple documentation says it is available in iOS 14.0+, macOS 11.0+, tvOS 14.0+, watchOS 7.0+, so maybe we could get a new version cut with those versions as minimum in the Package file?
Thanks!
🙇

Hello @paulo-bc,
Thank you for the report!

Version 0.6.0 has shipped 🚀

authors: groue paulo-bc

repo: groue/GRDBQuery


text:
arm64 support

Hi,
I read your article in https://medium.com/better-programming/improve-cluster-monitoring-with-network-mapping-in-grafana-fa8bb479fd47
Thank you for that. I tried Caretta on my hybrid home cluster that has hybrid architecture amd64 and arm64 and I see that you don't provide multi architecture images that run on both architectures.
So please add arm64 support.

Hey @dkrizic, PR #50 addresses this issue and adds support for arm64 :) Make sure to run helm repo update groundcover to run the latest version.

authors: dkrizic udiz

repo: groundcover-com/caretta


text:
IllegalStateError: Backoff in progress.

I'm attempting to use homebridge-dacp with an Apple TV 4K.  Setting up the pairing works, but then I get this…
Any ideas?
Thanks!
[2017-12-12 20:55:30] [DACP] The accessory Homebridge Apple TV Remote is announced.
[2017-12-12 20:55:30] [DACP] Attempting to reconnect to Homebridge Apple TV Remote in 0.1 seconds.
[2017-12-12 20:55:30] [DACP] The accessory Homebridge Apple TV Remote is announced.

/opt/node/lib/node_modules/homebridge-dacp/node_modules/precond/lib/checks.js:15
    throw error;
    ^
IllegalStateError: Backoff in progress.
    at Backoff.backoff (/opt/node/lib/node_modules/homebridge-dacp/node_modules/backoff/lib/backoff.js:38:13)
    at DacpAccessory.accessoryUp (/opt/node/lib/node_modules/homebridge-dacp/src/DacpAccessory.js:131:19)
    at _accessories.forEach.accessory (/opt/node/lib/node_modules/homebridge-dacp/src/index.js:68:19)
    at Array.forEach (<anonymous>)
    at DacpPlatform._onServiceUp (/opt/node/lib/node_modules/homebridge-dacp/src/index.js:66:23)
    at emitOne (events.js:116:13)
    at DacpBrowser.emit (events.js:211:7)
    at Browser._browser.on.service (/opt/node/lib/node_modules/homebridge-dacp/src/dacp/DacpBrowser.js:22:12)
    at emitTwo (events.js:126:13)
    at Browser.emit (events.js:214:7)

Thanks for the bug report. I'll fix this in 0.7.4.

I just published 0.7.4, which should hopefully take care of this issue. Feedback would be appreciated.

Works great.  Thanks, @grover!  And thanks for #5 too!

authors: darrylhodgins grover

repo: grover/homebridge-dacp


text:
pollable_epoll stucks.

We found some case caused pollable_epoll stack at https://github.com/grpc/grpc/blob/master/src/core/lib/iomgr/ev_epollex_linux.cc#L956
The bt shows results:
(gdb) thread apply all bt

Thread 5 (LWP 41882):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b19cb54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 4 (LWP 41850):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b218b54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 3 (LWP 41849):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b22fb54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 2 (LWP 41848):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b246b54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 1 (LWP 41792):
#0  0x00007f1d50aef3d0 in epoll_pwait () from target:/lib/ld-musl-x86_64.so.1
#1  0x000055c58421f958 in ?? ()
#2  0x00007ffdb9f12240 in ?? ()
#3  0x00007f1d4fdcf918 in pollable_epoll (deadline=<optimized out>, p=0x55c584250e60) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc:956
#4  pollset_work (pollset=0xffffffffffffffff, worker_hdl=<optimized out>, deadline=<optimized out>) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc:1144
#5  0x00007f1d4fdd393c in pollset_work (pollset=0x55c58421f958, worker=0x7ffdb9f12328, deadline=9223372036854775807) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_posix.cc:320
#6  0x00007f1d4fdf9126 in cq_pluck (cq=0x55c58421f820, tag=0x55c58427a060, deadline=..., reserved=<optimized out>) at /tmp/pear/temp/grpc/src/core/lib/surface/completion_queue.cc:1263
#7  0x00007f1d4fdb1106 in zim_Call_startBatch (execute_data=<optimized out>, return_value=0x7f1d50220f90) at /tmp/pear/temp/grpc/src/php/ext/grpc/call.c:454
#8  0x000055c581bf4734 in execute_ex ()
#9  0x000055c581b4382b in zend_call_function ()
#10 0x000055c581a57cc8 in ?? ()
#11 0x000055c581bf39a4 in execute_ex ()
#12 0x000055c581bf56e8 in zend_execute ()
#13 0x000055c581b534c3 in zend_execute_scripts ()
#14 0x000055c581af0af8 in php_execute_script ()
#15 0x000055c5817c6969 in ?? ()
#16 0x00007f1d50aec13d in __libc_start_main () from target:/lib/ld-musl-x86_64.so.1
#17 0x000055c5817c77d5 in ?? ()
#18 0x0000000000000000 in ?? ()
(gdb) c
Continuing.
^C
Thread 1 "php-fpm" received signal SIGINT, Interrupt.
0x00007f1d50aef3d0 in epoll_pwait () from target:/lib/ld-musl-x86_64.so.1
(gdb) thread apply all bt

Thread 5 (LWP 41882):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b19cb54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 4 (LWP 41850):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b218b54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 3 (LWP 41849):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b22fb54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 2 (LWP 41848):
#0  0x00007f1d50b223ad in __clone () from target:/lib/ld-musl-x86_64.so.1
#1  0x00007f1d50b1fb8c in ?? () from target:/lib/ld-musl-x86_64.so.1
#2  0x00007f1d3b246b54 in ?? ()
#3  0x0000000000000000 in ?? ()

Thread 1 (LWP 41792):
#0  0x00007f1d50aef3d0 in epoll_pwait () from target:/lib/ld-musl-x86_64.so.1
#1  0x000055c58421f958 in ?? ()
#2  0x00007ffdb9f12240 in ?? ()
#3  0x00007f1d4fdcf918 in pollable_epoll (deadline=<optimized out>, p=0x55c584250e60) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc:956
#4  pollset_work (pollset=0xffffffffffffffff, worker_hdl=<optimized out>, deadline=<optimized out>) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc:1144
#5  0x00007f1d4fdd393c in pollset_work (pollset=0x55c58421f958, worker=0x7ffdb9f12328, deadline=9223372036854775807) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_posix.cc:320
#6  0x00007f1d4fdf9126 in cq_pluck (cq=0x55c58421f820, tag=0x55c58427a060, deadline=..., reserved=<optimized out>) at /tmp/pear/temp/grpc/src/core/lib/surface/completion_queue.cc:1263
#7  0x00007f1d4fdb1106 in zim_Call_startBatch (execute_data=<optimized out>, return_value=0x7f1d50220f90) at /tmp/pear/temp/grpc/src/php/ext/grpc/call.c:454
#8  0x000055c581bf4734 in execute_ex ()
#9  0x000055c581b4382b in zend_call_function ()
#10 0x000055c581a57cc8 in ?? ()
#11 0x000055c581bf39a4 in execute_ex ()
#12 0x000055c581bf56e8 in zend_execute ()
#13 0x000055c581b534c3 in zend_execute_scripts ()
#14 0x000055c581af0af8 in php_execute_script ()
#15 0x000055c5817c6969 in ?? ()
#16 0x00007f1d50aec13d in __libc_start_main () from target:/lib/ld-musl-x86_64.so.1
#17 0x000055c5817c77d5 in ?? ()
#18 0x0000000000000000 in ?? ()

and the value of r, in this case, is 0
(gdb) b /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc:957
Breakpoint 1 at 0x7f1d4fdcf91f: file /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc, line 958.
(gdb) c
Continuing.
[Switching to LWP 41882]

Thread 5 "php-fpm" hit Breakpoint 1, pollable_epoll (deadline=<optimized out>, p=0x55c583ff8760) at /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc:958
958	in /tmp/pear/temp/grpc/src/core/lib/iomgr/ev_epollex_linux.cc
(gdb) print r
$7 = 0
(gdb) print errno
$8 = 0

We found this may happen when the number of php-fpm processes reached pm.max_children.
pm = dynamic
pm.start_servers = 28
pm.min_spare_servers = 28
pm.max_spare_servers = 56
pm.max_requests = 3000
pm.max_children = 400

This graph showed the situation when php-fpm processes reached pm.max_children.
almost half of the servers will return to normal status and remains servers are not so lucky.

Sorry for the late reply. I will be working on this with priority now. @axot  Can we get a reproducible test case and some base line information?

Which platform and version?
Which PHP version?
Which gRPC PECL extension version?
Can we get a simpler .conf file for your php-fpm setup (perhaps some smaller values for these so that it makes reproducing the issue easier?)

pm.start_servers = 28
pm.min_spare_servers = 28
pm.max_spare_servers = 56
pm.max_requests = 3000
pm.max_children = 400

Would be nice if we can get a docker image to reproduce this so that we are on the same page. Thanks.

I'm trying to reproduce this issue in my local environment, I will update the thread when it has done.

Any luck? I have a basic fpm - grpc environment setup but I couldn't reproduce the issue yet.

I did not reproduce this issue yet even use the same load environment with much lower stress.
This was the situation when this happened in the last month.

Which platform and version?
We performed an INSERT(Spanner) heavy load test inside GKE with nginx and php-fpm,
it started at 12:11, the php-fpm stucks from 12:30 and at the same time, we observed Spanner was starting split and caused very high latency, PHP client got many Deadline Exceeded.

Which PHP version?

# cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.9.3

# php-fpm -v
PHP 7.2.18 (fpm-fcgi) (built: May  4 2019 02:35:45)

Which gRPC PECL extension version?
1.20.0

Just to keep a log of what I tried here:
Environment: Ubuntu 16.04, PHP 7.0.33, gRPC 1.22.0, nginx/1.10.3, FPM/FastCGI.
Here's some relevant config from /etc/php/7.0/fpm/pool.d/www.conf:
pm = dynamic
pm.max_children = 5
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3

I have a simple Node gRPC server set up. A simple client.php script making one unary call per invocation of that PHP script.
$host = 'localhost:50051';
$client = new Math\MathClient($host, [
    'credentials' => Grpc\ChannelCredentials::createInsecure(),
]);

$dividend = 7;
$divisor = 4;
$div_arg = new Math\DivArgs();
$div_arg->setDividend($dividend);
$div_arg->setDivisor($divisor);
$call = $client->Div($div_arg);
p("Dividing $dividend by $divisor");
list($response, $status) = $call->wait();
p('quotient = '.$response->getQuotient());
p('remainder = '.$response->getRemainder());

Verified that it prints out what I expected if I request localhost/client.php from a browser.
Now I tried to load test this with the ab tool, which allows me to send many requests with some sort of concurrency. For example:
ab -n 100000 -c 10 localhost:8080/client.php
allows me to hit the client.php script 100k times simulating 10 concurrent requests at the same time.
This takes about 1.5 minutes to complete. During that time, I observed that

Running ps -ef | grep fpm

first shows that there are 2 php-fpm child processes at startup/idle time (as specified by the pm.start_servers = 2 directive). Like:

www-data  2083  1107 33 21:46 ?        00:01:44 php-fpm: pool www
www-data  2114  1107 36 21:47 ?        00:01:34 php-fpm: pool www

then, as the ab tool is underway, now there are 5 php-fpm child processes being run simultaneously (as specified by the pm.max_children = 5 directive).
I also run top in another tab to check up on these 5 php-fpm child processes. And observed that they are running just fine. With the memory usage steady at 0.0%

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 2169 www-data  20   0  532092  15192   9100 S  63.1  0.0   0:38.53 php-fpm7.0
 2114 www-data  20   0  532092  15188   9100 S  62.1  0.0   1:32.89 php-fpm7.0
 2164 www-data  20   0  532092  15188   9100 R  62.1  0.0   0:38.91 php-fpm7.0
 2083 www-data  20   0  532200  15192   9096 R  61.8  0.0   1:42.63 php-fpm7.0
 2119 www-data  20   0  532092  15192   9100 R  61.5  0.0   1:31.78 php-fpm7.0
 1049 stanley+  20   0  974068  43884  24828 S  34.6  0.1   0:56.11 node
 1158 www-data  20   0  125464   4248   2484 S  19.3  0.0   0:06.23 nginx
 2163 stanley+  20   0   35160   7112   4176 R  16.9  0.0   0:10.73 ab

When the ab tool finishes running, ps -ef | grep fpm shows that now there are 3 idle php-fpm child processes waiting ( I suppose something to do with the pm.min_spare_servers = 1 directive).

This is the ab tool output
$ ab -n 100000 -c 10 localhost:8080/math_client.php
This is ApacheBench, Version 2.3 <$Revision: 1706008 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking localhost (be patient)
Completed 10000 requests
Completed 20000 requests
Completed 30000 requests
Completed 40000 requests
Completed 50000 requests
Completed 60000 requests
Completed 70000 requests
Completed 80000 requests
Completed 90000 requests
Completed 100000 requests
Finished 100000 requests

Server Software:        nginx/1.10.3
Server Hostname:        localhost
Server Port:            8080

Document Path:          /math_client.php
Document Length:        282 bytes

Concurrency Level:      10
Time taken for tests:   80.804 seconds
Complete requests:      100000
Failed requests:        0
Total transferred:      42800000 bytes
HTML transferred:       28200000 bytes
Requests per second:    1237.56 [#/sec] (mean)
Time per request:       8.080 [ms] (mean)
Time per request:       0.808 [ms] (mean, across all concurrent requests)
Transfer rate:          517.26 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       4
Processing:     3    8   1.3      8      41
Waiting:        3    8   1.3      8      41
Total:          4    8   1.3      8      41

Percentage of the requests served within a certain time (ms)
  50%      8
  66%      8
  75%      9
  80%      9
  90%      9
  95%     10
  98%     11
  99%     11
 100%     41 (longest request)

All 100k requests completed successfully. And I observed that the PID of the 5 child php-fpm processes stay the same throughout all 100k requests. So there was no crash.

Hello, sorry for the delayed reply, I can not reproduce this in my local, for now, it happened again in our heavy load test.
Is it useful because I has a coredump here?

@axot We received the core dump file. Will look at it shortly. Just to clarify - the issue is still not reproducible at will, but only under certain load testing scenarios right?

@stanley-cheung Yes, I can not reproduce this locally, may need more hint. It happens in large scale load tests in my experience.

authors: axot stanley-cheung

repo: grpc/grpc


text:
iOS build via CMake, error configure

What version of gRPC and what language are you using?
v1.25.0 v1.26.0
C++
What operating system (Linux, Windows,...) and version?
MacOS 10.15.3
What runtime / compiler are you using (e.g. python version or version of gcc)
XCode 10.2.1
AppleClang
What did you do?
I'm trying to configure project via CMake for ios platform with own build of openssl 1.0.2 libraries (the same error appears without them) with this ios toolchain (have seen posts of successful grpc build with this toolchain)
cmake ../grpc \
>  -DCMAKE_TOOLCHAIN_FILE=../ios-cmake/ios.toolchain.cmake \
>  -D_gRPC_PLATFORM_IOS=ON \
>  -DPLATFORM=OS \
>  -DCMAKE_SYSTEM_NAME=iOS \
>  -DRUN_HAVE_STEADY_CLOCK=0 \
>  -DRUN_HAVE_POSIX_REGEX=0 \
>  -DRUN_HAVE_STD_REGEX=0 \
>  -Dprotobuf_BUILD_PROTOC_BINARIES=OFF \
>  -DgRPC_BUILD_CODEGEN=OFF \
>  -DCMAKE_BUILD_TYPE=Release \
>  -DgRPC_SSL_PROVIDER=package \
>   -DOPENSSL_ROOT_DIR=/Users/vladimir/Documents/projects/OpenSSL-for-iPhone/lib \
>   -DOPENSSL_INCLUDE_DIR=/Users/vladimir/Documents/projects/OpenSSL-for-iPhone/include \
>   -DOPENSSL_CRYPTO_LIBRARY=/Users/vladimir/Documents/projects/OpenSSL-for-iPhone/lib/libcrypto.a \
>   -DOPENSSL_SSL_LIBRARY=/Users/vladimir/Documents/projects/OpenSSL-for-iPhone/lib/libssl.a

What did you expect to see?
Successful configuration done, without errors
What did you see instead?
-- Using the default min-version since DEPLOYMENT_TARGET not provided!
-- Enabling bitcode support by default. ENABLE_BITCODE not provided!
-- Enabling ARC support by default. ENABLE_ARC not provided!
-- Hiding symbols visibility by default. ENABLE_VISIBILITY not provided!
-- Using NON-strict compiler checks by default. ENABLE_STRICT_TRY_COMPILE not provided!
-- Using C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
-- Using CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
-- Using libtool: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool
-- Configuring iphoneos build for platform: OS, architecture(s): armv7;armv7s;arm64
-- Using SDK: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.2.sdk
-- Using minimum deployment version: 9.0 (SDK version: 12.2)
-- Merging integrated CMake 3.14+ iOS,tvOS,watchOS,macOS toolchain(s) with this toolchain!
-- Using a data_ptr size of: 8
-- Using install_name_tool: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool
-- Enabling bitcode support.
-- Enabling ARC support.
-- Hiding symbols (-fvisibility=hidden).
-- Using libtool: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool
-- The C compiler identification is AppleClang 10.0.1.10010046
-- The CXX compiler identification is AppleClang 10.0.1.10010046
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/local/bin/git (found version "2.22.0")
-- git Version: v1.5.0
-- Version: 1.5.0
-- Performing Test HAVE_CXX_FLAG_STD_CXX11
-- Performing Test HAVE_CXX_FLAG_STD_CXX11 - Success
-- Performing Test HAVE_CXX_FLAG_WALL
-- Performing Test HAVE_CXX_FLAG_WALL - Success
-- Performing Test HAVE_CXX_FLAG_WEXTRA
-- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
-- Performing Test HAVE_CXX_FLAG_WSHADOW
-- Performing Test HAVE_CXX_FLAG_WSHADOW - Success
-- Performing Test HAVE_CXX_FLAG_WERROR
-- Performing Test HAVE_CXX_FLAG_WERROR - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC
-- Performing Test HAVE_CXX_FLAG_PEDANTIC - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS - Success
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32 - Success
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED_DECLARATIONS
-- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED_DECLARATIONS - Success
-- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED
-- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED - Success
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WD654
-- Performing Test HAVE_CXX_FLAG_WD654 - Failed
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY - Success
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_CXX_FLAG_COVERAGE
-- Performing Test HAVE_CXX_FLAG_COVERAGE - Success
-- Performing Test HAVE_STD_REGEX
CMake Warning at third_party/benchmark/cmake/CXXFeatureCheck.cmake:38 (message):
  If you see build failures due to cross compilation, try setting
  HAVE_STD_REGEX to 0
Call Stack (most recent call first):
  third_party/benchmark/CMakeLists.txt:247 (cxx_feature_check)

-- Performing Test HAVE_STD_REGEX -- success
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX
CMake Warning at third_party/benchmark/cmake/CXXFeatureCheck.cmake:38 (message):
  If you see build failures due to cross compilation, try setting
  HAVE_POSIX_REGEX to 0
Call Stack (most recent call first):
  third_party/benchmark/CMakeLists.txt:249 (cxx_feature_check)

-- Performing Test HAVE_POSIX_REGEX -- success
-- Performing Test HAVE_STEADY_CLOCK
CMake Warning at third_party/benchmark/cmake/CXXFeatureCheck.cmake:38 (message):
  If you see build failures due to cross compilation, try setting
  HAVE_STEADY_CLOCK to 0
Call Stack (most recent call first):
  third_party/benchmark/CMakeLists.txt:257 (cxx_feature_check)

-- Performing Test HAVE_STEADY_CLOCK -- success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test BENCHMARK_HAS_O3_FLAG
-- Performing Test BENCHMARK_HAS_O3_FLAG - Success
-- Performing Test BENCHMARK_HAS_CXX03_FLAG
-- Performing Test BENCHMARK_HAS_CXX03_FLAG - Success
-- Performing Test BENCHMARK_HAS_WNO_ODR
-- Performing Test BENCHMARK_HAS_WNO_ODR - Success
-- Looking for res_servicename in resolv
-- Looking for res_servicename in resolv - found
-- Performing Test IOS_V10
-- Performing Test IOS_V10 - Failed
-- Performing Test MACOS_V1012
-- Performing Test MACOS_V1012 - Failed
-- Looking for gethostbyname in nsl
-- Looking for gethostbyname in nsl - found
-- Looking for gethostbyname in socket
-- Looking for gethostbyname in socket - found
-- Looking for socket in socket
-- Looking for socket in socket - found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for include file sys/types.h
-- Looking for include file sys/types.h - found
-- Looking for include file sys/socket.h
-- Looking for include file sys/socket.h - found
-- Looking for include file arpa/inet.h
-- Looking for include file arpa/inet.h - found
-- Looking for include file arpa/nameser_compat.h
-- Looking for include file arpa/nameser_compat.h - found
-- Looking for include file arpa/nameser.h
-- Looking for include file arpa/nameser.h - found
-- Looking for include file assert.h
-- Looking for include file assert.h - found
-- Looking for include file errno.h
-- Looking for include file errno.h - found
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Looking for include file inttypes.h
-- Looking for include file inttypes.h - found
-- Looking for include file limits.h
-- Looking for include file limits.h - found
-- Looking for include file malloc.h
-- Looking for include file malloc.h - not found
-- Looking for include file memory.h
-- Looking for include file memory.h - found
-- Looking for include file netdb.h
-- Looking for include file netdb.h - found
-- Looking for include file netinet/in.h
-- Looking for include file netinet/in.h - found
-- Looking for include file netinet/tcp.h
-- Looking for include file netinet/tcp.h - found
-- Looking for include file net/if.h
-- Looking for include file net/if.h - found
-- Looking for include file signal.h
-- Looking for include file signal.h - found
-- Looking for include file socket.h
-- Looking for include file socket.h - not found
-- Looking for include file stdbool.h
-- Looking for include file stdbool.h - found
-- Looking for include file stdint.h
-- Looking for include file stdint.h - found
-- Looking for include file stdlib.h
-- Looking for include file stdlib.h - found
-- Looking for include file strings.h
-- Looking for include file strings.h - found
-- Looking for include file string.h
-- Looking for include file string.h - found
-- Looking for include file stropts.h
-- Looking for include file stropts.h - not found
-- Looking for include file sys/ioctl.h
-- Looking for include file sys/ioctl.h - found
-- Looking for include file sys/param.h
-- Looking for include file sys/param.h - found
-- Looking for include file sys/select.h
-- Looking for include file sys/select.h - found
-- Looking for include file sys/stat.h
-- Looking for include file sys/stat.h - found
-- Looking for include file sys/time.h
-- Looking for include file sys/time.h - found
-- Looking for include file sys/uio.h
-- Looking for include file sys/uio.h - found
-- Looking for include file time.h
-- Looking for include file time.h - found
-- Looking for include file dlfcn.h
-- Looking for include file dlfcn.h - found
-- Looking for include file unistd.h
-- Looking for include file unistd.h - found
-- Looking for include files winsock2.h, windows.h
-- Looking for include files winsock2.h, windows.h - not found
-- Looking for 3 include files winsock2.h, ..., windows.h
-- Looking for 3 include files winsock2.h, ..., windows.h - not found
-- Looking for include files winsock.h, windows.h
-- Looking for include files winsock.h, windows.h - not found
-- Looking for include file windows.h
-- Looking for include file windows.h - not found
-- Performing Test HAVE_SOCKLEN_T
-- Performing Test HAVE_SOCKLEN_T - Success
-- Performing Test HAVE_TYPE_SOCKET
-- Performing Test HAVE_TYPE_SOCKET - Failed
-- Performing Test HAVE_BOOL_T
-- Performing Test HAVE_BOOL_T - Success
-- Performing Test HAVE_SSIZE_T
-- Performing Test HAVE_SSIZE_T - Success
-- Performing Test HAVE_LONGLONG
-- Performing Test HAVE_LONGLONG - Success
-- Performing Test HAVE_SIG_ATOMIC_T
-- Performing Test HAVE_SIG_ATOMIC_T - Success
-- Performing Test HAVE_STRUCT_ADDRINFO
-- Performing Test HAVE_STRUCT_ADDRINFO - Success
-- Performing Test HAVE_STRUCT_IN6_ADDR
-- Performing Test HAVE_STRUCT_IN6_ADDR - Success
-- Performing Test HAVE_STRUCT_SOCKADDR_IN6
-- Performing Test HAVE_STRUCT_SOCKADDR_IN6 - Success
-- Performing Test HAVE_STRUCT_SOCKADDR_STORAGE
-- Performing Test HAVE_STRUCT_SOCKADDR_STORAGE - Success
-- Performing Test HAVE_STRUCT_TIMEVAL
-- Performing Test HAVE_STRUCT_TIMEVAL - Success
-- Looking for AF_INET6
-- Looking for AF_INET6 - found
-- Looking for O_NONBLOCK
-- Looking for O_NONBLOCK - found
-- Looking for FIONBIO
-- Looking for FIONBIO - found
-- Looking for SIOCGIFADDR
-- Looking for SIOCGIFADDR - found
-- Looking for MSG_NOSIGNAL
-- Looking for MSG_NOSIGNAL - not found
-- Looking for PF_INET6
-- Looking for PF_INET6 - found
-- Looking for SO_NONBLOCK
-- Looking for SO_NONBLOCK - not found
-- Performing Test HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID
-- Performing Test HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID - Success
-- Performing Test HAVE_LL
-- Performing Test HAVE_LL - Success
-- Looking for bitncmp
-- Looking for bitncmp - not found
-- Looking for closesocket
-- Looking for closesocket - not found
-- Looking for CloseSocket
-- Looking for CloseSocket - not found
-- Looking for connect
-- Looking for connect - found
-- Looking for fcntl
-- Looking for fcntl - found
-- Looking for freeaddrinfo
-- Looking for freeaddrinfo - found
-- Looking for getaddrinfo
-- Looking for getaddrinfo - found
-- Looking for getenv
-- Looking for getenv - found
-- Looking for gethostbyaddr
-- Looking for gethostbyaddr - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for gethostname
-- Looking for gethostname - found
-- Looking for getnameinfo
-- Looking for getnameinfo - found
-- Looking for getservbyport_r
-- Looking for getservbyport_r - not found
-- Looking for gettimeofday
-- Looking for gettimeofday - found
-- Looking for if_indextoname
-- Looking for if_indextoname - found
-- Looking for inet_net_pton
-- Looking for inet_net_pton - found
-- Looking for inet_ntop
-- Looking for inet_ntop - found
-- Looking for inet_pton
-- Looking for inet_pton - found
-- Looking for ioctl
-- Looking for ioctl - found
-- Looking for ioctlsocket
-- Looking for ioctlsocket - not found
-- Looking for IoctlSocket
-- Looking for IoctlSocket - not found
-- Looking for recv
-- Looking for recv - found
-- Looking for recvfrom
-- Looking for recvfrom - found
-- Looking for send
-- Looking for send - found
-- Looking for setsockopt
-- Looking for setsockopt - found
-- Looking for socket
-- Looking for socket - found
-- Looking for strcasecmp
-- Looking for strcasecmp - found
-- Looking for strcmpi
-- Looking for strcmpi - not found
-- Looking for strdup
-- Looking for strdup - found
-- Looking for stricmp
-- Looking for stricmp - not found
-- Looking for strncasecmp
-- Looking for strncasecmp - found
-- Looking for strncmpi
-- Looking for strncmpi - not found
-- Looking for strnicmp
-- Looking for strnicmp - not found
-- Looking for writev
-- Looking for writev - found
-- Looking for __system_property_get
-- Looking for __system_property_get - found
CMake Error at third_party/cares/cares/CMakeLists.txt:678 (INSTALL):
  INSTALL TARGETS given no BUNDLE DESTINATION for MACOSX_BUNDLE executable
  target "ahost".

CMake Error at third_party/cares/cares/CMakeLists.txt:687 (INSTALL):
  INSTALL TARGETS given no BUNDLE DESTINATION for MACOSX_BUNDLE executable
  target "adig".

CMake Error at third_party/cares/cares/CMakeLists.txt:696 (INSTALL):
  INSTALL TARGETS given no BUNDLE DESTINATION for MACOSX_BUNDLE executable
  target "acountry".

CMake Warning at cmake/cares.cmake:33 (message):
  gRPC_INSTALL will be forced to FALSE because gRPC_CARES_PROVIDER is
  "module"
Call Stack (most recent call first):
  CMakeLists.txt:138 (include)

-- Looking for C++ include fnmatch.h
-- Looking for C++ include fnmatch.h - found
-- Looking for C++ include stddef.h
-- Looking for C++ include stddef.h - found
-- Check size of uint32_t
-- Check size of uint32_t - done
-- Looking for strtoll
-- Looking for strtoll - found
--
-- 3.8.0.0
CMake Warning (dev) at third_party/protobuf/cmake/install.cmake:60 (message):
  The file
  "/Users/vladimir/Documents/projects/grpc/third_party/protobuf/src/google/protobuf/stubs/io_win32.h"
  is listed in
  "/Users/vladimir/Documents/projects/grpc/third_party/protobuf/cmake/cmake/extract_includes.bat.in"
  but there not exists.  The file will not be installed.
Call Stack (most recent call first):
  third_party/protobuf/cmake/CMakeLists.txt:231 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found OpenSSL: /Users/vladimir/Documents/projects/OpenSSL-for-iPhone/lib/libcrypto.a (found version "1.0.2s")
-- Check size of off64_t
-- Check size of off64_t - failed
-- Looking for fseeko
-- Looking for fseeko - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Configuring incomplete, errors occurred!
See also "/Users/vladimir/Documents/projects/grpc-ios-build/CMakeFiles/CMakeOutput.log".
See also "/Users/vladimir/Documents/projects/grpc-ios-build/CMakeFiles/CMakeError.log".

CMakeOutput.log
CMakeError.log

@jackopoz  You need set up ' set(CMAKE_MACOSX_BUNDLE 0)'  to your CMakeLists.txt file.
Look at this about MACOSX_BUNDLE

@jackopoz You need set up those for your build:
-Dprotobuf_BUILD_PROTOC_BINARIES=OFF
-DgRPC_BUILD_CODEGEN=OFF
-DCARES_INSTALL=OFF

Thank you!
After make VERBOSE=1 to correct some of clang commands finally got build

@jackopoz Would you be able to post your final cmake config for this? I am also trying to cross compile grpc for ios from source, and after implementing the fixes suggested in this thread, I'm still running into other issues, including but not limited to:
ld: library not found for -lnsl
Thanks!

@jackopoz You need set up those for your build:
-Dprotobuf_BUILD_PROTOC_BINARIES=OFF
-DgRPC_BUILD_CODEGEN=OFF
-DCARES_INSTALL=OFF

Thank you!
After make VERBOSE=1 to correct some of clang commands finally got build

Hello @jackopoz . Please tell me whether you stuck with such error:
Scanning dependencies of target gen_hpack_tables
[ 53%] Building CXX object CMakeFiles/gen_hpack_tables.dir/tools/codegen/core/gen_hpack_tables.cc.o
[ 53%] Linking CXX executable gen_hpack_tables.app/gen_hpack_tables
ld: library not found for -lnsl
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [gen_hpack_tables.app/gen_hpack_tables] Error 1
make[1]: *** [CMakeFiles/gen_hpack_tables.dir/all] Error 2
make: *** [all] Error 2

yes, I have the similar problems on some files.
after make with verbose, I have compiled this places manually without -lnsl and some other libs

@jackopoz You need set up those for your build:
-Dprotobuf_BUILD_PROTOC_BINARIES=OFF
-DgRPC_BUILD_CODEGEN=OFF
-DCARES_INSTALL=OFF

Thank you!
After make VERBOSE=1 to correct some of clang commands finally got build

Hello @jackopoz . Please tell me whether you stuck with such error:
Scanning dependencies of target gen_hpack_tables
[ 53%] Building CXX object CMakeFiles/gen_hpack_tables.dir/tools/codegen/core/gen_hpack_tables.cc.o
[ 53%] Linking CXX executable gen_hpack_tables.app/gen_hpack_tables
ld: library not found for -lnsl
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [gen_hpack_tables.app/gen_hpack_tables] Error 1
make[1]: *** [CMakeFiles/gen_hpack_tables.dir/all] Error 2
make: *** [all] Error 2

@Rodionp13 did you manage to solve the ld: library not found for -lnsl error when building for IOS?

I have the same error ld: library not found for -lnsl. Has anyone been able to solve that?

@oliverepper
This is the cmake command I am using to compile for IOS, you can find the -DHAVE_LIBNSL=FALSE parameter
Hope this helps
 ${CMAKE} \
        -DCMAKE_INSTALL_PREFIX=${PREFIX_DIR} \
        -DPLATFORM=${PLATFORM} \
        -DCMAKE_TOOLCHAIN_FILE=${SOURCE_DIR}/ios-cmake/ios.toolchain.cmake \
        -DCMAKE_POLICY_DEFAULT_CMP0063=NEW \
        -DCMAKE_CXX_VISIBILITY_PRESET=hidden \
        -DCMAKE_VISIBILITY_INLINES_HIDDEN=ON \
        -DCMAKE_MAKE_PROGRAM=/usr/bin/make \
        -DCMAKE_OSX_DEPLOYMENT_TARGET=10.14 \
        -DCARES_INSTALL=OFF \
        -DCARES_STATIC=ON \
        -DCARES_STATIC_PIC=ON \
        -DCARES_BUILD_TESTS=OFF \
        -DCARES_BUILD_TOOLS=OFF \
        -DgRPC_BUILD_CSHARP_EXT=OFF \
        -DgRPC_BUILD_GRPC_CPP_PLUGIN=OFF \
        -DgRPC_BUILD_GRPC_CSHARP_PLUGIN=OFF \
        -DgRPC_BUILD_GRPC_NODE_PLUGIN=OFF \
        -DgRPC_BUILD_GRPC_OBJECTIVE_C_PLUGIN=OFF \
        -DgRPC_BUILD_GRPC_PHP_PLUGIN=OFF \
        -DgRPC_BUILD_GRPC_PYTHON_PLUGIN=OFF \
        -DgRPC_BUILD_GRPC_RUBY_PLUGIN=OFF \
        -DCMAKE_BUILD_TYPE=Release \
        -DgRPC_BUILD_CODEGEN=OFF \
        -DgRPC_BUILD_TOOLS=OFF \
        -DgRPC_BACKWARDS_COMPATIBILITY_MODE=ON \
        -DgRPC_BUILD_TESTS=OFF \
        -DgRPC_ABSL_PROVIDER=module \
        -DgRPC_CARES_PROVIDER=module \
        -DgRPC_PROTOBUF_PROVIDER=module \
        -DgRPC_RE2_PROVIDER=module \
        -DgRPC_SSL_PROVIDER=package \
        -DOPENSSL_CRYPTO_LIBRARY="${UE_THIRDPARTY_PATH}/OpenSSL/1.1.1/Lib/IOS/libcrypto.a" \
        -DLIB_EAY_LIBRARY_RELEASE="${UE_THIRDPARTY_PATH}/OpenSSL/1.1.1/Lib/IOS/libcrypto.a" \
        -DOPENSSL_INCLUDE_DIR="${UE_THIRDPARTY_PATH}/OpenSSL/1.1.1/Include/IOS" \
        -DSSL_EAY_LIBRARY_RELEASE="${UE_THIRDPARTY_PATH}/OpenSSL/1.1.1/Lib/IOS/libssl.a" \
        -DgRPC_ZLIB_PROVIDER=package \
        -DZLIB_INCLUDE_DIR="${UE_THIRDPARTY_PATH}/zlib/v1.2.8/include/Mac" \
        -DZLIB_LIBRARY_RELEASE="${UE_THIRDPARTY_PATH}/zlib/v1.2.8/lib/Mac/libz.a" \
        -Dprotobuf_BUILD_TESTS=OFF \
        -Dprotobuf_BUILD_PROTOC_BINARIES=OFF \
        -Dprotobuf_BUILD_SHARED_LIBS=OFF \
        -DENABLE_BITCODE=ON \
        -DHAVE_LIBNSL=FALSE \
        -DHAVE_SOCKET_LIBSOCKET=FALSE \
        -DHAVE_GHBN_LIBSOCKET=FALSE \
        -DHAVE_LIBSOCKET=FALSE \
        -DHAVE_LIBRT=FALSE \
        -DPLATFORM=${PLATFORM} \
        ../..
    make -j16
    make install

@posilva Perfect! Thanks a lot. Out of curiosity why do you use the C++ gRPC instead of grpc-swift on iOS?

We are writing  cross platform code in C++

Same reason here. If it is not essential to call into the gRPC request handlers from C++ it still might be worth considering using the grpc-swift. Swift NIO is excellent and has great platform support through NIO Transport Services. Anyways thanks a ton for your help!

For those who prefer to set it in CMakeLists.txt, be careful with lowercase :-D
set(Protobuf_BUILD_PROTOC_BINARIES OFF)
set(gRPC_BUILD_CODEGEN OFF)
set(CARES_INSTALL OFF)

@posilva But it seem doesn't work out with ssl using the parameters you gave. can you use ssl ?

It doesn't seem to work for me either:
[ 20%] Building CXX object CMakeFiles/grpc.dir/src/core/ext/filters/client_channel/lb_policy/grpclb/grpclb_channel_secure.cc.o
...
/Users/foo/GrpcAndSwiftProofOfConcept/grpc/src/core/tsi/ssl_transport_security.h:31:10: fatal error: 'openssl/x509.h' file not found
#include <openssl/x509.h>

authors: CarlosNano Jack-256 Rodionp13 jackopoz mramonlopez njbrake oliverepper posilva ymmuse


text:
gpr_time_from_XXX functions take long as a parameter.

Despite being fine for most practical purposes, this is only "kind-of" alright because long is only 32-bit on windows. Ideally, these functions would take an gpr_int64.
gpr_timespec gpr_time_from_micros(long x, gpr_clock_type clock_type);
gpr_timespec gpr_time_from_nanos(long x, gpr_clock_type clock_type);
gpr_timespec gpr_time_from_millis(long x, gpr_clock_type clock_type);
gpr_timespec gpr_time_from_seconds(long x, gpr_clock_type clock_type);
gpr_timespec gpr_time_from_minutes(long x, gpr_clock_type clock_type);
gpr_timespec gpr_time_from_hours(long x, gpr_clock_type clock_type);

This has been fixed already, a little while ago.

authors: jtattermusch nicolasnoble


text:
[PHP] Fatal error: Class 'Grpc\ChannelCredentials' not found

After installing using composer (via composer require grpc/grpc), I get the following error when trying to create channel credentials:
Fatal error: Class 'Grpc\ChannelCredentials' not found in vendor/grpc/grpc/src/php/lib/Grpc/BaseStub.php on line 61

The offending line:
$channel_credentials = \Grpc\ChannelCredentials::createInsecure();

My PHP version:
PHP 5.6.24 (cli) (built: Jul 22 2016 02:41:22)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies

Is there any guidance for this? I also get this line after installing the PECL extension.
cc/ @stanley-cheung for his support on this.

You will need to add extension=grpc.so into your php.ini file. Or add -d extension=grpc.so to your command line.

Oh nice, that worked. Thanks very much.
Any thoughts on whether that step could be included as part of the pecl installation? Or adding some extra guidance when doing composer require grpc/grpc? It's kinda confusing to do the composer install and still be left needing to do the pecl install grpc step

@mcos grpc have 2 part of library. One part it's a php extension and another path it is php library. Its work together. Composer can't install extensions in php and Pecl can't install libraries in your project. That's why you need to use pecl and composer.

@stanley-cheung Would it be possible for you to enable issues on https://github.com/stanley-cheung/Protobuf-PHP/?

Oh I wasn't aware issues weren't enabled. Just did. But please understand that the official Proto3 support from google/protobuf for PHP will be ready very soon so my Protobuf-PHP fork will be going away soon.

Oh Brilliant, thanks! I actually just wanted to mention a workaround I used to get proto3 timestamps working and whether it would be a good idea to PR it in to the repo?

@stanley-cheung How soon?, do you have any source?

@TeBoring should be a better person to provide that estimate in google/protobuf#1936

@mcos, what's the timestamp issue?

Closing this issue now as it's no longer about the Fatal Error. Please raise the timestamp issue over at stanley-cheung/Protobuf-PHP. Thanks.

Thanks @stanley-cheung, I'll add the issue over there.

@stanley-cheung I have same issue, my GRPC worked 2 days ago, after that I received update on my Ubuntu, after that always same error on same page that worked (ps on my server things are still working)
since quotes are not most frinedly here here is stakoverflow with more details


text:
Do not take ownership for grpc server global callbacks.

The function comment of grpc::Server::SetGlobalCallbacks() states that "Can only be called once per application. Does not take ownership of callbacks". However, the implementation uses shared_ptr which takes ownership. Make it the same as ClientContext's GlobalCallbacks.

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @wjywbs isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

Done.

Friendly ping for @mehrdada for 24b6d392125561b73e472dfe954613b6249faf97 and @vjpai for 64616496e2500bc99eeb52035e85a38ae8bb7244.

Rebased.

Pinging @hcaseyal and @vjpai for review. Thanks.

@vjpai Please check again since this has been open for 5 months and I've resolved merge conflicts for 3 times.

@vjpai Do you think this change can proceed? Thanks.

Weekly ping on this. Thanks.

Pinging on this again. @hcaseyal @vjpai

Waiting for vjpai to approve this

A year has passed. @vjpai Please check again.

authors: hcaseyal thelinuxfoundation wjywbs


text:
Lazily load protobuf from the grpc ruby errors module

This mitigates #18905 by fixing 2) in https://github.com/grpc/grpc/issues/18905#issuecomment-489766758.
This is overall a conservative approach to #18905 that keeps the status quo of not having a runtime dependency of the "core" grpc modules on google-protobuf.

/cc

interop cloud to cloud: https://github.com/grpc/grpc/issues/18967
interop cloud to prod: https://github.com/grpc/grpc/issues/18967
basic tests macos and objc macos: https://github.com/grpc/grpc/issues/18968


text:
csharp: remove List/Entry[] allocs from Metadata

Memory analysis shows that a lot of allocations come from Metadata - having Metadata is fine, but that then allocates a List<Entry> each time, which also allocates an Entry[] as soon as the first item is added:

The fact that we have 40k Metadata and 40k List<Metadata.Entry>, but only 10k Metadata.Entry[] tells us that most of those Metadata don't actually have any entries in them. Further analysis shows that most of the time, with default options, there's only a single Metadata.Entry in them - namely "user-agent". So; I propose two things:

don't allocate a List<T> unless we need it
we can special-case the single-item scenario by using an object field
detect the 3 scenarios (null, Metadata.Entry, List<Metadata.Entry>) in the relevant methods and act accordingly

Result:

here you can see 40k of Metadata, 10k of Metadata.Entry, but zero of either List<Metadata.Entry> or Metadata.Entry[]. Success!
Because this touched quite a few lines, I beefed of the metadata tests, too.

An interesting optimization, but I'm wondering if it makes things a bit too complex. Would it make sense to just make the List lazy and set it to null by default, which would avoid many allocations in cases where Metadata is empty (that happens often) and then try to figure out the case where we only have one metadata entry (the user-agent) separately (perhaps the solution would be different here - e.g. caching the whole metadata entry or so)?

Possibly, but I was also noting here that in grpc-dotnet on Kestrel there's also usually a single response headers too ("server", IIRC - perhaps I should find out and add as a well-known-key).
The problem with user agent is that it isn't an easy one to cache unless you have a logical session concept - you could presume that different clients will have different UAs, and doing something simple like a dictionary is a DDOS vector :(

authors: jtattermusch mgravell


text:
Fix some clang-tidy issue (fix-forward)

Fix forward of #28679
Previously it happened to break the test but I suspect it was caused by wrong merge so I'm trying to lang it as it was again.

Basic Test C/C++ MacOS test failed with the following error (log);
2022-01-26 14:48:31,304 my port server is version 21
Traceback (most recent call last):
  File "workspace_c++_macos_opt_native/tools/run_tests/run_tests.py", line 1884, in <module>
    build_only=args.build_only)
  File "workspace_c++_macos_opt_native/tools/run_tests/run_tests.py", line 1765, in _build_and_run
    one_run = set(spec for language in languages
  File "workspace_c++_macos_opt_native/tools/run_tests/run_tests.py", line 1766, in <genexpr>
    for spec in language.test_specs()
  File "workspace_c++_macos_opt_native/tools/run_tests/run_tests.py", line 361, in test_specs
    [binary, '--gtest_list_tests'], stderr=fnull)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 223, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '[u'cmake/build/interop_test', '--gtest_list_tests']' returned non-zero

Removed the change adding gtest to the dependency of the target by the warning from clang13. I guess having gtest in the dependency of non-test target disrupts our script running gtest-based tests only.


text:
The (new) face interface of RPC Framework.

This is the public API of the old face package of RPC Framework
extracted into a first-class interface and adapted to metadata, status,
and flow control.

The health checking spec requires having a way to abort RPCs with a particular low-level status. I don't see any way of doing that in the current interface. Am I looking in the wrong place?

authors: nathanielmanistaatgoogle soltanmm


text:
[deps] Update absl-py from 0.15.0 to 2.1.0

Changelog: https://github.com/abseil/abseil-py/blob/main/CHANGELOG.md
New changes should not be breaking for what we're using.
New features to look forward to:

absl.flags.set_default
absl.flags.override_value
absltest.TestCase.assertDataclassEqual

[ ] grpc/java/master/branch/psm-security
[ ] grpc/java/master/branch/xds_k8s_lb
[ ] grpc/java/master/branch/xds_url_map
[ ] grpc/core/master/linux/psm-csm

repo: grpc/psm-interop


text:
Extend syntax

also prepared release of version 0.4.0

Codecov Report

Merging #120 (08a902a) into master (fc669ca) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #120   +/-   ##
=======================================
  Coverage   99.74%   99.75%
=======================================
  Files           5        5
  Lines        1198     1211   +13
=======================================
+ Hits         1195     1208   +13
  Misses          3        3

Flag
Coverage Δ

unittests
99.75% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

pycep/transformer.py
100.00% <100.00%> (ø)

pycep/typing.py
100.00% <100.00%> (ø)

authors: codecov-commenter gruebel

repo: gruebel/pycep


text:
How do you make the parameter to read the directory listing?

Can you please let me know how do you make the parameter to read the directory listing.
Also, put the configuration of the process parameter demo.

Hi @alwaysharsha,
For the process demo, please have a look at the script webserver/processes_web_server.py.
To read the directory listing you can modify that script, but instead _list_processes method add new one named something like _list_folder, which could look something like:
    def _list_folder(self):
        self.send_response(200)
        self.send_header("Content-type", "application/json")
        self.end_headers()

        options = []
        for item in os.listdir(<YOUR_PATH_HERE>):
            try:
                options.append(dict(key=item, value=item))
            except psutil.NoSuchProcess:
                pass

        self.wfile.write(json.dumps(dict(options=sorted(options, key=lambda p: p['value'], reverse=True))))

authors: alwaysharsha grundic

repo: grundic/teamcity-web-parameters


text:
--terragrunt-exclude-dir not working?

I have the following structure
root
|- commons (should not read this directly)
     | - *.tf
     | - *.hcl
|-dev
     | - parent.hcl
     | - commons
|-test
     | - parent.hcl
     | - commons

I'd like to run a plan-all on the root folder but when I try to exclude commons dir it reads it anyway
terragrunt plan-all --terragrunt-exclude-dir ./commons
I'm getting
 Error processing module at '.../root/commons/dynamodb/items/configs/terragrunt.hcl'. How this module was found: Terragrunt config file found in a subdirectory of .../root/. Underlying error: .../root/commons/dynamodb/items/configs/terragrunt.hcl:9,10-33: Error in function call; Call to function "find_in_parent_folders" failed: ParentFileNotFound: Could not find a terragrunt.hcl in any of the parent folders of .../root/commons/dynamodb/items/configs/terragrunt.hcl. Cause: Traversed all the way to the root.., and 1 other diagnostic(s)

Can you share the full log output up to the interactive prompt asking if you would like to run this on a list of modules?

@yorinasub17 Sorry for the late response but that's all the logs I have. I'm not getting any kind of confirmation to run this

Ah ok so it is failing in the partial parsing of the configuration. Because the include and exclude functionality still processes the dependencies, terragrunt needs to read just enough of the configuration in ALL config that it finds in the current working directory to build the tree, before proceeding to process include and excludes. So you need to have a complete, valid config for those components even for those directories that are excluded.
As far as what components need to be valid, see https://terragrunt.gruntwork.io/docs/getting-started/configuration/#configuration-parsing-order, specifically the section about -all.

I'm also facing the same issue.
Perhaps there should be a new option to ask Terragrunt to simply ignore some directories when finding modules to run?

Perhaps there should be a new option to ask Terragrunt to simply ignore some directories when finding modules to run?

I am weary of adding additional config options here. I think real solution here would be to fix the processing so that terragrunt processes includes and excludes prior to reading the config. We're a bit buried to implement this, but a PR to fix that implementation would be much appreciated!

Ah FYI, https://github.com/gruntwork-io/terragrunt/pull/1644 would provide a workaround for this.

Any updates on this issue

repo: gruntwork-io/terragrunt


text:
Terragrunt configuration has misaligned inputs

Terraform Version: 0.14.8
Terragrunt Version: v0.28.15
I get an error when trying to validate inputs
terragrunt validate-inputs
ERRO[0000] Terragrunt configuration has misaligned inputs
ERRO[0000] Unable to determine underlying exit code, so Terragrunt will exit with error code 1

variables.tf
variable "machine_type" {
}

variable "image_family" {
}

variable "image_project" {
}

variable "instance_name" {
}

variable "admin_username" {
}

variable "admin_password" {
}

variable "instance_count" {
  default = 1
}

variable "region" {

}

terragrunt.hcl
inputs = {
  instance_count = 2
  image_family   = "windows-2019"
  image_project  = "windows-cloud"
  machine_type   = "e2-standard-2"
  instance_name  = "gcloud-instance"
  admin_username = "myadmin"
  admin_password = "somepassword"
  region         = "us-east1"
}

Could you share the full log output? Also, please turn up the logging level.

Is interesting that this command fails while the other commands like
terragrunt validate and terragrunt plan work normally.
DEBU[0000] Found locals block: evaluating the expressions.
DEBU[0000] Evaluated 1 locals (remaining 0): region
DEBU[0000] Running command: terraform --version          prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
DEBU[0000] Terraform version: 0.14.8
DEBU[0000] Reading Terragrunt config file at /Users/user1/repos/tf-gcloud/dev/us-east1/terragrunt.hcl
DEBU[0000] Found locals block: evaluating the expressions.
DEBU[0000] Evaluated 1 locals (remaining 0): region
DEBU[0000] Downloading Terraform configurations from file:///Users/user1/repos/tf-gcloud/modules into /Users/user1/repos/tf-gcloud/dev/us-east1/.terragrunt-cache/UwDU4KmcvYMwQpkXTB8TGycN1pI/cQSWxX-efoUW-6aaeb--TtWy8Hw
DEBU[0000] Copying files from /Users/user1/repos/tf-gcloud/dev/us-east1 into /Users/user1/repos/tf-gcloud/dev/us-east1/.terragrunt-cache/UwDU4KmcvYMwQpkXTB8TGycN1pI/cQSWxX-efoUW-6aaeb--TtWy8Hw/compute
DEBU[0000] Setting working directory to /Users/user1/repos/tf-gcloud/dev/us-east1/.terragrunt-cache/UwDU4KmcvYMwQpkXTB8TGycN1pI/cQSWxX-efoUW-6aaeb--TtWy8Hw/compute
DEBU[0000] The file path /Users/user1/repos/tf-gcloud/dev/us-east1/.terragrunt-cache/UwDU4KmcvYMwQpkXTB8TGycN1pI/cQSWxX-efoUW-6aaeb--TtWy8Hw/compute/provider.tf already exists, but was a previously generated file by terragrunt. Since if_exists for code generation is set to "overwrite_terragrunt", regenerating file.  prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
DEBU[0000] Generated file /Users/user1/repos/tf-gcloud/dev/us-east1/.terragrunt-cache/UwDU4KmcvYMwQpkXTB8TGycN1pI/cQSWxX-efoUW-6aaeb--TtWy8Hw/compute/provider.tf.  prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
WARN[0000] The following inputs passed in by terragrunt are unused:  prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
WARN[0000] 	- bucket_name                                prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
WARN[0000]                                               prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
INFO[0000] All required inputs are passed in by terragrunt.  prefix=[/Users/user1/repos/tf-gcloud/dev/us-east1]
ERRO[0000] Terragrunt configuration has misaligned inputs
ERRO[0000] Unable to determine underlying exit code, so Terragrunt will exit with error code 1

This is by design. See the command docs for information on what it is trying to achieve: https://terragrunt.gruntwork.io/docs/reference/cli-options/#validate-inputs
That said, I can see us having a --terragrunt-strict mode and default to relaxed, where:

relaxed: only error if missing required inputs
strict: error on unused vars as well


text:
Github action to run terragrunt

Implement Github Action which will allow execution of Terragrunt commands within actions:

automatically install required terragrunt and terraform versions
run terragrunt
collect outputs
load configurations from environment variables like log level, cli args, custom variables

Prototype implementation in:
https://github.com/denis256/tg-gh-action
https://github.com/denis256/tg-gh-action-examples

We now have an official action in: https://github.com/gruntwork-io/terragrunt-action
@denis256 Can we close this ticket? Have we updated our docs to point to the official action?


text:
Feat/telas cadastro

Adicionando telas do fluxo de cadastro

[x] Identificação
[x] Objetivos
[x] Sentimentos
[x] Hábitos
[x] Dados de autenticação

@ThaisMap só tem 3 pontos de melhorias que observei:

[ ] A mensagem de erro do campo de senha precisa só validar pra não estar em branco e que a "A senha deve ter 6 caracteres ou mais"

[ ] Ainda nessa tela vi que só marca a opção do livro quando clica bem em cima do check, mas se for possível, o ideal é quando clicar na linha toda da frase

[ ] Na tela de hábitos o botão fica em cima dos últimos hábitos (na tela de sentimento não fica em cima mas fica grudado)

As mensagens de erro corretas do e-mail e senha vão vir do auth do firebase quando chegarmos nessa parte :)

authors: ThaisMap kellynvd

repo: grupotesseract/jornadasolar-native


text:
🛑 h4.bretterhofer.at is down

In 95db6b3, h4.bretterhofer.at (https://h4.bretterhofer.at/toggle.php) was down:

HTTP code: 0
Response time: 0 ms

Resolved: h4.bretterhofer.at is back up in 22237f7.


text:
🛑 h4.bretterhofer.at is down

In da068c0, h4.bretterhofer.at (https://h4.bretterhofer.at/toggle.php) was down:

HTTP code: 0
Response time: 0 ms

Resolved: h4.bretterhofer.at is back up in 3cf4b86.


text:
🛑 kinderundjugendtanz.at is down

In 7e90a74, kinderundjugendtanz.at (https://kinderundjugendtanz.at) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kinderundjugendtanz.at is back up in 8053e21.


text:
can not find the cpp_mstar

when I cd into the od_mstar3 folder, and use the terminal to run 'python3 setup.py build_ext --inplace', I can't find any new file, even the cpp_mstar file.
And the setup.py in od_mstar3 can not run until using terminal.
I want to know how to obtain the cpp_mstar file, there is no build file in od_mstar3

when I cd into the od_mstar3 folder, and use the terminal to run 'python3 setup.py build_ext --inplace', I can't find any new file, even the cpp_mstar file.
And the setup.py in od_mstar3 can not run until using terminal.
I want to know how to obtain the cpp_mstar file, there is no build file in od_mstar3

repo: gsartoretti/PRIMAL