Allow type predicates as return types only

It does this in the parser instead of piecemeal in the checker. This means that the checker has some unused error checking code, so I took the opportunity to move the type predicate checking code into checkTypePredicate instead of checkSignatureDeclaration where it was previously.
Fixed #5903 and #5731. Obsoletes PRs #5936 and #5977.
@ahejlsberg and @weswigham, can you take a look?

@ahejlsberg does this look good now?

You might want to wait on @weswigham's work as a heads up.

@DanielRosenwasser I merged to get Wesley's changes. The parser may need some work to forbid this is X but I'll do that in a separate change I think.

I'd like to get this in for 1.8. @ahejlsberg, @weswigham, can you take another look?

@ahejlsberg can you take a look so I can merge this for 1.8?

:+1: With my minor suggested change.


adding shortcut icon (favicon)

we need an icon for CANBeWell when we add it to the home screen

these are sample for iPhone and android.
But in the android, there was written one time "W" in the icon, but its now there is a CanBeWell image inside the icon, and also its written "React App"

It is fixed on the test website for now.

For testers, this is how you need to test it: (This test is only applicable for phones and we need at least 2 devices: iPhone and Android)
1- Go to the website that you want to test it (for now, it's the test website).
2- while you are in the application, click on add to the home screen.
3- After adding it to the home screen, make sure that the name of the icon is CANBeWell and it should have an icon the same as the CANBeWell logo.
FYI @niharikaavasthi @nrosh052

I have tested with both iPhone and Android, I attached the results here.
it seems that for iPhone it worked. But for Android it is not ok:

I only test it with iPhone, and it seems work well on iPhone

since the professor asked to freeze canbewell 1.0, we need to move to canbewell 2.0
discuss with Rishang

since the professor asked to freeze canbewell 1.0, we need to move to canbewell 2.0
discuss with Rishang

the English instruction is done, the French instruction is not completed yet.

the English instruction is done, the French instruction is not completed yet.

tested successfully


Adjust TPC-H testing on CI

I don't see a point in testing 10 GB workloads. If we're cost-conscious, I'd rather reduce the frequency of testing.

how long is one test run (compared to the rest of the suite)?

Coiled estimates that the cluster cost for test_dask.py increase from ~$0.16 to $2.70 per run, which will add up to an increase of ~$75/month. test_optimization.py increases from ~$0.10 to ~$0.34, adding up to an increase of ~$7/month.

https://github.com/coiled/benchmarks/pull/1534 entirely disables all automated tests for PRs and reduces scheduled testing to once per week. This should mitigate cost concerns.


Release beta-tensorflow 0.1.1-1.3.0-beta (automated commit)

Release beta-tensorflow 0.1.1-1.3.0-beta (automated commit)
Description:
a13644bc68aa7070c511c301d226e3b7c789e2ff
Source URL: https://infinity-artifacts-ci.s3.amazonaws.com/autodelete7d/tensorflow/20171108-194808-B5jqfxLX6Myo9o0D/stub-universe-tensorflow.json
Changes since revision 0:
0 files added: []
0 files removed: []
3 files changed:
--- 0/marathon.json.mustache
+++ 1/marathon.json.mustache
@@ -47,7 +47,7 @@
     "USE_GCS_KEY": "{{service.use_gcs_key_secret}}",
     {{/service.use_gcs_key_secret}}
     {{#service.use_tensorboard}}
-    "USE_GCS_KEY": "{{service.use_tensorboard}}",
+    "USE_TENSORBOARD": "{{service.use_tensorboard}}",
     {{/service.use_tensorboard}}
     "WORKER_COUNT": "{{worker.count}}",
     "WORKER_PLACEMENT": "{{worker.placement_constraint}}",
--- 0/package.json
+++ 1/package.json
@@ -2,11 +2,13 @@
     "packagingVersion": "4.0",
     "minDcosReleaseVersion": "1.9",
     "upgradesFrom": [
+        "*"
     ],
     "downgradesTo": [
+        "*"
     ],
     "name": "beta-tensorflow",
-    "version": "0.1.0-1.3.0-beta",
+    "version": "0.1.1-1.3.0-beta",
     "maintainer": "https://dcos.io/community/",
     "description": "TensorFlow on DC/OS",
     "selected": false,
@@ -15,6 +17,6 @@
         "tensorflow"
     ],
     "preInstallNotes": "This is a community package. Community packages are unverified and unreviewed content from the community.",
-    "postInstallNotes": "The DC/OS TensorFlow service is being installed!\n\n\tDocumentation: https://mesosphere.github.io/dcos-tensorflow/\n\tIssues: https://chat.dcos.io\n\n\tIf you installed from the UI, enter `dcos package install beta-tensorflow --cli` from the DC/OS CLI to install the Beta TensorFlow CLI subcommands.",
+    "postInstallNotes": "The DC/OS TensorFlow service is being installed!\n\n\tDocumentation: https://mesosphere.github.io/dcos-tensorflow/\n\tIssues: https://chat.dcos.io",
     "postUninstallNotes": "The DC/OS TensorFlow service is being uninstalled.\n\nFor DC/OS versions from 1.10 no further action is required. For older DC/OS versions follow the instructions at https://mesosphere.github.io/dcos-tensorflow/uninstall to remove any persistent state if required."
 }
--- 0/resource.json
+++ 1/resource.json
@@ -4,9 +4,9 @@
       "bootstrap-zip": "https://downloads.mesosphere.com/dcos-commons/artifacts/0.30.2/bootstrap.zip",
       "jre-tar-gz": "https://downloads.mesosphere.com/java/jre-8u144-linux-x64.tar.gz",
       "libmesos-bundle-tar-gz": "https://downloads.mesosphere.io/libmesos-bundle/libmesos-bundle-1.10-1.4-63e0814.tar.gz",
-      "scheduler-zip": "https://downloads.mesosphere.com/tensorflow/assets/0.1.0-1.3.0-beta/tensorflow-scheduler.zip",
+      "scheduler-zip": "https://downloads.mesosphere.com/tensorflow/assets/0.1.1-1.3.0-beta/tensorflow-scheduler.zip",
       "executor-zip": "https://downloads.mesosphere.com/dcos-commons/artifacts/0.30.2/executor.zip",
-      "examples-zip": "https://downloads.mesosphere.com/tensorflow/assets/0.1.0-1.3.0-beta/tensorflow-examples.zip"
+      "examples-zip": "https://downloads.mesosphere.com/tensorflow/assets/0.1.1-1.3.0-beta/tensorflow-examples.zip"
     }
   },
   "images": {
@@ -25,7 +25,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://downloads.mesosphere.com/tensorflow/assets/0.1.0-1.3.0-beta/dcos-service-cli-darwin"
+          "url": "https://downloads.mesosphere.com/tensorflow/assets/0.1.1-1.3.0-beta/dcos-service-cli-darwin"
         }
       },
       "linux": {
@@ -37,7 +37,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://downloads.mesosphere.com/tensorflow/assets/0.1.0-1.3.0-beta/dcos-service-cli-linux"
+          "url": "https://downloads.mesosphere.com/tensorflow/assets/0.1.1-1.3.0-beta/dcos-service-cli-linux"
         }
       },
       "windows": {
@@ -49,7 +49,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://downloads.mesosphere.com/tensorflow/assets/0.1.0-1.3.0-beta/dcos-service-cli.exe"
+          "url": "https://downloads.mesosphere.com/tensorflow/assets/0.1.1-1.3.0-beta/dcos-service-cli.exe"
         }
       }
     }

The preliminary release notes here: https://github.com/mesosphere/dcos-tensorflow/releases/tag/untagged-90d803bc279e045a615f
The major change is support for HDFS (instead of requiring GCE).

Closing this PR as we need a new stub.


Set env variables in docker-compose to be used with interface and visualization parts of the app

Would it make sense to set environment variables here that reference the other YABA server addresses that can be accessed through ReactJS's process.env? This way only one place needs to change if the server information changes

