text:
Add modulation matrix

Modulation matrix update
This model is operational and it can handle CC.
Support

Amplitude
Pan
Width
Position
Pitch
Volume

Not much tested yet, also I will clean old source which is made obsolete by this.
This will also make obsolete #326.
The CC list will be obtainable by inspecting matrix edges of CC source. Also it permits to have access to the target, and determine a useful name for the midnam item.

There is some EventEnvelopesT code #if 0'd in the removal commit above. I'm not sure yet what to replace it with.
I removed all old things regarding modifiers.

The commit 51b7322 ensures to always run the modulation source, even if no voice uses it.
This ensures the CC will continue to smooth in the back, even with no voice playing.

@paulfd this faces a problem with the smooth filter shortcut..
For instance I'm smoothing pitch CC at center 600, value 1200.
The filter basically stops rising at around 599,121033, and it's too far off of the virtuallyZero` difference threshold such that shortcutting would be possible.
What to do in this case? consider relative difference?

There is some EventEnvelopesT code #if 0'd in the removal commit above. I'm not sure yet what to replace it with.
I removed all old things regarding modifiers.

You can remove it I think, these tests were not great and we can make better ones for the FlexEGs

@paulfd this faces a problem with the smooth filter shortcut..
For instance I'm smoothing pitch CC at center 600, value 1200.
The filter basically stops rising at around 599,121033, and it's too far off of the virtuallyZero` difference threshold such that shortcutting would be possible.
What to do in this case? consider relative difference?

Hmm I'd say yes, but is it OK on both ends ? (e.g. for small values too)

but is it OK on both ends ? (e.g. for small values too)

hmm, as a relative distance, how about:
(abs(x-y)) / (abs(y)+virtuallyZero)

Yes that seems reasonable.

The only remaining feature that I can see missing, it's a modulation affecting the depth of another modulation.
eg. lfoN_amplitude_onccX
This will be a feature for another PR.

authors: jpcima paulfd

repo: sfztools/sfizz


text:
OpenAI speculative execution

The current frontend using OpenAI will invoke multiple calls for the example below:
@sgl.function
def example(s):
  s += "Construct a character."
  s += "Name: " + gen("name") + " Birthday: " + gen("birthday") + " Job: " + gen("job")

We can optimize this to send less number of calls to save money:

Gen longer in the first gen call, and skip the later if the first gen did the right thing.
Allow using OpenAI's n=10 keyword argument to sample multiple completions when forked. We can also provide the interface example.run(n=10).

@Ying1123 see this PR https://github.com/sgl-project/sglang/pull/48

This team is fast! Thanks guys. Will update you here on the integration on our end

Completion supported in #48.

source: gharchive/issue

authors: Ying1123 okhat parasol-aser

repo: sgl-project/sglang

license_type: permissive

license_source: github-api


text:
adapt vllm distributed module to sglang

Motivation

Modifications

Move vllm distributed module (v0.6.4.post1) to sglang, and current model is stilll using vllm.distributed module
Checklist

[ ] Format your code according to the Contributor Guide.
[ ] Add unit tests as outlined in the Contributor Guide.
[ ] Update documentation as needed, including docstrings or example tutorials.

What to do Next

[ ] Install sgl-kernel for custom allreduce and replace vllm.distributed to sglang.srt.distributed
[ ] Add tensorrt allreduce module

QQ why not use the v0.6.4.post1

I see pyproject.toml require vllm>=0.6.3.post1

This is to maintain compatibility, 0.6.3.post1 uses torch 2.4, and 0.6.4.post1 uses torch 2.5.1. The current main branch is compatible with both torch 2.4 and torch 2.5.1. Regarding the distributed part, I suggest directly updating to v0.6.4.post1

ok

isort....................................................................Failed
- hook id: isort
- files were modified by this hook

Fixing /home/runner/work/sglang/sglang/python/sglang/srt/_custom_ops.py

I think the test failed is caused by pr #2266

source: gharchive/pull-request


text:
docs: update README.md

acheives -> achieves

Thanks. I corrected it.

authors: eltociear sh-lee-prml

repo: sh-lee-prml/PeriodWave

license: MIT


text:
Using ISO pre-install template

Hi sh0rez,
I using another method to approach customize vSphere VM using pre-install ISO which more generic way.
Not sure if this is good way. Welcome to discuss if you are interesting.
Regards,
Elsvent

Hi!
I appreciate your work, but I believe this is out of scope here. But I would be happy to link it as an alternative way in the README. It looks like you deleted your repository, so would you mind restoring it from this PR?

Sorry, I must delete this accidentally. Fortunately, I got backup from my previous company.
I will Close and create a new PR.

license: Unlicense


text:
[Bug]: Items not selectable for newly added Command component

Describe the bug
When utilizing a Command component that has been added/updated as of 03/07/2024 ~6PM PST, items cannot be clicked and are disabled. (Additionally some examples using command in the docs are incorrect)
Additionally, <CommandItem>s that are not surrounded by a <CommandList> will crash the application and upon opening the Command component, the error: TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator)) will be thrown.
This is due to cmdk making a new release with breaking changes: https://github.com/pacocoursey/cmdk/releases
Workaround
This can be fixed by pinning cmdk version to 0.2.1 in package.json
Haven't investigated shadcn fix yet.
Affected component/components
Command
How to reproduce

Run npx shadcn-ui@latest add command after 03/07/2024
Try to use command component

Codesandbox/StackBlitz link
https://codesandbox.io/p/devbox/shadcn-playground-forked-4xxqcw?workspaceId=2d1a1544-9936-4d36-a113-0092357e5e51
Logs
No response
System Info
cmdk v1.0.0

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Some notes, seems like  needs to be contained somewhere within a .  is no longer sufficient. Upon doing this however, items are no longer selectable with shadcn/ui

I'm face same issue

+1

I encountered a similar problem when using the Combobox, but in my situation, the issue wasn't that it was unclickable or "disabled"; rather, the application would crash whenever the Combobox was opened. This is what I ran into for anyone googling this error:
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
This is also solved by pinning cmdk version to 0.2.1 in package.json for now. Thanks @jhnguyen521

I encountered a similar problem when using the Combobox, but in my situation, the issue wasn't that it was unclickable or "disabled"; rather, the application would crash whenever the Combobox was opened. This is what I ran into for anyone googling this error:
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
This is also solved by pinning cmdk version to 0.2.1 in package.json for now. Thanks @jhnguyen521

Hey, I forgot to put in the error, but this is likely because you don't have a <CommandList> enclosing your <CommandItems> as I mentioned above:

Some notes, seems like  needs to be contained somewhere within a .  alone is no longer sufficient. Upon doing this however, items are now disabled with shadcn/ui

I encountered a similar problem when using the Combobox, but in my situation, the issue wasn't that it was unclickable or "disabled"; rather, the application would crash whenever the Combobox was opened. This is what I ran into for anyone googling this error:
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
This is also solved by pinning cmdk version to 0.2.1 in package.json for now. Thanks @jhnguyen521

Hey, I forgot to put in the error, but this is likely because you don't have a <CommandList> enclosing your <CommandItems> as I mentioned above, the cmdk version seems to have changed this behavior.
Some of the examples for the Command component are incorrect (which I also copy-pastaed (: ) and don't use a <CommandList> which I've also updated in the PR:

Some notes, seems like <CommandItem> needs to be contained somewhere within a <CommandList>. <CommandGroup> alone is no longer sufficient. Upon doing this however, items are now disabled with shadcn/ui

Try just putting a <CommandList> around your existing <CommandGroup>s under the Usage example here: https://ui.shadcn.com/docs/components/command

This is totally the issue, adding the  <CommandList>  around your <CommandItem>'s resolves the TypeError.
Any thought on if we should be wrapping <CommandList> above <CommandGroup> or below?
Updating the examples will resolve the crash issue for future users, but the "aria-disabled" breaking change will still need to be updated so anyone with this issue should keep 0.2.1 pinned in their package.json until https://github.com/shadcn-ui/ui/pull/2945 is merged by changing
   "cmdk": "^1.0.0" or similar
to
    "cmdk": "0.2.1"
Thanks again @jhnguyen521!

I also had to remove data-[disabled]:pointer-events-none data-[disabled]:opacity-50 from here
const CommandItem = React.forwardRef<
    React.ElementRef<typeof CommandPrimitive.Item>,
    React.ComponentPropsWithoutRef<typeof CommandPrimitive.Item>
>(({ className, ...props }, ref) => (
    <CommandPrimitive.Item
        ref={ref}
        className={cn(
            'relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-selected:bg-accent aria-selected:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50',
            className,
        )}
        {...props}
    />
))

Which makes me then wonder, what was it doing in the first place :)

Any thought on if we should be wrapping <CommandList> above <CommandGroup> or below?

I believe it should be above <CommandGroup> according to all the examples, additionally enclosing <CommandEmpty> but I think it works either way 🤷

I also had to remove data-[disabled]:pointer-events-none data-[disabled]:opacity-50 from here
const CommandItem = React.forwardRef<
    React.ElementRef<typeof CommandPrimitive.Item>,
    React.ComponentPropsWithoutRef<typeof CommandPrimitive.Item>
>(({ className, ...props }, ref) => (
    <CommandPrimitive.Item
        ref={ref}
        className={cn(
            'relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-selected:bg-accent aria-selected:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50',
            className,
        )}
        {...props}
    />
))

Which makes me then wonder, what was it doing in the first place :)

Ignore this, I missed the post about changing to data-[disabled='true'], so I just replaced those classes accordingly
I''ve also moved the position of <CommandList> as per the examples, and my combo-box is working again as it should

like @shainegordon said, I had to adjust the styles to fix this
const CommandItem = React.forwardRef<
  React.ElementRef<typeof CommandPrimitive.Item>,
  React.ComponentPropsWithoutRef<typeof CommandPrimitive.Item>
>(({ className, ...props }, ref) => (
  <CommandPrimitive.Item
    ref={ref}
    className={cn(
      "relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-base outline-none aria-selected:bg-accent aria-selected:text-accent-foreground data-[disabled='true']:pointer-events-none data-[disabled='true']:opacity-50",
      className
    )}
    {...props}
  />
));

note the change data-[disabled='true']

I had the same issue when updating to cmdk v1. I resolved the issue following your advices:

I added CommandList in the tree;
I replaced data-[disabled] by data-[disabled='true'].

Thank you! 🙏🏻

shadcn should lock the dependency version to avoid these bugs due to updates

+1 Onclick interactions doesn't work

Maybe you don't change all the data-[disabled] to data-[disabled='true'].
I'm facing the same issues, but when I see it again, I just change one data-[disabled], but it actually have two.
When I change it all, it works fine.

