text:
Questions Regarding Generation Weights Offloading and Buffer Usage

Hello Author,
First of all, thank you for your great work on this project. I have a couple of questions regarding the generation process that I hope you can clarify:

Offloading Generation Weights to the CPU:

Why are the generation weights offloaded to the CPU? My understanding is that during generation, the weights should remain consistent with those obtained after training. Therefore, I would expect the generation weights to directly utilize the trained weights rather than being reloaded from the CPU. Could you please explain the reasoning behind this approach?

Use of Two Buffers During Generation:

Why are two buffers used in the generation process instead of one? I noticed that the generation involves handling two separate buffers, and I'm curious about the benefits or requirements that necessitate this design choice. Is there a specific advantage to using two buffers over a single one?

I look forward to your insights on these matters. Thank you for your time and assistance!

Hi @metaqiang ,
As you can see in Figure 8 of the Paper (and also AllGatherPPModel class in code), the model in generation typically has a smaller Model Parallel Size compared to the model used in training. Therefore, during generation, we need to gather the weights from other ranks to form a contiguous buffer.
In AllGatherPPModel, we maintain two buffers: one for training (this_rank) and another for storing the weights from other ranks (cur_pp_rank != self.pp_rank) for generation. This is what we refer to as the two buffers for training and generation.
When we offload the generation weights to the CPU, it means that after the generation process is complete, we only need to keep the parameters from this_rank for the training stage. The weights from other_rank which are used to form the generation weights, are no longer required. Therefore, we offload these weights to reduce peak memory usage.

repo: volcengine/verl


text:
Expire Cache and Refresh Grid on Event

I want to make the grid cache expire on an event and then refresh the data grid.
To be more precise, I have a grid with LookupScript that are not updating after an import...or at least not fully. The fields are being updated on the DB but not on screen.
I know that after 2.4.6 there is now an expiration field for LookupScript but I'm not sure i'm implementing it properly.
I've updated the [LookupScript("xyz")] for the linked tables on their respective xyzRow.cs files to have [LookupScript("xyz"), Expiration = -1], which I believed would cause the cache to clear and thus would make the grid refresh after an import.
At this point after import, if I refresh (F5) the screen, the cache resets and the fields update but I want to achieve the grid refresh without needing to have the user do so manually.
Originally I wanted the grid to only reset the cache and refresh at the moment an import occurs, thus updating the lookup scripts on the grid but if I get the screen to refresh, I'm fine with leaving the general cache for LookupScript as Expiration = -1.
I also wanted to update the refresh button since, even after import, if I click on the refresh button, the cache doesn't refresh.

Q.reloadLookup

great. Thanks.  I was looking through the sample templates and I saw that. Was going to play around with it in a bit.

source: gharchive/issue

authors: sayuga volkanceylan

repo: volkanceylan/Serenity

license: mit

license_type: permissive

license_source: bigquery


text:
How to generate PDF from background thread.

Hi
I have a thread which runs in the night to send invoices to all client with PDF attachment. How can I generate the PDF from a background thread?
I implemented the ReportKey feature to generate the Invoice PDF which is working fine in the browser. But this is getting failed from the background thread due to unavailability of "Request" object and this object is not available when generating the PDF from a thread.
please suggest if anyone already has done the similar implementation.
Many Thanks in Advance.

Try to see this post https://github.com/volkanceylan/Serenity/issues/2819

Closing due to inactivity.

authors: AlperanQ Estrusco ramveersgh


text:
Why this is not working?

I have the following trying to check if TenantId==1
but it is not working and not showing while TenantId is 1
        public virtual void OnValidateRequest(IDeleteRequestHandler handler)
    {

        if (fld.TenantId==1)
        {
            throw new Exception("You are not allowed to delete this record. It is already approved!");
        }

    }

try this..
if (fld.TenantId.Equals("1"))
{
throw new Exception("You are not allowed to delete this record. It is already approved!");
}

@flextrio-gandhi
The same problem. Not working.

try once:
handler.Row.TenantId

authors: Junariz flextrio-gandhi ms4hafiz


text:
ToastrOptions

Dear @volkanceylan,
I'm playing with ToastrOptions trying to create a Toast with the close button that never disappear (until the close button is clicked).
So I managed to add the button and also modify the timeout like this
hub.client.globalNotification = function (notification) {
var to = {};
to.timeOut = 10000;
to.closeButton = true;
Q.notifySuccess(notification, '', to);
};
but I was wondering if there a 0 or -1 trick to obtain what I'm looking for...
Moreover, which is the difference between the TimeOut property and the ExtendedTimeOut one?
Thanks for your support
Best Regards

He's sleeping

copy that...I'll wait :-)

This does not directly write js, c# generated

See toastr options in its own repository / docs. I dont know this.

Ok thanks!

authors: 107295472 marcobisio volkanceylan


text:
Can't find wkhtmltopdf.exe which is required for PDF generation

how to rectify this issues

You can download it from http://wkhtmltopdf.org/downloads.html and install software.
copy wkhtmltopdf.exe to App_Data\Reporting folder.
regards
Shailesh

Read the rest of the error message, how can you read first sentence and not rest!

authors: GOBIBE shaileshbc volkanceylan


text:
Alternative syntax for take on a SQL 2008 based dialect

Serenity\Serenity.Data\FluentSql\SqlQuery_ToString.cs
Reason for update:

The comments were still in Turkish
The English translation is a courtesy of Google.

Use a SQL 2008 based dialect, with "UseTakeAtEnd" true.
Generally, this syntax performs much better with a large number of records
For example, using:
skip: 100
take: 5000
Instead of:
select *
from (
select top 5100
field1,
row_number() over (order by field1) as rowid
from table1
) result
where rowid > 5000
Use this:
select *
from (
select
field1,
row_number() over (order by field1) as rowid
from table1
) result
where
rowid > 5000 and rowid <= 5100

The previous code was based on a dialect that have "UseRowNum" true.
Updated the "take" section to use the "ROWNUM" alias "numberingofrow"

Updates were tested with:
Original dialects for SQL 2008 and SQL 2012
Custom SQL 2008 based dialect with "UseTakeAtEnd" true

Sorry for late reply. Thanks a lot, i should have translated them myself.
I'm a bit worried to break some other dialect while applying these changes. Will this only work on a custom SQL dialect that returns UseTakeAtEnd = true?

Couldn't get an answer, so closing.

source: gharchive/pull-request

authors: rjaquez-ais volkanceylan


text:
Use Rubocop v0.36.0

Problem
Policial uses Rubocop v0.35.1 , which is missing bug fixes.
Solution
Upgrade Rubocop to the current version, which is v0.36.0 .
/review @volmer, @etiennebarrie
/cc @mariusbutuc

Note: Some specs are failing, but I haven't been able to figure out why. They all relate to Rubocop::Cop::Cop objects having a nil value in @all . E.g.
  1) Policial::StyleChecker#violations skips style guides on files that they are not able to investigate
     Failure/Error: cop_classes.reject!(&:non_rails) unless config['AllCops'].fetch('Rails', {})['Enabled']

     NoMethodError:
       undefined method `without_type' for nil:NilClass
     # ./vendor/bundle/gems/rubocop-0.36.0/lib/rubocop/cop/cop.rb:82:in `all'
     # ./vendor/bundle/gems/rubocop-0.36.0/lib/rubocop/cop/cop.rb:90:in `non_rails'
     # ./lib/policial/style_guides/ruby.rb:31:in `reject!'
     # ./lib/policial/style_guides/ruby.rb:31:in `team'
     # ./lib/policial/style_guides/ruby.rb:10:in `violations_in_file'
     # ./lib/policial/style_checker.rb:21:in `block (2 levels) in violations_in_checked_files'
     # ./lib/policial/style_checker.rb:19:in `each'
     # ./lib/policial/style_checker.rb:19:in `flat_map'
     # ./lib/policial/style_checker.rb:19:in `block in violations_in_checked_files'
     # ./lib/policial/style_checker.rb:18:in `each'
     # ./lib/policial/style_checker.rb:18:in `flat_map'
     # ./lib/policial/style_checker.rb:18:in `violations_in_checked_files'
     # ./lib/policial/style_checker.rb:12:in `violations'
     # ./spec/style_checker_spec.rb:58:in `block (3 levels) in <top (required)>'

Wow, RuboCop 0.36 is huge! https://github.com/bbatsov/rubocop/releases/tag/v0.36.0
I'll check the changelog to understand exactly what's behind thos CI failures

RuboCop::ProcessedSource now requires the target Ruby version: https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/processed_source.rb#L23
You can get the version on ruby.rb using
config['AllCops']['TargetRubyVersion']

Thanks for the tips, @volmer. Yeah, Rubocop v0.36.0 is massive.
The target Ruby version is being given to RuboCop::ProcessedSource now, and the repo targets Ruby 2.1, and a few new Rubocop violations have been fixed. Could you review this again, please?

I like it! :+1:
Just one last thing: could you please squash your commits?

Sure, I can squash them. Out of curiousity, why? Isn't it better to preserve the steps that were needed to implement this?

Commits should be atomic enough to be reverted without causing inconsistencies on the repo history or broken builds (ideally). Also, the fewer commits we have, the better is the git log (good messages are equally important). Sure, in PRs with bigger changes multiple commits might make sense, but on this one I don't see a reason to have more than one commit.

Fair enough! The commits've been squashed.

Thank you! :100:

And thank you for building and maintaining Policial!

Whoops, I just realized that we probably should've bumped the minor version in this gem. Shall I submit a PR for that, and then a PR in Shopify/policial.io to bump the version of Policial?

Don't worry, Policial.io is updated based on the latest master. I'll do it soon.

authors: nickhoffman volmer

repo: volmer/policial


text:
Support for cactoos matchers API

@volodya-lombrozo take a look, please. jtcop check fails with
1) Method throwsOnCollectionChange doesn't have assertion statements.
Please add at least one assertion statement to the test method.
You can also ignore the rule by adding @SuppressWarnings("JTCOP.RuleAssertionMessage") annotation.
Rule: RuleAssertionMessage.
You can read more about the rule here: https://github.com/volodya-lombrozo/jtcop/blob/main/docs/rules/no-assertions.md

on test
@Test
void throwsOnCollectionChange() {
    final Set<String> checks = new ScannedChecks().value();
    new Assertion<>(
        new FormattedText(
        "Should throw exception when trying to modify: \n\t%s",
            checks
        ).toString(),
        () -> checks.add("123"),
        new Throws<>(UnsupportedOperationException.class)
    ).affirm();
}

but it should be okay
I think it would be nice if jtcop supported cactoos-matchers, wdyt?

@l3r8yJ Yes, I agree. Thank you for reporting this bug!

repo: volodya-lombrozo/jtcop

license: MIT

license_source: github-api


text:
[Android] ConferenceUserUtil.toMap fails if user.getStatus() is null

ConferenceUserUtil.toMap fails if user.getStatus() is null
In ConferenceUserUtil class toMap function throws exception if user status is null.
This line produces it:
map.putString("conferenceStatus", user.getStatus().name());

Expected Behaviour
Handle user status is null
After fixes for this issue VoxeetSDK.join promise always fails because of this problem.
Specifications
Plugin version: 0.1.26
Device: [Android Emulator Pixel 3XL]
OS: [Android 10 API 29]

The last commit 1bb81f9 will fix the issue. A fix is scheduled for the SDK to send the proper non null expected value

authors: AlexanderPodlesniyQs codlab

repo: voxeet/voxeet-uxkit-reactnative


text:
fix toggling field not capturing click some times

