Problem running gulp using nodist

i have multiple versions of node installed and choose 0.12.7 as global and local node version and 2.11.3 as global and local npm version.
i got this when i ran a gulp task
 gulp build -e production
11:12:00.455 0ns    0ns    nodist:shim-node - current target directory: C:\Program Files (x86)\Nodist\bin\node_modules\gulp\bin
11:12:00.456 976us  976us  nodist:shim - getTargetEngine: targetDir: C:\Program Files (x86)\Nodist\bin\node_modules\gulp\bin
11:12:00.456 0ns    0ns    nodist:shim - getTargetEngine: ReadFile C:\Program Files (x86)\Nodist\bin\node_modules\gulp\bin\package.json
11:12:00.457 976us  976us  nodist:shim - getTargetEngine: ReadFile C:\Program Files (x86)\Nodist\bin\node_modules\gulp\package.json
11:12:00.457 0ns    0ns    nodist:shim - parsePackageJSON: {Engines:{Npm: Node:>= 0.9}}
11:12:00.457 0ns    0ns    nodist:shim - Target engine found:'>= 0.9'
11:12:00.457 976us  976us  nodist:shim-node - Current version spec: >= 0.9
11:12:00.458 976us  976us  nodist:shim - checking 6.3.1 against >= 0.9
11:12:00.458 976us  976us  nodist:shim-node - found matching version: 6.3.1
11:12:00.458 0ns    0ns    nodist:shim-node - Determined architecture: x64:%!s(bool=true)
11:12:00.458 0ns    0ns    nodist:shim-node - Going to execute the following binary: C:\Program Files (x86)\Nodist/v-x64/6.3.1/node.exe
(node:9684) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
D:\work\masterproject\client\project\node_modules\gulp-sass\node_modules\node-sass\sass.js:22
  throw new Error('`libsass` bindings not found. Try reinstalling `node-sass`?');
  ^

Error: `libsass` bindings not found. Try reinstalling `node-sass`?
    at requireBinding (D:\work\masterproject\client\project\node_modules\gulp-sass\node_modules\node-sass\sass.js:22:9)
    at Object.<anonymous> (D:\work\masterproject\client\project\node_modules\gulp-sass\node_modules\node-sass\sass.js:25:15)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (D:\work\masterproject\client\project\node_modules\gulp-sass\index.js:3:13)

running a nodist env 0.12.7
solves the issue  and i get this output:
 gulp build -e production
11:20:20.138 0ns    0ns    nodist:shim-node - current target directory: C:\Program Files (x86)\Nodist\bin\node_modules\gulp\bin
11:20:20.138 0ns    0ns    nodist:shim - NODIST_NODE_VERSION found:'0.12.7'
11:20:20.139 960us  960us  nodist:shim-node - Current version spec: 0.12.7
11:20:20.139 0ns    0ns    nodist:shim - checking 6.3.1 against 0.12.7
11:20:20.139 0ns    0ns    nodist:shim - checking 5.11.1 against 0.12.7
11:20:20.139 0ns    0ns    nodist:shim - checking 0.12.7 against 0.12.7
11:20:20.140 976us  976us  nodist:shim-node - found matching version: 0.12.7
11:20:20.140 0ns    0ns    nodist:shim-node - Determined architecture: x64:%!s(bool=true)
11:20:20.140 0ns    0ns    nodist:shim-node - Going to execute the following binary: C:\Program Files (x86)\Nodist/v-x64/0.12.7/node.exe

looks to me that it ignores the global and local selected version of node and picks the latest one available.

Hi again,
this is a bug similar to the last one. The relevant lines in the debug output are:
11:12:00.457 976us  976us  nodist:shim - getTargetEngine: ReadFile C:\Program Files (x86)\Nodist\bin\node_modules\gulp\package.json
11:12:00.457 0ns    0ns    nodist:shim - parsePackageJSON: {Engines:{Npm: Node:>= 0.9}}
11:12:00.457 0ns    0ns    nodist:shim - Target engine found:'>= 0.9'
11:12:00.457 976us  976us  nodist:shim-node - Current version spec: >= 0.9

Unfortunately gulp specifies very loose node version constraints, allowing anything greater than 0.9. Sadly 6.x also matches these criteria, hence your error. You can manually run nodist env x.x.x, as you have done already. The package.json inspection definitely needs some conceptual polishing. Perhaps I will disable it entirely for globally installed modules.

Package.json inspection is now disabled by default, to avoid problems akin to yours. This fix has landed in v0.8.5.


Revert Get-ResourceFriendlyName to return friendly name again

At some point after the initial migration commit, the Get-ResourceFriendlyName stopped returning the friendly name. The current function does not reference the $ModulePath parameter.
This PR just adds back the lines present in the Initial Migration commit.

This change is

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

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


feat(httproute): add ReferenceGrant watch

What this PR does / why we need it:
This PR adds a watch for ReferenceGrant in HTTPRouteController.
With this change when a ReferenceGrant is deleted, the HTTPRoute gets its status update with a condition: type: ResolvedRefs, reason: RefNotPermitted and status set to "False".
Which issue this PR fixes:
Related: #3289
Apart from the above this will also make us pass this conformance test (yet to merged): https://github.com/kubernetes-sigs/gateway-api/pull/1853

Actually let me add a test for that


The documentation for KV Store is misconfigured

Expected Behavior
See:

https://github.com/kestra-io/docs/edit/develop/content/docs/13.terraform/resources/kv.md
https://github.com/kestra-io/docs/edit/develop/content/docs/13.terraform/resources/kv.md

instead of:

it should be --> see correct rendered version in the comment:

title: kestra_kv
editLink: false
description: |-
Manages a Kestra KV Pair.
kestra_flow (Resource)
Manages a Kestra KV Pair.
Example Usage
resource "kestra_kv" "new" {
  namespace = "company.team"
  key       = "my_key"
  value     = "Hello World"
  type      = "STRING"
}

Schema
Required

namespace (String) The flow namespace.
key (String) The key of the KV pair.
value (Multiple) the value of the KV pair.
type (String) the type of the value. Can be a string, number, boolean, datetime, date, duration, or JSON.

done


post handouts

we should post the exact bundles that were used in case the docker stuff changes slightly and people can't reproduce the exact binaries they saw on stream

Solved by @CouleeApps with https://github.com/Live-CTF/LiveCTF-DEFCON30/releases/tag/defcon30


FluentJson.Knockout.ToViewModel(model) where Model is a Mock

I get a AmbiguousMatchException when trying to use a mock in place of a real model when using fluentjson.knockout.toviewmodel.

Will take a look, do you have any code samples? Which mocking framework? Moq?

I did find an issue with circular referencing caused by Moq, but didn't run up on this error.  One issue I've noticed is that the metadata provider will pull data on all properties, even of subtypes, which in most cases is desired, but not always.
Mocking frameworks sometimes add a bunch of properties that aren't really meaningful to be serialized.  So I probably need to add a flag to exclude subtype properties.


devices with 0KB traffic and $0.0 won't show up

devices with 0KB traffic and $0.0 won't show up

This line is reponsible for that. A device that has 0 Byte of total traffic will not be inside the report.


JS/TS language services keeps crashing

JS/TS language services keeps crashing. I'm using codespaces, and it keeps crashing. I'm using a 2-core 16GB RAM 32GB storage machine. It used to run smoothly with no problem just yesterday. Unfortunately, just today, it has kept crashing and is barely workable. I've also tried disabling extensions, and even restarting my computer. I suspect that codespaces is too heavy for my physical device-- 2GB RAM, Intel Celeron N3050, 32GB Storage, outdated Windows 10 x64
Version: 1.92.2
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

2GB RAM

Is this the machine where the code space is running, or the machine you are connecting from?


Cannot resolve 'HotChocolate.Execution.Processing.OperationContext'

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Executing any request against a GraphQL server running the latest preview yields the following error:
System.InvalidOperationException: Cannot resolve 'HotChocolate.Execution.Processing.OperationContext' from root provider because it requires scoped service 'HotChocolate.Execution.DependencyInjection.IFactory`1[HotChocolate.Execution.Processing.DeferredWorkStateOwner]'.

Steps to reproduce
I just switched over a working project of the latest v12 to the latest preview version and noticed this error. Couldn't narrow it down to any wrongdoing in our application code.
Relevant log output
System.InvalidOperationException: Cannot resolve 'HotChocolate.Execution.Processing.OperationContext' from root provider because it requires scoped service 'HotChocolate.Execution.DependencyInjection.IFactory`1[HotChocolate.Execution.Processing.DeferredWorkStateOwner]'.
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteValidator.ValidateResolution(Type serviceType, IServiceScope scope, IServiceScope rootScope)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
         at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
         at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
         at Microsoft.Extensions.ObjectPool.DefaultObjectPool`1.Create()
         at Microsoft.Extensions.ObjectPool.DefaultObjectPool`1.Get()
         at HotChocolate.Execution.Pipeline.OperationExecutionMiddleware.ExecuteOperationAsync(IRequestContext context, IBatchDispatcher batchDispatcher, IOperation operation)
         at HotChocolate.Execution.Pipeline.OperationExecutionMiddleware.InvokeAsync(IRequestContext context, IBatchDispatcher batchDispatcher)
         at HotChocolate.Execution.Pipeline.OperationVariableCoercionMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.OperationResolverMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.OperationComplexityMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.OperationCacheMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.DocumentValidationMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.DocumentParserMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.DocumentCacheMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.TimeoutMiddleware.InvokeAsync(IRequestContext context)
         at HotChocolate.Execution.Pipeline.ExceptionMiddleware.InvokeAsync(IRequestContext context)

Additional Context?
No response
Product
Hot Chocolate
Version
13.0.0-preview.28

Had this issue myself. Was able to narrow it down to the environment variable ASPNETCORE_ENVIRONMENT in the launch profile in launchSettings.json

