WildFlySwarm - The generator should detect .war package

A wildfly swarm app may be packed as a .war also.
But this example was using .war
https://github.com/davsclaus/fabric8-hello/blob/master/helloswarm/pom.xml#L8
And then it was the default .war generator that was kicked in and wanted to run it as a tomcat.
We should detect that wildfly-swarm plugin is in the pom
https://github.com/davsclaus/fabric8-hello/blob/master/helloswarm/pom.xml#L35
And let the wildfly-swarm generator kick in instead.

Sounds like a regression of #526.

The wildfly generator is always taking over when being before the war-generator which is the case in the latest f-m-p releases already (3.2.27) (so #858 is not necessary and I will revert it if this is ok for @jstrachan )
There is still the issue that a .war is not picked up by the generator as the wildfly-swarm generator only deals with the fat jar. Since the fat-jar is created along side the war:
 ls -l target
total 273304
drwxr-xr-x  4 roland  wheel        136 Mar  6 08:42 classes
drwxr-xr-x  4 roland  wheel        136 Mar  6 08:42 docker
drwxr-xr-x  5 roland  wheel        170 Mar  6 08:42 fabric8
drwxr-xr-x  3 roland  wheel        102 Mar  6 08:42 generated-sources
drwxr-xr-x  4 roland  wheel        136 Mar  6 08:42 helloswarm
-rw-r--r--  1 roland  wheel        929 Mar  6 08:42 helloswarm-1.0-SNAPSHOT-helm.tar.gz
-rw-r--r--  1 roland  wheel  108056532 Mar  6 08:42 helloswarm-swarm.jar
-rw-r--r--  1 roland  wheel      11167 Mar  6 08:42 helloswarm.war
-rw-r--r--  1 roland  wheel   31854677 Mar  6 08:42 helloswarm.war.original
drwxr-xr-x  3 roland  wheel        102 Mar  6 08:42 maven-archiver
drwxr-xr-x  3 roland  wheel        102 Mar  6 08:42 maven-status

this still works, but picks up the fat jar, not the war.
The wildfly-swarm generator should be changed to detect the packaging, and if war is selected it should:

Choose a different base image (e.g. a Wildfly base image)
Pick the .war and not the -swarm.jar to put into the container.

This can be easily done for the plain Kubernetes mode, but not yet for the S2I mode as we don't have yet support for S2I webapps (but we should do this soon and this shouldn't be hard anyway).

@rhuss happy for my previous patch to be reverted.
BTW if the project creates a foo-warm.jar from the war, why not stick with the fat jar approach? Then we don't need to wait for S2I mode to support webapps?
We can let folks configure whether or not they want to use the foo war or the foo-swarm fat jar via the <build><finalName> configuration in the pom.xml?
e.g. this project worked great with no custom configuration of fmp (if you use my previous patch or you disable the webapp generator) since its finalName refers to the swarm fat jar so the fat jar approach works great
https://github.com/fabric8io/generator-backend/blob/master/pom.xml#L84

For me its still works even without the #858 patch as indeed the webapp generator never kicks in if the wildfly-swarm generator is before it in the chain. This is true in the latest releases and I verified, that a usable image is created, however with the fat jar instead of the war.
A reason for people to prefer a war is, that the image to create is much smaller as the Java EE server is already included in the base image. IMO it's a deficit of the wildfly-swarm plugin that it creates the fat jar, too when a war is requested, as it might take quite some time to generate 60MB+ jar files which are no needed.
So, for the moment and with version 3.2.28 @davsclaus example works out of the box even with packaging war (although the fat jar is picked up).
@jstrachan if the latest version 3.2.28 without your patch doesn't work for you, it would be awesome if you could please post the log of a Maven run with -Dfabric8.verbose as we then hopefully can see why the war-generator kicks in (which it doesn't in my tests).

Ok, just saw https://issues.jboss.org/browse/OBST-121 which is about the OpenShift S2I build. Let me check that, too (as I only checked the K8s case).

There is some details about WAR vs JAR here for swarm
http://wildfly-swarm.io/posts/to-war-or-jar/

@jstrachan in fact https://issues.jboss.org/browse/OBST-121 is due because of a different issue: The configuration in https://github.com/gytis/rest_wildfly-swarm/blob/fmp-3.2.28/pom.xml#L144-L150 cause the wildfly-swarm generator to be put last (this shouldn't be the case of course). If you remove this, it works with the latest versions of 3.2.28 already.
I will raise a new issue for the config regression.

@rhuss ah - maybe its the include of the wildfly-swarm generator that actually breaks the wildfly-swarm generator (as it moves it to the end of the list) ;)

@davsclaus thanks for the heads up.  So I guess we should support this with a war base image, too (and we need to fix this asap, too. its on my list for this week ;-)
However, I still consider the creation of an additional fat-jar even when using war packaging a regression.


Feature request: Add hostnames to Prometheus

Thanks for the great tool.
Is it possible to add Hostnames to the results in Prometheus. If I do lmstat -c<EMAIL_ADDRESS>-v I get a result like this:
Users of Nxhxhxhhx:  (Total of 78 licenses issued;  Total of 33 licenses in use)

"Nxhxhxhhx" v36.0, vendor: notapplicable, expiry: 1-jan-0
floating license
edengineer EDSCLIENT03 EDSCLIENT030.0 (v36.0) (licserver/28000 24025), start Tue 1/5 15:15

So I would like in above example the second column (EDSCLIENT03) also added to the metrics.

@JSP80 it is possible, but it is an antipattern, as the number of labels would explode, and also the number of stale labels would grow exponentially. See this.


Trying to fix relative paths in srcset attribute

Hey there, thank you for great plugin, it is very useful and needed.
It perfectly works with href and src attributes, but I often use srcset attribute for retina images:
<img src="pic.png"<EMAIL_ADDRESS>2x<EMAIL_ADDRESS>3x">

I've tried to change code to solve this problem by myself, but I think my solution terrifying.
In my opinion, my regular expression is not safe enough for production, because it's too open. It will replace all , /, but maybe there is the way to exec it only in srcset attribute?

@yagee Thank you!


