text:
Mathematical expressions are marked correct if they aren't

I have an inequality I'd like the students to simplify, but it does something unexpected.

Something like 5>=x also gets marked as correct, while something as -3>=x gets marked as incorrect.

The question itself: https://numbas.mathcentre.ac.uk/question/84481/test-ongelijkheden/

I think I found my mistake: I have to use the accuracy tab to fix this.
Is it possible to let it check all integers between -10 and 10 (once) though?

Marking inequalities is difficult: the standard marking algorithm checks numerically, which doesn't work particularly well for boolean expressions like this.
You can check a fixed set of values with a custom marking algorithm, redefining the vset note to contain all the values of x you want to check:
vset:
   map(["x": x], x, -10..10)

But that doesn't work when the student has a non-integer on the right hand side of the inequality.
This question is really about the form of the student's answer, so you should use a pattern restriction. A pattern of
x <= (`+- $n);rhs

would check that the student has simplified the inequality as far as you know they can. You can then set Numbas to check only the number part, which will require the student's number to be exactly the same number as in your expected answer.
I've made a copy of your question which does this at https://numbas.mathcentre.ac.uk/question/share/view/e1a6230b-acea-4aea-a57c-68ebf5e296a9

Marking inequalities is difficult: the standard marking algorithm checks numerically, which doesn't work particularly well for boolean expressions like this.
You can check a fixed set of values with a custom marking algorithm, redefining the vset note to contain all the values of x you want to check:
vset:
   map(["x": x], x, -10..10)

But that doesn't work when the student has a non-integer on the right hand side of the inequality.
This question is really about the form of the student's answer, so you should use a pattern restriction. A pattern of
x <= (`+- $n);rhs

would check that the student has simplified the inequality as far as you know they can. You can then set Numbas to check only the number part, which will require the student's number to be exactly the same number as in your expected answer.
I've made a copy of your question which does this at https://numbas.mathcentre.ac.uk/question/share/view/e1a6230b-acea-4aea-a57c-68ebf5e296a9

authors: YannickNeyt christianp

repo: numbas/Numbas


text:
AllorNothing marking script

Allows a user to choose whether or not to give partial credit when creating a multiple response question (e.g. needing to choose 2 correct answers out of 4 to get credit).

Thanks for this.
Many of the marking options become irrelevant in "all-or-nothing" marking, so they should be hidden. I'd prefer to have a drop-down box to pick a "marking mode", rather than a checkbox - the options could be "Exactly match the expected selection" and "Award marks for each selection".
It would make sense for the editing process in "all or nothing" mode to be:

give options
tick options which must be selected
give the number of marks to award.

So it would make sense if the marking matrix was an array of booleans rather than an array of numbers. Perhaps this should be a separate part type.

I ended up implementing this myself.

source: gharchive/pull-request

authors: christianp r-s-rai

repo: numbas/editor

license_type: permissive

license_source: bigquery


text:
check against stored processed multiple files

This is for a multiple-entry,each with their own js/css/templates, multiple-output scenario, as follows:
example directory
.
+-- node_modules
+-- build
+-- dist
|   +-- page1.html
|   +-- page2.html
|   +-- page3.html
+-- src
|   +-- pages
|   |   +-- page1
|   |   |   +-- template.hbs
|   |   |   +-- index.js
|   |   |   +-- styles.css
|   |   +-- page2
|   |   |   +-- template.hbs
|   |   |   +-- index.js
|   |   |   +-- styles.css
|   |   +-- page3
+-- package.json
+-- webpack.config.js
+-- //etc...
webpack.config.js
// ... some var setup above
let pageNames = ['page1','page2','page3'];

pageNames.forEach((pageName) => {
  entry[pageName] = `./src/pages/${pageName}`;
  extractTexts[pageName] = new ExtractTextPlugin('[name]-styles.css');

  loaders.push({
    test: /\.css$/,
    loader: extractTexts[pageName].extract('style', 'css'),
    include: [
      path.resolve(__dirname, 'src', 'pages', pageName)
    ]
  });

  plugins.push(new HtmlWebpackPlugin({
    chunks: [pageName],
    filename: `${pageName}.html`,
    template: `src/pages/${pageName}/template.hbs`
  }));

  plugins.push(extractTexts[pageName]);
});

plugins.push(new ScriptExtHtmlWebpackPlugin({
  inline: pageNames.map((pageName) => {
    return `${pageName}-scripts`;
  })
}));

plugins.push(new StyleExtHtmlWebpackPlugin());

Not sure if what I'm trying to do here is the best way, so any thoughts/suggestions would be greatly appreciated!

Thank you!
I'll take a look - but not until the weekend I'm afraid.
If OK, do you understand the unit tests (hint, hint)?

No worries on looking at it this weekend - thanks for the quick reply!
Some of the unit tests were failing upon initial checkout, before I edited anything, and those are the same that are failing now (it seems).
I'm also wondering if my use-case for this plugin is unique and I may not need to submit this? My next step is getting a sass-loader to work before this all, so i can eventually: write sass, compile it to css, extract it out of the js file, and inline it into the ...

Closing this one as I opened a new one with sass support

authors: hagmandan numical

repo: numical/style-ext-html-webpack-plugin

license: mit


text:
Fix issues

Updates, bug fixes, pesky IE problems, all squashed 😈🕷

@dhanesh-kapadiya can you resolve these issues so that I may merge?

repo: numieco/patriot-trading


text:
Adds a capability to generate a result xml file with nunit v2 spec.

