tests/test_parallel.py fails sometimes

Test_parallel fails frequently, but not always.
It seems that tests/test_parallel.py::test_render_bsdm  is causing it (most of the times?).
As it doesn't occur every time, it might be undefined behaviour related to the shared memory access.
I will first try to collect some tracebacks, maybe they show some pattern.
Test on macOS-latest with Python 3.6

test_jobs = None

    @pytest.mark.parametrize('test_jobs', JOB_COUNTS)
    def test_render_bsdm(test_jobs):
        sdm_p, sdm_phi, sdm_theta = [*np.random.randn(3, 1000)]
        hrirs = spa.IO.load_hrirs(fs=44100, filename='dummy')
        bsdm_l_r, bsdm_r_r = spa.sdm.render_bsdm(sdm_p, sdm_phi, sdm_theta, hrirs,
                                                 jobs_count=1)
        bsdm_l_t, bsdm_r_t = spa.sdm.render_bsdm(sdm_p, sdm_phi, sdm_theta, hrirs,
                                                 jobs_count=test_jobs)
>       assert_allclose([bsdm_l_t, bsdm_r_t], [bsdm_l_r, bsdm_r_r])
E       AssertionError:
E       Not equal to tolerance rtol=1e-07, atol=0
E
E       Mismatched elements: 1 / 2510 (0.0398%)
E       Max absolute difference: 0.64633057
E       Max relative difference: 1.
E        x: array([[ 1.955098,  0.205032, -1.341322, ...,  0.      ,  0.      ,
E                0.      ],
E              [ 1.955098,  0.205032, -1.341322, ...,  0.      ,  0.      ,
E                0.      ]])
E        y: array([[ 1.955098,  0.205032, -1.341322, ...,  0.      ,  0.      ,
E                0.      ],
E              [ 1.955098,  0.205032, -1.341322, ...,  0.      ,  0.      ,
E                0.      ]])

Strange. Also occasionally happens when you execute it locally, or only in tests?
It is always only one time domain sample that is wrong?
I have not looked into the actual processing at all, but this might be an idea on narrowing the error down.
The "sometimes" most likely happens due to the utilization of randn as an input. However, the splitting into multiple tasks should not alter the results anyways of course. The data types in both branches are exactly the same? Maybe it is a matter of lacking numerical precision, which is only sometimes triggered due to the noise.

I could also make it fail locally, however, only a single time so far. Seems to be a lot less frequent when executed on a local machine.
Yes, it seems that it is always exactly one sample...

Another traceback:
Test on ubuntu-latest with Python 3.7

=================================== FAILURES ===================================
_____________________________ test_render_bsdm[2] ______________________________

test_jobs = 2

    @pytest.mark.parametrize('test_jobs', JOB_COUNTS)
    def test_render_bsdm(test_jobs):
        sdm_p, sdm_phi, sdm_theta = [*np.random.randn(3, 1000)]
        hrirs = spa.IO.load_hrirs(fs=44100, filename='dummy')
        bsdm_l_r, bsdm_r_r = spa.sdm.render_bsdm(sdm_p, sdm_phi, sdm_theta, hrirs,
                                                 jobs_count=1)
        bsdm_l_t, bsdm_r_t = spa.sdm.render_bsdm(sdm_p, sdm_phi, sdm_theta, hrirs,
                                                 jobs_count=test_jobs)
>       assert_allclose([bsdm_l_t, bsdm_r_t], [bsdm_l_r, bsdm_r_r])
E       AssertionError:
E       Not equal to tolerance rtol=1e-07, atol=0
E
E       Mismatched elements: 1 / 2510 (0.0398%)
E       Max absolute difference: 1.31017305
E       Max relative difference: 1.
E        x: array([[0.916457, 2.660908, 1.464512, ..., 0.      , 0.      , 0.      ],
E              [0.916457, 2.660908, 1.464512, ..., 0.      , 0.      , 0.      ]])
E        y: array([[0.916457, 2.660908, 1.464512, ..., 0.      , 0.      , 0.      ],
E              [0.916457, 2.660908, 1.464512, ..., 0.      , 0.      , 0.      ]])

So it is not related to the Python version since this is 3.7 now? (That would have been very weird anyways, if all other packages are identical).
Max relative difference: 1. means that the single value is exactly double in one case?

I'm pretty certain this should solve it.
# part of parallel render_bsdm:
def _render_bsdm_sample(i, p, phi, theta, hrirs):
    h_l, h_r = hrirs[hrirs.nearest(phi, theta)]
    # global shared_array
    with shared_arr.get_lock(): # synchronize access
        shared_array[i:i + len(h_l), 0] += p * h_l
        shared_array[i:i + len(h_l), 1] += p * h_r

Hm, I am using multiprocessing.Array, which already includes a lock...
https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Array
I am quite surprised why this particular function seems to fail while others don't.

Yes. I see the documentation is confusing in regards of the lock. The way that I understood it so far is, that it provides lock functionality for synchronized access, but it is not managed for you. This is because many examples I found online are also applying the lock in the way I specified in the code above.
I did not check all methods. But could it be that bsdm is the only one where the system state is part of the processing (i.e. utilizing +=, hence require synchronization). If so, this is also a strong indicator that manual locking is required. Did you try it this way and test still fail occasionally?

Seems it was indeed the += inplace operator. I'm also casting back to a numpy array, so the operator seems to be not thread safe there.
cf77fa8f9065e7ecca2f8b6667baca8fdd42392b and f5e5654b7c463710f09c92ca4c07a272c32c0a8a target this issue.
The reentrant lock seemed necessary at least for Windows, even though on my local Linux machine I couldn't make it fail with
repeat 100 { pytest tests/test_parallel.py::test_render_bsdm }
Thank you @HaHeho !

Re-opening, because still not resolved.
The last times failing seem to happen always on Windows.
Traceback:
Cross-Platform Test / Test on windows-latest with Python 3.6

test_jobs = 2
54

55
    @pytest.mark.parametrize('test_jobs', JOB_COUNTS)
56
    def test_render_bsdm(test_jobs):
57
        sdm_p, sdm_phi, sdm_theta = [*np.random.randn(3, 1000)]
58
        hrirs = spa.IO.load_hrirs(fs=44100, filename='dummy')
59
        bsdm_l_r, bsdm_r_r = spa.sdm.render_bsdm(sdm_p, sdm_phi, sdm_theta, hrirs,
60
                                                 jobs_count=1)
61
        bsdm_l_t, bsdm_r_t = spa.sdm.render_bsdm(sdm_p, sdm_phi, sdm_theta, hrirs,
62
                                                 jobs_count=test_jobs)
63
>       assert_allclose([bsdm_l_t, bsdm_r_t], [bsdm_l_r, bsdm_r_r])
64
E       AssertionError:
65
E       Not equal to tolerance rtol=1e-07, atol=0
66
E
67
E       Mismatched elements: 1 / 2510 (0.0398%)
68
E       Max absolute difference: 0.01022394
69
E       Max relative difference: 1.
70
E        x: array([[-1.208554, -0.140148,  0.93946 , ...,  0.      ,  0.      ,
71
E                0.      ],
72
E              [-1.208554, -0.140148,  0.93946 , ...,  0.      ,  0.      ,
73
E                0.      ]])
74
E        y: array([[-1.208554, -0.140148,  0.93946 , ...,  0.      ,  0.      ,
75
E                0.      ],
76
E              [-1.208554, -0.140148,  0.93946 , ...,  0.      ,  0.      ,
77
E                0.      ]])

Windows potentially (by default) follows a different mechanic of spawning child processes. I am not sure why this would influence the lock though,
https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods
However, I did not really understand the way you implemented the lock there. What is the reason for using RLock() instead of Lock(). The multiprocessing documentation is pretty cryptic on practical differences. This seems to explain differences:
https://stackoverflow.com/questions/22885775/what-is-the-difference-between-lock-and-rlock
According to this, I would assume that Lock() is the more reasonable choice for you (supposed to be faster and does not allow multiple entries by the same process). Also, why not straight up use the associated lock created with the array (with shared_arr.get_lock():)?
I would try that and see if that solves the problem.

Actually, https://docs.python.org/3/library/multiprocessing.html#all-start-methods (Explicitly pass resources to child processes) explains that this might actually be cause by the different process spawning on Windows. I would still expect my suggested way above to work, and be the most easy to read.
Otherwise, you seem to be required to pass the lock instance to the function, in order to properly work under Windows.


'Could not resolve' error when importing a font file using a relative path in scss

Hey, apologies if I'm asking in the wrong place, I'm a bit puzzled - just wondering if you could help? :)

I've got a root folder called assets which contain my final outputted CSS & JS and also my images folder and a fonts folder
My uncompiled scss and js live in another root level folder, called resources

I'm using VSCode's path autocomplete within an @font-face rule and the path should be: url('../../../../assets/fonts/bricolage-grotesque-400.woff2') format('woff2') but I keep getting that error. I've tried other paths too but no luck :(
Am I missing an esbuild config setting or?
Thank you for your time, appreciate if any advice can be given :)

I added external: *.woff2 in my config and it seems to have fixed it! :)


Unable to open using 7.3.1 version

System information:

Operating system (distribution) and version: arch linux
DBeaver version: 7.3.1
Additional extensions:Nnone

Connection specification:

Database name and version: Unrelated
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
The system crashes when opening the application. it only talks about opening a log with the details.
Steps to reproduce, if exist:
Just try to open the application.
Using 7.3.0 version had no issue for me.
Include any warning/errors/backtraces from the logs
Here is the content of the generated log file:<PHONE_NUMBER>114.log
Here is my java version:
> java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)

Let me now if any additional details are requried

see https://github.com/dbeaver/dbeaver/issues/10837
Archlinux is declaring the dependency wrong, dbeaver now requires jdk 11. It is a bug in the archlinux package.