[ISSUE #972]🔥Supports client clusting consume🚀

Which Issue(s) This PR Fixes(Closes)

Fixes #972
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


Update docs with expect_table_columns_to_contain_set example

There is no example in the readme for the expect_table_columns_to_contain_set test and the hyperlink is broken.

Absolutely~ Just submitted one @clausherther

Closed via #121 👏


pre-1970time zones

Hello
you may now that TZ zones are only aiming to be good after 1970. If one wants correct tme zone information before 1970, additonal zones are needed. Actually up to 2500 extra zones. The worst are some US states and some Canada provinces, which gave authority up to 1967 to local counties or communes to decide about following daylight savin time or not.
If one leaves out these US states and Canada provinces, I have so far define 239 extra zones.
Question: how can one go about defining boundary lines for these?
The original TZ zones remain, but become much smaller. For example in Germany, in addition to Europe/Berlin appear these extra zones
Zone	Europe/Germany/Mannheim	0:33:56 -	LMT	1891 Mar 15 	#azn=133
Zone	Europe/Germany/Munich	0:46:12 -	LMT	1891 Mar 15 	# azn=134
Zone	Europe/Germany/Stuttgart	0:36:44 -	LMT	1891 Mar 15 0:00	#azn=135
Zone	Europe/Germany/Frankfurt	0:34:40 -	LMT	1893 Apr	#azn=136
Zone	Europe/Germany/Mainz	0:33:44 -	LMT	1891 Mar 15 	#azn=138
Zone	Europe/Germany/Cologne	0:27:56 -	LMT	1893 Apr	# azn=139
Zone	Europe/Germany/Breslau	1:08:00 -	LMT	1893 Apr 1 	# azn=140
Zone	Europe/Germany/Danzig	1:14:40 -	LMT	1893 Apr 1 	# azn=141
Zone	Europe/Germany/Saarbrucken	00:33:44 -	LMT	1891 Mar 15	# azn=143
Zone	Europe/Germany/Montabaur	0:33:04 -	LMT	1891 Mar 15 	# azn=144

Seems like an interesting idea. I wouldn't be able to work on this on my own, so would need help from whoever is interested in working on this.


Blocklauncher only opens in safe mode

I have a Dreamtab tablet that will not open Blocklauncher outside of safe mode. It has worked properly in the past but it currently will not open. I hope you can help me to alleviate this problem.
The Tablet is a DreamTab Nabi Tablet
KitKat 4.4.2
Blocklauncher 1.9.10
MCPE 0.11.1

Give me the FULL mod list that you have.

No mods, this is just a fresh install of blocklauncher.

Same problem.i have Samsung Galaxy tab 3 4.4.2 and blocklauncher pro 1.9.10 and mcpe 0.11.1 but blocklauncher keeps crashing even though i disabled mods and patches.and addons.

I have a Galaxy Tab 3.  Put BL 1.9.10 and MCPE 0.11.1.  Runs with and without mods (APK and .js) without any issues.
I'm running Rocket Tab on mine.  Found that almost 95%+ of my issues were related to the stock OS.  It was terrible.  Put RocketTab on there and almost all my issues went away.  Still some strangeness with the Wi-Fi, but for the most part, a reboot fixes that.  I'd suggest you switch to RocketTab, as I do not believe that your issues are BL related.

@lostrennie Blocklauncher 1.9.10 isn't compatible with MCPE 0.11.1
Solution: Use Blocklauncher 1.9.7


[FEAT]: CI pipelines

Describe the feature you'd like to request
Add CI pipeline to build and push docker image to docker hub container registry .
Describe the solution you'd like
Using github actions to write a workflow to do so
Describe alternatives you've considered
No response
Additional context
No response

Hey @Mr-Sunglasses, I would like to solve this issue.
Please assign!

@Srijan-SS02

@Srijan-SS02 Bhai Sher 🐯, sher he khede bhai ko, sheeeerrrrr

workflow exists


CORE-6783

Added Transaction Component Implementations
NOTE - PR AND MERGE CORE-6781 BEFORE THIS ONE

Do we still needs this PR or it can be closed without merging, please?


Set roles install path to provisioning/roles.

Vagrant provisioner installs the roles in provisioning/roles.

As of Drupal VM 3.0.0 there's actually no need to run the ansible-galaxy install command anymore. It runs automatically with vagrant provision. The docs section in your previous PR should actually be removed.
Was there a bug where it installed the roles in the wrong directory?

@oxyc - Yeah... do we even need the ansible.cfg file anymore, at all?

Removing ansible.cfg would be another option.  The current ./roles is wrong though.
IDK what's up with that test failure.


net/frr: Disable eBGP policies

Without eBGP filters no prefixes are exchanged without a policy.
To not break too many setups disable globally
https://github.com/FRRouting/frr/issues/6843
https://forum.opnsense.org/index.php?topic=18379.0

Merged, thanks!


[Question] Conside support @jsx comment?

It's a common pattern using /* @jsx Vue.h */ to replace the default createVnode function in jsx. There will be some issue that require this feature, conside support it?

Already supported https://github.com/vuejs/jsx-next/pull/322


This change allows the inclusion of additional CSS and JS assets

This change allows the inclusion of additional CSS and JS assets to be added to the master.blade.php through the voyager config.
The real benefit here is it removes the need for copying the voyager master.blade.php into your views folder avoiding issues if a future update makes changes to this file.
I hope this is acceptable.
Thanks,
Tim

Just a comment on the codeclimate errors line exceeding 120 characters.
I had to do this because the formatting when rendered was making the  be tabbed in twice and I thought that would annoy people.

Ignore CodeClimate for now 👍


Update code-splitting.md

Updated per https://github.com/webpack/webpack.js.org/blob/master/src/content/plugins/commons-chunk-plugin.md

Thanks!


feat: dump chunk-protocol, and check it when gen batch proof

Summary
Related scroll PR https://github.com/scroll-tech/scroll/pull/807

Add chunk-protocol when init aggregator prover, and check it with protocols in chunk-proofs when gen batch-proof.
Dump chunk-protocol when dump chunk-proof (used to save chunk-protocol as asset file).
Suppose if could also call chunk_chunk_proofs in go-prover of scroll, it could generate the clear error (to coordinator).

Test

Aggregation-tests could pass.

if we find chunk protocol is invalid, log::error something?   what about log sha256(self.chunk_protocol) and sha256(chunk_proof.chunk_protocol)?   since sha256 is in released assets, so it would be easier to check version quickly?

if we find chunk protocol is invalid, log::error something? what about log sha256(self.chunk_protocol) and sha256(chunk_proof.chunk_protocol)? since sha256 is in released assets, so it would be easier to check version quickly?

Add an error log for sha256 values of different chunk protocols in commit https://github.com/scroll-tech/scroll-prover/pull/217/commits/e2d36059aadfd673d354421e7c7125fded588344.

Prover and verifier tests could pass with https://github.com/scroll-tech/scroll/pull/807 in test_zkp.
Necessary to add chunk.protocol to asset dir.


[Minor] Correct the Documentation for Upgrade to 1.7 (clean-paths)

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
https://github.com/dbt-labs/docs.getdbt.com/blob/6a1e40d949a04215a1a9a9eee927dc1967de5a38/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.7.md?plain=1#L69C41-L69C136
What part(s) of the page would you like to see updated?
The content under the subsection for dbt clean refers to the clean-paths in dbt-project.yml.
This requires correction because it is actually clean-targets and not clean-paths
The correction would involve changing clean-paths to clean-targets
Additional information
Assigning to self

Closed as addressed in pr #6713


breadcrumbs nav #79

POC with Bootstrap on groups

CSS issue on ol tag.

Updating the view is a bit heavy.
And placing it in the navbar does'n return a nice vizual.
I would go for just a template update. Replacing the
Page title
 by the breadcrumb.
Example:


Add "shear mushroom_cow" giving EXP

Description of new idea or improvement on existing one
Currently you can only shear sheep, but can't shear mushroom, would be nice to add exp for this too.
Detailed information what should do
When you shear a mushroom_cow, give exp for this

9fd58eb990a178e75daa6a3870bde391006ff6c6


no token error with docker

Hi,
I have recently installed Crawl4AI with docker on my Mac, but unfortunately, I am unable to utilize Crawl4AI without a valid token. Upon specifying a token in the .env file and appending the line -CRAWL4AI_API_TOKEN=${CRAWL4AI_API_TOKEN}, I can successfully access http://localhost:11235/crawl. Conversely, if I indicate -CRAWL4AI_API_TOKEN=${CRAWL4AI_API_TOKEN:-} or omit this line entirely, I encounter a authentication error:
Health check: {'status': 'healthy', 'available_slots': 8, 'memory_usage': 12.6, 'cpu_usage': 0.4} Error during basic crawl: 403 Client Error: Forbidden for url: http://localhost:11235/crawl
After exhausting all possibilities, I have meticulously reviewed the documentation and illustrative examples, yet to no avail; the system remains inoperable without a legitimate token. Your guidance at this juncture would be most appreciated.

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

@Seven-94 Thanks for trying to crawl for AI. When you create a Docker pass, you can assign any value to this token.  Now that I think about it, it's not very crucial. You can even modify main.py to remove the need for it. However, if you want to deal with those troubles and headaches, just set this as an environment variable in the command line when you create the Docker pass. You can pass anything, and then we will use that value when you make requests to the server.

Thank you for your response, but it still doesn't work, I've followed what you said but I'm still getting the same error. I also tried without authentication and got the same error.
Additionally, I had to modify your commands because "docker run -e CRAWL4AI_API_TOKEN=your_token_here -p 11235:11235 crawl4ai" returned an error saying "unable to find image 'crawl4ai:latest' locally
docker: Error response from daemon: pull access denied for crawl4ai, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'."
So I modified the command with "docker run -p 11235:11235 unclecode/crawl4ai:basic" which allows me to start the container but I still get an authentication error.
I also followed the instructions in http://localhost:11235/mkdocs/basic/docker-deploymeny/  and none of them work.
This command "docker-compose -f docker-compose.local.yml up -d" and this one "docker-compose -f docker-compose.hub.yml up -d" return the same error "open /Users/xxxx/xxxxxx/xxxxx/crawl4ai/crawl4ai/docker-compose.local.yml: no such file or directory".
I'm not an expert in Docker containers, but generally I manage to install them without problems and even create my own, but this time I have to admit that I'm stuck.
Anyway, thank you for your response. And Merry Christmas Eve!


#162 Limit ctrl flow obfuscation as workaround

:white_check_mark: Build ConfuserEx 374 completed (commit https://github.com/mkaring/ConfuserEx/commit/f68237d1dc by @mkaring)


Error on PETR.UnitTest

I get an error when running on the UnitTest using the parsed document that comes with the repo. When I run
python2 petrarch_ud.py batch -i data/text/PETR.UnitTest.records.parsing_parsed_udpipe_2.0.xml -o output.txt

I get this error:
Traceback (most recent call last):
  File "petrarch_ud.py", line 409, in <module>
    main()
  File "petrarch_ud.py", line 71, in main
    run(paths, out , True)  ## <===
  File "petrarch_ud.py", line 402, in run
    events = PETRreader.read_xml_input(filepaths, s_parsed)
  File "/Users/ahalterman/MIT/NSF_RIDIR/UniversalPetrarch/UniversalPetrarch/PETRreader.py", line 2325, in read_xml_input
    holding[entry_id]['sents'][sent_id] = sent_dict
UnboundLocalError: local variable 'sent_id' referenced before assignment

I think the reason is that the format of UnitTest is not compatible with the required format of PETRARCH. I will upload another version of UnitTest with compatible format.

This needs to be fixed asap so we will be able to test the Spanish and
Arabic....
On Oct 31, 2017 22:21, "JingL1014"<EMAIL_ADDRESS>wrote:

I think the reason is that the format of UnitTest is not compatible with
the required format of PETRARCH. I will upload another version of UnitTest
with compatible format.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openeventdata/UniversalPetrarch/issues/9#issuecomment-340967626,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJrP1lNSMH9Z7I0E-CT4TdWi7N8ElpqJks5sx-OngaJpZM4QLrZX
.


GraphQL support

Does it support GraphQL by it self or it requires some other third-party packages like GraphQL or GraphQL ASP.NET?
if it doesn't support graphql right now, do you have any plan to support it in future?

asp.net minimal apis has no graphql support built-in and neither doe FE because of that.
afaik, none of the third party libraries have support for minimal api yet.
if one day microsoft adds graphql support to asp.net minimal apis, FE might be able to add support.
until then, graphql is beyond the scope of FE.


[ALLUXIO-2727] Make BlockStoreLocationTest final to avoid accidental extension

https://alluxio.atlassian.net/browse/ALLUXIO-2727
Make BlockStoreLocationTest final to avoid accidental extension

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14598/
Test PASSed.

Merged build finished. Test PASSed.


New package: Assets v0.1.0

Registering package: Assets
Repository: https://github.com/nielsls/Assets
Created by: @nielsls
Version: v0.1.0
Commit: 2cc4c272b787a66cd4a24738a80b62719dffa3e1
Git reference: master

Will change repo name to contain .jl


V0.8.4

🌱 c8b59ba Support envFile options electron-vite-vue/issues/209
🌱 2d7f033 Add ImportMeta['env'] declaration

Dang it, I don't understand how GitHub's review work 😭
Anyways, everything looks great 🚀 just consider adding "packageManager" option instead of the custom script


Suspected Alt

Hello staff,
My brothers / family minecraft account (the username was Cumbrus now its Fqxxx) was banned because it was supposedly an alt of mine.
Is there any way to undo it (he's 8 and playing on my pc because he's too young to get his own.) he really wants to play Pixelmon.
Regards
Bewwe,

You personally admitted to a staff member that you were using that account yourself and knew it was against the rules.

Yes thats true, i called it my alt because i bought it for my brother to play with me so i call it alt or family account.
I started playing on the account because i wanted my brother to get a fresh start.
I gifted myself my froakie because its my favorite pokemon and if staff wouldnt ask me if its my alt i wouldnt use / abuse it to get items , pokes.

Me and my brother wouldnt mind a stats/starter reset, cuz he rlly wants to play.
I have the Froakie (evolved into a greninja) in an seperate PC box.

You're unbanned. If this happens again, expect an indefinite ban.


fix(hist): failure if no MappedColumns

Fixes an undefined TypeError if no MappedColumn exist in the history entity

:tada: This PR is included in version @kittgen/nestjs-typeorm-history-v2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Plan for Vue CLI v5

Development branch: dev, and will be merged to next on each pre-release.
Documentation: https://next.cli.vuejs.org/migrations/migrate-from-v4.html

Here are the rough ideas:
Major Dependency Upgrades

[x] Webpack 5 (also allows to opt-out to webpack 4), https://github.com/vuejs/vue-cli/pull/6060
[x] HTML Webpack Plugin 4
[x] Cypress 6, would be a peer dependency
[x] Workbox 6
[x] Jest 26
[x] Mocha 8
[x] ESLint 7
Other necessary major dependency version bumps, including various webpack loaders and plugins

Planned New Features

[ ] Performance

Now that we use webpack 5 by default, we can utilize its persistent cache to have a better compilation performance.

[x] Predicatibility

A --transpile-all CLI flag to include node_modules for transpiration, as a fail-safe for the transpileDependencies option. The transpileDependencies option can be set to true to transpile all dependencies in node_modules. It should be the recommended way to build your app, especially when you are using webpack 5, as the compilation overhead should be tolerable with the persistent cache.

[ ] Modern mode

Enabled by default, with additional modern-only and no-modern CLI options
A separate polyfills chunk by default
Better browserslist integration. For example, safari-no-module-fix can be dropped when browserslist config does not target those buggy browsers.

[x] Configuration

Async config loading

Changed Behaviors

[x] vue serve/build will be an alias of npm run serve/build. If an entry is designated and no package.json found, it’ll prompt to use vite (Vue 3) or parcel (Vue 2) for instant prototyping instead.

Dropped Features

[x] Drop support of Node.js 8, 11, 13
[x] Drop support of TSLint
[x] Drop support of node-sass
[ ] Drop support of extension-less Vue SFC imports
[ ] Do not allow creating projects with uppercase names even in Vue CLI UI.

Other Breaking Changes Under Consideration

[ ] Respect XDG specification for the location of configs

Do we choose to drop extension less SFC imports even for webpack projects or only on vite?

Even for webpack projects. There are edge cases in webpack environment too: https://github.com/vuejs/vue-cli/issues/5307

VUE_CLI_SERVICE_CONFIG_PATH as a cli options ?  muilt vue.config.js in  monorepos
--debug mode for server run to output some verbose?  console is terrible method to track code of cli
default show spend time for build process，to optimize.

mark

If possible, please update postcss-loader dependency to 4.0.4 from 3.0.0 to add compatibility with Postcss 8/Tailwind 2.0.

eslint-loader has been deprecated. Why not eslint-webpack-plugin?

VUE_CLI_SERVICE_CONFIG_PATH as a cli options ?  muilt vue.config.js in  monorepos
--debug mode for server run to output some verbose?  console is terrible method to track code of cli
default show spend time for build process，to optimize.

mark

These are not major design changes, so can be reserved for later minor releases.
We'll focus on the changes listed in the post first.
The last one is easy, though. I'll take a look if time permits.

If possible, please update postcss-loader dependency to 4.0.4 from 3.0.0 to add compatibility with Postcss 8/Tailwind 2.0.

Yeah, I'm working on that.

eslint-loader has been deprecated. Why not eslint-webpack-plugin?

It will be included in the final release.

Can we add jsconfig.json when create project?
This will work better with Vetur or VueDX.

Can we address #4801  ?
It is really hard to develop & debug Service Worker when we have to rebuild the app on each iteration.
It could mean enabling service worker in development mode, which seems to be a major change.
Thanks

Async config loading

Try to achieve this feature, but block by issue https://github.com/benmosher/eslint-plugin-import/issues/883
sync @vue/cli-service/webpack.config.js is required by @vue/eslint-config-standard

Can we add .eslintigonre  when create project which has eslint?

sometimes it cannot auto import reactive api, like type ref , it can't auto import or using quickfix

when init the project, if choose typescript template, add ts-jest automatically also config jest.config

FYI v5.0.0-alpha.0 has been released with most underlying dependencies updated.
We'll work on the planned new features next.
https://github.com/vuejs/vue-cli/releases/tag/v5.0.0-alpha.0

Is module federation supported for multiple pages / build targets?

ES feature support in v5: #5881 ?
I created a brand new project using v5 alpha, but it doesn't work ?? etc.

Use the online presets(ajax？or other ways), not just from Git repo! I dont want to create a repo just for a single preset !
and if i have two preset in a repo，could I have a choice?

When is the official version expected to be released?

When is the official version expected to be released?

#2138
Will we consider supporting vue.config.ts?

#2138
Will we consider supporting vue.config.ts?

When is the official version expected to be released?

respecting the XDG specification shouldn't be listed as a breaking change, vue could fallback to legacy paths if the XDG ones (or their fallbacks)

Respecting the XDG specification shouldn't be listed as a breaking change, Vue could always fallback to legacy paths if the XDG ones (or their fallbacks) fail, I've just updated my issue #5649 regarding the matter.

Hi @sodatea , can the alpha version work now?
I just created a new project using 5.0.0-alpha.3, and I can not run the dev server:
95% emitting emit(node:17872) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
        Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
        Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
(Use `node --trace-deprecation ...` to show where the warning was created)
99% done plugins FriendlyErrorsWebpackPlugin

 ERROR  Failed to compile with 1 error                                                                                上午11:55:55
  Error: The loader "F:\template\vue\node_modules\html-webpack-plugin\lib\loader.js!F:\template\vue\public\index.html" didn't return html.

  - index.js:336 HtmlWebpackPlugin.evaluateCompilationResult
    [vue]/[html-webpack-plugin]/index.js:336:24

  - index.js:243
    [vue]/[html-webpack-plugin]/index.js:243:22

  - runMicrotasks

  - task_queues.js:93 processTicksAndRejections
    internal/process/task_queues.js:93:5

  - async Promise.all

  - async Promise.all

No issues found.

The error comes from an incompatibility between webpack 5.22.0 (that was just released) and the html-webpack-plugin v4.5.1.
This can be fixed by setting your webpack version to 5.21.2 for now in your package.json
The proper fix is to update the html-webpack plugin to v5.1.0 (see https://github.com/jantimon/html-webpack-plugin/issues/1603) . This has already been done by @sodatea in Vue CLI (see https://github.com/vuejs/vue-cli/commit/4ce7edd3754c3856c760d126f7fa3928f120aa2e), and will be out in the next release!

Is module federation supported for multiple pages / build targets?

module federation is a feature of webpack5, and when I use it in pure webpack without any cli, it works,
here is the link: https://github.com/Ge-yuan-jun/pure-webpack5-mf-plugin

Have a issue with v5.0.0-alpha.5
#6318

In webpack 5 you can set output.publicPath: "auto". Which is a great functionality in combination with module federation. Would be great if vue cli option "publicPath" would support it too as modifying it directly is not allowed.

Was wondering, probably Cypress should be v6 now, not v5? Or is it intentional?

https://github.com/neutrinojs/webpack-chain/issues/266 webpack-chain alternative plan ？

@Ge-yuan-jun did you manage to run module federation with vue cli <IP_ADDRESS> alpha ?

Was wondering, probably Cypress should be v6 now, not v5? Or is it intentional?

The latest alpha version uses v6 now. It was v5 when the issue was opened.

neutrinojs/webpack-chain#266 webpack-chain alternative plan ？

webpack-chain is still gonna be maintained. So no need to find an alternative.

add SSG support

@falstack projects like https://nuxtjs.org handle SSG. Just my feeling but it seems out of scope for the CLI

有没有个大概的时间

My updated plan:
Blocking issues for Beta:

Changes related to modern mode. Working on that. May be out next week.
Everything else can either be added or fixed later, as they are not likely to be breaking changes.

Things must be done before RC:

(Blocking) A good enough default cache configuration, so that the build speed is tolerable. At the moment, there are 2 PRs working on that https://github.com/vuejs/vue-cli/pull/6323 https://github.com/vuejs/vue-cli/pull/6390 but we need more testing during the betas.

Before stable release:

Mochapack webpack 5 support. https://github.com/sysgears/mochapack/pull/83 But if that's too hard, I think I'll go with webpack 4 anyway. And I believe the planned webpack 5 support could be backward compatible so it's not a blocking issue.

@sodatea Did you check the lazy compilation mode for Webpack 5 out? Could massively increase performance for big apps

@sodatea Did you check the lazy compilation mode for Webpack 5 out? Could massively increase performance for big apps

Yeah, it's marked as experimental, so I haven't decided whether to enable it by default or leave it as-is.

Hi @sodatea
I have just install global @vue/cli@next and do upgrade project (from vue cli v4) follow instruction in next.vue-cli site. I see a issue: when setup everything done, run vue-cli-service serve, it running thought with message:
 INFO  Starting development server...
99% done plugins FriendlyErrorsWebpackPlugin

 DONE  Compiled successfully in 57361ms                                                                                6:59:16 PM

99% done plugins vue-cli-service serve
  App running at:
  - Local:   http://localhost:8080/
  - Network: http://localhost:8080/

  Note that the development build is not optimized.
  To create a production build, run npm run build.

99% done plugins FriendlyErrorsWebpackPlugin

 DONE  Compiled successfully in 2336ms                                                                                6:59:20 PM

99% done plugins vue-cli-service serve
  App running at:
  - Local:   http://localhost:8080/
  - Network: http://localhost:8080/

Issue "99% ..." message showing from Alpha versions to until now. Site still work ok, but message a bit confuse, no see any error come next.
Other issue is when press cmd + c to terminate progress , in v4 it immediate disrupt dev server but in v5 it hangup few sec (amount ~ 4 5 secs), must press several times before it complete disrupt it show:
99% end closing watch compilation%

Can you help validate this issue ? i can not find any topic say about this.

@TrungRueta
The 99% issue is caused by webpack 5 continuing sending progress events after compilation is done (for things like caching).
It doesn't affect the actual compilation progress.
I've been trying to fix the output message. Any help is also appreciated.

Didn't know about the Ctrl + C issue before. I'll have a look.

I have not much experience about deep package scripting, but i will try to help clarify reason. I tested with fresh new project compare with my current project.
Fresh new project created from vue create <> is lightweight and only delay very short time when terminate. clip when start and stop it here
https://user-images.githubusercontent.com/12226007/116001293-f46d5380-a61d-11eb-8347-3f117fb1f309.mov
this is setup:

you can see 99% message, note that dev server only show process one time (finish after first message 99% shown). And when terminate dev server (you can see syntax ^c it is pressing ctrl + c) it delay 0.5s.

in second i running v5 on my current project which real and heavier. this is result:
https://user-images.githubusercontent.com/12226007/116001344-3dbda300-a61e-11eb-945c-c95fb17abf8b.mov
This time it show 99% at near end or project but then trigger compile progress again (or maybe bug message only, i dont know yet). Result is we have 2 complete notification. Later when press ctrl + c it give hug delay , i tried press multi times buttons to demo that in delay time can do nothing.
this is packages.json of my project.
{
"dependencies": {
    "@apollo/client": "^3.3.11",
    "@aws-amplify/auth": "^3.4.26",
    "@aws-amplify/core": "^3.8.18",
    "@fortawesome/fontawesome-svg-core": "^1.2.34",
    "@fortawesome/free-brands-svg-icons": "^5.15.2",
    "@fortawesome/pro-duotone-svg-icons": "^5.15.3",
    "@fortawesome/pro-light-svg-icons": "^5.15.2",
    "@fortawesome/pro-solid-svg-icons": "^5.15.2",
    "@fortawesome/vue-fontawesome": "^2.0.2",
    "@vue/composition-api": "^1.0.0-rc.2",
    "buefy": "^0.9.5",
    "chart.js": "^2.9.4",
    "comlink": "^4.3.0",
    "core-js": "^3.8.1",
    "d3": "^6.5.0",
    "faker": "^5.4.0",
    "fuse.js": "^6.4.6",
    "graphql": "^15.5.0",
    "luxon": "^1.26.0",
    "md5": "^2.3.0",
    "numeral": "^2.0.6",
    "portal-vue": "^2.1.7",
    "register-service-worker": "^1.7.2",
    "rxjs": "^6.6.3",
    "socket.io-client": "^4.0.0",
    "subscriptions-transport-ws": "^0.9.18",
    "uuid": "^8.3.2",
    "v-calendar": "^2.2.4",
    "vue": "^2.6.11",
    "vue-chartjs": "^3.5.1",
    "vue-emoji-picker": "^1.0.1",
    "vue-router": "^3.4.3",
    "vue-select": "^3.11.2",
    "vue-toastification": "^1.7.11",
    "yup": "^0.32.9"
  },
  "devDependencies": {
    "@types/d3": "^6.3.0",
    "@types/faker": "^5.1.7",
    "@types/jest": "^26.0.22",
    "@types/luxon": "^1.26.0",
    "@types/numeral": "^2.0.0",
    "@types/uuid": "^8.3.0",
    "@types/yup": "^0.29.11",
    "@vue/cli-plugin-babel": "~5.0.0-beta.0",
    "@vue/cli-plugin-pwa": "~5.0.0-beta.0",
    "@vue/cli-plugin-router": "~5.0.0-beta.0",
    "@vue/cli-plugin-typescript": "~5.0.0-beta.0",
    "@vue/cli-plugin-unit-jest": "~5.0.0-beta.0",
    "@vue/cli-service": "~5.0.0-beta.0",
    "@vue/runtime-dom": "^3.0.11",
    "@vue/test-utils": "^1.1.3",
    "@vuedx/typescript-plugin-vue": "^0.6.3",
    "prettier": "^2.2.1",
    "sass": "^1.30.0",
    "sass-loader": "^10.1.0",
    "typescript": "^4.2.3",
    "vue-template-compiler": "^2.6.11",
    "windicss": "^2.5.9",
    "windicss-webpack-plugin": "^0.3.2",
    "worker-loader": "^3.0.8"
  }
}

this is vue.config:
const WebpackWindiCSSPlugin = require('windicss-webpack-plugin').default;

module.exports = {
  pwa: {
    workboxOptions: {
      skipWaiting: true,
      clientsClaim: true,
    },
  },
  devServer: {
    host: 'localhost',
  },
  chainWebpack: (config) => {
    config.plugins.delete('fork-ts-checker').end();

    config.module
      .rule('worker')
      .before('ts')
      .test(/\.worker\.ts$/i)

      .use('worker-loader')
      .loader('worker-loader')
      .options({
        filename: '[name].[fullhash:8].js',
        // inline: 'fallback',
        worker: {
          type: 'SharedWorker',
          options: {
            credentials: 'omit',
            name: 'GrowApp', // for debbuging
          },
        },
      })
      .end();
  },
  configureWebpack: {
    plugins: [
      new WebpackWindiCSSPlugin({
        config: `tailwind.config.js`,
        scan: {
          dirs: ['./src'],
          exclude: ['node_modules', '.git', 'public/**/*', '*.template.html', 'index.html', 'dist'],
          include: [],
        },
        transformCSS: 'pre',
        compile: false,
      }),
    ],
  },
};

Hope there info can help team find issue!

When I package, the files in the public directory will also be compressed? Packing time is much longer than before.
version: 5.0.0-beta.1

Maybe you already know about this, but I just wanted to mention the remaining dependency conflicts (with npm 7) that I encountered when migrating to vue-cli 5.0.0-beta.2:

npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/vue-jest
npm WARN   dev<EMAIL_ADDRESS>from the root project
npm WARN   1 more (@vue/cli-plugin-unit-jest)
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/cache-loader
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@vue/cli-service
npm WARN   1 more (@vue/cli-plugin-typescript)

The first one comes from vue 3 being installed. I guess in that case vue-jest 5 is needed.
Apart from this minor problem the upgrade went quite smoothly. So thank you for that :heart:

Can we just make Vue SFC the only way, optimize a single compilation step that, and do away with literally everything else? I have spent days slogging through build crap and I like to think my project is pretty slimmed down and simple (I don't have TS, I don't have SASS or any other loaders, and it's all still a major PIA!)

I have a proposal, use 'glob' and 'require.resolve ' scan @vue/cli-plugin-*, replace the old way of querying through this.pkg.
example:
const projectPlugins = globs
    .sync([
        './node_modules/@vue/cli-plugin-*',
        './node_modules/vue-cli-plugin-*',
        './node_modules/@**/vue-cli-plugin-*'
    ])
    .map((depPath) => depPath.replace(/\.\/node_modules\//, ''))
    .filter(isPlugin)
    .map((id) => {
        if (this.pkg.optionalDependencies && id in this.pkg.optionalDependencies) {
            let apply = loadModule(id, this.pkgContext)
            if (!apply) {
                warn(`Optional dependency ${id} is not installed.`)
                apply = () => {}
            }

            return { id, apply }
        } else {
            return idToPlugin(id, resolveModule(id, this.pkgContext))
        }
    })

// link: https://github.com/vuejs/vue-cli/blob/882aaca1fc80f7f478bac2f309b5e9b7f1acfe6b/packages/%40vue/cli-service/lib/Service.js#L182
old:
 const projectPlugins = Object.keys(this.pkg.devDependencies || {})
                .concat(Object.keys(this.pkg.dependencies || {}))
                .filter(isPlugin)
                .map((id) => {
                    if (this.pkg.optionalDependencies && id in this.pkg.optionalDependencies) {
                        let apply = loadModule(id, this.pkgContext)
                        if (!apply) {
                            warn(`Optional dependency ${id} is not installed.`)
                            apply = () => {}
                        }

                        return { id, apply }
                    } else {
                        return idToPlugin(id, resolveModule(id, this.pkgContext))
                    }
                })

If use this, we can use base config configure project

@a951055 This will break Yarn PnP.

I have noticed two issues when running vue upgrade --next in my project:

yarn was used even if I only use npm. I guess this is probably because I ran this command in a subfolder of an npm monorepo where there is no package-lock.json file.
@vue/cli-* packages were added to dependencies instead of devDependencies where the old 4.x packages were left untouched.

@DanSnow I don't think so. because. I think that through shallow scanning is not much (scan level 1 and level 2 in '/node_modules'). and can support your project use BaseConfig, such as maven.
This is very useful for a large number of projects. that's what babel did.

@a951055 Yarn PnP doesn't use node_modules. Instead, it saves all of the packages in a flat structure and patch the require to resolve a package name to correct path. Here is how a project with Yarn PnP will look like:

@DanSnow i see. I understand wrong.

I'm here again. This time I want to change my ideas. I want to change it into "Vue plugin" by interface loading`.
I need this interface

@a951055 Please don’t spam this thread. You can create a feature request. Feel free to also provide a PR with the implementation while you are at it.

are there plans to migrate to webpack-dev-server@4 (currently in beta)?

I am the author of vue-cli-plugin-vite.
As of version v1.3.5, basic webpack config and the different of webpack ecosystem and vite is compat(e.g. env vars, css-loader, devServer.{before, public, host} and so on). We can also use html template in vite(public/index.html).
Problems we cannot campatible is the Heavy use chainWebpack or Heavy vue-cli-plugin like electron plugin /  ssr plugin.
for heavy use chainWebpack, we can warning users writing universal vue.config.js, like check plugin/args exists before modify/tap it.
// vue.config.js
if (config.plugins.has('xxx') {
  // then modify it. because in vue-cli-plugin-vite mode,
  // there are no real webpack-plugin like html-webpack-plugin.
}

Benefits, we use real vite in exists vue-cli project and migrate to vite in the future is smoothly. The BEST DX today with lighting fast devServer start and HMR.
PR for vue-enterprise-boilerplate, less than 20 lines codebase modifications and we successfully use vite in vue-enterprise-boilerplate. or you can vue create my-vite-app && vue add vite.
Do you think we can (or possible) use vite for development and webpack(vue-cli-service build) for production ?
What is the Future Planning of vue-cli and vite ?
Thanks.

I raised this with vite and see Evan's reply here - https://github.com/vitejs/vite/issues/1527
Please clarify how is Instant Prototyping possible with Vite.

Do we have any real terms when v5 will be released?

Is anyone working on upgrading ts-loader to v9 on the typescript plugin?

v5 version receive almost no commits.
maybe its time to release it and add improvements later?

Do you think it would be feasible to drop webpack completely, and go with esbuild instead? I've been using it lately and it's incredibly fast, way less bloat for sure.

Is webpack-dev-server v4 going to be supported? It's rc0 version has been released for a month.

I created a PR for removing cache-loader in favor of webpack's own filesystem cache (webpack 5).
https://github.com/vuejs/vue-cli/pull/6634

#6669 seems to be the PR for updating to webpack-dev-server v4, so it's in progress :-)

@IndexXuan @bodograumann I'm curious about the 👎 to my esbuild suggestion, since I didn't see any written-out responses. Is there a reason you feel esbuild would be a bad direction?

@ffxsam I don't think it is realistic to drop webpack from @vue/cli as it would break the entire ecosystem around it (plugins/loaders). If you want to use something more modern, you should probably look into vite since that already uses esbuild for some parts of it.

@DRoet Thanks - that makes total sense.

options has an unknown property 'overlay'.

Got something imcompatable with latest webpack-dev-server and beta.4
Also, I am not sure, but jest plugin seems imcompatable with latest jest:
 FAIL  tests/unit/example.spec.ts
  ● Test suite failed to run

    TypeError: Cannot destructure property 'config' of 'undefined' as it is undefined.

      at Object.getCacheKey (node_modules/vue-jest/lib/index.js:10:7)
      at ScriptTransformer._getCacheKey (node_modules/@jest/transform/build/ScriptTransformer.js:280:41)
      at ScriptTransformer._getFileCachePath (node_modules/@jest/transform/build/ScriptTransformer.js:351:27)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:588:32)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:758:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:815:19)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        14.588 s
Ran all test suites.

@Mister-Hope If you want to use Jest v27, you need to use the new package @vue/vue3-jest (or @vue/vue2-jest). Jest v27 had breaking changes, so we had to release a new version of vue-jest.
See https://github.com/vuejs/vue-cli/pull/6627 for more info on how to configure your project (or create a new project to check the configuration). If you run into an issue, feel free to open a dedicated issue and ping me!

@Mister-Hope If you want to use Jest v27, you need to use the new package @vue/vue3-jest (or @vue/vue2-jest). Jest v27 had breaking changes, so we had to release a new version of vue-jest.
See #6627 for more info on how to configure your project (or create a new project to check the configuration). If you run into an issue, feel free to open a dedicated issue and ping me!

Thanks for that reminder, I deleted vue-jest, and changed my jest.config,js, then unit test works fine now.
@sodatea I think we should better mark all the v27 alpha versions of vue-jest as deprecated to warn the users like me or especially mention this in changelog. Since V5 has been devloped for 9 month, I think there will be plenty of man switching to v5 alpha versions with webpack 4 to get full power of node 12 or 14. And this deps is manually decalred in package.json. instead of on the tool chain.

Is there any timeline on this?

Hi, is it possible to make Jest as peer dep? Vue CLI 4 doesn’t allow overwrite Jest dep (I haven’t tested Vue CLI 5 RC yet)

Evan has gone on the record saying <script setup> is intended to be the standard syntax for Vue single-file components going forward.
But right now the Vue Cli scaffolds single-file components using export default defineComponent({ etc etc });.
Therefore I suggest using <script setup> as the default scaffolding when selecting Vue 3. At the very least it should be an option during project creation. This will dramatically help with uptake, and move the community towards the intended standard syntax as outlined by Evan.

Evan has gone on record

He also went on record on reddit & twitter...
These pictures summarizes it:

... makes us wonder what the future of Vue-CLI is?

Hi, is it possible to make Jest as peer dep? Vue CLI 4 doesn’t allow overwrite Jest dep (I haven’t tested Vue CLI 5 RC yet)

Then we need separate packages for Jest presets. Ideally two, one for Vue 2 and one for Vue 3.
Then the complexity may grow out of control.
So at the moment, I prefer to keep it inside the plugin.
And we may bump Jest major versions more often after v5 is out.

Therefore I suggest switching to <script setup> as the default scaffolding when selecting Vue 3. At the very least it should be an option during project creation.

I'd love to but I don't have the time. So PR's welcome.
Actually, the new landing page in create-vue was originally implemented for Vue CLI.
But it messed up all the CLI tests and I can't fix them in a reasonable time frame. So it ends up in that new project without any tech debts. The CLI templates are remained as-is.

... makes us wonder what the future of Vue-CLI is?

Vue CLI will continue to be maintained and still the recommended tooling for webpack users.
Webpack is not going to fade away any time soon so Vue CLI isn't gonna be abandoned either.
But we must say, Vite and create-vue provide a better out-of-box experience for Vue users to start a new project.
That's why they are the "default recommendations".

Hi, is it possible to make Jest as peer dep? Vue CLI 4 doesn’t allow overwrite Jest dep (I haven’t tested Vue CLI 5 RC yet)

Then we need separate packages for Jest presets. Ideally two, one for Vue 2 and one for Vue 3. Then the complexity may grow out of control. So at the moment, I prefer to keep it inside the plugin. And we may bump Jest major versions more often after v5 is out.

I think a warning or error to ask users to install Jest as a dependency when trying to use the preset package could be an idea?
I think the idea to let CLI to install Jest when generating the project is good, but it shouldn’t prevent the users from upgrading Jest themselves whenever they need.

@ahnpnl We made Jest an explicit dep in CLI v5, you can give it a try (see https://github.com/vuejs/vue-cli/pull/6627). A new project now uses Jest v27 and @vue/vue3-jest instead of vue-jest

Can you provide an optional configuration of core-js@2?

@ahnpnl We made Jest an explicit dep in CLI v5, you can give it a try (see #6627). A new project now uses Jest v27 and @vue/vue3-jest instead of vue-jest

Tested out with CLI v5 it works fine. I only can test it my personal project, my work project won't allow to use CLI v5 until an official release is out.
Another idea is: since Vue 3 drops IE11 support IIRC, can we provide an option to opt-in/out core-js?

@sodatea May I ask when are we to expect the release of the final version of Vue CLI 5 ?

@ahnpnl Another idea is: since Vue 3 drops IE11 support IIRC, can we provide an option to opt-in/out core-js?

Perhaps keeping it simple would be a better idea: core-js used by default for Vue 2 projects (it still needs to support IE), but removed in Vue 3 projects (completely drop IE support)?

@ahnpnl Another idea is: since Vue 3 drops IE11 support IIRC, can we provide an option to opt-in/out core-js?

Perhaps keeping it simple would be a better idea: core-js used by default for Vue 2 projects (it still needs to support IE), but removed in Vue 3 projects (completely drop IE support)? Don't know if this is really feasible, though.

This option LGTM

@ahnpnl just want to clarify core-js usage since there isnt much documentation on it. If I have a vue2 app but only need to support modern/esm browsers (not ie11), is core-js doing anything of value or could i just remove it?

Hi, in short, you only need core-js if you need to support ie11. It's not specific to vue2 or vue3.

Hi, in short, you only need core-js if you need to support ie11

I don't think it's true, core-js provides various polyfills for features that are not available in other browsers too, for example Array.findLast which is not available in current Chrome and many more

Hi, in short, you only need core-js if you need to support ie11

I don't think it's true, core-js provides various polyfills for features that are not available in other browsers too, for example Array.findLast which is not available in current Chrome and many more

Array's findLast() method is in fact available in latest Chrome 97 https://caniuse.com/?search=findLast
But is Vue 2/3 or Vue CLI actually using it anywhere? I very much doubt it...

Array's findLast() method is in fact available in latest Chrome 97 https://caniuse.com/?search=findLast
But is Vue 2/3 or Vue CLI actually using it anywhere? I very much doubt it...

Yes, you are right.
Maybe someone else has some misunderstanding of what core-js does.

What happens to v5 if this project is now in maintenance mode? Or is create-vue the actual stable release? This is very confusing.

What happens to v5 if this project is now in maintenance mode? Or is create-vue the actual stable release? This is very confusing.

The entire official stance on any Vue tooling has been disjointed and a mess ever since Vue 3.

I'll continue maintaining this repo, applying patches, adding small new features.
I'll make no major changes to this project.
We recommend new projects to use create-vue.

Regarding the v5 stable release:

In most cases you can just use the RC version, it's quite stable IMO;
I would very much like to ship a new stable release, too. But I'm not confident enough to do so because I'm not ready for the incoming questions and issues once it's out.
Currently, my plan is to check again and do some last-minute bug fixes and ship another RC then stable.

I think one important thing that is still missing from v5.rc is the typechecking of script-setup sfcs.

I think one important thing that is still missing from v5.rc is the typechecking of script-setup sfcs.

If fork-ts-checker-webpack-plugin still can't fully support that, we may end up recommending using vue-tsc separately for type-checking.

@sodatea You said new projects should use create-vue. OK, but for us, who are used to vue-cli (I've been using it for a long time), there's also vite... so which one should we use. The ecosystem is becoming fragmented, without any obvious explanation as to why. Isn't vue spreading itself too thin? I don't blame anyone, just asking... it doesn't seem to go in the right direction IMHO.

create-vue is a scaffolding tool. It creates a Vue project that uses Vite for dev server and bundling.
Vite has about 400k/week downloads. It's mature enough for a new project.
You can keep using Vue CLI if you prefer webpack. It's still being maintained.
But Vite and create-vue provides a better out-of-box experience.

@sodatea Thanks for the explanation. For anyone out there still wondering what is going on and why there is no documentation, well... here's the new documentation at staging.vuejs.org which is currently kind of "hidden" and which will most probably become the official vuejs.org
https://staging.vuejs.org/guide/scaling-up/tooling.html#project-scaffolding

Currently, my plan is to check again and do some last-minute bug fixes and ship another RC then stable.

@sodatea Waiting patiently for the next Vue CLI 5 RC / stable version... I'm not ready to switch to Vite/create-vue for production yet.

For anyone feels missed with vue-ecosystem please, keep in mind what now vue is more easily to develop and deploy than vue 1 is launched, so to a bunch of reasons: vite is more simplest, lazy, fast way to develop, deploy and delivery like vue-cli do in the past, IMHO the vite not need a large list to reasoning with devs about why adopt vite over the vue-cli, reading the vite documentation is enough to understand the fact: now the things is more simple than the past, so trust in vue-core, we understand a lot what vue community need to improves our jobs ❤

@lpj145 Dude... I read that twice... now my brain hurts.

@lorand-horvath i don't know why, if my words feels aggressive don't worry, so if the fact of vite is now the boss, for me is like train passing above me, but it's life 🤣🤣

According to the last RC. v5 will be stable next week if there are no major regressions found.

@lorand-horvath, I would love to switch to vite if it had support for async web components. I opened a discussion thread on the vite repo a year ago requesting the feature.

v5.0.1 released.
Sorry that I've burnt out for quite some time last year and failed to do a stable release earlier.
There are still a few features that I wish I could add to this release but haven't finished (e.g. creating new projects with ESLint 8).
I plan to continue working on them for the following minor releases.
But anyway, this new major version is stable and ready for use. Please enjoy.

@sodatea Thank you for all your hard work on the project.

@sodatea THANK YOU

Thank you so much @sodatea, it's always stressful maintaining an open source project so many people rely on and it so often goes unappreciated. But speaking on behalf of the thousands of people who haven't even stumbled on this thread, thank you for helping improve our lives as developers!

@sodatea  we have updated the vue-cli version to 5.0.1 version for an existing project. This throws below error.
ValidationError: Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.
- options has an unknown property 'overlay'. These properties are valid:
object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? }
ValidationError: Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.

options has an unknown property 'overlay'. These properties are valid:
object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? }
at validate (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules\webpack-dev-server\node_modules\schema-utils\dist\validate.js:115:11)
at new Server (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules\webpack-dev-server\lib\Server.js:232:5)
at serve (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules@vue\cli-service\lib\commands\serve.js:183:20)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 1.

@sodatea we have updated the vue-cli version to 5.0.1 version for an existing project. This throws below error.
ValidationError: Invalid options object. Dev Server has been initialized using an options object that does not match the API schema. - options has an unknown property 'overlay'. These properties are valid: object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? } ValidationError: Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.

options has an unknown property 'overlay'. These properties are valid:
object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? }
at validate (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules\webpack-dev-server\node_modules\schema-utils\dist\validate.js:115:11)
at new Server (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules\webpack-dev-server\lib\Server.js:232:5)
at serve (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules@vue\cli-service\lib\commands\serve.js:183:20)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 1.

webpack-dev-server modified their api. You need to check their documentation for break changes.

For example:

@sodatea we have updated the vue-cli version to 5.0.1 version for an existing project. This throws below error.
ValidationError: Invalid options object. Dev Server has been initialized using an options object that does not match the API schema. - options has an unknown property 'overlay'. These properties are valid: object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? } ValidationError: Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.

options has an unknown property 'overlay'. These properties are valid:
object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? }
at validate (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules\webpack-dev-server\node_modules\schema-utils\dist\validate.js:115:11)
at new Server (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules\webpack-dev-server\lib\Server.js:232:5)
at serve (C:\Users\o885500\Vista\azj-geolocation-ui\node_modules@vue\cli-service\lib\commands\serve.js:183:20)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 1.

But anyway, this new major version is stable and ready for use. Please enjoy.

Based on your log, For example:

@yoyo837 Do we need to install webpack-dev-server? Because in our project we are not explicitly installed any webpack packages.

No, stop "in our project" why don't you check the lock file and see if you are actually using any webpack packages or not?


Timeouts on predective test selection

Expected Behavior
When I run tests the predective feature shouldn't throw a timeout
Observed Behavior
I'm getting time outs
Steps to Reproduce
Just run ./gradlew test after some changes
Context
I think our GE instance blow up because of my predictive-test request to it. After the build I clicked on the scan link and the server was not responsive. After a minute or so it reboots itself.
I'm not asking to disable it. I just want to report it if someone else get the same error or this is just a single event. (But to be honest I got the same issue yesterday but I was too lazy to report it)
Your Environment

Version of detekt used: main
Gradle scan link: https://ge.detekt.dev/s/nsdwojjie3qh2

Can you include the timeout error from the log next time you hit this?

https://ge.detekt.dev/s/nsdwojjie3qh2/console-log#L271 Here you can see those timeout errors.
I talked with people from GE and they gave us more RAM to our instance. Maybe that was the problem.

I think the RAM was the issue, I can't reproduce this issue anymore so I'm closing this :)


-2 active cases in Buldhana District (Maharashtra)

I just downloaded district wise CSV from https://api.covid19india.org/csv/latest/district_wise.csv. And it has -2 active cases in Buldhana District of Maharashtra (District_Key - MH_Buldhana).

This was because MH govt. dashboard was reporting the same way. Looks like this is fixed now on the website and the csv should reflect the same in the latest version. Please check.

Can't do much about these since this data is from the state dashboards. Closing this for now.


Need chat sessions and system role setting

Could you please add system role set for each chat and allow users to create several chat sessions?

@jozhn thank you for using the extension and bringing up feature improvement suggestions here. Browser auto-login method has that feature, you could see list of your past conversations and easily switch between them with that method. Could you elaborate a bit what you mean by system role setting?

@jozhn thank you for using the extension and bringing up feature improvement suggestions here. Browser auto-login method has that feature, you could see list of your past conversations and easily switch between them with that method. Could you elaborate a bit what you mean by system role setting?

ref: https://platform.openai.com/docs/guides/chat/introduction

The system message helps set the behavior of the assistant. In the example above, the assistant was instructed with “You are a helpful assistant.”

System role setting can help us to set the behavior of chatgpt before use.

@jozhn ok got it. You mean the message. Changing system roles isn't much of a help but the initial system message is what extension provides out of the box for the user at the moment. I have plans to make it customizable but not yet. I will update the thread if & when it becomes available in the extension as a setting.

@gencay thank you very much!


#289 - introduced dedicated Dwn.handleRecordsRead() method

introduced dedicated Dwn.handleRecordsRead() method that uses its own reply schema
added support for unsigned RecordsRead message + fixed the corresponding test

This one is for you @csuwildcat.

@diehuxx,

This makes sense to me. Is the eventual goal to add dedicate methods + return types for all Records methods? Or even further: for all methods of all interfaces?

Yes and yes, but of course feel free to provide feedback, alternative suggestions to #289.


Ability to pass flags (parameters)

In our gulp the tasks can receive flags, e.g, I can run gulp build or gulp build --watch.
How do I pass flags with sublime-gulp?

Hello! I never used arguments in my tasks so I didn't add this feature (so it's not possible right now), but I think is a good idea.
I'll give it a try, but can you give me an example of some task that uses flags please? so I can test locally.
Thanks!

