text:
ImportError: Numba could not be imported.

Am trying to set uo and environment for machine learning with pycaret
from pycaret.classification import * exp1 = setup(diabetes, target = 'Class variable')
and i am getting an error below

ImportError                               Traceback (most recent call last)
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typeconv\typeconv.py in
3     # Numba, if it fails to import, provide some feedback
----> 4     from numba.core.typeconv import _typeconv
5 except ImportError as e:
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
ImportError                               Traceback (most recent call last)
 in
1 from pycaret.classification import *
----> 2 exp1 = setup(diabetes, target = 'Class variable')
~\AppData\Roaming\Python\Python37\site-packages\pycaret\classification.py in setup(data, target, train_size, sampling, sample_estimator, categorical_features, categorical_imputation, ordinal_features, high_cardinality_features, high_cardinality_method, numeric_features, numeric_imputation, date_features, ignore_features, normalize, normalize_method, transformation, transformation_method, handle_unknown_categorical, unknown_categorical_method, pca, pca_method, pca_components, ignore_low_variance, combine_rare_levels, rare_level_threshold, bin_numeric_features, remove_outliers, outliers_threshold, remove_multicollinearity, multicollinearity_threshold, create_clusters, cluster_iter, polynomial_features, polynomial_degree, trigonometry_features, polynomial_threshold, group_features, group_names, feature_selection, feature_selection_threshold, feature_interaction, feature_ratio, interaction_threshold, session_id, silent, profile)
878
879     #import library
--> 880     from pycaret import preprocess
881
882     data = preprocess.Preprocess_Path_One(train_data = data,
~\AppData\Roaming\Python\Python37\site-packages\pycaret\preprocess.py in
24 from sklearn.decomposition import IncrementalPCA
25 from sklearn.preprocessing import KBinsDiscretizer
---> 26 from pyod.models.knn import KNN
27 from pyod.models.iforest import IForest
28 from pyod.models.pca import PCA as PCA_od
~\AppData\Roaming\Python\Python37\site-packages\pyod_init_.py in
2
3 from . import models
----> 4 from . import utils
5 # TODO: add version information here
6
~\AppData\Roaming\Python\Python37\site-packages\pyod\utils_init_.py in
9 from .data import generate_data
10 from .data import evaluate_print
---> 11 from .stat_models import pairwise_distances_no_broadcast
12 from .stat_models import wpearsonr
13 from .stat_models import pearsonr_mat
~\AppData\Roaming\Python\Python37\site-packages\pyod\utils\stat_models.py in
9
10 import numpy as np
---> 11 from numba import njit
12 from scipy.stats import pearsonr
13 from sklearn.utils.validation import check_array
~\AppData\Roaming\Python\Python37\site-packages\numba_init_.py in
18
19 # Re-export typeof
---> 20 from numba.misc.special import (
21     typeof, prange, pndindex, gdb, gdb_breakpoint, gdb_init,
22     literally, literal_unroll
~\AppData\Roaming\Python\Python37\site-packages\numba\misc\special.py in
1 import numpy as np
2
----> 3 from numba.core.typing.typeof import typeof
4
5
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typing_init_.py in
----> 1 from .context import BaseContext, Context
2 from .templates import (signature, make_concrete_template, Signature,
3                         fold_arguments)
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typing\context.py in
9 import numba
10 from numba.core import types, errors
---> 11 from numba.core.typeconv import Conversion, rules
12 from numba.core.typing import templates
13 from .typeof import typeof, Purpose
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typeconv\rules.py in
1 import itertools
----> 2 from .typeconv import TypeManager, TypeCastingRules
3 from numba.core import types
4
5
~\AppData\Roaming\Python\Python37\site-packages\numba\core\typeconv\typeconv.py in
15            "possible please include the following in your error report:\n\n"
16            "sys.executable: %s\n")
---> 17     raise ImportError(msg % (url, reportme, str(e), sys.executable))
18
19 from numba.core.typeconv import castgraph, Conversion
ImportError: Numba could not be imported.

Kindly assist with a diagnosis and solution

This is likely a duplicate of #5600.  There is a workaround in the issue discussion that should help until we get a patch release out next week.

@mbtallbert thank you for raising this issue with the Numba issue tracker. @seibert I concur with that assessment, will label and close the issue. @mbtallbert in case this is a mistake, please feel free to re-open the issue with additional information, thanks!

authors: esc mbtallbert seibert


text:
Update llvmlite version dependency.

Move to llvmlite>=0.21

Codecov Report

Merging #2601 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2601   +/-   ##
=======================================
  Coverage   86.32%   86.32%
=======================================
  Files         320      320
  Lines       65657    65657
  Branches     7382     7382
=======================================
  Hits        56677    56677
  Misses       7798     7798
  Partials     1182     1182

source: gharchive/pull-request

authors: codecov-io stuartarchibald

repo: numba/numba

license_type: permissive

license_source: bigquery


text:
bump llvmlite dependency to 0.38.0dev0 for Numba 0.55.0dev0

As required by https://github.com/numba/numba/issues/7164
Note: do not merge until a first llvmlite 0.38.0dev0 becomes available, else CI will fail.

/azp run


text:
refactor: Delineate three kinds of Sequence items

This code is a step toward resolving #23 and does not add new functionality.
Rather, it makes explicit the fact that there are three kinds of Sequence items:
Sequence "Getter"s that have a button at the bottom of the sequence menu,
which when used produces a new button for the specific sequence created;
Sequence "Family"s that have a button in the top of the sequence menu, but
need parameters to create a specific sequence each time their button is
pressed; and Sequence "Instance"s that were created by a "Getter" and which
select that one specific sequence when their button is pressed.
Formerly, which one of these kinds a Sequence functioned as was an indirect
result of whether it had a SequenceExportModule and whether or not "isOeis"
was true in that module; also, the button for the only "Getter" in practice,
the OEIS Sequence Template, was hard-coded.
This PR creates an explicit enumeration of the three kinds, and requires that
every Sequence object has a SequenceExportModule to show up in the Menu, and
the kind must be explicitly set in that module.
The motivation for this refactoring (besides code clarity and the removal
of hard-coding for the OEIS template) is to allow for additional Getters
besides the OEIS template, whose buttons will be automatically displayed
alongside the OEIS one at the bottom of the Sequence menu. The idea is that
the Sequence type to come that allows mixed formulas and OEIS sequences
will be such a Getter.

This sounds very sensible to me.

authors: gwhitney katestange

repo: numberscope/frontscope

license: MIT

license_source: github-api


text:
Translation to Brazilian Portuguese

Translation to Brazilian Portuguese

Apps are being archived. Thanks for contributing!

authors: Foggalong afmachado

license: mit


text:
Bump golang.org/x/tools from 0.1.11 to 0.6.0

Bumps golang.org/x/tools from 0.1.11 to 0.6.0.
Release notes
Sourced from golang.org/x/tools's releases.
gopls/v0.6.0
Features
Default to -mod=readonly
In Go 1.16, the Go command will no longer modify user's go.mod and go.sum files automatically (https://tip.golang.org/doc/go1.16#tools). In order to match this behavior, gopls now also uses -mod=readonly when running the go command. Any errors reported by the go command will be presented with a suggested fix to make the necessary fixes to your go.mod or go.sum files. As a consequence, your workspace may be in a partially broken state while you have errors in your go.mod or go.sum file. golang/go#42266 will mitigate this, but it will likely not be resolved until February.
Not recommended: If you must opt out of this behavior, you can set the allowModfileModifications configuration to true.
Default to GOPROXY=off
gopls no longer accesses the network implicitly. This should improve latency in all cases, but it also means that gopls will no longer automatically download modules that are not found in your local module cache. The one exception is that gopls will still download dependencies on start-up, so it will continue to work as expected if you have cloned a repository for the first time. If gopls detects a missing module, it will offer you a suggested fix that downloads it.
Not recommended: If you must opt out of this behavior, you can set the allowImplicitNetworkaccess configuration to true.
Inclusion/exclusion filters for directories gopls now supports excluding certain directories in your workspace from analysis. This may be useful if you are only working on a subset of a large repository. Note that these filters are not propagated to the go command, so gopls will still load metadata for these directories, which may be expensive. Configure the included/excluded directories through the directoryFilters setting. Debouncing for diagnostics
Diagnostics are now reported instantly only for the packages currently being edited. Diagnostics for other packages in the workspace will now only be computed after 250 milliseconds, meaning that, if you are actively typing, gopls will not start these more costly operations. This should significantly reduce CPU utilization. This debounce delay can be optionally configured via the experimentalDiagnosticsDelay setting. "Upgrade direct dependencies" code lens
In gopls/v0.5.4, we removed the per-require "Upgrade dependency" code lens, as it was very high latency, and its UX did not meet user needs. Some users have expressed disappointment about this, so, to bridge the gap, we have separated the existing "Upgrade all dependencies" code lens into two: "Upgrade transitive dependencies" and "Upgrade direct dependencies". The first is the equivalent of running go get -u all, while the second go gets each of your module's requires independently. We are continuing to work on improving these features and will likely bring back the "Upgrade dependency" code lens as a suggested fix (learn more: golang/go#38339).
Support for filling a partially-populated struct The "Fill struct" suggested fix will now be suggested for structs that have some, but not all, fields set. Experimental
Field alignment analyzer
A new analyzer has been added to suggest reordering fields in a struct in order to achieve the optimal alignment in memory. It is still off by default, but can be enabled by adding the following to your gopls settings: "analyses": {
	"fieldalignment": true
}

Fixes
Improvements to diagnostics tracking
Diagnostic messages were not being updated correctly when the GC details code lens was toggled on. New handling to differentiate diagnostics by sources should have resolved this issue.

... (truncated)

Commits

d0863f0 go.mod: update golang.org/x dependencies
545ca87 gopls/internal/regtest/marker: require go/packages
1ace7db go,gopls: remove license from package doc comments
ebad375 gopls/internal/lsp/protocol: prevent license rendering in godoc
10a39ef gopls/internal/lsp/regtest: address additional comments on marker.go
69920f2 gopls/internal/regtest/marker: add missing tests for hover
24a13c6 gopls/internal/regtest: fill out features of the new marker tests
2b149ce gopls/internal/regtest: add a regtest-based version of the marker tests
edddc5f go/packages: don't discard errors loading export data
a762c82 go/ssa: add MultiConvert instruction
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Pull Request Test Coverage Report for Build 4221578303

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.198%

Totals

Change from base Build 4221546050:
0.0%

Covered Lines:
553

Relevant Lines:
627

💛  - Coveralls

authors: coveralls nunnatsa

repo: nunnatsa/ginkgolinter


text:
Build Error: Could not deduce (StateType (Handler b Sqlite) ~ Sqlite)

Hi there,
I am trying the new version 0.4.8.3 and I'm getting an error while I am building my project.
The error is located for the HasSqlite instance. I added the import "Control.Monad.State" as it is shown in the example project, but cabal throws the error
"Could not deduce (StateType (Handler b Sqlite) ~ Sqlite) from the context (MonadCatchIO-transformers-0.3.1.3:Control.Monad.CatchIO.MonadCatchIO
(Handler b App) bound by the instance declaration at libarary\Application.hs:22:5--24.
Expected type: Handler b Sqlite Sqlite
Actual type: Handler b Sqlite (StateType (Handler b Sqlite))
Relevant bindings include
 getSqliteState :: Handler b App Sqlite
  (bound at library\Application.hs:23:5)
In the second argument of `with', namely get'

My code is the following:
{-# LANGUAGE OverloadedStrings   #-}
{-# LANGUAGE ScopedTypeVariables #-}
{-# LANGUAGE TemplateHaskell   #-}
{-# LANGUAGE FlexibleInstances #-}

-- | Module, which defines and holds several sub snaplets.
module Application where

import           Control.Lens
import           Control.Monad.State
import           Snap
import           Snap.Snaplet
import           Snap.Snaplet.SqliteSimple

-- | Holds the snaplets.
data App = App { _playerDAO :: Snaplet Sqlite  }

-- | Creates the snaplet.
makeLenses ''App

-- | Provides a HasSqlite instance for this module.
instance HasSqlite (Handler b App) where
    getSqliteState = with playerDAO get

Cabal-version: 1.18.05 using 1.18.1.3 of Cabal library
GHC: 7.8.3

Thanks for the report.  Is this a regression from the new snaplet-sqlite-simple-0.4.8.3 version, ie. was it working before?
The snaplet-sqlite-simple example app was building fine on GHC 7.6.3 on Travis: https://travis-ci.org/nurpax/snaplet-sqlite-simple/builds/66760603.
Did you try building in a clean sandbox?  Have you recently updated with "cabal update"?
I suppose either the snaplet code doesn't (anymore) build on GHC 7.8 or later, or you have some different versions of some dependent libraries.  Do you see any notable library version differences if you compare your locally installed versions against the ones picked up in https://travis-ci.org/nurpax/snaplet-sqlite-simple/builds/66760603?
I note that snaplet-postgresql-simple defines the HasPostgres differently.  From their docs:

instance HasPostgres (Handler b App) where
getPostgresState = with db get
setLocalPostgresState s = local (set (db . snapletValue) s)

Are you able to reproduce this in an isolated gist?  Would be easier for me to take a look.

Hi,
It worked before I updated to 0.4.8.3 aside from some strange random server time outs. But that's a different topic :)
I used a clean sandbox and I updated cabel in order to get snaplet-sqlite-simple 0.4.8.3.
My dependencies are a bit different. So I am using the latest snap (0.14.0.5), but I have to use snap core 0.9.6.3 instead of 0.9.7.0 because of this issue: https://github.com/snapframework/snap-core/issues/228.
Also I am using the newer version 0.4.9.0 of sqlite-simple (instead of 0.4.8.0).
I tried to create a small gist of my problem:
https://gist.github.com/wochinge/f84dc4f8fa8672827443
Thanks for your help!

Hi @wochinge, I think the problem is in your use of monads-tf package for monad transformers.  If I switch that package to mtl, your gist builds fine.
diff --git a/test.cabal b/test.cabal
index 7dea39a..990ca63 100644
--- a/test.cabal
+++ b/test.cabal
@@ -25,7 +25,7 @@ library
     exposed-modules:        Application
     build-depends:
         base,
-        monads-tf,
+        mtl,
         snap == 0.14.0.5,
         blaze-builder,
         snap-core == 0.9.6.3,

I've never actually come across monads-tf whereas mtl seems to be pretty common.  The mtl package is one of the dependencies for snap so it seems like it's a pretty safe bet to use the same in apps too.
I have no idea why this build problem arose in the context of my snaplet-sqlite-simple update though. :)

Thank you very much! It works now! Then nothing stops me from upgrading :-)
I guess I added the dependeny a bit too fast when cabal complained ;)

source: gharchive/issue

authors: nurpax wochinge

repo: nurpax/snaplet-sqlite-simple


text:
streams methods

Hi what are the common stream methods that we should know?

good to know your different types of source, intermediate, terminating operations. Like your generate, iterate, pipeline operations like map, filter, flatMap etc

you might want to familiarize urself with toList(), boxed(), mapToObj(), mapToInt(), reduce(), limit(), count() too

Apart from the above, you can take note of terminating operations like forEach, anyMatch, allMatch, noneMatch, findFirst and findAny

Also, it will be good to note and understand the parameters for the different methods (e.g. generate takes in a Supplier, iterate (overloaded) takes in different parameters), a decent summary can be found in extra Lec8-notes

finals is over you can close this issue


text:
[T4A6][W13-B4] Conan Kian

Ready for review

@ckjr
Some comments added. Please ack & close the PR after reading comments.

Acknowledged.

authors: ckjr okkhoy


text:
[T4A5][T15-B4] Leow Zheng Yu

Ready for Review. Adapted from Eugene Peh Xian Bin code.

@zhengyu92 Use the imperative form of the verb for commit messages.


text:
[T4A7][T11-B2]Pankaj Bhootra

Ready for review

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


text:
[T3A2][F10-A3]SAN SOK SAN

Ready for review.

Good Job!

authors: chanjunweimy ericsssan


text:
[T2A4][F12-A2]Lee Jun Han Bryan

Ready for review.
Will look at sort feature again soon.

Thanks (:


text:
Update Linter usage in project

Linting targets weren't included in build processes making way for unlinted go and yaml files in the codebase.
This PR add the linters in place using golangci-lint and yamllint and fixes the linting errors highlighted.

/retest

/hold

/test e2e-capx-controller-upgrade

/hold cancel


text:
Tab design prototype

fixes https://github.com/nuvla/ui/issues/438

When we don't have a NB status. I think it's better to display as in HOST segment, status not available

Somewhere there is a  as a child of

@0xbase12 ⬆

repo: nuvla/ui


text:
Fix stateful regex

Can not use "g"  global flag here together with exec since the index is stored globally and follow-up rendering may fail to filter "amp-body" - via https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp/exec

Thanks

authors: falvhb farnabaz

repo: nuxt-community/amp-module


text:
BrowserslistError: Unknown browser query dead error

Version
v1.2.0
Reproduction link
https://github.com/nuxt-community/create-nuxt-app
Steps to reproduce
i tried to create a new project. but it shows an error in Bootstrap. i think we need to downgrade boostrap version. how to fix this for all, instead of me without having a pane.

I fixed the issue by downgrading the Bootstrap version into 4.0.0 or 4.1.0 (remove ^ before the version number and put 4.0.0 or 4.1.0)
What is expected ?
fix this for all.
What is actually happening?
version mismatch break!

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

maybe, U can edit 'nuxt.config.js' , 'bootstrap-vue/nuxt',  to  ['bootstrap-vue/nuxt', { css: false }],

authors: Chathula clotee

repo: nuxt-community/create-nuxt-app


text:
Translations from composition api setup method

Hi,
We're using the i18n-loader, meaning we specify the translations in the components itself, and that works perfectly fine when accessing them directly from the template, for example
<i18n>
{
  "en": {
    "title": "Hello World"
  }
}
</i18n>

<template>

{{ $t('title') }}

</template>

But when we're trying to access the messages, specified in the <i18n> block from within the setup method/context, the i18n.messages object/array is empty, is there any workaround or alternative way of doing this?
Here's a full example of what we're trying to do, but as stated above, this doesn't work.
<i18n>
{
  "en": {
    "title": "Hello World"
  }
}
</i18n>

<template>

{{ text }}

</template>

Thought it could be a timing issue at first, but i've tried accessing the messages property after the component is mounted, but that doesn't make any difference, it's still empty.

Composition API support is not implemented and since I haven't looked deeper into it, I'm not sure what it would take to implement it. The solution would potentially be based on https://github.com/intlify/vue-i18n-composable/blob/master/src/index.ts though.

authors: RobinBertilsson rchl


text:
Nuxt3 bug: require is not defined in ES module scope, you can use import instead

Version
On the dev branch of this repo, latest version of nuxt
Steps to reproduce

Clone the supabase-module and goes to the dev branch
yarn, yarn build and yarn link
Go on the repo using the module, you can use pushupers
yarn then yarn link @larbish/supabase
yarn dev
Constat the error: require is not defined in ES module scope, you can use import instead

What is Expected?
No error, website loading normally.
What is actually happening?
The require statement is coming from cross-fetch  , dependency of supabase/supabase-js, itself used by the module.
Nuxt does not transpile it.
I already tried:
nuxt.options.build.transpile.push()  and  nuxt.options.vite = { optimizeDeps: { include: [] } }  for both cross-fetch and supabase/supabase-js but without success.

Hi. The issue is likely caused because using the linked package which is outside of node_modules and not being transpiled for CommonJS require.  Also made a test publish on @pi0/supabase and works well for pushupers repo both dev and prod.
Will improve Nuxt to replace cross-fetch with native (https://github.com/nuxt/framework/issues/3421) but probably not an issue to solve here.

Thanks @pi0 for the feedback. Even when using a published version, I still have an error on runtime: Uncaught SyntaxError: The requested module '/_nuxt/node_modules/cross-fetch/dist/browser-ponyfill.js?v=d0e09cad' does not provide an export named 'default' .

After a new attempt, adding cross-fetch to the optimiseDeps of vite fixes the problem: https://github.com/larbish/supabase-module/commit/66d0aa1e515dff3b43ed9903c48a033197749f96#diff-030fc083b2cbf5cf008cfc0c49bb4f1b8d97ac07f93a291d068d81b4d1416f70R106

any progress?

@zzxxiinn Yes it is fixed. However, this module is no more on my personal account, it has just been moved to the nuxt-community organization. You can now install it with yarn add --dev @nuxtjs/supabase and no more with @larbish/supabase. Documentation is ready: https://supabase.nuxtjs.org/setup

@larbish Thank you for your reply!

authors: larbish pi0 zzxxiinn

repo: nuxt-community/supabase-module


text:
fix: color mode in server

When using ssr it cannot get colorMode from options
Closes #158.

@Atinux thank you!

repo: nuxt-modules/color-mode


text:
TS2345: Argument of type '"i18n:beforeLocaleSwitch"' is not assignable to parameter of type 'HookKeys '.

Hello im trying to create an i18n plugin using runtime hooks based on docs here https://v8.i18n.nuxtjs.org/guide/runtime-hooks but im getting TS Errors

the package.json versions :
"@nuxtjs/i18n": "npm:@nuxtjs/i18n-edge",
"nuxt": "3.4.1",

i have also tried this way :

im resolving it using // @ts-ignore but i should not , any ideas ?

Hey, I've run into the same issue. Did you find a fix?

https://github.com/vasilistotskas/grooveShop/tree/master/storefrontUINodeNuxt/src

Closing this as I'm unable to reproduce this issue using the latest version, reproduction demonstrate here.

authors: BobbieGoede NathanD19 vasilistotskas


text:
feat: Supporting Hot Reload

🆒 Your use case
Very interesting project @danielroe and the team. Thank you all.
I tried supporting hot reload to a nuxt/ionic project. Here's what I did:

Installing @ionic/cli as a dependency.
adding "ionic:serve": "nuxt dev" command in package.json.

That's it. It worked for me.
It's worth mentioning that when I tried to run the iOS Simulator, I saw this error message from Ionic VSCode Extension.

🆕 The solution you'd like
Supporting Hot Reload in a way that Ionic VSCode understands.
🔍 Alternatives you've considered
No response
ℹ Additional info
No response

If for some reason the Ionic VSC Plugin doesn't like your package.json, make sure you have a name and a version.
  "name": "app",
  "version": "0.10.0",

@Tragio Maybe worth adding to docs? Or printing a warning message when Nuxt starts if missing?

authors: Tragio adhamfarrag danielroe

repo: nuxt-modules/ionic


text:
user permissions plugin. Update request won't work

Version
@nuxtjs/strapi: ^1.9.3
nuxt: ^3.7.0
Steps to reproduce
Have a strapi server v4 on and you need to be using user::permissions plugin to handle your users.
https://docs.strapi.io/dev-docs/plugins/users-permissions
try to update your user
const { update } = useStrapi();
await update('users', userId, { email: 'user@fmail.com' });

fail miserably.
What is Expected?
You should be able to update your users.
What is actually happening?
The requisition returns 200, but nothing is being updated. 'Why?' you ask.
For some reason the user:permissions plugin doesn't expect the data to be wrapped in a data object. They are not going against strapi guidelines, their logic is that they're doing the work for you, so you don't need to send your data wrapped in a data object.
The whole problem lies with this function, it always wraps the data inside a data object. So the user:permissions gets it and wraps under an additional data object. The requisition succeeds, but there's no nested data property to be found and updated, so nothing changes.
 const update = <T>(contentType: string, id: string | number | Partial<T>, data?: Partial<T>): Promise<T> => {
    if (typeof id === 'object') {
      data = id
      // @ts-ignore
      id = undefined
    }

    const path = [contentType, id].filter(Boolean).join('/')

    return client(path, { method: 'PUT', body: { data } })
  }

What I ask in behalf of the user:permissions plugin and of all those who want to go against strapi best-practices by building their own custom endpoints is an option, an optional option, to not wrap the data inside a data object.
For now, here's the workaround
const client = useStrapiClient();
await client(`/users/${props.id}`, {
        method: 'PUT',
        body: { email: 'user@fmail.com' },
      });

Hey @doubleyooz The way to update the users collection is with the useStrapiClient composable like so
const client = useStrapiClient();

await client("users", {
  method: "PUT",
  body: { email: "user@fmail.com" }
});

I think this is the case because this module wraps all the update requests in an object like so:
data: {
// your data gets spread here when passed to the `update` function
}

You can check out the signature of the update function here: https://github.com/nuxt-modules/strapi/blob/dev/src/runtime/composables-v4/useStrapi4.ts#L66
& here: https://github.com/nuxt-modules/strapi/blob/dev/src/runtime/composables-v4/useStrapi.ts#L9

authors: BayBreezy doubleyooz

repo: nuxt-modules/strapi


text:
Nuxt Bridge Middleware Chain Not Breaking on navigateTo(),  abortNavigation()

Environment

Operating System: Darwin
Node Version:     v18.17.1
Nuxt Version:     2.17.2
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager:  npm@9.6.7
Builder:          webpack
User Config:      bridge, router, serverHandlers, devServerHandlers, devServer, typescript, nitro, buildModules
Runtime Modules:  -
Build Modules:    (), @nuxt/bridge@3.0.1-28452354.e299e14

Reproduction
Reproduction repo: https://github.com/atomiomi/nuxt-bridge-middlewares
The repo has README with steps to reproduce
Describe the bug
In Nuxt Bridge, when a middleware uses the navigateTo(),  abortNavigation() utility to redirect the user, the middleware chain does not break as expected. This behavior results in subsequent middlewares being called, potentially leading to errors. This issue is particularly problematic in scenarios where a root middleware checks for user authentication and attempts to block access to a page.
Additional context
No response
Logs
No response

Looking at the comments on this issue, etc., this behavior appears to be as expected.
https://github.com/nuxt/nuxt/issues/20696

Hey @wattanx  thank you for the quick response.
I think the issue that you've linked describes another bug, which is order in which middlewares are called.
The issue I'm describing is that child middleware shouldn't be called at all.
I setup redirects just for demonstration purposes in my repo.
I have / page that has root and nested middlewares
and /redirect which has only root. it doesn't have nestes middleware.
so in my case it should just call global (by / page), global (by redirect page)

I finally understood.
I misunderstood the issue 🙈

i have the same problem in nuxt bridge 3.3.1

authors: atomiomi guska8 wattanx

repo: nuxt/bridge


text:
502 - Bad Gateway

Hi,
Just made a new project with create-nuxt-app, added vercel.json (also tried now.json) and deployed.
Getting 502 - Bad Gateway.
Logs seem OK, no errors.
Last message is 11:59:30.799  Done with "nuxt.config.js"
repo: https://github.com/varna/agrobase-web
Unless I don't know something, there shouldn't be any custom servers or middlewares there, any ideas?

@varna I suspect it's your Vuetify colours, which are referenced in your nuxt config but are not in your production dependencies.
Are you sure there is nothing in the Vercel logs?

Logs when I posted issue:
11:58:24.557  Retrieving list of deployment files...
11:58:24.722  Downloading 32 deployment files...
11:58:27.121  Installing build runtime...
11:58:29.374  Build runtime installed: 2253.654ms
11:58:29.770  Looking up build cache...
11:58:29.852  Build cache found. Downloading...
11:58:32.267  Build cache downloaded [86.30 MB]: 2413.927ms
11:58:32.669   ----------------- Prepare build -----------------
11:58:32.669  Downloading files...
11:58:32.910  Working directory: /vercel/381058fe
11:58:32.912  Using yarn
11:58:32.913  ℹ Prepare build took: 243.86168 ms
11:58:32.913   ----------------- Install devDependencies -----------------
11:58:32.914  Running yarn install --prefer-offline --frozen-lockfile --non-interactive --production=false --modules-folder=/vercel/381058fe/node_modules --cache-folder=/vercel/381058fe/.now_cache/yarn
11:58:33.174  yarn install v1.22.0
11:58:33.255  [1/5] Resolving packages...
11:58:33.774  success Already up-to-date.
11:58:33.776  Done in 0.61s.
11:58:33.789  ℹ Install devDependencies took: 875.305421 ms
11:58:33.789   ----------------- Nuxt build -----------------
11:58:33.819  Running nuxt build --standalone --no-lock --config-file "nuxt.config.js"
11:58:34.730  ℹ Production build
11:58:34.771  ✔ Builder initialized
11:58:34.798  ✔ Nuxt files generated
11:58:35.967  ℹ Compiling Client
11:58:49.678  ✔ Client: Compiled successfully in 13.71s
11:58:49.683  ℹ Compiling Server
11:58:57.798  ✔ Server: Compiled successfully in 8.11s
11:58:57.800  Hash: ad8b8fe2554d4e8672e7
11:58:57.800  Version: webpack 4.43.0
11:58:57.800  Time: 13714ms
11:58:57.800  Built at: 05/26/2020 8:58:49 AM
11:58:57.800                           Asset       Size  Chunks                                Chunk Names
11:58:57.800  ../server/client.manifest.json   13.8 KiB          [emitted]
11:58:57.800         289a5b0e3622c5f408dd.js   2.35 KiB       3  [emitted] [immutable]         runtime
11:58:57.800         845e0cdbb8ab4490164f.js    4.3 KiB       4  [emitted] [immutable]
11:58:57.800                        LICENSES  318 bytes          [emitted]
11:58:57.800         b3e369394da7520f3475.js  817 bytes       2  [emitted] [immutable]         pages/inspire
11:58:57.800         d532bf7c20ac7a7778b0.js   19.4 KiB       1  [emitted] [immutable]         pages/index
11:58:57.800         f1a0820c5b565bc8dad4.js    631 KiB       0  [emitted] [immutable]  [big]  app
11:58:57.800       icons/icon_120.5f6a36.png   4.68 KiB          [emitted]
11:58:57.800       icons/icon_144.5f6a36.png    5.8 KiB          [emitted]
11:58:57.800       icons/icon_152.5f6a36.png    6.1 KiB          [emitted]
11:58:57.800       icons/icon_192.5f6a36.png   7.83 KiB          [emitted]
11:58:57.800       icons/icon_384.5f6a36.png   18.1 KiB          [emitted]
11:58:57.800       icons/icon_512.5f6a36.png     20 KiB          [emitted]
11:58:57.800        icons/icon_64.5f6a36.png   2.35 KiB          [emitted]
11:58:57.800          manifest.56bd406b.json  685 bytes          [emitted]
11:58:57.801   + 2 hidden assets
11:58:57.801  Entrypoint app = 289a5b0e3622c5f408dd.js f1a0820c5b565bc8dad4.js
11:58:57.801  WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
11:58:57.801  This can impact web performance.
11:58:57.801  Assets:
11:58:57.801    f1a0820c5b565bc8dad4.js (631 KiB)
11:58:57.801  Hash: 1800c3e64ffc8bf9472c
11:58:57.801  Version: webpack 4.43.0
11:58:57.801  Time: 8116ms
11:58:57.801  Built at: 05/26/2020 8:58:57 AM
11:58:57.801                    Asset       Size  Chunks                         Chunk Names
11:58:57.801  5a6a38a189814d7e9dc7.js  793 bytes       2  [emitted] [immutable]  pages/inspire
11:58:57.801  81f0127d22d942c59416.js     18 KiB       1  [emitted] [immutable]  pages/index
11:58:57.801                server.js    563 KiB       0  [emitted]              app
11:58:57.801     server.manifest.json  239 bytes          [emitted]
11:58:57.801   + 1 hidden asset
11:58:57.801  Entrypoint app = server.js server.js.map
11:58:57.885  ℹ Nuxt build took: 24095.034342 ms
11:58:57.885   ----------------- Install dependencies -----------------
11:58:57.886  Running yarn install --prefer-offline --pure-lockfile --non-interactive --production=true --modules-folder=/vercel/381058fe/node_modules --cache-folder=/vercel/381058fe/.now_cache/yarn
11:58:58.145  yarn install v1.22.0
11:58:58.221  [1/5] Resolving packages...
11:58:58.790  [2/5] Fetching packages...
11:58:58.859  [3/5] Linking dependencies...
11:58:59.198  [4/5] Building fresh packages...
11:58:59.200  [5/5] Cleaning modules...
11:58:59.431  Done in 1.29s.
11:58:59.448  ℹ Install dependencies took: 1562.722394 ms
11:58:59.448   ----------------- Collect artifacts -----------------
11:59:01.254  ℹ Collect artifacts took: 1803.365614 ms
11:59:01.941  Uploading build outputs...
11:59:05.928  Build completed. Populating build cache...
11:59:09.030   ----------------- Collect cache -----------------
11:59:11.350  ℹ 30379 files collected from .now_cache
11:59:12.996  ℹ 25540 files collected from node_modules_dev
11:59:13.150  ℹ 2415 files collected from node_modules_prod
11:59:13.151  ℹ Collect cache took: 4120.966129 ms
11:59:29.512  Uploading build cache [86.30 MB]...
11:59:30.782  Build cache uploaded: 1270.286ms
11:59:30.799  Done with "nuxt.config.js"

Thanks for response @danielroe,
Sorry for being silly and forgetting to check that all required dependencies are not in devDependencies! It fixed my problem, thanks!

authors: danielroe varna

repo: nuxt/now-builder


text:
Nuxt not building on Windows machine

I have just installed adonuxt (which basically is Adonis.js + nuxt).
Unfortunately, nuxt is not building on Windows machine.
When I run npm run build (which stands for node ./ace nuxtbuild (which stands for webpack, I guess)), all I get is a bunch of errors in my terminal.
IMO, these errors are related with Windows backslash.
All the errors state the same thing.
ERROR in ./.nuxt/App.vue
Module not found: Error: Can't resolve 'C:UsersGustavsDocumentsWWWproject_name
ode_modulesue-loaderlibcomponent-normalizer' in 'C:\Users\Gustavs\Documents\WWW\project_name\.nuxt'
 @ ./.nuxt/App.vue 4:16-123
 @ ./.nuxt/index.js
 @ ./.nuxt/server.js

As you can see, path is resolved incorrectly and backslashes are ignored. Also the letter n in node_modules path is ignored because of that backslash.

> node -v && npm -v
v7.4.0
4.0.5

Can you confirm me that you have the same error with the starter template?

@Atinux Yes, the same happens with starter template.
You can see full console output here.

same issue here, on win10. even with the vue-cli starter template.
clean new project, following exact instructions from intallation guide.

'ERROR in ./.nuxt/components/nuxt.vue
Module not found: Error: Can't resolve 'C:wamp64www
uxt     est
ode_modules♂ue-loaderlibcomponent-normalizer' in 'C:\wamp64\www\nuxt\test\.nuxt\components'
 @ ./.nuxt/components/nuxt.vue 1:16-99
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi webpack-hot-middleware/client?reload=true ./.nuxt/client.js

...
[C:\wamp64\www\nuxt\test\node_modules\C:wamp64www
uxt     est
ode_modules♂ue-loaderlibcomponent-normalizer]
 @ ./components/Footer.vue 1:16-99
 @ ./~/babel-loader/lib?{"plugins":["transform-async-to-generator","transform-runtime"],"presets":[["es2015",{"modules":false}],"stage-2"],"cacheDirectory":true}!./~/vue-loader/lib/selector.js?type=script&index=0!./layouts/default.vue
 @ ./layouts/default.vue
 @ ./~/babel-loader/lib?{"plugins":["transform-async-to-generator","transform-runtime"],"presets":[["es2015",{"modules":false}],"stage-2"],"cacheDirectory":true}!./~/vue-loader/lib/selector.js?type=script&index=0!./.nuxt/App.vue
 @ ./.nuxt/App.vue
 @ ./.nuxt/index.js
 @ ./.nuxt/server.js

definetly looks like a windows backslash thing
> node -v && npm -v
v6.9.4
4.1.2

Do you mind trying with npm 3?
It works on my computer with npm 3

@Atinux It builds successfully with npm 3, but IMO this package should support the latest version of npm anyway.

It should and it will.
It was to isolate the error first to better fix it.
On Sat, 28 Jan 2017 at 21:46, Gustavs Rācenājs notifications@github.com
wrote:

@Atinux https://github.com/Atinux It builds successfully with npm 3,
but IMO this package should support the latest version of npm anyway.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/170#issuecomment-275873565, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA3OFMc12OfGDsoBPiVWH2EiKHqAjXWxks5rW6k_gaJpZM4LwM_p
.

I'm sorry I can't be of any further help, digging into it.
I'm not really a node expert (not even a webpack or babel one, to be honest). Tried for a while to stack trace the thing, and make some fixes myself, but I really don't have a clue. Judging by the console output (malformed paths), my best guess would be that there must be  some ridiculously small thing (it always is), like a bad  regexp, while composing paths. somewhere. probably babel. I'm afraid I lack the expertise to trace it properly :(

@samkitano @GustavsR do you ming uploading the .nuxt folder generated when you launched npm run dev?

@Atinux There you go - https://drive.google.com/file/d/0B2et1wX5sB_XWVhWVzdzZ05tTzQ/view?usp=sharing

I mean, there is the .nuxt directory for npm run dev - https://drive.google.com/file/d/0B2et1wX5sB_XVlZTUWNmNUhxNWc/view?usp=sharing
The previous was from npm run build.

test.zip
There you are

Just did a test on my Win 10 computer, and it all seems okay.
These are the commands I ran in Powershell (also tried Cmd.exe with same result).
node -v
v7.4

npm -v
v4.0.5

vue init nuxt/starter nuxt-test
cd nuxt-test
npm install
npm run dev
 *** works just fine ***
npm run build
*** worked as well ***

Well, that's awkward...
I've just upgraded Node.js to v7.4.0 to try and replicate @SkaterDad env, and now it's working fine!

Yes, now it is working fine, and I haven't changed my node or npm versions.
I think it is related with the latest commits.

Thanks, @Atinux, @GustavsR, and @SkaterDad.

authors: Atinux GustavsR SkaterDad samkitano


text:
nuxt-start only works when nuxt installed

Installing only nuxt-start and starting yarn nuxt-start returns "server error" page with no messages in console.
Adding nuxt, but running yarn nuxt-start (not nuxt  start) produces normal operation.

 #1813

(((private board)))

(((private board)))

Not anymore @qm3ster :)


text:
asyncData doesn't work when load from static

For some reason this doesn't work
asyncData ({ params }) {
    return axios.get('data.json')
      .then((res) => {
        return { title: res.data.title }
      })
  }

How to load data from static folder?
I have JSON files there, where I want to manage content.

You'll have to either provide the full url:
axios.get('http://localhost:3000/data.json')

Or load it in the mounted hook:
mounted () {
  axios.get('/data.json')
    .then(({ data }) => {
      return { title: data.title }
    })
}

@cretueusebiu if I load it in mounted then it doesn't server render content! Is there any way to solve it? I want both - ssr and ability to modify content in builded app.

Use the full URL as in the first example.

@cretueusebiu and conditionally replace url when build? I mean there will be one url in Dev and another in Prod, right?

Of course, you would use an env variable for the url. And maybe extract the code to a file where you have the api calls.

If I use
asyncData ({ params }) {
    return axios.get('http://localhost:3000/data.json')
      .then((res) => {
        console.log(res)
        return { data: res.data }
      })
  }

Then I can't do npm run generate because Error: connect ECONNREFUSED 127.0.0.1:3000

It shouldn't be separate server. I wan't this JSON file inside Nuxt app.

If you don't want to load it just import it as you do with js files:
import data from 'path/to/data'

I tried that first. Then I can't edit file content. If I edit JSON file it doesn't have any effect to app.

And this is strange behavior. Because Nuxt is copying JSON file into dist for some reason. Why it's doing that, if it doesn't consume it?

I guess it's because JSON file is from static folder. But then this is not a solution for me, because requiring the JSON is merging it's data with app. I want it to be separate

I guess you either figured this out by now, or did something else; but I would try putting the file you want in your assets folder, rather than static, and import from there via webpack. I believe the contents of assets are tracked for changes...

I tried that first. Then I can't edit file content. If I edit JSON file it doesn't have any effect to app.

You can add custom watch paths to your nuxt config:
build: {
  watch: ['path/to/data']
}

A change to these files will trigger a rebuild and restart the server.
Note that Nuxt path prefixes (@, ~, etc.) in watch paths won't work: https://github.com/nuxt/nuxt.js/issues/2983

Same problem here. But no need for editing json files.
Just the requirement to load json files during nuxt generate with asyncData.
return axios.get('http://localhost:3000/data.json') does not work, as we know,
but what else could I use...?

I had this working by simply using require to require the JSON file. Webpack takes care of it. If you need route params to know what file to require, you can do it inside the asyncData callback.

I make simple workaround for this issue.
After run npm run generate, i start simple server on folder /static, and write new path to $axios settings
on nuxtconfig.js
    ['@nuxtjs/axios', {       baseURL: 'http://localhost:8000'     }]
on nuxt run generate script call to localhost:8000 and successfully get data from /static folder
P.S.: May be important at what address you run the temporary server.
When i run php -S localhost:8000 - the script gave the same error as before.
But when i run php -S 127.0.0.1:8000 script run successfully.

authors: Jones-S cretueusebiu iamdubx lunelson mootari wett1988


text:
Travis gives fatal error when running "npm run generate" task

Version
v2.0.0
Steps to reproduce
> nuxt generate
[02:18:45] [FATAL] Nuxt Build Error
7
   ╭────────────────────────╮
   │                        │
   │   ✖ Nuxt Fatal Error   │
   │                        │
   │   Nuxt Build Error     │
   │                        │
   ╰────────────────────────╯

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

Please get more into detail and try to provide a reproduction.

authors: ahmetzeybek manniL


text:
How add ScrollMagic in nuxt project?

I followed this article: https://nuxtjs.org/guide/plugins
I've added ScrollMagic.js in nuxt.config.js
module.exports = {
 plugins: [
    { src: '~plugins/ScrollMagic', mode: 'client' }
  ],
}

Then I've added this snippet in my component:
import Vue from 'vue'
import ScrollMagic from 'scrollmagic'

Vue.use(ScrollMagic)

I got this issue: ReferenceError window is not defined
Even if cover it like this:
if (process.client) {
  Vue.use(ScrollMagic)
}

I still have this issue...
Thanks in advance for your help

This question is available on Nuxt community (#c9762)

I am still having the same issue. Anyone can please provide a solution?

You need to use it in mounted ()

According to what I understand those kind of library (like Three.js, Awesome Swiper and such...) need access to the window object so when compiling for prerender (whether or not wrapped in a "isClient" statement) webpack still load the library and things go wrong. So in order to still use ScrollMagic you need to import the library  on the client side, here's an example:
<template>

My ScrollMagic component

</template>

By the way I've always been storing controller inside the $options object because I don't want it to be reactive, though I don't know if that's a best practice or not or if this can have any impact on performances, but anyway this work like that if anyone knows a better way to handle this I'd be glad to know about it :)

You can use it with a CDN or you can copy CDN file and import it localy, eitherway you have access to ScrollMagic in you mounted hook.

You can use it with a CDN or you can copy CDN file and import it localy, eitherway you have access to ScrollMagic in you mounted hook.

authors: lihbr sa8ab saadkhaan tommylinks williamsbs


text:
fix - store no available in context on client side

Store no available in context on client side.

Sorry for dirty pull request )

Codecov Report

Merging #442 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #442   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          11     11
  Lines         445    445
=====================================
  Hits          445    445

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 c4962f0...4353375. Read the comment docs.

@Atinux Please check it.

Thank you @evseevnn
I will push to a new version very soon.

authors: Atinux codecov-io evseevnn


text:
UseState not working in plugin and useFetch

Environment
Nuxi 3.2.3                                                                                16:50:41
Nuxt 3.2.3 with Nitro 2.2.3
Stackblitz
Reproduction
https://stackblitz.com/edit/nuxt-starter-czyl17?file=pages/index/index.vue
just execute code and check content displayed
We try to use useState to put value a init file (in plugins folder) and reuse it later in a menu, we are calling useFetch and in the response (200) we want to set value, but nothing more happen, no error message, no data put, and moreover we don't go further in the code. we exit the useFetch then we go on the end of file
PS: outside the useFetch it was working
Describe the bug
We should see
Home page
this is a test TEST
this is a test test value2
but we see only
Home page
this is a test test value2
in log we should see :
useState will be set
useState was set
end of init

but we see only
useState will be set
end of init

Additional context
No response
Logs
✔ Nitro built in 1013 ms                                                                        nitro 09:52:12
ℹ Vite client warmed up in 5048ms                                                                     09:52:12
✔ Vite server hmr 24 files in 1746.06ms                                                               09:52:15
useState will be set                                                                                09:52:15
end of init                                                                                09:52:15
useState will be set                                                                                09:52:15
end of init

So following previous issue :
let username: String;
	let role: String;
	let isConnected: boolean = false;

	//useState('username', ()=>'test');
	if (token !== null && token?.length > 0) {
		await useFetch(REST_API_URL + '/auth/validate', {
			method: 'POST',
			headers: {
				'Authorization': 'Bearer ' + token,
				'Content-Type': 'Application/json'
			},
			onResponse({request, response, options}) {
				// Process the response data
				if (response.status === 200) {
					const payload = parseJwt(token)
					username = payload.username
					role = payload.role
					isConnected = true
				}
			},
			onResponseError({request, response, options}) {
				console.log('token is not valid or expired');
				if (response.status === 400) {
					console.error('token expired or invalid');
				} else {
					console.error('internal issue problem');
				}
				router.push("/")
			},
		});

		if (isConnected) {
			useState('isConnected', () => isConnected);
			useState('username', () => username);
			useState('role', () => role);
		}

	} else {
		console.log('No token registered')

	}

do the trick, but is it the best solution to do ... i don't know

useState should not be called in a response handler: see https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables. (And also, you should not use useFetch in this case, but $fetch.)
  export default defineNuxtPlugin(async () => {
+   const test = useState('test');
-   await useFetch('https://httpbin.org/get', {
+   await $fetch('https://httpbin.org/get', {
      onResponse({ request, response, options }) {
        // Process the response data
        if (response.status === 200) {
          console.log('useState will be set');
-         useState('test', () => 'test value');
+         test.value = 'test value'
          console.log('useState was set');
        }
      },
      onResponseError({ request, response, options }) {
        //We don't care
      },
    });
    console.log('end of init');
  });

useState should not be called in a response handler: see https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables. (And also, you should not use useFetch in this case, but $fetch.)
  export default defineNuxtPlugin(async () => {
+   const test = useState('test');
-   await useFetch('https://httpbin.org/get', {
+   await $fetch('https://httpbin.org/get', {
      onResponse({ request, response, options }) {
        // Process the response data
        if (response.status === 200) {
          console.log('useState will be set');
-         useState('test', () => 'test value');
+         test.value = 'test value'
          console.log('useState was set');
        }
      },
      onResponseError({ request, response, options }) {
        //We don't care
      },
    });
    console.log('end of init');
  });

hi, thanks
what is the difference using $fetch and useFetch i am always lost...

useFetch is a Vue composable that handles moving data from server -> client, reactively updating data when the inputs change, etc. And crucially it should only be called in a Vue setup function. Whereas $fetch is the underlying fetch call that powers useFetch and can be used standalone when you simply need to programmatically fetch from an endpoint.

Really clear
Envoyé depuis mon appareil Galaxy
-------- Message d'origine --------
De : Daniel Roe @.>
Date : 02/03/2023 14:26 (GMT+04:00)
À : nuxt/nuxt @.>
Cc : leccyril @.>, Author @.>
Objet : Re: [nuxt/nuxt] UseState not working in plugin and useFetch (Issue #19382)
useFetch is a Vue composable that handles moving data from server -> client, reactively updating data when the inputs change, etc. And crucially it should only be called in a Vue setup function. Whereas $fetch is the underlying fetch call that powers useFetch and can be used standalone when you simply need to programmatically fetch from an endpoint.
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnuxt%2Fnuxt%2Fissues%2F19382%23issuecomment-1451638510&data=05|01||e0996042b66241b89d1708db1b088f55|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638133495794529061|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ej2J8pQcGXdH50UkU%2BaFsHaMZij%2FWy8CrZlQP5sPzmQ%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAYVWJUA5GTKXKP5ZVIDRQDW2BYUTANCNFSM6AAAAAAVM54CMI&data=05|01||e0996042b66241b89d1708db1b088f55|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638133495794529061|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=N2Si1XgqDsVe%2Fi2nCq6DcQowZOUnnCTrgZNqlMPnJZA%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

authors: danielroe leccyril

repo: nuxt/nuxt


text:
Page does not load - blank screen

Environment

Operating System: Darwin
Node Version:     v16.15.0
Nuxt Version:     3.4.3
Nitro Version:    2.4.0
Package Manager:  pnpm@8.4.0
Builder:          vite
User Config:      css, app, runtimeConfig, modules, sitemap
Runtime Modules:  @nuxt/image-edge@1.0.0-27919678.2f5b64b, nuxt-simple-sitemap@1.0.11, @nuxtjs/robots@3.0.0

Reproduction
Just build the project
Describe the bug
When we run in Dev mode nothing happens and our application works nice, but when we build the application and deploy it, the first page load doesn't work on Safari and Firefox. After reload the page, the application runs like a charm. We aren't able to simulate the behaviour on develop mode. The print screens below is the only way to see the issue.

Additional context
What we figured out in our investigation is something related to vue-router processing during build phase.
Logs
No response

Would you provide a reproduction? 🙏

Hi @danielroe as I mentioned before it is hard to reproduce because it only happens after the build process (performing 'pnpm build`). Our client already asked us about when we will fix it and, which is pretty hard for us to debug.