Hello I used your project (https://github.com/nunit/nunit-v2-result-writer) to adapt a funcionality to convert the result file for old format (v2).
To do it, just add parameter "--convert-to-v2" to "dotnet test" command.
I did it, because some project like Cobertura, Jenking and Hudson still does not have compatibility with v3 spec.

A few comments...

You added the source code of the v2 result writer, which gives us an extra place to make updates. Could you use the existing assembly, distributed through nuget or otherwise?

You added a new option, rather than giving the --result option a new value for format. That makes this command-line different from both the nunit3 console and nunitlite.

Something happenedin the runner file (white space?), making it look as if most lines got changed when viewed under GitHub.

Hello.
1 and 2 - I will do the changes and send a new pull request.
3 - I'm sorry for this, my VS changed the file's encode and I didn't realize it.

Hello @CharliePoole. I did the changes like you was suggest.
Now, to convert, you just need add '--result=filename.xml;format=nunit2' parameter on 'dotnet test' command.
Thanks!

Hello @CharliePoole. I did the changes like you was suggest.
Now, to convert, you just need add '--result=filename.xml;format=nunit2' parameter on 'dotnet test' command.
dotnet test ./test/MyProject.Tests --result=TestResult.xml;format=nunit2

Thanks!

Great! That will make it easier for users to switch form the console to the dotnet runner and for us to maintain. In future, I'm hoping to create a module that will optionally load an extension assembly, if requested by name, without all the overhead of supporting extensions fully. This will lead into that pretty well, I think.
@rprouse should still review this.

The code looks good to me although this will be of limited use once Visual Studio 2017 is released next month. Once the .NET Core CSPROJ format is fully released, this adapter will no longer work in Visual Studio or on the command line. Microsoft is dropping support for it. From my reading, as soon as you install the new dotnet tools, the old style no longer works?
I will merge, but I am not sure if we will do another release.

I'm with you, but I have a project in current NetCore version and I don't know why, but Hudson CI and Jenkins CI doesn't supports the v3 format of NUnit TestResult.xml. For this reason, and because there is no one UI to visualize the result of the executed tests into VsCode I did this PR.
Thanks for the merge!
I'm fan of NUnit. Thanks for your work!

For now, you can use the CI build of the package from the Appveyor nuget feed.

Great! Thank you very much!
Em sex, 10 de fev de 2017 às 18:23, Rob Prouse notifications@github.com
escreveu:

For now, you can use the CI build of the package from the Appveyor nuget
feed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nunit/dotnet-test-nunit/pull/103#issuecomment-279056377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEfLCiB7tKrUShMV3Ce4pUBj4RhPFvYcks5rbMdagaJpZM4L8pSS
.

--
Bernardo A.C. Esbérard

authors: CharliePoole bernardbr rprouse

repo: nunit/dotnet-test-nunit


text:
Update to version 2.1.1

Larastan Version: 2.1.0
--level used: none
Pull request with failing test:

Description
If you are using the Laravel IDE helper from barryvdh but want to upgrade larastan to the latest version there is a compatibility issue through composer/pcre.
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires barryvdh/laravel-ide-helper ^2.12.2 -> satisfiable by barryvdh/laravel-ide-helper[v2.12.2, 2.12.x-dev].
    - You can only install one version of a package, so only one of these can be installed: composer/pcre[1.0.0, 1.0.1, 1.x-dev, 2.0.0, 2.x-dev, 3.0.0, 3.x-dev].
    - nunomaduro/larastan v2.1.1 requires composer/pcre ^3.0 -> satisfiable by composer/pcre[3.0.0, 3.x-dev].
    - barryvdh/laravel-ide-helper[v2.12.2, ..., 2.12.x-dev] require composer/pcre ^1.0 -> satisfiable by composer/pcre[1.0.0, 1.0.1, 1.x-dev].
    - Root composer.json requires nunomaduro/larastan ^2.1.1 -> satisfiable by nunomaduro/larastan[v2.1.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

This is not related to Larastan.

@paddockDev laravel-ide-helper support both Laravel 8 & 9 so it cannot jump to composer/pcre:^3.0 :(

@szepeviktor It's been fixed. :)

source: gharchive/issue

authors: canvural paddockDev szepeviktor

repo: nunomaduro/larastan

license: MIT

license_source: github-api


text:
feat: use correct builder return types for Model::newQuery* methods

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

Changes
This PR adds new NewModelQueryDynamicMethodReturnTypeExtension that returns correct types for Model::newQuery* method family.
Breaking changes
n/a

I like the arrows!

authors: canvural szepeviktor


text:
refactor: consolidate duplicated constants

Looks like these were copy pasted. Let's consolidate and just reference constants from one place.

LGTM if you fix the style error.

thanks @canvural , all done

authors: canvural mr-feek


text:
System.out.println() error

Summary
System.out.println() is being read?
Description:
Hi, not sure why I'm running into this error, google doesn't offer any solutions either...
Seems like jshell wants to read the system.out.println line which is weird.
my toString methods involves getting the log history and then concatenating them into a string, then putting them into a supplier again. my public String toString() gets them before returning it.
thanks in advance for the help m going crazy! ><
Code Snippets
this is my toString method!
`
Supplier<String> stringeh() {
    String stringy = "";
    if (this.getInputs().size() > 0) {
        stringy += "Logger[" + this.getItem() + "]";
        for (int x = 0; x < this.getInputs().size(); x++) {
            stringy += this.getInputs().get(x).get();
        }
    } else {
        stringy += "Logger[" + this.getItem() + "]";
    }
    final String stringyy = stringy;
    Supplier<String> stringoh = () -> stringyy;
    return stringoh;
}

public String toString() {
    return this.stringeh().get();
}`

Screenshots

Hi, it seems redundant to wrap String around a Supplier since toString() is returning a String anyway. But yeah, very weird that jshell runs your code fine then get this error. Maybe you can provide more details on where you think the error might be coming from for others to help you?

Not entirely sure but I think the sub 1 is being inputted in jshell (and hence treated as a statement) rather than from the print statement (where it should be treated as a String), hence it is raising the error.  Maybe you can try uploading to code crunch to confirm whether this is really being caused by your code?

hi @weiquany @Albunist thanks for the inputs! Will try again, appreciate it a lot!!

authors: Albunist tammehh weiquany


text:
[T2A4][F09-A3] TanSuanZhi

Ready for review

Let's don't say refactor code when we trying to make the code unreadable. :P
Anyway, good job :)


text:
[T3A2][T11-A1]TAN JUN HAO

Ready for review

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


text:
Google Analytics does not track page views

In spa mode, click to switch page Google Analytics (analysis) can not track the page view, only when re-refresh the page, will be tracked by ga

Why didn't you just Google it? Please try to fix issues first by yourself. This one really isn't difficult.
Hint: Custom nuxtRoute event

Why didn't you just Google it? Please try to fix issues first by yourself. This one really isn't difficult.
Hint: Custom nuxtRoute event

gtm: {
    enabled: true,

    id: process.env.GTM_ID,
    layer: 'dataLayer',
    variables: {
      sites: 'h5-cs'
    },

    pageTracking: true,
    pageViewEventName: 'nuxtRoute',   // nuxtRoute and pageViewEventName

    autoInit: true,

    scriptDefer: true
  }

NuxtRoute has been added, now GA cannot track when switching routers

This helped for me:
https://stackoverflow.com/questions/52885180/can-anyone-help-implementing-nuxt-js-google-tag-manager/52885317

Ah, looks like a googled result...

This helped for me:
https://stackoverflow.com/questions/52885180/can-anyone-help-implementing-nuxt-js-google-tag-manager/52885317

Thanks. It's work without pageURL variable.

authors: AlexZd bart liseipi nadrshin

repo: nuxt-community/gtm-module


text:
[NEXT] Route navigation resets locale

Version
@nuxtjs/i18n: 8.0.0-alpha.1
nuxt: 3.0.0-rc.11
Nuxt configuration
Please change to [x] if relevant for this issue:

[ ] Applies to a site deployed to a static server (site generated with nuxt generate)
[x] Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration

Reproduction Link
https://stackblitz.com/edit/github-jzewpd-crebuq?file=package.json
Steps to reproduce
Swap the locale using the button, then navigate with the link at the bottom. The locale will be reset to the fallbackLocale
What is Expected?
locale selection should be persisted across route change
What is actually happening?
the selected locale does not persist across navigation

Thank you for your reporting as always!
I've just checked your reproduction!
no_prefix routing strategy is used in your repro.
no_prefix routing strategy is depended in browser & cookie detection
see also the docs: https://v8.i18n.nuxtjs.org/guide/routing-strategies#no_prefix
These features hasn't still implemented fully yet.
when we will have been completed it, please you will check it again 🙏
So, we will close this issue.
Thanks!

authors: kazupon warflash


text:
Login using OAuth Providers

Is your feature request related to a problem? Please describe.
Would be great to have the possibility to login with OAuth Providers such as Google or Github and then automatically store the JWT for future requests.

I was searching this right now to connect to Auth0 and, since there's nothing on Docs, I was searching here.
+1 for the improvement.

Closing this as it has been implemented in v1.0.0 version of the module for nuxt 3 with getProviderAuthenticationUrl and authenticateProvider methods.

authors: AdrianoCahete benjamincanac rylax

repo: nuxt-community/strapi-module


text:
Different domains only working on defaultLocale on Nuxt 3.5.2

Environment

Operating System: Darwin
Node Version:     v16.17.0
Nuxt Version:     3.5.1
Nitro Version:    2.4.1
Package Manager:  yarn@1.22.19
Builder:          vite
User Config:      modules, gtag, vite, linkChecker, experimental, nitro, robots, i18n, image, extends, runtimeConfig, css, build, app
Runtime Modules:  @storyblok/nuxt@5.4.6, @nuxt/image-edge@1.0.0-28059208.2abef1b, @nuxtjs/i18n@8.0.0-beta.12, nuxt-schema-org@2.1.3, nuxt-simple-robots@1.0.9, nuxt-gtag@0.5.7
Build Modules:    -
Server : Vercel

Reproduction
We can't make the Different Domains working by using the default configuration on i18n (https://i18n.nuxtjs.org/different-domains#runtime-environment-variables)
And in our cases, we need to have different branches for different domains & defaultLocale to make it work
Here are our repo
For SG language: https://github.com/evercam/evercam-static/tree/multi-domain
For IE language: https://github.com/evercam/evercam-static/tree/io-multi-domain
For AU language: https://github.com/evercam/evercam-static/tree/au-multi-domain
Describe the bug
From my perspective, it should be running well without using a different branch right? In that case, what is missing on our side?
This is the example nuxt.config for sg
// https://nuxt.com/docs/api/configuration/nuxt-config
const localeDomains = require('./config/locale-domains')

export default defineNuxtConfig({
    modules: [
        ['@storyblok/nuxt', { accessToken: process.env.STORYBLOK_API_KEY }],
        // Activate unlight house only if want to check locally
        // '@unlighthouse/nuxt',
        '@nuxt/image-edge',
        '@nuxtjs/i18n',
        'nuxt-schema-org',
        'nuxt-simple-robots',
        'nuxt-gtag'
    ],
    gtag: {
        id: process.env.G_TAG
    },
    // Activate this if get [ERROR] No loader is configured for ".node" files: node_modules/fsevents/fsevents.node
    vite: {
        //...
        optimizeDeps: { exclude: ["fsevents"] },
    },
    linkChecker: {
        failOn404: false,
    },
    experimental: {
        inlineSSRStyles: false
    },
    nitro: {
        prerender: {
            routes: ['/']
        }
    },
    robots: {
        sitemap: [
            '/sitemap.xml',
        ],
    },
    i18n: {
        locales: [
            {
                code: 'en-sg',
                iso: 'en-sg',
                name: 'SG',
                domain: localeDomains.sg,
            },
            {
                code: 'en-ie',
                iso: 'en-ie',
                name: 'IE',
                domain: localeDomains.ie,
            },
            {
                code: 'en-uk',
                iso: 'en-uk',
                name: 'UK',
                domain: localeDomains.uk,
            },
            {
                code: 'en-au',
                iso: 'en-au',
                name: 'AU',
                domain: localeDomains.au,
            },
            {
                code: 'en-us',
                iso: 'en-us',
                name: 'US',
                domain: localeDomains.us,
            },
            {
                code: 'en-pl',
                iso: 'en-pl',
                name: 'PL',
                domain: localeDomains.pl,
            },

        ],
        defaultLocale: 'en-sg',
        differentDomains: true,
        detectBrowserLanguage: false
    },
    image: {
        provider: 'storyblok',
        storyblok: {
            baseUrl: 'https://a.storyblok.com'
        }
    },
    extends: [
        'nuxt-seo-kit'
    ],
    runtimeConfig: {
        public: {
            siteUrl: localeDomains.sg,
            siteName: 'Construction Time-lapse & Project Management Live Cameras | Evercam',
            siteDescription: 'Construction time-lapse cameras & project management software helps in marketing content, project management and dispute avoidance in the construction industry.',
            language: 'en-sg', // prefer more explicit language codes like `en-AU` over `en`
        },
        indexable: true
    },
    css: [
        // CSS file in the project
        '@/assets/css/main.css',
        '@fortawesome/fontawesome-svg-core/styles.css',
    ],
    build: {
        transpile: ['@fortawesome/vue-fontawesome'],
    },
    app: {
        head: {
            charset: 'utf-8',
            viewport: 'width=device-width, initial-scale=1',
            link: [
                { rel: 'stylesheet', href: 'https://cdn.jsdelivr.net/npm/bootstrap@5.2.0-beta1/dist/css/bootstrap.min.css', integrity: 'sha384-0evHe/X+R7YkIZDRvuzKMRqM+OrBnVFBL6DOitfPri4tjfHxaWutUpFmBp4vmVor', crossorigin: 'anonymous' },
                { rel: 'stylesheet', href: 'https://evercam.io/wp-content/themes/evercam/css/main.css?id=2165878 ' },
                { rel: 'stylesheet', href: 'https://evercam.io/wp-content/themes/evercam/css/main.css?id=3162236' },
                { rel: 'stylesheet', href: 'https://evercam.io/wp-content/themes/evercam/fontawesome/css/all.min.css' },
                { rel: 'icon', type: 'image/x-icon', href: 'https://evercam.io/favicon.ico' }
            ],
            script: [
                { src: 'https://cdn.jsdelivr.net/npm/bootstrap@5.2.0-beta1/dist/js/bootstrap.bundle.min.js', integrity: 'sha384-pprn3073KE6tl6bjs2QrFaJGz5/SUsLqktiwsUTF55Jfv3qYSDhgCecCxMW52nD2', crossorigin: 'anonymous' },
                {
                    type: 'text/javascript',
                    id: 'zsiqchat',
                    body: true,
                    innerHTML: `var $zoho=$zoho || {};$zoho.salesiq = $zoho.salesiq || {widgetcode: "694935cc19da1884296ec776ee2796a95201621fa2797eb644df334acc9aa292", values:{},ready:function(){}};var d=document;s=d.createElement("script");s.type="text/javascript";s.id="zsiqscript";s.defer=true;s.src="https://salesiq.zoho.com/widget";t=d.getElementsByTagName("script")[0];t.parentNode.insertBefore(s,t);`
                }
            ]
        },
    },
})

Additional context
Also, we are using the default SSR on Nuxt, will it be the case? If yes, what's needed for us to run this without using different branch? thanks
Logs
No response

Hi!
Thank you for your reporting!
I've confirmed your repository.
However, I could not understand to how to reproduce with your repository.
I seem that your repository a little huge.
Could you give us more minimal repository please 🙏

close in-activity.
if you have still issue, please you would open as new issue with minimal reproduction.
Thanks!

Have the same issue, @studentofcoding did you solve your issue?

authors: IBakeCookies kazupon studentofcoding


text:
docs: use css variable for color

Since Docus not does use Tailwind anymore.

Thank you!

authors: Atinux danielroe

repo: nuxt-modules/ionic


text:
nuxi build prerenders pages

Environment
Nuxt CLI v3.0.0-rc.4                                                    13:43:07
RootDir: /sandbox                                                       13:43:07
Nuxt project info:                                                      13:43:07

Operating System: Linux
Node Version:     v14.18.1
Nuxt Version:     2.16.0-27616340.013f051b
Package Manager:  yarn@1.22.17
Builder:          webpack
User Config:      ssr, serverHandlers, devServerHandlers, bridge, buildModules
Runtime Modules:  -
Build Modules:    @nuxt/bridge@3.0.0-27621385.6ebdec4

Reproduction
https://codesandbox.io/s/vigilant-mayer-90ctqf?file=/package.json

Open a new terminal
Run yarn build
Notice the log output about prerendering.

Describe the bug
nuxi build should not prerender my pages when SSR is enabled. It takes around 10 minutes for my nuxt application and then crashes with a Heap out of memory error.
Additional context
No response
Logs
No response

This is the new nitropack behaviour - you can prevent it with the following config:
export default defineNuxtConfig({
  nitro: {
    prerender: {
      crawlLinks: false
    }
  },
})

repo: nuxt/bridge


text:
1.0.0-alpha Breaking changes

Hello, it seems like 1.0.0-alpha1 has been pushed to npm last night.
My Nuxt.js project is broken now. Can anyone tell, what the breaking changes are?

@John0x I think you were too fast in adopting. The website and changelog still does not exist. As far as I can see the most important change is removing injectAs from plugin creation and being able to export a function inside of any plugin file. But better roll back and wait for an official release with changelog

I'm getting this too:
Nuxt.js Error:

Error: [nuxt] state should be a function in store/index.js

Assuming that's a breaking change and not a bug?

Sigh

Nuxt.js Error:

Error: [nuxt] state should be a function in store/index.js

+1

What's surprising to me is that the new package was pushed to NPM, but no release was made on Github. It's entirely possible this release was a mistake and was intended for internal use.
That being said, since it's marked as alpha, I wouldn't bother reporting any errors until there's an actual release here on the repository.

New release 1.0.0-alpha1 is semver incompatible with previous releases (0.x.x) so exiting users should be safe as long as they don't explicitly upgrade dependencies. (This is just whay versioning is used right? :D) We have intentionally postponed release notes and docs to get feedback from alpha users and releasing a final and stable migration guide to avoid multiply breaking changes.
Although Nuxt has many internal improvements since this version, but migration should be easy for exiting users. Here is an unofficial and incomplete migration guide for those who willing experiment new release:
runInNewContext
Most of breaking changes are because of new vue ssr performance improvements. Each render request is by default is executing in the same process context as server while this gives huge improvements it needs additional steps in your project code. learn more
Stores state should return a function
As of global context, just like data function for components which returns a function instead of data itself we need to make this change for stores as well.

See vuex-store-modules and vuex-store examples for reference.

If your root store is currently returning a Vuex instance, it should be changed to something like this:

const createStore = () => new Vuex.store({
  // Store options
}

All of your stores (including submodules) should return a function instead of object :

export state = () => {
  // initial state data
}

Plugins should export a function if want to mutate global state
If your plugins are chaging global state, such as store and api tokens you should export a function which sets it for each request.

See i18n example for reference.
Consider that if you don't take this step, it may lead to potential SECURITY BUGS as tokens are reused across requests

How would the vue-apollo example be updated with the new injectAs deprecation in mind? I just spent the last few hours trying to get that working on a fresh app, had no idea there were breaking changes and not all examples were updated.
Note that I've seen the i18n example, but the vue-apollo integration needs to inject apolloProvider into the Vue instance. I don't see which line in the i18n example does this and I[m not familiar with that plugin.
Thanks.

@pi0  How to get store instance now? In the previous version is

I'd like to know this too. I figured out the answer to my own question--turns out app is the root Vue instance so adding properties to that injects them--but now I need to access the store in my Apollo client to set authentication tokens. Can't see how to do that now that it's a function.
Thanks.

Store instance is available in vue components instance as this.$store . It is also passed into plugins and middleware function context as store.  Not tried to locally test Apollo integration.

Ok, i has been found it, i use store instance in plugins, example https://nuxtjs.org/examples/i18n/
Thanks.

If I understand correctly, the Nuxt constructor now returns a promise?
Isn't this a bad practice as explained here ?

@pi0 do you know how the changes on alpha3 can make vue-apollo work correctly? It would be great if the example could get updated. Thanks!

@dohomi Sure. Will work on that soon ;)

@pi0 how do you import in plugins now? Ie I normally import axios through an instance i created as a plugin.
For example, import axios from '~plugins/axios'
Now that '~' is no longer available and the plugin file returns a function, are the plugins registered somewhere globally?

@pi0 is there a more expansive breaking changes document? window.onNuxtReady is also no longer available.

@uptownhr For your first question, access plugins instance is a little more tricky, as SSR context is shared across request. You may use axios module for easier usage or looking into it's implementation to get idea how we could access context from inside components. (There is also another workaround using this.$ssrContext but i haven experimented it yet)

window.onNuxtReady is also no longer available.

It should not happen!! If possible please prepare a glitch test to reproduce problem and opening an issue for that.

hi @pi0 modules is new to me and I need to look at it more. But it looks like it will not resolve the issue I am having. As I'd like to get access to the same axios instance from all parts of the app. Like store, plugins, middleware or even my own personal library.
Last night i wrote a quick workaround but let me know if I'm thinking about this incorrectly and if there is a better approach.
Here is my plugins/axios.js
import axios from 'axios'

let options = {}

if (process.SERVER_BUILD) {
  options.baseURL = `http://localhost:3000/api`
} else {
  options.baseURL = `/api`
}

const apiHandler = axios.create(options)

export default function ({store, router}) {
  apiHandler.interceptors.response.use( response => {
    return response
  }, error => {
    if ( error.response.status == 401) {
      //alert('You have been logged out')
      return store.dispatch('logout').then( res => {
        router.push('/login')
      })
    }

    throw error
  })

  console.log('onnuxtready', window.onNuxtReady)

  return apiHandler
}

export { apiHandler as axios }

This exports the default function to retrieve the context and exports another axios. Now I can import import {axios} from ~plugins/axios and get the same axios instance.

Consider axios instance is created in global context! So is being shared across requests in server side. This is a WRONG and insecure approach.
Take a look at axios/plugin.js#L87 :
export default ({app}) => {
  // Create new axios instance
  const axios = Axios.create({
    baseURL: API_URL + (process.env.API_PREFIX || '/api')
  })

  // Setup instance interceptors
  axios.interceptors.request.use(withCredentials);
  axios.interceptors.response.use(undefined, handleError);

  // Make accessible using {this,$nuxt}.$root.$options.$axios
  app.$axios = axios

  // setToken helper
  axios.setToken = setToken.bind(axios)
}

How can I access Axios from within the store?

Could it be that Vuex Actions don't work anymore?

@pi0 How to get store instance now? In the previous version is
import VueStore from '~store'

Know any one a solution for that?

@LowM4N Do you want to access store outside of components/plugins/middleware ? Please explain more about use case.

@pi0 Is there a new general solution for this kind of thing?
I don't see how one would access the axios instance within a store for example.

@John0x Sorry for delay answering. Give us a little more time we are actively working on new changes and their documentation, Also will update axios and auth store modules soon for reference :)

@pi0 I want encapsulate my api logic in classes, but for that i need the jwt token from my store. I have the same problem with the router, I want use it in my store modules, but I dont know how to get him. A solution is to pass it to the action as parameter, but I found this to hacky.

@pi0 I also tried to migrate my project to version 1.0 but I failed so far. I am using apollo-client instead of vue-apollo, because the ssr documentation was not complete, when I started building my app.
Like others here did as well, I imported the client instance from the
My apollo.js plugin file looks like this:

let hostUrl = __API__

export default ({app}) => {
  var networkInterface = createNetworkInterface({
    uri: hostUrl + '/graphql',
    transportBatching: true,
    opts: {
      credentials: 'same-origin'
    }
  })

  let apolloClient = new ApolloClient({
    networkInterface: networkInterface
  })

   networkInterface.use([{
      applyMiddleware (req, next) {
         // auth stuff
         next()
      }
  }])
  app.apolloClient = app.$apolloClient = apolloClient
...
}

From what I understood, the documentation implies that this plugin snippet should provide a global option to use this.$apolloClient inside any of my components. Well, I can at least access it in asyncData ({app}) which is nice and everything is rendered as expected, but where I need it even more is on client-side reactively calling queries from inside the components and this is not working. Since I can not import it directly anymore, I have no idea what to do at that point.
Maybe I could put it into my store, but this seems like a dirty patch to me.
Or did I misunderstand something from the examples?
I have been using 1.0-alpha4

@tillkolter here is a small repo as a follow up on vuex apollo and vue-apollo: https://github.com/PierBover/vuex-apollo-example-project
Maybe it helps, I'm also thinking of moving away from vue-apollo and use the vuex approach

@dohomi I also use your suggested pattern in my app. I must admit not consistently, but I do use it in a lot of cases exactly like that. The problem with your posted solution is, that it wouldn't work with the suggested pattern for Nuxt 1.0 if you want to explicitly make apollo.js a plugin. Maybe it should be treated as a plugin at all? I have a couple of types in my schema which are only resolved if the user is authenticated that why it is convenient to have its initialisation inside some instance connected hook to connect the authentication middleware. I must admit I used this pattern mostly because I wanted to use vue-cookie (like this.$cookie). Dont know if I should skip the plugin approach now and handle Apollo and cookies the Vanilla way, but I was hoping to find an "official" recommendation on that.

You guys are killing me.  As a new nuxt user, I naively ran yarn add nuxt (per the docs), which gave me the latest (alpha.4).  The docs are written for 0.10.6, and the examples are apparently current (leaving the user scratching their head as to the reason why).  The release docs are lacking things like the removal of injectAs and the store process is now different.  If you're lucky, you'll find this issue thread, which provides some insight as to what's going on.
At minimum, update the docs to tell the user to install 0.10.6 so you can roll out experimental prereleases without causing confusion.  Not everyone has been following Nuxt from day-1, and reading through every commit to piece together the differences between the docs and the code.

@bjunc Apologies for any inconveniences.  First docs are indicating are based on 0.10.7 and alpha tagged releases started for more advanced users that can find out this changes quickly and getting feed back about final release. Next release would be probably Beta tagged and comes with docs with short delay. Anyway feel free asking questions, Our opensource community always tries it's best answer this questions in best manner as possible :)

Is it possible NOT to make alpha packages as default-latest packages?
I mean... why npm install gives me alpha version which is broken?
Shouldn't alpha version be optional?

I'm not an NPM expert, but I believe it is possible by using tags (not latest).  So for instance, if you wanted to install the alpha prerelease, you would run npm install nuxt@alpha.  It appears though that the alpha releases are being treated as the latest.
My request is more simple.  Just explicitly put the version number in the installation guide that matches up with the version the documentation is for, and don't sprinkle prerelease examples in.
Currently, the doc pages say VERSION 0.10.6.  So in my opinion, there shouldn't be any examples of alpha releases in there, and the NPM install should explicitly target 0.10.6.
By the way, I think Nuxt is great – I was just annoyed since I spent hours second guessing myself before I found this thread and realized the docs weren't for the version being pushed out via npm install.

"It appears though that the alpha releases are being treated as the latest." - EXACTLY
It is pretty natural to run "npm install" on given official examples and expect that they will work... :)

Me too:
plugins/axios.js
import store from '~store'
import router from '~router'

in interceptors got router/store on undefined

I would like to access state of store instance
see:  https://nuxtjs.org/guide/directory-structure/#aliases
import store from '~store' // => undefined
const store = require('~store') // => { createStore: [Getter] }

both on above returned unexpected thing instead of store instance.
for some reason, I dont want to access state at page component or plugin, any idea?

@pi0 @Atinux I would like to suggest that you guys keep release notes in a simple CHANGELOG.md. Its a very well known place and you could add the release notes for each of the alpha releases as well. You would get more early adopters and testers - like me :) - on board. Thanks!

