[feat] Popup-based:  toggle by v-model

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow DiDi's contributing guide.
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Travis tests have failed
Hey @AmyFoxFN,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: 6

     npm test

><EMAIL_ADDRESS>test /home/travis/build/didi/cube-ui
> npm run unit && npm run codecov

><EMAIL_ADDRESS>unit /home/travis/build/didi/cube-ui
> cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run

(node:4090) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
24 04 2018 08:26:25.173:INFO [karma]: Karma v1.7.1 server started at http://<IP_ADDRESS>:9876/
24 04 2018 08:26:25.177:INFO [launcher]: Launching browser PhantomJS_mobile with unlimited concurrency
24 04 2018 08:26:25.187:INFO [launcher]: Starting browser PhantomJS
24 04 2018 08:26:26.027:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket NoB8VDK3gcy5lKufAAAA with id 62470561
PhantomJS 2.1.1 (Linux 0.0.0) INFO LOG: 'You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html'

  ActionSheet
    ActionSheet.vue
      ✓ use
      ✓ should render correct contents
      ✓ should render correct contents - no data
      ✓ should render correct contents - picker style
      ✓ should trigger events
    ActionSheet API
      ✓ $createActionSheet API

  Button.vue
    ✓ use
    ✓ should render correct contents
    ✓ props
    ✓ events-called
    ✓ events-no-called

  CascadePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when use alias
    ✓ should trigger events
    ✓ should call methods
    ✓ $updateProps
    ✓ should add warn log when single is true

  CheckboxGroup.vue
    ✓ use
    ✓ should render correct contents (horizontal=false)
    ✓ should render correct contents (horizontal=true)
    ✓ should change v-model value

  Checkbox.vue
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  DatePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when configured startColumn and columnCount
    ✓ should render correct contents when configured format
    ✓ should trigger events
    ✓ should call methods
    ✓ $updateProps
    ✓ should add warn log when single is true

  Dialog
    Dialog.vue
      ✓ use
      ✓ should render correct contents - icon
      ✓ should render correct contents - title
      ✓ should render correct contents - alert
      ✓ should render correct contents - confirm
      ✓ should render correct contents - confirmBtn/cancelBtn
      ✓ should trigger events
      ✓ should not trigger events when btn is disabled
    Dialog API
      ✓ $createDialog API

  Drawer
    ✓ use
    ✓ should render correct contents
    ✓ should trigger events

  Form.vue
    ✓ use
    ✓ should render correct contents
    ✓ should validate & reset correctly
    ✓ should validate & reset correctly - async validate
    ✓ should validate correctly - trigger blur
    ✓ should validate correctly - debounce
    ✓ should trigger events

  IndexList
    IndexList.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
      ✓ should trigger pulling-up
      ✓ should trigger pulling-down
      ✓ should fixed title
      ✓ should not have navbar when navbar prop is false
      ✓ run normal when group or item undefined
      ✓ should handle condition of unexpected param

  Input.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not show clear button when no text
    ✓ should show clear button when has text
    ✓ value should be empty when clear button clicked
    ✓ should support more native props
    ✓ should show password eye and work correctly
    ✓ should trigger events

  Loading.vue
    ✓ use
    ✓ should render correct contents - no size
    ✓ should render correct contents - with size

  Picker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when use alias
    ✓ should toggle by change v-model visible
    ✓ should trigger events
    ✓ should refill correct
    ✓ should add warn log when single is true
    ✓ setData when picker is invisible
    ✓ setData when picker is visible

  Popup
    Popup.vue
      ✓ use
      ✓ should render correct contents - no type
      ✓ should render correct contents
      ✓ should toggle by change v-model visible
      ✓ events
    Popup API
      ✓ $createPopup API

  Radio.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - horizontal
    ✓ should toggle v-model value

  Rate.vue
    ✓ use
    ✓ should render correct contents
    ✓ should trigger change event
    ✓ should trigger change event with click

  Scroll
    ✓ use
    ✓ should correct by default
    ✓ should render correct contents
    ✓ should trigger pullingDown
    ✓ should not trigger pullingDown
    ✓ should trigger pullingUp
    ✓ should not trigger pullingUp
    ✓ should trigger click
    ✓ should trigger other events
    ✓ should call correct method

  SegmentPicker
    ✓ use
    ✓ should render correct contents
    ✓ should correct by default
    ✓ should trigger events
    ✓ $updateProps
    ✓ should add warn log when single is true

  Select.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - update txt
    ✓ should trigger events

  Slide.vue
    ✓ use
    ✓ should render correct contents
    ✓ should clone nodes if loop is true
    ✓ should trigger change event
    ✓ should go to right pageIndex if set initialIndex

  Swipe
    ✓ use
    ✓ should render correct contents
    ✓ should shrink if the swipe width not enough
    ✓ should shrink if the last moving direction is right
    ✓ should shrink and not moved if the duration is more than momentumLimitTime and moving distance is less than momentumLimitDistance
    ✓ should shrink and not moved if y-axis distance is more than x-axis distance
    ✓ should grow if the swipe width enough
    ✓ should grow if the duration is less than momentumLimitTime and moving distance is more than momentumLimitDistance
    ✓ should not swipe out of the boundaries when swiping left
    ✓ should not swipe out of the boundaries when swiping right
    ✓ should trigger events
    ✓ should shrink if another swipe item active
    ✓ should do nothing if active the same swipe item
    ✓ should call refresh if the btns prop has changed
    ✓ should use default props if do not pass any prop

  Switch
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  Textarea.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not expand when blur
    ✓ should expand when focus, fold when blur
    ✓ should has remain when focus
    ✓ should change value
    ✓ should support more native props

  TimePicker
    ✓ use
    ✗ should render correct contents
	AssertionError: expected '0' to equal '-36' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

    ✓ should render correct contents - no showNow
    ✓ should trigger events
    ✓ should add warn log when sigle is true

  Tip.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents with offset[X]
    ✓ should be hidden after clicked content
    ✓ should be hidden after clicked close button

  Toast
    Toast.vue
      ✓ use
      ✓ should render correct contents - no type
      ✓ should render correct contents - time 0
      ✓ should render correct contents - with type
    Toast API
      ✓ $createToast API
      ✓ should trigger correct event

  Upload.vue
    ✓ use
    ✓ should render correct contents
    ✓ should add files & upload
    ✓ should remove file
    ✓ should start & pause upload
    ✓ should retry upload
    ✓ should trigger events

  Validator
    Validator.vue
      ✓ use
      ✓ should render correct contents - invalid
      ✓ should reset correctly
      ✓ should not validate when disabled
      ✓ should trigger events
    rules
      ✓ should be valid - no rule
      ✓ should be valid - unstated rule
      ✓ should be invalid - require: array
      ✓ should be invalid - type: string
      ✓ should be valid - type: string
      ✓ should be invalid - type: number
      ✓ should be valid - type: number
      ✓ should be invalid - type: array
      ✓ should be valid - type: array
      ✓ should be invalid - type: date
      ✓ should be valid - type: date
      ✓ should be invalid - type: email
      ✓ should be valid - type: email
      ✓ should be invalid - type: tel
      ✓ should be valid - type: tel
      ✓ should be invalid - type: url
      ✓ should be valid - type: url
      ✓ should be invalid - min: string
      ✓ should be valid - min: number
      ✓ should be valid - max: string
      ✓ should be invalid - max: number
      ✓ should be valid - len: string
      ✓ should be invalid - len: number
      ✓ should be invalid - notWhitespace
      ✓ should be invalid - pattern
      ✓ should be invalid - custom
    methods
      ✓ should add customized rule and message
      ✓ should rewrite raw type
      ✓ should change the language of default message

