text:
Missing JMX options to connect to the instance

I know JMX is discouraged, Jolokia is available, but this image is very handy to simulate a standalone installation.
However there is a missing part in the documentation about being able to connect to the Artemis via JMX. I am not sure if this should be a part of the image/runtime config:
 -e JAVA_OPTS="-Dcom.sun.management.jmxremote.local.only=false \
               -Djava.rmi.server.hostname=`ipconfig getifaddr en0`"

The hostname is resolved to the wireless adapter IP address via the ipconfig command on my Mac. Not sure about a more generic approach.
With this option among with forwarded ports we were finally be able to connect to the instance via JMX:
docker run -it --rm --name=artemis \
  -e ARTEMIS_USERNAME=devuser \
  -e ARTEMIS_PASSWORD=pass \
  -e ENABLE_JMX=true \
  -e BROKER_CONFIG_NAME=dev_artemis \
  -e JMX_PORT=2099 \
  -e JMX_RMI_PORT=2099 \
  -p 8161:8161 \
  -p 61616:61616 \
  -p 2099:2099 \
  -e JAVA_OPTS="-Dcom.sun.management.jmxremote.local.only=false \
                -Djava.rmi.server.hostname=`ipconfig getifaddr en0`" \
    vromero/activemq-artemis:1.5.6

I confirm the configuration above also works for me.
I am not knowledgeable enough about automatically adding the JAVA_OPTS. The current documentation mentions Kubernetes, and I cannot figure out how would Kubernetes access the container's JMX w/o the aforementioned options, maybe it can, but again, don't know much about Kubernetes either.
One thing I am almost sure is to include the BROKER_CONFIG_NAME parameter explicitly in the documentation. This is required to get external JMX access, because the default is random.

On second thought, maybe leaving the hostname=0.0.0.0 in the documentation makes more sense: The user might install the docker on another machine (not the same host), and try to access externally. I am not sure localhost -> remote_docker_host -> artemis_container scenario would still work with 0.0.0.0.

0.0.0.0 should work, it means all addresses in all network interfaces, which works great for docker to avoid the need of predicting the ip address provided to the container.
I'm thinking on perhaps adding an `-e JMX_ALLOW_REMOTE=true' that would add those two parameters. Will think a bit more about it and then in a few days implement.

i happened to be looking at jmx today as well, just a couple other notes.

it probably also makes sense to expose 1099 & 1098 inside the dockerfile as well
0.0.0.0 doesn't work for me if I want to connect via jmx using the dns entry of the external vip.  so in my case to get it to work i have to put the java.rmi.server.hostname=vip_dns_name.   With this in mind, it might make more sense to have a variable such as JMX_HOSTNAME which defaults to 0.0.0.0 but can be overriden when needed.   Although simply using JAVA_OPTS works well also.

Yeah so in my experience (and I might be wrong) 0.0.0.0 only works for localhost connections, I'm surprised it even works in docker but it does. The reason why it acts wacky is that there are two connections, the first one for jmx and then it reconnects using RMI to whichever is the ipaddress configured there, and 0.0.0.0 randomly (or at least non-deterministically) picks one. I have no solution for this, no-one seems to have and that is why I and pretty much everybody recommends jolokia over JMX in docker.
Passing the ip address with bash tricks and so on its not acceptable imho and very platform dependent.

jmx is still useful if you want to use jconsole/visualvm, passing the external dns name to java.rmi.server.hostname works fine in this case.

yes, hence my doubt. I guess I could add a JMX_HOSTNAME env defaulted to 0.0.0.0 and document very clearly the use case.
It is also arguably also that tanuki and the hawtio console are more than enough.

I have decided to ignore this for the time being, I don't want to support randomized ports within Docker at the moment. Might revisit later but not for now.

authors: abedwardsw bahrigencsoy vromero

repo: vromero/activemq-artemis-docker


text:
Docs of Setup CouchDB is needed.

From Forum:
Basics

Self-hosting limitations.
Setup CouchDB ( bare? / dockerimage? )
Preferred configurations
Expose to the internet by ngrok for testing.

Additional

Expose to the internet by own domain and the setup the reverse proxy with SSL.

I think if I encourage someone to host and maintain a server. End to End encryption is needed to reduce the impacts of misconfigurations and/or vulnerabilities.

FYI - https://github.com/vrtmrz/obsidian-livesync/issues/17 has a working docker-compose.yml - just add another volume line with the local.ini as shown by @vrtmrz
    volumes:
        - ./conf/couchdb/local.ini:/opt/couchdb/etc/local.ini

and put an .env file like this in the same dir as your docker-compose.yml:
COUCHDB_SERVER=<fully qualified server name>
COUCHDB_USER=<(to be created) couchdb user name>
COUCHDB_PW=<(to be created) couchdb password>

Caddy Docker Proxy will get a LetsEncrypt cert on its own and you should be all set...

Not there yet for multiple devices, see https://github.com/vrtmrz/obsidian-livesync/issues/20

For me, this docker-compose.yml together with the following CouchDB local.ini works now:
[chttpd]
require_valid_user = true

[chttpd_auth]
require_valid_user = true

[httpd]
WWW-Authenticate = Basic realm="couchdb"
enable_cors = true

[cors]
origins = app://obsidian.md, capacitor://localhost
credentials = true
headers = accept, authorization, content-type, origin, referer
methods = GET, PUT, POST, HEAD, DELETE

Android probably has a 3rd origin, haven't tested that yet, will update as soon as I have

Thank you for awsome information! It's very helpful!
I'm making the repo for docker-compose.
After I tested to establish bland new server by the repo.
It will be public.
And if you don't mind, may I add your name(arminus is ok?) into the docker-compose.yml?

And if you don't mind, may I add your name(arminus is ok?) into the docker-compose.yml?

sure

I wrote simple instructions and docker-compose.yml on new repo
I really appreciate your investigations and giving me your docker-compose.yml

it took 26 days but was finally done :)

Can we put it behind a forward authentication through for example authentik ?

This is the first time I have heard of Authentik. This is fantastic. (I thought about adopting it personally).
However, currently, Self-hosted LiveSync cannot use this. It cannot open the UI for authentication during the replication connection. (However, if it were possible, it would make easier connection configuration, especially in the office or lab environment. It is very interesting).
From Authentik's functional point of view, if it could be opened, it would at least be available in Proxy Provider.
I regret to say this, but this is now a situation.

@vrtmrz dang, i was here hoping for authentik as well.
if the device i am using has already been logged in to authentik and should not need interaction with authentication, is it still not able to be forwarded by authentik to the domain, hands free?

source: gharchive/issue

authors: SutanuNandigrami arminus princinv vrtmrz

repo: vrtmrz/obsidian-livesync

license: MIT

license_type: permissive

license_source: github-api


text:
[Icon Request] CAKE folder

vscode-icons already supports .cake files, however it would also be nice if it would highlight CAKE's folder in a similar way that .nuget folder is being highlighted:
the folder's name is CAKE and it's typically located within the tools folder.

Please see #650.

repo: vscode-icons/vscode-icons

license: mit

license_source: bigquery


text:
Update Bloc folder icon

Changes proposed:

[ ] Add
[ ] Delete
[x] Fix
[ ] Prepare

The bloc library updated its logo last week.

Thanks so much for doing this! One question, does it matter that the size of the icon was modified? Previously it was 40x40 but the new one is 34x34. I just want to make sure that was intentional 👍

@felangel it is intentional, all the icons must be 28x28 whereas the viewport is 32x32 (2px of margin on each side) and the small icon inside the folder must not be greater than 20x20.

source: gharchive/pull-request

authors: KingDarBoja felangel


text:
[Feature Request] use "|" or any other "rare" character as concatenation character in the model  model name  instead of "_"

I've trying to design a common dashboard for all possible models where to see evolution for real/predicted data.
Something like that.

In order to build the queries by only selecting the model name could be interesting if could build variables like in the picture, from the incoming model name.
right now the name is something like "$db_$measurement_$oper_$field_$tagkey_$tagvalue_time_$groupby", when trying to build variables in grafana with regexp is difficult because  the "_" character is commonly used in db names , field names , tag names.

Would be nice if  we can select the concatenation character , if the model name was any of these:

swarm|cpu|mean|usage_active|host|worker1|time|5m
swarm:cpu:mean:usage_active:host:worker1:time:5m
swarm cpu mean usage_active host worker1 time 5m

instead of
swarm_cpu_mean_usage_active_host_worker1_time_5m
build the regex would be easier than before , and could cover most of the normal cases.
If done I will be able to share these generic dashboards
Thank you very much for your work @vsergeyev

Hi @vsergeyev I'm trying to automate with ansible with the before proposed format and is not working because of model name restrictions as in https://github.com/regel/loudml/issues/62
It seems that model name should match this regex  ^[a-zA-Z0-9-_@]+$  the only non usual character perhaps could be '@'

Hi @toni-moreno
Agree this should be a way to specify model name in panel itself.
This may give a possibility to specify variables in model name field,
so it will be converted to required when "Create baseline" button is clicked.
V.

authors: toni-moreno vsergeyev

repo: vsergeyev/loudml-grafana-app


text:
add security code and docker

As you can see I added the security code in the config.py file and check it at the same time as the whitelist.
I also added a Dockerfile and docker-compose.yml file for those who like to run it inside a container.

Awesome, thank you - appreciate it!

You're welcome ^^

What should I do to use this security code ?
I am getting this error

Hi @Rhydderch, I replied to your issue in #18.

authors: Rhydderch TheDevFab jon4hz vsnz

repo: vsnz/TradingView-Webhook-Bot


text:
Added AREK to permissions section

Project URL
https://github.com/ennioma/arek
Description
I've added AREK to the permissions section.
Why it should be included to awesome-ios (optional)
Checklist

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

we can merge this after the readme includes some installation instruction :) ^

thx @ennioma

authors: dkhamsing ennioma

repo: vsouza/awesome-ios


text:
Add Framezilla to Layout section

Framezilla
https://github.com/Otbivnoe/Framezilla
Description
Elegant library which wraps working with frames with a nice chaining syntax.

          1 Error

:no_entry_sign:
Found 4 link issues

Link issues by awesome_bot

Line
Status
Link

416
301
http://developer.couchbase.com/mobile/ redirects tohttps://developer.couchbase.com/mobile/

2429
503
https://www.amazon.com/Programming-Objective-C-6th-Developers-Library/dp/0321967607

2432
503
https://www.amazon.com/Core-Data-iOS-Data-Driven-Applications/dp/0321670426

2433
503
https://www.amazon.com/Cocoa-Design-Patterns-Erik-Buck/dp/0321535022

  Generated by :no_entry_sign: danger

Thank you! 🎉

authors: Otbivnoe danger-awesome-ios victorgama


text:
Update README.md

add a swift sqlite orm
Project URL
https://github.com/izouxv/SwiftyDB
Description
orm for sqlite
Why it should be included to awesome-ios (optional)
Checklist

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