Originally posted by @Chris-Schnaufer in https://github.com/PecanProject/BETYdb-YABA/pull/69#discussion_r498525361
The aim of this issue is to set port and host environment variables for the interface and visualization part in the docker-compose file itself so that can be used in these parts through ReactJS's and Node.js process.env
For reference- Reading an environment variable in react which was set by docker

I'd like to work on this issue.


Updated dependencies

This PR updates Microsoft.Extensions.DependencyModel from 2.0.3 to 2.0.4 and updates the scripting libraries to 2.6.1. It also adds an explicit NuGet reference to Newtonsoft.Json with version 10.0.3  which solves #214 because Microsoft.Extensions.DependencyModel pulls in version 9.0.1 which is too low in many cases. Newtonsoft.Json is one of the few dependencies that we indirectly rely on via Microsoft.Extensions.DependencyModel and hence we need to pull in the latest here.

thanks a lot for fixing this!


Igordust patch 1

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

0 out of 2 committers have signed the CLA.

[ ] Igor D'Astolfo
[ ] igordust

Igor D'Astolfo seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.


How to open tesseract GUI program on Mac OS platform?

Hi there. Sorry for the silly question... after I installed this application on my system using Mac ports I could not invoke it's GUI. Do you know where the program is installed so I can open it up with the GUI? Thank you.

Please use tesseract user forum for asking question/support.


Can't Manually Import Mappings (Mac OSX)

The viewer only allows for the automatic download of mappings from http://export.mcpbot.bspk.rs/snapshot/, it would be useful if you could manually open up mappings (e.g. like the pre-release mappings for 1.11). I do not know if this is true for other OS' but I would assume it is.

this

If someone is feeling ambitious and wants this functionality, they are welcome to add it, but it won't likely become a part of this repo. Forks are, of course, allowed.


Revisit docs organization and content

Should focus on answering and providing examples, as clear and soon as possible, for:

How to make it work with DVC.
How to make it work with {X} ML Framework.
How to log scalars, images and plots.

Current Get Started focus too much on API overview, whereas most common use case would be to use an ML framework integration + DVC.

Current Get Started focus too much on API overview, whereas most common use case would be to use an ML framework integration + DVC

