Choosing to print only odd pages with 2 pages per side doesn't work

Version: 1.4.3
CUPS.org User: Futterwaken
I'm not sure if this bug should be reported here...
The Problem
If you choose to print 2 pages per side and select to print just the odd pages, the system does the following:
Print page 1 and page 2 of the document side by side,
Then pages 5 and 6
Then pages 9 and 10
And so forth...
If you then choose to print just the even pages you get the complimentary result:
Pages 3 and 4
Then pages 7 and 8
And so forth...
===Notice that I get odd and even pages but it skips every other pair===
What's going on
So what happens is that the result is composed with the odd and even pages of the original document and then this result gets filtered out such that if you select just odd pages, it gives you just odd pages of the result, not the original document.
What should it do
I believe that when the user picks up an option to print just odd pages (or even pages) the system should apply that filter along with the selected range of pages in the first place, only then these pages should be composed side by side (or 4  in one side or whatever).
Original scenario
I was trying to print a 400 page manual of a Texas instruments calculator.
I wanted to print two pages on each side of a A4 sized piece of paper, totalling 4 pages at A5 size in one piece of paper.
Also, I wanted to match the front side of the paper with the back side so that if the front had page 1, the back had to have page 2.
I hoped by combining front/back as pages 1/2, 3/4, 5/6, and so forth, that in the end I could cut the printed papers and make a book...
But if pages 1 and 2 get printed on the same face of the same piece of paper how can they ever be printed back to back???
I tried various workarounds with no success.
(we also should be able to select "odd" pages or "even" pages in page range and "-odd"/"-even" to get them in the reverse order).
The only working solutions involve the rearrangement of pages of the original document prior to the printing request.
How did I get through it
In the end (this make me sad) I end up doing the job on my laptop which has Windows 7 and features similar printing options, only they do what you expect.
Regards,
Futterwaken

This behaves correctly according to the requirements of IPP.

See #4837 and https://github.com/apple/cups/issues/3008#issuecomment-222032365.
I wanted to clarify the closure of this bug in case someone else stumbles upon it. It's actually in violation of IPP (and common sense) but Michael Sweet argued somewhere (I can't find where) that very few users use these options on Mac systems, so it's not worth fixing. My feeling is that perhaps the options are not often used because they don't work properly; and besides that we should work towards eventually having properly functioning software (even if this takes years to achieve).

@archenemies There is no standard IPP attribute for printing even or odd numbered pages, so the semantics as implemented by CUPS are correct - we defined them!
As for the interaction between the "number-up" and "page-ranges" attributes, we have acknowledged the issue but if we "fix" the interpretation then we will break existing clients and software that depend on behavior that has existed in CUPS since v1.0.

In IPP, as I recall, the flat rectangular entities which are created after processing "number-up" are called "impressions" and not "pages". So even if the functionality of selecting even or odd numbered pages is not part of the IPP spec, it should result in what the user is requesting, not what CUPS has implemented "according to the requirements of IPP".
In this case I can see how some users would prefer the current behavior, for example if printing a manual duplex run of a document with 2-up pages. But it should also be possible to get the more intuitive behavior that this user requested.
Regarding number-up/page-ranges - I understand the desire to preserve backwards compatibility - and I agree strongly that we should do so. But I seem to recall you arguing earlier that it was impossible to change the number-up/page-ranges interaction because apparently it involves logic which has been copy-pasted into a huge number of PPDs or filters or something, and it would be difficult to change them all at once. However, if the main obstacle is now backwards compatibility then I would advocate creating some new syntax which can allow users to get the correct/desired behavior without breaking existing applications. I can suggest such an option syntax if you like.

Per RFC 8011, "number-up" and "page-ranges" apply to input pages, which are imposed to create impressions which are printed on media sheets. Hopefully we've clarified this over RFC 2911, since many implementations have messed up on this, not just CUPS... :/
The CUPS "page-set" attribute semantics are really "impression-set", meaning it selects a set of impressions specifically to support things like manual duplex. And this is one of the reasons why it hasn't been adopted as a standard IPP extension...

Thank you for clarifying regarding the RFC. That's pretty much what I was trying to say, but it's good to know that we're on the same page (so to speak!). When you said "according to the requirements of IPP" earlier, it made it sound like you were claiming that the behavior of CUPS was specified by the standards, and I just wanted to point out that this is not the case here.
Here is the part of my message which you haven't addressed yet, should you care to do so:

... But it should also be possible to get the more intuitive behavior that this user requested.

Regarding number-up/page-ranges - I understand the desire to preserve backwards compatibility - and I agree strongly that we should do so. But I seem to recall you arguing earlier that it was impossible to change the number-up/page-ranges interaction because apparently it involves logic which has been copy-pasted into a huge number of PPDs or filters or something, and it would be difficult to change them all at once. However, if the main obstacle is now backwards compatibility then I would advocate creating some new syntax which can allow users to get the correct/desired behavior without breaking existing applications. I can suggest such an option syntax if you like.

While I appreciate wanting to provide alternate functionality for page range selection, I don't think we will be introducing a new attribute that implements the original IPP semantics with new names. Aside from causing a great deal of confusion, it will be an implementation/interoperability nightmare.


Implement c7n-sentry deploy

Closes #738. Includes #852 (will rebase if/when that lands before this is ready).

I've created the lambda using get_function, I see it in the console w/ no trigger now ... but still the same KeyError on event['awslogs'] as at https://github.com/capitalone/cloud-custodian/issues/738#issuecomment-273770074.

Alright, I think those were holdovers from previous lambda deployments. Now that we're using LogSubscription instead of Events, I think we won't expect any logs from cloud-custodian-sentry unless we log an exception from custodian-bar.

Where does cloud-custodian-sentry get its logs from? How is the configured?

/me looking into log_groups ...

I don't find UI in the console to see the arn of a log group (required by mu), guessing based on these docs ....

Progress!
(cloud-custodian) $ c7n-sentry deploy -c config.json --region=us-west-2
2017-01-20 09:09:11,758: custodian.lambda:INFO Creating subscription filter for /aws/lambda/custodian-bar
Traceback (most recent call last):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/bin/c7n-sentry", line 11, in <module>
    load_entry_point('c7n-sentry', 'console_scripts', 'c7n-sentry')()
  File "/Users/whit537/workbench/capitalone/cloud-custodian/tools/c7n_sentry/c7n_sentry/c7nsentry.py", line 509, in main
    options.command(options)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/tools/c7n_sentry/c7n_sentry/c7nsentry.py", line 468, in deploy
    manager.publish(func)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 249, in publish
    if e.add(func):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 970, in add
    destinationArn=func.alias or func.arn)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 251, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 537, in _make_api_call
    raise ClientError(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (InvalidParameterException) when calling the PutSubscriptionFilter operation: Could not execute the lambda function. Make sure you have given CloudWatch Logs permission to execute your function.
(cloud-custodian) $

diff --git a/c7n/mu.py b/c7n/mu.py
index 4525e30..1b6581e 100644
--- a/c7n/mu.py
+++ b/c7n/mu.py
@@ -960,6 +960,7 @@ class CloudWatchLogSubscription(object):
                 # iam eventual consistency and propagation
                 time.sleep(self.iam_delay)
             except ClientError as e:
+                log.exception(e)
                 if e.response['Error']['Code'] != 'ResourceConflictException':
                     raise
             # Consistent put semantics / ie no op if extant
diff --git a/tools/c7n_sentry/c7n_sentry/c7nsentry.py b/tools/c7n_sentry/c7n_sentry/c7nsentry.py
index b98786e..890aff8 100644
--- a/tools/c7n_sentry/c7n_sentry/c7nsentry.py
+++ b/tools/c7n_sentry/c7n_sentry/c7nsentry.py
@@ -456,7 +456,10 @@ def deploy(options):
         name='cloud-custodian-sentry',
         handler='handler.process_log_event',
         role='arn:aws:iam::644160558196:role/custodian-mu',
-        log_groups=[],
+        log_groups=[{
+            'logGroupName': '/aws/lambda/custodian-bar',
+            'arn': 'arn:aws:logs:us-west-2:644160558196:log-group::*'
+        }],
         project=None,
         account_name=None,
         account_id=None

(cloud-custodian) $ c7n-sentry deploy -c config.json --region=us-west-2
2017-01-20 09:20:09,172: custodian.lambda:INFO Creating subscription filter for /aws/lambda/custodian-bar
2017-01-20 09:20:09,623: custodian.lambda:ERROR An error occurred (ResourceConflictException) when calling the AddPermission operation: The statement id (aws-lambda-custodian-bar) provided already exists. Please provide a new statement id, or remove the existing statement.
Traceback (most recent call last):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 958, in add
    Principal='logs.%s.amazonaws.com' % region)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 251, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 537, in _make_api_call
    raise ClientError(parsed_response, operation_name)
