Feature: Dynamic route parameters should not be set using definePageMeta

Discussed in https://github.com/nuxt-modules/i18n/discussions/1730

Originally posted by adesombergh December 13, 2022
Hi, thanks for the great work with this module.
I stumbled into a problem with i18n module v8 and nuxt3 and I think it might be interesting to change this in the future, as it makes it difficult to use with dynamic content.
Please, correct me if i'm not doing in right.
The Problem
According to the Dynamic route parameters documentation, to set translations for route params we should use definePageMeta like so:
<script setup>
definePageMeta({
  // ...
  nuxtI18n: {
    en: { id: 'my-post' },
    fr: { id: 'mon-article' }
  }
  // ...
})
</script>

However, the Nuxt 3 documentation about definePageMeta (right here) says that the page meta object cannot reference the component (or values defined on the component).
It means that the content inside definePageMeta({}) is supposed to be hard-coded and cannot be dynamic, making it impossible to set the page route params dynamically (as they often are). The following code won't work:
<script setup>
// /pages/[slug].vue
const route = useRoute()
const { locale } = useI18n()
const { data } = await useFetch(
  `https://yourapi.com/${locale}/page/${route.params.slug}`
)

definePageMeta({
  nuxtI18n: data.value.other_languages // Throws an error because data is undefined
})
</script>

{
  "other_languages": {
    "en": { "slug": "tech-specs"},
    "fr": { "slug": "specifications-techniques"},
  },
  ...more content ...
}

A solution
Instead of using definePageMeta, maybe i18n module could give us a composable like setParamsTranslations or whatever,  that could be used like this:
<script setup>
// /pages/[slug].vue
const route = useRoute()
const { locale, setParamsTranslations } = useI18n()
const { data } = await useFetch(
  `https://yourapi.com/${locale}/page/${route.params.slug}`
)
setParamsTranslations(data.value.other_languages)
</script>

If anyone agrees I can create an issue (feature)

This issue was miss-taken.
We need to more discuss this issue.

I have the same issue.
My dirty workaround for the time being:
<script setup>
// /pages/[slug].vue
const route = useRoute()
const { locale } = useI18n()
const { data } = await useFetch(
  `https://yourapi.com/${locale}/page/${route.params.slug}`
)

if (data?.value) {
  route.meta.nuxtI18n = data.value.other_languages;
}
</script>

having the same troube! in nuxt 2 I used this: https://i18n.nuxtjs.org/lang-switcher#dynamic-route-parameters
would be amazing to see this in the new V8

Your solution works great @provok-it, but it doesn't work on SSR, right? With view-source:, I get the same URLs:

And with the inspector, it shows the updated URLs:

Is that the case with you as well?

Got is working like this:
// pages/blog/[slug].vue

const { data: blog } = await useFetch(`https://yourapi.com/${locale}/page/${route.params.slug}`)

if (blog?.value) {
  route.meta.nuxtI18n = blog.value?.languages || {};
}

const head = useLocaleHead({
  identifierAttribute: "id",
  addSeoAttributes: true,
});

useHead({
  link: head.value.link,
  meta: head.value.meta,
});

Where blog.value.languages is an object like this:
{
  en: { slug: "english-slug" },
  de: { slug: "german-slug" },
  fr: { slug: "french-slug" }
}

Works both in SSR and normal mode.

It seems not to work with SSG. Has anyone tried to get with working with static rendering?

@adriaanvanrossum I double checked.
My version of the hack is also working with SSR 👌

My version of the hack is also working with SSR 👌

The workaround seems to work, but it seems you will have to set the route meta on each route change.
I made a reproduction to show that the meta links lose their translations if query parameters change and the route meta is not set again here.

@BobbieGoede
This comment will probably help you:
https://github.com/nuxt-modules/i18n/issues/1807#issuecomment-1405023044

@provok-it
I'm not sure if I had issues with switching locales but it would make sense if that wasn't working as well. For me it was just meta tags not updating while on the 'same' page (switching categories in a search page).
I ended up with the following composable, it's not pretty but it seems to work so far.
import { resolveUnref } from "@vueuse/shared";

type UseHeadParams = Parameters<typeof useHead>;
type useLocaleHeadParams = Parameters<typeof useLocaleHead>[0];

export default ([input, options]: UseHeadParams, localeOptions: useLocaleHeadParams) => {
    const route = useRoute();
    const i18nHead = useLocaleHead(localeOptions);

    useHead(() => {
        const i = resolveUnref(input);
        return {
            ...i,
            link: [...(resolveUnref(i?.link) ?? []), ...(i18nHead.value.link ?? [])],
            meta: [...(resolveUnref(i?.meta) ?? []), ...(i18nHead.value.meta ?? [])],
        };
    }, options);

    const _i18nParams = ref<Record<string, any>>({});
    const i18nParams = computed({
        get: () => _i18nParams.value,
        set: (val: Record<string, any>) => {
            _i18nParams.value = val;
            route.meta.nuxtI18n = i18nParams.value;
        },
    });

    watch(
        () => route.fullPath,
        () => (route.meta.nuxtI18n = i18nParams.value)
    );

    return { i18nParams };
};

Usage like so
const { i18nParams } = useI18nParams(
    [() => ({ title: t('productSearchTitle') })],
    { identifierAttribute: 'id', addSeoAttributes: true }
)

const fetchProducts = async () => {
    // ... fetch products
    // set i18nParams triggering composable to update `route.meta.nuxtI18n`
    i18nParams.value = {
        en: { slug: "english-slug" },
        de: { slug: "german-slug" },
        fr: { slug: "french-slug" }
    }
}

Try using useHead and see if you can make it auto update on changes.

I'm experiencing the same issue. The route.meta.nuxtI18n value seems to be updated. For example when using something like this:
const { data } = await asyncData(`https://myapi.com/page`)

if (data?.value) {
  route.meta.nuxtI18n = {
    en: {
      slug: data.value?.page?.languages.en.slug
    }
  }
}

But the switchLocalePath method still uses it's initial value – pointing to the wrong slug.
Is there maybe a way to force update switchLocalePath?

I changed Lang Switcher slightly...
<NuxtLink @click="switchLocale(locale.code)">
    {{ locale.name }}
</NuxtLink>

const switchLocale = async (locale) => {
  setLocale(locale);
  await navigateTo(switchLocalePath(locale));
};

Hope that helps.

I changed Lang Switcher slightly on strategy 'prefix_except_default'
<NuxtLink @click="switchLocale(locale.code)">
    {{ locale.name }}
</NuxtLink>

const switchLocale = async (locale) => {
  setLocale(locale);
  await navigateTo(switchLocalePath(locale));
};

Hope that helps.

This worked for me. I adjusted it a little bit to still be able to make use of :to instead of @click in NuxtLink:
<NuxtLink
      v-for="locale in locales"
      :key="locale.code"
      :to="switchLocale(locale.code)"
    >
      {{ locale.name }}
 </NuxtLink>

const switchLocalePath = useSwitchLocalePath()
const switchLocale = (locale: string) => {
  return switchLocalePath(locale)
}

nonetheless – this is a workaround and only works if route.meta is being updated manually (as explained above).
I hope we can find a solution for using definePageMeta dynamically as it is intended to be used:
definePageMeta({
  nuxtI18n: data.value.other_languages // Throws an error because data is undefined
})

Any updates? The hacky workarounds mentioned here are somewhat working, but the issue with definePageMeta must be solved.

I gave this another try but still can't get dynamic route parameters to work properly with data that is being fetched async.
As mentioned in the docs i tried to set them via the compiler macro definePageMeta. The issue seems to be that the compiler macro is being compiled away and can't be referenced with component data, as mentioned in the nuxt docs here.
In my case i fetch some data:
<script lang="ts" setup>
const { locale } = useI18n()

const { data } = await useAsyncGql({
  operation: 'getSlugPage',
  variables: {
    site: locale, // de
    slug: 'ueber-uns',
  },
})
// ...

The data i recive includes a page with a translation:
data: {
  page: {
    slug: 'ueber-uns',
      translation: {
        slug: 'about-us'
      }
   }
}

Then i would like to use this data and set the dynamic routes on nuxtI18n with it:
definePageMeta({
    nuxtI18n: {
      de: { slug: [data.value.page.slug] }, // should resolve to ueber-uns
      en: { slug: [data.value.page.translation.slug] } // should resolve to about-us
    },
})

When trying to do so i get the error that data is not defined:
[nuxt] [request error] [unhandled] [500] data is not defined
  at ./pages/[...slug].vue:2:21
  at ViteNodeRunner.directRequest (./node_modules/vite-node/dist/client.mjs:341:11)

If definePageMeta is not intended to hold fetched component data, how should dynamic routes with fetched data be updated? Any idea how this might be possible?
Many thanks for any help!

Hi, you can add it in script blog. Try...
const looksLike= {
  de: { slug: data.value.page.slug }
}
const route = useRoute();
route.meta.nuxtI18n = looksLike || {};

Hi, you can add it in script blog. Try...
const looksLike= {
  de: { slug: data.value.page.slug }
}
const route = useRoute();
route.meta.nuxtI18n = looksLike || {};