What changes are proposed in this pull request?
Fixes an issue where toggle field does not register click sometime if you move cursor right after click a field or checkbox.
How is this patch tested? If it is not, please explain why.
Visually inspected to ensure clicking and moving the cursor away is registered as toggle but drag or selection is not.
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[x] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Thanks @benjaminpkane for the suggestion! I have updated to just onClick.


text:
CentOS 6: Enable acceptance tests

our metadata.json claims to support CentOS 6. In that case we should
also test on it.

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

CentOS 6 tests don't work anymore (probably since a very long time)
CentOS 6 is soon EOL
CentOS 6 ships python 2.6 which is EOL since ages
We already support CentOS 7

I'm :+1: to drop CentOS 6 unless someone else fixes the tests.

repo: voxpupuli/puppet-python


text:
Target intent not triggered when the optionnal answer is specified in an action

When building a story in the admin UI:
If an action is added with a non-empty answer and a target intent is specified, the answer will be displayed but the story associated with target intent will not be triggered.

Wrong GitHub

repo: voyages-sncf-technologies/tock


text:
[Icon request] .yaml is not recognized, .yml is

[x] I'm sure this issue is not a duplicate?
[ ] I want to create an icon request

When using the default settings, the .yaml extension is not recognized, .yml is.

Can .yaml and .yml both be shown as .yml now is?
Best regards!
Sander.

Err, that's not our theme, that's the default one. You may want to activate our theme? or file an issue at the original repository?

repo: vscode-icons/vscode-icons


text:
Add StringStylizer

Add StringStylizer to "Text" section
Project URL
https://github.com/kazuhiro4949/StringStylizer
Description
Type strict builder class for NSAttributedString.
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 Error

  :no_entry_sign:
  Found 2 link issues

Link issues by awesome_bot

Line
Status
Link

386
301
https://github.com/SugarRecord/SugarRecord redirects tohttps://github.com/carambalabs/SugarRecord

1771
301
https://github.com/jollychang/robotframework-appiumlibrary redirects tohttps://github.com/serhatbolsu/robotframework-appiumlibrary

  Generated by :no_entry_sign: danger

@dkhamsing can we have @ReadmeCritic to run at every pull request so he corrects those Github user redirects?

Hey @kazuhiro4949, really cool lib! I know the pain of NSAttributedStrings because I implemented NSAttributeStrings extensions for EZSwiftExtensions, so your library is definitely sooo useful!
Thanks for contributing! 😉

Thanks! 😄

@lfarah hm let me think on it

authors: danger-awesome-ios dkhamsing kazuhiro4949 lfarah

repo: vsouza/awesome-ios


text:
Add Scyther

Project URL
https://github.com/bstillitano/Scyther
Category
Debugging
Description
Add Scyther to the awesome list in the Debugging section
Why it should be included to awesome-ios (mandatory)
Scyther is the first debugging tool intended to be shipped with your app. It removes the overhead and boilerplate involved when dealing with debugging tools. Scyther provides a single line setup and uses absolutely 0 private APIs. This sets Scyther apart on many levels from similar tools in that it is safe and hassle-free.
Checklist

[x] Has 50 GitHub stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[x] Has more than one contributor
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hi @bstillitano, thanks for contributing!

authors: bstillitano vsouza


text:
Added CocoaMultipeer

This repository is a peer to peer framework for OS X, iOS and watchOS 2 that presents a similar interface to the MultipeerConnectivity framework (which is iOS only) that lets you connect any 2 devices from any platform.

Thanks

authors: choiceforyou victorgama


text:
Added MTCircularSlider.

Added MTCircularSlider, A feature-rich circular slider control.
Project URL

https://github.com/EranBoudjnah/MTCircularSlider
Description

Added MTCircularSlider, with diamond to indicate it was written in Swift.
Checklist

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

hey @EranBoudjnah, as I mentioned here, your project is just missing a description and then it's ready to go!

Thanks, @Ifarah - totally missed that. Fixed.

thanks

authors: EranBoudjnah dkhamsing lfarah


text:
compatibility with element-ui

Hi, thanks for amazing package ,if you can replace simple input by element-ui i think this package is the best.
best regards.

Support for third party UI frameworks can be provided as a separate package.
We won’t be adding any specific UI framework dependencies to VFG Core.
Feel free to create a compatible plugin for VFG and submit a PR to the README and Docs with a link to the plugins repo.

repo: vue-generators/vue-form-generator


text:
首次进入 有短暂的时间没有style样式

页面刷新时或首次进入后，有短暂的时间没有样式，请问下如何解决

这个后面应该会出一个解决方案#6659
参考ant-design的extract-ssr

@aibayanyu20 https://github.com/ant-design/static-style-extract 可以把这个 pr 到主库里

@aibayanyu20 ant-design/static-style-extract 可以把这个 pr 到主库里

OK

+1

We are still waiting for a release from ant-design-vue right?

We are still waiting for a release from ant-design-vue right?

Yes coming soon !

+1

I have reviewed the configuration in the document and the issue still remains unresolved. Can you please update the document to provide instructions on how to configure and resolve this problem?

look at this https://github.com/vueComponent/ant-design-vue-nuxt/issues/15

I have reviewed the configuration in the document and the issue still remains unresolved. Can you please update the document to provide instructions on how to configure and resolve this problem?

look at this #15

I have reviewed the configuration in the document and the issue still remains unresolved. Can you please update the document to provide instructions on how to configure and resolve this problem?

Thank you for the starter repo, while I was configuring the ConfigProvider within genAntdStyle, it's showing 'Invalid name ConfigProvider'
https://www.antdv.com/docs/vue/ssr-extract-ssr

look at this #15

I have reviewed the configuration in the document and the issue still remains unresolved. Can you please update the document to provide instructions on how to configure and resolve this problem?

Thank you for the starter repo, while I was configuring the ConfigProvider within genAntdStyle, it's showing 'Invalid name ConfigProvider' antdv.com/docs/vue/ssr-extract-ssr

Can you provide a reproduction?

look at this #15

I have reviewed the configuration in the document and the issue still remains unresolved. Can you please update the document to provide instructions on how to configure and resolve this problem?

Thank you for the starter repo, while I was configuring the ConfigProvider within genAntdStyle, it's showing 'Invalid name ConfigProvider' antdv.com/docs/vue/ssr-extract-ssr

Can you provide a reproduction?

Attempting to add the config provider according to the docs,
https://stackblitz.com/edit/github-52q5xr?file=scripts%2FgenAntdStyle.ts

@thisisandreww try this https://stackblitz.com/edit/github-52q5xr-ve5njf?file=scripts%2FgenAntdStyle.ts

@thisisandreww try this https://stackblitz.com/edit/github-52q5xr-ve5njf?file=scripts%2FgenAntdStyle.ts

That works! However, when I tried adding algorithm: theme.darkAlgorithm as the props, it seems to generate the exact same antd.css file as the one without dark algorithm.

@thisisandreww try this https://stackblitz.com/edit/github-52q5xr-ve5njf?file=scripts%2FgenAntdStyle.ts

It doesn't work for me, it throw an error:
/User/xxx/xxx/node_modules/.pnpm/@ant-design+icons-vue@7.0.0_vue@3.3.4/node_modules/@ant-design/icons-vue/lib/utils.js:120
  return getRoot(ele) instanceof ShadowRoot;
                                 ^
ReferenceError: ShadowRoot is not defined

it looks like icon's problem, 'ShadowRoot' doesn't exist on node environment.

@thisisandreww try this stackblitz.com/edit/github-52q5xr-ve5njf?file=scripts%2FgenAntdStyle.ts

It doesn't work for me, it throw an error:
/User/xxx/xxx/node_modules/.pnpm/@ant-design+icons-vue@7.0.0_vue@3.3.4/node_modules/@ant-design/icons-vue/lib/utils.js:120
  return getRoot(ele) instanceof ShadowRoot;
                                 ^
ReferenceError: ShadowRoot is not defined

it looks like icon's problem, 'ShadowRoot' doesn't exist on node environment.

Try downgrading @ant-design/icons-vue to 6.1.0

@thisisandreww try this stackblitz.com/edit/github-52q5xr-ve5njf?file=scripts%2FgenAntdStyle.ts

It doesn't work for me, it throw an error:
/User/xxx/xxx/node_modules/.pnpm/@ant-design+icons-vue@7.0.0_vue@3.3.4/node_modules/@ant-design/icons-vue/lib/utils.js:120
  return getRoot(ele) instanceof ShadowRoot;
                                 ^
ReferenceError: ShadowRoot is not defined

it looks like icon's problem, 'ShadowRoot' doesn't exist on node environment.

Try downgrading @ant-design/icons-vue to 6.1.0

Succeed :) Thanks!

hI, I can still reproduce the issue, here is an example, just refresh the page. Am I doing something wrong @aibayanyu20  ? Thanks beforehand :)
https://stackblitz.com/edit/github-52q5xr-wk4qod?file=layouts%2Fdefault.vue,scripts%2FgenAntdStyle.ts

authors: aibayanyu20 betteroneday eward957 fskarmeta linsxw tangjinzhou thisisandreww vietanhbui

repo: vueComponent/ant-design-vue-nuxt


text:
Return values, not keys

Is it possible to get the selected values as ['kia', 'mazda'] and not [1, 2] as it is now?
options: ['ford', 'kia', 'mazda'] and mode is tags

You can do that by providing options as an object or an array of objects which have the same values as labels:
options: {
  ford: 'ford',
  kia: 'kia',
  mazda: 'mazda',
}

or
options: [
  { value: 'ford', label: 'ford' },
  { value: 'kia', label: 'kia' },
  { value: 'mazda', label: 'mazda' },
]

You can do that by providing options as an object or an array of objects which have the same values as labels:
options: {
  ford: 'ford',
  kia: 'kia',
  mazda: 'mazda',
}

or
options: [
  { value: 'ford', label: 'ford' },
  { value: 'kia', label: 'kia' },
  { value: 'mazda', label: 'mazda' },
]

Thanks Adam,
but if I only have lists as input, means to make a transformation in each control?
			<Multiselect 				mode="tags" 				v-model="state.resource" 				:options="state.items.map((item) => { 					return {value: item, label: item} 				})" 				:object="false" 			/>

Thanks Adam,
but if I only have lists as input, means to make a transformation in each control?
			<Multiselect 				mode="tags" 				v-model="state.resource" 				:options="state.items.map((item) => { 					return {value: item, label: item} 				})" 				:object="false" 			/>

Yes, exactly

Yes, exactly

ok. thanks

ok. thanks

authors: adamberecz bugsel

repo: vueform/multiselect


text:
Essentials > Conditional Rendering の翻訳

Epic: #1
About
https://v3.vuejs.org/guide/conditional.html の翻訳をお願いします。
Goal
https://v3.vuejs.org/guide/conditional.html の翻訳が全てなされていること
Note
翻訳ガイドラインは、ひとまず v2 のものに完全に遵守することとします。
https://github.com/vuejs/jp.vuejs.org/blob/lang-ja/CONTRIBUTING.md

@potato4d
このページの翻訳やります🙋
（Vue2のときもやったので…）

お願いいたします！


text:
props falsy to false

原文是对的，falsy 不是 false。

authors: Justineo wenjy


text:
teleport should be reactive

