support for hystrix event stream output

Signed-off-by: talis<EMAIL_ADDRESS>admin filter: add support for hystrix dashboard output
Description:
This PR adds an admin endoint for hystrix dashboard output.
When there is a request to admin_port/hystrix_event_stream, envoy starts sending SSE stream, using the same socket of the initial request.
The admin URL can be accessed directly from hystrix dashboard.
Risk Level:  Medium
Testing:
Added unit testing hystrix_test.cc
The admin endpoint was not tested, since it returns an infinite event stream, so current mechanisms for testing admin endpoint do not work. If there are any suggestions on how to test it, we will add.
Docs Changes:
changed docs/root/operations/admin.rst.
PR: https://github.com/envoyproxy/data-plane-api/pull/523
Release Notes:
Support was added to hystrix event stream output. From hystrix dashboard, set the Eureka URL to envoy_ip:8001, and add stream from http://envoy_ip:8001/hystrix_event_stream
Note that not all hystrix dashboard statistics are supported. More detail can be found here: <link to the documentation generated from docs/root/operations/admin.rst >
Fixes #1244

Thanks for so many comments! Will probably take until middle of next week to start pushing the fixes.

@trabetti recommend focusing on big picture first (hystrix as stats sink).  I have a growing concern with dependency-creep in Envoy as lots of deployments differ greatly and we'd like it to be easy to configure the parts we really need without generating a sea of ifdefs.

Just updating, we got distracted by some urgent task this week, will start pushing fixes next week..

Per new release note policy please add a release note with any applicable feature docs to https://github.com/envoyproxy/data-plane-api/blob/master/docs/root/intro/version_history.rst. Thank you!

@trabetti Below are examples for each of the two cases you mentioned.

Probably something like:

NiceMock<Server::MockInstance> server;
NiceMock<Upstream::MockCluster> cluster;
mock_cluster.info_->name_ = "test_cluster";
Upstream::ClusterInfoMap cluster_map;
cluster_map["test_cluster"] = cluster;
ON_CALL(server.cluster_manager_, clusters()).WillByDefault(Return(cluster_map));
// Code below here should see the new cluster in the server.

I haven't tested that, but I think that it should mostly work.  Let me know if there's something wrong with that approach.

See https://github.com/google/googlemock/blob/master/googlemock/docs/CheatSheet.md#actions for details, but here's one way to grab the data:

NiceMock<Http::MockStreamDecoderFilterCallbacks> decoder_callbacks;
Buffer::OwnedImpl buffer;
auto encode_callback = [&buffer](Buffer::Instance& data, bool end_stream) {
  buffer.add(data); // This will append to the end of the buffer, so multiple calls will all be dumped
                    // one after another into this buffer.  See Buffer::Instance for other buffer
                    // buffer modification options.
};
ON_CALL(decoder_callbacks, encodeData(_, _)).WillByDefault(Invoke(encode_callback));
// Verify the data in buffer here.

Once again, I haven't tested this, but this general approach should work.
Let me know if you have any other issues or questions!

Just pushed a new version, with hystrix support as a sink. it is not final, there are many TODO comments with questions. Would like to get initial feedback.

It looks like as a sink you still need to get the Http::StreamDecoderFilterCallbacks* into your system, but can we get this by plumbing through the AdminFilter* rather than having this empty-base-class/dynamic-cast strategy? Or @mattklein123 do you have a better idea?

I haven't reviewed this PR at all yet so I don't have any comments, but I definitely want to avoid any dynamic casting. Do you want me to look through the whole things or are there specific things I should look at?

Before the sink implementation, we had multiple variables to pass to the handler, so it made sense to add something generic like the handlerInfo, to pass all of them in one class. We also thought that other handlers may be able to use it, instead of adding more and more arguments.
Now that we moved to the sink implementation, and we only need the callbacks from the filter, one option is to get rid of the handlerInfo and add instead the callbacks as an arguments to the handler interface.
Another direction - We also talked about changing the handlers from methods to classes (in a separate issue and a separate PR). I didn't think this through, but I this may also solve the problem.

