Azure NSG is misconfigured

I have an azure cluster created with the following manifest
apiVersion: hmc.mirantis.com/v1alpha1
kind: ManagedCluster
metadata:
  name: azure-reg1
  namespace: hmc-system
  labels:
    motel: "regional"
spec:
  template: azure-standalone-cp-0-0-3
  credential: azure-cluster-identity-cred
  config:
    controlPlaneNumber: 1
    workersNumber: 3
    location: "westus2"
    subscriptionID: "${AZURE_SUBSCRIPTION_ID}"
    controlPlane:
      vmSize: Standard_A4_v2
    worker:
      vmSize: Standard_A4_v2
    tenantID: "${AZURE_TENANT_ID}"
    clientID: "${AZURE_CLIENT_ID}"
    clientSecret: "${AZURE_CLIENT_SECRET}"
  servicesPriority: 100
  services:
    - template: ingress-nginx-4-11-3
      name: ingress-nginx
      namespace: ingress-nginx
    - name: cert-manager
      namespace: cert-manager
      template: cert-manager-1-16-1
      values: |
        crds:
          enabled: true
    - name: motel-regional
      namespace: motel
      template: motel-regional-0-1-1
      values: |
        victoriametrics:
          vmauth:
            ingress:
              host: reg-1.example.com
            credentials:
              username: motel
              password: motel
        grafana:
          ingress:
            enabled: true
            host: grafana.reg-1.example.com
        cert-manager:
          email<EMAIL_ADDRESS>

In result a nginx-ingress LB was created
ingress-nginx   ingress-nginx-controller                          LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:30999/TCP,443:31409/TCP   75m

But the ingress-nginx-controller cannot receive any requests due to misconfiguration of

More context.
The correct rule is being created in the control plane SG, instead of node SG
Probably due to default SG in the azure.json


when i call writeDone()  then called Asyncnext() function on ubuntu it crash,what should i do?

as title describe, on ubuntu system , i used grpc , but when i want to finsh write ,I called writeDone() function, and then called AsyncNext() function to get the tag ,but is crash , log as follow ,
speech@speech-ThinkPad-X230:~/Desktop/SDK/linux/demo$ gdb ./demo_grpc core
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./demo_grpc...done.
[New LWP 5173]
[New LWP 5172]
[New LWP 5171]
[New LWP 5174]
[New LWP 5176]
[New LWP 5180]
[New LWP 5177]
[New LWP 5178]
[New LWP 5179]
[New LWP 5175]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./demo_grpc'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f039889211e in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_assign(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
[Current thread is 1 (Thread 0x7f0396bcb700 (LWP 5173))]
(gdb) bt
#0  0x00007f039889211e in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_assign(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x00007f03988924b9 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x00007f0398d810aa in grpc::ClientContext::set_debug_error_string (this=0x7f03901c9d70, debug_error_string="") at /usr/local/include/grpc++/impl/codegen/client_context.h:386
#3  0x00007f0398d82227 in grpc::internal::CallOpClientRecvStatus::FinishOp (this=0x7f03901cb798, status=0x7f0396bcabb7) at /usr/local/include/grpc++/impl/codegen/call.h:598
#4  0x00007f0398d8a44c in grpc::internal::CallOpSet<grpc::internal::CallOpRecvInitialMetadata, grpc::internal::CallOpClientRecvStatus, grpc::internal::CallNoOp<3>, grpc::internal::CallNoOp<4>, grpc::internal::CallNoOp<5>, grpc::internal::CallNoOp<6> >::FinalizeResult (
    this=0x7f03901cb788, tag=0x7f0396bcabf0, status=0x7f0396bcabb7) at /usr/local/include/grpc++/impl/codegen/call.h:658
#5  0x00007f0397f6a042 in grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) () from /usr/local/lib/libgrpc++.so.1
#6  0x00007f0398dab671 in grpc::CompletionQueue::AsyncNext<std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l,<PHONE_NUMBER>l> > > > (this=0x7f03901c98e0, tag=0x7f0396bcabf0, ok=0x7f0396bcabb7, deadline=...)
    at /usr/local/include/grpc++/impl/codegen/completion_queue.h:157
#7  0x00007f0398da6feb in sogou::speech::ASRGrpc::doidle (this=0x7f039019b790) at /workspace/src/libssasr/ssasr/src/grpc/ss_asr_grpc.cpp:434
#8  0x00007f0398da7094 in sogou::speech::ASRGrpc::IsActive (this=0x7f039019b790) at /workspace/src/libssasr/ssasr/src/grpc/ss_asr_grpc.cpp:460
#9  0x00007f0398d6d9c1 in sogou::speech::EngineImpl::DoIdle (this=0x7f0390000b40) at /workspace/src/libssasr/ssasr/src/ss_engine_impl.cpp:164
#10 0x00007f0398d78a54 in sogou_speech_do_idle (engine=0x7f0390000b40) at /workspace/src/libssasr/ssasr/src/ss_engine_wrapper.cpp:54
#11 0x00000000004054ae in asr_thread_func (audio_buffer=..., term=...) at /workspace/src/libssasr/ssasr/demo/grpc_asr.cpp:165
#12 0x0000000000432d1d in std::_Bind_simple<void (*(std::reference_wrapper<concurrent_queue<std::vector<unsigned short, std::allocator<unsigned short> > > >, std::reference_wrapper<concurrent_event>))(concurrent_queue<std::vector<unsigned short, std::allocator<unsigned short> > >&, concurrent_event&)>::_M_invoke<0ul, 1ul>(std::_Index_tuple<0ul, 1ul>) (this=0x129e898) at /usr/include/c++/5/functional:1531
#13 0x0000000000432b60 in std::_Bind_simple<void (*(std::reference_wrapper<concurrent_queue<std::vector<unsigned short, std::allocator<unsigned short> > > >, std::reference_wrapper<concurrent_event>))(concurrent_queue<std::vector<unsigned short, std::allocator<unsigned short> > >&, concurrent_event&)>::operator()() (this=0x129e898) at /usr/include/c++/5/functional:1520
#14 0x0000000000432ab0 in std::thread::_Impl<std::_Bind_simple<void (*(std::reference_wrapper<concurrent_queue<std::vector<unsigned short, std::allocator<unsigned short> > > >, std::reference_wrapper<concurrent_event>))(concurrent_queue<std::vector<unsigned short, std::allocator<unsigned short> > >&, concurrent_event&)> >::_M_run() (this=0x129e880) at /usr/include/c++/5/thread:115
#15 0x00007f0398829510 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007f0398afc6ba in start_thread (arg=0x7f0396bcb700) at pthread_create.c:333
#17 0x00007f039829341d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

could any one help me ?

I would try to run your binary with some memory checker to understand the problem. From this stack trace, I can only guess that the ClientContext object may have been deleted...

Hello there. The reason that @yang-g asked if you could run your code through a memory checker (such as valgrind, asan, etc) is that memory corruptions are often non-deterministic on execution and highly-platform-specific. Thus the same code that fails on some platforms may succeed on others. So can you try Yang's suggestion? That would help us a lot in helping to figure this one out.

I am sorry answer so late. I am newer for grpc and linux , I will try your suggest later.  And i found a way to crash on windows ,stack is here
 	ssasr.dll!grpc::CoreCodegen::grpc_byte_buffer_destroy(grpc_byte_buffer * bb) 行 101	C++
 	ssasr.dll!grpc::ByteBuffer::~ByteBuffer() 行 62	C++
 	[外部代码]
 	ssasr.dll!sogou::speech::ASRGrpc::Start(std::function<void __cdecl(std::error_code,std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::basic_string<char,std::char_traits<char>,std::allocator<char> >,bool)> cb) 行 123	C++
 	ssasr.dll!sogou::speech::ASRGrpc::RequestFinish::__l2::<lambda>(bool ok) 行 360	C++
 	[外部代码]
 	ssasr.dll!sogou::speech::ASRGrpc::doidle() 行 444	C++
 	ssasr.dll!sogou::speech::ASRGrpc::IsActive() 行 455	C++
 	ssasr.dll!sogou::speech::EngineImpl::DoIdle() 行 164	C++
 	ssasr.dll!sogou_speech_do_idle(_sogou_speech_engine * engine) 行 55	C++
 	demo_grpc.exe!asr_thread_func(concurrent_queue<std::vector<unsigned short,std::allocator<unsigned short> > > & audio_buffer, concurrent_event & term) 行 166	C++
 	[外部代码]

the biz as follow ,I have connect grpc by stub->asyncxxxx method ,and write data ,then writeDone() , after the finish callback, then reconnect by stub->asyncxxxx( the queue and contect also renewed),  it crash 。 I also think some object memary has problem, but where I can not find .so  asked help， hoped the help of the problem reason . thanks

Please provide a repro of the crash. We cannot do much with just the backtrace.

Changing priority label because of incorrect triaging.


New release?

Last release was on 21 Jul. :)

Yeah. Next release will be 2.0.0 as there were breaking changes from OS 6.x to 7.x, see #182, #184. I would like to take the opportunity of this semver jump to change some of the golang API, but I havn't really planned much details yet.


Snake Game in C

It is great! But add a README.md file and specify how to compile and execute and which Operating Systems are supported. Like you can see the README https://github.com/sohan-k/Snake-game/tree/master/cpp.
NOTE: If you are contributing to Hacktober fest then pull requests from 1st to 31st October is counted so close this one and create in time between

Thanks, sohan. I'll create a new pull on 1st oct, okay? Those hacktober
t-shirts are very tempting.
On Tue, 29 Sep, 2020, 3:26 pm Sohan Kale<EMAIL_ADDRESS>wrote:

It is great! But add a README.md file and specify how to compile and
execute and which Operating Systems are supported. Like you can see the
README https://github.com/sohan-k/Snake-game/tree/master/cpp http://here
.
NOTE: If you are contributing to Hacktober fest then pull requests from
1st to 31st October is counted so close this one and create in time between
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sohan-k/Snake-game/pull/7#issuecomment-700598304, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHB7MV2BVU72W5XGNKFM6PDSIGVMBANCNFSM4R5Q6SJQ
.


Add weights for substrate pallets

Acceptance Criteria

