text:
Several issues

I noticed several issues that should be adressed to be a proper framework.

(And what bothers me most is that) The readme of this repository gets edited without any reason. I can only guess that it serves the purpose of being in the top search results. This is highly deceiving and it messes up the Insights/Network view.

Classes are way to dependant on parent classes. For example it is impossible to use the app-navbar-list-item on its own if i desire to (to have my own custom sidebar / sidebar buttons).

        Home

Styles should not depend on tags. In fact, tags shouldnt be used anywhere for styling. It should all be doable with plain divs and styles only applied to classes.

.app-navbar-wrap nav {
    ...
}

Hi @Slluxx,
Thanks for looking into this,
After taking an insight at the CSS i can confirm that this really needs a brush up as follows below

Replace tags with it's class/div name instead.
Reduce unnecessary class dependency of parent and put those child class outside of it's parent.
No more deceiving commits.

Once all issue got fixed then only i will close this issue :)

Thank you!
Maybe its possible to give this project a rewrite and make it more accessible to editing / extending? I tried to set up the repository myself to fix some issues (for example the menu buttons height being too large) but i wasnt even able to set the project up properly. There are a lot of outdated modules and one didnt want to install at all. The mixture of windows 10 and windows 11 style css also increases the overall difficulty of the project.
I noticed other things too, such as the dark color theme only being "correct" if we take an unfocused windows 11 application as example (see screenshot for focus comparison). This makes it feel like its always "unfocused" and not actually the active window. Since i am working with tools such as https://github.com/python-eel/Eel, https://github.com/r0x0r/pywebview and very recently also with https://github.com/neutralinojs/neutralinojs, having 1=1 windows 11 style applications makes a big difference! (I have an eye for whats right and wrong but my css/scss skills are just not good enough to make it myself.) Maybe its a good idea to have classes applied to the body that will change all colors accordingly. This way, focus and unfocus event handlers can be build into our python apps.
Your repository is seemingly the only css framework that uses Windows-native-elements, looks good and is usable and i hope i (and others) can use it to build "native like" applications without the need to rely on WinUI 3 and XAML in C# or C++. I really hope it can become even better than it is right now.
In the future i would also love to make a VueJS library out of it but at its current state, its sadly too limited in its modularity. A Bootstrap or Tailwind approach to classes would greatly improve the usability aswell as customizability (.btn .btn-primary or .card .bg-primary mt-3 etc).
Unfocused (basically the current windows-ui color scheme):

Focused (how an active window should look like):

Thanks for all the elaboration on what can be improved/fixed to this project.
You are correct the button height, navigation toggle button etc. were not as same size of what should be as per windows 11, also the unnecessary windows 10 styles in the SCSS file needs to be removed so i was tried first fixing these issues on my other project - react-windows-ui additionally adding blur effect and more life to make components feel exact like windows 11.
What got already fixed

Size of components are now 1:1
Removed windows 10 unused CSS code from source SCSS files
Fixed some color variables
Updated All node modules -versions

What needs to be fix

Adding Blur effects to Components with adding a .blur class to components.
Active/Inactive Window (As per this issue)
Will try to see what classes Bootstrap use probably make this as simple as possible.

Just having concern for having utility classes since my objective for this project was to provide Native look and feel components and not how a developer add them to either Grid or Flex layout on their project.
Do you want a kind of prop for button - medium/small/large ??
Have a look at under development -v4.2.3 of react-windows-ui
New SnapShot

Old SnapShot

Do you want a kind of prop for button - medium/small/large ??

Hm. As per: https://learn.microsoft.com/en-us/windows/apps/design/signature-experiences/signature-experiences and https://learn.microsoft.com/en-us/windows/apps/design/controls/buttons it looks like buttons have always the same height, unless the text forces them into multiple rows.
I think btn should be the most standard button and then have prop classes for btn-primary for example.

Just having concern for having utility classes since my objective for this project was to provide Native look and feel components and not how a developer add them to either Grid or Flex layout on their project.

Yes, you are right. The normal classes (btn, card, ...) must be enough to build a native looking website. However i also think sometimes you need more or less space between elements or if you want to make a custom element, utility classes really help.
If they are out of scope or not is up for you to decide. After thinking about it for a bit, i would agree with both.

Does that all good to have prefix of app- on all components including the button that currently has class app-btn app-btn-primary ?
It was intended so that it will not interfere with other dependencies mostly with the react version of this project.

Does that all good to have prefix of app- on all components including the button that currently has class app-btn app-btn-primary ? It was intended so that it will not interfere with other dependencies mostly with the react version of this project.

Usually no. With React and Vue, you should only import the elements you actually need and not everything. In VueJS for example: import Button from 'primevue/button';
Either dont import the button if you want to use your own or if you want to use a different button from a different framework, import Button from 'a_different_framework/button';
You can remove your prefix and dont need to care about other frameworks.

authors: Slluxx virtualvivek

repo: virtualvivek/windows-ui


text:
alias与color冲突

<template>

    <v-chart :forceFit="true" :height="height" :data="data" :scale="scale">
      <v-tooltip />
      <v-legend />
      <v-axis />
      <v-bar position="companyName*price" color="companyName" />
    </v-chart>

</template>

<template>

    <v-chart :forceFit="true" :height="height" :data="data" :scale="scale">
      <v-tooltip />
      <v-axis />
      <v-bar position="companyName*price" color="companyName" />
    </v-chart>

</template>

<template>

    <v-chart :forceFit="true" :height="height" :data="data" :scale="scale">
      <v-tooltip />
      <v-axis />
      <v-bar position="companyName*price" color="companyName" />
    </v-chart>

</template>

不设置color="companyName"  v-legend失效，设置了scale别名失效

不设置color="companyName"  v-legend失效，设置了scale别名失效

source: gharchive/issue

repo: viserjs/viser

license: mit

license_type: permissive

license_source: bigquery


text:
possibly wrong E_sums in KamadaKawai.js

I'm trying to read the layout part code of visjs, but I found this line confusing.
It seems dE_dx or dE_dy should be the sum of the whole row (or column identically) of E_matrix, but it's only the sum of the row in upper triangle of E_matrix.
For example, when calculating energy of 3 points, E_sums[0][0] = E_matrix[0][1][0] + E_matrix[0][2][0] is correct (here the last 0 index indicates x axis), but E_sums[1][0] = E_matrix[1][2][0] and E_sums[2][0] = 0, which seems to be incorrect.
If there are some tricks in code that I've missed, I think it should be documented in comments. Otherwise, if it's a bug and if necessary, I can create a pull request.

As I don't know KamadaKawai, I find the whole file confusing. Maybe the original authors (@AlexDM0 and @ludost) would be so nice and join this discussion?
Anyway if you have time you can open the PR and we can compare which version behaves better.

Its been a long time since I wrote that. It could be that there is a bug in there, but the referenced paper is stated at the top of the file. I suggest you cross reference it with the paper, if it is a bug, fix it and test it. There is not much more we can add to this other than doing the exact same thing.

I will have to do some serious digging in my memory to answer that question.
The specific line came from an optimization effort, in which I reduced the time to do the startup positioning by an order of complexity. I agree I need to re-discover the steps I took, to document these better. I'll try to find some time for that in the coming days. (See: https://github.com/visjs/vis-network/commit/5af416587cf0b038a8c57ca68313f4c0facb6716)
That said, this method is used for the initial positioning, which doesn't have to be perfect as the gravity engine will then take over to further position everything. I remember I actually contemplated removing this method completely and replacing it with a more random starting position.

Okay, I'm quite busy these days, and I'll create a pull request and test it some day later.
The problem I mentioned before is about initial layout, so it have little impact on performance.
Here are some other confusing parts and potential bugs I found.

