text:
Test Issue created at Fri, 23 Apr 2021 11:06:54 GMT

Test issue body  Fri, 23 Apr 2021 11:06:54 GMT

Comment on issue at Fri, 23 Apr 2021 11:06:57 GMT

repo: nodemationqa/nodeQA


text:
CSRF/CORS

Look into this and figure what needs to be done.

Fixed

https://github.com/nodes-vapor/readme/pull/65
https://github.com/nodes-vapor/template/pull/8

source: gharchive/issue

authors: BrettRToomey steffendsommer

repo: nodes-vapor/admin-panel-provider

license: mit

license_type: permissive

license_source: bigquery


text:
feat: change the output Image Stream name and tag

fixes #337
@lance when you get a chance,  you want to test this out.
I still need to added tests and update the readme and and stuff.  but the functionality should all be there
there are now  --outputImageStream and --outputImageStreamTag  flags to specify the different output stream names and tag

Will do perhaps tomorrow or early next week. Feel free to bug me about it
again if it slips through the cracks.

Pull Request Test Coverage Report for Build 876

9 of 9 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 96.614%

Totals

Change from base Build 219:
0.01%

Covered Lines:
629

Relevant Lines:
654

💛  - Coveralls

@lance just a friendly ping :)

source: gharchive/pull-request

authors: coveralls lance lholmquist

repo: nodeshift/nodeshift

license_source: github-api


text:
Gitlab Migration - Corrections

As this project was originally hosted on Gitlab and migrated to Github some problems have occurred:

[!NOTE]
This issue can be closed when ALL migrated items are closed

Some issue numbers do not match what was given in Gitlab. #2 through #214

to rectify this on working on any issue/pr the references within the description are to be incremented by +1. i.e. ref #1 becomes #2

Issues opened by a user in gitlab may not be reflected within github issues. This can be identified within the issue description's first line. i.e. In GitLab by @<username> on Aug 5, 2024, 06:48 the user in <username> was the user who opened the issue.

to rectify this use the following comment so they become subscribed to the issue again:
@username, this issue was migrated from gitlab to github. During this migration you were not added as the user whom opened this issue. This message will ensure that you receive further updates on this issue as it progresses.

Further information can be found within #215

Gitlab migrated issues #2 through #169 match Gitlab issues #1 through #168
Gitlab migrated Merge Requests are  #181 through #214 for PRs.
Tasks

[x] Fix milestone names

[x] label all migrated items with label Migrated from gitlab

[x] Migrate Difficulty labels to the github Equivelents

[x] Add this issues number to the label description

[ ] Update readme to denote Github hosted, not gitlab

[x] migrate Module labels to project fields

remove Gitlab CI

[ ] no gitlab releases
[ ] no gitlab sync to github
[ ] no gitlab publish

[x] Update this issue with the issue numbers that went skew-if

[ ] Do Last (After repo changes) Push changes to Gitlab

Post git changes to be pushed to gitlab
when all CI changes done, push to gitlab to prevent gitlab mirror from overwriting Github changes.
Issues (W/Link to Gitlab issue)

Issues Migrated from Gitlab

Migrated From Gitlab (gitlab-1): #2
Migrated From Gitlab (gitlab-2): #3
Migrated From Gitlab (gitlab-3): #4
Migrated From Gitlab (gitlab-4): #5
Migrated From Gitlab (gitlab-5): #6
Migrated From Gitlab (gitlab-6): #7
Migrated From Gitlab (gitlab-7): #8
Migrated From Gitlab (gitlab-8): #9
Migrated From Gitlab (gitlab-9): #10
Migrated From Gitlab (gitlab-10): #11
Migrated From Gitlab (gitlab-11): #12
Migrated From Gitlab (gitlab-12): #13
Migrated From Gitlab (gitlab-13): #14
Migrated From Gitlab (gitlab-14): #15
Migrated From Gitlab (gitlab-15): #16
Migrated From Gitlab (gitlab-16): #17
Migrated From Gitlab (gitlab-17): #18
Migrated From Gitlab (gitlab-18): #19
Migrated From Gitlab (gitlab-19): #20
Migrated From Gitlab (gitlab-20): #21
Migrated From Gitlab (gitlab-21): #22
Migrated From Gitlab (gitlab-22): #23
Migrated From Gitlab (gitlab-23): #24
Migrated From Gitlab (gitlab-24): #25
Migrated From Gitlab (gitlab-25): #26
Migrated From Gitlab (gitlab-26): #27
Migrated From Gitlab (gitlab-27): #28
Migrated From Gitlab (gitlab-28): #29
Migrated From Gitlab (gitlab-29): #30
Migrated From Gitlab (gitlab-30): #31
Migrated From Gitlab (gitlab-31): #32
Migrated From Gitlab (gitlab-32): #33
Migrated From Gitlab (gitlab-33): #34
Migrated From Gitlab (gitlab-34): #35
Migrated From Gitlab (gitlab-35): #36
Migrated From Gitlab (gitlab-36): #37
Migrated From Gitlab (gitlab-37): #38
Migrated From Gitlab (gitlab-38): #39
Migrated From Gitlab (gitlab-39): #40
Migrated From Gitlab (gitlab-40): #41
Migrated From Gitlab (gitlab-41): #42
Migrated From Gitlab (gitlab-42): #43
Migrated From Gitlab (gitlab-43): #44
Migrated From Gitlab (gitlab-44): #45
Migrated From Gitlab (gitlab-45): #46
Migrated From Gitlab (gitlab-46): #47
Migrated From Gitlab (gitlab-47): #48
Migrated From Gitlab (gitlab-48): #49
Migrated From Gitlab (gitlab-49): #50
Migrated From Gitlab (gitlab-50): #51
Migrated From Gitlab (gitlab-51): #52
Migrated From Gitlab (gitlab-52): #53
Migrated From Gitlab (gitlab-53): #54
Migrated From Gitlab (gitlab-54): #55
Migrated From Gitlab (gitlab-55): #56
Migrated From Gitlab (gitlab-56): #57
Migrated From Gitlab (gitlab-57): #58
Migrated From Gitlab (gitlab-58): #59
Migrated From Gitlab (gitlab-59): #60
Migrated From Gitlab (gitlab-60): #61
Migrated From Gitlab (gitlab-61): #62
Migrated From Gitlab (gitlab-62): #63
Migrated From Gitlab (gitlab-63): #64
Migrated From Gitlab (gitlab-64): #65
Migrated From Gitlab (gitlab-65): #66
Migrated From Gitlab (gitlab-66): #67
Migrated From Gitlab (gitlab-67): #68
Migrated From Gitlab (gitlab-68): #69
Migrated From Gitlab (gitlab-69): #70
Migrated From Gitlab (gitlab-70): #71
Migrated From Gitlab (gitlab-71): #72
Migrated From Gitlab (gitlab-72): #73
Migrated From Gitlab (gitlab-73): #74
Migrated From Gitlab (gitlab-74): #75
Migrated From Gitlab (gitlab-75): #76
Migrated From Gitlab (gitlab-76): #77
Migrated From Gitlab (gitlab-77): #78
Migrated From Gitlab (gitlab-78): #79
Migrated From Gitlab (gitlab-79): #80
Migrated From Gitlab (gitlab-80): #81
Migrated From Gitlab (gitlab-81): #82
Migrated From Gitlab (gitlab-82): #83
Migrated From Gitlab (gitlab-83): #84
Migrated From Gitlab (gitlab-84): #85
Migrated From Gitlab (gitlab-85): #86
Migrated From Gitlab (gitlab-86): #87
Migrated From Gitlab (gitlab-87): #88
Migrated From Gitlab (gitlab-88): #89
Migrated From Gitlab (gitlab-89): #90
Migrated From Gitlab (gitlab-90): #91
Migrated From Gitlab (gitlab-91): #92
Migrated From Gitlab (gitlab-92): #93
Migrated From Gitlab (gitlab-93): #94
Migrated From Gitlab (gitlab-94): #95
Migrated From Gitlab (gitlab-95): #96
Migrated From Gitlab (gitlab-96): #97
Migrated From Gitlab (gitlab-97): #98
Migrated From Gitlab (gitlab-98): #99
Migrated From Gitlab (gitlab-99): #100
Migrated From Gitlab (gitlab-100): #101
Migrated From Gitlab (gitlab-101): #102
Migrated From Gitlab (gitlab-102): #103
Migrated From Gitlab (gitlab-103): #104
Migrated From Gitlab (gitlab-104): #105
Migrated From Gitlab (gitlab-105): #106
Migrated From Gitlab (gitlab-106): #107
Migrated From Gitlab (gitlab-107): #108
Migrated From Gitlab (gitlab-108): #109
Migrated From Gitlab (gitlab-109): #110
Migrated From Gitlab (gitlab-110): #111
Migrated From Gitlab (gitlab-111): #112
Migrated From Gitlab (gitlab-112): #113
Migrated From Gitlab (gitlab-113): #114
Migrated From Gitlab (gitlab-114): #115
Migrated From Gitlab (gitlab-115): #116
Migrated From Gitlab (gitlab-116): #117
Migrated From Gitlab (gitlab-117): #118
Migrated From Gitlab (gitlab-118): #119
Migrated From Gitlab (gitlab-119): #120
Migrated From Gitlab (gitlab-120): #121
Migrated From Gitlab (gitlab-121): #122
Migrated From Gitlab (gitlab-122): #123
Migrated From Gitlab (gitlab-123): #124
Migrated From Gitlab (gitlab-124): #125
Migrated From Gitlab (gitlab-125): #126
Migrated From Gitlab (gitlab-126): #127
Migrated From Gitlab (gitlab-127): #128
Migrated From Gitlab (gitlab-128): #129
Migrated From Gitlab (gitlab-129): #130
Migrated From Gitlab (gitlab-130): #131
Migrated From Gitlab (gitlab-131): #132
Migrated From Gitlab (gitlab-132): #133
Migrated From Gitlab (gitlab-133): #134
Migrated From Gitlab (gitlab-134): #135
Migrated From Gitlab (gitlab-135): #136
Migrated From Gitlab (gitlab-136): #137
Migrated From Gitlab (gitlab-137): #138
Migrated From Gitlab (gitlab-138): #139
Migrated From Gitlab (gitlab-139): #140
Migrated From Gitlab (gitlab-140): #141
Migrated From Gitlab (gitlab-141): #142
Migrated From Gitlab (gitlab-142): #143
Migrated From Gitlab (gitlab-143): #144
Migrated From Gitlab (gitlab-144): #145
Migrated From Gitlab (gitlab-145): #146
Migrated From Gitlab (gitlab-146): #147
Migrated From Gitlab (gitlab-147): #148
Migrated From Gitlab (gitlab-148): #149
Migrated From Gitlab (gitlab-149): #150
Migrated From Gitlab (gitlab-150): #151
Migrated From Gitlab (gitlab-151): #152
Migrated From Gitlab (gitlab-152): #153
Migrated From Gitlab (gitlab-153): #154
Migrated From Gitlab (gitlab-154): #155
Migrated From Gitlab (gitlab-155): #156
Migrated From Gitlab (gitlab-156): #157
Migrated From Gitlab (gitlab-157): #158
Migrated From Gitlab (gitlab-158): #159
Migrated From Gitlab (gitlab-159): #160
Migrated From Gitlab (gitlab-160): #161
Migrated From Gitlab (gitlab-161): #162
Migrated From Gitlab (gitlab-162): #163
Migrated From Gitlab (gitlab-163): #164
Migrated From Gitlab (gitlab-164): #165
Migrated From Gitlab (gitlab-165): #166
Migrated From Gitlab (gitlab-166): #167
Migrated From Gitlab (gitlab-167): #168
Migrated From Gitlab (gitlab-168): #169