PhantomJS 2.1.1 (Linux 0.0.0): Executed 202 of 202 (1 FAILED) (35.335 secs / NaN secs)
TOTAL: 1 FAILED, 201 SUCCESS

1) should render correct contents
     TimePicker
     AssertionError: expected '0' to equal '-36' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

=============================== Coverage summary ===============================
Statements   : 92.96% ( 2205/2372 )
Branches     : 80.28% ( 912/1136 )
Functions    : 90.76% ( 216/238 )
Lines        : 93.02% ( 2199/2364 )
================================================================================

npm ERR! Linux 4.14.12-041412-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.14.1/bin/node" "/home/travis/.nvm/versions/node/v6.14.1/bin/npm" "run" "unit"
npm ERR! node v6.14.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>unit: `cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>unit script 'cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cube-ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cube-ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cube-ui
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/didi/cube-ui/npm-debug.log
npm ERR! Test failed.  See above for more details.

Travis tests have failed
Hey @AmyFoxFN,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: 6

     npm test

><EMAIL_ADDRESS>test /home/travis/build/didi/cube-ui
> npm run unit && npm run codecov

><EMAIL_ADDRESS>unit /home/travis/build/didi/cube-ui
> cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run

(node:4089) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
24 04 2018 09:52:55.474:INFO [karma]: Karma v1.7.1 server started at http://<IP_ADDRESS>:9876/
24 04 2018 09:52:55.477:INFO [launcher]: Launching browser PhantomJS_mobile with unlimited concurrency
24 04 2018 09:52:55.549:INFO [launcher]: Starting browser PhantomJS
24 04 2018 09:52:59.606:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket ZObm0liphbtZPagLAAAA with id 65494223
PhantomJS 2.1.1 (Linux 0.0.0) INFO LOG: 'You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html'

  ActionSheet
    ActionSheet.vue
      ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - no data
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
      ✓ should render correct contents - picker style
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
LOG LOG: 'show'
      ✓ should trigger events
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
LOG LOG: 'show'
    ActionSheet API
      ✓ $createActionSheet API

  Button.vue
    ✓ use
    ✓ should render correct contents
    ✓ props
    ✓ events-called
    ✓ events-no-called

  CascadePicker
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents when use alias
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
    ✓ should trigger events
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
    ✓ should call methods
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ $updateProps
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should add warn log when single is true

  CheckboxGroup.vue
    ✓ use
    ✓ should render correct contents (horizontal=false)
    ✓ should render correct contents (horizontal=true)
    ✓ should change v-model value

  Checkbox.vue
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  DatePicker
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
LOG LOG: 'visible', true
    ✓ should render correct contents when configured startColumn and columnCount
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents when configured format
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
LOG LOG: 'visible', true
    ✓ should trigger events
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
LOG LOG: 'visible', true
    ✓ should call methods
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
LOG LOG: 'visible', true
    ✓ $updateProps
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should add warn log when single is true

  Dialog
    Dialog.vue
      ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - icon
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - title
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - alert
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - confirm
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - confirmBtn/cancelBtn
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
      ✓ should trigger events
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
      ✓ should not trigger events when btn is disabled
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
    Dialog API
      ✓ $createDialog API

  Drawer
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
LOG LOG: 'show'
LOG LOG: 'show'
    ✓ should trigger events

  Form.vue
    ✓ use
    ✓ should render correct contents
    ✓ should validate & reset correctly
    ✓ should validate & reset correctly - async validate
    ✓ should validate correctly - trigger blur
    ✓ should validate correctly - debounce
    ✓ should trigger events

  IndexList
    IndexList.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
      ✓ should trigger pulling-up
      ✓ should trigger pulling-down
      ✓ should fixed title
      ✓ should not have navbar when navbar prop is false
      ✓ run normal when group or item undefined
      ✓ should handle condition of unexpected param

  Input.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not show clear button when no text
    ✓ should show clear button when has text
    ✓ value should be empty when clear button clicked
    ✓ should support more native props
    ✓ should show password eye and work correctly
    ✓ should trigger events

  Loading.vue
    ✓ use
    ✓ should render correct contents - no size
    ✓ should render correct contents - with size

  Picker
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
    ✓ should render correct contents when use alias
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', true
LOG LOG: 'picker show:', false
LOG LOG: 'picker isVisible', true
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', false
LOG LOG: 'visible', false
    ✗ should toggle by change v-model visible
	AssertionError: expected spy to have been called exactly once, but it was called twice
	    spy(true) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23
	    spy(false) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23 (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'picker show:', false
    ✓ should trigger events
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
    ✓ should refill correct
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
    ✓ should add warn log when single is true
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
    ✓ setData when picker is invisible
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
    ✓ setData when picker is visible
LOG LOG: 'visible', false

  Popup
    Popup.vue
      ✓ use
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - no type
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
      ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', false
      ✗ should toggle by change v-model visible
	AssertionError: expected spy to have been called exactly once, but it was called twice
	    spy(true) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23
	    spy(false) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23 (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

LOG LOG: false
LOG LOG: 'visible', false
      ✓ events
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'show'
    Popup API
      ✓ $createPopup API

  Radio.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - horizontal
    ✓ should toggle v-model value

  Rate.vue
    ✓ use
    ✓ should render correct contents
    ✓ should trigger change event
    ✓ should trigger change event with click

  Scroll
    ✓ use
    ✓ should correct by default
    ✓ should render correct contents
    ✓ should trigger pullingDown
    ✓ should not trigger pullingDown
    ✓ should trigger pullingUp
    ✓ should not trigger pullingUp
    ✓ should trigger click
    ✓ should trigger other events
    ✓ should call correct method

  SegmentPicker
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should correct by default
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'picker show:', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', false
LOG LOG: 'visible', true
LOG LOG: 'show'
    ✓ should trigger events
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ $updateProps
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should add warn log when single is true

  Select.vue
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
    ✓ should render correct contents - update txt
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
    ✓ should trigger events
LOG LOG: 'visible', false

  Slide.vue
    ✓ use
    ✓ should render correct contents
    ✓ should clone nodes if loop is true
    ✓ should trigger change event
    ✓ should go to right pageIndex if set initialIndex

  Swipe
    ✓ use
    ✓ should render correct contents
    ✓ should shrink if the swipe width not enough
    ✓ should shrink if the last moving direction is right
    ✓ should shrink and not moved if the duration is more than momentumLimitTime and moving distance is less than momentumLimitDistance
    ✓ should shrink and not moved if y-axis distance is more than x-axis distance
    ✓ should grow if the swipe width enough
    ✓ should grow if the duration is less than momentumLimitTime and moving distance is more than momentumLimitDistance
    ✓ should not swipe out of the boundaries when swiping left
    ✓ should not swipe out of the boundaries when swiping right
    ✓ should trigger events
    ✓ should shrink if another swipe item active
    ✓ should do nothing if active the same swipe item
    ✓ should call refresh if the btns prop has changed
    ✓ should use default props if do not pass any prop

  Switch
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  Textarea.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not expand when blur
    ✓ should expand when focus, fold when blur
    ✓ should has remain when focus
    ✓ should change value
    ✓ should support more native props

  TimePicker
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
LOG LOG: 'visible', false
LOG LOG: 'visible', false
    ✗ should render correct contents
	AssertionError: expected '0' to equal '-36' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
    ✓ should render correct contents - no showNow
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker show:', false
LOG LOG: 'visible', true
LOG LOG: 'show'
LOG LOG: 'visible', true
LOG LOG: 'picker show:', true
LOG LOG: 'visible', false
LOG LOG: 'visible', false
    ✓ should trigger events
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: 'picker isVisible', false
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should add warn log when sigle is true

  Tip.vue
    ✓ use
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should render correct contents with offset[X]
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should be hidden after clicked content
LOG LOG: false
LOG LOG: 'visible', false
    ✓ should be hidden after clicked close button

  Toast
    Toast.vue
      ✓ use
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - no type
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - time 0
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should render correct contents - with type
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
    Toast API
      ✓ $createToast API
LOG LOG: false
LOG LOG: 'visible', false
LOG LOG: false
LOG LOG: 'visible', false
      ✓ should trigger correct event

  Upload.vue
    ✓ use
    ✓ should render correct contents
    ✓ should add files & upload
    ✓ should remove file
    ✓ should start & pause upload
    ✓ should retry upload
    ✓ should trigger events

  Validator
    Validator.vue
      ✓ use
      ✓ should render correct contents - invalid
      ✓ should reset correctly
      ✓ should not validate when disabled
      ✓ should trigger events
    rules
      ✓ should be valid - no rule
      ✓ should be valid - unstated rule
      ✓ should be invalid - require: array
      ✓ should be invalid - type: string
      ✓ should be valid - type: string
      ✓ should be invalid - type: number
      ✓ should be valid - type: number
      ✓ should be invalid - type: array
      ✓ should be valid - type: array
      ✓ should be invalid - type: date
      ✓ should be valid - type: date
      ✓ should be invalid - type: email
      ✓ should be valid - type: email
      ✓ should be invalid - type: tel
      ✓ should be valid - type: tel
      ✓ should be invalid - type: url
      ✓ should be valid - type: url
      ✓ should be invalid - min: string
      ✓ should be valid - min: number
      ✓ should be valid - max: string
      ✓ should be invalid - max: number
      ✓ should be valid - len: string
      ✓ should be invalid - len: number
      ✓ should be invalid - notWhitespace
      ✓ should be invalid - pattern
      ✓ should be invalid - custom
    methods
      ✓ should add customized rule and message
      ✓ should rewrite raw type
      ✓ should change the language of default message

PhantomJS 2.1.1 (Linux 0.0.0): Executed 202 of 202 (3 FAILED) (35.613 secs / NaN secs)
TOTAL: 3 FAILED, 199 SUCCESS

1) should toggle by change v-model visible
     Picker
     AssertionError: expected spy to have been called exactly once, but it was called twice
    spy(true) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23
    spy(false) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23 (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

2) should toggle by change v-model visible
     Popup Popup.vue
     AssertionError: expected spy to have been called exactly once, but it was called twice
    spy(true) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23
    spy(false) at $emit@webpack:///node_modules/vue/dist/vue.esm.js:2538:0 <- index.js:3007:23 (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

3) should render correct contents
     TimePicker
     AssertionError: expected '0' to equal '-36' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

=============================== Coverage summary ===============================
Statements   : 93.25% ( 2211/2371 )
Branches     : 80.75% ( 906/1122 )
Functions    : 93.53% ( 217/232 )
Lines        : 93.31% ( 2205/2363 )
================================================================================

npm ERR! Linux 4.14.12-041412-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.14.1/bin/node" "/home/travis/.nvm/versions/node/v6.14.1/bin/npm" "run" "unit"
npm ERR! node v6.14.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>unit: `cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>unit script 'cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cube-ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cube-ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cube-ui
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/didi/cube-ui/npm-debug.log
npm ERR! Test failed.  See above for more details.

