Rawio improvement

See #895
Some important change in rawio API.

use now the concept of signals_stream + signal_channels to avoid ambiguity
_get_analogsignal_chunk work with local to stream index
better raw_annotations
raw_annotations also handle array_annotations
signal 'id' is now a str (like all other 'id')

TODO:

create generic lay object
implemnent prefer_slice=True/False

For nowonly ExampleIO/Examplerawio is done.

Hello @samuelgarcia! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/io/basefromrawio.py:

Line 139:13: E265 block comment should start with '# '
Line 140:13: E265 block comment should start with '# '
Line 141:13: E265 block comment should start with '# '
Line 142:13: E265 block comment should start with '# '
Line 143:17: E117 over-indented (comment)
Line 143:17: E265 block comment should start with '# '
Line 144:25: E117 over-indented (comment)
Line 144:25: E265 block comment should start with '# '
Line 145:25: E117 over-indented (comment)
Line 145:25: E265 block comment should start with '# '
Line 146:25: E117 over-indented (comment)
Line 146:25: E265 block comment should start with '# '
Line 146:100: E501 line too long (110 > 99 characters)
Line 147:25: E117 over-indented (comment)
Line 147:25: E265 block comment should start with '# '
Line 148:25: E117 over-indented (comment)
Line 148:25: E265 block comment should start with '# '
Line 149:25: E117 over-indented (comment)
Line 149:25: E265 block comment should start with '# '
Line 150:25: E117 over-indented (comment)
Line 150:25: E265 block comment should start with '# '
Line 165:17: E265 block comment should start with '# '
Line 166:17: E265 block comment should start with '# '
Line 248:9: E265 block comment should start with '# '
Line 249:9: E265 block comment should start with '# '
Line 250:13: E116 unexpected indentation (comment)
Line 250:13: E265 block comment should start with '# '
Line 251:13: E116 unexpected indentation (comment)
Line 251:13: E265 block comment should start with '# '
Line 252:17: E116 unexpected indentation (comment)
Line 252:17: E265 block comment should start with '# '
Line 253:25: E116 unexpected indentation (comment)
Line 253:25: E265 block comment should start with '# '
Line 254:25: E116 unexpected indentation (comment)
Line 254:25: E265 block comment should start with '# '
Line 255:21: E116 unexpected indentation (comment)
Line 255:21: E265 block comment should start with '# '
Line 256:21: E116 unexpected indentation (comment)
Line 256:21: E265 block comment should start with '# '
Line 257:37: E116 unexpected indentation (comment)
Line 257:37: E265 block comment should start with '# '
Line 259:21: E116 unexpected indentation (comment)
Line 259:21: E265 block comment should start with '# '
Line 260:25: E116 unexpected indentation (comment)
Line 260:25: E265 block comment should start with '# '
Line 261:25: E116 unexpected indentation (comment)
Line 261:25: E265 block comment should start with '# '
Line 261:100: E501 line too long (101 > 99 characters)
Line 262:25: E116 unexpected indentation (comment)
Line 262:25: E265 block comment should start with '# '
Line 264:21: E116 unexpected indentation (comment)
Line 264:21: E265 block comment should start with '# '
Line 265:21: E116 unexpected indentation (comment)
Line 265:21: E265 block comment should start with '# '
Line 266:1: W293 blank line contains whitespace

In the file neo/io/proxyobjects.py:

Line 94:9: E265 block comment should start with '# '
Line 95:13: E116 unexpected indentation (comment)
Line 95:13: E265 block comment should start with '# '
Line 96:9: E265 block comment should start with '# '
Line 97:9: E265 block comment should start with '# '
Line 98:9: E265 block comment should start with '# '
Line 99:1: W293 blank line contains whitespace
Line 120:77: E231 missing whitespace after ','
Line 135:100: E501 line too long (112 > 99 characters)
Line 138:1: W293 blank line contains whitespace
Line 139:9: E265 block comment should start with '# '
Line 140:9: E265 block comment should start with '# '
Line 141:13: E116 unexpected indentation (comment)
Line 141:13: E265 block comment should start with '# '
Line 142:13: E116 unexpected indentation (comment)
Line 142:13: E265 block comment should start with '# '
Line 143:17: E116 unexpected indentation (comment)
Line 143:17: E265 block comment should start with '# '
Line 144:13: E116 unexpected indentation (comment)
Line 144:13: E265 block comment should start with '# '
Line 146:9: E265 block comment should start with '# '
Line 147:13: E116 unexpected indentation (comment)
Line 147:13: E265 block comment should start with '# '
Line 148:13: E116 unexpected indentation (comment)
Line 148:13: E265 block comment should start with '# '
Line 149:9: E265 block comment should start with '# '
Line 150:9: E265 block comment should start with '# '
Line 151:9: E265 block comment should start with '# '
Line 152:9: E265 block comment should start with '# '
Line 153:9: E265 block comment should start with '# '
Line 154:49: E116 unexpected indentation (comment)
Line 154:49: E265 block comment should start with '# '
Line 155:9: E265 block comment should start with '# '
Line 156:9: E265 block comment should start with '# '
Line 157:9: E265 block comment should start with '# '
Line 158:49: E116 unexpected indentation (comment)
Line 158:49: E265 block comment should start with '# '
Line 162:5: E265 block comment should start with '# '
Line 163:9: E265 block comment should start with '# '
Line 164:9: E265 block comment should start with '# '
Line 165:13: E116 unexpected indentation (comment)
Line 165:13: E265 block comment should start with '# '
Line 166:9: E265 block comment should start with '# '
Line 167:13: E116 unexpected indentation (comment)
Line 167:13: E265 block comment should start with '# '
Line 168:9: E265 block comment should start with '# '
Line 169:13: E116 unexpected indentation (comment)
Line 169:13: E265 block comment should start with '# '
Line 170:9: E265 block comment should start with '# '
Line 239:79: W291 trailing whitespace
Line 241:21: E116 unexpected indentation (comment)
Line 241:21: E265 block comment should start with '# '
Line 245:13: E265 block comment should start with '# '
Line 263:83: W291 trailing whitespace
Line 264:100: E501 line too long (101 > 99 characters)
Line 265:37: E116 unexpected indentation (comment)
Line 265:37: E265 block comment should start with '# '
Line 265:100: E501 line too long (101 > 99 characters)
Line 324:100: E501 line too long (118 > 99 characters)
Line 337:1: W293 blank line contains whitespace
Line 358:100: E501 line too long (115 > 99 characters)
Line 393:1: W293 blank line contains whitespace
Line 400:1: W293 blank line contains whitespace
Line 430:9: E303 too many blank lines (2)
Line 430:100: E501 line too long (118 > 99 characters)
Line 433:1: W293 blank line contains whitespace
Line 449:1: W293 blank line contains whitespace
Line 450:1: W293 blank line contains whitespace
Line 461:1: W293 blank line contains whitespace
Line 462:1: W293 blank line contains whitespace
Line 463:1: W293 blank line contains whitespace
Line 480:1: W293 blank line contains whitespace
Line 641:1: E265 block comment should start with '# '
Line 642:5: E265 block comment should start with '# '
Line 643:5: E265 block comment should start with '# '
Line 644:5: E265 block comment should start with '# '
Line 645:5: E265 block comment should start with '# '
Line 646:5: E265 block comment should start with '# '
Line 647:5: E265 block comment should start with '# '
Line 648:5: E265 block comment should start with '# '
Line 649:5: E265 block comment should start with '# '
Line 650:5: E265 block comment should start with '# '
Line 651:9: E116 unexpected indentation (comment)
Line 651:9: E265 block comment should start with '# '
Line 652:21: E116 unexpected indentation (comment)
Line 652:21: E265 block comment should start with '# '
Line 653:9: E116 unexpected indentation (comment)
Line 653:9: E265 block comment should start with '# '
Line 654:13: E116 unexpected indentation (comment)
Line 654:13: E265 block comment should start with '# '
Line 655:9: E116 unexpected indentation (comment)
Line 655:9: E265 block comment should start with '# '
Line 656:13: E116 unexpected indentation (comment)
Line 656:13: E265 block comment should start with '# '
Line 658:5: E265 block comment should start with '# '
Line 659:5: E265 block comment should start with '# '
Line 660:9: E116 unexpected indentation (comment)
Line 660:9: E265 block comment should start with '# '
Line 661:13: E116 unexpected indentation (comment)
Line 661:13: E265 block comment should start with '# '
Line 663:5: E265 block comment should start with '# '
Line 664:5: E265 block comment should start with '# '
Line 665:9: E116 unexpected indentation (comment)
Line 665:9: E265 block comment should start with '# '
Line 666:9: E116 unexpected indentation (comment)
Line 666:9: E265 block comment should start with '# '
Line 668:5: E265 block comment should start with '# '

In the file neo/rawio/baserawio.py:

Line 67:21: E261 at least two spaces before inline comment
Line 68:19: E261 at least two spaces before inline comment
Line 72:21: E261 at least two spaces before inline comment
Line 73:19: E261 at least two spaces before inline comment
Line 200:1: W293 blank line contains whitespace
Line 210:1: W293 blank line contains whitespace
Line 211:1: W293 blank line contains whitespace
Line 212:1: W293 blank line contains whitespace
Line 213:1: W293 blank line contains whitespace
Line 216:1: W293 blank line contains whitespace
Line 219:100: E501 line too long (117 > 99 characters)
Line 220:100: E501 line too long (161 > 99 characters)
Line 221:100: E501 line too long (121 > 99 characters)
Line 222:100: E501 line too long (156 > 99 characters)
Line 223:100: E501 line too long (118 > 99 characters)
Line 224:100: E501 line too long (161 > 99 characters)
Line 225:1: W293 blank line contains whitespace
Line 235:1: W293 blank line contains whitespace
Line 250:1: W293 blank line contains whitespace
Line 272:1: W293 blank line contains whitespace
Line 273:1: W293 blank line contains whitespace
Line 274:9: E303 too many blank lines (2)
Line 281:28: E222 multiple spaces after operator
Line 283:1: W293 blank line contains whitespace
Line 287:30: W291 trailing whitespace
Line 292:1: W293 blank line contains whitespace
Line 294:9: E303 too many blank lines (2)
Line 296:5: E265 block comment should start with '# '
Line 297:9: E265 block comment should start with '# '
Line 298:9: E265 block comment should start with '# '
Line 299:9: E265 block comment should start with '# '
Line 300:9: E265 block comment should start with '# '
Line 301:9: E265 block comment should start with '# '
Line 302:9: E265 block comment should start with '# '
Line 303:13: E116 unexpected indentation (comment)
Line 303:13: E265 block comment should start with '# '
Line 304:9: E265 block comment should start with '# '
Line 305:13: E116 unexpected indentation (comment)
Line 305:13: E265 block comment should start with '# '
Line 306:9: E265 block comment should start with '# '
Line 307:13: E116 unexpected indentation (comment)
Line 307:13: E265 block comment should start with '# '
Line 308:13: E116 unexpected indentation (comment)
Line 308:13: E265 block comment should start with '# '
Line 309:9: E265 block comment should start with '# '
Line 310:13: E116 unexpected indentation (comment)
Line 310:13: E265 block comment should start with '# '
Line 311:13: E116 unexpected indentation (comment)
Line 311:13: E265 block comment should start with '# '
Line 329:1: W293 blank line contains whitespace
Line 337:37: E201 whitespace after '{'
Line 415:1: W293 blank line contains whitespace
Line 419:1: W293 blank line contains whitespace
Line 425:100: E501 line too long (140 > 99 characters)
Line 426:1: W293 blank line contains whitespace
Line 429:5: E265 block comment should start with '# '
Line 430:9: E265 block comment should start with '# '
Line 431:9: E265 block comment should start with '# '
Line 433:9: E265 block comment should start with '# '
Line 434:9: E265 block comment should start with '# '
Line 435:9: E265 block comment should start with '# '
Line 436:9: E265 block comment should start with '# '
Line 437:9: E265 block comment should start with '# '
Line 438:9: E265 block comment should start with '# '
Line 440:9: E265 block comment should start with '# '
Line 441:13: E116 unexpected indentation (comment)
Line 441:13: E265 block comment should start with '# '
Line 442:9: E265 block comment should start with '# '
Line 443:9: E265 block comment should start with '# '
Line 444:9: E265 block comment should start with '# '
Line 445:13: E116 unexpected indentation (comment)
Line 445:13: E265 block comment should start with '# '
Line 447:5: E265 block comment should start with '# '
Line 448:9: E265 block comment should start with '# '
Line 449:9: E265 block comment should start with '# '
Line 451:9: E265 block comment should start with '# '
Line 452:9: E265 block comment should start with '# '
Line 453:9: E265 block comment should start with '# '
Line 454:13: E116 unexpected indentation (comment)
Line 454:13: E265 block comment should start with '# '
Line 455:13: E116 unexpected indentation (comment)
Line 455:13: E265 block comment should start with '# '
Line 456:13: E116 unexpected indentation (comment)
Line 456:13: E265 block comment should start with '# '
Line 457:13: E116 unexpected indentation (comment)
Line 457:13: E265 block comment should start with '# '
Line 458:17: E116 unexpected indentation (comment)
Line 458:17: E265 block comment should start with '# '
Line 459:17: E116 unexpected indentation (comment)
Line 459:17: E265 block comment should start with '# '
Line 460:13: E116 unexpected indentation (comment)
Line 460:13: E265 block comment should start with '# '
Line 461:9: E265 block comment should start with '# '
Line 462:13: E116 unexpected indentation (comment)
Line 462:13: E265 block comment should start with '# '
Line 484:5: E265 block comment should start with '# '
Line 485:9: E265 block comment should start with '# '
Line 486:9: E265 block comment should start with '# '
Line 487:9: E265 block comment should start with '# '
Line 488:9: E265 block comment should start with '# '
Line 489:9: E265 block comment should start with '# '
Line 490:13: E116 unexpected indentation (comment)
Line 490:13: E265 block comment should start with '# '
Line 492:9: E265 block comment should start with '# '
Line 493:13: E116 unexpected indentation (comment)
Line 493:13: E265 block comment should start with '# '
Line 495:9: E265 block comment should start with '# '
Line 496:1: W293 blank line contains whitespace
Line 504:1: W293 blank line contains whitespace
Line 506:9: E265 block comment should start with '# '
Line 507:13: E117 over-indented (comment)
Line 507:13: E265 block comment should start with '# '
Line 512:9: E265 block comment should start with '# '
Line 513:13: E117 over-indented (comment)
Line 513:13: E265 block comment should start with '# '
Line 518:9: E265 block comment should start with '# '
Line 519:13: E117 over-indented (comment)
Line 519:13: E265 block comment should start with '# '
Line 520:13: E117 over-indented (comment)
Line 520:13: E265 block comment should start with '# '
Line 521:9: E265 block comment should start with '# '
Line 522:13: E117 over-indented (comment)
Line 522:13: E265 block comment should start with '# '
Line 523:9: E265 block comment should start with '# '
Line 524:9: E265 block comment should start with '# '
Line 531:1: W293 blank line contains whitespace
Line 534:100: E501 line too long (111 > 99 characters)
Line 535:12: W291 trailing whitespace
Line 538:9: E265 block comment should start with '# '
Line 539:9: E265 block comment should start with '# '
Line 540:13: E116 unexpected indentation (comment)
Line 540:13: E265 block comment should start with '# '
Line 541:1: W293 blank line contains whitespace
Line 552:9: E265 block comment should start with '# '
Line 553:9: E265 block comment should start with '# '
Line 554:13: E116 unexpected indentation (comment)
Line 554:13: E265 block comment should start with '# '
Line 555:1: W293 blank line contains whitespace
Line 584:100: E501 line too long (108 > 99 characters)
Line 596:100: E501 line too long (104 > 99 characters)
Line 735:100: E501 line too long (110 > 99 characters)
Line 737:100: E501 line too long (109 > 99 characters)
Line 761:100: E501 line too long (101 > 99 characters)

In the file neo/rawio/examplerawio.py:

Line 78:100: E501 line too long (103 > 99 characters)
Line 105:1: W293 blank line contains whitespace
Line 113:1: W293 blank line contains whitespace
Line 114:1: W293 blank line contains whitespace
Line 181:1: W293 blank line contains whitespace
Line 183:1: W293 blank line contains whitespace
Line 187:9: E265 block comment should start with '# '
Line 188:1: W293 blank line contains whitespace
Line 200:17: E265 block comment should start with '# '
Line 201:21: E116 unexpected indentation (comment)
Line 201:21: E265 block comment should start with '# '
Line 202:21: E116 unexpected indentation (comment)
Line 202:21: E265 block comment should start with '# '
Line 208:100: E501 line too long (102 > 99 characters)
Line 209:1: W293 blank line contains whitespace
Line 254:100: E501 line too long (110 > 99 characters)
Line 285:1: W293 blank line contains whitespace
Line 324:100: E501 line too long (101 > 99 characters)
Line 341:100: E501 line too long (101 > 99 characters)

@apdavison @JuliaSprenger @mdenker @PeterNSteinmetz
Here a PR for proof of concept of a new rawio refactoring mainly on signals by adding the concept of streams.
This should simplify writting IOs when there are multi stream and not complixify too much when there is only one stream.
This PR also simplify and enhance annotations/array_annotations. This is a consequence of the removal of ChannelIndex.
This PR will be enormous because it will affet all rawio.
If you when to have a look the sooner the simpler : now only examplrawio/exampleio is done.
@jpgill86 @PeterNSteinmetz : I will maybe need your help at some point to port IOs you ar involded in.
@alejoe91 @mhhennig @colehurwitz
This PR will also help a lot to enhance the bridge between neo and spikeinterface.

Thank you Julia for this.
I will try to clean soon.
I am still figthing with the nixrawio....

Hi @samuelgarcia,
I've only just begun looking at this and haven't yet wrapped my head around what this PR is about, but I did quickly check to see if these changes are compatible with ephyviewer's AnalogSignalFromNeoRawIOSource and encountered some minor problems. I started a draft PR for ephyviewer here that fixes the issues I've found so far: NeuralEnsemble/ephyviewer#150.
The API changes proposed here will be backwards-incompatible with ephyviewer. Is that intended? I'm still trying to figure out what a "stream" is.

Hi Jeffrey,
you are faster that me.
I also wanted to propagate that change to ephyviewer.
This PR clarify the "group" in channel map. And call it "signal stream".
So device with several sampling rate or explicit group are split in "signal streams"
It make simpler to handle channel index inner stream.

OK, thanks!

@JuliaSprenger
For me, this is finish.
Test are passing now.
pep8 is ok (or almost)
Do you think we can merge this soon ?

pep8 stuff are not refresh for some reason but they are fixed in the code.

About slice speeds I will make test.

Hi Julia.
Thank you for this new review.
About slice and speed test.
You are right. The older version is faster and strangly calling to method is super super slow (I thought the contrary)
I will go back.
import timeit

mysetup = """
import numpy as np
a = np.random.rand(1000,300)

mask = np.zeros(300, dtype='bool')
mask[100:] = True
indices, = np.nonzero(mask)
"""

number = 100000

print(timeit.timeit(setup = mysetup,
                     stmt = 'a[10:200, :][:, indices]',
                     number = number
                    ))

print(timeit.timeit(setup = mysetup,
                     stmt = 'a[10:200, indices]',
                     number = number
                    ))

print(timeit.timeit(setup = mysetup,
                     stmt = 'a[10:200, :][:, mask]',
                     number = number
                    ))

print(timeit.timeit(setup = mysetup,
                     stmt = 'a[10:200, mask]',
                     number = number
                    ))

print(timeit.timeit(setup = mysetup,
                     stmt = 'a[10:200].take(indices, axis=1)',
                     number = number
                    ))

print(timeit.timeit(setup = mysetup,
                     stmt = 'a[10:200].compress(mask, axis=1)',
                     number = number
                    ))

print(timeit.timeit(setup = mysetup,
                     stmt = 'np.compress(mask, a[10:200], axis=1)',
                     number = number
                    ))

Give me:
2.828962470000988
2.7259579469991877
2.8593898180006363
2.855899320999015
14.526134342999285
14.504813733999981
14.647908297998583


Updates to type reference directive resolution and module resolution when failed

When user has supplied typeRoots resolve the typeReference as file or directory instead of just directory resolution as before.
1c2318d92e2e93c99b8ed87419470ddfd7719796 This is fix for issue Bug 2 reported in #37708
If configuration has supplied typeRoots stop looking into node_modules/@types containing file's ancestor directories to resolve type reference as secondary lookup.
40bb75c8f5273d5cd379c97cb683f08a04947b58 This is fix for issue Bug 1 reported in #37708
When resolving modules, if resolution fails, try resolving it from typeRoots if user has supplied. This helps solve the issues with module augmentation etc if when types are included through typeRoots.
a6fed14f5bb2279bac45f348f49ee984baa3512d This is fix for #39691 and #37958

