Exception using YCSB with Elasticsearch (ver. 5.x.x) binding in remote mode

Hello, i have a problem using the Elasticsearch binding in remote mode. I tried the following command with the Elasticsearch versions 5.5.1, 5.5.2 and 6.0.0 beta and the YCSB version 0.12.0 as well as a snapshot from the current master and the risdenk fork (28.08.17):
./bin/ycsb.sh load elasticsearch -P workloads/workloada -p es.remote=true -p path.home=/usr/share/elasticsearch -s
I configured the elasticsearch.yml with the following line:
cluster.name: es.ycsb.cluster
It works perfectly with Elasticsearch version 2.2.3 according to the examples in the elasticsearch binding folder as well as the answer in the following issue from jasontedor.
On the described versions i get the following error message:
YCSB Client 0.12.0
Command line: -db com.yahoo.ycsb.db.ElasticsearchClient -P workloads/workloada -p es.remote=true -p path.home=/usr/share/elasticsearch -s -load
Loading workload...
Starting test.
2017-08-28 14:43:20:938 0 sec: 0 operations; est completion in 0 seconds
Elasticsearch starting node = es.ycsb.cluster
Elasticsearch node path.home = /usr/share/elasticsearch
Elasticsearch Remote Mode = true
Elasticsearch Remote Hosts = localhost:9300
Aug 28, 2017 2:43:21 PM org.elasticsearch.plugins.PluginsService <init>
INFORMATION: [Chen Lu] modules [], plugins [], sites []
Aug 28, 2017 2:43:21 PM org.elasticsearch.client.transport.TransportClientNodesService$SniffNodesSampler$1$1 handleException
INFORMATION: [Chen Lu] failed to get local cluster state for {#transport#-1}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}, disconnecting...
NodeDisconnectedException[[][<IP_ADDRESS>:9300][cluster:monitor/state] disconnected]

Exception in thread "Thread-3" NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}]]
	at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)
	at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)
	at org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
	at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:288)
	at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:359)
	at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:348)
	at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.execute(AbstractClient.java:1221)
	at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.exists(AbstractClient.java:1241)
	at com.yahoo.ycsb.db.ElasticsearchClient.init(ElasticsearchClient.java:146)
	at com.yahoo.ycsb.DBWrapper.init(DBWrapper.java:99)
	at com.yahoo.ycsb.ClientThread.run(Client.java:418)
	at java.lang.Thread.run(Thread.java:745)
2017-08-28 14:43:21:806 0 sec: 0 operations; est completion in<PHONE_NUMBER>67300 days 15 hours
[OVERALL], RunTime(ms), 898.0
[OVERALL], Throughput(ops/sec), 0.0
[TOTAL_GCS_PS_Scavenge], Count, 1.0
[TOTAL_GC_TIME_PS_Scavenge], Time(ms), 68.0
[TOTAL_GC_TIME_%_PS_Scavenge], Time(%), 7.57238307349666
[TOTAL_GCS_PS_MarkSweep], Count, 0.0
[TOTAL_GC_TIME_PS_MarkSweep], Time(ms), 0.0
[TOTAL_GC_TIME_%_PS_MarkSweep], Time(%), 0.0
[TOTAL_GCs], Count, 1.0
[TOTAL_GC_TIME], Time(ms), 68.0
[TOTAL_GC_TIME_%], Time(%), 7.57238307349666

I also wanted to try the elasticsearch5 binding like described in this README commited from the risdenk fork, but it seems not to be recognized from the ycsb script, since it is not implemented as an option yet.
ycsb: error: argument database: invalid choice: 'elasticsearch5' (choose from 'accumulo', 'aerospike', 'arangodb', 'asynchbase', 'basic', 'cassandra-cql', 'cassandra2-cql', 'couchbase', 'couchbase2', 'dynamodb', 'elasticsearch', 'geode', 'googlebigtable', 'googledatastore', 'hbase094', 'hbase098', 'hbase10', 'hypertable', 'infinispan', 'infinispan-cs', 'jdbc', 'kudu', 'mapkeeper', 'memcached', 'mongodb', 'mongodb-async', 'nosqldb', 'orientdb', 'rados', 'redis', 'rest', 'riak', 's3', 'solr', 'solr6', 'tarantool', 'voldemort')

I really would be glad for some help regarding this issue. I already looked up the answers to the issues #856 , #796 but setting client.transport.sniff=false didn't work also (i'm not using docker). Embedded mode works fine in all versions that i've tested.
If you need more details just ask me!

To use the elasticsearch5 flag, add the following line in bin/yscb, in dictionary DATABASES:
"elasticsearch5": "com.yahoo.ycsb.db.elasticsearch5.ElasticsearchClient",

Thank you very much @levaphenyl for the instruction! It is actually working now with the elasticsearch5 flag and Elasticsearch version 5.5.1 as well as the new 5.5.2 (it is not working with 6.0.0 but its just a beta so we shouldn't really care). It tried it on a local machine as well as with a remote call to another server with a running Elasticsearch instance, both works, so the issue can be closed from my side!


MediaRecorder: support more mimeTypes than audio/wav

First #507 should be implemented.
Then we can switch out hound for the encoding and use symphonia

Encoding is not provided by Symphonia so we either need to find a new general purpose encoder or use dedicated crates per type


Validation of default and maximum partitions for environment

What happened?
I want to create new environment.
I set:
Default partitions = 2
Maximum Partitions = 12
Validation failed with information that default partitions should be less than maximum.
It looks like the validation doesn't compare numeric values but strings.
What did you expect to happen?
Validation should pass.
What else do we need to know?
Klaw 2.9.0

Hey @maciejmaciejko-gid thank you for this I will check this out today.

@maciejmaciejko-gid A PR is now open to address this issue thank you for reporting it


Use laxar-developer-tools-content as submodule

The embedded content application has a own repository now.

Implemented on master (v2.3.0).


Apps using IPFS

Just some apps I've found around the interwebz that use IPFS. I'll try to keep this list updated in order of activity. Make a comment to be added and I'll comment when I find something. Feel free to subscribe to stay up to date.

git-ipfs-rehost: A script to rehost your git repos in ipfs.
Author: Jeromy Johnson

IPFS playback support in Playback video player. This allows casting a video in IPFS to a Chromecast.
Patch Author: Juan Benet

ipfs-firefox-addon: A Firefox addon for redirecting gateway.ipfs.io links to your local gateway.
Author: Marcin Rataj

IPFS Linux Init Daemon: For anyone running ipfs on a server somewhere (like an rpi in your living room), I've created a script that will install the ipfs daemon as a Linux system daemon. No more screen processes! :D
Author: Dylan Powers

IPFS Gateway Redirect: A Chrome extension that allows you to access gateway.ipfs.io urls the way they were meant: from your locally running ipfs daemon.
Author: Dylan Powers

ipfs-userscript: Browser userscript for redirecting gateway.ipfs.io links to your local gateway. This should work on any browser that hasn’t had an extension written for it yet and has support for userscripts.
Author: loadletter

IPFS Share: An IPFS backed Pastebin / Image Host / File Sharing application.
Author: Varun Ramesh

IPFS Event Drop: An app that allows for improved visualization of ipfs events.
Author: Travis Person

Cohort: A golang app to preset a threejs interface and get all of its assets out of IPFS.
Author: zignig

IPFS playback support in Playback video player. This allows casting a video on IPFS to a Chromecast.
Patch Author: Juan Benet

git-ipfs-rehost: A script to rehost your git repos in ipfs.
Author: Jeromy Johnson

This list is pretty sweet, can we bring it to https://github.com/ipfs/awesome-ipfs and make that the location for all of these links?
Plus, would love if the list could be embed on ipfs.io. @RichardLitt ? :)

@diasdavid I think moving all of these links over would be a good thing to do. I'll add that to my things to do next sprint. Embedding it also sounds good.

Closing as ipfs/awesome-ipfs satisfies this need.

please write a simple GUI to manage files. and then I added files and delete them can't anymore. many simply unrealistic to use this because of the difficulties


Docker: Java heap space

Hi,
I'm trying to install Concourse via Docker.
But i'm getting this error in console after install:

Exception in thread "Client Worker 0" java.lang.OutOfMemoryError: Java heap space
at org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.java:379)
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:230)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:27)
at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Hi @mehrdd,
Thanks for reporting this issue. What command are you using to run Concourse via Docker?  After the container starts, are you running any additional commands?
Thanks in advance for the info. We'll get you up and running soon once we're able to diagnose things further.
Best,
Jeff

Hi Jeff,
I'm just using normal commands like:
docker run -p 1717:1717 --name concourse cinchapi/concourse

After installing my Concourse container, i opened my browser and entered http://localhost:1717
I'm trying to use Concourse with node.js for a very dynamic-query-based SaaS project like Zoho Creator
Is Concourse a good fit for such project?
Thank you Jeff,
Best regards,
Mehrdad