@pi0 are there any news about accessing plugins from within stores?

@pi0 How to customize axios ? I want to use an interceptor in the plugin

Why was this issue closed? 1.0 is still in the release candidate phase.

@alexchopin this should not be closed. The issues are still not resolved

authors: Etheryte John0x LowM4N MJ6174 SzHeJason bjunc dohomi hookszhang johnlindquist juliojerrick lewebsimple lukasborawski ndarilek pi0 tillkolter uptownhr w550 yfxie


text:
page:start hook doesn't work on browser page reload

Environment
Nuxi 3.0.0
RootDir: /home/projects/nuxt-starter-ir6yuz
Nuxt project info:

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager:  npm@7.17.0
Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-ir6yuz?file=plugins/hooks.js
Describe the bug
"page:start" hook is not called on page reload.
If I navigate to the other page, it does work, but not when I reload a page in the browser.

I would expect it to be called during the page reload.
Additional context
No response
Logs
No response

This isn't a bug - this is expected behaviour, because by the time the page arrives from the server the page has already been loaded (specifically, suspense is not triggered in this situation).
However, if you have a desired use-case, please feel free to open a feature request with more details about what you want to do and what you're trying.

repo: nuxt/nuxt


text:
Inlined style are not minified

Environment

Operating System: Linux
Node Version:     v16.20.0
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager:  npm@9.4.2
Builder:          vite
User Config:      app, runtimeConfig, modules, css, nitro, content, unocss, site, sitemap, routeRules, devtools
Runtime Modules:  @nuxt/content@2.7.2, @vueuse/nuxt@10.3.0, @unocss/nuxt@0.55.3, nuxt-simple-robots@3.1.1, nuxt-simple-sitemap@3.2.5, nuxt-schema-org@2.2.0, @nuxthq/studio@0.13.4, @nuxtjs/plausible@0.2.1
Build Modules:    -

