Add project tools test

@edmond-zhu I combined the two projection test into this branch, please review this branch.

Pr for project unit test
Check result

clang-format: OK
local build result:
+ windows:
Several warnings encoutered, which is caused in ASM_SSE2 objects and will not appear in remote builing. So ignored.

      x86inc.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not
be used by any link operation that consumes this library [F:\work\SVT-AV1\Build\windows\Source\Lib\Common\ASM_SSE2\COMM
ON_ASM_SSE2.vcxproj]
x86_abi_support.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it
will not be used by any link operation that consumes this library [F:\work\SVT-AV1\Build\windows\Source\Lib\Common\ASM_
SSE2\COMMON_ASM_SSE2.vcxproj]
x64inc.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not
be used by any link operation that consumes this library [F:\work\SVT-AV1\Build\windows\Source\Lib\Common\ASM_SSE2\COMM
ON_ASM_SSE2.vcxproj]
x64Macro.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will no
t be used by any link operation that consumes this library [F:\work\SVT-AV1\Build\windows\Source\Lib\Common\ASM_SSE2\CO
MMON_ASM_SSE2.vcxproj]

+ linux:
  Warning #1 encountered, which will be fixed in terpred_tools_test pr:

     [ 58%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/SpatialFullDistortionTest.cc.o
In file included from /opt/work/SVT-AV1/Source/Lib/Common/Codec/EbSequenceControlSet.h:22:0,
                from /opt/work/SVT-AV1/Source/Lib/Common/Codec/EbTransforms.h:30,
                from /opt/work/SVT-AV1/test/SpatialFullDistortionTest.cc:13:
/opt/work/SVT-AV1/Source/Lib/Common/Codec/EbThreads.h:96:0: warning: "__USE_GNU" redefined
#define __USE_GNU
^
In file included from /usr/include/math.h:26:0,
                from /opt/work/SVT-AV1/test/SpatialFullDistortionTest.cc:6:
/usr/include/features.h:325:0: note: this is the location of the previous definition
# define __USE_GNU 1
^
In file included from /opt/work/SVT-AV1/Source/Lib/Common/Codec/EbSequenceControlSet.h:22:0,
                from /opt/work/SVT-AV1/Source/Lib/Common/Codec/EbTransforms.h:30,
                from /opt/work/SVT-AV1/test/SpatialFullDistortionTest.cc:13:
/opt/work/SVT-AV1/Source/Lib/Common/Codec/EbThreads.h:97:0: warning: "_GNU_SOURCE" redefined
#define _GNU_SOURCE
^
<command-line>:0:0: note: this is the location of the previous definition

  Warning #2, which can be fixed by appending additional parameter to build.sh:
  `make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.`
+ Mac:
  One warning, which can be fixed in interpred_tools_test pr:
  `ld: warning: -pie being ignored. It is only used when linking a main executable`,

remote build result:
+ windows: no warnings
+ linux:
One warning, which will be fixed interpred_tools_test pr:

    [ 84%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/SpatialFullDistortionTest.cc.o
In file included from /home/travis/build/Cidana-Developers/SVT-AV1/Source/Lib/Common/Codec/EbSequenceControlSet.h:22:0,
                 from /home/travis/build/Cidana-Developers/SVT-AV1/Source/Lib/Common/Codec/EbTransforms.h:30,
                 from /home/travis/build/Cidana-Developers/SVT-AV1/test/SpatialFullDistortionTest.cc:13:
/home/travis/build/Cidana-Developers/SVT-AV1/Source/Lib/Common/Codec/EbThreads.h:96:0: warning: "__USE_GNU" redefined
 #define __USE_GNU
 ^
In file included from /usr/include/math.h:26:0,
                 from /home/travis/build/Cidana-Developers/SVT-AV1/test/SpatialFullDistortionTest.cc:6:
/usr/include/features.h:325:0: note: this is the location of the previous definition
 # define __USE_GNU 1
 ^
In file included from /home/travis/build/Cidana-Developers/SVT-AV1/Source/Lib/Common/Codec/EbSequenceControlSet.h:22:0,
                 from /home/travis/build/Cidana-Developers/SVT-AV1/Source/Lib/Common/Codec/EbTransforms.h:30,
                 from /home/travis/build/Cidana-Developers/SVT-AV1/test/SpatialFullDistortionTest.cc:13:
/home/travis/build/Cidana-Developers/SVT-AV1/Source/Lib/Common/Codec/EbThreads.h:97:0: warning: "_GNU_SOURCE" redefined
 #define _GNU_SOURCE
 ^
<command-line>:0:0: note: this is the location of the previous definition

+ Mac
One warning encountered, which will be fixed in interpred_tools_test pr:
```
ld: warning: -pie being ignored. It is only used when linking a main executable
```

Test Plan:
Run the unit test with ./SvtAv1UnitTest --gtest_filter="*Proj*", and check the result
Dry-run result:
$: ../../Bin/Debug/SvtAv1UnitTests --gtest_filter="*Proj*"
Running main() from /Users/yons/work/SVT-AV1/third_party/googletest/src/gtest_main.cc
Note: Google Test filter = *Proj*
[==========] Running 7 tests from 3 test cases.
[----------] Global test environment set-up.
[----------] 1 test from SelfGuidedToolsTest
[ RUN      ] SelfGuidedToolsTest.GetProjSubspaceMatchTest
[       OK ] SelfGuidedToolsTest.GetProjSubspaceMatchTest (111835 ms)
[----------] 1 test from SelfGuidedToolsTest (111835 ms total)

[----------] 3 tests from RST/PixelProjErrorLbdTest
[ RUN      ] RST/PixelProjErrorLbdTest.MatchTestWithRandomValue/0
[       OK ] RST/PixelProjErrorLbdTest.MatchTestWithRandomValue/0 (1706 ms)
[ RUN      ] RST/PixelProjErrorLbdTest.MatchTestWithRandomSizeAndValue/0
[       OK ] RST/PixelProjErrorLbdTest.MatchTestWithRandomSizeAndValue/0 (1727 ms)
[ RUN      ] RST/PixelProjErrorLbdTest.MatchTestWithExtremeValue/0
[       OK ] RST/PixelProjErrorLbdTest.MatchTestWithExtremeValue/0 (177 ms)
[----------] 3 tests from RST/PixelProjErrorLbdTest (3610 ms total)

[----------] 3 tests from RST/PixelProjErrorHbdTest
[ RUN      ] RST/PixelProjErrorHbdTest.MatchTestWithRandomValue/0
[       OK ] RST/PixelProjErrorHbdTest.MatchTestWithRandomValue/0 (1682 ms)
[ RUN      ] RST/PixelProjErrorHbdTest.MatchTestWithRandomSizeAndValue/0
[       OK ] RST/PixelProjErrorHbdTest.MatchTestWithRandomSizeAndValue/0 (1696 ms)
[ RUN      ] RST/PixelProjErrorHbdTest.MatchTestWithExtremeValue/0
[       OK ] RST/PixelProjErrorHbdTest.MatchTestWithExtremeValue/0 (180 ms)
[----------] 3 tests from RST/PixelProjErrorHbdTest (3558 ms total)

[----------] Global test environment tear-down
[==========] 7 tests from 3 test cases ran. (119003 ms total)
[  PASSED  ] 7 tests.

Merged.


Add stubs for Collection (template/generics)

Since Laravel collections are quite popular and I'm not sure that it will be typed (I mean template annotations in Laravel code; see this https://github.com/laravel/framework/pull/31486#issuecomment-586609823), I would like to suggest adding stubs for Collection.

Also amused by @voku’s ill-fated attempt to impose any sort of external constraints on the code in Laravel core.
laravel/framework is an untamed horse galloping across the Great Plains, ya know... it’s this magnificent beast that knows no bondage, and you want to put a saddle on it? That’s just not right, man. Real PHP artisans would understand.

@vladyslavstartsev @muglug I took a shot at this #32


Increment versions for servicebus releases

Increment versions for servicebus releases post july-2023 patch release

API change check
API changes are not detected in this pull request.


An example would be extremely helpful.

Type of issue
Typo
Description
[Enter feedback here]
Title says it all
Page URL
https://learn.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.dbcontextoptionsbuilder-1.enabledetailederrors?view=efcore-8.0
Content source URL
https://github.com/dotnet/EntityFramework.ApiDocs/blob/live/dotnet/xml/Microsoft.EntityFrameworkCore/DbContextOptionsBuilder`1.xml
Document Version Independent Id
a42e7dfa-dc25-592e-21e9-37d9fe3fc079
Article author
@dotnet-bot

See https://learn.microsoft.com/en-us/ef/core/logging-events-diagnostics/extensions-logging?tabs=v3#getting-detailed-messages, which is in the Logging docs linked from the API page you referenced.


docker restart always policy does not work if container was unable to start.

Description
I have simple compose.yml
where i run few containers with rsyslog swarm and registry
swarm and registry containers have those sections
    restart: always
    depends_on:
       - rsyslog
    logging:
      driver: syslog
      options:
        syslog-address: "tcp://localhost:5140"
        syslog-facility: "local0"

so if i start containers with compose everything is ok, but if i do docker daemon restart or pc reboot docker start containers with random order and as result in logs I see this:
Mar 21 12:28:26 dev dockerd-current: time="2017-03-21T12:28:26.413440689Z" level=error msg="Failed to start container 53eb2f3fa935503488a1b824a738656e82044f7faa8e705ee74f77fe22ccda1b: Failed to initialize logging driver: dial tcp <IP_ADDRESS>:5140: getsockopt: connection refused"

This happen because rsyslog container was not ready when dependent containers was starting.
I've expected that it will try to restart automatically due to restart: always but it does not.
it seems that restart always works ONLY if app in container crashed but in my case container start is failed and im not sure if this a bug or not.
I wonder maybe there is some workarounds for this?
Output of docker version:
Client:
Version:         1.12.6
API version:     1.24
Package version: docker-common-1.12.6-11.el7.centos.x86_64
Go version:      go1.7.4
Git commit:      96d83a5/1.12.6
Built:           Tue Mar  7 09:23:34 2017
OS/Arch:         linux/amd64

Server:
Version:         1.12.6
API version:     1.24
Package version: docker-common-1.12.6-11.el7.centos.x86_64
Go version:      go1.7.4
Git commit:      96d83a5/1.12.6
Built:           Tue Mar  7 09:23:34 2017
OS/Arch:         linux/amd64

Output of docker info:
Containers: 14
Running: 11
Paused: 0
Stopped: 3
Images: 21
Server Version: 1.12.6
Storage Driver: devicemapper
Pool Name: docker-253:1-53051684-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 2.088 GB
Data Space Total: 107.4 GB
Data Space Available: 46.82 GB
Metadata Space Used: 3.903 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.144 GB
Thin Pool Minimum Free Space: 10.74 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: null overlay bridge host
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Security Options: seccomp selinux
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 4
Total Memory: 6.494 GiB
Name: dev.box.com
ID: EGUH:UPDK:G5F6:I2NA:MQ4U:VGFY:IWCL:AQ3R:FDP5:6UH3:XBNI:3XF6
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
<IP_ADDRESS>/8
Registries: docker.io (secure)

This is the expected behavior. It's frustrating at times, but not sure it's correct to change it either.

hi @cpuguy83 thanks for the response! maybe there is any way how to configure docker to respect the order of how containers should start after daemon restart, I cant believe that daemon just don't care about that, otherwise all sort of logic related to dependencies on start up does not make any sense in production.

It will do a best effort for --link'd containers.
The "depends_on" functionality is wholly implemented in compose.

I see, ty for explanation. It seems I should get rid of using driver: syslog with rsyslog in container.

I think @cpuguy83 answered my question so I close issue. thanks.


Dialog Disappears on Device Rotation

When I perform these sequences of events, the dialog on screen disappears:
Sequence 1: With at least a palette inserted in list

Click on Manage Palette
Long click on palette item in list
Click on Rename item of the contextual app bar
Orientation Change

Sequence 2:

Long Click on Palette Item
Click on Edit
Orientation Change

Whoah, someone actually installed this old app?
Thanks for the good report with repro steps, but is unlikely that I'll work on this app again.
It would be fun to try and build it out to original vision, but I doubt there's demand and I should really be spending my time elsewhere...


Fix php detection when called by composer 1.3+

As Composer 1.3RC is out, this should be done to avoid any problems with our new xdebug-circumvention code..
See https://github.com/composer/composer/issues/5783#issuecomment-265133968 and especially the last comment for details. If you want maximum compatibility, you can use Composer\Composer::VERSION to do it selectively for new versions, but this is set to a git hash for snapshot builds so maybe rather check if VERSION is not a hash and is below 1.3 then do the old behavior, otherwise do new behavior (as snapshots are more likely to be recent I guess..)

this issue was fixed for a while but latest self-update caused composer to update to version 1.3.0 2016-12-24 00:47:03 and the issue re-appeared

Same as @red-smeg:
composer update
using composer 1.3.0 (Symfony 2.8.15, PHP 5.6 on Ubuntu 16.04.01LTS) gives
Cannot load Zend OPcache - it was already loaded PHP Warning: Module 'mysqlnd' already loaded in Unknown on line 0 PHP Warning: Module 'PDO' already loaded in Unknown on line 0
...and so on for every PHP module, and this appears multiple times each time PHP is invoked. Looks like an issue with composer and using multiple (copies of) the PHP ini file?
This started happening I think when I changed my composer.json to use
'"sensio/distribution-bundle": "~5.0"'
Hope this can be fixed.

I just ran composer update sensio/distribution-bundle (v5.0.15 => v5.0.17) and the warnings disappeared! Thanks a lot for the fix @fabpot!

Confirmed fixed this end too: 'composer update' now runs without any PHP module warnings. Huge thanks.

Thanks for backporting this to v4 as well @fabpot!


nix-shell sets $PYTHONPATH, normal environment does not

Issue description
I'm trying to install python with some packages, for use by a vim plugin (CoVim). This means I want that setup to be available in my regular shell. However, even though I can properly import all the packages in a python prompt, vim cannot access them because the $PYTHONPATH is not set. When I make the same packages available with nix-shell, it sets the $PYTHONPATH and everything works fine.
Is there some way I can generate the PYTHONPATH in my regular environment?
Steps to reproduce
I put this in python.nix:
with import <nixpkgs> {};
pkgs.python27.withPackages (ps: with ps; [ twisted argparse service-identity ])

and activated with nix-env -if python.nix. Running import twisted in python works fine, but loading CoVim gives an error. echo $PYTHONPATH shows the variable is empty.
If I run nix-shell -p pythonPackages.twisted and then echo $PYTHONPATH everything I need is there.
Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
NixOS version 16.09.1650.d2cd8a0 (Flounder)
Nix version: (run nix-env --version)
nix-env (Nix) 1.11.6
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)
16.09.1650.d2cd8a0

I'm trying to install python with some packages, for use by a vim plugin (CoVim). This means I want that setup to be available in my regular shell. However, even though I can properly import all the packages in a python prompt, vim cannot access them because the $PYTHONPATH is not set.

Other programs should not rely on a global $PYTHONPATH. Instead, they should make sure they point to the Python environment that should be used.

When I make the same packages available with nix-shell, it sets the $PYTHONPATH and everything works fine.

nix-shell is a shell for development of packages/expressions. A setup-hook builds up $PYTHONPATH. This shouldn't be relied on outside of nix-shell.

and activated with nix-env -if python.nix. Running import twisted in python works fine, but loading CoVim gives an error. echo $PYTHONPATH shows the variable is empty.

That's because CoVim is not aware of this Python environment.
Do we have CoVim in Nixpkgs? I cannot find it. In any case, this should be fixed in the expression of CoVim.

Actually I installed CoVim with Vundle - so I should use nix to install vim plugins?
When I look at the CoVim source code I don't actually see any reliance on $PYTHONPATH though, it simply calls python in a vim file. Also when I run !which python inside vim it gives me the same path that I get when running it which python in my regular shell, that makes it surprising to me that the environment is different.

Whenever a program needs another program during runtime, we wrap the first with a wrapper that adds the second program to PATH. With Nix you can have multiple Python environments simultaneously, much like virtualenv. Now, I don't know how you use CoVim and what Python environment you expect it to use.
If the vim file has calls python, and you have the Python environment installed in your profile, as you described, then vim should be able to find it and everything should work. PYTHONPATH is indeed still empty, because we don't use it at all.
Anyway, I'm not really familiar with vim or Vundle so I can't help you much there. I am closing this issue because its not a Nixpkgs issue, but if you have more questions, feel free to write them here. For a question like this you might also want to write to the nix-dev list.

In my NixOS environment I'm not really using python so I intended to just have a single, global one. I expected that vim_configurable would in fact make sure that python is available, because it has python support. But maybe something goes wrong there - perhaps vim_configurable requires only python and does not call its packages, somehow.
Your second paragraph seems counter to my experiences :) It's what I expected as well though, that's why I put the issue here.
I guess if I will want to use CoVim (I actually never tried it before) I will just have to package it. I haven't done that before, but I will try to make some time for that.