Travis tests have failed
Hey @AmyFoxFN,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: 6

     npm test

><EMAIL_ADDRESS>test /home/travis/build/didi/cube-ui
> npm run unit && npm run codecov

><EMAIL_ADDRESS>unit /home/travis/build/didi/cube-ui
> cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run

(node:4087) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
25 04 2018 08:43:00.192:INFO [karma]: Karma v1.7.1 server started at http://<IP_ADDRESS>:9876/
25 04 2018 08:43:00.195:INFO [launcher]: Launching browser PhantomJS_mobile with unlimited concurrency
25 04 2018 08:43:00.205:INFO [launcher]: Starting browser PhantomJS
25 04 2018 08:43:01.250:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket rB9ttKrc73xH9-xvAAAA with id 2888757
PhantomJS 2.1.1 (Linux 0.0.0) INFO LOG: 'You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html'

  ActionSheet
    ActionSheet.vue
      ✓ use
      ✓ should render correct contents
      ✓ should render correct contents - no data
      ✓ should render correct contents - picker style
      ✓ should trigger events
    ActionSheet API
      ✓ $createActionSheet API

  Button.vue
    ✓ use
    ✓ should render correct contents
    ✓ props
    ✓ events-called
    ✓ events-no-called

  CascadePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when use alias
    ✓ should trigger events
    ✓ should call methods
    ✓ $updateProps
    ✓ should add warn log when single is true

  CheckboxGroup.vue
    ✓ use
    ✓ should render correct contents (horizontal=false)
    ✓ should render correct contents (horizontal=true)
    ✓ should change v-model value

  Checkbox.vue
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  DatePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when configured startColumn and columnCount
    ✓ should render correct contents when configured format
    ✓ should trigger events
    ✓ should call methods
    ✓ $updateProps
    ✓ should add warn log when single is true

  Dialog
    Dialog.vue
      ✓ use
      ✓ should render correct contents - icon
      ✓ should render correct contents - title
      ✓ should render correct contents - alert
      ✓ should render correct contents - confirm
      ✓ should render correct contents - confirmBtn/cancelBtn
      ✓ should trigger events
      ✓ should not trigger events when btn is disabled
    Dialog API
      ✓ $createDialog API

  Drawer
    ✓ use
    ✓ should render correct contents
    ✓ should trigger events

  Form.vue
    ✓ use
    ✓ should render correct contents
    ✓ should validate & reset correctly
    ✓ should validate & reset correctly - async validate
    ✓ should validate correctly - trigger blur
    ✓ should validate correctly - debounce
    ✓ should trigger events

  IndexList
    IndexList.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
      ✓ should trigger pulling-up
      ✓ should trigger pulling-down
      ✓ should fixed title
      ✓ should not have navbar when navbar prop is false
      ✓ run normal when group or item undefined
      ✓ should handle condition of unexpected param

  Input.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not show clear button when no text
    ✓ should show clear button when has text
    ✓ value should be empty when clear button clicked
    ✓ should support more native props
    ✓ should show password eye and work correctly
    ✓ should trigger events

  Loading.vue
    ✓ use
    ✓ should render correct contents - no size
    ✓ should render correct contents - with size

  Picker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents when use alias
    ✓ should toggle by change v-model visible
    ✓ should trigger events
    ✓ should refill correct
    ✓ should add warn log when single is true
    ✓ setData when picker is invisible
    ✓ setData when picker is visible

  Popup
    Popup.vue
      ✓ use
      ✓ should render correct contents - no type
      ✓ should render correct contents
      ✓ should toggle by change v-model visible
      ✓ events
    Popup API
      ✓ $createPopup API

  Radio.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - horizontal
    ✓ should toggle v-model value

  Rate.vue
    ✓ use
    ✓ should render correct contents
    ✓ should trigger change event
    ✓ should trigger change event with click

  Scroll
    ✓ use
    ✓ should correct by default
    ✓ should render correct contents
    ✓ should trigger pullingDown
    ✓ should not trigger pullingDown
    ✓ should trigger pullingUp
    ✓ should not trigger pullingUp
    ✓ should trigger click
    ✓ should trigger other events
    ✓ should call correct method

  SegmentPicker
    ✓ use
    ✓ should render correct contents
    ✓ should correct by default
    ✓ should trigger events
    ✓ $updateProps
    ✓ should add warn log when single is true

  Select.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - update txt
    ✓ should trigger events

  Slide.vue
    ✓ use
    ✓ should render correct contents
    ✓ should clone nodes if loop is true
    ✓ should trigger change event
    ✓ should go to right pageIndex if set initialIndex

  Swipe
    ✓ use
    ✓ should render correct contents
    ✓ should shrink if the swipe width not enough
    ✓ should shrink if the last moving direction is right
    ✓ should shrink and not moved if the duration is more than momentumLimitTime and moving distance is less than momentumLimitDistance
    ✓ should shrink and not moved if y-axis distance is more than x-axis distance
    ✓ should grow if the swipe width enough
    ✓ should grow if the duration is less than momentumLimitTime and moving distance is more than momentumLimitDistance
    ✓ should not swipe out of the boundaries when swiping left
    ✓ should not swipe out of the boundaries when swiping right
    ✓ should trigger events
    ✓ should shrink if another swipe item active
    ✓ should do nothing if active the same swipe item
    ✓ should call refresh if the btns prop has changed
    ✓ should use default props if do not pass any prop

  Switch
    ✓ use
    ✓ should render correct contents
    ✓ should toggle v-model value

  Textarea.vue
    ✓ use
    ✓ should render correct contents
    ✓ should not expand when blur
    ✓ should expand when focus, fold when blur
    ✓ should has remain when focus
    ✓ should change value
    ✓ should support more native props

  TimePicker
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - no showNow
    ✓ should trigger events
    ✓ should add warn log when sigle is true

  Tip.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents with offset[X]
    ✓ should be hidden after clicked content
    ✓ should be hidden after clicked close button

  Toast
    Toast.vue
      ✓ use
      ✓ should render correct contents - no type
      ✓ should render correct contents - time 0
      ✓ should render correct contents - with type
    Toast API
      ✓ $createToast API
      ✓ should trigger correct event

  Upload.vue
    ✓ use
    ✓ should render correct contents
    ✓ should add files & upload
    ✓ should remove file
    ✓ should start & pause upload
    ✓ should retry upload
    ✓ should trigger events

  Validator
    Validator.vue
      ✓ use
      ✗ should render correct contents - invalid
	AssertionError: expected 'cube-validator cube-validator_validating' to include 'cube-validator_invalid' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

      ✓ should reset correctly
      ✓ should not validate when disabled
