As a package publisher I would like to be notified by email when a published packaged is indexed

When I work on a package, I often want to publish it and immediately consume in another project. There is an email notification when the package is published, but no notification when it is indexed.

I spoke to someone at the MVP Summit who had the same request. Our existing publish notification which happens after validation. This point in time is pretty inconsequential since your users can't do anything with it. If we could move the notification until it has been indexed in all of the search service, that would be more ideal.


Issue with Topic Creation Using ReplicaAssignments in xk6-kafka

Hi!
Environment:

Kafka 3.7.0 running in Kubernetes
Docker image: mostafamoradian/xk6-kafka:0.28.0

Description:
I'm encountering an issue when trying to create a topic with replicaAssignments. Below is the code snippet used:
connection.createTopic({
  topic: "my-topic",
  numPartitions: -1, // Also tried declaring only `topic` and `replicaAssignments`
  replicationFactor: -1, //
  replicaAssignments: [{partition: 0, replicas: [0,1,2]}]
});

The error message I receive is:
time="2024-11-22T11:23:47Z" level=error msg="Failed to create topic., OriginalError: [42] Invalid Request: this most likely occurs because of a request being malformed by the client library or the message was sent to an incompatible broker, se the broker logs for more details" error="Failed to create topic., OriginalError: [42] Invalid Request: this most likely occurs because of a request being malformed by the client library or the message was sent to an incompatible broker, se the broker logs for more details"

Observations:
Upon checking the code, I noticed that in this section of the source code, default values for NumPartitions and ReplicationFactor are set to 1 if they are <= 0.
        if topicConfig.NumPartitions <= 0 {
		topicConfig.NumPartitions = 1
	}

	if topicConfig.ReplicationFactor <= 0 {
		topicConfig.ReplicationFactor = 1
	}

This behavior seems incorrect when using replicaAssignments since NumPartitions and ReplicationFactor should be inferred from the replicaAssignments field according to the Kafka protocol.
References:

Kafka Go tests: Example test with replicaAssignments
Kafka protocol documentation: Topic creation protocol

Suggested Fix:
The library should allow NumPartitions and ReplicationFactor to remain unset or explicitly -1 when replicaAssignments is provided. This would align the behavior with Kafka’s protocol and similar libraries.

Hi @mostafa,
Thank you for your work on the xk6-kafka project—it’s been incredibly useful for our Kafka-related testing needs.
I’ve encountered an issue when trying to create a topic with replicaAssignments and have provided a detailed report [above/in this issue]. It seems like the library sets default values for NumPartitions and ReplicationFactor even when replicaAssignments is provided, which contradicts Kafka’s protocol.
Would you be able to take a look when you have time? I’ve included links to relevant Kafka documentation and test cases from kafka-go library to help clarify the context.
Let me know if there’s any additional information I can provide or steps I can take to assist. Thanks again for maintaining this project!
Best regards,
Dmitriy

Hey @vereshchagin-d,
Looks like a bug. Would you please create a PR to fix this?

Hey @mostafa,
I'm currently swamped with work and won't be able to address this issue in the next few weeks. I'll circle back to it as soon as I have some bandwidth.
Thanks for understanding!


Add integration test harness using Ferrum

WIP

@joelhawksley Does storybook and yarn build still work without webpack in demo/?

@joelhawksley Does storybook and yarn build still work without webpack in demo/?

Just checked locally, and both still work 👍🏻


get resource from camera

hi. I want to use the code with open my  pc camera, but i do not know how could i get the video resources from camera?

Hello, @ZHENSU .
Input images of the demo code are provided from WebCamInput.cs.
This code use the video resources from the webCamName variable name camera if the staticInput Texture variable is null.
Thanks.


chore(deps): update dependency vue-tsc to v1

This PR contains the following updates:

Package
Type
Update
Change

vue-tsc
devDependencies
major
^0.40.7 -> ^1.0.0

Release Notes

vuejs/language-tools
v1.6.5
Compare Source

