Removing run-tests.py file.

Description
Trying to remove run-tests.py file.

Yet to add conftest.py file

I think I messed up the branch. I'm having problems while pushing changes. I've made the changes.

@prady0t Is your branch still having problems? Do you need help fixing the branch?

@prady0t Is your branch still having problems? Do you need help fixing the branch?

I can work with this, although I made a lot of commits.

No worries, we'll squash merge anyway, but to learn how to rewrite history would be up to you as an exercise

@prady0t, could you fix the failure in the style jobs so that the tests can run?

@prady0t, could you fix the failure in the style jobs so that the tests can run?

Done. I removed lot of code lines from conftest.py file and now we are using -m for everything. If a user runs pytest without any marker value, it runs all the tests, otherwise only those specified by -m flag.

Added documentation fixes.

This will need approval from @arjxn-py since he previously requested changes, we can merge after that

No unnecessary logs this time around: https://github.com/pybamm-team/PyBaMM/actions/runs/10115401416/job/27976388229

No unnecessary logs this time around: https://github.com/pybamm-team/PyBaMM/actions/runs/10115401416/job/27976388229

Noticed that, just that we'd need to update branch to merge. My bad, I should have done it earlier.


Bring automatic and in-app updates.

Manually updating every time is a hassle.

v0.18.1 seems added this feature.


Remove typo from the Reviewing pull requests section in Documentation

Problem:
On line 97 of the Reviewing pull requests section, the word 'add' appears twice.
Proposed Solution:
One 'add' should be removed.
Additional Information:
/good-first-issue
/kind documentation
/assign

“Here, you can add add a summary of your review” - that does look wrong to me.
/language en
/triage accepted
New contributors, PRs are welcome!

Hi @harshitasao are you working on this issues? if not can you assign it to @kadtendulkar. She is new contributer.

I have opened a PR for this issue. Please check: https://github.com/kubernetes/website/pull/33737

Related PR merged. We need to manually close this. Thanks!!


AIY recorder uses only one channel