[Fixes #7425] Session Locator | Isolation Levels not respected in Sites.config

Hi @joshnogales, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

WE'll merge it tomorrow, and also copy this change to 1.10.x

@sebastienros Part of the reason for the mixup that caused this issue, was that TransactionManager was refactored out of SessionLocator code.  When this was done, the implementation of TransactionManager was left in SessionLocator.cs even though there is TransactionManager.cs file that holds ITransactionManager and some helper.
If there is interest, I have already cleaned TransactionManger back into TransactionManger.cs and can submit a pull request of it.


vue/max-len not work

extends
<EMAIL_ADDRESS>.eslintrc.js
'vue/max-len': [
  'warn',
  {
    code: 140,
    template: 200,
    tabWidth: 2,
    ignoreTemplateLiterals: true,
    ignoreStrings: true,
    ignoreUrls: true,
    ignoreComments: true,
    ignoreHTMLAttributeValues: true,
    ignoreHTMLTextContents: true
  }
]

package-lock.json
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
formater alway follow max-len default code: 80,
not my setting vue/max-len code: 140 and template: 200.

@UnRealSKY Thank you for creating an issue. I'll get to trying to reproduce it as soon as I can.

@UnRealSKY Using the example project here: https://github.com/idahogurl/vs-code-prettier-eslint/tree/master/examples/javascript-vue
I was able to get vue/max-len to work somewhat where it formatted the line to 100 characters. I used the Prettier-ESLint CLI and got the same result. There is a defect in the Vue ESLint plugin (not mine) that making the ESLint settings not apply.
I ran eslint *.vue and received the following:

I used the ESLint configuration you provided but yet it says the max length is 100 not 140.


receive: Unknown Symbol on compaction does not allow head to be compacted.

Introduced by: https://github.com/thanos-io/thanos/pull/2867
Lesson to us @sylr to not update Prometheus that fast (:
Details: https://github.com/prometheus/prometheus/issues/7373
This is only on master after above PR.

Reverted on Prom master https://github.com/prometheus/prometheus/pull/7556

Potential fix: https://github.com/prometheus/prometheus/pull/7560
cc @pracucci @codesome


unable to access object.errors

Hi!
Thanks for this helpful gem which helped me a lot to quickly create a REST-based model.
With basic requests working I now wanted to carry on with error handling. I wanted to use active-rest-client's validation capability, when I got stuck with not being able to access the errors hashmap.
In short, this didn't work:
class MyRestClass < ActiveRestClient::Base
  validates :myAttribute, presence: true
[...]
end

> restobject = MyRestClass.new()
> restobject.valid?
> restobject.errors
 => nil

I wondered why, because both valid? and errors are defined in validation.rb, but somehow I wasn't able to use the errors method. It wasn't in the list of restobject.methods either, so I started digging and found that the errors method seems to get undefined in base.rb:L14. When I removed errors from the array, all started working as expected.
I'm no ruby/rails expert, but to me it looks like a bug. Or is it me doing something wrong?

The only reason may be it's quite common for REST responses to contain an error key.  Maybe the method should be _errors so it doesn't conflict with an errors key from the response?  Or maybe have #errors also work, if there was no such key.  I'll have a look in to this.

If you can test the latest github version, see if that works for you?  If so, I'll release it as a new version as it's interface compatible.

Thanks for the ultra quick response!

Maybe the method should be _errors so it doesn't conflict with an errors key from the response?

I don't think so, since "errors" is the error hash name commonly used in ActiveRecord. If the response should contain an errors key, I think you could rewrite it with a proxy.
The latest github version works for me, it's exactly the same change as what I did locally.
But I'm wondering if I'm really the only one trying to read the errors from validations?! Cause from the commit history it looks like this hasn't been working for a longer time...
(And perhaps the validation spec tests should be modified to not use a struct but a real ActiveRestClient::Base object?)
Anyways, it's working now, so I'm going to close this issue.

Oops, I didn't see that you renamed the errors method to _errors. This basically makes the errors thing work, but I can't use the ActiveRestClient objects in my views the same way as ActiveRecord objects. I have a helper function that checks for object.errors.any? which now doesn't work for ActiveRestClient objects anymore.
Don't you think that your model should be as close as possible to ActiveRecord?

Well, don't bother. I just found that I can't use my helper function anyways, as I'm using ActiveRecord::Errors specific calls, which is the errors type for ActiveRecord objects.

We aim for it to be as close as possible, but there are some differences as we're potentially accessing a wider variety of "databases" ;-)
No to worry, sorry the quick response didn't help you in the end.

No to worry, sorry the quick response didn't help you in the end.

It did help me: By calling _errors I'm now able to access the validation errors at all, which I wasn't before. Or was I?

No, you're right, I think it had been broken a while.  I guess no-one was using the validations :-)


Deploy final versions of fivethirtyeight and parlgov datasets (with view pagination)

Final versions should be deployed using the first released version of datasette.

The fivethirtyeight dataset:
datasette publish now --name fivethirtyeight --metadata metadata.json fivethirtyeight.db
now alias https://fivethirtyeight-jyqfudvjli.now.sh fivethirtyeight.datasettes.com

And palrgov:
datasette publish now parlgov.db --name=parlgov --metadata=parlgov.json
now alias https://parlgov-hqvxuhmbyh.now.sh parlgov.datasettes.com

Parlgov was throwing errors on one of the views, which takes longer than 1000ms to execute - so I added the ability to customize the time limit in https://github.com/simonw/datasette/commit/1e698787a4dd6df0432021a6814c446c8b69bba2
datasette publish now parlgov.db --metadata parlgov.json --name parlgov --extra-options="--sql_time_limit_ms=3500"
now alias https://parlgov-nvkcowlixq.now.sh parlgov.datasettes.com

https://parlgov.datasettes.com/parlgov-25f9855/view_cabinet now returns in just over 2.5s


Table Resizing Lags behind Cursor on Drag Start When No Explicit WidthSet

Describe the bug
When an explicit width is not set via defaultColumn.size or when the content of a cell becomes larger than defaultColumn.size the resizer lags behind the cursor on the initial column resize. This only happens when using table element, when using div (relative or absolute) it seems to work fine.
Your minimal, reproducible example
Demo
Steps to reproduce

Using the link above, go to the firstName column of the <table /> containing a cell with the text tannertannertannertanner
Try to resize the column using the resizer

Expected behavior
Resizing should happen at the same pace as mouse cursor move
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
ALL
react-table version
v8.9.10
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Hey @sslgeorge were you able to fix this? I'm running into this issue currently


[test] Add indexing regression test case for @dynamicMemberLookup on a protocol.

Adds a regression test for an already-fixed crasher.
Resolves rdar://problem/63558609

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 1f01103cc1500a4ea50255922be9f1675687d385

Failure seems unrelated:
15:29:02 Failing Tests (1):
15:29:02     Swift(macosx-x86_64) :: Python/python_lint.swift

@swift-ci please test OS X Platform

@swift-ci please test Windows Platform


ticks stay inside the domain

fixes #162
partial revert of f5883f640bec70926823d733fd68d1036d73d3f2

My preference is #164.

yes—superseded by #164.


Load default .ini config

Is your feature request related to a problem? Please describe.
You can't load an initial configuration file without fill the build_config method in your App.
In my case, i'm obliged to add fake data to the config, before my config file can be taken in account like this :
def build_config(self, config):
    config.setdefaults('section1', {
        'key1': 'value1',
        'key2': '42'
    })

Describe the solution you'd like
I would like to avoid to fill the build_config method, if you have a default config file, or to load two times the same file.
Describe alternatives you've considered
I think, it can be resolved by remove the lines 795 and 796 of kivy/app.py, in method load_config
 if len(config.sections()) == 0:
        return

I don't know if it is very necessary to return. Why not continuous and load the app config if founded.

I don't understand what you're trying to do. Are you trying to use Kivy's config file for your own config? If so, you should create and use python's config parser instead. Kivy's config parser and config file is mostly for managing kivy config.
Kivy's config file is properly initialized before reading it so I don't see how you could have this issue.

I don't understand what you're trying to do. Are you trying to use Kivy's config file for your own config? If so, you should create and use python's config parser instead. Kivy's config parser and config file is mostly for managing kivy config.
Kivy's config file is properly initialized before reading it so I don't see how you could have this issue.

I talking about app level config : Use the configuration file
You can't load an exiting config file, without create it before in build_config.
Kivy "know" the default path for app level config (ei: app_name.ini). You can't just create a .ini file at that path, so that it is taken in account at startup like for the default .kv file

I see what you mean. I didn't know that config stuff existed.
What if len(config.sections()) == 0: is trying to do is check if the user is using the app config and if so it creates the file. However, as you indicate, that is a bad way of detecting whether the user wants to use the app config. A better way would have been to have build_config explicitly return True/False to indicate if the app config should be created.
However, I'm not sure we can change this given the backward compat issues this would cause. But we should consider changing it I guess.
However, for now, I'd suggest that you don't make use of this default config filename. Instead you can get the path with get_application_config, but then change the filename to something else that won't clash with the one kivy is attempting to open.

Ha. I think it's just the documentation that's a little unclear; it seems you can populate the default values just fine from an existing .ini like so:
  def build_config(self, config):
    config.read("myapp.ini")

This of course depends on having a complete and correctly formatted .ini file, so you may want to start off with setting the defaults anyway, and remove that block later in the development cycle.


PlaceholderAPI expansion error

Paper 1.13.2 build 652
PlaceholderAPI v2.10.4
LuckPerms 4.4.1
This occurs on server start, started to happen after updating LuckPerms expansion with papi ecloud command.
https://hastebin.com/dexenogafi.sql

So? I don't really see what that image should tell me

It says plain as day "Update for LuckPerms API 5" meaning it WON'T work for LP v4.
You would also know that if you would join the LP Discord and checked the #luckperms-v5 channel for information.
The tl;dr is that the API of LP got rewritten which is a breaking change. Your solutions are either:

Not using latest version of the expansion as it only works with LuckPerms v5
Update LuckPerms to v5. This may break plugins that use the old v4 API and a workaround is to use the legacy-api extension of LP.

Thanks


Extreme naming / description [FEATURE]

Is your feature request related to a problem? Please describe.
I would like to be able to adjust the name / description of an Extreme using the IOM xml definition. Currently this is not possible and the default "E 1", "E 2" etc. is used.
Describe the solution you'd like
Add support for a  tag:
  <Extremes>
    <CheckSectionExtreme xsi:type="StandardCheckSectionExtreme">
      <Fundamental>...</Fundamental>
      <Description>not E 1</Description>
    </CheckSectionExtreme>
  </Extremes>

In the GUI it concerns these fields:

It would give us a big leap forward in using IdeaStatica as part of our digital production line. Without it, we can't link the results to the report/FEM model, which is a huge miss.
Thanks in advance!

Hi @johan-tuls, this is in development and will be available in the next release of IDEA StatiCa. We have added a 'Description' parameter in IOM which can be used to set this property.

Thanks for the update. We will check it out. Hopefully it is available through the XML option as well. This wasn't yet the case for the Design Member naming, but this adjustment would help a lot. Thanks for the support

Hi @johan-tuls, I am pretty sure it is available for the Design Member. You may be using an old version of the IOM implementation. Or can you please show me in more detail what you mean? Currently everything in RCS creation goes through IOM.xml so it cannot be populated without this.

and @johan-tuls just to be sure this is the property that needs to be set:

Hi @nathanlukeIDEA , sorry for the late reply. It worked! :-) So we will implement this, thanks for the help and support
It will be much more readable than our previous version where the name was missing ;-)