I'm happy to take a reproduction that only reproduces in certain situations (like after build) as long as there are steps I can follow to reproduce the problem.

authors: danielroe keuller


text:
Nuxt 3 Webpack Invalid Token In Dev Mode

Environment

Operating System: Darwin
Node Version:     v18.18.2
Nuxt Version:     3.12.2
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager:  npm@9.9.1
Builder:          webpack
User Config:      devtools, builder
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/~/github.com/Huseyin-Yilmaz-98/nuxt3-webpack-demo
https://github.com/Huseyin-Yilmaz-98/nuxt3-webpack-demo
Describe the bug
Because of the bundle file name problems with Vite, I have decided to give Webpack a try. However, it throws errors like invalid or unexpected token from multiple files (app.js or vendors.js or another random file) in dev mode. So I started another project with nuxi init and saw that the console error occurs even with the starter project. In the demo repo, I haev set webpack-dev-middleware version to 7.0.0 because of this issue. But it did not help either.

Additional context
No response
Logs
No response

Sorry, duplicate of https://github.com/unjs/nitro/issues/2541


text:
Will Nuxt release an app router similar to Next in the future?

Now the page and the components it needs to use are separated into multiple directories, as well as APIs. This is difficult to manage
If the Vue component is written into pages, it will be treated as a page router.

