Angular 13 - ng build-watch inifinity loop

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: 11
Description
 A clear and concise description of the problem...
I updated my project from Angular 11 to Angular 13
From now on, when I run a ng build --watch the command runs in an infinite loop
🔬 Minimal Reproduction
Here is my package.json :
    "name": "open-capture-for-invoices",
    "version": "2.1.0",
    "scripts": {
        "ng": "ng",
        "start": "ng serve",
        "build-watch": "ng build --watch",
        "build:prod": "NODE_ENV=production ng build --configuration production",
        "reload-packages": "rm -Rf node_modules && rm package-lock.json && npm cache clean --force && npm i --force",
        "extract-translations": "ngx-translate-extract --input ./ --output ./src/assets/i18n/frontend/*.json --clean --sort --format namespaced-json --marker _"
    },
    "private": true,
    "dependencies": {
        "@angular/animations": "~13.2.4",
        "@angular/cdk": "^13.2.4",
        "@angular/common": "~13.2.4",
        "@angular/compiler": "~13.2.4",
        "@angular/core": "~13.2.4",
        "@angular/forms": "~13.2.4",
        "@angular/material": "^13.2.4",
        "@angular/material-moment-adapter": "^13.2.4",
        "@angular/platform-browser": "~13.2.4",
        "@angular/platform-browser-dynamic": "~13.2.4",
        "@angular/router": "~13.2.4",
        "@biesbjerg/ngx-translate-extract-marker": "^1.0.0",
        "@fortawesome/fontawesome-free": "^6.0.0",
        "@ngx-translate/core": "^14.0.0",
        "@ngx-translate/http-loader": "^7.0.0",
        "@schematics/angular": "^13.2.5",
        "@swimlane/ngx-charts": "20.0.1",
        "@syncfusion/ej2": "^19.4.53",
        "jquery": "^3.6.0",
        "moment": "^2.29.1",
        "ng-click-outside": "^9.0.1",
        "ng-sortgrid": "^5.3.0",
        "ng2-datepicker": "^12.0.0",
        "ngx-file-drag-drop": "^5.1.3",
        "ngx-mat-select-search": "^4.0.2",
        "remove-accents": "^0.4.2",
        "rxjs": "~7.5.4"
    },
    "devDependencies": {
        "@angular-builders/custom-webpack": "^13.1.0",
        "@angular-devkit/build-angular": "^13.2.5",
        "@angular/cli": "~13.2.5",
        "@angular/compiler-cli": "~13.2.4",
        "@biesbjerg/ngx-translate-extract": "^7.0.4",
        "@types/d3-scale": "^4.0.2",
        "@types/d3-selection": "^3.0.2",
        "@types/node": "^17.0.21",
        "autoprefixer": "^10.4.2",
        "postcss": "^8.4.7",
        "tailwindcss": "^3.0.23",
        "ts-node": "^10.3.1",
        "tslint": "~6.1.3",
        "typescript": "~4.5.5",
        "zone.js": "~0.11.4"
    }
}

🔥 Exception or Error

/usr/bin/npm run build-watch --scripts-prepend-node-path=auto

><EMAIL_ADDRESS>build-watch /var/www/html/opencaptureforinvoices
> ng build  --watch

