text:
[NC | NSFS] WAL based tape migrations and recalls

Explain the changes
This PR adds WAL based migrations and recalls to NooBaa. The PR adds 2 commands manage_nsfs:

tape recall - Uses eeadm to restore all the files that were requested for restore.
tape migrate - Uses eeadm to migrate all the files to the tape.

NOTE: There were many races but now I hope I am dealing with all of them. What are the races I accounted for?

Multiple nodes issuing the migrate/recall at the same time (maybe cron doing it?).
Same nodes issue migrate and recall at the same time such that both of them interleave which is not problematic on the surface as they don't share the log but it is problematic because eventually they all deal with the same S3 objects. Imagine, (1) Upload a file to GLACIER (2) Issue a restore-object (3) Cron schedules tape recall as well as tape migrate (4) a file gets "recalled" but then is migrated.
A single instance of migrate is running (probably because WAL was huge and eeadm is slow) while another one got scheduled. Same for recall.

NOTE: This solution does NOT allow running tape recall and tape migrate at the same time. It is intentional. One call will block another.

[ ] Doc added/updated
[ ] Tests added

Ah, there is still one possible race here:

P1 opens a file
P2 renames the file
Someone issues a tape migrate which gets exclusive access to the recently renamed file
P1 gets blocked as tape migrate as the exclusive access
tape migrate unlinks the file on completion
P1 gets unblocked, happily performs write (the file won't be deleted as there is an open FD).
P1 closes the FD upon swap, the file gets deleted

RESULT: Lost writes.
Working on it now...

repo: noobaa/noobaa-core


text: IMAGE

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
文の途中でも行間が開いてしまう問題

「あああああああああ
　ああああ。
ああああああああ。」
ではなく
「ああああああああ
ああああ。
ああああああああ。」
と表示されてしまい読みにくい感じがします（自分だけ？）。
ただ、
・置換後の文字列をotayori_adjustedに代入
・行間調整
の処理順なので、うまい修正が思いつきません。

@kitokun
環境、条件、入力を教えてくだせえ

Windows/Chrome、（仕様の話なので環境は関係なさそう）
「朝起きたらとなりでルイズが寝ていた。
俺は死ぬほど嬉しかった。
何せ夢にまで見たルイズだ。
童貞の俺にもついに彼女が出来て幸せに暮らしてい
ける。
そしてマイホームを買って子供をつくって毎日幸せ
な生活をする。」
こうなっているのを
「朝起きたらとなりでルイズが寝ていた。
俺は死ぬほど嬉しかった。
何せ夢にまで見たルイズだ。
童貞の俺にもついに彼女が出来て幸せに暮らしてい
　ける。
そしてマイホームを買って子供をつくって毎日幸せ
　な生活をする。」
こうしたほうが読みやすくないですか？（文がつながってる場合は、行間を詰めたほうが読みやすそう）
という主張です。

「本来の文の改行」と「ブラウザの幅が原因の改行」の行間を変えたいという事ね。
調べたけど解決方法がわからなかったのでペンディングでお願いします。ｽﾜｾﾝ…

authors: kitokun norihitoishida

repo: norihitoishida/adjust-posts


text:
fix: BUG-8180/INC-B17940

Updated navigation to 'replace' so that ?code entry which in history with the intended new url without ?code

Hi @akshaykalaskar1,
So as I understand it, replace forces the page to reload and therefore running the process to remove code from the URL and load correctly.  Is that right?

source: gharchive/pull-request

repo: norm-l/odx


text:
Append custom regex to errorMatch for a project

Hi,
I am using a Makefile to compile an ocaml project. This makefile actually calls ocamlbuild, which is a wrapper around ocamlc/ocamlopt (the ocaml compilers).
The errors that are provided by those compilers follow this schema:
File "foo/bar.ml", line 277, characters 12-13:
Warning 26: unused variable g.
File "foo/bar.ml", line 280, characters 6-64:
Warning 34: unused type t.
File "foo/bar.ml", line 279, characters 0-6:
Error: Syntax error

I have a regex to match the warnings and errors:
(?<file>[\\/0-9a-zA-Z\\._\\-]+)", line (?<line>\\d+), characters (?<col>\\d+)-(?<col_end>\\d+):\\n(?<message>.+)

For the moment, I have a fork of build-make in which I added my regex to the errorMatch array.
I wonder if there is a way with .atom-build.{js,json,cson,yml} to specify my regex rather than to modify build-make?
I'm thinking about using preBuild to append my regex to the existing array, but I'm not sure this is the clean way to do it. Also, I would have to create a custom build command for all the targets in my makefile. This is not really convenient, I would like to use this regex for all the targets.
Or should I create a build provider for ocamlc/ocamlopt and even if I launch a make task, the regex from my provider will be applied? As my workflow (Makefile + ocamlopt) is common in the ocaml world, I would be happy to provide a solution that works for everyone.
I have the problem for ocaml now, but will probably have the same one with C/C++ or other languages/tools later. I am curious to know what is the best solution.
Also, subsidiary questions:

is there a way to display the warnings and the errors in a different way? (I suspect it is not possible because of this line)
can I access col and col_end from postBuild? I'd like to modify their value.

Thanks

Can you not make a PR to build-make with your regex?

Sure, I will do it today.

Oh, also saw your other questions now:

There is no way to differentiate between errors and warnings right now. I wouldn't mind a way of doing this, I just don't know the best way yet.
You cannot access col or col_end from postBuild, not change them either. Before enabling things like this I want to verify that it makes sense in all (at least most) scenarios. I haven't thought too much about what one might want to achieve in postBuild, it's a quite new feature.

Ok, thanks for the answers and for your great tool :)

authors: Khady noseglid

repo: noseglid/atom-build


text:
Preact compatibility

Would you be open for a PR to make it compatible with preact?
Just checking..

Unfortunately we have limited resource to make it work and keep update with all those awesome libs, so this is not in the plan yet.
Also sorry for the late response.

Close it for now.

authors: nosir viktor-izettle

license_source: bigquery


text:
How to check what moderator permissions client has?

I can see what permissions I (an account) has by GET to https://www.reddit.com/subreddits/mine/moderator/.json and looking at the property mod_permissions on each subreddit.
I don't see this available through getMe() or getModeratedSubreddits() in snoowrap. And the only place permissions are mentioned in typings is for inviteModerator()  and setModeratorPermissions() as arguments.
How, using snoostorm, can I check that the authenticated account has permission to perform mod actions on a subreddit other than just trying and seeing if i get a 400/401/403 back?

It is done like this:
// options to getModerators is optional but will ensure index 0 of the returned array is the user you are looking for
const mods = snoowrap.getSubreddit('mySubreddit').getModerators({name: 'modName'});
const modPermissions = mods[0].mod_permissions;

repo: not-an-aardvark/snoowrap

license: mit


text:
Develop

Added get_guest_user_ISE_API.py

Added Headlines to the exportet csv File


text:
feat: last-modified date colorizer

Adds ability to colorize by "last modified date".
Example: https://npmgraph-git-datecolorizer-npmgraph.vercel.app/?q=express#color=modified
I'm a little unsure whether to merge this.   The "Last modified date" is last time the package record was modified in the NPM registry.  That'll generally be the date of the last version that was published, but could also be something unrelated (e.g. when a version was unpublished, or an owner changed or... whatever.)  I'm concerned this could be more confusing or misleading than actually helpful.
Thoughts?

Closing unmerged.  This is going to be more confusing than it will be useful, I think.

repo: npmgraph/npmgraph


text:
Bug: audio player and web vr icon aren't showing up on mobile by default

rotating the device causes the controls to show up.

Fixed.

authors: TylerFisher lindamood

repo: nprapps/rockymountain


text:
Facebook login works, but profile view gives error in android emulator(works fine in plnkr, postman, even pasting url in browser)

I am able to login to Facebook and get back access_token , but when making angular $http request for viewing profile page, if throws error:
$http request code:
var url =  "https://graph.facebook.com/me?access_token=" + $localStorage.accessToken;
$http({
method: 'GET',
url: url
}).then(function successCallback(response) {
alert("success");
alert(JSON.stringify(response.data));
}, function errorCallback(response) {
alert("error");
alert(JSON.stringify(response));
});
above code works properly in plnkr, postman and browser but throws error in android emulator:
error:
"{"data":"","status":404,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"https://graph.facebook.com/me?access_token=*****","headers":{"Accept":"application/json, text/plain, /"}},"statusText":"Not Found"}",

adding this : ionic plugin add cordova-plugin-whitelist
solved the problem

repo: nraboy/ng-cordova-oauth


text:
URL without www loads page, but has a CORS error for the data.

I.e., visiting https://rustaceans.org/findwork rather than https://www.rustaceans.org/findwork (and presumably the http versions) loads the website, but is stuck at loading... forever becaue fetching the data gives a CORS error.

Similarly, navigating to the http site (http://rustaceans.org/findwork) will lead you somewhere else entirely.

https://github.com/aturon/rfcs/blob/roadmap-2018/text/0000-roadmap-2018.md links to the broken page...

authors: jwatt nrc skade

repo: nrc/find-work


text:
Rustfmt always recompiles

Rustfmt always recompiles on my machine, even if no source code has been altered. Is this happening for other people as well? If so, why does it happen and how can we prevent it?

It's also happening for me. It seems to be related to the build script. Commenting the line build=build.rs prevent the rebuild when nothing has changed. (I don't know why ?)

Interesting. Maybe it updates the last edit timestamp on default.toml in the root directory, which could trick Cargo into believing code may have changed?

Commenting the line std::fs::copy(in_file, out_file).unwrap(); doesn't change anything. It's maybe a default behavior of Cargo to rebuild everything when there is a build script... needs more investigation.

