Can't make dxvk with ubuntu 18.04

I've got this output when i try to build dxvk by myself. I've installed MinGW64 from apt-get  and build glslangValidator by myself. Can some one help me?
The Meson build system
Version: 0.45.1
Source dir: /home/skif/Proton/dxvk
Build dir: /home/skif/Proton/dxvk/dxvk-master/build.64
Build type: cross build
Project name: dxvk
Native C compiler: cc (gcc 7.3.0 "cc (Ubuntu 7.3.0-16ubuntu3) 7.3.0")
Cross C compiler: x86_64-w64-mingw32-gcc (gcc 7.3.0)
Native C++ compiler: c++ (gcc 7.3.0 "c++ (Ubuntu 7.3.0-16ubuntu3) 7.3.0")
Cross C++ compiler: x86_64-w64-mingw32-g++ (gcc 7.3.0)
Host machine cpu family: x86_64
Host machine cpu: x86_64
Target machine cpu family: x86_64
Target machine cpu: x86_64
Build machine cpu family: x86_64
Build machine cpu: x86_64
Library vulkan-1 found: YES
Library d3d11 found: YES
Library dxgi found: YES
Library d3dcompiler_43 found: YES
Library d3dcompiler_47 found: YES
Program glslangValidator found: YES (/home/skif/glslang/build/install/bin/glslangValidator)
Dependency threads found: YES
Configuring setup_dxvk.sh using configuration
Build targets in project: 10
Found ninja-1.8.2 at /usr/bin/ninja
[5/178] Compiling C++ object<EMAIL_ADDRESS>FAILED<EMAIL_ADDRESS>x86_64-w64-mingw32-g++  -Isrc/util/util@sta -Isrc/util -I../../src/util -I../.././include -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++1z -O3 -DNOMINMAX -MD -MQ<EMAIL_ADDRESS>-MF<EMAIL_ADDRESS>-o<EMAIL_ADDRESS>-c ../../src/util/config/config.cpp
In file included from ../../src/util/config/config.cpp:7:0:
../../src/util/config/../log/log.h:50:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex    m_mutex;
          ^~~~~
[8/178] Compiling C++ object<EMAIL_ADDRESS>FAILED<EMAIL_ADDRESS>x86_64-w64-mingw32-g++  -Isrc/util/util@sta -Isrc/util -I../../src/util -I../.././include -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++1z -O3 -DNOMINMAX -MD -MQ<EMAIL_ADDRESS>-MF<EMAIL_ADDRESS>-o<EMAIL_ADDRESS>-c ../../src/util/log/log_debug.cpp
In file included from ../../src/util/log/log_debug.h:5:0,
                 from ../../src/util/log/log_debug.cpp:1:
../../src/util/log/log.h:50:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex    m_mutex;
          ^~~~~
[9/178] Compiling C++ object<EMAIL_ADDRESS>FAILED<EMAIL_ADDRESS>x86_64-w64-mingw32-g++  -Isrc/util/util@sta -Isrc/util -I../../src/util -I../.././include -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++1z -O3 -DNOMINMAX -MD -MQ<EMAIL_ADDRESS>-MF<EMAIL_ADDRESS>-o<EMAIL_ADDRESS>-c ../../src/util/log/log.cpp
In file included from ../../src/util/log/log.cpp:1:0:
../../src/util/log/log.h:50:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex    m_mutex;
          ^~~~~
../../src/util/log/log.cpp: In member function ‘void dxvk::Logger::emitMsg(dxvk::LogLevel, const string&)’:
../../src/util/log/log.cpp:49:28: error: ‘mutex’ is not a member of ‘std’
       std::lock_guard<std::mutex> lock(m_mutex);
                            ^~~~~
../../src/util/log/log.cpp:49:33: error: template argument 1 is invalid
       std::lock_guard<std::mutex> lock(m_mutex);
                                 ^
../../src/util/log/log.cpp:49:40: error: ‘m_mutex’ was not declared in this scope
       std::lock_guard<std::mutex> lock(m_mutex);
                                        ^~~~~~~
../../src/util/log/log.cpp:49:35: warning: unused variable ‘lock’ [-Wunused-variable]
       std::lock_guard<std::mutex> lock(m_mutex);
                                   ^~~~
[10/178] Compiling C++ object<EMAIL_ADDRESS>FAILED<EMAIL_ADDRESS>x86_64-w64-mingw32-g++  -Isrc/util/util@sta -Isrc/util -I../../src/util -I../.././include -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++1z -O3 -DNOMINMAX -MD -MQ<EMAIL_ADDRESS>-MF<EMAIL_ADDRESS>-o<EMAIL_ADDRESS>-c ../../src/util/com/com_guid.cpp
In file included from ../../src/util/com/../../d3d11/../dxgi/dxgi_include.h:14:0,
                 from ../../src/util/com/../../d3d11/d3d11_include.h:3,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:3,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxgi/../util/log/log.h:50:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex    m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_buffer_res.h:4:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_buffer.h:6,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:4,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_memory.h:259:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex                                      m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_framebuffer.h:4:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_constant_state.h:4,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:6,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_renderpass.h:206:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex                      m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_query_pool.h:5:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_query_tracker.h:3,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_cmdlist.h:12,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_barrier.h:4,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_context.h:3,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:7,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_query.h:191:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_graphics.h:8:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_context_state.h:7,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_context.h:6,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:7,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_pipecompiler.h:49:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex                  m_compilerLock;
          ^~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_pipecompiler.h:50:10: error: ‘condition_variable’ in namespace ‘std’ does not name a type
     std::condition_variable     m_compilerCond;
          ^~~~~~~~~~~~~~~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_context.h:10:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:7,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_meta_mipgen.h:194:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_context.h:11:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:7,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_meta_resolve.h:105:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_context.h:13:0,
                 from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:7,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_pipemanager.h:104:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex m_mutex;
          ^~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:16:0,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_queue.h:55:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex              m_mutex;
          ^~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_queue.h:56:10: error: ‘condition_variable’ in namespace ‘std’ does not name a type
     std::condition_variable m_condOnAdd;
          ^~~~~~~~~~~~~~~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_queue.h:57:10: error: ‘condition_variable’ in namespace ‘std’ does not name a type
     std::condition_variable m_condOnTake;
          ^~~~~~~~~~~~~~~~~~
In file included from ../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:18:0,
                 from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:57:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex           m_mutex;
          ^~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h: In member function ‘dxvk::Rc<T> dxvk::DxvkRecycler<T, N>::retrieveObject()’:
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:32:28: error: ‘mutex’ is not a member of ‘std’
       std::lock_guard<std::mutex> lock(m_mutex);
                            ^~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:32:33: error: template argument 1 is invalid
       std::lock_guard<std::mutex> lock(m_mutex);
                                 ^
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:32:40: error: ‘m_mutex’ was not declared in this scope
       std::lock_guard<std::mutex> lock(m_mutex);
                                        ^~~~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h: In member function ‘void dxvk::DxvkRecycler<T, N>::returnObject(const dxvk::Rc<T>&)’:
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:49:28: error: ‘mutex’ is not a member of ‘std’
       std::lock_guard<std::mutex> lock(m_mutex);
                            ^~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:49:33: error: template argument 1 is invalid
       std::lock_guard<std::mutex> lock(m_mutex);
                                 ^
../../src/util/com/../../d3d11/../dxvk/dxvk_recycler.h:49:40: error: ‘m_mutex’ was not declared in this scope
       std::lock_guard<std::mutex> lock(m_mutex);
                                        ^~~~~~~
In file included from ../../src/util/com/../../d3d11/d3d11_interfaces.h:7:0,
                 from ../../src/util/com/com_guid.cpp:3:
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h: At global scope:
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:404:10: error: ‘mutex’ in namespace ‘std’ does not name a type
     std::mutex                  m_submissionLock;
          ^~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h: In member function ‘void dxvk::DxvkDevice::lockSubmission()’:
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:347:7: error: ‘m_submissionLock’ was not declared in this scope
       m_submissionLock.lock();
       ^~~~~~~~~~~~~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:347:7: note: suggested alternative: ‘m_submissionQueue’
       m_submissionLock.lock();
       ^~~~~~~~~~~~~~~~
       m_submissionQueue
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h: In member function ‘void dxvk::DxvkDevice::unlockSubmission()’:
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:357:7: error: ‘m_submissionLock’ was not declared in this scope
       m_submissionLock.unlock();
       ^~~~~~~~~~~~~~~~
../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:357:7: note: suggested alternative: ‘m_submissionQueue’
       m_submissionLock.unlock();
       ^~~~~~~~~~~~~~~~
       m_submissionQueue
ninja: build stopped: subcommand failed.
cp: cannot stat '/home/skif/Proton/dxvk/dxvk-master/install.64/bin/d3d10.dll': No such file or directory
cp: cannot stat '/home/skif/Proton/dxvk/dxvk-master/install.64/bin/d3d10_1.dll': No such file or directory
cp: cannot stat '/home/skif/Proton/dxvk/dxvk-master/install.64/bin/d3d10core.dll': No such file or directory
cp: cannot stat '/home/skif/Proton/dxvk/dxvk-master/install.64/bin/d3d11.dll': No such file or directory
cp: cannot stat '/home/skif/Proton/dxvk/dxvk-master/install.64/bin/dxgi.dll': No such file or directory
rm: cannot remove '/home/skif/Proton/dxvk/dxvk-master/wine.64': No such file or directory
rm: cannot remove '/home/skif/Proton/dxvk/dxvk-master/install.64': No such file or directory

Described on the wiki: https://github.com/doitsujin/dxvk/wiki/Common-issues
Solution/copy-paste:
update-alternatives --config x86_64-w64-mingw32-gcc
update-alternatives --config x86_64-w64-mingw32-g++

You could also try building it as a winelib, that way you don't need a crosscompiler, but the winelib build is broken right now (https://github.com/doitsujin/dxvk/issues/651)

@illiaSkif  look here: https://github.com/doitsujin/dxvk/issues/532