⠙ Generating browser application bundles (phase: setup)...Processing legacy "View Engine" libraries:
- @biesbjerg/ngx-translate-extract-marker [es2015/esm2015] (git+https://github.com/biesbjerg/ngx-translate-extract-marker.git)
- ng-sortgrid [es2015/esm2015] (git+https://github.com/kreuzerk/ng-sortgrid.git)
Encourage the library authors to publish an Ivy distribution.
✔ Browser application bundle generation complete.
✔ Index html generation complete.

Initial Chunk Files | Names         |  Raw Size | Estimated Transfer Size
main.js             | main          |   2.38 MB |               387.54 kB
styles.css          | styles        | 193.14 kB |                26.85 kB
scripts.js          | scripts       |  98.08 kB |                31.26 kB
polyfills.js        | polyfills     |  36.25 kB |                11.54 kB
runtime.js          | runtime       |   1.75 kB |               897 bytes

                    | Initial Total |   2.70 MB |               458.06 kB

Build at: 2022-02-25T10:26:46.590Z - Hash: fe49d0ef9ef41c8f - Time: 278344ms

Warning<EMAIL_ADDRESS>depends on 'clone-deep'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

✔ Browser application bundle generation complete.
✔ Index html generation complete.

Initial Chunk Files | Names | Raw Size | Estimated Transfer Size
main.js             | main  |  2.38 MB |               387.50 kB

4 unchanged chunks

Build at: 2022-02-25T10:27:56.686Z - Hash: f8c2fee1caa5580f - Time: 82609ms
✔ Browser application bundle generation complete.
✔ Index html generation complete.

Initial Chunk Files | Names | Raw Size | Estimated Transfer Size
main.js             | main  |  2.38 MB |               387.18 kB

4 unchanged chunks

Build at: 2022-02-25T10:28:48.990Z - Hash: 0676e9987a5e28b7 - Time: 54989ms
✔ Browser application bundle generation complete.
✔ Index html generation complete.

5 unchanged chunks

Build at: 2022-02-25T10:29:02.132Z - Hash: 0676e9987a5e28b7 - Time: 12987ms
✔ Browser application bundle generation complete.
✔ Index html generation complete.

5 unchanged chunks

Build at: 2022-02-25T10:29:12.450Z - Hash: 0676e9987a5e28b7 - Time: 10184ms
✔ Browser application bundle generation complete.
✔ Index html generation complete.

5 unchanged chunks

Build at: 2022-02-25T10:29:22.540Z - Hash: 0676e9987a5e28b7 - Time: 9973ms
✔ Browser application bundle generation complete.
✔ Index html generation complete.

5 unchanged chunks

Build at: 2022-02-25T10:29:33.921Z - Hash: 0676e9987a5e28b7 - Time: 11259ms
✔ Browser application bundle generation complete.
✔ Index html generation complete.

5 unchanged chunks

🌍 Your Environment

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 13.2.5
Node: 14.19.0
Package Manager: npm 6.14.16
OS: linux x64

Angular: 13.2.4
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, material-moment-adapter, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1302.5
@angular-devkit/build-angular   13.2.5
@angular-devkit/core            13.2.5
@angular-devkit/schematics      13.2.5
@angular/cli                    13.2.5
@schematics/angular             13.2.5
rxjs                            7.5.4
typescript                      4.5.5

Anything else relevant?

Try with updated node and npm, the issue is still present

I noticed that you are using @angular-builders/custom-webpack can you remove it’s usage and use the official builders and see it the problem persists?
If the problem persists please setup a minimal repro please.
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Hi @alan-agius4
Thanks for you quick answer. I tried to made a repro-app, using the same package.json, angular.json etc.. but could reproduce the problem in a smaller app..
Could you check my project, I made a branch with my Angular 13 test ?
https://github.com/edissyum/opencaptureforinvoices/tree/repro_oc_angular_v13
Thanks in advance

The issue appears to be caused by misconfiguration of tailwind css. This is causing the root directory to be added as a dependency.
This also causes redundant files and directory traversals which does cause the builds to be significantly slower.
content: [
-   '**/*.{html,ts}'
+   'src/frontend/**/*.{html,ts}'
],


Build ko for Windows

Also explicitly build for macOS (darwin), I'm not sure how that was being done before.

Codecov Report

Merging #339 (550a6f1) into main (d498734) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #339   +/-   ##
=======================================
  Coverage   38.24%   38.24%
=======================================
  Files          33       33
  Lines        1527     1527
=======================================
  Hits          584      584
  Misses        849      849
  Partials       94       94

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 d498734...550a6f1. Read the comment docs.


May sprintjs register as a npm module?

or just create the package.json let us happy to go:
$ npm install -S git+https://github.com/bendc/sprint.git

Duplicate of #5


American Eagle ERJ145LR (Livery Request)

I was really bored of what aircrafts should I make. But I ended up making this livery. Btw can you send me the texture image of the B737-800? I wanna make some liveries of the aircraft. And I didn't add a US flag in the aircraft. And it's because I was scared of searching the US flag for some reason😅😅 My stress level is going to rise up in weekdays.  rip lol

Here's the texture
https://ibb.co/rmTwMG6
And here's the uv map


Measurement Client Generator | Default value support for the client

[x] This contribution adheres to CONTRIBUTING.md. (Required)
[ ]  Automatically post PR comments with images for G code changes? (Recommended for small changes)

What does this Pull Request accomplish?

Updated the Client Generator to retrieve default values from the Measurement Plug-In and update the client with the values.
Updated the representation of Enum control created in the client to U32, to provide support for more values in the generated Enum.

Why should this Pull Request be merged?

To provide default value support in the generated Measurement Plug-In Client.
To update representation of the generated Enum control in the client.

What testing has been done?

Created clients for example measurements and tested.

Create control.vi
Diff image:

Modify Client Controls.vi
Diff image:
Before:

After:

Update Measurement from Metadata.vi
Diff image:
Before:

After:


add more screenshots

At right moment screenshots may be incorrect because https://github.com/nvim-treesitter/nvim-treesitter/issues/3651


Feature Request: SVG Response option

Any size can be requested - but why request sizes when you can request an SVG that will scale at any size and look terrific no matter the DPI of the device?

I think this would be really cool!


feat: system view > manage user's project membership

There was the idea to add a user to a project from system view "list of users". This PR implements this missing feature as "Manage project membership" for each user. Resolves #55

Great form! Looks very nice!
I have just 2 little things:

I have noticed that the drop-down menu opens at the top of the dialog box when there are 2 or more selected projects in the list (when there is only one project, the menu opens in front of the menu field):

I have added my user (myself) as a collaborator and admin to the BEOL project (as a test). But when I open the membership dialog box in system>all users right after, the project BEOL does not appear in the list. I have to refresh the page manually.

I have noticed that the drop-down menu opens at the top of the dialog box when there are 2 or more selected projects in the list (when there is only one project, the menu opens in front of the menu field):

hm...strange. It never happened to me. I will test it again, as soon my local knora installation works again.

I have added my user (myself) as a collaborator and admin to the BEOL project (as a test). But when I open the membership dialog box in system>all users right after, the project BEOL does not appear in the list. I have to refresh the page manually.

Then it's a issue with the cache service. I will fix it

Oh...I saw that I forgot to exclude the knora default projects. I will fix that too

@flavens It should work now

@kilchenmann I still have the same project with the cache. After adding a user from http://localhost:4200/system/projects, the list in http://localhost:4200/system/users is not up-to-date. It updates after a manual reload of the page.

I can't reproduce the mentioned issue. Did you used browser's "previous page"-button?
I added me to the Webern project and switched to system/users and clicked on "manage project membership" and the Webern project was listed there. I did the same in reverse: In system/users I added me to the BEOL and switched to the BEOL collaboration page and I was listed there as well.
But it's true, when I use the "previous page"-button it doesn't refresh the page. This is an issue in general. I will try to fix in a quick way: Update project cache in the membership component.

@kilchenmann Another little thing: when I delete a project from the list and I want to add it again without closing/reopening the dialog box, the list is not up-to-date. So if you delete the wrong project, you have to close/open the dialog or reload the page.. Cache again I suppose.

when I delete a project from the list and I want to add it again without closing/reopening the dialog box, the list is not up-to-date.

You mean in the Membership-thing?

@kilchenmann yes in the Membership dialog box

@flavens I tried to fix the mentioned issue about updating cache. Would you have a look on it again

@kilchenmann LGTM

@flavens Thanks


Suffix not present on hooks anymore

Describe the bug
Since I upgraded to 2.2.6 and above, the suffix is not added on hooks anymore with plugin typescript-react-apollo and option typesSuffix: MySuffix.
To Reproduce
Steps to reproduce the behavior:

Install<EMAIL_ADDRESS>Generate hooks with option typesSuffix: MySuffix
Create some custom hooks calling useFindUserQueryMySuffix()
Upgrade to<EMAIL_ADDRESS>or above.
Make the exact same generation
The apollo hooks are generated without the MySuffix and this breaks all of the generated hooks imports

My GraphQL schema:

scalar Date

schema {
  query: Query
}

type Query {
  me: User!
  user(id: ID!): User
  allUsers: [User]
  search(term: String!): [SearchResult!]!
  myChats: [Chat!]!
}

enum Role {
  USER,
  ADMIN,
}

interface Node {
  id: ID!
}

union SearchResult = User | Chat | ChatMessage

type User implements Node {
  id: ID!
  username: String!
  email: String!
  role: Role!
}

type Chat implements Node {
  id: ID!
  users: [User!]!
  messages: [ChatMessage!]!
}

type ChatMessage implements Node {
  id: ID!
  content: String!
  time: Date!
  user: User!
}

My GraphQL operations:

query findUser($userId: ID!) {
  user(id: $userId) {
    ...UserFields
  }
}

fragment UserFields on User {
  id
  username
  role
}

My codegen.yml config file:

generates:
  types-and-hooks.tsx:
    plugins:
      - typescript
      - typescript-operations
      - typescript-react-apollo
    config:
      typesSuffix: MySuffix

Expected behavior
Could we have a way to workaround this new behavior ? There's nothing I can do except renaming all my imports or downgrading to 2.2.5.
Environment:

OS: OSX 11.4
packages :
"@graphql-codegen/cli": "^1.21.6",
"@graphql-codegen/introspection": "^1.18.2",
"@graphql-codegen/typescript": "^1.22.4",
"@graphql-codegen/typescript-operations": "^1.18.3",
"@graphql-codegen/typescript-react-apollo": "2.2.5",
NodeJS: v14.17.0

Additional context

Link to the fix where this behavior changed : #6001 #6002

See https://github.com/dotansimha/graphql-code-generator/pull/6213

Fix available in<EMAIL_ADDRESS>


When converting to 'format' type, existing '%' characters are not escaped

I ran into an issue when using a modulo operator (%) in a query which originally used named parameters (:foo) but had to be converted to format parameters (%s). The modulo operator is not escaped which caused the MySQLdb library to fail when inserting parameter substitutions. Here is an example.
>>> query = sqlparams.SQLParams('named', 'format')
>>> query.format('select x % :value from tbl', dict(value=10))
('select x % %s from tbl', [10])

I expected the query string to be:
select x %% %s from tbl

@kesmit13 Thanks for the report. What you expected is how the library should generate the query string. The psycopg2 library behaves similarly: the modulo operator (%)  needs to be escaped. I'll look into fixing this.

I see a similar issue, but in reverse for numeric parameters. In this case, I'm going from numeric to pyformat and the :: is not getting un-escaped.
cur.execute('select `id`, `time` from alltypes where `id` = :1 and `time` = "00::07::00"', [0])

The above results in the following query.
select `id`, `time` from alltypes where `id` = %(_1)s and `time` = "00::07::00" {'_1': 0}

Note that the :: in the time field is still there, but it should result in 00:07:00.

@kesmit13 The escape_char=True argument should solve your issue.

@kesmit13 % characters are now escaped when converting format/pyformat. This feature is in the new release 4.0.0.


qt6.qtmultimedia: add qtquick3d, ffmpeg and libva to buildInputs

Description of changes
Enables the new ffmpeg backend and VAAPI support.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 194167 run on x86_64-linux 1

6 packages built:

beamerpresenter
beamerpresenter-poppler
jami-client-qt
qt6.qt3d
qt6.qtmultimedia
qt6.qtspeech


Plugin error when extracting PSFs too close together

Hello
I wanted to report some behaviour of your plugin. It's not necessarily an issue but is maybe something to be aware of.
If points are closer together than the PSF box size then the plugin will only measure one of the points. "Extract PSFs" runs with no error, the problem comes when saving, it looks like you have built in some check to compare the number of points against the number of measurements. In the case outlined above there are fewer measurements than there are points so then upon trying to save the error ValueError: Length of values (xx) does not match length of index (yy) appears where xx is less than yy and the save cannot complete.
Obviously most people aren't going to try to fit points so close together but it's not always obvious when selecting points exactly how big the PSF box will be without a scale bar. So maybe a warning box or something should appear to warn users if they try this?
I realised because my automatic bead finding script was excluding points too close together based on euclidean distance, so at points where my beads were diagonally close together they were not being excluded by my script. I have now fixed this and included a buffer where the distance threshold is larger than the PSF box size and now it seems to work okay.
Thanks a lot
Claire

Hi @clairemitchell308,
Thank you for reporting this. This might be a bug and I will have a look.
Best wishes!


Mostly of the link are broken/expired.

Almost (if not all) of the links just returns "This content is no longer available."
We could make an "archive" and upload any glitched downloaded .webms to this repo, that's because GitHub don't have the "Expiring links" problem.

I found a Wayback Machine link of this repository (from 2022), and all the webms works because the way Wayback Machine works, but it's too slow to download all the webms and may not work on Discord.
https://web.archive.org/web/20220804194450/https://github.com/PanIntegralus/discord.webm-compilation

We could make an "archive" and upload any glitched downloaded .webms to this repo, that's because GitHub don't have the "Expiring links" problem.

I ain't gonna do this, but if you want to create a PR with this, I'll push it.

We could make an "archive" and upload any glitched downloaded .webms to this repo, that's because GitHub don't have the "Expiring links" problem.

I ain't gonna do this, but if you want to create a PR with this, I'll push it.

Ok, I'm making an PR that created a folder, and inside the folder, there's WEBMs, so people can send the link for Discord, or just download.


v-html="$options.filters.nl2br(text)" doesn't work

When I try to use it like this

  gives errors.
The error is "TypeError: _vm.$options.filters.nl2br is not a function"

@hkmsadek Sorry, I forgot to publish the update to NPM。 I have published it now, you can reinstall this package.


Escape only '|', 'n' and '' in table cells.

From what I see in Gherkin2 (explored through Cucumber-JVM), the behaviour of '' in table cell is:
'\n' -> <newline>
'\|' -> '|'
'\\' -> '\'
\<other>' -> '\<other>'

This PR makes Gherkin3 behave the same, with the following addition:
'\\n' -> '\n' (the character '' followed by the character 'n').
In Gherkin2 both '\\n' and '\\\n' becomes '\<newline>' which makes it impossible to get a string with the character '' followed by the character 'n' from a table cell.
The Objective-C fix is untested, since I (so far) have no Objective-C compiler on my Linux box.
Fixes #113.

just FYI, changing escape rules again will:

break compatibility for users that already escape characters like \\s in regular expressions
will prevent backward compatible escaping of characters other than \n and \ and |

I would prefer to see cucumber keep \ always as an escape and add in the future more characters to be escaped like \t, numeric ascii and perhaps random unicode code. Perhaps even forbid escaped characters that do not have special meaning to prevent users from using strings that may change behaviour at some point. e.g. if user puts in a table \s raise an error because \s is not s special escape and if in the future such escape is defined, then behaviour may change.
In any case taking a decision on that and sticking to it is most important as introducing syntax incompatibilities is highly disruptive.

Is this PR changing the escape rules again, or is it fixing the bug that made the behaviour of \ in table cells different from Gherkin2?

@brasmusson , I suspect this is meant as a rhetoric question but I'll answer. From my point of view it is changing behaviour as there've been a good time now all backslashes \ have been handled differently and now the fixing is an actual change in behaviour for existing users (whether or not original feature was meant like that or not).

@akostadinov Yes, the question was mostly meant as a rhetoric question, but afterwards it occurred to me:

break compatibility for users that already escape characters like \\s in regular expressions

No, also after this change \\s will work since \\ is (still) changed to \, that means that after this change both \\s and \s will produce \s.

@brasmusson, ha, you're right.
I would have preferred a couple of more escapes but as long as consensus goes with only 3, I can live with it.
Thanks.


Updated birthdays, YouTube, LaMetric, Shelly

RE-CHECK!

Automated adapter checker
ioBroker.birthdays

:thumbsup: No errors found
ioBroker.youtube

:thumbsup: No errors found
ioBroker.lametric

:thumbsup: No errors found
ioBroker.shelly

:thumbsup: No errors found

[ ] :eyes: [W171] "common.title" is deprecated in io-package.json

Add comment "RE-CHECK!" to start check anew

birthdays 01.05.2023 - OK
youtube 13.03.2023 - OK
shelly 23.04.2023 - OK
lametric - 10.06.2023 *** released today***
Releases added to stabel should have been available some time at latest repository. lametric is not even at latest because it has been built / tagged today. Please indicate if this is a hotfix or some other condition apply which requires an immidiate release to stable. Otherwise I would suggest to move lametrics to a seperated PR as the other three adapters are ok for stable yet.

Please indicate if this is a hotfix or some other condition apply which requires an immidiate release to stable.

🙄 Okay, I will re-try i a few month...

@klein0r I think of for that time, just please consider in the futurre :-)


URL validator does not match ips ending with 0

WARNING: This IP host malicious software
The url 'http://5[.]196[.]190[.]0/' should return True when validating. Although ips ending with 0 could be network address, that's not always the case.

This is related with https://github.com/kvesteri/validators/issues/49


vexflow5

@jaredjj3 this is the one

I am lost now with docker... of course it fails

In tsconfig, I think you can map imports from vexflow to vxflw-early-access.
{
  "compilerOptions": {
    "paths": {
      "vexflow": ["node_modules/vxflw-early-access"]
    }
  }
}

So, revert the import statements and try this mapping... Annoyingly you might need to update jest.config.js too:
module.exports = {
  moduleNameMapper: {
    '@/(.*)': '<rootDir>/src/$1',
    'vexflow': '<rootDir>/node_modules/vxflw-early-access',
  },
};

I'm unsure if that's needed or if that'll work.

I am lost now with docker... of course it fails

Does it work on main at HEAD? If not, I'll consider making a testing server for us to have a consistent environment to test against. The complication is that Google Chrome (which is what puppeteer is using for the image snapshot tests) renders SVG slightly differently depending on the platform.
You can always just run the tests locally with yarn jest, but expect the integration tests to fail (unless you're on the same platform as the Docker image).

can you try to get this one to run? yarn test on master runs ok

Sure, I'm just finishing some docs, then I can look at this in an hour or so.

I was able to get the tests to run in https://github.com/stringsync/vexml/commit/f2861b1e70b5181a4adb853749f4b47c1cd0f24c. However, the integration tests fail with:
[RuntimeError] Font: No txt context

Would you copy that commit and see if you get the same thing?

@jaredjj3 how do I pull this commit from github? I have no idea.

I also do not remember which yarn command was the right one to see the test results in the browser. Too much time with VexFlow

Font: No txt context

@jaredjj3 this relates to not being able to create a canvas to measure text. Does the react infraestructre not support canvas?
 /** Measure the text using the textFont. */
  measureText(): TextMetrics {
    let txtCanvas = Element.#txtCanvas;
    if (!txtCanvas) {
      // Create the canvas element that will be used to measure text in the event
      // of a cache miss.
      txtCanvas = document.createElement('canvas');
      Element.#txtCanvas = txtCanvas;
    }
    const context = txtCanvas.getContext('2d');
    if (!context) throw new RuntimeError('Font', 'No txt context');
    context.font = Font.toCSSString(Font.validate(this.#fontInfo));
    this.#textMetrics = context.measureText(this.#text);
    this.#height = this.#textMetrics.actualBoundingBoxAscent + this.#textMetrics.actualBoundingBoxDescent;
    this.#width = this.#textMetrics.width;
    this.#metricsValid = true;
    return this.#textMetrics;
  }

I also do not remember which yarn command was the right one to see the test results in the browser. Too much time with VexFlow

It used to be yarn dev. However, when I added the snapshot testing infrastructure, I removed the dev server because I didn't want us to maintain multiple snapshot sources. Someone might come along and wonder which snapshot is correct.
You will need to use yarn jest integration (local) or yarn test integration (docker) to render the examples wired up in the tests > integration directory. The snapshots get saved to tests > integration > image_snapshots and the diffs (from any test run) are in the image_snapshots > diff_output directory.
If you want to update snapshots, you'll need to run yarn test integration --updateSnapshot and you must run it in Docker because it will replicate the environment that Github actions runs with.
I think the testing infrastructure is less convenient, but it standardizes structure for us to achieve<EMAIL_ADDRESS>As you try to use it, would you let me know what parts don't work or are unclear in the root README? I'll try to update the dev workflow and README accordingly.

@jaredjj3 this relates to not being able to create a canvas to measure text. Does the react infraestructre not support canvas?

React is out of the picture now, and we're using puppeteer to render the examples in a Chrome browser. See lilypond.test.ts for how this is done.
I'm not able to do this right now, but the next step to troubleshooting this is to see if our puppeteer setup has issues with canvas. In lilypond.test.ts, temporarily comment out the tests and make a new one that creates a <canvas> and renders something with it.
(inside a test)
const canvas = document.createElement('canvas');
canvas.setAttribute('id', 'canvas');

await page.setContent(canvas);

await page.evaluate(() => {
  const canvas = document.getElementById('canvas');
  const ctx = canvas.getContext('2d');
  ctx.fillStyle = 'green';
  ctx.fillRect(50, 50, 100, 100);
});

await page.screenshot({ path: 'foo.png' });

If all that works, then puppeteer is not the problem and we need to dig further why this might not be attaching to the DOM.

Quick addendum: an even simpler approach is to do everything inside the page.evaluate callback.

@rvilarl I was able to take a look and I found the issue. The problem is with jest and jsdom because that's where the vexflow APIs are being called.
I reran the tests and got errors like:
Error: Not implemented: HTMLCanvasElement.prototype.getContext (without installing the canvas npm package)

I followed the instructions on Automattic/node-canvas and installed canvas locally. I didn't have to do anything with Docker to get it to work.
After I did that, i reran the tests and observed that they render, although the renderings seem broken. Maybe this is something we're doing wrong in this library?
snapshot, diff, test result

@jaredjj3 thanks! this looking good!
The only thing that is missing now are the fonts, the library uses them directly. This why we are getting the squares. Do you know how to use FontFace with puppeteer / jsdom? The fonts are available in<EMAIL_ADDRESS>

@rvilarl we're closer in https://github.com/stringsync/vexml/commit/64042c43e97cadd19b5cbd7c177a00ea9c0767bb, but something is still wrong. The sizing and formatting now match the snapshot, but I'm still getting the boxes. @ronyeh, I didn't see the otf files you referenced in https://github.com/vexflow/vexflow/pull/98#issuecomment-1722452632 — they had different names. What else am I doing wrong?
snapshot, diff, test result

can you share your branch? I would like to get a look into it.

Sure the branch has the same name in this repo: https://github.com/stringsync/vexml
If you develop in this repo or give me access to your fork, I can PR into the branch you've been working on.

I think I have an idea what's going on: the browser doesn't have the fonts loaded, which is why we're still getting the squares. However, when we render in jsdom, the fonts are there, which is why the spacing seems correct.

I think I have an idea what's going on: the browser doesn't have the fonts loaded, which is why we're still getting the squares. However, when we render in jsdom, the fonts are there, which is why the spacing seems correct.

@rvilarl, this was the issue. When also I load the fonts inside of the browser that puppeteer controls, it works:
snapshot, diff, test result

I will close this one and merge your branch. Thanks @jaredjj3 !!!

@rvilarl, this was the issue. When also I load the fonts inside of the browser that puppeteer controls, it works:

@ronyeh it seems that we will be able to text with puppeteer!

I'm glad you were able to figure it out!
Yes, since puppeteer (and similar testing tools like playwright) use real browsers, there is always a way to load a font and measure text using the standard HTML/CSS/JS APIs.
The hurdle we need to solve is to 1) teach developers how to do it and/or 2) have a super easy (or automated) way for VexFlow to do this upon launching. I imagine most developers will run into the empty boxes issue at some point. I did as well. I just want to make it easy so that end users will never see empty boxes on a score.
The problem with jsdom (vexflow legacy code uses it) is that it doesn't conform exactly to modern web APIs. It uses node canvas internally, and that library requires a different solution for loading fonts ahead of time: registerFont(). It also doesn't support woff2, like all modern browsers do.

@ronyeh, if there's a way you can detect whether the fonts you need are loaded (Document.fonts?), you can throw an error that has a brief description and a link to a vexflow wiki doc that has a detailed description+an enumeration of common remedies.
However, this approach would undoubtedly detract from developer experience which seems important to vexflow. I think your automated approach would be better in that regard, but I would recommend at least leaving some sort of warning artifact that the fonts were autoloaded, and that may have performance implications.


Returning html always return a HTTP 200 status code

When using this plugin the handler will always return HTTP 200 code even if status code is explicitly set
reproduction
export const app = new Elysia()
	.use(html())
	.get('/should-return-error', ({set}) => {
		set.status = 422;

		return

;
	})

it returns http code 200 instead of 422.
Most of the time it's fine. But sometimes (for example using htmx) you want to be able to return html with your error

I think I found the issue, the response will always return with status 200 here
https://github.com/elysiajs/elysia-html/blob/d8a228e1929ccca9b693d75f0175d40317e987c7/src/handler.ts#L25
And it is not updating the status received on the set property before returning the response here
https://github.com/elysiajs/elysia-html/blob/d8a228e1929ccca9b693d75f0175d40317e987c7/src/html.ts#L58

I will take a shot at this one 🏀

According to this code, using cookies or any other headers will not work as well @SaltyAom
https://github.com/elysiajs/elysia-html/blob/d8a228e1929ccca9b693d75f0175d40317e987c7/src/html.ts#L52

I ended up just making my own plugin/middleware to handle HTML rendered using JSX with Kita HTML. You don't need much as Kita by default always renders to a string. I ended up grabbing the is html-check from the Elysia HTML plugin, but handle returning HTML as suggested in one of the documentation pages. Just transform with onAfterHandle and add the one necessary content header. If you need streaming support you probably want to use the official HTML plugin though.
In tsconfig compilerOptions:
{
    "jsx": "react-jsx",
    "jsxImportSource": "@kitajs/html",
    "plugins": [{ "name": "@kitajs/ts-html-plugin" }],
}

The custom plugin module:
import { Elysia } from "elysia";

/**
 * A super fast and simple way to check if a string is HTML
 * Check for opening and closing <tags> and if they are the same
 * @param str the response
 */
export function isHTML(str: unknown): str is string {
	if (typeof str !== "string") return false;
	const trimmed = str.trim();

	return (
		trimmed.length >= 7 &&
		trimmed[0] === "<" &&
		trimmed[trimmed.length - 1] === ">"
	);
}

/**
 * Adds an onAfterHandle hook to the app that checks if the response is HTML.
 * If it is, it sets the content-type header to text/html and adds a doctype.
 * We only ever render HTML to string, so we don't need to care about streaming.
 * @returns
 */
export const htmlPlugin = () => {
	const app = new Elysia({ name: "html" })
		.derive({ as: "global" }, () => {})
		.onAfterHandle({ as: "global" }, ({ response, set }) => {
			if (isHTML(response)) {
				set.headers["content-type"] = "text/html; charset=utf-8";
				return `<!doctype html>${response}`;
			}
		});

	return app;
};


(pkg/trace) Change the telemetry proxy to respond immediately and proxy request in tghe background

What does this PR do?
Instead of proxying requests and waiting for response, we write a success immediately to the client, and spawn a goroutine that forwards the routine in the background.
To still have backpressure and not buffer too many requests, if the throughput is lower than what the backend accepts, this puts a limit of up to 100 concurrent forwarded telemetry requests, and respond with 429 if we're past this.
Motivation
We currently have a telemetry proxy endpoint in the trace agent. It forwards requests and waits for the backend response to forward the response.
The response itself has very limited value, because the EVP intake also does async handling of messages.
But the backend can be stall requests for up to 15s in most extreme cases, which blocks client libraries sending telemetry due to the synchronous nature of the proxy.
This is fine for long-lived application using APM libraries since they can maintain a background thread that sends telemetry, but lately a lot of projects have needing fire-and-forget telemetry.
In particular, there are two cases where buffering requests and returning immediately will be very helpful:

The SSI injector. It sends a telemetry metric on every successful injection, and blocks the injector process (for up to 1s. This timeout is both too large, since adding 1s to a new process startup is very bad UX, and too short since the EVP endpoint can have long latencies up to multiple tine per days, where have telemetry blips).
Crashtracking. The crashtrackers can send telemetry on SIGSEGV but waits for the telemetry to be received before exiting.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

I added a goroutine pool to forward the requests. This allows to limit the number of inflight requests as well as the number of inflight bytes

/merge


module fail with worker tier

Running the example code with the additional tier      = "Worker" option fail with:

Error: Error applying plan:

1 error(s) occurred:

* module.elastic_beanstalk_environment.aws_elastic_beanstalk_environment.default: 1 error(s) occurred:

* aws_elastic_beanstalk_environment.default: ConfigurationValidationException: Configuration validation exception: Load Balancer ListenerEnabled setting cannot be applied because AWSEBLoadBalancer doesn't exist.
	status code: 400, request id: bd7a5475-7390-4fe9-a213-a728bf9c3895

Manually commenting out all the eb settings that starts with aws:elb worked. If I can come up with some better solution I'll propose a PR.

While testing I see that even setting the ListenerEnabled settings manually to "false" yields the same exception. That means that the only way is currently (without using Terraform 0.12 dynamic blocks is to remove support for worker tier for this module, as it doesn't work along with the load balancer settings.

For now, I simply created a fork that is suitable for worker environments. It is tested to work when I change the module pointer to the worker-environment branch in my fork:
module "elastic_beanstalk_environment" {
  source    = "git::https://github.com/AlmogCohen/terraform-aws-elastic-beanstalk-environment.git?ref=worker-environment"
...
}

Hope to find a better way to fix this...

Maybe a sister module for workers is needed instead... :)

eI just ran into this problem too, however it seemed that removing anything to do with the elb (even commands that disable it) seems to allow this to work. Perhaps try that?

I opened PR #93 to fix this using Terraform 0.12 and dynamic blocks


Rename the default index 'one-by-one' to 'sequence'

There was a concern about the naming 'one-by-one' since it's confusing (see https://groups.google.com/forum/m/#!topic/koalas-dev/xzZ0VvXFsGM)
This PR proposes to rename the default index 'one-by-one' to 'sequence'.

Merged for now.


Using Ingress for spark web-ui can't load the static files

kubernetes ： 1.2
ingress-controller: gcr.io/google_containers/nginx-ingress-controller:0.8.3
spark: 2.0.0

ingress yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: spark-ingress
  namespace: default
spec:
  rules:
  - host: k8s.spark.com
    http:
      paths:
      - path: /ui
        backend:
          serviceName: spark-master-service
          servicePort: 8080

Hi , I was about to using ingress to expose my spark-web-ui from kubernetes at a specific hostname like http://k8s.spark.com/ui
previously using service to do so works just fine.
when i switch to use ingress , it seems the ui tried to load the static files from the host i specified in ingress rules just like below

Problem solved by add ingress rules to route the request for static files
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: spark-ingress
  namespace: default
spec:
  rules:
  - host: k8s.spark.com
    http:
      paths:
      - path: /ui
        backend:
          serviceName: spark-master-service
          servicePort: 8080
      - path: /static
        backend:
          serviceName: spark-master-service
          servicePort: 8080


sfu-ws Deployment Failure on Web (Successful in Local Environment)

Your environment.

Version: https://github.com/ponyo877/example-webrtc-applications folk from master(1956024) for web deploy
Browser: Google Chrome 121.0 & Firefox 122.0
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

What did you do?
I create a video and audio communication service using the WebRTC package, Pion, in Go.
I made some modifications to sfu-ws in pion/example-webrtc-applications and deployed it on the web.
https://sub.folks-chat.com/ (fail)
What did you expect?
Please let me know what can be improved.
What happened?
when I made some modifications to sfu-ws in pion/example-webrtc-applications and deployed it on the web, the ICE connection state always transitions from 'new' to 'checking' and then to 'disconnected', and I am unable to establish a video call.
(In my local environment, I was able to successfully make a video call.)
Please let me know what can be improved.
Here are the modifications I made:

Added TURN and STUN servers to the settings when creating PeerConnection

TURN server: Used account information issued by expressturn
STUN server: stun:stun.l.google.com:19302
With the above two settings, the type of Trickle ICE transitions from host->srflx->Done->relay

(Embedded index.html to dockerize)
Changed the websocket protocol in index.html from ws to wss
Placed nginx in front of the sfu-ws application
Implemented HTTPS communication by setting a certificate obtained from Lets Encrypt to nginx
Deployed by installing docker on a VM instance of Google Cloud

The above configuration is published at https://sub.folks-chat.com/ (as mentioned above, WebRTC is not implemented).
Here are the codes I used:

sfu-ws application
docker-compose

Everything is made by forking pion/example-webrtc-applications. The changes can be easily understood by looking at the following two commits:

commit 3f58dc9
commit b93304e

Thanks you, Your point was right on the money!
It was due to the fact that I was using a container, which resolved.
I solved it by adding network_mode: host to the container.
commit 36a4708


bump vispy, remove unnecessary data.copy()

Description
with the release of vispy 0.6.2, the data.copy() that we added in #613 will now incur overhead for anyone who updates vispy.  This PR updates our vispy requirement to 0.6.2 and removes the redundant data.copy()
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[x] Dependency update

References
https://github.com/vispy/vispy/releases/tag/v0.6.2
How has this been tested?

[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality

Woot! Thank you! And thank you @djhoese! =D


Change CI browser example

ember-frost-core now uses Chrome for both CI and dev environments
This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Change CI browser example in README.md to match ember-frost-core usage

I don't mind having the example say Chrome, it doesn't actually matter, since the piece of that snippet that matters is just the reporter section. Just to note though, this addon has nothing to do with frost, so what is in ember-frost-core should have no influence on what's here. These are generic ember helpers.

:+1:


fix: info passed to handler should be specific to current field

Following https://github.com/accesimpot/graphql-lookahead/pull/103

Make the GraphQLResolveInfo specific to the current field state except for info.path (it will always be the initial info.path - to be improved)
Cache values of info and fieldDef getters

:tada: This PR is included in version 1.3.1-beta.3 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


OpenAPI3: emit all properties for unreferenced schemas

Fix #2571.
BREAKING CHANGE: Since the previous behavior was to emit unreferenced schemas with Read visibility, this change can produce a breaking change in Swagger if unreferenced schemas were previously emitted that had write visibility properties stripped.

Investigating the weird cause of the "DeleteOrCreateOrUpdateOrReadItem" suffixes. It seems to be a very edgy edge case...
Playground

@markcowl the REST API specs pass with this change:


Batch Normalization with virtual_batch_size not equal to None not implemented correctly for inference time

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04.5 LTS
TensorFlow installed from (source or binary):
TensorFlow version (use command below): v2.7.0-rc1-69-gc256c071bb2 2.7.0
Python version: 3.7.12
Bazel version (if compiling from source):
GPU model and memory:
Exact command to reproduce:

Describe the problem.
The batch normalization implementation respects the virtual_batch_size parameter in both train and inference modes. As such you are unable to do inference with batch sizes that are not multiples of the virtual_batch_size. Algorithm 1 in the ghost batch norm paper makes it clear that virtual_batch_size should only be respected in train mode. See https://github.com/tensorflow/tensorflow/issues/23050 for a previous discussion, since 2018. Opening here on the direction of @tensorflowbutler
Describe the current behavior.
If the batch dimension is not a multiple of virtual_batch_size  tensorflow raises:
tensorflow.python.framework.errors_impl.InvalidArgumentError: Exception encountered when calling layer "batch_normalization" (type BatchNormalization).

Input to reshape is a tensor with 784 values, but the requested shape requires a multiple of 25088 [Op:Reshape]

Call arguments received:
  • inputs=tf.Tensor(shape=(1, 28, 28, 1), dtype=float32)
  • training=False

Describe the expected behavior.
The layer should normalize using the saved statistics from train time - essentially ignoring the virtual_batch_size
Contributing.

Do you want to contribute a PR? (yes/no): no

Standalone code to reproduce the issue.
import tensorflow as tf
import numpy as np

virtual_batch_size = 32

x_train = np.random.random(size=[4*virtual_batch_size, 28, 28, 1])
x_test = np.random.random(size=[virtual_batch_size, 28, 28, 1])
x_inference = np.random.random(size=[1, 28, 28, 1])

bn_layer = tf.keras.layers.BatchNormalization(virtual_batch_size=virtual_batch_size)

assert bn_layer(x_train) is not None
assert bn_layer(x_test, training=False) is not None

# fails on this line:
bn_layer(x_inference, training=False)

https://colab.research.google.com/drive/1msCAtSzBAhwmegi41Bs5bgf6PsHLYtg5?usp=sharing

@ccurro,
I am able to reproduce the issue reported in colab with TF 2.7.0. Please find the gist here. Thanks!

Triage: keeping this open for contribution as the team doesn't currently have the bandwidth.

@rchao @ccurro
Correct me if I am wrong. Arent ghost batches like mini batches. That is the ghost batched will be subset of the batch?
So the batch size must be divisble by ghost batch number which is exactly what is recommended by keras-team in this line of comment
So here the error is raised since 1 cannot be divided by 32.

@old-school-kid That is true when training=True but when training=False you should be able to have any batch size. virtual_batch_size should have no effect during inference.

@ccurro,
The related PR #17065 was merged and also tried to execute the mentioned code on tf-nightly(2.14.0-dev20230508) and it was executed without any issue/error. Kindly find the gist of it here.
https://github.com/keras-team/keras/blob/master/keras/layers/normalization/batch_normalization.py
Thank you!

Looks good! Thanks @tilakrayal :slightly_smiling_face:


RR-DE-0002: Set Validity to 180 from 183

Version 1.1.0 of the CertLogic specification supports the + months/years for plusTime, and version 0.8.0 of certlogic-js supports that specification, and is used here. You could consider upping the EngineVersion to 1.1.0 and perform “+ 6 months” if you want, and if you're certain that the {Cert|Json}Logic engine you use supports that as well.
In any case: approved.

@f11h Can you let me know whether you want to follow up on the previous comment, or want to merge this PR as-is?

As for now it let it as it is because or "real rule writer" is on vacation.


delete endpoint does keep consuming array based on index instead of object id -> if object not present throw error and 404!

Closed by last commit


Update sendtoaddress

What current issue(s) does this address, or what feature is it adding?

Adds non-zero send provision as discussed here: https://github.com/CityOfZion/neo-python/pull/607#issuecomment-424250715
Adds improved test coverage

How did you solve this problem?
Trial and Error
How did you make sure your solution works?
Unittest
Are there any special changes in the code that we should be aware of?
No
Please check the following, if applicable:

[x] Did you add any tests?
[x] Did you run make lint?
[x] Did you run make test?
[x] Are you making a PR to a feature branch or development rather than master?
[x] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage increased (+0.2%) to 79.109% when pulling 9f37bf39ed74ec4c55b0f0527e4664b7edeeff17 on jseagrave21:update-sendtoaddress into 3bec0d8e027ba93179adbfa7aaa5f258c14bcdfd on CityOfZion:development.


Changed "class" for atomtypes 151, 152, 153 on 'oplsaa.xml'

The "class" on opls_151, opls_152, and opls_153 SMARTS strings were updated.  This should fix missing bond information for alkyl chlorides.

The changes to the OPLS XML look good.  Just need to remove version.py from the PR and we should be good to merge, although I'll need to look a bit more into why the AppVeyor builds are failing...

The Appveyor build for Python 3.4 is failing, but this is because we're now only supporting 2.7 and 3.5, so I'm going to go ahead and merge this PR and then edit the Appveyor.yml file so that we no longer test on 3.4.


[StarRocks On ES] Support ES 8.x

Elasticsearch 7.x, type was removed from ES mapping, default type is _doc
7.0 reference
From Elasticsearch 8.x
a. Specifying types in requests is no longer supported,
b. The include_type_name parameter is removed
7.17 reference

If the version of Elasticsearch is 8.x, do not specify the type when creating the table， such as
CREATE EXTERNAL TABLE `es8x` (
  `k1` varchar(20) NULL COMMENT "",
  `k2` varchar(20) NULL COMMENT ""
) ENGINE=ELASTICSEARCH
COMMENT "ELASTICSEARCH"
PROPERTIES (
"hosts" = "http://<IP_ADDRESS>:9200",
"index" = "test_index"
);

If the version of ES is greater than or equal to 7.x, it is recommended to no longer specify type
Known compatibility issues Please Note：
If the table ( only for 8.x ES) was created before upgrading the version that contains this PR, you need to delete the created table and recreate it after the upgrade
What type of PR is this：

[x] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes https://github.com/StarRocks/starrocks/issues/7823
Problem Summary(Required) ：

[FE PR Coverage check]
:disappointed: fail : 4 / 11 (36.36%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/EsScanNode.java
0
2
00.00%

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
2
00.00%

:large_blue_circle:
com/starrocks/catalog/EsTable.java
3
6
50.00%

:large_blue_circle:
com/starrocks/external/elasticsearch/MappingPhase.java
1
1
100.00%

[FE PR Coverage check]
:disappointed: fail : 4 / 11 (36.36%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/EsScanNode.java
0
2
00.00%

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
2
00.00%

:large_blue_circle:
com/starrocks/catalog/EsTable.java
3
6
50.00%

:large_blue_circle:
com/starrocks/external/elasticsearch/MappingPhase.java
1
1
100.00%

[FE PR Coverage check]
:disappointed: fail : 4 / 11 (36.36%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/EsScanNode.java
0
2
00.00%

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
2
00.00%

:large_blue_circle:
com/starrocks/catalog/EsTable.java
3
6
50.00%

:large_blue_circle:
com/starrocks/external/elasticsearch/MappingPhase.java
1
1
100.00%

[FE PR Coverage check]
:disappointed: fail : 4 / 11 (36.36%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/EsScanNode.java
0
2
00.00%

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
2
00.00%

:large_blue_circle:
com/starrocks/catalog/EsTable.java
3
6
50.00%

:large_blue_circle:
com/starrocks/external/elasticsearch/MappingPhase.java
1
1
100.00%

run starrocks_fe_unittest

[FE PR Coverage check]
:disappointed: fail : 4 / 11 (36.36%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/EsScanNode.java
0
2
00.00%

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
2
00.00%

:large_blue_circle:
com/starrocks/catalog/EsTable.java
3
6
50.00%

:large_blue_circle:
com/starrocks/external/elasticsearch/MappingPhase.java
1
1
100.00%


Import more iCalendar feeds

https://www.gugelhupf-dresden.de/tanz-in-dresden/calendar/icslist/calendar.ics: Not very helpful, missing URL and timezone.

https://kalender.digital/574d155c91900caea879 has an iCalendar feed which might be worth adding.

https://www.folkclub-marburg.de/wp/ has links to an iCalendar feed.


Please ignore this. This is a bug bounty test... sfxxdw

Please ignore this. This is a bug bounty test... sfxxdw

 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.


Create Alert - Hydrological / Meteorological Mislabeled

Currently when you create an application the field labeled "Meteorological Conditions" actually populates the "Hydrological Conditions"
the data entry boxes for each of these fields is mislabeled.

See PR: https://github.com/bcgov/nr-rfc-alertauthoring/pull/122


Improve join classification by optimizing the expression of the join condition

Problem Statement
We recently had various issues where joins were wrongly assigned to their actual join implementation. This can cause sub-optimal performance e.g. when a nestedloop-join is used when a hash-join could be used. It can also cause wrong results when a hash-join is used and the join condition is not applicable for hash-value generation. See https://github.com/crate/crate/issues/15368, https://github.com/crate/crate/issues/16173 https://github.com/crate/crate/issues/16227, https://github.com/crate/crate/issues/15324. We have a similar problem here https://github.com/crate/crate/issues/15443
Possible Solutions
It will be easier to classify the join condition when the corresponding expression is simplified. Expressions can be optimized by evaluating constants and applying algebraic simplifications.  This makes processing easier, and less error-prone.
Here are some examples of common simplifications:

a > 2 AND a > 2 can be simplified to a > 2
a > 2 OR a > 2 can be simplified to a > 2
a = true and a != false to a when a is of boolean type
a = false and a != true to !a when a is of boolean type
a = a to true
true = true and false = false to true
false = true and true = false to false
!!a to a
a = null to null
a OR (a AND b) to a (if b not null)
(a AND b) OR a to a (if b not null)
a AND (a OR b) to a (if b not null)

There are many possibilities see, https://github.com/apache/datafusion/blob/main/datafusion/optimizer/src/simplify_expressions/expr_simplifier.rs for more details.

Hi @kotlalokeshwari098. First of all, thank you for your interest in contributing to CrateDB.
I'd like to let you know that this issue can be rather complex, and maybe it's better to get started with an issue which is marked with good first issue label. Nevertheless, you're more than welcome to give it a try if you want, but we have decided not to assign issues to external contributors, please see our guide: https://github.com/crate/crate/blob/master/CONTRIBUTING.rst#issue-assignments

Thank you for your response and for the guidance! I appreciate the suggestion to start with an issue marked as good first issue. I’m eager to begin my journey in open-source contribution and would love any advice or recommendations on where to start or which issues might be suitable for beginners.
If there are any specific areas you think I should focus on, please let me know. Thank you!

@kotlalokeshwari098 This is a good ticket to get started https://github.com/crate/crate/issues/2036

Thank you for pointing me to ticket #2036! I’m excited to get started on this issue and will review it thoroughly. If I have any questions or need clarification, I’ll be sure to reach out. Thanks again for your support!

Thank you for pointing me to ticket #2036! I’m excited to get started on this issue and will review it thoroughly. If I have any questions or need clarification, I’ll be sure to reach out. Thanks again for your support!


Unknown error occur after query

by using this schema
model User {
  id              String   @default(cuid()) @id
  email           String   @unique
  password        String
  name            String?
  firstName       String?
  lastName        String?
  createDate      DateTime @default(now())
  profileImageUrl String?
  eventFollow     Event[]
}

model Event {
  eventId              String         @default(cuid()) @id
  eventNameTH          String?
  eventNameEN          String?
  eventNameTHLowerCase String?
  eventNameENLowerCase String?
  slug                 String?
  createDate           DateTime       @default(now())
  eventDate            DateTime?
  eventDateStart       DateTime?
  eventDateEnd         DateTime?
  bookableDateStart    DateTime?
  bookableDateEnd      DateTime?
  priceStart           Int?
  priceEnd             Int?
  organizer            String?
  latitude             Float?
  longtitude           Float?
  location             String?
  keyword              String?
  locationTextShowTH   String?
  locationTextShowEn   String?
  provinceTH           String?
  provinceEN           String?
  provinceLowerCase    String?
  eventAdminCreator    Admin?         @relation(references: [adminId], name: "eventAdminCreator")
  raceType             String?
  linkUrl              String?
  coverPhotoUrl        String?
  coverPhotoUrl_resize String?
  thumbnailPhotoUrl    String?
  youtubeUrl           String?
  eventGroup           EventGroup?    @relation(references: [eventGroupId])
  descriptionTH        String?
  descriptionEN        String?
  comment              Comment[]
  lastUpdateTime       DateTime?      @updatedAt
  lastUpdateAdmin      Admin?         @relation(references: [adminId], name: "lastUpdateAdmin")
  followBy             User[]
  eventScore           Float?
  distance             DistanceType[]
  isOfficialPartner    Boolean?
}

model EventGroup {
  eventGroupId              String   @default(cuid()) @id
  eventGroupName            String
  createTime                DateTime @default(now())
  slug                      String?
  event                     Event[]
  eventGroupImageUrl        String
  eventGroupImageUrl_resize String
  eventGroupAdminCreator    Admin    @relation(references: [adminId], name: "eventGroupAdminCreator")
  lastUpdateTime            DateTime @updatedAt
  lastUpdateAdmin           Admin    @relation(references: [adminId], name: "eventGroupAdminLastUpdate")
}

model Comment {
  commentId    String         @default(cuid()) @id
  comment      String
  createTime   DateTime       @default(now())
  user         User           @relation(references: [id])
  event        Event          @relation(references: [eventId])
  approve      Boolean
  photo        CommentPhoto[]
  commentScore Float
  approveBy    Admin          @relation(references: [adminId])
  approveTime  DateTime
}

model CommentPhoto {
  commentPhotoId String  @default(cuid()) @id
  imageUrl       String
  comment        Comment @relation(references: [commentId])
}

model DistanceType {
  distanceTypeId String @default(cuid()) @id
  distance       Float
  event          Event  @relation(references: [eventId])
}

model Admin {
  adminId              String       @default(cuid()) @id
  email                String?
  password             String?
  firstName            String?
  lastName             String?
  createDate           DateTime     @default(now())
  event                Event[]      @relation(references: [eventId], name: "eventAdminCreator")
  eventLastUpdate      Event[]      @relation(references: [eventId], name: "lastUpdateAdmin")
  eventGroup           EventGroup[] @relation(references: [eventGroupId], name: "eventGroupAdminCreator")
  eventGroupLastUpdate EventGroup[] @relation(references: [eventGroupId], name: "eventGroupAdminLastUpdate")
  comment              Comment[]
}

Can you please also paste the query here? I can't infer that 😅

@pantharshit00 this query
query searchEvent($searchString : String, $startDate : DateTime, $endDate : DateTime
,$province : String, $raceType: String, $fromDistance: Float, $toDistance : Float)
{
events(where: {
AND: [
{OR: [{
eventNameTHLowerCase: {
contains: $searchString
}},
{
eventNameENLowerCase: {
contains: $searchString
}
}]
},
{
location: {
contains: $province
}
}
,
{
raceType: {
equals : $raceType
}
},
{
eventDateStart: {
gte : $startDate
}
},
{
eventDateStart : {
lte : $endDate
}
}
,{
distance: {
some: {
AND: [
{distance: {
gte: $fromDistance
}},
{
distance: {
lte : $toDistance
}
}
]
}
}
}
]
}){
eventNameTH
eventNameEN
createDate
eventDateStart
eventDateEnd
coverPhotoUrl
distance{
distance
}
location
raceType
}
}
but it happen sometime, not all the time. after new npm start, this error seem to disappear for a moment then occur again

I am unable to reproduce this:

Can you please run your query in debug mode(run export DEBUG=*) to enable it and paste the output of the failing query here.
I used<EMAIL_ADDRESS>binary version: e7579bd35e0938dbf773f1706c098a0d14a5a038

this is the first error

after that when u query anything, it repeat this error below until u restart the server, then the error disappear and repeat again from the first error

@pantharshit00

now i open the debug and wait for error to happen

this is after open debug
@pantharshit00

@pantharshit00

Can you please send me a dump of your database if possible? Seems like some value in the database is causing this.
Also, https://github.com/prisma/photonjs/issues/357 might improve the error message

@justicejoe Since #357 is fixed, can you please try this again and see what the actual error is? Thanks.

I think you mean https://github.com/prisma/photonjs/issues/357

Ping @justicejoe  about Harshit's last followup. We want to move this issue forward, but need your help.

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.


Add option to specify event and configuration path when creating pipeline via API and CLI

Partially address  #1668 (UI missing)

Codecov Report
Patch coverage: 35.71% and project coverage change: -0.01 :warning:

Comparison is base (b90e790) 39.15% compared to head (b363610) 39.14%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1722      +/-   ##
==========================================
- Coverage   39.15%   39.14%   -0.01%
==========================================
  Files         167      167
  Lines       10787    10792       +5
==========================================
+ Hits         4224     4225       +1
- Misses       6290     6294       +4
  Partials      273      273

Impacted Files
Coverage Δ

server/model/pipeline.go
0.00% <ø> (ø)

server/model/secret.go
48.07% <0.00%> (ø)

server/pipeline/create.go
0.00% <0.00%> (ø)

server/model/const.go
44.44% <66.66%> (ø)

server/forge/configFetcher.go
95.23% <100.00%> (+0.04%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Closing as this introduces risks as discussed in the maintainer channel recently.


[SPARK-50497][SQL] Fail queries with proper message if MultiAlias contains non-generator function

What changes were proposed in this pull request?
MultiAlias fails if the underlying function is not a generator.
Why are the changes needed?
Syntax for multi aliasing should return proper error and not fail in check analysis with unresolved.
Does this PR introduce any user-facing change?
Yes, error message changes
How was this patch tested?
Added test.
Was this patch authored or co-authored using generative AI tooling?
Yes.

@MaxGekk please review this.

@vladimirg-db for context.

thanks, merging to master!


[CVE-2019-8331] Fix security issue related with [data-template]

Upgrade the code to prevent: https://nvd.nist.gov/vuln/detail/CVE-2019-8331
We won't actually merge this pull request.
To check how this branch diverges from the original one, click here

Do not delete this branch!
⚠


Support for DML Statements

Is there support for any DML available e.g. UPDATE, DELETE, MERGE on the datasets as I could not find them on the example.
If no, what are the suggested options.

I would also look for support for any kind of SQL Statement to Execute, not necessarily DML, but for example also Exec procedure.  As this was possible with the prev version of the drivers ( with com.microsoft.azure:azure-sqldb-spark:1.0.2 I could just do sqlContext.sqlDBQuery and the Config could contain any String as queryCustom). Maybe we just miss examples for that.

I am also really looking forward to this!
It would greatly increase the usability of the connector and allow us to do some proper ETL from/to Databricks/Spark

Merge Functionality will be super helpful and avoid multiple code base in SQL and Databricks. Looking forward to Merge functionality either supporting Delta table or with Parquet files.

Merge Functionality will be super helpful and avoid multiple code base in SQL and Databricks. Looking forward to Merge functionality either supporting Delta table or with Parquet files.

Hi all,
As mentioned in #21
While the older Azure SQL DB Spark connector did include this functionality to execute DML and DDL statements, since this connector is based on the Spark DataSource APIs, it is out of scope.
This functionality is provided by libraries like pyodbc.

Hi all,
As mentioned in #21
While the older Azure SQL DB Spark connector did include this functionality to execute DML and DDL statements, since this connector is based on the Spark DataSource APIs, it is out of scope.
This functionality is provided by libraries like pyodbc.


keep the resize function the same in test time the same with training time

The result may be affected  when   the implementation of resize function in inference time  and training time is inconsistent,so I changed the code in inference time to keep them same.

The only difference I see is that the images might be larger than 1333 pixels, but is this a problem?

The only difference I see is that the images might be larger than 1333 pixels, but is this a problem?

Yes,when the images are very large,for example in my own dataset,it may cause large error as it haven't been trained in such size,which took me several weeks to find out this problem.

Ok, fair enough.


Batch Running Scripts

We have some batch running scripts, but it might be nice to consolidate them into something easy for users.
Currently, I run a batch script for all functions in a program via
# prime the cache
echo tar_dirname | parallel --eta --joblog ./results/log --timeout 3000 -j 6 './run_single.sh {} > results/{}'
cat names.txt | parallel --eta --joblog ./results/log --timeout 1000 -j 6 './run_single.sh {} > results/{}'

Where names.txt is a file with all the function names I want to check and run_single.sh contains
bap wp \
  --function=$1 \
  --num-unroll=0 \
  --no-byteweight \
  --mem-offset \
  --show=bir,paths \
  --compare-post-reg-values=R12,R13,R14,R15,RBX,RSP,RBP,RAX \
  ../binaries/tar_amd64_linux_gcc_o0_dynamic \
  ../binaries/tar_amd64_linux_gcc_o0_dynamic-rewritten

We should have some kind of script that generalizes out these various parameters and passes them through. Also names.txt should be generated easily.

names.txt can be generated with bap --no-byteweight -dsymbols <binary-name>

The script should encompasses all of the iterations of running wp on our example binary:

bap -dsymbols --no-byteweight orig > names.txt to get all subroutines
run all subs with mem-offset turned on
grab the sats, and run with mem-offset flag off
grab the sats, and run with all registers specified in the pointer-reg flag
parse the results from the results directory into a giant csv that shows: sub name, z3 result, time, (possibly line count)

Fixed in #292.


Update proc-macro dependencies

Choose one: is this a 🐛 bug fix, a 🙋 feature, or a 🔦 documentation change?

Checklist

[x] tests pass (at least the ones that did before)
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added

Context
fixes #11

Semver Changes
patch

v1.0.2 :tada:


Add "Propagate Access Control Lists..." for root directories

Due to a bug in the JS SDK, we were unable to ship "Propagate Access Control Lists..." for root directories. Once the SDK is fixed we will be able to enable this scenario.

SDK bug: https://github.com/Azure/azure-sdk-for-js/issues/12813


feat: add kratos quick start

 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.shenqidebaozi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Bug]: Docs link in Registry is incorrect

What happened?
The Registry uses to https://go.microsoft.com/fwlink/?linkid=2224253
This points to the OLD docs and not the NEW docs.
Registry site: https://mcr.microsoft.com/en-us/product/azure-databases/data-api-builder/
Version

What database are you using?
Azure SQL
What hosting model are you using?
Container Apps
Which API approach are you accessing DAB through?
REST, GraphQL
Relevant log output
No response
Code of Conduct

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

This has been fixed.


Add possibility to use markup in the site definition

Currently, the site definition is loaded, as is without processing. Adding a markup (freemarker, for example) would allow the construction of dynamic site definitions.
It would enable more extensive projects to define rules for attachments, child pages, etc. in the parent pom. These would then evaluate the proper result in the child project.
I'll prepare the PR.

Hi @LZaruba
This is a great idea and thanks for your PR,  however, starting from this idea, I would implement possibilty to plug different "template engine" and not force to use one.
So I'll think about how to implement it

fix released in 6.7 version


Merging UKB SV Files

Hi,
In the recent release of 500,000 genomes, the UKB has provided SV calls, but only in bgzipped sample-level vcf files.
I've tried merging these files in groups to create a pVCF- after unzipping each vcf, as survivor doesn't seem to take .gz files? - but the file size is growing such that I can't merge those groups (I get a "Killed" error). I tried trimming the vcf files to just genotypes in the FORMAT field using bcftools - but then the merging was odd, in that when merging two files with 9000 people each in, I got only 2 individuals in the output
Do you have any suggestions for how I could perform this analysis?
Cheers,
Gareth

I should add - I'm using a 72-core machine - each group file (approx 9k people) is ~ 270GB.


Allow for direct unpublish/delete when user is authenticated and authorized

We currently don't allow unpublish/delete unless the document is removed, which is a complicated user experience.
When authentication is enabled we could support a direct unpublish/delete and offer that in sidekick.

:tada: This issue has been resolved in version 6.27.0 :tada:
The release is available on:

GitHub release
v6.27.0

Your semantic-release bot :package::rocket:


The sri lankan flag is missing

I noticed that the sri lankan flag(🇱🇰 ) is missing. Could you add it please

It's there isn't it? Under the 'Country Flag'...

As mentioned by @alanwuha, it's under the Country Flag category with the shortcode :sri_lanka:.


sg200x: the pinmux tables are incomplete

For example, the pin XGPIOB[14] is missing.

For example, the pin XGPIOB[14] is missing.

Can you please details the problem, in what product and in what section?  We have separated TRM for SG2002 and SG2000.
I double checked the document, seems the problem is in section "10.1.2 FMUX Registers Description" for SG2000, and it lacks some pin definition. I compare with the pin out xls sheet @ https://github.com/sophgo/sophgo-hardware/blob/master/SG200X/03_SG2000/04_SG2000_PINOUT.xlsx
Is this the problem?

Yes this is the problem i'm talking about.
Also, I wasn't aware of the xls document. It may be worth it to mention it in the manual.

Yes this is the problem i'm talking about.
Also, I wasn't aware of the xls document. It may be worth it to mention it in the manual.

Yes, actually the content of pinmux info in TRM is from that xls sheet, and seems something are missed for sg2000.
Directly providing the link to xls doc in TRM may be a better idea, we are considering do like this.

Fixed with commit: a69a1c4.
We have released v1.01 to include this change.
https://github.com/sophgo/sophgo-doc/releases/tag/sg2002-trm-v1.01
https://github.com/sophgo/sophgo-doc/releases/tag/sg2000-trm-v1.01


Suggested change to make Penny source easier to update

I brought in the update of Shield, and felt that updating Penny while it is interleaved with the rest of my app had become too messy. It's also not possible to update Penny by simply doing a git update from your repository. My solution was to move Penny to its own directory, separate from my app, and make this monster of an app.cr file to put Penny and my app together. It thus works with no modifications to Penny and I can git update without pain. Require statements were expanded to be per-directory in a few places, because I am avoiding pulling in your versions of layouts, api_action and browser_action, base_model, etc. Hopefully you can think of a neater way to do this. It strikes me that this would also work with a shard, which would make updating even cleaner. Thanks!
require "./queries/mixins/**"
require "./queries/**"
require "./operations/mixins/**"
require "./operations/**"
require "../../penny/src/operations/**"
require "./serializers/base_serializer"
require "../../penny/src/serializers/bearer_login_serializer"
require "../../penny/src/serializers/login_serializer"
require "../../penny/src/serializers/user_serializer"
require "./serializers/**"
require "./emails/base_email"
require "./emails/**"
require "../../penny/src/emails/email_confirmation_request_email"
require "../../penny/src/emails/guest_password_reset_request_email"
require "../../penny/src/emails/login_notification_email"
require "../../penny/src/emails/password_change_notification_email"
require "../../penny/src/emails/password_reset_request_email"
require "../../penny/src/emails/user_email_confirmation_request_email"
require "../../penny/src/emails/user_welcome_email"
require "../../penny/src/emails/welcome_email"
require "./actions/mixins/**"
require "./actions/api_action"
require "./actions/browser_action"
require "../../penny/src/actions/api/**"
require "../../penny/src/actions/bearer_logins/**"
require "../../penny/src/actions/current_login/**"
require "../../penny/src/actions/current_user/**"
require "../../penny/src/actions/email_confirmations/**"
require "../../penny/src/actions/mixins/**"
require "../../penny/src/actions/password_resets/**"
require "../../penny/src/actions/users/**"
require "./actions/**"
require "./components/base_component"
require "./components/**"
require "./pages/mixins/**"
require "./pages/main_layout"
require "./pages/auth_layout"
require "../../penny/src/pages/bearer_logins/**"
require "../../penny/src/pages/current_login/**"
require "../../penny/src/pages/current_user/**"
require "../../penny/src/pages/email_confirmations/**"
require "../../penny/src/pages/mixins/**"
require "../../penny/src/pages/password_resets/**"
require "../../penny/src/pages/users/**"
require "./pages/**"
require "./handlers/base_handler"
require "./handlers/**"
require "../config/env"
require "../config/**"
require "../db/migrations/**"
require "./app_server"

Penny is a starter template, so pulling it out defeats the purpose. One may add and remove stuff as one wants, so it's difficult to figure out what goes in and what doesn't.
I would advise against updating Penny itself for every Shield release. Instead, check penny.diff for any changes, and apply them manually as required. There's probably a better way, but this works for now.


GIoULoss doesn't go below 1

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04 LTS
TensorFlow version and how it was installed (source or binary): 2.1.0 (binary)
TensorFlow-Addons version and how it was installed (source or binary):0.7.1 (binary)
Python version: 3.6.9
Is GPU used? (yes/no): yes

Describe the bug
I am using the GIoULoss to train a small CNN using keras which predicts the (x,y) of a bounding box. The training starts with loss at 1.04 and stops decreasing after 1.0. I tried changing the architecture and epochs but it gets stuck at val_loss=1.0
Code to reproduce the issue
def PreprocessLabels(row,col,rad):
    # Convert (row,col) & radius to (x1,y1) & (x2,y2)
    # This helps us to shape the problem as bounding box prediction problem
    # where we can use GIoU as our loss function.
    x1 = int(row)-int(rad)
    y1 = int(col)-int(rad)
    x2 = int(row)+int(rad)
    y2 = int(col)+int(rad)
    return [y1,x1,y2,x2]

    def DataGenerator(FileList,mode='train'):
        DataInput, DataLabels = [],[]
            for img_name in FileList:
                img = cv2.imread(img_name,2)
                row,col,rad = img_name.split("_")[2:]
                rad = rad.split(".")[0]
                DataInput.append(img)
                DataLabels.append(PreprocessLabels(row,col,rad))
        return np.expand_dims(np.array(DataInput),axis=3),np.array(DataLabels)

def Model():
    model = Sequential()
    model.add(Conv2D(64,kernel_size=3,activation='relu',input_shape=(200,200,1)))
    model.add(Conv2D(64,kernel_size=5,activation='relu'))
    model.add(Conv2D(32,kernel_size=3,activation='relu'))
    model.add(Flatten())
    model.add(Dense(4,activation='linear',use_bias=False,kernel_initializer="he_normal"))
    return model

FileList = glob("images/*.png")
x,y = DataGenerator(FileList)

model = Model()
model.compile(optimizer='adam',loss=GIoULoss())
model.fit(x,y,batch_size=64,epochs=10,verbose=1,validation_split=0.2,shuffle=True,)

I am having the same problem as well, the loss reaches 1 and stays there!

I am having the same problem as well, the loss reaches 1 and stays there!

Same problem here...

Same problem as well.

Seems like changing the batch size fixed it for me

Seems like normalizing the data fixed it for me

Seems like adding normalization fixed it for me

Hi All. Can someone please confirm if this issue has been fixed? The last comment is too cryptic. Thanks in advance!


Cross compile to Scala.js

Thanks for this great library.
I kindly request to publish it cross-compiled to Scala.js so that it can be used in hybrid (Scala/Scala.js) projects.
Thank you!

Sorry for delay in getting to this.  I initially missed the issue.
I have republished the 0.6.1-SNAPSHOT with cross compile versions for JVM and Scala.js.
Let me know if it doesn't work.
Thanks.

HI @garyKeorkunian , sorry I couldn't test until now.
It seems to working just fine, thank you very much!


process on the border of mask and original images

sorry to bother you again.
I notice that you process the border of dataset masks and original images during inference:

I do the process according to paper, but output bad results! would you like to provide the process code ?
Best

thank you for your kindly reply and i will try the blur trick code.
wIsh you have a nice weekend

Hey I get this error when running the inference script:
File "/home/humaid/Desktop/realfill/infer.py", line 83, in
result = Image.composite(result, image, mask_image)
File "/home/humaid/mambaforge/envs/realfill/lib/python3.10/site-packages/PIL/Image.py", line 3363, in composite
image.paste(image1, None, mask)
File "/home/humaid/mambaforge/envs/realfill/lib/python3.10/site-packages/PIL/Image.py", line 1738, in paste
self.im.paste(im, box, mask.im)
ValueError: images do not match


Is it possible to add doctest support?

Currently I am running doctest every time when my source file is saved. (I use vim write file trigger)
It would be nice if ghcid also run doctest when file is changed.
ghcid only run once and exit when I try  ghcid --command 'doctest source.hs'

ghcid --command 'cabal new-repl' --test ':!doctest source.hs' also doesn't work.
Some error is reported but I can't read because the screen keep flickering.

The first of those strings definitely won't work - the command has to be what you use to start ghci. The second looks plausible - does it work if you omit the --test? Can you hit Ctrl-C in the terminal and thus find out what the error is?

I am trying with data61 fp-course
ghcid --command 'cabal new-repl' seem working. if my code failed to compile it will give the error. if my code is compiled it give me this
All good (27 modules, at 08:24:27)

but it also give
Reloading...
  Error when waiting, if this happens repeatedly, raise a ghcid bug.
  "/data/learn/haskell/fp-course/(0.01 secs, 763,864 bytes)/src/": can't watch what isn't there!: does not exist

For ghcid --command 'cabal new-repl' --test ':!doctest src/Course/MoreParser.hs'
it give the same error above and Interrupted
Interrupted.

All good (27 modules, at 08:31:29)
Running test...

But the doctest didn't work. it should report some failed test.
For example, If i run cabal new-repl from bash prompt and :!doctest  in repl's prompt I got this
λ> :!doctest src/Course/MoreParser.hs
Loaded package environment from /data/learn/haskell/fp-course/.ghc.environment.x86_64-linux-8.4.3
Loaded package environment from /data/learn/haskell/fp-course/.ghc.environment.x86_64-linux-8.4.3
src/Course/MoreParser.hs:268: failure in expression `parse hexu "u0010"'
expected: Result >< '\DLE'
 but got: *** Exception: todo: Course.MoreParser#hexu
          CallStack (from HasCallStack):
            error, called at src/Course/MoreParser.hs:285:3 in main:Course.MoreParser

Problem is you have +s in a .ghci file somewhere. I fixed that as part of #162, but hadn't made a release since I was planning to do more changes, but got delayed. I've now made a release so 0.7.1 should fix it.

Build profile: -w ghc-8.4.3 -O1
In order, the following will be built (use -v for more details):
 - ghcid-doctest-<IP_ADDRESS> (exe:ghcid-doctest) (ephemeral targets)
Preprocessing executable 'ghcid-doctest' for ghcid-doctest-<IP_ADDRESS>..
GHCi, version 8.4.3: http://www.haskell.org/ghc/  :? for help
Loaded GHCi configuration from /data/works/dotfiles/_ghci
[1 of 1] Compiling Main             ( Main.hs, interpreted )
Ok, one module loaded.
*Main
λ> *Main
λ> *Main INTERNAL_GHCID
it :: ()
it :: ()

All good (1 module, at 17:33:05)
Running test...

it :: ()
it :: ()
Loaded package environment from /home/wizzup/tmp/ghcid-doctest/.ghc.environment.x86_64-linux-8.4.3
Loaded package environment from /home/wizzup/tmp/ghcid-doctest/.ghc.environment.x86_64-linux-8.4.3
Main.hs:5: failure in expression `1 + 1'
expected: 1
 but got: 2

Examples: 1  Tried: 1  Errors: 0  Failures: 1

...done

Reloading...
  Error when waiting, if this happens repeatedly, raise a ghcid bug.
  "/home/wizzup/tmp/ghcid-doctest/it :: ()/": can't watch what isn't there!: does not exist

All good (1 module, at 17:33:06)
Running test...

What is causing it :: () to appear at the end of each line? That's going to be the problem. I suspect it's your .ghci at fault, which you haven't put in the repo for the bug.

Thanks for the new release. I just test version 0.7.1 and it is is working.

doctest now stop at the first error
no more reloading error
I can now use +t and +s in my .ghci


fix: map RepoSync RoleBinding to RepoSync namespace

The RoleBinding created for RepoSyncs is actually in the namespace of the RepoSync, rather than the controller namespace. This change fixes the watch configuration and mapping logic to correctly map the RoleBinding.

/assign @karlkfi


Fio: Hostdir support

Hostdir parameter is helpful to measure disk speed on the nodes. Fio should be extended to enhance our flexibility.

@wgershwitz Can you please elaborate further on this? What exactly would this hostdir parameter do?

@julio-santiesteban : sorry, it is really hostpath and not hostdir. updated the description, you can find k8s reference there now.


Make JSON parsing more robust

Log invalid JSON errors on the console, and always return either a parsed object (for correct JSON) or an empty object (for incorrect or absent JSON).

Change will be made here instead: https://github.com/NCI-Agency/anet/commit/71bb283dc2ec5701aca10f0f9d243ac818b97edd


Please add DateTimeOffset overloads

For all of the things like IssuedAt that take a DateTime, would you please add an overload that takes a DateTimeOffset?

@daviddesmet I see you merged this, thanks, but it doesn't look like you push a new release to NPM

@grosch oh yeah, I forgot to push the draft release. It will be available in a couple of minutes at NuGet.org

For my packages I created a workflow that runs on release of type published so that when I create a release it automatically publishes to NuGet.  I stored a nugget api key in the repo secrets and then the workflow just does a dotnet nugget push with appropriate flags.

Yeah, the workflow does run similarly to what you mentioned. It creates a draft release with the merged PRs and closed issues, and then when you move the draft to publish it triggers the Nuget push. You just need to publish the release whenever you feel appropriate. I like it this way since you have more control over things.


NEEDLE API query for ZTF data

Hi,
I can see there is a notebook for LSST but what about ZTF? Is it similar?
And also was NEEDLE run on older data?
Thank you,
Lydia

What is the question here?
What system are you running on?
What is the notebook you refer to?
When you say older data please explain.

Let me clarify. Here is the the notebook https://github.com/lsst-uk/lasair-examples/blob/main/notebooks/API_lsst/Query_NEEDLE_Annotations.ipynb but this is on LSST and I was wondering if there's a guide for ZTF.
In terms of older data, I mean earlier than 2024.


Add support to read Structs from parquet

A struct array poses an interesting challenge because it requires deserializing multiple arrays per row group as part of the same Array.
Since we are postponing decisions over how deserialization work is done (in parallel), this requires a more exotic API to support this use-case with high performance.

Closed by #547


Compilation error with disposables

Trying to use babel 6 to compile this package results in:
ERROR in ./~/disposables/modules/index.js
Module build failed: ReferenceError: [BABEL] C:\...\node_modules\disposables\modules\index.js: Using removed Babel 5 option: C:\...\node_modules\disposables\.babelrc.stage - Check out the corresponding stage-x presets http://babeljs.io/docs/plugins/#presets

The disposables repo states that the package is not maintained, is it posible to update this dependency?

Are you using yarn to install deps? It's using babel 6 now, and it's functioning correctly in CI.

I'm using npm, only method that worked was manually removing the .babelrc file from disposables

Same problem: Using removed Babel 5 option: base.stage
Is it possible to update disposables to rx.disposables?

Having the same problem here. Please note disposables is unmaintained, and their readme recommends switching to rx.disposables.

@darthtrevino - how can you just close this issue before the person even answered your question about yarn? In fact, react-dnd docs show use of npm and me and a list of other people have trouble because of the old disposables.

Other people have answered the question, and there was a PR that proposed to fix this issue where the author confirmed they were using npm. I believe the top-level docs were updated to mention yarn, but if you find any other references, feel free to cut a PR or call them out in an issue.


VectorSQL logo

Word is bond.

Codecov Report

Merging #45 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   81.45%   81.47%   +0.01%
==========================================
  Files         116      116
  Lines       10221    10221
==========================================
+ Hits         8326     8328       +2
+ Misses       1603     1601       -2
  Partials      292      292

Impacted Files
Coverage Δ

src/transforms/transform_datasource.go
83.33% <0%> (+5.55%)
:arrow_up:

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 a079141...2184e42. Read the comment docs.

Thanks for the Art Contribution, Prof.


The following bug occurred during my cluster deployment, and the program was forced to launch. Where is the configuration problem?

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[x] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
The following bug occurred during my cluster deployment, and the program was forced to launch. Where is the configuration problem?

_
Bug

Which version of SkyWalking, OS and JRE?
helm 3.+
ealstaticsearch 7
skwalking 8.+

Which company or project?

What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.

Requirement or improvement

Please describe your requirements or improvement suggestions.

OAP is reading API server for getting instance/pod list. Somehow, it is rejecting.


Impress Documentation

Describe the problem
I think the impress library currently has no documentation recognize by the METARHIA community
Describe the solution
I wish to develop one for the community and the users of impress,  who wish to use the library, one that has all the resources needed to start using the library

Now we docs: https://github.com/metarhia/Docs and specs: https://github.com/metarhia/Contracts


Simplify Touch to a single DoF class

          I think we can remove the iteration and simplify the class to process a single DoF

Originally posted by @edumeneses in https://github.com/Puara/puara-gestures/pull/20#discussion_r1889102170

Not 100% sure if this has been done or not in the previous PR, just putting this here to make sure we wouldn't forget about it !

ah yep perfect thank you! It hasn't been done but is my next set 🚀


Policyfile can normalize run list to an invalid value

I had a policyfile with the following:
run_list "recipe[cia_infra:base]"

That is incorrect because it should have two colons instead of one (i.e., it should be recipe[cia_infra::base]). If you run chef install with this, it normalizes the run list item to "recipe[cia_infra:base::default]" which the server will reject, with a curt error message:
Error: Failed to upload policy to policy group uwotmate
Reason: (Net::HTTPServerException) HTTP 400 Bad Request: Field 'run_list' is not a valid run list

Probably the best thing to do is to copy the server's validation and run that against the normalized run list, though this specific problem can be fixed by ensuring the cookbook name doesn't contain a colon.

Fixed by: https://github.com/chef/chef-dk/pull/635


[typing] Add DefaultAzureCredential to allowed types for credentials in KeyVaultClient

Description
The current typing for KeyVaultClient does not match the steps described in current documentation: here
I have added the DefaultAzureCredential from azure.identity based on the current recommended steps from the documentation.

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

Hi @soer7022, thank you for opening a PR and contributing to the SDK!
In this instance though, I believe the current typing is correct. Key Vault clients (and other clients in the SDK) don't necessarily require azure-identity credentials. They accept any credential that supports the TokenCredential protocol, which does include the DefaultAzureCredential, but also includes other azure-identity credentials and even custom credentials (some examples). So, TokenCredential is used as the credential type here and elsewhere 🙂
Do you think the documentation should be more clear about that? And/or is there a type checker that raised an error when providing a DefaultAzureCredential to a Key Vault client? If so, that might be something we'd want to find a fix for.

Thank you for the detailed reply 😄
The main reason that I made this pull request is due to PyCharm flagging it as a incorrect type:

Is my fix the right fix? Or should we look into making something more general?

@soer7022 Thank you for providing context about the issue! That's the first time I've seen an IDE raise a concern with the typing, and suggests that there's something we can do to make the protocol implementation more clear to Python (and users).
I can't reproduce the PyCharm warning on my end unfortunately -- I'm using a Python 3.10.0 interpreter on PyCharm Community Edition 2021.1.3. Could I know what interpreter and PyCharm version you're using?
If you don't mind, I'd like to continue this discussion on https://github.com/Azure/azure-sdk-for-python/issues/25175, an issue I opened to track this. It would be great if you could continue to help us to fix this! If not, that's no problem -- I appreciate that you brought this to our attention 🙂
I'm going to close this PR though, since the solution should come from the credential definition and/or the TokenCredential protocol definition.

Thank you! I will add further details and comments on the issue