text:
Added type="button" to 'set privacy button'

Added type="button" to 'set privacy button'  to fix the opening of page privacy menu on hitting enter in a char block in edit stream-page page.
Closes #6592

Merged in 400bc57536729edec8a6b71468c60ddd19282e74

authors: gasman sagar-wal


text:
Avoid assuming an integer PK named 'id' on multiple upload views

Fixes #6512. Eliminate int() casting in JSON responses and use .pk rather than .id to accommodate the possibility of non-standard PK fields.
This isn't really testable without either wider changes to support non-integer IDs in the images app (e.g. in URL routes), or setting up a custom 'multiple upload' app within the test apps, both of which are probably overkill for such a niche requirement - so this is best considered code cleanup rather than a full-fledged new feature.

Nice! I've been meaning to do the same changes in views/generic/models.py so that the Snippets views can override less code, but I haven't checked whether that would break anything (I assume not).

@laymonage  - not sure if it is the same but this issue has been raised recently https://github.com/wagtail/wagtail/issues/9205

source: gharchive/pull-request

authors: gasman lb-

repo: wagtail/wagtail

license_type: permissive

license_source: github-api


text:
🛑 cyconet.org Blog is down

In 890f75b, cyconet.org Blog (https://log.cyconet.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cyconet.org Blog is back up in 9ebfe06 after 2 hours, 15 minutes.

source: gharchive/issue

repo: waja/cyconet-upptime

license: MIT


text:
🛑 cyconet.org is down

In 811bff7, cyconet.org (https://www.cyconet.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cyconet.org is back up in 6f9fef9 after 57 minutes.


text:
Do a bundler run as part of the CI

This is a feature request
Problem
js-waku depends on novel packages such as js-libp2p family of libraries but also cryptography related libraries.
These dependencies change fast and do have breaking changes.
While these library target both browser and NodeJS environment, the biggest users are NodeJS (Lodestar Eth node).
Hence, regressions that only impact the browser can and have been introduced in the past. The most impactful one being the introduction of a NodeJS API usage, that then requires a polyfill in the browser or react native environment.
Polyfills mean added configuration to the bundler for js-waku maintainers and users, it also increases the final size of the web app using js-waku.
Proposed Solutions
Run as part of the CI/tests, a bundling of the library with popular bundlers. The default config of the bundlers should be used to ensure minimum friction of js-waku users.
List of bundlers to consider (some items in this list might not be bundlers):

webpack
react-scripts
Preact
Vite
Rollup
esbuild
parcel
SvelteKit

Notes
Would be good to review best practice for TypeScript library. In my time-boxed search, I could not find anything promising. Yet, I believe I have seen this pattern in the past.
Most likely, we want to have some very simple applications using @waku/sdk as a test.

Not sure if it fits in the "bundler" category, but there are cases where bundlers, such as vite have framework-specific plugins that may modify the bundling environment.
For example, the use case that I have is being able to use SvelteKit (automatically uses vite for bundling) to create a project using js-waku.

@mfw78 good point. I quickly checked and it seems that vite can be used for that task as well. Since it is a front-end tooling similar to webpack.

As for the description just putting it in my words.
What we want to do is to have a step in our pipeline that helps to make sure @waku/sdk is able to be built within some abstract web application (react, svelte, etc).
I think before making it a bounty let's agree on boundaries of what is bare coverage.
I would say that if a web app with @waku/sdk in it is able to be built with 1 - 3 most common web frameworks and 1 - 3 most common build tools then we are safe. I am leaning towards 1, to be honest, because I don't see anything specific to web frameworks or build tools and I'd like to have at least surface here as possible.
The thing is if we have such a pipeline step configured then we'll need to support it in the same fashion as js-waku-examples: updating versions, fixing bugs and problems.

So long as this meets the requirements of ensuring: "I'm a developer building in XYZ framework and @waku/sdk just works" where XYZ is in the list of the aforementioned frameworks. I'm not bundler expert and have wasted many hours digging into the dependencies abyss. Making this accessible, and preserving it's accessibility is key.

Well that's the thing.
Even if it works with webpack and React uses webpack it doesn't mean it works with React because of some way React configures webpack (eg react-script doesn't support cjs files).
If we do not want an explosion of pipelines then we can just add pipelines for web frameworks but not bundlers.

Then let me summarise:

we want to check if js-waku is able to be build within a web framework X;
success criteria if it is built without errors;

As additional step could be a combination of https://github.com/waku-org/js-waku/issues/52 and those simple web apps with js-waku in them.

Todo:

[ ] simple React example
[ ] pipeline step for releases
[ ] write bounty for other framework examples

An example, right now, using svelte with the latest version of js-waku, the development server runs waku, no problems. But, unfortunately, after building, it no longer works.

An example, right now, using svelte with the latest version of js-waku, the development server runs waku, no problems. But, unfortunately, after building, it no longer works.

What's the error? did you open an issue? @helpisdev also mentioned an issue with latest version of @waku/sdk.

Sorry for the delay in getting back to this one. Currently in the environment:

"@sveltejs/kit": "^1.15.5",
"@waku/interfaces": "^0.0.15",
"@waku/sdk": "^0.0.16",

Using vite ^4.2.1 as the bundler. The application works fine in the dev mode (ie. pnpm run dev), however, after being built it fails with:

A repository for reproducing this error is available at https://github.com/rndlabs/pastebee.

hey @mfw78, strangely I have the app working with pnpm install and pnpm run dev.
Maybe worth trying if you didn't:

reinstall pnpm or even npm;
removing pnpm-lock and node_modules;
using @waku/sdk of 0.0.18 version;

authors: fryorcraken mfw78 weboko

repo: waku-org/js-waku


text:
Make non-ephemeral messages costly

In Store incentivization, servers are supposed to store all non-ephemeral messages forever. Even if we implement payments for every request, there still a mismatch between who causes costs (the sender) vs who pays for it later (the requester).
Shall the sender of a non-ephemeral message (partially?) pay for its future storage? Or, at least, should sending a non-ephemeral message be more expensive than sending an ephemeral one? After all, we probably want to discourage non-ephemeral messages where ephemeral ones suffice.

Some thoughts on the matter.
The reason of Waku store is to cater for resource-restricted devices that are (mostly) offline and cannot participate to relay to access past messages.
It is assumed that the share of store client nodes, ie, nodes without permanent internet access, is high enough that Waku store is the best solution for the problem (and not, let's say, rebroadcasting on demand for a minor share of non-relay nodes).
Hence, it is assumed that the functional benefit of Waku Store is for these end-users that have offline devices, which is why the proposed approach would be for "retrieving" users to pay for this service (or at least, for the act of retrieving being the incentivized action).
Which introduces this possible discrepancy between the incentivized action (retrieved message) and the actual cost of the action (assumed disk space costs more than upload bandwidth).
In terms of ROI, assuming that retrieval is the selected incentivization mechanism, it means that an operator may want to store messages that are likely to be most queried.
E.g., whether related to a popular app or popular content topic. ML could even be applied to let a node learn what messages are most likely to be retrieved based on their content topic, metadata, timestamp, rln proof, payload size.
This in itself, could potentially be an issue for content topic with less users.
Do note that for privacy reasons, we encourage usage of "buckets" for content topic to get some k-anonymity when using light client (e.g., do not use a public key in content topic, instead Status protocol uses 4 first bytes of hash of public key in content topic)
Yet, this does not solve the issue for brand new app with less users.

In terms of business model, I see 4 possibilities:

A user wholesomely pays for the usage of Waku by a group of people (e.g. Status Community owners pays for the community, or dapp dev pay for infra).
A user contributes to the usage of Waku by a group of people (e.g. Status Community member contributes to cost of running community).
A user only pays for their own usage (e.g. user pays for his 1:1 messages retrieval).
User runs infra and "nobody" pays for infra (e.g. users enable stores in their Status Desktop instance).

For (1) and (2), a model where the users pay for storage makes sense. e.g., Alice pays for the network/an operator to store messages on the content topic of her community, versus Alice pays for the network/an operator to let users retrieve messages on the content topic of her community.

One risk in relying on a decentralized storage system for this model is that, AFAIK, there is no decentralized storage system that caters for web apps. All systems I know either do not cater for web apps at all or only provide centralized gateways as a solution for web app. The only solution I found so far is webtorrent, that enables web app participation to the torrent network using webrtc.
This could be one solution as Codex aims to be a protocol that can give durability to existing storage systems such as BitTorrent.

I agree with @alrevuelta's proposal above that one way to incentivized dapp developer to only use store when necessary would be to make RLN heavier for store messages.

authors: fryorcraken s-tikhomirov

repo: waku-org/research


text:
How to destroy videojs-transcript?

I am using videojs-transcript with videojs-playlist and videojs-playlist-ui.
It's has been pretty fiddly getting it working, I think I am close, but as playlists (audio playlists for example) sometime don't require the transcript plugin, I think i need to remove the transcript plugin before switching playlists, else I get the error:

Uncaught TypeError: Cannot read property 'activeCues' of undefined

How can it be removed when it is not required?
Thank You.

Update: I think (still need to test more) I resolved this by using dispose() on the player, and resetting all html, videojs and videojs plugins back up whenever I changed a playlist.

I'm curious if you ever got this working. I'm not using playlists and run into this same error by simply including the script and calling it in the player.

authors: npstcole oshihirii

license: mit

license_source: bigquery


text:
Is it possible to only delete media files in each project?

Is your feature request related to a problem? Please describe.
It seems there's no way to only delete the media files in each run after it finishes. The media usually consumes the largest storage yet the least useful. So is there any way to just delete all images uploaded to the run?
Describe the solution you'd like
A way to delete all images or media uploaded.
Describe alternatives you've considered
None.
Additional context
None.

Found the feature on the web app

repo: wandb/client


text:
🛑 探针_nezha is down

In c559ede, 探针_nezha (https://nz.wsee.cf) was down:

HTTP code: 521
Response time: 705 ms

Resolved: 探针_nezha is back up in e04cc92 after 37 minutes.

repo: wang-task/upptime


text:
发现一个XX bug

具体bug描述

Thanks

repo: wangabeng/test


text:
mention渲染出来info没有数据的解决方法/自定义样式

昨天突然需要一个@提及的方法 发现v5版本有插件 所以昨天从v4版本升级v5 两者的差异的初始化有点大
遇到一个问题 所有渲染的mention的Node 插入到编辑器里 都是data-slate-node="element"的存在 只能把value渲染出来 导致要显示的值是name 但是实际操作的值提醒的人是user_id 不可能把user_id显示到屏幕上吧 看了半天的源代码 包太分散太复杂了 感觉是模块下的elem-to-html没有应用到
解决方法1：直接提交富文本的时候将编辑器所有children拿出来 递归筛选出type为mention的节点
// 每次提交的时候调用方法获取id
getMentionList() {
      let mentionSet = new Set()
      const getMention = item => {
        if (item.type == 'mention') {
          mentionSet.add(item.info.id)
        }
        item.children &&
          item.children.forEach(child => {
            getMention(child)
          })
      }
      this.editor.children.forEach(x => {
        getMention(x)
      })
      return [...mentionSet]
}

问题来了 我觉得样式不够美观 而且 我想修改基础样式 并且当被@到的人 进来页面高亮显示
解决方法2：直接修改renderMention模块 在注册前修改  不需要修改源码文件 更换环境也不受影响
import mentionModule from '@wangeditor/plugin-mention'
import MentionModal from './MentionModal'
mentionModule.renderElems[0].renderElem = function (elem, children, editor) {
  // 当前节点是否选中
  const selected = DomEditor.isNodeSelected(editor, elem)
  const { value = '', info } = elem
  // 构建 vnode
  const vnode = h(
    'span',
    {
      props: {
        contentEditable: false, // 不可编辑
      },
      // 自定义的属性 这个h的class没有效果 所以直接再attrs下编写
      attrs: {
        'data-id': info.id,
        class: 'w-mention',
      },
      style: {
        marginLeft: '3px',
        marginRight: '3px',
        backgroundColor: 'var(--w-e-textarea-slight-bg-color)',
        border: selected // 选中/不选中，样式不一样
          ? '2px solid var(--w-e-textarea-selected-border-color)' // wangEditor 提供了 css var https://www.wangeditor.com/v5/theme.html
          : '2px solid transparent',
        borderRadius: '3px',
        padding: '0 3px',
      },
    },
    `@${value}`, // 如 `@张三`
  )

  return vnode
}

在标签中有自定义的class 也可以直接修改style里样式
所以可以
::v-deep .w-mention {
  cursor: pointer !important;
  color: red;
}

导出的富文本html里面也有需要的数据

我是两种方法结合使用 第二种是写前端被提醒者查看时高亮提醒 第一种是我写后端的时候set拿到的id不会重复 我就可以安心做我的提醒操作

该怎么实时定位当前的聚焦位置 让菜单在鼠标的位置下方

该怎么实时定位当前的聚焦位置 让菜单在鼠标的位置下方

根据demo里面的代码修改 但是他的代码有个问题 封装的modal是绝对布局 如果你的自己封装的vue组件div 不是相对布局位置就会偏移到能寻找到是相对布局的上层dom直到body 所以解决方法如下：
更换demo modal中的mounted代码 我自己修改了下拉框的组件 所以有些许不同
 mounted() {
    // 获取到当前父对象的编辑器选取位置top left 也可以直接prop传入
    let pos = this.$parent.editor.getSelectionPosition()
    // 由于需要全屏功能 所以我的编辑器不是相对布局 我要获取到编辑器在页面的位置
    let dom = document.querySelector('.w-e-text-container')
    this.top = `${dom.offsetTop - 45 + parseFloat(pos.top.replace('px', ''))}px`
    this.left = `${dom.offsetLeft + parseFloat(pos.left.replace('px', ''))}px`
    // vuetify 组件的下拉列表显示
    this.$refs.input.isMenuActive = true
    let selectInput = document.querySelector('#mention-modal input')
    // 当内容为空的时候 按下退格键 需要关闭@框以及清除@符号
    selectInput.onkeydown = e => {
      if (!this.search && e.code == 'Backspace') {
        this.$emit('closeMentionModal')
      }
    }
  },

希望我的回答能够帮助到你

该怎么实时定位当前的聚焦位置 让菜单在鼠标的位置下方

我没有做跟随下拉菜单在鼠标下方 我是根据当前编辑器的光标在在它旁边显示

嗯嗯，非常感谢 这对我帮助很大

// 当前节点是否选中
const selected = DomEditor.isNodeSelected(editor, elem) 这个DomEditor是？

// 当前节点是否选中 const selected = DomEditor.isNodeSelected(editor, elem) 这个DomEditor是？

噢噢 忘了
import { createEditor, Boot, createToolbar, DomEditor } from '@wangeditor/editor'

非常感谢

编写高亮功能的时候 发现导出html渲染回网页的时候 elem-to-html是getHtml的时候生效的 所以之前自定义的样式不见了 同理 修改一遍渲染器的为源码即可
mentionModule.elemsToHtml[0].elemToHtml = function (elem, childrenHtml) {
  const { value = '', info = {} } = elem
  return `<span data-w-e-type="mention" class="w-mention" data-w-e-is-void data-w-e-is-inline data-user_id="${info.user_id}">@${value}</span>`
}

authors: GWnbsp codecnmc


text:
希望添加字体和背景调色板功能

目前只有特定几种颜色选择，对运营配置文本不大足够，希望能加上一个调色板，谢谢！

不知道你有没有好好看文档，字体，颜色都可以自定义增加上的，很方便

指的是在线调色板，类似element-ui的ColorPicker 那种

哦哦，理解错了，增加在线调色板功能的话应该更不错

希望增加，对于不具备写代码能力的人非常有用

authors: JohnnyZhangQiao wjup


text:
Model Application Transfering

Do you consider transferring the model to medical image recognition or segment? Medical images always include multiple targets or structures, especially in longitudinal monitoring in vivo, can your model be applied to track or swiftly extract different structures from these images?
Lucas

TransCD is a model for change dectection task. However, there are varies of Vision Transformer-based model for object detection, image classification and segmentation, such as Swin-Transformer, DETR, SEGR, and TransFuse, MedT for medical images, and so on.


text:
在横屏状态下，切换回竖屏，导航栏上变白，子元素不见了？

我开始首页Page1    不见了

我开始首页的 标题    page1 不见了

(BOOL)navigationBar:(UINavigationBar *)navigationBar shouldPopItem:(UINavigationItem *)item {
试试把这个方法注了

authors: libercata mengxinyizhui


text:
Update to the new version of Android Studio

Is it possible to update the library to support the new version of Android Studio and gradle?

@anhmiuhv Many thanks for your pull request.

authors: anhmiuhv warkiz

repo: warkiz/IndicatorSeekBar


text:
Transfer of current folder "." crashes both sides of connection

wormhole send .

Created a giant zipfile then waited.  Ok.
wormhole receive

Asked for code then crashed:
Error: refusing to overwrite existing '.'
TransferError: transfer rejected

This also killed the sender !  Had run send and make the (huge) zipfile again, then:
wormhole receive -o tempfolder

Worked around the issue.  :/
Use of the current folder "." should be handled transparently, thank you.

Assigning to @mixmastamyk for verification: please close (or tell me to close) if 0.10.4 works as expected.

I haven't heard any further problem reports, so I'm assuming this is fixed. @mixmastamyk , please re-open if you see otherwise.

authors: mixmastamyk warner

repo: warner/magic-wormhole


text:
chore: reuse animation library from modal in expandable

Two primary goals in this PR:

Reuse @itsy/animate that the Modal component uses for transitioning the title to ensure small bundle size
Simplify the expand-transition component, might need some checks from @digitalsadhu to ensure I haven't missed something critical - but I don't understand why some of the moving parts are in the original

This PR can safely wait for the Modal's merge, so no rush to review
(I still need to replace the element-collapse use in Toast, but I don't anticipate that being a blocker and wanted to get an RFC first on this change)

@digitalsadhu - just quickly can you see if there's anything in the expand-transition component I'm changing that is obviously bad? (it did a few obscure things I don't understand the rationale for)

@pearofducks After running the docs locally on Safari, I noticed that the content doesn't hide/show on expand/collapse the same way it does on Chrome and Firefox. The previous implementation worked fine on Safari, which can be checked here.

@BalbinaK - thanks for looking into this and spotting that quirk, I'll take a look!

authors: BalbinaK pearofducks

repo: warp-ds/elements


text:
add HeaderFooterEmptyRecyclerView repo

for support android RecyclerView support Header Footer and Empty list

https://github.com/miladheydari/HeaderFooterEmptyRecyclerView

somebody please answer meeeeeeeeeeeee

repo: wasabeef/awesome-android-ui


text:
[BUG] wash app delete command returns success for invalid application name

Affected project(s)

[ ] documentation
[ ] examples
[ ] wasmCloud host
[x] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[ ] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Describe the bug
If an incorrect model name is passed without a version to the wash app del <app_name> command, it still outputs a success message ("Deleted application: <app_name>") even though this app does not exist.
Steps to reproduce

list all applications with wash app list
try to delete an app using an invalid name without specifying a version
check the apps again with wash app list to confirm no changes have occurred

Example:
$ wash app list
  Name                                  Deployed Version                      Status
  rust-hello-world                      01JE99W346KMJR9XG33FE7QBYM            Deployed
    └ HTTP hello world demo in Rust, using the WebAssembly Component Model and WebAssembly Interfaces Types (WIT)

$ wash app del test
Deleted application: test

$ wash app list
  Name                                  Deployed Version                      Status
  rust-hello-world                      01JE99W346KMJR9XG33FE7QBYM            Deployed
    └ HTTP hello world demo in Rust, using the WebAssembly Component Model and WebAssembly Interfaces Types (WIT)

Expected behavior
The wash app del command should return a meaningful message for invalid app names instead of printing a success message. The output should be the same as for invalid versions:
$ wash app del test 1.0.0
Already deleted application: test

Environment

OS: MacOS
Shell: zsh
wasmcloud Versions:$ wash -V
wash          v0.37.0
├ nats-server v2.10.20
├ wadm        v0.18.0
└ wasmcloud   v1.4.2

Root Cause
wadm only checks wether the application actually exists if a version has been specified (see here). If no version was specified, wadm simply deletes the application manifest (see here) without covering the DeleteResult::Noop case.
Proposal
Checking first if for the specified application a manifest exists and start a deletion attempt only in case it does. Otherwise return early with DeleteResult::Noop.
If you agree with my proposal, I would be happy to create a PR for it.

@ffuerste I agree here! I think we should still mark the operation as successful for idempotency, but we should indicate that the application was "already deleted" as you said. Please feel free to open a PR anytime

authors: brooksmtownsend ffuerste

repo: wasmCloud/wadm


text:
[BUG] wasmcloud provider wit bindgen fails to export interfaces

Affected project(s)

[ ] documentation
[ ] examples
[ ] wasmCloud host
[ ] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[ ] capability providers
[X] provider bindgen
[ ] control interface client
[ ] other / not sure

Describe the bug
When i use the following custom sql interface:

interface types {
    /// one single row item
    record row {
        fields: list<field-value>,
    }

    record field-value {
        field-name: string,
        value: data-type,
    }

    /// common data types
    variant data-type {
        int32(s32),
        int64(s64),
        uint32(u32),
        uint64(u64),
        float(float64),
        double(float64),
        str(string),
        boolean(bool),
        date(string),
        time(string),
        timestamp(string),
        binary(list<u8>),
        null
    }

    /// allows parameterized queries
    /// e.g., prepare("SELECT * FROM users WHERE name = ? AND age = ?", vec!["John Doe", "32"])
    resource statement {
        prepare: static func(query: string, params: list<string>) -> result<statement, error>;
    }
    /// An error resource type.
    /// Currently, this provides only one function to return a string representation
    /// of the error. In the future, this will be extended to provide more information.
    resource error {
		trace: func() -> string;
  	}

    /// A connection to a sql store.
    resource connection {
        open: static func(name: string) -> result<connection, error>;
    }
}

I am unable to compile my provider as I get this error:
|
= help: message: "static_statement.prepare" is not a valid identifier
Steps to reproduce

Reproduce wasi:sql with new custom interface
Create example provider
wit-bindgen = { version = "0.19.2", features = ["default"] }
wasmcloud-provider-wit-bindgen = { git = "https://github.com/wasmCloud/wasmCloud.git", branch = "main" }

Expected behavior
Expect for my wit to be generated
Environment

OS: Mac

Screenshots / Logs / Additional context

This is the only error that i receive from the macro it seems so, however this isn't the only case. If i try to depend on wasi:logging instead of my custom port of wasi:sql which is very similar and I doubt is problematic (it works for all of my actors that depend on the same WIT)  and remove all dependencies and only import wasi:logging in my final world for my provider like so:
world provider-my-world {
import wasi:logging/logging;
export my-world-provider-interface;
}
then i get this error:
help: message: failed to translate export fn: unsupported type kind TypeDef {
name: Some(
"level",
),
kind: Enum(
Enum {
cases: [
EnumCase {
name: "trace",
docs: Docs {
contents: Some(
"Describes messages about the values of variables and the flow of\ncontrol within a program.",
),
},
},
EnumCase {
name: "debug",
docs: Docs {
contents: Some(
"Describes messages likely to be of interest to someone debugging a\nprogram.",
),
},
},
EnumCase {
name: "info",
docs: Docs {
contents: Some(
"Describes messages likely to be of interest to someone monitoring a\nprogram.",
),
},
},
EnumCase {
name: "warn",
docs: Docs {
contents: Some(
"Describes messages indicating hazardous situations.",
),
},
},
EnumCase {
name: "error",
docs: Docs {
contents: Some(
"Describes messages indicating serious errors.",
),
},
},
EnumCase {
name: "critical",
docs: Docs {
contents: Some(
"Describes messages indicating fatal errors.",
),
},
},
],
},
),
owner: Interface(
Id {
idx: 0,
},
),
docs: Docs {
contents: Some(
"A log level, describing a kind of message.",
),
},
}
So the provider bindgen then starts complaining about the logging WIT

Any updates here?

Hey @wbaileyisla did you run into the same issue? Would you mind sharing a reproduction?
@LUK3ARK Resource support is lacking in provider bindgen right now -- I assume that the thing you're trying to implement must use a resource, is that correct?

I am just trying to get the macro to compile, yes please refer to sql here:

    /// allows parameterized queries
    /// e.g., prepare("SELECT * FROM users WHERE name = ? AND age = ?", vec!["John Doe", "32"])
    resource statement {
        prepare: static func(query: string, params: list<string>) -> result<statement, error>;
    }
    /// An error resource type.
    /// Currently, this provides only one function to return a string representation
    /// of the error. In the future, this will be extended to provide more information.
    resource error {
		trace: func() -> string;
  	}

    /// A connection to a sql store.
    resource connection {
        open: static func(name: string) -> result<connection, error>;
    }

I also have a custom sql provider that I cannot use because of this error. Currently blocked heavily on this.
please see the world definition:
package lattica:provider-sql;

world provider-sql-client {
    export org:sql/readwrite@0.1.0;
}

interface readwrite {
    use types.{statement, row, error, connection};

    /// query is optimized for querying data, and
    /// implementors can make use of that fact to optimize
    /// the performance of query execution (e.g., using
    /// indexes).
    query: func(c: borrow<connection>, q: borrow<statement>) -> result<list<row>, error>;

    /// exec is for modifying data in the database.
    exec: func(c: borrow<connection>, q: borrow<statement>) -> result<u32, error>;
}

interface types {
    /// one single row item
    record row {
        fields: list<field-value>,
    }

    record field-value {
        field-name: string,
        value: data-type,
    }

    /// common data types
    variant data-type {
        int32(s32),
        int64(s64),
        uint32(u32),
        uint64(u64),
        float(float64),
        double(float64),
        str(string),
        boolean(bool),
        date(string),
        time(string),
        timestamp(string),
        binary(list<u8>),
        null
    }

    /// allows parameterized queries
    /// e.g., prepare("SELECT * FROM users WHERE name = ? AND age = ?", vec!["John Doe", "32"])
    resource statement {
        prepare: static func(query: string, params: list<string>) -> result<statement, error>;
    }
    /// An error resource type.
    /// Currently, this provides only one function to return a string representation
    /// of the error. In the future, this will be extended to provide more information.
    resource error {
		trace: func() -> string;
  	}

    /// A connection to a sql store.
    resource connection {
        open: static func(name: string) -> result<connection, error>;
    }
}

Hey @LUK3ARK, thanks for the additional example. Give us just a sec to circle the wagons. A bunch of us are knee deep in 1.0 work right now but I’ll try to get you a clear answer as to how we’re going to fix it and workarounds by tomorrow hopefully

Hi @LUK3ARK please see my previous comment:

@LUK3ARK Resource support is lacking in provider bindgen right now -- I assume that the thing you're trying to implement must use a resource, is that correct?

What you can do in the meantime is to use a pseudo-resource approach:
interface readwrite {
    use types.{statement, row, error, connection};
    /// Pseudo resource that identifies a created connection
    type connection-id = u32;
    /// Pseudo resource that identifies a prepared statement
    type statement-id = u32;

    /// query is optimized for querying data, and
    /// implementors can make use of that fact to optimize
    /// the performance of query execution (e.g., using
    /// indexes).
    query: func(c: connection-id, q: statement-id) -> result<list<row>, error>;

    /// exec is for modifying data in the database.
    exec: func(c: connection-id, q: statement-id) -> result<u32, error>;

    prepare_statement: func(func(query: string, params: list<string>) -> result<statement-id, error>

    open_connection: func(name: string) -> result<connection-id, error>;
}

This should unblock you for now, as we work on resource support in bindgen.

Thank you for the replies.
I get the error:
invalid character in identifier '_'
I fixed the wit definition to this:

interface readwrite {
    use types.{statement, row, error, connection};
    /// Pseudo resource that identifies a created connection
    type connection-id = u32;
    /// Pseudo resource that identifies a prepared statement
    type statement-id = u32;

    /// query is optimized for querying data, and
    /// implementors can make use of that fact to optimize
    /// the performance of query execution (e.g., using
    /// indexes).
    query: func(c: connection-id, q: statement-id) -> result<list<row>, error>;

    /// exec is for modifying data in the database.
    exec: func(c: connection-id, q: statement-id) -> result<u32, error>;

    prepare-statement: func(query: string, params: list<string>) -> result<statement-id, error>;

    open-connection: func(name: string) -> result<connection-id, error>;
}

After making these changes I still get the error:
help: message: "static_statement.prepare" is not a valid identifier
I have tried on v0.17 v0.19.2 and v0.20 of wit-bindgen all are no luck

Awesome to hear @LUK3ARK , thanks for reworking it, I've fixed the underscores in my own comment as well. Thanks for working around this -- resources are awesome, but operations on them aren't QUITE ready to fly over the lattice just yet.

12 |   wasmcloud_provider_wit_bindgen::generate!({
|  _^
13 | |     impl_struct: Sql,
14 | |     contract: "org:sql",
15 | |     wit_bindgen_cfg: "provider-sql-client"
16 | | });
| |__^ variant or associated item not found in InvocationError
Still getting this error come from the macro

I'm not sure if it will impact it or not, but we have wit bindgen on 0.17 right now in our wasmcloud deps

I have tried 0.17, 0.19.2 and the new 0.2 but that seems very breaking, all result in same

Got a fix for this, I changed my dependency and ran cargo update and got this working:
wasmcloud-provider-wit-bindgen = { git = "https://github.com/wasmCloud/wasmCloud.git", rev = "5a3a37af8c4051989e0fcc9c965668a7a7d0599f" }
I tried this with my original setup in hopes this was the original cause of that but I still had issues building. When applying @vados-cosmonic suggested changes and moved to the specific revision I was able to compile my provider.
This removes my blocker

repo: wasmCloud/wasmCloud


text:
Make the ProviderArchive type derive clone

It's an inconvenience for consuming types to not be able to clone this struct even though all of its fields (should) be cloneable.

should this structure definition be moved to a new smithy interface? (or control-interface?)

Provider archive is a completely separate crate and isn't a serialization struct it's an api

authors: autodidaddict stevelr


text:
Replace manual subscriptions with Consumer Supervisors (actors)

Today actors subscribe to their RPC topic manually, e.g. {:ok, subscription} = Gnat.sub(:lattice_nats, self(), topic, queue_group: topic). This is fine in testing, but if that subscription were to die or become unstable, there's nothing to fix it. By switching to a consumer supervisor, the subscription can be maintained more durably.

This has been done for a while! :D

authors: autodidaddict brooksmtownsend

repo: wasmCloud/wasmcloud-otp


text:
Update MOST-ANNOYING-COOKIE-BANNER.md

Description

Describe your PR! If it fixes specific issue, mention it with "Fixes # (issue)".

Contributor Checklist

Make sure to do the following steps if they are applicable to your PR:

[ ] Update e2e tests: If you changed the /template/app, then make sure to do any neccessary updates to /template/e2e-tests also.
[ ] Update demo app: If you changed the /template/app, then make sure to do any neccessary updates to /opensaas-sh/app_diff also. Check /opensaas-sh/README.md for details.
[ ] Update docs: If needed, update the /opensaas-sh/blog/src/content/docs.

@vincanger I can't seem to add the hackathon label to this for some reason, sorry!

repo: wasp-lang/open-saas


text:
Fix/husky on windows

Description
Branch to fix husky on windows and speed up dev on the platform
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Chore: cleanup/renaming, etc
[ ] RFC

Notes

I can't test because I don't have a Windows machine. But feel free to merge if it works on yours.

Cancelled for now

authors: EstebanDalelR baristaGeek

repo: watermelontools/wm-extension


text:
Cookie API

Currently, only Browser#clear_cookies is implemented. There has been some discussion about the cookie API on the wtr-development list, but no conclusion.
The API needs to be implementable cross-browser, so taking some clues from WebDriver's cookie handling is probably wise (since it's already cross-browser).
watirspec is also missing specs for this.

We should get this fixed. I think something like  this was suggested once, and I quite like it:
browser.cookies.clear
browser.cookies.add 'foo', 'bar', :path => "/", :expires => 10.days.from_now, :secure => true
browser.cookies.delete 'foo'
browser.cookies.to_hash

Thoughts @jarmo, @alisterscott, @zeljkofilipin?

I did not work with cookies a lot, but the API looks good to me.

Seems good to me if 10.days.from_now is not going to be part of that API, but it's coming from ActiveSupport or any other 3rd party library.

+1 Looks great to me

OK, then that's what we'll do. Except cookies.to_hash should of course really be cookies.to_a

authors: alisterscott jarib jarmo zeljkofilipin

repo: watir/watir-webdriver


text:
cannot access elements in iframes when after_hook accesses the DOM

Meta -
Watir Version: 6.16.5
Selenium Version: 3.142.7
Browser Version: Chrome 79.0.3945.79
Browser Driver Version: Chromedriver 79.03945.36
OS Version: Linux Mint 19.1
Expected Behavior -
calls to elements in an iframe work even if an after_hook is accessing the DOM
Actual Behavior -
cannot find elements in an iframe
Steps to reproduce -
slightly modifying the test here  passes successfully when the hook accesses the browser's title
    it 'runs after_hooks after FramedDriver#switch!' do
      browser.goto(WatirSpec.url_for('iframes.html'))
      @page_after_hook = proc { @yield = browser.title == 'Iframes' }
      browser.after_hooks.add @page_after_hook

      expect(browser.h1.text).to eq 'Iframes'
      expect(browser.iframe.element(css: '#senderElement')).to exist

      expect(@yield).to be true
    end

but when changing the hook to look at an element in the DOM, we get an error that it cannot find the element in the iframe
    it 'runs after_hooks after FramedDriver#switch!' do
      browser.goto(WatirSpec.url_for('iframes.html'))
      @page_after_hook = proc { @yield = browser.h1.text == 'Iframes' }
      browser.after_hooks.add @page_after_hook

      expect(browser.h1.text).to eq 'Iframes'
      expect(browser.iframe.element(css: '#senderElement')).to exist

      expect(@yield).to be true
    end

     Failure/Error: expect(browser.iframe.element(css: '#senderElement')).to exist
       expected #<Watir::HTMLElement: located: false; {:tag_name=>"iframe"} --> {:css=>"#senderElement"}> to exist

in browser.ensure_context, we flip to the default context and run the hook
i went ahead and took a quick pass at having it then flip back to the frame when the after_hook completed
i exposed a new property on the Browser called current_frame and set that in the iframe code
    def switch!
      @browser.current_frame = @element # <---- this is new
      @driver.switch_to.frame @element
      @browser.default_context = false
      @browser.after_hooks.run
    rescue Selenium::WebDriver::Error::NoSuchFrameError => e
      raise UnknownFrameException, e.message
    end

and then when we aren't in the default context, we flip back to the frame
    def ensure_context
      return if @default_context

      driver.switch_to.default_content
      @default_context = true
      after_hooks.run
      driver.switch_to.frame @current_frame
      @default_context = false
    end

it looks like it got my test to pass, but if i attempt to make a second call to an element inside the iframe, the second call fails :cry:
i'm also about 99% sure that this behavior is now actually running the checker in both contexts - the main frame and the iframe - as a side effect, it breaks a handful of tests :sob:
I'm not sure if this is the change we are looking for... :thinking:

i can get moving again if i revert https://github.com/watir/watir/pull/837, but not sure that's the change we're looking for either

So, just wanted to update this since I didn't work on a fix for the 6.17 release...
I really want to provide an easy way to specify which afterhooks get run where, but that's out of scope for a bit still...
Reverting #837 might make the most sense and then update nokogiri to monkeypatch the class.

authors: MatthewMazaika titusfortner

repo: watir/watir


text:
Reduce rubocop offenses

The aim of the PR is to bump rubocop version and to reduce to minimum rubocop offenses.

Looks like this broke the unit tests? Can you double check? Thanks.

@titusfortner I've:

fix one selector
left the offense about ENV['SAUCE_USERNAME']

Style/FetchEnvVar: Use ENV.fetch('SAUCE_USERNAME') or ENV.fetch('SAUCE_USERNAME', nil) instead of ENV['SAUCE_USERNAME']

so now all unit tests passed.
Now:

229 files inspected, 11 offenses detected, 7 offenses autocorrectable

but we should discuss detected offenses one by one, as well as .rubocop_todo.yml and they could be fixed in another PR.
Could you please review that PR again.
Thank you in advance!

merged, thanks - 255caf9b09414bcebb5b92ad57401363530fdebe

authors: ivodimitrov titusfortner


text:
phrase "I do not understand." from unknown source

in Watson Conversation, I get the response “I do not understand.” I have scoured the stack, and do not see this phrase anywhere:

my app
node_modules
botkit
botkit-middleware-watson
my Dialog config JSON

I already have an anything_else node, with different phrases.
Sometimes the phrase comes up, and then the bot moves to the next step.
In fact, a series of nonsense questions in the "Test it Out" feature at https://www.ibmwatsonconversation.com I get the expected response.
Can someone identify the source or how to debug/find it?

Example debug output:
Hears:	eeeeeep opppp Orkk AH-HA!
189b7a08-2d24-4ddc-9327-75d8eb38a930
exited:	true
stack:	1
turn:	336
info: >   [End]  0  Conversation with  W3NKCD3GX in D5844SSKA
info: [End]  0  Task for  W3NKCD3GX in D5844SSKA

Two interesting clues to add:

the "I do not understand." reply kept occurring, even after the bot had exited due to an error
I went through the Cloudant records and deleted

a number of users (who were team members but not conversing with the bot, i think)
users/ME**** - the test Slack user attached to my own Slack

After the data clear-out, the bot began responding as expected. I saved the records for my user as JSON, in case they are of diagnostic value.

@mitchmason ^^

@monte-hayward where you able to fix this?

closing this due to inactivity

authors: germanattanasio monte-hayward


text:
android.media.AudioTrack: getMinBufferSize(): 1948401012 Hz is not a supported sample rate.

Hi. I've got this error when call synthesize method.
I found someone in IBMDeveloper site got the same error but no solution yet.
https://developer.ibm.com/answers/questions/230127/android-text-to-speech-returns-2-buffer-size.html
LOGCAT :

07-08 21:33:04.060 28864-28864/ D/TextToSpeech: synthesize called: https://stream.watsonplatform.net/text-to-speech/api/v1/synthesize
07-08 21:33:04.060 28864-28864/ I/com.ibm.watson.developer_cloud.android.text_to_speech.v1.TTSUtility: Start requesting TTS... (audio/wav)
07-08 21:33:04.070 28864-29059/ D/com.ibm.watson.developer_cloud.android.text_to_speech.v1.TTSUtility: using basic authentication
07-08 21:33:06.280 28864-29059/ E/android.media.AudioTrack: getMinBufferSize(): 1948401012 Hz is not a supported sample rate.
07-08 21:33:06.280 28864-29059/ W/System.err: java.lang.IllegalArgumentException: 1948401012Hz is not a supported sample rate.
07-08 21:33:06.290 28864-29059/ W/System.err:     at android.media.AudioTrack.audioParamCheck(AudioTrack.java:380)
07-08 21:33:06.290 28864-29059/ W/System.err:     at android.media.AudioTrack.(AudioTrack.java:315)
07-08 21:33:06.290 28864-29059/ W/System.err:     at android.media.AudioTrack.(AudioTrack.java:265)
07-08 21:33:06.290 28864-29059/ W/System.err:     at com.ibm.watson.developer_cloud.android.text_to_speech.v1.TTSUtility.initPlayer(TTSUtility.java:129)
07-08 21:33:06.300 28864-29059/ W/System.err:     at com.ibm.watson.developer_cloud.android.text_to_speech.v1.TTSUtility.access$800(TTSUtility.java:52)
07-08 21:33:06.300 28864-29059/ W/System.err:     at com.ibm.watson.developer_cloud.android.text_to_speech.v1.TTSUtility$TTSThread.run(TTSUtility.java:220)
07-08 21:33:06.300 28864-29059/ I/com.ibm.watson.developer_cloud.android.text_to_speech.v1.TTSUtility: Stopping audioTrack...

Codes:
protected void procTTS(View view) throws JSONException {
        textAnswer = (TextView) findViewById(R.id.txtAnswer);
        String ttsText=textAnswer.getText().toString();
        TextToSpeech.sharedInstance().synthesize(ttsText);
    }
private boolean initTTS() {
        String username = getString(R.string.TTSUsername);
        String password = getString(R.string.TTSPassword);
        String serviceURL = "https://stream.watsonplatform.net/text-to-speech/api";
        TextToSpeech.sharedInstance().initWithContext(getHost(serviceURL));
        TextToSpeech.sharedInstance().setCredentials(username, password);
        TextToSpeech.sharedInstance().setVoice(getString(R.string.voiceDefault));
        return true;
    }

How large is the text you are trying to synthesize? I think this just happens if you synthesize a large text.

Just one sentence or few words that I tried.

Got this error too.
Just synthesize("Hello");

Any luck with this? I am experiencing the same problem with text to speech in one of my projects. The example application provided as part of the Android Speech SDK works fine. However, when I copy paste the same code under my project, it does not work. I even started a new project from scratch, using the same target and min SDK versions as in the Android Speech SDK example app. But that does not work either. I am running the code on a Nexus 6 emulator, with very short text messages.
I have noticed that using the  Android Speech SDK example app, AudioTrack is instantiated by TTSUtility with the following parameters: new AudioTrack(3, 22050, 4, 2, 2064, 1). However, from my code it is bing instantiated with: new AudioTrack(3, 1948401012, 4, 2, -2, 1).
Any idea?

I even started a new project from scratch, using the same target and min SDK versions as in the Android Speech SDK example app. But that does not work either.

@ylassoued Can you share this sample app?

Problem solved. This is was an error on my side... Somehow my credentials which are specified in a config file got messed up. As error messages from the Watson TTS service are not dealt with by the Speech Android API, TTSUtility was attempting to read the server response (error message) as WAV data... I figured this out after I used the latest Watson Java SDK 3.4.0, which threw an exception upon the authentication failure...

Glad to know!
I have experienced weird issues somewhere else and then realized credentials were incorrect..  😢

Hi Guys, I am also getting the same exception while trying for Text-to-Speech.
Below is the log:
D/OkHttp: --> POST https://stream.watsonplatform.net/text-to-speech/api/v1/synthesize?voice=en-US_MichaelVoice http/1.1 (13-byte body)
D/OkHttp: <-- 200 OK https://stream.watsonplatform.net/text-to-speech/api/v1/synthesize?voice=en-US_MichaelVoice (417ms, unknown-length body)
E/android.media.AudioTrack: getMinBufferSize(): 1987804923 Hz is not a supported sample rate.
I am using the service credentials for the Text-to-Speech API as given on the bluemix site.

Can anyone suggest where am I going wrong? I am using the Android SDK along with the Java SDK.

authors: TThana YoungCholKim germanattanasio ihuman15 nacho4d ylassoued


text:
Updating validation signature

Fixes #37 .
Todo:

[ ] update documentation
[x] update Literal import for python versions < 3.8 (see https://github.com/wayfair-incubator/columbo/pull/88/checks?check_run_id=1858256105)
[x] retain support for legacy validator
[x] update new ValidationFailure to require an error string

@jamescurtin and @plannigan : I've made some updates to columbo to address #37 . When you get a chance, could you review the changes I've made? I still need to update the documentation, but want to make sure my updates are solid before updating documentation. Thanks!

repo: wayfair-incubator/columbo


text:
[WIP] Search lyric and select manually

fix #9
thx @taoky 's work

It's unfinished yet. I think this PR should be changed from ready to a draft now.

repo: waylyrics/waylyrics


text:
[BUG] Problem when configuring the password of the kibanaserver user

issue related: https://github.com/wazuh/wazuh-packages/issues/3056
In the installation tests using the 4.9.0 installation assistant, a problem was detected when changing the password of the kibanaserver user. Analyzing the code of the Wazuh password tool, we do not see any differential treatment for the kibanaserver user, that is, the method of creating the password as well as the hash is the same for all users, so at the code level, we do not see anything that generates this behavior.
It is strange that if the password of the kibanaserver user is then individually changed using the Wazuh password tool, the change is applied.
We carry out different tests to validate, in the first instance, at the code level there are no differences between the code of the Wazuh password tool in version 4.8.1 and version 4.9.0 in the methods used to change the password of this user.
We tested installing 4.9.0 using wazuh-install.sh from 4.8.1, and the installation gave the same error. https://github.com/wazuh/wazuh-packages/issues/3056#issuecomment-2250916258
I also installed version 4.8.1 using the wazuh-install.sh script from 4.8.1 and the installation ran successfully, which leads me to think that perhaps we should check the Wazuh indexer package to see if something could be causing this behavior. https://github.com/wazuh/wazuh-packages/issues/3056#issuecomment-2250953450

This issue was initially reported here:

https://github.com/wazuh/wazuh/issues/24847#issuecomment-2243263492

While running tests on a clean VM I see that with a single node setup, the kibanaserver password works ok:
root@kibanaserver-error:~# curl -sO https://packages.wazuh.com/4.8/wazuh-install.sh

curl -sO https://packages.wazuh.com/4.8/config.yml
root@kibanaserver-error:~# vim config.yml
root@kibanaserver-error:~# bash wazuh-install.sh --generate-config-files
26/07/2024 14:01:27 INFO: Starting Wazuh installation assistant. Wazuh version: 4.8.1
26/07/2024 14:01:27 INFO: Verbose logging redirected to /var/log/wazuh-install.log
26/07/2024 14:01:28 INFO: Verifying that your system meets the recommended minimum hardware requirements.
26/07/2024 14:01:31 INFO: --- Dependencies ----
26/07/2024 14:01:31 INFO: Installing gawk.
26/07/2024 14:01:34 INFO: Installing lsof.
26/07/2024 14:01:36 INFO: --- Configuration files ---
26/07/2024 14:01:36 INFO: Generating configuration files.
26/07/2024 14:01:36 INFO: Generating the root certificate.
26/07/2024 14:01:36 INFO: Generating Admin certificates.
26/07/2024 14:01:36 INFO: Generating Wazuh indexer certificates.
26/07/2024 14:01:36 INFO: Generating Filebeat certificates.
26/07/2024 14:01:36 INFO: Generating Wazuh dashboard certificates.
26/07/2024 14:01:37 INFO: Created wazuh-install-files.tar. It contains the Wazuh cluster key, certificates, and passwords necessary for installation.
26/07/2024 14:01:37 INFO: --- Dependencies ----
26/07/2024 14:01:37 INFO: Removing gawk.
26/07/2024 14:01:37 INFO: Removing lsof.

root@kibanaserver-error:~# bash wazuh-install.sh --wazuh-indexer node-1
26/07/2024 14:01:41 INFO: Starting Wazuh installation assistant. Wazuh version: 4.8.1
26/07/2024 14:01:41 INFO: Verbose logging redirected to /var/log/wazuh-install.log
26/07/2024 14:01:42 INFO: Verifying that your system meets the recommended minimum hardware requirements.
26/07/2024 14:01:46 INFO: --- Dependencies ----
26/07/2024 14:01:46 INFO: Installing gawk.
26/07/2024 14:01:46 INFO: Installing lsof.
26/07/2024 14:01:49 INFO: --- Dependencies ----
26/07/2024 14:01:49 INFO: Installing apt-transport-https.
26/07/2024 14:01:50 INFO: Installing software-properties-common.
26/07/2024 14:01:59 INFO: Installing gnupg.
26/07/2024 14:02:01 INFO: Wazuh repository added.
26/07/2024 14:02:01 INFO: --- Wazuh indexer ---
26/07/2024 14:02:01 INFO: Starting Wazuh indexer installation.
26/07/2024 14:03:29 INFO: Wazuh indexer installation finished.
26/07/2024 14:03:29 INFO: Wazuh indexer post-install configuration finished.
26/07/2024 14:03:29 INFO: Starting service wazuh-indexer.
26/07/2024 14:03:39 INFO: wazuh-indexer service started.
26/07/2024 14:03:39 INFO: Initializing Wazuh indexer cluster security settings.
26/07/2024 14:03:40 INFO: Wazuh indexer cluster initialized.
26/07/2024 14:03:40 INFO: --- Dependencies ----
26/07/2024 14:03:40 INFO: Removing gawk.
26/07/2024 14:03:41 INFO: Removing lsof.
26/07/2024 14:03:42 INFO: Installation finished.

root@kibanaserver-error:~# bash wazuh-install.sh --start-cluster
26/07/2024 14:09:34 INFO: Starting Wazuh installation assistant. Wazuh version: 4.8.1
26/07/2024 14:09:34 INFO: Verbose logging redirected to /var/log/wazuh-install.log
26/07/2024 14:09:35 INFO: Verifying that your system meets the recommended minimum hardware requirements.
26/07/2024 14:09:38 INFO: --- Dependencies ----
26/07/2024 14:09:38 INFO: Installing gawk.
26/07/2024 14:09:38 INFO: Installing lsof.
26/07/2024 14:09:46 INFO: Wazuh indexer cluster security configuration initialized.
26/07/2024 14:10:12 INFO: Updating the internal users.
26/07/2024 14:10:14 INFO: A backup of the internal users has been saved in the /etc/wazuh-indexer/internalusers-backup folder.
26/07/2024 14:10:19 INFO: --- Dependencies ----
26/07/2024 14:10:19 INFO: Removing gawk.
26/07/2024 14:10:20 INFO: Removing lsof.
26/07/2024 14:10:20 INFO: Wazuh indexer cluster started.

root@kibanaserver-error:~# cat wazuh-install-files/wazuh-passwords.txt
# Admin user for the web user interface and Wazuh indexer. Use this user to log in to Wazuh dashboard
  indexer_username: 'admin'
  indexer_password: 'Y4YliNbZ3CcWOu+Ppq48bLxo5gY6d0.r'

# Wazuh dashboard user for establishing the connection with Wazuh indexer
  indexer_username: 'kibanaserver'
  indexer_password: 'X3*4RD.weQ87y3H2qH3NhpkII3WG.3CK'

# Regular Dashboard user, only has read permissions to all indices and all permissions on the .kibana index
  indexer_username: 'kibanaro'
  indexer_password: 'oEyiCGtl4TUjhS0.GeamHQ?443Ho3lmP'

# Filebeat user for CRUD operations on Wazuh indices
  indexer_username: 'logstash'
  indexer_password: 'HtqM9KBHejTZS*kC?kTP9R*PfNv*Q2Qg'

# User with READ access to all indices
  indexer_username: 'readall'
  indexer_password: 'aY+x2fL+FdjtCeYFoO7ojAxkD?OywS4T'

# User with permissions to perform snapshot and restore operations
  indexer_username: 'snapshotrestore'
  indexer_password: '1ByWM9g7FIQHk6?WhmN5UiqRvI4OOA75'

# Password for wazuh API user
  api_username: 'wazuh'
  api_password: 'AvhiVZ.c?+unASiMeSNN3sfPgyC2PMDS'

# Password for wazuh-wui API user
  api_username: 'wazuh-wui'
  api_password: 'ep?L8og06UlokxFE4ynA+TemvIELlylY'

root@kibanaserver-error:~# curl -ku admin:'Y4YliNbZ3CcWOu+Ppq48bLxo5gY6d0.r' https://localhost:9200
{
  "name" : "node-1",
  "cluster_name" : "wazuh-indexer-cluster",
  "cluster_uuid" : "ZfkLf3KZSfiSqiQiMSFG1Q",
  "version" : {
    "number" : "7.10.2",
    "build_type" : "rpm",
    "build_hash" : "eee49cb340edc6c4d489bcd9324dda571fc8dc03",
    "build_date" : "2023-09-20T23:54:29.889267151Z",
    "build_snapshot" : false,
    "lucene_version" : "9.7.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

root@kibanaserver-error:~# curl -ku kibanaserver:'X3*4RD.weQ87y3H2qH3NhpkII3WG.3CK' https://localhost:9200
{
  "name" : "node-1",
  "cluster_name" : "wazuh-indexer-cluster",
  "cluster_uuid" : "ZfkLf3KZSfiSqiQiMSFG1Q",
  "version" : {
    "number" : "7.10.2",
    "build_type" : "rpm",
    "build_hash" : "eee49cb340edc6c4d489bcd9324dda571fc8dc03",
    "build_date" : "2023-09-20T23:54:29.889267151Z",
    "build_snapshot" : false,
    "lucene_version" : "9.7.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

It seems the problem affects all users but the admin one:
26/07/2024 14:37:28 INFO: Starting Wazuh installation assistant. Wazuh version: 4.9.0
26/07/2024 14:37:28 INFO: Verbose logging redirected to /var/log/wazuh-install.log
26/07/2024 14:37:31 INFO: --- Dependencies ----
26/07/2024 14:37:31 INFO: Installing gawk.
26/07/2024 14:37:34 INFO: Verifying that your system meets the recommended minimum hardware requirements.
26/07/2024 14:37:37 INFO: --- Configuration files ---
26/07/2024 14:37:37 INFO: Generating configuration files.
26/07/2024 14:37:38 INFO: Generating the root certificate.
26/07/2024 14:37:38 INFO: Generating Admin certificates.
26/07/2024 14:37:38 INFO: Generating Wazuh indexer certificates.
26/07/2024 14:37:38 INFO: Generating Filebeat certificates.
26/07/2024 14:37:38 INFO: Generating Wazuh dashboard certificates.
26/07/2024 14:37:38 INFO: Created wazuh-install-files.tar. It contains the Wazuh cluster key, certificates, and passwords necessary for installation.
26/07/2024 14:37:38 INFO: --- Dependencies ----
26/07/2024 14:37:38 INFO: Removing gawk.
26/07/2024 14:37:39 INFO: Starting Wazuh installation assistant. Wazuh version: 4.9.0
26/07/2024 14:37:39 INFO: Verbose logging redirected to /var/log/wazuh-install.log
26/07/2024 14:37:42 INFO: --- Dependencies ----
26/07/2024 14:37:42 INFO: Installing gawk.
26/07/2024 14:37:43 INFO: Verifying that your system meets the recommended minimum hardware requirements.
26/07/2024 14:37:46 INFO: --- Dependencies ----
26/07/2024 14:37:46 INFO: Installing lsof.
26/07/2024 14:37:53 INFO: --- Dependencies ----
26/07/2024 14:37:53 INFO: Installing gnupg.
26/07/2024 14:37:56 INFO: Installing apt-transport-https.
26/07/2024 14:38:02 INFO: Wazuh development repository added.
26/07/2024 14:38:02 INFO: --- Wazuh indexer ---
26/07/2024 14:38:02 INFO: Starting Wazuh indexer installation.
26/07/2024 14:39:20 INFO: Wazuh indexer installation finished.
26/07/2024 14:39:20 INFO: Wazuh indexer post-install configuration finished.
26/07/2024 14:39:20 INFO: Starting service wazuh-indexer.
26/07/2024 14:39:28 INFO: wazuh-indexer service started.
26/07/2024 14:39:28 INFO: Initializing Wazuh indexer cluster security settings.
26/07/2024 14:39:29 INFO: Wazuh indexer cluster initialized.
26/07/2024 14:39:29 INFO: --- Dependencies ----
26/07/2024 14:39:29 INFO: Removing gawk.
26/07/2024 14:39:30 INFO: Removing lsof.
26/07/2024 14:39:30 INFO: Installation finished.
26/07/2024 14:39:30 INFO: Starting Wazuh installation assistant. Wazuh version: 4.9.0
26/07/2024 14:39:30 INFO: Verbose logging redirected to /var/log/wazuh-install.log
26/07/2024 14:39:33 INFO: --- Dependencies ----
26/07/2024 14:39:33 INFO: Installing gawk.
26/07/2024 14:39:35 INFO: Verifying that your system meets the recommended minimum hardware requirements.
26/07/2024 14:39:39 INFO: Wazuh indexer cluster security configuration initialized.
26/07/2024 14:40:11 INFO: Updating the internal users.
26/07/2024 14:40:12 INFO: A backup of the internal users has been saved in the /etc/wazuh-indexer/internalusers-backup folder.
26/07/2024 14:40:18 INFO: --- Dependencies ----
26/07/2024 14:40:18 INFO: Removing gawk.
26/07/2024 14:40:18 INFO: Wazuh indexer cluster started.
root@kibanaserver-error:~# view confi^C
root@kibanaserver-error:~# ls
script.sh  wazuh-install-files  wazuh-install-files.tar  wazuh-install.sh
root@kibanaserver-error:~# vim script.sh
root@kibanaserver-error:~# cat wazuh-install-files
wazuh-install-files/     wazuh-install-files.tar
root@kibanaserver-error:~# cat wazuh-install-files/wazuh-^C
root@kibanaserver-error:~# cat wazuh-install-files/wazuh-passwords.txt
# Admin user for the web user interface and Wazuh indexer. Use this user to log in to Wazuh dashboard
  indexer_username: 'admin'
  indexer_password: '9aiiCCRVM*zGMFgoP0i3fe42GSh3Fme.'

# Wazuh dashboard user for establishing the connection with Wazuh indexer
  indexer_username: 'kibanaserver'
  indexer_password: 'V?ZsT5M1DKsq7QaWVM3WsLBWuUd.oxDG'

# Regular Dashboard user, only has read permissions to all indices and all permissions on the .kibana index
  indexer_username: 'kibanaro'
  indexer_password: 'iiED5olB8IMcu9ZSrizstsN*7*9jpkdG'

# Filebeat user for CRUD operations on Wazuh indices
  indexer_username: 'logstash'
  indexer_password: 'JfDbMlymk04d.ZE6H3oYC1UdYFXVwG77'

# User with READ access to all indices
  indexer_username: 'readall'
  indexer_password: 'OD4VUJEM.wqA.HpVhesi0HoTDVLlPuNL'

# User with permissions to perform snapshot and restore operations
  indexer_username: 'snapshotrestore'
  indexer_password: 'GqdY6gfEnVxL7Z8eT0y+yW.+cWk4GsTe'

# Password for wazuh API user
  api_username: 'wazuh'
  api_password: 'h*5HRH?Y*sM.x0z69AQiVRs9*vbi4AIZ'

# Password for wazuh-wui API user
  api_username: 'wazuh-wui'
  api_password: '5rC9JbTR5m9yOIEV.eIaDMV1DQmNHyiz'

root@kibanaserver-error:~# curl -ku admin:'9aiiCCRVM*zGMFgoP0i3fe42GSh3Fme.' https://localhost:9200
{
  "name" : "node-1",
  "cluster_name" : "wazuh-indexer-cluster",
  "cluster_uuid" : "giRhmpf6SKKBsOqK0BfQEQ",
  "version" : {
    "number" : "7.10.2",
    "build_type" : "deb",
    "build_hash" : "2c952aba7735bee5f4b0bb9cfc821d68ffbdd636",
    "build_date" : "2024-07-19T16:32:15.451255Z",
    "build_snapshot" : false,
    "lucene_version" : "9.10.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}
root@kibanaserver-error:~# curl -ku kibanaserver:'V?ZsT5M1DKsq7QaWVM3WsLBWuUd.oxDG' https://localhost:9200
root@kibanaserver-error:~# curl -ku kibanaro:'iiED5olB8IMcu9ZSrizstsN*7*9jpkdG' https://localhost:9200
root@kibanaserver-error:~# curl -ku logstash:'JfDbMlymk04d.ZE6H3oYC1UdYFXVwG77' https://localhost:9200
root@kibanaserver-error:~# curl -ku readall:'OD4VUJEM.wqA.HpVhesi0HoTDVLlPuNL' https://localhost:9200
root@kibanaserver-error:~# curl -ku snapshotrestore:'GqdY6gfEnVxL7Z8eT0y+yW.+cWk4GsTe' https://localhost:9200

I'm trying to run the securityadmin.sh script manually with the internal_users.yml file as created by the wazuh-install.sh script, without success:
root@kibanaserver-error:~# cat script.sh
#!/bin/bash

certsdir="/etc/wazuh-indexer/certs"
capem="${certsdir}/root-ca.pem"
adminpem="${certsdir}/admin.pem"
adminkey="${certsdir}/admin-key.pem"
IP="127.0.0.1"
debug="/root/output.log"
JAVA_HOME="/usr/share/wazuh-indexer/jdk"

eval "JAVA_HOME=${JAVA_HOME} OPENSEARCH_CONF_DIR=/etc/wazuh-indexer /usr/share/wazuh-indexer/plugins/opensearch-security/tools/securityadmin.sh -f /etc/wazuh-indexer/opensearch-security/internal_users.yml -t internalusers -p 9200 -nhnv -cacert ${capem} -cert ${adminpem} -key ${adminkey} -icl -h ${IP} ${debug}"

root@kibanaserver-error:~# ./script.sh
**************************************************************************
** This tool will be deprecated in the next major release of OpenSearch **
** https://github.com/opensearch-project/security/issues/1755           **
**************************************************************************
Security Admin v7
Will connect to 127.0.0.1:9200 ... done
Connected as "CN=admin,OU=Wazuh,O=Wazuh,L=California,C=US"
OpenSearch Version: 2.13.0
Contacting opensearch cluster 'opensearch' and wait for YELLOW clusterstate ...
Clustername: wazuh-indexer-cluster
Clusterstate: GREEN
Number of nodes: 1
Number of data nodes: 1
.opendistro_security index already exists, so we do not need to create one.
Populate config from /root
Force type: internalusers
Will update '/internalusers' with /etc/wazuh-indexer/opensearch-security/internal_users.yml
   SUCC: Configuration for 'internalusers' created or updated
SUCC: Expected 1 config types for node {"updated_config_types":["internalusers"],"updated_config_size":1,"message":null} is 1 (["internalusers"]) due to: null
Done with success

root@kibanaserver-error:~# curl -ku kibanaserver:'V?ZsT5M1DKsq7QaWVM3WsLBWuUd.oxDG' https://localhost:9200
root@kibanaserver-error:~#

I tried generating a new hash for the kibanaserver password with:
JAVA_HOME="/usr/share/wazuh-indexer/jdk" /usr/share/wazuh-indexer/plugins/opensearch-security/tools/hash.sh -p V?ZsT5M1DKsq7QaWVM3WsLBWuUd.oxDG
**************************************************************************
** This tool will be deprecated in the next major release of OpenSearch **
** https://github.com/opensearch-project/security/issues/1755           **
**************************************************************************
$2y$12$Yz94o8jwKpd6MY17g7/23OSjFx/l3u36dDltfvekR60OM8X1wlIGa

And then updated the hash in internal_users.yml:
root@kibanaserver-error:~# grep 'kibanaserver:' /etc/wazuh-indexer/opensearch-security/internal_users.yml -A4
kibanaserver:
  #  hash: $2y$12$0RTZr4sxcl8n2rqLl0zP6.ImtKphWurUGED1QphE8xU7kdYLQhjwO
  hash: $2y$12$Yz94o8jwKpd6MY17g7/23OSjFx/l3u36dDltfvekR60OM8X1wlIGa
  reserved: true
  description: "Demo OpenSearch Dashboards user"

And rerun securityadmin.sh with the same command the wazuh-install.sh script uses:
**************************************************************************
** This tool will be deprecated in the next major release of OpenSearch **
** https://github.com/opensearch-project/security/issues/1755           **
**************************************************************************
Security Admin v7
Will connect to 127.0.0.1:9200 ... done
Connected as "CN=admin,OU=Wazuh,O=Wazuh,L=California,C=US"
OpenSearch Version: 2.13.0
Diagnostic trace written to: /root/securityadmin_diag_trace_2024-Jul-26_15-55-17.txt
Contacting opensearch cluster 'opensearch' and wait for YELLOW clusterstate ...
Clustername: wazuh-indexer-cluster
Clusterstate: GREEN
Number of nodes: 1
Number of data nodes: 1
.opendistro_security index already exists, so we do not need to create one.
Populate config from /root
Force type: internalusers
Will update '/internalusers' with /etc/wazuh-indexer/opensearch-security/internal_users.yml
   SUCC: Configuration for 'internalusers' created or updated
SUCC: Expected 1 config types for node {"updated_config_types":["internalusers"],"updated_config_size":1,"message":null} is 1 (["internalusers"]) due to: null
Done with success

This seems to work as well:
root@kibanaserver-error:~# curl -ku kibanaserver:'V?ZsT5M1DKsq7QaWVM3WsLBWuUd.oxDG' https://localhost:9200
{
  "name" : "node-1",
  "cluster_name" : "wazuh-indexer-cluster",
  "cluster_uuid" : "giRhmpf6SKKBsOqK0BfQEQ",
  "version" : {
    "number" : "7.10.2",
    "build_type" : "deb",
    "build_hash" : "2c952aba7735bee5f4b0bb9cfc821d68ffbdd636",
    "build_date" : "2024-07-19T16:32:15.451255Z",
    "build_snapshot" : false,
    "lucene_version" : "9.10.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

In a call with @c-bordon we detected the presence of a new internal user in internal_users.yml, namely anomalyadmin.
Removing the anomalyadmin entry off internal_users.yml before running wazuh-install.sh --start-cluster gets the kibanaserver working again.
root@kibanaserver-error:~# bash wazuh-install.sh --wazuh-indexer node-1
30/07/2024 13:32:47 INFO: Starting Wazuh installation assistant. Wazuh version: 4.9.0
30/07/2024 13:32:47 INFO: Verbose logging redirected to /var/log/wazuh-install.log
30/07/2024 13:32:50 INFO: --- Dependencies ----
30/07/2024 13:32:50 INFO: Installing gawk.
30/07/2024 13:32:52 INFO: Verifying that your system meets the recommended minimum hardware requirements.
30/07/2024 13:32:55 INFO: --- Dependencies ----
30/07/2024 13:32:55 INFO: Installing lsof.
30/07/2024 13:33:02 INFO: Wazuh development repository added.
30/07/2024 13:33:02 INFO: --- Wazuh indexer ---
30/07/2024 13:33:02 INFO: Starting Wazuh indexer installation.
30/07/2024 13:33:08 INFO: Wazuh indexer installation finished.
30/07/2024 13:33:08 INFO: Wazuh indexer post-install configuration finished.
30/07/2024 13:33:08 INFO: Starting service wazuh-indexer.
30/07/2024 13:33:17 INFO: wazuh-indexer service started.
30/07/2024 13:33:17 INFO: Initializing Wazuh indexer cluster security settings.
30/07/2024 13:33:18 INFO: Wazuh indexer cluster initialized.
30/07/2024 13:33:18 INFO: --- Dependencies ----
30/07/2024 13:33:18 INFO: Removing gawk.
30/07/2024 13:33:18 INFO: Removing lsof.
30/07/2024 13:33:19 INFO: Installation finished.

### HERE WE ARE REMOVING the anomalyadmin entry

root@kibanaserver-error:~# vim /etc/wazuh-indexer/opensearch-security/internal_users.yml

###

root@kibanaserver-error:~# bash wazuh-install.sh --start-cluster
30/07/2024 13:33:35 INFO: Starting Wazuh installation assistant. Wazuh version: 4.9.0
30/07/2024 13:33:35 INFO: Verbose logging redirected to /var/log/wazuh-install.log
30/07/2024 13:33:38 INFO: --- Dependencies ----
30/07/2024 13:33:38 INFO: Installing gawk.
30/07/2024 13:33:40 INFO: Verifying that your system meets the recommended minimum hardware requirements.
30/07/2024 13:33:45 INFO: Wazuh indexer cluster security configuration initialized.
30/07/2024 13:34:26 INFO: Updating the internal users.
30/07/2024 13:34:28 INFO: A backup of the internal users has been saved in the /etc/wazuh-indexer/internalusers-backup folder.
30/07/2024 13:34:33 INFO: --- Dependencies ----
30/07/2024 13:34:33 INFO: Removing gawk.
30/07/2024 13:34:34 INFO: Wazuh indexer cluster started.

root@kibanaserver-error:~# curl -ku kibanaserver:'V?ZsT5M1DKsq7QaWVM3WsLBWuUd.oxDG' https://localhost:9200
{
  "name" : "node-1",
  "cluster_name" : "wazuh-indexer-cluster",
  "cluster_uuid" : "AV8m9O56TxqYFd6whxyQSw",
  "version" : {
    "number" : "7.10.2",
    "build_type" : "deb",
    "build_hash" : "2c952aba7735bee5f4b0bb9cfc821d68ffbdd636",
    "build_date" : "2024-07-19T16:32:15.451255Z",
    "build_snapshot" : false,
    "lucene_version" : "9.10.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

Closing this, as the issue will be handled over at:

https://github.com/wazuh/wazuh-packages/issues/3056

authors: c-bordon f-galland

repo: wazuh/wazuh-indexer


text:
x-axsis Ticks problem

Hi,
Is there any way to Hide auto-generate  X-axsis's tick,
just show the x-axsis whick in my Xvalues[]?
thanks.

Yeah, but what if you want to remove them completely as he asked? If I set Ticks: nil, it just uses the default ticks.

repo: wcharczuk/go-chart


text:
RC tagging process doesn't follow semver2, confuses go modules

Describe the bug
Our RCs are tagged v1.2.3-rc4. However, rc4 isn't a semver identifier for "4th rc", it's a identifier for "pre-release of type rc4". This means the RC version is compared lexically, not numerically, which in turn means that rc10 is older than rc9 because 1 comes before 9. This makes go get downgrade to the wrong RC - I'm unsure on whether npm does.
Suggestions to fix are either v1.2.3-rc.4 (the bits after the dash are split by . and compared one by one) or v1.2.3-rc+4 (pre-release "rc", build 4) - both compare accurately, though I've tested neither.
This isn't normally a problem, except if we're at the tail end of a big reloaded project and are now poking at the release process.
Environment
N/A
To Reproduce
$ go get -d -u github.com/weaveworks/weave-gitops
go get: upgraded github.com/weaveworks/weave-gitops v0.7.0-rc11 => v0.7.0-rc9

Workaround
Open go.mod, change the version, and refresh go.sum with go mod tidy.
Or, go from rc9 to rca and do the alphabet instead.

The new instructions recommend rc.4

repo: weaveworks/weave-gitops


text:
Broken links in Installing Weave Net page

There are several broken links in https://github.com/weaveworks/weave/blob/master/site/installing-weave.md specifically, the link to deploying applications and also the links that point to github files don't seem to to be working.

fixed

repo: weaveworks/weave


text:
The error encountered when the Chunker option is set to Code.

Hello,
On the Import Config page, when I select the Chunker option as Code, I choose either the Python or PHP option. Then, I select a file with the .py or .php extension according to my choice, and when I perform the import, I get the following error. I wonder if this error is related to LangChain? I feel like I might be missing something that needs to be done, but I also wanted to report it in case it might be a issue.
Import for framework.py failed: '>' not supported between instances of 'int' and 'str' | 0

✔ Collected all Batches of framework.py
ℹ Removing framework.py from BatchManager
ℹ Found existing Client
ℹ FileStatus.STARTING | framework.py | Starting Import | 0
ℹ Loading framework.py (py)
ℹ FileStatus.LOADING | framework.py | Loaded framework.py | 0.14
ℹ FileStatus.CHUNKING | framework.py |  | 0
ℹ FileStatus.ERROR | framework.py | Import for framework.py failed: '>'
not supported between instances of 'int' and 'str' | 0.0
✘ No documents imported 0 of 1 succesful tasks
ℹ FileStatus.ERROR | framework.py | Import for framework.py failed:
Import for framework.py failed: '>' not supported between instances of 'int' and
'str' | 0

Thanks for the issue, I'll look into it!

It is clear that this is definitely a bug. Could you update the status as a bug? Thanks.

Let me know if this issue still exists 😄 I wasn't able to recreate your issue, if it still exists can you let me know which python version you're using? (Sorry for the late reply 🙏 )

repo: weaviate/Verba


text:
Improved UI of Videos , Images and GIFS in DOCS

Issue soled - #125
It will maintain continuity in UI.
Changes made in both Version of DOCS.
Before :

After:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Can we make this a plugin or something of Rspress ? That would be easy to maintain.

@yuyutaotao Sir, could you please provide more details about it? I'm willing to help.

Hi，it should be a plugin like this: https://github.com/linbudu599/rspress-plugins/tree/main/packages/rspress-plugin-align-image

@yuyutaotao I'll start work on it.

repo: web-infra-dev/midscene


text:
[Bug]: failed to disable source map

Version
System:
    OS: Windows 11 10.0.22631
    CPU: (18) x64 Intel(R) Core(TM) Ultra 5 125H
    Memory: 7.73 GB / 23.47 GB
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @rsbuild/core: ^1.0.4 => 1.0.4
    @rsbuild/plugin-sass: ^1.0.1 => 1.0.1
    @rsbuild/plugin-vue2: ^1.0.1 => 1.0.1

Details
我看文档写的默认生产环境js和css都不生成map文件，但是打包出来js是有类似index.6a43bdf3.js.map这种map文件的，然后配置项里设置js: import.meta.env.NODE_ENV === 'production' ? false : 'cheap-module-source-map'同样无效。
const path = require('path')

import { defineConfig, loadEnv } from '@rsbuild/core'
import { pluginVue2 } from '@rsbuild/plugin-vue2'
import { pluginSass } from '@rsbuild/plugin-sass'
import { pluginSvgSpriteLoader } from 'rsbuild-svg-sprite-loader'

const ConfigGenerator = require('./plugins/config-generator')

export default defineConfig({
    html: {
        template: './public/index.html'
    },
    output: {
        copy: [{ from: './public/config.js' }],
        sourceMap: {
            js: import.meta.env.NODE_ENV === 'production' ? false : 'cheap-module-source-map'
        },
    },
    plugins: [
        pluginVue2(),
        pluginSass({
            sassLoaderOptions: {
                additionalData: '@import "@/assets/styles/modules/_variables.scss";'
            }
        }),
        pluginSvgSpriteLoader({
            path: path.join(__dirname, 'src/assets/icons'),
            symbolId: 'icon-[name]'
        })
    ],
    source: {
        entry: {
            index: './src/main.js'
        }
    },
    tools: {
        rspack: {
            devtool: 'source-map',
            resolve: {
                extensions: ['.vue', '.js', '.json'],
                alias: {
                    '@': path.resolve(__dirname, 'src')
                }
            },
            plugins: [new ConfigGenerator()]
        }
    },
})

Reproduce link
无
Reproduce Steps
无

remove this line: devtool: 'source-map',

感谢

repo: web-infra-dev/rsbuild


text:
processAssets custom stage number not supported

System Info
all
Details
Inside of the index-html-webpack-plugin for Angular CLI there is an apply call that leverages custom processAssets stages. Compilation.PROCESS_ASSETS_STAGE_OPTIMIZE + 1 this is not currently supported in Rspack.
Reproduce link
No response
Reproduce Steps
Using Angular builder for Rspack.

bump

bump

bump

bump

@ahabhgk this should be resolved now?

Yes, hook with any stage number supported in >= v0.6.0

authors: ahabhgk hardfist xc2 zackarychapple

repo: web-infra-dev/rspack


text:
automatic update outdated dependency

Rsbuild uses renovate to do automatic update dependency https://github.com/web-infra-dev/rsbuild/issues/1316, Rspack can also integrate this to ensure dependency is updated.

I can turn it on for Rust and github actions.
Our npm dependencies are too convoluted to be updated automatically yet. I tried using depcheck and skott but things start falling apart when I start removing dependencies.

Rust crates and github actions are done.
FYI https://developer.mend.io/github/web-infra-dev/rspack shows the update list at the bottom.

Bulk of the work is done https://github.com/web-infra-dev/rspack/blob/main/.github/renovate.json
I'll update it when things become convoluted.

authors: Boshen hardfist


text:
resolve error when enable testcase webpack-test/configCases/inner-graph/basic

System Info
not related
Details
    message =   × Failed to resolve loader: ../_helpers/testModuleLoader in  OxcResolver(NotFound(".....; formatted =   × Failed to resolve loader: ../_helpers/testModuleLoader in  OxcResolver(NotFound("...;
moduleIdentifier = /xxxx/Documents/rspack/rspack/webpack-test/configCases/inner-graph/_hel...; moduleName = ../_helpers/entryLoader.js?{"usedExports":[],"expect":{"./assert":["equal"]},"name":...; modu
leId = 649; compilerPath = nothing without module concatenation

Reproduce link
current repo
Reproduce Steps

remove webpack-test/configCases/inner-graph/basic/test.filter.js
cd webpack-test
pnpm test case -- -t inner-graph

Here's the error message in detail:
{
          message: '  × Failed to resolve loader: ../_helpers/testModuleLoader in  OxcResolver(NotFound("../_helpers/testModuleLoader"))\n',
          formatted: '  × Failed to resolve loader: ../_helpers/testModuleLoader in  OxcResolver(NotFound("../_helpers/testModuleLoader"))\n',
          moduleIdentifier: '/Users/bytedance/github/rspack/webpack-test/configCases/inner-graph/_helpers/entryLoader.js?{"usedExports":[],"expect":{"./assert":["equal"]},"name":"nothing"}!',
          moduleName: '../_helpers/entryLoader.js?{"usedExports":[],"expect":{"./assert":["equal"]},"name":"nothing"}!',
          moduleId: '228',
          compilerPath: 'nothing without module concatenation'
        },

Why is there a ! at the end of the filename? Resolver is not going to work with this !.

Related: https://github.com/web-infra-dev/rspack/issues/5393

bump

Update: missing __webpack_exports_info__.usedExports support.

authors: Boshen IWANABETHATGUY h-a-n-a


text:
[Feature]: Support for injecting extra head tags via front matter

What problem does this feature solve?
Provide support for injecting extra head tags via front matter, like Vuepress and Vitepress:

https://vitepress.dev/reference/frontmatter-config#head
https://vuepress.vuejs.org/guide/frontmatter.html#predefined-variables

What does the proposed API look like?
---
head:
  - - meta
    - name: description
      content: hello
  - - meta
    - name: keywords
      content: super duper SEO
---

The parsing function of frontmatter uses gray-matter and doesn't use mdx-rs.
To achieve this function, maybe you can view:  https://github.com/web-infra-dev/rspress/blob/ec951a7a94ab6a3dd0185d9a3289b2f4536a7968/packages/shared/src/node-utils/loadFrontMatter.ts#L5-L9

Is there progress or timeline on this feature? Any additional input before I open PR for this?

No progress yet, feel free to send a PR for this 😄

At present, this PR#1145 only implements this feature in theme-default, and further exploration is needed to achieve as vitepress.

At present, this PR#1145 only implements this feature in theme-default, and further exploration is needed to achieve as vitepress.

Yes ☹ Probably plugging in the build step and injecting the headers there would be better. Couldn't find this place and that is why I implemented it in the default theme layout. Maybe help me find this place and I can move the implementation over to there?

The rendering page step when build is here. https://github.com/web-infra-dev/rspress/blob/d4432ac1108130f43ae928aafedff6c9fe6de669/packages/core/src/node/build.ts#L83-L89

Done with #1168

Thanks!

authors: Timeless0911 chenjiahan shulaoda toteto

repo: web-infra-dev/rspress


text:
Add features for @import and @supports

I picked these up because api.CSSImportRule.supportsText is newly available.

OK, I changed the @supports identifier and change the name and description. I used an "Also known as feature queries" to capture the alternate name.

repo: web-platform-dx/web-features


text:
added story for static month in DatePicker

name: 'Pull request'
about: A new pull request
New Pull Request
Checklist

[x] I am not disclosing a vulnerability.
[x] My code is conform the code style
[x] I have made corresponding changes to the documentation
[x] I have updated Typescript definitions when needed

Issue Description
In Datepicker component in Static Date story inside Forms section, when the type is set to month, it doesn't works instead shows blank line.

Related issue: #836
Solution Description
when type is set to date then format for default/static value is 'yyyy-mm-dd'
when the type is set to month static value format should be 'yyyy-mm'.
I created a new story for the case of type-month with 'yyyy-mm' as a static value to let the users know that both static date format is different for type month.

Great job, TY for your contribution 🥳


text:
Unable to Unequip Piano

When we equip the piano, we are not able to unequip it.
https://user-images.githubusercontent.com/104460803/168891537-6c8a313f-62be-421c-90fb-22defe842fa9.mp4

We can unequip it with space but that is not much of a good solution. The reason we can't uneuip it with "R" is because the piano's R is interfering with unequip key "R".
@Loryhoof Can you look into this?

repo: webaverse/app


text:
fails on builder step

Here is my config:
on: [push]

jobs:

  testRunnerInAllModes:
    name: Unity test
    runs-on: ubuntu-latest
    env:
      UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
    steps:
      # Checkout repository (required to test local actions)
      - name: Checkout repository
        uses: actions/checkout@v1

      - name: Unity - Activate
        uses: webbertakken/unity-activate@v1

      - run: ls -l

      - name: Unity - Builder
        uses: webbertakken/unity-builder@v0.3
        with:
          projectPath: "."
          unityVersion: "2019.2.11f1"
          buildCommand: "UnityEditor.SyncVS.SyncSolution"
          targetPlatform: StandaloneWindows64

I am getting this error message when it gets to Unity - Builder step:
 Generate Solution0s
##[error]Node run failed with exit code 1
Run webbertakken/unity-builder@v0.3
/usr/bin/docker build /home/runner/work/MirrorNG/MirrorNG --file /home/runner/work/MirrorNG/MirrorNG/Dockerfile --build-arg IMAGE=gableroux/unity3d:2019.2.11f1-windows --tag unity-builder:2019.2.11f1-windows
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/runner/work/MirrorNG/MirrorNG/Dockerfile: no such file or directory
##[error]The process '/usr/bin/docker' failed with exit code 1
##[error]Node run failed with exit code 1

Here is a link to the failed job:
https://github.com/MirrorNG/MirrorNG/commit/70cd06ab6fa3f7ec7d00fdf1a37608245405a12a/checks?check_suite_id=380753696

Here is an update,  v0.2 works fine with the exact same configuration,  it seems this is a regression in v0.3

Here is an update, v0.2 works fine with the exact same configuration, it seems this is a regression in v0.3

Hi @paulpach,
Thanks for reporting the issue. I'll have a look when I get the chance.
Please note that v0.2 has a different readme and did not allow for builds other than from the webgl image at all. A lot has changed since.
See also the progress on supporting multiple platforms here https://github.com/webbertakken/unity-actions/issues/12

Work can be tracked here: https://github.com/webbertakken/unity-builder/pull/9

This is fixed in https://github.com/webbertakken/unity-builder/pull/10
As can also be seen here: https://github.com/webbertakken/unity-actions/pull/24/checks?check_run_id=376523913

I was also getting this error when targeting Android on Unity 2019.2.17f1. Any idea when this fix will be deployed?

Please note that I'm doing all this just in my free time, while my real goal in that time is creating a unity project. That said, I'll do what I can do. Could you please try it on v0.4 and create a new issue for it and show the error?

@webbertakken That seems to have fixed it 🙂 I'm still getting build errors, but it looks like now its because there's no gableroux/unity3d Dockerfile for Unity 2019.2.17f1 yet. Guess my next Issue/PR will be over there lol

@Rabadash8820 already done ;) https://gitlab.com/gableroux/unity3d/merge_requests/77

@GabLeRoux Awesome! And damn, impressive following of other repos' Issues 😛

authors: GabLeRoux Rabadash8820 paulpach webbertakken

repo: webbertakken/unity-actions


text:
Add HTMLLinkElement support

This is mostly for fixing https://projects.gatunes.com/wsvr/#/41983/144,-144, which is a very 2D site at boot.

This gets us to everything except drawing the chunks cubemarch. The chunks are generating since you can walk on them,.

Tested with node . -x none https://projects.gatunes.com/wsvr/#/41983/144,-144, but there's still more to be done on that site.

repo: webmixedreality/exokit


text:
Resolve ambiguous null interpretation with regards to defaultValues

There is some ambiguity in both the GraphQL spec and various implementations with regards to when defaultValues are applied to arguments.
A spec change to resolve this is being considered and there is a proposed PR for the JS implementation as well.
I have run into this during use of graphql-php where I wanted defaultValue to be applied for an optional argument (which can't be null either), but the client used sends null as the value for the argument. I expected the defaultValue to be substituted, but null was the coerced value instead.
This PR tries to apply a similar fix for the ambiguity in the above PR for the JS implementation, always using the defaultValue for a node if the value is explicitly sent as null (either directly or via variables).

Coverage decreased (-0.02%) to 92.82% when pulling 658836cb3d725636de3e81f645282e15959ee0dc on samsouder:master into 94525c00252696b47673db1ca56fe0436c5949be on webonyx:master.

I think we should wait for a fix in the reference implementation.

The reference implementation merged the referenced PR in April.

Needs rebase tho

Also, i think spec and reference implementation changed since this PR.  Explicit "null" don't sets value to default anymore.

This looks like an important bugfix, especially considering that the reference implementation is now also fixed.
The spec definitely says that explicit null is not the same as omitting the argument: https://graphql.github.io/graphql-spec/draft/#sec-Null-Value

I no longer have interest in fixing this specific issue to ensure it matches the current reference implementation.

@vladar i would be willing to champion this and create a new PR, ok?

@spawnia Yeah, as long as it matches reference implementation and spec, sure.

Fixed in https://github.com/webonyx/graphql-php/commit/bf4e7d4a9f078fb926f92a32725a6ccf0c0e09a2
@vladar Thanks for tackling this important issue. You are doing a great job with this library!

@spawnia thanks %)

authors: SevInf coveralls nagledb samsouder simPod spawnia vladar

repo: webonyx/graphql-php


text:
eslint-loader doesn't check if additional .eslintrc exists

eslint gives ability to overrides rules for specific folders, for example:
- app/
- app/index.js
- app/.eslintrc // (a) Overrides rules from (b)
- index.js
- .eslintrc // (b)

In my project when I use eslint by eslint-cli I don't get any errors but when I develop and use webpack + eslint-loader, then I get errors.
ERROR in ./src/components/Icons/IconSearch.js

/a/b/c/e/f/g/h/src/components/Icons/IconSearch.js
  8:1  error  Line 8 exceeds the maximum line length of 100  max-len

✖ 1 problem (1 error, 0 warnings)

 @ ./src/views/home/index.js 13:0-61
 @ ./src/app/routes.js
 @ ./src/app/index.js
 @ ./src/index.js
 @ multi app

I don't want append
/* eslint-disable max-len */

in each file that contains SVG because I have a lot of icons...
Is there any way to instrument this loader to check if additional .eslintrc files exists?

eslint-loader doesn't load the eslintrc files - it uses an instance of eslint.CLIEngine which the eslint-cli also uses and that should resolve the correct rules for each file itself. I've just tried nested .eslintrc files and it seemed to be working correctly for me.
Do you have the eslint-loader cache option enabled? If so then you may be experiencing the problem described in #124 where if you change the eslint rules the previously cached results are still being output. Try setting cache to false and if that fixes the issue you can delete node_modules/.cache/eslint-loader to reset the cache properly.

Do you have the eslint-loader cache option enabled?

Yes. If I disable cache, it doesn't change anything.
I'm using webpack 2.1.0-beta.27 with this configuration:
{
    module: {
      loaders: [
        {
          enforce: 'pre',
          test: /\.js$/,
          loader: 'eslint-loader',
          exclude: /node_modules/,
        },
      ],
    },
    plugins: [
      new webpack.LoaderOptionsPlugin({
        test: /\.js$/,
        options: {
          eslint: {
            configFile: utils.root('.eslintrc'), // this is my helper for resolving paths
            cache: false,
          }
        },
      }),
    ],
  }

I'm using also eslint-config-airbnb but this probably is not related. I will try reproduce this issue and create an example repository that shows this bug.

@wrakky https://github.com/hinok/webpack2-eslint-loader
npm install

# Run eslint by eslint-cli
npm run lint

# Run webpack2 + eslint-loader
npm start

Repository contains demo.gif added in README.md that shows recorded behaviour.
Look at additional .eslintrc inside subfolder.

If you use the -c option in the npm run lint command (eslint . --ext .js -c .eslintrc) which is the equivalent to the eslint-loader configFile option you get the same output from both eslint cli and weback.
The file passed to theconfigFile option is not extendable which is why you are having the problem. You probably want to either remove the option if possible or maybe the baseConfig option will work for you instead.
Either way this isn't an eslint-loader issue. Hope that helps!

Yep, that's it. Sorry for the confussion! When I found yesterday that removing configFile solved the problem, I was pretty sure that let's say it's the eslint's fault not eslint-loader - if we could name it as a fault.
I close this issue and maybe it's worth to update README? I could add PR if you want.

PR welcome!

Added PR https://github.com/MoOx/eslint-loader/pull/130

I am having a similar problem, can you post your actual config files which resolved your issue?
configs:

webpack
package.json

The problem can be fixed by adding the option configFile
{
  test: /\.(js|vue)$/,
  loader: 'eslint-loader',
  enforce: 'pre',
  include: [resolve('src'), resolve('test')],
  options: {
    formatter: require('eslint-friendly-formatter'),
    emitWarning: !config.dev.showEslintErrorsInOverlay,
    configFile: '.eslintrc.js'
}

@dualeoo: I still got a same issue with latest eslint-loader and eslint, even when configFile is there

@midori0507 sr but

which issue are you referring to?
which version of eslint-loader and eslint you are using?
can you give me your config file?

@dualeoo:
Issues: Eslint-loader didn't show any error when build, but when you run node_modules/.bin/eslint  it show multiple lint errors, Eslint-loader does work, just not 100%.
Version: eslint-loader@2.1.2
eslint 5.14.0
Config:
module: {
    rules: [
      {
        enforce: "pre",
        test: /\.js$/,
        exclude: /node_modules/,
        options: {
           babelPath: require.resolve('eslint'),
           configFile: path.resolve(__dirname, '../.eslintrc'),
        },
        loader: "eslint-loader"
      },
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: "babel-loader"
      }
    ]
  }
  // ...

.eslintrc
{
"extends": "airbnb",
"env": {
"browser": true,
"mocha": true,
"node": true
},
"globals": {
"SETTINGS": true
},
"parser": "babel-eslint",
"plugins": [
"import",
"react"
],
"settings": {
"import/resolver": {
"webpack": {
"config": "./config/webpack.common.js"
}
}
},
"rules": {
"class-methods-use-this": "off",
"import/no-extraneous-dependencies": "off",
"import/order": [
"error",
{
"groups": [
"builtin",
"external",
[
"internal",
"parent",
"sibling",
"index"
]
],
"newlines-between": "always"
}
],
"import/prefer-default-export": "off",
"new-cap": [
"error",
{
"capIsNew": false,
"newIsCap": true
}
],
"no-underscore-dangle": [
"error",
{
"allow": [
"_paq"
]
}
],
"no-unused-expressions": "off",
"no-use-before-define": [
"error",
"nofunc"
],
"react/forbid-prop-types": "off",
"react/jsx-filename-extension": "off",
"react/jsx-sort-props": [
"error",
{
"ignoreCase": true
}
],
"react/no-string-refs": "off",
"react/no-unused-prop-types": [
"error",
{
"skipShapeProps": true
}
],
"react/prefer-stateless-function": "off",
"linebreak-style": 0,
"no-restricted-globals": [
"error",
"history"
],
"prefer-destructuring": "off",
"react/destructuring-assignment": "off",
"react/require-default-props": "off",
"jsx-a11y/click-events-have-key-events": "off",
"jsx-a11y/anchor-is-valid": "off",
"jsx-a11y/label-has-for": "off",
"react/no-array-index-key": "off"
}
}

@midori0507 maybe webpack doesn't include files with error in the build. Is it realy used in code?

In my case the issue was fixed by changing from the old webpack.module.rules.Rule.query key to webpack.module.rules.Rule.options.

authors: MoOx Venryx dualeoo hinok midori0507 nmccready oceandrama wrakky

repo: webpack-contrib/eslint-loader


text:
Add changelog

Because it’s important.

@sokra genuinely doesn't care about informing people of what he's doing with webpack.  You'll be waiting a long time for this.

@d3viant0ne I guess this will be solved once we get this project to follow the standard structure, right?

yep standard version generates a CHANGELOG.md following git tags and extract them based on the angular commit convention, so at mininum commits starting from the last (current)  tag must be reworded to follow the convention

@michael-ciniawsky Is it possible to lint PRs against the commit convention? I think that would help a lot.

@bebraw https://github.com/marionebl/conventional-changelog-lint [+ https://gitcop.com/]

@michael-ciniawsky 👍 Thanks.

We have a standard setup for this, i'll PR it in shortly. See webpack/webpack#4104

Already fixed changelog

authors: bebraw d3viant0ne evilebottnawi michael-ciniawsky sapegin warrenrumak


text:
variables in webpack's css loader

I started using the webpack's css loader and I find it really useful in terms of having "local scope" in css. What I need is variables e.g. I have something like this
:local(#names > input){
  flex: 0 1 100%;
  background: #2E2E2E;
  margin: 2px;
  border: 1px solid #FF5251;
}

I want to define a variable for the color, e.g. $pink = '#FF5251 Is there a way to do that inside this css file with the css loader or the only solution is to change loader and use sass ?
I mean, since it is not a "real" css file and it already has things like local and composes, someone would expect support for variables.

Have a look at @value, which is now part of webpack css-loader:
https://github.com/css-modules/postcss-modules-values
Using @value to pass arbitrary values between module files is similar to $sass-variables, but without the global scope implications.

@dspnorman cool, thx! I will close the issue.

authors: AvraamMavridis dspnorman

repo: webpack/css-loader


text:
Won't load videos

The documentation shows:

but for some reason I can't get the require('./file.mp4') to work.
I posted a question on StackOverflow about this.  Any ideas why this isn't working?

Do you still have this issue? There are a couple of answer on your StackOverflow question.

I'm closing this issue because of inactivity. Feel free to comment, and we can always re-open it again.

repo: webpack/file-loader


text:
only ${require('..')} to be translate.

Please check if the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
The template language has ${list.href} flag when i use Freemarker template and i want to the loader to only translate ${require('..')} and require that.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the following...

Impact:
Migration path for existing applications:
Github Issue(s) this is regarding:

Other information:

tests are unhappy, thank for the PR!

Current coverage is 96.62% (diff: 100%)

Merging #80 into master will increase coverage by 0.85%

@@             master        #80   diff @@
==========================================
  Files             2          2
  Lines            71         89    +18
  Methods          10         11     +1
  Messages          0          0
  Branches         14         15     +1
==========================================
+ Hits             68         86    +18
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update 10280c2...51efc66

authors: Justinidlerz codecov-io hemanth

repo: webpack/html-loader


text:
Update index.md

Add markup-inline-loader

Done.
Sorry for my poor English ^_^ .

@asnowwolf, make sure to submit a PR for https://github.com/webpack-contrib/awesome-webpack#loaders as well.

@simon04 Done, Thank you!


text:
Compiling without creating a dev-server

Hi guys! How can I compile and run a page directly from index.html without starting webpack-dev-server? I'm a beginner so every explanation that could make me understand how this works and how it can be fixed would be great. Thanks!

Check this out https://webpack.github.io/docs/tutorials/getting-started/

Ok I had it working. I think I didn't explain my problem well - sorry.
I would like to post my project on github gh-pages. If I store my project locally I have to manually compile it. Does github compile it by default or do I have to make other settings?

Ok I got it working. Running webpack in console created my bundled js. Thanks for your help! :D

authors: MariusGarbea adithyan

repo: webpack/webpack