Hi,
I am using aiy voice kit V1 which uses Voice HAT microphone board. On the microphone board, there is 2-mic array. However, on _recoder.py library, currently it executes arecord with -c1 which means recording happens on a single channel.
Could you please kindly explain to me or I misunderstand the code?
One more thing, on alsa website, they say the route value is usually from (0.0 to 1.0)
what does the "30" number within the asoundrc configuration file means?
pcm.micboost {
    type route
    slave.pcm dsnoop
    ttable {
        0.0 30.0
        1.1 30.0
}

Recorder class has a constructor parameter channels (which is 1 by default), so its behavior can be adjusted.
We recently switched to PulseAudio and don't need ALSA config anymore, please take the latest image from releases page.


docs: add missing parameter to controlled Switch example

No issue, sorry, just found that described prop is missing from the example
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[x] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Check that docs have been updated
🧢 Your Project:

Same as https://github.com/adobe/react-spectrum/pull/6823 I did the PR from my main account now, where I signed the CLA


Support for Rider 2024.3 in Reqnroll.Rider

Hi Reqnroll.Rider team,
We're using Rider 2024.3 but are unable to use the plugin due to compatibility issues. Can you please add support for this latest version?
Thanks!

I noticed a commit for the upgrade https://github.com/reqnroll/Reqnroll.Rider/commit/4c821406aa64afcda90af2e0cffc970ffcb76eee
Any release date in mind :D?


Models are broken in the new torch version

PyTorch introduced approximate GELU. This breaks the MLP-Mixer models. The fix is to save pre-trained models as weight dicts and not complete pickle objects.

For now, a quick fix would be something along the lines of:
for i in net.mixer:
    if isinstance(i, torch.nn.Sequential):
        for k in i:
            k.fn[1].approximate = "none"

Guess it can be closed now

Thanks a lot @neverix for pointing out the issue and providing the solution!

Merged now in master @neverix

I ran into this same issue just now despite using the latest master. The original solution from Nev does work though.

@PaulScotti  I see, could you please show the exact exception you get and with which model ?

PyTorch 1.12.0+cu113
Using cc12m_32x1024_mlp_mixer_clip_ViTB32_pixelrecons_256x256_v0.4.th (v0.3 also produces the same error)
AttributeError: 'GELU' object has no attribute 'approximate'
I checked main.py to make sure I am indeed using the latest script that has the "_fix_mlp_mixer_gelu_issue" edits.
Error does not occur if I use PyTorch 1.8

@PaulScotti Thanks for the details,  I couldn't reproduce it so far not sure what I am missing, could you also please provide the line where it happens so that I could investigate more closely?

Sure, attached are screenshots of the full error message:
https://i.imgur.com/FbLimQa.png
https://i.imgur.com/WnDY9CO.png
https://i.imgur.com/FBcmzNR.png

Thanks @PaulScotti for the screenshots! I see now, the reason is that the _fix_mlp_mixer_gelu_issue function is not called. If you would like to load the models manually, like in the screenshots above, you could use the function load_model from main.py, e.g., from main import load_model; net = load_model(<PATH>);net(emb);, should work.

Great, closing the issue now since it is solved


qtextedit for input stream

Create a widget that will accept input and then push a message to the conversation.
This will require a GUI which means this will require a Session
Once entered it will clear the current input, and then begin to read in the output of the model. When the model completes, it will create  a new message, add it to the conversation, then refresh the conversation html view.
SESSION IS NEEDED FIRST

Ended up getting this to work fine just updating the msg.as_styled_html as each token comes in...Kinda shocked that it's working as well as it is and might need to add a small throttle just to make sure that things don't spit out in giant chunks, which I find harder to read in real time


Error::get_ref can return unstable Errors

You can get the underlying cause of an Error with err.get_ref(). This means you'll have dynamic access to hyper::Error and serde_urlencoded::ser::Error, which are both pre-1.0. Is this a compatibility hazard?
cc @dtolnay

Some ways to handle this:

Do not return any error from an unstable library in get_ref. You can still see a text description from reqwest::Error, and know vaguely that it was an HTTP parse error by checking error.is_http()
"Hide" the actual error type by returning a private opaque wrapper. It still implements std::error::Error, but does not allow someone to downcast to a hyper::Error while hyper is unstable.

Opened https://github.com/brson/rust-api-guidelines/issues/96


'Trying to reconnect..' in UI even though its connected

Fixes #352

@davkal is this good to go?  Can I get an LGTM?

@tomwilkie please review my fix.

Whoops, LGTM


Add docker container for druid

This container is an 'omnibus' (since there is such a high overlap with the various services). It includes all contrib extension as well as the msql connector.
It is intended to be run as docker run NAME SERVICE (e.g. docker run druid:latest broker)
Signed-off-by: Don Bowman<EMAIL_ADDRESS>

there have been no comments on the mailing list.

I'm not sure what else is needed of me here.
No comments received.
I've made the requested changes.

for posterity there is a discussion on the incubator list about docker releases (only tangentially related)
http://mail-archives.apache.org/mod_mbox/incubator-general/201902.mbox/<CAGaRif1NXV4ZmakmR3bhGS-UvkOf%3DmJJg3HOKCTEKtaYBW3NDQ%40mail.gmail.com>
and the discussion on the druid list seems to have no specific objections and pretty good counter examples:
<EMAIL_ADDRESS>

team city issues look unrelated

Once this PR is merged I will add the docker-compose example.
FWIW I am using the above in Kubernetes.

Are we planning to automatically build those images and push to dockerhub ?

@maver1ck see discussion on<EMAIL_ADDRESS>My vote is obviously yes.

I am having issues building the docker image using the command in the docker readme: docker build -t druid:0.14.0 -f distribution/docker/Dockerfile .
Here is the build failure output:

[INFO] druid-time-min-max ................................. SUCCESS [  2.133 s]
[INFO] druid-google-extensions ............................ SUCCESS [  6.508 s]
[INFO] druid-virtual-columns .............................. SUCCESS [  2.119 s]
[INFO] druid-thrift-extensions ............................ SUCCESS [  9.566 s]
[INFO] ambari-metrics-emitter ............................. FAILURE [  2.370 s]
[INFO] sqlserver-metadata-storage ......................... SKIPPED
[INFO] kafka-emitter ...................................... SKIPPED
[INFO] druid-redis-cache .................................. SKIPPED
[INFO] druid-opentsdb-emitter ............................. SKIPPED
[INFO] materialized-view-maintenance ...................... SKIPPED
[INFO] materialized-view-selection ........................ SKIPPED
[INFO] druid-momentsketch ................................. SKIPPED
[INFO] distribution ....................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  10:02 min
[INFO] Finished at: 2019-03-25T23:08:02Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ambari-metrics-emitter: Could not resolve dependencies for project org.apache.druid.extensions.contrib:ambari-metrics-emitter:jar:0.15.0-incubating-SNAPSHOT: Could not transfer artifact org.apache.ambari:ambari-metrics-common:jar:<IP_ADDRESS>.22 from/to hortonworks (http://repo.hortonworks.com/content/repositories/releases): Failed to transfer file http://repo.hortonworks.com/content/repositories/releases/org/apache/ambari/ambari-metrics-common/<IP_ADDRESS>.22/ambari-metrics-common-<IP_ADDRESS>.22.jar with status code 503 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :ambari-metrics-emitter
The command '/bin/sh -c mvn install -ff -DskipTests -Dforbiddenapis.skip=true -Pdist -Pbundle-contrib-exts' returned a non-zero code: 1

It does fetch the files from your local dir (e.g. whatever you have checked
out). is it possible there was an error there?
I just tried from the RC tag:
don@cube[gke-corp]:druid$ git checkout -b druid-0.14.0-incubating-rc1
Switched to a new branch 'druid-0.14.0-incubating-rc1'
don@cube[gke-corp]:druid$ docker build -t druid:0.14.0 -f
distribution/docker/Dockerfile .
...
[INFO]
[INFO] Reactor Summary for Druid 0.15.0-incubating-SNAPSHOT:
[INFO]
[INFO] Druid .............................................. SUCCESS [
33.112 s]
[INFO] druid-core ......................................... SUCCESS [01:24
min]
[INFO] druid-hll .......................................... SUCCESS [
4.200 s]
[INFO] extendedset ........................................ SUCCESS [
2.976 s]
[INFO] druid-processing ................................... SUCCESS [
21.345 s]
[INFO] druid-aws-common ................................... SUCCESS [
4.630 s]
[INFO] druid-console ...................................... SUCCESS [
24.877 s]
[INFO] druid-server ....................................... SUCCESS [
26.654 s]
[INFO] druid-examples ..................................... SUCCESS [
5.936 s]
[INFO] druid-indexing-hadoop .............................. SUCCESS [
29.969 s]
[INFO] druid-indexing-service ............................. SUCCESS [
7.512 s]
[INFO] druid-sql .......................................... SUCCESS [
9.218 s]
[INFO] druid-services ..................................... SUCCESS [
11.430 s]
[INFO] druid-s3-extensions ................................ SUCCESS [
2.291 s]
[INFO] druid-datasketches ................................. SUCCESS [
3.742 s]
[INFO] druid-histogram .................................... SUCCESS [
2.981 s]
[INFO] mysql-metadata-storage ............................. SUCCESS [
2.301 s]
[INFO] druid-kafka-indexing-service ....................... SUCCESS [
6.335 s]
[INFO] druid-basic-security ............................... SUCCESS [
2.670 s]
[INFO] simple-client-sslcontext ........................... SUCCESS [
1.788 s]
[INFO] druid-integration-tests ............................ SUCCESS [
5.130 s]
[INFO] druid-benchmarks ................................... SUCCESS [
18.045 s]
[INFO] druid-avro-extensions .............................. SUCCESS [
24.472 s]
[INFO] druid-bloom-filter ................................. SUCCESS [
2.969 s]
[INFO] druid-kerberos ..................................... SUCCESS [
2.383 s]
[INFO] druid-hdfs-storage ................................. SUCCESS [
3.115 s]
[INFO] druid-stats ........................................ SUCCESS [
1.587 s]
[INFO] druid-kafka-eight .................................. SUCCESS [
3.535 s]
[INFO] druid-lookups-cached-global ........................ SUCCESS [
4.772 s]
[INFO] druid-kafka-extraction-namespace ................... SUCCESS [
2.186 s]
[INFO] druid-kinesis-indexing-service ..................... SUCCESS [
5.159 s]
[INFO] druid-parquet-extensions ........................... SUCCESS [
4.767 s]
[INFO] postgresql-metadata-storage ........................ SUCCESS [
2.715 s]
[INFO] druid-protobuf-extensions .......................... SUCCESS [
4.891 s]
[INFO] druid-lookups-cached-single ........................ SUCCESS [
2.436 s]
[INFO] druid-influx-extensions ............................ SUCCESS [
1.388 s]
[INFO] druid-azure-extensions ............................. SUCCESS [
1.911 s]
[INFO] druid-cassandra-storage ............................ SUCCESS [
6.038 s]
[INFO] druid-rocketmq ..................................... SUCCESS [
2.398 s]
[INFO] druid-cloudfiles-extensions ........................ SUCCESS [
11.416 s]
[INFO] graphite-emitter ................................... SUCCESS [
2.465 s]
[INFO] druid-kafka-eight-simple-consumer .................. SUCCESS [
1.497 s]
[INFO] druid-rabbitmq ..................................... SUCCESS [
1.860 s]
[INFO] druid-distinctcount ................................ SUCCESS [
1.428 s]
[INFO] statsd-emitter ..................................... SUCCESS [
4.146 s]
[INFO] druid-orc-extensions ............................... SUCCESS [
7.612 s]
[INFO] druid-time-min-max ................................. SUCCESS [
1.394 s]
[INFO] druid-google-extensions ............................ SUCCESS [
3.875 s]
[INFO] druid-virtual-columns .............................. SUCCESS [
1.480 s]
[INFO] druid-thrift-extensions ............................ SUCCESS [
7.749 s]
[INFO] ambari-metrics-emitter ............................. SUCCESS [
3.212 s]
[INFO] sqlserver-metadata-storage ......................... SUCCESS [
1.762 s]
[INFO] kafka-emitter ...................................... SUCCESS [
2.080 s]
[INFO] druid-redis-cache .................................. SUCCESS [
3.056 s]
[INFO] druid-opentsdb-emitter ............................. SUCCESS [
1.802 s]
[INFO] materialized-view-maintenance ...................... SUCCESS [
2.006 s]
[INFO] materialized-view-selection ........................ SUCCESS [
2.072 s]
[INFO] druid-momentsketch ................................. SUCCESS [
1.911 s]
[INFO] distribution ....................................... SUCCESS [01:22
min]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time:  08:54 min
[INFO] Finished at: 2019-03-26T02:28:23Z
[INFO]
Removing intermediate container e9517d295277
...
On Mon, 25 Mar 2019 at 19:10, Robert Espinoza<EMAIL_ADDRESS>wrote:

I am having issues building the docker image using the command in the
docker readme: docker build -t druid:0.14.0 -f
distribution/docker/Dockerfile .
Here is the build failure output:
[INFO] druid-time-min-max ................................. SUCCESS [
2.133 s]
[INFO] druid-google-extensions ............................ SUCCESS [
6.508 s]
[INFO] druid-virtual-columns .............................. SUCCESS [
2.119 s]
[INFO] druid-thrift-extensions ............................ SUCCESS [
9.566 s]
[INFO] ambari-metrics-emitter ............................. FAILURE [
2.370 s]
[INFO] sqlserver-metadata-storage ......................... SKIPPED
[INFO] kafka-emitter ...................................... SKIPPED
[INFO] druid-redis-cache .................................. SKIPPED
[INFO] druid-opentsdb-emitter ............................. SKIPPED
[INFO] materialized-view-maintenance ...................... SKIPPED
[INFO] materialized-view-selection ........................ SKIPPED
[INFO] druid-momentsketch ................................. SKIPPED
[INFO] distribution ....................................... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 10:02 min
[INFO] Finished at: 2019-03-25T23:08:02Z
[INFO]
[ERROR] Failed to execute goal on project ambari-metrics-emitter: Could
not resolve dependencies for project
org.apache.druid.extensions.contrib:ambari-metrics-emitter:jar:0.15.0-incubating-SNAPSHOT:
Could not transfer artifact
org.apache.ambari:ambari-metrics-common:jar:<IP_ADDRESS>.22 from/to hortonworks (
http://repo.hortonworks.com/content/repositories/releases): Failed to
transfer file
http://repo.hortonworks.com/content/repositories/releases/org/apache/ambari/ambari-metrics-common/<IP_ADDRESS>.22/ambari-metrics-common-<IP_ADDRESS>.22.jar
with status code 503 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn -rf :ambari-metrics-emitter
The command '/bin/sh -c mvn install -ff -DskipTests
-Dforbiddenapis.skip=true -Pdist -Pbundle-contrib-exts' returned a non-zero
code: 1
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-druid/pull/6896#issuecomment-476412013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE5Ok9dnuH44NVNsT7npKQdpuFhd_3xEks5vaVd3gaJpZM4aLkB1
.

I still get the error

[ERROR] Failed to execute goal on project ambari-metrics-emitter: Could not resolve dependencies for project org.apache.druid.extensions.contrib:ambari-metrics-emitter:jar:0.15.0-incubating-SNAPSHOT: Could not transfer artifact org.apache.ambari:ambari-metrics-common:jar:<IP_ADDRESS>.22 from/to hortonworks (http://repo.hortonworks.com/content/repositories/releases): Failed to transfer file http://repo.hortonworks.com/content/repositories/releases/org/apache/ambari/ambari-metrics-common/<IP_ADDRESS>.22/ambari-metrics-common-<IP_ADDRESS>.22.jar with status code 503

I also posted on here since it might be related that closed issue:
https://github.com/apache/incubator-druid/issues/4537

I still get the error

[ERROR] Failed to execute goal on project ambari-metrics-emitter: Could not resolve dependencies for project org.apache.druid.extensions.contrib:ambari-metrics-emitter:jar:0.15.0-incubating-SNAPSHOT: Could not transfer artifact org.apache.ambari:ambari-metrics-common:jar:<IP_ADDRESS>.22 from/to hortonworks (http://repo.hortonworks.com/content/repositories/releases): Failed to transfer file http://repo.hortonworks.com/content/repositories/releases/org/apache/ambari/ambari-metrics-common/<IP_ADDRESS>.22/ambari-metrics-common-<IP_ADDRESS>.22.jar with status code 503

I also posted on here since it might be related that closed issue:
#4537

is it possible you have a proxy or firewall in the path?
I can download the referenced file w/o the 503 you get.
maybe a cache?

@donbowman Yea that might the issue.  I tried building in a different computer and it was able to get all the way to the end but then failed on the distribution.

main:
[INFO] Executed tasks
[INFO]
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ distribution ---
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:exec (pull-deps) @ distribution ---
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Mar 28, 2019 3:57:01 AM org.hibernate.validator.internal.util.Version
INFO: HV000001: Hibernate Validator 5.1.3.Final
03:57:05.241 [main] ERROR org.apache.druid.cli.PullDependencies - Unable to resolve artifacts for [org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT (runtime) -> [] < [ (https://repo1.maven.org/maven2/, releases+snapshots)]].
org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384) ~[aether-impl-0.9.0.M2.jar:?]
at io.tesla.aether.internal.DefaultTeslaAether.resolveArtifacts(DefaultTeslaAether.java:289) ~[tesla-aether-0.0.5.jar:0.0.5]
Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (	at org.apache.druid.cli.PullDependencies.downloadExtension(PullDependencies.java:400) [druid-services-0.15.0-incubating-SNAPSHOT.jar:0.15.0-incubating-SNAPSHOT]
at org.apache.druid.cli.PullDependencies.run(PullDependencies.java:299) [druid-services-0.15.0-incubating-SNAPSHOT.jar:0.15.0-incubating-SNAPSHOT]
at org.apache.druid.cli.Main.main(Main.java:117) [druid-services-0.15.0-incubating-SNAPSHOT.jar:0.15.0-incubating-SNAPSHOT]
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
https://repo1.maven.org/maven2/)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:459) ~[aether-impl-0.9.0.M2.jar:?]
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262) ~[aether-impl-0.9.0.M2.jar:?]
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367) ~[aether-impl-0.9.0.M2.jar:?]
... 4 more
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
at io.tesla.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:828) ~[aether-connector-okhttp-0.0.9.jar:0.0.9]
at org.apache.druid.cli.PullDependencies.run(PullDependencies.java:323)
at org.apache.druid.cli.Main.main(Main.java:117)
at io.tesla.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:824) ~[aether-connector-okhttp-0.0.9.jar:0.0.9]
at io.tesla.aether.connector.AetherRepositoryConnector$GetTask.flush(AetherRepositoryConnector.java:619) ~[aether-connector-okhttp-0.0.9.jar:0.0.9]
at io.tesla.aether.connector.AetherRepositoryConnector.get(AetherRepositoryConnector.java:238) ~[aether-connector-okhttp-0.0.9.Caused by: java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.jar:0.0.9]
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:535) ~[aether-impl-0.9.0.M2.jar:?]
apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
at org.apache.druid.cli.PullDependencies.downloadExtension(PullDependencies.java:413)
at org.apache.druid.cli.PullDependencies.run(PullDependencies.java:299)
... 1 more
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
at io.tesla.aether.internal.DefaultTeslaAether.resolveArtifacts(DefaultTeslaAether.java:289)
at org.apache.druid.cli.PullDependencies.downloadExtension(PullDependencies.java:400)
... 2 more
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436) ~[aether-impl-0.9.0.M2.jar:?]
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262) ~[aether-impl-0.9.0.M2.jar:?]
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367) ~[aether-impl-0.9.0.M2.jar:?]
... 4 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:459)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
... 4 more
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.apache.druid.extensions:druid-google-extensions:jar:0.15.0-incubating-SNAPSHOT in  (https://repo1.maven.org/maven2/)
at io.tesla.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:828)
at io.tesla.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:824)
at io.tesla.aether.connector.AetherRepositoryConnector$GetTask.flush(AetherRepositoryConnector.java:619)
at io.tesla.aether.connector.AetherRepositoryConnector.get(AetherRepositoryConnector.java:238)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:535)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
... 6 more
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Druid 0.15.0-incubating-SNAPSHOT:
[INFO]
[INFO] Druid .............................................. SUCCESS [ 47.188 s]
[INFO] druid-core ......................................... SUCCESS [02:14 min]
[INFO] druid-hll .......................................... SUCCESS [  8.983 s]
[INFO] extendedset ........................................ SUCCESS [  5.054 s]
[INFO] druid-processing ................................... SUCCESS [ 34.886 s]
[INFO] druid-aws-common ................................... SUCCESS [  8.940 s]
[INFO] druid-gcp-common ................................... SUCCESS [  6.691 s]
[INFO] druid-console ...................................... SUCCESS [ 42.963 s]
[INFO] druid-server ....................................... SUCCESS [ 57.461 s]
[INFO] druid-examples ..................................... SUCCESS [  9.237 s]
[INFO] druid-indexing-hadoop .............................. SUCCESS [01:07 min]
[INFO] druid-indexing-service ............................. SUCCESS [  9.791 s]
[INFO] druid-sql .......................................... SUCCESS [ 20.586 s]
[INFO] druid-services ..................................... SUCCESS [ 13.657 s]
[INFO] druid-s3-extensions ................................ SUCCESS [  2.204 s]
[INFO] druid-datasketches ................................. SUCCESS [  5.365 s]
[INFO] druid-histogram .................................... SUCCESS [  3.603 s]
[INFO] mysql-metadata-storage ............................. SUCCESS [  3.189 s]
[INFO] druid-kafka-indexing-service ....................... SUCCESS [ 11.545 s]
[INFO] druid-basic-security ............................... SUCCESS [  3.160 s]
[INFO] simple-client-sslcontext ........................... SUCCESS [  2.036 s]
[INFO] druid-integration-tests ............................ SUCCESS [  7.488 s]
[INFO] druid-benchmarks ................................... SUCCESS [ 24.864 s]
[INFO] druid-avro-extensions .............................. SUCCESS [ 40.578 s]
[INFO] druid-bloom-filter ................................. SUCCESS [  4.275 s]
[INFO] druid-kerberos ..................................... SUCCESS [  2.794 s]
[INFO] druid-hdfs-storage ................................. SUCCESS [  4.179 s]
[INFO] druid-stats ........................................ SUCCESS [  1.852 s]
[INFO] druid-kafka-eight .................................. SUCCESS [  6.808 s]
[INFO] druid-lookups-cached-global ........................ SUCCESS [  9.768 s]
[INFO] druid-kafka-extraction-namespace ................... SUCCESS [  2.624 s]
[INFO] druid-kinesis-indexing-service ..................... SUCCESS [  9.363 s]
[INFO] druid-parquet-extensions ........................... SUCCESS [  9.126 s]
[INFO] postgresql-metadata-storage ........................ SUCCESS [  5.150 s]
[INFO] druid-protobuf-extensions .......................... SUCCESS [  8.850 s]
[INFO] druid-lookups-cached-single ........................ SUCCESS [  3.312 s]
[INFO] druid-ec2-extensions ............................... SUCCESS [  2.370 s]
[INFO] druid-google-extensions ............................ SUCCESS [  2.598 s]
[INFO] druid-influx-extensions ............................ SUCCESS [  1.553 s]
[INFO] druid-azure-extensions ............................. SUCCESS [  2.705 s]
[INFO] druid-cassandra-storage ............................ SUCCESS [ 17.027 s]
[INFO] druid-rocketmq ..................................... SUCCESS [  8.270 s]
[INFO] druid-cloudfiles-extensions ........................ SUCCESS [ 29.625 s]
[INFO] graphite-emitter ................................... SUCCESS [  3.725 s]
[INFO] druid-kafka-eight-simple-consumer .................. SUCCESS [  1.669 s]
[INFO] druid-rabbitmq ..................................... SUCCESS [  3.329 s]
[INFO] druid-distinctcount ................................ SUCCESS [  1.647 s]
[INFO] statsd-emitter ..................................... SUCCESS [ 10.834 s]
[INFO] druid-orc-extensions ............................... SUCCESS [  9.057 s]
[INFO] druid-time-min-max ................................. SUCCESS [  1.667 s]
[INFO] druid-virtual-columns .............................. SUCCESS [  1.676 s]
[INFO] druid-thrift-extensions ............................ SUCCESS [ 11.044 s]
[INFO] ambari-metrics-emitter ............................. SUCCESS [  6.588 s]
[INFO] sqlserver-metadata-storage ......................... SUCCESS [  2.197 s]
[INFO] kafka-emitter ...................................... SUCCESS [  4.234 s]
[INFO] druid-redis-cache .................................. SUCCESS [  5.004 s]
[INFO] druid-opentsdb-emitter ............................. SUCCESS [  2.184 s]
[INFO] materialized-view-maintenance ...................... SUCCESS [  2.445 s]
[INFO] materialized-view-selection ........................ SUCCESS [  2.465 s]
[INFO] druid-momentsketch ................................. SUCCESS [  4.241 s]
[INFO] distribution ....................................... FAILURE [ 10.252 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  13:08 min
[INFO] Finished at: 2019-03-28T03:57:05Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (pull-deps) on project distribution: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :distribution
The command '/bin/sh -c mvn install -ff -DskipTests -Dforbiddenapis.skip=true -Pdist -Pbundle-contrib-exts' returned a non-zero code: 1

After finally getting it to build and run, I was wondering how one goes about loading the wikipedia tutorial data described in the loading a file tutorial from the druid docs?  http://druid.io/docs/latest/tutorials/tutorial-batch.html
The overlord container does not seem to have bash and python installed to be able to run the script bin/post-index-task.
Or am I missing something here?

you run those from your host, outside the container, pointing @ the ports you exposed.

@donbowman After running the docker-compose up command to run druid, it seems to work fine.  But the issue I am having now is running the Load Batch Data tutorial by running the following command:
curl -X 'POST' -H 'Content-Type:application/json' -d @quickstart/tutorial/wikipedia-index.json http://localhost:8090/druid/indexer/v1/task from my local repo while inside the examples directory.  The ingestion task immediately fails after each time I try submitting the task.
And I changed the docker-compose services ports to match the same ports as the docker ports, so my overlord on my localhost is running on 8090.
Here is the output of the overlord gui console:

index_wikipedia_2019-04-02T02:43:17.912Z
index
2019-04-02T02:43:17.923Z
1970-01-01T00:00:00.000Z
FAILED
FAILED
NONE
3356
null
-1
-1
wikipedia
null

And here is the docker logs overload | grep FAIL:

2019-04-02T05:34:07,970 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] wrote FAILED status for task [index_wikipedia_2019-04-02T05:34:04.235Z] on [TaskLocation{host='<IP_ADDRESS>', port=8100, tlsPort=-1}]
2019-04-02T05:34:07,970 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] completed task[index_wikipedia_2019-04-02T05:34:04.235Z] with status[FAILED]
2019-04-02T05:34:07,971 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Received FAILED status for task: index_wikipedia_2019-04-02T05:34:04.235Z
2019-04-02T05:34:07,995 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.MetadataTaskStorage - Updating task index_wikipedia_2019-04-02T05:34:04.235Z to status: TaskStatus{id=index_wikipedia_2019-04-02T05:34:04.235Z, status=FAILED, duration=3474, errorMsg=null}
2019-04-02T05:34:07,998 ERROR [Curator-PathChildrenCache-1] org.apache.druid.java.util.emitter.core.LoggingEmitter - Event [{"feed":"metrics","timestamp":"2019-04-02T05:34:07.998Z","service":"druid/overlord","host":"<IP_ADDRESS>:8090","version":"0.15.0-incubating-SNAPSHOT","metric":"task/run/time","value":3474,"dataSource":"wikipedia","taskId":"index_wikipedia_2019-04-02T05:34:04.235Z","taskStatus":"FAILED","taskType":"index"}]
2019-04-02T05:34:07,998 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Task FAILED: AbstractTask{id='index_wikipedia_2019-04-02T05:34:04.235Z', groupId='index_wikipedia_2019-04-02T05:34:04.235Z', taskResource=TaskResource{availabilityGroup='index_wikipedia_2019-04-02T05:34:04.235Z', requiredCapacity=1}, dataSource='wikipedia', context={}} (3474 run duration)
2019-04-02T05:34:08,000 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T05:34:04.235Z] status changed to [FAILED].
2019-04-02T05:40:11,573 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] wrote FAILED status for task [index_wikipedia_2019-04-02T05:40:08.259Z] on [TaskLocation{host='<IP_ADDRESS>', port=8100, tlsPort=-1}]
2019-04-02T05:40:11,573 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] completed task[index_wikipedia_2019-04-02T05:40:08.259Z] with status[FAILED]
2019-04-02T05:40:11,573 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Received FAILED status for task: index_wikipedia_2019-04-02T05:40:08.259Z
2019-04-02T05:40:11,584 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.MetadataTaskStorage - Updating task index_wikipedia_2019-04-02T05:40:08.259Z to status: TaskStatus{id=index_wikipedia_2019-04-02T05:40:08.259Z, status=FAILED, duration=3285, errorMsg=null}
2019-04-02T05:40:11,588 ERROR [Curator-PathChildrenCache-1] org.apache.druid.java.util.emitter.core.LoggingEmitter - Event [{"feed":"metrics","timestamp":"2019-04-02T05:40:11.588Z","service":"druid/overlord","host":"<IP_ADDRESS>:8090","version":"0.15.0-incubating-SNAPSHOT","metric":"task/run/time","value":3285,"dataSource":"wikipedia","taskId":"index_wikipedia_2019-04-02T05:40:08.259Z","taskStatus":"FAILED","taskType":"index"}]
2019-04-02T05:40:11,588 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Task FAILED: AbstractTask{id='index_wikipedia_2019-04-02T05:40:08.259Z', groupId='index_wikipedia_2019-04-02T05:40:08.259Z', taskResource=TaskResource{availabilityGroup='index_wikipedia_2019-04-02T05:40:08.259Z', requiredCapacity=1}, dataSource='wikipedia', context={}} (3285 run duration)
2019-04-02T05:40:11,588 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T05:40:08.259Z] status changed to [FAILED].
2019-04-02T05:50:40,948 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] wrote FAILED status for task [index_wikipedia_2019-04-02T05:50:37.645Z] on [TaskLocation{host='<IP_ADDRESS>', port=8100, tlsPort=-1}]
2019-04-02T05:50:40,948 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] completed task[index_wikipedia_2019-04-02T05:50:37.645Z] with status[FAILED]
2019-04-02T05:50:40,949 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Received FAILED status for task: index_wikipedia_2019-04-02T05:50:37.645Z
2019-04-02T05:50:40,959 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.MetadataTaskStorage - Updating task index_wikipedia_2019-04-02T05:50:37.645Z to status: TaskStatus{id=index_wikipedia_2019-04-02T05:50:37.645Z, status=FAILED, duration=3277, errorMsg=null}
2019-04-02T05:50:40,961 ERROR [Curator-PathChildrenCache-1] org.apache.druid.java.util.emitter.core.LoggingEmitter - Event [{"feed":"metrics","timestamp":"2019-04-02T05:50:40.961Z","service":"druid/overlord","host":"<IP_ADDRESS>:8090","version":"0.15.0-incubating-SNAPSHOT","metric":"task/run/time","value":3277,"dataSource":"wikipedia","taskId":"index_wikipedia_2019-04-02T05:50:37.645Z","taskStatus":"FAILED","taskType":"index"}]
2019-04-02T05:50:40,961 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Task FAILED: AbstractTask{id='index_wikipedia_2019-04-02T05:50:37.645Z', groupId='index_wikipedia_2019-04-02T05:50:37.645Z', taskResource=TaskResource{availabilityGroup='index_wikipedia_2019-04-02T05:50:37.645Z', requiredCapacity=1}, dataSource='wikipedia', context={}} (3277 run duration)
2019-04-02T05:50:40,961 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T05:50:37.645Z] status changed to [FAILED].
2019-04-02T06:01:05,315 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] wrote FAILED status for task [index_wikipedia_2019-04-02T06:01:01.993Z] on [TaskLocation{host='<IP_ADDRESS>', port=8100, tlsPort=-1}]
2019-04-02T06:01:05,315 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] completed task[index_wikipedia_2019-04-02T06:01:01.993Z] with status[FAILED]
2019-04-02T06:01:05,316 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Received FAILED status for task: index_wikipedia_2019-04-02T06:01:01.993Z
2019-04-02T06:01:05,327 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.MetadataTaskStorage - Updating task index_wikipedia_2019-04-02T06:01:01.993Z to status: TaskStatus{id=index_wikipedia_2019-04-02T06:01:01.993Z, status=FAILED, duration=3291, errorMsg=null}
2019-04-02T06:01:05,329 ERROR [Curator-PathChildrenCache-1] org.apache.druid.java.util.emitter.core.LoggingEmitter - Event [{"feed":"metrics","timestamp":"2019-04-02T06:01:05.329Z","service":"druid/overlord","host":"<IP_ADDRESS>:8090","version":"0.15.0-incubating-SNAPSHOT","metric":"task/run/time","value":3291,"dataSource":"wikipedia","taskId":"index_wikipedia_2019-04-02T06:01:01.993Z","taskStatus":"FAILED","taskType":"index"}]
2019-04-02T06:01:05,329 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Task FAILED: AbstractTask{id='index_wikipedia_2019-04-02T06:01:01.993Z', groupId='index_wikipedia_2019-04-02T06:01:01.993Z', taskResource=TaskResource{availabilityGroup='index_wikipedia_2019-04-02T06:01:01.993Z', requiredCapacity=1}, dataSource='wikipedia', context={}} (3291 run duration)
2019-04-02T06:01:05,329 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T06:01:01.993Z] status changed to [FAILED].
2019-04-02T06:18:10,552 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] wrote FAILED status for task [index_wikipedia_2019-04-02T06:18:07.137Z] on [TaskLocation{host='<IP_ADDRESS>', port=8100, tlsPort=-1}]
2019-04-02T06:18:10,552 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.RemoteTaskRunner - Worker[<IP_ADDRESS>:8091] completed task[index_wikipedia_2019-04-02T06:18:07.137Z] with status[FAILED]
2019-04-02T06:18:10,552 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Received FAILED status for task: index_wikipedia_2019-04-02T06:18:07.137Z
2019-04-02T06:18:10,563 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.MetadataTaskStorage - Updating task index_wikipedia_2019-04-02T06:18:07.137Z to status: TaskStatus{id=index_wikipedia_2019-04-02T06:18:07.137Z, status=FAILED, duration=3387, errorMsg=null}
2019-04-02T06:18:10,565 ERROR [Curator-PathChildrenCache-1] org.apache.druid.java.util.emitter.core.LoggingEmitter - Event [{"feed":"metrics","timestamp":"2019-04-02T06:18:10.565Z","service":"druid/overlord","host":"<IP_ADDRESS>:8090","version":"0.15.0-incubating-SNAPSHOT","metric":"task/run/time","value":3387,"dataSource":"wikipedia","taskId":"index_wikipedia_2019-04-02T06:18:07.137Z","taskStatus":"FAILED","taskType":"index"}]
2019-04-02T06:18:10,565 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskQueue - Task FAILED: AbstractTask{id='index_wikipedia_2019-04-02T06:18:07.137Z', groupId='index_wikipedia_2019-04-02T06:18:07.137Z', taskResource=TaskResource{availabilityGroup='index_wikipedia_2019-04-02T06:18:07.137Z', requiredCapacity=1}, dataSource='wikipedia', context={}} (3387 run duration)
2019-04-02T06:18:10,565 INFO [Curator-PathChildrenCache-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T06:18:07.137Z] status changed to [FAILED].