This is confirmed by current analytics (see https://github.com/iterative/dvc.org/pull/3923#issuecomment-1239774786).


typo in release

@rultor relese, tag is 0.0.11

@rultor relese, tag is 0.0.11

@yegor256 I'm sorry, I don't understand you :( Check this page and try again please

@rultor release, tag is 0.0.11

@rultor release, tag is 0.0.11

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.11

@yegor256 Done! FYI, the full log is here (took me 10min)


TypeError: Converting circular structure to JSON

I'm getting this error with the following syntax. Anyone know if I've messed something up?

es.search({
lat: 59.831834,
lng: 17.635795,
accessToken: //accessToken
})
.then((events) => {
console.log(JSON.stringify(events));
})
.catch((err) => {
console.error(JSON.stringify(err));
});

UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Converting circular structure to JSON

Can you show the full code and the complete stacktrace?

Here's the code with the accessToken stripped out.
const httpstatus = require('http-status');
const EventSearch = require("facebook-events-by-location-core");
const es = new EventSearch();

module.exports = (app, options) => {
const repo = options.repo;

/*

=================================
GET - GET EVENTS
=================================

*/

app.get('/events', (req, res, next) => {
    if (req.query.longitude && req.query.latitude) {

        es.search({
            lat: parseFloat(req.query.latitude),
            lng: parseFloat(req.query.longitude),
            accessToken: //accessToken
        })
        .then((events) => {
            res.status(httpstatus.OK).json(events);
        })
        .catch((err) => {
            res.status(httpstatus.INTERNAL_SERVER_ERROR).json({errorMessage: 'Something went wrong when searching for nearby events'});
        });

    } else {
        res.status(httpstatus.BAD_REQUEST).json({errorMessage: 'Please specify longitude & latitude coordinates'});
    }

});

}
The thing is that I don't get the error object from the Catch-phase. So the TypeError is all that ends up in my console. I've double-checked and it looks like something is wrong within the lib itself.

Slightly off-topic, but why don’t you use https://github.com/tobilg/facebook-events-by-location as you’re apparently trying to build an API service?

Mainly because I have a quite big & complex API already setup, and I found that this repo would be the easiest way to get the functionality in.

After some digging, the problem seems to occur on line 124. That success function never executes.

I actually couldn't find a way to get it to error-ing out... Made some minor tweaks in #23. Tests pass.

New version 0.8.1 has been published to npm. Please check and close accordingly.

Thanks for such a quick solution. 0.8.1 works fine. Closing issue.


classifier needs to be an array

This fixes a python3 bdist_wheel upload issue:
running upload
Traceback (most recent call last):
  File "setup.py", line 57, in <module>
    'Programming Language :: Python :: 3.6',
  File "/usr/local/lib/python3.6/site-packages/setuptools/__init__.py", line 131, in setup
    return distutils.core.setup(**attrs)
  File "/usr/local/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/local/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/local/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.6/distutils/command/upload.py", line 64, in run
    self.upload_file(command, pyversion, filename)
  File "/usr/local/lib/python3.6/distutils/command/upload.py", line 162, in upload_file
    body.write(value)
TypeError: a bytes-like object is required, not 'str'

It looks like this was previously resolved some time ago. Closing as duplicate and apologies for the delay.


网关

Fast Enterprise Application Development with WSO2
http://pan.baidu.com/s/1dF7mwEl : tjny
Lynda – Ethical Hacking: Perimeter Defenses
链接: http://pan.baidu.com/s/1bVyBgi : hehu

API manager throtting

WSO2文档


useThemeVars not working correctly with ConfigProvider

TuSimple/naive-ui version (版本)
2.18.2
Vue version (Vue 版本)
3.2.6
Browser and its version (浏览器及其版本)
Chrome(93.0.4577.82)
System and its version (系统及其版本)
MacOS(11.5.2)
Node version (Node 版本)
Reappearance link (重现链接)
https://codesandbox.io/s/fragrant-glitter-6773d?file=/src/Demo.vue
Reappearance steps (重现步骤)
Wrap components in n-config-provider and provide custom colors. Then try to get the theme colors with useThemeVars.
Expected results (期望的结果)
Colors provided from useThemeVars are the same as provided from custom theme with n-config-provider.
Actual results (实际的结果)
useThemeVars returns just the default colors.
Remarks (补充说明)
First of all, thank you very much for your great work on Naive UI!
Unfortunately useThemeVars is unusable right now when using a custom theme. I would expect it to return the customized theme instead of just default values. I hope this can be fixed and I will be able to use the theme vars across my project with custom components! :)

Edit: I hope this is not the same bug as 1176. Unfortunately I don't speak Chinese :)

@Volankey This seems to be an actual bug, take a look.

@07akioni Hello, is this issue actually fixed ? In the CodeSandbox link provided by the author, and using the latest naiveui version (2.25.2), the themeVars values still don't match the themeOverrides values...

@07akioni Hello, is this issue actually fixed ? In the CodeSandbox link provided by the author, and using the latest naiveui version (2.25.2), the themeVars values still don't match the themeOverrides values...

The bug is fixed. In the demo the config provider and useThemeVars are used in the same component, which isn't correct.

This is the correct behavior

Oh right, my bad. Thanks for your answer!


Cannot collect coverage due to a breaking change in instanbul instruments

Do you want to request a feature or report a bug?
Bug
What is the expected behavior?
It should work.
What is the current behavior?
Failed to write coverage reports:
        ERROR: TypeError: metrics.isEmpty is not a function
        STACK: TypeError: metrics.isEmpty is not a function
    at tableRow (/home/travis/build/jy95/mediaScan/node_modules/istanbul-reports/lib/text/index.js:133:27)
    at TextReport.onSummary (/home/travis/build/jy95/mediaScan/node_modules/istanbul-reports/lib/text/index.js:188:15)
    at TextReport.onDetail (/home/travis/build/jy95/mediaScan/node_modules/istanbul-reports/lib/text/index.js:193:17)
    at Visitor.(anonymous function) [as onDetail] (/home/travis/build/jy95/mediaScan/node_modules/istanbul-lib-report/lib/tree.js:34:30)
    at ReportNode.Node.visit (/home/travis/build/jy95/mediaScan/node_modules/istanbul-lib-report/lib/tree.js:123:17)
    at /home/travis/build/jy95/mediaScan/node_modules/istanbul-lib-report/lib/tree.js:116:23
    at Array.forEach (<anonymous>)
    at visitChildren (/home/travis/build/jy95/mediaScan/node_modules/istanbul-lib-report/lib/tree.js:115:32)
    at ReportNode.Node.visit (/home/travis/build/jy95/mediaScan/node_modules/istanbul-lib-report/lib/tree.js:126:5)
    at /home/travis/build/jy95/mediaScan/node_modules/istanbul-lib-report/lib/tree.js:116:23

Log file
Issue on instanbul
Please provide your exact Jest configuration
jest.config.js
  System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
  Binaries:
    Node: 8.9.3
    Yarn: Not Found
    npm: 5.8.0
  npmPackages:
    jest:
      wanted: ^22.4.3
      installed: 22.4.3

duplicate of https://github.com/facebook/jest/issues/5772


Fix caching in benchmark Marshaler function

Update the Marshal function to call TypeID on the input value rather
than on the type object to generate the cache key.
The TypeID function internally calls TypeOf on the input and returns the
pointer to the resulting object. Calling TypeID on the type object
always returns the TypeID of "Type". This causes the Marshal function to
generate an encoder for the type on the first call, then reuse that same
encoder for all subsequent calls regardless of the input type. Changing
this to call TypeID on the input object results in the correct behavior.
Also adds a space between elements to make the formatting clearer.

Thank you for contribution !


Traefik sporadically failing when proxying requests

Hello,
I will show here a simple scenario that reproduces the problem that I'm having with traefik. I have a traefik instance, configured with 1 backend and proxying all requests to it. The backend is just a uWSGI instance serving a 1024 bytes static file.
First I will present the results and what I could observe and then I will show how to reproduce the problem.
Both systems are running on the same host and traefik is proxying content using <IP_ADDRESS>. I'm using apache ab to generate the load.
Here is the current traefik config file:
graceTimeOut = 600
MaxIdleConnsPerHost = 100000

logLevel = "DEBUG"
defaultEntryPoints = ["http"]
[entryPoints]
[entryPoints.http]
address = ":90"

[web]
address = ":8082"

[file]
[backends]
  [backends.backend1]
    [backends.backend1.servers.server1]
    url = "http://<IP_ADDRESS>:9993"
    weight = 0
    [backends.backend1.LoadBalancer]
      method = "drr"
    [backends.backend1.maxconn]
      amount = 2048
      extractorfunc = "request.host"
[frontends]
  [frontends.frontend1]
  backend = "backend1"
  passHostHeader = true
    [frontends.frontend1.routes.test_1]
    rule = "Host:myhost"

I'm running this version of traefik, downloaded from github.
Version:      v1.0.2
Codename:     reblochon
Go version:   go1.6.2
Built:        2016-08-02_05:35:02PM
OS/Arch:      linux/amd64

And when I run apache ab, even with a low load I see sporadic failing requests:
The command: ab -c 2 -n 10 -H "Host: myhost" http://localhost:90/static/data
The result from apache ab:
Document Path:          /static/data
Document Length:        1024 bytes

Concurrency Level:      2
Time taken for tests:   0.016 seconds
Complete requests:      10
Failed requests:        1
   (Connect: 0, Receive: 0, Length: 1, Exceptions: 0)
Non-2xx responses:      1
Total transferred:      10849 bytes
HTML transferred:       9237 bytes
Requests per second:    630.28 [#/sec] (mean)
Time per request:       3.173 [ms] (mean)
Time per request:       1.587 [ms] (mean, across all concurrent requests)
Transfer rate:          667.76 [Kbytes/sec] received

And traefik logs shows:
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.703455ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 2.42295ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.628134ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 2.788108ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.647956ms
WARN[2016-08-12T18:01:14-03:00] Error forwarding to http://<IP_ADDRESS>:9993, err: net/http: HTTP/1 transport connection broken: readLoopPeekFailLocked: EOF
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.542621ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.591373ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.308187ms
DEBU[2016-08-12T18:01:14-03:00] Round trip: http://<IP_ADDRESS>:9993, code: 200, duration: 1.281541ms

Interesting to note is that only 9 requests are shown in uWSGI logs, that is, the failed request didn't even make to the backend server.
Important to note is that I can run this same ab command directly to uWSGI instance and no requests fails. Even with higher loads, for example:
concurrency: 64, total requests: 2048
Document Path:          /static/data
Document Length:        1024 bytes

Concurrency Level:      64
Time taken for tests:   0.463 seconds
Complete requests:      2048
Failed requests:        0
Total transferred:      2275328 bytes
HTML transferred:       2097152 bytes
Requests per second:    4419.50 [#/sec] (mean)
Time per request:       14.481 [ms] (mean)
Time per request:       0.226 [ms] (mean, across all concurrent requests)
Transfer rate:          4794.98 [Kbytes/sec] received

0 failed requests when running directly to uWSGI server.
Do you have any insights of what could be happening here? At the same time that I think traefik has a problem I think that uWSGI might be also part of the problem, because if I switch uWSGI with nginx, all requests works as expected. But how to explain the fact that uWSGI responds to all requests when accessed directly (not proxied by traefik)?
Thanks a LOT for any insights you may have on this problem.
How to reproduce
Running uWSGI
You need to install uwsgi. You can do this wih pip install uwsgi. Create a static/ folder and create the 1024 bytes file inside it:
mkdir static
dd if=/dev/zero bs=1 count=1024 of=static/data

Run uwsgi with:
uwsgi --buffer-size 32768 --http-socket <IP_ADDRESS>:9993 --processes 4 --http-timeout 60 --static-map2=/static=./
Running Traefik
Just run traefik with the provided config.
Running apache ab
ab -c 2 -n 10 -H "Host: myhost" http://localhost:90/static/data

This is just my guess, but it seems like uwsgi closes a connection that traefik thinks should be active (connection: keep-alive).
There is an issue related to this in golang https://github.com/golang/go/issues/15446  (resolved in golang 1.7 due out any day now...)
That issue only mentions POST requests, but the symptom you get is the same.
What happens if you disable keep-alive in uwsgi? Do you get the same result?

Hello @andersbetner, thanks for the insight. Actually my current uwsgi setup dos not add the Connection: keep-alive header. So my first results were gathered with keep-alive turned off.
I jusst ran a quick test and added the option --add-header "Connection: Keep-Alive" to my uwsgi instance. The header is being added corectly:
➜  ~ curl -siH http://localhost:31100/static/css/skins/skin.css | head -5
HTTP/1.1 200 OK
Content-Type: text/css
Content-Length: 5331
Last-Modified: Tue, 28 Jun 2016 17:19:21 GMT
Connection: Keep-Alive

I re-ran the ab test and still see failing requests, same behavior.
I also tried to compile traefik changing the FROM golang:1.6.3 line to FROM golang:1.7 (inside build.Dockerfile), but it did not work. =D
Indeed it will be a good test to dun traefik with Go 1.7.
Thanks!!

Hello all,
I did the following test:
Ran the same ab command line (2 concurent connections with 10 total requests), but this time I captured all the traffic with tcpdump. In this run I had 1 failed request.
Here is the tcpdump saved file: https://s3-us-west-2.amazonaws.com/daltonmatos-public/ab-lo.tcpdump
Note: In this test traefik is running on port 90 and uwsgi on port 9000.
I opened the saved tcpdump file in wireshark and applied these filters:
tcp.dstport == 90 && tcp.connection.syn Returns 10 results, that is, apache ab opened 10 connections to traefik.
tcp.dstport == 9000 && tcp.connection.syn Returns 9 results, that is, traefik is only connecting 9 times to uwsgi.
http && http.request.uri == "/static/collect/ok" && tcp.dstport == 9000 Returns 9 results, thats is, only 9 http requests were sent to uwsgi.
This shows me that traefik is missing one connection to my backend, in this case, uwsgi.
Any insight about what could cause this?
@emilevauge

@daltonmatos it looks to me like the issue linked to by @andersbetner is to blame.  could you try your tests with containous/traefik:pr-641 as that image should have been built with go 1.7...

Ok @errm, I will test it again and report back. Thank you very much!

Hello @errm, I just ran the tests again. The error still occurs, but the error message is now much more understandable. Look:
This is the log of a fisrt run of 10 requests, concurrency of 2.
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 768.454µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 804.515µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 659.699µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 866.266µs"
time="2016-09-13T14:02:15Z" level=warning msg="Error forwarding to http://<IP_ADDRESS>:9000, err: http: server closed idle connection"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 637.583µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 386.634µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 654.521µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 430.565µs"
time="2016-09-13T14:02:15Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 466.203µs"

With this error I can now search about how uwsgi behaves with idle connections.
On a second run (same parameters) there was new errors.
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 488.213µs"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 794.536µs"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 451.204µs"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 582.514µs"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 367.537µs"
time="2016-09-13T14:02:49Z" level=warning msg="Error forwarding to http://<IP_ADDRESS>:9000, err: EOF"
time="2016-09-13T14:02:49Z" level=debug msg="New attempt 2 for request: /static/collect/ok"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 392.388µs"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 400.474µs"
time="2016-09-13T14:02:49Z" level=warning msg="Error forwarding to http://<IP_ADDRESS>:9000, err: http: server closed idle connection"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 312.167µs"
time="2016-09-13T14:02:49Z" level=debug msg="Round trip: http://<IP_ADDRESS>:9000, code: 200, duration: 480.283µs"

Both runs resulted in 1 request failed, which means that traefik seems to be correctly retrying the request when this "EOF" error occurs.
About the idle connections, does it make sense to traefik detect this closed connection and automatically reconnect with the backend?
I will now search about uwsgi and idle connections.
Thanks a lot for the help!
Also, are there any plans to officially release traefik built with golang 1.7? Thanks!

Hey @errm and @andersbetner,
@andersbetner suggested earlier that keep alive could be the problem. At that time I "validated" this by only adding the Connection: keep-alive header in the responses but this is wrong since uwsgi is not really working with keep alive turned on, after all this is just a header like any other.
I now found out the --http-keepalive option of uwsgi (I found it searching about idle connections being closed) and now it all works!
I ran a test with 128 concurrent requests and a total of 10k requests, no errors!
At the same time that I thank you all for the help I also apologize for making you loose some time on this problem. Although the problem could have been solved before, the "idle connection" hint was the key to finally solve it.
Thank you very much!
Even so, I still hope to see traefik officially built on golang 1.7! ;-)

@daltonmatos
No worries, I'm glad you solved your problem.

Just closing, since the problem is now solved.
Thanks all!

@daltonmatos I am having the exact same issue but uWSGI doesn't seem to have a --http-keepalive flag:
# uwsgi --http-keepalive
uwsgi: unrecognized option: http-keepalive
getopt_long() error

What version of uWSGI were you using?

Seems like the http plugin needs to be loaded in order for the --http-keepalive flag to work:
# uwsgi --plugin http --http-keepalive

However, even with that set, I'm still getting the same http: server closed idle connection error. Strangely enough, running ab with the keepalive (-k) flag produces the following output:
# ab -c 2 -n 100 -k http://myserver:80/static/img/photo/CYC5207.jpg
...
Concurrency Level:      2
Time taken for tests:   0.073 seconds
Complete requests:      100
Failed requests:        0
Keep-Alive requests:    0
Total transferred:      29774500 bytes
HTML transferred:       29763000 bytes

The Keep-Alive requests: 0 is leading me to believe that I'm still missing a setting or flag somewhere.

@nathan-osman you need to add the http plugin, ie. --plugin python27,http --http-keepalive


install failed

➜  ~ helm install crane -n crane-system --create-namespace crane/crane
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: APIService "v1beta1.custom.metrics.k8s.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "crane"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "crane-system"

Hi francis:
Please refer to documents: https://gocrane.io/zh-cn/docs/getting-started/installation/#安装-crane-报错

Stil doesn't work

How can i get  the result as your doc says

How can i get the result as your doc says

Please make sure your helm repo is newest.  You can use this cmd to update it:
helm repo update

Stil doesn't work

Seems you used existing prometheus, so please check the docs here https://gocrane.io/zh-cn/docs/getting-started/installation/#使用外部的-prometheus可选

@francis-jjk Is your problem resolved?


assorted fixes

Removing stale faqs, updating images, fixing some documentation stuff.

Jenkins job istio.github.io/presubmit passed


New: first implementation of selection in FlexTable

Previously, when using the FlexTable developers needed to define their own system to handle the selection.
Now it is integrated in the component FlexTable.
This PR adds the following feature for the selection :
- Handler onRowSelect(rowIndex) -> called when a row is selected
- Handler onRowDeselect(rowIndex) -> called when a row is deselected
- Handler onSelectionIndexesForProposedSelection(indexes) -> called to confirm or change the future selected rows, in this callback you could get the set 1,2,3 but returns 5,6 to select the rows 5 and 6. This is useful to cancel a selection, for instance to show a confirmation panel.
- Added the propTypes allowsMultipleSelection, multiple selection will work only when using the mask key shift
- Added the propTypes selectedRows to preselect the rows
- The function rowWrapperStyle will give the boolean isSelected in the given object to specify if the row is selected or not.
Unit tests have been added in FlexTable.test.js

Let me know what was your idea with the HOC!

[Current coverage][cc-pull] is 95.02%

Merging [#298][cc-pull] into [master][cc-base-branch] will increase coverage by 0.06%

@@             master       #298   diff @@
==========================================
  Files            32         32
  Lines          1130       1145    +15
  Methods          87         89     +2
  Messages          0          0
  Branches        238        247     +9
==========================================
+ Hits           1073       1088    +15
  Misses           57         57
  Partials          0          0

Powered by Codecov. Last updated by [22135ed...1c7289c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bvaughn/react-virtualized/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bvaughn/react-virtualized/compare/22135ed2ac606b7e8261afdd7a37f8213a53f6f0...1c7289c0797d94285ace5b969aae071c5e424134
[cc-pull]: https://codecov.io/gh/bvaughn/react-virtualized/pull/298?src=pr

Hey @Dogild,
Thanks for sharing this PR. :)
I still prefer for this functionality to not live within FlexTable though. I think FlexTable should be all about layout and stateful things like selection should be done in a HOC. (That way FlexTable doesn't get more complicated and harder to maintain and optimize.)
You could move the properties you added to FlexTable, more or less, to a new HOC that decorates a FlexTable or a VirtualScroll and uses the existing row-click event to manage selected state.
I'm still on the fence a bit about whether this should be in core react-virtualized or if it's too specific a use-case.

[Current coverage][cc-pull] is 95.02%

Merging [#298][cc-pull] into [master][cc-base-branch] will increase coverage by 0.06%

@@             master       #298   diff @@
==========================================
  Files            32         32
  Lines          1130       1145    +15
  Methods          87         89     +2
  Messages          0          0
  Branches        238        247     +9
==========================================
+ Hits           1073       1088    +15
  Misses           57         57
  Partials          0          0

Powered by Codecov. Last updated by [22135ed...1c7289c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bvaughn/react-virtualized/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bvaughn/react-virtualized/compare/22135ed2ac606b7e8261afdd7a37f8213a53f6f0...1c7289c0797d94285ace5b969aae071c5e424134
[cc-pull]: https://codecov.io/gh/bvaughn/react-virtualized/pull/298?src=pr

Let me know what you think about this version :)

Hey @Dogild,
This approach looks more consistent with the other components/HOCs. So that's 👍
I'm still undecided about whether it belongs in core or if it should be an external NPM project that depends on react-virtualized. I've found myself wishing I'd made some other components external libraries (eg ScrollSync and CellMeasurer) to keep react-virtualized core lighter and easier to maintain.
I'll leave a couple of thoughts on the PR. But I will need to give it a bit more consideration before I decide whether to merge or not. :)

[Current coverage][cc-pull] is 95.09%

Merging [#298][cc-pull] into [master][cc-base-branch] will increase coverage by 0.13%

@@             master       #298   diff @@
==========================================
  Files            32         33     +1
  Lines          1130       1162    +32
  Methods          87         90     +3
  Messages          0          0
  Branches        238        250    +12
==========================================
+ Hits           1073       1105    +32
  Misses           57         57
  Partials          0          0

Powered by Codecov. Last updated by [22135ed...c2bb144][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bvaughn/react-virtualized/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bvaughn/react-virtualized/compare/22135ed2ac606b7e8261afdd7a37f8213a53f6f0...c2bb144421970d490292a3733827b3364a45810a
[cc-pull]: https://codecov.io/gh/bvaughn/react-virtualized/pull/298?src=pr

I have corrected the implementation following your instruction

Sorry for kind of letting this hang. I went to Japan for a few weeks for work and it kind of slipped my mind. :/
I was on the fence about this PR, but I think this component would be better as a dependent component (eg react-infinite-calendar, react-sortable-hoc, react-virtualized-checkbox, react-virtualized-select). That way if it's useful to others, they can benefit from it, but I won't have to manage the additional complexity. (I've been pretty strapped for time lately.)
I'd be happy to link to it from the main README as I do with the other components I mentioned above. I'd also be happy to answer any questions you have about getting a repo setup or getting the component published to NPM (if you haven't done it before).
I appreciate the contribution and the suggestion. Happy to help get it up and out for others to use. Let me know if I can do anything. :D

That feature is exactly what I need now. Thanks @bvaughn for the great work! Have you managed to package that component into a separate npm project?

Hi @remon-georgy, no I didn't put the component in a separate package. The company where I work doesn't have a open source policy yet...We will release that in the future, but I don't now when...

@Dogild fair enough. I'll still like to use your PR for inspiration :).


[FLINK-18513][Kinesis] Add AWS SDK v2.x dependency and KinesisProxyV2

What is the purpose of the change
Adding AWS SDK v2.x dependency and skeleton proxy interface for Fan Out consumption.
Brief change log

Update pom file to include AWS SDK v2.x dependency

Dependencies are shaded and relocated into the connector jar (similar to AWS SDK V1)

Added a KinesisProxyV2Interface skeleton (methods and implementation will come in follow up tasks)
Add utility methods to create an AWS SDK v2.x Kinesis Client from connector properties, including:

Region
Credential Provider
HTTP Client config
Other properties

Verifying this change
This change added tests and can be verified as follows:

AWSUtil > AWSUtilTest
AwsV2Util > AwsV2UtilTest

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): yes
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure

I'll address my own comments and proceed to merge this. Thanks @dannycranmer !

@dannycranmer
I've been fixing a few bugs in the PR that has failed CI, before merging it.
So far have bumped into this:
2020-09-02T10:18:54.5913921Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade (shade-flink) on project flink-connector-kinesis_2.11: Error creating shaded jar: duplicate entry: META-INF/services/org.apache.flink.kinesis.shaded.software.amazon.awssdk.http.async.SdkAsyncHttpService -> [Help 1]
2020-09-02T10:18:54.5915252Z [ERROR]
2020-09-02T10:18:54.5916062Z [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2020-09-02T10:18:54.5916918Z [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2020-09-02T10:18:54.5917384Z [ERROR]
2020-09-02T10:18:54.5918070Z [ERROR] For more information about the errors and possible solutions, please read the following articles:
2020-09-02T10:18:54.5918907Z [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
2020-09-02T10:18:54.5919331Z [ERROR]
2020-09-02T10:18:54.5919700Z [ERROR] After correcting the problems, you can resume the build with the command
2020-09-02T10:18:54.5920396Z [ERROR]   mvn <goals> -rf :flink-connector-kinesis_2.11

Original build logs:
https://dev.azure.com/tzulitai/tzulitai-flink/_build/results?buildId=35&view=logs&jobId=66592496-52df-56bb-d03e-37509e1d9d0f&j=66592496-52df-56bb-d03e-37509e1d9d0f&t=ae0269db-6796-5583-2e5f-d84757d711aa

@tzulitai the build issue was caused by running multiple builds without clean. For example:
mvn package
mvn package

The files left hanging around were not being overridden by the shade plugin. The org.apache.maven.plugins.shade.resource.ServicesResourceTransformer configuration is inherited by an ancestor pom. I have verified that these service manifest files are not required by the connector and removed them from the shaded jar (if you know a different/better way to configure this plugin, happy to swap it out):
  META-INF/services/reactor.blockhound.integration.BlockHoundIntegration
- META-INF/services/org.apache.flink.kinesis.shaded.software.amazon.awssdk.http.async.SdkAsyncHttpService
- META-INF/services/org.apache.flink.kinesis.shaded.software.amazon.awssdk.http.SdkHttpService

@flinkbot run azure

Thanks for the update @dannycranmer! I'll wait for this CI run.


Actions bar layout

Hi
I have two very large display 2560x1080
Would it bepossible to group all actions
present in the upper bar  bar, as such
Left center or right
It would make thé lms expérience even better
Jacques

Duplicate of your own issue!!!! #977

Sorry i double myself
Le mer. 13 nov. 2024, 17:59, CraigD @.***> a écrit :

Duplicate of your own issue!!!! #977
https://github.com/CDrummond/lms-material/issues/977
—
Reply to this email directly, view it on GitHub
https://github.com/CDrummond/lms-material/issues/978#issuecomment-2474210260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZRVELVVEGKVOK6R2RSATD2AOAQXAVCNFSM6AAAAABRWEH2F2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUGIYTAMRWGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Formatting axis labels

I wish to be able to control the axis label style and format, such as font properties, in a similar way we do with ticks.
I don't mind too much about the API, but something like the following seems reasonable to me:
bq.Axis(label='my label', label_format={'font-size': 10})

I stumbled across this limitation, and surprisingly I wasn't able to find a solution. If the feature is already implemented it would be great if anyone could share a code snippet.
Thanks!

Yes, I also could not find a way of doing this.   A label_style attribute similar to the tick_style would be nice
axis.tick_style  =
    dict({'font-family': 'Verdana',
    'font-size': '15px',
    'font-weight': 'bold',
    'font-style': 'italic'})

I came here looking for a solution to this.


Set up Github Pages

Go to repository Settings and set up GitHub Pages (from the main branch), update repository description with the proper website link. Follow the link to check if everything is fine - you should see your index.html content.

Done


core: update to 0.7.4

ref to https://github.com/textileio/ios-textile/commit/ffdc0d03fe0f8770635059ef8aefe19c266b8f38

Hey @flyskywhy thanks! I actually got those same changes into https://github.com/textileio/android-textile/pull/59 which I'll just merge now. That way, we'll get the other fixes in that PR as well.

thanks @flyskywhy!


Symfony 4 support

Will you update this bundle to support Symfony 4?

Ah, never mind. I see a PR was already merged. Could you please make a new release though?


Random Error?

Description
Random Error that I don't know why is popping up.
Detailed Information
Is available here

Your plugin BanManager is broken. Talk to the dev of that plugin.


some issues about the pre-training caffemodel

I want to download your pre_training caffemodel,but I found the website http://mmlab.siat.ac.cn can't connect,so it's hard to download the caffemodel ,although  I have the  shadow socks ......   Could you give another website or netdisc address？
Thanks very much!!

All models have been moved out of that server days ago. Please update your codebase.


WTP wifi when connecting to WTP

We successfully archived to connect the WTPs and CPP with the controller but not the clients with the WTPs. The clients could not connect to WTPs because there is not any empower wifi network available. This happens only when the WTPs are connected to the CPP.
Do we need to configure anything more to the CPP or WTP ?

No, the CPP should work like normal switches. Did you connect the OVS in
the CPP with an OF controlelr? if so did you load the learning switch
application on the OF controller?
On 3 May 2017 at 12:02, Georgios Tsiatsios<EMAIL_ADDRESS>wrote:

We successfully archived to connect the WTPs and CPP with the controller
but not the clients with the WTPs. The clients could not connect to WTPs
because there is not any wifi client. This happens only when the WTPs are
connected to the CPP.
Do we need to configure anything more to the CPP or WTP ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/5g-empower/empower-lvnf-agent/issues/3, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAdzTK5BOwt4UH_5ev932JSMRRKaaZmQks5r2FCegaJpZM4NPL0v
.

I followed your empower network installation. The cpp is connected to the empower-runtime controller.
Which application are you referring to?

I fixed this error. But now all the clients have IP but could not connect to internet.


[Feature]: onRowUnselected action in a table

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
When a row gets unselected, users want to trigger an action like clearing a value.
Why should this be worked on?
It's useful for clearing values from store or un-assigning values.
 Front conversations

Hi, I just want to point out a use case I have.
I have two tables on one page
One is a list of Jobs
The other is a list of Actions
I want to filter the actions table based on the job selected row. When the user clears their selected row, I'd like to run the ActionsSelectApi again to fetch all actions, no filter.
Right now I don't see a way to do that without this trigger.

@ZackKnopp a workaround for this is to have 2 APIs

Fetch All Data
Fetch Filtered Data
and then in the 2nd table, depending of whether the first table contains the selected row, you can show either al the data or the filtered data

While only a few users might need this, not having this blocks them in cases when they want to run functions.

@Nikhil-Nandagopal how will a user trigger an event in this case? Since onRowSelected will not be triggered, is there a way to listen for this being set to undefined and trigger? Like any JS function needs to be in sync with this.

@dilippitchika what I mean is a user will configure the below code in an input default text or image
{{Table1.selectedRow ? Table1.selectedRow.name : undefined}}
and with that, the widget will get no value when the table is unselected

No i think that is different, because triggering events is similar to onRowSelected event here. People ideally want to run a new api because this solution we have already given to people.

https://discord.com/channels/725602949748752515/1052032905322442793
please refer

Assuming 10% of onRowSelected users need this
Stats

Stat
Values

Reach
110

Effort (months)
0.5

I have this same issue. My use case is enabling a button outside the table when a selection is made and disable it when it is unselected.
As a workaround, I am using a column with a button. When the user clicks the button I can check which row it came from.

@cberiganTAG you can disable the button by changing the button disabled property to JS and writing code in it like
{{ Table1.selectedRow.id === undefined }}
This will disable a button if the table selected row's column is not there or rather the tables row is not selected

@cberiganTAG you can disable the button by changing the button disabled property to JS and writing code in it like {{ Table1.selectedRow.id === undefined }} This will disable a button if the table selected row's column is not there or rather the tables row is not selected

I was able to do {{able1.selectedRow.id === ''}}.

+1 for either a new action 'onRowUnselected' or an option to trigger the 'onRowSelected' action when a user de-selects a row.  Also when the 'select all' is clicked in the column header.

Maybe change name of action to rowSelection which would trigger whether the row is selected or unselected.  The selected row would become -1 as it currently does, but this would be actionable.

I second the above suggestion from @pchambless. This could also be fired for the select all checkbox as suggested by @mmcallister-selkirk, or any other time the value of selectedRow changes.


[carbon-cache] Error: Connection refused by other side: 111

Greetings,
I am building out a new Graphite Box since or other one is using a much older version and not appropriately configured. That being said I am trying to set up using two carbon-cache processes with 1 carbon-relay. It basically works, but reviewing the logs for carbon-cache I see many of these messages.
11/10/2017 12:04:50 :: Tagging carbon.agents.ubuntu-16-ctk-b.committedPoints
11/10/2017 12:04:50 :: Starting factory _HTTP11ClientFactory(<function quiescentCallback at 0x7f6980d56ed8>, <twisted.internet.endpoints.HostnameEndpoint object at 0x7f6980d3b990>)
11/10/2017 12:04:50 :: Stopping factory _HTTP11ClientFactory(<function quiescentCallback at 0x7f6980d56ed8>, <twisted.internet.endpoints.HostnameEndpoint object at 0x7f6980d3b990>)
11/10/2017 12:04:50 :: Error tagging carbon.agents.ubuntu-16-ctk-b.committedPoints: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by other side: 111: Connection refused.
]
11/10/2017 12:05:21 :: Tagging ubuntu-16-ctk.disktotals.writekbs
11/10/2017 12:05:21 :: Starting factory _HTTP11ClientFactory(<function quiescentCallback at 0x7f6980f80410>, <twisted.internet.endpoints.HostnameEndpoint object at 0x7f6980d25090>)
11/10/2017 12:05:21 :: Stopping factory _HTTP11ClientFactory(<function quiescentCallback at 0x7f6980f80410>, <twisted.internet.endpoints.HostnameEndpoint object at 0x7f6980d25090>)
11/10/2017 12:05:21 :: Error tagging ubuntu-16-ctk.disktotals.writekbs: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by other side: 111: Connection refused.
]

I do see metrics getting recorded, but this seems to indicate that not all of them are. What am I doing wrong?
Besides Carbon Metrics I was also using Callectl to test metric ingestion.
sudo collectl --export graphite,<IP_ADDRESS>:2013
carbon.conf
[cache]
DATABASE = whisper
ENABLE_LOGROTATION = True
USER =
MAX_CACHE_SIZE = inf
MAX_UPDATES_PER_SECOND = 500
MAX_CREATES_PER_MINUTE = 50
MIN_TIMESTAMP_RESOLUTION = 1
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2003
ENABLE_UDP_LISTENER = False
UDP_RECEIVER_INTERFACE = <IP_ADDRESS>
UDP_RECEIVER_PORT = 2003
PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2004
USE_INSECURE_UNPICKLER = False
CACHE_QUERY_INTERFACE = <IP_ADDRESS>
CACHE_QUERY_PORT = 7002
USE_FLOW_CONTROL = True
LOG_UPDATES = False
LOG_CREATES = False
LOG_CACHE_HITS = False
LOG_CACHE_QUEUE_SORTS = False
CACHE_WRITE_STRATEGY = sorted
WHISPER_AUTOFLUSH = False
WHISPER_FALLOCATE_CREATE = True

[cache:b]
LINE_RECEIVER_PORT = 2103
PICKLE_RECEIVER_PORT = 2104
CACHE_QUERY_PORT = 7102

[relay]
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2013
PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2014

RELAY_METHOD = consistent-hashing
DESTINATIONS = <IP_ADDRESS>:2004:a, <IP_ADDRESS>:2104:b
MAX_QUEUE_SIZE = 10000
MAX_DATAPOINTS_PER_MESSAGE = 500
QUEUE_LOW_WATERMARK_PCT = 0.8
TIME_TO_DEFER_SENDING = 0.0001
USE_FLOW_CONTROL = True
USE_RATIO_RESET=False
MIN_RESET_STAT_FLOW=1000
MIN_RESET_RATIO=0.9
MIN_RESET_INTERVAL=121
[aggregator]
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2023
PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2024
FORWARD_ALL = True
DESTINATIONS = <IP_ADDRESS>:2004
REPLICATION_FACTOR = 1
MAX_QUEUE_SIZE = 10000
USE_FLOW_CONTROL = True
MAX_DATAPOINTS_PER_MESSAGE = 500
MAX_AGGREGATION_INTERVALS = 5

Any help would be appricated. Thank you.

You need to configure GRAPHITE_URL = http://your.graphite to point to your graphite-web install if it's not available on localhost port 8000

Woot, thank you. You saved me the rest of my day.. Probably a couple of days, lol!


Fallback for skip_page/peek_page without OffsetIndex in SerializedPag…

…eReader
Which issue does this PR close?

Closes #2459
Closes #2434
Rationale for this change

Need to be able to peek/skip pages even if we do not have an OffsetIndex
What changes are included in this PR?

Implement skip_next_page and peek_next_page in SerializedPageReader
Are there any user-facing changes?

I believe @Ted-Jiang is already working on this in #2460... Perhaps we could keep some of the tests from this?

I believe @Ted-Jiang is already working on this in #2460... Perhaps we could keep some of the tests from this?

Ah, sorry about that.


[Serial] Propagate changes in cudaCompat to source code

Propagate the changes expressed in cudaCompat.h to source code changes in the serial variant.  This makes it easier to read as a "serial" (or non-CUDA) code.
Most of the changes were made programmatically using comby (https://comby.dev) and cleaned up with clang-format.
The cuda-specific code (under the CUDA_ARCH preprocessor define and all of radixSort.h) was removed manually.
The comby matches/rewrites are stored in configuration files (.toml suffix).  Individual configuration files are applied with the command:
comby -i -config remove_syncthreads.toml -matcher .c  -d pixeltrack-standalone/src/serial
The configuration files are attached
serial_rewrite.tar.gz
Some of the changes:

Remove __host__, __device__, __global__, __shared__, __forceline__ attributes
Replace gridDim, blockDim, gridIdx, blockIdx.  Some of the patterns get more involved in order to simplify the resulting expressions.  Also some of the expressions are assigned to an auto variable, which needs to have a more specific type once the expression is simplified to a number.
Remove syncthreads, threadfence, etc.
Remove __ldg

There were some remaining cuda index references (to the z component) that were removed manually.
The atomic calls were left alone as useful markers to know where to put atomic operations in any parallel code based off this branch.

Physics and performance are unchanged.


contrast_loss issue

Is it normal for the contrast loss to be negative？even，the contrast loss can be reduced

Is it normal for the contrast loss to be negative？even，the contrast loss can be reduced

I have the same question as yours.  If you figured it out, could you please make a explaination about this?


Predicting only one row

Hello,
firstly I'd like to congratulate you and tell you that you have done a really good work in this package.
I'm trying to test on a dataset that looks like this:

The last columns are 'category', 'lifetimes'(T) and 'observed'(E).

My code is as follows and works fine:
cf = CoxPHFitter()
cf.fit( auxDF, 'T', event_col='E', strata = ['category'])
r = cf.predict_median(coxDF.ix[ 0: 1, :8 ])   #two lines of testing (indices 0 and 1) until the 8th column
But when I try to predict only one line:
r = cf.predict_median(coxDF.ix[ 1, :8])   #one line of testing (index 1)
I get the error:
ValueError: Shape of passed values is (1, 1), indices imply (1, 8)

Any idea what am I doing wrong? I've tried creating another DF, np.array(in the right order), nothing works.
Thank you!

interesting, thanks for the bug report.
I think the difference is that .ix[ 0: 1, :8 ] returns a Dataframe (of size (2, 8)), and .ix[1, :8] returns a Series of size (8,). Kinda lame that lifelines will fail on this.
For now, you can do .ix[[1], :8] (note the [] included)

Thank you!

This line worked:
cf.predict_median(coxDF.ix[ [0], :8])

This didn't work
cf.predict_median(coxDF.ix[ [1], :8])

This works and returns me the result 4 times:
cf.predict_median(coxDF.ix[ [1,1], :8])

Very stange that cf.predict_median(coxDF.ix[ [1], :8]) didn't work - what is the error message? Also, what is the index of your dataframe?

I'm wondering if basic questions like this may be better-suited for
stackoverflow. For example, code snippets, data snapshots, and error
messages could be provided so that the community may suggest solutions.
On Mon, Feb 22, 2016 at 12:57 PM, Cameron Davidson-Pilon <
<EMAIL_ADDRESS>wrote:

Very stange that cf.predict_median(coxDF.ix[ [1], :8]) didn't work - what
is the error message? Also, what is the index of your dataframe?
—
Reply to this email directly or view it on GitHub
https://github.com/CamDavidsonPilon/lifelines/issues/227#issuecomment-187294444
.

It's a lifelines problem, so I think it's appropriate to put here as well

ah cool, sounds good.
On Mon, Feb 22, 2016 at 1:11 PM, Cameron Davidson-Pilon <
<EMAIL_ADDRESS>wrote:

It's a lifelines problem, so I think it's appropriate to put here as well
—
Reply to this email directly or view it on GitHub
https://github.com/CamDavidsonPilon/lifelines/issues/227#issuecomment-187299628
.

Problem solved with:
testDF = pd.DataFrame(columns = [..my8columns..])
testdf.loc[0] = np.array( OriginalDF.ix [n, :8] )
result = cf.predict_median(testdf)

What function do I need to call to know the predicted median time and its corresponding probability? I would like to know when does my predicted survival function crosses 0.5 first time.

@gpras I don't think that question is valid, in a frequentist framework at least.
The predicted survival curve does or does not cross 0.5, there is not way to attack a probability to it.

I would like to know when does my predicted survival function crosses 0.5 first time.

This is exactly the median, which is finite if the curve crosses 0.5, and infinite if the curve never crosses.

@CamDavidsonPilon - Is there a way I can input specific event_at (specific time) while using the function predict_survival_function in Cox's regression


Add css unrolling option to bin/carto

Given the current status this is unlikely to happen. But feel free to reopen if you don't agree.


Fix continuation marks

Previously, the continuation marks (a backslash) was incorrectly outputted on the line that didn’t have a trailng newline, rather than on the following record.
This also cleans up writing metadata.

Not sure if this handles errors followed by output records correctly.

Fixed and tests added.


header test

Am I going mad?  in header.spec.js I can make both
    expect(_wrapper.contains(<Link to='/counter'/>)).to.equal.false
    expect(_wrapper.contains(<Link to='/counter'/>)).to.equal.true

I think you need
    expect(_wrapper.contains(<Link to='/counter'/>)).to.be.true

and when u fix the test it fails as Link has activeClassName

Good catch. These really should use should expectations with actual method calls to prevent mistakes like this. Will fix.

Thank you for your PR: https://github.com/davezuko/react-redux-starter-kit/pull/861. Your fix has been merged into master.


Change Twitter Symbol to X in footer section

I would like to propose a change to update the Twitter symbol to "X" to reflect Twitter's recent rebranding. This change ensures consistency with the platform's new identity and avoids any potential confusion for users.
please assign this issue to me

@Sanskriti1102  please assign this issue to me

Update logo of Twitter in index.html file
#12 issue solved


promoting _appmetadata() method to an independant file

As we march toward the development of prototype of the app-directory (https://github.com/clamsproject/clams-apps/issues/15), it seems that we need a easier way to query for app metadata. In the linked issue, there were two suggestions on how a machine can read app metadata.

@marcverhagen suggested "a metadata file in JSON or YAML format"
@keighrim suggested "Automatically build the app image from Dockerfilein the repo, start a container and query for app metadata"

And @kelleyl and I talked about this last week, and we'd like to suggest a third way. But first, possible issues with the above suggestions;

Metadata as a static file: this will provide probably the easiest way for a machine to read the metadata. The problem is that either app developers have to edit raw JSON/YAML files to update the metadata (as opposed to using python code in the SDK that already provides abstraction of JSON syntax and automatic validation) or use the python code to specify metadata and then manually export it to a JSON/YAML file (which can be automated, but not at the python SDK level). I dislike the latter case more, as one more manual step means more room for human error.
Build-and-run a container and send GET request: obvious issue with this is the time and energy wasted to build the whole thing, which can include downloading GB of models or compiling underlying software like kaldi, just to get the (mostly) static content.

So the third way;
App development side
Developers can choose between metadata.json or metadata.py to write the app metadata.

metadata.json (or yaml): this is identical to the first suggestion above. If a developer is confident in directly editing raw JSON file and makes sure the file is valid JSON as well as CLAMS app metadata, they should be able to choose this path and not worry about writing more python code as described in the below.
metadata.py: we provide a skeleton for this file via the SDK documentation or the template code repository. This file MUST import only python builtins and clams-python library to minimize time and effort to build and run this file.

SDK development side
And then in the SDK, we remove _appmetadata() method and re-write annotate() so that

if metadata.json is present, just load the metadata from the file.
if metadata.py is present, import the module and call a function inside to load metadata.

App template
And, the metadata.py in the starter kit should look like;
from clams import AppMetadata
from mmif import DocumentTypes, AnnotationTypes
# developers MUST not change the above

def get_metadata(): # the name of this function must be consistent throughout all the apps compatible with the "app-directory"
    metadata = AppMetadata(
        # fill these
        name="",
        description="",
        url="http://repository/of/source_code",
        app_license="",
        analyzer_version="",
        analyzer_license="",
        identifier="",
        )
    metadata.add_input(DocumentTypes.xxxDocument)
    metadata.add_output(AnnotationTypes.xxxAnnotation)
    return metadata

# developers MUST not change the below
if __name__ == '__main__':
    return get_metadata().json(exclude_defaults=True, by_alias=True)

app-directory side story
And finally, but not the least, app directory automation can

when metadata.json is present, just read the file in
when metadata.py is present, run pip install $(grep clams-python requirements.txt); python metadata.py > metadata.json and read in the json file

A few question to resolve to make this happen:

Is the separate "template" repository the best place to put the metadata.py template? If we do so, then when there's an update in the metadata scheme, we need to update two different codebase. I think that's probably not the best practice. We can maybe package the whole template repository inside the SDK and add a CLI command (like clams new-app) to release a local copy of the template on demand.
If we make the SDK responsible for some of metadata (e.g. #114), we need to decide where in the code the "injection" should occur.

If the injection is done inside appmetadata() method, the output of metadata.py (and the app-directory) won't have those to-be-injected fields
If the injection is done inside the metadata.py, it is no longer a part of SDK. In this case, if there's metadata.json instead of the metadata.py, the app-directory, again, won't have those to-be-injected fields.
We can add a CLI command (like clams app-metadata) to collect information from the working directory (metadata.json, metadata.py, git log, $APP_VERSION, etc) and generate a complete metadata JSON.

Now I'm all ears. Let me know what you think.

Regarding the question number 2 from the previous comment, implementation of app_version injection that's proposed in https://github.com/clamsproject/clams-python/pull/118 is done basically by setting a default value (default but dynamically generated) to the field before _appmetadata(), appmetadata(), or metadata.{jons,py}. So the question seems to have become irrelevant. However it may come back for a future development (addition, change) of a field in AppMetadata that needs automatic generation but cannot use a "default_factory"-like mechanism. (I can't imagine such an example for now though)

Additionally, with some fields are being auto-generated (currently mmif_version, possibly app_version and identifier in the future depending on how #114 resolves), I actually don't think having static JSON/YAML files is a good option anymore. Conceptually, if there's metadata.py I would immediately think that there should be something dynamically generated, but when I see a JSON or YAML file, I'd take the file as static information and consider what in there is a complete set of necessary information. However, with auto-generating values, a static JSON/YAML file cannot be a complete, source-of-truth file, unless the maintainer takes extreme care of the content not to be outdated, which I would not expect from any human being.

resolved via #128 .


Develop

We should avoid using intern.
Tests passed on my side, sbcl64 1.2.8, but we should wait for the comprehensive testing results on travis-ci.

https://travis-ci.org/guicho271828/arrow-macros/builds/68179252

I may even want to get rid of the code walker... do we really need it?
Possibly a simple symbol-macrolet would suffice.

Thanks for your pull request.
I understand your point about implicit intern and I will accept this later.
But travis-ci status seems to be failing. Can you fix this?
The detailed comment at line 96-132 in arrow-macros.lisp is very helpful for me (thanks!), but I don't want to include this in the source file, so can you remove this? Or can you move it here?
About code walker, I prefer less dependencies too.
I use this for finding <> symbols in same context in nested diamond wands.
If you have any ideas to substituting this, please let me know.

travis test script was fixed, and it builds on most implementations except cmucl (not tested) and ecl (failure loading hu.dwim.walker).
I agree that I should remove the comments in the script.
re: code walker, currently I do not have a good answer...

https://travis-ci.org/guicho271828/arrow-macros

I have merged your commit and added a few sentence to README.md.
Thanks!


Add Create Fileshare for AWS

Issue/Feature Description:
Create Fileshare in AWS with provided name, size/quota and region
[POST] v1/<tenantId>/Backend/<backendId>/shares
Why this issue to fixed / feature is needed(give scenarios or use cases):
This will add support for creating the fileshare which can be used later for mounting
Cof CRUD
How to reproduce, in case of a bug:
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

Done in https://github.com/sodafoundation/multi-cloud/pull/1032

Closing


[SPARK-6899][SQL] Fix type mismatch when using codegen with Average on DecimalType

JIRA https://issues.apache.org/jira/browse/SPARK-6899

Test build #30305 has started for   PR 5517 at commit 8ae5f65.

Test build #30305 has finished for   PR 5517 at commit 8ae5f65.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30305/
Test PASSed.

Thanks!  Merged to master.


plug#load("some-plugin") fires BufReadPost event

Calling load manually fires BufReadPost event. This alone may not be a problem. However, combined with the following it is. It may fire other events I may not be aware of, since sometimes the cursor moves to places that are not defined by the '" register.
I have the following in my init.vim
"restore cursor position
au BufReadPost *
      \ if line("'\"") > 0 && line("'\"") <= line("$") |
      \     execute 'normal! g`"zvzz' |
      \ endif

Is this intentional? How can I prevent this?
minimal init.vim to reproduce
call plug#begin('~/.config/nvim/plugged')

  Plug 'kana/vim-textobj-user'   " Any plugin
  "Plug 'kana/vim-textobj-user', {'on': []} "The same as above

call plug#end()
au BufReadPost * echo "BufReadPost Fired"

Just execute the following:
:call plug#load('vim-textobj-user')

@khalidchawtany Hello. Had a look in the function, we fire the BufRead autocmd before returning from the load. I looked in the git history and that dates back to the addition of the plug#load function itself before I was here. You will have to wait for @junegunn to comment. I imagine he had a good reason, it must in some way relate to loading the plugin.

I took a look at the source code and saw the code too. If it is necessary and there is no way to remove it, cannot we at least set a variable before doautocmd and free the variable after it? This way we can check for this variable's existence and act accordingly.

I wonder if firing BufRead implicitly fires BufReadPost?

I beleive it is needed for lazy loading plugin that have the ftplugin folder: since we "potentially" already loaded the buffer then we have to fire the event again for the ftplugin script to be sourced.

There must be workaround (At least what I suggested should work :point_up:  ). If you have a plugin that is lazy loaded with a <Plug>(Do_Something_With_Text_Under_Cursor), you find your cursor jumps miles away, after the operation is finished :(

I can use the following to work around this issue. However, it is a hack :(
    au BufReadPost *
          \ if exists('g:current_file_path') |
          \   if g:current_file_path != expand("%:p") |
          \     if line("'\"") > 0 && line("'\"") <= line("$") |
          \       execute 'normal! g`"zvzz' |
          \       let g:current_file_path=expand("%:p") |
          \     endif |
          \   endif |
          \ else |
          \     if line("'\"") > 0 && line("'\"") <= line("$") |
          \       execute 'normal! g`"zvzz' |
          \       let g:current_file_path=expand("%:p") |
          \     endif |
          \ endif

@vheon is correct. File type detection by convention is performed on BufRead event. So if we don't fire it, filetype-specific plugin that we load with the function will not be activated immediately for the current buffer, until we "reopen" it with something like :e command.
If you see the output of :autocmd BufRead, you'll also notice that BufRead event is usually used for setting up the plugin state for the current buffer. e.g. fugitive, signify, etc. So I figured that it would be beneficial for most users that plug#load triggers the event, though the approach is a little crude and can have unwanted side effects like you experienced.
You can suppress the event with :silent noautocmd call plug#load('vim-textobj-user').

@khalidchawtany Did you try what junegunn suggested? I'd like to know if we can close this, as he's explained everything.
And damn my noobishness for forgetting about noautocmd!

@starcraftman I have tried his solution it works. However, as @junegunn stated, it is needed by some plugins, usually to setup some variables.
I still use the variable solution to prevent restoring cursor position.


Height of chart

If the doses administered line is part of chart, then grow the height of component, so chart is big enough.

appears not to be a problem. closing.