SyntaxError: Unexpected reserved word when importing elements from example project

When importing elements from figmagic example project we get the following error message:

Here is our figma json attached.
Error message is really not explicit. maybe this issue is about producing a better error message. plz advice
Using the master branch and node version 12.14

Interesting. I will see how I can troubleshoot this. I'm kind of putting down version 3 for now, as I am finishing the fairly big migration to Typescript coming in version 4.
Note that the error itself is not output through Figmagic. "Unexpected reserved word" makes me thing maybe your component(s) has a named that is reserved in JS? Weird, but who knows.
Keeping this open, and I'll see what this is about.

I see you changed title. Is this with figmagic-example? (https://github.com/mikaelvesavuori/figmagic-example)

With a fresh figmagic-exampleI just verified basic functionality by:

Fresh pull
Install dependencies
Rename env to .env and set your URL and token; you can copy a Figmagic template at https://www.figma.com/community/file/821094451476848226/Figmagic-%E2%80%94-Design-System-for-Tokens
Create .figmagicrc and set syncElements: true
Run npm run figmagic

No errors. Can you specify in more detail your current setup and how much you are doing "from scratch"?

Hi @mikaelvesavuori, I work with @anback.
I just tried:

Local install of<EMAIL_ADDRESS>(on node v13.12.0)
.env with FIGMA_TOKEN, FIGMA_URL
The default .figmagicrc from README but with syncElements and syncGraphics being true.
Running with node --experimental-modules ./node_modules/figmagic/index.mjs --syncGraphics --syncElements

Design tokens are created just fine, but I get SyntaxError: Unexpected reserved word and no elements.
Output:
$ node --experimental-modules ./node_modules/figmagic/index.mjs --syncGraphics --syncElements

Attempting to fetch data from Figma API...

Writing Figma base file...

Writing design tokens...

Attempting to parse elements...

|||||
|||||
|||||
|||||
|||||
|||||
|||||
|||||
|||||
* Form > Form
|||||
[
  {
    id: '3010:3',
    name: 'empty',
    visible: false,
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 274, y: 626, width: 78, height: 15 },
    constraints: { vertical: 'TOP', horizontal: 'LEFT' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'asdf',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue',
      fontWeight: 400,
      paragraphSpacing: 1,
      fontSize: 12,
      textAlignHorizontal: 'LEFT',
      textAlignVertical: 'CENTER',
      letterSpacing: 0,
      lineHeightPx: 14.0625,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {},
    styles: { text: '2875:20' }
  },
  {
    id: '3009:111',
    name: 'Normal',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 581, width: 32, height: 32 },
    preserveRatio: true,
    constraints: { vertical: 'CENTER', horizontal: 'CENTER' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 100,
    rectangleCornerRadii: [ 100, 100, 100, 100 ]
  }
]
MAIN_ELEMENT {
  id: '3009:111',
  name: 'Normal',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 581, width: 32, height: 32 },
  preserveRatio: true,
  constraints: { vertical: 'CENTER', horizontal: 'CENTER' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 1,
  strokeAlign: 'INSIDE',
  effects: [],
  cornerRadius: 100,
  rectangleCornerRadii: [ 100, 100, 100, 100 ]
}
* Normal > Normal
[
  {
    id: '3009:133',
    name: 'empty',
    visible: false,
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 274, y: 626, width: 78, height: 15 },
    constraints: { vertical: 'TOP', horizontal: 'LEFT' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'asdf',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue',
      fontWeight: 400,
      paragraphSpacing: 1,
      fontSize: 12,
      textAlignHorizontal: 'LEFT',
      textAlignVertical: 'CENTER',
      letterSpacing: 0,
      lineHeightPx: 14.0625,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {},
    styles: { text: '2875:20' }
  },
  {
    id: '3009:116',
    name: ':checked',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 581, width: 32, height: 32 },
    preserveRatio: true,
    constraints: { vertical: 'CENTER', horizontal: 'CENTER' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 100,
    rectangleCornerRadii: [ 100, 100, 100, 100 ]
  }
]
MAIN_ELEMENT {
  id: '3009:116',
  name: ':checked',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 581, width: 32, height: 32 },
  preserveRatio: true,
  constraints: { vertical: 'CENTER', horizontal: 'CENTER' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 1,
  strokeAlign: 'INSIDE',
  effects: [],
  cornerRadius: 100,
  rectangleCornerRadii: [ 100, 100, 100, 100 ]
}
* :checked > :checked
|||||
* Slider > Slider
|||||
* HR > HR
|||||
|||||
[
  {
    id: '2874:71',
    name: ':invalid',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 211, width: 320, height: 48 },
    constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 2,
    strokeAlign: 'INSIDE',
    effects: [ [Object] ],
    styles: { effect: '2657:133' },
    cornerRadius: 4,
    rectangleCornerRadii: [ 4, 4, 4, 4 ]
  },
  {
    id: '3010:4',
    name: ':invalid',
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: {
      x:<PHONE_NUMBER>984375,
      y: 211,
      width:<PHONE_NUMBER>03125,
      height: 48
    },
    constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'Sample input',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue',
      fontWeight: 400,
      paragraphSpacing: 1,
      fontSize: 16,
      textAlignHorizontal: 'LEFT',
      textAlignVertical: 'CENTER',
      letterSpacing: 0,
      lineHeightPx: 18.75,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {},
    styles: { text: '2743:5' }
  }
]
MAIN_ELEMENT {
  id: '2874:71',
  name: ':invalid',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 211, width: 320, height: 48 },
  constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 2,
  strokeAlign: 'INSIDE',
  effects: [
    {
      type: 'DROP_SHADOW',
      visible: true,
      color: [Object],
      blendMode: 'NORMAL',
      offset: [Object],
      radius: 5
    }
  ],
  styles: { effect: '2657:133' },
  cornerRadius: 4,
  rectangleCornerRadii: [ 4, 4, 4, 4 ]
}
* :invalid > :invalid
[
  {
    id: '3010:20',
    name: ':placeholder',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 211, width: 320, height: 48 },
    constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 2,
    strokeAlign: 'INSIDE',
    effects: [ [Object] ],
    styles: { effect: '2657:133' },
    cornerRadius: 4,
    rectangleCornerRadii: [ 4, 4, 4, 4 ]
  },
  {
    id: '3010:18',
    name: ':placeholder',
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: {
      x:<PHONE_NUMBER>808594,
      y: 211,
      width:<PHONE_NUMBER>03125,
      height: 48
    },
    constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'Placeholder text',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue',
      fontWeight: 400,
      paragraphSpacing: 1,
      fontSize: 16,
      textAlignHorizontal: 'LEFT',
      textAlignVertical: 'CENTER',
      letterSpacing: 0,
      lineHeightPx: 18.75,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {},
    styles: { text: '2743:5' }
  }
]
MAIN_ELEMENT {
  id: '3010:20',
  name: ':placeholder',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 211, width: 320, height: 48 },
  constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 2,
  strokeAlign: 'INSIDE',
  effects: [
    {
      type: 'DROP_SHADOW',
      visible: true,
      color: [Object],
      blendMode: 'NORMAL',
      offset: [Object],
      radius: 5
    }
  ],
  styles: { effect: '2657:133' },
  cornerRadius: 4,
  rectangleCornerRadii: [ 4, 4, 4, 4 ]
}
* :placeholder > :placeholder
[
  {
    id: '2874:36',
    name: 'Normal',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 211, width: 320, height: 48 },
    constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 2,
    strokeAlign: 'INSIDE',
    effects: [ [Object] ],
    styles: { effect: '2657:133' },
    cornerRadius: 4,
    rectangleCornerRadii: [ 4, 4, 4, 4 ]
  },
  {
    id: '2874:38',
    name: 'Normal',
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: {
      x:<PHONE_NUMBER>808594,
      y: 211,
      width:<PHONE_NUMBER>03125,
      height: 48
    },
    constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'Sample input',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue',
      fontWeight: 400,
      paragraphSpacing: 1,
      fontSize: 16,
      textAlignHorizontal: 'LEFT',
      textAlignVertical: 'CENTER',
      letterSpacing: 0,
      lineHeightPx: 18.75,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {},
    styles: { text: '2743:5' }
  }
]
MAIN_ELEMENT {
  id: '2874:36',
  name: 'Normal',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 211, width: 320, height: 48 },
  constraints: { vertical: 'CENTER', horizontal: 'LEFT_RIGHT' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 2,
  strokeAlign: 'INSIDE',
  effects: [
    {
      type: 'DROP_SHADOW',
      visible: true,
      color: [Object],
      blendMode: 'NORMAL',
      offset: [Object],
      radius: 5
    }
  ],
  styles: { effect: '2657:133' },
  cornerRadius: 4,
  rectangleCornerRadii: [ 4, 4, 4, 4 ]
}
* Normal > Normal
|||||
[
  {
    id: '3005:95',
    name: '_:hover',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3010:17',
    name: 'Error',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3005:96',
    name: 'Error',
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'Error',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue-Bold',
      fontWeight: 700,
      paragraphSpacing: 1,
      textCase: 'UPPER',
      fontSize: 16,
      textAlignHorizontal: 'CENTER',
      textAlignVertical: 'CENTER',
      letterSpacing: 0.8,
      lineHeightPx: 18.75,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {}
  }
]
MAIN_ELEMENT {
  id: '3010:17',
  name: 'Error',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
  constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 1,
  strokeAlign: 'INSIDE',
  effects: [],
  cornerRadius: 8,
  rectangleCornerRadii: [ 8, 8, 8, 8 ]
}
* Error > Error
[
  {
    id: '3005:98',
    name: '_:hover',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3010:16',
    name: 'Warning',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3005:99',
    name: 'Warning',
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'Warning',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue-Bold',
      fontWeight: 700,
      paragraphSpacing: 1,
      textCase: 'UPPER',
      fontSize: 16,
      textAlignHorizontal: 'CENTER',
      textAlignVertical: 'CENTER',
      letterSpacing: 0.8,
      lineHeightPx: 18.75,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {}
  }
]
MAIN_ELEMENT {
  id: '3010:16',
  name: 'Warning',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
  constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 1,
  strokeAlign: 'INSIDE',
  effects: [],
  cornerRadius: 8,
  rectangleCornerRadii: [ 8, 8, 8, 8 ]
}
* Warning > Warning
[
  {
    id: '3005:101',
    name: '_:hover',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    styles: { fill: '1:114' },
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3013:3',
    name: '_:disabled',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    styles: { fill: '1:102' },
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3010:15',
    name: 'Normal',
    type: 'RECTANGLE',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [ [Object] ],
    strokeWeight: 1,
    strokeAlign: 'INSIDE',
    effects: [],
    cornerRadius: 8,
    rectangleCornerRadii: [ 8, 8, 8, 8 ]
  },
  {
    id: '3005:102',
    name: 'Normal',
    type: 'TEXT',
    blendMode: 'PASS_THROUGH',
    absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
    constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
    fills: [ [Object] ],
    strokes: [],
    strokeWeight: 1,
    strokeAlign: 'OUTSIDE',
    effects: [],
    characters: 'Normal',
    style: {
      fontFamily: 'Helvetica Neue',
      fontPostScriptName: 'HelveticaNeue-Bold',
      fontWeight: 700,
      paragraphSpacing: 1,
      textCase: 'UPPER',
      fontSize: 16,
      textAlignHorizontal: 'CENTER',
      textAlignVertical: 'CENTER',
      letterSpacing: 0.8,
      lineHeightPx: 18.75,
      lineHeightPercent: 100,
      lineHeightUnit: 'INTRINSIC_%'
    },
    characterStyleOverrides: [],
    styleOverrideTable: {}
  }
]
MAIN_ELEMENT {
  id: '3010:15',
  name: 'Normal',
  type: 'RECTANGLE',
  blendMode: 'PASS_THROUGH',
  absoluteBoundingBox: { x: 284, y: 53, width: 320, height: 48 },
  constraints: { vertical: 'SCALE', horizontal: 'SCALE' },
  fills: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokes: [ { blendMode: 'NORMAL', type: 'SOLID', color: [Object] } ],
  strokeWeight: 1,
  strokeAlign: 'INSIDE',
  effects: [],
  cornerRadius: 8,
  rectangleCornerRadii: [ 8, 8, 8, 8 ]
}
* Normal > Normal
SyntaxError: Unexpected reserved word
Done in 2.87s.