And here is the docker logs middlemanager | grep FAIL:

2019-04-02T05:34:07,958 INFO [forking-task-runner-0] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T05:34:04.235Z] status changed to [FAILED].
2019-04-02T05:34:07,968 INFO [WorkerTaskManager-NoticeHandler] org.apache.druid.indexing.worker.WorkerTaskManager - Job's finished. Completed [index_wikipedia_2019-04-02T05:34:04.235Z] with status [FAILED]
2019-04-02T05:34:55,113 INFO [WorkerTaskManager-CompletedTasksCleaner] org.apache.druid.indexing.worker.WorkerTaskManager - Deleting completed task[index_wikipedia_2019-04-02T05:34:04.235Z] information, overlord task status[FAILED].
2019-04-02T05:40:11,567 INFO [forking-task-runner-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T05:40:08.259Z] status changed to [FAILED].
2019-04-02T05:40:11,571 INFO [WorkerTaskManager-NoticeHandler] org.apache.druid.indexing.worker.WorkerTaskManager - Job's finished. Completed [index_wikipedia_2019-04-02T05:40:08.259Z] with status [FAILED]
2019-04-02T05:44:54,999 INFO [WorkerTaskManager-CompletedTasksCleaner] org.apache.druid.indexing.worker.WorkerTaskManager - Deleting completed task[index_wikipedia_2019-04-02T05:40:08.259Z] information, overlord task status[FAILED].
2019-04-02T05:50:40,942 INFO [forking-task-runner-2] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T05:50:37.645Z] status changed to [FAILED].
2019-04-02T05:50:40,947 INFO [WorkerTaskManager-NoticeHandler] org.apache.druid.indexing.worker.WorkerTaskManager - Job's finished. Completed [index_wikipedia_2019-04-02T05:50:37.645Z] with status [FAILED]
2019-04-02T05:54:54,999 INFO [WorkerTaskManager-CompletedTasksCleaner] org.apache.druid.indexing.worker.WorkerTaskManager - Deleting completed task[index_wikipedia_2019-04-02T05:50:37.645Z] information, overlord task status[FAILED].
2019-04-02T06:01:05,306 INFO [forking-task-runner-0] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T06:01:01.993Z] status changed to [FAILED].
2019-04-02T06:01:05,313 INFO [WorkerTaskManager-NoticeHandler] org.apache.druid.indexing.worker.WorkerTaskManager - Job's finished. Completed [index_wikipedia_2019-04-02T06:01:01.993Z] with status [FAILED]
2019-04-02T06:04:54,997 INFO [WorkerTaskManager-CompletedTasksCleaner] org.apache.druid.indexing.worker.WorkerTaskManager - Deleting completed task[index_wikipedia_2019-04-02T06:01:01.993Z] information, overlord task status[FAILED].
2019-04-02T06:18:10,546 INFO [forking-task-runner-1] org.apache.druid.indexing.overlord.TaskRunnerUtils - Task [index_wikipedia_2019-04-02T06:18:07.137Z] status changed to [FAILED].
2019-04-02T06:18:10,550 INFO [WorkerTaskManager-NoticeHandler] org.apache.druid.indexing.worker.WorkerTaskManager - Job's finished. Completed [index_wikipedia_2019-04-02T06:18:07.137Z] with status [FAILED]
2019-04-02T06:19:54,996 INFO [WorkerTaskManager-CompletedTasksCleaner] org.apache.druid.indexing.worker.WorkerTaskManager - Deleting completed task[index_wikipedia_2019-04-02T06:18:07.137Z] information, overlord task status[FAILED].