Thanksfor the info i'm closing this now.  Sorry for the extra noise but I did not find the existing bug report


Make Store.spec.lua destruct all stores

This PR closes #51

Coverage remained the same at 99.351% when pulling 0f7ef24c7467c7aa90f19baa76118f1fe3a92d23 on OverHash:destructure-stores into efda50fa7059b2c9538e5d846ace296e13598398 on Roblox:master.

commenting for the CLA bot

I have read the CLA Document and I hereby sign the CLA

Hi, thanks for your contribution! This comment should kickstart the CLA bot and re-run it


blog links moved

The five links at the bottom of the page to the series of blogs from Microsoft Support are no longer valid. They are now at the following URLs:

ConfigMgr 2012 Data Replication Service (DRS) Unleashed - https://techcommunity.microsoft.com/t5/configuration-manager-archive/configmgr-2012-data-replication-service-drs-unleashed/ba-p/339916
ConfigMgr 2012 DRS – Troubleshooting FAQs - https://techcommunity.microsoft.com/t5/configuration-manager-archive/configmgr-2012-drs-troubleshooting-faqs/ba-p/339934
ConfigMgr 2012 DRS Initialization Internals - https://techcommunity.microsoft.com/t5/configuration-manager-archive/configmgr-2012-drs-initialization-internals/ba-p/339948
ConfigMgr 2012: DRS and SQL service broker certificate issues - https://techcommunity.microsoft.com/t5/configuration-manager-archive/configmgr-2012-drs-and-sql-service-broker-certificate-issues/ba-p/339910

The ConfigMgr DRS Synchronization Internals post is in progress to move to the same location

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

ID: 66942850-8515-4767-ae2f-0678536dcfcd
Version Independent ID: 109df485-0281-1118-5e83-aa14666b6280
Content: Troubleshoot SQL replication - Configuration Manager
Content Source: sccm/core/servers/manage/replication/overview.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Most of these were just fixed today with MicrosoftDocs/SCCMDocs-pr#4931, except the first one.

ConfigMgr DRS Synchronization Internals -
https://techcommunity.microsoft.com/t5/configuration-manager-archive/configmgr-drs-synchronization-internals/ba-p/1154317


Server Demo

Hello,
This seems neat, is there a site online with this running (a demo)? Thanks.

localhost


install_requires is not executed with custom install command

Originally reported by: andi0661 (Bitbucket: andi0661, GitHub: Unknown)

When using install_requires in the input arguments to setup(), it is only executed when installing the package via "pip install", but it is ignored when installing via "python setup.py install".
It would be nice if "python setup.py install" could be made to do the same thing as "pip install ." (i.e. install from package unpack directory containing setup.py), as far as "install_requires" is concerned.
This is with setuptools v17.0, which is the latest setuptools I get with virtualenv for python 2.6 on RHEL 6.7.

Bitbucket: https://bitbucket.org/pypa/setuptools/issue/456

@jaraco I hit the very same issue with custom install step. I overrode _called_from_setup in a derived class which represents the custom install to return True, which I found quite nasty. Would it be possible to fix it?
Apparently there are more people out there having the same problem:
http://stackoverflow.com/questions/14441955/how-to-perform-custom-build-steps-in-setup-py

It may be possible to fix it, though I'm not sure when I will get into it. Next steps are for someone to deep analyze the problem, characterize the issue, and propose something that might fix it.

Very annoying bug, but this solution works: https://stackoverflow.com/a/21196195/448776

I'm hitting this issue - does anyone know of a workaround?
i have both install_requirements and setup_requires in my setuptools.setup method call. But they seem to simply be ignored 😓.

I am also facing the same issue. Any updates?

FWIW it's highly discouraged to use setup.py install directly because it breaks things in the pip ecosystem starting with the inability to uninstall packages installed like this. Implementing a proper dependency resolution mechanism is a lot of work and it would basically reimplementing what pip does and vendoring resolvelib. I think it's not worth it and better be deprecated.

Apparently there are more people out there having the same problem:
http://stackoverflow.com/questions/14441955/how-to-perform-custom-build-steps-in-setup-py

I note that at least in this use-case, the user is attempting to alter the 'build' behavior and they're doing so by altering the 'install' command. My recommendation here would be to avoid altering the install behavior and instead try to alter the build behavior, in particular to alter the build.subcommands to include the additional behavior. I plan to work on a demo for this. I created #2591 to capture that idea.
In the meantime, I welcome those interested in working on this issue to consider a few approaches:

Proper fix: delve into the implementation, add some test coverage to capture the current expectations, add some tests that capture the missed expectation when install is subclassed, and then devise a fix in _called_from_setup.
Investigate: In any install subclass, override _called_from_setup to replace the 2 with 3. Does that fix the issue?
Redesign: The point of that check is to bypass egg-based installs for bdist_* commands. Perhaps those commands could explicitly set a flag on the install command to bypass egg-based installs.
Redesign: Perhaps as a step toward deprecating egg-based installs, install could be separated into different commands, perhaps creating install_egg and install_plain... and callers like bdist could use install_plain and callers who really want eggs could use install_egg.
Bypass: Stop doing egg installs altogether and use pip-based installs, as egg-based installs are discouraged and will be deprecated (soon?).


Add standalone example

What is the issue?
Add standalone example for simplification
Suggestion(s)/solution(s) [Optional]
add new directory example/standalone or example/presto_standalone
Checklist (after created issue)

[x] Added label(s)
[ ] Added to project
[ ] Added to milestone

working on this, but a huge blocker in https://github.com/fredrikhgrelland/terraform-nomad-hive/issues/52 atm


README.md

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

@DanielToucedo closing the issue due to no response. Feel free to create a new issue adding only your name and link as per suggested by the maintainers. Thank you.


feat(iroh): make all important iroh_base types available

Description
Otherwise one has to pull in some things from iroh-base and some from here
Breaking Changes
None, just additions
Notes & open questions

Change checklist

[ ] Self-review.
[ ] Documentation updates following the style guide, if relevant.
[ ] Tests if relevant.
[ ] All breaking changes documented.

I assume that this does not mean that things like AddrInfoOptions

it is actively used right now in code, which is why I need to expose it, but would love to see a PR improving the API

will remain until 1.0.

iroh-base is part of hitting 1.0, so time to clean up any APIs you don't think should stay


Bullets as question marks

@elcopeland commented on Wed Jan 31 2018
http://munews.wpengine.com/120620_26-mercer-law-students-receive-stipends-for-summer-internships/

To be clear, that's not a real HTML list

 list.
Those are just bullet characters copy+pasted into the content.
Fixed with entity encoding.


Service set_cover_combined_position fails in 1.60.0

I agree to the following

[X] I have read the documentation right now
[X] I have read the FAQs right now
[X] I am aware of the latest release notes
[X] I am aware that an integration that was installed via HACS also needs to be updated via HACS
[X] The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
Service set_cover_combined_position fails with 1.60.0
I‘m using HMIP FBL Jalousieaktoren
What version of HomematicIP (local) has the issue?
1.60.0
What was the last working version of HomematicIP (local)?
1.59.0
What type of installation are you running?
Home Assistant OS
What type of installation are you running for your homematic backend?
CCU3
Which version of your homematic backend are you running?
3.75.7
What hardware are you running for your system?
Blue
Which config details do you use

