text:
[BUG] Images downloaded from COCO dataset are from the wrong class

Describe the problem
Hi, I am trying to download a subset of the COCO dataset, specifying only some classes.
Hence, I have tried both the fiftyone.zoo.load_zoo_dataset() and fiftyone.utils.coco.download_coco_dataset_split(), specifying the label_types, and classes argument, respectively. The problem is that images of different class than the one I am requesting are downloaded.
Code to reproduce issue
Here I am asking for bears, but cows are downloaded
import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset(
    "coco-2017",
    split="train",
    label_types=["detections", "segmentations"],
    classes=["bear"],
    only_matching=True,
    max_samples=10,
)

Same here, asking for "stop sign", but hydrants are given:
import fiftyone as fo
import fiftyone.zoo as foz
fo.utils.coco.download_coco_dataset_split(dataset_dir="~/coco-2017", split="train", classes=["stop sign"], max_samples=5)

System information

OS Platform and Distribution Ubuntu 20.04
Python version (python --version): Python 3.8.10
FiftyOne version (fiftyone --version): FiftyOne v0.25.2, Voxel51, Inc.
FiftyOne installed from (pip or source): pip

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently
[x] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community
[ ] No. I cannot contribute a bug fix at this time

Hi @torydebra 👋
This was fixed by https://github.com/voxel51/fiftyone/pull/4884. Upgrading pip install fiftyone>=1.01 should resolve for you ✅

Hi @brimoor, thanks, but unfortunately it seems that the last version for my system is the 0.25.2 :
pip install "fiftyone>=1.01"
ERROR: Could not find a version that satisfies the requirement fiftyone>=1.01 (from versions: 0.1.0, 0.1.0.1, 0.1.2, 0.1.3, 0.2.0rc1, 0.2.0, 0.2.1, 0.3.0, 0.4.0, 0.4.1, 0.5.0, 0.5.1, 0.5.2, 0.5.2.1, 0.5.3, 0.5.3.1, 0.5.4, 0.5.5, 0.5.5.1, 0.5.6, 0.6.0, 0.6.0.1, 0.6.1, 0.6.1.1, 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.6.5.1, 0.6.5.2, 0.6.6, 0.7.0, 0.7.0.1, 0.7.1, 0.7.1.1, 0.7.1.2, 0.7.1.3, 0.7.1.4, 0.7.2, 0.7.3, 0.7.3.1, 0.7.3.2, 0.7.3.3, 0.7.3.4, 0.7.4, 0.8.0, 0.8.0.1, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.10.0, 0.11.0, 0.11.1, 0.11.2, 0.11.2.1, 0.12.0, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.14.0, 0.14.1, 0.14.2, 0.14.3, 0.14.4, 0.15.0, 0.15.0.1, 0.15.0.2, 0.15.1, 0.16.0, 0.16.1, 0.16.2, 0.16.3, 0.16.4, 0.16.5, 0.16.6, 0.17.0, 0.17.1, 0.17.2, 0.18.0rc0, 0.18.0, 0.18.1rc0, 0.18.1rc1, 0.18.1rc2, 0.18.1rc3, 0.18.1rc4, 0.18.1rc5, 0.18.1rc6, 0.18.1rc7, 0.18.1rc8, 0.18.1rc9, 0.18.1rc10, 0.18.1rc11, 0.18.1rc12, 0.18.1rc13, 0.18.1rc14, 0.18.1rc15, 0.18.1rc16, 0.18.1rc17, 0.18.1rc18, 0.18.1rc19, 0.18.1rc20, 0.18.1rc21, 0.18.1rc22, 0.18.1rc23, 0.18.1rc24, 0.18.1rc25, 0.18.1rc26, 0.19.0, 0.19.1rc0, 0.19.1rc1, 0.19.1, 0.20.0, 0.20.1rc1, 0.20.1rc2, 0.20.1rc3, 0.20.1, 0.21.0, 0.21.1, 0.21.2, 0.21.3, 0.21.4, 0.21.5, 0.21.6, 0.22.0, 0.22.1, 0.22.2, 0.22.3, 0.23.0rc1, 0.23.0rc2, 0.23.0, 0.23.1, 0.23.2, 0.23.3rc1, 0.23.3, 0.23.4, 0.23.5, 0.23.6, 0.23.7, 0.23.8, 0.24.0, 0.24.1, 0.25.0, 0.25.1, 0.25.2)

In fiftyone>=1.0 we dropped support for Python 3.8 as it has reached end of life. I bet that's the reason.
Hopefully you can upgrade to Python >=3.9 as FiftyOne has enjoyed some big upgrades since v0.25.2!

authors: brimoor torydebra


text:
4.x version. Initialization of replset and user creation problem.

Puppet: 5.5.19
puppet-mongodb module version: v3.1.0
MongoDB: 4.0.x and 4.2.x

I'm using puppet-mongodb module directly from https://github.com/voxpupuli/puppet-mongodb
:git => 'https://github.com/voxpupuli/puppet-mongodb.git'
:tag => 'v3.1.0'
What are you seeing
When I use MongoDB 3.x (3.4, 3.6) everything is OK. During installation of node I get just one warning:
Warning: Host is available, but you are unauthorized because of authentication is enabled: true
but everything is OK. Puppet successfully completes initialization of replset (primary) and all necessary users have been created:
[root@myhost.example.com ~]# mongo
MongoDB shell version v3.6.17
connecting to: mongodb://127.0.0.1:27017/?gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("1d48b06f-1b16-4235-92a9-4c36ff9c1844") }
MongoDB server version: 3.6.17
mon-rep:PRIMARY>
Great!
So, when I'm trying to do the same with MongoDB 4.x versions (my hiera configuration of puppet is totally the same in all cases) the result is negative:
MongoDB shell version v4.2.6
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("0b21d660-4eca-4e13-a9ea-79c9ff33476d") }
MongoDB server version: 4.2.6
Error: Authentication failed.

So,  initialization of replset (primary), authentication, and creation of users failed. So, MongoDB isn't prepared to use.
What behaviour did you expect instead
It would be great to get the same result with 4.x in preparation of MongoDB as I have with 3.x versions.
Thanks.

Does the anyone use this module with MongoDB 4.2 version? Is it everything is OK?

Using this mod via Satellite 6.7 and MongoDB 4.2
Initialize a replset with auth enabled fails.

Can someone fir the issue. It's impossible to use the module with mongo 4.x enabling auth and replica set.

Don't even need a replset. Can't setup admin user, database and database user here with auth enabled.

We have the same issue, but we found an kind-of acceptable workaround in comparison to what would have to change in the module.
Within a wrapper module we check it like so:
  if $facts['mongodb_is_master'] == 'not_installed' {
    $cluster_args = {}
  } else {
    create_resources('mongodb::db', $databases)

    $cluster_args = {
     # your actualy config goes here
    }
  }

i don't understand what the values of $facts['mongodb_is_master'] can be
given the name, you'd think the value should be Boolean

Another dirty workaround during the first deployment run with 4.2:

fact the primary in the mongo host array and ensure that there is no lock file
stop the mongod
start the mongod without authentication in a subshell
create the admin user with db.createUser()
kill the mongod process
create lock file
trigger new puppet apply

source: gharchive/issue

authors: DENISKI bimcas dhs-rec epopoee igalic makmarius tsgoff

repo: voxpupuli/puppet-mongodb

license_type: permissive

license_source: github-api


text:
Add Ubuntu 24.04 support

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Hello,
I just tried this WA and seems ok with Ubuntu 24 as it is a noble familly: https://github.com/exo-puppet/puppet-nfs-wa/commit/f65e3775918214b6423277ad106ca49e0ef85624#diff-e78db79abb0b543310767fb9d2814cc4e2408f613de4985186251c70bdd4edbbL119
I am interested of your PR as it seems more global

Would be nice to have!

source: gharchive/pull-request

authors: bastelfreak bourasom mwinkens

repo: voxpupuli/puppet-nfs


text:
Fix uk local

It also seems better. Add missed keys

@al0mie, thank you. I'll make a release.

repo: vsch/laravel-translation-manager

license: mit

license_source: bigquery


text:
[End of line] - mouse selection skip last character (edge case)

I have the same bug with both neovim and vim: issue from vscodevim
Describe the bug
When in vim 'Normal' mode, if the cursor is on the last character of a line, selecting with with a mouse omits the last character (the one before the newline).
To Reproduce
Steps to reproduce the behavior:

Enter 'Normal' mode
Navigate to last character of a line of text
Select that line with the mouse
Last character (before the newline) will not be in the selection

Screenshots

I have stumbled across this a few times too. A workaround (very cumbersome though) is to double click next to the line.

I have stumbled across this a few times too. A workaround (very cumbersome though) is to double click next to the line.

For me I need to triple click next to the line and even then it doesn't select the first character.

Seems to be fixed now.

This is still an issue for me