“NoSuchMethodErrors” due to multiple versions of com.google.auth:google-auth-library-oauth2-http

Issue Description:
Hi, there are multiple versions of com.google.auth:google-auth-library-oauth2-http in google-cloud-java-1.24.0/java-monitoring/google-cloud-monitoring. As shown in the following dependency tree, according to Maven  "nearest wins" strategy, only com.google.auth:google-auth-library-oauth2-http:1.20.0 can be loaded, com.google.auth:google-auth-library-oauth2-http:1.4.0 and com.google.auth:google-auth-library-oauth2-http:1.20.0 will be shadowed.
However, several methods defined in shadowed version com.google.auth:google-auth-library-oauth2-http:1.4.0 are referenced by client project via com.google.api:gax-grpc:2.37.0 and com.google.api:gax:2.37.0 but missing in the actually loaded version com.google.auth:google-auth-library-oauth2-http:1.20.0.
For instance, the following missing method(defined in com.google.auth:google-auth-library-oauth2-http:1.4.0 and com.google.auth:google-auth-library-oauth2-http:1.20.0) are actually referenced by Google Cloud Monitoring, which will introduce a runtime error(i.e., "NoSuchMethodError") into Google Cloud Monitoring.

<com.google.auth.oauth2.ServiceAccountCredentials: java.lang.String getQuotaProjectId()>  is invoked by Google Cloud Monitoring via the following path:

paths--
<com.google.cloud.monitoring.v3.stub.GroupServiceStubSettings$Builder: void init (com.google.api.gax.rpc.ClientContext)> com.google.cloud:google-cloud-monitoring:3.31.0;
<com.google.api.gax.rpc.StubSettings$Builder: void init (com.google.api.gax.rpc.ClientContext)> com.google.api:gax:2.37.0;
<com.google.api.gax.rpc.StubSettings$Builder: java.lang.String getQuotaProjectIdFromClientContext(com.google.api.gax.rpc.ClientContext)> com.google.api:gax:2.37.0;
<com.google.auth.oauth2.ServiceAccountCredentials: java.lang.String getQuotaProjectId()>

Suggested fixing solutions:

Upgrade direct dependency com.google.auth:google-auth-library-oauth2-http from 1.20.0 to 1.20.0. Because version 1.20.0 includes the above missing methods and is compatible with other versions of com.google.auth:google-auth-library-oauth2-http in the project.

Please let me know if you agree to this solution? I can submit a PR to fix it.
Thank you very much for your attention.
Best regards,
Dependency tree --