Reproduction
https://stackblitz.com/github/unjs/website?file=README.md
Describe the bug
Hello,
I don't know how to create a smaller reproduction of this issue.
You can read more in this issue https://github.com/unjs/website/issues/89
Additional context
No response
Logs
No response

Checked and I can't reproduce with a new Nuxt project. Would you see if you can pare down the example to the minimum level to cause this issue? 🙏

No reproduction so far, closing here ☺
@Barbapapazes (or anyone else who might experience a similar issue) If you can provide a running repro, please comment here 👍🏻

authors: Barbapapazes danielroe manniL


text:
Uncaught (in promise) non-precached-url: non-precached-url :: [{"url":"/"}]

Environment

Node Version:     v21.4.0
Nuxt Version:     3.8.2
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager:  pnpm@8.12.1
Builder:          -
User Config:      telemetry, srcDir, app, extends, modules, appConfig, runtimeConfig, vite, css, postcss, colorMode, device, image, content, pwa, robots, sitemap, site
Runtime Modules:  @nuxtjs/robots@3.0.0, @nuxtjs/color-mode@3.3.2, @nuxtjs/fontaine@0.4.1, @nuxtjs/device@3.1.1, @nuxt/content@2.8.2, @nuxt/image@1.1.0, @vueuse/nuxt@10.7.0, @vite-pwa/nuxt@0.3.5, nuxt-typed-router@3.5.0, nuxt-svgo@3.7.0, nuxt-simple-sitemap@4.1.17, nuxt-schema-org@3.2.3, nuxt-lodash@2.5.3
Build Modules:    -

Reproduction
Just see in console. There may be an error in the workbox.
Describe the bug
Inside console have error:
workbox-cd63daf5.js:1 Uncaught (in promise) non-precached-url: non-precached-url :: [{"url":"/"}]
    at O.createHandlerBoundToURL (https://wokalek.ru/workbox-cd63daf5.js:1:13245)
    at Object.createHandlerBoundToURL (https://wokalek.ru/workbox-cd63daf5.js:1:14828)
    at https://wokalek.ru/sw.js:1:1025
    at https://wokalek.ru/sw.js:1:565

Appears once and does not occur a second time after the page is reloaded. But even a single appearance affects SEO.
Additional context
No response
Logs
No response

Uncaught (in promise) bad-precaching-response: bad-precaching-response :: [{"url":"https://apnabijjnes.com/200","status":404}]

Had the same issue. This helped:
https://github.com/vite-pwa/nuxt/issues/53#issuecomment-1615266204

https://github.com/vite-pwa/vite-plugin-pwa/issues/731

authors: desaisoftwaree maxflex meliceanu wokalek


text:
fix(nuxt): stringify cookie values before broadcasting them

🔗 Linked issue
https://github.com/nuxt/nuxt/issues/21651

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[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)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Resolves #21651 by preparing the cookie value for the structuredClone that's used by BroadcastChannel.postMessage.
It does this simply by cloning the value which might potentially hold nested Refs. toRaw unfortunately only applies to the root Ref, not to any nested Refs.

📝 Checklist

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

This PR will be squashed right? I'd force push to avoid the little commits, if not ;-)

Yes, the pr will be squashed. I guess I'm thinking that the encoder has to produce a string to save the cookie. (It won't be undefined as we have defaults.)

Thank you ❤

@danielroe I noticed you removed the ternary. This could theoretically lead to encode or decode being undefined. {...defaults, ..._opts }, unlike defu overwrites when a key is set to undefined.
Not sure if thats something this should really worry about as it would clearly be the users fault, but it's theoretically possible, so I wanted to mention it :)

Ah, you're right. I initially thought it would error if the user did that, but I think implementation in cookie-es would actually just fallback to encodeURIComponent directly.
I think this is likely an edge case but if you want to, we could also cover this scenario. I just don't want to add too much runtime code to cover this scenario.

Has this actually been merged? I'm still facing the issue on the latest nuxt release:
DOMException: Failed to execute 'postMessage' on 'BroadcastChannel': #<Object> could not be cloned.
    at SupabaseAuthClient._notifyAllSubscribers (http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/chunk-A274CJAX.js?v=fac2f4d6:2156:31)
    at SupabaseAuthClient._recoverAndRefresh (http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/chunk-A274CJAX.js?v=fac2f4d6:2101:20)
    at async SupabaseAuthClient._initialize (http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/chunk-A274CJAX.js?v=fac2f4d6:987:7)
    at async http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/chunk-A274CJAX.js?v=fac2f4d6:950:16
_recoverAndRefresh @ chunk-A274CJAX.js?v=fac2f4d6:2105
await in _recoverAndRefresh (async)
_initialize @ chunk-A274CJAX.js?v=fac2f4d6:987
await in _initialize (async)

It was released in Nuxt 3.8. Are you sure the log you linked is related to this code, and not another issue in the supabase module?

authors: Aietes danielroe hendrikheil


text:
Unable to select "n" as an option in participating

I've never used Nuxt before. This is my first time, and when running npm install, it's asking me to participate, but if I type n, it just keeps asking me.

oh, apparently after typing n I just had to hit enter... So I guess the issue here is just the UX of why it keeps repeating the prompt and less of it just not working.. :sweat_smile:

I think that might be an issue within nuxi... cc: @pi0

Does not work with Y either.... but hit Enter and "No" is the current selected response

I had the same problem, thank you for sharing the solution!

This should be resolved in the latest release via https://github.com/nuxt/telemetry/pull/103

authors: MissShim danielroe jwoertink matiasperrone

repo: nuxt/telemetry


text:
[FEA]: (Work in Progress) Add c++ level 'DataManager', and high level python 'PayloadManager' objects.

Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
This feature will support three primary goals:

Seamlessly support existing ControlMessage use cases, with no performance degradation.
Introduce new c++ DataRecordManager object which is responsible for CRUD operations on DataRecord objects providing the same basic CRUD interface for a specific type of backing device.
Introduce new PayloadManager object which will take the place of the existing ControlMessage payload; this class will be responsible for keeping track of stored object metadata.

Describe your ideal solution
Pseudocode
Data Manager Object
Management Object
class DataManager {
public:
  // Constructors & Destructors
  DataManager();
  ~DataManager();

  // CRUD Operations
  bool Create(const std::string& key, const std::vector<uint8_t>& data, const std::string& type);
  bool Read(const std::string& key, std::vector<uint8_t>& data_out);
  bool Update(const std::string& key, const std::vector<uint8_t>& new_data);
  bool Delete(const std::string& key);

private:
  std::unordered_map<std::string, std::unique_ptr<DataRecord>> data_map_;
};

Base DataRecord class
class DataRecord {
public:
  virtual ~DataRecordFragment() = default;
  virtual bool Create(const std::vector<uint8_t>& data) = 0;
  virtual bool Read(std::vector<uint8_t>& data_out) = 0;
  virtual bool Update(const std::vector<uint8_t>& new_data) = 0;
  virtual bool Delete() = 0;
};

Derived in-memory class
class MemoryRecord : public DataRecord {
public:
  bool Create(const std::vector<uint8_t>& data) override;
  bool Read(std::vector<uint8_t>& data_out) override;
  bool Update(const std::vector<uint8_t>& new_data) override;
  bool Delete() override;

private:
  std::vector<uint8_t> data_;
};

Derived on-disk record class
class DiskRecord : public DataRecord {
public:
  bool Create(const std::vector<uint8_t>& data) override;
  bool Read(std::vector<uint8_t>& data_out) override;
  bool Update(const std::vector<uint8_t>& new_data) override;
  bool Delete() override;
private:
 std::string m_file_path;
};

Payload Manager Object
This example assumes we're working with DataFrames, this does not have to be the case long term, but serves to illustrate the process.
class DataFragment:
    def __init__(self, data_manager, ...):
        self._cached_df = None  # Cached DataFrame for this object
        self._data_manager = data_manager  # Reference to the C++ DataManager
        self._lock = Lock()  # Lock for thread safety

    def create(self):
        # Perform create operation
        # Use self._data_manager to perform byte-level CRUD
        pass

    def read(self):
        # Perform read operation
        # Use self._data_manager to perform byte-level CRUD
        pass

    def update(self):
        # Perform update operation
        # Use self._data_manager to perform byte-level CRUD
        pass

    def delete(self):
        # Perform delete operation
        # Use self._data_manager to perform byte-level CRUD
        pass

class DataFragmentSet:
    def __init__(self):
        self.fragments = []  # List to hold DataFragment objects
        self.fragment_sizes = []  # List to hold the sizes of each DataFragment
        self.total_size = 0  # Total size of all DataFragments in the set

    def add_fragment(self, fragment):
        ...

    def remove_fragment(self, fragment):
        ...

class PayloadManager:
    def __init__(self):
        self.data_record_manager = DataRecordManager()  # Reference to C++ DataRecordManager
        self.data_record_sets = {}

    def _create_record_set(data_object, storage_type):
        # ... If (storage_type) == reference, we just store the object reference.
        # ... fragment, collect metadata, and persist to backing store
        return DataRecordSet(...)

    def _gather(self, data_object_id, row_offset, row_count):
         # ... collect object fragments and return as a list
         return fragment_list

    def create(self, data_object, data_object_id=None, storage_type="in_memory"):
          # ... Validation
          # ... Create in backing store
          self._data_record_sets[data_object_id] = self._create_record_set(data_object)

          return data_object_id

    @contextmanager
    def read_mutable(self, data_object_id, row_offset, row_count):
        fragments = self._gather(data_object_id, row_offset, row_count)
        # Lock fragments, create concated DataFrame, cache and yield it.
        yield df
        # Synchronize changes back to DataFragments/DataFragmentSets and backing storage.
        self.update(data_object_id, df, row_offset, row_count, ...)

    def read(self, object_id, row_offset, row_count):
        fragment = self._gather(object_id, row_offset, row_count)
        # Lock fragments, create concated DataFrame, and cache it
        return df.copy_on_write()  # Return a copy-on-write DataFrame

    def update(self, data_object_id, row_offset, row_count):
        object_id_set = self._gather(data_object_id, row_offset, row_count)

        # ... Update stored objects ... this may result in re-balancing
        return data_object_id

    def delete(self, data_object_id):
        # ... Delete from local cache
        # ... Delete from backing store

Additional context
Example use case(s)
Suppose we take our existing ControlMessage object and update it to use our PayloadManager structure.
class ControlMessage
{
  public:
    ...
  private:
    std::shared_ptr<PayloadManager> m_payload_manager{nullptr};
}

Single object payload with no backing medium -- we don't need to supply a data_object_id
# Read a copy of the allocated DataFrame
df = control_message.payload().read()

# modify df, ControlMessage owned DataFrame is unaffected.
do_work_on_df(df)

# Obtain a reference to the mutable DataFrame owned by the ControlMessage
with control_message.payload().read_mutable() as df:
    # modify df, ControlMessage owned immediately reflects the modifications
    do_work_on_df(df)

    # on __exit__, nothing happens because df has no backing medium

Single object payload with a backing medium -- we don't need to supply a data_object_id
# Read a copy of the allocated DataFrame
df = control_message.payload().read()

# modify df, ControlMessage owned DataFrame is unaffected.
do_work_on_df(df)

# Obtain a reference to the mutable DataFrame owned by the ControlMessage
with control_message.payload().read_mutable() as df:
    # modify df, ControlMessage owned immediately reflects the modifications
    do_work_on_df(df)

    # on __exit__, all transactional changes on df will be propagated to the backing store.
    # This will likely need to be restricted in various ways to avoid un-necessary complexity.

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I have searched the open feature requests and have found no duplicates for this feature request

I think i understand how it would translate, but I'd really like to see an example that's framed around a stage, specifically the map operation of the stage (where by "map" I mean self.process_message in mrc.operators.map(self.process_message))).