ClientError: An error occurred (ResourceConflictException) when calling the AddPermission operation: The statement id (aws-lambda-custodian-bar) provided already exists. Please provide a new statement id, or remove the existing statement.
Traceback (most recent call last):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/bin/c7n-sentry", line 11, in <module>
    load_entry_point('c7n-sentry', 'console_scripts', 'c7n-sentry')()
  File "/Users/whit537/workbench/capitalone/cloud-custodian/tools/c7n_sentry/c7n_sentry/c7nsentry.py", line 509, in main
    options.command(options)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/tools/c7n_sentry/c7n_sentry/c7nsentry.py", line 468, in deploy
    manager.publish(func)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 249, in publish
    if e.add(func):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 971, in add
    destinationArn=func.alias or func.arn)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 251, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 537, in _make_api_call
    raise ClientError(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (InvalidParameterException) when calling the PutSubscriptionFilter operation: Could not execute the lambda function. Make sure you have given CloudWatch Logs permission to execute your function.

Maybe we have an old permission stuck in there that needs to be cleared out?

Sounds like statements are part of policies, but I don't find any policies (available to me?).

Where else might that statement be hiding? Somewhere under the custodian-bar Lambda?

Nothing suggestive on the advanced settings of the custodian-bar lambda.

https://docs.aws.amazon.com/lambda/latest/dg/intro-permission-model.html#intro-permission-model-access-policy

that should be in mu.py in the log subscription filter event

Yes, that is where the error is coming from (once I enabled logging). But what does it mean and how do I fix it?

I mean, apparently we think it's okay to ignore the ResourceConflictException, so that the error I should focus on is the InvalidParameterException:

Could not execute the lambda function. Make sure you have given CloudWatch Logs permission to execute your function.

I don't find a UI to view Lambda resource policies, so I guess I use the API:
(cloud-custodian) $ c7n-sentry deploy -c config.json --region=us-west-2
2017-01-21 05:44:16,096: custodian.lambda:INFO Creating subscription filter for /aws/lambda/custodian-bar
> /Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py(965)add()
-> if e.response['Error']['Code'] != 'ResourceConflictException':
(Pdb) extant
{u'Policy': u'{"Version":"2012-10-17","Id":"default","Statement":[{"Sid":"aws-lambda-custodian-bar","Effect":"Allow","Principal":{"Service":"logs.us-west-2.amazonaws.com"},"Action":"lambda:InvokeFunction","Resource":"arn:aws:lambda:us-west-2:644160558196:function:cloud-custodian-sentry","Condition":{"ArnLike":{"AWS:SourceArn":"arn:aws:logs:us-west-2:644160558196:log-group::*"}}}]}', 'ResponseMetadata': {'RetryAttempts': 0, 'HTTPStatusCode': 200, 'RequestId': '8e4e8d80-dfc6-11e6-a24f-b522455ea1d2', 'HTTPHeaders': {'date': 'Sat, 21 Jan 2017 10:44:16 GMT', 'x-amzn-requestid': '8e4e8d80-dfc6-11e6-a24f-b522455ea1d2', 'content-length': '422', 'content-type': 'application/json', 'connection': 'keep-alive'}}}
(Pdb) pp extant
{u'Policy': u'{"Version":"2012-10-17","Id":"default","Statement":[{"Sid":"aws-lambda-custodian-bar","Effect":"Allow","Principal":{"Service":"logs.us-west-2.amazonaws.com"},"Action":"lambda:InvokeFunction","Resource":"arn:aws:lambda:us-west-2:644160558196:function:cloud-custodian-sentry","Condition":{"ArnLike":{"AWS:SourceArn":"arn:aws:logs:us-west-2:644160558196:log-group::*"}}}]}',
 'ResponseMetadata': {'HTTPHeaders': {'connection': 'keep-alive',
                                      'content-length': '422',
                                      'content-type': 'application/json',
                                      'date': 'Sat, 21 Jan 2017 10:44:16 GMT',
                                      'x-amzn-requestid': '8e4e8d80-dfc6-11e6-a24f-b522455ea1d2'},
                      'HTTPStatusCode': 200,
                      'RequestId': '8e4e8d80-dfc6-11e6-a24f-b522455ea1d2',
                      'RetryAttempts': 0}}
(Pdb)

diff --git a/c7n/mu.py b/c7n/mu.py
index 4525e30..4b5302e 100644
--- a/c7n/mu.py
+++ b/c7n/mu.py
@@ -960,6 +960,8 @@ class CloudWatchLogSubscription(object):
                 # iam eventual consistency and propagation
                 time.sleep(self.iam_delay)
             except ClientError as e:
+                extant = lambda_client.get_policy(FunctionName=func.name)
+                import pdb; pdb.set_trace()
                 if e.response['Error']['Code'] != 'ResourceConflictException':
                     raise
             # Consistent put semantics / ie no op if extant
diff --git a/tools/c7n_sentry/c7n_sentry/c7nsentry.py b/tools/c7n_sentry/c7n_sentry/c7nsentry.py
index b98786e..890aff8 100644
--- a/tools/c7n_sentry/c7n_sentry/c7nsentry.py
+++ b/tools/c7n_sentry/c7n_sentry/c7nsentry.py
@@ -456,7 +456,10 @@ def deploy(options):
         name='cloud-custodian-sentry',
         handler='handler.process_log_event',
         role='arn:aws:iam::644160558196:role/custodian-mu',
-        log_groups=[],
+        log_groups=[{
+            'logGroupName': '/aws/lambda/custodian-bar',
+            'arn': 'arn:aws:logs:us-west-2:644160558196:log-group::*'
+        }],
         project=None,
         account_name=None,
         account_id=None

JSON-decoded:
(Pdb) pp policy
{u'Id': u'default',
 u'Statement': [{u'Action': u'lambda:InvokeFunction',
                 u'Condition': {u'ArnLike': {u'AWS:SourceArn': u'arn:aws:logs:us-west-2:644160558196:log-group::*'}},
                 u'Effect': u'Allow',
                 u'Principal': {u'Service': u'logs.us-west-2.amazonaws.com'},
                 u'Resource': u'arn:aws:lambda:us-west-2:644160558196:function:cloud-custodian-sentry',
                 u'Sid': u'aws-lambda-custodian-bar'}],
 u'Version': u'2012-10-17'}
(Pdb)

I don't see something in the policy that would vary such that it would cause the InvalidParameterException. Something else is going on ...

Like, what's the effect of the policy?

Ah! I bet it's SourceArn=group['arn'].

So I'm back to needing to determine the ARN for a log group, which there appears to be no UI for.

Guessed and confirmed via API:
arn:aws:logs:us-west-2:644160558196:log-group:/aws/lambda/custodian-bar:*

(cloud-custodian) $ c7n-sentry deploy -c config.json --region=us-west-2
2017-01-21 06:49:15,806: custodian.lambda:INFO Creating subscription filter for /aws/lambda/custodian-bar
(cloud-custodian) $

We have logs!

That's cloud-custodian-sentry picking up a log event from custodian-bar. 👍

No error! Is it in Sentry!?

Yes! 💃

Phew! Okay! The next step here is to unhardwire everything in 63ca909fd9f58f73ae3ba5b2281e2435d36e1f48.

A behavior I am seeing: I get an InvalidParameterException as before, but an immediate rerun succeeds:
(cloud-custodian) $ c7n-sentry deploy -c config.json --region=us-west-2
2017-01-23 04:21:16,897: custodian.lambda:INFO Creating subscription filter for /aws/lambda/custodian-bar
Traceback (most recent call last):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/bin/c7n-sentry", line 11, in <module>
    load_entry_point('c7n-sentry', 'console_scripts', 'c7n-sentry')()
  File "/Users/whit537/workbench/capitalone/cloud-custodian/tools/c7n_sentry/c7n_sentry/c7nsentry.py", line 504, in main
    options.command(options)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/tools/c7n_sentry/c7n_sentry/c7nsentry.py", line 461, in deploy
    manager.publish(func)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 249, in publish
    if e.add(func):
  File "/Users/whit537/workbench/capitalone/cloud-custodian/c7n/mu.py", line 970, in add
    destinationArn=func.alias or func.arn)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 251, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/whit537/workbench/capitalone/cloud-custodian/lib/python2.7/site-packages/botocore/client.py", line 537, in _make_api_call
    raise ClientError(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (InvalidParameterException) when calling the PutSubscriptionFilter operation: Could not execute the lambda function. Make sure you have given CloudWatch Logs permission to execute your function.
(cloud-custodian) $ c7n-sentry deploy -c config.json --region=us-west-2
2017-01-23 04:22:46,658: custodian.lambda:INFO Creating subscription filter for /aws/lambda/custodian-bar
(cloud-custodian) $

Alright, so I'm looking at how to utilize the orgreplay machinery with deploy, because presumably we want the same extraction of account into from config.json? And the same auto-creation of teams and projects?

What's up with calling process_log_group twice?

Hub and spoke.

Rebased and squashed. Was e7465e10df580f8137922af382d7fefbb41d8535.

Ready for review, @kapilt! :-)