Properties file storage

Problem
Command line interfaces, and other processes that terminate after each call, don't persist the properties in a way that simulates the idea of a "session". We need a way for CLIs to use the same anonymous ID with each call so we can sanely correlate the ID with a distinct ID at a later time when they run a login command.
Changes
Introduces the class, PostHogFsStorage into posthog-core and updated posthog-node to use the persistence option to toggle between in-memory storage and filesystem storage of properties like the anonymous_id.
Release info Sub-libraries affected
Bump level

[ ] Major
[ ] Minor
[x] Patch

Libraries affected

[ ] All of them
[ ] posthog-web
[x] posthog-node
[ ] posthog-react-native

Changelog notes

Added support for filesystem properties persistence for the posthog-node library

This is great, thanks for the contribution! 🚀
Would love to see some tests, like here: https://github.com/PostHog/posthog-js-lite/blob/master/posthog-react-native/test/storage.spec.ts#L4

It doesn't look like there's currently a basis for testing storage/persistence in the node package (looks like you linked to the react-native package which this doesn't touch). Any suggestions or best practices for testing would be most appreciated.

Yeah, I meant the exact same file, but for posthog-node (and FsStorage). Things should be similar enough, thanks to similar interfaces, that the file should be a good indicator of what to do for node :)

I added a test suite for the file storage class, but I can't seem to run the full test suite locally. I get the following error on 17 of the different test files:
TypeError: Cannot assign to read only property 'performance' of object '[object global]'

      at hijackMethod (node_modules/@sinonjs/fake-timers/src/fake-timers-src.js:946:32)
      at Object.install (node_modules/@sinonjs/fake-timers/src/fake-timers-src.js:1733:17)
      at FakeTimers.useFakeTimers (node_modules/@jest/fake-timers/build/modernFakeTimers.js:110:36)


Redisgn of PRoduct Page

I have made changes to the Product Page @sagun03 Could you please see the padding Part and sticky key part.


Remove robotics and supermatter lobby images

They don't look good, we have way better ones now.

Forgot about attribution file

3D bros, its so over


Class Yajra\Datatables\Html\Builder does not exist

Summary of problem or feature request
I have installed
"yajra/laravel-datatables-oracle": "~8.0",
"yajra/laravel-datatables-html":"^3.0",

When I try to render the table, I am getting Class Yajra\Datatables\Html\Builder does not exist
System details

Operating System
PHP Version 7.0
Laravel Version 5.5
Laravel-Datatables Version "yajra/laravel-datatables-oracle": "~8.0",

