text:
GraphQL errors are ignored when using pollInterval

Describe the bug
GraphQL errors returned by the server after the first request are ignored when using pollInterval.
To Reproduce
Steps to reproduce the behavior:

Write a apollo query using pollInterval
The server should return a successful result the first time.
The server returns a graphql error the second time.
The error is ignored

Expected behavior
The graphql error should not be ignored. Network errors, if you stop the graphql server for example, are not ignored. If the error occurs for the first query, before it waits to poll, it's not ignored either.
Versions
vue: 2.6.12
vue-apollo: 3.0.5
apollo-client: 2.6.10

Could you please provide a runnable minimal reproduction of this so I can take a look when I have some time? Thanks! :pray:

Sure, I will hopefully get some time for that next year. 🙂

Hi, I ran into this problem as well. It seems that any error from a previous fetch is kept in cache, even if later calls to the GraphQL server don't return any errors anymore. The changes in #1120 seem to fix it for me... @fungiboletus Could you check if this solves it?

Could you check if this solves it?

I'm using the V3 and your change is for the V4. I checked and the code looks quite different. Actually my bug may not exist in the V4.

Oh sorry, my bad :see_no_evil:

authors: Akryum fungiboletus yaroedi

repo: vuejs/vue-apollo


text:
devServer config do not work correct on vue ui

Version
3.0.0-rc.3
Reproduction link
https://jsfiddle.net/fyAgent/cmyjdsvf/
Steps to reproduce
// edit vue.config.js;
module.exports = {
assetsDir: undefined,
baseUrl: undefined,
outputDir: undefined,
runtimeCompiler: undefined,
productionSourceMap: undefined,
parallel: undefined,
css: undefined,
devServer:{
port:9000,
host:"localhost"
}
}
run vue ui
run serve
What is expected?
it will work correct when i change the configuration of devServer
What is actually happening?
when use vue ui to start the server,it will still open at port 8080

It's because in the parameters in the UI you have port set to 8080.

source: gharchive/issue

authors: Akryum fyAgent

repo: vuejs/vue-cli

license: MIT

license_type: permissive

license_source: github-api


text:
The initial README.md has markdown lint issues - MD040/fenced-code-language: Fenced code blocks should have a language specifiedmarkdownlintMD040

Vue version
5.0.8
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-cxxzon?file=README.md&terminal=dev
Steps to reproduce
After  vue create my-app , the initial README.md has some markdown lint issues.

What is expected?
Project setup
npm install

Compiles and hot-reloads for development
npm run serve

Compiles and minifies for production
npm run build

Lints and fixes files
npm run lint

What is actually happening?
MD040/fenced-code-language: Fenced code blocks should have a language specified markdownlintMD040
Maybe you shpi;d add the language specified (e.g. shell, bash etc.)?
System Info
No response
Any additional comments?
No response

Vue CLI does not integrate Markdonwlint. We don't feeel required to respect its rules.
Vue CLI is in maintenance mode. We only fix relevant bug and security problems.


text:
How we should work with different enviroments?

What problem does this feature solve?
More clearest way to work with different enviroments.
What does the proposed API look like?
I think we need only one .env file, that contain all kind of enviroment variables.
That file should not be tracked by VCS.
But we can have documented .env.example.
I mean build script should load variables only from one .env
NOT merging .env.local with .env.whatever
NOT loading multiple .env
JUST load .env and build
For CI, dev, stage, ..., or every other enviroment, you should preconfigure .env, thats all.
Dont need magic mode for vue-cli-service build --mode=internal.
vue-cli-service build should see .env and just build.
Should use dotenv.
The process for any kind of enviroment setup:

pull (vcs)
configure(.env)
build(vue-cli-service build)

# Usage:
# bash
vue-cli-service build
APP_ENV=/full/custom/path/to/your/env/vars vue-cli-service build
vue-cli-service build --env=/full/custom/path/to/your/env/vars

// Possible implementation
const args = require('yargs').argv
require('dotenv').config({path: process.env.APP_ENV || process.args.env || '.env'})

// Usage:
// package.json
{
    "scripts": {
        "build": "vue-cli-service build",
        "build:first_variant": "vue-cli-service build --env=/full/custom/path/to/your/env/vars",
        "build:second_variant": "ENV_PATH=/full/custom/path/to/your/env/vars vue-cli-service build",
    }
}

People may want some variables checked in, some not. Your use case is not the only use case. If you don't need modes, just don't use it.


text:
Minor improvements for 2.x warning

There are two problems (IMHO at least) with the current 2.x "warning":

It's not an error per se, more like an information, so I changed the color to green instead of red.
Grammar.

Since both happen in one line, I decided to merge them into one commit.

I agree as well. I'm merging because we're already 3 :)

source: gharchive/pull-request

authors: phanan zigomir


text:
Can you please provide a similar extension for firefox ?

Kudos!! The extension is a must while learning Vue atleast. I would like to request you to provide a similar extension for Firefox.
Please! can i expect it?
Update: (17-March-2017)
It is now possible to use (chrome's) vue dev-tools in Firefox.

Install Firefox Developer Edition
Install Chrome Store Foxified extension
Now go to Chrome Web store and search for vue- devtools, you will now see an option to install in firefox/ add to firefox

It's definitely planned in the future, however probably not until a few months out...

Thanks. Eagerly awaiting.
On 28 Nov 2015 11:52, "Evan You" notifications@github.com wrote:

It's definitely planned in the future, however probably not until a few
months out...
—
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue-devtools/issues/57#issuecomment-160252649.

I've started work on a firefox version of the same. You can check out my branch hope to finish this in 2-4 weeks.
Progress so far:

@skyronic very cool! Excited to have someone working on this. Let me know if you have any questions :)

Awesome  @skyronic , I will check out your branch.
On Mon, 30 Nov 2015 20:19 Evan You notifications@github.com wrote:

@skyronic https://github.com/skyronic very cool! Excited to have
someone working on this. Let me know if you have any questions :)
—
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue-devtools/issues/57#issuecomment-160651321.

@yyx990803 any news on this?

Almost half a year later. :) Any news?

@yyx990803 , @skyronic  - any progress? still awaiting devtools for firefox

throwing in my vote as a firefox developer edition user

Is there any news on this? I'd love to be able to use FF dev edition for Vue just as I do with everything else. @skyronic? Any plans on finishing this or at least releasing some basic instructions to install what you already had?
Thanks!

Hey guys, are you still working in the FF version of dev tools? It would be a great enhancement... Tks!

Yes! I am still working on FF devtools, and I'll be happy with Vue plugin!! :)

Hey folks, can we install a chrome plugin inside firefox? I remember reading this some time back. It was a blog post by Firefox team saying that we can easily install a chrome plugin inside firefox.

Yes, it's called WebExtensions. But I don't think it works developer tools.
see http://arewewebextensionsyet.com/#devtools.panels

That's bad news.

Still no FF extension? :(

@yyx990803 You got any update on this topic?

I've subscribed this issue for Firefox addon. 🔔
Firefox user life isn't easy with Vue as Chrome. 😭
Still looking forward to using Firefox addon. 😳

My christmas wish this year: that there will be a Firefox version of vue-devtools 🎄

I'm interested in this too.

Anyone here wishes to build a firefox addon for Vue? I am open to collaborating, we can build our own version by checking the source code of the chrome version, do let me know if anyone is willing to participate.

Skyronic has started working on it it would seem, maybe try to get in touch?
As for me, my plate is full atm unfortunately.

Hey I had gotten some work done on this a long time ago by re-using ideas from the react-devtools project. I stopped using firefox due to some other reason so I didn't continue work on this.
A lot of the structure for vue-devtools is inspired by https://github.com/facebook/react-devtools
so you'd want to create a folder in 'shells' similar to this one - https://github.com/facebook/react-devtools/tree/master/shells/firefox

The maybe I can start working on your version itself. I've never written a extension, so it will take a little time!

look forward to the firefox version

So, which features are prevent this from just being ported over?
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities

I can confirm that this doesn't work for our case: https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/

@wamoyo devtools.panels API is needed http://arewewebextensionsyet.com/#devtools.panels
Some progress has been made recently, so hopefully we will be able to port easily soon

This is a so-needed tool 👎 I don't want to use chrome for this matter either

Why is there still no plugin for Firefox? Would really appreciate it!

Because Vue + core libs  is more prioritised than this

My year wish this develop this add-ons for firefox .

Just to let you know, firefox Developer edition now has the panel displayed. It doesnt work atm, doesnt recognize the Vue app, but its showing up! We are almost there 😆

@dobromir-hristov How do I install this for Firefox Dev edition?

@thewhitetulip Go to about:debugging#addons and click button and browse to add-on file (manifest.json).

There is a plugin in firefox plugins to install Chrome Extensions directly from the Chrome Extensions website.

@gluons @dobromir-hristov I'll try this today and let you know, thanks!

We should wait until Mozilla finish dev tool API.

@gluons That's probably only a few months out then, no?

it does work already on Aurora channel with Chrome Store Foxified extension

@brunjick Thanks for the update! I have the Aurora channel installed, will try and confirm back!

Also confirmed working with the latest release of dev edition and vue devtools.

Firefox Dev Edition aurora 54.0a2 (2017-03-15) (64-bit)
Chrome Store Foxified 2.4
Vue.js devtools 3.1.2

@neeravp  Can you please update the content of this issue to state that the extension now works with Firefox?

@thewhitetulip I have updated the issue content .

@neeravp Thank you!

@brunjick tks! Here is working too att Firefox Dev Edition with Chrome Store Foxified.
Look it @mauricionr

Tested it on the latest release of Firefox (52.01 (64-bit)), although I get the icon next to me addressbar, no Vue pane can be found.

@Hendriksie Latest release is 54.0a2 (2017-03-19) (64-bit)

@brunjick forgot to mention that I use the normal release version, no dev edition / aurora edition

@Hendriksie Yes, we are using the dev edition :)

Anyone here would like to write a guide about how to install this addon? I wasn't able to install it!

@thewhitetulip They use Chrome Store Foxified.

@gluons I did use that addon, it asked me to sign in using Firefox dev account, I did that, but I didn't get an option to install the addon, I could just download the .crx version or temporarily install it, I'll take a look at it today and let you know.

@thewhitetulip If you have downloaded the addon, then you can go to the addon management interface in firefox by navigating to about:addons.
Once on the about:addons interface, you can click the gear icon in the top right before the search field and you will get an option Install Add-on from file, it will allow you to install the downloaded addon.
Hope this helps.

@neeravp This is awesome, thank you! I was able to install the addon and it looks cool. Thank you very much.

@thewhitetulip @neeravp It should be mentioned for any future Googlers, you first want to choose the "Save Signed Addon" option. This will generate a signed XPI file you can then install from the about:addons page.