See comments above.


⚠ WSINGRESOS - OXXO has degraded performance

In d5b4e4b, WSINGRESOS - OXXO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/compartido/wspagosoxxo.r) experienced degraded performance:

HTTP code: 200
Response time: 21708 ms

Resolved: WSINGRESOS - OXXO performance has improved in c4586ce after 9 minutes.


[Do not merge] Add product dropdown to nav menus

Removes forum from mobile and desktop navigation in favor of new product dropdown that's being added to the hugo site for the product launch.
@jess-edwards @jseldess

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/483b38319eb18c5e500cfc4c7cdd227dab6a0330/

@jseldess & @deronjohnson
The Nav item order should be:
FAQ, PRODUCT, DOCS, COMMUNITY, ABOUT, BLOG
The product descriptions in the nav dropdown should be:
CockroachDB Core
A cloud-native SQL database designed to grow with you.
CockroachDB Enterprise
A cloud-native SQL database built for global businesses.
When you're on a page, that nav item should stay highlighted in green (as an indicator that you are on DOCS, for example).

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e6b090fa9728a7c7149f5eadb7d656a324e459da/

LGTM @deronjohnson & @jseldess
cc: @kuanluo

LGTM as well!


[connectivity_plus] Remove unused IPHelper file

Description
IPHelper.h is being used in the (now deprecated) flutter/plugins/connectivity repo, but not in this plus_plugins repo. We can re-add it when needed.
Related Issues
None.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Not sure the macos-latest test is cancelling for a good reason or not. Anyone know?

I just updated main branch can you please  update with main

Thanks looks good one more favor,
Can you please add a changelog and pump version of the package?
thank you

Not sure the macos-latest test is cancelling for a good reason or not. Anyone know?

passing now


docs: Replace the confusing word with official defination

Replace the confusing word with official defination
Signed-off-by: Le Yao<EMAIL_ADDRESS>Commit Message: Replace the confusing word with official defination
Additional Description: In the proto and doc comments, sometimes it is HTTP Alrernate Services, and sometimes it is HTTP Alternative Services. And the official defination is  HTTP Alternative Services, so replace it to make it more clear.
Risk Level: Low
Testing: N/A
Docs Changes: Yes
Release Notes: N/A
Platform Specific Features: N/A
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

/assign-from @envoyproxy/api-shepherds


Remove abandoned pymbar-datasets code

This PR removes any code associated with the now-abandoned http://github.com/choderalab/pymbar-datasets, as it was untested and broken.
If someone cares enough to make this work, they can restore the code on the conditions that:

The code works
The code is tested
These tests run as part of the nightly tests to ensure it doesn't stop working at some point

I disagree with throwing out use cases that 1) are part of how other people actually use MBAR for publications and 2) helped us find problems with MBAR.
HOW to best save such examples is a good question that deserves discussion.

This code simply does not work now. The pytables code doesn't even work with the current pytables API. We have to purge it.
If you'd like to add back a working version that is sustainable---that is, included in continuous integration---at some point in the future, you are more than welcome to. But we CANNOT keep broken, untested code in the main development repository.

The code isn't going way---it will be easy to find if you have the time to resurrect it.

This code simply does not work now. The pytables code doesn't even work with the current pytables API. We have to purge it.

Sounds like Kyle broke it in the process of trying to update it to run CI.  It worked fine manually before (I.e. read the README, and run).
We need to have a good way of distributing reference examples, since what other people do with MBAR is extremely valuable.
In terms of CI, it should be REALLY simple.  For each example, when the code is updated, does it still give the same answer as it did before? That should be it.

We need to have a good way of distributing reference examples, since what other people do with MBAR is extremely valuable.

I think these other issues are good things to discuss next week.

Well, it's not really my code.  It's collaborators code that we found very useful to have, because it broke MBAR.
Discussing how to handle these sounds good.  I think the right way to handle this important, because it would be great to archive how other people are using it, without expecting that we have to make all of their work best-practices.
I agree that fixing these things are a priority.  But we do need to schedule times fix things -- I can't necessarily find the time on new years eve when my brother and his children are here. . .

What we need is an agreed-upon set of standards for collaborative code development. If we stick to that, we'll make sure I don't have to be fixing someone else's broken code on New Year's Eve.

We've started to collect some guidelines here:
https://github.com/choderalab/software-development
I'll make sure to update it to prevent this situation from reoccurring.


Livewire auto-discovery.

Added livewire auto-discovery support.
You need to create the Livewire folder within the src/Http folder
Just an example of how to render the view for the component is the same namespace "schema" as returning views in regular controllers.
class ExampleLivewireComponent extends Component
{

    public function render()
    {
        return view('$moduleName::livewire.example');
    }
}

The "bootLivewireComponents()" commit was accidental ..... Sorry about that.

This looks good. Once #22 is merged in, can you update this to match that style (using moduleForPathOrFail() and catching DirectoryNotFoundException explicitly)? Also, would it be possible to add a simple test or two? We can potentially install Livewire as part of the Github Action workflow, and you can just have the test run conditionally if Livewire is installed.

I've updated the files now to match moduleForPathOrFail() and DirectoryNotFoundException()
But I need some help to figure out how to test it, my pitfall was that in the test I want to make:livewire so I can verify that the module is registered. Tried to make a new Command and extend it to livewires own make command in the ModularizedCommandsServiceProvider.php but I cant get it to register...

Updated for auto discovery with the new methods

I just pushed up a PHP CS Fixer config. Can you run ./vendor/bin/php-cs-fixer fix src on this PR?

Actually, I just ran it myself.

It looks like Livewire hard-codes app()->getNamespace() and app('path'), so I don't see how this will work without either a PR to Livewire to fix that, or extending the ComponentParser as well.

I took a little stab at implementing a test. You just have to install Livewire locally to run the test (we can add this to the CI steps so that it tests them in CI, but doesn't mark Livewire as a dependency). Maybe you can use that as a starting point.
But generally, ComponentParser::generatePathFromNamespace looks to be the next problem to overcome.

Any plans on picking this back up? Or should I close it for now?

It actually looks like https://github.com/livewire/livewire/pull/2505 resolves some of those issues, so it may be easier to get this working now!

I added the test for nested components, think its all clear now?

Are we ready to merge this? :)


Update Python to 3.11.0b4 in emscripten test

Try to fix emscripten test failure.

Well the test failure on the main branch seems to be because search_lib_dir is failing to find sysconfigdata. I'm not sure why that started happening, the first commit where the problem occurs looks pretty unrelated. The memory error looks more confusing, is there any way you could make it print the traceback? I'm pretty busy today but I can spend some time looking into this over the weekend if you don't figure it out before then.

Traceback:
---- exceptions::asyncio::tests::CancelledError stdout ----
thread 'main' panicked at 'Can not import module asyncio: Traceback (most recent call last):
  File "/lib/python3.11/asyncio/__init__.py", line 8, in <module>
    from .base_events import *
  File "/lib/python3.11/asyncio/base_events.py", line 45, in <module>
    from . import staggered
  File "/lib/python3.11/asyncio/staggered.py", line 6, in <module>
    import typing
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 936, in exec_module
  File "<frozen importlib._bootstrap_external>", line 1083, in get_code
  File "<frozen importlib._bootstrap_external>", line 746, in _code_to_timestamp_pyc
', src/exceptions.rs:698:5

Looks pretty weird...

@messense does this repro if you just import typing? I ask because that's the module in the traceback which it looks like the import is attempting when this fails.
Code raising the error is here:
https://github.com/python/cpython/blob/5a7e1e0a92622c605ab28c95b3dd61a21d285ad5/Lib/importlib/_bootstrap_external.py#L746
Looks like it's trying to serialise the module source to a bytearray. Running out of memory or exceeding a page size or something? Either in marshal.dumps or bytearray.extend. @hoodmane maybe you have an idea how wasm memory constraints might affect this?

does this repro if you just import typing?

Same MemoryError:
---- exceptions::tests::test_import_typing stdout ----
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: PyErr { type: <class 'MemoryError'>, value: MemoryError(), traceback: None }', src/exceptions.rs:749:47

There might be a linker flagthat will fix it. In Pyodide we pass a couple relevant flags:
https://github.com/pyodide/pyodide/blob/ebea82caffa6d05d6c56da764ac388ec9726d1dc/Makefile.envs#L106

There might be a linker flagthat will fix it. In Pyodide we pass a couple relevant flags: https://github.com/pyodide/pyodide/blob/ebea82caffa6d05d6c56da764ac388ec9726d1dc/Makefile.envs#L106

ALLOW_MEMORY_GROWTH=1 worked like a charm!


Unable to detect the kernel-plus version

Running the binary 'centos2alma' it returns 'Do preparation checks...' and it is the verbose log:
2024-02-06 14:32:38,096 - DEBUG - Start checks
2024-02-06 14:32:38,097 - DEBUG - Make check checking if distro is CentOS7
2024-02-06 14:32:38,097 - DEBUG - Make check checking if Plesk version is actual
2024-02-06 14:32:38,104 - DEBUG - Make check checking if Plesk installer is in progress
2024-02-06 14:32:38,116 - DEBUG - Make check checking available space
2024-02-06 14:32:38,116 - DEBUG - Make check checking outdated PHP
2024-02-06 14:32:38,425 - DEBUG - Make check checking domains uses outdated PHP
2024-02-06 14:32:38,436 - DEBUG - Make check checking cronjob uses outdated PHP
2024-02-06 14:32:38,446 - DEBUG - Make check checking if grub is installed
2024-02-06 14:32:38,446 - DEBUG - Make check checking if there is more than one NIC interface using ketnel-name
2024-02-06 14:32:38,446 - DEBUG - Make check checking if the system not in a container
2024-02-06 14:32:38,447 - DEBUG - Make check checking if the last installed kernel is in use
2024-02-06 14:32:40,373 - DEBUG - Installed kernel versions:
2024-02-06 14:32:40,374 - ERROR - max() arg is an empty sequence