Weird -- commenting out that line does the trick here...

The source of trouble was a symlink rustfmt/rustfmt -> rustfmt/target/debug/rustfmt. Cargo seems to consider all files under rustfmt/ to decide when to rebuild.

Did you create this symlink by hand?

Unfortunately, https://github.com/nrc/rustfmt/pull/111 does not prevent recompilation one when of the test files in /tests/source/ or /tests/target/ changes... Any ideas on how we could fix that?

Yes, I created the symlink by hand (for tests, because cargo run recompiled always).
I don't know how to avoid rebuild when a non-source file is touched, but I have maybe an explaination why it occurs: the build script is intended to build external dependencies, but cargo doesn't which files the script builds, so it takes a conservative approach : rebuild if any file changed. If you remove the build script from Cargo.toml, a change in test files doesn't trigger rebuild anymore.
I think the good thing would be to remove the build script, and use something like a deploy script, but it doesn't seem to exist (yet ?). There is maybe another way : cargo is made to recieve build commands from the stdout of the build script, there are maybe commands to indicate dependencies (But at first sight there isn't anything like this in the docs.)

Removing the build script sounds good to me. Maybe we can add the default.toml to the root directory in the repository and also add it to .gitignore, so that editing it will not register as a change to the repository.

Might be worth asking on #cargo about this, seems like there ought to be a solution.

It's a known issue: https://github.com/rust-lang/cargo/issues/1162. No known workarounds at the moment. Maybe it's a nice issue to work on.

Build script was removed by #165.

authors: cassiersg marcusklaas nrc

repo: nrc/rustfmt


text:
Reviewers Doc

Need a doc for reviewers. Not only syntax but the spirit of the project. Focusing on the workflow rather than just "automating the network". Being neat with diagrams and examples. Not only for reviewers but also so contributors know what to expect. Convey that our goal is to make this the first impression for automators, so it has to preserve that.

Closing in lieu of #17

repo: nre-learning/antidote


text:
Is it possible to get help to create a new pull request?

Hello,
I would like to create new pull requests (for #356 and #332), but I am not familar with the branch/fork and pull technologies....
Is it possible to get help? (or better, someone creates the pull reqests directly!)
My changes are already well tested, a documentation is also availlable.
Regards
Ess Bee

Hi!
did you make your changes on a cloned Git repository of brouter-web?

Hi @EssBee59, the procedure should be:

Click on Fork button on https://github.com/nrenner/brouter-web/ page:

Then clone your repository locally with: git clone git@github.com:EssBee59/brouter-web.git
Modify the code as you wish.
Commit with it with a brief explanation of the changes: git commit -am "Improve voice hint generation. Fix #356" for instance.
Push it: git push
Create a pull request by opening https://github.com/nrenner/brouter-web/compare/master...EssBee59:master

And voilà!

As I am not familiar with repositories I have a local installation on my PC.
So I make the changes locally, and test locally first.
When the tests are succesfull, I install the "dist"  on an instance of brouter.de (brouter.de/essbee)
The changes are documented in both issues, by need I can deliver more documentation
Thank for your help and regards
Ess Bee

Maybe it's easiest to create an archive of your local BRouter installation and provide it as download or send it as mail attachment so that someone else can integrate the patches and create the pull-requests. I've some time tomorrow and would take a look if it's ok with you.

mjaschen,
Thank for your proposal, that I liked to accept!!
Please send me a mail addrees where I can send my changes
Reagrds
Ess bee

mjaschen@gmail.com should work :-)

Thank´s all for your help!

Some more information:
GitHub used to have nice, short step-by-step guides that I can't find anymore. They seem to have rewritten the docs, and now I fear this is too much for starting:
Collaborating with issues and pull requests - GitHub Docs
From a quick search this seems to be a nice guide:
How to make your first pull request on GitHub
There is also GitHub Desktop if you prefer using a UI over command line  (Windows and MacOS, also as Linux Fork):

Setting up GitHub Desktop and Git
Cloning and forking repositories from GitHub Desktop
Committing and reviewing changes to your project
Pushing changes to GitHub
Creating an issue or pull request (missing!?)

authors: EssBee59 bagage mjaschen nrenner

repo: nrenner/brouter-web


text:
[nrf fromtree] net: if: Extend the usage of rejoining the multicast groups

It may happen that the interface is up but not yet running when we issue the rejoin_ipv6_mcast_groups(). This can be fixed by calling this function again right after the iface is set to 'running' state in the notify_iface_up handler.
Signed-off-by: Marcin Kajor marcin.kajor@nordicsemi.no
(cherry picked from commit b571e45d80923a786979460f218618e2000da8f3)

Green light on the corresponding sdk-nrf PR. We can merge this one I guess.

repo: nrfconnect/sdk-zephyr


text:
hotfix: add try-catch in setTimeout/setImmediate

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[ ] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #748 (379e4b3) into release41 (c80781a) will increase coverage by 0.02%.
The diff coverage is 16.66%.

@@              Coverage Diff              @@
##           release41     #748      +/-   ##
=============================================
+ Coverage      69.86%   69.88%   +0.02%
=============================================
  Files            302      302
  Lines          34428    34434       +6
  Branches        4662     4664       +2
=============================================
+ Hits           24052    24065      +13
+ Misses          9925     9917       -8
- Partials         451      452       +1

Impacted Files
Coverage Δ

meteor/server/api/userActions.ts
20.97% <0.00%> (-0.28%)
:arrow_down:

meteor/lib/api/userActions.ts
100.00% <100.00%> (ø)

packages/job-worker/src/ingest/rundownInput.ts
78.33% <0.00%> (+2.07%)
:arrow_up:

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 c80781a...379e4b3. Read the comment docs.

authors: codecov-commenter jstarpl

repo: nrkno/sofie-core


text:
Repository transfer

Hi @mechairoi, I got this updated in the PureScript Registry quicker than expected. :-)
At this point, I would like to migrate the repository to a different namespace, e.g. purescript-contrib, rowtype-yoga, or similar. This can distribute the maintenance burden and avoid either of us being a "single point of failure".
In the interim, though, would you please transfer this repository to my username?
Thanks again!

Thanks @nsaunders. I'm grad to hear that.
I have requested to transfer the repository to you. I think it's a good idea to migrate to a namespace like those.
Thanks again for your contribution!

Thank you @mechairoi!

authors: mechairoi nsaunders

repo: nsaunders/purescript-unique


text:
SSH Deployer key based authentication not working

First things first: Thanks for this great plugin!
There seems to be a bug with SSH Deployer authentication when using SSH keys. Password authentication works fine, however, when selecting "Default Private Key" I can not enter a username with which to authenticate with the server (even if using a default private key, it's still mandatory for authentication to specify the user that should be used on the remote host).
It is also not possible to circumvent that problem by selecting "Custom Private Key" (with this it is possible to specify a user name) as the path to the "custom identity file" is incorrectly resolved. It always tries to find the path one specifies relative the to buildagent work dir instead of the home dir and it is not possible to specify an absolute path either as that always just get's appended to the current working dir. Hence, specifying something like ~/.ssh/id_rsa does not work. Using %agent.home.dir% doesn't work either (appends the home dir to the temp dir).

Bitbucket: https://bitbucket.org/nskvortsov/deployer/issue/23
Originally reported by: Sebastian Siemssen
Originally created at: 2014-01-07T14:29:06.547

fixed in this build

allow to enter username for default key
allow absolute paths to custom key

Original comment by: Nikita Skvortsov

repo: nskvortsov/deployer


text:
verifyCredentialsWithSuccessBlock not returning

So here goes - I had an old code of STTwitter not via cocoapods.
Using pods now.
The problem:
verifyCredentialsWithSuccessBlock not returning - not success block and not errorBlock.
It started with the latest version (0.2.1) so I thought it has something to do with the deprecation of the function.
Reverted to 0.2.0 (with patching of the extern to get it to link)
Still same thing.
When a user already logged-in in the past I'm saving it in UserDefaults and retrying with it with the following code.
Any assistance on investigating will be appreciated
NSUserDefaults *prefs = [NSUserDefaults standardUserDefaults];
NSString *oauthAccessToken = [prefs stringForKey:@"twitterAccessToken"];
NSString *oauthAccessTokenSecret = [prefs stringForKey:@"twitterAccessTokenSecret"];
NSString *key = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"twitterKey"];
NSString *secret = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"twitterSecret"];

if (oauthAccessToken != nil) //we are logged in
{

    STTwitterAPI *twitter = [STTwitterAPI twitterAPIWithOAuthConsumerKey:key consumerSecret:secret oauthToken:oauthAccessToken oauthTokenSecret:oauthAccessTokenSecret];
    [twitter verifyCredentialsWithSuccessBlock:
               ^(NSString *username) {
                                //great... do stuff and login to the app

                } errorBlock:^(NSError *error) {
                    NSLog(@"error verifying credentials: %@", error);
                    [self gotoLoginScreen];
                }];
}

