Research and refactor component to leverage this.attrs

This issue involves more than just simply replacing syntax, but instead requires understanding what this new capability offers and determine what parts of the component implementation should/needs to be modified to align.
this.attr resources:

http://emberjs.com/blog/2015/05/10/run-up-to-two-oh.html#toc_new-lifecycle-hooks
http://emberjs.com/blog/2015/05/10/run-up-to-two-oh.html#toc_the-code-attrs-code-property
http://emberjs.com/blog/2015/05/24/another-two-oh-status-update.html#toc_new-lifecycle-hooks
https://github.com/emberjs/ember.js/pull/11127
“Separated Component Parameters” section of https://github.com/emberjs/rfcs/pull/15
“Improving Actions” section of https://github.com/emberjs/rfcs/pull/15
Also pay mind to the info in the “Transition Plan” of this section
https://github.com/emberjs/rfcs/pull/15#issuecomment-61534266
https://github.com/emberjs/rfcs/pull/15#issuecomment-61545249
https://github.com/emberjs/ember.js/blob/0ff1f46ebda74da54d48f6e094a96bdcb8728a79/packages/ember-htmlbars/tests/integration/component_lifecycle_test.js#L81

I'll work on this.

Per the conversation captured in the attached screen shots, work regarding this.attrs is being postponed until further solidification of the feature set.

Additional conversation - https://github.com/emberjs/ember.js/pull/12501

http://locks.svbtle.com/to-attrs-or-not-to-attrs


Environments to set activated extensions and settings

Many developers do not only touch one language during their life so VS Code extensions and settings can get a real mess after some time, especially if you have two or more languages you deeply care about to have ideal environments and developer experience.
I would like to present an idea about environments that hold extensions and settings for specific languages (identifiers).
The performance increase is not huge (see tests) in my example TypeScript project but it can be higher in other projects, it totally depends on activated global extensions.
Tell me what you think about it! :)

Repo with benchmarks: https://github.com/muuvmuuv/vscode-environments

What would environments do and what are they?
You would install all extension you need globally like you do currently but then choose which are not ideally to use in a global scope or new workspace/project. For example Rust extensions when you are a frontend developer who mainly codes in JavaScript. Most extension wont activate in certain workspaces but still be loaded on startup.
After that you create a new environment (via command "Add new environment") and add VS Code settings and extension that you would like to activate explicitly for it.
VS Code will test each on startup and cache environment changes and their workspace. If either changes it will test again. This should speed up recuring start up times so it does not need to do identification tests again everytime. (wip)
The auto-detection can be disabled, so you choose an environment manually via "Select environment".
Editing environments can be done through the standard VS Code settings panel or manually in a JSON format.
Bonus: An option to async load an environment to apply settings/extensions. to speed up start up times. If it has extensions that require a reload it will reload after it has cached the environment or display a hint with a reload now button.
The format for environments would be as follow:
Environments
[
  {
    // For the cache to create
    "name": "python",
    // For the extension panel or manual selection
    "label": "Python",
    // Identifiers auto activate this environment for you.
    // For performance reasons it will not search anything recursively
    // but you can choose if you want that. This is optional!
    "identify": {
      // If a .py file was found
      "extensions": [".py"],
      // If a file with language python was found
      "languages": ["python"],
      // If a file `.python-version` etc. was found (regex allowed)
      "files": [".python-version", "requirements.txt"],
      // If e.g. extensions should be search recursively (default: false)
      "recursively": false
    },
    // Settings only for this environment
    "settings": {
      // This allows us to no longer need to do `"[python]": { }`
      "editor.defaultFormatter": "ms-python.vscode-pylance",
      // All settings are allowed
      "python.languageServer": "Pylance",
      "python.linting.enabled": true,
      "python.linting.pylintEnabled": true,
      "python.showStartPage": false,
      "python.venvPath": "~/.pyenv"
    },
    // Extensions that should be enabled
    "extensions": [
      "vscode.python", // builtin's are supported as well
      "visualstudioexptteam.vscodeintellicode",
      "ms-python.python",
      "ms-python.vscode-pylance",
      "ms-toolsai.jupyter"
    ]
  }
]

In my case it would reduce my extensions from 156 to 92 with builtin extensions in an TypeScript project, see below.

Benchmarks
System Info

Code - Insiders: 1.53.0-insider (c265dff48a27868c7f0f84fd25a169897dc43d73)
OS: darwin(19.6.0)
CPUs: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz(8 x 2800)
Memory(System): 16.00 GB(0.26GB free)
Memory(Process): NaN MB working set(100.37MB private, 0.10MB shared)
VM(likelyhood): 0%
Initial Startup: false
Has 0 other windows
Screen Reader Active: false
Empty Workspace: true

Tests
Tests can vary. I tested through a example VS Code extensions launcher.

Opened test extension workspace
Adjusted extensions and settings
Run launcher in TypeScript or empty workspace a few times
Collected "Startup Performance" report
Collected installed extensions through test extension

Setup
Startup time (ms)
Extensions load (ms)
Extensions count
Description

Vanilla
3312
445
default
No changes.

Minimal
2543
372
42
Deactivated all extensions not related to web + go,rust,python

Recommended Markdown
5772
4743
86
Added some personal recommended extensions and settings

Recommended TypeScript
6579
5423
126
above plus TypeScript/Angular stuff

All TypeScript
6339
28188
156
All extensions activated + my extensions

Only TypeScript
6120
13617
92
What I would use only for TypeScript + Angular

/duplicate
Assuming this us a feature request to support lang environments inside VS Code. And there is already a request for this. Hence marking this as duplicate.

/duplicate
Assuming this us a feature request to support lang environments inside VS Code. And there is already a request for this. Hence marking this as duplicate.

Where I couldn't find it?

Where I couldn't find it?


[sap.ui.richtexteditor.RichTextEditor] a11y, announcement is not proper enough upon expanding the menu.

OpenUI5 version: 1.125.1
Browser/version (+device/version): Edge (123.0.2420.81 (Official build) (64-bit))
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible): https://sapui5.hana.ondemand.com/#/entity/sap.ui.richtexteditor.RichTextEditor/sample/sap.ui.richtexteditor.sample.RichTextEditor
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

use NVDA as the SR(2024.1).
narrow the browser width to 600px so that some of the actions will be grouped in the overflow button
navigate to the overflow button using the tab key and click the button using the enter key
open the font dialog
the announcement will be like "Available Values dialog, list, 10pt 2 of 7"

What is the expected result?
It's an incident from the customers, they expect "expanded state along with focused element info" to be announced. We should emphasize that the popup is expanded and the item e.g.,  10pt is selected.
What happens instead?
Currently, the announcement is like "Available Values dialog, list, 10pt 2 of 7".

Any other information? (attach screenshot if possible)
I'm from SAP SF and it's an incident from the customer.

Hello @AlexYanSap,
The sap.ui.richtexteditor.RichTextEditor is part of SAPUI5 not of OPENUI5. GitHub is a place for managing issues for OPENUI5 only.
Please, open a ticket in SAP ticket system for managing incidents.
Kind regards,
Nikoleta Terzieva


Can it be used headless?

I'm trying to automate peer add/delete. Can I use this without the interface in a non blocking way? Just run one command and output the new peer config instead of it waiting for the next input.
wg-cmd wg0 delete <peerpublickey>
wg-cmd wg0 add

Not at the moment. It should not be difficult to add this however. Package https://github.com/AndrianBdn/wg-cmd/tree/main/backend has most of the functions implemented.
Are you sure you need wg-cmd at all? You can add peers with command line using wg/wg-quick that bundled with WireGuard. See https://gist.github.com/chrisswanda/88ade75fc463dcf964c6411d1e9b20f4


Fix switch_mode_and_capture_image method

Fixes #557
Its looks like return was unintentionally omitted in PR 436

Hi, thanks very much for spotting this. We normally have a preferred style of commit message (see here) that we ask people to use, just to be clear that contributions are being given to Raspberry Pi. I don't think there's too much to worry about here, but it would be good just to have your official "sign-off" to acknowledge that. Then I'd be very happy to merge this patch.
Thanks again!

Commit updated

Thanks!


Scala Native 0.5.0 support

Hi 🖖🏻
This PR brings support for Scala Native, similarly to existing JS support.
I hope it won't be troublesome to maintain since the library has no dependencies and is using pure Scala.

Amazing! Thanks, @susliko!

Ah, could you run sbt githubWorkflowGenerate?

Yep, done


ensure MultipleChooserPanel selecting unique objects

Fixes #10496
one solution for this issue is disable the duplicate objects or checkboxes, as shown below:

another solution instead of disable the already selected objects, just not add the duplicate objects , when the user add
duplicate object , this object not added to the selection objects. I can update the PR , if this solution is better.

Another thing - as per https://github.com/wagtail/wagtail/issues/10496#issuecomment-1570233449, we only want to enable this behaviour when we're sure that choosing duplicates should not be allowed. Ideally, it would do this by looking for a unique constraint on the model - but as a first pass, an allow_duplicates flag on MultipleChooserPanel (defaulting to True) would do the job.

depend on the suggestions, I did :

move the "getChoiceSelectIds " method to "MultipleChooserPanel".
set another unique attribute to the hidden input to make it unique.
add "allow_duplicates" flag to "MultipleChooserPanel".

some fails because I added attribute to hidden input, I will work on this fails with unit tests. if I miss something regarding suggestions or this PR need any modification, please let me know.

Great, I will update this PR soon.

yes make the code or the  components independent is better .I updated the PR, so please let me know, if it work
as expected or not.

Thanks for the Feedback, I will start wok on it ASAP.

done, but now I write unit test for the server side, but I don't know what must be done for a unit test for the client, since I removed the disableCheckboxes logic to server side, I don't know if I must write unit tests for this function "getChoiceSelectIds"  or not,  so please let me know what must done for unit test for the client. and if miss something regarding unit test or this PR in general , or if it need any modification, please let me know.

This is great, thanks @elhussienalmasri! Hope this makes into a release soon


Detailed View - (Bug) In change log, URL is being flagged as changed for other changes (possibly all)

Log into Marketplace as Admin
Pick a listing and open detailed view
Open in Create / Edit or admin tab
Change anything about the listing a legacy adaptor listing (?)
Open Detailed View, Admin Tab
View details of the change that was made
See interesting URL information

Changes made for this image were (in chronological order)

Flagging as featured
Changing version number to 1.23

(Also, after I did the second change, I opened the Featured flag change again and instead of being below the launch URL change like the version number change details, it's now above the URL change - as seen in the screenshot.)

Looking at the screenshot this is accurate in the fact that the launch url is changing.  It appears that each time the listing is saved the % value gets encoded again for example if you have a % in the url it encodes with %25 and when you edit and save the listing it saves as %2525.

I had fixed this in #222, not sure how it was undone. I'll have a look at it though; I was able to replicate it.

Confirmed working on ci-master with Chrome, FF24 and IE9.

Passed – Tested in STG
Verified fixed by modifying fields in listings and adding spaces to the URL.  In the preview, the URL displays %20 and the changes to fields are displayed correctly.


Button alignment issue on whats on this weekend or today.

What

Small cosmetic issue with button alignment issue on whats-on page where the spacing and button are close together.
Viewed on :
Chrome - browser
Iphone - chrome
Android - chrome
Where

https://wellcomecollection.org/whats-on/today
https://wellcomecollection.org/whats-on/this-weekend

The MoreLink component didn't used to have this button styling until recently (it didn't have a border) so it didn't require any extra vertical space. I think converting this div to a <Space /> styled-component to add a small amount of vertical space should deal with it.