If this value is set to Development, the issue occurs. If the value is anything else or missing, the project works fine. Not sure how helpful this information is, but posting just in case it can help point in the right direction :)
Was able to reproduce with both launch types below, both have the issue when the environment variable is set, and both work without.

Thanks for your feedback ... we are currently working on fixing this issue.

Hope this gets prioritized as It makes all the preview versions after 13.0.0-preview.24 unusable

This is fixed in the latest preview.

We no longer support netcore 3.1 for Data since the final release of 13 will be somewhere in December netcore 3.1 will be out of support. Full support of all 13 features is now only available with net 6 and net 7.


[Bug]: Camera widget is unable to capture high quality images

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When using camera widget, the image resolution is low which leads to blurred images
Steps To Reproduce

Add a new camera widget
Take a photo from phone
Observe the resolution of images is lower than expected.

Public Sample App
No response
Version
Production

I linked the native app with a separate web view.
https://blog.naver.com/spring1a/222863510106
https://washswat.slack.com/files/U03K2BQBA64/F04285V5XDE/screen_recording_20220901_000251__1___1_.mp4


Please add to documentation

Uncomment  in config.yml:
translator:      { fallback: %locale% }

See above.


align with FMS submission: add gene_synopsis, make gene_type required

Simple changes to bring LinkML model in line with agr_schemas model.

Add gene_synopsis slot (a simple string).
Make gene_type/gene_type_curie (aka soTermId, gene biotype) a required slot for Gene/GeneDTO classes

I want to handle gene genomic locations in a separate PR.

@gildossantos This looks OK, but I'd like to point out that the mechanism for gene descriptions we worked out with the gene descriptions group was to submit various description types as related_notes with an appropriate note_type for each type of description. If you check the "Gene Related Note Type" vocabulary in the curation tool:
https://curation.alliancegenome.org/#/vocabterms
We already have note types "automated_gene_description" and "MOD_provided_gene_description" for the gene description group use cases, in addition to the gene note types requested by SGD:
gene_regulation_summary gene_disease_summary gene_protein_summary gene_interaction_summary gene_function_summary gene_phenotype_summary gene_sequence_summary
We probably don't want to have multiple different ways of attaching a gene description, so we may want to either forgo the "gene_synopsis" slot OR discuss a different approach with the gene descriptions and gene working groups.

@chris-grove That makes sense. I removed the gene_synopsis slots. In the Gene notes, I added some explanation on the mapping of FMS BGI geneSynopsis and geneSynopsisUrl to LinkML slots that I think will be helpful to DQMs, at least during the FMS-LinkML transition. I added note_dtos to the GeneDTO slot to allow for notes submission.


Support for PaloAlto FWAAS.

@ashutosh-mishra @njagadish @chenchenWang @songole
This is a pull request for palo alto firewall driver support
added Feature:
orchestration:

added support in nfp node driver to pick paloalto firewall service
no hotplug support.
no sharing support.

configuration:

create_interface: create ip on the static interface
create_route: creates pbr rule to route traffic from provider to stitching
create_firewall: creates firewall rules
delete_firewall: deletes firewall rules

FYI - we are depending on a paloalto related python library called "python-pan" which can be installed using either pip or through git clone: https://github.com/kevinsteves/pan-python. Was not sure on how we handling driver dependency packages. @songole suggested when we are doing rpms we can install this library when the rpm is installed. for now we can put it in run.sh in the configurator image.

@rayalaman - Discuss with @DhuldevValekar for how to install this dependency

@ashutosh-mishra yes we decided to do a git clone of the pan-os when when we do image builder of the configurator vm.

@njagadish - changes are fine

Closing this as it got merged as part of 03 June PR


Divide By Zero error with English inputs

for English input, I noticed a divide by zero error today and caught it by limiting all numbers smaller than 1e-17 to 1e+17. I'm not sure which word exactly caused the error, though.
https://github.com/summanlp/textrank/blob/985402e621b8f34825bc423a952beeb97e74c0e0/summa/pagerank_weighted.py#L74 .

I double-checked just now, the error does not exist on the current git version of textrank, but only version 0.0.7. Please disregard this ticket.


Tool Button Icon Tips

Add Icon Tips for all tool buttons.  Kearey will provide you with a list of Tool Tip Titles for the application.

https://angular-ui.github.io/bootstrap/#/tooltip?


Fix/macro audit 15

Fix findings found in Macro Audit 15.

So the reason why I didnt want to go with another version of the share price oracle contract, is so that we dont need multiple versions of cross chain share price oracles, we will just need 1. Also I think it is likely that mainnet oracles relaying an L2 cellars share price will use this logic in them to check the state of the L2 sequencer.
As for adding a real test, I think having a mock one is fine since mimicing the state of the real data feed is so easy. Plus the last arbiturm outage was not properly recorded by the sequencer uptime feed.


Hot-Reloading SSL cert

Functionality - Backport Hot Reload SSL configuration to <IP_ADDRESS> and below
This will enable users to reload nodes certificates without restarting elasticsearch

Test Result
Tests run: 55, Failures: 0, Errors: 0, Skipped: 17
There is one failure test, but that has been there before this commit


Self-exams: waiting after finding

added:

new column to keep waiting due date (+56 days now)
scheduled daily task to closing the waiting and switch to waiting for the finding result

koukam, ze ta confirm funkce je dobre dlouha...  pokusim se to jeste zitra nejak rozpadnout.


error: [vite:dep-pre-bundle] Failed to resolve entry for package "@vue/runtime-dom".

same issue：https://github.com/vitejs/vite/issues/2883
win10
node 14.15.3
pnpm 6.0.0
npm run example:dev
error: [vite:dep-pre-bundle] Failed to resolve entry for package "@vue/runtime-dom".

In pnpm v6 it use # in folder name, vite will get confuse with that, keep track on vitejs/vite#2883, will close this one because it's not related to this repo.


Problem on running the install step

The document has the install step:
https://ml-in-barcelona.github.io/server-reason-react/local/server-reason-react/intro.html#install
But when running opam install server-reason-react
The following error appears:
[ERROR] No package named server-reason-react found.
Is it available at opam? Is the documentation right?

It's currently not available in opam, and should be installed with a pin. Let me update the instructions.
opam pin add server-reason-react.dev "https://github.com/ml-in-barcelona/server-reason-react" -y

Updated the documentation in https://github.com/ml-in-barcelona/server-reason-react/commit/dc38221e4de0ad21d209d855217c61fbfe46de6c
Thanks for reporting. Feel free to open as many issue as you find :D


Use of FastTermTermMap for acceleration with caching

Not yet complete

This might have made it a bit slower :( .
Hard to judge without performance measures.
I need to add this next before making any changes for the program optimization.

Hopefully a lot of times once some performance bugs in the code are fixed

The parser takes 20% of all time in the performance tests - this has to wait till the parser is way faster.

There is no measurable improvement because it seems to be below the noise - I don't like to check it with a CPU with disabled turboboost and hyperthreading without any apps running


feat(Drawer): add show-footer Props

Types of changes

[x] New feature
[ ] Bug fix
[ ] Documentation change
[ ] Coding style change
[ ] Component style change
[ ] Refactoring
[ ] Performance improvement
[ ] Test cases
[ ] Continuous integration
[ ] Typescript definition change
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

drawer
新增属性 footer
add property  footer

Checklist:

[ ] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[x] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

@jekip 感谢PR，周五发版的时候会merge进去


[YouTube] JSON subtitles not included

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.12.09. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.12.09

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl --skip-download --print-json --list-subs 'https://www.youtube.com/watch?v=RgKAFK5djSk' -v
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--skip-download', '--print-json', '--youtube-skip-dash-manifest', '--list-subs', '--no-playlist', 'https://www.youtube.com/watch?v=RgKAFK5djSk', '-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.12.09
[debug] Python version 3.5.2 - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.2, ffprobe 3.2, rtmpdump 2.3
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Description of your issue, suggested solution and other information
Subtitles are not included in the JSON response when using "--list-subs". The only workaround I found was to use "--write-subs" but this way they are also saved in the working dir and I don't want any files to be downloaded (--skip-download).

No JSON output is supposed to be written at all when --list-subs is used,

I see. OK, how to get a JSON response with all the media files and the subs?


Recommended way to monitor sealed/unsealed status?

I have a vault-operator-installed cluster that I'm monitoring with Prometheus.  The StatsD exporter provides some metrics, but I am looking for a way to track the number of sealed/unsealed vault instances.  (For example: I'd like to trigger an alert when a certain number of nodes are unsealed.)
I know that vault-operator keeps the VaultService resource's "status" section up to date with this information, but I haven't found a convenient way to get this information into Prometheus.
I've found the vault_exporter tool, perhaps that can be installed as a sidecar alongside the StatsD exporter?

@cpick - the Banzai Cloud Vault operator does monitor this (and other stuff as well), with charts, etc included. You might want to check this post: https://banzaicloud.com/blog/monitoring-vault-grafana/

I created PR #347 with the solution I landed on.
@matyix if we didn't already have a CoreOS vault-operator installation and we were installing from scratch I think we would go with Banzai Cloud Vault operator.  It seems to be more feature complete and, more importantly, actively maintained :(


feat: init ovfs

Initialize ovfs project.

Hi, @Xuanwo, is there anything else should be added in this PR.

is there anything else should be added in this PR.

I prefer to remove code rather than add more... :smile:

It's ready for review now.


Pattern changes are not immediately reflected

For things like credit cards the pattern needs to be updated on the fly. E.g. if an amex card is detected that uses a different pattern to visa for example.
Currently MaskedInput doesn't use setPattern to update the pattern when it changes so changing the pattern dynamically results in no changes.

+1

+1

What should we do with the existing value when setting the pattern?
Default is currently to attempt to pass on the current raw value.

