text:
Allow viewing the source code of blocks

Description
Features
This PR adds an experimental view command that lets you view the source code of:

a block
a module
a custom command

Caveats

Currently, viewing individual blocks of export env is not possible -- you need to view the whole module. However, viewing export def and export def-env is possible (e.g., using `view "module-name def-name").
It shows only the block part. E.g., the def name [args...] parts will be lost.

Tests
Make sure you've run and fixed any issues with these commands:

[x] cargo fmt --all -- --check to check standard code formatting (cargo fmt --all applies these changes)
[x] cargo clippy --all --all-features -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect to check that you're using the standard code style
[x] cargo build; cargo test --all --all-features to check that all the tests pass

“View” seems very generic choice for internal source code and might conflict in the future with some actual viewing functionality. Maybe a more explicit name like “View-source” would be better?

Ahh, I like view-source, too. Reminds me of viewing source on a webpage :grinning:

authors: jntrnr kubouch vwkd

repo: nushell/engine-q


text:
Remove save button on top bar

This is to ensure user scrolls down to bottom of page (and discover test command).

Fixed in this commit 06123c10bce3f702241d53cdebbd240414f0ef9e

source: gharchive/issue

repo: nuvla/ui

license_type: permissive

license_source: github-api


text:
lose current language with path without prefix

I have a link http://localhost:3100/fr/test, if i removed fr prefix and reload, current language is return default . I want it keep current language
ex: http://localhost:3100/test reload to http://localhost:3100/fr/test

I solved this problem by
detectBrowserLanguage: {
onlyOnRoot: false // solved here
},

license: MIT


text:
Breaks not rendering when using $md.render()

Hello.  Hoping for some direction here about what I might be doing wrong.
I am using the markdownit module to render content produced from the Netlify CMS editor.  The markdown-it configuration breaks: true doesn't seem to be honored in the HTML output.  I deleted  linkify: true just to see if any of the config settings were working, and, indeed, http://bla.com stopped displaying as an anchor, so that at least that is working as expected.
Any idea why \n\n is not showing up as a
?
markdown-it docs say:

breaks - false. Set true to convert \n in paragraphs into

Thanks for your help!
nuxt.config.js
 modules: [
    '@nuxtjs/markdownit'
  ],

  // [optional] markdownit options
  // See https://github.com/markdown-it/markdown-it
  markdownit: {
    injected: true,
    preset: 'default',
    linkify: true,
    breaks: true,
    use: [
      'markdown-it-container',
      'markdown-it-attrs'
    ]
  },

stuff.json
{
  "title": "Stuff",
  "date": "2018-03-01T23:59:10.464Z",
  "body": "Some stuff is here\n\n**And a whole bunch more here!**\n\n1. stuff\n2. stuff\n3. and more stuff\nhttp://bla.com"
}

stuff.vue
<template>

{{ title }}

</template>

HTML output

Stuff

Some stuff is here

And a whole bunch more here!

stuff

stuff

and more stuff

            http://bla.com

This question is available on Nuxt.js community (#c115)

Did you find a solution yet ?

Did you have a solution? I fell into the exact same problem.

Adding CSS white-space: pre-line; to the div solves my problem.

I solved this by
add

and add global style with

repo: nuxt-community/modules

license: mit

license_source: bigquery


text:
help: Sitemap file location

📚 What are you trying to do?
This is more of a question but an actual issue right now. Hope you can help me clarify things a bit.
While playing around with the multiple sitemaps feature, I noticed that the path of every sitemap entry is generated with a loc similar to https:example.com/__sitemap__/[my-sitemap-entry].xml.
A coworker pointed out that the location or path of the sitemap should be considered when using multiple sitemaps. Under https://www.sitemaps.org/protocol.html you can read about it. Basically it says:

The location of a Sitemap file determines the set of URLs that can be included in that Sitemap. A Sitemap file located at http://example.com/catalog/sitemap.xml can include any URLs starting with http://example.com/catalog/ but can not include URLs starting with http://example.com/images/.

So my question is: Isn't this contradicting with the default behavior that multiple sitemaps will always be generated with the __sitemap__ path?
🔍 What have you tried?
No response
ℹ Additional context
No response

Hey, great question. I don't know in this instance, it's possible it does not adhere to the spec but it doesn't explicitly say about having alternative paths when using the root sitemap index file.
No search engine has an issue with it to the best of my knowledge.
The routes are setup like this due to how Nitro route matching works, we can't dynamically match routes such as <sitemap>-sitemap.xml which means we need to use a middleware that has performance overhead and other drawbacks.

Thanks for your quick reply. I also can't tell if search engines do have any issues with this. Will get back if I can find any further information on this.

I found a similar quote in the google docs:

The location of a Sitemap file determines the set of URLs that can be included in that Sitemap. A Sitemap file located at http://example.com/catalog/sitemap.xml can include any URLs starting with http://example.com/catalog/ but can not include URLs starting with http://example.com/images/.

So, if you ask me I would rather go with safe than sorry. But I don't both how to verify how google really treats sitemaps not following this rule and what consequence a rollback on your side would have.

Add the sitemap to google search console and it should tell you if there's an issues

Hey Harlan. Can we revisit this? I, too, would like to be able to control where my sitemaps live. I can create a post-build script to move them out of sitemap, but I would rather have a flag within the module config.

I am considering rolling the initial change back and allowing people to put them wherever they find appropriate, give me a couple of days to decide.

I'll avoid rolling back for now due to potential breaking changes for end users but you can easily change the multi-sitemap path using sitemapsPathPrefix and prefix your sitemaps however you like.
export default defineNuxtConfig({
   sitemap: {
      sitemapsPathPrefix: '/',
      sitemaps: {
         ['sitemap-foo']: {}
      }
   }
})

I've added this to the docs as well.

authors: harlan-zw resolutionathens toytonic

repo: nuxt-modules/sitemap


text:
Can't use Vue components in Nuxt

Hi there, I'm new to just about everything (Vue.js, Nuxt.js, webpack...) so if I'm asking this in the wrong place my apologies.
I would like to use a Vue component such as Vuebar on my app but have as yet been unable to use pretty much any component I've tried to add. I install the package via npm install --save vuebar and it appears in my package.json, then I try to import it in my default layout using
import Vuebar from 'vuebar' export default {   components: {     Vuebar } }
but when I try to use it in the default layout with <div v-bar></div> it says "failed to resolve directive: bar"
I haven't been able to get any other packages that are used in components to work either so I can't help but think I'm missing some fundamental step here, do I need to add an alias to nuxt.config.js or something like that?
Again, my apologies for the uninformed question, if this is the wrong place please feel free to delete this.

Alright as I suspected I finally came across the answer right after posting a question, my apologies, found the answers in the plugin documentation here. Somehow I didn't think that applied until I looked at it again just now. Sorry.

Thanks for your issue, I made the same mistake.


text:
A real fix for: The client-side rendered virtual DOM tree is not matching server-rendered content.

Even after loading a plugin with ssr: false and using the plugin's components wrapped around <no-ssr></no-ssr> I still get this error and the component does not load unless I change the code to trigger a hot-update then it loads. Then, after doing a refresh through the browser button, the error does not show and the component does not show either.
I have to trigger a hot-update for the component to show and that's what's interesting.

<no-ssr></no-ssr> only works for the components which although not support 'ssr' but didn't use DOM related api in initialization.
If your component uses DOM, you can use async and dynamic component. such as:
<template>
  <div>
    <component :is="asyncComp"></component>
  </div>
</template>

<script>
export default {
  data: () => ({
    asyncComp: ''
  }),
  components: {
    'example': () => {
      import('@/components/example')
    }
  },
  mounted() {
    this.asyncComp = 'example'
  }
}
</script>

authors: clarkdo nigeltiany


text:
ie9 not support find method in store.js

in store.js
const indexFilename = filenames.find((filename) => filename.includes('./index.'))
SCRIPT438: 对象不支持“find”属性或方法

See the workaround reported here:
https://github.com/nuxt/nuxt.js/issues/951


text:
Pages not automatically appearing when created while npm run dev running

Environment

Operating System: Darwin
Node Version:     v14.19.1
Nuxt Version:     3.0.0-rc.4
Package Manager:  npm@8.5.5
Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
npx nuxi init nuxt-app
cd nuxt-app
npm install
npm run dev -- -o

Add a new page into /pages folder (eg. test.vue)
In your browser visit: http://localhost:3000/test
Get a 404
Stop/Start npm run dev -- -o
In your browser visit: http://localhost:3000/test
Get the page!
Describe the bug
Any files added to /pages folder while development server is running should be reachable in the browser straight away. Instead you have to restart nuxt.
Additional context
No response
Logs
No response

any updates?

authors: craigharman lafllamme

repo: nuxt/nuxt


text:
NuxtLoadingIndicator doesn't work in Nuxt 3.2.0

Environment

Operating System: Darwin
Node Version:     v16.15.1
Nuxt Version:     3.2.0
Nitro Version:    2.2.1
Package Manager:  yarn@1.22.4
Builder:          vite
User Config:      modules, app, vite, i18n, build, runtimeConfig, telemetry
Runtime Modules:  @pinia/nuxt@0.4.6, @nuxtjs/tailwindcss@6.2.0, @nuxtjs/i18n@8.0.0-beta.7
Build Modules:    -

Reproduction

Install the latest nuxt version (3.2.0)
create at least 2 pages for navigating
Add NuxtLoadingIndicator to your app.vue file like state here

Describe the bug
When adding nuxtLoadingIndicator to app.vue it will not show up. This only happens in Nuxt version 3.2.0. In Nuxt version 3.0.0 it works fine.
Additional context
No response
Logs
No response

You can set throttle to 0. By default we only show it for transitions longer than 200ms.

I'm also experiencing this problem，but I don't understand what throttle does 。 Must be 0 or it will not take effect

I'm also experiencing this problem，but I don't understand what throttle does 。 Must be 0 or it will not take effect

throttle will surpress the indicator for given amount of millis. So according to my understanding - if the navigation ends before it (default is 200), you won't see an indicator at all

As described above.
It will always show up if you set trottle to 0.
     <NuxtLoadingIndicator :throttle="0" />

authors: AloisSeckar dadaguai-git danielroe elpeyotl


text:
The useFetch function sends 2 requests every time it is called

Environment
nodejs: v18.17.3
nuxt: v3.6.5
Reproduction
https://stackblitz.com/edit/nuxt-starter-kdgkx9
Describe the bug
my code:

When I click button “click me”, it will call function "submitForm" and the console will display:

This only outputs once "111", indicating that this function was only called once, but the network request shows this:

This request will not respond correctly because it is just a request I casually wrote to demonstrate the problem, which does not hinder the problem I want to describe because the correct request I wrote in my work will also have the same problem,and it did send two requests to my server.
It is obvious that it has made two requests, and I suspect that this issue is related to the cache of nuxt. However, using the official combination function "clearNuxtData" is not helpful. So did I make a mistake somewhere?
Thanks!
Additional context
No response
Logs
No response

From looking at your code, I think this is the expected behaviour. useFetch uses oFetch under the hood. It has built in auto-retry functionality. By default, it is 1 for GET requests.
If you changed the form submission to a POST request, it would not auto-retry.

From looking at your code, I think this is the expected behaviour. useFetch uses oFetch under the hood. It has built in auto-retry functionality. By default, it is for requests.1``GET
If you changed the form submission to a request, it would not auto-retry.POST

It turns out that's the case, I don't understand why it's designed like this.Many times we use GET requests, and repeated requests on top of this can waste server resources. Does Nuxt have a design to avoid this situation?

@FatNerdPeng Since GET requests shouldn't have a body, using a POST request to submit the form would be your best cource of action. Otherwise, you can disable the retries by setting it to 0.

What is written here is correct.
Also, when submitting a form, I'd usually resort to $fetch, because you don't want/need reactivity and want a "one-off" for the request instead.

authors: FatNerdPeng luc122c manniL


text:
when using manualChunks, get 'cannot access 'X' before initialization'

Environment
Nuxt project info:

Operating System: Windows_NT
Node Version:     v18.10.0
Nuxt Version:     3.7.3
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager:  pnpm@8.6.12
Builder:          -
User Config:      devtools, build, modules, css, sourcemap, app, vite, vue,
elementPlus, experimental
Runtime Modules:  @element-plus/nuxt@1.0.6, @nuxt/devtools@0.8.4, @unocss/nuxt@0.55.7, @vueuse/nuxt@10.4.1
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-gmvrwz-x9yx6b?file=nuxt.config.ts
Describe the bug
I'm trying to split some dependencies (for example vue) into a separate chunk.  i see error like Uncaught ReferenceError: Cannot access 'X' before initialization in console and nothing works in production build.
#20058
Additional context
No response
Logs
No response

I would think this is more of a Vite/Rollup issue than Nuxt.
In your nuxt.config.ts, you are declaring vite.build.rollupOptions.output.
Other than that, the whole application is the default generated Nuxt app, or am I missing something?

let's track in https://github.com/nuxt/nuxt/issues/21354.

authors: danielroe kingyang milos018


text:
After updating to 3.7.0 Safari < 15.4 ofetch (useFetch) fails with "TypeError: e.at is not a function" in some cases

Environment
Nuxt project info:

Operating System: Windows_NT
Node Version:     v18.19.0
Nuxt Version:     3.9.2
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager:  npm@10.3.0
Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-ezocff
Describe the bug
After upgrading nuxt to 3.7.0 (in particular destr to 2.0.2) ofetch starts to fail on Safari < 15.4 with message:
TypeError: e.at is not a function. (In 'e.at(-1)', 'e.at' is undefined)
It can be reproduced on Safari < 15.4
Additional context
As I understand the reason is an updated destr dependency from 2.0.1 to 2.0.2 which introduced at(-1) in the codebase: https://github.com/unjs/destr/compare/v2.0.1...v2.0.2#diff-a2a171449d862fe29692ce031981047d7ab755ae7f84c707aef80701b3ea0c80
As a quick fix I override its version in package.json as
"override": {
  "destr": "2.0.1"
}

Trying to set something like this in my nuxt.config.ts doesn't help:
export default defineNuxtConfig({
  vite: {
      build: {
          target: 'es2021'
      },
      esbuild: {
          target: 'es2021'
      },
      optimizeDeps: {
          esbuildOptions: {
              target: 'es2021'
          }
      }
  },
  build: {
      transpile: [
          'destr'
      ]
  }
})

Logs
No response

Because String.at/Array.at are only supported since Safari 15.4.
The topic of supporting legacy browser was covered a few times, e.g. in https://github.com/nuxt/nuxt/issues/20087, https://github.com/nuxt/nuxt/issues/19328 and https://github.com/nuxt/nuxt/issues/15464

Because String.at/Array.at are only supported since Safari 15.4.
The topic of supporting legacy browser was covered a few times, e.g. in #20087, #19328 and #15464
Instead of transpiling back, you could also try adding a polyfill for Array.at instead 😊

Thanks, manniL!
So there is no way to change the target?
I guest I'll have to do a polyfill in this case.
Afaics 3.7.0 https://github.com/nuxt/nuxt/releases/tag/v3.7.0 says nothing about dropping support for Safari 15.
Is it usually done without any notifications?
I see that nuxt states 2 most recent versions https://nuxt.com/blog/v3#the-browser-and-nodejs-support
But I thought it uses vite config https://vitejs.dev/guide/build.html#browser-compatibility

So there is no way to change the target? I guest I'll have to do a polyfill in this case.

As mentioned, there are various ways (you tried quite some of them as you shown before). Eventually, we want to support a top-level target option to make it easier but so far this is not implemented.

Is it usually done without any notifications?

No

I see that nuxt states 2 most recent versions nuxt.com/blog/v3#the-browser-and-nodejs-support
The core browser set targets the 2 most recent major versions of Chrome, Firefox, and Edge on a monthly basis and Safari on a yearly basis.

authors: manniL maprox


text:
My environment variables aren't working??

Discussed in https://github.com/nuxt/nuxt/discussions/27467

Originally posted by DarshGupta16 June  6, 2024
Just as I said in the title. I've spent hours trying to find out what's wrong but I'm not able to figure it out. This is my .env file in the root of my project -
OWM_API_KEY=...
FIRE_API_KEY=...

This is nuxt.server.ts -
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  devtools: { enabled: true },
  postcss: {
    plugins: {
      tailwindcss: {},
      autoprefixer: {},
    },
  },
  css: ["~/assets/css/main.css"],
  runtimeConfig: {
    private: {
      fireApi: process.env.FIRE_API_KEY,
      owmApi: process.env.OWM_API_KEY,
    },
  },
});

And when I try this in the pages/index.vue file -
<script lang="ts" setup>
console.log(useRuntimeConfig().private.fireApi);
</script>

I get this error -
[nuxt] error caught during app initialization TypeError: Cannot read properties of undefined (reading 'fireApi')
Also one more thing to note is that I'm using VS Code and the environment variables I created in the .env file just don't show up in the intellisense. Any variables created in the .env file are supposed to be auto imported and made accessible in the process.env file as well right? Can someone help me please?
Another little interesting thing to note- the API key gets printed in the terminal. Not sure if that's gonna be very helpful, but I'll tell you anyway.

Answered in Discussions


text:
Integration with Nuxt Image for built in image optimization

Description
For elements like UAvatar that use images, it would be a good idea to integrate with Nuxt Image for those who have it installed to benefit from image optimizations like setting image format, applying modifiers, and all the other features that Nuxt Image offers.
Additional context
No response

You can already do this using the as prop of the Avatar component:
<script setup>
const NuxtImg = resolveComponent('NuxtImg')
</script>

<template>
  <UAvatar src="https://github.com/benjamincanac.png" :as="NuxtImg" />
</template>

@benjamincanac
My apologies if it seemed as a duplicate, my suggestion was more so meant for automatic detection and usage of NuxtImg, not just plain capability. It would be a nice DX improvement in my opinion as it would simplify pages with a lot of avatar/other image elements.

@GalacticHypernova Indeed, we could automatically use <NuxtImg> if installed. We can't do it yet in v3 because of nuxt/ui#2141, we'll have to wait for a fix in Radix Vue first.

authors: GalacticHypernova benjamincanac

repo: nuxt/ui


text:
Possibility of OPAM package?

Hi, firstly, excellent work! Telegram bots and OCaml, two things I love! Though I haven't tried it yet, given that you use it on an existing bot, it seems fairly complete, if not absolutely so.
I was wondering; Are you planning to add the library to OPAM as a package in the future? It'd make installation a lot more convenient. Keep up the good work!

There's actually [a PR open for that right now]
(https://github.com/ocaml/opam-repository/pull/5597) which will hopefully be merged into master in a few hours.
Anyways, glad to see the interest in the project. For the record, it's still missing some of the more obscure features in the API (inline bots, user profile pics, etc.). For now it's fine for developing most basic bots but it's not "'complete."

Excellent! Thanks for the quick reply. The more obscure features being absent are fine. I have some experience with the API myself and know a few other people who will be interested in this, so it's possible we can contribute them if necessary.

authors: nv-vn rein

repo: nv-vn/TelegraML


text:
bumped copyright date from 2018 to 2019

GitHub Issue (If applicable): n/a
PR Type
What kind of change does this PR introduce?

Refactoring (no functional changes, no api changes)

What is the current behavior?
2009-2018
What is the new behavior?
2009-2019
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tested code with current supported SDKs
[ ] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[ ] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
[ ] Wasm UI Tests are not showing unexpected any differences
[ ] Contains NO breaking changes
[ ] Updated the Release Notes
[ ] Associated with an issue (GitHub or internal)

Other information
MSDN - https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assemblycopyrightattribute?redirectedfrom=MSDN&view=netframework-4.8

/azp run

source: gharchive/pull-request

repo: nventive/Uno


text:
🛑 PufferAI HPC Portal is down

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

HTTP code: 0
Response time: 0 ms

Resolved: PufferAI HPC Portal is back up in 12bf9e5.

repo: nvgsg/lab-upptime


text:
🛑 Kubeflow ML Platform is down

In 23f5552, 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 d06f5da.


text:
🛑 PufferAI HPC Portal is down

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

HTTP code: 0
Response time: 0 ms

Resolved: PufferAI HPC Portal is back up in 37104c6.


text:
Neotest-jest not working with describe.each

I'm trying to run some unit tests using neotest-jest, and I can't see the test results for some reason when using describe.each.
When running a test, such as:
import { sum } from '../src/AlgorithmsInTypescript/math'

describe('test sum module',() =>{
   test('1 + 2 should equal 3',()=> {
    const [a,b] = [1,2]
    expect(sum(a,b)).toBe(3)
  })
})

I can see the tests running fine.

However, if I run the following test:
import groupAnagrams from '../src/AlgorithmsInTypescript/GroupAnagrams'

const testCases = [
  {
    input: ['abc', 'cba', 'bca', 'xyz', 'yxz', 'zxy'],
    output: [
      ['abc', 'cba', 'bca'],
      ['xyz', 'yxz', 'zxy'],
    ],
  },
  {
    input: ['rat', 'tar', 'art', 'star', 'tars', 'rats'],
    output: [
      ['rat', 'tar', 'art'],
      ['star', 'tars', 'rats'],
    ],
  },
  {
    input: ['no', 'on', 'is', 'si', 'at', 'ta'],
    output: [
      ['no', 'on'],
      ['is', 'si'],
      ['at', 'ta'],
    ],
  },
  {
    input: ['bored', 'robed', 'debit card', 'bad credit', 'earth', 'heart'],
    output: [
      ['bored', 'robed'],
      ['debit card', 'bad credit'],
      ['earth', 'heart'],
    ],
  },
  {
    input: [''],
    output: [['']],
  },
  {
    input: ['a', 'b', 'c', 'a', 'b', 'c'],
    output: [
      ['a', 'a'],
      ['b', 'b'],
      ['c', 'c'],
    ],
  },
  {
    input: ['apple', 'paple', 'pale', 'leap', 'peal'],
    output: [
      ['apple', 'paple'],
      ['pale', 'leap', 'peal'],
    ],
  },
]

describe.each(testCases)('Test group anagrams', ({ input, output }) => {
  it(`The input: ${input} should return ${output}`, () => {
    const result = groupAnagrams(input)
    const resultGroups = result.map((group) => new Set(group))
    const expectedGroups = output.map((group) => new Set(group))

    expectedGroups.forEach((expectedGroup) => {
      expect(resultGroups).toEqual(
        expect.arrayContaining([
          expect.objectContaining({
            size: expectedGroup.size,
            ...expectedGroup,
          }),
        ]),
      )
    })

    resultGroups.forEach((resultGroup) => {
      expect(expectedGroups).toEqual(
        expect.arrayContaining([
          expect.objectContaining({ size: resultGroup.size, ...resultGroup }),
        ]),
      )
    })
  })
})

I don't see the result if I run it via Neo-Test Jest, and it gives me a blue icon in the test explorer. It will work if I run the test via CLI.

Below is my lua config with lazy for Neotest jest showing how I configured it.
return {
    -- Main testing dependency
    "nvim-neotest/neotest",
    dependencies = {
        "nvim-neotest/nvim-nio",
        "nvim-lua/plenary.nvim",
        "antoinemadec/FixCursorHold.nvim",
        "nvim-treesitter/nvim-treesitter",
        "nvim-neotest/neotest-jest",
        "Issafalcon/neotest-dotnet"
    },
    config = function()
        require("neotest").setup({
            adapters = {
                require("neotest-dotnet")({
                    discovery_root = 'solution'
                }),
                require("neotest-jest")({
                    jestCommand = "yarn test", -- Adjust this based on your npm command
                    jestConfigFile = "jest.config.js", -- If you have a Jest config file
                    env = { CI = true },

                    cwd = function(path)
                        -- Assuming tests are in a 'tests' folder
                        local relative_path = vim.fn.fnamemodify(path, ":~:.")
                        if string.match(relative_path, "^tests/") then
                            return vim.fn.getcwd()
                        end
                        return vim.fn.getcwd()
                    end,
                }),
            },
        })
    end,
}

Hello @tweiss777, did you manage to make this work? Have you tried setting jest_test_discovery  ?
require('neotest-jest')({
      ...,
      jest_test_discovery = true,
    }),

https://github.com/nvim-neotest/neotest-jest?tab=readme-ov-file#parameterized-tests

Actually I have the same issue, even with jest_test_discovery set, the tests are not displayed as expected

repo: nvim-neotest/neotest-jest


text:
Issue building with oxi

~/.local/share/nvim/lazy/nvim-spectre/spectre_oxi remotes/origin/HEAD*
❯ cargo build --release
   Compiling spectre_oxi v0.1.0 (/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi)
error: linking with `cc` failed: exit status: 1
  |
  = note: env -u IPHONEOS_DEPLOYMENT_TARGET -u TVOS_DEPLOYMENT_TARGET LC_ALL="C" PATH="/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/bin:/Users/jrreed/Library/Caches/fnm_multishells/55738_1711547154352/bin:/home/neonvoid/.local/share/fnm:/home/USER/.pyenv/bin:/Users/jrreed/.cargo/bin:/Applications/Fortify/Fortify_SCA_and_Apps_22.1.0/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/jrreed/.cargo/bin:/Users/jrreed/.antigen/bundles/robbyrussell/oh-my-zsh/lib:/Users/jrreed/.antigen/bundles/zsh-users/zsh-syntax-highlighting:/Users/jrreed/.antigen/bundles/zsh-users/zsh-autosuggestions:/Users/jrreed/.antigen/bundles/zsh-users/zsh-completions:/Users/jrreed/.antigen/bundles/unixorn/fzf-zsh-plugin-main:/Users/jrreed/.antigen/bundles/sindresorhus/pure-main:/Users/jrreed/.antigen/bundles/unixorn/fzf-zsh-plugin-main/bin:/opt/homebrew/opt/fzf/bin:/Users/jrreed/.yarn/bin:/Users/jrreed/.cargo/bin:/Users/jrreed/.rd/bin" VSLANG="1033" ZERO_AR_DATE="1" "cc" "-Wl,-exported_symbols_list,/var/folders/tp/ylt_symn7fg4wl37vj8ws9rc0000gn/T/rustcoybkTA/list" "-arch" "arm64" "/var/folders/tp/ylt_symn7fg4wl37vj8ws9rc0000gn/T/rustcoybkTA/symbols.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.1.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.2.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.3.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.4.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.5.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.6.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.7.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.8.rcgu.o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/spectre_oxi.32y4jhppwf8rzr2m.rcgu.o" "-L" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps" "-L" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libregex-1c101da71372e508.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libregex_automata-df3b701fc73b0090.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libaho_corasick-629c512e02813702.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libmemchr-7a0a96f66bb4f1cd.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libregex_syntax-8d0b10724907df37.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libnvim_oxi-2d81e0bb3228b590.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/liboxi_api-859f194b648c2184.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/liboxi_types-9191aa5704cb5cea.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/liblibc-2a600e5bbb3fd567.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libserde-7185e9148770aff9.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/liboxi_luajit-842b3184b51fef6a.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libonce_cell-41a5367adc81ee10.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libthiserror-ff8e8e01a18a0a69.rlib" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/liblazy_static-e95b4f4989c02d9c.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libstd-b0083070c892a1db.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libpanic_unwind-8282820217d7b362.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libobject-f163e9d1987a8318.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libmemchr-350512940f04084a.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libaddr2line-e19e4ea986b9addc.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libgimli-363744fff3c4e7ba.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc_demangle-e1d006f163566466.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libstd_detect-dea09910a3b22702.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libhashbrown-4802352fcc77de56.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc_std_workspace_alloc-e71c86d9086176a7.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libminiz_oxide-6d82e7a8c3f5e2c7.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libadler-e66d24d044cc2029.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libunwind-46eaa7bd445cb528.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libcfg_if-3c8a48285a1e7255.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/liblibc-50e20e60add24734.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/liballoc-edb678dd3e28691a.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc_std_workspace_core-3b6c10a2acaa607f.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libcore-2447397acf63b01e.rlib" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libcompiler_builtins-5816c590a0da89c2.rlib" "-liconv" "-lSystem" "-lc" "-lm" "-L" "/Users/jrreed/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib" "-o" "/Users/jrreed/.local/share/nvim/lazy/nvim-spectre/spectre_oxi/target/release/deps/libspectre_oxi.dylib" "-Wl,-dead_strip""-dynamiclib" "-Wl,-dylib" "-nodefaultlibs"
  = note: ld: Undefined symbols:
            _luaL_ref, referenced from:
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
            _lua_createtable, referenced from:
                nvim_oxi::entrypoint::entrypoint::hd231b45a37751297 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.5.rcgu.o
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
            _lua_error, referenced from:
                oxi_luajit::utils::handle_error::hcafe16d3a2f9af92 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.5.rcgu.o
                oxi_luajit::utils::handle_error::h3af1311b143e36ea in liboxi_luajit-842b3184b51fef6a.rlib[5](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.2.rcgu.o)
            _lua_gettop, referenced from:
                _$LT$i32$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h54304f6c3e8e4427 in liboxi_luajit-842b3184b51fef6a.rlib[3](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.0.rcgu.o)
                _$LT$alloc..string..String$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h44ea9c77b616421f in liboxi_luajit-842b3184b51fef6a.rlib[4](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.1.rcgu.o)
                oxi_luajit::utils::grow_stack::ha66f69946ace327b in liboxi_luajit-842b3184b51fef6a.rlib[5](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.2.rcgu.o)
            _lua_newuserdata, referenced from:
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
            _lua_pushboolean, referenced from:
                _$LT$bool$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h14ee19cea805d2d8 in liboxi_luajit-842b3184b51fef6a.rlib[6](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.3.rcgu.o)
            _lua_pushcclosure, referenced from:
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
                spectre_oxi::spectre_oxi::h8064762acfe3bec4 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.0.rcgu.o
            _lua_pushinteger, referenced from:
                _$LT$i64$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h57deb381b347ef14 in liboxi_luajit-842b3184b51fef6a.rlib[6](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.3.rcgu.o)
            _lua_pushlstring, referenced from:
                oxi_luajit::utils::handle_error::hcafe16d3a2f9af92 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.5.rcgu.o
                nvim_oxi::entrypoint::entrypoint::hd231b45a37751297 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.5.rcgu.o
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
                _$LT$alloc..string..String$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::heb4c59c42db2bd54 in liboxi_luajit-842b3184b51fef6a.rlib[4](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.1.rcgu.o)
                oxi_luajit::utils::handle_error::h3af1311b143e36ea in liboxi_luajit-842b3184b51fef6a.rlib[5](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.2.rcgu.o)
            _lua_pushnil, referenced from:
                _$LT$$LP$$RP$$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h457bf868469abc42 in liboxi_luajit-842b3184b51fef6a.rlib[6](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.3.rcgu.o)
            _lua_pushnumber, referenced from:
                _$LT$f64$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h37a2ec3dd3b0b834 in liboxi_luajit-842b3184b51fef6a.rlib[6](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.3.rcgu.o)
            _lua_rawgeti, referenced from:
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
            _lua_rawset, referenced from:
                nvim_oxi::entrypoint::entrypoint::hd231b45a37751297 in spectre_oxi.spectre_oxi.975d73f1102ced35-cgu.5.rcgu.o
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
            _lua_rawseti, referenced from:
                _$LT$oxi_types..object..Object$u20$as$u20$oxi_luajit..pushable..Pushable$GT$::push::h5260a41f726f7289 in liboxi_types-9191aa5704cb5cea.rlib[5](oxi_types-9191aa5704cb5cea.oxi_types.305d47a708d575b1-cgu.2.rcgu.o)
            _lua_settop, referenced from:
                _$LT$i32$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h54304f6c3e8e4427 in liboxi_luajit-842b3184b51fef6a.rlib[3](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.0.rcgu.o)
                _$LT$alloc..string..String$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h44ea9c77b616421f in liboxi_luajit-842b3184b51fef6a.rlib[4](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.1.rcgu.o)
                oxi_luajit::utils::grow_stack::ha66f69946ace327b in liboxi_luajit-842b3184b51fef6a.rlib[5](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.2.rcgu.o)
            _lua_tointeger, referenced from:
                _$LT$i32$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h54304f6c3e8e4427 in liboxi_luajit-842b3184b51fef6a.rlib[3](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.0.rcgu.o)
            _lua_tolstring, referenced from:
                _$LT$alloc..string..String$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h44ea9c77b616421f in liboxi_luajit-842b3184b51fef6a.rlib[4](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.1.rcgu.o)
            _lua_touserdata, referenced from:
                oxi_luajit::function::store::c_fun::h93c53f875af7072f in liboxi_luajit-842b3184b51fef6a.rlib[7](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.4.rcgu.o)
            _lua_type, referenced from:
                _$LT$i32$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h54304f6c3e8e4427 in liboxi_luajit-842b3184b51fef6a.rlib[3](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.0.rcgu.o)
                _$LT$alloc..string..String$u20$as$u20$oxi_luajit..poppable..Poppable$GT$::pop::h44ea9c77b616421f in liboxi_luajit-842b3184b51fef6a.rlib[4](oxi_luajit-842b3184b51fef6a.oxi_luajit.d2861a17a563e43d-cgu.1.rcgu.o)
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

error: could not compile `spectre_oxi` (lib) due to previous error

On MacOS

https://github.com/rust-lang/rust/issues/59705
met with same issue.

Not seeing it anymore

authors: jacobrreed towry

repo: nvim-pack/nvim-spectre


text:
refactor: reach the master

This adds commits from the master into the refactor branch #35 . Needs more tests to merge.
TODO

[x] db_root option does not work.
Type annotations have many errors.

I will fix this later in another PR.

[x] auto_validate works validly?

Seems working now.

Hi. I'm hopefully going to have time to show the plugins I wrote a bit more love now.
Thanks for all the work - this looks great!. Give me a couple of days to try read through the changes and try it out.

Now this takes over #35, so changes the target to main.

I have been dog-fooding long time, and it seems safe to merge.

I have been dog-fooding long time, and it seems safe to merge.

I will merge this. Another refactoring is needed.

I will merge this. Another refactoring is needed.

authors: delphinus sunjon


text:
nvm doesn't load nodejs v16.15.1

Operating system and version:
Linux localhost 3.10.61-8299335 #1 SMP PREEMPT Mon Dec 17 19:36:17 KST 2018 armv8l armv8l armv8l GNU/Linux
nvm debug output:

make[1]: *** [tools/v8_gypfiles/run_gen-regexp-special-case.target.mk:13: /root/.nvm/.cache/src/node-v16.15.1/files/out/Release/obj/gen/src/regexp/special-case.cc] Error 252    make[1]: *** Waiting for unfinished jobs....               rm 1cd53092da92343245362681778580af238f70c5.intermediate 6b3eb8c0a11bfa12b21a13a98c32785ea2628270.intermediate        make: *** [Makefile:113: node] Error 2                     nvm: install v16.15.1 failed!

(debug is too long)

nvm ls output:

->       system                                            iojs -> N/A (default)                                      node -> stable (-> N/A) (default)                          unstable -> N/A (default)                                  lts/* -> lts/gallium (-> N/A)                              lts/argon -> v4.9.1 (-> N/A)                               lts/boron -> v6.17.1 (-> N/A)                              lts/carbon -> v8.17.0 (-> N/A)                             lts/dubnium -> v10.24.1 (-> N/A)                           lts/erbium -> v12.22.12 (-> N/A)                           lts/fermium -> v14.20.0 (-> N/A)                           lts/gallium -> v16.16.0 (-> N/A)

How did you install nvm?

Using curl, from this tutorial:
https://tecadmin.net/install-nodejs-with-nvm/
What steps did you perform?
It's up
What happened?
I typed nvm install v16.15.1 then I wait for half hour with a lot of log in terminal, and after all that Error installing nodejs v16.15.1.
What did you expect to happen?
I expect to work but it's not.
Is there anything in any of your profile files that modifies the PATH?

I don't know, I just follow the tutorial up ^

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

Trying 104.20.23.46:443...                             * TCP_NODELAY set                                          * Connected to nodejs.org (104.20.23.46) port 443 (#0)     * ALPN, offering h2                                        * ALPN, offering http/1.1                                  * successfully set certificate verify locations:           *   CAfile: /etc/ssl/certs/ca-certificates.crt               CApath: /etc/ssl/certs                                   * TLSv1.3 (OUT), TLS handshake, Client hello (1):          * TLSv1.3 (IN), TLS handshake, Server hello (2):           * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):   * TLSv1.3 (IN), TLS handshake, Certificate (11):           * TLSv1.3 (IN), TLS handshake, CERT verify (15):           * TLSv1.3 (IN), TLS handshake, Finished (20):              * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):* TLSv1.3 (OUT), TLS handshake, Finished (20):             * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384    * ALPN, server accepted to use h2                          * Server certificate:                                      *  subject: CN=*.nodejs.org                                *  start date: Jan 11 00:00:00 2022 GMT                    *  expire date: Feb 11 23:59:59 2023 GMT                   *  subjectAltName: host "nodejs.org" matched cert's "nodejs.org"                                                      *  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA                                                          *  SSL certificate verify ok.                              * Using HTTP2, server supports multi-use                   * Connection state changed (HTTP/2 confirme)          * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0                                      * Using Stream ID: 1 (easy handle 0xf067238)               > HEAD /dist/ HTTP/2                                       > Host: nodejs.org                                         > user-agent: curl/7.68.0                                  > accept: */*                                              > accept-encoding: deflate, gzip, br                       >                                                          * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):      * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):      * old SSL session ID is stale, removing                    * Connection state changed (MAX_CONCURRENT_STREAMS == 256)!< HTTP/2 200                                               HTTP/2 200                                                 < date: Thu, 07 Jul 2022 16:51:56 GMT                      date: Thu, 07 Jul 2022 16:51:56 GMT                        < content-type: text/html                                  content-type: text/html                                    < last-modified: Thu, 07 Jul 2022 16:20:09 GMT             last-modified: Thu, 07 Jul 2022 16:20:09 GMT               < cache-control: max-age=14400                             cache-control: max-age=14400                               < cf-cache-status: HIT                                     cf-cache-status: HIT                                       < expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"                  expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"                    < vary: Accept-Encoding                                    vary: Accept-Encoding                                      < server: cloudflare                                       server: cloudflare                                         < cf-ray: 727216724d861c3b-SOF                             cf-ray: 727216724d861c3b-SOF                               < content-encoding: br                                     content-encoding: br

<
* Connection #0 to host nodejs.org left intact

What kind of machine do you have? What distro of linux?
As for that tutorial, it should not be recommending using master - use the latest released version in the readme ONLY.

@ljharb Well I use UserLAnd App on PlayStore, and I use Linux ubuntu in it

tbh I would never assume that a linux build on android would have the capacity to compile node in a performant way; it's just not a reasonable expectation.
That said, I'm not familiar with the "UserLAnd" app. Can you share a paste of the last few hundred lines of log output that includes the error?

@ljharb looks like the problem is the lack of mapping from armv8l to armv7l, I tried to run nvm in a 32-bit lxc conatiner on arm64 system, it started building nodejs as it tried to download https://nodejs.org/dist/v12.22.12/node-v12.22.12-linux-armv8l.tar.gz that doesn't exist, uname -m returns armv8l in such environment, so I guess the same happened to @iTzVoko. It's also reproducible with linux32 uname -m on an arm64 system.
https://github.com/nvm-sh/nvm/blob/e6fa80cb6178ff4e9735265281b5eae811f05f11/nvm.sh#L1920
I believe there should be armv8l) NVM_ARCH="armv7l" ;;

Seems like this was fixed with #3102.

authors: iTzVoko ilya-fedin ljharb

repo: nvm-sh/nvm


text:
adding custom metadata columns

this adds custom metadata columns defined as input dictionary argument to samples, events, messages data frames.

see my individual comments. The code at this stage is compatible with both 2 and 3. Is there something else I could do at this stage?

This works with no problem with .loc[:,key] = value
In [9]: samples, events, messages =
edf.pread("/home/onat/Documents/Code/Python/pyedfread/SUB001.EDF",ignore_samples=True,filter='all',meta={'subj':[12]})
However, when the meta dict doesn't have value of dtype list, it crashes.
In [10]: samples, events, messages =
edf.pread("/home/onat/Documents/Code/Python/pyedfread/SUB001.EDF",ignore_samples=True,filter='all',meta={'subj':"12"})
ValueError                                Traceback (most recent call last)
 in ()
----> 1 samples, events, messages =
edf.pread("/home/onat/Documents/Code/Python/pyedfread/SUB001.EDF",ignore_samples=True,filter='all',meta={'subj':"12"})
/home/onat/anaconda2/lib/python2.7/site-packages/pyedfread/edf.pyc in
pread(filename, ignore_samples, filter, split_char, trial_marker, meta)
60         events.loc[:,key] = value
61         messages.loc[:,key]=value
---> 62         samples.loc[:,key] = value
63         #events.insert(0,key,value)
64         #messages.insert(0,key,value)
/home/onat/anaconda2/lib/python2.7/site-packages/pandas/core/indexing.pyc
in setitem(self, key, value)
139             key = com._apply_if_callable(key, self.obj)
140         indexer = self._get_setitem_indexer(key)
--> 141         self._setitem_with_indexer(indexer, value)
142
143     def _has_valid_type(self, k, axis):
/home/onat/anaconda2/lib/python2.7/site-packages/pandas/core/indexing.pyc
in _setitem_with_indexer(self, indexer, value)
289                         if any([not l for l in len_non_info_axes]):
290                             if not is_list_like_indexer(value):
--> 291                                 raise ValueError("cannot set a
frame with no "
292                                                  "defined index and
a scalar")
293                             self.obj[key] = value
ValueError: cannot set a frame with no defined index and a scalar
In [11]:

repo: nwilming/pyedfread


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 9554ea6.

repo: nxvvvv/uptime


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in db69107.


text:
Reminders

Keep track of the last time that the user performed certain actions, issue a reminder to do them.
Things like refreshing keys, running "advise"
Maybe key refresh should be automatic?

Of course, that implies the question: what is the "right" way to refresh keys? Some (including myself) would say Parcimonie.

FWIW, I believe there was a bash port of Parcimonie written at some point.

Parcimonie can be installed with apt-get install parcimonie (on Debian based systems). I think that it should be part of setting up (or initializing the system), and that's all.
By the way, I have started a fork of the project here: https://github.com/dashohoxha/egpg
I don't know all the details about GnuPG (it is huge), so any ideas or suggestions about improving it would be wellcome.

authors: dashohoxha nyarly strugee

repo: nyarly/simplekey

license: unlicense


text:
GL渲染内存泄漏

程序运行一段时间内存爆掉，跟踪内存可知：
background.cpp中void Background::Draw(Mat &frame)
backmesh.h中void Draw(cv::Mat &frame)
渲染每一帧用glGenTextures(1, &texture);重复创建新的纹理ID，
解决办法：函数尾部加glDeleteTextures(1, &texture);

了解了，谢谢大佬


text:
SIG Reviewer/Maintainer Nomination: @micronAMZN

Documentation maintainer

[x] Has been a Reviewer for 2+ months
[x] 8+ reviewed Pull Requests in the previous 2 months
[x] 2+ D&C SIG Maintainers who support promotion.

Maintaining status: 8+ Pull Requests reviewed per month.

Reviewer/Maintainer Nomination
Fill out the template below including nominee GitHub user name, desired role and personal GitHub profile

I would like to nominate: @micronAMZN to become a Maintainer on behalf of sig-docs-community. I verify that they have fulfilled the prerequisites for this role.
NOTE: Mike has been unofficially performing in the role of reviewer for 6+ months since the launch of O3DE.

Nominee's GitHub Profile: @micronAMZN

Reviewers & Maintainers that support this nomination should comment in this issue.

I support @micronAMZN's promotion to maintainer of sig-docs-community.

I support the nomination of @micronAMZN to maintainer of the sig-docs-community.

Approved!

authors: FiniteStateGit chanmosq sptramer


text:
SIG Maintainer Nomination: Michał Pełka

Nomination Guidelines
Maintainer Nomination Requirements

Has been a Reviewer for 2+ months
8+ reviewed Pull Requests in the previous 2 months
200+ lines of code changed across all reviewed Pull Request
2+ O3DE Maintainers that support the promotion from Reviewer to Maintainer
Requirements to retain the Reviewer role: 4+ Pull Requests reviewed per month

Maintainer Nomination
Fill out the template below including nominee GitHub user name, desired role and personal GitHub profile

I would like to nominate @michalpelka to become a Maintainer on behalf of sig-simulation. I verify that they have fulfilled the prerequisites for this role.

Nominee's GitHub Profile https://github.com/michalpelka

Reviewers & Maintainers that support this nomination should comment in this issue.

I support this nomination

I support this nomination

Approved in today's triage.

authors: adamdbrw lgleim spham-amzn


text:
Crashes on windows

Seems to crash (ends program and Python interpreter) on Windows during transcription (when calling whisper_full) without any other output or error.

After getting it in a debugger, I saw that the crash was happening when trying to read from the audio frame data passed to whisper_full.
My assumption is that the garbage collector was freeing the frame data before the call to whisper_full, but it could keep working if the memory doesn't actually get removed from the process's address space.
The behavior of how the memory is reclaimed is probably different on different platforms, which could explain why the crash wasn't happening everywhere.
Regardless, it's no longer crashing after the fix in #7.

Should be fixed by d8c0617 let me know if there's any further issues.

authors: boolemancer o4dev stlukey


text:
Specify the module name in ansible 2.7

Since the changes in the ovirt_disk will come to ansible 2.8
make sure this version from library folder is going to be used in
ansible 2.7.

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow #3 option )
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

Why do you think we need that?
According to https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse_roles.html#embedding-modules-and-plugins-in-roles

This can also be used, with some limitations, to modify modules in Ansible’s core distribution, such as to use development versions of modules before they are released in production releases. This is not always advisable as API signatures may change in core components, however, and is not always guaranteed to work. It can be a handy way of carrying a patch against a core module, however, should you have good reason for this. Naturally the project prefers that contributions be directed back to github whenever possible via a pull request.

The role is still failing with ansible 2.7. Most probably because the original module was used before and the updated module from library folder is not loaded. To rename the module it is a save way how to enforce the module from library to be used.
The same technique was used for example here:
https://github.com/oVirt/ovirt-ansible-vm-infra/pull/43/files by machacekondra.

ci add to whitelist

ci build please

By default using the standard module name under library/ is enough to have it winning over the vanilla ansible one.
This is just needed if the user is explicitly overriding ANSIBLE_LIBRARY ant env level.

authors: jirimacku ovirt-infra tiraboschi

repo: oVirt/ovirt-ansible-hosted-engine-setup


text:
Show 'Next Run' label

Blue 'Changes Pending' label is rendered if next_run exists
Fixes: https://github.com/oVirt/ovirt-web-ui/issues/238

repo: oVirt/ovirt-web-ui


text:
Found manga cant be downloaded

Describe the bug
If you search for a Manga you sometimes cant download it cuz it doesnt display any info under Downloads (after selecting the time) and then it simply throws an error manga could not be found.
Reproduction steps

Select Source
Enter Name of more niche Manga
Select Manga
Enter Time
No Info Displayed
No Download

Expected behavior
It should find all Info it needs since it can find the Manga and it exists on the site.
Additional context
I used Manganato and Game Of Familia: Kazoku Senki.

Yeah i wonder if we will ever see this fixed....

@ElryWeeb @ghost
I think it is relate to this issus cause by special caracter.
After multiple test with mangal, it doen't seems to be a problem with the extractor because I can extrat the manga with delimiter using "inline" mode or "mini" manualy.
Maybe Kaizoku don't handle the conversion when trying to create the title with what mangal return.
Anyway, for the small number of manga that have a problem, I use the "mangasee" source witch works fine.

authors: ElryWeeb ghost mg-dev25

repo: oae/kaizoku


text:
Feat/pupil 159/mcq multi answers

User Story
I want to take multiple choice quiz questions with multiple correct answers
Implementation details

Involves considerable refactoring of Quiz Components and the QuizContext

Acceptance criteria

[x]  handles text and image questions
[x]  provides feedback according to the figma designs

How to test
https://deploy-preview-2143--oak-web-application.netlify.thenational.academy/pupils/programmes/english-secondary-ks4-aqa/units/non-fiction-crime-and-punishment/lessons/reading-complex-texts-about-crime-and-punishment#starter-quiz
https://deploy-preview-2143--oak-web-application.netlify.thenational.academy/pupils/programmes/maths-secondary-ks3/units/graphical-representations-of-data/lessons/constructing-bar-charts-by-utilising-technology#starter-quiz (2nd question)
Notes for reviewers

I was torn between using context inside the components or passing props. In the end I went for context to keep logic out of the quiz renderer class
NB. the single choice is not yet consistent with this approach but will be in future
Quiz surrounds are out of scope for this ticket.

:tada: This PR is included in version 1.316.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:
fix: update imports (type prefixes, paths)

Description

Continued work on linting
Updates import paths, either using the import type pattern or directly to an appropriate file

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

authors: oak-machine-user stefl

repo: oaknational/oak-ai-lesson-assistant


text:
[OPPRO-137] optimize compile process

What changes were proposed in this pull request?
First compile use -Dbuild_arrow=ON
Second compile use exists arrow_root=tools/build/arrow_install
How was this patch tested?
manual tests

@zhztheplayer please help to have a see, thanks!

repo: oap-project/gluten


text:
converts STIX2.0 to 2.1

How to convert my CTI expressed in STIX 2.0 to STIX 2.1?

thx, but when I run this in a stix 2.0 JSON file, I encountered a waining in begin of the output JSON and two warnings at the end of the output JSON, what's wrong?
`[stixmarx.utils] [WARNING] [2021-03-31 12:08:05,954] No module named 'maec'
{
The output JSON
}
[-] Results for: enterprise-attack/malware/malware--007b44b6-e4c5-480b-b5b9-56f2081b1b7b.json
[+] STIX JSON: Valid
[!] Warning: malware--007b44b6-e4c5-480b-b5b9-56f2081b1b7b: {216} malware_types contains a value not in the malware-type-ov vocabulary.
[!] Warning: malware--007b44b6-e4c5-480b-b5b9-56f2081b1b7b: {302} External reference 'mitre-attack' has a URL but no hash.     `

Hi @lizitong67,
Use pip to download the maec python package.  That should get rid of the first warning.
The other warnings are from the stix validator.  The generated JSON is valid, but the warnings mean you are doing something that the STIX specification recommends against.  See https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.html

repo: oasis-open/cti-stix-elevator


text:
Move the Localnet docker section into separate chapter

Similarly to how we moved the network settings to a separate chapter and how we revamped the Band protocol (#907), I suggest we devote a new "Localnet Development" (dapp/tools/localnet.md) chapter which includes the current content of https://docs.oasis.io/dapp/sapphire/guide#running-a-private-oasis-network-locally
TODO:

[x] mention it could also be used for running Emerald (and replace https://docs.oasis.io/dapp/emerald/writing-dapps-on-emerald#running-a-private-oasis-network-locally with a link to the new chapter)
[ ] mention it in the ROFL chapter: https://docs.oasis.io/rofl/app#testing-it-on-sapphire-localnet
[ ] replace any links throughout the docs pointing to Sapphire Guide subsection or any links pointing directly to https://github.com/oasisprotocol/oasis-web3-gateway/pkgs/container/sapphire-localnet or https://github.com/oasisprotocol/oasis-web3-gateway/tree/main/docker with the new https://docs.oasis.io/dapp/tools/localnet
[x] mention that minimum requirements for running the Sapphire Localnet image (at least 16GB of memory)

Merge sequence:

[ ] New page goes in first https://github.com/oasisprotocol/docs/pull/977
[ ] Dependent reference https://github.com/oasisprotocol/sapphire-paratime/pull/429
[ ] Dependent reference https://github.com/oasisprotocol/oasis-sdk/pull/2023
[ ] Bump sapphire-paratime and oasis-sdk submodules to publish

authors: aefhm matevz

repo: oasisprotocol/docs


text:
release: Add macOS builds

TODO: figure out how to cross-compile with CGO using goreleaser. reference: https://goreleaser.com/cookbooks/cgo-and-crosscompiling
Avoid the complex setup of cross-compiling Oasis Core Ledger's macOS binaries on Linux due to dependencies requiring CGO.
Instead, build macOS binaries on macOS and use them when building and publishing an Oasis Core Ledger's release on Linux.

Both oasis-core-ledger and ledger-signer from https://github.com/tjanez/oasis-core-ledger/releases/tag/v1.1.0 confirmed  working on my mac

repo: oasisprotocol/oasis-core-ledger


text:
sink filter is incorrect, not handling all tokens

case token_type::ty_eof:
break;
case token_type::ty_sl_comment:
[[fallthrough]];
case token_type::ty_blk_comment:
if (!ignore_comments)
handle(t, tf.svalue(t));
else
token_ignored = true;
break;
default:
handle(t, tf.svalue(t));

remove the stop variable in sink.

Add:
`
struct token
{
union content
{
token_data td;
rtoken_ptr rt;
content() : td{} {}
content(rtoken_ptr v) : rt{v} {}

};
content    value;
token_type type = token_type::ty_eof;
bool       disabled = false;`
Make token disabled in disabled section

else if ((!section_disabled || !ignore_disabled))
{
tok.disabled = section_disabled;
post(tok);
}

repo: obhi-d/ppr


text:
New ffcode parameters

New ffcode parameters looks bad:

Here is an example with old ffcode parameters:

I think we need to fix it. Also I think, that old font was more readable.

@yegor256, what do you think?

@c71n93 I still think that the first format is better (bold+sf). Try to shorted the names of the objects. childObject1 is a really bad name.

@yegor256 ok, I understand. But in some cases it can't resolve some symbols:
New:

Old:

This definitely needs to be fixed.

repo: objectionary/eo-book


text:
lang.IndexOutOfBoundsException in org.eolang.jeo.representation.xmir.XmlAnnotation.child

I'm getting this:
[INFO] >> [INFO] --- jeo:0.6.3:assemble (default-cli) @ hone ---
[INFO] >> [INFO] Assembling files from '/target/generated-sources/unrolled' to '/target/classes'
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone_maven_plugin/HelpMojo.xmir' (1Mb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/RmiMojo.xmir' (42Kb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/BuildMojo.xmir' (184Kb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/Mktemp.xmir' (95Kb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/Docker.xmir' (186Kb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/AbstractMojo.xmir' (59Kb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/package-info.xmir' (2Kb)
[INFO] >> [INFO] Assembling '/target/generated-sources/unrolled/org/eolang/hone/OptimizeMojo.xmir' (163Kb)
[INFO] >> [INFO] '/target/generated-sources/unrolled/org/eolang/hone/package-info.xmir' assembled to '/target/classes/org/eolang/hone/package-info.class' (80b) in 129ms
[INFO] >> [INFO] Assembling of 'org/eolang/hone/package-info' finished successfully.
[INFO] >> [INFO] ------------------------------------------------------------------------
[INFO] >> [INFO] BUILD FAILURE
[INFO] >> [INFO] ------------------------------------------------------------------------
[INFO] >> [INFO] Total time:  0.669 s
[INFO] >> [INFO] Finished at: 2024-10-15T09:52:16Z
[INFO] >> [INFO] ------------------------------------------------------------------------
[INFO] >> [ERROR] Failed to execute goal org.eolang:jeo-maven-plugin:0.6.3:assemble (default-cli) on project hone: Execution default-cli of goal org.eolang:jeo-maven-plugin:0.6.3:assemble failed. IndexOutOfBoundsException: Index 0 out of bounds for length 0 -> [Help 1]
[INFO] >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eolang:jeo-maven-plugin:0.6.3:assemble (default-cli) on project hone: Execution default-cli of goal org.eolang:jeo-maven-plugin:0.6.3:assemble failed.
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
[INFO] >>     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
[INFO] >>     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
[INFO] >>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
[INFO] >>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
[INFO] >>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
[INFO] >>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
[INFO] >>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
[INFO] >>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
[INFO] >>     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
[INFO] >>     at java.lang.reflect.Method.invoke (Method.java:580)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
[INFO] >> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.eolang:jeo-maven-plugin:0.6.3:assemble failed.
[INFO] >>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:133)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
[INFO] >>     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
[INFO] >>     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
[INFO] >>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
[INFO] >>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
[INFO] >>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
[INFO] >>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
[INFO] >>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
[INFO] >>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
[INFO] >>     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
[INFO] >>     at java.lang.reflect.Method.invoke (Method.java:580)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
[INFO] >> Caused by: java.lang.IndexOutOfBoundsException
[INFO] >>     at jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance (DirectConstructorHandleAccessor.java:62)
[INFO] >>     at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:502)
[INFO] >>     at java.lang.reflect.Constructor.newInstance (Constructor.java:486)
[INFO] >>     at java.util.concurrent.ForkJoinTask.getThrowableException (ForkJoinTask.java:542)
[INFO] >>     at java.util.concurrent.ForkJoinTask.reportException (ForkJoinTask.java:567)
[INFO] >>     at java.util.concurrent.ForkJoinTask.invoke (ForkJoinTask.java:670)
[INFO] >>     at java.util.stream.ForEachOps$ForEachOp.evaluateParallel (ForEachOps.java:160)
[INFO] >>     at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel (ForEachOps.java:174)
[INFO] >>     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:233)
[INFO] >>     at java.util.stream.ReferencePipeline.forEach (ReferencePipeline.java:596)
[INFO] >>     at org.eolang.jeo.Assembler.assemble (Assembler.java:84)
[INFO] >>     at org.eolang.jeo.AssembleMojo.execute (AssembleMojo.java:117)
[INFO] >>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
[INFO] >>     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
[INFO] >>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
[INFO] >>     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
[INFO] >>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
[INFO] >>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
[INFO] >>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
[INFO] >>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
[INFO] >>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
[INFO] >>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
[INFO] >>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
[INFO] >>     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
[INFO] >>     at java.lang.reflect.Method.invoke (Method.java:580)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
[INFO] >>     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
[INFO] >> Caused by: java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
[INFO] >>     at jdk.internal.util.Preconditions.outOfBounds (Preconditions.java:100)
[INFO] >>     at jdk.internal.util.Preconditions.outOfBoundsCheckIndex (Preconditions.java:106)
[INFO] >>     at jdk.internal.util.Preconditions.checkIndex (Preconditions.java:302)
[INFO] >>     at java.util.Objects.checkIndex (Objects.java:385)
[INFO] >>     at java.util.ArrayList.get (ArrayList.java:427)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlAnnotation.child (XmlAnnotation.java:81)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlAnnotation.descriptor (XmlAnnotation.java:68)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlAnnotation.bytecode (XmlAnnotation.java:57)
[INFO] >>     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:197)
[INFO] >>     at java.util.ArrayList$ArrayListSpliterator.forEachRemaining (ArrayList.java:1708)
[INFO] >>     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:509)
[INFO] >>     at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:499)
[INFO] >>     at java.util.stream.ReduceOps$ReduceOp.evaluateSequential (ReduceOps.java:921)
[INFO] >>     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
[INFO] >>     at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:682)
[INFO] >>     at org.eolang.jeo.representation.bytecode.BytecodeAnnotations.<init> (BytecodeAnnotations.java:61)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlAnnotations.bytecode (XmlAnnotations.java:54)
[INFO] >>     at java.util.Optional.map (Optional.java:260)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlField.bytecode (XmlField.java:64)
[INFO] >>     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:197)
[INFO] >>     at java.util.ArrayList$ArrayListSpliterator.forEachRemaining (ArrayList.java:1708)
[INFO] >>     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:509)
[INFO] >>     at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:499)
[INFO] >>     at java.util.stream.ReduceOps$ReduceOp.evaluateSequential (ReduceOps.java:921)
[INFO] >>     at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
[INFO] >>     at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:682)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlClass.bytecode (XmlClass.java:104)
[INFO] >>     at org.eolang.jeo.representation.xmir.XmlProgram.bytecode (XmlProgram.java:106)
[INFO] >>     at org.eolang.jeo.representation.XmirRepresentation.toBytecode (XmirRepresentation.java:144)
[INFO] >>     at org.eolang.jeo.Assemble.apply (Assemble.java:59)
[INFO] >>     at org.eolang.jeo.LoggedTranslation.apply (LoggedTranslation.java:84)
[INFO] >>     at org.eolang.jeo.BachedTranslator.translate (BachedTranslator.java:71)
[INFO] >>     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:197)
[INFO] >>     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:197)
[INFO] >>     at java.util.stream.ReferencePipeline$2$1.accept (ReferencePipeline.java:179)
[INFO] >>     at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:197)
[INFO] >>     at java.util.Spliterators$ArraySpliterator.forEachRemaining (Spliterators.java:1024)
[INFO] >>     at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:509)
[INFO] >>     at java.util.stream.ForEachOps$ForEachTask.compute (ForEachOps.java:291)
[INFO] >>     at java.util.concurrent.CountedCompleter.exec (CountedCompleter.java:754)
[INFO] >>     at java.util.concurrent.ForkJoinTask.doExec (ForkJoinTask.java:387)
[INFO] >>     at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec (ForkJoinPool.java:1312)
[INFO] >>     at java.util.concurrent.ForkJoinPool.scan (ForkJoinPool.java:1843)
[INFO] >>     at java.util.concurrent.ForkJoinPool.runWorker (ForkJoinPool.java:1808)
[INFO] >>     at java.util.concurrent.ForkJoinWorkerThread.run (ForkJoinWorkerThread.java:188)
[INFO] >> [ERROR]

Again, it's not clear which .xmir file caused the problem.

@volodya-lombrozo please, help

@volodya-lombrozo also, would be nicer to have
Assembling of 'org/eolang/hone/package-info.class' (4Kb) finished successfully.

instead of
Assembling of 'org/eolang/hone/package-info' finished successfully.

@rultor release, tag is 0.6.4, title is 0.6.4.

@rultor release, tag is 0.6.4, title is 0.6.4.

@volodya-lombrozo OK, I will release it now. Please check the progress here.

@rultor release, tag is 0.6.4, title is 0.6.4.

@volodya-lombrozo Done! FYI, the full log is here (took me 12min).

@yegor256 Could you try with the new 0.6.4 version, please?

@volodya-lombrozo this one is gone, thanks

authors: rultor volodya-lombrozo yegor256

repo: objectionary/jeo-maven-plugin


text:
Potential new issue placeholder

@neroux you mentioned something about the issue? :)

I did, but then I double checked 😆. Apologies, my bad.
I used addHeader() instead of setHeader() and got two user agent headers.
Only thing, I believe the description is not entirely accurate.
https://github.com/oblac/jodd-http/blob/720a304ee8db25429c69922b21f6587e0a408dc4/src/main/java/jodd/http/HeadersMultiMap.java#L36-L39

Ah, true... HTTP headers are so crazy. We can have one, we can have multiple... fun :)))

Though not all headers like that. Yep, fun :)

authors: igr neroux

repo: oblac/jodd-http


text:
Wrong contentHeight results in content being hidden in 13.0.0

This is what I know so far:
Until this commit https://github.com/oblador/react-native-collapsible/commit/b882388c90227b5dc13f7fa301ec9d5c9ad9a4ef we've been using componentWillReceiveProps but now we use: componentDidUpdate
Here's the series of events that took place when collapsible is set to true:
Before the commit (componentWillReceiveProps):

First _handleLayoutChange runs

Second measureContent runs

Third _handleLayoutChange runs again

After the commit (componentDidUpdate):

First _handleLayoutChange runs

Second measureContent runs

What's the problem?
The first 2 events calculate the wrong height, and before the commit, the third one (_handleLayoutChange) was the one that set the correct height, and fixed it all.
But after the commit from above that no longer happens, so we're left with a wrong height.
Where I tested:
Happens in react-native-collapsible: 13.0.0
Does NOT happen in react-native-collapsible: 12.0.1

Could you create the example where this would happen? I'd love to fix it if it's a bug, but i need some sort of benchmark to test against

Sure I'll try to create one today.

I spent a lot of time trying to re-create the issue on a fresh rn project, but couldn't :/
This turned out to be harder than what I thought it would be, therefore we're just going to use 12.0.1 for now and hope for a fix in the future.
That being said, any idea what might cause getNode().measure to return a smaller value than the actual height?

I experienced a similar issue. Here a basic example: https://snack.expo.io/@matbrady/collapsable-switch
Downgrading to 0.12.0 fixes the issue for me on my local project but not when I adjust the version in Expo. (Not sure if Expo actually downloads the different version)

I have a similar problem.
Example:

I add an item to the list
I set collapse = false
I add a new item
collapse = true
and I add a new item

The collapse component doesn't refresh his content height, then I have to set collapse = false again and set collapse = true again, to the component refresh his height...
Downgrading to 0.12.0 solved the issue...

Had a similar issue with the current version 1.4.0, using the default prop for align fixed the issue

This is still an issue with getNode().measure in 2019.
Still don't know why.

Using accordion with react-native-collapsible will not dynamically change its content height.
I used a flatlist inside accordion and faced similar problem.. I solved it by setting a flag and re-rendering the view of accordion.
This is my flatlist.
<FlatList           data={section.content}           renderItem={this.renderItem}           extraData={this.state.refresh}           ListEmptyComponent={this.ListEmptyView}         />
I re-rendered my accordion view like this when i add new content to flatlist.
{this.state.refresh ? (             <View style={styles.flatlistMainContainer}>               <Accordion                 sections={this.state.accordionArray}                 activeSections={this.state.activeSections}                 renderHeader={this.renderAccordionHeader}                 renderContent={this.renderAccordionItem}                 onChange={this._updateSections}                 touchableComponent={TouchableOpacity}               />             </View>           ) : null}
When i make any change in its content dynamically i will set the flag as :
this.setState({ refresh: false }, () => {                         this.setState({ refresh: true });                       });
By doing like this component  refresh his content height.

I'm seeing a similar issue. I have a tree structure using nested Collapsible components built recursively. When the component renders, it's supposed to expand all of the collapsible panels down to the currently selected item.
The internal state of all of the collapsible components is correct, but the top level item seems to be incorrectly calculating the height of the content, so many of the nested children are getting cut off.
Downgrading to 1.5.2 fixes the issue for me, so I suspect the issue is related to this change to the content measurement logic: https://github.com/oblador/react-native-collapsible/compare/v1.5.2...v1.5.3

It seems my issue is related to the fact that _measureContent only gets called when the collapsible is expanded. If the content changes dynamically, the height does not get recalculated.

Yep, I confirm that's still an issue in 2021

Did anyone find a solution for this? I am facing the same issue

authors: JoeKyx SudoPlz daveporras gilshaan iRoachie joebochill matbrady to-dy

repo: oblador/react-native-collapsible


text:
ViewPropTypes warning in RN 0.44

Import ViewPropTypes, and fix some linting.!

Fixed on next branch https://github.com/oblador/react-native-collapsible/commit/960fd76ab8317b78ce72fe4767273738fec38f5f. Will be live on next release

authors: iRoachie raubas


text:
frontal bossing

Add:
frontal bossing (child of abnormal forehead shape MP:0030045 )
DEF: bilateral bulging of the lateral frontal bone prominences with relative sparing of the midline; this is not the same as prominent forehead
EXACT SYNONYMS: frontal protuberance; skull bossing
SOURCE: PMID:19125436
Annotation in J:36305 (MGI:2177551), J:152152 (MGI:4360984), J:50144 (MGI:3717417)

frontal bossing MP:0030262


text:
Support OpenShift 3.x and 4.x

OpenShift will likely work without issue, however, some things are different. For example, OS 3.11 does not support startup probe.

Hello @jsirianni ,
Me and my team are currently working on deploying this chart on openshift 4.X. We are facing issues where the runAsUser and fsGroup values of the bindplane.yaml template are hardcoded to 66534 :
https://github.com/observIQ/bindplane-op-helm/blob/main/charts/bindplane/templates/bindplane.yaml#L33
https://github.com/observIQ/bindplane-op-helm/blob/main/charts/bindplane/templates/bindplane.yaml#L355
This is a major issue for us as this prevents us from deploying the ressource. OpenShift requires these values to be in a specific range (rootless uids). Making those securityContext fully customizable via the values.yaml, would fix this issue.
(Examples here : https://github.com/grafana/helm-charts/blob/main/charts/grafana/templates/_pod.tpl#L9-L12, https://github.com/prometheus-community/helm-charts/blob/main/charts/prometheus/templates/deploy.yaml#L62-L65 )
This would be a first step for us, as we would be able to deploy the chart, and get pods running for further possible debugging.

Hi @PaulEvans8669, I still need to have my team review this, but if you would like to check this PR I would love to have your feedback https://github.com/observIQ/bindplane-op-helm/pull/32

Hello @jsirianni , this looks very good from my point of view.
I'm really looking forward to see this get merged :)
Thank you!

@PaulEvans8669 we have merged and released, you can find the release here https://github.com/observIQ/bindplane-op-helm/releases/tag/bindplane-0.0.33.
Please let us know if you need anything else :+1:

repo: observIQ/bindplane-op-helm


text:
Create sitemap / RSS

Like vitepress, build an items array from the list of pages, with a transformItems hook that allows the user to modify the array before passing it to https://www.npmjs.com/package/sitemap (with options).
Ref. https://vitepress.dev/guide/sitemap-generation
It seems sensible to adopt the same approach here.
To build a sitemap, we need to know the full URL (including domain name and subdirectory, ref. #42).

#843 removed client-side access to the search index.
It was the closest thing we had to a sitemap.xml/rss list of contents, but now only search.js knows where this file can be found—which is for the better, since it's not supposed to be a public API. But it means a renewed urgency to have a public list of the advertised pages. (By advertised I mean listed in pages or indexed.) As an example use case, I had made a little game on the home page of my pangea website which was using the minisearch.json dataset to display the count of pages and a shuffled random selection of 5 pages to explore.
For the game in question I can replace this with an ad hoc data loader, but it feels like it belongs to this more generic question.

I think we should transpile import.meta.resolve(…) (in addition to import(…)).
Then you could say fetch(import.meta.resolve("observablehq:minisearch.json")) to load the search index.
Also this would allow you to register additional files to download.

I wrote a postbuild script to add a simple sitemap to pangea, with the proper headers that reference it.
https://github.com/Fil/pangea/blob/e179717808c66526d5e17a933245f7fe6b91851b/package.json#L7-L8
https://github.com/Fil/pangea/blob/e179717808c66526d5e17a933245f7fe6b91851b/observablehq.config.ts#L101
It would still be nice to have an easier method to push static/public files, but I think we don't have to have native support for RSS or sitemaps (a helper would be nice, but it can all be done in userland); this issue can now be folded under #169.

For more discussion, see https://github.com/observablehq/framework/discussions/1199#discussioncomment-10561389

authors: Fil mbostock

repo: observablehq/framework

license: ISC


text:
refactor: group CSS classes

Description
Pure refactoring - nest CSS classes by their parent
Motivation and Context
Improve readability and make changes and reasoning about CSS classes in EditTask.scss simpler.
How has this been tested?
Visual test in demo vault.
Types of changes
Internal changes:

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change has adequate Unit Test coverage.

CSS not covered by unit tests

Terms

[x] My contribution follows this project's contributing guide
[x] I agree to follow this project's Code of Conduct

Thank you. I will get the released out and then merge this (since I've created the release notes already...)
You're probably thinking this already, but one thing I've noticed is that some of the CSS for our separate .svelte components is in this top-level .scss file, and perhaps it might be good at some point to move some of this code down to the component-specific .scss files....

Thank you. I will get the released out and then merge this (since I've created the release notes already...)

oh good idea!

You're probably thinking this already, but one thing I've noticed is that some of the CSS for our separate .svelte components is in this top-level .scss file, and perhaps it might be good at some point to move some of this code down to the component-specific .scss files....

Yes, indeed. This is one of the reasons for this PR. We need to group the CSS code by parent classes first, then remove CSS properties assigned to HTML elements like input and select and instead introduce dedicated CSS classes and after that extraction to component-specific files will be obvious and lightning fast.

authors: claremacrae ilandikov

repo: obsidian-tasks-group/obsidian-tasks


text:
OneNote import duplicating images/not importing at all

I'm noticing quite a few issues on my end with OneNote import.

I make a notebook in OneNote and added a section. That section contains one note. That note has some text and three different images.
I select OneNote in Importer and sign in via web browser. Obsidian says "Unexpected Auth event. Please restart the auth process."
I click Import and the progress bar shows. Two error messages pop up saying something like

Cannot copy image002.png, file already exists.
Cannot copy image003. png, file already exists.

I go to the import location and see the attachments folder and the converted page. The attachment folder only contains one image. I open up the note and that one image (image001.png) is now in the note three times, replacing the second and third images with the first.
I decided to try to recreate this with a new note in OneNote. I create a new note in the same section and add some text and three images. I save and exit OneNote, go back to Obsidian Importer and sign in browser again. I click import and now it doesn't even want to import at all. No progress.
I then try to make a new section in OneNote and move that test note to that section. Save and exit OneNote. Sign in on Obsidian Importer and see thay the new section pops up. Click import. Same thing, no progress. it creates a folder location for each section in my vault but no files are imported.
I go back to OneNote. Delete the second section and test note and get it back to where it was with the original note in one section. I then try to import the original note with the three images and now we're back to the issue of only one image importing and replacing the two other instances of images.

I address at least part of your report, the repeated images, in #102 - but some of your other points don't seem to be related to what I reported.

@kepano @p3rid0t Unfortunately this is not quite working as it should with the latest importer update, this is what happens per page that is now imported via OneNote:

That "A complete Mercurial branching strategy.md" directory corresponding to the Page of the same name in OneNote has only 6 images. But the resulting import has 124 files created. That "A succesful Git branching model considered harmful.md" Page has 6 as well, but the directory after import has 113 files created.

repo: obsidianmd/obsidian-importer


text:
Fix breakage in ob shell and ob hoogle

This was caused by #946 which accidentally replaced a use of
runProcess_ with runProc. Similarly named, but different behavior.
Pondering: better way to test ob shell behavior.
Also pondering: better names!
I have:

[x] Based work on latest develop branch
[x] Followed the contribution guide
[x] Looked for lint in my changes with hlint . (lint found code you did not write can be left alone)
[ ] Run the test suite: $(nix-build -A selftest --no-out-link)
[x] Updated the changelog
[ ] (Optional) Run CI tests locally: nix-build release.nix -A build.x86_64-linux --no-out-link (or x86_64-darwin on macOS)

@alexfmpe email me ur contact info so we can stay in touch better!

LGTM. Old behavior is back

Damned github won't let me change my comment to an approval and I noticed too late. Fantastic. Great

authors: alexfmpe madeline-os plt-amy

repo: obsidiansystems/obelisk