Beautify for php does not work

Description
The results of beautification are not what I expect. It always generates the php cs fixer path warning, although I have added it in settings and ensured it works.
Input Before Beautification
Included in debug.md
Expected Output
Should be formatted output as expected
Actual Output
It didn't work at all, with warning about cs fixer path.
Steps to Reproduce

Open php file
Run command Atom Beautify: Beautify Editor
Generates warning and does not beautify

Debug
Here is a link to the debug.md Gist: https://gist.github.com/Samnan/81a3c442a8f789bc8e22bba7fe372ae5
Checklist
I have:

[ x] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ x] Reloaded (or restarted) Atom to ensure it is not a caching issue
[ ]x Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ x] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ x] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

Within two minutes of submitting the bug, I got this email. The links given in the email point to some http://0.0.xxx.xxx domain. Is this some kind of malware?

Same Error Here:
`Could not find 'php-cs-fixer'. The program may not be installed.
See php-cs-fixer installation instructions at https://github.com/Glavin001/atom-beautify#beautifiers or go to https://github.com/FriendsOfPHP/PHP-CS-Fixer
Your program is properly installed if running 'which php-cs-fixer' in your Terminal returns an absolute path to the executable.
Error: Could not find 'php-cs-fixer'. The program may not be installed.
at Function.Executable.commandNotFoundError (/Users/mharding/.atom/packages/atom-beautify/src/beautifiers/executable.coffee:276:14)
at HybridExecutable.Executable.commandNotFoundError (/Users/mharding/.atom/packages/atom-beautify/src/beautifiers/executable.coffee:268:18)
at /Users/mharding/.atom/packages/atom-beautify/src/beautifiers/executable.coffee:196:22
at tryCatcher (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:689:18)
at Async._drainQueue (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:143:10)
at Async.drainQueues (/Users/mharding/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:17:14)
at process._tickCallback (internal/process/next_tick.js:103:7)`

Yes it is installed. I’m on a Mac.
Thank you,
Michael Harding
Senior Project Manager
Genesis Digital
(704) 727-8033 - Office
<EMAIL_ADDRESS><EMAIL_ADDRESS>- E-Mail
www.genesisdla.com - Website
On Tue, Aug 15, 2017 at 8:26 PM, szeck87<EMAIL_ADDRESS>wrote:

How did you install php-cs-fixer? Did you add it to your Windows
environment path?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Glavin001/atom-beautify/issues/1811#issuecomment-322624925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AINep9a2b54b1vtEUMv7rz_8Kz_eZEogks5sYjdBgaJpZM4O16h6
.

I hava a issue like this .
Could not find 'sqlformat'. The program may not be installed.
See sqlformat installation instructions at https://github.com/Glavin001/atom-beautify#beautifiers or go to https://github.com/andialbrecht/sqlparse
Your program is properly installed if running 'where.exe sqlformat' in your CMD prompt returns an absolute path to the executable.

@Samnan : Here is an extract from your logs:
2017-08-14T03:36:16.877Z - debug: [] spawn F:\Servers\AMPPS\php-cs-fixer.bat 0=fix, 1=--allow-risky=no, 2=--using-cache=no, 3=C:\Users\Sam\AppData\Local\Temp\temp117714-4908-1s4yyt3.3nm56ogvi.php
2017-08-14T03:36:19.642Z - debug: [] spawn done<PHONE_NUMBER>
C:\Users\Sam\AppData\Local\Temp>F:\Servers\AMPPS\php\php "F:/Servers/AMPPS/php-cs-fixer.phar" fix --allow-risky=no --using-cache=no C:\Users\Sam\AppData\Local\Temp\temp117714-4908-qbwl8a.clabdquxr.php

2017-08-14T03:36:19.642Z - verbose: [] spawn result, returnCode<PHONE_NUMBER>

It looks like Atom-Beautify ran correctly, and there was an error from within PHP-CS-Fixer with return code<PHONE_NUMBER>.
Here is the command Atom-Beautify used:
F:\Servers\AMPPS\php-cs-fixer.bat fix --allow-risky=no --using-cache=no FILE_NAME.php

I recommend trying it on the same file and confirming the expected result.

@mharding7va : Please follow the issue template provided. More specifically, adding a link to the required debug.md Gist which includes debugging information that answers our most commonly asked questions.
Thank you.

gem install rubocop


No need to include timestamp, already provided by clock

Substreams provide two native modules:

block
clock

which means every map module output already contains everything that's related to block number & timestamp by using clock.
The clock data can be extracted based on which sink needs that information, thus not being required in the map module outputs.
Scope

Remove timestamp from map modules
Add timestamp to graph_out using clock

Example
Using clock in graph_out
https://github.com/pinax-network/substreams-erc20-supply/blob/48dc84c5eddfe454fd0325c970bea162b1dfed46/src/sink.rs#L8C1-L24C2