perfect! great.


the mnist dataset in cnn_mnist.py

I can't see how to build the dataset 'mnist' as in the tutorials below:

def main(unused_argv):
  # Load training and eval data
  mnist = tf.contrib.learn.datasets.load_dataset("mnist")
  train_data = mnist.train.images # Returns np.array
  train_labels = np.asarray(mnist.train.labels, dtype=np.int32)
  eval_data = mnist.test.images # Returns np.array
  eval_labels = np.asarray(mnist.test.labels, dtype=np.int32)

My codes don't work of course. And I have downloaded the following dataset in the  MNIST. So what can I do?

Thank you a lot.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Have I written custom code: N
OS Platform and Distribution:
TensorFlow installed from: Anaconda
TensorFlow version: 1.6.0
Bazel version
CUDA/cuDNN version
GPU model and memory: N
Exact command to reproduce

Hi WendyMin,
I think you are confused between MNIST dataset provided by the TF bundle and the one which you have downloaded from http://yann.lecun.com/exdb/mnist/.
TF MNIST Data are parsed and converted into arrays of image pixels, whereas http://yann.lecun.com/exdb/mnist/ has files into IDX format which is fairly simple format to extract your image pixels for each files.
Please refer "THE IDX FILE FORMAT" on same page http://yann.lecun.com/exdb/mnist/  to understand how you can easily convert downloaded IDX files into your array/tfRecord which TF can accept as input.
You may want to refer https://www.tensorflow.org/programmers_guide/datasets
Thanks,
Jinay

Nagging Assignee @skye: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


getSubscriptions retrun error : Error not specified with Amazon Live App Testing.

Hello
I have implemented react-native-iap (version:12.10.5)
I am trying to get subscription detail by using getSubscription() method. but I am getting below error  in live app testing.
Error: "Error not specified"
But when I am testing in sandbox (AppTester) it works fine.
Here is my code to get a subscription:
    getSubscriptions({         skus: ['App SKU'],     })    .then(async res => {           console.log('Amazon subscription----', res);     })    .catch(error => {         console.log('error in IAP-----', error);         stopLoader();    });
Please help me to fix this issue.

@FastAlien  Thank you. Its works for me.

@FastAlien  I have same problem for Apple TV. please help me.
I have test with emulator and Mi Fire stick. but when I tried to getSubscription it return same error "Error not specified"
here is my code:
getSubscriptions({ skus: ['App SKU'], }) .then(async res =>         { console.log('Androd subscription----', res);  }).catch(error =>         { console.log('error in IAP-----', error); stopLoader();  });


Rename init method in BackfillHiveSource

Simple rename of initialize method to initBackfillHiveSource since the name conflicts with method in super class

Self merging trivial refactor.


fix: inject configured objectMapper into kafka producer

I now considered 3 possible solutions and I still think that my solution in this PR is the 'least intrusive' option:

Solution 1: Configure a DefaultKafkaProducerFactoryCustomizer with a JsonSerializer and the correct ObjectMapper
Configuring the Serializer an a ProducerFactory level applies it to all producers that are created with that factory, so it must be 'un-configured' for all producers that should use a different serializer, e.g. the DLT producer. It also needs to be unconfigured whenever a user of the library creates its own kafkaTemplate und wants to use a different serializer.

Solution 2: Configuring the default kafkaTemplate with a JsonSerializer and the correct ObjectMapper
Defines the serializer only for this producer, which is intended as a Json producer anyway. But it is then fixed to that, if a dev wants to use a different serializer he needs to create a new Bean and can’t simply configure the spring.kafka.producer.value-serializer property.

Solution 3: Configure the ObjectMapper that is used by the default JsonSerializer
Unfortunately not possible, creating a serializer implicitly (e.g. through the producer.properties) creates a new ObjectMapper from scratch without the needed configuration. See https://github.com/spring-projects/spring-kafka/blob/a455eed0843597a9fe54e04895c0c19bd98395fd/spring-kafka/src/main/java/org/springframework/kafka/support/serializer/JsonSerializer.java#L84

Therefore I propose we go with the current solution, solution 2.


make all tests pass within es5 environment

All code for this library is written in es5, except for these two tests. So they fail when run in es5 environment. This PR fixes that.

This was fixed as part of #128, although I think I want to get all the environments switched over to ES2015+ soon.  In any case, thanks for this and your other PRs.


Policy assignment in Azure to list out registered and notregistered services as per our policy

I have some requirment to list registered and not registered services from my policy assignment.
For some of the services, let us say, Microsoft.Sql services we have whitelisted most of the services and did not whitelist few services.  Get-Azresourceprovider command treats all the whitelisted services as "NotRegistered" in the command output.  But most of the services are whitelisted and hence registered.
I need some help to get only the output which are not registered and registered.  Looks like Get-azresourceprovider command treats one service as Notregistered if one of the component is not whitelisted.

@Kannadasa
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

I am using Get-AzpolicyAssignment command to list out all the resources we allowed as part of the policy.  We would also like to list out the resources which we did not whitelist in our policy.
THis is our requirment.

https://user-images.githubusercontent.com/17334473/214600400-dd8b4561-50e8-4824-9dad-f1418dd0f712.png.
If you look into the screenshot, there are services in the dropdown with checkbox to the left.  I am able to list out the services which are checked because we allowed these services in the policy.  But I am unable to list out the services which are unchecked because we did not whitelist these services in our policy.
Is there anyway to list out only the Unchecked services from this drop down menu so we can allow them in our policy.
This is our requirement

@Kannadasa
Thank you for providing the details. We need to exact a Microsoft document that you referred to us via a share link after only assigning it to the relevant service team.

Thanks Ramanathan,
Actually i found out something else... THere is something called Azure Resource Explorer in azure portal which has all the providers from Microsoft and this is exactly same as in Policy assignment windows dropdown list (where we see all the services in the Azure Resource Explorer).  Is there any way to convert the list from Resource Provider to any text files?  This will solve our problem.  We already have a JSON file which has the white listed services and the list from Azure Resource Provider will give us all the services from Microsoft.  DIfference between these two files will give us the services to be whitelisted.
So listing out all the providers/services from Azure REsource Explorer in a text file using some REST API calls will be very crucial, any help here will be highly appreciated

@Kannadasa
Thanks for your response!!
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1


Mirror required build images in arointsvc.azurecr.io

Which issue this PR addresses:

Fixes https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/13904032/
What this PR does / why we need it:
We're no longer allowed to reference Red Hat's container registry directly in our codebase, so this sets up mirroring so that we can pull from an ACR instead.

Mirrors the required Red Hat images used for building to arointsvc.azurecr.io
Updates Dockerfiles to reflect the change
Updates documentation to reflect the change

Test plan for issue:

Run INT - Mirror images pipeline using this PR (currently blocked by expired client secrets)
Run e2e to confirm that the existing pipelines can build ARO from arointsvc.azurecr.io
Associated portal/muo tests (if neccesary)

Is there any documentation that needs to be updated for this PR?
Documentation has been updated - let me know if I missed anything.

/azp run all

/azp run ci

/azp run ci

Our mirroring pipelines (both ev2 and azp) are still failing with authentication issues, but @bennerv manually pushed the required images to our arointsvc ACR and CI/e2e is passing with the changes now and the scanner looks happy.


feat: translation linter needs to check numerus format

Originally posted by @patricklodder in https://github.com/dogecoin/dogecoin/issues/3439#issuecomment-1962778297
There's an issue that the linter doesn't catch with numerus: when we delete the numerus form in favor of a single form, the compilation breaks.
In the linter (contrib/devtools/check-translations.py) we should add a check that if there is a numerus="yes" attribute on the <message> element, that its child <translation> element ONLY contains <numerusform> elements, and no text node.

Would it be done around here like below?
if translation_node.text is not None:
    print(f'Numerus message contains text {translation_node.text}, needs to be fixed.')
    have_errors = True


Delphi example doesn't work

when I run Delphi example it' compile ok but application does not work (message :)

Hi, this could be an optimizer issue with Delphi Community Edition (10.4 Update 2) , try to building the example (Shift - F9) instead of compiling and run again see if the problem is solved.
Cheers
H

