iwona (font): init at 0_995

Motivation for this change
Another great sans-serif font!
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Just out of curiosity, can someone clarify what the flags that have been added to this issue mean?

@siddharthist it means it affects rebuilds of no more than 10 packages.

Thanks for the reviews, and special thanks to @Mic92 for fixing it up! I'm glad to learn about install, I've never seen that before.


Slimmelezer.yaml uri changed

Describe the bug
The slimmelezer.yaml template refers to uri links that don’t work with (at least mine) slimmelezer.
The links are slightly different “energy delivered” versus “energy consumed” etc.
I believe the template should be as shown below, but as I can’t compile evcc myself, Im not 100% certain this template would work (sorry Im new to this). Is there a way to for me to test this updated template to be certain my config works as a template instead of defining the meter in evcc.yaml?

template: slimmelezer
products:
  - brand: Zuidwijk
    description:
      generic: SlimmeLezer(+)
  - brand: ESPHome
    description:
      generic: DSMR
params:
  - name: usage
    choice: ["grid"]
  - name: host
render: |
  type: custom
  power:
    source: calc
    add:
    - source: http
      uri: http://{{ .host }}/sensor/power_consumed
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1000
    - source: http
      uri: http://{{ .host }}/sensor/power_produced
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: -1000
  energy:
    source: calc
    add:
    - source: http
      uri: http://{{ .host }}/sensor/energy_produced_tariff_1
      method: GET
      headers:
      - content-type: application/json
      jq: .value
    - source: http
      uri: http://{{ .host }}/sensor/energy_produced_tariff2
      method: GET
      headers:
      - content-type: application/json
      jq: .value
  currents:
  - source: http
    uri: http://{{ .host }}/sensor/current_phase_1
    method: GET
    headers:
    - content-type: application/json
    jq: .value
  - source: http
    uri: http://{{ .host }}/sensor/current_phase_2
    method: GET
    headers:
    - content-type: application/json
    jq: .value
  - source: http
    uri: http://{{ .host }}/sensor/current_phase_3
    method: GET
    headers:
    - content-type: application/json
    jq: .value
  powers:
  - source: calc
    add:
    - source: http
      uri: http://{{ .host }}/sensor/power_produced_phase_1
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1000
    - source: http
      uri: http://{{ .host }}/sensor/power_consumed_phase_1
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: -1000
  - source: calc
    add:
    - source: http
      uri: http://{{ .host }}/sensor/power_produced_phase_2
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1000
    - source: http
      uri: http://{{ .host }}/sensor/power_consumed_phase_2
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: -1000
  - source: calc
    add:
    - source: http
      uri: http://{{ .host }}/sensor/power_produced_phase_3
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: 1000
    - source: http
      uri: http://{{ .host }}/sensor/power_consumed_phase_3
      method: GET
      headers:
      - content-type: application/json
      jq: .value
      scale: -1000

Steps to reproduce
Current template results in no meter values
Configuration details
N/A

Log details
N/A

What type of operating system are you running?
Windows
Version
0.121.1

Happy to take a PR!


the payload is invalid

Can you check the network tab to see exactly what was the payload sent?

I had the same error.
It occurred because the Laravel debugger was enabled, and it was injecting the output of its script into the file field in the payload.
To fix this error, the quickest way is to disable the debugger.


TODO listing does not look good on desktop

I have opened a PR https://github.com/leonardopliski/react-antd-todo/pull/53 for this issue.
Please take a look @leonardopliski

https://github.com/leonardopliski/react-antd-todo/pull/55


Resources.zip and packages in commits

Resources.zip and install / source packages archives should not be tracked by git. Currently "changes" in them just infesting commit page with needless info.

Closing due to age


Refactoring generated operationId in Ballerina to OpenAPI tool

Description:
$Subject
Currently, we are using the resource function name as the operation name. Ballerina to OpenAPI tool we are unable to generate human-readable operationId, since we can’t capture enough details by looking at the resource and make it unique. Therefore to avoid duplicate behaviour we followed some action rules for generating the operations Id.
But the generated operationId has some issues with

not user friendly
some scenarios have lengthy operationId ex: post_passenger_passport_no_bookings_booking_id_response
path parameter and special characters with patch operation has operationId with unreadable ex: "operation_get_/say-hello/{path-param}"

The purpose of this task is to improve the operationId generation process to increase human readability.
Describe your task(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

As per having an offline discussion with @shafreenAnfar , we came up with the below outcome for current operation id generation.
please refer to this ballerina example :
service on new http:Listener(9090) {
    resource function get passenger/[string passportNo]/bookings() {
    }
}

for the above example, we currently generated operationId in below way
get:
      operationId: "operation_get_/passenger/{passportNo}/bookings"
      parameters:
...

during the discussion, suggested removing the operation from id and making it normalizing id removing special characters and capitalising variable names.
suggested operationId : getPassengerPassportNoBookings
This approach will address the mentioned issue points  2, 3 and partial from 1.  @hevayo we are pleased to have input for this improvement approach for the code generations process?
At the same time, we received suggestions to use have some approach for overriding the auto-generated operation id with user given value. Please refer to this https://ballerina-platform.slack.com/archives/C47EAELR1/p1648721879663829


Do we fully support fragments?

** Which Category is your question related to? **
GraphQL transformer codegen
** Provide additional details e.g. code snippets **
I'm adding a fragment in a custom GraphQL query file. For example:
fragment SheetParts on Sheet {
  id,
  name,
  bpm,
}

query ListItemPage($id: ID!) {
  getList(id: $id) {
    name,
    sheets {
      items {
        ...SheetParts
      }
    }
  }
}

query MyLibraryPage($limit: Int, $nextToken: String) {
  listSheets(limit: $limit, nextToken: $nextToken) {
    nextToken,
    items {
      ...SheetParts
    }
  }
}

Codegen gracefully generates SheetPartsFragment into my API, but when requesting the qery through the generated API, I get this error:
core.js:15724 ERROR Error: Uncaught (in promise): Object: {"data":null,"errors":[{"path":null,"locations":[{"line":9,"column":9,"sourceName":null}],"message":"Validation error of type UndefinedFragment: Undefined fragment SheetParts @ 'getList/sheets/items'"}]}
Am I missing something?
Thanks

This seems a bug in the angular service generation. The fragment definition is missing in the generated API queries. It works if I manually edit the generated service and add the missing fragment after the query.

@brunostuani Currently Amplify Codegen does not support fragments. Marking this as an enhancement.

I have been using a hacky implementation for some time now and finally managed to assemble it as a fork https://github.com/artemkloko/amplify-cli
It supports only TypeScript and is not for production. Still would be nice if someone could test it on a playground project or comment on the strategy itself.

@artemkloko I'm really liking the look of that library!  I have also created your first issue! (sorry!) - https://github.com/artemkloko/amplify-graphql-fragments-generator/issues/1
let me know if you need any help with the issue 👍


Anton-Clock can optionally show ISO-8601 calendar weeknumber

The ISO-8601 calendar weeknumber added as or behind weekday.
The "display with seconds " mode was untouched.
No "core" update this time ;)
PS: copied GIST for ISO-Week # is als "MIT-license"

Thanks!


Update README.md

Added ts-express-boilerplate to starter kits

Merged; Thank you @d4rkstar!

Thank you too !


single deployment order of operations

