WIP: Support for Additional Registry storage backends

Introduces additional registry storage options beyond local storage to resolve #49

The following are several configurations that can be used to test this PR:
Azure:
apiVersion: redhatcop.redhat.io/v1alpha1
kind: QuayEcosystem
metadata:
  name: example-quayecosystem
spec:
  quay:
    keepConfigDeployment: true
    registryBackends:
      - name: azure
        azure:
          azure_container: <container>
          azure_account_name: <account_name>
          azure_account_key: <account_key>
    imagePullSecretName: <pull secrert>

AWS S3
apiVersion: redhatcop.redhat.io/v1alpha1
kind: QuayEcosystem
metadata:
  name: example-quayecosystem
spec:
  quay:
    keepConfigDeployment: true
    registryBackends:
      - name: aws
        s3:
          s3_access_key: <access_key>
          s3_bucket: <bucket>
          s3_secret_key:<secret_key>
          host: <host>
    imagePullSecretName: <pull secrert>

Replicated S3
apiVersion: redhatcop.redhat.io/v1alpha1
kind: QuayEcosystem
metadata:
  name: example-quayecosystem
spec:
  quay:
    keepConfigDeployment: true
    enableStorageReplication: true
    registryBackends:
      - name: aws-1
        s3:
          s3_access_key: <access_key>
          s3_bucket: <bucket>
          s3_secret_key:<secret_key>
          host: <host>
          replicateByDefault: true
      - name: aws-2
        s3:
          s3_access_key: <access_key>
          s3_bucket: <bucket>
          s3_secret_key:<secret_key>
          host: <host>
          replicateByDefault: true
    imagePullSecretName: <pull secrert>

Extra CA Certificates can now be added using the following example

Create Secret containing CA certificate (example uses a certificate called extraca.crt)

oc create secret generic extracert1 --from-file=extraca.crt=<certificate_file>

Create the QuayEcosystem resource
apiVersion: redhatcop.redhat.io/v1alpha1
kind: QuayEcosystem
metadata:
  name: example-quayecosystem
spec:
  quay:
    keepConfigDeployment: true
    imagePullSecretName: redhat-pull-secret
    extraCaCerts:
      - secretName: extracert1

The extraCaCerts property has been reorganized. Here is an example of how to leverage new configFiles property in context to the Swift (OpenStack) registry backend
apiVersion: redhatcop.redhat.io/v1alpha1
kind: QuayEcosystem
metadata:
  name: example-quayecosystem
spec:
  quay:
    registryBackends:
      - name: swift
        swift:
          auth_url: <auth url>
          auth_version: "3"
          ca_cert_path: "conf/stack/<filename_from_secret>"
          swift_password: <password>
          swift_user: <username>
          swift_container: <container>
          storage_path: /datastorage/registry
          os_options:
            object_storage_url: <object_storage_url>
            project_id: <project_id>
            user_domain_name: <user_domain_name>
    configFiles:
      - secretName: <secret>
  imagePullSecretName: redhat-quay-pull-secret

@thomasmckay this is ready for review and merge


Anjali-Kshirsagar.txt file added

anjali.txt file created

LGTM 🥳
Thanks for your contribution 🤩 @Anjali-Kshirsagar


[Vue PWA] Feature - Inject environment variables in service-worker.js

What problem does this feature solve?
We need to inject environment variables in service-worker.js
process.env.VUE_APP_MY_VAR should be replaced by the DefinePlugin of webpack (automatically configured by Vue CLI) by a value defined in my .env but it works for all files except the "service-worker.js"
My vue.config.js
module.exports = {
  transpileDependencies: [],
  configureWebpack: {
    resolve: {
      symlinks: false
    }
  },
  pwa: {
    workboxPluginMode: 'InjectManifest',
    workboxOptions: {
      swSrc: 'public/service-worker.js'
    }
  }
}

What does the proposed API look like?
I found two obscure solutions for this problem :
The first one : https://stackoverflow.com/a/57051150/4864628
The second (better): https://github.com/diachedelic/vue-cli-plugin-bundle-service-worker
This last solution uses webpack to bundle the service-worker.js file. In my opinion this should be the default behavior of Vue PWA.

So... no way?

While waiting for the managers to take care of it, I recommend this link which served as an alternative
https://stackoverflow.com/a/57051150/4864628

The following line in webpack.config.js solves the problem to me:
module.exports = {
  ...
  externals: [ 'aws-sdk', 'commonjs2 firebase-admin' ],
  ...
};

This would be a great feature. I'm having the same issue and need to change the service worker to cache different API requests depending on deployed environment e.g. QA, UAT and Prod.

You can encapsulate variables into a query string appended to the service worker script path.
navigator.serviceWorker.register(
    import.meta.env.VITE_SW_PATH + (import.meta.env.VITE_SW_PATH.includes('?') ? '&' : '?') + 'vapid_public_key=' + import.meta.env.VITE_VAPID_PUBLIC_KEY
)

Use .env.development during development & .env.production or actual environment variables to influence what happens at build time.


Text nodes are not distributed to default slot

When entering text nodes in the host element, they are not distributed to the default slot.
Live Demo
http://codepen.io/oridan/pen/rrgvQY?editors=1000
Expected Results
The live demo should show two rows as follows:
[Icon] item 1
[Icon] item 2
Actual Results
I see just two icons:
[Icon]
[Icon]
Browsers Affected

[x] Chrome
[x] Firefox
[?] Edge
[x] Safari 9
[?] Safari 8
[?] IE 11

Versions

Polymer: v1.7.0
webcomponents: v0.7.22

In this case default slot gets shimmed to <content select=":not([slot])">, which seems not to work on anonymous nodes.

Unfortunately my PR fixes shady only.  How would I go about resolving this failing test in shadow?

Unfortunately we can't make a shady-only fix, so we can't take @TomK's solution.
I think we're going to resolve this by rolling back the automatic :not([slot]) selector for catch-all <slot>'s since it was a little too fancy trying to match the V1 changes to how default-slot is not take-all but rather only selects non-slotted nodes, and in the process broke textNode selection.
Instead, we'll just convert catch-all <slot>'s to catch-all <content>, and document that if the user is OK with not selecting textNodes, they can manually add the :not([slot]) selector and get more fidelity with V1.

Any update on this? It's a blocker for deploying 1.7 for us.

@ChadKillingsworth you should be able to convert all your <content select="..."> tags to <slot name="..."> tags, but leave any default <content> tags as they are until a fix is released.
I appreciate that this is not ideal as it means you will need to change them to slots for 2.0.  However, It may be sufficient for your deployment in the meanwhile.

We can make that work for now. Thanks.

I think we have a workable strategy now.
Basically, there is no good way to transform this slot construction into content:
<slot></slot>

Middle?

<slot name="specific"></slot>

and keep text nodes working.
Instead, it will have to be up to the user to have the "fallback" slot last in the order, and if necessary, use flexbox or transform to move the visual DOM into the desired position.
Here's an example using flexbox ordering to simulate the above DOM: http://jsbin.com/kugudot/2/edit?html,output


[Feature request] Spawning near the death location within a configurable radius

I love the idea of having an extra respawn option, but perhaps of configurable difficulty? What are your thoughts? Better Spawn does something a bit similar but this mod differs in providing an additional option rather than replacing the existing spawn button.

So essentially you want to add an option which allows you to configure a radius around the death location point? So instead of respawning right at that point, it picks a random location in that radius?

Sorry for delay - yes I was proposing something like an option to essentially "Spawn Near" rather than spawn at death. Within a configurable distance, i.e. to add a bit more configurable difficulty

@Nyfaria Up to you whether you want to do this

@Nyfaria Up to you whether you want to do this

hmm ill see about maybe doing it when i push the next update


How should [INTERFACE_]{C,CXX}_STANDARD and [INTERFACE_]{C,CXX}_EXTENSIONS affect cflags and cxxflags?

Does CMake compute the mapping and fill in [INTERFACE_]COMPILE_OPTIONS for us, or do we have to re-implement that functionality?

Conan should probably not pull it up into the flags (if anything at all).
The idea is that it's hard to reason about a global flag string if all subprojects fight for the right to control it. And with the user too! It complicates the process of forming and checking the valid flag string for the whole DAG.
Projects should instead operate on the input flag string and explicitly fail if there are incompatibilities.

@Minimonium does Conan have a way to model "minimum C++ standard" in cpp_info or elsewhere? Will it (i.e. is there an open issue)?

Ok, I think it should make a best-effort check, then.


Add info - When not to use Radix

In the Getting started section, add a new page
When not use Radix
These are not supported in Radix, however some can be done using workarounds
some info....
No direct on-prem connectivity
Need to use own terraform configurations
Need to use own helm charts or flux
Need to use DAPR
Need to use sidecars
Need to have direct access to Kubernetes components (pods, secrets, etc.)
Need low-latency persistant storage (eg. databases and similar)
Needs to accept traffic other than HTTP (eg. mqtt or UDP)
need to run own operators (e.g. redis operator to run Redis database in cluster)

Feedback from DynaGeo team:
https://github.com/equinor/dynageo/issues/4128


[Indexing] Add Indexing dialect

Add boilerplate for Indexing dialect.

Looks good as far as I can tell: I don't have a strong enough sense about the whole problem space to say something about the op but the boilerplate code etc looks good!

Just a btw - that op is just upstream tensor.gather (added by @nicolasvasilache) but with the small addition of DeclareOpInterfaceMethods<InferTypeOpInterface>. I plan to upstream (very shortly) whatever gets worked out here regarding its semantics.

This was super useful to go through for me, though I am still struggling to produce intuitive representations of these multi-dimensional slices in my head...

I don't think it's useful to in fact picture the slices (unless you generally can picture things in n-D lol). Instead I think it's better to just focus on the mapping between the numpy syntax and the indexing dialect syntax. So I made this explainer for indexing.gather (I will add it to the repo when it comes time for docs):


feat(constraints): Supports constraints for Marathon provider

Needs a rebase :)

Ping @containous/traefik

LGTM


sub configs .sqlfluff not recognized

I am using sqlfluff through pyenv and managed to get the extension mostly working. I set the path explicitly. When I use this path and sqlfluff by command line it recognizes .sqlfluff config files deeper in the project. The extension unfortunately only picks up the top level config in the project.
Is this project still getting support?

