Restricted Admins need to be distinguished from standard user.

Internal reference: SURE-3906
dashboard reference: https://github.com/rancher/dashboard/issues/4954
Issue description:
Restricted Admin users are unable to see the Global Settings menu item under CONFIGURATION.
Restricted Admin only have resourceMethods: [GET]. So we don't have a way to distinguish between standard user and a restricted admin user.
"id": "management.cattle.io.setting",
    "type": "schema",
    "links": {
      "collection": "https://localhost:8005/v1/management.cattle.io.settings",
      "self": "https://localhost:8005/v1/schemas/management.cattle.io.setting"
    },
    "pluralName": "management.cattle.io.settings",
    "resourceMethods": [
      "GET"
    ],

Business impact:
Customers using Hosted Rancher cannot view global settings in the UI
Troubleshooting steps:
none
Repro steps:

Create a restricted admin user.
Log in as the restricted admin user.
Click the menu icon in the top left corner

Workaround:
Is workaround available and implemented?

yes
What is the workaround:
You can navigate directly to the URL, for example https://support.rancher.cloud/dashboard/c/c-p24tr/settings/management.cattle.io.setting

Actual behavior:
Global Settings menu is missing from UI for restricted admin users.
Expected behavior:
Global Settings menu should be available for restricted admin users. See also [https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/global-permissions/] (Under Settings, Restricted Admin should be able to list, but not edit, settings)

@Shavindra Would you mind explaining a bit more what you are looking for here? According to the docs that you linked - standard users and restricted admins should both be able to list settings.
From reading that page I would expect this button's behavior to be the same for restricted admin and standard user - can you elaborate on why they should be different?

@gaktive or @nwmac - Do you think we could get an update from @Shavindra so that we can maybe put this into someone's queue to look at?


项目运行一直报错，找不到idea_version 但是这个是对的版本，能给一个编译的步骤吗，或者是不是不用master？

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

你好
这边没有master分支。
请确认你使用的分支名。
如果不能编译那么流水线会过不去。
请参考流水线。
https://github.com/XenoAmess/p3c/blob/xenoamess_maintain_fork/.github/workflows/build.yml


changing tensor's shape/Keras implementation

Hi
I am going to implement the model on Keras. In concatenate layer, it doesn't let me to concatenate tensors because of different dimensions. Will flattening them affect the network's performance?

OS: Linux

Tensorflow Version:  1.14.0

OpenCV Version: <IP_ADDRESS>

Keras version: 2.2.4

We have reimplemented the models in Keras successfully beforehand. To clarify which model and which layer are you referring to (FireNet or InceptionV1-OnFire) ?

Thanks for your help.
The model is inceptionOnFire.
The layer is the first concatenate layer (I think all concatenate layers are the same).
Here is my code:
def inc_v1_on_fire(input_shape):

    input_layer = K.Input(input_shape)
    conv_7_7 = K.Conv2D(64,
                      7,
                      strides = 2,
                      activation = 'relu',
                      padding = 'same',
                      name = 'conv1_7_7_s2')(input_layer)

    pool1_3_3 = K.MaxPooling2D(3,
                            strides = 2,
                            padding = 'same')(conv_7_7)
    pool1_3_3 = LRN()(pool1_3_3)

    conv2_3_3_reduce = K.Conv2D(64,
                               1,
                               activation = 'relu',
                               name = 'conv2_3_3_reduce')(pool1_3_3)
    conv2_3_3 = K.Conv2D(128,
                        3,
                        activation='relu',
                        name='conv2_3_3')(conv2_3_3_reduce)

    conv2_3_3 = LRN()(conv2_3_3)
    pool2_3_3 = K.MaxPooling2D(3,
                             strides = 2,
                             padding = 'same',
                             name ='pool2_3_3_s2')(conv2_3_3)

    inception_3a_1_1 = K.Conv2D(64,
                               1,
                               activation = 'relu',
                               name = 'inception_3a_1_1')(pool2_3_3)

    inception_3a_3_3_reduce = K.Conv2D(96,
                                      1,
                                      activation ='relu',
                                      name='inception_3a_3_3_reduce')(pool2_3_3)

    inception_3a_3_3 = K.Conv2D(128,
                               3,
                               activation = 'relu',
                               name = 'inception_3a_3_3')(inception_3a_3_3_reduce)
    inception_3a_5_5_reduce = K.Conv2D(16,
                                      1,
                                      activation = 'relu',
                                      name ='inception_3a_5_5_reduce')(pool2_3_3)
    inception_3a_5_5 = K.Conv2D(32,
                               5,
                               activation='relu',
                               name= 'inception_3a_5_5')(inception_3a_5_5_reduce)
    inception_3a_pool = K.MaxPooling2D(3,
                                    strides = 1,
                                    padding = 'same')(pool2_3_3)
    inception_3a_pool_1_1 = K.Conv2D(32,
                                    1,
                                    activation='relu',
                                    name='inception_3a_pool_1_1')(inception_3a_pool)

    # merge the inception_3a__
    inception_3a_output = K.Concatenate(axis=3)([inception_3a_1_1,
                                       inception_3a_3_3,
                                       inception_3a_5_5,
                                       inception_3a_pool_1_1])

    inception_3b_1_1 = K.Conv2D(128,
                              1,
                              activation='relu',
                              name = 'inception_3b_1_1')(inception_3a_output)
    inception_3b_3_3_reduce = K.Conv2D(128,
                                      1,
                                      activation = 'relu',
                                      name='inception_3b_3_3_reduce')(inception_3a_output)
    inception_3b_3_3 = K.Conv2D(192,
                               3,
                               activation = 'relu',
                               name='inception_3b_3_3')(inception_3b_3_3_reduce)
    inception_3b_5_5_reduce = K.Conv2D(32,
                                      1,
                                      activation='relu',
                                      name = 'inception_3b_5_5_reduce')(inception_3a_output)
    inception_3b_5_5 = K.Conv2D(96,
                               5,
                               name = 'inception_3b_5_5')(inception_3b_5_5_reduce)
    inception_3b_pool = K.MaxPooling2D(3,
                                     strides = 1,
                                     padding = 'same',
                                     name='inception_3b_pool')(inception_3a_output)
    inception_3b_pool_1_1 = K.Conv2D(64,
                                    kernel_size=1,
                                    activation='relu',
                                    name='inception_3b_pool_1_1')(inception_3b_pool)

    #merge the inception_3b_*
    inception_3b_output = K.Concatenate(axis=3,
                                      name='inception_3b_output')([inception_3b_1_1,
                                       inception_3b_3_3,
                                       inception_3b_5_5,
                                       inception_3b_pool_1_1])

    pool3_3_3 = K.MaxPooling2D(pool_size=3,
                             strides=2,
                             padding = 'same',
                             name='pool3_3_3')(inception_3b_output)
    inception_4a_1_1 = K.Conv2D(192,
                              kernel_size=1,
                              activation='relu',
                              name = 'inception_4a_1_1')(pool3_3_3)
    inception_4a_3_3_reduce = K.Conv2D(96,
                                     1,
                                     activation = 'relu',
                                     name = 'inception_4a_3_3_reduce')(pool3_3_3)
    inception_4a_3_3 = K.Conv2D(208,
                              3,
                              activation = 'relu',
                              name = 'inception_4a_3_3')(inception_4a_3_3_reduce)
    inception_4a_5_5_reduce = K.Conv2D(16,
                                     kernel_size=1,
                                     activation='relu',
                                     name='inception_4a_5_5_reduce')(pool3_3_3)
    inception_4a_5_5 = K.Conv2D(48,
                              kernel_size=5,
                              activation='relu',
                              name='inception_4a_5_5')(inception_4a_5_5_reduce)
    inception_4a_pool = K.MaxPooling2D(pool_size=3,
                                     strides=1,
                                     padding='same',
                                     name='inception_4a_pool')(pool3_3_3)
    inception_4a_pool_1_1 = K.Conv2D(64,
                                   kernel_size=1,
                                   activation='relu',
                                   name='inception_4a_pool_1_1')(inception_4a_pool)

    inception_4a_output = K.Concatenate(axis = 3,
                                      name = 'inception_4a_output')([inception_4a_1_1,
                                       inception_4a_3_3,
                                       inception_4a_5_5,
                                       inception_4a_pool_1_1])

    pool5_7_7 = K.AveragePooling2D(5,
                                   padding = 'same',
                                   strides = 1)(inception_4a_output)
    pool5_7_7 = K.Dropout(0.4)(pool5_7_7)
    output_layer = K.Dense(2,
                   activation='softmax')(pool5_7_7)
    model = Model(input_layer,output_layer)
    model.compile(optimizer=opt,
                  loss = loss_f)
    return model