@cwharris I think I might need a bit more context on your question. In the context of usage in a stage, here is a snippet from the dfp_training code, and how it would be adapted to produce the same behavior as before:
Before
        while (control_message.has_task("training")):
            control_message.remove_task("training")

            user_id = control_message.get_metadata("user_id")
            message_meta = control_message.payload()

            with message_meta.mutable_dataframe() as dfm:
                final_df = dfm.to_pandas()

            model = AutoEncoder(**model_kwargs)

            # Only train on the feature columns
            train_df = final_df[final_df.columns.intersection(feature_columns)]
            model.fit(train_df)

After
        while (control_message.has_task("training")):
            control_message.remove_task("training")

            user_id = control_message.get_metadata("user_id")
            final_df = control_message.payload().read()

            model = AutoEncoder(**model_kwargs)

            # Only train on the feature columns
            train_df = final_df[final_df.columns.intersection(feature_column s)]
            model.fit(train_df)

In the context of having a very large, backed data source, something like this would probably be more appropriate:
After
        while (control_message.has_task("training")):
            control_message.remove_task("training")

            user_id = control_message.get_metadata("user_id")
            df_loader = control_message.payload().as_data_loader(feature_columns) # Note, this isn't in the pseudo code.

            model = AutoEncoder(**model_kwargs)

            # Only train on the feature columns
            model.fit(df_loader)

Question: Since reading/writing might require IO, would it be beneficial to have async versions of the CRUD operations? On the C++ side, I imagine we'd release the gil. That allows other threads to continue processing, but without an async API in Python, we're blocking the current thread from reading more messages while any CRUD is in-flight.

@cwharris Yes, for most operations we'll likely want to drop the GIL or perform them asynchronously. I won't say this is 100% true, because for some record managers, we may utilize something like fsspec via pybind for the initial implementation.
In the context of a python call, we should see other python threads have a chance to grab the GIL and start executing as soon as we drop it in the c++ function. Similarly, when the c++ function issues a syscall for something like a file or network read, we should see it yield as well and let some other thread execute.
If I'm understanding the context correctly, the only thing we're likely to be blocked on is processing more messages within the current python node; I don't know of any current situations where this would be a problem.

repo: nv-morpheus/Morpheus


text:
Forward-merge branch-23.01 to branch-23.03

Forward-merge triggered by push to branch-23.01 that creates a PR to keep branch-23.03 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge.

SUCCESS - forward-merge complete.


text:
Можно ли реализовать общее правило, исправляющее раскладку клавиатуры?

Для примера:
"св юю" --> "cd .."
"ды -дф" --> "ls -la"
Я сделал несколько правил для самых моих популярных опечаток в раскладке.
Но хочется общее красивое))

В 1.16+ должно работать из коробки.

Use kdbb for remember language per windows

@nvbn Агонь, пошел тестить) :beer:

It's works, thx!

authors: klinkin nvbn platinumthinker

repo: nvbn/thefuck


text:
🛑 NVIDIA AI Enterprise Hub is down

In c815bbf, 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 c077871.

repo: nvgsg/lab-upptime


text:
🛑 Kubeflow ML Platform is down

In 3583818, 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 8f3c309.


text:
Upgrade boltons.fileutils.AtomicSaver

Hi there! I noticed that you were using the boltons atomic file saving feature. I just wanted to let you know that there have been some recent improvements to cross-platform functionality and corner-case behavior and that you might want to re-vendor the code. There are a couple API improvements, but nothing that would affect your code; it should be 100% drop-in.
Let me know if you have any questions! Thanks for using boltons!

Thanks @mahmoud, I did upgrade this back when you reported in August, but I forgot to thank you for it and close this ticket :)
Btw, do you have any idea if this should be fixed in AtomicSaver? I think it'd be a nice little corner case to fix generically: #268

Agreed! The older version could have done a better job, and I think the current design does a better job than I had originally hoped. I replied over on the other thread; I was unable to reproduce that issue, so I'm hoping it's just a matter of environment or permissions getting copied over from an existing file.

authors: mahmoud nvie

repo: nvie/pip-tools


text:
新安装的kickstartnvim，代码补全按回车会直接换行

Describe the bug

第一次使用 nvim 。新安装的 kickstartnvim ，代码补全按回车会直接换行，应该是默认的 lsp ，启动了 neo-tree 和 autopairs
To Reproduce

输入 a
会出现代码提示
按回车就会换行

https://github.com/user-attachments/assets/9866b326-8e28-4375-8906-5a932d9d1e0c
Desktop

OS: Windows
Terminal: cmd/powershell

Neovim Version

NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1713484068
Run "nvim -V1 -v" for more info

If I understand well you are complaining about the default "accept autocompletion" keymap not being tab or enter ? (google translate is not that efficient here)
You can find and edit the nvim-cmp keymaps here :
https://github.com/nvim-lua/kickstart.nvim/blob/8d1ef972bc32faa86fee21a57f9033b41f612ebb/init.lua#L775-L822

Sorry, my English is bad.
Thanks for your reply, I think Google Translate is right.
I don't know why the video won't play, I can play it yesterday.
Your reply is solved my problem.
I'm noob, and very very very thank you!!!


text:
[Cross-Plugins] Cannot work with session plugin projections.nvim

As title. After restoring the session, some empty buffer(i.e. [No Name]) that is nonmodifiable, filetype neo-tree, buftype nofile causing error on :Neotree toggle focus:
Error executing vim.schedule lua callback: .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:874: Failed to rename buffer
stack traceback:
        [C]: in function 'nvim_buf_set_name'
        .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:874: in function 'create_window'
        .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:1013: in function 'draw'
        .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:1151: in function 'show_nodes'
        ...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:95: in function 'render_context'
        ...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:118: in function <...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:117>

reported there too https://github.com/GnikDroy/projections.nvim/issues/4. This is probably a consequence of #633

In any session plugin, Neo-tree windows/buffers need to be excluded from being saved.

@cseickel Yes, I know that. That plugin provides me a store_hooks field in its setup. But the problem is that I have tried calling:
store_hooks = {
  pre = function () vim.cmd('tabd Neotree ') end,
  post = function () require 'neo-tree.sources.manager'.close_all() end,
},

I still cannot close the neo-tree "window(s)". Notice that the neo-tree buffer did get closed, but I said "window(s)" because of the way of neo-tree trying to "replace/occupy" another window #633.