/cc @jasonpagetas

G'Day, @ozf
Noticed that you're a watcher on this project and would like to inform you that this project will be deleted due to the issues as notated in this issues OP.
Never fear though as the project is being recreated at the same path with the same name.

license: MIT


text:
Smart Select re-init page history -1, when option select and  close

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 1.6.4

Platform and Target:  CORDOVA

What you did
I have page_1  wich calls page_2 via a simple   href=''
page_2 has an smartselect like this:

Datos de la cabecera

		<form class="list-block inputs-list">

			            <select name="cmb_comprobante_tipo2" id="cmb_comprobante_tipo">
                                             <option value='1'> val 1</option>
                                             <option value='2'> val 2</option>
                                             <option value='3'> val 3</option>
                                             <option value='4'> val 4</option>
			            </select>

receipt

Tipo de comprobante

FACTURA C

MyApp is defined like this, so when you select in any option, it close the smartselect
var myApp = new Framework7({
    pushState: false,
    swipePanel: 'left',
    material: true,
    materialPageLoadDelay:0,
    materialRipple:true,
    materialPreloaderHtml:true,
    precompileTemplates: true,
    cache:true,
    template7Pages: true, // enable Template7 rendering for Ajax and Dynamic pages
    fastClicks:true,
    dynamicPageUrl: 'content-{{name}}',
    smartSelectBackOnSelect: true,

    // ... other parameters
});

BUT, when I click in an option and close the smartselect page, it refresh me page_1 executing the onPageInit method.
I don't know if it's the expected behavior but for me is not. ¿why re-init me the first page?

Expected

ok, it's rare that behavior. Page 1 has nothing to see with that smart-select.
If I need to capture the change of smart-select in page2 to assign that value and work with the result, when the back refresh me page1, it erase the content.
In my case I couldn't use it, and I had to change it to a normal select. Maybe someone happens to.
Could be optional this refresh.

This is unexpected

In all seriousness this is not a bug, it's a feature

chit
reply@reply.github.com
เมื่อ 17 มิ.ย. 2017 03:35 "VOUSYS" notifications@github.com เขียนว่า

This is a (multiple allowed):

bug
enhancement
feature-discussion (RFC)
Framework7 Version: 1.6.4
Platform and Target: CORDOVA
What you did
I have page_1 wich calls page_2 via a simple
page_2 has an smartselect like this:

Datos de la cabecera

 val 1
 val 2
 val 3
 val 4

receipt

Tipo de comprobante
FACTURA C

MyApp is defined like this, so when you select in any option, it close the
smartselect
var myApp = new Framework7({
pushState: false,
swipePanel: 'left',
material: true,
materialPageLoadDelay:0,
materialRipple:true,
materialPreloaderHtml:true,
precompileTemplates: true,
cache:true,
template7Pages: true, // enable Template7 rendering for Ajax and Dynamic pages
fastClicks:true,
dynamicPageUrl: 'content-{{name}}',
smartSelectBackOnSelect: true,
// ... other parameters

});
BUT, when I click in an option and close the smartselect page, it refresh
me page_1 executing the onPageInit method.
I don't know if it's the expected behavior but for me is not. ¿why re-init
me the first page?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nolimits4web/Framework7/issues/1645, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AT6XhQrg02ls65_m5YaevOQajotiX_xJks5sEub3gaJpZM4N86Dx
.

authors: ZanderBrown chittattoo snowbreeze vousys


text:
Added SignalR Hub and TumblerPhaseBroadcaster.

Have also added a call to the Broadcaster within TumblerstateMachine.UpdatePhase.
You can test by running - it will fire up a test html page with javascript to connect to client and a way to fire a broadcast back to the clients.

Ignore the comment in the Controller that says:
"//If collection.Count > 3 a SignalR broadcast is made to clients that connected via client-test"
As soon as you get client-test-broadcast in the controller it fires the broadcast.


text:
[ps-scroll-y]how to get scroll distance

hi,when i using the event ps-scroll-y.how can i know the scroll distance in y direction?
$(window).on('ps-scroll-y',function(){
   // is there any params that i can get scroll distance
})

thanks

You need get '.ps__scrollbar-y' dom element and read this 'offsetTop' property. But perfect-scrollbar fires events before re-render scrollbar dom element, and so 'offsetTop' property has old value (value before re-rendering scrollbar dom element).

You can just refer to scrollTop on scroll event.

authors: DMShamonov jslixiaolin noraesae

repo: noraesae/perfect-scrollbar


text:
Dispatch custom events on update and fix scroll-end event not being triggered when dragging

See commit descriptions for more info.

Thank you @axelboc! I'll have a look at this soon.

Awesome, thanks! :+1:

authors: DanielApt axelboc


text:
How to vectorize prompt creation?

I want to generate multiple prompts and run them via GPT.
Can we add support for vectorizing on top of text.prompt?
This gives me an error:
import outlines.text as text
import outlines

@outlines.vectorize
@text.prompt
def foo(input):
    '''
    Complete the line {{input}}
    '''

prompts = foo(["abc", "def"])

Maybe it's best not to support this, given the complexity of many arguments of different types.

We could implement that in the future, although I'd need to see a full example where a Python loop doesn't do the job.

authors: arunpatro rlouf

repo: normal-computing/outlines


text:
Masking/Hiding Value

Hopefully a simple question here:
Does Cleave have the ability to mask a value in an input after it has been typed, similar to a password input type.
so for example if someone typed in a credit card number it would be masked like:
####-####-####-1234
Thanks very much

@nosir Will there be any support for this feature?

@abhinukala sorry, this is not in the plan.

trying to figure this out as well

Hi, any news on this request @karlkras ? Did you manage to get a solution? Thanks!

authors: abhinukala jonnycraze msahores nosir srakl


text:
Configuration file spec

Capturing the configuration file, at its current state

This reflects the current implementation of #83
Suggestion to merge this and #83, and open Issues and PRs for the proposed name changes.
This provides a baseline to test and iterate with issues on functioning bits from main.

repo: notaryproject/notation


text:
图直接占了一页的三分之二

我看了那个浮动设置，参数设置为[h]

建议阅读浮动体位置最后部分，仅根据你目前给出的素材，我无法做出更多的判断。

这是我的tex文件部分

建议阅读浮动体位置最后部分，设置一下那两个参数，是否可以调节。

或者阅读断页机制切换开关，检查是否是所述问题。

感谢，改了段页机制，现在正常了


text:
alt+e won't open the menu

Hello, I'm using Notion Enhancer 2.0.18-1 (2.0.18-1) on mac os big sur 11.6.1. Unfortunately, no matter how many times I hit Alt+E, the Mod Menu will not open.
I've just got the latest version and my mac does not have the Original Notion app FYI.
What do you recommend ?
best

new update:
I followed this step and it resolved the problem for me: https://github.com/notion-enhancer/notion-repackaged/issues/82#issuecomment-1003435037
best

repo: notion-enhancer/desktop


text:
Add funding.yml

Changes:

Adds funding.yml entries for author's funding links.

Rationale:

This is one of the most useful tools available for PDS hackers

added it in a .github repo so it shows on all my repos instead

authors: jesselawson notjuliet

repo: notjuliet/pdsls


text:
add dart generator support

add dart generator support

@fanngyuan Thanks for sharing the PR. Dart is not a top priority for my project right now but it is certainly useful to have people experiment with Dart ahead of time.

authors: fanngyuan matbd

repo: novifinancial/serde-reflection


text:
onVideoStopped is double called

Problem
As per this, on stop and on release both call onVideoStopped.
Potential Solution
Only emit a state if it is different from the previous state. Similar to how we handle it for the play here.
Impact
Clients should not need to deal with multiple calls to the same state, it could potentially lead to inconsistencies and crashes, especially if we delay patching this.

This has been addressed and released as part of v2.0.6

repo: novoda/no-player


text:
update hyper to 0.10

Hyper 0.10 dropped unofficial serde support completely. This crate now is the only way to use serde with hyper. Please update hyper dependency to allow using this crate with hyper 0.10

This was done.

authors: imp nox


text:
Adding a modulesFolder option to allow overriding the directory to check...

... for dependencies (previously hardcoded to node_modules)

What's the use case for this change? I know it seems pretty self-contained (although it would need a test to land), but read-installed, due to its reliance on read-package-json and readdir-scoped-modules, is pretty much optimized solely for use with npm. I'd really like to avoid adding configurability that moves away from that without strong motivation.

I'm working on a utility to check the package.json against node_modules to see which packages are missing and/or wrong versions. With this small change to read-installed I would be able to use the same code to also check bower.json against bower_components.
This utility will be used as part of a gulp/grunt "watch" task. The idea is that when a developer pulls in new changes from git, this dependency-checker task will run and immediately let them know if they need to do an npm/bower install.

In that case, I don't think this change makes sense, and am -1 on it. As I said previously, there's a lot of magic baked in to read-package-json and some of the other dependencies of read-installed specifically for dealing with npm stuff. It might work for your purposes for Bower, and it might not, but I think you're way better off writing a purpose-built checker that's optimized for Bower.

I was afraid you'd say that ;). I was hoping that removing the hardcoded reference to "node_modules" would be motivation enough. It does look like read-package-json also has one hardcoded reference to "node_modules" (line #129). I could remove that one as well if it would help my case.

I don't want to rule out npm relaxing its dependencies on node_modules in the future, as we're still considering our options for making npm work better for managing front-end dependencies, but that should be done in the context of an overall change to npm, not just ad hoc like this.

