error installing qtum on vps

ubuntu@ip-172-31-46-217:~/qtum$ make -j1
Making all in src
make[1]: Entering directory '/home/ubuntu/qtum/src'
make[2]: Entering directory '/home/ubuntu/qtum/src'
CXXLD    libbitcoinconsensus.la
copying selected object files to avoid basename conflicts...
/usr/bin/ar: u' modifier ignored since D' is the default (see `U')
CXX      libbitcoin_server_a-addrman.o
CXX      libbitcoin_server_a-addrdb.o
CXX      libbitcoin_server_a-bloom.o
CXX      libbitcoin_server_a-blockencodings.o
CXX      libbitcoin_server_a-chain.o
CXX      libbitcoin_server_a-checkpoints.o
CXX      libbitcoin_server_a-httprpc.o
CXX      libbitcoin_server_a-httpserver.o
CXX      libbitcoin_server_a-init.o
virtual memory exhausted: Cannot allocate memory
Makefile:8827: recipe for target 'libbitcoin_server_a-init.o' failed
make[2]: *** [libbitcoin_server_a-init.o] Error 1
make[2]: Leaving directory '/home/ubuntu/qtum/src'
Makefile:13327: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ubuntu/qtum/src'
Makefile:692: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
ubuntu@ip-172-31-46-217:~/qtum$ free -m
total        used        free      shared  buff/cache   available
Mem:            990          46         878           6          65         828
Swap:             0           0           0
Actual behaviour
Tell us what happens instead
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of Qtum are you using?
List the version number/commit ID
Machine specs:

OS:
CPU:
RAM:
Disk size:

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

does it have anything to do with the security settings on my vps? should i edit inbound rules to open all traffic? now it is limited to my current location ip via ssh

Hi Bereska,
The issue is low ram, see where it says: "virtual memory exhausted: Cannot allocate memory". I also noticed you don't have swap enabled, most VPS don't create a swap file by default so I'd recommend doing the following:
dd if=/dev/zero of=/swapfile bs=1M count=3000
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
echo "/swapfile none swap defaults 0 0" >> /etc/fstab

This creates a swap file which will help you build and run Qtum.
The commands create the swap, give proper permissions, enable the swap and activate it on boot time in case your VPS restarts.
Please try the above, it'll solve your issue.

Hi Mikehash, thanks for prompt reply. Sure, i'll try try that. Could you also give me ALL requirements for VPS to stake qtum? Memory (you just covered that), disk space, security settings, etc. I want to configure it the way it could stake qtum at least for a year from now. I am on AWS Linux free tier right now.

actually, it would be great if you could post this kind of information in your tutorials so people could set it all up easily and promptly without waiting for you replies for days. If you want to us to invest in qtum of course. Can anyone answer my question above before the weekend?

1gb Ram is more than enough for staking Qtum. However you do need more than that to compile qtum (around 2gb ram is needed).
Any 20GB disk will suffice for a while, Qtum is quite new and the blockchain is only 245mb right now.
Any VPS will do, AWS is among the best of course, but due to the low ram in the free instance, you need a swap file to help out during build.
Regarding security, there's many tutorials and how-tos online, it really depends on which distribution you're using.
You can take a look at this one if you're using ubuntu
https://www.thefanclub.co.za/how-to/how-secure-ubuntu-1604-lts-server-part-1-basics

thank you


Get unique size for /data1 partition

For some reason the physical nodes return two records for /data1 partition (block device), thus it returns two partition sizes.

Just tested it in vocms0310, so I'm merging it :)

Sure go ahead. I think all unit test fails due to this patch.
https://github.com/dmwm/WMCore/pull/7655
I made a mistake in the dependency. I will fix that.

Bad job! ;)

Hehe, I got a failure merging it, it seems we pushed the button almost at the same time (but you won :))

It was my mistake. I was pushing it merge button. I was trying to reply your Bad job comment.


Is it possible to replace folders names (from the search context) to custom titles in dropdown options at the search page?

docusaurus.config:
themes: [
[
require.resolve("@easyops-cn/docusaurus-search-local"),
/** @type {import("@easyops-cn/docusaurus-search-local").PluginOptions} */
{
language: ["en"],
hashed: true,
indexDocs: true,
indexPages: true,
indexBlog: false,
docsRouteBasePath: "/",
searchContextByPaths: ["user-guide", "developer-guide", "admin-guide"],
hideSearchBarWithNoSearchContext: true,
},
],
],
package.json
"dependencies": {
"@docusaurus/core": "3.0.1",
"@docusaurus/preset-classic": "3.0.1",
"@easyops-cn/docusaurus-search-local": "^0.38.1",

@Elvehnn Try 0.39.0 which supports searchContextByPaths: [{ label: "Community", path: "community" }]

Great! Thanx a lot!

weareoutman and it would be great to be able to  use these labels with i18n for the multi-language apps.

Try v0.40.0:


Create a global downtime for all monitors synced by cli

Requirements for Contributing to this repository

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue, or add one feature, at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.

What does this PR do?
Create a global dowmtime for all monitors synced by cli tool so user would not get false positive notifications, until data failover is completed and monitors have enough data to make correct evaludation, user can manually remove this downtime and monitors can operate as usual.

Description of the Change

Alternate Designs

Possible Drawbacks

Verification Process

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.

Closing. Superceded by https://github.com/DataDog/datadog-sync-cli/pull/212 and https://github.com/DataDog/datadog-sync-cli/pull/211


laravel-popular does not work in laravel / framework v6.0.1

Laravel 6 gives error in the version will update?

Can you share more info about the error?

composer require jordanmiguel/laravel-popular command's output, but only for laravel 6 and above,
_Using version ^1.0 for jordanmiguel/laravel-popular
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install jordanmiguel/laravel-popular v1.0.4
- Conclusion: don't install jordanmiguel/laravel-popular v1.0.3
- Conclusion: don't install jordanmiguel/laravel-popular v1.0.2
- Conclusion: don't install jordanmiguel/laravel-popular v1.0.1
- Conclusion: remove laravel/framework v6.1.0
- Installation request for jordanmiguel/laravel-popular ^1.0 -> satisfiable by jordanmiguel/laravel-popular[v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4].
- Conclusion: don't install laravel/framework v6.1.0
- jordanmiguel/laravel-popular v1.0.0 requires illuminate/support ~5.1 -> satisfiable by illuminate/support[5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.4, v5.8.8, v5.8.9].
- don't install illuminate/support 5.5.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.16|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.17|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.2|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.28|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.33|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.34|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.35|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.36|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.37|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.39|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.40|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.41|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.43|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.5.44|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.6.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.1|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.10|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.11|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.12|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.13|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.14|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.15|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.16|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.17|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.19|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.2|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.20|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.21|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.22|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.23|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.24|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.25|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.26|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.27|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.28|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.29|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.3|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.30|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.31|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.32|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.33|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.34|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.35|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.36|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.37|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.38|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.39|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.4|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.5|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.6|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.7|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.8|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.6.9|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.7.17|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.7.18|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.7.19|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.7.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.1|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.10|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.11|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.15|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.2|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.20|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.21|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.22|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.23|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.26|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.27|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.28|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.3|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.4|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.5|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.6|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.7|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.8|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.7.9|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.8.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.11|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.12|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.14|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.15|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.17|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.18|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.19|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.2|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.20|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.22|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.24|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.27|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.28|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.29|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.3|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.30|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.31|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.32|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.33|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.34|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.35|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.4|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.8|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.8.9|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.1.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.2.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.3.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support 5.4.x-dev|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.1|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.13|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.16|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.2|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.20|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.22|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.25|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.28|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.30|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.31|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.41|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.6|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.1.8|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.19|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.21|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.24|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.25|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.26|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.27|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.28|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.31|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.32|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.37|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.43|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.45|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.6|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.2.7|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.3.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.3.16|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.3.23|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.3.4|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.0|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.13|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.17|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.19|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.27|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.36|don't install laravel/framework v6.1.0
- don't install illuminate/support v5.4.9|don't install laravel/framework v6.1.0
- Installation request for laravel/framework (locked at v6.1.0, required as ^6.0) -> satisfiable by laravel/framework[v6.1.0].
Installation failed, reverting ./composer.json to its original content._

Having same issue with laravel 6.3

i added "dev-master" and it's work!
composer require jordanmiguel/laravel-popular dev-master


New / Edit Operation Step window: Time range fields are being reset

Expected behavior
Using GUI to run through Use Case 6 happy path. Applied a subset_temporal operation.
In the “New Operation Step” window, selected a start time of 2007-01-01
Then cleared the end time field. Expected the start time which had just been entered not to change.
Actual behavior
The start time reset itself to 1980-01-01.
Notes:

Similar behaviour is seen if the end time has been entered and then the start time is cleared. The end time will reset itself to the current date.
Similar behaviour is seen in “Edit Operation Step” window as well as “New Operation Step” window
Similar behaviour is seen for other operations which contain a time range: anomaly_internal and open_dataset

Steps to reproduce the problem

Ensure there is at least one resource of type Dataset in the workspace
From operations panel, select subset_temporal then Apply
In New Operation Step window, select a Dataset resource
Next to TimeRange, enter a start time (the end time field is then automatically populated with today’s date)

Clear the end time field and see that the start time has been reset to 1980-01-01

Enter new end time

Clear start time. Now end time has been reset.

Specifications
Cate 0.9.0-dev.5
Windows 7 Professional

We should switch to simple text fields.

Confirmed fixed in cate-0.9.0.dev.6


Add Api configuration demo for dubbo

Most things out there use spring or spring boot. It would be nice to have a demo for how to configure tracing for dubbo when someone is only using the api (per @chickenlj)
http://dubbo.io/books/dubbo-user-book-en/configuration/api.html
One challenge is I can't see how Dubbo manages lifecycle if any for extensions. It would seem instructions should include shutting down the component.
At any rate I don't know how to do this, except maybe a hard-coded extension factory like so:
public class TracingExtensionFactory implements ExtensionFactory {
  public <T> T getExtension(Class<T> type, String name) {
    if (type != Tracing.class) return null;

    final AsyncReporter<Span> spanReporter =
        AsyncReporter.create(URLConnectionSender.create("http://<IP_ADDRESS>:9411/api/v2/spans"));

    // flush spans on ctrl-c
    Runtime.getRuntime()
        .addShutdownHook(
            new Thread() {
              @Override
              public void run() {
                spanReporter.close();
              }
            });

    return Tracing.newBuilder()
        .localServiceName(/** where to get dubbo's application name */, "foo")
        .currentTraceContext(MDCCurrentTraceContext.create()) // puts trace IDs into logs
        .spanReporter(spanReporter)
        .build();
  }
}

I tried integrating this with spring boot and found I had to manually call the tracing filter setter:
    // TODO: Why isn't TracingFilter.setTracing called automatically by Dubbo's spring stuff
    ((TracingFilter) ExtensionLoader.getExtensionLoader(Filter.class)
        .getExtension("tracing"))
        .setTracing(tracing);

If anyone can try this branch and help me figure out what I don't understand, I would appreciate it. Also we can then have simple instructions for those wanting to try this.
cc @xionghuiCoder @chickenlj
https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing

sent email to<EMAIL_ADDRESS>

Everything in the example related with dubbo seems to be in the right way, i have also tested TraceFilter in a separate Spring project and it works fine (tracing can be auto injected).
Will give a check on the “sleuth-webmvc-example” later, as i have no access to my computer now.

@adriancole please use official dubbo-spring-boot-starter

@mercyblitz The  dubbo-spring-boot-starter adriancole use is the official one.

progress on the spring boot (via spring-cloud-sleuth) side https://github.com/spring-cloud/spring-cloud-sleuth/pull/885

@chickenlj @mercyblitz so I still have one question, which is how to externally register a filter so that all providers and consumers use it (as opposed to setting it on an annotation). We will need this for sleuth as we don't want users to have to change their annotations to switch on tracing

Check concepts of Consumer and Provider in dubbo:
http://dubbo.io/books/dubbo-user-book-en/references/xml/dubbo-consumer.html http://dubbo.io/books/dubbo-user-book-en/references/xml/dubbo-consumer.html
http://dubbo.io/books/dubbo-user-book-en/references/xml/dubbo-provider.html http://dubbo.io/books/dubbo-user-book-en/references/xml/dubbo-provider.html
XML looks like this:

<dubbo:consumer timeout="5000" filter="tracing" />
And annotation or spring boot, use .properties instead, for example:
dubbo.consumer.filter="tracing"
Is this what you want? Adrian
Best regards,
Jun Liu

On 6 Mar 2018, at 3:58 PM, Adrian Cole<EMAIL_ADDRESS>wrote:
@chickenlj https://github.com/chickenlj @mercyblitz https://github.com/mercyblitz so I still have one question, which is how to externally register a filter so that all providers and consumers use it (as opposed to setting it on an annotation). We will need this for sleuth as we don't want users to have to change their annotations to switch on tracing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/openzipkin/brave/issues/632#issuecomment-370695232, or mute the thread https://github.com/notifications/unsubscribe-auth/ARQliQy8Fx6W2c1t1vy_eerUof8K3-gMks5tbkG0gaJpZM4Sa2cy.

spring boot (via sleuth) side of things is near perfect I added some notes https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
I will update the readme shortly about manual config


Added contribution to 129-koch-snowflake.md

Here's my version of the Koch Snowflake challenge.

Well Done ❤

This is so cool!


Pure pattern-matching

This pull-request aims to resolve #149. This will be done in the following steps

[x] Add flag about strictly positive recursion to definitions of ADT in Unif
[x] Add flag about strictly positive recursion in ADT environment (TypeInference.Module.adt_info)
[x] Recognition of strictly positive recursive types in TypeInference
[x] Use information about strictly positive recursion in the effect of pattern-matching (TypeInference.Pattern)
[x] Update translation to Core
[x] Add flag about strictly positive recursion to definitions of ADT in Core
[x] Add effect of pattern-matching to TData type in Core
[x] Adjust internal type-checker for Core

This implementation has some slight problem with generated accessors for recursive records. For instance, when we write the following code
data rec  T = { x : T }
let f (t : T) = t.x

the f function is impure. This problem comes from the desugaring of recursive records. The above definition is a syntactic sugar for
rec
  data T = T of { x : T }
  method x { self = T { x } : T } = x
end

Notice, that the method is in recursive block, and therefore is impure, even if the pattern-matching on self is pure.

All the changes look good to me, however I did look at the problem mention above and there seems to exist simple (partial) fix. It will make record accessors non recursive when record is marked rec and when it is in rec block with only other records, data definitions and labels. It won't always make accessors pure, like in this piece of code:
rec
  let foo (x : T) (n : Int) =
    if n == 0 then x
    else foo (x.x n) (n - 1)

  data T = { x : Int -> T }
end

If we ever decide to make non-termination detection more precise, for example like the one that's present in coq, my change will become redundant as whole problem will be solved. Until then it will help with the not obscure code.

changes mentioned:
diff --git a/src/DblParser/Desugar.ml b/src/DblParser/Desugar.ml
index 27d4fe2..ed8bcae 100644
--- a/src/DblParser/Desugar.ml
+++ b/src/DblParser/Desugar.ml
@@ -42,6 +42,19 @@ let tr_ctor_name' (cname : Raw.ctor_name) =

 let with_nowhere data = { pos = Position.nowhere; data = data}

+let rec node_is_rec_data (def : Raw.def) =
+  match def.data with
+  | DRecord _ -> true
+  | DData   _ -> true
+  | DLabel  _ -> true
+  | _ -> false
+
+let node_is_data_def (def : def) =
+  match def.data with
+  | DData  _ -> true
+  | DLabel _ -> true
+  | _ -> false
+
 let annot_tp e tp =
   { pos = e.pos;
     data = Raw.EAnnot(e, with_nowhere tp)
@@ -751,6 +764,11 @@ and tr_def ?(public=false) (def : Raw.def) =
   | DOpen(pub, path) ->
     let public = public || pub in
     [ make (DOpen(public, path)) ]
+  | DRec(pub, defs) when List.for_all node_is_rec_data defs ->
+    let public = public || pub in
+    let dds, accessors = tr_defs ~public defs
+      |> List.partition node_is_data_def in
+    make (DRec dds) :: accessors
   | DRec(pub, defs) ->
     let public = public || pub in
     [ make (DRec (tr_defs ~public defs)) ]

@Foxinio These changes looks reasonable, but I think we should merge them in a separate pull-request. This PR propose basic solution to the problem of pure pattern-matching that has some limitations, but has no edge cases. Your fix improves the solution, but is not perfect, and in a long run will be probably replaced by something better. Having separate commits for them would make history cleaner, and it would be easier to revert your changes in order to provide the final solution.


Snake Case Contract resolvers

Creating Snake case contract resolvers to both forms of snake case.

snake_case1 or
snake_case_2

:+1:

This can be a separate package or be something that a user does.

@JamesNK is right.
FYI @dschniepp https://github.com/RaphHaddad/Newtonsoft.Json.Serialization.ContractResolverExtentions


Add support for error templates in tests

PR checklist

[ ] Addresses an existing issue: #0000
[x] New feature, bugfix, or enhancement

[x] Includes tests

[ ] Documentation update

Overview of change:
It's pretty unwieldy to write and maintain test for rules that contain a name in the error message (e.g. prefer-const, no-unused-variable, no-shadowed-variable, ...). I added basic template support to error message substitutions which uses node's util.format() to replace placeholders.
Syntax is inspired by python: name % (substitution1[, substitution2, ...]). I doubt this will accidentally break anyone's tests.
The added test shows best what can be done with this.
As an example I also rewrote the tests of prefer-const to use templates.
Is there anything you'd like reviewers to focus on?
Do you have a better idea for the syntax?
I'll add documentation once there is consensus regarding the syntax.
CHANGELOG.md entry:

Is it common to manually generate the .lint file errors? My workflow is usually to write out the file without the errors, run the test, then copy the generated actual output. This feature seems unnecessarily complex.

Is it common to manually generate the .lint file errors?

At least I do. And given that @andy-hanson uses message substitutions a lot in his PRs, I think he also does.
Call it test driven development if you like. I want to test what I expect the implementation to do instead of using the output of the initial implementation for future testing.
Your workflow works for setting up the initial test. When the rule changes, e.g. finds more failures or changes its error message, you will also have to edit the test by hand.

also needs docs. please update https://github.com/palantir/tslint/blob/master/docs/develop/testing-rules/index.md

@nchen63 I updated the implementation and added docs

@nchen63 @adidahiya you both approved this PR. Can this be merged? I recently missed this feature while I refactored some rules and needed to edit their tests.

@ajafff thanks for the reminder, sorry for the delay.


Add higher version of webpack-subresource-integrity

Fixing webpack-subresource-integrity security issue

#!/bin/bash -eo pipefail
make license-check
bin/licensei check
gopkg.in/square/go-jose.v2: no license file found
make: *** [main-targets.mk:133: license-check] Error 2
Exited with code exit status 2
CircleCI received exit code 2

#382 ought to fix it

@xyztdanid4 PR merged


Support F# 4.1?

Thoughts on bumping FSharp.Core to latest nuget? Looks like things are set to 4.0 and with no binding redirect access, there's no way to address this ourselves unless I've missed something.
Changing binding redirect to <IP_ADDRESS> for the CLI caused the precompiled function app to work locally at least.

@fabiocav have you looked at this at all? Any thoughts on whether this is safe?

Another package that would need to be bumped is Newtonsoft.Json, 10.0.1 fixed working with FSharp's list type in 4.1: https://github.com/JamesNK/Newtonsoft.Json/issues/1180

Moving Fsharp.Core to latest should be pretty safe. We can validate and perhaps @sylvanc can comment as well.
For JSON.NET, since it is a major version bump, it has the potential to be impactful, but, aside from scenarios where you're binding to JSON.NET types, you'd still be able to reference higher versions and bind to those assemblies though.

Bumping FSharp.Core should be good. @dsyme may jump in, but I don't think there are any problems.

why it's postponed again?
Since there is no solution for binding redirects, it's harder and harder to keep project to work in Azure Functions

@ed-ilyin not postponed, just updated to reflect the sprint we're currently on. This unfortunately wasn't addressed in the previous sprint.

Please, reopen as change was reverted

This was closed  as it was a 1.0 (current runtime) item and it won't be done there. 2.0 is already on the later F# Core version (and will be on the latest available at the time of release) and we have this issue open (working through a couple of minor issues with the team) for the compiler service https://github.com/Azure/azure-webjobs-sdk-script/issues/1931


added unalias cleos

added unalias cleos for people who followed the instructions from the eosio dev docs and got an Error: No such container: eosio

It would be good to elaborate and specifically address the issue without referencing other repositories.
Run ‘unalias cleos’ and try again ```

I'll merge then edit and added your comments @chris-allnutt  ..


Support --indent 0

Problem Statement
Today, the flag --indent is limited to values 1-8.
In some cases, it also makes sense to use indentation 0, further compacting the resulting xml...
Expected Result
<?xml version="1.0"?>
<simple>
<element_1>value 1</element_1>
<element_2>value 2</element_2>
</simple>

Ok, let it be.


New apps wo router using main, errors twice on load, every time

Problem
Apparently some new warnings are triggered by the built in behavior of dioxus. That seems undesirable 😉
ERROR GITDIR/dioxus/packages/core/src/properties.rs:144 It looks like you called the component App like a function instead of a component. Components should be called with braces like `App { prop: value }` instead of as a function
demo.js:449:21

To be clear, @ealmloff , it looks like this is from https://github.com/DioxusLabs/dioxus/pull/2461/files#diff-e6199434c34c915eed237c16bcdf8167d70272bafd878fb3c95054939c585e11R122
Steps To Reproduce
Repro with dx new, false router, use dioxus local with main HEAD instead of crate (dioxus = { path = "../dioxus/packages/dioxus", features = ["web"] }), then dx serve
Expected behavior
Don't throw errors for a starter app automatically!
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:

Dioxus version: main
App platform: web

Questionnaire

[x] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

https://discord.com/channels/899851952891002890/1252735056242278450/1252736410885161050 might add more context


Installing to Android devices

Hi, this plugin is so wonderfull, im successfully use this plugin on windows build, but i got problem when i need to build to android, can i  get some help or advice ? :(
im now on Parse URI scheme credentials PLIST file, and its done..
but after that, when going to Download and install PlayServicesResolver, idk what to do :(, can i get some advice on this sir? thankyou so much

like, maybe i need some tutorial to installing for Android build


🚀 Feature: Upgrade TFB Network to Minecraft 1.20.1

🔖 Feature description
Upgrading servers to Minecraft 1.20.1
🎤 Context
Minecraft 1.20 is out and we need to keep up if we want to keep our players around and get all the new exciting features!
✌ Possible Implementation
It's been highly requested that we do NOT reset survival servers like Vanilla/Factions.
If there is no other thing to do than resetting the world, we should consider making a NEW server instead of upgrading the current one.
We should allow players to finish playing 1.19 and when that version is "dead" we should move the world to our Museum server, where players can teleport to players homes and remember the good times.
Servers that are ready to be updated:

[ ] Vanilla
[ ] Factions
[ ] Lobby
[ ] Parkour
[ ] Creative

List of plugins not updated to 1.20 yet (or not downloaded yet):

Reconnect
PlayerReferrals
EssentialsX
HexNicks
VoidGen
Vulcan @lucas2kdk
CoreProtect
ParkourTopTen
SaberFactions
PlotSquared @KatieDeForest
PlotHider

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find any similar issue

Are you willing to submit PR?
Yes I am willing to submit a PR!

Added Plotsquared 7.0.0-RC 2 to our artifactory, as it supports Minecraft version 1.20.1


Parsing required slots prior to filling

Rasa Core version: 0.9.6
Python version: 3.6.5
Operating system (windows, osx, ...): OSX
Issue:
I have a question concerning the FormAction class. I want to parse certain required slots before they are filled so that all the time slots are in the format %I:%M (i.e., 09:30). Would the best way to implement this be within the submit() function since (I'm assuming) it is run everytime a required slot is filled?
Content of domain file (if used & relevant):

The submit function only gets called once all the slots are filled. But you could make the required changes to the slot values in that function and just return SlotSet events from that function

So my function would look something like this?:
    def submit(self, dispatcher, tracker, domain):
        avg_bedtime = tracker.get_slot("avg_bedtime")
        goal_bedtime = tracker.get_slot("goal_bedtime")

        avg_bedtime_object = parser.isoparse(avg_bedtime)
        goal_bedtime_object = parser.isoparse(goal_bedtime)

        avg_bedtime_object.strftime('%I:%M')
        goal_bedtime_object.strftime('%I:%M')

        return [SlotSet("avg_bedtime", value=avg_bedtime_object),
                SlotSet("goal_bedtime", value=goal_bedtime_object)]

Yes it would!


Investigate using GATs for View

Now that GATs are supported, in theory the Key type on View can be updated to use a generic lifetime rather than for<'k> Key<'k>.
To support this, Key will also need a new function and associated type that can promote Key<'k> to a static lifetime, to support flows that require owning the returned value.

If data needs to be returned, any key type that implements Key<'k> will inherently implement Key<'static>, and the data can be passed in as Ephemeral or Owned rather than Borrowed to force the Key type not to use the borrowed case. There doesn't need to be any sort of .into_owned method defined for this

Cow<'a, str> supports Key<'a>. If a view's key is Cow<'a, str> so that the view map() call can return a value that borrows from the passed document, the definition cannot also be defined as Cow<'static, str>.
This issue is to investigate how to support using the same associated type definition to support both flows -- allowing returning borrowed data as well as converting a value that potentially used borrowed data into a static lifetime when needed.

I'm stuck. I don't know if this is actually possible. I'd love for someone to help by modifying this example to make it work (playground link):
use std::borrow::Cow;

pub trait Key<'k> {
    fn as_bytes(&'k self) -> Cow<'k, [u8]>;
}

impl<'k> Key<'k> for Cow<'k, [u8]> {
    fn as_bytes(&'k self) -> Cow<'k, [u8]> {
        Cow::Borrowed(self)
    }
}

pub trait View {
    type Key<'doc>: Key<'doc>;

    fn map<'doc>(&self, doc: &'doc [u8]) -> Self::Key<'doc>;
}

pub trait SerializedView {
    fn map(&self, doc: &[u8]) -> Vec<u8>;
}

#[derive(Debug)]
struct MyView;

impl View for MyView {
    type Key<'doc> = Cow<'doc, [u8]>;

    fn map<'doc>(&self, doc: &'doc [u8]) -> Self::Key<'doc> {
        Cow::Borrowed(doc)
    }
}

impl<T> SerializedView for T
where
    T: View,
{
    fn map(&self, doc: &[u8]) -> Vec<u8> {
        let mapped = T::map(self, doc);
        let as_bytes = mapped.as_bytes();
        as_bytes.into_owned()
    }
}

fn main() {
    let view: Box<dyn SerializedView> = Box::new(MyView);
    let mapped = view.map(b"test");
    assert_eq!(mapped, b"test");
}

This is a very simplified version of what the view mapping code needs. Internally, the view mapper is invoked via type erasure, so the SerializedView must be boxable. It's the layer between that is currently causing lifetime errors because the GAT seems to limit the lifetime too far -- by making the lifetime be present on the GAT, it becomes possible for it to leak, and I'm not sure how to tell the compiler it can't -- except to not use GATs, and instead use the for<'k> variation instead. Unfortunately, that leaves us back at where the current limitations are.
Thank you in advance to anyone who tries to help solve this problem!

I think the problem is with the &k self for Cow<'k, [u8]> which ends up as &'k Cow<'k, [u8]> which asserts that the Cow lives exactly as long as it is borrowed
possible solutions:

Clone Cow<'k, [u8]> to Cow<'k, [u8]> in as_bytes

pub trait KeyEncoding<'k> {
    fn as_bytes(&self) -> Cow<'k, [u8]>;
}