this line solves the linear equations, but it seems wrong, and this may have large impact on layout performance (maybe I'm wrong).
this line contains two nested while loop, but outer threshold is smaller than innerThreshold, and this means the execution will enter the outer loop without entering the inner loop, no change is made, the same node will be selected as highE_nodeId and outer loop will uselessly execute again and agian until maxIterations is reached.

Okay, I've taken a look.
You mention three items:

MatrixSum: This looks okay to me. The dE_dx and dE_dy are the sum for node 'm' and take into account the entire "row" of 'm'. (all values of iIdx) Maybe it's a bit confusing that E_Matrix is actually not a 2d Array, but an object with fields, indexed by node 'm', with an array as value.
Linear equation: I can't comment on this one, I don't have the original paper at hand. But what is it that looks wrong here?
LoopThresholds: I guess you're right that this looks a bit wrong. This has been part of the original implementation, so predates my optimizations. I'm not sure how often any real-life data will hit this situation? But at the very least we could add a double check to see if we hit the same node twice and chicken-out earlier.

Maybe that matrix sum part becomes clearer in the pseudocode below:
Loop through nodes: m @ mIdx
	Set dE vars to 0
	Loop through nodes: i @ iIdx
		Create new E_Matrix[m][iIdx] entry _(based on x & y of both m & i)_
		Store entry also in E_Matrix[i][mIdx]
		Increase dE vars with new entry values
	Store dE vars into separate storage E_sums[m]

As far as I can tell at the end the E_sums will contain a matrix of the dE sums for each node.
It doesn't help at all that the "row" and "column" terminology in the comments seems transposed to me. But this is probably due to that research paper. It looks like the 'm @ mIdx' loop is over rows, with the 'i @ iIdx' loop being over columns.

It seems I've successfully implemented Kamad Kawai based in my own project. And some extra possible bugs are found.

this line should be this.E_matrix[i][mIdx] = -this.E_matrix[m][iIdx];.
this line should be changed to sum[0] += (oldDx-dx);, so as the following line.
this.E_matrix[i][mIdx] = [-dx, -dy] should be added below this line.

After all, I don't know how to test my visjs code. Can someone help me?

repo: visjs/vis-network

license_source: github-api


text:
    docs(ssr): update example projects

New updates on head repo.
https://github.com/vitejs/vite/commit/02cd0439e88fb17184978509025d4269bd6ebaa0

#1088 のあとに対応

authors: jay-es kiaking

repo: vitejs/docs-ja

license: MIT


text:
HMR when using imported styl (stylus) files

Describe the bug
Is it possible to trigger HMR when importing variables from a .styl file?
Reproduction
// vars.styl
myVar = blue

<template>

{{ text }}

    <button>I'm a button</button>

</template>

System Info
@vue/compiler-sfc: 3.0.0-rc.4
vite: 1.0.0-rc.3
macos: 10.15.6
node: 12.14.1

Thank you so much @underfin

repo: vitejs/vite


text:
fix(server): the server restart port should remain unchanged

Description

Start a project, the default port is 5173.
Start another project, because the default port is already in use, so the listening port after the project is started is 5174.
Close the first project.
At this point, modifying the configuration file of the second project, such as the '.env' file, causes the server to restart. Since the second project may already be in the access state, I think the port that was listening on before should be maintained.

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

@ArnaudBarre Already modified as @patak-dev  suggested and added the comments you provided. ❤

source: gharchive/pull-request


text:
documentation: provide context for Vue DX Typescript support

This fixes the problem I outlined in #2017. Please let me know if this is the wrong place for this change.

This is inaccurate - see https://github.com/vitejs/vite/issues/2017#issuecomment-779312203


text:
Including tests from different directories is broken in vitest 0.34.*

Describe the bug
Hello, and thank you for reading.
I have been using vitest 0.33.0 with the happy-dom environment.

I have a multi-projects structure, every project containing tests.
One of the projects is running the tests of all the other projects. This project contains the vite.config.ts with the following include to ensure running all tests: include: [...configDefaults.include, '../**/*.test.ts']

It's working great, but as soon as I upgrade to vitest 0.34.0 or higher it doesn't work.
I have read the doc and the release notes, but I don't see why it stopped working.
Reproduction

npm init vue@3 to generate a base project (say "No" to all, except for vitest tests)
Set vitest to version 0.34.5
Create a new simple test to an external directory, for example ../SimpleTest.spec.js:

import {expect, test} from 'vitest'

test('simpleTest', async () => {
  expect(1).toEqual(1)
})

In vitest.config.js, add include to target specifically this test:

defineConfig({
    test: {
      ...
      include: ['../SimpleTest.spec.js']
    }
  })

npm run test:unit

Expected results
The test is successfully executed.  This is the case if I downgrade vitest to the version 0.33.0 OR if I set environment: 'node'. In jsdom or happy-dom environments, the test fails (see below).
Actual results
 DEV  v0.34.5 /Users/nico/sandbox/vitest-bug-2/test

 ❯ ../SimpleTest.spec.js (0)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  ../SimpleTest.spec.js [ ../SimpleTest.spec.js ]
Error: Failed to load url /Users/nico/sandbox/vitest-bug-2/SimpleTest.spec.js (resolved id: /Users/nico/sandbox/vitest-bug-2/SimpleTest.spec.js). Does the file exist?
 ❯ loadAndTransform node_modules/vite/dist/node/chunks/dep-df561101.js:54939:21

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

 Test Files  1 failed (1)
      Tests  no tests
   Start at  17:32:08
   Duration  350ms (transform 13ms, setup 0ms, collect 0ms, tests 0ms, environment 222ms, prepare 49ms)

 FAIL  Tests failed. Watching for file changes...
       press h to show help, press q to quit
Cancelling test run. Press CTRL+c again to exit forcefully.

Note: the file path indicated in the error message is valid (the file does exist).
System Info
System:
    OS: macOS 13.5.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 480.17 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.5.1 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.8.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 117.0.5938.88
    Safari: 16.6
  npmPackages:
    @vitejs/plugin-vue: ^4.3.4 => 4.3.4
    vite: ^4.4.9 => 4.4.9
    vitest: ^0.34.5 => 0.34.5

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

All tests that use browser API also have limited access to the file system. Vitest allows files in the same directory the config is by default. You can disable this with server.fs.strict: false or add your directory to server.fs.allow:
export default defineConfig({
  server: {
    fs: {
      // either or
      strict: false,
      allow: ['../']
    }
  }
})

Thanks a lot @sheremet-va! Now I understand and the issue is fixed.

authors: NicolasFrossard sheremet-va

repo: vitest-dev/vitest


text:
chore: repro --no-threads issues

Adds an additional step to the CI job to reproduce the --no-threads issues

Can you share more context about this? Not all tests are capable of running in the same thread.

There are currently several issues when running tests with --no-threads:

jsdom issues: it turns out that the teardown function of the jdsom env is never called in threaded mode. When threads are disabled, then the teardown function is called, and tests break
some mocks and spies tests are failing as well, maybe for a similar reason (pnpm test -- --no-threads)

@antfu Just saw your comment. There is at least one issue with jsdom (and happy-dom probably) env: their teardown function is never called when threads are enabled if I'm not mistaken. That leads to behavior difference between threaded and non-threaded mode.

Related issue #835

authors: antfu cexbrayat


text:
Update sidebar.topHTML  after initialization

It seems there is a regression in the sidebar.
I cannot update sidebar.topHTML definition.
The code below already worked, and now it doesn't.
E.g. updating nodes still works...
(w2ui 2.0.x (nightly) (12/30/2023, 11:12:53 AM)
w2ui.sidebarRight['nodes'] = getSnapshotNodeDefinitions.value   // this works
w2ui.sidebarRight['topHTML'] = 'aaa'  // this doesn't work, the old content is still shown
w2ui.sidebarRight.refresh()

Are you sure it used to work? I checked the code and I see that it will update top and bottom html when render() method is called, but not referesh. Looking at the code, I see comments that say that topHTML should not be refreshed in refresh() as it might have input control with search for example, and then it would clear it. Refresh method updates nodes, I think it would be better to update topHTML and bottomHTML manually is needed after initial render

I propose we keep it like it is

I thing it woud be very usefull feature. E.g. you have sidebar with many items which number differs in time  and in the topHTML you have actuall number of items.

@jankrnavek , you can easily implement this feature directly updating html inside topHTML, I do think it should be done with grid.refresh(). Thank you.

authors: jankrnavek vitmalina


text:
feat: Add compute-feature to BaseBone

Extension for #623. With this PR you can now pass a compute parameter to each bone.
The compute parameter is a dataclass and consists of the following attributes.
@dataclass
class Compute:
    fn: callable  # The callable computing the value
    threshold: ThresholdValue   # The value caching interval
    raw: bool = True  # defines whether the value is used as is, or is passed to bone.fromClient

The ThresholdValue is a dataclass to and defiend like this.
class ThresholdMethods(Enum):
    Always = 0
    Until = 1
    Once = 2

@dataclass
class ThresholdValue:
    method: ThresholdMethods = ThresholdMethods.Always
    seconds: int = 0

Hello @ArneGudermann,
thanks for starting this pull request draft.
I think you've used my first proposal from [https://github.com/viur-framework/viur-core/issues/629#issuecomment-1409531246](my comment in #629) which you got by email, but I did several revisions on it. I think, that Threshold is the wrong value for this, and named it (in a later version of the comment) into ComputeInterval. Can you please re-check this and merge this proposal into this pull request?
For clarification, here's my comment from the link above as a copy. I've tested it and it should entirely fulfill all requirements on issue #692.

Hello @ArneGudermann,
I think that this namedtuple + enum definition would generally be the better choice in BaseBone. This draft defines all required features, and might also answer your question: The compute-definition might be configured to allow for raw values or to pass them through the bone's fromClient.
from dataclasses import dataclass
from enum import Enum, unique

@unique
class ComputeInterval(Enum):
    ALWAYS = 1
    ONCE = 2
    SECONDS = 3

    @classmethod
    def seconds(cls, value):
        instance = cls.SECONDS
        instance._value_ = value
        return instance

@dataclass
class Compute:
    fn: callable  # the callable computing the value
    interval: ComputeInterval = ComputeInterval.ALWAYS   # the value caching interval
    raw: bool = True  # defines whether the value is used as is, or is passed to bone.fromClient

Afterwards, compute_me can be defined this way:
def testme():
    return "123.1"

compute_me = NumericBone(
    compute=Compute(testme)
)

# Compute(fn=<function testme at 0x7f790476cee0>, interval=<ComputeInterval.ALWAYS: 1>, raw=True)

compute_me_securely = NumericBone(
    compute=Compute(testme, raw=False)
)

# Compute(fn=<function testme at 0x7f790476cee0>, interval=<ComputeInterval.ALWAYS: 1>, raw=False)

compute_me_2min = NumericBone(
    compute=Compute(testme, ComputeInterval.seconds(60 * 2))
)

# Compute(fn=<function testme at 0x7f790476cee0>, interval=<ComputeInterval.SECONDS: 120>, raw=True)

The readOnly is automatically enforced by the constructor.
What do you think? I want to avoid enforcing to only accept str and parse them always via fromClient, as this might result in values generated, converted to a parse-able representation to become the same representation as originally created in the end, which is an unnecessary round trip.

Hello @phorward
Thanks for your answer. I have one thing.
compute_me_2min = NumericBone(
    compute=Compute(testme, ComputeInterval.seconds(60 * 2))
)

Unfortunately this does not work because when I clone the skeleton before passing it to the compute function I get 120 as the value of the enum.

Unfortunately this does not work because when I clone the skeleton before passing it to the compute function I get 120 as the value of the enum.

You're right and I apologize. I really miss Rust's enums in Python, as
enum ComputeInterval {
    Always,
    Once,
    Seconds(usize),
}

is what I wanted to imitate here.
Anyway, could we make it simply this way first?
from dataclasses import dataclass

@dataclass
class Compute:
    fn: callable  # the callable computing the value
    seconds: int = 0  # interval in seconds, default is always
    raw: bool = True  # defines whether the value is used as is, or is passed to bone.fromClient

So seconds is just an int, which defines 0 as always, anything < 0 as once and >0 as timeout?
compute_me = NumericBone(
    compute=Compute(testme)
)

#Compute(fn=<function testme at 0x7fe27e97fd90>, seconds=0, raw=True)

compute_me_securely = NumericBone(
    compute=Compute(testme, seconds=-1, raw=False)
)

#Compute(fn=<function testme at 0x7fe27e97fd90>, seconds=-1, raw=False)

compute_me_2min = NumericBone(
    compute=Compute(testme, seconds=60 * 2)
)

#Compute(fn=<function testme at 0x7fe27e97fd90>, seconds=120, raw=True)

@sveneberth @ArneGudermann I've made a reworked proposal based on Arne's draft. It works, but I think some things could be improved as well. Can you please make a review on this?

Can we resolve https://github.com/viur-framework/viur-core/pull/639/files#r1166918242 before merging?

This refers to #639, can you clarify?

For the caching thing I've create an issue #709

Thanks! :+1:

Can we resolve https://github.com/viur-framework/viur-core/pull/639/files#r1166918242 before merging?

This refers to #639, can you clarify?

For the caching thing I've create an issue #709

Thanks! +1

The link was stupid... This was the issue, that has been resolved: https://github.com/viur-framework/viur-core/pull/639#discussion_r1166918242

authors: ArneGudermann phorward sveneberth

repo: viur-framework/viur-core


text:
Textboxes should position text to show cursor if text overflows box

Right now, you cant see what you're typing if you type text which is too long for a textbox. Let's make this work intuitively.

We could do this with a transform on the text rendering, though this might require the textbox to use custom drawing. Any thoughts on a possible implementation?
While we're on the subject of the textbox there's 2 other features I'd like to add:

placeholder text when the textbox is empty
an ellipsis (or custom character) at the end when the text overfl...

I think this is something we'll need another piece of state for, since you should be able to move the cursor around the text box without triggering text motion, unless you move it outside the bounds. The best interface for this is probably something like "move_position_into_bounds", which is called on cursor movement and updates the aforementioned state.

My thinking was that you could determine if the caret position is outside of the bounds of the textbox and then transform the text accordingly. So if the caret is inside the bounds then no transform happens. I'm not sureI understand what you mean by another piece of state and the move_position_into_bounds interface. What does this state track? Whether or not the caret is outside the textbox clip bounds?

repo: vizia/vizia


text:
Month view stop working

Im using cdn, not sure if you just drop an update on it but my calendar month view stop working without any changes. I figure out I have to add display: contents to the .ec-body class to get it back working. The week and day view were working okey
https://snipboard.io/kFeWab.jpg

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

No, I took a look and demo was working fine. I was making some changes in localhost and after 3pm the calendar stop showing. I removed my changes to see what was going on but still the same. Then I took a look into the main web page and the calendar was gone too, without pushing any changes. Luckily it was just a css fix, thank you for the cdn link, I was going to ask how to stop auto-updates

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

To reproduce it, initialize the calendar using example in Pre-built browser ready bundle, and setting the view to "dayGridMonth"
After setting the height, the days will start showing again.

In v0.15.0 I dropped support for IE. Do you have this issue reproduced on demo?

To reproduce it, initialize the calendar using example in Pre-built browser ready bundle, and setting the view to "dayGridMonth"
After setting the height, the days will start showing again.

Thanks a lot for the tip. I fixed this issue in version 0.15.1. Please check.
I also corrected the README so that the code for cdn specifies the version of the library.

I hope I can close this issue.

authors: AdrianGzzEsc altasB2 vkurko

repo: vkurko/calendar


text:
Type hints for Pin class are incomplete

Hey,
the Pin class is sadly lacking some type hints. For example Pin.board.X, Pin.high() and Pin.low() are missing.
Cheers
Kevin

@Streyder Thanks for reporting it. A pull request with missing type hints is welcome.

I implemented the changes on my end. Sadly I am not allowed to create a new branch to create a pull request. Actually I don't know how I would make a proper pull request. Maybe you can help out.

@Streyder We use the standard GitHub workflow for pull requests to this repository, I'm sure there are good tutorials about pull requests on GitHub. The basic idea is that you close this repository to your account, so it becomes github.com/Streyder/intellij-micropython, then you create your new branch there and then GitHub will show you the message about creating a pull request to the original repository on the page of your clone.

Created pullrequest 63 for this issue

Closing it as a duplicate of #16.

authors: Streyder vlasovskikh

repo: vlasovskikh/intellij-micropython


text:
Upgrade webpack 4 to 5

Fixes issue #19

@psychobolt Thank you for PR!

authors: psychobolt vlazh

repo: vlazh/node-hot-loader


text:
Add Dev Container

Dev Container open up a whole new world of possibilities:

It is easy to make dev environment even for frontenders, for whom currently it is hard as stated by #178
You can develop even on microwave by utilizing cloud super powers of Github Codespaces

There are also task and launch target defined for VS Code, so that environment is kinda complete, you just start vs code open dev container from source, click run and boom, everything just works (including debugging, and lint and stuff 🔥)
We can probably continue to improve that environment in the future (like for example when we can use Python 3.10 #221).
Before merge:

[ ] update README
[x] fix make help error
[ ] put python deps into image to speedup container starting
[ ] fix .gitignore (ignore whole ./vscode exclude required for devcontainer)
[ ] try to use docker-compose-dev.yml for devcontainer

We probably should store our dependencies in image, since they are not updating that frequently to speed up codespaces/local image builds.

Looks cool! I'll check this out next week

@egregors I disagree that we should exclude .vscode from repository, IT SHOULD NOT contain personal preferences, it should contain project wise preference see https://github.com/microsoft/vscode/tree/main/.vscode (especially https://github.com/microsoft/vscode/blob/main/.vscode/settings.json) for example.

@egregors I disagree that we should exclude .vscode from repository, IT SHOULD NOT contain personal preferences, it should contain project wise preference

Mine does ¯_(ツ)_/¯

@egregors I disagree that we should exclude .vscode from repository, IT SHOULD NOT contain personal preferences, it should contain project wise preference

Mine does ¯_(ツ)_/¯

Can you provide example what's in your project settings?

@egregors I disagree that we should exclude .vscode from repository, IT SHOULD NOT contain personal preferences, it should contain project wise preference

Mine does ¯_(ツ)_/¯

Can you provide example what's in your project settings?

"python.pythonPath": "/home/cpro/.pyenv/versions/3.6.6/bin/python",

@egregors I disagree that we should exclude .vscode from repository, IT SHOULD NOT contain personal preferences, it should contain project wise preference

Mine does ¯_(ツ)_/¯

Can you provide example what's in your project settings?

"python.pythonPath": "/home/cpro/.pyenv/versions/3.6.6/bin/python",

Fair enough. Mine contains pyPath as well. ://

@egregors @C-Pro Well, I don't like absolute paths relative to local system, probably something like pipenv/venv/etc would be better. But there's not much we can do now. Maybe later we can focus on enhancing process of development without Dev Container, but for now I have found a solution to use settings json specific to container - https://github.com/microsoft/vscode-dev-containers/blob/main/containers/go/.devcontainer/devcontainer.json#L17 . So we can safely put .vscode/settings.json into .gitignore

BTW I did not set this path manually. It is changed everytime I select interpreter in vscode via dropdown menu on the bottom.

@C-Pro Ye, that is probably not a best place to store interpreter by vscode 🤷♂

[ ] try to use docker-compose-dev.yml for devcontainer

@egregors it seems like no fix to me currently. We should probably somehow remove last line, where we start bot from dev Dockerfile or something else.

[ ]  try to use docker-compose-dev.yml for devcontainer

@egregors it seems like no fix to me currently. We should probably somehow remove last line, where we start bot from dev Dockerfile or something else.

Sure, let's talk about it after NY :D :D I believe we could extract it subtask into a separate issue.
Anyway, your fixes looks grate! I gonna test it locally, just to be sure, and will merge it.

@egregors there are a bit work still left, i accidentally commited junk comments, so probably we should merge after NY🌚🌚

@egregors there are a bit work still left, i accidentally commited junk comments, so probably we should merge after NY🌚🌚

@getjump If you are talking about junk in Dockerfile, I cleaned it already. But if smth else here, and you wanna freeze merge for a time, it's okey.

@egregors Ye that's probably all. I also added new extension by Microsoft, but we can add it later maybe "visualstudioexptteam.intellicode-api-usage-examples"

@egregors Ye that's probably all. I also added new extension by Microsoft, but we can add it later maybe "visualstudioexptteam.intellicode-api-usage-examples"

So, in this way I gonna merge it now. @getjump could you please drop a bit more details in https://github.com/vldc-hq/vldc-bot/issues/237?

authors: C-Pro egregors getjump

repo: vldc-hq/vldc-bot


text:
Feature/camera components

In GitLab by @VitorLamego on Jun 2, 2023, 21:53
Gitlab MR Web Template
Descrição
A issue em questão tem como objetivo adicionar o componente FileSelector, responsável por adicionar arquivos a partir de um botão. A ideia de colocar o componente no szot-ui é para que o componente possa ser inserido no contexto do Form.
Tempo de desenvolvimento
1h30
Tipo de mudança

[ ] Bug fix (Correção de um problema que não quebrava algo grande)
[x] New feature (Mudança que adiciona novas funcionalidades)
[ ] Breaking change (correção ou recurso que faria com que a funcionalidade existente não funcionasse como esperado)
[ ] Refactor (Alteração que melhora algo que já existente)

Em quais navegadores foi testado?

[ ] Google Chrome
[ ] Mozilla Firefox
[ ] IE 11 (Windows 10)
[ ] Edge
[ ] Opera
[ ] Opera GX
[x] IOS Safari
[ ] IOS Chrome
[ ] Android Chrome
[ ] Android Firefox
[x] iOS Simulator

Testei as seguintes resoluções no navegador:

[ ] 2520 x 1080
[ ] 1920 x 1080
[ ] 1400 x 790
[ ] 1280 x 720
[ ] 1024 x 1366 (iPad Pro vertical)
[ ] 1366 x 1024 (iPad Pro horizontal)
[ ] 768 x 1024 (iPad vertical)
[ ] 1024 x 768 (iPad horizontal)
[x] 375 x 812 (iPhone X)
[ ] 320 x 568 (iPhone 5/SE)

Checklist:
Qualidade

[x] Segui os padrões de criação da stack em svelte
[x] Eu revisei ou reli o meu próprio código
[x] Segui o formato de criação e nomenclatura de variáveis CSS

Documentação

[x] Documentei onde era mais necessário e difícil de entender no meu código
[x] Documentei as variáveis CSS que meu componente externaliza
[x] Criei bons exemplos no storybook para meu componente

Teste

[ ] As mudanças que esta MR implementa possui testes automatizados
[x] Executei e garanto que os testes automatizados já criados estão todos passando
[x] Executei e garanto que não há erros de lint
[x] Executei e garanto que não há erros de typescript

MR

[x] Eu conferi a checklist de atividades, e expliquei no meu merge request caso algo não tenha sido necessário ou possível

In GitLab by @VitorLamego on Jun 2, 2023, 21:54
added 1 commit
faf4f395 - FileSelector (refactor): change path of FileSelector
Compare with previous version

In GitLab by @VitorLamego on Jun 2, 2023, 21:55
added 1 commit
afc19bc3 - FileSelector (refactor): change path of FileSelector
Compare with previous version

In GitLab by @VitorLamego on Jun 7, 2023, 17:24
added 5 commits
afc19bc3...7e15de38 - 4 commits from branch masterc9271ad6 - Merge branch 'master' of gitlab.com:team-tecnologia/public-pkgs/szot-ui into...
Compare with previous version

In GitLab by @VitorLamego on Jun 7, 2023, 17:32
added 1 commit
314f07c1 - stories (fix): remove errors from merge
Compare with previous version

In GitLab by @VitorLamego on Jun 7, 2023, 17:38
marked this merge request as ready

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:13
Commented on src/lib/components/formFields/FileSelector/FileSelector.stories.ts line 8
Esse é um componente usado no forms, então a documentação dele tem que está no formfields

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:14
Commented on src/lib/components/formFields/FileSelector/FileSelector.stories.ts line 8
Mudar nos outros locais da documentação para estar tudo dentro da pasta formfields

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:36
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 31
Essas variáveis deveriam estar sendo exportadas, não?

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:38
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 35
Essas aqui tbm não deveriam estar sendo expostas?

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:49
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 70
    return (_value != null);

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:55
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 11
Onde isso está sendo usado?

In GitLab by @DaniloRaposo on Jun 9, 2023, 13:59
Commented on src/lib/components/formFields/FileSelector/FileSelectorExample.svelte line 11
Acho que apenas label ou buttonLabel ficaria um nome melhor para a label do botão, não?

In GitLab by @DaniloRaposo on Jun 9, 2023, 14:00
Acho que seria legal documentar o uso dessa props accept, já que o que ela recebe é meio que uma string especifica

In GitLab by @VitorLamego on Jun 9, 2023, 18:50
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 11
É a tipagem do restProps. Para eu conseguir passar o $restProps dentro do Button eu preciso fazer essa tipagem pro usuário conseguir enviar os argumentos do Button também.

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
Commented on src/lib/components/formFields/FileSelector/FileSelector.stories.ts line 8
changed this line in version 6 of the diff

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 16
changed this line in version 6 of the diff

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 35
changed this line in version 6 of the diff

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 70
changed this line in version 6 of the diff

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
Commented on src/lib/components/formFields/FileSelector/FileSelector.svelte line 85
changed this line in version 6 of the diff

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
Commented on src/lib/components/formFields/FileSelector/FileSelectorExample.svelte line 11
changed this line in version 6 of the diff

In GitLab by @VitorLamego on Jun 9, 2023, 19:44
added 1 commit
5bb57553 - FileSelector (fix): fix errors on mr
Compare with previous version

In GitLab by @VitorLamego on Jun 12, 2023, 19:57
resolved all threads

In GitLab by @DaniloRaposo on Jun 12, 2023, 20:01
approved this merge request

In GitLab by @01oseluiz on Jun 16, 2023, 12:59
added 5 commits
5bb57553...42c589f1 - 4 commits from branch master887eb731 - Merge remote-tracking branch 'origin/master' into feature/camera-components
Compare with previous version

In GitLab by @victoragcosta on Jun 16, 2023, 13:25
requested review from @victoragcosta

In GitLab by @01oseluiz on Jul 6, 2023, 11:33
changed target branch from master to develop

In GitLab by @01oseluiz on Jul 6, 2023, 12:44
Pelo que me lembro de ter falado com o cubo isso daqui ia ser fechado e levado para o mobile diretamente.

repo: vlgi/ui


text:
Can vLLM support medusa head?

https://sites.google.com/view/medusa-llm

@simon-mo is this a feature you'd like to see implemented?

Is there any plan for implementing this feature? Will it occur in Q2 roadmap?

Yes this is planned to happen. After the speculative decoding framework is in.

authors: MichaelJayW chizhang118 hmellor simon-mo

repo: vllm-project/vllm


text:
[Usage]: Llama-2-7b-chat-hf as embedding model

Your current environment
Following the code example provided here, I modified the model to Llama-2-7b-chat-hf and attempted to run the code, but I encountered the following error:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[3], line 4
      2 model = LLM(model="//common/public/LLAMA2-HF/Llama-2-7b-chat-hf", enforce_eager=True, task="embedding")
      3 # Generate embedding. The output is a list of EmbeddingRequestOutputs.
----> 4 outputs = model.encode(prompts)
      6 # # Print the outputs.
      7 # for output in outputs:
      8 #     print(output.outputs.embedding)  # list of 4096 floats

File ~/second/lib/python3.10/site-packages/vllm/utils.py:1063, in deprecate_kwargs.<locals>.wrapper.<locals>.inner(*args, **kwargs)
   1056             msg += f" {additional_message}"
   1058         warnings.warn(
   1059             DeprecationWarning(msg),
   1060             stacklevel=3,  # The inner function takes up one level
   1061         )
-> 1063 return fn(*args, **kwargs)

File ~/second/lib/python3.10/site-packages/vllm/entrypoints/llm.py:781, in LLM.encode(self, prompts, pooling_params, prompt_token_ids, use_tqdm, lora_request, prompt_adapter_request)
    772     pooling_params = PoolingParams()
    774 self._validate_and_add_requests(
    775     prompts=parsed_prompts,
    776     params=pooling_params,
    777     lora_request=lora_request,
    778     prompt_adapter_request=prompt_adapter_request,
    779 )
--> 781 outputs = self._run_engine(use_tqdm=use_tqdm)
    782 return self.engine_class.validate_outputs(outputs,
    783                                           EmbeddingRequestOutput)

File ~/second/lib/python3.10/site-packages/vllm/entrypoints/llm.py:942, in LLM._run_engine(self, use_tqdm)
    940 total_out_toks = 0
    941 while self.llm_engine.has_unfinished_requests():
--> 942     step_outputs = self.llm_engine.step()
    943     for output in step_outputs:
    944         if output.finished:

File ~/second/lib/python3.10/site-packages/vllm/engine/llm_engine.py:1454, in LLMEngine.step(self)
   1450 if allow_async_output_proc:
   1451     execute_model_req.async_callback = self.async_callbacks[
   1452         virtual_engine]
-> 1454 outputs = self.model_executor.execute_model(
   1455     execute_model_req=execute_model_req)
   1457 # We need to do this here so that last step's sampled_token_ids can
   1458 # be passed to the next iteration for PP.
   1459 if self.scheduler_config.is_multi_step:

File ~/second/lib/python3.10/site-packages/vllm/executor/gpu_executor.py:125, in GPUExecutor.execute_model(self, execute_model_req)
    122 def execute_model(
    123     self, execute_model_req: ExecuteModelRequest
    124 ) -> Optional[List[Union[SamplerOutput, PoolerOutput]]]:
--> 125     output = self.driver_worker.execute_model(execute_model_req)
    126     return output

File ~/second/lib/python3.10/site-packages/vllm/worker/worker_base.py:343, in LocalOrDistributedWorkerBase.execute_model(self, execute_model_req)
    338     if (self.observability_config is not None
    339             and self.observability_config.collect_model_execute_time):
    340         orig_model_execute_time = intermediate_tensors.tensors.get(
    341             "model_execute_time", torch.tensor(0)).item()
--> 343 output = self.model_runner.execute_model(
    344     model_input=model_input,
    345     kv_caches=self.kv_cache[worker_input.virtual_engine]
    346     if self.kv_cache is not None else None,
    347     intermediate_tensors=intermediate_tensors,
    348     num_steps=num_steps,
    349     **kwargs,
    350 )
    352 model_execute_time = time.perf_counter() - start_time
    353 if not get_pp_group().is_last_rank:
    354     # output is IntermediateTensors

File ~/second/lib/python3.10/site-packages/torch/utils/_contextlib.py:116, in context_decorator.<locals>.decorate_context(*args, **kwargs)
    113 @functools.wraps(func)
    114 def decorate_context(*args, **kwargs):
    115     with ctx_factory():
--> 116         return func(*args, **kwargs)

File ~/second/lib/python3.10/site-packages/vllm/worker/embedding_model_runner.py:138, in EmbeddingModelRunner.execute_model(self, model_input, kv_caches, intermediate_tensors, num_steps)
    134 if not self.is_driver_worker:
    135     return []
    137 return [
--> 138     self.model.pooler(hidden_states=hidden_or_intermediate_states,
    139                       pooling_metadata=model_input.pooling_metadata)
    140 ]

File ~/second/lib/python3.10/site-packages/vllm/model_executor/models/llama.py:573, in LlamaForCausalLM.pooler(self, hidden_states, pooling_metadata)
    567 def pooler(
    568     self,
    569     hidden_states: torch.Tensor,
    570     pooling_metadata: PoolingMetadata,
    571 ) -> Optional[PoolerOutput]:
    572     logits = self.compute_logits(hidden_states, None)
--> 573     return self._pooler(logits, pooling_metadata)

File ~/second/lib/python3.10/site-packages/torch/nn/modules/module.py:1736, in Module._wrapped_call_impl(self, *args, **kwargs)
   1734     return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1735 else:
-> 1736     return self._call_impl(*args, **kwargs)

File ~/second/lib/python3.10/site-packages/torch/nn/modules/module.py:1747, in Module._call_impl(self, *args, **kwargs)
   1742 # If we don't have any hooks, we want to skip the rest of the logic in
   1743 # this function, and just call forward.
   1744 if not (self._backward_hooks or self._backward_pre_hooks or self._forward_hooks or self._forward_pre_hooks
   1745         or _global_backward_pre_hooks or _global_backward_hooks
   1746         or _global_forward_hooks or _global_forward_pre_hooks):
-> 1747     return forward_call(*args, **kwargs)
   1749 result = None
   1750 called_always_called_hooks = set()

File ~/second/lib/python3.10/site-packages/vllm/model_executor/layers/pooler.py:136, in Pooler.forward(self, hidden_states, pooling_metadata)
    133         offset += prompt_len
    134         pooled_data_lst.append(pooled_data_i)
--> 136     pooled_data = torch.stack(pooled_data_lst)
    137 else:
    138     raise ValueError(f"Invalid pooling type: {self.pooling_type}")

RuntimeError: stack expects each tensor to be equal size, but got [6, 32000] at entry 0 and [8, 32000] at entry 1

Given below is the code I'm using:
from vllm import LLM

# Sample prompts.
prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]

# Create an LLM
model = LLM(
    model="//common/public/LLAMA2-HF/Llama-2-7b-chat-hf",
    enforce_eager=True,
    task="embedding",
)

# Generate embedding. The output is a list of EmbeddingRequestOutputs.
outputs = model.encode(prompts)

How would you like to use vllm
I want to run inference to extract embeddings but I'm encountering errors. Help would be appreciated.
Before submitting a new issue...

[x] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Hi, I'm pulling the latest vllm version v0.6.4.post1. Is that what you meant?

No, I am referring to latest main branch.

Please see here for installation instructions.

Hi @DarkLight1337,
The code generates outputs of size 6 and 32,000 (for the first example), and the outputs is a list of length 4. Contrary to what's stated, the code actually provides a list of 4,096 floats. Could you please help me understand this discrepancy? The size of 32,000 appears to be related to the vocabulary size.
len(outputs[0].outputs.embedding[0]) --> 32000 instead of 4096

The embedding size depends on the model. Since you have changed the model to a different one, the output size may also be different.

Hi @DarkLight1337 I'm getting following text while prompts are being processed, how to deal with it?
Autosave too slow: 503.74 sec, over 25% limit. Backing off to 100 sec

Processed prompts:   0%|          | 0/12928 [00:00<?, ?it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Processed prompts:   0%|          | 1/12928 [00:09<35:33:09,  9.90s/it, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Processed prompts:   2%|▏         | 257/12928 [00:19<13:24, 15.75it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Processed prompts:   4%|▍         | 513/12928 [00:28<09:56, 20.81it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Processed prompts:   6%|▌         | 769/12928 [00:38<08:43, 23.24it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Processed prompts:   8%|▊         | 1024/12928 [00:48<08:32, 23.24it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Processed prompts:   8%|▊         | 1025/12928 [00:57<11:03, 17.94it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Autosave too slow: 503.74 sec, over 25% limit. Backing off to 100 sec
Processed prompts:  10%|▉         | 1280/12928 [01:18<10:49, 17.94it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]

This message seems to be from Jupyter Notebook, maybe the size of your notebook is being inflated by the tqdm output?


text:
What a fast tokenizer can be used for Baichuan-13b?

"When I was running baichuan-13b, I received the following warning: 'Using a slow tokenizer. This might cause a significant slowdown. Consider using a fast tokenizer instead.' How can I solve this? What  a fast tokenizer can I use?"

same question

+1

+1

same.
And I have met another problem, which is I got worse results when inferring with only 1 input and unusable results when inferring with multiple inputs. weird.
I have tried to align the samplingparams with the generation config in Baichuan's code, which is below
SamplingParams(temperature=0.3, top_p=0.85, top_k=5, max_tokens=4096, presence_penalty=1.1)

I have met the same question,do we need to write a new fast tokenzier?

how long do you load baihcuan2_13b?
请教楼主，你加载13b模型需要多久时间呢

same problem

same problem，how to solve it...help....


text:
[Frontend][Misc] Goodput metric support

This PR adds support of goodput metric for benchmarking serving system.
If the user doesn't specify --goodput, request goodput will not be shown.
Supported service level objectives: TTFT, TPOT, E2EL
FIX #8782
Usage Example
Start a server
vllm serve meta-llama/Llama-3.2-1B-Instruct \
    --disable-log-requests \
    --tensor-parallel-size 1 \

Benchmark serving with goodput
cd benchmarks
python benchmark_serving.py \
    --backend vllm \
    --model meta-llama/Llama-3.2-1B-Instruct \
    --dataset-name sonnet \
    --num-prompt=10 \
    --dataset-path="sonnet.txt" \
    --sonnet-input-len 600 \
    --save-result  \
    --goodput ttft:500 tpot:14 e2el:2500

Example Console Output
============ Serving Benchmark Result ============
Successful requests:                     10
Benchmark duration (s):                  2.37
Total input tokens:                      5477
Total generated tokens:                  1500
Request throughput (req/s):              4.23
Request goodput (req/s):                 1.69
Output token throughput (tok/s):         634.23
Total Token throughput (tok/s):          2950.01
---------------Time to First Token----------------
Mean TTFT (ms):                          288.13
Median TTFT (ms):                        272.04
P99 TTFT (ms):                           435.43
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          13.93
Median TPOT (ms):                        14.04
P99 TPOT (ms):                           14.89
---------------Inter-token Latency----------------
Mean ITL (ms):                           13.93
Median ITL (ms):                         12.85
P99 ITL (ms):                            14.35
==================================================

TODO

[ ] Investigate proper service level objectives for CI Dashboard model.
[ ] Add goodput plot to CI Dashboard.

cc: @ywang96 @KuntaiDu Any inputs from you and the community will be extremely valuable for future CI Dashboard work on Goodput. Like what kind of plots,  setting what kind of SLOs for different LLM applications on different CI hardware.

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Hey @ywang96 @KuntaiDu do you have any thoughts on @Imss27 question above?

cc: @ywang96 @KuntaiDu Any inputs from you and the community will be extremely valuable for future CI Dashboard work on Goodput. Like what kind of plots, setting what kind of SLOs for different LLM applications on different CI hardware.

I am not an industry guy so I am not the best guy checking if the definition of TTFT < TTFT SLO and Average TPOT < TPOT SLO is the right way to define goodput (especially using average TPOT < TPOT SLO to define goodput) @comaniac @ywang96 would be great if you can share your thoughts!

I am not an industry guy so I am not the best guy checking if the definition of TTFT < TTFT SLO and Average TPOT < TPOT SLO is the right way to define goodput (especially using average TPOT < TPOT SLO to define goodput) @comaniac @ywang96 would be great if you can share your thoughts!

Goodput is a well-defined term in https://arxiv.org/pdf/2401.09670. @Imss27 please provide more information about goodput in the RFC, PR description and the script.

I am not an industry guy so I am not the best guy checking if the definition of TTFT < TTFT SLO and Average TPOT < TPOT SLO is the right way to define goodput (especially using average TPOT < TPOT SLO to define goodput) @comaniac @ywang96 would be great if you can share your thoughts!

Yes - I can confirm that in our paper, a request is "good" if

its TTFT < TTFT SLO
its average TPOT < TPOT SLO

In practice, whether this is a good enough metric remains questionable, although this is what a lot of other LLM system paper still continues to use.

Thanks for the review and discussion! Updated according to the great suggestions.
@comaniac Please take a look when you get a chance😄

Found a bug during local test🤣, we compared values in the wrong direction for SLOs and req_metrics. Please take a look when you get a chance. @comaniac

authors: GindaChen Imss27 KuntaiDu andoorve comaniac


text:
Doesn't seem to support '$and' or '$or' filtering

Doesn't seem to support conditional queries:
Example
object = my_collection.find_one(
{'$and': [{'object_id': object_id},
{'$or': [{'has_attr': 1}, {'has_attr': True}]}]
})
it returns None when there is a fixture like this

Nevermind, you need to stringify str() all integers before passing them in for query.

repo: vmalloc/mongomock


text:
get garbled text after render chartjs unexpectedly

Hi everyone,
I run the sample and output image successful, but all text become garbled text in the image :

Did I miss something ?
[Environment]
OS : centos 7,5
Nodejs : v8.11.3
npm : 5.6.0
Thanks.

I had install font and set the parameter as below, it seems work now !
chartNode.on('beforeDraw', function (Chartjs) { 		//Chartjs.defaults 		//Chartjs.pluginService 		//Chartjs.scaleService 		//Chartjs.layoutService 		//Chartjs.helpers 		//Chartjs.controllers 		//etc 		Chartjs.defaults.global.defaultFontFamily = "cjkuni-ukai-fonts"; 		Chartjs.defaults.global.defaultFontSize = 18; 		Chartjs.defaults.global.defaultFontColor = 'blue'; 	});

repo: vmpowerio/chartjs-node


text:
Enhance the module to use status codes for API requests

Code of Conduct

[X] I have read and agree to the project's Code of Conduct.
[X] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
[X] Do not leave "+1" or other comments that do not add relevant information or questions.
[X] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description
Enhance the module to use API status code, where applicable, for low-level API requests.
Use Case(s)
Enhanced error handling for API requests.
Potential Configuration
    $results = Invoke-Webrequest -uri https://api.rainpole.io/api/v1/hello -Method Get -headers $headers
    if($results.StatusCode -ne 200) {
        Write-Output "Whoopies!"
        break
    }

References
No response

I'll be working on portion of this issue.

This may not be possible in the module. Our code used Invoke-RestMethod versus Invoke-Webrequest. Based on my research, only the latter with return the status codes, unless there is another option to do so with Invoke-RestMethod.
Ryan

Invoke-RestMethod directly returns JSON and XML to objects while with Invoke-WebRequest you have to convert it from JSON to PS objects
Example getting NSXT transport zones:

Option 1 (Invoke-RestMethod)

$restMethod = Invoke-RestMethod -Method Get -Uri "https://$nsxtmanager/api/v1/transport-zones" -ContentType application/json -Headers $nsxtHeaders
$results = $restMethod.results

Option 2 (Invoke-WebRequest)

$webRequest = Invoke-WebRequest -Method Get -Uri "https://$nsxtmanager/api/v1/transport-zones" -ContentType application/json -Headers $nsxtHeaders
$results = ($webRequest.Content | ConvertFrom-Json).results

The difference is that with Invoke-WebRequest we got some additional properties like Headers, StatusCode and StatusDescription that can be used for error handling

Invoke-RestMethod

PS C:\Windows\system32> $RestMethod | gm

   TypeName: System.Management.Automation.PSCustomObject

Name           MemberType   Definition
----           ----------   ----------
Equals         Method       bool Equals(System.Object obj)
GetHashCode    Method       int GetHashCode()
GetType        Method       type GetType()
ToString       Method       string ToString()
results        NoteProperty Object[] results=System.Object[]
result_count   NoteProperty int result_count=3
sort_ascending NoteProperty bool sort_ascending=True
sort_by        NoteProperty string sort_by=display_name

Invoke-WebRequest

PS C:\Windows\system32> $webRequest | gm

   TypeName: Microsoft.PowerShell.Commands.HtmlWebResponseObject

Name              MemberType Definition
----              ---------- ----------
Dispose           Method     void Dispose(), void IDisposable.Dispose()
Equals            Method     bool Equals(System.Object obj)
GetHashCode       Method     int GetHashCode()
GetType           Method     type GetType()
ToString          Method     string ToString()
AllElements       Property   Microsoft.PowerShell.Commands.WebCmdletElementCollection AllElements {get;}
BaseResponse      Property   System.Net.WebResponse BaseResponse {get;set;}
Content           Property   string Content {get;}
Forms             Property   Microsoft.PowerShell.Commands.FormObjectCollection Forms {get;}
Headers           Property   System.Collections.Generic.Dictionary[string,string] Headers {get;}
Images            Property   Microsoft.PowerShell.Commands.WebCmdletElementCollection Images {get;}
InputFields       Property   Microsoft.PowerShell.Commands.WebCmdletElementCollection InputFields {get;}
Links             Property   Microsoft.PowerShell.Commands.WebCmdletElementCollection Links {get;}
ParsedHtml        Property   mshtml.IHTMLDocument2 ParsedHtml {get;}
RawContent        Property   string RawContent {get;set;}
RawContentLength  Property   long RawContentLength {get;}
RawContentStream  Property   System.IO.MemoryStream RawContentStream {get;}
Scripts           Property   Microsoft.PowerShell.Commands.WebCmdletElementCollection Scripts {get;}
StatusCode        Property   int StatusCode {get;}
StatusDescription Property   string StatusDescription {get;}

In the Power Validated Solutions mainly Invoke-RestMethod is used and a few times Invoke-WebRequest
In PowerShell 7 Invoke-RestMethod  introduce [-StatusCodeVariable ] but AFAIK PVS is not yet PS7 compatible

Thanks for the research, Tony. Given that this would be a major overhaul and that our focus is PS5+, we'll table this for future consideration.

authors: antonystefanov tenthirtyam


text:
[Docs]

Description
The PackageRepository tag (i.e. projects.registry.vmware.com/tce/main:0.9.1) mentioned in the docs here seems to be out of date with the Package versions mentioned in the docs.
Wondering if the tag should be 0.10.0 instead of 0.9.1? This seems to pull in the correct Package versions that match the current docs.
Additional Context
I am installing the PackageRepository without using the tanzu cli. Just using a PackageRepository resource that references the above bundle.

I think this may be a side effect due to our lack of versioned docs so far. The currently released version of TCE is v0.9.1, but there have been updated merged in to the repo for our next (v0.10.0) release. Prior to that release, but after the next package tag is created, the docs should be updated to point to the new main:0.10.0.
@seemiller - can you confirm?

Please re-open if there's any follow-up needed.
At this point, docs should always reference 0.9.1 as its the only thing we've released (while technically 0.10.0 is discoverable, it's not released).

authors: danielhelfand joshrosso stmcginnis

repo: vmware-tanzu/community-edition


text:
Dynamic Supervisor OIDC Clients proposal

Technical Proposal: "Dynamic Supervisor OIDC Clients"
Release note:
NONE

Thanks Ryan. I've left a bunch of thoughts as I read through - apologies in advance for anything I've misunderstood (a few times later points you made clarified my earlier questions) or for which I lack the relevant background :)

@absoludity I'm not sure why, but GitHub won't let me reply to your comment which said "That would be different to most other client definitions, wouldn't it? (not that it's a reason not to do so)".
I'm not sure what you mean by that comment. Could you explain? Thanks!

repo: vmware-tanzu/pinniped


text:
ng add @clr/angular@next fails with Angular9

Describe the bug
ng add @clr/angular@next

fails on a fresh new Angual9 project
How to reproduce
Steps to reproduce the behavior:

Create a new Angular9 project with ng add my-project
Add clarity 3 next with ng add @clr/angular@next

I get this error
An unhandled exception occurred: Collection "@clr/angular" cannot be resolved.
See "/private/var/folders/xv/8mqxb9qx61bbj7bvxgdv9vmm0000gq/T/ng-II6mmk/angular-errors.log" for further details.

angular-errors.log
Expected behavior
Everything goes well
Versions
App

Angular: 9.0.1
Angular CLI: 9.0.2
Node: 10.13.0
Clarity: 3.0@next0

Device:

Type: MacBook
OS: macOS

This is a known issue due to a publishing error, it will be resolved in the next release. Essentially the schematics weren't published with the package.

Fixed by #4262. Will be fixed in next release.

repo: vmware/clarity


text:
SMTP without TLS doesn't work

Hello,
I have installed Harbor but sending mail via an no authenticated internal smtp server doesn't work.
The ping is ok for information
I have this in the ui.log
Feb 13 14:37:41 172.19.0.1 ui[447]: 2018-02-13T13:37:41Z [DEBUG] [mail.go:92]: establishing TCP connection with smtp.******.com:25 ...
Feb 13 14:37:41 172.19.0.1 ui[447]: 2018-02-13T13:37:41Z [DEBUG] [mail.go:117]: creating SMTP client for smtp.*********.com ...
Feb 13 14:37:41 172.19.0.1 ui[447]: 2018-02-13T13:37:41Z [DEBUG] [mail.go:134]: the email server smtp.********.com:25 does not support STARTTLS
Feb 13 14:37:41 172.19.0.1 ui[447]: 2018-02-13T13:37:41Z [DEBUG] [mail.go:139]: authenticating the client...
Feb 13 14:37:41 172.19.0.1 ui[447]: 2018-02-13T13:37:41Z [ERROR] [email.go:109]: failed to ping email server: unencrypted connection

My harbor.cfg
email_identity =

email_server = smtp.******.com
email_server_port = 25
email_username =
email_password =
email_from = Admin Docker-Hub  <docker-hub_admin@*****.com>
email_ssl = false
email_insecure = true

Docker version
Server:
 Engine:
  Version:  17.12.0-ce
  API version: 1.35 (minimum version 1.12)
  Go version: go1.9.2
  Git commit: c97c6d6
  Built: Wed Dec 27 20:09:54 2017
  OS/Arch:  linux/amd64
  Experimental: false

Docker Compose version
docker-compose version 1.8.0, build unknown
docker-py version: 1.9.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.1.0f  25 May 2017

The credentials are only sent when the connection is using TLS for security issue. So make sure your SMTP server supports TLS.

I don't use a SMTP TLS server.

I have the exact same issue.
I use an internal mail server without TLS

Fixed by #4375.

repo: vmware/harbor


text:
Add an architecture diagram

I cannot "sell" VDK to engineers unless they assess the architecture. A picture is worth a thousand words. A reusable file (e.g. .pptx) would be even better.

Triaged. This is WiP that will be completed soon.

authors: PyMeH sabadzhiev

repo: vmware/versatile-data-kit


text:
运行回测时需要给datetime添加时区信息

环境

操作系统: ALL
Python版本: ALL
VeighNa版本: ALL

Issue类型
三选一：Bug
运行回测时需要给datetime添加时区信息，否者输入的时间和实际想要回测的时间会不一致哦，建议官方在图形界面和example里边修改一下
'''
from pytz import timezone
DB_TZ = timezone("Asia/Shanghai")
start=datetime(2021, 11, 1,6,5).astimezone(DB_TZ),
end=datetime(2022, 3, 11,12,23).astimezone(DB_TZ),
'''

请问你用的数据库是mongodb吗？

对

已经在vnpy_mongodb修复

authors: EzMoney-Sniper noranhe vnpy

repo: vnpy/vnpy


text:
新增DataRecording应用场景下面的时序图资料

建议每次发起的PR内容尽可能精简，复杂的修改请拆分为多次PR，便于管理合并。
改进内容

增加文档资料。利用plantUML做成DataRecording应用场景下面的时序图，便于新手理解各layer的工作机制和作用。

相关的Issue号（如有）
Close #

请给个功能说明吧


text:
Automatic slides screening

By analyzing the slides source a switch to another slide seems easy to detect.
voc2mix easily could use that information to get informed about when the speaker is switching the current slide.
This signal could be easily used to switch to a composite lec(slides,camX) or fs(slides) automatically if slides are currently not shown.
I think that would give the speaker a more natural access to the mixing output when she/he starts to explain something new which is on slide.

This would be great, but I would also like a way to disable it on the fly, like when the presenter has an animated gif on their slides that trips the "new slide" trigger.
more ideas:
disable for X seconds - 15 seconds perhaps.   my main thought is to stop thrashing between two sources  - like often my talks involve discussing a long running script - the only thing interesting about the spew of text is we can tell it is still active, but we don't need to focus on all the gcc warnings and what dirs things are being installed to.
sensitivity adjustment - I am assuming the analyzing will have a threshold that needs to be exceeded to trigger "change"  provide a ui control to adjust that, I can see it being adjusted per talk.

authors: CarlFK fightling

repo: voc/voctomix


text:
Install repo2docker from git

Since it will correspond to the most recent version, and Binder also uses the latest repo2docker.

Looks good:

repo: voila-dashboards/tljh-voila-gallery


text:
Why are there two definition files of Queue and PodGroup in the apis/scheduling directory?

There are two definition files of Queue and PodGroup in the apis/scheduling directory, such as apis/scheduling/types.go and apis/scheduling/v1beta1/types.go. Both files are used in the code.  Are there any design considerations？

I think they can be merged as one.

apis/scheduling/types.go does not include version, apis/scheduling/v1beta1/types.go has version info.

Thanks for your answer.

/close

repo: volcano-sh/apis


text:
Lookup filter

Dialog  olulşturuldugunda   şartlara göre Lookup doldurmak istiyorum. Yardımcı olurmusunuz
aşağıdaki gibi yaptım fakat olmadı.
constructor() {
this.form.AdresId.items =AdresRow.getLookup().items.filter(f => f.Id === 5 );
}

LookupEditor bu şekilde çalışmaz. FilterField, FilterValue deneyin.

authors: YunusV volkanceylan

repo: volkanceylan/Serenity


text:
Customer Dialog Template Overlap

I'm having an issue with a Dialog Template overlap that seems to be ghosting around and I can't figure out where to remove it from.
I created most of my tables before removing the Northwind Database and Samples. At the time there seemed to have been a overlap where my own Customer table in Modules/MyProject/Customer was overlapping with the Northwind Customer dialog template. After I removed all of the Northwind and samples data, per manual, I now have an odd Dialog template that has broken tab links yet I can't find where it's feeding from. I attached a screen shot.
As a side note, I did notice that every time I rebuild the MVC.cs file also re-adds the Northwind Class, no matter how many times I've removed it. I've ran up and down the files making sure to scrub out Northwind and have yet to find it.

You have Northwind folder in disk. Use file explorer to delete files.

Damn. So simple ....I completely forgot about that. sorry for the troubles.

Np. If you dont want templates got mixed you can prefix them with namespaces. E.g. Northwind.CustomerDialog.Template.html

I know but since I was planning on getting rid of Northwind anyway I didn't bother. I just haven't finished scrubbing out the disk side of things due to laziness since I'm still developing the platform. I'm planning on redoing a number templates we need internally anyhow so I figured I'd deal with it then,.

authors: sayuga volkanceylan


text:
Dynamic Home/Landing Page, based on permissions?

As the subject says, I am looking for a good/best practice way to "redirect" a users login/landing page (after authentication, of course), based on that users "permissions" (and/or "roles"). Is anyone willing to share what they have done?

you can redirect like in MVC after Loggedin.
If you want to reach this page with any permission who is loggedin, you can use Permission("?") on action.

You could also handle this in AccountLogin.cshtml or Login.ts based on your version, use Q.Authorization.hasPermission etc.

authors: ShayneJud hubeyb volkanceylan


text:
Alert message not in local language

Hi, this I cannot understand :).

Should be English.

Configuration automatically loaded web.config

Converted to localtext, will be in next version.

authors: 107295472 volkanceylan wpvking


text:
mini_magick dependency conflicts with CarrierWave bug workaround

Just an FYI, there's currently some issues with CarrierWave when using certain features that forces one to require an old version of mini_magick (~> 3.8.0): https://github.com/carrierwaveuploader/carrierwave/issues/1520
Since bootsy requires mini_magick ~> 4.0, this causes issues with those of us that need to use the old version of mini_magick. No biggie, I made my own fork to work around it, but just wanted to let you know.
P.S. thanks for the neat gem!

Thanks for letting me know, I wasn't aware of that. By the way, how did you fix it? Did you just change the dependency to >= 3.8?

In my fork I removed the version clause since I already have it pinned in my application's Gemfile. But yeah >= 3.8 should work.

Looks like this is no longer an issue on the latest versions. Thanks for the help!

authors: abevoelker volmer

repo: volmer/bootsy


text:
Update jtcop up to 0.1.16

Update jtcop up to the 0.1.16 version.
Add assertion messages for all the rest tests.

PR-Codex overview
Focus of this PR:
Update the version of a Maven plugin and add additional assertions in test cases.
Detailed summary:

Updated the version of the jtcop-maven-plugin to 0.1.16 in the pom.xml file.
Added additional assertions in the ModelSourceFileSystemTest and ProjectJavaParserTest test cases.
Added formatted error messages for assertion failures in various test cases.
Added new test cases in the RulePresentSimpleMlTest, TestCaseJavaParserTest, TestClassJavaParserTest, and TestClassJavaParserTest classes.
Improved error messages and added additional assertions in the TestClassJavaParserTest class.

The following files were skipped due to too many changes: src/test/java/com/github/lombrozo/testnames/javaparser/TestClassJavaParserTest.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

authors: rultor volodya-lombrozo

repo: volodya-lombrozo/jtcop


text:
Patch to improve item highlighting in project/context selectors

It's a minor UX thing, but it would be nice, IMO, if item highlighting filled the whole Selector width, like it does for completion.
Here's a patch:
98-fix-highlghting-in-project-context-selectors.diff.gz
In addition, would it be possible not to truncate project and context selector titles? Maybe a minimal title width can be implemented to make sure short titles like "Select project" and "Select context" do not get ellipsized?

Without minimal title width, we can get a situation like this:

:)

Patch is merged and the title is no longer cut off!

Nice!

authors: andrei-a-papou vonshednob

repo: vonshednob/pter


text:
CivicInfoAPIKey.plist.template CivicInfoAPIKey.plist couldn't be opened

Hi guys,
I am trying to run the project  by following the readme file but it is giving me error. Please see the attached snap-shots. Thanks
On Terminal

On XCode

Path

Thanks for bringing this to our attention.
Looks like the cp command in the readme is wrong. Try:
cp CivicAPIKey.plist.template CivicAPIKey.plist

Thanks, It worked!!!

authors: CloudNiner Frehiwet


text:
First version of the colang plugin.

A first implementation of exporting a Voxable project into Colang. It doesn't have support for contexts yet.
The output is dumped at stdout and can be copy-pasted into the colang playground to play with.

Thanks so much again for being our first contributor, @drazvan! 😃 I'll be reviewing & merging this ASAP.
I wanted to let you know that we just relicensed the project to the BSD 3-Clause License. It's essentially the same as the  MIT License, with one additional clause to protect the Voxable trademark.
This was just based on advice we received and isn't related to any changes in this PR. I just wanted to let you know since you're our only contributor so far, and we made this change after you submitted your code.

Thanks so much again for being our first contributor, @drazvan! 😃 I'll be reviewing & merging this ASAP.
I wanted to let you know that we just relicensed the project to the BSD 3-Clause License. It's essentially the same as the MIT License, with one additional clause to protect the Voxable trademark.
This was just based on advice we received and isn't related to any changes in this PR. I just wanted to let you know since you're our only contributor so far, and we made this change after you submitted your code.

Thanks for the info, Matt. Yes, the BSD 3 license ok for my contribution ;)

authors: drazvan techpeace

repo: voxable/cli


text:
[BUG] Copying views is broken for stages with VALUE

I'm having difficulty understanding the logic of ViewExpression.__deepcopy__ but it is where the issue is, I believe.
from copy import copy

import fiftyone as fo
import fiftyone.zoo as foz
from fiftyone.core.expressions import VALUE

F = fo.ViewField

dataset = foz.load_zoo_dataset("quickstart")
view = dataset.set_field("ground_truth.tags", F("$ground_truth.detections").reduce(VALUE.extend(F("tags")), []))
print(view._stages[-1]._expr)

copied_view = copy(view)
print(copied_view._stages[-1]._expr)

OUT:
{
    '$reduce': {
        'input': '$ground_truth.detections',
        'initialValue': [],
        'in': {'$concatArrays': ['$$value', '$$this.tags']},
    },
}
{
    '$reduce': {
        'input': '$ground_truth.detections',
        'initialValue': [],
        'in': {'$concatArrays': ['$value', '$tags']},
    },
}

The copied expr has one of its $ removed.

Hmm looks like this is the problem:
from copy import deepcopy
from fiftyone.core.expressions import VALUE

print(VALUE)
# '$$value'

print(deepcopy(VALUE))
# '$value'

authors: benjaminpkane brimoor


text:
[BUG] workflow for patching quickstart groups

I THINK this solves the rotation issue for quickstart-groups. The transformation makes the bounding boxes fit the objects really well. The fit isn't perfect, but I've compared against the KITTI multiview (and original quickstart groups) and the fit isn't perfect in those either. Take a look for yourself.
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

Users should know that the detections are stored with different directions and numbers, so their quantitative results will be impacted if they use the same pipeline for the old and new versions of the dataset for anything that involves compute.
(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
Undoing the "pointCloud", "overlay", and "itemRotation" from 3D visualizer, making the coordinates of the detections match the point cloud coordinates out of the box.
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[x] Documentation: FiftyOne documentation changes
[x] Other -- zoo dataset

Superseded by https://github.com/voxel51/fiftyone/pull/2474.

authors: brimoor jacobmarks


text:
Merge release/v0.24.1

Summary by CodeRabbit

New Features

Added a new method for downloading 3D scene assets in the fiftyone package.
Introduced parameters for controlling dataset persistence and generation behavior in various dataset creation functions.

Bug Fixes

Corrected a comment related to sample_id association with frames in clips datasets.

Documentation

Updated documentation to include new methods and parameters.
Adjusted header levels in the anomaly detection tutorial for better content presentation.

Refactor

Improved handling of file paths and asset paths across multiple modules for consistency and robustness.
Renamed and simplified functions in the storage module.

Tests

Added new test methods to verify the functionality of patch generation and asset path updates.
Modified existing tests to ensure accurate path handling and dataset persistence.

Closing in favor of #4459


text:
add forwarding delegate being able to implements unused UIcollectionV…

…iewDelegate methods in the controller

Coverage increased (+0.01%) to 96.633% when pulling 0e90963189a4a6c95867cd6c26c055121d053779 on forwardingDelegate into bde2244334d9528d2c694a6baa9fae766845609f on master.

authors: coveralls gwennguihal

repo: voyages-sncf-technologies/Collor


text:
Remove compress dependency

Functionality of the compress dependency is available through the node zlib module. This pull request removes the compress dependency and replaces it with zlib.
The PR also adds a test for the server compression. This test consists of sending the same request twice, once through a soap client, once through a gzip stream. Afterwards both responses are checked for equality.
I based the test on an example from the request-response-samples folder. This might not be ideal, so feel free to suggest another wsdl file and example request that I can use.

Coverage increased (+0.4%) to 93.513% when pulling b6efeb4d0ad21061c6840585d5734841b90485d6 on tdecaluwe:remove-compress into 01d8585b9f33381821c5ba4e10acf3fb6ab98f19 on vpulim:master.

Coverage increased (+0.4%) to 93.513% when pulling b6d33d0b27c4df8aeba29cac26fca5553f84a83f on tdecaluwe:remove-compress into 01d8585b9f33381821c5ba4e10acf3fb6ab98f19 on vpulim:master.

please rebase your PR with the latest master - I updated our travis.yml in order to fix the failing node 4.x tests 👍

Coverage increased (+0.4%) to 93.513% when pulling 3d0e03445899f09c65512fd006382191d8c7e5d6 on tdecaluwe:remove-compress into 84628de9c7e9aa3b3c7e1206568700b9cef1407f on vpulim:master.

Thanks a lot @tdecaluwe 👍

authors: coveralls herom tdecaluwe

repo: vpulim/node-soap


text:
CustomSelect not taking style attribute

Unless I am overlooking something, settings the style attribute on a CustomSelect doesn't propagate into the actual drawn div with the 'cui-custom-select' class. The documentation says that style is a valid attribute.
Thank you for your amazing work, it has been smooth sailing!

Fix in v0.3.1, thanks!

authors: jdiderik vrimar

repo: vrimar/construct-ui


text:
Windows 11 and sleep

First of all, I must give my thanks for this developing this software, it is keeping my headset from turning itself off all the time which is a nuisance.
This issue has previously been mentioned here.
To summarize, SoundKeeper prevents Windows 11 from entering sleep mode. It is not an issue in Windows 10 or older operating systems.
I am not satisfied with the proposed solution of allowing Windows 11 to go into sleep mode no matter what is occurring on the screen, for example you could be watching a movie or Youtube video and the computer will go to sleep.
With Windows 10 updates becoming deprecated soon perhaps it's time to revisit this problem and implement a proper solution?

Microsoft needs to either provide a way to stream audio using WASAPI without blocking sleep mode, or fix NtPowerInformation(SystemPowerInformation, ...) (that does not work on Windows 11).
I have ideas how to workaround it, but the priority of this task is low since I don't use Windows 11 yet, and Microsoft could eventually provide the required API.

You can use windows task scheduler to create an event based trigger for soundkeeper which runs it at logon and kills/runs it it on workstation lock/unlock optionally. There are a ton of other types of events that are available in the task scheduler for a new task that may be suitable to improve this use-case.
This is also a method i would recommend for running this in the first place instead of adding it to the start-up. This allows also the program to optionally die on workstation lock in case there are long term memory issues. I have this triggered to run at logon, but i personally don't need the lock/unlock events because this is a desktop that never sleeps :)
@vrubleg  You could consider creating some pre-baked taskmanager tasks that users can import through their task scheduler as part of your package to help set them up and configure them, and updating the readme accordingly :)

authors: Sipu filthyfreak vrubleg

repo: vrubleg/soundkeeper


text:
[Task] Handle failed updates

[x] I'm sure this issue is not a duplicate.

It so happens that in some cases when the extension gets updated and the user does not restart (not reload) the editor, loading the extension again results to misbehavior.
We should add a handler for such cases that will clean up the mess and if needed prompt the user to restart the editor.

@vscode-icons/development I was thinking of creating an integrity check of the icons folder content using Nodejs crypto. Any other suggestions?

Here is an example how vscode is using the same idea.

Hopefully we will not use md5. :/

Why not? We don't need any special cryptography. I believe using sha is overkill.

I'm afraid of hash collisions :/

@robertohuertasm Are you OK with this concept?

Yes, no problem.

Good, cause I have done half the coding.

This is going to be covered by nsri in v9. The default hash algorithm is sha-1 for files and sha-512 for directories.

authors: JimiC jens1o robertohuertasm

repo: vscode-icons/vscode-icons


text:
feat(icon): add Uiua icon

Fixes #3357
Changes proposed:

[x] Add

I noticed the icon is currently 22kB big, I'll optimize the paths to make it as small as possible

Alright, I got it down to pretty much exactly 2kB. This is ready to be merged now!


text:
Show that a line has a codetour associated outside of "tour mode"

I think it might be helpful to be able to see that a file you're currently viewing has a code tour step associated with it even though you're not currently viewing a tour.
So in tour mode:

Not in tour mode

It can serve as a hint that this thing might be important and by clicking it you can start the tour at that step and learn why. Might also be helpful as a reminder that if you edit this file you might need to update some line number for the hint itself 😅

Hey! I was tracking this already via #17, but I like the detail/screenshots you provided better 😄 So I'll close that issue and we can use this one to track progress 👍

I just shipped an extension update with support for "tour markers". The UX might benefit from some tweaking, so I'd love to hear any feedback 👍

authors: lostintangent stefanforsberg

repo: vsls-contrib/codetour


text:
Added SnapLayout

Add SnapLayout to README
Project URL

github.com/sp71/SnapLayout
Description

Update README
Why it should be included to awesome-ios (optional)
Reduces programmatic layout code
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@sp71, can you rebase this PR?

@miguelarauj1o updated

repo: vsouza/awesome-ios


text:
add SelectionList

Project URL
https://github.com/yonat/SelectionList
Category
Table View / Collection View
Description
Simple single-selection or multiple-selection checklist, based on UITableView.
Why it should be included to awesome-ios (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

1641
301
https://github.com/necolt/Swifton redirects tohttps://github.com/sauliusgrigaitis/Swifton

  Generated by :no_entry_sign: Danger

authors: danger-awesome-ios yonat


text:
add Coinpaprika API client

Project URL
https://github.com/coinpaprika/coinpaprika-api-swift-client
Category
Blockchain
Description
Coinpaprika API client with free & frequently updated market data from the world of crypto: coin prices, volumes, market caps, ATHs, return rates and more.
Why it should be included to awesome-ios

API is free & unlimited (not paid like in other services)
API provides data about whole cryptocurrencies world using data downloaded directly from several exchange markets
library is simple & open source

Checklist

[x] Only one project/change is in this pull request
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

1212
301
https://github.com/prynt/PryntTrimmerView redirects tohttps://github.com/HHK1/PryntTrimmerView

1571
301
https://github.com/facebook/facebook-ios-sdk redirects tohttps://github.com/facebook/facebook-objc-sdk

  Generated by :no_entry_sign: Danger

@dstranz : Keep one project/change in this pull request as per checklist.
Also resolve conflicts.

@arasu01 Sorry, I want to fix previous Danger warnings about redirects. Now it only one change without conflicts.

@dstranz Thanks for contributing

authors: arasu01 danger-awesome-ios dstranz vsouza


text:
does not contain bitcode. You must rebuild it with bitcode enabled

I added the library with success, but when trying to archive the app for distribution, I am getting this error:
 :-1: '/Users/alouanemed/Library/Developer/Xcode/DerivedData/app-hcgydxapjqidfmaldslmgpvdjrff/Build/Intermediates.noindex/ArchiveIntermediates/App Beta/BuildProductsPath/Release-iphoneos/AcknowList/AcknowList.framework/AcknowList' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. file '/Users/alouanemed/Library/Developer/Xcode/DerivedData/app-hcgydxapjqidfmaldslmgpvdjrff/Build/Intermediates.noindex/ArchiveIntermediates/App Beta/BuildProductsPath/Release-iphoneos/AcknowList/AcknowList.framework/AcknowList' for architecture arm64

I know this issue has been open for a while, but I’m not sure what to do with it. This doesn’t look like an error caused by AcknowList itself.
@alouanemed Are you still stuck with this error message?

I agree with you, I disabled this pluding that stores locally bitcode of all pods and it all went all.
Thank you!

Alright then. Thank you for the clarification 👍

authors: alouanemed vtourraine

repo: vtourraine/AcknowList


text:
label-has-for doesn't report errors if there is no control wrapped inside

I'm using the accessibility plugin, especially the rule label-has-for. My configuration looks like the following:
    'vuejs-accessibility/label-has-for': [
      'error',
      { required: { some: ['nesting', 'id'] } },
    ],

The problem is that the rule doesn't fire when I use it like that:

It only fires when there is no elements in it:

II think the nesting validation rule is broken. I took a look at the implementation and I think this line is incomplete. It should check if there is a form control inside the children 🙂

Thanks @thomlom! The linked PR will close this and then I'll release a new version.

authors: kddeisz thomlom