the max() function is returning an empty sequence. Is a python error that means the expected value is null and it's unable to continue.

Please show the results of the rpm -qa kernel* command.

Currently kernel-plus isn't supported, though probably it should work. We will check.

Thanks for the confirmation. We'll wait an update to do that migration using kernel-plus. Let me know if I can help with anything.

The problem should be fixed in #172. Please find attached archive with related version of centos2alma -
centos2alma.zip.

Hello @SandakovMM, I have tested this build and can't confirm that it's not working. The behavior was the same, just returned "Do preparation checks..." and stopped.
Additionally, I've looked at your PR, and it does not include the string for 'kernel-plus', only 'kernel-rt', is that alright?
Let me know if I can help with something else. Thanks.

Additionally, I've looked at your PR, and it does not include the string for 'kernel-plus', only 'kernel-rt', is that alright?

You right, we should also mention them when collecting packages list. I've added the fix in #175.
Attaching new centos2alma.zip as well.

Tested using the last build works fine in kernel plus. It looks like solved.

Yes, after this build is solved, I'm closing this issue. Thanks.


closure-make-deps generates incorrect paths on Windows.

To Reproduce

Create working directory (e.g. C:\work\test).
Change directory (e.g. cd C:\\work\\test).
Clone closure-library (e.g. git clone https://github.com/google/closure-library.git).
Change directory (e.g. cd closure-library).
Install npm package (e.g. npm install).

Following the above steps will generate closure/goog/deps.js.
When you open deps.js, it has the following contents.
goog.addDependency('../C:\work\test\closure-library\closure\goog\a11y\aria\announcer.js', ['goog.a11y.aria.Announcer'], ['goog.Disposable', 'goog.Timer', 'goog.a11y.aria', 'goog.a11y.aria.LivePriority', 'goog.a11y.aria.State', 'goog.dom', 'goog.dom.TagName', 'goog.object', 'goog.string'], {'lang': 'es6'});
goog.addDependency('../C:\work\test\closure-library\closure\goog\a11y\aria\aria.js', ['goog.a11y.aria'], ['goog.a11y.aria.Role', 'goog.a11y.aria.State', 'goog.a11y.aria.datatables', 'goog.array', 'goog.asserts', 'goog.dom', 'goog.dom.TagName', 'goog.object', 'goog.string']);

Expected behavior
The following content will be generated.
goog.addDependency('a11y/aria/announcer.js', ['goog.a11y.aria.Announcer'], ['goog.Disposable', 'goog.Timer', 'goog.a11y.aria', 'goog.a11y.aria.LivePriority', 'goog.a11y.aria.State', 'goog.dom', 'goog.dom.TagName', 'goog.object', 'goog.string'], {'lang': 'es6'});
goog.addDependency('a11y/aria/aria.js', ['goog.a11y.aria'], ['goog.a11y.aria.Role', 'goog.a11y.aria.State', 'goog.a11y.aria.datatables', 'goog.array', 'goog.asserts', 'goog.dom', 'goog.dom.TagName', 'goog.object', 'goog.string']);

I have a solution and I am preparing for PR.

Can this be considered closed now that the PR has been merged?  Or does this project only close issues when a release is completed?

For anyone else on this issue looking for a solution before the next release is published, this is how you use a pre-release version at the SHA1 where this issue was fixed: https://github.com/shaka-project/shaka-player/pull/4086/files

We usually try to set it up so that merging the PR auto-closes the issue.  I guess that didn't happen here.


Add validation feature for patterns only

This adds a simple validation mode that checks the provided pattern is valid JSON Schema; this isn't perfect but it gives us some guarantees.
Addresses issue #73 and #317

This is a good first cut, but I think we can improve upon this later  - e.g. running with -v shows loads of 'strict mode' errors that could be useful here:
debug:   Pattern Instantiation was not provided, only the JSON Schema will be validated
strict mode: unknown keyword: "defs"
strict mode: unknown keyword: "defs"
strict mode: required property "deployed-in" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/0" (strictRequired)
strict mode: required property "composed-of" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/1" (strictRequired)
strict mode: required property "interacts" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/2" (strictRequired)
strict mode: required property "connects" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/3" (strictRequired)
strict mode: "prefixItems" is 4-tuple, but minItems or maxItems/items are not specified or different at path "#/properties/nodes"
strict mode: missing type "object" for keyword "required" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/nodes/prefixItems/0" (strictTypes)
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/nodes/prefixItems/0" (strictTypes)
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/nodes/prefixItems/1" (strictTypes)
strict mode: missing type "object" for keyword "required" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/nodes/prefixItems/2" (strictTypes)
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/nodes/prefixItems/2" (strictTypes)
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/nodes/prefixItems/3" (strictTypes)
strict mode: "prefixItems" is 3-tuple, but minItems or maxItems/items are not specified or different at path "#/properties/relationships"
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/relationships/prefixItems/0" (strictTypes)
strict mode: required property "deployed-in" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/0" (strictRequired)
strict mode: required property "composed-of" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/1" (strictRequired)
strict mode: required property "interacts" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/2" (strictRequired)
strict mode: required property "connects" is not defined at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/draft/2024-04/meta/core.json#/properties/relationship-type/oneOf/3" (strictRequired)
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/relationships/prefixItems/1" (strictTypes)
strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/finos/architecture-as-code/main/calm/pattern/api-gateway#/properties/relationships/prefixItems/2" (strictTypes)
info:    The JSON Schema is valid


generateChangelog optionally creates runOnChange=true and replaceIfExists=true for createView changes

Closes #4634
Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[x] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR introduces two new options:

--run-on-change-types=createView,createProcedure will set runOnChange="true" for each changeSet which contains solely createView and createProcedure changes. For backwards compatibility, the default is an empty list.
--replace-if-exists=createView,createProcedure will set replaceIfExists="true" for each createView and createProcedure change. For backwards compatibility, the default is an empty list.

Things to be aware of
N/A
Things to worry about
N/A
Additional Context
N/A

Converted to draft to further improve this PR.

Hi @mkarg,
I left two review comments (one it's a very minor thing, though). Could you please look at them?
I was planning to add some integration test to do something like this:
def "Ensure generate changelog set runOnChange and replaceIfExists properties correctly"() {
        given:
        CommandUtil.runUpdate(mysql,"src/test/resources/changelogs/mysql/complete/view.procedure.changelog.xml")

        CommandScope commandScope = new CommandScope(GenerateChangelogCommandStep.COMMAND_NAME)
        commandScope.addArgumentValue(DbUrlConnectionCommandStep.URL_ARG, mysql.getConnectionUrl())
        commandScope.addArgumentValue(DbUrlConnectionCommandStep.USERNAME_ARG, mysql.getUsername())
        commandScope.addArgumentValue(DbUrlConnectionCommandStep.PASSWORD_ARG, mysql.getPassword())
        commandScope.addArgumentValue(GenerateChangelogCommandStep.REPLACEIFEXISTS_TYPES_ARG, "createView")
        commandScope.addArgumentValue(GenerateChangelogCommandStep.RUNONCHANGE_TYPES_ARG, "createView")

        OutputStream outputStream = new ByteArrayOutputStream()
        commandScope.setOutput(outputStream)

        when:
        commandScope.execute()

        then:
        def outputContent = outputStream.toString();
        outputContent.contains(" runOnChange=\"true\">")
        outputContent.contains(" replaceIfExists=\"true\"")

        cleanup:
        CommandUtil.runDropAll(mysql)
}

for which probably better to use String.matches() and use a regular expression to look for the runOnChange on the changeset tag and replaceIfExists in the createView (or createProcedure) tag.

@MalloD12 I am PTO this week and look into this next week.

Hi @mkarg,
Have you had a chance to look at my comments?
Thanks,
Daniel.

Sorry this week was booked out. Will try to find time for it next week.

Moving this PR to "In Discussion" column until we can resolve the above discussion.

I left two review comments (one it's a very minor thing, though). Could you please look at them?

Thank you for your patience and for reporting my faults. I fixed all of them (so I hope). :-)

I was planning to add some integration test to do something like this:

Nice, thank you! :-)

for which probably better to use String.matches() and use a regular expression to look for the runOnChange on the changeset tag and replaceIfExists in the createView (or createProcedure) tag.

I have no strong feeling about that, but sometimes simpler is better (easier to read).

Moving this PR to "In Discussion" column until we can resolve the above discussion.

IMHO discussion is resolved now.

@mkarg FYI I have updated your code a bit as requested to extend the behavior you added here also for Diff-Changelog command (which's similar to generate-changelog). If you have any objection/concerns please let me know.
@filipelautert could you please review this PR again when you have a chance?
@rberezen it's ready for you to test when you have a chance.
Thanks,
Daniel.

@mkarg FYI I have updated your code a bit as requested to extend the behavior you added here also for Diff-Changelog command (which's similar to generate-changelog). If you have any objection/concerns please let me know.

As long as it does not delay the integration of this PR any further I do not have any objections.

I've manually tested this PR, using both --replace-if-exists-types=createView,createProcedure and --run-on-change-types=createView,createProcedure and all combinations of the following:

Database

PostgreSQL
MySQL
DB2
Oracle

Changelog file type

xml
yml
sql
json

Command

generate-changelog
diff-changelog

The point of this was to try being as thorough as possible, with some of the most widely used databases.
Here are the results:
It works as expected for file types xml, yml and json, for all 4 tested databases and both commands.
There are some problems with the sql files for all 4 databases. I'll specify them below.
All databases
None of the changesets are decorated with runOnChange=true, both for generate-changelog and for diff-changelog
PostgreSQL, Oracle, MySQL
The create procedure changesets are created as follows (with the correct SQL syntax for each database):
-- changeset tfernandez:1702560678224-5 splitStatements:true
DROP PROCEDURE IF EXISTS "procedure1";
CREATE OR REPLACE PROCEDURE public.procedure1()
 LANGUAGE plpgsql
AS $procedure$
	BEGIN
		insert into public.entities (id, name) values (1, 'two');
	END;
$procedure$;

The statement DROP PROCEDURE IF EXISTS shouldn't be there. This is true when running either command.
Oracle
Running generate-changelog generates the CREATE VIEW changeset as CREATE OR REPLACE FORCE VIEW "NEWVIEW" ("A") AS SELECT 1 AS A FROM DUAL;.
Running diff-changelog generates it as CREATE OR REPLACE FORCE VIEW NEWVIEW (A) AS SELECT 1 AS A FROM DUAL;.
Note that one uses quotes for the view name and the other one doesn't. Both statements are correct, but this behaviour should be consistent.
PostgreSQL
The CREATE VIEW changesets are generated as follows:
DROP VIEW IF EXISTS "newview";
CREATE VIEW "newview" AS SELECT id,  name
   FROM entities;

The DROP VIEW IF EXISTS statement shouldn't be there. This happens when running either command.

That's all I found. Let me know if there is anything else I can help with.

@MalloD12 can you review @tati-qalified comments? thanks!

Thanks @tati-qalified for your very detailed testing. I think these "issues"/inconsistencies are not because of these changes.  For example, in the case of runOnChange property looking into CreateViewGenerator or CreateProcedureGenerator we can see none of them have support for runOnChangeand I think that's why we don't see it when generating a SQL output.
Regarding the "drop procedure" statement you are right it shouldn't be there, but again this is an existent piece in the code I would recommend similarly to the previous finding to deal with in a separate issue.
I think the same applies to the other findings.
Again, I would recommend dealing with each of these findings separately, so we don't keep this ticket on hold more time since these findings haven't been introduced with this PR.
What do you think @filipelautert - @rberezen - @tati-qalified?
Thanks,
Daniel.

@MalloD12, I agree with you on creating a separate issue for the problems described

Sounds good to me

@MalloD12 could you fix the conflicts?
@rberezen could you please finish the review?

@MalloD12 could you fix the conflicts? @rberezen could you please finish the review?

@filipelautert done!

Internal documentation ticket: https://datical.atlassian.net/browse/PD-4098


GetMarketSymbolsMetadata for Bitstamp

@superhappychris can you review?

@vslee looks good to me!

Great, thanks for looking


Expand markdown tables to full width

We want tables generated via markdown to expand to the full width of their container, otherwise we get squished-looking tables like on the icon page:

However, we can't just .m-variation table { width: 100% } because it will affect our non markdown tables like the ones on the table page.
Can we have jekyll apply a class to markdown tables when it generates the HTML pages?

It's possible to add a custom class to a Markdown table in Jekyll. See this gist for an example, using Kramdown. Would this be an acceptable solution?

It's possible to add a custom class to a Markdown table in Jekyll. See this gist for an example, using Kramdown. Would this be an acceptable solution?

It looks like this was attempted. The Markdown contains {: class="icon-table"} markup after each table, but the class isn't being applied.

It looks like this was attempted. The Markdown contains {: class="icon-table"} markup after each table, but the class isn't being applied.


Web UI doesn't start after updating

After updating Home Assistant from 0.80.3 to 0.81.6 UI doesn't start. In the log file I get this error:
2018-11-04 15:54:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1713803312] Received invalid command: get_panels
2018-11-04 15:54:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1713803312] Received invalid command: frontend/get_themes
2018-11-04 15:54:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1713803312] Received invalid command: auth/current_user
2018-11-04 15:54:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1713803312] Received invalid command: frontend/get_translations
2018-11-04 15:54:06 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_protocol.py", line 390, in start
    resp = await self._request_handler(request)
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_app.py", line 366, in _handle
    resp = await handler(request)
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_middlewares.py", line 106, in impl
    return await handler(request)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/static.py", line 68, in staticresource_middleware
    fingerprinted = _FINGERPRINT.match(request.match_info['filename'])