I have the same issue (it's driving me insane)

Two ways:

Click twice on the end position.

:set ve=onemore
Highly recommended. This option will also resolve other cursor issues, such as "cursorMove with wrappedLines".

@xiyaowong thanks, but I found the actual bug: Disabling frame-indent-rainbow.  fixed it. This is a known issue.
I'm now using indent-rainbow and it works fine.

These two issues are not related

I'm still seeing this issue in May 2024 with VSCode 1.89.1, VSCode Neovim released 2024-05-21, 04:51:37, and NVIM v0.9.5.

repo: vscode-neovim/vscode-neovim

license: MIT


text:
chore: Only build commonly used binaries

The default configuration of goreleaser builds windows and 32-bit variants of the binary.
Checklist

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog

With this file the build flags are set in three places:

Makefile
Github pipelines
goreleaser config

That's pretty terrible. This stuff should be in one place, not 3. I don't like this but I also have no solutions other than throwing out goreleaser.

We could get rid of goreleaser and only publish the Container Images, that would make things much easier.

authors: davidgubler mhutter


text:
BrokenPipeError

python3 - Function blynk.virtual_write() irregularly ends with Broken Pipe Error. I have no ide how to fix or prevent it.

I would be interested to know how your comment about “the easy coding” helps to solve the problem. Node Red is unintuitive that I refuse to try it.

May I ask you why?
Have you ever tried Node-RED?

I have, I am not comfortable with using  it.
This is the code. The broken pipe error usually occures on the line with red dot.

Does it work properly if you comment that line out?

What have you done to troubleshoot it?
Just print the data you want to send and see if it’s correct. If it is, send some bogus data to Blynk. In other words, try to pin point the problem.

authors: John93-Blynk ebolisa kristonela kristonelka

repo: vshymanskyy/blynk-library-python


text:
Added Gitignore Templates Under Other Xcode Section

Project URL

Description

Checklist

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

          1 Warning

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

  Generated by :no_entry_sign: danger

@aashishtamsya  please, squash this commits. Or if you feel more confortable you can close this PR and send a new with only  one commit.
Thank you.

New entry should go to the bottom

Okay I will do the same next time

Added the one repo per push in chronological order (bottom of category)

authors: aashishtamsya danger-awesome-ios dkhamsing vsouza

repo: vsouza/awesome-ios


text:
Add FileExplorer

Project URL
https://github.com/Augustyniak/FileExplorer
Description
Add information about FileExplorer control
Checklist

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

          1 Error

:no_entry_sign:
Found 1 link issue

Link issue by awesome_bot

Line
Status
Link

2256
301
http://www.ioscreator.com/ redirects tohttps://www.ioscreator.com/

  Generated by :no_entry_sign: danger

Thank you for contributing to awesome-ios 😄


text:
Add FAQView

Project URL
https://github.com/mukeshthawani/faqview
Description
An easy to use FAQ view for iOS written in Swift.
Why it should be included to awesome-ios (optional)
Checklist

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

Thank you for contributing to awesome-ios 😄

authors: dkhamsing mukeshthawani


text:
Removed PJAlertView

No activity in the past 2 years

          1 Warning

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

Link issues by awesome_bot

Line
Status
Link

313
Error
http://oclint.org/  getaddrinfo: Name or service not known

2446
Error
https://iconresizer.com/  Connection refused - connect(2) for "iconresizer.com" port 443

  Generated by :no_entry_sign: Danger

authors: danger-awesome-ios lfarah


text:
Minimap Overlaps diagram

Expected behaviour
The minimap is restricted to a small space
graph LR
   subgraph a
      A --> B
      B --> C
      A --> C
   end
   D --> A
   A --> B
   B --> A
   A --> D
   D --> A

Actual behaviour
Minimap creeps into the actual diagram space
Include:

Preview mode: Mermaid
Theme used: dark
I know a similar issue is already fixed in https://github.com/vstirbu/vscode-mermaid-preview/issues/66
Can you please add an option to turn off minimap during preview

I have a similar issue. Can I turn the minimap off completely?

The minimap visibility is controlled via mermaid.vscode.minimap configuration.

true for visible
false for hidden

authors: minemax-ua sebinjohn vstirbu

repo: vstirbu/vscode-mermaid-preview


text:
Добавление ещё одного джойстика на Pro Micro

Можно ли убрать линию PL(как указано в документации), перекинуть пины для управления драйвером на 3 и 5 цифровые пины(у них есть PWM) и докинуть ещё 1 джойстик на пины A9 A10(9 и 10 пины аналоговые)?

Нет. Во первых, пины управления драйвером нельзя так просто поменять, там управление не через analogWrite, а через таймер 1, у которого выходы на пины 9-10.
Во вторых, у контроллера все равно может быть не больше 8 осей (больше Windows не увидит).

authors: alivergg vsulako

repo: vsulako/AFFBWheel


text:
Application Crashes on Missing Pages Instead of Displaying 404 Error - Regression

Describe the bug
When the page is not found, the application breaks instead of displaying the 404 page.
Happening also: https://starter.vtex.app/test-page-no-found
Expected behavior
Show 404 page

Current behavior

Thank you for reporting this!
We've just rolled back some changes that had caused this issue, it now seems to be working as expected

repo: vtex/faststore


text:
integrate with Lightning ecosystem CI

Hello and so happy to see you use Pytorch-Lightning! :tada:
Just wondering if you already heard about quite the new Pytorch Lightning (PL) ecosystem CI where we would like to invite you to... You can check out our blog post about it: Stay Ahead of Breaking Changes with the New Lightning Ecosystem CI :zap:
As you use PL framework for your cool project, we would like to enhance your experience and offer you safe updates to our future releases. At this moment, you run tests with a particular PL version, but it may accidentally happen that the next version will be incompatible with your project... :confused: We do not intend to change anything on our project side, but still here we have a solution - ecosystem CI with testing both - your and our latest development head we can find it very early and prevent releasing eventually bad version... :+1:
What is needed to do?

have some tests, including PL integration
add config to ecosystem CI - https://github.com/PyTorchLightning/ecosystem-ci

What will you get?

scheduled nightly testing configured for development/stable versions
slack notification if something went wrong to investigate
testing also on multi-GPU machine as our gift to you :rabbit:

in fact I already started this integration for you so if you could have look https://github.com/PyTorchLightning/ecosystem-ci/pull/27

Hi @Borda. Thank you for including us :) I'll take a look at the ecosystem.
What should we add to the PR?

Hi @Borda. Thank you for including us :) I'll take a look at the ecosystem.

@vturrisi you are very welcome!

What should we add to the PR?

if you could check it and:

approve if it looks good to you
if you are on PL slack provide your user name so I can add you as the contact person for notifications

also, I was checking the compatibility for the latest master, and seems that one of your tests is not expecting loops in checkpoint so if you mind consider updating this test so we would be aligned also with the latest development state...
https://github.com/PyTorchLightning/ecosystem-ci/runs/4934800624?check_suite_focus=true

Hi @Borda, there's a typo in the file name (solo-learn_pl-devlop.yaml -> solo-learn_pl-develop.yaml). Apart from that, my email is vt.turrisi@gmail.com, if you could add it. I'm not part of the slack channel, but I would be happy to join (also think @DonkeyShot21 would like to join as well).
I've just fixed the tests, it should now allow new keys to be there. Let me know if it worked. Also, we would like to integrate dali tests, but those are a bit more work, as installing it with our setup is not working sometimes.
Currently, our tests are not actually training the model itself so they are a bit limited in that regard. Eventually, we would want to run a couple of epochs for each method/dataset and catch potential errors (e.g. loss not going down and so on). Would this be possible?

I've just fixed the tests, it should now allow new keys to be there. Let me know if it worked.

just re-running the tests :rabbit:

Also, we would like to integrate dali tests, but those are a bit more work, as installing it with our setup is not working sometimes.

that would be cool... we can make this addition in follow-up PR (well if you add it to your codebase it will be run automatically, we may just add/build the DALI, btw, DALI makes sense only test on GPU, right?)

Currently, our tests are not actually training the model itself so they are a bit limited in that regard. Eventually, we would want to run a couple of epochs for each method/dataset and catch potential errors (e.g. loss not going down and so on). Would this be possible?

that sounds reasonable, for that we should rather use the GPU machine as it is more powerful so the short training would not take too much time :+1:

that would be cool... we can make this addition in follow-up PR (well if you add it to your codebase it will be run automatically, we may just add/build the DALI, btw, DALI makes sense only test on GPU, right?)

Yes, DALI only works for GPU (it works on CPU but has bad performance). We already have tests for dali in tests/dali and those work, it's just the installation that might not work straight from solo (I would say it's better if we can build from dali directly).

that sounds reasonable, for that, we should rather use the GPU machine as it is more powerful so the short training would not take too much time

Agreed. I can start to develop some new tests which directly call the bash scripts with a very small number of epochs and then we can decide on that. Does it sound good to you?

authors: Borda vturrisi

repo: vturrisi/solo-learn


text:
Webpack configuration

Hi,
I am using webpack 2. What is the configuration you recommend for the library?
Dick Chan

The config file of vue-admin may help.

authors: dickhfchan luventa

repo: vue-bulma/canvas-gauges


text:
Closing a dynamic modal throws error: enableBodyScroll unsuccessful

In the browser console, closing a dynamic modal always throws the error:
enableBodyScroll unsuccessful - targetElement must be provided when calling enableBodyScroll on IOS device
Environment:
Vue3 - globally registered vue-final-modal so calling this.$vfm.show works everywhere
Chrome
The dynamic modal component (MyDialog) is just a vanilla component with just HTML in the template text:
<template>

HELO WERLD

</template>

The modal is opened with:
this.$vfm.show({component:MyDialog})
Closing is done by clicking on the coverall background.

+1

+2

I get the same error when I close the modal window and go to another route (the view in which the modal window was destroyed).
If I add a delay of 300 ms before the transition, there is no error.

+1

+1

@Iviyan
$vfm.hideAll() returns a promise, if you wait for the promise to resolve before switching routes you won't get this error.

authors: AnatoliiDev Iviyan Shade465 jairoblatt jifka nmarsh92 pommedepain

repo: vue-final/vue-final-modal


text:
[Question] How to pass any attribute to the component

How can I pass any attribute to the component? Maybe something is wrong with my typescript configuratin, but I can't pass anything other then props that are provided by the component and a few common attributes like "style" as "key".

For example, if I try to pass the "src" value to a component, typescript gives the following error:
Type '{ class: string; src: string; }' is not assignable to type 'IntrinsicAttributes & { as?: AsTag | undefined; class?: unknown; readonly asChild?: boolean | undefined; key?: string | number | symbol | undefined; ref?: VNodeRef | undefined; ... 8 more ...; style?: unknown; }'.
  Property 'src' does not exist on type 'IntrinsicAttributes & { as?: AsTag | undefined; class?: unknown; readonly asChild?: boolean | undefined; key?: string | number | symbol | undefined; ref?: VNodeRef | undefined; ... 8 more

When I use sfc template I can pass anything to the component, but with jsx I can't do that.
Here is my tsconfig.
{
	"compilerOptions": {
		"target": "ES2020",
		"useDefineForClassFields": true,
		"module": "ESNext",
		"lib": ["ES2020", "DOM", "DOM.Iterable"],
		"skipLibCheck": true,

		/* Bundler mode */
		"moduleResolution": "bundler",
		"allowImportingTsExtensions": true,
		"resolveJsonModule": true,
		"isolatedModules": true,
		"noEmit": true,
		"jsx": "preserve",
		"jsxImportSource": "vue",

		/* Linting */
		"strict": true,
		"noUnusedLocals": true,
		"noUnusedParameters": true,
		"noImplicitReturns": true,
		"noFallthroughCasesInSwitch": true,
		"noUncheckedIndexedAccess": true,
		"allowUnreachableCode": false,
		"noImplicitThis": true,
		"forceConsistentCasingInFileNames": true,
		"noImplicitAny": true,
		"paths": {
			"#/*": ["./src/*"],
			"#generated/*": ["./generated/*"]
		}
	},
	"include": [
		"src/**/*.ts",
		"src/**/*.d.ts",
		"src/**/*.tsx",
		"src/**/*.vue",
		"generated/**/*.ts",
		"generated/**/*.d.ts"
	],
	"references": [{ "path": "./tsconfig.node.json" }]
}

Would appreciate any help 😄!

@MellKam
Code example to pass attrs to component:
https://github.com/funny-family/vue3-ts-playground/blob/master/src/app/shared/components/text-field/text-field.component.ts#L24
https://github.com/funny-family/vue3-ts-playground/blob/master/src/app/components/not-found/not-found.component.tsx#L190

authors: MellKam funny-family

repo: vuejs/babel-plugin-jsx


text:
Visual Studio Code - vue.volar extension - JS/TS language service cannot be started successfully

When loading/opening a non-Vue project (e.g. NextJS [React]) with the Visual Studio Code vue.volar extension installed (v2.0.10+) I get the following error message:

Downgrading vue.volar to v2.0.6 or disabling the extension altogether fixes this issue. Loading a Vue project (e.g. Nuxt) does not experience this issue.