The solution I use:
In @/components/ui/command.tsx file, you can change the classname on line 120 as follows: "relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-selected: bg-accent aria-selected:text-accent-foreground data-[disabled=true]:pointer-events-none data-[disabled=true]:opacity-50"

The component was built on version 0.2.1, but it automatically updated to version 1.0.0, indicating a major release. This could be due to the automatic incrementation of major versions when installing shadcn

I had the same issue and fixed with
adding CommandList in the tree (check shadcn docs)
I replaced data-[disabled] by data-[disabled='true']. I just don't like that but it's working

I had the same issue and fixed with adding CommandList in the tree (check shadcn docs) I replaced data-[disabled] by data-[disabled='true']. I just don't like that but it's working

you can downgrade the cmdk into previous version 0.2.1

I had the same issue and fixed with adding CommandList in the tree (check shadcn docs) I replaced data-[disabled] by data-[disabled='true']. I just don't like that but it's working

This. Just wrapped my CommandGroup with CommandList and it works now...

I also had to remove data-[disabled]:pointer-events-none data-[disabled]:opacity-50 from here
const CommandItem = React.forwardRef<
    React.ElementRef<typeof CommandPrimitive.Item>,
    React.ComponentPropsWithoutRef<typeof CommandPrimitive.Item>
>(({ className, ...props }, ref) => (
    <CommandPrimitive.Item
        ref={ref}
        className={cn(
            'relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-selected:bg-accent aria-selected:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50',
            className,
        )}
        {...props}
    />
))

Which makes me then wonder, what was it doing in the first place :)

thanks for the solution, I also wonder this now 😂😂😂

Still getting this issue, the fixes listed above work - however clicking on a CommandItem doesn't close the popover, leaving a meh UX

Tahnks for the solutions it works after removing  data-[disabled]:pointer-events-none data-[disabled]:opacity-50
I wonder if this will be fixed soon.

Thanks for the solutions it works after removing data-[disabled]:pointer-events-none data-[disabled]:opacity-50 I wonder if this will be fixed soon.

This is correct and I hope we will have an official fix soon in next version

I've used  to wrap both  and , but I encountered an unusual issue. Upon inspecting my console, I've noticed a multiple warnings indicating that children within the  components share the same key.

Warning: Encountered two children with the same key, 44. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

This warning isn't isolated to just one item; it applies to all . It appears that  attempts to render twice with identical keys. I resolved this by appending the map index to my unique ID. The fact that this solution works confirms that the component mounts twice simultaneously.
That aside, there's a huge lag when the button is clicked to the popover appearing, further confirming my thesis.
<PopoverContent className="w-[300px] p-0">
  <Command>
    <CommandInput placeholder="Search country..." />
    <CommandList>
      <CommandEmpty>No country found.</CommandEmpty>
      <CommandGroup>
        {countries.map((country, idx) => (
          <CommandItem
            key={`${country.value}-${idx.toString()}`} // without `idx`, you'll get duplicate key error
            value={country.label}
            onSelect={() => doStuff()}
            }}
          >
            {country.label}
          </CommandItem>
        ))}
      </CommandGroup>
    </CommandList>
  </Command>
</PopoverContent>

0.2.1

clicking on a CommandItem doesn't close the popover

I've used ^0.2.0 in different projects, works great for me

I've used ^0.2.0 in different projects, works great for me

Did you make any modifications to the CommandItem classnames?, here's mine;
<CommandPrimitive.Item
ref={ref}
className={cn(
"relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-[selected='true']:bg-accent aria-[selected='true']:text-accent-foreground data-[disabled='true']:pointer-events-none data-[disabled='true']:opacity-50",
className
)}
{...props}
/>

This is what I have
const CommandItem = React.forwardRef<
  React.ElementRef<typeof CommandPrimitive.Item>,
  React.ComponentPropsWithoutRef<typeof CommandPrimitive.Item>
>(({ className, ...props }, ref) => (
  <CommandPrimitive.Item
    ref={ref}
    className={cn(
      "relative flex cursor-pointer select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-selected:bg-accent aria-selected:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50",
      className
    )}
    {...props}
  />
));

As mentioned above by folks, the difference might be data-[disabled='true'] as I only have data-[disabled] for this version. (^0.2.0)

Figured out the issue, in cmdk changenotes: The aria-disabled and aria-selected props will now be set to false, instead of being undefined in https://github.com/pacocoursey/cmdk/commit/c57e6b7f81a5796395c7a016d6b1b2aac9591973
It seems that the data-disabled prop is also set to false whereas before the property would not exist at all until being disabled, and data-[disabled]:pointer-events-none will apply even for data-disabled="false".
The fix is to replace data-[disabled] with data-[disabled='true']. This should be backwards compatible too! :) I see that shadcn/ui uses data-[disabled] in numerous places, may be worth fixing this behavior everywhere. Going to make a PR.

This works like a charm

Figured out the issue, in cmdk changenotes: The aria-disabled and aria-selected props will now be set to false, instead of being undefined in https://github.com/pacocoursey/cmdk/commit/c57e6b7f81a5796395c7a016d6b1b2aac9591973
It seems that the data-disabled prop is also set to false whereas before the property would not exist at all until being disabled, and data-[disabled]:pointer-events-none will apply even for data-disabled="false".
The fix is to replace data-[disabled] with data-[disabled='true']. This should be backwards compatible too! :) I see that shadcn/ui uses data-[disabled] in numerous places, may be worth fixing this behavior everywhere. Going to make a PR.

Legend! Thank you 🙏

replace data-[disabled]: with data-[disabled=true]: in components/ui/command.tsx
https://stackoverflow.com/a/78308802/11438881