It does look like read-package-json also has one hardcoded reference to "node_modules" (line #129). I could remove that one as well if it would help my case.

I think that just goes to underline my point – these modules aren't general-purpose filesystem tree-walkers that just happen to know about semver, they're calling things like normalize-package-data and readdir-scoped-modules that have lots of domain-specific specialization for npm. Repackaging them for other purposes might work now, but we've made pretty drastic changes to them recently for npm-related reasons, and pretty much have to reserve the right to do so in the future, so depending on their current behavior to work for a different package manager (which Bower is) seems like a bad plan to me.

Ok, fair enough. I get where you're coming from and I can't say as I 100% disagree w/ you.

It seems like this settled on a decision not to take this pull request, so I'm going to close this. Drop a note here if that's not the case and I'll reopen it.

authors: herbrandson iarna othiym23

repo: npm/read-installed

license: isc


text:
Deep Linking 利用時 LMS 側にある元のタイトルと説明文をそのまま使う

どのような問題を解決する機能追加でしょうか?
CHiBi-CHiLOのDeepLink設定では，CHiBi-CHiLOのブック名と解説をLMS側にtitle,textとして返す設定になっているが，実際に運用を始めると，LMS側ですでにtitle,textの情報が設定されているケースがあり，混乱を起こしてしまった，
そのため，LMS側ですでにtitle,textの情報をそのまま返すよう変更する．
あなたが望む解決方法について書いてください
該当箇所を修正する
https://github.com/npocccties/chibichilo/blob/0cf1bf8afe032e777f8e8fddf2de533ddf3b3332/server/services/ltiDeepLinking.ts#L74-L75
本 issue を close する条件

[x] コードに実装された。

追記・備考
Moodleは title にあたる「活動名」が空白の場合，ツールURL名（例えばCHiBi-CHiLO）を渡す仕様になっているが，これは許容する．

対応

repo: npocccties/chibichilo


text:
Reformat match expressions with visual indent

Rather than block indent. Check other expressions such as if to make sure they all do the same thing. We should probably fall back to block indent if we can't do visual indent. (Possibly some heuristic for when visual indent will look bad too).

Is this still an issue? We're now doing block indent unless an argument of a multi-line function call, in which case we do a visual indent. It works OK in most cases, I think.

authors: marcusklaas nrc

repo: nrc/rustfmt


text:
[nrf fromlist] drivers: pwm: nrfx: adjust PWM driver to fast PWM120

Fast PWM120 instance works with 320MHz clock, thus pwm_nrfx_get_cycles_per_sec needs to be adjusted.
Also, it uses cachable RAM, thus sys_cache function needs to be added to flush the cached sequence.
Upstream PR : https://github.com/zephyrproject-rtos/zephyr/pull/80672

There were changes to the [nrf fromlist] commits. Please fix commit body.
Upstream PR #:
Instead of the old:
Upstream PR:

authors: mstasiaknordic nordic-segl

repo: nrfconnect/sdk-zephyr


text:
Update sbt to 1.8.2

Updates org.scala-sbt:sbt from 1.6.2 to 1.8.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #246.


text:
Create tag 1.1.4 and update podspec

Hi, could you please create tag 1.1.4 and update the related pod with this version?
Thanks a lot!

done

authors: BubiDevs nst

repo: nst/STHTTPRequest


text:
WIP: enable section indexes by default, allow deeper nesting in sidenav

refactor sidenav to use recursion
add option to allow for deeper sidenav nesting
doc reorganization
breaking change version bump

TODO:

[ ] consider: add back in feature where an active page does not display as a clickable link in the sidenav
[ ] review documentation that refers to ^
[ ] unit tests
[ ] fix or write up TODO issue for the bug where there is an empty ul element
[ ] consider: prefix config.extra variables with mkdocs-terminal

[ ] consider: do they need to be caps?

[ ] update docs so that "navigation.side.indexes" is standard
[ ] remove references to "navigation.side.indexes" in code

Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.
Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, etc.
If the UI is being changed, please provide before/after screenshots.

References

Include any links supporting this change such as a:

GitHub Issue/PR number addressed or fixed
Related pull requests/issues from other repos

If there are no references, simply delete this section.

Testing

Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If there are existing unit and/or integration test suites, tests should be added for new functionality and existing tests should complete without errors.
Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
Also include details of the environment this PR was developed in (language/platform/browser version).

[ ] This change adds test coverage for new/changed/fixed functionality

Checklist

[ ] I have added documentation for new/changed functionality in this PR or in mkdocs-terminal/documentation
[ ] All active GitHub checks for tests, formatting, and security are passing

relates to #137

repo: ntno/mkdocs-terminal


text:
ci: Add commit message check

As part of our CI, we would like to add commit message checks. This patch tries to address this by checking the commit message for our internal policy regarding commits. More info in the CONTRIBUTING.md doc.

will revisit at some point

repo: nubificus/urunc


text:
Alternative update & installation

Updating system depends on python installing on target machine, sometimes it not working unless that machine is restart.
Let create a new binary named nmkup which copy functionality of rustup. This binary will manage

nmk (the config)
entrypoint
nmkpkg
itself

merge nmk and nmkup into single multicall binary

repo: nuimk/nmk


text:
Error handling clarification

Following the examples here a snippet of my code:
process.on('uncaughtException', err => {
    console.error((new Date).toUTCString() + ' uncaughtException:', err);
    console.error("Exiting...");
    process.exit(1)
})

// ...

var DB = require('node-adodb'), connection = DB.open('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=pathToDatabase.mdb');

function submit(data, callback) {
    var id = data.id;
    var query = // create query from data values

    connection
        .execute(query)
        .then(data => {
            return callback({ id: id, success: true });
        })
        .catch(error => {
            console.error('submit query failed: ' + error.process.message);
            return callback({ id: id, success: false });
        });
}

So I'm expecting that if the query fails it nicely calls the callback reporting the failure.
To test it, after initialization I suddenly remove the database file. The error is apparently handled:

submit query failed: Impossibile trovare il file pathToDatabase.mdb

but then the program crashes due to an "unhandled error":

Tue, 15 Jan 2019 12:33:23 GMT uncaughtException: { Error: Unhandled "error" event. ([object Object])
Exiting...

I'm running Node v8.12.0 under Windows 7.
I forgot something in the configuration/use of node-adodb?

Some exception throw by cscript, but cscript exception information is bad！

[I don't think is so nice to immediately close an issue without waiting for a while if users have any further question...]
Anyway, I kindly ask an example how to handle such a situation. I understand cscript exception information is bad, but I cannot let my program crash. Would you mind to show m how to change my snippet above in order to correctly catch the exception? Thanks in advance.

repo: nuintun/node-adodb


text:
🛑 Difesa is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Difesa is back up in 4d3d3c2.


text:
🛑 Difesa is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Difesa is back up in 083b928.


text:
🛑 Università e ricerca is down

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

HTTP code: 403
Response time: 589 ms

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


text:
🛑 Salute is down

In 9c776ea, Salute (http://www.salute.gov.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Salute is back up in 985246d after 9 hours, 47 minutes.


text:
🛑 Università e ricerca is down

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

HTTP code: 403
Response time: 618 ms

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


text:
Why does opleader create mapping in both normal and visual mode?

Why does opleader create a mapping in both normal and visual mode? I noticed that the mapping I set for operator-pending mode appears as an xmap as well. Is there a specific reason for why it is set in visual mode as well? Is it even possible to perform an operator-pending command from visual mode?
From the README:
---LHS of operator-pending mappings in NORMAL + VISUAL mode
---@type table
opleader = {
    ---Line-comment keymap
    line = 'gc',
    ---Block-comment keymap
    block = 'gb',
},

Is there a specific reason for why it is set in visual mode as well?

Because then in visual mode you will be able to do something like V10jgc to comment 10 lines in visual mode.

Ok I think see your point.
It sorta clashed with my setup because I wanted try using as cm as a trigger in normal mode and <leader>c in visual mode, but this caused cm to become an operator in visual mode as well which I didn't want.
I'll just use #98 to set up my mappings instead as you suggested in #104.

authors: melkster numToStr


text:
Remove reference existing issue from GH template.

As title.

Whilst well intentioned, this hasn't really been used, elected to removed.

repo: numba/numba


text:
Try xml test reporting in Azure

https://github.com/numba/numba/pull/8630#issuecomment-1334114164 is another case why this is needed

This is going to be redesigned.

authors: apmasell sklam


text:
Update README.md

漏了个字

非常感谢！

authors: ferstar numbbbbb


text:
devshell doesn't work with flake version of nix-direnv 1.5.0

Describe the bug
Nix-direnv 1.5.0 has stopped executing the shellHook when cached in the flake version of it since that mirrors how the classic nix version works (it doesn't execute the shellHook). Since, afaict, devshell depends on the shellHook executing even when cached this broke devshell on nix-direnv 1.5.0.
Personally I'm not entirely sure it is correct to stop executing the shellHook since, as the pull request that changes this behavior in nix-direnv notes, nix develop does in fact always execute the shellHook. So the bug might actually be in nix-direnv.
To Reproduce
Update nix-direnv to 1.5.0, then try entering a directory with a devshell in it that is already cached and you'll find that you don't have any of the expected executables in PATH.
Expected behavior
That devshell works together with nix-direnv 1.5.0
System information
nix-direnv 1.5.0 and devshell from master.
Additional context
This is a relevant issue in nix-direnv: https://github.com/nix-community/nix-direnv/issues/109

I think the issue is on nix-direnv's side.

Nix-direnv PR is merged; we can probably close this?

authors: charmoniumQ johnae zimbatm

repo: numtide/devshell


text:
Test ourselves

@nunomaduro This is very interesting.

My two PRs also address this (fix errors):
#65, #66.

Thank you.

@szepeviktor Thanks! Just merged and upgraded the --level to max.

@nunomaduro Thanks.
Please remove the change from tests/laravel-test.sh as it does exactly the same for the second time.

authors: nunomaduro ondrejmirtes szepeviktor

repo: nunomaduro/larastan


text:
feat: support sole method

[x] Added or updated tests
[ ] Documented user facing changes
[x] Updated CHANGELOG.md

Changes
Add support for the sole method on Laravel 8.
(sorry I did something wrong and it auto-close the previous PR… Don't really know why…)

@canvural As I was expected the sole presence of the docblock on the other versions is failing the tests.

Ah, you are right. I totally forgot about that. I'm sorry!
Ok then let's remove it and hope PHPStan merges definitions from stubs and actual method reflections :smile:

hope PHPStan merges definitions from stubs and actual method reflections

Stubs are there specifically to overwrite actually PHPDoc blocks in the source code.

Thank you!

authors: ThibaudDauce canvural szepeviktor


text:
Add a Gitter chat badge to README.md

nupic-community/nupic.visualizations now has a Chat Room on Gitter
@jefffohl has just created a chat room. You can visit it here: https://gitter.im/nupic-community/nupic.visualizations.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

:+1:

authors: breznak gitter-badger


text:
How much "Stream" should we use?

Summary
kinda late to be asking this but I'm slightly confused of how much of our code should utilize Stream?
Description
In Lab 7, we are told to use Java Streams for our method implementations. But are we expected to only use stream methods and do everything in the pipeline or can we use other additional things or data structures? :sweat_smile:

Hi, for question 3, I was thinking of using reduce in the function. For example, the reduce would compare a value with the value before it and the value after it, but this would require 3 parameter inputs, and ternary conditional operators, is there any way I could input 3 parameters into stream functions?

@zxgoh I don't think that Stream can take 3 inputs, but not sure. Maybe one way to do it is that from 1 integer i, based on what u mentioned, you can access array[i-1] and array[i+1].

Hi, for question 3, I was thinking of using reduce in the function. For example, the reduce would compare a value with the value before it and the value after it, but this would require 3 parameter inputs, and ternary conditional operators, is there any way I could input 3 parameters into stream functions?

@zxgoh I don't think that Stream can take 3 inputs, but not sure. Maybe one way to do it is that from 1 integer i, based on what u mentioned, you can access array[i-1] and array[i+1].

@zxgoh yep! as mentioned, you can't really pass in multiple parameters - one workaround is to create a helper class that can hold 3/4 values, and update them using a process function that you can then call inside reduce
Your code will look something like this:
Helper Class
class Helper {
    private final int sum;
    // insert your other values here
    ...
    Helper process(Helper h2) {
        // construct a new helper class that has your updated values
        return new Helper(...)
    }
}

Main
stream.map(x -> new Helper(x))
    .reduce(new Helper(), (r1, r2) -> r1.process(r2))
    ...

Hi, for question 3, I was thinking of using reduce in the function. For example, the reduce would compare a value with the value before it and the value after it, but this would require 3 parameter inputs, and ternary conditional operators, is there any way I could input 3 parameters into stream functions?

@zxgoh I don't think that Stream can take 3 inputs, but not sure. Maybe one way to do it is that from 1 integer i, based on what u mentioned, you can access array[i-1] and array[i+1].

ahh i see, i tried that method of accessing the array instead and it worked, thanks!

authors: JavierTham cliftonfelix mjgui zxgoh


text:
Weird behavior case 8_1.in

Hi! Anyone know why 14 queues at 2 instead of 1 (see pic below)?  The state of the servers then is:
Server 1: [10, 13] (i.e. slot for one more, 10 is serving and 13 is waiting now)
Server 2: [12]
My understanding is they are allocated based on Server numbers as

A customer that chooses the first queue available and joins at the tail

and this is corroborated by the previous lines which are consistent with this.
However, in this case it seems to possibly be allocated by balancing queue length (inconsistent with previous lines) or completion time (requiring Lazy.get() to be called eagerly, thus not possible).
Am I missing something?
Thank you!

Okay I think I pulled restTime wrongly, oops

hi @shotnothing im facing the same issue,, may i know how u fixed the problem?

authors: elysiaojr shotnothing


text:
Ex 5 Maybe

Hello, does anyone know why is the test case here true? Shouldn't the equals method return true when "the contained values are "equal to" each other via their respective equals method." In this case new A(1).equals(new B(1)) is true?

I think there is some form of inheritance relationship between A and B, making A and B substitutable, and thus ma.equals(mb) returns true . You could check if your main if statement uses Maybe<?> rather than Maybe<T>, as that clause is supposed to check the .thing attribute as long as other is a Maybe.

Agree with @wjiayis's comment, if you did a else if obj instanceof Maybe<T> then it wouldn't enter the clause and thus return false.

I think there is some form of inheritance relationship between A and B, making A and B substitutable, and thus ma.equals(mb) returns true . You could check if your main if statement uses Maybe<?> rather than Maybe<T>, as that clause is supposed to check the .thing attribute as long as other is a Maybe.

Hi thanks for the reply! I already did a Maybe<?> typecast. However I did try to include a maybe.thing.equals(this.thing) statement. This throws an error whenever a Maybe.empty() is compared. How do you check for the fact that other.thing has an inheritable relationship with this.thing

Hi, to compare between Maybe.empty(), you would need to do a check to see if this.thing is null. If it is, then you check if the other thing is null as well. Your current error is thrown because null does not have a .equals() method iirc.

Agreed with @wjiayis above, I personally used if-else clauses to account for the cases where both things are null and where both things are not null.

yep managed to find the bug! thanks guys!

authors: jamielfh junhuiii wjiayis zclzz


text:
Test case 7 Lab 3

Summary
Hi all, I am facing an error for test case 7 in lab 3 and am having trouble identifying the source of the error. Would anyone be able to advise me where to look for the error?
Screenshots

hi! i think this test case usually they catching people who invoked getServiceTiming() at the wrong place (i had this error too). did u call it while ur Serve is being executed?

From your screenshots, it is not enough to narrow down where exactly went wrong. Try to manually create a larger test case (say 5 servers and 15 customers) then print out the timings and figure out whichever event is causing you issues.

U gave customers a service time once they entered the queue, which is not what the question requires.
For customers waiting in a queue they dont have service time, service time is only given when the customer exits the queue and gets served by the server.

thank you everyone for your help! finally managed to get a correct implementation.

authors: Xiang-le gnimnix iceflakes12 xiang-qiuyu


text:
[v1.x][T16-B2] Work In Progress

This PR will update as we make change to our master code such that our progress can be monitored

@asiddharth @meerakanani10 @ncaminh @ngshikang @mattbuot
To track changes in the team repo

Could you change the PR name to be [v1.0][T16-B2] <Project_name> ? Next PR should be titles [v1.1][T16-B2] <> and so on.

Target User Profile also has to be updated

how do we make a new PR for v1.1 if we haven't closed this one? or should we just rename this on for v1.1

Review comments at : https://github.com/nus-cs2103-AY1718S2/addressbook-level4/pull/105

@meerakanani10 @ncaminh @ngshikang @mattbuot
The code collation should be in a folder called collated in the root. Under collated there should be a functional and test folder. You do not have to change the location of the collated files.  Sorry for the confusion during the tutorial.

authors: asiddharth meerakanani10 ngshikang


text:
[CS2103T-W11-2] Staff'd

Staff'd helps restaurant managers manage their staff. It is optimised for CLI users so that frequent tasks can be done faster by typing in commands.

Codecov Report

Merging #83 (f18915f) into master (ba53b8c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #83   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 ba53b8c...f18915f. Read the comment docs.

authors: Gabau codecov-commenter


text:
[W5][T08-3]Sean Yap

Added sort functionality that sorts all the people in the address book into ascending order according to their full name. Only in ascending order for now.

Overall a good working implementation of the added functionality with correct coding style!
Great update to I/O & JUnit Tests!
Just some minor comments below:
https://github.com/nusCS2113-AY1819S2/addressbook-level2/blob/e95fec5d9eeef3f99259ea46b369b531efe21ba5/src/seedu/addressbook/commands/SortCommand.java#L1-L8
Consider updating the comments to indicate the new behavior that you have incorporated in this class.
https://github.com/nusCS2113-AY1819S2/addressbook-level2/blob/e95fec5d9eeef3f99259ea46b369b531efe21ba5/test/java/seedu/addressbook/data/AddressBookTest.java#L126-L132
I noticed that you implemented the sort() test in Addressbook Class. Since sort is a command, maybe it is better to create a SortCommandTest under commands instead? Nevertheless, this test still suffices in checking for functionality of the sort function implemented.

Overall a good working implementation of the added functionality with correct coding style!
Great update to I/O & JUnit Tests!
Just some minor comments below:
addressbook-level2/src/seedu/addressbook/commands/SortCommand.java
Lines 1 to 8 in e95fec5
package seedu.addressbook.commands;
/**

Lists all persons in the address book to the user.
*/
public class SortCommand extends Command {

Consider updating the comments to indicate the new behavior that you have incorporated in this class.

Oh yes, thanks for informing this, a clumsy mistake on my part ! This has been edited in the latest commit.

addressbook-level2/test/java/seedu/addressbook/data/AddressBookTest.java
Lines 126 to 132 in e95fec5
@Test
public void sort() throws Exception {
UniquePersonList unsortedPersons = defaultAddressBook.getAllPersons();
UniquePersonList personsToCheck = new UniquePersonList(aliceBetsy, bobChaplin, charlieDouglas, davidElliot);
unsortedPersons.sort();
assertTrue(isIdentical(unsortedPersons, personsToCheck));
}
I noticed that you implemented the sort() test in Addressbook Class. Since sort is a command, maybe it is better to create a SortCommandTest under commands instead? Nevertheless, this test still suffices in checking for functionality of the sort function implemented.

I chose not to do this as similarly with the list command, these commands are not the same as with the others, there is no change in output and no exception/error messages thrown regardless of the state of the program. But it is true that it is still a command on its own. This could be done in the future.
the list command was too not implemented the same way as with other commands.

See my comments for suggestions. Please close this PR after reading comments.

authors: 0WN463 marcus-pzj seanieyap


text:
[FEATURE] Add helpers for the replied messages

Is your feature request related to a problem? Please describe.
My Code:

Natgram has helpers  for users and current user messages. But it seems that there is no helper for the messages that are replied to.
For example, suppose in a group user A replies to user B's message, there is no helper to get the details of user B's message.
Suppose I want to get the user_id or chat_id of user B's message easily (like this: $bot->userId() or $bot->chatId()). But this is not possible.
It would be good if helpers for replied messages were added.
This is sometimes confusing and causes small bugs in the program. Because not all developers are professionals and are not familiar with the Telegram API. For example, if our code is as follows:
// Suppose the input update sent from an group:
$userId = $bot->message()->reply_to_message->chat->id;

// Above code return the group's chat_id and not the user's chat_id and finally it sometimes causes small bugs like this...

Describe the solution you'd like
I can't think of a solution, but if it can be done like this, it might be good:

Describe alternatives you've considered
No response
Additional context
These additional helpers can be added as well:
$bot->repliedMessage()->user();
$bot->repliedMessage()->chat();
//....

We will not add a repliedMessage helper for now.
Just do this:
$user_id = $bot->message()?->reply_to_message?->chat->id ?? $bot->userId();

repo: nutgram/nutgram


text:
fix: Can't render pages on older versions of Nuxt if options.watch is missing

If nuxt.config.js doesn't contain a watch property, Nuxt v1.4.2 fails to render a page with a TypeError: Cannot read property 'push' of undefined error.
This PR adds an empty watch array to the options as a fallback to fix the issue.
Tested on Nuxt v1.4.2 and v2.14.6

@arikw thanks

authors: arikw ricardogobbosouza

repo: nuxt-community/eslint-module


text:
Custom input/output path brakes building process

How to reproduce:
Specify the custom path for input/output property, e.g. :
input: ~/static/icons/svg
output: ~/static/icons/gen
Actual Result:
Build fails with an error:

~/assets/sprite/gen/sprites.json in ./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@nuxtjs/svg-sprite/lib/pages/icons-list.vue?vue&type=script&lang=js&

Expected result:
Build should compile successfully
This issue is caused by the fact that the sprite path is hardcoded in icon-list.vue to ~/assets/sprite/gen/sprites.json. This path should reflect an output path instead

i have the same issue

Sorry for the late response.
This is a mistake of mine, icons-list should've placed at buildDir and read output path from module options. I'll fix it ASAP
@nassosyian creating option to disable icons list is not solution for this issue

authors: AndrewBogdanovTSS farnabaz nassosyian

repo: nuxt-community/svg-sprite-module


text:
Not usable on Client Side

Hello!
Currently, I am in an environment where one function gets called both on server-side and on client-side:
import devalue from '@nuxt/devalue'
// ...
transformState(state) {
  return import.meta.env.SSR ? devalue(state) : state
}
// ...

However, even when the check import.meta.env.SSR returns false and the function devalue does not get called, I still get a ReferenceError.
Hence, I added a PR #16 that checks for the node internal process in order to make this package usable in an environment where no process is available.
Thanks for this awesome package btw!

Hi @pantajoe. #16, as well as a set of huge, refactors to improve esm/universal compatibility released as 2.0.0-0 (prerelease to test changes). Please let me know about your experience with new release and anything else is missing :)

Hey, @pi0! Sorry for the rather late answer, but the new prerelease works like a charm for me! Both on client and on server sides, I have no issues with dependencies, environment variables or functionality. Also, the new build process really did something 😄 I no longer have to define an alias in by wepack/rollup config for it to work with vite.
Thanks!

repo: nuxt-contrib/devalue


text:
useLocaleHead stop workding when upgrade to 8.0.0-rc.5

Environment

Operating System: Linux
Node Version:     v18.17.0
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager:  pnpm@8.7.5
Builder:          -
User Config:      typescript, $development, runtimeConfig, build, nitro, modules, unocss, i18n, image, vue, $production
Runtime Modules:  @unocss/nuxt@0.56.5, @nuxtjs/i18n@8.0.0-rc.5, @nuxt/image@1.0.0-rc.3
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-s3mfea-rnbn7m?file=layouts%2Fdefault.vue
Describe the bug
When I upgrade from 8.0.0-rc.3 to 8.0.0-rc.5, useLocaleHead stop working.
Additional context
No response
Logs
[vue-i18n-routing] Locale ISO code is required to generate alternate link

Hmm, It appears to have been degrade by rc.5 release. /cc @BobbieGoede
https://github.com/nuxt-modules/i18n/compare/v8.0.0-rc.4...v8.0.0-rc.5

Ah, I believe this is a bug introduced by my refactor, sorry about that! 🙏
Fortunately there is a simple workaround for this, if you add another property to each locale, it should work as expected. I recommend adding a name to each locale, but any key will do. I have changed your reproduction to demonstrate here.
As for the reason this happens, the shape of the configured locales { code: string; iso: string; } is identical to the shape of string locales after being normalized. My bug incorrectly tries to restore the original configuration and writes that to .nuxt/i18n.options.mjs, I will look into a fix shortly!

authors: BobbieGoede everyx kazupon


text:
Version 2.11.0 is crashing

I'm running npx create-nuxt-app <project-name>
I got this:
create-nuxt-app v2.11.0
✨  Generating Nuxt.js project in renasci
Trace: { Error: Cannot find module './prompts'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/Users/jhiguitasanchez/.config/yarn/global/node_modules/create-nuxt-app/saofile.js:9:12)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3) code: 'MODULE_NOT_FOUND' }
    at sao.run.catch (/Users/jhiguitasanchez/.config/yarn/global/node_modules/create-nuxt-app/cli.js:46:17)

Node version: v10.16.0
npm version: 6.9.0
https://github.com/nuxt/create-nuxt-app/releases/tag/v2.11.0

version https://github.com/nuxt/create-nuxt-app/releases/tag/v2.10.1 is working very well

How can i use old version to create nuxt-app?

@wrtisans I don't know how to specify a version with yarn. However, if you can use npx, try doing:
npx create-nuxt-app@2.10.1 warrenbrasil.com

@wmartins thanks, it works!! hope can fix the bug soon!

duplicate of https://github.com/nuxt/create-nuxt-app/issues/350#issuecomment-536716487

authors: aldarund jeisonhiguita wmartins wrtisans

repo: nuxt/create-nuxt-app


text:
Using CSS inlined style to import images

I have searched throughout the issues in Nuxt and Next and found no solution to importing images directly in the vue <template>.
Here is what I am trying to do:
<template lang="html">
    <div class="background" :style="{ backgroundImage: `url(${backgroundUrl})` }">
</template>

Basically this component needs to accept a prop of backgroundUrl and needs to be inline styled so that I can use this component on different pages with different backgrounds.
Thoughts?
EDIT: One way that I can think of is add the images into the static folder and call the directly, but I'm not sure that's the best way to approach this since I want all my images to be in one folder assets/images.

You may have a try.
<template>

    <div class="background" :style="{ backgroundImage: `url(${backgroundUrl})` }">

</template>

Did some digging and realized that I have ran into a require context issue explained in https://webpack.js.org/guides/dependency-management/
I did mention that backgroundUrl is a prop. So my solution to the issue (for those interested) is:
index.vue
<app-hero :background-url="require('~/static/images/hero.jpg')">Tagline</app-hero>

AppHero.vue
<div :style="{ backgroundImage: `url(${backgroundUrl})` }">Content with background here

Doing this gives me the flexibility to reuse AppHero on multiple pages with different background images. If anyone has a better solution to this let me know. I personally think including the require everywhere is dirty.


text:
How to config server to serve /api ?

https://nuxtjs.org/api/configuration-servermiddleware shows if I define handler function in serverMiddleware spec, I can do that. But the question is how?  Here's my setup:
server.js:
const
fastify = require('fastify')
,{Nuxt, Builder} = require('nuxt')
,config = require('./nuxt.config.js')
,host = process.env.HOST || '127.0.0.1'
,port = process.env.PORT || 3000
,nuxt = new Nuxt(config)
,app = fastify()

// Enable live build & reloading on dev
if (config.dev) {
  new Builder(nuxt).build()
}

// __ONLY one of these work as they conflict__:
// app.register(require('./api/index'), {prefix: '/api'})
// app.use(nuxt.render)

app.listen(port, host)

api/index.js:
module.exports = async function (fastify, opts, next) {
  fastify.get('/', (req, reply) => {
    reply.send({ hello: 'world' })
  })
}

thanks.

If you just want to forward that traffic under '/api' to some other service, then there are  out-of-box solutions for you. See belwo:
https://github.com/nuxt-community/axios-module
https://github.com/nuxt-community/proxy-module

@fuzzthink did you find a solution?

Why not turning the way around and use a serverMiddleware for the API endpoint (similar to my sending email example)?

authors: chanlito fuzzthink husayt manniL


text:
Replace src from method

Hello,
How do we change the src from a method?

I get a 404 error.
Help please.

<template>

    {{ msg }}

</template>

Thank You @Atinux

authors: Atinux tenjojeremy


text:
Middleware for a specific page not working.

Hi,
MIddleware does not work when I do the following:

Moreover when I add the midleware to the nuxt.config.js file as shown in the docs. the app brakes.
Thank you in advance.

Hi @tenjojeremy
Where is located your fixtures.vue  file?

@Atinux
It is located inside the components folder.
Oh, so middleware only works on files under pages?

Yes, only for pages components.

Got it.
Thank you! @Atinux


text:
How can i disabled polyfill ?

What problem does this feature solve?
I want use polyfill-service, so i need disable nuxt default polyfill
i do this but not work
babel: {
  presets({ isServer }, [preset, options]) {
    options.useBuiltIns = isServer ? 'usage' : false
  },
}

What does the proposed changes look like?
babel: {
  presets({ isServer }, [preset, options]) {
    options.useBuiltIns = isServer ? 'usage' : false
  },
}

can work

This feature request is available on Nuxt community (#c9446)

Your proposal should work fine, could you provide a reproducible repo ?

@clarkdo
reproducible  repo
step

clone repo
yarn
npm run dev

> nuxt

   ╭─────────────────────────────────────────────╮
   │                                             │
   │   Nuxt.js v2.8.1                            │
   │   Running in development mode (universal)   │
   │                                             │
   │   Listening on: http://localhost:3000/      │
   │                                             │
   ╰─────────────────────────────────────────────╯

ℹ Preparing project for development                                                       23:49:13
ℹ Initial build may take a while                                                          23:49:13
✔ Builder initialized                                                                     23:49:13
✔ Nuxt files generated                                                                    23:49:13

✖ Client
  Compiled with some errors in 4.02s

✔ Server
  Compiled successfully in 3.34s

                                                                                23:49:16
The `corejs` option only has an effect when the `useBuiltIns` option is not `false`

 ERROR  Failed to compile with 21 errors                                  friendly-errors 23:49:19

These dependencies were not found:                                        friendly-errors 23:49:19
                                                                          friendly-errors 23:49:19
* @babel/runtime-corejs2/core-js/array/is-array in ./.nuxt/index.js, ./.nuxt/components/nuxt.js
* @babel/runtime-corejs2/core-js/date/now in ./.nuxt/index.js, ./.nuxt/components/nuxt-link.client.js
* @babel/runtime-corejs2/core-js/get-iterator in ./.nuxt/utils.js, ./.nuxt/components/nuxt-link.client.js
* @babel/runtime-corejs2/core-js/json/stringify in ./.nuxt/client.js      friendly-errors 23:49:19
* @babel/runtime-corejs2/core-js/object/assign in ./.nuxt/client.js       friendly-errors 23:49:19
* @babel/runtime-corejs2/core-js/object/define-property in ./.nuxt/index.js, ./.nuxt/components/no-ssr.js
* @babel/runtime-corejs2/core-js/object/get-own-property-descriptor in ./.nuxt/index.js, ./.nuxt/components/no-ssr.js
* @babel/runtime-corejs2/core-js/object/get-own-property-symbols in ./.nuxt/index.js, ./.nuxt/components/no-ssr.js
* @babel/runtime-corejs2/core-js/object/keys in ./.nuxt/utils.js, ./.nuxt/components/no-ssr.js
* @babel/runtime-corejs2/core-js/promise in ./.nuxt/client.js, ./.nuxt/components/nuxt-link.client.js
* @babel/runtime-corejs2/core-js/symbol in ./.nuxt/utils.js               friendly-errors 23:49:19
* @babel/runtime-corejs2/core-js/symbol/iterator in ./.nuxt/client.js     friendly-errors 23:49:19
* @babel/runtime-corejs2/regenerator in ./.nuxt/index.js                  friendly-errors 23:49:19
                                                                          friendly-errors 23:49:19
To install them, you can run: npm install --save @babel/runtime-corejs2/core-js/array/is-array @babel/runtime-corejs2/core-js/date/now @babel/runtime-corejs2/core-js/get-iterator @babel/runtime-corejs2/core-js/json/stringify @babel/runtime-corejs2/core-js/object/assign @babel/runtime-corejs2/core-js/object/define-property @babel/runtime-corejs2/core-js/object/get-own-property-descriptor @babel/runtime-corejs2/core-js/object/get-own-property-symbols @babel/runtime-corejs2/core-js/object/keys @babel/runtime-corejs2/core-js/promise @babel/runtime-corejs2/core-js/symbol @babel/runtime-corejs2/core-js/symbol/iterator @babel/runtime-corejs2/regenerator
ℹ Waiting for file changes                                                                23:49:19
ℹ Memory usage: 183 MB (RSS: 255 MB)

@falstack Will be fixed in next release. For now you can fix the error by adding @babel/runtime-corejs2, but it may have some polyfill added by runtime plugin:
yarn add @babel/runtime-corejs2

authors: clarkdo falstack


text:
Factory function to create useFetch and useAsyncData with defaults

Describe the feature
It is common that a (bigger) project and library/module authors want to create a composable that is based on either useFetch or useAsyncData and provides some defaults.
There is a nice example by @516310460 that demonstrates it in nuxt/framework#6995.
The basic idea is to create factory composables that wrap useFetch and useAsyncData with defaults while preserving the behavior:

export const useMyAPI = createFetch(/* defaults */)
export const useMyAPI = createAsyncData(/* defaults */)

Currently it is possible with $fetch.create to make const useMyAPI = $fetch.create(/* defaults */) but it is just plain fetch without benefits of useFetch with reactivity.
With this new factory function, we can also find an opportunity to auto-generate keys for these custom instances too based on eager scanning with AST or fast regex. Currently, if a wrapper is custom-made, the key and state of any usage are shared and the same.
Additional information

[ ] Would you be willing to help implement this feature?
[X] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

@danielroe I'm up to add a composable exemple with onRequest in the docs if needed

@adrienZ That would be great!

Hello everyone!
This is what I've been trying to do myself for the last month... and still unsuccessfully.
I mention this problem in this ideas section, but it not get attention. Then i wrote this discussion which do not get attention as well.
This problem needs to be solved first of all in my opinion. And that's why:
Large projects must be well structured to be flexible and easily scalable. There is one idea that at least my company uses in every project - сomponents/pages must not contain request code. This means you should have a place to store all your requests as individual functions which you can use in components. It allows you to keep your components/pages clean and also you now has a single point of truth for all your backend requests.
In our old project we use nuxt2 + axios. We have a file structure like this:

endpoints.ts files in our project contains somthing similar to this code:
export const GET_USER = defineEndpoint((id: number) => {
  url: `api/users/${id}`,
  method: 'GET',
});

requests.ts files use endpoints.ts and contains somthing  similar to this code:
import { GET_USER } from './endpoints.ts';

interface User {
  id: number;
  firstName: string;
  lastName: string;
}

export const getUser = defineRequest<User>(GET_USER);
// returns (id: number, options: RequestOptions = {}) => axios({ ...GET_USER, ...options});
// options: RequestOptions allows you to fullfil request with additional options on call if you want
// axios() contains axios instance with default parameters such as baseUrl.

Then you are able to use this request function in your nuxt page:
<template>
  ...
</template>

<script>
import { getUser } from 'api/users/requests';

export default {
  methods: {
    async fetchUser() {
      const data = await getUser(this.selectedUserId);
    }
  },
};
</script>

It would be awesome if Nuxt 3 had such feature!
But for now it's very complicated to create such composition and keep all types, functionality and code cleaness.

had some trouble with pnpm, the PR is ready for you @Atinux :)

I'm also trying to create useFetch wrapper. But when I try to make another call inside this wrapper, it throws an error of nuxt instance not available. I'm catching 401 error and using refresh token api to refresh access token and again make the same old request but it doesn't work on server side give the error of nuxt instance not available.

@Awais-019 Check this discussion: https://github.com/nuxt/nuxt/discussions/20392.

I hope it will help someone. What works for me, provides proper types for options (default, transform, pick etc.):
import type { UseFetchOptions } from '#app'
import type { KeysOf } from 'nuxt/dist/app/composables/asyncData'

function useApiFetch <T, R = T, K extends KeysOf<R> = KeysOf<R>, D = null>(path: string, options: UseFetchOptions<T, R, K, D>) {
  return useFetch(path, options)
}

There's example of creating custom useFetch composable in nuxt docs however demo for custom $fetch is missing.

I'm using the following as a wrapper
import { defu } from 'defu'
import type { UseFetchOptions } from '#app'
type Url = string | (() => string)

export default function () {
  const baseURL = useRuntimeConfig().public.baseUrl
  const lang = useLocaleUtils().localeLanguage.value
  const userToken = useAuth().token

  function useCustomFetch<T>(url: Url, customOptions: UseFetchOptions<T> = {}) {
    const defaults: UseFetchOptions<T> = { baseURL, headers: { lang, Authorization } }
    const options = defu(customOptions, defaults)
    return useFetch(url, options)
  }

  return { useCustomFetch }
}

Passing a DataT works and I get type support for the response type
But passing an ErrorT I get an error
// Works and I get type suppport
 const { data, error } = await useCustomFetch<DataT>('/user')

// Type Error: Expected 1 argument but got 2
 const { data, error } = await useCustomFetch<DataT,ErrorT>('/user')

// Works with plain `useFetch`, but need to send headers manually with each call
 const { data, error } = await useFetch<DataT,ErrorT>('/user')

Has someone stumbled into this?

I didnt read all of the issue but please dont forget $fetch itself :)

Hey @danielroe I guess with v4 we can fix this (There will be major release so Nuxt can make some bold move here), WDYS?

`I didnt read all of the issue but please dont forget $fetch itself

$fetch is similar to native fetch primitive and is stateless. Modifying global APIs behavior is an inherently dangerous design. Anything we introduce would be under a new explicit name.

But I want to set the base url so api/my-route does not link to integrated Nitro server but instead to my external API.
I extensively use useFetch, useLazyFetch and $fetch in my Nuxt app. It wouldnt make sense if can only set this for useFetch and useLazyFetch.

You can use $fetch.create to create a custom preconfigured fetch instance for your needs.

Will this feature be implemented in v4?

Related: https://github.com/nuxt/nuxt/discussions/28357
Maybe there should be a way of telling useAsyncData to not catch (or rethrow 🤔) any error?

useAsyncData is a composable (= declarative), and if you are using it imperatively and expect it to throw then that's an indication you should probably be using using something else, like directly calling $fetch.

Here is what I have comeup with. @danielroe Could you please provider your take on this code snippet.
import constants from "~/constants";
export default defineNuxtPlugin((nuxtApp) => {
  return {
    provide: {
      api: {
        authorizedRequest,
        publicRequest,
      },
    },
  };
});

/**
 * The function `authorizedRequest` sends authorized requests with auth token and refreshing tokens logic.
 * @param request - same as the `request` parameter in the `$fetch` function.
 * @param options - extended from `options` of $fetch and extra options
 * `authToken` - authentication token used to authorize the request.
 * `refreshToken` - function to refresh the authentication token if it has expired.
 * `maxRetries` - max number of retries if authentication token has expired.
 * `retryCount` - current retry count.
 * @returns returns a Promise of type `T`.
 */

type Request = Parameters<typeof $fetch>[0];
type Options = Parameters<typeof $fetch>[1];

type ExtendedOptions = Options & {
  authToken: string;
  refreshTokens: () => Promise<string>;
};

async function authorizedRequest<T>(
  request: Request,
  options: ExtendedOptions,
): Promise<T> {
  try {
    const response = await $fetch<T>(request, {
      ...options,
      headers: {
        ...options.headers,
        Authorization: options.authToken,
      },
      baseURL: useRuntimeConfig().public.baseURL,
    });
    return response;
  } catch (error: any) {
    if (error.statusCode == constants.STATUS_UNAUTHORIZED) {
      const newToken = await options.refreshTokens();
      if (newToken != "") {
        options.authToken = newToken;
        return authorizedRequest(request, options);
      }
    }
    throw error;
  }
}

/**
 * This function makes a public request that does not require authentication.
 * @param request - same as the `request` parameter in the `$fetch` function.
 * @param options - same as the `options` parameter in the `$fetch` function.
 * @returns A Promise of type T is being returned.
 */

function publicRequest<T>(
  request: Request,
  options?: Options,
): Promise<T> {
  return $fetch<T>(request, {
    ...options,
    baseURL: useRuntimeConfig().public.baseURL,
  });
}

declare module "#app" {
  interface NuxtApp {
    $api: {
      authorizedRequest: typeof authorizedRequest;
      publicRequest: typeof publicRequest;
    };
  }
}

waste me a lot of time for setting a default baseURL in project scope

Also interested in having a way to do that directly from within nuxt but in case that can help, here's what I've done:
// utils/createCustomUseFetch.ts
import type { FetchResult, UseFetchOptions } from "#app";
import type { AvailableRouterMethod, NitroFetchRequest } from "nitropack";
import type { KeysOf } from "#app/composables/asyncData";
import { defu } from "defu";
import type { DefaultAsyncDataValue } from "#app/defaults";

export function createCustomUseFetch<
    O extends Partial<
        Omit<
            UseFetchOptions<unknown>,
            | "key"
            | "transform"
            | "body"
            | "default"
            | "method"
            | "params"
            | "pick"
        >
    >,
>(baseOptions: O) {
    return <
        ResT = void,
        ReqT extends NitroFetchRequest = NitroFetchRequest,
        Method extends AvailableRouterMethod<ReqT> = ResT extends void
            ? "get" extends AvailableRouterMethod<ReqT> ? "get"
            : AvailableRouterMethod<ReqT>
            : AvailableRouterMethod<ReqT>,
        _ResT = ResT extends void ? FetchResult<ReqT, Method> : ResT,
        DataT = _ResT,
        PickKeys extends KeysOf<DataT> = KeysOf<DataT>,
        DefaultT = DefaultAsyncDataValue,
    >(
        req: MaybeRef<ReqT>,
        opts?: UseFetchOptions<_ResT, DataT, PickKeys, DefaultT, ReqT, Method>,
    ) => {
        return useFetch(req, defu(opts, baseOptions) as typeof opts);
    };
}

And then I get to keep everything working as expected (including types), while preserving the ability to customize default options per request 🚀
export const globalRefToWatchOnEveryRequest = ref(1);

export const useCustomFetch = createCustomFetch({
   headers: { 'X-Auth-Token': 'some-token', 'my-header': 'default-value' },
   deep: false,
   watch: [globalRefToWatchOnEveryRequest]
})

<script lang="ts" setup>
const { data: foo } = useCustomFetch('/api/foo')

const { data: bar } = useCustomFetch('/api/bar', {
    headers: { 'my-header': 'override-default-value' }
})

globalRefToWatchOnEveryRequest.value = 2 // Refreshes all my useCustomFetch
</script>

Also, I think with such a factory function in nuxt core, it'd be easy to add/refactor related functions like:
const useLazyFetch = createCustomUseFetch({ lazy: true })
const useDeepFetch = createCustomUseFetch({ deep: true })
const useClientFetch = createCustomUseFetch({ server: false })
...

I find an easy way to have your own simple useFetch without relying on a type replicate of use fetch:
import { defu } from 'defu';

export const useApi: typeof useFetch = (req, opts) => useFetch(
  req,
  defu(opts, { $fetch: useNuxtApp().$api }) as typeof opts,
);

@cernymatej you'd be welcome to pick - checked with @pi0 to ensure he didn't have a WIP! ❤

Do we have any specific requests for the functionality? The thread here is getting quite long, so it might be a good idea to summarize what we want to achieve with this factory function before I start implementing it.

Until this is done, I want to share my approach to create a custom fetch. Personally I use it to talk to my (external) API, but another use case is to check if the response is 401 (unauthorized) and then redirect to login page:
plugins/api.ts
export default defineNuxtPlugin((nuxtApp) => {
  const config = useRuntimeConfig();

  const api = $fetch.create({
    baseURL: config.public.apiUrl,
  });

  return {
    provide: {
      api,
    },
  };
});

composables/use-fetch-api.ts
import type { UseFetchOptions } from 'nuxt/app';

export function useApi<T>(
  url: string | (() => string),
  options?: UseFetchOptions<T>,
) {
  return useFetch(url, {
    ...options,
    $fetch: useNuxtApp().$api as typeof $fetch,
  });
}

export const useApiLazy = <T>(
  url: string | (() => string),
  options?: UseFetchOptions<T>,
) => {
  return useLazyFetch(url, {
    ...options,
    $fetch: useNuxtApp().$api as typeof $fetch,
  });
};

Explanation: I create a custom $fetch that can be used with useNuxtApp().$api() as well as custom useFetch and useLazyFetch that can directly be used useApi() and useApiLazy().

@MickL This is helpful, thank you!
In your composables/use-fetch-api.ts, is passing in a $fetch option undocumented? I can't find anything in the useFetch docs about useFetch taking a $fetch option.

@command-tab Definitely would be good to document (exists since https://github.com/nuxt/nuxt/commit/9845467421687e5d2a588284388675fc86af63b2)! In the types but also as text.

I also need to thank @TheAlexLichter because without his video I wouldnt been able to make it

authors: Awais-019 MickL MuhammadM1998 TheAlexLichter TimGuendel adrienZ awais019 cernymatej command-tab danielroe enkot gnidustotalus jd-solanki localusercamp menthol pi0 shiny yassilah

repo: nuxt/nuxt


text:
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client

Environment

Operating System: Linux
Description:	Ubuntu 20.04.5 LTS
Release:	20.04
Node Version:     v16.18.0
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager:  npm@8.19.2
Builder:          vite
User Config:      css, ssr, app, postcss
Runtime Modules:  -
Build Modules:    -

Reproduction
Created an error.vue page like this
<template>

{{ error.message }}

      There was an error 😱

      <button @click="handleError">Clear error</button>

      <NuxtLink to="/404"> Trigger another error </NuxtLink>

      <NuxtLink to="/"> Navigate home </NuxtLink>

</template>

Describe the bug
When i curl this url :
$ curl http://192.168.0.117:3000/old-slug -v
...
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Access-Control-Allow-Origin: *
< location: /new-slug
< content-type: text/html
< server-timing: -;dur=0;desc="Generate"
< date: Wed, 30 Nov 2022 18:25:24 GMT
< connection: close
< content-length: 95
<
* Closing connection 0
<!DOCTYPE html><meta http-equiv="refresh" content="0; url=/new-slug">

everything works correctly except get this error on server:
[nitro] [dev] [unhandledRejection] Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at new NodeError (node:internal/errors:387:5)
    at ServerResponse.setHeader (node:_http_outgoing:644:11)
    at Object.errorhandler [as onError] (/nuxt3test/nuxt-app/.nuxt/dev/index.mjs:427:20)
    at Server.toNodeHandle (/nuxt3test/nuxt-app/node_modules/h3/dist/index.mjs:752:27)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 'ERR_HTTP_HEADERS_SENT'
}

Additional context
No response
Logs
No response

Would someone be able to provide a standalone reproduction? 🙏

@adriaanvanrossum Do you use i18n? I see lang prefix in your urls. We have similar problem in our project. And it looks similar to that issue: https://github.com/nuxt-modules/i18n/issues/1611. My reproduction for i18n is here: http://github.com/lukaszflorczak/nuxt-middleware-playground

@danielroe here you go: https://stackblitz.com/edit/github-vgyh5u?file=middleware/redirects.global.js

@lukaszflorczak, I don't think it's i18n because it happens without it (as well).

@adriaanvanrossum Great. This should be resolved with https://github.com/nuxt/nuxt/pull/18445.

That's very fast. Thank you!

Looks like this solved my problem as well.

@danielroe Hi~ Can you explain the possible reasons for this error message? Because I upgraded to v3.3.3 and still encountered this problem, thank you very much.

same error here
nuxt 3.6.5 + nitro 2.6.0
[nuxt] [request error] [unhandled] [500] Cannot set headers after they are sent to the client
at new NodeError (node:internal/errors:371:5)
at ServerResponse.setHeader (node:_http_outgoing:576:11)
at setResponseHeaders (./.output/server/chunks/nitro/node-server.mjs:1:128298)
at ./.output/server/chunks/handlers/renderer.mjs:1:4866
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Object.handler (./.output/server/chunks/nitro/node-server.mjs:1:134475)
at Server. (./.output/server/chunks/nitro/node-server.mjs:1:136797)

still same issue here, internal middleware that should return on fail gives me:
nuxt-app  |  ERROR  [nitro] [unhandledRejection] Cannot set headers after they are sent to the client
nuxt-app  |
nuxt-app  |   at ServerResponse.setHeader (node:_http_outgoing:703:11)
nuxt-app  |   at sendRedirect (node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:765:18)
nuxt-app  |   at ServerResponse.<anonymous> (server/middleware/handleFail.ts:12:1)

Thought I'd share, not awaiting promises caused this for me, check you've not missing any await

authors: Developer27149 OhB00 adriaanvanrossum artmarydotir danielroe lafllamme lukaszflorczak videmann


text:
NuxtLoadingIndicator not working anymore

Environment
Nuxt project info:                                                                                17:11:46

Operating System: Linux
Node Version:     v16.15.0
Nuxt Version:     3.1.1
Nitro Version:    2.1.0
Package Manager:  npm@8.5.5
Builder:          vite
User Config:      typescript, nitro, app, alias, css, vite, runtimeConfig
Runtime Modules:  -
Build Modules:    -

Reproduction
StackBlitz from the docs: https://nuxt.com/docs/api/components/nuxt-loading-indicator#nuxtloadingindicator
https://stackblitz.com/github/nuxt/nuxt/tree/main/examples/routing/pages?file=package.json&terminal=dev
Describe the bug
Loading indicator never appears
Additional context
After updating to Nuxt 3.1.1, the NuxtLoadingIndicator component stopped working.
Logs
No response

Setting the throttle property to 0 makes the loading indicator appear again. However, this is not how I interpret what throttle behavior should be. I would expect the throttle function only to kick in when the loading bar is already visible, not already on the first appearance. The behavior from 3.0.0 made more sense to me. Not sure if this is a bug or intendend behavior?

I think it's desired behaviour not to display the loading indicator when the transition is less than a given amount of time: https://github.com/nuxt/framework/pull/9832. (This was also how it worked in Nuxt 2.)

Exactly. That's the purpose of the throttle. If your page loads instantly, a flashing NuxtLoadingIndicator doesn't really make that much sense from a UI/UX perspective, compared to a quick, elegant page transition. I would expect a loading bar to appear if something is taking more than normal to load, so I won't think I missed clicking the button/link or that my web browser broke.
Nonetheless, as you mentioned, you can force it to appear always by setting the throttle to 0.
The default throttle value is stated in the docs, which is 200ms.
Maybe it comes as a surprise for people used to always expect it to appear from previous Nuxt versions and now updating it to the last version. At the same time, it will be a surprise for other people who no matter what throttle value they set, it never worked :)

Mmm. If the page takes more than the throttle time, it will show the loading bar. I'm confused. Have you checked an escenario where it takes > throttle time to load?

The issue is that the example linked to in the docs isn't actually designed to show the loading indicator in action and the transitions are instant. We do need to fix that.
The change in behaviour is in the nature of a bug fix, but apologies if it has affected you negatively.

The issue is that the example linked to in the docs isn't actually designed to show the loading indicator in action and the transitions are instant. We do need to fix that.
The change in behaviour is in the nature of a bug fix, but apologies if it has affected you negatively.

No worries, all I needed to know was if it's a bug or intended behavior. Updating the docs/example is also fine.

Oh sorry I didn't understand the issue. Yes, agree 100% with updating the docs with a full working example

Guys any updates on this? Why do I have to look inside the component code to understand and set it rather looking in the offical documentation lol?
declare const _default: import("vue").DefineComponent<{
    throttle: {
        type: NumberConstructor;
        default: number;
    };
    duration: {
        type: NumberConstructor;
        default: number;
    };
    height: {
        type: NumberConstructor;
        default: number;
    };
    color: {
        type: (BooleanConstructor | StringConstructor)[];
        default: string;
    };
    errorColor: {
        type: StringConstructor;
        default: string;
    };
    estimatedProgress: {
        type: () => (duration: number, elapsed: number) => number;
        required: false;
    };
}, () => import("vue").VNode<import("vue").RendererNode, import("vue").RendererElement, {
    [key: string]: any;
}>, unknown, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<import("vue").ExtractPropTypes<{
    throttle: {
        type: NumberConstructor;
        default: number;
    };
    duration: {
        type: NumberConstructor;
        default: number;
    };
    height: {
        type: NumberConstructor;
        default: number;
    };
    color: {
        type: (BooleanConstructor | StringConstructor)[];
        default: string;
    };
    errorColor: {
        type: StringConstructor;
        default: string;
    };
    estimatedProgress: {
        type: () => (duration: number, elapsed: number) => number;
        required: false;
    };
}>>, {
    color: string | boolean;
    height: number;
    duration: number;
    throttle: number;
    errorColor: string;
}, {}>;
export default _default;

authors: Arecsu danielroe lafllamme mcrapts


text:
fix(config): upgrade md4 -> md5 on node > 16

🔗 Linked issue
resolves https://github.com/nuxt/nuxt/issues/10844
https://github.com/nuxt/nuxt/discussions/19078
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
We have a tricky situation upcoming, with Node 16 due to be EOL on September 11th, 2023, but Nuxt 2 is not EOL until the end of the year.
Webpack 4 hard-codes md4 algorithm in several places in the code base meaning our options to resolve this for Nuxt 2 users are somewhat limited. In build/dev mode, this change monkey patches the crypto.createHash function if running on Node > 16 to upgrade md4 to md5. Would welcome other ideas too 🙏
Note: This should not be taken for an endorsement of continuing to run with Webpack 4, which is out of date and has a number of dependencies with issues. I expect that number to continue to grow, and we will not be able to resolve all of them. I would strongly urge migrating to Nuxt 3 if possible and the team will do our best to make this possible over the course of the year ❤
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Codecov Report
Base: 66.25% // Head: 66.18% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (55437ae) compared to base (fcc999d).
Patch coverage: 16.66% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##              2.x   #19108      +/-   ##
==========================================
- Coverage   66.25%   66.18%   -0.08%
==========================================
  Files          93       93
  Lines        4090     4096       +6
  Branches     1156     1158       +2
==========================================
+ Hits         2710     2711       +1
- Misses       1115     1119       +4
- Partials      265      266       +1

Flag
Coverage Δ

unittests
66.18% <16.66%> (-0.08%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/config/src/options.js
92.94% <16.66%> (-1.84%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter danielroe


text:
feat(vite): unpin vite from minor

🔗 Linked issue
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This unpins vite from minor versions as it is now safe to rely on vite.experimental.renderBuiltUrl across new 4.x minors.
cc: @patak-dev
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Leaving a reference to the discussion to gather feedback about stabilizing experimental.renderBuiltUrl in Vite 5:

https://github.com/vitejs/vite/discussions/13834

authors: danielroe patak-dev


text:
OTP Input

Description
Example: https://vuetifyjs.com/en/components/otp-input/#usage
Additional context
No response

I built this kind of component for my own project which uses Nuxt UI:

It has theses props:
otpLength: number; // choose the number of digits
autoFocus: boolean;
autoValidation: boolean; // trigger a method automatically when all fields are filled
hide: boolean; // hide digits (like a password)

And it handles:

autofocus to next input when typing
pasting the code directly

At that point, I'm wondering how hard would it be to transform it to a nuxt UI component, as I never built one by myself...

@benjamincanac are you interesting in merging this component if I make a PR?
Any special recommendations?
Thanks.

@ddahan Do you have the source code for this component? I would love to try it out in my own Nuxt project!

You may want to test with https://vue-input-otp.vercel.app/.

@ddahan is it possible to share this component.

@ddahan is it possible to share this component.

@emwadde @marcbejar @pierresigwalt @JoelHutchinson
Sorry I did not receive notifications for this one. Here is the code if it can still help:
<template>
  <UFormGroup>

 i)" :key="i" class="w-12">

          <UInput
            :ref="(el) => (uInputComponents[i] = el)"
            size="xl"
            maxlength="1"
            :type="hide ? 'password' : 'text'"
            :ui="{ base: 'text-center', size: { xl: 'text-lg' } }"
            :autofocus="i === 0 && autoFocus"
            v-model="otp[i]"
            @input="autoTab(i)"
            @focus="selectTextOnFocus(i)"
            @paste="handlePaste($event)"
            @keydown.delete="handleBackspace(i, $event)"
          />

  </UFormGroup>
</template>

authors: JoelHutchinson aloky castrogarciajs ddahan emwadde

repo: nuxt/ui


text:
Do you have a homepage carousel component?

Description
I didn't find any image carousel components

There is an open PR: https://github.com/nuxt/ui/pull/927

close


text:
Add UIcon import on UMeter

Description
It seems that in the UMeter component (unlike UMeterGroup), the UIcon component is not imported. This absence is causing several errors. Would it be possible to add it?

Indeed! Thanks for the report 😊

authors: benjamincanac vgenevois


text:
Uncaught (in promise) ReferenceError: ref is not defined - ui-edge

Note able to use the Tabs functionality.

Version
Nuxt project info:                                                                                8:51:02 PM

------------------------------
- Operating System: Windows_NT
- Node Version:     v18.16.1
- Nuxt Version:     3.6.5
- Nitro Version:    2.5.2
- Package Manager:  npm@9.8.0
- Builder:          vite
- User Config:      extends, devtools, vite, nitro, routeRules, site, webVitals, typescript, colorMode, app, modules, image, googleFonts, runtimeConfig, linkChecker
- Runtime Modules:  @nuxt/devtools@0.7.1, @nuxtjs/supabase@0.3.8, @nuxtjs/google-fonts@3.0.2, @nuxthq/ui@2.6.0-28174590.2cd6208, @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.1.1, @nuxtjs/web-vitals@0.2.6, @nuxtjs/fontaine@0.4.1, @nuxt/content@2.7.2, @storyblok/nuxt@5.5.2, nuxt-link-checker@1.0.5, @nuxt/image@1.0.0-rc.1
- Build Modules:    -
------------------------------

Steps to reproduce
<script setup>
const items = [
    {
        label: "Tab1",
        content: "This is the content shown for Tab1",
    },
    {
        label: "Tab2",
        disabled: true,
        content: "And, this is the content for Tab2",
    },
    {
        label: "Tab3",
        content: "Finally, this is the content for Tab3",
    },
];
</script>

<template>
    <UTabs :items="items" />
</template>

What is Expected?
page should load without error
What is actually happening?
404 error

Thanks for noticing! It should be fixed in latest edge.

authors: CareTiger benjamincanac

repo: nuxtlabs/ui


text:
Script for updating the namespace due to compartmentalization changes

python morpheus_namespace_update.py --directory <directory> --dfp
python morpheus_namespace_update.py --directory <directory> --llm

/ok to test

/ok to test

/ok to test

/ok to test

/merge

repo: nv-morpheus/Morpheus


text:
🛑 Kubeflow ML Platform is down

In 5eaf11b, 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 a0ddd58.

repo: nvgsg/lab-upptime


text:
🛑 NVIDIA AI Enterprise Hub is down

In b7d2b47, 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 017f9c8.


text:
🛑 Kubeflow ML Platform is down

In 005da15, 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 1d0b010.


text:
Convert unitest to pytest

Took a little longer than I expected. (However that just makes me appreciate the work that was done originally even more!)
One test that succeeded under unittest fails under pytest:
def test_get():
    pq = pqdict(sample_items)
    assert pq.get("A") == 5
    assert pq.get("A", None) == 5
    assert pq.get("does_not_exist", None) is None

    # INVESTIGATE: in unit test, this succeded
    with pytest.raises(KeyError):
         pq.get('does_not_exist')

Fixes #7

Interesting... pq.get is inherited from Mapping and maybe the behavior changed at some point. I would expect it to return None, just like it does now and just like dict does. I'm not sure why I expected it to raise KeyError before.

Thanks for reviewing.
The think things are resolved now. I made those changes with a regexp search and replace which explains why some are faulty.
(I make a lot of mistake which is why I work on debuggers. But testing is very important too!)

Yeah, I figured it was a regexp issue.
Thank you so much for doing this!

I work on debuggers.

Very cool! I should check out some of your projects.

authors: nvictus rocky

repo: nvictus/priority-queue-dictionary


text:
Question: How do source in the same group affect each other?

Hey,
I have a question which I can't find an answer for in the docs or already open issues. So basically the header already states it, but maybe that's a bit generic. So in more detail I'm interested to know how the different speed of sources that are in the same group or side-by-side group affect the auto-completion. So for example I have snippet and lsp in my default first level group and recently also path. Does the auto-completion wait until all sources have responded before it publishes the completion candidates or does it immediately push when the first source responds and then continuously updates the list when the slower sources respond as well? So is the grouping only about not cluttering the completion list too much and keep it more focused or does it also relate to performance.
And a bit more special. Assuming that auto changing the source is enabled and my first group is super slow, would it then jump to the second group if that can provide candidates faster or..?
Sorry for these stupid (?) questions. Reading through them myself is a bit awkward. I'm faced with a large and complex code-base that causes heavy load on the language server. So the lsp source as my primary go-to is quite slow and I barely good help of auto-completion there. Although I was first not so happy about the intersection of LSP and Treesitter, I now consider to integrate Treesitter as well as a faster completion source on a first stage until LSP responds (or if Treesitter basically can't find something [correct]). Thereby I was about to edit my completion list configuration again, but had all of these questions.

Currently, popup menu will show only after all sources in the same group have responded, and auto-changing only happens if all the sources respond but no there is no available items. This is probably not the best way related to performance though. If you have any feedback on this, please let me know:)

Hmm. It would be cool if a group could populate to the same menu (means I don't switch manually to the next group/menu) but are independently pushing asynchronously to the current completion list items.
How could that be useful: you could for example combine treesitter and LSP into the first group. For complex code-bases the LSP might be slow (I saw the quite long open issue with many discussions about that). But Treesitter should remain quite fast as it is only focused on the current file. So while LSP is still working in background, the completion items of Treesitter might be already enough to help. I they don't because I want to access for example a property of something I have imported, I need to wait for LSP. But for everything buffer "internal" it would be faster.
But if the group waits until Treesitter and LSP are ready, the Treesitter source is likely useless since LSP should be always smarter (I would hope so). And splitting them into two groups is also not so nice, because then Treesitter would often shadow LSP if I don't switch manually. But eventually I should give it a try, because hopefully the list of Treesitter is empty if I use something external what only LSP can tell me. And then I have auto-switch that works well, as the empty response of Treesitter probably arrives earlier than LSP its. But wait, could it be that the second group get only "asked" for candidates when the first is empty. So I would get an even worse time of response when Treesitter does not find something?

repo: nvim-lua/completion-nvim


text:
feat: Add dropdown layout strategy

Adds a dropdown strategy.
Adds results_title and preview_title options.
nnoremap <Leader>f <cmd>:lua require'telescope.builtin'.find_files({ sorting_strategy = "ascending", preview_cutoff = 200,border = false, layout_strategy = "dropdown", prompt = "",
width = 50,winblend = 3, results_title = "", borderchars = { '', '', '', '', '', '', '', ''} })<CR>

https://clips.twitch.tv/ExpensiveExquisitePigeonVoHiYo

Right now I can't hide the preview and it leaves a box on the top left.

Also its called dropdown but you need to set the sorting_strategy to get it to work right.
That may be part of the "theme" abstraction.

This is ready for me to review?
I may push some ideas for easier config, but I could always update these after I implement them, unless you wanted to.
I like the idea of "themes".

Closing in favor of #79

authors: rockerBOO tjdevries