I just found that problem on that plugin. Sorry for my misunderstood. It's related to the usage of switcher. Let me close this issue for now.

authors: cseickel nyngwang


text:
feat(zig): update queries to parser update

See https://github.com/nvim-treesitter/nvim-treesitter/pull/7097

nice


text:
Hover Doc does not disappear in tsx

Describe the bug
In tsx or ts files, Hover Doc does not disappear.

Steps to reproduce
vim.keymap.set('n', 'K', '<Cmd>Lspsaga hover_doc<CR>')
Expected behavior
When my cursor moved, the Hover Doc disappeared.
Neovim version (nvim -v)
0.9.0
lspsaga commit
lastest
Terminal name/version
term2

IDK but before have same issue then he tell me the reason is typescript.nvim

I'm experiencing the same issue, I can only close hover_doc by clicking with mouse first then :q. @nbili did you find the fix maybe? Thanks!

can you reproduce it with a min config ?

I have this issue, but it seems to be caused by tsconfig.json, not by any vim plugins. TS sample:
export interface Repro {
  /**
   * minimal repro
   */
  minimal: number
}

It works fine without tsconfig.json. But now put in the following tsconfig.json:
{
  "compilerOptions": {
    "target": "es6",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules", "services"]
}

Then this issue will repro (press "K" on minimal)
I removed all my nvim config and all but the following plugins:
lspsaga.nvim
nvim-lspconfig
nvim-treesitter
nvim-web-devicons

and config:
local keymap = vim.keymap.set
require("lspsaga").setup({})
keymap("n", "K", "<cmd>Lspsaga hover_doc<CR>")

I'll try to see if I can trim down the tsconfig.json to find the problematic line.

I am not sure you run it with clean flag . nvim --clean - u min.lua a.ts . I can't reproduce.
min.lua
vim.opt.rtp:append('~/Workspace/lspsaga.nvim')
vim.opt.rtp:append('~/Workspace/nvim-lspconfig')
vim.opt.rtp:append('~/.local/share/nvim/lazy/nvim-treesitter/')
require('nvim-treesitter').setup({})

local lspconfig =require('lspconfig')
lspconfig.tsserver.setup({})

local keymap = vim.keymap.set
require("lspsaga").setup({})
keymap("n", "K", "<cmd>Lspsaga hover_doc<CR>")

give it a test

^Using those steps I was able to isolate it to two changes from your min.lua
Add, after
lspconfig.tsserver.setup({})

this line:
lspconfig.custom_elements_ls.setup({})

then it repros.
Maybe there is something wrong with custom_elements_ls language server. It's not too important to me, so I can just disable it :+1:. Hopefully this helps others

So I think what's happening is when you have two language servers responding, hover_doc will open 2 hover windows and close only one.

okay add that line reproduced.

oh I think I know what happen. two servers both have response

as a trace I will create a new issue for this and fix in next version

authors: glepnir jovanovicbogdan llllvvuu nbili


text:
Support --no-build option in serve target

Support --no-build option in serve target. If we know code has already been built, there is no point in trying to build it again before serving. But currently there is no way to disable that.
serve target should support noBuild option to pass --no-build flag to dotnet run, just as test target does.
dotnet run --help
Description:
  .NET Run Command

Usage:
  dotnet run [<applicationArguments>...] [options]

Arguments:
  <applicationArguments>  Arguments passed to the application that is being run. []

Options:
  -c, --configuration <CONFIGURATION>     The configuration to run for. The default for most projects is 'Debug'.
  -f, --framework <FRAMEWORK>             The target framework to run for. The target framework must also be specified in the project file.
  -r, --runtime <RUNTIME_IDENTIFIER>      The target runtime to run for.
  --project <project>                     The path to the project file to run (defaults to the current directory if there is only one project).
  -p, --property <property>               Properties to be passed to MSBuild.
  -lp, --launch-profile <launch-profile>  The name of the launch profile (if any) to use when launching the application.
  --no-launch-profile                     Do not attempt to use launchSettings.json to configure the application.
  --no-build                              Do not build the project before running. Implies --no-restore.
  --interactive                           Allows the command to stop and wait for user input or action (for example to complete authentication).
  --no-restore                            Do not restore the project before building.
  --sc, --self-contained                  Publish the .NET runtime with your application so the runtime doesn't need to be installed on the target machine.
                                          The default is 'false.' However, when targeting .NET 7 or lower, the default is 'true' if a runtime identifier is specified.
  --no-self-contained                     Publish your application as a framework dependent application. A compatible .NET runtime must be installed on the target machine to run your application.
  -v, --verbosity <LEVEL>                 Set the MSBuild verbosity level. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].
  -a, --arch <ARCH>                       The target architecture.
  --os <OS>                               The target operating system.
  --disable-build-servers                 Force the command to ignore any persistent build servers.
  -?, -h, --help                          Show command line help.

Note, is is actually possible if you define serve target like this:
        "serve": {
          "targetName": "serve",
          "dependsOn": [],
          "cache": false,
          "options": {
            "watch": false,
            "configuration": "Debug",
            "no-build": true
          },
          "configurations": {
            "production": {
              "configuration": "Release"
            }
          }
        }

Note addition of "no-build": true option. This actually passes through to the dotnet run command. But this is something of an undocumented hack as there is no no-build option documented, and if it were to be supported properly, the option should be noBuild.

repo: nx-dotnet/nx-dotnet


text:
Add generator option for standalone projects

Add a new option to the app, lib, and test generators to build standalone project.json files instead of placing all configuration in workspace.json. Update the local workspace to use the new standalone project configurations.
Resolves #70

@bcallaghan-et  Looking into failing tests, to fix nx-ghpages:test you need to add the following:
import * as fs from 'fs';

jest.mock('fs', () => ({
  ...(jest.requireActual('fs') as typeof fs),
  stat: (path: string, cb: (err: unknown, stats: unknown) => void) =>
    cb(null, {}),
}));

@AgentEnder The e2e tests fail locally as well. Do you have any guidance why yarn would fail, or why @nx-dotnet/core/package.json can't be found?

Hey, yeah. Make sure to run the e2e with npm run e2e or yarn e2e instead of through Nx.

I tried yarn e2e and that produced the same errors.

authors: AgentEnder bcallaghan-et


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in eadb54d.

repo: nxvvvv/uptime


text:
🛑 Harmony Bot Website is down

In 297a639, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 7a23bf9.


text:
Add marvin's EncodeProtoRequest function to server/kit

https://godoc.org/github.com/NYTimes/marvin#EncodeProtoRequest
This is needed for an app updating from GAE 1.9.

This actually exists within go-kit now: https://godoc.org/github.com/go-kit/kit/transport/http/proto#EncodeProtoRequest
It had some issues about not being tagged a while ago, but I haven't checked in a while.

Nice! It has been tagged! https://github.com/go-kit/kit/releases/tag/v0.9.0
Mind giving it a shot and closing this if all works out?

I have used the go-kit method without a problem, not sure if we want to have parity between gizmo and marvin though

Oh woops, didn't check there. It works for me. Thanks

I'm making some dep updates right now for gizmo, ill see if i can bring in the latest go-kit too.

authors: brianfoshee jprobinson matzika

repo: nytimes/gizmo


text:
readme change so we can tag a new release

We need a new, unique git hash to get our build working again. Hopefully it is also a useful addition to the readme.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #129   +/-   ##
=======================================
  Coverage   68.71%   68.71%
=======================================
  Files           7        7
  Lines         537      537
=======================================
  Hits          369      369
  Misses        151      151
  Partials       17       17

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 f14eff8...a127ae7. Read the comment docs.

authors: codecov-io esonderegger

repo: nytimes/video-captions-api


text:
Add Swagger annotations in 'UPDATE'

As a user
I need a UPDATE Swagger Docs
So that  we can use the API
Assumptions:

We would use Swagger
update update_promotions under the PromotionResource #118  in the routes.py
add expect with promotion_model
add marshal_with
add 404 and 400 descriptions in the response

Acceptance Criteria:
Given the /apidocs/
When we try to access PUT /promotions/{promotion_id} in the doc
Then we can see Parameters( promotion_model) and Responses code(404 and 400), and Responses 200 with response json values

When we send UPDATE request(Try it out) with all requirement parameters by following the doc
Then I can get code 200 and the response as the doc said
And I can see the updated promotion (e.g., by using LIST)

When we send UPDATE request(Try it out) with existing ID but NOT all requirement parameters by following the doc
(e.g., request body does not have "start_date")
Then I can get code 400
And I see the promotion is not updated (e.g., by using LIST)

When we send UPDATE request(Try it out) with NOT existing ID
Then I can get code 404

Given update_promotions function in PromotionResource Class
Then swagger annotations exist

We can see all response codes we need, and it worked from /apidocs Try it out !


text:
chore(main): release 0.9.1

:robot: I have created a release beep boop
0.9.1 (2024-12-10)
Bug Fixes

bump nanoid from 3.3.6 to 3.3.8 (#632) (e46a8f6)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.9.1
:sunflower:

repo: nzdjb/static-site-generator


text:
(A11y severity 3) Remove redundancy from search box

The search box in the top right of all pages has a hidden <label>, an aria-label, and title attribute that all label the field. This causes lots of redundant information to be presented to screen readers (title is read by some screen readers in addition to labels). Remove the redundant aria-label and title.

assigning to @nicolaasmatthijs for review

Finished review. Back to @sathomas

We could remove the hidden label instead of the title attribute, but some screen readers won't read title text, so that would make the search inaccessible to those users. Alternatively we could use the Bootstrap tooltip component instead of the title attribute. @nicolaasmatthijs would you like me to update the PR with a Bootstrap implementation to check out, or would you rather keep it simple and delete the label?

@sathomas : Would you mind reaching out to WebAIM to check if it is acceptable to have both a hidden label and a title attribute for tooltip purposes? I'm assuming removing the hidden label is not going to be acceptable, but it might be worth checking with them.

It turns out that things aren't so clear cut. There's an extended discussion of this problem on the WebAIM mailing list, but the conclusion seems to be that it's okay to use a title instead of a <label> if you want the tooltip.
Corroboration from WebAIM Guidelines:

If a form field has a title attribute, but no , the screen reader will read the title as if it were a label.

Further support from The Paciello Group

Always provide an explicitly associated text label for a text field, using either the label element or the title attribute.

It seems like the biggest disadvantage to using title is that sighted keyboard-only users will never see it. They will, of course, see the magnifying glass icon, but I suppose there might be some cultures in which that iconography isn't clear. If we want to address that concern, we could add a placeholder attribute to the field.
I've updated the PR by removing the <label> element instead of the title attribute. Back to @nicolaasmatthijs for thoughts, review, etc.

Looks good. Merged.

authors: nicolaasmatthijs sathomas


text:
Add folders Create folder and Upload File section to the library

For a more straightforward understanding of the interface, it will be necessary to include a section where the user can immediately click a button to add:

a new folder/label
a new file

This action can be accessed both from the sidebar (Upload or Create) and from within the library.

Mockups to show the exact structure to be added soon

repo: oaeproject/Cake


text:
Horizontal REPL / Vertical Split

Hello Zach, I bought Nightcode from AppStore, how do I split the REPL side by side with the editor vertically??
Thanks

You can edit nightcode.edn and save it to ~/Library/Containers/info.oakleaf.nightcode/Data/nightcode.edn. That's the special home directory for the MAS version of Nightcode.

Let me know if that doesn't work...I haven't tried it =)