KeyError: 'filename'

Automation seems to be working fine. Home Assistant is running on RPi (Raspbian).

Further investigations showed these in the log:
2018-11-04 16:33:05 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Invalid config.
2018-11-04 16:33:08 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend
2018-11-04 16:33:08 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: Could not set up all dependencies.

In the configuration.conf with frontend I have only one option:
frontend:
  themes: !include_dir_named themes/

After commenting out themes everything works fine. Apparently some themes are broken or something. They didn't work for me before so I'm ok without the themes. Thanks anyway.

Same here, I updated from 0.76 to 0.81.6 the UI comes up on first boot.
I added the mqtt option in my config file without any switches, check config file and then tried to reboot but no luck.
this is my log:
2018-11-05 01:50:15 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError('0 bytes read on a total of 1 expected bytes',) 2018-11-05 01:50:15 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError('0 bytes read on a total of 1 expected bytes',) 2018-11-05 01:50:15 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.shutdown callback) OSError: [Errno 107] Socket not connected 2018-11-05 01:50:15 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.shutdown callback) OSError: [Errno 107] Socket not connected 2018-11-05 01:50:15 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.shutdown callback) OSError: [Errno 107] Socket not connected 2018-11-05 01:50:43 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError('0 bytes read on a total of 1 expected bytes',) 2018-11-05 01:50:43 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError('0 bytes read on a total of 1 expected bytes',) 2018-11-05 01:50:43 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError('0 bytes read on a total of 1 expected bytes',)

My problem started after i upgraded mosquitto addon to V3 and HA to 0.81.6.
not sure which part broke my system but i'm leaning towards the mosquitto addon.
This is how i was able to get my devices up and running.

I rolled HA back to 0.81.2
deleted the existing mqtt: from configuration.yaml
created a new user in configurations users.
entered that user info in the mosquitto ddon settings
configured mqtt from the list of new integrations
entered core-mosquitto as my broker, i believe you could use your pi's IP address
entered username and password used in the new user and mosquitto addon
Ticked the discovery box, i believe you could leave that unchecked
Restarted home assistant.

also make sure your supervisor is updated to V139
Initially i wanted to use the build in mosquitto, so I uninstalled the mosquitto add on and used the built in by simply adding mqtt: and password in the configuration.yaml file. my system was stuck in a boot loop, i believe that's related to the built in mqtt memory leak. So i switched back to a different mqtt broker.
This discussion helped me fix my problem
https://community.home-assistant.io/t/mosquito-mqtt-update-v3-broke-my-hassio/76991/61
Hope this helps

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

Hi, no issue resolved some time back. New issue on 0.90 though with KNX thermostats, I’ve looked at the release notes and the updated documentation, but it’s still a bit confusing. I need somehow to relate the descriptions to the true KNX definitions.
My Thermostats are Gira Touch Sensor 3+


Two App Bundles are produced when downloading Catalina 10.15.7_19H15

:beetle: Description
I recently tried to download the Catalina app for installation on an older computer but noticed that two app bundles get produced.  The first is macOS Catalina 10.15.7_19H15.app, downloaded to where I specified.  The second is macOS Catalina.app, located in the Applications folder with a prohibited symbol.
:clipboard: Steps to Reproduce

Open Mist.app
Click on download macOS Catalina 10.15.7 (19H15)
Click Continue on the compatibility warning
Keep default export type as Application and select the Downloads folder

:white_check_mark: Expected Behaviour
I was expecting one .app file like when downloading from the App Store.
:computer: Environment

Mist version (App menu ⇨ About Mist): 0.20
macOS Version (sw_vers): 13.6.7
Hardware (system_profiler SPHardwareDataType):

Model Identifier: Mac14,9
Chip : M2 Pro

:camera: Screenshots

If applicable, add screenshots to help explain the bug.
Create boot disk process automatically stops:

@A00736470 thanks for raising this issue, it appears to be the same issue as https://github.com/ninxsoft/Mist/issues/138
Good news is, it's a simple fix: https://github.com/ninxsoft/Mist/pull/145


Open Street Map has No Boundaries for scrolling.

Affected hardware version
Bangle 2
Your firmware version
2v12
The bug
In open street map you can scroll off the edge of the map. It is an issue because if you scroll too far off the edge of the map you can lose where the map is and can’t get back to it.

I think you can just press the button or tap to re-centre?
The idea was at some point you'd be able to upload more than one mapping area (which I guess could overlap) so maybe while clipping makes sense now, when that happens it may be something we don't want

Oh, ok Thanks I did not realize you could do that!


Adversarial Learning Tutorial Additions

Zoey and I are partners working on a project to help improve NSL documentation (specifically this tutorial).
I noticed in online communities and from personal experience, while the corresponding Youtube videos verbally explain concepts well for beginners, the recommended interactive collabs were a bit difficult to follow for beginners. That's why I wanted to better connect the video content with the collab content thus I created a recap section for beginners that includes all the concepts explained in the Youtube video. Also for some, they may prefer reading content over watching, some may also just want to have a written reference integrated into the collab tutorial.

@googlebot I signed it!

Thanks for the interest and great summary from the video.
@angela-wang1 could you remove the files in .vs/ in this PR?

I just removed the vs files and also inserted fenced code blocks instead

Thanks, @angela-wang1! The updated version looks good. I will merge this PR shorty.


registering as contributor

Hi folks,
I work at SAP and would like to make some contributions to the cf-java-client lib.

Rado started with the following contributions:

https://github.com/cloudfoundry/cf-java-client/issues/1160
https://github.com/cloudfoundry/cf-java-client/pull/1185 - a substantial contribution to support security groups using CF API v3

The requirements listed in rfc-0008-role-change-process.md are fulfilled so I merge the PR.
Welcome @radoslav-tomov  as new Cloud Foundry contributor.


docker 交叉编译规则更新

这个 PR 实现什么功能/修复什么问题:

docker 交叉编译规则更新

是否需要 backport 到之前的 release 分支:

NONE

Codecov Report

Merging #8849 (e084421) into master (d3b892d) will increase coverage by 1.89%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #8849      +/-   ##
=========================================
+ Coverage    5.92%   7.81%   +1.89%
=========================================
  Files         817     252     -565
  Lines      127584   33643   -93941
=========================================
- Hits         7553    2628    -4925
+ Misses     119353   30746   -88607
+ Partials      678     269     -409