@insin I've just gotten around to testing this out and it's looking pretty good!
Fwiw all examples are using braintree's test card numbers
My use case is updating a credit card pattern to different card format as the input is entered/pasted etc.
Starting with a visa pattern e.g. 1111 1111 1111 1111 entering this is fine: 4111 1111 1111 1111
If I start over (with the pattern being visa by default) if I start typing '37' to get the amex detection on my card input to change the pattern I end up with the new pattern, but the caret is at the end. E.g. typing 37 gives me:  37__ ______ _____.
Starting over with an empty field if I paste in an amex number e.g.<PHONE_NUMBER>98431 then the pattern is correctly updated to 1111<PHONE_NUMBER>1 which is excellent - and what I'd hoped getRawValue() would help with.
The only nit is the caret is at the start of the string, post pattern change.
When pasting back the longer visa example: 4111 1111 1111 1111
The field ends up with this:
4111 1111 1111 111_
Again the caret is at the start of the inputted string. Ideally I could paste 4111 1111 1111 1111 and get 4111 1111 1111 1111 but I can see dealing with the pattern change around the paste will be tricky.

@muffinresearch I created a component that will help you.
https://github.com/andrevvalle/react-mask

@insin I've been looking at  PR #9 by @Philmod. With one small change it looks to address most of the issues I descibed above wrt selection above.
The only case that still doesn't work is going from the shorter pattern to a longer one. Not losing part of the pasted string is going to be hard. But if the selection could be in the right place I think we're close enough to something releasable.
I'll add some comments to the PR.


can't select specific test case in v0.31.1

Hello, I am unsure if this is a bug or just missing from current release but,
I'm using ceedling v0.31.1 installed through gem.
I've tried adding to the project.yml
:test_runner:
  :cmdline_args: TRUE

and
:defines:
  # in order to add common defines:
  #  1) remove the trailing [] from the :common: section
  #  2) add entries to the :common: section (e.g. :test: has TEST defined)
  :common: &common_defines
    - UNITY_USE_COMMAND_LINE_ARGS

Then I call
ceedling test:FILE --test_case=<test case name>
But it just runs all tests in FILE. No matter what I write in test case or no matter which argument I use it just seems too ignore it all together.

You mean that worked in some previous version but it doesn't work anymore?

I have never tried using ceedling in a previous version
On Thu, 7 Dec 2023, 21:33 Crt Mori, @.***> wrote:

You mean that worked in some previous version but it doesn't work anymore?
—
Reply to this email directly, view it on GitHub
https://github.com/ThrowTheSwitch/Ceedling/issues/832#issuecomment-1846145031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWXYX4IGWSQAXOLZ6BDSRDYIIY3VAVCNFSM6AAAAABALPET7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBWGE2DKMBTGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

So this is feature request, to execute a single test case out of a test file?

The feature is mentioned in the docs but now I realize this is not in the v0.31.1 docs
I guess I'll need to try a release candidate

Sorry, I was not aware of the feature.
FILE I assume is without path, without test_ and .c, while testcase is also without test_ prefix?

yes I've tried multiple combinations. FILE always been without the path and just the module name otherwise it doesn't even run.
the testcase I've tried multiple combinations. With test_, without test_ and other substrings.
It always runs the entire FILE test cases

@Letme this is related to #831


find uv binary relative to package root

Summary
ruff's find_bin implementation can find the binary in relative to the package root. It'd be nice to have the same functionality for uv.

And welcome to the project :)

Thank you! Good to be here


AssertAssignableInstr::Canonicalize sometimes creates checks against TypeRef which runtime can't handle

In the optimized version of the function f from the reproduction below compiler ends up generating AssertAssignable:6(v3, TypeRef: B<...> (@0xf5d8f331 Hefbb15c), 'field' instantiator_type_arguments(v0)) because AssertAssignableInstr::Canonicalize replaces destination type of the original AssertAssignable against type parameter with whatever InstantiateFrom returned (and it returns TypeRef). However Instance::IsInstanceOf (which is called in the runtime function TypeCheck) apparently can't cope with dst_type being  TypeRef - it returns false even though it would return true if we unwrap the ref.
Either optimizing compiler needs to take care and unwrap TypeRef when canonicalizing or runtime system must be able to cope with TypeRefs passed to IsInstanceOf.
Note: this issue causes flakiness on the dart2js buildbot.
/cc @whesse @asgerf @rakudrama @fsc8000 @crelier
// VMOptions=--enable_asserts --enable_type_checks --enable-inlining-annotations --optimization-counter-threshold=10

const AlwaysInline = "AlwaysInline";
const NeverInline = "NeverInline";

abstract class A<T extends A<T>> {
  @AlwaysInline
  m(x) => new R<T>(x);
}

class B extends A<B> {}

class R<T> {
  @AlwaysInline
  R(T field);
}

class C extends B {}

class D extends C {}

// Method A<T>.m will be inlined and T=B will be forwarded to AssertAssignable in the
// R. However B will be wrapped in the TypeRef which breaks runtime TypeCheck
// function (Instance::IsInstanceOf does not work for TypeRefs).
@NeverInline
f(o) => new B().m(o);

main() {
  final o = new D();
  for (var i = 0; i < 10; i++) {
    f(o);
  }
}

$ out/DebugIA32/dart --enable_asserts --enable_type_checks --enable-inlining-annotations --optimization-counter-threshold=10 test.dart
Unhandled exception:
type 'D' is not a subtype of type 'B' of 'field'.
#0      R.R (file:///usr/local/google/home/vegorov/src/dart/sdk/test.dart:16:7)
#1      A.m (file:///usr/local/google/home/vegorov/src/dart/sdk/test.dart:9:15)
#2      f (file:///usr/local/google/home/vegorov/src/dart/sdk/test.dart:27:17)
#3      main (file:///usr/local/google/home/vegorov/src/dart/sdk/test.dart:32:5)
#4      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:261)
#5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

Fixed in b2994a4f556a13d6420b122a97ceef739f427653 by unwrapping TypeRef in the optimizer.


contains<C>(_:) does not behave as expected

Because this is defined on Collection it is available to all Collection types, not just String. The behavior on other types is odd at best. It isn't even predictable when working with a Set. I think it should either be fixed to behave as expected, or narrowed down to just work on String?
Attached is an example playground to experiment with which demonstrates the issue.
Contains.playground.zip

For collection types like Set and Dictionary that are semantically unordered (i.e. their order isn't guaranteed to be the same each time you run a program), any API that requires semantic ordering won't really be usable. The same is true for standard library collection algorithms like starts(with:) and equalElements(_:).
For ordered collections, like strings, arrays, buffers, and many of the collection types in swift-collections, the contains method works just as you'd expect.


modified gles icons

I tweaked both gles2 and 3 svg, the result is not finalized yet.

I couldn't notice what's different with attached image.
Here is closer look.

My old eyes dont see a significant difference. I would remove the line, it does not match the font style. According to Wikipedia, it's okay to write GLES` as one word: https://en.wikipedia.org/wiki/OpenGL_ES

According to Wikipedia, it's okay to write GLES as one word: en.wikipedia.org/wiki/OpenGL_ES

It's a trademarked logo, it's probably not a good idea to modify it too much.

The logo is already very different ;)

Yes, you can't cut part of logo and think it will still work.

I am good as long as that line is fixed, be it deleted or modified, just need a conclusion :)

I am good as long as that line is fixed, be it deleted or modified, just need a conclusion :)

That's the hard part, I'm already out of smileys :)

I don't get why there is such a fuss about a pipe in a logo, but I don't care either way. If you guys prefer a slightly different logo or plain text, it's fine by me.

I don't get why there is such a fuss about a pipe in a logo, but I don't care either way. If you guys prefer a slightly different logo or plain text, it's fine by me.

The designer part of my brain doesn't get why someone would cut a piece of a logo and pipe it somewhere, but I see many worse things every day.

Well so be it, let's go with plain text. Superseded by #22027.


Updated faraday dependency

To use latest and always latest faraday to avoid any http bugs that were fixed in faraday library.

Coverage remained the same at 95.858% when pulling ba39b5665d2dd5a10bfce341b3ab91ee97ae2f81 on nazarhussain:master into 96daaf56765652a5ffc792f645f6b3a4a42ce9bb on intridea:master.

All test seems to be failing on RubyCop syntax check. Is it normal, as I didn't make any change in to code.


Bar Chart Not Showing All xAxes Labels

I'm now facing this problem where I didn't see any solution around the community. Please check this links.
Issue:
https://github.com/jtblin/angular-chart.js/issues/423
JSFiddle:
https://jsfiddle.net/gnns7wbn/1/
Problem Summary:
Not all the labels are showing until you resize your browser.

The post you links to says to use autoskip: false. Did you try that?


Client and server apps must have same Application.productName for auto-discovery to work

As the Transport uses Application.productName as a means of validating whether an auto-discovery request should be processed, apps that have different product names will always fail discovery.
I found this out when testing two related client and server apps, one with 'Client' appended to the product name and the other with 'Server'. As you already have to provide a shared discovery key to validate an auto-discovery request, is this not a redundant restriction to place on apps, perhaps?

This is to prevent different software using the same networking library from trying to connect to each other, having the library take care of this is much more convenient and intuitive than doing it yourself.
Also, if you're using Mirror, two separate projects for client and server won't work properly

Thanks for your quick response @MichalPetryka! I agree, it's definitely intuitive to have the library take care of validation for you, I'm just wondering if you need to use both the product name and the discovery token to validate requests? If you do, then could the transport be configured to use a different shared string instead of the product name?
I am building my client and server apps from the same project, but applying different product names at build time, so networking with Mirror is just fine, apart from this issue with auto-discovery.

Please make a PR adding a virtual method, that would return application name, but could be overrided and changed if you want.