chore: bump vue deps to 3.3 stable (#3167) - thanks @ferferga
fix(vue-tsc): avoid throw when composite is enabled (#2622)
perf(language-service): avoid request name casing from language client multiple times (#3158) - thanks @kalvenschraut
fix: avoid slot name report TS8013 in js component (#3121)

Full-time Support by

WebContainer API is here.

Our Sponsors ⭐✨

		Add you via
		GitHub Sponsors
		or
		Open Collective

v1.6.4
Compare Source

feat: support color pickers for inline css
feat: support lang="vue" (#3105) - thanks @HunYan-io
fix: when the source type of v-for is any, the item type should be any (#3108) (#3112)
fix: avoid slots report error when noPropertyAccessFromIndexSignature enabled (#3106)
fix(component-type-helpers): import module causes tsc error (#3114)
fix: empty slot name auto-complete not working
fix: accessing an unknown slot name does not report an error
fix: format adds spaces to v-for if nested template element assigns type to slot props (#2750) (#2757)
fix: parentheses auto insert not working in template

Breaking changes

drop support for Vue 3.3 slots short definition (#3116)

v1.6.3
Compare Source

feat: expose custom blocks attrs (#3099) - thanks @HunYan-io
fix: event "@update:" syntax causes TS error (#3100)
fix: generic attr unexpectedly trimmed when formatting if attr value includes "<" (#3101)
fix: required event props always shows in missing props hint
fix: exclude null / undefined from v-for source type (#3102)

v1.6.2
Compare Source

fix: consume required props for events (#2468)
fix: support infer v-for types for generic (#2758)
fix: slot missing props don't report error
fix: cannot assign generic component to components option of defineComponent
fix: "TS1002: Unterminated string literal" in slots edge case (#2710)
fix: generic component prop with default type incorrect (#2754)

v1.6.1
Compare Source

feat: support for specify vue library name by vueCompilerOptions.lib option (#2722)
fix: avoid <component :is> type checking with string literal assignment (#2725)
fix: <slot> reporting false positive error when strictTemplates enabled (#2726) (#2723)
fix: error using custom directive: Expected 2 arguments, but got 1. (#2730)
fix: namespaced tag not working without script setup
fix: component intellisense not working in template if TS version < 5.0 (#2742)
fix: class is not assignable to generic components (#2744)
fix: components options is not set correctly when component name is kebab-case and auto-importing (#2745)

v1.6.0
Compare Source

feat(doctor): show warning for TS 4.9 (#2190)
feat: support inlayHints for vueCompilerOptions.optionsWrapper
fix: avoid props type-checking for VNode (#2720)
fix: revert "fix: trim modifiers for slot name"
refactor: update extension settings from volar.* to vue.*
refactor(language-server): remove petiteVue, vitePress from server init options

for IDEs other than VSCode, use additionalExtensions: ['html', 'md'] instead of

Breaking changes

deprecated vueCompilerOptions.jsxTemplates (#2677)
deprecated vueCompilerOptions.nativeTags (#2685)

v1.5.4
Compare Source

fix: defineExpose macro missing for Vue 3.3
fix(component-meta): meta info is empty if missing vue-component-type-helpers dependency
fix: don't check time for codeActions when saving multiple files

v1.5.3
Compare Source

feat: support type-checking for dynamic components
feat: support element type-checking for directives
fix: cannot infer event type for <Transition> (#2700)
fix: tag / prop casing status not working
fix: slot name accidentally included modifiers in virtual code
fix: avoid always pop "Saving time is too long" edge case
fix: only generate JSX.ElementChildrenAttribute type when vueCompilerOptions.jsxSlots enabled (#2714)
fix: top level await error in SFC if two script blocks are present (#2712)
fix: cannot use generic components inside defineComponent (#2709)
fix: intellisense not working in es module project (#2661)

v1.5.2
Compare Source

fix: cannot recognize hyphenate tag name (#2688)

v1.5.1
Compare Source

refactor: deprecate nativeTags option (#2685)
fix: props type-check not working for one argument functional component (#2686)
fix: <Suspense> default slot reporting error (#2683)
fix: cannot infer slots type in vue2 project (#2682)
fix: static directive arg should not recognize as expression (#2678)

v1.5.0
Compare Source

refactor: deprecate jsxTemplates option (#2677)

v1.4.4
Compare Source

fix: missing FunctionalComponent props are no longer reported in the template (#2676)

v1.4.3
Compare Source

feat: add volar.nameCasing.status setting to disable nameCasing status (#2453)
fix(vue-typescript): add missing peer dependency typescript (#2665) - thanks @merceyz
fix: slots references codeLens, renaming not working
fix: pug multiline attribute values are marked as error (#2413)
fix: incorrect extra inlay hints inside template when enabled typescript.inlayHints.parameterNames (#2670)
fix: failed to resolve tsdk path for "JavaScript and TypeScript Nightly" (#2663)
revert: "fix(vue-tsc): add throw message if composite / incremental enabled" (https://github.com/vuejs/language-tools/commit/b596a60154a0f2a6345244a90868b5cc67eb9ff8)

v1.4.2
Compare Source

fix: cannot disable auto insert .value feature
fix: avoid slot props reporting error if component does not have $slots type (#2646)
fix: prefer component constructor signature instead of call signature (#2647)
fix: avoid tsconfig reporting "Comments are not permitted" when takeover mode enabled (#2648)

v1.4.1
Compare Source

fix: generic slot props type not incorrect (#2639)
fix: third-party library components cannot accept unknown props (#2636)
fix: allow props less functional component (#2638)
fix: native tags event type become never (#2640)
fix: cannot resolve tsdk on windows (#2637)

v1.4.0
Compare Source

feat: support intellisense for directive arg expression (#2588)
feat: asking disable codeActions if saving time is too long
feat: file definition cross file mapping result fall back to 0:0
fix: fixed dynamic slot arg expression virtual code (#2586) (#2617) (#2592)
fix: add hack support for v-if + v-slot template (#625)
fix: goto definition not working for alias path without script setup (#2600)
fix: avoid missing prop hint for native tags (#2616)
fix: vue-language-plugin-pug broken with yarn (#2608)
fix: native tags reporting missing prop error (#2629)
fix(vue-tsc): add throw message if composite / incremental enabled (#2622)
fix: slot props are not recognized at the root component (#2554)
fix: missing props hint incorrect for model property for vue 2 (#2635)
fix: cannot show css hover message (#2634)
fix: duplicate ts unused reports if noUnusedLocals is enabled (#2627)

v1.3.19
Compare Source

feat: change vue.features.codeActions.enable default value to true
feat: auto disable vue.features.codeActions.enable when document saving time is too long
feat: changing vue.features.* settings no longer requires reload vscode

v1.3.18
Compare Source
Extension settings refactoring

codeActions disabled by default
updateImportsOnFileMove disable by default
missing props hint, event argument hint disabled by default

For more details, see #2620.
v1.3.17
Compare Source

feat: support document links for tsconfig when takeover mode is actived (#2467)
fix: avoid server crash when tsconfig extends path invalid
fix: auto import should not appending .js (#1763) (#2518)
fix: inhibit unknown props error when if strictTemplates is disabled
fix: absolute SCSS import resolving inconsistency (#2517)
fix: <template> multi-line comments shift with each format (#2505)

v1.3.16
Compare Source

feat(component-meta): expose definition location information as declarations property
perf: fixed TS auto import performance regression since v1.13.11 (https://github.com/volarjs/typescript-auto-import-cache/pull/2)
fix(language-server): show component meta command not working
fix: v-for item adds spaces if enabled insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets (#2571)
fix: when the takeover mode is enabled, json documents shows duplicate outline (#2573)

v1.3.15
Compare Source
v1.3.14
Compare Source

feat: add vue-component-type-helpers package (#2590)
feat(component-meta): integrated vue-component-type-helpers
feat: upgrade to lerna-lite 2.0 (#2597) - thanks @ghiscoding
feat: support prop renaming for defineModel and defineProp
fix: template-based slots type incorrect (#2590)
fix(vue-tsc): patch build info roots for TS 5.0 (#2580) - thanks @blake-newman

v1.3.13
Compare Source
v1.3.12
Compare Source

feat: Support for Vue 3.3 experimental defineModel() API (#2579)
feat: Support for vue-macros defineProp() API (#2579)
feat: support short define for defineSlots()
feat: new <script setup> codegen implement for DX improve (#2582) (#2421)
fix: falsely reports "Virtual script not found"
fix(vue-tsc): emit declaration throws TS4060 (#2581) - thanks @blake-newman

v1.3.11
Compare Source

feat: support goto source file definition for project references for TS 5.0 (https://github.com/volarjs/volar.js/pull/24) (#1344) (#2296) (#2340) (#1815) - thanks @blake-newman
feat: support auto imports for unused modules for TS 5.0 (https://github.com/volarjs/volar.js/pull/24) (https://github.com/volarjs/volar.js/issues/19) (#963) - thanks @blake-newman

v1.3.10
Compare Source

feat: support for vue 3.3 defineSlots() API (#2568)
feat(vue-tsc): prettify script setup props, emits type in emit
fix: plugins, hooks, experimentalAdditionalLanguageModules options of vueCompilerOptions not working (#2558) - thanks @rchl
fix(vue-tsc): fixed typescript 5 support (#2555) - thanks @blake-newman
fix: incorrectly incremented end offset when deleting the last text in an directive expression
fix: "typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyParenthesis": true caused formatting issues with v-bind expressions (#2507)
fix: normalizeComponentAutoImportName not working for import statement completion (#2511)
fix: ignore null type for dynamic argument (#2514)
fix: vue-twoslash-queries plugin not working
fix: redo JSX.ElementChildrenAttribute implement (#2472)
fix(component-meta): support for functional component (#1992)
fix: avoid crash when chdir() (#2480)
fix: expand selection ranges incorrect (#2477)
fix: directive semanticTokens display range incorrect (#2454)
fix: <textarea> formatting indent incorrect
perf(vue-tsc): streamline virtual code to improve emit performance

v1.3.9
Compare Source
v1.3.8
Compare Source

fix: missing props type check stop working

v1.3.7
Compare Source

feat: support normalizeComponentImportName for additionalExtensions (#2481)
feat: support generic component without jsxTemplates
feat: support slot references for anonymous default slot (#2547)
feat: recognize slots property with JSX.ElementChildrenAttribute (#2472)
feat: support slot required checking when enabled strictTemplates (#1820)
fix: handle edge tag name casing <xxx--yyy> (#2463)
fix: incremental update causes multi-line style node damage (#2519)
fix: formatting break multi-line attribute value indent (#2519)
fix: formatting break <pre> tag contents indent (#2520)
fix: typescript labelDetails in completions not processed (https://github.com/volarjs/plugins/issues/31) - thanks @zardoy

Breaking changes

deprecated volar.vueserver.textDocumentSync setting
deprecated narrowingTypesInInlineHandlers for vueCompilerOptions and always enabled now

v1.3.6
Compare Source

feat: RFC 436 leaves experimental (#2545)
feat: auto resolve vueCompilerOptions.target by default
feat: auto append /** @jsxImportSource vue */ when jsxTemplates enabled and target >= 3.3 for avoid #592
feat(doctor): remove target check for vueCompilerOptions

v1.3.5
Compare Source
v1.3.4
Compare Source

fix: some environments throws Failed to resolve tsconfig path (https://github.com/vuejs/language-tools/pull/2471#issuecomment-1475350770)
fix: diagnostics break when changing code (https://github.com/yaegassy/coc-volar/pull/262#issuecomment-1475468100)
fix: all server capabilities loss in IDEs other than VSCode (#2526)

v1.3.3
Compare Source

feat: disable missingRequiredProps, eventArgumentInInlineHandlers by default
fix: vueCompilerOptions cannot extends from non-relative paths (#2345) - thanks @dschmidt
fix(vue-component-meta): exposed missing when use TS 5.0
perf(vue-component-meta): props, events, slots, exposed lazy calculation
perf: provide change range of virtual file snapshot for typescript program

v1.3.2
Compare Source

feat(language-server): declare workspaceFolders support in server capabilities for IDEs (https://github.com/volarjs/volar.js/pull/18) - thanks @the-mikedavis
feat(vue-tsc): supports incremental emit (https://github.com/volarjs/volar.js/pull/17) - thanks @blake-newman
feat: allow code actions to run rename command after applying (#2498) (https://github.com/volarjs/plugins/pull/29) - thanks @zardoy
perf(vue-component-meta): faster initialization (#2506) - thanks @stafyniaksacha
perf: search tsconfig on demand (https://github.com/volarjs/volar.js/pull/16)

v1.3.1
Compare Source

feat: change vue.features.codeActions.enable default value to true
feat: auto disable vue.features.codeActions.enable when document saving time is too long
feat: changing vue.features.* settings no longer requires reload vscode

v1.3.0
Compare Source

feat: support for korean html data
feat(doctor): remove vue-tsc version check
feat(doctor): rename setting from volar.doctor.statusBarItem to volar.doctor.status
feat(doctor): check VSCode settings emmet.includeLanguages, files.associations (#2487)
feat(doctor): check plugins version for volar.config.js
feat: add description link for $event => hint (#2445)
feat(language-server): support for ServerMode.PartialSemantic
fix: Show Component Meta command not working
fix: name casing status do not update with changed settings (#2460)
fix: component auto import not working with kebab case (#2458)
fix: missing props hints do not recognize @xxx (#4568)
fix: code action document version incorrect (https://github.com/yaegassy/coc-volar/issues/254)

Breaking changes

Remove built-in web intellisense support and recommended TypeScript IntelliSense for Web instead of (#2475)
Upgrade required version of @volar-plugins/* to >= 2.0.0

After upgrade, you need to access default property with require('@volar-plugins/xxx').default in volar.config.js

Upgrade build target from ES2016 to ES2021 (#2489)

v1.2.1
Compare Source
v1.2.0
Compare Source

feat: compatible with upstream monaco integration (https://github.com/volarjs/volar.js/pull/10)
feat: support array extends for tsconfig (#2344)
feat: make cursor inside quotes when insert missing required props edit (#2414)
feat: support mixin child nodes for pug (#2447)
fix: ignore native tags for missing required props hint
fix: ignore methods for missing required props hint (#2443)
fix: SFC outline not show child nodes (#2446)

v1.1.7
Compare Source

fix: document symbols request crash with arrow function declaration (#2438)
fix: document symbols child node range incorrect
fix: SFC document symbols tree incorrect

v1.1.6
Compare Source

fix: template comments were trimmed with formatting in production mode (#2435)
fix: inaccurate outline view of script content
fix: takeover mode causes IDE to get stuck in large .ts files due to a long list in the outline view

v1.1.5
Compare Source

feat: prettify type for css module $style
fix: only generate component with function type when use generic attribute
fix: document links feature broken (#2426)
fix: missing props inlay hints not working for namespace components
fix: component tags type-check not working
fix: pug template reporting TS2339 when strictTemplates enabled (#2431)
fix: pug tag completion not working at empty lines

v1.1.4
Compare Source

feat: support for script src path intellisense (#2331)
feat: support name casing setting for component auto import (#2362)
feat: add volar.vueserver.fullCompletionList setting (#2422)
perf: filter completion items in language server for better performance (#2306)
fix: strictTemplates did not check for unknown components (#2291)
fix: duplicate document links in the template
fix: completion not working for namespace components (#2382)
fix: html comments and js template strings format indent incorrect (#2420)
fix: do not correspond v-model to checked prop for checkbox and radio input tags (#2415)

v1.1.3
Compare Source

feat: visualize event argument in inline handlers
feat: add description for model modifiers (#2405)
fix: remove deprecated preview commands (#2402)
fix: missing required props hint not working with v-model (#2407)
fix: cannot collapse code in .js / .ts files with takeover mode (#2408)
fix: symbols view stopped working for .js / .ts files with takeover mode (#2404)
fix: cannot rename html tags (#2410)
fix: cannot display rename fail message
fix: format on type cannot working for code blocks that enabled volar.format.initialIndent (#2401)
fix: vue-tsc crashes in watch mode when file changed (#2403)
fix: prop type definition inaccurate for v-model directive on native input (#2399)

v1.1.2
Compare Source

fix: format adding unnecessary newline to CRLF document (#2385)
fix: incidentally inserting indents when inserting new lines when if editor.formatOnType (#2394)
fix: template formatting last line indent incorrect (#2393)
fix: template start tag got deleting if first line is comment (#2390)
fix: takeover mode status incorrect in display (#2389)
fix: diff window's document was unexpectedly diagnosed (#2391)
fix: emmet completions appear inside open tag (#1329)
fix: opencc is depended on by language server (#2388)

v1.1.0
Compare Source

feat: support initialIndent for pug and sass
feat: add description for built-in directives, attributes, component, and elements
feat: support localization for event modifiers and props modifiers
feat: missing required props inlay hints (needs enabled volar.inlayHints.missingRequiredProps)
feat: show (takeover) instead of (vue) in status bar for takeover mode (#2365)
feat: more reliable formatting edits combine
fix(doctor): update source code link (#2307)
fix(typescript-plugin): tsserver multiple initializations lead to infinite loop (https://github.com/microsoft/vscode/issues/171591)
fix: syntactic features not working for untitled vue document
fix: spaces removed from ternary operator inside {{ }} (#2305)
fix: source.addMissingImports accidentally made imports for properties used the template (#2304)
fix: code action auto import should not append to the same line with the script tag (#916)
fix: multi-line interpolation last line indent incorrect
fix: declaring empty emits like defineEmits<{}>() would fail the type-checking process (#2370)
fix: ignore name prop / attr for slot (#2308)

Breaking changes

Removed pug convert tool
Removed script setup convert tool
Unsupported tracing for vue-tsc (#2378)
Extract Vite, Nuxt and component preview features to Vue and Nuxt Preview

feat: support vite-plugin-vue-component-preview for nuxt 3.2
feat: add vue-preview.root setting for Nuxt component preview
fix: prevent random creation of multiple preview terminals
fix: support nuxt preview without vite serving allow list (#2287)

v1.0.24
Compare Source

feat: add vueCompilerOptions.macros setting for vue-macros plugins
feat(framework): expose FileCapabilities.full, FileRangeCapabilities.full, MirrorBehaviorCapabilities.full
feat: renamed normalizeComponentAutoImportName setting to normalizeComponentImportName
feat: support normalize component name for import statement completion (#2286)
feat: normalize Index to folder name when normalizeComponentImportName enabled (https://github.com/vuejs/language-tools/issues/2071#issuecomment-1373701277)
feat: support update imports on multiple files move
fix(typescript-plugin): fixed Projects must list all files or use an 'include' pattern error (#2271)
fix: language client sending parseSfc requests when not a vue document changed
fix: typescript actions not working for codeActionsOnSave setting (#2188)
fix: fixed c is not iterable error edge case (#2282)
fix: cannot select workspace tsdk on status bar with takeover mode
fix(plugin-api): cannot catch errors for getEmbeddedFileNames(), resolveEmbeddedFile()
fix(component-meta): cannot detection of slots in script-less SFC (#2113)
perf(component-meta): resolve schema on demand (#2288)

v1.0.22
Compare Source

fix: document folding ranges not working in .ts

v1.0.21
Compare Source

fix: cannot jump to .vue definition from .ts with takeover mode
fix: cannot detect @volar/vue-language-plugin-pug installed (#2272)
fix: ignore incremental update for v-for expression (#2266)
fix: auto insert spaces for {{}} not working
fix: completion in template inserts stray leading dot (#2155)
fix: if source document EOL is \r\n, virtual document mapping decorations range incorrect

v1.0.20
Compare Source

feat: support browser navigation for embedded preview
feat: released pug extension (#2274)
feat: add volar.takeOverMode.extension setting for choice extension that takeover *.ts language support
fix(typescript-vue-plugin): can't always get latest status of .vue files (#2271)
fix: multi-line template interpolation formatting indentation incorrect
refactor(framework): simplify LanguageServerPlugin api and dependency injection connection (#2273)
refactor(framework): combine createLanguageService and createDocumentService

v1.0.19
Compare Source

feat: add experimentalAdditionalLanguageModules option for vueCompilerOptions (#2267)
fix: TS typescript/javascript.preferences.autoImportFileExcludePatterns setting not working
fix: formatting not working for extra vue file extensions (#2263)
fix(doctor): accidentally report @vue/compiler-dom warning (#2262)
fix(vue-component-meta): required property incorrect (#2256)
fix(preview): cannot start preview if project never start run vite server (#2223)
fix: references codeLens not working

v1.0.18
Compare Source

feat: check deprecated properties for vueCompilerOptions in tsconfig
fix: auto add spaces for {{}} not working if template block not at the top
fix: remove duplicate file watchers for .vue files
fix: auto complete randomly report [TS Error] { } and failed (#2190)
fix: cross-file renaming cannot be performed consecutively
fix: should not report unknown tag error without strictTemplates enabled (#2255)

v1.0.17
Compare Source

feat: support syntax highlighting for lang="json5" (#2244)
feat: support for generating virtual file from multiple sources (#2253)
feat: display mapping data on hover for virtual document
feat: re-support component semantic token (#2252)
fix(vue-tsc): cannot resolve hook path from extends options
fix: fixed workspace configs caching not working edge case (#2062)
fix: cannot find volar.config.js for sub folder tsconfig project
fix: emmet abbreviation suggestion keeps disappearing every third letter (#2240)
fix: {{ }} colorizedBracketPairs not working (#1759)
fix: fixed volar-base language servers executePluginCommand duplicate registration error
fix: avoid throw on un-exist workspace folder (#2039)
fix: ignore class, style attrs when v-bind exist (#2166)
fix: functional component type check not working when return type includes props property (#2206)
fix: v-slot error when noPropertyAccessFromIndexSignature is enabled (#2236)
fix: skipTemplateCodegen should ignore template slots emit (#2237)
fix: recursive closing of html tag edge cases (#2238) (#2247)
fix: double quotes not allowed in attribute value (#2250)
perf: embedded files on demand calculation not working

v1.0.16
Compare Source

feat(component-meta): make schema.ignore accept functions (#2232)
feat: add volar.icon.splitEditors setting (#2163)
feat: support twoslash queries in .ts when using takeover mode
fix: fixed typescript-vue-plugin performance regression (#2228)
fix: deleting space for {{ |}} become {{ | }} (#2222)
fix: dynamic slot name type <slot :name="(name as 'a' | 'b')" /> not working (#2233)
fix: typed template slots missing when template only exist dynamic slots (#2233)
fix: fixed template Type 'void' has no call signatures errors (#2225)
fix(vue-tsc): shim vue-tsc/out/proxy.js for vite-plugin-checker (https://github.com/fi3ework/vite-plugin-checker/issues/193)
perf: rewrite typescript-vue-plugin for much better performance and fixed path resolve edge case (#2137)

v1.0.14
Compare Source

feat: add angular language server example (#2215)
feat(vue-tsc): support for hook api (#2217)
feat: add vue-tsc-eslint-hook module to support use eslint in vue-tsc (#2220)
feat: add setting volar.vueserver.maxFileSize (#2186)
feat: add setting volar.doctor.checkVueTsc and disable by default (#2186)
feat: add setting volar.vueserver.configFilePath (#2078)
feat: auto add space between double curly brackets (#2088)
feat: support formatting for style v-bind (#2105)
fix: virtual code mapping ignored offset 0 (#2052)
fix: auto complete ref value with '.value' not working (#2203)
fix: template AST broken by slot name incremental update (#2207)
fix: preview not working for Vite v4 (#2198)

v1.0.13
Compare Source

feat(web-ide): show loading file at status bar
feat(web-ide): support node_modules types via CDN
feat(web-ide): support locale typescript diagnostic messages
fix(web-ide): cannot use default typescript lib types
fix(web-ide): cannot found match tsconfig
fix: volar.config.js plugins dirty cache between different tsconfig projects

v1.0.12
Compare Source

feat: added @volar/vscode-language-client package (#2181)
fix: document content messed up randomly (#1807)
fix: "Show Virtual Files" mapping background color unclear with light theme (#2147) (#2170)
fix: props type checking not working for Element Plus components (#2176) (#2180)
fix: attribute values being wrapped in parentheses while typing (#2182)
fix: formatting crashes (#2077)
fix: cannot emit component type with DefineComponent when template has slots (#2161)

v1.0.11
Compare Source

fix(vue-tsc): dts emit do not generated DefineComponent type (#2161)
fix: global components types loss in vue 2 projects (#2157)
fix: Vite / Nuxt app preview crash when template includes <html> tag

v1.0.10
Compare Source

feat: add volar.vueserver.json.customBlockSchemaUrls setting to support preset json schema urls for custom blocks (#2079)
feat: add volar.vueserver.reverseConfigFilePriority setting to support customize tsconfig priority (#1815)
feat: add volar.vueserver.disableFileWatcher setting for better performance (#2027)
feat(vue-tsc): support for TypeScript 5.0 (#2095)
feat: auto insert parentheses for instanceof expressions (#2099)
feat: more accurate HTML attributes auto-complete
feat: add nativeTags instead of experimentalRuntimeMode to vueCompilerOptions for uni-app supports (#2065)
feat: remove split editors icon and use command instead of
fix: goto definition not working with nvim-lspconfig (https://github.com/vuejs/language-tools/pull/1916#issuecomment-1293166322)
fix(preview): more accurate script judgment (#2135)
fix: local components types should cover global components types (#1886)
fix: auto insert parentheses for AsExpressions not working
fix: template code mapping confusion when undo with invalid template code (#2151)
fix: output Server Stats through LSP API (#2050)
fix: vite app preview not working if project path includes spaces (https://github.com/johnsoncodehk/vite-plugin-vue-component-preview/issues/7)
fix: avoid component preview create multiple terminals (#2128)
fix: avoid folding when join split editors (#1887)
fix: split editors command crash with empty document (#2072)
fix: avoid escape " (#2091)
fix: script setup first variable jsdoc missing (https://github.com/vuejs/language-tools/issues/1327#issuecomment-1304784005)
fix: document symbols of SFC blocks range incorrect (#2118)
fix: strictTemplates option works only bound props (#2136)
fix: props required warning missing when jsxTemplates option enabled (#2139)
fix: cannot infer events parameter type in recursive component (#2140)
perf: faste

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: frontend/package-lock.json
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated<EMAIL_ADDRESS>Versions '1.x' and '2.x' of '@aws-amplify/ui' have been deprecated. Please visit https://ui.docs.amplify.aws/ for the current version of Amplify UI.
npm WARN deprecated<EMAIL_ADDRESS>The Amazon Sumerian service is no longer accepting new customers. Existing customer scenes will not be available after February 21, 2023. The AWS Amplify XR features depend on the Amazon Sumerian service to function and as a result, will no longer be available.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm notice
npm notice New major version of npm available! 8.19.4 -> 9.6.7
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code 127
npm ERR! path /tmp/renovate/repos/github/bcgov/nr-forests-access-management/client-code-gen/gen
npm ERR! command failed
npm ERR! command sh -c -- npm run build
npm ERR! ><EMAIL_ADDRESS>build
npm ERR! > tsc && tsc -p tsconfig.esm.json
npm ERR! sh: 1: tsc: not found

npm ERR!


Adding Support / Integration LLMLingua ?

Thank you for this most excellent project !
I am surveying the state of the art for RAG and I just discovered LLMLingua which seems like an obviously good idea to me, to make the most of an LLM's context.
Do you think it would fit LLMware's scope to provide LLMLingua's context compression ?
Best Regards

We will take a look. Thank you for the suggestion!


ci: test latest release on master branch only

See discussion at https://github.com/mandiant/capa-rules/issues/556#issuecomment-1242375052

on merge into v5-dev:

See check on merge into branch v4 at https://github.com/mandiant/capa-rules/actions/runs/3084041841/jobs/4985707859.


rename porterlb to openelb

rename porterlb to openelb in the code

Please change the package name github.com/kubesphere/openelb to github.com/openelb/openelb

/lgtm
/approve

@all-contributors please add @renyunkang and @zheng1 for code and doc


Change Request for  Wrack Spell

I love the Wrack Spell, but I we need to make one minor change.
-> The spell should not be able to target undead or construct creatures.

fixed on dev.


Add a note

Despite we do NOT recommend using VHD Set files in production because of many limitations and issues exist, there is no public doc to explain it. I do not want to provide negative impression publicly, but to reduce call generators I file this pull request.

#sign-off

@NAO-MSFT  I will go ahead and approve/merge this PR. But in the future, as a Microsoft employee, please use the private repo, windowsserverdocs-pr (https://github.com/MicrosoftDocs/windowsserverdocs-pr). This repo is strictly for non-Microsoft employees. Thanks!!

@eross-msft, I see. Thank you!


Provision load test resource in test environment

Context
AB#225957 AB#222362
Cherry-picked from ca31bd514f0d84cdf69aaa04a450c2e18f72a41e
Change proposed in this pull request
Provision new resource that will in turn contain individual load tests. Only targeting test environment at this time.
Checklist (add/remove as appropriate)

[x] Work items have been linked (use AB#)
[ ] Your code builds clean without any errors or warnings
[ ] You have run all unit/integration tests and they pass
[x] Your branch has been rebased onto main
[ ] You have tested by running locally

Not required. Apologies, should have added to the ticket - pipeline and initial terraform/resources has already been done.
https://dfe-ssp.visualstudio.com/s198-DfE-Benchmarking-service/_build?definitionId=3123

Not required

I did check for the test resource in Portal but couldn't find it... because I was on the wrong subscription!


filter out control chars

this is a pretty cool project, having some issues though
the tail command on Mac OSX seems to filter out (interpret) control chars
Is there an option to do so with frontail?

the red line at the top is via control chars, so not sure why that got interpreted correctly - it was a part of the first 10 lines from the original tail command if that's of any help

also it doesn't appear that new line chars are being honored either, here is what iTerm2 looks like tailing the same file:

Weird, lines are converted using https://github.com/drudru/ansi_up. Looks like something wrong here.

I can probably prevent logging control chars upstream, but then I won't get any colors. Definitely would be great to have colors available in the browser. Let me know if you need more info.

any luck investigating this? I haven't thought about it much but will let you know if I can think of a good reason why it may happen

@ORESoftware haven't had enough time. I'm pretty busy these days :/

word np
On Jun 30, 2016 11:36 PM, "Maciej Winnicki"<EMAIL_ADDRESS>wrote:

@ORESoftware https://github.com/ORESoftware haven't had enough time.
I'm pretty busy these days :/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mthenw/frontail/issues/72#issuecomment-229866165, or mute
the thread
https://github.com/notifications/unsubscribe/AKn56Guzxp-mFb3q7GIxz6MBWiMlnBfCks5qRLVtgaJpZM4I1vK6
.

Fixed in v3.1.2 :)

cool will test it out thx!
On Sep 4, 2016 9:56 AM, "Maciej Winnicki"<EMAIL_ADDRESS>wrote:

Closed #72 https://github.com/mthenw/frontail/issues/72.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mthenw/frontail/issues/72#event-777686890, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AKn56KU8geJEvWsOsKvs99TfMy8047PSks5qmvgpgaJpZM4I1vK6
.


Issues with CSSModules

Issue details
I'm having difficulty getting CSSModules to work with storybook. I've created a webpack config for the .storybook directory to incorporate the modules:
const paths = require('../webpack/config').paths

module.exports = {
  entry: {
    vendor: ['bootstrap-loader/extractStyles']
  },
  module: {
    rules: [
      // Apply loader
      {
        test: /^((?!\.module).)*scss$/,
        use: [
          'style-loader',
          'css-loader',
          'sass-loader?sourceMap'
        ]
      },
      {
        test: /\.module.scss$/,
        use: [
          'style-loader?singleton',
          'css-loader?modules&importLoaders=1&localIdentName=[name]__[local]__[hash:base64:5]',
          'postcss-loader?sourceMap',
          'sass-loader?sourceMap',
          {
            loader: 'sass-resources-loader',
            options: {
              // Provide path to the file with resources
              resources: [`${paths.node}/bootstrap/scss/bootstrap.scss`, `${paths.source}/scss/**/*.scss`]
            }
          }
        ]
      }
    ]
  },
};

When I run the storybook, the outer shell renders, but the inner iFrame looks like this:

There's really no stack trace to speak of, so it's exceptionally difficult to debug.
Steps to reproduce
Here is the repo:
https://github.com/yazdog8/launchpad
If you don't want to use yarn...just use npm to install dependencies. From there all you need to do is run the storybook command npm run storybook or yarn storybook. This will start the server at http://localhost:9001/.
If you remove the css modules from some of the root modules, they will actually render (like the welcome.js). Otherwise you get the error mentioned above.
preview.bundle.js:45483 TypeError: Cannot assign to read only property 'children' of object '#<Object>'
    at linkElement (preview.bundle.js:45820)
    at preview.bundle.js:45823
    at mapSingleChildIntoContext (preview.bundle.js:17946)
    at traverseAllChildrenImpl (preview.bundle.js:17819)
    at traverseAllChildrenImpl (preview.bundle.js:17835)
    at traverseAllChildren (preview.bundle.js:17890)
    at mapIntoWithKeyPrefixInternal (preview.bundle.js:17966)
    at Object.mapChildren [as map] (preview.bundle.js:17988)
    at linkElement (preview.bundle.js:45820)
    at linkElement (preview.bundle.js:45818)

Please specify which version of Storybook and optionally any affected addons that you're running

"storybook/addon-actions" 3.3.15
"storybook/addon-backgrounds" 3.3.15
"storybook/addon-info" 3.3.15
"storybook/addon-knobs" 3.3.15
"storybook/addon-links" 3.3.15
"storybook/addon-notes" 3.3.15
"storybook/addon-options" 3.3.15
"storybook/addons" 3.3.15
"storybook/react" 3.3.15

I am running webpack 4.1.1 as my webpack server for the regular build. Not sure if this is causing the issue.

I am running webpack 4.1.1 as my webpack server for the regular build. Not sure if this is causing the issue.

This is most likely the case. Webpack 4 support is being added in #3148

Thanks for the response! I see that you might be ready for an Alpha release soon. I'll wait for that, upgrade and see if that might fix the problem.

It turns out the problem is not related to webpack or even to storybook. If I change Admin component from src to this, yarn start breaks as well:
class Admin extends Component {
  render () {
    return (

Admin Section

    )
  }
}

Looks like react-css-modules package doesn't work well with React 16. See e.g. https://github.com/gajus/react-css-modules/issues/200
I would advice to use a bit more verbose but a lot less magical syntax for CSS modules:
import React from 'react'

import styles from './welcome.module.scss'

const Welcome = () => {
  return (

Welcome to the Company Storybook

This is a UI component development environment for interdisciplinary team collaboration of core and shared components in the Company web application.

This page was built using React Storybook

  )
}

export default Welcome


[ISSUE #7453] Fix the problem in constructing the GetMessageResult

Which Issue(s) This PR Fixes

Fixes #7453
Brief Description

How Did You Test This Change?

 两个构造函数看起来并没有本质上区别，这个修改是否能带来性能优化？

我改成每次取的最大消息条数了，之前是4k，请求多的时候每次都会初始化4k的3个list，非常耗费性能

Codecov Report

Merging #7456 (ceeb960) into develop (7e4879a) will decrease coverage by 0.01%.
The diff coverage is 50.00%.

@@              Coverage Diff              @@
##             develop    #7456      +/-   ##
=============================================
- Coverage      42.69%   42.69%   -0.01%
- Complexity      9481     9487       +6
=============================================
  Files           1150     1150
  Lines          82825    82823       -2
  Branches       10771    10771
=============================================
- Hits           35361    35358       -3
  Misses         43044    43044
- Partials        4420     4421       +1

Files
Coverage Δ

...rocketmq/broker/processor/PopMessageProcessor.java
45.10% <100.00%> (+0.49%)
:arrow_up:

...ocketmq/broker/processor/PeekMessageProcessor.java
3.24% <0.00%> (+0.02%)
:arrow_up:

... and 20 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


add custom resolve option for node/nodes

A draft for #664 the only thing i do not know is how to implement type inference.
For now i copied one of the tests & examples but i could provide other tests if needed.
Also i added a small bit to the plugins docs but haven't mentioned that a custom resolve for node/nodes isn't something most people would want.

awesome, this looks like a great start!  Thanks for working on this.
I think it's actually pretty close.

the only thing i do not know is how to implement type inference.

Can you elaborate on what you mean by this?  I am guessing you mean that type-checking the custom resolver?  Unfortunately I don't think this is possible in a way that is actually useful.

For now i copied one of the tests & examples but i could provide other tests if needed.

I don't think we need a lot more tests, but simplifying the tests so that there aren't so many unused types/options/fields might be good.  Right now the example used for the test has tons of things that make it hard to figure out what is relevant to that specific test
I think one thing that may be missing (or helpful) is a way to fallback to the default resolver.  I think what you really want is a way to handle just specific ids, and then use the default loaders you already defined for most of the resolvers right?  I am not sure what that API would look like, and it might be something to add later, but I imagine it could be quite useful.

the return type of resolve is now unknown and removed a lot of options on the test. Getting the tests to pass however isn't something i yet succeeded in. i've modified the arg to be of the type globalID & globalIDList instead of id and idList but it throws an error here because it cannot resolve the ref because its undefined any idea what could cause this?

@JipSterk you can merge this: https://github.com/JipSterk/pothos/pull/1 to fix the issues with tests not running, just did a small refactor for how resolveNodes works to avoid extra re-encoding of global ids


Create mod train door causes a lot of lag

Describe the Bug
Hey! I build trains that have a lot of doors (about 25 with a full model train). When the train starts/stops it causes a lot of lag.
Reproduction Steps
Build a train, that has a minimum of 20 or 30 doors
Expected Result
A way to turn off train door animation or turning off automatic closing/opening
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 11
Mod Version
0.5.0g
Minecraft Version
1.19.2
Other Mods
No response
Additional Context
No response

duplicate of #847


Distinct Instances of Date Range picker share same config

I have a problem when using the date range picker in two different combination, once with single date and once with date range. Both are in two different pages (even popups). When using any one individually it works, however. When first using the single date picker and then navigating to a page with the date range picker, only a single date drop down is shown. Somehow there seems to be a global state that is not reset.
Happens on all browsers and latest angular-daterangepicker version.
Any idea where to start looking for this? as we use the component directly I do not see how this can be coming from any configuration we do, looks like something that is not reset from a global daterangepicker setting?

I just downloaded this today and am finding similar issues.  Everything seems to be shared between multiple instances.  I'm using $watch to get when the field changes.
I've got ranges, "Yesterday" "Today" "Last 7" "Last 30".  If I go to one screen and click on Today.  The dates are filled in on the form, and the $watch executes perfectly.
If i then go to a completely different screen, bring up the calendar, first off, Today is already highlighted, and if I click Today, it fills in the dates on the form, but the $watch does NOT fire.
This is a huge problem.


Color adjustment asap please - Docs

Describe the problem
Hello ladies and gents.
I am fairly new to Svelte/Sveltekit but I would like to make a suggestion please.
It is regarding documentation...
Can somebody change the background color of the sidebar from this difficult color #676778; to something darker?
Literally every time you want to focus on a link on the sidebar your eyes hurt and you lose at least 1 to 2 seconds until you focus on what you want to find and all that because poor contrast.
Also the "highlighted" link (the active one) is, honestly, almost indistinguishable from the inactive links below and above, why is this?
Why not make it something like almost black background with white inactive links and the active link like the orange color from the logo? Perhaps put a divider line in between links or something?
By the way, I do these things every time  I use the docs, this is how bad it is, no offense to anyone, but 1-2 seconds of faster focus per person per time they visit the docs, well, we want to be talking about performance when we are talking about Svelte right?
Please do the right thing, the nice svelte logo orange color matches great with a darker blackish background color, why put that ugly blueish/purplish (which is not dark enough for a bg color)?
To whoever can make this happen, PLEASE we need docs that can be scanned quickly.
Here is the contrast score https://coolors.co/contrast-checker/ffffff-676778
It's almost poor... if you have any sort of sight issues... I mean come on, how come no one addressed this before, docs is a huge part of the process.
Describe the proposed solution
Color for the "active" link => #ff3e00
Color for the sidebar background => #242426
Any dark enough background (with no colors, either blackish or grayish/blackish will do)
Alternatives considered
Please adjust this so visually impaired or people with sight difficulties (even the ones with glasses) can focus easier on the links and traverse faster.
Importance
i cannot use SvelteKit without it
Additional Information
Every time I browse the docs I literally go to inspect and change these myself....!
Thanks for your understanding!

I tend to agree that we could add more contrast to the sidebar. I'm not sure I like the proposed changes though. Here's a screenshot of what they look like

Alternatively, here's the sideback background set to #363636 with no change to the active link

Another idea, here's using bold rather than color to indicate the active item

Hey @benmccann  thanks for the response here.
On the first slide the accent color looks kinda red and not the actual orange brand color, are you sure you used the right code?
If it is the right color code then perhaps on that particular background we could lighten the orange just a bit.
Listen I very much appreciate your feedback here but I have to mention that as a person that has poor sight, I would argue that it's imperative the background to be kept at least a bit darker than your proposed hex above and the active link to be of an accent color (instead of a base like white) so it easily distinguishable and not on the same hue as the inactive links (truly important).
Check this =>
https://vuejs.org/guide/introduction.html
(They also have dark and light theme...)
We want to grow as a framework and as a user base but Vue.js is killing us with those Docs comparing to Svelte/kit's.
Please choose a slight darker background color, just a tiny touch and keep a punchy accent color close to the logo for the active links, I am positive this will help grow the framework, it sounds crazy but it is in my experience an important detail really.
Between choosing competing stuff online I personally have chosen then ones with the more accessible documentation.
@benmccann  thanks again for your consideration!

If only there was something like https://caniuse.com/mdn-css_at-rules_media_forced-colors

Hey @UltraCakeBakery, thanks for your reply here.
I am not sure what you are suggesting and if there is sarcasm involved on your reply.
To be honest it feels there is sarcasm involved in your message because of the way you started your sentence and you didn't expand on what you are trying to say, you didn't take the time, you pasted a link and asked of us to figure everything else out.
You provided no basis for all other people to work with. Is this link a universal and time-efficient solution to the current problem?
Do you mind telling us a little bit more please?
This is a serious matter that affects thousands of people (in different degrees).
Are you suggesting we all take the above action instead of adjusting 2 colors in the actual docs?
This is a genuine problem that needs solving, please provide constructive feedback/solutions.
No negativity is needed, thank you.

Hey @UltraCakeBakery, thanks for your reply here.
I am not sure what you are suggesting and if there is sarcasm involved on your reply. To be honest it feels there is sarcasm involved in your message because of the way you started your sentence and you didn't expand on what you are trying to say, you didn't take the time, you pasted a link and asked of us to figure everything else out.
You provided no basis for all other people to work with. Is this link a universal and time-efficient solution to the current problem? Do you mind telling us a little bit more please?
This is a serious matter that affects thousands of people (in different degrees). Are you suggesting we all take the above action instead of adjusting 2 colors in the actual docs?
This is a genuine problem that needs solving, please provide constructive feedback/solutions. No negativity is needed, thank you.

This is a serious matter that affects thousands of people (in different degrees).
Are you suggesting we all take the above action instead of adjusting 2 colors in the actual docs?

Hey @savannahx, thanks for your reply here.
I am not sure if there is unawareness or selfishness involved on your reply.
To be honest it feels there was unawareness and selfishness involved in your message because of the way you formulated yourself and did not think about us, the other 99% of svelte-kit users, who also have to deal with this change and asked of us to actually do all the work of implementing this new color.
You provided no way for us to reach a middle ground where both you and others can be happy. It seems like you really just want us to change the color to what you want. Did you even read the link that I posted in the one minute before you started writing this reply you posted 3 minutes after me making my original comment? Do you mind telling us why you get a bad vibe from my comment (saying it is sarcastic) even though I was trying to be helpful?
Suggestions like these affects billions of people (in different degrees). Are you suggesting we completely change the documentation instead of asking you and "the others" to start using the build-in tools provided to you by your operating system and browser?
This is a genuine problem that needs solving, please consider changing your mindset. We do not need more any people in the world that are like:
"THE WORLD NEEDS TO CHANGE, N̵̠̲͛̿͘O̵̞̙̒̇͘T̴̼͓̮̈́͂ ME"
"I AM N̵̠̲͛̿͘O̵̞̙̒̇͘T̴̼͓̮̈́͂ GONNA WEAR GLASSES OR CHANGE MY SETTINGS!

WE are the ones with disabilities, not the rest of the world. WE need to adapt ourselves to the world, NOT the other way around.
The documentation could offer better support for high contrast mode, dark mode, screen readers.. But I don't think it should.
It is fine as is.
If you are still unable to read the documentation (which is also available on Github, which has a very great accessibility).
you might want to buy a new monitor, open or close your blinds, change your color profile, tweak the brightness, gamma, contrast and other settings, increase the scale of your UI or install a extension which can do automatic contrast for you.
Again, this is a problem only we deal with. We are an edge case.

Dude's raging, for young people it's mostly preferable to fortify behind a false sense of reality and stand their ground. They are young and cocky (at least on the internet :P)
I am too old for this. it's okay, I am not perfect either, nobody is.
Anyway I really hope this gets addressed if anyone has access and time to implement this color edit (removing the washed out blueish background and using an accent color for the active link).
I would create a pull request but I barely know Svelte so apologies for not taking the initiative in that regard.
@benmccann  feel free to let me know if and when I should close this Issue and thanks again for your consideration.

alright, time out. i locked the conversation.
accessibility matters to us and we want to get this right. people shouldn't have to fiddle with browser settings just to read documentation. at the same time, there's a balance to be struck between maximising contrast and making the site pleasant to look at for people without visual impairments and/or shitty screens (we could just use pure black on pure white or vice versa everywhere, but that would be very tiring for most people to look at for any length of time).
so we will address this, though i make no guarantees about where it sits in the priority queue, and putting 'asap' in the issue title or declaring that the current contrast ratio means 'i cannot use SvelteKit without it' (unlikely) won't affect that decision (though there is now a pull request for it pending review — https://github.com/sveltejs/sites/pull/327)


Support Yandex.Metrica

Issue #83

@jcassee Looks like there is an issue with pip version 8.1.1 for builds running Python 3.2, most probably unrelated to the code of this PR.
Line 204 of the log says: "UserWarning: Support for Python 3.0-3.2 has been dropped. Future versions will fail here." -- We have to pin / install an earlier version of pip, or drop Python 3.2 support altogether.

I would not mind dropping support for Python 3.0-3.2. All distributions that come with Python 3 are on >= 3.3, right?

:+1: Changes look good.

Very bad: Django 1.8 still runs on Python 3.2. But I guess we're not the only ones being affected. I would first try to pin the version of pip<8.1.1, though.

Ah, we need to support Python 3.2 then. Let's try pinning pip then.

@sikmir Could you rebase against the new master branch? This should trigger a rebuild that should fix the failing checks.

Same here as in PR #88. Also the coverage decreased and needs action.
@jcassee What's the best place to add a test for triggering the TemplateSyntaxError?

@bittner Probably test_tag_analytical.py?

I think we can merge this PR. What do you think, @jcassee?


Remaining mentions of nf-core

Hi there,
Great work on what looks like a really nice pipeline! I notice that it looks like you used the @nf-core template to start the pipeline. This is no problem at all (we try to build our tools in such a way that people can do exactly this), but it looks like there are a few spots where you still need to strip out the default nf-core/ prefixes: https://github.com/canceromics/MeRIPseqPipe/search?q=nf-core
https://github.com/canceromics/MeRIPseqPipe/blob/15e8ae21b6978f51cfe16a0f9042549369d1ed88/assets/email_template.html#L9
https://github.com/canceromics/MeRIPseqPipe/blob/15e8ae21b6978f51cfe16a0f9042549369d1ed88/assets/email_template.txt#L7
https://github.com/canceromics/MeRIPseqPipe/blob/15e8ae21b6978f51cfe16a0f9042549369d1ed88/assets/email_template.txt#L13
https://github.com/canceromics/MeRIPseqPipe/blob/15e8ae21b6978f51cfe16a0f9042549369d1ed88/bin/scrape_software_versions.py#L8
https://github.com/canceromics/MeRIPseqPipe/blob/15e8ae21b6978f51cfe16a0f9042549369d1ed88/assets/multiqc_config.yaml#L2
https://github.com/canceromics/MeRIPseqPipe/blob/b3f70b4c6cd80b410abb457b81fd5d2fc24c5dec/README.md#L5
It's always nice to have some mention of nf-core in the readme too, just to acknowledge the work that goes into the template. But it's not a requirement, at the end of the day we are happy if what we build is useful for others.
Thanks,
Phil

Hi Phil, I was just added as one of the maintainers of this project. I have been following nf-core for a long time.  Many thanks for your suggestion, and we did benefit a lot from nf-core project. I appreciated your advices, and we will keep using nf-core in our coming project. @ewels
Also thanks for @apeltzer for my other project.

Great stuff! I just remembered that we have a fairly new tutorial listing which bits should be edited if using the template outside of @nf-core which might be helpful: https://nf-co.re/developers/tutorials/unofficial_pipelines

We will update the pipe by the tutorial .  @canceromics

Great stuff, thanks! One left! 😁
https://github.com/canceromics/MeRIPseqPipe/blob/48808328bed689a5a3406783c226a8dc8dec84b1/assets/email_template.txt#L7-L13

Many thanks! @ewels


Skipping DASH manifest

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.09.08. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[ ] I've verified and I assure that I'm running youtube-dl 2016.09.08

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[ ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v https://www.youtube.com/watch?v=rFUcrSLOJXQ
[debug] System config: []
[debug] User config: ['-f', 'best[height=720][fps <= 60]mp4']
[debug] Command-line args: ['-v', 'https://www.youtube.com/watch?v=rFUcrSLOJXQ']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2016.09.08
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: none
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Description of your issue, suggested solution and other information
WARNING: [youtube] rFUcrSLOJXQ: Skipping DASH manifest: ExtractorError('Failed to download MPD manifest: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)

Duplicate of #8944.


feat(cache): use vary headers to compare cached response with request headers

In this first commit, the cache handler handles multiple cached entries from the same cache key. It then tries to find which of the entries match the request, if any.
What I can't get my head around is how we are supposed to set the cache. We need both the response and the request at the same time. We need the vary headers and data from the response -  the vary headers so that we can compare, the data to cache the response, and the request headers to have something to compare against.
My interpretation of the current functionality is that after we fetch an existing entry from the cache, the onComplete method caches that object again. What is the purpose of caching the same entry again?

I implemented a CacheStore, with a simple interface so that it could be exchanged for a different cache if needed. Can we move the current implementation of CacheStore out of the cache.js file - maybe to util.js or to its own file? The reason would be so that we can export it and so that it can be tested and/or used elsewhere.

I tried to make the CacheStore class accessible from the outside using Symbol(), but couldn't get it to work. I exported it explicitly with export which works for now.

Is like to have max entry size and max entry ttl options

Also more tests wouldn't hurt

Is like to have max entry size and max entry ttl options

What should happen when the cache gets full? Simply ignore more entries to be stored, or delete an old one when there is a new entry?

What about range queries? Are those implicit vary?

No, technically range headers are not implicit vary, but practically they are, if the response is 206 Partial Content  and includes a Content-Range when sending in a range header.

Continued in https://github.com/nodejs/undici/pull/3562


contrapone, beneficial (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Dump failing images to a directory

I'm dealing with a scenario right now where a lot of tests are failing the image regression test on Windows but not other platforms on CI. It would be nice if there were an option to dump the failing images to a specific path so that I can upload those as a CI artifact to inspect. I'm currently manually doing this

I am doing this in https://github.com/pyvista/pyvista/pull/3609 which would need to migrate here

Another option is to save all image files during a test to a folder (default to a temporary folder).  Then you could upload this to an artifact in CI.  This would lead to larger artifacts, but also has other advantages, for example being able to inspect for false negatives.  I don't have a feeling one way or the other.

Good point. I'd rather this be to save all produced images, not just failing ones

To expand upon this: I think we should have two configurable directories. 1) the stored image cache, 2) the generated images for a single run.

stored image cache.  Can there be a universal way to set this?  It should be related to the testing code, which could be hierarchical, so tricky to access here. If it is required to be explicitly set by the user, we should check that this is done, or raise an error.
generated images.  This could be in the shared appdirs by default.

It would also be great in the future to allow for an optional check that all the files in the cache dir have a corresponding file in generated dir, and vice versa.  This would ensure that everything is working as expected during testing.


Color command applied over a time frame is also applied to other objects in editor outside of that frame

As a mapper, I want to be able to color note groups a certain color so I can differentiate sections.

Currently, we may not want to do this in terms of design direction, but worth considering

Decided to close this since this is expected behavior for now.

Decided to close this since this is expected behavior for now.


When pasting into Documentation field, the paste is not style free

OSX using 1.14
when you paste from certain applications like a web browser, the style of the copy is being pasted into the text box.  This is occurring for the Documentation field.

Related to https://github.com/camunda/camunda-modeler/issues/702

Needs fix via https://github.com/bpmn-io/bpmn-js-properties-panel/issues/265.

Needs fix in dmn-js-properties-panel and cmmn-js-properties-panel, too.

Fixed via https://github.com/camunda/camunda-modeler/pull/1730


Namespace input and chip overlap fix

Signed-off-by: Ayush<EMAIL_ADDRESS>Description
This PR fixes #2896
The Below video must be enough I believe.
Changes

Margin for the container of both is fixed.
Made the input bar flexible.
Alignment for chip and input changed to fix chip at top when the list of suggested namespace appear.

After changes
https://user-images.githubusercontent.com/59086855/120035889-f0699280-c01c-11eb-9f23-324ab632173a.mov
For reviewers
I replaced Grid from material UI to normal divs because its not easy to customise them and we need to override them and sometimes makes things dirty.
Signed commits

[x] Yes, I signed my commits.

NOTE:Ignore the lag.

@leecalcote I hope this is what you were expecting.


Allow aeson 2.2

https://github.com/commercialhaskell/stackage/issues/7031

This build actually tested against aeson 2.2: https://github.com/tfausak/patrol/actions/runs/5422668475/jobs/9859601593?pr=13#step:12:13


Changing between presets that have side arrows keeps the old arrow style

Repro: make a man_made=embankment line (line 1 in screenshot), change to barrier=guard_rail (expected line 2) -- observe that the side arrow style remains from embankment (line 3).

2.14.3, Firefox x64 65.0.2

@RudyTheDev Thanks for reporting! Turned out to be a simple fix once I tracked it down 👍


Feature Request: Add a flag to not include the Git tag reference in the change log

When generating the CHANGELOG.md, I would like to be able to not add the Git references to the document.
For instance, I have the following generated by semver (the highlighted part is what I would want to suppress with the new option):
[timesheet-api]  Calculated new version "0.2.0".

---
## [0.2.0](https://.../compare/timesheet-api-0.1.0...timesheet-api-0.2.0) (2022-07-07)

### Features

* **timesheet-api:** add a /metrics endpoint with Prometheus data ([7150594](.../commit/7150594277a3e1d446d15930567cbff3086809ed))
* **timesheet-api:** add the /healthz health check with terminus for NestJS ([7c5a1bc](https://.../commit/7c5a1bcfa010a81dad13cd7cb855217a8d10f510))

### Bug Fixes

* **timesheet-api:** add the OPTIONS method to /api for the health check to validate http is up ([74260b9](https://.../commit/74260b90228fcb9b56255c0f8c96521c10106ecf))
* **timesheet-api:** correct the database configuration to be supported with the TypeORM migrations ([18d03b2](https://.../commit/18d03b277ce42a387ad2b1c89488a9910257555a))
* **timesheet-api:** correct the database connection information ([513ac27](https://.../commit/513ac274159dd249e82841ca21879b7051a383ac))
---

which would then generate:
[timesheet-api]  Calculated new version "0.2.0".

---
## [0.2.0](https://.../compare/timesheet-api-0.1.0...timesheet-api-0.2.0) (2022-07-07)

### Features

* **timesheet-api:** add a /metrics endpoint with Prometheus data
* **timesheet-api:** add the /healthz health check with terminus for NestJS

### Bug Fixes

* **timesheet-api:** add the OPTIONS method to /api for the health check to validate http is up
* **timesheet-api:** correct the database configuration to be supported with the TypeORM migrations
* **timesheet-api:** correct the database connection information
---

This would need to be able to customize the output of the changelog generation, note that actually, we rely on conventional-changelog.


[oap-native-sql] Some fixes for codegen groupby aggr

use arrow::internal::HashTraitsarrow::StringType::MemoTableType instead of ScalarMemoTable
update metrics for groupby hashaggr

Signed-off-by: Chendi Xue<EMAIL_ADDRESS>

Hi, @zhouyuan , this is a fix for TPCH Q21, I realized that I used ScalarMemoTablestd::string rather than BinaryMemoTable, which brought some incorrect hashmap result, fixed in this PR

Cool, let me see if we can create another PR to master, thanks!
Thanks, -yuan

From: Chendi.Xue<EMAIL_ADDRESS>Sent: Friday, July 3, 2020 6:55:24 PM
To: Intel-bigdata/OAP<EMAIL_ADDRESS>Cc: Yuan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Intel-bigdata/OAP] [oap-native-sql] Some fixes for codegen groupby aggr (#1434)
Hi, @zhouyuanhttps://github.com/zhouyuan , this is a fix for TPCH Q21, I realized that I used ScalarMemoTablestd::string rather than BinaryMemoTable, which brought some incorrect hashmap result, fixed in this PR
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Intel-bigdata/OAP/pull/1434#issuecomment-653487201, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAKXDMPJP22UUSLPEYDDX3RZW2JZANCNFSM4OPWO42A.


[TEVA-1758] Add route to jobseeker job applications index page

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-1758
Changes in this PR

Consistent option order in routes (only/controller)
Use resource for jobseeker job_application new/create routes (prevents clash + makes more sense)
Add index route for jobseeker job_applications

Review app deployed to https://teaching-vacancies-review-pr-2982.london.cloudapps.digital