[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[X] Homematic IP
[ ] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information (no logs here)
No response
Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!
Logger: homeassistant.components.websocket_api.http.connection
Quelle: custom_components/homematicip_local/cover.py:175
Integration: Home Assistant WebSocket API (Dokumentation, Probleme)
Erstmals aufgetreten: 21:06:29 (3 Vorkommnisse)
Zuletzt protokolliert: 21:08:26

[281473220034752] Error handling message: Unknown error (unknown_error) Alexander Strotmann from <IP_ADDRESS> (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2024.4 (io.robbie.HomeAssistant; build:2024.624; iPadOS 17.4.1) Mobile/HomeAssistant, like Safari)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 794, in handle_execute_script
    script_result = await script_obj.async_run(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1728, in async_run
    return await asyncio.shield(create_eager_task(run.async_run()))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 457, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 509, in _async_step
    self._handle_exception(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 562, in _handle_exception
    raise exception
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 507, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 742, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 705, in _async_run_long_action
    return await long_task
           ^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2543, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2580, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
    raise result from None
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1580, in async_request_call
    return await coro
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1043, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/homematicip_local/cover.py", line 175, in async_set_cover_combined_position
    await collector.send_data(
          ^^^^^^^^^^^^^^^^^^^^
TypeError: CallParameterCollector.send_data() missing 2 required positional arguments: 'use_command_queue' and 'use_put_paramset'

Additional information
No response

After rolling back to 1.59.0 it‘s working again.

Thanks for reporting


feat(caas): backport from caas

Description of your changes

backport from caas
update

XEKS

add aws-auth configmap
add XIRSA configmap (oidc provider)

XCluster

add region as input
add providerConfig as input
using patchSets
IAMRole/IAMUser as default admin input

XNetwork
XService

add flux
use prometheus as default

XIRSA

no usage of alpha features needed

rename folder package -> apis
switch crossplane.yaml to root folder
update Makefile

Fixes #95
Closes #100
I have:

[x] Read and followed Upbound's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested
UPTEST_CLOUD_CREDENTIALS=$(cat ~/.aws/uptest) make e2e
--- PASS: kuttl (2168.96s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/case (2166.96s)
PASS
15:48:22 [ OK ] running automated tests

/test-examples

@ytsarev let me double check - one issue is building for MCP Controlplane is not possible when using example folder  - so we need to find a good way for both build options

/test-examples

/test-examples

/test-examples

@ytsarev please check again  - license/cla check is yellow don't know whats going on - on cla.upbound.io everything is signed

/test-examples

/test-examples

/test-examples

/test-examples


Buggy elements parsing, especially in FF (and IE 10)

Greatly improved yesterdays pr #117.
Groups of inline elements (not separated with line break or block element) are wrapped in one paragraph now.

Hi!
Sorry for looooong time... I don't have forget you, I was just busy.
I've merge your amazing work with some optimizations/improvements and squash your commits.
Thanks for your awesome contribution to Trumbowyg! You've got fix multiples bugs with that PR!

Thank you as well!


Traefik fails to start after enabling redirect to https via CLI

Do you want to request a feature or report a bug?
Bug
What did you do?
I wanted to set up traefik inside a docker container, configuring backends and frontends via a separate rules.toml.
I used an old example configuration before #2798 got in, so used the configuration from below, but without the single quotes at the --entrypoints= arguments. This kinda worked, with the exception of the SSL redirect not happening.
After following up with #2798, I changed my configuration as shown below.
What did you expect to see?
Traefik now trying to redirect from HTTP to HTTPS
What did you see instead?
Traefik failing to start:
time="2018-05-09T13:57:33Z" level=fatal msg="Unknown entrypoint \"'https'\" for provider ACME configuration"

Output of traefik version: (What version of Traefik are you using?)
Version:      v1.6.0
Codename:     tetedemoine
Go version:   go1.10.1
Built:        2018-04-30_09:28:44PM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
docker-compose.yaml:
version: '3'

services:
  reverse-proxy:
    image: traefik:alpine
    command:
      - "--api"
      - "--entrypoints='Name:http Address::80 Redirect.EntryPoint:https'"
      - "--entrypoints='Name:https Address::443 TLS'"
      - "--defaultentrypoints=http,https"

      - "--acme"
      - "--acme.storage=/etc/traefik/acme/acme.json"
      - "--acme.entryPoint=https"
      - "--acme.httpChallenge.entryPoint=http"
      - "--acme.OnHostRule=true"
      - "--acme.onDemand=false"
      -<EMAIL_ADDRESS>      - "--file.filename=/etc/traefik/rules.toml"
    ports:
      - "80:80"
      - "443:443"
      - "8080:8080"
    volumes:
      - acme-storage:/etc/traefik/acme
      - ./rules.toml:/etc/traefik/rules.toml
volumes:
  acme-storage:

rules.toml only contains [backend] and [frontend] sections, no enty-point specifics here.

Thanks for your interest in Traefik 😃
Remove the single quotes: https://docs.traefik.io/v1.6/configuration/entrypoints/#cli

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Træfik!
We dedicate the issue tracker to bug reports and feature requests only.
If you have questions and need community support, you can join our Slack workspace and reach out to us on the #support channel.
Another option is to use Stack Overflow and tag your question traefik.
Of course, double checking Træfik's documentation is always a good idea :sweat_smile:

@ldez Thanks for the hint - it seems like traefik parses the configuration as I pass, but doesn't react accordingly - I get a 404, instead of the redirect to the HTTPS backend.
Nothing in the logs on that request :-/
{
  "LifeCycle": {
    "RequestAcceptGraceTimeout": 0,
    "GraceTimeOut":<PHONE_NUMBER>0
  },
  "GraceTimeOut": 0,
  "Debug": true,
  "CheckNewVersion": true,
  "SendAnonymousUsage": false,
  "AccessLogsFile": "",
  "AccessLog": null,
  "TraefikLogsFile": "",
  "TraefikLog": null,
  "Tracing": null,
  "LogLevel": "",
  "EntryPoints": {
    "http": {
      "Address": ":80",
      "TLS": null,
      "Redirect": {
        "entryPoint": "https",
        "permanent": true
      },
      "Auth": null,
      "WhitelistSourceRange": null,
      "WhiteList": null,
      "Compress": false,
      "ProxyProtocol": null,
      "ForwardedHeaders": {
        "Insecure": true,
        "TrustedIPs": null
      }
    },
    "https": {
      "Address": ":443",
      "TLS": {
        "MinVersion": "",
        "CipherSuites": null,
        "Certificates": [],
        "ClientCAFiles": null,
        "ClientCA": {
          "Files": null,
          "Optional": false
        }
      },
      "Redirect": null,
      "Auth": null,
      "WhitelistSourceRange": null,
      "WhiteList": null,
      "Compress": false,
      "ProxyProtocol": null,
      "ForwardedHeaders": {
        "Insecure": true,
        "TrustedIPs": null
      }
    },
    "traefik": {
      "Address": ":8080",
      "TLS": null,
      "Redirect": null,
      "Auth": null,
      "WhitelistSourceRange": null,
      "WhiteList": null,
      "Compress": false,
      "ProxyProtocol": null,
      "ForwardedHeaders": {
        "Insecure": true,
        "TrustedIPs": null
      }
    }
  },
  "Cluster": null,
  "Constraints": [],
  "ACME": null,
  "DefaultEntryPoints": [
    "http"
  ],
  "ProvidersThrottleDuration":<PHONE_NUMBER>,
  "MaxIdleConnsPerHost": 200,
  "IdleTimeout": 0,
  "InsecureSkipVerify": false,
  "RootCAs": null,
  "Retry": null,
  "HealthCheck": {
    "Interval":<PHONE_NUMBER>0
  },
  "RespondingTimeouts": null,
  "ForwardingTimeouts": null,
  "AllowMinWeightZero": false,
  "Web": null,
  "Docker": null,
  "File": {
    "Watch": true,
    "Filename": "/etc/traefik/rules.toml",
    "Constraints": null,
    "Trace": false,
    "TemplateVersion": 0,
    "DebugLogGeneratedTemplate": false,
    "Directory": ""
  },
  "Marathon": null,
  "Consul": null,
  "ConsulCatalog": null,
  "Etcd": null,
  "Zookeeper": null,
  "Boltdb": null,
  "Kubernetes": null,
  "Mesos": null,
  "Eureka": null,
  "ECS": null,
  "Rancher": null,
  "DynamoDB": null,
  "ServiceFabric": null,
  "Rest": null,
  "API": {
    "EntryPoint": "traefik",
    "Dashboard": true,
    "Debug": true,
    "CurrentConfigurations": null,
    "Statistics": null
  },
  "Metrics": null,
  "Ping": null
}

Turned out, each frontend still needs to keep the endpoint that's serving the redirect in it's configuration, either by using defaultentrypoints, or per frontend in their configuration.


react-scripts 3.3.0 / 3.3.1 -> [HMR] Waiting for update signal from WDS... in console (Edge not working still)

Describe the bug
I am pretty new to React, so bear with me please.
I tried setting up a new project in react and these are the default dependencies generated in package.json :
"react": "^16.12.0",
"react-dom": "^16.12.0",
"react-scripts": "3.3.0"
After I run npm start I get a message in the console "[HMR] Waiting for update signal from WDS..."
The page still shows up and refreshes automatically whenever a change is made but it only works on Chrome and Mozilla.
For some reason Microsoft Edge doesn't work anymore even though it did before
Did you try recovering your dependencies?

I tried going back to different versions of react or scripts and everything goes back to normal when I have :
"react": "^16.12.0",
"react-dom": "^16.12.0",
"react-scripts": "3.3.0-next.62"
Everything above "react-scripts": "3.3.0-next.62" gives the error in the console and Edge stops working.
Which terms did you search for in User Guide?

I tried npm run eject to configure the webpack.config but I am not really that experienced and couldn't see a problem
Environment

System:
OS: Windows 10 10.0.18363
CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Binaries:
Node: 10.16.3 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.13.3 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: ^16.12.0 => 16.12.0
react-dom: ^16.12.0 => 16.12.0
react-scripts: 3.3.0 => 3.3.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

(Write your steps here:)

npx create-react-app [NAME]
npm start
open console in browser

Expected behavior

No message in console.
Microsoft Edge to show page.
Actual behavior

Message in console.
Blank Page in Edge.
Edge with react-script: 3.3.0:

Edge with react-scripts: 3.3.0-next.62:

Chrome with react-script: 3.3.0 :

Chrome with react-scripts: 3.3.0-next.62:

Reproducible demo

https://github.com/Dodobrat/react-scripts-error

Sounds like a super of #8084

I checked it and tried the suggested fix.
Microsoft Edge works now but this is not a solution. Anytime I install a new package it goes back to the previous version. Also the message still persists.

I'm experiencing the issue as well, in my case this message appears in any browser that runs the app.

Yes @willjopling . It appears on all browsers, yet it only breaks Microsoft Edge. Mozilla and Chrome work just fine. Currently I am developing with version react-scripts: 3.3.0-next.62 , which works just fine on all browsers and doesn't give any messages in the browser.
I guess we should just wait for a new version.

I'm also experiencing the issue, the message just sits there at the console, but everything seems to be working

Trying to console.log something from inside a react component method will not work, seems the console is being cleared?

I have the same issue.
While waiting for a fix, I create my projects with :
npx create-react-app kapibook-client --scripts-version 3.2.0

I have the same issue.
While waiting for a fix, I create my projects with :
npx create-react-app project-name --scripts-version 3.2.0

I have the same issue.
While waiting for a fix, I create my projects with :
npx create-react-app project-name --scripts-version 3.2.0

It even helped just to change package.json version to "3.2.0" and delete node_modules directory

i have the same issue too everything working but i can't fetch data from API (jsonplaceholder api) any buddy got solution?

02.01.2020 and the same here.
In my Mac OS X today in started a project react and when I tried use a api the "problem" happy. :(

02.01.2020 and the same here.
In my Mac OS X today in started a project react and when I tried use a api the "problem" happy. :(

Do you use Axios in this project?

not
atul prajapati<EMAIL_ADDRESS>escreveu no dia sexta, 3/01/2020
à(s) 01:58:

02.01.2020 and the same here.
In my Mac OS X today in started a project react and when I tried use a api
the "problem" happy. :(
[image: Screen Shot 2020-01-02 at 15 13 14]
https://user-images.githubusercontent.com/5879047/71683840-6b6c4200-2d72-11ea-8261-28c7fdfbb089.png
Do you use Axios in this project?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/8153?email_source=notifications&email_token=ABM3KB7EJCX4G4GG5Q533STQ33AXHA5CNFSM4JZROMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIAJDZY#issuecomment-570462695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM3KB32EUFDIGVHCRO7AP3Q33AXHANCNFSM4JZROMZQ
.

not atul prajapati<EMAIL_ADDRESS>escreveu no dia sexta, 3/01/2020 à(s) 01:58:
…
02.01.2020 and the same here. In my Mac OS X today in started a project react and when I tried use a api the "problem" happy. :( [image: Screen Shot 2020-01-02 at 15 13 14] https://user-images.githubusercontent.com/5879047/71683840-6b6c4200-2d72-11ea-8261-28c7fdfbb089.png Do you use Axios in this project? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8153?email_source=notifications&email_token=ABM3KB7EJCX4G4GG5Q533STQ33AXHA5CNFSM4JZROMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIAJDZY#issuecomment-570462695>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABM3KB32EUFDIGVHCRO7AP3Q33AXHANCNFSM4JZROMZQ .

i can't understand what are you trying to say

I have the same issue.
While waiting for a fix, I create my projects with :
npx create-react-app project-name --scripts-version 3.2.0

Thanks!

if you have already installed create-react-app. try to uninstall
create-react-app then directly
run this command
npx create-react-app project-name
to create your project :)
On Sat, Jan 4, 2020 at 1:57 AM Djordje Cvetkovic<EMAIL_ADDRESS>wrote:

I have the same issue.
While waiting for a fix, I create my projects with :
npx create-react-app project-name --scripts-version 3.2.0
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/8153?email_source=notifications&email_token=AJYYZNWRPZG3KKDKNEGSIJDQ36NTNA5CNFSM4JZROMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICAJ6Q#issuecomment-570688762,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJYYZNULMQQG5IGXEEJZCBLQ36NTNANCNFSM4JZROMZQ
.

For my quick Edge test, I set a breakpoint where the Syntax Error occurs, then pasted a reimplementation of url.format into the console.
url.format = function ({protocol, hostname, port, pathname}) {return protocol + '://' + hostname + ':' + port + pathname };

The two slashes are missing in the original url.format() return value and that causes new WebSocket(url) to throw a Syntax Error.

The one-liner temporary very hacky fix is to run the following:
sed --in-place -e "66a\    slashes: true," ./node_modules/react-dev-utils/webpackHotDevClient.js

This will add in slashes: true to line 66 of the ./node_modules/react-dev-utils/webpackHotDevClient.js file

Bumping this for relevance. Hoping the future release will fix this. Error is making it difficult to test before deploying.

Updated to react-scripts 3.3.1.
I observe slashes: true,  on line 67 of ./node_modules/react-dev-utils/webpackHotDevClient.js.
I killed node. I restarted VS Code. I even rebooted.
Unfortunately, I still observe [HMR] Waiting for update signal from WDS... in console.

Can anyone confirm if 3.3.1 fixes this issue for them? We fixed some issues with the usage of the WebSocket API that were introduced in 3.3.0.

Still seeing the same issue with Edge.

Environment Info:
current version of create-react-app: 3.3.1
System:
OS: Windows 10 10.0.18362
Binaries:
Node: 12.15.0
Yarn: 1.19.1
npm: 6.13.7
Browsers:
Edge: 44.18362.449.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: ^16.12.0 => 16.12.0
react-dom: ^16.12.0 => 16.12.0
react-scripts: 3.3.1 => 3.3.1
npmGlobalPackages:
create-react-app: Not Found

@drew-thorson that looks unrealted to this issue?

@drew-thorson that looks unrealted to this issue?

This is the same result I have now that I updated to react-scripts: 3.3.1
You can clone the demo repo: __https://github.com/Dodobrat/react-scripts-error__
It is a bare bones create-react-app project, nothing else has been done.

There is another thread on this issue here on Github (https://github.com/webpack/webpack-dev-server/issues/2154) and @shaheemMPM suggested:
"Actually that is not an error it's just normal working log
But I also found that log annoying and get rid of it by commenting the log statement..
You can do it by following steps
Goto node_modules -> webpack -> hot folder
Under that you'll find a log.js file open that
edit the section (comment the log under if(level === "info") )
module.exports = function(level, msg) {
if (shouldLog(level)) {
if (level === "info") {
// console.log(msg);
} else if (level === "warning") {
console.warn(msg);
} else if (level === "error") {
console.error(msg);
}
}
};"
The first time I encountered this problem the solution above worked. However I am now building a simple To-do list (I'm new to React) and just commenting out the bit stated above doesn't work. I was wondeing, is there any other file in the node_modules folder that could be displaying the same informational message? If so, maybe commenting it out would help? I don't know what to do to get rid of the issue and it's hard to test anything if the message is popping up

@veronicapc92
check the source of the log in your browser, I'm sure you can find the file that triggers this message.

I also tried to revert back to 3.2.0 by changing the react-scripts in my packages, deleting the node modules directory, and running npm install. It found 2 security vulnerabilities asking me to run "npm audit fix". Then I started the app and the issue was still not resolved.

I just updated the demo repo to react-scripts: 3.4.0 and I am happy to announce that it works.
The message in the console still shows up, but Microsoft edge works now out of the box.
Great job React Team
I am closing the issue


VSCode 1.52 - Git branch missing

VSCode Version: 1.52
OS Version: macOS 11.0.1

Steps to Reproduce:

click on the active branch to show the action bar
compare my two screenshots

VSCode 1.41 :

VSCode 1.42 :

Does this issue occur when all extensions are disabled?: Yes

Same here: Local branches are missing.

I believe this might have been caused by https://github.com/microsoft/vscode/issues/92146
Can you provide the output of git for-each-ref --sort -committerdate --format "%(refname) %(objectname) %(*objectname)" I think something might be going wrong with our parsing there.

The output:
joe733 @ xpsl502x in dcp on  main
➜ git branch -a
* main
  python
  remotes/origin/main

joe733 @ xpsl502x in dcp on  main
➜ git for-each-ref --sort -committerdate --format "%(refname) %(objectname) %(*objectname)"
refs/heads/python bf593588d016e314e9af9eb61602d5d38c989468
refs/remotes/origin/main 9f366c7ec2aefc46e3476506f24947fa0bf15bef
refs/heads/main 9f366c7ec2aefc46e3476506f24947fa0bf15bef

The output:
joe733 @ xpsl502x in dcp on  main
➜ git branch -a
* main
  python
  remotes/origin/main

joe733 @ xpsl502x in dcp on  main
➜ git for-each-ref --sort -committerdate --format "%(refname) %(objectname) %(*objectname)"
refs/heads/python bf593588d016e314e9af9eb61602d5d38c989468
refs/remotes/origin/main 9f366c7ec2aefc46e3476506f24947fa0bf15bef
refs/heads/main 9f366c7ec2aefc46e3476506f24947fa0bf15bef

Thanks! Will be fixed in tomorrow's insiders!

Thanks! Will be fixed in tomorrow's insiders!

Thanks for the fix!

Thanks for the fix!

/verified

/verified


Optimize Docker image.

Run all commands in a single RUN, and wipe out any cached data.

With this, the image size is cut by nearly 50%:
core@ip-10-0-6-211 ~/storm $ docker images
REPOSITORY          TAG                        IMAGE ID            CREATED              VIRTUAL SIZE
storm-optimized     latest                     1f39373ae7b5        About a minute ago   662.8 MB
storm               latest                     103c496716a0        18 minutes ago       1.133 GB
mesosphere/mesos    0.25.0-0.2.70.ubuntu1404   e31a58e079d3        7 weeks ago          523.7 MB
core@ip-10-0-6-211 ~/storm $

thanks, that's much better!


[WIP] Create an AWS Multi Language development container.

This is a rather large template unlike the existing options but it can be paired back by commenting out various bits and I thought it helps demonstrate just how powerful, and flexible, these dev containers can be.

 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.:x: hastarin sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR - Will try to carve out some time here to check it out and get back to you in more detail.
One thought is that we've been talking about adding some "Kitchen Sink" dev container definitions for quickly getting started.  The idea would be that you can just install the kitchen sink image to start, and then refine from there - and it would cover a bunch of different languages.  This actually fits that quite well with what you are doing here, but with an AWS spin.  To keep these together, perhaps we should call this:
"Kitchen Sink - AWS" and kitchensink-aws
A non-cloud kitchen sink could just be kitchensink, and we could then have versions for other cloud vendors if appropriate. Common docs could then tell people to look for "Kitchen Sink" images and see all of them.

A few other questions comments:

Right now this doesn't appear to work as expeced on macOS and Linux.  Some of the volume mounts use Windows specific environment variables like USERPROFILE and APPDATA. We'd want to also support the macOS and Linux equivalent locations (presumably somewhere under HOME).  It also uses USERNAME which does not exist on macOS / Linux - it's USER there.
How critical is posgres to the definition?  Is this used by some of the AWS tools? I ask because database tech is one of those things that tends to go by community - e.g. Mongo is popular in the Node.js space.

@Chuxel I'm happy to refine/improve/change as needed to what you think is going to offer the most benefit to the wider community.  This is just based off something I'm using for a POC project and it's early days yet so I certainly welcome feedback/suggestions.
Postgres/pgAdmin4 are not critical at all.  They can certainly be removed if needed or perhaps just commented out by default but left in the docker-compose as an example?
I had included some notes about Mac/Linux in the README.md.  If need be I can try to make some time this weekend to investigate what the mounts would need to be for those and include some further comments/sections.

@Chuxel I've done what I can without VSCode on macOS/Linux to test it further.  Feel free to review when you get the chance.

You may want to get rid of the continuation character at the end of line 166 of the dockerfile?

Right now this doesn't appear to work as expeced on macOS and Linux.  Some of the volume mounts use Windows specific environment variables like USERPROFILE and APPDATA. We'd want to also support the macOS and Linux equivalent locations (presumably somewhere under HOME).  It also uses USERNAME which does not exist on macOS / Linux - it's USER there.

Just put the two variables next two eachother. USER and USERNAME should not be available on any one system and if it is not set it will be blank.
Example from my devcontainer.json file:
"mounts": [
		"source=${localEnv:HOME}${localEnv:USERPROFILE}/.aws/credentials,target=/home/vscode/.aws/credentials,type=bind"
	],

Note: I did not come up with this but rather found it in a blog post somewhere. It does seem to work well for me, though.

Apologies folks I'd forgotten all about this and haven't worked on it any further. We've got our own containers internally and trying to get this updated is not something I have the time/motivation for at this point. Thanks to all those who provided feedback.


Fix responses and expected results files for regression tests

Description
While looking into something else, I noticed that the *-responses-and-expected-results.yml files for a number of flows were out-of-date:

check-uk-visa
student-finance-forms
state-pension-through-partner
overseas-passports

This PR updates those files and identifies the PR in which they should have been updated in the first place. I haven't done any checking that these changes are sensible, but I plan to ask the authors of the relevant PRs to check for me, because they will have more context.
While fixing the above, I also came across a few other problems:

The changes in #2498 meant that the scripts for generating both the "questions & responses" and "responses & expected results" files were trying to use a local instance of the Whitehall app rather than the production instance.
The questions & responses file for simplified-expenses-checker contained some invalid YAML.
The questions & responses file for landlord-immigration-check was not up-to-date with the stubbed imminence lookups in the regression test nor its responses & expected results file.

I've fixed all of the above and it would be good to get this merged as soon as possible.
Note that I've also noticed that the script for generating the responses & expected results is using the wrong stubbed value of current time for some flows. I plan to address that in a separate PR, but that PR will rely on this one.
External changes
None. These changes only affect test code - no changes to production code.

Apart from my single comment, this all looks good to me.

I wonder whether it's worth adding tests to avoid these sort of problems in future? Do you think the effort of adding such tests would be warranted?

@chrisroos:

I wonder whether it's worth adding tests to avoid these sort of problems in future? Do you think the effort of adding such tests would be warranted?

I'm not sure. It's not obvious to me how these changes were missed. I suspect that because many PRs only involve content changes people may just get into the habit of only updating the regression test artefacts & checksums, and not think about whether these files need updating.
I think the first thing to do would be to check that the documentation makes it clear when you should update these files. Then we could consider adding some kind of check or test to make sure they do get updated. I did wonder whether we could just always run the generate script before running the regression test for that flow. Anyway, I think it's out of scope for this PR, but I've created a Trello card to capture the idea.

I'm going to rebase this against master and open a fresh PR so as not to disrupt the comments on this one.

Superseded by #2527. Closing.


WebNowPlaying-Library ETA?

Hi,
Sorry to disturb you like this by creating issues,  I just wanted to know the ETA of releasing the WebNowPlaying-Library
Thanks!
PS: Sorry for disturbing you.

The new library and CLI adapter are just about done but it might take me a few weeks to release them.
I see you forked PyWNP and noted This repo is currently the same as PyWNP by keifufu. This repo will be updated when the WebNowPlaying-Library is released.
This new library will contain language bindings, as it is written in C and making bindings for it should be possible for most other languages.
I deprecated both the Python and C# libraries to instead create bindings.
It would be greatly appreciated if you contribute to keifufu/WebNowPlaying-Library rather than maintaining your own fork on GitHub/PyPI.
Don't worry about asking questions by the way.

Thank you for letting me know about the ETC!
I would do my best to contribute towards keifufu/WebNowPlaying-Library, However I am still new to programming and the only language i am fully familiar with is JS. (Even though i create python scripts, i dislike python and don't know much of it).
I haven't even touched any other languages (Excluding html and css), so I might be pretty useless...

The library is on GitHub now, but it will remain without releases until further testing has been done. I would appreciate it if you removed your PyWNP fork, unless you want do actually maintain / expand the Python version of course.


Inject structured data into DLP to enhance search engine performance

From @satra: "this would involve injecting the metadata record into the html rendering. here is a pointer: https://developers.google.com/search/docs/advanced/structured-data/intro-structured-data"

This is related to #872.


Please chose a license

Hello from Germany,
nice work here! I'd like to include this in an open source module for a content management system that is well known here.
But I see no license here. Would be great if you'd chose a license for spotlight.
Thanks,
Kim

Hi @SchneiderSIT,
Although haven't touched the project for 2 years I am glad that you have a purpose for it. I updated npm dependencies, added MIT license, and would be glad that it serves someone. Would love to see it in action if you don't mind sharing your project when it's implemented.
Best Regards,
Karlis


Fix statistic of json type

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Fix what
Misestimate the cost of plan node than contains the JSON type. E.g. the following SCAN costs 0 though it has 6001215 rows of data.
MySQL sb_json> explain logical select count(*) from lineorder_flat_json;
+---------------------------------------------------------------------------------------+
| Explain String                                                                        |
+---------------------------------------------------------------------------------------+
| - Output => [4:count]                                                                 |
|     - AGGREGATE(GLOBAL) []                                                            |
|             Estimates: {row: 1, cpu: 0.00, memory: 8.00, network: 0.00}               |
|             4:count := count()                                                        |
|         - EXCHANGE(GATHER)                                                            |
|                 Estimates: {row: 6001215, cpu: 0.00, memory: 0.00, network: 0.00}     |
|             - SCAN [lineorder_flat_json] => [3:j]                                     |
|                     Estimates: {row: 6001215, cpu: 0.00, memory: 0.00, network: 0.00} |
|                     partitionRatio: 7/7, tabletRatio: 336/336                         |
+---------------------------------------------------------------------------------------+
9 rows in set

Modification

Fix typeSize estimation of JSON
Use char_length function to calculate the row-size of JSON
Modify the Statistic, make the least row-size to 1, avoid huge cost estimate error

Problem Summary(Required) ：

Statistic for JSON type is inaccurate, which make select count(*) from json_table generates one stage aggregation plan, which is in-efficient.

@Mergifyio backport branch-2.2

Statistic for JSON type is inaccurate, which make select count(*) from json_table generates one stage aggregation plan, which is in-efficient.

please  add  UT cover  it.

[FE PR Coverage check]
:disappointed: fail : 9 / 12 (75.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/PrimitiveType.java
1
4
25.00%

:large_blue_circle:
com/starrocks/catalog/Table.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/Statistics.java
6
6
100.00%

:large_blue_circle:
com/starrocks/statistic/StatisticExecutor.java
1
1
100.00%


Thank you

This is clearly not an issue.
Just wanted to say a big thanks for the package, I was really struggling with Semantic not compiling.
Still, while I'm at it, any idea how to make Meteor watch .variables and .overrides files?

(well, just renamed all /site files with suffix .import.less and it works :)

I’m very happy that this package also helps other people! :)

Just to let you know there is a package called semantic:ui which lets you customize Semantic UI with all the less files etc. :)


NDRS-521 remove unbond_purse arg in withdraw_bid contract

Removing the unbond_purse arg to allow casper-client 1.4.0 to use this contract.
This will be undone once the fix of client for NDRS-521 is complete.

Accidentally based on release rather than master.  Cleaned up.

Don't apply this (or other similar changes to these contracts) to master; the contracts are correct. There is a bug ticket to fix the client to handle Optional args.

client resolved, no longer needed.


Load files parallelly

Please describe the feature you'd like to see
Currently, we load files to the table sequentially. We can alternatively use get_file_list to load_file parallelly.
 LoadFile.partial(
        task_id="load_gcs_to_bq",
        output_table=Table(
            metadata=Metadata(
                schema=ASTRO_BIGQUERY_DATASET,
            ),
            conn_id=ASTRO_GCP_CONN_ID,
        ),
        use_native_support=True,
    ).expand(input_file=get_file_list(path=GCS_BUCKET, conn_id=ASTRO_GCP_CONN_ID))

But in the above code, get_file_list can result in 100s of files, which will result in 100s of tasks.
Describe the solution you'd like
for example, GCS_BUCKET has the following files:
s3://tmp/test1.csv
s3://tmp/test2.csv
s3://tmp/test3.csv
s3://tmp/test4.csv
s3://tmp/test5.csv
s3://tmp/test6.csv

Currently get_file_list will produce:
[
  s3://tmp/test1.csv,
  s3://tmp/test2.csv,
  s3://tmp/test3.csv,
  s3://tmp/test4.csv,
  s3://tmp/test5.csv,
  s3://tmp/test6.csv
]

We can have a partial approach where get_file_list can produce buckets for files like where we can specify the max bucket size by get_file_list(path=GCS_BUCKET, conn_id=ASTRO_GCP_CONN_ID, max_bucket_size=3):
[
   [s3://tmp/test1.csv, s3://tmp/test2.csv, s3://tmp/test3.csv]
   [s3://tmp/test4.csv, s3://tmp/test5.csv, s3://tmp/test6.csv]
]

Then, load_file should be able to process the list of files so that we can load file parallelly and simultaneously control the number of tasks generated. Since there are only two items generated it will result in two tasks and not six tasks.
 LoadFile.partial(
        task_id="load_gcs_to_bq",
        output_table=Table(
            metadata=Metadata(
                schema=ASTRO_BIGQUERY_DATASET,
            ),
            conn_id=ASTRO_GCP_CONN_ID,
        ),
        use_native_support=True,
    ).expand(input_file=get_file_list(path=GCS_BUCKET, conn_id=ASTRO_GCP_CONN_ID, max_bucket_size=3))

Are there any alternatives to this feature?
Open to suggestions
Acceptance Criteria

[ ] All checks and tests in the CI should pass
[ ] Unit tests (90% code coverage or more, once available)
[ ] Integration tests (if the feature relates to a new database or external service)
[ ] Example DAG
[ ] Docstrings in reStructuredText for each of  methods, classes, functions and module-level attributes (including Example DAG on how it should be used)
[ ] Exception handling in case of errors
[ ] Logging (are we exposing useful information to the user? e.g. source and destination)
[ ] Improve the documentation (README, Sphinx, and any other relevant)
[ ] How to use Guide for the feature (example)

Consider letting the user to specify this max_bucket_size attribute


Scrollbars do not appear at all on MacOS 11.0.1

Steps to reproduce:
Open Todo example
Add 20 items
Expected: Scrollbar appears on right
Actual: No scrollbar is visible
Have tried on my other app and cannot get VerticalScrollbar to display

That's how it looks on my macOS machine with 18afa24fe0b24cc998eade489bda78357d78c866. Could it be that your monitor is too dark to see scrollbars?

Also try to resize the window. Will scrollbar appear?

Also on 18afa24fe0b24cc998eade489bda78357d78c866. It seems like it isn't even allowing space for it (adding a border to VerticalScrollbar doesn't show either)

I think I wasn't on the latest commit sorry. It is working now.

I did notice that sometimes I needed to resize the window for the scollbar to appear yes

I needed to resize the window for the scollbar to appear

Scrollbar should appear if there is more items than can be displayed in the list.
Also there is another bug:
https://github.com/JetBrains/compose-jb/issues/47

Steps to reproduce:

Change to use ScrollableColumn in Todo app sample.
Run Todo app
Add 30 items
Close app.
Run Todo app again.
Expected: Scrollbar is visble
Actual: No scrollbar appears. Scrolling the list does not make the scrollbar appear. Resizing the window makes it appear.

Thanks! I reproduced the issue. Will look at it.

Fixed in 0.2.0-build132

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Update PR Template MD to warn about PullRequests on Forks

A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.

/azp run TransportPackage-Foundation-PR

@kythant PR builds or forks works now, you can revert this PR and remove the guidance.

Oh what has changed?

From: Jevan Saks @.>
Sent: Thursday, March 28, 2024 8:51 AM
To: microsoft/WindowsAppSDK @.>
Cc: Will Thant @.>; Mention @.>
Subject: Re: [microsoft/WindowsAppSDK] Update PR Template MD to warn about PullRequests on Forks (PR #4294)
@kythanthttps://github.com/kythant PR builds or forks works now, you can revert this PR and remove the guidance.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/WindowsAppSDK/pull/4294#issuecomment-2025548458, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALQ7TUEDPO7QEBJBIUPPFDTY2Q37FAVCNFSM6AAAAABFLZA4HWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGU2DQNBVHA.
You are receiving this because you were mentioned.Message ID: @.***>


License text

Greetings! Would it be possible to add another license to your project, preferably MIT or BSD license?
Background:
I recently started working for TOPTICA Photonics and we would like to use your code. However, your zero-clause Guthrie license does not explicitly state that we may use and modify it, etc.

yeah, we can accommodate that. I'll make it Apache unless anyone complains.

If you submit a PR that changes the license to Apache then I will happily merge it

Fixed in https://github.com/OxfordIonTrapGroup/wand/pull/58.


Fixture adjustments

Couple of additions to the default settings fixtures:
Social Accounts

<EMAIL_ADDRESS>- https://twitter.com/tryghost
<EMAIL_ADDRESS>- https://www.facebook.com/ghost

Design/Navigation

Home -<EMAIL_ADDRESS>(already exists)
Tag -<EMAIL_ADDRESS>Author -<EMAIL_ADDRESS>Help - https://help.ghost.org

Ghost User

{{author.twitter}} - https://twitter.com/tryghost
{{author.facebook}} - https://www.facebook.com/ghost
{{author.location}} - The Internet
{{author.website}} - https://ghost.org
{{author.bio}} - You can delete this user to remove all the welcome posts (already exists)

(Optional, but would be nice:)
Set default {{author.profile_image}} for Ghost user - should look like https://demo.ghost.io/author/ghost/ - it's fine to add this image file to Ghost core, don't need to load remotely, if that's easier.

Closed via https://github.com/TryGhost/Ghost/commit/f4e9563f94e70e53e51fc789406c9424bfe54063. This is part of the Ghost 2.0 branch.


[Docs] Clarify in the AsyncStorage docs that it is global to the app, not OS

There was some confusion over whether AsyncStorage is shared across the entire OS (definitely not); clearing that up.

Yeah this is really helpful especially for iOS newbies as I am when we discussed in the IRC channel with @ide.
BTW, the docs for clear are confusing as well:
static clear(callback?: ?(error: ?Error) => void)

Erases all AsyncStorage for all clients, libraries, etc. You probably don't want to call this - use removeItem or multiRemove to clear only your own keys instead. Returns a Promise object.

What's clients here?

Yeah, iOS n00bs might not realize that apps are sandboxed at the OS level...

What's clients here?

Any code that calls the AsyncStorage API.

@facebook-github-bot import


FI-1310 Lock input

Codecov Report

Merging #36 (ddb855f) into main (c408192) will increase coverage by 1.22%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #36      +/-   ##
==========================================
+ Coverage   93.64%   94.87%   +1.22%
==========================================
  Files          88      102      +14
  Lines        1937     2262     +325
==========================================
+ Hits         1814     2146     +332
+ Misses        123      116       -7

Impacted Files
Coverage Δ

dev_suites/demo_ig_stu1/groups/demo_group.rb
93.06% <100.00%> (+0.21%)
:arrow_up:

lib/inferno/test_runner.rb
100.00% <0.00%> (ø)

lib/inferno/config/application.rb
100.00% <0.00%> (ø)

lib/inferno/dsl/request_storage.rb
100.00% <0.00%> (ø)

lib/inferno/apps/web/serializers/test.rb
100.00% <0.00%> (ø)

lib/inferno/apps/web/serializers/test_group.rb
100.00% <0.00%> (ø)

dev_suites/smart/code_received_test.rb
100.00% <0.00%> (ø)

dev_suites/smart/token_exchange_test.rb
100.00% <0.00%> (ø)

dev_suites/smart/standalone_launch_group.rb
94.44% <0.00%> (ø)

dev_suites/smart/token_response_body_test.rb
100.00% <0.00%> (ø)

... and 15 more

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 c408192...ddb855f. Read the comment docs.

The primary use case of locking inputs is for someone reusing a set of tests but want to restrict options, for example, we want to see you pass the 'SMART Launch Test' with Confidential Client locked to 'true'.   I'm not sure how often a test writer would write a test with an input that can never be changed (then it isn't really an input).  We can't lock params yet when you create a test from another test yet, right @Jammjammjamm?  So this may be premature, or we can consider this to lay the foundation for that later?

I would expect locking an input to just prevent the value from being changed by the user. It could be locked to default value or a value set by a previous test. We use this in program for things like preventing the user from changing the access token received during the launch.

I haven't looked too closely yet, but the changes in this PR should be enough to allow us to set an input as locked on an imported test.

Picture of changes. After talking with Rob in early September, this is probably the best quick fix barring a major UI change.

Rebasing/testing/linting was a pain because I did something wrong along the way, but should be all good now. UI should look as pictured directly above.

It looks like the submit button doesn't work when running the demo tests, even though I think i've filled in all the non-optional fields?


fix: Array field issues

Fixes #618
Potentially fixes #573

Codecov Report
Attention: Patch coverage is 50.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 88.82%. Comparing base (51ef17f) to head (9aa3bc2).
Report is 2 commits behind head on main.

Files
Patch %
Lines

packages/form-core/src/utils.ts
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #635      +/-   ##
==========================================
- Coverage   88.91%   88.82%   -0.10%
==========================================
  Files          28       28
  Lines         812      814       +2
  Branches      187      188       +1
==========================================
+ Hits          722      723       +1
- Misses         83       84       +1
  Partials        7        7

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


Looking to hire developer to fix my pool

https://pool.mining.sg/mining_key
Blocks are being mined on zencash but nothing is  being paid out and individual stats page doesn't work... desperately need help...

I'll take a look.
irc: xbrooks irc.freenode.com (always lurking in #evergreencoin
bitcointalk: nino_decoy


Update to v0.14.0-rc3

Backlinking to purescript/purescript#3942

CI is now failing due to two reasons:

Foldable1 now includes foldr1 and foldl1
kind annotation compiler warnings

@paluh, I've fixed the kind annotations in this PR to your branch: https://github.com/paluh/purescript-transformers/pull/1
Please merge that when you get a chance. After its merged, the only thing blocking this PR is the purescript-lazy dependency. Its Foldable1 instance for Lazy needs to be updated.

@JordanMartinez I'm not sure how I was able to don't notice these warnings. Sorry. You fix is included in this PR now.

This is blocked by purescript-arrays now due to using it as a test dependency.


worker pod crashing

I deployed airflow webserver, scheduler, postgres, redis, worker, flower on different openshift pods.
webserver, scheduler, postgres, redis, flower are successfully deployed & running.
Scheduler is performing LPUSH into redis queue with task instance.
Can see airflow UI with dags, dag runs & task instance.
Status of Dagruns remains running & task instance queued.
Worker deployment is crashing shows only following logs in the log terminal of worker pod:
[2019-05-28 14:04:36,401] {{settings.py:174}} INFO - settings.configure_orm(): Using pool settings. pool_size=5, pool_recycle=1800, pid=1
| [2019-05-28 14:04:37,401] {{init.py:51}} INFO - Using executor CeleryExecutor
Logs on webserver's log terminal are:
[2019-05-28 13:15:15,595] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
| [2019-05-28 13:15:16,765] {{settings.py:174}} INFO - settings.configure_orm(): Using pool settings. pool_size=5, pool_recycle=1800, pid=192
  | [2019-05-28 13:15:17 +0000] [192] [INFO] Starting gunicorn 19.9.0
  | [2019-05-28 13:15:17 +0000] [192] [INFO] Listening at: http://<IP_ADDRESS>:8081  (192)
  | [2019-05-28 13:15:17 +0000] [192] [INFO] Using worker: sync
  | [2019-05-28 13:15:17 +0000] [197] [INFO] Booting worker with pid: 197
  | [2019-05-28 13:15:17 +0000] [198] [INFO] Booting worker with pid: 198
  | [2019-05-28 13:15:17 +0000] [199] [INFO] Booting worker with pid: 199
  | [2019-05-28 13:15:17 +0000] [200] [INFO] Booting worker with pid: 200
  | Running the Gunicorn Server with:
  | Workers: 4 sync
  | Host: <IP_ADDRESS>:8081
  | Timeout: 120
  | Logfiles: - -
  | =================================================================
  | [2019-05-28 13:15:18,036] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:18,529] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:18,743] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:18,929] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:20,740] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
  | [2019-05-28 13:15:21,029] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
  | [2019-05-28 13:15:21,047] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
  | [2019-05-28 13:15:21,132] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags......
Anybody can assist on fixing this up.
Thanks In Advance.
Hitesh

I am facing the same issue
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: apache-airflow[google_auth] in /home/airflow/.local/lib/python3.6/site-packages (1.10.15)
Requirement already satisfied: python-daemon>=2.1.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.2.4)
Requirement already satisfied: json-merge-patch==0.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.2)
Requirement already satisfied: cached-property~=1.5 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.2)
Requirement already satisfied: flask-swagger<0.3,>=0.2.13 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.2.14)
Requirement already satisfied: pygments<3.0,>=2.0.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.7.2)
Requirement already satisfied: flask-login<0.5,>=0.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.4.1)
Requirement already satisfied: pendulum==1.4.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.4.4)
Requirement already satisfied: tabulate<0.9,>=0.7.5 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.8.7)
Requirement already satisfied: dill<0.4,>=0.2.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.3.3)
Requirement already satisfied: lazy-object-proxy<1.5.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.4.3)
Requirement already satisfied: pandas<2.0,>=0.17.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.1.4)
Requirement already satisfied: psutil<6.0.0,>=4.2.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (5.7.3)
Requirement already satisfied: croniter<0.4,>=0.3.17 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.3.36)
Requirement already satisfied: cryptography>=0.9.3; python_version >= "3.0" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.2.1)
Requirement already satisfied: packaging in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (20.7)
Requirement already satisfied: iso8601>=0.1.12 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.1.13)
Requirement already satisfied: importlib-metadata~=2.0; python_version < "3.9" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.1.0)
Requirement already satisfied: sqlalchemy~=1.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.3.20)
Requirement already satisfied: cattrs<1.1.0,>=1.0; python_version <= "3.6" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.0.0)
Requirement already satisfied: colorlog==4.0.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.0.2)
Requirement already satisfied: email-validator in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.1.2)
Requirement already satisfied: funcsigs<2.0.0,>=1.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.0.2)
Requirement already satisfied: python-dateutil<3,>=2.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.8.1)
Requirement already satisfied: configparser<3.6.0,>=3.5.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.5.3)
Requirement already satisfied: jsonschema~=3.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.2.0)
Requirement already satisfied: werkzeug<1.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.16.1)
Requirement already satisfied: flask-appbuilder~=2.2; python_version >= "3.6" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.3.4)
Requirement already satisfied: argcomplete~=1.10 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.12.2)
Requirement already satisfied: markdown<3.0,>=2.5.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.6.11)
Requirement already satisfied: thrift>=0.11.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.13.0)
Requirement already satisfied: future<0.19,>=0.16.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.18.2)
Requirement already satisfied: setproctitle<2,>=1.1.8 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.2)
Requirement already satisfied: attrs<21.0,>=20.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (20.3.0)
Requirement already satisfied: marshmallow-sqlalchemy<0.24.0,>=0.16.1; python_version >= "3.6" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.23.1)
Requirement already satisfied: pep562~=1.0; python_version < "3.7" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.0)
Requirement already satisfied: flask-admin==1.5.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.4)
Requirement already satisfied: jinja2<2.12.0,>=2.10.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.11.2)
Requirement already satisfied: python-slugify<5.0,>=3.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.0.1)
Requirement already satisfied: flask-caching<1.4.0,>=1.3.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.3.3)
Requirement already satisfied: alembic<2.0,>=1.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.4.3)
Requirement already satisfied: importlib-resources~=1.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.0)
Requirement already satisfied: flask-wtf<0.15,>=0.14.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.14.3)
Requirement already satisfied: zope.deprecation<5.0,>=4.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.4.0)
Requirement already satisfied: typing-extensions>=3.7.4; python_version < "3.8" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (<IP_ADDRESS>)
Requirement already satisfied: tzlocal<2.0.0,>=1.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.1)
Requirement already satisfied: requests<2.24.0,>=2.20.0; python_version >= "3.0" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.23.0)
Requirement already satisfied: gunicorn<21.0,>=19.5.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (20.0.4)
Requirement already satisfied: flask<2.0,>=1.1.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.1.2)
Requirement already satisfied: tenacity==4.12.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.12.0)
Requirement already satisfied: graphviz>=0.12 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.15)
Requirement already satisfied: python-nvd3~=0.15.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.15.0)
Requirement already satisfied: unicodecsv>=0.14.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.14.1)
Requirement already satisfied: sqlalchemy-jsonfield~=0.9; python_version >= "3.5" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.9.0)
Requirement already satisfied: Flask-OAuthlib<0.9.6,>=0.9.1; extra == "google_auth" in /usr/local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.9.5)
Collecting requests-oauthlib==1.1.0; extra == "google_auth"
  Downloading requests_oauthlib-1.1.0-py2.py3-none-any.whl (21 kB)