ERROR LOG: '[Vue warn]: Error in nextTick: "AssertionError: expected 'cube-validator' to include 'cube-validator_validating'"

found in

---> <CubeValidator> at /home/travis/build/didi/cube-ui/src/components/validator/validator.vue
       <Root>'
ERROR LOG: AssertionError{message: 'expected 'cube-validator' to include 'cube-validator_validating'', showDiff: false, actual: 'cube-validator', expected: undefined, stack: undefined, line: 210, sourceURL: 'http://localhost:9876/absolute/home/travis/build/didi/cube-ui/node_modules/chai/chai.js?ab7cf506d9d77c111c878b1e10b7f25348630760'}
      ✗ should trigger events
	AssertionError: expected 'cube-validator cube-validator_invalid' to include 'cube-validator_valid' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

    rules
      ✓ should be valid - no rule
      ✓ should be valid - unstated rule
      ✓ should be invalid - require: array
      ✓ should be invalid - type: string
      ✓ should be valid - type: string
      ✓ should be invalid - type: number
      ✓ should be valid - type: number
      ✓ should be invalid - type: array
      ✓ should be valid - type: array
      ✓ should be invalid - type: date
      ✓ should be valid - type: date
      ✓ should be invalid - type: email
      ✓ should be valid - type: email
      ✓ should be invalid - type: tel
      ✓ should be valid - type: tel
      ✓ should be invalid - type: url
      ✓ should be valid - type: url
      ✓ should be invalid - min: string
      ✓ should be valid - min: number
      ✓ should be valid - max: string
      ✓ should be invalid - max: number
      ✓ should be valid - len: string
      ✓ should be invalid - len: number
      ✓ should be invalid - notWhitespace
      ✓ should be invalid - pattern
      ✓ should be invalid - custom
    methods
      ✓ should add customized rule and message
      ✓ should rewrite raw type
      ✓ should change the language of default message

PhantomJS 2.1.1 (Linux 0.0.0): Executed 202 of 202 (2 FAILED) (34.836 secs / NaN secs)
TOTAL: 2 FAILED, 200 SUCCESS

1) should render correct contents - invalid
     Validator Validator.vue
     AssertionError: expected 'cube-validator cube-validator_validating' to include 'cube-validator_invalid' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

2) should trigger events
     Validator Validator.vue
     AssertionError: expected 'cube-validator cube-validator_invalid' to include 'cube-validator_valid' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

=============================== Coverage summary ===============================
Statements   : 95.37% ( 2243/2352 )
Branches     : 82.85% ( 923/1114 )
Functions    : 95.24% ( 220/231 )
Lines        : 95.44% ( 2237/2344 )
================================================================================
PhantomJS 2.1.1 (Linux 0.0.0) ERROR
  TypeError: null is not an object (evaluating 'vm.validating')
  at webpack:///test/unit/specs/validator.spec.js:185:8 <- index.js:119279

PhantomJS 2.1.1 (Linux 0.0.0): Executed 202 of 202 (2 FAILED) ERROR (35.232 secs / NaN secs)

=============================== Coverage summary ===============================
Statements   : 95.37% ( 2243/2352 )
Branches     : 82.85% ( 923/1114 )
Functions    : 95.24% ( 220/231 )
Lines        : 95.44% ( 2237/2344 )
================================================================================