@neeravp @Zetaphor is right, it would be amazing if you could just copy paste the message which you sent me, the exact steps to install the addon at the top of the issue in the description, so new people finding this page via google won't face any issues.

@yyx990803 Should I close the issue Evan? Or should it be open till a native Firefox addon/extension is available?

I think it should be opened til devtools API released.
This issue is for Firefox add-on. Not for installing Chrome extension in Firefox.

@gluons Yes, until this is available in normal Firefox we should wait, when it is however, we do not need a new addon in firefox thus, we can close this, what do you think?

Well, that is good news, but I think I will keep this open until the required features land in Firefox stable. In the meanwhile, I'd be happy to take a PR updating the README to point out how to use this extension in Firefox dev build.

I was thinking about a PR, but there are two things holding me back. First I have never contributed to any open source project by means of PR so am not sure about how to do it properly. I can prepare a gist and send it across you @yyx990803 .
But even before that using Chrome Store Foxified requires to sign the extension/addon, for which I had to create an account at AMO. What I am wondering is that for anyone who wants to use vue-devtools in Firefox will need to open an account at AMO just for the purpose of signing the extension.
Wouldn't it be better if we (anyone) can create an accont at AMO and sign the extension and then download the signed extension, which can then be included in this repo as a workaround for Firefox.
Then any subsequent users can just download the signed extension from here and use Install Addon from file to get vue-devtools working in firefox.
I am trying to figure out if such a signed extension can be reused.

@neeravp There is no rocket science in submitting a PR, you just fork the project, edit the README.md file and submit it as a PR, based on the time @yyx990803 or other collaborators have, they'll merge it.
I agree with you and I was going to say this earlier, we can just upload a signed version of the addon rather than have everyone create a firefox account as it is a waste of time and resources, if you are willing, I'd send my addon to you, just try to install it on your firefox dev, and if that's fine, we can upload it directly on github itself.

If you are fine with an unofficial build and want to run VueJS DevTools without the hassle of singing and converting the addon, I made one here.
I posted a lot of info related to Firefox addons on this issue in case you need the info.

I just picked the built version in shells/chrome, duplicated that into shells/firefox and used the web-ext tool and packed it. It is working for me. It would be trivial to ship that to AMO. It would be cool if the original author did it.

Do you guys have problems with the Vue devtools panel not being scrollable? Because I have to close all the tree branches to be able to see anything that is in the lower part of the panels, for example in the Vuex Store panel.

I am using Waterfox. I installed vuejs devtool, and restarted browser. However I couldn't find Vue tab in inspect window.

We're still waiting on Firefox to complete bug 1300590 such that $0 and inspect bindings will work in the devtools.inspectedWindow.eval API.  Once that lands this is the list of things I believe need to be done for this issue to be closed out.

[ ] #339 : update the manifest.json permissions
[ ] Change enabled popup text to say "Open DevTools"
[ ] Need to review the webpack options for target browser and dev mode I think we could likely just add { firefox: 55 }
[ ] Update manifest description to mention Firefox as well as Chrome
[ ] Investigate custom fonts that aren't working in Firefox
[ ] Submit WebExtension zip to AMO
[ ] Update README to refer to Firefox extension
[ ] Remove Firefox workaround doc

Investigate custom fonts that aren't working in Firefox

I'm getting this error:
downloadable font: GSUB: too large substitute

And it looks like this stackoverflow answer might be the path forward: https://stackoverflow.com/a/36803177/897414

Need to review the webpack options for target browser and dev mode I think we could likely just add { firefox: 55 }

Getting an error with 55 right now. Chrome is currently shipping 58 and 60 for Canary so I don't think it'll be an issue to use Fx 48 for now.
Here's the error:
Module build failed: Error: Support data exists for the following versions of firefox: 43, 44, 45, 46, 47, 48. Please raise an issue at https://gitlab.com/Rich-Harris/buble/issue

Bug 1300590 - Implement support for $0 and inspect bindings in devtools.inspectedWindow.eval just landed. It will probably be available in the next Nightly update :D

Great! Hope this plan come true soon

This is now official, but how exactly I install it on Firefox ?
Do I still need this workaround ?
I someone working on an official Firefox addon ?
This is very exciting!

@lionel-bijaoui

Firefox continues its rapid implementation of new WebExtension APIs. These APIs are designed to work cross-browser, and will be the only APIs available to add-ons when Firefox 57 launches this November.

It's on Firefox 57? It may not work now. I think still need it for now.

@gluons Oh... I read it to fast it seem... I will wait then... 😞

@lionel-bijaoui Firefox Nightly is 56 now. So close. Let's try it when 57 come. 😜

@lionel-bijaoui having a workaround is silly when you can have a one click install I really hope the VueJS DevTools devs spent a few minutes to provide an official unlisted addon untill it will be ready to be listed on AMO. It makes no sense to wait for v57 especially since some of us use v56 already.

Installing Vue-devtools via the workaround (https://github.com/vuejs/vue-devtools/blob/master/docs/workaround-for-firefox.md) works great on Firefox 54 (released just a few days ago).
Only thing I noticed is that I can't scroll inside the devtools window.

@andreicristianpetcu THANK YOU! It work perfectly (except for the scroll)

@Hendriksie what is the advantage of the workaround over the one click install I proposed? The workaround seems complicated and unnecessary but please correct me if I'm wrong. I tend to like thing that just work.

Either is fine. Using Chrome Store Foxified directly just cuts out a middleman :)
Based on @clarkbw's comment above, it looks like all the pieces are in place for this, we just need to get it submitted to AMO and wait for the next release of Firefox to pick up a few fixes on our end.

Something appeared in AMO :ghost:

Firefox workaround doc was removed in c8b9b1e5428fe6c834619d21f00e1e7c620deeb4 and README was updated in 182fe6875f2b2d9b2479f6b4bee1a52863b77f37
I think we're all done here!
Thanks to everyone who helped and especially @yyx990803

@yyx990803 Can you add Vue logo on AMO page? Maybe easier to recognize.

authors: Draluy Drive4ik Hendriksie Jonas-buriti LaiHuanMin PascalAOMS Zetaphor adriaanzon andreicristianpetcu brunjick callahad clarkbw dobromir-hristov gluons imuller ivansieder j3j5 lionel-bijaoui locolauty97 miladjef nacr-dev neeravp posva ptibbetts samrayleung skyronic soapdog stefanpolzer suncoastkid thewhitetulip wamoyo yyx990803 zironycho

repo: vuejs/vue-devtools

license: mit

license_source: bigquery


text:
feat(ref): all refs are now an async iterable

Refs can now be consumed with a for-await loop, or with other APIs, such as rxjs@7 that accept AsyncIterable.
After some discussion with @yyx990803, here is a small PR to add async iterable support to instance of RefImpl.
If this lands, then any API that accepts an async iterator will "just work" with a ref instance. For example, in RxJS, anything that accepts an Observable could now just accept a RefImpl from Vue. Similarly, updates to a ref can be consumed with for await loops, or perhaps even yield-ed within an AsyncGenerator (async function*). So there's a lot of interesting potential here.
It might also help create opportunities to right interesting code, or maybe even coroutines at some point, within the library itself.
Open Questions
One open question/concern I have, is this relies on watch. Since I don't understand the mechanics of watch yet, I assume it relies on some underlying global state that may or may not switch between given async contexts. So... if someone were to wait and create the iterable out-of-band with a setup or some other part of Vue's lifecycle, I'm not sure how they will behave.
Another concern I would have isn't necessarily about the feature, but more about for-await in general, and what we can add to this feature to keep people from shooting themselves in the foot. Since, in theory, a ref lasts for as long as someone has a handle to it, if someone uses for await to endlessly consume the ref, it's possible to end up with a single hung promise when a component unmounts. It may be prudent to add an onUnmount in the RefAsyncIterable initialization that flushes all pending promises when it's unmounted.
Example usage:
const myRef = ref(0);

async function someHandler() {
   for await (const value of myRef) {
      // triggered each time `myRef.value` is updated.
      console.log(value);
   }
}

// Later this would trigger the for await loop.
myRef.value++;

Example of it "just working" with another library:
import { from } from 'rxjs';
import { ref } from 'vue';

const myRef = ref(0);

from(myRef).subscribe(console.log); // will log on each change to `myRef.value`;

// later
myRef.value++;

Really thinking about all of the implications of this, some sort of Observable type is more ideal for this (not necessarily an RxJS observable), but a push stream that is lazy and cancellable. AsyncIterable, while cool because of for await, may not be the best way to go.

repo: vuejs/vue-next


text:
Wrapper properties vm cant read  the  exposed properties

Comp setup return a render function,  and expose specific properties
export default defineComponent({
    setup(prop, { expose }){
        const str = ref('hello'), domRef = ref(null);
        const handleClick = () => {
          console.log('handleClick')
        }
        expose({
          handleClick,
          str,
          domRef
        })
        return () => (
{ str.value }
)
      }
})

I cant get str handleClick ... it is version problem?
import Comp from './comp';
test('comp', () => {
  it('vm', () => {
    const wrapper = mount(Comp)
    console.log(wrapper.vm.handleClick)
  })
})

Hi @NidusP
You'll need to give us more details to help you: what version are you using? What is failing?
If you're using the latest VTU version (rc.17 at the moment), it should work.
If you have an issue with the latest version, you can either:

try to provide us a minimal reproduction in a github repo so we can take a look
add a failing unit test to this repository (see expose.spec.ts for all the expose related tests)

Thanks for your help!  I write the test according to the guide and it passed !  (rc.17 and rc.9)
The failed tests environment  were built by someone else,  I looked at the dependencies,  such as jest @vue/test-utils babel-jest @types/jest.  So  I tried to add @vue/vue3-jest to the dependencies and updated jest.config.js , but  still failed.
Does it concern @vue/vue3-jest? I am not very clear about jest.config.js details  and the relationships  between dependencies.  The test maybe pass if  jest.config.js  is configured correctly ?  I'll look into it again.

authors: NidusP cexbrayat

repo: vuejs/vue-test-utils-next


text:
chore: fix missing rollup dependency

Couldn't build the project with yarn build unless I added this dependency. Can someone validate that this is also happening for them?

I am building perfectly fine?

Are you really? Do you have the dependency that I added?

Ah, the dep is in the root and my environment was just messed up

authors: JessicaSachs dobromir-hristov

repo: vuejs/vue-test-utils


text:
Documentation Suggestion

Greetings,
First and foremost I believe Vue is a revolutionary framework. I have just started working with Vue and see great potential in the way we build applications for the future. With that being said I believed one of the many things that has helped frameworks like React, Angular, and Polymer grow so rapidly is a clear and concise direction on how to build, publish and distribute "Components" and "Component Libraries" not necessarily Applications or SPAs. Although the webpack setup has great configuration for distributing your application, I have been able to find a seamless webpack setup that offers the same publishing/testing capabilities as the Vue templates.
I believe if clear directions on vuejs.org and/or configuration settings in the webpack/browserify templates also included publishing a single component or component library this could be the igniter to the rocket that set's Vue on an even higher level than other frameworks.
Kind Regards,
Ryan W.

