text:
Any ways to show Nuxt's error page when a query failed?

I want to call the context.error({...}) to show the Nuxt's error page when a query failed (Item not found, etc.).
In asyncData(context) {...}, we can easily do that as context is always given.
However inside vue-apollo's smart queries, I can't find a way to access the error()

I just found that I can access the error function via this.$root in server-side.
Is it the right (or stable) way?
  apollo: {
    entry: {
      query: ENTRY_QUERY,
      error() {
        this.$root.error({'statusCode': 404, 'message': 'OK'})
      },
      variables: {
          // ...
      },
      prefetch: true,
    }
  },

Hi @ciscorn
I think there are several ways of doing it. I prefer to redirect the user inside of the result hook. But your way is also a possible way of doing it

@dohomi I noticed that my code above (and your suggestion) doesn't work in SSR because the result and error handler are evaluated after SSR has done.

@ciscorn yes we discovered this. Its something you can track inside of vue-apollo it has not necessary something todo with this package.
Try wrap your code in
result({data}){
  this.$nextTick(() => {
     // here you can set context to your component
  })
}

Sorry I think I misread your question. Maybe @Akryum has a good idea how to solve this, I always wait for the result and then redirect the user to error pages

@dohomi Thanks. I think something (such as prefetchResult handler) should be implemented on vue-apollo to serve real 404/302 pages in SSR.

@ciscorn please open an issue inside of vue-apollo package. This package just supersets the usage of vue-apollo and will not add any features to extend vue-apollo

Please ignore if this is irreverent.
I created a modified version of apollo-module just for testing.
https://github.com/ciscorn/apollo-explicit-module
It solves the error/redirect problem and a (potential) concurrency problem without any modifications of Nuxt and vue-apollo. (However it introduces breaking changes.)
Please read a brief explanation in my README.md.

@ciscorn what happens if you use:
  async fetch(context) {
    const result = await contxt.app.apolloProvider.defaultClient.query(YOUR_QUERY_OBJECT)
    // You can call context.error (or redirect) based on the result
  },

 //! without any apollo...

with this package? I do this on some parts and had no issues so far.