Namespace updated, see https://yajrabox.com/docs/laravel-datatables/master/upgrade


KNL-1426 allow Sharestream and Kaltura LTI URLs

instead of making Sakai institutions customize their AntiSamy policies

LGTM


botkit 4.x support?

I love the idea of this project. Is it going to be updated for bot.createConversation and other botkit 4.x changes?

Yes. We use botkit intensely in our project so it will remain updated as
botkit continues to version up. Is there any other functionality (other
than createConversation) that you would like to see?
On Sat, Jan 14, 2017 at 7:24 AM Alec Lazarescu<EMAIL_ADDRESS>wrote:

I love the idea of this project. Is it going to be updated for
bot.createConversation and other botkit 4.x changes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gratifychat/botkit-mock/issues/14, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKLHiRYd5lwe0mTLk2vTXwlm8lCLlDAks5rSL6KgaJpZM4LjnEG
.

Nice. In addition to being able to test conversation flows/state (setting variables, repeating until you give an accepted answer, etc would be good to have reactions and reminders API support - https://github.com/howdyai/botkit/blob/master/lib/Slack_web_api.js#L80

Thanks @alecl we'll leave this issue open until we push that functionality. Feel free to submit a PR if you happen to add this into your own fork first.

I think a great tracking goal would be to support test all the examples here: https://github.com/howdyai/botkit-starter-slack
I actually forked that to start my bot and when doing simple testing found I couldn't test a few more things there too.
The storage mock was created on the botkit class but not the controller so that is still needed.
  controller.hears(['hello', 'hi'], 'direct_message,direct_mention,mention', function (bot, message) {

    bot.api.reactions.add({
      timestamp: message.ts,
      channel: message.channel,
      name: 'robot_face',
    }, function (err, res) {
      if (err) {
        bot.botkit.log('Failed to add emoji reaction :(', err);
      }
    });

    controller.storage.users.get(message.user, function (err, user) {
      if (user && user.name) {
        bot.reply(message, 'Hello, ' + user.name + '!!');
      } else {
        bot.reply(message, 'Hello.');
      }
    });
  });

Also the message.match came up as undefined when stepping through the code with the mock
controller.hears(['^say (.*)','^say'], 'direct_message,direct_mention', function(bot, message) {
        if (message.match[1]) {

            if (!wordfilter.blacklisted(message.match[1])) {
                bot.reply(message, message.match[1]);
            } else {
                bot.reply(message, '_sigh_');
            }
        } else {
            bot.reply(message, 'I will repeat whatever you say.')
        }
    });

I'm debating with myself whether to continue down this route or record the Slack incoming/outgoing messages and use that to simulate things somehow.

We'll work to get these implemented. Thanks for the link.
I'm not sure what you mean by simulate, but If you're talking about hacking around something that can be covered in botkit-mock, then it's probably best to avoid and wait for a PR.

Solved in latest version of master. Grab the latest version from npm.


limit doesn't work properly with more than one digit

basically limit: 10 doesn't work at all, it shows no result at all.
limit: 11 shows one result,  limit: 12 shows two results, and so on.
something is very broken here
(using latest version of typeahead - 0.11.1)

I have the exact same problem. Here's my code:
// initialize dataset
    var dataset = new Bloodhound({
      datumTokenizer: Bloodhound.tokenizers.whitespace,
      queryTokenizer: Bloodhound.tokenizers.whitespace,
      remote: {
        url: '<remoteUrl>?query=%QUERY',
        wildcard: '%QUERY',
        cache: false,
      }
    });

    $elem.typeahead({
      hint: false,
      highlight: true,
      minLength: 3
    }, {
      display: "label",
      async: true,
      limit: 10,
      source: dataset,
      templates: {
        suggestion: function (data) {
          return $('<p>' + data.label + '</p>');
        }
      }
    });

I installed typeahead from bower, version 0.11.1.
If I don't specify a limit it works great. But as soon as I set a limit, it doesn't work as expected.
Even if i set limit to 5, which is default, it doesn't work. Whereas the server always returns the expected suggestions, typeahead just doesn't render them...


What can I resize block.db and block.wal?

I have three osds, and my dedicated_devices is very low. I want to discrease block.db. What should I do?

oh I see， change bluestore block db size   this can help me.


[BUG] Revamp parsing logic that relies on FMTONLY

Currently there are multiple issues open that rely on correctly parsing the user's SQL statement and using FMTONLY to query the database for the column metadata. This issue will keep a cumulative track of such issues until the parsing logic has been revamped.
List of issues related to parsing the SQL query for FMTONLY:
https://github.com/Microsoft/mssql-jdbc/issues/493
https://github.com/Microsoft/mssql-jdbc/issues/848
https://github.com/Microsoft/mssql-jdbc/issues/887
https://github.com/Microsoft/mssql-jdbc/issues/911
https://github.com/Microsoft/mssql-jdbc/issues/921

Hi @gs-rezaem, @and-costea, @jkoskela, @mohitj13, and @drewclauson
The team has recently created a PR which should address these issues. I'd like to invite you to test the PR and see if the problems are resolved on your end. The team has tested internally and the PR should resolve all of the issues listed above. You can clone the PR from the branch and turn the new property on by specifying useFmtOnly=true in the connection string, or by using SQLServerDatasource.setFmtOnly(true).

@vborisoff can you please followup? Have a look at #493 to find the reproducible issue. You'll need to clone this repository, setup a local test environment, switch to the PR branch and test using the code in #493.

@gs-rezaem : I have tested the pull request #1044 against Azure SQL server. The PR #1044 has the issue from #493 resolved. I ran the original issue code with  "userFmtOnly=true" added to mssql_jdbc_test_connection_properties, and had getParameterMetaData() returning SQLServerParameterMetaData as expected.
thank you

@rene-ye #493 is resolved by the PR. Thanks @vborisoff

#1044 has been merged and will be available starting next release, closing the issue.


Make incremental entity providers more resilient to failed data sources

Signed-off-by: Damon Kaswell<EMAIL_ADDRESS>Hey, I just made a Pull Request!
This is a minor update to introduce the concept of a REMOVAL_THRESHOLD to incremental entity providers. The threshold is the maximum percentage (currently set to 5%) of entities managed by a given entity provider that it is permitted to remove at the end of the ingestion cycle.
For example, if Backstage is ingesting entities from a flaky API that sometimes returns 0 records or a null cursor when it shouldn't, it's possible for the computeRemoved method to inadvertently mark all or most entities managed by the provider for removal. The REMOVAL_THRESHOLD mechanism causes the provider to avoid removing anything if the process would otherwise remove more than 5% of the total entities managed by the provider.
No other functionality is modified.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

A quick first thought on this:
When merging the previous PR, i commented that I really would prefer to make this module not read catalog-internal tables at all. It's just too easy to inadvertently break things across module boundaries and it's an unfortunate data dependency to have. This PR now digs further down along that path.
Could we instead make it so that this compares to the previous ingestion in your own tables? The final_entities table is by its very nature a very bad index to rely on for this, because of the eventually consistent nature of things. The only thing you can safely rely on is your own track record.
On top of that - is it unfortunate to set a threshold this low? I'm not sure that there's a lot of room for accidental behaviours that are that much of a "grey area". Previous times where we've been defensive along these lines, we just disallowed having exactly zero items ingested, otherwise letting it through. I have a hard time figuring a source dropping 5% of items stealthily and us wanting to catch that and at the same time being able to avoid false negatives when valid modifications to the source system are made. Is there some prior accident that happened that led to this code being added?

A quick first thought on this:
When merging the previous PR, i commented that I really would prefer to make this module not read catalog-internal tables at all. It's just too easy to inadvertently break things across module boundaries and it's an unfortunate data dependency to have. This PR now digs further down along that path.
Could we instead make it so that this compares to the previous ingestion in your own tables? The final_entities table is by its very nature a very bad index to rely on for this, because of the eventually consistent nature of things. The only thing you can safely rely on is your own track record.

This... is definitely possible. Since each ingestion run maintains its own set of entities, I suppose we could query the ingestion_mark_entities table for entities that were ingested in the prior run and use that instead. I do like the idea of segmenting our work away from the core tables as much as possible. I'll rework this PR to do that.

On top of that - is it unfortunate to set a threshold this low? I'm not sure that there's a lot of room for accidental behaviours that are that much of a "grey area". Previous times where we've been defensive along these lines, we just disallowed having exactly zero items ingested, otherwise letting it through. I have a hard time figuring a source dropping 5% of items stealthily and us wanting to catch that and at the same time being able to avoid false negatives when valid modifications to the source system are made. Is there some prior accident that happened that led to this code being added?

Bingo. We encountered a persistent issue with misbehaving data sources that should error out, but instead would return what looked like legitimate responses with nothing in them.
Would it make sense to make the threshold configurable and optional?

Would it make sense to make the threshold configurable and optional?

Maybe just a rejectEmptyEntityCollections?: boolen parameter on the thing?

Would it make sense to make the threshold configurable and optional?

Maybe just a rejectEmptyEntityCollections?: boolean parameter on the thing?

How about both? For the simple case of "please don't delete all of my entities if the data source failed completely but said it was successful," we could use the boolean. For people who want a little more control, we could have the threshold.

Sure. And it would probably be good to put them both as (optional) options on the constructor, so that it's adjustable from the outside.
rejectEmptySourceCollections?: boolean and rejectRemovalsAbovePercentage?: number or something like that?

Sure. And it would probably be good to put them both as (optional) options on the constructor, so that it's adjustable from the outside.
rejectEmptySourceCollections?: boolean and rejectRemovalsAbovePercentage?: number or something like that?

Done! And I used those names, because those are good and descriptive.


[PORT] Fix LuisRecognizer to not return intents if there is no utterance

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/4129

Fixes #4117
Description
Luis Recognizer returns an intent of string.empty with a perfect score of 1.0.  This messes up logic downstream in RecognizerSet because it thinks it has a perfect intent.
Specific Changes

Changed LuisRecognizer to return empy RecognizerResult (no intents or entities) when there is no utterance.

Changed projects

Microsoft.Bot.Builder.AI.LUIS
Microsoft.Bot.Builder.Dialogs.Adaptive
Microsoft.Bot.Builder.AI.LUIS.Tests

Added PR for the same #1387


 This is a godsend for trying to write E2E tests.
I tried following the instructions about Duplicating the tab, but whatever I do, the "Protractor" tab is always either blank, or says "No Properties"

Same here. :(

Create a duplicate tab and start using elementor, it loads suggestions.


should not call return new Promise((resolve, reject) => {

In the https://github.com/btomashvili/react-redux-firebase-boilerplate/blob/master/src/app/utils/firebase.js each method is constructing a new promise to return. This is a bad practice when you're internally calling functions which return a promise already. You should just chain your promises.

@capaj  Thanks for your feedback. Will be fixed ;)

@btomashvili thanks, much nicer now.


feat: Use new sort for licensed sales GRO-831

This PR updates the auctions page to use the new sort and boost licensed sales.
https://artsyproduct.atlassian.net/browse/GRO-831
/cc @artsy/grow-devs

looks good!
#mergeOnGreen


Add submariner-gateway role permissions for leases

This is needed for leader election resource locking in K8s 0.24.

This doesn't need to be backported if the code changes aren't also backported.


color in log file

Hi David,
I tested your module and code and the console output is in colors, but the log file is not (on my CentOS Linux).
Can you tell why?
Thanks,
Lavi

The repository offers two formatters: ColorizedArgsFormatter and BraceFormatStyleFormatter.
ColorizedArgsFormatter supports both {} brace-style formatting and logging in colors with ANSI escape sequences.
BraceFormatStyleFormatter only supports {} brace-style formatting
The example provided uses BraceFormatStyleFormatter for file handler in purpose so that escape codes will not appear in the log files. However, you can just replace it to ColorizedArgsFormatter and you will get colors (or at least their escape codes) in log files.

Thanks, will check it out!
From: David Ohana<EMAIL_ADDRESS>Sent: Monday, July 13, 2020 3:44 PM
To: davidohana/colargulog<EMAIL_ADDRESS>Cc: Lavi Buchnik<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [davidohana/colargulog] color in log file (#1)
CAUTION: EXTERNAL Email.
The repository offers two formatters: ColorizedArgsFormatter and BraceFormatStyleFormatter.
ColorizedArgsFormatter supports both {} brace-style formatting and logging in colors with ANSI escape sequences.
BraceFormatStyleFormatter only supports {} brace-style formatting
The example provided uses BraceFormatStyleFormatter for file handler in purpose so that escape codes will not appear in the log files. However, you can just replace it to ColorizedArgsFormatter and you will get colors (or at least their escape codes) in log files.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/davidohana/colargulog/issues/1*issuecomment-657538253__;Iw!!NkSChLMW7qAT!tSDkHB5nSBNWcfsBFr3zupnglfB6fnK3YcrXlwVMyXpuISssMP7_W97dKZsz4jsJIIRbmGfO$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ACLHNEAGITRM7RNFKG7BK2TR3L6QPANCNFSM4OYKOHZA__;!!NkSChLMW7qAT!tSDkHB5nSBNWcfsBFr3zupnglfB6fnK3YcrXlwVMyXpuISssMP7_W97dKZsz4jsJIATuP3h_$.

Hi David,
Working like a charm. Thanks for writing it and replying back.
BR,
Lavi


tedge-mapper must send the init messages to cloud only after checking the bridge status

Is your feature improvement request related to a problem? Please describe.
The tedge-mapper-c8y sends the init messages to the Cumulocity cloud when it starts for the first time
These messages like  inventory_fragments_message,  supported_operations_message,  device_data_message,            pending_operations_message, cloud_child_devices_message.
The mapper depends on the mqtt bridge to communicate with the cumulocity cloud. In the current implementation, these messages are sent without checking the bridge status., whether the bridge is established or not. So, if the bridge is not established the messages will be lost. This will have a bad experience for the further operation of thin-edge.io.
Describe the solution you'd like
The proposed solution is first to check that the bridge is established or not before sending out the init messages that are mentioned above. If the bridge is not established, then the mapper must defer and wait till the bridge gets established.
Mapper can subscribe to tedge/health/mosquitto-c8y-bridge topic to check the health status of the bridge.
The init message can be sent either the status of the bridge is up/down. That means the bridge must be established, if its not up at present then the Mosquitto broker can buffer those messages and can deliver once it comes up.
Describe alternatives you've considered

Additional context
This will be helpful when the thin-edge components run on different containers. For example tedge-mapper running on an independent container than the mosquitto broker in another then will be more useful.

@albinsuresh is this now covered after merging https://github.com/thin-edge/thin-edge.io/pull/2695

Yes, it is already addressed in #2695. Closing the issue.


Cluster not available while snapshotting leading to inconsistent updates

I have several problems:

Frequent timeouts: (header timeout is 10 seconds) still seems to occur around snapshots.
It seems that a PUT(key1, val1) on etcd1 timed out, a subsequent put (key1, val2) succeeds, and then it the original PUT(key1, val1) is applied on top of it leading to an inconsistent value val2.

Logs are included. The times on all etcds are synchronized.
related  https://github.com/coreos/etcd/issues/5130 (etcd upgraded to 2.3.5)

etcd Version: 2.3.5
Git SHA: a535dc9
Go Version: go1.6.2
Go OS/Arch: linux/amd64

Here's an instance of the 2 problems with logs from all etcds
Error message from etcd client

time="2016-05-28T04:29:17Z" level=error msg=" client: etcd cluster is unavailable or misconfigured error #0: client: endpoint http://etcd1:4001 exceeded header timeout\nerror #1: client: endpoint http://etcd2:4001 exceeded header timeout\nerror #2: client: endpoint http://etcd3:4001

ETCD 1
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2339] ignored a MsgVote message with lower term from 5d810f2e22e40331 [term: 2337]
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: 9a35171390025721 received vote from 2433079c1a52e50c at term 2339
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [quorum:2] has received 2 votes and 0 vote rejections
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became leader at term 2339
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: raft.node: 9a35171390025721 elected leader 9a35171390025721 at term 2339
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: failed to read 5d810f2e22e40331 on stream MsgApp v2 (read tcp <IP_ADDRESS>:50186-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:28:09 ip-10-0-0-123 etcd[28442]: the connection with 5d810f2e22e40331 became inactive
May 28 04:28:10 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2339] received a MsgVote message with higher term from 2433079c1a52e50c [term: 2340]
May 28 04:28:10 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became follower at term 2340
May 28 04:28:10 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208, vote: 0] rejected vote from 2433079c1a52e50c [logterm: 2336, index
May 28 04:28:10 ip-10-0-0-123 etcd[28442]: raft.node: 9a35171390025721 lost leader 9a35171390025721 at term 2340
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became active
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 5d810f2e22e40331 became active
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the clock difference against peer 2433079c1a52e50c is too high [3.921781879s > 1s]
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: failed to write 2433079c1a52e50c on stream Message (write tcp <IP_ADDRESS>:2380-><IP_ADDRESS>:38545: write: broken pipe)
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became inactive
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: failed to heartbeat 5d810f2e22e40331 on stream MsgApp v2 (write tcp <IP_ADDRESS>:2380-><IP_ADDRESS>:60648: write: broken
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 5d810f2e22e40331 became inactive
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 5d810f2e22e40331 became active
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became active
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: got unexpected response error (etcdserver: request timed out) [merged 2 repeated lines in 11.33s]
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: failed to write 2433079c1a52e50c on stream MsgApp v2 (write tcp <IP_ADDRESS>:2380-><IP_ADDRESS>:38546: write: broken pip
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became inactive
May 28 04:28:11 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became active
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: 9a35171390025721 is starting a new election at term 2340
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became candidate at term 2341
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: 9a35171390025721 received vote from 9a35171390025721 at term 2341
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208] sent vote request to 2433079c1a52e50c at term 2341
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208] sent vote request to 5d810f2e22e40331 at term 2341
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: failed to read 5d810f2e22e40331 on stream Message (read tcp <IP_ADDRESS>:50185-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:28:14 ip-10-0-0-123 etcd[28442]: the connection with 5d810f2e22e40331 became inactive
May 28 04:28:15 ip-10-0-0-123 etcd[28442]: failed to read 2433079c1a52e50c on stream Message (read tcp <IP_ADDRESS>:42098-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:28:15 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became inactive
May 28 04:28:21 ip-10-0-0-123 etcd[28442]: got unexpected response error (etcdserver: request timed out)
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became active
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 is starting a new election at term 2341
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became candidate at term 2342
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 received vote from 9a35171390025721 at term 2342
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208] sent vote request to 2433079c1a52e50c at term 2342
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208] sent vote request to 5d810f2e22e40331 at term 2342
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208, vote: 9a35171390025721] rejected vote from 2433079c1a52e50c [logte
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: got unexpected response error (etcdserver: request timed out) [merged 6 repeated lines in 35.14s]
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: the connection with 5d810f2e22e40331 became active
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: got unexpected response error (etcdserver: request timed out) [merged 3 repeated lines in 3.88s]
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2342] ignored a MsgVote message with lower term from 2433079c1a52e50c [term: 2341]
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2342] ignored a MsgVote message with lower term from 5d810f2e22e40331 [term: 2338]
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: the clock difference against peer 5d810f2e22e40331 is too high [31.682759642s > 1s]
May 28 04:29:00 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2342] ignored a MsgVoteResp message with lower term from 5d810f2e22e40331 [term: 2341]
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: saved snapshot at index 11612187
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: got unexpected response error (etcdserver: request timed out)
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2342] received a MsgVote message with higher term from 5d810f2e22e40331 [term: 2343]
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: compacted raft log at 11607187
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became follower at term 2343
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208, vote: 0] rejected vote from 5d810f2e22e40331 [logterm: 2336, index
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2343] received a MsgVote message with higher term from 5d810f2e22e40331 [term: 2344]
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became follower at term 2344
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208, vote: 0] rejected vote from 5d810f2e22e40331 [logterm: 2336, index
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2344] received a MsgVote message with higher term from 5d810f2e22e40331 [term: 2345]
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became follower at term 2345
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208, vote: 0] rejected vote from 5d810f2e22e40331 [logterm: 2336, index
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: failed to read 2433079c1a52e50c on stream Message (read tcp <IP_ADDRESS>:42108-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:29:21 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became inactive
May 28 04:29:23 ip-10-0-0-123 etcd[28442]: got unexpected response error (etcdserver: request timed out) [merged 9 repeated lines in 1.44s]
May 28 04:29:26 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2345] received a MsgVote message with higher term from 5d810f2e22e40331 [term: 2346]
May 28 04:29:26 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became follower at term 2346
May 28 04:29:26 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208, vote: 0] rejected vote from 5d810f2e22e40331 [logterm: 2336, index
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 is starting a new election at term 2346
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became candidate at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 received vote from 9a35171390025721 at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208] sent vote request to 2433079c1a52e50c at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [logterm: 2339, index: 11612208] sent vote request to 5d810f2e22e40331 at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 received vote from 5d810f2e22e40331 at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [quorum:2] has received 2 votes and 0 vote rejections
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: 9a35171390025721 became leader at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: raft.node: 9a35171390025721 elected leader 9a35171390025721 at term 2347
May 28 04:29:30 ip-10-0-0-123 etcd[28442]: purged file /var/lib/etcd/ox.etcd/member/snap/00000000000008c7-0000000000b06aa5.snap successfully
May 28 04:29:49 ip-10-0-0-123 etcd[28442]: the connection with 2433079c1a52e50c became active
May 28 04:29:53 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2347] ignored a MsgVoteResp message with lower term from 2433079c1a52e50c [term: 2342]
May 28 04:29:53 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2347] ignored a MsgApp message with lower term from 2433079c1a52e50c [term: 2342]
May 28 04:29:53 ip-10-0-0-123 etcd[28442]: 9a35171390025721 [term: 2347] ignored a MsgHeartbeat message with lower term from 2433079c1a52e50c [term: 2342]