@mikaelvesavuori I added a try/catch to figmagic/index.mjs and got this clue:
SyntaxError: Unexpected reserved word
  at Loader.moduleStrategy (internal/modules/esm/translators.js:81:18)
  at async link (internal/modules/esm/module_job.js:37:21)

Hey! I've done a small set of updates and pushed 3.0.24 now. However, none of that has any clear, 100% sure impact on the issue. The error comes from deeper inside Node, as previously stated. I did in fact get that same error on my first attempt, but it "magically" disappeared on the second run...?
The new version updates dependencies, removes the unnecessary console.log() messages and removes the --experimental-modules flag. Running locally in a freshly pulled Figmagic folder with requisite .env, I get full functionality using the Figma template, using Node 12.18.3, Node 13.14.0, and Node 14.8.0.
See if that improves your situation.

Hi @mikaelvesavuori, thanks for the rapid response & action!
Unfortunately, I get the same error with 3.0.24 as before.
I also, sometimes, get this error (had same with 3.0.23):
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/MY_PROJECT_PATH/tokens/colors.mjs' imported from /MY_PROJECT_PATH/node_modules/figmagic/bin/functions/process/parseTypographyStylingFromElement.mjs

…but I think they’re unrelated.

Too bad, but was worth a shot, if at least to update dependencies.
Tell me a bit about your current setup? Are you running within the Figmagic project, or are you using Figmagic as a dependency and running commands inside that project (as intended)?
One aspect I was reminded of now, since I am obviously not the typical consumer of Figmagic (rather, the producer), is that you need a folder of templates in your working directory (though, this does not seem to be your problem currently; but please verify).
There are a couple of things that are poor about the version 3 implementation of the code you point to.

When refactoring, I saw that a lot of async stuff can in fact just be standard sync, reducing asynchronous errors, like file writes.
The .mjs file ending is hard coded and not actually dynamic, though you can write tokens to other formats than MJS. The code in 3.0.24 being:

const PATH = isTest ? path.join('testdata', 'tokens') : `tokens`;
const _colors = await import(path.join(`${process.cwd()}`, `${PATH}`, `colors.mjs`));

Both these should already have been handled in the on-going (unreleased) v4 work.
Summary: Based on the above, it smells like either this is an async problem or that you've specified another file format, thus not resolving the path.

It sounds like it could be “folder of templates” problem, will check that out.
I created a blank project with yarn init and added Figmagic as dependency.

P.S. @mikaelvesavuori Figmagic is such a game changer for UI development. I tried to make a Twitter shoutout that Figma should pay you to work on this but couldn’t find you on Twitter...

Yeah, social media just ate so much time so I got rid of everything other than LinkedIn, years ago.  :) Much appreciated though, and I am always happy to hear from anyone using it. Feel free to hit me up if you are in the Göteborg area.
I am still continuing to see what I can possibly do in v3 before v4 drops, so keep nagging me if it ain't working.

Sounds like smart priorities! Will certainly ping you when I’m in Göteborg.
Anyway, I changed the paths in .figmagicrc:
"templates":{
  "templatePathReact":"./node_modules/figmagic/templates/react.jsx",
  "templatePathStyled":"./node_modules/figmagic/templates/styled.jsx",
  "templatePathStorybook":"./node_modules/figmagic/templates/story.js"
}

…but still getting the “Unexpected reserved word”.
Complete .figmagicrc:
{
  "debugMode":true,
  "fontUnit":"rem",
  "letterSpacingUnit":"em",
  "opacitiesUnit":"float",
  "outputTokenFormat":"mjs",
  "outputFileName":"figma.json",
  "outputFolderBaseFile":".figmagic",
  "outputFolderTokens":"tokens",
  "outputTokenDataType":"enum",
  "outputFolderElements":"elements",
  "outputFolderGraphics":"graphics",
  "outputFormatGraphics":"svg",
  "outputScaleGraphics":1,
  "recompileLocal":false,
  "remSize":16,
  "skipFileGeneration":{
    "skipReact":false,
    "skipStyled":false,
    "skipCss":false,
    "skipStorybook":false,
    "skipDescription":false,
    "forceUpdate":true
  },
  "spacingUnit":"rem",
  "syncElements":false,
  "syncGraphics":false,
  "templates":{
    "templatePathReact":"./node_modules/figmagic/templates/react.jsx",
    "templatePathStyled":"./node_modules/figmagic/templates/styled.jsx",
    "templatePathStorybook":"./node_modules/figmagic/templates/story.js"
  },
  "usePostscriptFontNames":false
}

Will continue hunting...

Progress! Using https://github.com/mikaelvesavuori/figmagic-example instead of my "from scratch" project manages to export Elements. Now trying to figure out what was missing in my project.

Awesome! If you find what the diff was, I will be happy to improve docs for version 4.

...and "solved"! Copying .figmagicrc from https://github.com/mikaelvesavuori/figmagic-example instead of using the one in the README https://github.com/mikaelvesavuori/figmagic#configuration-file-figmagicrc made it work.
Here’s the diff, I haven’t been able to figure out what caused the problem (it’s not usePostscriptFontNames):

This is my current, minimalistic yet working .figmagicrc:
{
  "outputTokenFormat": "mjs",
  "templates": {
    "templatePathReact": "./node_modules/figmagic/templates/react.jsx",
    "templatePathStyled": "./node_modules/figmagic/templates/styled.jsx",
    "templatePathStorybook": "./node_modules/figmagic/templates/story.js"
  }
}

I tried changing outputTokenFormat to js but I get build errors referring to mjs, so maybe it’s hardcoded somewhere. No biggie.

Cheers! Thanks for the update. Will have this in mind for v4. Closing since the issue is resolved.
Did a quick poke previously today on fixing the JS errors, but it's non-trivial enough that's I'll let that be fixed in the major release, instead of spending time fixing it now.


Facing error while installing in Ubuntu 20.04.1

Unable to install this package. npm install is giving the following error:make: *** [sha3.target.mk:107: Release/obj.target/sha3/src/addon.o] Error 1
make: Leaving directory '/home/pam/Documents/Tokens/node_modules/sha3/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 5.4.0-58-generic
gyp ERR! command "/usr/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pam/Documents/Tokens/node_modules/sha3
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pam/.npm/_logs/2021-01-02T04_16_46_133Z-debug.log
Any other tips for proper installation?

Seems this issue existed on Ubuntu 16.04 too. Apparently, there this thread solved on Stack Overflow.


Fixed typo

@googlebot I signed it!

Fixed in https://github.com/google/mediapipe/commit/a9b643e0f5978425d948050a2228398929733d05.


getBalances doc is not correct

hello
getBalances doc says "Get the locked and unlocked balances in a single request.", but it returns (total) balance, not locked balance
I think it can be changed to just "Get the balance and unlocked balance in a single request."

Only the RPC wallet supports getBalances(), which returns an array with the total balance and unlocked balance.
I ran a quick test to ensure it's returning an array as expected.

Ah I just realized what you were saying, with the documentation being incorrect.
Fixed in https://github.com/woodser/monero-ts/pull/194/commits/e84126a644cdf0d6720bd6bb6bc1d382cdd48eb7.
Thanks.


Fix: Async iterators defition

Hey,
#1337 everything is explained inside this issue.

Trying to fix/help with this definition file.

good catch

Is this fix in a release yet? It appears version 4.3.0 still has this issue


[KVCache] Support returning query positions

This PR adds a new function to PagedKVCache to return in-sequence positions for each location in a batch of sequences that is being forwarded. This function helps apply positional embeddings for language models that do not use Rotary positional embeddings.

cc @rickzx


Map issues: not centering on location during location search; results are over-truncated

[ ] Map no longer centers on location when performing a location search.
If you do the following the map does not center on the location when performing the location search:

Visit map search page.

Zoom in very far somewhere on the map (eg. cape town).

Ensure the "by location" option is selected. Type Berlin in the search box, click on the Berlin, Germany option in the dropdown menu.

The results appear, but the map will remain on cape town and not re-center over Berlin.

[ ] Over-truncated query results make searching for hosts in large cities a pain.
On a somewhat related note, query results are currently limited to 50, which is very low for large cities like Berlin, Istanbul, Prague, NYC, etc. Query results should be truncated to 200.