@dohomi @Akryum
Nuxt.js has a built-in functionality to return 404/403/302/301 responses with context.error(...) and context.redirect(...). However in the original @nuxtjs/apollo, prefetching is performed after the Nuxt has finished checking the error/redirect flags, so the Nuxt's context.error doesn't work with apollo-module.
(I think #35 is a bit related to the same problem.)
Using my modified version, I can return "real 404/403" responses to clients. I think this is an important aspect of SSR. Redirecting to /404 page or something are not beautiful. We should be able to return 404/403/etc without URL changes and should be able to return error status codes directly (as Nuxt.js kindly supports this.)
  async fetch({app, error}) {
    const prefetchResult = await app.apolloPrefetch(this)
    if (!prefetchResult.article.data.article) {
      error({statusCode: 404, message: "Item Not Found"})
    }
  },

@ciscorn ok I understand now better. @Akryum what do you think about this approach?

@kavalcante @ciscorn haven't had this implementation on my radar yet. You can gain same result with following code:
async asyncData({error, app, params}){
  const article = await app.apolloProvider.defaultClient.query({
    query: `someGql`,
    variables:{id: params.id}
  }).then(({data}) => data && data.Article)
  if(!article){
    return error({statusCode: 404, message: 'Not found'})
  }
  return {article}
}

Is there any reason why not using asncData directly, you would write actually less code to receive the same result. Setting up a fetch method is slightly redundant in my eyes. I'm not sure if its straight forward to decouple the query call and add the fetch statement to it. @Akryum I'd still be interested if you have any opinion as you have better knowledge in the vue-apollo client.

@dohomi One major reason to do ciscorn's implementation is that with your solution I have to do a query.   Given this basic example of routing :
Pages
/product
_id.vue
The query is always sent before I can validate or asyncData (fetch isn't even invoked SSR).  All I'd like to do is if there is no param provide re-route to the home page or something, but I can't if apollo is included in the component.  It maybe a bug in vue-apollo and I'm going to go submit it there as well.  But it makes sense here because nuxt includes server side and can pre-empt the query on an in-valid url.

My solution is a kind of dirty hack to avoid using beforeNuxtRender.
It would be the best if we can set up a hook here.

As version 4 follows now a different approach I will close this issue. Most likely it does not solve your issue but maybe the best way would be to run a separate module for it.

@dohomi, you mention a new approach as of version 4, but I'm not sure where to find more information on that approach. Would you mind pointing me towards some docs?
Thanks for all your work on @nuxtjs/apollo!

@aaronransley whats the exact issue you are facing?

I see this issue is closed, does that mean smart queries are officially discouraged in favor of asyncData?
Right now I don't see a way to set the HTTP status code from the server side using a smart query, so instead we must use context.app.apolloProvider.defaultClient.query; definitely less elegant

+1 Definitely would like to see this in the smart query as well.

It is also important to note that if you using asyncData, the the data will not update with mutations.

authors: JRobber aaronransley ciscorn dohomi jsbroks mccxiv sebmor

repo: nuxt-community/apollo-module


text:
nuxt/i18n custom route paths doesn't work

Environment
My nuxt and i18n version are:
"@nuxtjs/i18n": "^8.3.0",
"nuxt": "^3.10.1"
Reproduction
It's my github repo: https://github.com/Gizem346/i18n-testing
and stackblitz reproduction link is here : https://stackblitz.com/~/github.com/Gizem346/i18n-testing
Describe the bug
Current locale is: en
When i change language as deutch, also i want to change url path as de/uber-uns and de/kontaktiere-uns but it doesn't.
When I manually type the address de/uber-uns into the search bar, I can access the page, but not when I change it via links.
Here is nuxt/i18n custom route paths documantation: https://i18n.nuxtjs.org/docs/guide/custom-paths
What is Expected?

de/uber-uns
de/kontaktiere-uns

What is actually happening?

de/about-us
de/contact-us

Additional context
No response
Logs
No response

First of all, thank you for your contribution.
Yes, when I updated it as you said, I saw that the url changed depending on the link I clicked. Thanks a lot
Expected: de/uber-uns
Obtained: de/uber-uns
But before, when I manually typed de/uber-uns in the search bar, I could see the "Uber Uns" page in RouterView. Now I can't see the relevant pages even though the router has changed.

Sorry for the very late response, I just took another look at your reproduction, hopefully you already managed to figure it out on your own.
In your reproduction project you're not exactly making full use of the i18n module features. Each page will be used by the module to generate a localized version and by using the translation functions provided by vue-i18n these pages will render the correct translations.
I have modified your reproduction project to demonstrate here, please note the files in pages and the usage of translation functions. I think this should resolve your issue so I'll close this for now, but please let me know if you have any questions and I'll make sure to have a quicker response 🙏

thanks a lot @BobbieGoede , actually what i want to do is exactly this; i don't want to translate pages, i want to have two different .vue files named about-us and uber-uns and i want the user to change between them (change the route).
I don't want to translate pages.
For example, let's say 'en' is selected, the user is on the about-us page and wants to switch to uber-uns which is in German ('de'), when he clicks on uber-uns the page should switch to uber-uns.vue instead of being translated.
I'm not sure if it is possible to do this in nuxt-i18n, what do you think?

You can achieve something similar by using the modified reproduction's setup, except having a component per language. It needs to be a single Vue page file if you want to make use of the custom routes feature.
<!-- about-us.vue -->
<script setup>
const { locale } = useI18n();
</script>

<template>
  <AboutUsEnglishComponent v-if="locale === 'en'" />
  <AboutUsGermanComponent v-if="locale === 'de'" />
</template>

Is there any particular reason why you don't want to use the translate functions?

thanks again @BobbieGoede , i will try .
And yes, the reason is that we may need to customize the design a bit more for German and other additional languages on our website. When English and German and other languages are translated, it can cause distortions in the design due to word lengths or similar reasons.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
feat!: new icon approach

This PR introduces a brand new icon approach that works much better with SSR (no flicking on the client side) and should help reduce the load of Iconify's public API by a lot.
Breaking Changes

<Icon> and <IconCSS> is merged together, use <Icon mode="svg"> and <Icon mode="css">
<Icon> now default using css mode, (set icon.defaultMode: 'svg' to use the previous beahvor
<IconCSS> component is removed
Emoji-as-name is no longer supported
Slot fallback is not supported yet
App config key changed from nuxtIcon to icon
App config schema changes

iconifyApiOptions has been removed
iconifyApiOptions.url -> iconifyApiEndpoint
iconifyApiOptions.publicApiFallback -> fallbackToApi (default: true)

New Features

Support loading icons for local icons folder, close https://github.com/nuxt-modules/icon/issues/131

Approaches

Create a /api/_nuxt_icon/ endpoint that will serve the icons from server-bundle, or fallback to Iconify API (fallback to use public API when ssr:false
CSS Mode: <Icon name="icon-name" mode="CSS" /> will render the icon as a CSS class, SSR is supported by injecting compiled CSS into HTML.

On the client side, it will look up the registered CSS selectors. If the class is already presented, it will skip icon rendering (compatible with pre-compiled UnoCSS icons-as-css solution, TW support is still in research)

SVG Mode: <Icon name="icon-name" /> component will use useAsyncState to fetch the icon data from the server (local fetch when SSR) and force Iconify to render the icon to SSR. Hydrate the data back on client side.

For dynamic icons that are presented on the server side, no client request will be made.
For dynamic icons that are presented only on the client side, a client request to /api/_nuxt_icon/ will be made to fetch the icon data (cached event handler).

TODOs

[ ] Update docs

@antfu Would that be pertinent to add an option to append aria-hidden="true" on every icon?

Maybe a defaultAttrs option in the app config, what do you think?

I'm not sure it's a good idea for @nuxt/ui to configure this for all icons but this could be a nice addition anyway for nuxt-icon users 😊

Alright, I think it should be good to go for a few beta releases.

(set icon.defaultMode: 'svg' to use the previous beahvor)

its icon.defaultMode: 'svg' or icon.mode: 'svg' 😅

source: gharchive/pull-request

authors: antfu benjamincanac gitFoxCode

repo: nuxt-modules/icon


text:
Is there any option to enable multi-language switch in header menu like nuxt/content-theme-docs ?

Cannot find how to setup multi-language in docs

i guess its better move to nuxt/content. since this project seems early alpha and the documentation is fcked up.

authors: OxyzOne ROBJkE

repo: nuxt-themes/docus


text:
Generate only routes provided in generate.routes

It appears that the behavior has changed from completely ignoring filesystem API for generate if routes are provided to concatenating the user-supplied and generated routes? (in lib/builder/generator.js)
How can I only generate some routes?
(also, that should include generating no HTML by explicitly passing an empty array)

Did you try the router module? https://github.com/nuxt-community/router-module

@robyedlin doesn't that require manually specifying the component for each route?

According o documentation:

This module disable the pages/ directory into Nuxt and will use a router.js file at your srcDir directory

Yes, is required manually specifying the component for each route.

If for some reason we want to maintain compatibility with the current behavior of concatenating manual and generated routes, taking a function, like extendRoutes does, would be ideal.
{ build: {
  routes: function(routes) {
  // muahaha, we ignore you, generated routes!
  return ['/about']
}}

Hi,
We decided to set routes to add the dynamic routes ignored by nuxt generate. If you want to generate only a specific route, I recommend you to use Nuxt.js programmatically since it will avoid you to run nuxt generate every time and wait for the build time.

authors: Atinux qm3ster rAugustos robyedlin


text:
Error failing to load CSS/JS chunk after every new deployment.

Versions

nuxt: v2.14.1
node: 12

Reproduction

Additional Details
This is related to https://github.com/nuxt/nuxt.js/issues/6982 which was marked resolved, however other users appear to still be experiencing similar issues after the supposed fix in 2.12.2
Unable to provide repro site due to commercial sensitivity.
The bulk of our Sentry logs suggest this might be a Safari/iOS issue, although there are a few Windows 10/IE Edge instances.
nuxt.config.js
  mode: 'spa',
  srcDir: 'src/',

  head: {
    titleTemplate: '',
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { name: 'title', content: '' },
      { name: 'og:title', content: '' },
      { name: 'og:site_name', content: '' },
      { name: 'apple-mobile-web-app-title', content: '' },
      {
        hid: 'description',
        name: 'description',
        content:
          ""
      }
    ],
    link: [{ rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }]
  },
  typescript: {
    typeCheck: {
      eslint: true
    }
  },
  pwa: {
    manifest: {
      name: '',
      short_name: '',
      description: ""
    }
  },

  customProperties: true,

  css: ['@/assets/scss/main.scss'],

  plugins: [
    { src: '~/plugins/localStorage', ssr: false }
  ],

  buildModules: [
    '@nuxt/typescript-build',
    'nuxt-typed-vuex',
    '@nuxtjs/google-analytics',
    '@aceforth/nuxt-optimized-images',
    '@nuxtjs/pwa',
    'nuxt-babel',
    '@nuxtjs/style-resources'
  ],

  modules: ['@nuxtjs/sentry'],

  router: {
    middleware: 'router'
  },

  optimizedImages: {
    handleImages: ['jpeg', 'png', 'svg', 'webp', 'gif'],
    optimizeImages: true,
    optimizeImagesInDev: false // disable in dev to reduce compile time
  },

  styleResources: {
    scss: [
      '~/assets/scss/_settings.typography.scss',
      '~/assets/scss/_settings.breakpoints.scss',
      '~/assets/scss/_settings.buttons.scss',
      '~/assets/scss/_tools.mixins.scss'
    ]
  },

  build: {
    extractCSS: process.env.NODE_ENV === 'production',
    extend(config, ctx) {
      if (ctx.isDev && ctx.isClient) {
        config.module.rules.push({
          enforce: 'pre',
          test: /\.(js|vue)$/,
          loader: 'eslint-loader',
          exclude: /(node_modules)/
        })
      }

      config.module.rules.use = {
        loader: 'url-loader',
        options: {
          limit: 8192
        }
      }
    },

    transpile: [/typed-vuex/],

    plugins: [
      new BundleAnalyzerPlugin({
        analyzerMode: 'static',
        openAnalyzer: false,
        defaultSizes: 'gzip',
        reportFilename: 'webpackBundleReport.html'
      })
    ]
  }
}

Steps to reproduce

Deploy production build
User goes to page and sees an infinite loading spinner on the page (only hard refresh fixes)

What is Expected?
App functions without interruption after a deployment.
What is actually happening?
An infinite page spinner appears and remains even after a page refresh. A hard cache clear fixes the issue. Problem reoccurs after the next deployment.
Browser console errors (not necessarily appearing at the same time):
ChunkLoadError Loading chunk 19 failed. (timeout: /_nuxt/pages/index.23e1e4a.js)
Loading CSS chunk 19 failed. (/_nuxt/pages/index.633102b.css)

Same issue when deploying on Digital Ocean with App Plateform.

I have also very hard times with the "infinity spinner" problem after updating from Nuxt 2.0.0 to 2.14.6.
Spinner only browsers I found:

all version iOS, Safari and FF all versions
W10, Firefox 77 and older. 77 shows me in console SyntaxError: invalid regexp group in file beginning with window.webpackJsonp
W10, IE 11

Other strange issues I encounter after updating to the latest Nuxt:

latest Chrome and FF crashes to an error page saying "Uncaught (in promise) TypeError: Cannot read property 'store' of undefined".

Both are critical bugs!

It has something to do with invalid regexs. Both FF and Chrome crash on regex errors. For example, the first working Firefox is 78 that adds "New RegExp engine in SpiderMonkey, adding support for the dotAll flag, Unicode escape sequences, lookbehind references, and named captures."

I have also very hard times with the "infinity spinner" problem after updating from Nuxt 2.0.0 to 2.14.6.
Browsers that suffer infinite spinner:

all version iOS, Safari and FF all versions

Firefox 77 and older. 77 shows me in console SyntaxError: invalid regexp group in file beginning with window.webpackJsonp

Chrome 61 and older

IE 11 (console shows nothing)

Beside this, latest Nuxt suffer another serious bug. It somehow break JS and and in my case on latest Chrome and FF causes crashing to an error page saying "Uncaught (in promise) TypeError: Cannot read property 'store' of undefined".

Both are critical bugs!
You can see it in action on https://snippets.documatt.com. But only for a short time, because I will downgrade to old Nuxt.

This looks like a related, but separate issue to the original issue documented.

Yes, they are related. However, I'm not skilled enough to say something valuable. If you are, I created a minimal demo that suffers both errors ("SyntaxError: invalid regexp group" and "ChunkLoadError: Loading chunk 2 failed.") because I'm going to downgrade the website https://snippets.documatt.com where I discover these bugs back to old Nuxt where everything worked perfectly.
The crashing Nuxt is at https://gitlab.com/mattdocumatt/nuxt-infinite-spinner-bug-demo. Keep in mind you have to visit it with few months old browser versions to see the bugs.

One more detail: now I discovered it works in anonymous mode! Can anybody explain this mess?!

One more detail: now I discovered it works in anonymous mode! Can anybody explain this mess?! @Atinux?

Because in Anonymous mode, it automatically clears your cache.

One more detail: now I discovered it works in anonymous mode! Can anybody explain this mess?! @Atinux?

Because in Anonymous mode, it automatically clears your cache.

What does it mean? What is causing these errors?

Is anybody from the core team interested that, under certain and unknown conditions, Nuxt doesn't work in the majority of browsers and devices? This is a show-stopper error. I can't do more than only urge @Atinux @alexchopin @pi0 @bdrtsky... :-(

@mattdocumatt From what you've said, I would investigate your service worker setup.

@mattdocumatt From what you've said, I would investigate your service worker setup.

I have only a brief understanding of service workers. In Chrome on page chrome://serviceworker-internals/ I don't see snippets.documatt.com listed, i.e. my web didn't register a service worker. Is that correct or not? Actually, I don't touch any single line in files generated by npx create-nuxt-app except adding few new dependencies.

authors: Icesofty danielroe mattdocumatt simondib


text:
feat(webpack): allow function entries for build.transpile

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

It's mostly a feature for module, thinking of @nuxt/http for example that need to add ky in build.transpile but only for legacy mode.
Before:
{
  build: {
    transpile: ['ky']
  }
}

After:
{
  build: {
    transpile: [
      ({ isModern }) => isModern ? null : 'ky'
    ]
  }
}

The main issue I see is that module author will have to check Nuxt version to be able to push a function in build.transpile otherwise it justs breaks 😢
Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[x] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

The main issue I see is that module author will have to check Nuxt version to be able to push a function in build.transpile otherwise it justs breaks cry

This is a feat/fix by next release. Nothing will be breaking.

Some other enhancements we could do is adding an option like transpileLegacy or allow object form like { name: 'ky', legacy: true } or { name: 'ky', modern: false }

I also thought of keeping a string directly and do something like legacy:ky, WDYT?

Codecov Report

Merging #6120 into dev will decrease coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #6120      +/-   ##
==========================================
- Coverage   95.77%   95.74%   -0.03%
==========================================
  Files          80       80
  Lines        2651     2657       +6
  Branches      678      682       +4
==========================================
+ Hits         2539     2544       +5
- Misses         96       97       +1
  Partials       16       16

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.84% <75%> (+0.03%)
:arrow_up:

#unit
92.43% <100%> (-0.03%)
:arrow_down:

Impacted Files
Coverage Δ

packages/webpack/src/config/base.js
94.89% <100%> (+0.16%)
:arrow_up:

packages/webpack/src/config/server.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
93.49% <0%> (-0.82%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ac00f7a...9eaa409. Read the comment docs.

@clarkdo Making build.transpile a function will be harder for modules author to extend it I guess, this is why I thought about handling a push as a method (see https://github.com/nuxt/http/commit/2ce08de2ecceda27d362982eebdf0f15470f7fee#diff-d1234a869b3d648ebfcdce5a76747d71R100)

Ready to review

authors: Atinux codecov-io pi0


text:
Modules should be resolved with import condition

Currently we do resolve modules with _require.resolve  this makes modules not working if they use exports like this:
"exports": { "import": "./dist/module.mjs" }

Leading to an error like this:
 Cannot start nuxt:  No "exports" main defined in

Current workaround is modules exporting without condition like "exports": "./dist/module.mjs".
We should adopt mlly.resolveModule to solve this. And also need to continue search if a nuxt module is only resolvable with CJS condition.
Related: https://github.com/nuxt/nuxt.js/issues/11858

Linking (as partly implemented in) https://github.com/nuxt/nuxt/pull/19608, https://github.com/nuxt/nuxt/pull/19537, https://github.com/nuxt/nuxt/pull/19635.
There is likely some follow-up work to do.

repo: nuxt/nuxt


text:
Cannot find module ../middleware in ./.nuxt/nuxt-i18n/middleware.js

Environment
npx envinfo --system --npmPackages '{nuxt,@nuxt/*}' --binaries --browsers
Reproduction
I am sorry but as this is a project for my company I cannot share whole code, though I will describe it.
Describe the bug
So my package.json dependencies looks like this:
  "dependencies": {
    "@nuxtjs/axios": "^5.13.6",
    "@nuxtjs/gtm": "^2.4.0",
    "@nuxtjs/i18n": "^7.3.1",
    "bootstrap": "^4.6.0",
    "core-js": "^3.8.3",
    "nuxt": "^2.16.2"
  },

So whenever I run npm run dev(build) there is added new folder to .nuxt folder which is nuxt-i18n. In that folder I have a file named middleware.js which looks like this:
// @ts-ignore
import nuxtMiddleware from '../middleware'

/** @type {import('@nuxt/types').Middleware} */
const i18nMiddleware = async (context) => {
  const { app, isHMR } = context

  if (isHMR) {
    return
  }

  const [status, redirectPath, preserveQuery] = await app.i18n.__onNavigate(context.route)
  if (status && redirectPath) {
    const query = preserveQuery ? context.route.query : undefined
    context.redirect(status, redirectPath, query)
  }
}

nuxtMiddleware.nuxti18n = i18nMiddleware

. So and the error on build is: ❯ log friendly-errors › This relative module was not found:
❯ log friendly-errors › * ../middleware in ./.nuxt/nuxt-i18n/middleware.js .
Therefore as there is realy not that module in .nuxt I am facing an error that unless I delete first and the last row of the code my app won't build at all. I tried with different versions of node ( 14.15, 10.21, 16.9, 18.1...) Any help would be appreciated :)
Additional context
No response
Logs
No response

This looks like an issue with @nuxtjs/i18n rather than Nuxt. Maybe you could raise an issue there instead?


text:
[Form] Input events validate-on code example missing.

Environment
Operating System: Windows_NT
Node Version: v20.18.0
Nuxt Version: -
CLI Version: 3.14.0
Nitro Version: -
Package Manager: unknown
Builder: -
User Config: -
Runtime Modules: -
Build Modules: -
Version
v3.0.0-alpha.6
Reproduction
Cannot use v3 on stackblitz so no repo.
Description
There is no code example for the validate-on prop. Like how do I stop blur,input and change validations?
https://ui3.nuxt.dev/components/form#input-events
Additional context
No response
Logs
No response

@benjamincanac Is it currently possible to do PR requests for v3 docs?

Closing this as there is actually an example on the docs: https://ui3.nuxt.dev/components/form#input-events.

authors: benjamincanac onurusluca

repo: nuxt/ui


text:
ESLint is broken as soon as WebpackBar is added as a plugin

Operating System: Ubuntu
Node Version: 9.9.0
NPM Version: 5.6.0
webpack Version: 4.6.0
eslint Version: 4.19.1
webpack-serve Version: -

This issue is for a:

[x] bug
[ ] feature request
[ ] modification request

Code
CLI Command
yarn run lint

webpack.config.js
https://github.com/nobt-io/frontend/blob/f71c5079d3b35a1389ce5d7425c090b1963a9823/webpack.config.js
.eslintrc.js
https://github.com/nobt-io/frontend/blob/f71c5079d3b35a1389ce5d7425c090b1963a9823/.eslintrc.js
Expected Behavior
ESLint runs as usual
Actual Behavior
ESLint reports at lot of errors because it fails to resolve imports
How Do We Reproduce?

git clone https://github.com/nobt-io/frontend
git checkout feature/webpackbar
yarn install
yarn run lint

Lint fails.

git checkout HEAD^1
yarn run lint

Lint succeeds.
If you look at the commit, nothing else is changed besides adding the webpackbar plugin.
I think it has something do with the referencing the webpack config in .eslintrc.js. However, I don't understand why adding WebpackBar changes any of that.

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

Why is this auto-closed?

repo: nuxt/webpackbar


text:
Number of channels for mask for binary segmentation

Hi,
Thanks for releasing the code!
Just a silly question:
I have no experience with GANs and the loss functions employed so I was wondering if the optimization process works better when binary masks are given in two channels or just with one  (0:background, 1:Region of interest). For example for the X-Ray problem, how do you feed the model?
Thank you!

Hi, Thanks for releasing the code! Just a silly question: I have no experience with GANs and the loss functions employed so I was wondering if the optimization process works better when binary masks are given in two channels or just with one (0:background, 1:Region of interest). For example for the X-Ray problem, how do you feed the model?
Thank you!

same question,have you fixed it?

I tried both and I got slightly better FID scores (same initialization) with two channels but I haven't tried a proper evaluation on the subject. Some operations are more numerically stable employing two channels but in this case, I haven't checked in detail.
Let me know how it works for you!

Hi @PeterMcGor , no problem at all and sorry for the late reply. If you have a region of interest, you can apply a mask when doing inverse optimization where only the region of interest is reconstructed/segmented. In this case, depends on your use case, you might want to evaluate it by the task performance.

authors: PeterMcGor lidaiqing zeta7337


text:
Image control in Xaml without specified Source causes Wasm error

<Image Name="imageIntegratedButton" Stretch="Fill" Opacity="0.7"/>
The above code causes the following Wasm error:
Uno.UI.js:258 Error:  attribute height: Expected length, "NaN".
setAttribute @ Uno.UI.js:258
(anonymous) @ VM3147:1
ASM_CONSTS @ mono.js:1
...
The following code works:

Source : https://gitter.im/uno-platform/Lobby?at=5b48a3c91c0f906b144f4152
Occurring when there's no source on the image.

This issue has been fixed in recent updates, thanks!

authors: carldebilly jeromelaban zipswich

repo: nventive/Uno


text:
[Specific to branch feature/SupportAndroid13] Android 13 does not display Splashscreens

Expected Behavior
Upon opening the application, the splashscreens should display correctly.
Actual Behavior
Upon opening the application, the splashscreens are not displayed correctly.
Steps to Reproduce the Problem

Build the application and deploy it on an Android device or emulator.
Open the app.
Look at the welcome and log in pages.

Specifications

Version: Android 13
Platform: Android devices
Subsystem:

Image

Link of branch
https://github.com/nventive/UnoApplicationTemplate/tree/feature/SupportAndroid13

Do you have any video or GIF file?

Do you have any video or GIF file?

@Soap-141 No but I have a picture.

@Soap-141 A picture was added in the description above.

@Soap-141 To me, the app worked fine, it was just every splashscreen that was not displayed correctly.

Is it only on the first installation?

@Soap-141 What do you mean? I can also retest it one more time with the application uninstalled and with git clean -fdx. I can get back to you.

@nguyeenvy Add a link to the branch that reproduces this issue. 😀

@Soap-141 What do you mean? I can also retest it one more time with the application uninstalled and with git clean -fdx. I can get back to you.

Meant that if you restart the application does it happen again?

@Soap-141 So I just deleted the app from my device and I redeployed it, and I did not get the issue. When I restart the application, I also don't have the issue anymore.

@nguyeenvy @jeanplevesque Looks like a .NET 6+ issue. Happens to me sometime every assets in like random and misplaced. Closing the issue for now.

authors: Soap-141 jeanplevesque nguyeenvy

repo: nventive/UnoApplicationTemplate


text:
🛑 NVIDIA AI Enterprise Hub is down

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

HTTP code: 0
Response time: 0 ms

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

repo: nvgsg/lab-upptime


text:
🛑 Kubeflow ML Platform is down

In 99139cd, 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 8260afa.


text:
🛑 Kubeflow ML Platform is down

In 7522dd5, 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 3dce181.


text:
🛑 Kubeflow ML Platform is down

In d811b25, 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 598ac9f.


text:
🛑 Kubeflow ML Platform is down

In 6a0112d, 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 91b7c02.


text:
Add mv/cp commands that take typed input

The error message:
[WARN] ...nvim/lua/neo-tree/sources/filesystem/lib/fs_actions.lua:263 Could not rename the files

https://user-images.githubusercontent.com/24765272/153801933-25030e6c-7f9a-49d3-b16f-0957136daf27.mov
debug Info.
NVIM
NVIM v0.7.0-dev+1082-g046950f63
Build type: Release
LuaJIT 2.1.0-beta3

tested on
neo-tree.nvim commit: d20d630

I've added new mappings for filesystem:
        ["y"] = "copy", -- takes text input for destination
        ["m"] = "move", -- takes text input for destination

which will behave the way you want. You can also just change your r mapping to the new "move" command.

Sorry for my late reply, was busy about Unity things. Let me check this now :)

You can also just change your r mapping to the new "move" command.

It's a great success. Very satisfying result to me :) Let me close this now!

authors: cseickel nyngwang


text:
FEATURE: K to move cursor to the first file in the opened directory, J - to last

Did you check the docs?

[X] I have read all the docs.

Is your feature request related to a problem? Please describe.
no problem, just feature request
Describe the solution you'd like.
suppose I am in
 nixos
│  home
│  modules
│  pkgs
│  root
│ │  environment
│ │ └  default.nix
│ │  fonts
│ │  services
│ │  shells
│ │  systemd
│ │  users
│ │  zsh
│ │  configuration-generated.nix
│ │  default.nix
│ └  hardware-configuration.nix

cursor on [s]ystemd
clicking K - would bring me to [e]nvironment
Describe alternatives you've considered.
this dont work
  -- Add custom mappings for jumping to the first and last files
   opts.window.mappings["J"] = function(state)
     local children = state.tree:get_nodes()
     if children and #children > 0 then
       local last_child = children[#children]
       require("neo-tree.ui.renderer").focus_node(state, last_child)
     end
   end

   opts.window.mappings["K"] = function(state)
     local children = state.tree:get_nodes()
     if children and #children > 0 then
       local first_child = children[1]
       require("neo-tree.ui.renderer").focus_node(state, first_child)
     end
   end

Additional Context
No response

didit
local function log_to_file(content)
  local log_file = "/tmp/neo-tree-debug.log"
  local file = io.open(log_file, "a")  -- Open in append mode
  if file then
    file:write(content .. "\n")
    file:close()
  else
    print("Error opening log file!")
  end
end

function focus_some_file(mylambda)
  return function(state)
    local log = require("neo-tree.log")

    -- Get the current node
    local tree = state.tree
    local success, node = pcall(tree.get_node, tree)
    -- log_to_file(vim.inspect(success))
    -- log_to_file(vim.inspect(node))

    if not (success and node) or node.type == "message" then
      log.debug("Could not get node.")
      return
    end

    -- Get the parent directory of the current node
    local directory = tree:get_node(node:get_parent_id())
    if not directory or directory.type ~= "directory" then
      log.debug("No parent directory found.")
      return
    end

    -- Get the children of the directory (files or subdirectories)
    local children = directory:get_child_ids()
    -- log_to_file(vim.inspect(children))
    if not children or #children == 0 then
      log.debug("No other files in directory.")
      return
    end

    -- Use the passed lambda function to determine which file to focus
    local target_child_id = mylambda(children)
    -- log_to_file(vim.inspect('target_child_id', target_child_id))

    if not target_child_id then
      log.debug("Could not get target node.")
      return
    end

    -- Focus the selected file
    local renderer = require("neo-tree.ui.renderer")
    renderer.focus_node(state, target_child_id, true)
  end
end

return {
  "nvim-neo-tree/neo-tree.nvim",
  opts = function(_, opts)
    -- opts.filesystem.hijack_netrw_behavior = "open_default"
    opts.filesystem.filtered_items = opts.filesystem.filtered_items or {}
    opts.filesystem.filtered_items.visible = true
    opts.filesystem.filtered_items.hide_dotfiles = true
    opts.filesystem.filtered_items.hide_gitignored = true
    opts.filesystem.filtered_items.hide_by_name = { "node_modules", ".git" }
    opts.filesystem.filtered_items.never_show = { ".DS_Store", "thumbs.db", "desktop.ini" }

    opts.filesystem.follow_current_file.leave_dirs_open = true

    opts.commands["focus_first_file_in_directory"] = focus_some_file(function(x) return x[1] end)
    opts.commands["focus_last_file_in_directory"] = focus_some_file(function(x) return x[#x] end)

    opts.window.position = "left"
    opts.window.width = 40

    opts.window.mappings["K"] = "focus_first_file_in_directory"
    opts.window.mappings["J"] = "focus_last_file_in_directory"
    opts.window.mappings["<cr>"] = "open_with_window_picker"
    opts.window.mappings["o"] = "split_with_window_picker"
    opts.window.mappings["O"] = "vsplit_with_window_picker"
    opts.window.mappings["s"] = false
    opts.window.mappings["S"] = false
    opts.window.mappings["/"] = false
    opts.window.mappings["f/"] = "fuzzy_finder"

    -- don't steal from 'zz'
    opts.window.mappings["z"] = nil
    opts.window.mappings["Z"] = "close_all_nodes"
    opts.window.mappings["zz"] = function(state) vim.cmd("normal! zz") end

    opts.window.mappings["a"] = {
      "add",
      -- this command supports BASH style brace expansion ("x{a,b,c}" -> xa,xb,xc). see `:h neo-tree-file-actions` for details
      -- some commands may take optional config options, see `:h neo-tree-mappings` for details
      config = {
        show_path = "relative", -- "none", "relative", "absolute"
      },
    }

    -- opts.window.mappings["Yf"] = opts.window.mappings["Y"]
    -- opts.window.mappings["Y"] = nil
    -- opts.window.mappings["Yr"] = {
    --   function(state)
    --     local node = state.tree:get_node()
    --     local path = node:get_id()
    --     -- local root = require("lazyvim.util").root.get()
    --     local relative_path = vim.fn.fnamemodify(path, ":.")
    --     -- if vim.startswith(relative_path, root) then
    --     --   relative_path = vim.fn.fnamemodify(relative_path, ":s?" .. root .. "/??")
    --     -- end
    --     vim.fn.setreg("+", relative_path, "c")
    --   end,
    --   desc = "Copy Root relative path to Clipboard",
    -- }

    opts.source_selector.sources = {
      { source = "filesystem", display_name = "󰉓 Files" },
    }
  end,
}


text:
feat: prompt title accepts string or function

Motivation
When I'm navigating in different folders I want to see the name of the current folder listed in the finder's prompt title.
Implementation
Expose prompt_title option as function or string.
If a function is passed, it will be evaluated with current finder as parameter.
If a string is passed, its value is set to the finder.
If not defined, the default value is a function that will output a string with the current path relative to the cwd of the finder.
A opts.prompt_title_fn field is added to store the function. This is due to telescope/plenary expecting a string in the prompt_title option
Preview
Command Telescope file_browser previewer=false theme=dropdown follow=true path=%:p:h

Kapture 2022-06-30 at 15.41.50.webm

Thanks for your PR!
Looks like a cool feature at first glance. I'll review your PR hopefully some time next week, as I'm travelling for the remainder of this one.

Sounds good to me. So we have the follow as default be behaviour unless the user defines the title?
I'll add some changes later!

No, default should not change per se.

Default of that function is what's currently in fb_utils.redraw_border_title

Was meant as a reference to master. I'm unfortunately only on mobile until mid next week. If I recall correctly (apologies if that's wrong), follow is mostly useful when only the prompt title is shown (like for dropdown theme) and utility is otherwise largely void.
In other words, titles should be string|function such that follow would primarily be one function example to implement (and be referred to on the wiki).
Hope that makes sense.

For those not patient enough to wait for this PR to get merged, here's a small hack that you can use right now in your config:
local file_browser = telescope.extensions.file_browser
local fb_utils = require("telescope._extensions.file_browser.utils")
local redraw_border_title = fb_utils.redraw_border_title
fb_utils.redraw_border_title = function(current_picker)
  local Path = require("plenary.path")
  local finder = current_picker.finder
  if current_picker.prompt_border then
    local parent = Path:new(finder.cwd):parent().filename
    local new_title = Path:new(finder.path):make_relative(parent)
    if parent == finder.path then
      new_title = parent
    end
    current_picker.prompt_border:change_title(new_title)
  end
  redraw_border_title(current_picker)
end

local picker = file_browser.file_browser
file_browser.file_browser = function(opts)
  local Path = require("plenary.path")
  local parent = Path:new(opts.cwd):parent().filename
  opts.prompt_title = Path:new(opts.path):make_relative(parent)
  picker(opts)
end

@fdschmidt93 sorry for the long time with this PR!
I have made the changes but for some reason I don't see the redraw_border_title being called when changing folders in the finder, what am I missing to trigger it so the function can be evaluated again?

It's fixed. Let me know if we need some rephrasing for the docs or updates in any other file

By the way, is there a way to query the width of the title so that we can trim the title optimally?
Plenary trims the end of the path like this: long/paths/gets/tri... by default, which makes it not very useful for longer paths.

@protiumx sorry for not having had a look at this more in depth, on a high level, the PR is fine, I'd probably eventually do some clean up for personal nits I'd have. Nothing to worry about. I'm currently more focused on #210.

By the way, is there a way to query the width of the title so that we can trim the title optimally? Plenary trims the end of the path like this: long/paths/gets/tri... by default, which makes it not very useful for longer paths.

You can always get the prompt buf with the get_prompt_buf util in make_entry.lua. Then,
  local prompt_border_win = require "telescope.state".get_status(prompt_bufnr).prompt_border_win
  local prompt_win_width = vim.api.nvim_win_get_width(prompt_border_win)

and use align_str I think from plenary.strings to left-truncate the title.

Ah, to clarify, I meant to trim it by creation. Since the window isn't created yet, there's no way to check its width.
Maybe the title can be set somewhere after creation?

The PR would have to support that then I guess. You could always embed a defer call or something I guess to recall setting the title for the time being or something along these lines. For the time being, I'd refer to OP though.

I'd probably eventually do some clean up for personal nits I'd have
If you give me some directions I could implement them. I'm not very happy with this code https://github.com/nvim-telescope/telescope-file-browser.nvim/pull/155/files#diff-57d81f1b1356358e13623948fb3fc7825d9d650aa7c776933e47cfa0bb9cb7b1R104-R112

Perhaps it makes sense we always have a function. If user pass a function, we use that. If user passes a string, we wrap the string in a function. Else we default to the prompt_title_fn.

Ah, to clarify, I meant to trim it by creation. Since the window isn't created yet, there's no way to check its width.
Maybe the title can be set somewhere after creation?

It would be neat to add this to the default Fn but I don't know what would be the best approach. I think it would be better if telescope itself does a left trim or provides an option to trim it since every other extension would have the same problem.
I'd prefer we close this with the working feature and think about trimming in another PR or request a feature in telescope

This looks to be changing the current default behavior of the prompt title from what I can tell ('File Browser' and 'Folder Browser' depending on which finder you're using).
This new option seems reasonable but I'd like to preserve the current default behavior otherwise it is a semi-breaking feature.
Depending on the theme you use, having the path in the prompt title is redundant as the result title can already display the current path.

Based on @jamestrew comment I'd suggest this PR adds support for prompt_title: string|function
And provide the promp_title_fn as an example in the docs. Thoughts?

I think that could work. I am however wondering how much value exposing the prompt_title option as something which can take a function would bring.
Maybe all we need is a new option something like prompt_title_show_path (default: false). I think this would simplify things for users if they do want the path in the prompt title and they wouldn't have to dig too much into docs or write their own functions.
I don't know, what do you think?
Maybe you can convince me of other use cases but I think 99% of people would just want either:

"File/Folder Browser" depending on current finder (current default behavior)
some static string (supported currently with the default telescope prompt_title option)
current path (what this PR would enable)

And having a boolean option would just be easier for users and we'd be able to largely reuse the code for the results_title.

Sounds good. I've been using this extension for quite a while now and didn't come up with other use for the prompt title, I just find it useful to always show the full relative path of the current folder, as initially planned on this PR (a follow option).
So to sum this up:

I will add prompt_title_show_path (default: false). It could also be show_path imo
When enabled the prompt title will show the current path of the file browser
If agreed I'll add the changes during the week.
I only need some guidance to deal with truncating the path to fit the window. I guess I can take a look at the implementation of this https://github.com/nvim-telescope/telescope.nvim/blob/master/doc/telescope.txt#L262

Sounds good.
I think show_path isn't specific enough since the current behavior already shows the path in results_title on most themes/layouts.
As for the truncating of the path... I kinda don't want to worry about it :sweat_smile:
But if it's frequently cutting off paths for you then yeah maybe making the option something like prompt_title_path_display table: display current path in prompt title using telescope.defaults.path_display options (default: {})
You can then do something like
require'telescope.utils'.transform_path({path_display = opts.prompt_title_path_display}, path)

Closing this, it's been a while and I ended up dropping the feature from my personal config as I don't set a prompt title in all the pickers I use

authors: fdschmidt93 jamestrew musjj protiumx


text:
Show virtual text in context line

It would be great if when your context line has virtual text on it, that virtual text gets rendered on the context line as well
This would allow LSP errors and type hints to show along with test results in neotest for example.
I'm happy to look into implementing this myself, but I would absolutely appreciate if someone familiar with the codebase could point me in the right direction.

Done in #468

repo: nvim-treesitter/nvim-treesitter-context


text:
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing

Operating system and version:
MacBook Ai

nvm debug output:

nvm ls output:
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing

How did you install nvm? (e.g. install script in readme, Homebrew):
I have godday shared hosting , I am connecting with ssh and at home directory I ran
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash

What steps did you perform?

What happened?
I am getting tthe following error :
error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing

What did you expect to happen?
Install nvm , in order to install nodejs

Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?
no

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

Please stop filing duplicate issues for the same thing. Closing in favor of #2031 and #2040.

fatal: unable to access 'https://github.com/ChrissaLouvrou/lesson0.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
This is the message i am getting when trying to connect with my repository.

@ChrissaLouvrou that implies that your computer's SSL certificates, and/or system clock, are wrong/out of date.

authors: ChrissaLouvrou delphiy ljharb

repo: nvm-sh/nvm


text:
matIndex not available in Closest Hit Shader

The matIndex buffer does not seem to be available in the .rchit shader.
Following the tutorial at section 12: https://nvpro-samples.github.io/vk_raytracing_tutorial/#simplematerials

Noticed one just has to add the following to the raytrace.rchit shader file:
layout (binding = 4, set = 1, scalar) buffer MatIndex { int i[]; } matIndex[];
Of course it makes sense but maybe add it to the tutorial as the set = 1 was important for me,
(cannot just copy paste from the rasterizers fragment shader) otherwise the program would crash as it cannot bind the descriptor set to the shader (in my case).
Also, not that severe but the naming should be consistent across the rasterizer fragment shader and the raytracing hit-shader: In the rasterizer version the array is defined as matIdx but in the closest-hit-shader it is matIndex, because at section 12 of the tutorial we access the array using:
int               matIdx = matIndex[objId].i[gl_PrimitiveID];

Thank you, Michael, this will be fixed in the next release.
Note that there is a new version of the tutorial, based on the 'soon to be officially released' VK_KHR_ray_tracing.
https://nvpro-samples.github.io/vk_raytracing_tutorial_KHR/

authors: michaeleggers mklefrancois


text:
Does not apply theme to GTK-4 apps

Is there a way to get nwg-look to work with GTK-4 apps?

I see
Cheers,
Barry Deeney
On Wed, Apr 17, 2024, 20:33 Piotr Miller @.***> wrote:

It works. Just does not work with libadwaita. See #22
https://github.com/nwg-piotr/nwg-look/issues/22.
—
Reply to this email directly, view it on GitHub
https://github.com/nwg-piotr/nwg-look/issues/56#issuecomment-2061154645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIDAKLENGQIGW5VDCVENLDY5ZTYLAVCNFSM6AAAAABGLGMCWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRRGE2TINRUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

repo: nwg-piotr/nwg-look


text:
Is this package supported?

The last release was 3 years ago. NW.js continues to be developed, while this important and useful package remains stagnant and starts to build up vulnerabilities and deprecations.
Are there alternatives?

Hi, new maintainer here. That's the plan - triage issues and pull requests and go from there. Realistically, it'll probably take me ~2 weeks to get the next release out.

That's great!!! Thanks!

authors: ayushmxn jssuttles

repo: nwjs-community/nw-builder

license: mit

license_source: bigquery


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 47f223a.

repo: nxvvvv/uptime


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 8ebf7f2.


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in e3251a0.


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 377ef2d.


text:
🛑 Harmony Bot Website is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 837f6a1.


text:
Fixed XML validation issues

Changed “&” to “$amp;”, added missing end tags for elements
The existing XML files were not valid and required some cleanup.

Thanks! I'll merge and make sure these issues are fixed prior to the next update commit.

authors: mjbrodsky nitya

repo: nyphilarchive/PerformanceHistory


text:
Breaking changes to some TSNode types coming in typescript-eslint-parser

PR: https://github.com/eslint/typescript-eslint-parser/pull/388
Issue: https://github.com/eslint/typescript-eslint-parser/issues/386
Background: https://github.com/babel/babylon/pull/710
Should be very straightforward to track down any occurrences of the affected nodes and prefix them with TS

What's the timeline for this @JamesHenry?
I can work on this, but can't do it before the weekend, can we wait until then?

There shouldn't be any real pressure to update the parser in this codebase, it's not blocking any features/fixes etc
So even if the parser PR gets merged over the next few days, the plugin update can definitely wait a bit longer, just wanted to open the issue to give visibility

Understood, then I will work on this over the weekend, as you said this should be an easy fix...

Initial work in weirdpattern/support-updated-ts-nodes.
To test:
$ npm install eslint/typescript-eslint-parser#fbb98c416806a034bcccad765ed5a67ac880213f
$ npm run test

I will update the parser package dependency (and any other) once work on PR 388 has been completed and a new release of the parser has been published to npm.

@JamesHenry where are we on this?
I see some of the issues/PRs have already been merged.

Thanks for your patience on this @weirdpattern! I have submitted a PR to prettier confirming the relevant changes there too, so we are basically good to go on this now I think.
Any problems getting the plugin updated?

No, shouldn't be a problem.
I will do it in the next couple of days, if not today....

Ok no problem, it will be a major version bump in the parser anyway so there shouldn't be any timing issues

If that is the case, shouldn't I wait until the parser has been updated so I can update the version in our package.json file?

@weirdpattern You can just use a commit from GitHub to get the PR started, then switch to the npm version once the parser changes get released.

@j-f1 yeah that's how I did it when I implemented the changes. I was just hoping to avoid a second (or third) rebase/commit to my code... no biggie... I will keep doing what I did before (point to the commit) then update the version...

It's merged and I've released v10.0.0

Perfect, I will take it from here

Alrigth, it's done 😄

authors: JamesHenry j-f1 weirdpattern

repo: nzakas/eslint-plugin-typescript


text:
zk system only finds o1js from the ui and contracts directories

I installed the latest version of the Mina zkApp CLI:
$ npm update -g zkapp-cli
and successfully created a zkApp CLI with tutorial 4
However, the zk system command doesn't find o1js from the root project directory:
➜  04-zkapp-browser-ui git:(main) ✗ pwd
/Users/barriebyron/zkprojects/04-zkapp-browser-ui
➜  04-zkapp-browser-ui git:(main) ✗ zk system
Be sure to include the following system information when submitting a GitHub issue:

  System:
    OS: macOS 13.5.1
    CPU: (12) arm64 Apple M2 Pro
  Binaries:
    Node: 18.5.0 - ~/.nvm/versions/node/v18.5.0/bin/node
    Yarn: Not Found
    npm: 8.12.1 - ~/.nvm/versions/node/v18.5.0/bin/npm
  npmPackages:
    o1js: Not Found (not in a project)
  npmGlobalPackages:
    zkapp-cli: 0.11.2

Success with the zk system command from the 04-zkapp-browser-ui/ui directory and the /04-zkapp-browser-ui/contracts directory
➜  04-zkapp-browser-ui git:(main) ✗ pwd
/Users/barriebyron/zkprojects/04-zkapp-browser-ui
➜  04-zkapp-browser-ui git:(main) ✗ cd ui
➜  ui git:(main) ✗ zk system
Be sure to include the following system information when submitting a GitHub issue:

  System:
    OS: macOS 13.5.1
    CPU: (12) arm64 Apple M2 Pro
  Binaries:
    Node: 18.5.0 - ~/.nvm/versions/node/v18.5.0/bin/node
    Yarn: Not Found
    npm: 8.12.1 - ~/.nvm/versions/node/v18.5.0/bin/npm
  npmPackages:
    o1js: 0.* => 0.12.1
  npmGlobalPackages:
    zkapp-cli: 0.11.2

@barriebyron This issue should be in the zkApp-cli repo https://github.com/o1-labs/zkapp-cli/

authors: barriebyron ymekuria


text:
Remove Postinstall.js script

Describe the problem
Sometimes the installation of the zkapp-cli  takes a long time or hangs.
Describe the proposed solution
This hanging often occurs in the postinstall.js script. The script was initially created to support offline use of the zkapp-cli. Supporting offline use has been deprioritized. Removing the file will lead to a better dev experience.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

Closed with #391


text:
我有兴趣赞助你这个项目，请与我联系！

RT

RT

774309635@qq.com. 您好，这是我的邮箱


text:
When user has a pool VM created from template in cluster that user doesn't have any permissions for, the template name for the VM is N/A instead of the name of the template.

When user has a pool VM created from template in cluster that user doesn't have any permissions for, the template name for the VM is N/A instead of the name of the template.
Originally posted by @isaranova in https://github.com/oVirt/ovirt-web-ui/pull/1019#issuecomment-504404351

Hi Guys I checked that and it seems like the issue is already fixed:
I logged in to the web Admin as an admin and removed t1 user's permissions to Default-new cluster:
cluster's permissions screenshot:

Then I logged in to vmPortal as t1 user and viewed pool VM which created from template in Default-new cluster.
The described issue wasn't occur:
vmDetails card screenshot:

It seems it's already been fixed.
did I checked it well? or I did something wrong in the proccess?
@sgratch @sjd78

@bamsalem based on verification mentioned above the issue is not reproduced anymore and therefore I am closing it.

authors: bamsalem sgratch sjd78

repo: oVirt/ovirt-web-ui


text:
Allow group profile to be seen by non-members for private joinable groups

They should also be able to see the featured members feed in the profile. Generally we don't reveal members, however if a user can simply join the group, there is no privacy being protected by restricting it.

@mrvisser : Is it possible to see the activity feed before joining as well?

Depends if we have #loggedin / #public feeds for groups.

Incorporating into the design backlog

authors: mrvisser nicolaasmatthijs


text:
PUPIL-348: Serve quiz images from new Cloudinary distribution

Description
Music year: 1971
With the new pupil pages we made a change to serve quiz images directly from Cloudinary instead of passing them through Next's image processing proxy. This was done to improve image loading which has been greatly improved. Unfortunately this had the unintended side-effect of moving requests for those images off thenational.academy domain. This increased the chances of a request being blocked by a school network policy and possibly incurring additional tariffs for some users.
This change moves those requests back under a thenational.academy origin mitigating those issues.
How to test

Go to https://deploy-preview-2269--oak-web-application.netlify.thenational.academy/pupils/programmes/english-primary-ks2/units/developing-reading-preferences-in-year-5/lessons/developing-reading-preferences-in-year-5-through-appreciation-of-characters
Take the quiz
Inspect each image and you should see that it is served from a Cloudinary distribution under thenational.academy and it should load no differently than before.
Go to https://deploy-preview-2269--oak-web-application.netlify.thenational.academy/pupils/programmes/science-secondary-ks3/units/moving-by-force/lessons/reading-distance-time-graphs
Take the starter quiz
Inspect the images in the answers and they should also be served from a Cloudinary distribution under thenational.academy

Checklist

[x] Added new env vars to development and production configs.
[x] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices

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

authors: carlmw oak-machine-user

repo: oaknational/Oak-Web-Application


text:
Doc: Update the IPU Workflow Image

The IPU Workflow has been updated loooong time ago. Let's reflect
the change as we can call it quite stable really.

Can one of the admins verify this patch?

repo: oamg/leapp


text:
Unify leapp-preupgrade and leapp-upgrade logs

Instead of having a dedicated leapp-CMDNAME file for
each command log latest run as leapp.log.

Can one of the admins verify this patch?

Well if you would do this now, this would mean you would have to update all the documentation. Also would this clash a bit with C2R - While I am pretty sure why you think we need this, I think there might be an alternative solution. I think it might work if you would set leapp.logger._logger to None after you're done.

Well iiuc clash with convert2rhel is not something we have to worry about anymore, as they won't be using leapp for conversions.
If we don't have doc freeze I'd rather have 1 log file, but maybe leapp.log is a very bad name yeah. How about keeping leapp-upgrade.log for both preupgrade and upgrade? Or maybe just leapp-run.log?

/rerun 850

This one came in pair with https://github.com/oamg/leapp-repository/pull/850 which is now closed in favor of https://github.com/oamg/leapp/pull/764

authors: centos-ci fernflower vinzenz


text:
[CH] Memory statistics maybe not correct

Backend
CH (ClickHouse)
Bug description
In our yarn cluster, we have gluten config as following:
spark.executor.cores 1
spark.executor.memory.offHeap.size 3g
spark.executor.memory 1g
spark.Executor.memoryoverhead 0g
spark.executor.instances 1000
spark.gluten.sql.columnar.backend.ch.runtime_settings.max_threads 1

We got following metrics from spark web UI,

Spark version
Spark-3.3.x
Spark configurations
spark.executor.cores 1
spark.executor.memory.offHeap.size 3g
spark.executor.memory 1g
spark.Executor.memoryoverhead 0g
spark.executor.instances 1000
spark.gluten.sql.columnar.backend.ch.runtime_settings.max_threads 1

System information
ubuntu 16.04
Relevant logs
executor-499.log
executor-181.log
No response

Memory usage is good, close this issue.

nm的日志，因为物理内存超限，kill掉了container
2023-08-29 09:25:52,856 WARN  monitor.ContainersMonitorImpl (ContainersMonitorImpl.java:checkLimit(702)) - Container [pid=22674,containerID=container_e63_1691660805290_1090390_01_000071] is running 396840960B beyond the 'PHYSICAL' memory limit. Current usage: 6.4 GB of 6 GB physical memory used; 18.6 GB of 12.6 GB virtual memory used. Killing container.
container日志，ch的内存监控显示只用了2.02G，没有报not enough offheap memory，offheap给的3G，符合预期。
2023-08-29 09:25:52.577  MemoryTracker: Current memory usage (for query): 2.02 GiB.
23/08/29 09:25:52.651 INFO [Executor task launch worker for task 3879.0 in stage 0.0 (TID 14935)] UnifiedMemoryManager: Acquiring 67108864 bytes of off-heap memory.
spark的peak memory监控，on heap只有1.1G，offheap只有110MB（严重不准），on heap内存给的是2G，也没报on heap oom，说明on heap mem没有超过2G，那剩下的2G？尝试把jemalloc的decay参数设置到500ms(set (JEMALLOC_CONFIG_MALLOC_CONF "percpu_arena:percpu,oversize_threshold:0,muzzy_decay_ms:500,dirty_decay_ms:500")，问题还是存在。

Tuning parameters can lower down the probability of killing by yarn NM, but it maybe heart performance.

Currently, we donot relay on memory audit offered by gluten, instead we use NM to kill container if too many memory used.

repo: oap-project/gluten


text:
[GLUTEN-1897][CH] Respect hdfs-site.xml configs for clickhouse libhdfs3

What changes were proposed in this pull request?
(Fixes: #1898)

Firstly we apply 4 spark hadoop configs to clickhouse backend:

spark.hadoop.input.connect.timeout: default 180s
spark.hadoop.input.write.timeout: default 180s
spark.hadoop.input.read.timeout: default 180s
spark.hadoop.dfs.client.log.severity: default "INFO"

Above spark.hadoop.* configs maybe from spark-submit configs or hdfs-site.xml file(the former has higher priority). If no config key is specified, default value is applied in CH libhdfs3.
 --conf spark.hadoop.input.connect.timeout=600000 \
 --conf spark.hadoop.input.read.timeout=600000 \
 --conf spark.hadoop.input.write.timeout=600000 \
 --conf spark.hadoop.dfs.client.log.severity="DEBUG2" \

@zzcclp do you hive time to review this pr, thanks!

download files failed, can you help retrigger the failed uts @zzcclp

failed velox uts seems not related to this pr.

@taiyang-li Could you rebase to the main branch? This issue should be fixed.

authors: rui-mo taiyang-li


text:
[GLUTEN-4642][CH]Fix cse issue in aggregate

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
(Fixes: #4642)
How was this patch tested?
UT

@zzcclp do you have time to review it, thanks!

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_4651_time.csv
log/native_master_02_24_2024_7e7fbd277_time.csv
difference
percentage

q1
32.03
34.34
2.311
107.22%

q2
24.46
24.77
0.312
101.27%

q3
37.39
38.78
1.388
103.71%

q4
37.85
37.81
-0.044
99.88%

q5
70.30
71.67
1.377
101.96%

q6
7.22
5.66
-1.563
78.35%

q7
84.41
83.96
-0.454
99.46%

q8
87.56
86.74
-0.828
99.05%

q9
124.48
125.66
1.174
100.94%

q10
43.32
42.79
-0.529
98.78%

q11
20.57
20.56
-0.008
99.96%

q12
25.37
28.79
3.425
113.50%

q13
44.48
45.21
0.727
101.64%

q14
18.77
20.63
1.858
109.90%

q15
28.60
28.31
-0.291
98.98%

q16
15.53
13.32
-2.204
85.81%

q17
102.47
102.37
-0.102
99.90%

q18
149.23
149.07
-0.159
99.89%

q19
12.62
12.59
-0.035
99.72%

q20
26.34
26.67
0.325
101.23%

q21
225.56
226.20
0.638
100.28%

q22
13.69
13.50
-0.191
98.61%

total
1232.26
1239.39
7.129
100.58%

authors: GlutenPerfBot taiyang-li


text:
Stojanovic/fe 19 implement related field select with autocomplete

Ahoj Miro,
I have made a working version of the component. I think the component is generic and could be reused. I made some comments in the code regarding the things I am not sure about, so when you take a look, we can discuss please. Thanks!

@mirekys Ahoj Miro,
I made some modifications to the code:

in single choice mode automatic selection of item when clicked
wrapped the component with another functional component sample usage
`  <RelatedSelectField
fieldPath="remote"
suggestionAPIUrl={"/api/vocabularies/institutions"}
clearable
externalSuggestionApi={"/api/vocabularies/licenses"}
search={(options) => options}
selectOnBlur={false}
multiple={true}
/>
<RelatedSelectField
fieldPath="remote2"
suggestionAPIUrl={"/api/vocabularies/institutions"}
clearable
externalSuggestionApi={"/api/vocabularies/licenses"}
search={(options) => options}
selectOnBlur={false}
// multiple={true}
/>
<RelatedSelectField
fieldPath="remote3"
suggestionAPIUrl={"/api/vocabularies/institutions"}
clearable
externalSuggestionApi={"/api/vocabularies/licenses"}
search={(options) => options}
selectOnBlur={false}
// multiple={true}
serializeSuggestions={serializeVocabularySuggestions}
/>
<RelatedSelectField
fieldPath="remote4"
suggestionAPIUrl={"/api/vocabularies/institutions"}
clearable
externalSuggestionApi={"/api/vocabularies/licenses"}
search={(options) => options}
selectOnBlur={false}
serializeSuggestions={serializeVocabularySuggestions}
multiple={true}
/>

`
first two are using default serializer one is single, other multi, other two are using vocabulary serializer that can show breadcrumbs. You need to import vocab serializer
import {   RelatedSelectField,   serializeVocabularySuggestions, } from "@js/oarepo_ui/forms/components/RelatedSelectField";
I was not sure where to keep this serializer. I know it is vocab serializer, but it would only be used with this component so I think it makes sense that you import it from the same module if you want to use it.
Please let me know what you think.

repo: oarepo/oarepo-ui


text:
rubygems has version .1.1, not .1.2

Hi,
Would you mind updating your gem on rubygems.org to the latest version, .1.2? Currently rubygems has .1.1, which lacks some nice features of .1.2.
Thanks

Please accept my overdue apologies. nbayes is now updated to version 1.3.

authors: nogre oasic

repo: oasic/nbayes


text:
Oasis CLI is lacking man pages

Running man oasis after Oasis CLI has been installed:
No manual entry for oasis
See 'man 7 undocumented' for help when manual pages are not available.

This is, in general, a hard problem. Note that even golang does not have a man page.

Hard problem in which way? How to install them? Or how to generate them? There are probably tools for both?

is oasis help not sufficient? generating man pages isn't automatic

is oasis help not sufficient?

Depends on the amount of information you provide. Currently help does not provide enough documentation anyway. But if you would really start providing full documentation to the degree git does, then help would not be really beneficial. I would even say you could do the same as git, simply opening man page if you run help.

generating man pages isn't automatic

There are Markdown to man page converters:
http://rtomayko.github.io/ronn/ronn.1
Probably others could be find as well.

Currently help does not provide enough documentation

Yeah I just got that feedback from someone else. I'm hoping to revive #148. Maybe if the format is amenable to man pages, I'll add it (but probably not because managing installs and uninstalls is arduous).

Also, this was filed in the wrong repo.

authors: nhynes omitar

repo: oasislabs/oasis-rs


text:
Consider replacing EarlyLogAndExit() in CLI commands

SUMMARY
Following up from https://github.com/oasisprotocol/oasis-core/pull/3044#discussion_r444865403, we should should check the uses of github.com/oasisprotocol/oasis-core/go/oasis-node/cmd/common.EarlyLogAndExit() and replace it with os.Exit() where appropriate to avoid printing error message twice (for an example, see f5f906b3c076290d20ea6cbd298ce548c2000513).
ISSUE TYPE

Clean-up

we should should check the uses of github.com/oasisprotocol/oasis-core/go/oasis-node/cmd/common.EarlyLogAndExit() and replace it with os.Exit() where appropriate to avoid printing error message twice.

I did that in #3230, other uses cases are appropriate.

repo: oasisprotocol/oasis-core


text:
Hiding exceptions is dangerous

The plain rescue in MultiJson can potentially hide useful exceptions (intridea/multi_json#143)
:json  => lambda { |body| MultiJson.load(body) rescue body }, # rubocop:disable RescueModifier`

https://github.com/intridea/oauth2/blob/3d0ad2df0a3dd7e31b103e621dc3cfcd9895ca42/lib/oauth2/response.rb#L53
That's probably why rubocop complaints in the first place :frog:.
Assuming the rescue is there for bad content-types and not to hide MultiJson errors, wouldn't it be better to ask the user to fix the issue himself by setting the parser?

I agree.  The next release will include breaking changes, and we will stop rescuing during parsing.

Fixed by https://github.com/oauth-xx/oauth2/pull/367

This will require significant investigation, testing, and perhaps redesign.

authors: elia pboling


text:
NTR: additional microbiology assay/datum terms

Requesting 3 microbiology assay and 3 microbiology datum terms based on the following specimen terms:
skin of body specimen
bone marrow specimen
nasal wash specimen
following the existing design pattern.

Discussed 2023-04-03. Will add terms.

repo: obi-ontology/obi


text:
inconsistent definition of identity between scales and projections

For regular scales (e.g. x, y, color), "identity" is meant to opt out of any scaling and pass raw values. For projections, this is what null does, and identity means a planar-rescalable projection.
Suggestion to rename the null projection to "identity", and the identity projection to "planar". Another idea would be "planar-up" (for the current "reflect-y") and "planar-down" (for the current "identity").

I’m not happy with any of the alternative words we considered, so I’d prefer to just leave this as-is even if it’s not perfect.

authors: Fil mbostock

repo: observablehq/plot

license: ISC


text:
feat: add ignore global query instruction

Description
Add ignore global query instruction to discard the Global Query in a given task block.
Motivation and Context
Fixes #2074
How has this been tested?
Unit test + smoke test
Global Query = tags include #test

Types of changes

Changes visible to users:

[x] New feature (prefix: feat - non-breaking change which adds functionality)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] My change has adequate Unit Test coverage.

Terms

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

Hi, thanks very much for the contribution!
At the moment I am focussing on getting custom filtering released. There is still a lot of documentation to go...
If I get that done before our next session, I will pick up #2112...
So it will be some time until I get to this one, unfortunately.
Some initial thoughts though, from reading the diff on an iPad....
One thing I will be looking at when I go get to this is how explicit and clear it is, in the explain output, that the global query has been skipped.
Also, just to note that it doesn't fully fix the referenced issue - whose subject line was not updated to mention the discussion that what what we settled on is to add the ability to revert parts of the global query, as more generally useful than overriding the whole thing.
In other words, whilst this PR is useful, thanks, the more flexible alternative is still wanted.

One thing I will be looking at when I go get to this is how explicit and clear it is, in the explain output, that the global query has been skipped.

Do you mean that in case of the ignore, the explanation shall mention that?

Also, just to note that it doesn't fully fix the referenced issue - whose subject line was not updated to mention the discussion that what what we settled on is to add the ability to revert parts of the global query, as more generally useful than overriding the whole thing.
In other words, whilst this PR is useful, thanks, the more flexible alternative is still wanted.

True, this is a partial fix. I thought that there are 2 things to implement there - one is the 'ignore...' and the other is 'clear...'. This PR is about the first one.

One thing I will be looking at when I go get to this is how explicit and clear it is, in the explain output, that the global query has been skipped.

Do you mean that in case of the ignore, the explanation shall mention that?

Let me try it out and then answer that...

Also, just to note that it doesn't fully fix the referenced issue - whose subject line was not updated to mention the discussion that what what we settled on is to add the ability to revert parts of the global query, as more generally useful than overriding the whole thing.
In other words, whilst this PR is useful, thanks, the more flexible alternative is still wanted.

True, this is a partial fix. I thought that there are 2 things to implement there - one is the 'ignore...' and the other is 'clear...'. This PR is about the first one.

Indeed. I was unclear.
I meant that the description in this one says Fixes nnnn - which will make GitHub close that request when this PR is merged...
Partially fixes nnnn would also make it fix the other one.
So I prefer not to say anything like fixes... for a partial fix.
An alternative might be This is a partial fix for nnnn. Then GitHub pattern matching (probably) won't trigger.

An alternative might be This is a partial fix for nnnn. Then GitHub pattern matching (probably) won't trigger.

I was not aware that GitHub was closing these automatically. Thanks for your explanations, I modified the description.

Also, just to note that it doesn't fully fix the referenced issue - whose subject line was not updated to mention the discussion that what what we settled on is to add the ability to revert parts of the global query, as more generally useful than overriding the whole thing.

I have updated the issue subject line to reflect the discussion. Let me know if I can change anything else to be more clear

authors: claremacrae david-jarman ilandikov

repo: obsidian-tasks-group/obsidian-tasks


text:
Small simplifications for Vcs.cmd calls

A tiny simplification found while investigating some issue, I think it can be merged independently.

Subsumed by #219

repo: ocamllabs/dune-release


text:
Document LOCAL_PACKAGE syntax for lock

These can have version numbers.

I rebased and added a sentence about that.

repo: ocamllabs/opam-monorepo


text:
[Bug]: Personal space execution structure comparison failed

ODC version
odc424
OB version

What happened?

What did you expect to happen?
Execution succeeded
How can we reproduce it (as minimally and precisely as possible)?
Comparison of Personal Space Execution Structure
Anything else we need to know?
No response
Cloud
No response

pass

repo: oceanbase/odc


text:
Driver for Universal Resolver

https://github.com/decentralized-identity/universal-resolver
https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c
https://github.com/decentralized-identity/universal-resolver/blob/master/docs/design-goals.md
https://github.com/decentralized-identity/universal-resolver/blob/master/docs/architecture-drivers.md
https://github.com/decentralized-identity/universal-resolver/blob/master/docs/api-definition.md

The drivers are implemented as docker containers.

https://github.com/decentralized-identity/universal-resolver/blob/master/docs/driver-development.md

authors: carlosflrs mrinalwadhwa

repo: ockam-network/ockam


text:
Create First Base Project

Create a base project that includes only OctopOSPrime picture and a message for construction.

Closed with #7

repo: octoposprime/op-fe-app


text:
Optimizer closure

Add support for L-BFGS, etc.
Do batch-wise optimizer step only if closure is required. For most optimizers, the optimizer step will be performed only once after all batches are run.
Redo some of the previous changes and fix test failure.

@matinmoezzi Hi Matin, I made some minor changes such that

When using L-BFGS or any optimizer where closure is required, the gradients will be zeroed in every batch, and an optimization step is performed after every batch.
When using most other optimizers (e.g. Adam, SGD, etc.), the gradients will be zeroed (only once) before the first batch; the gradients will be accumulated across batches; and a single optimizer step is performed after the last batch. (This is the current behavior of neurodiffeq, which enables arbitrarily large training sets to be trained on a limited-memory GPU.

If you don't have any problems, I'm about to merge it into master.

Hi Shuheng, yes, you are right. I agree with these changes. Thank you for your careful consideration.

authors: matinmoezzi shuheng-liu

repo: odegym/neurodiffeq


text:
Update README.md

"If you feel that you really must do this, denote such comments with a character such as '#'." <-- this may be confusing. Feel free to leave out for simplicity.

@BobHarper1 This seems to have a conflict but I'm not sure how best to resolve it.

Thanks @slowe

repo: odileeds/open-data-tips


text:
Fix typos

I was too fast with my previous PR, I found two other typos.

:) I'm sure, there's more! Thanks again.

repo: odis-labs/streaming


text:
Check column dtype in metadata of CBS raw files

We are primarily using pyreadstat.read_sav() for reading sav files from CBS.
This library uses the dtype given in the meta data of the sav files to decide the dtype of the columns in the returned df.
My current assumption is CBS keeps every column's type as String.
While doing data-driven approach for LLM pretraining, this assumption should be verified.
Also, we should check if some of the CBS raw files are csvs.

implemented by Tanzir and Ana


text:
fix to #1294

I'm a total noob. I don't expect these change to get merged but I had fun anyway :D

do npm run lint to check for lint issues

combining with https://github.com/odota/ui/pull/1318

repo: odota/ui


text:
proto: invalid type: map[string]string for bigquery recipe when include_column_profile is false

Run a big query to console recipe with include_column_profile as false. It fails when creating the Table struct with the issue proto: invalid type: map[string]string
I suspect the issue is because labels have been removed from the Table proto. It fails when it tries to convert lables of type map[string]string to map[string]interface. Earlier it was part of Properties and not Attributes.
Code for reference: https://github.com/odpf/meteor/blob/0aba47c054dc1305bdce5e1ec58607d7a2222d72/plugins/extractors/bigquery/bigquery.go#L223

@anjali9791 created a PR for the fix https://github.com/odpf/meteor/pull/411
thanks for reporting and sorry for the inconvenience 🙏

repo: odpf/meteor


text:
refactor: extension

This PR is to address #172 . Further update will be added later.

Pull Request Test Coverage Report for Build 2273200361

361 of 390 (92.56%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.8%) to 75.916%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ext/exd/default_installer.go
23
25
92.0%

ext/exd/provider/github/client.go
73
77
94.81%

ext/exd/default_manifester.go
30
40
75.0%

ext/exd/manager.go
122
135
90.37%

Totals

Change from base Build 2219262482:
0.8%

Covered Lines:
6405

Relevant Lines:
8437

💛  - Coveralls

Let's have a conversation about these changes. This is too much code for refactor.
Let's discuss the design first for these changes and then we can have a look at the PR.

Let's have a conversation about these changes. This is too much code for refactor. Let's discuss the design first for these changes and then we can have a look at the PR.

I agree that it's a bit much. We can have the discussion.

authors: coveralls irainia sbchaos

repo: odpf/optimus


text:
XTDB connector is not publishing the jar-with-dependencies

The gradle build is not building/packaging the -jar-with-dependencies
Noticed when trying to download via
http://oss.sonatype.org/service/local/artifact/maven/redirect\?r\=snapshots\&g\=org.odpi.egeria\&a\=egeria-connector-xtdb\&v\=4.0-SNAPSHOT\&c\=jar-with-dependencies

Found that the uber jar is built, but is not published in the maven package
The main egeria repo is uising the shadow plugin. Here we use a different approach but either should be fine.
The plugin modifies the publish process, so when doing explicitly (as here) the publish step in gradle will also need updating

Ah, of course! I forgot that wasn't being published 🙈 If you're up to take a stab at it, even re-using the shadow-based approach, happy to receive it as a PR!

I noticed a few other improvements we could make, but in the process hit https://github.com/odpi/egeria/issues/7421
Whilst building an uber jar doesn't require this, it's good to do a good job of validating a good connector build to prove out the artifacts we're creating in egeria are good. Looks like we have a regression in the BOM creation.

The main fix is done now, and merged.
However will leave open just to come back and refine the constraints & test

repo: odpi/egeria-connector-xtdb


text:
🛑 urbamonde.org is down

In 3b0374b, urbamonde.org (https://www.urbamonde.org) was down:

HTTP code: 429
Response time: 476 ms

Resolved: urbamonde.org is back up in 09d948c.

repo: odqo/upptime


text:
🛑 urbamonde.org is down

In 24e5190, urbamonde.org (https://www.urbamonde.org) was down:

HTTP code: 429
Response time: 852 ms

Resolved: urbamonde.org is back up in 8fb1c57.


text:
🛑 urbamonde.org is down

In b00a085, urbamonde.org (https://www.urbamonde.org) was down:

HTTP code: 429
Response time: 618 ms

Resolved: urbamonde.org is back up in fc3a731.


text:
Add decorator to tests which require internet connection.

Hello.
I found out that some tests newly require internet and therefore they have to be skipped in an environment without the internet connection.
The latest virtualenv bundles pip 10.0.1. Pip from version 10.0.0 has support for pyproject.toml files (PEP 518) which means that pip now installs build dependencies specified in pyproject.toml file automatically. And it doesn't work without internet obviously.
It would be nice if you can do a release so it would be possible for me to drop downstream patch. Currently, I had to create this patch twice - once for this PR and once for currently released version 0.20.0.
Have a nice day.
Lumír

Please squash the fixup commit during a merge.

Exactly the same here. RPM build in Fedora doesn't have access to the internet.

@frenzymadness , you may have noticed https://bugzilla.redhat.com/show_bug.cgi?id=1761091 .  Good to see you've already been working on trying to solve these problems.  I've added a few more PRs to userpath.  My userpath spec is still using master.tgz because of  https://github.com/ofek/userpath/issues/11 https://build.opensuse.org/package/show/home:jayvdb:py-new/python-userpath
I have hatch 0.20.0 packaged up reasonably well now, using userpath(master) instead of adduserpath, by adding some patches.
https://build.opensuse.org/package/show/home:jayvdb:py-new/python-hatch

authors: frenzymadness jayvdb

repo: ofek/hatch


text:
Support for check-model-has-one-of-tests-by-name

Describe the feature you'd like
Many dbt projects require at least one unique test per model. However, this test may be one of several flavors, e.g.:

test_unique
test_unique_where
test_unique_threshold
test_unique_combination_of_columns

Initial thought: We could leverage some sort of "OR" functionality, e.g.
test_unique | test_unique_where = 1

Thank you @jtalmi for a great idea. I am definitely for implementing this hook. I would rather use 2 arguments - test_names and min_test_cnt (or test_cnt) then one with some OR functionality test_unique | test_unique_where = 1 since parsing with Argparse would be too complicated. E.g.:
--test-names test_unique test_unique_where --test-ct = 1

What do you think?

yep, i like that. going to take a stab at that now.

Closed in #6

For anyone that lands here, you can reference tests like dbt_utils.unique_combination_of_columns with unique_combination_of_columns

authors: ConstantinoSchillebeeckx jtalmi tomsej

repo: offbi/pre-commit-dbt


text:
FAILED (remote: 'Download is not allowed on locked devices')

Sending 'encryptData' (0 KB)                       FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed

Device: Redmi K50
product: rubens

In the Atest branch, when I press Enter nothing happens and the wait time is over half an hour.I have enabled oem unlock in developer mode.On Apr 20, 2024 12:01 AM, offici5l @.***> wrote:
Try with this branch :
https://github.com/offici5l/MiUnlockTool/tree/Atest
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


text:
[UI fix] Hide opened menu when click on menu button

When you click a MenuButton, it opens a PopupMenu underneath it.  However, the only way to close the PopupMenu without selecting an item is to click outside the MenuButton and the PopupMenu.  Depending on the layout, this may be difficult.  In order to conform with other GUI systems, the PopupMenu will now close when the MenuButton is pressed.
Simple, but I think it's important. :)

:+1:

repo: okamstudio/godot


text:
🛑 Ekşi Sözlük is down

In 91a2e92, Ekşi Sözlük (https://eksisozluk.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ekşi Sözlük is back up in 842053e.

repo: okankocyigit/upptime


text:
🛑 Ekşi Sözlük is down

In c7ccf3f, Ekşi Sözlük (https://eksisozluk.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ekşi Sözlük is back up in e071296.


text:
js und css Links für Offline Entwicklung umstellen (macht aku)

In den Partials in themes/hugo-cfg/layouts/partials sind absolute Links auf https://dev.codefor.de, dadurch kann man nicht offline entwickeln. Vorschlag: ersetzen durch Filesystems links:

statt
link rel="icon" type="image/png" href="https://dev.codefor.de/images/favicon.png" />
etc. für alle Bilder, css, js und fonts.

Aku

Funktioniert würde ich sagen. #28 #30

authors: digital-codes joliyea ubergesundheit


text:
Abstand Dropdown Menü

Lass die Abstände für der Auswahlfelder im Menü für das Dropdown auch mal anfassen. Ich füge es in Sketch hinzu.

@stadine ist das jetzt ok?

halt die fresse, arne

authors: arnese stadine

repo: okfde/ifg-index


text:
Default-Method isn't temporary, but persistent

Hi, this just bit me - maybe I just misunderstood the docs, which say:

To define the default type for session variables, set persistent_session.default_method to your preferred type in your config/settings.json file:
{
  "public": {
    "persistent_session": {
      "default_method": 'your-preferred-type'
    }
  }
}

persistent_session.default_method can take one of the following values:
persistent
authenticated
In any other case the default_method will fall back to temporary

While in the code it is:
https://github.com/okgrow/meteor-persistent-session/blob/master/lib/persistent_session.js
// initialize default method setting
var default_method = 'persistent'; // valid options: 'temporary', 'persistent', 'authenticated'
if (Meteor.settings &&
    Meteor.settings.public &&
    Meteor.settings.public.persistent_session) {
  default_method = Meteor.settings.public.persistent_session.default_method;
}

Did I misread the docs? I expected the default Session.set() and Session.get() - commands to stay temporary if Meteor.settings.public.persistent_session wan't set, but they were indeed persistent, which would confuse my code (and actually third party - code which relied on sessions being non-persistent).

Also, it might be nice to document that the "persistent" - option also leads to session variables being shared across browser windows/tabs. That is implied by using localstorage, but that makes the behaviour differ from the default session in two major ways (persistent across reloads + shared between windows), not only one.

Agreed, it appears the docs are incorrect. I was just bit by this as well.

Thanks @DanielDornhardt and @nickw, and sorry for the slow reply. We'll fix it!

I tend to think it should be as the docs say, which will actually be a breaking change, what do you think @rgould? Definitely should bump the major version # then.

@pauldowman yeah, that was my expectation as well.

This should be fixed by df7386932a0ec9a162806111d4c0ec123ad32ab7, which has been released now. Reopen this if the issue persists!

Thank you!

authors: DanielDornhardt nickw pauldowman rgould

repo: okgrow/meteor-persistent-session


text:
[Feature request] Possibility to customize highlight.js

Hi!
Would you consider adding the two following configuration parameters:

possibility to disable the default highlight.js build provided in order to include a richer one (with support for more languages) in the static/js folder.
highlighjsTheme : to be able to select one of the highlight.js bundled themes.

I started hacking on this myself and noticed that the highlightjs support in this theme is mostly hardcoded.
I'm looking into making those points customizable from the config.toml. If I come to a usable solution, I'll make a PR.

If you want to load a richer build of highlight.js, just put it in static/lib/highlight.pack.js at the root of your project.
Chroma is the default choice  in next release(4.0.0). This feature is already done in next branch (https://github.com/olOwOlo/hugo-theme-even/commit/77101032aa61cad251fbe02476aa6d1e0df24d74).

If you want to try the next branch, please note that there have been some breaking changes, and there may be more breaking changes afterwards. And you need to rebuild the theme.
# install dependencies
yarn
# build
yarn build

authors: Punie olOwOlo

repo: olOwOlo/hugo-theme-even


text:
Some team logos are not loaded

Reproduced on Champions League fixtures

Merci. Ca vient des accents dans le nom du pays qui n'est pas present dans l'url.
par exemple: j'essaye d'acceder https://tvfoot.net/images/teams/gr%C3%A8ce/large/oly.png tandis que c'est https://tvfoot.net/images/teams/grece/large/oly.png

Ah oui j'ai un bout de code pour échapper les noms des pays.
/**
 * Normalizes the input url using the following rules:
 *  - lowercase
 *  - whitespace replace by -
 *  - accents are removed
 *
 * @param {String} url The URL to normalize
 */
angular.module('tvfoot').filter('normalizeURL', function() {
  return function(url) {
    var map = {
      'à':'a', 'á':'a', 'â':'a', 'ã':'a', 'ä':'a',
      'ç':'c',
      'è':'e', 'é':'e', 'ê':'e', 'ë':'e',
      'ì':'i', 'í':'i', 'î':'i', 'ï':'i',
      'ñ':'n',
      'ò':'o', 'ó':'o', 'ô':'o', 'õ':'o', 'ö':'o',
      'ù':'u', 'ú':'u', 'û':'u', 'ü':'u',
      'ý':'y', 'ÿ':'y',
      '&': 'and' // Hack to fix #44
    };
    return url.toLowerCase().replace(/\s+/g, '-').replace(/\W/g, function(c) {return map[c] || c;}).replace(/\/-|-\//g, '/');
  };
});
`

J'ai laisse Java s'en occuper moi. On verra si ca regle tout les problemes.

authors: mbilbille oldergod

repo: oldergod/red


text:
Краш при переходе в "Открытки" при наличии фотографов в базе данных.

Думаю, там и в издательствах тоже косяк может быть.

fixed in https://github.com/oldsaratov/postcards/commit/5b5c014c3c95fa0afb41e15d95bbc401c2d63e1d

authors: Ketoth okolobaxa

repo: oldsaratov/postcards


text:
ham member xp rates

🐛 Bug Report
Since I have started pickpocketing ham members I have noticed that when I first use the command =pickpocket male ham member I get 33,750xp when the trip ends, however if I use the command to send out for the same trip again afterwards I get 27,750xp. It also says I am pickpocketing female ham members after using =m right after sending a trip out for male ham members.
https://discord.com/channels/342983479501389826/732207379818479756/803115922784387152
https://discord.com/channels/342983479501389826/732207379818479756/803119737579372605

resolved

authors: Lajnux ReZeroed

repo: oldschoolgg/oldschoolbot


text:
Build CSS in pipeline

For now, site.css is prebuilt and checked in. Issues with the default action for building and publishing to Azure SWP

Fixed

repo: olebru/harmonyexplorer


text:
1.3.1 Incredibly Slow

Upgraded to 1.3.1 and it is incredibly slow.
The previous version 1.3.0 it took about 30 minutes to complete (35000 products). On 1.3.1 it takes in excess of 3 hours, and in fact I have not waited for it to complete as I killed the process, downgraded and went back to 1.3.0.
It took about 30 minutes for the first progress dot to appear and each subsequent progress dot.

I'm experiencing the same issue. I have 43,000 products and it took over 36 hours to complete. No idea why though.

same here, over 27000 products. works endless. Is running now about 20 hours :-(

Downgrading to version 1.3.0 solved the problem for me.  😄

Notice. Do not downgrade to 1.3.0 while using Magento 2.2.6.
The regenerator is quite fast then but deletes all url_keys from products and that results in pain.

The DELETE SQL query in the catalog_url_rewrite_product_category table is too slow (because ON DELETE CASCADE). We have 1.4 million products and and 3 stores and a DELETE query takes 20 to 25 seconds ....  and  will never finish.

https://github.com/magento/magento2/issues/11951

Hello All.
I've released version 1.4.0. Please, test it. Take into account that logic of whole script was changed a bit - read "How To" section.

Hello @jlfguthrie , @jbutkowski , @BNEP , @budoland-ab , @paul-blundell .
Issue was fixed in version 1.4.1. Please, upgrade extension.
Best regards,
Oleg Koval.

authors: BNEP Kamik budoland-ab jbutkowski jlfguthrie olegkoval


text:
Allow missing points

This is a prerequisite for #2.
I suggest we allow this:
# Theory: /50
## Question 1: 5/10
## Question 2: 10/20
## Question 3: 10/20

The validator should allow for points to be missing in all but the bottom-most judgements, and report that points are missing if some bottom-most judgements lack them.
In general, the lack of points can be represented in the AST with 1/0, i.e. Infinity. This is because 1/0 == 1/0 ~> True.

See:

99cac72ec332f42120d7ac514e70d37d17936880
666edbe1ae091fb0f89279e616e7732d8fbdd1ef
ab7ea9c6295cab662a7ae58c02ed5220e6506eb5

repo: oleks/remarks


text:
getMIMEFromPath call cb two time in error case.

getMIMEFromPath call cb two time in error case.
index.js line 223
// gets a MIME type of a file from the path to it
function getMIMEFromPath(path, cb) {
ReadChunk(path, 0, 262, function (err, buffer) {
if (err) { cb(null, ""); }
var fileType = FileType(buffer);
return cb && cb(null, fileType && fileType.mime || "");
});
}
Following code work for me.
// gets a MIME type of a file from the path to it
function getMIMEFromPath(path, cb) {
ReadChunk(path, 0, 262, function (err, buffer) {
if (err) { cb(null, ""); return;}   // need return here !!
var fileType = FileType(buffer);
return cb && cb(null, fileType && fileType.mime || "");
});
}

Sure does. Nice catch. Thanks. Added to master and will release later this week.

repo: oliver-moran/jimp


text:
Remove CHCONF options from CMake

We currently define certain ChibiOS ch configuration options in two places: CMake and chconf.h. CMake options have priority. We can either remove the variables from CMake so only the ones in chconf are used or vice-versa.

:+1: sounds good.

authors: mickvangelderen oliverlee

repo: oliverlee/phobos