Collecting oauthlib!=2.0.3,!=2.0.4,!=2.0.5,<3.0.0,>=1.1.2; extra == "google_auth"
  Downloading oauthlib-2.1.0-py2.py3-none-any.whl (121 kB)
Requirement already satisfied: docutils in /home/airflow/.local/lib/python3.6/site-packages (from python-daemon>=2.1.1->apache-airflow[google_auth]) (0.15.2)
Requirement already satisfied: setuptools in /usr/local/lib/python3.6/site-packages (from python-daemon>=2.1.1->apache-airflow[google_auth]) (54.1.1)
Requirement already satisfied: lockfile>=0.10 in /home/airflow/.local/lib/python3.6/site-packages (from python-daemon>=2.1.1->apache-airflow[google_auth]) (0.12.2)
Requirement already satisfied: PyYAML>=5.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-swagger<0.3,>=0.2.13->apache-airflow[google_auth]) (5.3.1)
Requirement already satisfied: pytzdata>=2<IP_ADDRESS> in /home/airflow/.local/lib/python3.6/site-packages (from pendulum==1.4.4->apache-airflow[google_auth]) (2020.1)
Requirement already satisfied: numpy>=1.15.4 in /home/airflow/.local/lib/python3.6/site-packages (from pandas<2.0,>=0.17.1->apache-airflow[google_auth]) (1.19.4)
Requirement already satisfied: pytz>=2017.2 in /home/airflow/.local/lib/python3.6/site-packages (from pandas<2.0,>=0.17.1->apache-airflow[google_auth]) (2020.4)
Requirement already satisfied: natsort in /home/airflow/.local/lib/python3.6/site-packages (from croniter<0.4,>=0.3.17->apache-airflow[google_auth]) (7.1.0)
Requirement already satisfied: six>=1.4.1 in /home/airflow/.local/lib/python3.6/site-packages (from cryptography>=0.9.3; python_version >= "3.0"->apache-airflow[google_auth]) (1.15.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /home/airflow/.local/lib/python3.6/site-packages (from cryptography>=0.9.3; python_version >= "3.0"->apache-airflow[google_auth]) (1.14.4)
Requirement already satisfied: pyparsing>=2.0.2 in /home/airflow/.local/lib/python3.6/site-packages (from packaging->apache-airflow[google_auth]) (2.4.7)
Requirement already satisfied: zipp>=0.5 in /home/airflow/.local/lib/python3.6/site-packages (from importlib-metadata~=2.0; python_version < "3.9"->apache-airflow[google_auth]) (3.4.0)
Requirement already satisfied: dnspython>=1.15.0 in /home/airflow/.local/lib/python3.6/site-packages (from email-validator->apache-airflow[google_auth]) (1.16.0)
Requirement already satisfied: idna>=2.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from email-validator->apache-airflow[google_auth]) (2.8)
Requirement already satisfied: pyrsistent>=0.14.0 in /home/airflow/.local/lib/python3.6/site-packages (from jsonschema~=3.0->apache-airflow[google_auth]) (0.17.3)
Requirement already satisfied: click<8,>=6.7 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (6.7)
Requirement already satisfied: PyJWT>=1.7.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.7.1)
Requirement already satisfied: marshmallow<3.0.0,>=2.18.0 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (2.21.0)
Requirement already satisfied: Flask-Babel<2,>=1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.0.0)
Requirement already satisfied: Flask-SQLAlchemy<3,>=2.4 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (2.4.4)
Requirement already satisfied: apispec[yaml]<2,>=1.1.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.3.3)
Requirement already satisfied: Flask-OpenID<2,>=1.2.5 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.2.5)
Requirement already satisfied: Flask-JWT-Extended<4,>=3.18 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (3.25.0)
Requirement already satisfied: marshmallow-enum<2,>=1.4.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.5.1)
Requirement already satisfied: colorama<1,>=0.3.9 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.4.4)
Requirement already satisfied: sqlalchemy-utils<1,>=0.32.21 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.36.8)
Requirement already satisfied: prison<1.0.0,>=0.1.3 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.1.3)
Requirement already satisfied: wtforms in /home/airflow/.local/lib/python3.6/site-packages (from flask-admin==1.5.4->apache-airflow[google_auth]) (2.3.3)
Requirement already satisfied: MarkupSafe>=0.23 in /home/airflow/.local/lib/python3.6/site-packages (from jinja2<2.12.0,>=2.10.1->apache-airflow[google_auth]) (1.1.1)
Requirement already satisfied: text-unidecode>=1.3 in /home/airflow/.local/lib/python3.6/site-packages (from python-slugify<5.0,>=3.0.0->apache-airflow[google_auth]) (1.3)
Requirement already satisfied: Mako in /home/airflow/.local/lib/python3.6/site-packages (from alembic<2.0,>=1.0->apache-airflow[google_auth]) (1.1.3)
Requirement already satisfied: python-editor>=0.3 in /home/airflow/.local/lib/python3.6/site-packages (from alembic<2.0,>=1.0->apache-airflow[google_auth]) (1.0.4)
Requirement already satisfied: itsdangerous in /home/airflow/.local/lib/python3.6/site-packages (from flask-wtf<0.15,>=0.14.2->apache-airflow[google_auth]) (1.1.0)
Requirement already satisfied: certifi>=2017.4.17 in /home/airflow/.local/lib/python3.6/site-packages (from requests<2.24.0,>=2.20.0; python_version >= "3.0"->apache-airflow[google_auth]) (2020.11.8)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /home/airflow/.local/lib/python3.6/site-packages (from requests<2.24.0,>=2.20.0; python_version >= "3.0"->apache-airflow[google_auth]) (1.25.11)
Requirement already satisfied: chardet<4,>=3.0.2 in /home/airflow/.local/lib/python3.6/site-packages (from requests<2.24.0,>=2.20.0; python_version >= "3.0"->apache-airflow[google_auth]) (3.0.4)
Requirement already satisfied: typing>=3.6; python_version < "3.7" in /home/airflow/.local/lib/python3.6/site-packages (from sqlalchemy-jsonfield~=0.9; python_version >= "3.5"->apache-airflow[google_auth]) (<IP_ADDRESS>)
Requirement already satisfied: pycparser in /home/airflow/.local/lib/python3.6/site-packages (from cffi!=1.11.3,>=1.8->cryptography>=0.9.3; python_version >= "3.0"->apache-airflow[google_auth]) (2.20)
Requirement already satisfied: Babel>=2.3 in /home/airflow/.local/lib/python3.6/site-packages (from Flask-Babel<2,>=1->flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (2.9.0)
Requirement already satisfied: python3-openid>=2.0 in /home/airflow/.local/lib/python3.6/site-packages (from Flask-OpenID<2,>=1.2.5->flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (3.2.0)
Requirement already satisfied: defusedxml in /home/airflow/.local/lib/python3.6/site-packages (from python3-openid>=2.0->Flask-OpenID<2,>=1.2.5->flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.6.0)
Installing collected packages: oauthlib, requests-oauthlib
  Attempting uninstall: oauthlib
    Found existing installation: oauthlib 3.1.0
    Uninstalling oauthlib-3.1.0:
      Successfully uninstalled oauthlib-3.1.0
  Attempting uninstall: requests-oauthlib
    Found existing installation: requests-oauthlib 1.3.0
    Uninstalling requests-oauthlib-1.3.0:
      Successfully uninstalled requests-oauthlib-1.3.0
Successfully installed oauthlib-2.1.0 requests-oauthlib-1.1.0
WARNING: You are using pip version 20.2.4; however, version 21.2.4 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
  ____________       _____________
 ____    |__( )_________  __/__  /________      __
____  /| |_  /__  ___/_  /_ __  /_  __ \_ | /| / /
___  ___ |  / _  /   _  __/ _  / / /_/ /_ |/ |/ /
 _/_/  |_/_/  /_/    /_/    /_/  \____/____/|__/
[2021-08-15 15:22:37,380] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:39,337] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:39,338] {dagbag.py:417} INFO - Filling up the DagBag from /dev/null
[2021-08-15 15:22:39,969] {security.py:478} INFO - Start syncing user roles.
[2021-08-15 15:22:40,349] {security.py:388} INFO - Fetching a set of all permission, view_menu from FAB meta-table
[2021-08-15 15:22:40,507] {security.py:331} INFO - Cleaning faulty perms
[2021-08-15 15:22:42 +0000] [36] [INFO] Starting gunicorn 20.0.4
[2021-08-15 15:22:42 +0000] [36] [INFO] Listening at: http://<IP_ADDRESS>:8080 (36)
[2021-08-15 15:22:42 +0000] [36] [INFO] Using worker: sync
[2021-08-15 15:22:42 +0000] [40] [INFO] Booting worker with pid: 40
[2021-08-15 15:22:42 +0000] [41] [INFO] Booting worker with pid: 41
[2021-08-15 15:22:42 +0000] [42] [INFO] Booting worker with pid: 42
[2021-08-15 15:22:42,201] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:42 +0000] [43] [INFO] Booting worker with pid: 43
[2021-08-15 15:22:42,252] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:42,344] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:42,468] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:43,483] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,485] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:22:43,558] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,559] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:22:43,585] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,587] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:22:43,676] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,678] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:40)
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:41)
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:42)
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:43)
[2021-08-15 15:24:43 +0000] [112] [INFO] Booting worker with pid: 112
[2021-08-15 15:24:43 +0000] [113] [INFO] Booting worker with pid: 113
[2021-08-15 15:24:43 +0000] [114] [INFO] Booting worker with pid: 114
[2021-08-15 15:24:43 +0000] [115] [INFO] Booting worker with pid: 115
[2021-08-15 15:24:43,597] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:43,616] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:43,646] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:43,691] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:44,848] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,850] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:44,933] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,935] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:44,935] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,937] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:44,973] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,975] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:112)
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:113)
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:114)
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:115)
[2021-08-15 15:26:44 +0000] [184] [INFO] Booting worker with pid: 184
[2021-08-15 15:26:44 +0000] [185] [INFO] Booting worker with pid: 185
[2021-08-15 15:26:44 +0000] [186] [INFO] Booting worker with pid: 186
[2021-08-15 15:26:44 +0000] [187] [INFO] Booting worker with pid: 187
[2021-08-15 15:26:44,914] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:44,924] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:44,973] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:45,059] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:46,167] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,169] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:46,192] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,194] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:46,194] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,196] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:46,250] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,252] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:184)
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:185)
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:186)
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:187)
[2021-08-15 15:28:45 +0000] [256] [INFO] Booting worker with pid: 256
[2021-08-15 15:28:46 +0000] [257] [INFO] Booting worker with pid: 257
[2021-08-15 15:28:46 +0000] [258] [INFO] Booting worker with pid: 258
[2021-08-15 15:28:46 +0000] [259] [INFO] Booting worker with pid: 259
[2021-08-15 15:28:46,200] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:46,243] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:46,271] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:46,277] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:47,398] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,400] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:47,559] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,561] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:47,636] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,638] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:47,648] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,650] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags

The airflow webserver workers keeps timing out


Fix oslo-config and octavia-ui configs

Fix symlink for dashboard content (which isn't installed by default
in Python path) for octavia-ui and replace DNF installation with
test-requirements.txt installation for oslo-config.

Ideally I'd like to see this as two commits.  What're you're doing is fixing things, true but logicallly the fixes are "different".   Ultimately that's a personal style issue and no reason to hold up this PR.  I do agree with @yazug that barbicanclient shoudl be mentioned.


AttributeError: module 'bar_chart_race' has no attribute 'prepare_long_data'

AttributeError                            Traceback (most recent call last)
 in
<1 import bar_chart_race as bcr       2  ----> 3 change_values,change_ranks = bcr.prepare_long_data(change2,index = "week",columns = "Location",values = "Amount Spent",steps_per_period=1)       4        5 change_values.head()>````

Can you make sure you upgrade to the most recent version? Thanks!


Haskell compatible utxo and certs

Description
Address issue #525.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[x] Code is formatted according to CONTRIBUTING.md
[x] Self-reviewed the diff

@WhatisRT I believe I implemented your suggested changes as you intended.  Everything type-checks now, but I still can't get it to pass the CI.  I will try again over the weekend.


Create a release of latest master.

Also bump the version in pentagon/lib/pentagon/vpc/main.tf

Performed this, however realized that we need circle.yaml to have a release stanza. Will be re-releasing as v2.1.1


Use Service Account JSON Key File

It is recommended by Google that we use Service Account credentials make
API calls from server. See this issue comment for details.
Docs and tests are not yet updated. DO NOT MERGE.

closing, but if you'd like to update, pls reopen


change resume to portfolio multipage website

Making it to a full multipage portfolio website will bring a resume to a new level


chore: add languages

https://prismjs.com/#supported-languages:~:text=Docker - docker%2C dockerfile
Needed for Dockerfile code blocks in New Relic docs. Example.

this might need a fix or feat commit in order for it to be published to NPM and used in docs site

looks like these are already in docs config too. does it not work there already? https://github.com/newrelic/docs-website/blob/develop/gatsby-config.js