text:
🛑 Elmas Yeşiloğlu is down

In c798212, Elmas Yeşiloğlu (https://www.elmasyesiloglu.com/) was down:

HTTP code: 404
Response time: 21828 ms

Resolved: Elmas Yeşiloğlu is back up in 279c2fe after 1 hour, 47 minutes.


text:
Price Ticker Not Updating

The price ticker on my Bitnode won't update.  It's been broken for a few weeks now.  Any ideas?  Everything else about the device seems fine.

This was reported and resolved here: https://forum.bitnodes.io/t/usd-btc-price-is-stuck/87/6

Thank you, sir.

source: gharchive/issue

repo: ayeowch/bitnodes-hardware

license: mit

license_type: permissive

license_source: bigquery


text:
Agent.write_inner_memory_from_logs() got an unexpected keyword argument 'only_tool_calls'

Hello, I'm trying to reproduce the numbers on GAIA found in the announcement post. When I run gaia.py I get the following error: Agent.write_inner_memory_from_logs() got an unexpected keyword argument 'only_tool_calls' that comes from this line of code: https://github.com/aymeric-roucher/agent_reasoning_benchmark/blob/00469f509dce67b48beb3890dfb707a0f89c4c32/gaia.py#L231
I tried searching through previous versions of the transformers library, but I can't seem to find any version of write_inner_memory_from_logs() that contains an argument for only_tool_calls.
Thank you for looking into this!

Same problem.

This should be fixed in the latest commit thatI just pushed: could you try again?

Also, you can find a newer version of this attempt to top GAIA here: https://github.com/aymeric-roucher/GAIA

authors: ahjwang aymeric-roucher bofei5675

license_source: github-api


text:
Bump default version of OTP to 1.4.0

Released July 30th.
https://repo1.maven.org/maven2/org/opentripplanner/otp/

@azavea/operations does this need a review? It's pretty trivial.

source: gharchive/pull-request

repo: azavea/ansible-opentripplanner


text:
Update release instructions

Overview
This PR updates release instructions to use chan for everything. The reason to do so is that chan gh-release handles tagging, pushing the tag, and creating GitHub releases, so when we had a separate tagging step we wound up with duplicated tags:

Checklist

[x] New tests have been added or existing tests have been modified
[x] Changelog updated (please use chan)

Follow up to #190

This is the wrong move because of how chan handles tags. Closing in favor of #190

This is the wrong move because of how chan handles tags. Closing in favor of #190


text:
Virtual relations (manually created)

Today Azimutt uses foreign keys as relations between columns (and so tables).
This is great but they are not the only way to do joins.
Some possible joins are either not declared (cf wordpress schema) or could not be declared, for performance reasons or flexibility (ex: polymorphic relations in Rails).
Virtual relations are relations present in the database but not declared as foreign keys in the schema.
With virtual relations, a user should be able to create new relations in his/her schema:

click on "create virtual relation"
click on the column referencing an other one
click on the referenced column (both tables should be visible)

With this, columns could have multiple outgoing relations (ex: Rails polymorphic relations).
If you like this idea and want to see it in Azimutt, please leave a :+1: reaction to this issue.
Also don't hesitate to as questions or suggest different implementations on this.

Implemented in https://github.com/azimuttapp/azimutt/pull/40

It would be nice if virtual relations were visually more distinguishable from foreign key constraints. Right now, when I create a virtual relation I'm not sure how I'd know that it's markup and not a fk relation if I didn't add the relation myself.

Yeah, I see what you mean.
For Azimutt, virtual relation are normal relations but in an other source. So they are not that different but indeed I could identify them. The bigger question for me is how to make them distinguishable? Color is already used for source table and dashed ones are for nullable foreign key. Maybe a dotted one? What do you think? Not sure if it would be clear.

Yeah, it's not that easy I guess, because they may also be nullable or not. A special stroke-dasharray like 35,10,5,10,5,10,5,10 for nullable and 35,10 for required virtual relation might work?

authors: loicknuchel michi-zuri

repo: azimuttapp/azimutt

license: MIT


text:
🛑 Sakai Wolford Bot is down

In 5424486, Sakai Wolford Bot (https://sakaibot-discord.uzumekiulee.repl.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sakai Wolford Bot is back up in d1c646c after 17 minutes.

repo: azrielbsi/monitor


text:
🛑 Sukri Online is down

In bd94e7d, Sukri Online (https://discord-aklx.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sukri Online is back up in eb66c0d after 7 minutes.


text:
🛑 azuma doa: Mailing Service is down

In 099dc7b, azuma doa: Mailing Service (https://azuma-health.tech/health/doa-mailing) was down:

HTTP code: 0
Response time: 0 ms

Resolved: azuma doa: Mailing Service is back up in 37f1285 after 22 minutes.

repo: azuma-healthtech-public/uptime-prd


text:
Added memory barrier before thread scheduling for ARMv8-A ThreadX SMP.

PR checklist

[x] Updated function header with a short description and version number
[ ] Added test case for bug fix or new feature
[ ] Validated on real hardware

Apply fix from #217 and expand to ARMv8-A arch.

repo: azure-rtos/threadx


text:
feat(element): first/last element child getters

closes #68

LGTM, thanks

can we release it?

authors: b-fuze ralyodio sno2

repo: b-fuze/deno-dom


text:
Add documentation

Fixes #53 and include basic documentation on the library

Coverage remained the same at 99.648% when pulling f134cec88ac651563f969f410b47dc31a5d8a405 on docs into 2ab9935b4e75b2eb1ac1fc557db683faf53272c3 on release-candidate.

authors: coveralls gcotelli

repo: ba-st/Stargate


text:
Question about input of evaluation

Hello,
Thanks for your great work!
What is the format of input in evaluation, directly using the input image or using stitched input?

Hi, thanks for your interest. During inference, we use the stitched input to align with the training setup.

Thanks, now I am clear about the inference formulation.
Another question about the results of joint training: does the result is obtained by first jointly training on multiple task then finetune on specific target task or directly using the jointly trained model?

The jointly trained model is directly evaluated on multiple tasks without task-specific fine-tuning.

Thank you very much!

repo: baaivision/Painter


text:
Template string failing with  Cannot read property 'range' of null

Upgraded to 10.0.3 and now everywhere in my .jsx I have template strings, it blows up with this error.
TypeError: Cannot read property 'range' of null
This is my current list of devDependencies
"@babel/core": "^7.2.0",
"@babel/plugin-proposal-class-properties": "^7.1.0",
"@babel/plugin-proposal-decorators": "^7.1.2",
"@babel/plugin-proposal-do-expressions": "^7.0.0",
"@babel/plugin-proposal-export-default-from": "^7.0.0",
"@babel/plugin-proposal-export-namespace-from": "^7.0.0",
"@babel/plugin-proposal-function-bind": "^7.0.0",
"@babel/plugin-proposal-function-sent": "^7.0.0",
"@babel/plugin-proposal-json-strings": "^7.0.0",
"@babel/plugin-proposal-logical-assignment-operators": "^7.0.0",
"@babel/plugin-proposal-nullish-coalescing-operator": "^7.0.0",
"@babel/plugin-proposal-numeric-separator": "^7.0.0",
"@babel/plugin-proposal-optional-chaining": "^7.0.0",
"@babel/plugin-proposal-pipeline-operator": "^7.0.0",
"@babel/plugin-proposal-throw-expressions": "^7.0.0",
"@babel/plugin-syntax-dynamic-import": "^7.0.0",
"@babel/plugin-syntax-import-meta": "^7.0.0",
"@babel/plugin-transform-regenerator": "^7.0.0",
"@babel/plugin-transform-runtime": "^7.0.0",
"@babel/plugin-transform-template-literals": "^7.0.0",
"@babel/polyfill": "^7.0.0",
"@babel/preset-env": "^7.1.5",
"@babel/preset-react": "^7.0.0",
"@babel/register": "^7.6.0",
"autoprefixer": "^9.1.3",
"babel-eslint": "10.0.3",
"babel-loader": "^8.0.0",
"babel-plugin-add-module-exports": "^0.2.1",
"babel-plugin-istanbul": "^5.2.0",
"babel-plugin-lodash": "^3.3.4",
"babel-preset-react-hmre": "^1.1.1",
"chai": "^3.4.1",
"chai-as-promised": "^5.1.0",
"chai-enzyme": "^1.0.0-beta.1",
"compression-webpack-plugin": "^1.1.11",
"css-loader": "^3.2.0",
"cssnano": "^4.1.0",
"enzyme": "^3.7.0",
"enzyme-adapter-react-16": "^1.6.0",
"eslint": "^6.0.1",
"eslint-config-airbnb": "^10.0.1",
"eslint-loader": "^2.2.1",
"eslint-plugin-babel": "^3.2.0",
"eslint-plugin-import": "2.14.0",
"eslint-plugin-jsx-a11y": "^2.2.3",
"eslint-plugin-react": "^6.2.0",
"extract-text-webpack-plugin": "^3.0.2",
"fetch-mock": "^5.10.0",
"file-loader": "^1.1.11",
"fs-extra": "^0.30.0",
"html-webpack-plugin": "^3.2.0",
"image-webpack-loader": "^4.6.0",
"ip": "^1.1.4",
"js-md5": "^0.4.1",
"karma": "^4.3.0",
"karma-chai": "^0.1.0",
"karma-chai-as-promised": "^0.1.2",
"karma-chai-sinon": "^0.1.5",
"karma-chrome-launcher": "^3.1.0",
"karma-coverage": "^1.1.2",
"karma-mocha": "^1.3.0",
"karma-sourcemap-loader": "^0.3.7",
"karma-spec-reporter": "0.0.26",
"karma-webpack": "^4.0.0-beta.0",
"koa-logger": "^1.3.0",
"loader-utils": "^1.1.0",
"lost": "^7.0.3",
"macaddress": "~0.2.9",
"mini-css-extract-plugin": "^0.3.0",
"mocha": "~5.2.0",
"node-noop": "^1.0.0",
"nodemon": "^1.18.7",
"optimize-css-assets-webpack-plugin": "^5.0.0",
"postcss-custom-media": "^7.0.8",
"postcss-focus-visible": "^3.0.0",
"postcss-focus-within": "^2.0.0",
"postcss-import": "^12.0.0",
"postcss-loader": "^3.0.0",
"postcss-nesting": "^6.0.0",
"postcss-preset-env": "^5.3.0",
"postcss-reporter": "^6.0.0",
"puppeteer": "^1.19.0",
"raw-loader": "^0.5.1",
"react-hot-loader": "^3.0.0-beta.7",
"react-text-truncate": "^0.12.0",
"react-toastify": "^2.1.0",
"redbox-react": "^1.5.0",
"redux-devtools": "^3.4.1",
"redux-devtools-dock-monitor": "^1.1.2",
"redux-devtools-log-monitor": "^1.4.0",
"redux-logger": "^3.0.6",
"redux-mock-store": "^1.0.2",
"sinon": "^1.17.2",
"sinon-chai": "^2.8.0",
"sonarqube-scanner": "^2.5.0",
"style-loader": "^0.21.0",
"stylelint": "^9.10.1",
"stylelint-webpack-plugin": "^0.10.5",
"svg-sprite-loader": "3.9.0",
"svgo": "^1.3.0",
"svgo-loader": "^2.1.0",
"url-loader": "^1.1.2",
"webpack": "^4.20.2",
"webpack-cli": "^3.0.8",
"webpack-dev-middleware": "^3.1.3",
"webpack-hot-middleware": "^2.22.3",
"webpack-merge": "^4.1.1",
"webpack-modernizr-loader": "^4.0.1"

Same for me. Possibly related to #691. @hzoo are you aware of any recent changes that might have effected your fix for that issue?

Workaround in https://github.com/babel/babel-eslint/issues/530#issuecomment-447511293 worked for me.

Same for me, I'm having issues where eslint after upgrading from v10.0.2to v10.0.3 breaks on the first file that contains a template string.

@ethansisson nice idea, for me simply just doing npm uninstall --save-dev @babel/types @babel/traverse was enough to fix the issue.

@ethansisson good point, for me simply just doing npm i @babel/types @babel/traverse --save-dev was enough to fix the issue.

Thanks man.

@einsiol it worked

It shows same error on code with dynamic import, template literal inline and rule template-curly-spcing as follow:
Tested on:
"babel-eslint": "^10.0.3"
"eslint": "^6.7.2"
Sample code:
import(`${'package.json'}`)

.eslintrc.json
{
  "parser": "babel-eslint",
  "rules": {
    "template-curly-spacing": ["error", "never"]
  }
}

Workaround:
Declare the template literal in a const instead of inline
I was not knowledgeable enough to fix it, hope someone will.

I resolved this by adding "@babel/parser": "7.7.5" to my package.json dependencies.

works for me
    "rules": {
      "indent": [
        "error",
        2,
        {
          "ignoredNodes": [
            "TemplateLiteral"
          ]
        }
      ],
      "template-curly-spacing": [
        "off"
      ]
    },

I resolved this by adding "@babel/parser": "7.7.5" to my package.json dependencies.

I installed it and it didn't work for me

this suddenly started failing after a recent yarn upgrade
const res = await import(`../../lang/locale/${payload}.json`);

replaced by
        const langFile = `../../lang/locale/${payload}.json`;
        const res = await import(langFile);

Fixed the error, but now am getting this warning instead Critical dependency: the request of a dependency is an expression

It shows same error on code with dynamic import, template literal inline and rule template-curly-spacing as follow:
Tested on:
babel-eslint@10.0.3
eslint@6.7.2
Sample code:
import(`${'package.json'}`)

.eslintrc.json
{
  "parser": "babel-eslint",
  "rules": {
    "template-curly-spacing": ["error", "never"]
  }
}

Workaround:
Declare the template literal in a const instead of inline
I was not knowledgeable enough to fix it, hope someone will.
EDIT:
It looks like the problem is actually coming from @babel/parser@7.7.7, which added ImportExpression.

I was in the midst of writing up an issue until I saw this comment which pretty much nails it. Hope this gets fixed later.

Adding this to package.json seems to work:
 "resolutions": {
    "@babel/parser": "7.7.5"
  }

It shows same error on code with dynamic import, template literal inline and rule template-curly-spacing as follow:
Tested on:
babel-eslint@10.0.3
eslint@6.7.2
Sample code:
import(`${'package.json'}`)

.eslintrc.json
{
  "parser": "babel-eslint",
  "rules": {
    "template-curly-spacing": ["error", "never"]
  }
}

Workaround:
Declare the template literal in a const instead of inline
I was not knowledgeable enough to fix it, hope someone will.
EDIT:
It looks like the problem is actually coming from @babel/parser@7.7.7, which added ImportExpression.

I'm facing the same situation, when TemplateLiteral is inside a dynamic import statement, error occurs. I found the SourceCode.getFirstToken() returns null instead of a Token, and function checkSpacingBefore() throws due to token is null.

I resolved this by adding "@babel/parser": "7.7.5" to my package.json dependencies.

This worked for me! I tried all the others solutions, but none of them worked.
Until this one, just added "@babel/parser": "7.7.5"

If you use package where @babel/parser is in dependencies, add "@babel/parser": "<7.7.7" in resolutions in package.json file, something like that
"resolutions": {
    "@babel/parser": "<7.7.7"
},

lete node_modules, package-lock.json/yarn.lock and then run npm install or yarn

Adding this to package.json is a temporary work-around:
 "resolutions": {
    "@babel/parser": "7.7.5"
  }

Then delete node_modules, package-lock.json/yarn.lock and then run npm install or yarn

It worked for me. thanks!

npm install does not work for me as "resolution" seems to be ignored.
I had to install yarn beforehand with (warning: the ubuntu package of yarn seems buggy for now)
sudo npm install -g yarn

Why this issue is appears again and again?

Adding this to package.json is a temporary work-around:
 "resolutions": {
    "@babel/parser": "7.7.5"
  }

Then delete node_modules, package-lock.json/yarn.lock and then run npm install or yarn

npm i -D @babel/parser@7.7.5
npm remove @babel/parser

Updates package-lock.json and fix issue aswell.

Upgraded from 10.0.3 to 10.1.0 and now I have the same error.
I would like to avoid this curly rule workaround and stay on 10.0.3 for now.
(Using vueJS & vuetify)

Got this issue again with v10.1.0.

Adding this to package.json is a temporary work-around:
 "resolutions": {
    "@babel/parser": "7.7.5"
  }

Then delete node_modules, package-lock.json/yarn.lock and then run npm install or yarn

⚠ Never ever delete the lockfile!
Use @ogonkov's solution: https://github.com/babel/babel-eslint/issues/799#issuecomment-585978781

@vladimyr If you don't delete the lock file, yarn/npm will read from that and try to put everything back. The lock file always contains your latest, even though your package.json may have ^1.0.0 for a package. Therefore, if you don't delete the lock file, you will get back the version of the parser you are trying to downgrade.

@hawkeye64 So it will affect only @babel/parser, right? We can simply ignore hundreds if not thousands of other side effects?! :man_facepalming:
I kindly suggest that you learn stuff in deep before you start giving out hazardous advice. Here is a good starting point: https://code-trotter.com/web/mastering-yarn-lock-file/

For people who were having this same issue as me. This error shows up as the following with eslint@7.1.0, @babel/parser@7.9.6, babel-eslint@10.1.0:

TypeError: Cannot read property 'value' of null

This work-around worked for me (npm@6.4.1):
npm i -D @babel/parser@7.7.5

I'm having this happen on the new ?? operator instead
https://gist.github.com/GeorgeWL/0a7ce21622259e84d39a929b8cd72c81 for the full logs and details

I too had issues after using nullish coalescing (?? operator) in a vuejs project.
After upgrading the eslint dependencies to a version which supported it, it resolved the issue for me.
I used the following dependencies to make it work:
"@vue/cli-plugin-eslint": "^4.4.5",
"@vue/eslint-config-standard": "^4.0.0",
"@vue/eslint-config-standard": "^5.1.2",
"@vue/eslint-config-typescript": "^4.0.0",
"@vue/eslint-config-typescript": "^5.0.2",
"eslint": "^5.16.0",
"eslint": "^6.8.0",
"eslint-plugin-vue": "^5.0.0",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-vue": "^6.2.2",
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-standard": "^4.0.1",
"eslint-plugin-import": "^2.21.2",
"@typescript-eslint/eslint-plugin": "^2.34.0",
"@typescript-eslint/parser": "^2.34.0"

Looks like you just switched from the Babel eslint parser to the typescript eslint parser

Hi! While we are in the same boat for this issue, a better version for resulutions workaround is:
  "resolutions": {
    "babel-eslint/@babel/parser": "7.7.5"
  },

This helps only using old @babel/parser for babel-eslint
For the alternative workaround, there was a difference for switch-case ident. So i used:
{
  "rules": {
    "indent": [
      "error",
      2,
      {
        "SwitchCase": 1,
        "ignoredNodes": [
          "TemplateLiteral"
        ]
      }
    ],
    "template-curly-spacing": 0
  }
}

The template string issue may be a separate issue from the nullish coalescing issue, so I'm gonna open a new ticket for the nullish coalescing and ref this thread.

My workaround was to not use backticks to interpolate strings. I refactored this:
import(`./${path}`)

into this:
import('./' + path)

and voila, it worked.

@joemaffei I'm having this issue with a Vue.js component containing this code:
        this.dynamicComponent = () => import('~/static/blog/${this.fileName}.md').then((loaded) => {
                        // ...

but, unfortunately, turning it into
        this.dynamicComponent = () => import('~/static/blog/'
            + this.fileName + '.md').then((loaded) => {
                        // ...

didn't work. I'm still getting TypeError: Cannot read property 'range' of null. Running
$ npx eslint --version

gives v7.5.0. I have this to my .eslintrc.json:
    "parser": "vue-eslint-parser",
    "parserOptions": {
        "parser": "babel-eslint",
        "ecmaVersion": 2018,
        "sourceType": "module"
    },

because before that ESlint complained about "unexpected import".

Fixed in @babel/eslint-parser 7.11.0, please see https://babel.dev/blog/2020/07/13/the-state-of-babel-eslint#the-future for the renaming guide.

@JLHwung I'm still experiencing this issue with @babel/eslint-parser 7.11.0 (with eslint 7.5.0 and @babel/core 7.11.0) 😞 Specifically with an import expression:
const foo = import(`${bar}`);

I've created a small repo to reproduce this issue: https://github.com/miikka/babel-eslint-799-repro

Thank you for the PR. Now that @babel/eslint-parser has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.

authors: Burtonium GeorgeWL JLHwung KempfCreative LCINA MartinX3 PatrickSchuster SabrinaFZ Strahinja demaet einsiol ethansisson fangbinwei hawkeye64 joemaffei kaicataldo miikka ntnyq ogonkov patrickmonteiro pbn04001 pi0 pitaj roland-reed s3bul techsin vesper8 vladimyr wandersonpjbkn yitomok

repo: babel/babel-eslint


text:
esLint integration

@jmeas  I integrated ESLint successfully on my test project. You can copy & paste. Just make sure you also copy the .eslint file in the root.
You find the code here: https://github.com/Kflash/ES2015/blob/master/gulpfile.js#L81-L98
esLint now works for source files and the test unit files.
There is a little issue. The jsNotify is not working out of the box with esLint it seems. I will investigate later. Other things to do now.
NOTE! You have to adjust and set your own rules, and remove the old lint files in your repo

@kflash, there's already an issue regarding ESLint over at #144. Gonna close this as a duplicate. I'll reference this when I go about adding ESLint, though, so thanks!

Sure. No problem. And I'm now out of your project. My time ended. I figure
waste of time to help out.
On May 12, 2015 1:14 AM, "James Smith" notifications@github.com wrote:

@kflash https://github.com/kflash, there's already an issue regarding
ESLint over at #144
https://github.com/babel/babel-library-boilerplate/issues/144. Gonna
close this as a duplicate. I'll reference this when I go about adding
ESLint, though, so thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/babel/babel-library-boilerplate/issues/159#issuecomment-100981756
.

authors: Kflash jmeas

repo: babel/babel-library-boilerplate


text:
Significant but hard-to-find bug in parsing arrow functions

As of a recent release (Don't know when, exactly, but this issue broke code that was working fine around June 4), babylon's parsing of arrow functions has broken in a very peculiar way. When babylon encounters the following pattern:
<some expression> :
    <a parenthesized arrow expression> ?
    <an unparenthesized arrow expression>

It reports an error parsing the parenthesized arrow expression:
Module build failed: SyntaxError: <path to file>: Assigning to rvalue (23:3)

For example:
let x = foo() ?
    (value => true) :
    value => false

The contents of the condition don't seem to matter, nor does parenthesizing the entire conditional expression. However, if the parenthesis around the first arrow function are removed, or parenthesis are added to the second arrow function, or either arrow function is something other than an arrow function, it is parsed fine. This specific pattern is the only one that triggers the error.
For what it's worth, I'm running babylon via babel via webpack, but the stack trace I get is entirely from babylon.
This seems implausible, I know, so I've created a git repo which reproduces the error, available here:
https://github.com/Lucretiel/babylon-error
The specific file I'm trying to pack is index.js with no dependencies or requires. The raw output from webpack is in build_result.

Quick follow up: I've just discovered that this bug ONLY manifests itself if the react babel plugin is being used.

Ok, so it only happens when flow/jsx parsing is on

I just did a git bisect and this is the result:

d15a2310cd405cb0bbfae1fbeb12d8ffbd4e28cb is the first bad commit

I will have a look what my change broke.

After digging around I also found this case which is not working anymore:
a ? (b): c => d

Because babylon with flow now sees the "valid-looking" arrow function (b): c => d.
Thinking about reverting my change and then reopening the other bug and redoing the fix.

authors: Lucretiel danez hzoo

repo: babel/babylon


text:
Draft 中属性赋值时错位

UPDATE
导致BUG原因：AbstractEntity的派生类所生成的Draft类XXXDraft中，Implementor.__get(prop: Int): Any?方法中字段下标顺序与基类AbstractEntityDraft字段下标顺序不一致
问题描述
定义了AbstractEntity基类，其中有 createTime 和 updateTime属性。定义 DraftInterceptor, 当插入表数据时自动设置createTime为当前时间:
@MappedSuperclass
interface AbstractEntity {
    val createTime: LocalDateTime
    val updateTime: LocalDateTime
}

class BaseEntityDraftInterceptor : DraftInterceptor<AbstractEntityDraft> {
    override fun beforeSave(draft: AbstractEntityDraft, isNew: Boolean) {
        if (isNew && !isLoaded(draft, AbstractEntity::createTime)) {
            draft.createTime = LocalDateTime.now()
        }
    }
}

期望结果：createTime 被设为当前时间
实际结果：updateTime 被设为当前时间，插表的 INSERT SQL语句字段也只有 updateTime没有createTime
原因分析猜测
框架代码里面可能有涉及到 entity 属性的索引下标（例如： 0,1,2）但是索引下标错位，或者是根据类查找字段（因为这几个字段都是 LocalDateTime），导致赋值错误。
为了证实不是个例，我在 AbstractEntity 中，在 createTime和updateTime中穿插添加了几列columnA、B、C
@MappedSuperclass
interface AbstractEntity {
    val columnA: LocalDateTime
    val createTime: LocalDateTime
    val columnB: LocalDateTime
    val updateTime: LocalDateTime
    val columnC: LocalDateTime
    val createBy: String?

    val updateBy: String?
}

再次运行代码，结果是columnC被赋值为当前时间（调试结果见下图）
生成的 INSERT 语句为（没有 createTime ）：
insert into sys_api_access_log(COLUMN_C, USER_ID, USER_TYPE, REQUEST_METHOD, REQUEST_URI, REQUEST_PARAMS, IP, USER_AGENT, START_TIME, DURATION, STATUS_CODE, CODE, MESSAGE) values(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

我这边不知如何重构，把你的基接口、派生接口，以及二者的Draft，打个压缩包，附带在本issue上。

code.zip
AbstractEntityDraft.kt#L70 以及 ApiAccessLogDraft.kt#L104 顺序不一致

我用你附件中的实体实测，没问题

该问题出现于多模块项目。下面的附件是一个简单的样例工程代码，用于复现该问题。AbstractEntity位于data公共模块，ApiAccessLog位于app业务模块。
jimmer-issue-69-recurrence.zip

哦

是不是data重新生成代码了而app没有？
如果是这个问题，解决办法：报错，基本类型被修改，派生类项目需要重新生成代码（虽然它的代码没有变）。

是不是data重新生成代码了而app没有？
如果是这个问题，解决办法：报错，基本类型被修改，派生类项目需要重新生成代码（虽然它的代码没有变）。

执行gradle clean确保所有生成代码被清除，然后重新build，问题存在。
PS：你可以试下我提供的那个工程。
PS：个人猜测此问题出现的原因是data被编译成jar包后被app引用，而编译成的jar包中字段顺序是按照字段名排序。因此在生成ApiAccessLogDraft代码时，要读取AbstractEntityDraft #__get方法中的字段顺序，而不是AbstractEntity中的字段顺序。

懂了

It is closed by github automatically, reopen it.
Try 0.7.51 please.

authors: aboutZZ babyfish-ct

repo: babyfish-ct/jimmer


text:
🛑 SM Service is down

In 5960ab2, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 0f8d3a7.

repo: bachmannschumacher/upptime


text:
Catalog-graph plugin: Be able to customize nodes of the graph

Feature Suggestion
To increase readability on catalog graphs, I'd like to be able to customize the color of the node of my graph, for example depending on their types (e.g team, component, service, resource, etc.) and after that, may be remove labels on the nodes and add the legend of my colors.
I didn't see anything about that in the page Customize the look-and-feel of your app.
Context
With my team, we could have very large graphs. From now, this is actually pretty hard to see the difference between a node that is a Team, or a Component or a Resource for example. I mean, we could read the labels, but on very large graphs it's not that easy

I had a similar requirement to this for EntityRelationsGraph.
Pushed two props renderNode and renderLabel in EntityRelationsGraph. Please see this file if it can be helpful to solve your use case.
https://github.com/backstage/backstage/commits/121211bb81c5b1b49419a868a2ec1af01a6d2c61/plugins/catalog-graph/src/components/EntityRelationsGraph/EntityRelationsGraph.tsx
https://github.com/backstage/backstage/blob/master/plugins/catalog-graph/src/components/EntityRelationsGraph/EntityRelationsGraph.tsx
Related issue #8850

@shailahir Thanks, I think this could solve my problem.
Do you have any example of usage for this two attributes ?
If it works, it only lacks of documentation on this IMHO.

I have full example but cannot show it as is because of the org policies.

@shailahir please provide some sample examples or documentation for this amazing contribution

@shvmbisht Did not try it for now. Will try to test what @shailahir pointed and get back with some documentation on this point if we succeed.

@shailahir TBH, I understand that your functions may solve my problem but I don't really get where to write and put such a function.
A sample example (or at least a written explanation) could be really useful here.

@LvffY Sure. Let me put together an example. I will share in a few hours after closing my day at work.

@shailahir Did you have time to look at some example ?

@shailahir no pressure but any news on those examples?

Hi @shvmbisht @LvffY , Sorry for delay
I have created one example, please have a look
https://gist.github.com/shailahir/f6b0cb591e29a66001bf830329470849

@shailahir @LvffY checkout this https://github.com/backstage/backstage/pull/12034

@Neemys we need to try the solutions provided here

authors: LvffY shailahir shvmbisht

repo: backstage/backstage


text:
🚀 Feature: unique cluster names

🔖 Feature description
Let's ensure that the name field of a cluster is a unique identifier. More specifically, if I make a request to the /api/kubernetes/clusters endpoint, the JSON array returned should contain objects such that each name value appears exactly once.
🎤 Context
From my perspective, a nice thing about this is that the bug #15901 would no longer occur. Moreover, having some kind of unique identifier is probably intuitive for integrators (I know I would have expected it when I first started with Backstage), and is a small step towards #13727.
Now there have been some valid criticisms of the difficulty of generating consistently unique names, and also the likelihood that such names will not be human-readable. The latter I hope should be addressed by #21398.
✌ Possible Implementation
The first thing I would try is modifying the CombinedClustersSupplier to check every single cluster it processes and make sure it hasn't seen its name before, throwing an error if it sees a duplicate:
https://github.com/backstage/backstage/blob/fc92656e4290aece5f332c2f4f54af50903afe5d/plugins/kubernetes-backend/src/cluster-locator/index.ts#L27-L41
At first, though, this might be too aggressive. Maybe we setup a migration plan for this; first just have the combined supplier log a warning to learn a bit more about possible sources of duplication.
As of now, I can think of two such sources:

I'm pretty sure that, based on issues like #13793 and #15668, the presence of AwsEKSClusterProcessors in the ingestion system can result in ambiguous cluster names.
the ConfigClusterLocator itself doesn't validate that the clusters it processes have unique names -- this would be pretty easy validation to add on startup.

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

@mclarke47 can this be closed? :pray:

I would like to find time to fix this but that doesn't seem like it's gonna happen soon

authors: benjdlambert jamieklassen mclarke47


text:
BEP: Authentication of External Services

🔖 Feature description
This proposal builds upon the foundation laid out in the 0003-auth-architecture-evolution BEP by introducing an authentication mechanism designed for external callers seeking to access the REST APIs exposed by Backstage or its plugins.
🎤 Context
https://github.com/backstage/backstage/tree/master/beps/0007-auth-external-services
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

For the jwks key type will it be possible to restrict the trust of the external jwks based on specific claims in addition to listing jwks.  For example, if using Entra to generate those secondary trusted credentials, you wouldn't want to blindly trust https://login.microsoftonline.com/common/discovery/v2.0/keys as those same signing keys are the default used for all Entra tenants.  At minimum you'll need to validate the iss claim, and you probably want to also validate aud (and possibly other claims)

@afscrome makes sense, thank you :+1:

authors: Rugvip afscrome freben


text:
feat(backend-common): exposed onAuth callback

Hey, I just made a Pull Request!
Exposed the onAuth callback from isomorphic git to allow callers to specify a callback to resolve credentials based on the URL of the remote instead of providing static credentials. For example, the DefaultAzureDevOpsCredentialsProvider can be used to resolve Azure DevOps credentials based on the request URL.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] ~Added or updated documentation~
[x] Tests for new functionality and regression tests for bug fixes
[x] ~Screenshots attached (for UI changes)~
[x] All your commits have a Signed-off-by line in the message. (more info)

To give some more context, the onAuth callback seems to be my only options to use the DefaultAzureDevOpsCredentialsProvider in the commitAndPush action of @parfuemeriedouglas/scaffolder-backend-module-azure-repositories.
But in general this feels like a good way to pass the authentication specifics off to a credential provider for the specific integration (Azure DevOps, GitHub, GitLab, etc) instead of requiring plugin authors to resolve credentials for a given URL themselves.

Thinking out loud here, should we mark the StaticAuthOptions as deprecated or is it fine to keep both options side-by-side removing the complexity of specifying an AuthCallback when you have static credentials.

@benjdlambert I processed your comments. Can you have another look?

This looks pretty good I think, just one thing about the changeset

@benjdlambert @Rugvip thanks for your reviews, I have resolved your comments 👍

authors: benjdlambert sanderaernouts


text:
Dictionary key serialization too strict

a key can start with a '' and non leading characters can also be '' or '.':
https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-19#section-4.1.1.3
The regex here does not permit this:
https://github.com/evert/structured-headers/blob/abda0ba6b041c9d934306cf22545091edffa06b4/src/serializer.ts#L35

This library was several drafts behind, and instead of trying to get it up to date with the current RFC, I rewrote it. The new parser passes all official tests, but the serializer is not done yet. More here soon

Current master branch is fully up to date with the new RFC, and we're passing all httpwg tests.

authors: evert jkhales

repo: badgateway/structured-headers


text:
Configuring Ranger

:clipboard: Description
I noticed that you installed Ranger but have not yet used it to automate merging PRs, closing issues, or handling other tasks.
Have you had any trouble with it, or need any help configuring it? I am here to help! 👍
If not, feel free to close this issue (or have Ranger do it for you 🙂)

hi @mfix22, thanks for reaching out. We did try to use it a while back on our PRs but were unable to get it to work. I still think we'd really benefit from the functionality, but we didn't really have time to dig into why it wasn't working/what we may have been missing/etc.
If you have any insight on how we could get it working that would be great!
One example of a PR where we tried: https://github.com/badges/shields/pull/3526

Hey @calebcartwright sorry to hear that! I would love to help make sure it is working correctly for you. I see that all the checks passed on your PR, so that is looking good ✅ Did you have any other protections on the master branch at all?
On a fresh clone of the repo, I see that Ranger is working fine, https://github.com/mfix22/shields/pull/1#event-2592619178, so I am assuming it has something to do with your other integrations, most likely CI/CD.
If you could try again with a small/dummy PR, that would be great, otherwise I will try and set up CircleCI on my fork to better recreate the situation.

We use quite a lot of branch protection rules on this repo. My assumption is that one of these rules is preventing repo ranger from being able to merge for us. We have the following rules enabled:

Require pull request reviews before merging
Required approving reviews: 1
Dismiss stale pull request approvals when new commits are pushed
Require status checks to pass before merging
Require branches to be up to date before merging
Include administrators
Restrict who can push to matching branches: Organization and repository administrators, badges/shields-core

Any thoughts?
While its nice that you've proactively contacted us about this, one of the reasons we've not followed this up at all is that its not very obvious how to contact you with a support query. Even if your code is not public, have you considered setting up a public issues-only repo or something?
Thanks

Just wanted to say @mfix22 that a merge queue we could kick off after an approving review that would take care of updating the branch, waiting for tests to pass (except LGTM and Docker, which take too long), and then squash-merging, would be super helpful for this project. I'd estimate it would save 1–2 hours of maintainer time a week.

While it's nice that you've proactively contacted us about this, one of the reasons we've not followed this up at all is that its not very obvious how to contact you with a support query. Even if your code is not public, have you considered setting up a public issues-only repo or something?
Thanks

@chris48s this is great feedback, thank you. We have a public feedback form you can contact me at here: https://reporanger.com/feedback, however, I will also set up a public issues-only repo for tracking bugs/issues here: https://github.com/reporanger/feedback.

@paulmelnikow that is great to hear — I would absolutely love to help you save those hours.
If you add the "squash when passing" label to a PR, Ranger will automatically squash-merge the PR once all the required statuses are passing, following all integration status checks, branch protection rules, etc.
I you can add the label to a branch in need of merging, I can investigate why it might not be being merged.

Can you look at the example @calebcartwright posted? https://github.com/badges/shields/pull/3526

Can you look at the example @calebcartwright posted? #3526

On it 👌

#3880 has the necessary approvals.

This is what we have under "restrict who can push to matching branches".

Do we need to add a user for Ranger?

Hey @paulmelnikow I think you are right! The public status listing shows that the PR has a mergeable_state of clean, which means "good to go", however Ranger is getting the status: blocked which means that is is not able to merge the PR.
Can you try adding Ranger to an approved list you mentioned above? We have never seen this specific set of branch blocking rules before so I really appreciate you are letting me debug this 🙂

I can only add GitHub users. Which user is it?

@repo-ranger is the username.

It's added!

Looks like the PR was merged!

Great! 👍 Thanks for working through this with me. I added another set of logging to our backend that will help me understand this issue faster in the future 👌
Now that we got it working, are there any other features you would like help automating? On other repos I maintain, I configure things like: automatically deleting HEAD branches, deleting ":+1:" comments, stuff like that 🙂

Awesome!
Will it update an out-of-date branch before attempting to merge it? That's the thing we need for this to be useful.

Will it update an out-of-date branch before attempting to merge it?

And would we need that to be done via a dependabot command on dependabot opened PRs to avoid merge conflicts, and if so can ranger support that?

We are actively building out that feature, but trying to figure out how to best fit it in with the rest of Ranger's config.
I will ping in this thread, or in a new issue immediately once the feature ships.

Thanks for helping with this. Even without the ability to auto-@dependabot rebase this will probably save a bit of time.
It would be helpful to mention in the documentation that users need to manually give @repo-ranger write access to master in the branch protection config as well as authorising the app. I suspect we won't be the first users not to understand this.

@chris48s done! reporanger.com/docs — Under the section on "Merging Pull Requests"
Also I have just pushed the feature that will keep a branch up to date as long as your branch protection rules require that. Would you like me to enable that feature for you repo?

Nice. Yes. Lets give it a try. Thanks

@mfix22 I noticed the merge queue is waiting on LGTM to run, which is not a required check, mostly because it is sometimes very slow!
Can I request a feature that only the required checks must pass in order to merge?
Or alternatively, that we can list certain checks to ignore?

The automatic branch updating is working!

Hey @paulmelnikow 👋 looks like Ranger no longer has permission to merge your branches. Did a branch protection rule recently get updated? You might have to give Ranger write access to re-enable PR merging.
You can find how to handle this under the "Branch Protection" section of the Repo Ranger docs

Seems to have just merged one in #5026 no?

Oh, okay. Great!

Thanks for reaching out!
We had an issue where maintainers couldn't click the "Update Branch" button. It might have been due to a setting on the PR or maybe it was some GitHub fluke. See https://github.com/badges/shields/pull/5008#issuecomment-622978456
Maybe that was related?

That could be! Thanks @paulmelnikow. I'm just glad it is still working 👍

repo: badges/shields


text:
Maven-Metadata renders a version like "1.0" as "1"

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] gh-badges NPM package

:beetle: Description
For the following metadata:
metadata: http://central.maven.org/maven2/com/google/guava/guava-beta-checker/maven-metadata.xml
The actual badge rendered

expected badge

Presumably some kind of issue with how versions are handled (as strings vs numbers)?

Thanks @loosebazooka
You could use the MavenCentral version badge in the interim which provides your expected format
https://img.shields.io/maven-central/v/com.google.guava/guava-beta-checker?label=maven)

I recall something similar in the MavenCentral service (fixed in #3935), so I imagine the same fix could be applied to the MavenMetadata service to fix this

Thank you @calebcartwright for the pointer! Let's see if I could prepare a PR for that.

Closed via #4224

authors: calebcartwright loosebazooka netsgnut


text:
Add Travis CI badge to img.shields.io repo

I'm thinking it would be neat to start using our own badges now that we have a real codebase. :smile:

Outdated.


text:
Add support for custom MyGet tenants

Add support for custom MyGet tenants (e.g. dotnet.myget.org)
Sample shield URL would be: https://img.shields.io/dotnet.myget/dotnet-coreclr/v/Microsoft.DotNet.CoreCLR.svg

Thanks @maartenba for submitting this PR. We (dotnet\corefx) team would like to use these badges for some of our packages.

@maartenba Thanks for your contribution! I agree for the record with @weshaggard. Can you perform this change to the existing myget mapping? Would you be against me rewriting your commit?
@weshaggard On an unrelated topic, I would love it if you had a bit of time to look at #678.

@espadrine Feel free to rewrite, totally fine with that :-)

Thanks for the contribution. The change is live! You can try it out; I'll add an example to the main website in 24h.

Awesome, thanks!

Thanks for the taking the change.

@weshaggard On an unrelated topic, I would love it if you had a bit of time to look at #678.

Sorry I don't have the much influence or context on the nuget team. It looks like you have filed the right issue on nuget\home.

authors: espadrine maartenba weshaggard


text:
Stylesheet is missing

When I run "npm run build", the link to the app.version.css is missing in build/index.html.
To fix it, remove quotes from 'false' because debug is not a string.
https://github.com/badsyntax/react-seed/blob/master/app/index.html#L7

Are you sure? 'debug' is a string, because it's passed as a string: https://github.com/badsyntax/react-seed/blob/f6cbd0378413840c11d1ea9688126640b0791ad0/webpack/loaders.js#L19 (Not ideal, I know).
This is the output I'm getting in index.html when I run npm run build:
<!DOCTYPE html>

  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width" />
  <title>react-seed</title>

  <link type="text/css" rel="stylesheet" media="all" href="css/app.0.0.13.css" />

Input: app/index.html

The type of 'version' variable is <%= typeof(version) %>
\n

The type of 'title' variable is <%= typeof(title) %>

The type of 'debug' variable is <%= typeof(debug) %>

  ...

Output: build/index.html

The type of 'version' variable is string

The type of 'title' variable is string

The type of 'debug' variable is boolean

  ...

I found out why. I started react-seed from a fresh install of node_modules so I use the last version of "loader-utils" package. (https://github.com/webpack/loader-utils/commit/1c75aac162e77351442bcc05e186959315abcea3 and https://github.com/webpack/loader-utils/commit/63f19e9a0772292c1cb1e48944cbc3294317fd3f)
"true" and "false" strings are converted to boolean since loader-utils@0.2.9.

template-html-loader@0.0.3 /tmp/react-seed/node_modules/template-html-loader
├── consolidate@0.10.0
└── loader-utils@0.2.10

What is your version of loader-utils ?

Thanks for feeding back this information! That's exactly what's happened. Dev's should be more careful about how they release, a change of behaviour should not be a patch release, as is the case here.
I'll fix this when I have some time. Thanks again!

Or feel free to send a PR!
I'd like to update all the packages at some point (npm-check-updates is helpful here).

Thanks for the new release.

authors: badsyntax dcorral

repo: badsyntax/react-seed


text:
Log Fehler Configuration

Was hab ich falsch gemacht?
Muss ich was einfüllen in die Callback URL?
Mein-Log:

swiss-weather-api.0 | 2022-02-19 14:28:23.126 | error | Possible  cause is an incorrectly configured adapter. Please check configuration.  If error persists, create an issue on  https://github.com/baerengraben/ioBroker.swiss-weather-api.

swiss-weather-api.0 | 2022-02-19 14:28:23.126 | error | Delivered SRF-JSON is not valid: {"access_token":"", "expires_in": , "token_type":"Bearer"}

Hat funktioniert. Der Browser hat nicht den ganzen Consumer Key angezeigt.


text:
Add a column Zip code/Zip Range in Tax Rates Page.When we export tax rate, Zip code and range is not available in exported file and while exporting tax rate also no range for zip is defined after importing the tax rate we need to define zip code seprately for all tax rate.

Framework Version:0.1.5

Framework Version: 0.1.5
Fixed

repo: bagisto/bagisto


text:
Tags for project

Please have a look at the https://help.github.com/en/github/administering-a-repository/classifying-your-repository-with-topics — the topics describe a repository in GitHub.

https://cdn1.savepice.ru/uploads/2020/6/28/523f0c8ff3de4787152058d0816e8cd1-full.png
(Topics)

repo: bahmanm/ojlang-core


text:
$validator.validate not working as expected when using Vue Test Utils' setChecked method

I'm using Jest and Vue Test Utils to test an app that uses Vee Validate.
My App component contains a form which in turn contains a bunch of child components.
I'm trying to test a child component that uses radio buttons.
My problem is that after using Vue Test Utils' setChecked method to check one of the radio buttons, Vee validate still considers the form field to be invalid.
Here is the failing test:
it('framework radio buttons require a value', async () => {
  // Component has two radio buttons where name='framework'
  // The first radio button is marked v-validate="'required'"

  await wrapper.vm.$validator.validate('framework');
  expect(wrapper.vm.errors.has('framework')).toBe(true);

  // One of the radio buttons has id="vue"
  const radio = wrapper.find('#vue');
  radio.setChecked(true);
  await flushPromises();

  await wrapper.vm.$validator.validate('framework');
  expect(wrapper.vm.errors.has('framework')).toBe(false);
});

The first expect passes — I have mounted the component, am validating the radio buttons  and expecting that when neither radio button is checked, the field is invalid.
The second expect fails and this is what I don't understand.
Here, I am selecting one of the radio buttons and setting its checked property to true. I would have thought that when I revalidate the field, the validator would recognize it as  valid.
Yet the test fails with:
  ● App › framework requires a value

    expect(received).toBe(expected) // Object.is equality

    Expected: false
    Received: true

      34 |
      35 |     await wrapper.vm.$validator.validate('framework')
    > 36 |     expect(wrapper.vm.errors.has('framework')).toBe(false);

However, the same strategy works fine with a text input. In this case everything passes:
it('first_name requires a value', async () => {
  // first_name is a text input that is marked as 'required'

  await wrapper.vm.$validator.validate('first_name');
  expect(wrapper.vm.errors.has('first_name')).toBe(true);

  const input = wrapper.find("#first_name");
  input.setValue("Emmie");
  await flushPromises();

  await wrapper.vm.$validator.validate('first_name');
  expect(wrapper.vm.errors.has('first_name')).toBe(false);
});

I have made a sample repo that demonstrates the problem. To run the tests:
git clone git@github.com:jameshibbard/vee-validate-test-utils.git
cd vee-validate-test-utils
npm i
npm run test:unit

Do you have an idea what I am doing wrong? I would be grateful for any pointers.
Also, sorry if this is not a Vee Validate issue. In that case, please just let me know and I'll post this on the Vue Test Utils repo.

Sorry, it took a while for me to take a look at this.
I don't know if this is a setChecked issue or not. I have tests but I set the checked property and trigger change myself. Does it work if you do it manually?

No problem. I appreciate the response :)

Does it work if you do it manually?

If I interact with the form manually in the browser then everything works as expected.
In the test however, no matter what I try, I cannot make the failing test pass. I tried:

simulating a click on the radio button
setting the element's checked property manually, using setChecked
firing a change event manually (using dispatchEvent(new Event('change'))

But nothing worked.

By manually I meant changing the checked prop, these are the tests for vee-validate with radio and checkboxes:
  test('radio buttons fields', async () => {
    const input = wrapper.find('#rad1');
    input.trigger('change');
    await flushPromises();
    expect(wrapper.vm.errors.has('radioField')).toBe(true);

    // we need to set the element attribute
    input.element.checked = true;
    input.trigger('change');
    await flushPromises();
    expect(wrapper.vm.errors.has('radioField')).toBe(false);
  });

  test('checkbox fields', async () => {
    const input = wrapper.find('#cb1');
    input.trigger('change');
    await flushPromises();
    expect(wrapper.vm.errors.has('checkboxField')).toBe(true);

    input.element.checked = true;
    input.trigger('change');
    await flushPromises();
    expect(wrapper.vm.errors.has('checkboxField')).toBe(false);
  });

Unfortunately, that didn't work.
I changed the failing test (link to repo in post #1) to mirror what you posted above:
it('framework requires a value', async () => {
  const radio = wrapper.find('#vue');
  radio.trigger('change');
  await flushPromises();
  expect(wrapper.vm.errors.has('framework')).toBe(true);

  radio.element.checked = true;
  radio.trigger('change');
  await flushPromises();
  expect(wrapper.vm.errors.has('framework')).toBe(false);
});

Test fails with:
  ● App › framework requires a value

    expect(received).toBe(expected) // Object.is equality

    Expected: false
    Received: true

      34 |     radio.trigger('change');
      35 |     await flushPromises();
    > 36 |     expect(wrapper.vm.errors.has('framework')).toBe(false);
         |                                                ^
      37 |   });
      38 | });
      39 |

      at Object.toBe (tests/unit/example.spec.js:36:48)

Okay I cloned the repo and did a few things to pinpoint the issue, did you try setting attachToDocument for the mounting options?
const wrapper = mount(App, {
  sync: false,
  localVue,
  attachToDocument: true
});

Also you need to ditch setChecked since it doesn't seem to work properly for whatever reason, You can also replace it with this:
radio.element.checked = true;
radio.trigger('change');

This allowed the test to pass on my end, can you confirm? I have submitted a PR.

Yup, this solved things for me (also on my proper project, not just the test repo).
Thank you!

authors: jameshibbard logaretm

repo: baianat/vee-validate


text:
词重要性是如何建模的？

我看了下lac的源码，但是没能debug到词重要性的建模代码。

词重要性是直接使用BiGRU的模型，对于每个词进行重要性分类。
其使用词向量+标签向量（LAC的预测结果）作为特征输入，简洁有效；
具体可以参照预测代码，训练代码暂无开放

authors: Bond-H xueyongfu

repo: baidu/lac


text:
LAC 2.1.0 update

词性标注模型粒度更新为字词混合，在效果保持不变的情况下，性能提升最高可达40%。
新增加词语关键度分类功能，在维持LAC词性标注结果下可以标注词语关键程度。
修复了模型训练速度慢问题。
更新README.me
增加Changelog

rename parameter name and initialize all models at once


text:
+output[].result[].type如何定义？

默认的type是tts，除了手写改json，在图形流程编辑器里怎么定义？还有，多个result在图形流程编辑器里怎么定义？

目前output[].result[].type只支持tts，运行language_compiler/run.py程序即可生成，无需在图形流程编辑器里定义

authors: jiangshilin lyc-baidu

repo: baidu/unit-dmkit


text:
写@mixin 不知道为啥会报错

会报‘Support for the experimental syntax 'decorators-legacy' isn't currently enabled’ 这个错；
但是我引了 import mixin, { padStr } from '@/utils/mixin';
我刚开始学 对着这个项目敲来着 不是很懂 是不是我什么没装呀

需要安装修饰器的babel插件

请问 是babel-plugin-transform-decorators-legacy这个吗 我装了还是报错来着

好像因为版本的原因 我装了 @babel/plugin-proposal-decorators 这个然后再配置一下就可以了 谢谢啦！

authors: bailicangdu dadazhouRenee

repo: bailicangdu/react-pxq


text:
🛑 OhMy is down

In 230a3b8, OhMy (https://ohmy.xin) was down:

HTTP code: 500
Response time: 1274 ms

Resolved: OhMy is back up in 4cb2afb after 12 minutes.

repo: baizhiheizi/upptime


text:
Remove ignored files

Those files and directories have been ignored since https://github.com/balamod/balamod/commit/3af56b6716f5e5e6afb9feefaeb2a479bf411922.

@UwUDev Why closing?

repo: balamod/balamod


text:
Sails memory leak using sails-postgresql adapter and model.find

Sails version: 1.0
Node version: 8.9.0
NPM version: 5.5.1
DB adapter name: sails-postrgesql
DB adapter version: 1.0.0-12
Operating system: windows 10

Well this is a repost of an issue posted on stackoverflow.  https://stackoverflow.com/questions/48698000/does-v8-node-actually-garbage-collect-during-function-calls-or-is-this-a-sail
SailsJS seems to leak when repeated calling model.find({}). While the code uses populate, without populate it still "leaks" - though much less and it just takes more time to crash.
Github minimal example can be found at: https://github.com/pulli23/memory-leak-sails
To reproduce application must be run with the following options:
I run with the flag: --max-old-space-size=80
Environment variable: node_env=production
Then if using a POST request to localhost:1337/start-runner the runner should start (as found in WorkerController.DoRun() ). - It connects to a postgresql database (database information redacted for obvious reasons).
At my personal setup it runs about 2500 times, each time finding roughly 2000 elements.
After that node will crash reporting heap memory erro.
Increasing the max-old-space-size also dramatically increases the amount of runs, however it still crashes after "some" time.
Using a mock method (as is commented out in the github) it will not crash. And the program keeps running without problem.
The combination of those: Consistent crashing at about the same runcount when calling model.find({}) and not crashing when not using a mock that creates the same result, leads me to believe there's a memory leak in sails or the adapter.

I can't provide more information without any input of a developper. - I'd like to see some activity from your side.

I too have seen this, https://github.com/balderdashy/waterline/issues/1384 was my GitHub issue a while back. I've not solved it yet, I just run 4 threads (4 core CPU) in production with PM2 restarting the threads as they die every few days, which is usually less often than deployments restarting the threads.

@wulfsolter actually, just remembered you posted https://github.com/balderdashy/sails/issues/4264#issuecomment-374081327, and looks like that was slightly after.  Hopefully that means the issue is still fixed for you as well, but if not, please keep me apprised

I think the Model.find() leak is still around.... we're running a read heavy application (~3M rows being read only writing ~5000 daily) but it works, we have deploys more often than running out of RAM and PM2 simply restarts a thread @ 4GB. Sure we lose a few requests, but with most of our clients having less than perfect connectivity our RequestManager() is pretty robust.
Small problems compared to a beautiful framework that makes our lives so much easier :D And there were certainly a few 'death glares' when I did a pres on database migration of MySQL+Mongo -> Postgres with no downtime thanks to the great ORM :D https://wulfsolter.github.io/presentation-mongoToPostgre/#/

@wulfsolter haha no doubt, thanks for the link!
So just to clarify:  the valleys in that chart are where PM2 is restarting the process due to a process crash from running out of heap, and not where the garbage collector runs?

Hi I'm using mongo and I'm having same issue.
I'm using locust to load my api and I can verify that used memory always increase. I'm just doing a simple Model.find()
Help will be appreciated as my app is productive at this moment and my containers are crashing after some time.
Thanks

authors: mikermcneil pulli23 vidueirof wulfsolter

repo: balderdashy/sails


text:
Populating records with json column crashes if the populated model's column has the same name

Waterline version: 0.13.1-2
Node version:8.4.0
NPM version:5.0.4
Operating system:Windows 10 Pro x64

If you have two related models and both have the same JSON attribute like this
...
jsonAttr: {
  type: 'json'
}
...

Then when you do a populate on them, waterline tries to parse the populated record's json value twice if its an empty array, resulting in a crash:
SyntaxError: Unexpected end of JSON input
       at JSON.parse (<anonymous>)
       at checkAttributes (e:\UserData\Projects\ekola\node_modules\sails-mysql\helpers\private\query\process-each-record.js:77:35)

To repro:

Create model parent.js

{
  collection: {
     model: 'child',
     via: 'parent'
  },
  meta: {
    type: 'json',
    defaultsTo: []
  }
}

Create model child.js

{
  someWonderfulStuff: {
    type: 'string',
    defaultsTo: 'OK'
  },
  parent: {
     model: 'parent'
  },
  meta: {
    type: 'json',
    defaultsTo: {}
  }
}

Populate children's meta with some valid JSON
3.1) Ensure parent's meta values are equal to [] in the database, and that there are multiple child records that point to the same parent
Perform the following query: Child.find({ someWonderfulStuff: 'OK' }).populate('parent')
You should get the above error stack trace.
Current workaround is to keep the json value as NULL on parent until it can be filled with some data. This only happens when the parent's record value is an empty array and has the same name as the child's json attribute.

Seems like an edge case, but a pretty severe one, as it likely indicates that some record processing logic is faulty.

@megakoresh @sgress454 Hey everyone, we're currently moving the Waterline issues to Sails (balderdashy/sails) to keep a closer eye on updates and boost their exposure to the community.  I see a resolution was patched in to a newer version of Waterline.  Thanks for the efforts and hope it's now working for everyone.

@megakoresh @sgress454 hey ya'll we are further cleaning up Sails issues by closing older or resolved issues. As @johnabrams7 mentioned above the fix for this should be published in the newest version of waterline.

authors: johnabrams7 megakoresh raqem


text:
Update version of sails-hook-organics in newly-generated projects to fix vulnerabilities

machinepack-http currently uses lodash < 4.17.11, which has a prototype pollution vulnerability. This should be remedied per - https://nodesecurity.io/advisories/577 & https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487
To remedy, the @sailshq/lodash package in https://github.com/sailshq/machinepack-http/blob/master/package.json, https://github.com/sailshq/machinepack-urls/blob/master/package.json, https://github.com/node-machine/machine/blob/master/package.json, and https://github.com/balderdashy/include-all/blob/master/package.json should be updated to lodash >= 4.17.11.

Hi @chrisbellman, just took a look at this, and turns out we did update machinepack-http awhile back to resolve this vulnerability. I just noticed that the version of sails-hook-organics that comes bundled in the default Sails web app template is still using the old version of machinepack-http, though, so we ought to update that on our end so people are getting the newer version by default. (I'd be open to looking at a PR for this in sails-generate if someone wants to take a stab at that in the near future.)
In the mean time, you can try installing the latest version of sails-hook-organics in your project  to see if that resolves the issue for you (looks like it's currently on 1.0.0). Here's what's changed in the latest version of machinepack-http.

@rachaelshaw - I might be reading this wrong but it looks like the latest version of machinepack-http still has "@sailshq/lodash": "^3.10.2" in package.json, which is old/vulnerable. I'm using this in another project, not Sails.

@chrisbellman If you see ^ in the version, then it will install the latest minor or patched version; so it should bring in 3.10.4 automatically when you npm install 👍

Any updates on the subject? When will this vulnerability be fixed, please?
Can you update the dependency?

I submitted a PR to update the version of sails-hook-organics included by default when generating an app with the "Web app" template.
@hassench in your existing Sails app, you can run npm install sails-hook-organics@latest to get the updated version

I submitted a PR to update the version of sails-hook-organics included by default when generating an app with the "Web app" template.
@hassench in your existing Sails app, you can run npm install sails-hook-organics@latest to get the updated version

Thank you @rachaelshaw , I did that but how does that solve the vulnerability problem with lodash? How can I update it to the latest version? I still have "@sailshq/lodash": "^3.10.4"  as the latest version available.
However the latest version on lodash repo is 4.17.15.
Should I install it separately ?

@hassench @chrisbellman
Mike really likes using lodash 3 (we’re using _.pluck() all over the place) and @sailshq/lodash is our fork of lodash 3 where we’ve implemented security patches. 👍

authors: chrisbellman hassench johnabrams7 rachaelshaw


text:
patch: Add support for manaul workflow runs

Mysteriously our scheduled GitHub action workflow to update the website has stopped running. I checked the logs and recent commits to find potenial errors. It stopped running on the scheduled time for 5 days. Checking answers on the web, I found folks suggesting way to unclog the run queue to get the scheduled action running again along with a way to trigger it manually to get it running.

https://stackoverflow.com/questions/59560214/github-action-works-on-push-but-not-scheduled
Scheduled workflows are unreliable https://upptime.js.org/blog/2021/01/22/github-actions-schedule-not-working/
Adding a manual trigger seems a nice way to unblock when we are in a fix: https://devopsjournal.io/blog/2022/08/12/workflows-not-starting

Will give this a shot and see if it fixes it.
Signed-off-by: Vipul Gupta (@vipulgupta2048) vipul@balena.io

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@balena-ci I self-certify!

repo: balena-io/docs


text:
imx6ul-var-dart: Kernel warnings present with newer kernel 5.4.85

dmesg reports:
[  636.523174] Unhandled fault: external abort on non-linefetch (0x008) at 0x76ef7000
[  636.530755] pgd = 32d4d09d
[  636.533469] [76ef7000] *pgd=99df5835, *pte=000f0783, *ppte=000f0e33
[  646.554278] 8<--- cut here ---
[  646.557371] Unhandled fault: external abort on non-linefetch (0x008) at 0x76eb9000
[  646.564955] pgd = 34cc2e95
[  646.567668] [76eb9000] *pgd=8c180835, *pte=000f0783, *ppte=000f0e33

Doing a self-service update to Supervisor 13.1.10 will resolve the issue. Keeping this issue open until Supervisor 13.1.10 is included in a production release of balenaOS for imx6ul-var-dart.

Fixed in production at 2.98.33+rev1

authors: acostach rosswesleyporter

repo: balena-os/balena-variscite


text:
TP-LINK TL-WN722N: The device does not support Access Point mode

Hello! I'm trying to use Wifi-Connect with Balena, a Raspberry Pi CM4, and a TL-WN722N as recommended by the Readme here.
However, I'm getting the following D-Bus error when Wifi Connect tries to start an access point:
Can anyone advise on why that might be?
 wifi-connect  [network_manager::dbus_api:ERROR] org.freedesktop.NetworkManager::AddAndActivateConnection method call failed on /org/freedesktop/NetworkManager
 wifi-connect  Error: Creating the captive portal failed
 wifi-connect    caused by: D-Bus failure: org.freedesktop.NetworkManager::AddAndActivateConnection method call failed on /org/freedesktop/NetworkManager
 wifi-connect    caused by: "the device does not support Access Point mode"

Closing the loop here, I've had good success with the Panda Wireless modules which seem to play nicely with Network manager.

repo: balena-os/wifi-connect


text:
[Epic]: Add svg icons, update keywords, rename connection record as ConnectionConfig and update package.md to report issue at extended-library repo

Connector Name
All handwritten connectors
Epic description
Do the following things in all hand-written connectors

Pack svg icon within the resource folder, add that path in the display annotation
Update keywords in Ballerina.toml according to https://docs.google.com/spreadsheets/d/103CjLGTAZbbcdyEto-chz1vhvJV-t9uvLnYQ0LU-8m8/edit?usp=sharing
Rename the configuration record name as ConnectionConfig and update init function, test and samples according to this change.
In the issue reporting section in Package.md, point to https://github.com/ballerina-platform/ballerina-extended-library instead of the connector issues link

Related tasks
No response

Closing since this is done now

This was done to all handwritten connectors.
One example would be https://github.com/ballerina-platform/module-ballerinax-slack/pull/61


text:
Swagger tooling refactoring

Description:
This task is created to track the progress of the Ballerina Swagger tooling redesign and refactoring.

[x] Discuss the naming of the tool
[x] Rename Ballerina Code generator which generate Client for a service using openAPI specification. https://github.com/ballerina-platform/ballerina-lang/issues/13807
[ ] Write a spec for the tool.

[ ] Review the mapping details of the spec.
[ ] Share the designs with community.

[ ] Design how to show the swagger details on Ballerina Source
[ ] Upgrade swagger library versions to the latest https://github.com/ballerina-platform/ballerina-lang/issues/14538
[ ] Handle all content type in conversion from ballerina or to ballerina
[ ] Update Ballerina by Guides for swagger
[ ] Add warning for swagger annotation resolver for what was not possible to convert in to swagger
[ ] Rename swagger tool - https://github.com/ballerina-platform/ballerina-lang/issues/13807
[ ] Refactor and improve usability of CLI command
[ ] Refactor the CLI help files
[ ] Move on to generate Open API 3.0 (e.g: https://github.com/OAI/OpenAPI-Specification/blob/master/examples/v3.0/petstore.yaml)
[ ] Test with OpenAPI 3.0 https://github.com/ballerina-guides/open-api-based-service/issues/35

Swagger to Ballerina

[ ] Fix data losses during this conversion
[ ] Improve support for schemas, parameters, responses, requestBody
[ ] Improve template for generating ballerina source

Ballerina to Swagger

[ ] Fix data losses during this conversion
[ ] Support conversion for all types
[ ] Support conversion for parameters, responses, requestBody

Review Notes for the OpenAPI Spec

Review of OpenAPI Tooling Spec

[x] Remove unnecessary details from the spec.
[ ] Look in to whether we can move the OpenAPI object level description to markdown documentation
[ ] Create a annotation in service level to hold common details available for path item object which are not captured in resource function and resource annotations
[ ] Discuss with standard library team about mappings like required attribute in Parameter object to ballerina optional type in ballerina source.

Moved to a new issue #16935

repo: ballerina-platform/ballerina-lang


text:
Fix data table to xml/json usage.

This is not part of the spec.

table to JSON & table to XML conversions are moved out from the language. This will move to xmlutils and jsonutils.


text:
Implement a parser-listener/AST-generator V1

Description:
Implement $subject that is capable of generating the tree, for a input that is parsed from the parser in #20766

Initial version is available at https://github.com/SupunS/BallerinaParser/tree/master


text:
Query-expressions that construct maps and tables should not always have error type

Description:
$title. This should be fixed after fixing https://github.com/ballerina-platform/ballerina-lang/issues/36181.
Steps to reproduce:
Ex.
type Employee record {|
    readonly int id;
    string firstName;
|};

public function main() {
    table<Employee> key(id) employees = table [
        {id: 1, firstName: "John"}
    ];

    table<Employee> key(id) highPaidEmployees = table key(id) from var e in employees
                            select e; // expected 'table<Employee> key(id)', found '(table<Employee> key(id)|error)'
// Here, both `from-clause` and `select-clause` will not complete early with an error value.
// Therefore, for this scenario, compiler should allow this statement.
// Same for map case also
}

Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Table case which is described in https://github.com/ballerina-platform/ballerina-lang/issues/36686 will be fixed with https://github.com/ballerina-platform/ballerina-lang/issues/36686

@SandaruJayawardana shall we back-port the fix to applicable branches

@SandaruJayawardana shall we back-port the fix to applicable branches
Sure. I will send this fix to 2201.2.x.

https://github.com/ballerina-platform/ballerina-lang/pull/37925 will fix this issue in 2201.2.x branch.

authors: SandaruJayawardana pcnfernando


text:
[Improvement]: Inconsistent resource method names generated for call instruction

Description
$subject
Describe your problem(s)
When compiling a ballerina resource method, we generate new method names with the class/object-type name prefix. This is updated in the function invocation symbol name and several other fields contain the method names such as the expression name, and invocation symbol originalName.
But we only need the method name without the type name for the method call. Therefore we filter out the redundant parts during the BIRGen and CodeGen phases.

https://github.com/ballerina-platform/ballerina-lang/blob/10fc9656e84eb8734128fe58bf2e6bf1e71c3b93/compiler/ballerina-lang/src/main/java/org/wso2/ballerinalang/compiler/bir/BIRGen.java#L892
https://github.com/ballerina-platform/ballerina-lang/blob/10fc9656e84eb8734128fe58bf2e6bf1e71c3b93/compiler/ballerina-lang/src/main/java/org/wso2/ballerinalang/compiler/bir/codegen/JvmCodeGenUtil.java#L426

When I checked these name fields, the values they assigned were inconsistent for different use cases.
1. ABC.init
- Func expr name: ABC.init
- Func symbol name: ABC.init
- Func original name: init
- ObjectType name from receiver symbol: ABC

2. ABC.start
- Func expr name: ABC.start
- Func symbol name: ABC.start
- Func original name: 'start
- ObjectType name from receiver symbol: ABC

3. Int range iterator
- Func expr name: null
- Func symbol name: $anonType$return$createIntRange$_0.iterator
- Func original name: iterator
- ObjectType name from receiver symbol - null

4. Anontype
- Func expr name: compare
- Func symbol name: ($anonType$Atom$_0 & readonly).compare
- Func original name: compare
- ObjectType name from receiver symbol - null

5. MockListener
- Func expr name: detach
- Func symbol name: MockListener.detach
- Func original name: detach
- ObjectType name from receiver symbol: MockListener

Note that, to filter out the function name from the function symbol name, we use the receiverSymbol at BIRGen and the selfArg argument at CodeGen. This is because in some cases, the receiver symbol becomes null and the type can only be derived from the self-argument.
We need to have a more consistent way of providing the name. If we have a field that contains only the method name without the type prefix, we can directly use it without any filtering. It is not recommended to use string processing in the method names as they are error-prone (the user-defined name can contain special characters.) and can slow down the compilation as well.
Please find the log file with possible type name combinations here.
objectTypeFunctions.log
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
https://github.com/ballerina-platform/ballerina-lang/issues/42988
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

It seems the attached function name generated for immutable object contains a module name prefix.
For example,
public type File readonly & object {
    public function filename() returns string;
};

public function format(File file) {
    string line = file.filename();
}

public readonly class VirtualFile {
    *File;
    public function filename() returns string => "Hello";
}

public function main() {
    File d = new VirtualFile();
    format(d); // function name - (hinduja/test_listener:0:$anonType$File$_0 & readonly).filename
}

The filename() method is passed as (hinduja/test_listener:0:$anonType$File$_0 & readonly).filename from the compilation.
Ideally, we need to pass the original function name as a separate field similar to the other scenarios.


text:
Use process builder approach for single bal files

Purpose

Modify 'RunExecutableTask' to use the process builder approach for single bal files as well.

Fixes #22002
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #22180 into ballerina-1.2.x will not change coverage by %.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.2.x   #22180   +/-   ##
================================================
  Coverage            14.59%   14.59%
================================================
  Files                   51       51
  Lines                 1411     1411
  Branches               219      219
================================================
  Hits                   206      206
  Misses                1189     1189
  Partials                16       16

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 eb1232c...32a318c. Read the comment docs.

authors: codecov-io suganyasuven


text:
Added new endpoint to get function definition given position

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes # https://github.com/wso2-enterprise/choreo/issues/12425
https://github.com/ballerina-platform/ballerina-lang/issues/37414
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[x] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@axewilledge Shouldn't this changes go to 2201.2.x, 2201.3.x and master? I see the one for 2201.1.x has been merged.

@axewilledge Shouldn't this changes go to 2201.2.x, 2201.3.x and master? I see the one for 2201.1.x has been merged.

I have added to 2201.2.x one. https://github.com/ballerina-platform/ballerina-lang/pull/36961
but not for 2201.3.x


text:
[Client] Support integer, boolean types in request header

Purpose
Support integer, boolean types in request header.
Goals
Fixes https://github.com/ballerina-platform/ballerina-openapi/issues/730
Automation tests

Unit tests
Added

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Test environment
JDK 11

Shall we add another test case for this PR to meet the test coverage requirements ?

Addressed in https://github.com/ballerina-platform/ballerina-openapi/commit/ca91d3e71d482eec87f219e5d4b5fbb0761475b0

repo: ballerina-platform/ballerina-openapi


text:
Add MSSQL test cases

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

Let's change the UpdateTest to verify whether the data we inserted have been inserted as expected, in a separate PR, as discussed offline.

Let's change the UpdateTest to verify whether the data we inserted have been inserted as expected, in a separate PR, as discussed offline.

fixed in https://github.com/ballerina-platform/ballerina-scenario-tests/pull/38/commits/1402cee58bb3dd0339a86f09a6228ae0e8f64f1f

authors: Biruntha Manuri


text:
Add concurrency to cancel concurrent builds on same PR

Purpose
$Subject
Related issues: 3581
Examples
Checklist

[x] Linked to an issue
[ ] ~Updated the changelog~
[ ] ~Added tests~
[ ] ~Updated the spec~
[ ] ~Checked native-image compatibility~

Closing this since this is going to be implemented using workflow templates.


text:
[Enhancement] Block comments support

Better to have the block comment support in the ballerina.

This was decided to not support in ballerina. If you need to put a doc comment, it will be supported with document annotations. Other than that, every other comment can be put into maximum of several lines within code.

authors: chaminda chanakaudaya

repo: ballerinalang/ballerina


text:
Use is statements for responses in samples

Purpose

$subject

Goals

Syntax upto date

Codecov Report

Merging #205 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #205   +/-   ##
=========================================
  Coverage     65.06%   65.06%
  Complexity      117      117
=========================================
  Files            14       14
  Lines           561      561
  Branches         56       56
=========================================
  Hits            365      365
  Misses          167      167
  Partials         29       29

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 7eec8d2...3241098. Read the comment docs.

authors: codecov-io hemikak

repo: ballerinax/docker


text:
Update stage

Purpose

Update stage

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


text:
Support table function derived table

Support table function derived table
for example:
"select * from TABLE(SOME_FUNCTION(some_arg))"
see : https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html#table-function-derived-table

Pull Request Test Coverage Report for Build 191930384

36 of 38 (94.74%)  changed or added relevant lines in 3 files are covered.
27 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.02%) to 91.896%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/sqlparser_common.rs
23
25
92.0%

Files with Coverage Reduction
New Missed Lines
%

src/parser.rs
7
89.05%

tests/sqlparser_common.rs
20
96.76%

Totals

Change from base Build 191855500:
0.02%

Covered Lines:
4513

Relevant Lines:
4911

💛  - Coveralls

sorry for all the commit's - i got into some mess between my branch's ,
But fixed now  ..

authors: coveralls eyalleshem

repo: ballista-compute/sqlparser-rs


text:
Should we also extend spectral:oas?

Hello
I have a doubt while reading the documentation and the top of your rule file.
https://github.com/baloise-incubator/spectral-ruleset#possibility-a-reference-via-github-url
Should extend both your ruleset and "spectral:oas"? If so, could you update the documentation to make it clear?
Here is an example of specification which is not valid against spectral:oas, but ok with zalando ruleset:
npx @stoplight/spectral-cli lint v1.yaml

extends: ["https://raw.githubusercontent.com/baloise-incubator/spectral-ruleset/main/zalando.yml"]
extends: ["https://raw.githubusercontent.com/baloise-incubator/spectral-ruleset/main/zalando.yml", "spectral:oas"] # both
extends: ["spectral:oas", "https://raw.githubusercontent.com/baloise-incubator/spectral-ruleset/main/zalando.yml"] # spectral:oas is ignored...

rules:
  must-use-problem-json-as-default-response: false

openapi: "3.0.0"
info:
  title: Simple API overview
  version: 2.0.0
  contact:
    email: default@gmail.com
    name: default
    url: http://default.com
  description: default
  x-api-id: abcdef12345
  x-audience: external-public

servers:
- url: "https://development.gigantic-server.com/v1"
  description: "Development server"

tags:
  - name: user
    description: Users

paths:
  /users/{id}:
    parameters:
    - in: path
      name: toto   # wrong name
      required: true
      schema:
        type: integer
    get:
      operationId: get_user
      tags:
      - user
      responses:
        '200':
          description: successful operation
        default: {$ref: '#/components/responses/DefaultError'}

components:
  responses:
    DefaultError:
      description: Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'

  schemas:
    ApiError:
      description: Error object
      type: object
      properties:
        title:
          type: string

Thanks for the input. I have a look into it.

Check your input and you are right, the rules from spectral:oas aren't validated. Btw the rules can be found here https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules.
This is intentional as the purpose of this rule set is only to reason about Zalando specific rules.
But this isn't clearly documented, I will do a PR for the documentation.

repo: baloise-incubator/spectral-ruleset


text:
建议支持是以列表展示相册还是直接展示所有图片

问：你希望加什么新功能？
答：
问：微信、QQ等大APP的选择器，是否有这个功能？
答：
问：这个功能是否适合所有人？如不是，是否要加个属性开关？
答：
其它你希望补充的内容

老哥，你是这个意思吗？  https://github.com/banchichen/TZImagePickerController/issues/1332

一打开默认就是进入的【所有照片】相册，就是直接展示所有照片的...

authors: Cordeiring banchichen

repo: banchichen/TZImagePickerController


text:
Reduce gas costs by doing "address warm-up"

[details missing on how to exactly achieve this]
In the latest ethereum hard fork, they added the ability to "warm up" addresses - it's a way for miners to reduce gas costs in a tx a bit if they know beforehand which addresses are going to be used in a transaction
In order to do that, the frontend needs to adds some specific metadata to the tx
This is the EIP that introduced it -
https://eips.ethereum.org/EIPS/eip-2930
(also somewhat related: https://eips.ethereum.org/EIPS/eip-2929)
web3:
https://github.com/ChainSafe/web3.js/pull/4332
ethers:
https://docs.ethers.io/v5/single-page/#/v5/api/providers/types/-%23-types--transactions
https://docs.ethers.io/v5/single-page/#/v5/api/providers/types/-%23-providers-AccessList
There needs to be a way to get the access list from a tx simulation (e.g., estimageGas), but we need to look into it
There might be already a one-liner way to achieve this

@ashachaf can you please review the description as I'm not sure I added all the information that's required


text:
Upper Case

UPPER CASE BAD!
Camel Case Good :D

@meytal2021

looks good to me.

what is holding this off from being pushed to prod?

@Meytal2021 Can you review the new font sizes?

repo: bancorprotocol/webapp


text:
🛑 MXN Base On-ramps is down

In f409aac, MXN Base On-ramps ($QUOTE_ENDPOINT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MXN Base On-ramps is back up in 1c7154f after 23 minutes.

repo: bandohq/upptime-monitor


text:
Gulp branch

Brought test coverage to 100%.

Done reviewing current commits.

repo: bandwidthcom/node-bandwidth


text:
--color option breaks the output in Git Bash on Windows

$ git diff data/slugify.js | git-split-diffs | less

$ git diff data/slugify.js | git-split-diffs --color | less

(Truncated output; there are a few more lines.)

$ git --version
git version 2.31.1.windows.1

$ node -v
v14.13.0

$ npm ls -g --depth=0
C:\Users\mts\AppData\Roaming\npm
├── git-split-diffs@0.10.0
...

Any idea what might be wrong? I'm using Windows Terminal in the screenshots, but the --color option doesn't work either when used directly in Git Bash.
The output seems to be colorized when using CMD, even without the --color option, but I don't want to use CMD. (Btw the output looks gorgeous! 🤩)
From todo.md I can see that there's a completed item called "Test on windows." I wonder what kind of setup was used for the testing? Was CMD or Git Bash used?

From todo.md I can see that there's a completed item called "Test on windows." I wonder what kind of setup was used for the testing? Was CMD or Git Bash used?

I tested on a fresh Windows 10 VM  in VirtualBox, both with CMD and Git Bash:
$ git --version
git version 2.31.1.windows.1

$ node -v
v14.16.1

From the screenshot, it seems that the ANSI color codes are not being interpreted. I'd guess that this has to do with the TERM environment variable. For me it is set to xterm in git bash and unset in CMD and colors work in both. Can you check that?

Thank you!
$ echo $TERM
xterm-256color

I just noticed that if I don't pipe the output to less, everything works perfectly. So the problem is actually in the less command.
From superuser.com/q/117841/111704 I learned that I need to use the -R flag with less. -r seems to work as well.
So now it's working, and it's beautiful!

Hmm, now I noticed that the less commands in the "Install globally" and "Install locally" sections in the readme use the flags -RFX. Maybe the command in the "Use manually" section should also use at least the -R flag?

Oh yes, thanks. I'll update it

authors: banga mtsknn

repo: banga/git-split-diffs


text:
@MainActor isolation on expect functions

All the expect functions are @MainActor isolated and the async expression closures as well. I'm not sure, if this is always needed. The evaluate function uses an internal actor to protect the isFulfilled state. If I want to test some expression that has to run on the MainActor this is useful.
But for code that doesn't have to be isolated this requires MainActor isolation code to be added. I don't want to add this to the call site, if I don't actually need the isolation for data safety.
I think the async expression closures should also be @Sendable ?
I forked the code and I'm experimenting with non isolated expect function overloads. Unfortunately this requires different names it seems. Apparently Swift doesn't support function overloading with and without @MainActor isolation.

I think annotating the async closures with @MainActor makes them Sendable. Agree that it would be nice to skip adding the @MainActor on the client side. Would it work to remove the MainActor as default and just mark the closures as sendable?

Yes, I think it should be possible to just mark the closure as required to be @Sendable. I can take a look, when I have time.

authors: KaiOelfke bangerang

repo: bangerang/swift-async-expectations


text:
Make code regions error before recording itself in dependency graph (when possible)

Right now, if a Banyan job fails, it gets completely shut down. But unfortunately the user can't always just restart the job because data might be partially written. Now for errors because of large data, node failures, or split/merge/cast functions; this is a big issue where we need to have better resilience and some sort of retry logic with atomic writes; also, reusing failed jobs as warmed up jobs would be nice.
But for runtime error because of incorrect usage of an API, we should be able to catch these before we even send annotated code regions to the Banyan backend for scheduling. We just have to modify the @partitioned macro to first include the original code (which is run on cached data samples) with $(esc(code)) before actually submitting a task to be scheduled with record_request(RecordTaskRequest(task)) and finish_task().
This would allow us to catch a considerable amount of runtime error without actually crashing a job created with create_job. This would be useful only for REPL/notebook users because for other cases, you would probably run create_job

Resolved

repo: banyan-team/banyan-julia


text:
IgnoreVolumeClaimTemplateFields: ignore volumeMode

It seems volumeMode is set server-side in certain cases (e.g. k3s sets
it to 'Filesystem'), which causes unwanted diffs. Deleting the field
from both current and modified effectively ignores this field.

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets

License
Apache 2.0

What's in this PR?

IgnoreVolumeClaimTemplateTypeMetaAndStatus now ignores spec.volumeClaimTemplates[].spec.volumeMode by removing it from both current and modified.
Why?

I got "strange" diffs. It turned out, that this lib does not ignore spec.volumeClaimTemplates[].spec.volumeMode, which is set after Creating a sts. I am working with k3s at this time, so it may be a case that happens only with k3s or in certain edge cases.
Additional context

I'm using k3s with a very standard setup (just ran their script on the landing page)
Checklist

[X] Implementation tested (manually only, will add automated test if somebody can confirm this change makes sense!)
[X] Error handling code meets the guideline
[X] Logging code meets the guideline
[X] User guide and development docs updated (if needed)

To Do

[ ] Add automated test, if maintainers are interested in this PR.
[ ] Confirm if this change is actually safe to just ignore it, or if we have to introduce a new Option. I'd like to hear the opinion of a maintainer - i see the risk that this may be unwanted / unexpected to current users of IgnoreVolumeClaimTemplateTypeMetaAndStatus

Hey, thanks for putting this together! I'm not entirely sure what's happening here since any changes made solely on the server side should not cause any diffs as seen in this draft PR:
https://github.com/banzaicloud/k8s-objectmatcher/pull/50

Hey, indeed, it should not happen - but it does for me. I'll try to write a reproducer.

closing this due to inactivity, let me know if you want me to reopen

authors: birdayz pepov


text:
Accept SecretName in all api calls

Some of the api endpoints still expect secretID (like GetObjectStoreBucketStatus), which should have been changed in #1091

Are there any other calls then GetObjectStoreBucketStatus?

authors: bonifaido orymate

repo: banzaicloud/pipeline


text:
Azure  (and other providers) - handle quotas

Product info may show resources that are limited by user specific quota - this may lead to failures during cluster creation

https://github.com/Azure/azure-sdk-for-go/blob/master/services/compute/mgmt/2018-04-01/compute/models.go#L3752

authors: lpuskas prekoa

repo: banzaicloud/productinfo