Update font-iosevka to 1.11.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for your contribution,


trend analysis pickle bug

Hello,
i would like to test the project, espacially the topic extraction but when i run the command:
 python -m nlp_architect.solutions.trend_analysis.topic_extraction myfolder myfolder
i have this error:
INFO:main:extracting NPs
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/lib/python3.5/multiprocessing/pool.py", line 119, in worker
result = (True, func(*args, **kwds))
File "/home/nlp-architect/nlp_architect/solutions/trend_analysi
s/topic_extraction.py", line 52, in noun_phrase_extraction
np_app = NPScorer(parser=parser)
File "/home/nlp-architect/nlp_architect/solutions/trend_analysi
s/np_scorer.py", line 56, in init
self.nlp.add_pipe(NPAnnotator.load(_path_to_model, _path_to_params), last=Tru
e)
File "/home/nlp-architect/nlp_architect/pipelines/spacy_np_anno
tator.py", line 72, in load
model.load(_model_path)
File "/home/nlp-architect/nlp_architect/models/chunker.py", lin
e 213, in load
load_model(filepath, self)
File "/home/nlp-architect/nlp_architect/contrib/tensorflow/pyth
on/keras/utils/layer_utils.py", line 49, in load_model
model_data = pickle.load(fp)
_pickle.UnpicklingError: invalid load key, '<'.
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/nlp-architect/nlp_architect/solutions/trend_analysi
s/topic_extraction.py", line 331, in
main(args.target_corpus, args.ref_corpus, args.single_thread, args.no_train,
args.url)
File "/home/nlp-architect/nlp_architect/solutions/trend_analysi
s/topic_extraction.py", line 301, in main
result_t = run_np_t.get()
File "/usr/lib/python3.5/multiprocessing/pool.py", line 608, in get
raise self._value
_pickle.UnpicklingError: invalid load key, '<'.
I am on google compute engine, ubuntu 16.04.
Any idea in order to fix this ?
Thank you !

Hi, I'm guessing you got this issue because the model file downloaded is not valid.
Please remove  files from /nlp-architect/chunker-pretrained (this is the directory where the model is downloaded) and try running again.

Hi @peteriz , I faced the same issue. After removing the pretrained chunker folder - I still get the same error. It is able to successfully download the model and still runs into the pickle error.


Wrong stack pointer offset in objc_msgSend.aarch64.S leads to register corruption