Description
➕ Adds a spoke module that allows us to remove all the things under core/*
🙌 Updates the firewall module so that it can be Terraform apply'd without recreation saving countless hours
🔀 Moves Log Analytics Workspaces to a standalone resource at mlz/main.tf that other modules can refer to

closed in favor of https://github.com/Azure/missionlz/tree/singledeployment_updateautomation


using-functions bash tutorial

Populate functions/using-functions.sh with a tutorial and challenge.

Hi @funbeedev, I would like to take this one :)


updating CLI from 6.1.5 -> 7.0.3 indicates missing tsconfig files for ng serve / test (Karma)

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x] build
- [x] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node: v9.8.0
npm: 6.4.1
ng: 7.0.3
os: macOS Mojave
Repro steps

In our Angular app we use a library consisting of only .ts files. these are mostly typings (so we should maybe use .d.ts as suffix, but without this compilation worked fine in Angular 6.1.5.
After upgrading, for 3 out of 36 .ts files we get errors looking like the one in the log section below.
After including the include property in our tsconfig.json file:
"include" : [
<EMAIL_ADDRESS>    "src/main.ts",
    "src/polyfills.ts"
  ]

we get the same error for our main.ts and polyfills.ts files. After adding also these files, that fixes compilation for ng serve and ng build. For ng test (with Karma) however, we still get the same errors, even though our tsconfig.spec.json extends tsconfig.json.
Will try to come up with an MWE, WIP
The log given by the failure

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/@ngtools/webpack/src/index.js):
Error<EMAIL_ADDRESS>is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
    at AngularCompilerPlugin.getCompiledFile (/Users/michahell/project/node_modules/@ngtools/webpack/src/packages/ngtools/webpack/src/angular_compiler_plugin.ts:1028:15)
    at plugin.done.then (/Users/michahell/project/node_modules/@ngtools/webpack/src/packages/ngtools/webpack/src/loader.ts:49:29)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7)
 @ ./src/app/components/conversation-message/conversation-message.component.spec.ts 13:15-44
 @ ./src sync \.spec\.ts$
 @ ./src/test.ts

Desired functionality

compilation succeeds as before in 6.1.7

@michahell what was the original error that you experienced before adding the files in the include.
The latest error that you are experiencing is legit and is working as expected as libraries should not contain any TypeScript files and has been the case even for version 6.

@alan-agius4
We're only seeing variations on this error pointing to other .ts files, even before I added the files to include.
In version 6 we did not even get warnings regarding this and everything worked fine.
What is the way to go? Should we make everything .d.ts definitions ?

And should I not be allowed to do whatever I want in my libraries? Why is it prohibited to import .ts files? They should be warnings, just like the current error is a warning the user.

@filipesilva Thank you for your elaborate answer, this all makes sense. our use case is indeed usage as internal library. I'll look into reproducing this now

Here is a reproduction of what I'm experiencing.
steps:

I've used the Angular CLI to generate a new project using ng new
then I added our own internal .ts library to test if I was still experiencing this issue, which I was.
I removed our internal package
created a sample package inside node_modules called @sample-ts-lib with a sample exported enum and interface.
I use the enum from the sample package  in app.component like so: const mountain = MountainEnum.meru;
when I run both npm start and npm test I get the error mentioned above.
I then update tsconfig.json with the following include property:

"include" : [
<EMAIL_ADDRESS>    "src/main.ts",
    "src/polyfills.ts"
  ],

(side question: why do I have to explicitly include main.ts and polyfill.ts here? is it for the same reasons? but then why specify this in angular.json in the architect.build section?)

now, I don't get compile errors with npm start. I do get compile errors with npm test.
lastly, I tried adding<EMAIL_ADDRESS>to the include property of tsconfig.json to no avail.

ts-lib-repro.zip

We are currently seeing a similar issue. After upgrading, we found that our application seems to work fine, but our local test infrastructure fails because of the same Module build failed error related to our internally installed modules, which are symlinked into place for local development.
@michahell Are you guys symlinking your custom typings into place or are you actually installing the files into node_modules? We got rid of the symlinking and as soon as we did, Webpack/Karma properly picked up the custom modules.

@mko Thanks for the feedback! We are really installing them as a package into node_modules. Are you also adding files with a .ts extension instead of .d.ts? if so, could you give a barebone example of your tsconfig + app.tsconfig and test.tsconfig ?

@michahell I'm trying to use your repro but I can't see the error you mentioned. This is what I did:

download the .zip file you provided and extract it into the ts-lib-repro folder
go inside the folder
notice there's a node_modules folder with @sample-ts-lib inside, but nothing else
there's a yarn.lock file so I run yarn
run npm run build and see the error below:

kamik@RED-X1C6 MINGW64 ~/Downloads/ts-lib-repro (master)
$ npm run build

><EMAIL_ADDRESS>build C:\Users\kamik\Downloads\ts-lib-repro
> ng build

Date: 2018-11-09T14:16:56.736Z
Hash: 09489c23bd86db5f3663
Time: 5618ms
chunk {main} main.js, main.js.map (main) 628 bytes [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 94.6 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.22 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 17 kB [initial] [rendered]

ERROR in src/app/app.component.ts(2,30): error TS2307: Cannot find module '@sample-ts-lib/sample-enum'.

check node_modules again and see that @sample-ts-lib disappeared, probably during yarn
copy node_modules/@sample-ts-lib again from the zip file
run npm run build again, see the error below:

kamik@RED-X1C6 MINGW64 ~/Downloads/ts-lib-repro (master)
$ npm run build

><EMAIL_ADDRESS>build C:\Users\kamik\Downloads\ts-lib-repro
> ng build

Date: 2018-11-09T14:17:44.134Z
Hash: a905fc4c0cedc6d3ed28
Time: 3430ms
chunk {main} main.js, main.js.map (main) 628 bytes [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 94.6 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.22 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 17 kB [initial] [rendered]

ERROR in No NgModule metadata found for 'AppModule'.

I cannot see the error you mentioned (The missing file seems to be part of a third party library. etc) so I cannot investigate.
Can you provide me with precise instructions that I can follow to see the error please? To make sure it is reproducible, try following the repro yourself by doing the instructions.

OK for some reason, a default Angular CLI project defaults to yarn for me, I don't know why, I just used npm for this MWE.
Here is the same project, without .git, .idea and yarn.lock folders and files.
the @sample-ts-lib is moved into the project root.
What I did to make it 'work':

unzip folder somwhere
npm i
move @sample-ts-lib into the node_modules folder
npm start (nothing goes wrong here)
npm test (something DOES go wrong here)

ts-lib-repro-nogit-noyarn.zip

@michahell following your steps this is what I see:
kamik@RED-X1C6 MINGW64 ~/Downloads/ts-lib-repro-nogit-noyarn/ts-lib-repro2
$ npm i
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.

><EMAIL_ADDRESS>install C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2\node_modules\node-sass
> node scripts/install.js

Cached binary found at C:\Users\kamik\AppData\Roaming\npm-cache\node-sass\4.9.3\win32-x64-64_binding.node

><EMAIL_ADDRESS>postinstall C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2\node_modules\node-sass
> node scripts/build.js

Binary found at C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2\node_modules\node-sass\vendor\win32-x64-64\binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1095 packages from 1163 contributors and audited 39132 packages in 95.417s
found 0 vulnerabilities

kamik@RED-X1C6 MINGW64 ~/Downloads/ts-lib-repro-nogit-noyarn/ts-lib-repro2
$ mv \@sample-ts-lib/ node_modules/

kamik@RED-X1C6 MINGW64 ~/Downloads/ts-lib-repro-nogit-noyarn/ts-lib-repro2
$ npm start

><EMAIL_ADDRESS>start C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2
> ng serve

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

Date: 2018-11-14T09:26:14.712Z
Hash: a61de44769ba995d983a
Time: 3586ms
chunk {main} main.js, main.js.map (main) 1.92 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 92.4 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 16.6 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 318 kB [initial] [rendered]

ERROR in No NgModule metadata found for 'AppModule'.
i ｢wdm｣: Failed to compile.

kamik@RED-X1C6 MINGW64 ~/Downloads/ts-lib-repro-nogit-noyarn/ts-lib-repro2
$ npm test

><EMAIL_ADDRESS>test C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2
> ng test

 11% building modules 9/9 modules 0 active14 11 2018 09:26:31.238:WARN [karma]: No captured browser, open http://localhost:9876/
14 11 2018 09:26:31.249:INFO [karma]: Karma v3.0.0 server started at http://<IP_ADDRESS>:9876/
14 11 2018 09:26:31.250:INFO [launcher]: Launching browser Chrome with unlimited concurrency
14 11 2018 09:26:31.256:INFO [launcher]: Starting browser Chrome                                                                                × ｢wdm｣: Hash: 8d1070eadef0f8342111Version: webpack 4.19.1
Time: 9489ms
Built at: 11/14/2018 9:26:35 AM
       Asset      Size     Chunks  Chunk Names
     main.js  35.1 KiB       main  main
polyfills.js   525 KiB  polyfills  polyfills
   styles.js  20.8 KiB     styles  styles
   vendor.js  8.21 MiB     vendor  vendor
Entrypoint main = vendor.js main.js
Entrypoint polyfills = polyfills.js
Entrypoint styles = vendor.js styles.js
<EMAIL_ADDRESS>233 bytes {polyfills} [built]
[./node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/raw-css-loader.js!./node_modules/postcss-loader/src/index.js?!./node_modules/sass-loader/lib/loader.js?!./src/styles.scss] ./node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/raw-css-loader.js!./node_modules/postcss-loader/src??embedded!./node_modules/sass-loader/lib/loader.js??ref--14-3!./src/styles.scss 554 bytes {styles} [built]
<EMAIL_ADDRESS>1.13 MiB {vendor} [built]
<EMAIL_ADDRESS>76.3 KiB {vendor} [built]
[0] multi ./src/polyfills.ts<EMAIL_ADDRESS>40 bytes {polyfills} [built]
<EMAIL_ADDRESS>9.7 KiB {vendor} [built]
[1] multi ./src/styles.scss 28 bytes {styles} [built]
<EMAIL_ADDRESS>100 KiB {vendor} [built]
<EMAIL_ADDRESS>7.13 KiB {vendor} [built]
[./node_modules/core-js/es7/reflect.js] 510 bytes {polyfills} [built]
[./node_modules/zone.js/dist/zone-testing.js] 67.4 KiB {vendor} [built]
[./src sync recursive \.spec\.ts$] ./src sync \.spec\.ts$ 192 bytes {main} [built]
[./src/polyfills.ts] 3.14 KiB {polyfills} [built]
[./src/styles.scss] 1.54 KiB {styles} [built]
[./src/test.ts] 599 bytes {main} [built]
    + 298 hidden modules

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/@ngtools/webpack/src/index.js):
Error<EMAIL_ADDRESS>is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
    at AngularCompilerPlugin.getCompiledFile (C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2\node_modules\@ngtools\webpack\src\packages\ngtools\webpack\src\angular_compiler_plugin.ts:1028:15)
    at plugin.done.then (C:\Users\kamik\Downloads\ts-lib-repro-nogit-noyarn\ts-lib-repro2\node_modules\@ngtools\webpack\src\packages\ngtools\webpack\src\loader.ts:49:29)
    at process._tickCallback (internal/process/next_tick.js:68:7)
 @ ./src/app/app.component.ts 11:0-58 15:23-35
 @ ./src/app/app.component.spec.ts
 @ ./src sync \.spec\.ts$
 @ ./src/test.ts
14 11 2018 09:26:36.684:INFO [Chrome 70.0.3538 (Windows 10 0.0.0)]: Connected on socket dNQFEa1gFZfe8oshAAAA with id 57726295
Chrome 70.0.3538 (Windows 10 0.0.0): Executed 0 of 0 ERROR (0.017 secs / 0 secs)

I see the build failing on both npm start and npm test.
If you change your src/tsconfig.spec.json from
  "include": [
<EMAIL_ADDRESS>    "**/*.spec.ts",
    "**/*.d.ts"
  ]

to
  "include": [
<EMAIL_ADDRESS>    "**/*.spec.ts",
    "**/*.d.ts"
  ]

Then npm test will now pass. The path in a tsconfig include section are relative to the file itself, and there's no node_modules inside src/ so that include was never found.
I'm not sure what the error on build is but since you say you're not seeing it yourself then I suppose it's some odd artifact of the repro.

I would also dismiss the npm start error as some weird repro artifact because I started a new Angular CLI project from scratch.
But why does the src/tsconfig.spec.json need to specify the include property again in the first place? I would expect it to inherit this from the extended tsconfig.json ?

When a property (like include) is re-declared in a tsconfig that inherits from another tsconfig, it is overwritten. src/tsconfig.spec.json has different includes so they need to be redeclared.

ah... that makes sense. I'd expected they would have been merged so no duplicating things / having a harder time maintaining.
and indeed, that seems to fix it, and then I have to be able to change this in our project, too.
Thanks @filipesilva !