pub trait Key<'k>: KeyEncoding<'k> {
    fn from_bytes(bytes: Cow<'k, [u8]>) -> Self;
}

impl<'k> KeyEncoding<'k> for Cow<'k, [u8]> {
    fn as_bytes(&self) -> Cow<'k, [u8]> {
        self.clone()
    }
}

impl<'k> Key<'k> for Cow<'k, [u8]> {
    fn from_bytes(bytes: Cow<'k, [u8]>) -> Self {
        bytes
    }
}

Create a borrow of self for as_bytes

pub trait KeyEncoding {
    fn as_bytes(&self) -> Cow<'_, [u8]>;
}

pub trait Key<'k>: KeyEncoding {
    fn from_bytes(bytes: Cow<'k, [u8]>) -> Self;
}

impl<'k> KeyEncoding for Cow<'k, [u8]> {
    fn as_bytes(&self) -> Cow<'_, [u8]> {
        Cow::Borrowed(self)
    }
}

impl<'k> Key<'k> for Cow<'k, [u8]> {
    fn from_bytes(bytes: Cow<'k, [u8]>) -> Self {
        bytes
    }
}


Yield the same order regardless of order in the file and database

Sorry in advance for formulating a possible bug in a form of PR.
I receive different results on chi_square for these 2 configurations (with postgres):
...
distribution_type: categorical
distribution_reference:
  weights:
  - 0.4
  - 0.6
  bins:
  - A
  - B