Great, sure thing!


Added PHP 8.2 Version

Added Docker file for PHP 8.2
Added 'php82' placeholder in sample environment file, shell script or wherever needed.

Would be nice to approve this.

Hi @joaocosta-azores,
Thank you for approving but review is still required and the pull request is not yet merged.
Please review.
Thanks,

Hey there !
sorry for the delay. Thanks for contributing to the project. Looks good to me.


add to hackage

Hi, do you have plans to add this package to hackage soon?
I've written a package normalization-insensitive (essentially a clone of the case-insensitive package, but for normalization instead of case) which depends on unicode-transforms, but before I can put my package on hackage, its dependencies need to be on hackage first.
Thanks!

I essentially created this package to fix commercialhaskell/stack#1810 . I do have plans to put it on hackage but held it for two reasons:

I have been playing with Haskell implementation of normalization. I have got that to work faster than the C implementation that this package is using currently. I thought I would upload it to hackage once I am done with that. But as along as the API remains the same it should not matter.
I was wondering if it would make sense to integrate the haskell implementation in the text package itself (bos/text#148) rather than creating a separate package. But I don't know whether that can happen anytime soon since I have not got any update on that issue yet. Maybe I should think about it only after I am done with the Haskell implementation.

How soon do you need it? Can I have a look at your package?

Thanks for the info!
I don't have any specific timetable; I was just curious what your plans were.
I've pushed my repository to ppelleti/normalization-insensitive, so you can view it there.  It's a pretty direct port of basvandijk/case-insensitive.  I still have some work to do, such as porting the benchmarks.
Currently, I'm using normalization-insensitive in a personal project that involves synchronizing files between my Android phone and my Mac laptop.  Linux (and thus Android) uses NFC in its filesystem, and Mac OS X uses NFD in its filesystem, so in order to accurately determine which files correspond, I must do normalization insensitive comparison.
I'd just thought normalization-insensitive might also be useful to other people, but I'm not in any particular hurry to release it.

That looks cool! I wanted something like that. The only thing I found earlier was text-normal, your approach seems more general and works for all string like data types. I think it will be very useful. In fact that's the way most end users should be using normalization.
BTW, was there a specific reason for choosing NFKD over NFD or NFC?
I will try to put my package on hackage soon. We can switch the underlying implementation to Haskell even later as long as the API remains the same.
Maybe at some point all the unicode related packages should be consolidated to make it easier for the users.

No, there wasn't a compelling reason to choose NFKD, and I'd be happy to change it to one of the other forms, but my reasoning was like this:

I chose NFKD over NFD because my understanding is that NFKD normalizes a few additional "compatibility" code points, such as ligatures.  But my logic was just that it might be helpful, and shouldn't hurt anything.  I'm not using any compatibility code points myself.

I chose NFKD/NFD over KFKC/NFC on the thought that the sort order might be a little more sane in decomposed form than in composed form.

But both of these are fairly weak reasons.  And I haven't benchmarked the various normalization forms to see which is fastest.  That could be a more compelling reason to choose one over the other.
I'm certainly open to changing it, though, and would welcome any thoughts you have on the matter.

[Unicode website] (http://unicode.org/faq/normalization.html) suggests NFC for most use cases. There is no sort order in composed forms. In decomposed forms normalization has to always keep the combining chars sorted in a canonical order, so that does not matter either.

OK, I switched it to NFC.  There is still a sort order, though, because the Ord instance is necessary to use normalization-insensitive strings in sets and maps, which I consider to be one of the main use cases.  This ordering leaks out to the user a little bit, if you print the set or map in order.

Ah! I completely misunderstood sort order earlier. I was thinking about the ordering of the combining chars for normalization. My bad. Yeah the sorting order of strings will depend on the normalization form since we are sorting on individual char values.

I created a REL0.1 branch for uploading to hackage. Please take a look. I have changed Data.Unicode.Normalize to Data.Unicode.Types, you will need to make corresponding changes at your end. I tested it on Linux/mac/windows with ghc 7.8/7.10/8.0. Try this with your package and I will upload if all works well.

I uploaded a candidate tarball here https://hackage.haskell.org/package/unicode-transforms-<IP_ADDRESS>/candidate. Can you try that?

I've tried your candidate tarball with my package with ghc 7.8, 7.10, and 8.0, and it all looks good.

Thanks, I will wait a couple more days and then publish it.

version <IP_ADDRESS> is on hackage - https://hackage.haskell.org/package/unicode-transforms .


USD as base rate on Free?

Can someone confirms this still works for US merchants with a base rate of USD?
In reviewing the docs on Fixer.io it states:
"Minor limitations include our new 1000 requests/month limit and ***EUR being the only available base currency for customers using a free account."
If true, $10/mo a little steep for a currency changer and need a different solution.

This may be true but I haven't looked into it.
Yahoo has a solution that M2.1+ integrates with natively.
On Sun, Jun 10, 2018 at 3:09 PM Alex<EMAIL_ADDRESS>wrote:

Can someone confirms this still works for US merchants with a base rate of
USD?
In reviewing the docs on Fixer.io it states:
"Minor limitations include our new 1000 requests/month limit and ***EUR
being the only available base currency for customers using a free account."
If true, $10/mo a little steep for a currency changer and need a different
solution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/philwinkle/Philwinkle_Fixerio/issues/28, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAj-7uiJsuBx8ZSBHflospQpMMfVXv-Lks5t7W74gaJpZM4Uh1Xh
.

--
Follow me on Twitter - @philwinkle
Listen to MageTalk, the Magento Community Podcast! http://magetalk.com

Migrating to m2 for the currency updates not economical

I'm making the point that the service exists, I'm not suggesting that you
migrate to M2. You could integrate with that instead - or you could pay for
Fixer.
On Sun, Jun 10, 2018, 6:51 PM Alex<EMAIL_ADDRESS>wrote:

Migrating to m2 for the currency updates not economical
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/philwinkle/Philwinkle_Fixerio/issues/28#issuecomment-396088283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAj-7hR737E13RN6vjNCcY5v7yEYbvaBks5t7aMGgaJpZM4Uh1Xh
.

Eh. No good options there.
Last I heard Yahoo had shut down their API last year
$120/yr to update rates via Fixer not worth it. Better to just shut off the changer
I'll post what Fixer says on the EUR base rate only policy.

Update: If you already had an account with Fixer.io prior to the change you can get a Legacy Plan
This plan comes with free SSL support and the ability to change base currency

Can someone confirms this still works for US merchants with a base rate of USD?

This should work for all currencies.  I worked on that part specifically to keep the service free for everyone and tested the accuracy:
Review the details of https://github.com/philwinkle/Philwinkle_Fixerio/issues/22
This also has brought up a few things I should update:

Documentation
Scheduling updates.


Not processing zurb foundation RGB mixin

I'm getting this error when trying to compile foundation for sites sass.
Module build failed:
  $rgba: red($color), green($color), blue($color);
        ^
      Argument `$color` of `red($color)` must be a color

Backtrace:
	node_modules/foundation-sites/scss/util/_color.scss:19, in function `red`
	node_modules/foundation-sites/scss/util/_color.scss:19, in function `color-luminance`
	node_modules/foundation-sites/scss/util/_color.scss:44, in function `color-contrast`
	node_modules/foundation-sites/scss/util/_color.scss:63, in function `color-pick-contrast`
	node_modules/foundation-sites/scss/components/_badge.scss:59, in mixin `foundation-badge`
	node_modules/foundation-sites/scss/foundation.scss:84, in mixin `foundation-everything`
	stdin:16
      in /Applications/MAMP/htdocs/site/node_modules/foundation-sites/scss/util/_color.scss (line 19, column 10)

 @ ./resources/assets/manager/scss/manager.scss 4:14-257
 @ multi ./mix-entry.js ./resources/assets/manager/scss/manager.scss

Any ideas on the cause?
Cheers

Is this related to your issue?
Cheers
Kev


Installation clickhouse_fdw

Hi! Command "cmake .." completed with error: "CMake Error at src/CMakeLists.txt:39 (target_compile_features):   target_compile_features specified unknown feature "c_std_11" for target
"clickhouse_fdw"". Which C/C++ compilers is better for clickhouse_fdw? ALT Linux, postgresql11, gcc5, gcc5-c++, libcurl, libuuid are installed on server.

Could you try to remove that line?

When I removed this line: "target_compile_features(clickhouse_fdw PRIVATE c_std_11)" at src/CMakeLists.txt:39, command "cmake .." completed without errors but next command "make" completed with great amount of errors: "This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the
-std=c++11 or -std=gnu++11 compiler options".
Current version gcc is x86_64-alt-linux-gcc (GCC) 5.3.1. I'm reading, GCC 4.8.1 was the first feature-complete implementation of the 2011 C++ standard: https://gcc.gnu.org/projects/cxx-status.html#cxx11. Therefore, I beleive I must have not any problems.
File build/CMakeFiles/CMakeOutput.log contains next lines:
Detecting CXX [-std=c++1] compile features...
/usr/bin/gcc -std=c++11 -o ...
Can you recommend how to force "cmake" correctly execute a line "target_compile_features(clickhouse_fdw PRIVATE c_std_11)"?
I'm not a programmer for Linux unfortunately, I'm afraid I will be to solve a problem too long. I will be to google "cmake target_compile_features c++11" and to learn recommendations.

I've some changes, could you try to recompile the extension?

Yesterday I solve this problem. Version of cmake must be 3.8+ but  file src/CMakeLists.txt check version 3.5 minimum. I install cmake 3.6.3 earlier but this version not support future c_std_11. Yesterday I install cmake 3.16, gcc 7 (minimum 6.3 for c++14) and commands cmake, make, "make install" are completed succesfully.
Whether I install your "some changes" again?

Not sure if I have understood your question. The compilation should be fixed in latest commit, but if everything works on your side now, there is no need to do anything.

I execute command:
create extension clickhouse_fdw
ERROR: load library "/usr/lib64/pgsql/clickhouse_fdw.so" :
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib64/pgsql/clickhouse_fdw.so)
ls -l /usr/lib64/libstdc++.*
lrwxrwxrwx 1 root root      19 dec  9 11:47 /usr/lib64/libstdc++.so.6 -> libstdc++.so.6.0.21
-rw-r--r-- 1 root root 1545576 apr 22  2019 /usr/lib64/libstdc++.so.6.0.21
strings /usr/lib64/libstdc++.so.6.0.21 | grep GLIBCXX
GLIBCXX_3.4, GLIBCXX_3.4.1 - GLIBCXX_3.4.21
#apt-get install libstdc++6
not install new version
gcc --version
gcc (GCC) 7.3.1 20180712 (ALT p8 7.3.1-alt8.M80P.1)
its max version in p8
What to do?

This problem was solved successfully after I change repository and make full upgrade.


Do the same data consistency and validity checks inv1 and v2 compute_secret

v1::Party::compute_secrets checks for shares missing from a particular key_id, while v2 checks for shares missing for a particular key_id.
Split the MissingShares error into two separate errors, and check for both errors in v1 and v2.

I think this was fixed already by https://github.com/Trust-Machines/wsts/commit/47290393c9760b0d60b3ced231d6fe30173d27b1

I think this was fixed already by 4729039

We made progress on this in that commit, but PR #95 will do more!


Added support for using custom docker image

This adds the option of using a custom docker image. The main use case is adding libraries or packages required at compile time on top of the xgo provided images.

I've pushed quite a few commits out to support Android cross compilation too. Doing this however I made a merge conflict with your PR. I'd like to include this PR into the repo too, so would you be so kind as to rebase on top of the current head? Thanks :)