@jhnguyen521  you are doing great job, such a motivation. I am working on creating Multiselect component in this fashion using Popover (radix-ui/shadcn) with cmdk 1.0.0 but facing the same TypeError issue.  I tried using multiple solution from above thread but none worked and issue is randomly occuring. Can you please have a look?
Following is the code.
`import { Command as CommandPrimitive, useCommandState } from 'cmdk'
import { X } from 'lucide-react'
import * as React from 'react'
import { forwardRef, useEffect } from 'react'
import { Badge } from '@/components/shadcn/Badge'
import { Command, CommandGroup, CommandItem, CommandList } from '@/components/shadcn/Command'
import { cn } from '@/utils'
import { Popover, PopoverContent, PopoverTrigger } from './Popover'
export interface Option {
value: string
label: string
disable?: boolean
/** fixed option that can't be removed. /
fixed?: boolean
/* Group the options by providing key. */
[key: string]: string | boolean | undefined
}
interface GroupOption {
[key: string]: Option[]
}
interface MultiSelectProps {
values?: string[]
defaultOptions?: Option[]
/** manually controlled options /
options?: Option[]
placeholder?: string
/* Loading component. /
loadingIndicator?: React.ReactNode
/* Empty component. /
emptyIndicator?: React.ReactNode
/* Debounce time for async search. Only work with onSearch. /
delay?: number
triggerSearchOnFocus?: boolean
/* async search /
onSearch?: (value: string) => Promise<Option[]>
onChange?: (values: string[]) => void
/* Limit the maximum number of selected options. /
maxSelected?: number
/* When the number of selected options exceeds the limit, the onMaxSelected will be called. /
onMaxSelected?: (maxLimit: number) => void
/* Hide the placeholder when there are options selected. /
hidePlaceholderWhenSelected?: boolean
disabled?: boolean
groupBy?: string
className?: string
badgeClassName?: string
selectFirstItem?: boolean
/* Allow user to create option when there is no option matched. /
creatable?: boolean
/* Props of Command /
commandProps?: React.ComponentPropsWithoutRef
/* Props of CommandInput */
inputProps?: Omit<React.ComponentPropsWithoutRef, 'value' | 'placeholder' | 'disabled'>
}
export interface MultiSelectRef {
selectedValue: Option[]
input: HTMLInputElement
focus: () => void
}
export const useDebounce = <T,>(value: T, delay?: number): T => {
const [debouncedValue, setDebouncedValue] = React.useState(value)
useEffect(() => {
const timer = setTimeout(() => setDebouncedValue(value), delay || 500)
return () => {
  clearTimeout(timer)
}

}, [value, delay])
return debouncedValue
}
const transToGroupOption = (options: Option[], groupBy?: string) => {
if (options.length === 0) {
return {}
}
if (!groupBy) {
return {
'': options,
}
}
const groupOption: GroupOption = {}
options.forEach((option) => {
const key = (option[groupBy] as string) || ''
if (!groupOption[key]) {
groupOption[key] = []
}
groupOption[key].push(option)
})
return groupOption
}
const removePickedOption = (groupOption: GroupOption, picked: Option[]) => {
const cloneOption = JSON.parse(JSON.stringify(groupOption)) as GroupOption
for (const [key, value] of Object.entries(cloneOption)) {
cloneOption[key] = value.filter((val) => !picked.find((p) => p.value === val.value))
}
return cloneOption
}
const CommandEmpty = forwardRef<HTMLDivElement, React.ComponentProps>(
({ className, ...props }, forwardedRef) => {
const render = useCommandState((state) => state.filtered.count === 0)
if (!render) return null

return (
  <div
    ref={forwardedRef}
    className={cn('py-3 text-center text-sm', className)}
    // eslint-disable-next-line react/no-unknown-property
    cmdk-empty=""
    role="presentation"
    onFocus={() => alert()}
    {...props}
  />
)

},
)
CommandEmpty.displayName = 'CommandEmpty'
export const MultiSelect = React.forwardRef<MultiSelectRef, MultiSelectProps>(
(
{
values,
onChange,
placeholder,
defaultOptions: arrayDefaultOptions = [],
options: arrayOptions,
delay,
onSearch,
loadingIndicator,
emptyIndicator,
maxSelected = Number.MAX_SAFE_INTEGER,
onMaxSelected,
hidePlaceholderWhenSelected,
disabled,
groupBy,
className,
badgeClassName,
selectFirstItem = true,
creatable = false,
triggerSearchOnFocus = false,
commandProps,
inputProps,
}: MultiSelectProps,
ref: React.Ref,
) => {
const inputRef = React.useRef(null)
const [open, setOpen] = React.useState(false)
const [isLoading, setIsLoading] = React.useState(false)
const getSelectedOptions = () =>
  (arrayDefaultOptions || arrayOptions).filter((option) => values?.includes(option.value))

const [selected, setSelected] = React.useState<Option[]>(getSelectedOptions() || [])
const [options, setOptions] = React.useState<GroupOption>(transToGroupOption(arrayDefaultOptions, groupBy))
const [inputValue, setInputValue] = React.useState('')
const debouncedSearchTerm = useDebounce(inputValue, delay || 500)

React.useImperativeHandle(
  ref,
  () => ({
    selectedValue: [...selected],
    input: inputRef.current as HTMLInputElement,
    focus: () => inputRef.current?.focus(),
  }),
  [selected],
)

const handleUnselect = React.useCallback(
  (option: Option) => {
    const newOptions = selected.filter((s) => s.value !== option.value)
    setSelected(newOptions)
    onChange?.(newOptions.map(({ value }) => value))
  },
  [onChange, selected],
)

const handleKeyDown = React.useCallback(
  (e: React.KeyboardEvent<HTMLDivElement>) => {
    const input = inputRef.current
    if (input) {
      if (e.key === 'Delete' || e.key === 'Backspace') {
        if (input.value === '' && selected.length > 0) {
          handleUnselect(selected[selected.length - 1])
        }
      }
      // This is not a default behaviour of the <input /> field
      if (e.key === 'Escape') {
        input.blur()
      }
    }
  },
  [handleUnselect, selected],
)

useEffect(() => {
  if (values) {
    setSelected(getSelectedOptions())
  }
}, [values])

useEffect(() => {
  /** If `onSearch` is provided, do not trigger options updated. */
  if (!arrayOptions || onSearch) {
    return
  }
  const newOption = transToGroupOption(arrayOptions || [], groupBy)
  if (JSON.stringify(newOption) !== JSON.stringify(options)) {
    setOptions(newOption)
  }
}, [arrayDefaultOptions, arrayOptions, groupBy, onSearch, options])

useEffect(() => {
  const doSearch = async () => {
    setIsLoading(true)
    const res = await onSearch?.(debouncedSearchTerm)
    setOptions(transToGroupOption(res || [], groupBy))
    setIsLoading(false)
  }

  const exec = async () => {
    if (!onSearch || !open) return

    if (triggerSearchOnFocus) {
      await doSearch()
    }

    if (debouncedSearchTerm) {
      await doSearch()
    }
  }

  void exec()
}, [debouncedSearchTerm, groupBy, open, triggerSearchOnFocus])

const CreatableItem = () => {
  if (!creatable) return undefined

  const Item = (
    <CommandItem
      value={inputValue}
      className="cursor-pointer"
      onMouseDown={(e) => {
        e.preventDefault()
        e.stopPropagation()
      }}
      onSelect={(value: string) => {
        if (selected.length >= maxSelected) {
          onMaxSelected?.(selected.length)
          return
        }
        setInputValue('')
        const newOptions = [...selected, { value, label: value }]
        setSelected(newOptions)
        onChange?.(newOptions.map(({ value }) => value))
      }}
    >{`Create "${inputValue}"`}</CommandItem>
  )

  // For normal creatable
  if (!onSearch && inputValue.length > 0) {
    return Item
  }

  // For async search creatable. avoid showing creatable item before loading at first.
  if (onSearch && debouncedSearchTerm.length > 0 && !isLoading) {
    return Item
  }

  return undefined
}

const EmptyItem = React.useCallback(() => {
  if (!emptyIndicator) return undefined

  // For async search that showing emptyIndicator
  if (onSearch && !creatable && Object.keys(options).length === 0) {
    return (
      <CommandItem value="-" disabled>
        {emptyIndicator}
      </CommandItem>
    )
  }

  return <CommandEmpty>{emptyIndicator}</CommandEmpty>
}, [creatable, emptyIndicator, onSearch, options])

const selectables = React.useMemo<GroupOption>(() => removePickedOption(options, selected), [options, selected])

/** Avoid Creatable Selector freezing or lagging when paste a long string. */
const commandFilter = React.useCallback(() => {
  if (commandProps?.filter) {
    return commandProps.filter
  }

  if (creatable) {
    return (value: string, search: string) => {
      return value.toLowerCase().includes(search.toLowerCase()) ? 1 : -1
    }
  }
  // Using default filter in `cmdk`. We don't have to provide it.
  return undefined
}, [creatable, commandProps?.filter])

return (
  <Popover open={open} onOpenChange={setOpen}>
    <Command
      {...commandProps}
      onKeyDown={(e) => {
        handleKeyDown(e)
        commandProps?.onKeyDown?.(e)
      }}
      className={cn('overflow-visible bg-transparent', commandProps?.className)}
      shouldFilter={commandProps?.shouldFilter !== undefined ? commandProps.shouldFilter : !onSearch} // When onSearch is provided, we don't want to filter the options. You can still override it.
      filter={commandFilter()}
    >
      <PopoverTrigger onFocus={() => inputRef.current?.focus()}>
        <div
          className={cn(
            'group rounded-md border border-input p-[5px] text-base ring-offset-background focus-within:border-blue-700 focus-within:border-2',
            className,
          )}
        >
          <div className="flex flex-wrap gap-1 items-center">
            {selected.map((option) => {
              return (
                <Badge
                  key={option.value}
                  className={cn(badgeClassName)}
                  data-fixed={option.fixed}
                  data-disabled={disabled}
                  variant="subtle"
                >
                  {option.label}
                  <button
                    className={cn(
                      'ml-1 rounded-full outline-none ring-offset-background focus:ring-2 focus:ring-ring focus:ring-offset-2',
                      (disabled || option.fixed) && 'hidden',
                    )}
                    onKeyDown={(e) => {
                      if (e.key === 'Enter') {
                        handleUnselect(option)
                      }
                    }}
                    onMouseDown={(e) => {
                      e.preventDefault()
                      e.stopPropagation()
                    }}
                    onClick={() => handleUnselect(option)}
                    type="button"
                  >
                    <X className="h-3 w-3 text-muted-foreground hover:text-foreground" />
                  </button>
                </Badge>
              )
            })}
            {/* Avoid having the "Search" Icon */}

            <CommandPrimitive.Input
              {...inputProps}
              ref={inputRef}
              value={inputValue}
              disabled={disabled}
              onValueChange={(value) => {
                setInputValue(value)
                inputProps?.onValueChange?.(value)
              }}
              onBlur={(event) => {
                setOpen(false)
                inputProps?.onBlur?.(event)
              }}
              onFocus={(event) => {
                setOpen(true)
                triggerSearchOnFocus && onSearch?.(debouncedSearchTerm)
                inputProps?.onFocus?.(event)
              }}
              placeholder={hidePlaceholderWhenSelected && selected.length !== 0 ? '' : placeholder}
              className={cn(
                'flex-1 bg-transparent outline-none placeholder:text-muted-foreground',
                inputProps?.className,
              )}
            />
          </div>
        </div>
      </PopoverTrigger>
      <PopoverContent className="p-0">
        <CommandGroup className="w-full rounded-md border bg-popover text-popover-foreground shadow-md outline-none animate-in">
          {isLoading ? (
            <>{loadingIndicator}</>
          ) : (
            <>
              {EmptyItem()}
              {CreatableItem()}
              {!selectFirstItem && <CommandItem value="-" className="hidden" />}
              {Object.entries(selectables).map(([key, dropdowns]) => (
                <CommandList key={key} className="h-full overflow-auto">
                  <>
                    {dropdowns.map((option) => {
                      return (
                        <CommandItem
                          key={option.value}
                          value={option.value}
                          disabled={option.disable}
                          onMouseDown={(e) => {
                            e.preventDefault()
                            e.stopPropagation()
                          }}
                          onSelect={() => {
                            if (selected.length >= maxSelected) {
                              onMaxSelected?.(selected.length)
                              return
                            }
                            setInputValue('')
                            const newOptions = [...selected, option]
                            setSelected(newOptions)
                            onChange?.(newOptions.map(({ value }) => value))
                          }}
                          className={cn('cursor-pointer', option.disable && 'cursor-default text-muted-foreground')}
                        >
                          {option.label}
                        </CommandItem>
                      )
                    })}
                  </>
                </CommandList>
              ))}
            </>
          )}
        </CommandGroup>
      </PopoverContent>
    </Command>
  </Popover>
)

},
)
MultiSelect.displayName = 'MultiSelect'
`
Error appears randomly not every time [TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator)) which is very annoying and cannot go to production with cmdk 1.0.0.
Moreover I wrote a test case which always gets failed using this MultiSelect component.
This test case for sure failed every time with error [TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))] that catches the issue very easily.
it('handles keyboard interactions', async () => {
   const onChange = vi.fn()
   const { getByRole } = render(
     <MultiSelect
       options={[
         { value: '1', label: 'Option 1' },
         { value: '2', label: 'Option 2' },
       ]}
       onChange={onChange}
     />,
   )
   const multiselectElement = getByRole('combobox')
   fireEvent.keyDown(multiselectElement, { key: 'ArrowDown' })
   fireEvent.keyDown(multiselectElement, { key: 'Enter' })
 })

Any help would be appreciated. Here is sandbox link  Issue rarely happens but yes it happens, usually reproduced on backspace/enter pressed in combobox. But test case is failing that's catching the issue every time.

This is work for me
<FormField
  control={form.control}
  name="language"
  render={({ field, fieldState }) => (
    <FormItem className="flex flex-col">
      <FormLabelValidate
        label={'Language'}
        htmlFor="language"
        invalid={fieldState.invalid}
      />
      <Popover open={open} onOpenChange={setOpen}>
        <PopoverTrigger asChild>
          <FormControl>
            <Button
              variant="outline"
              role="combobox"
              className={cn(
                'w-[200px] justify-between',
                !field.value && 'text-muted-foreground',
              )}
            >
              {field.value
                ? languages.find(
                    (language) => language.value === field.value,
                  )?.label
                : 'Select language'}
              <CaretSortIcon className="ml-2 size-4 shrink-0 opacity-50" />
            </Button>
          </FormControl>
        </PopoverTrigger>
        <PopoverContent className="w-[200px] p-0">
          <Command>
            <CommandInput
              placeholder="Search language..."
              className="h-9"
            />
            <CommandList>
              <CommandEmpty>No language found.</CommandEmpty>
              <CommandGroup>
                {languages.map((language) => (
                  <CommandItem
                    value={language.label}
                    key={language.value}
                    onSelect={() => {
                      form.clearErrors('language')
                      form.setValue('language', language.value)
                      setOpen(false)
                    }}
                  >
                    {language.label}
                    <CheckIcon
                      className={cn(
                        'ml-auto size-4',
                        language.value === field.value
                          ? 'opacity-100'
                          : 'opacity-0',
                      )}
                    />
                  </CommandItem>
                ))}
              </CommandGroup>
            </CommandList>
          </Command>
        </PopoverContent>
      </Popover>
      <FormMessageValidate />
    </FormItem>
  )}
/>

CommandList

I had the same issue but after adding CommandList around CommandItem solved the problem. However, I had to change the disabled to equal true ("data-[disabled=true]:pointer-events-none data-[disabled=true]:opacity-50" instead of  "data-[disabled]:pointer-events-none data-[disabled]:opacity-50") so I can select the value I want.
(I hope this was a helpful 🙌)

