Support VueCli3 with Jest

Summary
Unable to run stryker because it fail on import in test.
Stryker config
module.exports = function(config) {
  config.set({
    mutate: ["src/**/*.js", "src/**/*.ts", "src/**/*.vue"],
    mutator: "vue",
    testRunner: "jest",
    jest: {
      config: require('./jest.config.js')
    },
    reporters: ["progress", "clear-text", "html"],
    coverageAnalysis: "off"
  });
};

Stryker environment
    "@stryker-mutator/core": "^1.1.1",
    "@stryker-mutator/html-reporter": "^1.1.1",
    "@stryker-mutator/javascript-mutator": "^1.1.1",
    "@stryker-mutator/jest-runner": "^1.1.1",
    "@stryker-mutator/vue-mutator": "^1.1.1",
    "@vue/cli-plugin-e2e-cypress": "^3.2.0",
    "@vue/cli-plugin-unit-jest": "^3.2.0",
    "@vue/cli-service": "^3.2.0",
    "@vue/test-utils": "^1.0.0-beta.20",
    "babel-jest": "^23.6.0",
    "jest-junit": "^5.2.0",
    "vue-jest": "^3.0.2",
    "core-js": "^3.0.0",

Test runner environment

Npm command :
"test:e2e": "vue-cli-service test:e2e",
 "test:unit": "vue-cli-service test:unit"

Jest config:
module.exports = {
  moduleFileExtensions: [
    'js',
    'jsx',
    'json',
    'vue',
  ],
  transform: {
    '^.+\\.js$': 'babel-jest',
    '^.+\\.vue$': 'vue-jest',
    '.+\\.(css|styl|less|sass|scss|svg|png|jpg|ttf|woff|woff2)$': 'jest-transform-stub',
    '^.+\\.jsx?$': 'babel-jest',
  },
  moduleNameMapper: {
    '^@/(.*)$': '<rootDir>/src/$1',
  },
  snapshotSerializers: [
    'jest-serializer-vue',
  ],
  testMatch: [
    '**/tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx)',
  ],
  testURL: 'http://localhost/',
  reporters: [
    'default',
    'jest-junit',
  ],
  collectCoverage: true,
  collectCoverageFrom: [
    'src/**/*.{js,vue}',
    '!src/main.js',
    '!src/index.js'
  ],
  coverageReporters: [
    'lcov',
    'cobertura',
  ],
  coverageDirectory: './target',
};

My Environment

software
version(s)

node
v11.0.0

npm
v6.9.0