Add weights to substrate pallets
Configure the runtime to use the new weights
Verify that the weights are being used

Note: Weights that are included in pallets are used for testing purposes. Add the weights by running benchmarks for substrate pallets. For additional information visit stackexchnage.

Duplicate


Refactor mpi_write_hlp to not be recursive

Description
Refactor mpi_write_hlp() to not be recursive, to fix stack overflows.
Iterate over the mbedtls_mpi division of the radix requested,
until it is zero. Each iteration, put the residue in the next LSB
of the output buffer. Fixes #2190
Status
READY
Requires Backporting
Yes
Which branch?
mbedtls-2.1
mbedtls-2.7
Migrations
NO
Additional comments
Tested on Linux machine, K64F, NRF52840_DK
Todos

[x] Tests
[ ] Documentation
[x] Changelog updated
[ ] Backported

Steps to test or reproduce
Run the test_suite_mpi on embedded platforms.

@hanno-arm I addressed your comments

@hanno-arm I fixed according to your comment

@RonEld Thanks. I agree that it should never happen, but apart from the reason for including the check I've already given, is it really that obvious that length will never exceed buflen? The caller checks buflen against a shifted version of mbedtls_mpi_get_bitlen(), while the evolution of length in this function depends on iterated calls to mbedtls_mpi_mod_mpi() and mbedtls_mpi_cmp_int(). We rely on all of these functions to work properly if we want to reason that we don't risk an overflow. In my opinion, that's too much risk compared to adding the check. I fully agree that we should reduce code-size whenever we can, see e.g. the latest commit in https://github.com/ARMmbed/mbedtls/pull/2128, but I think it must not come at the cost of too complex reasoning about the safety of the resulting code.

@hanno-arm I don't mind doing these changes, I just think they should be tracked in a different github issue

@hanno-arm Thanks for the review!
I created https://github.com/ARMmbed/mbedtls/issues/2216 to track the other two optimization suggestions

@hanno I modified according to your comments

@andresag01 If you haven't started reviewing yet, I will squash the code commits tomorrow, to a single commit, and update the ChangeLog as you requested

@andresag01 If you haven't started reviewing yet, I will squash the code commits tomorrow, to a single commit, and update the ChangeLog as you requested

Sorry, I had already started reviewing by the time you posted the message...

@andresag01 I have addressed your comments.
Note that https://github.com/ARMmbed/mbedtls/pull/2214#discussion_r235145504 will be addressed as part of hanno's work on #2216

@andresag01 @hanno-arm I have squashed the PR into two commits. A refernce branch for comparison before the commit is in https://github.com/RonEld/mbedtls/tree/2627_reference
Please review

A backport to mbedtls-2.7 is in #2234


Realm Migration for Client Upgrade

Summary
Added in Realm setup for Client Upgrade screen migration.
Added new files for Writer, Actions, Action-Type, Model for client_upgrade.
Updated the index.js for client_upgrade to use Realm data rather than Redux.
Ticket Link
https://mattermost.atlassian.net/browse/MM-20874
Device Information
This PR was tested on:
iPhone X 13.2 Simulator
Android Pixel 2 API 29 Simulator
Screenshots

+1


Version 6.2 still missing contact events?

I'd like to use a feature that @schteppe added 2 years ago:
https://github.com/schteppe/cannon.js/issues/249#issuecomment-164848927
Unfortunately it seems these changes have not made it into the current npm version. What happened?
Edit: I just noticed the latest release was 3 years ago! Maybe it's time for one? :)

Check out my comment here: https://github.com/schteppe/cannon.js/issues/249#issuecomment-779684001


No split pane with :GoRun results or :GoDoc

Not getting any panes opened when I run :GoRun. Same thing happens with :GoDoc. :GoBuild works fine and does generate the binary. Not sure where my settings are preventing the editor from opening up the result of go run . in a different buffer. This is my basic setup:
    use({
        "ray-x/go.nvim",
        config = function()
            require("go").setup({
                verbose = false,
                run_in_floaterm = true,
            })
        end,
    })

nvim_lsp.gopls.setup({
    -- lsp_cfg = false,
    on_attach = on_attach,
    capabilities = capabilities,
    root_dir = require("lspconfig").util.root_pattern(".git", "go.mod", "."),
    flags = {
        debounce_text_changes = 150,
    },
    cmd = { "gopls", "serve" },
    settings = {
        gopls = {
            experimentalPostfixCompletions = true,
            analyses = {
                nilness = true,
                simplifyrange = true,
                unusedwrite = true,
                unusedparams = true,
                shadow = true,
            },
            staticcheck = true,
        },
    },
})

Do you have guihua.lua installed?

Still getting same result after installing it.

I added a sample init.lua
https://github.com/ray-x/go.nvim/blob/master/playground/init.lua
Hope it works for you
Also you can check the output of :checkhealth go and see if there are any warnings/errors.

thank you. seems to work now with the float option. here is a dumb question...what's the recommended way to close the floating window?

thanks @jaredmcqueen.


When opening the game an error message appears

When I open the game a message appears saying: Unable to load language files!
Steps to reproduce the behavior:
I Downloaded the game using the launcher then opened REDRIVER2.exe and the error message appears.

Game version Release Candidate 2
Operating System: Windows

I put both the bin and cue files on the install folder, but only renamed the bin

Use Setup feature in the launcher, it will unpack game and convert necessary game files.


ray()->queries() BadMethodCallException

Describe the bug
ray()->queries() and ray()->showQueries() both throw BadMethodCallException exceptions.
Versions
Ray 1.04
Laravel Ray 1.20
PHP version: 7.4.11
Laravel version: 8.21.0
To Reproduce
Steps to reproduce the behavior:
Add ray()->queries() or ray()->showQueries()
Expected behavior
Expect queries to be output to the Ray app.
Screenshots
Desktop (please complete the following information):

OS: macOS
Version 11.1

Additional context
Stack trace:
BadMethodCallException Method queries does not exist.
    vendor/spatie/macroable/src/Macroable.php:66 Spatie\Ray\Ray::__call
    routes/web.php:7 require
    vendor/laravel/framework/src/Illuminate/Routing/RouteFileRegistrar.php:35 Illuminate\Routing\RouteFileRegistrar::register
    vendor/laravel/framework/src/Illuminate/Routing/Router.php:424 Illuminate\Routing\Router::loadRoutes
    vendor/laravel/framework/src/Illuminate/Routing/Router.php:381 Illuminate\Routing\Router::group
    vendor/laravel/framework/src/Illuminate/Routing/RouteRegistrar.php:135 Illuminate\Routing\RouteRegistrar::group
    app/Providers/RouteServiceProvider.php:48 App\Providers\RouteServiceProvider::App\Providers\{closure}
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36 Illuminate\Container\BoundMethod::Illuminate\Container\{closure}
    vendor/laravel/framework/src/Illuminate/Container/Util.php:40 Illuminate\Container\Util::unwrapIfClosure
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:81 Illuminate\Container\BoundMethod::callBoundMethod
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:37 Illuminate\Container\BoundMethod::call
    vendor/laravel/framework/src/Illuminate/Container/Container.php:610 Illuminate\Container\Container::call
    vendor/laravel/framework/src/Illuminate/Foundation/Support/Providers/RouteServiceProvider.php:120 Illuminate\Foundation\Support\Providers\RouteServiceProvider::loadRoutes
    vendor/laravel/framework/src/Illuminate/Foundation/Support/Providers/RouteServiceProvider.php:45 Illuminate\Foundation\Support\Providers\RouteServiceProvider::Illuminate\Foundation\Support\Providers\{closure}
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36 Illuminate\Container\BoundMethod::Illuminate\Container\{closure}
    vendor/laravel/framework/src/Illuminate/Container/Util.php:40 Illuminate\Container\Util::unwrapIfClosure
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:81 Illuminate\Container\BoundMethod::callBoundMethod
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:37 Illuminate\Container\BoundMethod::call
    vendor/laravel/framework/src/Illuminate/Container/Container.php:610 Illuminate\Container\Container::call
    vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.php:113 Illuminate\Support\ServiceProvider::callBootedCallbacks
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:872 Illuminate\Foundation\Application::bootProvider
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:850 Illuminate\Foundation\Application::Illuminate\Foundation\{closure}
    [internal] array_walk
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:851 Illuminate\Foundation\Application::boot
    vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/BootProviders.php:17 Illuminate\Foundation\Bootstrap\BootProviders::bootstrap
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:230 Illuminate\Foundation\Application::bootstrapWith
    vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:152 Illuminate\Foundation\Http\Kernel::bootstrap
    vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:136 Illuminate\Foundation\Http\Kernel::sendRequestThroughRouter
    vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:110 Illuminate\Foundation\Http\Kernel::handle
    public/index.php:52 require
    /Users/wdavis/.composer/vendor/laravel/valet/server.php:214 [main]

PHPStorm (2020.3.1) does not recognize the methods either.

Invalidating the PHPStorm caches had no effect on discovering the methods.

Are you using the laravel-ray package ? because it's only available in this package and not just ray package

Are you using the laravel-ray package ? because it's only available in this package and not just ray package

Closing this, because @Ashraam is right.
You should run composer require spatie/laravel-ray

Closing this, because @Ashraam is right.
You should run composer require spatie/laravel-ray


Add a Grafana dashboard for NGinx logs

On both production and staging if you would like to test.

I think the list of machines in this JSON file will get out of date quite quickly as people forget to add and remove them. What about templating this file and creating the list of machines dynamically using the output of govuk_node_list and maybe the Puppet generate() function?

I think the list of machines in this JSON file will get out of date quite quickly as people forget to add and remove them. What about templating this file and creating the list of machines dynamically using the output of govuk_node_list and maybe the Puppet generate() function?

Shouldn't be necessary to template it, as Grafana will regenerate the list from the data in Graphite when the dashboard is opened in the users browser. I'd prefer to just remove all the entries if you don't want them in the repository?

If they're generated by Grafana then not having them in this repo would be great, thanks! The same for domains and status codes if those are also generated.

If they're generated by Grafana then not having them in this repo would be great, thanks! The same for domains and status codes if those are also generated.

Ok, now updated.


Rename package to RtoSQLServer