@michahell so by reading your issue, it seems I need to add node_modules to the include array for my library (https://github.com/PeterHdd/date-filtersjs)
to work in angular?


Update benchmark.py

Thanks @tobymao! I'm about to push a release for the latest version and can cherry pick this test fix and re-run the benchmark suite.

@tobymao benchmarks have been restated, looks like sqlglot is ~2x as fast since the last run!


Got some problems when build the server

I want to build the server in Ubuntu 16.04, firstly, I got the same problem like #458 ,then I use meson 0.37 to build again, and another problem occurred:
Meson encountered an error:
Could not detect Ninja v1.6 or newer

I find that when I run
# client build dependencies
sudo apt install make gcc pkg-config meson ninja-build \
                 libavcodec-dev libavformat-dev libavutil-dev \
                 libsdl2-dev

I just can install ninja-build v1.5 , I can not get ninja v1.6 or newer version for Ubuntu 16.04 , so how should I solve the problem?
Waiting for your response, thanks.

I don't have Ubuntu 16.04 here, but when I tested, I just had to install a newer meson via pip3, I don't remember any problem with ninja (but maybe because now the new meson requires a more recent ninja).
Anyway, you can probably install a newer ninja-build from backports: https://packages.ubuntu.com/xenial-backports/ninja-build

I don't have Ubuntu 16.04 here, but when I tested, I just had to install a newer meson via pip3, I don't remember any problem with ninja (but maybe because now the new meson requires a more recent ninja).
Anyway, you can probably install a newer ninja-build from backports: https://packages.ubuntu.com/xenial-backports/ninja-build

Thanks for your help, I downloaded a newer ninja-build and run meson command successfully, but when I run ninja command, a new problem come in process:
[32/33] 'Generating scrcpy-server with a custom command.'
FAILED: server/scrcpy-server.jar
'/home/wanjiasheng/my_workspace/scrcpy/server/./scripts/build-wrapper.sh' '../../scrcpy/server/.' 'server/scrcpy-server.jar' 'release'

FAILURE: Build failed with an exception.

* What went wrong:
Could not create service of type ScriptPluginFactory using BuildScopeServices.createScriptPluginFactory().
> Could not create service of type FileHasher using BuildSessionScopeServices.createFileSnapshotter().

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

This is my gradle information:
------------------------------------------------------------
Gradle 2.10
------------------------------------------------------------

Build time:   2016-01-26 15:17:49 UTC
Build number: none
Revision:     UNKNOWN

Groovy:       2.4.5
Ant:          Apache Ant(TM) version 1.9.6 compiled on July 20 2018
JVM:          1.8.0_191 (Oracle Corporation 25.191-b12)
OS:           Linux 4.4.0-21-generic amd64

So what should I do? Thanks.

For simplicity, you should try with the prebuilt server, it will not call gradle at all.
It weird, it didn't have all these problems when I built on 16.04 (but 16.04 is quite old, now).

For simplicity, you should try with the prebuilt server, it will not call gradle at all.
It weird, it didn't have all these problems when I built on 16.04 (but 16.04 is quite old, now).

Alright, thanks for your help.

For simplicity, you should try with the prebuilt server, it will not call gradle at all.
It weird, it didn't have all these problems when I built on 16.04 (but 16.04 is quite old, now).

Alright, thanks for your help.

I have solved the problem and build the server successfully, it looks like a permission issue.
Run sudo chmod -R 777 for some folders and then the problem did not appear again.


Github Project Links

Behrend Trees: https://github.com/N00000DLE/BehrendTrees/issues/1

Kingdom Hearts: https://github.com/austinmurry/KingdomHeartOfTheCards


Simple install: create database if not present (no need for setup.py)

As it says.
based on experimental branch.

redid it in masterbranch. see https://github.com/mrkipling/maraschino/pull/23


omnibus bumps and lints

NOTE: this is an omnibus PR, and it isn't scoped.  Future PR's would be more tightly scoped, where this one is more aimed at cleaning the repository and stabilizing it some.

fix dockerfile
lint tests
add tests where needed (mainly error checks, kinda no big deal)
bump to sdk v0.45.14-ics
bump to ibc-go v4.3.0
Add automated checks

codacy
build the docker image on pull request without pushing the image, push it on merges
cosmos flavored codeql
regular codeql

Recommend that we get this in, that way future PR's to this branch use up to date versions of:

cosmos-sdk
ibc
interchain-security
cosmos-proto

That way, when we make future PR's to neutron, we are testing against code that is closer to what we'd like to ship in production.
note
This contains all of the fixes that have been made to the audit branch, as well as additional fixes and version bumps.  It should help greatly with evaluations of this repository by validators.

https://github.com/neutron-org/neutron/pull/191/files i've reworked the pr, dropped the changes we cannot approve. I believe it's safe to close this one.


File upload

Hello, first thing firt, i should say that is probably the most sharp and nice webapp related to openai api.
Thanks to all contributor.
I would like to know if there a setting that should be configured/updated and where it should be, to be able to upload file and send to gpt4 model.
If i can remmeber correctly, the chatpt-midjourney project had this option, i would like to know if there a way to add it etc or if it related to option in some file that need to be activated.
(Im talking about the true file send to gpt4 api model, and not the file to text.)
thanks alot.

OpenAI's gpt-4 API still does not support receiving files, only the official web UI: chat.openai.com supports direct file uploads.


Update dependency versions for consistency

Move to netty-tcnative-boringssl-static version 2.0.26.Final and protobuf version 3.10.0 to match to match target gRPC version 1.25.0.
Move more recent versions of auto-value and protoc-jar-maven-plugin.
Make log4j dependencies in examples modules have scope of runtime since they are not needed for compilation.

Please see the table in the Netty section here for gRPC + Netty version compatibility.

Friendly ping for @nwbirnie and @devchas for review

da004ba646af2a580f34c391c0b8847f45d05030@jradcliff .com


[DRAFT] Passing meta to map_partitions for read_data

Description

Usage

# Add snippet demonstrating usage

Checklist

[ ] I am familiar with the Contributing Guide.
[ ] New or Existing tests cover these changes.
[ ] The documentation is up to date with these changes.

Should be safe to close this, as https://github.com/NVIDIA/NeMo-Curator/pull/311 will allow users to pass in any valid keyword arguments into our read_* functions.


[network] implement message handling behavior for Choke & Interested

implement message handling for Choke, Unchoke, Interested, and Uninterested message types.
Currently, there's some basic handling in PeerConnector.handleMessage, but the behavior is not complete, and would need to implement checks in SocketConnector.
Max's Estimate: 2h

Also need to refactor Peer. Keep track of not only "interested" and "choked", but instead if "we are interested", "they are interested", etc. This is documented here: https://wiki.theory.org/BitTorrentSpecification#Overview


Recent changes of the Gootloader zombied script, causes GootLoaderAutoJsDecode.py to fail

These samples are failing the autoJsDecode:
https://www.virustotal.com/gui/file/975fe5897c8b00c5a18c5bae04b40e3feb94f9a2deb201697dc7059bba2ad581
https://www.virustotal.com/gui/file/6e4d270446a5a47be01f8181890052819b67430e163116e5f78c66ce61a227f1
JS code they are hiding in, is based off this<EMAIL_ADDRESS>With certain lines removed.

@GootloaderSites they should work with the latest release.


Cannot launch anything in Anaconda Navigator

Issue Report Checklist

[√ ] Searched the issues page for similar reports
[√ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[√ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ √] Tried basic troubleshooting (if a bug/error)

[√ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[√ ] Reinstalled the latest version of Anaconda
[ √] Tried the other applicable steps from the Troubleshooting Guide

[√ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I just downloaded Anaconda 3.7 version, but when I opened the Anaconda Navigator, all the items cannot be launched. I tried several times to uninstall and reinstall the software but nothing changed.
What steps reproduce the problem?

rebot the laptop
uninstall the Anaconda
reinstall the Anadonca

What is the expected output? What do you see instead?
I expected that all items could run properly but actually they couldn't.
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE
```json
[
    {
        "level": "ERROR",
        "line": 234,
        "message": "Invalid url https://www.anaconda.com/wp-content/uploads/2017/05/Webinar20-20Three20Ways20to20Move20your20Data20Science20Projects20to20Production.png",
        "method": "_download",
        "module": "download_api",
        "path": "C:/Users/Amanda/python/lib/site-packages/anaconda_navigator/api/download_api.py",
        "time": "2019-09-15 14:43:53,879"
    }
]

## Versions
<!--- You can get this information from Help > About Spyder...
or (if Spyder won't launch) the "conda list" command
from the Anaconda Prompt/Terminal/command line. --->

* Spyder version: 3.3.6
* Python version: 3.7
* Qt version:
* PyQt version:
* Operating System name/version:

### Dependencies
<!--- Please go to the menu entry Help > Dependencies,
press the Copy to clipboard button and paste below --->

PASTE DEPENDENCIES HERE
Soory, there is no Dependencies in the version.

Please report this problem here:
https://github.com/ContinuumIO/anaconda-issues/issues


Generate Bytes for bytes

https://docs.rs/prost-build/0.7.0/prost_build/struct.Config.html#method.bytes
This can facilitate fewer copies when working with data-heavy APIs.

@shikhar Your suggestion is very cool. I'm a fan of the bytes crate.
However, this change is destructive and should be released with caution.
(Although it's not so popular as to release it so carefully 😅)

Indeed, it would be a breaking change!


[Explore view] duplicated /api/v1/chart/id requests

How to reproduce the bug

Open explore view from chart list,
or Explore chart from dashboard,

Actual results
You will see 2 /api/v1/chart/id requests
Expected results
only 1 api call for each endpoint.
Screenshots

Environment
latest master
Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

@geido 🙏


clustermesh: Rename host-reachable-svc opt

Rename to --bpf-lb-sock, as --enable-host-reachable-services was removed in https://github.com/cilium/cilium/pull/22083.

@brb This broke external workload installs on Cilium 1.11, as --bpf-lb-sock is unknown there. It seems this change needs to be made conditional on the Cilium version?

Opened issue #1232


Add a warning for decimal PKs with SqlServer

We use strict comparisons for PK values that can fail in some scenarios: https://github.com/aspnet/EntityFrameworkCore/issues/17799, https://github.com/aspnet/EntityFrameworkCore/issues/14952
Consider recommending to use SET NUMERIC_ROUNDABORT ON

Triage: We should avoid breaking changes in 3.1, but we are not sure this would be one.


Sweeping of onchain funds not possible

I want to empty my raspiblitz onchain wallet to zero. In the wallet there is only 1 utxo (10.000sats) I have tried RTL and thunderhub but get the same error message on both:
RTL (sweep all funds)"Insufficient Input To Create Sweep Tx: Input_sum=0.0001 Btc, Output_sum=0.0001128 Btc":
thunderhub (with send all): "UnexpectedSendCoinsError. insufficient input to create sweep tx: input_sum=0.0001 BTC, output_sum=0.0001128 BTC"
How can I empty my wallet? Is sweeping possible at all?

If you use LND ... have you tried out loggin in thru SSH and in the main menu go LND > CASHOUT?

I get the same error:
"FAIL: [lncli] rpc error: code = Unknown desc = insufficient input to create sweep tx: input_sum=0.0001 BTC, output_sum=0.00012143 BTC"
Is the missing amount the tx fee? Shouldn't (in a sweep tx) the tx fee be calculated such that it is included in the total available funds?
If tx fee ist 2143sats (as I assume in this case), the output would be 10000 - 2143 = 7857.
Or is the calculated tx fee higher than the available funds (i.e. > 10000)

Even with SSH and in the main menu go LND > CASHOUT, the error persists:

Sweep all possible Funds

redis-cli set ln_lnd_mainnet_wallet_onchain_pending:out 0 EX 900
OK
redis-cli set ln_lnd_mainnet_wallet_onchain_balance:out 0 EX 900
OK
sudo -u bitcoin /usr/local/bin/lncli -n=mainnet --rpcserver localhost:10009 sendcoins --sweepall --addr=bc1qk***************** --conf_target=36
FAIL: [lncli] rpc error: code = Unknown desc = insufficient input to create sweep tx: input_sum=0.0001 BTC, output_sum=0.00011431 BTC
#################################
FAIL --> Was not able to send transaction (see error above)
#################################


run: improve automatic DKIM private key creation

Run opendkim-genkey with the "-D" ("--directory") option instead of
changing directory manually in a bash subshell.
Also output an informational message when a DKIM private key is being
generated. This is useful to see, especially if you were expecting an
existing file to be found (e.g. if the wrong selector was used).

Thanks! that is nicer


No unique 'key' prop for children

In most of the components unique 'key' prop is not set
You can check the console in http://onsenui.github.io/react-onsenui-kitchensink/demo.html.
Having unique 'key' for each children is critical not only for application performance

@emildimitrov you have to set the keys for now by yourself, take a look at this demo here https://github.com/OnsenUI/react-onsenui/tree/master/demo. We could set automatic keys, but i don't think this is a good idea.

Hi :) I tried with the tabbar, but couldn't get how to ensure that every child has key. I'll be happy if could give me direction for example how to ensure this here https://onsen.io/tutorial/index.html?framework=react&category=Reference&module=tabbar

@emildimitrov You can add keys to your pages and tabs like this:
  renderTabs: function() {
    return [
      {
        content: <MyTab key='home' title='Home' />,
        tab: <Ons.Tab key='home' label='Home' icon='md-home' />
      },
      {
        content: <MyTab key='settings' title='Settings' />,
        tab: <Ons.Tab key='settings' label='Settings' icon='md-settings' />
      }
    ];
  },

This should get rid of the error.

@argelius  It shound be on document


Please Add the following Pornography Domains to Block

Hello @StevenBlack and @Sinfonietta,
Please add the following pornography domains to the Porn Hosts blocker:
tribbinglesbians.com
panochasyculos.com
omorashi.org
youleaked.com
hentaifc.com
aveliporn.com
humpingmasturbation.com
xxxa.com
xxxxsx.com
pornevening.com
eliteporn.cc
cloudixgirls.com
nebyda.com
hentaiheart.com
novelcrow.com

Thanks @g1t3m!
Ping @sinfonietta for inclusion.

@StevenBlack these are added.

Thanks @Sinfonietta!
Closing.


Please update to league/oauth2-client version 2

Version 2 is available now for https://github.com/thephpleague/oauth2-client/releases/tag/2.0.0

https://github.com/thephpleague/oauth2-instagram/releases/tag/2.0.0


Automated Package Upgrade

:tada: This PR is included in version 9.0.22 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix: Ignoring Characters with ALT Key

Fix: Ignoring Characters with ALT Key
When you press the ALT key and a character at the same time, the character is ignored.

Closes #5338

On Mac (and probably other OSes), Alt/Option is used to input special characters that will now be impossible to write


ACL display/edit widget doesn't show all informations

Real example:
On the following deployment we see only the group Nuvla Administrator Group in the list of owners.
But if we look in raw (json), this group is not an owner but instead there is a user.
The deployment:

on api page: https://nuvla.io/ui/api/deployment/84b8a30a-9d5e-4161-b323-39349871c2a0
on dashboard page: https://nuvla.io/ui/dashboard/84b8a30a-9d5e-4161-b323-39349871c2a0

By looking at all the ACL in raw we can see that what is display on the "ACL widget" doesn't match the real ACL, not only for the owners field.

I don't see the issue @schaubl. The acl is
  "acl": {
    "owners": [
      "group/nuvla-admin"
    ]
  }
``` and the acl widget is showing this as well


Deny publishing packages with non-standard name formats (Fix #6043)

This PR resolves #6043.
The issue requesting this feature mentions adding a warning, but because packages can't be removed once published, it seemed to make more sense to outright deny the publishing attempt by default. Packages with non-snake-case names can still be published using the allow-non-snake-name option.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @matklad (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR! In light of https://internals.rust-lang.org/t/cargo-and-rustup-development/8615/1 I don't think we're willing to merge this at this time. This is a relatively large change to Cargo itself which I unfortunately think we don't have tie to prioritize and review until after the edition and planning.

Gotcha- that definitely makes sense given that context. Thanks for letting me know!


Allow access to full IO expression set from app

Expression download currently has immunomodulator expression only. Full expression set would be preferable.
Before closing this issue, be sure it is mirrored in 2.0

A file to share would be https://www.synapse.org/#!Synapse:syn21123525 (currently in non-public space), according to @DanteBortone . One option might be to move that to a location in https://www.synapse.org/#!Synapse:syn10337516/wiki/458420 and link to it

A file to share would be https://www.synapse.org/#!Synapse:syn21123525 (currently in non-public space), according to @DanteBortone . One option might be to move that to a location in https://www.synapse.org/#!Synapse:syn10337516/wiki/458420 and link to it

Link to Synapse added to v1.4.1: https://www.synapse.org/#!Synapse:syn24200710
Link already added to 2.0.

Link to Synapse added to v1.4.1: https://www.synapse.org/#!Synapse:syn24200710
Link already added to 2.0.


Ticket 93

added engineers with data to array of each planet, issues now with repair fn

Merge conflict resolved in a new push


navigation state show correct index?

Version
Tell us which versions you are using:

react-native-router-flux v3.37.0
react-native v0.37.0

Expected behaviour

I would expect index to be 3.
Actual behaviour
Instead it shows 0 and the key seems to have right number in it? showing 1.
Any ideas on how to expose this index correctly.
I want to use index to decide whether to show a back button or not, without having to write my own reducer and store this index myself?

Hello @rmnegatives,
I need to do something like that. Can you resolve that?
Thanks!

@jaisonveneri you mean @aksonov right?

@rmnegatives Can you get the correct index in another way? Sorry for the misunderstanding.

@jaisonveneri  with this specific version notice that key: 'tile_1_tile' you can parse that out. But it seems like index should say 1 as well.

Yes, you are right @rmnegatives,
For me it seems that in "key" has the index inside.
I needed to know the count stack navigation to show or not a custom back button on a custom navbar. I think that I use this.
Thanks for the reply.

No prob had the same reason! @jaisonveneri

Any news on this ?


Implement BatchNorm2D class

Hello, Thank you very much for your great work on this project!
I am currenty working on neural network using your package, but I miss the BatchNorm2D layer.
Will it be implemented in a next release, and if yes when?
If no and if you are interested, I can contribute on this one.
Let me know, have an excellent day!

@enrico174 Please do contribute
The focus for me in this project is a the level of LibTorch functions, not layers, because that is what is consumed by DiffSharp.
There are some layer wrappers implemented, as you can see, you should be able to follow Linear and other similar layers to work out how to do it and test it

@dsyme Thank you very much for your reply
I understand your priorities. In deed I have seen the C++ wrappers parts, and the way they are coded seems repeatable for new layers coding on my side. I will try to see what I can do, possibly next month.
Thank you again for this project!

Reference to previous issue on BatchNorm


Is it compatible with poollab 2.0?

As the title suggest?

I can confirm that it works with the Poollab 2.0


Update guide for podman

In the newer versions of func there is no need for starting the service and setting the DOCKER_HOST envvar.
It should be handled automatically.

cc @abrennan89 @rh-max

/lgtm


1.2.0 RELEASE.

@jordangarcia - feel free to send commits to this fixing the CHANGELOG.

one minor change, thanks for writing release notes!


Fully implement Typescript

There are some functions with typescript (tsx) and others with jsx. For better linting and autocompletion, we should go for full Typescript

I think that this is done with #20


Ubuntu 15 fails because /sbin/status is not found

Not sure if this is rightly here or in chef's Upstart code, but using
$> chef -v
Chef Development Kit Version: 0.6.0
chef-client version: 12.3.0
berks version: 3.2.4
ckitchen version: 1.4.0
and openssh cookbook 1.4.0
to build ubuntu 15.04 server I get an error:
     * service[ssh] action enable

       ================================================================================
       Error executing action `enable` on resource 'service[ssh]'
       ================================================================================

       Errno::ENOENT
       -------------
       No such file or directory - /sbin/status

None of those files (enable, restart, status) exist in /sbin in the 15.04 image I'm building from. The same cookbook in the same environment builds 14.04 just fine. (and while there is no /sbin/status the command "service ssh status" works.

A follow up with some more information. Falling back to version 1.3.0 of this cookbook seems to work well in Ubuntu 15 (can log in and the config file is correct) as well as Ubuntu 14.

@Paladin This should be resolved here:
https://github.com/opscode-cookbooks/openssh/pull/62

This should be fixed in the 1.5.0 release

Same issue systemd/upstart change at debian:stretch.

I think adding smth like
if  'debian' == node['platform']
  if Chef::VersionConstraint.new('>= 9').include?(node['platform_version'])
    service_provider = Chef::Provider::Service::Upstart
  else
    service_provider = Chef::Provider::Service::Systemd
  end
end

here: https://github.com/adepue/openssh/blob/ee32e90bc66d94a22b0ff82814e49d8d1b3d931e/recipes/default.rb#L69
will resolve issue


Add settings for speed and cargo.

Add settings for speed and cargo.
Fix Ukrainian locale.
Made sample changelog edit and minor version bump, up to OP what they want to do about those bits.

The max_speed property for rolling_stock prototypes is in tiles per tick. That's the 1.2 default for the vanilla locomotive. Tiles are considered to be 1 metre per side, it's somewhere on the wiki. So to convert from kilometres per hour to tiles per tick, I divide by 60 three times (60 ticks per second, 60 seconds per minute, 60 minutes per hour). The default values are just the reverse -- take the values you used, and multiply by 60 three times.
The max speed for the wagons is set to be 33% higher than the equivalent locomotive, following the pattern shown by the vanilla loco and wagons.

Added new settings with commit 844d184, now available on the mod portal. Thanks!


API specs lost if predefined spec includes an endpoint at '/'

First of all, this module is awesome - thank you for maintaining it!
Overview of the Problem
I ran into an issue today on an application which I think has a fairly simple solution. I'm going to submit a PR for it and would appreciate someone looking through it to make sure there aren't any unintended side-effects.
Basically, if the existing oas document has an endpoint defined with the path '/', the generator fails to write an entry to the oas document for any API which:

Has any path params or query params
AND has a trailing slash in the request url path

Reproducing the Problem
Use the attached express server to generate docs.
minimal-reproduction.zip
This server has two endpoints: GET  / and GET  /some/other/endpoint/with/{pathParam}.

Run the server with node index.js
Call the endpoint http://localhost:3001/some/other/endpoint/with/5/ Note the trailing slash on the URL
Check the generated oas docs - there shouldn't be any response information (or detailed param information) in the doc for this endpoint
Call the endpoint again but remove the trailing slash (http://localhost:3001/some/other/endpoint/with/5)
Check the oas docs again - there should now be detailed param and response information in the doc
The server has a git repo bundled so you can reset the oas docs.

More Details
I tracked the issue down to getPathKey() in index.js, specifically where it generates the regex for checking the path keys. The regex is currently generated with this line:
`${pathKey.replace(/{([^/]+)}/g, '(?:([^\\\\/]+?))')}/?$`

In the case where the pathKey is '/', that will result in this pattern being generated:
`//?$`

This pattern will match any character string that ends with a forward slash. In addition, the path key is checked by getPathKey() only if the request url doesn't exactly match the path key in the swagger doc, which happens if it has path params or query params. So the end result here is that if a URL has path params or query params and also has a trailing slash, and if the swagger document includes a path key that is at the root of the api ('/'), then it will be merged into the swagger doc entry for the path '/' rather than the entry for the correct path.
This particular issue can be fixed very simply by adding a beginning check (^) to the generated pattern like so:
`^${pathKey.replace(/{([^/]+)}/g, '(?:([^\\\\/]+?))')}/?$`

That would then result in the following pattern being generated for the pathKey '/':
^//?$

Which will no longer incorrectly match other paths with trailing slashes.
Can anyone see any side-effects of this proposed change?
I'll submit a PR with tests soon.

Thanks, Aaron for raising the issue. I see no potential problem with the described solution. The PR is very welcome!


IPv6 for overlay network?

Is it possible to use IPv6 for the internal overlay network? Our IPv4 RFC1918 allocation strategy has been...not good.

Not currently, but this was a conscious decision in the short term. Support for IPv6 as the underlying udp transport is something we will likely get to in the near term.
As far as Nebula IPs, they have an interesting property that led to us not directly supporting IPv6, namely that you can create nebula IPs sequentially, regardless of where in the world that host lives. This means that you can efficiently use an ip range of whatever size makes sense in your organization, because you don't need to divide things into subnets for routing.

I think he was referring to the fact that given the big or complex enough landscape, in brownfields you can end up with partial overlappings that break local traffic as soon as you establish the tunnel.
Here local traffic would be endpoints external to the overlay that are routed by local network elements.

hi , with tinc vpn there is a router/switch/hub modes(i use with brctl to bridge local network to vpn network).....that will exist in the nodes of  nebula? or some way to bridging local physical network to nebula overlay network ?

As far as Nebula IPs, they have an interesting property that led to us not directly supporting IPv6, namely that you can create nebula IPs sequentially, regardless of where in the world that host lives. This means that you can efficiently use an ip range of whatever size makes sense in your organization, because you don't need to divide things into subnets for routing.

How exactly is IPv6 not compatible with sequential numbering? All of the random and generated address schemes are optional. Assuming Nebula IPs were out of 2001:db8:1234:5678::/64, if desired they can be allocated 2001:db8:1234:5678::1, 2001:db8:1234:5678::2,  and so on.
IPv6 has the advantage of having enough address space to not conflict with anything, from any organization, globally. Nebula IPs could come from v6 "public" allocations, or Unique Local Addresses.
v6 also solved the big enough address range problem. All subnets are /64. Every net that wants one can get a /64.

IPv6 has the advantage of having enough address space to not conflict with anything, from any organization, globally. Nebula IPs could come from v6 "public" allocations, or Unique Local Addresses.
v6 also solved the big enough address range problem. All subnets are /64. Every net that wants one can get a /64.

ipv6 could also be used to address one significant issue with Nebula, which is that the scope of trust for the CA is too broad.  Not only is this an opportunity for accidents/shenanigans, it makes scenarios where you want multiple authorities (limited scope delegation, multi-tenancy)  untenable.  Scoping CAs to a single /64 would enable this.

How exactly is IPv6 not compatible with sequential numbering? All of the random and generated address schemes are optional. Assuming Nebula IPs were out of 2001:db8:1234:5678::/64, if desired they can be allocated 2001:db8:1234:5678::1, 2001:db8:1234:5678::2, and so on.

@jpmahowald I was not saying ipv6 is incompatible with the numbering. Sorry for the confusion. I was saying that because nebula doesn't care about routes, we can efficiently use ipv4 addresses with ease. A single /16 worth of addresses can represent 65,534 hosts without wasting a single address.

ipv6 could also be used to address one significant issue with Nebula, which is that the scope of trust for the CA is too broad. Not only is this an opportunity for accidents/shenanigans, it makes scenarios where you want multiple authorities (limited scope delegation, multi-tenancy) untenable. Scoping CAs to a single /64 would enable this.

In what way is the scope of trust currently too broad, and how does an ipv6 /64 change this?

I too vote/wish for IPv6 support in the overlay.

@rlyeh In what way is the scope of trust currently too broad, and how does an ipv6 /64 change this? We support limiting CA scope via groups, and in practice we write all rules based on groups, never ip/network/hostname. Adding the capability to limit the subnets a CA can address may be useful to others, so I guess this is something we may do in the future.

I was referring to limiting the networks the CA can address, in the CA itself (via Name Constraints).  Ideally this combined with proper support for sub-ca's, allowing for rigorous control in some address spaces and lax control in others, with one or two roots of trust.

IPV6 combined with subgroups (eg. wildcarded groups) would also solve our requirements. Can someone provide the status or document what is blocking this?

I'm doing Nebula with non-RFC1918 globally routable space (and I'm actually routing to my nebula network from the internet) as part of a broadcast video platform. The ability to push v6 around the same way would be super useful for my (admittedly nonstandard) usecase, especially as we're ditching v4 as much as possible elsewhere in the platform.

As a current ZeroTier user, I've been referred to this project as an up-and-coming alternative, but I personally cannot consider it ready for prime time until IPv6 addressing in the overlay network is available.
The IPv4 address space of my mobile provider occupies the entire <IP_ADDRESS>/8 subnet, and I've seen public Wi-Fi networks that do the same - that breaks most IPv4 VPN's right there. Plus, I have containers, virtual machines, LAN segments, etc. that need to be reachable behind my machines. All of this complexity would be completely unmanageable with pure RFC1918 IPv4 addressing.

This is currently implemented in master and should be considered beta until we release v1.4.0

I am a new (tentative) Nebula user, and I naively tried to use IPv6 addresses in the overlay. The thing is, the fact that IPv6 is not supported is not obvious, I didn't find a mention in the documentation and the certificate generation tool didn't complain, stuffing inside the certs the lower 32 bits of the addresses I provided.
This led to some confusion and wasted time, and I had to dig a little inside the Nebula code to understand what was happening. Would it be possible to let nebula-cert throw out an obvious fatal error on invalid addresses?

any updates on this?

It's something that we would like to support but is not high on our priority list at the moment.

I am a new (tentative) Nebula user, and I naively tried to use IPv6 addresses in the overlay. The thing is, the fact that IPv6 is not supported is not obvious, I didn't find a mention in the documentation and the certificate generation tool didn't complain, stuffing inside the certs the lower 32 bits of the addresses I provided.
This led to some confusion and wasted time, and I had to dig a little inside the Nebula code to understand what was happening. Would it be possible to let nebula-cert throw out an obvious fatal error on invalid addresses?

The very same happened to me as nebula-cert seems to interpret an IPv6 address ending in e.g. ::c013/64 (defacto …:0000:c013/64) as <IP_ADDRESS>/0, but only for the network, not for the host IP itself. This results in such weird error messages like this one:
ERRO[0000] static_host_map key is not in our subnet, invalid  network=<IP_ADDRESS>/0 vpnIp="[…]::c013"

So yes, at least an error message or a helpful line in the example config (quicker, but needs to be removed again later) would already help here to avoid further wasted time (and probably also unnecessary support requests).

I, like all other colleagues and friends, really need IPv6 support in the overlay.
This functionality will avoid address conflicts when using a nebula.
This would greatly expand the possibilities of use.
Could you clarify why this is not a priority?
In any case, thanks for a cool project!

I also vote for the implementation of IPv6 support in the overlay. Thank you for your efforts.

I also vote for the implementation of IPv6 support in the overlay! Thanks :-)

github has reactions.
please vote by adding your reaction to the first post.
each (useless) comment in here just results in spamming everyone subscribing to this issue.

I am trying to gauge the likelihood of ipv6 in the future. Is there any sort of roadmap for this feature?
It would be helpful in my early stages of deciding on a solution to be able to gauge whether I should roll out a Nebula network with the assumption that ipv6 may be down the line or whether to play it safe and start with another solution.

🤔


RuntimeError: Checksum mismatch after transfer

I dont know if the syntax is right.
I'm using:
 ./bscp  /dev/sda2 <IP_ADDRESS>:/dev/sda2
And I get:
Traceback (most recent call last):
  File "./bscp", line 162, in <module>
    (in_total, out_total, size) = bscp(local_filename, remote_host, remote_filename, blocksize, hashname)
  File "./bscp", line 142, in bscp
    raise RuntimeError('Checksum mismatch after transfer')
RuntimeError: Checksum mismatch after transfer

No other output before that.
I have python 2.7.15rc1 in Ubuntu 18.

This is strange.
The error message means that all blocks had correct checksums, but the overall checksum did not match.
To debug this, please try to do the same with files rather than devices. Also, you might want to use smaller files (i.e. tens of megabytes rather than gigabytes).

The same here. Both devices have different checksum after running bscp, devices are unmounted.# # python2 -V
Python 2.7.15
Gentoo

I can see possible problem in invoking python on remote side. Default version of python is 3.x but changing bscp in this way:
-        remote_command = 'python -c "%s"' % (remote_script,)
+        remote_command = 'python2 -d -c "%s"' % (remote_script,)
``` didn't solve problem. How to catch output from snippet running on remote side?

Both sides communicate over a binary protocol. Mostly transferring raw data (from the block devices), also exchanging size and checksum information in between. Essentially, you can intercept any ".read()" and ".write()" and print the received value (size, checksum, raw data) to the console.

@xtaran Thanks for your thorough analysis! I fully agree with it and accepted the pull request.

To anyone involved in this issue, please see #16 "Future of bscp".


onChange function triggers too frequently in v4.0.0-alpha.12

I'm trying to use the new feature in v4 of MUI that allows you to disable certain time ranges and I am facing an issue where the onChange function is triggering when it's not supposed to.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

I have a controlled component that uses the Time Picker and receives it's value and change function from a parent component. When I click to open the time picker, the modal opens up showing hours and minutes (as expected), when I click on a new hour, this change is instantly submitted and the onChange function runs and my component re-renders with the new value and the modal closes. The sane happens when I click to change from AM to PM, the onChange function runs re-rendering my component and closing the modal as a result. This actually happens for any time change.
Expected Behavior 🤔

What I expected to happen is something similar to the v3.2.10 release where the onChange function is  only triggered when the user submits their value by clicking the "ok" button, and is able to discard the pending changes they made by clicking the "cancel" button, meaning the onChange function would only run when the user has submitted their final time choice.
Steps to Reproduce 🕹

Steps:

Context 🔦

Your Environment 🌎

Tech
Version

@material-ui/core
v4.11.0

@material-ui/pickers
v4.0.0-alpha.12

React
16.13.1

Browser
Chrome

TypeScript

etc.

@jbyomuhangi Thanks for raising, agree. We have #2001 and #1980 that touch on this very problem. It's almost a duplicate.


[hotfix/ZF2-86] Zend\View

If you call $this->render('somescript.phtml') from within a layout script, the layout variables are erased. Calling something like echo $this->raw('content') later in the layout script results in an empty string being echo'd.

Nice and clean! Merged and pushed to master.


MMT 2.1 neural trainning is using more card memory

I'm currently testing the latest version. The new version is nearly saturating the card memory, while the previous one was using half of it. I just wonder if this is the expected behaviour of the new version. There is perhaps a small risk to overload the card...

Hi @EtienneAb3d,
From version 2.0.2 to version 2.1 there were no relevant changes in the internal structures we save in the GPU RAM, so it is hard to figure why your GPU card appears more heavily loaded.
In our tests, updating CUDA drivers and PyTorch did not affect the GPU RAM load.
However note that during training the GPU RAM usage is very unstable (it has a sort of irregular sinusoid pattern), so you may be experiencing a very temporary peak.
A way to be completely safe from GPU overloading in any case is to use a smaller batch size.
You can choose manually the batch size to use in our training with option --batch-size in ./mmt create command (default is 64 lines).
I hope this helps!
Have a nice day :)
Andrea

In exactly the same conditions, when training on the other languages sens, after 2 checkpoints, it is still using only 5G, like with the previous version. Waiting to see if the amount is increasing at some time..

After 1 epoch, it is using 6G. A bit more, but far from the 10G above.


安装不上

FAILURE: Build failed with an exception.

What went wrong:
Task 'initFreeline' not found in root project 'DZ'.

Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.

BUILD FAILED
Total time: 2 mins 10.119 secs

@cubebbox apply plugin: "com.antfortune.freeline"..按照REAMDE或者sample来做即可...

已经按照了sample来做的依然提示如下：
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.or
g/2.14.1/userguide/gradle_daemon.html.
FAILURE: Build failed with an exception.

What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:

Error occurred during initialization of VM
Could not reserve enough space for 1572864KB object heap

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

我的gradle：
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.0'
classpath 'com.antfortune.freeline:gradle:0.8.2'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
我的app 的gradle：
apply plugin: 'com.android.application'
apply plugin: 'com.antfortune.freeline'
android {
compileSdkVersion 24
buildToolsVersion '24.0.0'
defaultConfig {
applicationId "com.chuangke.designer"
minSdkVersion 15
targetSdkVersion 24
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
productFlavors {
}
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_7
targetCompatibility JavaVersion.VERSION_1_7
}
}
dependencies {
androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
exclude group: 'com.android.support', module: 'support-annotations'
})
compile project(':frame')
compile project(':widgets')
compile project(':multi-image-selector')
}

@cubebbox 按照错误日志google一下就行...跟freeline无关...
Android Studio Gradle Could not reserve enough space for object heap


OpenSSL incompatibilities with SChannel

Hello,
I have set up a secure SSL connection between a Mariadb client and a Mariadb server.
Upon upgrade from OpenSSL 3.0.6 to 3.0.7, the Windows-based client now refuses to connect to the server with an SSL error:
SSL connection error: no cipher match. Error 0x80090331(SEC_E_ALGORITHM_MISMATCH)
Files are attached certificates-and-keys.zip and generated as follows:
# CA cert
$ openssl req -x509 -newkey rsa:2048 -keyout ca.key -out ca.crt -days 365 -nodes -subj '/C=EU/ST=Europe/O=test/CN=test.com/' -sha256

# Server cert
$ openssl req -newkey rsa:2048 -days 365 -nodes -keyout server.key -subj '/C=EU/ST=Europe/O=server test/CN=server.test.com/' -sha256 > server.csr
$ openssl x509 -req -in server.csr -days 365 -CA ca.crt -CAkey ca.key > server.crt

# Client cert
$ openssl req -newkey rsa:2048 -days 365 -nodes -keyout client.key -subj '/C=EU/ST=Europe/O=client test/CN=client.test.com/' -sha256 > client.csr
$ openssl x509 -req -in client.csr -days 365 -CA ca.crt -CAkey ca.key > client.crt

OpenSSL version on the server: OpenSSL 3.0.7 1 Nov 2022
Server: MariaDB 10.9.4 running on ArchLinux 01SEP 2022
OpenSSL conf file:  openssl.cnf.zip
Client: HeidiSQL (linked with MariaDB C Connector, itself linked with SChannel)
Client system: Windows 10 22H2 19045.2486
Wireshark capture: wireshark_capture.zip
As you can see the client abruptly aborts the connection for some reason.
The client and the server are able to find a common cipher algorithm, but I suspect that it cannot find a common signature algorithm.
Adding more verbose logging on SChannel via the registry doesn't give more information; the system simply tells about a "bad handshake".
The logs of the server are not helpful either. The server only sees an aborted connection from the client.
Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: '<IP_ADDRESS>' (This connection closed normally without authentication).
Using other clients (Python, etc...) fails as well as they are all linked with SChannel on Windows.
Similar issues

Using CipherString = DEFAULT:@SECLEVEL=1 as recommended here did not help.
Similar issue posted in parallel on the client: https://github.com/HeidiSQL/HeidiSQL/issues/1426

Can you please help with the issue? Getting desperate about this after having spent days. Only workaround was to disable SSL requirement.
Thanks a lot and best regards

Using CipherString = DEFAULT:@SECLEVEL=1 as recommended here did not help.

Could you please try to use CipherString = DEFAULT:@SECLEVEL=0 ?

Is it possible to get a wireshark capture of a working server (i.e. with OpenSSL 3.0.6)...it might help identify the differences. The wireshark capture you provided doesn't show anything untoward that I can identify up until the point that the client abruptly closes the connection.

Thanks, it works with CipherString = DEFAULT:@SECLEVEL=0
Attached Wireshark capture of a working server still with OpenSSL 3.0.7: good_seclevel0.zip
The server seems to advertise more signature algorithms:
BAD
Signature Hash Algorithms (20 algorithms)
[...]

GOOD
Signature Hash Algorithms (23 algorithms)
[...]
    Signature Algorithm: ecdsa_sha1 (0x0203)
    Signature Algorithm: rsa_pkcs1_sha1 (0x0201)
    Signature Algorithm: SHA1 DSA (0x0202)

It almost certainly is related tot he sig algs. In particular the added sig algs all use SHA1 which is widely considered to be broken. Probably the aborting client is relying on them.
I'm slightly surprised that this behaviour changed between 3.0.6 and 3.0.7 though. SHA1 was supposed to be disabled in the default security level in 3.0.0, so I would have expected this to already be broken in 3.0.6. I'm wondering what has changed to cause this.

Interestingly there is an overlap between between the sigalgs supported by the client and those supported by the server.
For example when it comes to declaring support for signature verification the client claims to support "rsa_pkcs1_sha256" and the server also claims to be able to support verifying this algorithm. But when it comes to signature generation it seems that the client is only willing to support sha1 based sig algs. This seems like quite a significant deficiency on the client side.

Even more curious is that I am currently unable to find a difference between 3.0.6 and 3.0.7 that would explain this. In my testing it seems that a 3.0.6 server will not claim support for SHA1 based sig algs at the default security level.
E.g. running s_server like this with 3.0.6:
openssl s_server -verify 5 -no_tls1_3

Results in the following sig algs being advertised in the CertificateRequest:
        ecdsa_secp256r1_sha256 (0x0403)
        ecdsa_secp384r1_sha384 (0x0503)
        ecdsa_secp521r1_sha512 (0x0603)
        ed25519 (0x0807)
        ed448 (0x0808)
        rsa_pss_pss_sha256 (0x0809)
        rsa_pss_pss_sha384 (0x080a)
        rsa_pss_pss_sha512 (0x080b)
        rsa_pss_rsae_sha256 (0x0804)
        rsa_pss_rsae_sha384 (0x0805)
        rsa_pss_rsae_sha512 (0x0806)
        rsa_pkcs1_sha256 (0x0401)
        rsa_pkcs1_sha384 (0x0501)
        rsa_pkcs1_sha512 (0x0601)
        ecdsa_sha224 (0x0303)
        rsa_pkcs1_sha224 (0x0301)
        dsa_sha224 (0x0302)
        dsa_sha256 (0x0402)
        dsa_sha384 (0x0502)
        dsa_sha512 (0x0602)

So, no mention of SHA1. Modifying the command to this:
openssl s_server -verify 5 -no_tls1_3 -cipher "DEFAULT:@SECLEVEL=0"

Results in the SHA1 sigalgs appearing:
        ecdsa_secp256r1_sha256 (0x0403)
        ecdsa_secp384r1_sha384 (0x0503)
        ecdsa_secp521r1_sha512 (0x0603)
        ed25519 (0x0807)
        ed448 (0x0808)
        rsa_pss_pss_sha256 (0x0809)
        rsa_pss_pss_sha384 (0x080a)
        rsa_pss_pss_sha512 (0x080b)
        rsa_pss_rsae_sha256 (0x0804)
        rsa_pss_rsae_sha384 (0x0805)
        rsa_pss_rsae_sha512 (0x0806)
        rsa_pkcs1_sha256 (0x0401)
        rsa_pkcs1_sha384 (0x0501)
        rsa_pkcs1_sha512 (0x0601)
        ecdsa_sha224 (0x0303)
        ecdsa_sha1 (0x0203)
        rsa_pkcs1_sha224 (0x0301)
        rsa_pkcs1_sha1 (0x0201)
        dsa_sha224 (0x0302)
        dsa_sha1 (0x0202)
        dsa_sha256 (0x0402)
        dsa_sha384 (0x0502)
        dsa_sha512 (0x0602)

So, basically, it is currently unclear how this ever worked for you with OpenSSL 3.0.6. It should be behaving the same way as 3.0.7 in this regard. Unless there was some other difference in configuration between the two versions??

Maybe this makes more sense and explains the issue more accurately!

Yes! If it was actually using 1.1.1q then that would explain a lot. SHA1 was still available at the default security level then. That was changed from 3.0.0.
Unfortunately, it doesn't help a lot solving your problem. The client insists on using SHA1 for signing even though it is perfectly capable of using other digests for verifying. If you don't have control of the client, and you want to allow the client to sign using SHA1, then I think the only option left is to lower the default security level to allow it.

If you compare that list with the list I gave above in https://github.com/openssl/openssl/issues/20138#issuecomment-1405041440 you'll see that they shoull all already be being advertised. Those are all in the default sigalgs list.

Indeed I wasn’t paying attention. I’ll close this for now.
Thanks all!
If you have any idea where I could file a bug report with SChannel I’ll gladly take it.

If you have any idea where I could file a bug report with SChannel I’ll gladly take it.

No idea. Sorry.

Note: Jira issue created here with MariaDB C Connector: https://jira.mariadb.org/browse/CONC-639


Videonauth: Watch cryptoexchangescript.com

Videonauth requests the watch of the watch_keyword cryptoexchangescript\.com. See the Metasmoke search here and the Stack Exchange search here.

cryptoexchangescript\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Coverage remained the same at 65.732% when pulling 082030a259ef37adf319e479cb07c35afec6d6e8 on auto-blacklist-1527936496.2649848 into 88cbffb6fc9120efd97d6d18428d99db71622448 on master.

!!/approve


Exclude the generated proto files in the repo

https://github.com/alibaba/GraphScope/blob/101ab6f3f19dfcaceb8f1ea5bbcd97420815668c/interactive_engine/src/api/sdk-common/src/main/generated/com/alibaba/maxgraph/proto/AddIndexReq.java#L1
and the whole folder in GraphScope/interactive_engine/src/api/sdk-common/src/main/generated/com/alibaba/maxgraph/proto
the java code of proto files should be compile with maven, with the dep:
<dependency>
    <groupId>com.google.protobuf</groupId>
    <artifactId>protobuf-java</artifactId>
    <version>${protobuf.version}</version>
</dependency>

BTW, I found in many java repo, it seems that a common practice for the location of proto files is:
src/main/resources/protobuf/
# or
src/main/resources/proto/

btw, a single file GraphScope/interactive_engine/src/api/sdk-common/src/main/generated/com/alibaba/maxgraph/Message.java is 1.69M!

Known files to exclude:
/interactive_engine/src/api/sdk-common/src/main/generated/*
/interactive_engine/src/common/java/src/main/generated*

Known files to exclude:
/interactive_engine/src/api/sdk-common/src/main/generated/*
/interactive_engine/src/common/java/src/main/generated*
/interactive_engine/src/common/rust/common/src/proto/mod.rs

Generated files are removed. mod.rs is required.


Backport action: Automatically delete old branches

It would be nice if the GitHub action for backports would automatically delete branches in NixOS/nixpkgs after merging or closing PRs (or if we had another GH action that deletes old backport-* branches without an open PR). It might also be desirable to create the branches in a different repository (that way the backport action might not even need write access to Nixpkgs).
Initially I didn't know that I had to delete these branches manually (https://github.com/NixOS/nixpkgs/pull/127458#issuecomment-865003289) but even if one knows this it requires an additional manual step that might be easy to miss once in a while.

In the project settings there is "Automatically delete head branches" which may also work.

In the project settings there is "Automatically delete head branches" which may also work. Description is "After pull requests are merged, you can have head branches deleted automatically." and it notes "Deleted branches will still be able to be restored."

This won't work because there are branches which would briefly (multiple hours) be head branches, but have PRs targeted against them, like haskell-updates. Deleting such a branch results in all PRs targeted against it being deleted.

i have been removing the merged branches manually using
https://github.com/NixOS/nixpkgs/branches/all?query=backport


Missing Attribute Types?

This page lists the Metadata Objects for Boolean, Picklist, State, and Status, but what about the others? The various numeric types... Date Time, Lookup/Customer/Owner, Text...

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

ID: bf6143f9-6760-18c0-a08f-196c8bce8c2f
Version Independent ID: 74a79a52-be75-ad56-642c-8a3aa6b5ab0d
Content: getEntityMetadata (Client API reference) in model-driven apps - Power Apps
Content Source: powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Utility/getEntityMetadata.md
Service: powerapps
Sub-service: mda-developer
GitHub Login: @adrianorth
Microsoft Alias: aorth

Thanks for your comment, @devlinl. This issue has been assigned to the doc author for review.

@devlinl
Thanks for your feedback. Sorry for the delay in responding.
I think that the Attribute objects section is pretty clear.
All types return the Base (AttributeMetadata) columns, and the AttributeType property tells you what type.
Only the types mentioned include additional properties. For example, some return an OptionSet, and this object has some different methods.
This API doesn't seem to return all available AttributeMetadata Class or derived class properties. It appears to be a selected set of properties that have value for client-side scripting.
Are you seeing that it returns more properties than documented?

You're correct that not all metadata attributes are returned... So, for the Text fields, it doesn't return Max Length, and for the numeric fields, it doesn't return Min Value and Max Value. However, there are definitely several metadata attributes that are returned for many column types which are not documented here.

Money

Precision
PrecisionSource (I didn't check what the values for this mean)

DateTime

Behavior (1: User Local, 2: Date Only, 3: Time Zone Independent)
Format ("date" or "dateandtime")

Decimal & Double

Precision

Integer

Format (0: None, 1: Duration, 2: Time Zone, 3: Language)

Lookup

Targets

OK. I see your point.
Pasting this function in the Developer tools console:
var entityName = "account";
var attributes = [
  "revenue",
  "createdon",
  "exchangerate",
  "address1_latitude",
  "opendeals",
  "primarycontactid"];

// Define the success callback function
var successCallback = function (result) {
  // Log the result to the console
  result.Attributes.forEach(attribute => {
    console.log(attribute.LogicalName);
    console.log(` AttributeType=${attribute.AttributeType}`)
    console.log(` LogicalName=${attribute.LogicalName}`)
    // Money, Decimal, & Double have Precision
    if(attribute.Precision){
      console.log(` Precision=${attribute.Precision}`)
    }
    // DateTime has Behavior
    if(attribute.Behavior){
      console.log(` Behavior=${attribute.Behavior}`)
    }
    // DateTime and Integer have Format
    if(attribute.Format){
      console.log(` Format=${attribute.Format}`)
    }
    // Lookups have Targets
    if(attribute.Targets){
      console.log(` Targets=${attribute.Targets}`)
    }

  });
};

// Define the error callback function
var errorCallback = function (error) {
  // Log the error to the console
  console.error(error);
};

// Call the Xrm.Utility.getEntityMetadata function
Xrm.Utility.getEntityMetadata(entityName, attributes).then(successCallback, errorCallback);

I get output like this:
revenue
   AttributeType=8
   LogicalName=revenue
   Precision=2
createdon
   AttributeType=2
   LogicalName=createdon
   Behavior=1
   Format=dateandtime
exchangerate
   AttributeType=3
   LogicalName=exchangerate
   Precision=10
address1_latitude
   AttributeType=4
   LogicalName=address1_latitude
   Precision=5
opendeals
   AttributeType=5
   LogicalName=opendeals
   Format=0
primarycontactid
   AttributeType=6
   LogicalName=primarycontactid
   Targets=contact

This demonstrates that the properties you listed (Precision, Behavior, Format and Targets) are returned, and they aren't included in the document.
This doesn't test for others, but it is evidence that the documented properties are incomplete.
I'll take this up with the dev team. IDK why only a few were documented, or perhaps more were added over time.


ng test logging

Hi Guys,
Is it possible to output

ng test --watch=false --build=false

to external file? so that I can parse the file in TeamCity and fail the build. I tried below

ng test --watch=false --build=false > log.txt

but it only write True in it. It would be good to have full output in a file like

ng test --watch=false --build=false --output=path\log.txt

If you need to correctly run tests on teamcity use karma-teamcity-reporter with phantomjs browser (because I don't think that Chrome will work on teamcity, eventually it will timeout).
Just install these npm dependencies:
npm i karma-phantomjs-launcher phantomjs-prebuilt karma-teamcity-reporter --save-dev
Import them in karma.conf.js plugins:
config.set({
  ...
  plugins: [
    ...
    require('karma-phantomjs-launcher'),
    require('karma-teamcity-reporter')
  ],
  ...
});

And you're ready to run ng test --watch=false --browsers=PhantomJS --reporters=teamcity.
Using this method it will even show the details of successful/failed tests and of course fail your build if needed.

@kamran-pervaiz Is this issue still on ?  Did you solve it ?
Otherwise, you can try this:  ng test --watch=false --build=false 1>log.txt 2>&1.

Closed as outdated.

@dzonatan @catull @filipesilva
sorry i was away for other project and never tried it, I am back on the same project and will try tomorrow. will update you

@kamran-pervaiz the lines starting with TypeError: mean you have an error in your code that prevents TS compilation. Have a look at that, and also try using a browser other than PhantomJS (it's very outdated and has a lot of problems).

@filipesilva thanks filip I have managed to make it work for now. i uncommented polyfill.ts and it started working. as for upgrading phantomJs to other browser what is your recommendation? chrome headless? will it report to teamcity?


[Bug] no messages are generated, the TOOLS_CONSUMER consumer group has been consuming messages quickly.

Before Creating the Bug Report

[X] I found a bug, not just asking a question, which should be created in GitHub Discussions.

[X] I have searched the GitHub Issues and GitHub Discussions  of this repository and believe that this is not a duplicate.

[X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment
centos8
RocketMQ version
4.9.7
JDK Version
1.8
Describe the Bug
The dashboard interface shows that a large number of messages were consumed today, but no messages are actually generated at this time. Check stat.log, the information is as follows：
dashboard界面显示今日消费了大量消息，此时实际上并没有消息产生，查看stat.log,信息如下：
2023-12-06 13:45:00 INFO - [GROUP_GET_LATENCY] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, TIMES: 293665 AVGRT: 0.02
2023-12-06 13:45:00 INFO - [GROUP_GET_NUMS] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM: 3817645 TPS: 63627.42 AVGPT: 13.00
2023-12-06 13:46:00 INFO - [GROUP_GET_SIZE] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM:<PHONE_NUMBER> TPS: 69412257.90 AVGPT: 14073.00
2023-12-06 13:46:00 INFO - [GROUP_GET_LATENCY] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, TIMES: 295940 AVGRT: 0.02
2023-12-06 13:46:00 INFO - [GROUP_GET_NUMS] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM: 3847181 TPS: 64119.68 AVGPT: 13.00
2023-12-06 13:47:00 INFO - [GROUP_GET_SIZE] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM:<PHONE_NUMBER> TPS: 70000274.75 AVGPT: 14073.00
2023-12-06 13:47:00 INFO - [GROUP_GET_LATENCY] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, TIMES: 298444 AVGRT: 0.02
2023-12-06 13:47:00 INFO - [GROUP_GET_NUMS] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM: 3879798 TPS: 64663.30 AVGPT: 13.00
2023-12-06 13:48:00 INFO - [GROUP_GET_SIZE] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM:<PHONE_NUMBER> TPS: 68720335.40 AVGPT: 14073.00
2023-12-06 13:48:00 INFO - [GROUP_GET_LATENCY] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, TIMES: 292988 AVGRT: 0.02
2023-12-06 13:48:00 INFO - [GROUP_GET_NUMS] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM: 3808857 TPS: 63480.95 AVGPT: 13.00
2023-12-06 13:49:00 INFO - [GROUP_GET_SIZE] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM:<PHONE_NUMBER> TPS: 59952621.85 AVGPT: 14073.00
2023-12-06 13:49:00 INFO - [GROUP_GET_FALL_TIME] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats Every 5 Minutes, Value: -5634663807447474569
2023-12-06 13:49:00 INFO - [GROUP_GET_LATENCY] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, TIMES: 255609 AVGRT: 0.02
2023-12-06 13:49:00 INFO - [GROUP_GET_NUMS] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM: 3322891 TPS: 55381.52 AVGPT: 13.00
2023-12-06 13:49:00 INFO - [GROUP_GET_FALL_SIZE] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats Every 5 Minutes, Value: 152237
2023-12-06 13:50:00 INFO - [GROUP_GET_SIZE] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM:<PHONE_NUMBER> TPS: 69943044.55 AVGPT: 14073.00
2023-12-06 13:50:00 INFO - [GROUP_GET_LATENCY] [2@sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, TIMES: 298200 AVGRT: 0.02
2023-12-06 13:50:00 INFO - [GROUP_GET_NUMS] [sms_batch_send_topic@TOOLS_CONSUMER] Stats In One Minute, SUM: 3876613 TPS: 64610.22 AVGPT: 13.00
Steps to Reproduce
Unable to reproduce
What Did You Expect to See?
Know what causes this problem
What Did You See Instead?
Know what causes this problem
Additional Context
No response

dashboard里面有一些功能（查询消息等），会使用TOOLS_CONSUMER 作为消费者消费，有可能造成这个现象，之前遇到过。
如果持续增长，重启一下dashbaord一般就可以了，dashboard里面有一个查询的地方，有个死循环我记得。


Unitless breakpoints

If I want to customise the breakpoints using em, I get compatibility errors.
$grid-breakpoints: (
    default: 0em,
    watch: 20em,
    phone: 30em
    // etc.
}

It is good practice to set breakpoints in em instead of px when users change font size in their browser. See https://zellwk.com/blog/media-query-units/#concluding-the-experiments for more information why someone would like to do this. Only Safari users could get annoyed: https://adamwathan.me/dont-use-em-for-media-queries/
In any case, using a unitless number at line 42 would be very convenient.

While it seems like this may be a bad option according to Adam's article, it makes sense to me to make this change, and allow the user to choose whether or not the Safari bug is an issue for them.
I was not familiar with SCSS math, so I did a little digging into whether this is valid, and it turns out, it works!  If you use a unitless value with a value with a unit, the unit is preserved. However, mixing units will result in an error.
.style {
    height: 500em - 100;
    width: 500px - 100;
}

compiles to
.style {
    height: 400em;
    width: 400px;
}

Hi @johanlef thanks a lot for your contribution.
There has been a lot of discussion around this issue, among them #22006, #25632, #19619, #25166, and others related to why we are using pxs instead of rems or ems
Personally, I think we should look into moving to relative units, but at this point, it'd be a breaking change for v4.
Having said that I think this is a good discussion point for v5.

Okay, I understand moving to other units will be a breaking change.
@andresgalante Going from px to unitless on this particular line is not a breaking change: as @browner12 pointed out, the units are preserved.

Correct me if I'm wrong, but I don't believe this would be a breaking change in v4.
As I showed in my first comment, when doing math in SCSS, if one of the values is unitless, the other units will be preserved.
By merging this PR, all existing code would work as is, and it would allow people who choose to use em breakpoints to not run into a compile error.

@andresgalante My proposal is about removing the unit, not changing to another one. When the unit is removed, the original unit is preserved, so this change would not cause any issues.

Just so that we are safe, is this backwards compatible?

@XhmikosR I believe so—this is Sass math, and previously we required folks to use pixels only for media queries. This opens it up so others can use ems, and doesn't prevent folks from using pixels.


Sheehan et al. 2018: landesque capital intensive agriculture and sociopolitical hierarchy

http://www.pnas.org/content/early/2018/03/13/1714558115

I was just going to ask about this ^^, glad I search the issues first. I noticed some instances where this dataset has different coding from the old EA033 etc. I imagine that most of the time, this more recent set is better to use? Or that the focal year will differ and help tease the codings apart.

Not sure, you'd need to ask Sheehan et al.

Is the intention that datasets from papers like this will be added to D-place?

yes, subject to ease and availability.

Hi! I found myself thinking about this again. What's the status here? Can I help in anyway?

The datasets aggregated in D-PLACE now all have their individual, cldfbench-curated repository, e.g. https://github.com/D-PLACE/dplace-dataset-ccmc . Here's a short description how to go about creating such a repos: https://github.com/D-PLACE/pydplace?tab=readme-ov-file#usage

The datasets aggregated in D-PLACE now all have their individual, cldfbench-curated repository, e.g. https://github.com/D-PLACE/dplace-dataset-ccmc . Here's a short description how to go about creating such a repos: https://github.com/D-PLACE/pydplace?tab=readme-ov-file#usage

@SimonGreenhill would you like me to have a go at that? I can contact Oliver and work on it together with him?

ok that would be great, if you could!

ok that would be great, if you could!

sure thing, I'll add it to do -list

@SimonGreenhill
The supplementary of the paper uses ABVD codes to identify languages/societies. Are these the same as the current ABVD website and CLDF-set? There's been no change in identifiers since this paper?

yes and no (ABVD codes have never changed)

yes and no (ABVD codes have never changed)

ace

@xrotwang I assume I should make a repos within the D-PLACE organisation. Can I get access to make a new repos there?
Or should I make it just anywhere?

@HedvigS you should have received an invitation to https://github.com/D-PLACE/dplace-dataset-sheehanetal2018

@HedvigS you should have received an invitation to https://github.com/D-PLACE/dplace-dataset-sheehanetal2018

Thank you!


insert driving nuts!

Hi,
I'm trying to use SQLite.swift (iOS version) but I got stuck with the following insert statement.
XCode keeps telling me:
"Could not find an overload for 'insert' that accepts the supplied arguments"
let userDirectory = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true).first as String
let name = "test.sqlite3"
let db = Database(path)
let package: Query = db["package"]
let id: Expression = Expression("id")
db.create(table: package, ifNotExists: true) { table in
table.column(id)
}
package.insert(id <- 0) ERROR HERE!
I can't see what I'm doing wrong!

insert returns multiple types, which can be indeed confusing. I try to document the discrepancy but I wish I had control over the error message. Adding a ?, !, or checking for error/success should remedy the situation. E.g.,
package.insert(id <- 0)?


Open api docs

Description
Just OpenAPI docs
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

API Docs can be accessed at hostname/api-docs


Is OpenCFD-FWH capable of calculating the aerodynamic noise of a rotor?

Hello!
I'm interested in understanding if this code can be utilized for calculating the noise generated by a rotor. Furthermore, I would appreciate it if you could provide me with detailed information regarding the inputs and outputs of this code.
Thank you!

Hello!
Of course this code can be utilized for rotor noise problems. You need to wrap this rotor with a porous FW-H sampling surface (avoid direct passage of wakes generated by the rotor through the sampling surface, i.e. withour endcap). As for the inputs and outputs of this code, please refer to this article: https://arxiv.org/abs/2312.16263 and use the tutorial cases.
Best regards.

OK！I get it!
Thank you for your help!
Have a nice day!


merge package template from Kronos-Tools/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(engines): update<EMAIL_ADDRESS>from template
docs(package): remove keyword null

.travis.yml

chore(travis): merge from template .travis.yml

Coverage remained the same at 91.667% when pulling<PHONE_NUMBER>9929839eab867dc5efe6a8fdbaf5e3 on template-sync-1 into ebd99bf04e97c5420e0929b3d3a9a03ade6eb874 on master.

Codecov Report

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

@@          Coverage Diff           @@
##           master     #83   +/-   ##
======================================
  Coverage    92.3%   92.3%
======================================
  Files           1       1
  Lines          26      26
======================================
  Hits           24      24
  Misses          2       2

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 ebd99bf...2958490. Read the comment docs.


Don't require apps to use com.google.android.c2dm.permission.RECEIVE permission for GCM/FCM

This PR allows apps to use and register to FCM without having to add com.google.android.c2dm.permission.RECEIVE permission in their manifest.
That's because this permission is not required anymore by FCM (see this official migration guide from GCM to FCM, minute 3:15) and causes apps that don't use it to crash (e.g. Google Earth amongst others).
This should fix #1113, fix #939, fix #918 and fix #866.
Note: I haven't tested this PR on a device due to a lack of time. I've just checked that the code builds successfully.

I think you just fixed the notification settings (FirebaseRemoteConfig was giving errors) in the Disaster Prediction App (com.disasterprediction.ios) ... notifcation settings seem to be setting now, waiting for earthquakes and space weather notifcations show up to make it sure it's all working. Thanks.

@Fs00 the official migration guide is incomplete https://developers.google.com/cloud-messaging/android/android-migrate-fcm#remove-from-androidmanifest.xml
non official migration guide from GCM to FCM https://mobikul.com/migrating-fcm-gcm/
says: delete all com.google.android.c2dm.*

@Fs00 the official migration guide is incomplete https://developers.google.com/cloud-messaging/android/android-migrate-fcm#remove-from-androidmanifest.xml

Yep! In fact at first I looked at the guide you linked. But then I saw the official video guide I linked above, where Google recommends to remove that permission from the manifest.