Stryker.log
14:37:36 (9999) ERROR InitialTestExecutor One or more tests resulted in an error:
	  ● Test suite failed to run

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/AwesomeTable.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import "core-js/modules/es6.array.sort";
                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    SyntaxError: Unexpected string

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/models/PaginationUtils.class.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import PaginationUtils from<EMAIL_ADDRESS>                                                                                ^^^^^^^^^^^^^^^

    SyntaxError: Unexpected identifier

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/components/filters/FilterDate.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { shallowMount } from '@vue/test-utils';
                                                                                ^

    SyntaxError: Unexpected token {

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/components/filters/FilterText.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import _Promise from "/home/vmoittie/Workspaces/awesome-table/node_modules/@babel/runtime-corejs2/core-js/promise";
                                                                                ^^^^^^^^

    SyntaxError: Unexpected identifier

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/components/RowData.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { shallowMount, createLocalVue } from '@vue/test-utils';
                                                                                ^

    SyntaxError: Unexpected token {

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/components/FilterManager.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { shallowMount } from '@vue/test-utils';
                                                                                ^

    SyntaxError: Unexpected token {

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/App.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { shallowMount } from '@vue/test-utils';
                                                                                ^

    SyntaxError: Unexpected token {

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

	  ● Test suite failed to run

    /home/vmoittie/Workspaces/awesome-table/.stryker-tmp/sandbox3319273/tests/unit/components/filters/FilterList.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import "core-js/modules/es6.array.find";
                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    SyntaxError: Unexpected string

      at ScriptTransformer._transformAndBuildScript (../../node_modules/jest-runtime/build/script_transformer.js:403:17)

14:37:36 (9999) ERROR StrykerCli an error occurred Error: Something went wrong in the initial test run
    at InitialTestExecutor.validateResult (/home/vmoittie/Workspaces/awesome-table/node_modules/@stryker-mutator/core/src/process/InitialTestExecutor.js:117:15)
    at InitialTestExecutor.<anonymous> (/home/vmoittie/Workspaces/awesome-table/node_modules/@stryker-mutator/core/src/process/InitialTestExecutor.js:46:30)
    at step (/home/vmoittie/Workspaces/awesome-table/node_modules/tslib/tslib.js:133:27)
    at Object.next (/home/vmoittie/Workspaces/awesome-table/node_modules/tslib/tslib.js:114:57)
    at fulfilled (/home/vmoittie/Workspaces/awesome-table/node_modules/tslib/tslib.js:104:62)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Thank for your support :)

Thanks for opening this issue! Is it possible for you to create a repository with an example of this issue? (I assume the code is not open source)

Yes, I do that, please wait =D

https://github.com/Zorin95670/stryker-test
It's a simple project create with vue cli 3, then I add stryker.

I've looked into this. When you use jest directly, you get the same error:
$ npx jest -c jest.config.js
 FAIL  tests/unit/example.spec.js
  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    C:\z\github\Zorin95670\stryker-test\tests\unit\example.spec.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { shallowMount } from '@vue/test-utils';

Apparently, your unit test command is: vue-cli-service test:unit
So, yet another CLI to ruin this beautiful day.
The magic this CLI does is incredibly simple. It sets 2 environment variables and then calls jest. Apparently, those environment variables are what does the magic 🙄
https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-plugin-unit-jest/index.js#L13-L15
Workaround:

Install cross-env: npm i -D cross-env
Add this script: "stryker": "cross-env VUE_CLI_BABEL_TARGET_NODE=true VUE_CLI_BABEL_TRANSPILE_MODULES=true stryker run"
Run Stryker: npm run stryker

That should do the trick.
Note: Apparently: the HTML reporter cannot handle </script> tags in user code yet. Please see #1482

Thank a lot for your response, I go test it =D

@simondel I'm not sure what we should do here. Adding a projectType: 'vue-cli-service' doesn't seem maintainable. Who knows what they will add in the future. On the other hand, how else would we support it?

I think Vue 3 will change things quite a bit. Unfortunately we can't really wait on that because it's currently planned for Q3 2019.
I think we should add a project type for the  vue -cli-service in this case.

Or, I can also report the bug in vu-cli project. Because is link to vue cli .

@nicojs This got rid of all of the transform errors, but it now results in a different set of errors:
><EMAIL_ADDRESS>stryker /home/dphillips/Documents/RedHat/Workspace/ui-bootstrap
> cross-env VUE_CLI_BABEL_TARGET_NODE=true VUE_CLI_BABEL_TRANSPILE_MODULES=true stryker run

21:39:33 (9666) INFO ConfigReader Using stryker.conf.js in the current working directory.
21:39:33 (9666) INFO InputFileResolver Found 7 of 49 file(s) to be mutated.
21:39:33 (9666) INFO InitialTestExecutor Starting initial test run. This may take a while.
21:39:34 (9666) ERROR InitialTestExecutor One or more tests resulted in an error:
          ● Test suite failed to run

    TypeError: $export is not a function

      at Object.<anonymous> (../../node_modules/core-js/library/modules/es6.object.define-property.js:6:1)
      at Object.<anonymous> (../../node_modules/core-js/library/fn/object/define-property.js:3:1)
      at Object.<anonymous> (../../node_modules/@babel/runtime-corejs2/core-js/object/define-property.js:3:18)
      at Object.<anonymous> (../../node_modules/core-js/library/modules/_object-dp.js:5:46)
      at Object.<anonymous> (../../node_modules/core-js/library/modules/_hide.js:3:10)
      at Object.<anonymous> (../../node_modules/core-js/library/modules/_export.js:9:12)
      at Object.<anonymous> (../../node_modules/core-js/library/modules/_iter-define.js:5:15)
      at Object.<anonymous> (../../node_modules/core-js/library/modules/es6.string.iterator.js:6:1)
      at Object.<anonymous> (../../node_modules/core-js/library/fn/promise.js:5:1)
      at Object.<anonymous> (../../node_modules/@babel/runtime-corejs2/core-js/promise.js:3:18)
      at Object.<anonymous> (../../node_modules/regenerator-runtime/runtime.js:5:39)

I'll see if I can jigger the tranform ignores a little and make some progress.

Woot!!! Success!
I had transtormIgnorePatterns: ['<rootDir>/node_modules/'] in my jest.config.js. I changed it to transtormIgnorePatterns: ['/node_modules/'] and Styker runs perfectly!!!
Thanks again for all of the help!!!

I had transtormIgnorePatterns: ['<rootDir>/node_modules/'] in my jest.config.js. I changed it to transtormIgnorePatterns: ['/node_modules/'] and Styker runs perfectly!!!

@InfoSec812 Great to hear you got it working. However, we do want it to work out-of-the-box with your jest config. Could you open a separate issue detailing how to reproduce it? That would be most welcome!
@simondel
I agree, let's add it.

@nicojs So, like most others on this thread, I created a new Vue app using @vue/cli. Other than that, the only special things I have done (and it doesn't seem to make any difference) is that I sometimes use quasar-framework on top of Vue (vue add quasar). The instructions I just gave my colleague which seem to work are as follows:
Setting up Stryker for mutation testing:

Install stryker CLI: npm install -g stryker-cli
Initialize Stryker inside the project: stryker init
Add a script to package.json to run Stryker: "stryker": "cross-env VUE_CLI_BABEL_TARGET_NODE=true VUE_CLI_BABEL_TRANSPILE_MODULES=true stryker run"

I have created an example project to demonstrate the config, but the HTML reports are garbled for some reason:
https://github.com/InfoSec812/example-stryker-vue-project

I'm running into #1229 when I try and use vue+ts.  Tried using the cross-env setup from above, but I still get the import/export/module error.

Is this issue still present? I think we support 3x versions?

Is this issue still present? I think we support 3x versions?

https://github.com/stryker-mutator/stryker/issues/1229#issuecomment-646393363

@stephen-smith it seems to be working in 4.0.0 version :)
take a look at https://github.com/stryker-mutator/stryker/tree/epic/mutation-switching/e2e/test/vue-cli-javascript-jest
With small tweaks I could make it work as standalone
tests.zip

I think we should add a project type for the vue-cli-service in this case.

This should improve vue support. Something like this.
{
  "jest": {
    "projectType": "vue-cli"
  }
}

Finally got around to confirming this does work with:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>
configured with:
{
  "$schema": "https://raw.githubusercontent.com/stryker-mutator/stryker/master/packages/api/schema/stryker-core.json",
  "mutate": [
    "{src,lib,tests}/**/*.{{j,t}s?(x),vue}",
    "!{src,lib,tests}/**/?(*.)+(spec|test).{{j,t}s?(x),vue}"
  ],
  "disableTypeChecks": "{src,lib,tests}/**/*.{{j,t}s?(x),vue}",
  "testRunner": "jest",
  "coverage-analysis": "perTestInIsolation",
  "reporters": ["clear-text", "progress", "html"]
}

Issue can be closed.  (I don't have permissions.)

Thanks! Just a remark, you have some older dependencies that are no longer used: @stryker-mutator/vue-mutator, @stryker-mutator/javascript-mutator, @stryker-mutator/typescript can all be removed.


Clicks Per Minite Game Added

PR Description 📜
Fixes #4480
The "Click Per Minute Game" is an exciting and engaging game where users aim to achieve the highest number of clicks within one minute. It’s a fun and competitive way to test and improve your clicking speed and reaction time.

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @zalabhavy ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @zalabhavy, You have reached your limit to contribute in GameZone with a score of 170.
We believe in giving equal opportunity to everyone so you will not be able to contribute to GameZone now onwards. 💗
Thank you for your valuable time and contribution in GameZone 🕹!
Your merged pull requests:

#4435 with labels: level3 score: (45)
#4262 with labels: level3 score: (45)
#3987 with labels: level1 score: (10)
#3840 with labels: level3 score: (45)
#3728 with labels: level2 score: (25)

Thank you  @zalabhavy , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


doc: add --target option to README

Missed this in #937
If there are any other changes that need making to the README (or other documentation) I can add them in, this is a bit small by itself.

Thanks, landed in c4344b3.


Streaming api patch

Temp fix to reporter to always report data to streaming clients in a blocking way. This addresses the issue of explorer backend missing rewards but doesn't solve the issue of multiple clients on streams that use same reporter channels.

going to do this pr from develop and not from tag/0.1.29


bump wgpu to v13.1; Add Bracket Systems to correct stages

wgpu needed to be bumped to v13.1 to keep updated with bevy standards. I also bumped the packages since if you used bracket-pathfinding with bracket-bevy it complained about differences in bracket-geometry.
The final change was to add your custom systems to their respective stages. Previously you created the stages, and then added the systems using add_system but this adds the system to the CoreStage::Update of bevy. I created an enum for your stages for better readability than simple strings

Unfortunately, bumping wgpu isn't proving to be a simple thing at all. I'm working my way through - a lot of syntax changed. I'd like to not break the webgpu feature, so there's a lot to do!

Ah might have figured it would be more difficult. I'll close this PR since you plan to address this without breaking changes


JuliaCon 2025

Hi Cormullion :),
Are you interested in starting on the 2025 templates and graphics (or continuing at all)?
CC: @ranjanan
Best,
Raye

Yes I'd love to contribute to JuliaCon2025 in some/any way - I can't contribute much to Julia code itself, so having a minor role is very rewarding for me... :)
By the way, I was thinking the JuliaCon website could do with an overhaul - unfortunately I'm not much of a web developer (I can just criticize from a safe distance though...)

Do you have any thoughts on a JuliaCon Global 2025 logo? Something Pittsburgh specific? Cc @rkurchin

I must be honest and say I know nothing about Pittsburgh... So any hints or suggestions would be welcome... !

Pittsburgh is defined by many things, most notably its colors of Black & Gold. (https://pittsburghpa.gov/pittsburgh/flag-seal)

Black and gold for sure! Some other notable visuals around the city include:

Three Sisters bridges
the funnicular railroads, in particular the Duquesne Incline
the city skyline
presuming the venue does end up being some combination of Pitt and CMU, there are some iconic things on the campuses as well, such as the Cathedral of Learning, the Pausch Bridge, or The Fence

@rkurchin Thanks - I’ll indulge in a bit of armchair tourism! 😀

Not very original, but OK-ish-looking...

the bridges

gold border needs more forging

Another bridge

I tried something with the awesome 'cathedral' building, but not sure if it works:

Something a little more quirky:

a simple array


Added the init_.py to gcp and aws modules.

The modules gcp and aws do not define init.py that result in missing in the fabfed-py package.


Registry: eliminate entry pages?

I'd like to propose a little cleanup of the registry before considering a move (#2202). In particular, I'd like to suggest dropping the individual entry pages. Here's an example from https://opentelemetry.io/registry/instrumentation-js-angular:

Here is what is displayed on the Registry page for this entry:

How useful are the individual entry pages? Analytics show that they are consulted. For example:

https://opentelemetry.io/registry/collector-exporter-elastic/ accounts for 1.7% of the Registry traffic in the past 6 months, but if you visit it now, this link is now a 404
The Angular JS page referenced abvoe got 1.5% of the Registry traffic.

I'd like to suggest that we drop the individual entries pages. Folks who are interested in an entry, can visit the page/repo that it is linked to from the main Registry page. But I'm open to being convinced otherwise.
Thoughts @cartermp @svrnm @austinlparker

I didn't even know those pages exist 😅

That's because the registry doesn't provide a link to them :) ... so very few people will know about these pages.

I would agree with dropping them.


HSEARCH-4432 + HSEARCH-4433 + HSEARCH-4434 Upgrade to Hibernate ORM 5.4.33.Final

HSEARCH-4433: Upgrade to Log4j 2 in Hibernate Search 5.x tests
HSEARCH-4434 (backport from #2830): Avoid unnecessary synchronization in ExpectedLog4jLog
HSEARCH-4432: Upgrade to Hibernate ORM 5.4.33.Final

Marking as draft until ORM 5.4.33*.Final* gets released (right now it's published under the wrong version number 5.4.33)
cc @Sanne

It's released

Thanks @Sanne ; I restarted the CI job to test the upgrade.


The module is visible as completed after adding new unit

Describe the bug
The module is visible as completed after adding new unit.
To Reproduce
Steps to reproduce the behavior:

Finish module.
New Unit was added.

Expected behavior
I think xp shouldn't indicating that this module is finished.
Screenshots

Desktop:

OS: Windows 10
Browser: Chrome

This could be connected with #2058 and #2059.


Merge master to live #3

Second attempt to push new redirect live

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OfficeDev/VBA-content, working directory: W:\z0cc-s, target branch: live, target branch commit: 4f53a8d35069ebc57e10122696d7b151be1e1c45, source branch: master, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Scrape restricted twitter accounts

Can this scraper scrape tweets like https://twitter.com/jackiec57 ?
To remove the need to click "show sensitive content anyways", it would need to...

Login just like https://gist.github.com/momota10/969d904b4cad239da2a5c00df1ad87e7
Go to https://twitter.com/settings/safety
Check the "show sensitive" box in
<input name="search-settings-nsfw" checked="" class="SearchSettings-toggleInput SearchSettings-toggleInput--sensitive" type="checkbox">
click "submit" in <button id="settings_save" class="EdgeButton EdgeButton--primary EdgeButton--medium" type="submit" disabled="">Save changes</button>

It isn't designed to scrape accounts with sensitive contents.

@justinlittman but it can be modified to do so, as it uses Selenium. All it has to do is login, no?

Yes, I believe so. However, I don't believe that you can hydrate protected tweets from Twitter's API (though I could be mistaken).

I think you can hydrate protected tweets from API if your account follows the protected account (but i'm also not sure about this and need to double check in case this changed).
Protected tweets don't appear at all in searches though, so you can't display from:protected_account.
It is possible to "login" and get tweets that may be hidden as "sensitive" - I have that half working in my fork.


Underrun every START_FILL frames when writing to pipe

First off, nice work on Shairport!  My setup, all running on the same macbook pro:
iTunes connecting to shairport,
shairport writing to a named pipe at /tmp/shairport,
another terminal running "cat /tmp/shairport > /dev/null".
Every 2 seconds or so I would get an underrun.  It was way too regular to be any kind of network problem -- it was like clockwork.  So I added some debugging to hairtunes.c and this is what I found:
underrun: ab_read = 47011, buf_fill = 0
buffer_put_packet: done buffering
underrun: ab_read = 47293, buf_fill = 0
buffer_put_packet: done buffering
underrun: ab_read = 47575, buf_fill = 0
buffer_put_packet: done buffering
underrun: ab_read = 47857, buf_fill = 0
buffer_put_packet: done buffering
underrun: ab_read = 48139, buf_fill = 0
buffer_put_packet: done buffering
Notice how ab_read increases by START_FILL==282 every time.
This does NOT happen if I'm using the libao to send audio to the sound card.

I am seeing underruns - are these real errors or just a cosmetic/debugging artifact?  I ran a Wireshark capture of the received RTP stream from iTunes and ran a stream analysis - the received RTP stream is pretty clean - no jitter. The debugging from shaitunes.c correctly spits out "missing frames" - and these match up with the Wireshark analysis. But I see
I hacked out all the ao code for debugging, so I know the underruns have nothing to do with the sound hardware.
(FWIW, I was getting segfaults with libao/pulseaudio to udp output).
The perl script pipe seems to be unusable, but with the C version writing directly to a fifo, its working nicely with a liquidsoap script for icecast. The sound seems fine on the receiver. Now if Shairport could send track titles that would be amazing.


Factor out utilities for use in testing, should fix coverity issues.

Signed-off-by: Christopher D. Leary<EMAIL_ADDRESS>

/tmp/workspace/OpenROAD-Public_PR-2801-head/src/utl/include/utl/CFileUtils.h:35:10: fatal error: boost/core/span.hpp: No such file or directory
 #include <boost/core/span.hpp>

/tmp/workspace/OpenROAD-Public_PR-2801-head/src/utl/include/utl/CFileUtils.h:35:10: fatal error: boost/core/span.hpp: No such file or directory
 #include <boost/core/span.hpp>

At first I was thinking the build configuration was incomplete somehow, but turns out the CentOS 7 build uses Boost 1.76.0 which doesn't have span in core: https://www.boost.org/doc/libs/1_76_0/libs/core/doc/html/index.html Will think about the best next step on Mon.

I wouldn't overengineer something that is temporary scaffolding.  Just pass a string or char* & length.

I wouldn't overengineer something that is temporary scaffolding. Just pass a string or char* & length.

This may be a potato poh-tah-to thing, but I do think of this not as "overengineering this one unimportant thing" but more "how is modern C++ written, and can we use naturally-error-avoidant C++ conventions in the OpenROAD code base". Hopefully that makes sense -- if we were to ramp other engineers on the code base I'd want to be able to provide appropriate developer guidance/guidelines in that dimension.

Modern c++ is not written with FILE*.   This code should have its life span measured in months and nobody else should be using it.

My view is that you should always prefer a std vector, array, or string to a raw C-style array unless very specifically justified by a substantial gain in profiling.  This would be my guidance to  new developer on the project.
We have legacy uses but I am not aware of any justified cases in OR so far.  Therefore haven't had any cases where span makes sense to me as a developer recommendation.
Recommendations generally live in https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/docs/contrib/CodingPractices.md.  Cherry wrote it and I generally agree.  Practice #14 aligns with my comments above.
What is your feeling about when span should be used?  Do you agree with the above?

Talking it over a bit with @QuantamHD -- we think if the CI for CentOS used the DependencyInstaller we would have a uniform version of Boost available. Right now it finds 1.76.0 in the system path, but the DependencyInstaller installs 1.80 ( https://github.com/The-OpenROAD-Project/OpenROAD/blob/1a3a873fde8c04d768515a8c72f7ae086e04dd8d/etc/DependencyInstaller.sh#L15 ) -- this is quite similar to the TCL version skew issue we were seeing cause confusion last week -- from https://jenkins.openroad.tools/blue/rest/organizations/jenkins/pipelines/OpenROAD-Public/branches/PR-2801-head/runs/7/nodes/48/log/?start=0
-- Found SWIG: /usr/bin/swig (found suitable version "4.0.1", minimum required is "3.0")
-- Found Boost: /usr/local/lib/cmake/Boost-1.76.0/BoostConfig.cmake (found version "1.76.0")

Can we update the CI to do DependencyInstaller first and then we can assume a uniform boost library version (1.80)? That would enable use of spans and avoid more development-version-skew-based-issues going forward.

@vvbandeira please comment on the boost version in CI.

I'm glad to take a beat to discuss them.  I have the same concerns about span and string_view as they serve a similar goal.
Swig doesn't support them so they can't be used in swig'ed interface.  That means the recommendation on when to use them is more complex.
They are non-owning and therefore error prone.  I understand that you get some efficiency benefit but I prefer safety as a first priority.  The most common use cases to actually get a benefit from them are anti-patterns from my perspective (raw C style string or arrays).
Do you see practical benefit from them in your experience outside of legacy code support?

I'm glad to take a beat to discuss them. I have the same concerns about span and string_view as they serve a similar goal.
Swig doesn't support them so they can't be used in swig'ed interface. That means the recommendation on when to use them is more complex.

I can mostly just speak to Google C++ code, but that Abseil C++ tip gives some of the reasons it's used pervasively here. Any time you have a "borrow" of a contiguous piece of data (mutable or immutable), a span (or const span) is used, because it avoids concretizing the code on an implementation detail that just makes it less reusable (e.g. taking a const vector&). The type itself documents that the lifetime of the data is borrowed from the caller, so people are less tempted to stash away a pointer to it for longer term keeping (as they might with a const vector&), as it also uses value semantics.
For bindings you can define a type map that makes defensive copies for returning outwards, similar to what you would do for a function returning a const vector&. Bindings always have to be more complicated when you return things with derivative lifetimes, spans are not particularly special there vs any other borrowed refs your functions might be returning.

They are non-owning and therefore error prone. I understand that you get some efficiency benefit but I prefer safety as a first priority. The most common use cases to actually get a benefit from them are anti-patterns from my perspective (raw C style string or arrays).
Do you see practical benefit from them in your experience outside of legacy code support?

Things like arenas, or being polymorphic over array vs vector are one use case. Another is that being able to pop off the prefix is O(1) which is not possible with a vector. As a case study, lexers/parsers classically take a view of contiguous characters and chomp off the front, and spans/views are the kind of things that give a natural datatype for safe bounds tracking and checking. Spans often /improve/ safety where people would normally reach for raw pointer/length values that then had to be externally maintained. One of the design goals for spans is that no performance is lost for these benefits.
Spans don't really have much to do with legacy code support, except that they are easy to make / reach for to make things safer if somebody was previously using a broken out pointer/length contiguous data idiom. The XLS project has no legacy code and it has 1.1k uses of span according to sourcegraph ( https://sourcegraph.com/search?q=context:global+repo:^github\.com/google/xls%24+absl::Span+count:2000&patternType=standard&sm=0&groupBy=path ). Honestly it's one of those things you take for granted because it's a nice abstraction and usually not too contentious -- is there a particular bad property we'd be avoiding if we allowed use of boost spans (as are present in Boost 1.80, if we got uniform support for that)?

@vvbandeira I was thinking we could use this PR as a canary for whether the dependencies were set up uniformly in CI (e.g. for Boost 1.80), but if that's not on your short list I'll just work around it in this PR. Let me know if you're thinking it's more "few days" or "few weeks", thanks!

@vvbandeira I was thinking we could use this PR as a canary for whether the dependencies were set up uniformly in CI (e.g. for Boost 1.80), but if that's not on your short list I'll just work around it in this PR. Let me know if you're thinking it's more "few days" or "few weeks", thanks!

ETA tomorrow end of day, early Thursday the latest to have all CI synced.

CI should be up to date now. You need to fix the merge conflict for CI to run. Also it is a good idea to merge latest master to get #2841, without it the CI will fail.

CI should be up to date now. You need to fix the merge conflict for CI to run. Also it is a good idea to merge latest master to get #2841, without it the CI will fail.

Will do! Thanks for the update Vitor.

One review comment note, I copy/pasta'd the unit test procedure from helpers.tcl in the RCX dir to the ODB one just because I'm not sure how imports work in the regression runner TCL setup. If you have guidance on how to avoid the copy/pasta would be happy to fix it.

Just an explicit ping on that last request for comment @maliberty but no rush.

There is already a version in test/helpers.tcl. I imagine the one in odb is left over from when it was an independent submodule and should be removed (along with your copy).

Ok turned helpers.tcl in the ODB subdir into a symlink to top level $OR/tests/helpers.tcl which required hoisting a few of the helpers that were depended upon in ODB tests. Hope that was what you were saying, PTAL.

Just for posterity: one issue was that this was needed on the Centos7 build:
if {[package vcompare [package present Tcl] 8.6] == -1} {
    proc lmap {args} {
        set result {}
        set var [lindex $args 0]
        foreach item [lindex $args 1] {
            uplevel 1 "set $var $item"
            lappend result [uplevel 1 [lindex $args end]]
        }
        return $result
    }
}

Just FYI, Ath__parser is another one on my list of things we should get rid of eventually.


Fixes formatting on android due to keypress not working

👏 thank you!

Only fixes card number. The issue is still there for expiry.


Fix typo in README

Fix small typo in README.md
Thank you for the time you are putting into AlaSQL!

Codecov Report

Merging #1131 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1131   +/-   ##
========================================
  Coverage    70.68%   70.68%
========================================
  Files            1        1
  Lines        14201    14201
  Branches      4790     4790
========================================
  Hits         10038    10038
  Misses        4163     4163

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 dd08758...31a8b88. Read the comment docs.


Show benchmarks logs

It's useful to see the benchmarks logs when the benchmarks are running or failed (or just if someone wants to reproduce the results and see what have been built). Currently these logs are not accessible.

Fixed by #20 You can now see the logs on the frontend.


feat: add machine type param to gke cluster builder

Related: https://github.com/Kong/kubernetes-ingress-controller/issues/3555

@czeslavo PTAL again. I forgot that rebasing with Github UI doesn't sign the commits 🤦


Updateable help is putting metadata files in $PSHome which prevents clean uninstall

Steps to reproduce
Install beta.2
Update-Help
Uninstall beta.2

Expected behavior
c:\program files\powershell\6.0.0-beta.2 folder to be removed

Actual behavior
folder remains with a bunch of helpinfo.xml files

Environment data

Name                           Value
----                           -----
PSVersion                      6.0.0-beta
PSEdition                      Core
GitCommitId                    v6.0.0-beta.3
OS                             Microsoft Windows 10.0.16225
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Is this still a problem? Update-Help seems to put files in ~\Documents\PowerShell\Help now.

@sdwheeler Can this issue be closed?


Revert port forward logging

It seems the proposed logging solution is bugged and cause race conditions

/lgtm
/approve

/retest


fix pod pile update

Fix pod bug (did not update pile with ips for short sessions)
Fix documentation and config files to refer to 0.6

closing to refresh easyCLA

cc @psschwei , please approve

/cherry-pick release-0.6


[SC-907] VelocimeterV2 on Base

deploy VelocimeterV2 oracle
fix SolidlyOracle
redeploy MultiSwitch on zksync

Codecov Report
Patch coverage: 73.91% and project coverage change: -0.07% :warning:

Comparison is base (0950952) 77.83% compared to head (58ce0c2) 77.77%.
Report is 9 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
- Coverage   77.83%   77.77%   -0.07%
==========================================
  Files          26       30       +4
  Lines         731      765      +34
  Branches      156      158       +2
==========================================
+ Hits          569      595      +26
- Misses        162      170       +8

Files Changed
Coverage Δ

contracts/oracles/SolidlyOracle.sol
0.00% <0.00%> (ø)

contracts/oracles/SolidlyOracleNoCreate2.sol
0.00% <0.00%> (ø)

contracts/wrappers/Wrapper.sol
81.81% <81.81%> (ø)

contracts/wrappers/BaseCoinWrapper.sol
100.00% <100.00%> (ø)

contracts/wrappers/ChaiWrapper.sol
100.00% <100.00%> (ø)

contracts/wrappers/SDaiWrapper.sol
100.00% <100.00%> (ø)

contracts/wrappers/WstETHWrapper.sol
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Refactor API

This is preliminary work on simplifying the API. The major (breaking) change is a new test-run event that passes an emitter for that specific test run. Said emitter is an instance of the new TestData class (might be more appropriately named TestRun). This contains test results that we were storing directly on the API instance. That really doesn't make sense anymore given that the API instance is called multiple times by Watcher. I feel this way makes a little more sense. There is definitely room for further refactoring, but this represents a big diff, and I want to get it reviewed and merged before further refactoring.

This contains test results that we were storing directly on the API instance. That really doesn't make sense anymore given that the API instance is called multiple times by Watcher. I feel this way makes a little more sense.

Yea that's always stuck me as strange.
Note though that the reporters reference these properties. Their tests use a stubbed api so they're still passing.

Said emitter is an instance of the new TestData class (might be more appropriately named TestRun).

RunStatus?

I set reporter.api to the new testData instance with each test-run event.
I added a to-do comment that that should be cleaned up. I might just change it to pass testData as a param to reporter events. Some reporters could be stateless that way.

I might just change it to pass testData as a param to reporter events. Some reporters could be stateless that way.

:+1:


Python extension loading...

Type: Bug
Upgraded to last version today and have multiple notifications related to Python.
The "Python extension loading..." never ends
Extension version: 2022.20.1
VS Code version: Code - Insiders 1.75.0-insider (79c4f9b75db3b4f50468fc022cacf8ba6d640aff, 2023-01-05T05:21:10.552Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.73GB (13.73GB free)

Process Argv
--crash-reporter-id 6272d00f-39e8-4d45-bc5c-632f1453b2e9

Screen Reader
no

VM
0%

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vsdfh931cf:30280410
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vscaac:30438845
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
pylantcb52:30590116
pyindex848:30611229
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12:30622696
fim-prod:30623723

I also have this problem. Possible regression of #6863 and/or #16026.

@jzvikart See https://github.com/microsoft/vscode-python/issues/20247.

@stenaksel We would need the following logs:

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXXX

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Try adding "telemetry.telemetryLevel": "off" in User settings and see if it fixes the issue.

@karrtikr just upgraded to the new release, and now I'm getting this error for the Python extension as well.
"telemetry.telemetryLevel": "off" doesn't appear to work, and trying to enable source map support yields another error

Here's my console output: vscode-app-1675368883556.log
Python output is just this:
Telemetry level is off
Experiments are disabled, only manually opted experiments are active.

I have the same issue since updating to VSCode v1.75 and the latest version of the Python extension.

FYI switching to the pre-release version of the extension fixes it

We just released a stable version of Python extension:

Please try that.

Yes, reinstalled it to this version and everytyhing is fixed, thanks

I can confirm that the new version works on my system as well. Thanks @karrtikr for the quick response!

That's great, glad you got it working!


Webpack breaking vuex

Bug report
What is the current behavior?
Vuex breaks and throws error:
Uncaught TypeError: Cannot assign to read only property 'watch' of object '#'
If the current behavior is a bug, please provide the steps to reproduce.
import vue and import vuex;
What is the expected behavior?
No error
If this is a feature request, what is motivation or use case for changing the behavior?
Mac
Webpack 4.0.1
Vue 2.5.13
Vuex 3.0.1

Do you have a repository to reproduce the issue?


Schedule with backend v2

Summary
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

64 of 80 (80.0%)  changed or added relevant lines in 9 files are covered.
23 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.03%) to 85.865%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/scheduler/config.py
0
1
0.0%

qiskit/compiler/scheduler.py
16
19
84.21%

qiskit/scheduler/lowering.py
15
18
83.33%

qiskit/compiler/sequencer.py
10
19
52.63%

Files with Coverage Reduction
New Missed Lines
%

qiskit/scheduler/config.py
2
66.67%

crates/qasm2/src/lex.rs
3
90.89%

crates/qasm2/src/parse.rs
18
95.74%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
73065

Relevant Lines:
85093

💛  - Coveralls

Hi @to24toro, I'm also studying in area that needs schedule function and reached to this end of your work. You seem to have changed a lot in qiskit/pulse.
I tried the last branch of yours(feature/schedule_with_backendV2) and still came up with some issues of NoneType in meas_map.
I assume that I connected wrongly with my current qiskit well. It would be great if you leave the comment of whether current branch is working well or not. Also, if you are okay, I'd like to hear and participate in your progress. Thanks for the work.

@sungwooahn
Thank you for your contribution. Could you please share your code with gist or anything else? I would like to check it.

https://github.com/Qiskit/qiskit/pull/10988 solve the bug of scheduling with backendV2.
This PR includes an additional improvement but it is the minor change for the edge case of U gates.
So I close it once.


Complete Example Project

hi this is the only package i'm really needed, but im blind on how to use it, so can you give me a complete example of using it, the example tab on pb dev doesn't give me anything so, if u could do that i really appreciate it

i think you can check this one 🤔  https://github.com/ekasetiawans/flutter_bluetooth_printer_plugin/tree/master/packages/flutter_bluetooth_printer/example


[SR-12646] Ambiguous type name error in Module Interface

Previous ID
SR-12646

Radar
rdar://problem/62202466

Original Reporter
leavez (JIRA User)

Type
Bug

Attachment: Download

Environment
Test on xcode 11.4 and Swift toolchain snapshot 2020-04-19

Additional Detail from JIRA

Votes
0

Component/s
Compiler

Labels
Bug, ParseableInterfaces

Assignee
@slavapestov

Priority
Medium

md5: 61fa54ea5c7a0723325eb34c5b8b74da

Issue Description:
Problem
The generated module interface file below will got an error when parsed by xcode.

// swift-interface-format-version: 1.0
// swift-compiler-version: Apple Swift version 5.3-dev (LLVM 5e4413896d, Swift f0df46771f)
// swift-module-flags: -target x86_64-apple-ios8.0-simulator -enable-objc-interop -enable-library-evolution -swift-version 5 -enforce-exclusivity=checked -Onone -module-name A
@_exported import A
import Foundation
import Swift
public protocol Pt {
  typealias AnotherName = Swift.String
}
@_hasMissingDesignatedInitializers public class Name<T> : A.Pt {
  public typealias AnotherName = Swift.Int
  public func hi() -> A.Name<T>.AnotherName
  @objc deinit
}

("A" is the name of the framework)
Source code
public protocol Pt {
    typealias AnotherName = String
}

public class Name<T>: Pt {
    public typealias AnotherName = Int
    public func hi() -> AnotherName {
        return 0
    }
}

Steps to Reproduce

build a framework with the source above, with "Build Libraries for Distribution" enabled

delete the .swiftinterface files in the framework

add the generated framework to another project, import and build

Why Important
The module interface cannot be used , which means module stability never achieve its goal.

If I change the source code to reference AnotherName as a member of Name, I get the same error:

This appears to work as expected now. Closing.


Nested Grouping

Hi all,
This script accomplishes 95% of what I need, so it sucks that I can't figure this one out.
Problem:
When looking at Nested Lists, I can't figure out a way to create new "parents".
Even the demo fails at this.
Try making item 1.3. a child of item 1.2. and it probably won't work, unless I'm missing something really obvious.
I can move child items out of their parent containers, as I can move child elements into grandchild positions, but I cannot seem to create new parents,
Help?
Thank you.
JSBin/JSFiddle demonstrating the problem:
https://sortablejs.github.io/Sortable/#nested

@dumitrub Hi, this is because the items that start off as empty do not contain a Sortable container within themselves.
It is as simple as creating one yourself: https://codepen.io/owen-m/pen/pXQoEv?editors=1010
In that codepen, you can drag into any of the items - even the ones that start off as empty. You might have to play a bit with swapThreshold and emptyInsertThreshold to get a more desirable effect, I tried my best in the codepen to make them work.

Wow... 🤦♂
Thank you! Now it works.

Yay, an isolated code sample... Your guys' "documentation" on nesting is severely lacking...


ImageSlideshow in Swift 2.2

Hello, I would like to use your framework (version 0.6) in a project made in Swift 2.2 but when I try to compile the program, it gives me a bunch of errors. It seems like there are a syntaxis errors. Could you help me, please?
Thanks in advance!!

Hi, I tested it now on Xcode 7 / Swift 2.2 using pod 'ImageSlideshow', '~> 0.6' and it compiled correctly. Please check you're declaring this in Podfile correctly. Also make sure you have the latest CocoaPods version installed.


GitOps Run - Replicate vcluster connect behavior in WGOSS

Blocks #3434
In the current implementation, the vcluster connect command is directly imported from the vcluster v0.12 package to enable session mode in WGOSS.
However, we recently encountered an issue when trying to upgrade Flux to v0.40 and API machinery to v0.26.1, which broke the vcluster v0.12 package. To unblock this dependency management for now and future versions, we need to replicate the behavior of vcluster connect in WGOSS. This will ensure that session mode continues to function properly and that we can upgrade our dependencies without breaking any functionality.
User story
As a user of WGOSS,
I want to be able to use session mode with the latest versions of Flux and API machinery,
so that I can benefit from the latest features and improvements while also ensuring that my software stack is up to date.
Acceptance Criteria:

The new implementation should be backward-compatible and should not break existing session mode functionality.
Session mode should be able to work with the latest versions of Flux and API machinery without any issues.
The behavior of the replicated vcluster connect command in WGOSS should match the behavior of the original command from the vcluster v0.12 package.

Resource: https://raw.githubusercontent.com/loft-sh/vcluster/main/cmd/vclusterctl/cmd/connect.go


Functions not deploying

I have a function that I am using as a Hasura action. Everything works as expected locally, using the CLI, however when the project deploys in the cloud the functions do not get built.
I am I doing something wrong? Or is there somewhere I can see detailed deployment logs?
Version: Nhost CLI v0.6.12 for darwin-amd64
Functions located in functions directory:

Deploy occurs after committing to repo, but no functions were built:

No functions listed:

Server returns generic error, if I change the function name to gibberish I get the same error message returned:

It works when running locally:

I'm not on your machine but I suspect your problem is that you're including code from a shared folder locally that isn't in the repo you're syncing to NHost.

I'm not on your machine but I suspect your problem is that you're including code from a shared folder locally that isn't in the repo you're syncing to NHost.

@pkreipke thank you for chiming in! That shared folder is part of the repo.
It not directly in the api directory though, which is where nhost is, maybe that is the issue?
VS Code:

GitHub:

I copied the generated directory and import from there instead, but that still did not work.

Out of an abundance of caution I named all my utility folders, subfolders and files with a leading prefix. I haven't tracked down the code to see if that's necessary (e.g. do files inside a _... folder need a prefix too?).
E.g. in your screen above I would have named useQuery.ts as _useQuery.ts. I'm hoping this is not necessary for exactly the reason you're find above (copying a large quantity of files over).
Have you tried a simple function with just a few sample imports with a mix of _ as you have above to see if it gets deployed?
Otherwise you may need to get on Discord and ask for some quick help from an NHost person to track down deployment logs.

This isn't promising:

@pkreipke I figured out what the issue is. The issue is that nhost is not building functions found in a subdirectory. Migrations and metadata are picked up, but functions are not.
Does NOT work:

Does work:

Base directory is set:

There are two bugs in this issue, and I've been able to reproduce both.
1. Functions are not built when using a subdirectory

The issue is that nhost is not building functions found in a subdirectory. Migrations and metadata are picked up, but functions are not.

2. CLI doesn't skip endpoints for _ file/folders.

@joserocha3 the fix has been rolled. Please re-trigger your deployment and let me know if it worked.

@joserocha3 thanks for reporting and sorry for this happening. The problem is that our system installs dependencies from the root dir, not from the base dir where nhost and functions are located. The fix is coming very soon...

@elephant3 thank you for the explanation. I have copied the dependencies to a package.json in the repo root and the deploy works. Although, it is not ideal.

@joserocha3 please check now, it should pick up package.json from the base dir

@elephant3 it failed with the below message:

Shouldn't fail due to no license. Or maybe there is another error not shown in the logs?

Oh, I think it might be because I have package.json in the repo root, and in the base directory. Could it be seeing the repo root package.json and attempting to process it?

@joserocha3 I assume your base directory (configured in the Nhsot Dashboard) is: ./api?

@joserocha3 I can confirm from server logs that the api/package.json was used

@joserocha3 I found the issue, the fix is coming...

I your base directory (configured in the Nhsot Dashboard): ./api?

@elitan yes, it is

I found the issue, the fix is coming...

Awesome 👍🏼 thank you @elephant3, if you still need the file contents let me know

@joserocha3 please re-trigger now and let me know if everything is fine

@joserocha3 awesome!


WebCam is not access by using Java in MAC ventura  version

i am trying to access webcam  using javafx in my project in mac ventura and catlina version.but to unable to get access plz tell me the solutions.

Try this https://github.com/eduramiba/webcam-capture-driver-native
It's a native driver that I have tested with all recent MacOS versions

i have setup this code in my STS IDE it can get webcam list but unable to open webcam.Facing webcam locked issue and other app does not access webcam during the execution of project.

i am trying to access webcam using javafx in my project in mac ventura and catlina version.but to unable to get access plz tell me the solutions.

please use OpenCVFrameGrabber to capture the image


Optimize cell cleanup routine

So, -_cleanupCells gets run zillions of times during scrolling. I've replaced it with a version that runs almost twice as fast (the old one averaged about 1.2ms on my iPhone, whereas the new one averages around 0.7ms).
The main deal was that I replaced the nice high-level enumeration and filtering with an array of structs (effectively the tuple type (KKGridViewCell*,KKIndexPath*). I'm sure everyone knows that you're not supposed to store Objective-C objects in C structs (unless you're using C++); this is because ARC won't know how to manage their memory. But for these objects, we know that they're already owned (by the _visibleCells dictionary); so, we can mark the pointers __unsafe_unretained, and ARC is happy. And we get a fast collection of cell/path pairs that we can deal with.
Let me know if you have any concerns or questions.

For obvious stuff like this Jon, you can pull right into the main repo.  You're permissioned.
Sent from my iPhone
On Dec 17, 2011, at 10:26 PM, Jonathan<EMAIL_ADDRESS>wrote:

So, -_cleanupCells gets run zillions of times during scrolling. I've replaced it with a version that runs almost twice as fast (the old one averaged about 1.2ms on my iPhone, whereas the new one averages around 0.7ms).
The main deal was that I replaced the nice high-level enumeration and filtering with an array of structs (effectively the tuple type (KKGridViewCell*,KKIndexPath*). I'm sure everyone knows that you're not supposed to store Objective-C objects in C structs (unless you're using C++); this is because ARC won't know how to manage their memory. But for these objects, we know that they're already owned (by the _visibleCells dictionary); so, we can mark the pointers __unsafe_unretained, and ARC is happy. And we get a fast collection of cell/path pairs that we can deal with.
Let me know if you have any concerns or questions.
You can merge this Pull Request by running:
git pull https://github.com/jonsterling/KKGridView optimize_cleanup
Or you can view, comment on it, or merge it online at:
https://github.com/kolinkrewinkel/KKGridView/pull/78
-- Commit Summary --

Replaced -_cleanupCells with an optimized version

-- File Changes --
M KKGridView/KKGridView.m (27)
-- Patch Links --
https://github.com/kolinkrewinkel/KKGridView/pull/78.patch
https://github.com/kolinkrewinkel/KKGridView/pull/78.diff

Reply to this email directly or view it on GitHub:
https://github.com/kolinkrewinkel/KKGridView/pull/78

Will do in the future. Thanks, Kolin!

Not a problem. :)
Sent from my iPhone
On Dec 17, 2011, at 10:29 PM, Jonathan<EMAIL_ADDRESS>wrote:

Will do in the future. Thanks, Kolin!

Reply to this email directly or view it on GitHub:
https://github.com/kolinkrewinkel/KKGridView/pull/78#issuecomment-3193455


SDK Release Readiness

This epic is for requirements for SDK Release readiness milestone.

[ ] https://github.com/Azure/azure-sdk-tools/issues/5087
[ ] SDK Release Readiness UI in the re-designed SDK Release app - https://github.com/Azure/azure-sdk-tools/issues/5632

I imagine the requirements covered in #5087 will be part of the UX enhacements design which is already an epic. @ladonnaq  you open to closing this?

I imagine the requirements covered in #5087 will be part of the UX enhacements design which is already an epic. @ladonnaq you open to closing this?

This is the epic to track the requirements.  https://github.com/Azure/azure-sdk-tools/issues/5087 is a requirement.

I added the automation status to the first comment of this issue.


Capture Users Last Loot

Description:
When getting loot via bank images, it can be hard to discern what it is that has been received if you don't recognise the item. To combat this I've added a entry in the DB which tracks what the last loot that was added to the users bank was, excluding impling captures. This can be returned by a new /minion command last_loot in 3 different formats:

Text - Text string of loot, strings over 500 characters are sent as .txt instead
Names - Bank image with names
Image - Bank image as normal

Changes:
Add lastLoot entry to Prisma Schema and UserSchema
Add LastLoot option for UserSettings
Updated addItemsToBank function to track the last received loot in the aforementioned field, only if it's not a impling capture.
Add a command to /minion called last_loot which returns the loot in 3 different formats mentioned above.
Other checks:
Checked it with a large amount of commands and all loot seems to be appropriately tracked.

[x] I have tested all my changes thoroughly.

Bump pls 🙏

Don't plan on adding this currently, sorry.


Add Traveler normal attacks to optimization targets

Fix #641 - Add Traveler normal attacks to optimization targets

Oops, I submitted my review for the wrong PR. This is borked af, optimize button throws numerous errors and no builds are ever returned for any character, any optimization target
Or something is wrong with my dev environment, not sure

Hm jk it happens on any branch for some reason, even after npm install

Left comments

where?


google::protobuf::FatalException

Hello,
while running the Demo I receive an FatalException from Google Protobuf. Did anyone before solved this issue?
Thanks for help!
python3 main.py
Open camera...
[ WARN:0] global /home/nvidia/host/build_opencv/nv_opencv/modules/videoio/src/cap_gstreamer.cpp (933) open OpenCV | GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
<VideoCapture 0x7f56cabb50>
Build transformer...
/usr/local/lib/python3.6/dist-packages/torchvision-0.8.0a0+45f960c-py3.6-linux-aarch64.egg/torchvision/transforms/transforms.py:280: UserWarning: The use of the transforms.Scale transform is deprecated, please use transforms.Resize instead.
"please use transforms.Resize instead.")
Build Executor...
/home/kea/temporal-shift-module/online_demo/mobilenet_v2_tsm.py:95: TracerWarning: Converting a tensor to a Python index might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
x1, x2 = x[:, : c // 8], x[:, c // 8:]
[libprotobuf ERROR google/protobuf/descriptor_database.cc:57] File already exists in database: onnx/onnx-ml.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1164] CHECK failed: generated_database_->Add(encoded_file_descriptor, size):
terminate called after throwing an instance of 'google::protobuf::FatalException'
what():  CHECK failed: generated_database_->Add(encoded_file_descriptor, size):
Aborted (core dumped)

I am seeing a similar problem
Followed the instruction at https://github.com/mit-han-lab/temporal-shift-module/tree/master/online_demo to install the demo on a Jetson Nano
Worked through all of the dependencies.

Same error here, is there any solution,?
thanks


In a container, sshd should not run as root

Add the option to choose the owner of configurations files and their locations.

I am not sure how to handle the groups though. https://github.com/dev-sec/ssh-baseline/blob/micheelengronne-patch-2/controls/ssh_spec.rb#L37

@artem-sidorenko is it ok for you ? Is there smthg I did wrong ?

@chris-rock is it ok to merge ?

Yes. In the case of a sshd server in a container, the root user should not be used as a container process should not run as root.
In that case, it is not very good to use a reserved root path like /etc/ssh to store configurations.
There is no clear definition of where a configurations ssh folder should be present when a non root user runs sshd. The sshd command is called with the -f flag in that case.
HOME/.ssh is used for the ssh keys and not the configurations. The 2 should not be mixed as they have a different lifecycle (the ssh keys are alterable during the container life, the configurations not).
As there is no clear definition, I think each user should have the choice.

Thank you. Can you trigger a release please ?

Just out of curiosity: does this mean that the container ensures the security of the host here? If yes, wouldn't this miss the point of privilege separation and, well, containment?
In other words: If the container is not secure once a process therein attains root privileges, then the container is just not that secure and should rather be run unprivileged, no?

The problem is that unprivileged in the container world (particularly docker, less for podman) is not so unprivileged.
/etc/passwd is shared with the host as many other system files. So if your process runs as root in container, it can be considered as running as root (with some restrictions but still) in the host. That is a security risk.

It is generally a bad pattern to write a CMD without specifying a USER first.

Thanks for the explanation.
Sorry in case I am missing obvious things here, as I primarily use LXC/LXD. If the container is within a user namespace (uidmap/gidmap), the container should never be able to run a process with the host's uid 0 (however, a process can be run with the container's uid 0, but that is mapped). This should be independent from what files are shared with the host (except maybe the Docker configuration and its control socket, you get it), as far as I understand.
But we don't need to get too philosophical here. I just wanted, for the record, to raise the concern about the container's containment qualities if a root process therein threatens the host security (as in: running nothing as root inside the container is the wrong thing to fix).

for some references:

https://neoteric.eu/blog/docker-containers-with-root-privileges/
https://medium.com/@mccode/processes-in-containers-should-not-run-as-root-2feae3f0df3b

The problem is that the main used container provided is docker and they made some wrong choices for their project.
The docker daemon is generally run as root (and is a daemon). uid are not mapped but shared so uid 0 is really root in the host.
Podman fixed these problems but is not very widely used. It is compatible with docker. I would generally advice to use podman over docker when possible.


Add shadow root support for isInDOM function

@matpl What does this fix?

I was trying to use Monaco Editor from within a web component with a shadow root, and the isInDOM check would fail and the editor wouldn't be rendered. It's because the parent of a shadow root node is found in the "host" property, and not "parentNode". This fix makes sure the isInDOM function can climb up the visual tree until it reaches the body node, even when there are shadow roots in the page.


Bump to v0.25.3

It looks like this includes the removal of integration testing from forc test which is quite breaking for those who were previously using forc test - should we consider a bump to 0.26?

It looks like this includes the removal of integration testing from forc test which is quite breaking for those who were previously using forc test - should we consider a bump to 0.26?

True! Thanks for pointing that out. Let me update the PR.


Minification issue with at-keywords that are not rulesets

Given input like:
@import url("foo");
html {
  color: red;
}

Output will look like this:
@import url("foo")html{color:red;}

At the lexical level, the output is valid. But at the syntactic level, the production for an at-rule does not terminate until either a complete block is seen or a semicolon (outside a block) is seen. Therefore, @import url("foo")html{color:red;} is actually interpreted as a single (unrecognized) at-rule, terminating at }.
https://www.w3.org/TR/css-syntax-3/#consume-an-at-rule
As a result, both Chrome and Firefox (didn’t test others) correctly consider the resulting stylesheet to have no rules. Adding the semicolon fixes it. This is true regardless of whether the specifier portion is provided as an actual URL token (bare string in parens), functiontoken+string+paren, or string.

@thysultan can this be a bug in the rule-sheet plugin?

Yes it is... published a patch for it.

Fixed #358


UserProvider Causing Page Rerender on Sign-In Check

The UserProvider component, responsible for verifying user sign-in status, is triggering unwanted page rerenders upon completion of the loading phase. This behavior occurs as the UserProvider assesses whether the user is currently signed in. Consequently, the entire website undergoes a complete rerender post the loading phase, causing unnecessary performance impacts and disrupting user experience.
Proposed Solution
One potential solution to prevent the complete rerender after the UserProvider's loading phase is to implement an animation that hides the website content until the UserProvider completes its sign-in check. This method aims to mask the visual impact of the rerender by concealing the elements until the necessary verification is done.
This issue is critical for maintaining a smooth user experience and overall website performance. Any assistance, insights, or contributions to resolving this issue would be highly appreciated.
Screenshots

after review, the issue came from the products grid #23 / #61
@medshk please check


feat: Display the Account Balance

This PR adds a simple component to display the selected account.

When I use "Remove Account" and click the user, it shows an error:


New image: Cowsay

Chainguard Images Pull Request Template
Image Vulnerabilities

[x] The Grype vulnerability scan returned 0 CVE(s).
[ ] The Grype vulnerability scan returned > 0 CVE(s) (please explain in the notes).

Duplicate


can we integrate opentest with CircleCI?

OpenTest version number: X.X.X

Steps to reproduce:

(describe step 1 here)
(describe step 2 here)

Relevant log information:
(paste log contents here)

Yes, you can. Sadly, there isn't a lot of great documentation around integrations like this.

Please watch part 4 of the tutorial here that talks about Jenkins integration, as it'll teach you most of what you need to know (except the CircleCI specifics). Any type of CI integration will of course be specific to the particular CI tool, but the basic workflow is the same:

Run the opentest session create command in your CI pipeline to kick off the tests and output the results in the JUnit XML format.
Feed the JUnit XML to to your particular CI tool to read the test results.


Difference between CNV signature from SigProfilerAssignment and SigprofilerExtractor

Hello! I used a sequenza segment file containing 60 samples and ran it through both SigProfilerAssigment and SigProfilerExtractor. They gave me very different results. SigProfilerAssigment's result had samples matching all 24 Cosmic CN signatures, but according to the decomposed results from Sigprofiler extractor there are only 8 cosmic CN signatures 2 de novo signatures. Why did the two packges gave such different results?  Thank you so much for your time!

Hi @TgenJZhang,
SigProfilerExtractor and SigProfilerAssignment are doing different things. SigProfilerExtractor decomposes de novo signatures into cosmic signatures, and both de novo and cosmic signatures are used for assignment. This is different from SigProfilerAssignment's cosmic_fit, which assigns cosmic signatures to the samples.

I see. Thank you for the reply!


Remove procedure to explicitly open port 28100

Describe your changes in brief
The documented step is unnecessary and needs to be removed.
Changes

[ ] This change is required to remove the unnecessary user step to update firewall port config
[ ] The port removed is taken care of by Provisioner state for firewall config

How Has This Been Tested? (Optional)

[ ] Tested with OVA.
[ ] Removal of unnecessary additional execution step would improve user experience

Screenshots (if appropriate)
Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Closing for a newer one: https://github.com/Seagate/cortx/pull/822


Latest changes breaking rest api and core views on parse.com due to addition of _PushStatus in _SCHEMA

Background: We are slowly migrating over to parse-server from parse.com.  Current implementation is mongoDB migrated to mLab with both parse-server and parse.com running on the same mLab DB instance.   We need to be able to run both in parallel.
Issue: Recent code changes in parse-server is causing issues with parse.com,  particularly with pushes through rest api and even trying to view core collections on parse.com dashboard.  The following error message is thrown:
{"code":103,"error":"Invalid classname: _PushStatus, classnames can only have alphanumeric characters and _, and must start with an alpha character "}
Cause: This occurred after updating parse-server with latest commits and then sending a push notification through parse-server.  From what I found, parse-server is adding the following entry to the _SCHEMA collection:
{
    "_id": "_PushStatus",
    ...
    "failedPerType": "object"
}

While this works fine for parse-server, this is causing parse.com to completely break.  Removing _PushStatus entry from _SCHEMA fixes this and parse.com dashboard and API works.

@alanphoon can you please post the logs that happen on parse-server when parse.com is trying to send the push to it when running in VERBOSE=1?

This is parse.com breaking, not Parse Server. We should either revert that PR, or hold off on releasing 2.2.8 until we have a better solution. Maybe we can use a different collection name for the new system schemas, so Parse.com doesn't see them, but Parse Server does.

@flovilmart As per @drew-gross  comments,  no logs as parse.com is breaking not parse-server.  Let me know if you guys need anything else.  Thanks.

oh shit.... so remove the _PushStatus from the reserved classes?

I say keep in in reserved classes and either have the mongoAdapter have a check and not create anything that isn't one of the known special classes, or have it create it in a different collection. I do think the ideal behaviour is to have _PushStatus be a Parse Object, so if we can move towards that being true while also not breaking Parse.com that would be sweet.

yeah, I'd skip the creation altogether, but not in the adapter, as the problem may surface with other adapters.

Other adapters probably wouldn't be used if you are still using Parse.com. Once we extract the current adapter we can call it LegacyMongoAdapter and have it do all sorts of crazy shit to be compatible with Parse.com, and recommend new projects use MongoAdapter which will actually be consistent and do things that make sense (if it ever exists...)

uhm ok, I'll check it out

fixed by #1636

If I understand it right, this issue should not be present anymore in current version 2.2.16 , correct ? However I am seeing this in my AWS EB deployment. Once a push is sent from parse-server, _PushStatus appears in the _SCHEMA collection and dashboard.parse.com breaks  with:
{"code":103,"error":"Invalid classname: _PushStatus, classnames can only have alphanumeric characters and _, and must start with an alpha character "}
Also, pushes from parse.com do not go through anymore, while pushes from parse-server are ok. After removing the _PushStatus document from the _SCHEMA collection, the problem goes away and pushes from parse.com succeed once more, until another push is sent from parse-server.
This is the only thing now holding us back from fully migrating to parse-server.

@grd888 @flovilmart I'm hitting the same problem and it is also the last thing holding us back from fully migrating. Did you end up finding a solution???

@sprabs I ended up rolling back to 2.2.7, which does not exhibit this issue. Once I get sufficiently enough clients upgrade their mobile apps to the version that uses parse-server, that's the time I will consider moving parse-server to the latest versions.

If you use parse-dashboard, is it all ok?

@flovilmart: I mean, the bigger issue is that push notifications fail when sent from any clients still using parse.com (which would be a number of clients in the month or so that our users transition via force update).

Copying my comment from https://github.com/ParsePlatform/parse-server/issues/2275
@flovilmart I checked the commit you added to fix the issue in April. I noticed that in the latest code, part of that was lost. I have done a point fix on my side and am still testing. It's just a single line in src/Controllers/DatabaseController.js from: #1636
Would incorporating that change back in solve the _PushStatus problem or does more need to be done?


MisalignmentFlex and MisalignmentRigid do not run for rotors with less than 2 disks

I was running some examples with these classes to get familiar with them, and when I tried running them using a rotor model with a single or no disk, it returned an error:
Traceback (most recent call last):

  File "<ipython-input-2-37037196aef6>", line 4, in <module>
    response = misalignment_flex_parallel_example()

  File "ross\defects\misalignment.py", line 962, in misalignment_flex_parallel_example
    misalignment = rotor.run_misalignment(

  File "ross\rotor_assembly.py", line 2589, in run_misalignment
    defect.run(self)

  File "ross\defects\misalignment.py", line 152, in run
    self.ndofd1 = (self.rotor.disk_elements[0].n) * 6

IndexError: list index out of range

Taking a closer look at .run() function, I noticed these 2 attributes:
        self.ndofd1 = (self.rotor.disk_elements[0].n) * 6
        self.ndofd2 = (self.rotor.disk_elements[1].n) * 6

It requires at least 2 disks in the rotor model.
So, I would just like to clarify if these analyzes deal with misalignment between 2 disks only or it's possible to analyze other scenarios, like no disks or multiple disk, etc.
@verg1lio, @bela-bs, @marcusfilipesr.

Hello Rodrigo, the way the programming was done, yes. We will have to modify some parameters in the code to improve it for arbitrary tests. We'll do that tomorrow.

Hello Rodrigo, the way the programming was done, yes. We will have to modify some parameters in the code to improve it for arbitrary tests. We'll do that tomorrow.


Support MiniScript files (.ms)

It would be great to have a support for MiniScipt files too.
Grey Script is based on MiniScript, and as far as I'm aware, it has no differences compared to the 2021 version of MiniScript.
A simple change would be to include the extension to cover .ms files, but ideally, some changes to autocompletion are needed to make the extension not to suggest GreyHack-only APIs

Hey so when it comes to syntax you are right there are no differences to GreyScript. But there are the following differences:

basic MiniScript intrinsics don't match 100%
GreyScript has "import_code" which is kind of like an ingame on "build" include

Additionally most of the functionality provided by this extension is pretty much focused on GreyScript and probably doesn't have any purpose for MiniScript. I mean I can just add the .ms extension but not sure how much this extension can help with actual MiniScript coding.
But I think it would be pretty "easy" to create a new extension reusing some of the packages used within this extension. Also I am not sure which of the features this extension provides you are looking for?

I see so just wondering which features specifically are we speaking about? Automcomplete, HoverDocs, Diagnostics, Interpreter etc? Just to get an idea which packages are required.
Yeah I think this is specifically the issue. I think there needs to be some decoupling done in order to make this not horrible to maintain.

I'd frame it as "everything that isn't GreyHack specific" like the game intrinsics. The debugger is especially powerful since you can't do that with the official MiniScript implementations.
 But this is also the exact sort of stuff you can decouple from the core interpreter and potentially allow mixing and matching with GreyScript intrinsics.
e.g. when firing up the interpreter/debugger, you have some options defined somewhere to tell it which intrinsics package(s) should be loaded into the script VM.

What is good to have:

Auto formatter (beautify). I have autoformatter in my fork of the extension, but it's regex-based, not actually parsing syntax tree,
Autocomplete. Autocomplete for intrinsics and standard library would be ideal.
Syntax error detection. It's a big one
Interpreter... Not sure, it may be useful for "raw" miniscript, but a lot of use cases are for MiniMicro and so it's probably not very useful
Code bundling. This extension seems to have pretty good bundling capabilities, which are pretty useful outside GH too, to avoid issues with the default MiniMicro import, which behaves more like include

Interpreter... Not sure, it may be useful for "raw" miniscript, but a lot of use cases are for MiniMicro or embedded environments and so it's probably not very useful

Being able to introspect your code, is tremendously useful - create a fake/mock of whatever MiniMicro function(s) you need and fire up the debugger.

I'd frame it as "everything that isn't GreyHack specific" like the game intrinsics. The debugger is especially powerful since you can't do that with the official MiniScript implementations.

I see so that means I need to decouple the lexer, parser, transpiler and interpreter. I mean I could mix them but that would kinda make it probably confusing to work with.
Lexer, parser, transpiler and interpreter are pretty simple to decouple since I would just need to decouple import_code I believe. I also probably need to switch it's dependency order. Since right now it's greyscript-core > greybel-core. So in the future it should be more like miniscript-core > greybel-core > greyscript-core.

 But this is also the exact sort of stuff you can decouple from the core interpreter and potentially allow mixing and matching with GreyScript intrinsics.

Adding intrinsics shouldn't be difficult since that part is already quite decoupled. So for that there would be just new intrinsics packages required and as you mentioned somekind of intrinsic package selection.

Syntax error detection. It's a big one

For this I would probably need to add also an option to select the diagnostics syntax. Since there are some minor differences. So GreyScript for example allows non literal default values in args (which is broken) but still supported.

Code bundling. This extension seems to have pretty good bundling capabilities, which are pretty useful outside GH too, to avoid issues with the default MiniMicro import, which behaves more like include, or for embedded environments that don't have import functionality.

For this I would probably need some input or look into on how the bundling should work for MiniMicro and MiniScript. Are there any differences?

Anyway I am up to do some decoupling if it helps the MiniScript community. I'm just not yet sure on how I am gonna do it. I may going to create a new extension if I see it becomes too much of a hassle to put it into this one. This may gonna take some time though.

I've added .ms as an extension in the meantime https://github.com/ayecue/greybel-vs/pull/98/commits/0d712d3d79306a2e226d6ea0553982f0635905ac. Should be available as soon https://github.com/ayecue/greybel-vs/pull/98 is merged.

Yeah, seems reasonable. On the quick glance, the only thing that is not a part of standard MiniScript is exit with string argument, but that is easily resolved just by defining a polyfill.

Yeah I am currently working on changing the transpiler to only support MiniScript as a default. Everything related to GreyScript will be decoupled into a new package.
Doing the same for the meta and parser/lexer part.
After the transpiler is decoupled I'll then also decouple the interpreter.

Okay I've finished porting greybel-vs to miniscript-vs. It's available here https://github.com/ayecue/miniscript-vs


added frontmatter to release-0.3.1 docs

Signed-off-by: thisisobate<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
Added frontmatter to release-0.3.1 docs

Verification
Works on local

ups, conflict (:

ups, conflict (:

Fixed! @bwplotka


Updated links, Second Class Added, Reveal Accessibility Plugin

I've had a fork of these slides for a while now, so I figured it was time to submit a pull request! I've taught the class two times for Girl Develop It Seattle. Here are some features in the slides:

Accessibility plugin: really hides inactive slide content, dynamically generates skip links for slides
Updated links and content in Class 1
New Class 2: HTML and CSS accessibility, hands-on exercises

Let me know if I need to host images instead of including them. Thanks!

Love some of the stuff you have added! The class 2 slides are very sparse; do you have plans to build out some of the content?

I wasn't planning on it. It could be that my presentation style is different than the original...I tend to create more info-dense slides to use as a reference. I could have left out important details on accident though...things like what I use the Web Developer toolbar for (added to the Headings section). After teaching the whole thing twice, it seemed like a good amount of content.

Okay, I see more content in your branch. Let me double-check to make sure that it is not just a me-merging-wrong issue.

Ahh. Here is a link to the compiled slides: http://marcysutton.github.io/gdi-web-accessibility/
We can certainly make changes to them, I'm not against it! I just don't have as much time to work on them as I'd like. :)

Yeah, when I tried to merge them I got an intermediate version of the slides with only headers and no content. This is much nicer!
Let's see if I can clear the merge conflicts quickly.

On May 5, 2015, at 2:00 PM, Marcy Sutton<EMAIL_ADDRESS>wrote:
Ahh. Here is a link to the compiled slides: http://marcysutton.github.io/gdi-web-accessibility/
We can certainly make changes to them, I'm not against it! I just don't have as much time to work on them as I'd like. :)
—
Reply to this email directly or view it on GitHub.

I tried to get fancy by squashing some commits, which may not have helped. Let me know if you want to pair!

I've got a GDI class tonight where some of our instructors and TAs are GitHub guros. I'm going to attempt the merge with them there to help. I'll let you know how it goes!

Ok great! Please let me know if merging continues to suck, I can just resubmit the PR without squashed commits. Sorry for the trouble!

Hi @Roenok, I have rebased the PR to resolve conflicts. The commits are no longer squashed, revealing a pretty noisy commit history. Let me know if you would like it cleaned up, otherwise this should be good to go!

Very lovely, thanks! I'll go ahead and merge these.

Yay! :tada: Thanks @Roenok!


Floats are possible broken

During working on the List Sort stdlib component I discovered that floats seemingly don't work.
When trying to do anything with them, we receive
Example code:

Output:

This is also an occurance when you use float instead of any and when you use just a float value instead of an array.

fix #538


Error: "Invalid character in header content ["Location"]"

I add octomments to my repo https://github.com/alex-pancho/worm_ru, my github pages with plugin is https://alex-pancho.github.io/worm_ru/001_Глава_1.01.html
When I try send comment I get errror:
{"error": "Invalid character in header content ['Location']"}
Session protocol is:

GET https://ocs.now.sh/octomments/token?redirect=https://alex-pancho.github.io/worm_ru/001_%25D0%2593%25D0%25BB%25D0%25B0%25D0%25B2%25D0%25B0_1.01.html
GET https://github.com/login/oauth/authorize?client_id=Iv1.c929bff56a0bafb5&redirect_uri=https://ocs.now.sh/octomments/token?r=https://alex-pancho.github.io/worm_ru/001_Глава_1.01.html&scope=public_repo
GET  https://ocs.now.sh/octomments/token?r=https://alex-pancho.github.io/worm_ru/001_Глава_1.01.html&code=dc57c93be87d1c8056a0

Hey @alex-pancho,
did you install the Octomments app to your profile and did you give access to worm_ru repo?

yes

can this be related to the use of Cyrillic?

Now when you are saying it. Indeed that could be the reason.

so, you have a task for fixing, I checked and with Latin characters all is well


All code in English

Is very important to maintain the entire code in English lang.
https://github.com/dafiti/correios/blob/master/src/Dafiti/Correios/Entity/Config.php#L19

Somethings should not be in english, so that other colaborators can relate the property with the configuration stated at the documentation.

Correios API was write in portuguese, translate this to english will delegate to programmer more work to find and translate things from correios documentation to our client. About references, "Clean Code, The Bible" say to not do this.


Device Driver and IO manager needs edge triggered and abstraction

To prevent 100% load in application using poll the device driver need to be re-worked to only raise events on poll for  HW TX Empty And TX queue Not Empty for ACTIVE interfaces.
Since the UAVCAN io and multiplexing on the interfaces is handled internally by the io layer and the only interface the application has is to give UAVCAN cpu is spin_xxx there a violation of the encapsulation and abstraction needed by having the notion of interface choice and state managed by the application. There should be only one event used on the FD and it should only be set buy uavcan when the i/o layer can send or receive data.

See the referenced commit. All events are edge-triggered now and treated as POLLIN, so the issue of overlapping events we discussed last Friday is now resolved.
The abstraction issue is also sort of resolved (with caveats): since all events are now edge-triggered, a situation with events being stuck permanently in active state is not possible anymore. Hence, the poll() configuration code that violates abstraction can now be removed from the application. The caveat is that such handling can sometimes cause the library to handle irrelevant events, e.g. the driver will wake up poll() on a TX event, but the library doesn't have anything to transmit.

Waiting for David to test it.

I updated the app code to not check the tx queue and revered the poll to just POLLIN. Tested Working


Add supply chain security using Docker scout

Add to the main workflow docker scout or  Scout Action
docker scout cves ghcr.io/pre-commit-ci/runner-image:2023-09-02-d10dad3-full

these cve scanners are all garbage -- they don't understand debian's policies
there aren't any relevant vulnerabilities anyway as this isn't "exposed" like a traditional application (people would just be sabotaging their own runs)


Is it a working contract?

Is it a working contract? Can be used in a real environment?

I see.
What those features and validation would be, for instance?

For example:

Right now the contract is setup with a deposit and rental terms, but there is no instruction to refund the deposit. Should this happen immediately after the last payment or as a separate transaction, only allowed if the contract is in a complete state?
There is an instruction to TerminateEarly, but under what conditions should that be allowed (or should it be removed?) and how can issue the instruction? Do you need both parties approval or just the owner (payee)?

Hi @BryanMorgan, do you have an example for client side? Thanks :)

Right now I don't have a fully functional client-side example I can share. But I pulled out some of the key capabilities from a client example I am working on and shared it in this Gist. Hopefully that's enough to get you started with the 3 key steps:

Create a rent share account
Initialize the rental agreement with the terms (deposit, rent, duration, keys)
Record a rental payment from a payer to a payee

It uses the @solana/web3.js library along with BN and borsh for big number and binary serialization support:
https://gist.github.com/BryanMorgan/2da2ed2b1ce8371d12812cfc2db6e73b

Thanks @BryanMorgan

But that requires duplicating all those AgreementStatus, RentDuration and other things.... in JS?

No, you don't have to. You don't even have to use a JavaScript/web3.js client. You could write a client in Rust and re-use the same definitions.
But if you're building a web3-based client it probably makes it easier to keep track of the data you're sending in TransactionInstructions if you model the contract schema data in JavaScript.


Update README.md

backgroundremover: error: unrecognized arguments: -gp 4
=> -gb 4

This would be an issue, I saw you opened another one, so I feel they are both related.

As you wish, i thought it was just a typo in the readme, which is why I opened the pull request ;)

Didn't realize you had pushed the change.  Tx.


No output on Linux mint 17

Try it 👍
sudo rm -rf /

Now I can finally see lot of output.
But at some point it get stuck again...

Did you try doing nothing?
try this:


HISTORY.md newest position is called (unreleased)

When making a new release, HISTORY.md newest position is called (unreleased) instead of the newest version.
I've created a simple workaround by modifying release under Makefile.
Instead of calling:
@$(ENV_PREFIX)gitchangelog  > HISTORY.md

You could perhaps do something like:
@$(ENV_PREFIX)gitchangelog | sed "s/(unreleased)/$${TAG} ($$(date +%Y-%m-%d))/g" > HISTORY.md

Furthermore, you could get rid of all the release commits from changelog:
@$(ENV_PREFIX)gitchangelog | sed "s/(unreleased)/$${TAG} ($$(date +%Y-%m-%d))/g" | grep -v "Release: version" > HISTORY.md

This way HISTORY.md contains relevant commits only.

Yeah, got the same question: How do you tag a git commit, but append the history to this very git commit afterwards (with gitchangelog)?


ISPN-13036 - Check if JSON value is array to prevent UnsupportedOpera…

…tionException
Proposed fix for https://issues.redhat.com/browse/ISPN-13036

ok to test

@gustavonalle not sure if test failures are related to the change.

Merged with a reproducer, thanks @cristianonicolai !


Main form, test form parsing Starts from XML or CSV OE2010

Merged new changes from Netbeans. Netbeans insists using a master branch instead the main branch


How to downlaod GoogleSignIn with framework ？

we do not need source code，we use google sign in with framework，how can i to upgrade our googleSignIn framework?

Duplicate of https://github.com/google/GoogleSignIn-iOS/issues/61


rpc: add pagination support to all relevant RPC APIs

Today we have pagination support for some calls like the QueryAssetStats call. We should also add them where relevant to the set of other calls that can return lists of data.
One example is the QueryAssetRoots and AssetLeafKeys call. Eventually both of these will exceed the default gRPC message limit, so we need to add pagination support here to ensure syncing, etc can still work.

For the leaf keys and the leaves, we should either have pagination be based on the block height, or sort in the query before we send things over.

One example is the QueryAssetRoots and AssetLeafKeys call. Eventually both of these will exceed the default gRPC message limit, so we need to add pagination support here to ensure syncing, etc can still work.

Here I guess you refer to the AssetRoots rpc call? That's the one that fetches all the roots for all known assets
QueryAssetRoots returns info about a specific asset

Correct, AssetRoots is the most important one. With QueryAssetStats following second, as that also allows to pull a lot of info in just one call.


Remove deprecated Hazelcast PubSub component

Signed-off-by: Bernd Verst<EMAIL_ADDRESS>Description
Remove deprecated Hazelcast PubSub component
Closes #5874

Should this be in 1.11 or 1.12? The component was deprecated mid-way through 1.9 (meaning: docs were updated half-way in the lifecycle of 1.9, but warning in code was added in 1.10 only)

It was listed as Alpha for the longest time I updated the docs to say Beta only in 1.8 because I found it had conformance tests. But either way, it doesn't meet Dapr PubSub at least once guarantees.
I think we can remove this in 1.11. Nothing forces us to wait two release cycles for components which are not stable.

1.11 is fine.


Longhorn Online Rebuilding

Which issue(s) this PR fixes:

Issue longhorn/longhorn#7199
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context

@mergify backport v1.7.x