Hi Zach, thanks. I have tried it, it doesn't work. :((

OK I'll take a look soon.

Sorry for the delay. I just tested it and it does indeed work. Please make sure that you put the file in the right place, and that you edited it so it says :panel :horizontal.

Thanks, it does work. :+1:

authors: codxse oakes

repo: oakes/Nightcode

license: unlicense


text:
feat: reporting legacy canonical 404s to bugsnag before redirect

Description
I want a metric showing the proportion of redirects which are returned back to acorn
This change doesn't quite achieve the above, but it forwards 404s from the canonical page to bugsnag ahead of the redirect being returned. If necessary, this data could be used to cross-check the redirects being tracked by the analytics team, but it also gives us a quick and dirty way of viewing how many redirects from OWA to Acorn are occuring.
How to test

Go to https://deploy-preview-2264--oak-web-application.netlify.thenational.academy/pupils/l/video-editing-7a9a/lessons/what-is-video-c4v68d
you will be redirected to the Acorn version of the lesson
Now go to bugsnag
You should see the error reported with the title pupils::lesson-overview-legacy-canonical::getStaticProps::pupilLessonOverviewCanonical

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

authors: kimon-satan oak-machine-user

repo: oaknational/Oak-Web-Application


text:
[VL] Use a config to control coalesce batches

What changes were proposed in this pull request?
Use a config to control whether CoalesceBatches should be inserted.
How was this patch tested?
under test

@jinchengchenghh

I would remove Arrow, after shuffle write Velox RowVecter, I will remove CoalesceBatch operator

retest this please

This PR beak clickhouse backend ci @rui-mo , I will revert it.

authors: jinchengchenghh liuneng1994 rui-mo zhouyuan

repo: oap-project/gluten


text:
[GLUTEN-2139][CORE] Add default fallback reason

What changes were proposed in this pull request?
The main change in this pr is:

Make all gluten plan inherit GlutenPlan, e.g., ColumnarToRowExec, RowToColumnarExec
Then we can add default fallback reason for all vanilla SparkPlan

(Fixes: #2139)
How was this patch tested?
add test

Thanks so much for your efforts!
I just noted there are some fallback rules in TransformHintRule.scala, e.g., FallbackOnANSIMode. Is it possible to add fallback reason for them? I think it may be also helpful to users to understand why a query plan falls back. Thanks!

hi @PHILO-HE , it should has already supported. If you compile and rule current gluten main branch, then it will show:

hi @PHILO-HE , it should have already supported. If you compile and run current gluten main branch, then it will show:

Great! Thanks!

cc @zhouyuan this is for those SparkPlan which do not contain unsupport transformable tag, e.g., broadcast nested loop join

Could you please update gluten doc to tell user how to check the fallback reason in a follow-up PR? Maybe, ending part of Velox.md is a good place to document it. Thanks!

@PHILO-HE sure, I will do a followup for docs

authors: PHILO-HE ulysses-you


text:
[Draft] Evaulation Refactoring

Hi @oarriaga ,
I have started working on  #91. You will be able to see the changes in this pull request. I will inform you once I am done. Then, you can review and merge it.
Thanks,
Mohandass

Thank you Mohandass! would it be also possible to provide new unit-tests for each function?

Yes Sure Octavio. I will do it.

authors: mohanrobotics oarriaga

repo: oarriaga/paz


text:
Fix the CustomExtension example in the custom.ipynb jupyter notebook.

Fixes issue #518 .
These changes also include whatever other minor stuff came along with making a minimal change and saving the resulting notebook.

Codecov Report

Merging #520 (92903a4) into master (17170e6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #520   +/-   ##
=======================================
  Coverage   87.20%   87.20%
=======================================
  Files         153      153
  Lines       17911    17911
=======================================
  Hits        15619    15619
  Misses       2292     2292

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 17170e6...92903a4. Read the comment docs.

authors: chisholm codecov-commenter


text:
Reorganize backends to be per consensus backend

Since #1878 the backends for various services (staking, beacon, scheduler, roothash, etc.) have been made per consensus backend, so setting the consensus backend configures all of the appropriate backends.
We should also reorganize the Tendermint-based backends to live under go/tendermint and change the common.ConsensusBackend interface to include a method that returns all the (initialized) backends appropriate for that consensus backend.

While we are doing this, we should also:

Create go/consensus and move go/common/consensus stuff there.
Move go/tendermint under go/consensus/tendermint.

repo: oasislabs/oasis-core


text:
不从typora打开的文件还是单独窗口

软件很不错，但有点小问题，不从typora打开的文件还是单独窗口，并没有受到标签页管理，我习惯与使用everyting检索文件直接打开，能做下优化吗。

还有标签页切换的快捷键能优化为ctr+pgup/pgdn 吗。

@aiqyqy 感谢反馈。

这个 issue 之前已经有不少人提出来了。从原理上来说就是做不到的（除非你用的是低版本）。typora_plugin 本质是一个前端项目，Typora 并不支持插件功能。本项目的做法是通过各种黑魔法强行实现功能。使用命令行直接和后端交互，就绕开了 typora_plugin。要想实现这个功能，要么等待 Typora 官方支持，或者 Typora 官方提供插件系统。
可以做，你可以明天再来。

你这种情况或许可以绕过：写一个脚本对接 commander.js 插件。然后让 commander.js 打开文件。

@aiqyqy 你好。
1.1.1 版本已经发布，添加了快捷键 ctr+pgup/pgdn 切换标签。
因为移动了 window_tab.js 的位置，更新时需要替换整个 plugin 目录。

authors: aiqyqy obgnail


text:
newline in samples for tests leads to an error

When I write some sample in src/test/eo/org/eolang/dejump and add a newline in the end of the file it will lead to an error:
Caused by: org.eolang.parser.ParsingException: [19:4] extraneous input '\n    ' expecting {COMMENT, 'Q', 'QQ', '*', '...', '&', '$', '[', '(', '@', '^', BYTES, BOOL, STRING, INT, FLOAT, HEX, NAME, TEXT, UNTAB}: "    "

It seems when we build tests this extra newline space break parser rules and add it before $.equal-to matcher.

@Graur, Which test caused this error? In other tests there is a new line and works ok

@MikhailLipanin It was my tests and now I can't reproduce it. Maybe it was two newlines. Let's close. Thanks!

authors: Graur MikhailLipanin

repo: objectionary/dejump


text:
text.concatted implemented

https://github.com/objectionary/eo-strings/issues/44

@Graur @levBagryansky please, have a look

@yegor256 please have a look

@EugeneDar I think everybody will hate us for this name, because they used to concat. How about glued instead?

@EugeneDar chained sounds good for me

@yegor256 please have a look

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 3min)

authors: EugeneDar rultor yegor256

repo: objectionary/eo-strings


text:
the Haste package 'react-native-vector-icons'

error: bundling failed: Error: While resolving module react-native-vector-icons /Ionicons, the Haste package react-native-vector-icons was found. However the
module Ionicons could not be found within the package.

Dup of #626
it's an RN issue https://github.com/facebook/react-native/issues/17610
Will be fixed by https://github.com/facebook/react-native/pull/17672
Workaround https://github.com/oblador/react-native-vector-icons/issues/626#issuecomment-362386341

Thanks @MoOx for the helpful summary.  :)

@MoOx

Will be fixed by facebook/react-native#17672 is it permanent fix?

@mtt87 Thanks it worked for me.

@Yandamuri yes it will. Nothing is wrong in this package. It's RN repo that contains the name of this package (and it should not).

thanks @mtt87 .It works like a charm
💯

4 months later and this still isn't fixed in React Native 0.53.3.
Quick fix as others point out is to run rm ./node_modules/react-native/local-cli/core/__fixtures__/files/package.json but you'll need to do this after every fresh npm install.
So, to run this automatically, you can add it to your package.json as a postinstall script:
package.json
"scripts": {
  "postinstall": "rm ./node_modules/react-native/local-cli/core/__fixtures__/files/package.json"
}

I found the solution.Delete this file.
rm ./node_modules/react-native/local-cli/core/fixtures/files/package.json
Delete file package.json

I delete this file but error continued. :c