Suggested no need to include Versioning in its name.
https://www.njtierney.com/post/2017/10/27/change-pkg-name/

Fixed by #21


✨ Added member edit screen

Adds the ability to manually add a new member through members/new screen
Adds basic validation to member form fields

On TODO menu:

[x] make email optionally editable
[x] put in basic validation for member model!
[x] email + other field validation
[x] tests

@peterzimon one of scenarios that I'd want to clarify is what happens when an admin enters some dummy email and clicks save? The only way to recover from this situation is to delete the member and start editing again. We are basically giving one chance to input an email for the member.

@kevinansfield would need your expertise on the flaky test here :) The one that is failing is behaving in a strange way, when run in isolation on CI or locally it fails. But when I open up browser through ember test -s -f 'Acceptance: Members' --launch=chrome it always passes. Experimented with different configurations of await wait() and await timeout(xxx) with no luck :/ Maybe you can spot the problem easily?


Adding telemetry publish command to task lib

@ericsciple, @TingluoHuang  can you please review and approve the same?

@TingluoHuang to review. afaik i know this makes sense but i believe ting was involved more on the ## command on the agent side.

@TingluoHuang Can you please complete the review/PR?


Add version command

Closes #95

Could have a test, but happy to merge without.

There's a functional test which I think tests everything that a unit test would.


add over flow hidden for the card body

In the chrome browser card showing the scroller so made the overflow hidden.

Thanks! @mohitkhatri06


performance improvements

added netlify headers for .jsx, .jpeg, .jpg
code splitting was not present for 404 page. implemented codesplitting for 404 page

@smaranjitghose I this PR was WIP😅. netlify.toml was not commited by mistake. I was just 2 mins late😅


Where can I find map markers in the Elements tree?

Sometimes changes I make to map markers cause them to have zero size.  I can find the markers in the React plugin for Chrome, but I can't seem to find them anywhere in the HTML Elements tab.  Where does the GoogleMapMarkers component get mounted?

In chrome you can click on magnifier icon (top left corner in dev tools) and then place a mouse cursor over the marker, then click

@istarkov well that works when the markers are visible, but when they're zero size I can't find them (if only the React dev tools simply had a go to DOM element function)

It looks like overlay views are always placed by gmap in same places, and you need to remember that path (find path with visible marker and magnifier tool)


Why not a single netstandard library for all .Net environment?

Looking at the project I see it is a  netcoreapp2.0
Since AuthorizeNet is a library it should be a netstandard1.3 or netstandard2.0 and be the same code for .Net framework and .Net Core.
What is the reasoning for not making a NetStandard library that can be shared accross all .Net environment?
Thank you,
Frederic

I also have this question , I am working on a project that use dotnet core 2.2 lately. but I found there is no official release version of AuthorizeNet sdk.


Twitch Support

Add the ability for the mod to connect to Twitch's chat servers.
Edit: Chat rooms have been discontinued by Twitch and will no longer be pursued.

A connection implementation has been written. A means of specifying credentials has yet to be written. In addition, the connector has no means of rate limiting itself, nor would be able to monitor the connection's status to reconnect should it be disconnected, or Twitch issues a RECONNECT notice.


Fast-forward alternate branch to current state of repository

Updating remote alternate branch to allow fast-forward of local copy of alternate branch with git fetch/git pull

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


duplicate notification of star event

Hello,
When I changed the star event's condition to true, I saw that it started sending notifications twice.
"star": {
  "created": true,
  "deleted": true
},

I have checked and fixed the pull request. Please help me check.
Thanks!

thanks!
please wait for me to check.

This PR is also related #41


Terminal inline chat buttons can go beyond widget

Clicking outside of the input fixes the problem
Using stable 1.94.1 and Copilot 0.22.1

Can't repro anymore


Fix javascript examples

You should either use import or require. Mixing them is invalid.

Learn Build status updates of commit 759ea09:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/azure-monitor/app/azure-ad-authentication.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@AaronMaxwell,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


On signing with entitlements for distribution outside the Mac App Store?

I've done some testing and the signing process seems to work fine for distributing outside the MAS.
However if you put in the com.apple.security.app-sandbox entitlement into your entitlement plist files then OSX will enforce your app to obey the sandbox limitations. Everything will look fine when you are debugging, but once you sign the bundle your app will throw errors if you try to do something like access files outside the sandbox, etc. Even if your app is not obtained through the MAS.
I know everything works fine if you simply leave out the entitlements altogether. It might also be fine to just specify a different plist file without any entitlements?

@jasonhinkle Thanks for creating some tests with the App Sandbox!
I've just published a PR for signing with entitlements on apps for distribution outside the Mac App Store. As the darwin builds technically do not obey the rules of sandboxing (there possibly being private API calls or binaries causing denials like crash_report), I set the default entitlements for darwin empty of sandbox entitlement keys as you suggested. This should work as a fallback plan for those who wants signing with custom entitlements, even for darwin. :+1:
There are some other questions I came across when going through the documentation... I'll address them in separate issues. This beta could now go official I think.


Support for 2D rigidbodies

Added Mirror.Experimental.NetworkRigidbody2D, which supports 2D rigid bodies instead of regular ones.

All of the issues Codacy seems to have logged come from the original source code of NetworkRigidbody.


Like Count Displays Likes

When participants hits the number in the ( ) next to the word LIKE, it shows who liked it.
When participant hits "LIKE" it perform the action of LIKING something.

[#108485424]
[#108473396]

What is the point of displaying the work 'Like' if an item is un-likable:
Like

Nevermind, I see how it could get confusing with a like count that isn't labeled with 'Like'.


monorepo: move api directories into ./client

Begin the process of moving API directories into ./client. We believe https://github.com/kubernetes-csi/external-snapshotter is using the latest best practices for CSI, Kubernetes, and Golang projects and are following its structure as a guide.

mv ./apis -> ./client/apis
mv ./crds -> ./client/config/crd (note the change from crds to crd)
mv ./hack -> ./client/hack
disable CI tests in Makefile while things are expected to be failing (replace with TODO note)

No further changes are made in order to keep the changes for this commit concise.
This means that the hack scripts are broken, and the go mod may not be working either. This is intended at this time because we want to track hack script and go mod changes explicitly, which will come next.

Can you add a note about the TODO in the PR description?

/lgtm
/approve


Add line break between commands

Currently the second command seems to "disappear" between the two outputs. This change tries to mitigate it.

Thanks @eyalev !


What's new banner

Description:
Add what's new banner that will be shown after new web build was pushed that includes new features
To be used in major version updates to notify users about new features
In web need to be able to show banner about major version updates
--
If we change banner json after release to new id to tell user about new feature and point to changelog, and after 1 week we would revert back to original banner json that has old id, is it so that those users who have already closed that original banner they won't see it because the id is the same as original one?

An idea:

Elias confirmed in the meeting that the original banner won't be shown again to the user. So we can close this as we also decided that we won't need a more fancy what's new banner and we can use the current implementation for now.


HTTP Error 413: Payload Too Large PayloadTooLargeError: request entity too large

Describe the bug
When we are in the middle of the conversation we receive answer as utters names, for example utter_hello instead of receiving the message "Hello" itself.
Rasa Version: rasa-for-botfront-1.7.1-bf4
Botfront: 0.21.3
This is the error from Rasa instance:
2020-03-27 10:47:59 DEBUG    rasa.core.processor  - Predicted next action 'utter_Ikbuu_Rur' with confidence 1.00.
2020-03-27 10:47:59 DEBUG    rasa_addons.core.nlg.graphql  - Requesting NLG for utter_Ikbuu_Rur from http://sah-botfront:3000/graphql.
2020-03-27 10:47:59 DEBUG    sgqlc.endpoint.http  - Query:
query(
    $template: StringOrListOfStrings!
    $arguments: Any
    $tracker: ConversationInput
    $channel: NlgRequestChannel
) {
    getResponse(
        template: $template
        arguments: $arguments
        tracker: $tracker
        channel: $channel
    ) {
text
        metadata
        ...on QuickReplyPayload { buttons { title, type, ...on WebUrlButton { url } ...on PostbackButton { payload } } }
        ...on ImagePayload { image }
        ...on CustomPayload { buttons { title, type, ...on WebUrlButton { url } ...on PostbackButton { payload } }, elements, attachment, image, custom }
    }
}
2020-03-27 10:47:59 ERROR    sgqlc.endpoint.http  - http://sah-botfront:3000/graphql: HTTP Error 413: Payload Too Large
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Access-Control-Allow-Origin: *
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Connection: close
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Content-Length: 144
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Content-Security-Policy: default-src 'self'
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Content-Type: text/html; charset=utf-8
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Date: Fri, 27 Mar 2020 10:47:59 GMT
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: Vary: Accept-Encoding
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response header: X-Content-Type-Options: nosniff
2020-03-27 10:47:59 INFO     sgqlc.endpoint.http  - Response [text/html; charset=utf-8]:
<!DOCTYPE html>

<meta charset="utf-8">
<title>Error</title>

Payload Too Large

2020-03-27 10:47:59 ERROR    rasa_addons.core.nlg.graphql  - NLG web endpoint returned an invalid response: 'NoneType' object is not subscriptable
2020-03-27 10:47:59 DEBUG    rasa.core.processor  - Action 'utter_Ikbuu_Rur' ended with events '[BotUttered('utter_Ikbuu_Rur', {"elements": null, "quick_replies": null, "buttons": null, "attachment": null, "image": null, "custom": null}, {},<PHONE_NUMBER>.54703)]'.

Botfront GraphQL logs:

2020-03-27T09:55:39.899Z [info] : PUT at http://sah-rasa:5005/model succeeded user: 33N4pWyaeNFWqdZ5s /imports/api/instances/instances.methods.js - rasa.train with {"projectId":"bf","instance":{"_id":"9e693b5a-8311-44b1-b2ba-005965fe98a6","name":"Default Instance","host":"http://sah-rasa:5005","projectId":"bf"}} 204 url: http://sah-rasa:5005/model
PayloadTooLargeError: request entity too large
    at readStream (/opt/bundle/bundle/programs/server/npm/node_modules/raw-body/index.js:155:17)
    at getRawBody (/opt/bundle/bundle/programs/server/npm/node_modules/raw-body/index.js:108:12)
    at read (/opt/bundle/bundle/programs/server/npm/node_modules/body-parser/lib/read.js:77:3)
    at jsonParser (/opt/bundle/bundle/programs/server/npm/node_modules/body-parser/lib/types/json.js:135:5)
    at Layer.handle [as handle_request] (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:317:13)
    at /opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:335:12)
    at next (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:275:10)
    at cors (/opt/bundle/bundle/programs/server/npm/node_modules/cors/lib/index.js:188:7)
    at /opt/bundle/bundle/programs/server/npm/node_modules/cors/lib/index.js:224:17
    at originCallback (/opt/bundle/bundle/programs/server/npm/node_modules/cors/lib/index.js:214:15)
    at /opt/bundle/bundle/programs/server/npm/node_modules/cors/lib/index.js:219:13
    at optionsCallback (/opt/bundle/bundle/programs/server/npm/node_modules/cors/lib/index.js:199:9)
    at corsMiddleware (/opt/bundle/bundle/programs/server/npm/node_modules/cors/lib/index.js:204:7)
    at Layer.handle [as handle_request] (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:317:13)
    at /opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:335:12)
    at next (/opt/bundle/bundle/programs/server/npm/node_modules/express/lib/router/index.js:275:10)
    at promiseWillStart.then (/opt/bundle/bundle/programs/server/npm/node_modules/apollo-server-express/dist/ApolloServer.js:85:41)
    at /opt/bundle/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40