If the Vue component is written into pages, it will be treated as a page router.  already like that please check i guest. this https://nuxt.com/docs/guide/directory-structure/pages  will help you

It's possible to use layers to separate bits of your app into self contained Nuxt projects (with components/pages directories of their own).
Or you can use an ignore prefix to ignore directories within pages/
See https://www.youtube.com/watch?v=fr5yo3aVkfA and https://deltener.com/blog/nuxt-enterprise-patterns-component-management/

It's possible to use layers to separate bits of your app into self contained Nuxt projects (with components/pages directories of their own).
Or you can use an ignore prefix to ignore directories within pages/
See https://www.youtube.com/watch?v=fr5yo3aVkfA and https://deltener.com/blog/nuxt-enterprise-patterns-component-management/
Beyond that, there doesn't currently seem a need for more, but please let me know if you have a need Nuxt isn't meeting for you 🙏

I want to write the components that only need to be used once near page. vue for easy code organization. It seems that layer cannot meet this requirement, right? Is layer used as a template to inherit the project?

If the Vue component is written into pages, it will be treated as a page router. 已经这样了，请查看文档 https://nuxt.com/docs/guide/directory-structure/pages 将帮助你

Are you referring to layers? Is that convenient for organizing multiple projects? But it is not convenient to organize the components used for individual pages.