Thanks for the suggestion! Moved to https://github.com/vuejs/vuejs.org/issues/585

Thank you Evan.
My apologies didn't realize there was a repo for the site.
On Tue, Nov 15, 2016, 9:08 AM Evan You notifications@github.com wrote:

Closed #4206 https://github.com/vuejs/vue/issues/4206.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue/issues/4206#event-859636262, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFFsSahX4w-LBNNFWhMuKJz5meuHFLFDks5q-djogaJpZM4KyrBd
.

repo: vuejs/vue


text:
IOS10 Safari浏览器中select唤起后，点击完成无法选择当前项目。

Version
2.4.2
Reproduction link
https://jsfiddle.net/smpd16g0/
Steps to reproduce
<select v-model="value">
        <option v-for="item in options" :value="item.value">{{item.name}}</option>
</select>

{
    value: null,
    options: [
        {name: '男', value: 1},
        {name: '女', value: 2},
        {name: '其他', value: 3}
    ]
}

在IOS Safari中点击下拉框，此时默认会选中第一个，随后点击完成按钮，select框没有选择任何数据。
What is expected?
点击完成按钮后，第一项会选中。
What is actually happening?
点击完成按钮后，未选择任何数据。必须滑动到其他选项再回到第一项才能选中。

Just met the same thing today!
<select v-model="value">
  <option v-for="item in options" :value="item.value" :disabled="item.disabled">
    {{item.name}}
  </option>
</select>

options.unshift({ name: '请选择', value: '', disabled: true })
// options.unshift({ name: 'pick one', value: '', disabled: true })

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
acmeideal@gmail.com
Domain biomassiv.es has exceeded the max emails per hour (113/100 (112%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext5.iad.github.net ([192.30.252.196]:34581 helo=github-smtp2a-ext-cp1-prd.iad.github.net)
by chi-server32.websitehostserver.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.89)
(envelope-from noreply@github.com)
id 1drlib-004GLK-Lp
for greg@biomassiv.es; Tue, 12 Sep 2017 08:59:13 -0500
Date: Tue, 12 Sep 2017 06:35:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1505223743;
bh=ZMdD1/xxyc/uY0ySnEgRhSxC1w/XmyTS4bGf+7IF5/g=;
h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=xHz6XZt5xDjvTtd7qfWwfzn8op4qmwAgancM0TVo5DtYGGsjYVj99ssaYEqlqA5mt
BtphXWblr6ocubP5HMEU/620MwS4osTHZmgurMMZhb65Adrc+AffgN0PHArTDIWgRb
AfwOjFz95J05x+HaizDkw1mkKpRUMW7iPxNmzRcA=
From: Fritz Lin notifications@github.com
Reply-To: vuejs/vue reply@reply.github.com
To: vuejs/vue vue@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Message-ID: vuejs/vue/issues/6581/328854818@github.com
In-Reply-To: vuejs/vue/issues/6581@github.com
References: vuejs/vue/issues/6581@github.com
Subject: Re: [vuejs/vue] IOS10 Safari浏览器中select唤起后，点击完成无法选择当前项目。 (#6581)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59b7e285ef877_2ce73f7fef3c3c385679b";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: fritx
X-GitHub-Recipient: biomassives
X-GitHub-Reason: subscribed
List-ID: vuejs/vue <vue.vuejs.github.com>
List-Archive: https://github.com/vuejs/vue
List-Post: mailto:reply@reply.github.com
List-Unsubscribe: mailto:unsub+0042d4e24b1e33d4661c51585323aa9652fc827e0e90e42c92cf0000000115cfa48592a169ce0f5070f9@reply.github.com,
https://github.com/notifications/unsubscribe/AELU4qNVHhyXP4wxoYad4lpM8UIdl80gks5shoiFgaJpZM4PUKDf
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: greg@biomassiv.es
----==_mimepart_59b7e285ef877_2ce73f7fef3c3c385679b
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Just met the same thing today!
<select v-model=3D"value">
  <option v-for=3D"item in options" :value=3D"item.value" :disabled=3D"it=
em.disabled">
    {{item.name}}
  </option>
</select>

options.unshift({ name: '=E8=AF=B7=E9=80=89=E6=8B=A9', value: '', disable=
d: true })
// options.unshift({ name: 'pick one', value: '', disabled: true })

-- =
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/vuejs/vue/issues/6581#issuecomment-328854818=
----==_mimepart_59b7e285ef877_2ce73f7fef3c3c385679b
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Just met the same thing today!
<select v-model=3D"value">
  <option v-for=3D"item in options=
" :value=
=3D"item.value" :disabled=3D"item.disabled">
    {{item.name}}
  </option>
</select>
=
options.unshift({ name: '=E8=AF=
=B7=E9=80=89=E6=8B=A9', value: '', disabled:<=
/span> true })
// options.unshift({ nam=
e: 'pick one', value: '', disabled: true })
&m=
dash;You are receiving this because you are subscribed to this thre=
ad.Reply to this email directly, view it on GitHub, or mute the thread.

=
----==_mimepart_59b7e285ef877_2ce73f7fef3c3c385679b--

This is a iOS system issue and we can't do much in Vue core. You have 2 workarounds:

Add a hidden optgroup before options: <optgroup hidden="true" disabled></optgroup>

Make sure to initialize the select with a default value that has a matching option.


text:
ASYNC Method called from Vue Template returns 'undefined'

Version
^2.5.13
Reproduction link
https://jsfiddle.net/fsaiyed/ewgdh120/
Steps to reproduce
From the vue template, I'm calling a methods to render data as:
<td v-if="fieldNumber ==0">
         {{ getName(item.service) }}
     </td>

and in methods:
getName: async function (taskId) {
        taskId = await this.titleCase(taskId)
        let resultName = await deepRecord.deepRecord.getCurrentTraget(this.instanceId, taskId)
        let name = resultName.name
        console.log('Name: ', JSON.stringify(name))
        return name
      }

Here, in the console, I get the value, but it does not return to the template
What is expected?
Methods should return value
What is actually happening?
Method returns 'undefined'

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function#Return_value
Return value of async functions are Promise instances

Hi. Return value of an async function is a Promise instance so you should not use it in the template.
I've modified your fiddle and this is how it suppose to work: https://jsfiddle.net/gcva5bk4/.

Still doesn't work: https://jsfiddle.net/fsaiyed/ewgdh120/9/

@Justineo , your code will work if my str is static, but as given in the about example, my data loops through items. So here, I cannot call method from mounted.

@sodatea , Promise still returns empty object : https://jsfiddle.net/fsaiyed/ewgdh120/10/

Any help, please?

You were filing a bug report but it's actually the expected behavior so the issue is closed. Maintainers don't have to ask for permission to do this.

@Justineo , your code will work if my str is static, but as given in the about example, my data loops through items. So here, I cannot call method from mounted.

Just loop through your items to make multiple network requests and maintain the resolved value in an local data array. This is not something Vue should take care of and you should decide how to organize your application logic yourself.

@faizansaiyed, This kind of situation happens always, when you are implementing asynchronous operations. It can be solved using promise chaining which means

executing two or more asynchronous operations back to back, where each subsequent operation starts when the previous operation succeeds, with the result from the previous step.

const promise = doSomething();
const promise2 = promise.then(successCallback, failureCallback);
so here is the modified JSFiddle
I hope it's helpful.
Enjoy!

authors: Justineo Nabute faizansaiyed fsaiyedOB sodatea


text:
Using  statement evaluated as a function(e.g. f.bind()) inside v-on handler doesn't work

Version
2.5.21
Reproduction link
https://codesandbox.io/s/vq4rx8pzk7?module=%2Fsrc%2FApp.vue
Steps to reproduce
Use method with bind()(e.g. someMethods.bind(this)) in v-on handler
<button v-on:click="handleButtonClick.bind(this);">not working</button>

What is expected?
When the event triggered,  the registered method handler should be called.
What is actually happening?
The registered method is not called. some.Methods.bind(this) is recognized as simple inline statement.

It's expected. Vue will invoke the handler for you only if you provide a property path or a function literal.
https://github.com/vuejs/vue/blob/0ed0aad77228b95e9a61a87386736938837527f8/src/compiler/codegen/events.js#L99-L106
BTW, You don't need to call bind because methods are already bound to the component instance, unless you mistakenly used arrow functions.

authors: Justineo jaeseokk


text:
Vue.version

Vue.version update to 1.0.9

Thanks for the PR - this has been fixed as part of the build script updates.


text:
add ignoring WebStorm project folder

Duplicate of https://github.com/vuejs/vue/pull/4383

as @petervmeijgaard said. See #4383 for the explanation

authors: miherlosev petervmeijgaard posva


text:
[Bug report]When I add a plug-in in config.js, an error will be reported

Error message
TypeError: plugins.reduce is not a function
    at Object.resolvePluginsFromConfig (E:\vue\blog\node_modules\@vuepress\core\lib\app\resolvePluginsF
romConfig.js:13:20)
    at Object.createBaseApp (E:\vue\blog\node_modules\@vuepress\core\lib\app\createBaseApp.js:47:48)
    at Object.createDevApp (E:\vue\blog\node_modules\@vuepress\core\lib\app\createDevApp.js:10:33)
    at dev (E:\vue\blog\node_modules\vuepress\node_modules\@vuepress\cli\lib\commands\dev\createDev.js:
27:28)

I want to use the vssue plugin in vuepress, but when I configure it in config.js, only the array method can be used to start successfully. If the object method is used, this error will occur
module.exports = {
    plugins: {
            '@vssue/vuepress-plugin-vssue': {
                platform: 'github',
                clientId: '9566158....',
                clientSecret: '28787d76277...',
                owner: '',
                repo: '',

            },
        },
}

I use this method to report an error

This is because that the vssue plugin is not yet compatible with the latest version of VuePress v2.0 you can wait for the author to update it or If you are a coder you can fork repository and update it.

What @ramesh-dada said is correct. Also, the Object style config is not supported in v2.

@ramesh-dada thanks very much

@meteorlxy @ramesh-dada I looked at the vuepress documentation and saw the plug-in where the object can be used. I thought something went wrong, thank you very much

authors: meteorlxy qsyyke ramesh-dada

repo: vuepress/vuepress-next


text:
🛑 b.emdayo is down