[INFO] |  |  +- (io.grpc:grpc-protobuf:jar:1.59.0:compile - version managed from 1.59.0; omitted for duplicate)
[INFO] |  |  +- (io.grpc:grpc-stub:jar:1.59.0:compile - version managed from 1.59.0; omitted for duplicate)
[INFO] |  |  +- (com.google.protobuf:protobuf-java:jar:3.24.4:compile - version managed from 3.24.0; omitted for duplicate)
[INFO] |  |  +- org.conscrypt:conscrypt-openjdk-uber:jar:2.5.2:compile
[INFO] |  |  +- (com.google.guava:guava:jar:32.1.2-jre:compile - version managed from 32.0.1-jre; omitted for duplicate)
[INFO] |  |  +- (com.google.auth:google-auth-library-oauth2-http:jar:1.20.0:compile - version managed from 1.4.0; omitted for duplicate)
[INFO] |  |  \- (io.grpc:grpc-netty-shaded:jar:1.59.0:compile - version managed from 1.59.0; omitted for duplicate)
[INFO] |  +- io.grpc:grpc-auth:jar:1.59.0:compile (version managed from 1.59.0; scope not updated to compile)
[INFO] |  |  +- (io.grpc:grpc-api:jar:1.59.0:compile - version managed from 1.59.0; omitted for duplicate)
[INFO] |  |  +- (com.google.auth:google-auth-library-credentials:jar:1.20.0:compile - version managed from 1.4.0; omitted for duplicate)
[INFO] |  |  \- (com.google.guava:guava:jar:32.1.2-jre:runtime - version managed from 32.0.1-android; omitted for duplicate)
[INFO] |  +- (io.grpc:grpc-protobuf:jar:1.59.0:compile - version managed from 1.59.0; omitted for duplicate)
[INFO] |  +- (io.grpc:grpc-stub:jar:1.59.0:compile - version managed from 1.59.0; omitted for duplicate)
[INFO] |  +- io.grpc:grpc-netty-shaded:jar:1.59.0:compile (version managed from 1.59.0; scope not updated to compile)
[INFO] |  |  +- (com.google.guava:guava:jar:32.1.2-jre:runtime - version managed from 32.0.1-android; omitted for duplicate)

Upgrade direct dependency com.google.auth:google-auth-library-oauth2-http from 1.20.0 to 1.20.0.

It seems there's a typo. Both versions are the same. Would you correct the suggestion?

I'll close this issue. If you really encounter dependency conflicts, let us know.


Code refactoring

Description
This PR contains two commits:

Introduces ConnectorIntegrationTest base class for connectors integration tests.
Introduces and uses AuthorisationRequest instead of User request.

There is no story for this work.
Add a link to the relevant story in Jira
[SASS-CHANGE-ME](ADD URL HERE)
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[ ]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[x]  Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[x]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[x]  Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
[x]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of main?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[ ]  Have you checked the PR Builder passes?

can be rebased


CLI: have an option to get raw json from the send event command

Is your feature request related to a problem? Please describe.
To make it easier to add into scripts.  Currently the output is plain text of just the keptn context id
Describe the solution you'd like
have command line option like -o json
Describe alternatives you've considered
in bash have to do things like: KEPTN_CONTEXT_ID=$(echo $POST_RESPONSE| grep "ID of Keptn context" | cut -d ":" -f2 | tr -d '[:space:]')
Additional context
This is related to same need in issue: https://github.com/keptn/keptn/issues/6713

I opened this issue for this one command, but I would love it if ALL the commands had the option to output JSON.
@johannes-b if you agree having this be more the universal behavior, should we rename this issue title if this issue or shall I open a new issue?


Fixes GHES docs for PAT as SSO not available

Why:
GitHub Enterprise Server (GHES) allows generating personal access tokens (PATs), but unlike GitHub Cloud or GitHub Enterprise Cloud (GHEC) there is no option in GHES to enable SAML SSO for PATs.
Closes: #33696

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adds a screenshot from GHES that doesn't show PAT with "configure SSO"
Updates PAT docs to use new screenshot for GHES

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@amarvin Thanks so much for opening a PR! I'll get this triaged for review ✨

Thanks, @nguyenalex836!

Hi @amarvin, thanks for working on this, it looks like a really good change!
Before we merge this, can I ask you to make one tiny change? Our style guide asks us not to include liquid conditionals in filenames, this can cause problems for a few automations we have.
It won't look as neat but could you change this so we have two complete image tags? For example:
{% ifversion ghes %}![Screenshot of the "{% data variables.product.pat_generic_caps_plural %}" page. Next to a blurred-out token, an icon of two overlapping squares is outlined in orange.](/assets/images/help/settings/personal-access-tokens-ghes.png){% else %}![Screenshot of the "{% data variables.product.pat_generic_caps_plural %}" page. Next to a blurred-out token, an icon of two overlapping squares is outlined in orange.](/assets/images/help/settings/personal-access-tokens.png){% endif %}
Let me know once you've made the change so I can review and get this merged! ✨

Hi @amarvin, thanks for working on this, it looks like a really good change!
Before we merge this, can I ask you to make one tiny change? Our style guide asks us not to include liquid conditionals in filenames, this can cause problems for a few automations we have.
It won't look as neat but could you change this so we have two complete image tags? For example:
{% ifversion ghes %}![Screenshot of the "{% data variables.product.pat_generic_caps_plural %}" page. Next to a blurred-out token, an icon of two overlapping squares is outlined in orange.](/assets/images/help/settings/personal-access-tokens-ghes.png){% else %}![Screenshot of the "{% data variables.product.pat_generic_caps_plural %}" page. Next to a blurred-out token, an icon of two overlapping squares is outlined in orange.](/assets/images/help/settings/personal-access-tokens.png){% endif %}
Let me know once you've made the change so I can review and get this merged! ✨

Great point and sorry for missing that in the style guide! I've made the change for you to review.

@stevecat, this is ready for your review.

nudge @stevecat

@amarvin Hello! 👋 Thank you very much for your patience - it looks like @stevecat might not be available for a little while. The changes you made as requested look great! I'll go ahead and get this merged 💛 Thank you again for your patience!


Create transformer for MEDLINE database records

If the result is not from MEDLINE it can be skipped.

Blocked by https://github.com/sul-dlss/rialto/issues/26? or maybe a missing ticket?