@roivant-matts Are you still seeing this issue in 0.1.0? If so, possibly try setting the workingDirectory configuration. You should be able to use workingDirectoyr="${fileDirname}" or something similar to set the working directory at the same location as the file. SQLFluff should then pick up the configs.

Thanks! I am still having trouble. It could be my lack of knowledge with sqlfluff config though. Linting is working, but I can't get it to pickup config of jinja variables. e.g.
This is what I currently have:
[sqlfluff]
dialect = bigquery
[sqlfluff:templater:jinja:context]
staging_prefix=tcb_raw
files_to_ingest=files_to_ingest
I can't be sure if either config is picked up, but the variables are not and I get for example:
Undefined jinja template variable: 'staging_prefix' in a template using that var
I set the workingDirectory by var and explicitly to the root of my repo where I have a .sqlfluff file. I also have a .sqlfluff file living with a specific set of templates. Even if I put the more specific jinja:context config in either it does not seem to pickup.
I had an environment to debug the extension, but this is lost now :)

ok, actually I have it working again as it was before (was pyenv mistake). Basically, onSave takes config properly but onType ignores my nested config.

Interesting, this might be a SQLFluff issue. When doing onSave I pass in the file path and let SQLFluff read from the file directly, but when doing onType I have to stream the contents of the file directly via stdin to SQLFluff. My guess is SQLFluff does configuration detection differently for those two options. I had hoped directly using the workingDirectory might fix that, but thinking about it further it should already be using the file location as the default working directory so I am not sure that setting really matters in this case. I will take a closer look when I get some time, but my guess now is you might have to use the onSave option.

I have the same issue with nested configs not being detected.
My structure is the following:
swlp-main (project root)
swlp-main/.sqlfluff (main config with 'dialect=none')

swlp-main/packages/swlp-models/migrations/mysql (dir containing migration files for mysql in 3 subdirectories)
swlp-main/packages/swlp-models/migrations/mysql/.sqlfluff (config file only setting 'dialect=mysql')

swlp-main/packages/swlp-models/migrations/sqlite (dir containing migration files for sqlite in 3 subdirectories)
swlp-main/packages/swlp-models/migrations/mysql/.sqlfluff (config file only setting 'dialect=sqlite')

When I run sqlfluff lint or sqlfluff fix while my CWD is the project root all works as intended.
The linting via the VSCode extension ("sqlfluff.linter.run": "onSave") also works like intended. Config files are picked up and the different dialects are used for their respective directories.
I don't use onType but I can kind of understand the issue with "sqlfluff.linter.run": "onType" because there is no file being linted, so sqlfluff has no "file working directory" and can propably only rely on a passed config file (via --config) I guess.
My problem lies with the formatting part of sqlfluff. Just like with "lint onType" the config files are not being picked up when I format a file. And I get the same result when I use "format onSave" or manually format via the command palette.
Here is the output:
------------------------------------------------------------

Format triggered for /home/admin-riedelc/projects/swlp-main/packages/swlp-models/migrations/sqlite/deploy/add_users.sql

------------------------------------------------------------

Reading from stdin, not file, input may be dirty/partial

--------------------Executing Command--------------------

sqlfluff fix --force -

------------------------------------------------------------

Received close event, code 1 signal null
Raw stdout output:

------------------------------------------------------------

------------------------------------------------------------

Raw stderr output:

------------------------------------------------------------