Fixes #37708, #39691, #37958, #44270

@typescript-bot run dt
@typescript-bot test top100

@sheetalkamat  I'm going through all the ready-to-merge PRs, and this one was intended either for 5.0 or 5.1, so I vote to merge it now that 5.1 development has started.

I still confuse with the usage of "typeRoots" under Typescript 5.1-beta.
Here is my simple example.
My project structure:
typescript1
 ┣ @types
 ┃ ┗ mypackage
 ┃   ┗ index.d.ts
 ┣ node_modules
 ┣ src
 ┃ ┗ 5-1-main.ts
 ┣ package.json
 ┗ tsconfig.json

my package.json:
{
  "name": "typescript1",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "tsc": "tsc ./src/5-1-main.ts",
    "tsct": "tsc ./src/5-1-main.ts --traceResolution",
    "tscv": "tsc -v"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {},
  "dependencies": {
    "typescript": "beta"
  }
}

my tsconfig.json:
{
  "compilerOptions": {
    "target": "es2016",
    "module": "esnext",
    "typeRoots": ["./@types"]
  },
}

my custom type defined file:
//<EMAIL_ADDRESS>interface MyObject {
    name: string;
}

my source code:
// ./src/5-1-main.ts
var a: MyObject = {
    name: '12',
}

Before I run the script npm run tsc, I run tscv to ensure my typescript version is 5.1-beta.

Then I run script npm run tsc.I got  the error:
src/5-1-main.ts:1:8 - error TS2552: Cannot find name 'MyObject'. Did you mean 'Object'?