Flag
Coverage Δ

aFlag
7.81% <ø> (+1.89%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/hostnetworks.go

pkg/apis/list.go

pkg/mcclient/options/dnsrecords.go

pkg/keystone/models/users.go

pkg/cloudcommon/validators/validators_actor.go

pkg/appsrv/send.go

pkg/cloudcommon/db/quotas/quotakeys.go

pkg/compute/models/loadbalancerawscachedlbbg.go

pkg/hostman/system_service/fluentbit.go

pkg/compute/models/managedresource.go

... and 555 more

Continue to review full report at Codecov.

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

/lgtm
/approve


chore: Lt hashmap refactoring

Changes

Removed algo::Error
Refactored computers LT HashMap into: u64 => u64 => f32
Refactored verifiers LT HashMap into: u64 => u64 => f32

Reminders

[x] Add a prefix to PR: feat: (for features), chore: (for chores/refactoring), fix: (for bug fixes), or any from: https://www.conventionalcommits.org/en/v1.0.0/#summary
[x] Assign reviewers
[x] Link related issues
[x] Make it draft if it is still WIP
[x] Write unit tests for your code if possible
[x] Do manual testing and make sure your changes don't break the rest of the codebase

Ah, sorry.
Pls disregard my question above. @lazovicff
I forgot that if sum is zero, the seed values are distributed as outbound local trust values.


Update Chinese translations

[ ] Update both Chinese translations

@Patrick1904 https://github.com/near/near-wallet/blob/4d47a6e7871cb01db3a8a9b9046362a54d0e24ee/src/translations/en.global.json#L221 Please look at this line. if the English string is "Delete Recovery Method"?

@Patrick1904
https://github.com/near/near-wallet/blob/4d47a6e7871cb01db3a8a9b9046362a54d0e24ee/src/translations/en.global.json#L221
Please look at this line. If the English string is "Delete Recovery Method"?

@picturepan2 we specifically want to communicate to the user they they need to confirm deleting a key on their Ledger device.

@Patrick1904 The PR looks good now.


Comedy Central Change

The Nightly Show has changed to a different format.  Much thanks.
$ youtube-dl -F "http://www.cc.com/full-episodes/xlbpt6/the-nightly-show-march-26--2015---isis-on-tatooine---bacon-rage-at-mcdonald-s-season-1-ep-01035" --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-F', u'http://www.cc.com/full-episodes/xlbpt6/the-nightly-show-march-26--2015---isis-on-tatooine---bacon-rage-at-mcdonald-s-season-1-ep-01035', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.04.03
[debug] Python version 2.7.6 - Linux-3.13.0-48-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] exe versions: avconv 9.18-6, avprobe 9.18-6, rtmpdump 2.4
[debug] Proxy map: {}
[ComedyCentral] the-nightly-show-march-26--2015---isis-on-tatooine---bacon-rage-at-mcdonald-s-season-1-ep-01035: Downloading webpage
ERROR: Unable to extract mgid; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/mtv.py", line 176, in _real_extract
og_url = self._og_search_video_url(webpage)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 641, in _og_search_video_url
return self._html_search_regex(regexes, html, name, **kargs)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 557, in _html_search_regex
res = self._search_regex(pattern, string, name, default, fatal, flags, group)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 547, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 651, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 275, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/mtv.py", line 186, in _real_extract
webpage, 'mgid')
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 547, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract mgid; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

This patch is working for me to grab The Daily Show and the Nightly Show.

Daily Show no longer working for me:
$ youtube-dl --verbose -t http://thedailyshow.cc.com/full-episodes/zwardy/april-16--2015---eric-greitens
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'-t', u'http://thedailyshow.cc.com/full-episodes/zwardy/april-16--2015---eric-greitens']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.04.17
[debug] Python version 2.7.9 - Darwin-14.3.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.6.2, ffprobe 2.6.2, rtmpdump 2.4
[debug] Proxy map: {}
[ComedyCentralShows] april-16--2015---eric-greitens: Downloading webpage
[ComedyCentralShows] april-16--2015---eric-greitens: Downloading show index
[ComedyCentralShows] april-16--2015---eric-greitens: Downloading configuration for segment 1 / 4
[ComedyCentralShows] april-16--2015---eric-greitens: Downloading configuration for segment 2 / 4
[ComedyCentralShows] april-16--2015---eric-greitens: Downloading configuration for segment 3 / 4
[ComedyCentralShows] april-16--2015---eric-greitens: Downloading configuration for segment 4 / 4
[download] Downloading playlist: thedailyshow April 16, 2015 - Eric Greitens
[ComedyCentralShows] playlist thedailyshow April 16, 2015 - Eric Greitens: Collected 4 video ids (downloading 4 of them)
[download] Downloading video 1 of 4
 ERROR: No video formats found!; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 Traceback (most recent call last):
   File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 662, in extract_info
     return self.process_ie_result(ie_result, download, extra_info)
   File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 821, in process_ie_result
extra_info=extra)
   File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 708, in process_ie_result
return self.process_video_result(ie_result, download=download)
   File "/opt/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1047, in process_video_result
raise ExtractorError('No video formats found!')
 ExtractorError: No video formats found!; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Sounds like #5449 to me, which was fixed after your version (2015.04.17) was released.

Sorry, I searched on “comedy” in issue title and this was the only recent open one. Thanks!

Indeed, this is fixed in git.  Thanks malept.
$ python -m youtube_dl -F --verbose "http://thedailyshow.cc.com/full-episodes/9q0y2l/april-15--2015---billy-crystal"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-F', u'--verbose', u'http://thedailyshow.cc.com/full-episodes/9q0y2l/april-15--2015---billy-crystal']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.04.17
[debug] Git HEAD: b4c0806
[debug] Python version 2.7.6 - Linux-3.13.0-49-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] exe versions: avconv 9.18-6, avprobe 9.18-6, ffmpeg 2.6.2, ffprobe 2.6.2, rtmpdump 2.4
[debug] Proxy map: {}
[ComedyCentralShows] april-15--2015---billy-crystal: Downloading webpage
[ComedyCentralShows] april-15--2015---billy-crystal: Downloading show index
[ComedyCentralShows] april-15--2015---billy-crystal: Downloading configuration for segment 1 / 4
[ComedyCentralShows] april-15--2015---billy-crystal: Downloading configuration for segment 2 / 4
[ComedyCentralShows] april-15--2015---billy-crystal: Downloading configuration for segment 3 / 4
[ComedyCentralShows] april-15--2015---billy-crystal: Downloading configuration for segment 4 / 4
[download] Downloading playlist: thedailyshow April 15, 2015 - Billy Crystal
[ComedyCentralShows] playlist thedailyshow April 15, 2015 - Billy Crystal: Collected 4 video ids (downloading 4 of them)
[download] Downloading video 1 of 4
(yada yada)


Problem: New TDBE related genesis parameters are not described in detail

Solution: Added proper names and descriptions of TDBE related genesis parameters. Fixes #194.

there is also https://chain.crypto.com/docs/protocol/network-parameters.html where they should be reflected

Done


Clustering related ceph fixes

Make ceph volumes work correctly with clustering.

/lxc-ci/build/tmp.cd4q0Q1R1b/go/src/github.com/lxc/lxd/lxd/db/cluster/update_test.go:289:11: ineffectual assignment to err

@freeekanayaka comment in this PR when it's ready for review, otherwise I'll just do a quick check every now and then.

@stgraber it's ready for review an merge. As mentioned in the PR description, the rest will come separately.


Named exports in umd builds

Summary

The solution to have valid umd builds for the libraries.
All libraries use React and ReactDOM as peer deps for reusable component support.

Would allow us to build the netlify-cms.js bundle from the umd buld (~+200k overhead added), but we can save that 200k by going direct to the code since we are handling the transforms and plugins within the base webpack monorepo setup anyway.
Test plan
netlify-cms
Make sure the netlify-cms.js bundle is working correctly (full tests).
Make sure all tests are running correctly.
Make sure all development workflow works correctly.
others: netlify-cms-
Run a development server with all script imports like the following example and make sure they run without a bundle:
  <script<EMAIL_ADDRESS>  <script<EMAIL_ADDRESS>  <script<EMAIL_ADDRESS>  <script src="/cms/netlify-cms-default-exports/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-editor-component-image/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-lib-auth/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-lib-util/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-media-library-uploadcare/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-media-library-cloudinary/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-ui-default/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-backend-bitbucket/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-backend-github/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-backend-gitlab/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-backend-git-gateway/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-backend-test/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-core/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-media-library-cloudinary/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-boolean/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-date/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-map/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-markdown/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-number/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-object/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-relation/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-select/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-string/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-text/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-backend-git-gateway/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-datetime/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-file/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-list/dist/umd/index.js"></script>
  <script src="/cms/netlify-cms-widget-image/dist/umd/index.js"></script>

Detail
What this PR accomplishes
These build improvements fix the umd bundles in the monorepo for each library.
The current UMD target builds are broken. If you wanted to import from one of the monorepo published libraries and access them through an import, they would fail. It is the major reason we are using the code directly in the netlify-cms bundle.
There are 2 targets for a umd UMD (Universal Module Definition) library:

You can access them from a script <script src="/cms/netlify-cms-widget-image/dist/umd/index.js"></script>
This allows you to access window.NetlifyCmsWidgetImage in this case from the browser. (think React)
They allow you to use them from es code imports
This allows you to access the exports of the module import { Control, Preview } from 'netlify-cms-widget-image'

We are deriving the NetlifyCmsWidgetImage global namespace by using the library name, stripping the - and Capitalizing each section. This allows us to use webpack's bundler to name the umd export and be able to have them targeted within the modules for export globally.
The format in the above others: netlify-cms- test case above is a valid example of bringing the whole CMS into the browser without bundling, it is only a side affect of the builds, and allows for testing the builds, It would be recommended to create your own bundle from the libraries using a package manager. This way you have a managed set of code you can use to build a smaller bundle of the netlify-cms with targeted module versions.
Example
A netlify-cms bundle using:

git-gateway backend
the internal media library)
exports the CMS core for manual init and registration of custom widgets
could register your own widgets within this bundle also

import * as CMS from 'netlify-cms-core';

/* See note on React, ReactDOM as peers  */

/** Backend **/
import { Control as NetlifyCmsBackendGitGateway } from 'netlify-cms-backend-git-gateway';
CMS.registerBackend('git-gateway', NetlifyCmsBackendGitGateway);

/** Widgets */
import * as NetlifyCmsWidgetString from 'netlify-cms-widget-string';
import * as NetlifyCmsWidgetNumber from 'netlify-cms-widget-number';
import * as NetlifyCmsWidgetText from 'netlify-cms-widget-text';
import * as NetlifyCmsWidgetImage from 'netlify-cms-widget-image';
import * as NetlifyCmsWidgetFile from 'netlify-cms-widget-file';
import * as NetlifyCmsWidgetDate from 'netlify-cms-widget-date';
import * as NetlifyCmsWidgetDatetime from 'netlify-cms-widget-datetime';
import * as NetlifyCmsWidgetSelect from 'netlify-cms-widget-select';
import * as NetlifyCmsWidgetMarkdown from 'netlify-cms-widget-markdown';
import * as NetlifyCmsWidgetList from 'netlify-cms-widget-list';
import * as NetlifyCmsWidgetObject from 'netlify-cms-widget-object';
import * as NetlifyCmsWidgetRelation from 'netlify-cms-widget-relation';
import * as NetlifyCmsWidgetBoolean from 'netlify-cms-widget-boolean';
import * as NetlifyCmsWidgetMap from 'netlify-cms-widget-map';

CMS.registerWidget('string', NetlifyCmsWidgetString.Control, NetlifyCmsWidgetString.Preview);
CMS.registerWidget('number', NetlifyCmsWidgetNumber.Control, NetlifyCmsWidgetNumber.Preview);
CMS.registerWidget('text', NetlifyCmsWidgetText.Control, NetlifyCmsWidgetText.Preview);
CMS.registerWidget('list', NetlifyCmsWidgetList.Control, NetlifyCmsWidgetList.Preview);
CMS.registerWidget('markdown', NetlifyCmsWidgetMarkdown.Control, NetlifyCmsWidgetMarkdown.Preview);
CMS.registerWidget('image', NetlifyCmsWidgetImage.Control, NetlifyCmsWidgetImage.Preview);
CMS.registerWidget('file', NetlifyCmsWidgetFile.Control, NetlifyCmsWidgetFile.Preview);
CMS.registerWidget('date', NetlifyCmsWidgetDate.Control, NetlifyCmsWidgetDate.Preview);
CMS.registerWidget('datetime', NetlifyCmsWidgetDatetime.Control, NetlifyCmsWidgetDatetime.Preview);
CMS.registerWidget('select', NetlifyCmsWidgetSelect.Control, NetlifyCmsWidgetSelect.Preview);
CMS.registerWidget('object', NetlifyCmsWidgetObject.Control, NetlifyCmsWidgetObject.Preview);
CMS.registerWidget('relation', NetlifyCmsWidgetRelation.Control, NetlifyCmsWidgetRelation.Preview);
CMS.registerWidget('boolean', NetlifyCmsWidgetBoolean.Control);
CMS.registerWidget('map', NetlifyCmsWidgetMap.Control, NetlifyCmsWidgetMap.Preview);

/** Un-comment the next few lines to have an automatic start of the bundle just like `netlif-cms.js` */
// if (typeof window !== 'undefined') {
//   CMS.init();
// }

export default CMS;

Notes:

NetlifyCMS Default exports Includes React, ReactDOM as peers
and includes the dependencies needed for your module.
Make sure to include React, ReactDOM in your bundle or
make them peer dependencies if you can import your library into a React app.

build note: size of bundle:  2.95 MiB vs 3.41 MiB
Thoughts about why this is Imperative!

Currently, the CMS does not support a bundle where it is a reusable react component and a single instance of React.
All the UMD builds should support the pattern of React, ReactDOM as peer dependencies. Including the core.
We should consider doing a build for the case a developer wants to just grab the whole thing and use it as a reusable component. This PR accomplishes that target very easily, because we can just add a simple module equal to netlify-cms.js with React and ReactDOM as peer dependencies.
The size of NetlifyCMS is becoming larger and larger with the addition of new default features. The size is due to a lot of unused code that could be targeted using the libraries directly and importing only what a project is using. This would not affect the netlify-cms.js default bundle, but allow developers to control the size of their cms bundle size.

Follow Up (React as Peer):
The following code produces a bundle using the proposed umd bundled libraries with react and react-dom as a peer dependency (external).
Discussion needs to happen for whether to use this as a published library or have developers do this build.
import * as CMS from 'netlify-cms-core';
/** Backends */
import { Control as NetlifyCmsBackendGithub } from 'netlify-cms-backend-github';
import { Control as NetlifyCmsBackendGitlab } from 'netlify-cms-backend-gitlab';
import { Control as NetlifyCmsBackendGitGateway } from 'netlify-cms-backend-git-gateway';
import { Control as NetlifyCmsBackendBitbucket } from 'netlify-cms-backend-bitbucket';
import { Control as NetlifyCmsBackendTest } from 'netlify-cms-backend-test';
/** Widgets */
import * as NetlifyCmsWidgetString from 'netlify-cms-widget-string';
import * as NetlifyCmsWidgetNumber from 'netlify-cms-widget-number';
import * as NetlifyCmsWidgetText from 'netlify-cms-widget-text';
import * as NetlifyCmsWidgetImage from 'netlify-cms-widget-image';
import * as NetlifyCmsWidgetFile from 'netlify-cms-widget-file';
import * as NetlifyCmsWidgetDate from 'netlify-cms-widget-date';
import * as NetlifyCmsWidgetDatetime from 'netlify-cms-widget-datetime';
import * as NetlifyCmsWidgetSelect from 'netlify-cms-widget-select';
import * as NetlifyCmsWidgetMarkdown from 'netlify-cms-widget-markdown';
import * as NetlifyCmsWidgetList from 'netlify-cms-widget-list';
import * as NetlifyCmsWidgetObject from 'netlify-cms-widget-object';
import * as NetlifyCmsWidgetRelation from 'netlify-cms-widget-relation';
import * as NetlifyCmsWidgetBoolean from 'netlify-cms-widget-boolean';
import * as NetlifyCmsWidgetMap from 'netlify-cms-widget-map';
/** MediaLibraries */
import uploadcare from 'netlify-cms-media-library-uploadcare';
import cloudinary from 'netlify-cms-media-library-cloudinary';
/** EditorComponents */
import image from 'netlify-cms-editor-component-image';

/** Backends */
CMS.registerBackend('git-gateway', NetlifyCmsBackendGitGateway);
CMS.registerBackend('github', NetlifyCmsBackendGithub);
CMS.registerBackend('gitlab', NetlifyCmsBackendGitlab);
CMS.registerBackend('bitbucket', NetlifyCmsBackendBitbucket);
CMS.registerBackend('test-repo', NetlifyCmsBackendTest);
/** Widgets */
CMS.registerWidget('string', NetlifyCmsWidgetString.Control, NetlifyCmsWidgetString.Preview);
CMS.registerWidget('number', NetlifyCmsWidgetNumber.Control, NetlifyCmsWidgetNumber.Preview);
CMS.registerWidget('text', NetlifyCmsWidgetText.Control, NetlifyCmsWidgetText.Preview);
CMS.registerWidget('list', NetlifyCmsWidgetList.Control, NetlifyCmsWidgetList.Preview);
CMS.registerWidget('markdown', NetlifyCmsWidgetMarkdown.Control, NetlifyCmsWidgetMarkdown.Preview);
CMS.registerWidget('image', NetlifyCmsWidgetImage.Control, NetlifyCmsWidgetImage.Preview);
CMS.registerWidget('file', NetlifyCmsWidgetFile.Control, NetlifyCmsWidgetFile.Preview);
CMS.registerWidget('date', NetlifyCmsWidgetDate.Control, NetlifyCmsWidgetDate.Preview);
CMS.registerWidget('datetime', NetlifyCmsWidgetDatetime.Control, NetlifyCmsWidgetDatetime.Preview);
CMS.registerWidget('select', NetlifyCmsWidgetSelect.Control, NetlifyCmsWidgetSelect.Preview);
CMS.registerWidget('object', NetlifyCmsWidgetObject.Control, NetlifyCmsWidgetObject.Preview);
CMS.registerWidget('relation', NetlifyCmsWidgetRelation.Control, NetlifyCmsWidgetRelation.Preview);
CMS.registerWidget('boolean', NetlifyCmsWidgetBoolean.Control);
CMS.registerWidget('map', NetlifyCmsWidgetMap.Control, NetlifyCmsWidgetMap.Preview);
/** MediaLibraries */
CMS.registerMediaLibrary(uploadcare);
CMS.registerMediaLibrary(cloudinary);
/** EditorComponents */
CMS.registerEditorComponent(image);

export const NetlifyCmsReact = CMS;
export { CMS as default };