ETCD2
May 28 04:29:48 ip-10-0-2-150 etcd[28308]: the connection with 9a35171390025721 became active
My 28 04:27:47 ip-10-0-2-150 etcd[28308]: the connection with 5d810f2e22e40331 became inactive
May 28 04:28:15 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out)
May 28 04:28:20 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c is starting a new election at term 2340
May 28 04:28:22 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c became candidate at term 2341
May 28 04:28:22 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c received vote from 2433079c1a52e50c at term 2341
May 28 04:28:22 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2336, index: 11612206] sent vote request to 9a35171390025721 at term 2341
May 28 04:28:22 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2336, index: 11612206] sent vote request to 5d810f2e22e40331 at term 2341
May 28 04:28:24 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out) [merged 2 repeated lines in 5.98s]
May 28 04:28:52 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out)
May 28 04:28:52 ip-10-0-2-150 etcd[28308]: the connection with 9a35171390025721 became active
May 28 04:28:55 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out) [merged 7 repeated lines in 1.04s]
May 28 04:28:55 ip-10-0-2-150 etcd[28308]: the clock difference against peer 5d810f2e22e40331 is too high [21.972643202s > 1s]
May 28 04:28:55 ip-10-0-2-150 etcd[28308]: the clock difference against peer 9a35171390025721 is too high [8.41104543s > 1s]
May 28 04:28:55 ip-10-0-2-150 etcd[28308]: purged file /var/lib/etcd/ox.etcd/member/snap/00000000000008ca-0000000000b06bde.snap successfully
May 28 04:28:56 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c is starting a new election at term 2341
May 28 04:28:56 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c became candidate at term 2342
May 28 04:28:56 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c received vote from 2433079c1a52e50c at term 2342
May 28 04:28:56 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2336, index: 11612206] sent vote request to 5d810f2e22e40331 at term 2342
May 28 04:28:56 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2336, index: 11612206] sent vote request to 9a35171390025721 at term 2342
May 28 04:28:57 ip-10-0-2-150 etcd[28308]: failed to dial 9a35171390025721 on stream MsgApp v2 (read tcp <IP_ADDRESS>:38559-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:28:57 ip-10-0-2-150 etcd[28308]: the connection with 9a35171390025721 became inactive
May 28 04:29:48 ip-10-0-2-150 etcd[28308]: saved snapshot at index 11611991
May 28 04:29:48 ip-10-0-2-150 etcd[28308]: the connection with 9a35171390025721 became active
May 28 04:29:48 ip-10-0-2-150 etcd[28308]: saved snapshot at index 11611991
May 28 04:29:49 ip-10-0-2-150 etcd[28308]: the connection with 5d810f2e22e40331 became active
May 28 04:29:49 ip-10-0-2-150 etcd[28308]: compacted raft log at 11606991
May 28 04:29:49 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2336, index: 11612206, vote: 2433079c1a52e50c] rejected vote from 9a35171390025721 [logterm: 2339, index: 11612208] at term 2342
May 28 04:29:49 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2342] ignored a MsgVoteResp message with lower term from 5d810f2e22e40331 [term: 2341]
May 28 04:29:49 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c received vote from 5d810f2e22e40331 at term 2342
May 28 04:29:49 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [quorum:2] has received 2 votes and 0 vote rejections
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out)
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: the clock difference against peer 5d810f2e22e40331 is too high [37.874101903s > 1s]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: the clock difference against peer 9a35171390025721 is too high [39.922149257s > 1s]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c became leader at term 2342
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: raft.node: 2433079c1a52e50c elected leader 2433079c1a52e50c at term 2342
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2342] received a MsgVote message with higher term from 5d810f2e22e40331 [term: 2343]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c became follower at term 2343
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2342, index: 11612211, vote: 0] rejected vote from 5d810f2e22e40331 [logterm: 2336, index: 11612165] at term 2343
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: raft.node: 2433079c1a52e50c lost leader 2433079c1a52e50c at term 2343
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2343] ignored a MsgVoteResp message with lower term from 9a35171390025721 [term: 2342]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2343] received a MsgHeartbeat message with higher term from 9a35171390025721 [term: 2347]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c became follower at term 2347
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: raft.node: 2433079c1a52e50c elected leader 9a35171390025721 at term 2347
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [logterm: 2342, index: 11612211, vote: 0] rejected vote from 9a35171390025721 [logterm: 2339, index: 11612208] at term 2347
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2347] ignored a MsgVote message with lower term from 5d810f2e22e40331 [term: 2344]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2347] ignored a MsgVote message with lower term from 5d810f2e22e40331 [term: 2345]
May 28 04:29:50 ip-10-0-2-150 etcd[28308]: 2433079c1a52e50c [term: 2347] ignored a MsgVote message with lower term from 5d810f2e22e40331 [term: 2346]
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: failed to send out heartbeat on time (deadline exceeded for 3m1.860312969s)
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: server is likely overloaded
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: failed to send out heartbeat on time (deadline exceeded for 2m46.754982957s)
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: server is likely overloaded
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out) [merged 8 repeated lines in 1.01s]
May 28 04:29:52 ip-10-0-2-150 etcd[28308]: failed to read 9a35171390025721 on stream MsgApp v2 (http: unexpected EOF reading trailer)
May 28 04:29:52 ip-10-0-2-150 etcd[28308]: the connection with 9a35171390025721 became inactive
May 28 04:29:52 ip-10-0-2-150 etcd[28308]: the connection with 9a35171390025721 became active
May 28 04:29:54 ip-10-0-2-150 etcd[28308]: found conflict at index 11612207 [existing term: 2342, conflicting term: 2336]
May 28 04:29:54 ip-10-0-2-150 etcd[28308]: replace the unstable entries from index 11612207
May 28 04:30:00 ip-10-0-2-150 etcd[28308]: etcdserver: request timed out, possibly due to previous leader failure
May 28 04:30:01 ip-10-0-2-150 etcd[28308]: etcdserver: request timed out, possibly due to previous leader failure [merged 3 repeated lines in 1.29s]
May 28 05:25:38 ip-10-0-2-150 etcd[28308]: start to snapshot (applied: 11621992, lastsnap: 11611991)
May 28 05:26:18 ip-10-0-2-150 etcd[28308]: got unexpected response error (etcdserver: request timed out)
May 28 05:26:21 ip-10-0-2-150 etcd[28308]: failed to heartbeat 5d810f2e22e40331 on stream MsgApp v2 (write tcp <IP_ADDRESS>:2380-><IP_ADDRESS>:54081: write: broken pipe)