To Reproduce
Steps to reproduce the behavior:
Write a long a conversation to create big payloads
Expected behavior
Return the reponse text

Hi friends,
There is a quick fix for this?
I already read some information regarding this issue, it seems we need to modify the BodyParser in order to accept bigger HTTP Body request
all the best

Hi @alebeta90,
As you can see here, the default is 100kb. It's hard for me to imagine a bot response over 100kb, but if you can confirm a use for this, we can add an environment variable setting.

If you're working with the code, the quick fix is to add bodyParserConfig: { limit: '50mb' } to server.applyMiddleware's argument in server/apollo.js.

Hi @pheel thank you very much for your useful answer.
Yes by any reason the response is being over 100kb, this is why we get that error. Dont know if you may like to receive additional information.
It would be good if the fix could come from you directly, just to avoid from our side to maintain the image. But if it is not possible we could code it.
Let us know what is the best solution for all.
All the best

No problem, stay posted for next release.

Implemented here: https://github.com/botfront/botfront/pull/540.


Highlight destination identifier on in-page navigation

Selecting a function only works on small screens.
Heres what I mean:
When I click on a function.

The godoc page takes me to that function's section. However the function I'm looking for is lost among the other functions.

This can be improved by making the selected function stand out.

It tries to put the function at the top of the screen, but can't because the page is too short/your browser window is tall.
So this only affects things in the bottom-most area as tall as your window.
I agree it can be improved though.

You're right. It tries to put the function at the top of the screen. That usually works until it doesn't, then I get this very painful confusion because the function is supposed to be at the top of the screen but its not there. That totally destroys my flow. Its not a pleasant experience. The UX should be consistent. This is broken.
Highlighting the selected function makes the experience consistent.

I think the solution here is to add some javascript to highlight the target identifier on navigation. Should be pretty straightforward.

Taking a look at this

Submitted a Pull Request https://github.com/golang/gddo/pull/328

ok Thanks.

Should this be closed or is there more to do?


Documentation eva

additions and fixes to documentation
new notebook to run simulations

Merging since this shouldn't be at danger of breaking anything.


ESPHome update to uart compiling error

Hi,
I'm not sure if this is universal now after updating ESPHome, but in case it helps someone...On trying to install the code via ESPHome from the sample code for a Victron (100/30) MPPT controller to a esp8266 d1_mini, flagged a compiling uart error on that line (two errors flagged). From another thread (https://community.home-assistant.io/t/esphome-update-and-uart2/562633/16)  changes to ESPHome and uarts used internally, uart0 can no longer be used. Changing
"uart:
id: uart0"  from uart0 to uart_0 and again
"victron:
uart_id: uart0" to uart_0 seems to fix the issue for me.
I'm using and updating ESPHome within Home Assistant. I have a Victron MPPT 100/30 controller and your code works great. Thank you so much for your work.

Hi, I also always run the latest version of esphome. Now i tried your fix because i was having the same issue. But i still get no reading from my victron controller. And i don't know what i did wrong. I connected the gnd to gnd and the TX pin of the controller to the D8 pin. Is there any way to troubleshoot it? And check if there is a connection between the 2?
Kind regards,

Yours compiled and uploaded, and you just don't receive data you mean? TX
from Victron to ESP Pin D7 on the sketch.
MNB
On Sun, 30 Apr 2023, 18:47 gabcraftia, <
@.***> wrote:

Hi, I also always run the latest version of esphome. Now i tried your fix
because i was having the same issue. But i still get no reading from my
victron controller. And i don't know what i did wrong.
DuckDuckGo removed 1 tracker.
More →
https://duckduckgo.com/-BhYN3Hm3itRh6Rucl_pDHLP0SYM3BzgcGL5LjyY2vKURZgWaJhhYOTBUQMeW6ERAz243PAg7FTNo7BalatZ6Sz2dY-oTGK4xmefpeE2F4BDhBYfg62Je8DCAvDoIwbvZ5h58_XRXexR38MImXwkV-CYm_xtqk_fHl8k6B3gkqOMxLJLuP2H5o1NxKs5sYyBMafWNsKC5ocNe-r1-x-CoXTobwKjTA2FeWNLaO8AxI57bjw5VrRKBfyPWpALub74gRBg57jMRbMN8C9UXfOCnQYZBA9ALmEGbYjbHbL5-GrEgDQ
Hi, I also always run the latest version of esphome. Now i tried your fix
because i was having the same issue. But i still get no reading from my
victron controller. And i don't know what i did wrong. I connected the gnd
to gnd and the TX pin of the controller to the D8 pin. Is there any way to
troubleshoot it? And check if there is a connection between the 2?
Kind regards,
—
Reply to this email directly, view it on GitHub
https://github.com/KinDR007/VictronMPPT-ESPHOME/issues/110#issuecomment-1529094206,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2JRCUAHJDPSKSD5T3GIVQDXD2QTZANCNFSM6AAAAAAXQ5NPIE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes that is the problem but it i think it just needs a level shift converter. from 5v to 3.3V ordered some and i will see what it does.

eAusweis

Yes that is the problem but it i think it just needs a level shift converter. from 5v to 3.3V ordered some and i will see what it does.

Die Daten kommen auch ohne Level Shift, aber auf Dauer ist das nicht gut. Eventuell RX und TX vertauscht? Ging mir so.

Guten tag, Ich habe nur diesem video gefolgt. https://www.youtube.com/watch?v=D08sjKWBW7o&ab_channel=KPeyanski
Ab 3:33 kansst du sehen das pin eins und drei verbinded sind das habe ich auch gemacht. eins to GND und drei to pin D7. wenn ich in die logs siehe ist da keine data von der victron. Entschuldigung fur meiner deutsch das ist nicht perfect :)

Ich habe das nur getested mit der batterie angeslossen nicht mit paneelen.

Ok, da lief es bei mir mit dem esp8266 noch fehlerfrei. Hast Du mal einen anderen esp versucht?

ja das haben ich versucht. aber kein unterschied.


Support termux

Currently it fails when trying to install on termux.
Seems to be an issue with how the temp folder is specified