What problem does this feature solve?
One of the main features of Vue is to control, what components are displayed.
Teleport however requires that an element is mounted before the teleport tag is mounted.
If for some reason the teleport target is removed but mounted again, the teleport does not work.
What I want is:
If teleport is enabled (:disable="false"), then look for the element to be teleported to.
return error or warning if not found.
teleport if found.
This feature would make teleport a lot more easy to use, because it fits better into an Vue environment where everything is reactive.
As for a use-case:
I currently want to teleport an input-field to a sidebar (https://www.primefaces.org/primevue/sidebar) that is displayed on small displays. The sidebar is displayed when I click on the inputfield. Even if I make sure that the teleport is enabled after (up to 10sec) the sidebar is displayed, the teleport fails silently.
What does the proposed API look like?
If teleport is enabled (:disable="false"), then look for the element to be teleported to.
return error or warning if not found.
teleport if found.

You should be able to use a key to force the recreation of the teleport

It has a wierd workaround, that I found seconds before giving up:
    <Sidebar v-model:visible="showMobile" position="top">

    </Sidebar>
    <teleport
      v-if="ready"
      to="#mobileTarget"
      :disabled="disableTeleport"
    >
    ....
    @focus="switchToMobile"
    ....
</teleport>

 data() {
    return {
      showMobile: true,            //Initially the teleporttarget is present
      ready: false,                     // Initially teleport is not created.
      disableTeleport: true,
    };
  },
mounted() {
    this.ready = true;                 //Delays the mount, therefore teleport will not throw an error, because teleporttarget is still present
    this.showMobile = false;     //removes teleporttarget, so its not displayed
  },
methods:{
allowTeleportToMobile(): boolean {
      return this.breakpoint === "xs" || this.breakpoint === "sm";
      },
 switchToMobile() {
      if (this.allowTeleportToMobile && !this.showMobile) {
        this.showMobile = true;              // first make the teleporttarget available
        this.ready = false;                       // remove the teleport
        setTimeout(() => {                      //wait a little (it doesn't work without setTimeout
          this.disableTeleport = false;     //enable the teleport
          this.ready = true;                     // render it ==> now it teleports properly.
        }, 1);
      }
    },
}

But its a very verbose and ugly workaround if you ask me.
The teleport should check for the existence of the target, when activated. I would even propose that the target can be a vue component it self, but it would certainly help if that mounted requirement is gone.
Don't know what exactly you were proposing with the key. I only know it from lists (v-for), which isn't my current use-case.

@telion2  the work around with key would be adding the :key attribute to the component (or teleport, not sure exactly which is most appropriate @posva). If you change the key, vue will see this and force a re-render.
Its not a feature that has to be exclusively used with v-for or iteration over data. It can be used in any situation.

Have a very similar usecase — using portal-vue to make it work — but would be nice if Teleport supported these scenarios.

authors: ScottAwesome posva renatodeleao telion2

repo: vuejs/core


text:
fix: type checking for unknown components when strictTemplates enabled

fixes #3539
vue-ignore doesn't work tho

@so1ve
Thank you for looking into this, would be great to get it working again.
I remember that strictTemplates was able to report unknown props,
but i can't remember if it reported unknown event listeners too.
Would it be possible to make it report unknown event listeners?
I can make a new issue for this ofc, just need to know if that would be a separate issue.

@IceBlizz6 Sure please open a new feature request :D

#3718

Is there anything that can be done to help this pull request along?
Would be great if this could be made available in the near future.

repo: vuejs/language-tools


text:
Allow bypassing getters in @pinia/testing

From https://github.com/vuejs/pinia/discussions/944

There should be a way to bypass any getter when testing components that use a store.
Some Ideas:

use the createTestingPinia() to add a plugin that allows modifying any getter:
// in a test
const store = useStore()
store.myGetter // getter computed value
store.myGetter = newvalue
store.myGetter // newvalue

Maybe a different way to pass options specific to stores:
createTestingPinia({ overrides: [
  [useSomeStore, { getters: { /* autocompletion */ stuff: ... }}]
] })

This! A thousand times this!
I am in favor of the first variant, because the stubbing might happen in a different place from where the testing pinia was created.
Until today I was using store.$patch, which works and passes type-checking as long all of the store properties are read-only. (Probably not intended.)

This isn't working properly with Typescript.
// store.ts
import { defineStore } from 'pinia';

export const useStore = defineStore('store', {
  getters: {
    foo: () => true,
  },
});

// test.ts
import { createTestingPinia } from '@pinia/testing';
import { useStore } from 'store.ts';

describe('Test', () => {
  const pinia = createTestingPinia();
  const store = useStore(pinia);

  // Error TS2540: Cannot assign to ' foo' because it is a read-only property
  store.foo = false;
});

Versions

typescript: 4.7.3
pinia: 2.0.16
@pinia/testing: 0.0.12

I am doing the following now (latest version 2.0.17):
type Mocked<T> = { [P in keyof T]: ReturnType<typeof jest.fn> };
function mocked<Id extends string, S, G, A>(store: Store<Id, S, G, A>): S & UnwrapRef<G> & Mocked<A> {
  /* eslint-disable-next-line @typescript-eslint/ban-ts-comment -- the new type is due to `app.use(createTestingPinia())` */
  //@ts-ignore
  return store;
}

describe('Test', () => {
  const pinia = createTestingPinia();
  const store = mocked(useStore(pinia));

  store.foo = false;
});

@posva can this issue be reopened or should I create a new one?

I'm also struggling with it myself.

This isn't working properly with Typescript.
// store.ts
import { defineStore } from 'pinia';

export const useStore = defineStore('store', {
  getters: {
    foo: () => true,
  },
});

// test.ts
import { createTestingPinia } from '@pinia/testing';
import { useStore } from 'store.ts';

describe('Test', () => {
  const pinia = createTestingPinia();
  const store = useStore(pinia);

  // Error TS2540: Cannot assign to ' foo' because it is a read-only property
  store.foo = false;
});

To fix this I needed to add the next line just above each getter modification
 // @ts-expect-error: Getter is read only

Versions

typescript: 4.7.3
pinia: 2.0.16
@pinia/testing: 0.0.12

Unfortunately, this doesn't seem to work when your getters are defined as computed.

any workarounds or solutions for this?

If you are using Jest, I've bypassed it like that (probably because Typescript has lost track):
jest.spyOn(store, 'foo').mockImplementationOnce(() => false)
Maybe not the best workaround but doesn't trigger any error on my end.
If you are using another framework there should be something similar to mock object methods.

to bypass the error for me I had to do
let store: Record<string, any>;

beforeEach(() => {
  setActivePinia(createTestingPinia());
  store = useStore();
});

then later in a test
// For normal getters
store.isAvailable = true

// For parametrized getters
storetore.isAvailableAddOn = jest
  .fn()
  .mockReturnValue(false);

And I don't have any errors and the getter is correctly overwritten.

authors: JJBocanegra Kaperskyguru bodograumann damafeez lbineau posva sebakocz venux92

repo: vuejs/pinia


text:
--url option is not working for plugin cli-plugin-e2e-cypress

Version
3.0.3
Node and OS info
node 8.9.4", npm 6.2.0", Windows 10 (Platform: win32 (10.0.17134))
Steps to reproduce

Set up a Vue CLI application that uses an external local dev server like IIS (not through npm run serve)
Add cypress e2e test supported by VueCLI
Add "test:e2e": "vue-cli-service test:e2e --url http://localhost:33333" to scripts in package.json
Run npm run test:e2e

What is expected?
Cypress to run as normal, testing http://localhost:33333
What is actually happening?
I receive the following error:
Error: Command failed: C:\Users\...\node_modules\cypress\bin\cypress open --config baseUrl=http://localhost:33333

Set up a Vue CLI application that uses an external local dev server like IIS (not through npm run serve)

So:

that server is already running on port 33333 while you start cypress
you tested it's reachable under that port
And that server is actually serving your app
...and it fails as described above,
while with a dev-server through `yarn serve, it works?

Thanks for the swift response,
More info...
I've tried the above on a different set-up: Mac OS, node 10.7.0, npm 6.1.0 with the same versions of Vue CLI and all the plugins... using a remote url through --url works, so I'll close the issue.

Well if this is a windows-related problem we might still be able to do something. But it might also be a Cypress bug.

To... I found something that may or may not be useful: after clearing out node_modules etc... I re-installed everything. I was served the following message:
Cypress 3.1.0 is already installed in C:\Users\...\AppData\Local\Cypress\Cache\3.1.0
The error from the open command that comes from node_modules looks like this:
Command failed: C:\Users\...\node_modules\cypress\bin\cypress open --config baseUrl=http://localhost:33333/
Around the time this stopped working I updated from:
"@vue/cli-plugin-e2e-cypress": "^3.0.0-rc.7",
To:
"@vue/cli-plugin-e2e-cypress": "^3.0.3",
A funny thing about this project, though it shouldn't have a bearing on Cypress, is: we're not using npm run serve. We're building to dist and watching src. This is because our templates are served by an IIS server through x-template script tags, and, quite honestly, because I can't get the devServer proxy to work.

This https://github.com/cypress-io/cypress/issues/5466 seems to be a root cause of the issue

authors: LinusBorg irriss ness-EE

repo: vuejs/vue-cli


text:
Environment Variables .env with ^M character (by gitlab-ci) can not be read

Version
3.0.5
Reproduction link
https://github.com/govo
Node and OS info
node v8.9.0 ,nvm 6.4.1, Mac and Linux
Steps to reproduce
Using gitlab-ci, Settings->CI / CD ->Secret variables, add new key, with 3 variables:
DEV_ENV
value:
VUE_APP_BASE_URL="./v1"
VUE_APP_API_VERSION="1.0.1"
VUE_APP_API_ROOT="/v1"
Then setup gitlab-ci.yml, to make an .env.production file:
(part of codes)
script:
- echo $DEV_ENV > .env.production
- npm run build
Then an .env.production will be generated, and will be used.
But the .env.production file has some carriage-return character: ^M. This makes vue-cli recognizing .env.production failed, all environment variables is empty!
What is expected?
vue-cli should recognize the .env.production variables correctly, with 3 variables.
What is actually happening?
vue-cli can not recognize the variables

if there is only one variable, the cli work find, because of no ^M character.
like this, key:
DEV_ENV
value:
VUE_APP_BASE_URL="./v1"

@LinusBorg If I need more configuration, for continuous integration & delivery, like this:
test env:
key:DEV_ENV
value:
VUE_APP_BASE_URL="./v1.0.1/"
VUE_APP_API_ROOT="http://debug.xxx.com/v3/"
production env:
key:DEV_ENV
value:
VUE_APP_BASE_URL="http://cdn.xxx.com/"
VUE_APP_API_ROOT="http://xxx.com/v2/"


text:
Linting results are different between ‘vue-cli-service serve’ and ‘vue-cli-service lint’

Version
3.9.3
Reproduction link
https://github.com/junyo/test-tslint
Environment info
Environment Info:

  System:
    OS: Windows 10
    CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
  Binaries:
    Node: 11.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.17.3 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 44.17763.1.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.0.0
    @vue/babel-preset-app:  3.10.0
    @vue/babel-preset-jsx:  1.1.0
    @vue/babel-sugar-functional-vue:  1.0.0
    @vue/babel-sugar-inject-h:  1.0.0
    @vue/babel-sugar-v-model:  1.0.0
    @vue/babel-sugar-v-on:  1.1.0
    @vue/cli-overlay:  3.10.0
    @vue/cli-plugin-babel: ^3.10.0 => 3.10.0
    @vue/cli-plugin-e2e-cypress: ^3.10.0 => 3.10.0
    @vue/cli-plugin-typescript: ^3.10.0 => 3.10.0
    @vue/cli-plugin-unit-jest: ^3.10.0 => 3.10.0
    @vue/cli-service: ^3.10.0 => 3.10.0
    @vue/cli-shared-utils:  3.10.0
    @vue/component-compiler-utils:  2.6.0 (3.0.0)
    @vue/preload-webpack-plugin:  1.1.1
    @vue/test-utils: 1.0.0-beta.29 => 1.0.0-beta.29
    @vue/web-component-wrapper:  1.2.0
    jest-serializer-vue:  2.0.2
    typescript: ^3.4.3 => 3.5.3
    vue: ^2.6.10 => 2.6.10
    vue-class-component: ^7.0.2 => 7.1.0
    vue-hot-reload-api:  2.3.3
    vue-jest:  3.0.4
    vue-loader:  15.7.1
    vue-property-decorator: ^8.1.0 => 8.2.1
    vue-router: ^3.0.3 => 3.1.2
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.10 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vuex: ^3.0.1 => 3.1.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
Warnings output
npm run serve
No Warnings and Errors output
npm run lint
What is expected?
results output from 'vue-cli-service serve' command should be same as 'vue-cli-service lint' command
What is actually happening?
no errors and warnings from 'vue-cli-service lint' command

I am having the same issue

+1

The same happens between npm run lint (no errors) and npm run build (multiple errors)!

I believe it's a cache issue as if you remove node_module/,cache folder, you get similar results on the first run.

Sadly this doesn't make a difference for me.

up

This issues still exists on 4.0.0-rc7 removing the cache folder as mentioned above has no effect, typescript errors (or rather warnings defined as errors) are only showed on serve not lint.

npm run serve does not honor .eslintrc rules while npm run lint does.
I have the following rules defined
{
  "rules": {
    "quotes": ["error", "double", { "avoidEscape": true }],
    "comma-dangle": ["error", "never"]
  }
}

with npm run serve I get a lot of warnings related to double quote and missing commas but npm run lint doesn't report anything.

Same issue reproducing for me

npm run serve does not honor .eslintrc rules while npm run lint does.
I have the following rules defined
{
  "rules": {
    "quotes": ["error", "double", { "avoidEscape": true }],
    "comma-dangle": ["error", "never"]
  }
}

with npm run serve I get a lot of warnings related to double quote and missing commas but npm run lint doesn't report anything.

I'm having the same issue. I have to disabled "lintOnSave" in the vue config to get it to stop spamming my terminal with warnings.

Same.  I initialized a new repository with version "@vue/cli-service": "^4.0.0", on Sunday (Nov 10)
I'm using vsCode with Prettier extension installed.  The default code in Hello World where the Router Links are separated by |... Prettier continually converts it to no space, and I get the yellow warning spam whenever I save, telling me I need to put in a space.  But then I run the lint command and it says there are no errors.
I'd ignore it except sometimes I make legit errors and need to see them in the console.

+1

In my case setting lintOnSave: true in vue.config.js file fixes the issue.
module.exports = {
    lintOnSave: true,
    ...
}

I'm getting a build error on the linter: unexpected console statement (no-console) but this error is not shown on npm run lint or when i serve the application
I would like to get all errors which i might get in npm run build in the npm run lint otherwise it goes wrong on deployment instead of when we are in development

I'm seeing the same issue.  Of particular note is getting an unused expression message for every call to expect() in my tests.  I have chai-friendly installed and configured and it works great when I explicitly run the lint command, but when running tests or building or anything else I get the error message.

Has there been any progress on this?

To accentuate the importance of this issue, I'm unable to run build, always resulting in Build failed with errors.
Whether lintOnSave is set to true or false has no effect.

Found out these are not ESLint errors, but type checking errors.
The weird part is that I've developed using a NPM script for the command tsc --noEmit, and it is giving me clean check.
However type checking errors given by vue-cli-service build are different and there are a whole bunch of them. Where does these come from?

tsc cannot check .vue files. There's an issue tracking this: https://github.com/vuejs/vue-cli/issues/1891

May 8th, still here =)

Same problem in mid 2020, with @vue/cli 4.4.1

same issue for me
no error on serve
have to use lint to see the errors inside the lint and the serve (in different terminal)

Anything figured out ? same issue on 11 July.

Side but strongly related issue: lintOnSave is a terribly misleading name for a setting that controls wether linting is run during build. It has nothing to do with the "saving" of anything.

It should be lintOnServe, right @jasonkarns?!

Hi @sodatea , could you please help me)
Providing repo where you can reproduce it
https://github.com/Olexandr24664/vuecli-eslint-lint-build-diff
I was trying with lintOnSave - doesn't work for me.
Maybe there are problems with packages versions?
Appreciate your help)

1

authors: BabOuDev LuccaPrado Olexandr24664 SRNV ahmadarif bogdan-pomirleanu canassa cdekok davidmoseler dgnthr farazshuja jasonkarns jc-lab junyo mbaev nilobarp novaknole ricardovanlaarhoven shelbykauth sodatea techbirds thedavefulton ux-engineer zacharykeeping


text:
【cli-plugin-pwa】 Add 【Launching a page fullscreen from home screen】 support for 【Chrome for Android】

What problem does this feature solve?
Currently, Apple's 【meta】 can be supported through the 【appleMobileWebAppCapable】 option.
https://developers.google.com/web/fundamentals/native-hardware/fullscreen/
【Chrome for Android】 is
<meta name="mobile-web-app-capable" content="yes">

Is there a general option to merge apple and Android.
What does the proposed API look like?
pwa.mobileWebAppCapable
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="mobile-web-app-capable" content="yes">

just put those meta tags in you index.html ?

【Chrome for Android】 is compatible with current Apple's meta。
So now 【appleMobileWebAppCapable】 works for Android and IOS
I Think 【appleMobileWebAppCapable】---> 【mobileWebAppCapable】
And it's better to set these two meta in public/index.html at the same time.
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="mobile-web-app-capable" content="yes">

For me if I added appleMobileWebAppCapable: 'yes' in vue.config.js the meta tag is generated at the end of the  tag in index.html, which means that other meta tags to generate ios splash screen (apple-touch-startup-image) do not work as they are specified before the apple-mobil-web-app-capable meta tag.

authors: KristineTrona LinusBorg lqzhgood


text:
feat(wip): add filesystem cache config for webpack 5

New:

Turn on filesystem cache by default in webpack 5
An addBuildDependencies plugin API for plugins to add additional
dependencies to the cache config

To Fix:

Need to implement a --no-cache option for both serve and build
command
Maybe we should hide the implementation behind a --experimental-cache flag first
Need to decide how to deal with .js config files when a random
environment variable change may affect its exports
lintOnSave option needs an overhaul to work better with webpack 5
and the new cache mechanism
Not sure how to test the cache implementation

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

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)
Due to the may-be-buggy cache configuration, it should be considered as a breaking change.

[x] Yes
[ ] No

Other information:

lintOnSave option needs an overhaul to work better with webpack 5 and the new cache mechanism

Some information about lintOnSave needs to be taken into account
When we set lintOnSave: true, CLI will pass emitWarning: true, emitError: false to eslint-webpack-plugin.
In eslint-webpack-plugin@2.4.3, it will emit all eslint error as compilation warning.
But after 2.5.0https://github.com/webpack-contrib/eslint-webpack-plugin/pull/46 , it will only emit eslint warning as compilation warning, and doesn't report eslint error. We couldn't see eslint rule error message in console totally, the behavior of emitError and emitWarning is just like its name.
And I believe we can use the default value true of both emitError and emitWarning, and using failOnError, failOnWarning instead according to  https://github.com/webpack-contrib/eslint-webpack-plugin/pull/72 https://github.com/webpack-contrib/eslint-webpack-plugin/pull/85
The version of eslint-webpack-plugin is pinned to 2.4.3 in https://github.com/vuejs/vue-cli/pull/6291, Is there more information about this?

And I believe we can use the default value true of both emitError and emitWarning, and using failOnError, failOnWarning instead according to webpack-contrib/eslint-webpack-plugin#72 webpack-contrib/eslint-webpack-plugin#85

Yeah, I think so.

The version of eslint-webpack-plugin is pinned to 2.4.3 in #6291, Is there more information about this?

Somehow the newest version won't re-lint when I run yarn serve the second time in my test project. Haven't figure out the reason yet. But I guess it's related to this PR: https://github.com/webpack-contrib/eslint-webpack-plugin/pull/67

Any update on this?

authors: fangbinwei sodatea yoyo837


text:
can't bind "is" attribute with v-bind object syntax

Version
3.2.24
Reproduction link
codesandbox.io
Steps to reproduce
See reproduction link.
What is expected?
is in  v-bind object behaves like in the single syntax, so:
both :is="component" and v-bind="{ is: component }" should work.
What is actually happening?
v-bind="{ is: component }" will be only an attribute but won't behave as the actual is attribute for dynamic components.

Not sure if it should be listed as a breaking change or should vue 3 handle this as vue 2.6.x did
The solution for this to work is  <component v-bind="componentOptions" :is="componentOptions.is" /> however this solution still puts an is attribute on the component which is unintended.

Please, search existing issues and pull requests before opening issues, it saves maintainers a lot of time 🙏: https://github.com/vuejs/vue-next/issues?q=is%3Aissue+sort%3Aupdated-desc+v-bind+is+is%3Aclosed

Duplicate of https://github.com/vuejs/vue-next/issues/2279

repo: vuejs/vue-next


text:
uc手机浏览器请求无反应

uc手机浏览器请求无反应，使用vue_resource的项目白屏，因为请求无反应，阻塞了进程。

+1

+1

+1

这个问题有人解决没有啊，我也遇到了

这个问题我的解决方法是降低了版本

我在v1.0.3中遇到请求阻塞问题，平台是Android，浏览器是UC浏览器

authors: WoJoinGitHub chengzhuotc dp199313 slashhuang viko16 wuxiaolinchn

repo: vuejs/vue-resource


text:
base option not working

Vue.js / vue-router versions
2.1.2 / 2.1.1
Reproduction Link

http://jsfiddle.net/xgrjzsup/1352/
http://stackoverflow.com/questions/42664712/how-base-option-works-in-vue-router
Steps to reproduce
add base in route:
const router = new VueRouter({
  base: "/app/",
  routes
})

What is Expected?
It should had added /app/ in all the routes when hitting from the browsers.
What is actually happening?
When I do /app/foo in the browser, it is not going to corresponding route of /foo.

As they told you on the SO post, the base doesn't have to be part of the link

authors: mimani posva

repo: vuejs/vue-router


text:
apache .htaccess not working with lazy-loaded routes

Version
3.0.3
Reproduction link
https://beta.pow.cool/members
Steps to reproduce

Create a new app
Add a lazy loaded route named 'myRoute'
Build it
Check that you have a myRoute.js file in your build folder
Deploy it to an apache server after following the .htaccess recommandation in the vue-router docs
Check that your browser shows the content of the myRoute.js file instead of serving the index.html file when browsing http://mysite.com/myRoute

What is expected?
The browser shoud display the index.html at the given route.
What is actually happening?
The browser displays the js content of the javascript file.

It works as expected with the following conf (taken from create-react-app):
Options -MultiViews
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.html [QSA,L]

I see, can you submit a Pull request with the configuration provided. I don't use Apache, so I will need someone to validate it though

we have the apache tomcat one

authors: posva xseignard


text:
Does not recognize custom elements or elements with dash (eg. <q-page>)

<template>
  <q-page class="row">
    <q-scroll-area id="content" class="col">

Main Colors

      <div class="main-color shadow-1 row inline flex-center text-white" v-for="color in main" :key="color" :class="`bg-${color}`">
        {{ color }}

      <div class="main-color shadow-1 row inline flex-center text-white" v-for="color in alert" :key="color" :class="`bg-${color}`">
        {{ color }}

      <div class="main-color shadow-1 row inline flex-center text-white" v-for="color in dark" :key="color" :class="`bg-${color}`">
        {{ color }}

      <div class="main-color shadow-1 row inline flex-center text-dark" v-for="color in light" :key="color" :class="`bg-${color}`">
        {{ color }}

Full Palette

      <q-tabs inverted>
        <q-tab default slot="title" name="tab-default" label="red" color="red" />
        <q-tab-pane name="tab-default">
          <div class="detailed-color column flex-center" v-for="n in 14" :key="n" :class="`bg-red-${n}`">red-{{ n }}

        </q-tab-pane>
        <q-tab v-for="(color, index) in colors" :key="color" slot="title" :name="`tab-${index}`" :label="color" :color="color" />
        <q-tab-pane v-for="(color, index) in colors" :key="color" :name="`tab-${index}`">
          <div class="detailed-color column flex-center" v-for="n in 14" :key="n" :class="`bg-${color}-${n}`">{{ color }}-{{ n }}

        </q-tab-pane>
      </q-tabs>
    </q-scroll-area>
  </q-page>
</template>

The color of <q-*> elements should be green and not the same color than an attribute.
Currently:

Expected:

Yeah this definitely is an issue, I'll see if I can fix it in the next few days.
Github's syntax highlighting uses the old tmLanguage which is not particularly fun to update. Lemme see if I can backport some fixes from vetur and update the old language syntax.

Any news? @skyronic

authors: skyronic slowaways

repo: vuejs/vue-syntax-highlight


text:
[Feature Request] Find Wrapper by Data Attribute

Feature Description
Its not a best practice to find elements by css classes. A better and concise solution is the use of data attributes. So we can give those testable elements a data-testId with a specific name
eg.
<input data-testId="passwordInput" />
Now I can use this data attribute across my test frameworks (unit and e2e testing) without touching other unwanted elements.
Problem
If I search an element by
const firstTypeBasedTicketCard = wrapper.find(
      '[data-test="typeBasedTicketCard-support-request"]'
)

expect(firstTypeBasedTicketCard.exists()).toBe(true)

I get an error
Error: expect(received).toBe(expected) // Object.is equality

Expected: true
Received: false

So I can assume my element does not exist, which is wrong, since the e2e test with nightwatchJs finds the element.
Expected behaviour
I expect to find an element via data attributes.
Edit: Here is my Component HTML
as you see I declared:
:data-test="`typeBasedTicketCard-${ticketType.id}`"

<template>

{{ $t('common.createTicket') }}

    <v-row class="mt-n2">
      <v-col
        v-for="ticketType in ticketTypes"
        :key="ticketType.id"
        cols="12"
        lg="4"
      >
        <v-hover v-slot="{ hover }">
          <v-card
            :elevation="hover ? 16 : 2"
            height="100%"
            nuxt
            exact
            :data-test="`typeBasedTicketCard-${ticketType.id}`"
            :to="
              localePath(
                `/dashboard/product/${productId}/ticket/wizard?type=${ticketType.id}`
              )
            "
          >
            <v-card-title>

{{ $t(ticketType.title) }}

            </v-card-title>
            <v-card-text>
              {{ $t(ticketType.description) }}
            </v-card-text>
          </v-card>
        </v-hover>
      </v-col>
    </v-row>

</template>

Hi!

Its not a best practice to find elements by css classes

Totally agree on that :)
Since wrapper.find accepts any valid DOM selector, you can already write something like
wrapper.find(`[data-test="typeBasedTicketCard-${ticketType.id}"]`)

Also, this is kind of solved in user-land by Testing Library (there's a specific version for Vue, too). Testing Lib uses data-testid,  but it would serve your needs, too.
Hope it helps!

Thank you,
It seems it's a problem with rendering. You pointed out that data attributes are already functional, it's also in the docs. Then I ask myself, why I can find my data attributes.
I try the testing library and update this issue if I get anything to work. If no update comes, assume I still have that issue :D

Okay I close this issue, since i found the magic.
The problem is not about the data-*, its about the rendered HTML. I used the snapshot function to show the generated HTML

common.createTicket

  <v-row class=\"mt-n2\">
    <v-col cols=\"12\" lg=\"4\">
      <v-hover></v-hover>
    </v-col>
    <v-col cols=\"12\" lg=\"4\">
      <v-hover></v-hover>
    </v-col>
    <v-col cols=\"12\" lg=\"4\">
      <v-hover></v-hover>
    </v-col>
  </v-row>

as you see, v-hover has no content, which is actually a problem. So I think the issue is about vuetify testing.

https://github.com/vuetifyjs/vuetify/discussions/13836

authors: afontcu derHodrig

repo: vuejs/vue-test-utils


text:
Click event not firing on slot child component

I thought I'd post this here first in case I was encountering a bug, or if not whether it'd be a quick feature to implement into Vue.js. I can easily move it to the forum if needed.
I'm trying to add a click handler to a child component (using slot), but the method doesn't seem to be firing when the target is clicked (see http://jsbin.com/ficihu/edit?html,js,console,output). I'm sure I've seen other people use a similar thing, but I could be wrong.
Any guidance as to whether this is an issue or not would be awesome. Thanks!

Related to https://github.com/vuejs/vue/issues/2306

Closing in favor of #2306

authors: dcgauld simplesmiler yyx990803

repo: vuejs/vue


text:
Any plan on service-worker for offline usage?

The hexo-offline supports using sw-precache to generate a service worker for offline usage on any hexo site.
Browser Support

As I just mentioned here, I'm definitely not opposed to adding offline support. 👍

I tried hexo-offline with the following configuration:
offline:
  maximumFileSizeToCacheInBytes: 10485760
  staticFileGlobs:
    - public/**/*.{js,html,css,png,jpg,gif,svg,eot,ttf,woff}
    - public/**/**/*.{js,html,css,png,jpg,gif,svg,eot,ttf,woff}
    - public/manifest.json
    - public/browserconfig.xml
  stripPrefix: public

In general, it works, but I was confused by these errors. I also was not able to properly configure caching CDN scripts and Google fonts, it works only through the browser cache.

CDN scripts should be cached using runtimeCaching, see https://github.com/GoogleChrome/sw-precache#runtimecaching-arrayobject
I will document the usage of runtimeCaching on hexo-offline later.
I cannot reproduce the error using the given configuration.

@JLHwung  I tried using runtimeCaching, but I could not achieve results without the use of regular expressions.
I think you can not reproduce the error since it occurs because of files that I generated for use with manifest.json (#772).
Maybe you try yourself and send a request? It would be great :flushed:

Hi morigs,
I've updated the README section to include CDN usage. The runtimeCaching works on the demo site.
I am happy to guide through, don't hesitate to contact me if there is any questions.

Fixed in #918

authors: JLHwung chrisvfritz gogamwar


text:
Update with mixed type id got success but got fail when query

dispatch('create', {
    data: [{
      id: '1',
      checked: false
    }]
  })
getters.find(1) //  null
getters.find('1') // {id: "1", checked: false}
dispatch('update', {
  id: 1, // typeof id is number
  checked: true
})
getters.find(1) // null
getters.find('1') // {id: 1, checked: true}

since query with mixed type would fail,maybe it should throw a warn or error when update,
otherwise query should be success

Ah, yea this could lead problems. To solve this problem, I have a plan to add more strict attributes such as this.string() or this.number instead of this.attr() that should convert '1' to 1.
It's kinda hard to throw warn since ID can be string, and changing type of the id field is OK if a user wants to do that.
I think adding strict attributes is a way to go here.

they have to be taken into account in both: getters & setters, just for consistency
I just hit this issue when I default numbers in models using ... numbers, but updating them into forms converts them into strings and this breaks filtering and stuff ...

This is now possible with Vuex ORM 0.24.3 🎉
https://github.com/vuex-orm/vuex-orm/releases/tag/v0.24.3

authors: kiaking ljwrer razvanioan

repo: vuex-orm/vuex-orm


text:
Automatic Updates

 Issue by jsmith
Wednesday Oct 03, 2018 at 22:43 GMT
Originally opened as https://github.com/vuesic/vuesic/issues/5

As a user, I don't want to worry about manually updating the software everytime a new version comes out. This should be an almost automatic process.
I want to get this feature done early so we can push out updates to whoever install our software. There is definitely stuff out there that should allow us to roll out automatic updates.

Automatic updates should be enabled by default. They should be able to be disabled in the settings (which currently doesn't exist).
While downloading the new application, we should show a spinner in the footer. When the download is complete, we should show a notification with a button that says something like Restart to Update.

 Comment by jsmith
Tuesday Oct 09, 2018 at 20:51 GMT

See https://www.electron.build/auto-update
This is the tool we are using to build out software. We will probably want to implement our own events so we can display information to the user (ie. don't use checkForUpdatesAndNotify). For now though, we can probably just use checkForUpdatesAndNotify until we have a machanism to notify users.
Look here to see how to configure publishing and to hook it into Travis CI.
If you have time, look into a way to test our release cycle using Minio (see https://www.electron.build/auto-update#debugging). This could probably become it's own issue though after we have a basic implementation of auto updates done.

repo: vusic/vusic


text:
ValuePolar sometimes does not draw itself

Open HowTo Use a ValuePolar
The widget is not drawn
Place a Slider, plug it to the Elementa node : it shows up
Now plug ValuePolar again : it draws correctly

IntegerPolar and IntegerPolarUpDown behave the same


text:
Better Trueskill evaluation

Continuing the thread from #43 here because #43 is closed.
@kachayev mentioned

Note sure this is the most convenient avenue for the discussion (let me know if you want to move this to Discord).

I am ok with both. Github issues are archived and easy to view for future users, which is nice. Whereas Discord is easier to do quick chat, so both have pros and cons.

I finally got time to play around with this proposal. I think it's a good idea! Playing games with least predictable outcome should reduce overall uncertainty about skill estimates. Initially I though this is used for matchmaking for training but it seems it's only used for evaluation. Empirically the same approach would be problematic when deciding on opponents for training but just for measurements.

Yes, currently it's only used for evaluation: the Trueskill of the reference agent are fixed and we only update the trueskill of the training agent.

There's still an interesting concern, or even a topic for research/investigations. TrueSkill relies on the prior estimate for draws. For some games, even when following random policy, there is a little chance to get draw (e.g. Chess, or Go). But in other games, it actually takes more sophisticated policy to avoid "drawing" all the time. Specifically keeping in mind practical limitation of using "timestep budget" that typically results in draw. Working with MicroRTS environment we get around this (partially) because we have scripted bots that are quite good from get go. Other options would be an SL policy (imitation learning) to bootstrap the initial population where the estimate of TrueSkill would have reasonably low sigma (and reasonably low prob of drawing).

Questions now are:

how sensitive algorithm to the quality of prior?
how to properly estimate draws prior for a given population?
how does it change with training?
and more

These questions are a bit outside of my realm, haha, but I think are interesting questions worth investigating.

Another question: do we need to re-evaluate skill for existing players when injecting new players into the population. Empirically for large populations, the answer is "yes". It would be interesting to run experiments here for a small size population and only a few newcomers. As we talk about latent variable estimate, we don't ground truth to compare to. But we can run simplified version with only a few match ups selected for each new player vs. full round robin. And measure how different the final result is.

The short answer is no at least in this paradigm. I am following OpenAI Five and AlphaStar's evaluation of fixing the trueskill for reference agents.
See

Hey! More thoughts on the topic as I'm working with evaluation code. It seems like we rely on an assumption that is not as obvious I thought before, and probably needs a verification: both binary search and quality-based sorting assume that A > B and B > C means A > C. Which might not be always the case. There might be a niche strategy out there that doesn't give you much of a winrate but still can outplay a given agent consistently. In the case of trueskill, it seems like estimate of mean is going to be okay. But estimate of variance might overfit into draws. Assume the league structured as the following:

3 top agents that can outplay everyone
10 so-so agents that are mostly scoring draws
3 weird agents with niche strategies that mostly lose

Our prior should give us middle of the distribution, "draw" agents. Quality based estimate here should be heavily skewed towards playing against "draw" agents, because prior belief to lose to "weird" agents it low enough already (middle agents outplay lower agents, playing against middle agents and winning should settle mean MMR higher). As the implication most games goes into mid part of the leaderboard, and the algorithm decrease variance based on those games. When, in fact, epistemic uncertainty about mean estimate is still high.
I can try to build a probabilistic simulation to showcase the scenario. Overall, what do you think about the initial assumption? Would it be a problem for this specific environment? Should we validate it somehow?
As a safety measure, I think playing random games as a part of evaluation should be able to elevate concerns. Or, even more targeted, random games against agents with highest variance. WDYT?

This is a very practical consideration. As a preliminary fix, I randomly pick one of the three opponents with the highest quality scores, which IMO helps to a certain extent.
While the weird agent situation could definitely occur, it is unlikely the case with the current league composition: the bots with low true scale are things like passive AI and random AI. That said, I see this would be a bigger problem once we run into larger leagues.

I think playing random games as a part of evaluation should be able to elevate concerns. Or, even more targeted, random games against agents with highest variance.

I think this is a great idea. The only issue is time: doing matches like this could take a long time and does not reduce the agent's sigma.

There's another problem with the way TrueSkill is used for evaluation right now: the result depends on the order of matches. Especially when we only have a handful of updates (compared to 50+ games per player that are typically used to analyze convergence properties). TrueSkill2 paper has an example of how this could go wrong even with just 8 teams in the tournament. TrueSkill2 solves this by introducing batch update stage using EP algorithm, and as far as I'm aware there's no open sourced implementation of EP inference except the one in Infer.NET (will be glad to be wrong on this).
I'm not sure what would be a good solution here, maybe running 1-to-1 inference over shuffled batch of games results (similar how we do ML training, just minibatch size = 2). This won't be a problem from computation perspective, as we only need to calculate Gaussian params over and over, and we only have a few opponents. But I don't know if we can get theoretical guarantees of the result not depending on the order of evaluations. I need to run deeper investigation, and maybe play around with evaluations that we already have.

authors: kachayev vwxyzjn

repo: vwxyzjn/gym-microrts


text:
mySIMBLHelper still present after Uninstall

Dear w0lfschild,
I've tried since yesterday to fully uninstall mySIMBL, but unfortunately, the process mySIMBLHelper ist still running after startup. Since the uninstall script in the app package didn't work I manually deleted every program file from mySIMBL I could find and even re-installed MacOS Mojave. Please tell me how to fully remove the app without any remaining files/processes. That would help me a lot.
Cheers

Dear w0lfschild,
I've tried since yesterday to fully uninstall mySIMBL, but unfortunately, the process mySIMBLHelper ist still running after startup. Since the uninstall script in the app package didn't work I manually deleted every program file from mySIMBL I could find and even re-installed MacOS Mojave. Please tell me how to fully remove the app without any remaining files/processes. That would help me a lot.
Cheers

Same issue, did you figure it out?

Fortunately it's gone now.
What I did was looking which files the mySimblHelper process does access using Activity Monitor, then deleting some of these (not the one which appear to be native macOS files) using Terminal in Mac Recovery (CMD + R on startup).

Anyone get a fix for this / list of files to delete? I'm having the same issue and I'm too scared to start deleting files on my own...👼

This is the uninstall script:

#!/bin/sh

function nukeFiles() {
    if [[ -e "$1" ]]; then
        if [[ -f "$1" ]]; then
            rm -v "$1"
        else
            rm -vr "$1"
        fi
    fi
}

function createFolder() {
	if [[ ! -e "$1" ]]; then
		mkdir -pv "$1"
	fi
	chmod 777 "$1"
}

log_dir="$HOME"/Library/"Application Support"/mySIMBL/logs
createFolder "$log_dir"
exec &>"$log_dir"/removeSIMBL.log

cleanupFiles=(
"/Library/Application Support/SIMBL"
"/Library/LaunchAgents/net.culater.SIMBL.Agent.plist"
"/Library/ScriptingAdditions/SIMBL.osax"
"/Library/ScriptingAdditions/EasySIMBL.osax"
"/System/Library/ScriptingAdditions/SIMBL.osax"
"/System/Library/LaunchAgents/net.culater.SIMBL.Agent.plist"
"$HOME/Library/ScriptingAdditions/SIMBL.osax"
"$HOME/Library/ScriptingAdditions/EasySIMBL.osax"
)

launchctl unload /Library/LaunchAgents/net.culater.SIMBL.Agent.plist
killall SIMBLAgent

echo "Removing files"

for i in "${cleanupFiles[@]}"; do
    echo Removing: "$i"
    nukeFiles "$i"
done

echo "Done"

This is the uninstall script:
#!/bin/sh

function nukeFiles() {
    if [[ -e "$1" ]]; then
        if [[ -f "$1" ]]; then
            rm -v "$1"
        else
            rm -vr "$1"
        fi
    fi
}

function createFolder() {
	if [[ ! -e "$1" ]]; then
		mkdir -pv "$1"
	fi
	chmod 777 "$1"
}

log_dir="$HOME"/Library/"Application Support"/mySIMBL/logs
createFolder "$log_dir"
exec &>"$log_dir"/removeSIMBL.log

cleanupFiles=(
"/Library/Application Support/SIMBL"
"/Library/LaunchAgents/net.culater.SIMBL.Agent.plist"
"/Library/ScriptingAdditions/SIMBL.osax"
"/Library/ScriptingAdditions/EasySIMBL.osax"
"/System/Library/ScriptingAdditions/SIMBL.osax"
"/System/Library/LaunchAgents/net.culater.SIMBL.Agent.plist"
"$HOME/Library/ScriptingAdditions/SIMBL.osax"
"$HOME/Library/ScriptingAdditions/EasySIMBL.osax"
)

launchctl unload /Library/LaunchAgents/net.culater.SIMBL.Agent.plist
killall SIMBLAgent

echo "Removing files"

for i in "${cleanupFiles[@]}"; do
    echo Removing: "$i"
    nukeFiles "$i"
done

echo "Done"

Whenever I run that script it will never finish. And my simblagent still runs at startup.  I'm running it as a .command file.  That should work right?

You would need to run it as root and SIP also has to be off.

You would need to run it as root and SIP also has to be off.

Thank you for clarifying, I was expecting the terminal to echo done but I found the log file of the uninstallation.  Thanks!

Hi.
I have lurked the web to uninstall this software that was popping up every second for every app, until I learned that is not compatible with SIP.
Mojave 10.14.5
SIMBL 0.7.5
mySIMBLHelper wont uninstall.
I have disabled SIP with :
[quote] Boot into Recovery mode: Restart and hold cmd+r
In Menu -> Toolings -> Start “Terminal”
$ csrutil disable; reboot[/quote]
[quote] and change to "enable" to re-enable SIP[/quote]
Then as root, executed the script with "sudo" and verified the log file.
After relogging, rebooting, restarting in safe mode to delete temps, it is still running.
If I try to close it will inmediatelly restart.
Files opened by it refers to 2 temporal location that are rather permanent.
[quote]"$HOME/Library/Caches/org.w0lf.mySIMBLHelper"
"/private/var/folders/tl//T/AppTranslocation//d/mySIMBL.app"[/quote]
For the case of the private folder, there is something like a mounted file that can not be delete by means of "rm" it contains a copy of the mySIMBL.
If I try to unmount it, it will inmediatelly regenerate with another encoded folder name.
Is it possible to uninstall this?
Do I have to learn how to fully reinstall a MAC?

Ok.. So I found the way myself.
The next are all the files that need to be added to the script.
I deleted them manually, so I am not sure if it will work without editing.
With this, mySIMBLHelper stoped starting and all the dumpstate shown with by launchctl.
Hope it helps.
"$HOME/Library/Caches/org.w0lf.mySIMBLHelper"
"/private/var/folders/tl//T/AppTranslocation//d/mySIMBL.app"
"/private/var/folders/tl/*/C/org.w0lf.mySIMBLHelper"
"$HOME/Library/Preferences/org.w0lf.mySIMBL.plist"
"$HOME/Library/Preferences/org.w0lf.mySIMBLHelper.plist"
"$HOME/Library/Caches/org.w0lf.mySIMBLHelper"

try these commands to completely remove it launchctl list | egrep {SIMBLAgent} and launchctl remove {SIMBLAgent}

authors: FabianStern a-ten albertputinjobs alextenczar jacobidiego meanmemes w0lfschild


text:
Linters error out in iTerm2

Information
I am using iTerm2 Build 3. I am not really sure it its iTerm2 bug or ale bug. I am hoping someone can help me figure out.
VIM version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul 26 2017 19:10:24) Included patches: 1-503, 505-642
Operating System: MacOS High Sierra 10.13.3
:ALEInfo
Current Filetype: python
Available Linters: ['flake8', 'mypy', 'prospector', 'pycodestyle', 'pyflakes', 'pylint', 'pyls']
Enabled Linters: ['pylint']
Linter Variables:
let g:ale_python_pylint_change_directory = 1
let g:ale_python_pylint_executable = 'pylint'
let g:ale_python_pylint_options = ''
let g:ale_python_pylint_use_global = 0
Global Variables:
let g:ale_cache_executable_check_failures = 0
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = 100
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = 50
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_lint_on_insert_leave = 0
let g:ale_linter_aliases = {}
let g:ale_linters = {'python': ['flake-8', 'pylint']}
.
.
.
Command History:
(executable check - success) pylint
(started) ['/bin/zsh', '-c', 'cd ''/Users/amitk/Work/Personal/Github/Practice-python/linked_list'' && ''pylint''  -
-output-format text --msg-template="{path}:{line}:{column}: {msg_id} ({symbol}) {msg}" --reports n ''/Users/amitk/W
ork/Personal/Github/Practice-python/linked_list/list.py''']
(finished - exit code 127) ['/bin/zsh', '-c', 'cd ''/Users/amitk/Work/Personal/Github/Practice-python/linked_list''
&& ''pylint''  --output-format text --msg-template="{path}:{line}:{column}: {msg_id} ({symbol}) {msg}" --reports n
''/Users/amitk/Work/Personal/Github/Practice-python/linked_list/list.py''']
<<>>
(finished - exit code 127) ['/bin/zsh', '-c', 'cd ''/Users/amitk/Work/Personal/Github/Practice-python/linked_list''
&& ''pylint''  --output-format text --msg-template="{path}:{line}:{column}: {msg_id} ({symbol}) {msg}" --reports n
''/Users/amitk/Work/Personal/Github/Practice-python/linked_list/list.py''']
<<>>
What went wrong
As included in Info section the linter returns non zero exit code.
(finished - exit code 127) ['/bin/zsh', '-c', 'cd ''/Users/amitk/Work/Personal/Github/Practice-python/linked_list''
 && ''pylint''  --output-format text --msg-template="{path}:{line}:{column}: {msg_id} ({symbol}) {msg}" --reports n
 ''/Users/amitk/Work/Personal/Github/Practice-python/linked_list/list.py''']

I have tried to run the /bin/zsh -c pylint command it works as expected giving out error message.
However its not working from vim.
I even tried to check it with standard iTerminal application, where it works as expected.
Not sure what's causing execution difference for vim in iTerm2 and standard iTerm.
Screenshots
Successful execution of linter in standard mac terminal

Failed execution of linter in iTerm2

Reproducing the bug
Not 100 % sure of reproducability but in any case
Steps for repeating the bug:

Install https://iterm2.com/
Install  https://github.com/w0rp/ale using https://github.com/tpope/vim-pathogen
Install https://github.com/vim-airline/vim-airline
Set let g:airline#extensions#ale#enabled = 1 in ~/.vimrc
Create *.py file
Try to get pylinter working.

There must be some different in the environment variables or something similar between both terminals. Have a look at your environment variables and such.

Interestingly removing this https://github.com/Yggdroot/indentLine from my pathogent setup resolved all issues.
There is some cosmic relation of packages which I am missing here. Still not sure why it worked in standard terminal though.
Thanks for response @w0rp.

Perhaps some terminal settings caused pylint to output errors with color output, but to a terminal where it wouldn't work, or something. Something to think about.


text:
languagetools: stop auto-appending --autoDetect

I've updated the relevant tests and run them; they pass

This pull request fixes an issue where Ale prevents the user from overriding a broken setting in languagetools (--autoDetect). --autoDetect conflicts with a local
command line usage of languagetools with the ngram data installed
locally. In my case, I've downloaded "en" ngrams with support for the English language.
If you want to retain current behavior, you can change the default value for the languagetools command. That said, since it appears to be somewhat broken, it's probably better to just default to languagetools with no options (as this PR currently implements).
Design-wise, auto-appending anything to a command is a problem because it prevents
users from overriding the appended configuration. There was no way to
remove --autoDetect from the executed command without this commit /
updating the plugin source code. If a user wants autoDetect they are free to place it in their bash script (or other path-included script).
Example command (in a bashscript in my path called languagetools):
#!/bin/bash
java -jar ~/java/LanguageTool-4.5/languagetool-commandline.jar \
  --languagemodel $HOME/Data/ngrams \
  ${@}

By placing "--autoDetect" before my filename, languagetools would only
return linting messages unassociated with ngrams (which are necessary
for checking "their" versus "there" errors). Once I manually removed
this line, everything works correctly.
Example with ngrams and NO autoDetect

notice the second suggestion for "their" versus "there"
Example with ngrams and autoDetect

notice there is only 1 suggestion

@w0rp the _options variables has been created. I've updated the tests and the docs accordingly. Please let me know if there's anything else required.

I don't use ngrams but experiencing issue with --autoDetect resulting in the following output:
[main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999988934696109 ]] 18:56:09.429 [main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999990562851635 ]] 18:56:09.429 [main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999984259788106 ]] 18:56:09.429 [main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999962700310778 ]]
Changing '--autoDetect' to -'-language en-GB' in the handler fixes the issue.

It seems that LanguageTool checks for ngram errors or alike by default when --language``` is passed, but not --autoDetect` as there are less error messages using the latter.
In the meanwhile, you could work around this issue by my simple plug-in (together with, say, Makejob to run the LanguageTool grammar check in the background) where all parameters passed can be entirely overridden.

I don't use ngrams but experiencing issue with --autoDetect resulting in the following output:
[main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999988934696109 ]] 18:56:09.429 [main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999990562851635 ]] 18:56:09.429 [main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999984259788106 ]] 18:56:09.429 [main] DEBUG com.optimaize.langdetect.LanguageDetectorImpl - ==> [DetectedLanguage[en:0.9999962700310778 ]]
Changing '--autoDetect' to -'-language en-GB' in the handler fixes the issue.

@w0rp it seems like the comments in this thread are pointing out that --autoDetect may be a bad default. That said, this PR makes it easily override-able. If there is nothing else to do, would we be able to merge this soon? I'd like to stop using my personal fork for daily work, if possible.

authors: Konfekt abers pappasam


text:
Cannot generate trt

Hi, I'm using your docker 15liangwang/auto-ipu to run LSD, because i didn't have powerful enough GPU, but when i run the script in the way you write in README.md
bash sensor_inference/pytorch_model/export/generate_trt.sh

It output the error message like that:
sensor_inference/pytorch_model/export/generate_trt.sh: line 4: /usr/src/tensorrt/bin/trtexec: No such file or directory
sensor_inference/pytorch_model/export/generate_trt.sh: line 12: polygraphy: command not found

Everything is ok except this command, looking forward to your reply, thand you.

Hi, I'm using your docker 15liangwang/auto-ipu to run LSD, because i didn't have powerful enough GPU, but when i run the script in the way you write in README.md
bash sensor_inference/pytorch_model/export/generate_trt.sh

It output the error message like that:
sensor_inference/pytorch_model/export/generate_trt.sh: line 4: /usr/src/tensorrt/bin/trtexec: No such file or directory
sensor_inference/pytorch_model/export/generate_trt.sh: line 12: polygraphy: command not found

Everything is ok except this command, looking forward to your reply, thand you.

Hi,
This command can be ignored if you use the non-cuda docker image

Hi, I'm using your docker 15liangwang/auto-ipu to run LSD, because i didn't have powerful enough GPU, but when i run the script in the way you write in README.md
bash sensor_inference/pytorch_model/export/generate_trt.sh

It output the error message like that:
sensor_inference/pytorch_model/export/generate_trt.sh: line 4: /usr/src/tensorrt/bin/trtexec: No such file or directory
sensor_inference/pytorch_model/export/generate_trt.sh: line 12: polygraphy: command not found

Everything is ok except this command, looking forward to your reply, thand you.

Hi,
This command can be ignored if you use the non-cuda docker image

Thand you for your reply. When I use the Example Data to test the LSD, I change the mode to 目标检测, I can't see the detected object in the 预览. Except this command error, everything is OK and I can run the mode 建图定位. I want to know if I do somethong wrong.
One more question, Is there a way to independently test each module?

The object detection is based on tensorRT, so the GPU is necessary.
What are the modules you want to test independently?

I want to test the sensor_inference.
It's the lidar detection also need the GPU, what the minimum GPU I need if I want to run object detection in X86 platform.

I want to test the sensor_inference.
I will test the LSD in the platform with GPU later, thank you for your nice replies.


text:
new syntaxes

This PR update the package to be up-to-date with the latest discord markdown flavor

The URL_REGEX regex is a regex bomb. I still need to find a better one and test it properly.

Tested on production environment for two weeks now, seems to be perfectly working. Ready for review.

@Kyrela
Sorry for not getting back to you on this. I'm not actively working on this project anymore. Since you're interested in this, how about I add you as a contributor and you can just adopt this project and merge the changes yourself?

Hi, not sure if I'm the most relevant person to be a contributor (I just fixed a few issues, @Vioshim is the author of 90% of the changes), but as I'm relying on this package for some of my projects, I'll necessarily have to maintain it in any case, so I'd be happy to accept.
PS: I don't think he'd be interested, given that his fork looks abandoned (https://github.com/Vioshim/discord-markdown-ast-parser/pull/2), but it would be interesting to also offer @Vioshim to contribute to the project.

My apologies for the lack of response, never got notifications about it in my email until now, I'll be looking into this, thanks for the patience

@w4rum can you perhaps add @Vioshim as a collaborator?

@Kyrela Sorry for the delay.
I added @Vioshim as a collaborator. Hey, @Vioshim!

Thanks! Not merging anything for now as there isn't any caption (-#) support, and the quote support has big false positives, both on #2 and #4.

authors: Kyrela Vioshim w4rum


text:
利润表的接口里缺少研发费用字段

2018年财务表再次修订，利润表新增研发费用等

同求此数据！

目前是在财务指标接口里，后续我们再加

authors: fujiayue jimmysoa wonderui

repo: waditu/tushare


text:
get_tick_data无法获取数据

get_tick_data这个方法，无法获取数据

报这种问题，需要更详细的说明，不然不知道是什么情况
n [5]: ts.get_tick_data('600848', date='2017-05-24')
Out[5]:
time  price change  volume  amount type
0     15:00:00  16.82     --       0       0   卖盘
1     15:00:00  16.82  -0.03       0       0   卖盘
2     15:00:00  16.85     --       0       0   买盘
3     14:59:54  16.85     --      24   40440   买盘
4     14:59:48  16.85     --      20   33700   买盘
5     14:59:45  16.85     --      32   53920   买盘
6     14:59:42  16.85   0.01      10   16850   买盘
7     14:59:39  16.84  -0.01       5    8420   卖盘
8     14:59:36  16.85     --       0       0   买盘
9     14:59:33  16.85   0.02      10   16850   买盘
10    14:59:30  16.83     --      23   38708   卖盘
11    14:59:27  16.83  -0.02     100  168299   卖盘
12    14:59:24  16.85     --       3    5055   买盘
13    14:59:21  16.85     --       9   15165   买盘
14    14:59:18  16.85  -0.01      58   97730  中性盘
15    14:59:06  16.86     --       0       0   买盘
16    14:59:03  16.86   0.04     501  844686   卖盘
17    14:58:54  16.82     --       0       0   卖盘
18    14:58:51  16.82     --       0       0   卖盘
19    14:58:48  16.82  -0.06      20   33640   卖盘
20    14:58:45  16.88   0.02       8   13504   买盘
21    14:58:39  16.86   0.04      20   33720   买盘
22    14:58:36  16.82  -0.01     204  343128   卖盘
23    14:58:33  16.83     --       0       0   卖盘
24    14:58:30  16.83  -0.05     300  504899   卖盘
25    14:58:09  16.88     --      10   16880   买盘
26    14:58:06  16.88     --      30   50640   买盘
27    14:58:03  16.88   0.05       5    8440   买盘
28    14:58:00  16.83  -0.05      90  152311   卖盘
29    14:57:54  16.88   0.03      11   18568   卖盘
...        ...    ...    ...     ...     ...  ...
1604  09:33:12  17.36  -0.04     122  211792   卖盘
1605  09:33:09  17.40     --       1    1739   卖盘
1606  09:33:06  17.40  -0.01       2    3479   卖盘
1607  09:33:03  17.41     --       9   15669   卖盘
1608  09:32:48  17.41   0.01       2    3482   买盘
1609  09:32:32  17.40     --       7   12179   买盘
1610  09:32:29  17.40   0.04       2    3479   买盘
1611  09:32:23  17.36     --       5    8680   卖盘
1612  09:32:17  17.36  -0.04       3    5208   卖盘
1613  09:32:11  17.40     --       2    3479   买盘
1614  09:32:08  17.40   0.04       2    3479   买盘
1615  09:31:56  17.36     --       4    6944   买盘
1616  09:31:53  17.36     --       1    1736   买盘
1617  09:31:47  17.36     --       2    3472   买盘
1618  09:31:38  17.36     --       2    3472   买盘
1619  09:31:32  17.36     --       2    3472   买盘
1620  09:31:29  17.36   0.01      19   32984   卖盘
1621  09:31:11  17.35   0.01       3    5205   买盘
1622  09:31:08  17.34  -0.01       8   13872   卖盘
1623  09:30:59  17.35  -0.01       2    3470  中性盘
1624  09:30:50  17.36   0.02       2    3472   买盘
1625  09:30:44  17.34  -0.02      52   90168   买盘
1626  09:30:41  17.36     --       0       0   买盘
1627  09:30:26  17.36   0.13       4    6944   买盘
1628  09:30:23  17.23  -0.13       2    3980   卖盘
1629  09:30:08  17.36   0.19      20   34720   买盘
1630  09:30:05  17.17  -0.03     106  182002   卖盘
1631  09:30:02  17.20     --      10   17200   买盘
1632  09:29:00  17.20     --       0       0   买盘
1633  09:25:01  17.20   17.2      91  156520   买盘
[1634 rows x 6 columns]
In [6]:

ts.get_tick_data('600848', date='2017-05-24')
HTTP Error 456:
HTTP Error 456:
HTTP Error 456:
Traceback (most recent call last):
File "", line 1, in
File "C:\Python27\lib\site-packages\tushare\stock\trading.py", line 167, in get_tick_data
raise IOError(ct.NETWORK_URL_ERROR_MSG)

测试了网络是正常的，不知道为什么在我这里调用会这样？

网络被禁了？

我也遇到了跟楼主一样的问题，是因为被防火墙禁了吗？

但是有的时候又能调的出来，感觉像是服务器端不是很稳定啊

这几天同样出现这个问题HTTP Error 456。现象为就最开始能读取一两次数据，之后提示HTTP Error 456，进tushare调试，返回异常；将请求地址复制到浏览器显示“新浪安全拦截”结果页面。猜想服务器不稳定或者做限制了。改成单线程访问结果一样。

日线数据都是正常的，按道理也没必要单独限制tick数据吧

更新了0.7.9之后还是一直显示HTTP Error 456:

https://github.com/waditu/tushare/issues/38

遇到同样的情况，似乎是新浪检测IP了

也遇到一样的问题，难道是新浪作了限制？

新增了两个数据源，通过src设置，tt=腾讯，nt=网易，默认是sn新浪

腾讯的数据源好像不是很完整，我调14年的tick数据有些调不出来

有什么方法能够解决新浪的数据源问题吗？感觉它家的目前最靠谱。

数据问题不是很大，sina只是多了一些成交量为0的tick

完了，我也遇到同样的问题了。无论是腾讯的，网易的还是新浪的，只要每过五，六秒调一次这个API，我的IP就会被禁止，这两天刚刚变得这样的。估计这些公司不允许我们这么干了，咋办啊？好难搞到数据的，还有什么手段可以得到Tick数据吗？

authors: DatumWorld ashtonhong clockzhong jimmysoa lynic pakchoiko phoenixzxj zjujjm


text:
get_k_data设置了ktype之后，起始日期的设置失效

比如，设置了起始日期是2017-07-17，但数据返回的仍然是从2017-07-03开始
ts.get_k_data('000001', start='2017-07-17', end='2017-07-18', ktype='5')
如果不加ktype，默认日K线，则正常。

除了日k线，其他的都是返回所有值，没有时间范围控制。

分钟线只有最近几日的数据，所以没有让日期区间生效

authors: jimmysoa tombluemoon wsrhp


text:
Issue810 GitHub io

Revised structure of the github.io documentation page #810

Checklist before merging:

[x] Existing tests still work (check by running the test suite, e.g. from RStudio).
[ ] Added tests (if you added functionality) or fixed existing test (if you fixed a bug).
[ ] Updated or expanded the documentation.
[x] Updated release notes in inst/NEWS.Rd with a user-readable summary. Please, include references to relevant issues or PR discussions.
[ ] Added your name to the contributors lists in the DESCRIPTION and CITATION.cff files.

Codecov Report

Merging #857 (4b36c34) into master (fc1c679) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 4b36c34 differs from pull request most recent head f6fcfbe. Consider uploading reports for the commit f6fcfbe to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master     #857   +/-   ##
=======================================
  Coverage   73.68%   73.68%
=======================================
  Files          89       89
  Lines       11914    11914
=======================================
  Hits         8779     8779
  Misses       3135     3135

authors: codecov-commenter jhmigueles

repo: wadpac/GGIR


text:
Use appropriate content licence in Guide footer

Currently the Wagtail guide footer says

© Copyright 2022, Hitansh Shah and contributors

I understand this was from the original work and also acknowledges the epic start that @Hitansh-Shah made.
However I think that the content on this site should at a minimum use the same liberal BSD licence as the code. https://github.com/wagtail/guide/blob/main/LICENSE
Alternatively we should consider the content, in isolation having a creative commons licence in its most liberal form.
Either CC0 -https://creativecommons.org/share-your-work/public-domain/cc0/
Or potentially the basic one with attribution required https://creativecommons.org/licenses/
I do think we should acknowledge the contribution and contributors by name ( see https://github.com/wagtail/guide/issues/66 ) but think it's important we ensure the content on this new guide matches the same copyright licence as the Wagtail docs & platofm it's based on.
Proposal
We use the same licence note in the footer as Mozilla's 'how do I Wagtail' - https://foundation.mozilla.org/en/docs/how-do-i-wagtail/

Content available under a Creative Commons Attribution 4.0 International license (CC-BY)

Just realised the Wagtail docs have a copyright statement as follows

© Copyright 2022, Torchbox and contributors

So maybe I'm wrong about this and we should have a copyright statement, I just don't understand how that aligns with the licence used in the code (especially for Wagtail docs which are in files in that code).

I think CC0 would be also a nicer option for the content.

Have raised this with the core team for additional feedback.

@lb @thibaudcolas please review this:
Copyright licensing
There are no rights reserved for this user guide documentation. There are no explicit permission requirements for using, distributing, remixing, adapting or building on its content. All of it is in the public domain and may be used, distributed, remixed, adapted, and built upon for private and commercial purposes to the fullest extent permitted law.
Licensing grounds
The content of this user guide is not restricted in accordance with open source principles. The purpose of this is to facilitate innovation by encouraging open collaboration that is flexible.
Liabilities
The contributors to this user guide documentation assume no responsibility or liability for any damages resulting from errors or omissions in the content. All content in this user guide documentation is provided on an "as-is" basis and no guarantee is provided as to completeness, accuracy, or timeliness.

Done!

Thanks all for this - it's great to clearly articulate that this is a community resource and hopefully the remixes of it will be epic.

Note to self - might be worth raising a similar issue for the Sphinx Wagtail theme docs) & Wagtail docs.

authors: activus-d lb- thibaudcolas

repo: wagtail/guide


text:
Add a UUIDField to the Page model

Is your proposal related to a problem?
There is a general consensus in the tech industry that it's a bad idea for public APIs to expose too much information about a system's inner workings - using page's autoid values as identifiers in the API could be classed by some as exposing 'too much'.
Also, we've seen recently (e.g. in wagtail-transfer) that there is value in being able to identify pages across multiple environments, and relying on autoid values in such a scenario is simply not viable.
Describe the solution you'd like
I'm not suggesting that we replace the AutoIDField with a UUIDField. The AutoIDField does the job - it's efficient, it is relied upon a lot internally, and it's handy to have a short, human-friendly identifier in a lot of situations. Not to mention it would be practically impossible to achieve from a migration/backwards-compatibility perspective.
Rather, I am suggesting that we add a separate UUID field (I would suggest public_id or simply uuid as the name, but that's by-the-by). The field would have a unique constraint, but wouldn't replace the primary key. It would be automatically generated at initialisation and available before saving a page (possibly useful in some scenarios), and would serve as an alternative way of referring to the page when using the autoid value is less than ideal.
You could argue that having more than one identifier for a page is a bit redundant. Some might even use words like 'messy' or 'ludicrous' - and I would have to agree to a point; I wouldn't bake this into something by design. But, I believe the pluses outweigh the negatives here. The overhead of generating and storing a single UUID value for each instance isn't really worth mentioning, and there's nothing to say that we have to make any other changes immediately (although it would be nice to update a few places to support them instead of / as well as the id).
Describe alternatives you've considered
The alternative is that when a project needs to have a UUID for a page, it is added to a custom page model, and the API functionality is overridden, but even then, it would be tricky to use as general 'Page' identifier (you'd always need to be working with specific pages). And in apps like wagtail-transfer, the value is generated and stored in a separate table (which must certainly have an impact on join performance at the database level).

Awesome! Do you plan to transparently replace the id in the API using this as the natural key?

@thenewguy that is the idea, yes. but I thought it best to leave that to a separate PR/discussion and keep this change simple.

authors: ababic thenewguy

repo: wagtail/wagtail


text:
6.1 release notes & documentation fixes

Fix a typo in the filename for one of the tutorial pages.
A few small fixes for the 6.1 release notes (fix typo in example regex, add documentation links where possible, improve readability with a few additional backticks).
Add better JSDoc examples to support the KeyboardController changes from #11853 .

So glad we have the docs check happening, found we had a malformed documentation reference.

Changes picked to 6.1 stable also dd0e3c00b606767013c38c816b7bfb2486633bbf & parents.


text:
Allow hook override of user profile avatar url in admin tags

Resolves #12661

Add the 'get_avatar_url' hook.
Unittest the 'get_avatar_url' hook.
Update documentation.

@gasman

Thanks @jhrr! Merged in 5402010d16dfdd1ea1d09d5e478c9e4bd58c76c8 (with some small final cleanups to the tests).
I've added you to the contributors list as "jhrr" - let me know if you'd like this changed to a full name.

Thanks @jhrr! Merged in 5402010 (with some small final cleanups to the tests).
I've added you to the contributors list as "jhrr" - let me know if you'd like this changed to a full name.

You can add "James Harrington" to the contributors, sure thing.
My pleasure. Many thanks for the library, currently using it and have used it in multiple projects. Hope I can contribute more as and when the opportunity arises.

@jhrr No problem - updated now!

@jhrr No problem - updated now!

Great stuff thanks!

authors: gasman jhrr


text:
License?

Hi:
What's the license for this library?
Thanks!

It's at the top of the source files, phf.h and phf.cc.
I've committed a LICENSE file for Github's benefit.

@wahern Thanks... Gee I was completely and desperately blind. Sorry for the noise!

No sweat. It happens to all of us. Just pay it forward ;)

authors: pombredanne wahern

repo: wahern/phf


text:
🛑 Matrix Synapse is down

In 9934805, Matrix Synapse (https://matrix.a64.work) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Matrix Synapse is back up in 8a0a3fe.

repo: wakira/my-upptime


text:
NCBI_accession corresponds to sample_id in place of run_id for HMP samples

Hello,
In the file combined_metadata.rda, the field NCBI_accession corresponds to the sample_id in place of the run_id for HMP samples.
For example:
dataset_name | sampleID | subjectID | NCBI_accession
HMP_2012 | SRS056519 | HMP_2012_765094712 | SRS056519
HMP_2012 | SRS018427 | HMP_2012_160218816 | SRS018427
Should be replaced by:
dataset_name | sampleID | subjectID | NCBI_accession
HMP_2012 | SRS056519 | HMP_2012_765094712 | SRR063503;SRR063504
HMP_2012 | SRS018427 | HMP_2012_160218816 | SRR059916;SRR059917
Thank you.

Thanks for catching this typo. I see that a similar problem is also affecting the KarlssonFH_2013 and the YuJ_2015 datasets.
@paolinomanghi could you generate the right NCBI_accession for these three datasets?

@schifferl
Yes, all the HMP samples are concerned.

authors: edoardopasolli fplaza

repo: waldronlab/curatedMetagenomicData