ETCD3
May 28 04:27:43 ip-10-0-4-26 etcd[27048]: the connection with 9a35171390025721 became inactive
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: the connection with 9a35171390025721 became active
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: publish error: etcdserver: request timed out
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out)
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 is starting a new election at term 2337
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became candidate at term 2338
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 received vote from 5d810f2e22e40331 at term 2338
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 2433079c1a52e50c at term 2338
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 9a35171390025721 at term 2338
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2338] received a MsgVote message with higher term from 2433079c1a52e50c [term: 2340]
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became follower at term 2340
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165, vote: 0] voted for 2433079c1a52e50c [logterm: 2336, index: 11612206] at term 2340
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2340] received a MsgVote message with higher term from 9a35171390025721 [term: 2341]
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became follower at term 2341
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165, vote: 0] voted for 9a35171390025721 [logterm: 2339, index: 11612208] at term 2341
May 28 04:28:24 ip-10-0-4-26 etcd[27048]: the clock difference against peer 9a35171390025721 is too high [10.56462006s > 1s]
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: the clock difference against peer 9a35171390025721 is too high [10.56462006s > 1s]
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: failed to heartbeat 2433079c1a52e50c on stream Message (write tcp <IP_ADDRESS>:2380-><IP_ADDRESS>:33867: write: broken pipe)
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: the connection with 2433079c1a52e50c became inactive
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: publish error: etcdserver: request timed out
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out) [merged 4 repeated lines in 8.28s]
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out) [merged 15 repeated lines in 27.11s]
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: failed to read 9a35171390025721 on stream Message (read tcp <IP_ADDRESS>:60653-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: the connection with 9a35171390025721 became inactive
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165, vote: 9a35171390025721] rejected vote from 2433079c1a52e50c [logterm: 2336, index: 11612206] at term 2341