Rebased to master and adjusted the flag description.


Is that possible to do one_step forward in vllm?

I want to have one step forward and output only one token in each step like:
output = model.generate(prompt=prompt, past_key_value=past_key_value)
This is super important for streaming output. Is this possible in vllm?

I have same question.

LLM.llm_engine.step()


GNU tests are killed after 16 minutes & ~30 seconds

No clear error message
PASS: tests/split/line-bytes.sh
make[4]: *** Deleting file 'tests/split/l-chunk.log'
make[3]: *** [Makefile:21230: check-TESTS] Terminated
make[1]: *** [Makefile:21007: check-recursive] Terminated
make[4]: *** Deleting file 'tests/misc/sort-stale-thread-mem.log'
make[4]: *** [Makefile:21248: tests/misc/sort-stale-thread-mem.log] Terminated
make[2]: *** [Makefile:21490: check-am] Terminated
make: *** [Makefile:21492: check] Terminated

maybe github updated the run time period?

Example:
https://github.com/uutils/coreutils/actions/runs/3553735725/jobs/5969424031

I opened the question/bug here: https://github.com/orgs/community/discussions/40200

Closing this ticket as the GNU tests are no longer killed and the rollback to ubuntu-20.04 has been undone at some point.


Fix focus-visible for Safari

Fixes

Fixes #723  by @sarayourfriend
Description

Fixes focus-visible for Safari using a polyfill and a postcss plugin.
Testing Instructions

Checkout this branch and run it in Safari and verify that focus rings appear on elements that need them when focused via the keyboard (like buttons in the header).
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[N/A] I added or updated tests for the changes I made (if applicable).
[N/A] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb Is there a global root file for Nuxt? I couldn't really find one that is accessible to edit, that's why I placed it in the layouts 🤔

There has to be some level above the layouts. I'll dig through the docs.

If we can do that, it'll be great. But considering the a11y implications of completely forgetting about a browser, we could also merge this as a quickfix for now.

Well, either way we'll have to deploy the fix which probably won't happen for another couple hours anyway.
@zackkrida can you see any reason not to use a CDN version of the polyfill (provided we include all the appropriate integrity checks?)
We could use https://unpkg.com/focus-visible@5.2.0/dist/focus-visible.js?meta as we already rely on Cloudflare anyway.

I'm comfortable with unpkg + integrity checks, I don't see any issue there!

Went the plugin route that @obulat recommended. It's much more sensible!


Push Customer from OMS to NetSuite

We need to prepare a Customer CSV file with the following information.

External Id -> Shopify customer Id -> You can get this value from PartyIdentification
Individual -> T
First Name -> PartyDetail.FirstName
Last Name -> PartyDetail.LastName
status -> CUSTOMER-Closed Won
Phone -> TelecomNumber.countryCode + TelecomNumber.areaCode + TelecomNumber.contactNumber
Address -> PostalAddress.address1
City -> PostalAddress.city
State -> PostalAddress.stateProvinceGeoId
Zip -> PostalAddress.postalCode
Country -> PostalAddress.countryGeoId (We will have to transform country value from USA to US)
Addressee -> PostalAddress.toName
Default Shipping -> Yes
Default Billing -> Yes
Subsidiary -> 1

Note: We will get the Subsidiary value from the SystemProperty entity as this can be different on the NetSuite account.
When we prepare the feed for the customer, we will make a PartyIdentification entity record to filter out the customer which is already sent to NetSuite

Customer_Test.csv

As per discussion with Deepak sir, we will not send customer address information while making customer records on NetSuite as we don't store customer addresses on OMS.
Here is the final CSV information:

External Id -> Shopify customer Id -> You can get this value from PartyIdentification
Individual -> T
First Name -> PartyDetail.FirstName
Last Name -> PartyDetail.LastName
status -> CUSTOMER-Closed Won
Subsidiary -> 1

Customer_Test.csv

As per discussion with @dixitdeepak,

We will not send address details for the customer as OMS currently does not manage addresses for customers. - This looks good as it is added in the earlier comment as well.
For the External Id, I think it was discussed to use HC Party ID instead of Shopify customer Id.
In the scenario if some failure occurs to create PartyIdentification record in HC for the customer detail being sent to NetSuite, and the same External ID is sent again in the next feed, what is the expected behavior?

@rehan3586
Can you please check and confirm on points 2 & 3.

Hello @gurveenbagga,
#2. As per my last discussion with Aditya Patel, we decided to store shopifyCustomerId in PartyIdentfication instead of HC partyId because Celigo also uses shopifyCustomerId in the externalId of the customer. But we will discuss this once again with the team and finalize which id will be used.
#3. In that case, NetSuite will not create the record and return error 'Duplicate record exists' for the customer. This is expected behavior but we need to create a PartyIdentification record for the customer on the OMS side.

Here is the sample customer CSV file.
Customer_Test.csv

Hello @gurveenbagga,
Here is the SFTP location for the customer feed.
/home/{SFTP_USER}/netsuite/customer/export

This task has been completed and working as expected. So I am closing it.


Set material-components-web version < 4.0

Version 4.0.0 of material-components-web has BC breaks that cause this to stop working. 0.39.0 does work.
Requires reworking how MDCDialog is setup and initialised. MCDDialog.show() is now .open() but just changing the call in FriendlyEats.View.js isn't enough. Believe it needs all the lists shown in the dialog to be updated. I'm not familiar enough with MDC (nor will I be) to do all the updates.

Opened PR on wrong account


Pajek parser and writer for pangraph.

Support for a the pajek (.net) graph format. The pajek format is used by the Pajek program. A good description of the format can be found here

@zouroboros This looks great to me, many thanks! I've restarted the CI, since the failure looked like a glitch.
@thisiswhereitype Do you have any comments?

P.S.: The CI is now all green.

Thanks @zouroboros for your contribution, I am happy to merge this.


Own library!

@uarif @pratibha77118 @yasmensarhan27
Is it necessary to make own library for the unit test also?

I think if you don't make its own library, it will not be executed.  @tirthbha

Are you keeping your unit test code sepearte?

I mean it's a separate file, or you are keeping it inside the original cod?

@tirthbha  could you make it more clear what exactly mean making seperate library for unit test?

@uarif  No this is not for the unit test this one is just for the original code. However, you can do for the unit test in the similar way.

@uarif I have made for your code so its your library not mine. My library is different

@tirthbha could you make it more clear what exactly mean making seperate library for unit test?

You can see the examples that professor has shared to the second point in the task section of our HW3 for more detail.


Add sample usage of SetupAdd method

The test file provided as documentation does not include any sample usage of the SetupAdd method.
Would it be possible to add some examples?
A desirable test case could be:
Sample Implementation
var foobar = new Foobar();
_foobarContext.Foobars.Add(foobar);
await _foobarContext.SaveChangesAsync();

Sample Test
// Arrange
var context = new Mock<FoobarContext>();
// context.SetupAdd()

// Assert
context.Verify(c => c.Add(It.IsAny<Foobar>()), Times.Exactly(1));
context.Verify(c => c.SaveChangesAsync(It.IsAny<CancellationToken>()), Times.Exactly(1));

I added an example that should support your case UsersServiceTest.cs.
Please check if it works for you.

Thanks much!


Bundle references into components

Reason/Context
Currently, we inline the references inside the AsyncAPI document. However, I think the references should be kept, and relocate it inside components instead, or provide an option to do so, although I dont know why both would be needed. This also fixes a problem with circular references.
For example:
# asyncapi.yaml
asyncapi: '2.2.0'
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  user/signup:
    subscribe:
      message:
        $ref: './messages.yaml#/messages/UserSignedUp'

#messages.yaml
messages:
  UserSignedUp:
    payload:
      type: object
      properties:
        displayName:
          type: string
          description: Name of the user
        email:
          type: string
          format: email
          description: Email of the user

Should resolve to:
# After combining
asyncapi: 2.2.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  user/signedup:
    subscribe:
      message:
        $ref: '#/components/messages/UserSignedUp'