Nvm, problem seems to be with binary (guess I wasn't building them statically correctly)
ldd gives
        libpthread.so.0 => not found
        libc.so.6 => not found
        libdl.so.2 => not found

Those errors are fixed by building a musl binary (Which zig statically links)
But now it cant load curl (One discussion said that musl can't dynamically link, which is supported by the error saying its not supported)


Fix: bug related to header line, https://github.com/votca/csg/issues/370

The lammps data reader was not accounting for the header line, and was incorrectly throwing errors because none of the keywords were matching with the comments.
Fix #370

I don't think so, you mean if the header line is empty. If there is a missing header line that would qualify as an ill formatted data file.

Looks like I failed to update the tests.


Add native Boris method

It's time to add some native particle pushers in the package!
Background
The Boris method is the de facto particle pusher in plasma physics, because of its excellent conservation behavior and relative simplicity. The Boris method is a second order method with discrete phase error related to the choice of fixed time step. If the time step is not fixed, this method can still be used, but the conservation of phase space trajectory will be violated.
Why do we need this?
The Boris method is specifically designed for the expression of Lorentz force. A general ODE solver in OrdinaryDiffEq.jl does not take into account the special form of the Lorentz equation, which is also the reason why the Boris method does not exist in OrdinaryDiffEq.jl. With my recent tests on multiple algorithms from OrdinaryDiffEq.jl, the default Tsit5() has poor conservation properties in many cases, and there are only a few options that display nice energy conservation behaviors #73. The Boris method also requires a fixed timestep for conservation, which makes it a bit harder for investigating a new problem, but we should have a version of our own in this package.
Plan

[x] Implementing a first working version of the Boris method with similar APIs to the ODE solver.
[x] Cleaning up the code.
[x] Testing the accuracy and performance compared with other ODE solvers.
[x] Add a demo using the native Boris method.

This is an exciting idea. Do you have a ToDo list? Maybe I can do something.

This is an exciting idea. Do you have a ToDo list? Maybe I can do something.

Yes! I've added a ToDo list above. After I clean up the code a bit more, feel free to directly push to this branch!
Adding the Boris method was not in my original plan for this package. I want to try this now because of some performance issue I encountered recently with a large number of test particles (> 1e7). Tsit5() is fast, at a cost of violation of phase space conservation; Vern9() together with a time step limitation based on local gyroperiod has much nicer conservation behavior, but it consumes a lot of memory with extremely high GC time (>70% in Julia 1.9.3 and 1.10.0-rc1). I frequently encounterd OOM errors running the trials on a cluster.
By adding a native particle pusher, the high GC time may be largely avoided.

I'm going to merge this to master in order to test the performance for a specific problem. We can further polish this part afterwards.

Have you read this paper?
PS. Perhaps you have also come across this author.

I've heard of this paper recently from a senior member of my group. By briefly scanning through the derivations, I got the impression that $|R|=1$ is based on the assumption that $\Delta t = \textrm{const}$. I will confirm this with some numerical experiments.


hexo g报错

$ hexo g
INFO  Start processing
ERROR Process failed: board/index.md
TypeError: Cannot read property 'utcOffset' of null
at Object.exports.timezone (E:\blog2\node_modules\hexo\lib\plugins\processor\common.js:44:40)
at E:\blog2\node_modules\hexo\lib\plugins\processor\asset.js:43:42
at tryCatcher (E:\blog2\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (E:\blog2\node_modules\bluebird\js\release\promise.js:509:35)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at PromiseArray._iterate (E:\blog2\node_modules\bluebird\js\release\promise_array.js:114:31)
at PromiseArray.init [as _init] (E:\blog2\node_modules\bluebird\js\release\promise_array.js:78:10)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:566:21)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:574:26)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
ERROR Process failed: categories/index.md
TypeError: Cannot read property 'utcOffset' of null
at Object.exports.timezone (E:\blog2\node_modules\hexo\lib\plugins\processor\common.js:44:40)
at E:\blog2\node_modules\hexo\lib\plugins\processor\asset.js:43:42
at tryCatcher (E:\blog2\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (E:\blog2\node_modules\bluebird\js\release\promise.js:509:35)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at PromiseArray._iterate (E:\blog2\node_modules\bluebird\js\release\promise_array.js:114:31)
at PromiseArray.init [as _init] (E:\blog2\node_modules\bluebird\js\release\promise_array.js:78:10)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:566:21)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:574:26)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
ERROR Process failed: tags/index.md
TypeError: Cannot read property 'utcOffset' of null
at Object.exports.timezone (E:\blog2\node_modules\hexo\lib\plugins\processor\common.js:44:40)
at E:\blog2\node_modules\hexo\lib\plugins\processor\asset.js:43:42
at tryCatcher (E:\blog2\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (E:\blog2\node_modules\bluebird\js\release\promise.js:509:35)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at PromiseArray._iterate (E:\blog2\node_modules\bluebird\js\release\promise_array.js:114:31)
at PromiseArray.init [as _init] (E:\blog2\node_modules\bluebird\js\release\promise_array.js:78:10)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:566:21)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:574:26)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
ERROR Process failed: _posts/markdown语法/Markdown.md
YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 4, column 1:
^
at generateError (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:165:10)
at throwError (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:171:9)
at readBlockMapping (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1046:9)
at composeNode (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1332:12)
at readDocument (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1492:3)
at loadDocuments (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1548:5)
at Object.load (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1569:19)
at parseYAML (E:\blog2\node_modules\hexo-front-matter\lib\front_matter.js:80:21)
at parse (E:\blog2\node_modules\hexo-front-matter\lib\front_matter.js:56:12)
at E:\blog2\node_modules\hexo\lib\plugins\processor\post.js:52:18
at tryCatcher (E:\blog2\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (E:\blog2\node_modules\bluebird\js\release\promise.js:509:35)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at PromiseArray._iterate (E:\blog2\node_modules\bluebird\js\release\promise_array.js:114:31)
at PromiseArray.init [as _init] (E:\blog2\node_modules\bluebird\js\release\promise_array.js:78:10)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:566:21)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)

ERROR Process failed: _posts/python数据结构/python数据结构~字典.md
YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 3, column 1:
^
at generateError (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:165:10)
at throwError (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:171:9)
at readBlockMapping (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1046:9)
at composeNode (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1332:12)
at readDocument (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1492:3)
at loadDocuments (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1548:5)
at Object.load (E:\blog2\node_modules\js-yaml\lib\js-yaml\loader.js:1569:19)
at parseYAML (E:\blog2\node_modules\hexo-front-matter\lib\front_matter.js:80:21)
at parse (E:\blog2\node_modules\hexo-front-matter\lib\front_matter.js:56:12)
at E:\blog2\node_modules\hexo\lib\plugins\processor\post.js:52:18
at tryCatcher (E:\blog2\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (E:\blog2\node_modules\bluebird\js\release\promise.js:509:35)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at PromiseArray._iterate (E:\blog2\node_modules\bluebird\js\release\promise_array.js:114:31)
at PromiseArray.init [as _init] (E:\blog2\node_modules\bluebird\js\release\promise_array.js:78:10)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:566:21)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)