MEDLINE records come from the WoS API, but have a different data structure (since they come from a different database on Clarivate's end and Clarivate is not normalizing into a single data structure), so will require a different mapping than WoS database records.  Including them would improve our publication coverage in RIALTO, but can be deferred for if/when we have time to loop back and include them in the publication harvest.


about fix_events_for_older_kernels

is it a bug?
I run this plugin and I can't collect perf stat, this is the error:
cpu/event=0x80,umask=0x4,cmask=0x1,edge=0x1,name=ICACHE_16B.c: No such file or directory
But I can run this plugin successfully after I fix this function:fix_events_for_older_kernels.
I fix "int(kernel_part_number) >= 1000" to "int(kernel_part_number) <= 1000", and I can run it.
environment:
CentOS Linux release 7.2.1511 (Core)
3.10.0-693.el7.x86_64
perf version 3.10.0-1160.83.1.el7.x86_64.debug

Thanks for providing the environment information. Could you also run this tool https://github.com/intel/svr-info and upload the output html file. I'm curious about your hardware's information (SPR, ICX, SKU etc.)

this got fixed in the most recent release https://github.com/intel/PerfSpect/releases/tag/1.2.5 and extended support to centos 7 kernel 3.10


[python/ci] Pin dask version 2024.11.2 to unblock CI

Issue and/or context: #3398
Changes: Pinning dask to 2024.11.2 version
Notes for Reviewer:

@johnkerl Can i have your final acceptance review here?


Prevent crash when requesting unavailable functionality

This fixes #106 - Back in #48 we broke some functionality that would return sensible errors when an API consumer requests an unavailable CRUD feature.
With this change, if you remove the MemoryStore.prototype.search function within lib/memoryHandler.js and visit http://localhost:16006/rest/articles you'll see this:
{
  jsonapi: {
    version: "1.0"
  },
  meta: {
    description: "This block shows up in the root node of every payload"
  },
  links: {
    self: "http://localhost:16006/rest/articles"
  },
  errors: [
    {
      status: "403",
      code: "EFORBIDDEN",
      title: "Resource not supported",
      detail: "The requested resource 'articles' does not support 'search'"
    }
  ]
}

Which was the original expected behaviour.

Can we add a regression test for this where we disable one of the functions and verify we get the 403 error?

Yep, absolutely :+1:

@pmcnr-hx - Test added :+1:


Report an error

Hi, RekGRpth, thanks for your excellent work, it really helps me a lot.
I compiled the module with nginx-1.24.0 on windows. It basically works fine, but errors of [crit] level will be logged, if a connection in the queue is closed by client. It seems the socket cannot be terminated as expected in that case.
Here is the steps to reproduce the error:

Prepare a toy backend-server, which never respond to requests.
Run nginx with the appended config file. This config only allows one connection to the backend.
Open two browser tabs to <IP_ADDRESS>, Only the first request will be able to reach backend, and the second one has to wait in the queue.
Close the second tab.

Then the error could be found in log:

2024/04/08 19:37:22 [info] 6652#12568: *4 client prematurely closed connection, so upstream connection is closed too while connecting to upstream, client: <IP_ADDRESS>, server: localhost, request: "GET / HTTP/1.1", upstream: "http://backend_server/", host: "<IP_ADDRESS>"
2024/04/08 19:37:22 [debug] 6652#12568: *4 finalize http upstream request: 499
2024/04/08 19:37:22 [debug] 6652#12568: *4 finalize http proxy request
2024/04/08 19:37:22 [debug] 6652#12568: *4 close http upstream connection: 0
2024/04/08 19:37:22 [debug] 6652#12568: *4 free: 0000022A07576C80, unused: 48
2024/04/08 19:37:22 [debug] 6652#12568: *4 event timer del: 0:<PHONE_NUMBER>907
2024/04/08 19:37:22 [debug] 6652#12568: *4 reusable connection: 0
2024/04/08 19:37:22 [crit] 6652#12568: *4 closesocket() 0 failed (10038: An operation was attempted on something that is not a socket) while connecting to upstream, client: <IP_ADDRESS>, server: localhost, request: "GET / HTTP/1.1", upstream: "http://backend_server/", host: "<IP_ADDRESS>"

nginx.conf:
worker_processes 128;
error_log logs/error.log debug;

events {
    worker_connections 1024;
}

http {
    include mime.types;
    default_type application/octet-stream;

    access_log off;
    keepalive_timeout 0;

    upstream backend_server {
        server <IP_ADDRESS>:10000 max_conns=1;
        queue 1024 timeout=1m;
    }

    server {
        listen 80;
        server_name localhost;

        location / {
             #root html;
             #index index.html;

            proxy_pass http://backend_server;
            proxy_read_timeout 10d;
        }

    }
}

Although nginx will continue working properly, I'm not sure whether further problems will be caused. Could this problem be fixed?

It seems the bug was introduced by the last commit. Try without it.

fixed by https://github.com/RekGRpth/ngx_http_upstream_queue_module/commit/8ce938eb5bc3e785caf1bed1884a63b42fbc7b4b

Thanks for your reply. The error still exists. I noticed the modification is made in  "ngx_http_upstream_queue_peer_free". It seems the error happens before this function is called. Below is the complete error_log by following the steps listed above:
the error could be find at "2024/04/09 13:33:14 [crit] 1880#14996"

2024/04/09 13:33:08 [debug] 9004#13496: bind() <IP_ADDRESS>:80 #496
2024/04/09 13:33:08 [notice] 9004#13496: using the "select" event method
2024/04/09 13:33:08 [debug] 9004#13496: malloc: 000001B46DF47D70:30
2024/04/09 13:33:08 [debug] 9004#13496: counter:<PHONE_NUMBER>E00080, 1
2024/04/09 13:33:08 [notice] 9004#13496: nginx/1.24.0
2024/04/09 13:33:08 [info] 9004#13496: OS: 260200 build:9200, "", suite:100, type:1
2024/04/09 13:33:08 [debug] 9004#13496: master started
2024/04/09 13:33:08 [debug] 9004#13496: close listening <IP_ADDRESS>:80 #496
2024/04/09 13:33:08 [notice] 9004#13496: start worker processes
2024/04/09 13:33:08 [debug] 9004#13496: GetModuleFileName: "C:\nginx\nginx.exe"
2024/04/09 13:33:08 [notice] 9004#13496: start worker process 1880
2024/04/09 13:33:08 [debug] 1880#11788: bind() <IP_ADDRESS>:80 #496
2024/04/09 13:33:08 [debug] 1880#11788: malloc: 000002385F9D8690:30
2024/04/09 13:33:08 [debug] 1880#11788: counter:<PHONE_NUMBER>E00080, 1
2024/04/09 13:33:08 [notice] 1880#11788: nginx/1.24.0
2024/04/09 13:33:08 [info] 1880#11788: OS: 260200 build:9200, "", suite:100, type:1
2024/04/09 13:33:08 [debug] 1880#11788: worker started
2024/04/09 13:33:08 [debug] 9004#13496: WaitForMultipleObjects: 0
2024/04/09 13:33:08 [notice] 1880#11788: create thread 14996
2024/04/09 13:33:08 [notice] 1880#11788: create thread 12380
2024/04/09 13:33:08 [notice] 1880#11788: create thread 1416
2024/04/09 13:33:08 [debug] 1880#14996: malloc: 000002385FA05A10:16384
2024/04/09 13:33:08 [debug] 1880#14996: malloc: 000002385FA2BE80:237568
2024/04/09 13:33:08 [debug] 1880#14996: malloc: 000002385FA65E90:147456
2024/04/09 13:33:08 [debug] 1880#12380: cache manager WaitForMultipleObjects: 1
2024/04/09 13:33:08 [debug] 1880#14996: malloc:<PHONE_NUMBER>4A0080:147456
2024/04/09 13:33:08 [debug] 1880#14996: select add event fd:496 ev:768
2024/04/09 13:33:08 [debug] 1880#14996: worker cycle
2024/04/09 13:33:08 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:08 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:08 [debug] 1880#14996: select ready 0
2024/04/09 13:33:08 [debug] 1880#14996: timer delta: 511
2024/04/09 13:33:08 [debug] 1880#14996: worker cycle
2024/04/09 13:33:08 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:08 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:09 [debug] 1880#14996: select ready 0
2024/04/09 13:33:09 [debug] 1880#14996: timer delta: 502
2024/04/09 13:33:09 [debug] 1880#14996: worker cycle
2024/04/09 13:33:09 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:09 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:09 [debug] 1880#14996: select ready 0
2024/04/09 13:33:09 [debug] 1880#14996: timer delta: 501
2024/04/09 13:33:09 [debug] 1880#14996: worker cycle
2024/04/09 13:33:09 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:09 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:10 [debug] 1880#14996: select ready 0
2024/04/09 13:33:10 [debug] 1880#14996: timer delta: 502
2024/04/09 13:33:10 [debug] 1880#14996: worker cycle
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:10 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:10 [debug] 1880#14996: select ready 1
2024/04/09 13:33:10 [debug] 1880#14996: select read 496
2024/04/09 13:33:10 [debug] 1880#14996: post event 000002385FA65E90
2024/04/09 13:33:10 [debug] 1880#14996: timer delta: 201
2024/04/09 13:33:10 [debug] 1880#14996: posted event 000002385FA65E90
2024/04/09 13:33:10 [debug] 1880#14996: delete posted event 000002385FA65E90
2024/04/09 13:33:10 [debug] 1880#14996: accept on <IP_ADDRESS>:80, ready: 0
2024/04/09 13:33:10 [debug] 1880#14996: malloc: 000002385FA09B60:512
2024/04/09 13:33:10 [debug] 1880#14996: *1 accept: <IP_ADDRESS>:51112 fd:560
2024/04/09 13:33:10 [debug] 1880#14996: *1 event timer add: 560: 60000:1712640850557
2024/04/09 13:33:10 [debug] 1880#14996: *1 reusable connection: 1
2024/04/09 13:33:10 [debug] 1880#14996: *1 select add event fd:560 ev:768
2024/04/09 13:33:10 [debug] 1880#14996: worker cycle
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:560 wr:0
2024/04/09 13:33:10 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:10 [debug] 1880#14996: select ready 1
2024/04/09 13:33:10 [debug] 1880#14996: select read 560
2024/04/09 13:33:10 [debug] 1880#14996: *1 post event 000002385FA65F20
2024/04/09 13:33:10 [debug] 1880#14996: timer delta: 0
2024/04/09 13:33:10 [debug] 1880#14996: posted event 000002385FA65F20
2024/04/09 13:33:10 [debug] 1880#14996: *1 delete posted event 000002385FA65F20
2024/04/09 13:33:10 [debug] 1880#14996: *1 http wait request handler
2024/04/09 13:33:10 [debug] 1880#14996: *1 malloc: 000002385FA09D70:1024
2024/04/09 13:33:10 [debug] 1880#14996: *1 WSARecv: fd:560 rc:0 441 of 1024
2024/04/09 13:33:10 [debug] 1880#14996: *1 reusable connection: 0
2024/04/09 13:33:10 [debug] 1880#14996: *1 malloc:<PHONE_NUMBER>4C4090:4096
2024/04/09 13:33:10 [debug] 1880#14996: *1 http process request line
2024/04/09 13:33:10 [debug] 1880#14996: *1 http request line: "GET / HTTP/1.1"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http uri: "/"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http args: ""
2024/04/09 13:33:10 [debug] 1880#14996: *1 http exten: ""
2024/04/09 13:33:10 [debug] 1880#14996: *1 malloc: 000002385FA0EA40:4096
2024/04/09 13:33:10 [debug] 1880#14996: *1 http process request header line
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Host: <IP_ADDRESS>"
2024/04/09 13:33:10 [debug] 1880#14996: 1 http header: "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0"
2024/04/09 13:33:10 [debug] 1880#14996: 1 http header: "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Accept-Language: en-US,en;q=0.5"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Accept-Encoding: gzip, deflate, br"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Connection: keep-alive"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Upgrade-Insecure-Requests: 1"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Sec-Fetch-Dest: document"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Sec-Fetch-Mode: navigate"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Sec-Fetch-Site: none"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header: "Sec-Fetch-User: ?1"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http header done
2024/04/09 13:33:10 [debug] 1880#14996: *1 event timer del: 560:<PHONE_NUMBER>557
2024/04/09 13:33:10 [debug] 1880#14996: *1 generic phase: 0
2024/04/09 13:33:10 [debug] 1880#14996: *1 rewrite phase: 1
2024/04/09 13:33:10 [debug] 1880#14996: *1 test location: "/"
2024/04/09 13:33:10 [debug] 1880#14996: *1 using configuration "/"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http cl:-1 max:1048576
2024/04/09 13:33:10 [debug] 1880#14996: *1 rewrite phase: 3
2024/04/09 13:33:10 [debug] 1880#14996: *1 post rewrite phase: 4
2024/04/09 13:33:10 [debug] 1880#14996: *1 generic phase: 5
2024/04/09 13:33:10 [debug] 1880#14996: *1 generic phase: 6
2024/04/09 13:33:10 [debug] 1880#14996: *1 generic phase: 7
2024/04/09 13:33:10 [debug] 1880#14996: *1 access phase: 8
2024/04/09 13:33:10 [debug] 1880#14996: *1 access phase: 9
2024/04/09 13:33:10 [debug] 1880#14996: *1 access phase: 10
2024/04/09 13:33:10 [debug] 1880#14996: *1 post access phase: 11
2024/04/09 13:33:10 [debug] 1880#14996: *1 generic phase: 12
2024/04/09 13:33:10 [debug] 1880#14996: *1 generic phase: 13
2024/04/09 13:33:10 [debug] 1880#14996: *1 http init upstream, client timer: 0
2024/04/09 13:33:10 [debug] 1880#14996: *1 http script copy: "Host"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http script var: "backend_server"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http script copy: "Connection"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http script copy: "close"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http script copy: ""
2024/04/09 13:33:10 [debug] 1880#14996: *1 http script copy: ""
2024/04/09 13:33:10 [debug] 1880#14996: 1 http proxy header: "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0"
2024/04/09 13:33:10 [debug] 1880#14996: 1 http proxy header: "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http proxy header: "Accept-Language: en-US,en;q=0.5"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http proxy header: "Accept-Encoding: gzip, deflate, br"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http proxy header: "Upgrade-Insecure-Requests: 1"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http proxy header: "Sec-Fetch-Dest: document"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http proxy header: "Sec-Fetch-Mode: navigate"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http proxy header: "Sec-Fetch-Site: none"
2024/04/09 13:33:10 [debug] 1880#14996: 1 http proxy header: "Sec-Fetch-User: ?1"
2024/04/09 13:33:10 [debug] 1880#14996: 1 http proxy header:
"GET / HTTP/1.0
Host: backend_server
Connection: close
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Upgrade-Insecure-Requests: 1
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: none
Sec-Fetch-User: ?1
"
2024/04/09 13:33:10 [debug] 1880#14996: *1 http cleanup add:<PHONE_NUMBER>4C5078
2024/04/09 13:33:10 [debug] 1880#14996: *1 ngx_http_upstream_queue_peer_init
2024/04/09 13:33:10 [debug] 1880#14996: *1 ngx_http_upstream_queue_peer_get
2024/04/09 13:33:10 [debug] 1880#14996: *1 get rr peer, try: 1
2024/04/09 13:33:10 [debug] 1880#14996: *1 peer.get = 0
2024/04/09 13:33:10 [debug] 1880#14996: *1 stream socket 564
2024/04/09 13:33:10 [debug] 1880#14996: *1 connect to <IP_ADDRESS>:10000, fd:564 #2
2024/04/09 13:33:10 [debug] 1880#14996: *1 select add event fd:564 ev:768
2024/04/09 13:33:10 [debug] 1880#14996: *1 select add event fd:564 ev:16
2024/04/09 13:33:10 [debug] 1880#14996: *1 http upstream connect: -2
2024/04/09 13:33:10 [debug] 1880#14996: *1 malloc: 000002385F9BC010:128
2024/04/09 13:33:10 [debug] 1880#14996: *1 event timer add: 564: 60000:1712640850557
2024/04/09 13:33:10 [debug] 1880#14996: *1 http finalize request: -4, "/?" a:1, c:2
2024/04/09 13:33:10 [debug] 1880#14996: *1 http request count:2 blk:0
2024/04/09 13:33:10 [debug] 1880#14996: worker cycle
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:496 wr:0
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:560 wr:0
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:564 wr:0
2024/04/09 13:33:10 [debug] 1880#14996: select event: fd:564 wr:1
2024/04/09 13:33:10 [debug] 1880#14996: select timer: 500
2024/04/09 13:33:10 [debug] 1880#14996: select ready 1
2024/04/09 13:33:10 [debug] 1880#14996: select write 564
2024/04/09 13:33:10 [debug] 1880#14996: *1 post event<PHONE_NUMBER>4A01A0
2024/04/09 13:33:10 [debug] 1880#14996: timer delta: 0
2024/04/09 13:33:10 [debug] 1880#14996: posted event<PHONE_NUMBER>4A01A0
2024/04/09 13:33:10 [debug] 1880#14996: *1 delete posted event<PHONE_NUMBER>4A01A0
2024/04/09 13:33:10 [debug] 1880#14996: *1 http upstream request: "/?"

2024/04/09 13:33:14 [debug] 1880#14996: *3 http upstream check client, write event:0, "/"
2024/04/09 13:33:14 [debug] 1880#14996: *3 http upstream recv(): 0
2024/04/09 13:33:14 [debug] 1880#14996: *3 select del event fd:584 ev:768
2024/04/09 13:33:14 [info] 1880#14996: *3 client prematurely closed connection, so upstream connection is closed too while connecting to upstream, client: <IP_ADDRESS>, server: localhost, request: "GET / HTTP/1.1", upstream: "http://backend_server/", host: "<IP_ADDRESS>"
2024/04/09 13:33:14 [debug] 1880#14996: *3 finalize http upstream request: 499
2024/04/09 13:33:14 [debug] 1880#14996: *3 finalize http proxy request
2024/04/09 13:33:14 [debug] 1880#14996: *3 close http upstream connection: 0
2024/04/09 13:33:14 [debug] 1880#14996: *3 free: 000002385F9BBB90, unused: 48
2024/04/09 13:33:14 [debug] 1880#14996: *3 event timer del: 0:<PHONE_NUMBER>984
2024/04/09 13:33:14 [debug] 1880#14996: *3 reusable connection: 0
2024/04/09 13:33:14 [crit] 1880#14996: *3 closesocket() 0 failed (10038: An operation was attempted on something that is not a socket) while connecting to upstream, client: <IP_ADDRESS>, server: localhost, request: "GET / HTTP/1.1", upstream: "http://backend_server/", host: "<IP_ADDRESS>"
2024/04/09 13:33:14 [debug] 1880#14996: *3 http finalize request: 499, "/?" a:1, c:1
2024/04/09 13:33:14 [debug] 1880#14996: *3 http terminate request count:1
2024/04/09 13:33:14 [debug] 1880#14996: *3 http terminate cleanup count:1 blk:0
2024/04/09 13:33:14 [debug] 1880#14996: *3 http posted request: "/?"

I opened a tcp server with matlab "Backend=tcpserver(10000)" as backend, whose port is 10000. It can accept tcp connection and receive http requests. This Backend allows a connection keeping alive forever, and no response will be automatically sent back.
By doing this, the first client can build a connection and sent its request to the toy Backend, but it will wait for response forever (if no timeout is set). Then latter connections from other clients are put in the queue. Error happens when we close a waiting client in the queue.
No further problem is observed. After the error, If I let the Backend start to send responses, the queue will start running as expected: the closed client will be skipped.

I have already found the reason for the problem and work on its elimination ...

fixed by https://github.com/RekGRpth/ngx_http_upstream_queue_module/commit/0d83416edb780ced4d226c404f313132c4c56b14

hi @RekGRpth, can you explain more about the modifaction?
I can see the goal is to set shared = 1 to avoid connection removal. But in my opinion, when calling ngx_event_connect_peer internally will call ngx_get_connection anyway, this function will give u->peer->connection a new avaliable freeconnection.
how to keep that shared = 1 setting still avalibale?

can you explain more about the modifaction?

Does the last solution work for you?

I can see the goal is to set shared = 1 to avoid connection removal

No, I set this so that the ngx_close_connection function does not try to close socket 0 of the dummy connection.

can you explain more about the modifaction?

Does the last solution work for you?

seems all the requests will return 502.  queue size is set to 10.

when calling ngx_event_connect_peer internally will call ngx_get_connection anyway

Yes, the dummy connection is overwritten by the real one.

I can see the goal is to set shared = 1 to avoid connection removal

No, I set this so that the ngx_close_connection function does not try to close socket 0 of the dummy connection.

socket 0 or fd = 0 is the stdin, right? so the root case for the original error is that stdin is closed?

socket 0 or fd = 0 is the stdin, right?

yes

so the root case for the original error is that stdin is closed?

No, initially the error was that I was manually creating a dummy connection rather than taking it from the pool, and then this dummy connection ended up in the pool and an error occurred when using it.

Maybe I should close this dummy connection first?

did

I do a request and then it quickly fullup the queue size ,and cause all the request after that return 502. queue size is set to 10.

Isn't that exactly how it should work?

I only triggered 1 http call , and then queue filled up. and the 2nd http call will return 502, since queue is full.

above is the calltrace for the very begining, since we return NGX_AGAIN in peer_get, we runs into:

and then it comes over and over again, till queue is fulled up:

I only triggered 1 http call , and then queue filled up. and the 2nd http call will return 502, since queue is full.

I run in one window
while true; do nc -lp 10000; done

then in second window
curl <IP_ADDRESS>

then in third window
curl <IP_ADDRESS>

then in fourth window
curl <IP_ADDRESS>

and no errors
also in fourth window I press Ctrl+C to interrupt and again run, and no errors
my config
upstream backend_server {
    server <IP_ADDRESS>:10000 max_conns=1;
    queue 10;
}
server {
    listen 80 default_server;
    listen [::]:80 default_server;
    error_log stderr error;
    access_log off;
    location / {
        keepalive_timeout 0;
        access_log /var/log/nginx/nginx/backend_server.log main;
        error_log /var/log/nginx/nginx/backend_server.err debug;
        proxy_pass http://backend_server;
        proxy_read_timeout 10d;
    }
}

I think its duel to the proxy_connect_timeout config . if u set to 1s, it will run up the queue size.

I think its duel to the proxy_connect_timeout config . if u set to 1s, it will run up the queue size.

fixed by https://github.com/RekGRpth/ngx_http_upstream_queue_module/commit/524b621f5ebc4ccaa0604aa5e2fed0f407a04c5a

hi @RekGRpth , although we can avoid queue fillup by if we use ngx_min(u->conf->connect_timeout, qscf->timeout), but we are losing the ability of queue the request with the timeout set by queue directive.
Maybe we should test the connection in peer_get phase?

but we are losing the ability of queueing requests with the timeout set by queue directive.

Why? It is only when u->conf->connect_timeout < qscf->timeout

Maybe we should test the connection in peer_get phase?

What do you mean?

but we are losing the ability of queueing requests with the timeout set by queue directive.

Why? It is only when u->conf->connect_timeout < qscf->timeout

yes, as we always will config proxy_connect_timeout to a small value like 1s or 3s.  but in queue directive, we will config size like 1k, and timeout like 10-30s. which means queue's timeout will be overwrite by connection timeout in most of cases.

we always will config proxy_connect_timeout to a small value like 1s or 3s.

Why?

function ngx_http_upstream_connect ngx_add_timer(c->write, u->conf->connect_timeout) after my function ngx_http_upstream_queue_peer_get return NGX_AGAIN, so single solution is use queue's timeout < connection timeout

yes, thats the hard part.
since peer.get happens before ngx_get_connection, we have no idead wether this connection can be established or not.
so is it possible if we test connection first and if connection can't be established we don't add this request in queue?

we test connection first and if connection can't be established

then we add this request to queue

are you using keepalive option?

no

can we change the queue to a hashset liked queue, when the same request comes again, just ignore it.

By the way, I have an idea how to remove the connection timeout timer after being queued...

By the way, I have an idea how to remove the connection timeout timer after being queued...

done via https://github.com/RekGRpth/ngx_http_upstream_queue_module/commit/d98f43f96f0b399185298e26b2c4de2ecf5da990

It works!
btw I'm changing to ngx_add_timer(&d->connect_timeout, u->conf->connect_timeout / 2);, make sure clean handler happens before 'retry'.

ngx_add_timer(&d->connect_timeout, u->conf->connect_timeout / 2);

applied


RuntimeError: Error(s) in loading state_dict for MultiModal: 	Unexpected key(s) in state_dict: "clip_model.vision_model.embeddings.position_ids".

I downloaded the CLIP, T5-ance, and OpenMatch.marvel-ance-webqa models for use in my code. But when I run this code:
t5_tokenizer, model, image_processor = load_model(args, device)
model.load_state_dict(torch.load(args.checkpoint)['model'])
I get the following error:
RuntimeError: Error(s) in loading state_dict for MultiModal:
Unexpected key(s) in state_dict: 'clip_model.vision_model.embeddings.position_ids'.
Could you help me figure out what's going wrong?"

Please make sure the relevant package versions are consistent with the ones we provide.
For example, transformers==4.22.2 and clip==1.0.
If you still have questions, please contact us.


[Enhancement]: improve ticdc cpu usage metric

The MaxProcs line use different y-axis with the cpu usage. Although the cpu usage is low, its line pass the line of MaxProcs which may give a false impression that the cpu usage is near the limit.

/label type/enhancement

/type enhancement

/assign @lidezhu


feat(execution): compute state_diff_size and add it to bouncer info

This change is

Codecov Report
Attention: 27 lines in your changes are missing coverage. Please review.

Comparison is base (0a5416b) 70.43% compared to head (12618ee) 70.29%.

Files
Patch %
Lines

...ates/native_blockifier/src/transaction_executor.rs
7.14%
26 Missing :warning:

crates/blockifier/src/fee/actual_cost.rs
93.33%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@               Coverage Diff                @@
##           main-v0.13.1    #1395      +/-   ##
================================================
- Coverage         70.43%   70.29%   -0.15%
================================================
  Files                59       59
  Lines              7713     7747      +34
  Branches           7713     7747      +34
================================================
+ Hits               5433     5446      +13
- Misses             1853     1874      +21
  Partials            427      427

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Python side: https://github.com/starkware-industries/starkware/pull/33662

crates/native_blockifier/src/transaction_executor.rs line 141 at r1 (raw file):

                    sender_address,
                    &mut transactional_state,
                )?;