I updated the code, still not working.
From what I was able to dig in the code:
successBlock(username, userID); (ln 247 - in the success block of verifyCredentialsRemotelyWithSuccessBlock)
Is getting called twice, with nil in username, and userID,
And only afterwards the GET request from twitter returns (ln 246 in STTwitterOAuth.m) and nothing is done with the result
Not sure why :(

I'm confused. The following code works for me with the latest version of STTwitter. Can you double check that you're also using it? (by typing git pull)
NSString *oauthAccessToken = @"";
NSString *oauthAccessTokenSecret = @"";
NSString *key = @"";
NSString *secret = @"";

STTwitterAPI *twitter = [STTwitterAPI twitterAPIWithOAuthConsumerKey:key
                                                      consumerSecret:secret
                                                          oauthToken:oauthAccessToken
                                                    oauthTokenSecret:oauthAccessTokenSecret];

[twitter verifyCredentialsWithSuccessBlock:^(NSString *username) {
    NSLog(@"-- username: %@", username);
} errorBlock:^(NSError *error) {
    NSLog(@"-- error: %@", error);
}];

If it still doesn't work for you, can you please setup a minimal Xcode project, so that I'll be able to reproduce and fix the bug? Thank you for your help.

sorry for the noob question - how can I git pull if I'm using pod?

maybe you can git pull somewhere else, replace your curren  STTwitter directory with the new one and run the project again

P.S. you can get a pod from GIT by doing:
pod 'STTwitter', :git => 'https://github.com/nst/STTwitter.git'
Anyway - a small project works, so it is not the code itself... I'll look for differences between the projects.
Do you think it is related to the fact that STTwitter used to be code in my project? (leftover frameworks?)

Well... after commenting out the verifyCredentialsLocallyWithSuccessBlock to see if it works and figuring out it is still gets executed I just removed all pods and podCache - reinstalled, and now everything works....
I hate Cocoapods!!!!
Well, thanks again! I believe we found a real bug in the process so it wasn't all for nothing...

Glad to hear that.
Don't hesitate to report any other issue you may find in the future.

authors: boazin nst

repo: nst/STTwitter


text:
License

Thanks for creating this library, it looks nice and simple to use 👍
I notice the mix.exs file says the license is MIT, but I don't see a LICENSE file in the repo.
Could you add one just to clarify.
Thanks again!

Thanks for the heads up @mbuhot. Missing LICENSE has been added. Will be available in the next hex release.

authors: mbuhot nsweeting

repo: nsweeting/authex


text:
Add cyrillic letters to sort tests

Fixes https://github.com/nt4f04uNd/sweyer/issues/158

Thanks for adding the tests.

Thanks for making them =)

I've seen this CI failure before, but I can't replicate it locally. My guess is that we start the initialization in a test, and then the test ends but the while the initialization is waiting on an await point and we start a new test overwriting the queue controller. For now I think you can just re-run the test, but a real solution it to either find a way to cancel / await all un-awaited futures started or to not have singletons and instead pass in all controllers when creating the app.

Created an issue https://github.com/nt4f04uNd/sweyer/issues/162


text:
ResultView: Add action panel to text/html output

Closes #26
Just make the pre element clickable if it's a single line output.

I see a bug but I can't reproduce it reliably.
When it fails:

When it works:

The logs in the dev console look the same.
I will look at this more carefully. But I'm not sure if I'll be able to look at this tomorrow.

Thanks for taking a look.
I can't reproduce this. I always get the second output no matter how many times I try.

It happens more often when I use C-A-enter.

Strangely enough this doesn't happen on my machine.

Does it happen when you add back the previousText check at line 111 like this?
previousText = @getAllText()
container.appendChild htmlElement

if mimeType is 'text/plain'
    text = @getAllText()
    if previousText is '' and text.length < 50 and text.indexOf('\n')

@lgeiger I that was it. After adding the check, I don't it to fail.

It should work now.

I think it's easier for the user to be able to click anywhere container.
Another problem with the pre hack is that it breaks when a block with multiple stdouts is executed, e.g.:
print('A plot')
plt.plot(t, s)

OK I'll revert my changes except those directly related to #26.

All right, back to the basics :wink:

LGTM

authors: lgeiger n-riesco

repo: nteract/hydrogen


text:
Provide cell corners

Moin Nicolas,
First of all, thanks a lot for providing the healpix package!
To add HEALPix support to UXarray, an xarray extension for unstructured grids, we need a function that computes the vertices, and ideally also a mapping of the vertices to the cells.
I've played a bit with the healpix package, and found that the _uv functions will provide the corners if supplied with the correct arguments, as in this gist. From there, one can move on with unique functions as in this gist by @philipc2.
I'm sure this is not the most efficient way of generating the vertices, but I was wondering if you would be interested in supporting this operation in your library. I'd be more than happy to create a merge request if that helps.
Pinging @philipc2 and @erogluorhan, as they are core developers of UXarray.
Cheers
Flo

Hi Flo!
Thanks for getting in touch. It would be great if we added add a healpy-compatible function such as
def boundaries(nside, ipix, step=1, nest=False):
    ...

to the code. In the first instance, I think that using the pix2ang_uv functions at the Python layer, as in your examples, is perfectly fine. In a second step, it could make sense to add the boundaries() function directly to the C library. That might save a bit of overhead -- but it would anyway be good to have the Python functions in place to make the comparison.
How does that sound?

Thanks for pinging me @florianziemen!
We are excited to use this package to add support for HEALPix within UXarray. To add onto what Flo already mentioned:

UXarray is written around the UGRID conventions, which requires at least the vertices (node_lon, node_lat) and cell- vertex indicies(face_node_connectivity) to represent an arbitrary 2D unstructured grid. This would be for loading a HEALPix grid into UXarray.
Going the other way, converting from UGRID to HEALPix can be achieved using a nearest neighbor remap, however for conservative remapping, knowing the boundaries is important

Hi,
sorry for the late reply. I've been at the AGU conference and took a couple days off afterwards. I've looked into the boundaries function. In principle, I know what to do to replicate it. I'm not sure, we want to mimic exactly this function, as it kind of assumes a single point going in, and only goes to xyz (if I remember correctly).
Basic thought would be to provide the behavior of boundaries with a signature that's matching the original call for compatibility, and provide a second function, that produces angles in (theta/phi) and (lon/lat) notation.
I won't manage to do this before the holidays, but it's high on my todo list for early next year.
Cheers
Flo

authors: florianziemen ntessore philipc2

repo: ntessore/healpix


text:
Speed up generate function

Describe what you would like to achieve
Provide a mechanism to speed up generation of large numbers of prefixes or ASNs.
Describe why the current solution (if any) is not satisfactory
When passing a large number of ASNs or Prefixes to the generate function, the process takes several hours.
Provide an example
time ./bin/bgpalerter-macos-x64 generate -m -l .output/prefixes.txt -o output/prefixes-test.yml
real    245m27.073s
user    8m16.969s
sys     1m10.959s

Your information
Ryan Harden: AS11537

Hi @ancker010,
What does prefixes.txt contains and how many ASes are you monitoring?

prefixes.txt is a list of prefixes, one per line, currently 6887.
And approximately 1045 ASNs.

repo: nttgin/BGPalerter


text:
请问一下如何将表中的英文修改为中文的形式？

我使用了 listings 这个包，然后按照这个格式插入了一串代码：
\begin{lstlisting}[caption={不透明谓词示例一}, label={tab:opaque1}, frame=single]
xxxxxx
\end{lstlisting}

编译后生成的是这个格式：

我希望将其中的 Listing 改为中文该怎么做呢？

另外好像不管怎么设置 label 都不会被 \autoref 引用

目前模板没有适配常用宏包（偷懒的借口），你可以在 global.tex 里加上：
\renewcommand{\lstlistingname}{演算法}
\newcommand\lstlistingautorefname{算法}

当然，上面的名字只是示例，请根据自己的需求，修改成合适的名字。

非常感谢！

repo: nuaatug/nuaathesis


text:
Switch to Encodable for JSONification

Now that Swift 4 is out, we have Codable!  Yaaaay!
Except that it wasn't meant for situations where you use some structs and some random dictionaries.  It really doesn't like trying to encode [String: Any]s or even [String: Encodable]s (trying to encode either with the default implementation throws a FatalError saying fatal error: Array<Encodable> does not conform to Encodable because Encodable does not conform to itself. You must use a concrete type to encode or decode.)
Is the new implementation hackish?  A little.  But I think it's a little less hackish than the one it's replacing.  Also, we can finally follow the Swift API Guidelines on acronyms (I'm talking about you, Id and Url) without an overly complicated snakecase function (though that's not implemented here).

Yeah whenever conditional conformance arrive it should get rid of the hacky things we have to here since it'll let them handle these in the stdlib

@tellowkrinkle Have you toyed around with trying bring deserialization to the holding types? It would be fantastic if we could get rid of all that crufty stuff we have now.

Although thinking about it more I guess conditional conformance really won't help with the case where it's just Any... since it can't know what to encode. And toying around it doesn't look like you define a custom protocol that just declares Codable conformance to use, which is kind of a bummer.

I haven't looked into deserialization much yet.  I do know that Codable doesn't support autogenerating with defaults, so we'll still need to manually implement init(from decoder:).

authors: nuclearace tellowkrinkle

repo: nuclearace/SwiftDiscord


text:
fix: add type to favicon field

resolve #146
Adds the image type to the favicon field

Thank you!

authors: nobkd tipiirai

repo: nuejs/nue


text:
chore: exclude examples and docs from triggering test run

https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore

Good change


text:
🛑 Università e ricerca is down