Still an issue in v2.0.14
This problem is really effecting DX... no type completion and refactoring of types is really bad. Productivity down 80%.

Closing this one as many things have changed in the latest 2.x versions. Feel free to create a new issue with a minimal reproduction if you're still having issues, thanks!

authors: abarke davidmatter nico-sth

repo: vuejs/language-tools


text:
Bug:  ReferenceError: Vue is not defined

Bug Detail
I am writting test cases using vue3 version ^3.3.4 but  its throwing error on run test
ReferenceError: Vue is not defined in Object.<anonymous> (node_modules/@vue/test-utils/dist/vue-test-utils.browser.js:8418:8)
import { shallowMount } from "@vue/test-utils";
case code
 const wrapper = shallowMount(Mycomponent);
Related information:
vue: 3.3.4,
vue/utils : 2.4.3
vue/vue3-jest

Can you provide us a small repro online using https://stackblitz.com/github/vuejs/create-vue-templates/tree/main/typescript-vitest?file=src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts ?
It only takes a few minutes, and we'll be able to take a look

I resolved the problem, thank you for your immediate response.

@Suryadeep-bhujel Can you please specify how you solved this issue ?

I resolved the problem, thank you for your immediate response.

Can you please specify how you solved this issue? thank you

authors: Suryadeep-bhujel cexbrayat fullMooth shubhangchourasia

repo: vuejs/test-utils


text:
Don't include babel by default

What problem does this feature solve?
Babel adds additional comprehension overhead in entering the modern web app ecosystem (more libraries, more plugins to learn about and understand) as well as potential adding performance hits when transpiling code that isn't standardised. While it has some benefits (supporting older browsers) I don't think we should assume that everyone will use it.
What does the proposed API look like?
I think the only difference is that the create workflow should have an extra step for including babel and the vue preset; the complexity lies in other parts of vue-cli potentially relying on babels presence.

I think it should be included by default because I'd say probably more than half of the users need it. But yeah we should have a way to opt-out.

True, I should've thought that through in a more utilitarian way. As you said, an opt-out would be good.

repo: vuejs/vue-cli


text:
cache of cache-loader causes problems with worker-loader

Version
3.0.0-rc.5
Node and OS info
node: 8.11.1, npm: 6.1.0, OS: Debian 9
Steps to reproduce
I am using webpack worker-loader for web-workers. My vue.config looks like this
module.exports = {
  parallel: false,
  baseUrl: '/',
  configureWebpack: {
    /**
     * Setting the global object is necessary to make the loading of web-workers work. Otherwise, window is referenced
     * in the produced bundle, which is not accessable from a worker context. This seems to be a webpack 4 bug
     * https://github.com/webpack/webpack/issues/6642
     * https://github.com/webpack/webpack/issues/6629
     */
    output: {
      globalObject: 'self',
    },
    module: {
      rules: [
        {
          test: /\.worker\.js$/,
          use: [{ loader: 'worker-loader' }, { loader: 'babel-loader' }],
        },
        {
          test: /\.worker\.ts$/,
          use: [{ loader: 'worker-loader' }, { loader: 'babel-loader' }, { loader: 'ts-loader' }],
        },
      ],
    },
  },
}

What is expected?
Worker-loader should generate bundle files ([hash].worker.js) which should be loaded on request.
What is actually happening?
When /node_modules/.cache is emptied everything works as expected.
If webpack-dev-server is started again via vue-cli-service serve The server doesn't seem to have the requested worker script and serves index.html instead.
This is probably the intended behaviour by historyApiFallback of webpack-dev-server.

Is there any possibility to turn of caching as a temporary workaround?

I'm not sure how this relates to cache-loader since you don't even use it in your config, and since your didn't provide a reproduction (which we generally ask you to provide), I can't say what'S going on, I have nothing to look at.

Note with rules added like this, both your loaders AND the internal loaders configured for *.js will be applied to *.worker.js files. You may want to use chainWebpack to add *.worker.js files to the exclude list of the built-in js rule:
chainWebpack: config => {
  config.module.rule('js').exclude.add(/\.worker\.js$/)
}

Thanks a lot @yyx990803. Excluding worker files from default loaders solved my problem.

@Janekdererste Can you give me a code example?

Hi @tangxiaolang101, yes I can. What parts are you particularly interested in?

@yyx990803 Thank you sir! You just saved me from hours of headache :)

find a more concise way to config worker-loader, do not need add configureWebpack in vue.config.js, just add:
chainWebpack: config => {
  config.module.rule('webWorker').post().test(/\.worker\.(j|t)s$/).use('worker-loader').loader('worker-loader');
}

authors: Janekdererste LinusBorg andersrehn qidaneix tangxiaolang101 yyx990803


text:
如何导入自定义的Index.html

Version
3.6.3
Environment info

Environment Info:

  System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
  Binaries:
    Node: 8.10.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.6.0 - C:\Users\123456\AppData\Roaming\npm\yarn.CMD
    npm: 6.8.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 42.17134.1.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0-beta.3
    @vue/babel-plugin-transform-vue-jsx:  1.0.0-beta.3
    @vue/babel-preset-app:  3.6.0
    @vue/babel-preset-jsx:  1.0.0-beta.3
    @vue/babel-sugar-functional-vue:  1.0.0-beta.3
    @vue/babel-sugar-inject-h:  1.0.0-beta.3
    @vue/babel-sugar-v-model:  1.0.0-beta.3
    @vue/babel-sugar-v-on:  1.0.0-beta.3
    @vue/cli-overlay:  3.6.0
    @vue/cli-plugin-babel: ^3.6.0 => 3.6.0
    @vue/cli-service: ^3.6.0 => 3.6.0
    @vue/cli-shared-utils:  3.6.0
    @vue/component-compiler-utils:  2.6.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    @xkeshi/vue-qrcode: ^1.0.0 => 1.0.0
    babel-helper-vue-jsx-merge-props:  2.0.3
    emoji-mart-vue: ^2.6.6 => 2.6.6
    vue: ^2.6.10 => 2.6.10
    vue-amap: ^0.5.4 => 0.5.9
    vue-cookie: ^1.1.4 => 1.1.4
    vue-echarts: 3.0.7 => 3.0.7
    vue-hot-reload-api:  2.3.3
    vue-loader:  15.7.0
    vue-router: ^3.0.3 => 3.0.6
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.5.21 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vuedraggable: ^2.16.0 => 2.20.0
    vuex: ^3.0.1 => 3.1.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
随便找个webpack3.0时期的项目，根目录下会有index.html文件，打包时会使用到。但是cli3.0未使用。
What is expected?
使用根目录的index.html进行构建，该html内有加载动画及其他js文件。
What is actually happening?
未使用根目录的html进行构建

vue.config.js如何配置才能使用？

感谢关注，但是我们的 GitHub issues 只用于 Bug 反馈和特性请求，如果有使用上的问题建议到官方论坛、Discord、StackOverflow 或其他问答网站上提问。

现在放在 public/index.html

authors: DougFlands sodatea


text:
Map display improvements (length, pagination)

What problem does this feature solve?

Number of elements in the Map
Hide Map Default. I use Map to store large data. When I open DevTools everything hangs. Since DevTools renders all the Map items. I think the same behavior as the array will be just right

What does the proposed API look like?

I can pick this enhancement.

authors: axp-dev rajzshkr

repo: vuejs/vue-devtools


text:
sfc-playground does not support vue-class-component syntax

What problem does this feature solve?
It would provide the support in SFC playground of the vue-class-component syntax like this:
<template>

{{ greeting }} World!

    <Comp ref="comp" />

</template>

Currently, I am facing an issue only with this syntax but I can't create a reproducer in SFC playground
What does the proposed API look like?
Provide an import of the vue-class-component module in the import map or document the URL somewhere if it already exists so that we can have in the import map something like:
{
  "imports": {
    "vue": "https://sfc.vuejs.org/vue.runtime.esm-browser.js"
    "vue-class-component": "https://sfc.vuejs.org/vue-class-component.runtime.esm-browser.js"
  }
}

The playground uses sucrase for transpiling TS in browser, which does not support decorators.

Vue class component is no longer recommended, so the playground has no plan in supporting it.

repo: vuejs/vue-next