Seems like there is something wrong with my code. I never use the block-level state changes.
Would we like to have the "difference"(whatever that means) between self.new_state_changes and self.block_level_state_changes?
I think I know what I get by running the command: get_new_state_changes. I am not sure what I want to send to the bouncer.
Code quote:
                self.new_state_changes = get_new_state_changes(
                    &fee_type,
                    self.block_context.clone(),
                    sender_address,
                    &mut transactional_state,
                )?;

Redesign in #1413.

replaced with #1438.


Little UX improvments

UX improvement

These are good little changes that make stuff easier for everyone! Thanks for your contribution.


Nearby crash when LatLng is null

Summary:
I am able to get this crash on some first runs. Then it gets solved.
Steps to reproduce:
Not very stable, sometimes, it happens. Ie, once I turned off wireless connection and it happened.
Add System logs:
                                 Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'double android.location.Location.getLatitude()' on a null object reference
                                                                             at fr.free.nrw.commons.location.LatLng.from(LatLng.java:45)
                                                                             at fr.free.nrw.commons.location.LocationServiceManager.getLKL(LocationServiceManager.java:109)
                                                                             at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:224)
                                                                             at android.app.Activity.dispatchRequestPermissionsResult(Activity.java:6553)
                                                                             at android.app.Activity.dispatchActivityResult(Activity.java:6432)