components:
  messages:
    UserSignedUp:
      payload:
        type: object
        properties:
          displayName:
            type: string
            description: Name of the user
          email:
            type: string
            format: email
            description: Email of the user

I think we can use https://github.com/asyncapi/optimizer to move references to components, I haven't tested anything yet but giving a quick read I think we will be able to do it.
I will try this out and let you know @jonaslagoni


Added a warning and a disclaimer

This section will warn users about the downsides of installing the exploit onto a PS1 memory card and exempt the developers from any liability regarding damaged cards.

If even MCA can't format a MC with the exploit installed, what can?
I don't know any other PS2-program for memory cards which also supports PS1-cards.
Some game? Formula One (the first, not 97), Alien Trilogy, Destruction Derby allegedly have menu-options for formatting memory-cards, but that could also just apply to new ones which haven't been formatted to begin with.
Some hardware, like the PS3-USB-memorycard-adapter or a memcarduino?
After some searching I found a tool which has to be started from disc on a PS1, called "PSX Memory Card Formatter" (psxmcfor-1.0.zip): https://reachcoding.eu/psx-memory-card-formatter
It offers to format and unformat a card, which sounds promising.


⚠ Bofrost.lu has degraded performance

In 41a9325, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1464 ms

Resolved: Bofrost.lu performance has improved in e14f510 after 29 minutes.


Add SVG Schema

This may be possible if the following PRs are merged
https://github.com/Hopding/pdf-lib/pull/1073

[ ] Read & Write SVG Schema
[ ] Readonly SVG Schema

ref https://github.com/hand-dot/labelmake/issues/25

ref: https://github.com/pdfme/pdfme/pull/384


AbstractHmBody.java:60-63: Right now the describeTo...

The puzzle 485-6f864529 from #485 has to be resolved:
https://github.com/yegor256/takes/blob/a98eb9681cd67703409dc0637dba93766676941a/src/main/java/org/takes/facets/hamcrest/AbstractHmBody.java#L60-L63
The puzzle was created by rultor on 09-Feb-18.
Estimate: 30 minutes, role: IMP.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Job #795 is now in scope, role is DEV

The job #795 assigned to @t-izbassar/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

The puzzle 485-6f864529 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #832 is still not solved.

@elenavolokhova/z please review this job completed by @t-izbassar/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

The job #795 is now out of scope

@0crat quality good

Order was finished, quality is "good": +35 points just awarded to @t-izbassar/z

Quality review completed: +8 points just awarded to @elenavolokhova/z

@0pdd the only puzzle #832 is solved here.


URL rewrite functionality

Can there possible be a label to specifiy that the backend config that generated should rewrite the base path from the frontend.
Currently having an issue where I'm trying to put kibana behind the docker-flow-poxy but apparently it requires a url rewrite.

Realised this is probably in the wrong place. Closing


mapCoverage issues

Hi,
I'm getting coverage issues with Jest.
When I set mapCoverage: true, some files disapear from the coverage report.
Example:
# mapCoverage:true
src/api                |      100 |      100 |      100 |      100 |                |
  index.js             |      100 |      100 |      100 |      100 |                |
  linkHeaderParser.js  |      100 |      100 |      100 |      100 |                |
  repositories.js      |      100 |      100 |      100 |      100 |                |
src/components         |     7.84 |     2.94 |     5.88 |    11.76 |                |
  FileExplorer.vue     |        0 |        0 |        0 |        0 |... 51,52,53,54 |
  MenuUserRepoList.vue |        0 |        0 |        0 |        0 |... 32,33,34,35 |
  Profile.vue          |        0 |        0 |        0 |        0 |... 57,58,59,60 |
  Readme.vue           |       80 |       50 |       50 |       80 |             23 |

# mapCoverage:false
src/api                |    92.86 |    84.21 |      100 |    92.86 |                |
  index.js             |    84.62 |    66.67 |      100 |    84.62 |          10,26 |
  linkHeaderParser.js  |      100 |      100 |      100 |      100 |                |
  repositories.js      |      100 |      100 |      100 |      100 |                |
  users.js             |      100 |      100 |      100 |      100 |                |
src/components         |     53.4 |    29.73 |    40.74 |    51.61 |                |
  FileExplorer.vue     |        0 |        0 |        0 |        0 |... 51,52,53,54 |
  FooterBar.vue        |    92.86 |       50 |      100 |      100 |        4,5,6,7 |
  MenuNavBar.vue       |      100 |       50 |      100 |      100 |       20,21,22 |
  MenuUserRepoList.vue |        0 |        0 |        0 |        0 |... 32,33,34,35 |
  Profile.vue          |        0 |        0 |        0 |        0 |... 57,58,59,60 |
  Readme.vue           |    94.74 |    57.14 |       80 |    92.86 |             25 |
  RepoListItem.vue     |      100 |       50 |    66.67 |      100 |       45,46,47 |