so, are there any other solutions besides a hacky workaround?

This is work for me
<FormField
  control={form.control}
  name="language"
  render={({ field, fieldState }) => (
    <FormItem className="flex flex-col">
      <FormLabelValidate
        label={'Language'}
        htmlFor="language"
        invalid={fieldState.invalid}
      />
      <Popover open={open} onOpenChange={setOpen}>
        <PopoverTrigger asChild>
          <FormControl>
            <Button
              variant="outline"
              role="combobox"
              className={cn(
                'w-[200px] justify-between',
                !field.value && 'text-muted-foreground',
              )}
            >
              {field.value
                ? languages.find(
                    (language) => language.value === field.value,
                  )?.label
                : 'Select language'}
              <CaretSortIcon className="ml-2 size-4 shrink-0 opacity-50" />
            </Button>
          </FormControl>
        </PopoverTrigger>
        <PopoverContent className="w-[200px] p-0">
          <Command>
            <CommandInput
              placeholder="Search language..."
              className="h-9"
            />
            <CommandList>
              <CommandEmpty>No language found.</CommandEmpty>
              <CommandGroup>
                {languages.map((language) => (
                  <CommandItem
                    value={language.label}
                    key={language.value}
                    onSelect={() => {
                      form.clearErrors('language')
                      form.setValue('language', language.value)
                      setOpen(false)
                    }}
                  >
                    {language.label}
                    <CheckIcon
                      className={cn(
                        'ml-auto size-4',
                        language.value === field.value
                          ? 'opacity-100'
                          : 'opacity-0',
                      )}
                    />
                  </CommandItem>
                ))}
              </CommandGroup>
            </CommandList>
          </Command>
        </PopoverContent>
      </Popover>
      <FormMessageValidate />
    </FormItem>
  )}
/>

does scroll work for you?

For anyone new to community to resolve this you need to change this in:  components/ui/command.tsx
Where you installed the components not in the component you are building 🗡 . Hopefully this help someone.
replace data-[disabled]: with data-[disabled=true]: in components/ui/command.tsx

the scrollbar doesn't work

I also had to remove data-[disabled]:pointer-events-none data-[disabled]:opacity-50 from here
const CommandItem = React.forwardRef<
    React.ElementRef<typeof CommandPrimitive.Item>,
    React.ComponentPropsWithoutRef<typeof CommandPrimitive.Item>
>(({ className, ...props }, ref) => (
    <CommandPrimitive.Item
        ref={ref}
        className={cn(
            'relative flex cursor-default select-none items-center rounded-sm px-2 py-1.5 text-sm outline-none aria-selected:bg-accent aria-selected:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50',
            className,
        )}
        {...props}
    />
))

Which makes me then wonder, what was it doing in the first place :)

This is very interesting, because in tailwind, you cannot add multiple classes to different states, like hover/active/focus/disabled

Nothing is working for me: scroll, field focus, items mouse over. It is just static and I've applied all workaround suggested in here. I'm using react 18 and nextjs 14.2.4

I'm on the same boat as @paulofabiano
May I know what else need to be done beside downgrading  cmdk to 0.2.0?

I'm on the same boat as @paulofabiano
May I know what else need to be done beside downgrading cmdk to 0.2It.0?

It should be working by downgrading cmdk to 0.2.0?
<Popover>
  <PopoverTrigger asChild>
    <Button>OK</Button>
  </PopoverTrigger>
  <PopoverContent>
    <Command>
      <CommandInput></CommandInput>
      <CommandList>
        <CommandItem key="1" onSelect={() => console.log("first")}>
          123
        </CommandItem>
        <CommandItem key="2" onSelect={() => console.log("second")}>
          456
        </CommandItem>
      </CommandList>
    </Command>
  </PopoverContent>

replace data-[disabled]: with data-[disabled=true]: in components/ui/command.tsx
https://stackoverflow.com/a/78308802/11438881

This works well for me.
data-[disabled=true]:pointer-events-none data-[disabled=true]:opacity-50

Figured out the issue, in cmdk changenotes: The aria-disabled and aria-selected props will now be set to false, instead of being undefined in https://github.com/pacocoursey/cmdk/commit/c57e6b7f81a5796395c7a016d6b1b2aac9591973
It seems that the data-disabled prop is also set to false whereas before the property would not exist at all until being disabled, and data-[disabled]:pointer-events-none will apply even for data-disabled="false".
The fix is to replace data-[disabled] with data-[disabled='true']. This should be backwards compatible too! :) I see that shadcn/ui uses data-[disabled] in numerous places, may be worth fixing this behavior everywhere. Going to make a PR.

Works perfectly. Thank you!

Been hearing about Shadcn for a while, finally trying it out and one of the first components I try is buggy. Surprised this is still not fixed as of August. Thanks for the fix, though!

form.clearErrors('language')

saved me a lot of time. Thanks!

Seems like an issue still

I was playing around with the first example Combobox from the docs and even after applying the fixes it still breaks.

Tried going back to 0.2.0, still didn't work for me. Looks like I chose the wrong library

It’s an extremely simple fix, just do this - https://github.com/shadcn-ui/ui/issues/2944#issuecomment-1986062418
Rather don’t throw the baby out with the bath water, for a lot of use cases, this is actually an excellent “library”

Still broken. I tried everything in this thread:
Removing data-[disabled=true]:pointer-events-none and data-[disabled=true]:opacity-50.
Pinning "cmdk": "0.2.1"
Using onSelect.
Now remembering that this is what caused me to drop shadcn on a previous project -- combobox is a nightmare. It's generally worked for me for everything else, so i'm not ready to abandon it yet. But I totally empathize with people who try out shadcn, can get the boilerplate combobox to work, and abandon the library.

Go into your command.tsx component and do this
const CommandDialog = ({ children, ...props }: CommandDialogProps) => {
  return (
    <Dialog {...props}>
      <DialogContent className="overflow-hidden p-0">
        <Command className="[&_[cmdk-group-heading]]:px-2 [&_[cmdk-group-heading]]:font-medium [&_[cmdk-group-heading]]:text-zinc-500 [&_[cmdk-group]:not([hidden])_~[cmdk-group]]:pt-0 [&_[cmdk-group]]:px-2 [&_[cmdk-input-wrapper]_svg]:h-5 [&_[cmdk-input-wrapper]_svg]:w-5 [&_[cmdk-input]]:h-12 [&_[cmdk-item]]:px-2 [&_[cmdk-item]]:py-3 [&_[cmdk-item]_svg]:h-5 [&_[cmdk-item]_svg]:w-5">
            <CommandList>{children}</CommandList>
        </Command>
      </DialogContent>
    </Dialog>
 )
}

anybody got lucky with this issue? I'm well aware of the data-[disabled=true]:pointer-events-none data-[disabled=true]:opacity-50 workaround, which, upon installing the command component I see that it already had it, so I didn't need to make the change. However, it crashes the moment I select an option.
here's a sample usage:
   <FormField
          name="productTypes"
          render={({ field }) => (
            <FormItem>
              <FormLabel className="text-xs uppercase text-gray-400">
                Product Types
              </FormLabel>
              <FormControl>
                <div className="relative">
                  <Command onKeyDown={(e) => e.stopPropagation()}>
                    <CommandInput
                      placeholder="Select an option"
                      value={
                        options.find(
                          (opt) => opt.value === selectedOption,
                        )?.label || ''
                      }
                      onFocus={() => setIsOpen(true)}
                    />
                    {isOpen && (
                      <CommandList className="absolute z-10 w-full rounded-lg bg-white shadow-md">
                        <CommandEmpty>No options found.</CommandEmpty>
                        <CommandGroup>
                          {hardcodedOptions.map((option) => (
                            <CommandItem
                              key={option.value}
                              onSelect={() => handleSelectOption(option.value)}
                            >
                              {option.label}
                            </CommandItem>
                          ))}
                        </CommandGroup>
                      </CommandList>
                    )}
                  </Command>
                </div>
              </FormControl>
              <FormMessage />
            </FormItem>
          )}
        />

A bit strange to see that the issue is still there despite the particular cmdk related fixes being applied. Has anyone found a workaround? Not sure if downgrading to 0.2.1 is the right way to go here.

Any chance some of this behavior has resurfaced recently?  These comboboxes were working fine for me a 1-2 weeks ago and now I can't select any of the options, despite not making any related code changes or library upgrades.
My command component already has the data-[disabled=true] fix. It had been working fine for me on cmdk 1.0.0 and downgrading to 0.2.1 doesn't seem to fix it.

Any chance some of this behavior has resurfaced recently? These comboboxes were working fine for me a 1-2 weeks ago and now I can't select any of the options, despite not making any related code changes or library upgrades.
My command component already has the data-[disabled=true] fix. It had been working fine for me on cmdk 1.0.0 and downgrading to 0.2.1 doesn't seem to fix it.

Still not sure what broke this for me, but I found a fix by adding the modal prop to the Popover component of my combobox:
<Popover modal open={open} onOpenChange={setOpen}>

authors: ARiyou2000 Armadillidiid Babailan Danilo-A KhoaLee Kqan1 Liberty34 Malachite40 OmarKhattab RanitManik Sholamide ZubriQ abdasis abdulApp abolajibisiriyu apethree baxsm bdlowery benjamin-guibert bowen0110 collinversluis derrickstaten faintblack iamisti itxtoledo javed24 jhnguyen521 kyusungpark matowang myudak optimbro othman316 paulofabiano samofoke seanpquig shainegordon televators thomas-cruz tjhoo tuanvt vienpt youneszahzouh zahidiqbalnbs

repo: shadcn-ui/ui


text:
docs(www): update code highlight

Fix incorrect code highlight lines
Add missing useForm import

This PR is superseded by #1586


text:
refactor(www): update ThemeProviderProps type extraction for next-themes v0.4.0 compatibility

Since next-themes v0.4.0 no longer provides types in dist, replaced the import of ThemeProviderProps from next-themes/dist/types with a new type extraction using React.ComponentProps. This change ensures continued type safety and compatibility with the updated library version.

ThemeProviderProps is back as of 0.4.2: https://github.com/pacocoursey/next-themes/releases/tag/v0.4.2
But the import needs to be changed to be from next-themes instead of next-themes/dist/types

ThemeProviderProps is back as of 0.4.2: https://github.com/pacocoursey/next-themes/releases/tag/v0.4.2
But the import needs to be changed to be from next-themes instead of next-themes/dist/types
Duplicate PR: #5718

Thanks for the update! To ensure compatibility across versions, I've used React.ComponentProps to extract ThemeProviderProps. This approach works for both older versions (using next-themes/dist/types) and newer ones (v0.4.2+ with next-themes), supporting backward and forward compatibility.


text:
[CLI] : add src directory in tailwind.config