In db35ae0, b.emdayo (https://b.emdayo.fr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: b.emdayo is back up in 80e9f52.


text:
Unsound push_constants command implementation

The current implementation of push_constants in auto.rs has many problems:
1- Serious buffer overflow bug (increment offset with same size):
https://github.com/vulkano-rs/vulkano/blob/4f094396ad7f8452e44ff6a907bfe43603e5c37f/vulkano/src/command_buffer/auto.rs#L1874-L1877
2- When calling push_constants we don't know which stages will be pushed to:
If you have multiple stages, it will try to include as many as it can.
For example if you have these push_constant ranges:
fragment (0..4)
vertex (0..4)

It will push to the two of them, even if the content is different, for example:
fragment:
layout(push_constant) uniform PushConstantData1 {
    uint a;
} pc;

vertex:
layout(push_constant) uniform PushConstantData2 {
    uint b;
} pc;

3- Also there is a bug in selecting the stages, if you have two stages
fragment (0..4)
vertex (0..8)

And you pushed struct of size 8, it will push to the two of them, which invalidates
VUID-vkCmdPushConstants-offset-01795
For each byte in the range specified by offset and size and for each shader stage in stageFlags, there must be a push constant range in layout that includes that byte and that stage

I'll create a PR on making it mandatory to supply the stage that is needed, and also fix the buffer overflow bug.
Any other suggestions to improve push_constants handling?

I'm not sure if you understood it that way, but there isn't different push constant data for different stages. Rather, there is one set of data for all stages, and each stage declares (in the pipeline layout) which part of that data it's going to access. So in the example you gave for point 2, a and b will always map to the same data, the data can't be set for each one separately.
To actually make them map to different ranges, you'd do it like this:
layout(push_constant) uniform PushConstantData1 {
    layout(offset = 0) uint a;
} pc;

layout(push_constant) uniform PushConstantData2 {
    layout(offset = 4) uint b;
} pc;

Now, one stage has the range 0..4 and the other has 4..8.

Yes, your example is correct if we want to push two data using one push_constant command.
But Vulkan allows to push two separate data and changing the ShaderStageFlags bits, in our current implementation, we can't do that.

"Incrementally" means between one draw/dispatch command and the next. But there is only one set of data per single draw/dispatch command, one command will always use the current push constant data for all stages. The stageFlags value doesn't indicate that the new data only affects those stages, but rather it's simply a value that you must set to indicate all stages whose range overlaps the data you're setting. That's what VUID-vkCmdPushConstants-offset-01796 indicates. You can experiment a bit with it and see.

I think I might have misunderstood some parts of it, I'll experiment it.

If push_constants was called two times:

offset=0, size=4, data=123u32
offset=4, size=4, data=456u32

Does that mean that all shaders will get the same data: [123u32, 456u32]?

Yes, assuming that they access the whole 0..8 range.

Then, it is be possible to handle push_constants without having to pass the stages flags. Only need to fix the bugs.

The stage flags must be set in order to do what VUID-vkCmdPushConstants-offset-01796 requires. The code here figures out the stages automatically:
https://github.com/vulkano-rs/vulkano/blob/4f094396ad7f8452e44ff6a907bfe43603e5c37f/vulkano/src/command_buffer/auto.rs#L1843-L1871

My plan to fix point 3. is to call cmdPushConstants multiple times, each with correct offset and size

I don't think 3 is an error at all. The VUID just means "every byte must be in at least one of the push constant ranges". And in this case it is, since all 8 bytes are within the vertex stage's range.

Actually it is, the validator reports it, that's what got me to investigate it

Hmm that may mean the code above has a bug in it then. What error did the validator give?

Thread 1, Frame 0:
vkCreatePipelineLayout(device, pCreateInfo, pAllocator, pPipelineLayout) returns VkResult VK_SUCCESS (0):
    device:                         VkDevice                         = 0x56055c03a980
    pCreateInfo:                    const VkPipelineLayoutCreateInfo* = 0x7faf20e8eeb8:
        sType:                          VkStructureType                  = VK_STRUCTURE_TYPE_PIPELINE_LAYOUT_CREATE_INFO (30)
        pNext:                          const void*                      = NULL
        flags:                          VkPipelineLayoutCreateFlags      = 0
        setLayoutCount:                 uint32_t                         = 1
        pSetLayouts:                    const VkDescriptorSetLayout*     = 0x7faf20e8f100
            pSetLayouts[0]:                 const VkDescriptorSetLayout      = 0x7faf1c01b8a0
        pushConstantRangeCount:         uint32_t                         = 2
        pPushConstantRanges:            const VkPushConstantRange*       = 0x7faf20e8efdc
            pPushConstantRanges[0]:         const VkPushConstantRange        = 0x7faf20e8efdc:
                stageFlags:                     VkShaderStageFlags               = 1 (VK_SHADER_STAGE_VERTEX_BIT)
                offset:                         uint32_t                         = 0
                size:                           uint32_t                         = 24
            pPushConstantRanges[1]:         const VkPushConstantRange        = 0x7faf20e8efe8:
                stageFlags:                     VkShaderStageFlags               = 16 (VK_SHADER_STAGE_FRAGMENT_BIT)
                offset:                         uint32_t                         = 0
                size:                           uint32_t                         = 72
    pAllocator:                     const VkAllocationCallbacks*     = NULL
    pPipelineLayout:                VkPipelineLayout*                = 0x7faf1c0201e0

.....

VUID-vkCmdPushConstants-offset-01795(ERROR / SPEC): msgNum: 666667206 - Validation Error: [ VUID-vkCmdPushConstants-offset-01795 ] Object 0: handle = 0x7faf1c06ec10, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x27bc88c6 | vkCmdPushConstants(): VK_SHADER_STAGE_VERTEX_BIT|VK_SHADER_STAGE_FRAGMENT_BIT, VkPushConstantRange in VkPipelineLayout 0x7faf1c0201e0[] overlapping offset = 0 and size = 72, do not contain VK_SHADER_STAGE_VERTEX_BIT. The Vulkan spec states: For each byte in the range specified by offset and size and for each shader stage in stageFlags, there must be a push constant range in layout that includes that byte and that stage (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkCmdPushConstants-offset-01795)
    Objects: 1
        [0] 0x7faf1c06ec10, type: 6, name: NULL
Thread 1, Frame 3:
vkCmdPushConstants(commandBuffer, layout, stageFlags, offset, size, pValues) returns void:
    commandBuffer:                  VkCommandBuffer                  = 0x7faf1c06ec10
    layout:                         VkPipelineLayout                 = 0x7faf1c0201e0
    stageFlags:                     VkShaderStageFlags               = 17 (VK_SHADER_STAGE_VERTEX_BIT | VK_SHADER_STAGE_FRAGMENT_BIT)
    offset:                         uint32_t                         = 0
    size:                           uint32_t                         = 72
    pValues:                        const void*                      = 0x7faf1c038eb0

I have these p

repo: vulkano-rs/vulkano


text:
Update reject case of new structured CVE's

If this Pull Request is work in progress, Add a prefix of “[WIP]” in the title.
What did you implement:
I updated the logic to handle newly structured CVEs that are rejected. The change ensures that CVEs with descriptions starting with "Rejected reason:" are also ignored, in addition to those containing "** REJECT **".
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Ran the application with test data and confirmed they are handled correctly.
Checklist:
You don't have to satisfy all of the following.

[ ] Write tests
[ ] Write documentation
[x] Check that there aren't other open pull requests for the same issue/feature
[ ] Format your source code by make fmt
[ ] Pass the test by make test
[ ] Provide verification config / commands
[ ] Enable "Allow edits from maintainers" for this PR
[ ] Update the messages below

Is this ready for review?: YES

close by https://github.com/vulsio/go-cve-dictionary/pull/387

repo: vulsio/go-cve-dictionary


text:
Fix Tests

Although this is not a priority, several of the tests need to be updated to be compatible with the now-updated dependencies. This will also fix the Build:Failing message on the git page.

In case this becomes a nightmare which sucks time and energy: Ping me and we postpone to a later milestone.

authors: cjfreeze wintermeyer

repo: vutuv/vutuv


text:
Using several "PushToOverlay", don't behave as expected

Only one overlay can be open, if i trigger the second one the first one closes and viceversa

New overlay system fixes this.

New overlay system fixes this.

authors: lasalillo sebescudie


text:
Petting zoo API

I created a petting zoo environment that wraps around the MicroRTSGridModeSharedMemVecEnv. I tested it on the petting zoo api test and it passed.

I think I also included some of the changes to the hello_world.py and vec_env.py, please ignore them.

Hey @BolunDai0216, thanks for this PR. I have added a few things: 1) added pettingzoo to poetry, 2) added rendering.
Also, please run poetry run pre-commit run --all-files to format code and remove unused imports.

bool(done[i].astype) is basically bool(False.astype), which will evaluate to true :) So I went ahead and fixed it.

@BolunDai0216 Fixed a few things now it kind of works:
https://user-images.githubusercontent.com/5555347/158036008-802c0802-760f-46b7-aef0-321fb45e3468.mp4

I have added a checklist of todo items. @BolunDai0216 if you could work on those that will be great :D Thanks again for this awesome contribution.

I have added a checklist of todo items. @BolunDai0216 if you could work on those that will be great :D Thanks again for this awesome contribution.

Thanks for listing the tasks! I will try to tackle them.

Hey just following up with this. I think just adding a simple test case and a section in the readme would be enough

Hey just following up with this. I think just adding a simple test case and a section in the readme would be enough

Sure, I plan to do it tonight.

Introduce efficient valid action sampling in hello_world.py #71

I see that you changed the keywork "mask" in the dict returned by observe() to "action_mask". I think given that there is a difference in the definition of what the action mask does in pettingzoo and what we currently have it will not pass the pettingzoo api test. That was the reason I named it "mask" instead. What are your thoughts on this?

I see that you changed the keywork "mask" in the dict returned by observe() to "action_mask". Given that there is a difference in the definition of what the action mask does in pettingzoo and what we currently have, it will not pass the pettingzoo api test. That was the reason I named it "mask" instead. What are your thoughts on this?