I ended up just using shell to run gulp, however, I still think it could be added as a nice feature. For example, we pass an environment flag to our gulp, like so: gulp build --env=windows
Then we check it inside like so:
var argv = require('minimist')(process.argv.slice(2));
var env = argv.env || null;

+1. We use the --cwd flag with gulp because have a single gulp file servicing many little projects.

Sorry for the big delay. I have a local branch for this feature but I haven't been able to get significant progress.
It might be taking me a lot more than expected but I'll keep you posted when I have something.

I finally got around doing this feature, sorry for the massive delay.
I'll close this for now but if you have any feedback let me know and I'll reopen it.


Problem with entering az backup vault update --name $name --rv01 --resource-group test-dev-bcdr-rg --classic-alert disable

Describe the bug
az backup vault update --name {vault-name} --resource-group {rg} --classic-alert disable
When I enter the command, I get a python error message. The items in the brackets are just place holders, the real information was left out.

I have included the error message for your review.

Related command
az backup vault update --name {vault-name} --resource-group {rg} --classic-alert disable
Errors
The command failed with an unexpected error. Here is the traceback:
'NoneType' object has no attribute 'classic_alert_settings'
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 664, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 731, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 723, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/backup/_exception_handler.py", line 11, in backup_exception_handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 701, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 334, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/backup/custom.py", line 164, in update_vault
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/backup/custom.py", line 243, in _get_vault_monitoring_settings
AttributeError: 'NoneType' object has no attribute 'classic_alert_settings'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
Issue script & Debug output
$vname=test1 # The items listed are just place holders to give you an idea
$rg=test1-rg
Just ran a line of code and it failed - (ex - az backup vault update --name $vname --resource-group $rg --classic-alert disable)
Expected behavior
When I run the command as indicated above, I get a Python error message
The command failed with an unexpected error. Here is the traceback:
'NoneType' object has no attribute 'classic_alert_settings'
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 664, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 731, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 723, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/backup/_exception_handler.py", line 11, in backup_exception_handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 701, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 334, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/backup/custom.py", line 164, in update_vault
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/backup/custom.py", line 243, in _get_vault_monitoring_settings
AttributeError: 'NoneType' object has no attribute 'classic_alert_settings'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
Environment Summary
C:\Users\chsanders>az --version
azure-cli                         2.61.0
core                              2.61.0
telemetry                          1.1.0
Dependencies:
msal                              1.28.0
azure-mgmt-resource               23.1.1
Additional context
None at this time.

Thank you for opening this issue, we will look into it.

I am running the update now, will keep you posted as to what I find

choco install azure-cli
Installed - Azure Cli 2.64

az --version
azure-cli                         2.64.0
core                              2.64.0
telemetry                          1.1.0
Dependencies:
msal                              1.30.0
azure-mgmt-resource               23.1.1
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\chsanders-pv.azure\cliextensions'
Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb  6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]
====================================================
Now I am getting this error after the upgrade:
======================================
C:\Windows\system32>az login --use-device-code
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code AVG4X9CHJ to authenticate.
Encryption failed: [WinError -2146892987] The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. See also https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/enable-computer-and-user-accounts-to-be-trusted-for-delegation Consider disable encryption.
Please report to us via Github: https://github.com/Azure/azure-cli/issues/21010


linux-amd64 hangs at "connecting"

Hello there,
> uname -a
Linux raoel 4.14.0-3-amd64 #1 SMP Debian 4.14.17-1 (2018-02-14) x86_64 GNU/Linux

> lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (buster)
Release:	testing
Codename:	buster

(debian testing)
clean install from official binary release called yakyak-1.4.3-linux-x64.tar.gz
Installed with > cd /opt && sudo tar xzvf ~/Downloads/yakyak-1.4.3-linux-x64.tar.gz
I enter username / password / 2-FA and then I get a "connecting" screen and nothing happens.
This is what happens in my console:
> /opt/yakyak-linux-x64/yakyak
hconnect
reconnecting 0
resolving proxy http://plus.google.com
resolving proxy https://plus.google.com
resolved proxy DIRECT
resolved proxy DIRECT
connected 0