ERROR Process failed: _posts/python爬虫学习/第三部分.md
TypeError: Cannot read property 'utcOffset' of null
at Object.exports.timezone (E:\blog2\node_modules\hexo\lib\plugins\processor\common.js:44:40)
at E:\blog2\node_modules\hexo\lib\plugins\processor\post.js:83:42
at tryCatcher (E:\blog2\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (E:\blog2\node_modules\bluebird\js\release\promise.js:509:35)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at PromiseArray._iterate (E:\blog2\node_modules\bluebird\js\release\promise_array.js:114:31)
at PromiseArray.init [as _init] (E:\blog2\node_modules\bluebird\js\release\promise_array.js:78:10)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:566:21)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
at PromiseArray._resolve (E:\blog2\node_modules\bluebird\js\release\promise_array.js:126:19)
at PromiseArray._promiseFulfilled (E:\blog2\node_modules\bluebird\js\release\promise_array.js:144:14)
at Promise._settlePromise (E:\blog2\node_modules\bluebird\js\release\promise.js:574:26)
at Promise._settlePromise0 (E:\blog2\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (E:\blog2\node_modules\bluebird\js\release\promise.js:693:18)
at Promise._fulfill (E:\blog2\node_modules\bluebird\js\release\promise.js:638:18)
I agree and want to create new issue
yes

[] Yes, I was on Hexo Docs page, especially on Templates, Variables, Helpers and Troubleshooting.
[] Yes, I was on NexT Documentation Site.
[] And yes, I already searched for current issues and this is not help to me.

Expected behavior
Actual behavior
Steps to reproduce the behavior

N/A
N/A
N/A

Link to demo site with this issue: N/A
Link(s) to source code or any usefull link(s): N/A

Hexo Information

NexT Information
NexT Version:

[] Latest Master branch.
[] Latest Release version.
[] Old version -

NexT Scheme:

[] All schemes
[] Muse
[] Mist
[] Pisces
[] Gemini

Other Information

===============================================================
========================= ATTENTION! ==========================
===============================================================
NexT repository is moving here: https://github.com/theme-next
===============================================================
It's rebase to v6.0.0 and future maintenance will resume there
===============================================================
---------------------------------------------------------------
Theme Core Configuration Settings
---------------------------------------------------------------
Set to true, if you want to fully override the default configuration.
Useful if you don't want to inherit the theme _config.yml configurations.
override: false
---------------------------------------------------------------
Site Information Settings
---------------------------------------------------------------
To get or check favicons visit: https://realfavicongenerator.net
Put your favicons into hexo-site/source/ (recommend) or hexo-site/themes/next/source/images/ directory.
Default NexT favicons placed in hexo-site/themes/next/source/images/ directory.
And if you want to place your icons in hexo-site/source/ root directory, you must remove /images prefix from pathes.
For example, you put your favicons into hexo-site/source/images directory.
Then need to rename & redefine they on any other names, otherwise icons from Next will rewrite your custom icons in Hexo.
favicon:
small: /images/favicon-16x16-next.png
medium: /images/favicon-32x32-next.png
apple_touch_icon: /images/apple-touch-icon-next.png
safari_pinned_tab: /images/logo.svg
#android_manifest: /images/manifest.json
#ms_browserconfig: /images/browserconfig.xml
Set default keywords (Use a comma to separate)
keywords: "Hexo, NexT"
Set rss to false to disable feed link.
Leave rss as empty to use site's feed link.
Set rss to specific value if you have burned your feed already.
rss:
footer:
Specify the date when the site was setup.
If not defined, current year will be used.
since: 2017
Icon between year and copyright info.
icon: user
If not defined, will be used author from Hexo main config.
copyright:
-------------------------------------------------------------
Hexo link (Powered by Hexo).
powered: true
theme:
# Theme & scheme info link (Theme - NexT.scheme).
enable: true
# Version info of NexT after scheme info (vX.X.X).
version: true
-------------------------------------------------------------
Any custom text can be defined here.
#custom_text: Hosted by GitHub Pages
---------------------------------------------------------------
SEO Settings
---------------------------------------------------------------
Canonical, set a canonical link tag in your hexo, you could use it for your SEO of blog.
See: https://support.google.com/webmasters/answer/139066
Tips: Before you open this tag, remember set up your URL in hexo _config.yml ( ex. url: http://yourdomain.com )
canonical: true
Change headers hierarchy on site-subtitle (will be main site description) and on all post/pages titles for better SEO-optimization.
seo: false
If true, will add site-subtitle to index page, added in main hexo config.
subtitle: Subtitle
index_with_subtitle: false
---------------------------------------------------------------
Menu Settings
---------------------------------------------------------------
When running the site in a subdirectory (e.g. domain.tld/blog), remove the leading slash from link value (/archives -> archives).
Usage: Key: /link/ || icon
Key is the name of menu item. If translate for this menu will find in languages - this translate will be loaded; if not - Key name will be used. Key is case-senstive.
Value before || delimeter is the target link.
Value after || delimeter is the name of FontAwesome icon. If icon (with or without delimeter) is not specified, question icon will be loaded.
menu:
home: /
about: /about || user
tags: /tags
categories: /categories || th
archives: /archives
#schedule: /schedule/ || calendar
#sitemap: /sitemap.xml || sitemap
#commonweal: /404/ || heartbeat
board: /board || book
Enable/Disable menu icons.
menu_icons:
enable: true
home: home
about: user
categories: th
tags: tags
archives: archive
board: book
---------------------------------------------------------------
Scheme Settings
---------------------------------------------------------------
Schemes:
scheme: Muse
scheme: Mist
scheme: Pisces
scheme: Gemini
---------------------------------------------------------------
#sidebar:
#postion: left
#display: post
---------------------------------------------------------------
Social Links.
Usage: Key: permalink || icon
Key is the link label showing to end users.
Value before || delimeter is the target permalink.
Value after || delimeter is the name of FontAwesome icon. If icon (with or without delimeter) is not specified, globe icon will be loaded.
social:
GitHub: https://github.com/flying-fisher || github
知乎: http://www.zhihu.com/people/cui-jun-lei-54 || 知乎
#E-Mail<EMAIL_ADDRESS>|| envelope
#GitHub: https://github.com/yourname || github
#E-Mail<EMAIL_ADDRESS>|| envelope
#Google: https://plus.google.com/yourname || google
#Twitter: https://twitter.com/yourname || twitter
#FB Page: https://www.facebook.com/yourname || facebook
#VK Group: https://vk.com/yourname || vk
#StackOverflow: https://stackoverflow.com/yourname || stack-overflow
#YouTube: https://youtube.com/yourname || youtube
#Instagram: https://instagram.com/yourname || instagram
#Skype: skype:yourname?call|chat || skype
social_icons:
enable: true
Github: GitHub
知乎: zhihu
#E-Mail: E-Mail
icons_only: false
transition: false
Blog rolls
links_icon: link
links_title: Links
links_layout: block
links_layout: inline
links:
#Title: http://example.com/
Sidebar Avatar
in theme directory(source/images): /images/avatar.gif
in site  directory(source/uploads): /uploads/avatar.gif
avatar: /uploads/touxiang.jpg
Table Of Contents in the Sidebar
toc:
enable: true
Automatically add list number to toc.
number: true
If true, all words will placed on next lines if header width longer then sidebar width.
wrap: false
Creative Commons 4.0 International License.
http://creativecommons.org/
Available: by | by-nc | by-nc-nd | by-nc-sa | by-nd | by-sa | zero
creative_commons: by-nc-sa
creative_commons:
sidebar:
Sidebar Position, available value: left | right (only for Pisces | Gemini).
position: left
position: right
Sidebar Display, available value (only for Muse | Mist):
- post    expand on posts automatically. Default.
- always  expand for all pages automatically
- hide    expand only when click on the sidebar toggle icon.
- remove  Totally remove sidebar including sidebar toggle.
display: post
#display: always
#display: hide
#display: remove
Sidebar offset from top menubar in pixels (only for Pisces | Gemini).
offset: 12
Back to top in sidebar (only for Pisces | Gemini).
b2t: false
Scroll percent label in b2t button.
scrollpercent: false
Enable sidebar on narrow view (only for Muse | Mist).
onmobile: false
---------------------------------------------------------------
Post Settings
---------------------------------------------------------------
Automatically scroll page to section which is under  mark.
scroll_to_more: true
Automatically saving scroll position on each post/page in cookies.
save_scroll: false
Automatically excerpt description in homepage as preamble text.
excerpt_description: true
Automatically Excerpt. Not recommend.
Please use  in the post to control excerpt accurately.
auto_excerpt:
enable: false
length: 150
Post meta display settings
post_meta:
item_text: true
created_at: true
updated_at: false
categories: true
Post wordcount display settings
Dependencies: https://github.com/willin/hexo-wordcount
post_wordcount:
item_text: true
wordcount: false
min2read: false
totalcount: false
separated_meta: true
Wechat Subscriber
wechat_subscriber:
enabled: false
qcode: /uploads/weixin_qcode.jpg
#description: ex. subscribe to my blog by scanning my public wechat account
Reward
#reward_comment: Donate comment here
#wechatpay: /images/wechatpay.jpg
#alipay: /images/alipay.jpg
#bitcoin: /images/bitcoin.png
Declare license on posts
post_copyright:
enable: false
license: CC BY-NC-SA 3.0
license_url: https://creativecommons.org/licenses/by-nc-sa/3.0/
---------------------------------------------------------------
Misc Theme Settings
---------------------------------------------------------------
Reduce padding / margin indents on devices with narrow width.
mobile_layout_economy: false
Android Chrome header panel color ($black-deep).
android_chrome_color: "#222"
Custom Logo.
!!Only available for Default Scheme currently.
Options:
enabled: [true/false] - Replace with specific image
image: url-of-image   - Images's url
custom_logo:
enabled: false
image:
Code Highlight theme
Available value:
normal | night | night eighties | night blue | night bright
https://github.com/chriskempson/tomorrow-theme
highlight_theme: normal
---------------------------------------------------------------
Font Settings
- Find fonts on Google Fonts (https://www.google.com/fonts)
- All fonts set here will have the following styles:
light, light italic, normal, normal italic, bold, bold italic
- Be aware that setting too much fonts will cause site running slowly
- Introduce in 5.0.1
---------------------------------------------------------------
CAUTION! Safari Version 10.1.2 bug: https://github.com/iissnan/hexo-theme-next/issues/1844
To avoid space between header and sidebar in Pisces / Gemini themes recommended to use Web Safe fonts for global (and logo):
Arial | Tahoma | Helvetica | Times New Roman | Courier New | Verdana | Georgia | Palatino | Garamond | Comic Sans MS | Trebuchet MS
---------------------------------------------------------------
font:
enable: false
Uri of fonts host. E.g. //fonts.googleapis.com (Default).
host:
Font options:
external: true will load this font family from host above.
family: Times New Roman. Without any quotes.
size: xx. Use px as unit.
Global font settings used on  element.
global:
external: true
family: Lato
size:
Font settings for Headlines (h1, h2, h3, h4, h5, h6).
Fallback to global font settings.
headings:
external: true
family:
size:
Font settings for posts.
Fallback to global font settings.
posts:
external: true
family:
Font settings for Logo.
Fallback to global font settings.
logo:
external: true
family:
size:
Font settings for  and code blocks.
codes:
external: true
family:
size:
---------------------------------------------------------------
Third Party Services Settings
---------------------------------------------------------------
MathJax Support
mathjax:
enable: false
per_page: false
cdn: //cdn.bootcss.com/mathjax/2.7.1/latest.js?config=TeX-AMS-MML_HTMLorMML
Han Support docs: https://hanzi.pro/
han: false
Swiftype Search API Key
#swiftype_key:
Baidu Analytics ID
#baidu_analytics:
Duoshuo ShortName
#duoshuo_shortname:
Disqus
disqus:
enable: false
shortname:
count: true
Hypercomments
#hypercomments_id:
changyan
changyan:
enable: false
appid:
appkey:
Valine.
You can get your appid and appkey from https://leancloud.cn
more info please open https://valine.js.org
valine:
enable: false
appid:  # your leancloud application appid
appkey:  # your leancloud application appkey
notify: false # mail notifier , https://github.com/xCss/Valine/wiki
verify: false # Verification code
placeholder: Just go go # comment box placeholder
avatar: mm # gravatar style
guest_info: nick,mail,link # custom comment header
pageSize: 10 # pagination size
Support for youyan comments system.
You can get your uid from http://www.uyan.cc
#youyan_uid: your uid
Support for LiveRe comments system.
You can get your uid from https://livere.com/insight/myCode (General web site)
#livere_uid: your uid
Gitment
Introduction: https://imsun.net/posts/gitment-introduction/
You can get your Github ID from https://api.github.com/users/
gitment:
enable: false
mint: true # RECOMMEND, A mint on Gitment, to support count, language and proxy_gateway
count: true # Show comments count in post meta area
lazy: false # Comments lazy loading with a button
cleanly: false # Hide 'Powered by ...' on footer, and more
language: # Force language, or auto switch by theme
github_user: # MUST HAVE, Your Github ID
github_repo: # MUST HAVE, The repo you use to store Gitment comments
client_id: # MUST HAVE, Github client id for the Gitment
client_secret: # EITHER this or proxy_gateway, Github access secret token for the Gitment
proxy_gateway: # Address of api proxy, See: https://github.com/aimingoo/intersect
redirect_protocol: # Protocol of redirect_uri with force_redirect_protocol when mint enabled
Baidu Share
Available value:
button | slide
Warning: Baidu Share does not support https.
#baidushare:
type: button
Share
This plugin is more useful in China, make sure you known how to use it.
And you can find the use guide at official webiste: http://www.jiathis.com/.
Warning: JiaThis does not support https.
#jiathis:
##uid: Get this uid from http://www.jiathis.com/
#add_this_id:
Share
#duoshuo_share: true
NeedMoreShare2
This plugin is a pure javascript sharing lib which is useful in China.
See: https://github.com/revir/need-more-share2
Also see: https://github.com/DzmVasileusky/needShareButton
iconStyle: default | box
boxForm: horizontal | vertical
position: top / middle / bottom + Left / Center / Right
networks: Weibo,Wechat,Douban,QQZone,Twitter,Linkedin,Mailto,Reddit,
Delicious,StumbleUpon,Pinterest,Facebook,GooglePlus,Slashdot,
Technorati,Posterous,Tumblr,GoogleBookmarks,Newsvine,
Evernote,Friendfeed,Vkontakte,Odnoklassniki,Mailru
needmoreshare2:
enable: false
postbottom:
enable: false
options:
iconStyle: box
boxForm: horizontal
position: bottomCenter
networks: Weibo,Wechat,Douban,QQZone,Twitter,Facebook
float:
enable: false
options:
iconStyle: box
boxForm: horizontal
position: middleRight
networks: Weibo,Wechat,Douban,QQZone,Twitter,Facebook
Google Webmaster tools verification setting
See: https://www.google.com/webmasters/
#google_site_verification:
Google Analytics
#google_analytics:
Bing Webmaster tools verification setting
See: https://www.bing.com/webmaster/
#bing_site_verification:
Yandex Webmaster tools verification setting
See: https://webmaster.yandex.ru/
#yandex_site_verification:
CNZZ count
#cnzz_siteid:
Application Insights
See https://azure.microsoft.com/en-us/services/application-insights/
application_insights:
Make duoshuo show UA
user_id must NOT be null when admin_enable is true!
you can visit http://dev.duoshuo.com get duoshuo user id.
duoshuo_info:
ua_enable: true
admin_enable: false
user_id: 0
#admin_nickname: Author
Post widgets & FB/VK comments settings.
---------------------------------------------------------------
Facebook SDK Support.
https://github.com/iissnan/hexo-theme-next/pull/410
facebook_sdk:
enable: false
app_id:       #<app_id>
fb_admin:     #<user_id>
like_button:  #true
webmaster:    #true
Facebook comments plugin
This plugin depends on Facebook SDK.
If facebook_sdk.enable is false, Facebook comments plugin is unavailable.
facebook_comments_plugin:
enable:       false
num_of_posts: 10    # min posts num is 1
width:        100%  # default width is 550px
scheme:       light # default scheme is light (light or dark)
VKontakte API Support.
To get your AppID visit https://vk.com/editapp?act=create
vkontakte_api:
enable:       false
app_id:       #<app_id>
like:         true
comments:     true
num_of_posts: 10
Star rating support to each article.
To get your ID visit https://widgetpack.com
rating:
enable: false
id:     #<app_id>
color:  fc6423
---------------------------------------------------------------
Show number of visitors to each article.
You can visit https://leancloud.cn get AppID and AppKey.
leancloud_visitors:
enable: false
app_id: #<app_id>
app_key: #<app_key>
Another tool to show number of visitors to each article.
visit https://console.firebase.google.com/u/0/ to get apiKey and projectId
visit https://firebase.google.com/docs/firestore/ to get more information about firestore
firestore:
enable: false
collection: articles #required, a string collection name to access firestore database
apiKey: #required
projectId: #required
bluebird: false #enable this if you want to include bluebird 3.5.1(core version) Promise polyfill
Show PV/UV of the website/page with busuanzi.
Get more information on http://ibruce.info/2015/04/04/busuanzi/
busuanzi_count:
count values only if the other configs are false
enable: false
custom uv span for the whole site
site_uv: true
site_uv_header:
site_uv_footer:
custom pv span for the whole site
site_pv: true
site_pv_header:
site_pv_footer:
custom pv span for one page only
page_pv: true
page_pv_header:
page_pv_footer:
Tencent analytics ID
tencent_analytics:
Tencent MTA ID
tencent_mta:
Enable baidu push so that the blog will push the url to baidu automatically which is very helpful for SEO
baidu_push: false
Google Calendar
Share your recent schedule to others via calendar page

API Documentation:
https://developers.google.com/google-apps/calendar/v3/reference/events/list
calendar:
enable: true
calendar_id:
api_key:
orderBy: startTime
offsetMax: 24
offsetMin: 4
timeZone: Asia/Shanghai
showDeleted: false
singleEvents: true
maxResults: 250
Algolia Search
algolia_search:
enable: false
hits:
per_page: 10
labels:
input_placeholder: Search for Posts
hits_empty: "We didn't find any results for the search: ${query}"
hits_stats: "${hits} results found in ${time} ms"
Local search
Dependencies: https://github.com/flashlab/hexo-generator-search
local_search:
enable: false
if auto, trigger search by changing input
if manual, trigger search by pressing enter key or search button
trigger: auto
show top n results per article, show all results by setting to -1
top_n_per_article: 1
---------------------------------------------------------------
Tags Settings
---------------------------------------------------------------
External URL with BASE64 encrypt & decrypt.
Usage: {% exturl text url "title" %}
Alias: {% extlink text url "title" %}
exturl: false
Note tag (bs-callout).
note:
Note tag style values:
- simple    bs-callout old alert style. Default.
- modern    bs-callout new (v2-v3) alert style.
- flat      flat callout style with background, like on Mozilla or StackOverflow.
- disabled  disable all CSS styles import of note tag.
style: simple
icons: false
border_radius: 3
Offset lighter of background in % for modern and flat styles (modern: -12 | 12; flat: -18 | 6).
Offset also applied to label tag variables. This option can work with disabled note tag.
light_bg_offset: 0
Label tag.
label: true
Tabs tag.
tabs:
enable: true
transition:
tabs: false
labels: true
border_radius: 0
#! ---------------------------------------------------------------
#! DO NOT EDIT THE FOLLOWING SETTINGS
#!  ---------------------------------------------------------------
Use velocity to animate everything.
motion:
enable: true
async: false
transition:
# Transition variants:
# fadeIn | fadeOut | flipXIn | flipXOut | flipYIn | flipYOut | flipBounceXIn | flipBounceXOut | flipBounceYIn | flipBounceYOut
# swoopIn | swoopOut | whirlIn | whirlOut | shrinkIn | shrinkOut | expandIn | expandOut
# bounceIn | bounceOut | bounceUpIn | bounceUpOut | bounceDownIn | bounceDownOut | bounceLeftIn | bounceLeftOut | bounceRightIn | bounceRightOut
# slideUpIn | slideUpOut | slideDownIn | slideDownOut | slideLeftIn | slideLeftOut | slideRightIn | slideRightOut
# slideUpBigIn | slideUpBigOut | slideDownBigIn | slideDownBigOut | slideLeftBigIn | slideLeftBigOut | slideRightBigIn | slideRightBigOut
# perspectiveUpIn | perspectiveUpOut | perspectiveDownIn | perspectiveDownOut | perspectiveLeftIn | perspectiveLeftOut | perspectiveRightIn | perspectiveRightOut
post_block: fadeIn
post_header: slideDownIn
post_body: slideDownIn
coll_header: slideLeftIn
# Only for Pisces | Gemini.
sidebar: slideUpIn
Fancybox
fancybox: true
Progress bar in the top during page loading.
pace: false
Themes list:
#pace-theme-big-counter
#pace-theme-bounce
#pace-theme-barber-shop
#pace-theme-center-atom
#pace-theme-center-circle
#pace-theme-center-radar
#pace-theme-center-simple
#pace-theme-corner-indicator
#pace-theme-fill-left
#pace-theme-flash
#pace-theme-loading-bar
#pace-theme-mac-osx
#pace-theme-minimal
For example
pace_theme: pace-theme-center-simple
pace_theme: pace-theme-minimal
Canvas-nest
canvas_nest: false
three_waves
three_waves: false
canvas_lines
canvas_lines: false
canvas_sphere
canvas_sphere: false
Only fit scheme Pisces
Canvas-ribbon
size: The width of the ribbon.
alpha: The transparency of the ribbon.
zIndex: The display level of the ribbon.
canvas_ribbon:
enable: false
size: 300
alpha: 0.6
zIndex: -1
Script Vendors.
Set a CDN address for the vendor you want to customize.
For example
jquery: https://ajax.googleapis.com/ajax/libs/jquery/2.2.0/jquery.min.js
Be aware that you should use the same version as internal ones to avoid potential problems.
Please use the https protocol of CDN files when you enable https on your site.
vendors:
Internal path prefix. Please do not edit it.
_internal: lib
Internal version: 2.1.3
jquery:
Internal version: 2.1.5
See: http://fancyapps.com/fancybox/
fancybox:
fancybox_css:
Internal version: 1.0.6
See: https://github.com/ftlabs/fastclick
fastclick:
Internal version: 1.9.7
See: https://github.com/tuupola/jquery_lazyload
lazyload:
Internal version: 1.2.1
See: http://VelocityJS.org
velocity:
Internal version: 1.2.1
See: http://VelocityJS.org
velocity_ui:
Internal version: 0.7.9
See: https://faisalman.github.io/ua-parser-js/
ua_parser:
Internal version: 4.6.2
See: http://fontawesome.io/
fontawesome:
Internal version: 1
https://www.algolia.com
algolia_instant_js:
algolia_instant_css:
Internal version: 1.0.2
See: https://github.com/HubSpot/pace
Or use direct links below:
pace: //cdn.bootcss.com/pace/1.0.2/pace.min.js
pace_css: //cdn.bootcss.com/pace/1.0.2/themes/blue/pace-theme-flash.min.css
pace:
pace_css:
Internal version: 1.0.0
https://github.com/hustcc/canvas-nest.js
canvas_nest:
three
three:
three_waves
https://github.com/jjandxa/three_waves
three_waves:
three_waves
https://github.com/jjandxa/canvas_lines
canvas_lines:
three_waves
https://github.com/jjandxa/canvas_sphere
canvas_sphere:
Internal version: 1.0.0
https://github.com/zproo/canvas-ribbon
canvas_ribbon:
Internal version: 3.3.0
https://github.com/ethantw/Han
han:
needMoreShare2
https://github.com/revir/need-more-share2
needMoreShare2:
Assets
css: css
js: js
images: images
Theme version
version: 5.1.4
这是我的配置文件，希望能够你们可以帮帮我

NexT is rebased into organization repo.
If you want new feature, fix, or support, create new in NexT v6.x repo (desirable in English).
There is instructions on English or Chinese how to update from v5.1.x to v 6.x
You also may read this for details.


Allow custom names for inversions of bool flags

It would be useful to have the ability to customize the inversion name of a boolean flag.
For example you might have --grow and --shrink.
Maybe the FlagInversion can take a .customLong name to allow for full control of the flag spelling.

Hi @ashgti – this is handled by conforming to the EnumerableFlags protocol. See an example in the documentation here: https://swiftpackageindex.com/apple/swift-argument-parser/1.2.3/documentation/argumentparser/enumerableflag


Better GUI

Some features that have been requested:

[x] Customizable, including button colors/materials, padding colors/materials, back-button material, title, etc
[x] Buttons to select search flags

Added in v1.2


Policy won't upload

This policy won't upload. Complains about "issuerUserId" not found. This has now been renamed to "socialIdpUserId".
Also, the certificate is called "SamlCert" in the documentation but in the XML is called "ADFSSamlCert".

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

ID: e14a5d4c-5125-8ed2-7fda-38aee1296b76
Version Independent ID: 054d298b-937e-9f01-ae56-7025e47e4eec
Content: Add ADFS as a SAML identity provider using custom policies in Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-custom-setup-adfs2016-idp.md
Service: active-directory
Sub-service: b2c
GitHub Login: @davidmu1
Microsoft Alias: davidmu

Ah - I see. I was using LocalAccounts but I should have been using SocialAndLocalAccounts for federation (which is confusing). In LocalAccounts, it's called "socialIdpUserId". In SocialAndLocalAccounts it's called "issuerUserId".
Maybe add a note to say you need to use a Social policy to add ADFS.

Also just to note that the VS Code B2C extension when it generates an ADFS template uses "socialIdpUserId".

@rbrayb thanks for the feedback! I'm looking into your doc update recommendation.

I created a pull request to add these things as a note but I will let @davidmu1 make the final call on how to handle this.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/78243
Thanks @rbrayb


Change default event loop for WIndows

@ThomasLaPiana can you see if this fixes this issue https://github.com/ethyca/fides/issues/513 ?
Note: I was unable to run the test suite even before making any changes because of a Snowflake error.

@sanders41 i'll take a look, thank you!

@PSalant726 I'm assuming we're expecting this CI error due to hidden credentials?

ah, good point. will need to implement that fix over there too then and in fidesops, etc.

can we not do a conditional import here and only import the windows selector if we detect the windows platform?


Release azure-cli-sql 2.0.4

Reviewers, please verify the following for this PR:

[ ] The PR title has format Release <component-name> <version>.
[ ] setup.py has been modified with the same version as in the PR title.
[ ] HISTORY.rst has been modified with appropriate release notes.
[ ] If releasing azure-cli or azure-cli-core, __version__ defined in __init__.py should also be modified to match.

Started releasing azure-cli-sql 2.0.4...

Release of 'azure-cli-sql' with version '2.0.4' successful. View at https://pypi.python.org/pypi/azure-cli-sql/2.0.4.

GitHub release created. https://github.com/Azure/azure-cli/releases.


Fix a couple of typos

What was the end-user problem that led to this PR?
The problem was typos.
What is your fix for the problem, implemented in this PR?
My fix is to correct typos.

@bundlerbot r+


[FEATURE] Improve replica rebuilding speed when using 10Gb/s

Is your feature request related to a problem? Please describe.
I am finding that when using Longhorn I see that when replicas are being rebuilt, the speeds are not saturating my 10Gb network.
Describe the solution you'd like
While replicas are being rebuilt it would be nice to see it going faster than 100MB/s
Additional context
I asked this first on the cloud-native slack in the longhorn channel, below is the link with some more context and debugging. I have confirmed from host to host and container to container speeds able to reach near 10Gb/s.
https://cloud-native.slack.com/archives/CNVPEL9U3/p1600260401112400

It seems that Longhorn can launch multiple goroutines to speed up the rebuilding when there are multiple snapshot files in the replica: https://github.com/longhorn/longhorn-engine/blob/9db1eed79a0144526259846a78d9f80df664c823/pkg/sync/rpc/server.go#L404
Due to there are some additional checks during the file syncing, the single file rebuilding may not be able to eat up all of the bandwidth. We may need to test all much bandwidth the single file syncing can take first: https://github.com/longhorn/sparse-tools/blob/e548e37f91af9a7a53149b433d37d68bd7a051d7/sparse/client.go#L244

I forgot to mention that my longhorn volumes are SSDs, formatted as ext4 filesystem.

My understand of replica rebuilding is not only about the network bandwidth, CPU and memory resources also play important roles here, also the SSD read/write bandwidth. It's like a chain. Say first need to have enough CPU and memory resource to read the data from one replica (SSD drive in this case) and send it over TCP to another host and then write the data to another replica, Just found SSD speed: 500MB/s read, 200MB/s write, . I think this this case regardless of CPU and memory resources, due to the write speed limitation, it can not reach 10Gb/s. And if the CPU are very busy with other tasks, it won't 100% focus on this replica rebuilding. This could be another impact on the speed as well.
Please let me know if anything doesn't make sense to you or any question. Thanks.

I should have corrected my post, these are NVMe drives.

Could you run a bandwidth test on the local disk directly to get the performance? Then try using Longhorn with one replica which is locally on this host and see what's the performance difference? In this case we can first focus on the same node and disk to limit the factors. Thanks.

Hi @onedr0p ,
Is this issue concerned about the replica rebuilding speed or it's the Longhorn volume speed in general?
For the rebuilding, we don't aim to saturate the network.
For Longhorn volumes, the bandwidth Longhorn provided for the block device should be at the same level of disk provides (given enough CPU to Longhorn).

Originally I was concerned with the replica rebuilding speed, but I suppose it could be both. I know debugging this issue is hard, you would need a test environment with 10Gb. But if there's ever time a developer could look into it that would be great.

@onedr0p for the replica rebuild, we don't aim to saturate the network or disk, since rebuild is a secondary operation. The most important operation for the volume is read/write, which can cause more pressure on the disk and network. So we currently use a single thread for the rebuilding purpose, and don't expect it to use the maximum bandwidth of the disk or network. Do you think it makes sense?
Regarding the Longhorn volume performance, we do aiming to provide higher bandwidth and IOPS. The result will be likely constrained by the disk speed and CPU. So unless you only have a 1G network, network bandwidth isn't a major concern here.

@yasker that does make sense! We should not be taking away from the read/write of the volumes. I'll close this issue. Thanks for describing it to me!


Proposal: CSS nesting changes.

Purpose
Proposing the removal of nested child divs in the css output as described in https://github.com/sdras/cssgridgenerator/issues/75
Change Summary
I've changed the code box structure to reflect a closing of the parent div and line items for the children. Additionally, I have added HTML Encoded < and > characters to the HTML output, though I can make this an additional PR if we think it's scope creep :). I have also removed the 'child' CSS class from the children divs to pretty up the output now that the CSS isn't nested. The child class was adding 40px left padding to simulate indentation in the parent CSS.
Additional Information
An example of the output code would be:
Before:
.parent {
  display: grid;
  grid-template-columns: repeat(5, 1fr);
  grid-template-rows: repeat(5, 1fr);
  grid-column-gap: 0px;
  grid-row-gap: 0px;
  .div1 { grid-area: 1 / 1 / 4 / 5; }
  .div2 { grid-area: 2 / 5 / 3 / 6; }
  .div3 { grid-area: 2 / 5 / 4 / 6; }
}

After:
.parent {
  display: grid;
  grid-template-columns: repeat(5, 1fr);
  grid-template-rows: repeat(5, 1fr);
  grid-column-gap: 0px;
  grid-row-gap: 0px;
}
.div1 { grid-area: 1 / 1 / 4 / 5; }
.div2 { grid-area: 2 / 5 / 3 / 6; }
.div3 { grid-area: 2 / 5 / 4 / 6; }

Additional Sceenshots of the before and after changes are attached! (Screenshots taken in Chrome v77.0.3865.90, with a res of 1920x920)

I'm unexcited about this change, but I'm overruled :) let's 🚢 it!

@sdras would you be interested in adding a selector for how one would want the output? It also kinda solves an issue I was facing around a ui component that addresses the ie compatibility issue. Maybe 3 options of vanilla css, Sass, or IE safe css? I can open up an issue for it :)