May 28 04:29:02 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2341] received a MsgVote message with higher term from 2433079c1a52e50c [term: 2342]
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became follower at term 2342May 28 04:29:02 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165, vote: 0] voted for 2433079c1a52e50c [logterm: 2336, index: 11612206] at term 2342
May 28 04:29:02 ip-10-0-4-26 etcd[27048]: the connection with 2433079c1a52e50c became active
May 28 04:29:09 ip-10-0-4-26 etcd[27048]: failed to read 2433079c1a52e50c on stream MsgApp v2 (read tcp <IP_ADDRESS>:54046-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:29:09 ip-10-0-4-26 etcd[27048]: the connection with 2433079c1a52e50c became inactive
May 28 04:29:11 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 is starting a new election at term 2342
May 28 04:29:11 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became candidate at term 2343
May 28 04:29:11 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 received vote from 5d810f2e22e40331 at term 2343
May 28 04:29:11 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 2433079c1a52e50c at term 2343
May 28 04:29:11 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 9a35171390025721 at term 2343
May 28 04:29:13 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out)
May 28 04:29:13 ip-10-0-4-26 etcd[27048]: publish error: etcdserver: request timed out
May 28 04:29:14 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out) [merged 13 repeated lines in 1.47s]
May 28 04:29:15 ip-10-0-4-26 etcd[27048]: saved snapshot at index 11612165
May 28 04:29:15 ip-10-0-4-26 etcd[27048]: compacted raft log at 11607165
May 28 04:29:16 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 is starting a new election at term 2343
May 28 04:29:16 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became candidate at term 2344
May 28 04:29:16 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 received vote from 5d810f2e22e40331 at term 2344
May 28 04:29:16 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 2433079c1a52e50c at term 2344
May 28 04:29:16 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 9a35171390025721 at term 2344
May 28 04:29:20 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out)
May 28 04:29:20 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 is starting a new election at term 2344
May 28 04:29:20 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became candidate at term 2345
May 28 04:29:20 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 received vote from 5d810f2e22e40331 at term 2345
May 28 04:29:20 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 2433079c1a52e50c at term 2345
May 28 04:29:20 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 9a35171390025721 at term 2345
May 28 04:29:21 ip-10-0-4-26 etcd[27048]: the connection with 9a35171390025721 became active
May 28 04:29:21 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out) [merged 2 repeated lines in 1.26s]
May 28 04:29:23 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out) [merged 1 repeated lines in 2s]
May 28 04:29:24 ip-10-0-4-26 etcd[27048]: publish error: etcdserver: request timed out
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 is starting a new election at term 2345
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became candidate at term 2346
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 received vote from 5d810f2e22e40331 at term 2346
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 2433079c1a52e50c at term 2346
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165] sent vote request to 9a35171390025721 at term 2346
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 received vote rejection from 9a35171390025721 at term 2346
May 28 04:29:26 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [quorum:2] has received 1 votes and 1 vote rejections
May 28 04:29:27 ip-10-0-4-26 etcd[27048]: got unexpected response error (etcdserver: request timed out)
May 28 04:29:30 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2346] received a MsgVote message with higher term from 9a35171390025721 [term: 2347]
May 28 04:29:30 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 became follower at term 2347
May 28 04:29:30 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [logterm: 2336, index: 11612165, vote: 0] voted for 9a35171390025721 [logterm: 2339, index: 11612208] at term 2347
May 28 04:29:30 ip-10-0-4-26 etcd[27048]: raft.node: 5d810f2e22e40331 elected leader 9a35171390025721 at term 2347
May 28 04:29:30 ip-10-0-4-26 etcd[27048]: published {Name:etcdd ClientURLs:[http://4001]} to cluster 28f83de0b4b59355
May 28 04:29:32 ip-10-0-4-26 etcd[27048]: the clock difference against peer 2433079c1a52e50c is too high [5.53732623s > 1s]
May 28 04:29:32 ip-10-0-4-26 etcd[27048]: purged file /var/lib/etcd/porx.etcd/member/snap/00000000000008c7-0000000000b06ae0.snap successfully
May 28 04:29:49 ip-10-0-4-26 etcd[27048]: the connection with 2433079c1a52e50c became active
May 28 04:29:53 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2347] ignored a MsgApp message with lower term from 2433079c1a52e50c [term: 2342]
May 28 04:29:53 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2347] ignored a MsgHeartbeat message with lower term from 2433079c1a52e50c [term: 2342]
May 28 04:29:53 ip-10-0-4-26 etcd[27048]: 5d810f2e22e40331 [term: 2347] ignored a MsgVoteResp message with lower term from 2433079c1a52e50c [term: 2343]
May 28 04:29:55 ip-10-0-4-26 etcd[27048]: failed to read 2433079c1a52e50c on stream MsgApp v2 (read tcp <IP_ADDRESS>:54080-><IP_ADDRESS>:2380: i/o timeout)
May 28 04:29:55 ip-10-0-4-26 etcd[27048]: the connection with 2433079c1a52e50c became inactive
May 28 04:29:55 ip-10-0-4-26 etcd[27048]: the connection with 2433079c1a52e50c became active

@coozy What do you mean by inconsistent state? How can I reproduce the issues you mentioned above?

@coozy
Also there is something really bad happened to your machine probably.
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: failed to send out heartbeat on time (deadline exceeded for 3m1.860312969s)

This means that sever go routines was unresponsive for server minutes.
Also etcd was reporting time difference between your machines. If you are sure the time is synced, then it means the requests processing time is very long.
We are testing etcd 2.3.5 under extreme high workload, and never see this issue. My best suggestion for you right now is to check your own environment. Or if you have reliably reproduce this issue on any specific cloud virtual or bare-mental environment, we can look into it.

@coozy Moreover, the snapshot took more than a minute or so to finish, either your machine is too slow or you put unreasonable amount of data into etcd2.
etcd2 can hold as much as several 100s of MB of data. See https://github.com/coreos/etcd/blob/master/Documentation/benchmarks/etcd-2-2-0-rc-memory-benchmarks.md#data-size-threshold

Inconsistent because
t1:  etcdclient->etcd1 update (key1, foo)
t2: etcdclient timesout (presumably because etcd1 is snapshotting..)
t3: etcdclient->etcd2 delete (key1) succeeds
t4: etcd1 finishes snapshot or whatever it was doing
And it updates key1, with foo
t5: I have key1 with foo, I expect key1 to not exist
You should be able to repro by artificially pausing everything after you get a put request including heartbeats, get kicked out the cluster, wake up and process the put the request.
(Correct implementation would be to drop all pending requests if you got kicked out of the cluster)

This happens all the time
May 28 04:29:51 ip-10-0-2-150 etcd[28308]: failed to send out heartbeat on time (deadline exceeded for 3m1.860312969s)`

Try this for testing:
for i in {1..1000000};  do
rand1=$RANDOM;
rand2=$RANDOM;
 /bin/etcdctl  --endpoints "http://etcd1:4001,http://etcd2:4001,http://etcd3:4001"  set /test/test$i-$rand1-$rand2 "ABCDEFGHIJKLMNOPQRSTUVWXYXZ-ABCDEFGHIJKLMNOPQRSTUVWXYXZ-ABCDEFGHIJKLMNOPQRSTUVWXYXZ-ABCDEFGHIJKLMNOPQRSTUVWXYXZ-
ABCDEFGHIJKLMNOPQRSTUVWXYXZ-ABCDEFGHIJKLMNOPQRSTUVWXYXZ-ABCDEFGHIJKLMNOPQRSTUVWXYXZ-$rand";
done

The amount of data is a little bit on the high side - around 100MB? This is on EC2 with EBS. So yes probably slow and I move to provisioned IOPS too.
I think the snapshot mechanism is inefficient, a real snap should be literally a No-op. Perhaps you could leverage snaps at the block device or provide hooks for someone to provide that?

@coozy

Inconsistent because:

That is not inconsistent. That is just that update request was slowly being processed and finished after the delete.

May 28 04:29:51 ip-10-0-2-150 etcd[28308]: failed to send out heartbeat on time (deadline exceeded for 3m1.860312969s)`

Please check your environment. This is abnormal and I believe there is something wrong on your environment if this happens all the time.

I think the snapshot mechanism is inefficient, a real snap should be literally a No-op. Perhaps you could leverage snaps at the block device or provide hooks for someone to provide that?

It is not a no-op and I do not know why you think it is a no-op. The snapshot has nothing to do what kind of file-system or device you use. It is just how etcd2 works to save its in-memory data structure onto disk. There are ways to improve that. For etcd3, we already do incremental snapshot. However, it will never be a no-op as you described.

@coozy
You need to get a stable environment that etcd cluster can run without printing ANY warning/errors. Then you need to know the exact IOPS that the environment can handle. Then you can start to benchmark etcd2. Also remember that etcd2 cannot handle more than 100MB data or more than 300K keys.