Closing as stale – we now separate out exhibitions and events on the What's On page, so the two buttons are always far apart.


Install and configure pam_auth

Any chance of getting this merged?

@Sauraus yes, this will be merged, but it doesn't actually work correctly at the moment. I have started adding an integration test and fixing the missing bits, but I've also been sick for a little bit and haven't had as much time as I would like to get it wrapped up. Support is in progress and will be merged, but I don't have a hard date at the moment, sorry.

@phlipper thanks for the update and get well. :)

Any update on the merge?

Buehler? :(

@Sauraus I'm sorry for the delay. I still have not had a chance to get this branch fully working yet. I would be happy to merge this if you are able to update this with working integration tests. If I am able to get a chance to get things working, I will merge it in then as well. This isn't a feature I use so other issues have taken priority.


Build log always shows source directory even when using out of source builds

Brief Issue Summary
When build the project using out of source build directory (vscode-build ), log still shows source directory (10.11 below)
[main] Building folder: 10.11
[build] Starting build
[proc] Executing command: /usr/local/bin/cmake --build /home/anel/GitHub/mariadb/server/build/vscode-build --config Debug --target all --

CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
From file cmakeProject.js can be seen that only current folderName is used (source directory). It should be binaryDir IMHO.
Suggested fix should be
log.info(localize('run.build', 'Building folder: {0}', this.binaryDir ? this.binaryDir : this.folderName ), (targets && targets.length > 0) ? targets.join(', ') : '');

Thanks for the heads up! I'll mark this as a bug and tag it. We welcome OSS contribution and would greatly appreciate you contributing this fix!

Closed, fixed in #3778

@gcampbell-msft  I forgot about this to contribute, glad to see it is fixed.
Thanks


DOM Api fails to select an element in a dom-repeat in polymer 1.1

Doing something like:
Polymer.dom(this.root).querySelectorAll('some-element')

worked pretty well in polymer 1.0. Both elements in in the local dom as well as results from dom-repeat templates are selected. With polymer 1.1, the elements produced with dom-repeat are not selectable anymore.

I'm not able to confirm this issue. Here's a jsbin that confirms it's working (press the Test button and see the console output):
http://jsbin.com/hizevocota/edit?html,console,output
Would you mind providing more info about when you're calling this method?

I'm calling this method from an on-tap handler, though the later doesn't really matter. Calling Polymer.dom(ELEMENT.root).querySelectorAll('*') doesn't contain the expected elements.
The elements which never appear in these queries are all from within a dom-repeat template, located here:
https://github.com/urandom/readeef/blob/7f13bc0769d5477e26ceaabfaa0b46f9620ace31/templates/components/rf-feed-base.tmpl#L106
When I try to fetch a particular element from within, the result is always undefined:
https://github.com/urandom/readeef/blob/7f13bc0769d5477e26ceaabfaa0b46f9620ace31/templates/components/rf-feed-base.tmpl#L259
The component which holds all of that html as its content is here:
https://github.com/urandom/readeef/blob/7f13bc0769d5477e26ceaabfaa0b46f9620ace31/templates/components/rf-app-scaffold.tmpl

Hello, i have the same problem. A working demo with the bug can be found here:
http://jsbin.com/razotukane/1/edit?html,console,output
When you open the drawer and click on an item the console output should be 4 (the number of items). Instead it is 0. The function that can't find the elements is called from a tap event on one of the items that get rendered by the dom-repeat.
If you go to the head element and change the polymer.html to the 1.0.9 version, everything works as it should. It also works if you change from shady to shadow dom.

confirmed.
The mouseover highlighting stopped working in:
http://github.com/m4b/silicon-hex-table
when polymer was updated to 1.1.
Further investigation confirmed, as mentioned above, that Polymer.dom(this.root).querySelectorAll('.hex') was no longer returning the array of nodes with class hex at line 363.  (it doesn't have to do with the this.async call either, as I've tested trying to get the hex nodes in an on-tap handler as well).
Pinning polymer to 1.0.9 returns the highlighting behavior as expected, and the nodes returned by querySelectorAll are as expected.
Note: the element generated was fairly complicated, perhaps this had something to do with it?
<template is="dom-repeat" items="[[_table]]" as="row">

            [[_getOffset(offset, index)]]

            <template is="dom-repeat" items="[[_get(row)]]" as="col">[[_getHex(_bytes, offset, col)]]</template>

            <template is="dom-repeat" items="[[_get(row)]]" as="col">[[_getAscii(_bytes, offset, col)]]</template>

 </template>

Ok, can confirm this problem now and it's definitely a regression. We're working on fixing it asap.

Still experience this problem with Polymer 1.6.1

It works fine in Chrome, but this is still an issue for Safari 10.

Problem still persists with Polymer 1.7.


Talent icons not displayed

The talent icons are not displayed in the app when installed from the HeroesMatchTrackerSetup.exe. I am running Heroes Match Tracker 2.5.0 on Windows 7 64bit.

I noticed that the images that aren't appearing are the .dds images.  After some research it seems to be something with Windows 7, Windows Imaging Component (WIC), and possibly not supporting WDDM 1.2.
So I guess I'll have to convert the all .dds images now.

This should be fixed now


Error installing

Hello.
Unable to install plugin. Fails with error:
rake redmine:plugins RAILS_ENV=production --trace
** Invoke redmine:plugins (first_time)
** Execute redmine:plugins
** Invoke redmine:plugins:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
NameError: uninitialized constant ActiveSupport::Reloader
/usr/share/redmine/plugins/redmine_omniauth_cas/init.rb:8:in <top (required)>' /usr/share/redmine/lib/redmine/plugin.rb:155:in block in load'
/usr/share/redmine/lib/redmine/plugin.rb:146:in each' /usr/share/redmine/lib/redmine/plugin.rb:146:in load'
/usr/share/redmine/config/initializers/30-redmine.rb:21:in <top (required)>' /usr/lib/ruby/vendor_ruby/rails/engine.rb:652:in block in load_config_initializer'
/usr/lib/ruby/vendor_ruby/active_support/notifications.rb:166:in instrument' /usr/lib/ruby/vendor_ruby/rails/engine.rb:651:in load_config_initializer'
/usr/lib/ruby/vendor_ruby/rails/engine.rb:616:in block (2 levels) in <class:Engine>' /usr/lib/ruby/vendor_ruby/rails/engine.rb:615:in each'
/usr/lib/ruby/vendor_ruby/rails/engine.rb:615:in block in <class:Engine>' /usr/lib/ruby/vendor_ruby/rails/initializable.rb:30:in instance_exec'
/usr/lib/ruby/vendor_ruby/rails/initializable.rb:30:in run' /usr/lib/ruby/vendor_ruby/rails/initializable.rb:55:in block in run_initializers'
/usr/lib/ruby/2.5.0/tsort.rb:228:in block in tsort_each' /usr/lib/ruby/2.5.0/tsort.rb:350:in block (2 levels) in each_strongly_connected_component'
/usr/lib/ruby/2.5.0/tsort.rb:422:in block (2 levels) in each_strongly_connected_component_from' /usr/lib/ruby/2.5.0/tsort.rb:431:in each_strongly_connected_component_from'
/usr/lib/ruby/2.5.0/tsort.rb:421:in block in each_strongly_connected_component_from' /usr/lib/ruby/vendor_ruby/rails/initializable.rb:44:in each'
/usr/lib/ruby/vendor_ruby/rails/initializable.rb:44:in tsort_each_child' /usr/lib/ruby/2.5.0/tsort.rb:415:in call'
/usr/lib/ruby/2.5.0/tsort.rb:415:in each_strongly_connected_component_from' /usr/lib/ruby/2.5.0/tsort.rb:349:in block in each_strongly_connected_component'
/usr/lib/ruby/2.5.0/tsort.rb:347:in each' /usr/lib/ruby/2.5.0/tsort.rb:347:in call'
/usr/lib/ruby/2.5.0/tsort.rb:347:in each_strongly_connected_component' /usr/lib/ruby/2.5.0/tsort.rb:226:in tsort_each'
/usr/lib/ruby/2.5.0/tsort.rb:205:in tsort_each' /usr/lib/ruby/vendor_ruby/rails/initializable.rb:54:in run_initializers'
/usr/lib/ruby/vendor_ruby/rails/application.rb:352:in initialize!' /usr/share/redmine/config/environment.rb:14:in <top (required)>'
/usr/lib/ruby/vendor_ruby/rails/application.rb:328:in require' /usr/lib/ruby/vendor_ruby/rails/application.rb:328:in require_environment!'
/usr/lib/ruby/vendor_ruby/rails/application.rb:457:in block in run_tasks_blocks' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in block in execute'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in each' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in execute'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:214:in block in invoke_with_call_chain' /usr/lib/ruby/2.5.0/monitor.rb:226:in mon_synchronize'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:194:in invoke_with_call_chain' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:238:in block in invoke_prerequisites'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:236:in each' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:236:in invoke_prerequisites'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:213:in block in invoke_with_call_chain' /usr/lib/ruby/2.5.0/monitor.rb:226:in mon_synchronize'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:194:in invoke_with_call_chain' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:183:in invoke'
/usr/share/redmine/lib/tasks/redmine.rake:57:in block (2 levels) in <top (required)>' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in block in execute'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in each' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:273:in execute'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:214:in block in invoke_with_call_chain' /usr/lib/ruby/2.5.0/monitor.rb:226:in mon_synchronize'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:194:in invoke_with_call_chain' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/task.rb:183:in invoke'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:160:in invoke_task' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:116:in block (2 levels) in top_level'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:116:in each' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:116:in block in top_level'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:125:in run_with_threads' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:110:in top_level'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:83:in block in run' /var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:186:in standard_exception_handling'
/var/lib/gems/2.5.0/gems/rake-12.3.2/lib/rake/application.rb:80:in run' /var/lib/gems/2.5.0/gems/rake-12.3.2/exe/rake:27:in <top (required)>'
/usr/local/bin/rake:23:in load' /usr/local/bin/rake:23:in <top (required)>'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:74:in load' /var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:74:in kernel_load'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:28:in run' /var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/cli.rb:463:in exec'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run' /var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in invoke_command'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor.rb:387:in dispatch' /var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/cli.rb:27:in dispatch'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/base.rb:466:in start' /var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/cli.rb:18:in start'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/exe/bundle:30:in block in <top (required)>' /var/lib/gems/2.5.0/gems/bundler-1.17.3/lib/bundler/friendly_errors.rb:124:in with_friendly_errors'
/var/lib/gems/2.5.0/gems/bundler-1.17.3/exe/bundle:22:in <top (required)>' /usr/local/bin/bundle:23:in load'
/usr/local/bin/bundle:23:in `'

Same error here on Redmine 3.4.11.stable, any luck installing?

With Redmine 3, you should use an older version, not the master branch of the plugin.
You can use this tag: https://github.com/jbbarth/redmine_omniauth_cas/tree/v3.4.6


Restructure navigation for 6th release and feature use cases 1-3 prominently

Initial design to do's

[x] Adding use cases call to action link on the 6th release notes card.
[x] Create 3 documents for Use Case 1-3, send to Katy, Andi, Bruce
[x] Add documents to HRA Content Tracker
[x] Navigation dropdown for use cases replacing CCF Ontology.
[x] Remove CCF ontology from main navigation and move to Data
[x] Create a use case overview page.
[x] Obtain content from Katy, Bruce, and Andi. Titles, subtitles, and page content are needed to fulfill the milestone.
[x] Pass 4 new pages for the HRA Portal to development (User Stories Overview, US1-3). Note that the video content will come later.

Resources:

Google Doc: CNS UX Specs - 10/4
Figma design file: 6th Release
HRA Content Tracker
Google Drive folder: Use Case 6th

Restructure navigation for 6th release and feature use cases 1-3 prominently
Navigation has been modified and four pages have been added to the HRA Portal. The CCF Ontology page has been categorized as a Data item, moving it into the Data menu and Data Overview page.
Notes for the development team:

Figma acts as the source of truth for the content within this issue.
Links go to the respective Figma design file nodes below.
Currently, on the new User Stories pages, placeholder boxes remain for what will eventually be embedded YouTube videos. Please note that we will embed a YouTube video on each of these pages before the 6th Release on December 15th.

Implementation To Do's:

[ ] Navigation bar: Move CCF Ontology to the Data menu in the navigation bar.
[ ] Data Overview: Add CCF Ontology card button to the Data Overview page.
[ ] Navigation bar: Add a new dropdown option titled "Use the HRA" in place of the former CCF Ontology listing.
[ ] Navigation bar: Add a dropdown menu linking to the Overview page and to each user story page.
[ ] Overview: Use the HRA page: Implement the new Use the HRA Overview page.
[ ] User Story 1 page: Implement the new page Improve Cell Type Annotations.
[ ] User Story 2 page: Implement the new page Predict 3D Spatial Origin of Tissue Samples
[ ] User Story 3 page: Implement the new page Explore Biomarker Expressions for Cell Types

@libby-maier  I have implemented these changes. You can review them here
https://humanatlas-io.netlify.app/

Hi @bhushankhope, it's looking great.
The only issue I see right now is that this image for US3 needs to expand out to the whole page. Is it possible to get this closer to the specification? The image should expand to its full size responsively. Also, this image will be changing, so I'll submit an issue as soon as it needs to be updated.
Use the file below, located in the UI Annotations Figma File.

n?

Adding Katy's example of the responsive 4K visual functionality we want to achieve with the annotation graphic

https://opencell.czbiohub.org/help

Bhushan and I have been working together on this issue for user story 3. See the Figma design file for the updated mockup.
New UI:

New Annotation Image

@bhushankhope & @bherr2 -
The navigation and pages all look great but we do need to update the videos and the headers for them.

Please remove the video demonstration section if we don't have time to make these demo videos happen before December 15th. Thanks so much for all of your hard work, team!

@libby-maier @bhushankhope
It was brought to my attention that we need video demos. I assume one for US1 and one for US2? Will YT video IDs links work?

Yep!

HRA US1: https://youtu.be/KuZ_bwLHipM
HRA US2: https://youtu.be/AlcTRCMU2ME

Thanks! Updated and added to staging.

Hi @bherr2,
@andreasbueckle and I made some significant updates to the EUI annotation visual for US#3 today.
Would it be possible to replace the current annotation with the updated image below?

You betcha, just added to develop https://github.com/cns-iu/humanatlas.io/commit/d292866b8a3af70c4237961b8e0e89f8d00819d9

Thank you so much @bherr2! It appears squished from a random Google Chrome browser window size on my big home monitor. It looks fine when my browser is set to full screen. Is it possible to prevent it from looking squished?

I'll have daniel or ed look at it

Excellent, thank you so much!

Image squishing fixed by #377

Thank you so much team!


Update record BBEs

Purpose

$subject

Codecov Report

Merging #20345 into release-stage will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release-stage   #20345   +/-   ##
==============================================
  Coverage          15.21%   15.21%
==============================================
  Files                 50       50
  Lines               1341     1341
  Branches             208      208
==============================================
  Hits                 204      204
  Misses              1121     1121
  Partials              16       16

Continue to review full report at Codecov.

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


.meta files

Hi, I know that .meta files contain references and other stuff so I wanted to ask if there is a specific need for them in this project? I usually ignore them as they get recreated on import.

No specific need I just didn't think of them that much. I removed and ignored them.


Mercado Pago for Latin America  [Feature Request]

It would be possible to add Mercado Pago as an alternative for Latin America, as it is the best option for accepting several payment methods internally.
https://www.mercadopago.com.br/developers/en

It would be really good.

If there is any documentation or guide on the development of payment gateways, I myself have already made a plugin to integrate Mercado Pago with API's for Wordpress. Following some example for FOSS I could program an extension...

Hello my friends,
Any news about the Mercado Pago gateway?
Thanks
Heber

Closing to make one larger issue to track the payment gateways that have been requested


Re-emit ignored events from grabbed devices to uinput devices

Ignored events (i.e. events other than key presses for now) are re-emitted to the uinput devices. This allows grabbing mouses and other pointer devices while still allowing the cursors to work.
In some cases, events are not re-emitted at all when the uinput device handles keys, relative axes and switches. By sending switch events to a separate uinput device just for switches and another one for keys and relative axes, we can re-emit keys, pointer events, and switches events properly.

Closes https://github.com/waycrate/swhkd/issues/131

Great! Should I merge this into main directly or into the mouse-fix branch first?
Do you want other team members to test this further?

Great! Do you want other team members to test this further?

Would be nice if eden took a look too. I think eden is a little busy with university so if they don't respond, we shall go ahead with the merge.

Hi @ajanon, really sorry to bother you but would you mind rebasing this onto main branch?

@Shinyzenith Here you go!

Thank you!

@ajanon Please go ahead and merge this if convenient ❤

I just rebased this onto main. I will merge it once CI finishes.

@Shinyzenith If you could just approve this again so that I can merge it, it would be great!

Pr seems great! Go for the merge. Thank you for the patch ❤

How about now?

Perfect! :)

Reminder to self: push to mirror


PlugClean doesn't remove removed plugins

First, thank you for the great project. I just love it and use it every day. My problem is that :PlugClean doesn't clean the removed plugins. Doesn't matter whether I comment them " or just delete them completely from init.vim. :PlugClean doesn't remove them from plugged folder. I do not have any errors but every time I should go to delete them by hand.

Type:

[x] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[ ] Linux
[x] OS X
[ ] Windows

Vim:

[ ] Terminal Vim
[ ] GVim
[x] Neovim

Me too, for a few weeks now it just hang and I have to delete them by hand or remove the complete vimplug cache folder.
Any steps to know how to debug this?

To delete a plugin, comment out or delete the code that adds the plugin to vim-plug's list of plugins (ie. :Plug), close the editor, and then start a new editor process. :PlugClean should find the directory where the plugin was installed and delete that directory.
vim-plug does not support an uninstall command to uninstall the plugin in runtime because Vim/Neovim do not support plugin namespaces such that plugin code is isolated from the global Vim/Neovim environment and other plugins. It's useful to have one to cleanup non-Vimscript dependencies (ie. python, ruby, nodejs, binaries) because it may rely on the runtime environment.

@janlazo I tried what you suggested but it doesn' work. I deleted the line with the Plugin, sourced the init.vim, closed the editor, opened it again and run :PlugClean and I receive the message "Already clean" but the folder of the deleted plugin is still there.

Can you provide a minimal init.vim that demostrates the problem?


Weirdness with p value correction

The nominal and corrected p values for pulmonic stenosis are the same (PTPN11 cohort):
Let's double check the code for this -

As a minor issue, it would be good to align all columns left!

I think this is OK, because the corrected p value is equal to the nominal p value only in the _last _ term. I think this is expected in Benjamini/Hochberg correction.
In other words, we test 3 terms and only in case of the 3rd term the corrected p value is equal to the nominal p value.
However, please let me know if this sounds weird..


Dart FFI function returns num instead of int

Dart SDK Version Dart SDK version: 2.14.4 (stable) (Wed Oct 13 11:11:32 2021 +0200) on "linux_x64"
On Linux (x86_64)

While testing FFI I ran into an odd issue which is either non-intuitive or wrong (AKA: a bug), but I cannot exclude that I do something wrong.
I wrote a as-simple-as-possible test case here: https://github.com/haraldkubota/dart-ffi/tree/ffinum/ffi with a short README.md to explain how to reproduce this.
Summary:
primitives_bench.dart:46:15: Error: A value of type 'num' can't be assigned to a variable of type 'int'.
    sum = sum + prlib.plusOne(i);
              ^

prlib.plusOne() should have this signature: int prlib.plusOne(int), but I get above error and somehow Dart think it's returning a num instead.
This works:
    sum = sum + prlib.plusOne(i) as int;

Is this a bug? Is there an implicit num somewhere?

Same result on ARMv8 (same version 2.14.4), so it's not x86_64

variable prlib is declared as var prlib - so its static type is dynamic. Consequently prlib.plusOne(i) is a dynamic call which returns a value of static type dynamic. int + dynamic is num. Hence the error message.


VSC and JB add rate limit error handling UX

We need to indicate to PLG users that a quota has been exceeded for the following rate limits:

Chat and commands (20 messages/month, Pro: Unlimited)
Autocompletions (500 autocompletions/month, Pro: Unlimited)
Embeddings (Free: 200 mb/user/month, Pro: 1 GB/user/lifetime)

Requirements:

As a Code Free user who has hit a chat/command rate limit, I should see a notification that says, "Cody chat and command quota exceeded. Upgrade to Pro [link to /manage]."

This notification should appear in the chat panel if I've hit my limit by executing a chat
This notification should appear in the chat panel if I've hit my limit by executing a command that opens a new chat window (e.g., /smell, /explain, /test).
This notification should appear as a Code Lens if I've hit my limit by executing a command that generates in-editor code (e.g., /doc, /edit, or "Ask Cody to Explain," "Ask Cody to Fix," "Ask Cody to Edit" Code Actions). We need a fallback if Code Lenses are disabled.

As a Cody Free user who has hit an autocomplete rate limit, I should see a notification that says, "Cody autocomplete quota exceeded. Upgrade to Pro [link to /manage]."
As a Cody Free user who has hit an embeddings rate limit, I should see a notification in the "Enhanced Context" panel

If my project has already been indexed for embeddings, but these embeddings will no longer update, the message should be "Cody embeddings will no longer update because you've exceeded your quota. Upgrade to Pro [link to /manage]."
If my project has not been indexed for embeddings, the message should be "Unable to generate embeddings because you've exceeded your quota. Upgrade to Pro [link to /manage]."

As a Cody Pro user who has hit an embeddings rate limit, I should see a notification in the "Enhanced Context" panel

If my project has already been indexed for embeddings, but these embeddings will no longer update, the message should be "Cody embeddings will no longer update because you've exceeded your quota. Manage settings [link to /manage]."
If my project has not been indexed for embeddings, the message should be "Unable to generate embeddings because you've exceeded your quota. Manage settings [link to /manage]."

Closing in favor of https://github.com/sourcegraph/cody/issues/1576


docs(sidebar): Improve nested object specs in docs.md for sidebar

Previous version of docs did not contain proper specifications on nested objects in Docusaurus sidebars. See related issue: #3855
Motivation
There were no previous clear instructions on the matter of nested objects/items in the Docusaurus sidebar. Although minor, I believe it will help a great number of users, as I was struggling with this problem myself. Hope this helps! Let me know if anything must be fixed.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Since the code changed was just MD in the docs, I made sure it was of the proper, adequate standard by comparing the grammar, voice, and narration style throughout the rest of the Docusaurus documentation. This way, I made sure to maintain the same tone that makes the docs so engaging 👍 .
Example of what was covered in the newly added portion of documentation:

Related PRs
No related Pull Requests for this one. :)

Thanks
Unfortunately I think it's not the good place and good wording to describe this feature.
And after looking more carefully, it looks to me it's already documented properly:
https://v2.docusaurus.io/docs/docs-introduction/#category

Perfect! Thanks for letting me know @slorber


WIP: BUG: Pass CellData In Triangle Cell Subdivision

Currently, any CellData in the input mesh is not passed to the
subdivided output mesh.  This patch checks if any CellData exists,
and if so, passes that data into the child cells of the subdivided
output mesh.  This patch creates a new method, PassCellData, which
is called immediately following each call to AddFaceTriangle.  Moreover,
the interfaces to SplitTriangleFromOneEdge, SplitTriangleFromTwoEdges,
and SplitTriangleFromThreeEdges have all been extended to take the
cell identifier of the input cell, so that it will be available to pass to
the PassCellData method.  This has also required that the class for
iterative subdivision (IterativeCellSubdivisionQuadEdgeMeshFilter) be
updated.

Butterfly, Nonuniform:

Butterfly, Uniform:

Linear, Nonuniform:

Linear, Uniform:

Loop, Nonuniform:

Loop, Uniform:

Square, Nonuniform:

Square, Uniform:

@thewtex @hjmjohnson @arnaudgelas -- Tests are passing on my machine, looks like there are some wrapping errors.  Any feedback on this patch from someone more familiar with the codebase would be highly appreciated!

@DVigneault given that you cross-ref'ed this in PR #22, I am curious to know the whether the visualizations on the left are the ones that got your patch set applied and the ones in the right those that did not or else what the difference between the left/right renderings is.
BTW, very nice work !

@jhlegarreta Sorry for not being clear above--the left is prior to subdivision, the right is after subdivision.  Without the patch applied, the cell data is not passed, and so there is no color on right-and-side image.

@DVigneault awesome :rocket:, thanks for the explanation !

@thewtex Failing on windows because it can't find the executable files (KWStyle, testing drivers).  For example:
Unable to find executable: D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/KWStyle
D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/KWStyle
D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/KWStyle.exe
D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/Release/KWStyle
D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/Release/KWStyle.exe
Release/D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/KWStyle
Release/D:/a/ITKSubdivisionQuadEdgeMeshFilter/build/KWStyle-build/KWStyle.exe

Do you have any insight into where this might be coming from?

Problem was because I had used char**argv instead of char*argv[] in the function signature of my test.  Wish I could say that was the first (or last) time I'd made that mistake...


Update skoala install & upgrade docs

See preview: https://deploy-preview-2711--daocloud-docs.netlify.app/skoala/quickstart/skoala-init.html


shape of output data

Hi.
I ran infer_optimized.py with my webcam by reference to #20 and #42
But, i cant understand why out.shape = (1, 360, 640) (line38 : out = sess.run(y, feed_dict={x: img}).
i think this should be(360, 640, 3) because this is RGB image.
Can anyone explain this reason?

Hi.
After that, I understood (1, 360, 640) is Argmax. So, i used img_utils.py to show webcam images. But, fps drop to 80fps→12fps by showing images. im using gtx1080. Can i get more fps ? Thanks.

Hi.
After that, I understood (1, 360, 640) is Argmax. So, i used img_utils.py to show webcam images. But, fps drop to 80fps→12fps by showing images. im using gtx1080. Can i get more fps ?
Thanks.

the code which converts the argmax to an rgb image is very slow and not optimized as it is for looping on values and convert it to the correspond RGB color.
I don't know for now if there is a better algo or implementation for this.
I will try to get you something faster.
if i found something. i will let you know.

Hi@moemen95
Thank you for your reply.
I understand, I am looking forward to it.


Error at start

Hello,
The program generates an error at start. Though I can press continue and bring up the main window, But it won't ask for my credentials, or open a web page so I can login to my Drive account.

Hi,
Please follow the steps mentioned in "Step 1" in this document: https://developers.google.com/drive/v3/web/quickstart/dotnet
It's very important you place the "client_secret.json" file in the same folder where the software is located.

I'm closing this issue as this is documented in the Readme.
The next release will check if this file exists. If not, it will prompt you to follow the steps provided in the comment above. This check is already in the source code.


Should all commands always update from API?

If there is something wrong with my proxy server, it will wait a long time.

Renamed to "Should all commands always update from API?"
My take on thinking about this more is: "other than commands that formerly did brew update beforehand: no, probably not if we have an existing cache".
Would welcome any other @Homebrew/maintainers thoughts for or against here.

Renamed to "Should all commands always update from API?"
My take on thinking about this more is: "other than commands that formerly did brew update beforehand: no, probably not if we have an existing cache".
Would welcome any other @Homebrew/maintainers thoughts for or against here.

Thank you for your correction.
I noticed that I used a Chinese mirror, is it possible that this is because our cache validation mechanism keeps returning false for files downloaded from such mirrors?

@MikeMcQuaid not sure I totally understand the question here. Is the question whether to make Homebrew::API publicly documented to allow external commands to trigger their own updates?

I completely agree with defaulting to the cached file for non-autoupdate commands. Should be simple enough to figure out too since we already have all the autoupdate logic already, right?

Though there might be some other commands internally which now rely on the new behavior of fetching more frequently.

I noticed that I used a Chinese mirror, is it possible that this is because our cache validation mechanism keeps returning false for files downloaded from such mirrors?

@istomyang Try to play around with HOMEBREW_API_AUTO_UPDATE_SECS and see if it still updates every time.

@MikeMcQuaid not sure I totally understand the question here. Is the question whether to make Homebrew::API publicly documented to allow external commands to trigger their own updates?

@Rylan12 No. My thinking was whether we only automatically update if we have no existing cached data for AUTO_UPDATE_COMMANDS: https://github.com/Homebrew/brew/blob/9d5b0762fb40163d8b760c4df131b16745a287d2/Library/Homebrew/brew.sh#L272-L279

Should be simple enough to figure out too since we already have all the autoupdate logic already, right?

@apainintheneck Yeh, I think so. It's probably just a matter of setting something like export HOMEBREW_IN_AN_AUTO_UPDATE_COMMAND=1 in brew.sh and then using ENV["HOMEBREW_IN_AN_AUTO_UPDATE_COMMAND"].present? to adjust the auto-update logic accordingly.

Though there might be some other commands internally which now rely on the new behavior of fetching more frequently.

IMO these should be fine; if they work from a cache, they'll work with this. The only additional one that we should probably add here is brew outdated. It's always been a little confusing that brew outdated; brew upgrade outdated can say it's not going to update anything and then upgrade auto-updates and does so...

My thinking was whether we only automatically update if we have no existing cached data for AUTO_UPDATE_COMMANDS:
Yeh, I think so. It's probably just a matter of setting something like export HOMEBREW_IN_AN_AUTO_UPDATE_COMMAND=1 in brew.sh and then using ENV["HOMEBREW_IN_AN_AUTO_UPDATE_COMMAND"].present? to adjust the auto-update logic accordingly.

Opened https://github.com/Homebrew/brew/pull/14943 for this

The only additional one that we should probably add here is brew outdated. It's always been a little confusing that brew outdated; brew upgrade outdated can say it's not going to update anything and then upgrade auto-updates and does so...

Opened https://github.com/Homebrew/brew/pull/14942 for this


Add testnet tax override

Temporarily adds testnet consts to rhp/v2 for the tax hardfork. Enables testnet builds in hostd and renterd

👍🏻
Really need a better long-term solution for this. Maybe something like:
package consensus

type NetworkParams struct {
    BlockInterval time.Duration
    HardforkTax uint64
    HardforkStorageProof uint64
    // ... stuff from siad/types/constants.go, basically
}

var MainNet = NetworkParams{ /* ... */ }
var TestNet = NetworkParams{ /* ... */ }

type State struct {
    Network NetworkParams
    // ...
}


refactored panic handling - using build severe

Fixes #489
Using build.Severe right now almost everywhere. Maybe there is some indication of where I can use these build.Critical statements? Tests required some refactor also.

Since not only the statenents where if build.Debug were refactored, I would remove the if build.Debug from the Crtical funton to keep the behaviour consistent.

As @LeeSmet said, removing all the check with build.Debug && anotherExpensiveOperation
will reduce performance since this anotherExpensiveOperation will always be checked even if the build isn't debug. Any thoughts @robvanmieghem ?

This is true , question is if anotherExpensiveOperation is really that expensive, which requires  a thorough knowledge of the code . I prefer a sanity check that panics instead of an unseen error.

It's not really about a single check, but now we will always do all debug checks even in production. Maybe we should test this by letting a production build sync and time it, and letting a debug build sync and time it, to get an idea of how much of a performance penalty this is going to be (if any).

It's not really about a single check, but now we will always do all debug checks even in production.

OK, it does mean that you now indeed will have those if checks even when not in DEBUG, but as Rob says, I do think having some logging even in production for those situations which we deem severe anyhow, is not a luxury;
build.DEBUG will still be removed from compilation whether it is in a function or not.
it is true we will now do the other checks, but most of them just check something cheap enough to compute, with the exception of a few boltdb bucket calls, but even those are cheap enough that I don't expect the performance to go suddenly down;

I would just merge it as-is, and if you do start to see performance drops, we can measure and if needed define a function such as:
func SevereIf(f func() bool, v ...interface{})


cannot run due to bedrock-entry.sh operation not permitted

I am seeing this in the container logs:
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=5000 from match path
DEBU[0000] Resolved GID=5000 from match path
FATA[0000] Failed to run sub-command                     error="fork/exec /opt/bedrock-entry.sh: operation not permitted"
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=5000 from match path
DEBU[0000] Resolved GID=5000 from match path
FATA[0000] Failed to run sub-command                     error="fork/exec /opt/bedrock-entry.sh: operation not permitted"

this is running on an Ubuntu machine in digital ocean with this docker version:
root@minecraft-docker-01a:~# docker --version
Docker version 20.10.7, build 20.10.7-0ubuntu5~20.04.2

I am using this script to start the container:
#!/bin/bash

mkdir -p /var/lib/minecraft/data/
chown 5000:5000 /var/lib/minecraft -R

# -dit means detach, interactive, pseudo tty. This allows you to attach and detach from stdin
#
# 3G memory should leave some room within the 4G that the VM has?
#
docker run \
	-dit \
	--restart="on-failure" \
	-v /var/lib/minecraft/data:/data:Z \
	-p 19132:19132/udp \
	-u 5000:5000 \
	-e VERSION=LATEST \
	-e SEED="-479112237913370" \
	-e OPS="DerElbenkoenig" \
	-e OVERRIDE_OPS=true \
	-e EULA=TRUE \
	-e MEMORY=3G \
	--name minecraftserver \
	docker.io/itzg/minecraft-bedrock-server:latest

Well. as it turns out, removing the -u 5000:5000 appears to have fixed this. but I'm not sure if that's what I want, because I think that means the whole container is running as root... maybe that's fine?

Well. as it turns out, removing the -u 5000:5000 appears to have fixed this. but I'm not sure if that's what I want, because I think that means the whole container is running as root... maybe that's fine?

The startup system demotes the bedrock process to match the owner of the data volume, so it's ultimately not running as root even when you're leaving off the -u.
I will still investigate this a bit, because maybe I'm missing logic to skip the demotion if already running as the user.

Hey, I'm experiencing the same issue. I had replaced an HDD over the weekend and copied the data, including my docker containers to the new drive.
My script is as follows
#!/bin/bash
docker run -d --restart="always" --name=minecraft --env EULA=TRUE -e PUDI=1000 -e PGID=998 --net=docker_bridge --ip=<IP_ADDRESS> -p 19132:19132/udp --volume /etc/localtime:/etc/localtime:ro  --volume /mnt/OtherMedia/DockerContainers/minecraftbr:/data itzg/minecraft-bedrock-server
When it creates the volume for /data, it's creating it as root:root even though it should the owner/group specified.

@itzg I apologize, I commented on the wrong thread. I'm not having the same issue as Op. My issue is actually the same as #141

@itzg I'll give it a shot next time I restart my server, thanks for the reply!


Crash when CompilationUnit.declaredElement is null

NoSuchMethodError: The getter 'topLevelVariables' was called on null.
Receiver: null
Tried calling: topLevelVariables
#0      LibraryAnalyzer._resolveFile (package:analyzer/src/dart/micro/library_analyzer.dart:683)
#1      LibraryAnalyzer.analyzeSync.<anonymous closure>.<anonymous closure> (package:analyzer/src/dart/micro/library_analyzer.dart:148)
#2      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:397)
#3      LibraryAnalyzer.analyzeSync.<anonymous closure> (package:analyzer/src/dart/micro/library_analyzer.dart:147)
#4      OperationPerformanceImpl.run (package:analyzer/src/util/performance/operation_performance.dart:137)
#5      LibraryAnalyzer.analyzeSync (package:analyzer/src/dart/micro/library_analyzer.dart:146)
#6      FileResolver.resolve.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:analyzer/src/dart/micro/resolve_file.dart:382)
#7      _rootRun (dart:async/zone.dart:1354)
#8      _CustomZone.run (dart:async/zone.dart:1258)
#9      _runZoned (dart:async/zone.dart:1788)
#10     runZoned (dart:async/zone.dart:1710)
#11     NullSafetyUnderstandingFlag.enableNullSafetyTypes (package:analyzer/dart/element/null_safety_understanding_flag.dart:42)
#12     FileResolver.resolve.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:analyzer/src/dart/micro/resolve_file.dart:381)
#13     OperationPerformanceImpl.run (package:analyzer/src/util/performance/operation_performance.dart:137)
#14     FileResolver.resolve.<anonymous closure>.<anonymous closure> (package:analyzer/src/dart/micro/resolve_file.dart:380)
#15     PerformanceLog.run (package:analyzer/src/dart/analysis/performance_logger.dart:32)
#16     FileResolver.resolve.<anonymous closure> (package:analyzer/src/dart/micro/resolve_file.dart:365)
#17     PerformanceLog.run (package:analyzer/src/dart/analysis/performance_logger.dart:32)
#18     FileResolver.resolve (package:analyzer/src/dart/micro/resolve_file.dart:336)
#19     CiderCompletionComputer.compute.<anonymous closure>.<anonymous closure> (package:analysis_server/src/cider/completion.dart:61)
#20     OperationPerformanceImpl.run (package:analyzer/src/util/performance/operation_performance.dart:137)
#21     CiderCompletionComputer.compute.<anonymous closure> (package:analysis_server/src/cider/completion.dart:60)
#22     CiderCompletionComputer.compute.<anonymous closure> (package:analysis_server/src/cider/completion.dart:59)
#23     OperationPerformanceImpl.runAsync (package:analyzer/src/util/performance/operation_performance.dart:157)
#24     CiderCompletionComputer.compute (package:analysis_server/src/cider/completion.dart:59)
#25     CiderCompletionComputer.warmUp (package:analysis_server/src/cider/completion.dart:176)

A related fix https://dart-review.googlesource.com/c/sdk/+/182366

Add debug information: https://dart-review.googlesource.com/c/sdk/+/182367

Closing as stale; please re-open if you see this crash on a recent version of Dart.


Make explorer geo more optimized

Batch call watchers so the loading symbol doesn't flicker (just tabbed everything over)
If scatter/line, swap to points/path
Projection doesn't always seem to be provided, so use crs instead

New test failure; prob should handle in a separate PR.
AttributeError: The geopandas.dataset has been deprecated and was removed in GeoPandas 1.0. You can get the original 'naturalearth_cities' data from [https://www.naturalearthdata.com/downloads/110m-cultural-vectors/.](https://www.naturalearthdata.com/downloads/110m-cultural-vectors/)


Use service-lifecycle-v2-beta

Replace deprecated APIs

@adam-fowler can you update this to 2.0 now?

@adam-fowler can you update this to 2.0 now?

done


Some links to nixos options contain nixos/modules/ twice

For example: https://search.nixos.org/options?channel=unstable&show=environment.shells&from=0&size=50&sort=relevance&type=packages&query=environment.shells
has Declared in nixos/modules/nixos/modules/config/shells-environment.nix which links to https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/nixos/modules/config/shells-environment.nix
The correct name would be nixos/modules/config/shells-environment.nix and link https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/config/shells-environment.nix

Not a nixos-search issue: this issue also appears in the upstream options.json. First bad commit is https://github.com/NixOS/nixpkgs/commit/52b0ad17e3727fe0c3ca028787128ede5fb86352

Fixed by https://github.com/NixOS/nixpkgs/pull/185056#issuecomment-1206572049


build(ts-model-api): remove dependencies on configuration files from The Really Project

The Really Project is not suited to provide default configuration files because those configuration files are specific to that project.
I inlined and merged the configurations from The Really Project (v2.0.0).
See https://github.com/reallyland/tsconfig/blob/v2.0.0/tsconfig.json
To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

This will also resolve #438

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


Add: Canal 40 Caucete

Channel Name
Canal 40 Caucete
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
AR
Subdivision (optional)
No response
City (optional)
San Juan
Broadcast Area
s/AR
Languages
esp
Categories (optional)
general
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://canal40hd.com.ar/
Logo
https://lh3.googleusercontent.com/p/AF1QipNRmy5EGdR4rcvXxs643rRbaTTudXvcll17pxKH=s680-w680-h510
Notes
No response

Already on the database as "Canal40Cauecte.ar"

Whoops!


Fix ServiceTuple and ServicePublic definitions

Add missing required attributes.

Warnings

:warning:

Please include a Pivotal story at the beginning of the PR title (see below).

Example of PR titles that include pivotal stories:

single story: [#123456] my PR title
multiple stories: [#123456,#123457,#123458] my PR title

  Generated by :no_entry_sign: dangerJS

@fpersico released in v0.59.0


Add support for BROKER_TRANSPORT_OPTIONS

Add support for BROKER_TRANSPORT_OPTIONS in Celery 4.1 and up.

Fixes #67

Coverage decreased (-0.6%) to 95.862% when pulling 6b4a7f95b844acb412a7107b8211364474be8c2d on CasperCL:master into e2799fcb7960edee0b2e1a2554742dccba01c85f on sontek:master.

Thanks!  I'll get this merged and released today

Thanks! I'll get this merged and released today

This would be very helpful thank you :)

@CasperCL Can you  merge master into this PR so we can see the tests passing?   Then I think we are good to go

Oh I didn't realise the build was fixed on master! My repo is now up to date with yours.

@CasperCL I'm thinking of updating this API a bit.  You've designed it out to look like this:
broker_transport_options = {'visibility_timeout': 18000}

Which could get weird to work with / read because you can't use whitespace or anything in it.  I'm thinking instead that we put the key/value pairs underneath:
broker_transport_options =
    visibility_timeout: 18000
    max_retries: 5

or introducing a new configuration section which would be more ini like:
[celery:broker_transport_options]
visibility_timeout = 18000
max_retries = 5

I'm leaning towards the second for semantics of the ini file but it'd be interesting to hear your thoughts

Actually, I just realized we do the second way for both celerybeat and celeryroute, so I think thats the way to go

@sontek I'm all for it.

@CasperCL How does this look?
https://github.com/sontek/pyramid_celery/pull/86

Implemented in #86


Wrong logging of offsets.

Hi,
I started a consumer subscribing to an empty topic. Then with extreme speed dumped 37869 messages in a that clean topic. My consumer side by side started fetching. Looking at the log shows that it processed exactly 37869 times. But when I see the offset that is processed, there are duplicates => so some offsets are missing [to account for the duplicate.]. So I think that there is issue with logging.
You can see that offset 14, 15 47, etc being repeated. As this is not a complete log you cannot see the missing ones. But I counted the complete processed lines and it is 37869 but the uniq offsets in the logs are only 36213.
Log:
[2018-02-01T18:36:54.665162 #9229] DEBUG -- : Opening connection to <IP_ADDRESS>:9092 with client id app...
[2018-02-01T18:36:54.666681 #9229] DEBUG -- : Sending topic_metadata API request 1 to <IP_ADDRESS>:9092
[2018-02-01T18:36:54.667059 #9229] DEBUG -- : Waiting for response 1 from <IP_ADDRESS>:9092
[2018-02-01T18:36:54.734866 #9229] DEBUG -- : Received response 1 from <IP_ADDRESS>:9092
[2018-02-01T18:36:54.735114 #9229]  INFO -- : Discovered cluster metadata; nodes: <IP_ADDRESS>:9092 (node_id=0)
[2018-02-01T18:36:54.735727 #9229] DEBUG -- : Closing socket to <IP_ADDRESS>:9092
[2018-02-01T18:36:54.736415 #9229]  INFO -- : Joining group `app.test-consumer`
[2018-02-01T18:36:54.736644 #9229] DEBUG -- : Getting group coordinator for `app.test-consumer`
[2018-02-01T18:36:54.737095 #9229] DEBUG -- : Opening connection to <IP_ADDRESS>:9092 with client id app...
[2018-02-01T18:36:54.738381 #9229] DEBUG -- : Sending group_coordinator API request 1 to <IP_ADDRESS>:9092
[2018-02-01T18:36:54.738769 #9229] DEBUG -- : Waiting for response 1 from <IP_ADDRESS>:9092
[2018-02-01T18:36:54.740335 #9229] DEBUG -- : Received response 1 from <IP_ADDRESS>:9092
[2018-02-01T18:36:54.752906 #9229] DEBUG -- : Coordinator for group `app.test-consumer` is 0. Connecting...
[2018-02-01T18:36:54.753322 #9229] DEBUG -- : Connected to coordinator: <IP_ADDRESS>:9092 (node_id=0) for group `app.test-consumer`
[2018-02-01T18:36:54.765412 #9229] DEBUG -- : Sending join_group API request 2 to <IP_ADDRESS>:9092
[2018-02-01T18:36:54.795344 #9229] DEBUG -- : Waiting for response 2 from <IP_ADDRESS>:9092
[2018-02-01T18:36:54.825464 #9229] DEBUG -- : Received response 2 from <IP_ADDRESS>:9092
[2018-02-01T18:36:54.825875 #9229]  INFO -- : Joined group `app.test-consumer` with member id `app-6219334d-867f-4d6b-aff6-d1e841912c07`
[2018-02-01T18:36:54.826119 #9229]  INFO -- : Chosen as leader of group `app.test-consumer`
[2018-02-01T18:36:55.832149 #9229]  INFO -- : Fetching cluster metadata from kafka://<IP_ADDRESS>:9092
[2018-02-01T18:36:55.832409 #9229] DEBUG -- : Opening connection to <IP_ADDRESS>:9092 with client id app...
[2018-02-01T18:36:55.833883 #9229] DEBUG -- : Sending topic_metadata API request 1 to <IP_ADDRESS>:9092
[2018-02-01T18:36:55.834169 #9229] DEBUG -- : Waiting for response 1 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.835199 #9229] DEBUG -- : Received response 1 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.835335 #9229]  INFO -- : Discovered cluster metadata; nodes: <IP_ADDRESS>:9092 (node_id=0)
[2018-02-01T18:36:55.835403 #9229] DEBUG -- : Closing socket to <IP_ADDRESS>:9092
[2018-02-01T18:36:55.835788 #9229] DEBUG -- : Sending sync_group API request 3 to <IP_ADDRESS>:9092
[2018-02-01T18:36:55.836217 #9229] DEBUG -- : Waiting for response 3 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.840094 #9229] DEBUG -- : Received response 3 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.840194 #9229]  INFO -- : Partitions assigned for `users`: 0
[2018-02-01T18:36:55.840358 #9229] DEBUG -- : Sending offset_fetch API request 4 to <IP_ADDRESS>:9092
[2018-02-01T18:36:55.840597 #9229] DEBUG -- : Waiting for response 4 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.841112 #9229] DEBUG -- : Received response 4 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.841285 #9229] DEBUG -- : Sending list_offset API request 5 to <IP_ADDRESS>:9092
[2018-02-01T18:36:55.841527 #9229] DEBUG -- : Waiting for response 5 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.854307 #9229] DEBUG -- : Received response 5 from <IP_ADDRESS>:9092
[2018-02-01T18:36:55.854537 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:36:55.854915 #9229] DEBUG -- : Sending fetch API request 6 to <IP_ADDRESS>:9092
[2018-02-01T18:36:55.855252 #9229] DEBUG -- : Waiting for response 6 from <IP_ADDRESS>:9092
[2018-02-01T18:37:00.859910 #9229] DEBUG -- : Received response 6 from <IP_ADDRESS>:9092
[2018-02-01T18:37:00.862207 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:00.862523 #9229] DEBUG -- : Sending fetch API request 7 to <IP_ADDRESS>:9092
[2018-02-01T18:37:00.862960 #9229] DEBUG -- : Waiting for response 7 from <IP_ADDRESS>:9092
[2018-02-01T18:37:05.866017 #9229] DEBUG -- : Received response 7 from <IP_ADDRESS>:9092
[2018-02-01T18:37:05.866268 #9229]  INFO -- : Sending heartbeat...
[2018-02-01T18:37:05.866508 #9229] DEBUG -- : Sending heartbeat API request 8 to <IP_ADDRESS>:9092
[2018-02-01T18:37:05.866932 #9229] DEBUG -- : Waiting for response 8 from <IP_ADDRESS>:9092
[2018-02-01T18:37:05.867952 #9229] DEBUG -- : Received response 8 from <IP_ADDRESS>:9092
[2018-02-01T18:37:05.868115 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:05.868393 #9229] DEBUG -- : Sending fetch API request 9 to <IP_ADDRESS>:9092
[2018-02-01T18:37:05.868784 #9229] DEBUG -- : Waiting for response 9 from <IP_ADDRESS>:9092
[2018-02-01T18:37:10.872356 #9229] DEBUG -- : Received response 9 from <IP_ADDRESS>:9092
[2018-02-01T18:37:10.872620 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:10.872828 #9229] DEBUG -- : Sending fetch API request 10 to <IP_ADDRESS>:9092
[2018-02-01T18:37:10.873052 #9229] DEBUG -- : Waiting for response 10 from <IP_ADDRESS>:9092
[2018-02-01T18:37:15.879963 #9229] DEBUG -- : Received response 10 from <IP_ADDRESS>:9092
[2018-02-01T18:37:15.880153 #9229]  INFO -- : Sending heartbeat...
[2018-02-01T18:37:15.880293 #9229] DEBUG -- : Sending heartbeat API request 11 to <IP_ADDRESS>:9092
[2018-02-01T18:37:15.880564 #9229] DEBUG -- : Waiting for response 11 from <IP_ADDRESS>:9092
[2018-02-01T18:37:15.881873 #9229] DEBUG -- : Received response 11 from <IP_ADDRESS>:9092
[2018-02-01T18:37:15.882035 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:15.882276 #9229] DEBUG -- : Sending fetch API request 12 to <IP_ADDRESS>:9092
[2018-02-01T18:37:15.882596 #9229] DEBUG -- : Waiting for response 12 from <IP_ADDRESS>:9092
[2018-02-01T18:37:20.885767 #9229] DEBUG -- : Received response 12 from <IP_ADDRESS>:9092
[2018-02-01T18:37:20.885968 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:20.886338 #9229] DEBUG -- : Sending fetch API request 13 to <IP_ADDRESS>:9092
[2018-02-01T18:37:20.886756 #9229] DEBUG -- : Waiting for response 13 from <IP_ADDRESS>:9092
[2018-02-01T18:37:25.891438 #9229] DEBUG -- : Received response 13 from <IP_ADDRESS>:9092
[2018-02-01T18:37:25.891691 #9229]  INFO -- : Sending heartbeat...
[2018-02-01T18:37:25.891980 #9229] DEBUG -- : Sending heartbeat API request 14 to <IP_ADDRESS>:9092
[2018-02-01T18:37:25.892540 #9229] DEBUG -- : Waiting for response 14 from <IP_ADDRESS>:9092
[2018-02-01T18:37:25.893998 #9229] DEBUG -- : Received response 14 from <IP_ADDRESS>:9092
[2018-02-01T18:37:25.894296 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:25.894606 #9229] DEBUG -- : Sending fetch API request 15 to <IP_ADDRESS>:9092
[2018-02-01T18:37:25.894912 #9229] DEBUG -- : Waiting for response 15 from <IP_ADDRESS>:9092
[2018-02-01T18:37:30.900586 #9229] DEBUG -- : Received response 15 from <IP_ADDRESS>:9092
[2018-02-01T18:37:30.902817 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:30.903222 #9229] DEBUG -- : Sending fetch API request 16 to <IP_ADDRESS>:9092
[2018-02-01T18:37:30.903673 #9229] DEBUG -- : Waiting for response 16 from <IP_ADDRESS>:9092
[2018-02-01T18:37:35.906216 #9229] DEBUG -- : Received response 16 from <IP_ADDRESS>:9092
[2018-02-01T18:37:35.906349 #9229]  INFO -- : Sending heartbeat...
[2018-02-01T18:37:35.906485 #9229] DEBUG -- : Sending heartbeat API request 17 to <IP_ADDRESS>:9092
[2018-02-01T18:37:35.906702 #9229] DEBUG -- : Waiting for response 17 from <IP_ADDRESS>:9092
[2018-02-01T18:37:35.908049 #9229] DEBUG -- : Received response 17 from <IP_ADDRESS>:9092
[2018-02-01T18:37:35.908200 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:35.908439 #9229] DEBUG -- : Sending fetch API request 18 to <IP_ADDRESS>:9092
[2018-02-01T18:37:35.908703 #9229] DEBUG -- : Waiting for response 18 from <IP_ADDRESS>:9092
[2018-02-01T18:37:40.910913 #9229] DEBUG -- : Received response 18 from <IP_ADDRESS>:9092
[2018-02-01T18:37:40.911282 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:40.911484 #9229] DEBUG -- : Sending fetch API request 19 to <IP_ADDRESS>:9092
[2018-02-01T18:37:40.911729 #9229] DEBUG -- : Waiting for response 19 from <IP_ADDRESS>:9092
[2018-02-01T18:37:45.914329 #9229] DEBUG -- : Received response 19 from <IP_ADDRESS>:9092
[2018-02-01T18:37:45.914544 #9229]  INFO -- : Sending heartbeat...
[2018-02-01T18:37:45.914694 #9229] DEBUG -- : Sending heartbeat API request 20 to <IP_ADDRESS>:9092
[2018-02-01T18:37:45.914959 #9229] DEBUG -- : Waiting for response 20 from <IP_ADDRESS>:9092
[2018-02-01T18:37:45.916428 #9229] DEBUG -- : Received response 20 from <IP_ADDRESS>:9092
[2018-02-01T18:37:45.916642 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 0
[2018-02-01T18:37:45.916982 #9229] DEBUG -- : Sending fetch API request 21 to <IP_ADDRESS>:9092
[2018-02-01T18:37:45.917291 #9229] DEBUG -- : Waiting for response 21 from <IP_ADDRESS>:9092
[2018-02-01T18:37:48.876384 #9229] DEBUG -- : Received response 21 from <IP_ADDRESS>:9092
[2018-02-01T18:37:48.882302 #9229] DEBUG -- : Marking users/0:0 as processed
[2018-02-01T18:37:48.882483 #9229]  INFO -- : Committing offsets with recommit: users/0:1
[2018-02-01T18:37:48.882635 #9229] DEBUG -- : Sending offset_commit API request 22 to <IP_ADDRESS>:9092
[2018-02-01T18:37:48.882937 #9229] DEBUG -- : Waiting for response 22 from <IP_ADDRESS>:9092
[2018-02-01T18:37:48.885830 #9229] DEBUG -- : Received response 22 from <IP_ADDRESS>:9092
[2018-02-01T18:37:48.885981 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 1
[2018-02-01T18:37:48.886155 #9229] DEBUG -- : Sending fetch API request 23 to <IP_ADDRESS>:9092
[2018-02-01T18:37:48.886364 #9229] DEBUG -- : Waiting for response 23 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.062736 #9229] DEBUG -- : Received response 23 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.065367 #9229] DEBUG -- : Marking users/0:1 as processed
[2018-02-01T18:37:49.065489 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 2
[2018-02-01T18:37:49.077563 #9229] DEBUG -- : Sending fetch API request 24 to <IP_ADDRESS>:9092
[2018-02-01T18:37:49.077726 #9229] DEBUG -- : Waiting for response 24 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.101840 #9229] DEBUG -- : Received response 24 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.106902 #9229] DEBUG -- : Marking users/0:2 as processed
[2018-02-01T18:37:49.107106 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 3
[2018-02-01T18:37:49.107895 #9229] DEBUG -- : Sending fetch API request 25 to <IP_ADDRESS>:9092
[2018-02-01T18:37:49.108265 #9229] DEBUG -- : Waiting for response 25 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.117768 #9229] DEBUG -- : Received response 25 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.122265 #9229] DEBUG -- : Marking users/0:6 as processed
[2018-02-01T18:37:49.127335 #9229] DEBUG -- : Marking users/0:7 as processed
[2018-02-01T18:37:49.130767 #9229] DEBUG -- : Marking users/0:8 as processed
[2018-02-01T18:37:49.134990 #9229] DEBUG -- : Marking users/0:9 as processed
[2018-02-01T18:37:49.139811 #9229] DEBUG -- : Marking users/0:8 as processed
[2018-02-01T18:37:49.143620 #9229] DEBUG -- : Marking users/0:9 as processed
[2018-02-01T18:37:49.148249 #9229] DEBUG -- : Marking users/0:12 as processed
[2018-02-01T18:37:49.151859 #9229] DEBUG -- : Marking users/0:13 as processed
[2018-02-01T18:37:49.155126 #9229] DEBUG -- : Marking users/0:14 as processed
[2018-02-01T18:37:49.158733 #9229] DEBUG -- : Marking users/0:15 as processed
[2018-02-01T18:37:49.162549 #9229] DEBUG -- : Marking users/0:14 as processed
[2018-02-01T18:37:49.165250 #9229] DEBUG -- : Marking users/0:15 as processed
[2018-02-01T18:37:49.170275 #9229] DEBUG -- : Marking users/0:44 as processed
[2018-02-01T18:37:49.172494 #9229] DEBUG -- : Marking users/0:45 as processed
[2018-02-01T18:37:49.175404 #9229] DEBUG -- : Marking users/0:46 as processed
[2018-02-01T18:37:49.179739 #9229] DEBUG -- : Marking users/0:47 as processed
[2018-02-01T18:37:49.184462 #9229] DEBUG -- : Marking users/0:48 as processed
[2018-02-01T18:37:49.188032 #9229] DEBUG -- : Marking users/0:49 as processed
[2018-02-01T18:37:49.191116 #9229] DEBUG -- : Marking users/0:50 as processed
[2018-02-01T18:37:49.194450 #9229] DEBUG -- : Marking users/0:51 as processed
[2018-02-01T18:37:49.197938 #9229] DEBUG -- : Marking users/0:52 as processed
[2018-02-01T18:37:49.201562 #9229] DEBUG -- : Marking users/0:53 as processed
[2018-02-01T18:37:49.205061 #9229] DEBUG -- : Marking users/0:54 as processed
[2018-02-01T18:37:49.207701 #9229] DEBUG -- : Marking users/0:55 as processed
[2018-02-01T18:37:49.210568 #9229] DEBUG -- : Marking users/0:56 as processed
[2018-02-01T18:37:49.212780 #9229] DEBUG -- : Marking users/0:57 as processed
[2018-02-01T18:37:49.216208 #9229] DEBUG -- : Marking users/0:58 as processed
[2018-02-01T18:37:49.218950 #9229] DEBUG -- : Marking users/0:59 as processed
[2018-02-01T18:37:49.220674 #9229] DEBUG -- : Marking users/0:60 as processed
[2018-02-01T18:37:49.223278 #9229] DEBUG -- : Marking users/0:61 as processed
[2018-02-01T18:37:49.227621 #9229] DEBUG -- : Marking users/0:62 as processed
[2018-02-01T18:37:49.229517 #9229] DEBUG -- : Marking users/0:63 as processed
[2018-02-01T18:37:49.232582 #9229] DEBUG -- : Marking users/0:64 as processed
[2018-02-01T18:37:49.235681 #9229] DEBUG -- : Marking users/0:65 as processed
[2018-02-01T18:37:49.240375 #9229] DEBUG -- : Marking users/0:66 as processed
[2018-02-01T18:37:49.246845 #9229] DEBUG -- : Marking users/0:67 as processed
[2018-02-01T18:37:49.251738 #9229] DEBUG -- : Marking users/0:68 as processed
[2018-02-01T18:37:49.254770 #9229] DEBUG -- : Marking users/0:69 as processed
[2018-02-01T18:37:49.259062 #9229] DEBUG -- : Marking users/0:70 as processed
[2018-02-01T18:37:49.263681 #9229] DEBUG -- : Marking users/0:71 as processed
[2018-02-01T18:37:49.265919 #9229] DEBUG -- : Marking users/0:72 as processed
[2018-02-01T18:37:49.271436 #9229] DEBUG -- : Marking users/0:73 as processed
[2018-02-01T18:37:49.282440 #9229] DEBUG -- : Marking users/0:46 as processed
[2018-02-01T18:37:49.288774 #9229] DEBUG -- : Marking users/0:47 as processed
[2018-02-01T18:37:49.289384 #9229] DEBUG -- : Fetching batch from users/0 starting at offset 48
[2018-02-01T18:37:49.289677 #9229] DEBUG -- : Sending fetch API request 26 to <IP_ADDRESS>:9092
[2018-02-01T18:37:49.324238 #9229] DEBUG -- : Waiting for response 26 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.410467 #9229] DEBUG -- : Received response 26 from <IP_ADDRESS>:9092
[2018-02-01T18:37:49.417028 #9229] DEBUG -- : Marking users/0:69 as processed
[2018-02-01T18:37:49.427439 #9229] DEBUG -- : Marking users/0:70 as processed
[2018-02-01T18:37:49.429819 #9229] DEBUG -- : Marking users/0:71 as processed

Consumer:

class TestConsumer < Racecar::Consumer
  subscribes_to 'users', start_from_beginning: false

  def process(message)
    count = Rails.cache.read("count")

    unless count
      count = 0
    end

    Rails.cache.write("count", count + 1)
  end
end

Versions:

Racecar: 0.3.5
Ruby Kafka: 0.5.1
Ruby: 2.3.1

PS: This is fixed in Ruby Kafka: 0.5.2


Unshaky doesn't work with Bitwarden

Describe the bug
Sometimes unshaky stop working and debug windows is empty.
To Reproduce
Not every time it stops working, but until you close Bitwarden debug windows is empty and unskaky not working.
Desktop (please complete the following information):

macOS version: 10.15.6

Additional context
Unshaky doesn't stop working every time and every day. But after the close of Bitwarden, everything is fine. This is very strange. Bitwarden is open source password management https://bitwarden.com/

Do you have the option ignore external keyboard on? It is likely Bitwarden changes the keyboard types.

Close due to inactivity


dylib support

Thanks for your excellent script, it would be much more useful if you could add the option to build dylib instead of .a libraries.

Thanks, the script is a slight refinement of another work. Also, this fork precisely addresses . dylib outputs -I made this mainly for CocoaPods-, you can generate a dynamic framework from the command line.


[s3]  post to filer  http: read on closed response body

Describe the bug
post to filer  http: read on closed response body return
s3_1         | E1111 06:44:18     1 s3api_object_handlers.go:317] post to filer: Put "http://filer:8888/buckets/registry/.uploads/8ed6ddca-e16f-476f-8fb4-57cc2ac3b268/0001.part?collection=registry": http: read on closed response body
s3_1         | I1111 06:44:18     1 s3api_handlers.go:89] status 500 application/xml: <?xml version="1.0" encoding="UTF-8"?>
s3_1         | <Error>InternalError<Message>We encountered an internal error, please try again.</Message><Resource>/registry/docker/registry/v2/blobs/sha256/75/75f829a71a1c5277a7abf55495ac8d16759691d980bf1d931795e5eb68a294c0/data</Resource><RequestId>1605077058120997200</RequestId></Error>
filer_1      | I1111 06:44:18     1 common.go:53] response method:PUT URL:/buckets/registry/.uploads/8ed6ddca-e16f-476f-8fb4-57cc2ac3b268/0001.part?collection=registry with httpStatus:500 and JSON:{"error":"read input: unexpected EOF"}

System Setup
version 2.09
local-registry-compose.yml:
version: '2'

services:
  master:
    image: chrislusf/seaweedfs:local
    ports:
      - 9333:9333
      - 19333:19333
    command: "master -ip=master"
  volume:
    image: chrislusf/seaweedfs:local
    ports:
      - 8080:8080
      - 18080:18080
    command: "volume -mserver=master:9333 -port=8080 -ip=volume -max=0"
    depends_on:
      - master
  filer:
    image: chrislusf/seaweedfs:local
    ports:
      - 8888:8888
      - 18888:18888
    command: 'filer -master="master:9333"'
    depends_on:
      - master
      - volume
  s3:
    image: chrislusf/seaweedfs:local
    ports:
      - 8333:8333
    command: '-v 9 s3 -filer="filer:8888"'
    depends_on:
      - master
      - volume
      - filer
  minio:
    image: minio/minio
    ports:
      - 9000:9000
    command: 'minio server /data'
    environment:
      MINIO_ACCESS_KEY: "some_access_key1"
      MINIO_SECRET_KEY: "some_secret_key1"
    depends_on:
      - master
  registry1:
    image: registry:2
    environment:
      REGISTRY_HTTP_ADDR: "<IP_ADDRESS>:5001" # seaweedfs s3
      REGISTRY_LOG_LEVEL: "debug"
      REGISTRY_STORAGE: "s3"
      REGISTRY_STORAGE_S3_REGION: "us-east-1"
      REGISTRY_STORAGE_S3_REGIONENDPOINT: "http://s3:8333"
      REGISTRY_STORAGE_S3_BUCKET: "registry"
      REGISTRY_STORAGE_S3_ACCESSKEY: "some_access_key1"
      REGISTRY_STORAGE_S3_SECRETKEY: "some_secret_key1"
      REGISTRY_STORAGE_S3_V4AUTH: "true"
      REGISTRY_STORAGE_S3_SECURE: "false"
      REGISTRY_STORAGE_S3_SKIPVERIFY: "true"
      REGISTRY_STORAGE_S3_ROOTDIRECTORY: "/"
      REGISTRY_STORAGE_DELETE_ENABLED: "true"
      REGISTRY_STORAGE_REDIRECT_DISABLE: "true"
      REGISTRY_VALIDATION_DISABLED: "true"
    ports:
      - 5001:5001
    depends_on:
      - s3
      - minio
  registry2:
    image: registry:2
    environment:
      REGISTRY_HTTP_ADDR: "<IP_ADDRESS>:5002" # minio
      REGISTRY_LOG_LEVEL: "debug"
      REGISTRY_STORAGE: "s3"
      REGISTRY_STORAGE_S3_REGION: "us-east-1"
      REGISTRY_STORAGE_S3_REGIONENDPOINT: "http://minio:9000"
      REGISTRY_STORAGE_S3_BUCKET: "registry"
      REGISTRY_STORAGE_S3_ACCESSKEY: "some_access_key1"
      REGISTRY_STORAGE_S3_SECRETKEY: "some_secret_key1"
      REGISTRY_STORAGE_S3_V4AUTH: "true"
      REGISTRY_STORAGE_S3_SECURE: "false"
      REGISTRY_STORAGE_S3_SKIPVERIFY: "true"
      REGISTRY_STORAGE_S3_ROOTDIRECTORY: "/"
      REGISTRY_STORAGE_DELETE_ENABLED: "true"
      REGISTRY_STORAGE_REDIRECT_DISABLE: "true"
      REGISTRY_VALIDATION_DISABLED: "true"
    ports:
      - 5002:5002
    depends_on:
      - s3
      - minio

run
docker-compose -f local-registry-compose.yml -p seaweedfs up
Expected behavior
Avoid httpStatus:500
Additional context

docker pull logstash:7.9.3
docker tag logstash:7.9.3 <IP_ADDRESS>:5001/logstash:7.9.3
docker push <IP_ADDRESS>:5001/logstash:7.9.3

The push refers to repository [<IP_ADDRESS>:5001/logstash]
d531f1620717: Pushed
da29e51f4b5a: Pushed
e130db055e76: Pushed
d01d03eef5d2: Pushed
11689358ee84: Pushed
39d2e7f98e7d: Pushed
174f912d511e: Pushed
99de5206293b: Pushing [=================>                                 ]    102MB/290.2MB
51ff5420b316: Pushed
2e0e4cba5ae9: Retrying in 8 seconds
613be09ab3c0: Retrying in 15 seconds

but for mino it is OK

The push refers to repository [<IP_ADDRESS>:5002/logstash]
d531f1620717: Pushed
da29e51f4b5a: Pushed
e130db055e76: Pushed
d01d03eef5d2: Pushed
11689358ee84: Pushed
39d2e7f98e7d: Pushed
174f912d511e: Pushed
99de5206293b: Pushed
51ff5420b316: Pushed
2e0e4cba5ae9: Pushed
613be09ab3c0: Pushed
7.9.3: digest: sha256:cbd441b072dbd5271ecd02de560d7780594672321f90036c9ace1618be41f042 size: 2823

can you try this? Add the -max=0
    command: "volume -mserver=master:9333 -port=8080 -ip=volume -max=0"

can you try this? Add the -max=0

tried the error remained

Add the "-max=0", not "-max 0"

Add the "-max=0", not "-max 0"

did not help

I disable  multipart copy chunks on registry, size up to 1Gb
      REGISTRY_STORAGE_S3_MULTIPARTCOPYCHUNKSIZE: "1048576000"
      REGISTRY_STORAGE_S3_MULTIPARTCOPYTHRESHOLDSIZE: "1048576000"

https://docs.docker.com/registry/configuration/#list-of-configuration-options
then push worked
docker push <IP_ADDRESS>:5001/logstash:7.9.3
The push refers to repository [<IP_ADDRESS>:5001/logstash]
d531f1620717: Layer already exists
da29e51f4b5a: Layer already exists
e130db055e76: Layer already exists
d01d03eef5d2: Layer already exists
11689358ee84: Layer already exists
39d2e7f98e7d: Layer already exists
174f912d511e: Layer already exists
99de5206293b: Pushed
51ff5420b316: Layer already exists
2e0e4cba5ae9: Pushed
7.9.3: digest: sha256:cbd441b072dbd5271ecd02de560d7780594672321f90036c9ace1618be41f042 size: 2823

It seems to have something to do with determining the file size
Since for multipart copy chunks  registry sees layer size 290.2MB
99de5206293b: Pushing [============================================>      ]  259.9MB/290.2MB
but Pushing 301.9MB

Yes, I can reproduce. What was the previous chunk size? May need to test with a simpler case. Maybe using aws s3?

by default chuck size 32Mb
multipartcopychunksize: 33554432
multipartcopythresholdsize: 33554432
There were no problems with aws cli during the whole testing period

Found the problem. It was an error that the reader is closed too early with s3 UploadPartCopy.
Thanks for the detailed bug reporting!

I do not confirm that this fixes

can you apply the latest commits and show the logs?

can you apply the latest commits and show the logs?

I'm sorry, I double-checked everything works


create_thirdparty_resource should be an actual python file (.py)

This example: https://github.com/kubernetes-incubator/client-python/blob/master/examples/create_thirdparty_resource.md
should be a runnable python file.

@jonathan-kosgei do you have any update on this? The example is misleading people. If you have a working version and you can send a PR for that, that would be nice.


Change Stream Analytics job's blob storage output format to 'Array'

I would hardly recommend to store the data inside the blobs in the Array format. They are JSON objects and saving them line separated creates an invalid(!) JSON file. The correct JSON format would be comma separated and with square brackets around the full document. The 'Array' format does exactly that!

I understand the concern. However, the hadoop code to parse JSON arrays gets a little too complicated for our class to grasp. We will keep it as line separated for now. We'll consider changing the format to an array format during a later update. Thanks!


[REQUEST] Run DeepSpeed inference in C++

Is your feature request related to a problem? Please describe.
What is the best way to run DeepSpeed inference in C++?
Describe the solution you'd like
Documenting if it is already possible, maybe using TorchScript with custom ops. Otherwise provide a way to run the model in C++.
Describe alternatives you've considered
Using TorchScript  and adding the ops
Additional context
For prod environments we need to run the inference in C# but C++ binding is an acceptable solution

Closing this ticket for now! I will reopen this ticket when PyTorch 2.0 is released, and we start to adopt PyTorch 2.0 deployment software stack.

@arashb ping

@arashb ping


Allow anchors to be linked together

Hi, great work on raygui and rguilayout :+1:
I am wondering if there is a way to link an anchor to another anchor?
Thanks!

@FederAndInk Yeah, several users asked for it, unfortunately at the moment is not easy to implement this feature, considering how the code is structured. Maybe I'll review it for a future version.


ECM-73

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/ECM-73
Change description
Added a DynamicFixed list for Respondent Representative
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

resp_rep_name will need to stay due to existing cases. what will happen is we will show the list and whatever value is chosen from that, we can set that to resp_rep_name as well


Help dependencies switch over to new anndata backend

[x] Cell2location
[ ] ConstrastiveVI
[ ] scGen
[x] scArches

scArches will have no issues as it directly imports our models

scGen is already pinned to not break on our release, so we can make a PR at a later date.


Auto play not working

I'm trying to start the slider playing immediately, but i can't get it to work. I've tried with and without onFirstInit callback.
            var defaultData = {
            mode: 'horizontal',
            loop: true,

            slidesPerView: 2,
            roundLengths: true,
            autoPlay:2000,
            keyboardControl: true,
            onFirstInit:function(swiper)
            {
                swiper.startAutoplay();
            },
            onInit: function (swiper) {
                var num = ($(window).width() < 800) ? 2 : 4;
                swiper.params.slidesPerView = num;
            }
        };

Also, unrelated, I've noticed that onInit is fired on every window resize event. You might want to optionally debounce that.

I know this is old, but in case anyone else finds themselves here. Change "autoPlay" to "autoplay" in the parameters, and it should fix the issue.


Exclude std:: functions from fuzz introspector reports

C++ std::.. calls can be very noisy and likely aren't very useful to fuzzer developers. e.g. for leveldb: https://storage.googleapis.com/oss-fuzz-introspector/leveldb/inspector-report/20220316/calltree_view_0.html
@Navidem and I discussed this and thought that we should just exclude all of these from the calltree.
@DavidKorczynski @AdamKorcz WDYT?

We should also include known libc / other builtin functions. The fuzz blockers list on https://storage.googleapis.com/oss-fuzz-introspector/leveldb/inspector-report/20220316/fuzz_report.html also point to __clang_call_terminate and strlen as the largest blocked functions, which doesn't seem so useful.
On this note, what exactly is the definition of the "largest blocked function" ?

We have had a discussion about this as well. The same could be said about calls to free, abort, exit, malloc, calloc etc. In some calltrees these add up to 100+ and will just be noise. And option we considered was to add a button that would allow the user to hide/display these calls.

we should just exclude all of these from the calltree.

We actually have support for all this already:
https://github.com/ossf/fuzz-introspector/blob/808f2d4334f831bffce3388d0cbb92e1b6e275b7/post-processing/fuzz_html.py#L657-L663
There is a difference between when/where to include the data -- if we exclude only in the calltree then some analysis may seem wrong as it will be based on another instance of the calltree, i.e. in this case we should block undesired functions at the compiler level to discard it from any data processing -- or improve the data processing pipeline.
However, this problem is bigger than this. The main point is that inevitably users will want to "adjust the data analysed" by fuzz-introspector. The key thing is users may want to "refine the threat model, i.e. refining the source code they are interested in". For example, consider a project (such as Envoy) who builds all of their dependencies as part of the build. This is  going to explode with information that is not interesting to the Envoy developers as such.
For the more general problem, I have made this: https://github.com/ossf/fuzz-introspector/issues/35

On this note, what exactly is the definition of the "largest blocked function" ?

The function with largest cyclomatic complexity amongst all functions that are blocked

one thing about excluding callsites from the calltree is that it does remove transparency into the code under analysis. I wonder if it would make sense to also try and make them in some form of toned coloring to show they are "not so important". We can perhaps try both and see what works.

Fixed this one for new -- the solution is to cut off the functions early in the LLVM plugin so they never enter the analysis https://github.com/ossf/fuzz-introspector/pull/115
Long term I think it would make sense moving towards a direction where fuzz-introspector is purely focused on gathering a lot of data and offering analyses, but without being highly opinionated (i.e. removing data) on the exact parameters of the analyses etc but rather allowing the users themselves to choose. But that's many months from now.

Thanks for addressing this! Re long term making this configurable: completely agree, but we should still have an opinionated default that will work best for the majority of users.

Good show for the short term, but that option needs to be added - if nothing else, it documents a limitation of the default. I added an issue here for adding an option for more complete analysis: https://github.com/ossf/fuzz-introspector/issues/133


[BUG] Being rate-limited for reloading/loading/unloading a Cog

Describe the bug.
Almost whenever I reload, load, or unloading a cog, I'm being rate-limited for like 60 secs.
I assume you need to to put a small delay to avoid this
List the steps.
bot.reload(f"{folder}.{extension}")
What you expected.
To reload without issues
What you saw.
Instead, I received this traceback error given from my Python terminal:
The HTTP client has encountered a per-route ratelimit. Locking down future requests for 57.597 seconds.

What version of the library did you use?
release
Version specification
4.2.1
Code of Conduct

[X] I agree to follow the contribution requirements.

The unstable branch has an argument preventing the deletion of commands on cog removal

The unstable branch has an argument preventing the deletion of commands on cog removal

What is that supposed to mean? That I wouldn't constantly keep being rate-limited for reloading a cog?

The unstable branch has an argument preventing the deletion of commands on cog removal

What is that supposed to mean? That I wouldn't constantly keep being rate-limited for reloading a cog?

Yes, currently it removes all commands of the cog by default. On unstable you can specify remove_commands=False into reload or remove so it does not remove the commands


Use webRTC audio as inputs

Hi James, Just wondering if it is possible to use webRTC audio streams with your mixer somehow?
Thank you!

I think that would not be possible without complicating it because you would have to ensure the streams are in sync as they come in.

Hey, we are handling the syncing ourselves already. we just need a way to mix audio in the cloud.

Hi Michael, There seem to be some methods available in the Web Audio API which enable working with WebRTC (https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/webrtc-integration.html). Currently this mixer works by first buffering all of the audio tracks in the Daw class before initalising the Mixer class. You'd need to do a lot of refactoring in the Mixer clas to get this working with the code as it is. I'm think this is possible but I'd be starting from scratch if I were trying to achieve this.

Hi James! I see. we are looking for audio mixing in the cloud, and so far have not found anything solid. We don't really have time to do the development ourselves giving some time constraints. Thank you so much for responding here! I hope you and your family are safe in these crazy times.


fixed open_output return type for windows

Sorry for the delay, it's not like I forgot to merge it, I just wanted to do a proper review of the changes.


Output event hub partitionKey column

Add explicit description about setting partition key column in output event hub to enable proper partition topology.

@xindzhan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@xindzhan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Added macOS installation with brew documentation

Added macOS installation with brew documentation in README.md

@antonellof thanks!


Move TestClock in opencensus-testing package.

@bogdandrutu Are you planning to put the testing package in a testing library for users?

Codecov Report

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

@@             Coverage Diff             @@
##             master    #368      +/-   ##
===========================================
- Coverage     89.81%   89.7%   -0.11%
+ Complexity      572     563       -9
===========================================
  Files            94      93       -1
  Lines          2189    2167      -22
  Branches        176     176
===========================================
- Hits           1966    1944      -22
  Misses          183     183
  Partials         40      40

Impacted Files
Coverage Δ
Complexity Δ

...va/io/opencensus/trace/config/TraceConfigImpl.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

So this package will be released to maven central and will allow users to test the API using fake/tesing objects.


Crash caused by font even after recreating it

I get this crash even after I've deleted the font, cleared the projects cache, and recreated it.
Hopefully someone here can help.
Here's the font I'm using (px10 version in this case):
https://takwolf.itch.io/ark-pixel-font

There are 10 different .zip files with 7 font files apiece. Which font are you actually using?
Also, please send a .txt file containing your entire debug log as this contains extra information.

Closing due to inactivity.


Turn back on macOS shard Cirrus caching

Description
Revisiting https://github.com/flutter/flutter/pull/49585 in light of revent Cirrus network unstability on mac VMs.
Related Issues
Reverts part of https://github.com/flutter/flutter/pull/37880.
Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

No more dart SDK, pub, or artifacts download during setup.  Also reduces setup time from 3 minutes to 1:30 minutes.

Talked offline - I think the only way to address my concern that makes sense is to split readable and writable cache as Jenn is suggesting.  LGTM

Holding this until I get clarity from @fkorotkov about what seems to be cache corruption at https://cirrus-ci.com/task/6396945455382528?command=all_flutter#L17 that's causing cache misses.

Holding this until I get clarity from @fkorotkov about what seems to be cache corruption at https://cirrus-ci.com/task/6396945455382528?command=all_flutter#L17 that's causing cache misses.

https://github.com/cirruslabs/cirrus-ci-docs/issues/567