Thank you @bitmonti for the quick respond.
I have tried your suggestion and it seems to work when wrapped inside onBeforeMount similar to what i have tried here:
<script setup>
onBeforeMount(() => {
  route.meta.nuxtI18n =
    {
      de: { slug: [data.value.page.slug] },
      en: { slug: [data.value.page.translation.slug] },
    } || {}

What it doesn't seem to fix is the problem when prerendering the page with nuxt generate and crawlLinks: true.
I get all routes duplicated for each locale. I'm using the prefix_except_default strategy:
Prerendering 8 initial routes with crawler
  ├─ /
  ├─ /en
  ├─ /en/about-us
  ├─ /about-us
  ├─ /ueber-uns
  ├─ /en/ueber-uns
  ...

My langswitch component looks like this (similar to your approach):
<template>
  <div>
    <NuxtLink
      v-for="loc in availableLocales"
      :key="loc.code"
      :to="switchLocale(loc.code)"
    >
      {{ loc.name }}
    </NuxtLink>
  </div>
</template>

<script lang="ts" setup>
const switchLocalePath = useSwitchLocalePath()
const { locale, locales } = useI18n()

const availableLocales = computed(() =>
  locales.value.filter((loc) => loc.code !== locale.value),
)

const switchLocale = (locale: string) => {
  return switchLocalePath(locale)
}
</script>

This setup seems to works on the server using nuxi dev but not staticly with nuxi generate. It looks like the langswitch doesn't update in time and points to a wrong route or has the wrong locale... did you get this working with static generation?

I gave this another try but still can't get dynamic route parameters to work properly with data that is being fetched async.
As mentioned in the docs i tried to set them via the compiler macro definePageMeta. The issue seems to be that the compiler macro is being compiled away and can't be referenced with component data, as mentioned in the nuxt docs here.
In my case i fetch some data:
<script lang="ts" setup>
const { locale } = useI18n()

const { data } = await useAsyncGql({
  operation: 'getSlugPage',
  variables: {
    site: locale, // de
    slug: 'ueber-uns',
  },
})
// ...

The data i recive includes a page with a translation:
data: {
  page: {
    slug: 'ueber-uns',
      translation: {
        slug: 'about-us'
      }
   }
}

Then i would like to use this data and set the dynamic routes on nuxtI18n with it:
definePageMeta({
    nuxtI18n: {
      de: { slug: [data.value.page.slug] }, // should resolve to ueber-uns
      en: { slug: [data.value.page.translation.slug] } // should resolve to about-us
    },
})

When trying to do so i get the error that data is not defined:
[nuxt] [request error] [unhandled] [500] data is not defined
  at ./pages/[...slug].vue:2:21
  at ViteNodeRunner.directRequest (./node_modules/vite-node/dist/client.mjs:341:11)

If definePageMeta is not intended to hold fetched component data, how should dynamic routes with fetched data be updated? Any idea how this might be possible?
Many thanks for any help!

My issue explained above regarding duplicate crawled dynamic routes has been fixed since version 8.0.0-rc.3 with this setup using nuxt 3.6.5 and nuxi generate:
export default defineNuxtConfig({
  modules: ['@nuxtjs/i18n'],
  i18n: {
    strategy: 'prefix_except_default',
    defaultLocale: 'de',
    locales: [
      {
        name: 'Deutsch',
        code: 'de',
      },
      {
        name: 'English',
        code: 'en',
      },
    ],
  },
})

What about this?
definePageMeta({
  middleware: [
    async function ({ meta, params }) {
      const data = await useNewsDetails(params.slug);
      meta.nuxtI18n = data.value.localizations || {};
    },
  ],
});

von Outlook für Androidhttps://aka.ms/AAb9ysg

From: Fabian @.>
Sent: Tuesday, August 22, 2023 4:14:06 PM
To: nuxt-modules/i18n @.>
Cc: Mario Kreidl @.>; Mention @.>
Subject: Re: [nuxt-modules/i18n] Feature: Dynamic route parameters should not be set using definePageMeta (Issue #1736)
I gave this another try but still can't get dynamic route parameters to work properly with data that is being fetched async.
As mentioned in the docshttps://v8.i18n.nuxtjs.org/guide/lang-switcher#dynamic-route-parameters i tried to set them via the compiler macro definePageMeta. The issue seems to be that the compiler macro is being compiled away and can't be referenced with component data, as mentioned in the nuxt docs herehttps://nuxt.com/docs/guide/directory-structure/pages/#page-metadata.
In my case i fetch some data:

I have tried this, but get the following error:
[nuxt] error caught during app initialization Error: Must be called at the top of a `setup` function Caused by: SyntaxError: Must be called at the top of a `setup` function

Discussed in https://github.com/nuxt-modules/i18n/discussions/1730

Originally posted by adesombergh December 13, 2022
Hi, thanks for the great work with this module.
I stumbled into a problem with i18n module v8 and nuxt3 and I think it might be interesting to change this in the future, as it makes it difficult to use with dynamic content.
Please, correct me if i'm not doing in right.
The Problem
According to the Dynamic route parameters documentation, to set translations for route params we should use definePageMeta like so:

<script setup>

definePageMeta({

  // ...

  nuxtI18n: {

    en: { id: 'my-post' },

    fr: { id: 'mon-article' }

  }

  // ...

})

</script>

However, the Nuxt 3 documentation about definePageMeta (right here) says that the page meta object cannot reference the component (or values defined on the component).
It means that the content inside definePageMeta({}) is supposed to be hard-coded and cannot be dynamic, making it impossible to set the page route params dynamically (as they often are). The following code won't work:

<script setup>

// /pages/[slug].vue

const route = useRoute()

const { locale } = useI18n()

const { data } = await useFetch(

  `https://yourapi.com/${locale}/page/${route.params.slug}`

)

definePageMeta({

  nuxtI18n: data.value.other_languages // Throws an error because data is undefined

})

</script>

{

  "other_languages": {

    "en": { "slug": "tech-specs"},

    "fr": { "slug": "specifications-techniques"},

  },

  ...more content ...

}

A solution
Instead of using definePageMeta, maybe i18n module could give us a composable like setParamsTranslations or whatever,  that could be used like this:

<script setup>

// /pages/[slug].vue

const route = useRoute()

const { locale, setParamsTranslations } = useI18n()

const { data } = await useFetch(

  `https://yourapi.com/${locale}/page/${route.params.slug}`

)

setParamsTranslations(data.value.other_languages)

</script>

If anyone agrees I can create an issue (feature)

Any news on this issue, or is it beeing tracked somewhere else?

Any solution that work with nuxt-simple-sitemap?

Working for me @luca-smartpricing:
https://github.com/nuxt-modules/i18n/issues/1736#issuecomment-1438358316

@provoks-land
No, sorry it doesn't work. nuxt-simple-sitemap don't set rel="alternate" also if i set the param in the middleware.
  middleware(to) {
    to.meta.nuxtI18n.en = {
      blog: 'a-simple-blog'
    }
  }

It some time but with #2580 merged and released in rc.9 I will close this issue.
Try out the new useSetI18nParams composable, more detailed example of its usage here! Internally it works in a similar way to the workarounds described here, but improves on it by updating meta tags during SSR as well.
If you run into any bugs please open a new issue with a minimal reproduction 💪

It some time but with #2580 merged and released in rc.9 I will close this issue.
Try out the new useSetI18nParams composable, more detailed example of its usage here! Internally it works in a similar way to the workarounds described here, but improves on it by updating meta tags during SSR as well.
If you run into any bugs please open a new issue with a minimal reproduction 💪

Thank you @BobbieGoede - the new release solved my issues and the useSetI18nParams seems to work as expected. 👍


Connect Cancel Button Cause Connect Error Going Forward

When using the SnowflakeExcelAddin.xlam Add In, if I click Connect and then Cancel.  Every time afterwards I receive an error "ERROR: Problem connecting: SQL compilation error:  Object does not exist, or operation cannot be performed."
This did go away once after my computer went to sleep over night but I was able to recreate by clicking Cancel from the Connect Window.

I'm not able to reproduce this one.
Does the error happen after you click OK once you entered the user/password? Are you using SSO or username and password?
Are you able to see what the last SQL executed was in Snowflake? If you look on the History tab in the Snowflake UI you should see a query executed with an error. Would you let me know what that is?
Thanks.

I am using SSO.   Attached are screenshots.  The history was from an hour ago.  No new queries seem to be issued.
[cid:23401ae3-4ec4-473a-bf1d-2c2761e548db]
Thanks for the quick reply.  The tool is awesome when working!!!
Terry Campbell
Sr. Manager, IT - Enterprise Intelligence Systems
6600 N. Military Trail | Boca Raton,  FL 33496
Tel:<PHONE_NUMBER> | Terry.Campbell<EMAIL_ADDRESS>[Office Depot | Max]
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

From: Steven Segal @.>
Sent: Thursday, March 18, 2021 5:13 PM
To: Snowflake-Labs/Excelerator @.>
Cc: Terry Campbell @.>; Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
[CAUTION: EXTERNAL SENDER]
I'm not able to reproduce this one.
Does the error happen after you click OK once you entered the user/password? Are you using SSO or username and password?
Are you able to see what the last SQL executed was in Snowflake? If you look on the History tab in the Snowflake UI you should see a query executed with an error. Would you let me know what that is?
Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Snowflake-Labs/Excelerator/issues/21#issuecomment-802303633, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHON4JJNPE6LAVARM5T43X3TEJUIBANCNFSM4ZNLXQGQ.

Good morning, I tried using the addin this morning after waking my laptop from hibernation.  I was able to connect the first time.  I closed excel.  I launched Excel again a little later and cannot connect to Snowflake.  I receive the "ERROR: Problem connecting: SQL compilation error: Object does not exist, or operation cannot be performed.".

Another user I am working with is having the same issue.

Terry,
Would you check your version of the Add-in? Click the Config button in the Ribbon. You should see the version number at the top. If you don't have the latest (1.1.15), would you download it?

I have 1.1.13.  I will update to 1.1.15.  Thanks.
Terry Campbell
Sr. Manager, IT - Enterprise Intelligence Systems
6600 N. Military Trail | Boca Raton,  FL 33496
Tel:<PHONE_NUMBER> | Terry.Campbell<EMAIL_ADDRESS>[Office Depot | Max]
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

From: Steven Segal @.>
Sent: Friday, March 19, 2021 11:28 AM
To: Snowflake-Labs/Excelerator @.>
Cc: Terry Campbell @.>; Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
[CAUTION: EXTERNAL SENDER]
Terry,
Would you check your version of the Add-in? Click the Config button in the Ribbon. You should see the version number at the top. If you don't have the latest (1.1.15), would you download it?
[image]https://user-images.githubusercontent.com/13276366/111804096-bef67d00-889d-11eb-851d-574648b7410a.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Snowflake-Labs/Excelerator/issues/21#issuecomment-802915817, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHON4JNB4R2726OK7IP74ZLTENUSNANCNFSM4ZNLXQGQ.

I installed 1.1.15 but extracting the new download over the existing files.  I updated the file properties and checked the unblock check box.  I was able to connect and run a query.
I closed Excel and reopened Excel.  I can no longer run queries.  I am receiving the same error.
[cid:01dab402-f40c-47ec-af12-6857a8de431b]
I am available for a debug session if you'd like.
Thanks.
Terry Campbell
Sr. Manager, IT - Enterprise Intelligence Systems
6600 N. Military Trail | Boca Raton,  FL 33496
Tel:<PHONE_NUMBER> | Terry.Campbell<EMAIL_ADDRESS>[Office Depot | Max]
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

From: Terry Campbell @.>
Sent: Friday, March 19, 2021 11:35 AM
To: Snowflake-Labs/Excelerator @.>; Snowflake-Labs/Excelerator @.>
Cc: Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
I have 1.1.13.  I will update to 1.1.15.  Thanks.
Terry Campbell
Sr. Manager, IT - Enterprise Intelligence Systems
6600 N. Military Trail | Boca Raton,  FL 33496
Tel:<PHONE_NUMBER> | Terry.Campbell<EMAIL_ADDRESS>[Office Depot | Max]
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

From: Steven Segal @.>
Sent: Friday, March 19, 2021 11:28 AM
To: Snowflake-Labs/Excelerator @.>
Cc: Terry Campbell @.>; Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
[CAUTION: EXTERNAL SENDER]
Terry,
Would you check your version of the Add-in? Click the Config button in the Ribbon. You should see the version number at the top. If you don't have the latest (1.1.15), would you download it?
[image]https://user-images.githubusercontent.com/13276366/111804096-bef67d00-889d-11eb-851d-574648b7410a.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Snowflake-Labs/Excelerator/issues/21#issuecomment-802915817, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHON4JNB4R2726OK7IP74ZLTENUSNANCNFSM4ZNLXQGQ.

Terry, as discussed this issue is due to the pseudo role ALL.
The latest version of the Add-in 1.1.16, will set the role to an empty string if the previous Role used was ALL. This should prevent the error from occurring.
Please download the latest version and let me know if it works for you.
Thanks.
Steve

Thanks Steven, I will download today and test it out.   Really appreciate the support.
Sent from my T-Mobile 4G LTE Device
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Steven Segal @.>
Sent: Monday, March 22, 2021 11:12:02 PM
To: Snowflake-Labs/Excelerator @.>
Cc: Terry Campbell @.>; Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
[CAUTION: EXTERNAL SENDER]
Terry, as discussed this issue is due to the pseudo role ALL.
The latest version of the Add-in 1.1.16, will set the role to an empty string if the previous Role used was ALL. This should prevent the error from occurring.
Please download the latest version and let me know if it works for you.
Thanks.
Steve
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Snowflake-Labs/Excelerator/issues/21#issuecomment-804549708, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHON4JJLDY3N3QIUFSTZFS3TFABIFANCNFSM4ZNLXQGQ.
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

Steven,
1.1.16 is working great for me.  Thank you for the quick turnaround and the great tool!
Regards,
Terry
Terry Campbell
Sr. Manager, IT - Enterprise Intelligence Systems
6600 N. Military Trail | Boca Raton,  FL 33496
Tel:<PHONE_NUMBER> | Terry.Campbell<EMAIL_ADDRESS>[Office Depot | Max]
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

From: Terry Campbell @.>
Sent: Tuesday, March 23, 2021 7:21 AM
To: Snowflake-Labs/Excelerator @.>; Snowflake-Labs/Excelerator @.>
Cc: Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
Thanks Steven, I will download today and test it out.   Really appreciate the support.
Sent from my T-Mobile 4G LTE Device
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Steven Segal @.>
Sent: Monday, March 22, 2021 11:12:02 PM
To: Snowflake-Labs/Excelerator @.>
Cc: Terry Campbell @.>; Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
[CAUTION: EXTERNAL SENDER]
Terry, as discussed this issue is due to the pseudo role ALL.
The latest version of the Add-in 1.1.16, will set the role to an empty string if the previous Role used was ALL. This should prevent the error from occurring.
Please download the latest version and let me know if it works for you.
Thanks.
Steve
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Snowflake-Labs/Excelerator/issues/21#issuecomment-804549708, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHON4JJLDY3N3QIUFSTZFS3TFABIFANCNFSM4ZNLXQGQ.

Great to hear Terry. It was great working with you on this.
Are both issue now resolved? If so would you close them out?
Thanks.
Steve

Yes sir, both issues are resolved.  You can close issues #21 and #22.  Thanks again!
Terry Campbell
Sr. Manager, IT - Enterprise Intelligence Systems
6600 N. Military Trail | Boca Raton,  FL 33496
Tel:<PHONE_NUMBER> | Terry.Campbell<EMAIL_ADDRESS>[Office Depot | Max]
CONFIDENTIALITY NOTICE: The information contained in this email and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this email in error, please immediately notify the sender and delete it from your system.

From: Steven Segal @.>
Sent: Tuesday, March 23, 2021 11:06 AM
To: Snowflake-Labs/Excelerator @.>
Cc: Terry Campbell @.>; Author @.>
Subject: Re: [Snowflake-Labs/Excelerator] Connect Cancel Button Cause Connect Error Going Forward (#21)
[CAUTION: EXTERNAL SENDER]
Great to hear Terry. It was great working with you on this.
Are both issue now resolved? If so would you close them out?
Thanks.
Steve
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Snowflake-Labs/Excelerator/issues/21#issuecomment-804980105, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHON4JLCA3UTTGPYMQPCA6DTFCVBHANCNFSM4ZNLXQGQ.


Support for Ed25519?

Will a future update add support for Ed25519 encryption?

As far as I know, OpenVPN does not support Ed25519.

It will ask which authentication method you wish the guts of your server to use. If you go for WireGuard, you don't get to choose: you will use a Curve25519 public key, which provides 128-bit security.

Also mentioned in the README.


[OPAL-353] Make changes to bluesky adapter backwards compatible

@ouranos @BrunoChauvet Note that this PR is not compatible with my changes on mnoe-angular and mnoe-admin panel (only minor changes required)


[QUESTION] - Is it possible to search using multiple queries on different fields?

In the following example:
[{"code": "A000", "desc": "Cholera due to Vibrio cholerae 01, biovar cholerae", "work_item": 1}]

I was wondering if I could search like this: "Cholera" IN "desc" AND "1" IN "work_item".
In this library, I could search using SearchParams{Query: "Cholera", Properties: []string{"desc"}}.
If I could search using multiple queries it would be great:
SearchParams{Query: "Cholera", Properties: []string{"desc"}} AND SearchParams{Query: "1", Properties: []string{"work_item", Exact: true}}

It's an interesting idea. I plan to add faceted search to this library, which would partially solve your problem. However, adding support for multiple queries, as you mentioned, is not currently on my list.

I'm not sure it's good implementation, I've implemented it this way to make it work as per my requirement at the moment.
func (db *Store[Schema]) Search(params *Params) (Result[Schema], error) {
	if db.cache == nil {
		db.cache = make(map[uint64]map[int64]float64)
	}
	cachedKey := params.ToInt64()
	if cachedKey != 0 {
		if score, ok := db.cache[cachedKey]; ok {
			return db.prepareResult(score, params)
		}
	}
	idxParams, err := db.prepareFindParams(params)
	if err != nil {
		return Result[Schema]{}, err
	}
	queryScores := db.findDocumentIds(idxParams)
	if len(params.Extra) > 0 {
		idScores := make(map[int64]float64)
		for key, val := range params.Extra {
			param := &Params{
				Query:      fmt.Sprintf("%v", val),
				Properties: []string{key},
				BoolMode:   params.BoolMode,
				Exact:      true,
				Tolerance:  params.Tolerance,
				Language:   params.Language,
			}
			extraParams, err := db.prepareFindParams(param)
			if err != nil {
				return Result[Schema]{}, err
			}
			scores := db.findDocumentIds(extraParams)
			for id, _ := range scores {
				if v, k := queryScores[id]; k {
					idScores[id] = v
				}
			}
		}
		if cachedKey != 0 {
			db.cache[cachedKey] = idScores
		}
		return db.prepareResult(idScores, params)
	}
	if cachedKey != 0 {
		db.cache[cachedKey] = queryScores
	}
	return db.prepareResult(queryScores, params)
}

If it works for you, that's fine, but you are only binding queries to properties, in your example you wanted the second serach to be exact, with this implementation the rest of the parameters are shared between queries.

So, in above implementation what I tried to do is:

Search the main query with provided properties
Whenever there's any extra param (map[string]any), I'm applying new query for the key, value (exact = true) of param

That is individual query has it's own set of parameters
data := readFileAsMap("icd10_codes.json")
	ftsSearch := search.New[any](&search.Config{
		TokenizerConfig: &tokenizer.Config{
			EnableStopWords: true,
			EnableStemming:  true,
		},
	})
	errs := ftsSearch.InsertBatch(data, 100)
	if len(errs) > 0 {
		panic(errs)
	}
	start := time.Now()
	s, err := ftsSearch.Search(&search.Params{
		Query:    "Diabetes in pregnancy first trimester",
		BoolMode: search.AND,
		Exact:    false,
		Extra: map[string]any{
			"code": "O24911",
		},
	})
	if err != nil {
		panic(err)
	}
	fmt.Println(s.Hits)

https://gist.github.com/sujit-baniya/3e23d90e44dc7cfbef09e66f80fc7a18

It looks a bit hacky, but as I said, if it works for you, that's fine. I'll close this issue, because there are no plans to change the library API to support such a query.


[Bug-FE][UI Next][V1.0.0-Alpha] shell componentTwo fields are missing

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
shell component Two fields are missing

What you expected to happen
Consistency with other components
How to reproduce
Two fields are missing
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This issue is the same as #9073 .


More live update of settings

currently few settings changes after initialization is complete does not update the dom nodes.
This needs to be fixed.

Added initialize function. Hence, to update the dimension after a settings update is acheived through

detach
initialize
attach


Cherry pick add sort fun when filter label in tag page

Add sort fun when filter label in tag page #4617
Modify images filter with label issue

Coverage decreased (-0.03%) to 64.413% when pulling 3839b39706ce66fb00662419a2e95421e75258b2 on pengpengshui:upstreamLabelFilter into b22ca7ec91bcd307ab91bf4dcf9ed56dc81f02bc on vmware:release-1.5.0.


Scanner fails when provided OpenAPI specification file is of moderate size

I am trying to run scans for Argo CD project. The OpenAPI specification file of Argo CD is not too huge, it is around 284KB. When I start the scan, it fails with below error:
Job openapi started
Job openapi target: https://localhost:8000/ invalid API URL: https://localhost:8000/swagger.json
Job openapi finished, time taken: 00:00:01
Automation plan failures:
        Job openapi target: https://localhost:8000/ invalid API URL: https://localhost:8000/swagger.json
WARNING:The ZAP process did not finish correctly, and exited with code 1

In the zap.log, I see some deserialization errors
2024-02-29 19:35:24,526 [main ] INFO  CommandLine - Job openapi started
2024-02-29 19:35:25,576 [main ] WARN  DeserializationUtils - Error snake-parsing yaml content
io.swagger.v3.parser.util.DeserializationUtils$SnakeException: Exception safe-checking yaml content  (maxDepth 2000, maxYamlAliasesForCollections<PHONE_NUMBER>)
	at io.swagger.v3.parser.util.DeserializationUtils$CustomSnakeYamlConstructor.getSingleData(DeserializationUtils.java:483) ~[openapi-beta-37.zap:?]
	at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:493) ~[openapi-beta-37.zap:?]
.........

2024-02-29 19:35:25,639 [main ] ERROR DeserializationUtils - Error parsing content
com.fasterxml.jackson.dataformat.yaml.JacksonYAMLParseException: The incoming YAML document exceeds the limit: 3145728 code points.
 at [Source: (StringReader); line: 49813, column: 50]
..........

2024-02-29 19:35:25,702 [main ] WARN  OpenAPIV3Parser - Exception while parsing:
com.fasterxml.jackson.dataformat.yaml.JacksonYAMLParseException: The incoming YAML document exceeds the limit: 3145728 code points.
 at [Source: (StringReader); line: 49813, column: 50]

Looks like it is related to https://github.com/swagger-api/swagger-parser/pull/1872. I could workaround the failure by adding a global JAVA system property to increase the maxYamlCodePoints as suggested in the swagger-parser PR.
export _JAVA_OPTIONS=-DmaxYamlCodePoints=99999999

After adding _JAVA_OPTIONS I am able to run the scans successfully via Rapidast.
Enviroment
I am running Rapidast on Mac M1.

Thanks for the info & analysis !
We will try to find a nice way to integrate this. It's not the first time we see problems with large OpenAPI.
Maybe we could add a misc option such as expect_large_openapi: [true|false]

Maybe we could add a misc option such as expect_large_openapi: [true|false]

It might be challenging to define 'large'. How about just adding one for configuring "maxYamlCodePoints=NNN"?

I created a PR for this: we have currently decided to simply add a troubleshooting note for adding the corresponding environment variable.
Also, a quick note: from my previous analysis of another instance of this particular crash, we found out that converting from Swagger v2 to Swagger v3 could also resolve the problem (at least in that particular case). So if you're using a Swagger v2 as source, it might be worth checking if updating to v3 helps.


[libmicrohttpd] update to 1.0.1

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Feature https tested successfully in x64-linux triplet.


[enhancement] insert multiple schemaless records using JSON

This is originally from https://groups.google.com/forum/#!topic/orient-database/A2eJvthrYnk. It was suggested I open an enhancement ticket.
I have three records that I need to insert in a single query:
{name: 'mal', role: 'captain', ship: 'firefly'}
{name: 'zoe', role: 'first', husband: 'wash'}
{name: 'book', role: 'shephard', past: 'unknown'}

What I really want is for this to be possible:
INSERT INTO characters CONTENT {}, {}, {}
Obviously with the correct JSON content. But that throws errors.
The only alternative I can find is following the VALUES syntax like
INSERT INTO characters (name, role, ship, husband, past)
VALUES
('mal', 'captain', 'firefly', null, null),
('zoe', 'first', null, 'wash', null),
('book', 'shephard', null, null, 'unknown')

However, building this programatically (like inside a query builder) is a nightmare.

What I really want is for this to be possible:
INSERT INTO characters CONTENT {}, {}, {}

or:
INSERT INTO characters CONTENT [{}, {}, {}]

:+1:

This is cool, nice catch @chrismichaels84. Kudos to your team @luigidellaquila and @lvca for this enhancement in version 2.2.0


Add nav bar to contributors.html

contributors.html needs a the new nav bar linked to it, with the nav menu changed

@michaella23 I can take care of this

I think PR #98 closes this, right @Samcraig77 ?

Right you are @michaella23, thanks for the heads up 😊


Cinder / nova plugin loose ends

Follow up on https://github.com/openvstorage/framework-cinder-plugin/issues/17 where features of cinder backup and nova migration are not implemented/tested, so following items need to be taken into account when continuing the work on this.

[ ] Package the OVS FWK rest client
[ ] Think about possible integration of OVS template capability
[ ] Upload volume to image: investigate why the removal of the image from the local path immediately after upload to glance seems to be nothing more than a reference in glance. Is the upload async or done with wrong params?
[ ] Support for change volume type? Purely OVS wise this would mean the volume has to end up on another vpool, when different vpools would use the same backend the best integration would be a volume detach/attach to namespace operation. In all other cases we require a full data copy.
[ ] Nova snapshot fails with a not implemented error. Needs to be investigated further(libvirt or qemu) and see what we can do.

Hi @wimpers.
Cinder has a important feature, it create a volume then attach volume to existing instances.
Attach_volume method in driver  do nothing.
Thanks.
Hoan.

Hi @hoanhdo, I believe you are referring to https://github.com/openvstorage/framework-cinder-plugin/issues/19 . Thanks for reporting that one. The cinder plugin is fully functional with the Newton release.  We currently don't have the bandwidth to validate the  Octa release.

@wimpers
I am not referring #19 .
Because #19, i installed newton realease .This feature in newton realease.
Thanks.

One more interesting feature, both glance and cinder use OpenVStorage, it can zero copy, time to create volume from image is very fast.
Thanks.

This plugin is no longer used.


Is there any way to forge CPU usage?I don't want people to see the real CPU load by command

Is there any way to forge CPU usage?I don't want people to see the real CPU load by command

Could you please tell us what do you do by hiding the CPU usage and we'll try to suggest you what to do.

We can hide miner CPU usage by hooking kernel function account_process_tick. By doing so, we can skip the ticks(https://superuser.com/a/101202/1315928) for our  process. Our CPU usage could not be accounted for and would be equal to zero.


Cache URLParser objects for reuse

Cache URLParser objects for reuse
Description

URLParser objects are created once in every RouterRequest. Their creation involves a conversion of String representation of a URL to Data followed by a parsing step. Typically, a webservice consists of a limited number of routes, and hence a limited number of target URLs. It may hence make sense to cache the URLParser objects against the String representations of the URLs. Since we are talking about a limited number of URLs here, the possibility of a leak is negligible.
Motivation and Context
Caching can lead to a significant performance gain in certain workloads.
How Has This Been Tested?
Tested on Linux and macOS

I don't understand how you are caching UrlParsers based on URLs.
Won't they often be different? Even if only by an id in the URL.

Hi @shmuelk - I am hoping to cache the KituraNet.URLParser objects which simply look like a collection of parsed components of a URL. I assume identical URLs will can share  URLParser objects?

You are correct that the same exact URLs can share the same URLParser object. However, that will negate your assumption of the number of URLParse objects involved. You will be potentially caching one URLParse object for every single HTTP request ever made to the server. The question will be how many of the URLs in the requests will be duplicates.

Thanks @shmuelk I get your question now. Give me some time! I need to do some more work on
https://github.com/IBM-Swift/Kitura-NIO/pull/106 to answer this question :)

After careful consideration, we've dropped the idea of reusing HTTPServerRequest and HTTPServerResponse objects in Kitura-NIO. With that, this proposal also goes out of scope. Closing the PR.


DockerCompose@0 - Add Compose CLI/ACI Support

Required Information
Question, Bug, or Feature?
Type: Feature
Enter Task Name: DockerCompose@0
Description
We're currently trying to set up a pipeline to deploy a multi-container group to ACI using a docker-compose.yml file, but the DockerCompose@0 task only supports the original compose tool (docker-compose ...) and not the newer compose-cli tool (docker compose ...) that can deploy to ACI.
I tried setting the dockerComposePath input to a shell script that forwards its arguments to docker compose, but then I realised that the two commands expect their arguments in a different order: docker-compose -f <file> up vs. docker compose up -f <file>.
It would be helpful if the DockerCompose@0 task supported compose-cli and ACI natively.

This hasn't been implemented yet.

This hasn't been implemented yet.

is this being worked on?


Show keypad sn column also in pdf.

Fixed: Show "vote now" button for named voting only.

@jwinzer Do you want to review/test this pr?

Tested. Approved.


Measurement rate instead of oversampling rate used for generation of scaling factor

Hi, thank you for your work with this library!
I'm currently building a project based on the DPS310 and am using parts of your code to interface with the sensor.
While connecting my sensor, I noticed that the measurement rate (i.e. the burst length when using the sensor in Background mode) is stored in the variables g_pressure_rate and g_temperature_rate and subsequently used to derive the scale factor.
https://github.com/sensidev/sensor-dps310/blob/e2ee938cd0ec35660f006ea6e3ebe7f3e7bac709/dps310.c#L271-L298
This leads to wrong results since the relevant parameter for deriving the scale factor is actually the oversampling rate (see Table 9 in the datasheet).

@jadeaffenjaeger Thank you very much for this observation - would you like to submit a pull request?
I was inspired from the original library available on Infineon github repo.
Maybe you would like to create an issue also on their repo - to help fix this.
https://github.com/Infineon/DPS310-Pressure-Sensor/blob/667f6e0d17696e683d36361cdad8fd1d62a198a7/src/DpsClass.cpp#L4


pvnet_app: add sentry

Add sentry to PVnet foreacst
Will have to do small infrastructure change, to add sentry dsn too

@peterdudfield is this done?

yes, althought I would like @ADIMANV to perhpas tidy it up in a new format, so ill leave it open if thats ok


Include count next to species names on dropdown

Makes using length indicators easier

Added in d7568b4

Added in d7568b4


Wrong Resultset Exported, Export Using Wrong Values For SQL Variables

Using DBeaver 4.0.8 against a DB2 for i database to export various resultsets
SQL Select contains variables with values set within the session
When exporting a resultset, the export uses values for the SQL variables from the database rather than the values set in the session. What's being exported is not the resultset in the Result pane.
-- Create SQL variables
CREATE OR REPLACE VARIABLE HHRlib.BegDate Date DEFAULT '2016-12-01';
CREATE OR REPLACE VARIABLE HHRlib.EndDate Date DEFAULT '2016-12-31';
-- Simple Range Query
SELECT Min(CountDate), Max(CountDate), Count(*)
FROM TcsLib.TcsRadarP
WHERE CountDate BETWEEN HHRLib.BegDate AND HHRLib.EndDate;
Select Results:
Min Date		Max Date		Count
2016-12-01	2016-12-31	157422
-- Change dates for SQL variables
-- SET only updates values for SQL variable within current session
SET HHRLib.BegDate = '2017-05-01';
SET HHRLib.EndDate = '2017-05-31';
Rerun Simple Range Query Results:
Min Date		Max Date		Count
2017-05-01	2017-05-31	160134
But when Exporting the Resultset (whether right click on SQL statement or in Result pane), the Export picks up the values for the SQL variables from the database rather than from the session, resulting in the wrong resultset being exported:
Min Date		Max Date		Count
2016-12-01	2016-12-31	157422

Hi,
Can you confirm that you have unchecked "open new connection(s)" in the export settings?
if it's checked, what you see is expected.

Regards

The box was checked. Unchecking "open new connection(s) fixed my issue.
Thank you!!

Hi, Serge.
The box was checked. Unchecking the box fixed my issue.
Thank you for your help. I've closed the issue.
Regards,
Herb.

From: masebu<EMAIL_ADDRESS>Sent: Wednesday, June 14, 2017 5:25 AM
To: serge-rider/dbeaver
Cc: Herb Rea; Author
Subject: Re: [serge-rider/dbeaver] Wrong Resultset Exported, Export Using Wrong Values For SQL Variables (#1765)
Hi,
Can you confirm that you have unchecked "open new connection(s)" in the export settings?
if it's checked, what you see is expected.
[image]https://user-images.githubusercontent.com/19706602/27125184-bf7b787e-50f3-11e7-9895-a7c8c03883d6.png
[https://user-images.githubusercontent.com/19706602/27125184-bf7b787e-50f3-11e7-9895-a7c8c03883d6.png]
Regards
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/serge-rider/dbeaver/issues/1765#issuecomment-308375938, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AcCwBgWDGwkThEycu0HyBQ1I7kW1XeaYks5sD6cigaJpZM4N4lCx.


Adding ETS2 launch parameter

Hello,
Is it possible to add a launch option like in the Steam Game properties? In my case I need a "-sysmouse" otherwise I don't have a mouse pointer on the desktop after ALT-TAB out of the game.

Currently ETS2/ATS options are hardcoded:

Multiplayer: main() [truckersmp-cli.c]

const char opts[] = "-nointro -64bit";

Singleplayer: start_with_proton() [truckersmp_cli/main.py]

argv += gamepath, "-nointro", "-64bit"

If we need to allow to use other options, we need to:

add new option (e.g. --game-options="-option1 -option2 ...") to our Python script
add command line options handling to truckersmp-cli.c

An example of command line options handling for our inject program:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>

#define BUF_SIZE 1024

int
main(int argc, char **argv)
{
    int i;
    char opts[BUF_SIZE] = {0};

    if (argc < 3) {
        fprintf(stderr, "Usage: truckersmp-cli GAMEDIR MODDIR, GAME_OPTIONS...\n");
        return EXIT_FAILURE;
    }

    if (argc == 3)
        strcpy(opts, " -nointro -64bit");

    for (i = 3; i < argc; i++) {
        strcat(opts, " ");
        strcat(opts, argv[i]);
    }

    printf("options: \"%s\"\n", opts);

    return EXIT_SUCCESS;
}

(Too few arguments)
$ ./opttest
Usage: truckersmp-cli GAMEDIR MODDIR, GAME_OPTIONS...

(Use default options)
$ ./opttest /path/to/game /path/to/mod
opts: " -nointro -64bit"

(Use custom options)
$ ./opttest /path/to/game /path/to/mod -nointro -64bit -sysmouse
opts: " -nointro -64bit -sysmouse"

As a workaround, users can edit the hardcoded options, compile truckersmp-cli.c, and replace original truckersmp-cli.exe with compiled executable.

Thanks for the advice of workaround. I compiled truckersmp-cli.exe with the additional launch option and it works.
It would be nice to have an option for ETS2/ATS specific launch parameter in a newer version of truckersmp-cli, because there are some useful options to tweak performance a bit like "-mm_max_resource_size" or "-mm_max_tmp_buffers_size".


standarized IPEX, ITEX & INC abbrevations

@ishaghosh27 I have made some new commit resolving the above issues. Please have a look


Error: listen EAFNOSUPPORT

Hello
I have the next issue:
droppy start
     __
  --|  |---- ----- ----- ----- -- --
 |  _  |   _|  _  |  _  |  _  |  |  |
 |_____|__| |_____|   __|   __|___  |
                  |__|  |__|  |_____|

 droppy 3.5.3 running on node 0.10.36
 config at /root/.droppy
 files at /root/.droppy/files

2015-11-06 17:54:55 [INFO] Loading and minifying resources ...
2015-11-06 17:54:55 [INFO] Listening on http://<IP_ADDRESS>:8989
2015-11-06 17:54:55 [ERROR] Error: listen EAFNOSUPPORT
    at errnoException (net.js:905:11)
    at Server._listen2 (net.js:1024:19)
    at listen (net.js:1065:10)
    at net.js:1147:9
    at dns.js:72:18
    at process._tickCallback (node.js:442:13)
[ERROR] Error: listen EAFNOSUPPORT

How can I fix it?

Could I get some more detail of the IP configuration on your maching? Maybe post or mail me the output of ip addr or ifconfig. Is IPv4 perhaps disabled?

`ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:9B:20:07
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:76573 errors:0 dropped:0 overruns:0 frame:0
TX packets:81254 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:104529807 (99.6 MiB)  TX bytes:16727394 (15.9 MiB)
lo        Link encap:Local Loopback
inet addr:<IP_ADDRESS>  Mask:<IP_ADDRESS>
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:276 errors:0 dropped:0 overruns:0 frame:0
TX packets:276 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21438 (20.9 KiB)  TX bytes:21438 (20.9 KiB)`
 cat /etc/redhat-release CentOS release 6.7 (Final)

Looks like it's related to the missing IPv6. I'll test in a VM.

Ok. I am looking forward to the results

While I couldn't reproduce your exact error, even when disabling IPv6, I now handle such listening errors gracefully and it will start up if at least one listening socket is present (while still printingt the errors, which you can fix through droppy config.
Relevant commits:

https://github.com/silverwind/droppy/commit/d0c28f6106980731494cdafbb6d5eecf93d73d36
https://github.com/silverwind/droppy/commit/a4dc3cc5d0b37335e3f3de2065bc2554cfaa43da

Thanks for reporting!

I try to update and i have next error
make: Entering directory /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/utf-8-validate/build'   CXX(target) Release/obj.target/validation/src/validation.o In file included from ../src/validation.cc:15: ../node_modules/nan/nan.h:328: ошибка: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’ make: *** [Release/obj.target/validation/src/validation.o] Ошибка 1 make: Leaving directory /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/utf-8-validate/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 2.6.32-573.7.1.el6.x86_64
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/utf-8-validate
gyp ERR! node -v v0.10.36
gyp ERR! node-gyp -v v0.10.6
gyp ERR! not ok
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm http GET https://registry.npmjs.org/streamsearch/0.1.2
npm http GET https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/inherits

<EMAIL_ADDRESS>install /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

make: Entering directory /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/bufferutil/build'   CXX(target) Release/obj.target/bufferutil/src/bufferutil.o npm http 304 https://registry.npmjs.org/streamsearch/0.1.2 In file included from ../src/bufferutil.cc:16: ../node_modules/nan/nan.h:328: ошибка: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’ make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Ошибка 1 make: Leaving directory /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/bufferutil/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 2.6.32-573.7.1.el6.x86_64
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/admin7/fsapp/droppy_new/droppy/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v0.10.36
gyp ERR! node-gyp -v v0.10.6
gyp ERR! not ok
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>

This looks to be caused by the patched version of node which CentOS uses. I recommend using a nodesource version of node, ideally 0.12 or above:
https://github.com/nodesource/distributions#installation-instructions-1
And then do a clean install.`


Unclear what 'state' is

I was looking at this page https://github.com/ReactTraining/history/blob/v3/docs/Location.md and I'm not sure what it means. I am looking for a way to redirect from a function and wondered how to pass data into the receiving page, so I thought this will work (?):
import { push } from 'react-router-redux';

const myFunc = ({ name, address }) => (
    push({
        pathname: '/foo',
        state: {
            name,
            address,
        }
    })
);

then in /foo, the component setup on the route for this path will receive the data:
this.props.location.name;
this.props.location.address;

Is there an alternative that allows Json-like data to be passed to a page?


Evaluate switching to Symphony LLC developed Java client

Symphony LLC have released a Java client for their API that appears to duplicate some or all of the functionality of the community-developed Symphony Java Client that clj-symphony is currently using.
The task here is to evaluate the new library and determine whether it might be a better choice for clj-symphony going forward.  See also https://github.com/symphonyoss/symphony-java-client/issues/122 and https://github.com/SymphonyPlatformSolutions/symphony-api-client-java/issues/8.

Based on a recent chat conversation with @ftbb (summarised in https://github.com/symphonyoss/symphony-java-client/issues/122), SJC remains the preferred option.

Reopening this issue, given the status changes proposed here: https://github.com/symphonyoss/symphony-java-client/pull/143

This task should also consider https://github.com/deutschebank/symphony-java-client-parent, especially given that the Symphony LLC developed Java client is not a FINOS-hosted project (and so doesn't provide the kinds of longevity and governance guarantees needed by clj-symphony).


”Marpod”, ”Ilimbav” are listed in the drop-down menu

Description:
When user writes ”Marpod”, ”Ilimbav” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Marpod"

Expected results
The location appears in the drop-down menu as "Sat Marpod, SIBIU (Marpod)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Ilimbav"

Expected results
The location appears in the drop-down menu as "Sat Ilimbav, SIBIU (Marpod)".


New license

Coverage remained the same at 57.865% when pulling c2396b114374974566d98a664bf28ffbc3f5b72a on lmazuel:new_license into 06499603a16830e022becf77fa535f3ddb8b1ccf on Azure:dev.


Claim FB page

Perhaps we are in a place now where we can "claim" the old FB page and merge the followers from old page into ours?
Current FB page (owned by scikit-learn):
https://www.facebook.com/scikitlearnofficial
Older FB page: 871 followers
https://www.facebook.com/ScikitLearn
Resource: claim FB page
https://www.reviewtrackers.com/blog/claim-facebook-business-page/
cc:  @laurburke

I can look into this! They may require our page to exist for over a certain time period before they take action

Hello @laurburke, do you have news about this issue?

I think we may need to have the page for a bit longer before we would be able to file for a claim. I would say after 6 months, we can file the motion to claim the other page and merge them.


Can llavanext-llama3-8B see more than one image in one conversation

I am following the LLaVa-NeXT-Image example and have been able to get the exact same results as the example. However, I wish to give the model 2 images or more in the same conversation prompt. So now I am passing 2 images for the image_tensor and modifying the prompt part like this:
image1 = Image.open("1.png")
image2 = Image.open("2.png")
image_tensor = process_images([image1, image2], image_processor, model.config)
image_tensor = [_image.to(dtype=torch.float16, device=device) for _image in image_tensor]

text1 = DEFAULT_IMAGE_TOKEN + "\nThis is image1"
text2 = DEFAULT_IMAGE_TOKEN + "\nThis is image2"
question = "tell me how many images do you see?"
conv.append_message(conv.roles[0], text1)
conv.append_message(conv.roles[0], text2)
conv.append_message(conv.roles[0], question)
conv.append_message(conv.roles[1], None)
...

And I am getting the output as ['\nI see one image of a person with pink hair and glasses.']
The interesting thing is that image1 is a photo of a woman with pink hair, and image2 is a man with glasses. So the model seems to see both images but treats them as a whole. I don't know if there is something wrong with my implementation of the conversation or if this is the expected behavior of llavanext-llama3-8B. Also I would want to know if there are ways to let the model see 2 images at the same time and treat them as different images so that I can ask it to compare them?

Just noticed in the original llava repo there were a lot of comments on this, I will try out interleave.


iometer is not efficient to benchmark a Windows VM

For the Windows part, iometer is a very old app, the last update was in 2010, recently I tested with it but the result is not optimal and is not as expected.
diskspd.exe is more commonly used by Windows HA team to benchmark a disk within the Windows, and the benchmark result is also reflect the performance the Azure disk can provide.
https://github.com/Microsoft/diskspd
https://gallery.technet.microsoft.com/DiskSpd-A-Robust-Storage-6ef84e62
Can you add diskspd.exe guidance?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a29e4933-1dc6-c222-5ea5-25bdfaa3b426
Version Independent ID: 2c387745-4f69-21b2-8388-71600a09d450
Content: Benchmarking your application on Azure Disk Storage - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/disks-benchmarks.md
Service: virtual-machines-windows
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

Thanks for the issue @uonie , I've assigned this issue to the doc author to see if they want to add diskspd guidance.

@uonie Thanks for the feedback, and for reaching out, we have updated the article to use diskspd. Accordingly, I'll close this out.
#please-close


Allow providing "hint.strategy" in join operator

Include guidance regarding best practices in the docs

isn't this equivalent to 104?


dark picture / flatfield cutout is wrong?

dark_fullpic = calculate_dark(CCDitem)
image_dark_sub = (
image
- dark_fullpic[
CCDitem["NRSKIP"] : CCDitem["NRSKIP"] + CCDitem["NROW"],
CCDitem["NCSKIP"] : CCDitem["NCSKIP"] + CCDitem["NCOL"] + 1,
]
)
I think caluculate_dark allready takes into account nrskip and ncskip...

Same issue in flatfield_calibration

Yes, it looks like you are right. But I dont have any image with NSKIP to test on.  So you can remove it  and test? Or send me images to test with?

fixed


feat(tree-view-behavior): default deselectItems param

allow for nicer api by removing all items if nothing is passed to
deselectItems.
closes issue #13

Will wait for Austin to review as well.

This was handled during the refactor for #14


Add multiple screens for the beta version

Includes three button:

News: Points to the CDC website for now.
Import: Points to the privatekit.mit.edu website.
Export: Shows QR code which goes to the privatekit.mit.edu website.

The code is quite repetitive and redundant at the moment.


Stockfish support

Any plans for this?
Contributions welcome?

Contributions very welcome! Would love to support this!

By all means, please do! Let me know of you have any questions!


Move plugins

move some, but not all plug-ins, to components

@gamaanderson Which PR would you rather I focus on first?

#194 first, as #195 descend from it

I receive the following error after install
Traceback (most recent call last):
  File "/Users/guy/anaconda/bin/artview", line 4, in <module>
    import artview.__main__
  File "/Users/guy/anaconda/lib/python2.7/site-packages/artview/__init__.py", line 59, in <module>
    from . import components
  File "/Users/guy/anaconda/lib/python2.7/site-packages/artview/components/__init__.py", line 50, in <module>
    from .corrections import *
ImportError: No module named corrections

I think I just lost my computer, I will not be able to review this.
I do not understand the fail import error, you should have a corrections folder with a init.py in there.

Not sure what the heck is going on, still getting that darn error. I'm working on it, though!

I can't believe it took me this long, but I finally figured out the import error. Need to add a single line to the `artview.artview.setup.py'. Note the 8th line down.
def configuration(parent_package='', top_path=None):
    from numpy.distutils.misc_util import Configuration
    config = Configuration('artview', parent_package, top_path)
    config.add_subpackage('core')
    config.add_subpackage('components')
    config.add_subpackage('plugins')
    config.add_subpackage('scripts')
    config.add_subpackage('components.corrections')
#    config.add_subpackage('icons')
    config.add_data_dir('icons')

    return config

if __name__ == '__main__':
    from numpy.distutils.core import setup
    setup(**configuration(top_path='').todict())

my bad, as I run always local I didn't got the error.
Now it is corrected
Thank you.

No worries, I should have picked that up before. One of those nagging things that was just out of reach in my head! Going to merge and move forward. It looks good. I like the way you have divided it up.


rename test-utils to playwright-utils

objective here is to keep consistency between folder and package names

rename folder test-utils to playwright-utils
search for all occurrence of test-utils to see if needs to be replaced

it should be done only after we work on uniting the frontend repositories

it may not make sense to do this one as we already have https://github.com/FuelLabs/fuel-connectors/issues/100


Insider Edition: Explorer window shows wrong nodes when expanding/collapsing folders

VSCode Version: Version <IP_ADDRESS>-Insider (d2b050911cbf3b6e77584f61b0cf088058a20fe5)
OS Version: macOS high sierra (10.13.6)

This is what happens

Unfortunately reproducing is kinda' hard. Starts happening after a while of using VSCode

Does this issue occur when all extensions are disabled?: Yes

This is weird. Let me know if you can reproduce.

@joaomoreno well that's exactly the problem 🤔. Any way I can give you some debug info when it happens? Because it starts happening quite immediately when I start VSCode and it started with today morning's update of the insiders edition.
Also for instance, if I tell Code to select the open item in the Explorer, it fails

In the screenshot you see the list-page-base.component.ts being active, but vta-detail.component.spec.ts being selected.

I got this https://github.com/Microsoft/vscode/commit/2803a8655cf5e05066a4ee47cce303eefca6408c
Update to latest insiders to fix.

fixed!! 🎉 🎉 🎉 🎉  🙇 🙇
YOU. GUYS. SIMPLY. ROCK
keep it up 💪


lovr.headset.setBackground;

This refactors the new background layer types (cube/sphere) into a lovr.headset.setBackground function that can take an equirect or cubemap texture/images.  Now there is just 1 layer type (quads) and LayerType is removed.

stereo backgrounds aren't supported yet, but could be.
formats are annoying.  you can't do lovr.headset.setBackground('sky.hdr') because that will load an rgba32f image, but right now layers must be rgba8.  Runtimes do support other texture formats for layers, but rgba32f isn't supported everywhere.  However, you CAN do lovr.headset.setBackground(lovr.graphics.newTexture('sky.hdr')) because this will do a texture blit, which supports format conversion.  Hopefully we can smooth this out in the future.


Default password (changeme) not correctly set

Problem description
Default password (changeme) is not correctly set, and 'changeme' (with quotes) is set instead.
Running the following command:
docker-compose config | grep  "changeme"

Gives the following strings as result of parsing the .env file:
  ELASTIC_PASSWORD: '''changeme'''
  KIBANA_SYSTEM_PASSWORD: '''changeme'''
  LOGSTASH_INTERNAL_PASSWORD: '''changeme'''
  ELASTIC_PASSWORD: '''changeme'''
  KIBANA_SYSTEM_PASSWORD: '''changeme'''
  LOGSTASH_INTERNAL_PASSWORD: '''changeme'''

It seems like docker-compose is escaping the quotes found in the .env  file, where variable values are assigned as follows:
ELASTIC_PASSWORD='changeme'
LOGSTASH_INTERNAL_PASSWORD='changeme'
KIBANA_SYSTEM_PASSWORD='changeme'

After running command:
docker-compose up

Containers are created/launched as expected, but when opening the web browser or using curl,etc the default expected password changeme doesn't work but 'changeme' works fine instead.

Extra information
Stack configuration

Docker setup

$ docker version
Client:
 Version:           20.10.12
 API version:       1.41
 Go version:        go1.16.2
 Git commit:        20.10.12-0ubuntu2~20.04.1
 Built:             Wed Apr  6 02:14:38 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.12
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.2
  Git commit:       20.10.12-0ubuntu2~20.04.1
  Built:            Thu Feb 10 15:03:35 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.5.9-0ubuntu1~20.04.4
  GitCommit:
 runc:
  Version:          1.1.0-0ubuntu1~20.04.1
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

$ docker-compose version
docker-compose version 1.25.0, build unknown
docker-py version: 4.1.0
CPython version: 3.8.10
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020

Container logs

Thanks for the issue report. We are aware of this behaviour, it's been reported several times already and is caused by a bug in older versions of Compose.
Please use a supported version of Compose.
Closing as duplicate of #698

Is it possible to add a warning on the "readme" of the project so people is aware of the issue and don't report it over and over again?

I believe we do?

Requirements
Host setup

Docker Compose version 1.26.0 or newer (including Compose V2)

Also the aforementioned issue is pinned 📌

I believe we do?

Requirements
Host setup

Docker Compose version 1.26.0 or newer (including Compose V2)

We could add the word "Warning" but if people don't scroll to the requirements I doubt they will see it, no matter how many warnings we add there. (I could be wrong, just talking from experience writing docs.)
Also the aforementioned issue is pinned 📌 so when you click Issues it should appear at the very top. Hard to miss!


[BUG] UI - The longhorn URL incorrectly redirect in upgraded set up on refreshing the page.

Describe the bug
The URL incorrectly redirects in upgraded set up on refresh to something like https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy/volume#/node
To Reproduce
Steps to reproduce the behavior:

Install longhorn v1.0.2 app on a cluster in a Rancher set up.
Click the app link appears on the App page and open the longhorn page.
Upgrade the longhorn to Master.
Refresh the longhorn page.
It redirects https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy/volume#/node

Expected behavior
It should redirect to link https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy/#/dashboard
Environment:

Longhorn version: Longhorn Master commit id - 717e50a
Kubernetes version: 18.6
Node OS type and version: Ubuntu 18.04

This issue cannot be solved. Because our v1.0.2 rancher-proxy has access to the address https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http: longhorn-frontend:80/proxy/volume
Ifuser refresh the page directly after upgrading, the user will request the same address. Therefore, the user will be redirected to the wrong address. If the user clicks on the link on the rancher-ui instead of refreshing the page, then the problem should not occur.
Can we make some hints when upgrading. Prompt the user to re-visit the rancher-proxy or remove longhorn-frontend's own domain（volume, dashborad,  node, backup, setting, engineimage） from the original longhorn url. @khushboo-rancher @yasker

This issue cannot be solved. Because our v1.0.2 rancher-proxy access address is  https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http: longhorn-frontend:80/proxy/volume
Ifuser refresh the page directly after upgrading, the user will request the same address. Therefore, the user will be redirected to the wrong address. If the user clicks on the link on the rancher-ui instead of refreshing the page, then the problem should not occur.
Can we make some hints when upgrading. Prompt the user to re-visit the rancher-proxy or remove longhorn-frontend's own domain（volume, dashborad,  node, backup, setting, engineimage） from the original longhorn url. @khushboo-rancher @yasker

@smallteeths So the problem should affect the new installation? @khushboo-rancher Is it an upgrade or new installation?

It won't affect the new installation, it will only affect the existing user's browser which has our longhorn access path. For example, if a user still accesses https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/' after upgrading. proxy/volume This access will fail. He should be accessing https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy.
Of course, if the user clicks on the longhorn-ui link directly from our rancher-ui, it will redirect correctly. Because the address of the rancher-proxy is https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy @yasker

It won't affect the new installation, it will only affect the existing user's browser which has our longhorn access path. For example, if a user still accesses https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy/volume after upgrading, there will be an access error. He should be accessing https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy/.
Of course, if the user clicks on the longhorn-ui link directly from our rancher-ui, it will redirect correctly. Because the address of the rancher-proxy is https://rancher-server/k8s/clusters/c-l4d8s/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend:80/proxy @yasker

OK, that should be fine. We can add a release note to this.

It is too minor to be mentioned in the release note. Close this as won't fix for now.

In my case I upgraded from 1.0.2 to 1.1.0, and went to a bookmarked URL http://mylonghorndomain/volume which was getting redirected to the invalid URL http://mylonghorndomain/volume#/dashboard.
The fix is to just visit http://mylonghorndomain which redirects to http://mylonghorndomain/#/dashboard.


BUG : dismissViewControllerAnimated with a completion to push a new segue

If i transition to menu A , and dismissViewControllerAnimated with a completion to transition to ViewController B,then the backView will have offset which is equal to the ScreenHeight(or ScreenWidth) minus menu's contentLength
How to fix it?

#23 Will look into this. It is a bug.


PairedEndSingleSampleWf.wdl is not portable

String sub_strip_path = "gs://.*/" should be replaced with usages of basename(). At the moment this workflow can not run with S3, etc

Looks like this was done before for the five-dollar workflow, I'll use this as reference to make the change.

Exactly the case, thanks @bshifaw


Use custom uart handler alongside MCUmgr uart

I want to be able to handle serial (uart) communications using a custom protocol. I've set this up using the interrupt driven API. My problem is that I also want to enable mcumgr via serial (uart). I don't see a nice way to make these co-exist.
I thought of a couple different options: add an API to get the current uart callback so it can be saved/managed, allow the user to enable mcumgr during runtime (not only at SYS_INIT), or pass data from my callback through to the mcumgr handler.
All these options have some drawbacks so I don't know what the best solution is.
I'm using MCUmgr for FWUP, so for my use case I only need to switch from my handler to mcumgr once, but I could see a scenario where switching back and forth could be useful.

It would be a lot of effort to support something like this because it would need functions adding for removing an SMP transport and freeing up the resources of the transport. Instead I would suggest doing similar to what the shell transport does, have your own UART handling code and have it enter a mode whereby it forwards the data on to MCUmgr for processing https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/shell/backends/shell_uart.c#L94 you would need to create a new transport for this (could copy the shell one and rename it)

I'm actually using USB CDC. It seems straightforward to pass data to smp_shell using smp_shell_rx_bytes, but there doesn't seem to be a nice way to supply my own TX function. smp_shell seems directly tied to shell_uart and uses its TX function directly.

If you are using USB CDC, why not have 2 instances of it, one for your application and one dedicated for MCUmgr?

Ohh, I didn't know about that. I was able to use CONFIG_USB_COMPOSITE_DEVICE and get it working!
It would be nice if there was a way to easily distinguish the two ports host side but I can work with this. Thanks for your help!


Portfolio

@RomainGoussault aren't we good on that one with the experiment you showed us on Tuesday? I'd say this closes #140 and #146


[REEF-703] Make NameLookupClient injectable

This patch:

Adds a Tang-injectable constructor for NameLookupClient
Marks the constructor "private" to emphasize that it
should be called only by Tang
Deprecates all non-injectable constructors

JIRA:
REEF-703

@zerg-zerg I did a pass and left one comment. Also, can you suppress the warning in NameClient?

@markusweimer  I've updated the pull request

@zerg-zerg Thanks, I will merge


Implement quantum Louvain algorithms by Cade et al

Depends on #17.

[ ] QLouvain (Search + MaxFind, just Search)
[ ] Repeat Version of QLouvain (Search + MaxFind, just Search)
[ ] QEdgeLouvain: grover/max on edges (also implement a classical version)
[ ] Re-produce benchmarking results of Cade et al

What's the situation here - on hold until the classical implementation is validated?

The scaffold implementation is completed. We now have to see how to access nested data (pass max results out to the scope that called the enclosing search, for example) and then validate benchmarking results


Don't generate legacy components for new client builds

Previously caused issues when the MERGE_FILES is OFF because it tries to create very long solution source file names. These legacy components should be skipped when using TensileCreateLibraryFiles in cmake as it is designed for the new client only

Hmmm, looks like this change has broke our CI. I think you just have to pass this --no-legacy-components to the hip/CMakeLists.txt file as well


Total items ordered.

A list of all items currently on order and the quantity of each would be extremely useful for fulfillment in preorder pop-up/delivery contexts

I think "on order" is insufficiently clear to make this workable in current form...  maybe we need a seperate location like a wiki or a trello board for "feature ideas" and they become issues only when well specified/ready to be prioritized?  not sure, but want to improve state of our "open issues" to make sure most or all of them are startable without too much ambiguity


How to use ejs with uWebSockets.js?

https://ejs.co/
I need to add data to the HTML files I send. How do I do this with ejs in uWebSockets.js?

the same way you do it in node.js, why are you opening issue for this, ejs is a basic string template library

the same way you do it in node.js, why are you opening issue for this, ejs is a basic string template library

Okay, thank you!


New flag parsing breaks restic?

Thank you very much for all you hard work!
What is the problem you are having with rclone?
By default, restic calls rclone like this:
rclone serve restic --stdio --b2-hard-delete --drive-use-trash=false

Since yesterday, our integration tests break, rclone exits with an error message:
rclone: Error: invalid argument "--drive-use-trash=false" for "--b2-hard-delete" flag: parsing "--drive-use-trash=false" as bool failed: expected newline

I saw that you removed the pflag library. It looks like all the boolean flags now need an explicit true or false value, this seems to work:
rclone serve restic --stdio --b2-hard-delete=true --drive-use-trash=false

Was this breaking change intentional (not meant as an accusation, just curious)? I know that pflag has too many options for its own good :)
Do you have an idea on how to mitigate this (also from restic's point of view)? At the moment, the default arguments for rclone are hard-coded into the restic binary, but can be overwritten by command-line flags. I'm fearing that users will use an older restic binary with a fresh rclone binary and it won't work out of the box, is there anything we can do?
What is your rclone version (eg output from rclone -V)
rclone v1.42-DEV
- os/arch: linux/amd64
- go version: go1.10.3

Which OS you are using and how many bits (eg Windows 7, 64 bit)
Linux, amd64
Which cloud storage system are you using? (eg Google Drive)
Local
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone serve restic --stdio --b2-hard-delete --drive-use-trash=false

Ah, interesting! I just saw that pflag was removed almost everywhere in a commit. I'm eager to find out what's going on here ;)

Cool, thanks!


No usable generator found

###I was used llvm-mingw-20211002-msvcrt-x86_64,and follow this https://code.visualstudio.com/docs/cpp/CMake-linux to learn how to config cmake in VSCcode, all the bin I have add in system path (this cmake bin and llvm-mingw-20211002-msvcrt-x86_64 bin)
when I follow into the [CMake: Configure] step,VSCode return this error,.
I try to fix the cmake-tools-kits.json and setting.json ,but it didn't work.
the cmake-tools-kits.json part I use is (I don't change anything just native json text):
{
"name": "Clang 13.0.0 x86_64-w64-windows-gnu",
"compilers": {
"C": "F:\llvm-mingw-20211002-msvcrt-x86_64\bin\clang.exe",
"CXX": "F:\llvm-mingw-20211002-msvcrt-x86_64\bin\clang++.exe"
}
and the setting.json is:
{
"window.zoomLevel": 0,
"workbench.colorTheme": "Default Dark+",
"[cpp]": {
"editor.defaultFormatter": "ms-vscode.cpptools"
}
}
What should I do?

I try to change the json like this:
the cmake-tools-kits,json:
{
"name": "Clang 13.0.0 x86_64-w64-windows-gnu",
"compilers": {
"C": "F:\llvm-mingw-20211002-msvcrt-x86_64\bin\clang.exe",
"CXX": "F:\llvm-mingw-20211002-msvcrt-x86_64\bin\clang++.exe"
},
"preferredGenerator": {
"name": "MinGW Makefiles",
"platform": "x64"
},
"environmentVariables": {
"PATH": "F:\llvm-mingw-20211002-msvcrt-x86_64\bin"
}
}
the setting.json:
{
"window.zoomLevel": 0,
"workbench.colorTheme": "Default Dark+",
"[cpp]": {
"editor.defaultFormatter": "ms-vscode.cpptools"
},
"cmake.cmakePath": "F:\CMake\bin\cmake.exe",
"cmake.mingwSearchDirs": [
"F:\llvm-mingw-20211002-msvcrt-x86_64\bin"
],
"cmake.generator": "MinGW Makefiles"
}
but it still didn't work

While maybe I have find out the reason why, before I run cmake:quick start command ,In my project dir I have created a main.cpp
file,then after I run the quick start command the VSCode didn't auto create build dir .I have create a new empty dir and run quick cmake,this time I get the correct result
but whem I run cmake: configure the OUTPUT window output this:
[main] Configuring folder: testste
[proc] Executing command: F:\CMake\bin\cmake.exe --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_C_COMPILER:FILEPATH=F:\llvm-mingw-20211002-msvcrt-x86_64\bin\clang.exe -DCMAKE_CXX_COMPILER:FILEPATH=F:\llvm-mingw-20211002-msvcrt-x86_64\bin\clang++.exe -He:/VSCodeProject/testste -Be:/VSCodeProject/testste/build -G "MinGW Makefiles"
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Configuring done
[cmake] -- Generating done
[cmake] -- Build files have been written to: E:/VSCodeProject/testste/build
[ctest] There was an error running ctest to determine available test executables
It say "There was an error" ,What is the Error?

Today I change other computer and run Cmake: Quick Start command in a empty dir,it just create two files, one is CMakeLists.txt another is main.cpp ,the [build] dir no auto create and then the Error show up: [Unable to determine what CMake generator to use. Please install or configure a preferred generator, or update settings.json, your Kit configuration or PATH variable.]

I think I fixed this problem, before I fixed ,the native json is:

setting.json

{
   "workbench.colorTheme": "Default Dark+",
    "explorer.confirmDelete": false,
    "cmake.cmakePath": "E:\\CMake\\bin\\cmake.exe"
}

cmake-tools-kit.json

...
{
    "name": "Clang 13.0.0 x86_64-w64-windows-gnu",
    "compilers": {
      "C": "E:\\llvm-mingw-20211002-msvcrt-x86_64\\bin\\clang.exe",
      "CXX": "E:\\llvm-mingw-20211002-msvcrt-x86_64\\bin\\clang++.exe"
    }
  }
...

after fixed, add some items in it:

setting.json

{
    "workbench.colorTheme": "Default Dark+",
    "explorer.confirmDelete": false,
    "cmake.cmakePath": "E:\\CMake\\bin\\cmake.exe",

    "cmake.generator": "MinGW Makefiles"
}

cmake-tools-kit.json

...
{
    "name": "Clang 13.0.0 x86_64-w64-windows-gnu",
    "compilers": {
      "C": "E:\\llvm-mingw-20211002-msvcrt-x86_64\\bin\\clang.exe",
      "CXX": "E:\\llvm-mingw-20211002-msvcrt-x86_64\\bin\\clang++.exe"
    },
    "preferredGenerator": {
      "name": "MinGW Makefiles",
      "platform": "x64"
    }
  }
...

Hi @FuXiii sorry we weren't able to get to this issue sooner to help.  What you shared looks correct for MinGW compilers.  Do you need any help with anything else, or shall we close this issue?

Fine，close it, thanks


4.0.0-RC1 does not support mysql bulk insert?

4.0.0-RC1 does not support mysql bulk insert? The previous 3.0.1 version can be inserted in batches, and replaced with 4.0.0-RC1 without error message.
such as :
INSERT INTO tbl_name (col1, col2, …) VALUES (?, ?, ….), (?, ?, ….)

use default-data-source-name="rw0"


config to disable classification count retirmenent

closes #1368 - allow workflow's with custom retirement (aggregation engine) to disable the count retirement worker.

It might be cleaner to just have a different retirement scheme that does absolutely nothing. But I think that will require adapting PFE to support selecting between multiple schemes. Mental note to refactor this into a Never retirement scheme whenever we pick that up?

i'll have a look at a refactor to use a disabled retirement scheme.

LGTM if you want to merge this in the meantime btw.

Going to steal this WIP

thanks :+1:

closing in favour of #1528


Add collect extrinsic to reward-distribution pallet

This ticket is a part of https://github.com/pendulum-chain/tasks/issues/47
This ticket depends on https://github.com/pendulum-chain/spacewalk/issues/405
Add an extrinsic collect (or similar) that takes a the argument collateral_asset (a CurrencyId) and that allows a signed account id as the origin

call withdraw_reward of PooledRewards where pool_id is collateral_asset, stake_id is the origin, currency_id is the native token
call T::Currency::deposit_creating where who is the origin and value is the return value of withdraw_reward

Hey team! Please add your planning poker estimate with Zenhub @adelarja @b-yap @ebma @gianfra-t @TorstenStueber

If we implement the new PooledRewards as it is proposed in here, we would have to review the specifics of this issue.
Since stake_id will be vault_id, the rewards cannot be directly extracted from this pallet just by calling with the collateral_asset and the origin. If we would like to maintain the same user level functionality which is to extract all the rewards of a the native currency_id (or any reward currency) for any given nominator account_id across all vaults it stakes in, we need to store such map (probably in the stake pallet) and iterate through it when the extrinsic is called.
Alternatively, we could extend this functionality even more so that the user calls without any parameter, and iterate through all the vault_id under its control, and for each distribute the rewards for all the currency_id distributed in the fees (which would require yet another map).

The collect extrinsic has been added on the rewards-pallet in this PR. The extrinsic added allows for the account to withdraw at a given vault_id and reward_currency_id.
Although it is not exactly the same functionality stated in the issue, it allows for the proper collection of rewards. I believe that if we don't require an extrinsic that allows to collect all the vault's staked by a given account at the same time, we could close this issue.

Closing this ticket now that https://github.com/pendulum-chain/spacewalk/pull/415 is merged.


Removed obsolete api/mocks/mocks.go

Motivation
The file is not needed

bors merge

bors merge

bors merge


Windows trust command suggestion includes newline and cruft

Description
When running nitro trust in WSL2, this exact output is printed as shown:
Users on WSL will need to open an elevated (run as administrator) Command Prompt or terminal on Windows and run the following command:
certutil -addstore -f "Root" \\wsl$\Ubuntu-20.04\home\username\.nitro\nitro.crt\nNitro certificates are now trusted 🔒

If one literally copies the following as instructed, disappointment will follow:
certutil -addstore -f "Root" \\wsl$\Ubuntu-20.04\home\username\.nitro\nitro.crt\nNitro certificates are now trusted 🔒

But the line should obviously read:
certutil -addstore -f "Root" \\wsl$\Ubuntu-20.04\home\username\.nitro\nitro.crt

Steps to reproduce

Make sure Nitro is running in Windows and open an Ubuntu shell.
Run the nitro trust command.
Observe output as stated above.
Run corrected certutil command before line break and rejoice, but with hesitation.

Additional info

Nitro version: 2.0.5
Docker Desktop 3.2.1, Docker API 1.41
Ubuntu 20.04 WSL2
Windows 10 Pro 10.0.19041

Possible regression from: https://github.com/craftcms/nitro/issues/257

Will this also fix the same message displayed when running nitro init using WSL? Assuming init process also runs nitro trust at the completion stage?

@jamiematrix yes that is correct. The init command calls the trust command right after so fixing it there will resolve both.


Set paid plans as default

Free plans have some restrictions, we should use paid plans to enable all the capabilities.

released in https://github.com/terraform-ibm-modules/terraform-ibm-watsonx-saas-da/releases/tag/v0.2.0


enhance data export scripts

[ ] revise dwellings.py script to fit members.py script
[ ] write unit tests for export dwellings.py
[ ] open pull request on s&co repository

From Rebecca: There are necessary code updates to revise the data export scripts and then export and validate the datasets. We could export and publish new datasets with existing code, but it wouldn't include all the updates they've been working on for dates + addresses which is needed for the geographic analysis.

As a note, here's the quick script I ran to export the 'dwellings' data from a running mep-django installation. I will write this as a PR to mep-django as an export_dwellings.py command.
# export_dwellings.py

# allow django models in use
import os,django,datetime as dt
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "mep.settings")
os.environ["DJANGO_ALLOW_ASYNC_UNSAFE"] = "true"
django.setup()
from mep.people.models import Person
from mep.common.utils import absolutize_url

def export_dwellings():
    old=[]
    for person in Person.objects.all():
        print(person)
        for account in person.account_set.all():
            for addr in account.address_set.all():
                loc = addr.location

                odx=dict(
                    # Member
                    member_uri=absolutize_url(person.get_absolute_url()),

                    # IDs
                    person_id=person.id,
                    account_id=account.id,
                    address_id=addr.id,
                    location_id=loc.id,

                    # Address data
                    start_date = addr.start_date,
                    end_date = addr.end_date,
                    start_date_precision = addr.start_date_precision,
                    end_date_precision = addr.end_date_precision,
                    care_of_person_id = addr.care_of_person_id,

                    # Location data
                    street_address=loc.street_address,
                    city=loc.city,
                    postal_code=loc.postal_code,
                    latitude=loc.latitude,
                    longitude=loc.longitude,
                    country_id=loc.country_id,
                    arrrondissement=loc.arrondissement(),

                )
                old.append(odx)
    now=dt.datetime.now()
    ofn=f'dwellings.{now.year:02}-{now.month:02}-{now.day:02}.pkl'
    import pickle
    with open(ofn,'wb') as of:
        pickle.dump(old, of)

if __name__=='__main__': export_dwellings()

Note: The above code needs to be adapted on the model of export_members.py

@quadrismegistus @jkotin some comments on the address data export enhancements:
Here's the relevant GitHub issue in the mep-django codebase:
https://github.com/Princeton-CDH/mep-django/issues/612
There isn't much detail there, just a suggestion of how we might structure it (which looks similar enough to what you've done here).
I don't think we should introduce a new term ("dwellings"); I strongly recommend we continue to call these addresses for consistency with previous versions of the datasets. My plan is for exported address data to be packaged with the members data for a new version of the members dataset. We'll have to update the datapackage validation and dataset readme to document the fields in the addresses export and how the two files relate. We'll also need to clearly document this in the dataset change log.  There will be redundancy with the main member export data, but I think we should keep that for backwards compatibility.
I suggest the new export filename should be member_addresses.csv or possibly account_addresses.csv.  We should generate both csv and json formats, and our existing export script code should make that easy.  I think the easiest way to implement is a new manage command that extends our existing BaseExport class.  It might be nice to create a convenience omnibus export manage command that uses call_command to run all the exports.
I still think it would be incredibly valuable to have a GeoJSON export of this data, because that would make the data usable with so many tools; that would require additional work, but there must be python packages that would help with this. (Maybe something in geodjango would be useful.).
field-specific comments:

do not include any numeric database ids
technically addresses are associated with accounts, not members; we should member uris the same way that they are exported in the events dataset, and we should consider including member names and sort names as well (as we do there) so that the file can be used to some extent on its own
start and end dates should each be exported as a single field using partial_start_date and partial_end_date, which will compile the date information and precision information into the ISO format we're using across all the data exports

Just a brief note: this all sounds good to me.  I agree about "addresses" over "dwellings," and having GeoJSON exports.  I'm happy to write the readme files once the specific formats are determined. I can already picture the enhanced books dataset (with author nationalities and genders) but not the enhanced members with the addresses. What will the columns look like to show addresses at particular times?

I'm going to close this as a duplicate, since the work is being tracked on https://github.com/Princeton-CDH/mep-django/issues/791 and https://github.com/Princeton-CDH/mep-django/issues/792


Handling covariate with different granularity

Thank you team for bringing us this awesome library and I have found this is very useful for my problem.
However, there are some covariates that has higher/lower granularity than the target series. For those with lower granularity, I can do aggregation to avoid it. However for those with higher granularity, I am not sure what would be the best approach. I will try a naive approach (equal-splitting) v.s. omitting this covariate.  But it would be great to know if the model can be extended to handle mixed-frequency time series.

Hello @davidlkl,
I'm glad you like gluon-ts!
Sadly, I think this problem is out of scope for gluon-ts. If we were to add this, then I think we would end up with some sort of "smart" averaging and then this could be just done as well as a data preprocessing step.
Hope that answers your question.


Soe willows

New Divine Key that is named the same as the other dkey but the other one sucks so much it doesn't deserve the acronym. Also the new G4 Ice stigs

Thanks for the PRs!


Changes done for adding support for "ø" for DK idn

When ever I try to create Uri object for url string "http://www.fitnessø.dk/", it throws an exception with message "Host "www.fitnessø.dk" is not valid or is not accepted by...". And when debugged the source, I came to know that this error is because it is not validated by HostName validator in Uri::isValidDnsHostname().

Travis failure is due to https://github.com/zendframework/zend-servicemanager/issues/182, not this PR.

Are there any other characters that should be allowed in a DK url?

@akrabat , I am not sure for the other characters, I just came across the use case for this character and hence created this PR for the same.
Thanks,
Krish Damani

@akrabat , I have added two more characters and updated the PR,
Reference for allowed characters in dk domain names https://www.dk-hostmaster.dk/sites/default/files/Characters allowed in.pdf
Thanks,
Krish Damani