It's possible to use layers to separate bits of your app into self contained Nuxt projects (with components/pages directories of their own).
Or you can use an ignore prefix to ignore directories within pages/
See https://www.youtube.com/watch?v=fr5yo3aVkfA and https://deltener.com/blog/nuxt-enterprise-patterns-component-management/
Beyond that, there doesn't currently seem a need for more, but please let me know if you have a need Nuxt isn't meeting for you 🙏

I can automatically import components, but I cannot delete this page.

Please read the second link I provided. I think it is exactly what you are asking for.

Please read the second link I provided. I think it is exactly what you are asking for.

See, will this increase the loss of operational performance? It would be even better if nuxt could provide a built-in feature.

authors: bbhxwl danielroe silvesterwali


text:
Issue with external scripts when in dev mode

Environment

Operating System: Darwin
Node Version:     v22.7.0
Nuxt Version:     3.13.2
CLI Version:      3.13.2
Nitro Version:    2.9.7
Package Manager:  npm@10.8.2
Builder:          vite
User Config:      modules, css, compatibilityDate
Runtime Modules:  @nuxtjs/tailwindcss@6.12.1, @nuxt/image@1.8.0, @nuxt/content@2.13.2
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-1bvrus?file=app.vue
Describe the bug
Hello!
I'm trying to add a CRM form that is being provided via external scripts. When running in dev mode, the following error appears in the console:
TypeError: Cannot read properties of undefined (reading 'extend')
and the form won't render.
Here’s a minimal reproduction link.
The issue doesn’t occur when I write the same code using pure Vue or in a Vue SSR sandbox. Here’s the expected result using pure Vue SSR.
It also doesn’t appear after I run npx nuxi generate.
My guess is that it’s somehow connected to the Nuxt dev server, but unfortunately, I don’t have enough expertise yet to understand how everything works under the hood.
I’d appreciate any suggestions!
Additional context
No response
Logs
No response

Looks like this script

Doesnt have access to Vue instance and therefor it fails to execute code

Yes, but as this form is generated by SaaS, there’s only so much I can do. It’s also supposed to be separate from my site’s code and should work in most situations.
My biggest concerns with this issue are:
Why does it work in pure Vue then?
Why doesn’t it work after I generate a static page in Nuxt?
It seems like there might be differences in how the page is rendered in Vue vs Nuxt (even though Nuxt uses Vue), even with SSR turned off. That’s what I’m trying to understand) May be there's a bug or a room for improvement for Nuxt in this case.


text:
fix(schema): only show payloadExtraction warning when it is unset

🔗 Linked issue
No linked issue.
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 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
This is only a minor change and I am not sure if it is a good one.
This change should be made because when users sets experimental.payloadExtraction to true on purpose, they are hinting that either they are doing this on purpose or wanting the warnings to be gone.
This code change only changes the code so that if the enabled property is undefined (meaning the user did not set any configuration), it shows the warnings, but if the user sets it to true there will be no warnings.
🧪 Tests / Examples

I pressed the wrong button. Sorry.

Oops, my apologies; I forgot how we are doing this. In fact we set this here:
https://github.com/nuxt/nuxt.js/blob/6e78f9dbb03a059814d1284511f732b901dea4f6/packages/nuxi/src/commands/build.ts#L30-L34
So we don't want to show warning always if it is null or undefined because it is only on prerendering that it is in fact enabled, and in that case it is because it is set to true.

I want to work on this, but I am not exactly sure how it works.


text:
Cannot find module '.../html-parser' imported from '.../telegram-scraper.js'

https://github.com/nuzulul/telegram-scraper/blob/26dfe73090b72b58f6edaf8bb948a400f30f0c85/src/telegram-scraper.js#L1
Change to "import html_parser from './html-parser.js'"

https://github.com/nuzulul/telegram-scraper/blob/26dfe73090b72b58f6edaf8bb948a400f30f0c85/src/telegram-scraper.js#L1
Change to "import html_parser from './html-parser.js'"

@deuxego Hi thanks, i have changed it, you can check the latest version if you don't mind

authors: deuxego nuzulul

repo: nuzulul/telegram-scraper


text:
checkpoint

Hi, thank you for your excellent work~ It seems that the provided checkpoint is not right.
I run datasetGAN/test_deeplab_cross_validation.py, and the wrong is as follows:
"File "datasetGAN/test_deeplab_cross_validation.py", line 357, in test
classifier.load_state_dict(checkpoint['model_state_dict'])
Missing key(s) in state_dict: "backbone.conv1.weight", "backbone.bn1.weight", "backbone.bn1.bias", "backbone.bn1.running_mean", "backbone.bn1.running_var"....
Unexpected key(s) in state_dict: "module.layers.0.weight",.."
The parameters in the classifier and the provided .pth model are not consistent.