after using shadcn-ui init it should also add './src/**/*.{ts,tsx}' path in tailwind.config.js for src directory
 content: [
    "./pages/**/*.{ts,tsx}",
    "./components/**/*.{ts,tsx}",
    "./app/**/*.{ts,tsx}",
    "./src/**/*.{ts,tsx}",
  ],

I've created a pull request

I've encountered the same problem as my next project was originally initialized with a src dir. Not sure if specifically limiting the scope of tailwind parser to pages/app/components folder has any advantage or your fix ./src/**/* would work just fine, since all three are contained within src.

Maybe you can choose not include all these folders in the src folder all together when initializing a Next project from scratch with shadcn

That's a good point. However the original next.js app CLI provides an option to include src during initialization. And simply re-initialize a project to add shadcn UI library as a dependency might not be an option for some people.
Granted this is an easy fix, but it is confusing when the shad CLI doesn't support next options.

I believe this is fixed in the latest cli. Marking this as done. Feel free to reopen if not.

authors: TechTheAwesome kratos-respawned monstajoe2002 shadcn

repo: shadcn/ui


text:
Generate Visual Studio projects using Premake

This change adds a premake5.lua file that allows us to generate our Visual Studio solution using Premake 5 (https://premake.github.io/).
The existing Visual Studio solution/projects are now replaced with the Premake-generated ones, and project contributors will be expected to update these by running premake after adding/removing files.
I have not changed the Linux Makefile build at all, because that file is also used for things like running our tests, so that clobbering it with a premake-generated Makefile would break our continuous testing.
Hopefully future changes can switch to a generated Makefile and perhaps even add an XCode project as well.
Notes:

The build/slang-build.props file is no longer needed/used, so it has been removed.

The slang-eval-test test fixture wasn't following our naming conventions for its directory path, so it was updated to streamline the Premake build configuration work. This required changes to the Makefile as well

Some seemingly unncessary preprocessor definitions that were specified for core and slang-glslang have been dropped. We will see if anything breaks from that.

This is not anything to do with my interest in possibly moving our own code generation logic to Lua, although I can see how you might think that (if we had a custom code generation solution then it would start to make sense to consider using it to build project files...).
We were asked to consider using premake by a customer (since it would ease their work in customizing our build), and from looking at it I decided that it could streamline the task of maintaining native build files for different platforms (VS solution for windows, Makefile for Linux, and XCode project for MacOS).
Premake-generated project files can be checked in to source control so that developers who just want to start working with the Slang build don't need to worry about downloading Premake at all. This is unlike CMake, which is viral in that any time you want to build a CMake-based project you need to install and run (the correct version of) CMake yourself.
I'm not strongly attached to Premake over alternative project-file generators, but I am attached to the idea of not maintaining per-platform build files by hand in the long run.

repo: shader-slang/slang

license: mit

license_source: bigquery


text:
TLS problem: "user: Current not implemented on linux/amd64"

It works in http mode, but after I change server_port from 80 to 443 and add tls; to plugin_opts , plugin service exit unexpectedly. Error is "user: Current not implemented on linux/amd64".
I have change my Cloudflare domain SSL to Flexible.
My cert is issued by ~/.acme.sh/acme.sh --issue --dns dns_cf -d mydomain.me
and it issues successfully.
config.json (it works)
{
    "server":"0.0.0.0",
    "server_port":80,
    "local_port":1080,
    "password":"***",
    "timeout":60,
    "no_delay":true,
    "ipv6_first":true,
    "reuse_port":true,
    "method":"chacha20-ietf-poly1305",
    "plugin":"v2ray-plugin",
    "plugin_opts":"server;host=mydomain"
}

ss-server log
Mar 16 05:32:33 ubuntu01 ss-server[1974]: 2019/03/16 05:32:33 V2Ray 4.16 (Po) Custom
Mar 16 05:32:33 ubuntu01 ss-server[1974]: 2019/03/16 05:32:33 A unified platform for anti-censorship.
Mar 16 05:32:33 ubuntu01 ss-server[1974]: 2019/03/16 05:32:33 [Warning] v2ray.com/core: V2Ray 4.16 started

config.json (doesn't work)
{
    "server":"0.0.0.0",
    "server_port":443,
    "local_port":1080,
    "password":"***",
    "timeout":60,
    "no_delay":true,
    "ipv6_first":true,
    "reuse_port":true,
    "method":"chacha20-ietf-poly1305",
    "plugin":"v2ray-plugin",
    "plugin_opts":"server;tls;host=mydomain"
}

ss-server log (something wrong)
root@ubuntu01:~# cat /var/log/syslog |grep ss-server
Mar 16 05:43:46 ubuntu01 ss-server[2223]: 2019/03/16 05:43:46 V2Ray 4.16 (Po) Custom
Mar 16 05:43:46 ubuntu01 ss-server[2223]: 2019/03/16 05:43:46 A unified platform for anti-censorship.
Mar 16 05:43:46 ubuntu01 ss-server[2223]: 2019/03/16 05:43:46 user: Current not implemented on linux/amd64
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 ERROR: plugin service exit unexpectedly
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: resolving hostname to IPv6 address first
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: plugin "v2ray-plugin" enabled
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: UDP relay enabled
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: enable TCP no-delay
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: initializing ciphers... chacha20-ietf-poly1305
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: tcp server listening at 127.0.0.1:33045
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: tcp port reuse enabled
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: udp server listening at 0.0.0.0:443
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: udp port reuse enabled
Mar 16 05:43:46 ubuntu01 ss-server[2223]:  2019-03-16 05:43:46 INFO: running from root user

Problem was solved by compile v2ray-plugin from source on my Ubuntu Server

I have same problem. I think CGO_ENABLED=0 is the cause of the problem.
https://github.com/shadowsocks/v2ray-plugin/blob/4f8b2c58e14f63228a7b007bb103c0f9ac2a0788/build-release.sh#L34

authors: Mjollnirs TomFrank


text:
feat: Add PDF Loader

Summary
This PR add PDF loader for llmchain.
Closes https://github.com/shafishlabs/llmchain.rs/issues/6

Our unit test need token and is not work on PR from forked repo. Please add the condition for those tests. Take OpenDAL as an example: https://github.com/apache/incubator-opendal/blob/main/.github/workflows/service_test_azblob.yml#L78


text:
new like buttons to be add

I guess we need some new buttons with fill animation effect .somewhat .like-->

I like it. If you wanna work on it, please let me know to assign you!

And if not, please add it in the buttons ideas file for someone else to see it. Let me know!

I like it. If you wanna work on it, please let me know to assign you!

surely i would like to take this up

Great! I assigned you @Pratyush-Saxena

Hi @Pratyush-Saxena are you still working on it? Please either submit a PR by tomorrow or I'll have to unassign you to give other contributors a chance. Thank you.

Hi @Pratyush-Saxena are you still working on it? Please either submit a PR by tomorrow or I'll have to unassign you to give other contributors a chance. Thank you.

I guess it should be assigned to someone else . because I m not able to work right now ... @shahednasser you must unassign me .

No problem @Pratyush-Saxena  thank you for letting me know.

@shahednasser i would like to give this a try.

Sure @harsh863  I'll assign you

Any update on this @harsh863 ?

If no one is working on this can I work on this issue @shahednasser ???

Yes @dsnehasish74 as this issue has taken too long.

@shahednasser sorry I am not able to solve this problem for now , because I am little busy now .You can assign this to other . Sorry.

It's ok @dsnehasish74 I understand! Thank you for letting me know.

Hey, i would love to work on it, if nobody else do it. :)

Sure @BeniB98 I'll assign you.

repo: shahednasser/sbuttons


text:
Can't Build on iOS

I'm using the package all good in Android, but when I try to use it in iOS I'm stack in step 6.
My project didn't have a MY_PROJECT-bridging-header.h file.

I try creating one, and now I'm getting errors:
Swift Compiler Error -> 'RNVideoProcessing.h' file not found
Any suggestions, please?

I've done all the configuration again following the instructions on this video, and it is finally working. Thanks!.

I've done all the configuration again following the instructions on this video, and it is finally working. Thanks!.

Doesn't work for last version React Native 0.60+

authors: aelarassi soledaddiez


text:
How to make the video to full screen?

Current Behavior
Fixed size through props width and height
Expected Behavior
Full screen mode through flex: 1
Your Environment

software
version

react-native-video-processing
^2.0.0

react-native
~0.62.2

node
12.16

Here i use the Trimmer view if it can help.


text:
Issue while blocking chunk network requests

Hi all, while testing DASH contents, for example Big Buck Bunny: the Dark Truths of a Video Dev Cartoon (DASH) if you block network requests for a quality https://storage.googleapis.com/shaka-demo-assets/bbb-dark-truths/v-0720p-2500k-libx264.mp4 in order to simulate a CDN error but only for a video quality:

The player does not try to switch to another quality when streaming.retryParameters.maxAttempts limit is reached.

Is there a setting to request the player to switch to another quality when maxAttempts limit is reached
Is there a way to remove/disable a variant when HTTP_ERROR is thrown?

Thank you very much

We don't do that automatically, but it could be possible in a future version.  Today AbrManager chooses tracks, but not based on errors.  Ideally, we could ban (permanently or temporarily) a track with too many errors.  This is discussed in https://github.com/shaka-project/shaka-player/issues/1542

Perfect, thx!

@albertdaurell Your idea seems good and it seems that it may be related to https://github.com/shaka-project/shaka-player/issues/2541, are you interested in submitting a PR?

authors: albertdaurell avelad joeyparrish

repo: shaka-project/shaka-player


text:
Option to not use style-loader

Ruby version: 2.7.4
Rails version: ~> 5.2.6
Webpacker version: 6.1.1
Desired behavior:
mini-css-extract-plugin is capable of HMR now. I'd like the ability to opt into just using it all the time, even when HMR is set in webpacker.yml. I'd like to get style-loader out of the dev pipeline so that my development and production environments more closely match, while retaining HMR. It turns out this isn't too hard!
Actual behavior:
Currently, hmr: true in webpacker.yml sets Webpack.inlining_css?, which prevents stylesheet_pack_tag form emitting <link> tags for CSS, on the assumption that style-loader is in play. I monkey patched my install with:
class Webpacker::Instance
  def inlining_css?
    false
  end
end

And my Webpack css loader with:
// Swap all style-loader rules for mini-css-extract-plugin, even if HMR. MCEP supports HMR now.
const MiniCssExtractPlugin = require("mini-css-extract-plugin");
webpackConfig.module.rules.forEach((rule) => {
  if ("test.css".match(rule.test) || "test.scss".match(rule.test)) {
    rule.use = rule.use.map((loader) => {
      if (loader === "style-loader") {
        return MiniCssExtractPlugin.loader;
      } else {
        return loader;
      }
    });
  }
});

and it works just dandy.
The fix should be as simple as allowing the explicit disabling of inlining css (perhaps inlineCss: false in webpacker.yml), then updating the Webpack::Instance#inlining_css? method and its partner in shakapacker/package/inliningCss.js to respect the flag if it's set.

@cheald can you submit a PR? This sounds reasonable.
Yes, we can have inline_css inside of the HMR config.
@tomdracz, thoughts?

Sure, I whipped something up. If you have further direction on what you'd like to see, I'm happy to further improve it.

@cheald just i've got a rails 5 setup just wondering where you placed below code ?
I've tried lib/webpacker/instance_methods.rb
class Webpacker::Instance
  def inlining_css?
    false
  end
end

@matoni109 please see comments here: https://github.com/shakacode/shakapacker/pull/75/files

@justin808 good to close!

repo: shakacode/shakapacker


text:
🛑 Shakedown Social - Uploads is down

In 9f7dc9f, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 330 ms

Resolved: Shakedown Social - Uploads is back up in 3c30677.

repo: shakedown-social/upptime


text:
🛑 Shakedown Social - Uploads is down

In 972f206, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 298 ms

Resolved: Shakedown Social - Uploads is back up in fb4c0e9.


text:
Project status/dependencies

Hey mate! Really nice project!
This is exactly something I was looking for a project I'm working with bevy (a 3D editor) that I plan to use something like this to get some vim-like functionality.
I know the project is in it's early stages but I tried to add it as a dependency and I'm having issues with the dependencies (the  error shown below, related to text_style).
error: failed to select a version for the requirement `text-style = "^0.4.0"`
candidate versions found which didn't match: 0.3.0, 0.2.0, 0.1.1, ...
location searched: crates.io index
required by package `bevy_minibuffer v0.1.0-alpha.1 (https://github.com/shanecelis/bevy_minibuffer#c4db46ec)`
    ... which satisfies git dependency `bevy_minibuffer`

Just wanted to know what is the status of the project, and if you plan on releasing an 0.1.0 any time soon without this patched dependencies, or if I could be of help with anything for reaching this state.
Cheers and thanks for your work on this!

Hey! Thanks for the interest.
Yeah, the patched dependencies have kept me from releasing it. I had been using Asky, which is a terminal-centric plugin. But I'd decided to just rewrite Asky for bevy located in bevy_asky directly to avoid the patched dependencies, which would probably be more performant anyway. I got stalled on it because I started to kind of reach for the moon in terms of having a richer-than-just-text UI and the UI focus plugin wasn't working for a couple cases. (Specifically I couldn't get it to change focus between a group of checkboxes or radio buttons; I didn't file an issue though.) My plan was to get bevy_asky working then use that in bevy_minibuffer.
Now, if I were less ambitious, like I was before I saw Asky, I'd accept textual input, and then make every other input a variation of that. Then I'd finally be able to release bevy_minibuffer.
So in answer to your question, development is stalled but not abandoned. My attention isn't currently on fixing it right now. If you wanted to help, you could kick the tires of bevy_asky. I pushed a few commits, so that it's in a working state. It's the checkbox_group example that dragged me down. I notice too that I should file a PR to ui-navigation to update it to bevy-0.14.
Thanks for dropping me a line. Helps to motivate sometimes.

Hi @caprilesport, I made some headway on the focus problem that had stymied me. I haven't published bevy_asky yet, but I think you can do a little test drive on bevy_minibuffer now. The examples all work and demonstrate now to principle ways to query the user using async or using triggers.

Nevermind. Looks like I broke something important trying to get it into a kick-tires state. Bah.

Hey @shanecelis!
Nice to see the updates! I did a quick prototype here and it seems to be working fine! Hope to have some time soon to dive deeper.
Thanks a lot for the quick fix and the ping here! :)