text:
Warn about root paths without a leading slash (fix #2550)

close #2550

This PR creates the following warning message when a root route exists without a leading slash:

This facilitates the debugging process as the current behavior does not generate any warnings or errors.

@posva Are you referring to the addRoutes function defined used by the matcher? If so, I believe that this function already calls createRouteMap which would trigger the warning message.

repo: vuejs/vue-router


text:
test  mapState failed.

Version
1.0.0-beta.29
Reproduction link
https://codepen.io/tolerious/pen/PowEEOO
Steps to reproduce
npm run test:unit
What is expected?
success
What is actually happening?
failed.
can not read 'submitLocationTotal' in  mapState.

Shouldn't it be
beforeEach(() => {
        store = new Vuex.Store({
            state: {
                claim: { submitLocationTotal: 123 }
            },
        })
    })

You forgot the claim field. I'm fairly sure this should work fine. The repro link is also not working; can you provide one that shows the error?

Shouldn't it be
beforeEach(() => {
        store = new Vuex.Store({
            state: {
                claim: { submitLocationTotal: 123 }
            },
        })
    })

You forgot the claim field. I'm fairly sure this should work fine. The repro link is also not working; can you provide one that shows the error?

Yeah, that's right , thank U ~

@lmiller1990  another question， if I use a third  part component library like vue-antdesign in my own component, how can I test my own component?

Same way you test any other component. If you have more questions, the best place to ask is https://vue.land/ in the #testing channel.

@tolerious like project's index.js file for example Vue.use(BootstrapVue), you should also put this line in jest setup file. it works for me

authors: alibalbars lmiller1990 tolerious

repo: vuejs/vue-test-utils


text:
Behavior of find and findAll

Should find and findAll return all nodes including the root node, or excluding the root node
Including root node:
const compiled = compileToFunctions('

')
const wrapper = mount(compiled).findAll('div').length // 2

excluding root node:
const compiled = compileToFunctions('

')
const wrapper = mount(compiled).findAll('div').length // 1

I think it should exclude the root node, but would be interested to hear others thoughts

First glance, would expect it to include the root node (count of 2).  What are thoughts for reason to exclude?

querySelector and querySelectorAll exclude the root node

I think including the root node would make sense, because .find() and .findAll are not called on the root node but the "wrapper"

Although methods are called on the wrapper, they refer to the root node:
const compiled = compileToFunctions('
')
const wrapper = mount(compiled)

wrapper.is('div') // returns true
wrapper.hasClass('class') // returns true
wrapper.hasAttribute('id', 'id') // returns true

Hmm, I still find inclusive match more intuitive, since the root node is also part of the template.

I think this depends on whether your headspace considers the method being called on the 'wrapper' or the node itself.
Are there other places where the user would think of the wrapper object as a node? Or is it typically treated as a wrapper that contains the node?

As @pearofducks says, this is a case of how we conceive of a wrapper.
I think we should treat it as a node, and not as containing a node. In my eyes, almost all methods treat the wrapper as a node:
wrapper.is('div') // checks node matches selector
wrapper.isEmpty() // checks node is empty
wrapper.hasAttribute('id', 'id') // checks node attribute
wrapper.trigger('click') // calls on the node

I can't imagine a use case where omitting the root node would be useful. But it seems strange to me to return the same div each time you call find:
wrapper.find('div').find('div').find('div') // would return the same div

Especially since we the find methods are so similar to querySelector and querySelectorAll
I think this would confuse users:
const compiled = compileToFunctions('

')
const rootDiv = wrapper.find('div')
rootDiv.findAll('div').length // 2

Maybe the answer is to include the root node when called on a vm wrapper, and exclude it when called on a DOM node wrapper.

Maybe the answer is to include the root node when called on a vm wrapper, and exclude it when called on a DOM node wrapper.

I agree, here is what i would expect while using find/findAll.
const compiled = compileToFunctions('

')

wrapper.findAll('div').length // would expect 2

const rootDiv = wrapper.find('#foo')
rootDiv.findAll('div').length // Would expect 1

Something else to consider is have a separate method so that we don't have to context switch.
find
findAll
findChildren

@Austio I don't think we should add an extra find method. Two is enough.
I thought about it this weekend and I agree with @yyx990803 . We should include the root node, in every find and findAll call.

+1 to including the root node: if the root node is returned and the user wasn't expecting it to, it's clear what happened and easy to work around, while it's less obvious the other way round.

Another vote for including the root node - as per @callumacrae's comment it's the least surprising thing to do. Anything else is getting a bit magical and will result in many GitHub issues being opened... 😬
While @eddyerburgh's chained find() example is at first a little confusing, it will be easy for a user to work it out for themselves.

I'm closing this again. We'll keep the behavior as it is

Thanks for closing.
FWIW I ended up changing my tests so I didn't need this - It felt too much like testing Vue's functionality to be worth the change.

authors: Austio callumacrae eddyerburgh pearofducks rowanu yyx990803


text:
fix: keep the overrides prototype information of component

add the component prototype override scenario and remove the version condition.
@eddyerburgh Actually I don't know why we need add a version condition here: https://github.com/vuejs/vue-test-utils/pull/709/commits/cacfda8acb2dfed54295b82fbd93e84205cec9d3 , any special reason?

Yes, it's due to a bug where extended options aren't resolved correctly (https://github.com/vuejs/vue/issues/4976)
It was fixed in Vue 2.3

This change is actually problematic.
We have an issue with components that already been extended (with Vue.extend). They never extend from the localVue class when they are instantiated, so they don't inherit assets like components set in stubs, and properties set in mocks.
The original code removed by this PR extended all components, including class components, EXCEPT in Vue < 2.3, where components extended with Vue.extend did not merge props correctly.
I would like to revert this PR, because it stops us from being able to add assets to the component without mutating it. But I can see that the previous code was causing you issues in your tests.
Can you give me some details about why your tests don't work when the component is extended?

@eddyerburgh Sure.
As we had overridden the prototype of extended component in my test, for some hijack requirements, when vue >= 2.3 in original code the process would go to _Vue.extend(component).extend(instanceOptions).
From the implementation of Vue.extend:
Vue.extend = function (extendOptions: Object): Function {
    extendOptions = extendOptions || {}
    const Super = this
    ...
    Sub.prototype = Object.create(Super.prototype)
    ...

We can see that if we call _Vue.extend(component), the Super will represent Vue  and Sub.prototype will extend from Vue.prototype rather than component.prototype, then the component prototype which we had overridden would be lost.

I would like to revert this PR, because it stops us from being able to add assets to the component without mutating it.
Shall we add some unit test to explain and guarantee this scenario?

Shall we add some unit test to explain and guarantee this scenario?

Yes definitely, I made a mistake by merging this PR because no tests were failing.
I'd also like to make sure your use case works as expected, but I can't see an easy solution.

uh... Could you show some code to explain what u wanna achive? Actually I don't really know yet😂

const Constructor = vueVersion < 2.3 && typeof component === 'function
? component.extend(instanceOptions)
: _Vue.extend(component)
```

it.only('adds variables to extended components', () => {
  const TestComponent = Vue.extend({
    template: `
      <div>
        {{$route.path}}
      </div>
    `
  })
  const $route = { path: 'http://test.com' }
  const wrapper = mountingMethod(TestComponent, {
    mocks: {
      $route
    }
  })
  const HTML =
    mountingMethod.name === 'renderToString' ? wrapper : wrapper.html()
  expect(HTML).contains('http://test.com')
})

authors: eddyerburgh kuitos


text:
vue-validator inside v-if/s-show - working first time only

Hi,
It is really strange. I am trying to create fiddle and it is giving similar results with point 2. I can't reproduce point 1 so far.
https://jsfiddle.net/mariaczi/ca6vc6oo/2/
There is 2 issues.
1.
I have a div with EDIT FORM. It has v-if="elementInEdit".
There is only one validator for standard text field - required.
When I first time open it - it is working. Next time when conditions will change and it will be gone and show up again - $validator is not existing anymore.
2. $validator is not available outside

I have a div with EDIT FORM. It has v-if="elementInEdit".
There is only one validator for standard text field - required.
When I first time open it - it is working. Next time when conditions will change and it will be gone and
Fixed.

$validator is not available outside

In currently, when we disabled validator with v-if, and enable, it does not work at outside validator because limited of 2.x architecture.
I'll try to improve this issue for 3.x (Vue 2.0 compatible)

any news on this?

released v3.0.0-alpha.1
https://github.com/vuejs/vue-validator/releases/tag/v3.0.0-alpha.1

Could you include the bugfix in v2, too? v3 is alpha and not usable in production.

authors: TinoGroteloh Tinoooo kazupon mariaczi

repo: vuejs/vue-validator


text:
Is there a way to initialize validation without propVal ?

I want to initialize the validation after click the submit button...how can i do ?
maybe i need a 'wait-for-all' attribute on every model to disabled all the model's validation, and initialize the validation after click submit button or text something in one of the models.

Hi @ablipan !!
Currently, vue-validator can't initialize at your own will.
I'm going to support at next version. :)

authors: ablipan kazupon


text:
How to update nested array

Vue.js version
1.0.26
Reproduction Link

Steps to reproduce
What is Expected?
What is actually happening?
I have some data like this
gist
Now I want to set the 'open' property of each item to control the dom show or hide. But Vue can only detect change of 'Root' node, other nodes like 'level 1-1' won't update dom.
I also tried use tree.children.$set() method, but nothing happend.

Hello ..
Thank your for your interest in this project.
However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests.
We encourage you to ask it on the forum  or on gitter.

authors: LinusBorg languanghao

repo: vuejs/vue


text:
Filter image src binding

Is it possible to filter the image source when data binding? I realise I could just make a computed property, but I feel like I'm missing a trick.
<img :src="src | dpi" />

https://vuejs.org/v2/guide/syntax.html#Filters
Maybe you can de this, maybe ugly but useful:
<img :src="$options.filters.dpi(src)" />

Of course, they will tell you that it is not an issue and you should ask this question in Gitter or forum.😂

Thanks @daryl ,  you could use computed property or the way as @JounQin mentioned for now.  It's still under discussion whether to bring the pipe syntax back to attribute or not.

authors: JounQin daryl defcc


text:
Cross Browser Issue on Vue API Docs Sidebar

When viewing the Vue 2.0 API docs on Safari the sidebar does not seem to render. It works on chrome however.
Chrome (Version 54.0.2840.98 (64-bit)):

Safari (Version 9.1.2 (11601.7.7)):

Do you see any errors in the console? It works fine for me on Safari 10 and even IE but I don't have Safari 9 to test.
Anyway, please open corresponding issue with any console information at https://github.com/vuejs/vuejs.org instead.

Sounds Good.
https://github.com/vuejs/vuejs.org/issues/598


text:
关于vue中的data为什么没有类型检测

What problem does this feature solve?
在vue中props可以限制数据的类型，从而帮前后端省去了很多验证的麻烦，比如限制number，就只能输入数字．如果在data中也能限制类型，那么我在input上绑了一个model就可以进行类型限制，或者其他限制都是可以的
What does the proposed API look like?
great!

对于任意 data 进行运行时类型检测会带来过多性能消耗。如果你真的对类型检测有这么强的需求，不如直接用 TypeScript + Vue.


text:
chore: updated elgohr/Publish-Docker-Github-Action to a supported version (v5)

elgohr/Publish-Docker-Github-Action@master is not supported anymore

You’re welcome. If you like it, you might consider sponsoring 🙂

repo: vuestorefront/shopware-pwa


text:
Surface capabilities query causes a validation error on windows

Version of vulkano: 0.32.3 and master
OS: Windows 10
GPU (the selected PhysicalDevice): Nvidia 1080 Ti
GPU Driver: 516.94

Running the triangle example with validation layers injected at runtime by the vulkan configurator results in this validation error:
    Objects: 1
        [0] 0x2916bb1aa60, type: 1, name: NULL
Using device: NVIDIA GeForce GTX 1080 Ti (type: DiscreteGpu)
VUID-vkGetPhysicalDeviceSurfaceCapabilities2KHR-pNext-02671(ERROR / SPEC): msgNum: -1949531159 - Validation Error: [ VUID-vkGetPhysicalDeviceSurfaceCapabilities2KHR-pNext-02671 ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE;
| MessageID = 0x8bcc83e9 | vkGetPhysicalDeviceSurfaceCapabilities2KHR(): pSurfaceCapabilities->pNext contains VkSurfaceCapabilitiesFullScreenExclusiveEXT, but pSurfaceInfo->pNext does not contain VkSurfaceFullScreenExclusiveWin32InfoEX
T The Vulkan spec states: If a VkSurfaceCapabilitiesFullScreenExclusiveEXT structure is included in the pNext chain of pSurfaceCapabilities, a VkSurfaceFullScreenExclusiveWin32InfoEXT structure must be included in the pNext chain of pS
urfaceInfo (https://vulkan.lunarg.com/doc/view/1.3.236.0/windows/1.3-extensions/vkspec.html#VUID-vkGetPhysicalDeviceSurfaceCapabilities2KHR-pNext-02671)
    Objects: 1
        [0] 0, type: 3, name: NULL

The validation layer is less detailed than the spec, which says:

If the pNext chain includes a VkSurfaceFullScreenExclusiveInfoEXT structure with its fullScreenExclusive member set to VK_FULL_SCREEN_EXCLUSIVE_APPLICATION_CONTROLLED_EXT, and surface was created using vkCreateWin32SurfaceKHR, a VkSurfaceFullScreenExclusiveWin32InfoEXT structure must be included in the pNext chain

repo: vulkano-rs/vulkano


text:
Upgrade to vue2.0 in progress

more info in branch upgrade-vue2

great~~

upgrade-vue2 has been merged into master

repo: vum-team/vum


text:
Размножаются значки

Вот такая забавная штука. Воспроизводится, если открыть панель, и несколько раз остановить-запустить бекенд.

Понял. Работает!


text:
Better localization strings source

Hi @vwochnik,
Since the currently provided language translations are incomplete, have duplicates and errors, I believe you may be interested in using the CLDR library (http://cldr.unicode.org), it has a much more complete and correct localization data, which includes not only translation of languages, but countries, dates and much more.
CLDR is used by Google, Microsoft and many others, so you know it's good.
You can grab the most recent release here: http://unicode.org/Public/cldr/28/. It's big, so you may want to parse the XML, take what you want, and put into YAML files.
When you download the core.zip file, the XML files containing the language translations are in common/main.
There are other projects related to CLDR that can help you get the data:

https://github.com/fschaeffler/cldr-languages
https://github.com/svenfuchs/ruby-cldr
https://github.com/twitter/twitter-cldr-rb
https://github.com/twitter/twitter-cldr-js

You were not satisfied with my limited but complete language set. You made one. Now you say it isn't good enough but I should write another script for that. Why don't you do it? I have a script on the scripts branch doing just that but with different sources.

Sorry @vwochnik, I'm not complaining, it's just that I know you were not satisfied with the translations I provided and I agree that they are not good enough, and the ones available on those gems from where you was getting the data were not great too.
Yes, you're right, you already did a great job on the plugin, I will get the data for you :)

Thanks. Any help is very much appreciated.

authors: Anthony-Gaudino vwochnik

repo: vwochnik/jekyll-language-plugin


text:
Udpver example improve

Udpver example improve

ok

Changed

authors: netroby vzex

repo: vzex/dog-tunnel


text:
Flake8 not working when it has Chinese character

thers is the ALEinfo:
 Current Filetype: python
Available Linters: ['flake8', 'mypy', 'pylint']
  Enabled Linters: ['flake8']
 Linter Variables:

let g:ale_python_flake8_executable = 'python3'
let g:ale_python_flake8_options = '-m flake8'
let g:ale_python_flake8_use_global = 0
 Global Variables:

let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = '✹ Error'
let g:ale_echo_msg_format = '[#%linter%#] %s [%severity%]'
let g:ale_echo_msg_warning_str = '⚠ Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
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_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_linter_aliases = {}
let g:ale_linters = {'python': ['flake8']}
let g:ale_open_list = 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_offset = 1000000
let g:ale_sign_warning = '！'
let g:ale_statusline_format = ['E•%d', 'W•%d', 'OK']
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(finished - exit code 0) 'cmd /c python3 -m flake8 --version'
(finished - exit code 1) 'cmd /c python3 -m flake8 --stdin-display-name ***\www\handlers.py - < C:\Users\***\AppData\Local\Temp\VIACBE6.tmp\handlers.py'

<<<OUTPUT STARTS>>>
Traceback (most recent call last):
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\checker.py", line 471, in run_ast_checks
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\processor.py", line 211, in build_ast
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcaf' in position 270: surrogates not allowed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Python36\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Python36\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\__main__.py", line 4, in <module>
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\main\cli.py", line 16, in main
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\main\application.py", line 328, in run
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\main\application.py", line 316, in _run
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\main\application.py", line 246, in run_checks
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\checker.py", line 319, in run
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\checker.py", line 303, in run_serial
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\checker.py", line 573, in run_checks
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\checker.py", line 474, in run_ast_checks
  File "C:\Python36\lib\site-packages\flake8-3.3.0-py3.6.egg\flake8\checker.py", line 441, in _extract_syntax_information
TypeError: '>' not supported between instances of 'str' and 'int'
<<<OUTPUT ENDS>>>

It will work when change the Chinese character to English character

This isn't a bug in ALE or flake8. You need to declare the encoding at the top of your file, and you need to configure the encoding in your editor appropriately. See here: https://docs.python.org/3/howto/unicode.html#python-s-unicode-support

but I had declare the encoding at the top of  file with 'utf-8', jusk like:
# -*- coding: utf-8 -*-
and I check the file encode with Notepad++ , the soft turn out the file encoded with 'utf-8 with out BOM'
and in my .vimrc  I set the file encoding in utf-8:
set encoding=utf-8
set fileencoding=utf-8
but it still always report the error

Is it the reason that I used it in gvim on Windows

Have a look through Google for '\udcaf'. One of the characters in your file isn't a valid UTF-8 character.

you can new a file with one line:
' print('你好吗‘)'
you will have the problem
it trouble me so many times , I can't have any way to solve It...

you can new a file with one line:
print('你好吗‘)
you will have the problem
it trouble me so many times , I can't have any way to solve It...

you can new a file with one line:
print('你好吗')
you will have the problem
it trouble me so many times , I can't have any way to solve It...
help me, please

Make sure you create files with the correct encoding, and the correct characters. This is a Python issue, not an ALE issue.


text:
Add checkmake (#866)

Adds checkmake linter for make file type.
One annoying thing is that checkmake, for some reason, uses DOS line endings (\r\n), so vim displays ^M in quickfix/loclist. Should I just substitute it?

Yep, that works. Cheers! :beers:


text:
[elixir] Rewrite the credo linter to use json output.

Doing so allows us to provide inline information. I asked the maintainer to add a json format for the errors, and he did so today! Now we can provide the start and end column information so that ALE can underline the relevant parts.
https://github.com/rrrene/credo/issues/471
Need to wait until a new version of credo is released.

Closed due to inactivity.

Sorry, I was still waiting for an official Credo 0.9 release (currently
rc8), I'll update the code shortly!
On Thu, 22 Mar 2018 at 02:49, w0rp notifications@github.com wrote:

Closed #1304 https://github.com/w0rp/ale/pull/1304.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/w0rp/ale/pull/1304#event-1533857625, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABTy9s-XbktRTzz1bSImuTPLgfBpfflrks5tgpKcgaJpZM4RmgnO
.

Sure, sounds good to me. I'll reopen this. Make sure to add a version check, as with linters like flake8, so changing this won't break running earlier versions of the linter.

Closing due to inactivity.


text:
Change acceptable currency

Changed the currency to USDC according to the suggestion
Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

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

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[X] I have read the application guidelines.
[X] A BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (aUSD/USDT) address for the payment of the milestones is provided in the application.
[X] The software delivered for this grant will be released under an open-source license specified in the application.
[X] The initial PR contains only one commit (squash and force-push if needed).
[X] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[X] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @deanyan:matrix.org (change the homeserver if you use a different one)

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

Close this PR according to 0xCaso's suggestion

Since the address is correct, the PR is not necessary, but I'm going to merge it anyway.


text:
Xcavate Blockchain & realXchange dApp

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

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

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or Polkadot (USDC & USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

Hi @Noc2 , thank you for your kind reply.
We will fix it as soon as possible. The former would be closed.
Best regards,
Alan

I have read and hereby sign the Contributor License Agreement.

Hi, David(@Noc2 )
Hope you are well. Could you give me any update for this PR?
Best,

Hi, Many thanks for your comments. I think this draft whitepaper https://xcavate.io/whitepaper might help to understand why we want to keep the Community Project Pallet separate. The issues surrounding the previous PR were driven by a lack of skills... we have plugged that knowledge gap with new team members. I hope this clarifies our position and answers your questions. Best Regards, Richard

We have entered our project in the Polkadot Winter Hackathon so pallet code can be found here... https://github.com/XcavateBlockchain/Xcavate_Node/tree/f4b0eec4305b963d119dba411199786e477d2ae1

If your concerns are purely around appropriateness of a W3F grant… are you suggesting we would be better suited to applying for this new fund? https://futures.web3.foundation/ https://futures.web3.foundation/

@xcavate2022

I thought the W3F grants were there to support projects, which either support the Dotsama ecosystem, or the wider global community (which I believe our pallet and dApp does)… Is that not correct?

Your assumption is correct. However, as you know we can not support every project, hence we decide based on different aspects, such as value the project brings to the community, viability, cost, reusability, previous work, technical aspects and other factors. As I already mentioned previously, I personally have concerns regarding resusability, viability (i.e. mechanism of securing the ownership of the real-world asset through an NFT), performance in the previous delivery, and I'm not convinced that blockchain is the best solution for this project. You haven't given me reasons to convince me otherwise, hence I've came to the conclusion to not add my approval to the project.

authors: meanking takahser xcavate2022


text:
Meetup - Polkadot - Bratislava, Slovakia

My name is Radka and I’m member of Progressbar :house: 👨💻 - the first Slovak hackerspace, coworking and hangout zone in downtown Bratislava. As a non-profit that cares about technology, we are trying to incentivize tech communities, by allowing them to use the venue for their events.

What is the plan: To organize the second meetup at the beginning of January 2019.
Number of people on your team: There are usually between 20 to 60 attendees regularly on meetups organized by our Progressbar team.
Do you need help from W3F: Polkadot team member to do either presentation, workshop or even hackathon would be appreciated. We even open to discuss and consider event like hackathon. 👨💻👩💻  Any help with covering costs (rent, catering, video recording) is welcomed and helpful.  And if we could get some t-shirts and stickers, we would be pleased! :shirt:

We happy to cooparate with W3F and eager to organize more and more meetups in the future!

Hey Radka, thanks for showing interest! It was great to meet you and the other folks from Slovakia at the last meetup.
As a general, we can probably help with a lot of the above. Some of the current considerations:
Internally, we are figuring out how many meetups we'd like to make in Q1 next year and how much budget we think we can assign to it. We will try to send people when we can, although we would also love if local teams could run their own meetups without us. I think that latter point may still be a future goal, but we want to help organisers obtain enough materials and knowledge to be able to present on Polkadot themselves.
In addition to general meetups, we'd really like to start doing more in-depth workshop type events (as you also indicated). Current thinking: get a small group of 20 people (max) and discuss Substrate (/Polkadot) in depth. Potentially, make it hands on and looking at code (we're working on building this). This is something to think about. Progressbar is probably ideal for such an event! 😃

Hello Edward! Apologies for my delayed response,  I've seen your email but couldn't respond earlier due to being fully absorbed by work. However, I suggest to proceed further, which means to agree on the following speaker, exact day of the event (either workshop or lecture) if possible.
We came across the unofficial list of possible speaker you've sent us, and we would firstly aim at your Technologist Adrian Brink. It would be our pleasure to organize in-depth workshop hosting him as speaker in our hackerspace in Progressbar. On the other hand, we are happy to host any member of your Polkadot team, who you find currently more appropriate for the upcoming meetup in January.
Our local team is willing to run our own meetups in the future, with no doubts! Occasional but regular visit of your team is also appreciated and welcomed. :)
I'm up to do a hangout sometime to chat about this!

Are you guys good to reply to these community requests for meetup support?
We can also jump on a call to help create a process for how we handle these
if that would be helpful.
On Wed, 28 Nov 2018 at 08:46, Radka Gettová notifications@github.com
wrote:

Hello Edward! Apologies for my delayed response, I've seen your email but
couldn't respond earlier due to being fully absorbed by work. However, I
suggest to proceed further, which means to agree on the following speaker,
exact day of the event (either workshop or lecture) if possible.
We came across the unofficial list of possible speaker you've sent us, and
we would firstly aim at your Technologist Adrian Brink. It would be our
pleasure to organize in-depth workshop hosting him as speaker in our
hackerspace in Progressbar. On the other hand, we are happy to host any
member of your Polkadot team, who you find currently more appropriate for
the upcoming meetup in January.
Our local team is willing to run our own meetups in the future, with no
doubts! Occasional but regular visit of your team is also appreciated and
welcomed. :)
I'm up to do a hangout sometime to chat about this!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/w3f/Web3-collaboration/issues/48#issuecomment-442451960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aoy1pX8zIcdX6zQNSQx3oHVfSZKNrQhOks5uzpPDgaJpZM4YtSt_
.

--
Jack Platts
Web3 Foundation
Reiffergässli 4, 6300 Zug, Schweiz
https://maps.google.com/?q=Reiffergässli+4,+6300+Zug,+Schweiz&entry=gmail&source=g

Hey @radkaag , let me email you!

authors: EdwardAThomson Josh0akley radkaag


text:
no results for part4 and part5

It seems that for some reason no output is generated for part4 and part5.
Find below the errors that appear in the console, the script I am using, and the sessioninfo() information. If you need something else let me know. Many thanks
------Console---------------------------------------------------------------------
Report part 4
loading all the milestone data from part 4 this can take a few minutes
[1] "report not stored, because no results available"

Report part 5
loading all the milestone data from part 5 this can take a few minutes
generating output for every parameter configurations...
NA-NA-NA-NA-NAreport not stored, because no results available NA-NA-NA-NA-report not stored, because no results available NA-NA-NA--NAreport not stored, because no results available NA-NA-NA--report not stored, because no results available NA-NA--NA-NAreport not stored, because no results available NA-NA--NA-report not stored, because no results available NA-NA---NAreport not stored, because no results available NA-NA---report not stored, because no results available NA--NA-NA-NAreport not stored, because no results available NA--NA-NA-report not stored, because no results available NA--NA--NAreport not stored, because no results available NA--NA--report not stored, because no results available NA---NA-NAreport not stored, because no results available NA---NA-report not stored, because no results available NA----NAreport not stored, because no results available NA----report not stored, because no results available -NA-NA-NA-NAreport not stored, because no results available -NA-NA-NA-r...

Generate visual reports
[1] "File Sab14.bin.bin"
Error in xy.coords(x, y, xlabel, ylabel, log) :
'x' and 'y' lengths differ
In addition: Warning message:
In rm(outputfinal, outputfinal2) : object 'outputfinal2' not found

-----------Script----------------------------------
`mode= c(1,2,3,4,5)
datadir= c("C:/Alba/03_Data/GeneActiv_Sab11y")
outputdir= c("C:/Alba/03_Data/GeneActiv_Sab11y_results_sleeplog")
f0 = 1
f1 = 3
g.shell.GGIR(#-------------------------------
# General parameters
#-------------------------------
mode=mode,
datadir=datadir,
outputdir=outputdir,
studyname=studyname,
f0=f0,
f1=f1,
overwrite = F,
do.imp=TRUE,
idloc=1,
print.filename=FALSE,
storefolderstructure = FALSE,
#-------------------------------
# Part 1 parameters:
#-------------------------------
windowsizes = c(5,900,3600),
do.cal=TRUE,
do.enmo = TRUE,
do.anglez=TRUE,
chunksize=1,
printsummary=TRUE,
#-------------------------------
# Part 2 parameters:
#-------------------------------
strategy = 1,
ndayswindow=c(7,9),
hrs.del.start = 1,
hrs.del.end = 1,
maxdur = 9,
includedaycrit = 1,
L5M5window = c(0,24),
M5L5res = 10,
winhr = c(5,10),
qlevels = c(c(1380/1440),c(1410/1440)),
qwindow=c(0,24),
ilevels = c(seq(0,400,by=50),8000),
mvpathreshold =c(100,120),
mvpadur =c(1,5,10),
#-------------------------------
# Part 3 parameters:
#-------------------------------
timethreshold= c(5),
anglethreshold=5,
ignorenonwear = TRUE,
#-------------------------------
# Part 4 parameters:
#-------------------------------
excludefirstlast = FALSE,
includenightcrit = 5,
def.noc.sleep = c(),
loglocation= "C:/Alba/03_Data/sleeplog_example.csv",
coln1 = 2,
colid=1,
outliers.only = FALSE,
criterror = 4,
relyonsleeplog = FALSE,
sleeplogidnum = FALSE,
do.visual = TRUE,
nnights = 9,
visualreport = TRUE,
#-------------------------------
# Part 5 parameters:
#-------------------------------
threshold.lig = c(30,40,50),
threshold.mod = c(100,120),
threshold.vig = c(400,500),
boutcriter = 0.8,
boutcriter.in = 0.9,
boutcriter.lig = 0.8,
boutcriter.mvpa = 0.8,
boutdur.in = c(10,20,30),
boutdur.lig = c(1,5,10),
boutdur.mvpa = c(1,5,10),
timewindow = c("WW"),
#-----------------------------------
# Report generation
#-------------------------------
do.report=c(1,2,3,4,5))`

-----------Sessioninfo----------

sessionInfo()
R version 3.3.2 (2016-10-31)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows >= 8 x64 (build 9200)

locale:
[1] LC_COLLATE=Spanish_Spain.1252  LC_CTYPE=Spanish_Spain.1252    LC_MONETARY=Spanish_Spain.1252 LC_NUMERIC=C
[5] LC_TIME=Spanish_Spain.1252
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] GGIR_1.5-16
loaded via a namespace (and not attached):
[1] zoo_1.7-14        tools_3.3.2       Rcpp_0.12.10      grid_3.3.2        GENEAread_1.1.1   data.table_1.10.2 bitops_1.0-6
[8] lattice_0.20-34

Thanks for posting this. To get a better understanding of the situation, can you please answer the following questions:

Do all your files have .bin.bin extension? This might be problematic for GGIR (I am not entirely sure). Can you try removing one .bin?
How does the output of part 2 look like, is it what you expect?
Based on the output of part2, can you confirm that the accelerometer was worn in the first 24 hours of the first participant?
Can you share your "C:/Alba/03_Data/sleeplog_example.csv", or at least the first couple of rows?

Hi Vincent,
Many thanks for your check. I tried it again only with one bin file

I did it and nothing changed (the file was previously named 14.bin and now is 14)
Find attached what I got as part2 output and a screenshot of myresults folder
Yes, participants wore the accelerometer since the beginning as it was placed by field nurses.
Find attached the sleeplog_example

part2_daysummary.xlsx
part2_summary.xlsx
visualisation_sleep.pdf
sleeplog_example.xlsx

Many thanks and do not hesitate to ask for further information if needed
Alba

part2 looks good with over 7 days of measurement and wear duration.
maybe inspecting 'QC/plots to check data quality 1.pdf' would be a good extra check to be sure.
Next step is to check that part3 worked well. Can you go to .../meta/sleep.qc and check that there are pdf files in here with meaningful plots of arm angle and sleep classification during the night?

Hi Vincent,
I had to leave the office on friday, I will check this tomorrow when I am
in the office again. In case there are, I will send these files to you
through github
Thanks
Alba
On 9 February 2018 at 14:29, Vincent van Hees notifications@github.com
wrote:

part2 looks good with over 7 days of measurement and wear duration.
maybe inspecting 'QC/plots to check data quality 1.pdf' would be a good
extra check to be sure.
Next step is to check that part3 worked well. Can you go to
.../meta/sleep.qc and check that there are pdf files in here with
meaningful plots of arm angle and sleep classification during the night?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wadpac/GGIR/issues/63#issuecomment-364433841, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AiSpxxE3oYFHK30rpvYzRaAvylWkTqRNks5tTEhUgaJpZM4RyK8m
.

--
Alba Cabré
Predoctoral researcher
ISGlobal
Barcelona Institute for Global Health - Campus MAR
Barcelona Biomedical Research Park (PRBB)
Doctor Aiguader, 88
08003 Barcelona, Spain
alba.cabre@isglobal.org alba.cabre@isglobal.org
--
This message is intended exclusively for its addressee and may contain
information that is CONFIDENTIAL and protected by professional privilege.
If you are not the intended recipient you are hereby notified that any
dissemination, copy or disclosure of this communication is strictly
prohibited by law. If this message has been received in error, please
immediately notify us via e-mail and delete it.
DATA PROTECTION. We inform you that your personal data, including your
e-mail address and data included in your email correspondence, are included
in the ISGlobal Foundation files. Your personal data will be used for the
purpose of contacting you and sending information on the activities of the
above foundations. You can exercise your rights of access, rectification,
cancellation and opposition by contacting the following address:
lopd@isglobal.org. ISGlobal Privacy Policy at www.isglobal.org.

CONFIDENCIALIDAD. Este mensaje y sus anexos se dirigen exclusivamente a su
destinatario y puede contener información confidencial, por lo que la
utilización, divulgación y/o copia sin autorización está prohibida por la
legislación vigente. Si ha recibido este mensaje por error, le rogamos lo
comunique inmediatamente por esta misma vía y proceda a su destrucción.
PROTECCIÓN DE DATOS. Sus datos de carácter personal utilizados en este
envío, incluida su dirección de e-mail, forman parte de ficheros de
titularidad de la Fundación ISGlobal  para cualquier finalidades de
contacto, relación institucional y/o envío de información sobre sus
actividades. Los datos que usted nos pueda facilitar contestando este
correo quedarán incorporados en los correspondientes ficheros, autorizando
el uso de su dirección de e-mail para las finalidades citadas. Puede
ejercer los derechos de acceso, rectificación, cancelación y oposición
dirigiéndose a lopd@isglobal.org . Política de privacidad en
www.isglobal.org.

Hi Vincent,
Here the file 'QC/plots to check data quality 1.pdf' and the pdf with the plots of arm angle
plots_to_check_data_quality_1.pdf
graphperday_id_14.bin_14.bin.pdf
I think they look good, maybe the problem is in step 4...let me know which is the next check
Many thanks,
Alba

That looks good indeed, maybe something goes wrong in reading the sleeplog data and maybe it has to do with the fact that you only have one sleep night in your sleeplog file.
To test whether this is the problem: Can you copy paste the row with sleeplog_example.csv and paste it a row lower and give it a random other ID number? In that way GGIR may better be able to find the sleeplog data it is looking for. If this is the case, then some improvements need to be made in how GGIR handles sleeplog files with a single row of data.

I did it and the same error came out (run the script for one bin file (id=14)  and the sleeplog with two ids (14 and a random id)
Report part 4
loading all the milestone data from part 4 this can take a few minutes
[1] "report not stored, because no results available"

Report part 5
loading all the milestone data from part 5 this can take a few minutes
generating output for every parameter configurations...
NA-NA-NA-NA-NAreport not stored, because no results available NA-NA-NA-NA-report not stored, because no results available NA-NA-NA--NAreport not stored, because no results available NA-NA-NA--report not stored, because no results available NA-NA--NA-NAreport not stored, because no results available NA-NA--NA-report not stored, because no results available NA-NA---NAreport not stored, because no results available NA-NA---report not stored, because no results available NA--NA-NA-NAreport not stored, because no results available NA--NA-NA-report not stored, because no results available NA--NA--NAreport not stored, because no results available NA--NA--report not stored, because no results available NA---NA-NAreport not stored, because no results available NA---NA-report not stored, because no results available NA----NAreport not stored, because no results available NA----report not stored, because no results available -NA-NA-NA-NAreport not stored, because no results available -NA-NA-NA-r...

Generate visual reports
Warning message:
In rm(outputfinal, outputfinal2) : object 'outputfinal2' not found
sleeplog_example.xlsx

Do you use that specific xlsx file? Can you convert it to csv, because that is how I designed GGIR.

Yes, .csv file but here I enclosed the excel file due to it does not allow to attach csv

authors: albacabre vincentvanhees

repo: wadpac/GGIR


text:
Replace npm with npx for running hardhat commands in cli plugin.

Solves #2110
Description
Replace npm with npx for running hardhat commands.
Current behavior is calling the hardhat plugin with npm runs "npm hardhat compile" which is not a valid command. npx command is used, which is recommended by the hardhat docs.
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address: 0xc5a23c04f05D8F1bc27344E394654B21bE9CC488

Thanks for working on this! Closing in favor of #2145 since I wasn't able to make changes here.

repo: wagmi-dev/wagmi


text:
Routable Page Mixin not Working

Issue Summary
When I start a new wagtail project and inherit from the RoutablePageMixin, none of the routes work. However, when I inherit from RoutablePage the routing does work. This is not inline with what is in the docs.

Steps to Reproduce

follow the first app docs to start a new project, then make HomePage inherit from RoutablePageMixin.
Add a routable_page to INSTALLED_APPS and add a path with overrides.
Make a template to test if the context is overridden.
Try to visit the overridden page or extensions off of it. It should result in 404.
Replace RoutablePageMixin with RoutablePage and revisiting the page works.

Example code:
home/models.py
from django.db import models

from wagtail.models import Page
from wagtail.fields import RichTextField
from wagtail.admin.panels import FieldPanel
from wagtail.contrib.routable_page.models import RoutablePageMixin, path

class HomePage(RoutablePageMixin):
    body = RichTextField(blank=True)

    content_panels = Page.content_panels + [
        FieldPanel("body"),
    ]

    def get_context(self, request, *args, **kwargs):
        context = super().get_context(request, *args, **kwargs)
        context["thing"] = "this is default"
        return context

    @path("")
    def override_example(self, request):
        return self.render(
            request,
            context_overrides={
                "thing": "this is not default",
            },
        )

    @path("routed/")
    def routed(self, request):
        return self.render(
            request,
            context_overrides={
                "thing": "this page is extended",
            },
        )

templates/home/home_page.py
{% extends "base.html" %}

{% load wagtailcore_tags %}

{% block body_class %}template-homepage{% endblock %}

{% block content %}

    {{ page.body|richtext }}

    {{ thing }}

{% endblock %}

and visit localhost:8000 and /routed
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
RoutablePageMixin is not working as it says in the docs. I don't even see a reference to RoutablePage in the docs either.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: Run python --version.
Django version: Look in your requirements.txt, or run pip show django | grep Version.
Wagtail version: Look at the bottom of the Settings menu in the Wagtail admin, or run pip show wagtail | grep Version:.
Browser version: You can use https://www.whatsmybrowser.org/ to find this out.

Working on this

Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Your code has class HomePage(RoutablePageMixin):, but the docs specify to inherit from both RoutablePageMixin and Page.

Ah I see, I made a typo when I was switching between RoutablePage and RoutablePageMixin. My code really was
class HomePage(Page, RoutablePageMixin):

But I am sure you are already seeing the problem with the order of inheritance in my code. In django, the mixin needs to come before, so it should be
class HomePage(RoutablePageMixin, Page):

I tried that out and it started working! This is how it is shown in the docs as well. Learned that today! Sorry and I hope this helps someone in the future.

authors: byfarm gasman

repo: wagtail/wagtail


text:
Fix pages in workflow status showing up as "live + draft"

Fixes #10925
It turns out the fix is literally one liner, changing the GenericRelation to use content_type instead of base_content_type. However, that depends on whether we're working with a specific queryset or the base Page queryset. I opted to have two GenericRelations instead so that we can use prefetch_workflow_states() with either, and it will pick the correct relation accordingly.
And yeah, it turns out prefetching GenericRelations with a custom queryset still works fine on Django < 5.0. The one that needs Django >= 5.0 is prefetching GenericForeignKeys, because the result can be of different models.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?

Please describe additional details for testing this change.
With bakerydemo, the issue in #10925 shouldn't occur anymore.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Merged in ad6688f2da05f23a7954da45b95014f0067edbed

authors: gasman laymonage


text:
Set new max_length for redirect.old_path and Page.url

This PR addresses issue #11053. This is an initial attempt  at resolving based on the ongoing conversation in #11053, and might still be subject to changes. This PR attempts a fix by setting a uniform max_length for both redirect.old_path and page.url_path. Thanks to @BertrandBordage for raising the issue.
Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

@BertrandBordage There is mySQL failing test due to this error MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 3072 bytes'), which is as a  result of the higher max_length and mySQL is not able to index it. One option is that we could create a prefix_index in class Meta that uses a substring of old_path to index the field in the database using class Index. This could potentially have some cross database compactibility issues. Or we could set db_index to False, which might cause some query performance issue (not super sure why it is indexed initially). If you have any suggestions you could provide it. Thanks.

@Temidayo32 it's a 'hash' of the old_path that we'd need to generate and apply the unique restraint to. We'd need to take that same hashing algorithm and apply it to lookup values too, which will take a bit of thinking, too.
We solved a similar problem for the Embed model a while ago ([PR here] (https://github.com/wagtail/wagtail/pull/6635)). Care will need to be taken so as not to introduce the same bugs, though.
While md5 hashing would work okay here, I've become quite fond of using Python's uuid5 for this purpose, e.g.:
uuid.uuid5(uuid.UUID("4ccf35b6-0e63-49ec-a878-50e680f3ecfc"), old_path)

Coupled with Django's UUIDField for storage, lookups in most production databases will be much faster than they would with a CharField.
Though your eagerness to help here is very much appreciated @Temidayo32, with so many  moving parts (and paryicularly fiddly migration work), I would suggest that this is something a dev from the core team needs to pick up.

hey guys, is there any update on the issue?

@nrezvoi this PR needs more work to fix the failures with MySQL as per https://github.com/wagtail/wagtail/pull/11129#issuecomment-1826378181
@Temidayo32 do you have time to follow up on this? If not, @nrezvoi is this something you could help with?

Another PR to attempt to solve this problem has been raised, pinging @zerolab @ababic & @BertrandBordage if you wanted to take a look.
https://github.com/wagtail/wagtail/pull/12398

authors: Temidayo32 ababic lb- nrezvoi zerolab


text:
Add Pillow 9.x to version range for Wagtail 2.11

Update Pillow dependency to allow 9.x

okay @gasman I have removed un-necessary upgrade and left only Pillow one for this PR


text:
Figma and postman is not tracked?

so i have two laptops which is personal and work. by installing wakatime i can track the xcode but both figma and postman are not tracked in my machine. so is this my machine problem or wakatime havent ready yet to track those app times? from what i see in leaderboard there is no postman or figma (maybe postman is json but its not even moving at all)

Yes, sorry we're working on finding another way to monitor Figma and Postman because they don't trigger AXFocusedUIElementChanged and similar accessibility events.

Fixed with #150.

authors: AlfinIndrawan alanhamlett

repo: wakatime/macos-wakatime


text:
Fix Haxe spelling

"HaXe" is an old spelling that was changed a while ago:
https://groups.google.com/d/msg/haxelang/O7PB-ZrX4i4/uL69CT44C-IJ

Coverage remained the same at 99.668% when pulling 87f8bde7624e6fa1a4f9ed2b25381bb13901eace on Gama11:patch-1 into 2d3864a10b207d1ec78714375f4f2216f974daee on wakatime:master.

Thanks!

authors: Gama11 alanhamlett coveralls

repo: wakatime/wakatime


text:
It doesn't work with C++ files?

Wakatime doesn't show up in lsp debug. I can only logs for clang
stderr: I[02:29:59.578] PID: 188986
stderr: I[02:29:59.578] Working directory: /home/rakim/programming-stuff/cp+dsa
stderr: I[02:29:59.578] argv[0]: /usr/bin/clangd
stderr: I[02:29:59.578] Starting LSP over stdin/stdout
stderr: I[02:29:59.578] <-- initialize(0)
stderr: I[02:29:59.579] --> reply:initialize(0) 0 ms
stderr: I[02:29:59.581] <-- initialized
stderr: I[02:29:59.581] <-- workspace/didChangeConfiguration
stderr: I[02:29:59.581] <-- textDocument/didOpen
stderr: I[02:29:59.581] <-- textDocument/didOpen
stderr: I[02:29:59.581] Failed to find compilation database for /home/rakim/programming-stuff/cp+dsa/leetcode/lc-1671.cpp
stderr: I[02:29:59.581] ASTWorker building file /home/rakim/programming-stuff/cp+dsa/leetcode/lc-1671.cpp version 0 with command clangd fallback
stderr: [/home/rakim/programming-stuff/cp+dsa/leetcode]
stderr: /usr/bin/clang -resource-dir=/usr/lib64/clang/18 -- /home/rakim/programming-stuff/cp+dsa/leetcode/lc-1671.cpp
stderr: I[02:29:59.581] Failed to find compilation database for /home/rakim/programming-stuff/cp+dsa/interesting_stuff/dp-1-get-all-interesting-substrings.cpp
stderr: I[02:29:59.581] ASTWorker building file /home/rakim/programming-stuff/cp+dsa/interesting_stuff/dp-1-get-all-interesting-substrings.cpp version 0 with command clangd fallback
stderr: [/home/rakim/programming-stuff/cp+dsa/interesting_stuff]
stderr: /usr/bin/clang -resource-dir=/usr/lib64/clang/18 -- /home/rakim/programming-stuff/cp+dsa/interesting_stuff/dp-1-get-all-interesting-substrings.cpp
stderr: I[02:29:59.853] Built preamble of size 2282016 for file /home/rakim/programming-stuff/cp+dsa/leetcode/lc-1671.cpp version 0 in 0.27 seconds
stderr: I[02:29:59.854] Indexing c++17 standard library in the context of /home/rakim/programming-stuff/cp+dsa/leetcode/lc-1671.cpp
stderr: I[02:29:59.880] --> textDocument/publishDiagnostics
stderr: I[02:30:00.022] Built preamble of size 3619304 for file /home/rakim/programming-stuff/cp+dsa/interesting_stuff/dp-1-get-all-interesting-substrings.cpp version 0 in 0.44 seconds
stderr: I[02:30:00.050] --> textDocument/publishDiagnostics
stderr: I[02:30:00.132] <-- workspace/didChangeConfiguration
stderr: I[02:30:01.393] Indexed c++17 standard library (incomplete due to errors): 14161 symbols, 1810 filtered

my config:
{
    "vim_mode": true,
    "ui_font_size": 16,
    "ui_font_family": "Zed Plex Mono",
    "buffer_font_family": "Iosevka Nerd Font",
    "buffer_font_size": 20,
    "tab_size": 4,
    "theme": {
        "mode": "system",
        "light": "One Light",
        "dark": "Ayu Mirage"
    },
    "lsp": {
        "wakatime": {
            "settings": {
                "api-key":"<key>"
            }
        },
        "biome": {
            "settings": {
                "config_path": "/home/rakim/biome.json"
            }
        }
    },
    "languages": {
        "json": {
            "formatter": {
                "language_server": {
                    "name": "biome"
                }
            }
        },
        "jsonc": {
            "formatter": {
                "language_server": {
                    "name": "biome"
                }
            }
        },
        "cpp": {
            "formatter": {
                "external": {
                    "command": "/usr/bin/clang-format",
                    "arguments": [
                        "--style=file",
                        "--assume-filename={buffer_path}"
                    ]
                }
            },
            "lsp": {
                "wakatime": {
                    "settings": {
                        "api-key": "<key>"
                    }
                }
            }
        }
    },
    "buffer_font_features": {
        "calt": false
    },
    "format_on_save": "on",
    "code_actions_on_format": {
        "source.fixAll.biome": true,
        "source.organizeImports.biome": true
    }
}

It works fine with json or python files though so I'm just confused on how to fix it

Hi, it is working fine on my pc.

hmm cpp files sometimes shows up, sometimes doesn't.
Wakatime language server initialized
Wakatime  command: "/home/rakim/.local/bin/wakatime-cli" "--time" "1730396537" "--write" "false" "--entity" "/home/rakim/programming-stuff/cp+dsa/leetcode/hello.c" "--plugin" "Zed/0.159.6 Zed-wakatime/0.1.4" "--language" "c"
Wakatime  command: "/home/rakim/.local/bin/wakatime-cli" "--time" "1730396565" "--write" "false" "--entity" "/home/rakim/programming-stuff/cp+dsa/leetcode/hello.py" "--plugin" "Zed/0.159.6 Zed-wakatime/0.1.4" "--language" "python"
Wakatime  command: "/home/rakim/.local/bin/wakatime-cli" "--time" "1730396565" "--write" "false" "--entity" "/home/rakim/programming-stuff/cp+dsa/leetcode/hello.py" "--plugin" "Zed/0.159.6 Zed-wakatime/0.1.4" "--language" "python"
Wakatime  command: "/home/rakim/.local/bin/wakatime-cli" "--time" "1730396582" "--write" "false" "--entity" "/home/rakim/programming-stuff/cp+dsa/leetcode/hello.py" "--plugin" "Zed/0.159.6 Zed-wakatime/0.1.4" "--guess-language" "--lineno" "0" "--cursorpos" "0"
Wakatime  command: "/home/rakim/.local/bin/wakatime-cli" "--time" "1730396608" "--write" "false" "--entity" "/home/rakim/programming-stuff/cp+dsa/leetcode/hello.py" "--plugin" "Zed/0.159.6 Zed-wakatime/0.1.4" "--language" "python"
Wakatime  command: "/home/rakim/.local/bin/wakatime-cli" "--time" "1730396774" "--write" "true" "--entity" "/home/rakim/programming-stuff/cp+dsa/leetcode/hello.cpp" "--plugin" "Zed/0.159.6 Zed-wakatime/0.1.4" "--guess-language"

@rakim-0 I have released v0.1.5. You will be able to update to the new version once the PR is merged.

Thank you!

repo: wakatime/zed-wakatime


text:
Sometimes it doesn't load and I have to reload

I don't know why, but sometimes it takes a while to serve up the webpage and you have to reload. It should only take a few seconds to generate the info. So why does it sometimes hang for many seconds? I think it is either an underlying python http server issue or something with how I determine ip/mac addresses maybe.
The simple solution is to just reload and it seems fine.

So this isn't so much of a bug as a "feature" of python web servers. They seem to be slow at times. I switched to flask to see if performance improved.

repo: walchko/hostinfo


text:
Add WatchYourLan

Add icon for https://github.com/aceberg/WatchYourLAN

Just realized the icon is already there
https://github.com/walkxcode/dashboard-icons/blob/main/png/watchyourlan.png

repo: walkxcode/dashboard-icons


text:
fix:前端跨域问题

// set CORS
func setCors() gin.HandlerFunc {
	return func(ctx *gin.Context) {
                 // fix:前端跨域问题
		if (ctx.Request.Header["Origin"] != nil) && (ctx.Request.Header["Origin"][0] != "") {
			ctx.Header("Access-Control-Allow-Origin", ctx.Request.Header["Origin"][0])
		} else {
			ctx.Header("Access-Control-Allow-Origin", "*")
		}
		keys := make([]string, 0, len(ctx.Request.Header))
		for k := range ctx.Request.Header {
			keys = append(keys, k)
		}
		if len(keys) > 0 {
			ctx.Header("Access-Control-Allow-Headers", strings.Join(keys, ","))
		} else {
			ctx.Header("Access-Control-Allow-Headers", "*")
		}
		ctx.Header("Access-Control-Allow-Methods", "GET, POST, PUT, PATCH, DELETE, HEAD, UPDATE, OPTIONS")
		ctx.Header("Access-Control-Allow-Private-Network", "true")
		ctx.Header("Access-Control-Allow-Credentials", "true")

		if ctx.Request.Method == "OPTIONS" {
			ctx.Header("Access-Control-Max-Age", "3600")
			ctx.AbortWithStatus(http.StatusNoContent)
			return
		}

		ctx.Next()
	}
}

感谢


text:
WandbCallback fastai failed to show prediction images on wandb app

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

Weights and Biases version: 0.8.15
Python version: 3.6
Operating System: Linux (google colab)

Hi,
I was using wandb.fastai.WandbCallback with setting input_type="images" to send prediction images after each epoch to wandb app. It did send prediction images to wandb app but it did not show anything in AUTO VISUALIZATION/MEDIA/Prediction Samples
(it appears the message of "this run didn't log images for key "Prediction Samples, step 2, index 0." )
I digged into the source code of WandbCallback and replace the line 193 - wandb.log({"Prediction Samples": pred_log}, commit=False) by this wandb.log({"prediction": pred_log}, commit=False), and it worked. Now the images can show in AUTO VISUALIZATION/MEDIA/prediction
Please help to check this issue.

Hey @phucnsp, sorry for the delay.  Can you point me to a run url this was happening for you in?  I think it may be fixed now.

Hey @phucnsp
In the past year we've majorly reworked the CLI and UI for Weights & Biases. We're closing issues older than 6 months. Please comment to reopen.

authors: ariG23498 phucnsp vanpelt

repo: wandb/client


text:
PyTorch stats logging

Stats for tensors, variables and modules. Records simple distribution statistics (min, max, median, ...).
New run history "row building" context manager that lets you add data to a row from a variety of sources (including callbacks etc), then ensures it actually gets written.
See docstrings for more detailed info. Let me know if something is unclear.

Yeah I'd be fine with that
On Sat, Feb 17, 2018 at 3:59 PM, Chris Van Pelt notifications@github.com
wrote:

@vanpelt commented on this pull request.
In wandb/history.py
https://github.com/wandb/client/pull/128#discussion_r168936275:

   self.fname = os.path.join(out_dir, fname)

   self.rows = []

   try:

       with open(self.fname) as f:

           for line in f:

               self._add_row(json.loads(line))

   except IOError:

       pass

   self._file = open(self.fname, 'w')

   self._add_callback = add_callback

   self._torch = None

@contextlib.contextmanager
def build_row(self, enabled=True):

Maybe we change this from build_row to accumulate
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wandb/client/pull/128#pullrequestreview-97388382, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEvyTA_edJQupdkuXn7RNTAfSJuGGQks5tV2fWgaJpZM4SJNap
.

Clossing this because it's been ported to my feature/images branch.

authors: adrianbg vanpelt


text:
[CLI-56] pdb fix

https://wandb.atlassian.net/browse/CLI-56
Fixes #386
Description
What does the PR do?

Respect pdb's excepthooks
Patch module spec before spawning backend process so that python -m pdb test.py works.

Testing
How was this PR tested? Unit test for case 1 and manual testing for case 2.
Case 1:

import sys
import wandb
import os

def _info(etype, value, tb):
    if hasattr(sys, 'ps1') or not sys.stderr.isatty():
        # we are in interactive mode or we don't have a tty-like
        # device, so we call the default hook
        sys.__excepthook__(etype, value, tb)
    else:
        import pdb
        import traceback
        # we are NOT in interactive mode, print the exception...
        traceback.print_exception(etype, value, tb)
        print()
        # ...then start the debugger in post-mortem mode.
        pdb.post_mortem(tb)

def register_pdb_hook():
    sys.excepthook = _info

register_pdb_hook()

if __name__ == '__main__':
    wandb.init()
    a = 1 / 0 # pdb should put a trace back on the failed line for debugging but it breaks when wandb.init() is used

python test.py

Case 2:

import wandb

if __name__ == '__main__':
    wandb.init()   # -> Errors
    a = 1 / 0

python -m pdb test.py

Traceback:
Problem at: c:\users\fariz\desktop\test.py 1 <module>
Traceback (most recent call last):
  File "c:\users\fariz\code\wandb\client\wandb\sdk\wandb_init.py", line 744, in init
    run = wi.init()
  File "c:\users\fariz\code\wandb\client\wandb\sdk\wandb_init.py", line 421, in init
    backend.ensure_launched()
  File "c:\users\fariz\code\wandb\client\wandb\sdk\backend\backend.py", line 129, in ensure_launched
    self.wandb_process.start()
  File "C:\Python36\lib\multiprocessing\process.py", line 105, in start
    self._popen = self._Popen(self)
  File "C:\Python36\lib\multiprocessing\context.py", line 322, in _Popen
    return Popen(process_obj)
  File "C:\Python36\lib\multiprocessing\popen_spawn_win32.py", line 33, in __init__
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "C:\Python36\lib\multiprocessing\spawn.py", line 172, in get_preparation_data
    main_mod_name = getattr(main_module.__spec__, "name", None)
AttributeError: module '__main__' has no attribute '__spec__'

tests/test_pdb.py? is that supposed to be empty?

Checked in by accident. Removed now.