Hey we didn't provide deep lab checkpoints.

Thanks for your reply！So I have to train one？ Is there a shortcut if I only want to have a try？ Do you provide a demo or colab？

authors: ToBeNormal arieling


text:
🛑 PufferAI HPC Portal is down

In fe87b91, PufferAI HPC Portal (https://hpc.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PufferAI HPC Portal is back up in 304d2ee.

repo: nvgsg/lab-upptime


text:
🛑 NVIDIA AI Enterprise Hub is down

In 427e044, 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 2b1efb7.


text:
🛑 Kubeflow ML Platform is down

In d8d6c69, 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 8c31f5c.


text:
🛑 NVIDIA AI Enterprise Hub is down

In 77477b1, 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 d92b032.


text:
🛑 NVIDIA AI Enterprise Hub is down

In a9f249e, 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 2b24601.


text:
🛑 Kubeflow ML Platform is down

In 124d490, 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 7e45e31.


text:
Change ../ to the previous folder name

Sometimes i forget where i am, emacs already do something like that.
Example:

with this, i always know where i am

Is prompt_path what you are looking for? Try setting it to true in extension's settings table.

Perfect, thats it, THANKS!


text:
get actual project name

Can I somehow get actual opened project? (from g: or something)? Or I must modify telescope-project to save this into g: variable scope?
I want it add into my lualine.

nevermind.. I witched to https://github.com/natecraddock/workspaces.nvim


text:
Official docker image M1 support

Unfortunately official docker images don't work on Mac M1.
You can test it on Mac M1 with a command:
docker run --rm -u \
  "$(id -u):$(id -g)" \
  -w=/tmp --mount \
  type=bind,source="$PWD"/Jenkinsfile,target=/tmp/Jenkinsfile nvuillam/npm-groovy-lint:11.1.1 --failon warning --verbose

It just doesn't do anything.
However, if I clone this repository and build the Docker image locally:
docker build -t my-npm-groovy-lint -f Dockerfile .

Then almost the same command (difference is only in image name):
docker run --rm -u \
  "$(id -u):$(id -g)" \
  -w=/tmp --mount \
  type=bind,source="$PWD"/Jenkinsfile,target=/tmp/Jenkinsfile my-npm-groovy-lint --failon warning --verbose

works flawlessly.

I don't have a mac M1 :(
But it seems that you can run amd64 based images by adding --platform linux/amd64 to your docker run command :)
https://forums.docker.com/t/run-x86-intel-and-arm-based-images-on-apple-silicon-m1-macs/117123/2

I believe to support multiple architectures something like this:
docker buildx build \
--push \
--platform linux/arm/v7,linux/arm64/v8,linux/amd64 \ --tag your-username/multiarch-example:buildx-latest .

should be added to CI/CD.
https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/

Would you like to make a pull request?

authors: McMerph nvuillam

repo: nvuillam/npm-groovy-lint


text:
Crash bug

password ==0010011password
checkPwd("test.rar","0010011password");
/check password/
func checkPwd(archivePath string,password string)(bool,error){
log.Printf("password:%s len:%d\r\n",password,len(password));
r,err:= rardecode.OpenReader(archivePath,password)
defer  r.Close();
if(err!=nil){
return false,err;
}
_,err=r.Next();
if(err!=nil){
return false,nil;
}
_, err = ioutil.ReadAll(r)
if(err!=nil){
return false,nil;
}
return true,nil;
}
goroutine 1 [running]:
github.com/nwaples/rardecode.(*huffmanDecoder).readSym(0xc00007fb20, 0x785180, 0xc0000fc060, 0x14, 0x0, 0x0)
D:/go/src/github.com/nwaples/rardecode/huffman.go:137 +0x3a9
github.com/nwaples/rardecode.readCodeLengthTable(0x785180, 0xc0000fc060, 0xc0001e6050, 0x194, 0x194, 0x6cfb01, 0x1, 0xc0000fe050)
D:/go/src/github.com/nwaples/rardecode/huffman.go:167 +0x1fb
github.com/nwaples/rardecode.(*lz29Decoder).init(0xc0001e6050, 0xc0000fc060, 0x0, 0x0)
D:/go/src/github.com/nwaples/rardecode/decode29_lz.go:71 +0xc1
github.com/nwaples/rardecode.(*decoder29).readBlockHeader(0xc0001e6000, 0xc0000fc060, 0xc000083d48)
D:/go/src/github.com/nwaples/rardecode/decode29.go:212 +0x1a9
github.com/nwaples/rardecode.(*decoder29).init(0xc0001e6000, 0xbd8170, 0xc000104070, 0x6cbb01, 0x784800, 0xbd8170)
D:/go/src/github.com/nwaples/rardecode/decode29.go:57 +0x104
github.com/nwaples/rardecode.(*decodeReader).init(0xc000112030, 0xbd8170, 0xc000104070, 0x784fc0, 0xc0001e6000, 0x11, 0x1, 0x10, 0xc000104070)
D:/go/src/github.com/nwaples/rardecode/decode_reader.go:148 +0x101
github.com/nwaples/rardecode.(*Reader).Next(0xc000112008, 0x8, 0x722b76, 0xf)
D:/go/src/github.com/nwaples/rardecode/reader.go:305 +0x497

Sorry for the delay.
Is this only one particular file that is the problem? Having a copy of it would help to debug.
Is the version of go 32 or 64 bit?

test.rar.zip
password is 123456
go version go1.13.1 windows/amd64
Thank you

Only when the password is "0010011password" to unzip will it crash.

Sorry for the delay, it should be fixed now.

authors: dosgo nwaples

repo: nwaples/rardecode


text:
Missing input in nix flake?

Running on Hyprland
wlr-randr package required, but not found, terminating.

I installed on my NixOs machine running unstable channel and got the above error.
Maybe it should be added to the nix file as an input/dependency ?

I don't do packaging, except for Arch User Repository. Contact the packager, please.

authors: LamprosPitsillos nwg-piotr

repo: nwg-piotr/nwg-displays


text:
ci(action): Adding secret and variable display action

Adding a workflow for secret and variable display when merging a pull request into the main branch.

Lgtm!

repo: nxsaloj/github-ci-test


text:
🛑 Harmony Bot Website is down

In 046102f, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 3cc84a0.

repo: nxvvvv/uptime


text:
The naming and logic here I think needs work to make it more descriptive and readable

https://github.com/nyc-cto/LPaaS2/blob/fb1af31e70964b784b507238b411b4ed276905b0/src/constants/links.js#L2-L6

Updated to make it more descriptive and readable!

authors: nyccto-rapicastillo saifulislamdev


text:
Updating controller routes for buttons

@TTrinkle You never cease to impress!

@TTrinkle Great work as always Tanya!


text:
Screen for edit signature fails with checked 'Edit RAW HTML'

Hi
I don't see any issue for this problem.
MacOs Sierra 10.12.4
Versión 2.0.15 (2.0.15)
Bug?
Not pluginx
Using SMTP/IMAP account
When I try to edit my signature, error for "edit box" when click on Edit RAW HTML

Same here, with Windows 10 Pro. The frame containing the HTML text can't be resized, making it hard to edit the text directly. As a workaround, I just select all, copy to a text editor, make the adjustments there and paste it back. Not very friendly.

Same results with multiple custom and default themes as well.

authors: GautamBose abkrim jmassagues

repo: nylas/nylas-mail


text:
Failed to load remote context when trying to run ldo build on many shex shapes

When trying to run npm run build on https://github.com/jeswr/microsoft-kg-as-rdf the following error consistently occurs:
> email_api_test@1.0.0 build
> ldo build --input ./shex --output ./ldo

◠ Generating LDO Documents/home/jeswr/Documents/GitHub/jeswr/email_api_test/node_modules/jsonld-context-parser/lib/ContextParser.js:722
            throw new ErrorCoded_1.ErrorCoded(`Failed to load remote context ${url}: ${e.message}`, ErrorCoded_1.ERROR_CODES.LOADING_REMOTE_CONTEXT_FAILED);
                  ^