...
distribution_type: categorical
distribution_reference:
  weights:
  - 0.6
  - 0.4
  bins:
  - B
  - A

I would expect not to.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Adding source caller id to the answer call option

Description
The source caller Id, a phone number is added to the answer call option.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-communication-callautomation


Allow lowercase variable

In preferences of multispectra analysis we should allow renaming to lowercase

@lpatiny
this what I did, you can enter the lower case and upper case character, did you test the last version?

Indeed I must have tested an old version. Thanks !


Add colors for Night mode

Add suitable colors for night mode in the night colors.xml file and corresponding light mode colors in the original colors.xml and use the colors wherever required. Each color in the night colors.xml should have the same name as their light mode counterpart in the original colors.xml.
Like for example
In the original colors.xml
<color name="text_color">#000000</color>

Then subsequently in the night colors.xml
<color name="text_color">#FFFFFF</color>

PS
  This is just an example, all the colors of the app need to be added and not just this (probably don't even need to add this)

Hi, this sounds interesting could I be assigned?

Sure @Dinoosawruss , good luck ! 😄

Have you got any specific reference to what kind of dark mode colours you might like or are you happy for me to explore?

You are free to explore what colors would look the best, there aren't any specific requirements for now 😇

Hello, may I please be assigned to contribute to your project?
I'm a new developer.
Thanks for participating in Hacktoberfest and providing this opportunity :)