1 is a bug, but 2 is more of an improvement than a bugfix. Not sure if the query result truncation issue can be resolved by web team or requires backend intervention. Split into new issue if necessary.

done in my PR, closing :)


PL-31624 details on text and file secrets

https://harness.atlassian.net/browse/PL-31624
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/PL-31624

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65a1a677e7ac41439ac30c56--harness-developer.netlify.app


Feature Request: Scoreboard in frontend and/or via webhook

It would be nice to get the scoreboard after a match is finished via webhook or if you can see the scoreboard in the frontend.

Last time I checked the game server actually sends score board like data via its logging to the tmt... BUT only at the beginning of a round and not at the end or after a round. So the final (last) scoreboard that would be displayed is of the start of the last round :(
Example data:
04/04/2024 - 07:54:54.138 - JSON_BEGIN{
04/04/2024 - 07:54:54.138 - "name": "round_stats",
04/04/2024 - 07:54:54.138 - "round_number" : "3",
04/04/2024 - 07:54:54.138 - "score_t" : "0",
04/04/2024 - 07:54:54.138 - "score_ct" : "2",
04/04/2024 - 07:54:54.138 - "map" : "de_dust2",
04/04/2024 - 07:54:54.138 - "server" : "TMT2 Test Server",
04/04/2024 - 07:54:54.138 - "fields" : "             accountid,   team,  money,  kills, deaths,assists,    dmg,    hsp,    kdr,    adr,    mvp,     ef,     ud,     3k,     4k,     5k,clutchk, firstk,pistolk,sniperk, blindk,  bombk,firedmg,uniquek,  dinks,chickenk"
04/04/2024 - 07:54:54.138 - "players" : {
04/04/2024 - 07:54:54.138 - "player_0" : "            17041626,      3,   7600,      1,      0,      0,    100, 100.00,   0.00,     50,      1,      0,      0,      0,      0,      0,      1,      1,      1,      0,      0,      1,      0,      1,      0,      0"
04/04/2024 - 07:54:54.138 - "player_1" : "                   0,      0,    800,      0,      0,      0,      0,   0.00,   0.00,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0"
04/04/2024 - 07:54:54.138 - "player_2" : "                   0,      2,   2700,      0,      1,      0,      0,   0.00,   0.00,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0,      0"
04/04/2024 - 07:54:54.138 - }}JSON_END

For a correct scoreboard I'd have to implement all events on their own and keep track of them. Not impossible only a lot of work... But something that I've considered to be able to get some nice stats about teams and players across multiple matches.

I'm part of the organization of a lan, and we'd like to use tmt2, but having players' stats after the event as we had we the ebot would be very cool. We're ready to develop this feature, but we don't know where to start, how tmt2 communicates with the server and how we can extract the data.

Hey thanks for your interest. Technical documentation is lacking a bit so I'll just write down the parts to get you started:
Every log line from the cs2 server is sent via http to tmt and will end up in oneLogLine: https://github.com/JensForstmann/tmt2/blob/f5499b972d7522dd0f4086e34f04aed8f19e7053/backend/src/match.ts#L462
There every different type is matched with regex and sent with parameters to a handling function.
I'm not sure that the game server will sent damage or grenade events by default. Eventually increasing the log level is needed. That can happen in in the setup function https://github.com/JensForstmann/tmt2/blob/f5499b972d7522dd0f4086e34f04aed8f19e7053/backend/src/match.ts#L217
Currently there is only the log on, but in the comment there are already other commands to increase the amount of logs.
TMT2 currently saves all data as text files (json or jsonl). But I'm not sure if that's the right direction when considerung saving stats. Maybe it's time to add sqlite to the project. It would make.
Tell me what you think about it. Do you need anything else to get started?

We made a fork with our own issues, and we'll work on it.
Sqlite is a good and easy way to store this data, it's fine for us.
We'll also add a switch in the admin panel to enable/disable the ability for anyone to create a private match, as everybody will be able to see the tmt2 panel during our event. The "Create match" tab will be replace by the scoreboard if disabled. Finally, we would like to add a french localization, as we are a french organization.
If we need you help at some point, I'll ask you here, thank you very much for your help !

Sounds great. If you plan to get your changes merged back into this project (I'd appreciate it), then please split it up into smaller PRs (instead of one big chunk).
Localization:
The frontend is prepared for this: https://github.com/JensForstmann/tmt2/blob/f5499b972d7522dd0f4086e34f04aed8f19e7053/frontend/src/utils/locale.ts
But the locale files are empty.
The messages sent from the backend to the game server are all (hard coded) in english currently, not system is in place there.
If you come up with any ideas (both frontend and backend) to better handle localization, then let me know. I never really did any i18n in projects, so experience from my side is low.

Hey @JensForstmann !
I'm currently working with @Ecnama on this, and we're having an issue where the auto-generated files swagger.json and routes.ts. When we run the app, they get generated in a different format than yours (with spaces instead of tabs, arrays formatted differently in the json, etc.). Is this due to a difference in user config ? :thinking:  I've never used tsoa before. If not, maybe we could add them to the .gitignore ?
Thanks !


Wrong energy for benzene

Running the calculation below
import pyscf

neutral = pyscf.M(
    atom = '''
C          0.00000        0.00000        1.39495
C          0.00000        1.20806        0.69748
C          0.00000        1.20806       -0.69748
C          0.00000        0.00000       -1.39495
C          0.00000       -1.20806       -0.69748
C          0.00000       -1.20806        0.69748
H          0.00000        0.00000        2.47753
H          0.00000        2.14560        1.23877
H          0.00000        2.14560       -1.23877
H          0.00000        0.00000       -2.47753
H          0.00000       -2.14560       -1.23877
H          0.00000       -2.14560        1.23877
''',
    basis = 'aug-pc-0',
    symmetry = True,
    verbose = 4,
    charge = 0,
    spin = 0
)

mf_neutral = neutral.KS().apply(pyscf.scf.addons.remove_linear_dep_)
mf_neutral.grids.prune = None
mf_neutral.grids.atom_grid = (100, 590)
mf_neutral.xc = 'hyb_gga_xc_bhandh'
mf_neutral.kernel()

anion = pyscf.M(
    atom = '''
C          0.00000        0.00000        1.39495
C          0.00000        1.20806        0.69748
C          0.00000        1.20806       -0.69748
C          0.00000        0.00000       -1.39495
C          0.00000       -1.20806       -0.69748
C          0.00000       -1.20806        0.69748
H          0.00000        0.00000        2.47753
H          0.00000        2.14560        1.23877
H          0.00000        2.14560       -1.23877
H          0.00000        0.00000       -2.47753
H          0.00000       -2.14560       -1.23877
H          0.00000       -2.14560        1.23877
''',
    basis = 'aug-pc-0',
    symmetry = True,
    verbose = 4,
    charge = -1,
    spin = 1
)

mf_anion = anion.KS().apply(pyscf.scf.addons.remove_linear_dep_)
mf_anion.grids.prune = None
mf_anion.grids.atom_grid = (100, 590)
mf_anion.xc = 'hyb_gga_xc_bhandh'
mf_anion.kernel()

gives me converged SCF energies -229.871832298617 and -229.835867695121 for the neutral molecule and the anion with PySCF 1.7.6.
Running the calculation with a snapshot of PySCF master branch gave poor convergence for the neutral and energies 10x and 20x too low for the neutral molecule and anion, respectively.... I am trying to recompile and see if that solves the issue

I recompiled the current master branch, and the aug-pc-0 calculations ran fine.
However, already in aug-pc-1 the calculation goes haywire:
init E= -231.101033245861
HOMO (B3g) = -7.7395871345262  LUMO (B3u) = -5.74268052711217
cycle= 1 E= -217163901.058065  delta_E= -2.17e+08  |g|= 2.46e+07  |ddm|= 1.57e+06
HOMO (B2u) = -852700.354299115  LUMO (B1u) = -852697.097562663
cycle= 2 E= -574631980.624751  delta_E= -3.57e+08  |g|= 1.84e+07  |ddm|= 1.37e+05
HOMO (B1u) = -427697.404388843  LUMO (B3g) = -417271.030480679
cycle= 3 E= -645385319.509049  delta_E= -7.08e+07  |g|= 1.93e+07  |ddm|= 6.91e+04
HOMO (B1u) = -256502.426523699  LUMO (B1u) = -173265.071839651
cycle= 4 E= -662487756.619415  delta_E= -1.71e+07  |g|= 2.08e+07  |ddm|= 5.86e+04
HOMO (B1u) = -239952.244014946  LUMO (B1u) = -174924.866586751

This is quite odd since the usual suspect for non-variational results would be an ill-conditioned basis, which is not the case here.

pc-2 also leads to wildly wrong results
init E= -231.629453403121
HOMO (B3u) = -0.43027997750106  LUMO (B3g) = -0.382114431715916
cycle= 1 E= -69676.0076400298  delta_E= -6.94e+04  |g|= 2.6e+04  |ddm|= 1.02e+04
HOMO (Ag) = -6555.91778160011  LUMO (B3g) = -6555.81467048198
cycle= 2 E= -384157.747689078  delta_E= -3.14e+05  |g|= 6.86e+04  |ddm|= 1.65e+04
HOMO (Ag) = -5824.34518008497  LUMO (B3g) = -5790.00400330834

and the calculations also fail at the Hartree-Fock level of theory

Turning off symmetry has no effect

Reduced test case
import pyscf

mol = pyscf.M(
    atom = '''
C          0.00000        0.00000        1.39495
C          0.00000        1.20806        0.69748
C          0.00000        1.20806       -0.69748
C          0.00000        0.00000       -1.39495
C          0.00000       -1.20806       -0.69748
C          0.00000       -1.20806        0.69748
H          0.00000        0.00000        2.47753
H          0.00000        2.14560        1.23877
H          0.00000        2.14560       -1.23877
H          0.00000        0.00000       -2.47753
H          0.00000       -2.14560       -1.23877
H          0.00000       -2.14560        1.23877
''',
    basis = 'pc-2',
    symmetry = True,
    verbose = 4
)

mf = mol.HF()
mf.kernel()

result
init E= -232.393799745241
HOMO (B3u) = -0.430682215804206  LUMO (B3g) = -0.35307779954462
cycle= 1 E= -78012.7949510677  delta_E= -7.78e+04  |g|= 2.5e+04  |ddm|= 1.02e+04
HOMO (Ag) = -6773.99600039286  LUMO (B3g) = -6773.89456486638
cycle= 2 E= -423067.480828103  delta_E= -3.45e+05  |g|= 6.63e+04  |ddm|= 1.7e+04
HOMO (Ag) = -6183.13637331776  LUMO (B3g) = -6135.99357445351
cycle= 3 E= -486677.0033498  delta_E= -6.36e+04  |g|= 4.7e+04  |ddm|= 1.74e+03
HOMO (Ag) = -6290.19474179859  LUMO (B2g) = -6242.05499997989
cycle= 4 E= -527709.459517495  delta_E= -4.1e+04  |g|= 1.31e+04  |ddm|= 1.58e+03
HOMO (B1u) = -7098.19399704283  LUMO (Ag) = -7023.76484545713
cycle= 5 E= -531649.380799805  delta_E= -3.94e+03  |g|= 3.41e+03  |ddm|=  940
HOMO (Ag) = -7354.02765485832  LUMO (B1u) = -7240.24478604687

This is with qcint; libcint gives the correct result

Possibly related to #953 ?
See eg. comment by @btglau in https://github.com/pyscf/pyscf/issues/953#issuecomment-849057359_

It's a bug in the integral library libcint 4.1.* - 4.4.2 due to a divide-by-0 bug. It is fixed in the new release 4.4.3

Confirmed, issue is fixed! Thanks!

Issue still prevails in PySCF 1.7.6 and qcint 4.4.3
init E= -232.393799745242
HOMO (B3u) = -0.430682215804213  LUMO (B3g) = -0.35307779954455
cycle= 1 E= -78012.7949510526  delta_E= -7.78e+04  |g|= 2.5e+04  |ddm|= 1.02e+04
HOMO (Ag) = -6773.99600039274  LUMO (B3g) = -6773.89456486676
cycle= 2 E= -423067.480828  delta_E= -3.45e+05  |g|= 6.63e+04  |ddm|= 1.7e+04
HOMO (Ag) = -6183.13637331704  LUMO (B3g) = -6135.99357445377

https://github.com/sunqm/libcint/commit/914caf2278bda61d5fbcecadbe1bccf5aa86ca9f
This looks like something that could cause such results. Checking

No, there is still definitely an issue with qcint 4.4.4 as well:
init E= -232.393799745242
HOMO (B3u) = -0.430682215804207  LUMO (B3g) = -0.35307779954462
cycle= 1 E= -78012.7949510903  delta_E= -7.78e+04  |g|= 2.5e+04  |ddm|= 1.02e+04
HOMO (Ag) = -6773.99600039593  LUMO (B3g) = -6773.89456486988
cycle= 2 E= -423067.480828085  delta_E= -3.45e+05  |g|= 6.63e+04  |ddm|= 1.7e+04
HOMO (Ag) = -6183.13637331985  LUMO (B3g) = -6135.99357445604
cycle= 3 E= -486677.003349847  delta_E= -6.36e+04  |g|= 4.7e+04  |ddm|= 1.74e+03
HOMO (Ag) = -6290.19474179985  LUMO (B2g) = -6242.05499998264

No, there is still definitely an issue with qcint 4.4.4 as well:
init E= -232.393799745242
HOMO (B3u) = -0.430682215804207  LUMO (B3g) = -0.35307779954462
cycle= 1 E= -78012.7949510903  delta_E= -7.78e+04  |g|= 2.5e+04  |ddm|= 1.02e+04
HOMO (Ag) = -6773.99600039593  LUMO (B3g) = -6773.89456486988
cycle= 2 E= -423067.480828085  delta_E= -3.45e+05  |g|= 6.63e+04  |ddm|= 1.7e+04
HOMO (Ag) = -6183.13637331985  LUMO (B3g) = -6135.99357445604
cycle= 3 E= -486677.003349847  delta_E= -6.36e+04  |g|= 4.7e+04  |ddm|= 1.74e+03
HOMO (Ag) = -6290.19474179985  LUMO (B2g) = -6242.05499998264

It looks like the output with old versions of libcint. In certain version ofl libcint (4.1 - 4.4.2), a bug in solving linear equation causes the error. However, qcint employs polynomial fittings for the relevant integrals so the error might be ~1e-9 but should not be as large as your test. Can you verify again the path and environment settings of your calculation?

Thanks @susilehtola @bogdanoff  for the detailed runtime environment. Error reproduced. Bug is fixed in qcint v4.4.5

Yes, now I get the same output for qcint as well
init E= -232.398192094587
HOMO (B1g) = -0.251465581587135  LUMO (Au) = 0.0342446621646966
cycle= 1 E= -230.714606240808  delta_E= 1.68  |g|= 0.402  |ddm|= 2.61
HOMO (B1g) = -0.35581581265675  LUMO (Au) = 0.102439491293234
cycle= 2 E= -230.773257120757  delta_E= -0.0587  |g|= 0.106  |ddm|= 0.42
HOMO (B1g) = -0.329722878863841  LUMO (Ag) = 0.109946711454335
cycle= 3 E= -230.777656226318  delta_E= -0.0044  |g|= 0.0267  |ddm|= 0.165
HOMO (B1g) = -0.338380098133097  LUMO (Ag) = 0.108836511682186
cycle= 4 E= -230.777865105423  delta_E= -0.000209  |g|= 0.00638  |ddm|= 0.0223
HOMO (B1g) = -0.337138770908494  LUMO (Ag) = 0.108880229573052
cycle= 5 E= -230.777878224334  delta_E= -1.31e-05  |g|= 0.00101  |ddm|= 0.00604
HOMO (B1g) = -0.336986073316625  LUMO (Ag) = 0.108868838597238
cycle= 6 E= -230.777879032948  delta_E= -8.09e-07  |g|= 0.000259  |ddm|= 0.00197
HOMO (B1g) = -0.336978193903298  LUMO (Ag) = 0.108860235905301
cycle= 7 E= -230.777879085415  delta_E= -5.25e-08  |g|= 2.14e-05  |ddm|= 0.000569
HOMO (B1g) = -0.336977664271867  LUMO (Ag) = 0.108859153860879
cycle= 8 E= -230.777879085681  delta_E= -2.66e-10  |g|= 2.48e-06  |ddm|= 5.47e-05
HOMO (B1g) = -0.336977369785647  LUMO (Ag) = 0.108859245616684
Extra cycle  E= -230.777879085684  delta_E= -3.35e-12  |g|= 7.76e-07  |ddm|= 7.24e-06
converged SCF energy = -230.777879085684


Ensure function signatures are consistent

This means that syntax is consistent with RDD, and that our ops use currying in a consistent manner, only where it benefits type inference.
This closes #24.

Codecov Report

Merging #25 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #25   +/-   ##
=======================================
  Coverage   94.96%   94.96%
=======================================
  Files          15       15
  Lines         139      139
  Branches        3        3
=======================================
  Hits          132      132
  Misses          7        7

Impacted Files
Coverage Δ

...heide/kontextfrei/stream/StreamBaseFunctions.scala
95% <ø> (ø)
:white_check_mark:

...elwestheide/kontextfrei/rdd/RDDBaseFunctions.scala
100% <ø> (ø)
:white_check_mark:

...elwestheide/kontextfrei/rdd/RDDPairFunctions.scala
100% <100%> (ø)
:white_check_mark:

...anielwestheide/kontextfrei/syntax/BaseSyntax.scala
100% <100%> (ø)
:white_check_mark:

...anielwestheide/kontextfrei/syntax/PairSyntax.scala
100% <100%> (ø)
:white_check_mark:

...heide/kontextfrei/stream/StreamPairFunctions.scala
100% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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


Advertise latest version

First of all thanks for writing the library, I used version 7.0.0 and it worked like a charm.
Could you include version 9.0.3 of this lib on the Readme? I tried to include version 9.0.1 in my maven project but it failed with an error while downloading dependencies. You can reproduce this with a simple maven project. The error is no longer present in version 9.0.3 but I did not realize it was released.
FYI the error was introduced with 7.0.1 and present up until 9.0.1:
[ERROR] Failed to execute goal on project patrick: Could not resolve dependencies for project com.example:exav:jar:0.0.1-SNAPSHOT
[ERROR] dependency: org.slf4j:slf4j-parent:jar:1.7.36 (compile)
[ERROR] 	Could not find artifact org.slf4j:slf4j-parent:jar:1.7.36 in central (https://repo.maven.apache.org/maven2)

Btw in version 9.0.3 I get a ton of logs (without any configuration) on INFO and some "Conditional Matched::" on stdout from here. Can I suggest printing the logs on DEBUG level instead of on INFO at least for most things like "Data Lookup Detected!", because this library is quite useful for scripts (my use-case) where configuring the debug level for a library is a hassle.
There are some errors with files that parsed fine with version 7.0.0 for example I see Error Parsing HCL...Error Parsing Numerical Value in HCL Attribute and Error Processing Tuple from source not a List (no errors in terraform validate or terraform plan on my project).

Regarding logs: yes we can fix that
Regarding your parser errors. 7.0.0 did not interpret tuples and ignored them. This is newer parser functionality. If you can provide samples on the parse errors listed we can get some unit tests in and see why it is occuring.

Also the read me has been updated for 9.0.4 thank you!


matchmaking question

Is this client still using Unity's matchmaking system or does the facilitator handle the matchmaking?
Does this still use up Unity's CCU limit?

By default it uses Unity's matchmaking but it's pretty easy to replace it
with something like steam lobbies.
If you leave "Use Matchmaking" enabled each host will use two ccu, one for
the host and one so that the match is not full. Once you 'go live' there is
no ccu limit though. You are only charged based on bandwidth over the
relays. As long you uncheck "Use Relays" no clients will actually connect
via relays so you should hardly use any bandwidth at all even though you
will technically be using two ccu for every game hosted.
If you uncheck "Use Matchmaking" and "Use Relays" then unity matchmaking
won't be used and no ccu will be taken up, but also..there will be no
matchmaking so you won't be able to connect until you replace it with
something like steam lobbies or any other matchmaking solution. The
Facilitator does not handle matchmaking itself, it just helps negotiate
ports for punchthrough.
Hopefully that answers your questions. Let me know if I've left you more
confused than you started :)
Cheers,
Zeb
On Thu, Oct 27, 2016 at 5:14 PM, n00ben<EMAIL_ADDRESS>wrote:

Is this client still using Unity's matchmaking system or does the
facilitator handle the matchmaking?
Does this still use up Unity's CCU limit?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/noblewhale/NATPunchthroughClient/issues/3, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABJ8srYrORa12fT9aG3FXRYb_M1iKGcvks5q4RQ9gaJpZM4Ki1UH
.

Thanks for the explanation.
One more question:
since we have NAT punchthrough, wouldn't it be possible to directly connect to the game using Unity's Network.Connect using the IP directly, assuming I don't want a Lobby system. Would this still require anything on Unity's part that would still use the CCU/bandwidth?

wouldn't it be possible to directly connect to the game using Unity's
Network.Connect using the IP directly

The connections made via the plugin are direct (as long as relays are
disabled). The ccu usage is due to listing the game for matchmaking. The
only way to avoid it is to replace unity's matchmaking with some other way
of passing around the host's connection info. Otherwise how do the client's
get the IP of the host to connect to? If you can get access to the
steamworks api that's really the way to go because it is free. Otherwise I
don't know of any other 100% free forever solution. Rolling your own
solution and hosting it on AWS would probably be the next cheapest (that's
more or less what I'm doing for my own game).
On Thu, Oct 27, 2016 at 8:49 PM, n00ben<EMAIL_ADDRESS>wrote:

Thanks for the explanation.
One more question:
since we have NAT punchthrough, wouldn't it be possible to directly
connect to the game using Unity's Network.Connect using the IP directly,
assuming I don't want a Lobby system. Would this still require anything on
Unity's part that would still use the CCU/bandwidth?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/noblewhale/NATPunchthroughClient/issues/3#issuecomment-256809417,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJ8sgn-OLqiS0xwTB2NeedCXn-PTEv8ks5q4UaRgaJpZM4Ki1UH
.


[Suggestion] Allow for regex substitution in model/texture path.

Hi,
I was writing a bunch of property file to change painting icons based on variant, and found the task to be needlessly repetitive.
Since CIT already supports regex-matching, I though it would be nice being able to use regex capture groups to automatically derive the texture path from the variant id. This way, everything could be compacted into a single file, which would look something like this:
type=item
items=painting

# Variant id is saved in capture group number 1
nbt.EntityTag.variant=regex:^mynamespace:(.+)$

# Value of group 1 is used as the filename
texture=regex:mynamespace:item/$1.png

Being able to merge everything into a single file could also offer an extra layer of optimizations. (Probably related to #230)
When stress-testing, I noticed that increasing the amount of .properties files for painting items could cause the framerate to drop quite fast.
When looking at an inventory-full of paintings, I'd loose 40fps for every 100 property files I added. (Increasing the cache period does help a little, but still causes lag spikes whenever paintings are dragged and dropped.)
For reference, the mods Painting+ and Texel Paintings alone add 74 and 40 paintings respectively. So reaching that amount of variants in-game seems plausible to me.

If anything might as well use named capture groups as they are much more readable.
The problem here is that as of right now CITs are fully deteministic, meaning that from reading the properties file you could learn the entire tree of json models that need to be loaded by the game. Which is what I am doing to request that these json models be loaded in addition to vanilla jsons.
Introducing something that creates the model path based on an ingame dynamic property turns this process non-determined. Like, what if some player ingame names an item something that the game isnt expecting, or modifies the nbt to be a new value that the properties is not taking into account since it is reading the value of the wild card it asks for. The cit conditions already passed, is it supposed to just throw a missing model on the item and call it a day?
This also means that the game would not be able to know right away(during resource loading) what json files it needs to load for the properties file.
I do however agree that this could be insanely powerfull for pack makers, and it would allow for a lot of cool stuff beyond the issue you described. And it would definitely reduce drastically the amount of cits required in large resourcepacks. The only question is how to implement it cleanly.
This is good timing as before I was taking my break from CIT Resewn I was working on recreating the model structure that the mod uses to be more usable. This is something I need to look at before I continue with that because it'd be hard to modify after.

As for the lag spikes when a high cache is used, that is exactly why the cache is there, without it, those lag spikes would be the case for every frame the game tries to render. It's just a mitigation for when things stay the same across frames(items arent being created and destroyed or modified so no need to recheck all of the conditions)

Named capture groups would be great as well. Functionally, they aren't much different from the numbered ones; those are just implicitely named.
Throwing a missing texture would sound like the expected behaviour to me. I've never manipulated models though, even outside of cit, so I have no idea what a missing model would look like.
Ignoring the file and falling back to a lower weight cit could be a handy option, but by no means necessary.

This also means that the game would not be able to know right away(during resource loading) what json files it needs to load for the properties file.

Here are a few ideas that came to mind :

A single separate file, which lists all files and folders with additional resources that need to be loaded, even if they are not mentioned in a cit property file.
Require pack makers to provide a search pattern in the cit files what need it, and load all resources which match this pattern. This would also allow them to provide resource patterns that are even more specific. For example I have a tendency to include dimensions in painting variants, so I can use that to exclude non-painting textures:

nbt.EntityTag.variant=regex:^mynamespace:(.+)$
texture=regex:mynamespace:item/$1.png
resources_to_be_loaded=pattern:mynamespace:item/*_?x?.png$

Automatically derive a search pattern from the model's regex, and load all resources that match this pattern. For example, mynamespace:item/$1.png would turn into mynamespace:item/*.png just by substituting all variables with *.
(Although in this case, it would be best that I move my painting textures into a subfolder or give them a constant prefix, so the resulting pattern can be more specific.)


Improve RichPayloadEventSource

RichPayloadEventSource is attempting several type casts.
Because of the if statements, there are several failed casts before finding the correct matching type.
https://github.com/Microsoft/ApplicationInsights-dotnet/blob/52e32b5695f35caf8548eb4bd256a408dbb9bb72/src/Microsoft.ApplicationInsights/Extensibility/Implementation/RichPayloadEventSource.cs#L41-L64
This can be eliminated with an internal interface returning private properties.

I closed the PR but I don't want to close this issue.
My PR broke the EventSource and exposed a gap in our tests that we don't currently catch.
Even if we don't attempt to improve RichPayloadEventSource we should try to improve test coverage.


Added "addGroup" feature to Group class

This way we can create groups of groups
what do you think?

Added other minor features + shim fix!


Fix convertDegreesToRadians method

There is currently a method called convertDegreesToRadians that lives in /lib/convertDegreesToRadians.js.
It is incomplete and needs to be fixed!
convertDegreesToRadians  should convert degrees to radians. If the parameter is not a number the method should throw an error.
Acceptance Criteria:

Running yarn test convertDegreesToRadians  results in tests passing.
You have written a skeleton method for someone else to work on.
You have written tests surrounding your skeleton method.
Running yarn lint does not print any errors to the console!
Optional: write one or two more tests surrounding the method you are solving to account for potential edge cases.

Please include the skeleton of a new method + an accompanying test for someone else to work on at the time of creating a pull request! A pull request will most likely be denied if it does not contain a skeleton method for someone else to work on! For more information, please read the Contributing Guide.
Thank you so much for your contribution!

@damjanh Hello, I would like to take this issue. Thanks

@jsjain007 All yours. You have appx 24 hours before we release it. Thanks for jumping on board!

Opening this back up.

Hello!
I've added a pull request for this issue :)

I merged it.


filetype php

When I open a file .php with the last onivim2.appimage on linux (7676fc5)
the filetype is not recognized.
When I try :set filetype=php It doesn't work any better.

We currently don't ship with any PHP syntax highlights, you can see the ones we do have over in https://github.com/onivim/oni2/tree/master/extensions.
A PR to add this should just be copying the extensions over from VSCode (#171, #636). That said, we are also looking at moving to tree-sitter powered syntax highlights as well, and PHP looks to have tree-sitter definitions, so we could use them in the future instead of the textmate ones.
We should probably raise a seperate issue to hook up set ft, since currently it doesn't do anything on the Oni side, where we'd rather send over a notification to Oni or something.

thanks

Why this enhancement was closed? I'm voting for PHP support, please!

I expect they installed it themselves locally!
I'll stick a PR in now for PHP, and if anyone else is wondering what the steps are it is as follows:

git clone VSCode
cp -r vscode/extensions/LANG ~/git/oni2/extensions/
Run Oni2 and just have a quick check with a test file.

Or, if its something more niche you think not worth commiting to the main repo, just copy to your extensions folder - https://onivim.github.io/docs/configuration/extensions#installing-extensions


Add WCRP columns to wcrp_watersheds.csv

Column shows which wcrp the watershed belongs to

Thanks - I'll merge once the migration has been applied and the table matches this new input.


Best way to allow multiple users access to S3 on a per-organization or per-group basis

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Which Category is your question related to?
Storage and Auth
Amplify CLI Version
4.13.4
What AWS Services are you utilizing?
Cognito, S3
Provide additional details e.g. code snippets
I'm currently building an application with multiple users divided across multiple (and indefinitely many) organizations. Users need to be able to access data related to their organization and none other. I am avoiding Coginto User Groups as they do not seem to be made for indefinetly many groups or organizations.
In my Graphql API this was pretty straight-forward to solve, using dynamic group auth with a custom groupClaim that I populate in a pretoken lambda.
When it comes to S3, however, I haven't quite figured out how to protect resources but allow all users of one organization to access these shared files. I have only found documentation on how to do so with static Cognito User Groups or general public/private/protected access on a per-user basis instead of a per-organization basis.
Any help or ideas?

@pafflu could you give some more details about your use case of using indefinitely many organizations? Its not clear to me why Cognito User Pools would not be a good choice here - you would still be able to add other groups with the right access levels later

@nikhname Thanks for the quick response!
It's a multi-tenant web-app for small enterprises, meaning users will register and belong to one company (and in larger companies sub-divided into different departments). I figured I'd rather manage this multi-tenant situation without User Groups, especially because they reach a hard limit at 500 per user pool as far as I know, and creating an entirely new pool for each company seems like a massive bother, too.
I currently use a pretoken lambda to stick the user's company id into their token that I then use when querying the API, and it works like a charm! It's just that I don't yet understand how to solve the same issue on the Storage side of things.
Any advice you can give me?

I am facing the same problem.

+1. Relevant comment about this that I posted in June in the @auth RFC: https://github.com/aws-amplify/amplify-cli/issues/1043#issuecomment-501462433

@pafflu @ricsirigu I had the same need as what you are describing (I believe) and solved it using S3 pre-signed URLs. You can read about my problem and solution here:
https://forums.aws.amazon.com/thread.jspa?threadID=317864

The current built in way of accomplishing this is to leverage User Pool Groups which will set appropriate IAM policy for your bucket locations: https://docs.amplify.aws/cli/auth/groups
Will mark this as a feature request for alternative solutions in the future.

The current built in way of accomplishing this is to leverage User Pool Groups which will set appropriate IAM policy for your bucket locations: https://docs.amplify.aws/cli/auth/groups
Will mark this as a feature request for alternative solutions in the future.

How does that give users from a group access to the files uploaded by other users within the group?
I'm not getting this. :)
If userA private file it will be under: "/myPrivatePrefix/${cognito-identity.amazonaws.com:sub}/*".
UserB does not know the sub of userA. And even if he did, how would you compose the IAM policy?

cc @palpatim @renebrandel @swaminator for visibility

A workaround for this use case would be to leverage Cognito’s custom attributes for managing multi-tenancy.

Configure tenant custom attribute for access control on the identity pool using steps mentioned here.
Next, configure the following auth role override to include a custom bucket policy based on on tenant principal tag

amplify override project

export function override(resources: AmplifyRootStackTemplate) {
    const authRole = resources.unauthRole;

    const basePolicies = Array.isArray(authRole.policies)
      ? authRole.policies
      : [authRole.policies];

    authRole.policies = [
      ...basePolicies,
      {
        policyName: "amplify-multi-tenant-custom-attribute-policy",
        policyDocument: {
          Version: "2012-10-17",
          Statement: [
            {
              Resource: "arn:aws:s3:::<bucketname>/${aws:PrincipalTag/tenant}/*", //resource to permission, needs to be restricted for according to scope
              Action: ['s3:ListBucket', 's3:PutObject', 's3:GetObject', 's3:DeleteObject'], //permissions
              Effect: "Allow", //action allow or deny
            },
          ],
        },
      },
    ];
}

We then configure the default public, protected & private prefixes to empty strings so that these prefixes does not get appended based on our auth configuration -

Amplify.configure(awsconfig);
Storage.configure({
  customPrefix: {
      public: '',
      protected: '',
      private: ''
  }

Lastly, while making get/put requests from front-end we can get custom attribute value using Auth.currentAuthenticatedUser() and make request -
const result = await Storage.put("<tenant>/test.txt", "Hello");


Feat: Implement Inverse PCA function

Description
Implemented a new method for inverse PCA, similar to sklearn.decomposition.PCA.inverse_transform()

Can you update to latest master?

Thank you!


Add access to the event in InputData

Description

Fixes #483 by adding event field on InputData struct.
I haven't added any tests only because there was no test module on the source I've worked on.
I also have tried to apply the same kind of fix to ChangeEvent but failed since the current API of ChangeData can't contain the event data.
Checklist:

[x] I have run ./ci/run_stable_checks.sh
[x] I have reviewed my own code
[ ] I have added tests

Looks great @XiNiHa! Thanks for adding this 👍
I marked this as a breaking change because it would break existing code that destructures like this InputData { value }  = data

Looks great @XiNiHa! Thanks for adding this +1
I marked this as a breaking change because it would break existing code that destructures like this InputData { value } = data

InputData { value , .. } = data


Documentation

Need to update the README file to keep it current with package features and document how to best utilize it in a Laravel project.

The README for this package should be updated to include references to the full documentation for the package at https://docs.tipoff.com as outlined in this issue:

https://github.com/tipoff/docs/issues/5


About unable to Failed when extracting features from images

Hi, I installed the libs and now can correctly make the project but I run into problem that It cannot extracting features from any images. it will say:
Config file is ../config/config.yaml
First image size: 320x240
Second image size: 320x240
Building inference engine......
SuperPoint and SuperGlue inference engine build success.
SuperPoint and SuperGlue test in 100 times.
Failed when extracting features from first image.
could you help me on this? thanks

it is this line throwing false statement

my cuda version is 11.6 and my tensorRT version is 8.4

@rrryy39 Hi, you can delete the old engine file and rerun it to generate the new engine file automatically.


Some doubts about pass rate

Hi,
I would like to express my gratitude for your efforts in open-sourcing this project. Your work is highly appreciated and I believe it is very valuable for the research community.
However, I am currently facing some issues while trying to reproduce the results as described in your paper.
Here are the details of the problem:
I used the current version of gpt3.5-turbo-16k as an evaluator to run tooleval on the reproduction_data/chatgpt_dfs/G3_instruction you provided, and obtained a pass rate of only 17%. I would like to know if this is due to the GPT version issue or if there was a mistake in one of my steps. Could you please provide updated results with the latest version?

Hi, did you figure out an answer for this? I am also encountering lower pass rates.


[Hacktoberfest]: Update Step 3 Try Some Code Section with new resource

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
To do:
Add the below line into the Readme.md at line 77 or after the last line in the "Try Some Code" / Step 3 table:
| Twilio Quest | Twilio | 3 | Learn to Use APIs While Playing a Game |
📋 Step by Step
Step by Step

🙋 Claim an issue: Comment on it.
Create a New Branch How to branch, Commit, Pull, Merge - start at step2
Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
Commit it Make it a good one
Make a Pull Request Tell us what you did
We'll review it and merge it in

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

Resolved by PR #63
@all-contributors please add @amykapernick  for code doc mentoring talks content examples 📋


UI Fixes on metadata filtering and checkbox dropdown

Description
This PR fixes some irregularities on metadata filtering and removes dropdown icon in check-all box
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix a feature that knowingly causes existing functionality to not work as expected)

Test and Reproduce
Outline the steps to test or reproduce the PR here.

Impacted Areas in Application
List general components of the application that this PR will affect:
Which pages?

[ ] Login Screen
[ ] Single Upload Page
[ ] Batch Upload Page
[ ] All Projects Page
[ ] Sample Details Page
[ ] Report Page

Specific components

Testing Script:
###Login Page

Successfully login to the application and get taken to the project page

###Single Upload

Using an AWS path that doesn't exist throws an error
Succesfully uploaded files from a folder (use test host)
Uploading a duplicate file throws an error
Pipeline gets initiated successfully

###Batch Upload

Using an AWS path that doesn't exist throws an error
Succesfully uploaded files from a folder (use test host)
Navigate to batch upload settings page after upload
Host selection from previous page still selected
Uploading a duplicate file throws a warning
Pipeline gets initiated successfully

###All Project Page

Switch between projects
Search for a sample
Navigate through different pages of samples
Select Upload new sample button
Select sample to see generated report

###Sample Details Page

Information is consistent from Project Page
Notes are editable and save successfully
Can navigate to report page

###Report Page

Data loads succesfully
Collapse and Uncollapse button works
Clicking on the taxonomy name gives you total reads for that taxon
Category filter works
Genus Search works
Filters work as expected
Disabling Filters works
Filtering by column works

Checklist:

[ ] I have run through the testing script to make sure current functionality is unchanged
[ ] I have done relevant tests that prove my fix is effective or that my feature works
[ ] I have spent time testing out edge cases for my feature
[ ] I have updated the test script or pull request template if necessary
[ ] New and existing unit tests pass locally with my changes

I still have trouble closing the metadata filter box. Had to refresh the page to close it.
When I filter on Tissue type '-', I got nothing. It should show all the samples with tissue type == nil

@yunfangjuan, the tissue-type issue has been fixed in this PR: https://github.com/chanzuckerberg/idseq-web/pull/788.

For metadata filtering could you make it not fetching samples if there’s no change when people open/close the filter box?
This is a question for @eggerdesigns but we don't really show people what filters are turned on because they are hiding behind the box and that makes the filtered results very confusing. I suppose we are not merging this PR to master directly once it's approved?

Also, here is a bug:
When you clicking on some filters, the url changes. But when you hit reload, it shows you different results. I think filters specified in the url needs to be respected.


SpecAn - AMPMLoadReferenceWaveformFromTDMSFile

What does this Pull Request accomplish?
Added Grpc device support for newly added private API -  LoadReferenceWaveformFromTDMSFile
It has been implemented for 2 personalities for RFmx
Why should this Pull Request be merged?
To support new APIs
What testing has been done?
NA

Work Item #2573723 -> https://dev.azure.com/ni/DevCentral/_workitems/edit/2573723/

@maxxboehme

@maxxboehme RFmx is getting this dependency ni-grpc-device-restricted-files from the following location
\us-aus-argo\RnD\perforceExports\build\exports\adhoc\ni-g\ni-grpc-device-restricted-files\official\export
I don't see any latest build. How does it get generated? We are dependent on this new export to push some changes in ni-central RFmx
@reckenro @astarche


PromiseKit 1.6.x - Support for tvOS and WatchOS

I'm developing a library that is dependant on AFN and PromiseKit. The latest AFN (3.0.0-beta) has support for watchOS and tvOS, and so does PromiseKit 2.x/3.x.
Is there anyway that we can add support for the said targets in PMK 1.6 please?
Thanks!

I can confirm that by adding
s.watchos.deployment_target = '2.0'
to the pod spec with the v1.6.0 tag that using PromiseKit 1.6 works on watchOS.
I could make a pull request, but I'm not sure how you guys plan to keep maintaining 1.6.x as it looks like it's currently all a linear history in master?

Thanks @staminajim - It seems like WatchOS is working, but tvOS is still no go.

@mofirouz does it work if you add
s.tvos.deployment_target = '9.0' to the 1.6.0 pod spec?
I don't have any tvOS targets set up to quickly try that.

Sadly I don't have a target that will enable that as well. I've added support for it in the library that I'm building for whenever PromiseKit adds that in.
On 24 February 2016 at 10:05:12, James V<EMAIL_ADDRESS>wrote:
@mofirouz does it work if you add
s.tvos.deployment_target = '9.0' to the 1.6.0 pod spec?
I don't have any tvOS targets set up to quickly try that.
—
Reply to this email directly or view it on GitHub.

I had a need to use Heroic Labs with tvOS, so I figured I would provide an update:
I locally copied both Heroic Labs and PromiseKit (v1.6), modified the pod spec files to include the tvOS target, and the pods successfully installed!

PR welcome, testing this is the tricky part, can advise how.

@mxcl I would but I honestly don't know where/which branch the code for the 1.6.x release is - similar to what @staminajim said above.
If you could advise on the git strategy for this project, I'll open a PR asap.

There is no branch, check out the tag.
git checkout -b 1.6.0

@mxcl , but don't we need a PK 1.6.x branch to make the pull request against and do future v1 releases from?  We can't clobber master since that's the v3 tree.

Never mind, I just found the discussion continued in the pull request ;)

Hi @nathanhosselton thanks for merging the PR in. Could I kindly ask for a new release of the 1.x branch so I can upgrade to it and use it in my code please? Thanks.

@mofirouz release it in what way, exactly?

@nathanhosselton A tag + cocoapods, please :)

So there are numerous failures occurring when attempting to lint the podspec related to the new inclusion of watchOS and tvOS. Aside from the 1.x version of the podspec file not being written in such a way as to trivially handle additional operating system targets, detailed exceptions are going to have to be declared for most of the subspecs' watchOS and tvOS source files, if not in the source code itself.
For example, CLLocationManager's startUpdatingLocation method is not available on watchOS or tvOS. On the master branch we simply don't include the CLLocationManager+PromiseKit source files for watchOS in the podspec (which is really a workaround since the functionality could theoretically be provided for those OSs), so the same could be done for 1.x, but this is just one of many updates that will be required. And again, the 1.x and 3.x podspec files are currently very different, so this unfortunately isn't a case where we could just copy+paste.
All this is to say that pushing 1.7.0 to the pod trunk is going to take longer than expected. I have done minimal work to this end since pushing the latest changes to the legacy-1.x branch, so if you were interested in taking this task on then you could start from there. Otherwise I will chip away at it when I can.

OK, I think I understand what changes need to be made to the podspec file now. I can probably knock this out tonight or tomorrow.

Alright, 1.7.0 should be available via CocoaPods now. I tested it locally with watchOS and tvOS targets and everything seemed to be fine, but let me know if you try it out and have issues.
For now I had to make the general sacrifices that I mentioned above in order to at least get it to lint, so some of the category subspecs are unavailable on watchOS and tvOS, most notably the NSURLConnection category. I've left comments in the podspec file at the subspec lines which can work with tvOS/watchOS but don't currently due to API availability differences, so anyone who is feeling adventurous enough can try to take those TODOs on.

Thank you ever so much @nathanhosselton for this. I've integrated it and it seems to work. :+1:


sdk/textanalytics/azure-ai-textanalytics/samples/sample_multi_category_classify.py

Psample_multi_category_classify.py:
****:
windows:
3.10:

Describe the bug
Module Existence: The MultiCategoryClassifyAction module might not be available in the version of the azure-ai-textanalytics package you have installed. It's possible that this module was introduced in a newer version.
Namespace Change: The module might exist in a different namespace or under a different name in the version you are using. Double-check the documentation or release notes for the package to see if there have been any changes in module organization.
Compatibility: Ensure that you are using a version of the azure-ai-textanalytics package that is compatible with the module you are trying to import.
To Reproduce
Steps to reproduce the behavior:

try to run below script
script path : sdk/textanalytics/azure-ai-textanalytics/samples/sample_multi_category_classify.py
script link : https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/textanalytics/azure-ai-textanalytics/samples/sample_multi_label_classify.py

Expected behavior
it not gone run
Traceback (most recent call last):
File "D:\ahaguru\ahaguru-analytics-aI-integration-scripts\Krunal - Ahaguru\prediction_api\modal_test1.py", line 81, in
from azure.ai.textanalytics import TextAnalyticsClient,MultiCategoryClassifyAction
ImportError: cannot import name 'MultiCategoryClassifyAction' from 'azure.ai.textanalytics' (D:\ahaguru.a\Lib\site-packages\azure\ai\textanalytics_init_.py)
Screenshots

Additional context
Try to test multilabel classification locallly

Thanks for the feedback, we’ll investigate asap.

@B2-krunalrana the model is called MultiLabelClassifyAction, not MultiCategoryClassifyAction. Can you try that in your code and let us know if it doesn't work?


Add ui8/si8 mobilenet benchmarks

Very early as these are known to not be performant but was thinking of
tracking already.

Benchmarking is currently pretty slow and resource limited. I'm therefore easy of adding "nice to have" models, especially if they are unoptimized (aka slow) and we are not actively optimizing against them (so it's unclear who's using these numbers)

That makes sense, these are slow but small models. I completely understand the concern though.

Small helps. Can you see empirically how much they slow down the pipeline overall (transferring artifacts is a cost too). Add the "buildkite:benchmark" label to trigger the benchmarks

(seems buildkite benchmark may be stuck post move)

Closing stale PR.


Debug: explore dynamic snippets

Refs: https://github.com/Microsoft/vscode/issues/62851
Dynamic snippets should be shown on top of the add configuration suggest box and they should get configurations via provideDebugConfigurations call.
One dynamic snippet per debug type.

Closing as duplicate of #65988


Null object

{System.NullReferenceException: Object reference not set to an instance of an object.
   at RtfPipe.Rtf.BuildHtmlContent(IRtfGroup content, XmlWriter writer)
   at RtfPipe.Rtf.ToHtml(RtfSource source, XmlWriter writer, RtfHtmlWriterSettings settings)
   at RtfPipe.Rtf.ToHtml(RtfSource source, RtfHtmlWriterSettings settings)}

When trying to parse:
"{\\rtf1\\ansi\\ansicpg1252\\uc1\\htmautsp\\deff2{\\fonttbl{\\f0\\fcharset0 Times New Roman;}{\\f2\\fcharset0 GenericSansSerif;}}{\\colortbl\\red0\\green0\\blue0;\\red255\\green255\\blue255;}\\loch\\hich\\dbch\\pard\\plain\\ltrpar\\itap0{\\lang1033\\fs18\\f2\\cf0 \\cf0\\ql{\\f2 {\\ltrch Alyssa Mourning}\\li0\\ri0\\sa0\\sb0\\fi0\\ql\\par}\r\n}\r\n}"

Using Rtf.ToHtml(rtfAsString);

I receive a similar error when attempting:
Rtf.ToHtml("{\\rtf1\\ansi\\b Hello World\\b0 }");
It may be worth noting that I'm using dotnent core

In my case the problem was a hidden inner exception:
'Windows-1252' is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.
Parameter name: name

I will try to fix it now...


Replaced cURL slack workflows with slackapi

Fixes

Fixes #3461 by @dhruvkb
Description

replaced the cURL with slackapi for github-actions to make it more aligned and maintainable.

Testing Instructions

Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Thank you so much @obulat and @dhruvkb.
I got little busy with holidays so was not able to make changes you requested.
Thank you so much for applying changes on my behalf.
Best,
Pk Patel


Bookmarks on files list disappear after add instruction in project

Describe the bug
I had few bookmarks in my project. Then I added instruction. When I came back to my project, all bookmarks disappeared.
To Reproduce
Steps to reproduce the behavior:

Go to any project
Add some bookmarks
Go to "Settings" -> "Instructions"
Add some instruction and save it
Go back to project and see that You have only one bookmark now: "Default"

Expected behavior
I expect to bookmarks don't disappear until I don't delete them :)
Screenshots
Before:

After add instruction to project:

Environment (please complete the following information):

Windows 7
Chrome
Label Studio Version [e.g.1.0.1]

@kasiopac Thank you for your report, it's a bug on our side. We will fix it asap.

@kasiopac Could you check this PR: https://github.com/heartexlabs/label-studio/pull/799
There is a fix of this bug.


I can't craft the blocks

Whenever I try to craft (for example : the mahogany chest) the crafting recipe does not show up and If i want it added to my world I need to use creative. The vanilla block versions work but the modded doesn't.  I play on 1.15.2.

Install the datapack that you can find undee additional files x)

oops haha.. do i just put the additional files in the mods folder?

in your world folder under datapacks :) you can check in-game if it worked with "/datapack list" i think

do we just copy-paste ? because that's what i did but still can't see recipes

just put the zip into the datapack folder

Ohhh silly me! I was extracting then pasting, tysm!


Issue when trying to enable tracing

Hi,
When I add the following piece of code in the taskweaver_config.json file:
"tracing.enabled": true,
"tracing.exporter": "otlp",
"tracing.endpoint": "http://<IP_ADDRESS>:4317",
"tracing.tokenizer_target_model": "gpt-4"
I'm getting the following error.
.ConnectTimeout: HTTPSConnectionPool(host='openaipublic.blob.core.windows.net', port=443): Max retries exceeded with url: /encodings/cl100k_base.tiktoken

Can someone suggest a reason for this error to occur?

It seems the tokenizer, i.e., tiktoken, failed to download its configuration file. Can you make sure that you environment has no problem of internet access?

I did have a problem of accessing the internet to download the tiktoken encoding dictionary. So I downloaded it locally for tiktoken to use. Found this link helpful" https://stackoverflow.com/questions/76106366/how-to-use-tiktoken-in-offline-mode-computer


[r] Port ephemeral classes from Python to R

Split-out from #839.
TBD how much of this, and how, goes over idiomatically to Python once #736 is merged.
In any event #736 is a prerequisite.

#736 has been completed, this work can start now.

✨

@mlin or @mojaveazure depending on cycles/scheduling


Release Zebra (v2.0.0-rc.0)

name: 'Release Checklist Template'
about: 'Checklist to create and publish a Zebra release'
title: 'Release Zebra (version)'
labels: 'A-release, C-trivial, P-Critical :ambulance:'
assignees: ''

Prepare for the Release

[ ] Make sure there has been at least one successful full sync test since the last state change, or start a manual full sync.
[ ] Make sure the PRs with the new checkpoint hashes and missed dependencies are already merged.
(See the release ticket checklist for details)

Summarise Release Changes
These steps can be done a few days before the release, in the same PR:
Change Log
Important: Any merge into main deletes any edits to the draft changelog.
Once you are ready to tag a release, copy the draft changelog into CHANGELOG.md.
We use the Release Drafter workflow to automatically create a draft changelog. We follow the Keep a Changelog format.
To create the final change log:

[x] Copy the latest draft changelog into CHANGELOG.md (there can be multiple draft releases)
[x] Delete any trivial changes

[ ] Put the list of deleted changelog entries in a PR comment to make reviewing easier

[ ] Combine duplicate changes
[ ] Edit change descriptions so they will make sense to Zebra users
[ ] Check the category for each change

Prefer the "Fix" category if you're not sure

README
README updates can be skipped for urgent releases.
Update the README to:

[ ] Remove any "Known Issues" that have been fixed since the last release.
[ ] Update the "Build and Run Instructions" with any new dependencies.
Check for changes in the Dockerfile since the last tag: git diff <previous-release-tag> docker/Dockerfile.
[ ] If Zebra has started using newer Rust language features or standard library APIs, update the known working Rust version in the README, book, and Cargo.tomls

You can use a command like:
fastmod --fixed-strings '1.58' '1.65'

Create the Release PR

[ ] Push the updated changelog and README into a new branch
for example: bump-v1.0.0 - this needs to be different to the tag name
[ ] Create a release PR by adding &template=release-checklist.md to the comparing url (Example).
[ ] Freeze the batched queue using Mergify.
[ ] Mark all the release PRs as Critical priority, so they go in the urgent Mergify queue.
[ ] Mark all non-release PRs with do-not-merge, because Mergify checks approved PRs against every commit, even when a queue is frozen.

Update Versions and End of Support
Update Zebra Version
Choose a Release Level
Zebra follows semantic versioning. Semantic versions look like: MAJOR.MINOR.PATCH[-TAG.PRE-RELEASE]
Choose a release level for zebrad. Release levels are based on user-visible changes from the changelog:

Mainnet Network Upgrades are major releases
significant new features or behaviour changes; changes to RPCs, command-line, or configs; and deprecations or removals are minor releases
otherwise, it is a patch release

Zebra's Rust API doesn't have any support or stability guarantees, so we keep all the zebra-* and tower-* crates on a beta pre-release version.
Update Crate Versions
If you're publishing crates for the first time, log in to crates.io,
and make sure you're a member of owners group.
Check that the release will work:

[ ] Update crate versions, commit the changes to the release branch, and do a release dry-run:

# Update everything except for alpha crates and zebrad:
cargo release version --verbose --execute --allow-branch '*' --workspace --exclude zebrad --exclude zebra-scan --exclude zebra-grpc beta
# Due to a bug in cargo-release, we need to pass exact versions for alpha crates:
cargo release version --verbose --execute --allow-branch '*' --package zebra-scan 0.1.0-alpha.4
cargo release version --verbose --execute --allow-branch '*' --package zebra-grpc 0.1.0-alpha.2
# Update zebrad:
cargo release version --verbose --execute --allow-branch '*' --package zebrad patch # [ major | minor | patch ]
# Continue with the release process:
cargo release replace --verbose --execute --allow-branch '*' --package zebrad
cargo release commit --verbose --execute --allow-branch '*'

Crate publishing is automatically checked in CI using "dry run" mode, however due to a bug in cargo-release we need to pass exact versions to the alpha crates:

[ ] Update zebra-scan and zebra-grpc alpha crates in the release-crates-dry-run workflow script
[ ] Push the above version changes to the release branch.

Update End of Support
The end of support height is calculated from the current blockchain height:

[ ] Find where the Zcash blockchain tip is now by using a Zcash explorer or other tool.
[ ] Replace ESTIMATED_RELEASE_HEIGHT in end_of_support.rs with the height you estimate the release will be tagged.

Optional: calculate the release tagging height

Add 1152 blocks for each day until the release
For example, if the release is in 3 days, add 1152 * 3 to the current Mainnet block height

Update the Release PR

[ ] Push the version increments and the release constants to the release branch.

Publish the Zebra Release
Create the GitHub Pre-Release

[ ] Wait for all the release PRs to be merged
[ ] Create a new release using the draft release as a base, by clicking the Edit icon in the draft release
[ ] Set the tag name to the version tag,
for example: v1.0.0
[ ] Set the release to target the main branch
[ ] Set the release title to Zebra  followed by the version tag,
for example: Zebra 1.0.0
[ ] Replace the prepopulated draft changelog in the release description with the final changelog you created;
starting just after the title ## [Zebra ... of the current version being released,
and ending just before the title of the previous release.
[ ] Mark the release as 'pre-release', until it has been built and tested
[ ] Publish the pre-release to GitHub using "Publish Release"
[ ] Delete all the draft releases from the list of releases

Test the Pre-Release

[ ] Wait until the Docker binaries have been built on main, and the quick tests have passed:

[ ] ci-unit-tests-docker.yml
[ ] ci-integration-tests-gcp.yml

[ ] Wait until the pre-release deployment machines have successfully launched

Publish Release

[ ] Publish the release to GitHub by disabling 'pre-release', then clicking "Set as the latest release"

Publish Crates

[ ] Run cargo login
[ ] Run cargo clean in the zebra repo (optional)
[ ] Publish the crates to crates.io: cargo release publish --verbose --workspace --execute
[ ] Check that Zebra can be installed from crates.io:
cargo install --locked --force --version 1.minor.patch zebrad && ~/.cargo/bin/zebrad
and put the output in a comment on the PR.

Publish Docker Images

[ ] Wait for the the Docker images to be published successfully.
[ ] Un-freeze the batched queue using Mergify.
[ ] Remove do-not-merge from the PRs you added it to

Release Failures
If building or running fails after tagging:

Tag a new release, following these instructions...

Fix the bug that caused the failure
Start a new patch release
Skip the Release Preparation, and start at the Release Changes step
Update CHANGELOG.md with details about the fix
Follow the release checklist for the new Zebra version

The following pull requests were not included in the changelog:
Trivial TODO: put this in a PR comment, not the CHANGELOG

release(checkpoints): Update checkpoints for 2.0.0.-rc.0 (#8924)
fix(clippy): last lints (#8855)
Update utilities README.md (#8824)
add(docs): Add minimal hardware requirements (#8822)
fix(deps): Replace serde_yaml by serde_yml (#8825)
build(deps): bump docker/scout-action from 1.13.0 to 1.14.0 in the devops group (#8890)
build(deps): bump the devops group with 3 updates (#8919)
build(deps): bump the devops group with 4 updates (#8905)
build(deps): bump the prod group across 1 directory with 24 updates (#8899)
build(deps): bump tj-actions/changed-files from 45.0.0 to 45.0.1 in the devops group (#8835)
build(deps): bump tj-actions/changed-files from 45.0.1 to 45.0.2 in the devops group (#8874)


errors

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/modify
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

It seems that you replaced the code in the Index.cshtml.cs file and not the Index.cshtml page. I’d recommend that you delete this project and start over making sure that you replace the code in the cshtml file. Let me know if that helps!
And I’m planning to add some clarification to the tutorial about this. /cc @danroth27


SAM CORS does not create needed Method Responses

Description:
Invalid Response status code specified when trying to apply CORS to SAM-created API gateway endpoints.
Steps to reproduce the issue:

Create a SAM template w/ CORS enabled
Deploy and have artifacts created
Attempt to set CORS

Observed result:
Error listed above. I think the issue is that the Method Responses that API Gateway automatically creates through the GUI when applying CORS are not being added to the endpoints that SAM creates. Therefore, when moving artifacts to another environment in a manual process (such as I have to do for my organization, we cannot use SAM to deploy Production-level artifacts) I run into the issue showed above.

Expected result:
Set endpoints correctly. Addt., why are endpoints created through SAM automatically set to use proxy-integration?
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
Output of sam --version:
0.6.0
Optional Debug logs:
Sample Template.YAML (Acct. Credentials/Role obscured for security):
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: ROLE
Globals:
    Function:
        Timeout: 300
Resources:
    MyAPI:
        Type: AWS::Serverless::Api
        Properties:
            Name: my-api
            StageName: v1
            EndpointConfiguration: EDGE
            Cors:
                AllowMethods: "'GET,POST,PUT,DELETE'"
                AllowHeaders: "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'"
                AllowOrigin: "'*'"
    MyAPIFunction:
        Type: AWS::Serverless::Function
        Properties:
            FunctionName: my-api
            CodeUri: my-api-lambda/
            Handler: index.handler
            Runtime: nodejs8.10
            Role: arn:aws:iam::XXXXXX:role/role
            Description: This lambda runs functionality.
            Environment:
                Variables:
                    HIDDEN: True
            Events:
                Get:
                    Type: Api
                    Properties:
                        Path: /my/{id}
                        Method: post
                        RestApiId:
                            Ref: MyAPI
                Test:
                    Type: Api
                    Properties:
                        Path: /my/test
                        Method: post
                        RestApiId:
                            Ref: MyAPI
                Update:
                    Type: Api
                    Properties:
                        Path: /my/{id}
                        Method: put
                        RestApiId:
                            Ref: MyAPI
                Sync:
                    Type: Api
                    Properties:
                        Path: /my/sync/{id}
                        Method: get
                        RestApiId:
                            Ref: MyAPI

What you likely want to do is export your API from the GUI (on the Stage page) and specify that Swagger in the DefinitionBody of MyAPI

Hi @brettstack, what I'm looking to do is avoid creating a Swagger file, or creating an API Gateway from the GUI. I'm trying to accomplish building and deploying my serverless application stack through SAM only. However, I am running into the issues above when trying to re-configure CORS, or add an API-Key.
I'm lead to believe there is something wrong either with SAM or my template, for instance, why do no Method Responses get generated for the endpoints I deploy?

I see. We do have a plan for minimizing the amount of Swagger you need to write; unfortunately, for now it sounds like your only option is to define Swagger for:

Using API Keys
Using API Gateway without Lambda Proxy Integration

@brettstack - What confuses me the most is why SAM is not creating the Method Resources. Is that by design? Is it due to my template? Again, when you create an endpoint via the GUI, the default Method Resources are created in order to set CORS on a resource. The screens I attached show that this was not possible during my deployment. It makes me feel as if I did something wrong in my SAM template.

SAM CORS only creates the preflight/OPTIONS configuration for you. This is because SAM creates API proxy integrations (as you mentioned) which do not allow setting method response.

Thanks @brettstack. I'm still a bit confused on the error I see on the API Gateway GUI (second screenshot) -- why does API Gateway make these checks for endpoints that are Proxy Integrations?


MacVim should disable Input Source in command mode

All commands are broken in command mode if an Input Source is activated.
MacVim should disable Input Source in command mode.

The snapshot shows the broken commands when I press `j` repeatedly if an Input Source is activated. The commands should have moved down the cursor if this bug is fixed.

Have you tried this setting?
set noimdisable