I was working on a test to fix this and stumbled upon #264. This was not trivial to find, as it was causing some random exceptions in libs-base.
diff --git a/objc_msgSend.aarch64.S b/objc_msgSend.aarch64.S
index 25cbfd6..e9e30ba 100644
--- a/objc_msgSend.aarch64.S
+++ b/objc_msgSend.aarch64.S
@@ -169,7 +169,7 @@ CDECL(objc_msgSend_stret):
        EH_NOP
        ldp    x2, x3, [sp, #32]
        EH_NOP
-       ldp    x4, x5, [sp, #64]
+       ldp    x4, x5, [sp, #48]
        EH_NOP
        ldp    x6, x7, [sp, #64]
        EH_NOP

I'll make a PR with this fix and a unit test.

This was never triggered by the tests, because clang never generated objc_msgSend calls. We cannot call objc_msgSend manually, as this would use the variadic calling convention.
We can rerun objc_msgSend.m with -Xclang -fobjc-dispatch-method=non-legacy.


process_full_conus remove apply to get x,y points

radar_sites['proj_geom'].apply(lambda point: point.x)
can be simplified to
radar_sites['proj_geom'].x
Similarly with y

This would be a good thing to test...the intent with that step was to make sure a regular pandas Series was obtained and not a GeoSeries, as there were some issues with pickling the GeoSeries to send off to the dask workers. However, if this does work, that would be a good clean up (that whole script is due up for a good refactor anyway).

This would be a good thing to test...the intent with that step was to make sure a regular pandas Series was obtained and not a GeoSeries, as there were some issues with pickling the GeoSeries to send off to the dask workers. However, if this does work, that would be a good clean up (that whole script is due up for a good refactor anyway).


As a designer I need some recommendations for additional colours that may be used in visualizations (graphs, charts, KPI´s etc).

Propose functional colours  ´traffic light colours´. No other additional colors will be added.

Done by #980


added table of contents in the readme

Added table of contents
The section "convention for contributors" and "roadmap" were included in a code block. I went ahead and fixed it. Sorry if it was an intentional issue aimed at other beginner contributors but the table of contents would not detect that particular hyperlink if it was enclosed in a code block. If you want i could undo that particular mistake. Thanks.

I'm sure it wasn't intentional - I was in a hurry :)


I don’t know my encrypt password

Hdllo! I didn’t create encrypt password, why should I know it? I know my 12 words, what else do I need to send my funds?

Hi. Using your 12 words you could delete the wallet and import it again, this will clear the encrypt password. Check that your 12 words are correct before doing this ( maybe you could import the wallet in another device first just to be sure )

Hi. I,ve tried to imprt the wallet in another device and the result was that the wallet was imported, but without funds..
Alexey Z.
вторник, 18 августа 2020 г., 15:40 +0300 от<EMAIL_ADDRESS><EMAIL_ADDRESS>
Hi. Using your 12 words you could delete the wallet and import it again, this will clear the encrypt password. Check that your 12 words are correct before doing this ( maybe you could import the wallet in another device first just to be sure )
—
You are receiving this because you authored the thread.
Reply to this email directly,  view it on GitHub , or  unsubscribe .

Just clear your cache in advanced settings and funds will return

Hi. I,ve tried to imprt the wallet in another device and the result was
that the wallet was imported, but without funds..
On 20 Aug 2020 12:22 pm, "aminimus"<EMAIL_ADDRESS>wrote:

Hi. I,ve tried to imprt the wallet in another device and the result was
that the wallet was imported, but without funds..
Alexey Z.
вторник, 18 августа 2020 г., 15:40 +0300 от<EMAIL_ADDRESS><
<EMAIL_ADDRESS>
Hi. Using your 12 words you could delete the wallet and import it again,
this will clear the encrypt password. Check that your 12 words are correct
before doing this ( maybe you could import the wallet in another device
first just to be sure )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or unsubscribe .

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bitpay/copay/issues/11085#issuecomment-677267049, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKW6U2DKXZOUFAHKR45MAE3SBS6J7ANCNFSM4QCDLCHQ
.

This method doesn’t work

why is my key phrase is invalid?

I'm going to sue the app Copay

I'm going to sue the app Copay

@aminimus
we have developed our own hardware for cracking all versions of bitcoin wallet password with superfast speed
and if you still has problem I can help you run it. you can find my contact details on my profile
or you can send me message in telegram: @johnjames333 or gmail<EMAIL_ADDRESS>

@aminimus
I have a powerful platform which cracks bitpay password if you have some password hints. you can talk to me in telegrm. my telegram id is: walletrecover


Compatibility issue with Shizuku firmware v1.00.62 wrt. session elapsed time/Time Limit safety feature

A new version of the Shizuku firmware has just released (v1.00.62), which appears to have added support for PD3.1 EPR/AVS. I have not yet tested this functionality, but have noticed some potential problems while testing DingoCharge on the new firmware.
One issue I've found is that the elapsed time (and therefore, the speed in which the bottom statusbar rotates through its different reports) is advancing about 10 times as fast as it's supposed to, which also means that the Time Limit safety feature also expires 10 times as fast (default becomes 2.4 hours rather than 24 hours).  Accumulated charge/energy measurements seem to be unaffected.
Further testing will need to be done to see what/if any bugfixes/workarounds are available.

It appears that the Lua os.date() function was advancing 10 times as fast as it previously did, but the Shizuku sys.gTick() function was unaffected. This was determined to be the reason why timing functions that required sub-second resolution still functioned as intended.
Even if this issue is addressed in a future Shizuku firmware update, I have moved functions that relied on the coarse 1-second resolution timer to use a divided sys.gTick() instead. This will be part of the upcoming DingoCharge v1.6 release.

Issue fixed in version 1.6.0 (see https://github.com/ginbot86/DingoCharge-Shizuku/pull/19).


Update sbt to 1.3.12

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

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

labels: library-update, semver-patch

Codecov Report

Merging #1476 into master will decrease coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1476      +/-   ##
==========================================
- Coverage   85.89%   85.71%   -0.19%
==========================================
  Files          57       57
  Lines        2184     2184
  Branches      109      109
==========================================
- Hits         1876     1872       -4
- Misses        308      312       +4

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/shapes/SizedInstances.scala
78.57% <0.00%> (-14.29%)
:arrow_down:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
91.66% <0.00%> (-8.34%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
84.79% <0.00%> (-1.76%)
:arrow_down:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
93.97% <0.00%> (ø)

...les/core/shared/src/main/scala/io/circe/Json.scala
79.88% <0.00%> (+0.55%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0.00%> (+2.70%)
:arrow_up:

Continue to review full report at Codecov.

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


spotify-bug fix

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes:  #571

Type of change

[x ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)

Checklist:

[ x] I have made this from my own

[x ] I have taken help from some online resources

[x ] My code follows the style guidelines of this project

[x ] I have performed a self-review of my own code

[ x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@VidhiBhatt01  maam ,I  removed the previous pr and added this pr , it fulfills every condition told by you.

https://deploy-preview-622--amazing-js-projects.netlify.app/spotify clone/

Everything is perfect, except the responsiveness. You wanna fix it or shall I create a new issue for that?

Just merge it, I will create that issue and fix it in the shortest possible time.

@VidhiBhatt01 maam, merge it, i will make it responsive responsive the next issue in which i am assigned by you.

@mayank-del make it responsive in this PR no need to make another

@DEEPALI-SUK , please check it now, I have added everything told by you, now please make it level 3.

@VidhiBhatt01  maam , @DEEPALI-SUK maam and @arpit456jain  sir, I added everything , now merge it and please make it level 3 for responsiveness issue fixed.

@VidhiBhatt01 maam , @DEEPALI-SUK maam and @arpit456jain sir, I added everything , now merge it and please make it level 3 for responsiveness issue fixed.

@arpit456jain


Add neurite_volume_density feature to neurom.get.

Returns array with the volume density of each neurite. The
volume density is the ratio of neurite volume to neurite convex hull
volume.

@lidakanari Does this resolve #504? It gives you per-neurite densities.

Sure, looks good to me!

OK good. Note that this means you can get the values with morph_stats now.


KAFKA-9113: Fix system / unit tests

Address comments from previous PRs.
Rebase from trunk (primarily KIP-562).
Fix system tests.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Triggered three for previously failed ones:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/3721/
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/3722/
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/3723/

I'm merging this back to base now in order to trigger another unit / system directly, please feel free to continue reviewing and I will address comments in further PRs.


Index page and some testing tweaks

5bcb992 Create index frame and rename characterlist to match scheme
ba7c198 Implement a root route / for navigation
793c531 Remove default to all characters
8dbd03a Create dead-code scan script

Codecov Report

Merging #7 (5bcb992) into main (0b7f83c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage   99.83%   99.83%
=======================================
  Files          26       26
  Lines         601      608    +7
  Branches       47       47
=======================================
+ Hits          600      607    +7
  Partials        1        1

Flag
Coverage Δ

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

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

Impacted Files
Coverage Δ

eqcharinfo/route_handler.py
100.00% <ø> (ø)

eqcharinfo/api.py
100.00% <100.00%> (ø)

tests/api_test.py
100.00% <100.00%> (ø)

tests/route_handler_test.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add board definition for upcoming Pololu 3pi+ 2040 Robot

This is to support a new Pololu robot that will be released soon.  We have tested this file with C and Micropython, and it is working for us!

The robot is now up for sale:
https://www.pololu.com/product/5001
Please let me know if there's anything we need to do to get this merged!

hadn't seen it - please add our copyright, and whilst #pragma once is fine in general, perhaps match the style of everything other board header and use #ifndef

Okay, I updated it with something like what's at the top of the other ones.  Please let me know if you need anything else.


Server stops when right clicking Shield Block

RFTools Version: 3.31
CoFHCore Version: 3.0.3-303
CoFHLib Version: 1.0.3-175
mcjtylib Version: 1.3.0
Error log: https://gist.github.com/Ikabodo/21fc6c9371577cf874d8
Some dependency I'm missing?

Oops. I'll fix this

Will be fixed in next version (3.32)


Handle 'empty' transactions more careful to avoid crashing when STATEMENT binlog occurs

I have the following situation:

DB is located on Amazon RDS
Binlog is enabled and set to ROW format
Amazon RDS has their own table mysql.rds_heartbeat2, which is updated every several minutes (for replication purposes, I guess)
These changes get into binlog
Binlog format can be configured per session. When Amazon updates this table, they do it in 'STATEMENT' mode for some reason.
Therefore, binlog ends up with:

BEGIN
'Query' record, which modifies the table (INSERT INTO ... ON DUPLICATE KEY UPDATE ...)
COMMIT

Mypipe ignores that query record and fails, because it looks like an empty transaction, while it clearly is not.

Although it's possible to ensure that ROW format is used across the application, I doubt it's possible to convince Amazon to change their update mode (looks like it's explicitly specified and they should have reasons for that). So, my suggestion is to handle two cases:

Transaction which contains 'Query' statements, but no row updates. Make a separate overridable handler for them (which calls handleEventError by default), so user can ignore some of these transactions. I guess it's also a good idea to 'accumulate' queries of transaction (in a list of strings or something), so user have some information about it.
Other 'empty' transactions. Process as previously.

By the way, you can reproduce that problem locally by running that sequence of queries:
CREATE TABLE something_strange (value INT);
SET SESSION binlog_format = 'STATEMENT';
SET SESSION TRANSACTION ISOLATION LEVEL REPEATABLE READ;
INSERT INTO something_strange VALUES (1);

@yeputons take a look at 7b9fab1728950ab3c593bbd2d5a28aa46f48950c. Does that sort this issue out for you?

@mardambey I think so, thank you! Will try that tomorrow and close the issue if everything's ok.

@mardambey It works, I have several other suggestions:
Shouldn't quit-on-empty-mutation-commit-failure be true by default to be compatible with previous behavior?
I also don't think that logging unknown queries on 'warning' level is a good idea - sometimes they're totally legitimate and known. So, my suggestion is to do that only if no transaction is in progress. Otherwise, these queries will be processed by handleEmptyCommitError

@mardambey Thank you!


abnormal string input to js function

When the input contains special characters, the value of the input JS function does not meet the expectations.
example:
vm := goja.New()
_, err := vm.RunString("function sum(a) {return a.length;}")
if err != nil {
	panic(err)
}
sum, ok := goja.AssertFunction(vm.Get("sum"))
if !ok {
	panic("Not a function")
}
res, err := sum(goja.Undefined(), vm.ToValue(string([]byte{206, 176})))
if err != nil {
	panic(err)
}
fmt.Println(res)

the output is  1
i think 2 is as expected.

ECMAScript operates in UCS2, therefore the supplied string is converted from UTF-8 to UCS which in your case represents a single code unit. An equivalent JS code:
const b = new Uint8Array([206, 176]);
console.log(new TextDecoder('utf-8').decode(b).length);

which prints 1.


Support for Mermaid Diagram Rendering & Width Adjustment

I recently came across your userscript, and I must say it's truly impressive! I decided to fork it and experiment with a couple of enhancements:

Add support for Mermaid diagram rendering

Enable adjustable width

With the help of Claude, I was able to implement these features to a certain extent. However, given the complexity of the script, I'm not entirely confident about making pull requests directly. (It's quite hacky frankly.) I've made a few commits that reflect the modifications, which you can check out. It would be great if you could review them and consider integrating similar improvements into the main repository.

mermaid: https://github.com/jerrylususu/ChatGPT-Enhancements/commit/23d9602396d924a0cbd8f4be63835cb6904a429b
resize: https://github.com/jerrylususu/ChatGPT-Enhancements/commit/b9abe14d6162e6e031a874cc037ee08ffba0fed8

Thank you once again for creating such a useful script!

Hey! Thanks so much, I'll check it out! I've definitely been thinking about adding support for more types of artifacts!

Resizing already works btw, just a bit convoluted, you have to resize by clicking the top bar and then dragging that

Mermaid support added with https://github.com/MartianInGreen/ChatGPT-Enhancements/commit/f40e8d2dbe445527ee1095c36e4d4ee04907c387. :)


Add RISC-V clang build

Description
We add a RISC-V target. We are interested in higher-performance cores, so make sure that the vector extension is in place for this. The functionality is on par with aarch64 cross builds. CI is added as well. We assume that the RISC-V target has vector extensions enabled, and that this is at least 128-bits long. This is in line with RISC-V International guidelines that application class processors have a vector length >= 128-bits
There are some modifications of the toolchain that are required to get vector support up and running. In particular, a newer qemu is required, and this needs to be set up with binfmt support, as the deb package does not automatically setup binfmt.
Changes proposed:

Add ability to install LLVM from an upstream repo
Pass the architecture to install GNU cross-compilers to apt.sh
Add ability to install qemu from a Debian package
Add a file for setting up binfmt to run RISC-V binaries without specifying QEMU on the command line
Add clang CMake toolchain file for RISC-V
Add a CI pipeline for running and testing (under emulation) RISC-V builds using LLVM
Allow the architecture string in the PLATFORM variable to be more than 3 characters long, so that we can use riscv64 as the architecture name in the oneDAL build
Update openBLAS builds to use RISC-V optimized builds with 128-bit vector length
Add a precompile macro TARGET_RISCV64 to identify when the build is targeting RISC-V, in order to target RISC-V specific parts of the code base
Add structs, macros and enums, as per the SVE build, so that future commits can target specific micro-architectures more easily, and so that the current build completes for RISC-V
Add a cpu_vendor to all builds for riscv64
Add lnxriscv64 as a platform to use in the makefile

/intelci: run

/intelci: run

/intelci: run

@Alexandr-Solovev are there some things that need fixing? The public CI is green, and there aren't any outstanding comments


Pick assembly files based on tools, not targets

When deciding whether to use NASM assembly files or the GNU assembly
files it makes more sense to check the tool we're using to compile,
as tools are what ultimately what decide which format is supported and
accepted.
cc @Jake-Shadle

This is actually a bit confusing for me, shouldn't this be masm since those are Microsoft Assembly files? NASM to me means https://www.nasm.us/, which is close, but not compatible with MASM.

ah yeah, lets just say its a typo.


Naming conflict and inconvenient

Is there by any chance plans to change the class name to a unique name to the library to avoid having to scroll through multiple loggers just to import Kermit?
For now I workaround it by defining typealias Kermit = co.touchlab.kermit.Logger which definitely help, but im checking to see  If you are open to the idea of changing the name and if so,  I could support and open a PR.

Cheers

No plans for this as of now. Thanks for the suggestion.

I would add a note here. I definitely see that adding yet another "Logger" isn't great. The new version of Kermit has modules designed so that the actual "public" face of Kermit is a small library on top of kermit-core, which really does the heavy lifting. It would be fairly easy to write a duplicate of the kermit module, specific to what you need, and use kermit-core under that to provide the plumbing. We may be doing this in some cases as it can make config easier in some contexts.
See Logger in the repo. That module has very little in it. We've had various API requests that all can't really be done. For example, info instead of i for the logging name. We kind of need to pick one standard, for better or worse, but making a custom API on top should be pretty quick.


[RESTEASY-1955] - MicroprofileClientBuilder can't handle nested @BeanParam's

Resteasy issue: https://issues.jboss.org/browse/RESTEASY-1955
The verifyInterface() method in MicroprofileClientBuilder didn't take into account that @PathParam's can be also defined in the @BeanParam annotated class. Therefore this PR adds behaviour to populate @PathParam's from the @BeanParam as well in the verifyInterface() method.
Cherrypicked the https://github.com/resteasy/Resteasy/pull/1895 to the master branch as well.

Thanks @MMarus , I actually already cherrypicked your changes into master, see https://github.com/resteasy/Resteasy/commit/02afa0a1139cf37f8c76bf3a065d496c7fa4a629


Multiples Stores

Hello,
Is it possible to have more than one store in refile ?

? :)

You can probably write your own backend that does that ;)

Do you mean as in Store files in multiple backends? It should be fairly easy to do by writing a backend which composes multiple backends. I think this would actually be quite useful, and should be reasonably simple to do.

@jnicklas I originally thought it would be possible to support multiple backends by setting within the class, like this:
class Person
  attachment :profile_pic,
    cache: S3BackendSetter.new("bucket-for-profile-pics").cache,
    store: S3BackendSetter.new("bucket-for-profile-pics").store
end

class Import
  attachment :csv,
    cache: S3BackendSetter.new("bucket-for-csvs").cache,
    store: S3BackendSetter.new("bucket-for-csvs").store
end

class S3BackendSetter
  def new(bucket)
    @bucket = bucket
  end

  def cache
    Refile::S3.new(prefix: "cache", **aws_settings)
  end

  def store
    Refile::S3.new(prefix: "store", **aws_settings)
  end

  def aws_settings
    {
      access_key_id: ENV["AWS_ACCESS_KEY"],
      secret_access_key: ENV["AWS_SECRET_ACCESS_KEY"],
      region: "us-east-1",
      bucket: @bucket,
    }
  end
end

But I learned something interesting about Ruby. The default arguments on attachment.rb in Refile are symbols.
So if you do:
def hi(foo: :bar)
  p foo
end

# $ hi
# $ => :bar
# $ hi("baz")
# $ => ArgumentError: wrong number of arguments (1 for 0)

So it seems that as long as attachment.rb is disallowing cache/store to be set dynamically AND you set Refile.cache or Refile.store as class vars (not thread-safe), instead of instance vars (thread-safe), it's not possible to use multiple backends without a major re-write of the gem.
Maybe I'm missing something obvious, but those were my initial findings. I'm happy to help/contribute on allowing multiple backends. I would just need to know what strategy you prefer @jnicklas.

@taylorbrooks the original issue is about something entirely different: using multiple backends at the same time, which is quite different from using different backends for different models. The latter is already supported by Refile, and actually quite easy to do:
Register the backend with:
# note that the key should be a String, not a Symbol!
Refile.backends["my_cache"] = SomeBackend.new("...")
Refile.backends["my_store"] = SomeBackend.new("...")

And then use your backend like this:
class Person
  attachment :profile_pic, cache: "my_cache", store: "my_store"
end

@jnicklas Yeah, I'm a bonehead. I just realized I was my S3BackendSetter didn't have an #initialize method and was throwing that error.
I should write more tests. Thanks for the great gem!


clear policy errors

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/42765
PROPOSAL: https://github.com/Expensify/App/issues/42765#issuecomment-2137621022
Tests

Create a group chat
Rename the group to something invalid for example "adoadoadoajdoajdoadoajdoajadoadoadoajdoajdoadoajdoajadoadoadoajdoajdoadoajdoajadoadoadoajdoajdoadoaỏ"
Follow the RBR and remove the error message
Confirm RBR on LHN gets removed from LHN as well

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Create a group chat
Rename the group to something invalid for example "adoadoadoajdoajdoadoajdoajadoadoadoajdoajdoadoajdoajadoadoadoajdoajdoadoajdoajadoadoadoajdoajdoadoaỏ"
Follow the RBR and remove the error message
Confirm RBR on LHN gets removed from LHN as well

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/93134676/67a1e1bd-d3d0-44d9-bff0-5201175ea5d3

Android: mWeb Chrome
https://github.com/Expensify/App/assets/93134676/b7360ec4-ed5d-41c7-9726-a3e105c66492

iOS: Native

https://github.com/Expensify/App/assets/93134676/cb154aad-2e4b-4d1f-856c-4cbedf26b5c2

iOS: mWeb Safari

https://github.com/Expensify/App/assets/93134676/b537c21d-bcf4-4d46-8736-6c58e2535654

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93134676/a5fa5058-df36-4dfe-83c0-04841f3875cb

MacOS: Desktop

https://github.com/Expensify/App/assets/93134676/66fea514-57a6-4ce9-9c7c-54c0672fd0fd

@rojiphil what is your ETA for the checklist?

I can still reproduce this error with openReport. And I still think we need to investigate this.
Otherwise, we will get this behavior where the GBR will be shown for some time and disappear due to openReport call i.e. when the user navigates away and then navigates back to the same report .

@Nodebrute Ok. Let me check this again then.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/d1d68c9d-c89a-4f3a-a01a-8dd65f6c533d

MacOS: Desktop
https://github.com/user-attachments/assets/f299aa67-0f14-4230-84ea-9663fedc5b45

iOS: mWeb Safari
https://github.com/user-attachments/assets/ddb96064-ef74-4b90-bb88-2fe4086860b1

Android: Native
https://github.com/user-attachments/assets/b873b05c-1376-459c-bb79-b709b27120f8

Android: mWeb Chrome
https://github.com/user-attachments/assets/cd0659d7-f47b-4071-b8ed-ea78b29c9e3d

iOS: Native
https://github.com/user-attachments/assets/6872c7b2-1aa4-416c-a785-415eb02e8c8f

I can still reproduce this error with openReport. And I still think we need to investigate this.
Otherwise, we will get this behavior where the GBR will be shown for some time and disappear due to openReport call i.e. when the user navigates away and then navigates back to the same report .

@Nodebrute Ok. Let me check this again then with the latest.

We can ignore this as I also cannot reproduce this behaviour now.

@Nodebrute Regarding test steps, let us use numbers instead of bullet points. Also, we can remove the steps to go offline and come back again online as this issue can be reproduced even otherwise.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.11-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 9.0.11-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.11-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Nav bar is too wide on Android

For some reason the nav bar got wide on Android with the update—will add screenshot.

It should retain the default height when on Android only, for example:


Add auth patch

Issue #, if available:
Description of changes:
Added new patch to all versions
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


error on "refresh druid metadata": Duplicate entry for key 'uq_columns_column_name'

A clear and concise description of what the bug is.
Expected results
after add druid cluster, I click "refresh druid metadata" button, I wish the databases of druid cluster can merge into database.
Actual results
erro log:
Error while processing cluster 'zjy' (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (MySQLdb._exceptions.IntegrityError) (1062, "Duplicate entry 'industrylevel2-2022' for key 'uq_columns_column_name'") [SQL: 'INSERT INTO columns (created_on, changed_on, column_name, verbose_name, is_active, type, groupby, count_distinct, sum, avg, max, min, filterable, description, datasource_id, dimension_spec_json, created_by_fk, changed_by_fk) VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s)'] [parameters: (datetime.datetime(2019, 6, 12, 15, 18, 13, 148434), datetime.datetime(2019, 6, 12, 15, 18, 13, 148443), 'industrylevel2', None, 1, 'STRING', 1, 0, 0, 0, 0, 0, 1, None, 2022, None, 1, 1)] (Background on this error at: http://sqlalche.me/e/gkpj)
Screenshots

my druid cluster conf:

superset view :

superset log:

How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Environment
(please complete the following information):
CentoOS 6.3

superset version: superset version === 0.28.1
python version: python --version === 3.6.8
node.js version: node -v
npm version: npm -v

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Based on that error it looks like you may already have a column in the table 2022 called industrylevel2, check your underlying datasource to make sure you aren't trying to create another column with the same name.


"Error: cannot convert -4 to u32" (via Souffle translator)

The problem: running a Datalog analysis in Doop with DDlog fails with this error:
Error: cannot convert -4 to u32

I don't know if the error comes from subtraction or overflowing addition but there seems to be a misrepresentation of signed integers as unsigned ones. For example, in this test Souffle program:
.decl X(n: number)
.output X

X(10).
X(-1).

the souffle.dump output shows -1 as the maximum 32-bit unsigned integer:
RX{10}
RX{4294967295}

You can test it via Doop:
export DDLOG_DIR=path/to/differential-datalog
./doop -i http://centauri.di.uoa.gr:8081/artifactory/Demo-benchmarks/test-resources/006-hello-world-1.2.jar -a micro --id hello-world --Xstats-none --via-ddlog -Ldebug

I am also attaching the analysis logic.
gen_1272258801802673380.dl.zip

Thanks for reporting. As a matter of fact, we are working on adding proper support for signed integers to both DDlog and the souffle-to-ddlog converter right now. We'll try to get it to a state that will be enough to unblock you today.

Once merged this PR will provide support for negative literals: https://github.com/ryzhyk/differential-datalog/pull/238

@gfour, I get this error when running Doop. Any idea how to get around it?
./doop -i http://centauri.di.uoa.gr:8081/artifactory/Demo-benchmarks/test-resources/006-hello-world-1.2.jar -a micro --id hello-world --Xstats-none --via-ddlog -Ldebug
> Task :generateGrammarSource FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':antlr'.
> Could not resolve org.antlr:antlr4:4.5.1-1.
  Required by:
      project :
   > Could not resolve org.antlr:antlr4:4.5.1-1.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/org/antlr/antlr4/4.5.1-1/antlr4-4.5.1-1.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/org/antlr/antlr4/4.5.1-1/antlr4-4.5.1-1.pom'.
            > Connection reset
   > Could not resolve org.antlr:antlr4:4.5.1-1.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/org/antlr/antlr4/4.5.1-1/antlr4-4.5.1-1.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/org/antlr/antlr4/4.5.1-1/antlr4-4.5.1-1.pom'.
            > Connection reset
   > Could not resolve org.antlr:antlr4:4.5.1-1.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/org/antlr/antlr4/4.5.1-1/antlr4-4.5.1-1.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/org/antlr/antlr4/4.5.1-1/antlr4-4.5.1-1.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 4.5.1-1

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

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

@ryzhyk This sounds like a temporary network error with fetching dependencies via our own repo front end. I couldn't reproduce it but I added an explicit upstream repo to our build file. Can you pull the latest version of Doop and try again?

@gfour , thanks, it made some progress, but now I get more of the same:
> Could not resolve org.clyze:clue-common:3.8.41.
  Required by:
      project :
   > Could not resolve org.clyze:clue-common:3.8.41.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/org/clyze/clue-common/3.8.41/clue-common-3.8.41.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/org/clyze/clue-common/3.8.41/clue-common-3.8.41.pom'.
            > Connection reset
   > Could not resolve org.clyze:clue-common:3.8.41.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/org/clyze/clue-common/3.8.41/clue-common-3.8.41.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/org/clyze/clue-common/3.8.41/clue-common-3.8.41.pom'.
            > Connection reset
   > Could not resolve org.clyze:clue-common:3.8.41.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/org/clyze/clue-common/3.8.41/clue-common-3.8.41.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/org/clyze/clue-common/3.8.41/clue-common-3.8.41.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 3.8.41
> Could not resolve org.clyze:deepdoop:0.9.2.
  Required by:
      project :
   > Could not resolve org.clyze:deepdoop:0.9.2.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/org/clyze/deepdoop/0.9.2/deepdoop-0.9.2.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/org/clyze/deepdoop/0.9.2/deepdoop-0.9.2.pom'.
            > Connection reset
   > Could not resolve org.clyze:deepdoop:0.9.2.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/org/clyze/deepdoop/0.9.2/deepdoop-0.9.2.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/org/clyze/deepdoop/0.9.2/deepdoop-0.9.2.pom'.
            > Connection reset
   > Could not resolve org.clyze:deepdoop:0.9.2.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/org/clyze/deepdoop/0.9.2/deepdoop-0.9.2.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/org/clyze/deepdoop/0.9.2/deepdoop-0.9.2.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 0.9.2
> Could not resolve com.github.plast-lab:HeapDL:1.0.2.
  Required by:
      project :
   > Could not resolve com.github.plast-lab:HeapDL:1.0.2.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/com/github/plast-lab/HeapDL/1.0.2/HeapDL-1.0.2.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/com/github/plast-lab/HeapDL/1.0.2/HeapDL-1.0.2.pom'.
            > Connection reset
   > Could not resolve com.github.plast-lab:HeapDL:1.0.2.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/com/github/plast-lab/HeapDL/1.0.2/HeapDL-1.0.2.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/com/github/plast-lab/HeapDL/1.0.2/HeapDL-1.0.2.pom'.
            > Connection reset
   > Could not resolve com.github.plast-lab:HeapDL:1.0.2.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/com/github/plast-lab/HeapDL/1.0.2/HeapDL-1.0.2.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/com/github/plast-lab/HeapDL/1.0.2/HeapDL-1.0.2.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 1.0.2
> Could not resolve ext:sootclasses:3.1.0.MINIMAL.
  Required by:
      project :
   > Could not resolve ext:sootclasses:3.1.0.MINIMAL.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/sootclasses/3.1.0.MINIMAL/sootclasses-3.1.0.MINIMAL.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/sootclasses/3.1.0.MINIMAL/sootclasses-3.1.0.MINIMAL.pom'.
            > Connection reset
   > Could not resolve ext:sootclasses:3.1.0.MINIMAL.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/sootclasses/3.1.0.MINIMAL/sootclasses-3.1.0.MINIMAL.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/sootclasses/3.1.0.MINIMAL/sootclasses-3.1.0.MINIMAL.pom'.
            > Connection reset
   > Could not resolve ext:sootclasses:3.1.0.MINIMAL.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/sootclasses/3.1.0.MINIMAL/sootclasses-3.1.0.MINIMAL.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/sootclasses/3.1.0.MINIMAL/sootclasses-3.1.0.MINIMAL.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 3.1.0.MINIMAL
> Could not resolve ext:AXMLPrinter:2.0.
  Required by:
      project :
   > Could not resolve ext:AXMLPrinter:2.0.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/AXMLPrinter/2.0/AXMLPrinter-2.0.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/AXMLPrinter/2.0/AXMLPrinter-2.0.pom'.
            > Connection reset
   > Could not resolve ext:AXMLPrinter:2.0.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/AXMLPrinter/2.0/AXMLPrinter-2.0.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/AXMLPrinter/2.0/AXMLPrinter-2.0.pom'.
            > Connection reset
   > Could not resolve ext:AXMLPrinter:2.0.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/AXMLPrinter/2.0/AXMLPrinter-2.0.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/AXMLPrinter/2.0/AXMLPrinter-2.0.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 2.0
> Could not resolve ext:soot-infoflow:2.5.1.
  Required by:
      project :
   > Could not resolve ext:soot-infoflow:2.5.1.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/soot-infoflow/2.5.1/soot-infoflow-2.5.1.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/soot-infoflow/2.5.1/soot-infoflow-2.5.1.pom'.
            > Connection reset
   > Could not resolve ext:soot-infoflow:2.5.1.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/soot-infoflow/2.5.1/soot-infoflow-2.5.1.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/soot-infoflow/2.5.1/soot-infoflow-2.5.1.pom'.
            > Connection reset
   > Could not resolve ext:soot-infoflow:2.5.1.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/soot-infoflow/2.5.1/soot-infoflow-2.5.1.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/soot-infoflow/2.5.1/soot-infoflow-2.5.1.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 2.5.1
> Could not resolve ext:soot-infoflow-android:2.5.1.
  Required by:
      project :
   > Could not resolve ext:soot-infoflow-android:2.5.1.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/soot-infoflow-android/2.5.1/soot-infoflow-android-2.5.1.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/soot-infoflow-android/2.5.1/soot-infoflow-android-2.5.1.pom'.
            > Connection reset
   > Could not resolve ext:soot-infoflow-android:2.5.1.
      > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/soot-infoflow-android/2.5.1/soot-infoflow-android-2.5.1.pom'.
         > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/soot-infoflow-android/2.5.1/soot-infoflow-android-2.5.1.pom'.
            > Connection reset
   > Could not resolve ext:soot-infoflow-android:2.5.1.
      > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/soot-infoflow-android/2.5.1/soot-infoflow-android-2.5.1.pom'.
         > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-snapshot/ext/soot-infoflow-android/2.5.1/soot-infoflow-android-2.5.1.pom'. Received status code 400 from server: Repository version policy: SNAPSHOT does not allow version: 2.5.1
> Could not resolve ext:com.ibm.wala.util:1.5.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.util:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.util:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.util:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.util/1.5.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.core:1.5.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.core:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.core:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.core:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.core/1.5.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.shrike:1.5.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.shrike:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.shrike:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.shrike:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.shrike/1.5.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.dalvik:1.5.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.dalvik:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.dalvik:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.dalvik:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.dalvik/1.5.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.cast:1.5.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.cast:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.cast/1.5.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.cast.java:1.5.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.cast.java:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast.java:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast.java:1.5.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.cast.java/1.5.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.cast.python:0.0.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.cast.python:0.0.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast.python:0.0.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast.python:0.0.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.cast.python/0.0.1-SNAPSHOT/maven-metadata.xml
> Could not resolve ext:com.ibm.wala.cast.lsp:0.0.1-SNAPSHOT.
  Required by:
      project :
   > Could not resolve ext:com.ibm.wala.cast.lsp:0.0.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-deps/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast.lsp:0.0.1-SNAPSHOT.
      > Unable to load Maven meta-data from http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'http://centauri.di.uoa.gr:8081/artifactory/plast-public/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml'.
               > Connection reset
   > Could not resolve ext:com.ibm.wala.cast.lsp:0.0.1-SNAPSHOT.
      > Unable to load Maven meta-data from https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml.
         > Could not get resource 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml'.
            > Could not GET 'https://soot-build.cs.uni-paderborn.de/nexus/repository/soot-release/ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: ext/com.ibm.wala.cast.lsp/0.0.1-SNAPSHOT/maven-metadata.xml

I was not able to run Doop to reproduce the problem, but it should hopefully be fixed in the latest DDlog master. Can you give it a go and let us know what happens?

The analysis no longer crashes with a negative number error, thank you for the fast fix!

Great! It's a pretty complex Datalog program. Curious to know how DDlog does on it.

Great! It's a pretty complex Datalog program. Curious to know how DDlog does on it.

This analysis takes 50 sec in DDlog (vs. 11 in Souffle). These are preliminary results (still some things to verify, such as using the same subset of regex syntax between the two engines). For another measure of the work done by the analysis, here are the computed relation sizes:
Output relation         Tuples
ApplicationMethod            2
ArrayIndexPointsTo       17101
CallGraphEdge            14905
InstanceFieldPointsTo   887275
Reachable                 3328
StaticFieldPointsTo       2806
VarPointsTo            2085101

Interesting, thank you! Another important parameter is memory. Because DDlog is incremental, it (or rather differential-dataflow DDlog is built upon) maintains a bunch of state in memory.  This state can be fairly large and can also affect the performance due to swapping.  We are currently working on some optimizations to reduce the memory footprint. Any chance you could check how much memory DDlog uses in your example (I simply use /usr/bin/time to obtain peak memory usage of the program)?
If you are using DDlog as a standalone executable rather than through an API, then parsing a large dataset and dumping the output to file could take a long time (these operations are not really super optimized).
Finally, it would be interesting to look at DDlog's CPU and memory profiles to figure out where exactly it spends time and memory. To do so, add the following command at the start of the DDlog command file: profile cpu on; and use the profile; command at the very end to dump CPU and memory profiles (these commands are documented here)

Thanks! I would also try with a different number of workers. In my experience, -w 1 or -w 2 is typically faster than -w 4.

For this program, -w 2 takes about the same time (51 sec), while -w 1 takes 63 sec.


Ollama: add link to /models

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Use a stack to create walk nested templates

On the heels of #825, this unrolls our recursive template processor into a stack based one.

What's the pre and post PR code size?
As I mentioned in #825 I really don't care about optimizing the nested template case, so this is interesting to me if it improves the non-nested case (by eliminating the closure as it does) or reduces code size. Or if you have a specific use case for nested templates :)

30b larger, with marginal improvements in no-nested-templates case and large improvements in nested-templates case. https://jsbench.github.io/#e5870d1cf2df2701c83f0e17f0f3c067


Block action Cut wouldn't work in Firefox

Describe the bug
Block action Cut wouldn't work in Firefox
To Reproduce

Open block action menu, click the Cut

Expected behavior
No response
Additional context
No response
Logs/tracebacks
No response

Because Firefox does not support the ClipboardItem API, it is difficult to write rich text into Clipboard without an event.
We should hide Cut and Copy actions when there is no ClipboardItem API.


mq地址为域名时RebalanceService解析报错

https://github.com/apache/rocketmq/blob/a5d72be665f80487fd81e60604fac5c8e6a971ea/remoting/src/main/java/org/apache/rocketmq/remoting/common/RemotingHelper.java#L56
如地址为: http://xxx:8080/xxx
这段代码不能解析出正确的端口

tcp socket address,like ip:port(eg:<IP_ADDRESS>:8080),not http url pattern

If you want to use http for nameserver discovery,please see here.
    public static final String WS_DOMAIN_NAME = System.getProperty("rocketmq.namesrv.domain", DEFAULT_NAMESRV_ADDR_LOOKUP);
    public static final String WS_DOMAIN_SUBGROUP = System.getProperty("rocketmq.namesrv.domain.subgroup", "nsaddr");
    // http://jmenv.tbsite.net:8080/rocketmq/nsaddr
    public static final String WS_ADDR = "http://" + WS_DOMAIN_NAME + ":8080/rocketmq/" + WS_DOMAIN_SUBGROUP;

other wise please go to http://rocketmq.apache.org/docs/simple-example/ for message pub/sub usage documentation.

As @devsong said, this addr is a TCP socket address.
And the Apache RocketMQ community is global, we recommend using English as our preferred language~


[Android 8] the application crashes when trying to take a photo in landscape

reported by @KireinaHoro:matrix.org
https://github.com/matrix-org/riot-android-rageshakes/issues/796

duplicated of https://github.com/vector-im/riot-android/issues/1557