When Tokenization is disabled on long lines, such as when I am reading a minified file or, yes, the line is in fact very long for a reason, I am plagued with messages telling me that Tokenization is turned off, every time I move the cursor. The message gets in the way WHETHER hover is set to above or below. The message is long and plain annoying once you have seen it once.
I like hover messages, but I want to turn just this one off.
Also tokenisation is not spelled with a zed.

tokenisation is not spelled with a zed
It is for American English

Please fix it. It was once closable #56773

These kinds of popups are so annoying. Please at least offer "don't show this again" for this kind of message, since other hovers are quite helpful. We certainly don't need to be reminded every time the cursor moves, as the OP mentioned.


For 0.5.1

Updated the version to 0.5.1
Changed and updated the videos till Archive Projects under the Projects tab in the sidebar.

@jobjohnsonc In the import project video, please remove the note part.


close connection for redis

@alphmth - this looks good. One thought around this is if we should make them all async as it might be needed by other 3rd party libraries and drivers.
Also, it would be good to update the readme with this update on the Keyv package with async disconnect()

@jaredwray all drivers disconnect method returns promise already.
I will update readme


es6-shim has to be 0.35.0 for angular 2 update

I updated angular 2 to version beta 12 and they updated the es6-shim to version 0.35.0.
But the ng2-translate want to have version 0.33.3
npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants es6-shim@>= 0.33.3

What version of node / npm do you use? They fixed the peer dependencies in npm 3 (it was too rigid in npm 2).
I'm asking for ">= 0.33.3" which should be ok.

@ocombe oops..... npm version: 2.14.12

Try again with npm 3 then, it should fix your problem :)


Pause possible?

Hi!
First: Great Plugin for HA!
But I have one question: I have to call a doorbell which expects PAUSES in the order of digits i send to it with send_dtmf.
Is it already possible? I didn't find anything.

ok, I have splitted the command in different separate actions, works!


It should not take 70sec to run a empty circuit with 1 shot

What is the expected feature or enhancement?
Currently the service takes ~70sec in the running mode to execute an empty circuit with a single shot.  It should not take this long to do so.
Acceptance criteria
Going through the current "legacy" pipeline is about an order of magnitude faster

@nonhermitian Could you please provide the job id? cc: @renier

Here is one.  This one took ~40sec 'c8bmuce6859eus3g3ni0'

This one took over 90sec in "running" on a simulator in the test cloud: 'c8bnkjiss066rcv2ndhg'

Thanks! @renier Could you please help check?

This should be better @nonhermitian . Try and let me know.

This should be better now. Please re-open issue if not.


Cannot do shift+escape

In slack ⇧+ESC marks all chat as read, using the tap to escape plugin you cannot trigger this key command.

@tal: Thanks for reporting this issue. shift+escape isn't a keyboard combination that I personally use for anything, so I haven't run into this problem. However, it would be nice if it worked for people that do use it, so I've added the help-wanted label to this issue in case anyone wants to submit a pull request for it.

True

There is a weird spot when you do the caps pressed alone = escape; caps pressed with something else = control + something else setup. When you press caps + shift, do you do control + escape or shift+ escape?
I use shift+escape in jupyter notebooks with the VIM binding nbextension (you need it to escape out into command mode), so that is definitely useful in my case.
With a karabiner along with this setup, I solved this by commenting control-escape.lua in init.lua and using this complex modification instead.
For some reason control-escape.lua was also a bit laggy, but the karabiner setup was working pretty smooth. Not sure it that's because of the logic in that file, or hammerspoon itself. I have been trying to wrap my head around how do I debug hammerspoon in pdb python style while it tweak these files. It's been tough and slow debugging it in the console.


chore: bump to v0.3.0-dev0 and enrich package.json

Bump version to 0.3.0-dev0 (latest code from today's main branch) and enrich the package.json with useful package metadata to support discovery via NPM.

I did some work on this before: https://github.com/WebOfTrust/signify-ts/pull/260#issuecomment-2116965535
However, the current NPM_DEPLOY_SECRET  does not have sufficient rights to publish. I also have a simplified version of the workflow that allows you to do the same thing locally, but I never finished that work. If we can get a new working deploy secret, either for signify-ts or @weboftrust/signify package, I can pick it up again over the weekend.


Button as share on mobile and copy in desktop

Is there the option to make a share button use the share api when available, and copy to clipboard as fallback?  Sorry if missed it in the docs. Thanks!

Yes, create a share and a copy button and set the fallback option to true on the copy button. If the share API is unavailable the share button will not display and the copy button will.


absolute paths

Script complains about absolute paths. Reported by @gtheler .

Both absolute, relative, and home folder paths should work now @gtheler . Let me know and close if you have possibility to confirm :) .

It works. Apparently I do not have enough permissions to close issues.

Perfect, many thanks for the confirmation, closing.


Broken link for advanced vector search