Traceback (most recent call last):
  File "/home/admin-riedelc/.local/bin/sqlfluff", line 8, in <module>
    sys.exit(cli())
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/cli/commands.py", line 1017, in fix
    _stdin_fix(lnt, formatter, fix_even_unparsable)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/cli/commands.py", line 755, in _stdin_fix
    result = linter.lint_string_wrapped(stdin, fname="stdin", fix=True)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/core/linter/linter.py", line 991, in lint_string_wrapped
    linted_path.add(self.lint_string(string, fname=fname, fix=fix))
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/core/linter/linter.py", line 829, in lint_string
    parsed = self.parse_string(
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/core/linter/linter.py", line 761, in parse_string
    rendered = self.render_string(in_str, fname, config, encoding)
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/core/linter/linter.py", line 697, in render_string
    config.verify_dialect_specified()
  File "/home/admin-riedelc/.local/pipx/venvs/sqlfluff/lib/python3.10/site-packages/sqlfluff/core/config.py", line 981, in verify_dialect_specified
    raise SQLFluffUserError(
sqlfluff.core.errors.SQLFluffUserError: No dialect was specified. You must configure a dialect or specify one on the command line using --dialect after the command. Available dialects:
ansi, athena, bigquery, clickhouse, databricks, db2, duckdb, exasol, greenplum, hive, materialize, mysql, oracle, postgres, redshift, snowflake, soql, sparksql, sqlite, teradata, trino, tsql

------------------------------------------------------------

When I set "sqlfluff.config": "${workspaceFolder}/.sqlfluff" I get the same result except that the executed command has the --config flag included.
Based on the Output I assume that the issue with formatting is the same as with "lint onSave". But I don't understand why for manual formatting stdin is used? Couldn't you pass the file path instead?
The same question goes for "format onSave". Or does the formatter hook in before the file is acctually saved on disk?

@Cielquan You could try setting sqlfluff.experimental.format.executeInTerminal to true. This forces the extension to use the file path when formatting instead of using stdin. I use stdin by default because allowing sqlfluff to format the file directly can cause issues if any changes are made to the document while formatting is occurring. Using this option also requires the file to be saved for formatting to occur, this extension saves the file for you so not much of an issue, but worth noting.
Let me know if that setting fixes your issue

@RobertOstermann Yes that fixes the issue. Thanks a lot.


Drop position attribute for footer

Fixes https://github.com/jenkins-infra/account-app/issues/250

Something happened to the footer, it takes up more space here than on jenkins.io and other pages using jio components. It also doesn't stick to the page bottom 🤔


esp-idf/examples/ethernet/eth2ap become watchdog fail. (IDFGH-1458)

Environment
freeRTOS version:V8.2.0
NEWLIB version:2.2.0
lwIP version:2-0-3-255
ESP-IDF version:v4.0-dev-1095-g16014079f

Problem Description
I updated esp-idf from v4.0-dev-1018-gbbafd5066-dirty to v4.0-dev-1095-g16014079f.
esp-idf/examples/ethernet/eth2ap become watchdog fail.
Before update,it's worked fine.

Steps to repropduce

Same issue to 3726

Hello.
I'm waiting your fix.

I tried esp-idf/examples/protocols/sntp using eth2ap.
Is this correct?

Theoretically it can work. From your log I can see your station has got an IP address via the wifi provided by another esp32 board, right? But for the tcpip_adapter error info, I don't know the reason. You might need to monitor the log from both the two esp32 board, to see what happened on eth2ap example when you got this tcpip_adapter error.

Hello.
This is the log from both the two esp32 board.
eth2ap side:
I (0) cpu_start: App cpu up.
I (386) heap_init: Initializing. RAM available for dynamic allocation:
I (393) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (399) heap_init: At 3FFB88C0 len 00027740 (157 KiB): DRAM
I (406) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (412) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (418) heap_init: At 40090468 len 0000FB98 (62 KiB): IRAM
I (425) cpu_start: Pro cpu start user code
I (443) spi_flash: detected chip: generic
I (443) spi_flash: flash io: dio
I (443) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (514) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (524) eth_example: Ethernet Started
I (534) wifi: wifi driver task: 3ffb94fc, prio:23, stack:3584, core=0
I (534) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (534) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (564) wifi: wifi firmware version: 82c4fce
I (564) wifi: config NVS flash: enabled
I (564) wifi: config nano formating: disabled
I (564) wifi: Init dynamic tx buffer num: 32
I (564) wifi: Init data frame dynamic rx buffer num: 32
I (574) wifi: Init management frame dynamic rx buffer num: 32
I (574) wifi: Init management short buffer num: 32
I (584) wifi: Init static rx buffer size: 1600
I (584) wifi: Init static rx buffer num: 10
I (594) wifi: Init dynamic rx buffer num: 32
I (6094) eth_example: Ethernet Link Up
I (6204) phy: phy_version: 4101, 100880e, Jul 12 2019, 19:32:06, 0, 0
I (6204) wifi: mode : softAP (30:ae:a4:ca:e1:43)
I (6204) wifi: Total power save buffer number: 16
I (6204) wifi: Init max length of beacon: 752/752
I (6214) wifi: Init max length of beacon: 752/752
I (47044) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (47044) wifi: station: 3c:71:bf:4f:c1:a0 join, AID=1, bgn, 40U
I (47064) eth_example: Wi-Fi AP got a station connected
I (54754) wifi: station: 3c:71:bf:4f:c1:a0 leave, AID = 1, bss_flags is 134243, bss:0x3ffc8460
I (54754) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<255,255>, prof:1
I (54764) eth_example: Wi-Fi AP got a station disconnected

sntp sido:
I (0) cpu_start: Starting scheduler on APP CPU.
I (468) example: Boot count: 1
I (468) example: Time is not set yet. Connecting to WiFi and getting time over NTP.
I (528) wifi: wifi driver task: 3ffc0d08, prio:23, stack:3584, core=0
I (528) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (528) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (558) wifi: wifi firmware version: 82c4fce
I (558) wifi: config NVS flash: enabled
I (558) wifi: config nano formating: disabled
I (558) wifi: Init dynamic tx buffer num: 32
I (558) wifi: Init data frame dynamic rx buffer num: 32
I (568) wifi: Init management frame dynamic rx buffer num: 32
I (568) wifi: Init management short buffer num: 32
I (578) wifi: Init static rx buffer size: 1600
I (578) wifi: Init static rx buffer num: 10
I (588) wifi: Init dynamic rx buffer num: 32
I (588) example_connect: Connecting to eth2ap...
I (698) phy: phy_version: 4101, 100880e, Jul 12 2019, 19:32:06, 0, 0
I (708) wifi: mode : sta (3c:71:bf:4f:c1:a0)
I (828) wifi: new:<1,1>, old:<1,0>, ap:<255,255>, sta:<1,1>, prof:1
I (1808) wifi: state: init -> auth (b0)
I (1818) wifi: state: auth -> assoc (0)
I (1828) wifi: state: assoc -> run (10)
I (1848) wifi: connected with eth2ap, channel 1, 40U, bssid = 30:ae:a4:ca:e1:43
I (1848) wifi: pm start, type: 1

I (3008) tcpip_adapter: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (3508) example_connect: Connected to eth2ap
I (3508) example_connect: IPv4 address: <IP_ADDRESS>
I (3508) example_connect: IPv6 address: fe80:0000:0000:0000:3e71:bfff:fe4f:c1a0
I (3518) example: Initializing SNTP
I (3518) example: Waiting for system time to be set... (1/10)
I (5528) example: Waiting for system time to be set... (2/10)
I (7528) example: Waiting for system time to be set... (3/10)
I (8138) example: Notification of a time synchronization event
I (9528) wifi: state: run -> init (0)
I (9528) wifi: pm stop, total sleep time: 5239617 us / 7677520 us

I (9528) wifi: new:<1,0>, old:<1,1>, ap:<255,255>, sta:<1,1>, prof:1
E (9528) tcpip_adapter: handle_sta_disconnected 197 esp_wifi_internal_reg_rxcb ret=0x3014
I (9568) wifi: flush txq
I (9568) wifi: stop sw txq
I (9568) wifi: lmac stop hw txq
I (9568) wifi: Deinit lldesc rx mblock:10
I (9578) example_connect: Disconnected from eth2ap
I (9578) example: The current date/time in New York is: Tue Jul 16 05:48:33 2019
I (9578) example: The current date/time in Shanghai is: Tue Jul 16 17:48:33 2019
I (9588) example: Entering deep sleep for 10 seconds

Does sntp work like this when you connect to a real router not the eth2ap?

I connected to a real router not the eth2ap.
This is not due to eth2ap.
I (0) cpu_start: App cpu up.
I (403) heap_init: Initializing. RAM available for dynamic allocation:
I (410) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (416) heap_init: At 3FFB9210 len 00026DF0 (155 KiB): DRAM
I (422) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (428) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (435) heap_init: At 40090C20 len 0000F3E0 (60 KiB): IRAM
I (441) cpu_start: Pro cpu start user code
I (459) spi_flash: detected chip: generic
I (460) spi_flash: flash io: dio
I (460) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (468) example: Boot count: 3
I (468) example: The current date/time in New York is: Tue Jul 16 10:01:14 2019
I (478) example: The current date/time in Shanghai is: Tue Jul 16 22:01:14 2019
I (488) example: Entering deep sleep for 10 seconds

Regarding the  esp_wifi_internal_reg_rxcb error, it should was reported already and the fix should be in master soon (https://github.com/espressif/esp-idf/issues/3587#issuecomment-511185777)

OK.
I'm waiting for master fix.


Avoid memory copy on MainThreadDispatcher

MainThreadDispatcher's internal queue worker system(ThreadSafeQueueWorker)’s current implementation is very simple.
I think it can improve so avoid memory copy.
My idea is use RingBuffer(like LMAX Disruptor? https://github.com/LMAX-Exchange/disruptor/wiki/Blogs-And-Articles )

Ah, MainThreadDispatcher already doesn't copy:)
(only do copy ensure capacity timing)
so, I reduced clear action, it’s enough.


Import fefc74a744: Made domain checkin timeouts longer for more forgiving loading on slow connections (by Caitlyn)

This is an automated proposal to look at a commit made by Caitlyn and import it into Overte

Commit:
fefc74a744b386a54d18448d6d4d67e37f486c9c

Author:
Caitlyn

Date:
Thu, 19 Mar 2020 00:24

Made domain checkin timeouts longer for more forgiving loading on slow connections

Stats:

Filename
Stats
Lines
Added
Removed
Lines in blame

libraries/networking/src/DomainHandler.cpp

2
1
1
1

libraries/networking/src/DomainHandler.h

2
1
1
1

2 files
-
4
2
2
2

To work on this, please assign the issue to yourself, then look at the commit and decide whether this would be a good addition to Overte.

If the commit is useful, tag it with "Tivoli: Keep", and keep it open until it's merged.
If the commit is not useful, tag it with "Tivoli: Discard", and close it.
If the commit is not useful right now, but might be later, tag it with "Tivoli: Maybe later", and close it.
If it's hard to decide, tag it with "Tivoli: Discuss", and keep it open.

Useful commits should be submitted as a PR against Overte. Tag this issue in PR, so that it's automatically closed once the PR is merged.
You can cherry-pick this issue with this command:
git cherry-pick fefc74a744b386a54d18448d6d4d67e37f486c9c

This looks potentially interesting


refactor(jQlite): Add the ability to use query selector without jQuery

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
refactor
What is the current behavior? (You can also link to an open issue here)
angular.element('.my-selector') throws an error if jQuery is not included.
What is the new behavior (if this is a feature change)?
angular.element('.my-selector') now finds the element and wraps it in a jQlite (or jQuery) object.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Other information:
angular.element threw an error if we tried to use query selector
directly without jQuery. I thought that this was a silly little
fix for the framework.
A lot of the projects that I've worked for
the past years are only including jQuery to use query selectors on
the app (I know that are options for this), and I'm only making this PR
because I think it's unnecessary to use
angular.element(document).find() to accomplish such a small thing and
to get the jQlite wrapper with the goodies.
Now we can do this, without jQuery:
angular.element('.something')
And get the same result.

There was extensive discussion about making .find(selector) work and we decided against it as it was impossible to defer to querySelectorAll in a simple way that will agree with jQuery (& common sense) due to a design bug of querySelectorAll with respect to running from non-document elements.
But these arguments don't extend to root-level selectors so I can see angular.element(selector) working in JQLite... I just want to make it clear we're not going to support .find(selector).
Thanks for the PR!

@rafaelfragosom Please make sure grunt test passes for you locally, there are some errors.

@mgol I agree, .find(selector) is too ugly for such a small DOM query.
I only want to be on the same page here. Are these changes wellcome or should I close this issue? Is querySelector an option or should I use a different approach? I can see the compatibility at almost 100% on caniuse.
Let me know so I can put some more effort on this.
Thank you.

@rafaelfragosom I consulted the team and we're OK with making angular.element(selector) work without jQuery but .find(selector) should still fail. As long as those conditions are met, we will accept a PR.
We'll need unit tests that confirm both of those conditions are met. Would you be willing to work on that?

@rafaelfragosom Hey, are you still interested in finishing this PR?


shouldAsyncValidate/asyncValidate not called if form is pristine on submit

Are you submitting a bug report or a feature request?
Bug
What is the current behavior?
shouldAsyncValidate does not get called if no fields have been touched.
What is the expected behavior?
If the form is pristine and user submits, asyncValidation should be called. I tried to override the behavior with shouldAsyncValidate but that also does not get called if the form is pristine and a user hits submit. As soon as I touch a field, however, all of the async errors are displayed. Any thoughts?
What's your environment?
redux-form 6.7.0

Since you didn't attach any examples/code sandbox, I'll need to investigate; but for now, I'm tagging this as a bug anyway.

Was not able to reproduce on codesandbox (see https://codesandbox.io/s/VG4Y6vpX). I'm not sure why it doesn't fire for me locally, but I will investigate. Closing for now.


Add import workspace functionality

One of the main feartures of the app is checking in workspaces to git and checking them out to use in Workbench. To support this we need the additional functionality of importing a checked-out workspace into the users Workbench.

Will work on that

Working on that


ng serve confusing raw size?

Command
serve
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I just saw that ng serve raw size seems to be wrong? In the past, I at least thought they were correct.(When we still used webpack)

We see a raw size of 20.22 KB for the main bundle and 33.24 KB for the polyfills. Let's see what the browser says.

Not even close.
Then I thought, okay, maybe these are estimates for when I eventually build the project. So let's build the project.

The main bundle is now 193 KB, but this time at least the 193 KB is correct. Interestingly, the polyfills have the exact same size in ng serve --configuration production as in ng build, at least in the console, but not in the browser.
Am i missing something? Am I not reading the numbers correct do they mean something different?
They are atleast confusing i would say.
Also just standard ng serve numbers are also not the same as in the browser?
EDIT:
Ok looks like vite is adding allways the sourcemaps inline in serve without it its 20.22kb,
And the main size is smaller in serve than in build because of the cached data created.
I was pretty confused by it and i can imagine many others are also confused by it especially the behavior atleast to my memory changed compared to webpack.
Would it maybe be possible to aknowledge all files in the console?
Minimal Reproduction
ng new testSize
cd testSize
ng serve --configuration production
Exception or Error
No response
Your Environment
Angular CLI: 17.3.7
Node: 20.12.2
Package Manager: npm 10.5.0
OS: darwin arm64

Angular: 17.3.8
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.7
@angular-devkit/build-angular   17.3.7
@angular-devkit/core            17.3.7
@angular-devkit/schematics      17.3.7
@angular/cli                    17.3.7
@schematics/angular             17.3.7
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.5

Anything else relevant?
It´s an behavior of showing the raw size in the console for ng serve completly different when compared to webpack.
Webpack shows for example 318.85kb for the main.js and the browser loads exactly 318.85kb its intuitive and predictable,
If we compare it to the current esbuilder/vite solution which adds sourcemaps (Not Angulars fault) and uses the cache on the file system and than shows 20.22kb which is literally impossible and absolutely unintuitive.
It would even be better to show no number at this point as it literally can't be evaluated for anything and only will bring confusion to anyone when they compare ng serve with ng build and the ng serve looks smaller in the cli log
No response

Development servers can perform transformation of code at runtime (typically on request) to support development workflows such as HMR, dependency prebundling, debugging, etc.  The downloaded size will not necessarily match the initial built size nor is it intended to do so within the development server.  While it is possible to use a production configuration with the development server, the result will still be a development-oriented browser experience.

@clydin this is only partially correct i looked into it , the main.js is bigger because sourcemaps are inlined inside of it.
Without it its exactly 20.22kb, than is the question why is it smaller than build? The Reason is in serve it uses the angular cache, all in all its very confusing and should in someway be reflected in the console.

Yes, sourcemaps may be inlined during development. The Vite-based development server adds them when it transforms a file to aid in debugging. To support a faster edit/refresh cycle, it also prebundles dependencies which is both why the code size is smaller and primarily why the files are transformed.
This is working as intended as the primary goal of the development server is to support the edit/refresh cycle. File sizes during development workflows are intended to be representative only and may vary greatly from a production deployment. Using a production configuration with the development server is also typically not a recommended workflow as it can cause a significant negative effect on edit/refresh times.
A note could be added to the console output to mention potential browser differences in transfer size. However, the console size information is still useful especially for larger projects with defer block and router usage where code splitting is present. The sizes can provide a useful indicator of potential issues in these cases.

Hi,
Raw file sizes do not reflect development server per-request transformations => what does it mean ? How to debug ?

Hi,
Raw file sizes do not reflect development server per-request transformations => what does it mean ? How to debug ?


Azure Crossplane User Agent Detail

What problem are you facing?
It would be great to be able to know which client:identity is calling into my Azure subscription, this is what I see when using native Crossplane and TerraForm:
This is the UserAgent for CrossPlane using identity 1:
Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 hashicorp/go-azure-sdk/managedclusters/2022-09-02-preview HashiCorp Terraform/1.2.1 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev

This is the UserAgent for TF using identity 1:
Go/go1.17.5 (amd64-darwin) go-autorest/v14.2.1 Azure-SDK-For-Go/v62.3.0 resources/2020-06-01 HashiCorp Terraform/1.4.6 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/3.0.2..

How could Crossplane help solve your problem?
Would you be able to add some detail that Crossplane is the client, which provider, provider version, OS type, cpuArch in the UserAgent?
Thank you!

Hi @danielsollondon,
#687 configures a partner ID (a9cee75d-8f11-42e4-bc19-953757f4ea3c) for this provider, which results in a UserAgent similar to the following as mentioned in the PR description:
HashiCorp/go-azure-sdk (Go-http-Client/1.1 capabilities/2023-11-01) HashiCorp Terraform/ (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev pid-a9cee75d-8f11-42e4-bc19-953757f4ea3c

If we register this UUID in the partner center, would this be sufficient for the attribution purposes?
Regarding the provider version, OS & CPU architecture, is there a specific syntax we need to follow? Would setting the UserAgent to something like the following (with a partner UUID) work?
HashiCorp/go-azure-sdk (Go-http-Client/1.1 capabilities/2023-11-01) HashiCorp Terraform/ (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev crossplane-provider-upjet-azure/v1.1.0 (arm64-darwin) pid-a9cee75d-8f11-42e4-bc19-953757f4ea3c

Or, without the partner UUID if we decide not to do it:
HashiCorp/go-azure-sdk (Go-http-Client/1.1 capabilities/2023-11-01) HashiCorp Terraform/ (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev crossplane-provider-upjet-azure/v1.1.0 (arm64-darwin)

And how can we test #687 to make sure it's working as expected, i.e., on the Azure side, we get something parsable with the desired information?
Thank you very much @danielsollondon.

Planning to merge #687 today but I want to keep this issue open to keep the conversion going. We can iterate on the implementation if we need any further enhancements/fixes.


Create a Docker FTP container

This may just require using an existing image from Docker Hub if we can find one that works. If not create a Dockerfile with a basic FTP service. This will be used to test Spark Connector with FTP provided data.

Docker compose entry added to create an FTP container. From within the docker directory use:
docker-compose up -d quasar_ftp

to start a FTP container.

Closed via #2471.


Converting tests to new module syntax

@scalvert Probably can close this PR now.  Did the same thing but would be too much in terms of merge conflicts.
https://github.com/sreedhar7/ember-app-scheduler/pull/22/files


Chain#link should return the chain

This would allow for nice chaining syntax:
Chain::new(handler).link(thing1).link(thing2)

Presumably, if Chain.link() is being updated, we should also update link_before(), link_after(), and around(), yes?
(As an aside, should around() be renamed to link_around() for consistency's sake?)

@AndrewBrinker yes and yes.
I am in favor of this change.

Cool. I am working on it now.

I think this should be closed.

This has been fixed, I'd like to reiterate the request for this issue to be closed.


COI - LDB workflow

We do not want a CRM ticket to be created for LDB folks. We want it to be sent directly to LDB an LDB mailbox. LDB mailbox to be confirmed.
AC

[ ] After supervisor approves, send pdf of the form, and attachments to [email TBD]
[ ] Email content should be as follows

SUB: TBD
TBD

@Stella-Archer tella confer with client about any different actions for LDB

need to do an explore ticket for attaching multiple files. rest of this is complete and waiting on email contents and ldb mailbox.

Cantact destination and email edits are being gathered in this document > https://bcgov.sharepoint.com/:w:/r/teams/03991/Shared Documents/Conflict of Interest/2024 Project Files/CoI UX test subjects.docx?d=w371abe9d00724210bc61235daebed56c&csf=1&web=1&e=jpAUed

Test this on dev. I have set it so all users go through the ldb workflow for testing. Just use your normal @gov.bc.ca email. Let me know when you are done and i will change it back.

Tested and received the LDB email!

changed the flow back so idir and ldb receive their respective emails. looks good to go.

Tested the employee emails, was not able to test supervisor emails or the email to LDB team. We can test that when we test with LDB employees

Worked great @Andrew-Vargas-bcgov  - can move to PROD for LDB testers, we can't test the supervisor side until then

@Andrew-Vargas-bcgov after we are finished testing with LDB people the final email is sent to > to<EMAIL_ADDRESS>as specified in the edits document >
https://bcgov.sharepoint.com/:w:/r/teams/03991/Shared Documents/Conflict of Interest/2024 Project Files/Conflict of interest_LDB Edits.docx?d=w18353bea5919421698111bcacb9664e1&csf=1&web=1&e=3MBQmk


loosen pins

Hey @conda-forge/rucio-clients!
Can you loosen the pins in this recipe and merge some of the latest versions?
I don't follow why stable packages like requests are pinned so tightly or why jsonschema has to be pinned down so strictly.

Hi @beckermr
Yes, It's on my todo list, I know it's lacking behind, but the dependencies will need some manual syncing.


A symbol is missing in inherited dependencies

Hi,
The documentation for the referenced field of the Symbol class says that it includes dependencies inherited from surrounding menus and if's.. However when I look at the value of the referenced field for COMEDI_NI_USB6501 (source), I don't see the USB symbol there:
> print(kconf.syms['COMEDI_NI_USB6501'].referenced)
set([<symbol COMEDI_USB_DRIVERS, tristate, "Comedi USB drivers", value m, user value m, visibility m, direct deps m, drivers/staging/comedi/Kconfig:1183>, <symbol COMEDI, tristate, "Data acquisition support (comedi)", value m, user value m, visibility y, direct deps y, drivers/staging/comedi/Kconfig:1>, <symbol STAGING, bool, "Staging drivers", value y, user value y, visibility y, direct deps y, drivers/staging/Kconfig:1>])

COMEDI_NI_USB6501 depends on COMEDI_USB_DRIVERS through an if, and COMEDI_USB_DRIVERS in turns depends on USB through a depends on. So AFAIU USB should be in referenced.
Is this a bug or there's something I misunderstand?
Thanks!

Hello,
referenced isn't transitive. It only includes "direct" references.
The reason dependencies from surrounding ifs and menus count as direct references has to do with dependency propagation. Basically, if FOO is just a shorthand for adding depends on FOO to each item within the if, and a depends on on a menu also gets propagated to all the items in it.
These two ways of defining two symbols A and B are equivalent:
With if:
if B

config A
	bool

endif

if C

config B
	bool

endif

With depends on:
config A
	bool
	depends on B

config B
	bool
	depends on C

In both cases, A ends with just B in referenced, and B ends up with just C.
To get transitive references, you'll have to calculate the transitive closure (I think that's the term...), recursively expanding the .referenced until no new symbols appear.
If you're only interested in the direct dependencies of a symbol (it's depends on, possibly inherited), have a look at Symbol.direct_dep btw. You can extract all the symbols in it with the global expr_items() function.

Ah, OK, I see. Maybe it makes sense to mention this in the documentation? The word inherited seems confusing to me here. Thanks!

Clarified the docstring and added some more details in https://github.com/ulfalizer/Kconfiglib/commit/814e2decd190d78b588dd775c1531dacd6bc38c6. Does it look okay?

Looks good, thanks you!


Remove unused webpack; other minor cleanups

squiggle-lang hasn't used webpack since December, I just forgot to remove the dep.

Codecov Report

Merging #1586 (62f74d8) into develop (725c28c) will increase coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head 62f74d8 differs from pull request most recent head 6afcc22. Consider uploading reports for the commit 6afcc22 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##           develop    #1586   +/-   ##
========================================
  Coverage    73.09%   73.09%
========================================
  Files           93       93
  Lines         5017     5018    +1
  Branches       838      846    +8
========================================
+ Hits          3667     3668    +1
  Misses        1326     1326
  Partials        24       24

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

Note that the Vercel Relative Value deployment is broken though.

That's ok, that deployment works only for relative-values PR.


Remove audience, platform, product, version, print

All unused.

@mjibson, I just got a local copy and served up the site. It's not rendering correctly. Not sure which changes caused this.
Docs home:

Install page:

I added the defaults back in. Works again.

Great. LGTM.


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1957 ms

Resolved: Bofrost.lu performance has improved in 5740152 after 8 minutes.


Make popup for auto poping Empowering Messages in Zoom Meeting Page

Make a page www.localhost:3000/message
Set few sample message for user
Make the message auto popup on Meeting page every 5 min while in the meeting
Make a toggle button to turn on/off the messages

We will not show the messaging every 5 mins.
We will show the message through the meeting inside our app (user can x out if they don't want to see it).


Add ID to Relationship, add follow unfollow test

Since the item of ID was included in Relationship, it added.
$ curl -X POST -H 'Authorization: Bearer xxxTOKENxxx' https://mstdn.jp/api/v1/accounts/4880/follow
{"id":4880,"following":true,"followed_by":true,"blocking":false,"muting":false,"requested":false}

$ curl -X POST -H 'Authorization: Bearer xxxTOKENxxx' https://mstdn.jp/api/v1/accounts/4880/unfollow
{"id":4880,"following":false,"followed_by":true,"blocking":false,"muting":false,"requested":false}

And, add AccountFollow and AccountUnfollow test.

Coverage increased (+2.7%) to 46.05% when pulling 13dd483b47f430ff1ba1d761eef93378e94a94bd on 178inaba:follow into b42014511bbd494e950b08b9072f8e8f1837feaa on mattn:master.

Test passed. Thanks. also fixing ID.


JekyllSupport.lookup_liquid_variables is called 7 times for every page, then stack overflows

Try a minimal plugin ... how many times is render called?


AOT build fails with angular 4.0.0-beta.4

AOT fails with angular 4 beta 4. Works with latest stable build of 2.4.5, so not 100% if it's a bug yet.
Anyway, the error I'm getting with angular 4 beta 4 is:
ERROR in [at-loader] _aot/app/node_modules/@ngrx/effects/src/effects.module.ngfactory.ts:35:67
    Argument of type 'Store<any>' is not assignable to parameter of type 'Observer<Actions>'.
  Types of property 'next' are incompatible.
    Type '(action: Action) => void' is not assignable to type '(value: Actions) => void'.
      Types of parameters 'action' and 'value' are incompatible.
        Type 'Actions' is not assignable to type 'Action'.
          Property 'type' is missing in type 'Actions'.

A minimum reproducible app attached below, though there's nothing special about it... just the standard increment/decrement example but with a timeout for the effects.
campaigns.zip

No longer an issue with angular 4.0.0-beta.7

issue with rc2 again? Or maybe just me?
Error at manage-users-effects.module.ngfactory.ts:87:68: Argument of type 'Store' is not assignable to parameter of type 'Observer'.

@karolmie1  I'm on angular 4-rc2 & effects 2.0.0 and everything works as before.

@guojenman Maybe your minimal example is too minimal? In case you would like to reproduce:
https://bitbucket.org/kmierzej/fragaria-webapp/branch/effects-angular4-issue99
You build with: yarn build:prod.

ERROR in [at-loader] compiled/node_modules/@ngrx/effects/src/effects.module.ngfactory.ts:33:67
TS2345: Argument of type 'Store' is not assignable to parameter of type 'Observer'.
Types of property 'next' are incompatible.
Type '(action: Action) => void' is not assignable to type '(value: Actions) => void'.
Types of parameters 'action' and 'value' are incompatible.
Type 'Actions' is not assignable to type 'Action'.
Property 'type' is missing in type 'Actions'.
ERROR in [at-loader] compiled/src/app/auth/token-services/token-services.module.ngfactory.ts:61:69
TS2345: Argument of type 'Store' is not assignable to parameter of type 'Observer'.
ERROR in [at-loader] compiled/src/app/prompt/login/login.module.ngfactory.ts:312:69
TS2345: Argument of type 'Store' is not assignable to parameter of type 'Observer'.
ERROR in [at-loader] compiled/src/app/prompt/prompt.module.ngfactory.ts:324:69
TS2345: Argument of type 'Store' is not assignable to parameter of type 'Observer'.
ERROR in [at-loader] compiled/src/app/view/manage-users/manage-users-effects.module.ngfactory.ts:87:68
TS2345: Argument of type 'Store' is not assignable to parameter of type 'Observer'.
ERROR in [at-loader] compiled/src/app/view/settings/settings-effects.module.ngfactory.ts:87:68
TS2345: Argument of type 'Store' is not assignable to parameter of type 'Observer'.

@karolmie1 the minimal example was just to illustrate the problem I was having w/ beta 4. My actual app is 20k+ lines of code and growing. Though I only have 2 effects classes which totals to around 400 lines of code.

@karolmie1 not at all. i cloned your repo and do see the error, though at a glance, I dont see anything terribly different from my build, except for config and build tools. I'd need to take a closer look but don't have the time at the moment.

I am facing the same issue with Angular 4.0.0 RC2, I think this has nothing to do with angular, this has to do with upgrading TS.

Related: https://github.com/ngrx/effects/issues/106


Help text doesnt fit the console window

Kind of self explanatory.  Maybe make a variable size console?  Not sure how to address just yet.

Made the help page full screen and added the stream command.


Annoying bug of code editor

Now, the code editor in the mainn view may:

Scroll suddenly when typing code
Scroll to the top when saving the file
Syntax Highlight disappear and the color of the whole text becomes the color of the first character when syntax highlighted after saving the file.

I haven't found any solutions so far, but I noticed that the scroll view will scroll to NSPoint(0, -0) after saving the file.

I will compare all the git versions and try to find the reason.

I will compare all the git versions and try to find the reason.

I found that it isn't because of minimap or line number view;
I reset the cocoa binding key path from "representedObject.contentString" to "representedObject.content.contentString" in one commit.
I will try to recover that and that may fixes.

I found that it isn't because of minimap or line number view;
I reset the cocoa binding key path from "representedObject.contentString" to "representedObject.content.contentString" in one commit.
I will try to recover that and that may fix.

I think this will not fix.. The result may disappoint me.

It worked a little.

Scroll suddenly when typing code

But this wasn't fixed.

No, No, No, that was fixed.

I will close this issue, but it may be reopened...


Fix error when add user has full name to team (#2973)

back port from #2973

fix error when add user has full name to team
add comment for extra uname check

LGTM

LGTM


Modularize dependencies

In the current setup many dependencies are pulled down into the project. This leads to a lot of node modules that may not be needed for some users, or that are only needed in dev environments, but not production.
Splitting up the dependencies, and giving more set up control, should result in a better DX.

Not doing


New version: DuongDieuPhap.ImageGlass version <IP_ADDRESS>2

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Automatic Validation ended with:

2024-04-30 18:39:13.398 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFC3613C11F: (caller: 00007FFC35EC8D6F) LogHr(1) tid(1f30) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFC36042B08: (caller: 00007FFC360EBC20) Exception(1) tid(1f30) 8A15005E ]
2024-04-30 18:39:13.398 [REPO] Failed to open available source: msstore
2024-04-30 18:39:17.388 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFC35C4C11F: (caller: 00007FFC359D8D6F) LogHr(1) tid(11b0) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFC35B52B08: (caller: 00007FFC35BFBC20) Exception(1) tid(11b0) 8A15005E ]
2024-04-30 18:39:17.388 [REPO] Failed to open available source: msstore
2024-04-30 18:39:25.363 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFC1F48C11F: (caller: 00007FFC1F218D6F) LogHr(1) tid(e54) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFC1F392B08: (caller: 00007FFC1F43BC20) Exception(1) tid(e54) 8A15005E ]
2024-04-30 18:39:25.363 [REPO] Failed to open available source: msstore
2024-04-30 18:39:26.534 [CLI ] No suitable installer found for manifest Microsoft.DotNet.DesktopRuntime.8 with version 8.0.4
2024-04-30 18:38:33.070 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFA0D66C11F: (caller: 00007FFA0D3F8D6F) LogHr(1) tid(cf4) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFA0D572B08: (caller: 00007FFA0D61BC20) Exception(1) tid(cf4) 8A15005E ]
2024-04-30 18:38:33.070 [REPO] Failed to open available source: msstore
2024-04-30 18:38:37.001 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFA0D66C11F: (caller: 00007FFA0D3F8D6F) LogHr(1) tid(18d8) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFA0D572B08: (caller: 00007FFA0D61BC20) Exception(1) tid(18d8) 8A15005E ]
2024-04-30 18:38:37.001 [REPO] Failed to open available source: msstore
2024-04-30 18:38:45.181 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FF9F2C4C11F: (caller: 00007FF9F29D8D6F) LogHr(1) tid(119c) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FF9F2B52B08: (caller: 00007FF9F2BFBC20) Exception(1) tid(119c) 8A15005E ]
2024-04-30 18:38:45.181 [REPO] Failed to open available source: msstore
2024-04-30 18:38:46.346 [CLI ] No suitable installer found for manifest Microsoft.DotNet.DesktopRuntime.8 with version 8.0.4

(Automated response - build 878.)


Feature Request - Ability to rename a peer

Is there a current way to rename a peer? Or if not, that would be a feature we'd (where we're testing innernet for use at work) find useful.
We understand the security implications of having immutable publickey/private IP tuples, which is fine. But we've run into a few instances were we need to move a peer and end up with cidrs full of peers like foo, foo_take2, foo_take3, etc. It'd be nice to be able to disable foo, then rename to diasabled (or whatever), and then create a new foo peer. This way we don't have cidrs full of confusing names (since we could later do something like filter by disabled, or even just grep -v, etc.)
I could see how some could say a DNS hostname suddenly changing private IP/public key could be an issue, however I'd argue that since the new public key/private IP tuple is valid on the wireguard network, and has a valid association you should be assuming it's safe anyways.

You could always modify the sqlite database to rename them and then have all peers run inn fetch as a temporary workaround.

As a matter of fact, PUT /v1/admin/peers/<id> does already support peer renaming (you can see all the allowed fields to edit on that endpoint at https://github.com/tonarino/innernet/blob/main/server/src/db/peer.rs#L133), so no server changes should be required to add that command to the client.
In the mean time you can either construct your own HTTP request to the server or edit the SQLite database on the server side directly. They should be roughly the same, with a slight preference for the HTTP API since it does validation of the hostname string that the SQLite checks won't do.

I don't mind putting in a PR for this if there is appetite to enable this feature through the CLI.

@kbknapp that would be great, I think it's a useful feature to have.


New release/ tag possible?

I was wondering if it is possible to create an updated release or a new tag?
The only tag available is 0.0.1 from the https://github.com/octodns/octodns-dnsimple/blob/main/octodns_dnsimple/init.py#L5C1-L5C22 string in the init.py
from back in 2021.
The project has seen a bit of development and some dependencies were updated so I think a new release would be nice for all users who don't use the commit hashes for the versioning.
Thanks :)

Hi @nerrehmit, looking over the changes since the v0.0.1 tag the only change that's not just formatting/linting or process/tooling related is the addition of a user-agent header, https://github.com/octodns/octodns-dnsimple/compare/v0.0.1...main#diff-9da4956bc34bd89944a48e498be6f04a612268d4b586fd88e11860565d5a5b2aR40.
Everything else is a noop as far as the functioning provider is concerned. For the most part the provider does all the things it needs.
The one thing that probably needs to be added is def list_zones so that the provider will support dynamic zone config, https://github.com/octodns/octodns/pull/1026.

Release cut https://github.com/octodns/octodns-dnsimple/pull/27


Create wiki for Team Web Warriors

Create a wiki page for your team in the wiki section on Github. It should include the team name, your team members' full names, roles, and Github ids.

How is it the case that this issue is still open?


test: add test experiments

Checks

[x] Manual check in Codesandbox.

:tada: This PR is included in version 4.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v4.3.0

Your semantic-release bot :package::rocket:


dev -> main-beta

:tada: This PR is included in version 2.0.0-beta.14 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Accordion  data-state="open" not working

Bug report
Current Behavior
The accordion isn't open when I set data-state="open" on the AccordionItem

Expected behavior
I expect it to be open
Reproducible example
[CodeSandbox Template](https://codesandbox.io/s/xenodochial-lamarr-z4zr6h?file=/src/App.tsx)
@radix-ui/react-accordion": "^1.1.2

To control the accordion you can use value and onValueChange props. Would be like this
const [value, setValue] = React.useState([]) // note that I'm using an array because you defined `type=multiple` otherwise it would just be a string

<Accordion.Root value={value} onValueChange={setValue}>
  { ... }
</Accordion.Root>

Ok thanks, might want to update the documentation as this is where I got this approach from?

It's already there :smile:  but I agree that it should be more direct. maybe with an example showing how to control the component


32 extractor source from develop

This change includes model changes requiring a grunt build.

Creating a pull request for a new branch with easier merge.


Scalariform

use scalariform for autoformat (with settings from akka)

Many thanks @jrieks for the pull request. Adding a formatter was overdue :smiley:.


Sort Filter by # of Pokemon Descending

Describe the issue
Currently, the dropdown is alphabetically sorted. The dropdown should be sorted. Perhaps there should also be the # of Pokemon indicated.
Acceptance Criteria

[ ] Sort dropdown by usage numbers
[ ] Display usage

Attempted to implement but ran into the following issues:

MUI select takes a string array when I'd like to pass in the # of elements as well
Without the aforementioned, the sorting makes no sense since we have no context about how it's sorted
Not worth investigating ATM


Failed to pull image at Helm install step

Prereqs all followed (i believe)
Images built and pushed to Docker Registry ok
Helm charts prepared, packaged and pushed ok.
Now run:
helm install release2 local-development/spm -f ../static/resources/crc-values.yaml
in separate tab:
kubectl get pods -w
NAME                                     READY   STATUS             RESTARTS   AGE
release1-apps-apply-customsql-mbl2f      0/1     ImagePullBackOff   0          18m
release2-apps-apply-customsql-fc8pb      0/1     ImagePullBackOff   0          53s
releasename-apps-apply-customsql-2bm8l   0/1     ImagePullBackOff   0          22m
release2-apps-apply-customsql-fc8pb      0/1     ErrImagePull       0          56s
(note releasename and release1 were also earlier fails)
Viewing log:
kubectl logs -f pod/release1-apps-apply-customsql-mbl2f
Error from server (BadRequest): container "apply-customsql" in pod "release1-apps-apply-customsql-mbl2f" is waiting to start: trying and failing to pull image
OS = MacOSx Catalina 10.15.7
ChartMuseum installed locally and run like this:
chartmuseum --debug --port=8080   --storage="local"   --storage-local-rootdir="./chartstorage"
CRC installed locally:
crc version
CodeReady Containers version: 1.15.0+e317bed
OpenShift version: 4.5.7 (embedded in binary)
Docker version 19.03.12

@heapey
Please check the image being pulled by any of the failing pods using the oc describe pod command.
If you are using CRC's internal image registry, there are several points to check:

Make sure that the target project exists before pushing the images

Verify the images were correctly published using curl -k -ukubeadmin:$(oc whoami -t) https://default-route-openshift-image-registry.apps-crc.testing/v2/_catalog and examine the output for your images

Push images using the "public" registry hostname (default-route-openshift-image-registry.apps-crc.testing), and set the "private" hostname (image-registry.openshift-image-registry.svc:5000) in the Helm override values file
Check that the details in the override values file correspond to the actual location where the images were published (i.e. global.images.registry and global.images.imageLibrary reflect the location where the images were pushed)

The sample file (crc-values.yaml) you are referencing expects the Docker images to have been published as default-route-openshift-image-registry.apps-crc.testing/ocp/<batch>:latest to a project named ocp

thanks for the pointer, i think there were two things:

I had to set imageLibrary: 'spm-deploy' in crc-values.yamp  (not ocp. Note spm-deploy was from earlier steps in the runbook (update runbook with more detail?)
this still failed, tracked it down to duplicate 'data:' element in mq-secret.yaml (is this a known issue?)

Tried new helm deployment (had to kill previous attempts by killing jobs that were resurrecting failed attempts)
But now get:
Failed to pull image "image-registry.openshift-image-registry.svc:5000/spm-deploy/batch:latest": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: unauthorized: authentication required
Obviously missed another step somewhere, will go back and look at this tomorrow but just wanted to give an update. Thanks for the pointer that got me further though

Thanks for the update.
I'll go over the text in the morning - the instructions assume that the namespace (project) where you push the images is the same as where you are deploying the application, though it is possible to separate this by allowing the Service Accounts in the deployment namespace to access the Registry namespace.
oc policy add-role-to-group \
    system:image-puller \
    system:serviceaccounts:<destination_project> \
    -n <source_project>

This allows <destination_project> to pull images from <source_project>.
I'll check what's going on with the duplicate key in the mq-secret.yaml file - that had been fixed back in August on our development branch, so it's strange that it isn't hasn't been picked up by our publish mechanism.

Thanks.
I believe my project where i'm pushing and deploying is the same, namely 'spm-deploy'.
I tried the above command but still get same error:
Failed to pull image "image-registry.openshift-image-registry.svc:5000/spm-deploy/batch:latest": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password: unauthorized: authentication required
Attaching my crc-values.yaml - you can see i have set my imagePullSecret with kubeadmin and password, is this correct?
Note I also tried the command suggested on https://ibm.github.io/spm-kubernetes/prereq/openshift/codeready-containers:
oc adm policy add-scc-to-user spm-dev-scc -z system:serviceaccount:${releasename}:default, but this fails:
The ClusterRoleBinding "system:openshift:scc:spm-dev-scc" is invalid: subjects[0].name: Invalid value: "system:serviceaccount:spm-deploy:default": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')
Looking at this more, is $releasename correct (set to spm-deploy earlier?) Later on in the helm install, running the install command will create a service account with the same name as the release given in the command:
e.g. helm install release11 local-development/spm -f ../static/resources/crc-values.yaml  then followed by:
kubectl get serviceaccounts
NAME                              SECRETS   AGE
builder                           2         41h
default                           2         41h
deployer                          2         41h
release11-apps-secret-manager     2         6m26s
Regardless, I tried running both the oc adm policy add-scc-to-user and the helm install using releasename ='spm-deploy', but got same errors.
What is spm-dev-scc in more detail? I looked in the source and see createSCC.sh, and now not sure if the build should take care of this step, or it is needed in the pre-reqs section as described in the link above.

This feels like potentially deep water so will hold fire for now, but please let me know if any other logs or info would help the diagnosis, or even if i should start again....
many thanks
crc-values.yaml.txt

The mq-secret.yaml error has been fixed in a new drop of the runbook we released today. See PR above.

Thanks for pointing out some stale docs - spm-dev-scc is actually no longer required, since all components in the latest version of the runbook are designed to run under the restricted policy.
While I rebuild my own CRC environment to deploy with your attached version of crc-values.yaml, try removing the global.imagePullSecret key - the token generated for the default Service Account should already have permissions to pull the images, so injecting kubeadmin credentials shouldn't be needed

Thanks! I think my original config was the default:
imagePullSecret:
registry: *imageRegistry
username: kubeadmin
password:
You are suggesting remove the whole thing?
Note I moved to try minikube as i couldn't get past the above error. Just got minkube up and running so will be spending a bit more time poking around there for a bit first and then go back to try the above suggestion on CRC if thats ok, so will let you know, thanks again

Hi @heapey
I checked locally that removing the imagePullSecret section from the CRC values file works correctly (something we'll fix in November's runbook release)

Actually, since my minikube docker images are stored in the minikube docker registry, and crc ones in the crc registry, given that the helm charts prepared as per https://ibm.github.io/spm-kubernetes/deployment/hc_preparation are platform agnostic, and the only thing that differentiates minikube vs crc is on the helm install step, specifying the override values yml, then in theory if i try the helm install on the CRC version again it should have no impact on the minikube version? Does that make sense, or anything else I need to consider?

Indeed, if you have pushed the images into both, then you can freely switch between Minikube and CRC. The only thing you have to change about your values file is the ingress hostname and the registry address - both use built-in credentials for pulling the images from the internal registry that don't need to be explicitly specified. In terms of the helm commands - the process is identical.

Hi,
Got to try this again and can confirm that completely removing the imagePullSecret now gets the process further and 3 out of 5 pods complete creating and up and running:
kubectl get pods
NAME                                           READY   STATUS    RESTARTS   AGE
crcrel1-apps-curam-consumer-78665dcdcc-ssh2l   0/1     Pending   0          14m
crcrel1-apps-curam-producer-5cbf6f78b-wwsl2       0/1     Pending   0          14m
crcrel1-mqserver-curam-775c99dd46-c9mxn           1/1     Running   0          14m
crcrel1-web-68bbdb447d-jlhrs                                    1/1     Running   0          14m
crcrel1-xmlserver-6ccb95b7df-mb5w5                       1/1     Running   0          14m
Unfortunately I'm out of CPU on my local laptop:
kubectl describe pods crcrel1-apps-curam-consumer-78665dcdcc-ssh2l
gives:
Events:
Type     Reason            Age                 From               Message

Warning  FailedScheduling  71s (x12 over 14m)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu, 1 Insufficient memory.
Happy to close this issue, as I know the CRC system requirements are a separate thing, but in case you need to update docs for clarity, in summary 2 things were needed in this issue :

remove the imagePullSecret from crc-values.yml
set  imageLibrary: 'spm-deploy' in crc-values.yaml (to match the value that is set in https://ibm.github.io/spm-kubernetes/prereq/openshift/codeready-containers)

Also on similar topic of updating docs, it would be good to distinguish between $releasename set in the prereqs, and the 'releasename' mentioned in https://ibm.github.io/spm-kubernetes/deployment/hc_deployment - since from what i can tell they can be independent, so slightly confusing to the first time user.
Many thanks for your help in getting me this far

Glad to hear you were unblocked on the original issue. Unfortunately between CRC's own requirements and the resource requirements for SPM, there is not a lot of room to reduce the system footprint to comfortably fit on a developer Macbook issued in the last ~2 years.
I'm going to keep this open until we push out the documentation updates.


UE edit Logging and diagnostics in gRPC on .NET

review

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

ID: a20ca5f3-1e63-e63f-07fa-99d523488893
Version Independent ID: e9e7c656-a610-7b17-4ca4-8342ecc7298e
Content: Logging and diagnostics in gRPC on .NET
Content Source: aspnetcore/grpc/diagnostics.md
Product: aspnet-core
Technology: aspnetcore-grpc
GitHub Login: @JamesNK
Microsoft Alias: jamesnk

Close due to low page count.


Java: add invokeScript to run lua scripts

Issue #, if available:
Description of changes:
Add the command invokeScript(Script) to the Java wrapper.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Transaction implementation is missing

@adanWattad would you be able to re-review please?


Feature request - support github deployment task as a constraint

I'd like to be able to only deploy specific things based on the task parameter from a Github deployment.

Task - Optional parameter to specify a task to execute, e.g. deploy or deploy:migrations. Default: deploy
https://developer.github.com/v3/repos/deployments/

An example of how that would look in .drone.yml configuration:
pipeline:
  deploy:
    when:
      event: deployment
      task: deploy
    image: some/image
    commands:
      - make deploy-web

  deploy-migrations:
    when:
      event: deployment
      task: deploy:migrations
    image: some/image
    commands:
      - make migrate

support for storing deployment parameters was added in https://github.com/drone/drone/commit/db7f0cdffba46c5ce9ac4959688d3ec8fc6e65b0. In order to conditionally execute steps based on these parameters, it should be added to our new Starlark scripting plugin. Starlark scripts can use any build attribute to dynamically build the configuration.
Here is the relevant repository and file that needs to be updated to support params:

https://github.com/drone/drone-convert-starlark
https://github.com/drone/drone-convert-starlark/blob/master/plugin/args.go

this is now possible in starlark configurations:
https://github.com/drone/drone-convert-starlark/commit/eba4f73f854dbdde8d78d20f07203a6fc9c7b202#diff-68cf9ea5a332e1f34f0148be48fda835R67
for example:
def main(ctx):
  pipeline = {
    "kind": "pipeline",
    "name": "default",
    "steps": []
  }

  if ctx.build.params["foo"] == "":
    # do something
  else:
    # do something else

  return pipeline

once we officially announce and document Starlark support this issue will be closed.  There are no plans to expand yaml conditionals at this time, and we will ask users to fallback to Starlark when they need something more complex not supported in yaml.

we officially announced support for starlark scripting:
https://blog.drone.io/create-pipelines-using-starlark/
with initial documentation:
https://docs.drone.io/starlark/overview/
as mentioned, we are pushing users toward starlark for advanced use cases that are not supported by the yaml.  hope this helps!


Guides - Set Up HMR with Redux

Redux specific HMR setup.

Isn't this covered by https://webpack.js.org/guides/hmr-react/?
Or is there more to be done?

Yeah. You can implement the interface for reducers like I have done here.

@bebraw I don't see anything in the article you linked to that cover HMR for redux. If you can point me to right places I might be able to tackle this either as a follow up or part of #1251. I'm actually somewhat interested in this anyway as I've used redux in multiple projects but changing reducers has always required a full browser refresh.

Hi, the info went to this article as I split it up. You have to scroll down a bit.


Dynamic ACLs

It is not a lot of use a client being able to search for e.g. Temperatures if that client doesn't have permission to read the data.
We need some way of automatically granting certain clients access to device matching certain criteria. To start with I think this wants to be implemented by the Directory automatically adding devices to (Auth service) groups, so clients can then be given access to appropriate groups.
This depends on #10. This could be implemented as a function of the Directory, or as a separate service. Either way the criteria for adding a device to a group needs to be configurable.

ABAC may provide an alternative to this.


ModuleNotFoundError: No module named 'degiro'

I installed your api using "python -m pip install degiro-api", and used the example as in the main logging. the python throws
Traceback (most recent call last):
  File "degiro_api.py", line 1, in <module>
    from degiro import DeGiro
ModuleNotFoundError: No module named 'degiro'

looks like the module name "degiro-api" and module being imported in the python 'degiro' is discrepant.
PS: i'm a perl scripter and there it works everything out of the box and python is quite new and bizzare and not so straight forward

Same problem here.
Installed the package. Pip list shows degiro-api 0.1
When I try to use it:
from degiro import DeGiro
ModuleNotFoundError: No module named 'degiro'
Thanks in advance for any clarification.

same here!


Adding schemaextension remove command resolving #16

Adding schemaextension remove command resolving #16

Coverage remained the same at 100.0% when pulling efa49d03ac556c84973355374a8a9794820aa8af on rabwill:issue-16 into f62e1ef8c7df7d30ab2e5898f036c4e999016f2b on pnp:dev.

hey @waldekmastykarz/ @VelinGeorgiev / @garrytrinder  happy to have you review and let me know any changes. It's been a while (almost 2 months) since last contribution so i feel like a first timer :D

Thanks @rabwill we will review shortly 👍🏻

Thank you Rabia @rabwill! Great work again! I did minor changes mentioned in the review, other than that the PR is ready to be merged from here: https://github.com/VelinGeorgiev/office365-cli/tree/schema-remove

Thanks so much @VelinGeorgiev ! 😊

Merged manually. Thank you @rabwill 👍


sorter/leveldb(ticdc): fix system stop blocks forever

What problem does this PR solve?
Issue Number: close #4699
Needs to merge #4819 first.
What is changed and how it works?
StopMessage maybe lost if the total broadcast time exceeds  1s.
If sorter system actors does not close in time, systeam.closedWg is blocked.
Check List
Tests

Unit test

Related changes

Need to cherry-pick to the release branch

Release note
Fix an issue that TiCDC can not exit.

/merge

/run-verify


⚠ Bofrost.si has degraded performance

In 44d8c4a, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 5542 ms

Resolved: Bofrost.si performance has improved in 4205551.


Cookbook exceding the timeout for chef-server deb download

Good afternoon,
Since yesterday, I'm facing a problem with the chef-server cookbook.
The cookbook runs well and when it reaches the download chef-server from repository stage, the node starts the download, and fails with a timeout error, as:
efault: * apt_package[chef-server] action install
==> default:
==> default:
==> default:
==> default: ================================================================================
==> default:       Error executing action install on resource 'apt_package[chef-server]'
==> default:
==> default: ================================================================================
==> default:
==> default:
==> default:
==> default:
==> default: Mixlib::ShellOut::CommandTimeout
==> default:
==> default: --------------------------------
==> default:       Command timed out after 900s:
==> default:       Command exceeded allowed execution time, process terminated
==> default:       ---- Begin output of apt-get -q -y install chef-server-core=12.2.0-1 ----
==> default:       STDOUT: Reading package lists...
==> default:       Building dependency tree...
==> default:       Reading state information...
==> default:       The following packages were automatically installed and are no longer required:
==> default:         chef-zero erubis ohai ruby-diff-lcs ruby-erubis ruby-hashie ruby-highline
==> default:         ruby-ipaddress ruby-mime-types ruby-mixlib-authentication ruby-mixlib-cli
==> default:         ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-net-ssh
==> default:         ruby-net-ssh-gateway ruby-net-ssh-multi ruby-rack ruby-rest-client
==> default:         ruby-sigar ruby-systemu ruby-yajl
==> default:       Use 'apt-get autoremove' to remove them.
==> default:       The following NEW packages will be installed:
==> default:         chef-server-core
==> default:       STDERR:
==> default:       ---- End output of apt-get -q -y install chef-server-core=12.2.0-1 ----
==> default:       Ran apt-get -q -y install chef-server-core=12.2.0-1 returned
==> default:
==> default:       Resource Declaration:
==> default:       ---------------------
==> default:       # In /var/chef/cache/cookbooks/chef-ingredient/libraries/helpers.rb
==> default:
==> default:        46:       declare_resource presource, new_resource.product_name do
==> default:        47:         package_name ingredient_package_name
==> default:        48:         options new_resource.options
==> default:        49:         version install_version if Mixlib::Versioning.parse(version_string(new_resource.version)) > '0.0.0'
==> default:        50:         source new_resource.package_source
==> default:        51:         timeout new_resource.timeout
==> default:        52:         action ingredient_action
==> default:        53:       end
==> default:        54:     end
==> default:
==> default:       Compiled Resource:
==> default:       ------------------
==> default:       # Declared in /var/chef/cache/cookbooks/chef-ingredient/libraries/helpers.rb:46:in package_resource' ==> default:        ==> default:       apt_package("chef-server") do ==> default:         action [:install] ==> default:         retries 0 ==> default:         retry_delay 2 ==> default:         default_guard_interpreter :default ==> default:         package_name "chef-server-core" ==> default:         version "12.2.0-1" ==> default:         declared_type :package ==> default:         cookbook_name "chef-server" ==> default:       end ==> default:        ==> default:  ==> default: [2015-09-10T16:16:00+00:00] INFO: Running queued delayed notifications before re-raising exception ==> default:      ==> default:      ==> default: ================================================================================ ==> default:     Error executing action installon resource 'chef_ingredient[chef-server]' ==> default:      ==> default: ================================================================================ ==> default:  ==> default:      ==> default:  ==> default:  ==> default:     Mixlib::ShellOut::CommandTimeout ==> default:     -------------------------------- ==> default:      ==> default: apt_package[chef-server] (/var/chef/cache/cookbooks/chef-ingredient/libraries/helpers.rb line 46) had an error: Mixlib::ShellOut::CommandTimeout: Command timed out after 900s: ==> default:  ==> default:     Command exceeded allowed execution time, process terminated ==> default:     ---- Begin output of apt-get -q -y install chef-server-core=12.2.0-1 ---- ==> default:     STDOUT: Reading package lists... ==> default:  ==> default:      ==> default: Building dependency tree... ==> default:  ==> default:     Reading state information... ==> default:      ==> default: The following packages were automatically installed and are no longer required: ==> default:      ==> default:   chef-zero erubis ohai ruby-diff-lcs ruby-erubis ruby-hashie ruby-highline ==> default:       ruby-ipaddress ruby-mime-types ruby-mixlib-authentication ruby-mixlib-cli ==> default:       ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-net-ssh ==> default:      ==> default:   ruby-net-ssh-gateway ruby-net-ssh-multi ruby-rack ruby-rest-client ==> default:       ruby-sigar ruby-systemu ruby-yajl ==> default:     Use 'apt-get autoremove' to remove them. ==> default:     The following NEW packages will be installed: ==> default:       chef-server-core ==> default:     STDERR:  ==> default:      ==> default: ---- End output of apt-get -q -y install chef-server-core=12.2.0-1 ---- ==> default:      ==> default: Ran apt-get -q -y install chef-server-core=12.2.0-1 returned  ==> default:      ==> default:  ==> default:      ==> default: Resource Declaration: ==> default:      ==> default: --------------------- ==> default:      ==> default: # In /var/chef/cache/cookbooks/chef-server/recipes/default.rb ==> default:      ==> default:      27: chef_ingredient 'chef-server' do ==> default:  ==> default:      ==> default:  28:   extend ChefServerCoobook::Helpers ==> default:      29:   version node['chef-server']['version'] ==> default:      ==> default:  30:   package_source node['chef-server']['package_source'] ==> default:      31:   config <<-EOS ==> default:      ==> default:  32: topology "#{node['chef-server']['topology']}" ==> default:      33: #{"api_fqdn \"#{node['chef-server']['api_fqdn']}\"" if api_fqdn_available?} ==> default:      34: #{node['chef-server']['configuration']} ==> default:      ==> default:  35: EOS ==> default:      36:   action :install ==> default:      ==> default:  37: end ==> default:      ==> default:  38:  ==> default:  ==> default:      ==> default:  ==> default:      ==> default: Compiled Resource: ==> default:      ==> default: ------------------ ==> default:     # Declared in /var/chef/cache/cookbooks/chef-server/recipes/default.rb:27:infrom_file'
==> default:
==> default:
==> default:
==> default: chef_ingredient("chef-server") do
==> default:
==> default:   action [:install]
==> default:
==> default:   updated true
==> default:
==> default:   updated_by_last_action true
==> default:
==> default:   retries 0
==> default:
==> default:   retry_delay 2
==> default:
==> default:   default_guard_interpreter :default
==> default:
==> default:   declared_type :chef_ingredient
==> default:
==> default:   cookbook_name "chef-server"
==> default:       recipe_name "default"
==> default:
==> default:   version :latest
==> default:
==> default:   config "topology "standalone"\napi_fqdn "vagrant-ubuntu-trusty-64"\n\n"
==> default:
==> default:   product_name "chef-server"
==> default:     end
==> default:
==> default:
==> default: [2015-09-10T16:16:00+00:00] INFO: Running queued delayed notifications before re-raising exception
==> default:
==> default: Running handlers:
==> default: [2015-09-10T16:16:00+00:00] ERROR: Running exception handlers
==> default: Running handlers complete
==> default:
==> default: [2015-09-10T16:16:00+00:00] ERROR: Exception handlers complete
==> default: Chef Client failed. 9 resources updated in<PHONE_NUMBER>12 seconds
==> default: [2015-09-10T16:16:00+00:00] INFO: Sending resource update report (run-id: 5d590a0a-7958-4824-9171-7774db100bb7)
==> default: [2015-09-10T16:16:01+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> default: [2015-09-10T16:16:01+00:00] ERROR: chef_ingredient[chef-server] (chef-server::default line 27) had an error: Mixlib::ShellOut::CommandTimeout: apt_package[chef-server] (/var/chef/cache/cookbooks/chef-ingredient/libraries/helpers.rb line 46) had an error: Mixlib::ShellOut::CommandTimeout: Command timed out after 900s:
==> default: Command exceeded allowed execution time, process terminated
==> default: ---- Begin output of apt-get -q -y install chef-server-core=12.2.0-1 ----
==> default: STDOUT: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following packages were automatically installed and are no longer required:
==> default:   chef-zero erubis ohai ruby-diff-lcs ruby-erubis ruby-hashie ruby-highline
==> default:   ruby-ipaddress ruby-mime-types ruby-mixlib-authentication ruby-mixlib-cli
==> default:   ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-net-ssh
==> default:   ruby-net-ssh-gateway ruby-net-ssh-multi ruby-rack ruby-rest-client
==> default:   ruby-sigar ruby-systemu ruby-yajl
==> default: Use 'apt-get autoremove' to remove them.
==> default: The following NEW packages will be installed:
==> default:   chef-server-core
==> default: STDERR:
==> default: ---- End output of apt-get -q -y install chef-server-core=12.2.0-1 ----
==> default: Ran apt-get -q -y install chef-server-core=12.2.0-1 returned
==> default: [2015-09-10T16:16:01+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.
Note: This errors appears either the AWS, or Vagrant machines.

Why is this issue closed? What is the solution to fix this?
I just encountered the same issue...

I closed since nobody has reported and from my side is ok. There is a way to re-open this ticket, then?

Reopened as requested by @turkenh

Hi, I have got the same error! The real problem seems to be that the gpg key for the repo is not imported.
==============================================================================
Error executing action `install` on resource 'chef_ingredient[chef-server]'
==============================================================================

Mixlib::ShellOut::CommandTimeout
    --------------------------------
apt_package[chef-server] (/var/chef/cookbooks/chef-ingredient/libraries/debian_handler.rb line 71) had an error: Mixlib::ShellOut::CommandTimeout: Command timed out after 900s:
Command exceeded allowed execution time, process terminated
---- Begin output of apt-get -q -y install chef-server-core=12.4.1-1 ----
STDOUT: Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
 chef-zero erubis ohai ruby-diff-lcs ruby-erubis ruby-hashie ruby-highline
 ruby-ipaddress ruby-mime-types ruby-mixlib-authentication ruby-mixlib-cli
 ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-net-ssh
 ruby-net-ssh-gateway ruby-net-ssh-multi ruby-rack ruby-rest-client
 ruby-sigar ruby-systemu ruby-yajl
Use 'apt-get autoremove' to remove them.
 The following NEW packages will be installed:
  chef-server-core
  STDERR:
---- End output of apt-get -q -y install chef-server-core=12.4.1-1 ----
Ran apt-get -q -y install chef-server-core=12.4.1-1 returned

When we execute the failing apt command we get a little hint:
root@chef:/vagrant# apt-get -q -y install chef-server-core=12.4.1-1
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  chef-zero erubis ohai ruby-diff-lcs ruby-erubis ruby-hashie ruby-highline
  ruby-ipaddress ruby-mime-types ruby-mixlib-authentication ruby-mixlib-cli
  ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-net-ssh
  ruby-net-ssh-gateway ruby-net-ssh-multi ruby-rack ruby-rest-client
  ruby-sigar ruby-systemu ruby-yajl
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  chef-server-core
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 463 MB of archives.
After this operation, 1,225 MB of additional disk space will be used.
Fetched 463 MB in 7min 32s (1,025 kB/s)
E: Failed to fetch https://packagecloud.io/chef/stable/ubuntu/pool/trusty/main/c/chef-server-core/chef-server-core_12.4.1-1_amd64.deb  Hash Sum mismatch

The last two words! hashsum mismatch! OK, the real error can be seen after an apt-get update:
W: GPG error: https://packagecloud.io trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 37BBEE3F7AD95B3F

So there is no valid gpg key for the package cloud repo. This key should be imported, then it must work.

I am not sure atm how this counts in, but tis recipe also installed a wrong package repository - in /etc/apt/sources.list.d/ I see:
deb     [trusted=yes] https://packagecloud.io/chef/stable/ubuntu/ lucid main

but this is a trusty server.

I've added a key curl https://packagecloud.io/gpg.key | sudo /usr/bin/apt-key add - now apt-get update isn't complaining about the lack of a key, but I still get Failed to fetch https://packagecloud.io/chef/stable/ubuntu/pool/trusty/main/c/chef-server-core/chef-server-core_12.4.1-1_amd64.deb  Hash Sum mismatch
and just to re the above comment, this is trusty and i see: cat /etc/apt/sources.list.d/chef-stable.list  deb     [trusted=yes] "https://packagecloud.io/chef/stable/ubuntu/" trusty main

@tomharvey I am not able to reproduce this in kitchen just yet -- is aside from setting node['chef-server']['version'] = 12.4.1 is there anything else you are pinning by any chance? Any additional information would be appreciated.

I'm getting the same results as @devopstiger when I run the install command manually.
See https://github.com/cat5inthecradle/chef-server-vagrant/tree/4e4df3251108aadf76731f01eebb67860db9c2d9 for my full dev environment.
sudo apt-get -q -y install chef-server-core=12.4.1-1 returns
`Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
chef-zero erubis ohai ruby-diff-lcs ruby-erubis ruby-hashie ruby-highline
ruby-ipaddress ruby-mime-types ruby-mixlib-authentication ruby-mixlib-cli
ruby-mixlib-config ruby-mixlib-log ruby-mixlib-shellout ruby-net-ssh
ruby-net-ssh-gateway ruby-net-ssh-multi ruby-rack ruby-rest-client
ruby-sigar ruby-systemu ruby-yajl
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
chef-server-core
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 463 MB of archives.
After this operation, 1,225 MB of additional disk space will be used.
Fetched 463 MB in 3min 5s (2,493 kB/s)
E: Failed to fetch https://packagecloud.io/chef/stable/ubuntu/pool/trusty/main/c/chef-server-core/chef-server-core_12.4.1-1_amd64.deb  Hash Sum mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?`
When I run sudo apt-get update --fix-missing I get the following as the last line of output:
W: GPG error: https://packagecloud.io trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 37BBEE3F7AD95B3F

This was fixed for ubuntu 10.04 and debian 6 based things in chef-ingredient 0.17.0, I'm guessing this will be resolved by doing a berks update chef-ingredient

The chef-ingredient dependency for this chef-server cookbook is 0.11.0, berks update doesn't change it - so I added 0.17.0 as a dependency for my project. Currently running now but looks like it's going to timeout again.

The depends is a >= depends so a berks update will bring in the latest cookbook unless you're constrained elsewhere in the node runlist.  I'm going to close this out though since we fixed the issue in chef-ingredient.