add swiftydb for sqlite orm

          1 Warning

:warning:
Please update the Pull Request title to contain the library name

  Generated by :no_entry_sign: Danger

@fish-red thanks for the suggestion
however the readme is incomplete so i will have to close this
feel free to open again or suggest something else when ready :)

authors: danger-awesome-ios dkhamsing fish-red


text:
Add MultiSlider

Project URL
https://github.com/yonat/MultiSlider
Description
UISlider clone with multiple thumbs and values, optional snap intervals, optional value labels.
Checklist

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

You're on fire today 🔥
Thanks again!

authors: lfarah yonat


text:
Style component is missing from exports

Hi
As per documentation, I added this code to my nuxt project:
<script setup lang="ts">
import { Head, Style } from '@vue-email/components'
</script>

But I am receiving this error:

The requested module '/_nuxt/node_modules/.cache/vite/client/deps/@vue-email_components.js?v=33decdef' does not provide an export named 'Style'.

All other components are imported without any issues.

should be there in 0.0.18 version, thank you for reporting it

Thanks for the quick response. I updated the package but still have the same issue.
I removed node_modules folder and pnpm-lock.yaml then tried to insall again using pnpm install but I received this error:

ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In : "@vue-email/render@workspace:*" is in the dependencies but no package named "@vue-email/render" is present in the workspace
This error happened while installing the dependencies of @vue-email/components@0.0.18

I ran pnpm install with version 0.0.17 and it is working fine.

weird, something has to do with how it was published, could you check 0.0.19 ?

btw, did you have @vue-email/render installed or not ?

Now it is working with version 0.0.19. Thanks.
Yes, I have installed @vue-email/render

authors: Flowko abdul-alhasany

repo: vue-email/vue-email


text:
jump to definition in template won't work when using defineModel

Describe the bug
在 setup 里使用 defineModel 会导致 template 变量和函数跳转到自定义失效，有时候还会出现跳转到错误行数的情况。

Reproduction
https://github.com/jhxxs/vue-maros-issue-reproduction
System Info
macOS: 13.2.1 (22D68)
vscode: 1.76.0

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

随着 volar 2.0 的发布，这个问题好像不存在了。

repo: vue-macros/vue-macros


text:
不支持optionalTypes ts报错

使用 optionalTypes 时，type 也是必须的。

authors: MaZhaolin yangmingshan

repo: vue-mini/vue-mini


text:
📝 DOCS: Missing import for apolloClient

On the setup page there is no indicator where the apolloClient actually comes from.
https://github.com/vuejs/apollo/blob/372892855d76622128ac560e8fadc689c50675bc/packages/docs/src/guide-composable/setup.md?plain=1#L48

https://github.com/vuejs/apollo/blob/372892855d76622128ac560e8fadc689c50675bc/packages/docs/src/guide-composable/setup.md?plain=1#L3

authors: Akryum sschneider-ihre-pvs

repo: vuejs/apollo


text:
Get scoped class name from useAttrs

What problem does this feature solve?
I want to set inheritAttrs: false and use class and style attributes in root element, but other in child element. It's not possible when I use <style scoped>.
What does the proposed API look like?
Now I have:
<script>
  defineOptions({ inheritAttrs: true });
</script>
<template>
  <label>
    <input v-bind="omit(attrs, ['class', 'style'])" />
  </label>
</template>

and I want:
<script>
  defineOptions({ inheritAttrs: false });
</script>
<template>
  <label v-bind="pick(attrs, ['class', 'style'])">
    <input v-bind="omit(attrs, ['class', 'style'])" />
  </label>
</template>

I'm not sure if I understand what you are asking for, but I assume you want the v-data-xxxx scope attribute to be included in attrs?
If so, I'm afraid that is not something we will support. It violates the scoping rules (only root node of child shares parent scope), and will also be a breaking change.

repo: vuejs/core


text:
acceptHMRUpdate skips optional attributes without default values

Reproduction
https://github.com/bodograumann/pinia-hmr-optional-attributes
Steps to reproduce the bug

git clone https://github.com/bodograumann/pinia-hmr-optional-attributes
cd pinia-hmr-optional-attributes
npm install
npm run dev
xdg-open http://localhost:5173
Press the "Increment" button. Sign says "positive".
touch src/store/counter.ts

Expected behavior
All the state should be preserved.
Actual behavior
counter.nr is preserved as 1, but counter.sign is lost. The page shows -, while it should show positive.
Additional information
The relevant code is here: https://github.com/vuejs/pinia/blob/93b5546cf18bc54bb90de2397219dec7360fa697/packages/pinia/src/hmr.ts#L41-L43

The problem is that the removal of the property sign could be intentional so I'm not sure if this is with changing as it would break other HMR cases.
In order to change this behavior, one could get each property with toRaw(newStore.$state) and check if the property is a ref in order to completely replace it rather than patchObject

Sounds to me like your proposed solution would keep the other use case of removing a property intact, right?
I think it should also work for us.
Normally I would be happy to contribute a PR, but given that my previous PR is still open and we are thus unable to use the latest pinia version, I am not sure how to proceed here :neutral_face:

I do need to check that PR. Currently we won’t be able to release a new version of pinia soon because of other changes 🥲

authors: bodograumann posva

repo: vuejs/pinia


text:
I made a mistake when creating a new vue/cli demo

Version
3.6.3
Reproduction link
https://github.com/qq229338869/my-question/blob/master/vue/vue-cli/question-one
Environment info
  System:
    OS: macOS Mojave 10.14.3
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  Binaries:
    Node: 10.15.3 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.4.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.103
    Firefox: 66.0.3
    Safari: 12.0.3
  npmGlobalPackages:
    @vue/cli: 3.6.3

Steps to reproduce
after install @vue/cli , webpack ,run  vue create my-project
What is expected?
create the vue/cle demo
What is actually happening?
fail
ERROR  command failed: pnpm install --loglevel error --shamefully-flatten

on windows ,i was success but macos.
i want to know "ERROR  command failed: pnpm install --loglevel error --shamefully-flatten"
when install pnpm ,run 'vue create', still fail,

If you are in China, it's very likely the error is caused by the taobao npm registry.
I haven't figured out why but changing the registry from https://registry.npm.taobao.org/ to https://r.cnpmjs.org/ fixed this issue on my machine.

If you are in China, it's very likely the error is caused by the taobao npm registry.
I haven't figured out why but changing the registry from https://registry.npm.taobao.org/ to https://r.cnpmjs.org/ fixed this issue on my machine.