npm ERR! Linux 4.14.12-041412-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.14.1/bin/node" "/home/travis/.nvm/versions/node/v6.14.1/bin/npm" "run" "unit"
npm ERR! node v6.14.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>unit: `cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>unit script 'cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cube-ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cube-ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cube-ui
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/didi/cube-ui/npm-debug.log
npm ERR! Test failed.  See above for more details.


Add release notes for v20.2.0-beta.3

Fixes #7981.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f1bcf4bb7f41292e10f822d75f427667661920f0/
Edited pages:

releases/v20.2.0-beta.3.md

Hey Eric! if you could review in the next 24 hours that would be great!  but if you can’t let me know, not a problem - i will ask someone else

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/80a7559f71aa86468752525493ed78bea8c26462/
Edited pages:

releases/v20.2.0-beta.3.md


BUG: Error creating NodePool while deploying on GKE

Description
Hi 👋
I am running ./src/deploy.sh and have configured the GCP Project credentials and the config.json already. I am running into this error due to which I was not able to deploy the BinderHub on GKE:
google_container_node_pool.primary_node_pool: Creating...
╷
│ Warning: Version constraints inside provider configuration blocks are deprecated
│
│   on main.tf line 12, in provider "google":
│   12:     version     = "3.46.0"
│
│ Terraform 0.13 and earlier allowed provider version constraints inside the provider configuration block, but that is now
│ deprecated and will be removed in a future version of Terraform. To silence this warning, move the provider version constraint
│ into the required_providers block.
╵
╷
│ Error: error creating NodePool: googleapi: Error 400: Auto_repair cannot be false when release_channel REGULAR is set., badRequest
│
│   with google_container_node_pool.primary_node_pool,
│   on main.tf line 40, in resource "google_container_node_pool" "primary_node_pool":
│   40: resource "google_container_node_pool" "primary_node_pool" {
│

I would be highly obliged if this can be fixed to automate the deployment (Thanks for this project!).

cc: @sgibson91

Thanks for the bug report! I'll try to get to it as soon as I can, but I am the only active maintainer of this project just so you're aware :)

Hi @sgibson91
I followed this commit to fix this error: https://github.com/melbourne-cdth/binderhub-deploy-gke/commit/9568b8528ef05878a9075c88d29226e66ed91417
The setup seems to work properly and I'm getting a few errors just around the gcloud which I will fix myself.


A full example of how to use NumericMenuItem

Is there any full simple example of how to use NumericMenuItem? I'm getting a little lost in the coding for being able to use prev and next methods to change the values. Basically I'd like to see an example that has a single  numeric menu item and then be able to change the value of the fields once it is selected. The comments in the code refer to having to set  _has_focus in sub classes but I'm not creating any sub classes. Does selecting the menu item by definition put it into focus and when you go back puts it out of focus?
Any help appreciated. Thanks

Going to close this. Found what i needed in serial-nav example and after looking at your implementation all makes sense now. Very nice design. Used composite design techniques over 35 years ago. Nice to see it still in practice.


Improve JSONPostTests by using jdi-dark Service Object's methods.

Same as https://github.com/jdi-testing/jdi-dark/issues/208

Demo has been done.


Escape class names

When an element has class names starting with number, the Element.matches is failing to identify the right element.

Ex: div.classA.2f683ff1c2173060crd67792e542ss17
Expected: Should identify element with classA and 2f683ff1c2173060crd67792e542ss17 as classes
Actual: Element.matches throws Error as it is invalid id
@Georgegriff Let me know your thoughts on this

https://stackoverflow.com/questions/21227702/is-there-a-workaround-to-make-css-classes-with-names-that-start-with-numbers-val according to this you need to escape the first digit for it to be a valid query selector

Closing, package moving to new owner


Error Plugin_not_installed

After creating a new app ionic2 , and add this plugin , in Android ionic-native does not find the plugin and asks to install, but does not work.

Probably duplicate of #95


Large arbitrary block of data

Hi!
I would like to transfer a large arbitrary block data to the device, chunk by chunk, since it can't fit all at once inside device RAM memory. Currently, I think, SCPI_ParamArbitraryBlock expects whole block to be inside the memory. Is there any other strategy to do this?
For the other way around, when I need to transfer large arbitrary block from device, I can use SCPI_ResultArbitraryBlockHeader and then SCPI_ResultArbitraryBlockData multiple times and it works fantastic!
For the context, let me tell you that I transfer data from PC to the SD card on the device, and vice versa.

I just figured out one strategy to do this. I will send one chunk of data with one SCPI command, i.e. each chunk will be different SCPI command.
For example, to transfer file from PC to device, I will do the following:
MMEMory:DOWNload:FNAMe "/lists/sin.csv"
MMEMory:DOWNload:DATA #264.... // send 1st 64 bytes
MMEMory:DOWNload:DATA #264.... // send 2nd 64 bytes
...

Hi!
See this post: https://github.com/j123b567/scpi-parser/issues/80

This is good workaround.
Current library design dos not support messages larger then the buffer. This is also the reason, I can't support indefinite format of arbitrary data, see issue #24.
Another approach would be, to add another API to the library. User will define user handler just for

detection of command header
detection of parameter, it can be called multiple times for one ARB parameter
detection of end of command

Detection of correct command will be on responsibility of the user of the library.
This is how another parsers works e.g. https://github.com/nodejs/http-parser

I think I can live with the workaround. Thanks!


Feature/multiple transports doc

Adding documentation for multiple transports feature

Moved feature to sdl_core_guides. https://github.com/smartdevicelink/sdl_core_guides/pull/50


Indices end index is 1 less than expected value.

I wanted to use the indices from the match object to format the matched text such as:
text: Hey
indices: [0,1]

Output:
Hey
However, the indices returned by fuse have the start and end match on the same character.
You can see this on the Fuse.js demo page:
Simply type o into the search and it returns [0,0] for indices as it matches 'O' in the 'Old Man's War'
[
  {
    "item": {
      "title": "Old Man's War",
      "author": {
        "firstName": "John",
        "lastName": "Scalzi"
      }
    },
    "matches": [
      {
        "indices": [
          [
            0,
            0
          ]
        ],
        "key": "title"
      },
...

Expected Result:
[0,1]
I feel like this would be obvious to be a bug so perhaps it's by design but can someone help me understand how it's intended to be used to highlight text this way?
All the string operations such as slice, substr and substring would use 0, 1 not 0, 0 to get the matched characters so I ended up manually adding 1 to all the end indices to make them useful and this seems odd.

I just started using this library, but I think this is because character positions are numbered by the place where the cursor is, which is right before the character. So the correct start and end position of the matched char 'o' would be [0, 0], indicating that only that character was matched. If the result said [0,1], that would imply that the next character was matched as well.
You're right that in order to highlight it you'd have to increase the end value by one. This essentially means "highlight the string starting with the character at position [0] until you reach the character at position [1]"

I think this is because character positions are numbered by the place where the cursor is, which is right before the character

I don't understand how cursors are related here.  I assumed (maybe incorrectly) that the library is primarily used for searching through items so your cursor would be following the search text and not related to the matching indicies which may be split up into separate groups even though search term is single string.
If you select the first character in a text block and return the selection object you get:

Which has 0 and 1 for offsets.
I've seen other libraries report indices using this manner of each character being index instead of the spaces between/around.  I can easily see both ways; however, one does seem more useful than the other for consumers.  From perspective of library author maybe internally simplifies logic, but for consumers you pass complexity on to them to always increment the last index for any use.
That all being said, I assume it's probably too late to make breaking change for this library anyway.  Perhaps in future it could be an option when you configure Fuse object.

I don't understand how cursors are related here.

I only mentioned the cursor position because that is the anchorOffset when the selection range is collapsed. It was a poorly worded explanation I suppose.

I'm only making assumptions here since I have no connection to the library besides using it. But my guess is that you're right and the main purpose of this library is not highlighting found searches. Since it uses a Bitap implementation of the Levenshtein distance we can also target spell checkers, OCR, etc.
Here's a contrived example. Suppose I wanted to fuzzy search and highlight OCR mistakes. Let's use "Old men" as the incorrect rendition, and "Old man" as the correct term. Using your proposed indices we'd end up with matches like so:
"matches": [
      {
        "indices": [
          [ 0, 5 ],
          [ 6, 7 ]
          ],
          [ 9, 10 ]
        ],

Now the consumer would have to implement weird logic to highlight the character at index 5 ("e") as the incorrect character (should be "a"). Also imagine how another dev would feel in a few months tracking down a bug wondering why indices 0-7 are matches, but only index 5 is highlighted as incorrect.
By keeping the indices to only the matching indices we get
"matches": [
      {
        "indices": [
          [ 0, 4 ],
          [ 6, 6 ]
          ],
          [ 9, 9 ]
        ],

It's now clear where the edit distance is, and makes it much easier to target incorrect characters, with the only drawback of increasing the end index in order to highlight. I don't know if this was the author's intent, but this is how I made sense of it (like you I was also confused as to why).


feature: Generic trackers support

An ability to track positions of generic trackers
The setup scene to bind trackers to hip / left foot / right foot by its device serial number (and to save it to JSON config)

This functionality provided by Vive Input Utility plugin, but it's difficult to make it work along with VRTK, because it has its own ViveCameraRig, connected to player, not to SDKManager.

You don't need to use the Vive Input Utility for tracker support, they're just another steamvr tracked object
https://youtu.be/p1u25WF0SWA?list=PLTiD-q2AfVNKwI9Wim5f-ge_Ucf7GjhVo&t=1691

HTC Vive input utility is providing bespoke solutions for a bespoke device. Vrtk tends not to support specific devices in a bespoke way. If you can come up with another way of supporting the tracker and potential future trackers in a generic way then I'd love to hear it


Resource file not found error when loading Favorite icon

The order of two arguments were flipped in recently merged #77932. If you had any favorites in the file dock, you would get ERROR: Resource file not found: res://PackedScene (expected type: )  cc: @KoBeWi.

Maybe don't merge this until #89646 is resolved.

How is this related to that issue? Does removing the error make it even slower?

How is this related to that issue? Does removing the error make it even slower?

There is no slowdown at all until you apply this fix. The error means that no scene files are loaded for the favorites, which is what is causing the slowdown as far as I can tell.

Pushed an update. This PR now fixes:

Flipped argument order causing error message.
Slowdown caused by trying to load an entire scene as an icon.
Custom icons were not shown if you run the file dock in split mode.

Thanks!


Several updates

Raised MSRV to 1.46.0 due to nix
Updated nix
Renamed use_tokio feature async-tokio like in gpio-cdev. (The word "use" is discouraged in feature names: C-FEATURE)
Fixed docs link
Use GHA for CI instead of Travis (tested on my fork)
Added embedded-linux team to authors

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ryankurte (or someone else) soon.
Please see the contribution instructions for more information.

bors try

Sounds good. I will add that in a separate PR, thanks!


Transform AMD modules to ES2015 modules

Same task for laxar-patterns as in LaxarJS/laxar#246, thus simply copied:
In a first step to nicer code in ES2015 syntax and in order to get rid of AMD module syntax, all modules should be transformed to ES2015 modules. Other ES2015 transforms can be applied in a later step.

Breaking Changes:

Currently a globally installed jspm-cli is required (this will change at latest before the first beta). So be sure to run npm install -g jspm for now.
Modules are now ES2015 module syntax. Thus, when using the sources directly make sure your environment supports loading ES2015 modules.

Implemented on master(v2.0.0).


implement make_transformer()

This function / feature should enable users to wrap any function into our Transformer with fit() and transform() functions.
(sklearn/func -> transformer conversion)
it accepts: sklearn transformer, regressor, classificator
and single def as well.

merged in #50 . closing this.


DAO contracts labels + ownership tests

This PR refactors the DaoContracts struct and adds tests for the labels naming convention introduced in the corresponding PR to the Neutron repo. Also adds several ownership tests.
PR to Neutron: https://github.com/neutron-org/neutron/pull/224

https://github.com/neutron-org/neutron-tests/actions/runs/4854771617


Add select team function

Summary
This PR implements the ability to switch between teams and manage the current team context.
Features

Team selection dropdown UI
Current team state management
Integration with team creation modal

Technical Details

Implemented TeamSelection component for managing team switching
Uses server-side data fetching for teams list
Maintains current team context across sessions

Testing

[ ] Switch between existing teams
[ ] Verify current team persists after page refresh
[ ] Confirm team creation modal integration

TODO

[ ] Add COOKIE_SECRET to Vercel environment value: Preview, Development
[ ] Add COOKIE_SECRET to Vercel environment value: Production

I'm hitting these issues 😓

https://github.com/shadcn-ui/ui/issues/2487
https://github.com/shadcn-ui/ui/issues/1859
https://github.com/radix-ui/primitives/issues/1241

I'll try a bit more, but if it doesn't work, I'll put it on hold for now.


Update offset on resize? [Potential bug]

When calling scroller.resize(), there should be a way to update the offset.
const scroller = scrollama()

function init () {
  scroller
    .setup({
      step: '#...,
      offset: midpoint + 'px',
      debug: true
    })
    .onStepEnter(...)

  window.addEventListener('resize', handleResize)

}

function handleResize () {
  scroller
    .setup({
      step: '...',
      offset: newMidpoint + 'px',
      debug: true
    })
    .onStepEnter(e => handleStepEnter(e, callbacks))

  scroller.resize()
}

This results in many offsets seemingly being set :

A potential solution could be to pass the new offset as param to the .resize() function.

There is a method for this, so you could chain them together or call one after the other. Assuming that is what you are looking for?

There is a method for this, so you could chain them together or call one after the other. Assuming that is what you are looking for?

Yes, wonderful, sorry about that & thanks for the great lib.

Yes, wonderful, sorry about that & thanks for the great lib.


x/build: update the rc1 announcement template to mention min gopls version and telemetry

For the go1.23rc1 release announcement, we want to:

Highlight the version of gopls required to use new language features (in this case, this will be<EMAIL_ADDRESS>or gopls@v0.16.0-pre.1).
Ask users to opt-in to telemetry to help improve our releases.

@dmitshur suggests that the easiest way to do this may be to modify the announcement template at
https://cs.opensource.google/go/x/build/+/master:internal/task/template/announce-rc.md;drc=59c99abb1cb61040972a82e0e4ba4f61a95ac34e
For this release, we could guard these additions with {{if eq .Version "go1.23rc1"}}, but in fact we may want to include both of these features in all future release candidate announcements. It seems like it may always be worthwhile to inform users which gopls version is required to work with new language features, and to ask them to enable telemetry so that we can collect more information about the release candidate.
CC @dmitshur @joedian @rsc

I'm not yet closing this issue with the above CL, because depending on whether we land<EMAIL_ADDRESS>we may want to also suggest using<EMAIL_ADDRESS>If we are able to release gopls prior to the RC, no such addition is necessary, since most users are auto-updated to the latest gopls version.

This is marked as a release blocker, is open, is not marked okay-after-RC1, and the scheduled cut for 1.23RC1 is roughly 24 hours from now. Where do we stand on this?


Refactor fruits.create to use async await

@rpancham can you please send a PR for this?
https://github.com/nodeshift-starters/nodejs-rest-http-crud/blob/opentel/lib/routes/fruits.js#L34-L43

PR merged https://github.com/nodeshift-starters/nodejs-rest-http-crud/pull/312


Fix Windows Event Log channel isolation semantics

Remove isolation attribute from Analytic and Debug channels. These channel types always have an isolation of Custom, regardless of what is put here in the manifest.
Since no events are being written to the Admin channel currently, remove it. This avoids the Windows Event Log pre-allocating a file for the channel.
PR Summary
Avoid setting incorrect values in the ETW manifest that get silently ignored by mc/wevtutil.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

Reopen The PR to restart CI Appveyor.

@dantraMSFT Please update your review.

@Robo210 Thanks for your contribution!


Add a page of successfully submission of the information.

Please assign me this issue.

@tjanhvi this issue is already open https://github.com/QAZIMAAZARSHAD/Voters-Registration-Portal/issues/5.
Before opening any issue always make sure that no other similar issue is open.


Remote Desktop Input failed & message box issue

When on remote desktop I cannot control mouse or keyboard input properly. The mouse will move however any button clicking or scrolling will not result in anything. The keyboard is the same.

Please follow the bug reporting guidelines: https://github.com/quasar/Quasar/issues/new?template=bug_report.md


⚠ Bofrost.lu has degraded performance

In d9d9c20, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 960 ms

Resolved: Bofrost.lu performance has improved in 0a4fb3e after 6 minutes.


SWARM-1693 [REV-2] - Microprofile + OpenAPI 1.0.1 spec implementation (fraction)

[x] Have you followed the guidelines in our Contributing document?
[x] Have you created a JIRA and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install? really this time

Ok it failed on Linux here too.
Will send a PR to see how it goes on Monday

Hi @EricWittmann I've sent you a possible fix for this: https://github.com/EricWittmann/wildfly-swarm/pull/2 . Can you check if it's enough?
Thanks!

I'll test it locally certainly.  But note that the build has never failed for me locally the way it has on CI and for others (e.g. @msavy ).  So if it passes my local build shall I push it to the PR branch so it can be tested on CI?

Hi @EricWittmann . Yes please, as that is the failing environment. If it passes, maybe I should make the PR properly with a right SWARM JIRA ticket.

OK everything worked locally.  I have pushed the commit to the PR branch.  Should be retesting now.

Ok @EricWittmann fingers crossed

Oh it fails on windows...

@EricWittmann, can https://github.com/wildfly-swarm/wildfly-swarm/pull/810 be closed as out of date?
@juangon, @mkouba, @michalszynkiewicz, @sberyozkin, @heiko-braun - I want this reviewed by a couple of people Tuesday morning, as it's lots of code, so that we can put it to bed and do the 2018.3.1 release to include it.
We can always revisit the Windows temp file issue later

@kenfinnigan will try to reproduce locally on Windows. If can't find a fix, I can send a PR for disabling temp file check for this test also

@juangon Hm, this time it failed in arquillian-test and not in OpenAPI TCK.
@kenfinnigan I already spent some time with this PR and I think it's good to go.

So this is getting interesting. I could reproduce the failure on Windows, but after some attempts couldn't make it work (file is still locked by Windows at that time).
And then I returned to the original failure in openapi TCK without my suggested fix. And in my windows env it works!! Maybe we should re-run CI tests for the original PR

@kenfinnigan Yes 810 is out of date.  This one supersedes it.  So other than @juangon's suggestion to retest #810 I can think of no reason not to close it.


(c-r v0.2.0) *: update CRD manifest file names to __crd.yaml

Description of the change: CRD manifest name changes from #1642.
Motivation for the change:

Depends on #1696 being merged into refactor branch.


Include ticks in countTimers

We understand you have a problem and are in a hurry, but please provide us with some info to make it much more likely for your issue to be understood, worked on and resolved quickly.

Lolex version : 4.0.1
Environment   : Node 10
Example URL   : N/A
Other libraries you are using: N/A

What did you expect to happen?
See https://github.com/facebook/jest/pull/8139 for justification. Tl;dr; is that a timer count should include all scheduled timers and friends, not just timers.
What actually happens
clock.nextTick does not contribute to the count
How to reproduce
const lolex = require("lolex");

const clock = lolex.createClock();

clock.setTimeout(() => {}, 5);
clock.nextTick(() => {});

console.log(clock.countTimers()); // 1

Sounds reasonable to me and easy to fix


bug: previous page nav bar stays for a while until transition animation finish

hi, I'm trying to use ion-back-button on my nav bar and when I navigate to other pages everything goes fine. but my problem is that when I click on the back button in pushed page after showing prev page, the last pages nav header stays for a while until transition animation finish
is it a bug or if anyone knows how to solve this problem please tell me how to solve it

I had the same problem in iOS mode. Turns out, it was just because you specifically need to specify your ion-toolbar inside your ion-header for the animation to work as expected.

it fixed when I moved my ion-toolbar to pages but is there any way that I can use a general custom component for the header?

I have been struggling with this myself. But as far as I know of, it's not possible. If you want your back animation to work on iOS, that is.
On Android there should be no problems.

I had the same problem in iOS mode. Turns out, it was just because you specifically need to specify your ion-toolbar directly inside your ion-header for the animation to work as expected. You can't put it inside a custom component.

I have been struggling with this myself. But as far as I know of, it's not possible. If you want your back animation to work on iOS, that is.
On Android there should be no problems.

yes it's a challenging bug I think. btw thanks. I hope they fix it soon

Thanks for the issue. I am going to close this as a duplicate of https://github.com/ionic-team/ionic/issues/18130.


error in loading datasets

I was trying to load the wiki dataset, but i got this error
traindata = load_dataset('wikitext', 'wikitext-2-raw-v1', split='train')
File "/home/aelkordy/.conda/envs/prune_llm/lib/python3.9/site-packages/datasets/load.py", line 1804, in load_dataset
ds = builder_instance.as_dataset(split=split, verification_mode=verification_mode, in_memory=keep_in_memory)
File "/home/aelkordy/.conda/envs/prune_llm/lib/python3.9/site-packages/datasets/builder.py", line 1108, in as_dataset
raise NotImplementedError(f"Loading a dataset cached in a {type(self._fs).name} is not supported.")
NotImplementedError: Loading a dataset cached in a LocalFileSystem is not supported.
I got similar error for C4.

Updating datasets should fix the issue.
pip install -U datasets


TestAll seems flaky

--- FAIL: TestAll (0.25s)

	scope_test.go:77: api_topology_test.go:37: Expected status 200, got 404. Path: /api/topology/pods-by-service/container%3A5e4d3c2b1a

https://circleci.com/gh/weaveworks/scope/2739?utm_campaign=build-failed&utm_medium=email&utm_source=notification

https://circleci.com/gh/weaveworks/scope/2742

This is pretty easy to reproduce.  I think it has to be something to do with the merging of renderable nodes.

Based on a couple failing cases with some logging, I am wondering if it is caused by conflicting cache hits.
Reflect.Value.Pointer docs say, "the returned pointer is an underlying code pointer, but not necessarily enough to identify a single function uniquely." Whether that is causing this bug or not, it's certainly a (serious) bug.


Align casing of arguments to lower case

A few arguments use upper case for some reason. As the lower case version 'c' is used often I would recommend simplifying to that one.

This is Panda's API: https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.plot.hexbin.html

Pandas plotting doesn't have a heatmap method so I guess hvPlot's signature was in this case inspired from the hexbin signature. Maybe you could open an issue on Pandas' Github to try to see why they chose C?


Next steps for F*-KreMLin extraction & interaction

[ ] Support for mutually recursive datatypes (cleaning up and merging Jared's work)
[ ] Attributes per binding and not per block of mutually recursive type definitions
[ ] Forward StackInline to KreMLin
[ ] Deprecate [@"substitute"]
[ ] Implement [@ (Const x) ] (and possibly other SAL-like annotations https://msdn.microsoft.com/en-us/library/hh916382.aspx)
[ ] Forward location information to KreMLin
[ ] Forward names for parameters of assumed vals

CC @nikswamy

cc @jroesch

cc @jroesch

Note: KreMLin now recovers from intermediary variables by using a syntactic criterion, meaning that [@"substitute"] can be truly deprecated and the Read effect can be put on the back burner.

Closing... attributes per binding don't seem to be needed, and with_frame seems more complicated than it's worth.


style: missing padding in VizTypeControl on "New Chart" page

Missing some padding in the viz type selector on "Add new chart" page:
Actual results

Expected results
The viz type control should look the same as on Explore page:

Screenshots
See above
How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Environment
(please complete the following information):

superset version: superset version
python version: python --version
node.js version: node -v
npm version: npm -v

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

@@kgabryje 🙏

not sure which pr fixed it, but it's fixed. closing the issue

This issue is back


There is a vulnerability in httpclient 4.5.1 ,upgrade recommended

https://github.com/apache/trafficcontrol/blob/83e5c3ab43b89c18daa26d19192fc819bfcd44c3/traffic_router/neustar/pom.xml#L73-L77
CVE-2020-13956
Recommended upgrade version：4.5.13

Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution.

We configure the URLs that TR makes requests to, and they don't contain malformed authority components in the URIs by default. Therefore, an ATC installation would only be "vulnerable" if they have configured URLs for TR to poll that have malformed authority components, which seems unlikely, because if that were the case then TR wouldn't be functioning properly in those ATC installations. Also, the likelihood that an operator-supplied URL actually includes a malformed authority component that also contains a malicious server seems very unlikely.

Also, @QiAnXinCodeSafe , in case that account isn't a bot and/or is monitored by someone: Opening issues directly for security concerns is discouraged as per our Security Policy - please refrain from publicly announcing vulnerabilities before going through the ASF reporting process


MySQL table columns

Good afternoon! I can't find anywhere what columns in the MySql "Skins" table should be made and what type are they?

Those are generated by the SkinsRestorer plugin: https://github.com/SkinsRestorer/SkinsRestorerX/blob/dev/shared/src/main/java/net/skinsrestorer/shared/storage/MySQL.java#L44-L56


Fix/editorconfig clashes w checkstyle

indent_size entry in seemed to be clashing with certain checkstyle.xml entries
removes/adds a number of of whitespaces/newlines

You can only remove the indent_size for java files, this way it would be still valid for xml, etc.
[*]
...

[!*.java]
indent_size = 2


StackStorm TSC Meetings

When
Every 1st Tuesday of the month, 09:30 AM US Pacific time @StackStorm/TSC members (see OWNERS.md) are gathering for 1 hour to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed.
These meetings are open and we invite others to join them to be up to date with the latest project developments and progress.
Where
Zoom Conference Room: https://us04web.zoom.us/j/966394889
Topic: StackStorm TSC Monthly Meeting

Join Zoom Meeting
https://us02web.zoom.us/j/966394889

Meeting ID: 966 394 889
One tap mobile
+13126266799,,966394889# US (Chicago)
+13462487799,,966394889# US (Houston)

Dial by your location
        +1<PHONE_NUMBER> US (Chicago)
        +1<PHONE_NUMBER> US (Houston)
        +1<PHONE_NUMBER> US (San Jose)
        +1<PHONE_NUMBER> US (New York)
        +1<PHONE_NUMBER> US (San Jose)
        +1<PHONE_NUMBER> US (Tacoma)
        +1<PHONE_NUMBER> US (Germantown)
Find your local number: https://us02web.zoom.us/u/kee1hDYTYT

Time zone distribution for the ST2 TSC members: https://www.worldtimebuddy.com/?qm=1&lid=5368361,4140963,12,2267057&h=5368361&date=2020-3-3&sln=9.5-10.5
In order to stick with the schedule, timeline, avoid noisy environment, interruptions and letting TSC do their work, we ask anyone outside of @StackStorm/maintainers and @StackStorm/contributors joining the meeting to keep their mics muted.
Previous meetings and history
https://github.com/StackStorm/discussions/issues?q=is%3Aissue+is%3Aopen+label%3ATSC%3Ameeting
Meeting Agenda
To respect each other time, every meeting should have an Agenda ordered by priority, highlighting what are the plans so others are prepared with their updates, questions, answers and opinions.
Example: https://github.com/StackStorm/discussions/issues/31
Meeting Minutes
Every meeting should have a high-level report describing what topics were discussed, what decisions were made by the team and who was present from the @StackStorm/tsc.
Example: https://github.com/StackStorm/discussions/issues/1
Offline/Async Discussions
While some high-level ideas could be discussed live, many topics need deeper technical research, argument, design, follow-up and thought.
We encourage creating proposals with the detailed problem overview and possible solutions with pros/cons research, so others (including community members) can provide their insight and be part of the discussion before the decision takes place. This helps avoiding overloading the monthly meetings and solve the problems as they arise in async and remote-friendly way.
This could be done by opening a new Issue in StackStorm/discussions repository per StackStorm GOVERNANCE. History of Proposals and Discussions: https://github.com/StackStorm/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Aproposal

I've created a public Google Calendar with the instance of this meeting: https://calendar.google.com/calendar?cid=MDA5bDJyN3NqcDlvam5uaTB2MjJqamNyZmdAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
Clicking this link will add the calendar to your Gmail.
If you don't use Gmail i've also exported the calendar to ICS format:
StackStorm TSC<EMAIL_ADDRESS>GitHub doesn't allow uploads of .ics files, so i renamed the file to .ics.txt if you download the file, just rename it to .ics and you can import it into your calendar application!


两个face recognition模型，推荐使用哪个，hfsoftmax还要用到python 2 ？

https://github.com/yl-1993/hfsoftmax
https://github.com/XiaohangZhan/face_recognition_framework

Both of them work.
https://github.com/deepinsight/insightface is also great. The key is to train a face recognition model to extract face features.


Controlled Access Point system Manager (CAPsMAN) wireless info

We have a client that configures every gateway with CAPsMAN so they can add an additional access point with minimal additional configuration. The received signal strength indicator and other wireless info isn't in the same menus if CAPsMAN is used.

https://wiki.mikrotik.com/wiki/Manual:CAPsMAN
/caps-man interface print
/caps-man registration-table print

Send me temporary login credentials and the IP address for a device that
has a /caps-man interface entry that runs 802.11 and has connected
stations listed in /caps-man registration-table.
Andrew
On Mon, Nov 15, 2021 at 9:38 PM mthoodlum @.***> wrote:

Assigned #20 https://github.com/ispapp/ispapp-routeros-client/issues/20
to @andrewhodel https://github.com/andrewhodel.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ispapp/ispapp-routeros-client/issues/20#event-5622175293,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVCSLUJOQEWP2SQHFBPRLUMHG2TANCNFSM5IDHOWIA
.


Azure Pipelines broken?

It seems like the automatic publishing step doesn't work anymore. I just created a new tag v1.16.4, but the version on PyPI is still 1.16.3. I can't even find evidence that Azure Pipelines was running the job, and I don't seem to have access to its settings either (I was expecting to see this in the "Actions" section here in the GitHub repo).
@cboulay can you check what's going on? And maybe you could also add me to Azure Pipelines so that I can fix it myself next time? That is, if Azure Pipelines run under your personal account, we should probably create a new one for this organization and repo (i.e. xdf-modules/pyxdf).
Alternatively, we could also switch to GitHub Actions, which doesn't require any external services.

If we can't make this work for v1.16.4, it would be great if you could manually make this PyPI release. You could also give me access on PyPI so I can do it myself.

@chkothe can you make me an owner on PyPI?

@cbrnr you are now an owner.

I just scrolled through my Azure account and couldn't even find the pipelines section, nor if I was part of an organization.
If you're up to it, I encourage you to transition to GitHub Actions. That's a lot more familiar to me.
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Yes, I'm using GHA in all my other repos. I'll try to switch this repo soon, but it will take some time. Thanks for making me an owner, I will upload v1.16.4 manually. Or do you have time to do it?

I just published v1.16.4!