I'm not sure what you mean by 'changing handlers from methods to classes'.
If you plumb through AdminFilter& rather than HandlerInfo&, the Filter object carries with it request-specific context, including the request-headers and the callbacks.  Currently the request-headers are not passed to handlers, but the response-headers are, but I think it's reasonable that some admin-handlers may grow a need for them.
So rather than passing all these occasionally-used parameters to all handlers, the AdminFilter& carries all the request-specific state and it simplifies the handler interface to pass that bundle rather than several of its member vars.  That would get you the callbacks (you'd have to add a one-line accessor to AdminFilter).  I could see sinking the response-headers into the filter object as well (if not already there) and removing that handler object.  Maybe even the Response as well.

Pushed a new version. The handler is added in the sync constructor. (plus other fixes).
If this direction looks good, I will continue to passing the AdminFilter to handlers, and the related changes we talked about.

Pushed a commit with AdminFilter passed to handler instead of the callbacks, and followed @mrice32 explanation.
As @jmarantz mentioned, now we can remove the request_headers parameter, and maybe even others. But at first step I did not change this, as this will result in many changes across various handlers, and also requires some work to do on testing (there is no mock for the filter yet).
Please give me feedback on this version, and if it looks as the right direction I will proceed.

Actually, while we are talking about new PRs, I think it would be worthwhile to break out the admin.cc changes as a separate easy-to-review PR.  It touches a bunch of lines but those issues are now pretty much settled, so might as well iterate on the map data structure issues @mrice32 and I have been discussing in a smaller PR.

@jmarantz fine with me. will open a separate PR for the admin changes. There's nothing directly related to the hystrix support there.

RE hystrix.cc being skipped: I think this is really a github UI filter
working as intended.  You can get to hysterix.cc you just have a to click
through a prompt in the 'files' diff that says "diff too large, click here
to show".  It's just a little counterintuitive because if you do a find in
the page, you won't cover any of the contents of hystrix.cc.
On Mon, Apr 23, 2018 at 3:53 PM trabetti<EMAIL_ADDRESS>wrote:

@trabetti commented on this pull request.
In source/extensions/stat_sinks/hystrix/hystrix.h
https://github.com/envoyproxy/envoy/pull/2736#discussion_r183517444:

/**

register a new connection

*/
void registerConnection(Http::StreamDecoderFilterCallbacks* callbacks_to_register);
/**

remove registered connection

*/
void unregisterConnection(Http::StreamDecoderFilterCallbacks* callbacks_to_remove);
HystrixStatCache& getStats() { return *stats_; }

+private:

HystrixStatCachePtr stats_;
std::vectorHttp::StreamDecoderFilterCallbacks* callbacks_list_{};
Server::Instance& server_;
std::map<std::string, uint64_t> current_stat_values_;

@jmarantz https://github.com/jmarantz why does hysrtix.cc being
skipped? I also noticed that some files are not updated here. Is it because
the github PR capacity issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/pull/2736#discussion_r183517444, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB2kPQTu8UdrBlN5Khew_ZnbPTquPSs2ks5trjEwgaJpZM4SeoHY
.

Closing this PR. Opened a new PR #3425.


Modify MEF library loading for tests

Library name(s)
UT.Members
Description
The current implementation loads the exported library types using MEF. However, the implementation is incorrect since the existing MarkDoc.Members.Dnlib library has a dependency on a NuGet package which failed to be resolved by MEF.
The goal is to create a universal solution which will load all dependencies automatically. If possible, create the solution in the MarkDoc.Helpers library so that it is reusable and can be applied for UT.Documentation and the final application.

Total: 2h 57m


Save pdf to server

How to save pdf to server

I used axios and a POST message using  headers:  content-type': 'application/pdf', then in nodejs you can read the post as a request with the file in the body.

@walmac has the right idea. You just need to send the Uint8Array to your server somehow. There are lots of options. This is a more generic JS question though. Stackoverflow can probably help you out here.


implement chunk tracker

There will always be a very small window after HO get the block address and before sending read to the underlying data service, the chunk got selected by GC, moved the blob, returned to heap chunk selector, select by a new shard and a new blob is written on the same block address. This is very unlikely to happen, but conceptually possible, and once it happens, there will be data mismatch. It can be solved by read verification (cross check the blob_id, shard_id from the key) with the data portion blob header. If the blob is rewritten to other shards, it will report mismatch and we should fail this read and let the gateway to retry. Retry will be successful as it will arrive on a new chunk.

we dont need this right?

yes, I believe we can get anther way to solve this issue, no need to blk_num()


Better handling of content types

Closes https://github.com/biopragmatics/bioregistry/issues/775.
This PR adds handling of headers to both the Flask and FastAPI implementations of the apps.

[x] Add Flask implementation
[x] Add FastAPI implementation
[ ] Add Flask tests
[ ] Add FastAPI tests
[ ] Should the output parameter be supported?

CC @vemonet. Ideally, I'd like to use https://github.com/vemonet/rdflib-endpoint and not re-implement this code, but we'll have to work through a few issues first (improving code modularity, documentation, and figuring out Flask suppot) before I can give that a try

Codecov Report

Merging #46 (059f452) into main (89ef83a) will decrease coverage by 0.45%.
The diff coverage is 90.00%.

@@             Coverage Diff             @@
##              main      #46      +/-   ##
===========================================
- Coverage   100.00%   99.55%   -0.45%
===========================================
  Files            7        7
  Lines          443      453      +10
  Branches        94       76      -18
===========================================
+ Hits           443      451       +8
- Misses           0        1       +1
- Partials         0        1       +1

Impacted Files
Coverage Δ

src/curies/mapping_service/__init__.py
97.80% <90.00%> (-2.20%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[OPPRO-261] Support DPP on Velox backend

What changes were proposed in this pull request?
Support reading partitioned table with Velox data reader.
Supported c2r in VeloxBuildSideRelation.
Supported reuse.
How was this patch tested?
Verified on TPC-DS partitioned table.

@zhouyuan do you have any further comment?


docs: optimize home page styles

The reasons for the change are as follows (Will not affect other codes):

Please expand for before and after comparison

1、Non-dark mode display abnormality
before

after

html.dark:has(.landing) {
  --vp-c-bg: #101010;
}

2、Switching to the home page, the transition animation of the header is stiff
before

after

transition: none;

.VPNavBar *:not(.wrapper *) {
  transition: none;
}

3、Appearance Small screen display is meaningless
before

after

.VPMenu .translations + .group {
  display: none;
}

Amazing PR description!
For no1, I think I've already fixed it at https://github.com/vitejs/vite/pull/18281 but i's not reflected on the site yet. It is on https://main.vite.dev though. So maybe we don't need that change here for now.
The rest looks great.

Amazing PR description!
For no1, I think I've already fixed it at #18281 but it's not reflected on the site yet. It is on https://main.vite.dev though. So maybe we don't need that change here for now.
The rest looks great.

No1
I actually changed the bottom of the search box because it does look a bit weird now.
Ⅰ. before (main.vite.dev)

Ⅱ. after (current)

Ⅲ. or change the text (If this is the presentation method, I will submit the code)

I will delete the code for No1 if it is not needed.

Oh I didn't realize that you're changing the footer part. Nevermind then, let's keep the PR as is 👍


exp - moved AnnoyVectorStore.py to experimental pkg

The test aren't passing yes. guess the vectorbase  hasn't be  concluded yet.


CI: use 2.4.6

This PR updates the CI matrix.

If I'm not wrong, setting just 2.4 will make travis fetch last point release version. We could do that for all ruby versions in all dry repos, so we don't have to manually change it at every release. What do you think?

@waiting-for-dev yes if you can confirm that this is how it works. I tried that some time ago and it did not work like that

I recently did it in a project (.travis.yml, build) and it worked, but I haven't seen it documented.

We need to confirm that with travis folks.

The file in rvm which lists what aliases are active: https://github.com/rvm/rvm/blob/master/config/known
If rvm is updated, and using that file, things will work right.

Good research! :)
Isn't rvm using that file always ? If so, then we would only rely on travis keeping rvm updated, which I don't know if they do very often. Anyway, the worst case scenario would be just testing against older versions in the same minor version branch, which I think it's not too terrible and it would unload a quite boring maintenance burden.


refactor: doc index structure

Two suggestions:
shorter imports
Since developers will most likely only interact with specific backend implementations, i.e. will only import those classes, let's make the import shorter.
Before:
from docarray.doc_index.backends.hnswlib_doc_index import HnswDocumentIndex

Now:
from docarray.doc_index import HnswDocumentIndex

less verbose file names
Being inside doc_index module, it's already clear that abstract_doc_index.py (same with hnswlib_doc_index.py) is about doc_index, so let's make it less verbose.
Before:
doc_index/abstract_doc_index.py
doc_index/backend/hnswlib_doc_index.py

Now:
doc_index/abstract.py
doc_index/backend/hnswlib.py

from docarray.doc_index import HnswDocumentIndex

I think we should also rename the doc_index part, i find it a bit verbose and i don't like having an underscore. Just index might be not so clear though, any other suggestions?

from docarray.doc_index import HnswDocumentIndex

I think we should also rename the doc_index part, i find it a bit verbose and i don't like having an underscore. Just index might be not so clear though, any other suggestions?

fully agree
from docarray.vectordb import HnswDocumentIndex
``` ?

```python
from docarray.index import HnswDocumentIndex
``` ?

```python
from docarray.search import HnswDocumentIndex
``` ?

```python
from docarray.db import HnswDocumentIndex
``` ?

@samsja @JohannesMessner
Let's go with
from docarray.index import HnswDocumentIndex

for now and if it doesn't suit docarray we can refine it later. wdyt?


Parse error

[{"ConsignmentInfoItems":[],"HasRestrictions":false},{"ConsignmentInfoItems":[],"HasRestrictions":false,"HasSerializeError":false}]
JObject.Parse()  results
"Newtonsoft.Json.JsonReaderException: Error reading JObject from JsonReader. Current JsonReader item is not an object: StartArray. Path '', line 1, position 1."

Read the darn error message. You are trying to read an json object, but look at your json data. What do you have in your json data: a json array (which is not an json object). It doesn't matter what the array contains, becauser a json array is a json array, and a json array is not a json object.


Minor fixes: r-get-started.md

Fixed minor typos, one resource link updated and added a new R internet resource.

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

Hi @grayknight2, thanks so much for your eagle-eyed edits. The changes look good.
#sign-off

@PeterCLu: I'm sorry - only the author of this article, @likebupt, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Spigot 1.9 and PEX 1.23.4

PEX does not function properly in this instance.  MANY people are coming to the forums with this problem and I have no solution for it.  The permissions.yml files are correct.  The config.yml files are correct.  But PEX still does not function properly on these servers.
One example case.

What is the problem exactly? Can I update my server to 1.9.2 or not?

Bad timings on 1.9.2 with PEX 1.23.4 @ Spigot 1.9.2: https://timings.spigotmc.org/?url=15766846

Preliminary reports indicate that EVERY group MUST now have an inheritance, even if the set is empty (inheritance: []).
Try this on your 1.9 servers and post the results.

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.


doc: support cassandra for docker image of server and doc for docker …

…image of loader
Main change

supplement how to use cassandra in the docker image of server
supplement how to use docker image of loader

Increment
The increment is about how to use loader with docker:

DIff
The diff is mainly about oracle and folding some files:

orcale
before:

after:

fold
before:

after:

fold2
before:

after:

keep the pr draft until https://github.com/apache/incubator-hugegraph-toolchain/pull/530 merged

OK, fine to sync the EN version 🔢


i18n(es): update react

Description (required)
updates react based on this commit b7d16563d8416907561cf30c565e9183a2fd7d92

Related issues & labels (optional)

Closes # N/A
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

es
guides/integrations-guide/react.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Fix required TFM for Source Generator runtime

Summary
For Source Generator to work in Visual Studio TFM has to be targeted to .netstandard 2.0 but for dotnet CLI it can be targeted to any TFM.
Changes:
Corrected misleading TIP regarding Source Generator not working with higher TFM than .netstandard 2.0

@sharwell So my basis for these changes were my own experiments with running Source Generator with netstandard 2.1, .net 5 and .net 6.
But my project would still not work in Visual Studio which I eventually got to fix with help from this comment: https://github.com/dotnet/roslyn/discussions/56532#discussioncomment-1356504
Which actually explains why Source Generators targetting higher .netstandard/.net TFM doesn't work in Visual Studio but work with other tooling like dotnet CLI.
And I think basis for aforementioned comment is actually your own comment here: https://github.com/dotnet/roslyn/discussions/47701#discussioncomment-79566
But I do see some caution that can be pointed out as mentioned here: https://github.com/dotnet/roslyn/discussions/47701#discussioncomment-1356495

I understand that this change is technically correct but it is still against our guidance. Customers generally don't differentiate between these scenarios. The expectation is that if their code builds with dotnet build then it will build with msbuild (and vice versa). Having a generator that targets anything other than netstandard2.0 breaks this and creates a lot of customer confusion.
Developers can safely target .NET Core in their generators but it's a much more complex setup that involves effectively multi-targeting the NuPkg and toggling the setup based on whether MSBuild is running on .NET Framework or .NET Core. It's certaintly doable but more of an expert level scenario.
The message from the compiler team remains that source generators and analyzers need to target netstandard2.0. The compiler has even started enforcing this by issuing warnings in cases where we detect generators / analyzers not doing this because of the customer confusion that it creates.

Closing based on https://github.com/dotnet/docs/pull/29303#issuecomment-1119785397

I understand having documentation reflect official position on the support, but I think it should also point out kind of gotcha or unintended consequences, like using dotnet CLI with a Source Generator that has TFM higher than netstandard 2.0 would work.
TIPs are percise place for this kinda information, wouldn't you say? Finding the same info that I needed to understand in Github Issues and Dicussion is just not nice, which I wanted others to avoid with the help of this PR.
I imagine alot of ppl like me, thought that dotnet CLI and msbuild in VS would work exactly the same. Cuasing more confusion in face of lack of comprehensive documents on a new feature, which made me question myself on using a new feature and just giving up.
A reference for these kinda frustrations is this article: https://turnerj.com/blog/the-pain-points-of-csharp-source-generators


x/tools/gopls: versions >= 0.7.0 consume entire cpu, whereas v0.6.11 works perfectly

What version of Go are you using (go version)?

$ go version
go1.16.7 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/nonroot/home/.cache/go-build"
GOENV="/nonroot/home/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/nonroot/home/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/nonroot/home/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.7"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/nonroot/home/workspaces/app/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3294291348=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Using coc.nvim and gopls v0.7.1, after about 1min 30secs of jumping around function definitions (specifically :call CocAction('jumpDefinition'), gopls consumes the entire cpu of the machine and editing slows to a crawl/the machine is no longer responsive.
Downgrading to gopls v0.6.11 alleviates all issues.
Here is a picture of htop with gopls v0.7.1 that shows the high cpu consumption:

Here is a picture of htop with gopls v0.6.11 that shows normal cpu consumption:

Note: this seems to only occur on low powered machines. I am using a digital ocean droplet with 1 CPU. On high powered machines (8-core, ubuntu), this is not a problem. However, it appears to be a regression from v0.6.11 and makes gopls unusable for a basic VM.
Here are the machine details where the problem occurs:

$ lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   40 bits physical, 48 bits virtual
CPU(s):                          1
On-line CPU(s) list:             0
Thread(s) per core:              1
Core(s) per socket:              1
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           85
Model name:                      DO-Premium-Intel
Stepping:                        4
CPU MHz:                         2494.138
BogoMIPS:                        4988.27
Virtualization:                  VT-x
Hypervisor vendor:               KVM
Virtualization type:             full
L1d cache:                       32 KiB
L1i cache:                       32 KiB
L2 cache:                        4 MiB
NUMA node0 CPU(s):               0
Vulnerability Itlb multihit:     KVM: Mitigation: Split huge pages
Vulnerability L1tf:              Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled
Vulnerability Mds:               Mitigation; Clear CPU buffers; SMT Host state unknown
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1
                                 gb rdtscp lm constant_tsc arch_perfmon rep_good nopl cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_
                                 1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_
                                 fault invpcid_single pti ssbd ibrs ibpb tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 sm
                                 ep bmi2 erms invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec
                                 xgetbv1 pku ospke md_clear

Here is my coc-settings.json, taken from the gopls documentation:

{
  "languageserver": {
    "golang": {
      "command": "gopls",
      "rootPatterns": ["go.mod", ".vim/", ".git/", ".hg/"],
      "filetypes": ["go"]
    }
  }
}

To reproduce this issue, you can use a docker container that I have built to show the problem.
step-by-step:
(1) Spin up a low powered VM
(2) Run docker run --rm -it -v ${PWD}:/home/nonroot/workspaces/app mperel/dev-container. This container has coc.nvim and gopls v0.6.11. It maps your current directory into the container, so you can edit files in the container.
(3) Create a basic main.go and use :call CocAction(‘jumpDefinition’) to jump around the standard library (specifically, I jumped into fmt.Println and jumped around to different files from there). Notice that everything is fine.
(4) Run go install golang.org/x/tools/gopls@latest to update gopls to v0.7.1
(5) Jump around using :call CocAction(‘jumpDefinition’) and notice after a little while that the machine becomes unresponsive. Consider running htop in another window to see the cpu consumption as the photos show.
What did you expect to see?
I expected gopls >= v0.7.0 to work on a low powered linux VM, just as gopls v0.6.11 does.
What did you see instead?
I saw excessive cpu consumption that drew the machine to a halt when using gopls >= v0.7.0.

Hi, thanks very much for the report. We weren't aware of this regression, and with your reproducer hopefully we can bisect.
You mention v0.7.1 specifically, but cite this problem for gopls >=v0.7.0. Just to clarify: did you test this explicitly on v0.7.0 and confirm that it reproduces with that version?

Ah, I think I know what this is.
I believe this is a consequence of https://golang.org/cl/330529, which fixed loading std and cmd, plus the way that coc.nvim sets workspace roots.
IIRC When you jump to definition in std in coc.nvim, it detects that you are jumping out of your workspace, and attempts to add a new workspace due to detecting the workspace root from the go.mod file in std. In other words, it sets the standard library as a new workspace. For workspaces, gopls loads everything (all packages, including function bodies) so that it can compute things like references. When the standard library is a workspace root, this pulls quite a lot of code into memory.
By comparison, other LSP clients (such as vscode-go) don't add a new workspace root, so gopls only fully parses and type checks packages that you have open in the standard library, not the entire standard library.
The CL above fixed a bug causing gopls to essentially not load the standard library. Before that CL, coc.nvim would have behaved very similarly to vscode-go or other LSP clients. After that CL, coc.nvim will incur a penalty for loading the entire standard library.
I wouldn't categorize this as a regression in gopls per se, but it is certainly a problem that one can't use gopls to work on the standard library on an underpowered machine.  While we have some distant plans to improve this by limiting the scope of the workspace gopls has to consider, can you try managing your workspaces explicitly in coc.nvim (using :CocList folders, I think?).

@findleyr Thanks for the quick and helpful response!
Having tested further, v0.7.0 works fine, so my title is a mistake, it should say > rather than >=. The problem is with v0.7.1 and above (I tried v0.7.1 and v0.7.2). Does that information check out with your hypothesis around https://golang.org/cl/330529?
As for running :CocList folders:
Before jumping to fmt.Println’s defintion in the standard library, I get:
/home/nonroot/workspace/app

After jumping to fmt.Println‘s definition (tested on v0.6.11 and v0.7.2), I get:
/home/nonroot/workspaces/app
/usr/local/go/src

which shows that you are correct, jumping into the standard library adds a new workspace.
As for the severity of the issue, I wouldn’t think of it so much in terms of people developing the standard library. Rather, I would think of it in terms of people who every now and then need to go to a definition to read an implementation/documentation. For this group of people (which I would imagine characterizes everyone at some point), they can no longer use coc.nvim with gopls effectively on a low powered machine. Testing out different VMs on digital ocean, v0.6.11 performs excellently on a $10 per month VM, whereas > v0.7.0 is still kind of slow on a $25 per month VM.
Do you think this is an issue that should be addressed with gopls or do you think it is worth raising an issue in coc.nvim?
Thanks again for all of your help :)

@michaelperel https://golang.org/cl/330529 is in v0.7.1 but not v0.7.0, so the fact that v0.7.0 is fine supports the hypothesis that this is the root cause.
Have you tried the settings listed in the coc.nvim documentation to prevent GOROOT/src from being set as a workspace folder? Unfortunately, it looks like coc.nvim really wants to place each open buffer inside a workspace.
I don't think we can (or rather should) do anything about this on the gopls side: coc.nvim is telling us that it wants GOROOT/src to be a workspace folder, and it wouldn't be correct for us to ignore this request. If you can't get this to work with the coc.nvim documentation, raising an issue with coc.nvim makes sense to me.

I'm going to close this, not because there isn't a poor experience here -- it's definitely a problem std consumes so many resources -- but because the root cause of this memory jump is not a regression.  We have other open issues for performance.


Join strings

There would be two main use cases of a join jar:

Join two strings
Join linked lists of strings

>>> "Gustav" :name var
>>> "Hello" name " " join println
"Hello Gustav"

>>> ("Hello" ("Gustav" ())) " " join println
"Hello Gustav"
>>> {"Hello" "Gustav"}] " " join println
"Hello Gustav"

In general, this would be the syntax for the two cases:
"first" "second" "joiner" join
{"first" "second" ... "final"}] "joiner" join

I'd use concat or ++ to add strings. Those operations are pretty different.

I would take inspiration from raku and use ~

@decorator-factory So you're saying that the following should exist:
"first" "second" "joiner" concat
{"first" "second" ... "final"}] "joiner" join

Why even separate it?

"Hello, " "world" concat -- "Hello, world"

That would remove the joiner, yeah.

I am not too fond of having a function do 2 different things, since someone screwing up and having the function do the wrong thing rather than just error would be annoying. And since you don't actually see what args are passed, it could be hard to tell which one is used.

Yeah, I think we should make distinct functions for distinct operations.

This would be the function for concat:
"first" "second" concat  # "firstsecond"

And for join, do we want the joiner or not?
{"first" "second" "third"}] "." join  # "first.second.third"

Yeah, concat would be + in Python, and join would be... well, join
I think we can follow @lavirlifiliol 's advice and just do python -c "print(dis(str))" | stdlib/strings.py

We have join and concat now.


Hide globe depth and pick depth options from Cesium Inspector

The Show globe depth and Show pick depth options were both broken in 1.45, likely related to the log depth changes.  This removes those options in the Cesium Inspector UI until we have a chance to fix them.
#6763

Thanks for the pull request @hpinkos!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

@mramato updated.  I think commenting it out make sense since this is meant to be temporary and it will make it easy to add back when we fix it.  All of the functionality in the view model is still there.  If I delete the code for the view here I think we'd probably want to delete all that from the view model as well so it doesn't look like we have properties that aren't used anywhere.


[AutoPR peering/resource-manager] Adding Specifications for Peering

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5343

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/4644


unable to save world difficulty

any time a single worlds difficulty is changed it gets changed back to what it was before after a server restart.
so for example. world "A" and world "B" both have a difficult of easy. If you change world "B" to have a difficulty of normal. It only stays that way until the server is restarted.

Reference #1163 - I think this may be the same issue.

@drakmirv , thank you for the suggestion. Unfortunately, that is beyond the scope of a basic server administration task, since in can't be accomplished by a server admin.

apparently it's not the same as #1163 since that issue be closed as resolved and this issue still persists.

Related: https://github.com/SpongePowered/SpongeForge/issues/568

This has been a long time coming but:
https://github.com/SpongePowered/SpongeCommon/tree/feature/multi-world-difficulty
Still a WIP but mostly there. Apologies for the very long wait!

@Zidane please push your branch when tested.

Already in latest builds.


add fixture 'elation/platinum-seven'

add fixture 'elation/platinum-seven'
update register.json

Thank you @Fxedel!

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
You can run a plugin's export tests by executing:
$ node cli/run-export-test.js -p <plugin name> <fixtures>
Fixture elation/platinum-seven changed in this PR

d-light

attributes-correctness

:white_check_mark: elation/platinum-seven-Basic.xml
:white_check_mark: elation/platinum-seven-Standard.xml
:white_check_mark: elation/platinum-seven-Extended.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Elation-Platinum-Seven.qxf

Broken links
(Output of test script tests/http-status.js.)
There were 0 internal and 1 external links failing.

http://www.ecue.de/


two new methods of a page

Add Page#insights_with_date_range method and Page#posts_with_time_range method

posts_with_time_range: basically same with posts method but without memoization, so you can get different result by calling more than two times
insights_with_date_range: it is similar with weekly_insights but it's adding all the daily insights of arbitrary date range. So if you insights_with_date_range(since: Jan 1, until: Jan 31) to get January data for example.

Coverage increased (+0.3%) to 97.696% when pulling f20f830cbcd52cc51b4dd6d791dada6adddb2664 on with-range into b254e214d7670f7f16e6aab4cf24b5ea42460a27 on master.


how can i filter only on the display name and not on any property of and object

any node in my tree have more values then i would like to present to the user.
for example
[
{name:"tim",parent name :"ron"}
{name:"alex",parent name :"tim"}
]
and I am presenting to user only the name.
the result of filtering by "tim"
will be "tim and alex"
there's a way to refine the filter to specific property

just figure it out.
referring to the filter example in: https://wix.github.io/angular-tree-control/
need to delete " $scope.predicate = "Node 1";"
and add the desired property to:
->


So why remove grunt, why not do both?

P.S. Your instruction site is not working. I'd love to use this, but NPM is failing for it.

I don't really have a reason for it, but you're right I could've done both...
Will consider that for the future. Thanks ^^


Daily/Futures not changing when inside a category

The same markets are showing under Daily and Futures. Toggling between is not working

this looks to be fixed


Enhances 'entra app permission add/list' commands. Closes #5786

Enhances entra app permission add an entra app permission list commands by adding an appName option. Closes #5786

Thank you @SmitaNachan, we'll try to review it ASAP!

Hi @SmitaNachan, could you resolve the merge conflicts on this PR for us?

Merged manually, thank you! 🎉


Change timeout time to 60 secs

Before

Request timeout time is 30 * 1000 ms

After

Request timeout time is 60 * 1000 ms

Merged! Thanks for the quick review 👍


ValueError: list.remove(x): x not in list in audio.py

Looks like endpointer_cb was fired more than it should have in main.py
Jun 03 08:55:20 raspberrypi python3[548]: return self._handle_response_stream(response_stream)
Jun 03 08:55:20 raspberrypi python3[548]: File "/home/pi/voice-recognizer-raspi/src/speech.py", line 206, in _handle_response_stream
Jun 03 08:55:20 raspberrypi python3[548]: self._end_audio_request()
Jun 03 08:55:20 raspberrypi python3[548]: File "/home/pi/voice-recognizer-raspi/src/speech.py", line 201, in _end_audio_request
Jun 03 08:55:20 raspberrypi python3[548]: self._endpointer_cb()
Jun 03 08:55:20 raspberrypi python3[548]: File "src/main.py", line 366, in endpointer_cb
Jun 03 08:55:20 raspberrypi python3[548]: self.recorder.del_processor(self.recognizer)
Jun 03 08:55:20 raspberrypi python3[548]: File "/home/pi/voice-recognizer-raspi/src/audio.py", line 77, in del_processor
Jun 03 08:55:20 raspberrypi python3[548]: self._processors.remove(processor)
Jun 03 08:55:20 raspberrypi python3[548]: ValueError: list.remove(x): x not in list

Thanks for the report! I've seen this before, and added a check to avoid it, but I guess that doesn't always work.
What were you doing when this happened? Are you able to reproduce it reliably?

I am having the exact same issue. Tried a rebuild from scratch. No matter what I say it fails. Can anyone help?

When I push the button and talk the log sits at recognizing for like a minute and then bombs. here is my log:
Jun 24 05:50:36 raspberrypi systemd[1]: Starting voice recognizer...
Jun 24 05:50:36 raspberrypi systemd[1]: Started voice recognizer.
Jun 24 06:11:05 raspberrypi python3[534]: [2017-06-24 06:11:05,221] INFO:audio:started recording
Jun 24 06:11:05 raspberrypi python3[534]: [2017-06-24 06:11:05,257] INFO:main:ready...
Jun 24 06:43:22 raspberrypi python3[534]: [2017-06-24 06:43:22,697] INFO:main:listening...
Jun 24 06:43:22 raspberrypi python3[534]: [2017-06-24 06:43:22,700] INFO:main:recognizing...
Jun 24 06:45:54 raspberrypi python3[534]: [2017-06-24 06:45:54,373] INFO:speech:event_type: 1
Jun 24 06:45:54 raspberrypi python3[534]: [2017-06-24 06:45:54,385] INFO:main:thinking...

Jun 24 05:50:36 raspberrypi systemd[1]: Started voice recognizer.
Jun 24 06:11:05 raspberrypi python3[534]: [2017-06-24 06:11:05,221]
INFO:audio:started recording
Jun 24 06:11:05 raspberrypi python3[534]: [2017-06-24 06:11:05,257]
INFO:main:ready...
Jun 24 06:43:22 raspberrypi python3[534]: [2017-06-24 06:43:22,697]
INFO:main:listening...
Jun 24 06:43:22 raspberrypi python3[534]: [2017-06-24 06:43:22,700]
INFO:main:recognizing...
Jun 24 06:45:54 raspberrypi python3[534]: [2017-06-24 06:45:54,373]
INFO:speech:event_type: 1
Jun 24 06:45:54 raspberrypi python3[534]: [2017-06-24 06:45:54,385]
INFO:main:thinking...

Reply to this email directly, view it on GitHub
https://github.com/google/aiyprojects-raspbian/issues/75#issuecomment-310834228,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVBgLSYtwhngD8cD75hy32J28uhUm8Zks5sHPjAgaJpZM4Nu5D_
.

@ywonglanecove and @daver99999, thanks for the report and for the complete log.
I've looked into this but can't reproduce. The correct order of events is:

Clap.
SyncMicRecognizer.recognize() get called.
recognize() calls recorder.add_processor().
recognize() sets recognizer_event
The background thread, _recognize() handles recognizer_event and takes over.
_recognize() calls recognizer.do_request(), which calls recognizer._handle_response_stream().
The server detects that the user has stopped speaking, and returns the END_OF_UTTERANCE event.
_handle_response_stream() gets this response and calls _stop_sending_audio(resp).
_stop_sending_audio() prints event_type: 1 then returns True.
_handle_response_stream() calls _end_audio_request(), which calls endpointer_cb().
endpointer_cb() calls del_processor(recognizer).
endpointer_cb() calls status('thinking') which prints thinking....
The server sends further responses with the transcript and audio data.

The problem appears to be that del_processor() is called more than once, because thinking... appears in davey's log, and it is printed after the first call to del_processor(). It is possible that the server returns an error after sending END_OF_UTTERANCE, which would lead to _end_audio_request being called twice. However, I can't think what would cause this this.
If that's the problem the right fix is to add state to GenericSpeechRequest so it only calls endpointer_cb() once per request.
@ywonglanecove, I wouldn't mind also adding a check to turn the crash into a warning. Would you like to make a PR with your check? If not I can do it.

I will create a pr in the weekend
On 27 Jun 2017 9:30 PM, "Rodrigo Queiro"<EMAIL_ADDRESS>wrote:

@ywonglanecove https://github.com/ywonglanecove and @daver99999
https://github.com/daver99999, thanks for the report and for the
complete log.
I've looked into this but can't reproduce. The correct order of events is:

Clap.
SyncMicRecognizer.recognize() get called.
recognize() calls recorder.add_processor().
recognize() sets recognizer_event
The background thread, _recognize() handles recognizer_event and
takes over.
_recognize() calls recognizer.do_request(), which calls
recognizer._handle_response_stream().
The server detects that the user has stopped speaking, and returns
the END_OF_UTTERANCE event.
_handle_response_stream() gets this response and calls
_stop_sending_audio(resp).
_stop_sending_audio() prints event_type: 1 then returns True.
_handle_response_stream() calls _end_audio_request(), which calls
endpointer_cb().
endpointer_cb() calls del_processor(recognizer).
endpointer_cb() calls status('thinking') which prints thinking....
The server sends further responses with the transcript and audio
data.

The problem appears to be that del_processor() is called more than once,
because thinking... appears in davey's log, and it is printed after the
first call to del_processor(). It is possible that the server returns an
error after sending END_OF_UTTERANCE, which would lead to
_end_audio_request being called twice. However, I can't think what would
cause this this.
If that's the problem the right fix is to add state to
GenericSpeechRequest so it only calls endpointer_cb() once per request.
@ywonglanecove https://github.com/ywonglanecove, I wouldn't mind also
adding a check to turn the crash into a warning. Would you like to make a
PR with your check? If not I can do it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/aiyprojects-raspbian/issues/75#issuecomment-311331109,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVBgD9wBugA9LFoeiRJ0e8cC-EkVHRQks5sIOfigaJpZM4Nu5D_
.

Closed as PR merged


Directly construct CircuitData in TwoQubitWeylDecomposition

Summary
In the recently merged #12740 a path was added for constructing the CircuitData in rust when synthesizing to a QuantumCircuit directly. However, in that PR this was done through a layer of indirection by first collecting the gates into an intermediate Vec and then passing an iterator of that into
CircuitData::from_standard_gates(). However this resulted in an unecessary allocation for two Vecs and it would have been better to just directly construct the CircuitData object directly. However, to accomplish this we needed more rust space methods for creating and manipulating a CircuitData object as it's mostly being constructed from Python space or using CircuitData::from_standard_gates() with an iterator so far. This commit makes those additions and then updates the TwoQubitWeylDecomposition code to directly construct the CircuitData object instead of using an intermediate Vec.
Details and comments

I've run a quick little benchmark script:
import statistics
import time

from qiskit.synthesis.two_qubit import TwoQubitWeylDecomposition
from qiskit.circuit.library import CXGate
from qiskit.quantum_info import random_unitary

unitaries = [random_unitary(4) for _ in range(10000)]
runtimes = []
for mat in unitaries:
    start = time.perf_counter()
    TwoQubitWeylDecomposition(mat).circuit()
    stop = time.perf_counter()
    runtimes.append(stop - start)
print(f"Mean runtime per unitary: {statistics.geometric_mean(runtimes)} sec.")
print(f"Total runtime for 10k unitary matrices: {sum(runtimes)} sec.")

to compare the performance with and without this PR. There is a consistent small speedup I'm seeing with this PR applied. With this PR:
Mean runtime per unitary: 2.8342069525664723e-05 sec.
Total runtime for 10k unitary matrices: 0.3291525247041136 sec.

on current main:
Mean runtime per unitary: 3.0709930013551664e-05 sec.
Total runtime for 10k unitary matrices: 0.3557815661188215 sec.

There is some fluctuation in the numbers obviously especially with fully random unitaries, but I haven't seen a case where the PR is slower (or the same speed) than main. Not that TwoQubitWeylDecomposition.circuit() is performance critical at all, but I wanted to put some numbers behind why we would want to do this.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

64 of 74 (86.49%)  changed or added relevant lines in 2 files are covered.
7 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.005%) to 89.926%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/accelerate/src/two_qubit_decompose.rs
17
27
62.96%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
94.02%

crates/qasm2/src/lex.rs
6
91.6%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.005%

Covered Lines:
65872

Relevant Lines:
73251

💛  - Coveralls


fix: rlp encode and decode of Proposal struct

What this PR does / why we need it?
This PR fix the rlp encode and decode of Proposal struct. The previous version omit the extra_data field.
What is the impact of this PR?
No Breaking Change
PR relation:

Ref #

CI Settings

CI Usage
Tip: Check the CI you want to run below, and then comment /run-ci.
CI Switch

[x] Web3 Compatible Tests
[x] OCT 1-5 And 12-15
[ ] OCT 6-10
[ ] OCT 11
[ ] OCT 16-19
[x] v3 Core Tests

CI Description

CI Name
Description

Web3 Compatible Test
Test the Web3 compatibility of Axon

v3 Core Test
Run the compatibility tests provided by Uniswap V3

OCT 1-5 | 6-10 | 11 | 12-15 | 16-19
Run the compatibility tests provided by OpenZeppelin

/run-ci

/run-ci

The local verification of this feature passed.


WK Browser

WK Browser - https://github.com/WhichBrowser/Parser-PHP/issues/202

Coverage remained the same at 100.0% when pulling bcf322c5535ac84b2f72767bfb49177ded71433f on ayumi-cloud:WKBrowser into 4899110cd2f87b01e04ced62dbb9dec541031dee on WhichBrowser:master.


Scalability questions

Hello,
We are considering to deploy Topaz as a micorservice inside our organisation to handle user's authorisations for a new project.
I have some questions/doubts regarding the scalability of such approach:

As you're using bbolt DB, which is an embedded Key-Value DB, does it means that it's is only possible to have 1 single instance of Topaz? (so, only vertical scaling is possible)
With a single instance, how to avoid it be a single point of failure?
If we deploy several instances of Topaz, is it possible to setup a sync data between them?
Do you have an mechanism for automatic backup/restore of DB?

Thanks in advance,
Anton

Hi Anton,
As you mentioned, Topaz includes an embedded DB that stores objects and relationships. Topaz consumes a gRPC contract for talking to a data store, and the embedded DB is one implementation of that contract. We have a postgres implementation as well (part of the Aserto commercial offering).
There are two strategies for keeping data in sync between Topaz instances:

Eventual consistency: data changes are made into each Topaz instance. You can either do this yourself (in code), or you can use the Aserto central directory and connect the Topaz instances to the Aserto control plane, which will distribute data changes to any Topaz instance that is connected to the control plane.
Stateless Topaz: Use a postgres-backed relational directory implementation, and configure the Topaz instances to talk to this directory.

Question 2: with either of these models, you can scale Topaz instances horizontally (no SPOF).
Question 3: the Aserto control plane was built to solve this problem.
Question 4: if you're running the Aserto Directory in your cloud, you can use your cloud provider's auto backup/restore (e.g. AWS RDS) for the Postgres instance.

Hi Omri,
Thanks for your detailed answers!
Considering your commercial offer, I have few more questions:

Is it possible to start with Topaz on our side but later switch to the Aserto commercial offering? What are the potential blockers that we may face?
Do you have any official migration guide from Topaz to Aserto?
Do you provide any support in doing this migration?

Many thanks

Thanks Anton!

Yes, you can start with "single-instance" Topaz, and when you're ready, you can connect that Topaz instance to the Aserto control plane. It's as easy as changing the Topaz config.yaml file.
The process is meant to be very simple. You create an Aserto tenant, install the aserto CLI, run aserto developer configure, which will create a topaz config file with the correct sections to connect the topaz instance to the Aserto control plane.
If you're a commercial customer, yes, we will definitely help you set this up!

@amOgury does this answer your questions?

@amOgury since we haven't heard back, I'm closing this issue - please feel free to re-open it if you need more information. Thanks!


ARROW-6626: [Python] Support converting nested sets when converting to arrow

@pitrou I should have addressed all feedback on the PR, let me know if it's ready to go or there is more to tweak


ValueError: numpy.dtype has the wrong size, try recompiling

root@bogon:~/Desktop# spyder
Traceback (most recent call last):
File "/usr/local/bin/spyder", line 4, in
import('pkg_resources').run_script('spyder==2.3.3', 'spyder')
File "/usr/local/lib/python2.7/dist-packages/setuptools-14.0-py2.7.egg/pkg_resources/init.py", line 698, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/local/lib/python2.7/dist-packages/setuptools-14.0-py2.7.egg/pkg_resources/init.py", line 1616, in run_script
exec(code, namespace, namespace)
File "/usr/local/lib/python2.7/dist-packages/spyder-2.3.3-py2.7.egg/EGG-INFO/scripts/spyder", line 2, in
from spyderlib import start_app
File "/usr/local/lib/python2.7/dist-packages/spyder-2.3.3-py2.7.egg/spyderlib/start_app.py", line 14, in
from spyderlib.config import CONF
File "/usr/local/lib/python2.7/dist-packages/spyder-2.3.3-py2.7.egg/spyderlib/config.py", line 22, in
from spyderlib.utils import iofuncs, codeanalysis
File "/usr/local/lib/python2.7/dist-packages/spyder-2.3.3-py2.7.egg/spyderlib/utils/iofuncs.py", line 158, in
import scipy.io as spio
File "/usr/local/lib/python2.7/dist-packages/scipy-0.15.1-py2.7-linux-x86_64.egg/scipy/io/init.py", line 85, in
from .matlab import loadmat, savemat, whosmat, byteordercodes
File "/usr/local/lib/python2.7/dist-packages/scipy-0.15.1-py2.7-linux-x86_64.egg/scipy/io/matlab/init.py", line 13, in
from .mio import loadmat, savemat, whosmat
File "/usr/local/lib/python2.7/dist-packages/scipy-0.15.1-py2.7-linux-x86_64.egg/scipy/io/matlab/mio.py", line 12, in
from .miobase import get_matfile_version, docfiller
File "/usr/local/lib/python2.7/dist-packages/scipy-0.15.1-py2.7-linux-x86_64.egg/scipy/io/matlab/miobase.py", line 22, in
from scipy.misc import doccer
File "/usr/local/lib/python2.7/dist-packages/scipy-0.15.1-py2.7-linux-x86_64.egg/scipy/misc/init.py", line 47, in
from scipy.special import comb, factorial, factorial2, factorialk
File "/usr/local/lib/python2.7/dist-packages/scipy-0.15.1-py2.7-linux-x86_64.egg/scipy/special/init.py", line 586, in
from ._ufuncs import *
File "init.pxd", line 155, in init scipy.special._ufuncs (scipy/special/_ufuncs.c:27042)
ValueError: numpy.dtype has the wrong size, try recompiling

This is not a Spyder error, as can be seen from the entire traceback. It seems you have compiled numpy and scipy by hand, so you have to figure it our what you've done wrong.
I'm sorry but we don't have time to help you with that. I'd recommend you to use Anaconda which won't give you these problems.


Don't use remote source files

Some build time optimizations

@rgardler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Update Firebase.cpp

fix for API KEY authentication
typo fix

I signed it!

when compile the code, usually happen the warning: returning reference to temporary [wreturn local addr] and cannot return any, if firebase error occur.
We should change the function in Firebase.cpp like this, then OK.
Please test it by your self, and update the file if helpful.
const String& FirebaseArduino::error() {
static const String& s = error_.message().c_str();
return s;
}

@michaelchien1972 I'm curious where you found the ?api_key option documented.
I think we should switch to:
https://firebase.google.com/docs/reference/rest/database/user-auth

@michaelchien1972 Any documentation for the ?api_key  ?


LSTM many to many resetting policy problem

I want to use RNN(LSTM) to predict multiple future values by using multiple historical (previous) values . I have a time series which is shown in the following plot:

Indeed I wan to predict 'nxt_time' in future in 'nxt_step_number' step numbers with equal distance by using 'prev_time' previous values in 'prev_step_number' step numbers.
My implementation is as follows:
 nxt_time = 1000
 nxt_step_number = 5
 prev_time = 10000
 prev_step_number = 500
 batch_size = 500
 epochs = 30
 hidden_neurons = 50

 (X_train, y_train), (X_test, y_test) = train_test_split(data)
 model = Sequential()
 model.add(LSTM(hidden_neurons,
           batch_input_shape=(batch_size, prev_step_number, 1),
           forget_bias_init='one',
           return_sequences=False,
           stateful=True))
  model.add(Dense(hidden_neurons))
  model.add(Dropout(0.2))
  model.add(RepeatVector(nxt_step_number))
  model.add(LSTM(hidden_neurons,
           batch_input_shape=(batch_size, prev_step_number, 1),
           forget_bias_init='one',
           return_sequences=True,
           stateful=True))
  model.add(TimeDistributed(Dense(1)))
  model.compile(loss='mse', optimizer='rmsprop')

 print('Training')
 numIteration = len(X_train)/batch_size
 for i in range(epochs):
     print('Epoch', i, '/', epochs)
     for j in range(numIteration):
        print('Batch', j, '/',numIteration,'Epoch', i)
        model.train_on_batch(X_train[j*batch_size:j*batch_size+batch_size,], y_train[j*batch_size:j*batch_size+batch_size,])
    model.reset_states()

 print('Predicting')
 predicted_output = model.predict(X_test, batch_size=batch_size)

########

 def train_test_split(df, test_size=0.3):
    ntrn = int(round(len(df) * (1 - test_size)))
    X_train, y_train = _load_data(df[0:ntrn])
    X_test, y_test = _load_data(df[ntrn:])
    return (X_train, y_train), (X_test, y_test)

  def _load_data(data):
      prev_interval_length = prev_time/prev_step_number
      nxt_interval_length = nxt_time/nxt_step_number
      cols = len(data[0])
      rows = len(data)-(nxt_time+prev_time)
      docX = np.empty([rows,prev_step_number,cols])
      docY = np.empty([rows,nxt_step_number,cols])

      for i in range(len(data)-(nxt_time+prev_time)):
          for j in range(prev_step_number):
              docX[i,j,] = data[i+prev_interval_length*(j),].reshape([1,cols])
         for j in range(nxt_step_number):
               docY[i,j,] = data[i+(prev_interval_length*prev_step_number)+nxt_interval_length*(j),].reshape([1,cols])

     return docX, docY

If I reset the states after each training epoch, then sth close to a constant value  is predicted for all 5 future values, But if I don't reset it then the predicted values increase but don't follow the right patterns. In the following figures you can find the plots for 5 future predicted values separately vs their real values.

Then I started to use stateless mode. I changed my model as follows:
model = Sequential()
model.add(LSTM(hidden_neurons,
           input_shape=(prev_step_number, 1),
           forget_bias_init='one',
           return_sequences=False))
  model.add(Dense(hidden_neurons))
  model.add(Dropout(0.2))
  model.add(RepeatVector(nxt_step_number))
  model.add(LSTM(hidden_neurons,
           forget_bias_init='one',
           return_sequences=True))
  model.add(TimeDistributed(Dense(1)))
  model.compile(loss='mse', optimizer='rmsprop')
  model.fit(X_train,y_train,batch_size = batch_size, nb_epoch = epochs, validation_data = (X_valid,y_valid),shuffle = False)

In the following figures you can find the plots for 5 future predicted values separately vs their real values by using this model. These plots show that always we can predict the first future value with high accuracy in stateless mode, although the second ones' pattern is similar to the first ones but I don't know why  the prediction accuracy starts to decrease (the predicted values start to shrink)!! Could anyone help me to fix this problem? What is the right policy for resetting? Which model is right  here (stateful or stateless)?

in the stateful case your prediction will depend on internal state values (the initial states for each batch/last states from the previous batch) that will be changing over time. This might lead to some instability issues.
When I tried it it worked better by setting the learning rate in stateful mode some order of magnitude lower. You also need to take into account that in stateful mode your model will always be a bit more biased towards the end of your sequence.
You might also maybe want to try pretraining stateless and then moving to stateful for finetuning.

@lemuriandezapada Thank you

setting the learning rate in stateful mode some order of magnitude lower
I don't understand what you mean. My optimizer is rmsprop and the default value for lr is 0.001

@mininaNik
I have a question here. Why did you use two LSTM layers here?

@gamehere007  The first one is encoder and the second one is decoder.

Hi! Where is the 5 future values, which you wanted to predict? As I see on your plots your have only prediction "for past" and no future values on plots.


Add list shortcut image

Codecov Report

Merging #216 (2758f2a) into master (476194c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #216   +/-   ##
=========================================
  Coverage     65.81%   65.81%
  Complexity      717      717
=========================================
  Files           114      114
  Lines          2542     2542
  Branches        294      294
=========================================
  Hits           1673     1673
  Misses          753      753
  Partials        116      116

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 476194c...2758f2a. Read the comment docs.


Error on range when using double-calendar and same day is set for start and end date

In my use case I am doing date range reporting, with month to date being the default option. When the system sets date for start and end date as the same day on the first day of the month, we get an invalid date range error when trying to select a new date. I would expect that even on a date range, you ought to be able to select start and end date to match sometimes, e.g. I only want to see one day of data, rather than build something to switch to single calendar if you want to do that.

I'll try and take a look sometime next week. Though the code is quite user friendly so feel free to take a look yourself. Should be an easy solve. I assume you tried the 'same_day: true' key: vale?

'same_day_range: true' sorry

@fafnirbcrow Can you confirm that the same_day_range isn't working for you?

@tyvdh I apologize, I somehow missed that that had gotten pulled in my project at some point in the past. Amazing how it works when you turn the setting on properly. Mi culpa. Thanks for the quick help!

@fafnirbcrow No worries. Glad it's working for you!


Fixed & Enhanced the Footer section

Previously, Footer section had large gap between the columns. Now it's fixed and compatible for all devices.
resolved the conflicts. issue related to #260
@c4coderandcreator

the reason conflicts are not allowed

yeah i understood, I solved it.👍


[DERCBOT-781] AI Orchestrator API - Generate sentences

… caller. Add of the endpoint to generate a list of sentences from a prompt.
Exemple of fast API call on Generate Sentences (replace the apiKey) :
{
"llm_setting": {
"provider": "AzureOpenAIService",
"apiKey": "",
"model": "gpt-35-turbo",
"deploymentName": "gpt-35-turbo",
"apiBase": "",
"apiVersion": "2023-03-15-preview",
"temperature": "0.7",
"prompt": "List 5 ice cream flavors."
}
}

Replaced by : https://github.com/CreditMutuelArkea/tock/pull/289


Restart daemon

How about setting up a simple daemon that will periodically check if chaosbot is still up and running? If it's no longer running, simply restart the process. Would be useful for times when the server owner is unavailable and something breaks.

Supervisor is apparently tasked with just that already: https://github.com/chaosbot/chaos/pull/6#issuecomment-303291429


???

in maps.w.d.b

Number of crashes: 1
Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/dmytro-karataievs-projects/android/apps/com.adkdevelopment.earthquakesurvival/issues/5816876e0aeb16625b4b33ad

Check this: http://stackoverflow.com/questions/36147370/released-unknown-imagedata-reference-on-map-clear


v3

This new release incorporates a number of changes:

Move to the Spring Boot framework
Upgrade to Spark 3
Refactored FHIRPath class model
Request caching
Improved error handling and reporting
Improved configuration
Support for invoking the aggregate operation with a GET request
Bug fixes and performance improvements

Breaking changes

Changes have been made to the encoding of the Parquet files from FHIR - any pre-existing Parquet data will need to be re-created from the FHIR sources before use with Pathling 3.
The format of the request to the aggregate operation has been simplified, removing the labels and flattening the structure of the parameters.
Configuration has been completely reworked - see the Configuration page for the new variable names.
Pathling now uses Spark 3 - this change will need to be reflected in any Spark cluster installations used to host Pathling.
The semantics of the subsumes function have changed, and may yield different results in Pathling 3. See
subsumes for the new specification.
Source URLs used with the import operation now need to be whitelisted, for security purposes. A list of valid prefixes can be configured, by default you can import from file:///usr/share/staging.

Resolves #2, #6, #70, #76, #88, #157, #167, #175, #179, #181, #182, #184, #185, #186, #196, #200, #202, #212, #213, #218, #220, #229.
Tasks:

[x] Update all dependencies to their latest versions
[x] Update licences and licence plugin configuration
[x] Commit design updates
[x] Create a description of the breaking changes within the release
[x] Add configuration to force correct language detection for repository
[x] Add config to GitHub Actions to publish JAR to GitHub Packages

Here is a diagram representing the new FHIRPath class model:

/cc @piotrszul

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9823f6e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #138   +/-   ##
=========================================
  Coverage          ?   80.43%
  Complexity        ?      904
=========================================
  Files             ?      119
  Lines             ?     3659
  Branches          ?      301
=========================================
  Hits              ?     2943
  Misses            ?      571
  Partials          ?      145

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 9823f6e...6b85423. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9823f6e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #138   +/-   ##
=========================================
  Coverage          ?   80.43%
  Complexity        ?      904
=========================================
  Files             ?      119
  Lines             ?     3659
  Branches          ?      301
=========================================
  Hits              ?     2943
  Misses            ?      571
  Partials          ?      145

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 9823f6e...6b85423. Read the comment docs.


Add french language for the number prompt

Hi,
After testing the number prompt on teams I just found an "error".
If your local is "fr" you can't use the number prompt since the language isn't imported in the prompt
Error: E_MISSING_BUNDLE: {"locale":"fr"}     at createError (...\node_modules\cldrjs\dist\cldr.js:339:11)     at validate (...\node_modules\cldrjs\dist\cldr.js:355:10)     at Cldr.main (...\node_modules\cldrjs\dist\cldr.js:669:3)     at numberNumberingSystem (...\node_modules\globalize\dist\globalize\number.js:553:14)             at numberPattern (...\node_modules\globalize\dist\globalize\number.js:1433:37)     at Globalize.numberParser.Globalize.numberParser (...\node_modules\globalize\dist\globalize\number.js:1545:13)     at NumberPrompt.<anonymous> (...\node_modules\botbuilder-dialogs\lib\prompts\numberPrompt.js:69:51)     at Generator.next (<anonymous>)     at ...\node_modules\botbuilder-dialogs\lib\prompts\numberPrompt.js:7:71     at new Promise (<anonymous>) {   code: 'E_MISSING_BUNDLE',   locale: 'fr' }
To fix that , in lib/prompts/numberPrompt.js

[...]
const Spanish = require("cldr-data/main/es/numbers.json");
const French = require("cldr-data/main/fr/numbers.json");
const Globalize = require("globalize");
Globalize.load(Chinese, English, Dutch, German, Japanese, LikelySubtags, NumberingSystem,
Portuguese, Spanish, French);
[...]

If this can be added that will be very nice (it's sad to extend the lib for that)
regards,
Arthur Rouet.

@mdrichardson Can you comment on this?

@tracyboehrer This is unrelated to the changes that I made to Confirm and Choice Prompts, as it uses the cldr npm package. I can look into it, however.

@erbizard @tracyboehrer Looks like this may be a mistake as Number Prompt supports all of the same languages as Confirm/Choice prompts except French.
It looks like we may be moving away from the cldr package. I'll add a fix for this, but I'll need to wait until after we decide what to do with the cldr package.

I've approved the PR. Just waiting for a JS person (@christopheranderson) to chime in and merge.

PR is currently failing to build. Working with @mdrichardson to get it fixed so we can merge.

@cleemullins Looking into it now.


not work

hi bro this not work

Hi,
Thanks for reporting it.
looks like the final executable was missing when i created the zip file, strange to me.
fixed, you can run install script again.

tanx bro it's ok


Request

Can you add an option to block accounts that don't follow you on instagram?

Actually I think that should be possible.
Could be a separate block option from the unfollow option.
I'll leave this open for now.
I don't think the demand for it is too great, but if the implementation would be as simple as it seems, then I don't see any reason for not adding it.


Add canonical urls for any address that also has a slug

(1) Decide if the slug or the id is the canonical url.
(2) Put a <link rel="canonical" href="{full external url}"> in the <head> when not on the canonical url.
(3) Generalize slugs so that everything has them. Probably.

Including for leagues as /2017/july/ or /2017-july/, etc.


Add git minimum version requirement

We are using rev-parse --git-path hooks, which on some RHEL setups and ancient git versions is broken. So let's make that failure more loud.
The version requirement is a rough approximation of when it should have started to work, based on git blame archeology, see https://github.com/git/git/commit/0701530c2663f82ff4b678de27db4c61f8b3092f
Issue found by @fritzgoebel

could you also add it into README?

Fritz confirmed it works :)


Offset in big vehicle Bounding Boxes position

CARLA version: 9.14
Platform/OS: Linux
Problem you have experienced: There is an offset in the position of the bounding box of big vehicles.
I am currently working to generate auto-labeled data. I generate point clouds, images and bounding boxes. I get the bounding boxes for each actor and I noticed that the bounding box for large vehicles like trucks or buses does not perfectly match the object in the point cloud. It can be seen in these images:

I know it is not the code because this does not happen with other actors or environment objects, as you can see in the example:

Same question to me, how to solve it?

Hi, I had a look at the bus, and you're right, but there is a reason:
If you look at this image, you can see how the left mirror is creating that offset, since the right mirror is not in the same position as the left. So when creating the bounding box, unreal is adding that extra size to the left side of the bus.
The bounding box is working as intended.

I've also checked the other big vehicles, and as you can see, their bounding box is correct, so, which ones do you mean are wrong, besides the bus?

I'm closing the issue, since the problem seems solved.
Thanks for your time.


adding a BMC entry with option_match in inventory doesn't work

Hi,
i find a new issue.
When I want to add a BMC entry with option82 match, the entry in dhcp file isn't added.
On the other hand, the entry with mac works.
          bmc:
            name: pm0-bmc05
            #mac: 08:00:27:0d:f8:b2
            option_match: |
              substring (option agent.remote-id, 0 , 64) = "0"
              and option agent.circuit-id = 01:00:10
              and (substring(option vendor-class-identifier, 0, 10) = "XXXX S BMC")
            ip4: <IP_ADDRESS>
            network: ice1-1

Kind regards,

Hello,
Fixed in https://github.com/oxedions/bluebanquise/commit/0931f6ca46dac6cebb262b81a2572b0947bdf777
My apologies for this bady copy/past :-p
Ox

great!
Thanks


Update design of the "Add Field" button in schema editor

Before:

After:

Hover:

I followed this design below. There are subtle color mismatches because I was trying to use our color variables.

Thanks for this, it does simplify a lot and I adjusted it as you suggested 🥂
Regarding always using class names for targeting I sometimes find it too bloaty and coming up with class names for every one-off little detail can be tiring that's why I avoided it in this case


Stack Overflow from analysis server

Analyzer Feedback from IntelliJ
Version information

IDEA IU-182.3684.101
2.0.0-edge.eab492385c3f345cb2f44f3b702b0e30e4a9c107
IU-182.3684.101, JRE 1.8.0_152-release-1248-b8x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.13.1 unknown, screens 1920x1080

Exception
Please append the contents of:
file:///private/var/folders/c0/n0mfd4qd2cx1s23z86jcwrd80000gn/T/report.txt
Dart analysis server, SDK version 2.0.0-edge.eab492385c3f345cb2f44f3b702b0e30e4a9c107, server version 1.20.5, error: Analysis failed: /Users/seifon/Project/mystery_live/lib/common/net/Address.dart context: exception_20180819_110309_577
Stack Overflow
#0      _HashMap._addEntry (dart:collection/runtime/libcollection_patch.dart:212:3)
#1      _HashMap.putIfAbsent (dart:collection/runtime/libcollection_patch.dart:145:7)
#2      Scope.define (package:analyzer/src/dart/resolver/scope.dart:1026:21)
#3      LibraryScope._defineLocalNames (package:analyzer/src/dart/resolver/scope.dart:632:7)
#4      LibraryScope._defineTopLevelNames (package:analyzer/src/dart/resolver/scope.dart:651:5)
#5      new LibraryScope (package:analyzer/src/dart/resolver/scope.dart:587:5)
#6      new ScopedVisitor (package:analyzer/src/generated/resolver.dart:7078:28)
#7      new AstRewriteVisitor (package:analyzer/src/generated/resolver.dart:60:9)
#8      new ExprTypeComputer (package:analyzer/src/summary/link.dart:2228:33)
#9      TypeInferenceNode.evaluate (package:analyzer/src/summary/link.dart:4849:26)
#10     TypeInferenceDependencyWalker.evaluate (package:analyzer/src/summary/link.dart:4696:7)
#11     DependencyWalker.walk.strongConnect (package:front_end/src/dependency_walker.dart:149:13)
#12     DependencyWalker.walk (package:front_end/src/dependency_walker.dart)
#13     VariableElementForLink.inferredType (package:analyzer/src/summary/link.dart:5119:47)

https://github.com/dart-lang/sdk/issues/34068


Mob's aggro distance not precise enough. Can we customize aggro distance drawn?

Even though my character (or the player dot) stands visually outsite a proximity mob's aggro range (very close but still outsite), the mob can be pulled. I can be sure the mob isn't moving.
Currently only found this in HoH, I haven't tested it in other deep dungeons yet. But judging by the code the aggro distance is a fixed value, so it should be the same in all the cases.
I am thinking it's probably a good idea that we would be able to change/tweak this value to our liking in configuration.
Where?
Instance: HoH

A dynamic mob aggro range tracker which will update accrutate data is already in the planned features. Would be cool because there are a few monsters where it's off by quite a bit

Sorry for the late reply. Yes this is already planned. I just dont have a clue how to meassure it correctly since i noticed that getting aggro is not always instant.
I was thinking to give all mobs generally a little bit more if the hitbox is big. Bigger mobs tend to have a larger area.

this would be a gerat feature and I'd love to help if you need to test some certain mobs
btw I noticed you said

I just dont have a clue how to meassure it correctly since i noticed that getting aggro is not always instant.

yes, though this is no news anymore just FYI it is related to the 3-second server ticks - at least that's how we test savage bosses, as far as I know. i.e., if no aggro in 3 seconds then it's safe to say the aggro range is smaller than that. I assume it's the same system as in DD but haven't tested it seriously.
maybe just get an approximate value and round it up by 0.1 (e.g., 16.82 > 16.9) should be far enough for most use cases I guess...?

just addad an opt in data collection system helping me to improve mob information.
gonna add movement time tracking and as well aggro distance measurement soon :3


[BUG] Duplicate GET parameters are dropped when the params kwargs is used

Using curl_cffi 0.6.2
Easier to explain with an example.
>>> from curl_cffi import requests
>>> requests.get("http://localhost:8000/?a=1&a=2", params=dict(b=3))
<Response [200]>

On the web server we receive GET /?a=2&b=3 (INCORRECT, missing first "a" parameter)
If using normal requests 2.31.0:
>>> import requests
>>> requests.get("http://localhost:8000/?a=1&a=2", params=dict(b=3))
<Response [200]>

On the web server we receive GET /?a=1&a=2&b=3 (CORRECT)

Fix is on the way, in the meanwhile, you can encode the url with urllib.parse yourself, without using the params parameter.


Allow the attached debugger to debug python installs.

Allow the attached debugger to debug installed python libraries used by your scripts.
Using the justMyCode configuration parameter when launching the unreal attached debug session.
So installed python libraries can be debugged along with your own python code, which can be useful in certain scenarios.

Made a pull request for the issue: #24.
Covering this issue and allows for further development if another similar issue arises.


chore(linode): pin kernel version

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1123  👈
#1122
#1119
#1118
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on  Graphite


ci: integrate the codecov

Add code coverage detection and ensure that 60% or higher of new code is covered with unit tests.
Currently we only focus on the coverage in the ./pkg directory, and will ignore the following packages or files in this directory:

"pkg/apis"
"pkg/client"
"*_test.go"
"fake_*.go"

Does the coverage data here include packages without any test files? See https://github.com/golang/go/issues/24570
I did a workaround in kelemetry because of this issue https://github.com/kubewharf/kelemetry/commit/26472190a8aa3ed42bb69bd38f0d3aa241216464

Does the coverage data here include packages without any test files? See golang/go#24570

I noticed this problem and it seems to be solved by adding the -coverpkg=./pkg/... parameter to the go test command. When I experimented in the local repository, it seemed that the coverage would include all packages in the ./pkg directory, even if there was no test file: https://github.com/qclc/kubeadmiral/pull/2#issuecomment-1777146050
According to experimental results, the old test report will not cover packages that do not contain single tests, but the new test report will cover all packages, even if there are no unit tests in them.

@qclc It seems the packages were included simply because your PR had diff in those packages. Maybe try with another commit that does not involve those packages? Would the total coverage decrease again?

@qclc It seems the packages were included simply because your PR had diff in those packages. Maybe try with another commit that does not involve those packages? Would the total coverage decrease again?

I experimented again and only modified the package containing the unit test. The coverage remained unchanged, which was also ~24% : https://app.codecov.io/gh/qclc/kubeadmiral/pull/4 . I also ran go test locally and observed the test report. After adding the -coverpkg=./pkg/... parameter, the test report will include all the packages in the ./pkg directory. Otherwise, it won't. It seems that the test report after adding the -coverpkg=./pkg/... parameter is fully covered.

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

Sorry to miss this comment on issue (https://github.com/golang/go/issues/24570#issuecomment-499863491) : using -coverpkg does not actually help if the package is never called in any test at all. -coverpkg is a cover-up that allows packages from a different package to provide coverage for this package.
The end result still requires some additional work, as @SOF3  did in repository kelemetry. Please take a review.


empty return statement should be a compiler error when return type is specified

Currently this function compiles just fine
function foo(x): string {
	return;
}

I understand that it's happening because undefined is a valid result for a variable of type string, and this sort of related back to #185, but a midway point could be to simply require the return statement to not be empty.
Similarly, this code fails to compile:
function foo(x): string {
}

But this one compiles:
function foo(x): string {
	if(false) {
		return;
	}
}

I think the expected behavior is that every branch should require an explicit return statement.
A side benefit of this is that you can get exhausting matching completeness basically for free:
function foo(x: number | string | boolean): string {
	if(typeof x === 'number') {
		return x.toString();
	} else if (typeof x === 'string') {
		return x;
	}
}

Currently the above compiles, but if TypeScript required an explicit return in every branch for non void return functions, there would be a compiler error because there are remaining types in the union. However this would compile:
function foo(x: number | string | boolean): string {
	if(typeof x === 'number') {
		return x.toString();
	} else if (typeof x === 'string') {
		return x;
	} else if (typeof x === 'boolean') {
		return ''+x;
	}
}

This is pretty nice! There is one edge case still -- because of the implicit void included in x, calling foo(null) or foo(undefined) will return undefined. I don't know what to do about this because it relates pretty heavily to #185. I think for now it can be ignored, and whatever resolution that (hopefully) happens there will take care of it.

function foo(x: number | string | boolean): string {
    if(typeof x === 'number') {
        return x.toString();
    } else if (typeof x === 'string') {
        return x;
    }
}

as a note, currently if you compile this code snippet with --noImplicitReturns flag you'll get error
test.ts(1,45): error TS7030: Not all code paths return a value.

Ah -- that's exactly what I was looking for. Thanks @vladima! I'm guessing this will be in 1.8.0?

yes. And it is already in typescript@next

so does this take care of the issue in OP?

I don't entirely think so; this does't cover accidentally omitting a return expression. But I shouldn't put words in @tejacques' mouth, so I'll let him speak for himself. :smile:

we can make --noImplicitReturns flag return statements with no expression if the function return type is not void or any. not sure if that would be too restrictive though.

I personally don't think it's too restrictive because the programmer has already declared their intent by specifying a return type on the function. If it remains as a flag, then doubly-so because it is opt-in. It's also a lot clearer that it is intentionally returning undefined if it is explicitly written out.

@vladima thoughts?

Accepting PRs. Make this an error only under the noImplicitReturns flag

Just for the interest of people here. Note the original example:
function foo(x): string {
    return;
}

will automatically be an error in --strictNullChecks : https://github.com/Microsoft/TypeScript/pull/7140 as I understand :rose:

thanks @martine!


add arg to support delete of named kv root

add arg to support delete of named kv root

agreed with @bitsofinfo .  Like the simplicity of this tool.  The only constraints seems like it doesn't take into consideration of deltas such as update or delete.  If you can support deltas update/delete from git, that would be great.  By supporting deltas, you don't stress out consul because you only update what needs to be updated from git

@josephlim75 please feel free to submit a PR!


Consistently handle CLI errors

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2200
Originally created by @DouweM on 2020-07-28 17:18:59

View 1 previous comment from the original issue on GitLab


Revert "Disable renovate until it can handle lockfile 9"

Reverts dotkom/monoweb#916

ah that explains a lot


Tutorial pages need content

this will be an issue for a long time...
It will probably be closed in the future and reopened under the different sections and categories

Work in progress issue needs to be more descriptive


toPlainText have a \n at the end

https://github.com/singerdmx/flutter-quill/blob/b8ebcbdbda2191a059b42ce6f6e438b5ab347b47/lib/src/models/documents/document.dart#L349
I don't know why toPlainText() have a line break at the, if modified it would it affect any thing ?

I think it will break a lot of things

alright, thanks for replying.


6470b Hd4000 Monterey 12.6 brightness slider missing

Hi since last 2 3 years I'm using my ProBook 6470b for my DJing/live music perfoming installed mac using your clover package creator Thank for your awesome work... @chris1111
Currently i have Monterey 12.6 running on 6470b (i7 3520m) pre install check and testing... For moving from high Sierra to Monterey (would love get suggestion big sur or Monterey?)
Monterey is running good (nice hd 4000 patch bro @chris1111 ) so far but i don't have brightness (so far my main concern is that)
No brightness slider in sys pref. also
Please help me get past this issue
I need Max perfomance out of my 6470b because this is the only thing i have for making music and perfoming at stage
Cpu : i7 3520m
GPU : Hd4000 (qe/ci working with hd4000 but no brightness control in sys pref and control center)

I'm not good with dsdt patching...and i tried a lot with it...
Bu I'm getting so many errors there

commented now
Would love to know if bigsur 11.7 will have brightness with hd4000 patch on 6470b

Hi
my experience with a slightly different combination: 6470b i5-3360M (HD4000) 1600x900 Monterey 12.6.1 fresh install yesterday: brightness control is working fine.
I selected both (high-screen) patches for 1600x900 in the "Install HP-Probook-Elitebook-macOS.pkg": "Intel HD4000 for 7 Series" and "HDMI High screen", after that I run the generated "PatchHD4000" app.
Maybe this helps, maybe not.


Version of libskia.so

Hi! Thanks for alpine package. Whats version of libskia.so your use? libskia.so needed for applications using SkiaSharp?
I'm trying use simple application with Avalonia on Alpine (https://github.com/AvaloniaUI/Avalonia/issues/2464) with your package, but does not work - don't throw errors, but generate empty image.

I tested the package on Alpine 3.9 on docker, and I used an empty project with the SkiaSharp package (v1.68.0) and this package (v1.68.0). You also need to have fontconfig installed on your machine


Dev - Infinite spinner while closing account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login to new
go to Settings - Security - Close account
observe the Spinner on Close account button

Expected Result:
Infinite spinner should not be displayed
Actual Result:
Infinite spinner while closing account
Workaround:
unknown
Platform:

Where is this issue occurring?

Web

Version Number: 1.2.36-2
Reproducible in staging?: Needs reproduction (Seems happening only in DEV)
Reproducible in production?: Needs reproduction
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/206235125-3f48bc96-1a81-4d1e-a0b9-2fcbd452e1c8.mov
Expensify/Expensify Issue URL:
Issue reported by: @varshamb
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1670346549403099
View all open jobs on GitHub

I'm not being able to reproduce this in staging/web or any platform/dev. I'm going to ask a bit more in the slack thread.

We rely on the Pusher events clearing the Onyx data after a successful CloseAccount request, I'm guessing that the reporting user may be somehow missing these updates sent through pusher:
https://github.com/Expensify/App/blob/46f8297c62f448180cfc79b8968f9383f1d9e12b/src/libs/actions/User.js#L72-L89

@Beamanator since you worked on the refactor of CloseAccount, do you see why this could be happening?
I'm inclined to just closing the issue because I think this is rare case where the user is missing the pusher events (that's my theory at least). An easy fix could be to clear the Onyx data also on successData, but that would mean that we are not trusting the Pusher which our application heavily relies on.

This has been resolved, Cloudflare was blocking the request api/command=AuthenticatePusher which ended up causing the Pusher not to work.
@sonialiap Can you handle the reporting compensation for @varshamb 🙏

Internal PR that fixed the issue: https://github.com/Expensify/Terraform/pull/616

@varshamb could you please apply for this job https://www.upwork.com/jobs/~01e2831fb3d87a6543

Upwork proposal sent

waiting for  @varshamb to approve offer so that I can issue payment

Payment issued and contract ended, closing


[EE-181] Add IntelliJ plugin check

Generic check to see if a particular IntelliJ plugin has been installed. Motivated by wanting people to have the Detekt plugin installed in IntelliJ. Based on docs here.
I've also pinned the black pre-commit hook to a different version because it was just broken for me.

Will review tomorrow, but there's an intellij required plugins setting built in to intellij which might do the same job as we're doing here

Ooh, that's a good spot! You can pin versions too, which seems way better than this hacky daktari check :tada:


SH Scraper fails

cc @baryluk
SH 2020-03-29T08:00       -       - FAILED 2020-03-29T11:30:08+02:00  # URLs: https://sh.ch/CMS/content.jsp?contentid=3209198&language=DE&_=1584807070095 # Errors: Missing cases. Confirmed cases is None

Duplicate of #303


update and refresh dep

Coverage remained the same at 100.0% when pulling 04aebd3300aba8b51e884c22c0fceda10e33f718 on update-dep into 35c701a207d1a6829c64b0170264df67963a9cad on master.


Rule registration should fail if YAML contains multiple actions

SUMMARY
Users can register rules containing multiple actions, but this is invalid. It will only use the last action in the file, silently ignoring the rest.
ISSUE TYPE

Bug Report

STACKSTORM VERSION
st2 2.10.3, on Python 2.7.12
OS / ENVIRONMENT / INSTALL METHOD
N/A
STEPS TO REPRODUCE
Create this rule:
---
name: relay_to_chat
pack: icinga2
description: Post to chat when icinga2 service state changes
enabled: false
trigger:
  type: icinga2.event.state_change
criteria:
  trigger.type:
    pattern: "StateChange"
    type: "eq"
  trigger.state_type:
    pattern: 0.1
    type: gt
action:
  ref: chatops.post_message
  parameters:
    message: Icinga2 service {{trigger.service}} on host {{trigger.host}} has changed its state to {{ trigger.state|int }}, state type {{ trigger.state_type|int }}
      {{trigger.check_result.output}}
    channel: 'general'
  ref: core.local
  parameters:
    cmd: "echo foobar"

Note the multiple actions.
Register with sudo st2ctl reload --register-rules, and then examine the above rule with st2 rule get icinga2.relay_to_chat
EXPECTED RESULTS
One of two things should happen:
1/ (Preferred) Registration should fail with some sort of fatal ERROR, e.g. "ERROR: Rule has multiple actions. Only a single action is allowed"
OR
2/ It should register and allow me to have multiple actions in a rule.
ACTUAL RESULTS
The rule is registered successfully, but only the last action takes effect:
extreme@ewcdemo:/opt/stackstorm/packs/icinga2/rules$ sudo st2ctl reload --register-rules
Registering content...[flags = --config-file /etc/st2/st2.conf --register-rules]
2019-03-07 16:52:50,606 INFO [-] Connecting to database "st2" @ "<IP_ADDRESS>:27017" as user "stackstorm".
2019-03-07 16:52:50,614 INFO [-] Successfully connected to database "st2" @ "<IP_ADDRESS>:27017" as user "stackstorm".
2019-03-07 16:52:51,047 INFO [-] =========================================================
2019-03-07 16:52:51,047 INFO [-] ############## Registering rules ########################
2019-03-07 16:52:51,048 INFO [-] =========================================================
2019-03-07 16:52:57,908 INFO [-] Registered 12 rules.
##### st2 components status #####
<snip>
extreme@ewcdemo:/opt/stackstorm/packs/icinga2/rules$ st2 rule get icinga2.relay_to_chat
+---------------+-------------------------------------------------+
| Property      | Value                                           |
+---------------+-------------------------------------------------+
| id            | 5c5a137c67824f533c57d138                        |
| uid           | rule:icinga2:relay_to_chat                      |
| ref           | icinga2.relay_to_chat                           |
| pack          | icinga2                                         |
| name          | relay_to_chat                                   |
| description   | Post to chat when icinga2 service state changes |
| enabled       | False                                           |
| action        | {                                               |
|               |     "ref": "core.local",                        |
|               |     "parameters": {                             |
|               |         "cmd": "echo foobar"                    |
|               |     }                                           |
|               | }                                               |
| context       |                                                 |
| criteria      | {                                               |
|               |     "trigger.type": {                           |
|               |         "pattern": "StateChange",               |
|               |         "type": "eq"                            |
|               |     },                                          |
|               |     "trigger.state_type": {                     |
|               |         "pattern": 0.1,                         |
|               |         "type": "gt"                            |
|               |     }                                           |
|               | }                                               |
| metadata_file | rules/relay_to_chat.yaml                        |
| tags          |                                                 |
| trigger       | {                                               |
|               |     "type": "icinga2.event.state_change",       |
|               |     "ref": "icinga2.event.state_change",        |
|               |     "parameters": {}                            |
|               | }                                               |
| type          | {                                               |
|               |     "ref": "standard",                          |
|               |     "parameters": {}                            |
|               | }                                               |
+---------------+-------------------------------------------------+
extreme@ewcdemo:/opt/stackstorm/packs/icinga2/rules$

Probably caused by yaml/pyyaml#165.
Dictionary keys in YAML should be unique, period (and this is a hard requirement in YAML 1.2+).
Silently converting duplicate actions into a list seems like it would contravene the YAML specification and make it impossible to continue support when the PyYAML project fixes that bug.
It's probably better to go with option 1, but fixing it properly means fixing the issue in PyYAML or using the hacks from this gist.