thank you for your answer.
i changed registry,it still doesn`t work.
now ,i create the demo on windows ,then copy it in macos ，it work.
forgive my Chinglish.

@qq229338869
Try edit ~/.vuerc and change the useTaobaoRegistry option to false.
Also, are you sure you have pnpm installed?

Fixed. See https://github.com/cnpm/cnpmjs.org/issues/1458

repo: vuejs/vue-cli


text:
Vue delimiters does not work with golang

hi great job
but
Golang uses {{}}
vuejs uses {{}}
I change delimiters
new Vue({
delimiters: ['${', '}']
})
but not working with golang

Hello @AttSee
Thank your for your interest in this project.
However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests (as outlined in our Contributing Guide).
We encourage you to ask it on the forum  , Stack Overflow or on gitter and are happy to help you out there.

The docs has a great search. We encourage you to use them: https://vuejs.org/v2/api/#delimiters

authors: AttSee LinusBorg posva


text:
SFC based on TS and  vue-property-decorator does not generate d.ts file

Version
3.5.5
Reproduction link
https://github.com/MikeMitterer/vue-cmp-liveforce
Environment info
  System:
    OS: macOS 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
  Binaries:
    Node: 12.12.0 - /usr/local/bin/node
    Yarn: 1.16.0
    npm: 6.11.3 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
    Safari: Not Found
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.1.2
    @vue/babel-preset-app:  4.0.5
    @vue/babel-preset-jsx:  1.1.2
    @vue/babel-sugar-functional-vue:  1.1.2
    @vue/babel-sugar-inject-h:  1.1.2
    @vue/babel-sugar-v-model:  1.1.2
    @vue/babel-sugar-v-on:  1.1.2
    @vue/cli-overlay:  4.0.5
    @vue/cli-plugin-babel: ^4.0.5 => 4.0.5
    @vue/cli-plugin-router:  4.0.5
    @vue/cli-plugin-typescript: ^4.0.5 => 4.0.5
    @vue/cli-plugin-unit-jest: ^4.0.5 => 4.0.5
    @vue/cli-plugin-vuex:  4.0.5
    @vue/cli-service: ^4.0.5 => 4.0.5
    @vue/cli-shared-utils:  4.0.5
    @vue/component-compiler-utils:  3.0.2
    @vue/preload-webpack-plugin:  1.1.1
    @vue/test-utils: ^1.0.0-beta.29 => 1.0.0-beta.29
    @vue/web-component-wrapper:  1.2.0
    jest-serializer-vue:  2.0.2
    typescript: ^3.7.2 => 3.7.2
    vue: ^2.6.10 => 2.6.10
    vue-class-component: ^7.1.0 => 7.1.0
    vue-hot-reload-api:  2.3.4
    vue-jest: ^3.0.5 => 3.0.5
    vue-loader:  15.7.2
    vue-property-decorator: ^8.3.0 => 8.3.0
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.10 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 3.0.0

Steps to reproduce
yarn run build
What is expected?
Should produce a d.ts file to import the component
What is actually happening?
Generates a MLiveForce.common.js but nothing TS specific.
The problem is that without a .d.ts file the component can't be imported. WebStorm says "Cannot find module xxx"

Duplicate of https://github.com/vuejs/vue-cli/issues/1081

authors: MikeMitterer sodatea


text:
Unify next() for beforeRouteUpdate  and beforeRouteEnter

What problem does this feature solve?
Hi there,
it would make our code base simpler if we received vm in beforeRouteUpdate too even though this method already has access to this. Then if the same logic applies for beforeRouteUpdate and beforeRouteEnter  it could be handled uniformly in one method only:
beforeRouteUpdate(to, from, next){
   handleRouteChange(to, from, next)
},

beforeRouteEnter(to, from, next){
   handleRouteChange(to, from, next)
}

Yes, sometimes you need to handle both the methods in a different way but if not this is a nice short cut. Is it possible to do it in Vue.js or not?
Kind regards,
Nobo
What does the proposed API look like?
Hi there,
it would make our code base simpler if we received vm in beforeRouteUpdate too even though this method already has access to this. Then if the same logic applies for beforeRouteUpdate and beforeRouteEnter  it could be handled uniformly in one method only:
beforeRouteUpdate(to, from, next){
   handleRouteChange(to, from, next)
},

beforeRouteEnter(to, from, next){
   handleRouteChange(to, from, next)
}

Yes, sometimes you need to handle both the methods in a different way but if not this is a nice short cut. Is it possible to do it in Vue.js or not?
Kind regards,
Nobo

dup of #1582

Reopening for further discussion following https://github.com/vuejs/vue-router/issues/1582#issuecomment-325031283

authors: LinusBorg posva zatziky

repo: vuejs/vue-router


text:
Support for md templates

It would be nice if markdown templates were highlighted:
<template lang="md">
	# Markdown test page
</template>

Hello @kennethjor
We try to stick and only support languages supported by the official vue component syntax. This definitely is something that might be useful, but at this time I don't think we can add this in. Thank you for your suggestion.

authors: kennethjor skyronic

repo: vuejs/vue-syntax-highlight


text:
Inconsistent documentation or behaviour of vm.$watch

Vue.js version
2.0.2
The following code produces the following error on the console:
const app = new Vue({
    el: '#app',
    // template: '#app-template',
    data: {
        height: 0,
        weight: 0,
    },
// ....
});
app.$watch('weight + height', function () {
  // do something
});

vue.js:2611[Vue warn]: Failed watching path: "weight + height" Watcher only accepts simple dot-delimited paths. For full control, use a function instead.

OTOH the documentation (https://vuejs.org/v2/api/#vm-watch) explicitely states that it's a valid syntax. It even has the same example.

Thanks @atleta ,  the document needs to be updated

moved to vuejs.org

A PR created. https://github.com/vuejs/vuejs.org/pull/570 .

authors: atleta defcc yyx990803

repo: vuejs/vue


text:
Add async option

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

Other information:
Closes #8200
We can use this in Vue Test Utils to run tests synchronously without editing Vue internals

Do you think it would make sense to use an ENV variable so it is completely stripped out in normal builds?

what's up with this amazing feature?

Waiting for that too, Vuetify is near impossible to test on vue-test-utils.
I'm seeing errors related to _transitionClasses not defined everywhere.

Is this still going into 2.6?

It should be out in 2.5.18

@eddyerburgh is there any ETA on 2.5.18 ?

authors: aldarund benirose eddyerburgh posva sobrinho trollepierre


text:
Sidebar Example - Locale

Added an example for rendering different sidebar options based on locale

Thanks, but the recommended way is to put it under different locales.
themeConfig: {
  locales: {
    '/': {
      sidebar: ...
    },
    '/zh/': {
      sidebar: ...
    },
  },
}

authors: bacon-delight meteorlxy

repo: vuepress/vuepress-next


text:
tags are removed before being refreshed on load

This line removes all link tags that aren't controlled by vueuse/head: https://github.com/vueuse/head/blob/392e8c8ca91df27d9b067dad8c2d9886b53ac756/src/index.ts#L208
If I remove that then this section does the same thing when run by vite-ssg because querySelector('link[key="null"]') just returns the first <link> due to a jsdom bug:
https://github.com/vueuse/head/blob/392e8c8ca91df27d9b067dad8c2d9886b53ac756/src/index.ts#L213-L218
Originally posted by @KaelWD in https://github.com/vueuse/head/issues/45#issuecomment-996908307

in fact I think this may be a downstream issue: https://github.com/nuxt/framework/pull/3212

My original comment was in the vuetify docs with just vite-ssg.

Related https://github.com/vueuse/head/issues/75

Seems like this may be fixed given the above comment, otherwise it's a duplicate of #75.
Feel free to re-open if that's not the case.

authors: KaelWD danielroe harlan-zw

repo: vueuse/head


text:
Liveseo has nice stuff

googlesuggestfield.js – I think it's ideal for "set keyword focus". Some kind a stars / points – also will be nice.
EDIT: After change Title and publish – 'Search Preview' needs to be refreshed to see changes (F5).

It already refreshes on save, whether published or not, but I agree with you that it'd be better to have the analysis lives just need to figure out a way to make it very simple for developers to contribute, as the best sales point of this module is the ability to create your own analyses very easily

repo: vulcandigital/silverstripe-seo


text:
huge PR - skiasharp support

Hi guys!
First of all thank you for this svg library - it is just great!
A while ago, I forked this library with the goal to get it to run on android.
Meanwhile, we are using SkiaSharp  for rendering.
This allows us to render on Android, iOS, Mac, Windows (and UWP) so basically everything except Linux.
Also, Skia supports hardware-rendering (OpenGL and Angle to translate the OpenGL calls to DirectX).
However, we did not just rip all the "System.Drawing" stuff out and replaced it, but refactored it into a factory with our own interfaces, so that you can (literally) stuff in any other render library you like.
My question is: Are you basically interested in merging this in?
As we changed a lot (e.g. removed all TypeDescriptor stuff as this is not supported on UWP) so merging will be quite tedious.
On the other hand, I see a lot of benefits for you guys too.
In that case, please reach out to me.
Our repository is: https://github.com/gentledepp/SVG
The latest branch with plattform support is https://github.com/gentledepp/SVG/tree/uwp_ios
Cheers!

hello, this sounds totally interesting and actually we are also planning to use SkiaSharp internally in other projects. so that would fit quite well.
i'll discuss it with my colleagues and get back to you.

Great - the build is actually already working and our tests run on ios, android, uwp and windows.
Maybe we could arrange a skype chat sometime. (I am based in Austria, ... also sollten wir kein Zeitzonenproblem haben ;-))

we had a short chat about the merge and came to the conclusion, that it would be better for us to schedule the merge bit further. even as far as july/august since we are preparing for a big event.
the merge could take a week or more of work. also a GDI implementation or at least forms adapter is needed...

sure - I am not in a hurry at all.
My skype nickname is the same as my github name.
Feel free to drop me a line ;-)

hello @gentledepp how is the status of the fork on your end? do you still maintain it?
maybe its more easy to release a final version of this master branch and then completely switch to yours. some PRs might get lost, but overall your branch looks like the was to go.

Hi!
Yes, it is still mainained.
However, we are only supporting a "PCL" version.
There are no plans for porting to .NET Core at the moment

great, thanks for the update!

What are your plans now?
We are happy to help lifting this codebase to a new level 👍

@tebjan - can you elaborate about your plans? If you plan to switch to / integrate with the skiasharp branch, this may have change the priorities of the other issues, or make them obsolete.

ideally we would merge the current master with the skiasharp master and combine all fixes. however, this sounds like a huge job and i am not sure whether we have enough time for that.
i could also imagine to get the latest PRs regarding netstandard into master, releasing a few more fixes for the nuget 2 and prepare a version 3 which is based on skia.
however, if @mrbean-bremen and @gentledepp are up for the task of merging, i'll do my best in order to support it.

This looks like a huge task, as the code bases seem to have deviated sufficiently.
Before starting this, we have to know where we want to go - e.g. what about .NET compatibility (which is not available in the skiasharp branch, as far as I understand, but in the long run will go away anyway).
Also, I read that PCL is deprecated in favor of netstandard, so we may want to go to netstandard directly. As has been discussed in another issue, netstandard compatibility for .NET Core seems not to be far away, so maybe this is something we can wait for while we sort out a merge strategy. Increasing the test coverage for different platform is also something that has to be considered IMHO.
Unfortunately, I myself have basically no experience in the related technologies - I'm only using .NET, and only under Windows so far (and only occassionally, most of the time using C++/Qt and Python), so while I'm willing to help, I'm hoping for you (@tebjan) and @gentledepp (and whoever is working on skiasharp now) to lead the work and make the decisions.

authors: gentledepp mrbean-bremen tebjan

repo: vvvv/SVG

license: MS-PL


text:
Running in RHEL

Didn't work
I am not sure if it's specific to ubutu, you need to mention
it did bunch of things and than removed containers

Can you explain what happened? I am unable to understand how it will remove containers. Moreover, the base image I am used is debian. I crafted the Dockerfile such that it would help me build a docker image with hadoop & hive together to ease my test process.

authors: mranjank vyanamandra


text:
Add hdevtools linter for haskell

This adds support for the hdevtools haskell linter
https://github.com/hdevtools/hdevtools
The output for hdevtools is near identical to the ghc output so this
also extracts the ghc handler into the handle file and adds tests

Cheers! :beers:


text:
[WIP] Begin to distinguish between Perl warnings and errors

This is a work in progress, but I was interested in getting some feedback.
The biggest change here is, I think, not clobbering messages from previous line numbers.  I could also change this to concatenate the messages rather than letting the first one win.

I think I've addressed all of the issues cited above.  I'd like to live with this for a few days before I remove the WIP label.  If this looks ok, would you like the commits squashed?

BTW, I had no problems running ./run-tests from my Mac.  Worked like a charm.

Cheers! :beers:

Thanks @w0rp!


text:
Consider to allow an implementer to publish a manifest instead of committing the manifest in the directory

It would be nice to give an implementer more freedom to operationally change [test]manifest. This way, it could evolve in a general manifest [services discovery], and also, it would be a great demonstration of using linked data, by starting just with one endpoint pointing to the manifest that an implementer has provided.

if you would be in a playful mood then the manifest could be signed and wrapped as VC ;) to support possible future direction focusing on a discovery. It could have an impact on wallets, etc. e.g. a wallet could download "trusted" verifier configuration, the manifest.

I definitely like where this could head and what doors it would open. Sadly, "for now" (however endless that may be...), I think we'll have to stay the course on committing/storing them here to keep the focus on building the actual test suites.
Definitely open to discussing the idea, though!

Well, sometimes you have to open the door just to see what's behind ;)  I see no risk as long as an implementer is interested to pass a test suite, i.e. to provide a correct, processable, manifest.


text:
Added 2 nodes of 1 candidate

Added:

2 nodes of @plussik:matrix.org

@ironoa Element handle of the user was verified


text:
GetSmart - Web3 digital achievement badges

Hi, I'm Josh, as host of CryptoMondays Global, I'm well connected in the industry, including with Unfinished and Unique Network and believe in the vision of a decentralized web.
My team built a game-changing platform using ERC1155 that enables the first decentralized digital badges as NFTs, without a third party issuer or data control.  We went farther and made it possible for fungible tokens to be linked to the digital badge, thus making also the first viable tool for decentralized scholarships and education funding.
I am considering building this either on a separate (para) chain or bridging to polkadot chains, but we don't have the technical capacity to decide.  We would seek a grant to fund the project.
An overview of the system is here: https://get-smart.net/nft-awards/
(also a whitepaper there)
The fully functioning platform is currently on Rinkeby testnet here:  https://getsmart.lapits.com
The key issue is how to replicate an ERC1155 on polkadot where the sponsor can create and issue "tokenized credentials"
Thanks for any help!
drawings_lange_credential_260722_final.pdf

Hi @get-smart-token. There is a standardization proposal for ERC1155-type tokens in ink! here. It's still in draft, but the reference implementation is part of OpenBrush, which is well documented: openbrush.io.

I'm closing this issue due to inactivity. Let me know if you have any further questions.

authors: get-smart-token semuelle


text:
LIP payments pallet

Project Abstract
This is a amendment successor to our initial PLIP proposal to accommodate to the update scope of the Virto Network(previously Valibre).
This proposal focuses on the core primitive of the Virto Network, the payments pallet that will enable our mission of providing decentralized infrastructure for marketplaces with local impact.
For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

 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.

Thanks for the submission, @olanod. We use the term 'amendment' for minor changes to an existing grant. Given that the scope and funds in this proposal are quite different from your previous grant (#520), I have replaced the term in your PR above. It also means that the previous grant will be cancelled if this application is accepted. That's just a technicality, though.

@Noc2 yes we did greatly underestimate our costs of development and timelines(as we developers usually do). Being a project we've been working on for almost the entire year going through different phases of redesign and iteration, the proposal might not even reflect the actual costs of development.
We believe our single pallet that represents the core of our technology will be of great benefit to the community and hope it can become the enabling primitive that will connect projects in the ecosystem and give crypto in general utility in the real world :)

Thanks for the feedback :) No problem updating the price to something that feels more suitable, right now our team values more the "Web3 grant" status than its profitability. Wanted to note that by no means we are trying to cover 100% of our (non-so-)early-stage funding, perhaps I'll also mention "self-funding" and my previous affiliation with Valiu in the last section of the document to reflect better the effort put in the project for the past couple of years.
Just sharing thoughts and context, I guess in my effort to reduce the scope of our application to make it more digestible and simpler to asses I made the mistake to make it look too simple, sometimes it's actually harder to write less code which I think It's the case with payments pallet, we went from a whole chain with multiple pallets doing one thing(on&off ramps) to a slick general purpose pallet that fits well in any chain and can have way more use cases, all thanks to not rushing and taking time to gather feedback from real non crypto users that are the ones that will ultimately benefit from what we're building.
For the price adjustment, the estimation was based only on the time spent last couple of months and 1 FTE -> 80kUSD/h(I've rejected Rust/Substrate offers higher than that😳 ... blame desperate teams I guess? 😅). With a lower rate of 1 FTE -> 60??USD/h the total value would be 36000 kUSD, does it look more appropriate?.
One last thing, what does core infrastructure look like? we have hopes to continue breaking down our infrastructure in smaller pieces that can apply for grants, perhaps is not the best approach? it's been a goal from the begging to try to keep Virto Network "pure" and not depend(for now) on institutional investment but I'm not sure now it's the best thing to do.

Looks good to me @olanod. Could you also add an article to the milestone 2 deliverables, similar to delivery 0e. in the template? This is generally mandatory for all grants and we can provide feedback on it as well as cross-promote it.

An article as in a blog post in our site that talks about what was built and how the Web3 grant made our dreams come true, etc? :)

Correct. The second part is up to you, but if it did, you should definitely mention it ;)

Could you expand on the details of your deliverables of Milestone 1?
E.g. Escrow functionality is a broad term - please describe how you envision this being implemented in substrate. What I'm looking for is an idea of what kind of storage you will need, and what public interface your substrate modules will have.

@mmagician Since milestone 1 code is complete a good reference is the pallet readme and the code itself. Elaborating a bit more here, the escrow works by transferring funds to the recipient and holding the assets until the sending account calls a second extrinsic to release the funds(e.g. user received a product, bank transfer, etc). Users have an incentive to release the funds because the payment includes a fee that is returned to the user after the release, also each payment gets assigned a "judge" account via a configurable handler to resolve any disputes.
Let me know if I should include further details or write it in the proposal document

authors: CLAassistant alxs mmagician olanod semuelle


text:
Allow specifying search boost values for individual blocks within StreamField

Is your proposal related to a problem?
When indexing the contents of a StreamField for searching, all content is given equal weighting - boost values can only be set on the SearchField definition, which applies to the StreamField as a whole. This means that you can't give heading blocks higher weighting than paragraph blocks, for example.
Describe the solution you'd like
Block classes should accept a search_boost parameter that applies the relevant boost to content using that block:
StreamBlock([
    ('heading', CharBlock(search_boost=2)),
    ('paragraph', RichTextBlock())
])

Describe alternatives you've considered
I briefly thought it might be possible to 'fake' boosting by returning multiple copies of the block's content in get_searchable_content:
class HeadingBlock(StructBlock):
    def get_searchable_content(self, value):
        return super().get_searchable_content(value) * 3

This has some effect, but nowhere near as much as a real boost value (which makes sense... if the entire streamfield content is a 10,000 word novel, a couple of extra repeats of the keywords from headings isn't going to make much difference).
Proposed implementation

All blocks that provide a search_index parameter, and implement a get_searchable_content method, will add a 'boost' parameter (and this should be documented at reference/streamfield/blocks.md)

The API of get_searchable_content will be updated so that rather than returning a list of strings to be indexed, it will return a dict of lists of strings, indexed by boost value. So, for example, a block defined as:
StreamBlock([
    ('heading', CharBlock(search_boost=2)),
    ('paragraph', RichTextBlock())
])

might return a value such as
{
    2.0: ["first heading"],
    1.0: ["first paragraph", "second paragraph"],
}

In the case that a block is recursively calling get_searchable_content on its children, and that block has a boost value itself, the boost values returned by the children will be multiplied by the block's own boost value in the returned result.

To accommodate third-party code that implements get_searchable_content according to the old definition, all code calling get_searchable_content must gracefully handle a list being returned, and treat ["some", "list"] as equivalent to {1.0: ["some", "list"]}.

As an alternative to this 'dict of lists' data structure, we might consider introducing a dedicated 'SearchableContent' object type that stores the same data but also provides utility methods to assist with these merging / multiplying operations.

Blocks will also implement a unique_boosts method or property, which returns the set of boost values that can potentially appear as keys in the get_searchable_content result for that block, taking any multiplication into account. For example, the above StreamBlock definition would return {1.0, 2.0}. This is to assist search backends that need to initialise their indexes with the expected boost values before indexing any documents.

StreamField will also provide a unique_boosts method/property that simply returns the result from its top-level block (as it already does for get_searchable_content).

Within wagtail.search.index, BaseField or SearchField (not sure which is more appropriate) will provide a way to retrieve the field's searchable content in the new SearchableContent / dict representation - this will call the underlying field's get_searchable_content if it provides one (which will only be the case for StreamField) and multiply by its own boost value, or construct its own result consisting of {self.boost: field_value} if not. I think this will be a new get_value_with_boosts method (or perhaps it should be named get_searchable_content too?), living alongside the existing BaseField.get_value method so that FilterField can continue working with the non-boosted value (and also so that we don't break third-party search backends) - which means that BaseField.get_value also needs to be updated to account for get_searchable_content returning the new representation and convert it back to a plain value.

SearchField will also provide a unique_boosts method/property that returns the underlying field's unique_boosts if it provides one - multiplied by its own boost value - or just its own boost value if not.

Finally, all search backends will need to be audited for their use of boost and get_value, so that rather than assuming that each SearchField has a single fixed boost value, they check the SearchField's unique_boosts and get_value_with_boosts methods. This is hopefully not a massive leap from what the search backend is doing already for indexing RelatedFields (where we have a single entry in search_fields that yields multiple values at potentially different boost values). From an initial look:

wagtail.search.backends.database.postgres.weights.get_boosts should use search_field.unique_boosts instead of search_field.boost
Within wagtail.search.backends.database.postgres.postgres.ObjectIndexer, prepare_field on a SearchField will yield multiple values, one for each entry in the get_value_with_boosts dict
Support for index-time boosting on the MySQL and Sqlite backends seems to be unfinished, as far as I can see - ObjectIndexer.prepare_field yields tuples of (field, value) where the corresponding method on the Postgres backend yields (field, boost, value), and the as_vector method exists but is never called and doesn't return a SearchVector anyhow - the strings returned from prepare_field are just concatenated instead. Please confirm that this is indeed not working (and if it looks like a quick fix, by all means fix it, but otherwise that's out of scope...)
Elasticsearch doesn't support index-time boosting, so we have to fake it by creating additional fields in the index named "_all_text_boost_N" to contain all text with a boost value of N, and applying a boost of N on that field at query time. There's also a separate code path (in Elasticsearch7SearchQueryCompiler._remap_fields) for searches that specify explicit fields, such as ArticlePage.objects.search("foo", fields=["title", "body"]) - up to now each field in that list equated to one field of the index to search on (with the appropriate boost value for the field applied at query time), but now this will become a one-to-many relation for fields with multiple values in unique_boosts, with the index including fields like "body_boost_N" for each of the field's unique boosts.

At indexing time, there's a tricky dance to construct the mapping (the 'schema' for the documents in the index) where get_field_mapping temporarily tags the fields with "include_in_all" and "boost" attributes, which then get dropped in replace_include_in_all as we walk over the tree a second time, inserting the rules for copying values into the "_all_text_boost_N" fields and assembling a unique_boosts set for the whole document. I think the right way to patch this is to have get_field_mapping return multiple results, one for each unique_boosts value, ensuring that each result is given a unique name of the form "body_boost_N" in the case that unique_boosts has more than one value. From there, the rest of the code will do the right thing with the document-wide unique_boosts and copy_to rules.
get_document should then be updated to call SearchField.get_value_with_boosts in place of get_value, and for fields with multiple unique_boosts, ensure that the content is directed to the appropriate "body_boost_N" field.
At query time, the logic for searching on explicit fields (the if fields branch of _remap_fields) should be updated so that whenever field.unique_boosts has multiple values, we add multiple Field entries to remapped_fields with the relevant boost value and unique-ified "body_boost_N" name. The logic for searching all fields will be mostly unchanged, but just needs to look at field.unique_boosts instead of field.boost when building the document-wide unique_boosts.

I'm working on this

authors: gasman jayanth-kumar-morem

repo: wagtail/wagtail


text:
Added switch method in ZoneController & Fix 12611

Please describe the problem you're fixing here. Include the issue number, if applicable.
Changes in code
This PR resolved #12609 & #12611 and contains changes on top of the commit  by @lb-
Screenshots

Intial states

After changing to public (No reloading page)

Switching in collection

https://github.com/user-attachments/assets/ffe5984c-a08c-40e2-8936-395b3c25fa48

Rebased and resolved all conversation, everything works as same attached file in PR (also as expected) and as there was change in modeValueChanged method here is drag&drop highlighting screenshots (works fine):
https://github.com/user-attachments/assets/a2d2b300-4777-41ca-9b57-b2121e7cf386

I'll do a full walkthrough of the code locally tomorrow, just added two more items I noticed. Thanks so much @ayaan-qadri

authors: ayaan-qadri lb-


text:
🛑 cyconet.org is down

In 01c4ba1, cyconet.org (https://www.cyconet.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cyconet.org is back up in c55ce0d after 2 hours, 45 minutes.

repo: waja/cyconet-upptime


text:
Release v1.25.1

Changelog:

Logging improvements for api errors #543

Hold on there's a pending PR we could aggregate into this. #545

authors: alanhamlett gandarez

repo: wakatime/wakatime-cli


text:
🍱 Adds AVG Management

Add Logo for AVG Management Console
Just PNG.

Thanks! Feel free to add a PR to add a copy named avg-management-console too.

repo: walkxcode/dashboard-icons


text:
[Q] Can't create a team after deleting one in an org

Hi,
I first created a corporate team. Realizing it has a trial period, I deleted the team, but the org is still there. Then, I changed the corporate org to an academic org; but now when I try to create a new team, the button isn't pressable. I'm not sure what I'm doing wrong. My profile link is: https://wandb.ai/tsc003

Hey @t-sekai , are you able to see the Teams panel on the bottom left in the UI like this:

Upon clicking Create a team to collaborate, you should be able to see a modal pop up on the right hand side in the UI:

Upon filling in the team details, you should be able to create a team. If this is not the case for you, could you please create a screen recording of what issue you are facing and send it our way so that we can further investigate into the issue?

I've tried the steps above, but the "Create team" button is unclickable before and after I enter the team name.

Hey @t-sekai , apologies for the confusion. If you are a part of an academic org (and a team in that org) already, you cannot create a new team in another academic org. I've relayed this discrepancy to our product team as well and out team will be updating the messaging in the UI shortly to reflect the same.

I understand the problem now. Can you help me delete the hm_gesture-org from my account? It's no longer useful.

Hey @t-sekai , hm_gesture-org is now deleted.

authors: anmolmann t-sekai

repo: wandb/wandb


text:
[Q]: Why I cannot connect the wandb? with CommError: It appears that you do not have permission to access the requested resource.

Ask your question

I connect wandb in colab env.
but When I call wandb.init(), then that error occured

how can i fixed it?
'ps'
I installed wandb==0.17.9 version

my account email is falconlee236@gmail.com

Hi @falconlee236 Good day and thank you for reaching out to us. Happy to help you on this!
Can you try to specify the entity on your wandb.init call? Let me know if this allows you to log your experiment.

Hi @falconlee236 Good day and thank you for reaching out to us. Happy to help you on this!
Can you try to specify the entity on your wandb.init call? Let me know if this allows you to log your experiment.

the wandb.init() method in colab is always specifiy entity, mode, project, name parameters
#Comment following two lines if you don't want logging
from lightning.pytorch.loggers import WandbLogger

run = wandb.init(
    entity="OptiMap",
    mode="online",
    project="test",
    name="advrp-cv"
)

logger = WandbLogger()

but almost tutorial of wandb with colab env is only use init function without other parameters.
I was so confused of that parameters was optional parameters anyway.
Do you change that parameters not optional parameter?
Or I gonna change that parameters necessary
@paulosabile-wb

Hi! @paulosabile-wb , @kptkin
Can I change     project, enttiy, mode parameters in python api?
and also this api docs change too.
If you approved. i gonna change my modification.
def init(
    job_type: Optional[str] = None,
    dir: Optional[StrPath] = None,
    config: Union[Dict, str, None] = None,
    project: str = None, # changed
    entity: str = None, # changed
    reinit: Optional[bool] = None,
    tags: Optional[Sequence] = None,
    group: Optional[str] = None,
    name: Optional[str] = None,
    notes: Optional[str] = None,
    magic: Optional[Union[dict, str, bool]] = None,
    config_exclude_keys: Optional[List[str]] = None,
    config_include_keys: Optional[List[str]] = None,
    anonymous: Optional[str] = None,
    mode: str = "online", # changed -> default is online in api docs.
    allow_val_change: Optional[bool] = None,
    resume: Optional[Union[bool, str]] = None,
    force: Optional[bool] = None,
    tensorboard: Optional[bool] = None,  # alias for sync_tensorboard
    sync_tensorboard: Optional[bool] = None,
    monitor_gym: Optional[bool] = None,
    save_code: Optional[bool] = None,
    id: Optional[str] = None,
    fork_from: Optional[str] = None,
    resume_from: Optional[str] = None,
    settings: Union[Settings, Dict[str, Any], None] = None,
) -> Run:

https://github.com/wandb/wandb/blob/v0.18.0/wandb/sdk/wandb_init.py#L979-L1249

Hi @falconlee236 Good day and thanks for your follow up suggestions here.
Upon checking in Collab, if you try to run wandb.init without the entity parameter, it should trigger wandb.login and you will be asked to enter your API key so you can proceed. The API key should allow the wandb service to identify which entity is this run for and this should prevent you from getting any permission errors.
When you tried to run your experiment using Collab, did you try to run wandb.login before executing wandb.init? I'd like to confirm as well which collab tutorial are you using so I can also review, if you can share a URL that can help me review the setup.
Thank you!

Hi @paulosabile-wb .
After your commented, The problem was absolutely resolved. How to fix the bug? What kind of the PR you uploaded concerning this Issue?
If you don't change about this code. You should close this issue.
This situation was so wired..


text:
the labels of camvid

@wanghao9610 Hello!The size of the trained model you gave is different from the size I trained .I looked at the difference.What is the difference between a Memory Head and a TMANet？
您好！您给出的训练好的模型大小和我训练出来的大小不太一样。我看了一下区别，请问Memory Head和TMA Head有什么区别吗？

Thank you for your reply!


text:
关于参数传递的问题

目前是keys和values一一对应来传递，请问一下如果一个controller有多个参数的时候应该如何传递？

建议通过：
- (__kindof UIViewController *)pageController:(WMPageController *)pageController viewControllerAtIndex:(NSInteger)index {
    // Initialize view controller..
    // ...
    vc.foo = foo;
    vc.bar = bar;
    return vc;
}

恩，当时没注意，我目前是在子控制器里通过通过代理返回参数的

另外还有一个问题，就是系统左滑的时候会出现scrollview和controller同时接收滑动事件的情况，如何在这个时候禁止scrollView的滑动呢？self.scrollView.otherGestureRecognizerSimultaneously = YES;这个属性貌似不好用

authors: MoonLht wangmchn

repo: wangmchn/WMPageController


text:
Query results returning cut off values at 63 bytes

When querying a table (in this case SELECT schemaname, tablename FROM pg_catalog.pg_tables), the returned values get cut off at 63 characters. When I inspect the column property from the result, I see columnSize: 63, however, this does not appear to be the case with the underlying table. When I look at the table in a SQL client (e.g. Postico), the full values are present in the table, and the columns do not show size constraints.
Rows:
  {
    "schemaname": "example",
    "tablename": "this_is_fine"
  },
  {
    "schemaname": "example",
    "tablename": "this_table_is_an_example_of_something_that_gets_cut_off_too_ear"
  },

Column metadata:
columns: [
  {
    name: 'schemaname',
    dataType: -9,
    columnSize: 63,
    decimalDigits: 0,
    nullable: true
  },
  {
    name: 'tablename',
    dataType: -9,
    columnSize: 63,
    decimalDigits: 0,
    nullable: true
  }
]

Could this be coming from node-odbc, or might this be an issue with the underlying driver? Or with ODBC itself?
In case it's relevant, I'm using the Redshift driver.

Hey @bencmbrook ,
This looks like a odbc v2.x issue. That repo is over here: https://github.com/markdirish/node-odbc/issues/
Would you mind posting there? Thanks!

Oh, woops! Keep getting these links mixed. Posting there in a moment. Thanks for the redirect

authors: bencmbrook markdirish

repo: wankdanker/node-odbc


text:
[FEATURE 💡] Cart Functionality

Description
Add cart Functionality to the website. Use dummy json data for reference
Screenshots
No response
Additional information
Make sure to read the CONTRIBUTING and SETUP docs before proceeding
Happy contributing. 💐
Star my other Repositories here

can we do something with local data and then local storage seems to be the only solution now.

yes sure, do you have any dummy data?

Can you create a dummy data for now.

cool, please assign


text:
[FEATURE] Add regex for alternate typo of onchanges

Add to the existing rule to catch onchanges typos:
on_change:
on_change_any:
on_change_in:
on_changes:
on_changes_any:
on_changes_in:

@jbouter @sblaisot @roaldnefs could one of you you take a look at this PR? or could you point me in the direction of someone who could help? Thanks in advance.

repo: warpnet/salt-lint


text:
Add feature handle group

#17
In this feature can send massage based on gitlab group project, using helper GroupDetection() see helper
Work well with push request

Work well in push and merge request

In push request, helper read Repository URL and split url string, in pushhandler() there is a switch case that receives a return from the helper and sends it according to the workplace group
In merge request, helper read SSH URL and split url string, in mergehandler()  there is a switch case that receives a return from the helper and sends it according to the workplace group

Please change Thread channel in each helper before using it in production
Q: Why push and merge hash different input variable ?
A: Because push and merge has different struct, so possible way to get group information by repository url in push request, and ssh url in merge request

repo: warungpintar/workplace-incoming-hook


text:
Io Error: UnexpectedEof "failed to fill whole buffer" after writing many files

I'm getting a strange error after attempting to open, read, and/or write many files. After about 20-25 writes I start getting the following error
Panicked at 'called `Result::unwrap()` on an `Err` value: Io(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })', stable-fs-0.1.11/src/storage/types.rs:85:51

Even after doing a redeploy I am still unable to open any additional files after I hit what feels like some sort of limit.
Here is a simple canister that illustrates the problem.
After running dfx cansiter call canister write_25_files once it cannot be called again without this error popping up. Nor can read_25_file be called without this same error.
use std::{
    cell::RefCell,
    io::{self, Read, Write},
};

use ic_stable_structures::{
    memory_manager::{MemoryId, MemoryManager},
    DefaultMemoryImpl,
};

thread_local! {
    static MEMORY_MANAGER_REF_CELL: RefCell<MemoryManager<DefaultMemoryImpl>> = RefCell::new(MemoryManager::init(DefaultMemoryImpl::default()));
}

#[ic_cdk::init]
fn my_init() {
    let polyfill_memory =
        MEMORY_MANAGER_REF_CELL.with(|manager| manager.borrow().get(MemoryId::new(0)));
    ic_wasi_polyfill::init_with_memory(&[], &[], polyfill_memory);
}

#[ic_cdk::post_upgrade]
fn my_post_upgrade() {
    let polyfill_memory =
        MEMORY_MANAGER_REF_CELL.with(|thing| thing.borrow().get(MemoryId::new(0)));
    ic_wasi_polyfill::init_with_memory(&[], &[], polyfill_memory);
}

#[ic_cdk::update]
pub fn write_25_files() {
    let dir_name = "auto";
    let file_count: u8 = 25;
    std::fs::create_dir_all(dir_name).unwrap();
    for i in 0..file_count {
        let path = format!("{}/my_file_{}.txt", dir_name, i);
        ic_cdk::println!("Writing to {}", path);

        let mut file = std::fs::OpenOptions::new()
            .create(true)
            .write(true)
            .open(&path)
            .unwrap();
        let write_buff = [i; SIZE_OF_FILE];
        file.write(&write_buff).unwrap();
        drop(file);
    }
}

#[ic_cdk::update]
pub fn read_25_files() {
    let dir_name = "auto";
    let file_count: u8 = 25;
    std::fs::create_dir_all(dir_name).unwrap();
    for i in 0..file_count {
        let path = format!("{}/my_file_{}.txt", dir_name, i);
        ic_cdk::println!("Writing to {}", path);

        let mut file = std::fs::OpenOptions::new()
            .create(true)
            .read(true)
            .open(&path)
            .unwrap();
        let mut read_buf = [1, 1, 1];
        let num_bytes = file.read(&mut read_buf).unwrap();
        ic_cdk::println!("Read {} bytes {}", num_bytes, path);
    }
}

I will have a look, but note, stable-fs v 0.1.11 has issues with the readdir implementation, it could cause errors when you work with multiple files. Please, try the latest version available from both the ic-wasi-polyfill (v0.3.17) and the stable-fs (v0.2.0).

Thanks for the heads up! I tried the latest version and still got the same error
The replica returned a replica error: reject code CanisterError, reject message Canister bkyz2-fmaaa-aaaaa-qaaaq-cai trapped explicitly: Panicked at 'called `Result::unwrap()` on an `Err` value: Io(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })', stable-fs-0.2.0/src/storage/types.rs:85:51, error code None

Hi Benjamin,
I've repeated running the same methods without errors (first writing 25 files, then reading 25 files, with and without upgrade). Which version of ic-stable-structures are you using? Apparently I am still missing some parts of your project (I assumed SIZE_OF_FILE is 300). Also, the error message is referencing src/storage/types.rs:85:51, the line does not exist in the original source code (does it?). Maybe try to check the ic-stable-structures is at least version 0.6.3 or send me more sources of your project.

Oh woops, sorry I forgot to include SIZE_OF_FILE. I have it at 1_000_000. That should make all of the difference. With something as small as 300 I am also not ever running into the problem, at least not quickly.
I double checked everything and it looks like that was the only thing I missed.
Here is my Cargo.toml to be sure.
[package]
name = "globals_and_memory"
version = "0.1.0"
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[lib]
crate-type = ["cdylib"]

[dependencies]
serde = '1.0.193'

candid = "0.10.5"
ic-cdk = "0.13.1"
ic-wasi-polyfill = { git = "https://github.com/wasm-forge/ic-wasi-polyfill", rev = "870e2cd0b533c03a45dbd3a516176a1fe261cea6", features = [
    "transient",
]}

ic-stable-structures = "0.6.3"

As for src/storage/types.rs:85:51 I was looking at that here https://github.com/wasm-forge/stable-fs/blob/4e3cb3b20b199d6ce23a38fc8304b8b07e7641f7/src/storage/types.rs#L85

Hello Benjamin,
sorry for keeping you waiting. I have found the error and will provide a fix later today.

Hello Benjamin,
I've published the error fix.
Please check out the latest ic-wasi-polyfill version on crates.io. Unfortunately, the change is not backward compatible, and will break existing storage.

I have tested this on version 0.5.0 and it is working as expected, thanks!

authors: bdemann wasm-forge

repo: wasm-forge/stable-fs


text:
[BUG] Docker CI build failing on missing lib files

Describe the bug
In the past few commits to main, the Docker CI jobs have all failed.
It appears the rust:alpine image is missing two files that our Dockerfile tries to copy over into the final image:

/usr/lib/libcrypto.so.46
/usr/lib/libssl.so.48

To Reproduce
Steps to reproduce the behavior:

Merge a PR into main.
Observe the failed Docker builds.

Expected behavior
The Docker builds not to fail due to missing files.
Environment (please complete the following information)
N/A, CI problem
Additional context
I tried pulling down the rust:alpine image we use, and then installed the packages from the first line of the Dockerfile:
apk add --no-cache clang clang-dev libressl-dev ca-certificates musl-dev llvm-dev clang-libs curl gcompat
When I enter the /lib directory these libs are present:

It appears the ending number on libcrypto and libssl have changed to .1.1 from .46 and .48 respectively. The dumb fix is to just change the file names, but then we'd just run into this problem again if another name changed.

Thanks for submitting @mattwilkinsonn , yeah looks like I took the "dumb fix" route with #203 and we might be better off doing something more general. @jordan-rash is there a general way to fix this type of error for working with a scratch container?

Edit: never mind, didn't see you submitted a fix as well! Thank you

authors: brooksmtownsend mattwilkinsonn

repo: wasmCloud/wash


text:
chore(runtime) Update Wasmer to 0.5.5

Fix #45.
This PR updates dependencies and the runtime to 0.5.5.

bors r+

repo: wasmerio/go-ext-wasm


text:
ResponsiveGridView have no Items

Hi,
I'm using a ResponsiveGridView and it works great when i download it from nuget (version 1.0.4). Unfortunately, there is no header property. So I downloaded the code from here and built with the build.bat. I made reference in my project to AppStudio.Uwp.dll and it turned out that the list is empty. What am I doing wrong? There is no compilation errors, and yet nothing has been changed.

I'm not sure what's happening. I recommend you to include the Windows.AppStudio.Uwp project on your solution, remove the reference in the project.json and add "project reference" from your client project to Windows.AppStudio.Uwp project. This way you will be sure to target the right reference.

Closing this due to non response.

authors: adamkalicinscy javitosanchez

repo: wasteam/waslibs


text:
URL download

Just correcting th download URL in the readme file

Thanks 👍


text:
Wish: can we get a toolchain/deploy to Bluemix button?

Would be handy to have a "deploy to Bluemix" button similar to the very nice Personality Insights demo.

This and other sample apps are available here https://console.bluemix.net/developer/watson/starter-kits

Do you mean like the the deploy to blue mix in the car dashboard?
https://github.com/watson-developer-cloud/car-dashboard

@RogerIBMSnook thank you for your suggestion, I will add this to the wish list

authors: RogerIBMSnook germanattanasio stevenpkg


text:
Cookie sessions

Now using cookie-sessions to store user credentials and basic twitter profile data.
Deployed version

[Current coverage][cc-pull] is 69.68%

Merging [#94][cc-pull] into [master][cc-base-branch] will increase coverage by 3.60%

@@             master        #94   diff @@
==========================================
  Files            17         20     +3
  Lines           168        188    +20
  Methods          40         46     +6
  Messages          0          0
  Branches         26         28     +2
==========================================
+ Hits            111        131    +20
  Misses           57         57
  Partials          0          0

Powered by Codecov. Last updated by [d4e29e4...6f4a198][cc-compare]
[cc-base-branch]: https://codecov.io/gh/watson-developer-cloud/personality-insights-nodejs/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/watson-developer-cloud/personality-insights-nodejs/compare/d4e29e422e33d468e95808d9494397e41aac6039...6f4a198e24229a1a049d429ba474aff25c2b43e8
[cc-pull]: https://codecov.io/gh/watson-developer-cloud/personality-insights-nodejs/pull/94?src=pr

authors: arypbatista codecov-io


text:
chore(master): release 1.4.7

:robot: I have created a release beep boop
1.4.7 (2023-04-27)
Miscellaneous

deps: update traefik docker tag to v2.10.1 (5638520)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/docker-shared-services/releases/tag/v1.4.7 :sunflower:

repo: wayofdev/docker-shared-services


text:
Release v0.1.0 in Chef supermarket

The latest version on Chef supermarket is the 0.0.9, but the 0.1.0 seems to be already out.

hola buenas

repo: wazuh/wazuh-chef


text:
[BUG] Dashboard reports a 400 status to an API petition

Describe the bug
The following error has been reported for the first time in a AL2 machine testing the installation with 4.8.1-RC2
[root@ip-172-31-38-18 ec2-user]# cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i -E "error|warn"
{"date":"2024-07-09T11:01:12.185Z","level":"error","location":"monitoring:getApiInfo","message":"Request failed with status code 400"}
[root@ip-172-31-38-18 ec2-user]#

It seems that the petition that is generating the 400 status is the following:
[root@ip-172-31-38-18 ec2-user]# cat /var/ossec/logs/api.log | grep 400
2024/07/09 11:01:12 INFO: wazuh-wui 127.0.0.1 "POST /security/user/authenticate" with parameters {} and body {} done in 0.526s: 400

Steps to reproduce
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Request a AL2 machine (maybe a local VM also works)
Install the Wazuh stack with the assistant, by downloading it with the curl -sO https://packages-dev.wazuh.com/4.8/wazuh-install.sh and install it with the bash wazuh-install.sh -a -i -v command.
Check the logs with the cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i -E "error|warn" command.
See error

Expected behavior
This error should be not generated.
Host/Environment (please complete the following information):

OS: Amazon Linux 2

I deployed a Wazuh stack on an Ubuntu 22.04 and I got a failed request with 401 code status instead of 400 as described on the issue.
root@server:/home/vagrant# cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i -E "error|warn"
{"date":"2024-07-10T13:05:51.726Z","level":"error","location":"monitoring:getApiInfo","message":"Request failed with status code 401"}
root@server:/home/vagrant# grep 401 /var/ossec/logs/api.log
2024/07/10 13:05:51 INFO: wazuh-wui 127.0.0.1 "POST /security/user/authenticate" with parameters {} and body {} done in 1.680s: 401
2024/07/10 13:05:51 INFO: wazuh-wui 127.0.0.1 "POST /security/user/authenticate" with parameters {} and body {} done in 0.218s: 401

I tested this in an AL 2 machine and could not replicate it. The only error shown seems to be related to a race condition. We assume this is because Wazuh server API may have been initializing when the request was made.
From the Wazuh Dashboard perspective we didn't find any issue.
Wazuh Dashboard logs:
[root@ip-0.0.0.0-ec2-user]# cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i monitoring
{"date":"2024-07-11T11:40:43.603Z","level":"error","location":"monitoring:getApiInfo","message":"socket hang up"}
{"date":"2024-07-11T11:47:06.656Z","level":"debug","location":"monitoring:initMonitoringConfiguration","message":"wazuh.monitoring.enabled: true"}
{"date":"2024-07-11T11:47:06.656Z","level":"debug","location":"monitoring:initMonitoringConfiguration","message":"wazuh.monitoring.frequency: 900 (0 */15 * * * *)"}
{"date":"2024-07-11T11:47:06.657Z","level":"debug","location":"monitoring:initMonitoringConfiguration","message":"wazuh.monitoring.pattern: wazuh-monitoring-* (index prefix: wazuh-monitoring-)"}
{"date":"2024-07-11T11:47:06.692Z","level":"debug","location":"monitoring:checkPluginPlatformStatus","message":"Waiting for Kibana and Elasticsearch servers to be ready..."}
{"date":"2024-07-11T11:47:06.736Z","level":"debug","location":"monitoring:checkTemplate","message":"Updating the monitoring template"}
{"date":"2024-07-11T11:47:06.975Z","level":"debug","location":"monitoring:checkTemplate","message":"Updated the monitoring template"}
{"date":"2024-07-11T11:47:07.031Z","level":"debug","location":"monitoring:getApiInfo","message":"Getting API info for default"}
{"date":"2024-07-11T11:47:08.003Z","level":"debug","location":"monitoring:fetchAllAgentsFromApiHost","message":"Getting all agents from ApiID: default"}
{"date":"2024-07-11T11:47:08.033Z","level":"debug","location":"monitoring:fetchAllAgentsFromApiHost","message":"ApiID: default, Agent count: 0"}

Wazuh API logs:

[root@ip-0.0.0.0 ec2-user]# cat /var/ossec/logs/api.log | grep -i error
2024/07/11 11:46:07 ERROR: Error in CTI service request: a72f3cc3-7f39-4993-9d9c-41ab4e97602a, v4.8.1
    raise WazuhInternalError(2100, extra_message=extra_message)
wazuh.core.exception.WazuhInternalError: Error 2100 - Error in CTI service request: a72f3cc3-7f39-4993-9d9c-41ab4e97602a, v4.8.1
wazuh.core.exception.WazuhInternalError: Error 2100 - Error in CTI service request: a72f3cc3-7f39-4993-9d9c-41ab4e97602a, v4.8.1

Ok then, we should close this issue as not planned, and use it as "known issue" if the error appears again. Thank you.

authors: Desvelao asteriscos davidcr01

repo: wazuh/wazuh-dashboard


text:
[BUG] Getting an error when I try to import ReactFlowProps

I am trying to access the react flow props, but my application keeps throwing an error. Is there something I'm missing with this import?
How I'm importing
import ReactFlow, {   MiniMap,   Controls,   Background,   ReactFlowProps, } from 'react-flow-renderer';
Error
The requested module '../../web_modules/react-flow-renderer.js' does not provide an export named 'ReactFlowProps'

hi, which version are you using? the export was added in 6.1.1 https://github.com/wbkd/react-flow/issues/539

I'm using version 6.1.3

tried to reproduce it here: https://codesandbox.io/s/staging-wood-pmnlk?file=/src/App.tsx

authors: akernizan chrtze

repo: wbkd/react-flow


text:
Channel progress bars

This pull request adds channel progress bars to the channel overview.
Let me know what you think, I can make changes to the style if needed. This also adds Bootstrap to the Project so if this is not wanted, I can try to accomplish the task in a different way.
There is still one bug in this which I don't understand:
When the plugin is clicked the Channel Balance does not display, only if you maximize the window or e.g. click on settings and then it shows up. If someone knows how to fix it I would be grateful.

Thanks for giving such detailed feedback, in hindsight this was a very embarrassing PR. I didn't follow any of your guidelines and added unnecessary code, so shame on me.
Thanks for being so nice, hopefully those changes make more sense now. Also let me know if want any other changes to the design, etc.

No worries man! Appreciate you taking the feedback, I'll take another look later. I'm also working on contributing guidelines (#45) which should make this kind of stuff more explicit.

I made a couple of changes that I've PR'd against your PR over here: https://github.com/PatrickLemke/joule-extension/pull/2
Hope you don't mind! I thought that would be easier than telling you some of my concerns. Let me know if you have any thoughts.

authors: PatrickLemke wbobeirne

repo: wbobeirne/joule-extension


text:
Not working with iTerm2 3.x

Latest iTerm2 (3.0.5) updated its applescript syntax, therefore iTerm.sh stops working.
New syntax documentation: https://iterm2.com/documentation-scripting.html

This is a duplicate of #89

authors: twolfson ushuz


text:
FiSH doesn't like standard commands

I'm unsure if this could be fixed using the custom params, but, looking at the docs, It doesn't look like it
FiSH (Friendly interactive shell) doesn't like when a command uses &&, and tends to barf on that. The proper way to run multiple commands in FiSH is with semicolons separating commands.
If possible, a way to specify the command run on terminal open would be greatly appreciated. Thanks

This should be repaired by #40 which will be landed within the next week. Thanks for the bug report!

This has been repaired in 1.6.0 via @kristianj with #40. Thanks for the bug report!


text:
🛑 reader is down

In 31bc645, reader (http://reader.wbsnpc.repl.co/#/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: reader is back up in 08715e8.

repo: wbsnpc/upptime


text:
lua/lsp-status/messaging.lua:24: attempt to index a nil value

I get this error when opening Rust file using rust-analyzer.

Error executing vim.schedule lua callback: .../opt/lsp-status.nvim/lua/lsp-status/messaging.lua:24: attempt to index a nil value

Did some print debugging, and I suspect that maybe goes wrong because of the global messages table in lua/lsp-status/messaging.lua and there's two messages in parallel (rustAnalyzer/cargoWatcher and rustAnalyzer/startup). But that's just a hunch.
client_id = 1
msg.token = rustAnalyzer/cargoWatcher
messages =  { {
    messages = {},
    name = "rust_analyzer",
    progress = {
      ["rustAnalyzer/startup"] = {
        message = "0/10 packages",
        percentage = 0,
        spinner = 1,
        title = "rust-analyzer"
      }
    },
    status = {}
  } }
Error executing vim.schedule lua callback: ...ackager/opt/lsp-status.nvim/lua/lsp-status/messaging.lua:24: attempt to index a nil value
client_id = 1
msg.token = rustAnalyzer/startup
messages =  { {
    messages = {},
    name = "rust_analyzer",
    progress = {
      ["rustAnalyzer/startup"] = {
        message = "9/10 packages",
        percentage = 90,
        spinner = 10,
        title = "rust-analyzer"
      }
    },
    status = {}
  } }
client_id = 1
msg.token = rustAnalyzer/cargoWatcher
messages =  { {
    messages = {},
    name = "rust_analyzer",
    progress = {
      ["rustAnalyzer/cargoWatcher"] = {
        spinner = 1,
        title = "Running `cargo check`"
      }
    },
    status = {}
  } }

As you can see in the first message msg.token is rustAnalyzer/cargoWatcher, but the progress table only contains rustAnalyzer/startup causing a lookup error on this line:
https://github.com/wbthomason/lsp-status.nvim/blob/d6ad84228c7a30dc6295afde110edb31bc331bdb/lua/lsp-status/messaging.lua#L24

Thanks for the report! I'll try to replicate the error.

Ah. So, this looks to be because rust-analyzer sends that rustAnalyzer/cargoWatcher message as an "end" kind without a corresponding "begin" first.
It looks like this might be a known rust-analyzer bug: https://github.com/rust-analyzer/rust-analyzer/issues/4384
However, I should still add code to check that we have info for a token before trying to update it.

Thanks for the quick response and fix! 👍

authors: lithammer wbthomason


text:
Move react and react-native to peerDependencies and devDependencies

Currently, react and react-native specified as package dependencies and installed with it even if parent package already has similar dependencies which leading to @providesModule naming collisions as reported in #16. Moving this deps to peerDependencies will solve the issue.

Any update on this? Can someone merge and publish it on npm?

This should be addressed in https://github.com/wcandillon/react-native-responsive-ui/pull/18

Thank you :-)

authors: kiurchv piranna wcandillon

repo: wcandillon/react-native-responsive-ui


text:
Неизвестная ошибка в ответ на NameError

Ввод:
NameError: name 'fkjj' is not defined
Вывод:
В файле "ror: name 'fkjj' is not define", строке ror: name 'fkjj' is not define:
  Неизвестная ошибка

Пока поддерживаются только полные трейбеки.

Эта возмжность добавилась просто исправлением ошибки считывания при вводе пустой строки: bb6bab8

authors: FrCln wchistow

repo: wchistow/Errors-translater


text:
wayland support

I would really like to run gmrun under wayland.  Is there a path for supporting wayland in gmrun?  maybe gtk4?

What is wrong with gtk 3 and wayland?

Oh I don't know, I guess I wasn't aware the gtk3 supported wayland.  Does gmrun support wayland currently?  I'm running a pure wayland system and when I try to launche gmrun I get:
servo:~ 0$ gmrun
(gmrun:138263): Gtk-WARNING **: 09:56:28.297: cannot open display:
servo:~ 1$
"""
What do I need to do to get it to work with wayland?  I'm running debian trixie/sid.

Gmrun should not care about Wayland, it already use the toolkit. I use it
on labwc, and even if it does not work it should fallback to X11, you have
other issues.
On Sat, Jul 6, 2024, 18:58 Jameson Graef Rollins @.***>
wrote:

Oh I don't know, I guess I wasn't aware the gtk3 supported wayland. Does
gmrun support wayland currently? I'm running a pure wayland system and when
I try to launche gmrun I get:
servo:~ 0$ gmrun
(gmrun:138263): Gtk-WARNING **: 09:56:28.297: cannot open display:
servo:~ 1$
"""
What do I need to do to get it to work with wayland?  I'm running debian trixie/sid.
—
Reply to this email directly, view it on GitHub
https://github.com/wdlkmpx/gmrun/issues/20#issuecomment-2211819028, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAEICQFBG4QU547W6IYVNDZLAO4DAVCNFSM6AAAAABKNUCEO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRHAYTSMBSHA
.
You are receiving this because you commented.Message ID:
@.***>

gmrun in debian does not work on wayland, so I'm trying to figure out what the issue is.  If you think upstream supports wayland that's great, I'll try to figure out what's wrong with the debian packages.
I'm not interested in running X anymore, so I'm not running Xwayland.

FYI I recompiled the latest upstream with gtk3 and it works fine on my wayland system.  I will help get the debian package recompiled against gtk3 as well.  Thanks for the patience and feedback.

repo: wdlkmpx/gmrun

license: ISC


text:
[Power Support] Enable weaveworks scope on Power.

Observed this particular test  was failing on ppc64le architecture. Added the test failure log below,
walker_linux_test.go:97:
                +++ have
                @@ -32,7 +32,7 @@
                   Cmdline: (string) (len=15) "curl google.com",
                   Threads: (int) 1,
                   Jiffies: (uint64) 0,
                -  RSSBytes: (uint64) 8192,
                +  RSSBytes: (uint64) 131072,
                   RSSBytesLimit: (uint64) 2048,
                   OpenFilesCount: (int) 3,
                   OpenFilesLimit: (uint64) 32768,

Hence modified the value for RSSBytes to accept variable value which is computed based on pageSize instead of hard-coded values, as suggested by Adam Harrison over slack channel.
I have verified this patch on x86 setup as well and all the tests pass there.  Please provide your comments/suggestions on this.
Thanks,
Meghali

Note there is a lint failure in this PR.

Yes, @bboreham , I am looking into this. I am expecting my build-changes should get this resolved.

@meghalidhoble Please run make lint locally to verify linting issues.

Please run gofmt -s -w probe/process/walker_linux_test.go then update the PR.  This should clear the lint error.

Thanks @bboreham , your suggestion helped to resolve the failure.

Please put into each commit message a description of the changes.
Some tips here
"code changes made" is not a useful description.

Hi @bboreham, @satyamz ,
Can we please merge this PR if no more modification is needed?

Hi @bboreham ,
I have addressed most of your comments and have pushed a few new code changes, Could you please take a look and let me know if any comments/suggestions?

Hi @bboreham , squashed all the commits to a single commit, with all the implementation details for each file being modified. Please take a look.

Sadly, it is inappropriate to directly modify anything in the tools directory because it is a vendored copy of https://github.com/weaveworks/build-tools.  Need to modify it upstream and then bring that commit in.
I'm sure this is maddening.
I might just change it to do nothing if it can't find shfmt, as is done for shellcheck, rather than have an architecture-specific test.

Hi @bboreham ,
I have addressed the concern raised for tools directory changes, hence I have removed the architecture specific changes. Sorry for multiple commits, I will squash those commits and will combine to a single commit. Let me know if these changes look ok.

Multiple commits is fine as long as they all form a progression and are all self-explanatory.
However the issue is that to change a file under the tools directory in this repo you need to change it in https://github.com/weaveworks/build-tools first and then do a git subtree to update the directory in this repo, as described in tools/README.md.

Hi @bboreham , I have raised a pull request at build-tools repo with the lint changes, once those changes are approved, I will run git subtree to update the directory in this repo.

Thanks!

authors: abdasgupta bboreham meghalidhoble satyamz

repo: weaveworks/scope


text:
Gather file descriptors as process metric

Fixes #729
Any other bits we should to gather? I'm not super-convinced it's actually all that useful?
@2opremio, wdyt?
See "Open Files" sparkline below.

I think it's a  very useful metric, but I am not convinced it should have
such protagonism, or whether it's useful to show it it's history in a
sparkline.
On Friday, February 12, 2016, Paul Bellamy notifications@github.com wrote:

Assigned #961 https://github.com/weaveworks/scope/pull/961 to @2opremio
https://github.com/2opremio.
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/pull/961#event-548798348.

Yes it would be good to have this hidden behind a show more.
On Friday, 12 February 2016, Alfonso Acosta notifications@github.com
wrote:

I think it's a very useful metric, but I am not convinced it should have
such protagonism, or whether it's useful to show it it's history in a
sparkline.
On Friday, February 12, 2016, Paul Bellamy <notifications@github.com
<javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Assigned #961 https://github.com/weaveworks/scope/pull/961 to
@2opremio
https://github.com/2opremio.
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/pull/961#event-548798348.

—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/pull/961#issuecomment-183423122.

Hiding a single element seems needless.

@paulbellamy From my own debugging experience, open files gets you straight into root cause analysis, whereas cpu and memory are quite vague. so I love its prominence there (until a better metric comes along).

Tried the branch, JS part looks good too.

minor-comments aside, LGTM

authors: 2opremio davkal paulbellamy tomwilkie


text:
make protocol more resilient to changes

At the moment every change to the protocol requires a change in version and introduces an incompatibility with all other versions.
We should make the protocol more resilient to change, permitting weave peers to communicate with each other when they speak slightly different protocol versions, without having to write any special code.
This works in conjunction with #871 by providing an easy route by to support multiple protocol versions.
Extracted from https://github.com/weaveworks/weave/issues/403#issuecomment-104048264.

I've been contemplating whether we should have a major/minor protocol versioning scheme. The major version would be what gets agreed through #871. The minor version of that is then what the individual peers actually speak, and need not be the same for the two sides.
Without a minor version, we could, say, have Peer A supporting version 11 and 12, and Peer B supporting 12 and 13, both agreeing on 12, yet B actually speaking 13, because it knows that 13 can be handled by 12. This may look somewhat strange when examining the message stream, and generally makes it somewhat less obvious what is going on.

It might be interesting to look back at all the changes that have precipitated protocol version bumps and see how they might have been handled under a major/minor scheme...

Not very well at all. Not without extra code. I said that much when we had the discussion in email.

I don't understand the usage of major/minor here. I would expect these terms to mean, in the example, that B supports 12.0 and 12.1, so 12 is the major version and .0 or .1 is the minor version.

Yes, that is correct. Though I am not sure whether the minor version should really feature in the negotiation, since it should have no bearing on it. OTOH, there is no other place where the minor version would appear, which would make it pointless since it only exists for clarity.

So after further discussion we have agreed that a single version number is sufficient. Let's keep things simple.

It is already possible to add new protocol messages.
I have raised bugs for

[ ] #911
[ ] #913

The other area worth examining is the various gossip codecs, e.g. topology, ipam.

authors: awh bboreham rade

repo: weaveworks/weave


text:
Change weavedb from an emptyDir to a hostPath volume

emptyDir has the same lifetime as the pod, whereas we want our persistence to extend past that, e.g. when Weave Net is upgraded.
We assume that /var/lib is writable.
Fixes #2610

As discussed on Slack, this requires a similar change in the Launch Generator.

Should we add a step to delete this directory in the tests?

Should we add a step to delete this directory in the tests?

I guess so; from the point of view of ensuring that we test the same thing each time.
Ideally we would extend the tests to do some sort of 'delete pods and restart' to check persistence worked.

Ideally we would extend the tests to do some sort of 'delete pods and restart' to check persistence worked.

Agreed.

Should we add a step to delete this directory in the tests?

I now think weave reset should clear out this persistence directory; this will help, e.g. if someone needs to move a peer from one cluster to another.
(it isn't easy to run weave reset in a Kubernetes context, but that's a different problem)

@brb, what do you think of these latest changes? (I'll wait for your final review before I merge)

authors: bboreham marccarre


text:
Questions about pytest -x

Performed the following installation operations as required

but

Hi, this is because you need the URLs to be set before running pytest (as it needs access to these webpages for some of the tests).

I ran all the environment installation commands, but I don't have the _state.json file in .auth folder.

python browser_env/auto_login.py
After running the above command, the _state.json file was not created.

authors: XinrunXu kohjingyu

repo: web-arena-x/visualwebarena


text:
fix: patch sendStats of webpack-dev-server

Summary
Patch webpack-dev-server to prevent it from reading empty stats (to whom using rspack-dev-server).
Continue: https://github.com/web-infra-dev/rspack/pull/4028

Test Plan
No need.

!eco-ci

!eco-ci

!eco-ci

Looks like it works like a charm:

Still, we should warn developers not to use webpack-dev-server and stick to rds

!eco-ci

repo: web-infra-dev/rspack


text:
Fix date range gap.

Motivation

[x] Fixes https://github.com/web-ridge/react-native-paper-dates/issues/271 and https://github.com/web-ridge/react-native-paper-dates/issues/281. @RichardLindhout I'm not 100% sure if flex-basis is being used properly here, but it did achieve the desired effect. I'm not sure if this will cause any unplanned issues, but maybe you have an idea.

Before

After

Note - There are no guidelines on selecting a range to itself, but this is a potential existing style bug, that I noticed while playing around trying to fix this issue. @RichardLindhout Let me know your thoughts on this.

Nice!!!! I never got what this issue was!

authors: RichardLindhout iM-GeeKy

repo: web-ridge/react-native-paper-dates


text:
App: highlight physics incorrect

This seems to only affect the highlight mesh, not the actual physics collisions:
Probably a missing updateMatrixWorld

I see this occasionally but it is much rarer now.
Closing until we have reliable reproduction steps.

repo: webaverse/app


text:
[Task] Update protocol-substrate metadata

SignatureBridge Pallet  added to protocol-substrate runtime PR-#

We have updated that in #45

repo: webb-tools/webb-rs


text:
Step retries lose world context

The Problem
When a retry is kicked off the functions that were added to the World are no longer available on. They are available in the first run ( as retry has not been kicked off) when the retry happens it looks like it removes the World context from the step definitions.
// worldjs
const expect = require('chai').expect;
const fixedUsers = require('../../../lib/fixtures/fixture.users');
const routes = require('../../../config/dist/routes');
const Brain = require('../../../lib/tools/dist/brain');
const users = require('../../../lib/api/dist/users');

function World () {
  this.fixedUsers = fixedUsers;
  this.expect = expect;
  this.routes = routes;
  this.brain = new Brain();
  this.users = users;
};

module.exports = function () {
  this.World = World;
};

//step defs
this.Given(/^some step definition$/, { retry: 2 }, () => {
        // Access to this.expect and others on runs run,
        // when retry happens because something failed
        // then the methods from world are undefined
    })

wdio-cuucmber-framework version: 0.2.5
wdio version: 4.2.11
cucumber version: 1.2.2

Happened for me, too. Any workaround for this one?

The line below seems to be related
https://github.com/webdriverio/wdio-cucumber-framework/blob/004a1a25a2eae80788dd8ee50fc03abe171a42d3/lib/adapter.js#L83

Any updates?

@shkaper the work around I found for this was to store any function / class instances in some custom object inside of the browser object. You would do this in a beforeScenario hook so it gets refreshed on every scenario. So something like this,
    beforeScenario: function (scenario) {
      browser['tools'] = {};
      browser['tools']['stuffInstance'] = new Stuff();
    }

Can someone provide a reproducible example?

world.js
function fooBar() {
   this.getValue = function() {
     return  'FooBar';
   }
}

function World () {
   this.fooBar = new fooBar();
};

module.exports = function () {
  this.World = World;
};

step_defs.js
this.Given(/^I call a world function with a retry$/, { retry: 1 }, function() {
   var foobar = this.fooBar.getValue();
   console.log(foobar);
   // Triggger a failure so retry is ran
  throw new Error('BOOM!');
})

test.feature
Feature: Retry test suite

 Scenario: retrying step def should retain world context
   Given I call a world function with a retry

The above code will run fine the first time, the second time because of retry 1
 this.fooBar.getValue();

Will return undefined. More specifically this.fooBar is undefined.

authors: christian-bromann shkaper si-mikey

repo: webdriverio/wdio-cucumber-framework


text:
There should be an upper limit for attachments size

I keep adding attachments and there seems to be no upper limit. When I finally hit send, only the first file was uploaded, all others were never shared and they are showing up as empty gray squares in the conversation window.

Thanks for reporting this issue @KamilSzostak, we'll look into this. In the mean time, if you have a suggestion for a fix, please don't hesitate to open a PR!

This will be resolved by #873

authors: KamilSzostak adamweeks bzang

repo: webex/react-ciscospark


text:
Automatically create user on successfull remote authorization

@spajus

:+1:

this is awesome :+1:
after testing on our forum we should contribute this back to upstream

@spajus Yep

Included in idnet discourse plugin

authors: EddieOne spajus yvon


text:
🛑 LEGO (abakus backend) is down

In 8b4c134, LEGO (abakus backend) (https://lego.abakus.no/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LEGO (abakus backend) is back up in 08e8285 after 9 minutes.

repo: webkom/uptime


text:
Steam + Oculus broken in VR - Only first frame rendered

Repro node . -x webvr https://possible-bench.glitch.me/ aframe master from november.
Probably requires an openvr lib update - @modulesio
Will look at this tomorrow.

Was this fixed by #754?

I don't think it was. However, I would consider this issue subsumed by https://github.com/webmixedreality/exokit/pull/787. Oculus was never officially supported before that PR.

authors: chrislatorres modulesio shaneharris

repo: webmixedreality/exokit