@13ArturBruno if on RN0.52+ you need ``rm node_modules/react-native/local-cli/core/fixtures/files/package.json`

authors: 13ArturBruno MoOx SridharAlagirisamy Yandamuri jasonc1025 joshuapinter junge68 paalex trinadhkoya

repo: oblador/react-native-vector-icons


text:
Documentation updates after adding autoloading & importing

After #10 has been merged, the documentation will need looked at.  Some of it will probably be out of date, and it could probably do with some updates to explain how the various bits fit together, and how an entire project should be structured.

Need to document autoloading, autoimporting & configuration of everything, also starting the ExUnitFixtures application.


text:
[Merge] foreskin melanocyte and melanocyte of foreskin

CL term (ID and Label)
CL_2000045 foreskin melanocyte
Reason for deprecation
Both terms are fairly similar; I don't know if there are non-skin foreskin melanocytes. In any case, at least the labels should be changed for clarity.
Term to be merged with (ID and Label)
https://www.ontobee.org/ontology/CL?iri=http://purl.obolibrary.org/obo/CL_2000045 foreskin melanocyte
https://www.ontobee.org/ontology/CL?iri=http://purl.obolibrary.org/obo/CL_2000082 melanocyte of foreskin

can someone else comment on this issue? maybe @bvarner-ebi ?
I am not really sure how merging works in CL

docs: https://oboacademy.github.io/obook/howto/merge-terms/

Hi @lubianat, thanks for the updated comment.
This was not on my radar since I saw it was assigned to you.
@shawntanzk reported that he forwarded you the documentation on how to merge. If you like, can you give it a go and provide feedback on whether or not the documentation was easy to follow? Of course, reach out if you run into issues along the way.

Sure, thanks @bvarner-ebi ! Won't be able to do it today, though; but it is on my to do list for the next CL slot on my agenda

Hi, @lubianat, checking in on this ticket.
Kindly advise if you would like help with this merge.

@bvarner-ebi thanks;
I won't be doing this merge in the near future. I cannot accurately estimate the time I'll take and how hard it will be
I might do it in the next semester, when some of my current commitments will be over

Hi @lubianat, I am checking old open tickets. Is it still in your plans to do the merge or would you like me to assign myself or another CL editor?

@aleixpuigb thanks for the ping again. I guess I fell into some rabbit hole on that and could not really complete the merge. Feel free to assign someone else (not sure if I'll be able to do it)

No problem, it will be good practice for new editors to merge terms.

authors: aleixpuigb bvarner-ebi lubianat

repo: obophenotype/cell-ontology


text:
abnormal glycogen synthesis

Add new term:
abnormal glycogen synthesis (a child of abnormal glycogen homeostasis MP:0005438)
DEF: any anomaly in the reactions and pathways involved in the formation of glycogen, a polydisperse, highly branched glucan composed of chains of D-glucose residues
SYN: abnormal glycogen anabolism
SYN: abnormal glycogen biosynthetic process
SYN: abnormal glycogen biosynthesis
SYN: abnormal	glycogen formation
SOURCE: GO:0005978
Child terms include:
decreased glycogen synthesis
DEF: any anomaly in the reactions and pathways involved in glycogen biosynthesis that results in reduced glycogen formation
SYN: impaired glycogen anabolism
SYN: impaired glycogen synthesis
SYN: impaired glycogen biosynthetic process
SYN: decreased glycogen biosynthesis
SYN: decreased glycogen formation
SYN: reduced glycogen synthesis
SYN: reduced glycogen biosynthesis
SYN: reduced glycogen formation
increased glycogen synthesis
DEF: any anomaly in the reactions and pathways involved in glycogen biosynthesis that results in increased glycogen formation
SYN: increased glycogen anabolism
SYN: increased glycogen biosynthetic process
SYN: increased glycogen biosynthesis
SYN: increased glycogen formation
SYN: enhanced glycogen synthesis
SYN: enhanced glycogen biosynthesis
SYN: enhanced glycogen formation

Added new terms:
abnormal glycogen synthesis MP:0030999
decreased glycogen synthesis MP:0031000
increased glycogen synthesis MP:0031001


text:
Node deprecation warning for Punycode

Node.js v22.2.0 documentation lists punycode as deprecated:
https://nodejs.org/api/punycode.html
However Framework uses this package:
https://github.com/observablehq/framework/blob/e4682b3afb4807f863bcd76f0858a8af0c3432a0/src/node.ts#L197
When running commands, I continually encounter this warning:
(node:42713) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

It would be great if we could find a way to avoid seeing this warning.

Framework doesn’t use punycode directly. The line you linked to is a list of Node’s built-in packages and is used for resolving node imports.
I traced the dependency to the psl library. The dependency chain is:
@observablehq/framework → jsdom@^23.2.0 → tough-cookie@^4.1.3 → psl@^1.1.33
This was fixed in https://github.com/lupomontero/psl/pull/298, but a new version of psl has not been published in two years, so it’s unclear if this will be fixed anytime soon. At any rate, the problem is not within this library, and unless we’re willing to drop the dependency on JSDOM. This may also be fixed by tough-cookie in https://github.com/salesforce/tough-cookie/pull/346, but it is waiting for a v5 release.

authors: aaronkyle mbostock

repo: observablehq/framework

license: ISC


text:
constant as part of the stdlib?

See https://beta.observablehq.com/@tmcw/interacting-with-promises-as-values - I'm trying to discuss how one uses Promises across cell boundaries. People might want to do this so they can demo a promise-based API, or for teaching JavaScript, or they might want to have more control over when Promises are resolved. One workaround is just never crossing cell boundaries: the other is a functor/constant that returns a promise.
Is there another workaround? If this is a useful pattern, is it something we should include in the runtime?

No current plans to do this, so closing.

authors: mbostock tmcw

repo: observablehq/notebook-runtime


text:
Feature: fetch HTML keywords as keywords when available.

There should be configurable support for extracting keywords from the links, such as HTML keywods meta, that are exported as obsidian tags.

This is already possible using meta variables {{meta:name:keywords}}
https://help.obsidian.md/Extending+Obsidian/Obsidian+Web+Clipper#Meta+variables

Thanks for the info, I will try it and report back.

authors: kepano tbrittoborges

repo: obsidianmd/obsidian-clipper


text:
Update netty-nio-client to 2.20.12

Updates software.amazon.awssdk:netty-nio-client from 2.18.41 to 2.20.12.
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 = "software.amazon.awssdk", artifactId = "netty-nio-client" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk", artifactId = "netty-nio-client" }
}]

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

Superseded by #248.


text:
Revise xposts internal representation

In the current version, exceptional post-conditions are represented with the type : (xsymbol * (pattern * term) list) list
This doesn't work well with exception that doesn't have any arguments. For example in:
exception E

val f : int -> int
(*@ y = f x
    raises E -> x = 42

the type checker has to fill for the pattern.
It wil linsert a tuple0 pattern, I believe because the type of E is Exn_tuple [].

After further investigation, the tuple0 is placed by the parser.
In case we have a pattern but no term (raises E _), the parser will insert a Ttrue.
I believe there are two ways to go:

either flatten the type and go for somethin along the way of (xsymbol * pattern option * term) list
add pattern for exceptions and go for (pattern * term) list which is even simpler

repo: ocaml-gospel/gospel


text:
Look up variables even if they refer to other packages

OpamPackageVar.resolve_switch only looks up variables that are in the current package (and not specifying ~package seems to make no difference), so add code to retrieve the name of the package from the variable, retrieve the package from the installed packages and look up the variable in that package.
This PR:

Fixes the problem of not resolving variables that refer to other packages
Silences the warning about unresolved variables if the variable refers to a package that is not installed.
Keeps the warning if the variable is not referring to a package and undefined OR the package is installed and is missing the definition.

Closes #45.

I don't understand why this need to be done, opam functions already do this resolving. From what I see, the issue comes from
https://github.com/ocaml-opam/opam-0install-solver/blob/b759d7c1c2f140724020f57599ead9ee394a8f7a/lib/switch_context.ml#L19-L32
From what i understand, OpamPackageVar.resolve_switch is given as argument the package that is looked at, while it should take as argument a package for which it resolves the variable.
For that was, better us OpamPackageVar.resolve, that fully handle package variables, and is more specific to filtering.

So, if I understand correctly (from https://github.com/ocaml/opam-repository/pull/23736), the warning comes when a package refers to another package's variables in the conflicts field, which shouldn't be done. So this isn't a problem, and opam-0install-solver is correct to warn about it?

Yes, I think that's a correct reading of the issue. Closing the PR as the issue was solved on the opam-repository side.

authors: Leonidas-from-XIV rjbou talex5


text:
feat: add feedback button

Kind: enhancement

Close #525

Description

Checklist

[x] Read the CONTRIBUTING.md guide and:

[x] Use Atomic Commits so each commit gathers a single logical change
[x] Use Conventional Commits regarding commit messages (needed by our release toolchain)

[ ] Add/update tests

[ ] Add/update documentation

[ ] …

Note to maintainers

Read this wiki page.
Make sure the PR has a milestone.
Assign yourself before merging.
Either do a regular merge:

for PRs containing several commits following conventional-commits,
or for PRs containing 1 commit shared with a later PR (to preserve the SHA1)

Or do a squash-merge:

for PRs containing only 1 commit (not shared with a later PR),
or for PRs containing several commits that need not be kept in the history;
→ Update the commit message header with a conventional-commit type,
→ Add a footer Close #… if a related issue exists.

Suggestion (to tweak further w.r.t. spacing)

actually the spacing looks fine now.
Two leftover tasks:

Convert draw style from black to white
Add an id <img id="learnocaml-main-feedback" src="/icons/icon_feedback.svg"> to make it possible to add an attribute title="Send Feedback", internationalized, thanks to some js_of_ocaml code.

Now, let's wait for the CI :white_check_mark:

This feature could be improved by implementing a sidebar. It would be more complex but way more elegant ! cf the google feedback option

authors: Plictox erikmd

repo: ocaml-sf/learn-ocaml


text:
Logging:  Allow node owner to decide where to log

We should allow node-owner to decide where to see/keep the logs.
Proposal:  Refactor logging module such:

have env LOG_LEVEL decide what logs are activated (no matter if NODE_ENV is production or development).  If LOG_LEVEL is not defined, then if NODE_ENV='production' -> LOG_LEVEL=info, else LOG_LEVEL=DEBUG
if env LOG_CONSOLE is True, then all logs should be displayed on the console
if env LOG_FILES is True, then all logs should be save in log fines
if env LOG_DB is True and we have noSQL db, then all logs should be saved in noSQL db

If none of LOG_CONSOLE, LOG_FILES, LOG_DB are set the we default to console
Default for casual user will be set in the yaml file (will not be set in code) would be LOG_DB: true and LOG_LEVEL: ERROR

closed on https://github.com/oceanprotocol/ocean-node/pull/553

repo: oceanprotocol/ocean-node


text:
Feature Request: handle public / private zones

Cloud DNS apis  identifies public from private zones by using a "visibility" field:
https://cloud.google.com/dns/docs/reference/v1/managedZones:
visibility | string | The zone's visibility: public zones are exposed to the  Internet, while private zones are visible only to Virtual Private Cloud  resources.           Acceptable values are:                        "private"             "public"
Today the default behaviour is to create the zone (on public side) if it does not exist.
If the zone exists internally, octodns will use the internal zone.
In case of split Horizon use case (same zone with different data ), It could be interresting to specify which zone we target.
Again, can help on testing.
Best regards,
Marc

Will throw this into the hopper, but tbh I'm building up quite a list at this point and not getting to spend a lot of time working through it. Others may get to it before I do.

authors: WhatshallIbreaktoday ross

repo: octodns/octodns-googlecloud


text:
🛑 Ahora+ (rrhh.octubre.org.ar) is down

In e55928e, Ahora+ (rrhh.octubre.org.ar) (https://rrhh.octubre.org.ar/api/health) was down:

HTTP code: 503
Response time: 773 ms

Resolved: Ahora+ (rrhh.octubre.org.ar) is back up in 1d71ca5.

repo: octubre-softlab/octubre-upptime


text:
Cleanup example pipelines

After the refastoring of the Task packaging workflows and the Pipeline building tooling the golang project pipeline was refactored, but the rest of the examples have not been refactored. this needs to be fixed

merged as part of https://github.com/ocurity/dracon/pull/184

repo: ocurity/dracon


text:
Almost done

Literals fixed, for and definition are written

license: WTFPL