Refactored with latest commit when writing this comment (https://github.com/pinax-network/substreams-atomicmarket-sales/commit/5ba31bb45352babe4ad6f101e299994f6f7c512c)


after disconnection, the Internet does not work, since the addresses of the dns servers change to <IP_ADDRESS> <IP_ADDRESS> and not revert to default

Which Cloudflare product(s) does this pertain to?
<IP_ADDRESS> WARP
Subject Matter
after disconnection, the Internet does not work, since the addresses of the dns servers change to <IP_ADDRESS> <IP_ADDRESS>
Content Location
after disconnection, the Internet does not work, since the addresses of the dns servers change to <IP_ADDRESS> <IP_ADDRESS> and not revert to default
Additional information
after disconnection, the Internet does not work, since the addresses of the dns servers change to <IP_ADDRESS> <IP_ADDRESS> and not revert to default

Additional information
after disconnection, the Internet does not work, since the addresses of the
dns servers change to <IP_ADDRESS> <IP_ADDRESS> and not revert to default
On Thu, 14 Jul 2022 at 13:12, AlexQuaken @.***> wrote:

Which Cloudflare product(s) does this pertain to?
<IP_ADDRESS>
Subject Matter
after disconnection, the Internet does not work, since the addresses of
the dns servers change to <IP_ADDRESS> <IP_ADDRESS>
Content Location
after disconnection, the Internet does not work, since the addresses of
the dns servers change to <IP_ADDRESS> <IP_ADDRESS> and not revert to default
Additional information
after disconnection, the Internet does not work, since the addresses of
the dns servers change to <IP_ADDRESS> <IP_ADDRESS> and not revert to default
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/cloudflare-docs/issues/5156, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNRQTLFU4XEJU544EJLAHLVT774HANCNFSM53SBMAVQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Sent from my iphone

Closing as this seems more a bug than documentation related. Thanks!


add this image full screen to the value of values slide

And also create a slide under close with this, which we will follow up with slide on our discussion site. Maybe you can come up with a screen shot of our discourse site for that too?
https://pixabay.com/en/milky-way-andromeda-stars-galaxy-923801/

Got it! See #100, commit d0fc0e7.
PR includes redpill (FRAG) notes and the above ticket. 🛠


[mgmt]: reconsider lro polling strategy to honour user input

Problem
We already have a customer issue regarding LRO in track1. The root cause is on the server side which doesn't return the correct Retry-After. However, retrospecting our track2 LRO implementation, there is one issue found: we totally ignore user input interval, thus in such cases there is no way for customers to work around.
Here is the RetryAfterDelayStrategy: https://github.com/Azure/azure-sdk-for-net/blob/8914c0e7076f82a95efa8a1d6cc955dd69b04c05/sdk/core/Azure.Core/src/Shared/RetryAfterDelayStrategy.cs#L41-L58
We choose the max value of Retry-After header and the fall-back strategy. And for mgmt, the fall-back strategy is ExponentialDelayStrategy: https://github.com/Azure/azure-sdk-for-net/blob/8914c0e7076f82a95efa8a1d6cc955dd69b04c05/sdk/core/Azure.Core/src/Shared/ExponentialDelayStrategy.cs#L40-L44
which ignores the user input. So there is no way for users to impact the polling interval, thus they lose the capability to remediate some cases.

After discussion, we recommend resolving the issue by polling control in client side. Below is an example.

var operation = await virtualNetworkCollection.CreateOrUpdateAsync(WaitUntil.Started, vnetName, vnet);
while (true)
{
    Thread.Sleep(TimeSpan.FromSeconds(30));
    await operation.UpdateStatusAsync();
    if (operation.HasCompleted)
    {
        break;
    }
}

One advantage of this solution is that for those sophisticated cases, simply honouring a constant value might not solve the problem. We already provide the API for developers to implement their own polling control. So probably the suggested changes above are not necessary.

we could enhance the doc here: https://github.com/Azure/autorest.csharp/issues/2286#issuecomment-1149540473

Has this issue been approved by .NET architects/Azure.Core team for use in data plane?


Add new API to determine whether GPU device is currently in standby(RC6) mode or not?

While initializing sysman using zesInit, sysman opens GPU device in order to collect some GPU data and then closes the device. After GPU device node is closed by UMD, device will take some time to enter to RC6 state.
Different GPU devices like ATSM/PVC etc might have different time to enter to RC6 state.
Now suppose user wants to collect some stats like power consumption when device is in idle state, then user first needs to know whether device is in idle state or not.
So, could we add some sysman API which could provide the device's current power state to user?
Other idea to provide such information to the user could be to add some event in event API which could help user in determining whether device entered to RC6 state or not? Currently we already have two events ZES_EVENT_TYPE_FLAG_DEVICE_SLEEP_STATE_ENTER and ZES_EVENT_TYPE_FLAG_DEVICE_SLEEP_STATE_EXIT which could provide an event to user whether device is about to enter/exit deep sleep state. Similarly could we add an event something like ZES_EVENT_TYPE_FLAG_STANDBY_ENTER/EXIT?

@sanilkumar0  please see above.


⚠ Bofrost.lu has degraded performance

In 82e8ae0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1636 ms

Resolved: Bofrost.lu performance has improved in ad1308c after 6 minutes.


Review use of dependency-injection module

The following script
from syringe import Inject
from devtools import debug

debug(Inject)

def foo():
    return 52

x = Inject(foo)
debug(x)
debug(Inject._dependencies)

outputs
syringe.py:61 _Inject.__init__
    'INIT' (str) len=4
x.py:4 <module>
    Inject: <syringe._Inject object at 0x7fd841228b50> (_Inject)
syringe.py:79 _Inject.__call__
    'CALL' (str) len=4
    _callable: <function foo at 0x7fd83f9a5a20> (function)
x.py:11 <module>
    x: 52 (int)
x.py:12 <module>
    Inject._dependencies: {} (dict) len=0

It looks to me and @ychiucco that this means that we are not using Inject at all!
Let's make sure that this is the case, and evaluate whether it's worth keeping this module (and what was its motivation in the first place).

The intended use case was related to

https://fastapi.tiangolo.com/advanced/settings/#settings-in-a-dependency
https://fastapi.tiangolo.com/advanced/testing-dependencies

Let's review this a bit and then check whether we can make things simpler (i.e. follow FasAPI docs rather than our custom solution).

I'm closing PR #891, since it's now fully out-of-date. That PR was the most complete attempt at fixing this issue (thanks @ychiucco!), and we should restart from it if we want to tackle this issue in the future.


Not returning anything

I tried a few slightly more complicated ideas, to access an objects sub-components.  Then I tried just returning a string:
return 'SomeText'
I tried giving the plugin readonly and then full rights with different API keys.  I've tried in chrome and firefox always the same an empty box.
This should be a really amazing adition.  Was hoping to use to make a api query on a datetime object and put write back a string of particular format.  If I can't even write back a string literal it's not looking so hopeful.

Hi @CraigChamberlain, Sorry to hear that it doesn't work for you. We have fixed a small bug regarding not updating data with a newly installed plugin. As soon as you can update or download version 1.2.2 that should be fixed.
I hope that will solve your problem.

Great, thanks velomovies.  It looks like the version available is still 1.2.1 not sure how/when the version number is bumped on dato?

Dato should pick up the new version automatically. That can take some time. I hope it will be updated in the next few days.

Hi @CraigChamberlain, you can now update the plugin to 1.2.2. Let us know if your issue is solved

This is all fine now.  However, it only works at all with development mode enabled.


Makefile: Remove the integration targets.

Description:
This would remove the integration-related Makefile targets as those are no longer used after the e2e rewrite has been merged.

Need to wait for https://github.com/openshift/release/pull/5925 to merge first.
/hold

/test all

/hold cancel

/lgtm
/approve


Additional Resources - don't include the current page

I like the idea of having the Additional resources section but it should not include a link to the same page that we are already on, in this case the Best Practices. It would be most helpful to include links to articles that are not immediately discoverable by scanning the contents links on the left.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 199fbc30-6751-5ee6-4fbb-f23f2f5137cc
Version Independent ID: 00bcc33c-c14b-fa5f-74ab-f1bd635dc043
Content: Best practices for using Azure Key Vault
Content Source: articles/key-vault/general/best-practices.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@DeanGross
Thanks for your feedback! We will investigate and update as appropriate.


Export-to-ExecuTorch via Optimum integration

Feature request
Feature request
Integrate ExecuTorch to `optimum, enabling an new "Export to ExecuTorch" workflow
Motivation
Enable a new e2e workflow for on-device ML use-cases via ExecuTorch
Your contribution
Drive initial integration
Provide default recipes for delegates, e.g. XNNPACK, CoreML, QNN, MPS, etc.

https://github.com/huggingface/optimum/pull/2090 is the initial integration to introduce ExecuTorch, the new backend for on-device ML via Optimum.


Update Login Screen UI

Why
In support of #2557, this issue aims to provide an initial task to help stakeholders get acclimated to the project.
Goal
Implement an updated login screen UI based on mockups by @AustinCondiff:
https://projects.invisionapp.com/share/3ATIRBHKW9F#/screens/380522637

Details

The mockup shows the Git Gateway password login screen - that UI comes from the netlify-identity-widget repo and is non-trivial to customize. Recommend considering that part out of scope for this issue.
Due to the previous point, a mockup should be made showing how the other backends, which currently consist only of a button instead of a form, should appear.
The current login components use some strange positioning, which led to https://github.com/netlify/netlify-cms/issues/2133 being opened. That issue can probably be resolved under this one.

Tasks

[ ] Create additional login screen mockup with oauth button in place of form - @AustinCondiff
[ ] Implement design and document related components in Storybook - @danoszz & @timmysmalls

Prerequisites

#3102

@timmysmalls I am ready to do a PR for this issue, how's stuff going with the external provider buttons? Can I assist with anything?
Once we have the buttons, we can resolve this issue 🏄♂

Our first Storybook component is alive 🎡

Closing as stale and/or outdated.


Location configuration not created under some circumstances

If your are using the latest image tag and recently updated your image: please make sure you've checked the required read on the project's README.
HTTPS does not work / certificate aren't created : please check in your letsencrypt-nginx-proxy-companion container logs if an authorization or verify error is mentioned, if it is please do the following before opening an issue:

check and follow the troubleshooting instructions in the docs.
search the existing similar issues, both opened and closed.

Bug description
I have 2 subdomains, one with and one without a config file in vhosts.d. When the containers are started as in the included docker-compose, only the subdomain with the config file gets the location configuration injected into it. the default file does not get it. To make things a little bit stranger, if add the environment variable to use the staging servers, all location configurations are injected and everything works. It only does not inject the configuration for default when using the production letsencrypt server.
letsencrypt-nginx-proxy-companion image version
Please provide the container version that should be printed to the first line of log at container startup:
Info: running letsencrypt-nginx-proxy-companion version v2.0.0-58-g8743298

nginx-proxy-companion configuration
docker-compose.yml
version: "3.8"

services:
  nginx-proxy:
    image: nginx
    container_name: nginx-proxy
    logging:
      driver: "json-file"
      options:
        max-size: "4m"
        max-file: "10"
    ports:
      - "80:80"
      - "443:443"
    restart: unless-stopped
    volumes:
      - conf:/etc/nginx/conf.d
      - html:/usr/share/nginx/html
      - certs:/etc/nginx/certs:ro
      - ./vhost.d:/etc/nginx/vhost.d

  nginx-proxy-gen:
    image: jwilder/docker-gen
    container_name: nginx-proxy-gen
    command: -notify-sighup nginx-proxy -watch -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
    logging:
      driver: "json-file"
      options:
        max-size: "2m"
        max-file: "10"
    restart: unless-stopped
    volumes:
      - conf:/etc/nginx/conf.d
      - certs:/etc/nginx/certs:ro
      - html:/usr/share/nginx/html
      - ./vhost.d:/etc/nginx/vhost.d
      - ./nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro

  nginx-proxy-le:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: nginx-proxy-le
    environment:
      NGINX_PROXY_CONTAINER: nginx-proxy
      NGINX_DOCKER_GEN_CONTAINER: nginx-proxy-gen
      DEFAULT_EMAIL<EMAIL_ADDRESS>    logging:
      driver: "json-file"
      options:
        max-size: "2m"
        max-file: "10"
    restart: unless-stopped
    volumes:
      - html:/usr/share/nginx/html
      - certs:/etc/nginx/certs:rw
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./vhost.d:/etc/nginx/vhost.d
      - acme:/etc/acme.sh

volumes:
  conf:
  html:
  certs:
  acme:

networks:
  default:
    external: true
    name: nginx-proxy

Containers logs
Please provide the logs of:

your letsencrypt-nginx-proxy-companion container
your nginx-proxy container (or nginx and docker-gen container in a three containers setup)

Failing log:
Info: running letsencrypt-nginx-proxy-companion version v2.0.0-58-g8743298
Generating a RSA private key
..............................................................++++
...................................................................................................++++
writing new private key to '/etc/nginx/certs/default.key.new'
-----
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
Info: a default key and certificate have been created at /etc/nginx/certs/default.key and /etc/nginx/certs/default.crt.
Info: Creating Diffie-Hellman group in the background.
A pre-generated Diffie-Hellman group will be used for now while the new one is being created.
Generating DH parameters, 2048 bit long safe prime, generator 2
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
2021/03/07 20:41:19 Generated '/app/letsencrypt_service_data' from 8 containers
2021/03/07 20:41:19 Running '/app/signal_le_service'
2021/03/07 20:41:19 Watching docker events
2021/03/07 20:41:19 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
[Sun Mar  7 20:41:21 UTC 2021] Create account key ok.
[Sun Mar  7 20:41:21 UTC 2021] Registering account: https://acme-v02.api.letsencrypt.org/directory
[Sun Mar  7 20:41:22 UTC 2021] Registered
[Sun Mar  7 20:41:22 UTC 2021] ACCOUNT_THUMBPRINT=''
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
Creating/renewal with-config.domain.com certificates... (with-config.domain.com)
[Sun Mar  7 20:41:24 UTC 2021] Using CA: https://acme-v02.api.letsencrypt.org/directory
[Sun Mar  7 20:41:24 UTC 2021] Creating domain key
[Sun Mar  7 20:41:28 UTC 2021] The domain key is here: /etc/acme.sh/**.**.com/with-config.domain.com/with-config.domain.com.key
[Sun Mar  7 20:41:28 UTC 2021] Single domain='with-config.domain.com'
[Sun Mar  7 20:41:28 UTC 2021] Getting domain auth token for each domain
[Sun Mar  7 20:41:30 UTC 2021] Getting webroot for domain='with-config.domain.com'
[Sun Mar  7 20:41:31 UTC 2021] Verifying: with-config.domain.com
[Sun Mar  7 20:41:34 UTC 2021] Success
[Sun Mar  7 20:41:34 UTC 2021] Verify finished, start to sign.
[Sun Mar  7 20:41:34 UTC 2021] Lets finalize the order.
[Sun Mar  7 20:41:34 UTC 2021] Le_OrderFinalize='https://acme-v02.api.letsencrypt.org/acme/finalize/114954757/8314335611'
[Sun Mar  7 20:41:35 UTC 2021] Downloading cert.
[Sun Mar  7 20:41:35 UTC 2021] Le_LinkCert='https://acme-v02.api.letsencrypt.org/acme/cert/03e6b07e0591fc014836fdb9e0400a6bd56f'
[Sun Mar  7 20:41:35 UTC 2021] Cert success.
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
[Sun Mar  7 20:41:35 UTC 2021] Your cert is in  /etc/acme.sh/**.**.com/with-config.domain.com.com/with-config.domain.com.com.cer
[Sun Mar  7 20:41:36 UTC 2021] Your cert key is in<EMAIL_ADDRESS>[Sun Mar  7 20:41:36 UTC 2021] The intermediate CA cert is in<EMAIL_ADDRESS>[Sun Mar  7 20:41:36 UTC 2021] And the full chain certs is there<EMAIL_ADDRESS>[Sun Mar  7 20:41:36 UTC 2021] Installing cert to:/etc/nginx/certs/with-config.domain.com/cert.pem
[Sun Mar  7 20:41:36 UTC 2021] Installing CA to:/etc/nginx/certs/with-config.domain.com/chain.pem
[Sun Mar  7 20:41:36 UTC 2021] Installing key to:/etc/nginx/certs/with-config.domain.com/key.pem
[Sun Mar  7 20:41:36 UTC 2021] Installing full chain to:/etc/nginx/certs/with-config.domain.com/fullchain.pem
Creating/renewal default.domain.com certificates... (default.domain.com)
[Sun Mar  7 20:41:37 UTC 2021] Using CA: https://acme-v02.api.letsencrypt.org/directory
[Sun Mar  7 20:41:37 UTC 2021] Creating domain key
[Sun Mar  7 20:41:40 UTC 2021] The domain key is here<EMAIL_ADDRESS>[Sun Mar  7 20:41:40 UTC 2021] Single domain='default.domain.com'
[Sun Mar  7 20:41:40 UTC 2021] Getting domain auth token for each domain
[Sun Mar  7 20:41:42 UTC 2021] Getting webroot for domain='default.domain.com'
[Sun Mar  7 20:41:42 UTC 2021] Verifying: default.domain.com
[Sun Mar  7 20:41:45 UTC 2021] default.domain.com:Verify error:Invalid response from http://default.domain.com/.well-known/acme-challenge/qkQOwj-jGdZNeSHFELIMCYDxfdfjKHBpUd6quxsGi9A [<IP_ADDRESS>]: 404
[Sun Mar  7 20:41:45 UTC 2021] Please check log file for more details: /dev/null
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
Sleep for 3600s
This is going to take a long time
Info: Diffie-Hellman group creation complete, reloading nginx.
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
2021/03/07 20:47:35 Received signal: terminated
2021/03/07 20:47:35 Received signal: terminated

Passing log (only change is setting environment variable for staging server):
Info: running letsencrypt-nginx-proxy-companion version v2.0.0-58-g8743298
Generating a RSA private key
........................................++++
.................................................................................................................................................................++++
writing new private key to '/etc/nginx/certs/default.key.new'
-----
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
Info: a default key and certificate have been created at /etc/nginx/certs/default.key and /etc/nginx/certs/default.crt.
Info: Creating Diffie-Hellman group in the background.
A pre-generated Diffie-Hellman group will be used for now while the new one is being created.
Generating DH parameters, 2048 bit long safe prime, generator 2
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
2021/03/07 20:48:12 Generated '/app/letsencrypt_service_data' from 8 containers
2021/03/07 20:48:12 Running '/app/signal_le_service'
2021/03/07 20:48:12 Watching docker events
2021/03/07 20:48:12 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
[Sun Mar  7 20:48:14 UTC 2021] Create account key ok.
[Sun Mar  7 20:48:14 UTC 2021] Registering account: https://acme-staging-v02.api.letsencrypt.org/directory
[Sun Mar  7 20:48:15 UTC 2021] Registered
[Sun Mar  7 20:48:15 UTC 2021] ACCOUNT_THUMBPRINT=''
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
Creating/renewal with-config.domain.com certificates... (with-config.domain.com)
[Sun Mar  7 20:48:17 UTC 2021] Using CA: https://acme-staging-v02.api.letsencrypt.org/directory
[Sun Mar  7 20:48:17 UTC 2021] Creating domain key
[Sun Mar  7 20:48:21 UTC 2021] The domain key is here: /etc/acme.sh/staging/with-config.domain.com/with-config.domain.com.key
[Sun Mar  7 20:48:21 UTC 2021] Single domain='with-config.domain.com'
[Sun Mar  7 20:48:21 UTC 2021] Getting domain auth token for each domain
[Sun Mar  7 20:48:23 UTC 2021] Getting webroot for domain='with-config.domain.com'
[Sun Mar  7 20:48:23 UTC 2021] Verifying: with-config.domain.com
[Sun Mar  7 20:48:27 UTC 2021] Success
[Sun Mar  7 20:48:27 UTC 2021] Verify finished, start to sign.
[Sun Mar  7 20:48:27 UTC 2021] Lets finalize the order.
[Sun Mar  7 20:48:27 UTC 2021] Le_OrderFinalize='https://acme-staging-v02.api.letsencrypt.org/acme/finalize/18444593/4141553'
[Sun Mar  7 20:48:28 UTC 2021] Downloading cert.
[Sun Mar  7 20:48:28 UTC 2021] Le_LinkCert='https://acme-staging-v02.api.letsencrypt.org/acme/cert/fa0f8f7ee39e032d08b65f8ba716c687f5c7'
[Sun Mar  7 20:48:29 UTC 2021] Cert success.
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
[Sun Mar  7 20:48:29 UTC 2021] Your cert is in  /etc/acme.sh/staging/with-config.domain.com/with-config.domain.com.cer
[Sun Mar  7 20:48:29 UTC 2021] Your cert key is in  /etc/acme.sh/staging/with-config.domain.com/with-config.domain.com.key
[Sun Mar  7 20:48:29 UTC 2021] The intermediate CA cert is in  /etc/acme.sh/staging/with-config.domain.com/ca.cer
[Sun Mar  7 20:48:29 UTC 2021] And the full chain certs is there:  /etc/acme.sh/staging/with-config.domain.com/fullchain.cer
[Sun Mar  7 20:48:29 UTC 2021] Installing cert to:/etc/nginx/certs/_test_with-config.domain.com/cert.pem
[Sun Mar  7 20:48:29 UTC 2021] Installing CA to:/etc/nginx/certs/_test_with-config.domain.com/chain.pem
[Sun Mar  7 20:48:29 UTC 2021] Installing key to:/etc/nginx/certs/_test_with-config.domain.com/key.pem
[Sun Mar  7 20:48:29 UTC 2021] Installing full chain to:/etc/nginx/certs/_test_with-config.domain.com/fullchain.pem
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
Creating/renewal default.domain.com certificates... (default.domain.com)
[Sun Mar  7 20:48:31 UTC 2021] Using CA: https://acme-staging-v02.api.letsencrypt.org/directory
[Sun Mar  7 20:48:31 UTC 2021] Creating domain key
[Sun Mar  7 20:48:35 UTC 2021] The domain key is here: /etc/acme.sh/staging/default.domain.com/default.domain.com.key
[Sun Mar  7 20:48:35 UTC 2021] Single domain='default.domain.com'
[Sun Mar  7 20:48:35 UTC 2021] Getting domain auth token for each domain
[Sun Mar  7 20:48:37 UTC 2021] Getting webroot for domain='default.domain.com'
[Sun Mar  7 20:48:37 UTC 2021] Verifying: default.domain.com
[Sun Mar  7 20:48:41 UTC 2021] Success
[Sun Mar  7 20:48:41 UTC 2021] Verify finished, start to sign.
[Sun Mar  7 20:48:41 UTC 2021] Lets finalize the order.
[Sun Mar  7 20:48:41 UTC 2021] Le_OrderFinalize='https://acme-staging-v02.api.letsencrypt.org/acme/finalize/18444593/4141704'
[Sun Mar  7 20:48:42 UTC 2021] Downloading cert.
[Sun Mar  7 20:48:42 UTC 2021] Le_LinkCert='https://acme-staging-v02.api.letsencrypt.org/acme/cert/fabcb27a3c0f4341071794101f6d247a1125'
[Sun Mar  7 20:48:43 UTC 2021] Cert success.
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
[Sun Mar  7 20:48:43 UTC 2021] Your cert is in  /etc/acme.sh/staging/default.domain.com/default.domain.com.cer
[Sun Mar  7 20:48:43 UTC 2021] Your cert key is in  /etc/acme.sh/staging/default.domain.com/default.domain.com.key
[Sun Mar  7 20:48:43 UTC 2021] The intermediate CA cert is in  /etc/acme.sh/staging/default.domain.com/ca.cer
[Sun Mar  7 20:48:43 UTC 2021] And the full chain certs is there:  /etc/acme.sh/staging/default.domain.com/fullchain.cer
[Sun Mar  7 20:48:43 UTC 2021] Installing cert to:/etc/nginx/certs/_test_default.domain.com/cert.pem
[Sun Mar  7 20:48:43 UTC 2021] Installing CA to:/etc/nginx/certs/_test_default.domain.com/chain.pem
[Sun Mar  7 20:48:43 UTC 2021] Installing key to:/etc/nginx/certs/_test_default.domain.com/key.pem
[Sun Mar  7 20:48:43 UTC 2021] Installing full chain to:/etc/nginx/certs/_test_default.domain.com/fullchain.pem
Reloading nginx docker-gen (using separate container nginx-proxy-gen)...
Reloading nginx (using separate container nginx-proxy)...
 Could you provide the configuration for your proxied containers as well (both the failing and passing ones) ?

docker-compose for the container that always passes:
version: "3.8"

services:
  ender4:
    image: nginx
    container_name: nginx-ender4
    environment:
      VIRTUAL_HOST: with-config.domain.com
      LETSENCRYPT_HOST: with-config.domain.com
    logging:
      driver: "json-file"
      options:
        max-size: "4m"
        max-file: "10"
    restart: unless-stopped
    volumes:
      - ./default.conf:/etc/nginx/conf.d/default.conf
      - ./htpasswd:/etc/nginx/conf/htpasswd

networks:
  default:
    external: true
    name: nginx-proxy

with-config.domain.com in vhost.d:
client_max_body_size 20M;

docker-compose for container that fails on production uri:
version: "3.8"

services:
  valheim-monitor:
    image: chainsdd/valheim-monitor
    container_name: valheim-monitor
    environment:
      VIRTUAL_HOST: default.domain.com
      LETSENCRYPT_HOST: default.comain.com
      SERVER_HOST: valheim-plus
      PORT: 80
    networks:
      - valheim
      - proxy
    restart: unless-stopped

networks:
  valheim:
    external: true
    name: valheim
  proxy:
    external: true
    name: nginx-proxy

The failing container does not have a matching file in vhost.d, but a blank default exists.

Ooh, this one is nasty. Here's what happens:
add_location_configuration calls enumerate_wildcard_locations
enumerate_wildcard_locations is intended to output a bunch "" strings, but because of the double quotes actually does shell expansion. (In other words, instead of ".bar.baz.example.com" it outputs "file1.bar.baz.example.com", "file2.bar.baz.example.com", etc.)
The script runs out /etc/nginx/certs, so it's actually enumerating all existing letsencrypt hosts. In the example, "default.domain.com" will wildcard expand "*.domain.com" to "with-config.domain.com".
A wildcard enumeration is considered to be a match if a vhost.d file exists ... which is true in this case. The result of this match is to override the domain, so "default.domain.com" becomes "with-config.domain.com".
After this, everything is pretty much a failure because all of the re-routing for the challenge files is happening on another domain.

@LoganK nice catch. Do you wish to submit a fix PR ?

I've tried a few techniques, but only set -f works for me. Happy to send shortly.

Just escaping the star char with \ should work in theory, it did not ?
I'd prefer set -o noglob / set +o noglob rather than set -f / set +f, I think the intent is more explicit this way (the former is just an alias of the latter).

Just escaping the star char with \ should work in theory, it did not ?

It did not. If you include the escape, then it survives into wildcard_domain and the file test fails.
(Setting up the appropriate conditions in the test case so I can easily repeat, which is why I haven't sent something yet. I'll iterate on various options at that point.)

I'd prefer set -o noglob / set +o noglob

Ack.


Add stress test for FS in guest VM

This patch adds a test to Eden that "stress" the filesystem on the guest VM using the ffsstress utility from the LTP package.
The test is started with the following command:
./eden test ./tests/fsstress

Please provide Readme, you can put several words from the description of the PR, just to keep it inside project.


Load balances of (imported) account

implement BinanceClient of asgardex-binance properly

Resolved by #210 #234


LCFS - Sign and Send Transfer without having to save a draft first

Describe the task
For a BCeID user with the transfer and Signing Authority roles to sign and send a transfer, they are currently required to save the transfer as a draft before the signing declaration is visible and the sign and send button is available (not greyed out).
BCeID users with the transfer and signing authority roles should be able to complete the signing declaration and the sign and send button should be available (not greyed out) without first saving a draft of the transfer.
Note: It is the Signing Authority role that is required to complete the signing authority declaration and be able to click on the sign and send button. The transfer role is required to create a new transfer; therefore, both roles are required (for different aspects) to create a new transfer and then sign and send it, all without saving a draft.
Note1: Signing Authority declaration should be visible for all BCeID users, but only the Signing Authority role can complete (check the box) the declaration.
Please see screenshot for current view:

Please see wireframe for what user should see:
https://preview.uxpin.com/59145260c7d8cc48969ac79401cc03d84843c3d9#/pages/164927056/simulate/sitemap
Acceptance Criteria

[ ] first
[ ] second
[ ] third

Additional context

Add any other context about the task here.
Or here

Can you look into a bug on the release branch when trying to sign and send a transfer directly from the new transfer page. There is a server error occurring on save.

Non-responsive sign and send button dealt with in card #489


cli_app.py:23: Перенести классы в отдельные файлы 8

The puzzle<PHONE_NUMBER>f from #899 has to be resolved:
https://github.com/blablatdinov/tg-quranbot/blob/ea15e984677c1c02034cd296d8c037c2bf036e67/src/services/cli_app.py#L23-L23
The puzzle was created by Ilaletdinov Almaz on 20-Jun-24.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle<PHONE_NUMBER>f has disappeared from the source code, that's why I closed this issue.


Add default capabilities for a Firefox

I saw these Chrome default capabilities:
https://github.com/minkphp/webdriver-classic-driver/blob/3a116f9a7369412bb210ce4ad272288b42d05356/src/WebdriverClassicDriver.php#L44-L49
Is it possible to add similar ones for the Firefox browser?

Note that these default capabilities are just to tweak the browser to behave as normally/standard as possible.
I looked into this, but it doesn't seem that Firefox displays an automation notification bar. Let me know if there is something in particular that should be fixed/changed!

I test too much in Chrome now. I had forgotten, that Firefox has a nice robot FavIcon and no banner to indicate it's being controlled from the outside.
Sorry for the false report.
Thank you.


Docstring + Swagger setup

Docstrings done. "Swagger setup" will be finished with the creation of Schemas, but seeing as those are a separate issue this one will be closed.


ìmage mod --label` change the config mediatype

Current Behavior
Using image mod to add or change labels of the image is changing the mediatype from application/vnd.docker.container.image.v1+json to application/octet-stream
regctl manifest diff localhost:5001/alpine:test localhost:5001/alpine --host tls=disabled,reg=localhost:5001
@@ -2,9 +2,9 @@
    "schemaVersion": 2,
    "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
    "config": {
-     "mediaType": "application/octet-stream",
-     "digest": "sha256:aae2036d9fac085bc134b1f6e66851e1679987bf4f02bbe52f8d9a61379c1c66",
-     "size": 610
+     "mediaType": "application/vnd.docker.container.image.v1+json",
+     "size": 1472,
+     "digest": "sha256:05455a08881ea9cf0e752bc48e61bbd71a34c029bb13df01e40e3e70e0d007bd"
    },

This might be the root cause of not being able to pull the modified image from kubernetes
Error: failed to create containerd container: error unpacking image: failed to extract layer sha256:5d12659955d5f1e588d826a8167277d9c3b4530db62e1ff82949b5ff621ff027: failed to get reader from content store: content digest sha256:1b95cff5bfd5d60f82ca7c9b10fec1caefa1caadbef690b9af7e5205a4df3e50: not found

Expected Behavior
The same media application/vnd.docker.container.image.v1+json and being able to pull from kubernetes
Steps To Reproduce
curl https://kind.sigs.k8s.io/examples/kind-with-registry.sh | bash

regctl image copy alpine localhost:5001/alpine --host tls=disabled,reg=localhost:5001
# or
docker tag alpine localhost:5001/alpine
docker push localhost:5001/alpine

regctl image mod localhost:5001/alpine --host tls=disabled,reg=localhost:5001 --label test=test --create test
regctl manifest diff localhost:5001/alpine:test localhost:5001/alpine --host tls=disabled,reg=localhost:5001

kubectl create deployment works--image=localhost:5001/alpine
kubectl create deployment doesntwork--image=localhost:5001/alpine:test

The kube part is normally reproductible ( my corporate network make it failed, i will update it from another computer) and should show pod from doesntwork not creating
Version
regctl version
VCSTag:     v0.5.7
VCSRef:     832109d4e9ef96982c4a4a8614b276b752509e5b
VCSCommit:  832109d4e9ef96982c4a4a8614b276b752509e5b
VCSState:   clean
VCSDate:    2024-02-06T21:25:52Z
Platform:   linux/amd64
GoVer:      go1.21.6
GoCompiler: gc

Environment

Anything else

Thank you for the report! That was a symptom of a bigger issue. I've got the fix ready to merge, just waiting on GitHub to recover from their issues.

So fast Thanks !


Add a "field" or two to the slack message with info about what repo haiku is from

See: https://api.slack.com/docs/message-attachments

This doesn't make sense anymore as you can add haikus not from a repository.


Depreciation messages in Chrome

Thanks for this lovely library. Just wanted to report that Chrome has started to warn about some depreciated apis.
[Deprecation] BiquadFilterNode.frequency.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed.
[Deprecation] BiquadFilterNode.Q.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed. See https://www.chromestatus.com/features/5287995770929152 for more details.
[Deprecation] OscillatorNode.frequency.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed. See https://www.chromestatus.com/features/5287995770929152 for more details.

I make an initial patch here https://github.com/zz85/nwc-viewer/commit/73d024827f8935fdf3e1a89f99befafafabee070


Unit tests ignore xunit.runner.json - Explains why the new stopOnFail setting wasn't working

See https://github.com/xunit/visualstudio.xunit/issues/189
Fix is to set xunit.runner.json to Copy On Newer:

(Adding this to UnitTests.csproj:
  <ItemGroup>
    <Content Include="xunit.runner.json" CopyToOutputDirectory="PreserveNewest" />
  </ItemGroup>

We can remove this line from ./UnitTests/AssemblyInfo.cs (it WAS what was preventing tests from running in parallel, but is no longer needed if xunit.runner.json is working):
// Since Application is a singleton we can't run tests in parallel
[assembly: CollectionBehavior (DisableTestParallelization = true)]

Once this is done, stopOnFail can be enabled by adding   "stopOnFail": true to xunit.runner.json.
I'd like to know if anyone has an objection to setting stopOnFail to true. I'd DEF want this for CI/CD, but am not sure if I like it for dev work.

There is situations which is preferable the unit tests stooped instead of some never end.

There is situations which is preferable the unit tests stooped instead of some never end.

Sorry @BDisp but I can't parse what you're saying? Can you try again?

Sorry @BDisp but I can't parse what you're saying? Can you try again?

I was referring that some unit tests fail silent and only opening the Tests on the drop down of the Output window we can verify there is an exception. But never mind.

Well I also agree with @tznind. If the intention is stop the tests when one of them fails, then we stop al  tests. I know running the tests in a command line the failed tests is only show when they finished, but we can do Ctrl+C to stop all. For CI/CD the @tznind suggestion is a good choice.

Cool. That's how we'll address this then.

I've also fixed this in #2612 so it will be picked up for v2 when I merge that.


Keyboard Input isn't processed properly on Android, but on iOS and Desktop

Bug - Keyboard Input isn't processed properly on Android, but on iOS and Desktop
I have the following two issues:

Issue 1: when the last paragraph of the imported (html, not delta) content is Bold I can only add 1 char in the next line. Then the editor looses its focus ==> .gif Example (droplr). Btw, it works if I switch the bold and not-bold text (.gif Example)
Issue 2: when there are two paragraphs, and the first one (also imported html) has the same setting, I can add a new line, but the second char-input jumps into the next line. ==> .gif Example (droplr)

Codepen

Issue 1: https://codepen.io/natterstefan/pen/veqOab
Issue 2: https://codepen.io/natterstefan/pen/MEMamV
Working Quill.js (no React Component) Example: https://codepen.io/natterstefan/pen/pWXjmO

Devices

iOS: it works without issues on my iPhone 6S Plus
Android: it does not work (eg. on Nexus 5X, or Pixel via Android Emulator)

FAQ
How do I access the wrapped Quill instance?
In the provided examples (eg. Codepen) I do not access it, just "listen" to the onChange and get its value there.
In our project we access it like this (abstract example):
 constructor(props, context) {
    super(props, context)
    this.quillRef = null      // Quill instance
    this.reactQuillRef = null // ReactQuill component
  }

 componentDidMount() {
    this.attachQuillRefs()
  }
  componentDidUpdate() {
    this.attachQuillRefs()
  }

  attachQuillRefs = () => {
    if (!this.reactQuillRef || typeof this.reactQuillRef.getEditor !== 'function') return
    this.quillRef = this.reactQuillRef.getEditor()
  }

  onChange() {
    // example
    console.log('onChange:', this.quillRef.getContents())
  }

 <ReactQuill
   ...props
   ref={(el) => { this.reactQuillRef = el }}
 />

Is there a bug in Quill?
Not sure yet, but I will test it, gonna add an Issue there too (if necessary) and link it here afterwards. In the meantime please check out my Codepens plase.
Update: I did not found a bug on their side. See the working Codepen (w/ Quilljs only) here.
React-Quill version

[x] 1.1.0

I can fix your first example by removing the inner div:
-

https://codepen.io/alexkrolick/pen/YEExeQ?editors=0010
Ultimately I think this is due to the .ql-cursor placeholder that gets inserted to preserve format across paragraph breaks interacting with the ReactDOM.clone and/or dangerouslyPasteHTML operations. Here is a related issue upstream: https://github.com/quilljs/quill/issues/1682

https://github.com/zenoamaro/react-quill/blob/2deb9ee16bce10dede7d5f522459539deee84d18/src/component.js#L339-L345

@alexkrolick thanks for your help and answer. At least the first issue should be resolved, I need to test it in our environment again.


fix: update author jinja command and add test

Types of changes

[ ] Hot fix (emergency fix and release)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation (change which affects the documentation site)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Release (develop -> main)

Quality assurance (all should be covered).

[ ] My code follows the code style of this project.
[ ] Documentation for my change is up to date?
[ ] My PR meets testing requirements.
[ ] All new and existing tests passed.
[ ] All commits are signed-off.

Summary
fix for: https://github.com/IBM/compliance-trestle/issues/1342
Key links:

Sonar coverage

Before you merge

Ensure it is a 'squash commit' if not a release.
Ensure CI is currently passing
Check sonar. If you are working for a fork a maintainer will reach out, if required.

@srmamit I´m just reviewing right now formatting, executing the code and tests and providing first line feedback.
It is required to fill out the quality assurance items, so please do as required.
Thanks


Merging first version

first library version working with test, travis and codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f577b34). Click here to learn what that means.
The diff coverage is 96.87%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   96.87%
=========================================
  Files             ?        1
  Lines             ?       32
  Branches          ?       16
=========================================
  Hits              ?       31
  Misses            ?        1
  Partials          ?        0

Impacted Files
Coverage Δ

src/Dropdown.js
96.87% <96.87%> (ø)

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 f577b34...d2b0cdf. Read the comment docs.


misc: add missing vars for https configuration to README

Fixed #198

@csutherl :facepalm:  (updated with missing infos from the role)


error when installing mono

x64@Ubuntu16:~/app/SysmonForLinux/build$ sudo apt-get install monodevelop
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
monodevelop : Depends: mono-runtime-sgen but it is not going to be installed
Depends: fsharp but it is not going to be installed
Depends: mono-runtime (>= 3.0~) but it is not going to be installed
Depends: libc6 (>= 2.27) but 2.23-0ubuntu11.3 is to be installed or
libc6.1 (>= 2.27) but it is not installable or
libc0.1 (>= 2.27) but it is not installable
Depends: libfontconfig1 (>= 2.12) but 2.11.94-0ubuntu1.1 is to be installed
Depends: libfsharp-core4.5-cil (>= 4.5) but it is not going to be installed
Depends: libglade2.0-cil (>= 2.12.45) but it is not going to be installed
Depends: libglib2.0-0 (>= 2.56.4) but 2.48.2-0ubuntu4.8 is to be installed
Depends: libglib2.0-cil (>= 2.12.45) but it is not going to be installed
Depends: libgtk2.0-cil (>= 2.12.45) but it is not going to be installed
Depends: libmono-cairo4.0-cil (>= 3.2.1) but it is not going to be installed
Depends: libmono-corlib4.5-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-microsoft-csharp4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-microsoft-web-infrastructure1.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-posix4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-componentmodel-composition4.0-cil (>= 3.0.6) but it is not going to be installed
Depends: libmono-system-componentmodel-dataannotations4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-configuration4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-core4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-data-entity4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-data-linq4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-data4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-design4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-drawing4.0-cil (>= 3.0.6) but it is not going to be installed
Depends: libmono-system-identitymodel4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-io-compression4.0-cil (>= 3.2.1) but it is not going to be installed
Depends: libmono-system-net-http4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-numerics4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-runtime-caching4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-runtime-serialization4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-system-runtime4.0-cil (>= 2.10.1) but it is not going to be installed
Depends: libmono-system-security4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-servicemodel4.0a-cil (>= 3.2.3) but it is not going to be installed
Depends: libmono-system-web-extensions4.0-cil (>= 2.10.3) but it is not going to be installed
Depends: libmono-system-web-services4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-web4.0-cil (>= 2.10.3) but it is not going to be installed
Depends: libmono-system-windows-forms4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-xaml4.0-cil (>= 1.0) but it is not going to be installed
Depends: libmono-system-xml-linq4.0-cil (>= 3.0.6) but it is not going to be installed
Depends: libmono-system-xml4.0-cil (>= 3.12.0) but it is not going to be installed
Depends: libmono-system4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed
Depends: libmono-windowsbase4.0-cil (>= 3.0.6) but it is not going to be installed
Depends: libpango-1.0-0 (>= 1.40.14) but 1.38.1-1 is to be installed
Depends: libpangocairo-1.0-0 (>= 1.40.14) but 1.38.1-1 is to be installed
Depends: monodoc-base (>= 3.2.1) but it is not going to be installed
Depends: msbuild but it is not going to be installed
Recommends: libgtk2.0-cil-dev but it is not going to be installed
Recommends: mono-devel but it is not going to be installed
Recommends: xamarin-gtk-theme but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
x64@Ubuntu16:~/app/SysmonForLinux/build$
hello developer,I have no idea why i can't install monodevelop,maybe beacause i installed wine and sourceInsight before...
i try this method but it still doesn't work:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update

If  you are using Ubuntu 16.04 which is End Of Life, you should first switch to a more recent release.
Very unlikely to be supported.
18.04 seems the target if source build.
18.04 or 20.04 if using pre-built packages


Fix for Stripe Customer ID

Fixed variable assignment issue with stripe customer ID.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for opening the PR @farookibrahim. Could you apply black formatting to your changes? Currently this one linter fails in CI.

@maarcingebala I applied black formatting now.

@farookibrahim It looks good now! Thank you for contributing to Saleor 🎉


CI cleaning

This PR is to clean up CI a bit, and separate out some tests into their own files. It also adds a RustFmt check.
Specifically, all of the tests for postgres/mysql/sqlite were all moved to respective test files (postgres.yml for example). All of the general unit tests, clippy, and other generic items were added to a rust-ci.yml file.

We can give it a try. But let's put rust fmt before everything so it fails fast.
The current workflow also have two stages, so if compilation fails, subsequent tests would abort.
I tried to look for a combined status badge for all workflows, but couldn't.

So we basically keep the unified old workflow and add a cargo fmt stage before it :P

I guess it wouldn't be the best, you could see the rendered version here.


Add Solutions for 'Buffer Not Found' Issue in React

Description:
This PR adds three solutions to address the 'Buffer not found' issue in React applications, particularly for projects created with Create React App (CRA). The update includes methods using CRACO, React-App-Rewired, and the Eject option, providing users with different levels of customization for webpack configuration.
Changes:

CRACO: Instructions and code for setting up CRACO to modify webpack config without ejecting.
React-App-Rewired: Guide and configuration details for using react-app-rewired.
Eject Method: Steps for ejecting from CRA and manually adjusting webpack.config.js.

Preview

Suggestions implemented in the last commit.


Allow upwards flexible versioning

This allows use with newer React versions. Quick spin with React 0.12.2 didn't show any problems.
Fixes #2

Please, merge this pull request.

+1

+1

+1

+1

+1

So, effectively, this project is dead. Too bad. It would only take a second to fix it.

True. A possibility for now is to use the fork.

I think it's pretty clear that the author has abandoned this project and a it should be forked. Volunteers?


Adding lookup tables to created linkages that are not spatial

The intention of this PR is to join Classes that do and don't have a spatial aspects to them.   Is it the grids they operate or a service area?  This bypasses that question by linking utilities with the communities they serve.

Looks good!


libm's functions

Rust's libm provides many of the functions described in jq's manual, with some exceptions (e.g. gamma). However, the manual states that availability depends on the system, since they're linked to the C standard library:

Unavailable math functions will be defined but will raise an error.

Should jaq do the same, always failing on functions that aren't defined in libm?
Also, and since including these would add another dependency, should they be feature-gated in jaq?

Should jaq do the same, always failing on functions that aren't defined in libm?

Yes, that sounds reasonable.

Also, and since including these would add another dependency, should they be feature-gated in jaq?

No, they should be unconditionally enabled, like regex (and soon time).

Should jaq do the same, always failing on functions that aren't defined in libm?

Yes, that sounds reasonable.

Oh, sorry, I misunderstood. You were referring to Rust's libm, not the system libm.
In that case, I would only define those functions as filters which are implemented in Rust's libm.


Parallelize the test runs via pytest-xdist

Summary of changes
This is a demo showing how using pytest-xdist affects the test runs.
Resolves #2458
Performance improvements
Comparing before/after, this patch makes the jobs run 2x faster in the CI and 4x faster locally.

main
this PR

py36/ubuntu-latest
240.99s  (0:04:00)
137.93s (0:02:17)

pypy3/macos-latest
1642.34s (0:27:22)
732.48s (0:12:12)

Pull Request Checklist

[x] Changes have tests
[ ] News fragment added in changelog.d/.
(See documentation for details)

This PR demonstrates both points raised in #2458:

There's some race condition supposedly because of insufficient test isolation
It's faster with xdist. Compare 233.77s (0:03:53) on master vs 105.42s (0:01:45) in this PR for the GHA ubuntu py3.8 job. (https://github.com/pypa/setuptools/runs/1419466762#step:17:1076 vs https://github.com/pypa/setuptools/pull/2459/checks?check_run_id=1419764437#step:17:2199)

setuptools/tests/test_build_meta.py::TestBuildMetaBackend::test_build_sdist_relative_path_import

This test seems to fail because pytest-xdists injects '' into sys.path (it's not there when I add -n 0 to disable it). But I've also noticed a chdir() call that is not thread-safe + a deprecated tmpdir fixture is used (it's recommended to use tmp_path instead).

setuptools/tests/test_build_meta.py::TestBuildMetaBackend::test_build_sdist_relative_path_import

This test seems to fail because pytest-xdists injects '' into sys.path (it's not there when I add -n 0 to disable it). But I've also noticed a chdir() call that is not thread-safe + a deprecated tmpdir fixture is used (it's recommended to use tmp_path instead).

I've already stumbled onto a use-case this breaks. I added a breakpoint() to the code to inspect something. Before adding xdist, such a breakpoint would enable me to begin inspecting the code at that point. With xdist, that causes the test suite to fail with a BdbQuit exception. The tests aren't just running in parallel, but they're being forked to other processes that don't have a terminal with which to interact.

I've already stumbled onto a use-case this breaks. I added a breakpoint() to the code to inspect something. Before adding xdist, such a breakpoint would enable me to begin inspecting the code at that point. With xdist, that causes the test suite to fail with a BdbQuit exception. The tests aren't just running in parallel, but they're being forked to other processes that don't have a terminal with which to interact.

I've already stumbled onto a use-case this breaks. I added a breakpoint() to the code to inspect something.

I don't have any particular insight into this, but I've recently been working on Django and they have a test runner that defaults to running the tests in parallel and explicitly throws an error if you run --pdb. Might be that you simply have to disable running in parallel if you want breakpoints. Seems like a fair trade to me, TBH. I run test suites much more frequently than I set breakpoints in them, and I usually only make the "can't debug under X condition" mistake once or twice per debugging session, for a large net savings of time.

I've already stumbled onto a use-case this breaks. I added a breakpoint() to the code to inspect something.

I don't have any particular insight into this, but I've recently been working on Django and they have a test runner that defaults to running the tests in parallel and explicitly throws an error if you run --pdb. Might be that you simply have to disable running in parallel if you want breakpoints. Seems like a fair trade to me, TBH. I run test suites much more frequently than I set breakpoints in them, and I usually only make the "can't debug under X condition" mistake once or twice per debugging session, for a large net savings of time.

@jaraco

I'd prefer if this could use pytest-enabler, because otherwise, it becomes difficult to turn this feature off or customize the setting for a particular run. e.g.:
[...]
I've already stumbled onto a use-case this breaks. I added a breakpoint() to the code to inspect something. Before adding xdist, such a breakpoint would enable me to begin inspecting the code at that point. With xdist, that causes the test suite to fail with a BdbQuit exception. The tests aren't just running in parallel, but they're being forked to other processes that don't have a terminal with which to interact.

In this cause, I normally use
$ tox -- -n0 -s path/to/test.py::test_something

-n0 disables xdist and makes it sequential + -s allows to use breakpoint() without pytest stealing stdin/stdout streams from you.
@pganssle

I don't have any particular insight into this, but I've recently been working on Django and they have a test runner that defaults to running the tests in parallel and explicitly throws an error if you run --pdb. Might be that you simply have to disable running in parallel if you want breakpoints.

I believe that it's a bit better with pure pytest: if you actually use --pdb and not breakpoint(), xdist will automatically disable the concurrency and turn the test run into sequential.
It'll error out, though, if you will attempt to force the concurrency:
$ pytest -n2 --pdb  # fails
[...]
ERROR: --pdb is incompatible with distributing tests; try using -n0 or -nauto.
$ pytest --pdb  # works

Seems like a fair trade to me, TBH. I run test suites much more frequently than I set breakpoints in them, and I usually only make the "can't debug under X condition" mistake once or twice per debugging session, for a large net savings of time.

My experience is about the same. I also occasionally do PYTHONBREAKPOINT=pudb.remote.set_trace and connect there via telnet in a separate terminal emulator tab.

@jaraco

I'd prefer if this could use pytest-enabler, because otherwise, it becomes difficult to turn this feature off or customize the setting for a particular run. e.g.:
[...]
I've already stumbled onto a use-case this breaks. I added a breakpoint() to the code to inspect something. Before adding xdist, such a breakpoint would enable me to begin inspecting the code at that point. With xdist, that causes the test suite to fail with a BdbQuit exception. The tests aren't just running in parallel, but they're being forked to other processes that don't have a terminal with which to interact.

In this cause, I normally use
$ tox -- -n0 -s path/to/test.py::test_something

-n0 disables xdist and makes it sequential + -s allows to use breakpoint() without pytest stealing stdin/stdout streams from you.
@pganssle

I don't have any particular insight into this, but I've recently been working on Django and they have a test runner that defaults to running the tests in parallel and explicitly throws an error if you run --pdb. Might be that you simply have to disable running in parallel if you want breakpoints.

I believe that it's a bit better with pure pytest: if you actually use --pdb and not breakpoint(), xdist will automatically disable the concurrency and turn the test run into sequential.
It'll error out, though, if you will attempt to force the concurrency:
$ pytest -n2 --pdb  # fails
[...]
ERROR: --pdb is incompatible with distributing tests; try using -n0 or -nauto.
$ pytest --pdb  # works

Seems like a fair trade to me, TBH. I run test suites much more frequently than I set breakpoints in them, and I usually only make the "can't debug under X condition" mistake once or twice per debugging session, for a large net savings of time.

My experience is about the same. I also occasionally do PYTHONBREAKPOINT=pudb.remote.set_trace and connect there via telnet in a separate terminal emulator tab.

Good points. I'm inclined to accept the detriments in favor of the benefits. I've also confirmed that simply passing --pdb to pytest disables xdist, so works to bypass the behavior. Also, with the use of pytest-enabler, -p no:xdist also works.

Good points. I'm inclined to accept the detriments in favor of the benefits. I've also confirmed that simply passing --pdb to pytest disables xdist, so works to bypass the behavior. Also, with the use of pytest-enabler, -p no:xdist also works.


Update CONTRIBUTING.md

[x] I'm ready to merge

What's the context for this pull request?
(this is a good place to reference any issues that this PR addresses)

What's new?

What should a reviewer feedback on?

Does anything need to be updated after merge?
(e.g the wiki or the WhitakerLab website)

Could anyone please review this?

Sorry for the delay, I don't think these commas improve the readability of the text, so I'll be closing this. Thank you so much for contributing!

Sorry for the delay, I don't think these commas improve the readability of the text, so I'll be closing this. Thank you so much for contributing!


azidentity: Adding SubjectName/Issuer support

Fixes #11874

It looks good, do you have a way to test that the header is correct?

The short and I would say is not a perfect way to test it. But what I was thinking about is maybe comparing the number of certificates in the slice and possibly encoding the certificate in the test and comparing it to the value in the header? That could be a way to test it. Also, just an FYI, I did manually perform a live test against AAD with this feature set and successfully authenticated since I received an access token in response.

Good idea on the test, and glad that the manual test worked.

Added the test! Could only check up to the JWT's header, since both the payload and signature have random or unique characters generated in them.


[EPIC] A collection of Interval arithmetic (not Intervals of time) improvements

Is your feature request related to a problem or challenge?
DataFusion contains a powerful general purpose interval arithmetic library, in intervals, first introduced in #5322
This library is currently used for statistic and selectivity estimation, and to provide additional guarantees during expression simplification.
This ticket tracks additional items needed to improve the sophistication of DataFusion in this regard

[ ] https://github.com/apache/arrow-datafusion/issues/7098
[ ] https://github.com/apache/arrow-datafusion/issues/7883
[ ] https://github.com/apache/arrow-datafusion/issues/7887

I am working on some new supports and improvements in interval arithmetic. I also plan to move the code into a more accessible place (possibly datafusion_expr). I will complete my work next week and link them here.

Thanks @berkaysynnada  -- note I just proposed three relatively small changes . Perhaps you have some time to look at them:

https://github.com/apache/arrow-datafusion/pull/7885
https://github.com/apache/arrow-datafusion/pull/7884
https://github.com/apache/arrow-datafusion/pull/7886

I also plan to move the code into a more accessible place (possibly datafusion_expr)

What would you think about making a datafusion-interval crate to hold the interval analysis library ? that would keep it nicely isolated and likely improve the development cycle time (I found it quite painful to work on in datafusion-physical-expr)

I also filed https://github.com/apache/arrow-datafusion/issues/7887

Thanks @berkaysynnada -- note I just proposed three relatively small changes . Perhaps you have some time to look at them:

Minor: Clarify Boolean Interval handling and verify it with a test #7885
Support Interval analysis for OR expressions #7884
Minor: Fix bug in AND interval analysis tests (not code), and add more coverage #7886

I also plan to move the code into a more accessible place (possibly datafusion_expr)

What would you think about making a datafusion-interval crate to hold the interval analysis library ? that would keep it nicely isolated and likely improve the development cycle time (I found it quite painful to work on in datafusion-physical-expr)

Thank you for the care and effort you have put into this issue. I tried to answer the current behavior and how it should actually be in the reviews you opened. However, as I mentioned in them, I am currently working on a comprehensive interval library update. It will eliminate many of the bugs you noticed and provide a more open, error-free API for users. I don't want to keep you waiting, but I think it will be easier to solve these issues after I quickly finalize my PR and present it to you.
As for making the new interval crate, it would be better to answer after discussing it with my teammates. Thanks again.

. I don't want to keep you waiting, but I think it will be easier to solve these issues after I quickly finalize my PR and present it to you.

There is no particular time pressure from my end. If you are working to revamp the code, I'll wait until that lands (and try to help review it promptly) and then we can pick up the PRs.
BTW is there a ticket somewhere that tracks what you plan to do (mostly I am thinking of any 'end user visible bugs/ behaviors' that might result)?

As for making the new interval crate, it would be better to answer after discussing it with my teammates. Thanks again.

Sounds good -- we can break it into a new crate at some later time too, if that is appropriate. There is no reason to do it as part of your in-filght refactoring

BTW is there a ticket somewhere that tracks what you plan to do (mostly I am thinking of any 'end user visible bugs/ behaviors' that might result)?

There is no ticket here but I can summarize them as follows:

Relocating the code.
Propagate arithmetic API change (the a-b<0 assumption will no longer be used for a<b propagation, which will also be useful for easy integration of supports such as OR).
Mul and Div support
Interval construct API (including checks)
The relationship of the next_value() function with infinite bounds.
I can open the PRs one by one, minimizing them and separating their concerns.

Sounds good -- we can break it into a new crate at some later time too, if that is appropriate. There is no reason to do it as part of your in-filght refactoring

👍


Copyedit_Overview

It would be great to loop in @ivypie for an SEO description and metadata title recommendation.

@vsyu -- let's track SEO optimization in a separate task.  For now in Q4, these recipes are going out in limited form.  In Q1 for the big launch, we can make sure to ask for @ivypie 's assistance.


textAlign style on  element gives Typescript error but works

Seems to be an issue with the typing.
If I do
<text style={{textAlign: "center"}}>
  some centered text
</text>

I get this Typescript error:
Type '{ textAlign: string; }' is not assignable to type 'Style'.
  Object literal may only specify known properties, and 'textAlign' does not exist in type 'Style'.  TS2322

but if I ignore it, the text is correctly centered.

Fixed in renderer v0.5.0.


Provide guidance on validating OpenAPI specs

Closes #125

Thoughts on this @fgheysels @MassimoC ?

Thoughts on this @fgheysels @MassimoC ?

Haven't taken the time yet to think about it.  Will do when I have some time to spare ...

No problem, thanks!


Adding a function that creates fixed length random number

This function creates a random number which is always no shorter (in terms of the number of digits) than the upper bound minus 1. For example if the upper bound is 100 then the random number will always be 2 digits long.
fixes #ISSUE_ID
:tada: Hi and welcome! Please read the text below and remove it - Thank you! :tada:
No worries if anything in these lists is unclear. Just submit the PR and ask away! :+1:

Things to check before submitting a PR

[ ] the tests are passing locally with cargo test
[ ] cookbook renders correctly in mdbook serve -o
[ ] commits are squashed into one and rebased to latest master
[ ] PR contains correct "fixes #ISSUE_ID" clause to autoclose the issue on PR merge

if issue does not exist consider creating it or remove the clause

[ ] spell check runs without errors ./ci/spellcheck.sh
[ ] link check runs without errors link-checker ./book
[ ] non rendered items are in sorted order (links, reference, identifiers, Cargo.toml)
[ ] links to docs.rs have wildcard version https://docs.rs/tar/*/tar/struct.Entry.html
[ ] example has standard error handling
[ ] code identifiers in description are in hyperlinked backticks

[`Entry::unpack`]: https://docs.rs/tar/*/tar/struct.Entry.html#method.unpack

Things to do after submitting PR

[ ] check if CI is happy with your PR

Thank you for reading, you may now delete this text! Thank you! :smile:

Thank you for your interest in the cookbook.  Please examine this recipe https://rust-lang-nursery.github.io/rust-cookbook/algorithms/randomness.html#generate-random-numbers-within-a-range  Notice the simplicity and the description with links that surround the code.
Additionally, we are looking for reusable components.  The primary purpose of the cookbook is to create things that we expect will have a high demand.  I can't think of a use case that warrants adding a loop checking length.
Again I appreciate your interest in the cookbook, but I don't see any value in adding another random generator to the cookbook.


[WIP] streaming version of select query

It is part of this discussion https://groups.google.com/d/msg/druid-development/FK5D162ao74/13F3ixfJEQAJ
This PR is a streaming version of select.
The query is similar to select query
{
    "queryType": "scan",
    "columns": [
        "q_sales","pv"
    ],
    "dataSource": "dws_tb_log_wl_100w_shard5",
    "limit": 10,
    "filter": {
        "dimension": "q_sales",
        "value": "55",
        "type": "selector"
    },
    "intervals": [
        "2015-01-01/2016-12-07"
    ]
}

The differences between select query and scan query, are

no pagingSpec, scan query reads events from the beginning to the end
select query returns 1 Object who contains a event list which is huge, like {[a,b,c,d,e,f,...]}, scan query returns list of small batch of events, like [ [a,b,c], [d,e,f], [...] ]
select query cost lots of memory because it has to buffer a huge list of events in memory, and flushes until the list is ready. scan query flushes when a small batch is ready, the client can get the batch while the server is preparing the next batch

It is tested by directly talking to historicals, and not fully tested from broker side.
Still on working:

respect timeout and cancel behavior like other queries (currently using qtp thread, then can't let the framework to manage timeout and cancel, is it better to use processing thread over qtp thread?)
exactly 'limit' from broker side

Do we need granularity for the scan query?

Can we do this by adding batchSize to existing select query?

Scan query is different from the select query in many ways, not only the batchSize thing.
Fg, the return structure, the way holding events in memory, the way handling merge results in toolchest.
Also scan query doesn't promise global ordering across segments according to query.decending to return response to client as soon as possible.
So I think it's better to create a new query type instead of reusing the select query.
@navis

Thanks @kaijianding for posting this!
To me, the differences (result format, lack of ordering, different processing style) are substantial enough that this should be a different query type from select.
we might also want to:

Remove the dimension/metric distinction, so the user can just ask for "columns". The dimension/metric split really only makes sense if we're aggregating, and Scan does not aggregate. The return format could be dictated either by the underlying column type and possibly overridden by a hint provided by the user. I'm not sure if we need to support extractionFns, but if we do, they could be provided explicitly instead of as part of DimensionSpecs. (that way, they'd even work on non-string columns!)

Maybe or maybe not keep "granularity", although if we do keep it, I think we shouldn't pass it to makeCursors. I think we only need to use it to truncate timestamps in the returned rows, and if so then splitting up the cursors by granularity bucket is extra overhead.

Would be nice to do what we need to do (if anything) to enable a future format change for the batches from JSON/Smile arrays into column-oriented binary form like Arrow or ValueVector. It'd be great if a future patch could change that for Scan through just a header or a flag on the query.

@kaijianding, do you have any thoughts on https://github.com/druid-io/druid/pull/3307#issuecomment-237303827?

@gianm
For #1, I agree we can use columns instead, and if user want do extraction, he can do it in his own code after  he gets the data . Even if he do want the extraction in druid, we can add the function back in another PR.
For #2, we can always use QueryGranularities.ALL, and remove granularity argument from the query.
For #3, I define ScanQuery extends BaseQuery<ScanResultValue> , the events data is wrapped inside of ScanResultValue, I can change event to type Object, then this Object can be List or ValueVector or Arrow. Another thing is that it need a http request header to tell the QueryResource to use some kind of more binary friendly protocol to transform thing like [{"segmentId":"xxx", "offset":offset, "events": "the binary here(List or ValueVector or Arrow)"}]

@kaijianding do you have any benchmarks around how fast data can be read using this query?

I looked this over and it looks very good to me.
One main comment is that the query doesn't use the processing pool and hence will not respect query priorities and may have multi-tenancy impacts but I am still in favor of the approach taken. I think we need to note that in the docs at a minimum.
👍  after docs are added

@kaijianding @KurtYoung is this still WIP? It looks ready

Still figuring out on how to do global limit from broker side to avoid sending requests to more historicals/realtimes if data from these servers definitely won't appear in final results after final merge(usually the first server can provide enough results if query.limit is set). In another word, can broker be sending requests to servers in sequence instead of in parallel?
Besides the global limit from broker side, this PR is functional ready, but still need to add UT and documents, maybe the caching strategy part of code(do we really need the caching strategy code for scan query?)
@fjy

@kaijianding no, we don't need caching for scan query IMO. A large result set will just fill up the entire cache.

@kaijianding IMO if there's a global limit it's fine to hit every data node and just throw away some data past the limit. This isn't optimal performance wise, but I think that the common use case for scan is likely to be with no limit and/or with hitting data nodes directly. So, I think it's okay if we don't fully optimize for the case where there is a limit and the query hits a broker.
I think caching is unnecessary, so we can just return a null caching strategy.
Docs and tests are important though.
@fjy I'm ok with committing to this as a core feature of druid rather than a contrib extension if the authors are into that. It seems like it'd be useful for integrating Druid with other systems.

@kaijianding have you had a chance to work on this recently? Like mentioned in https://github.com/druid-io/druid/pull/3307#issuecomment-245445404, I think it's ok to pass the global limit down to each data node for the first version of the broker-side query. IMO it would be nice to get something working here in master and then improve on it.

On vacation last few weeks and still on vacation until 8th Oct, will update this PR very soon

great, enjoy your vacation @kaijianding.

@KurtYoung @kaijianding any chance of finishing this up?

Sorry for haven't finished this, it's so busy these days......
Will finish it very soon.

Any performance numbers?

@kaijianding there's a merge conflict
are there any benchmarks?

@kaijianding @KurtYoung ping

@kaijianding is this still WIP or ready for review?

still have some work to respect timeout and cancel behavior like other queries, so it is still WIP

This looks great :-). If I am not mistaken, we should be able to mitigate problem described in #3297 with this. Don't hold me to it, but I'll try to squeeze some time next week to test it against real queries on real data we used there and see what the numbers are in comparison to "classic" select.

@kaijianding @KurtYoung is still WIP? We are really hoping to get it in for 0.10.0

I did not have a way to test it on our normal setups, yet, but I've done some preliminary checks on my home setup. The caveat is that the data was stored on HDD, as I don't have a large enough SSD at home.
At this time I can confirm that this indeed avoids the pitfall described in #3297. This means, in our case (on HDD) it is 100 times (!) faster than normal select. I was able to retrieve about a million rows per second (again, that's on HDD).
It was tested by talking directly to Historical.
Having used it a bit, I have a concern about the API, though. Currently, it seems that even though it's streaming, it always returns all data as one JSON list. This means that the client has to download the whole set anyway, before it's able to decode it.
Say that we ask for 5 billion rows (which is not very unusual in our setups), the client likely won't be able to fit it in memory at once.
What I'd like to see instead is a series of JSON lists, one for each batch, separated with new line (or \0 or whatever). E.g.
[{"segmentId": "...", "columns": [...], "events": [<first_batch>]}]
[{"segmentId": "...", "columns": [...], "events": [<second_batch>]}]
[{"segmentId": "...", "columns": [...], "events": [<third_batch>]}]

, instead of
[{"segmentId": "...", "columns": [...], "events": [<first_batch>, <second_batch>, <third_batch>]}]

It will produce a bit more "noise", true, but is more feasible to use in practice, I think.
Apart from better memory use, this would also enable the client to start processing partial data, while the db connector is downloading the next batch.
Anyway, thanks a lot for this, hopefully it will solve majority of our performance problems regarding Druid use :-).
/cc @kaijianding

You should use streaming jackson read to make it real streaming, please check the JsonParserIterator in DirectDruidClient.
In this way, you don't have to buffer all data in memory, you will get one batch on one time and get the next batch when you need it (the next batch is even not produced in historical before you retrieve it! This the real streaming). @KenjiTakahashi

@kaijianding Thanks, but we're using Python, not Java. Is it possible to perform such query in a generic manner? Or is it just an iterative JSON parser? That could work, but I've always felt that it's bending the JSON spec too much ;-).

https://pypi.python.org/pypi/ijson/ should work. @KenjiTakahashi
Druid can only export json, though I think it is not efficient, but this is the life :)

@kaijianding OK, so I get that it's not (easily) doable for Druid to return multiple JSONs for a single query? Well, then, I guess we'll have to live with that ;-).
I am aware of the ijson library, I'll try to make some use of it later, we'll see how it goes.

Use multi JSONs or not is defined by how QueryResource output the yielder, currently , it is jsonWriter.writeValue(os, yielder); which is actually in DruidDefaultSerializersModule
            try {
              jgen.writeStartArray();
              while (!yielder.isDone()) {
                final Object o = yielder.get();
                jgen.writeObject(o);
                yielder = yielder.next(null);
              }
              jgen.writeEndArray();
            } finally {
              yielder.close();
            }

We can copy the code to QueryResource and remove the  jgen.writeStartArray(); and jgen.writeEndArray(); to produce the result like:
{"segmentId": "...", "columns": [...], "events": [<first_batch>]}
{"segmentId": "...", "columns": [...], "events": [<second_batch>]}
{"segmentId": "...", "columns": [...], "events": [<third_batch>]}

However we can handle streaming json by using jackson in java and ijson in python, I think it is not a good idea to modify this part of code when we have alternative solution.
@KenjiTakahashi

@kaijianding I think we should make this finalized by this week, and fix every problems we met in production environment, what do you think?

@kaijianding I thought it might be possible to define the way data is returned within the scan query code itself. If this requires changes to the outside world, then maybe it's better to leave this for another change?
I have tested it with the ijson lib and it works. Although, as I expected, even with the new, experimental C-based backend (which is much faster than the current one), it is still 4 times slower than reading line delimited batches and using Python's stdlib JSON module on them. Using ujson (alternative implementation meant for speed), it is 10 times slower.
So, I think there's enough to be gained to consider implementing such alternative return syntax.

@fjy it is ready for review now

@KenjiTakahashi it needs to modify QueryResource to return line delimited JSON batches, maybe in another PR.
Also I added a new resultFormat called compactedList. In this format, the result is much less bytes and should improve JSON ser/der speed, memory usage, and network transfer speed. It is useful if you only need the values of each rows(currently, the map keys are redundant.) You can have a try.

@kaijianding Agreed that this can be considered a separate feature, for another PR.
I've tried the "compactedList" format and it is indeed noticeably (not much, but still) faster than the other one.
Thanks again for working on this, we really appreciate it!

@kaijianding it appears that if I send a query with a limit specified to broker... then it would give me different results on different calls based on which historicals responded first to the broker? in that case we should at least note that in the doc.
also, we have the potential to optimize and cancel queries to other historicals which haven't responded yet.
or may be remove the limit at broker and then the limit becomes "per historical" really.

The CachingClusteredClient will sort the sequences by query.getResultOrdering(), for scan query, it depends on the ordering of segmentId(see ScanResultValue.compareTo()), so the broker limit should always return same result.
After the broker get enough data, it calls yielder.close() which I expect it will call JsonParserIterator.close() for each sequence and interrupt the qtp thread on historicals which actually cancel the next batch on historicals @himanshug


Add sub state machine

Please check if the PR fulfills these requirements

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

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:

Codecov Report
Patch coverage: 35.43% and project coverage change: +2.64 :tada:

Comparison is base (54b48dc) 41.97% compared to head (a174c50) 44.61%.

:exclamation: Current head a174c50 differs from pull request most recent head 4e87cc9. Consider uploading reports for the commit 4e87cc9 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           dev/1.0    #1389      +/-   ##
===========================================
+ Coverage    41.97%   44.61%   +2.64%
===========================================
  Files          350      358       +8
  Lines        17787    18173     +386
  Branches      2598     2671      +73
===========================================
+ Hits          7466     8108     +642
+ Misses        9629     9281     -348
- Partials       692      784      +92

Impacted Files
Coverage Δ

...ges/core/src/2d/assembler/SlicedSpriteAssembler.ts
6.75% <0.00%> (+1.27%)
:arrow_up:

packages/core/src/RenderPipeline/RenderPass.ts
70.58% <ø> (ø)

...kages/core/src/RenderPipeline/SpriteMaskManager.ts
28.57% <0.00%> (ø)

packages/core/src/Scene.ts
70.55% <ø> (ø)

...ckages/core/src/animation/AnimatorStatePlayData.ts
13.04% <0.00%> (ø)

packages/core/src/lighting/AmbientLight.ts
26.26% <ø> (ø)

packages/core/src/lighting/DirectLight.ts
84.61% <ø> (+65.38%)
:arrow_up:

packages/core/src/lighting/PointLight.ts
18.51% <ø> (ø)

packages/core/src/lighting/SpotLight.ts
10.20% <ø> (ø)

packages/core/src/material/BlinnPhongMaterial.ts
90.90% <ø> (ø)

... and 56 more

... and 39 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add 'translate a name' issue - elijah

#33 / #1 - Add "elijah" + alias "eli" and a few translations, as well as the origin of the name.

Cool, thanks!
merged #33


Help Gabe Galvin pitch SHR to the nation of Qatar

From<EMAIL_ADDRESS><EMAIL_ADDRESS>On Behalf Of Sleeper, Harry A.
Sent: Tuesday, June 14, 2016 4:41 PM
To: hdi-10x-list Health Data Interoperability 10X Initiative<EMAIL_ADDRESS>Subject: FW: HDI-10x Proposal
Gabe is on board.
He also wants to use SHR with the nation of Qatar.
…H
From: Galvan, Gabriel F.
Sent: Monday, June 13, 2016 5:24 PM
To: Potter, Charles<EMAIL_ADDRESS>Honess-Morreale, Lauren R<EMAIL_ADDRESS>Cc: Sleeper, Harry A<EMAIL_ADDRESS>Subject: FW: HDI-10x Proposal
Chuck,
You asked me about electronic health records.  Harry Sleeper and team are working on this concept supported by our corporate officers to advance.  I understand Harry has pitched it to Yosry.
For your ‘listening’ session with Richard tomorrow, this might be a small opening to have in your back pocket, knowing that MITRE wants to engage with the VA do support this kind of initiative.  Feel free to reach out to Harry (based in Bedford) if you have questions.  While I don’t think you need to sell Dr. Stone on the concept’s value, it might be something your conversation gravitates towards given your respective work on DoD health records.  It would be a good addition to a list of items to reengage soon with him.
Regards,
Gabe
From: "Sleeper, Harry A."<EMAIL_ADDRESS>Date: Monday, June 13, 2016 at 5:08 PM
To: "Galvan, Gabriel F."<EMAIL_ADDRESS>Cc: "Sleeper, Harry A."<EMAIL_ADDRESS>Subject: HDI-10x Proposal
Gabe
We are pushing on a 10x initiative to help solve
Health Data Interoperability in the US (and beyond).
The core concept is to build a
Standard Health Record for all Emergency care,
Primary care, and, in time, other domains of healthcare delivery.
Please review the attached charts.
We'd like to brief you and get your support.
...H

Could Qatar be a pilot site for the very core (or more) of the SHR? It’s International (a MITRE goal) and a somewhat isolated sample population with sovereign status that may support quick PHI approval (SHR goal).
Some fun facts about Qatar:
•	The National Health Authority (NHA) was established in 2005 to replace the Ministry of Public Health.
•	The NHA overseas the necessary medical services and entrusts them to public health institutions, the main one being the Hamad Medical Corporation (HMC).
•	There are ~9 hospitals, ~5 are government run
•	Ambulance service is strong and linked to at least one major hospital via satellite
•	NHA controls make/market of drugs and conforms to international standards
•	Belief in preventive care and vaccines; country spends on healthcare


Gossip snappy compression

resolves #839

Lgtm. Is this mandatory to join Topaz?

Lgtm. Is this mandatory to join Topaz?

We won't join topaz as it has consensus bugs so it's basically useless testnet atm. But I think we need this to join Schlesi which is target for multiclient. I'll fix conflcts now


Fix border on 'Selection controls/Switch on and off'

Fix whatever is wrong with the 'Resting' layer.
https://www.figma.com/file/0bGXR2sCwMVSDNyyzu5BXrO5/UI—User-Interface?node-id=1471%3A2

Is this still relevant @lucasveil ?

No the link isn't relevant and not making any sense. The selection control will be fixed when we implement the new focus frame.


buf: 0.54.1 -> 1.0.0-rc7

Motivation for this change
Bump version to latest 1.0.0 release candidate: https://github.com/bufbuild/buf/releases/tag/v1.0.0-rc7
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Please but the maintainer list edit in a separate commit

@SuperSandro2000 please take a look and let me know if there is anything else needed.


sqrt gives wrong unit

The following code:
#include <iostream>
#include <units/physical/si/length.h>
#include <units/math.h>

namespace units::si
{
struct gigametre : prefixed_unit<gigametre, giga, metre> {};
} // namespace units::si

using position = units::si::length<units::si::gigametre>;

int main()
{
    auto const x = position{1.};
    std::cout << "x:         " << x << "\n"
              << "sqrt(x):   " << units::sqrt(x) << "\n"
              << "x*x:       " << x*x << "\n"
              << "sqrt(x*x): " << units::sqrt(x*x) << "\n";

}

gives the following output:
$ g++ -std=c++2a -fconcepts units.cpp && ./a.out
x:         1 Gm
sqrt(x):   1 m^(1/2)
x*x:       1 × 10¹⁸ m²
sqrt(x*x): 1 m

Hi, thanks for reporting and sorry for a late reply. I had family vacations and 3 business trips in the last 4 weeks. Crazy times...
Anyway, the bug is confirmed and the problem is here: https://github.com/mpusz/units/blob/master/src/include/units/ratio.h#L206. However, as I am not the author of this part of code and still am very busy (ISO C++ Committee meeting in Prague) I would appreciate the help here. @oschonrock could you please take a look at it?

I will try to take a look

Thanks! :-)


Error while connecting to dash.

Couldn't connect my dashboard to it

It may be because of Cloudflare Proxy try give bypass to the api folder which is https://dashurl/api/*

Might this helps you..


Change /income and /coins to use ?mining=(included|excluded|only) rat…

…her than nomine=1

Needed because of https://github.com/cjdelisle/pkt-explorer-backend/commit/9a6d2a2ca881a1f5a17baff097325ed087f2509d


Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npm when deploying on AEM Cloud Service ci/cd pipeline

Expected Behaviour
Successful build when deploying AEM Cloud Service ci/cd pipeline
Actual Behaviour
Build failing at build & Unit Testing step
Reproduce Scenario (including but not limited to)
Tried running several times
Steps to Reproduce
Run development pipeline on AEM CS
Platform and Version
AEM CS release 2023.1.10912.20230130T173736Z
Sample Code that illustrates the problem
Logs taken while reproducing problem
build_maven_build (47).log

@tonijhanel , the core components need not be built by the CI/CD pipeline. Instead your project can embed already released core component artifacts. To enable core core components, you may follow:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/creating-adaptive-form-core-components.html?lang=en#pre-requisites


Add a linter/formatter

We should add a linter/formatter to pick up small style issues and TS idioms which we can then integrate with the build process

Project already suggests you install ESLint. See devDependencies in package.json

I'd also like to integrate Prettier and set up some formatting rules.


Update .travis.yml

Could you supply a summary of what you did, why you did it and what issue this solves? Comment-less PRs are rather difficult to judge on :)

Closing this, looks like you added JSON into a YML file .. guess that wasn't the intention.