Oh really? Hmm, but that chess environment (https://www.pettingzoo.ml/classic/chess) has the same observation dictionaries; why would it pass the API test cases?

I see that you changed the keywork "mask" in the dict returned by observe() to "action_mask". Given that there is a difference in the definition of what the action mask does in pettingzoo and what we currently have, it will not pass the pettingzoo api test. That was the reason I named it "mask" instead. What are your thoughts on this?

Oh really? Hmm, but that chess environment (https://www.pettingzoo.ml/classic/chess) has the same observation dictionaries; why would it pass the API test cases?

I think in the case of checkers the action mask assigns a 0 or 1 value to every possible action (e.g. move from one position to another one). In our case the action mask assigns 0 and 1s to create the legal action space.

I think in the case of checkers the action mask assigns a 0 or 1 value to every possible action (e.g. move from one position to another one). In our case the action mask assigns 0 and 1s to create the legal action space.

Our action mask would also assign 0 or 1 to every possible action… I think?

So with the current definition the petting zoo test case would not pass?

So with the current definition the petting zoo test case would not pass?

Yeah, I think so. Naming it "mask" or anything other than "action_mask" will bypass this issue.

I accidentally clicked request approve...

So the only part of the api tests that look at the 'action_mask' part of the observation is the loop that plays through the actions:
        elif isinstance(prev_observe, dict) and 'action_mask' in prev_observe:
            action = random.choice(np.flatnonzero(prev_observe['action_mask']))
        else:
            action = env.action_space(agent).sample()

This is not meant to be a strong gate claiming that the action mask should be used in a particular way, but it was just useful for some of the environments currently in pettingzoo. We can certainly discuss changes to this loop to make it work for your case.

@vwxyzjn I've definitely considered having the action space contain the illegal action logic, however, it does not seem like the right abstraction. The action space is some static meta-information about the action, allowing for creation of persistent functions like neural networks. It does not appeal to me that the action space would be overloaded to also contain this state-dependent action masking logic.
However, I do wonder if action sampling/masking is worth having better builtin support for, as openspiel or some other marl libraries have.
One possible idea I just came up with would be action_space.sample(obs['action_mask']). I.e. have the space interpret and sample from the given mask.
Another possible idea is to to simply have a utility pettingzoo.sample(action_space, obs) which handles a bunch of different cases, including discrete and multidiscrete.

Hey, sorry for the late response. It has been really hectic recently. Building better validation petting zoo APIs would be a separate issue, and let's not block this PR. @BolunDai0216, sorry for the delay. I have renamed the action_mask key to the action_masks key temporarily until the pettingzoo upstream has a better API for this @benblack769 @jkterry1.
@BolunDai0216 thanks for contributing this PR :)

repo: vwxyzjn/gym-microrts


text:
Email Error: ApiService: Error: Request failed with status code 500

Docker Log doesn't show anything helpful that I could see.
[GIN] 2020/08/26 - 21:31:30 | 401 |      58.876µs |    70.66.37.212 | GET      "/api/v1.0/client/7dd1c67a-daf6-4843-beda-fa19b5a1af28/email"
[GIN] 2020/08/26 - 21:31:30 | 200 |       104.6µs |    70.66.37.212 | GET      "/"
[GIN] 2020/08/26 - 21:31:30 | 200 |     596.848µs |    70.66.37.212 | GET      "/js/chunk-vendors.85a05be0.js"
[GIN] 2020/08/26 - 21:31:30 | 200 |     148.216µs |    70.66.37.212 | GET      "/js/app.68f6b65a.js"
[GIN] 2020/08/26 - 21:31:31 | 200 |     162.375µs |    70.66.37.212 | GET      "/css/Clients.b58a7d31.css"
[GIN] 2020/08/26 - 21:31:31 | 200 |      46.867µs |    70.66.37.212 | GET      "/api/v1.0/auth/oauth2_url"
[GIN] 2020/08/26 - 21:31:31 | 200 |     209.766µs |    70.66.37.212 | GET      "/js/Clients.34dc9b04.js"
[GIN] 2020/08/26 - 21:31:31 | 200 |      87.589µs |    70.66.37.212 | POST     "/api/v1.0/auth/oauth2_exchange"
[GIN] 2020/08/26 - 21:31:31 | 200 |     190.419µs |    70.66.37.212 | GET      "/js/Clients~Server.d72886b6.js"
[GIN] 2020/08/26 - 21:31:31 | 200 |     205.766µs |    70.66.37.212 | GET      "/js/Server.1d2011ab.js"
[GIN] 2020/08/26 - 21:31:31 | 200 |     228.314µs |    70.66.37.212 | GET      "/css/Clients~Server.4dad6da0.css"
[GIN] 2020/08/26 - 21:31:31 | 200 |      86.037µs |    70.66.37.212 | GET      "/api/v1.0/auth/user"
[GIN] 2020/08/26 - 21:31:31 | 200 |      57.274µs |    70.66.37.212 | GET      "/api/v1.0/server/version"
[GIN] 2020/08/26 - 21:31:31 | 200 |     198.925µs |    70.66.37.212 | GET      "/api/v1.0/server"
[GIN] 2020/08/26 - 21:31:31 | 200 |     235.897µs |    70.66.37.212 | GET      "/api/v1.0/client"
[GIN] 2020/08/26 - 21:31:31 | 200 |      98.538µs |    70.66.37.212 | GET      "/favicon.png"
[GIN] 2020/08/26 - 21:31:31 | 200 |      87.517µs |    70.66.37.212 | GET      "/api/v1.0/server/config"
[GIN] 2020/08/26 - 21:31:31 | 200 |      420.37µs |    70.66.37.212 | GET      "/api/v1.0/client/bb5c5b45-3ee4-4de5-9950-7ed2130bd967/config?qrcode=false"
[GIN] 2020/08/26 - 21:31:31 | 200 |     382.183µs |    70.66.37.212 | GET      "/api/v1.0/client/7dd1c67a-daf6-4843-beda-fa19b5a1af28/config?qrcode=false"
[GIN] 2020/08/26 - 21:31:31 | 200 |   12.729587ms |    70.66.37.212 | GET      "/api/v1.0/client/bb5c5b45-3ee4-4de5-9950-7ed2130bd967/config?qrcode=true"
[GIN] 2020/08/26 - 21:31:31 | 200 |   14.782369ms |    70.66.37.212 | GET      "/api/v1.0/client/7dd1c67a-daf6-4843-beda-fa19b5a1af28/config?qrcode=true"

Can you please share your setup config (env variables) ? Which request result on 500 response ? see devtools on your navigator

Configuration file for docker-compose.yml
version: '3.3'
services:
    wg-gen-web:
        network_mode: host
        privileged: true
        volumes:
          - '/etc/wireguard:/data'
        ports:
          - '8080:8080'
        environment:
          - WG_CONF_DIR=/data
          - WG_INTERFACE_NAME=wg0.conf
          - SMTP_HOST=my.email.server
          - SMTP_PORT=587
          - SMTP_USERNAME=servers@mycompany.com
          - SMTP_PASSWORD=xxxxxxxxxxxxxxxxx
        image: 'vx3r/wg-gen-web:latest'

I have NGINX handling basic auth at the moment and 443
devtools -
Error: ApiService: Error: Request failed with status code 500
    get api.service.js:14
    promise callback*get api.service.js:13
    email client.js:80
    w vuex.esm.js:792
    dispatch vuex.esm.js:457
    dispatch vuex.esm.js:347
    dispatch vuex.esm.js:720
    r vuex.esm.js:1005
    email Clients.vue:558
    click Clients.vue:19
    VueJS 4
    click VBtn.js:126
    VueJS 33

Hope that helps

license: WTFPL


text:
Manage Peers using wg-api

I would like to manage remote wireguard installs without having to copy the wireguard config files there and reloading wg.
wg-api seems to be a perfect fit for this usecase as it allows to create and remove peers using the api. Persistence is ensured using SaveConfig in the wg-quick config.

i am thinking about rewriting whole project to use wg-api but a couple of things are blocking:

all components in docker containers ?
how to manage networking rules (nat) ?

Personally I have wg-gen-web running in docker on my Synology nas, wireguard on my rpi4 and wg-api in docker on rpi4.

I would suggest using https://github.com/WireGuard/wgctrl-go directly (that is also what wg-api uses internally), so you do not need an separate container for wg-api. I use it myself in https://github.com/h44z/wg-portal and it works flawlessly.


text:
Manifest version 2 is deprecated, and support will be removed in 2023.

Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.
{
// Required
"manifest_version": 2,
"name": "Long Press New Tab",
"version": "4.1",
// Recommended
"description": "Open links as background tabs by clicking links and holding",
"icons": {
    "16": "img/icon16.png",

This is one of my must have extensions! Thanks for the notice and I hope the developer or others can provide a fix when January 2023 arrives.

Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.

@p3P4 @ceedveed
Extension has been updated to manifest version 3 through #8 .
Overall, this was a fairly big change, so there may be a few bugs, but core functionality should be the same.

Now that I've been using it more, I'd say best to continue to use MV2 version until closer to the transition deadline.
IMO, this extension relies heavily on persistent background and MV3 at its current state does not allow that so sometimes it will not open new tab until the page refreshes.

@ceedveed
Yes, I would recommend still using the MV2 version as it is still working perfectly for me. Google has pushed back MV2 deprecation timeline to TBD. And I've been pretty busy with work and life so haven't had the time to look more into MV3.
I will support this extension to the best of my ability, as this is a feature I have used since the OG Opera days.


text:
Undefined behavior involving shifts of negative numbers

Hi Zsolt! First of all thanks for the great work. Library's been very helpful. Now when compiling it under clang with the undefined behavior sanitizer on, I get messages about left shifts of signed (negative) integers being undefined. As there are a lots of them, I cannot really use the sanitizer anymore to find undefined behavior in my own code 🙂
Also it seems to be a good idea to fix this anyway (even though the code is working fine!). See this  https://github.com/jedisct1/libsodium/issues/333 for a more detailed discussion (same issue occured in libsodium) and why it's good to fix it.
Could you have a look into this? Perhaps it is as simple as importing a new version of the upstream code.

Hi @pixelspark and thanks for the report!
Unfortunately the upstream library hasn't been updated in 6 months (2 months older than my copy), and is also affected. I will take a stab at fixing the issue here first, using the libsodium discussion and PRs as the base.

I took some ideas from the libsodium discussion for some mechanical changes to the problematic shifts – in Xcode, the isses went away while running the tests in the project.
I have tagged 0.1.1-beta.1 on the PR's branch, can you please test if this clears up the sanitizer's errors on your side, and if your project is still working correctly?

authors: pixelspark vzsg


text:
ALE may not lint with shell=powershell

Information
VIM version
NVIM v0.3.1
Build type: RelWithDebInfo
Operating System: Windows 10 Home 64bit
Version 1803
OS build 17134.345
What went wrong
Does not lint stylelint for scss file, when set shell=powershell.
Is it related this issue https://github.com/w0rp/ale/issues/1298?
Reproducing the bug
I setted NeoVim terminal for Windows PowerShell by set shell=powershell in init.vim
ALE does no response.
So remove set shell=powershell, and restart NeoVim, ALE works correctly.
:ALEInfo
Current Filetype: scss
Available Linters: ['sasslint', 'scsslint', 'stylelint']
Enabled Linters: ['sasslint', 'scsslint', 'stylelint']
Suggested Fixers:
'prettier' - Apply prettier to a file.
'remove_trailing_lines' - Remove all blank lines at the end of a file.
'stylelint' - Fix stylesheet files using stylelint --fix.
'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
Linter Variables:
let g:ale_scss_stylelint_executable = 'stylelint'
let g:ale_scss_stylelint_options = ''
let g:ale_scss_stylelint_use_global = 0
Global Variables:
let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 1
let g:ale_fixers = {'css': ['stylelint']}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_lint_on_insert_leave = 0
let g:ale_linter_aliases = {}
let g:ale_linters = {'css': ['stylelint']}
let g:ale_linters_explicit = 0
let g:ale_list_window_size = 10
let g:ale_list_vertical = 0
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
Command History:
(executable check - failure) sass-lint
(executable check - failure) scss-lint
(executable check - success) D:\wocker\data\asite\wp-content\themes\venite\node_modules.bin\stylelint
(started) 'cmd /s/c ""D:\wocker\data\asite\wp-content\themes\atheme\node_modules.bin\stylelint"  --stdin-filename "D:\wocker\data\venite\wp-content\themes\atheme\sass_about.scss" < "C:\Users\akiya\AppData\Local\Temp\nvimsH258S\3_about.scss""'
(executable check - failure) sass-lint
(executable check - failure) scss-lint
(finished - exit code 1) 'cmd /s/c ""D:\wocker\data\asite\wp-content\themes\atheme\node_modules.bin\stylelint"  --stdin-filename "D:\wocker\data\asite\wp-content\themes\atheme\sass_about.scss" < "C:\Users\akiya\AppData\Local\Temp\nvimsH258S\4_about.scss""'
<<>>

There was a similar issue I saw a while ago with someone using either zsh or bash as their shell, where only the inverse worked. For what purpose does ALE rely on &shell, and is it possible to remove it?

After looking at some stuff, powershell should never be run on a win32 platform, AIUI. Are you sure this is because of &shell being powershell?

It is not sure set shell=PowerShell.exe cause no response ale.
How can I separate ale problem or another factor?
May be, this issue is for NeoVim or another.

I'm having the same issue. ALE breaks if I set shell=powershell in Neovim, but it works perfectly in Vim. Removing set shell=powershell allows ALE to work in Neovim and Vim.

How do you run NeoVim on Windows? What's the output of :echo has('win32')?

I'm running Neovim in powershell just by running nvim or nvim main.cpp.
I'm currently using a prerelease build of 0.4, but I have the same issue on 0.3.4.
:echo has('win32') returns 1.

I just pushed a commit now to force jobs to run in a CMD shell on Windows. Give it a try.

It seems to be working perfectly now. Thank you!

Okay, that should do it.

ALE is working on my Windows. Thanks!


text:
Update validator-selection-algorithm.md

Adding the section at the beginning and changing the weekly rate to 1500

@jonasW3F let me know if you are happy with these changes


text:
zkwasm rollup amend timeline

As I commented, I would like to amend timeline.
https://github.com/w3f/Grants-Program/pull/1487#issuecomment-1572935659

Thanks @ashWhiteHat much appreciated. I see that you added a table with the new timelines, however could you incorporate these new durations into the milestones as well? Since the contract started on Feb. 17th 2023, technically the overall estimated duration would be closer to 11 months now. I will make the suggested changes below in order for you to easily change them. Thanks!

Hi @keeganquigley
Thank you for the comment!
That makes sense to me.
I changed our PR accordingly.
I would appreciate it if you could confirm.
Thank you!

Hi there
Regarding Milestone 1, it passed test now so we are going to describe tutorial and get thing done by this week.
https://github.com/KogarashiNetwork/Kogarashi/pull/91/files#diff-569c4866ec743e47bcc4258ec42720e55d00c382c8bc859b2916a4fe4f2ae030R10

Hi @ashWhiteHat how is M3 coming along? Checking in since it was due around 6 months ago I believe.

Hi @keeganquigley
Thank you for the message.
For instance, this grant was amended and completed.
Following PR changed to the latest status.
https://github.com/w3f/Grants-Program/pull/2077
Summary of Above PR
zkwasm rollup was proposed as scaling solution by zero knowledge proof
however, introduction of core time and considering number of network validators, zero knowledge proof overhead costs more
so working on functionality by zero knowledge proof instead scaling solution
It was completed as follows.
https://github.com/w3f/Grant-Milestone-Delivery/pull/1092
Please ping me whenever you have questions.
Thank you!

Thanks @ashWhiteHat much appreciated. I did see the amendment but hadn't noticed that M3 + M4 were removed completely. I will adjust our records, thanks!

authors: ashWhiteHat keeganquigley


text:
hello, predecessor,why not update?

hello, predecessor,why not update?
have girlfirend, no forget blog~

Oh my friend,
I join 了 a company , then there is no more then....

authors: relign wagnlinzh


text:
Wagtail 5.1

Includes changes from this PR: https://github.com/wagtail/wagtail-autocomplete/pull/156
Upgrade related fixes:

Includes 4.0, 4.1, 4.2, 5.0, and 5.1 upgrade considerations
Removed Wagtail upperbound

Other fixes:

Configure github workflow for testing and use tox-gh-actions

Superseded by: https://github.com/wagtail/wagtail-autocomplete/pull/169

repo: wagtail/wagtail-autocomplete


text:
Report for (search) query hits

Is your proposal related to a problem?
In order to gain insight into the popular search teams as a content editor and/or marketeer I want to view a report.
Currently the only way is to view this by registering a (django) ModelAdmin config or use the popup via search promotions.
Describe the solution you'd like
An option to add a report with search teams with relevant filters via the settings, just as any other wagtail report.
As reports are not often familiar for content editors it would be nice to switch this feature on/off via django settings.
Working on this
We have capacity to create this report as a pull request. Planned already to implement this within an active project.

Sounds great @robmoorman! I can see why it’d be useful to view this information in a filterable / export-able report.

An option to add a report with search teams with relevant filters via the settings, just as any other wagtail report.
As reports are not often familiar for content editors it would be nice to switch this feature on/off via django settings.

From my perspective I’d expect the presence of the report by default for sites using this app to not be much of an issue, as reports have their own menu item to be hidden inside of. It’d be nice to align with other apps / reports on how exactly this is configurable

Ok great! We will see if we can put a PR in on short notice. I expect it's an easy feature to implement and review as it makes pretty sense what to do here and put in the report.
Looking at other "feature flags" the name of the setting can be something like WAGTAIL_SEARCHPROMOTION_REPORT_ENABLED (default set to True). It's sort of a convention to put the xxx_ENABLED to turn a feature on/off.

Completed in #12341.

authors: gasman robmoorman thibaudcolas

repo: wagtail/wagtail


text:
Improve error validation UX on user account creation

I just spent ten minutes trying to figure out why it was saying that my password was too common over and over even though I was entering really long, random strings.
When creating a new user in Wagtail settings, the process is as follows:

Enter user details including password
click roles button
add user roles
click add user button

Currently the content entered at step one doesn't get validated until step 4. This is particularly confusing because when you then update the content at step 1 (such as picking a more secure password) then click the roles button again, the original validation message still displays which makes it appear your update still has errors when it in fact will only validate again by clicking add user. I've added a video that hopefully explains this better than I can in words.
The simplest solution would be to validate on step 2  rather than step 4.
password-usability-issue.mov.zip

This seems to me like a general problem in Wagtail which we would want to address with Autosave (including auto-validation), rather than a change specifically to the user account form. Closing.

authors: thibaudcolas tmsndrs


text:
Avoid raising warning on missing use_json_field during migrations

Perform check in contribute_to_class so that we can skip it for fake models in migrations.
Also bump the deprecation up to RemovedInWagtail40Warning (since it's a multi-stage deprecation that will be strung out for too long otherwise)

I haven't put release notes for this, can do a bit later if you don't get to it first Matt

Thanks @lb-! I don't think this needs a release note, as it's a fix to a piece of code that's new in 3.0 (so it's covered by the original release note for that work).

no problems.

authors: gasman lb-


text:
Spanish Language

Added Spanish folder to application/

Thanks for the PR :)


text:
Add static, left and top properties

Hey @wakirin
We have a production SPA app and all screens are actually modals. With that, date picker always showing itself on wrong position.

I believe this and next line is the reason for that. https://github.com/wakirin/Litepicker/blob/2336ce1b0ac3a4ef733fda0eef8b9ef4dd99b0d0/src/core.ts#L271
There is no offset. It returns always 0. Just inline mode works as expected.
We researched the other date pickers and we saw the results someting similar.

But flatpickr giving us an option to resolve this issue with named static. Here: https://github.com/flatpickr/flatpickr/blob/31d0195b0cb8261685a3ec9093341bc54675fb09/src/index.ts#L2188
This option allows us to place datepicker statically next to element. This PR targets the same result.
Thank you.

I believe this and next line is the reason for that.
const scrollX = window.scrollX || window.pageXOffset;
There is no offset. It returns always 0. Just inline mode works as expected.

I am not sure about it.
window.scrollX || window.pageXOffset
In this case that mean if scrollX is exists and more than 0, then will use scrollX, since scrollX can't be less than 0, this line can't affect to wrong position.
pageXOffset is used for ancient browser (IE11), and it's ignored when scrollX have value more than 0.
It would be great to see the page with problem, if you don't want publish your url here, you can send me email.

authors: sinankeskin wakirin

repo: wakirin/Litepicker


text:
EventBase::loop(): Failed to invoke event callback, breaking the loop.

businessWorker运行一段时间之后产生以下报错信息，使用K8S部署，启动3个pod，只有1个pod出现这问题，不会同时出现；
------------------------------------------- WORKERMAN --------------------------------------------
Workerman version:4.1.11          PHP version:8.1.16           Event-Loop:\Workerman\Events\Event
-------------------------------------------- WORKERS ---------------------------------------------
proto   user            worker            listen          processes    status
tcp     root            BusinessWorker    none            12            [OK]
--------------------------------------------------------------------------------------------------
Press Ctrl+C to stop. Start success.
GatewayConnection Error : 2 ,client closed
Exception: connection close tcp://10.2.164.000:2301 in /home/htdocs/im/vendor/workerman/gateway-worker/src/Lib/Gateway.php:1182
Stack trace:
#0 /home/htdocs/im/vendor/workerman/gateway-worker/src/Lib/Gateway.php(1111): GatewayWorker\Lib\Gateway::sendAndRecv()
#1 /home/htdocs/im/vendor/workerman/gateway-worker/src/BusinessWorker.php(362): GatewayWorker\Lib\Gateway::getSession()
#2 /home/htdocs/im/vendor/workerman/workerman/Connection/TcpConnection.php(646): GatewayWorker\BusinessWorker->onGatewayMessage()
#3 [internal function]: Workerman\Connection\TcpConnection->baseRead()
#4 /home/htdocs/im/vendor/workerman/workerman/Events/Event.php(193): EventBase->loop()
#5 /home/htdocs/im/vendor/workerman/workerman/Worker.php(1629): Workerman\Events\Event->loop()
#6 /home/htdocs/im/vendor/workerman/workerman/Worker.php(1423): Workerman\Worker::forkOneWorkerForLinux()
#7 /home/htdocs/im/vendor/workerman/workerman/Worker.php(1397): Workerman\Worker::forkWorkersForLinux()
#8 /home/htdocs/im/vendor/workerman/workerman/Worker.php(560): Workerman\Worker::forkWorkers()
#9 /home/htdocs/im/src/Command/ServerCommand.php(129): Workerman\Worker::runAll()
#10 [internal function]: App\Command\ServerCommand->__invoke()
#11 /home/htdocs/im/vendor/minicli/minicli/src/App.php(239): call_user_func()
#12 /home/htdocs/im/vendor/minicli/minicli/src/App.php(218): Minicli\App->runSingle()
#13 /home/htdocs/im/app(27): Minicli\App->runCommand()
#14 {main}
PHP Warning:  EventBase::loop(): Failed to invoke event callback, breaking the loop. in /home/htdocs/im/vendor/workerman/workerman/Events/Event.php on line 193
worker[BusinessWorker:14] exit with status 64000
GatewayConnection Error : 2 ,client closed
GatewayConnection Error : 2 ,client closed
GatewayConnection Error : 2 ,client closed
PHP Warning:  stream_socket_client(): Unable to connect to tcp://10.2.164.000:2303 (Connection timed out) in /home/htdocs/im/vendor/workerman/gateway-worker/src/Lib/Gateway.php on line 1409
PHP Warning:  EventBase::loop(): Failed to invoke event callback, breaking the loop. in /home/htdocs/im/vendor/workerman/workerman/Events/Event.php on line 193
Exception: can not connect to tcp://10.2.164.000:2303 Connection timed out in /home/htdocs/im/vendor/workerman/gateway-worker/src/Lib/Gateway.php:1411
Stack trace:
#0 /home/htdocs/im/vendor/workerman/gateway-worker/src/Lib/Gateway.php(1165): GatewayWorker\Lib\Gateway::getGatewayConnection()
#1 /home/htdocs/im/vendor/workerman/gateway-worker/src/Lib/Gateway.php(1111): GatewayWorker\Lib\Gateway::sendAndRecv()
#2 /home/htdocs/im/vendor/workerman/gateway-worker/src/BusinessWorker.php(362): GatewayWorker\Lib\Gateway::getSession()
#3 /home/htdocs/im/vendor/workerman/workerman/Connection/TcpConnection.php(646): GatewayWorker\BusinessWorker->onGatewayMessage()
#4 [internal function]: Workerman\Connection\TcpConnection->baseRead()
#5 /home/htdocs/im/vendor/workerman/workerman/Events/Event.php(193): EventBase->loop()
#6 /home/htdocs/im/vendor/workerman/workerman/Worker.php(1629): Workerman\Events\Event->loop()
#7 /home/htdocs/im/vendor/workerman/workerman/Worker.php(1423): Workerman\Worker::forkOneWorkerForLinux()
#8 /home/htdocs/im/vendor/workerman/workerman/Worker.php(1397): Workerman\Worker::forkWorkersForLinux()
#9 /home/htdocs/im/vendor/workerman/workerman/Worker.php(560): Workerman\Worker::forkWorkers()
#10 /home/htdocs/im/src/Command/ServerCommand.php(129): Workerman\Worker::runAll()
#11 [internal function]: App\Command\ServerCommand->__invoke()
#12 /home/htdocs/im/vendor/minicli/minicli/src/App.php(239): call_user_func()
#13 /home/htdocs/im/vendor/minicli/minicli/src/App.php(218): Minicli\App->runSingle()
#14 /home/htdocs/im/app(27): Minicli\App->runCommand()
#15 {main}
worker[BusinessWorker:19] exit with status 64000

查询status 有一个进程是N/A  busy状态
Workerman[/home/htdocs/im/src/Command/ServerCommand.php] status
----------------------------------------------GLOBAL STATUS----------------------------------------------------
Workerman version:4.1.11          PHP version:8.1.16
start time:2023-09-13 11:09:39   run 0 days 9 hours
load average: 15.7, 17.4, 17.13  event-loop:\Workerman\Events\Event
1 workers       12 processes
worker_name    exit_status      exit_count
BusinessWorker 64000            3
----------------------------------------------PROCESS STATUS---------------------------------------------------
pid     memory  listening    worker_name    connections send_fail timers  total_request qps    status
9       2.84M   none         BusinessWorker 13          0         56      1031441       0      [idle]
10      N/A     none         BusinessWorker N/A         N/A       N/A     N/A           N/A    [busy]
11      2.81M   none         BusinessWorker 13          0         41      1017494       0      [idle]
12      2.81M   none         BusinessWorker 13          0         45      1008825       0      [idle]
13      2.82M   none         BusinessWorker 13          0         49      1006094       0      [idle]
16      2.84M   none         BusinessWorker 13          0         50      997295        0      [idle]
17      2.84M   none         BusinessWorker 13          0         54      1013818       0      [idle]
18      2.84M   none         BusinessWorker 13          0         58      986283        0      [idle]
21      2.86M   none         BusinessWorker 13          0         57      1016074       0      [idle]
2444    2.8M    none         BusinessWorker 13          0         50      1010678       0      [idle]
2989    2.75M   none         BusinessWorker 13          0         41      1003286       0      [idle]
6740    2.79M   none         BusinessWorker 13          0         56      36494         0      [idle]
----------------------------------------------PROCESS STATUS---------------------------------------------------
Summary 22M     -            -              143         0         557     10127782      0      [Summary]

请问作者大佬，此问题应该如何排查定位问题

10.2.164.000 ip错的
Message ID: @.***>

这是我为提交issue 隐藏机器IP 手动改掉的， 原本IP是对的 已核对过

请问负载是从load average: 15.7, 17.4, 17.13 得出吗，一般该值超出多少则可认为负载太高  该值在三种进程中的含义是否一致？（参考值是否一致）
是的  分布式部署
gatewayWorker进程有以下输出和status状态

frame not masked so close the connection
frame not masked so close the connection
frame not masked so close the connection
frame not masked so close the connection
frame not masked so close the connection
frame not masked so close the connection
frame not masked so close the connection
frame not masked so close the connection

Workerman[/home/htdocs/im/src/Command/ServerCommand.php] status
----------------------------------------------GLOBAL STATUS----------------------------------------------------
Workerman version:4.1.11          PHP version:8.1.16
start time:2023-09-13 11:09:50   run 0 days 10 hours
load average: 22.3, 20.97, 20.85 event-loop:\Workerman\Events\Event
1 workers       4 processes
worker_name  exit_status      exit_count
Gateway      0                0
----------------------------------------------PROCESS STATUS---------------------------------------------------
pid     memory  listening                worker_name  connections send_fail timers  total_request qps    status
9       7.85M   websocket://0.0.0.0:1216 Gateway      1154        4         3       25770080      0      [idle]
10      9.19M   websocket://0.0.0.0:1216 Gateway      1377        9         3       27351740      0      [idle]
11      8.04M   websocket://0.0.0.0:1216 Gateway      1190        5         3       25933475      0      [idle]
12      8.83M   websocket://0.0.0.0:1216 Gateway      1321        7         3       26545133      0      [idle]
----------------------------------------------PROCESS STATUS---------------------------------------------------
Summary 32M     -                        -            5042        25        12      105600428     0      [Summary]

load average: 15.7, 17.4, 17.13
是负载，一般不超过cpu核心数70%

好的，我先尝试扩容降低负载再观察是否还有loop的问题 谢谢大佬

你们是压测么？
gatewayWorker内部接口调用(例如Gatway::sendToAll())一般会与所有gateway进程通讯一次，所以整个集群的gateway进程数越少整个集群效率越高，负载越低。如果系统是因为内部频繁Gateway接口调用导致的负载高，增加gateway服务器并不能减少负载，反而会让负载更高。
如果你们有非常频繁的Gateway接口调用，gateway服务器建议只开两台服务器，每台只开2个进程，可以降低整个集群负载。

不是压测，是正式环境的请求量
目前gatewaWorker的进程数量为：3个节点，每个节点4个进程。
会频繁调用Client::sendToUid()

不是压测，是正式环境的请求量 目前gatewaWorker的进程数量为：3个节点，每个节点4个进程。 会频繁调用Client::sendToUid() 我们尝试一下降低gatewayWorker进程数量观察一下负载

现在怎么样了。

authors: twomiao walkor xuanyanwow

repo: walkor/GatewayWorker


text:
Videojs-transcript is not working with videojs version 7

When I tried to use videojs-transcript with with videojs version 7.18 , its not working. But where as if I use videojs 4.12 then its working as expected. Can you give support for updated versions as well?

Use tombyrer/videojs-transcript-click@1.0
var video = videojs('video')
video.ready(function(){
  var transcript = this.transcript();
  var transcriptContainer = document.querySelector('#transcript');
  transcriptContainer.appendChild(transcript.el());
});

authors: pradeepaanumalla wemrekurt


text:
Console like in node.js, port node.js util module (contains functions…

… required for console to work)
You can't argue that node.js (or devtools) console works better than ScriptCraft's.
Main differences:

functions support multiple arguments console.log("a", 1, "b") -> a 1 b
better handling of objects console.log({}) -> {} instead of [object Object]

No backwards compatibility breaks. As an additional value, developers can use other functions available in util.js module, like util.inherits() or type checking functions.

I'm not comfortable with bringing in node-specific Joyent-owned code into ScriptCraft's codebase - e.g. debuglog is node-specific. Is there a cleaner way?

The copyright in there is pretty clearly open to this usage though... What gives you pause?

This is over a year old now. I'd rather have this than another year of waiting for a PR of a cleaner way, would prevent testing requiring multiple console.logs for every variable and JSON.stringify()ing all of them.

On one hand this looks like a good enhancement, and the license is clear that this usage is approved. On the other hand, I agree with @walterhiggins that there are other concerns.
First, there are Node-specific remnants in there which may require debugging. For example, the process global is Node-specific, not available in Rhino or SC. So on its own we see one obvious issue in the code.
I'm not suggesting the code is buggy or inadequate. But as-is it's simply not ready for inclusion. If we know before it's merged that there is an open question, then the maintainer(s) of this package have already accepted a development burden (of arguable size). This project already has a number of issues that could use attention. Adding another one won't help.
Second, consider maintenance. What if the code gets a nice enhancement or fix elsewhere. Does it fall to the maintainer(s) here to retrofit the change here? What if a bug is found in the integration with SC? Will issues will have to be reported to and resolved by Joyent, or will uswill be asked to just pull the module from their code? Who looks like the bad guy if that happens?
I'm just saying we don't know what else is in there without more research. Now, perhaps Walter would agree to a merge if you guys volunteer to do that research: edit down that code a bit to remove external "dependencies", test the port on your own, and document ScriptCraft-specific usages in a small test suite that exercises defined functionality. Yeah, I know, it's a hassle. And I understand that the code should function as-is, even with or without process and whatever other globals might be in there. If you're not inclined to do this, consider it's exactly the effort that you're asking someone else to do. Please help. If you do, I don't think this will be too tough to get by the boss. ;)

authors: MrVoltz TonyGravagno demipixel djMax walterhiggins

repo: walterhiggins/ScriptCraft


text:
Does it work on Expo.dev?

Recently, I needed to use Crisp inside an application with Expo. I tried using this library, but it didn't work. Is there a specific walkthrough for apps that use expo?
Ps: I use expo SDK 41.
Expo Doc: https://docs.expo.dev/versions/v41.0.0

I have made a PR to support custom dev client : https://github.com/walterholohan/react-native-crisp-chat-sdk/pull/76

@mateusw3c I just release version 0.11.0 which includes expo support. Thank you @mlecoq

authors: mateusw3c mlecoq walterholohan


text:
TensorFlow 2: TensorBoard import error

wandb --version && python --version && uname

Weights and Biases version: 0.9.3
Python version: 3.6.9
Operating System: Linux

Description
I am trying to sync the client with TensorBoard in a Docker container with the TF2.2 base image. However, the client is unable to import TensorBoard, although I can import this package just fine. Related issue.
What I Did
I have created a minimal repository to reproduce the issue.
git clone https://github.com/pascal-hwky/wandb-tb-bug.git
cd wandb-tb-bug
./run.sh

Sample output:
wandb: Dry run mode, not syncing to the cloud.
wandb: Tracking run with wandb version 0.9.3

...

wandb: ERROR Couldn't import tensorboard, not streaming events. Run `pip install tensorboard`
wandb: Program ended successfully.
wandb: You can sync this run to the cloud by running:
wandb: wandb sync wandb/dryrun-20200716_123910-351imp5c

Any help is appreciated, as I cannot currently use my favorite experiment tracking framework with the Object Detection API. Running in Docker is a requirement for me, I cannot use virtual environments as suggested in the previous issue.

Hi there, thank you for reporting. I'm filing an internal ticket for this. We'll look into this and get back to you.

Hi @tyomhak, do you have any update on this issue? Were you able to reproduce it?

Any updates on this issue? I have it with tensorflow 2.3.0 too.

Apologies for the delay.  The issue is being caused by sys.path issue messing up our ability to import tensorboard.  We've fixed this in our latest library.  You can install it with pip install wandb -U --pre.  I've verified this works in the example docker image provided.

Can confirm this is fixed in version 0.10.2.

authors: ktobah pascal-hwky tyomhak vanpelt

repo: wandb/client


text:
Add Korean i18n support

Thank you for making this awesome theme !

Thanks!

authors: jungwone wangchucheng

repo: wangchucheng/hugo-eureka


text:
missing  video_base4_m

The video_base4_m file is missing. Could you please add this modle file? Thank you very much!

Could you provide the detailed errors?

------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2024年6月13日(星期四) 晚上9:41
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [wangchx67/BCNet] missing  video_base4_m (Issue #2)
Could you provide the detailed errors?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

谢谢，感谢，这个错误我排除了。
------------------ 原始邮件 ------------------
发件人:                                                                                "wangchx67/BCNet"                                                                                @.>;
发送时间: 2024年6月13日(星期四) 晚上9:41
@.>;
@.@.>;
主题: Re: [wangchx67/BCNet] missing  video_base4_m (Issue #2)
Could you provide the detailed errors?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


text:
使用非线性函数决定按压时间

https://github.com/wangshub/wechat_jump_game/issues/64 在这里我给出我提出的这个issue的解决方案
第86行改为distance的0.85次方再乘以press_coeffcient，相应的press_coeffcient调为3.705
在经过调试后发现用3.705可以实现几乎次次跳到中心
原理大致为：可以认为跳起距离是按压时间的n次函数，距离=时间^n，1<n<2，相应的，代码中算出距离后再来计算时间时，时间=距离^（1/n），这里我试验中初步取1/n=0.85
使用这个修改过的代码，我的棋子最高连续40次跳到中心

感谢～ @VitalyAnkh

authors: VitalyAnkh wangshub


text:
Shell completion for code

It would be nice to have wormhole accept 6-<tab> do shell completion instead of having to enter the program. Click supports dynamic generation of completion options, so the list of codes could be generated on the fly.

Ooh, that would be pretty neat.
One wrinkle.. to support localized wordlists some day (i.e. sender chooses the language, receiver gets tab-completion in the language they picked), the receiving side doesn't really know which wordlist to use until they've claimed the "nameplate" (the numerical part of the code). And once they've claimed it, nobody else can claim it. The code-entry state machine goes from a "no nameplate, no wordlist" state, to "have nameplate, have wordlist, waiting for words" state.
I believe that bash's application-specific tab completion works by running the target program with some special "if I ran you with arguments X, what completions Y would you recommend?" mode or flag or environment variable or something. That means we'd run wormhole once, it would see the nameplate 6 and claim it, learn the wordlist, emit the list of completions, and then exit. Then, later, wormhole would be run again, now with 6-word-word or something. But by that point the nameplate would have been claimed by the first invocation, leaving the second invocation out in the cold. The first invocation doesn't have a way to leave state around for the second one.
But.. well, I guess we could make it work for the default English wordlist. wormhole --get-completions 6- could not try to claim the nameplate, but just assume we're going to use English and return completions against that list. Then we only talk to the server at all on the last invocation, where we're invoked with the complete code.

authors: jtrakk warner

repo: warner/magic-wormhole


text:
Wallet

Where to add or enter or provide our wallet address?It only asks for private keys.Help me out

The private key is unique to your wallet address. So once you provide it, it will be able to read your wallet.
Disclaimer: I would recommend to always be cautious and don't use your main wallet. Just create a new wallet and supply it with a mimimum amount of funds to test with.

Never use your main wallet for bot!!!!
@ImSan286 you can create a new wallet with solana-keygen new --outfile bot-keypair.json
In json file bot-keypair.json, the private key is in array format like [1, 2, 3, ....]
you can use following nodejs script to convert the private key in bot-keypair.json
const fs = require('fs');
const {Keypair} = require('@solana/web3.js');
const bs58 = require('bs58');

// Replace with the path to your keypair.json file
const keypairPath = './bot-keypair.json';

const keypair = Keypair.fromSecretKey(new Uint8Array(JSON.parse(fs.readFileSync(keypairPath, 'utf-8'))));
console.log(bs58.encode(keypair.secretKey));

➜  solana-trading-bot git:(master) ✗ node keyToBase58.js
<private key in base 58 encoding>

having same issue do i type this into command prompt?

Create key.js file and put it in it

not allowed to create a new file in the Solana sniper bot directory. were is the javascript code pointing to. Sorry for all the questions im a newb when it comes to coding.

repo: warp-id/solana-trading-bot

license: MS-PL


text:
关于add_defines和add_defines_if_ok的区别

在option里面使用这个两个命令, 我感觉这两个命令是等效的.
从代码上好像也是等效的? 是在core/tool/compiler.lua的中的_addflags_from_target函数中执行的?
1.如果这两个命令真的是等效的, 是否只保留一个就行了? 同理add_undefines和add_undefines_if_ok也应该是一样的?
2.另外关于add_defines_h_if_ok, 这个命令是在头文件里面定义宏, 然后你在include这个头文件. 那为什么不直接用add_defines定义了, 最后的结果不是一样的吗? 不太明白为什么要生成这个头文件的必要.

稍微有点区别，option如果在不进行检测，仅仅用于手动配置的情况下，这两个效果都是一样的，就是
如果option启用，那么添加宏定义

但是在option用于自动检测的情况下，这两个是有区别的

add_defines：option中所有不带_if_ok的设置，都是在option检测前就设置的，此处用于在检测前添加宏定义
add_defines_if_ok：_if_ok结尾的表示，在option检测通过后，需要添加的配置，此处用于option检测通过后，添加宏定义

例如：
option("pcre2")

    -- 如果检测通过，会在config.h中添加此此宏开关定义
    add_defines_h_if_ok("$(prefix)_PACKAGE_HAVE_PCRE2")

    -- 在检测前预先添加PCRE2_CODE_UNIT_WIDTH=8的宏定义，否则编译检测是通不过的
    -- 检测通过后，也会追加此宏定义
    add_defines("PCRE2_CODE_UNIT_WIDTH=8")

    -- 而此宏定义，只会在检测通过后添加，当然手动配置启用，或者默认启用的时候，也会添加此设置
    add_defines_if_ok("XXXX")

    -- 在检测前，添加libpcre-8.a的链接库，检测的时候会去尝试链接它，链接不通过，选项检测失败
    -- 检测通过后，add_options("pcre2") 到target的时候，也会自动追加此链接
    add_links("pcre2-8")

    -- 检测pcre2/pcre2.h的pcre2_compile接口
    add_cincludes("pcre2/pcre2.h")
    add_cfuncs("pcre2_compile")

总而言之，option里面不带if_ok的add_xxx接口，检测前设置，检测成功后也会设置
而带if_ok的add_xxx接口，仅在检测成功（或者手动启用，默认启用）后被设置
具体可以参考这篇文章：http://tboox.org/cn/2016/08/07/custom-option/
而add_defines_h_if_ok用于在config.h中添加宏定义，一般用于代码中进行条件编译使用
具体config.h的设置，见set_config_h

明白了, 感谢!

repo: waruqi/xmake


text:
TagSphereView

Could you add this library to the main list?
Thanks

@magic-goop Cool!

authors: magic-goop wasabeef

repo: wasabeef/awesome-android-ui


text:
Does wasmer-go support importing memory into the wasm module

Summary
I don't see any examples in the docs if wasmer-go supports importing memory from the host environment into the Wasm module? Is it possible and how?
Additional details
For example: The Wasm module (the one below) should be able to use the memory provided by the host and use the host provided functions to manage it.
Type: wasm
Size: 2.5 MB
Imports:
  Functions:
    "env"."ext_allocator_free": [I32] -> []
    "env"."ext_allocator_malloc": [I32] -> [I32]
  Memories:
    "env"."memory": not shared (20 pages..)
  Tables:
  Globals:
Exports:
  Functions:
    "intr_cust_function": [I32, I32] -> [I64]
  Memories:
  Tables:
    "__indirect_function_table": FuncRef (352..352)
  Globals:
    "__data_end": I32 (constant)
    "__heap_base": I32 (constant)

Found what I was looking for.

@radkomih it'd be useful if you posted the solution =P

authors: james-lawrence radkomih

repo: wasmerio/wasmer-go