(I remove some file for a better readability. See full coverage report (link to travis build):
All sources files are available here: https://github.com/maxpou/gitvub and jest config here
Thank you

I created simple example: https://github.com/tmy/vue-jest-map-coverage-issue-sample

Run vue init webpack vue-jest-map-coverage-issue-sample
(https://circleci.com/gh/tmy/vue-jest-map-coverage-issue-sample/1)

-----------------|----------|----------|----------|----------|----------------|
File             |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
-----------------|----------|----------|----------|----------|----------------|
All files        |     6.25 |        0 |       25 |     9.09 |                |
 src             |        0 |        0 |        0 |        0 |                |
  App.vue        |        0 |        0 |        0 |        0 |... 27,28,29,30 |
 src/components  |      100 |      100 |      100 |      100 |                |
  HelloWorld.vue |      100 |      100 |      100 |      100 |                |
-----------------|----------|----------|----------|----------|----------------|

Edit src/components/HelloWorld.vue
(https://circleci.com/gh/tmy/vue-jest-map-coverage-issue-sample/2)

----------|----------|----------|----------|----------|----------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
----------|----------|----------|----------|----------|----------------|
All files |        0 |        0 |        0 |        0 |                |
 App.vue  |        0 |        0 |        0 |        0 |... 27,28,29,30 |
----------|----------|----------|----------|----------|----------------|

I've had some issues aswell:
1/ Using an older version of vue-jest and the vue-cli webpack template, my colleague and me had different files listed on the code coverage with the same code (maybe some slight changes but definitely the same components, and imports)
2/ We migrated the source code to a more recent vue-cli webpack template that has jest "support" from scratch, and while we now have every single file listed contrary to before, it now displays a bunch of inexisting Uncovered lines, as @tmy 's coverage points out.

Hi,
I'm the original author of this PR on vue-template/webpack repo
I think the problem come from Jest itself.
I tried to switch to jest-vue-preprocessor (witch is an equivalent)... and I get similars issues. I'm not the only one who get issue with this coverage (example: https://github.com/vire/jest-vue-preprocessor/issues/41)

I've got some updates on this issue: my coverage report is bugged on my Windows 10 machine (even with a fresh install of my repo), but testing inside Docker or on CircleCI provides a coverage report that seem correct.

@nirkki: I can confirm this fixed the exact same issue I had.  Just added the data property back and coverage came in properly.

I have a problem with mapCoverage too. I have some components with no logic at all in it, only html. Something like the following:
GameInstruction.vue:
<template>

This game ... blah blah blah

</template>

Add looks like Jest is picking up the coverage with this config:

I have a problem with mapCoverage too. I have some components with no logic at all in it, only html. Something like the following:
GameInstruction.vue:
<template>

This game ... blah blah blah

</template>

Add looks like Jest is picking up the coverage with this config:
module.exports = {
  'moduleFileExtensions': [
    'js',
    'json',
    'vue',
  ],
  'transform': {
    '.*\\.(vue)$': '<rootDir>/node_modules/vue-jest',
    '^.+\\.js$': '<rootDir>/node_modules/babel-jest',
  },
  'collectCoverage': true,
  'collectCoverageFrom': [
    'src/**/*.{js,vue}',
    '!**/node_modules/**',
  ],
  'coverageReporters': ['text', 'html', 'lcov'],
  'mapCoverage': true,
  'moduleDirectories': ['node_modules'],
  'moduleNameMapper': {
    '^@/(.*)$': '<rootDir>/src/$1',
  },
};

And the resulting coverage is 0%. 😢
I saw the comment mentioning about the absence of data() in component. So I tried adding the data() attribute and the coverage become 100%.
Is this the expected behaviour? Are we not suppose to have empty components that only have template?

Definately not expected behaviour.
I just happened to notice it when comparing files that were present in coverage and those which were not. As a temporary workaround I added the empty data segment and now the coverage works well! Well, I had to cleanup some scss files as well, but that is another story.
Hope this gets fixed in some point, but I'm happy with the workaround until that.

Ok, coz I am new to testing in vue. I was just following the steps on the documentation on here and thought I was doing something wrong.
Alright, now at lease I now I am not the only one. I will just add data() as a work around then.

Hi,
Good spot @ycmjason !
As you mention, I added data() and it increase my coverage!

Initial coverage:

File                      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
--------------------------|----------|----------|----------|----------|----------------|
All files                 |    11.34 |     6.38 |     6.25 |    15.94 |                |
 src                      |        0 |        0 |        0 |        0 |                |
  App.vue                 |        0 |        0 |        0 |        0 |... 60,61,62,63 |
 src/api                  |      100 |      100 |      100 |      100 |                |
  index.js                |      100 |      100 |      100 |      100 |                |
  linkHeaderParser.js     |      100 |      100 |      100 |      100 |                |
  repositories.js         |      100 |      100 |      100 |      100 |                |
 src/components           |     4.42 |     1.47 |     5.71 |     7.69 |                |
  FileExplorer.vue        |        0 |        0 |        0 |        0 |... 59,60,61,62 |
  MenuLateral.vue         |        0 |        0 |        0 |        0 |      1,4,5,6,7 |
  MenuNavBar.vue          |       20 |        0 |    33.33 |       20 |    42,47,48,49 |
  MenuUserRepoList.vue    |        0 |        0 |        0 |        0 |... 32,33,34,35 |
  NotFound.vue            |        0 |        0 |        0 |        0 |... 33,34,35,36 |
  OfflineNotification.vue |        0 |        0 |        0 |        0 |    21,22,24,25 |
  Profile.vue             |        0 |        0 |        0 |        0 |... 58,59,60,61 |
  Readme.vue              |       80 |       50 |       50 |       80 |             27 |
  RepoList.vue            |        0 |      100 |        0 |        0 |             57 |
  RepositoryHeader.vue    |        0 |        0 |        0 |        0 |... 48,49,50,51 |

After adding data() (on OfflineNotification.vue, Readme.vue and RepoList.vue). You can see the PR here: https://github.com/maxpou/gitvub/pull/34/files

All files                 |    12.24 |     6.38 |     9.64 |    17.14 |                |
 src                      |        0 |        0 |        0 |        0 |                |
  App.vue                 |        0 |        0 |        0 |        0 |... 60,61,62,63 |
 src/api                  |      100 |      100 |      100 |      100 |                |
  index.js                |      100 |      100 |      100 |      100 |                |
  linkHeaderParser.js     |      100 |      100 |      100 |      100 |                |
  repositories.js         |      100 |      100 |      100 |      100 |                |
 src/components           |      6.9 |     1.47 |    13.16 |    11.76 |                |
  FileExplorer.vue        |        0 |        0 |        0 |        0 |... 59,60,61,62 |
  MenuLateral.vue         |        0 |        0 |        0 |        0 |      1,4,5,6,7 |
  MenuNavBar.vue          |       20 |        0 |    33.33 |       20 |    42,47,48,49 |
  MenuUserRepoList.vue    |        0 |        0 |        0 |        0 |... 32,33,34,35 |
  NotFound.vue            |        0 |        0 |        0 |        0 |... 33,34,35,36 |
  OfflineNotification.vue |       20 |        0 |       50 |       20 |    25,26,28,29 |
  Profile.vue             |        0 |        0 |        0 |        0 |... 58,59,60,61 |
  Readme.vue              |    83.33 |       50 |    66.67 |    83.33 |             31 |
  RepoList.vue            |       50 |      100 |       50 |       50 |             57 |
  RepositoryHeader.vue    |        0 |        0 |        0 |        0 |... 48,49,50,51 |
// ...

Now this 3 component got better coverage. That's cool. But there is still some missing files 😢

After adding data() + removing jest's mapCoverage option:

--------------------------|----------|----------|----------|----------|----------------|
File                      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
--------------------------|----------|----------|----------|----------|----------------|
All files                 |    30.85 |    20.75 |    25.93 |    35.06 |                |
 src                      |        0 |        0 |        0 |        0 |                |
  App.vue                 |        0 |        0 |        0 |        0 |... 60,61,62,63 |
 src/api                  |    92.31 |    84.21 |      100 |    92.31 |                |
  index.js                |    81.82 |    66.67 |      100 |    81.82 |          10,26 |
  linkHeaderParser.js     |      100 |      100 |      100 |      100 |                |
  repositories.js         |      100 |      100 |      100 |      100 |                |
  users.js                |      100 |      100 |      100 |      100 |                |
 src/components           |    33.68 |    20.63 |    26.92 |    36.84 |                |
  FileExplorer.vue        |        0 |        0 |        0 |        0 |... 59,60,61,62 |
  MenuLateral.vue         |        0 |        0 |        0 |        0 |      1,4,5,6,7 |
  MenuNavBar.vue          |    62.96 |    33.33 |       50 |    66.67 |    49,54,55,56 |
  MenuUserRepoList.vue    |        0 |        0 |        0 |        0 |... 32,33,34,35 |
  NotFound.vue            |        0 |        0 |        0 |        0 |... 33,34,35,36 |
  OfflineNotification.vue |       80 |       40 |       75 |    63.64 |    27,28,30,31 |
  Profile.vue             |        0 |        0 |        0 |        0 |... 58,59,60,61 |
  Readme.vue              |    94.74 |    57.14 |       80 |    92.86 |             25 |
  RepoList.vue            |       50 |    36.36 |    42.86 |     87.5 |             64 |
  RepositoryHeader.vue    |        0 |        0 |        0 |        0 |... 48,49,50,51 |

Now the file src/api/users.js appear (with 100% cc).  But if I check in detail the HTML report created by Jest, everything is wrong in the .vue files (I mean the highlighted lines).
Ps: I also tried to put data() in every .vue files (even if there are no tests on these files) but it didn't change anything.

@maxpou I find removing collectCoverageFrom in the jest config can be useful as well for now before vue-jest fix the issue. Some components really contain no logic and should not write tests on it, then the coverage should not be collected.

Hi,
FYI I recently switch my project (the one with the examples above) under the new vue-cli architecture (v3 still in beta).
and....everything works perfectly! :heart_eyes:
See related pull request and comments from the @codecov bot https://github.com/maxpou/gitvub/pull/43
The only thing that worry me is I don't know what's happened.
Maybe Jest team works on mapCoverage option and fix this issue... see https://github.com/facebook/jest/pull/5177

Sounds awesome! I will try it out later. I though Jest has remove the option mapCoverage?

yes this option is now deprecated!

Still something strange going on with the data() -blocks.
I have a bunch of more or less identical .vue -files and some got covered while some not.
Just for test I moved the (this time non-empty) data () {} -section as last after methods & computed and suddenly coverage was correct! Moved then back to original place and coverage was 0%.
Strange thing is that there are some files where the data block is not the last but the coverage is still working as expected. Is this some sort of timing problem where the parallel tests somehow affect each other?

@nirkki What OS are you using?
Can you try deleting this line in the package and see if it solves the issue—https://github.com/vuejs/vue-jest/blob/master/vue-jest.js#L6

Oh yes, removing getCacheKey solves the issue!
I verified this on 3 different files that had the problem.
OS is Windows 10.

I've removed cacheing in 2.1.1, can you see if this solved the issue?

Updated to 2.1.1
This solved both coverage issues I had in my project: the need for empty data () declaration as well as the changed behaviour when the data section position within .vue -file was altered.
So the coverage is now correct in my Windows 10 environment.

Is the fix for this still to add an empty data () block?  I'm on vue-jest 2.5.0 and this behavior still exists.

same here

Hi. I'm using vue-jest 2.5 with vue 2.5.16 and am also getting the problem with coverage. To try to isolate the problem, I'm running jest with --no-cache option, and I can confirm that putting in a data block will put the vue file in the coverage report, and taking it out will remove it.
Just as a note, if I run without the --no-cache option, I get inconsistent results depending on what I ran.

Just to complement the information from my last post, I did some more testing and found that not only adding a data section will cause the file to appear in coverage, but also adding things like a "methods" or "computed" section with a dummy function or adding lifecyle hooks such as created will also "work".
I'm not very familiar with jest, but running some debugging, it seems to me that the problem can be traced to when jest calls the istanbul function sourceMapStore.transformCoverage. At that point, it eliminates the vue components that don't have the aforementioned sections. It's as though it can't find any statements, functions or branches.

I'm also having this issue. Adding the data block combined with --no-cache helped partially. Why partially? Well, first let me briefly explain the project's composition:
I've split my component into these files: [comp1.html, comp1.scss, comp1.js, comp1.spec.js, index.vue].
Then, the index.vue is like this:
<template src="./comp1.html" />

So, after running the tests, the coverage is 100% on the index.vue but 0% on the comp1.js.

Was a solution found for this other than adding the empty data? Using the latest versions of vue-jest, vue-cli (3.0.1) etc and only way I can get "dummy" components that have props only to appear in the coverage reports is to include the additional markup.

I have been dealing with this issue setting up a new project. It can be reproduced using the latest vue-cli (3.0.5) and following the "Creating a Project" guide (https://cli.vuejs.org/guide/creating-a-project.html#vue-create).
vue create hello-world
> Manually select features
(x) Babel
(x) Unit Testing
> Jest
> In dedicated config files

Edit jest.config.js and add:
  collectCoverage: true,
  collectCoverageFrom: ['src/**/*.{js,vue}'],
  coverageReporters: ['text'],

Run npm run test:unit
Notice that HelloWorld.vue is missing from the test report.
Edit components/HelloWorld.vue and add in an empty data segment
data() {
  return {};
}

Run npm run test:unit again
Notice that HelloWorld.vue suddenly appears with its test coverage.
Thanks @nirkki for the workaround!! I have been parsing bug reports all evening with no luck as to what was causing this missing coverage.
The package.json that results from the vue-cli build:
{
  "name": "hello-world",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "test:unit": "vue-cli-service test:unit"
  },
  "dependencies": {
    "vue": "^2.5.17"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.0.5",
    "@vue/cli-plugin-unit-jest": "^3.0.5",
    "@vue/cli-service": "^3.0.5",
    "@vue/test-utils": "^1.0.0-beta.20",
    "babel-core": "7.0.0-bridge.0",
    "babel-jest": "^23.0.1",
    "vue-template-compiler": "^2.5.17"
  }
}

It's not a vue-cli issue, either, as I originally ran across the bug with a manual setup. In that scenario, the empty data segment also fixed the issue. That package json looks like:
{
  "name": "new-project",
  "version": "0.0.1",
  "description": "",
  "scripts": {
    "build": "webpack",
    "dev": "webpack-dev-server",
    "lint": "eslint 'src/**/*.{js,vue}'",
    "test": "jest",
    "tdd": "jest --watchAll"
  },
  "devDependencies": {
    "@babel/core": "7.1.2",
    "@babel/plugin-syntax-dynamic-import": "7.0.0",
    "@babel/preset-env": "7.1.0",
    "@vue/test-utils": "1.0.0-beta.25",
    "babel-core": "7.0.0-bridge.0",
    "babel-eslint": "10.0.1",
    "babel-jest": "23.6.0",
    "babel-loader": "8.0.4",
    "clean-webpack-plugin": "0.1.19",
    "eslint": "5.7.0",
    "eslint-plugin-jest": "21.26.1",
    "eslint-plugin-vue": "4.7.1",
    "html-webpack-plugin": "3.2.0",
    "jest": "23.6.0",
    "redux": "4.0.1",
    "reselect": "4.0.0",
    "vue": "2.5.17",
    "vue-cli": "2.9.6",
    "vue-jest": "3.0.0",
    "vue-loader": "15.4.2",
    "vue-router": "3.0.1",
    "vue-template-compiler": "2.5.17",
    "webpack": "4.22.0",
    "webpack-cli": "3.1.2",
    "webpack-dev-server": "3.1.10"
  }
}

I have also a strange issue.
With the help from this issue-report, i could fix 2 files of 4.
In short:
4 vue-files. 2 have now:
  data () {
    return {}
  }

THESE 2 files, will now be covered. The other 2 files have real data there (just an example):
  data () {
    return {
        items: [],
        somethingElse: []
    }
  }

These 2 files will not be under coverage, even with empty return{}. Project is created with vue-cli 2.9.6 webpack build.
Any ideas?

that's crazy, why in the world we need to add data property so the component can be tested for vuejs component? and the ticket was opened since 2017............
is there something wrong with vue or with jest? any idea?

Has anybody gotten code coverage to work for functional components?
If I add data() to a functional component, it will show up in the list, but I'll have 0% coverage on it because it never hits the return {} line.

that's crazy, why in the world we need to add data property so the component can be tested for vuejs component? and the ticket was opened since 2017............

...Srsly 🤦♂

The issue will be fixed by this PR. Sorry for the delay.

Still seems to be an issue in 3.0.4. @eddyerburgh any updates by chance?

Bump. @eddyerburgh–which vue-jest version fixes this?

Is there a solution to this?
It does not make much sense to create an empty data block only just for the file appears in coverage. 😞

It's the same thing for ava, or mocha.
I have never found a framework which work nyc and got a coverage to 100% without no tricks ...
Even a simple Logo.vue doesn't got a coverage at 100% with 5 poor lines :'(

People have already figured this out.. 🤦♂ It's because of the lack of a data property. Merely add the following to your component, and it will show up.
data() {
  return {
    // This solely exists to appear in the coverage report
  };
}

@range-of-motion It changes nothing to add an empty data.
Line are always incorrect and doesn't fix the coverage to 100% of the component :/

Right. But we're not gonna get much further with "this isn't working".. If you want this investigated, we need a test case.

@range-of-motion I will create a repository to reproduce this.
But on all subject that i could read, it's a problem between nyc and framework (jest, mocha, ava) about source map inline.


Add navigating CTags files

It would be amazing if it was possible to use LeaderF as a fuzzy finder for CTags files, which would make jumping to specific functions a lot easier.
Taglist.vim is an example of a viewer supporting ctag files: https://github.com/vim-scripts/taglist.vim

Duplicate with issue #8 .


Some fields in recorded events don't show nicely in jfr print command

When we print alloc or lock profiles recorded by async-profiler by jfr print --events command, it produces output like below:
% jfr print --events jdk.JavaMonitorEnter /path/to/async-profiler-profile.jfr | less
...
jdk.JavaMonitorEnter {
  startTime = 2023-07-22T10:05:19.508646833Z
  duration = PT0.00013625S
...

In contrast to the profiles recorded by JMC (or jcmd JFR.start), which produce pretty-formatted durations like:
% jfr print --events jdk.JavaMonitorEnter /path/to/jmc-profile.jfr | less
...
jdk.JavaMonitorEnter {
  startTime = 10:01:53.229
  duration = 46.750 us
...

This is because async-profiler doesn't annotate these types with ContentType.

https://github.com/adoptium/jdk17u/blob/jdk-<IP_ADDRESS>%2B1/src/jdk.jfr/share/classes/jdk/jfr/internal/tool/PrettyWriter.java#L355
https://github.com/adoptium/jdk17u/blob/jdk-<IP_ADDRESS>%2B1/src/jdk.jfr/share/classes/jdk/jfr/ValueDescriptor.java#L214

To produce readable (and consistent with JMC/JFR) output, it's nice to annotate these types with ContentType in async-profiler as well.
What do you think?
If it makes sense, I'm happy to submit a patch.

Good catch, thanks.
I committed the fix.

Thanks you for the quick fix!


[Idea 💡] Add concurrency configuration to some workflows

https://docs.github.com/en/actions/using-jobs/using-concurrency
Workflows that could benefit from this feature:

Workspace initialization (for the same issue)
Deployment of solution to validation or production

After some tests, we will configure concurrency on all workflows and make more tests to validate if it is useful or not.


WebXR Integration

Adding initial implementation for WebXR support. Currently this supports a basic viewer and some controller based locomotion.
Branched from brent/splatting

Currently work in progress features

Scene navigation (controllers + hand tracking)
Floating UI panels
Support for VR input for interactive clickable events

This supports VR and AR (mixed reality) mode
https://github.com/nerfstudio-project/viser/assets/9502341/807532a3-fb18-4bed-a957-d94aa357fabe

@cvachha I merged some of the experimental branches into main to make life easier for us. To clean up the commit history I then rebased your WebXR commit, do you mind double-checking that I didn't break anything?
If you've made other local changes this might cause problems, you could commit them somewhere and then cherry-pick back into this branch. Sorry 😬


on select one renderitem  onblur not applied to this, when i press one renderItem, the list disappear

Can you provide a code snipped where you use onblur?

<Autocomplete
	data={suggestions}
	renderItem={this.renderItem}
	hideResults={!this.state.focused}
	renderTextInput={this.renderTextInput}
/>

onBlur = () => {
	this.setState({ focused: false });
}

renderTextInput = () => {
	const { onChangeText, ...props } = this.props;

	return (
		<TextInput
			{...props}
			onChangeText={this.onChangeText}
			onFocus={this.onFocus}
			onBlur={this.onBlur}
			style={Styles.input}
		/>
	);
}

@alexeyMohnatkin you found any solution?

@Hashir524 AFAIR I created my own component from scratch

If the there is still an issue with onblur in the latest release feel free to reopen.

can this be re-opened? it's still an issue


I want to see how many tokens I can deposit

User story
As Chris I want to see how many tokens I can deposit so that I don't have to type a number first.
Orginal description
After connecting to Hub (0x5257964Ef9b81fba7276AF2a97c111AaD7B840D6) it doesn't show how much WETH I have available to open a channel, it only shows available WETH once I've typed in a number.
Acceptance criteria

Tasks

[ ]

CC @MrCleanerPickerUpper

Update the description and title

Current Token Flow
The home screen as it is implemented now displays all the user's connected token in one continuous list.
New Token Flow
The home screen should only display the user's current selected token together with its balance and all channels within its token network.
By displaying the channels for the token the user can easily get an overview of all the (open/closed/settled) channels as well as how many tokens have been deposited in respecitve channel.
A dropdown will reveal a list of all the user's connected tokens and the option to add a new token. If the user chooses another already connected token the user will be taken back to the home screen which will display this new token instead of the previous token.

That's consistent throughout the dApp and in my opinion, a nice option to not clutter the screen. Therefore I am closing it.
@MrCleanerPickerUpper Thanks again for your feedback :)


fix typo in readme sample code

Coverage remained the same at 95.12% when pulling b2a674c441476efaef24e3393adb6432371b21fd on moehabib:master into af87068bfeccaa3a0d55b74f1e7af868dfb02e8c on mc706:master.


Creating external XML help casing isn't consistent

Steps to reproduce
Create a markdown version of help for a command that has parameters. I did this for a module. Then create external help from the markdown file.
Expected behavior
Parameter attributes are often displayed with True/False values. I would expect the XML help file to create output like this:
-AsString [<SwitchParameter>]
    Display the timespan as a string.

    Required?                    False
    Position?                    named
    Default value                False
    Accept pipeline input?       False
    Accept wildcard characters?  False

Actual behavior
Instead I get this:
-AsString [<SwitchParameter>]
    Display the timespan as a string.

    Required?                    false
    Position?                    named
    Default value                False
    Accept pipeline input?       False
    Accept wildcard characters?  false

It is a minor issue for sure, but it would be nice if there was some consistency. The markdown files show False and True so during the XML conversion some strings are set differently. Personally I think it should be lower case.
Environment data

5.0.10586.117

I am using version 0.5.0 of the module on Windows 8.1 running PowerShell v5.

Good catch. We discussed casing for markdown part in #122 and picked FirstCaps. We should do the same maml generation.
I personally find lowercase more pleasant visually, in this case. But PowerShell uses this style for parameters, command names, and constants, so I think capitalizing the first letter is more consistent approach.

I was trying to see if there was any sort of pattern in other PowerShell help but there really isn't. Although for the most part lowercase seems predominant. Probably doesn't really matter as long as it is consistent.

Tried to implement this and found that we have no control over Required? and Accept wildcard characters?. They always displayed as lower-case. Note that they represent bool values.
Accept pipeline input?, Default Value and Position? are string values.
With Default Value all bets are off: we cannot tweak what user provided, because it could be case-sensitive.
Accept pipeline input? would result in things like true (ByPropertyName), which doesn't seems right ever.
At the end, it looks like there is no good way to unify these things.
I'm closing the issue as "By design" for now.
Please, feel free to re-open to continue the discussion.