I'm using Delphi 11.1 . tried to rebuild and I have the same issue .

There could be many reasons causing this issue, i don't know what environment you are using but here are some steps to check:

The examples were tested on onnxruntime version 1.13.1, in case you are using Windows x64, download the library and place the dll's next to the output executable, you can find the library here:
https://github.com/microsoft/onnxruntime/releases/download/v1.13.1/onnxruntime-win-x64-1.13.1.zip
the example runs on Windows 11 , x64 bit so make sure the onnx libraries and the example are build with 64 bit otherwise use the onnxruntime  relevant library
the Delphi example uses an FMX project make sure your Delphi FMX libraries are installed or you can refere to the Lazarus project to build in VCL
always make sure to build the project before compiling to ensure all unit libraries were updated
Cheers
H

working fine . thank you
On Sun, Mar 5, 2023 at 2:25 PM Haitham Shatti @.***>
wrote:

There could be many reasons causing this issue, i don't know what
environment you are using but here are some steps to check:

The examples were tested on onnxruntime version 1.13.1, in case you
are using Windows x64, download the library and place the dll's next to the
output executable, you can find the library here:

https://github.com/microsoft/onnxruntime/releases/download/v1.13.1/onnxruntime-win-x64-1.13.1.zip

the example runs on Windows 11 , x64 bit so make sure the onnx
libraries and the example are build with 64 bit otherwise use the
onnxruntime relevant library
the Delphi example uses an FMX project make sure your Delphi FMX
libraries are installed or you can refere to the Lazarus project to build
in VCL
always make sure to build the project before compiling to ensure all
unit libraries were updated
Cheers
H

—
Reply to this email directly, view it on GitHub
https://github.com/hshatti/TONNXRuntime/issues/1#issuecomment-1455077235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL6S27753PLKG5H7BQ47CDLW2SA5BANCNFSM6AAAAAAVN3YKSA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Clarify send/receive routes functionality

We probably just need to document the behavior discussed here: https://github.com/interledger-rs/interledger-rs/issues/277

Relates to #533


feat: port MeasureTheory.Constructions.Polish

[x] depends on: #4018

This PR/issue depends on:

leanprover-community/mathlib4#4018
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#4018
By Dependent Issues (🤖). Happy coding!

bors merge

bors merge

bors r-
bors d+

bors merge

bors merge


theme: remove .Scratch with .Store

Since Hugo 0.138 the first is an alias to the later. Better replace the call before getting deprecation warnings.

That was to early: Old Hugo versions don't have .Store in all places they have .Scratch


icon display error

Issue Type: Feature Request
icon display error when I import file
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

What is the error?

I mean the file icon should show like this when importing.
But it was fixed in the latest update.


Custom ExceptionHandler

Is it possible to overwrite the exception handler? If I would like to add custom syntax for the errors responses. Would be awesome if we could handle the entire exception handler outside of this package and use the default one that comes with the package out of the box.
Dingo\Api\Routing\Router::__construct() must be an instance of Dingo\Api\Exception\Handler, instance of App\Exceptions\Handler given,

I'm not sure what you're trying to do, but maybe this helps.
In your boot() function, you can do something like:
$exception = app('api.exception');
$exception->register(function(\Illuminate\Database\Eloquent\ModelNotFoundException $e) {
	return Response::make(
		['error' => 'Resource not found'],
		404);
});

which will then give you, for that exception:
{"error":"Resource not found"}

I want to map all thrown exceptions in this packages to my Laravel exception handler class instead of using the exception handler in this package. Since I want custom syntax for my API responses.

Sorry, don't know how to do that.

@camilstaps Okay, thanks anyway.

Catch all the exceptions then. Same method as above except use the general
Exception class to capture them all.
On Tue, 19 May 2015 23:54 Vincent Klaiber<EMAIL_ADDRESS>wrote:

@camilstaps https://github.com/camilstaps Okay, thanks anyway.
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-103504627.

@jasonlewis that's what I ended up doing in the end. Thanks!

@jasonlewis Do you have any example?

Well... you could rebind the Dingo exception handler as well. But what I was suggesting is to type-hint the standard Exception class in the Dingo exception handler and then pass the exception on to your applications handler.
app('api.exception')->register(function (Exception $exception) {
    return app('App\Exceptions\Handler')->render($excepton);
});

I tried to rebind the Dingo exception handler first but since it is typehinted within the Router class I didn't get it to work. I'll try the snippet you've provided. Thanks!

You'd need to extend to rebind it. The type hint in the router should still
work through inheritance.
On Wed, 27 May 2015 16:03 Vincent Klaiber<EMAIL_ADDRESS>wrote:

I tried to rebind the Dingo exception handler first but since it is
typehinted within the Router class I didn't get it to work. I'll try the
snippet you've provided. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-105767837.

Aah okay, didn't think about extending the handler form this package. I'll try it out. Thanks!

I might do up an interface for this though as that'll be easier in the long
run for folks that do what finer control over how exceptions are handled.
For some this might be a better option then using a catch all handler like
I demonstrated above where you type hint that default Exception class.
Would that better suit your needs? You'd then need to implement the handle
method on your class and in there you could do any customizing. Note that
you wouldn't have any of the default generic error responses that the
default handler implements.
On Wed, 27 May 2015 16:12 Vincent Klaiber<EMAIL_ADDRESS>wrote:

Aah okay, didn't think about extending the handler form this package. I'll
try it out. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-105769421.

Yeah, thats sound like a great idea! I think it would make this package even more extendable for the users that want to have their custom setup. Though, the current setup is great out of the box.
I'm currently using https://github.com/GrahamCampbell/Laravel-Exceptions package which just recently got support for custom displayers. I've created custom JsonDisplayer for all HTTP responses and for all API validation errors that are thrown. The main reason behind it is because I've chosen to follow the JSON-API standards.
Maybe the easiest way to handle this is to add a option in the configuration files to just turn of the exception handler included in this package? Then users could do whatever they want with all errors thrown. What do you think?

Hm... If I do go that route I probably won't add it to the configuration
file to keep it from becoming bloated with things that most people won't
touch. How about a method on the handler that let's you disable it so all
exceptions are simply thrown back out to be handled by the user?
On Wed, 27 May 2015 16:20 Vincent Klaiber<EMAIL_ADDRESS>wrote:

Yeah, thats sound like a great idea! I think it would make this package
even more extendable for the users that want to have their custom setup.
Though, the current setup is great out of the box.
I'm currently using https://github.com/GrahamCampbell/Laravel-Exceptions
package which just recently got support for custom displayers. I've created
custom JsonDisplayer for all HTTP responses and for all API validation
errors that are thrown. The main reason behind it is because I've chosen to
follow the JSON-API standards.
Maybe the easiest way to handle this is to add a option in the
configuration files to just turn of the exception handler included in this
package? Then users could do whatever they want with all errors thrown.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-105772268.

Thats sound good. Maybe you could add it to the configuration but don't add it by default? Calling the config() but return true if the config doesn't exist? Do you've how would it look code-wise with the method?

The way I'm thinking...
app('api.exception')->disable()
On Wed, 27 May 2015 16:48 Vincent Klaiber<EMAIL_ADDRESS>wrote:

Thats sound good. Maybe you could add it to the configuration but don't
add it by default? Calling the config() but return true if the config
doesn't exist? Do you've how would it look code-wise with the method?
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-105779204.

Thats sounds awesome! Let me know if I can help with that. Do you think it will be hard to implement?

Shouldn't take me more then a few minutes once I'm back at my computer.
On Wed, 27 May 2015 16:55 Vincent Klaiber<EMAIL_ADDRESS>wrote:

Thats sounds awesome! Let me know if I can help with that. Do you think it
will be hard to implement?
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-105780916.

Sounds great! This is the only thing holding me back from merging the dingo branch into my current API project. Let me know how it goes.

To be honest I the current exception handler could work if there only were a way to extend it even more. I'll try to extend it again.

I did manage to solve this rebinding the current exception handler. Though, I think the interface idea is still is great! Thanks for taking time to helping me out. Really appreciated :)

Yeah for sure mate. Going to implement an interface for this I think.

Cool, let me know how it goes!

There's now a contract for replacing it at Dingo\Api\Contract\Exception\Handler. The handle method is the only requirement.

Awesome! I'll try it out.

Hey guys! sorry to bring back to life an already closed issue but I'm not sure if my doubs merit a brand new issue on the same subject.
I've been playing with dingo/api for the past couple of weeks and I'm pretty much pleased with it....except for 1 inconvinient situation I'm having with the whole exceptions handling management this package offers. At first I thought dingo would only automatically handle exceptions extending from Symfony\Component\HttpKernel\Exception\HttpException as it's stated in the wiki...however when I throw a Illuminate\Database\Eloquent\ModelNotFoundException from a findOrFail() method... dingo seems to catch that too and render a 500 status code with the message "No query results for model...etc"
I've tried to make my own response to that exception but have had very little success since dingo's handler seems to act before anything I've tried so far... I found this issue to be my very own situation but it's not entirely clear to me how I'm supposed to extend the handler or implement the right method or even correctly register/bind it (tried doing the previous things in as many ways as I could think of). Could any of you guys give me some example on how to do this step by step? I'm not entirely new to laravel but I'm no master either :) so please bear with me. Thanks in advance!!

You can use the register method on the handler to setup your own responses
for certain exceptions. Just pass a closure with a type hinted exception.
On Fri, 17 Jul 2015 08:12 Oscar Espitia<EMAIL_ADDRESS>wrote:

Hey guys! sorry to bring back to life an already closed issue but I'm not
sure if my doubs merit a brand new issue on the same subject.
I've been playing with dingo/api for the past couple of weeks and I'm
pretty much pleased with it....except for 1 inconvinient situation I'm
having with the whole exceptions handling management this package offers.
At first I thought dingo would only automatically handle exceptions
extending from Symfony\Component\HttpKernel\Exception\HttpException as it's
stated in the wiki...however when I throw a
Illuminate\Database\Eloquent\ModelNotFoundException from a findOrFail()
method... dingo seems to catch that too and render a 500 status code with
the message "No query results for model...etc"
I've tried to make my own response to that exception but have had very
little success since dingo's handler seems to act before anything I've
tried so far... I found this issue to be my very own situation but it's not
entirely clear to me how I'm supposed to extend the handler or implement
the right method or even correctly register/bind it (tried doing the
previous things in as many ways as I could think of). Could any of you guys
give me some example on how to do this step by step? I'm not entirely new
to laravel but I'm no master either :) so please bear with me. Thanks in
advance!!
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122119182.

https://github.com/dingo/api/wiki/Errors-And-Error-Responses#custom-exception-responses
On Fri, 17 Jul 2015 08:17 Jason Lewis<EMAIL_ADDRESS>wrote:

You can use the register method on the handler to setup your own responses
for certain exceptions. Just pass a closure with a type hinted exception.
On Fri, 17 Jul 2015 08:12 Oscar Espitia<EMAIL_ADDRESS>wrote:

Hey guys! sorry to bring back to life an already closed issue but I'm not
sure if my doubs merit a brand new issue on the same subject.
I've been playing with dingo/api for the past couple of weeks and I'm
pretty much pleased with it....except for 1 inconvinient situation I'm
having with the whole exceptions handling management this package offers.
At first I thought dingo would only automatically handle exceptions
extending from Symfony\Component\HttpKernel\Exception\HttpException as it's
stated in the wiki...however when I throw a
Illuminate\Database\Eloquent\ModelNotFoundException from a findOrFail()
method... dingo seems to catch that too and render a 500 status code with
the message "No query results for model...etc"
I've tried to make my own response to that exception but have had very
little success since dingo's handler seems to act before anything I've
tried so far... I found this issue to be my very own situation but it's not
entirely clear to me how I'm supposed to extend the handler or implement
the right method or even correctly register/bind it (tried doing the
previous things in as many ways as I could think of). Could any of you guys
give me some example on how to do this step by step? I'm not entirely new
to laravel but I'm no master either :) so please bear with me. Thanks in
advance!!
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122119182.

Hey @jasonlewis ! thanks for the quick reply. Are you saying I can pass in "Illuminate\Database\Eloquent\ModelNotFoundException" to that method and instead of returning a response instance throw a different exception? if so where could I place that bit of code you've referenced? a service provider? I'm sorry but it's in the details where I'm struggling the most :(

You return a response instance from that method.
On Fri, 17 Jul 2015 08:24 Oscar Espitia<EMAIL_ADDRESS>wrote:

Hey @jasonlewis https://github.com/jasonlewis ! thanks for the quick
reply. Are you saying I can pass in
"Illuminate\Database\Eloquent\ModelNotFoundException" to that method and
instead of returning a response instance throw a different exception? if so
where could I place that bit of code you've referenced? a service provider?
I'm sorry but it's in the details where I'm struggling the most :(
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122121046.

I'm not sure why you'd want to throw another exception. You're trying to
return a valid error response so that the client can still consume the
response and see why the error was returned.
As for where it goes. A service provider is a good a spot as any. :)
On Fri, 17 Jul 2015 08:28 Jason Lewis<EMAIL_ADDRESS>wrote:

You return a response instance from that method.
On Fri, 17 Jul 2015 08:24 Oscar Espitia<EMAIL_ADDRESS>wrote:

Hey @jasonlewis https://github.com/jasonlewis ! thanks for the quick
reply. Are you saying I can pass in
"Illuminate\Database\Eloquent\ModelNotFoundException" to that method and
instead of returning a response instance throw a different exception? if so
where could I place that bit of code you've referenced? a service provider?
I'm sorry but it's in the details where I'm struggling the most :(
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122121046.

I see, well main reason I wanted to "catch" that particular exception and replace it with another is I'm using a small structure to format status codes and error codes in a centralized way and all the exceptions extending from that point will throw a simple HttpException that dingo catches to ultimately render the specific error. Is there any way I can achieve such behavour? or am I just going nuts with this?
BTW srsly thanks for your quick reply :)

The only way I can see you having that level of control is to either extend
or write your own handler and rebind the current one. You can rebind it by
replacing 'api.exception' with your instance. See more about that in this
issue above.
If I were you I'd probably simply extend it and override the
genericResponse method. You could probably do your logic there for
formatting your exceptions if you want.
On Fri, 17 Jul 2015 08:32 Oscar Espitia<EMAIL_ADDRESS>wrote:

I see, well main reason I wanted to "catch" that particular exception and
replace it with another is I'm using a small structure to format status
codes and error codes in a centralized way and all the exceptions extending
from that point will throw a simple HttpException that dingo catches to
ultimately render the specific error. Is there any way I can achieve such
behavour? or am I just going nuts with this?
BTW srsly thanks for your quick reply :)
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122122456.