Did a sudo chmod -R myuser.myuser /opt/yakyak-linux-x64/, just to make sure, but this did not help.
Connected over a wifi-connection, no proxy.

Same here, exactly the same output when running on CL. Debian 9. Any update on this if this is acknowledge or smth? Thanks.

Sam here too. I'm on corporate proxy and YakYak stucks on connecting loop.
I tried both latest version (1.5.3) and precompiled binary (version 1.5.0.)

I also have the same problem, with both yakyak 1.4.3 and 1.5.3
This started occurring today. connect_failed SyntaxError: Unexpected token <
reconnecting 0
resolving proxy http://plus.google.com
resolving proxy https://plus.google.com
resolved proxy DIRECT
resolved proxy DIRECT
connect_failed SyntaxError: Unexpected token <
    at Object.bind.out (/opt/yakyak/resources/app/node_modules/hangupsjs/lib/init.js:62:23)
    at /opt/yakyak/resources/app/node_modules/hangupsjs/lib/init.js:63:26
    at _fulfilled (/opt/yakyak/resources/app/node_modules/q/q.js:854:54)
    at self.promiseDispatch.done (/opt/yakyak/resources/app/node_modules/q/q.js:883:30)
    at Promise.promise.promiseDispatch (/opt/yakyak/resources/app/node_modules/q/q.js:816:13)
    at /opt/yakyak/resources/app/node_modules/q/q.js:877:14
    at runSingle (/opt/yakyak/resources/app/node_modules/q/q.js:137:13)
    at flush (/opt/yakyak/resources/app/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
error connecting SyntaxError: Unexpected token <
    at Object.bind.out (/opt/yakyak/resources/app/node_modules/hangupsjs/lib/init.js:62:23)
    at /opt/yakyak/resources/app/node_modules/hangupsjs/lib/init.js:63:26
    at _fulfilled (/opt/yakyak/resources/app/node_modules/q/q.js:854:54)
    at self.promiseDispatch.done (/opt/yakyak/resources/app/node_modules/q/q.js:883:30)
    at Promise.promise.promiseDispatch (/opt/yakyak/resources/app/node_modules/q/q.js:816:13)
    at /opt/yakyak/resources/app/node_modules/q/q.js:877:14
    at runSingle (/opt/yakyak/resources/app/node_modules/q/q.js:137:13)
    at flush (/opt/yakyak/resources/app/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
reconnecting 0

I think your issue is different. I get the same error today, even connecting with another computer without proxy.

Ok.
I created my own issue: https://github.com/yakyak/yakyak/issues/919
Hope these get fixed.

Your new ticket is a dupe of #918 I think.

Hi, I have the same problem on  ubuntu 14.04 node 6. Anybody know how to fix it?
I started it once, then I needed to login and after that the main windows didn't show.
Then I made a fresh clone and did:
npm install
npm run gulp
npm run electron app

Now the terminal shows this, but nothing else happens:
><EMAIL_ADDRESS>electron /home/robkorv/compound/yakyak
> electron "app"

hconnect
reconnecting 0
resolving proxy http://plus.google.com
resolving proxy https://plus.google.com
resolved proxy DIRECT
resolved proxy DIRECT
connected 0

While searching for a solution the main window just popped up and all is good now.

Stuck on connecting on Ubuntu 16.04 LTS, installed from the Software Center directly and through Snap with the same issues. It gets stuck indefinitely on "Connecting" after logging in with Google account info.

I can confirm that v1.5.3 fixes this issue :heart:.


Needs tests

I was going to update dependencies (to prune out old libp2p-crypto and bring new js-ipfs) but I was afraid to actually move forward without tests.
Also, I don't have publish perms on npm. Mind sharing it with me?

Still no tests


go: Make socketConn.Close thread-safe

Client: go
We used to rely on setting the connection inside TSocket/TSSLSocket as
nil after Close is called to mark the connection as closed, but that is
not thread safe and causing TSocket.Close/TSSLSocket.Close cannot be
called concurrently. Use an atomic int to mark closure instead.

Quick question regarding 0.16.0: Wait for this to complete?

only atomic.CompareAndSwapInt32 is atomic, first load and later store is not

while technically that's correct, that doesn't matter here.
the problem we are solving is that inside TSocket.Close and TSSLSocket.Close, we call underlying socket's close, and set the underlying socket to nil. The race condition is about two goroutines setting the socket to nil concurrently, not about the socket's Close being called concurrently, as that's already supported by the stdlib.
so the fix here is that we use atomic int being set to non-zero to replace the old socket is nil check, and eliminate the race condition.
so we can still get into the situation that two goroutines call Close concurrently, they both pass the isValid check, and get to the point of setting the atomic int to 1. this is still fine because two goroutines calling store is fine (the winner change it from 0 to 1 and the loser doesn't really make any changes), and then they will both call the underlying Close and that's still fine (the winner will close the socket and return nil error, the loser will get an already closed error).
we can change it to compare and swap here, and return the already closed error here directly (like in the failed isValid check case), but the already closed error returned by the underlying Close function contains extra info about the connection itself, which is slightly better than the "naked" error we are returning here.


service create needs to accept alias

@al

@mgoelzer @al is this still relevant? can you provide more details if so?

I'm not the Al you're looking for I'm afraid.
On 29 Aug 2016 17:57, "Drew Erny"<EMAIL_ADDRESS>wrote:

@mgoelzer https://github.com/mgoelzer @al https://github.com/al is
this still relevant? can you provide more details if so?
—
You are receiving this because you were mentioned.

Ah sure I'm just glad to get the odd email :)
Keep up the good work all.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/swarmkit/issues/878#issuecomment-243190121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAApvy7823PAYA2EC758dhjaN-NQE2ckks5qkxRlgaJpZM4IxoFR
.


feat: add textencoder polyfill for react native

Closes #28 and #31
Added a polyfill for TextEncoder which doesn't seem to exist in the hermes JS engine used by expo/react-native

This adds 194k to the bundle. I think it's better to include polyfill instructions in the documentation than to bloat the bundle with this. Should we do that, instead?


In master, readtable with makefactors = true does not seem to produce the desired type

The type it does produce is
julia> typeof(df_in[:person_1_gender])
Array{Nullable{CategoricalArrays.CategoricalValue{String,UInt32}},1}

when it should, I think, produce a
CategoricalArrays.NullableCategoricalArray{String,1,UInt32}

Somehow the Nullable and Categorical properties are reversed.
I can look at this later in the week if no one beats me to it.

That may well indicate a missing conversion method in CategoricalArrays. These things are really complex to get right.

Can you post a reproducer? In my tests, this works correctly:
x = """
a,b
x,y
"""
d = readtable(IOBuffer(x), makefactors=true)
typeof(d[:a])

@dmbates Bump.

Seems okay now, thanks.


Add LookupTable - sampled from a LookupCurve for performance

LookupCurve should have a handy function to sample it to a LookupTable.
The LookupTable uses lerp internally to find_y_given_x.
Can be used as a more performant alternative. For example in shaders.

Closing this in favor of the Curve trait coming to Bevy, which allows this kind of thing.


Clarify the behavior of using multiple stacks per queue

@catkins wrote an internal post about scaling up redundant agents if you use multiple elastic stacks per queue. This change aims to use a stronger recommendation not to do that and clarify the behavior if you do.

@mbelton-buildkite this might be good to add to a FAQ. Working back from the effect to the cause, it would be something like:

Why are my stacks are scaling out but not running any jobs?
If you have multiple Elastic CI Stacks, check that they are listening to unique queues. This is determined by the BuildkiteQueue parameter. Each Elastic CI Stack that you launch through CloudFormation should have a unique value for this paramter. Otherwise, each of them will scale out independantly to service all the jobs on the queue, but the jobs will distributed amongst them. This will mean that your stacks are overprovisioned. This could also happen if you have buildkite agents that are not part of an Elastic CI Stack started with a tag of the form queue=<name of queue>. Any agents that are started like this could compete with and Elastic CI Stack for jobs, but the Elastic CI Stack will scale out as if this competition did not exist.

@mbelton-buildkite this might be good to add to a FAQ

@triarius, I've added a section in the troubleshooting page using the content you suggested


How to use the fixture in the new version

I found in the new version (2.0.10) has been fully using the Codeception framework, but the official document of the fixture does not seem to update, I hope to be able to get on the testing document, only from the Codeception document on how to find more about Yii2 and the results of the case, especially in the use of fixture.

please tell us what to improve on docs after reading the following resources?

http://www.yiiframework.com/doc-2.0/guide-test-fixtures.html
http://danaluther.blogspot.nl/2015/12/testing-in-yii-20-with-codeception.html

I see these documents are based on the YII2 library yii\test\InitDbFixture, but the new version has not been used in it, I do not know what is the intention? I imagine the simple use of PHPUNIT, you can go to the database in each test case to fill some data, how to do it?  Can you please elaborate in more detail on what are you trying to achieve and what is preventing you from doing so.

Please forgive my poor English ^_^, I wrote a test case, I think at this point what to do before the execution of the function, actually want to notice to insert some data into MySQL. I would like to use the fixture to solve, but the effort has not been successful for a long time.

functional or unit tests?

unit tests

in the past, I used fixtures for that. But after a while I concluded that this was not optimal for several reasons.:

The unit tests we're too much entangled with 'fixture' logic
Unit tests are more difficult to manage/update
You always have to go to the fixtures to understand which data was used
Its was error prone when multiple tests use the same DB data

After a long research, I concluded it was way more useful to put it all in the test method itself. Similar like PHPunit's getMock(). In the beginning of the test method, you prepare the data. And then you test it. Its easy to grasp and to manage. Its not entangled with other parts of your test suite and self contained. An example:
class ArticleTest extends AppTestCase
{
    public function testSave()
    {
        $identity = $this->mockLogin();
        $model = new Article([
            'title' => 'Test',
        ]);
        $model->save();

        $this->assertEquals('test', $model->slug);
        $this->assertEquals($identity->id, $model->created_by);
        $this->assertEquals($identity->id, $model->updated_by);
        $this->assertTrue(is_int($model->created_at));
        $this->assertTrue(is_int($model->updated_at));
    }
}

One can argue, would this go at cost of performance? Well, if you are either setting them up with fixtures at the beginning of your run or during the testMethod, doesnt really make a difference. Actually, when testing a method only, its way more faster than a site wide fixture setup. And when you are using SQLite for your testsuite (which I am recommending anyone), performance isnt even a subject on the agenda anymore for record insertion.

You mean if I want to test a query function, I can write like this:
class ArticleTest extends AppTestCase
{
    public function testFind()
    {
        $model = new Article([
            'title' => 'Test',
        ]);
        $model->save();

        $articleModel = $model->findOne('1');
        $this->assertEquals('Test', $articleModel->title);
    }
}

Do I understand correctly?

A few important improvement:

you run in to the risk that other models are already exist in the DB if you specify a ID manually
its better to seperate the $config variable if you use it later in the assertions (static state)
its better to name variables to their state (in this case dbModel)

class ArticleTest extends AppTestCase
{
    public function testFind()
    {
        $config = [
            'title' => 'Test',
        ];
        $model = new Article($config);
        $model->save();

        $dbModel = Article::findOne($model->id);
        $this->assertInstanceOf(Article::className(), $dbModel);
        $this->assertEquals($config['title'], $dbModel->title);
    }
}

ok, thanks!!!


Naming convention for extractors

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 this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.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 2018.12.09

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] 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)
[x] Question
[ ] Other

Description of your issue, suggested solution and other information
What is the naming convention for extractors, and should we standardize current ones?
Examples:

[sitename:typeofcontent] [youtube], [youtube:playlist]
[Sitename:typeofcontent] [Bandcamp:weekly]
[SitenameTypeofcontent] [PornHubPlaylist]

No convection, it's just a display name.
No.


Add MarkdownEditor tests

Pre-Flight checklist

[x] Testing

[x] Code is tested

What are the relevant tickets?
Fixes #138
What's this PR do?
Adds a couple tests for MarkdownEditor, mocking out ckeditor to avoid complications with it. We already have tests for the other custom components so this should complete the issue.
How should this be manually tested?
Tests should pass

Codecov Report

Merging #330 (b5178e2) into master (4235050) will decrease coverage by 2.66%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #330      +/-   ##
==========================================
- Coverage   88.18%   85.52%   -2.67%
==========================================
  Files         123       63      -60
  Lines        3700     2356    -1344
  Branches      563      259     -304
==========================================
- Hits         3263     2015    -1248
+ Misses        398      304      -94
+ Partials       39       37       -2

Impacted Files
Coverage Δ

static/js/components/SiteContentEditor.tsx

static/js/pages/SitesDashboard.tsx

static/js/reducers/index.ts

static/js/types/forms.ts

static/js/hooks/tracker.ts

static/js/components/PaginationControls.tsx

static/js/components/forms/FormError.tsx

static/js/components/widgets/MarkdownEditor.tsx

static/js/components/widgets/ObjectField.tsx

static/js/util/incrementer.ts

... and 50 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4235050...b5178e2. Read the comment docs.


Off by one error; grid layout was capped at 8 participants for 3x3

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


Support for 3rd-party reporters?

See https://github.com/shyiko/ktlint/issues/176.

Would it work for you if I directly support https://github.com/mcassiano/ktlint-html-reporter (with the author's permission of course) as reporter for 'html'?
I could make it extensible with providers the way rule sets are, but I suspect it is a less common use case and I'm shooting for "simply works out of the box" for the most part with this gradle plugin.

That would work for me, and I think it makes sense in this case. An html reporter would be super useful out of the box.

Guys,
this is not stated in the ktlint's README (even though it should) but reporters are loaded using ServiceLoader same as rulesets. In other words, as long as jar containing Reporter implementation is on the classpath it will be loaded.
This is why something like
dependencies {
    ktlint "com.github.shyiko:ktlint:0.20.0"
    ktlint "com.github.mcassiano:ktlint-html-reporter:master-SNAPSHOT"
}

task ktlint(type: JavaExec, group: "verification") {
    description = "Check Kotlin code style."
    classpath = configurations.ktlint
    main = "com.github.shyiko.ktlint.Main"
    args "--reporter=html", "src/**/*.kt" # notice that no artifact=... is needed
}

should work (same applies to Maven). By extension, https://github.com/jeremymailen/kotlinter-gradle#custom-rules can be used for the same purpose.
This is for your information only. I'm not advocating any particular implementation (or a lack thereof).

Hey! I was going to publish this later on but there were some things I was trying to investigate further.
I'm not sure I was doing something wrong but loading the reporter from jar was not working. My guess is that in line 378 the wrong id is being used to query the map (it's using the id passed on as an argument, which in this case is a path), when it should be using ReporterProvider.id. I didn't have time to check if that's what's happening but I'd gladly open an issue and PR to ktlint if that's the case. (ping @shyiko)
What I did to use this in a project was loading the jar as a ruleset (it only loads the jar) and then passing  ReporterProvider.id of my reporter as an option (--reporter=html,output=${buildDir}/ktlint.html) which, I know, IS VERY HACKY. haha

Oh, I see, you fixed the bug! Nice.

Available now in https://github.com/jeremymailen/kotlinter-gradle/releases/tag/1.11.0

Thanks!
Configuring it now, and I'm considering elaborating on the solution to allow for a single report for all source sets, and/or a single report for multiple modules. Just to make configuring Jenkins a bit easier. Will update you if that ever happens :)


Refreshing one notebook, another notebook's gridwidth effect will dissapear

I recorded a gif as follows. A weird behavior (under newest version 0.2.1) ...

If the gridwidth effect is ineffective, the button will change the metadata, but the cell width is locked to full width. The following is another gif screenshot with button clicked and cell metadata obeserved.

can you please run
pip install -U jupyterlab-celltagsclasses

and try again ?

Works fine now by upgrading jupyterlab-celltagsclasses :) Thanks a lot!


Unique exception for cancelled tasks

Hi, thanks for the great package! Simple and very easy to use.
It would be nice to have a different exception thrown when tasks are cancelled when turnOff is called so a cancellation can be separated from exceptions thrown in the compute function.

@JetA2 Hi. Is this issue relevant for you now?

Hi, yes I'm still using your package so it would be a nice addition.

@JetA2  Sorry for the long wait https://github.com/91team/computer/pull/16.
3.2.0 in the pub