I am not very familiar with Keras directly.
Our example is heavily based on the standard inceptionV1 (googlenet) example, it is a cut down version of it as explained in the paper:
https://github.com/tflearn/tflearn/blob/master/examples/images/googlenet.py
in tflearn, which uses the same ops for concat.
Here is a Keras example of the same base inceptionV1 architecture:
https://gist.github.com/joelouismarino/a2ede9ab3928f999575423b9887abd14
I would suggest using this as a base. For example, in the Keras example for inceptionV1 they have axis=1, whilst in tflearn axis=3 used for concatenation to achieve the same effect it appears.
You have 3 in your code which is consistent with our tflearn code, but not the definition of inceptionV1 in Keras which uses axis=1, try this perhaps.


Suggestions highlights does not follow colorscheme

Hi ! I'm facing an issue pretty similar of https://github.com/yetone/avante.nvim/issues/654
i'm using catppuccin/nvim as colorscheme
When i apply the suggestion from avante, the results is pretty illisible and does not follow the colorscheme

i have to reapply the colorscheme using colorscheme catppuccin-mocha
Then i end up using the proper colors

I tried to apply the workaround from https://github.com/yetone/avante.nvim/issues/654 in my config but does not fix it
Do you have any clue about this?
I don't even know if this is an issue of the colorscheme or avante? or even just a config issue?
Catpuccin seems to define the TextAdd and TextDiff values
here are the dotfiles :
https://github.com/benjah13/dotfiles/blob/master/nvim
where i applied the workaround https://github.com/benjah13/dotfiles/blob/master/nvim/init.lua
avante config https://github.com/benjah13/dotfiles/blob/master/nvim/lua/plugins/avante.lua
Thanks in advance 💪

I close the issue
i temporarily avante and i have the exact same issue with git-conflict.nvim.
So not related to avante !


Return HTTP 301 to client when redirect occurs for old DSpace 6.x URLs

Describe the bug
Follow-up to #1147
The Google Scholar team noted that when older-style /handle URLs (e.g. /handle/[prefix]/[suffix]) are redirected to new URLs (e.g. /items/[uuid]), the redirect does not return an HTTP 301 Moved Permanently to the client.  Instead, a 200 OK is returned.
To Reproduce
Steps to reproduce the behavior:

Find the /handle/[prefix]/[suffix] for a Community, Collection or Item.
Open up your browser's DevTools, "network" tab for the current page.
Paste the /handle/[prefix]/[suffix] URL in your browser's address bar.  Notice in DevTools that a 200 OK is returned even though the redirect occurs (internally)

Expected behavior
Ideally the redirect should occur via 301 (or 302) response code.  This allows crawlers to be notified properly of the redirect and avoids the page being indexed twice under two different URLs.
Related work
Related to initial redirect work in #1147

Talked again with the Google Scholar team today.  Verified this feature is only needed on the server side.  They are using SSR content when indexing DSpace 7 sites.  In order for these older DSpace 6 URLs to be replaced in the Google Scholar index, a 301 Moved Permanently Redirect should be returned when a DSpace 6 URL is redirected to a DSpace 7 URL.


Enable opening variant details in separate browser tab

Currently, the link to the variant details from the filter results can't be opened via middle mouse click or "open in other tab". A user wished for that, investigate whether this is possible and if so what the effort would be.

After talking to @holtgrewe we port the feature of the "info-overlay-component-that-slides-in-from-the-right-side" from the v2 interface to the current interface.


Fix MASTER_DELETE_CODE to work with deletion codes with uppercase letters

Hello,
After about an hour of trying to figure out why my master delete code wasn't working, I discovered that the problem was that my master deletion code had uppercase characters. Deletion codes with uppercase characters are always rejected because each URL segment is converted to lowercase before being compared. My temporary solution was to just convert my code to lowercase.
The changes made in this PR will ensure that the MASTER_DELETE_CODE is converted to lowercase in the comparison, which will allow codes with uppercase letters to work.

thanks!


docker-compose up failed

How to reproduce the bug
git clone https://github.com/apache/superset.git
cd superset
docker-compose -f docker-compose-non-dev.yml pull
docker-compose -f docker-compose-non-dev.yml up

Expected results
visit: http://localhost:8088/ and http://localhost:8080/

Environment

browser type and version: Chrome 103.0.5060.114
superset version: 2.0 (Tue Jun 28 08:53:02 2022 -0400)

Additional context
$ docker-compose -f docker-compose-non-dev.yml up