Hello @jasonlewis me again... sadly :( I've been trying to do what you suggested I created my own Handler class called ApiHandler extending from Dingo\Api\Exception\Handler and overriding the genericResponse as follows:
// App\Exceptions\ApiHandler.php
protected function genericResponse(Exception $exception)
{
    if ($exception instanceof Illuminate\Database\Eloquent\ModelNotFoundException) {
        throw new App\Exceptions\Models\ModelNotFoundException();
    }
    parent::genericResponse($exception);
}

Then I added this line to the register method inside App\Providers\AppServiceProvider:
$this->app->bind('api.exception', 'PanelSW\Exceptions\ApiHandler');

I'm uncertain as for what am I doing wrong but it seems like I've completely broken the api responses as I get this message while testing any endpoint in Postman: Could not get any response.
I've tried making my ApiHandler not only extend Dingo\Api\Exception\Handler but also implement the Dingo\Api\Contract\Exception\Handler (ofc adding the corresponding handle method), even binding my ApiHandler to that contract in a similar fashion using the register method of App\Providers\AppServiceProvider, for crying outloud I've even tried creating a singleton within bootstrap/app.php and still have had zero success.
I'm sorry to bother you once again but could you please point me in the right direction here? how can I perform this rebind process you described and am I placing it in the wrong provider/method? An example would go a long way! Thanks!

BTW I should also mention that in some cases I've managed to make the responses work in Postman...however still have no success with that ModelNotFoundException I keep getting this instead of my formatted response:
{
  "message": "No query results for model [App\\\\Models\\\\Company].",
  "status_code": 500
}

I'm going to be overhauling exception handling today because I'm not happy with it, aside from the fact it doesn't behave properly in Lumen.
But I have to ask, what is the benefit you're getting by rethrowing the exceptions as a generic HttpException? It seems like you could simply catch all exceptions and format the response as you see fit. You can't throw an exception from within the handle method of the exception handler. Well, you can, but I have no idea what the result would be. It MUST return a response instance.

Well it all started with the incremental APIs series and the interesting idea of keeping responses agnostic without writing status/error codes directly into each response simply because it might become a nightmare to change in the future (this is true for long-term-support projects). So I began wrapping my head around the idea of creating contracts to centralize those using constants so I can easily just implement such contracts wherever I need to send a response. I started creating different exceptions for different particular situation such as TokenNotFound or TokenExpired and formatting the status code as well as the message to be returned (array including specific error code) all of them extending from HttpException and it all worked like a charm. I completely got rid of the need to have error responses in my controllers, I'd simply throw a particular exception.
At first I thought that dingo/api had it well covered with its catching of any HttpException thrown anywhere in the framework but then I ran into the ModelNotFoundException situation (very common) so I thought the easiest and most efficient way to handle that was to catch any and every ModelNotFoundException thrown by the query builder so I could just throw a different exception instead, one that'd extend from HttpException (formatted in a same fashion as the Token exceptions I mentioned above) so ultimately wouldn't mean much hassle and would still use dingo/api error response system.
Perhaps I'm overcomplicating myself here and should instead do what you advice me to...catch all exceptions and use my approach instead but allowing for actual error responses to be sent instead of that last step where I rely on dingo to do it for me.
Just so I don't keep messing my head and going around the problem for so long...what is the best way to efficiently disable all error responses sent by dingo/api?
Also, I must say it seems like the exception handling has given your amazing package lots of drawbacks and unexpected situations because everyone needs a different approach at it...exception handling ultimately includes a lot of custiomization. May I suggest to perhaps take a step back and go with a much simpler approach? Maybe if it's too difficult to make it work as flexible as possible so it pleases everyone while still keeping it easy to use...you should not include it at all? I'm thinking modularizing certain parts of your package to be completely replaceable/optional so if someone is not happy with your default behavour for exception handling...they could just as easy implement something else (3rd party exception handling packages or their own)?

I'll write a note detailed response in the morning but I will say this...
The exception handling is tough because I either do nothing and leave it up
to devs to implement their own exception handling, or I try to implement
something like I have now. There isn't really any middle ground.
I'll probably try and revise it a bit though. If I can. Like you said,
everyone wants exceptions differently. So perhaps not worrying about a
handler is the best approach. We'll see.
On Sun, 19 Jul 2015 00:32 Oscar Espitia<EMAIL_ADDRESS>wrote:

Well it all started with the incremental APIs series and the interesting
idea of keeping responses agnostic without writing status/error codes
directly into each response simply because it might become a nightmare to
change in the future (this is true for long-term-support projects). So I
began wrapping my head around the idea of creating contracts to centralize
those using constants so I can easily just implement such contracts
wherever I need to send a response. I started creating different exceptions
for different particular situation such as TokenNotFound or TokenExpired
and formatting the status code as well as the message to be returned (array
including specific error code) all of them extending from HttpException and
it all worked like a charm. I completely got rid of the need to have error
responses in my controllers, I'd simply throw a particular exception.
At first I thought that dingo/api had it well covered with its catching of
any HttpException thrown anywhere in the framework but then I ran into the
ModelNotFoundException situation (very common) so I thought the easiest and
most efficient way to handle that was to catch any and every
ModelNotFoundException thrown by the query builder so I could just throw a
different exception instead, one that'd extend from HttpException
(formatted in a same fashion as the Token exceptions I mentioned above) so
ultimately wouldn't mean much hassle and would still use dingo/api error
response system.
Perhaps I'm overcomplicating myself here and should instead do what you
advice me to...catch all exceptions and use my approach instead but
allowing for actual error responses to be sent instead of that last step
where I rely on dingo to do it for me.
Just so I don't keep messing my head and going around the problem for so
long...what is the best way to efficiently disable all error responses
sent by dingo/api?
Also, I must say it seems like the exception handling has given your
amazing package lots of drawbacks and unexpected situations because
everyone needs a different approach at it...exception handling ultimately
includes a lot of custiomization. May I suggest to perhaps take a step back
and go with a much simpler approach? Maybe if it's too difficult to make it
work as flexible as possible so it pleases everyone while still keeping it
easy to use...you should not include it at all? I'm thinking modularizing
certain parts of your package to be completely replaceable/optional so if
someone is not happy with your default behavour for exception
handling...they could just as easy implement something else (3rd party
exception handling packages or their own)?
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122549756.

Also worth noting is that you can't throw an exception from within Laravels
handler. You'll find that you probably need to catch the model not found
exception earlier and rethrow it, regardless of what changes I make. Is
that a possibility?
Or override the eloquent method that throws the exception.
On Sun, 19 Jul 2015 00:38 Jason Lewis<EMAIL_ADDRESS>wrote:

I'll write a note detailed response in the morning but I will say this...
The exception handling is tough because I either do nothing and leave it up
to devs to implement their own exception handling, or I try to implement
something like I have now. There isn't really any middle ground.
I'll probably try and revise it a bit though. If I can. Like you said,
everyone wants exceptions differently. So perhaps not worrying about a
handler is the best approach. We'll see.
On Sun, 19 Jul 2015 00:32 Oscar Espitia<EMAIL_ADDRESS>wrote:

Well it all started with the incremental APIs series and the interesting
idea of keeping responses agnostic without writing status/error codes
directly into each response simply because it might become a nightmare to
change in the future (this is true for long-term-support projects). So I
began wrapping my head around the idea of creating contracts to centralize
those using constants so I can easily just implement such contracts
wherever I need to send a response. I started creating different exceptions
for different particular situation such as TokenNotFound or TokenExpired
and formatting the status code as well as the message to be returned (array
including specific error code) all of them extending from HttpException and
it all worked like a charm. I completely got rid of the need to have error
responses in my controllers, I'd simply throw a particular exception.
At first I thought that dingo/api had it well covered with its catching
of any HttpException thrown anywhere in the framework but then I ran into
the ModelNotFoundException situation (very common) so I thought the easiest
and most efficient way to handle that was to catch any and every
ModelNotFoundException thrown by the query builder so I could just throw a
different exception instead, one that'd extend from HttpException
(formatted in a same fashion as the Token exceptions I mentioned above) so
ultimately wouldn't mean much hassle and would still use dingo/api error
response system.
Perhaps I'm overcomplicating myself here and should instead do what you
advice me to...catch all exceptions and use my approach instead but
allowing for actual error responses to be sent instead of that last step
where I rely on dingo to do it for me.
Just so I don't keep messing my head and going around the problem for so
long...what is the best way to efficiently disable all error responses
sent by dingo/api?
Also, I must say it seems like the exception handling has given your
amazing package lots of drawbacks and unexpected situations because
everyone needs a different approach at it...exception handling ultimately
includes a lot of custiomization. May I suggest to perhaps take a step back
and go with a much simpler approach? Maybe if it's too difficult to make it
work as flexible as possible so it pleases everyone while still keeping it
easy to use...you should not include it at all? I'm thinking modularizing
certain parts of your package to be completely replaceable/optional so if
someone is not happy with your default behavour for exception
handling...they could just as easy implement something else (3rd party
exception handling packages or their own)?
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-122549756.

Okay after a bit of deliberating I don't think I'm going to change it. For 95% of people it will work well. For the remaining 5% you already have the option of simply replacing it with your own handler. All you need to do is rebind the api.exception instance and update the Illuminate\Contracts\Debug\ExceptionHandler binding as well.
You should implement the Dingo\Api\Contract\Exception\Handler as well so that you can handle any exceptions. That way you have complete control over the exceptions.

:+1:

@jasonlewis I am quite new to Laravel and I am trying to rebind api.exception and implement totally custom exception handler. I can't get it work.
I have custom exception handler like this:
class Handler extends \Dingo\Api\Exception\Handler {
    function handle(Exception $exception) {
        dd("test");
        return parent::handle($exception);
    }
}

I have registered the handler in AppServiceProvider's register() method:
$this->app->bind('api.exception', 'App\Exceptions\Handler');

The handle() method never get's called. What am I doing wrong?
Thanks!

@jasonlewis What's the best way of implementing Bugsnag error reporting into the exception handler? Completely baffled by it. Thanks.

@LeeMcNeil I would use https://github.com/altthree/bugsnag by @GrahamCampbell

Would that automatically pickup exceptions when using Dingo? That's what
i'm having issues with - with the Bugsnag laravel package you need to
replace the exception handler which you can't easily do with Dingo.
On 2 February 2016 at 11:58, Vincent Klaiber<EMAIL_ADDRESS>wrote:

@LeeMcNeil https://github.com/LeeMcNeil I would use
https://github.com/altthree/bugsnag by @GrahamCampbell
https://github.com/GrahamCampbell
—
Reply to this email directly or view it on GitHub
https://github.com/dingo/api/issues/411#issuecomment-178529865.

--
Regards
Lee McNeil
Email<EMAIL_ADDRESS>Skype: lee.j.mcneil
Tebex Limited Registered in England & Wales No. 08129184.

I was able to replace Dingo exception hadler like this:
in AppServiceProvider.php
use Dingo\Api\Provider\ServiceProvider; //Instead of Illuminate\Support\ServiceProvider to use $this->config();
use App\Exceptions\ApiExceptionsHandler as ExceptionHandler;

class AppServiceProvider extends ServiceProvider
{
  public function boot()
  {
    $this->app->singleton('api.exception', function ($app) {
      return new ExceptionHandler(
        $app['Illuminate\Contracts\Debug\ExceptionHandler'],
        $this->config('errorFormat'),
        $this->config('debug')
      );
    });
  }
}

And content of app/Exceptions/ApiExceptionsHandler.php:
namespace App\Exceptions;

use Exception;
use Dingo\Api\Exception\Handler as DingoHandler;

class ApiExceptionsHandler extends DingoHandler {
  public function handle(Exception $exception)
  {
    return parent::handle($exception);
  }
}

And you can go from here.
Hope it helps someone :)

Finally! Sorry to post on closed issue, but I must share this solution somewhere, I lost so many hours on it..
First of all create your own exception handler:
app/Exceptions/ApiExceptionsHandler.php
<?php
namespace App\Exceptions;

use Exception;
use Dingo\Api\Exception\Handler as DingoHandler;

class ApiExceptionsHandler extends DingoHandler
{
    public function handle(Exception $exception)
    {
        return parent::handle($exception);
    }
}

Then create wrapper for Laravel Dingo service provider:
app/Providers/DingoServiceProvider.php
<?php
namespace App\Providers;

use Dingo\Api\Provider\LaravelServiceProvider;
use App\Exceptions\ApiExceptionsHandler as ExceptionHandler;

class DingoServiceProvider extends LaravelServiceProvider
{
    protected function registerExceptionHandler()
    {
        $this->app->singleton('api.exception', function ($app) {
            return new ExceptionHandler($app['Illuminate\Contracts\Debug\ExceptionHandler'], $this->config('errorFormat'), $this->config('debug'));
        });
    }
}

Lastly replace original Dingo service provider to this wrapper:
/config/app.com
...
'providers' => [
...
    //Dingo\Api\Provider\LaravelServiceProvider::class, // <- Remove this
    App\Providers\DingoServiceProvider::class,
...
];

That's it. Hope it'll help someone.

Dingo\Api\Exception\Handler supports Exceptions Status Code by default, as seen in line 180:
    protected function getStatusCode(Exception $exception)     {         return $exception instanceof HttpExceptionInterface ? $exception->getStatusCode() : 500;     }
All you have to do is implement the HttpExceptionInterface in your exception.
In my project, I just extend from Symfony's HttpException (which is the Interface implementation):
use Symfony\Component\HttpKernel\Exception\HttpException;

class PermissionDeniedException extends HttpException

@shanginn 's solution also works pretty well if you need a custom ExceptionHandler.

@shanginn thanks a lot, it work great.

@shanginn
I got a error

(1/1) BindingResolutionExceptionTarget [Illuminate\Contracts\Http\Kernel] is not instantiable.
--
in Container.php (line 918)
at Container->notInstantiable('Illuminate\\Contracts\\Http\\Kernel')in Container.php (line 758)
at Container->build('Illuminate\\Contracts\\Http\\Kernel')in Container.php (line 631)
at Container->resolve('Illuminate\\Contracts\\Http\\Kernel', array())in Container.php (line 586)
at Container->make('Illuminate\\Contracts\\Http\\Kernel', array())in Application.php (line 230)
at Application->make('Illuminate\\Contracts\\Http\\Kernel')in LaravelServiceProvider.php (line 28)
at LaravelServiceProvider->boot()
at call_user_func_array(array(object(DingoServiceProvider), 'boot'), array())

(1/1) BindingResolutionExceptionTarget [Illuminate\Contracts\Http\Kernel] is not instantiable.
--
in Container.php (line 918)
at Container->notInstantiable('Illuminate\\Contracts\\Http\\Kernel')in Container.php (line 758)
at Container->build('Illuminate\\Contracts\\Http\\Kernel')in Container.php (line 631)
at Container->resolve('Illuminate\\Contracts\\Http\\Kernel', array())in Container.php (line 586)
at Container->make('Illuminate\\Contracts\\Http\\Kernel', array())in Application.php (line 230)
at Application->make('Illuminate\\Contracts\\Http\\Kernel')in LaravelServiceProvider.php (line 28)
at LaravelServiceProvider->boot()
at call_user_func_array(array(object(DingoServiceProvider), 'boot'), array())in BoundMethod.php (line 29)
at BoundMethod::Illuminate\Container\{closure}()in BoundMethod.php (line 87)
at BoundMethod::callBoundMethod(object(Application), array(object(DingoServiceProvider), 'boot'), object(Closure))in BoundMethod.php (line 31)
at BoundMethod::call(object(Application), array(object(DingoServiceProvider), 'boot'), array(), null)in Container.php (line 549)
at Container->call(array(object(DingoServiceProvider), 'boot'))in Application.php (line 197)
at Application->register(object(DingoServiceProvider))in app.php (line 100)
at require('/usr/share/nginx/html/decaptcha/api/bootstrap/app.php')in index.php (line 14)

@shanginn thanks a lot, it work great.
:tada: 2

@shanginn I've followed exactly like that but it didn't work. I'm getting 500 response and no response data.

Hi guys
It's actually very easy to override the dingo exception handler. Just make a new exception handler class in your app, which extends the dingo one, and do the following in your AppServiceProvider
    /**
     * Register any application services.
     *
     * @return void
     */
    public function register()
    {
        $this->registerExceptionHandler();
    }

    /**
     * Register the exception handler - extends the Dingo one
     *
     * @return void
     */
    protected function registerExceptionHandler()
    {
        $this->app->singleton('api.exception', function ($app) {
            return new ApiExceptionHandler($app['Illuminate\Contracts\Debug\ExceptionHandler'], Config('api.errorFormat'), Config('api.debug'));
        });
    }

In this case, the ApiExceptionHandler is my custom exception handler. And so in extending dingo's one, you are free to override any methods you wish.

@rohitkhatri  @adhatama . Hi guys, I had this problem before, but I tried to solve it, it work great.
app/Providers/DingoServiceProvider.php   Change to
`<?php
namespace App\Providers;
use Dingo\Api\Provider\DingoServiceProvider as DingoServiceProviders;
use App\Exceptions\ApiExceptionsHandler as ExceptionHandler;
class DingoServiceProvider extends DingoServiceProviders
{
protected function registerExceptionHandler()
{
$this->app->singleton('api.exception', function ($app) {
return new ExceptionHandler($app['Illuminate\Contracts\Debug\ExceptionHandler'], $this->config('errorFormat'), $this->config('debug'));
});
}
}`

@double-reinbows You actually don't need to override the service provider at all - that is way too much effort, have a look at my post just up above.

@specialtactics thank you for your advice but none of the suggestions here provide a way for me to access the original request which I kinda need to redirect non-GET requests (trying to implement versioning).

@double-reinbows you can get request data globally using the request() laravel global helper.

i have faced the same issue and here is my custom solution this is simple and work for me,


Bootstrap timeout just fires once

If a boostrap timeout occurs, the boostrap process is retried but no other timeout is set in case the boostrap process does not succeed again.

This is fixed in 3.2.3.


Watson Conversation is called with the response payload

I got up and running with botkit and the watson middleware.
When I looked at the logs in the "improve" tab, I noticed that Watson Conversation was also getting called with the response payload.
In my example I would issue a "hello", Watson would respond with a "Hello Again" but then the code was sending this response back to the server as a user request so I would also see in the improve logs an utterance coming from the user of "Hello Again".
I debugged the code and it looks like receive also gets called when a message is sent back to the client (this was slack).  I hacked the code below to look for bot_id and this seems to have fixed it, but it may well only work for slack.
      if (!middleware.conversation) {
        debug('Creating Conversation object with parameters: ' + JSON.stringify(config, 2, null));
        middleware.conversation = new ConversationV1(config);
      }

      if (!message.text || ignoreType.indexOf(message.type) !== -1 || message.reply_to || message.bot_id) {
        // Ignore messages initiated by Slack. Reply with dummy output object

        message.watsonData = {
          output: {
            text: []
          }
        };
        return message;
      }

I've tested this with bot Slack and Facebook Messenger, and it looks like this problem is unique to Slack. The change you proposed above does fix the problem, and it seems like the best solution to me. I'll submit a pull request and have others review it as well.


[GH-15776]Switch center-channel-color-## with center-channel-color-rgb variables

Summary
Switched center-channel-color-## with center-channel-color-rgb variables
Ticket Link
Fixes: https://github.com/mattermost/mattermost-server/issues/15776

Hello @haardikdharma10,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


TCX support

Training Center XML is a thing, and should be supported here, instead of in the semi-abandoned tcx project.

I should just maintain tcx when necessary, this isn't a common enough format for inclusion.


ArbNumerics doesn't precompile

Just got the following error precompiling ArbNumerics.
ERROR: LoadError: LoadError: SystemError: realpath: No such file or directory
Stacktrace:
[1] #systemerror#43(::Nothing, ::Function, ::Symbol, ::Bool) at ./error.jl:134
[2] systemerror at ./error.jl:134 [inlined]
[3] realpath(::String) at ./path.jl:367
[4] top-level scope at /Users/giulio/.julia/packages/ArbNumerics/qyTDE/src/support/arblib.jl:15
[5] include at ./boot.jl:326 [inlined]
[6] include_relative(::Module, ::String) at ./loading.jl:1038
[7] include at ./sysimg.jl:29 [inlined]
[8] include(::String) at /Users/giulio/.julia/packages/ArbNumerics/qyTDE/src/ArbNumerics.jl:8
[9] top-level scope at none:0
[10] include at ./boot.jl:326 [inlined]
[11] include_relative(::Module, ::String) at ./loading.jl:1038
[12] include(::Module, ::String) at ./sysimg.jl:29
[13] top-level scope at none:2
[14] eval at ./boot.jl:328 [inlined]
[15] eval(::Expr) at ./client.jl:404
[16] top-level scope at ./none:3
in expression starting at /Users/giulio/.julia/packages/ArbNumerics/qyTDE/src/support/arblib.jl:9
in expression starting at /Users/giulio/.julia/packages/ArbNumerics/qyTDE/src/ArbNumerics.jl:145

Please let me see julia> versioninfo

Julia> versioninfo()
Julia Version 1.1.0
Commit 80516ca202 (2019-01-21 21:24 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin14.5.0)
CPU: Intel(R) Core(TM) i5-6287U CPU @ 3.10GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, skylake)
Environment:
JULIA_EDITOR = atom  -a
JULIA_NUM_THREADS = 2

A work-around is given here: https://github.com/JeffreySarnoff/ArbNumerics.jl/issues/24
I will develop a "cure" for this.

Please try
pkg> rm ArbNumerics
pkg> add ArbNumerics#master
julia> using ArbNumerics

and let me know if that works
thank you

This is what I get:
(coulomb-waves) pkg> add ArbNumerics#master
   Cloning git-repo `https://github.com/JeffreySarnoff/ArbNumerics.jl.git`
  Updating git-repo `https://github.com/JeffreySarnoff/ArbNumerics.jl.git`
 Resolving package versions...
  Updating `~/work/projects/td-cis/coulomb-waves/Project.toml`
  [7e558dbc] + ArbNumerics v0.6.9 #master (https://github.com/JeffreySarnoff/ArbNumerics.jl.git)
  Updating `~/work/projects/td-cis/coulomb-waves/Manifest.toml`
  [7e558dbc] + ArbNumerics v0.6.9 #master (https://github.com/JeffreySarnoff/ArbNumerics.jl.git)
  [01680d73] + GenericSVD v0.2.2
  [c145ed77] + GenericSchur v0.3.0
  [0d4725de] + Readables v0.3.3
  Building ArbNumerics → `~/.julia/packages/ArbNumerics/sxukQ/deps/build.log`

julia> using ArbNumerics
[ Info: Precompiling ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442]
ERROR: LoadError: LoadError: SystemError: unable to read directory /Users/jagot/.julia/packages/ArbNumerics/sxukQ/deps/usr/bin: No such file or directory
Stacktrace:
 [1] readdir(::String) at ./file.jl:628
 [2] top-level scope at /Users/jagot/.julia/packages/ArbNumerics/sxukQ/src/support/arblib.jl:10
 [3] include at ./boot.jl:328 [inlined]
 [4] include_relative(::Module, ::String) at ./loading.jl:1094
 [5] include at ./Base.jl:31 [inlined]
 [6] include(::String) at /Users/jagot/.julia/packages/ArbNumerics/sxukQ/src/ArbNumerics.jl:8
 [7] top-level scope at /Users/jagot/.julia/packages/ArbNumerics/sxukQ/src/ArbNumerics.jl:145
 [8] include at ./boot.jl:328 [inlined]
 [9] include_relative(::Module, ::String) at ./loading.jl:1094
 [10] include(::Module, ::String) at ./Base.jl:31
 [11] top-level scope at none:2
 [12] eval at ./boot.jl:330 [inlined]
 [13] eval(::Expr) at ./client.jl:432
 [14] top-level scope at ./none:3
in expression starting at /Users/jagot/.julia/packages/ArbNumerics/sxukQ/src/support/arblib.jl:10
in expression starting at /Users/jagot/.julia/packages/ArbNumerics/sxukQ/src/ArbNumerics.jl:145
ERROR: Failed to precompile ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442] to /Users/jagot/.julia/compiled/v1.2/ArbNumerics/Xn6ml.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1253
 [3] _require(::Base.PkgId) at ./loading.jl:1013
 [4] require(::Base.PkgId) at ./loading.jl:911
 [5] require(::Module, ::Symbol) at ./loading.jl:906

thanks .. that helps

OK -- I had written "dylib" as "dynlib", that should be fixed now.  The logic should select the proper directory, it counts occurrences of each possible extension in both the bin and lib dirs.
Please try the same sequence once again.  If it fail this time, I'll go with another approach.
Thanks for the help.

Hold up -- one more fix to do.

Alright, give it a go.

Just tried, still the same error as above:
julia> using ArbNumerics
[ Info: Recompiling stale cache file /Users/bcunha/.julia/compiled/v1.2/ArbNumerics/Xn6ml.ji for ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442]
ERROR: LoadError: LoadError: SystemError: unable to read directory /Users/bcunha/.julia/packages/ArbNumerics/5CSpq/deps/usr/bin: No such file or directory
Stacktrace:
[1] readdir(::String) at ./file.jl:628
[2] top-level scope at /Users/bcunha/.julia/packages/ArbNumerics/5CSpq/src/support/arblib.jl:16
[3] include at ./boot.jl:328 [inlined]
[4] include_relative(::Module, ::String) at ./loading.jl:1094
[5] include at ./Base.jl:31 [inlined]
[6] include(::String) at /Users/bcunha/.julia/packages/ArbNumerics/5CSpq/src/ArbNumerics.jl:8
[7] top-level scope at /Users/bcunha/.julia/packages/ArbNumerics/5CSpq/src/ArbNumerics.jl:145
[8] include at ./boot.jl:328 [inlined]
[9] include_relative(::Module, ::String) at ./loading.jl:1094
[10] include(::Module, ::String) at ./Base.jl:31
[11] top-level scope at none:2
[12] eval at ./boot.jl:330 [inlined]
[13] eval(::Expr) at ./client.jl:432
[14] top-level scope at ./none:3
in expression starting at /Users/bcunha/.julia/packages/ArbNumerics/5CSpq/src/support/arblib.jl:15
in expression starting at /Users/bcunha/.julia/packages/ArbNumerics/5CSpq/src/ArbNumerics.jl:145
ERROR: Failed to precompile ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442] to /Users/bcunha/.julia/compiled/v1.2/ArbNumerics/Xn6ml.ji.
Stacktrace:
[1] error(::String) at ./error.jl:33
[2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1253
[3] _require(::Base.PkgId) at ./loading.jl:1013
[4] require(::Base.PkgId) at ./loading.jl:911
[5] require(::Module, ::Symbol) at ./loading.jl:906

should work now -- really (my copy/paste error .. long night).

Sadly not...:
julia> using ArbNumerics
[ Info: Precompiling ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442]
ERROR: LoadError: LoadError: SystemError: realpath: No such file or directory
Stacktrace:
 [1] #systemerror#44(::Nothing, ::typeof(systemerror), ::Symbol, ::Bool) at ./error.jl:134
 [2] systemerror at ./error.jl:134 [inlined]
 [3] realpath(::String) at ./path.jl:380
 [4] top-level scope at /Users/jagot/.julia/packages/ArbNumerics/Q74bo/src/support/arblib.jl:55
 [5] include at ./boot.jl:328 [inlined]
 [6] include_relative(::Module, ::String) at ./loading.jl:1094
 [7] include at ./Base.jl:31 [inlined]
 [8] include(::String) at /Users/jagot/.julia/packages/ArbNumerics/Q74bo/src/ArbNumerics.jl:8
 [9] top-level scope at /Users/jagot/.julia/packages/ArbNumerics/Q74bo/src/ArbNumerics.jl:145
 [10] include at ./boot.jl:328 [inlined]
 [11] include_relative(::Module, ::String) at ./loading.jl:1094
 [12] include(::Module, ::String) at ./Base.jl:31
 [13] top-level scope at none:2
 [14] eval at ./boot.jl:330 [inlined]
 [15] eval(::Expr) at ./client.jl:432
 [16] top-level scope at ./none:3
in expression starting at /Users/jagot/.julia/packages/ArbNumerics/Q74bo/src/support/arblib.jl:43
in expression starting at /Users/jagot/.julia/packages/ArbNumerics/Q74bo/src/ArbNumerics.jl:145
ERROR: Failed to precompile ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442] to /Users/jagot/.julia/compiled/v1.2/ArbNumerics/Xn6ml.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1253
 [3] _require(::Base.PkgId) at ./loading.jl:1013
 [4] require(::Base.PkgId) at ./loading.jl:911
 [5] require(::Module, ::Symbol) at ./loading.jl:906

yuck -- It is difficult without a Mac. I may get a relatively inexpensive one this morning.

I can appreciate that. I hope you're not just getting the Mac to fix compile errors for others (although being a very kind gesture...)?

If you are willing to go through a few more iterations -- that would be easiest.
I am going to put some println statements into the file that does not yet precompile, and they may tell me what is off-kilter.

Sure, go ahead!

julia> using ArbNumerics
[ Info: Precompiling ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442]

bindir exts = [""]

libdir exts = [".dylib", ".dylib", ".2", ".dylib", ".dylib", ".13", ".dylib", ".dylib", ".la", ".dylib", ".dylib", ".la", ".dylib", ".dylib", ".la", ""]

dlls = (0, 0, 0)

dylibs = (20, 10, 10)

sos = (0, 0, 0)

use dlls, dylibs, sos = (false, true, false)

use bindir = true

ERROR: LoadError: LoadError: SystemError: realpath: No such file or directory
Stacktrace:
 [1] #systemerror#44(::Nothing, ::typeof(systemerror), ::Symbol, ::Bool) at ./error.jl:134
 [2] systemerror at ./error.jl:134 [inlined]
 [3] realpath(::String) at ./path.jl:380
 [4] top-level scope at /Users/jagot/.julia/packages/ArbNumerics/TO4Sj/src/support/arblib.jl:68
 [5] include at ./boot.jl:328 [inlined]
 [6] include_relative(::Module, ::String) at ./loading.jl:1094
 [7] include at ./Base.jl:31 [inlined]
 [8] include(::String) at /Users/jagot/.julia/packages/ArbNumerics/TO4Sj/src/ArbNumerics.jl:8
 [9] top-level scope at /Users/jagot/.julia/packages/ArbNumerics/TO4Sj/src/ArbNumerics.jl:145
 [10] include at ./boot.jl:328 [inlined]
 [11] include_relative(::Module, ::String) at ./loading.jl:1094
 [12] include(::Module, ::String) at ./Base.jl:31
 [13] top-level scope at none:2
 [14] eval at ./boot.jl:330 [inlined]
 [15] eval(::Expr) at ./client.jl:432
 [16] top-level scope at ./none:3
in expression starting at /Users/jagot/.julia/packages/ArbNumerics/TO4Sj/src/support/arblib.jl:54
in expression starting at /Users/jagot/.julia/packages/ArbNumerics/TO4Sj/src/ArbNumerics.jl:145
ERROR: Failed to precompile ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442] to /Users/jagot/.julia/compiled/v1.2/ArbNumerics/Xn6ml.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1253
 [3] _require(::Base.PkgId) at ./loading.jl:1013
 [4] require(::Base.PkgId) at ./loading.jl:911
 [5] require(::Module, ::Symbol) at ./loading.jl:906

please give it another try and copy the what is written to the screen when it precompiles

nvr mind -- found a problem

ok - give it a go

It seems to work 🎉 :
julia> using ArbNumerics
[ Info: Precompiling ArbNumerics [7e558dbc-694d-5a72-987c-6f4ebed21442]

bindir exts = [""]

libdir exts = [".dylib", ".dylib", ".2", ".dylib", ".dylib", ".13", ".dylib", ".dylib", ".la", ".dylib", ".dylib", ".la", ".dylib", ".dylib", ".la", ""]

dlls = (0, 0, 0)

dylibs = (10, 0, 10)

sos = (0, 0, 0)

use dlls, dylibs, sos = (false, true, false)

use bindir = false

Now, what do I do to test it? I'll try running the test suite.

😎
(I had to remove the Mac target for other reasons, not ready to add it back yet)