package.json dependencies
{
  "dependencies": {
    "create-react-class": "^15.6.3",
    "emotion": "^9.2.6",
    "immutable": "^3.7.6",
    "lodash": "^4.17.10",
    "moment": "^2.24.0",
    "netlify-cms-backend-bitbucket": "^2.0.0",
    "netlify-cms-backend-git-gateway": "^2.0.0",
    "netlify-cms-backend-github": "^2.0.0",
    "netlify-cms-backend-gitlab": "^2.0.0",
    "netlify-cms-backend-test": "^2.0.0",
    "netlify-cms-core": "^2.0.0",
    "netlify-cms-editor-component-image": "^2.0.0",
    "netlify-cms-media-library-cloudinary": "^1.0.0",
    "netlify-cms-media-library-uploadcare": "^0.3.0",
    "netlify-cms-widget-boolean": "^2.0.0",
    "netlify-cms-widget-date": "^2.0.0",
    "netlify-cms-widget-datetime": "^2.0.0",
    "netlify-cms-widget-file": "^2.0.0",
    "netlify-cms-widget-image": "^2.0.0",
    "netlify-cms-widget-list": "^2.0.0",
    "netlify-cms-widget-map": "^1.0.0",
    "netlify-cms-widget-markdown": "^2.0.0",
    "netlify-cms-widget-number": "^2.0.0",
    "netlify-cms-widget-object": "^2.0.0",
    "netlify-cms-widget-relation": "^2.0.0",
    "netlify-cms-widget-select": "^2.0.0",
    "netlify-cms-widget-string": "^2.0.0",
    "netlify-cms-widget-text": "^2.0.0",
    "prop-types": "^15.7.2",
    "react-immutable-proptypes": "^2.1.0"
  },
  "peerDependencies": {
    "react": "^16.8.1",
    "react-dom": "^16.8.1"
  }
}

Parcel bundle example
Repository Example Here
Demo Here
Although the build for parcel takes longer than I would like. The bundle size is acceptable and there is a very easy setup to consume the libraries as dependencies and build a working example of a netlify-cms bundle using parcel.

Rollup bundle example
Rollup sees the bundles as external UMD correctly and expects the library bundles would have to be included into a project as external libraries (same as the script imports example). To create a single bundle, there would need to be an ES module build where there is a module field (pkg.module). Rollup holds true to the standard module specs.
_Summary: _ Rollup would need to use the script imports until we get the solution for an ES module build. Otherwise you would just use the example given for script imports of the umd builds.

@erquhart Moved in the latest breaking changes. I hope we can get this in under alpha with these last changes.
In this refactor, I changed the names to match the API change in all the widgets, so it will be ready for the refactor and match the naming.

controlComponent
previewComponent

I like the no breaking API change. Seems like a solid way to register a widget.


Snapshot test theme-preval.js

We recently released a version of Primer React that broke theme-preval.js (https://github.com/primer/react/issues/1635). This PR adds a test for theme-preval.js that will prevent us from making a similar mistake again.

@jfuchs all good questions! Let's move forward with this and see if the snapshot test causes any problems.

What does it mean for someone testing locally who hasn't run a build? It would fail, right? Maybe that's okay, but we could make that experience more obvious?

🙏  yes please.. I just spent a good ten minutes trying to work out why the snapshot for theme-preval was failing despite being up-to-date, before realising I needed to run build. Tests - particularly snapshots - I assumed should run deterministically from checked in code, so if that's not the case here perhaps we can make build a prerequisite to test and create a separate test:ci that doesn't need to do this?


Added Compatibility tests for ExportSpec struct

Added different Compatibility tests for the ExportSpec struct
Changed the return value of IsCompatibleWith in exportspec.go to an error-struct
type contains the field that conflicts and the other cluster's id.

@itay-nakash if you're done with the requested changes, please re-request review


Add a method to delete the index only if it already exists

Trying to delete an index that does not exist on the MeiliSearch server will throw an error. To delete it without any error no matter what if it exists or not, we need a new method.

[ ] Add a method deleteIndexIfExists: it deletes the index but does not throw any error if the index does not exist.
[ ] Add tests

Example: https://github.com/meilisearch/meilisearch-python/pull/268/files
⚠ This issue is generated, and deleteIndexIfExists might be named differently in this package. Keep the already existing way of naming in this package to stay idiomatic with the language and the repository.
Related to https://github.com/meilisearch/integration-guides/issues/107
Sorry if this is already partially/completely implemented, feel free to let me know about the state of this issue.

@curquiza what is the state of the issue? Is it related to JavaScript?

Hello @MohsinNajmuddin, no it's not related to javascript
The state of this issue is still ready to be implemented :)

What do you mean with "related to the python"? I'm not sure to get your point

According to https://github.com/meilisearch/integration-guides/issues/157#issuecomment-998826170, we decided to remove this method from the SDKs. I'm closing this issue


Cant place districts/wonders

saw this reported somewhere else but can't find it now. tried replacing citypanel.lua but that didn't help, wondering if there's any other workarounds

This has been fixed in #152. Please download the fall-2017 branch and manually install as described in the readme. If the error still persists, please report to #152.
Thanks!


Kotlin inheritance with examples

Proposed title of article
Kotlin inheritance with examples
Proposed article introduction
Inheritance is a feature using which a class inherits all the features of another class. The class from which the features are inherited is known as base class or super class or parent class and the class that inherits the features is known as derived class or sub class or child class. In this tutorial, we will learn what is inheritance and how to implement it in the Kotlin with the help of examples.
Key takeaways

What's inheritance
Overriding member functions and properties in Kotlin
Calling data members and member functions of base class from child class
Kotlin Inheritance and primary constructor
Kotlin superclass implementation

Article quality
In this article kotlin inheritance with examples will make use of simple language and all examples will be explained in a simpler manners for beginners to understand with easy.
References
N/A

Thank you for submitting your topic. @Shee254
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentation.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
Please feel free to suggest an alternate topic to explore. 🚀


Support records

Would it be much work to support Java 15 records?
It seems that those are not working currently.
I guess the main problem is get missing from record "getters".

I've been looking at this myself for a bit. There are two main barriers to supporting records. The first is in the introspector. I think I've found a way to solve that problem. The second is in bean parameter resolver for Spring MVC and Webflux. There seems to be support for records by way of constructor argument binding but unfortunately the extension points for me to hook into don't provide enough data for me to run the introspector and fetch the data. I'm trying to see if there is a change I can make to Spring to provide a better extension point but so far no luck. The alternative is to duplicate the resolver which is not an idea I like as it would be a maintenance burden I'm not interested in.
Long story short, I have no ETA on records support.
I am open to suggestions and pull requests.

Thank you for the details. I will dive into the codebase and try to come up with ideas how to do it.

I spent some time yesterday working on this. My branch is here.
I have some basic support for records. Nested binding doesn't work and is unlikely to in this iteration.
I've published a snapshot (0.5.0-SNAPSHOT) to Maven Central if you want to try it out.

Thanks for the branch. We don't currently use need nested binding anyway. Will test it this week.

Snapshot version works with records for our (simple) cases.
One surprising thing is that e.g. @RequestParameter("first_name") accepts both first_name and firstName.
Thats fine for us though...
Another thing is Swagger (springfox-boot-starter, springfox-swagger-ui).
If I remember correctly, it worked with @ApiParam annotation on the class field, for @RequestParameter.
We use ApiImplicitParam on the endpoint method but it's more convenient to document fields directly.

@nikolavojicic I think that is due to the nature of how this binding works. I'm essentially leveraging the existing constructor binding that Spring has for creating beans. It can also bind via camelcase names. This is something I disabled in the standard bean binding but I'm not sure I can do that here.
I'll work to get the rest of the tests in place and make a release.

@nikolavojicic I just pushed up another snapshot with the completed work. Can you test one more time before I publish the final version to Maven Central? Thanks.

I've published version 0.5.0 to Maven Central. It might take a few hours to propagate. This should give basic records support. I'll keep following updates on the Spring framework support and adjust if they improve things there. Closing this as completed.