ErrorCoded: Failed to load remote context http://www.w3.org/ns/shex.jsonld: fetch failed
    at ContextParser.load (/home/jeswr/Documents/GitHub/jeswr/email_api_test/node_modules/jsonld-context-parser/lib/ContextParser.js:722:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at listOnTimeout (node:internal/timers:540:9)
    at process.processTimers (node:internal/timers:514:7)
    at async ContextParser.parse (/home/jeswr/Documents/GitHub/jeswr/email_api_test/node_modules/jsonld-context-parser/lib/ContextParser.js:588:58) {
  code: 'loading remote context failed'
}

Node.js v20.11.0

I suspect the best fix would be to use a custom document loader to cache http://www.w3.org/ns/shex.jsonld and supply that context to jsonld-context-parser. A brief look indicates that the jsonld-context-parser call is coming from the https://github.com/o-development/jsonld2graphobject dependency.

I would also recommend using the https context rather than the http context which redirects to the https context.

repo: o-development/ldo


text:
Restrict Group.fromJSON type to an object literal

Description
Fixes the weird behavior outlined in https://github.com/o1-labs/snarkyjs/issues/210
The Group.fromJSON function was defined in the snarky.d.ts file to accept parameters that the OCaml side was not handling. This PR changes the types that Group.fromJSON expects to be only valid ones, being an object literal with x and y values defined as either numbers or strings.

thanks!

authors: MartinMinkov mitschabaude


text:
Add link to welcome or login page from 'Please log in ...'

When the logout page 'Please log in...' is not redirected properly then user has no way how to go easily away from this page.

it happens by automatic logout

Fixed

authors: leistnerova mareklibra

repo: oVirt/ovirt-web-ui


text:
fix the render of the console button list on the VmDetail component

On the VM detail page, the button are now rendered with separators
both when the VM canConsole() and it can't canConsole().

this isn't critical and Bohdan wants to go first ;) so I'll hold off merging this until 1.4.2.
@sjd78 can you insert before and after screens (and on all such things)? ty

VmDetail is being replaced in #699 and #654 reworks the console button completely.
This PR is no longer needed as it just cleans up the console button list on VmDetail prior to merging #699.


text:
feat(PUPIL-166): display attribution for quiz images

Description
Music year: 1951
Displays image attribution when present below the questions of a starter or exit quiz.
How to test

Go to https://deploy-preview-2245--oak-web-application.netlify.thenational.academy/pupils/programmes/english-primary-ks2/units/developing-reading-preferences-in-year-5/lessons/developing-reading-preferences-in-year-5-through-appreciation-of-characters
Click on "Starter Quiz"
You should see attribution text beneath the first question

A few other lessons containing examples of attribution text:
https://deploy-preview-2245--oak-web-application.netlify.thenational.academy/pupils/programmes/english-primary-ks2/units/developing-reading-preferences-in-year-6/lessons/developing-reading-preferences-by-appreciating-characters-in-adaptations
https://deploy-preview-2245--oak-web-application.netlify.thenational.academy/pupils/programmes/english-primary-ks2/units/developing-reading-preferences-in-year-6/lessons/developing-reading-preferences-in-year-6-through-text-recommendations
Containing attribution on question images
https://deploy-preview-2245--oak-web-application.netlify.thenational.academy/pupils/programmes/science-secondary-ks3/units/moving-by-force/lessons/reading-distance-time-graphs
https://deploy-preview-2245--oak-web-application.netlify.thenational.academy/pupils/programmes/english-primary-ks2/units/weather-cold-calm-and-stormy-words/lessons/rich-vocabulary-associated-with-stormy-words
Screenshots
Desktop

Tablet

Mobile

@carlmw all good, I was just wondering if we could update the attributions on question images that have multiple to say 'Q1 XXX, Q2 xxx' etc with a comma added after each one if possible? That is the format of the attributions for multiple images at the bottom of the starter & exit quiz pdf's, sop would be good to match if that isn't too difficult to update in this pr? E.g:
For question stems with an image at the top, that would be the first, then the 'Q1 XXX, Q2 xxx' etc

@messmike
🤔 these aren't the images for the questions — they're the images for the answers in an MCQ with images. Would "A1 XXX, A2 XXX" be an appropriate treatment?

@carlmw all good, I was just wondering if we could update the attributions on question images that have multiple to say 'Q1 XXX, Q2 xxx' etc with a comma added after each one if possible? That is the format of the attributions for multiple images at the bottom of the starter & exit quiz pdf's, sop would be good to match if that isn't too difficult to update in this pr? E.g:
For question stems with an image at the top, that would be the first, then the 'Q1 XXX, Q2 xxx' etc

@messmike 🤔 these aren't the images for the questions — they're the images for the answers in an MCQ with images. Would "A1 XXX, A2 XXX" be an appropriate treatment?

Yep, you are totally correct! In that case, just the numbers are probably better. Cheers @carlmw

:tada: This PR is included in version 1.353.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: carlmw messmike oak-machine-user

repo: oaknational/Oak-Web-Application


text:
Need an example for component to component communication

Need example for communication between components.

We have a sample in https://github.com/oam-dev/samples that shows this

@iyyappam  could the samples repo help you?

I think it is better to have a section explaining how it is done and have a link to the samples repo. Because any functional app needs this capability and I couldn't readily find it in the repo.

After reading this, it's valid to have a section that links somewhere. Will change the tags.

authors: iyyappam suhuruli wonderflow

repo: oam-dev/rudr


text:
Fix Caluculation Error in Background Size

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Codecov Report

Merging #458 (938dae0) into dev/0.5 (f090167) will increase coverage by 0.17%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           dev/0.5     #458      +/-   ##
===========================================
+ Coverage    48.98%   49.16%   +0.17%
===========================================
  Files          346      346
  Lines        18559    18490      -69
  Branches      2481     2468      -13
===========================================
- Hits          9091     9090       -1
+ Misses        9468     9400      -68

Impacted Files
Coverage Δ

packages/core/src/Background.ts
100.00% <ø> (ø)

...ges/core/src/RenderPipeline/BasicRenderPipeline.ts
51.74% <ø> (ø)

packages/draco/src/decoder.ts
0.00% <0.00%> (-0.92%)
:arrow_down:

packages/loader/src/scene-loader/Oasis.ts
0.00% <0.00%> (ø)

...ackages/loader/src/scene-loader/ResourceManager.ts
0.00% <0.00%> (ø)

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 f090167...938dae0. Read the comment docs.

repo: oasis-engine/engine


text:
allow signing other messages

other than known consensus transaction types, e.g. paratime / runtime transactions
fixes #109
preview for unrecognized consensus transaction:

preview for unrecognized signature context:

no translations yet, cc @lindalu1111
UI doesn't support variable length message--this bridge lock transaction used as an example of a runtime tx is a little too long
can't copy text, which prevents people from searching or using tools to analyze the context+message

It would be better if the transaction was shown as pretty printed JSON instead of hex-encoded CBOR. This currently makes it impossible to see what the body is.

I experimented with that briefly, but the byte arrays are ugly. in the
simplest implementation they get serialized as something like {"0": 123,
"1": 45, ...}.
I wonder if it also would choke on non-string dictionary keys.
we'd need to serialize to something slightly more sophisticated than JSON
per se.
other troubles: we don't know what the different byte arrays are in this
problem, because we're assuming that we don't know the structure of the
body. so even if we set up something nice to base64-encode byte arrays,
it's not a good experience for addresses, which usually we see in bech32
On Mon, Aug 30, 2021, 10:41 PM Jernej Kos @.***> wrote:

It would be better if the transaction was shown as pretty printed JSON
instead of hex-encoded CBOR. This currently makes it impossible to see what
the body is.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/oasisprotocol/oasis-wallet-ext/pull/110#issuecomment-908916049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJDVILWXQOYPGN3VEHQZFJ3T7RTPBANCNFSM5DCZEEUA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Disclaimer: This e-mail and any attachments may contain confidential
information. If you are not the intended recipient, any disclosure,
copying, distribution or use of any information contained herein is
strictly prohibited. If you have received this transmission in error,
please immediately notify the sender and destroy the original transmission
and any attachments without reading or saving.

Let's file a follow-up issue for nicer display

authors: kostko peterjgilbert pro-wh

repo: oasisprotocol/oasis-wallet-ext


text:
export some default margins

export default margins (e.g. const item = [0, 0.5, 1]) or component wrappers that set some defaults (e.g. const Item = (props) => <Grid margin={[0, 0.5, 1]} {...props} />)
add to the wiki https://github.com/obartra/reflex/wiki/Spacing

Now that Col is provided do we still want to offer a list of "common" margins?

@arahansen

My preference would be to avoid doing this. Instead either have more
derived exports, or additional available properties for the existing
components.
Or just leave it to user land 😄
On Tue, Jul 4, 2017 at 11:40 AM Oscar notifications@github.com wrote:

Now that Col is provided do we still want to offer a list of "common"
margins?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obartra/reflex/issues/131#issuecomment-312933245, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIV0bhiXV0g2iV2tQ5MDwCxVZQKG2-gFks5sKobTgaJpZM4OIEv_
.

agreed, closing

authors: arahansen obartra

repo: obartra/reflex