[TimePicker] Fix TimePicker Null value

[TimePicker] Fix TimePicker Null value
FluentTimePicker supports nullable values but when inserting and removing a value, the value stays at the last value (which is 00:00 because backspace sets it first back to 00:00 and then to --:--).
See #2230
Before

After

Sorry, I didn't see it was the same as #2245. Closing.


Improve mass and tracer conservation test with and without topography in ClimaAtmos

It would be best to check conservation (a) with zero fluxes at the boundaries and (b) with non-zero fluxes (e.g., with constant fluxes and a tracer concentration that grows linearly in time). Some conservation problems (from interpolation issues) may only become manifest with non-trivial boundary fluxes.

It would be best to check conservation (a) with zero fluxes at the boundaries and (b) with non-zero fluxes (e.g., with constant fluxes and a tracer concentration that grows linearly in time). Some conservation problems (from interpolation issues) may only become manifest with non-trivial boundary fluxes.

We have one (a) type conservation test (mass \ energy conservation in the stretched grid) in the ci. Is the test urgent? We plan to let @valeriabarra work on the test, when she is back.

That's fine. (I think some of the recent interpolation changes only make a difference for conservation with nonzero boundary fluxes.)

Superseded by other issues on conservation.


tab click indication

i saw there is a listener for the onclick action for the click on each tab. The question is how can i indicate the tab on each click? if i need to perform a dedicated action toward the click for the tab - 2 I would need some sort of number and indication.