In this table in this section. Also, in the TOC in Advanced vector search, a couple of links are broken (sections renamed or don't exist anymore)

Thanks for your feedback! ❤
Oh btw, we have a slack channel for warm-heart contributors like you, where we discuss code, PR, and future of Jina. Strongly recommend to join us

If you haven't joined our Slack, click here to join
👨💻 👩💻 ➡  https://jina-ai.slack.com/messages/contributors/

Thanks for your feedback! ❤
Oh btw, we have a slack channel for warm-heart contributors like you, where we discuss code, PR, and future of Jina. Strongly recommend to join us

If you haven't joined our Slack, click here to join
👨💻 👩💻 ➡  https://jina-ai.slack.com/messages/contributors/


Fix Motion-list CSV export and add new Version to export

closes #4050
Added the editorial final version for the CSV export
=> the PDF now has the two options "final Version" and "editorial final Version", This can be changed back to only one option (If that is wanted which version should be used?)
=> The CSV only has two options ("Original" and "editorial final" Version), are these the only two options wanted for the CSV export?

After talking with @emanuelschuetze:

The editorial final version was reverted

Two options are neough for CSV export

we found a bug, where the crMode was not reset correctly after switching from pdf to csv


Update docs for more robust AWS deploy command

If you omit the AWS_TOKEN you get an error from pachctl reporting that it has 6 args but expects 7
Instead we should wrap the AWS ID, TOKEN, and KEY params in double quotes. This is probably a good idea as well since the TOKEN can have some funny characters I believe.

I think a better idea would be to just update pachctl so it doesn't take a token by default, that would help coax people toward the better deployment path. We can add it back in as a flag. Quotes are fine if the funny characters actually cause problems, my experience has been that quotes aren't really necessary unless I want to pass an empty token.

This is fixed, right @sjezewski?

No ... we still list an empty token " " in the pachctl deploy amazon ... command:
http://docs.pachyderm.io/en/latest/deployment/amazon_web_services.html

This is fixed. We use named args now.


Hook up evaluation scripts to database.

Evaluation should re-run everytime annoted misconceptions from UCI health team are updated.

I think this is a duplicate of #27. Let me close this, and leave your comment there.


.NET Core 1.0.4 and 1.1.1

Thanks for your interest in .NET Core.
You can read about .NET Core 1.0.4 and 1.1.1 in the .NET blog announcement.
Please report any issues you find with .NET Core 1.0.4 and 1.1.1 here, either responding to this issue or creating a new issue.
Please include the following information plus any other info that you think is relevant:
OS version
Repro steps
Repro code (if you can share it / is relevant)
Error messages
Whether this worked before
Method of installing .NET Core
Please note that this repo (dotnet/core) is not for filing product issues. Here are some repos where you can file an issue:
dotnet/cli - for CLI tools and questions
dotnet/corefx - for API issues and questions
dotnet/coreclr - for runtime issues
nuget/home - for NuGet questions and issues

When running the install steps from https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.1-download.md:
sudo sh -c 'echo "deb [arch=amd64] https://apt-mo.trafficmanager.net/repos/dotnet-release/ xenial main" > /etc/apt/sources.list.d/dotnetdev.list'
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 417A0893
sudo apt-get update
sudo apt-get install dotnet-sdk-ubuntu-x<IP_ADDRESS>

I get the following error:
portaljacker@vps:~$ sudo apt-get install dotnet-sdk-ubuntu-x<IP_ADDRESS>
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-sdk-ubuntu-x<IP_ADDRESS>
E: Couldn't find any package by glob 'dotnet-sdk-ubuntu-x<IP_ADDRESS>'
E: Couldn't find any package by regex 'dotnet-sdk-ubuntu-x<IP_ADDRESS>'

Doing dotnet -v returns version 1.0.0-rc4-004771.

Seems that it should be sudo apt-get install dotnet-dev-1.0.1
I'll submit a pull request.

@leecow @kendrahavens is possible to add the f# info from wiki to blog post?
https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-1.0.1
that add some important info and workarounds (like how fix intellisense 😄 ).

when i open dotnet-1.1.1-sdk-win-x64.exe, it show ".Net Core SDK 1.0.1".
But the installation process I also saw some 1.1.1 information.
I uninstalled all the old NetCore before i started installing 1.1.1

On Ubuntu 16.10, with dotnet SDK 1.1.1 when doing (lang is really irrelevant):
$ dotnet new console -lang f#
I get:
Object reference not set to an instance of an object.
   at Microsoft.TemplateEngine.Cli.New3Command.ParseTemplateArgs(ITemplateInfo templateInfo)
   at Microsoft.TemplateEngine.Cli.New3Command.<EnterSingularTemplateManipulationFlowAsync>d__64.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.TemplateEngine.Cli.New3Command.<EnterTemplateManipulationFlowAsync>d__65.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.TemplateEngine.Cli.New3Command.<ExecuteAsync>d__66.MoveNext()

CC @mlorbetske

@kontomondo could you zip up the directory at ~/.templateengine and mail it to me at<EMAIL_ADDRESS>please? After zipping it up and moving it out of that directory, please try running dotnet new --debug:reinit, after that runs things should return to working normally

@mlorbetske I see what the problem is now -- it got initialised in one directory and then I moved it to another, but the template engine settings still has the old "mount points", so it essentially wasn't able to find the files. It should probably check whether dotnet's path has changed and if so, re-initialise the template engine data ?

@enricosada After creating a sample F# application, dotnet restore works, but dotnet build fails with
/home/user/.nuget/packages/fsharp.net.sdk/1.0.1/build/FSharp.NET.Core.Sdk.targets(170,9): error MSB6006: "dotnet" exited with code 131

@kontomondo we agree, we're actively working on handling these sorts of scenarios

@kontomondo abouut f#, can you open an issue in https://github.com/dotnet/netcorecli-fsc/issues ?
Can you please add redo build with a bit more verbose log? it;s dotnet build -v n ? (just for compiler args, or -v d for more)

@kontomondo no need to add issue, probably is the same as https://github.com/dotnet/netcorecli-fsc/issues/91 . check that issue for status updates

@enricosada The F# link was added to the post earlier. :)

@kendrahavens i cannot find it in that blog post now, but thx anyway.
I think will be really good to have that wiki link in the blog post because is about .net core 1.0 tools (that works ok for f#, VS instead not, the wiki give more info exactly about that).
but np anyway

@enricosada Hmm, I can't find it either.
@richlander Where did you add https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-1.0.1 ?

@enricosada - I added the fsharp wiki link to release notes for 1.0.4 and 1.1.1

When can we expect 1.1.1 to be pushed to the repositories? I upgraded my project to 1.1.1 but Ubuntu 10.4 is still on 1.1.0.

@yesman85 - I've confirmed that the 1.0.1 SDK and 1.1.1 Runtime are on the feed using for Ubuntu 16.04 and 16.10. You should be able to sudo apt-get update  and sudo apt-get install dotnet-dev-1.0.1. I have seen dependency errors in some situations. If you see something like that, apt-get should recommend running sudo apt-get -f install (with no packages referenced) to clean things up.

@leecow very odd, I tried multiple times and even with a clean install but it stays on 1.1.1.
When I do an install:
user@ubuntu:~$ sudo apt-get install dotnet-dev-1.0.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  dotnet-host dotnet-hostfxr-1.0.1 dotnet-hostfxr-1.1.0 dotnet-sharedframework-microsoft.netcore.app-1.0.4 dotnet-sharedframework-microsoft.netcore.app-1.1.1
The following NEW packages will be installed:
  dotnet-dev-1.0.1 dotnet-host dotnet-hostfxr-1.0.1 dotnet-hostfxr-1.1.0 dotnet-sharedframework-microsoft.netcore.app-1.0.4
  dotnet-sharedframework-microsoft.netcore.app-1.1.1
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/97.1 MB of archives.
After this operation, 280 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Selecting previously unselected package dotnet-host.
(Reading database ... 29386 files and directories currently installed.)
Preparing to unpack .../dotnet-host_1.1.0-preview1-001100-00-1_amd64.deb ...
Unpacking dotnet-host (1.1.0-preview1-001100-00-1) ...
Selecting previously unselected package dotnet-hostfxr-1.0.1.
Preparing to unpack .../dotnet-hostfxr-1.0.1_1.0.1-1_amd64.deb ...
Unpacking dotnet-hostfxr-1.0.1 (1.0.1-1) ...
Selecting previously unselected package dotnet-sharedframework-microsoft.netcore.app-1.0.4.
Preparing to unpack .../dotnet-sharedframework-microsoft.netcore.app-1.0.4_1.0.4-1_amd64.deb ...
Unpacking dotnet-sharedframework-microsoft.netcore.app-1.0.4 (1.0.4-1) ...
Selecting previously unselected package dotnet-hostfxr-1.1.0.
Preparing to unpack .../dotnet-hostfxr-1.1.0_1.1.0-1_amd64.deb ...
Unpacking dotnet-hostfxr-1.1.0 (1.1.0-1) ...
Selecting previously unselected package dotnet-sharedframework-microsoft.netcore.app-1.1.1.
Preparing to unpack .../dotnet-sharedframework-microsoft.netcore.app-1.1.1_1.1.1-1_amd64.deb ...
Unpacking dotnet-sharedframework-microsoft.netcore.app-1.1.1 (1.1.1-1) ...
Selecting previously unselected package dotnet-dev-1.0.1.
Preparing to unpack .../dotnet-dev-1.0.1_1.0.1-1_amd64.deb ...
Unpacking dotnet-dev-1.0.1 (1.0.1-1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up dotnet-host (1.1.0-preview1-001100-00-1) ...
Setting up dotnet-hostfxr-1.0.1 (1.0.1-1) ...
Setting up dotnet-sharedframework-microsoft.netcore.app-1.0.4 (1.0.4-1) ...
Setting up dotnet-hostfxr-1.1.0 (1.1.0-1) ...
Setting up dotnet-sharedframework-microsoft.netcore.app-1.1.1 (1.1.1-1) ...
Setting up dotnet-dev-1.0.1 (1.0.1-1) ...
roger@ubuntu:~$ dotnet

Microsoft .NET Core Shared Framework Host

  Version  : 1.1.0
  Build    : 928f77c4bc3f49d892459992fb6e1d5542cb5e86

Usage: dotnet [common-options] [[options] path-to-application]

Common Options:
  --help                           Display .NET Core Shared Framework Host help.
  --version                        Display .NET Core Shared Framework Host version.

Options:
  --fx-version <version>           Version of the installed Shared Framework to use to run the application.
  --additionalprobingpath <path>   Path containing probing policy and assemblies to probe for.

Path to Application:
  The path to a .NET Core managed application, dll or exe file to execute.

If you are debugging the Shared Framework Host, set 'COREHOST_TRACE' to '1' in your environment.

To get started on developing applications for .NET Core, install the SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

It looks like it installed "dotnet-sharedframework-microsoft.netcore.app-1.1.1", but is it maybe the tooling that is reporting the wrong version?

First off, everything looks correct so you're in good shape :-). Second, I apologize for our versioning and the way it's reported is unclear and confusing. When you do an install there are three components which can version independently: host, runtime/shared framework and the SDK. All of these can live side-by-side. Trying to organize and tell a coherent story with all of these versions floating around is proving very difficult.
Your apt-get install output indicates the packages included in the 1.0.1 SDK are set up.
Setting up dotnet-host (1.1.0-preview1-001100-00-1) ...
Setting up dotnet-hostfxr-1.0.1 (1.0.1-1) ...
Setting up dotnet-sharedframework-microsoft.netcore.app-1.0.4 (1.0.4-1) ...
Setting up dotnet-hostfxr-1.1.0 (1.1.0-1) ...
Setting up dotnet-sharedframework-microsoft.netcore.app-1.1.1 (1.1.1-1) ...
Setting up dotnet-dev-1.0.1 (1.0.1-1) ...

dotnet will return the Host version (1.1.0) where dotnet --version returns the SDK version. If you poke around the directories under /usr/share/dotnet, you'll probably see a number of installed versions. There is policy in the various components to automatically choose the highest patch version within a minor version "family". So if you have 1.0.1, 1.0.3, 1.0.4 under /shared/Microsoft.NETCore.App, 1.0.4 will be used unless you specifically configure a project to use something different. The same rules apply to the other components.
Hope that brief explanation is helpful.

We have projects handling XSD, so we previously only use .net core 1.0 full framework, and wait Q3 .net core 2.0. So in this case, since full version can reference .net framework 4.6.1, so we can have part of projects using .net core 1.0, part of 4.6.1, they work well. But after I upgraded to visual studio 2017, it's said the projects are all not compatible with .netcore1.1, does this mean that .net core 1.1 doesn't support full framework?

Hi @leecow ,
I am trying to install .net core on ubuntu 14.04 LTS. I have installed it fresh and using it first time. I followed steps from here. The .net core version is dotnet-dev-1.0.4. I am getting this log when i run sudo apt-get install dotnet-dev-1.0.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-dev-1.0.4
E: Couldn't find any package by regex 'dotnet-dev-1.0.4'
Here are the logs
user@user-VirtualBox:~$ sudo apt-get update
[sudo] password for user:
Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB]
Ign http://in.archive.ubuntu.com trusty InRelease
Ign http://extras.ubuntu.com trusty InRelease
Get:2 http://extras.ubuntu.com trusty Release.gpg [72 B]
Get:3 http://extras.ubuntu.com trusty Release [11.9 kB]
Get:4 http://extras.ubuntu.com trusty/main Sources [14 B]
Get:5 http://extras.ubuntu.com trusty/main i386 Packages [14 B]
Get:6 http://in.archive.ubuntu.com trusty-updates InRelease [65.9 kB]
Get:7 http://security.ubuntu.com trusty-security/main Sources [130 kB]
Get:8 http://security.ubuntu.com trusty-security/restricted Sources [4,941 B]
Get:9 http://in.archive.ubuntu.com trusty-backports InRelease [65.9 kB]
Get:10 http://security.ubuntu.com trusty-security/universe Sources [52.5 kB]
Get:11 http://security.ubuntu.com trusty-security/multiverse Sources [3,206 B]
Ign http://extras.ubuntu.com trusty/main Translation-en_IN
Ign http://extras.ubuntu.com trusty/main Translation-en
Get:12 http://in.archive.ubuntu.com trusty Release.gpg [72 B]
Get:13 http://in.archive.ubuntu.com trusty-updates/main Sources [398 kB]
Get:14 http://in.archive.ubuntu.com trusty-updates/restricted Sources [6,327 B]
Get:15 http://in.archive.ubuntu.com trusty-updates/universe Sources [178 kB]
Get:16 http://in.archive.ubuntu.com trusty-updates/multiverse Sources [7,767 B]
Get:17 http://in.archive.ubuntu.com trusty-updates/main i386 Packages [937 kB]
Get:18 http://in.archive.ubuntu.com trusty-updates/restricted i386 Packages [16.9 kB]
Get:19 http://in.archive.ubuntu.com trusty-updates/universe i386 Packages [406 kB]
Get:20 http://in.archive.ubuntu.com trusty-updates/multiverse i386 Packages [14.6 kB]
Get:21 http://in.archive.ubuntu.com trusty-updates/main Translation-en [484 kB]
Get:22 http://in.archive.ubuntu.com trusty-updates/multiverse Translation-en [7,430 B]
Get:23 http://in.archive.ubuntu.com trusty-updates/restricted Translation-en [3,975 B]
Get:24 http://in.archive.ubuntu.com trusty-updates/universe Translation-en [215 kB]
Get:25 http://in.archive.ubuntu.com trusty Release [11.9 kB]
Get:26 http://in.archive.ubuntu.com trusty-backports/main Sources [9,712 B]
Get:27 http://in.archive.ubuntu.com trusty-backports/restricted Sources [28 B]
Get:28 http://in.archive.ubuntu.com trusty-backports/universe Sources [35.3 kB]
Get:29 http://in.archive.ubuntu.com trusty-backports/multiverse Sources [1,898 B]
Get:30 http://in.archive.ubuntu.com trusty-backports/main i386 Packages [13.3 kB]
Get:31 http://in.archive.ubuntu.com trusty-backports/restricted i386 Packages [28 B]
Get:32 http://in.archive.ubuntu.com trusty-backports/universe i386 Packages [43.2 kB]
Get:33 http://in.archive.ubuntu.com trusty-backports/multiverse i386 Packages [1,552 B]
Get:34 http://in.archive.ubuntu.com trusty-backports/main Translation-en [7,503 B]
Get:35 http://in.archive.ubuntu.com trusty-backports/multiverse Translation-en [1,215 B]
Get:36 http://in.archive.ubuntu.com trusty-backports/restricted Translation-en [28 B]
Get:37 http://in.archive.ubuntu.com trusty-backports/universe Translation-en [36.8 kB]
Get:38 http://in.archive.ubuntu.com trusty/main Sources [14 B]
Get:39 http://security.ubuntu.com trusty-security/main i386 Packages [570 kB]
Get:40 http://security.ubuntu.com trusty-security/main i386 Packages [570 kB]
Get:41 http://security.ubuntu.com trusty-security/restricted i386 Packages [13.8 kB]
Get:42 http://security.ubuntu.com trusty-security/universe i386 Packages [157 kB]
Get:43 http://security.ubuntu.com trusty-security/multiverse i386 Packages [4,289 B]
Get:44 http://security.ubuntu.com trusty-security/main Translation-en [334 kB]
Get:45 http://security.ubuntu.com trusty-security/multiverse Translation-en [2,201 B]
Get:46 http://security.ubuntu.com trusty-security/restricted Translation-en [3,505 B]
Get:47 http://security.ubuntu.com trusty-security/universe Translation-en [91.4 kB]
Fetched 4,414 kB in 3min 44s (19.6 kB/s)
W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/trusty/Release  Unable to find expected entry 'restricted/source/Sources' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download.  They have been ignored, or old ones used instead.
user@user-VirtualBox:~$ sudo apt-get install dotnet-dev-1.0.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-dev-1.0.4
E: Couldn't find any package by regex 'dotnet-dev-1.0.4'
user@user-VirtualBox:~$ ^C
user@user-VirtualBox:~$ dotnet help
dotnet: command not found
user@user-VirtualBox:~$
I am using ubuntu on VirtualBox
Can you please help me? what am i missing?

Hi @nikamsshekhar, many of those errors have to do with reaching the ubuntu feeds and not just the dotnet feed so something is definitely amiss. Can you confirm the contents of /etc/apt/sources.list.d/dotnetdev.list?

A couple of issues with the RedHat installation procedure:
OS version: Red Hat Enterprise Linux Server release 7.3
Repro steps: Azure VM / Redhat 7.3 and install .NET Core:
sudo subscription-manager repos --enable=rhel-7-server-dotnet-rpms
sudo yum install scl-utils
sudo yum install rh-dotnetcore11
sudo scl enable rh-dotnetcore11 bash

Error messages
sudo subscription-manager repos --enable=rhel-7-server-dotnet-rpms
Error: 'rhel-7-server-dotnet-rpms' does not match a valid repository ID. Use "subscription-manager repos --list" to see valid repositories.

and then running "sudo scl enable rh-dotnetcore11 bash" takes me to root user (?), but the following command still cannot find the dotnet: sudo which dotnet
If I run the 'scl' command without sudo, then the current user path recognizes where the dotnet is installed (/opt/rh/rh-dotnetcore11/root/usr/bin/dotnet), however this doesn't seem to be persistent, as after a re-login, 'which dotnet' returns the following:
which dotnet
/usr/bin/which: no dotnet in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/seguler/.local/bin:/home/seguler/bin)

I followed instruction : https://www.microsoft.com/net/core#linuxredhat to install .Net Core. Seems I need to enable dotnet with "scl enable rh-dotnetcore11 bash" whenever I started a new bash session. Is this behavior intended?
I know I can put the command in .bashrc. I just think it'd be much convenient if the installation can enable dotnet automatically.

How do I install .NET Core 1.1 (current) on my Ubuntu 16.04? I followed https://www.microsoft.com/net/core#linuxubuntu but it had instructions for 1.0.4 LTS.
To install .NET Core 1.1 on Ubuntu or Linux Mint, simply use apt-get. isn't too helpful.

@richlander @kendrahavens are the instructions correct?
If they are, they should explain explicitly why "sudo apt-get install dotnet-dev-1.0.4" installs 1.0.5 or 1.1.2. It is extremelly non-intuitive and it looks like a bug. Maybe part of our not-so-ideal versioning story?

Hey @EmmaZhu

I followed instruction : https://www.microsoft.com/net/core#linuxredhat to install .Net Core. Seems I need to enable dotnet with "scl enable rh-dotnetcore11 bash" whenever I started a new bash session. Is this behavior intended?

Yes. There's a few reasons for use-via-scl. The most important one is that .NET Core requires certain libraries that are just too old on base RHEL. In particular, some networking API requires features that are not a part of libcurl on base RHEL. So we build a modified version of libcurl that only gets activated via SCL. This lets all programs on the system continue working without being aware of the modified libcurl but .NET Core can see it and make use of more advanced features that part of the networking API in .NET Core needs.
Another reason is that without SCL, we would be tied to RHEL's release cycle and not be able to get updates out within days or weeks of upstream release.

I know I can put the command in .bashrc. I just think it'd be much convenient if the installation can enable dotnet automatically.

Please feel free to file bugs at bugzilla.redhat.com. User pains help us direct effort and weigh options. It's kind of hard for us Red Hat folks to monitor all github issues :)

The version of the tooling (1.0.4) and the versions of runtime(s) that it carries (1.1.2 and 1.0.5 in this case) are not tied together, as they have a different release cadence. For instance, we don't want to rev the runtime because of a tooling bug.

@livarcocc in that case we should mention it in the docs, something like "don't worry about not matching numbers". I am confused - I thought it is a bug, and I am on the team :(

@karelz I tried documenting it once: https://stackoverflow.com/documentation/.net-core/9592/components-and-versioning-in-net-core
Is this something that might be useful as part of .NET Core 1.x docs?

@omajid @karelz Thanks for the responses. It is clear to me now, but it isn't super obvious that the latest SDK 1.0.4 includes both LTS and current runtimes.
Also, one more thing on the instructions page:
Before you start, please remove any previous versions of .NET Core from your system by using this script. --> So, is 'side by side' not possible on Ubuntu? like windows?

@omajid it is not about docs. IMO it should be crystal clear from the main docs -- installation docs in this case. Additional documentation is just too late. The confusion has been already seeded.
@stanuku see https://github.com/dotnet/cli/issues/3773 for discussion about dotnet --version.

@karelz: Thanks
The discussion #3773, basically had a disappointing end in spite of many valid concerns and suggestions. I've been a .NET dev for a good decade and consider myself a decent one at it. But, never before I'm subjected to such confusion and uncertainty. I'm having a hard time wrapping my head around this stuff. I'm not sure if I'm prepared to answer questions that would follow when I propose the adoption of .NET Core in new projects at my work. And also when I try to guide and mentor mid and junior level developers on this stuff. Let alone the issues I might face communicating to the server and IT teams about the bits that I would need them to install on build and hosting servers.
How easy life can be when you just have to say we need .NET 4.6.2 or 4.5.1 etc, compared to this versioning nightmare. In my experience, an average developer (not so curious kind) would hardly care about the internals/SDK/CLI, they would expect the Visual Studio or other IDE to do the heavy lifting and abstract the complexity, so they can focus on solving the business problems and delivering their tasks. There is not much business value addition in spending tons of hours understanding these internals, which seem to be so fluid currently.
I hope common sense would prevail. One of the perils of the "open source" perhaps (Not that I'm against it, actually I love it when it is managed well and at a smaller scale. I don't expect everyone here to agree with me) however, exposing all the moving parts to a developer who could care less about the CLI/SDK etc etc and just wants to know a single one version number that can be used to pick up in the Target framework drop down in Visual Studio for example and be done with it and move on to more important business problems.
If you managed to read till here, thanks for your patience and understanding.

How easy life can be when you just have to say we need .NET 4.6.2 or 4.5.1 etc, compared to this versioning nightmare.

With .Net Framework, you use Visual Studio 2017, MSBuild 15 and C# 7 to develop and build your applications and .Net Framework 4.7 to run them. With .Net Core, you use Visual Studio 2017, MSBuild 15, C# 7 and .Net Core SDK 1.0 to develop and build your applications and .Net Core 1.1 to run them. It is more complicated and the naming can be confusing (since it's easy to overlook the "SDK" part), but I'm not sure it's as bad as you make it sound.

they would expect the Visual Studio or other IDE to do the heavy lifting and abstract the complexity, so they can focus on solving the business problems and delivering their tasks

Do you have any specific suggestions for how the tooling can be improved?

There is not much business value addition in spending tons of hours understanding these internals, which seem to be so fluid currently.

There were huge changes in the past (dnx → dotnet, project.json → csproj), but as far as I know, the only somewhat big change that's coming is .Net Standard 2.0. So I wouldn't exactly call it "fluid".
And if you really need "tons of hours" to understand that .Net Core and .Net Core SDK are distinct and versioned separately, then I think something is very wrong. (Maybe it's the documentation?)

@svick Thanks for you response (Just a disclaimer: I'm a very loyal .NET developer most of my professional career and made a living out due to it.)
Here are my thoughts/concerns:

Microsoft .NET development story has a long and solid history with Visual Studio + .NET full framework (albeit restricted to Windows). All the Businesses (LOB apps, SAAS, Product based) would be very anxious to move to .NET Core yet. Unless there is a great benefit. With all the churn happening since the past year and half or so, it delays that adoption even further. You can count me in that boat. I would have to cite the example of Entity Framework here. Are there any more improvements or enhancements planned after EF 6.3? if EF core is the future then .NET Core is the only way to go. I know there is a promise of .NET Standard 2.0. I really hope it lives up to the hype and expectations. I know, there is no point in dwelling on what has happened in the past, however, in the daily life of Architects/Developers who were early adopters, the reality is that they have been feeling misguided and in jeopardy of losing traction at work and with the management. The selling point of "cross-platform" is mostly for startups/midsize and green field development, whom historically not have been MS's focus or customer base. Those shops/organizations would still continue to be targeting full framework unless there is a simple and rock solid story for .NET Core migration which seems to be still long ways away. Is there an incentive or compelling reason for them to migrate now or in next one year?

I'm wondering how important/crucial it is for a developer to know what tooling /SDK/CLI/SharedHost/Runtime versions. Shouldn't it be left to their IDE to figure out based on one target version that he or she picks from the list? I'm referring to the traditional VS Architects/Developers, they never really needed to know anything other than the .NET framework version and a Managed language of their choice, for the most part.
I agree that VS 2017 has shown promise and hope, however we already have applications in production based on the project.json (from VS2015) . To upgrade all the servers with relevant bits and migrate to MSBuild/.csproj again takes a lot of convincing and confidence building measures.

Some suggestions/comments:

In VS 2017 IDE, I would ideally prefer the .NET Core listed in the target framework drop down instead of under templates. For a traditional VS developer, it is hard to relate to.

The documentation is getting better, not perfect though. Please refer to some of the issues that I've reported. https://github.com/dotnet/core/issues/656, and my comments in this post.

NOTE: I'm super excited about the .NET Core and ASP.NET Core but it is so far just limited to my personal projects and a couple simple cookie cutter web applications at work. I don't feel too confident yet to start building a case for a wider adoption at my work place at a bigger scale especially, training the devs. Given the management has bigger problems to solve and other priority and don't really see a pressing need to migrate. I'll have to sit out and watch .NET Standard 2.0 unfold. Sometimes I wonder who is MS targeting with the .NET Core movement.

@stanuku

With all the churn happening since the past year and half or so, it delays that adoption even further.

.Net Core SDK 1.0 was released this February. I don't think it's fair to complain about churn before that.

Are there any more improvements or enhancements planned after EF 6.3? If EF core is the future then .NET Core is the only way to go. I know there is a promise of .NET Standard 2.0. I really hope it lives up to the hype and expectations.

I don't know anything about future plans for EF or EF Core. But even if EF Core is the future, then you can still stay on .Net Framework, since EF Core is a .Net Standard library and .Net Framework does support .Net Standard. (And that's not something that's new with .Net Standard 2.0.)

Is there an incentive or compelling reason for them to migrate now or in next one year?

If any of the unique features of .Net Core (not just it being cross-platform, but also e.g. different deployment strategies) do not appeal enough to you, then you should not migrate, possibly ever. Even the documentation recommends not to migrate existing .Net Framework applications.

Shouldn't it be left to their IDE to figure out based on one target version that he or she picks from the list?

Isn't it like that already? If you install .Net Core tooling for VS from the VS installer, you don't have to care about any .Net Core SDK version, no?
The VS-specific section of the .Net Core getting started page also does not mention any SDK versions.

.Net Core SDK 1.0 was released this February. I don't think it's fair to complain about churn before that.

I think it is, especially given .NET Core 1.0 was released last year. I - and many others - had no idea SDK and non-SDK were different components, were being developed independently and were versioned separately. And I was talking to folks working on .NET Core every week...

@svick: Again I'm not debating on the decisions, but giving an outside perspective. This perspective is from people like me who would ultimately take the result of the efforts of people like you within and outside MS) to a bigger picture, people who would utilize your product to build bigger things, solver real problems and generate revenue and act as ambassadors of the .NET brand.
My main point is, did MS have .NET Standard 2.0 in mind all the way? if so, then the pain and rough ride for the early adopter could have been mitigated with proper and timely communication and guidance. If not, and if .NET Standard 2.0 just evolved based on the feedback, then it makes me feel a bit uncertain of what else could change in the future (for a brief period just before the BUILD 2017, there was confusion on .NET Core 2.0 not supporting .NET Standard 2.0. The big guns at MS had to do the damage control later and clear the confusion. I suspect they must have debated about it internally and retracted based on the feedback)

.Net Core SDK 1.0 was released this February. I don't think it's fair to complain about churn before that.

Not just the SDK I was referring to the other components of the .NET Core.  Same sentiment as @omajid has expressed.

Isn't it like that already? If you install .Net Core tooling for VS from the VS installer, you don't have to care about any .Net Core SDK version, no?
The VS-specific section of the .Net Core getting started page also does not mention any SDK versions.

Unless I'm missing something, the VS 2017 still doesn't show what versions I'm getting or targeting from the project creating dialogs. Although, I don't mind editing the project files and changing the TFMs and other details, not everyone would prefer to do that.
VS2017 is promising but, I'm suspecting we have good couple of iterations of .NET Core/Standard i.e. 2.*, 3.0 and VS 2018, 2019. Before, we get there where we want to be. I can't wait for it. But will watch cautiously. I had bore the brunt of early adaption in 2016 already.
Thanks

did MS have .NET Standard 2.0 in mind all the way?

As far as I know, they didn't. It came from the acquisition of Xamarin and their realization that the best way to support .Net Framework, .Net Core and Xamarin/Mono all at the same time was to expand .Net Standard.

for a brief period just before the BUILD 2017, there was confusion on .NET Core 2.0 not supporting .NET Standard 2.0. The big guns at MS had to do the damage control later and clear the confusion. I suspect they must have debated about it internally and retracted based on the feedback

To clarify, the confusion was about ASP.NET Core 2.0 not supporting .Net Standard 2.0, and thus also not being able to run on .Net Framework.

VS 2017 still doesn't show what versions I'm getting or targeting from the project creating dialogs. Although, I don't mind editing the project files and changing the TFMs and other details, not everyone would prefer to do that.

Yes, it doesn't. But you can change it from the project properties page, you don't have to edit the project file.

I can't wait for it. But will watch cautiously. I had bore the brunt of early adaption in 2016 already.

I'd say that in 2016, you were a very early adopter: i.e. not everything was even expected to work. In 2017, you're just an early adopter: everything should work, but the experience might not be quite polished yet. So waiting some more before switching to .Net Core sounds like a reasonable business decision to me. (Even if part of me wishes everyone would always work from master, not even wait for release, at least for the projects I'm currently most passionate about. 🙂)

@svick:

To clarify, the confusion was about ASP.NET Core 2.0 not supporting .Net Standard 2.0, and thus also not being able to run on .Net Framework.

You're right, my concern still applies though.

Yes, it doesn't. But you can change it from the project properties page, you don't have to edit the project file.

Yes, you still wouldn't know what the runtime version (major.minor.patch) is. Shouldn't we need to know?

Closing. .NET Core 1.0.5 and 1.1.2 have now shipped.
See #622


Change in User Interface

Looking forward for reporting a security issue:
Please report security issues by sending an email to<EMAIL_ADDRESS>instead of raising a GitHub issue.
Describe the bug
A clear and concise description of what the bug is.
The user interface seems to be different, basically the front end of the website. I also can't sign in to my account. :( When I tried to inspect the website, it shows this:
////
Failed to load resource: the server responded with a status of 500 ()
api.rollbar.com/api/1/item/:1 Failed to load resource: the server responded with a status of 429 ()
///
Hope this helps. The website had an alert that they already notified the organization itself.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Thanks for reporting, please checkout our community forum for details

The last time I checked, there is still a bug on the website.
It says this -->
"Something is not quite right. A report has been generated and the freeCodeCamp.org team have been notified."
Thanks for letting me know. I'll search up some threads to see if other people are also experiencing the bug.

We are working very hard to fix the issues. Thanks for your patience

Thank you so much for sharing this information!


Repair of towers and gates AI

I know already written repeatedly, but I would like to raise this question again.

Will be fixed in the next patch.


Train a more robust model

Maybe we need to add some augmentation to the training data or include more images with backgrounds instead of the images we have now with only the fruit/veggie cut out

We trained a new and much larger model after finding out through weights and biases that the models should be a lot larger. We now use convnext_large from TIMM pytorch.


Start typing transport.py based on transport.ts

This is just the beginning of an exploration into python3 typing for
the transport "interface". I found this PEP interesting:
https://www.python.org/dev/peps/pep-3119/#abcs-vs-interfaces
not sure if abc is really what we want but I'd rather not use
zope.interface (I think we should try to keep dependancies small).
I've added a "configure" method to the transport interface as a low cost
implementation of configuring dependancy injection.
TODO:

determine if we use dataclasses versus attrs
flesh out transport.py interface/types
actually implement and test requests_transport.py

This is still a work in progress. I spent time talking with @josephaxisa and kalen and the proposal is to continue using typing where it makes sense (e.g. for pluggable transport for sure, but might not be necessary in other parts of the python rtl).


Fix/837 client search improvements

Description
Closes #837
Getting help from Derek for the timeout issue
Changelog
New

None

Changed

Sorting algo and name format for client search table

Removed

None

How was this tested?

[ ] 🧠 Not needed
[ ] 👀 Eyeball
[ ] 🤖 Added tests

What gif/image best describes this PR or how it makes you feel?

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Frontend
Backend
Oracle-API
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Frontend
Backend
Oracle-API
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

opened for too long, just gonna merge and close


Number is too long error: fixed by using big integer in Jackson parser

@wanglingsong sure, added

@wanglingsong Hello, I've faced same problems with "Number is too long for Long type", could you submit pull request ?


Fix issue accessing non-existent tracker

fixes #1210
What was wrong?
The BaseExchange.run_exchange context manager was written to set and then remove the tracker attribute.  This wasn't necessary.
How was it fixed?
Changed to put the tracker in place during class initialization and no longer remove it in run_exchange.
Cute Animal Picture

Since there was a release yesterday, this should probably include a bugfix release note.

The user never sees the stacktrace, just a warning.  I think this is minor enough to not include it given your comment about big release notes.  Thoughts?

Yeah, I think that's fine, if it wasn't having a meaningful impact on performance. :+1:

I've been running it for a few hours and I haven't seen it show up with any regularity.  I believe it only happens when we're already disconnecting from a peer.


GetResourcesByResourceType

This script gets the resources that are using a given resource type.

Script GetResourcesByResourceType.groovy has been committed to the repository.


Revert "change color"

Thanks for submitting code to Blockly!  Please fill out the following as part of your pull request so we can review your code more easily.
The basics

[ ] I branched from develop
[ ] My pull request is against develop
[ ] My code follows the style guide

The details
Resolves
What Github issue does this resolve (please include link)?
Proposed Changes
Describe what this Pull Request does.  Include screenshots if applicable.
Reason for Changes
Explain why these changes should be made.  Include screenshots if applicable.
Test Coverage
Please show how you have added tests to cover your changes, or tell us how you tested it and on which platforms.  If it's plaform-agnostic you can delete these checkboxes.
Tested on:
Remove this hint: these checkboxes can be checked like this: [x]

[ ] Desktop:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Opera
[ ] IE 10+
[ ] IE 11
[ ] EDGE

[ ] Smartphone/Tablet/Chromebook (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional Information
Anything else we should know?

reject