1 var a: MyObject = {
         ~~~~~~~~

  node_modules/_typescript@5.1.0-beta@typescript/lib/lib.es5.d.ts:270:13
    270 declare var Object: ObjectConstructor;
                    ~~~~~~
    'Object' is declared here.

Found 1 error in src/5-1-main.ts:1

I specified the typeRoots in tsconfig.json, but MyObject defined in file<EMAIL_ADDRESS>not worked.
Then I added the file @types/mypackage2/index.d.ts into the dir ./node_modules.
typescript1
 ┣ @types
 ┃ ┗ mypackage
 ┃   ┗ index.d.ts
 ┣ node_modules
 ┃ ┗ @types
 ┃      ┗ mypackage2
 ┃          ┗ index.d.ts
 ┣ src
 ┃ ┗ 5-1-main.ts
 ┣ package.json
 ┗ tsconfig.json

And I run the script npm run tsct ( tsc command with --traceResolution), typescript could compile success.According to the log, MyObject defined in file<EMAIL_ADDRESS>was involed into the compilation.
That was so weird！！
><EMAIL_ADDRESS>tsct /Users/sisiea/Documents/playground/typescript1
> tsc ./src/5-1-main.ts --traceResolution

======== Resolving type reference directive 'mypackage2', containing file '/Users/sisiea/Documents/playground/typescript1/__inferred type names__.ts', root directory '/Users/sisiea/Documents/playground/typescript1/node_modules/@types,/Users/sisiea/Documents/playground/node_modules/@types,/Users/sisiea/Documents/node_modules/@types,/Users/sisiea/node_modules/@types,/Users/node_modules/@types,/node_modules/@types'. ========
Resolving with primary search path '/Users/sisiea/Documents/playground/typescript1/node_modules/@types, /Users/sisiea/Documents/playground/node_modules/@types, /Users/sisiea/Documents/node_modules/@types, /Users/sisiea/node_modules/@types, /Users/node_modules/@types, /node_modules/@types'.
File<EMAIL_ADDRESS>does not exist.
File<EMAIL_ADDRESS>exists - use it as a name resolution result.
Resolving real path for<EMAIL_ADDRESS>result<EMAIL_ADDRESS>======== Type reference directive 'mypackage2' was successfully resolved to<EMAIL_ADDRESS>primary: true. ========

Yes, it's mentioned in the Announcing TypeScript 5.1 blog post.

@loick can you log a fresh issue please? Thanks!

ok


ModuleNotFoundError: No module named 'bs4'

          thank you for your response. I installed beautifulsoup4 as per you instructions but it said "Requirement already satisfied" and when I ran the script again, it gave the same error message:

Originally posted by @quopquai in https://github.com/nedlir/languagepod101-scraper/issues/23#issuecomment-1455250304

So, I figured out i need to put the "language101_scraper.py" file in the "site-packages" folder and the script started to work properly! - but then i got another error message saying,
"Couldn't find a tree builder with the features you requested: lxml. Do you need to install a parser library?
Failed to parse the course's webpage, 'lxml' package might be missing."
Any help would be appreciated, thanks.
Do i need to subscribe to the course for this to work?

I moved the py script to the 3.10/site-packages instead of the 3.9/site-packages and it finally worked!
Although, it says, "Yatta! Finished downloading the course~", nothing has actually downloaded!?!?
What am i still missing?

Have you tried this solution?
https://stackoverflow.com/questions/37341614/modules-are-installed-using-pip-on-osx-but-not-found-when-importing
This seems like a problem with the system recognizing python installed libraries and not with the script.


Add methods for filling a buffer from an IO greedily/lazily

Feature Request
IO#read currently makes very few assumptions about the amount of data that must be read (only that 0 bytes returned = EOF).
This can be cumbersome when writing methods which process IO data.
Because of this, lots of code currently makes the assumption that IO#read fills the entire buffer if enough data is available (ex. #14604).
The only methods which currently allow reading greedily (#read_fully, #read_fully?) do not return the amount of bytes read if the buffer was not filled entirely, causing the remaining bytes to be lost if the IO does not implement #pos.
Therefore, I think it would be useful to add a separate method with this behaviour:
# Similar to `#read`, but with the additional guarantee that either
# the buffer will be entirely filled or the EOF will be reached while trying.
#
# Calling this method may result in multiple read calls if necessary.
def read_greedy(slice : Bytes) : Int32
  count = slice.size
  while slice.size > 0
    read_bytes = read(slice)
    return count &- slice.size if read_bytes == 0
    slice += read_bytes
  end
  count
end

Adding this as a separate method allows many IOs which already have this behavior implicitly (ex. IO::Memory) to implement it more efficiently while ensuring correctness for IOs which do not have this behavior.

Additionally, as an opposite counterpart, it may be useful to add a method (IO#read_lazy ?) for reading from an IO lazily (ex. non-blocking read from STDIN which simply returns 0 if there was no user input without concurrency).

I've been thinking about this as well since I recommended using IO.copy for this use case yesterday in https://github.com/crystal-lang/crystal/issues/14601#issuecomment-2122100178.
So IO.copy can basically do this and even more because it reads into an IO. But of course this is not as convenient if you want to read directly into a slice.
So it might be a good idea to add a method for this.

I second that. I'm not sure about the names, but having a couple methods to "try to read (nonblock)" and "try to fill (blocking, until EOF)" sounds good. Maybe:

IO#fill(buffer : Bytes) : Int32 fills the buffer until EOF is reached; returns the number of bytes read (usually the buffer size, but may be less when EOF is reached). Raises after EOF has been reached.
IO#fill?(buffer : Bytes) : Int32? same as #fill but returns nil instead of raising after EOF.

I'm also wondering about the following, but it's mixing two concepts (nonblock + eof) behind the ? suffix (not good):

IO#read?(buffer : Bytes) : Int32? same as #read but doesn't block until data is ready, and immediately returns 0 when nothing was read; returns nil on EOF.

@ysbaddaden These methods are all related to IO#read and IMO their names should be similar. #read_greedy may not be a great name, but at least it establishes that it's a variant of #read. Maybe we can find something better with #read_ prefix though?
Also it would be very helpful for consitency to keep the same general semantics as #read: indicate EOF with a zero return value and only raise if the IO is closed.
The proposed behaviour of #read? can be implemented via #peek and #skip. That's even more efficient because it doesn't not need to copy data into the buffer.

@straight-shoota I got confused, I thought we raised on eventual EOF.


server connection error

When I used micro web query ,sometimes mistakes happen
{
  "id": "go.micro.client",
  "code": 500,
  "detail": "connection error: dial tcp *******:30374: connectex: No connection could be made because the target machine actively refused it.",
  "status": "Internal Server Error"
}

It just sometimes , not always

This could happen for any number of reasons. If you have stale entries in the registry or if there's a server side error. The reference to "connectx" is outside the scope of micro and likely deployment related so I'm tempted to say this is related to the networking config of your containers.

2 weeks no response, closing


move functionality

Hello,
When pre-filled sqlite db size is too big, after it was copied. The application has two databases file. So this has problem with the application size. Could you can add a new move functionality (copy and remove source file).
For ex: Before sqlite installed app size : 25MB, pre-filled sqlite db size : 20MB.
When the application installed the app size reached the 65MB. (app size + source sqlite + copeid sqlite).
Thanks in advance.

+1

Will start working on it in two weeks.

+1

App directory is a read only directory, so we cannot move or delete any content from it. If you have any other suggestion, then please let me know.


Add new endpoint reference page for the validators module

Closes #1727

@ishantiw Many thanks, as requested I have updated, the heading to 'validateBLSKey'.
Just wanted to check that for the 'getValidator', should this remain as 'validators_getValidator' in line 87?


Slf4j Odin backend

Hi there. We are greatly enjoying Odin and will most likely switch to it from log4cats. However, if we are going to use Odin, we would want the ability in our published libraries to have an slf4j backend version so that consumers of those libraries will have a no hassle implicit logger available. I was curious if the maintainers would accept a PR that offers an Odin logger with an slf4j backend, similar to log4cats's Slf4jLogger.

I went ahead and made a PR that would add this functionality. Looking forward to any feedback. Thanks!


Remove reference to yotta for Mbed OS

Type: Bug
Priority: Major

Bug
Documentation
Documentation states that yotta is required for Mbed OS
https://github.com/ARMmbed/mbedtls/blob/master/README.md
Doc linked from:

https://github.com/ARMmbed/mbed-os/blob/master/features/mbedtls/README.md
https://os-doc-builder.test.mbed.com/docs/latest/reference/mbed-tls-entropy.html
https://os-doc-builder.test.mbed.com/docs/latest/reference/hardware-accelerated-crypto.html

This is not true and should be removed
@iriark01 @AnotherButler

@sbutcher-arm Could you comment on this please? Are the references there for older build support for TLS or can they just be removed for mbed-os docs?

We have an open PR to remove yotta support and references to yotta. That work is ongoing and is being resolved by PR #1609.
I don't think it's fair to say that the documentation 'states that yotta is required for Mbed OS'. It actually says Yotta is a supported build system and is used by Mbed OS 16.03, which was the old version numbering scheme for Mbed OS. I will agree it is misleading, and we're working to remove it.
This can't happen any earlier than Mbed OS 5.10 though, as to change the documentation in Mbed OS we need to release a new version of Mbed TLS into Mbed OS.

ARM Internal Ref: IOTSSL-2344

PR #1609 has been merged, so closing this


[Readme] composer require rector/rector - step removed

If we first run the composer require rector/rector --dev we may end up with a rector conflict in sylius/sylius-rector. Since sylius/sylius-rector depends on the rector/rector we only need to run one command and keep rector's upgrades in one place
Picrel:

Only sylius/sylius-rector required:

Thank you, Rafał! :tada:


[OP-35] Convert hex enode IP

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: macfarla:x: mark-terryYou have signed the CLA already but the status is still pending? Let us recheck it.


[BUG] K8s version - various issues ?

I might be doing something wrong, but I don't think so?
Seems like a backend issue ?

If I change that to 2 CPUs, then this doesn't fail but version format fails or something:

cc @shwstppr can you please test drive the K8s plugin in primate - I'm not sure if I'm doing something wrong, at least based on the official docs it should be fine.

the version needs to be specified as 1.15.0 (or x.y.z in general?) then it works fine (and with 2 CPU)
Should we have a popup (the "i" letter) that says "specify the version in format x.y.z" ? @shwstppr cc @davidjumani

@andrijapanicsb looks like 2CPU is a requirement and the version needs to be 1.15.0 as there is no k8s 1.15 release but 1.15.0 or 1.15.1 release. Have you followed the docs http://docs.cloudstack.apache.org/en/latest/plugins/cloudstack-kubernetes-service.html ?

I've added some improvements here, https://github.com/apache/cloudstack/pull/4269, error messages and API param description. I've not explicitly tied 2vCPU, 2GB memory requirement in UI as it might change once we move to a different template (from CoreOS)

Do we need to make any change in Primate @shwstppr cc @andrijapanicsb @davidjumani ?

@rhtyd I don't think any changes will be needed in Primate. Though, maybe we can verify backend changes with Primate which should show better error messages and parameter information now

Closing on your remark @shwstppr


Add a good example how to setup the layout app so you can overwrite it

Move automatically creates the app layout, but this is laborious. Almost always the user would like to overwrite this view. For now you can publish package views and overwrite the app layout, but this is not ideal. Beter would be a stub that creates an example app layout that you can implement and overwrite.

This has become obsolete because move:install now adds overwrites the default Jetstream layouts/app.blade.php file with the move app.blade.php stub.


Bump Dependencies #9288492546

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/9288492546

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


VS2019 / C++ 17, signal::disconnect compile error: syntax error: 'template'

Using custom functor, Signals fail to compile with:
signal_template.hpp(537,50): error C2059: syntax error: 'template'
Here:
              // check for wrapped extended slot
              bound_extended_slot_function_type *fp;
              fp = (*it)->slot().slot_function().template target<bound_extended_slot_function_type>();

The reason behind is that the signal expects the functor to be the boost::function / std::function, that would contain the target() method.
Minimal example:
struct MyFunctorThisComparer
{
	MyFunctorThisComparer(const void* this_) {}
	bool operator==(const MyFunctorThisComparer& other) const { return true; }
};

struct MyFunctor
{
	typedef void result_type;

	template<typename F>
	void operator=(F) {}
	void operator()() {}

	// disconnect by comparison with custom predicate
	bool operator==(const MyFunctorThisComparer& other) const { return true; }
	operator MyFunctorThisComparer() const { return MyFunctorThisComparer { nullptr }; }
};

void signals_disconnect()
{
	boost::signals2::signal<
		void(),
		//SignalSupport_::AllCall<typename boost::function_traits<void()>::result_type>,
		boost::signals2::optional_last_value<typename boost::function_traits<void()>::result_type>,
		int,
		std::less<int>,
		MyFunctor > s;

	s.connect( &signals_disconnect );
	s.disconnect( MyFunctorThisComparer(nullptr) );
}

I attempted here to provide the equivalence MyFunctorThisComparer predicate, that would filter out functors. In particular, it would know how to extract 'this' pointer from MyFunctor. However, it could be a more generic predicate.
Boost 1.72.0. However, I have checked the development version - it has the same lines there, so the issue is still present.

I've never given much thought to allowing for the SlotFunction to be anything other than boost::function or std::function, although I do remember considering dropping the SlotFunction template parameter entirely.  Recent changes to support c++20 means operator== won't even be used in the future (it uses the "contains" method instead).  I guess it might be possible to get rid of the "target" call and just rely on "contains".


Files with .MD (uppercase) extension are not recognized as markdown files

Hi,
I have an issue when I use my markdown folder as the 'database' dir. The files with .MD extension are not recognized as markdown files. As a result, these files do not show up in the frontend. To show them, I have to change all the files with .MD extension to .md.
I expect that both .MD and .md files should be treated as markdown files and show up in the frontend.
Thank you.

Hi. Thank you for raising this. Unfortunately though, this is by design.
For simplicity I chose to simply assume an extension of lowercase .md. If this could vary from note to note then I'd need to keep track of of it all the way through to the front end. This seemed like a lot of work for something that could be solved by sticking to a consistent extension.
Note: On Linux, my note.md and my note.MD are two different files.
I'll add this to the docs in case it catches anyone else out.

README has now been updated to include info about file extensions.

README has now been updated to include info about file extensions.

I can't locate this but there is a wiki FAQ entry https://github.com/dullage/flatnotes/wiki#what-file-extensions-are-supported


issue-issue

Analyzer Feedback from IntelliJ
Version information

IDEA AI-191.8<IP_ADDRESS>91312
2.4.0
AI-191.8<IP_ADDRESS>91312, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1366x768

Exception
Dart analysis server, SDK version 2.4.0, server version , FATAL error: NoSuchMethodError: The getter 'path' was called on null.
Receiver: null
Tried calling: path
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:50:5)
#1      Driver._getSdkPath (package:analysis_server/src/server/driver.dart:760:9)
#2      Driver.start (package:analysis_server/src/server/driver.dart:394:28)
#3      main (file:///C:/b/s/w/ir/k/src/third_party/dart/pkg/analysis_server/bin/server.dart:12:11)
<asynchronous suspension>
#4      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

For additional log information, please append the contents of
file://C:\Users\skha436\AppData\Local\Temp\report.txt.

Thanks for reporting this issue! This was previously reported in https://github.com/dart-lang/sdk/issues/35226; please follow along there.

Duplicate of https://github.com/dart-lang/sdk/issues/35226


json files end up with ".csv.json" in url

After DataSet is published, if you try to download any file in json format you'll get something like this: https://pkgstore-testing.datahub.io/0e9b59cd50f1884058c1aa242d71a228/finance-vix/latest/.datahub/json/data/vix-daily.csv.json
Plus if you try and open the file it is still CSV.
This also impacts resource paths in datapackage.json and crashes graphs and tables
...
resources: [{
   name: ...
   path: ".datahub/json/data/vix-daily.csv.json"
}]

This was fixed by creating separate resource names for the original and json resources.

@akariv link still ends with .csv.json. I guess that is expected behaviour as it's valid json for now, correct?
https://pkgstore-testing.datahub.io/0e9b59cd50f1884058c1aa242d71a228/co2-ppm/latest/.datahub/json/data/co2-mm-mlo.csv.json

Yes, we keep the original extension on purpose.
On Fri, Jul 28, 2017, 08:27 Irakli Mchedlishvili<EMAIL_ADDRESS>wrote:

@akariv https://github.com/akariv link still ends with .csv.json. I
guess that is expected behaviour as it's valid json for now, correct?
https://pkgstore-testing.datahub.io/0e9b59cd50f1884058c1aa242d71a228/co2-ppm/latest/.datahub/json/data/co2-mm-mlo.csv.json
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/datahq/assembler/issues/3#issuecomment-318563425, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQMdU47IgSRTSY7vVDE5aeyPfKahGmqks5sSXExgaJpZM4Ojg1W
.


ENH: Modified to be single dynamic library

This allows the environment to define numerous aspects of running under MKL.
Please see this link https://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/
Change-Id: Ic6b27d59f66ca802f4067326551d60a2d13405e9

Thanks for the patch. Could you explain what set of parameter you selected on the intel website to obtain the parameters that you updated?


Want to make Forms Working with backend

Want to make forms fully working @KaizenGirl1111  Please allow me to make changes

Okay 👍 @Abh1shekSingh


Fix for when parameters is a child of route and not of route[method]

For an exemple of a valid OpenApi spec file that cause the bug, please see: https://raw.githubusercontent.com/APIs-guru/openapi-directory/master/APIs/twitter.com/1.1/swagger.yaml
Parameters field is a child of Path and not of Path.Method

Hi! The link that you provided as an example is not valid and not official Open API reference. Could you please fix it?

Hi !
I dont understand your request !?
Let's forget about the "official" or not, the point is: it's a valid schema !

Proof of validity: Please test the schema against this online validator. The validator use the official librabries to do its work.

Cheers.

All that I want is a pointer to the specification https://swagger.io/docs/specification/describing-parameters/ saying that it's a valid case, but now I see that it's so


Unit Conversion

Brief Description
I would like to propose a set of engineering methods that would convert units (e.g., Fahrenheit to Celsius, or Pascals to mmHg, etc.) as well as prefixes (e.g., milligrams to kilograms, kWh to MWh, etc.).
This could go down a big rabbit hole.  But maybe we could rely on Pint, or a similar package.
Example API
# Convert a column of temperatures in Celsius to Fahrenheit
df.convert_units(column_name='temperature_c',
                 existing_units='C',
                 to_units='F',
                 create_new_column=False)

I don’t know how they compare, but it might be worth evaluating unyt as well.

This is a great idea! I will suggest the following API change, though, to match it more closely to the transform_column API:
# Convert a column of temperatures in Celsius to Fahrenheit
df.convert_units(
    column_name='temperature_c',
    existing_units='C',
    to_units='F',
    dest_column_name=None)

Suggesting this change only because it semantically is of the same idea as transform_column, so it's nice to keep these semantically-similar functions together.

After looking at pint and unyt, unyt appears to potentially be a better choice.  It definitely has more recent development, but its use will require sympy (as well as unyt itself, of course).
I would like to work on incorporating this convert_units() method.

Awesome stuff, thanks @rahosbach! Looking forward to your PRs :smile:. I'll mark this as "being hacked on".


I124 save parameters

Created variable model and tested

I added the variable model to the serializers, but I never worked with them so it would be useful if you could have a look Martin


Upgrade requests and certifi to the latest version

Right now we can't upgrade requests and certifi to the latest version because one of the recent versions of certifi break requests to SSL endpoints on RHEL 6 and RHEL 7 - they fail with cert validation error.
requests.exceptions.SSLError: ("bad handshake: Error([('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')],)",)

The reason for that is that a recent version of certifi removed 1024 bit root certificates (https://pypi.python.org/pypi/certifi) and those RHEL distros run older version of OpenSSL so validation fails (https://github.com/certifi/python-certifi/issues/32).
It works in existing versions of StackStorm because no certifi is installed by default as it's not yet a requests dependency and as such, old and obsolete system CA bundle is used.
The same issue would happen if user installed / upgraded certifi manually (which is a good practice anyway). This also means the whole thing is a ticking time bomb.
That's obviously problematic. It should be in the best user interest (for safety reasons of course) to always run latest version of certifi and OpenSSL.
There are a couple of possible solutions to that:

Update installer scripts and docs to install latest version of OpenSSL (>= 1.0.2) on RHEL.
Update our code to add certifi.old_where() to requests SSL CA cert search path. This location still contains old 1024 bit root certificates.

The second proposed solution is really a work-around and not something I would suggest for production - it should always be in the best interest of user to run latest version of OpenSSL and use latest up to date CA cert bundle.
It's also a bit problematic because requests is used in many different places and it's hard to ensure environment is set up correctly everywhere (also packs).
The "problem" with first approach is that users might encounter issues in case they try to manually install StackStorm on RHEL and they don't follow / see docs and don't update OpenSSL.
Comments? Other suggested approaches?

Just for reference:

Big RedHat thread about OpenSSL 1.0.2: https://bugzilla.redhat.com/show_bug.cgi?id=1276310
Bigger thread in python-certifi about the issue: https://github.com/certifi/python-certifi/issues/26

I'm :+1: for https://github.com/StackStorm/st2/pull/3604 revert for now as last worked solution.
Talking about the instructions for installing newer OpenSSL, - it's probably not realistic for now before RHEL officially adds a corresponding package. We don't have openssl-1.0.2 package in any RPM repo yet, building the package ourselves or asking users to install OpenSSL from sources is not an option too.
I'm afraid we're most probably stuck in limbo for a long time here, waiting for a proper solution from the upstreams.

Not an issue anymore, this seems to be fixed in upstream.


[Task] Create an API to update products table of Mock Database

We'd like the users to be able to learn to use API in the tutorial. For that, we'd like to create an API
Method: POST
API: https://mock-api.appsmith.com/products/:id/update
Auth: No auth
Params:  JSON with keys as column names
Response: JSON of updated product

Sample Input:
POST https://mock-api.appsmith.com/products/4/update
{ "mrp" : 20.50 }
Sample Output:
HTTP 200 OK
{    "entity":"product",    "productId":4,    "mrp":20.50,    "listingPrice":37,    "imageUrl":"http://res.cloudinary.com/drako999/image/upload/v1584095928/sl3ugfmotprtle3l3lk8.svg",    "description":"tastyZ",    "category":"DAIRY",    "isListed":true,    "availabilityDate":"2020-03-13",    "channel":"WARE_HOUSE" }

@mohanarpit can you please help us here. We're blocked on this to close the tutorials

This has been done. You can now update products via the API:
URL
PUT https://mock-api.appsmith.com/products/{productId}
Body
{
    "productName": "Bamboo Shoots",
    "mrp": 16.99,
    "listingPrice": 28.99,
    "imageUrl": "https://robohash.org/consequaturvoluptatererum.jpg?size=50x50&set=set1",
    "description": null,
    "category": "BEVERAGES",
    "isListed": false,
    "availabilityDate": "2019-04-02",
    "channel": "WARE_HOUSE",
    "createdAt": null,
    "updatedAt": "2020-12-04T08:00:12.408Z"
}

Also, as part of this change, the field productId has been removed from the products table. This can now be referenced via the id field itself. In the tutorials, please modify all references of products.productId to products.id


Use autorest preview version [DO NOT MERGE]

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

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

Testing Guidelines

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

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Looks like --preview did not have much of any affect in the generated code. Closing this since the original PR is merged now.


milestone issue all / open / close

milestone issue all / open / close

sysout 들어간것만 지워주세요~ Merge 받을게요


RC2: Controllers that have RequireHttpsAttribute won't load on Azure

With RC2 any controller that I have decorated with RequireHttpsAttribute won't load on Azure. It is just a flood of 302s and eventually times out.
Interestingly, I can access the site with HTTPS, but any controller that has that no longer works.

@sebastienros and I are investigating.

We are about to test on Azure App Services, are you using another setup?

Nope, just Azure App Services. Just like you'd create a new web app in VS Azure tools.

We were informed that this is a known issue which was mentioned in the Release notes. You can look at the section HTTPS requests appear as HTTP in Azure Web Sites in the following release notes for a workaround.
https://github.com/aspnet/Home/releases/tag/1.0.0-rc2-final

Ahhh.. gotcha! Thank you.

Yeah this is a dup of https://github.com/aspnet/IISIntegration/issues/140.


💡 [REQUEST] -

Start Date
No response
Implementation PR
No response
Reference Issues
No response
Summary
Need to implement the method to add the items from the detailed item scene to the current list being created/edited.
Basic Example
Clicking the add to list button on the orange item will have the product name of the item appear in the list on the NewListScene.
Drawbacks
No response
Unresolved questions
No response

Issue was not closed, so will test if this functionality was added properly.


Implement public ObjectExt::set_property() and ::get_property()

This is useful for using properties (or properties of types) that are
not part of any bindings in a still safe way.

For some background, I need this for the GStreamer bindings but could also add it to gst::Object instead. In GStreamer, plugins are providing new GObject subclasses that don't exist in any (public) headers and thus don't have any GObject-Introspection data around them (and can't easily be part of any bindings as such).
The API to be used on such types is the standard GObject API: setting/getting properties, connecting to signals, etc.
If this is accepted here, I'll also submit further pull requests that allow connecting (safely!) to arbitrary signals (via @antoyo's GClosure work) or emitting them. These will also be based on GValues.

Wo, great, thanks!

Thanks, @sdroege.
I agree that these functions is actually safe, but as warning maybe better mark unsafe?

The functions are not unsafe though, they are as safe as putting things in a HashMap<String, Value>, and for example safer than current generated property setters for i32 properties that have a limited range (setting a value outside the range will give a warning but it's still set).
In addition to this I'd also like to add ObjectExt::has_property(property_name: &str, type_: Option<Type>) -> bool later, if we agree that this is acceptable as-is.

Ok, then 👍 from me.
Thanks again.

Thanks, preparing the other pieces later :)


Tooltipster in Webpack

Hello and thanks in advance for your time sir. I'm stuck, I can't for the life of me figure out how to get tooltipster to work with webpack. Basically I just keep getting tooltipster is not a function. I'm not having any issues with any other jquery plugins and I'm trying to figure out why it is not defined. Any webpack examples with tooltipster out there would be awesome. Thanks!!

Same problem here, did somebody found a solution?

Did you require tooltipster and its CSS in the file where you reference it? Like this:
require("tooltipster");
require("tooltipster/dist/css/tooltipster.bundle.min.css");
// if you want custom themes
require("tooltipster/dist/css/plugins/tooltipster/sideTip/themes/tooltipster-sideTip-light.min.css");
require("tooltipster/dist/css/plugins/tooltipster/sideTip/themes/tooltipster-sideTip-shadow.min.css");

I believe the CSS needs to be loaded separately because of this bug with webpack.


clicking edit button on the profile

After clicking edit button on the profile, if we don't click on save button and we just jump up to another student, fields remains editable true. But it should be editible false.

solved()


Using as_text() on a physical key InputEvent returns an empty string silently

Godot version
3.4.4
System information
Linux, Debian 11
Issue description
As of now, when you call the as_text method in a physical key InputEvent, it simply returns an empty string. I would expect it to return either an error telling the user that the method does not function with physical keys, or for it to return the key in that physical position.
All in all, I realize this is a very small issue, and you can currently fix it by simply using keys instead of physical keys, but I think it should do something other than silently return nothing. It should be more obvious something is wrong.
Steps to reproduce

Make a new Godot project
Add an action in the Input Map, in my case I called it test_input
Assign a physical key to that action, in my case I chose A
Create a Control Node
Add a script to the Control Node

extends Control

func _ready():
	var event: InputEvent = InputMap.get_action_list("test_input")[0]
	var faulty_as_text: String = event.as_text()
	print(faulty_as_text)

Save and run the scene

It will not print anything, and if you add a breakpoint, you will see that although there is an InputEvent Object in event, but faulty_as_text remains empty. It will do this silently.
Minimal reproduction project
InputEventBug.zip
This project simply follows the above instructions. Simply run it and behold.

As far as I see problematic piece of code is this:
// core/os/input_event.cpp
String InputEventKey::as_text() const {
	String kc = keycode_get_string(scancode);
	if (kc == String()) {
		return kc;
	}

Events registered with physical keys don't have scancode member assigned from InputMap, so, keycode_get_string just returns nullptr
I don't know precisely how distinction is made internally, but something like this does seem to work:
uint32_t code = physical_scancode ? physical_scancode : scancode;
String kc = keycode_get_string(code);

The issue is no longer present on 4a11 :

The commit that modified InputEventKey::as_text is dfe4c5f8e13, so maybe we could just backport this commit to 3.x?

Fixed by #62633.


TSConfig Italian Translation: some files

Files:

importHelpers.md
incremental.md
isolatedModules.md

Ah well, it will on the nextt PRs

Ah well, it will on the nextt PRs


Load PDF from URL

Can i load/open my pdf from local directory?

When creating a document, you either get the data of the PDF file, or you get an instance of URL you can use to load using the Swift FileManager


More develop_aircraft plots: 1) Scatter plot (matplotlib) or scatter density kde with fill (seaborn) plot capability added for develop_aircraft

New capability for plotting scatter plot (using matplotlib) or scatter density kde fill (using seaborn): both can be generated interchangeably using fill = True (for kde)  in YAML , and fill =False for matplotlib scatter plot. Both can use the same colorbar style (either default matplotlib/seaborn colormaps or User-defined color_map attributes added in plot_grp3 YAML control options).
Example:

with fill =True, kde plot generated is as follows:

with fill = False, scatter plot generated is as follows:

See new commit for violin plot capability added to develop_aircraft. Example below (with comparison to corresponding box plot):

see results of latest commit which resolved the Multiple Model(s) versus Observation plotting issue for both scatter density and violin plots (also added the YAML example for it):
    For scatter plot, some edits are needed to improve their formatting, to finalize them yet, such as, need to resolve this comment still, but it generates the scatter plot for obs versus model1:

and also obs versus model2:


InsecureRequestWarning: Unverified HTTPS request

Running shows the following warning:
InsecureRequestWarning: Unverified HTTPS request is being made to host 'xxx'.
Adding certificate verification is strongly advised.
See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings

I had a look into it and the problem, at least for me, seems harder than expected. Apparently, it's an error with the urllib3 package.
In their documentation if you go to the Certificate Verification section, they have it detailed, but honestly, I don't understand how to implement it. https://urllib3.readthedocs.io/en/2.0.0a2/user-guide.html

We don't use urllib3 directly. This is used by requests.
Like this page say, it's because we have a verify=False somewhere: https://codeigo.com/python/disable-insecurerequestwarning
And if we search for verify, we see it twice:

https://github.com/Mulugruntz/Report-Tool/blob/bd42212d0603767c005b87003c1956217d848311/report_tool/communications/ig_lightstreamer.py#L462
https://github.com/Mulugruntz/Report-Tool/blob/bd42212d0603767c005b87003c1956217d848311/report_tool/communications/ig_lightstreamer.py#L524-L530

So, these are the 2 places where this comes from.
Don't waste too much energy on it though, as the end-goal is to actually replace requests by httpx, which is much more powerful, it has HTTP/2 support, and also async support :-).
I haven't created the ticket yet. It should not be too complicated, as both APIs are very similar. But depending on some edge cases, it could become quite tricky!
But, the HTTPS issue is still something that we might want to fix, either before or after migrating to httpx.


update wgsl grammar

Fix #39

It works but colors changed. Need help.

main difference: stride, offset, handle removed.


tx context

Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

20000!!!

and it's mine!!!


P.S.A. Pipelines Paused

We've encountered a couple of throughput limits. We hit the GitHub rate limits as well as some issues with Azure DevOps pipelines.
The pipelines are paused as we manually throttle them to get PRs validated. We're working on better mechanisms to handle the high-capacity periods.

Any updates? My PR is failing Installer Validation with what it says is a Binary Validation Error, even though the manifest installs fine locally and there is no virus scanner warning on my fully up-to-date PC using Windows Defender. I'm suspecting pipeline failure rather than a problem with the package...

@Jaifroid I think, most of us experience this behavior right now. Let's give @denelon and his team some time to fix the pipeline issues.

OK, thanks @numeredev. Will do.

Quick update: We implemented code to deal with the underlying infrastructure problems. We were validating our code and GitHub was having issues at the same time with their APIs. They seem to have subsided so we're moving ahead quickly to get this rolled out. We will manually trigger any builds that failed during this time once the services are back up and running at full capacity. We have been manually throttling the services to keep PRs flowing, and we will ensure none of the open PRs get missed.

Quick update: We implemented code to deal with the underlying infrastructure problems. We were validating our code and GitHub was having issues at the same time with their APIs. They seem to have subsided so we're moving ahead quickly to get this rolled out. We will manually trigger any builds that failed during this time once the services are back up and running at full capacity. We have been manually throttling the services to keep PRs flowing, and we will ensure none of the open PRs get missed.

Hi @denelon, is the pipeline issue solved? There's lots of PR backlogs (including mine)

@gnpaone,
They are not completely solved yet. We will leave this issue open until they are. The team is still working on parallel efforts to manually trigger runs (and watch logs/alerts for failures) and to work on automating the fixes/optimizations.

We've turned normal validation on. Any remaining PRs will be picked up by our "PR cleaner".


Is there any way to have the back button load just a cached page?

What version of Remix are you using?
2.0.1
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
I was observing my own site and a few sites in the Who's using remix in production discussion and it seems like out-of-the-box, Remix has this issue with the back button on mobile browsers where the back button doesn't really perform like you'd expect it to. It seems like by default, the page's loader is always re-run and you end up with this really janky experience:

Navigate to new page
Swipe to go back (or hit back button)
See flash of the latest page you were on, then the page you expect to see appears

Here's like 4 different examples I found pretty easily just by browsing through that discussion:
video of https://datagunung.com
https://imgur.com/aPe9TiN
video of https://hub.findkit.com
https://imgur.com/50NHxCH
video of https://basementcommunity.com
https://imgur.com/xruVJnD
video of https://ajourney.io
https://imgur.com/5vmVsaO
Now, from what I can tell, HTTP Cache control headers don't really solve this problem. I tried implementing them on both the document and each loader individually, and it seems like this issue still happens. I'm not sure if this is just a side-effect of using client-side hydration after the first render, or perhaps a side-effect of having markup that is generated at the time the page is requested, but I feel like getting a cached page when hitting the back button should be behavior default to Remix without the developer having to figure this out.
Expected Behavior
Page flashes old content before showing right content when hitting back button on mobile browsers
Actual Behavior
Page loads cached page with no flashing on mobile browsers

Also from what I can tell, this has been an issue with Remix from the start. I don't really have experience with Next.js, so I'm not sure if this is the norm with all universal-rendered frameworks that hydrate the client after first load, but I have a hunch that it is the norm.
Can this problem even be solved?

This looks like it might have something to do with <ScrollRestoration>.  Looks like the new react docs site had this same issue a while back and had to "hack" in a fix for safari only :/
https://twitter.com/dan_abramov/status/1568219286744797190
https://github.com/reactjs/react.dev/pull/5026
https://github.com/reactjs/react.dev/pull/5029
Anyone want to take a stab at a fix for this and see if the same thing works for <ScrollRestoration> in Remix?  The code itself is actually in react-router-dom so you could play around with direct edits to that in node_modules in your Remix app as a way to test it out locally.
https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/index.tsx#L1627

huh interesting. i'll try to give this a shot on my site

From my experience, it's happening only when client side logic receives new information from loader and forces history DOM to re-render and re-calculate. This is not the case, when your route's view is persistent or it's height stays the same as it is on history. When your first render (SSR) page looks the same as it is after first CSR will be applied, you will not see the jumping effect.
This flashing and jumpy effect can be avoided. It just requires a bit to think through the archidecture and rendering logic. Easiest way to understand what's going on your site, is to disable javascript temporary and navigate without javascript. Main reason, why this side-effect is so popular on production sites, is because developers are used to write CSR React.
Challenging topic is to avoid jumping effect on infinity pagination. There are loads of material about it on Google however and it isn't Remix issue, it's actually classical infinity pagination issue. That's why Facebook never destroy it's timeline from DOM when you navigate to another page.
About the ScrollRestoration of Remix - it's actually A+ grade component from my experience. About 1.5 year ago I used next.js on my projects and their ScrollRestoration was very chaotic and unpredictable back then. Not sure, if they have improved it by now.
Only case when revalidation of loaders during navigation on browser history stack causes the problem, is the case when entities sort order has changed (ie. new entity has been added or some entity has been resorted). It doesn't cause jumpy effect, it just replaces history elements with new sort order. I don't think that's expected UX behaviour. Users, who using browser navigation, usually expect to continue browsing where they left off.
So maybe this side-effect worths a discussion to add an option to opt-out from revalidation during the browser history navigation?

Also from what I can tell, this has been an issue with Remix from the start. I don't really have experience with Next.js, so I'm not sure if this is the norm with all universal-rendered frameworks that hydrate the client after first load, but I have a hunch that it is the norm.
Can this problem even be solved?

On iOS safari, if you visit next.js's documentation site, which is built upon nextjs itself, try to scroll back, you will have similar flashing issue. I think this might be a case in which safari does not behave well. No problems on chrome.

There in fact two problems during iOS swipe back action:

It shows a grey background instead of a snapshot of last page.
It does not go to the previous page at the same tick that popstate is fired. So the old page still shows and only after the loading is done, the previous page shows.

For problem 1, I'm not sure with the reason why a grey background shows. It seems this is the behavior if safari sees history.scrollRestoration === 'auto'? It should be a Safari problem.
For problem 2, for the current Remix which does not cache the data of useLoader, there can be hardly a perfect solution. Image popstate fires at the end of your swiping gesture, and you are supposed to see the previous page right after, but Remix makes you await the loader data, how can you see the loading previous page? You need to wait for the previous page's data to load, so the old page will still show.

just so it's on the record (and i haven't attempted the hack/fix yet, i can absolutely reproduce this on mobile chrome as well
just want this made aware before we write this off as a safari-only bug:
https://github.com/remix-run/remix/assets/7387001/e20b6e22-8ae0-4fa6-acd7-757610439eb7
i feel like there's 2 different issues here

the flashing of the previous page's content
the flashing of the blank white page

@martinmckenna I can reproduce issue on datagunung.com, however I am not able to reproduce issue on remix.run, shopify.com and on my projects.
I digged deeper and I can confirm datagunung have standard issue with infinity pagination which causes re-renders and blinking during back/forward navigation. You can read more about that on comment above.
Delay during back/forward navigation is caused by revalidation, which is different issue and discussion. It requires storing each state of the page to local_storage or session_storage to offer option to disable revalidation during browser history navigation. Currently, Remix do not save those states and that's why revalidation is required.

Hi @martinmckenna, I'm the maintainer of datagunung.com.
Thanks for highlighting the issue.
Have you got a chance to test this back button behavior in Android?
Here is one example that I was able to capture:
https://imgur.com/a/mLyeZrT
or
https://github.com/remix-run/remix/assets/101281822/d15acc5d-97cb-449c-8115-0dd56e44e8a3

@brophdawg11 so I FINALLY got around to trying out Dan's code and it seems to solve the blank page, but doesn't solve the issue of the "flashing the previous content"
https://imgur.com/9zL7bUf
I updated this code in my react-router-dom node_modules:
  // Trigger manual scroll restoration while we're active
  React.useEffect(() => {
    window.history.scrollRestoration = "manual";
    return () => {
      window.history.scrollRestoration = "auto";
    };
  }, []);

to this:
  React.useEffect(() => {
    const isSafari = /^((?!chrome|android).)*safari/i.test(navigator.userAgent);
    if (isSafari) {
      // This is kind of a lie.
      // We still rely on the manual Next.js scrollRestoration logic.
      // However, we *also* don't want Safari grey screen during the back swipe gesture.
      // Seems like it doesn't hurt to enable auto restore *and* Next.js logic at the same time.
      history.scrollRestoration = 'auto';
    } else {
      // For other browsers, let Next.js set scrollRestoration to 'manual'.
      // It seems to work better for Chrome and Firefox which don't animate the back swipe.
      window.history.scrollRestoration = "manual";
    }
  }, []);

I also tried without the cleanup function, but the issue still remains.
So as suspected, we have 2 bugs here, not 1.

i was doing some googling yesterday too and found some similar conversations happening in Svelekit, Nuxt, and Next:
https://github.com/sveltejs/kit/issues/10700
https://github.com/vercel/next.js/issues/57243
https://github.com/nuxt/nuxt/issues/6101

@brophdawg11 wondering if you had any thoughts on the above ^^
should the hacky fix be PRed here even if it doesn't solve the flickering issue?

To prevent white background instead of previous / forward page's preview during the half a scroll on Safari, the scrollRestoration auto hack seem to prevent that. However, it brings in visually more annoying feature - visual scroll jump. That's due to nature of "manual" and "auto" scrollRestoration behaviour.
I haven't seen any iOS user to use prev/forward actions to just preview the previous page. User goes back to navigate the last page where they left off. Considering that case scenario, white preview is less annoying than slower and jumpy previous page due to triple browser calcuations due to scrollPosition. White preview is something that iOS Safari developers can resolve if needed since it's not React, react-router (Remix), next.js problem - it's CSR problem. CSR happens with any SSR javascript framework which uses re-hydration / VirtualDOM (React, Angluar, Vue, ..).
All the other behaviours are logical - javascript will update your data on mount. During prev/scroll your view mounts and triggers data revalidation and all the other application specific mounting actions.

gonna post the react-router issues regarding the same bugs here too just for visibility:
https://github.com/remix-run/react-router/issues/10883

Since this issue has been open for years, may I assume Remix hasn't considered caching since day 0 thus is broken by design?

perhaps it would be a nice idea to just be able to turn off client-side routing altogether

perhaps it would be a nice idea to just be able to turn off client-side routing altogether

You can use  HTML-tag instead of  component to achieve that.

@mikkpokk lol good call, i'm dumb 😅

I implemented a workaround by listening for the touchstart, touchmove, and touchend events.
If the user attempts to use swipe gesture to previous / forward page, the default behavior is interrupted, and using history.go triggered navigate (like click back / forward page button behavior), preventing the brief display of the snapshot and ensuring smoother transitions.
See demo on pages, or try it

swipe gesture
custom swipe

Workaround

prevent touchstart clientX smaller than 20px from the screen left & right
touchend calculate distance since touchstart, if more than 40% of the screen width, than trigger history.go
add some transition in touchstart, touchmove and touchend


fix: add cache-key config for reusable workflows

Description
Using default cache-key will create a lot of caches (out of limit 10GB)
Steps To Reproduce

Update 'pubspec.lock'
Wait workflow finish
See new cache image

Expected Behavior
Have a config for cache-key
Screenshots
Not have
Additional Context
No

Hi @duythien0912 👋 Thanks for opening this issue.
Given that there has been no activity on this I'm actually going to close this as a won't fix. If this is still something that your facing we will need to get more details in order to triage this fully. If you have that information feel free to reopen the issue with it as a comment.


[K8S] Support to cleanup the spark driver pod after application terminates for retain period

:mag: Description
Describe Your Solution 🔧
As title, support to cleanup the application pod after application terminates for retain period
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Test locally.

Checklists
📝 Author Self Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review
[x] I have commented my code, particularly in hard-to-understand areas
[x] 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
[x] This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

[x] Pull request title is okay.
[x] No license issues.
[x] Milestone correctly set?
[ ] Test coverage is ok
[x] Assignees are selected.
[x] Minimum number of approvals
[ ] No changes are requested

Be nice. Be informative.

Codecov Report
Attention: 20 lines in your changes are missing coverage. Please review.

Comparison is base (23f32cf) 61.43% compared to head (1e07878) 61.38%.

Files
Patch %
Lines

...kyuubi/engine/KubernetesApplicationOperation.scala
13.04%
20 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5714      +/-   ##
============================================
- Coverage     61.43%   61.38%   -0.06%
  Complexity       23       23
============================================
  Files           607      607
  Lines         35735    35755      +20
  Branches       4896     4900       +4
============================================
- Hits          21955    21948       -7
- Misses        11402    11415      +13
- Partials       2378     2392      +14

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

thanks, merged to master and branch-1.8


Embedded images via Drawing Object

Hello Team/Community
is it possible to use pictures/images in Excel with binding to a cell?
If you have an image in Excel you can change the option via right mouse click on image -> size and options -> location and size dependent
I cannot see how to use this function via ABAP2XLS framework...
Thanks for response in advance

Sorry for the late answer.
I think it's possible. You can see it in action in the demo program ZDEMO_EXCEL16. The image moves when the top rows or left columns are resized:

No answer. Closing.


SQL Editor: Reconnect to the database if disconnected

Currently, if you try executing a query in the SQL editor against a disconnected data source, DBeaver will show an error that the connection needs to be established manually. Instead, we can ask the user if they want to connect and execute the query.

Please also consider an option in settings to disable the confirmation (agree automatically without confirmation).
Some other RDBMS behave in this way.

We already have this feature:

Just enable "Connect on editor activation"

I thought this option was turned off by default (and it indeed was until this year). I guess the issue can be closed now.


Update troubleshoot-vm-connectivity.md

Not everybody is aware of such tools. They should be added so readers know about their options.
netstat -an to list the ports that the VM is listening.
Test-NetConnection module in PowerShell to display diagnostic information for a connection such as ping test, tcp test etc.

@asudbring
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


why can we cat other Directory's files

we are able to cat resume.txt  while in struct

This is a valid issue, the moment I noticed this flaw, my immersion totally broke.


Viewport is not scrolled in both directions when changing both spy-x and spy-y at once

Sorry to bother again, but here is one more simple case which does not work as expected:
http://plnkr.co/edit/XwMjHTs3OAWXnJhTtBxs
It seems, some workaround is required (maybe even $digest or $timeout in the right place would work) to make it possible to update both x and y positions in one call.

Oh boy, it's fixed. Your spy variables are readable and writeable. When the first watcher on spyX fired it triggered a scroll which in turn overwrote both spies, spyX to the new and spyY to the previous value. Now, writing to spy variables happends async, after all watchers have been processed.


[slider] Style tab: update table with correct type style and spec image

-The type style token in the table should be $code-02 for the slider range label.
-Style spec image should reflect rule color changes, and type style change to start/end text values.

Closing, fixed with the v11 update.


Remove HasObservers.observations helper attribute

This clobbers the .observations attribute when used with HasObservations.

Sorry for a noob question - Would this model change require a migration?


Allow objects convertible to timestamps to be used in grains

Job: https://www.pivotaltracker.com/story/show/172553430
Makes use of https://github.com/bbc/rd-apmm-python-lib-mediatimestamp/pull/46 and will not pass CI until that is merged.

This has passed all CI tests fine. The spurious failure marking is due to a branch build.


Something to keep an eye on for outsourcing our postgres setup

Not sure if this plays nicely with helm, but might be worth looking at:
https://kubedb.com/docs/0.9.0/guides/postgres/

Superceded by the zalando operator.


Add placemarks and cluster markers

Statewide scale:

[ ] Identify TDI districts and districts with fellows separately using placemarks of different colors
[x] Remove the red and green coloring. Leave the numbering.

City scale:

[x] Combine icons into marker clusters displaying the number of entries / businesses
[ ] Change all cluster markers to (2016-06-14 Map Icon_Cluster Black.png) from the icons package

District scale:

[x] Adjust icons for scaling and collision
[x] Convert icons to placemarks, color by type (Utile)
[ ] Anchor placemark icons to parcel edge (in case of street front businesses) OR centroid of parcel (in case of parking lots)

I think as we left it Icons can overlap.

I have a demo of this almost ready. I will deploy to a staging environment for review.

Remove red and green coloring. Leave the count of points.

For custom group cluster icons: http://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.50000.html.

@nupoormonani Are we still wanting to change the cluster graphics to the icons package? I'm not sure how it'll look but we can if you think it's worth it.

@nupoormonani  @IanJakus

"Anchor placemark icons to parcel edge (in case of street front businesses) OR centroid of parcel (in case of parking lots)"

This point will require some further discussion. I don't think this is feasible for this release, but we should keep it on the table for the next version.

"Identify TDI districts and districts with fellows separately using placemarks of different colors"

Can you elaborate on this a little more? I thought we removed district markers?

@allthesignals @nupoormonani

thats fine
the idea was to have an icon to show which cities have fellows at the state level.
we are keeping circular shapes and removing coloring was my understanding, at least for this version.


Collapsing won't work when battery saving is enabled

Hi,
I've noticed that if the system is in battery saving mode (Android default one, Samsung one didn't affect this) the page won't collapse, as you can see in this vídeo:
youtu.be/iCS-hlQqods

I can see that some animations that were supposed to happen aren't occurring, so I believe that battery saving disables them and breaks InboxRecyclerView...

Found this warning on Logcat that only appears when battery saving mode is enabled:

W/OpenGLRenderer: Incorrectly called buildLayer on View: ExpandablePageLayout, destroying layer...

Hi, @saket, is there a possibility to fix this? Apparently batter saving mode disable some logic around ObjectAnimator and ValueAnimator...

Apparently some people were able to fix this by wrapping animations inside runnables, as seen here:
https://stackoverflow.com/questions/42523546/how-to-play-animations-in-battery-saver-mode-in-android-is-there-any-work-arou
https://stackoverflow.com/questions/36548097/object-animator-not-working-in-battery-saver-mode-post-jellybeanandroid-5-x

Sorry for taking so long to respond. I was moving to a new country, new job and a new home. This should be fixed in the next release


[Here’sHow To Watch!@$@ Canelo Alvarez vs Edgar Berlanga 𝘓𝘐𝘝𝘌 𝘚𝘵𝘳𝘦𝘢𝘮𝘪𝘯𝘨 Start Time, TV Channel

09 seconds ago-Saul "Canelo" Alvarez returns to the ring this weekend to defend his three (WBA, WBC and WBO) super middleweight world championships against Edgar Berlanga. It'll be a Mexico vs. Puerto Rico showdown this Saturday, with a fight card that also features matchups between Erislandy Lara and Danny Garcia, Caleb Plant and Trevor McCumby, Rolando Romero and Manuel Jaimes and more. The Canelo vs. Berlanga fight will go down at T-Mobile Arena in Las Vegas, kicking off at 8 p.m. ET, with ring walks anticipated around 11 p.m. ET.
WATCH 🔴📺▶ CLICK HERE TO WATCH LIVE
WATCH 🔴📺▶ CLICK HERE TO WATCH LIVE
Are you ready to tune in? If you’re looking for ways to watch this pay-per-view exclusive fight, we’ve got you covered. Here’s everything you need to know about how to watch the Canelo Álvarez vs. Edgar Berlanga fight, including the full fight card, two different ways to stream the boxing match and more.
How to watch the Canelo Álvarez vs. Edgar Berlanga fight:
Date: Saturday, Sept. 14, 2024
Start time: 8 p.m. ET
Fight time (approximate): 11 p.m. ET
Location: T-Mobile Arena, Las Vegas, NV
TV channel/streaming: PPV via DAZN
When is the Álvarez vs. Berlanga fight?
Canelo Álvarez and Edgar Berlanga are facing off for Mexican Independence Day weekend. The fight will be held this Saturday, Sept. 14, beginning at 8 p.m. ET. The pair are expected to face off in the ring around 11 p.m. that evening.
What channel is the Canelo Álvarez vs. Edgar Berlanga fight on?
The boxing match between Alvarez and Berlanga will be available only through pay-per-view in the US. You can purchase the fight through DAZN, Amazon PPV or directly through PPV.com.

Canelo Alvarez vs Edgar Berlanga


Support for path helpers

Currently, the likes of base_path() emits an UnresolvableInclude.
These are all of the path helpers to add support for
/**
     * Get the base path of the Laravel installation.
     *
     * @return string
     */
    public function basePath();

    /**
     * Get the path to the bootstrap directory.
     *
     * @param  string  $path Optionally, a path to append to the bootstrap path
     * @return string
     */
    public function bootstrapPath($path = '');

    /**
     * Get the path to the application configuration files.
     *
     * @param  string  $path Optionally, a path to append to the config path
     * @return string
     */
    public function configPath($path = '');

    /**
     * Get the path to the database directory.
     *
     * @param  string  $path Optionally, a path to append to the database path
     * @return string
     */
    public function databasePath($path = '');

    /**
     * Get the path to the environment file directory.
     *
     * @return string
     */
    public function environmentPath();

    /**
     * Get the path to the resources directory.
     *
     * @param  string  $path
     * @return string
     */
    public function resourcePath($path = '');

    /**
     * Get the path to the storage directory.
     *
     * @return string
     */
    public function storagePath();

Hey @muglug , any insight for how to inform psalm of these paths via the plugin?

A return type provider for that method that returns a literal string should work

Ah cool, i can probably just swap out the typehinted contract with the actual instance that provides these methods, thanks!

This should have been resolved in #99


Allow using TypeScript in iD's source?

I'd like to start a discussion whether iD should allow to use TypeScript in its source.
Using TypeScript in iD's source was rejected by @bhousel in 2018. But it seems as he changed his opinion about TypeScript since then as he is using TypeScript in id-sdk and RapiD - Facebook's fork of iD (as he pointed out in a comment and in his presentation at SOTM-US in 2019).
In my experience, using TypeScript does nothing less than taking the coding experience to a whole new level: When using an editor with TypeScript support (like VS Code for instance) you get code assistance as you type. This makes coding much more fluid and less error-prone than the indirect and delayed console outputs of the build or - even worse - errors which occur at runtime.
In my private fork of iD I added type information to iD (in the form of .d.ts files), which prevents me from looking up internal APIs all the time. If the iD team decides to allow TypeScript, I would be happy to contribute this work (by migrating the according .js files to .ts files, instead of adding .d.ts files).
In order to allow TypeScript, iD's build has to be changed in order to support this. I already contributed TypeScript build support (using the TypeScript compiler) in my PR "Add support for ReactJS". As I wrote in a comment, I would also contribute TypeScript build support using esbuild if the iD team decides rather to go this way, which would dramatically speed up build time.

How large is the increase of complexity in setup, for new contributors and in toolchain?

The setup is just the same: Once npm i, then the usual build commands npm run ….


County/State two-column identifier throwing error

To replicate:
Upload https://github.com/associatedpress/geomancer/blob/master/examples/my_fascinating_county_data.xlsx
Attempt to add Total population.
Error: No geographies matched

A note on this issue: This particular data set contained many county names that were truncated and some values that weren't actually counties (e.g. cities).
But I thought the expected behavior in these cases would be simply not to return data for the problem rows, rather than erroring for the entire mancing attempt.


Unable to build without this specific change.

Well the issue is that there's a ');' that the compiler doesn't recognize. Additionally, when using the change I'm trying to commit it doesn't recognize that the build is in WindowsDX. So instead I've just cut out the OpenGL if statements and put the DX ones in instead. Without the #IF or #IFELSE.

I've implemented this project by just copying all of the sourcecode into my project and removing the AssemblyInfo, Properties, and solution files. Is that what you meant?

Yep.

I pushed the following commit: https://github.com/discosultan/penumbra/commit/ac60beebab5e720defa6ebee8f21900f63f57d18. Does this work for you?

Yes, that solution resolves the issue. There's two other classes that implement similar #IF logic that also need that specific change.

Sweet, if you have Discord feel free to add me there. It's Eddie! #9684.
Over and out.


model analysis: separate dataset size for metric computation and explainer computation

schemas/pipeline config: add float type for training_size and validator when it's a float
model analysis: separate dataset size for explainer and regular metric computation

close #256


Privacy Settings UI for Posts

Should be able to set privacy of a new post creation:

private
private to another author
friends only
friends of friends
public

Completed.


Removing checklists from templates.

Pull Request Description
What issue does this change request address?
#325  (also discussed on developer mailing list)
What are the significant changes in functionality due to this change request?
It removes the checklists from the templates.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Job Test linux on 679fb9f : invalidated by @PaulTalbot-INL
Failure is not related to this merge request (framework/CodeInterfaceTests.melcorInterfaceForwardSamplingNoExe crashed).  Rerunning to check consistency.


Host Agent VSTFS Online Access Denied

Hi Folks, I have an unpacked solution within source control and is part of the deployment artifacts for release. I've configured the MSCRM Solution Package to pack this in a release however I get a Access Denied when the packer attempts to pack to the DeploymentArtifacts folder. I've tried other folders with the same error:
Access to the path 'd:\a\r1\a' is denied.
SolutionPackager: Exception thrown: System.UnauthorizedAccessException
Can anyone help please?
Thanks
Guy

Interestingly Copy files to System.DefaultWorkingDirectory works

@GuySimcox
The best practice is to pack the solution in the build definition and publish the solution zip as an artifact.
In your release definition you can then deploy the solution from the artifact.
Artifacts are generated in builds and consumed in releases.


Add support for newswrangler

It would be great if newsboat supported https://feedwrangler.net/ !
API docs: https://feedwrangler.net/developers

I won't mind merging such a PR and giving the contributor push access, as long as they want to support it by answering questions here and fixing bugs.
Current APIs are all implemented in C++, but we're moving to Rust. I don't know when remote APIs will be ported yet.


feature: remote stream id and track ids

should be using uuids but I need to track down something I suspect
about the bucket delay issue.

and yes, those helped tracking down what I was looking for...


Installation problem: No module named dopamine.atari

Hi,
I am facing a problem with installing and testing Dopamine. I am using an Ubuntu 18 OS and followed the exact instruction on the main page for "install via source" without getting any error. However, when I execute the commands on "Running tests" section I get errors
Command:
python tests/atari_init_test.py
Output:
ImportError: No module named dopamine.atari
Command:
python -um dopamine.atari.train
--agent_name=dqn
--base_dir=/tmp/dopamine
--gin_files='dopamine/agents/dqn/configs/dqn.gin'
Output:
Illegal instruction (core dumped)
I appreciate any suggestion on how I can solve this issue.

Likely that this was due to the PYTHONPATH not being set correctly.


Dockerfile: gems should be pinned to specific versions + http gem should be updateable from a separate file

I want to make sure we use a specific set of versions every time we build the Dockerfile, so we won't have unexpected problems / upgrades.
Please add a specific version specifier to all gems installed in the Dockerfile
In addition, I want to have the option to automatically update the http input plugin gem from CI/CD process. This can be done by creating a file e.g. fluent-plugin-http-cwm.version and then in the Dockerfile, COPY that file before the gem install script and do something like this: gem install fluent-plugin-http-cwm==$(cat fluent-plugin-http-cwm.version)

Sure. I'll pin the versions for S3 and ElasticSearch gems.
Regarding fluent-plugin-http-cwm's version, how about leaving it like that?
The latest/newest published gem will automatically be installed in the absence of a version specifier.

Sure. I'll pin the versions for S3 and ElasticSearch gems.
Regarding fluent-plugin-http-cwm's version, how about leaving it like that?
The latest/newest published gem will automatically be installed in the absence of a version specifier.

there are a few reasons:

to know exactly which version is installed, when it was updated, per each git commit
allow to rollback to a previous version
prevent problems where latest gem is not yet available so we may get previous version, or other possible problems depending on the gem repository

there are a few reasons:

to know exactly which version is installed, when it was updated, per each git commit
allow to rollback to a previous version
prevent problems where latest gem is not yet available so we may get previous version, or other possible problems depending on the gem repository

Added in #6.

Added in #6.


60FPS Hack stops Wind Waker from booting

If any other code other than "$FPSHack_00_SetParam_FramerateFactor__60" is ticked, Wind Waker will not boot. Issue present on Dolphin 5.0-7753. Having this code on by itself also makes no difference to the framerate.
GameINI is at default settings, no other AR codes in use, all graphical settings at default, CPU Clock Override makes no difference.

Can confirm that this hack seems to crash dolphin as of the current version 5.0- 8545

please add that to the readme :)


doc(lep): update system backup lep for backup bacingimages

ref: https://github.com/longhorn/longhorn/issues/5085
We now support backup backingimages when doing system backup
Update the lep.

Could you also check the Non-goals [optional] section regarding the backing image? It seems like it could be removed.

Hi @c3y1huang
Removed, thanks


Compare: how to remove a layer?

Close does not remove a layer; add a remove option?

There's an X to remove a layer:

It doesn't appear till you stop loading, but clicking the loading spinner stops loading, then the X appears and you can remove the layer by clicking the X.
I just tested and it seems to work. If you have a different experience, go ahead and reopen this ticket with more info (browser, example queries, what happens when you click, etc.)