I have a probelm with packages. It works fine in debugging mode but when i build the application, shows only white background. I think it may be issues with the packages. Please check it

  cupertino_icons: ^1.0.2
  firebase_auth: ^0.20.1
  cloud_firestore: ^0.16.0+1
  form_field_validator: ^1.0.1
  flutter_svg: ^0.22.0
  url_launcher: ^6.0.4
  shared_preferences: ^2.0.5
  firebase_storage: ^7.0.0
  file_picker: ^2.1.7

Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_core-0.7.0\android\src\main\java\io\flutter\plugins\firebase\core\FlutterFirebaseCorePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\cloud_firestore-0.16.0+1\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\cloud_firestore-0.16.0+1\android\src\main\java\io\flutter\plugins\firebase\firestore\streamhandler\TransactionStreamHandler.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_auth-0.20.1\android\src\main\java\io\flutter\plugins\firebase\auth\FlutterFirebaseAuthPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_storage-7.0.0\android\src\main\java\io\flutter\plugins\firebase\storage\FlutterFirebaseStoragePlugin.java:38: warning: [deprecation] Registrar in PluginRegistry has been deprecated
  public static void registerWith(PluginRegistry.Registrar registrar) {
                                                ^
1 warning
Note: C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\file_picker-2.1.7\android\src\main\java\com\mr\flutter\plugin\filepicker\FilePickerPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

Hi @never-give-up-vk
From what I can see, the issue is related to a FlutterFire plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,  providing your flutter doctor -v, your pubspec.yaml, a minimal reproducible code sample that does not use 3rd party plugins, your complete flutter run -v logs running the minimal code sample
and I will reopen it.
Thank you


[BUG] 25 words instead of 24 when creating a new wallet

You have the same issue as I have already reported on Chia-Network/chia-blockchain.
Chia-Network/chia-blockchain#8439

Please update to the latest version


Memory leaks

We're seeing a bunch of memory leaks in CCF again. I think it was 9fb8ae67554ad21bdf56277bb2b5afe3d7f82417 and the following snapshot in 1cf6f496a347b8740be8caf4af96b7c66fbd87f6, which removed KRML_HOST_FREE(s); from EverCrypt_Hash_free, so the state objects aren't freed anymore.
Was this removed intentionally? If so, will we have to call EverCrypt_Hash_Incremental_free manually whenever a hash object is deleted? Will we have to track whether it's an incremental or non-incremental object too?
Relates to https://github.com/microsoft/CCF/pull/1576

Thanks for the remark: it's a mistake and I'll push a fix soon.

Awesome, many thanks @Kachoc!

The following PR has just been merged and should fix the issue: https://github.com/project-everest/hacl-star/pull/347
@wintersteiger please tell me if it does('nt) so that I can close the issue.

Thanks for the quick fix @kachoc! That particular leak is gone, but there are others, e.g.
10: Direct leak of 32 byte(s) in 1 object(s) allocated from:
10:     #0 0x4ce3aa in calloc (/CCF/build/history_test+0x4ce3aa)
10:     #1 0xae01e4 in hash_r_alloc /CCF/3rdparty/hacl-star/evercrypt/MerkleTree.c:30:18
10:     #2 0xae24f7 in insert_copy___uint8_t__uint32_t /CCF/3rdparty/hacl-star/evercrypt/MerkleTree.c:990:17
10:     #3 0xae02c3 in insert_ /CCF/3rdparty/hacl-star/evercrypt/MerkleTree.c:1019:5
10:     #4 0xaddad7 in MerkleTree_Low_mt_insert /CCF/3rdparty/hacl-star/evercrypt/MerkleTree.c:1055:3
10:     #5 0xadda4c in mt_insert /CCF/3rdparty/hacl-star/evercrypt/MerkleTree.c:212:3
10:     #6 0x958ac3 in ccf::MerkleTreeHistory::append(crypto::Sha256Hash&) /CCF/src/node/history.h:337:7
...

I wasn't able to figure out whether that's a bug in the Merkle trees or in EverCrypt yet.

Thanks for the feedback! I'll have a look to check for forgotten calls to free in other places

I'm pretty sure it's hash_vec_r_free in the Merkle trees, it should call RV.free instead of V.free.


Settings editor resets scroll position when dragging between groups

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

VS Code Version: 1.58.2
OS Version: win10 20h2

Steps to Reproduce:
https://user-images.githubusercontent.com/26390254/126978427-47daa708-54ea-4b47-8be2-7b92e7e867ac.mp4

Can't tell what is going on, you moved it from one group to another? "Split Editor" works as normal on this. You can also hold alt and drag to copy to another group.

as you can see when drag to right side, the settings page shows start of page. but when backing it to main group it continues from terminal section.(where we were).

Got it, thanks. This is because the editor in the new group is actually a new editor, I am not sure how to preserve the context but I'm sure it's possible...

it doesn't happen for normal editors.
also it happans for extensions info view.

Got it, thanks. This is because the editor in the new group is actually a new editor, I am not sure how to preserve the context but I'm sure it's possible...


[FEATURE REQ] - Azure Key Vault Configuration Provider doesn't support complex configuration types

Library or service name.
What library or service is this request related to? [e.g. Azure.Storage.Blobs]
Microsoft.Extensions.Configuration.AzureKeyVault/Azure.Extensions.Configuration.Secrets
Is your feature request related to a problem? Please describe.
This issue was originally filed here (https://github.com/dotnet/extensions/issues/1522) but we were asked to move it to this repo instead.
We recently migrated our secret configuration from appsettings.json to Azure Key Vault. When using appsettings.json we always used complex strongly typed configuration classes such as ExternalAPIConfig where in appsettings.json this looked like the following:
"ExternalAPIConfig : { "APIUrl" : "https://myapiurl", "APIKey" : "myapikey" }
Then in startup.cs we would make GetSection and Bind calls like this:
ExternalAPIConfig apiConfig = new ExternalAPIConfig(); Configuration.GetSection("ExternalAPIConfig").Bind(apiConfig);
or register a service configuration like this:
services.Configure(Configuration.GetSection("ExteranlAPIConfig"));
or grab a connection string like this:
var connectionString = Configuration.GetConnectionString("ConnectionStringName");
This always worked perfectly and was very clean. After switching over to using Azure Key Vault we are finding that local dev secrets stored in secrets.json work identically to the way that they do when being consumed from appsettings.json, so what is above works perfectly (I assume b/c both use the underlying json configuration file provider).
However when we consume the same secret value from Key Vault (we are pasting the body of the setting from appsettings.json into the value for the secret in key vault so our secret values are json) using the Azure Key Vault Configuration Provider it appears that the kv provider treats the values of secrets as strings and does not recognize them as json objects so the only way to get at the value is with the .Value property of the ConfigurationSection as a string.
So when deployed to staging or prod where the values are actually pulled from key vault we can no longer use GetSection or GetConnectionString as shown above and instead we have to do something like this:
services.Configure(options => { var config = JsonConvert.DeserializeObject(Configuration.GetSection("ExteranlAPIConfig").Value); options.APIUrl= config.APIUrl; options.APIKey= config.APIKey; });
or
Dictionary<string, string> connectionStrings = JsonConvert.DeserializeObject<Dictionary<string, string>>(Configuration.GetSection("ConnectionStrings").Value);
So now I have to introduce environment specific code all over startup.cs just b/c my configuration source is different. It seems like I should be able to use these functions the same way whether I am using the json provider or the key vault provider. This feels very unnatural and results in different code depending on which provider we are using which seems to kind of defeat the purpose of the provider abstraction. Hoping we are missing something obvious here or just doing something plain wrong and would be happy to learn that is the case. What I have outlined above works but is that really the best approach?

@MikeBecatti, thank you for bringing this issue to our attention. There is indeed a way to get this working without having to make the changes you mentioned to your Startup.cs file. KeyVault uses a separate configuration provider than what is used when working directly with appsettings.json. Because of this, there is a different format for specifying hierarchical values. Here is an example that shows how to migrate from json to KV format:
"Serilog": {
  "WriteTo": [
    {
      "Name": "AzureTableStorage",
      "Args": {
        "storageTableName": "logs",
        "connectionString": "DefaultEnd...ountKey=Eby8...GMGw=="
      }
    },
    {
      "Name": "AzureDocumentDB",
      "Args": {
        "endpointUrl": "https://contoso.documents.azure.com:443",
        "authorizationKey": "Eby8...GMGw=="
      }
    }
  ]
}

Key
Value

Serilog--WriteTo--0--Name
AzureTableStorage

Serilog--WriteTo--0--Args--storageTableName
logs

Serilog--WriteTo--0--Args--connectionString
DefaultEnd...ountKey=Eby8...GMGw==

Serilog--WriteTo--1--Name
AzureDocumentDB

Serilog--WriteTo--1--Args--endpointUrl
https://contoso.documents.azure.com:443

Serilog--WriteTo--1--Args--authorizationKey
Eby8...GMGw==

In terms of actually storing the secrets in key vault, you can use the Azure CLI or manually create the secrets from the portal.
So to boil it down, instead of having one secret that is in json format, you would create separate secrets using the double dash notation to represent the hierarchy. At that point, your Startup code should work the same when consuming from KeyVault or using appsettings.json.

Thank you for your response.  The possibility of using "double dash" notation is mentioned in the original issue that I referenced.  However, since we can specify 'json' as the content type for a Key Vault secret I'd like to ask that an enhancement be made to support pulling hierarchical values out of a single key vault secret.

One issue to contend with is that this would be a breaking change for customers whose code is currently written to get back the json as a string. We could consider introducing a new content type such as application/json;configuration, which should make the possibility of breaking anyone extremely remote. Adding this to our backlog.
Thanks again for the suggestion @MikeBecatti!

@MikeBecatti, thank you for bringing this issue to our attention. There is indeed a way to get this working without having to make the changes you mentioned to your Startup.cs file. KeyVault uses a separate configuration provider than what is used when working directly with appsettings.json. Because of this, there is a different format for specifying hierarchical values. Here is an example that shows how to migrate from json to KV format:
"Serilog": {
  "WriteTo": [
    {
      "Name": "AzureTableStorage",
      "Args": {
        "storageTableName": "logs",
        "connectionString": "DefaultEnd...ountKey=Eby8...GMGw=="
      }
    },
    {
      "Name": "AzureDocumentDB",
      "Args": {
        "endpointUrl": "https://contoso.documents.azure.com:443",
        "authorizationKey": "Eby8...GMGw=="
      }
    }
  ]
}

Key	Value
Serilog--WriteTo--0--Name	AzureTableStorage
Serilog--WriteTo--0--Args--storageTableName	logs
Serilog--WriteTo--0--Args--connectionString	DefaultEnd...ountKey=Eby8...GMGw==
Serilog--WriteTo--1--Name	AzureDocumentDB
Serilog--WriteTo--1--Args--endpointUrl	https://contoso.documents.azure.com:443
Serilog--WriteTo--1--Args--authorizationKey	Eby8...GMGw==
In terms of actually storing the secrets in key vault, you can use the Azure CLI or manually create the secrets from the portal.
So to boil it down, instead of having one secret that is in json format, you would create separate secrets using the double dash notation to represent the hierarchy. At that point, your Startup code should work the same when consuming from KeyVault or using appsettings.json.

This is great stuff, but is there any way instead of storing secrets with the index of the array, to have a more powerful way that allows us to store it by telling the value of a property, so the position of the item itself inside the array is not relevant?
Based on the example above, a couple of suggestions:
SeriLog--WriteTo-Name:AzureTableStorage--Args--connectionString, instead of Serilog--WriteTo--0--Args--connectionString
SeriLog--WriteTo-AzureDocumentDB--Args--authorizationKey instead of Serilog--WriteTo--1--Args--authorizationKey
The syntax is just a suggestion, but something that allowed a more robust way. In my experience, using an index of an array soon or later some side effect will happen and you won't know what is causing it at least in a reasonable amount of time...

You can now implement this using a custom secret manager. See https://github.com/Azure/azure-sdk-for-net/pull/19788/files#diff-758e6ae3230293156dca90f33005ebb13d24a67f15076676b8661d87844e1e92R665-R682 for an example


Fix intermittent failure with diagnose metrics cmd

In the latest OCP deployments, it is seen that when the
validate-client pod is scheduled it gets terminated pretty
quickly even before its able to send the required data. We
have addressed similar issue earlier by modifying the client
pod to use HostNetworking enabled. This PR implements a similar
change even for diagnose firewall metrics command.
Fixes: https://github.com/submariner-io/subctl/issues/149
Signed-off-by: Sridhar Gaddam<EMAIL_ADDRESS>

@sridhargaddam I assume we want this in release-0.13?

Backport PR: https://github.com/submariner-io/subctl/pull/151


Update libraries. Target specific GPS vision dependency instead of the whole package

Thanks Paolo.  Good update.