In 088f9e3, Università e ricerca (https://www.mur.gov.it/it) was down:

HTTP code: 403
Response time: 689 ms

Resolved: Università e ricerca is back up in d4b33a1.


text:
🛑 Difesa is down

In aea87c5, Difesa (http://www.difesa.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Difesa is back up in 8d309f6.


text:
🛑 Cultura is down

In 5cb2ed6, Cultura (https://www.beniculturali.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cultura is back up in 1efe2bd.


text:
🛑 Difesa is down

In b4ef3ce, Difesa (http://www.difesa.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Difesa is back up in 8803e48 after 153 days, 9 hours, 17 minutes.


text:
🛑 Guardia di Finanza is down

In 10874ed, Guardia di Finanza (https://www.gdf.gov.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guardia di Finanza is back up in 0b35dd0 after 49 minutes.


text:
🛑 Guardia di Finanza is down

In c1a87d5, Guardia di Finanza (https://www.gdf.gov.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guardia di Finanza is back up in 325fea5 after 16 minutes.


text:
🛑 Guardia di Finanza is down

In 05de9a3, Guardia di Finanza (https://www.gdf.gov.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guardia di Finanza is back up in e11f053 after 5 minutes.


text:
Add: data_backup, ime_incognito to Thai's i18n

Added "data_backup" and "ime_incognito" Translations to Thai's i18n

69th commit, Nice :)

In this pull request

Localization

Add: data_backup, ime_incognito to Thai's i18n
Fully Translated Japanese

Thank you!

authors: nullxception rinme

repo: nullxception/boorusphere


text:
Component Testing for Python SDK

Summary
What change needs making?
Use Cases
When would you use this?

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Yeah we need some better tooling and developer experience on testing.
But it's hard to know what's in the making when only issue titles are filled.
Please include community so we can help you grow. 🙂

Indeed very hard to tell from "test" labels whether is related to numaflow core tests (go/sdk), or test framework for users (pipelines/udf).

We usually tag area/sdk when it is SDK related.

repo: numaproj/numaflow


text:
AWS SQS source and sink

Is your feature request related to a problem? Please describe.
Would be useful to be able to source events from AWS SQS.
Describe the solution you'd like
A source that turns GCP Pub/Sub events into messages for further processing.
Describe alternatives you've considered
None
Additional context
None

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@shubhamdixit863 once you complete the issues listed in https://github.com/numaproj-contrib/aws-sqs-source-go/issues, please go ahead and close this.

Completed! SQS Source and SQS Sink


text:
np.linalg.solve unexpectedly returns an F_CONTIGUOUS array for C_CONTIGUOUS inputs

Reporting a bug

[X] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[X] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Reproducer
import numpy as np
from numba import njit

def f(x, y):
    return np.linalg.solve(x, y)

if __name__ == "__main__":

    x = np.array([[1, 2], [3, 5]], dtype=np.float64)
    y = np.eye(2, dtype=np.float64)

    g = njit()(f)

    numpy_result = f(x, y)
    numba_result = g(x, y)

    print(numpy_result.flags)
    print(numba_result.flags)

This prints the following:
  C_CONTIGUOUS : True
  F_CONTIGUOUS : False
  OWNDATA : True
  WRITEABLE : True
  ALIGNED : True
  WRITEBACKIFCOPY : False
  UPDATEIFCOPY : False

  C_CONTIGUOUS : False
  F_CONTIGUOUS : True
  OWNDATA : False
  WRITEABLE : True
  ALIGNED : True
  WRITEBACKIFCOPY : False
  UPDATEIFCOPY : False

I am not sure if this is the expected/desired behaviour. I encountered this when attempting to feed the results of np.linalg.solve into np.dot and saw:
NumbaPerformanceWarning: np.dot() is faster on contiguous arrays, called on (array(float64, 2d, A), array(float64, 1d, C))

Thanks for the report. Given what Numba's implementation of np.linalg.solve does this is not surprising, however it is a bug as it ought to match NumPy.

I actually encountered the same issue, but with np.linalg.qr function. Are there any workarounds for this?

authors: JSKenyon stuartarchibald vroomzel

repo: numba/numba


text:
Fix typo(s).

For most cases in typeinfer.py, the word 'constrain' should actually be 'constraint'.

Yes, I've always been a bit confused by that :)

authors: pitrou stefanseefeld


text:
Require student to specify units in number entry parts

There should be an option to make the student specify the units of their answer. For example, make them type "50g" instead of just "50".
Options:

name of unit (g,s,N, etc.)
allow SI orders of magnitude? (i.e., student can enter either "5000g" or "5kg" and be marked correctly)
which alternate names do you allow? (e.g. just "kg", or "kilos" or "kilograms" or "kilogrammes")

Will have to hardcode most units - need to know all the names for different SI units. Or, have presets that can be modified.
Maybe give a list of units and a scaling factor. For example:

(g or grammes or grams) * 1
(kg or kilogrammes or kilograms or kilos) / 1000
(mg or milligrammes or milligrams) * 1000

Some unit systems are more complicated!

Currencies go in front: "£3.50", except for
Geographical coordinates have several components: "66°33’ N", 1° = 60’ = 3600”.

Should extend the TNum type to have a "units" property, describing the units the number was given in.
While doing this, maybe we should also deal with different decimal notations - see https://en.wikipedia.org/wiki/Decimal_mark#Examples_of_use
If we hardcode the units, need to make it easy to add more for international users or new subjects.
How complicated do we want to get with combinations of units? Need to do at least things like "m/s ms^-1" and "m/s^2 = ms^-2". Can all units be expressed as a product or ratio of other units?
See http://www.boost.org/doc/libs/1_37_0/doc/html/boost_units/Dimensional_Analysis.html for an existing implementation.

Fields to add to the number entry part:

expected units (string, not necessarily directly shown to the student - complicated schemes like geographical coords will need a name like "latitude", which tells the part how to format the expected answer)
allow different orders of magnitude? (i.e., allow "kg" as well as "g")
partial credit if units not given, and a feedback message
allow alternate names? (i.e., allow "grams" as well as "g", or "l" as well as "cm^3") - maybe this should be a list of allowed units

Another point: if we're adding dimension information to TNum, should addition and subtraction fail when attempted on incompatible measurements, and how should they be combined for multiplication and division?

Rink is an existing calculator which might work as a reference https://github.com/tiffany352/rink-rs/wiki/Rink-Manual

The % symbol behaves a lot like a units symbol.

JS-quantities looks like a decent JS unit-handling library.

There's now a quantities extension.

repo: numbas/Numbas


text:
Use multiple columns or something like that for contributor list

The contributor list is getting long. That's a good thing, but presented as a single-column list it's leaving a lot of whitespace on the About page. I recommend going to multiple columns, or just a comma-separated paragraph format, or something else space-efficient, if it grows much more. Certainly if each member of the  Delft team is added individually to the list, that wold be the time to fix that formatting.

Should be incorporated in overhaul of docs for alpha.

Fixed in ui2 per #464, closing.

repo: numberscope/frontscope


text:
Return testdox as test name

Return name generated for phpunit from testDox. This add possibility to rename test name with @testdox annotation.

No plans for changing this, sorry.

Hi, I currently use @testdox to describe my tests as it gives me a clearer interface. Is there any way to display it with the art test command. Currently if I set it as parameter art test --testdox the coverage functions do not work.
Example
art test --testdox --coverage --min=100.
This example does not work.
With the change I proposed it would work exactly the same for the current test suite and also the @testdox annotation would work.
How could I fix this?
Thanks.
Translated with www.DeepL.com/Translator (free version)

repo: nunomaduro/collision


text:
Fix unquoted command args with leading +

This PR fixes #131  by grouping "+/-" and digits in decimals.
Related test cases in cmd-026-unquoted-string-with-leading-plus.

Thanks!

authors: blindFS fdncred

repo: nushell/tree-sitter-nu


text:
jenkinsx-quickstart-nuxeo-poc to 1.0.11

Promote jenkinsx-quickstart-nuxeo-poc to version 1.0.11

 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.jenkins-x-bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant mcedica

repo: nuxeo-sandbox/environment-jx-staging


text:
feat: create jest preset

Jest preset for @nuxtjs/module-test-utils
// jest.config.js

export default {
  preset: '@nuxtjs/module-test-utils'
}

@pi0 Add something else to the preset?

repo: nuxt-community/module-test-utils


text:
Add vueI18nLoader to AllOptionsInterface of types

Add vueI18nLoader to AllOptionsInterface of types.
Because Options has vueI18nLoader.
https://nuxt-community.github.io/nuxt-i18n/options-reference.html

Thank you.

authors: munierujp rchl


text:
feat: cache management

nuxt-hub/platform#152

@Atinux The tests were passed by recreating the pnpm-lock using pnpm@9.

repo: nuxt-hub/core


text:
_ctx.$localePath is not a function

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.5.3
Nitro Version:    2.4.1
Package Manager:  npm@9.4.2
Builder:          vite
User Config:      modules
Runtime Modules:  @nuxtjs/i18n@8.0.0-beta.12
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-6vqdsb?file=app.vue,package.json,nuxt.config.ts
Describe the bug
According to documentation available at https://v8.i18n.nuxtjs.org/guide/migrating#change-some-export-apis-name-on-nuxt-context it seems that API methods have to be prefixed with $, however it results in 500 error (_ctx.$localePath is not a function).
This works, but shows type error in VSCode

This does not work and results in 500 error

This does work

Additional context
No response
Logs
No response

any updates on this? Having the same problem...
As a workaround i use <nuxt-link-locale>, which just works.
Components · @nuxtjs/i18n

still same problem exist if $localePath used outside of setup.

authors: antlionguard fabkho simkuns


text:
nuxt 3 module i18n dont working

Environment

Operating System: Linux
Node Version:     v18.16.0
Nuxt Version:     3.6.1
Nitro Version:    2.5.2
Package Manager:  pnpm@8.5.1
Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/productdevbook/i18n-bugs-layer
Describe the bug
pnpm install
pnpm dev admin
✔ Nitro built in 364 ms                                                                                nitro 11:55:20 AM
[intlify] Not found 'hello' key in 'en-US' locale messages.                                                                                11:55:21 AM
[intlify] Fall back to translate 'hello' key with 'en' locale.                                                                                11:55:21 AM
[intlify] Not found 'hello' key in 'en' locale messages.                                                                                11:55:21 AM
[intlify] Not found 'hello' key in 'en-US' locale messages.                                                                                11:55:21 AM
[intlify] Fall back to translate 'hello' key with 'en' locale.                                                                                11:55:21 AM
[intlify] Not found 'hello' key in 'en' locale messages.                                                                                11:55:21 AM
Additional context
pnpm install
pnpm dev admin
Logs
No response

Same here. All packages default (using Nuxt Content).

I got the same problem and tried nuxi upgrade --force once again (even though I updated the day 3.6.1 released) and it worked, dunno what happened tbh.

I got the same problem and tried nuxi upgrade --force once again (even though I updated the day 3.6.1 released) and it worked, dunno what happened tbh.

I updated the repo as you said, still the same problem persists.

Hi!
I’ve checked your minimal reproduction repo.
I’ve noticed that you need to set up two things to make nuxt i18n work with nuxt layer.
1. set your custom nuxt module at modules options
You need to set your nuxt module defined in the nuxt layer (layer dir) of the layer dir to nuxt.config.ts as follows
// https://nuxt.com/docs/api/configuration/nuxt-config
import MyModule from './module'
export default defineNuxtConfig({
  modules: [
    // https://i18n.nuxtjs.org/
    MyModule,
    '@nuxtjs/i18n',
  ],
  devtools: { enabled: true }
})

It seems that the nuxt layer does not automatically install a custom nuxt module if you just define one.

configure i18n options

For nuxt application (admin dir) that extend the nuxt layer, the i18n options must be set as follows. The following is a case where lazy loading is used.
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  extends: [
    '../layer'
  ],
  // see the docs: https://v8.i18n.nuxtjs.org/guide/layers
  i18n: {
    lazy: true,
    langDir: 'lang',  // need `lang` dir on `admin`
    locales: [
      {
          code: 'en',
          file: 'en.json',
      },
      {
          code: 'fr',
          file: 'fr.json',
      },
    ]
  }
})

If lazy loading is not used, at least the locales option must be defined; if locales does not have resource definitions in files, an empty array must be defined in files.
@BobbieGoede
If you have anything to add about the layer of nuxt i18n module, please comment. 🙏

Now that #2290 has been merged the configuration @kazupon described in step 2 are not necessary anymore. All you have to change in your reproduction is registering your module as mentioned.
I have changed your reproduction to demonstrate it works with the edge channel installed (I registered the module by putting it in a modules folder) check it out here.
Please let me know if you're still experiencing any issues even with the latest edge version installed!

@BobbieGoede

same repo nuxt 3.7.1 dont working
    "@nuxtjs/i18n": "8.0.0-rc.4",

It is not working, if the Layer is installed as node dependency.
https://github.com/nuxt-modules/i18n/discussions/2388
Should we start a new Issue or reopen?

authors: BobbieGoede Tigriz derHodrig kazupon productdevbook thaikolja


text:
500 init is not a function

Version
@nuxtjs/strapi: v1.5.0
nuxt: v3.0.0-rc.4
node: v16.16.0
strapi: v4.3.6
Linux Pop_OS 20.04
Reproduction Link
https://github.com/FKonig/NuxtStrapi_Bug
Steps to reproduce
Normal minimal installation like in the linked repo.
Opening http://localhost:3000 -> 500 init is not a function
What is Expected?
Successful start of the application
What is actually happening?
Browser:

Terminal:
[nuxt] [request error] init is not a function
  at Module.useState (./.nuxt/dist/server/server.mjs:993:26)
  at Module.useStrapiUser (./.nuxt/dist/server/server.mjs:3184:51)
  at Module.useStrapiAuth (./.nuxt/dist/server/server.mjs:3053:38)
  at ./.nuxt/dist/server/server.mjs:3020:47
  at fn (./.nuxt/dist/server/server.mjs:434:27)
  at Object.callAsync (./node_modules/unctx/dist/index.mjs:42:19)
  at callWithNuxt (./.nuxt/dist/server/server.mjs:436:23)
  at applyPlugin (./.nuxt/dist/server/server.mjs:391:29)
  at Module.applyPlugins (./.nuxt/dist/server/server.mjs:401:11)
  at async createNuxtAppServer (./.nuxt/dist/server/server.mjs:46:7)
[nuxt] [request error] init is not a function
  at Module.useState (./.nuxt/dist/server/server.mjs:993:26)
  at Module.useStrapiUser (./.nuxt/dist/server/server.mjs:3184:51)
  at Module.useStrapiAuth (./.nuxt/dist/server/server.mjs:3053:38)
  at ./.nuxt/dist/server/server.mjs:3020:47
  at fn (./.nuxt/dist/server/server.mjs:434:27)
  at Object.callAsync (./node_modules/unctx/dist/index.mjs:42:19)
  at callWithNuxt (./.nuxt/dist/server/server.mjs:436:23)
  at applyPlugin (./.nuxt/dist/server/server.mjs:391:29)
  at Module.applyPlugins (./.nuxt/dist/server/server.mjs:401:11)
  at processTicksAndRejections (node:internal/process/task_queues:96:5)

Hello FKonig,
I just cloned your reproduction repository.
Unfortunately it works fine on my machine.
If you use an functions from the @nuxtjs/strapi repo please consider this issue: #282 and there is an open pull request for this bug: #281

authors: FKonig Mechse

repo: nuxt-modules/strapi


text:
Release v1.0.0

Resolves #209
Resolves #185
Resolves #207
Resolves #163
Resolves #203
Resolves #153
Resolves #179
Resolves #137
Resolves #147
Resolves #80
Resolves #92
Resolves #208
Resolves #184
Resolves #165

Wooo! thanks a ton for this, works flawlessly. Im really curious why things seemed to implode over the last couple weeks for a ton of people? was it do to changes from the supabase team on their end?

The supabase libraries (mainly gotruejs) have evolved in a way that was not fiting our use in the module. A rewrite was needed !

authors: CptJJ larbish

repo: nuxt-modules/supabase


text:
Cannot create new project

C:\Users\Ala\Desktop\aa>npx create-nuxt-app dashboard
create-nuxt-app v2.15.0
✨  Generating Nuxt.js project in dashboard
? Project name dashboard
? Project description My kryptonian Nuxt.js project
? Author name
? Choose programming language JavaScript
? Choose the package manager Npm
? Choose UI framework Vuetify.js
? Choose custom server framework None (Recommended)
? Choose Nuxt.js modules Axios, Progressive Web App (PWA) Support, DotEnv
? Choose linting tools (Press  to select,  to toggle all,  to invert selection)
? Choose test framework None
? Choose rendering mode Universal (SSR)
? Choose development tools jsconfig.json (Recommended for VS Code)
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to
the actual version of core-js@3.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to
the actual version of core-js@3.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to
the actual version of core-js@3.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to
the actual version of core-js@3.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack     at VisualStudioFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to
the actual version of core-js@3.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack     at VisualStudioFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to
the actual version of core-js@3.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
gyp ERR! find VS
gyp ERR! find VS msvs_version not set from command line or npm config
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack     at VisualStudioFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:54:7
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\util.js:33:16
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:310:5)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at maybeClose (internal/child_process.js:1051:16)
gyp ERR! System Windows_NT 10.0.18363
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--release"
gyp ERR! cwd C:\Users\Ala\Desktop\aa\dashboard\node_modules\fibers
gyp ERR! node -v v14.2.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup your
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: sudo apt-get install g++ build-essential
RHEL users please run: yum install gcc-c++ and yum groupinstall 'Development Tools'
Alpine users please run: sudo apk add python make g++
'nodejs' n'est pas reconnu en tant que commande interne
ou externe, un programme ex�cutable ou un fichier de commandes.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\watchpack\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fibers@4.0.3 install: node build.js || nodejs build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fibers@4.0.3 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Ala\AppData\Roaming\npm-cache_logs\2020-05-08T02_57_25_403Z-debug.log

fibers@4.0.3 install C:\Users\Ala\Desktop\aa\dashboard\node_modules\fibers
node build.js || nodejs build.js

C:\Users\Ala\Desktop\aa\dashboard\node_modules\fibers>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\nod
e-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild --release )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js
" rebuild --release )
C:\Users\Ala\AppData\Roaming\npm-cache_npx\2584\node_modules\create-nuxt-app\node_modules\sao\lib\installPackages.js:108
throw new SAOError(Failed to install ${packageName} in ${cwd})
^
SAOError: Failed to install packages in C:\Users\Ala\Desktop\aa\dashboard
at ChildProcess. (C:\Users\Ala\AppData\Roaming\npm-cache_npx\2584\node_modules\create-nuxt-app\node_modules\sao\lib\installPackages.js:108:15)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.cp.emit (C:\Users\Ala\AppData\Roaming\npm-cache_npx\2584\node_modules\create-nuxt-app\node_modules\sao\node_modules\cross-spawn\lib\enoent.js:34:29)
at maybeClose (internal/child_process.js:1051:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) {
__sao: true
}

I had the same issue and after updating node, the issue was fix.

I had the same problem, and solved.
See this line
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: sudo apt-get install g++ build-essential
RHEL users please run: yum install gcc-c++ and yum groupinstall 'Development Tools'
Alpine users please run: sudo apk add python make g++

I used docker aipine image, so ran this.
apk update && apk add \
    python\
    make\
    g++

Then solved.

@petrovicz try to clear your npm cache https://dev.to/rishiabee/npm-err-unexpected-end-of-json-input-while-parsing-near-743

@ankoe Unfortunately it didn't solve the issue for me

I had the same issue again in another project.
I needed to downgrade to use the node TLS version.

LTS versions are working for me also.

I tried clearing my npm cache and yarn cache both are failing for on the same error.

It seems that this problem only occurs when choosing Vuetify UI-framework

Same here ... When choosing vuetify

LTS version is the only solution for now

It seems that this problem only occurs when choosing Vuetify UI-framework UPD: u can use npm init nuxt-app

On my side, experiencing this after choosing tailwind css.

authors: Lustach ahsanahmed321 alakameljebali alexon1234 ankoe daisuke-fukuda ellaidevs jcjp petrovicz

repo: nuxt/create-nuxt-app


text:
ERROR in common.83cd80e5c7fd8703ba74.js from UglifyJs

error

nuxt.config.js

package.json

why?

You should include the you dependency which use not supported es syntax yet in 'babel', pls have a look at: https://github.com/nuxt/nuxt.js/issues/1668#issuecomment-330510870


text:
Major issue with namespaced Vuex modules

Version
v1.4.2
Reproduction link
https://vuex.vuejs.org/guide/modules.html
Steps to reproduce
Setup a module mode index.js in the store folder with code
WORKS
Copy the exact same code in a second-file.js in the store folder
Change all the helpers I'm using to reference the new namespace e.g. mapState(['stateName']) to mapState(['second-file/stateName'])
DOESN'T WORK
What is expected ?
I'm expecting Nuxt to normally access the module
What is actually happening?
Nuxt does not recognize any of the properties from the store module
Additional comments?
I want to highlight that this happens with a clean Nuxt install through Vue CLI and with very simple code in order to exclude mistakes of different nature. The two store files are exactly identical apart from one becoming namespaced due to Nuxt default behavior. The same issue persist if I try to register the modules in the classic Vuex mode, since also in this case Nuxt creates namespaced modules. Is there a way to disable the automatic namespacing and instead merge all the modules properties into the main store?

This bug report is available on Nuxt community (#c7619)

Have you tried nuxt-edge? I am using namespaced modules without any issues with nuxt-edge.

How do I migrate to nuxt-edge?

For me it was as simple as:
Uninstall nuxt
Install nuxt-edge

same problem with nuxt-edge, are you using the helpers?

I just tried as last resort to use the vuex namespace helper and now it works:
import { createNamespacedHelpers } from 'vuex'
const { mapState, mapActions } = createNamespacedHelpers('moduleName')
and then just the 'stateName' in the code, while without the namespaced helpers and just 'moduleName/stateName' it doesn't. It's a very strange issue

I kind of find a solution, which still doesn't justify to me why the other method doesn't work.
...mapState(['navigation/pages']) NOT WORKING
...mapState('navigation', ['pages']) WORKING
maybe it's just me not getting the obvious, anyways I'm very happy now that I managed to get it working, I was getting crazy

@ultramarinelights
I’m glad to read that you found a solution.
I do use helpers and they were working when I last checked. Perhaps I was using the second syntax, where you supply the namespace as the first argument. I’ll check when I’m back from vacation.

Closed in favor of https://github.com/nuxt/docs/issues/850

authors: UltramarineLights manniL pbastowski


text:
npm version of @nuxt/babel-preset-app is not up to date

Version
v2.12.2
Reproduction link
https://www.npmjs.com/package/@nuxt/babel-preset-app
Steps to reproduce
check out npm version of @nuxt/babel-preset-app
first the version there is higher than the one in master (2.12.2 vs. 2.12.1)
second the "bugfixes" option is not present in the docs (and also not in the source).
What is expected ?
correct version / source of babel-preset-app
What is actually happening?
old version is packed and published

This bug report is available on Nuxt community (#c10566)

cc @clarkdo

@pi0 It looks like there is an unexpected 2.12.2 packages, do you have any idea why they are published  ?

@simllll The releases seem right, the release branch is 2.x not dev, we'll merge 2.x back to dev after release.
As bugfixs is a new feature, so it will be released 2.13.0.

Ah alright, wasn't aware of that. Thanks, looking forward to 2.13.0 then ;-)

Hi, @simllll release are correct. 2.12.1 and 2.12.2 released as hotfix to 2.x branch. For nuxt (stable) code reference, you should refer to 2.x branch not development.
New bugfixes option (#7144) added after 2.12.0 and will be available in nuxt@2.13.0 (also currently nuxt-edge)

authors: clarkdo manniL pi0 simllll


text:
content security policy header will lose When status code is 304

Versions

nuxt: v2.14.7
node: v12.16.3

Reproduction

Additional Details

Steps to reproduce
What is Expected?
What is actually happening?
I have a website built with nuxt.js, when I first visit, it has the correct csp header which I set in nuxt.config.js. When I visit this website again, it will lose csp header. And I found that when status code is 304, csp header will lose.

@pi0 @danielroe Would you please have a look on this issue ?  Do you think it is a bug when http status code is 304, the CSP header will lose, if not, is there a configuration can make CSP header work as expected, if it is bug, do you have a plan to publish a patch because this can cause security problem because of the miss of CSP header. Thanks

This should be fixed in v2.14.8. Please reopen if not.

This should be fixed in v2.14.8. Please reopen if not.

Thanks. I have confirmed it was solved from v2.14.8


text:
Option to disable build progress bars in CLI even when TTY is enabled

Is your feature request related to a problem? Please describe.
I use Docker and wanted to enable TTY so I could see colours in Docker Compose logs. However, enabling TTY also renders the webpack progress bars during builds. The bars work but have some rendering issues, most likely due to Docker Compose prefixing each log line with with the container name.
For example, the Client and Server bars render twice for each update.

Describe the solution you'd like
A top level option, or documentation, on how to disable the progress bars in the CLI, even in a development environment would be very useful. I'd be able to keep TTY enabled without the rendering issues.
Ideally this would not disable the progress bars displayed in the browser during build.
Basically, I'd like the result I get with TTY disabled, but with colours.

and during an update...

Describe alternatives you've considered
For now, I run with TTY disabled in Docker Compose, however, I lose colours.
I tried configuring the plugin in the nuxt.config.js build extend() function but couldn't seem to get any options to override.
I tried removing the progress bar plugin from the config.plugins list in extend(config) but that broke a bunch of things Nuxt or webpack was relying on.
I could also cut a bug ticket on the https://github.com/nuxt-contrib/webpackbar repo to see if the rendering can be fixed inside a docker TTY with the line prefixing.
Additional context

Naturally, as soon as I posted this, I decided to try one last configuration that targeted the progress bar reporters.
// nuxt.config.js
export default {
  // ...

  build: {
    extend: (config) => {
      const bar = config.plugins.find((p) => p.constructor.name === 'WebpackBarPlugin')
      bar.reporters = bar.reporters.filter((r) => r.constructor.name !== 'FancyReporter')
    }
  }
}

This worked!
By removing the FancyReporter from the WebpackBarPlugin's array of reporters it disabled the progress bars in the CLI but kept the progress bars in the browser.
It would appear that changing the WebpackBarPlugin.options.fancy = false doesn't work because the plugin already populated the reporters array based on that config (and environment) during setup.
I'll leave this here and keep the issue open since it may still be a good idea to streamline this process.

Some further investigation found that the previous example wasn't fully doing what I needed. It was removing the anonymous reporter that renders the progress bars in the browser. So instead of simply removing the FancyReporter, I wound up having to "clone" the WebpackBarPlugin, include the basic reporter and exclude the FancyReporter.
So here's the masterpiece
import isDocker from 'is-docker'

export default {
  build: {
    extend(config) {
      // hide the build progress bars in the CLI (but not the browser)
      // since they do not render correctly in docker-compose logs
      if (isDocker()) {
        const i = config.plugins.findIndex(
          (p) => p.constructor.name === 'WebpackBarPlugin'
        )
        const plugin = config.plugins[i]

        // replace existing bar plugins with clones that exclude the 'fancy'
        // reporter and include a 'basic' reporter
        config.plugins.splice(
          i,
          1,
          new WebpackBarPlugin({
            name: plugin.options.name,
            reporters: [
              'basic', // include reporter as string because we cannot import
              ...plugin.reporters.filter(
                (p) => p.constructor.name !== 'FancyReporter'
              ),
            ],
          })
        )
      }
    }
  }
}

For future me, it looks like here is where you'd have to start to implement this as a nuxt option
https://github.com/nuxt/nuxt.js/blob/ba44b0f9ca8955ddb884744f34192c831b2d1d16/packages/webpack/src/config/base.js#L445

Hi @Soviut. Have you tried MINIMAL=1 environment variable?

@pi0 I didn't know that was available but it seems to do the same thing. Is that environment variable controlling std-env to make env.minimalCLI?

Is that environment variable controlling std-env to make env.minimalCLI?
Yes :)

Thanks. I cut a ticket on the std-env repo to update the README with the environment variables. I'll see if I can contribute that documentation soon after.
https://github.com/nuxt-contrib/std-env/issues/9


text:
3.10.x: nuxt build creates vue files in .nuxt/dist/server/_nuxt folder

Environment
- Operating System: Darwin
- Node Version:     v21.2.0
- Nuxt Version:     3.10.0
- CLI Version:      3.10.0
- Nitro Version:    2.8.1
- Package Manager:  bun@1.0.25
- Builder:          -
- User Config:      devtools, css, modules, runtimeConfig, image, build, i18n, ignore, nitro, routeRules, security, vite
- Runtime Modules:  @nuxtjs/i18n@8.1.0, @nuxt/image@1.3.0, nuxt-icon@0.6.8, nuxt-security@1.1.1
- Build Modules:    -

Reproduction

Describe the bug
With 3.10.0 and 3.10.1 I get an error at the end of nuxt build: ERROR  RollupError: At least one <template> or <script> is required in a single file component, with 3.9.3 everything is fine.
Unfortunately I cant reproduce this in the sandbox but I already tried to debug this for hours. I nailed it down to one of my ~10 components: If it contains a <style> tag with ANY content (even just a comment). Weirdly when I delete the content of the <script> tag I can have styles:
Throws the error:
<script setup lang="ts">
// hello
</script>

<template>
  hello
</template>

<style lang="scss">
// hello
</style>

Doesnt throw an error:
<script setup lang="ts">
// hello
</script>

<template>
  hello
</template>

<style lang="scss"></style>

Doesnt throw an error:
<script setup lang="ts"></script>

<template>
  hello
</template>

<style lang="scss">
// hello
</style>

It also only happens with this one component named overlay.vue. I feel like I am getting crazy or something but this seems to make absolutely no sense.
Full error:
 ERROR  RollupError: At least one <template> or <script> is required in a single file component.         nitro 9:00:59 PM

undefined

 ERROR  At least one <template> or <script> is required in a single file component.                            9:00:59 PM

  at error (node_modules/rollup/dist/es/shared/parseAst.js:337:30)
  at Object.error (node_modules/rollup/dist/es/shared/node-entry.js:18507:20)
  at Object.error (node_modules/rollup/dist/es/shared/node-entry.js:17616:42)
  at node_modules/rollup-plugin-vue/dist/sfc.js:22:49
  at Array.forEach (<anonymous>)
  at Object.transformSFCEntry (node_modules/rollup-plugin-vue/dist/sfc.js:22:16)
  at Object.transform (node_modules/rollup-plugin-vue/dist/index.js:99:38)
  at node_modules/rollup/dist/es/shared/node-entry.js:18692:40

 ERROR  At least one <template> or <script> is required in a single file component.                            9:00:59 PM

error Command failed with exit code 1.

Additional context
No response
Logs
No response

This is unlikely to be an issue with Nuxt - rollup-plugin-vue is not used by Nuxt or Nitro and is what is throwing your error.

I am not 100% sure about that. Yes this plugin throws the error BUT I disabled the plugin and realized there is exactly one .vue file in the folder .nuxt/dist/server/_nuxt which is exactly the file I debugged to be the one creates the error. I guess there shouldnt be any vue file in this folder which one mean that there actually is a bug within Nuxt.

Interesting. Have you customised assetFileNames by any chance?

I did not

I probably can't look into this without a reproduction or more info.

I can try to dig more into this and make this reproducable.

@danielroe So it took me a few hours of removing more and more stuff from my app until I ended in an empty app and I realized:
This happens on a blank empty app created with nuxi init and just a single index page and a single component in it! If the component has a script with lang=ts and a style tag (both with ANY content) a vue file is in the .nuxt/dist/server folder!
Since StackBlitz doesnt seem to work, here is the repo: https://github.com/MickL/nuxt-bug

When you say that StackBlitz doesn't work, what do you mean?

I can't reproduce with that repo.
Here's a StackBlitz created from it - seemingly working fine: https://stackblitz.com/edit/github-iqamf7.
Could you share any more info about your setup?

I used bun install if that changed anything. My specs are at the very top. I think #25690 could be the same issue

When you say that StackBlitz doesn't work, what do you mean?

I meant that the links on the Nuxt website (the two I posted above) both dont start and produce errors.
So I double checked on another machine. I downloaded my repo, run npm install and then npm run buld. If I check the folder `` I see (as I described) there is a vue file which is probably supposed to be a js file:

You're quite right; it is reproducible there - I was checking .output, not .nuxt.

I am not sure if this is causing me problems now - I updated my packages to latest (all of them), and somehow I get an error:
cannot find module './stringify' (module in question is qs, which is only used by Strapi module as far as I can tell)
This only happens in dev mode, build is running fine. When I don't include it in the configuration everything works.
If I keep use the Nuxt ^3.10.1 version I have no problems. Does any of this ring a bell?

authors: KresimirCosic MickL danielroe

repo: nuxt/nuxt


text:
Horizontal landing hero  items end not works

Environment

Operating System: Darwin
Node Version:     v20.9.0
Nuxt Version:     3.10.2
CLI Version:      3.10.1
Nitro Version:    2.8.1
Package Manager:  npm@10.1.0
Builder:          -
User Config:      css, extends, modules, stripe, eslint, image, runtimeConfig, imports, ui, devtools, experimental
Runtime Modules:  @nuxt/ui@2.13.0, @nuxt/image@1.3.0, @nuxtjs/eslint-module@4.1.0, @vueuse/motion/nuxt@2.0.0, nuxt-clarity-analytics@0.0.6, dayjs-nuxt@2.1.9, @unlok-co/nuxt-stripe@2.0.0, @nuxtjs/i18n@8.1.1
Build Modules:    -

Version
"2.13.0",
Reproduction
In description
Description
Hello, i cannot override lg:items-center in uLandingHero when orientation is horizontal
<ULandingHero
        :ui="{
          container: 'lg:items-end sm:gap-0',
        }"
        orientation="horizontal"/>

Additional context
No response
Logs
No response

I've already transferred your issue to the @nuxt/ui-pro repository! This will be fixed in the next release.

authors: benjamincanac carlosvaldesweb

repo: nuxt/ui


text:
u-accordian - name and provide a type for items

import type { AccordianItems } from '@nuxtlabs/ui'

const items:AccordianItems = [
...

Is this in the edge? how do i import it?
import type { AccordianItem } from '@nuxthq/ui'

?

repo: nuxtlabs/ui


text:
Fix usage of the C++ impl of write_df_to_file

Description

Fixes a bug when C++ mode is enabled, the file would be written twice.

By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge

authors: dagardner-nv mdemoret-nv

repo: nv-morpheus/Morpheus


text:
kadf01-sp2

Link to application: https://eso.vse.cz/~kadf01/sp2/

@kadlecfilip mate duplikovae soubory, nevim ktere z nich hodnotit


text:
Enable the use of custom keybindings

The Fuck 3.28 using Python 3.6.10 and ZSH 5.8
system: 5.5.0-gentoo #1 SMP Wed Jan 29 23:29:22 MST 2020 x86_64 AMD Ryzen 7 2700 Eight-Core Processor AuthenticAMD GNU/Linux
As a vim user, and someone who rarely uses the arrow keys, it would be great to be able to assign the up/down functionality to j/k.

I just ran fuck, and it already has support for this feature

Ugh. I donno why i missed that. Probably because I'm in a neovim terminal and there was a delay of a second due to my keybindings
Thank you!

authors: bearcatsandor cjoshmartin

repo: nvbn/thefuck


text:
#N/A Remove fucked up cmd from history regardless of status

Most fucked up commands are erroneous, but that's not always the case.

Thanks!

authors: nvbn scorphus


text:
🛑 Kubeflow ML Platform is down

In e5849a5, Kubeflow ML Platform (https://kubeflow.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kubeflow ML Platform is back up in 2dbed50.

repo: nvgsg/lab-upptime


text:
🛑 NVIDIA AI Enterprise Hub is down

In 9f53d5e, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in 0b40186.


text:
🛑 NVIDIA AI Enterprise Hub is down

In 05b3aca, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in 8d62e44.


text:
🛑 NVIDIA AI Enterprise Hub is down

In 51c7cdf, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in a422781.


text:
@media doesn't seem to compile with css / scss modules + more

The Problem
I'm using jest-preview to visualize screens using css modules. Some of the styling is dependent on media queries. None of the @media statements seem to get compiled into the embedded style tags. Other classes from the module make it in fine.
I also cannot import SCSS files into the setup file. If I compile them using gulp or webpack and then import the resulting .css file, it appears to work fine.
Additional issue but not related, I can't get auto preview to work at all.
What I've tried
So far I've tried compiling the SCSS myself and removing hashes from the class names. I've faced trouble using the advanced configuration to try and remove the hashes from the jest-preview transform source. This didn't seem to work either.
I've also tried using a custom transform with some additional postCss utilities but haven't had any success. If I render components with no media queries, this tool is absolutely wonderful.
What is the framework/ technology you want to integrate Jest Preview to?
"react": "^16.13.1"
"jest": "^26.6.3"
"postcss": "^8.4.6"
"sass": "^1.53.0"
"sass-loader": "^10.2.1"

Thank you
Thank you for your time and continued effort on this tool! If I can contribute, I'd love to if someone can point me in the right direction.

None of the @media statements seem to get compiled into the embedded style tags

Can you provide minimum reproduction. I added a commit to include @media query and it works fine. Please refer to this commit:
https://github.com/nvh95/jest-preview/commit/0e8a8273146a993b300500e30b2c5fc7e157bbd3#diff-650149a55a5b9fea04fefedba299bd2bf341e1a1c8b4d6e63e483e95669efbfcR4-R9

I also cannot import SCSS files into the setup file.

Please help to prepare a reproduction. In our demo, we can import CSS modules file (https://github.com/nvh95/jest-preview/blob/41019e629c89c48580f29841d6380d89d8cdb41d/demo/setupTests.js#L4). Thanks.

It looks like you are correct! I do think I might have an idea of what's happening. I think the class name property on the component changes based on the media or screen size and it doesnt seem to be updating properly. Regardless of the window or screen size I stub in jest, it falls back to either default or the mobile values. Maybe it's something with the way I'm handling my renders?


text:
fix: remove hard-coded "weekly" in folder creation prompt

Proposed change

Replace hard-coded "Create weekly dir" in new folder creation prompt with more generic "Notes", resulting in the following:

Previous: "Create weekly dir folder /home//projects/second-brain/foobar/ does not exist! Shall I create it?"
New: "Notes folder /home/cameron/projects/second-brain/foobar/ does not exist! Shall I create it?"

Type of change

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (thank you!)
[x] Code quality improvements to existing code or addition of tests
[ ] Documentation update

Additional information

This PR fixes or closes issue: fixes #297

Checklist

[x] I am running the latest version of the plugin.
[x] The code change is tested and works locally.
[x] There is no commented out code in this PR.
[x] The code has been formatted using Stylua (a .stylua.toml file is provided)
[x] The code has been checked with luacheck (a .luacheckrc file is provided)
[ ] The README.md has been updated according to this change.
[ ] The doc/telekasten.txt helpfile has been updated according to this change.

Thank you for your contribution!


text:
pull_request diff view broken

in pull_request, when I try to switch to the "diff" mode, the preview shows only:
Usage:  gh pr diff [<number> | <url> | <branch>] [flags]

Flags:
  --color string   Use color in diff output: {always|never|auto} (default "auto")

[Process exited 1]

fix: https://github.com/nvim-telescope/telescope-github.nvim/pull/16


text:
overbrights

I have a scene which rendered overbright.
Is it posible to autoexposure or use all lights power for automatically balance of lights in scene.
In sky mode all looks ok

But when I upload HDRI and also when I set intensity to 0 - I have overbright

Looks like an issue

one more case of this issue - sun disk scale = 0 or sun disk intensity = 0 make overbrights

one more scene with emissive textures
with HDRI on

HDRI off

Have you tried the tonemappers ?

tone mappers doesnt helps.
emissive area lights not calculated in MIS well.
in code processed hdris and punctual lights, not area lights

The scene has indeed very strong lights, which I believe doesn't follow the rule of the intensity parameter, which is lumens per steradian (lm/sr).
There are a few things which can be done:

Increase "Max Luminance", which is controlling the Firefly Filter and is cutting out incoming energy.
Reduce the Tonemapper exposure to compensate the over bright lights
Set the sun elevation to -90 deg, to remove any contribution from the Physical Sun & Sky model. Changing the Disk Scale is not physically correct, but a user control was added for "artistical effect", but only the 1.0 value is correct.

Same is true for the SciFi scene

big versions of images doesnt open (started from private-user-images.githubusercontent.com

thank you for explaination. is this parameters can be automatic processed?
for example, "auto exposure" which can measure max luminance and fit parameters?

An auto-exposure can be done, but to properly do this, we need the inverse of the tonemapper in use. We do not plan this feature in the short term.

authors: mklefrancois tigrazone


text:
Dependency Graph not being correctly generated

Just started using nx-dotnet and having issues with dep-graph
To Reproduce
Just created a new workspace with two dotnet libs (lib1 ref lib2)
generate the workspace: npx create-nx-workspace@latest
choose template: apps
install nxdotnet: npm i --save-dev @nx-dotnet/core
create lib1 and lib2
add reference from lib1 to lib2
build everything: npx nx run-many --target=build --all
generate dep-graph: nx dep-graph
result:

also the lib1.csproj inside .cashe\nx\nxdeps.json doesn't contain any "deps" node
Expected behavior
nxdeps.json should contain the deps for each csproj

Can you run nx report and also check that '@nx-dotnet/core' is listed as a plugin in nx.json?

Yes i do have  "plugins": ["@nx-dotnet/core"] under nx.json
results for nx report
Node : 16.3.0
OS   : win32 x64
npm  : 7.18.1
nx : 13.8.3
@nrwl/angular : undefined
@nrwl/cli : 13.8.3
@nrwl/cypress : undefined
@nrwl/detox : undefined
@nrwl/devkit : 13.8.3
@nrwl/eslint-plugin-nx : undefined
@nrwl/express : undefined
@nrwl/jest : 13.8.3
@nrwl/js : undefined
@nrwl/linter : 13.8.3
@nrwl/nest : undefined
@nrwl/next : undefined
@nrwl/node : undefined
@nrwl/nx-cloud : 13.1.5
@nrwl/react : undefined
@nrwl/react-native : undefined
@nrwl/schematics : undefined
@nrwl/storybook : undefined
@nrwl/tao : 13.8.3
@nrwl/web : undefined
@nrwl/workspace : 13.8.3
typescript : 4.5.5
rxjs : 6.5.5
Community plugins:
@nx-dotnet/core: 1.9.2

authors: AgentEnder YasserKharab

repo: nx-dotnet/nx-dotnet


text:
🛑 Harmony Bot Website is down

In 095fc0e, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 06e5165.

repo: nxvvvv/uptime


text:
shards install not grabbing md5

in lib/pg/src/pq/connection.cr:2: while requiring "crypto/md5": can't find file 'crypto/md5' relative to '/root/cpomf/lib/pg/src/pq'
require "crypto/md5"
the crypto/md5 is not under the lib folder compared to the rest of the things shards installed
running a new version of Crystal compared to Crystal 0.20.4

https://github.com/crystal-lang/crystal/tree/master/src/crypto
md5 is missing from the newest one so might be why

we're currently running Crystal 0.20.4 without any issues; but we'll likely try to update to a newer Crystal version in the near future.
in the meantime i'd recommend just running Crystal 0.20.4, or submitting a pull request.

Switched to Crystal 0.20.4 and had to get shards and it compiles now

authors: formatme neko

repo: nya/cpomf


text:
Let users define the name of the expiredAt column

We use snake_case in our project, would be cool to just be able to pass this as an option

Not to revive an old comment, but if you/someone stumbles upon this, you can:
  @Index()
  @Column({ name: 'expired_at', type: 'bigint' })
  expiredAt: number;

which is a built-in functionality in TypeORM :)

authors: Agreon ali-elamri

repo: nykula/connect-typeorm


text:
Create vue demo for read-email use case

Description
This PR adds Vue support for read emails use cases. Functionally it works but the styling is a bit off.
License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@mrashed-dev is there some prettier plugin we can enable for vue?

authors: AaronDDM mrashed-dev

repo: nylas/use-cases


text:
[Support] No assets output at production

My craft won't output asset links with  {{ craft.vite.script("/src/app.js") }} at production.
Only the code below is output.
<script type="module">!function(){const e=document.createElement("link").relList;if(!(e&&e.supports&&e.supports("modulepreload"))){for(const e of document.querySelectorAll('link[rel="modulepreload"]'))r(e);new MutationObserver((e=>{for(const o of e)if("childList"===o.type)for(const e of o.addedNodes)if("LINK"===e.tagName&&"modulepreload"===e.rel)r(e);else if(e.querySelectorAll)for(const o of e.querySelectorAll("link[rel=modulepreload]"))r(o)})).observe(document,{childList:!0,subtree:!0})}function r(e){if(e.ep)return;e.ep=!0;const r=function(e){const r={};return e.integrity&&(r.integrity=e.integrity),e.referrerpolicy&&(r.referrerPolicy=e.referrerpolicy),"use-credentials"===e.crossorigin?r.credentials="include":"anonymous"===e.crossorigin?r.credentials="omit":r.credentials="same-origin",r}(e);fetch(e.href,r)}}();</script>

I couldn't figure out why but everything is fine at development mode.
craft 3.7.23
craft-vite 1.0.19
No error at debug bar at frontend.
Please help.

It seems be caused by some composer modules.
composer update will produce this issue.

I found that craft-plugin-vite 1.0.17 required by craft-vite 1.0.18 will cause the issue.

I created new issue for craft-plugin-vite and will close this.
https://github.com/nystudio107/craft-plugin-vite/issues/6


text:
Temperature/Humidity stopped working after update to 0.3.6

Hi,
since release 0.3.6 when support for BME280 was added, my sensor AM2320 returns "not installed" most of the time.
I tried to figure out what is wrong and discovered that it works after I reset the ESP (for example by klicking "save config" in the webinterface). It does not work after a power cycle.
Maybe a delay is needed after power up before initialization / detection?  I guess the DHT22 does not need that delay which is why no one else seems to be having that issue :)

Hi,
I'll take a look, however I don't have an AM2320 here.

Hi,
I am testing right now. The sensor supports i2C and single bus mode. For single bus mode, which is the same as with DHT22,  SCL (connected to GND) must be low for 500 ms. I guess reading the sensor earlier puts it into I2C mode. The datasheet also says that only a power cycle can change the mode. Page 5:
https://cdn-shop.adafruit.com/product-files/3721/AM2320.pdf
I tested a delay right before dht.setup. 400ms was too short, 500 worked most of the time, so I am using 600 ms now.

Hi, I think we can work with a delay here, the 600 ms should not be a problem.

Cool, thanks! 600ms works here without any problems so far.

fixed in  v0.3.14

Hi, after flashing the latest version, my sensor stoppend working. I think this happens because it checks for other sensors on the same pin before the 600 ms delay.
I have not verified this because I am missing getSmoothedLux. How do I update the library? I expected vscode / platform.io to do this automatically.
Thanks!

Got it, I had to do a "clean all" to get the latest version of the LDR lib. I moved the delay up to where it says "// Init Temp Sensors" and it's working again.

Seems like a longer delay of 800ms is needed to make it work reliably.
The problem that the sensor could not be detected happend only in the morning after powering up my Pixelit. Power cycles during the day, leaving it off for some minutes, resulted in a working sensor. Perhaps it depends on the room temperature.


text:
Check for updates program

Grabs a file, checks it's internal build number versus what the file provided is.
It'll have a method to disable itself on indev builds, and be put on GitHub (it's a text file...after all.)
Targeted to beta 3, but it may get pushed to beta 4.

Now implemented into 2.0.
I'll implement the update program into PyTerm 1.15.1 LTS, and stable 1.14.1 soon.