authors: caprilesport shanecelis


text:
🛑 upload is down

In 0c1c119, upload ($UPLOAD_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: upload is back up in 4c1bc36 after 20 hours, 59 minutes.

repo: shaowenchen/upptime


text:
docs: use intersphinx for some external links

Overview
Description of the changes proposed in this pull request:

Uses intersphinx sphinx extension for providing some of our external links, e.g. to scipy or to scikit-learn. This way we also ensure that the links are not outdated (else sphinx would complain during build), and the links are not hardcoded.
fix some minor documentation build errors (such as improper indentation)

I'm okay with these changes, and I appreciate your ongoing efforts to improve the docs.
I am a little hesitant about the switch from full URLs to the intersphinx style. The full URLs are readable and useful when browsing the source code, whereas the intersphinx links are quite opaque in the source code but are better in the rendered docs. Overall I'm not sure if the improved docs are worth the more opaque source.
That said, I don't want to hold up this PR on something which is quite subjective so happy to approve.

I've thought a bit more about this, and I think for a large public package like this the rendered docs are probably read a great deal more than the source code of the docs. So, the tradeoff makes sense and I wholeheartedly support this PR :)

authors: connortann thatlittleboy

repo: shap/shap


text:
BUG: solve minimum_rotated_rectangle is incorrect in 2.0.0

Closes https://github.com/shapely/shapely/issues/1670
restore and vectorized the custom oriented_envelope to solve #1670
add a new test and remove duplicated tests for oriented_envelope and minimum_rotated_rectangle

Pull Request Test Coverage Report for Build 4026376213

33 of 33 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.4%) to 87.198%

Files with Coverage Reduction
New Missed Lines
%

shapely/constructive.py
1
80.65%

Totals

Change from base Build 4026134479:
0.4%

Covered Lines:
2418

Relevant Lines:
2773

💛  - Coveralls

Thanks for updating the PR! Added a bunch of comments

I addressed your comments (except https://github.com/shapely/shapely/pull/1708#discussion_r1103879221), then squashed and rebased as there were too many conflicts otherwise.

Hmm... I'm not sure why it fails with something related to LINESTRING Z, there were not 3d geometries involved here...
Not equal to tolerance 1e-07
 x: array(<LINESTRING Z (1 1 0, 10 1 0)>, dtype=object)
 y: array(<LINESTRING (1 1, 10 1)>, dtype=object)

Hmm... I'm not sure why it fails with something related to LINESTRING Z, there were not 3d geometries involved here...
But it's strange that it is actually the method="geos" version that is failing, and that should not have changed ...

Ah, this is probably related to your change to use assert_geometries_equal instead of equals(..).al(). The latter is doing spatial equality, and will ignore the Z dimension. This seems to be a bug in older GEOS versions (incorrectly introducing a Z dimensio for this case) that we can ignore here.

Ah, this is probably related to your change to use assert_geometries_equal instead of equals(..).al(). The latter is doing spatial equality, and will ignore the Z dimension. This seems to be a bug in older GEOS versions (incorrectly introducing a Z dimensio for this case) that we can ignore here.

OK, I've updated the skip accordingly (3.6 -> 3.8)

Maybe the function itself can be wrapped in a PRE_GEOS_312 conditional on the C level?

You mean so the ufunc is actually only available when built with GEOS 3.12?
(This is a bit tricky, because we don't want to "officially" say that, but keeping it for all versions ensures that if someone really needs the ufunc but can't upgrade to the latest GEOS has it available through shapely.lib.oriented_envelope)

Going to move forward here, so we can make the release.
But happy to further update the tests afterwards (or address other comments)

Thanks @idan-miara for the initial PR!

authors: coveralls idanmiara jorisvandenbossche

repo: shapely/shapely


text:
FIX #1836 - polylabel runs into infinite loop with tiny polygon

I believe this should fix issue #1836

Thanks for the PR! And sorry for the slow reply .. Could you add a test for this? (I think you can take the example from the bug report for that, and add a test based on that in test_polylabel.py)

And it also seems to actually change the result (failing test, didn't look further into how the result is different):
    def test_polylabel(self):
        """
        Finds pole of inaccessibility for a polygon with a tolerance of 10

        """
        polygon = LineString(
            [(0, 0), (50, 200), (100, 100), (20, 50), (-100, -20), (-150, -200)]
        ).buffer(100)
        label = polylabel(polygon, tolerance=10)
        expected = Point(59.35615556364569, 121.8391962974644)
>       assert expected.equals_exact(label, 1e-6)
E       assert False
E        +  where False = <bound method BaseGeometry.equals_exact of <POINT (59.356 121.839)>>(<POINT (57.906 108.751)>, 1e-06)
E        +    where <bound method BaseGeometry.equals_exact of <POINT (59.356 121.839)>> = <POINT (59.356 121.839)>.equals_exact

shapely/tests/legacy/test_polylabel.py:21: AssertionError

As I mentioned on the issue, this is also being fixed by https://github.com/shapely/shapely/pull/1307 where we replace our custom polylabel implementation with a new function from GEOS. Therefore closing this PR. But @djm93dev thanks for the PR nonetheless!


text:
feat: osmosis delegation support

Description
Add delegation support for osmosis
Notice

[x] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
Osmosis bounty
Risk
Some risk that cosmos delegation could be affected by this
Testing

Make sure cosmos staking still works

No need to fully test osmosis staking as its behind a feature flag (we know the apr is showing as 0 and will fix it from unchained)

Screenshots (if applicable)

adding blocked until unchained stuff is merged

closing to re-open a new PR due to massive merge conflicts

repo: shapeshift/web


text:
Feat/test install script

Description:
This PR introduces several improvements to the validator-dashboard installer script to enhance usability, error handling, and compatibility for both interactive and non-interactive environments, especially in CI/CD pipelines such as GitHub Actions.
Key Updates:

Support for Non-Interactive Execution:

The script can now run in both interactive and non-interactive modes.
Default values are automatically applied in non-interactive environments (e.g., when running in GitHub Actions), allowing the installer to proceed without requiring user input.
Interactive prompts are retained when run in a local, interactive shell for flexibility.

Improved Error Handling:

Better handling of common errors, such as missing directories, with clear and descriptive error messages.
Error trapping and reporting have been added to improve debugging, including capturing and displaying output from failed Docker builds.

Docker Image Build Improvements:

Docker image build output is now captured and displayed in the event of a failure, making troubleshooting easier.
The installer now lists the built Docker images after a successful build, providing visibility into the build process.

SSL Handling in Curl Requests:

The script now supports running curl with the -k option, which allows bypassing SSL verification issues (e.g., self-signed certificates) for testing environments.
curl is used with -f and -k in combination to fail gracefully on HTTP errors while ignoring SSL certificate problems.

Directory Setup and Feedback:

The script now ensures the target directory for the installation exists and provides feedback when creating or validating directories.
Status messages have been added throughout the script for better transparency and progress reporting, especially for critical steps like writing the .env file and building Docker images.

Benefits:

CI/CD Compatibility: Improved support for automated environments like GitHub Actions, enabling seamless integration with non-interactive build pipelines.
Enhanced Debugging: Better error reporting ensures issues are easier to identify and resolve.
User-Friendly Prompts: Interactive and non-interactive modes offer flexibility, while new status messages improve clarity during the installation process.

I just bumped the version of the checkout action in the new workflow to clear out some deprecation warnings and. it looks like that worked so i'll approve and merge this in a sec

i'm bypassing this, i approve but it's not letting me approve now since i made changes but the changes are minor enough it doesn't really matter

Giving my retroactive approval :+1:

authors: BelfordZ TieDyedSheep muni-corn

repo: shardeum/validator-dashboard


text:
Project Setup

You can view the Kanban board setup here
For the code reviewer, there are two people in this group:
Sharon Odhiambo
Simba Eugene

Project Approved 👍
Hi @SimbaWANGU & @sharon-odhiambo, This is @sja-thedude your code reviewer.
Your project is complete!  There is nothing else to say other than... it's time to start working on it :shipit:
Congratulations! 🎉
Highlights:

All requirements completed

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me [@sja-thedude] in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

authors: SimbaWANGU sja-thedude

repo: sharon-odhiambo/Recipe-App


text:
php version

Is there a bump to the required php version, too? Seems like this plugin now requires at least 5.4 for the streamlined use of arrays.

Oh. I must have missed that. I'm running somewhere around 7 and have been off of 5.4 for years now.
I can revert the arrays back to be compatible with php pre 5.4. Is it just needing to go back to array() rather than []?

I think that is the only roadblock I'm hitting.

I'll try to roll an update tonight that makes it friendly to older versions of PHP. I'll update here when I do. Thanks for catching, Chris.

Fixed in 987434925c38a0e3835e91c854d4163407acc6c8 and c5e704a0b6a3d44870f5a2f3d804d17cb1008d68. Pushed to WordPress.org, and version 2.0.1 should be available soon.

Works again on our system! Thanks for the quick turnaround.

authors: shawnrice silsbyc

repo: shawnrice/reckoning


text:
Dot Code School Suggestion: Feedback for Section 2 - Chapter 3: Interacting with Balances

Lesson2: Chapter 3:
Setting and Reading User Balances
To be consistent with the code on the right side, the text on the left side in step 1 it should read :
impl Pallet {
....
}
instead of
impl BalancesModule {
..
}
// -- snip --

}

Thank you!

repo: shawntabrizi/rust-state-machine


text:
init() doesn't work on Block_Controller and subclasses

Goal: to be able to load in custom Requirements (JS and CSS) on a per-Block basis.  With Widgets, this was accomplished by adding an init() function to the WidgetController.  This method does not carry through to Blocks.
This may be related:  when attempting to access {$URLSegment}/block/{$Block-ID}, a 500 error is generated with message:
Call to a member function getController() on a non-object in /var/www/blocks/code/extensions/BlockContentControllerExtension.php on line 32

Such an error does not occur with Widgets, which have a similar ContentController extension.

Hi Sekjal, you can place your requirements calls in your template. I think that's the best approach as it keeps frontend stuff in the frontend. Alternatively you can place them in the forTemplate() method on your Block class.
The controller error might be an issue specific to 3.2. I think we need to give the controller a url segment. You on ss 3.2?

Still running 3.1.13.  Once I get through this next major dev push, I'll look at upgrading.
I'll add the Requirements to the templates temporarily, but I've just made a move system-wide to put them all in the controllers.  If I can figure out how to get init() to work more or less normally, would that be a worthwhile pull request?

What do we gain from being able to use a controller init() method over a
forTemplate() on the model? Is it just consistency with the way it's often
done on pages/contentcontrollers? Might be worth while but not a biggie.
Happy to merge a PR if you send one through.
On Thu, Dec 3, 2015 at 9:53 AM, Ian Walls notifications@github.com wrote:

Still running 3.1.13. Once I get through this next major dev push, I'll
look at upgrading.
I'll add the Requirements to the templates temporarily, but I've just made
a move system-wide to put them all in the controllers. If I can figure out
how to get init() to work more or less normally, would that be a worthwhile
pull request?
—
Reply to this email directly or view it on GitHub
https://github.com/sheadawson/silverstripe-blocks/issues/38#issuecomment-161430862
.

--
Shea Dawson
Web Developer
LiveSource
mobile +64 20 4028 5647
skype squatchnz
email shea@livesource.co.nz
*web *www.livesource.co.nz

Point taken; using forTemplate() does exactly what I'd want init() to do, so why prioritize this over other enhancements?  Perhaps a note in the documentation on how to do this would be a better pull request... I'll work on that and submit.

Sure thing :)
On Fri, Dec 4, 2015 at 3:06 AM, Ian Walls notifications@github.com wrote:

Point taken; using forTemplate() does exactly what I'd want init() to do,
so why prioritize this over other enhancements? Perhaps a note in the
documentation on how to do this would be a better pull request... I'll work
on that and submit.
—
Reply to this email directly or view it on GitHub
https://github.com/sheadawson/silverstripe-blocks/issues/38#issuecomment-161649515
.

--
Shea Dawson
Web Developer
LiveSource
mobile +64 20 4028 5647
skype squatchnz
email shea@livesource.co.nz
*web *www.livesource.co.nz

authors: sekjal sheadawson

repo: sheadawson/silverstripe-blocks


text:
Tokens Rotate in Reverse now

Odd bug, but the tokens rotate in reverse from their defaults since the latest update.

pfft, my bugfix may have had unintended consequences

Fixed in v1.8.6

authors: GambetTV shemetz

repo: shemetz/ZoomPanOptions


text:
Has support been added for scrapy-redis?

Current work frequently uses redis queues
Whether subsequent releases have support for redis push tasks, and scrapy-redis features
thanks

I will work on this feature in my free time.

good news，there is no need to release a new package and modify the source code to be compatible with scrapy-redis. You only need to simply modify the scrapy-redis example.
I have posted the example to myspider_redis in DemoSpider.

In addition, since the latest package of scrapy-redis that is compatible with the new version of scrapy has not been released, you need to package it yourself.
Packaging command:
git clone https://github.com/darkrho/scrapy-redis.git
cd scrapy-redis

then run, python setup.py install.
or run, make clean && make dist.

thanks scrapy-redis demo。
But I encountered a new problem。
Program error interrupt

But I encountered a new problem。

The solution is up there, you need to package the latest scrapy-redis.Instead of pip install scrapy-redis.

git clone https://github.com/darkrho/scrapy-redis.git
cd scrapy-redis

then run, python setup.py install.
or run, make clean && make dist.

After executing make clean && make dist, pypi will be generated in the dist directory, just install it.

I uploaded the latest package of scrapy_redis to the libs folder of DemoSpider. Please test again. Remember to uninstall before installing.

thansk
I can use it normally after using pip intall xx.whl. grateful
Can it be integrated into ayugeSpiderTools in the future?
❤

Can it be integrated into ayugeSpiderTools in the future?

AyugeSpiderTools and scrapy-redis do not conflict, and scrapy-redis is not used in the project yet, so it is the best way for users to add dependencies themselves.
After scrapy-redis is updated, it will be easier to install.

authors: georgeJzzz shengchenyang

repo: shengchenyang/AyugeSpiderTools


text:
oAuth Example

Can somebody provide an example of how to authorize? I dont know what to use for redirect URL

@objectiveSee I will do that soon. Thanks

@shernshiou - thanks for the awesome library.
@objectiveSee - I created a basic example here: https://github.com/scottdixon/node-express-uber-example

@shernshiou do you still need help with that? I have another sample here

@agraebe @scottdixon yeah help is greatly needed

@scottdixon I got inspired by your example and updated the README: https://github.com/shernshiou/node-uber/blob/master/README.md. Do you have any other suggestions for improvement?
@objectiveSee I hope this will be help for you. Let us know otherwise!

@agraebe Are you aware of any issues with creating/requesting a ride?
I seem to get a 401 (unauthorized) on every uber.requests.create() call -- all other API calls requiring access_token are functioning fine.

@aleksdao I'm not aware of any issues... let me double check in a few hours... Would you mind sharing your code within a new issue? And also, did you request the required scope (and enabled it for your app in the Uber Developer Dashboard)?

authors: agraebe aleksdao objectiveSee scottdixon shernshiou

repo: shernshiou/node-uber


text:
Spelling mistake in README.md.

I know it's a tiny change (sorry), but when I get time to start installing and using this repo, I'll see if I can contribute more. I just found about this repo.

@wlwl2 Thanks for the PR! 👍

repo: sheshbabu/freshlytics


text:
P0627R6 Function to mark unreachable code

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p0627r6.pdf

実装済み

repo: shibainuudon/HamonCore


text:
live updates not working on firefox

I'm on:

OSX 10.14.4
livedown 2.1.1
npm 6.9.0
node 11.13.0
firefox 66.0.2
chrome 73.0.3683.86

livedown start <path> --open --verbose
[livedown] markdowning started on http://localhost:1337

That displays the markdown file correctly in my browser, but file changes produce no further output on the command line or updates in the browser.

Doesn't seem to be working on Chromium either.

I reported this in #16 a long time ago. At some point, the issue resolved for me, but for the latest livedown versions, I'm seeing the issue again. Linux (Ubuntu 18.04) + recent Chrome versions.

Can't reproduce this with Ubuntu 20.04 + Firefox.

authors: Kevin-Mok amontalenti lucasavila00 toejough

repo: shime/livedown


text:
Add recent order API changes to the OAS

We add the recent changes to the Order API, like
order_line_item#returnability, to the Open API Schema.

deployed for review here: https://shipcloud-dev-portal-staging.firebaseapp.com/swagger-ui

@3wille I deployed the changes of 98535d9 again to the above staging URL

repo: shipcloud/shipcloud-developer-portal


text:
Update php

Build php

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-php


text:
Update php@7.0

build php@7.0

:beers: @BrewTestBot has triggered a merge.


text:
Toggle theme functionality implemented in all service pages

What kind of change does this PR introduce ?

Fixes #187
Implemented UI functionality for all Service pages

Checklist

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes

Links
https://udith51.github.io/Student-portal/
Screenshots
(PS: Dark theme and normal theme are shown side-by-side in screenshots)
Image to Pdf page

Doc to Pdf page

Text to Pdf page

Extract Zip page

Image Resizer page

Do update me, in case any changes are required:)

Hey, @aakankshabhende @swati2603 @shivshankar9 you may review this pr.

@udith51 Have you tried it by running it on a smartphone?

@udith51 Have you tried it by running it on a smartphone?

Yup @swati2603, I checked it just now. The toggle theme functionality is working perfectly fine on smartphone as well.

Add the screenshots of your smartphone.


text:
出现了pagemap的标签