@xiang90 thanks for following up.

Inconsistent because:

That is not inconsistent. That is just that update request was slowly being processed and finished after the delete.

As far as the client is concerned it is inconsistent -> the updates were A-> B and the result is A.  "Write order fidelity" is something that I would expect from a key value store.

You need to get a stable environment that etcd cluster can run without printing ANY warning/errors.

I'd love to and that's what I am trying to do :)  I have reset our etcd cluster and will ensure that we stick to the limits.

"Write order fidelity"

This can only be ensured if the previous write successfully returns. Or the write/read is on the same client. Other than that, you have to use index to argue about the ordering.

I'd love to and that's what I am trying to do :)

If you really need to put a lot of data, try etcd3. It scales at least 10x better.
Cloud environment can be trick especially on AWS, where enables some burst CPU/IO and will eventually slow any systems down like crazy when the credits used up.

I have reset our etcd cluster and will ensure that we stick to the limits.

These limited are measured by using machines similar to https://github.com/coreos/etcd/blob/master/Documentation/benchmarks/etcd-2-2-0-rc-memory-benchmarks.md#physical-machine.
Let us know if you still hit the same issue if you limit the #keys and size of the total data.
Thanks!


bridge doesn't work with DHCP

With podman version 4.7.2, netavark version 1.8.0:
macvlan driver works with DHCP:
# podman network create --disable-dns --driver macvlan --interface-name brint --ipam-driver dhcp lan
lan
# podman run -it --rm --network=lan alpine ip addr show eth0
2: eth0@if8: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 4e:81:42:14:17:be brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::4c81:42ff:fe14:17be/64 scope link tentative
       valid_lft forever preferred_lft forever

(note assigned <IP_ADDRESS> address there)
But bridge does not:
# podman network rm lan
# podman network create --disable-dns --driver bridge --interface-name brint --ipam-driver dhcp lan
lan
# podman run -it --rm --network=lan alpine ip addr show eth0
2: eth0@if28: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether c6:9b:3d:ec:27:6c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::c49b:3dff:feec:276c/64 scope link tentative
       valid_lft forever preferred_lft forever

Is this configuration supportable?
(For my setup, I need bridge instead of macvlan so that the host can communicate with the container too.  I can work around it with --cap-add NET_ADMIN,NET_RAW and running udhcpc inside the container, but would prefer to avoid that if possible.)

Actually this seems straightforward to support: #869


Publicize non-zero weierstrass affine variables

Description
I've found these to be useful for a recent project.
I also added an EqGadget implementation and a test.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Wrote unit tests
[x] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

Sorry for the delay; I was out-of-town.
We were working with a prime-order curve and had a large computation that could produce intermediate zeros with only negligible probability.


aadHttpClientFactory uses old refresh tokens in Teams Desktop Client

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[X] other (enter in the "Additional environment details" area below)

Additional environment details

browser version : Microsoft Teams Desktop Client
SPFx version: v1.10.0
Node.js version: v10.13.0
etc

Issue description
We have a SPFx Application built which uses aadHttpClientFactory to consume Azure AD protected Function Apps. The SPFx application works fine in SharePoint pages. We have created a Teams Tab using Teams App Studio. This Teams Tab just displays the SharePoint Page where the SPFx application is hosted.
We have an issue where the API calls are failing with the below error for some users
AADSTS70043: The refresh token has expired or is invalid due to sign-in frequency checks by conditional access. The token was issued on 2022-11-21T14:40:56.1540000Z and the maximum allowed lifetime for this request is 10800.
Trace ID: b0b9a151-8384-6406-8f49-bae28bddff00
Correlation ID: 3d017ca0-7ab3-d000-9c57-7401f6hj615e
Timestamp: 2022-11-25 08:28:28Z
Teams Desktop client uses old cached tokens and not getting refreshed even though the SharePoint page containing the SPFx component loads fine.

@wizneeraj - thanks for reporting it!
Few questions.

Why did you create a custom app to display a SharePoint page instead of using OOB SharePoint app?
If you use OOB SharePoint app - will your web part work correctly?

@wizneeraj - could you please clarify at what point are you seeing this error?
Also - is there anything specific about the users that are getting the issue?

@AJIXuMuK - We see this issue for users when Conditional Access policy forces the users to reauthenticate. Once that happens, the issue will occur for the user, since it seems like either MS teams Desktop client is unable to provide the new Auth token or aadHttpClientFactory is not refreshing the token

@lucabandMSFT - I have shared the teams manifest with Maria and she will be able to share it with you.

hey @wizneeraj ,
I took a look at the manifest; it looks like the manifest doesn't follow the rules described here: https://learn.microsoft.com/en-us/sharepoint/dev/spfx/deployment-spfx-teams-solutions
The key part is to ensure the {teamSiteDomain} moniker is there instead of the url of the tenant. Please, when you have time, let me know if this resolves the issue.

I have already tried using the {teamSiteDomain} moniker and it did not work. To reproduce the issue, I have updated the Teams manifest with this moniker and the app version, to ensure we are testing in the latest version. Even now, i am able to replicate the issue. Also, the issue is not with the Teams Personal app, even if I use the SharePoint OOTB App in Teams and point it to the SharePoint Page containing the SPFx component, I am able to reproduce the issue.

@wizneeraj , thanks. Do you have an environment we can look at to see the issue? Is that something we can work with Maria on?


Chicks overgenerate feathers by a preposterous amount

Issue Description:
I'm running a custom modpack on 1.10.2 with this, More Chickens (1.1.6), and Hatchery (0.2.10) (and 115 other mods, formerly including ChickenShed). After I began amassing my chicken army - I mean uh, my darling livestock, I began to notice a rather overabundance of feathers. It got worse as I went along, and eventually I figured out that it was tied to the chicks. During their chickhood, they produce feathers at a blistering pace.
I thought ChickenShed was the culprit, so I messed with it for a long time, eventually removing it entirely. Now, playing without it, the problem remains. I have 15,000 feathers and I doubt I will ever use them all. I don't know what's going on or how to stop it. Please let me know what other information you might need!
Steps to reproduce (important):

Breed chickens OR
Hatch an egg
The resulting chick should be a prolific fount of feathers
...

What happens:

What you expected to happen:
Not this.

Affected Versions (Do not use "latest"):

Chickens: 4.3.2
Minecraft: 1.10.2
Forge: <IP_ADDRESS>7

Upon further inspection, I'm not 100% certain that it's JUST the chicks. It's insane though...

Others have reported this in my mod hatchery Seems to happen when the eggs hatch, but we haven't figured out whats causing it.  are you running sponge at all? maybe a mod list.. but lets move this over here
https://github.com/GenDeathrow/Hatchery/issues

also the only thing that gives feathers in hatchery or chickens in pens.. chickens mod doesn't give feathers at all. so Im not sure whats causing this.

They are definitely not in the pens when they're spewing feathers. Thanks for the response, do I need to repost or is the thread migrated automatically?

here https://github.com/GenDeathrow/Hatchery/issues/75

#117


Can not run arproof

I install ARP component in hassbian 0.92.2 step by step in arpspoof.markdown
after reboot pi
The log show error :
2019-05-13 06:39:06 ERROR (MainThread) [homeassistant.setup] Setup failed for arpspoof: No setup function defined.
2019-05-13 06:39:17 ERROR (Thread-14) [custom_components.arpspoof.switch] ARP component not initialised!

My file in custom_component is /arpspoof/
init.py
arpspoof.py
manifest.json
switch.py
how to fix it. thanks

Hi i had to drop the support for that one as it is not reliable see here


Add log level in the metadata

We are using the django integration with APM.
it would be useful to add the log level for the messages.
eg log.warning -> level:warning
eg log.error -> level:erorr
'handlers': {

    'elasticapm': {
            'level': 'WARNING',
            'class': 'elasticapm.contrib.django.handlers.LoggingHandler',
        },
}
...
    'loggers': {
       'mylog': {
            'handlers': ['console','elasticapm'],
            'level': 'DEBUG',
            'propagate': True
        },
}

right now there's no way to get if the log was a warning or an error

Hi @esseti
You can find the log level in the error.log.level of the error document in Elasticsearch. However, it indeed doesn't look like this information is visible anywhere in the APM app. I'll ask our UI team and get back to you.

@esseti we have an issue for this in Kibana now, https://github.com/elastic/kibana/issues/68748
I'll close this issue as the agent is already sending all the relevant information. Make sure to subscribe to the Kibana issue if you want to follow along with the progress.


Tower-cli config support in python

There is a python module 'tower-cli' available which allows to use tower-cli api in the scripts. But you can only make it work if you have tower-cli.cfg created locally with username, password, host, verify_ssl.
It would be a great to make it possible to set tower-cli configuration using this library somewhere as a part of:
import tower_cli
tower_cli.conf.Settings
so it is not needed to create either tower-cli.cfg or enter configuration manually from the command line.
(I am creating it after tracing this issue with ansible support, just in case :) )

I would like to get a better picture of the use story that is desired. Let's say that I am user admin and I want to create a new user inside of a python script. The following script should work, while also avoiding editing of the config file.
user_res = tower_cli.get_resource('user')

resp_json = user_res.create(
    username='new-user',
    password='pa$$word',
<EMAIL_ADDRESS>    tower_host="http://towerhost.company.com/",
    tower_username="admin",
    tower_password="pa$$word")

After this, you should be able to get the new user id from resp_json['id'] if the creation was successful. Are there any problems or bugs with using this method?
Is the idea that you would like to be able to edit tower-cli.cfg from the python script? Or is it that you would like to edit the config inside the script without saving to the config file?
Thanks for giving us feedback.

I tried the way you propose it when no tower-cli.cfg exists locally:

import tower_cli
def test_rest_get():
    user_res = tower_cli.get_resource('user')
    resp_json = user_res.create(
    username='library-demo',
    password='library9876',
<EMAIL_ADDRESS>    tower_host="https://example.com/",
    tower_username="NormalUser",
    tower_password="test")

It fails with:
'Could not establish a secure connection. ' ConnectionError: Could not establish a secure connection. Please add the server to your certificate authority. You can run this command without verifying SSL with the --insecure flag, or permanently disable verification by the config setting: tower-cli config verify_ssl false

Coming back to the initial use case.
I want to be able to use tower_cli.api package

from tower_cli import api
def test_rest_get():
    c = api.Client()
    response = c.get('projects')
    print response.json()['count']

This will work only if I have locally tower-cli.cfg.
I want to get this working without creating locally tower-cli.cfg (and I though that should be possible so you can fully automate usage of your python scripts).
By the way I also tried to create tower-cli.cfg using python subprocess. It did not work well, the configuration is not updated immediately. If you are interested in these results more, I can give more info.
To sum up:

is it possible to use tower-cli api in python without creating locally tower-cli.cfg?
if not, what is the proposed way to generate tower-cli.cfg within python?
[The use case would be: I want to use tower-cli in python to script tests, which are checking some test data for different users - admin. user, superuser. So it means I need to change tower-cli configuration for every test]

Thanks!

Got it. Thanks for the info, this should be enough to move on. So basically, we need a way to continue to execute a command without making a reference to the config file (or to manage a version cached in memory, like what was suggested in the original issue comment). I think this is a very reasonable expectation when using it as an import, which we do want to support.

My current approach is to do something like this at the beginning of my program:
    tower_cli.conf.settings._runtime.set("general", "host", host)
    tower_cli.conf.settings._runtime.set("general", "username", auth[0])
    tower_cli.conf.settings._runtime.set("general", "password", auth[1])
    tower_cli.conf.settings._cache.clear()

you can also do it like so
from tower_cli import get_resource
from tower_cli import conf

with conf.settings.runtime_values(host='https://mytower/', username='jdavila', password='NSAp00f', verify_ssl=True):
    usr_r = get_resource('user')
    print usr_r.list()

Let me link this Ansible module PR here:
https://github.com/ansible/ansible-modules-extras/pull/2810
Importing tower-cli as a dependency for this was under consideration. I think it would be good to resolve this issue first, to make the python usage a little bit more clear and more stable.

Also, believed to be solved by #266

Issue solved. Patch will ship with 3.1.1 release.


Prevent errors to be logged multiple times

How to categorize this PR?

/area quality
/kind enhancement
/priority normal
What this PR does / why we need it:
controller-runtime.Reconciler errors are logged by the framework. See https://github.com/kubernetes-sigs/controller-runtime/blob/198197fe0fd7553cadd8afcd3338f8ee4b8a7e3f/pkg/internal/controller/controller.go#L258. Currently we have cases in which given error is logged multiple times - once by the actuator in the extension controller, once by the reconciler in g/g and once by the controller-runtime.
This PR removes superfluous logging in the extension reconcilers when error is supposed to be logged by controller-runtime.
Which issue(s) this PR fixes:
Ref #2325
Special notes for your reviewer:
Release note:

Extension Reconcilers do no longer log the same error which the controller-runtime is supposed to log too. This should prevent given error to appear multiple times in the logs.

Extension controllers using `extensions/pkg/controller/error.RequeueAfterError` need to make sure that the cause error is properly logged on their side.

Out of curiosity: Why you don't use errors.Wrapf?

I have no strong opinion - if there is a convention/agreement to use errors.Wrap, I can adapt this PR.

I'm fine with both, no strong opinion.


[Question] rke2 vs k3s

Hi @vitobotta ,
What is the best kubernetes distribution for hetzner? I research on internet , k3s is the suitable for edge computing and Iot. Can I use k3s with 50 -100 workers in hetzner cloud? I want to install rancher, that is why which one to choose rke2 or k3s?

Hi, please use Discussions for things other than issues with the tool.
k3s is very lightweight which makes it ideal for devices with limited resources, but it's a fully conformant Kubernetes distribution and can be used for large clusters with big nodes etc if you want. It's entirely up to you.
RKE2 is very similar to k3s. AFAIK the biggest difference is some advanced security features that might make it more appealing for things like governments etc. But k3s is rock solid and easy to operatr.


Refactor Contribute Site

What needs to be done

Refactor so it is all in one codelab that is sibling to "Atmosphere Pro"
Add a "Setting up your Fork" section within that codelab so people can learn how to contribute to the docs site on their own machines
"Contribute to this site" remove uppercasing

Hey @ZeroDayOwl for this task, we were thinking of removing the nested dropdown.
So something like this:
Contribute to the atPlatform
> Atmosphere Pro
> Docs Site

It's a lot of refactoring and a lot more content re-writing, so that's why this wasn't made into a hacktoberfest ticket (since there's a lot of context that is not easy for others to pick up on).
But if you'd still like to tackle on this task, you are more than welcome! We appreciate all PRs :)

I would like to work on it

Hey @JeremyTubongbanua I got it, thanks!
I'll look into the task and try to fix it in the meantime :)

If there seems to be no progress on this, @JeremyTubongbanua  Could you please let me try and assign this to me?

Hey @kumar-kalyan @ZeroDayOwl @mathagician ! Thanks for your interest. Feel free to tackle this issue. (Sorry that I did not see this comment before, I don't know how I missed it).
Please try your best to create draft PRs with the closes: #187 in the PR description so that it will be linked to this issue.


Create CITATION.bib

Creates a CITATION.bib for standardized citation as per discussion on JuliaLang slack's #academia channel

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #1   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          31     31
=====================================
  Hits           31     31

Continue to review full report at Codecov.

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

Oh thanks! I was planning to do that!
I restarted the buid that errored. (I don't think it should error. Maybe a spurious bug?)


在MacOS下为Pyqt6打包，运行xxx.app直接crash

在macos m1使用nuitka打包pyqt6，运行xxx.app程序crash
使用的命令：nuitka --standalone --macos-create-app-bundle --nofollow-imports --enable-plugin=pyqt6 --output-dir=o main.py
错误代码在from PyQt6.QtWidgets import *
开启--debugger得到以下一些信息
thread #1, queue= 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS(code=1, address=0x8)

frame #0: 0x00000001869bd204 CoreFundation`_CFGetNonObjCTypeID + 92
....

In the template, I have made it clear, that not filling out the issue template is not acceptable. I am closing this kind of report as invalid. The main reason is that I do not want to be left guessing. For you it's easy to erase the issue template and expect me to ask you questions only as necessary, but I cannot do that. I would much rather wait for you to create a new report, fill out the template, or wait for somebody with the necessary skill to do it.
In short: No issue template, no fun. Therefore I am likely just deleting the issue, as it serves as a bad example and detraction for searches.  And even worse, it might keep good reporters from reporting as is this "already known."


Last Week in Pony - December 5, 2021

Version 0.45.1 of ponylang/ponyc has been released.
See the release notes for more details.


surface gnomad filter threshold to somatic and immuno workflows

This is related to
https://github.com/wustl-oncology/analysis-wdls/issues/112

To be clear, we do NOT recommend turning off this filter by setting the value > 1.  We want the ability to do this in certain edge cases and for experimentation but recommend the current status quo for now (i.e. filtering out variants that appear in gnomad at >0.1% global AF).


Uncaught TypeError: Cannot read property 'split' of null

Describe the bug
Im getting Uncaught TypeError error on the JavaScript console while swtiching filter.
To reproduce

Create a resource for example UserResource
Add a filter that matches with some records. for example Admins
Add another filter that does not matches with any record. for example Members
Go to resource page.
Click Filter and select Members filter.
Then select Admins filter.
See the error on JavaScript console.

Expected behavior
Should not be any error there.
Statck Trace
LoadingStates.js:192 Uncaught TypeError: Cannot read property 'split' of null
    at LoadingStates.js:192
    at Array.forEach (<anonymous>)
    at startLoading (LoadingStates.js:190)
    at setLoading (LoadingStates.js:161)
    at LoadingStates.js:50
    at MessageBus.js:17
    at Array.forEach (<anonymous>)
    at MessageBus.value (MessageBus.js:16)
    at Object.call (HookManager.js:38)
    at Object.callHook (Store.js:120)
(anonymous) @ LoadingStates.js:192
startLoading @ LoadingStates.js:190
setLoading @ LoadingStates.js:161
(anonymous) @ LoadingStates.js:50
(anonymous) @ MessageBus.js:17
value @ MessageBus.js:16
call @ HookManager.js:38
callHook @ Store.js:120
sendMessage @ index.js:223
value @ index.js:231
later @ debounce.js:8
setTimeout (async)
(anonymous) @ debounce.js:12
value @ index.js:204
callback @ node_initializer.js:87

My Code
public static function table(Table $table): Table
{
    return $table
        ->columns([
            Text::make("id"),
            Text::make("name"),
            Text::make("email"),
            Text::make("role"),
        ])
        ->filters([
            Filter::make("admins", fn($query) => $query->where("role", "admin")),
            Filter::make("members", fn($query) => $query->where("role", "member")),
        ]);
}

Screenshots
Initial

Members filter selected.

Then Admins filter selected.

Context

Package version: 1.5.4
Livewire version: 2.4.0
Laravel version: 8.32.1
PHP version: 8.0.1
Browser: Chromium
Server OS: Arch Linux

@eislambey The error is actually coming from Livewire's JavaScript - I'll have to try and reproduce the problem first to figure out if it's something our side or Livewire's.

@ryangjchandler Please check these PR.
https://github.com/laravel-filament/filament/pull/212

I can confirm #212 solves the issue. Thanks @shuvroroy !

Merged into develop, please give the branch a thorough test!