Hi @neslihanturan @maskaravivek  I seem to have found the issue
if (lastKL == null) {                 lastKL = locationManager.getLastKnownLocation(LocationManager.NETWORK_PROVIDER);             }             return LatLng.from(lastKL);
The function LatLng.from(lastKL) crashes when lastKL is null, we have a null check for location from GPS_PROVIDER but not for NETWORK_PROVIDER,
Can I take this up?

Yup sure it’s yours @ashishkumar468

Thanks @maskaravivek Have raised the pull request for the same


[libxml2] update to 2.10.3

Library name: libxml2
New version number: 2.10.3
Other information that may be useful (release notes, etc...)
Version 2.10.3 fixes two vulnerabilities (CVE-2022-40303 and CVE-2022-40304): https://gitlab.gnome.org/GNOME/libxml2/-/releases

the url https://gitlab.gnome.org/GNOME/libxml2/-/releases now cannot reached, can you install libxml2?

It looks like the various gnome.org sites are experiencing outages: https://status.gnome.org/. Hopefully they will be back up soon.

Can confirm, this package cannot build because gnome is down, just tried from Canada.


Update doesn't work with example

The update function doesn't work if you follow the sample text. The reason is that backbone expects the json representation of the object to get returned under a successful save, but rails serves up a blank 200 response after update.
Not sure the best way to fix it for the tutorial, but I fixed it by changing:
format.json { render head: ok }
# to
format.json { render json: @post }

in app/controllers/posts_controller.rb

Very useful.
This should be at the end of README.md

+1

I believe this was do to a rails bug which has since been fixed. Can anyone confirm that this is still an issue?


[Bug] bundle install with github-pages = 198 results in an unresolveable dependency tree

Please read the contributing guidelines and code of conduct before creating an issue.
Please prefix your issue with one of the following: [Bug] [Proposal] [Question].
Please provide as much information as possible, ideally a summary to describe the issue and / or steps to reproduce the issue.

Creating a brand new project with the following Gemfile results in an unresolveable dependency tree on bundle install:
source 'https://rubygems.org'

require 'json'
require 'open-uri'

ruby '~> 2.6.0'

gem 'github-pages', JSON.parse(open('https://pages.github.com/versions.json').read)['github-pages']
gem 'alembic-jekyll-theme'

As of 16 May 2019, github-pages's latest version is 198.
The following output is returned:
Fetching gem metadata from https://rubygems.org/............
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    github-pages (= 198) was resolved to 198, which depends on
      activesupport (= <IP_ADDRESS>)

    github-pages (= 198) was resolved to 198, which depends on
      jekyll-mentions (= 1.4.1) was resolved to 1.4.1, which depends on
        html-pipeline (~> 2.3) was resolved to 2.11.0, which depends on
          activesupport (>= 2)

Bundler could not find compatible versions for gem "jekyll-feed":
  In Gemfile:
    alembic-jekyll-theme was resolved to 1.5.3, which depends on
      jekyll-feed (~> 0.5)

    github-pages (= 198) was resolved to 198, which depends on
      jekyll-feed (= 0.11.0)

Bundler could not find compatible versions for gem "jekyll-mentions":
  In Gemfile:
    alembic-jekyll-theme was resolved to 1.5.3, which depends on
      jekyll-mentions (~> 1.2)

    github-pages (= 198) was resolved to 198, which depends on
      jekyll-mentions (= 1.4.1)

Bundler could not find compatible versions for gem "jekyll-sitemap":
  In Gemfile:
    alembic-jekyll-theme was resolved to 1.5.3, which depends on
      jekyll-sitemap (~> 0.10)

    github-pages (= 198) was resolved to 198, which depends on
      jekyll-sitemap (= 1.2.0)

Bundler could not find compatible versions for gem "jemoji":
  In Gemfile:
    alembic-jekyll-theme was resolved to 1.5.3, which depends on
      jemoji (~> 0.7)

    github-pages (= 198) was resolved to 198, which depends on
      jemoji (= 0.10.2)

Yikes! Thanks for reporting this @komidore64. How did you discover it, from just trying to do a build or some kind of automated build?

How did you discover it, from just trying to do a build or some kind of automated build?

Simply started working on a new personal site and whamo!

Sorry, but I just realised what you're trying to do. Custom theme gems aren't supported by GitHub Pages, so trying to install the gem along with the GitHub Pages gems won't be beneficial. If you're wanting to use GitHub Pages I'd recommend following the remote theme installation steps in the readme
However if you're wanting to install the gem theme in the typical fashion you'll need to skip installing the github-pages gem and it's dependencies. Just install Jekyll and the theme itself and it will come with all the dependencies you require. Hope this helps!

Ah I understand now. Thank you for the explanation. Looking at the theme docs, it read like I had choices as opposed to step 1 ("As a Jekyll theme") being incompatible with GitHub Pages.
Thanks again!


🐛 Images failing to load

Hi Team,
Describe the Bug
All images on the home screen are failing to load, causing an issue with the user experience.
To Reproduce
Steps to reproduce the behavior:

Log into SSW Rules
Go to the home screen

Expected Behavior
I expected to see all the images on the home screen load properly, providing visual content as intended.
Tasks

[ ] Investigate
[ ] Fix

Environment

Device: MacBook Pro
Browser: Chrome
OS: MacOS

Thanks!

Hey team, still having issues with this but I've tracked it down to a caching issue. I will continue to work on this and see if I can find a fix.

Hey team, added and amendment to the issue describing the current status.

maybe this isn't related to us, this might be an issue with the provider instead

and another one


feat: Add terminal completion for the Bash shell

#112 Adding Bash completions

Sorry, i forgot the screenshot that shows it working:


Online / Offline solution ?

@bobaoapae
Can we get the online / offline information of a non-registered number?
This issue has not been solved for a long time
There must be a way to get status information of a non-registered number.

window.WAPI.findOnlineStatus = function (id,done) {          Store.Presence.find(id).then(                 function (r) {                    done(r.isOnline);                 }         ); };

window.WAPI.findIdFromNumber = function (number, done) {     if (done !== undefined) {         Store.WapQuery.queryExist(number + "@c.us").then(e => {             done(WAPI._serializeNumberStatusObj(e));         });     } else {         return Store.WapQuery.queryExist(number + "@c.us");     } };

fist find id from number!

@bobaoapae
VM102:1 Uncaught TypeError: Cannot set property 'findIdFromNumber' of undefined
at :1:30

load WAPI.js first...

I can only get information from the numbers I have contacted before
I want to receive information from an unregistered number that has not been contacted before
@bobaoapae

I use here with unregistered number... :/

@bobaoapae
command line
how to use your function
can you write example code

Hi!
You can try Chat-API.

100% Android Environment
Latest WA2.0 Protocol
Simple to setup
Detailed Documentation
Example Scripts are ready to use
Check it now on https://chat-api.net
Thanks

Adding these lines before the code
var idUser = new window.Store.UserConstructor(id);
Store.Chat.find(idUser);

From #398 and #383 @bobaoapae
You can send messages and check if an unregistered number is online.

@ecjN00B I am stuck with my school project. A small thing regarding this issue.Could you please help me ? https://github.com/mukulhase/WebWhatsapp-Wrapper/issues/512#issuecomment-441486304

@bobaoapae could you please help me ? https://github.com/mukulhase/WebWhatsapp-Wrapper/issues/512#issuecomment-441486304

can i check if a number is online
however it isnot on  my contact list ?

all solutions does not work

any updates on this issue? i cannot seen to get presence updates of any numbers who i havent interacted with. there has to be some workaround

Does any one know how the countless apps on the playstore do it? This for eg.
https://play.google.com/store/apps/details?id=com.wtrack_android
Looking at this there must be some way out without sending the user a message


Docs: Add "Validation messages" section

What
Need to add the section regarding Validation messages to the documentation.
Why
Because it's missing.

Added under e4cfcab757d1d855e968bd4ca5300d099830040a. Closing.


Consider a version without jQuery

Strange as it may sound, nanoScroller is the only plugin left in our project which still has a reference to jQuery. And we are keeping it this way since nanoScroller is the most adequate scrolling plugin I have encountered for the last years.
It would be really cool if you had a version without jQuery dependency as well. What do you think?

+100

+1000

+10000

I see ten thousand - one, I see ten thousand - two, I see ten thousaaaand...

+100000

This would be a cool idea. I think it's possible. But I haven't been able
to participate in the recent development of nanoscroller due to my day job.
:+1: from me as well hah
On Tue, Sep 8, 2015 at 12:56 AM, Aedaeum<EMAIL_ADDRESS>wrote:

+100000
—
Reply to this email directly or view it on GitHub
https://github.com/jamesflorentino/nanoScrollerJS/issues/315#issuecomment-138340246
.

--
James O. Florentino
Full-stack designer and engineer
http://blog.jamesflorentino.com

(y)

:+1:

:+1:
I just added jQuery on our website to embed this one. :)


return correct exit code - wmagent version of #7996

fix return code handling from subprocess

#7996

 Fix #8005 - return correct exit code


Implementing streaming market data

Hi,
Thank you for all the work you did on this API.
I've been following the YouTube videos, it seems like the API does not provide support for streaming data.
Could you explain how one might integrate streaming data with the existing functionality?
It would be nice to have a stream of market data, and for those using technical indicators, a bit of historical data to warm up the indicators that require more than 1 pricing data point.
Thank you!

Heres how I have it implemented. Its a little bit more complicated than simply going to the endpoint, you need to use a websocket (and SSL) to stream data, which also requires that you use a little bit of asyncio. Let me know if you have any questions. The print messages are where my logic would go
async def stream_data(websocket, path):
    try:
        async with connect('wss://localhost:5000/v1/api/ws', ssl=context) as ibsock:
            while True:
                s = asyncio.wait_for(websocket.recv(), timeout=3)
                print(await s)
                async for message in ibsock:
                    print(message)
                    continue