finally i got the solution.
SmartTabLayout layout
  layout.setOnTabClickListener(new SmartTabLayout.OnTabClickListener() {
            @Override
            public void onTabClicked(int position) {

            }
        });


RP E2E Test Execution

Which issue this PR addresses:
This PR addresses inefficiencies in our CI and E2E testing process. The current setup is slow and lacks full containerization and Hive integration for cluster management. By using Docker Compose and integrating Hive, this PR reduces runtime, simplifies orchestration, and improves testing reliability.
Fixes: ARO-9501
What this PR does / why we need it:
This PR introduces an E2E testing stage using Docker Compose to orchestrate the RP, Selenium, and E2E test services. The pipeline pulls the required RP image from Azure Container Registry (ACR) and ensures the correct environment is set up for the E2E tests. It helps validate the end-to-end functionality of the system and ensures that tests are running using containerized RP images.

Why we need it: The E2E stage ensures that the entire system is tested in a environment, using containerized components (including RP) and validating workflows through Selenium for browser-based testing.
Key benefits: This change helps automate the test execution process for the complete system, ensuring that every aspect of the application functions correctly in a containerized environment before deployment.

Key Points:

[ ] Improved Efficiency: This new E2E pipeline reduces the runtime for both CI and E2E stages by more than half compared to the current process.
[ ] Hive Integration: We’re now using Hive in the pipeline to create and manage clusters. Hive allows us to propagate required credentials to the installer, as outlined in Hive’s AWS provisioning guide (we apply similar functionality for Azure). This is a major step forward for MIWI, as it enhances our cluster setup, ensuring smoother and more reliable testing.
[ ] Deployment of Hive Operator: Deploying the Hive Operator in this process is another major step forward for MIWI, ensuring better control and integration of clusters.
[ ] Fully Dockerized Process: All services are run via Docker Compose, allowing us to orchestrate the setup with a single command, making the process simpler and more streamlined.
[ ] Image Management: Images for components like rp and e2e are created during the CI containerized stage and then pulled directly for use in the E2E stage.

Test plan for issue:

E2E tests are executed within the pipeline's new E2E stage using Docker Compose.
The tests are triggered automatically after the Containerized stage, ensuring seamless orchestration.

Is there any documentation that needs to be updated for this PR?
N/A
How do you know this will function as expected in production?
N/A

/azp run ci, e2e

/azp run ci, e2e