Starting superset_cache ... done
Starting superset_db    ... done
Starting superset_init        ... done
Starting superset_app         ... done
Starting superset_worker      ... done
Starting superset_worker_beat ... done
Attaching to superset_db, superset_cache, superset_worker_beat, superset_worker, superset_app, superset_init
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_cache          | 1:C 18 Jul 2022 14:33:50.007 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
superset_cache          | 1:C 18 Jul 2022 14:33:50.008 # Redis version=7.0.3, bits=64, commit=00000000, modified=0, pid=1, just started
superset_cache          | 1:C 18 Jul 2022 14:33:50.008 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
superset_cache          | 1:M 18 Jul 2022 14:33:50.008 * monotonic clock: POSIX clock_gettime
superset_cache          | 1:M 18 Jul 2022 14:33:50.009 * Running mode=standalone, port=6379.
superset_cache          | 1:M 18 Jul 2022 14:33:50.009 # Server initialized
superset_cache          | 1:M 18 Jul 2022 14:33:50.010 * Loading RDB produced by version 7.0.3
superset_cache          | 1:M 18 Jul 2022 14:33:50.011 * RDB age 10 seconds
superset_cache          | 1:M 18 Jul 2022 14:33:50.011 * RDB memory usage when created 1.19 Mb
superset_cache          | 1:M 18 Jul 2022 14:33:50.011 * Done loading RDB, keys loaded: 11, keys expired: 0.
superset_cache          | 1:M 18 Jul 2022 14:33:50.011 * DB loaded from disk: 0.000 seconds
db_1                    |
db_1                    | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1                    |
superset_cache          | 1:M 18 Jul 2022 14:33:50.011 * Ready to accept connections
db_1                    | 2022-07-18 14:33:50.078 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1                    | 2022-07-18 14:33:50.078 UTC [1] LOG:  listening on IPv6 address "::", port 5432
superset_worker         | Skipping local overrides
superset_worker         | Starting Celery worker...
db_1                    | 2022-07-18 14:33:50.086 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1                    | 2022-07-18 14:33:50.101 UTC [25] LOG:  database system was shut down at 2022-07-18 14:33:40 UTC
superset_worker_beat    | Skipping local overrides
superset_worker_beat    | Starting Celery beat...
db_1                    | 2022-07-18 14:33:50.189 UTC [1] LOG:  database system is ready to accept connections
superset_init           | Skipping local overrides
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 1/4 [Starting] -- Applying DB migrations
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    |                                     WARNING
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat    | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat    | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | logging was configured successfully
superset_worker_beat    | 2022-07-18 14:34:05,223:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat    | 2022-07-18 14:34:05,238:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker         | --------------------------------------------------------------------------------
superset_worker         |                                     WARNING
superset_worker         | --------------------------------------------------------------------------------
superset_worker         | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker         | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker         | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker         | --------------------------------------------------------------------------------
superset_worker         | --------------------------------------------------------------------------------
superset_worker         | logging was configured successfully
superset_worker         | 2022-07-18 14:34:05,261:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:34:05,264:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker         | 2022-07-18 14:34:05,274:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:34:05,282:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker         | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker         | 2022-07-18 14:34:05,289:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker         | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker         | 2022-07-18 14:34:05,306:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_init           | --------------------------------------------------------------------------------
superset_init           |                                     WARNING
superset_init           | --------------------------------------------------------------------------------
superset_init           | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init           | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init           | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init           | --------------------------------------------------------------------------------
superset_init           | --------------------------------------------------------------------------------
superset_init           | logging was configured successfully
superset_init           | 2022-07-18 14:34:09,697:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init           | 2022-07-18 14:34:09,730:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:34:09,746:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:34:09,764:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat    | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat    | Seems we're already running? (pid: 8)
superset_worker_beat    | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat    | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker         | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker         |
superset_worker         |  -------------- celery@c4a746c651f6 v5.2.2 (dawn-chorus)
superset_worker         | --- ***** -----
superset_worker         | -- ******* ---- Linux-5.10.104-linuxkit-x86_64-with-glibc2.2.5 2022-07-18 14:34:16
superset_worker         | - *** --- * ---
superset_worker         | - ** ---------- [config]
superset_worker         | - ** ---------- .> app:         __main__:0x4025c7e430
superset_worker         | - ** ---------- .> transport:   redis://redis:6379/0
superset_worker         | - ** ---------- .> results:     redis://redis:6379/1
superset_worker         | - *** --- * --- .> concurrency: 4 (prefork)
superset_worker         | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
superset_worker         | --- ***** -----
superset_worker         |  -------------- [queues]
superset_worker         |                 .> celery           exchange=celery(direct) key=celery
superset_worker         |
superset_worker         |
superset_worker         | [tasks]
superset_worker         |   . cache-warmup
superset_worker         |   . cache_chart_thumbnail
superset_worker         |   . cache_dashboard_thumbnail
superset_worker         |   . load_chart_data_into_cache
superset_worker         |   . load_explore_json_into_cache
superset_worker         |   . reports.execute
superset_worker         |   . reports.prune_log
superset_worker         |   . reports.scheduler
superset_worker         |   . sql_lab.get_sql_results
superset_worker         |
superset_worker         | /usr/local/lib/python3.8/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is
superset_worker         | absolutely not recommended!
superset_worker         |
superset_worker         | Please specify a different user using the --uid option.
superset_worker         |
superset_worker         | User information: uid=0 euid=0 gid=0 egid=0
superset_worker         |
superset_worker         |   warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format(
superset_worker         | [2022-07-18 14:34:16,396: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker         |     The 'CELERY_IMPORTS' setting is deprecated and scheduled for removal in
superset_worker         |     version 6.0.0. Use the imports instead
superset_worker         |
superset_worker         |   deprecated.warn(description=f'The {setting!r} setting',
superset_worker         |
superset_worker         | [2022-07-18 14:34:16,398: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker         |     The 'BROKER_URL' setting is deprecated and scheduled for removal in
superset_worker         |     version 6.0.0. Use the broker_url instead
superset_worker         |
superset_worker         |   deprecated.warn(description=f'The {setting!r} setting',
superset_worker         |
superset_worker         | [2022-07-18 14:34:16,398: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker         |     The 'CELERYBEAT_SCHEDULE' setting is deprecated and scheduled for removal in
superset_worker         |     version 6.0.0. Use the beat_schedule instead
superset_worker         |
superset_worker         |   deprecated.warn(description=f'The {setting!r} setting',
superset_worker         |
superset_worker         | [2022-07-18 14:34:16,399: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker         |     The 'CELERY_RESULT_BACKEND' setting is deprecated and scheduled for removal in
superset_worker         |     version 6.0.0. Use the result_backend instead
superset_worker         |
superset_worker         |   deprecated.warn(description=f'The {setting!r} setting',
superset_worker         |
superset_worker         | [2022-07-18 14:34:16,399: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker         |     The 'CELERY_ACKS_LATE' setting is deprecated and scheduled for removal in
superset_worker         |     version 6.0.0. Use the task_acks_late instead
superset_worker         |
superset_worker         |   deprecated.warn(description=f'The {setting!r} setting',
superset_worker         |
superset_worker         | [2022-07-18 14:34:16,400: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery/app/utils.py:204: CDeprecationWarning:
superset_worker         |     The 'CELERYD_PREFETCH_MULTIPLIER' setting is deprecated and scheduled for removal in
superset_worker         |     version 6.0.0. Use the worker_prefetch_multiplier instead
superset_worker         |
superset_worker         |   deprecated.warn(description=f'The {setting!r} setting',
superset_worker         |
superset_worker         | [2022-07-18 14:34:16,400: WARNING/MainProcess] Please run `celery upgrade settings path/to/settings.py` to avoid these warnings and to allow a smoother upgrade to Celery 6.0.
superset_worker_beat    | Skipping local overrides
superset_worker_beat    | Starting Celery beat...
superset_worker         | [2022-07-18 14:34:17,489: INFO/MainProcess] Connected to redis://redis:6379/0
superset_worker         | [2022-07-18 14:34:17,499: INFO/MainProcess] mingle: searching for neighbors
superset_worker         | [2022-07-18 14:34:18,545: INFO/MainProcess] mingle: all alone
superset_worker         | [2022-07-18 14:34:18,624: INFO/MainProcess] celery@c4a746c651f6 ready.
superset_init           | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
superset_init           | INFO  [alembic.runtime.migration] Will assume transactional DDL.
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_init           | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 1/4 [Complete] -- Applying DB migrations
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 2/4 [Starting] -- Setting up admin user ( admin / admin )
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    |                                     WARNING
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat    | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat    | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | logging was configured successfully
superset_worker_beat    | 2022-07-18 14:34:26,721:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat    | 2022-07-18 14:34:26,732:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:34:26,747:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:34:26,764:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat    | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker_beat    | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat    | Seems we're already running? (pid: 8)
superset_init           | --------------------------------------------------------------------------------
superset_init           |                                     WARNING
superset_init           | --------------------------------------------------------------------------------
superset_init           | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init           | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init           | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init           | --------------------------------------------------------------------------------
superset_init           | --------------------------------------------------------------------------------
superset_init           | logging was configured successfully
superset_init           | 2022-07-18 14:34:35,164:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init           | 2022-07-18 14:34:35,194:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:34:35,208:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:34:35,223:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat exited with code 73
superset_worker_beat    | Skipping local overrides
superset_worker_beat    | Starting Celery beat...
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_init           | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_init           | Recognized Database Authentications.
superset_init           | Error! User already exists admin
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 2/4 [Complete] -- Setting up admin user
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 3/4 [Starting] -- Setting up roles and perms
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    |                                     WARNING
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat    | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat    | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | logging was configured successfully
superset_worker_beat    | 2022-07-18 14:34:45,750:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat    | 2022-07-18 14:34:45,761:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:34:45,773:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:34:45,796:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat    | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker_beat    | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat    | Seems we're already running? (pid: 8)
superset_worker_beat exited with code 73
superset_worker_beat    | Skipping local overrides
superset_worker_beat    | Starting Celery beat...
superset_init           | --------------------------------------------------------------------------------
superset_init           |                                     WARNING
superset_init           | --------------------------------------------------------------------------------
superset_init           | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init           | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init           | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init           | --------------------------------------------------------------------------------
superset_init           | --------------------------------------------------------------------------------
superset_init           | logging was configured successfully
superset_init           | 2022-07-18 14:34:56,616:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init           | 2022-07-18 14:34:56,639:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:34:56,652:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:34:56,666:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    |                                     WARNING
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat    | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat    | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | logging was configured successfully
superset_worker_beat    | 2022-07-18 14:35:03,295:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat    | 2022-07-18 14:35:03,305:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:35:03,319:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:35:03,336:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_init           | Syncing role definition
superset_init           | 2022-07-18 14:35:08,982:INFO:superset.security.manager:Syncing role definition
superset_init           | Syncing Admin perms
superset_init           | 2022-07-18 14:35:09,030:INFO:superset.security.manager:Syncing Admin perms
superset_init           | Syncing Alpha perms
superset_init           | 2022-07-18 14:35:09,354:INFO:superset.security.manager:Syncing Alpha perms
superset_init           | Syncing Gamma perms
superset_init           | 2022-07-18 14:35:09,694:INFO:superset.security.manager:Syncing Gamma perms
superset_init           | Syncing granter perms
superset_init           | 2022-07-18 14:35:10,023:INFO:superset.security.manager:Syncing granter perms
superset_init           | Syncing sql_lab perms
superset_init           | 2022-07-18 14:35:10,336:INFO:superset.security.manager:Syncing sql_lab perms
superset_init           | Fetching a set of all perms to lookup which ones are missing
superset_init           | 2022-07-18 14:35:10,647:INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing
superset_init           | Creating missing datasource permissions.
superset_init           | 2022-07-18 14:35:10,939:INFO:superset.security.manager:Creating missing datasource permissions.
superset_init           | Creating missing database permissions.
superset_init           | 2022-07-18 14:35:10,958:INFO:superset.security.manager:Creating missing database permissions.
superset_init           | Cleaning faulty perms
superset_init           | 2022-07-18 14:35:10,984:INFO:superset.security.manager:Cleaning faulty perms
superset_init           | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat    | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker_beat    | celery beat v5.2.2 (dawn-chorus) is starting.
superset_worker_beat    | ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
superset_worker_beat    | Seems we're already running? (pid: 8)
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 3/4 [Complete] -- Setting up roles and perms
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_init           |
superset_init           | Init Step 4/4 [Starting] -- Loading examples
superset_init           |
superset_init           |
superset_init           | ######################################################################
superset_init           |
superset_worker_beat exited with code 73
superset_worker_beat    | Skipping local overrides
superset_worker_beat    | Starting Celery beat...
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    |                                     WARNING
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_worker_beat    | Use a strong complex alphanumeric string and use a tool to help you generate
superset_worker_beat    | a sufficiently random sequence, ex: openssl rand -base64 42
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | --------------------------------------------------------------------------------
superset_worker_beat    | logging was configured successfully
superset_worker_beat    | 2022-07-18 14:35:21,535:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker_beat    | 2022-07-18 14:35:21,548:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:35:21,562:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | 2022-07-18 14:35:21,590:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | --------------------------------------------------------------------------------
superset_init           |                                     WARNING
superset_init           | --------------------------------------------------------------------------------
superset_init           | A Default SECRET_KEY was detected, please use superset_config.py to override it.
superset_init           | Use a strong complex alphanumeric string and use a tool to help you generate
superset_init           | a sufficiently random sequence, ex: openssl rand -base64 42
superset_init           | --------------------------------------------------------------------------------
superset_init           | --------------------------------------------------------------------------------
superset_init           | logging was configured successfully
superset_init           | 2022-07-18 14:35:24,127:INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init           | 2022-07-18 14:35:24,153:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:35:24,170:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_init           | 2022-07-18 14:35:24,186:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
superset_worker_beat    | Stale pidfile exists - Removing it.
superset_worker_beat    | [2022-07-18 14:35:29,976: INFO/MainProcess] beat: Starting...
superset_worker_beat    | [2022-07-18 14:35:30,040: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker         | [2022-07-18 14:35:30,089: INFO/MainProcess] Task reports.scheduler[b9ac068c-a9b5-4b32-a9ba-24ac0f3fb7f2] received
superset_worker         | [2022-07-18 14:35:30,227: INFO/ForkPoolWorker-1] Task reports.scheduler[b9ac068c-a9b5-4b32-a9ba-24ac0f3fb7f2] succeeded in 0.11053812500904314s: None
superset_init           | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_init           | Loading examples metadata and related data into examples
superset_init           | Creating default CSS templates
superset_init           | Loading [World Bank's Health Nutrition and Population Stats]
superset_init           | Traceback (most recent call last):
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 1354, in do_open
superset_init           |     h.request(req.get_method(), req.selector, req.data, headers,
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 1256, in request
superset_init           |     self._send_request(method, url, body, headers, encode_chunked)
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 1302, in _send_request
superset_init           |     self.endheaders(body, encode_chunked=encode_chunked)
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 1251, in endheaders
superset_init           |     self._send_output(message_body, encode_chunked=encode_chunked)
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 1011, in _send_output
superset_init           |     self.send(msg)
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 951, in send
superset_init           |     self.connect()
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 1418, in connect
superset_init           |     super().connect()
superset_init           |   File "/usr/local/lib/python3.8/http/client.py", line 922, in connect
superset_init           |     self.sock = self._create_connection(
superset_init           |   File "/usr/local/lib/python3.8/socket.py", line 808, in create_connection
superset_init           |     raise err
superset_init           |   File "/usr/local/lib/python3.8/socket.py", line 796, in create_connection
superset_init           |     sock.connect(sa)
superset_init           | OSError: [Errno 99] Cannot assign requested address
superset_init           |
superset_init           | During handling of the above exception, another exception occurred:
superset_init           |
superset_init           | Traceback (most recent call last):
superset_init           |   File "/usr/local/bin/superset", line 33, in <module>
superset_init           |     sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
superset_init           |     return self.main(*args, **kwargs)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 601, in main
superset_init           |     return super().main(*args, **kwargs)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1053, in main
superset_init           |     rv = self.invoke(ctx)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
superset_init           |     return _process_result(sub_ctx.command.invoke(sub_ctx))
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
superset_init           |     return ctx.invoke(self.callback, **ctx.params)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
superset_init           |     return __callback(*args, **kwargs)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
superset_init           |     return f(get_current_context(), *args, **kwargs)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 445, in decorator
superset_init           |     return __ctx.invoke(f, *args, **kwargs)
superset_init           |   File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
superset_init           |     return __callback(*args, **kwargs)
superset_init           |   File "/app/superset/cli/examples.py", line 113, in load_examples
superset_init           |     load_examples_run(load_test_data, load_big_data, only_metadata, force)
superset_init           |   File "/app/superset/cli/examples.py", line 49, in load_examples_run
superset_init           |     examples.load_world_bank_health_n_pop(only_metadata, force)
superset_init           |   File "/app/superset/examples/world_bank.py", line 59, in load_world_bank_health_n_pop
superset_init           |     data = get_example_data("countries.json.gz")
superset_init           |   File "/app/superset/examples/helpers.py", line 79, in get_example_data
superset_init           |     content = request.urlopen(  # pylint: disable=consider-using-with
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 222, in urlopen
superset_init           |     return opener.open(url, data, timeout)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 531, in open
superset_init           |     response = meth(req, response)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 640, in http_response
superset_init           |     response = self.parent.error(
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 563, in error
superset_init           |     result = self._call_chain(*args)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 502, in _call_chain
superset_init           |     result = func(*args)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 755, in http_error_302
superset_init           |     return self.parent.open(new, timeout=req.timeout)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 531, in open
superset_init           |     response = meth(req, response)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 640, in http_response
superset_init           |     response = self.parent.error(
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 563, in error
superset_init           |     result = self._call_chain(*args)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 502, in _call_chain
superset_init           |     result = func(*args)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 755, in http_error_302
superset_init           |     return self.parent.open(new, timeout=req.timeout)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 525, in open
superset_init           |     response = self._open(req, data)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 542, in _open
superset_init           |     result = self._call_chain(self.handle_open, protocol, protocol +
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 502, in _call_chain
superset_init           |     result = func(*args)
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 1397, in https_open
superset_init           |     return self.do_open(http.client.HTTPSConnection, req,
superset_init           |   File "/usr/local/lib/python3.8/urllib/request.py", line 1357, in do_open
superset_init           |     raise URLError(err)
superset_init           | urllib.error.URLError: <urlopen error [Errno 99] Cannot assign requested address>
superset_init exited with code 1
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat    | [2022-07-18 14:36:00,030: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker         | [2022-07-18 14:36:00,064: INFO/MainProcess] Task reports.scheduler[c89c6a44-c584-4e0b-9a79-e0a719149022] received
superset_worker         | [2022-07-18 14:36:00,115: INFO/ForkPoolWorker-1] Task reports.scheduler[c89c6a44-c584-4e0b-9a79-e0a719149022] succeeded in 0.04363124999508727s: None
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_worker_beat    | [2022-07-18 14:37:00,036: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker         | [2022-07-18 14:37:00,063: INFO/MainProcess] Task reports.scheduler[f2044f9e-a42c-4d65-8648-7a7bad478008] received
superset_worker         | [2022-07-18 14:37:00,152: INFO/ForkPoolWorker-1] Task reports.scheduler[f2044f9e-a42c-4d65-8648-7a7bad478008] succeeded in 0.0697625830071047s: None
superset_app exited with code 2
superset_worker_beat    | [2022-07-18 14:38:00,047: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker         | [2022-07-18 14:38:00,082: INFO/MainProcess] Task reports.scheduler[29b8df55-2994-456a-b433-5b02f6f8fd6c] received
superset_worker         | [2022-07-18 14:38:00,218: INFO/ForkPoolWorker-1] Task reports.scheduler[29b8df55-2994-456a-b433-5b02f6f8fd6c] succeeded in 0.11490391600818839s: None
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2
superset_worker_beat    | [2022-07-18 14:39:00,030: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker         | [2022-07-18 14:39:00,067: INFO/MainProcess] Task reports.scheduler[91911a3a-54b9-4bb3-b886-02b6a5f18f4c] received
superset_worker         | [2022-07-18 14:39:00,151: INFO/ForkPoolWorker-1] Task reports.scheduler[91911a3a-54b9-4bb3-b886-02b6a5f18f4c] succeeded in 0.06387108299531974s: None
superset_app            | Skipping local overrides
superset_app            | Starting web app...
superset_app            | usage: gunicorn [OPTIONS] [APP_MODULE]
superset_app            | gunicorn: error: argument --max-requests: expected one argument
superset_app exited with code 2

solved by pulling latest updates from master branch

Closing for now!


Fix broken link to abi module documentation in README.md

That link gives a 404 error, at least when viewed on github. I suppose this is the intended target.

Thanks however all links in the crates' README are catered towards docs.rs, we unfortunately most of the time can't have both


Don't delete the underlying asset when removing asset from project

Closing this in favour of copying assets instead


add jetson

add jetson boot instructions
add nvidia logo for homepage
remove deprecated device logos

Hey Zach mind checking the instructions? I just copied them from you're docs PR and removed the mention of the dashboard.

@zwalchuk @craig-mulligan looks like it still refers to "provisioning", and shouldn't. I haven't had a chance to try an unmanaged version but given my guess:
a) Remove:

At this point your device will attempt to connect to the internet. If you selected wifi as your connectivity type, remember to attach the wifi antennas before booting the board. If you selected ethernet, make sure your ethernet cable is plugged in.

b) Replace:

After the device has been provisioned, it will shut itself off automatically. You can safely remove the SD card.

with something like:

After resinOS has been flashed onto the internal storage, the board it will shut itself off automatically and the power LED will turn off. You can safely remove the SD card.

Do these make sense in the context of the whole page? (can't build the site because of libsass at the moment, so can't check out this whole PR in its entirety quickly)
Also, the image of the module is okay, but do we want to put there the dev board's image too? (since that one has the power button and power plug) Just wondering.

No worries, yea that makes sense. I'll replace the image with the dev board too.


scan_stocks() not working pls help?

----- Scanning portfolio for stocks to sell -----
----- Scanning watchlist for stocks to buy -----
Traceback (most recent call last):
File "main.py", line 259, in
scan_stocks()
File "main.py", line 248, in scan_stocks
cross = golden_cross(symbol, n1=50, n2=200, days=10, direction="above")
File "main.py", line 159, in golden_cross
if(direction == "above" and not five_year_check(stockTicker)):
File "main.py", line 131, in five_year_check
if ((pd.Timestamp("now") - pd.to_datetime(list_date)) < pd.Timedelta("5 Y")):
TypeError: unsupported operand type(s) for -: 'Timestamp' and 'NoneType'

I believe this issue is due to a new version of robin_stocks.  I have corrected this in my fork.


nothing display except the button

I followed you example and only the "submit" button displays :
This is the generated html

<!DOCTYPE html>
<html lang="en">

<head>
    <meta name='viewport' content='initial-scale=1,maximum-scale=1,user-scalable=no' />
    <script src='https://api.tiles.mapbox.com/mapbox-gl-js/v1.0.0/mapbox-gl.js'></script>
    <link href='https://api.tiles.mapbox.com/mapbox-gl-js/v1.0.0/mapbox-gl.css' rel='stylesheet' />
    <script src='https://api.mapbox.com/mapbox-gl-js/plugins/mapbox-gl-geocoder/v4.4.0/mapbox-gl-geocoder.min.js'></script>
    <link rel='stylesheet' href='https://api.mapbox.com/mapbox-gl-js/plugins/mapbox-gl-geocoder/v4.4.0/mapbox-gl-geocoder.css' type='text/css' />
    <script src='https://code.jquery.com/jquery-3.3.1.min.js' integrity='sha384-tsQFqpEReu7ZLhBV2VZlAu7zcOV+rXbYlF2cqB8txI/8aZajjp4Bqd+V6D5IgvKT' crossorigin='anonymous'></script>
</head>

<body>
    <form method="post">
        <input type="hidden" name="csrfmiddlewaretoken" value="mwmHg2DYxvmcKlHq9PnLmqnOTHWRytqIsM83YbyQ0bCYsmN833pXT8T2VpbNu7ZT">

        <input type="submit" value="submit">
    </form>
</body>

why did the map don't display ?
what I have done wrong ??
Thanks

Did you pasted
<form method="post">
        {% csrf_token %}
        {{form}}
        <input type="submit" value="submit">
    </form>
{{ form.media }}

in your html template?

i found the same issue. please solve it.

I haven't encountered anything similar, so I'm gonna need some examples of your code to locate the source of your issue. On the beginning, please show me your html template and Django view

Also, please check the console in your browser's analytics tools and check some potential javascript errors.

Thanks for your feedback. I will provide you more detailed info this evening.

my template :
{% extends 'spots/base.html' %}

{% load mapbox_location_field_tags %}
{% location_field_includes %}
{% include_jquery %}

{% block content %}

<form method="post">
     {% csrf_token %}
     {{form}}
     <input type="submit" value="submit">
 </form>
{{ form.media }}

{% endblock %}

here is what I obtain (whit no specific javascript errors)

Maybe if you could provide a full exampl it will help to fugure out what is wrong for us...
Thanks

Your html template seems correct

The source of your problem may be the model or view

At your special request, I will upload the code of my live demo on Github soon

The code of the live demo is now at github here: https://github.com/Simon-the-Shark/live_demo_django_mapbox_location_field
It's very simple, but I hope you will find it usefull. Let me know about your progress. If that doesn't work, you can share me the code of your django view, I will try to help.

Thank you very much. It works!

I'm glad it worked


Balance form on swaponline.github.io: balance loading is too slow

Slow balance loading (takes around 1 minute). In the end we see a error from the next server with a status 504 (timeout status). Maybe it's related.
What's happen if we disable some assets? Maybe the problem is in one of them on balance requests
Screenshot or description

Environment

Domain: swaponline.github.io

This is because of NEXT currency is enabled, we need to disable it by default


GKE not starting sidecars

Hello,
I'm sorry but I'm pretty new to GKE and Dapr but I'm really excited about it.
I'm trying to run first service with Dapr sidecar on Google K8s engine. But my pods have never assigned a Dapr sidecar.
I have installed Dapr using Helm into K8s:
helm upgrade --install dapr dapr/dapr \
--version=1.2 \
--namespace dapr-system \
--create-namespace \
--wait

And I have running all pods runing:
NAME                                     READY   STATUS    RESTARTS   AGE
dapr-dashboard-658f76b85f-jsvtn          1/1     Running   0          2d2h
dapr-operator-6b9f657879-2wtr6           1/1     Running   0          2d2h
dapr-placement-server-0                  1/1     Running   0          2d2h
dapr-sentry-77749b6c66-5d8nv             1/1     Running   0          2d2h
dapr-sidecar-injector-59459899d6-blj7w   1/1     Running   0          2d2h

I have first microservice (ASP.NET 5.0) with deployment:
apiVersion: apps/v1
kind: Deployment
...
spec:
  ...
  template:
    metadata:
      annotations:
        dapr.io/app-id: asp-service
        dapr.io/app-port: "5000"
        dapr.io/config: tracing
        dapr.io/enabled: "true"
        dapr.io/log-level: debug

But when I run deployment using GitLab CICD using:
deploy to staging:
  - ...
  - kubectl patch deployment asp-service --patch "$(cat deploy-patch.yaml)"

There is no sidecar started for my service:
>kubectl get pods
NAME                                  READY   STATUS    RESTARTS   AGE
asp-service-b5f44cd67-qdcfn   1/1     Running   0          4m9s
...

>kubectl get services
NAME                                        TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)                                  AGE
asp-service-dapr                    ClusterIP   None          <none>        80/TCP,50001/TCP,50002/TCP,9090/TCP      2d2h
...

When I look for logs for sidecar-injector there is no error or something. It looks started but nothing more:
>kubectl logs -l app=dapr-sidecar-injector -n dapr-system
time="2021-06-29T10:14:42.104435436Z" level=info msg="log level set to: DEBUG" instance=dapr-sidecar-injector-59459899d6-blj7w scope=dapr.injector type=log ver=unknown
time="2021-06-29T10:14:42.105076056Z" level=info msg="metrics server started on :9090/" instance=dapr-sidecar-injector-59459899d6-blj7w scope=dapr.metrics type=log ver=unknown
time="2021-06-29T10:14:42.105456516Z" level=info msg="starting Dapr Sidecar Injector -- version 1.2.2 -- commit 8aabc2c" instance=dapr-sidecar-injector-59459899d6-blj7w scope=dapr.injector type=log ver=unknown
time="2021-06-29T10:14:42.107693316Z" level=info msg="Healthz server is listening on :8080" instance=dapr-sidecar-injector-59459899d6-blj7w scope=dapr.injector type=log ver=unknown
time="2021-06-29T10:14:42.130301045Z" level=info msg="Sidecar injector is listening on :4000, patching Dapr-enabled pods" instance=dapr-sidecar-injector-59459899d6-blj7w scope=dapr.injector type=log ver=unknown

When I try to pubsub in my service I get:
2021-07-01T12:59:02.977810296Z Connection id "0HM9SHVUEKQVK", Request id "0HM9SHVUEKQVK:00000002": An unhandled exception was thrown by the application.
Info
2021-07-01T12:59:02.977822806Z Dapr.DaprException: Publish operation failed: the Dapr endpoint indicated a failure. See InnerException for details.
Info
2021-07-01T12:59:02.977827966Z ---> Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: Connection refused (<IP_ADDRESS>:50001) SocketException: Connection refused", DebugException="System.Net.Http.HttpRequestException: Connection refused (<IP_ADDRESS>:50001)
Info
2021-07-01T12:59:02.977834176Z ---> System.Net.Sockets.SocketException (111): Connection refused
Info
2021-07-01T12:59:02.977839826Z at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)

Thank you very much for helping, understanding and patience

You're correct, in that it appears that the sidecar is not running in your cluster. Also, looking at your config, nothing stands out as obviously broken. In general, the sidecar logs should print success or failure anytime the k8s control plane sends it an event, so that suggests that no such event is being sent. Do you still have trouble when using kubectl apply instead of kubectl patch ? My wild guess is that maybe certain patch deployment strategies don't result in k8s control plane generating a request to the sidecar?

Also, just FYI: for more interactive debugging help, we have a community discord: https://aka.ms/dapr-discord . We have some GKE users in the community that might be able to speak to the nuances of running Dapr there.

It seems you have a solution directly in your documentation. Specifically here in the section for private GKE clusters:
https://docs.dapr.io/operations/hosting/kubernetes/cluster/setup-gke/
We added port 4000 permission to the firewall and Dapr booted properly.
I apologize for the useless question and next time I will use Discord.
Thanks for the great work!


Minor correction

In paragraph "Using nullable reference types is recommended since it flows the nullability expressed in C# code to EF Core's model and to the database, and obviates the use of the Fluent API or Data Annotations to express the same concept twice.", I think 'flows' should be 'follows'

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

ID: a4381838-81bb-52c6-d921-f8b9ae8163d2
Version Independent ID: 892a8dd8-7a63-ce0b-de20-27e92b88f971
Content: Entity Properties - EF Core
Content Source: entity-framework/core/modeling/entity-properties.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

"flows" is intentional: the C# code nullability is flowed to the EF Core model, and from there to the database, much like information can flow.


Load the hot-reloader when only needed.

This reduce the server boot-up time significantly.
With a 2015 MacBook Pro, it went down from 1000ms to 200ms

Wow 😲 Nice!


[v3.0.3-rc.7] iOS badge not updating

Since the upgrade to v3.0.3-rc.7 and migrating from Google GCM to Firebase FCM, iOS notification badge is stuck to one number. When clicking on app icon with a badge number of 3, it doesn't disappear afterwards. Sometimes it will change to a smaller or higher number, but never disappears completely.
PS: it was working fine in previous version v3.0.2.

@v3rron I have a same issue. :(

Yes, It's. v3.1.0-pre.1. when IOS client receive a notification(without open the app),the badge is always 1.But It will be changed if I Push.setBadge(count),It's a absolute value. May I listen the notification event ??? @raix


ListView miscalculates Pos when Toplevel is not Application.Top

This code:
		var keyLogLabel = new Label ("Key stroke log:") {
				X = Pos.Left (editLabel),
				Y = Pos.Top (editLabel) + 4,
			};
			Win.Add (keyLogLabel);

			var list = new List<string> ();
			var listView = new ListView (list) {
				X = 10,
				Y = Pos.Top (keyLogLabel) + 1,
				Width = Dim.Fill () - 30,
				Height = Dim.Fill (),
			};
			listView.ColorScheme = Colors.TopLevel;
			Win.Add (listView);

works correctly when Win has been added to Application.Top.

But when Win is added to another Toplevel the Y is mis-calculated, causing the ListView to be drawn too high:

This is likely related to #437

Wont fix.

I also verified that the percentage is not calculating well. I had to play with numbers to get more or less the desired size of each of the ListViews.


Todo: rewrite generation script

The original has written generation the script in fennel.
I want to improve it; mainly its error handling.
To improve it, either rewrite in a sane language, or learn fennel.

Are you considering any languages in particular? I'd be interested in helping out with this effort.

I'd be interested in helping out with this effort.

Nice, that would be great.

Are you considering any languages in particular?

Not really. I guess using a script language is not the worst idea, so maybe python?
But, I am open to any other suggestions

Hey,
I'm actually working on a similar project, which was mainly intended for my personal NixOS configuration.
Basically, I'm writing a small Rust CLI for generating buildVimPluginFrom2Nix expressions from a list of repsitories because I was annoyed that nixpkgs-unstable is missing so many plugins and I didn't want to update whole input just because a few Vim plugins need an update.
Then I discovered this project and noticed that my CLI may fit for this.
It's also much faster than the fennel script, and can generate the whole manifest.txt from this repository in about 20 seconds on my machine.
It's in a pretty early state because I began writing it only a few days ago, but maybe you're interested: https://github.com/Stupremee/vinix

This is implemented in #71
It should solve all duplicated plugins issues, plugins not updated, or other problems.
Let's hope


Relax cmake version requirement to 2.8

Ubuntu LTS and all derived distributions are shipping with cmake 2.8. With this simple change it is possible to compile on them without having the hassle to find a newer cmake. It is less elegant but it works on more systems.
ps. I couldn't help the whitespace commit ;)

Thank you, merged.
I have been planning to overhaul the buildsystem of string_id for months now, just didn't have the time. You can expect an improvement in the near future.

Thank you for merging.


Availability of CFU inbox driver (hidcfu.dll)

The sample INF configures the CFU inbox driver (hidcfu.dll) to enable the firmware update scenario for a virtual CFU Hid device.
Query: Is hidcfu.dll available in latest Windows 10?
Unable to find it on Windows 10 Version 1909 (OS Build 18363.1256)

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

ID: 3c8be335-f68e-4ace-6bd2-194e125927b6
Version Independent ID: 2c93d359-3d30-61b9-6184-963e314c6d77
Content: Component Firmware Update (CFU) INF configuration - Windows drivers
Content Source: windows-driver-docs-pr/cfu/cfu-inf-configuration.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @barrygolden
Microsoft Alias: bagold

Added a note that CFU is available in Windows 10, version 2004 (Windows 10 May 2020 Update) and later versions.


what metric name or collector should I use to get my instance data_source_name ?

I'm running sql_exporter with prometheus and I need to get the names of my data_source_name / target names (you can say as instance names as well)  as a metrics output. Because I need to use them as a drop-down for my grafana dashboard.
Below my sql_exporter.yml file
global:
  scrape_timeout_offset: 500ms
  min_interval: 0s
  max_connections: 3
  max_idle_connections: 3
target:
  data_source_name: 'sqlserver://prom_user:prom_password@dbserver1.example.com:1433/Hello'
  collectors: [mssql_standard]
collector_files:
  - "*myfile.collector.yml"

so  in above file sqlserver://prom_user:prom_password@dbserver1.example.com:1433/Hello  is the one I need to get from merics output.
So  Is there any metric name which I don't know to add into myfile.collector.yml ?  Or how can I get that name as a metric output ?

hi @free hope you understand my question, if not please leave a message, I will provide more information. Thanks

Hi @AmilaDevops, if this information can be inferred from the table, you can use key_labels and specify the column which contains a desired value. But if not, you can try to specify the names manually with static_labels parameter. Hope it helps. 😃

actually I decided to shift with windows_exporter to collect sql metrics with adding sql collector into it.  .  Thanks anyway,


How to update from 0.7.4 to 0.7.6

0.7.4 upgrade to 0.7.6 only change the bambooBSC application, the database no need re-import, because 0.7.4 version and 0.7.6 version database file are same.
download 0.7.6 version from:
https://github.com/billchen198318/bamboobsc/releases


Force update functionality

Task description
[placeholder]
Sub-tasks

[ ] subtask 1
[ ] subtask 2
[ ] subtask 3

Add label for component and priority.

Request:
GET /v0/appSettings?platform=android&appVersion=84
platform can be either android or ios.
appVersion is an integer.
Response json example:
{ "status":"ok", "url":"app-store-link" }
status can be:
"ok"
"warning"
"needsUpdate"
ok means that the app will not present anything to the user. The app can be used as normal.
warning means that the user will see a popup with a message like "There is a new version of the app. Do you want to update now?" Answer options are: "Update now", "Later".
needsUpdate means that the user will see a popup saying "There is a new version of the app. Please update now."
Answer option is only one "OK". The user cannot continue to use the app.
url is for example:
"https://play.google.com/store/apps/details?id=software.concordium.mobilewallet.mainnet"
"https://apps.apple.com/dk/app/concordium-mobile-wallet/id1566996491"
url can also point to a completely new app if that is required.

Not sure if it is a bug or merely a change request, but:
Steps:

Click "Make backup"
Then click "Export"
Go through export flow

Expected:
You are returned to the accounts page and the update popup is shown again
Actual:
You stay on the export page from which you can click "Export".
From there you have to click on the back arrow to get to the accounts page with the popup.

Can this issue be moved to "Verified" - or there something that needs to be fixed?

It was moved the verified. Then I closed the issue and automation moved it back to closed 😅

Moved back to Verified ;)


Update link to registrations page

Purpose
Update link to go to registrations page
Changes
Change wrong link to OSF registration help page.
Side effects

Ticket

https://openscience.atlassian.net/browse/OSF-6037

Looks good. 🎉 🐧 🎉


HIVE-25534: Error when executing DistCp on file system not supporting XAttrs

Committing the same as the tests are not related.


No cpu capping in cd

Do we need this? It causes us to not verify behavior with cpu capping, and don't we need the cpu because we run tests?
Use smaller flavors instead?

Starting services inside a Docker container takes a long time with small flavors today (.5 vcpu: ~6 mins, 1 vcpu: ~4 mins, 2 vcpus: ~2,5 mins). No capping of cpus could speed up testing a lot, so I would like to try this out to see what could be gained.
Doing it in all zones does not verify behavior with cpu capping, so maybe we should keep it as it is in prod zones?

Doing it in all zones does not verify behavior with cpu capping, so maybe we should keep it as it is in prod zones?

Sounds like a good compromise to me.


Add ORT worker proxy to prevent main thread locking, and service worker to cross-origin isolate which allows wasm threads

Please feel free to close this if you wanted to make the changes in a different way and just use this as a reference - figured it'd be easier to add a pull request than to explain in #8

Thanks so much! I'll try this out soon.

I tried to run it locally:
I got this warning 3 times:
c9b1644f-c3b0-49f6-b199-cec1b103569d:866

       Tried to spawn a new thread, but the thread pool is exhausted.
This might result in a deadlock unless some threads eventually exit or the code explicitly breaks out to the event loop.
If you want to increase the pool size, use setting `-s PTHREAD_POOL_SIZE=...`.
If you want to throw an explicit error instead of the risk of deadlocking in those cases, use setting `-s PTHREAD_POOL_SIZE_STRICT=2`.

and this error:
App.tsx:293

       DOMException: Failed to execute 'postMessage' on 'Worker': ArrayBuffer at index 2 is already detached.
    at http://localhost:3000/onnxruntime_web_build_inference_with_training_ops/ort.js:36387:25
    at new Promise (<anonymous>)
    at Object.run (http://localhost:3000/onnxruntime_web_build_inference_with_training_ops/ort.js:36384:16)
    at OnnxruntimeWebAssemblySessionHandler.run (http://localhost:3000/onnxruntime_web_build_inference_with_training_ops/ort.js:36547:47)
    at InferenceSession.run (http://localhost:3000/onnxruntime_web_build_inference_with_training_ops/ort.js:343:44)
    at runModel (http://localhost:3000/static/js/bundle.js:91:34)
    at train (http://localhost:3000/static/js/bundle.js:242:41)

Hmm, this could be related to your custom build of ORT Web using different Emscripten parameters (like PTHREAD_POOL_SIZE) to the normal build, but that doesn't seem likely if you just followed their usual build instructions.
One other guess is that your local machine has a larger-than-normal number of threads, and the normal build isn't "prepared" for that number. In that case I think it's probably a bug with ORT Web. Can you try putting the following line after the ort.env.wasm.proxy line that I added:
ort.env.wasm.numThreads = 2;

I think the default value is navigator.hardwareConcurrency/2 - i.e. half the number of cores/threads that your OS reports to the browser.
And also try this demo to see if it works on your machine (it takes a minute or so to init due to huge number of ops):
https://josephrocca.github.io/super-resolution-js/

Nah that site didn't work either

I'm using Edge, so yeah basically Chrome. I have 32GB of RAM.
With ort.env.wasm.numThreads = 2; but without ort.env.wasm.proxy = true;, it works but it's much slower.
With ort.env.wasm.numThreads = 8;, it's was about the same speed as before these changes but the UI seems more responsive.
I do get this output with 8 threads and got some of that but less times with 2 threads:
ort-wasm-threaded.js:850

       Tried to spawn a new thread, but the thread pool is exhausted.
This might result in a deadlock unless some threads eventually exit or the code explicitly breaks out to the event loop.
If you want to increase the pool size, use setting `-s PTHREAD_POOL_SIZE=...`.
If you want to throw an explicit error instead of the risk of deadlocking in those cases, use setting `-s PTHREAD_POOL_SIZE_STRICT=2`.
ia @ ort-wasm-threaded.js:850
ort-wasm-threaded.js:1776 Heap resize call from 16777216 to 20185088 took 0.1899999976158142 msecs. Success: true
2ort-wasm-threaded.js:850

       Tried to spawn a new thread, but the thread pool is exhausted.
This might result in a deadlock unless some threads eventually exit or the code explicitly breaks out to the event loop.
If you want to increase the pool size, use setting `-s PTHREAD_POOL_SIZE=...`.
If you want to throw an explicit error instead of the risk of deadlocking in those cases, use setting `-s PTHREAD_POOL_SIZE_STRICT=2`.
ia @ ort-wasm-threaded.js:850
ort-wasm-threaded.js:1776 Heap resize call from 20185088 to 24248320 took 0.12999999523162842 msecs. Success: true
ort-wasm-threaded.js:850

       Tried to spawn a new thread, but the thread pool is exhausted.
This might result in a deadlock unless some threads eventually exit or the code explicitly breaks out to the event loop.
If you want to increase the pool size, use setting `-s PTHREAD_POOL_SIZE=...`.
If you want to throw an explicit error instead of the risk of deadlocking in those cases, use setting `-s PTHREAD_POOL_SIZE_STRICT=2`.
ia @ ort-wasm-threaded.js:850
ort-wasm-threaded.js:1776 Heap resize call from 24248320 to 29097984 took 0.17499999701976776 msecs. Success: true

I think it's no longer using SIMD, because IIUC it should be loading ort-wasm-simd-threaded.js rather than ort-wasm-threaded.js (shown in the error message you pasted). So that probably explains why it doesn't seem to be giving you any boost but I'm not sure why it's suddenly not using SIMD.
This superresolution demo that I linked earlier loads ort-wasm-simd-threaded.js and runs fine for me in Chrome. So there's something weird happening here related to one or more of: Edge, your custom build of ORT Web, and the specific model that you're loading.

It seems like ArrayBuffer at index 2 is already detached is caused by ort.env.wasm.proxy = true, and if you could create a minimal example of this, including the ORT Web build instructions that you used, and post an issue on the onnxruntime repo, then the pros at ORT Web might be able to take it from here.
Another minimal example, but without ort.env.wasm.proxy = true would show that SIMD is not loading when it should be, and those "thread pool is exhausted" warnings.

Ideally you'd be able to reproduce these bugs/errors somehow without your custom build - I think that would raise the eyebrows of the ORT Web maintainers more. Swapping out the custom build for a normal build, and your current model (with training ops) for one that works without training ops would tell you whether it's training-ops-related.
Also, I realised that this error is probably not OOM-related, or at least not in the same way as that other issue I linked, since the number would indicate ~150mb, rather than 1.5gb. So if you could test that on Chrome then that would be interesting because it might be an Edge-related bug. I've tested on Edge (Linux) and it works fine for me.

BTW I tried using https://josephrocca.github.io/super-resolution-js/ in Google Chrome and I got a similar error to what I got in Edge: