Update test.md

Add documentation regarding custom test options.
I found it in the contribution guide here https://github.com/pnpm/pnpm/blob/726753f05d6512c93dd6f26787a92891ded59533/CONTRIBUTING.md#running-tests
And tested it on my local setup.

I think we should make the pnpm test command work with additional args too.


Blankline only shows first identation level

I am a having this issue, I don´t know if I am missing some config but I think blankline should show me also these identation levels, is this ok?

Something I am noticing is that when I insert a new line the identation level is not the one supposed:
Screencast from 2023-02-10 09-12-40.webm
Here I let you my blankline and treesitter config (maybe tree sitter is the responsible)
require("indent_blankline").setup {
     enabled = true,
     show_current_context = true,
     char = "|",
     char_blankline = '┆',
     use_treesitter = false,
     context_char = '*',
     use_treesitter_scope = false,
}

require'nvim-treesitter.configs'.setup {
  ensure_installed = { "html", "css", "scss", "vue", "javascript", "typescript", "tsx", "svelte", "json" },
  highlight = {
    enable = true,
    use_languagetree = true,
  },
  indent = {
    enable = false
  }
}

what is :set shiftwidth set to?


Question: Save for offline?

I am currently looking around at the various music streaming servers out there. For video, I will use Jellyfin - but music integration to it feels a little lackluster and more like, "its there". So eventually I came here and I really like the UI of the client, looks absolutely beautiful!
However, amongst the README and description, I couldn't see if I would be able to save certain stuff  - like a playlist - to my local disk to listen to them offline? I travel a lot with my laptop and would love to pull down songs I want to listen to, knowing that the train wifi is probably not going to perform too well :)
Thanks and kind regards,
Ingwie

👋 Stylophone doesn't really have any music-playing capabilities on its own (local playback really just plays back an .ogg stream from the server), I don't think there's any MPD client out there with an actual offline mode of sorts?
This would probably be better served by a more classic music player, sorry!


Feat dialog prompt

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.

#298

Travis tests have failed
Hey @dolymood,
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
View build log

     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:3551) 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.
10 10 2018 09:19:27.864:INFO [karma]: Karma v1.7.1 server started at http://<IP_ADDRESS>:9876/
10 10 2018 09:19:27.867:INFO [launcher]: Launching browser PhantomJS_mobile with unlimited concurrency
10 10 2018 09:19:28.002:INFO [launcher]: Starting browser PhantomJS
10 10 2018 09:19:28.943:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket 0OXG9lAVk9nwfXv9AAAA with id 46376813
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
    ✓ should support async cascade
    ✓ $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
    ✓ should add warn log when single is true
    ✓ $updateProps: {"value":"2012-10-01T00:00:00.000Z"}
    ✓ $updateProps: {"min":"2012-04-05T00:00:00.000Z"}
    ✓ $updateProps: {"min":"2010-04-05T00:00:00.000Z"}
    ✓ $updateProps: {"max":"2025-10-20T00:00:00.000Z"}

  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 - prompt
	expected undefined to equal 'Please input'

      ✓ 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

  ImagePreview
    ImagePreview.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
      ✓ should work correctly when slide & zoom
    ImagePreview API
      ✓ $createImagePreview API

  IndexList
    IndexList.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
WARN LOG: '[Cube tip]: <cube-index-list> The property "pull-up-load" is deprecated, please use the recommended property "options" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/index-list#cube-Propsconfiguration-anchor'
      ✓ should trigger pulling-up
WARN LOG: '[Cube tip]: <cube-index-list> The property "pull-down-refresh" is deprecated, please use the recommended property "options" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/index-list#cube-Propsconfiguration-anchor'
      ✓ 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
    ✓ v-model should be a number value

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

  ScrollNavBar
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - vertical
    ✓ should trigger events

  ScrollNav
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - side
    ✗ should sticky & nav correctly
	AssertionError: expected 'A' to equal '★热门城市' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

    ✓ should trigger events

  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 not trigger scroll events
    ✓ should trigger scroll events - with scroll-events
WARN LOG: '[Cube tip]: <cube-scroll> The property "listen-scroll" is deprecated, please use the recommended property "scroll-events" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/scroll#cube-Propsconfiguration-anchor'
WARN LOG: '[Cube tip]: <cube-scroll> The property "listen-before-scroll" is deprecated, please use the recommended property "scroll-events" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/scroll#cube-Propsconfiguration-anchor'
    ✓ should trigger scroll events - with listen-scroll
    ✓ 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 events
    ✓ should trigger scroll-end but without change
    ✓ should trigger scroll when changed
    ✓ should not trigger scroll when option.probeType !== 3
    ✓ should go to right pageIndex if set initialIndex
    ✓ should not reset current when set refreshResetCurrent=false

  Sticky
    ✓ use
    ✓ should render correct contents
    ✓ should fixed ele
    ✓ should fixed ele - checkTop
    ✓ should trigger events

  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

  TabBar
    ✓ use
    ✓ props
    ✗ should render correct content when pass data prop
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✓ should toggle v-model value
    ✓ should trigger click and change event
    ✓ should remove child dom when child component destroyed

  Textarea.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - no indicator
    ✓ 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 render correct contents - showNow text
    ✓ should trigger events
    ✓ should have correct args when select normal time
    ✓ should have correct selectText when config format
    ✓ should add warn log when single is true
    ✓ should init minutes correct when minute step is undefined
    ✓ should init minutes correct when minute step is 15
    ✓ should init minutes correct when minute step is [object Object]
    ✓ should init minutes correct when minute step is [object Object]
    ✓ should init minutes correct when minute step is [object Object]
    ✓ should init minutes correct when minute step is [object Object]
    ✓ should init minutes correct when minute step is [object Object]

  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

  Toolbar.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - more actions
    ✓ should trigger events

  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 254 of 254 (3 FAILED) (1 min 10.128 secs / NaN secs)
TOTAL: 3 FAILED, 251 SUCCESS

1) should render correct contents - prompt
     Dialog Dialog.vue
     expected undefined to equal 'Please input'

2) should sticky & nav correctly
     ScrollNav
     AssertionError: expected 'A' to equal '★热门城市' (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

3) should render correct content when pass data prop
     TabBar
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

=============================== Coverage summary ===============================
Statements   : 96.16% ( 2703/2811 )
Branches     : 84.92% ( 1104/1300 )
Functions    : 95.26% ( 261/274 )
Lines        : 96.21% ( 2689/2795 )
================================================================================

npm ERR! Linux 4.4.0-112-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.14.4/bin/node" "/home/travis/.nvm/versions/node/v6.14.4/bin/npm" "run" "unit"
npm ERR! node v6.14.4
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.

TravisBuddy Request Identifier: c76644f0-cc6d-11e8-9706-8d7bf71fb7b5

Travis tests have failed
Hey @dolymood,
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
View build log

     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:3552) 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.
10 10 2018 09:35:18.951:INFO [karma]: Karma v1.7.1 server started at http://<IP_ADDRESS>:9876/
10 10 2018 09:35:18.952:INFO [launcher]: Launching browser PhantomJS_mobile with unlimited concurrency
10 10 2018 09:35:18.958:INFO [launcher]: Starting browser PhantomJS
10 10 2018 09:35:19.627:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket 5Y0El1aYvANGJpPoAAAA with id 45462583
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
    ✓ should support async cascade
    ✓ $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
    ✓ should add warn log when single is true
    ✓ $updateProps: {"value":"2012-10-01T00:00:00.000Z"}
    ✓ $updateProps: {"min":"2012-04-05T00:00:00.000Z"}
    ✓ $updateProps: {"min":"2010-04-05T00:00:00.000Z"}
    ✓ $updateProps: {"max":"2025-10-20T00:00:00.000Z"}

  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 - prompt
      ✓ 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

  ImagePreview
    ImagePreview.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
      ✓ should work correctly when slide & zoom
    ImagePreview API
      ✓ $createImagePreview API

  IndexList
    IndexList.vue
      ✓ use
      ✓ should render correct contents
      ✓ should trigger events
WARN LOG: '[Cube tip]: <cube-index-list> The property "pull-up-load" is deprecated, please use the recommended property "options" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/index-list#cube-Propsconfiguration-anchor'
      ✓ should trigger pulling-up
WARN LOG: '[Cube tip]: <cube-index-list> The property "pull-down-refresh" is deprecated, please use the recommended property "options" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/index-list#cube-Propsconfiguration-anchor'
      ✓ 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
    ✓ v-model should be a number value

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

  ScrollNavBar
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - vertical
    ✓ should trigger events

  ScrollNav
    ✓ use
    ✓ should render correct contents
    ✗ should render correct contents - side
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✓ should sticky & nav correctly
    ✓ should trigger events

  Scroll
    ✓ use
    ✓ should correct by default
    ✓ should render correct contents
    ✗ should trigger pullingDown
	AssertionError: expected false to be true (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

    ✓ should not trigger pullingDown
    ✓ should trigger pullingUp
    ✓ should not trigger pullingUp
    ✓ should trigger click
    ✗ should not trigger scroll events
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✗ should trigger scroll events - with scroll-events
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

WARN LOG: '[Cube tip]: <cube-scroll> The property "listen-scroll" is deprecated, please use the recommended property "scroll-events" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/scroll#cube-Propsconfiguration-anchor'
WARN LOG: '[Cube tip]: <cube-scroll> The property "listen-before-scroll" is deprecated, please use the recommended property "scroll-events" to replace it. Details could be found in https://didi.github.io/cube-ui/#/en-US/docs/scroll#cube-Propsconfiguration-anchor'
    ✗ should trigger scroll events - with listen-scroll
	AssertionError: expected spy to have been called exactly once, but it was called 0 times (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

    ✓ should call correct method

  SegmentPicker
    ✓ use
    ✓ should render correct contents
    ✓ should correct by default
    ✓ should trigger events

  Select.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - update txt
    ✗ should trigger events
	TypeError: null is not an object (evaluating 'this.wheels[i]') (webpack:///picker.vue:158:0 <- index.js:59069)

  Slide.vue
    ✓ use
    ✓ should render correct contents
    ✓ should clone nodes if loop is true
    ✗ should trigger events
	TypeError: null is not an object (evaluating 'vm.picker') (webpack:///test/unit/specs/select.spec.js:73:6 <- index.js:123316)

    ✗ should trigger scroll-end but without change
	AssertionError: expected spy to have been called exactly once, but it was called 0 times (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

    ✓ should trigger scroll when changed
    ✓ should not trigger scroll when option.probeType !== 3
    ✓ should go to right pageIndex if set initialIndex
    ✓ should not reset current when set refreshResetCurrent=false

  Sticky
    ✓ use
    ✓ should render correct contents
    ✓ should fixed ele
    ✓ should fixed ele - checkTop
    ✓ should trigger events

  Swipe
    ✗ use
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✗ use
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

  Switch
    ✓ use
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents
    ✗ should toggle v-model value
	Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✗ should toggle v-model value
	Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✗ should toggle v-model value
	Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

  TabBar
    ✓ use
    ✓ use
    ✓ props
    ✓ props
    ✓ props

  Textarea.vue
    ✓ use
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents
    ✓ should render correct contents - no indicator
    ✓ should render correct contents - no indicator
    ✓ should not expand when blur
    ✓ should not expand when blur

  TimePicker
    ✓ use
    ✓ use

  Textarea.vue
    ✓ should has remain when focus
    ✓ should change value
    ✓ should support more native props

  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

  TimePicker
    ✓ should render correct contents - no showNow

  Swipe
    ✗ should grow if the swipe width enough
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✗ should grow if the swipe width enough
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✗ should grow if the swipe width enough
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

    ✓ should grow if the duration is less than momentumLimitTime and moving distance is more than momentumLimitDistance
    ✓ should grow if the duration is less than momentumLimitTime and moving distance is more than momentumLimitDistance

  Toast
    Toast.vue
      ✓ should render correct contents - with type

  Swipe
    ✗ should not swipe out of the boundaries when swiping left
	TypeError: null is not an object (evaluating 'vm.isVisible') (webpack:///test/unit/specs/toast.spec.js:72:10 <- index.js:134236)

  Toast
    Toast API
      ✓ $createToast API
      ✓ should trigger correct event

  Swipe
    ✓ 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

  Toolbar.vue
    ✓ use
    ✓ should render correct contents
    ✓ should render correct contents - more actions
    ✓ should trigger events

  Upload.vue
    ✓ use
    ✓ should render correct contents
    ✓ should add files & upload

  Validator
    Validator.vue
      ✓ use
      ✓ should render correct contents - invalid

  Upload.vue
    ✗ should remove file
	Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

PhantomJS 2.1.1 (Linux 0.0.0): Executed 209 of 254 (18 FAILED) (1 min 12.035 secs / NaN secs)
TOTAL: 18 FAILED, 191 SUCCESS

1) should render correct contents - side
     ScrollNav
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

2) should trigger pullingDown
     Scroll
     AssertionError: expected false to be true (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

3) should not trigger scroll events
     Scroll
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

4) should trigger scroll events - with scroll-events
     Scroll
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

5) should trigger scroll events - with listen-scroll
     Scroll
     AssertionError: expected spy to have been called exactly once, but it was called 0 times (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

6) should trigger events
     Select.vue
     TypeError: null is not an object (evaluating 'this.wheels[i]') (webpack:///picker.vue:158:0 <- index.js:59069)

7) should trigger events
     Slide.vue
     TypeError: null is not an object (evaluating 'vm.picker') (webpack:///test/unit/specs/select.spec.js:73:6 <- index.js:123316)

8) should trigger scroll-end but without change
     Slide.vue
     AssertionError: expected spy to have been called exactly once, but it was called 0 times (/home/travis/build/didi/cube-ui/node_modules/chai/chai.js:210)

9) use
     Swipe
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

10) use
     Swipe
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

11) should toggle v-model value
     Switch
     Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

12) should toggle v-model value
     Switch
     Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

13) should toggle v-model value
     Switch
     Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 1000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

14) should grow if the swipe width enough
     Swipe
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

15) should grow if the swipe width enough
     Swipe
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

16) should grow if the swipe width enough
     Swipe
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

17) should not swipe out of the boundaries when swiping left
     Swipe
     TypeError: null is not an object (evaluating 'vm.isVisible') (webpack:///test/unit/specs/toast.spec.js:72:10 <- index.js:134236)

18) should remove file
     Upload.vue
     Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

=============================== Coverage summary ===============================
Statements   : 91.96% ( 2585/2811 )
Branches     : 78.62% ( 1022/1300 )
Functions    : 88.32% ( 242/274 )
Lines        : 92.06% ( 2573/2795 )
================================================================================

npm ERR! Linux 4.4.0-112-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.14.4/bin/node" "/home/travis/.nvm/versions/node/v6.14.4/bin/npm" "run" "unit"
npm ERR! node v6.14.4
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.

TravisBuddy Request Identifier: fc771960-cc6f-11e8-9706-8d7bf71fb7b5

Codecov Report

Merging #327 into dev will decrease coverage by 0.05%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##              dev     #327      +/-   ##
==========================================
- Coverage   92.87%   92.81%   -0.06%
==========================================
  Files         131      131
  Lines        2807     2812       +5
  Branches      418      418
==========================================
+ Hits         2607     2610       +3
- Misses        107      108       +1
- Partials       93       94       +1

Impacted Files
Coverage Δ

src/modules/dialog/index.js
100% <100%> (ø)
:arrow_up:

src/components/dialog/dialog.vue
93.75% <75%> (-2.81%)
:arrow_down:

src/components/image-preview/image-preview.vue
92.5% <0%> (-1.25%)
:arrow_down:

Continue to review full report at Codecov.

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


crr autests modified again for more order failures

More fixes to deal with header reordering and incorrect xdebug key comparison.

[approve ci autest]

[approve ci autest]

[approve ci autest]

[approve ci autest]

[approve ci autest]

[approve ci clang-analyzer]

Cherry-picked to v9.0.x branch.


Change the 2100 autostart to suitable the Bigfat plane.

Change the 2100 autostart to suitable the Bigfat plane.
But the startup can not start the pwm out 5-7.
Please help me to find out where is wrong. Thank you!

I would recommend you to check out master fresh, re-do your mixer and try this again with minimal changes. Some of the things you did could be easily enough to let the mixer load fail, in particular the change to the mixer load logic.

OK. I will try again.


Filter packages that only contain ballerina source files when compiling

Purpose

Filter packages that only contain ballerina source files when compiling

Automation tests

Integration tests

Added integration tests

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Closing this PR for now since the changes done should be reviewed again.


[Docs] Allow to switch the theme on the all documentation

Having a look at a PR like https://github.com/callemall/material-ui/pull/2892, I'm not sure how to test it.
We only have a reduced list of component here http://www.material-ui.com/#/customization/themes.
I think that it would be really great to allow users to switch the light / dark theme on the whole documentation. That's should be straightforward to implement.

@oliviertassinari Yeah I guess. Where do you think the switch button would best fit into?


how can we use that library

my circuit diagram is an esp32 s3 connected Serial1 to rak3172 wisduo board of Serial1. I can send data over UART each others . But I couldn't get your library to work in this setup. what should be prepair first?

which code should be in rak3172
your this https://github.com/beegee-tokyo/RUI3-Arduino-Library/blob/main/examples/RUI3-AT-OTAA/RUI3-AT-OTAA.ino I am testing, I thing it should be installed in esp32 s3
connection diagram?

my circuit

online this line changed volatile bool breakout_flag = true;
OUTPUT:
10:41:23.116 -> Starting loop-through - exit with 'ESC' key
10:41:23.116 -> ===========================================
10:41:23.116 ->
10:41:23.116 -> Clear Serial1 RX buffer.
10:41:28.130 -> ===========================================
10:41:28.130 -> Convert byte array to ASCII array
10:41:28.130 -> Result:<PHONE_NUMBER>05060708090A0B0C0D0E0F
10:41:28.130 -> ===========================================
10:41:28.130 -> Convert ASCII array to byte array
10:41:28.130 -> Result: {00,01,02,03,04,05,06,07,08,09,0A,0B,0C,0D,0E,0F,}
10:41:28.130 -> ===========================================
10:41:28.130 -> Get version
10:41:34.149 -> Response: NO_RESPONSE
10:41:56.251 -> Try to set work mode.
10:42:07.322 -> set work_mode failed, please reset module.

can you show me a simple example such as at+ver=?. how can I get version of rak module. thanks

yes I understand thanks. esp32 should send the at commands over the serial1


Add Truffleruby support

Add Truffleruby support to CI
Extract Rubocop linting into separate workflow

Out of curiosity: why did you extract rubocop from the default rake tasks?
I think it is a good idea indeed. But will that have any impact on the Truffleruby support?

another example of the memory related issue what team is currently investigating: https://github.com/oracle/truffleruby/issues/2591

@aslakhellesoy @aurelien-reeves is there anything else I can do here?

@aslakhellesoy @aurelien-reeves is there anything else I can do here?

Looks pretty good actually, thank you for your contribution.
Would you have the possibility to update the README to add truffleruby in the supported platforms? And the CHANGELOG too?

@aurelien-reeves done

oO I missed that truffleruby is passing all cucumber tests now, that's great :)

@eregon thanks for the review!

Hi @gogainda,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber

The error is:
 rake cucumber
Running examples/sinatra
/home/runner/.rubies/truffleruby-head/bin/truffleruby -I "lib" "/home/runner/work/cucumber-ruby/cucumber-ruby/bin/cucumber" --format pretty
Feature: Addition
  In order to avoid silly mistakes
  As a math idiot
  I want to be told the sum of two numbers

  Scenario: Add two numbers           # features/add.feature:6
    Given I visit the calculator page # features/step_definitions/add_steps.rb:1
      TruffleRuby doesn't have a case for the org.truffleruby.language.objects.IsImmutableObjectNodeGen node with values of type com.oracle.truffle.llvm.runtime.except.LLVMPolyglotException
      	from org.truffleruby.language.objects.IsImmutableObjectNodeGen.executeAndSpecialize(IsImmutableObjectNodeGen.java:117)
      	from org.truffleruby.language.objects.IsImmutableObjectNodeGen.execute(IsImmutableObjectNodeGen.java:59)
      	from org.truffleruby.core.kernel.KernelNodes$DupNode.dup(KernelNodes.java:685)
      	from org.truffleruby.core.kernel.KernelNodesFactory$DupNodeFactory$DupNodeGen.executeAndSpecialize(KernelNodesFactory.java:2232)
      	from org.truffleruby.core.kernel.KernelNodesFactory$DupNodeFactory$DupNodeGen.execute(KernelNodesFactory.java:2213)
      	from org.truffleruby.language.methods.CallInternalMethodNode.alwaysInlined(CallInternalMethodNode.java:114)
      	from org.truffleruby.language.methods.CallInternalMethodNodeGen.executeAndSpecialize(CallInternalMethodNodeGen.java:199)
      	from org.truffleruby.language.methods.CallInternalMethodNodeGen.execute(CallInternalMethodNodeGen.java:87)
      	from org.truffleruby.language.dispatch.DispatchNode.dispatch(DispatchNode.java:308)
      	from org.truffleruby.language.dispatch.RubyCallNode.doCall(RubyCallNode.java:152)
      	from org.truffleruby.language.dispatch.RubyCallNode.execute(RubyCallNode.java:109)
      	from org.truffleruby.language.dispatch.RubyCallNode.executeArguments(RubyCallNode.java:185)
      	from org.truffleruby.language.dispatch.RubyCallNode.execute(RubyCallNode.java:98)
      	from org.truffleruby.language.dispatch.RubyCallNode.execute(RubyCallNode.java:89)
      	from org.truffleruby.language.dispatch.RubyCallNode.executeArguments(RubyCallNode.java:185)
      	from org.truffleruby.language.dispatch.RubyCallNode.execute(RubyCallNode.java:98)
      	from org.truffleruby.language.control.SequenceNode.execute(SequenceNode.java:37)
      	from org.truffleruby.language.RubyMethodRootNode.execute(RubyMethodRootNode.java:65) (TypeError)

I'll take a look (cc @bjfish).

Thanks @eregon :)

Indeed, it's green now: https://github.com/cucumber/cucumber-ruby/runs/6382227723?check_suite_focus=true

Yes, feel free to try truffleruby instead/additionally which uses the latest release.
Testing against truffleruby-head is helpful for the TruffleRuby team (and we monitor such failures via https://github.com/eregon/truffleruby-gem-tracker/, we noticed it just a bit after the ping), but we also understand if you want more stability.
Testing both also makes sense, then it's easy to differentiate if some change in cucumber/deps broke on TruffleRuby in general or if it's due to some change in truffleruby-head.

Yes, feel free to try truffleruby instead/additionally which uses the latest release.
Testing against truffleruby-head is helpful for the TruffleRuby team (and we monitor such failures via https://github.com/eregon/truffleruby-gem-tracker/, we noticed it just a bit after the ping), but we also understand if you want more stability.
Testing both also makes sense, then it's easy to differentiate if some change in cucumber/deps broke on TruffleRuby in general or if it's due to some change in truffleruby-head.

Noted! Thanks for the info! :)
We'll see what we could do


Some jobs have too many tasks

https://linen-slack.kedro.org/t/22732083/announcing-kedro-databricks-https-github-com-jenspederm-kedr#0dffcc72-1ac6-4c4f-9bb0-47a654643cd0

I have been trying out your plugin today.  I have more than 100 nodes in my default pipeline T.T which is why it is crashing...

A possible solution would be to group tasks, like kedro-airflow does since https://github.com/kedro-org/kedro-plugins/pull/241 cc @ankatiyar, @sbrugman
There are other possible solutions maybe.
I'm wondering, does this "100 tasks per job" limitation depend on the Databricks config/cluster? Or is it universal?

I'm wondering, does this "100 tasks per job" limitation depend on the Databricks config/cluster? Or is it universal?

My hunch is 1 task is 1 container - the same reason you shouldn't need 28 containers to run spaceflights

I'm wondering, does this "100 tasks per job" limitation depend on the Databricks config/cluster? Or is it universal?

My hunch is 1 task is 1 container - the same reason you shouldn't need 28 containers to run spaceflights

Think you're right. As far as I can tell, it's universal. But I haven't really found any mention of it outside of this issue from 2021: https://community.databricks.com/t5/data-engineering/how-many-jobs-can-i-create-in-my-databricks-workspace/td-p/18111


Add Test5 - create containers with RDF bodies

Resolves: https://jira.duraspace.org/browse/FCREPO-1947

@ruebot, It looks like the issue was that it was assumed that the user would run the test from the fcrepo4-jmeter directory. I have pushed a new commit that parameterizes the location of the "resource directory", i.e. the parent directory of sample.ttl.
I believe the following command should now work for you... if you update your branch with the latest commit:
vagrant@islandora-deux:~/git/apache-jmeter-3.0/bin$ ./jmeter -Dfedora_4_server=localhost -Dfedora_4_context=fcrepo/rest -Dresource_directory=/home/vagrant/git/fcrepo4-jmeter -Dcontainer_rdf_threads=1 -n -t /home/vagrant/git/fcrepo4-jmeter/fedora.jmx >> /tmp/pr-test.log


Unknown location; please try $lat,$long

wttr.in seems to be down.
$ curl wttr.in
> Follow @igor_chubin for wttr.in updates

$ curl wttr.in/Copenhagen?format=%c+%t
> Unknown location; please try ~55.6867243,12.5700724

Seems to be same issue as in #454

If you go to https://wttr.in/ in you browser you will see:

Sorry, we processed more than 1M requests today and we ran out of our datasource capacity.
We hope to solve the problem as soon as possible, so you can enjoy
your favourite weather service 24x365 even if it rains or snows.
We will solve the problem as soon as possible.
Follow @igor_chubin for the updates.
If you like to code (and you surely do), you can check the wttr.in repository
to see how the scalability problem is (not yet) solved.

which explains empty response for curl wttr.in

Thanks for the heads up!

Yes, the location problem yesterday was caused by the problem that @pkoziol metinoned. It should be fixed now, please test

It does indeed :smile:
I use this extensively in my setup. Is there any way to support the project? Maybe a Patreon page or something?

No Patreon page, just keep using it; bug reporting/criticism is also helpful

Not sure that this should be closed, I've been getting it on and off recently

@MyriaCore Yes it is ok that this one is closed; the problem occurs sometimes (when the load is peaking); the problem is known and referred by other open issues


update instructions for Tails 1.4

Update Pond build instructions for Tails 1.4 to manually download source code over https until Tails includes a version of go that does not download code over http, use the Additional Software feature instead of aliases to manage dependencies, and updates notes accordingly.

These instructions are missing the apt-get install line, but other than that I've confirmed that they do work on Tails 1.4. However, they don't leave the user an easy way to upgrade. I'd like to have a simple bash script in the pond repo which safely builds and installs the latest version of pond (and its dependencies) so that the instructions for tails and other debian distros can become 1) checkout the repo and 2) run the script. I'll try to write this soon if someone else doesn't do it first.

Thanks for catching the missing apt-get install line. There is now a new version of Tails 1.4.1 out and I'm not sure if these directions work. I made a cursory attempt to test the instructions against the new version and ran into some trouble with dotfiles, but I haven't investigated it sufficiently.
I wrote these instructions trying to stick to the apparent philosophy of the previous instructions, but I like @leif's idea. It would be nice if the script went all the way to building a Debian package locally so APT can manage versioning (this might have already been @leif's intent). Tails is based off Debian Jessie, so it's very likely that the two will be solved together. That also addresses the just entered issue for Debian Jessie https://github.com/agl/pond/issues/195
Thoughts?

Tails is based off Debian Jessie, so it's very likely that the two will be solved together. That also addresses the just entered issue for Debian Jessie #195.

Tails 1.4.1 is now using the Linux kernel from Debian Jessie, but is still based on Debian Wheezy otherwise. According to Tails' roadmap Tails 2.0 will be based on Jessie.
IIRC the plan is to release 2.0 late in 2015.


It localization v2beta

Update Italian Localization for GBStudio v2.

@chrismaltby sorry to bother you, but I will soon be using GBStudio b2 for a workshop involving 17yo kids. Would it be possible to merge this pull request so they will have the full IDE in italian?

@marcosecchi if you need them in a hurry and can live compile gbs from github, you could try building your own binaries
yarn <--- install dependencies
npm start <--- build and run the app live
yarn make:win or  yarn make:mac or just
yarn make <--- build the binaries
will save to GitHub\gb-studio\out\

@RichardULZ Thanks but unfortunately I get this error when compiling:
An unhandled rejection has occurred inside Forge:
[Error: ENOENT: no such file or directory, rename 'C:\Users\MARCOS~1\AppData\Local\Temp\electron-packager\win32-x64\GB Studio-win32-x64\electron.exe' -> 'C:\Users\MARCOS~1\AppData\Local\Temp\electron-packager\win32-x64\GB Studio-win32-x64\gb-studio.exe'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'rename',
  path: 'C:\\Users\\MARCOS~1\\AppData\\Local\\Temp\\electron-packager\\win32-x64\\GB Studio-win32-x64\\electron.exe',
  dest: 'C:\\Users\\MARCOS~1\\AppData\\Local\\Temp\\electron-packager\\win32-x64\\GB Studio-win32-x64\\gb-studio.exe'
}

Electron Forge was terminated. Location:
{}
error Command failed with exit code 1.

Do you have any advice on this?
Thanks.

@RichardULZ thanks for the heads up. As the pull request is from Dec. 2020 and it's just a localization update, I was hoping for a merge any time.
Anyway, unfortunately the make command fails with the following error:
An unhandled rejection has occurred inside Forge:
[Error: ENOENT: no such file or directory, rename 'C:\Users\MARCOS~1\AppData\Local\Temp\electron-packager\win32-x64\GB Studio-win32-x64\electron.exe' -> 'C:\Users\MARCOS~1\AppData\Local\Temp\electron-packager\win32-x64\GB Studio-win32-x64\gb-studio.exe'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'rename',
  path: 'C:\\Users\\MARCOS~1\\AppData\\Local\\Temp\\electron-packager\\win32-x64\\GB Studio-win32-x64\\electron.exe',
  dest: 'C:\\Users\\MARCOS~1\\AppData\\Local\\Temp\\electron-packager\\win32-x64\\GB Studio-win32-x64\\gb-studio.exe'
}

Electron Forge was terminated. Location:
{}
error Command failed with exit code 1.

Do you have any hint on how to solve this?
Thanks


package for npm

This project can't be accessed through a typical npm/browserify workflow because this line:
https://github.com/neodon/react-multiselect/blob/2734b1b8587bca407e889aae25fdba1a326eedae/package.json#L26
points to a file that does exist. Just point it to the file you're exporting your component from, and it should work.

Then you'll have to npm publish, of couse.

Thank you for reporting this.  I'll take a look and get it fixed.

Sorry for the long delay.  I think I was able to fix the issue as well as a problem preventing the react dependencies from being installed when the module is installed.  Would you mind seeing if you are able to get it to work with the latest version?  Do you still use this module?

Thanks for fixing and publishing it. I ended up going for https://github.com/JedWatson/react-select instead. But I did take your package for a test drive and confirmed that I could now npm install it.


Failing to Load on Mobile

I've got an issue where Quoth is failing to load on mobile (iOS, Obsidian Version 1.1.0 (37)).
The exact error message is (grabbed using Obsidian REPL):
Plugin failure: quoth
SyntaxError: Invalid regular expression: invalid group specifier name.

Just pushed the fix for this and tested on iOS. Thanks for the error message, it was super helpful.
Please let me know if you continue to have any issues.

Thanks for such a speedy fix! It loads fine now on the latest inside mobile build! ^^


Model::delete method

I'm curious why the Model::delete method is setup to only take an $id and and then there is a separate Model::deleteWhere? If Model::delete was more generic I think it could accommodate more conditions. As it stands now, the Model class needs to be extended to create your own "deleteOrWhere" and "deleteWhereIn" methods.
Thanks for all your hard work!

That's a fair point. Most of came simply from a base model I had used for years. I would create multiple small methods to handle specialized cases in each model so it was more readable, so the delete and deleteWhere were all that I needed.
With the current model, though, you can access all of the Builder methods in your method chain, as well as the model methods, so it might make more sense to remove deleteWhere and rename delete to deleteOne or something, then allow the builder's normal delete method to be used. But, then that's not consistent with what find and update do, so not sure.... will have to think on that a bit.

I think the delete should act like update/where clauses. I've been using the models myself and find it confusing why I can't do delete(['name'=>'thisname']) , Should delete whatever equals that query.  That's consistent with the update use, except you don't need to specify a second array/argument. That should be an easy fix, looking first to see if the user put an ID (primary key), or an array of IDs, and then next check if the user puts an array for where clause. This way the delete is used for how everyone would intend it. That's how I would assume it works given the update method.

@timothymarois I think delete is closer to find/findWhere in usage, honestly. update always requires a single id passed to it.
Looking back over the model methods, it might make sense to make these changes:

delete should take either one id, or an array of ids. That is consistent with find.
delete should also work like the Query Builder version when no parameters are passed in. This allows for $model->whereIn('status', $statuses)->delete(); flow without the need for a bunch of new custom methods.

I think it would be tricky to reliably determine between an array of ids (which might be strings, also) and would stay consistent with the find/findWhere combo, which has a closer relation to delete than update does, I think.
I'm tempted to say we get rid of findWhere and deleteWhere and allow both find and delete to work. Well - that doesn't quite make sense, actually. The find method is simply a helper method for limit->get.

@lonnieezell Yeah You're right, I used a version before which reminded me I had update(array, array) but in the current state of CI4 it's only update(id, array).
As for the findWhere I think it's useless because I always use where()->findAll(), findWhere to me doesn't make much sense. (unless there are other uses which I'm unaware of), I just like the simplicity of stating intention. I know findWhere is merely a helper function to where and get, but really should use the query methods instead. Plus multiple ways of doing the same thing can get confusing in the docs for which way it better than another, should be one straightforward way.
As for delete, I really am for a delete method being used for batch deleting based on where clause.  Honestly, this is how I believe update and delete should work for simplicity sake.
// simple update
$db->update($id, $array);
// batch id update
$db->update([1,2,3], $array);
// update based on where (as the first argument states which items it needs to update)
$db->update(['status'=>'pending'], ['status'=>'active']);

// simple delete
$db->delete($id);
// batch id delete
$db->delete([1,2,3]);
// delete based on where (as the argument states which items it needs to delete)
$db->delete(['status'=>'pending']);

These are my thought as to how I think they should work. I know most likely it's too late to really rethink how the model works. But I've always viewed it in this way because it makes the most sense and my intentions for using them. But you can correct me if there are some flaws in that.

We're not even to a beta-release, yet, so it's not too late :)
I like the simplification of what you've presented. I'm a little concerned that things get confused here. That one method now allows 3 ways to do things. The first two of them make sense and are close in functionality, but adding the third method muddies the usage. While it's simpler in some aspects, doesn't it make it a little less explicit about what it's doing? It's a bit more clear that updateWhere is providing a set of where conditions to find the rows by.
I realize I'm might be getting a little far in the weeds thinking about this one, so I'm definitely interested in other opinions on this. @daylightstudio @jim-parry what's your thoughts?

I could be misunderstanding PHP, but aren't
// batch id update
$db->update([1,2,3], $array);
// update based on where (as the first argument states which items it needs to update)
$db->update(['status'=>'pending'], ['status'=>'active']);
both cases of update($array,$array)? How would you tell them apart?
I can see enhancing the existing delete to accept an array of ids.
In the conversation earlier, there was a suggestion of method chaining, eg ->where(...)->delete(). This makes most sense to me, with similar changes to update(). In other words, enhance delete() and update() to work on the current "selection".

@jim-parry Well, they are 2 different forms of arrays so they could technically be checked for but that seems like it might be easy to miss some edge cases. One form would always have numeric keys while the other may/may not. Seems a bit fragile to me.

My opinion on the deleteWhere and the findWhere is that although convenient, I'd expect there to also be deleteOrWhere, findOrWhere... etc.

There is no end to it :-/
I would opt on the side if simplicity.

@jim-parry @lonnieezell  I do agree that chaining a where() to delete() would make things convenient and simple in action/clarity. I would be for that since its very self-explanatory. where method should be chained more so than using a findWhere or deleteWhere because the more methods you introduce would mean more documentation and the explanation of what each does and their arguments. But as it stands, I do think we should simplify in some way the current way of doing it cause it can be a bit inconsistent. I find myself referring to the documentation multiple times because there are multiple ways of doing queries in the model. Not sure if this is all getting off topic from the original, but that's my opinions (and after using CI4 in major projects already).

I think we have all come to more or less the same decision. Sounds good. So, to sum up:

remove findWhere, deleteWhere
delete should handle a single ID, and array of IDs or nothing. If nothing, will act as the query builder's delete method
find should work with a single ID, an array of IDs or nothing. If nothing, will simply be an alias for get().
to maintain consistency, update should work as it does, with an ID and an array, or just an array. If just an array it is expected to be the elements to update and would required a where call prior.

+1

@lonnieezell Agreed. I like the direction.

@lonnieezell Also let me know if you need any help, I know we both have been working a lot these days. If I can get my development env set back up for CI, I might be willing to make a few of these changes if you think it will be a while before you can get to them.

If you’ve got the time I’d say go for it. Knee deep in an outside of work project currently so time is definitely hard to come by for bigger changes right now.


JOSS paper discussion

Let's make a gollum paper!
Destination and bundling
The muler paper is destined to be submitted relatively soon, likely to JOSS (and possibly part of an affiliated AAS journals paper).  See the muler issue for that discussion:  https://github.com/OttoStruve/muler/issues/76
My inclination is to submit a standalone JOSS gollum paper.  I've already started a paper.md file here: 6e950e8
The alternative paths would be either A) combine it with muler, or B) associate it with an affiliated AAS Journals paper.  Option A seems a bit messy, and option B doesn't have a specific AAS journal paper in mind, since I see gollum as a general purpose tool/microservice.  So option B would delay the publication, essentially indefinitely.
Timeline and things-to-do before submitting
In principle we could submit now-- the framework is working and is pretty good albeit imperfect.
The main thing I want to add before submitting is support for the full Sonora-Bobcat 2021 model grid (Marley et al. 2021) with metallicity support (Issue #6).  My recommendation is to make adding this feature a priority.
We'd probably also want to add a tutorial or video screencast on how to use the dashboard.  Getting up-and-running with the dashboard is tricky since it only works locally (does not work on Google Colab, for example), and requires the voluminous model grids in a certain directory structure.  So showing the awesomeness of the dashboard without having to install is a key important step.
So that puts us around April/May 2022 for submission time.  I'm okay with that, and it allows some new contributors a chance to join in before then.

@sujayshankarUT and @Jiayi-Cao let's plan to submit the paper in the next coming weeks!

@SujayShankarUT and I are working in this now!

Let's add a screenshot of the dashboard to the paper!

This got put on the back burner while we worked on blasé, but is now active again. @SujayShankar2001  will be leading this. Sujay, here is the documentation on how to get started:
https://joss.readthedocs.io/en/latest/


FIX(designer): Fixes error setting number of operations in relationship

Fixes #177 . The number of operations is needed in the optimizer. @adriannieto , @perezp : please, have a look.

The code looks good to merge but as you have to agree with @perezp about the requirements  of the designer I will hold my vote until he answers.

@adriannieto : This is a fix, not a feature.

Good. +1 .
Merging


Milestones discussion on a weekly basis

We have a timeline for the project [here] (https://github.com/numfocus/gsoc/blob/master/2015/proposals/Amit.md). We have the following broad pointers to implement :

Propagator types for RK methods, exponential methods
Monte Carlo Wave-function Method
Time dependent problems (Hamiltonian, Collapse operators)
Parallelization of 2 and at a more abstract level (for example QuArray)

It would be great to hear from the community on any further pointers. Also we could be using this to discuss and set weekly milestones so that we can have a track of the progress.

Just a quick update for the first two weeks we have the done the following :
Pull :  https://github.com/JuliaQuantum/QuDynamics.jl/pull/4
Related Blog post : https://github.com/JuliaQuantum/JuliaQuantum.github.io/pull/24

News section has been updated with the blogs. Please refer to the posts tagged with GSoC 2015. Closing this.


Is the mean_IU in the program mIoU?

Is the mean_IU in the program mIoU?
IU_array = (tp / np.maximum(1.0, pos + res - tp))
mean_IU = IU_array.mean()

Yes.


Realtime visualisation

Is the idea to commit the load test metrics to a time series database (InfluxDB?) and visualise through Grafana?

That's certainly a possibility. If you create a recipe for this, please feel free to share!

InfluxDB is a possibility, I will also look into Kafka.

Could you please tell me how I specify 0.10.0-dev in Cargo.toml when goose on creates.io is published at 0.9.1? Thanks.

Please see the Specifying Dependencies documentation. You can check out the repo and include it locally, or even include directly from github.
Hopefully we're closing in on a 0.10.0 release soon, as well.


Factorial of a Given Number using c++

#hacktoberfest2022 beginner

If Excluded then contribute here.. https://github.com/RajkumarSony/LeetCode-Solutions.


Miden VM support, pliron for IR, Valida VM explorations

Use pliron for IR dialects.
Add Miden VM support:

Miden IR dialect;
Wasm -> Miden transformation;

Start Valida IR dialect and draft a simple Wasm -> Valida transformation.
Todo:

[x] rebase/merge main;
[ ] put start code into valida's prog op's entry block;

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1300 of 2545 (51.08%)  changed or added relevant lines in 77 files are covered.
487 unchanged lines in 26 files lost coverage.
Overall coverage decreased (-41.3%) to 40.426%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/codegen-midenvm/src/codegen/emit.rs
4
5
80.0%

crates/codegen-valida/src/codegen/emit.rs
3
4
75.0%

crates/ir-transform/src/pseudo_op_sub.rs
0
1
0.0%

crates/ir/src/pass.rs
0
1
0.0%

crates/codegen-midenvm/src/codegen.rs
37
39
94.87%

crates/codegen-tritonvm/src/codegen.rs
0
2
0.0%

crates/codegen-tritonvm/src/codegen/emit.rs
0
2
0.0%

crates/codegen-tritonvm/src/codegen/inst_buf.rs
0
2
0.0%

crates/codegen-tritonvm/src/target.rs
0
2
0.0%

crates/dialects/valida/src/lib.rs
6
8
75.0%

Files with Coverage Reduction
New Missed Lines
%

crates/codegen/src/config.rs
1
0%

crates/frontend/src/translate.rs
1
0%

crates/codegen-tritonvm/src/config.rs
2
0%

crates/ir/src/ir/inst/ext/triton.rs
2
0%

crates/frontend-shared/src/mod_builder/import_func_body.rs
3
0%

crates/ir/src/pass.rs
5
0%

crates/stdlib/src/lib.rs
6
0%

crates/codegen-tritonvm/src/ty.rs
7
0%

crates/ir-transform/src/and_minus_8.rs
7
0%

crates/ir-transform/src/pseudo_op_sub.rs
7
0%

Totals

Change from base Build<PHONE_NUMBER>:
-41.3%

Covered Lines:
1366

Relevant Lines:
3379

💛  - Coveralls


Unstructured supplementary service data

Description
A short summary of what is included in your Pull Request.
Fixes #(issue_no)
Replace issue_no in the above line, with the issue related to this PR.
Type of change
Choosing one or more options from the following as per the nature of your Pull request.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[x] I have added a working sample/screenshot of the script.

All done. Waiting for verification

Ok ,on it...

All requested changes attended to

All requirements checked and corrected where necessary

Any other requirements before you merge ?


hide the launcher devtools most of the time

@keybase/react-hackers usually we want the main devtools and not the menu widget

@keybase/react-hackers bump

:thumbsup:


fix for update list on-prem

CSOM v15 does not support MajorWithMinorVersionsLimit so UpdateList crashes on-premises

Thank you Ivan! Good catch! Will merge.


FieldGroups - All tables need default DropDown FieldGroup

It is not possible to extend a FieldGroup without it already existing.  E.g. the Item Variant (5401) table has no DropDown FieldGroup so I can't add any field from a tableextension to the default dropdown in a lookup.  It defaults to just Description.

This is better to be implemented on compiler level than on application tables. Transferring to al repo.

Hi @GreatScott000 ! This is not currently possible. We will consider it for our backlog.

This is still an issue.
Either add default DropDown and Brick fieldgroups to all base tables or change the TableExtension object to allow us to create it.
Either will suffice, but right now, it's just a hard stop.   We also can't change LookupPageID, so we're very stuck here.

I can understand why you may not be able to add fieldgroups with mixed base/extension fields, but I do not understand the underlying reasons why we can't specify fieldgroups with all base fields, or all extension fields.  Likewise with the lookuppageID.  This is a very difficult restriction to work with.

Any ETA or maybe a workaround?

Thank you the input! We have had a lot of great suggestions from the community and we have tried our best to prioritize the most important ones for the Fall release. Unfortunately, this did not fit in. It would be of great help if you could post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. It will allow us to better prioritize the issue for a future release.

@atoader @JesperSchulz this is something that was possible before, and is now lacking functionality. Without giving us a work around, why do you not treat it as a bug rather than a would be enhancement ?

@JesperSchulz @atoader  - Hey, when the Fall release comes out as pure AL code, could the community do one massive pull request with default DropDown and Brick fieldgroups to all the objects that are missing them?  From what I understand, the base app will be in GH, so we should be able to get this done where you cannot, yes?  (That's not criticism - we just need this fixed.)

I'm afraid we will not be publishing the BaseApp on GitHub - at least not now. What we are publishing, are the modules and add-on extensions we extract out of the BaseApp one by one. The reason for not publishing the BaseApp is that we would be struggling to keep up with the inflow of pull requests, as we know that many partners have many great ideas - but not all of them are compatible with each other and desiderable in the standard product. It would require a big investment to understand and polish all of the incoming suggestions. We're not in a state yet, where we can make that change and go truly open source on all of our application code.
So, for now you will have to stick with http://aka.ms/bcideas - try to get enough votes and we will take a look at it. And maybe some day, everything will be aligned to make the big move to open source all of our code - but that does require build system integration, a community which is prepared to chip in and review, a more structured base code and so on...

With that being said, it does not mean that we won't be looking at the concrete issue mentioned in this thread. My previous comment was purely on the aspect of open sourcing the BaseApp.

@JesperSchulz @atoader Are there any plans to implement default fieldgroups for atleast the main header tables (Sales Header, Purchase Header etc...) to allow us to work around this issue while you find a propper solution?

Hi @markusfjolnisson, if you could give me a complete list of the tables you'd like use to implement default fieldgroups in, I will process it for the upcoming major and minor release - while we wait for the correct solution in our platform.

Ideally, I would also need the definitions of the fieldgroups. That would speed up processing ;-)

Hi @JesperSchulz, Thanks for the fast response. It is a pleasure to be able to interact with your team on these issues!
As i see it, the most important tables would be the unposted header tables, and their corresponding line tables...
36		Sales Header
37		Sales Line
38		Purchase Header
39		Purchase Line
295		Reminder Header
296		Reminder Line
5740	Transfer Header
5741	Transfer Line
5900	Service Header
5901	Service Item Line
5902	Service Line
As for the definitions of the fieldgroups, i think the current default "Drilldown" options are fine. If I remember correctly, when a fieldgroup is not defined, the system uses the primary key of the table and the description or name field (If that is a field included in the table). My problem is not the default fieldgroups used by the system, but that i am unable to add a field to the dropdown list to aid the customer in registering data.

:-) I get that! I just don't want to add default fieldgroups (which are used by the majority of our users), which make the product worse. But I'll check what the functionality defaults to, and then I will set those explicitly on the tables you mention.

Hi @JesperSchulz
We have just implemented BC15.0 (upgraded to 15.2) and default fieldgroups are really missing and we are struggling with that a lot... The project is about 300MD and it is very hard to explain to our clients that we are able to change almost everything except this (that is from their point of view so easy).
I know that we can change baseapp (we are onPremise); however, we did the whole project without any change in baseapp...
Could you please add the default DrillDown fieldgroup to:

Shipment Method (ID10)
Transport Method (259)
Payment Method (289)
Shipping Agent (291)
Bank Account Statement (275)

I surely can! Adding those 5 tables to my pack to be released with next minor :-)
Any other requests out there while I'm at it?

table 99 "Item Vendor"
table 7012 "Purchase Price"
thanks

You got it! Final call for more tables ;-)

I surely can! Adding those 5 tables to my pack to be released with next minor :-)
Any other requests out there while I'm at it?

Sorry if i'm too late.. but can we have dropdown fieldgroup for Bin Contents table as well?

I'll see what I can do for you :) The other fieldgroups are getting released with the next minor end of month.

So, no hope to be able to define the fieldgroup for a base table from extension?

So, no hope to be able to define the fieldgroup for a base table from extension?

H,I I agree this should be available to create new FieldGroups in AL extensions. When can we expect it?

@pborring/@atoader, that question would be for you to answer.

@Techcronus-NAV, the Location table already has a FieldGroup!
fieldgroups
{
fieldgroup(Dropdown; "Code", Name)
{
}
}

Please create new issues for new requests, as this one has been closed a long time ago.
This last one I'll process in this issue though ;-) Item Variant seems to have a field group already:
fieldgroups
{
fieldgroup(DropDown; "Item No.", "Code", Description)
{
}
}

Hi~
@JesperSchulz
I create a new issue ,
Could you please help me solve it?
[#6644 ]
Thank you in advance.

Hi,
I now this thread is closed, but we need to add fieldgroups and brick on all Documents Archived tables (T5107 - Sales Header Archive, T5109 - Purchase Header Archive and all related tables - T5108 - Sales Line Archive, T5110 - Purchase Line Archive).
And, it must be supported that fieldgroups, and bricks can be added to the base tables via the tableextension objects. My customers ado not understand when I say to them, that sorry, not possible.

I'd open a new issue


Open forum from home

It is quite dreadful to open a community project at the moment: go to forum, open shared link (wait), click Open Code (wait) click "Edit" (wait).
This change sniffs the project url using the Discourse API and display a "Open In Editor" option.
*requires to deploy support for "forumUrl" card types

Note: one needs to enable CORS for the domains that use this feature in the discourse settings.


Issue 11: Create Badge Component

PR changes:

[X] Add Props: color?: 'neutral' | 'success' | 'danger' | 'warning', defaults to 'neutral'.
[X] Styles: I have added the colors below just on top of my head, feel free to make adjustments if the final look is not good

badge: {
   base: 'inline-flex px-2 text-xs font-medium leading-5 rounded-full',
   neutral: 'text-gray-700 bg-gray-100 dark:text-gray-100 dark:bg-gray-700',
   success: 'text-primary-tint40 bg-primary-shade60 dark:bg-primary-tint40 dark:text-primary-shade60',
   danger: 'text-red-700 bg-red-100 dark:text-red-100 dark:bg-red-700',
   warning: 'text-orange-700 bg-orange-100 dark:text-white dark:bg-orange-600',
 },

[X] Please use the span tag as the base element for building the badge
[X] The component should be extensible. So the user should be able className, children and other native HTML props which should be applied to the span tag. Already implemented in other components. Please have a look
[X] Add unit tests to test the above requirements, please have a look at tests written for other components
[X] Add the component to storybook

Visual Changes:

Test passing:

Small issue:
For the danger styles: text-red-700 bg-red-100 dark:text-red-100 dark:bg-red-700, I had to use bg-red instead 'cause Tailwind styles don't get injected for some strange reason. Also text-red-700 doesn't work. If you find a workaround, I am happ to push the changes @kirandash

I hope I was able to explain it clearly. If you need any help, feel free to let me know.

It was perfectly explained. I would let you do this change if you don't mind. I don't feel comfortable making changes in other components & risking not noticing any breaking style changes.


move sample data to the database

Original issue by @bmesuere on Fri Aug 03 2012 at 15:16.
Closed by @bmesuere on Wed Jan 16 2013 at 15:39.

duplicate of #100
Original comment by @bmesuere on Wed Jan 16 2013 at 15:39.


Add pattern_matching test cases for ast_builder

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

60 of 66 (90.91%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 98.955%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

test-suite/src/ast_builder/expr/pattern_matching.rs
60
66
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
42994

Relevant Lines:
43448

💛  - Coveralls


Andreas/cpp codegen/fix formatter differences

Part of #2647

What
For unknown reasons cpp formatter invoked via just file versus via codegen yielded slightly different results. Tried various things but to no avail. However, specifying some of the options in the clang format file more explicitely solves the issue.
Plus, changed how header sorting is handled.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview

Can confirm it works on Linux @ clang-format version 15.0.7


Pluggable Resolver- only respect valid Semantic Versions

Some repositories on GitHub doesn't maintain valid Semantic versioning on their tags.  For example: blockui
When implementing the releases(source: string): array from the API, the result would be empty because no tags are valid.
Bower without the resolvers implementation knows how to handle this kind of issue.

I'm seeing something related to this issue as I'm trying to implement a mercurial resolver.
As far as I can see, target is initalised to "*", and then the versions are returned by the releases function on the resolver. This responds with some array, e.g. [{ version: '*', target: 'whatever' }, { ... }]. However, any versions that aren't valid semver (e.g. "*") are removed, so the version cannot be resolved...
Am I missing something obvious here? @sheerun can you shed some light?

The releases method is expected to return list of valid semver versions (not ranges, like * or ^1.2.3), and matching targets. If there are no valid semver versions, return something like [{ version: '0.0.0', target: 'whatever' }].

Right, that makes sense. How would this work for people wanting to target named branches etc?

Bower executes releases method only if user provides a range like * (default) or ^1.2.3. If user provides non-semver target, like master, bower skips directly to fetch method.

Of course! Thanks!

I clarified releases method in documentation: https://github.com/bower/bower.github.io/commit/71b8c86eb4a2c506c38211ac0ddfb09a4cfcbe09

@sheerun, it appears that the above clarification you made to the documentation is no longer part of the formal pluggable resolver API docs on the Bower site. Is returning a 0.0.0 version or similar still the recommended practice, or has there been a change in guidance?

@fjmilens3 I can't account for the change in docs just yet, I'll look into that a bit later. I believe the spirit of the resolver is to support installing packages with semantic versions - the 0.0.0 release only seems to be listed as a default, but it might not be necessary. Are you working on a specific resolver that we can reference?

@fjmilens3 I created an example bower resolver (github link). I realize that it's very simple, but the resolver works without implementing the resolver.releases(). I noticed that the bower.io/pluggable-resolvers lists sample code with that method being optional. Does that answer your question?

Thanks for the information! I think it helps, but I'm not sure how applicable the example resolver would be to our particular scenario. The issue we're encountering is that we do want to support semantic versioning when available, but also have a need for a default behavior that would allow us to return the contents of master when a project hasn't any made any formal releases/created any tags in their repo.
So far, it appears that returning an empty array indicating no releases results in Bower failing with an indication that no suitable versions are available. However, making up a version can produce incorrect version numbers being saved in the user's bower.json if the user is using the --save option (it will record something like ^0.0.0 which is quite different semantically from *, which is what we really want). If we could return * as a valid version to handle the special case, that might solve the problem, and we could translate that to something meaningful in our resolver's fetch, but * isn't a valid semver and won't survive the trip.
This is specifically in the context of our resolver for Nexus 3 at https://github.com/sonatype/bower-nexus3-resolver, but I would imagine this could surface in similar scenarios as well. In our particular case it's a matter of wanting to support semantic versioning as our product is a repository manager, but also wanting to be able to support edge cases for high-profile projects that don't do formal releases with semantically-versioned git tags (and just rely on the git resolver behavior of checking out master).


Set up CI for main branch and for the Pull Request verifications

GH actions that trigger tests should be enough.

Done? @xstefank


feat: Make service_id a text column

Existing values will be converted

:tada: This PR is included in version 1.6.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How to update to nixos 23.11?

I see the packages in nix-portable are out-of-date. What should I do to update?
Thank you.

duplicate https://github.com/DavHau/nix-portable/issues/27


Fix notebook markup and improvements

Use correct markup on hyperlinks
Pass only training data to the grid search
Add final evaluation on test set

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Wrong readme.md

In infrence code, it sould be infrence.py, not train.py

Thanks for spotting this!


Issue with user table on denying doctor

Sometime when we deny a doctor the UserId is not cleared from the doctor table. This causes an error when a new user is added, who might get the same userId as the previously deleted one causing him to be a doctor when he is not.

Resolved in the latest version!!


 Last update e11702c...c11533a

LG


Cannot detect multiple devices on 2x p150 machine

yyzo-bh-01 is 2x p150 but running tt_SiliconDriver::detect_available_device_ids() only returns one device. Not sure if this is a UMD issue or something wrong with the machine.

I'm detecting 2 devices.
ls /dev/tenstorrent also returns 2 devices
This was mu reservation command for ird, did you indeed take 2 cards?
ird reserve --docker-image ghcr.io/tenstorrent/tt-metal/tt-metalium/ubuntu-20.04-amd64:v0.52.0-rc4-dev --timeout max blackhole --machine yyzo-bh-01 --num-pci 2
Note that create-ethernet-map still doesn't work for blackhole, so somewhere in the code we might just assume 1 card in the cluster. But enumerate_device, which just lists /dev/tenstorrent seems to be working.
Can you double check, and if it still doesn't work please provide steps for reproducing the issue

Ah user error, I didn't add --num-pci 2 last night when I tried this. But I confirmed that create-eth-map does not work for BH

Will be supported after #235


Dashboard: Spread (2)

This is the histogram of number of complaints each month for a given complaint type


Extended cell mouse events

Is there any way to access the mousedown or mouseup events, similar to the click event with onCellClicked?
The reason I'm asking is that we're keen to implement a multi row selection by clicking on a marker column cell and dragging the mouse down / up, similar to what Google Sheets or Apple Numbers does.

There is no access to these events. That said this is a great idea and I will add this to 5.2.0 prior to launch. No reason I can think of not to.

Amazing! Thank you

This is fixed in 5.2.0-beta2

Works nicely 👌

This is related. I guess it should only select if it’s not already a
selected cell.
On Tue, Oct 18, 2022 at 4:07 PM Thomas Winter @.***>
wrote:

I did some further tests with the 5.2.0-beta2 release and ran into an
issue with the onCellContextMenu callback which I'm not sure if it's
related to this change, or perhaps even new expected behaviour?
When I have a row selection and right click on any of the cells within
that collection, it clears the row selection and selects just that cell.
Previously it would keep the row selection.
This is our onCellContextMenu callback
const onCellContextMenu = useCallback(
(cell, event) => {
setContextMenuRow(cell[1]);
event.preventDefault();
},
[contextMenuRow]
);
I made a couple of screen recordings. Please let me know if you need any
further information
5.2.0-beta2
https://user-images.githubusercontent.com/5445640/196532689-d3d2f5bf-26dd-4dae-bcf5-c27d23dfe9dc.mov
5.1.4
https://user-images.githubusercontent.com/5445640/196532718-cae7230e-e9fc-4ee3-945a-2e2bacaccf07.mov
—
Reply to this email directly, view it on GitHub
https://github.com/glideapps/glide-data-grid/issues/532#issuecomment-1282940814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAHN22NBOMYEC5RD5ZLHFLWD37NDANCNFSM6AAAAAARCVPUZQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Please try 5.2.0-beta3

Yes, that works, maintaining the selection when right clicking on one.
One thing that doesn't quite make sense to me is that when you right click on the marker cell, it selects the first column. Should this select the whole row instead?


Fix OffchainOpRollupVotingSubmitResultAction submitted weight when member has not voted

Bug:
return createVote({
  proposalId: proposalHash,
  sig: voteData?.sig || '0x',
  timestamp: voteData ? Number(voteData.msg.timestamp) : 0,
  voteYes: voteData?.msg.payload.choice === VoteChoicesIndex.Yes,
  weight: memberBalancesAtSnapshot[i],
});

Fix:
return createVote({
  proposalId: proposalHash,
  sig: voteData?.sig || '0x',
  timestamp: voteData ? Number(voteData.msg.timestamp) : 0,
  voteYes: voteData?.msg.payload.choice === VoteChoicesIndex.Yes,
  weight: voteData ? memberBalancesAtSnapshot[i] : '0',
});

Related: https://github.com/openlawteam/snapshot-js-erc712/issues/28


Remove support for the unimplemented v2 series submission

A "new" v2 is in the works, but let's clear out the "old" v2 first to
avoid confusion.
Describe how to test your changes

Verify that metrics still work.
Verify that we haven't been using use_v2_api.series internally, much less with customers.

Checklist

[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] The appropriate team/.. label has been applied, if known.
[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.

Ah, this isn't enough -- the serialization for v2 is also "old".

It looks like sketches are always v2.
It appears events are also v1 (https://docs.datadoghq.com/api/latest/events/ contains "/v1/") but I haven't removed the v2 functionality here as I'm limiting scope to just series.


Document MySQL user privileges

Minion version: latest
Perl version: 5.16
Operating system: centos

Hello,
I've tried to install our worker on the new machine and I face some mysql errors:
DBD::mysql::st execute failed: TRIGGER command denied to user<EMAIL_ADDRESS>for table 'mojo_pubsub_notify' at /usr/local/share/perl5/Mojo/mysql/Database.pm line 47
If it's possible please mention what are the required privileges for minion to run.
Thanks,
Ovidiu

I'm sorry, but MySQL is not supported by Minion.

It was never supported? Because I'm using it successfully :) It work now as I just added the TRIGGER privilege.
Anyway, it would be very nice to be supported because mysql is our main db. We use it with mysql since about 3-4 months ago and this is the first time we encounter a problem with it.

There's a 3rd party module Minion::Backend::mysql on CPAN, you might want to contact its author instead.