请问页面上出现的这个（没有包含任何内容 看上去像是页面的缩略图  总之看起来像个bug）应该如何关掉呢？ 因为不考虑配置百度的统计图表 所以config里把它关掉了，在想是不是因为某些插件或是应用配置不完全导致的

canvas id="pagemap" width="150" height="116" style="cursor: pointer; width: 150px; height: 116.564px;"


text:
AOT compilation error with angular-cli 1.0.0

I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository

What is the current behavior?
Building a project with angular-cli 1.0.0 gives an error:
ERROR in /node_modules/angular2-modal/esm/components/swap-component.directive.d.ts (1,1): Cannot find type definition file for 'chai'.

Recently a bug was fixed in angular-cli that would mask certain errors when compiling templates. Following this fix, the above mentioned error appears.

Please tell us about your environment:

Angular version: 2.4.10
angular-cli 1.0.0

It should be fixed with this PR: https://github.com/shlomiassaf/angular2-modal/pull/325


text:
Add tests and fix bugs

Hi! Thank you for this, first of all! I fixed a few bugs and added tests, both for synchronous and async usage, and also for Redis specifically.

Hey, thanks for opening this! I'm a bit busy this week but I'll take a look as soon as I can.

I got 'NoneType' object has no attribute 'wait_for_capacity_sync'
error on this pull

I'm getting local variable 'redis' referenced before assignment without this, any chance we could get this merged?

@shobrook we'd like to use this in a blog post for ClickHouse.com if you have any interest in addressing..

Hi, sorry for the delay. Taking a look now.

Merged. Also upgraded the package on PyPi (v0.3.0). Please let me know if it's working for you now :)

thanks @shobrook same issue https://github.com/shobrook/openlimit/issues/9

authors: gingerwizard justinphan3110cais shobrook txus

repo: shobrook/openlimit


text:
Problem with Perl path on self-hosted runner

It seems that the code for the PERLLIB logic is assuming that the path is going to be __dirname something which causes the path to be built up badly:
Can't locate strict.pm in @INC (you may need to install the strict module) (@INC contains: /home/runner/_work/_actions/shogo82148/actions-setup-perl/v1/scripts/lib /opt/hostedtoolcache/perl/5.32.1/x64/lib/site_perl/5.32.1/x86_64-linux /opt/hostedtoolcache/perl/5.32.1/x64/lib/site_perl/5.32.1 /opt/hostedtoolcache/perl/5.32.1/x64/lib/5.32.1/x86_64-linux /opt/hostedtoolcache/perl/5.32.1/x64/lib/5.32.1)
When on a self-hosted runner the hostedtool cache folder is going to be /home/runner/_work/_tool/perl/... instead of /opt...

Unfortunately, actions-setup-perl doesn't support self-hosted runner.
The action uses binaries built on GitHub hosted runner and the binaries are not portable.
Please consider using Docker images or building perl binary on your machine.

Same issue running on Github Actions with actions-setup-perl used as a container. Not supported either?

authors: ekarlso shogo82148 ylavoie


text:
drop Go 1.7 support

https://github.com/shogo82148/go-sql-proxy/issues/23

Coverage increased (+0.4%) to 62.171% when pulling eb13d3be21faa5f509a95069861c8c0365f9d619 on drop-go17-support into 8daca4f94f6aa188f48d0536ef26ef75b1cc86b7 on master.

Coverage increased (+0.4%) to 62.171% when pulling eb13d3be21faa5f509a95069861c8c0365f9d619 on drop-go17-support into 8daca4f94f6aa188f48d0536ef26ef75b1cc86b7 on master.

Good Bye Go 1.7...


text:
Issue of install FastCoref in Colab

Its been working fantastic till last week in colab.
!pip install fastcoref==2.1.5 -q
!pip install fastcoref==1.6.0 -q
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 474.3/474.3 kB 8.1 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 9.5/9.5 MB 23.7 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.3/116.3 kB 5.4 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 207.3/207.3 kB 11.2 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 39.9/39.9 MB 12.9 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 311.4/311.4 kB 7.1 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 134.8/134.8 kB 6.0 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 194.1/194.1 kB 6.8 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.7/62.7 kB 845.9 kB/s eta 0:00:00
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
cudf-cu12 24.4.1 requires pyarrow<15.0.0a0,>=14.0.1, but you have pyarrow 17.0.0 which is incompatible.
ibis-framework 8.0.0 requires pyarrow<16,>=2, but you have pyarrow 17.0.0 which is incompatible.
from fastcoref import FCoref
model = FCoref(device='cuda:0')
model = FCoref(device='cpu')

AttributeError                            Traceback (most recent call last)
 in <cell line: 1>()
----> 1 from fastcoref import FCoref
2 # model = FCoref(device='cuda:0')
3 model = FCoref(device='cpu')
9 frames
/usr/local/lib/python3.10/dist-packages/pyarrow/_compute.pyx in init pyarrow._compute()
AttributeError: module 'pyarrow.lib' has no attribute 'ListViewType'
import pyarrow
pyarrow.version
14.0.2

!pip install -q pyarrow==14.0.1 datasets==2.10.0

Thanks for help but problems stays the same:
!pip install -q pyarrow==14.0.1 datasets==2.10.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 38.0/38.0 MB 11.6 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 469.0/469.0 kB 12.7 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 110.5/110.5 kB 6.8 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 134.3/134.3 kB 4.7 MB/s eta 0:00:00
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 194.1/194.1 kB 6.7 MB/s eta 0:00:00
!pip install fastcoref -q
Preparing metadata (setup.py) ... done
Building wheel for fastcoref (setup.py) ... done
from fastcoref import FCoref
model = FCoref(device='cuda:0')
model = FCoref(device='cpu')
/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_token.py:89: UserWarning:
The secret HF_TOKEN does not exist in your Colab secrets.
To authenticate with the Hugging Face Hub, create a token in your settings tab (https://huggingface.co/settings/tokens), set it as secret in your Google Colab and restart your session.
You will be able to reuse this secret in all of your notebooks.
Please note that authentication is recommended but still optional to access public models or datasets.
warnings.warn(
config.json: 100%
 819/819 [00:00<00:00, 14.2kB/s]
tokenizer_config.json: 100%
 393/393 [00:00<00:00, 4.15kB/s]
vocab.json: 100%
 798k/798k [00:00<00:00, 2.67MB/s]
merges.txt: 100%
 456k/456k [00:00<00:00, 3.61MB/s]
tokenizer.json: 100%
 1.36M/1.36M [00:00<00:00, 3.82MB/s]
special_tokens_map.json: 100%
 239/239 [00:00<00:00, 4.80kB/s]
/usr/local/lib/python3.10/dist-packages/transformers/tokenization_utils_base.py:1601: FutureWarning: clean_up_tokenization_spaces was not set. It will be set to True by default. This behavior will be depracted in transformers v4.45, and will be then set to False by default. For more details check this issue: https://github.com/huggingface/transformers/issues/31884
warnings.warn(
pytorch_model.bin: 100%
 362M/362M [00:04<00:00, 113MB/s]
ValueError                                Traceback (most recent call last)
 in <cell line: 3>()
1 from fastcoref import FCoref
2 # model = FCoref(device='cuda:0')
----> 3 model = FCoref(device='cpu')
7 frames
/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py in _check_and_enable_sdpa(cls, config, hard_check_only)
1729         if hard_check_only:
1730             if not cls._supports_sdpa:
-> 1731                 raise ValueError(
1732                     f"{cls.name} does not support an attention implementation through torch.nn.functional.scaled_dot_product_attention yet."
1733                     " Please request the support for this architecture: https://github.com/huggingface/transformers/issues/28005. If you believe"
ValueError: RobertaModel does not support an attention implementation through torch.nn.functional.scaled_dot_product_attention yet. Please request the support for this architecture: https://github.com/huggingface/transformers/issues/28005. If you believe this error is a bug, please open an issue in Transformers GitHub repository and load your model with the argument attn_implementation="eager" meanwhile. Example: model = AutoModel.from_pretrained("openai/whisper-tiny", attn_implementation="eager")

...problems stays the same:

no,  it's not the same :) The new error means transformers library was updated on Google Colab  again. So just install an older version supported by fastcoref. I found, for example, transformers==4.31.0 works fine

Hey. You can use this to go around the error you've seen. @xiongjun926g . Seems to load and do inference fine on transformers 4.45.1
import sys
from fastcoref import LingMessCoref as OriginalLingMessCoref
from transformers import AutoModel
import functools

class PatchedLingMessCoref(OriginalLingMessCoref):
    def __init__(self, *args, **kwargs):
        original_from_config = AutoModel.from_config

        def patched_from_config(config, *args, **kwargs):
            kwargs['attn_implementation'] = 'eager'
            return original_from_config(config, *args, **kwargs)

        try:
            AutoModel.from_config = functools.partial(patched_from_config, attn_implementation='eager')
            super().__init__(*args, **kwargs)
        finally:
            AutoModel.from_config = original_from_config

model = PatchedLingMessCoref(
    nlp="en_core_web_lg",
    device="cpu"
)

# Run your stuff here

Hey. You can use this to go around the error you've seen. @xiongjun926g . Seems to load and do inference fine on transformers 4.45.1
from fastcoref import LingMessCoref as OriginalLingMessCoref
from fastcoref import FCoref as OriginalFCoref
from transformers import AutoModel
import functools

class PatchedLingMessCoref(OriginalLingMessCoref):
    def __init__(self, *args, **kwargs):
        original_from_config = AutoModel.from_config

        def patched_from_config(config, *args, **kwargs):
            kwargs['attn_implementation'] = 'eager'
            return original_from_config(config, *args, **kwargs)

        try:
            AutoModel.from_config = functools.partial(patched_from_config, attn_implementation='eager')
            super().__init__(*args, **kwargs)
        finally:
            AutoModel.from_config = original_from_config

class PatchedFCoref(OriginalFCoref):
    def __init__(self, *args, **kwargs):
        original_from_config = AutoModel.from_config

        def patched_from_config(config, *args, **kwargs):
            kwargs['attn_implementation'] = 'eager'
            return original_from_config(config, *args, **kwargs)

        try:
            AutoModel.from_config = functools.partial(patched_from_config, attn_implementation='eager')
            super().__init__(*args, **kwargs)
        finally:
            AutoModel.from_config = original_from_config

model1 = PatchedLingMessCoref(
    nlp="en_core_web_lg",
    device="cpu"
)

model2 = PatchedFCoref(
    nlp="en_core_web_lg",
    device="cpu"
)

# Run your stuff here

This works for me, and the error output actually already states how to fix this problem: load your model with the argument attn_implementation="eager" meanwhile.

@shon-otmazgin Can you please implement that fix. It's an easy one. Thanks.

repo: shon-otmazgin/fastcoref