Nice, many thanks!

The exception works great but it's not exported, therefore the import 'package:computer/src/errors.dart' is needed.
This works fine but produces a linter recommendation (https://dart-lang.github.io/linter/lints/implementation_imports.html).
While everything still works it would be nice to have the exceptions exported to silence this recommendation.


Enable deployment of landing zones from Rover to multiple subscriptions

Is your feature request related to a problem? Please describe.
It seems that the Launchpad (Rover) and CAF Terraform Landing Zone examples are based on a single subscription model.
There are scenarios where it would make sense to support deployment of landing zone to a different subscription, for example setting up central logging and monitoring ("caf foundations"), so they would reside in separate subscription from production subscription. This could also include something like logging policies enforced on Management group level.
Are there plans to support deployment over several subscriptions from a single Launchpad (Rover)?
Describe the solution you'd like
rover /tf/caf/landingzones/landingzone_caf_foundations plan -var 'target_subscription_id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'

Describe alternatives you've considered
Currently, it seems that one should stick with just one "primary subscription". Launchpad (Level 0) is tied to a single subscription and the other Levels along with it.
If deploying resources to multiple subscriptions they're considered separate environments and each have their own launchpads.
Additional context
Single subscription model:
https://docs.microsoft.com/fi-fi/azure/cloud-adoption-framework/ready/landing-zone/terraform-landing-zone#design-decisions
Networking for spokes:
https://github.com/Azure/caf-terraform-landingzones/blob/master/landingzones/landingzone_hub_spoke/readme.md#introduction-to-hub-spoke-network-topology-in-azure-landing-zone

I kinda figured this out on my own.
Terraform supports this out-of-the-box:
https://www.terraform.io/docs/configuration/modules.html#passing-providers-explicitly
I wanted to deploy the Azure resources under "caf foundation" landing zone to a different subscription than where level 0 (launchpad) was provisioned.
This could be done my modifying the foundation LZ following way:
main.tf
`provider "azurerm" {
version = "~>2.4.0"
features {}
}
provider "azurerm" {
features {}
alias           = "foundations"
subscription_id = var.subscription_id
skip_provider_registration = "true"
}
...`
foundations.tf
`module "xxx" {
source                              = "./xxx/"
providers = {
    azurerm = azurerm.foundations
}

}`
This way I can control per module which subscription it targets. The subscription_id is passed in as an extra variable.

@Masahigo  can you provide a full example of this please. This would help many others like me who are stuck in deploying in single subscription.


Plugin is broken in Pipes Cloud

Describe the bug
Plugin is broken; queries (including datatank harvesting) error with
Error: rpc error: code = Internal desc = crtsh: rpc error: code = Internal desc = hydrate function listCertificate failed with panic setting PGSYSCONFDIR not supported (SQLSTATE HV000)

Steampipe version (steampipe -v)
Steampipe v0.22.0 locally, but this occurs in Pipes as well.
Plugin version (steampipe plugin list)
Unclear, this is running in Pipes
To reproduce
Query one of the tables provided by the plugin. For example:
select dns_names, not_after, not_before  from crtsh_certificate where query = 'turbot.com' AND not_after > now()

Expected behavior
The query returns results :)
Additional context
Add any other context about the problem here.

The query above is working for me in Pipes at the moment.
I suspect that it was a problem with the crt.sh service at the time you tried it?
crt.sh is unique in that the entire service runs off a Postgres database - including the HTTP layer! So, if you are getting Postgres errors while using it then it can (unexpectedly) be a problem on the crt.sh server side rather than on the steampipe side.
Could you please try again?

Hello @badideasforsale ,
Since we haven't received any further responses, and we are unable to reproduce the issue with the information provided, I will be closing it for now. If you encounter the same issue again or have any more details to share, please feel free to reopen this issue. Happy to help!
Thank you for reaching out, and we look forward to assisting you if you have additional questions👍.