Vertical scrolling is staggered

VSCode Version: 1.16.1
OS Version: Windows 10 Pro (1703)

Steps to Reproduce:

Scroll through any file using touchpad.

Reproduces without extensions:

Duplicate of #13612


implement JSL particle filtering examples

https://github.com/probml/JSL/blob/main/jsl/demos/bootstrap_filter.py
https://github.com/probml/JSL/blob/main/jsl/demos/bootstrap_filter_maneuver.py
https://github.com/probml/JSL/blob/main/jsl/demos/rbpf_maneuver.py
https://github.com/probml/JSL/blob/main/jsl/demos/sis_vs_smc.py

Let's loop in my lab on this one — Dieterich Lawson and Andy Warrington have written a lot of particle filtering code recently. I think we'll have lots of stuff to start from.


Add some info/debug commands

Chart Review tries to be a bit magic for you, but sometimes you want to know what's happening under the covers.

#34
Print the anon/real/label studio ID mappings and/or users (chart-review ids?)

Andy suggested headers like: LabelStudio ID, DocRef, Encounter, DEID, ignored (yes/no)
#37 (adds ignored status into normal info command)

Which labels are in the Label Studio export (make a csv of it? chart-review ls-labels?)

(I thought I already had a ticket for this, but I couldn't find it. :shrug:)

Request from Andy:
"Can we output how many times an annotator provided a label?"
Like:
Annotator | Chart Count | Label
ICD10 #,### ideation-past
ICD10 #,### ideation-present
ICD10 #,### action-past
ICD10 #,### action-present
Andy #,### ideation-past
Andy #,### ideation-present
Andy #,### action-past
Andy #,### action-present
Rena #,### ideation-past
Rena #,### ideation-present
Rena #,### action-past
Rena #,### action-present

OK all these ideas are now implemented, except: Which labels are in the Label Studio export (make a csv of it? chart-review ls-labels?) - breaking that out to its own ticket in #39.


cant preview html response

Your description here
View parsed html is useless now. I can only see a small strip with the actual content
Expected outcome
What should happen?
Allow me to scroll the entire page
Actual outcome
What happened?
Page shows up in a one-line-height scrollable view

Versions
App: <IP_ADDRESS>-stable
Chrome: 50.0.2661.102
Platform: Mac OS X (10_11_4)
Steps to reproduce

Hi,
Thank you for issue report.
Will it be able to send me a HTML you want to display? With changed data but I need something to test it because I can't reproduce a problem here.

I see the same thing when going from an parsed html response then clicking on the preview button.  The display collapses to a tiny windows that is barely scrollable. It appears to only happen if the html is just a snippet.


add fish, zsh, and bash support (link and/or source files)

Ref. lib/reel.rb:58
# TODO add fish, zsh, and bash support (link and/or source files)

(automatically generated by Github-Todos)

Ref. lib/reel.rb:39
# TODO: add fish, zsh, and bash support (link and/or source files)
# FIXME: fish loading does not seem to be working


Bump Flux CLI and controllers to latest GA releases

Bumping Flux CLI and controllers to their latest GA releases.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


qemu has the wrong url to download

% scoop install qemu
Installing 'qemu' (2.10.0-rc3).
The remote server returned an error: (404) Not Found.
URL https://qemu.weilnetz.de/w64/qemu-w64-setup-20170816.exe#/dl.7z is not valid

Url showld be
http://qemu.weilnetz.de/w64/qemu-w64-setup-20170824.exe
See here for a list of files
https://qemu.weilnetz.de/w64/

Your scoop bucket is out of date, please run scoop update and try it again.

Sorry for the trouble.  Thanks for the help.


Manufacturing Related Entities

Understanding you could build a custom model for Manufacturing using other entities, is there any work going on to build a model with entities specific to Manufacturing?  This would include things like work orders, equipment, testing (UUT - unit under test), inventory quantities, etc.
This would be a big effort when using with IoT and Digital Twin concepts.
I noticed there were Industry Accelerators.  There seems like there would be one for Manufacturing.

Hi there,
we do not have specific timeline for the Industry Accelerator for manufacturing at the moment. and agree with your assessment in re complexity


remove local embeddings for self-serve

See https://sourcegraph.slack.com/archives/C05AGQYD528/p1727282487703709 for context.
Test plan
CI & e2e

@sqs maybe I missed it, is anything being done to actually delete the embeddings files from users' machines?


release process for the ci/cd itself

Currently gitlab uses the trunk of the master branch of ingest-kube-deployment branch as the sourceof the delployment scripts (k8s deployment descriptors, helm charts, etc)
See pipeline definition
This makes it difficult to safely make changes to the ci/cd process without affecting deployment to all envs.
A simple way to tackle it would be to checkout the repo by a tag. This way deployment on dev can be tweaked while prod stays consistent.
A good naming scheme for the tag would be naming them as the environment.


Pulsar API improvements

Suggestions for Pulsar improvements:

It would be nice to have a simple API that just takes a URL and topic name
Schema itself could be serialized (via SchemaInfo) and no need to take a supplier
ProjectionFN should be optional and instead it should be Entry<K,V> that's emitted

Also, we should add a random suffix to default subscription name to avoid the name collisions occurring when running multiple jobs.


Remove invalid construct YIELD *

This PR modifies the grammar rule that allows the YIELD * construct, which is not recognized by Neo4j as valid syntax:
neo4j@neo4j> CALL db.labels() YIELD *;
Invalid input '*': expected whitespace, comment, aliased procedure result field or simple procedure result field (line 1, column 24 (offset: 23))
"CALL db.labels() YIELD *;"

Thank you for this! According to the specification, YIELD * should only be allowed in standalone calls. Although not even that is supported by Neo4j, which suggests that it might not be a very useful feature.

Oh, interesting! I just came across this and assumed it was an error; feel free to close the PR if you prefer to leave the specification unmodified.

No, I think you highlight a real inconsistency. But I note that there might be more that needs fixing than what you changed.
Given that YIELD * for standalone calls is not implemented by Neo4j, and not asked for, I'm wondering if it is really needed. So possibly we should change the specification.
I'll leave this open until there has been time to have a discussion around this, and then probably either merge it or supersede it with another change that fixes the related issues as well.
A simple one that I note is that YieldItems allows for a sequence of a sequence of items followed by an optional where clause - that is one level of sequence nesting too many.

To progress this I have created #497. If people are happy with #497 and is considered as a satisfactory solution, this PR here can probably be closed, eventually.

I have merged #497 and subsequently will close this PR.


FINERACT-1480: Fix Swagger UI broken by incremental build

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

... hmmm... 404... but the changes look ok to me...

Looks like the WAR set-up was not working correctly so have reworked that... it all works for me locally - let's see if the tests pass as well.


Fix list slice index check

Given a list slice li[i:j], the parser will crash when i > j. Add
a check to raise IndexOutOfRange.
Also add some tests.

Amended to address all the concerns(so far). Rebased onto current master.


New Storage Disk Types GCP

Add new disk type options to GCP

Hello @akira-miyazato! Thanks for opening this PR.

In the file dbaas/physical/migrations/0124_auto__add_diskofferingtype__add_field_volume_disk_offering_type__add_f.py:

Line 14:101: E501 line too long (108 > 100 characters)
Line 15:101: E501 line too long (104 > 100 characters)
Line 32:101: E501 line too long (106 > 100 characters)
Line 37:101: E501 line too long (188 > 100 characters)
Line 42:101: E501 line too long (197 > 100 characters)
Line 46:5: E303 too many blank lines (2)
Line 63:5: E303 too many blank lines (2)
Line 66:101: E501 line too long (115 > 100 characters)
Line 68:101: E501 line too long (131 > 100 characters)
Line 69:101: E501 line too long (130 > 100 characters)
Line 70:101: E501 line too long (130 > 100 characters)
Line 71:101: E501 line too long (126 > 100 characters)
Line 74:101: E501 line too long (110 > 100 characters)
Line 78:101: E501 line too long (101 > 100 characters)
Line 79:101: E501 line too long (115 > 100 characters)
Line 80:101: E501 line too long (116 > 100 characters)
Line 83:101: E501 line too long (102 > 100 characters)
Line 84:101: E501 line too long (190 > 100 characters)
Line 85:101: E501 line too long (101 > 100 characters)
Line 86:101: E501 line too long (119 > 100 characters)
Line 87:101: E501 line too long (111 > 100 characters)
Line 88:101: E501 line too long (129 > 100 characters)
Line 93:101: E501 line too long (102 > 100 characters)
Line 94:101: E501 line too long (158 > 100 characters)
Line 97:101: E501 line too long (187 > 100 characters)
Line 99:101: E501 line too long (123 > 100 characters)
Line 105:101: E501 line too long (111 > 100 characters)
Line 106:101: E501 line too long (103 > 100 characters)
Line 107:101: E501 line too long (107 > 100 characters)
Line 108:101: E501 line too long (180 > 100 characters)
Line 113:101: E501 line too long (110 > 100 characters)
Line 114:101: E501 line too long (106 > 100 characters)
Line 116:101: E501 line too long (195 > 100 characters)
Line 117:101: E501 line too long (105 > 100 characters)
Line 120:101: E501 line too long (161 > 100 characters)
Line 128:101: E501 line too long (115 > 100 characters)
Line 131:101: E501 line too long (110 > 100 characters)
Line 135:101: E501 line too long (115 > 100 characters)
Line 138:101: E501 line too long (214 > 100 characters)
Line 139:101: E501 line too long (110 > 100 characters)
Line 145:101: E501 line too long (115 > 100 characters)
Line 146:101: E501 line too long (126 > 100 characters)
Line 147:101: E501 line too long (205 > 100 characters)
Line 148:101: E501 line too long (234 > 100 characters)
Line 149:101: E501 line too long (122 > 100 characters)
Line 150:101: E501 line too long (126 > 100 characters)
Line 151:101: E501 line too long (176 > 100 characters)
Line 152:101: E501 line too long (203 > 100 characters)
Line 153:101: E501 line too long (186 > 100 characters)
Line 155:101: E501 line too long (111 > 100 characters)
Line 159:101: E501 line too long (103 > 100 characters)
Line 160:101: E501 line too long (124 > 100 characters)
Line 161:101: E501 line too long (123 > 100 characters)
Line 162:101: E501 line too long (106 > 100 characters)
Line 163:101: E501 line too long (103 > 100 characters)
Line 164:101: E501 line too long (172 > 100 characters)
Line 165:101: E501 line too long (165 > 100 characters)
Line 166:101: E501 line too long (129 > 100 characters)
Line 168:101: E501 line too long (123 > 100 characters)
Line 169:101: E501 line too long (111 > 100 characters)
Line 170:101: E501 line too long (101 > 100 characters)
Line 173:101: E501 line too long (120 > 100 characters)
Line 174:101: E501 line too long (102 > 100 characters)
Line 175:101: E501 line too long (115 > 100 characters)
Line 177:101: E501 line too long (122 > 100 characters)
Line 179:101: E501 line too long (114 > 100 characters)
Line 180:101: E501 line too long (102 > 100 characters)
Line 181:101: E501 line too long (111 > 100 characters)
Line 186:101: E501 line too long (115 > 100 characters)
Line 187:101: E501 line too long (184 > 100 characters)
Line 189:101: E501 line too long (103 > 100 characters)
Line 191:101: E501 line too long (110 > 100 characters)
Line 195:101: E501 line too long (115 > 100 characters)
Line 196:101: E501 line too long (189 > 100 characters)
Line 198:101: E501 line too long (103 > 100 characters)
Line 199:101: E501 line too long (103 > 100 characters)
Line 200:101: E501 line too long (110 > 100 characters)
Line 203:101: E501 line too long (150 > 100 characters)
Line 204:101: E501 line too long (115 > 100 characters)
Line 205:101: E501 line too long (178 > 100 characters)
Line 206:101: E501 line too long (227 > 100 characters)
Line 210:101: E501 line too long (117 > 100 characters)
Line 211:101: E501 line too long (117 > 100 characters)
Line 212:101: E501 line too long (118 > 100 characters)
Line 213:101: E501 line too long (153 > 100 characters)
Line 214:101: E501 line too long (127 > 100 characters)
Line 215:101: E501 line too long (111 > 100 characters)
Line 216:101: E501 line too long (109 > 100 characters)
Line 218:101: E501 line too long (153 > 100 characters)
Line 222:101: E501 line too long (115 > 100 characters)
Line 223:101: E501 line too long (137 > 100 characters)
Line 226:101: E501 line too long (142 > 100 characters)
Line 227:101: E501 line too long (146 > 100 characters)
Line 229:101: E501 line too long (115 > 100 characters)
Line 230:101: E501 line too long (110 > 100 characters)
Line 234:101: E501 line too long (115 > 100 characters)
Line 237:101: E501 line too long (103 > 100 characters)
Line 238:101: E501 line too long (110 > 100 characters)
Line 242:101: E501 line too long (177 > 100 characters)
Line 243:101: E501 line too long (115 > 100 characters)
Line 245:101: E501 line too long (153 > 100 characters)
Line 246:101: E501 line too long (192 > 100 characters)
Line 248:101: E501 line too long (103 > 100 characters)
Line 252:101: E501 line too long (110 > 100 characters)
Line 256:101: E501 line too long (115 > 100 characters)
Line 257:101: E501 line too long (177 > 100 characters)
Line 260:101: E501 line too long (110 > 100 characters)
Line 265:101: E501 line too long (115 > 100 characters)
Line 266:101: E501 line too long (176 > 100 characters)
Line 267:101: E501 line too long (107 > 100 characters)
Line 269:101: E501 line too long (109 > 100 characters)
Line 270:101: E501 line too long (124 > 100 characters)
Line 271:101: E501 line too long (128 > 100 characters)
Line 272:101: E501 line too long (128 > 100 characters)
Line 273:101: E501 line too long (122 > 100 characters)
Line 274:101: E501 line too long (104 > 100 characters)
Line 275:101: E501 line too long (106 > 100 characters)
Line 276:101: E501 line too long (106 > 100 characters)
Line 277:101: E501 line too long (111 > 100 characters)
Line 278:101: E501 line too long (118 > 100 characters)
Line 279:101: E501 line too long (120 > 100 characters)
Line 284:101: E501 line too long (115 > 100 characters)
Line 285:101: E501 line too long (154 > 100 characters)
Line 287:101: E501 line too long (184 > 100 characters)
Line 288:101: E501 line too long (140 > 100 characters)
Line 294:101: E501 line too long (101 > 100 characters)
Line 296:101: E501 line too long (113 > 100 characters)
Line 297:101: E501 line too long (111 > 100 characters)
Line 298:101: E501 line too long (111 > 100 characters)
Line 303:101: E501 line too long (115 > 100 characters)
Line 305:101: E501 line too long (124 > 100 characters)
Line 306:101: E501 line too long (177 > 100 characters)
Line 307:101: E501 line too long (110 > 100 characters)
Line 312:101: E501 line too long (115 > 100 characters)
Line 313:101: E501 line too long (180 > 100 characters)
Line 317:101: E501 line too long (110 > 100 characters)
Line 320:101: E501 line too long (147 > 100 characters)
Line 321:101: E501 line too long (146 > 100 characters)
Line 322:101: E501 line too long (115 > 100 characters)
Line 323:101: E501 line too long (127 > 100 characters)
Line 324:101: E501 line too long (125 > 100 characters)
Line 326:101: E501 line too long (181 > 100 characters)
Line 329:101: E501 line too long (113 > 100 characters)
Line 330:101: E501 line too long (110 > 100 characters)
Line 334:101: E501 line too long (115 > 100 characters)
Line 335:101: E501 line too long (104 > 100 characters)
Line 336:101: E501 line too long (213 > 100 characters)
Line 337:101: E501 line too long (225 > 100 characters)
Line 338:101: E501 line too long (136 > 100 characters)
Line 339:101: E501 line too long (224 > 100 characters)
Line 340:101: E501 line too long (176 > 100 characters)
Line 346:101: E501 line too long (239 > 100 characters)
Line 347:101: E501 line too long (178 > 100 characters)
Line 348:101: E501 line too long (103 > 100 characters)
Line 349:101: E501 line too long (239 > 100 characters)
Line 351:101: E501 line too long (194 > 100 characters)
Line 352:101: E501 line too long (191 > 100 characters)
Line 353:101: E501 line too long (111 > 100 characters)
Line 354:101: E501 line too long (190 > 100 characters)
Line 358:101: E501 line too long (115 > 100 characters)
Line 361:101: E501 line too long (142 > 100 characters)
Line 362:101: E501 line too long (111 > 100 characters)
Line 370:101: E501 line too long (115 > 100 characters)
Line 373:101: E501 line too long (146 > 100 characters)
Line 375:101: E501 line too long (103 > 100 characters)
Line 376:101: E501 line too long (109 > 100 characters)
Line 380:101: E501 line too long (161 > 100 characters)
Line 381:101: E501 line too long (111 > 100 characters)
Line 386:101: E501 line too long (103 > 100 characters)
Line 388:101: E501 line too long (101 > 100 characters)
Line 395:101: E501 line too long (115 > 100 characters)
Line 396:101: E501 line too long (121 > 100 characters)
Line 397:101: E501 line too long (182 > 100 characters)
Line 398:101: E501 line too long (109 > 100 characters)
Line 401:101: E501 line too long (205 > 100 characters)
Line 402:101: E501 line too long (186 > 100 characters)
Line 403:101: E501 line too long (110 > 100 characters)
Line 408:101: E501 line too long (127 > 100 characters)
Line 409:101: E501 line too long (115 > 100 characters)
Line 412:101: E501 line too long (130 > 100 characters)
Line 415:101: E501 line too long (131 > 100 characters)
Line 416:101: E501 line too long (110 > 100 characters)
Line 419:101: E501 line too long (121 > 100 characters)
Line 421:101: E501 line too long (115 > 100 characters)
Line 423:101: E501 line too long (159 > 100 characters)
Line 424:101: E501 line too long (165 > 100 characters)
Line 425:101: E501 line too long (110 > 100 characters)
Line 429:101: E501 line too long (115 > 100 characters)
Line 432:101: E501 line too long (141 > 100 characters)
Line 433:101: E501 line too long (176 > 100 characters)
Line 434:101: E501 line too long (111 > 100 characters)
Line 435:101: E501 line too long (119 > 100 characters)
Line 439:101: E501 line too long (115 > 100 characters)
Line 443:101: E501 line too long (111 > 100 characters)
Line 444:101: E501 line too long (101 > 100 characters)
Line 448:101: E501 line too long (115 > 100 characters)
Line 449:101: E501 line too long (132 > 100 characters)
Line 450:101: E501 line too long (182 > 100 characters)
Line 454:101: E501 line too long (109 > 100 characters)
Line 455:101: E501 line too long (111 > 100 characters)
Line 456:101: E501 line too long (107 > 100 characters)
Line 460:33: W292 no newline at end of file

In the file dbaas/physical/migrations/0125_initial_insert_disk_offering_type.py:

Line 21:101: E501 line too long (115 > 100 characters)
Line 23:101: E501 line too long (131 > 100 characters)
Line 24:101: E501 line too long (130 > 100 characters)
Line 25:101: E501 line too long (130 > 100 characters)
Line 26:101: E501 line too long (126 > 100 characters)
Line 29:101: E501 line too long (110 > 100 characters)
Line 33:101: E501 line too long (101 > 100 characters)
Line 34:101: E501 line too long (115 > 100 characters)
Line 35:101: E501 line too long (116 > 100 characters)
Line 38:101: E501 line too long (102 > 100 characters)
Line 39:101: E501 line too long (190 > 100 characters)
Line 40:101: E501 line too long (101 > 100 characters)
Line 41:101: E501 line too long (119 > 100 characters)
Line 42:101: E501 line too long (111 > 100 characters)
Line 43:101: E501 line too long (129 > 100 characters)
Line 48:101: E501 line too long (102 > 100 characters)
Line 49:101: E501 line too long (158 > 100 characters)
Line 52:101: E501 line too long (187 > 100 characters)
Line 54:101: E501 line too long (123 > 100 characters)
Line 60:101: E501 line too long (111 > 100 characters)
Line 61:101: E501 line too long (103 > 100 characters)
Line 62:101: E501 line too long (107 > 100 characters)
Line 63:101: E501 line too long (180 > 100 characters)
Line 68:101: E501 line too long (110 > 100 characters)
Line 69:101: E501 line too long (106 > 100 characters)
Line 71:101: E501 line too long (195 > 100 characters)
Line 72:101: E501 line too long (105 > 100 characters)
Line 75:101: E501 line too long (161 > 100 characters)
Line 83:101: E501 line too long (115 > 100 characters)
Line 86:101: E501 line too long (110 > 100 characters)
Line 90:101: E501 line too long (115 > 100 characters)
Line 93:101: E501 line too long (214 > 100 characters)
Line 94:101: E501 line too long (110 > 100 characters)
Line 100:101: E501 line too long (115 > 100 characters)
Line 101:101: E501 line too long (126 > 100 characters)
Line 102:101: E501 line too long (205 > 100 characters)
Line 103:101: E501 line too long (234 > 100 characters)
Line 104:101: E501 line too long (122 > 100 characters)
Line 105:101: E501 line too long (126 > 100 characters)
Line 106:101: E501 line too long (176 > 100 characters)
Line 107:101: E501 line too long (203 > 100 characters)
Line 108:101: E501 line too long (186 > 100 characters)
Line 110:101: E501 line too long (111 > 100 characters)
Line 114:101: E501 line too long (103 > 100 characters)
Line 115:101: E501 line too long (124 > 100 characters)
Line 116:101: E501 line too long (123 > 100 characters)
Line 117:101: E501 line too long (106 > 100 characters)
Line 118:101: E501 line too long (103 > 100 characters)
Line 119:101: E501 line too long (172 > 100 characters)
Line 120:101: E501 line too long (165 > 100 characters)
Line 121:101: E501 line too long (129 > 100 characters)
Line 123:101: E501 line too long (123 > 100 characters)
Line 124:101: E501 line too long (111 > 100 characters)
Line 125:101: E501 line too long (101 > 100 characters)
Line 128:101: E501 line too long (120 > 100 characters)
Line 129:101: E501 line too long (102 > 100 characters)
Line 130:101: E501 line too long (115 > 100 characters)
Line 132:101: E501 line too long (122 > 100 characters)
Line 134:101: E501 line too long (114 > 100 characters)
Line 135:101: E501 line too long (102 > 100 characters)
Line 136:101: E501 line too long (111 > 100 characters)
Line 141:101: E501 line too long (115 > 100 characters)
Line 142:101: E501 line too long (184 > 100 characters)
Line 144:101: E501 line too long (103 > 100 characters)
Line 146:101: E501 line too long (110 > 100 characters)
Line 150:101: E501 line too long (115 > 100 characters)
Line 151:101: E501 line too long (189 > 100 characters)
Line 153:101: E501 line too long (103 > 100 characters)
Line 154:101: E501 line too long (103 > 100 characters)
Line 155:101: E501 line too long (110 > 100 characters)
Line 158:101: E501 line too long (150 > 100 characters)
Line 159:101: E501 line too long (115 > 100 characters)
Line 160:101: E501 line too long (178 > 100 characters)
Line 161:101: E501 line too long (227 > 100 characters)
Line 165:101: E501 line too long (117 > 100 characters)
Line 166:101: E501 line too long (117 > 100 characters)
Line 167:101: E501 line too long (118 > 100 characters)
Line 168:101: E501 line too long (153 > 100 characters)
Line 169:101: E501 line too long (127 > 100 characters)
Line 170:101: E501 line too long (111 > 100 characters)
Line 171:101: E501 line too long (109 > 100 characters)
Line 173:101: E501 line too long (153 > 100 characters)
Line 177:101: E501 line too long (115 > 100 characters)
Line 178:101: E501 line too long (137 > 100 characters)
Line 181:101: E501 line too long (142 > 100 characters)
Line 182:101: E501 line too long (146 > 100 characters)
Line 184:101: E501 line too long (115 > 100 characters)
Line 185:101: E501 line too long (110 > 100 characters)
Line 189:101: E501 line too long (115 > 100 characters)
Line 192:101: E501 line too long (103 > 100 characters)
Line 193:101: E501 line too long (110 > 100 characters)
Line 197:101: E501 line too long (177 > 100 characters)
Line 198:101: E501 line too long (115 > 100 characters)
Line 200:101: E501 line too long (153 > 100 characters)
Line 201:101: E501 line too long (192 > 100 characters)
Line 203:101: E501 line too long (103 > 100 characters)
Line 207:101: E501 line too long (110 > 100 characters)
Line 211:101: E501 line too long (115 > 100 characters)
Line 212:101: E501 line too long (177 > 100 characters)
Line 215:101: E501 line too long (110 > 100 characters)
Line 220:101: E501 line too long (115 > 100 characters)
Line 221:101: E501 line too long (176 > 100 characters)
Line 222:101: E501 line too long (107 > 100 characters)
Line 224:101: E501 line too long (109 > 100 characters)
Line 225:101: E501 line too long (124 > 100 characters)
Line 226:101: E501 line too long (128 > 100 characters)
Line 227:101: E501 line too long (128 > 100 characters)
Line 228:101: E501 line too long (122 > 100 characters)
Line 229:101: E501 line too long (104 > 100 characters)
Line 230:101: E501 line too long (106 > 100 characters)
Line 231:101: E501 line too long (106 > 100 characters)
Line 232:101: E501 line too long (111 > 100 characters)
Line 233:101: E501 line too long (118 > 100 characters)
Line 234:101: E501 line too long (120 > 100 characters)
Line 239:101: E501 line too long (115 > 100 characters)
Line 240:101: E501 line too long (154 > 100 characters)
Line 242:101: E501 line too long (184 > 100 characters)
Line 243:101: E501 line too long (140 > 100 characters)
Line 249:101: E501 line too long (101 > 100 characters)
Line 251:101: E501 line too long (113 > 100 characters)
Line 252:101: E501 line too long (111 > 100 characters)
Line 253:101: E501 line too long (111 > 100 characters)
Line 258:101: E501 line too long (115 > 100 characters)
Line 260:101: E501 line too long (124 > 100 characters)
Line 261:101: E501 line too long (177 > 100 characters)
Line 262:101: E501 line too long (110 > 100 characters)
Line 267:101: E501 line too long (115 > 100 characters)
Line 268:101: E501 line too long (180 > 100 characters)
Line 272:101: E501 line too long (110 > 100 characters)
Line 275:101: E501 line too long (147 > 100 characters)
Line 276:101: E501 line too long (146 > 100 characters)
Line 277:101: E501 line too long (115 > 100 characters)
Line 278:101: E501 line too long (127 > 100 characters)
Line 279:101: E501 line too long (125 > 100 characters)
Line 281:101: E501 line too long (181 > 100 characters)
Line 284:101: E501 line too long (113 > 100 characters)
Line 285:101: E501 line too long (110 > 100 characters)
Line 289:101: E501 line too long (115 > 100 characters)
Line 290:101: E501 line too long (104 > 100 characters)
Line 291:101: E501 line too long (213 > 100 characters)
Line 292:101: E501 line too long (225 > 100 characters)
Line 293:101: E501 line too long (136 > 100 characters)
Line 294:101: E501 line too long (224 > 100 characters)
Line 295:101: E501 line too long (176 > 100 characters)
Line 301:101: E501 line too long (239 > 100 characters)
Line 302:101: E501 line too long (178 > 100 characters)
Line 303:101: E501 line too long (103 > 100 characters)
Line 304:101: E501 line too long (239 > 100 characters)
Line 306:101: E501 line too long (194 > 100 characters)
Line 307:101: E501 line too long (191 > 100 characters)
Line 308:101: E501 line too long (111 > 100 characters)
Line 309:101: E501 line too long (190 > 100 characters)
Line 313:101: E501 line too long (115 > 100 characters)
Line 316:101: E501 line too long (142 > 100 characters)
Line 317:101: E501 line too long (111 > 100 characters)
Line 325:101: E501 line too long (115 > 100 characters)
Line 328:101: E501 line too long (146 > 100 characters)
Line 330:101: E501 line too long (103 > 100 characters)
Line 331:101: E501 line too long (109 > 100 characters)
Line 335:101: E501 line too long (161 > 100 characters)
Line 336:101: E501 line too long (111 > 100 characters)
Line 341:101: E501 line too long (103 > 100 characters)
Line 343:101: E501 line too long (101 > 100 characters)
Line 350:101: E501 line too long (115 > 100 characters)
Line 351:101: E501 line too long (121 > 100 characters)
Line 352:101: E501 line too long (182 > 100 characters)
Line 353:101: E501 line too long (109 > 100 characters)
Line 356:101: E501 line too long (205 > 100 characters)
Line 357:101: E501 line too long (186 > 100 characters)
Line 358:101: E501 line too long (110 > 100 characters)
Line 363:101: E501 line too long (127 > 100 characters)
Line 364:101: E501 line too long (115 > 100 characters)
Line 367:101: E501 line too long (130 > 100 characters)
Line 370:101: E501 line too long (131 > 100 characters)
Line 371:101: E501 line too long (110 > 100 characters)
Line 374:101: E501 line too long (121 > 100 characters)
Line 376:101: E501 line too long (115 > 100 characters)
Line 378:101: E501 line too long (159 > 100 characters)
Line 379:101: E501 line too long (165 > 100 characters)
Line 380:101: E501 line too long (110 > 100 characters)
Line 384:101: E501 line too long (115 > 100 characters)
Line 387:101: E501 line too long (141 > 100 characters)
Line 388:101: E501 line too long (176 > 100 characters)
Line 389:101: E501 line too long (111 > 100 characters)
Line 390:101: E501 line too long (119 > 100 characters)
Line 394:101: E501 line too long (115 > 100 characters)
Line 398:101: E501 line too long (111 > 100 characters)
Line 399:101: E501 line too long (101 > 100 characters)
Line 403:101: E501 line too long (115 > 100 characters)
Line 404:101: E501 line too long (132 > 100 characters)
Line 405:101: E501 line too long (182 > 100 characters)
Line 409:101: E501 line too long (109 > 100 characters)
Line 410:101: E501 line too long (111 > 100 characters)
Line 411:101: E501 line too long (107 > 100 characters)
Line 415:33: W292 no newline at end of file

In the file dbaas/workflow/steps/util/volume_provider.py:

Line 531:101: E501 line too long (109 > 100 characters)

Do see the Hitchhiker's guide to code style

Codecov Report

Merging #681 (16cf565) into master (b7906d5) will increase coverage by 0.01%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master     #681      +/-   ##
==========================================
+ Coverage   41.66%   41.68%   +0.01%
==========================================
  Files         335      335
  Lines       24403    24415      +12
==========================================
+ Hits        10168    10177       +9
- Misses      14235    14238       +3

Flag
Coverage Δ

unittests
41.68% <75.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

dbaas/maintenance/tasks_create_database.py
12.67% <0.00%> (-0.19%)
:arrow_down:

dbaas/workflow/steps/util/volume_provider.py
43.70% <0.00%> (-0.04%)
:arrow_down:

dbaas/physical/models.py
75.23% <88.88%> (+0.14%)
:arrow_up:

dbaas/physical/admin/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b7906d5...16cf565. Read the comment docs.


SLSA Badge

📋 Description
https://slsa.dev/images/gh-badge-level3.svg
https://slsa.dev/images/gh-badge-level{1,2,3,4}.svg

🔗 Data
No data
🎤 Motivation
https://slsa.dev/

From in the issue template:

This issue template is for suggesting new badges which fetch and display data from an upstream service. If your suggestion is for a static badge (which shows the same information every time it is requested), it is already possible to make these. We don't add specific routes for badges which only show static information.


jekyll --version failed

Could not find jekyll-paginate-1.1.0, rake-13.0.6 in any of the sources (Bundler::GemNotFound

(re)install gems giving arch issues with native extensions
gem uninstall sassc
gem install sassc -- --disable-march-tune-native
gem uninstall ffi
gem install ffi
Update bundler for good measure
bundle update --bundler
Add webrick because otherwise Jekyll won't run on Ruby 3.0 #8523
bundle add webrick


NETOBSERV-1340: Add operator to "Networking" category in OperatorHub

There is a request to also add Network Observability to the "Networking" category.
See https://github.com/netobserv/network-observability-operator/pull/440 for related details.

/lgtm

@stleerh : I had to revert your previous PR adding to Observability category, as this isn't a recognized category.
Do you know if there is an ongoing change somewhere (OLM?) to create this category? I guess we need first to have this category created before we can add it here - not doing so generates validation failures (unstable downstream builds).
Adding to "Networking" is fine I guess, since this category already exists; you'll need to rebase the PR to fix conflict though

(I resolved the conflict via github)

/lgtm
/approve


Some additions

Hey @LPGhatguy, just wondering why your expectations are for code contributions. I'm guessing I need tests at least, what else would you say I need to add features like the below? I'm happy to do the legwork.
I really just did the minimal to make it work for me for the moment.

Coverage decreased (-0.6%) to 96.866% when pulling 1c383d143ffaf1db5d8ffd3de3006aed8a12d22c on kbarber:btk-changes into b8066e7c8bdf3fd0a01162bd15d7a716f0192b34 on LPGhatguy:master.

Thanks for the PR!
It's probably about time to write up a contributor guide for this repository, so that my expectations are a little more clear. I Set up some small guiding ideals in the README, but I don't think that's enough.
I'd like to keep individual PRs smaller in scope since they become easier to review and I can merge them a lot faster. I think this PR could probably be broken into:

MarketplaceService stub
Vector3 and Vector3Value
BasePart/Part
UITextSizeConstraint
Other miscellaneous UI changes

I don't want to implement deprecated or quasi-deprecated features, which would probably include ButtonStyle. From the point of view of Lemur, I think it's safe to pretend they don't exist 😄

@LPGhatguy agree on not using deprecated props, and I'll find some time to break up the PR, that literally is just my dev branch while I prove it all out. Give me some time, I'll find my way back soon.
This instance/class creation feels very laborious, how can we automate this? Can we scan the existing lib and dumps out these instead somehow? Maybe we could just code generate it from the cores metatable/table data - like protobufs.

Eventually, Roblox is going to have a nice JSON format for dumping object metadata that we can use to scaffold out a lot of the API. In the meantime, there isn't any useful type information or default value information we can effectively scrape, sadly. :(


Can't set ModuleDependencyAnalyzer log level

When trying to debug which modules are being transmitted, setting
lithops:
  log_level: DEBUG

doesn't show any messages from ModuleDependencyAnalyzer.
This doesn't seem to work either (in an example script):
logging.getLogger("multyvac.dependency-analyzer").setLevel(logging.DEBUG)

Should the logger in ModuleDependencyAnalyzer be changed to be like the other ones in Lithops?

@JosepSampe any thoughts?

Checking it

#994 Should be enough to show the logs from the module_dependency.py at the same level set in Lithops


CR-8211-2

Codecov Report

Merging #192 (8a42b72) into main (2534d05) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #192   +/-   ##
=======================================
  Coverage   24.86%   24.86%
=======================================
  Files           1        1
  Lines         189      189
=======================================
  Hits           47       47
  Misses        136      136
  Partials        6        6

Impacted Files
Coverage Δ

pkg/config/config.go
24.86% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7897481...8a42b72. Read the comment docs.

/e2e


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/opstest2/docs-archive-test-source.git

Docs Build status updates of commit f1c68fc:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RepositoryUnauthorizedWithSourceCommit] Git data access to 'https://github.com/opstest2/docs-archive-test-target' (branch: Release_Archive_main_2022-01-28-03-04-37) is not authorized.. It looks like this might be the first time user: v-alji submitted a pull request to this repo. Before user can run builds in a pull request, he/she can enable 'v-alji' GitHub account in Docs by visiting Docs Portal (https://ops.microsoft.com). After enabling his/her account (v-alji), close and then reopen this pull request to start another build.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Long press on the buttons, assigned as the system volume up/down hotkeys on Qin F21pro, changes the volume but doesn't perform the expected keyboard function.

There are no special buttons for changing volume on Qin F21pro. Usually, the numbers 8 and 0 are used as the volume up/down buttons (could be selected in System > Quick Settings). Until the Volume Up and the Volume Down hotkeys  appeared in TT9 settings everything worked fine. Now a long press on the system volume hotkey leads to a volume change, but not to the expected TT9 keyboard function (entering a number in prediction mode or selecting a character in 123 mode). Changing volume system hotkeys leads only to incorrect functioning of another numeric keys. The only way to use the TT9 keyboard without problems is to disable the system volume control hotkeys, but using this phone without the system volume control hotkeys is inconvenient. Could you do something about it?

At the very beginning the volume keys used to work properly, but they have stopped after a firmware update. Since I have other system hotkeys set, and they don't interfere with TT9, I assumed it is not possible to use the volume keys for anything else, so I haven't investigated the problem.
I doubt it is possible to fix the problem, but let's keep the issue open. I could try to tackle it in the future. Any help is welcome too!

TT9 v17 still works properly on the system firmware updated to version 1.1.6. Probably, this can help to find the bug.

I've tested some older releases and found that this issue appears in v.20. Up to v.19 there were no problems with the volume buttons.

I've reviewed again the changes between v19.0 and v20.0 and I've found the culprit. I must say, this bug is a perfect example how messed up Android is on some phones.
On this phone, the "Shortcut Keys" app checks whether there is a keyboard status icon, in order to disable itself, when any keyboard is active. And in version 20.0, I've removed the icon, which caused "Shortcut Keys" to always take precedence, because it was no longer able to detect TT9 was active.
I'll just create another hack for this under Initial Settings -> Compatibility... :cry:


Pytorch-directml Python 3.9/3.10/3.11 support :)

Hi, there is any plan for supporting python > 3.8 ? :)
Thank you for your amazing work!

Hi @Djdefrag, yes we will be supporting the latest version of pytorch in our next release coming very soon. Thanks!

Thank you!!

I'm looking forward to the next update because I'm using python 3.10 for a machine learning project with pytorch, but i have not any nvidia gpu. so i really need directML! Thank you!

Is there by any chance a definition for "very soon"? Stable Diffusion has lead to an explosion in the use of "hobby" ML. It is the perfect point in time to roll out an updated Pytorch DirectML. It would provide salvation for non-NVidia users and give DirectML a fair shot at being a default option. (Best to do it before Pytorch Vulkan gets a boost and takes it instead or AMD fixes ROCm and people switch to Linux)

@Amblyopius I'd like to know that too...

torch-directml is released with support of python 3.8 - 3.10. Please check out.

when will python3.12 be supported by torch-directml


Colab demo for jax agents not working. Error: "no attribute 'online_network'"

Hi, i tried to study the colab sample linked from: https://github.com/google/dopamine/tree/master/dopamine/jax
This colab sample:
https://colab.research.google.com/github/google/dopamine/blob/master/dopamine/colab/jax_agent_visualizer.ipynb
First issue is easy to fix, you need additional:
!pip install gym[accept-rom-license]
!pip install gym[atari]

to get the atari environments working.
But this issue then exists:

AttributeError: 'MyDQNAgent' object has no attribute 'online_network'
  In call to configurable 'Runner' (<class 'dopamine.discrete_domains.run_experiment.Runner'>)

I am seeing same issue. @kvrban were you able to find a way around it?


Add pre validate hook throw exception during after validation if there is errors

Hi all,
I have an issue with pre validate hook.
If I try to save a document without this kind of hook and a field have an error, no worries, save callback is called with err.
But if I add a pre validate hook, instead to have callback called, it throw an exception.
I posted an issue (2484) about a similar error during model.create.
Thanks.

Hmm can you provide a standalone example that reproduces this? I don't quite understand.

Basically, if I do doc.save(function(err){...}), callback is always called, normal.
But, if I have a pre validate hook (like below) on the model and that during the save, a validator is not valid, instead to go on callback with err that is equal to the error, an exception is thrown.
// Schema
schema.add({field:{type:String, required:true})
...
// Save
doc=new MyDoc();
doc.save(function(err){
}); // Callback is called with err because field is missing and required

// Schema
schema.add({field:{type:String, required:true})
...
// Add pre validate hook
schema.pre('validate',function(next){
  console.log('OK');
  next();
});
// Save
doc=new MyDoc();
doc.save(function(err){
}); // Console.log is done and callback should be called like before, but not, instead, exception is thrown

I didn't precise I use 3.9 version, I don't know if it is the same thing on 3.8

More, from 3.9.5, there is below code on lib/schema.js around line 119. So with taht, there is always a pre validate hook and when I use doc.save with errors, there is always exception instead callback.
So fix this pre validate error will fix save ;)
  this.pre('validate', function(next) {
    delete this.errors;
    next();
  });

I found the issue.
If pre validator is added on a method (save, validate...), orignal method is overwrite by $__registerHooksFromSchema method on lib/document.js.
On this method, at line 1499, you add a reject listener via $__handleReject that emit error event if there is error listener and else, thrown an exception.
If I add a "doc.on('error', function)", event is called and callback too because $__handleReject doesn't no longer thrown an exception.
I don't know if it is a good fix, but I did below changes on lib/document
      if (typeof lastArg == 'function') {
        wrapingPromise.onResolve(lastArg);
      }
      if (!(this instanceof Embedded) && !wrapingPromise.hasRejectListeners()) {
        wrapingPromise.onReject(self.$__handleReject.bind(self));
      }
      args.push(function () {
        return wrapingPromise.resolve.apply(wrapingPromise, arguments);
      });

to
      if (typeof lastArg == 'function') {
        wrapingPromise.onResolve(lastArg);
      }
      args.push(function () {
        if (!(this instanceof Embedded) && !wrapingPromise.hasRejectListeners()) {
          wrapingPromise.onReject(self.$__handleReject.bind(self));
        }
        return wrapingPromise.resolve.apply(wrapingPromise, arguments);
      });

With that, it give possibility to add reject listener on the promise and that fix pre validate error.

Thanks for the detailed report, that'll help me a lot in fixing this

I'm experiencing the same issue. Quick code to reproduce:
var mongoose = require('mongoose');

var schema = mongoose.Schema({
  name: { type: String, required: true }
});

var User = mongoose.model('User', schema);

new User({ name: 'user' }).validate().then(function () {
  console.log('works ok');

  new User().validate().then(null, function (err) {
    console.log('this error callback is not called, an exception is thrown instead');
  });
});

Hi,
I tried the last release (4.0.0-rc1), and it works now. So I think this issue is fixed in 4.0.0

Actually, this doesn't happen at all in 3.8.x, this was introduced in 3.9.1 and went away thanks to some unrelated work in 4.0.0-rc0. Thanks for pointing this out :)


Allow non-ascii characters in filepath on Windows

This PR fixes Issue #525 and allows 2ship to properly launch when there are non-ascii characters (such as þ) in the file path. I'm not sure if this was a Windows-only problem, but Windows is the only thing I can test.
I'm not sure if I put the changes in the best spot (src > code > main.c), so I'm open to moving those lines somewhere else if it's more appropriate.
Before:

After:

Build Artifacts

2ship-linux.zip
2ship-mac.zip
2ship-windows.zip

I've tried to do some reading around this and other options. I found two main links from Microsoft about this:

setLocale https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/setlocale-wsetlocale?view=msvc-160#utf-8-support
App Manifest changes https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page

Both achieve similar goals in different ways. The manifest one "feels" like a better approach in the sense that UTF-8 is enabled the moment the program executes, where as setLocale isn't valid until it is called in code at runtime. However, the manifest change requires users to be on a specific version of Windows to leverage it, where as setLocale can be statically linked so that it supports more Windows versions.
Considering you call setLocale basically as early as possible, I think it would probably be safe to just try this first and see if user reports die down.


Setup FOCA boilerplate

Add tesk/config.yaml, following the basic structure of other FOCA apps, e.g., proTES and Cloud Registry.
For the OpenAPI specification, make sure to include the latest TES release 1.1 (commit 117cd92; direct link to specification corresponding to the tagged commit).

Note: The changes from TES 1.0 to 1.1 are not very substantial. Given that the majority of code changes required for the 1.1 upgrade are likely required in the API and the API code needs to be re-implemented anyway, it makes sense to develop against version 1.1 right away.

add tesk/config.yaml, following the basic structure of other FOCA apps

So what will the structure look like, I thought initially api code will be in a separate dir, ie tesk/api. Let me know what makes sense here.
Str 1
Create a separation with api inside tesk
.
.
├── tesk
│   ├── api
│   │   ├── specs
|   │   │      ├── task_execution_service.openapi.yaml (exact copy of commit 117)
│   │   ├── app.py
│   │   ├── config.yaml
│   │   └── __init__.py
│   ├── __init__.py
│   └── services/
.
.

Str 2
Put all files in tesk.
.
.
├── tesk
│   ├── api
│   │   ├── task_execution_service.openapi.yaml (exact copy of commit 117)
│   ├── app.py
│   ├── config.yaml
│   ├── __init__.py
│   └── services/
.
.

Maybe like this?
.
├── tesk
│   ├── api
│   │   ├── ga4gh
|   │   │   ├── tes
|   │   │   |   ├── controllers.py
│   │   |   |   └── __init__.py
│   │   |   └── __init__.py
│   │   ├── specs
|   │   │   └── task_execution_service.openapi.yaml (exact copy of commit 117)
│   │   └── __init__.py
│   ├── __init__.py
│   └── services/

In this way, if TESK ever adopts other APIs, from GA4GH or otherwise, we will have a nice separation. Not that this is planned, but I wouldn't completely rule it out either.
As briefly mentioned previously, config.yaml I would put in the root or /deployment directory, because it's really just an example config for the app for quick starts that admins would/should modify for their particular circumstances.


Add option existingModule

so it will use an existing module instead of creating a new one.

What's the status on this? I want this :3

no activity from the author in the last 20 days...

Sorry for the delay.
Published to NPM as 0.3.4

@karlgoldstein Thank you for reacting promptly :3 You just made my life a lot easier!


Ruf format attempts to format git related files

Keywords searched: git
When creating a branch with a name that ends in .py, ruff attempts so format it.

Steps to reproduce

Create a branch in git with a name like my-file.py
Run the ruff formatter.
See how it tries to format a git file.

Hehe that's funny. Would you mind sharing your configuration? I wonder if respect-gitignore is on or off

How do I get my configuration?

Do you have a pyproject.toml with a [tool.ruff] section or a ruff.toml in your project? See How to configure Ruff

Oh yeah I remember this happenning to me once, but forgot to report. I don't have respect-gitignore set in any of my projects.

I verified this locally and I can only reproduce this behavior when overriding the exclude setting.
Ruff ignores the .gitignore directory by default because it is part of the default exclude list. You may want to consider using extend-exclude if you want to exclude some directories in addition to the default once.

I'm sharing my pyproject.toml
I'll also take a link into the extend-exclude

@naquiroz  I think you want to use tool.ruff.extend-include instead of tool.ruff.exclude. I think that should fix the problem for you.

I've just replicated this with a ruff.toml that doesn't have an exclude:
Link to the problematic branch name as an example: https://github.com/Avasam/pywin32/blob/Random-testFileTimes-test-failure-in-test_win32file.py/ruff.toml
Permalink for when I inevitably delete that branch from the remote one day: https://github.com/Avasam/pywin32/blob/41efba18976ed93966591109bcc46aa937f1ed8b/ruff.toml


创建流程无默认值导致前端加载不出界面

fix: flow_model has no default data when createFlow.
close #47.

Turbo provides core process-driven capabilities that can be adapted to different front ends. Different front-end products may have different formats, and the default value set here is not compatible with all front-end products. Therefore, when the front-end is processing, it should be compatible with the form of null to ensure that it can be loaded normally, and the structure of the front-end itself can be saved when saving again.


Update sbt-scoverage to 1.8.2

Updates org.scoverage:sbt-scoverage from 1.8.1 to 1.8.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #129 (83c2042) into master (0e3e73f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #129   +/-   ##
=======================================
  Coverage   80.35%   80.35%
=======================================
  Files           6        6
  Lines         112      112
=======================================
  Hits           90       90
  Misses         22       22

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e3e73f...83c2042. Read the comment docs.


Stable V1 release

This is the main pull request for the upcoming V1 release
All changes for the upcoming release should be opened for nightly.
Things to resolve:

[ ] #1
[x] #3
[ ] #6

More large-scale issues:

[ ] Robot server
[ ] Client Controller
[ ] Code uploader

Resolved: https://github.com/DranikiRobotics/arc/issues/3

#6 just emerger

I moved the robot server code to here
Is it done: NO


Suggestion: batch transferring

Would be nice if you can put checkboxes and then do a batch transfer of pokemon with a delay of X (random 5-10 sec?) between each request to avoid getting 401/403 responses.
During the process showing something like: Transferring X of Y. Time remaining: xxx minutes/seconds.

This is possible. I don't think it needs to be in 1.0.0, but it's a nice to have

I think that if batch transferring is implemented, it really needs to be done right. For instance, I think the app should be able to suggest the number of monsters of a particularly species that should be transferred based on how many monsters of that species the user is currently able to evolve. Furthermore, I think the app should suggest the specific monsters that should be transferred using, e.g., the metric I describe in #45.

I like @DanForbes' idea, I think that's eventually where we want to be. However, I'm not opposed to getting this initially implemented with a simpler mechanism.

I think, based on earlier conversations in #50, that this feature request should be closed and not supported. Implementing this feature would allow for operations faster than with the PoGo client itself and thus provide an unfair advantage and possibly raise some red flags (as useful as I find it).

@collinsmith, I agree


No Keys are shown on Amazon ElastiCache Redis

System information:

Operating system (MacOS) 10.15.6 (Catalina)
DBeaver version 7.3.0

Connection specification:

Redis [4.0.10 (Cluster , SSL) Amazon ElastiCache]
Driver Redis/DBeaver default (Jedis)
Do you use tunnels or proxies (SSH, SO (CKS, etc) ? No, direct connection.

Describe the problem you're observing:

Connection looks fine. When testing connection, Server information show "Redis null". In Connection->Databases->cluster-> "Key list" are empty
Tried without cluster and SSL ->skip host name validation , no luck.

Steps to reproduce, if exist:

Create new connection using Redis Driver
Set Host, (point to aws cluster URL), port, password
SSL check option ,Use SSL
Test Connection

Include any warning/errors/backtraces from the logs

Additional information:

RDM works fine.

Thank you for the bug report.

Still an issue with DBeaver Enterprise v21.2.0....

i had the same thing (Server information show "Redis null")
I was using  (ibm cloud) but might be the same
I disabled cluster and checked "Use SSL" , i just provided my CA Certifcate and could connect

Seeing similar behavior with Amazon MemoryDB on latest DBeaver EE (<IP_ADDRESS>112052011). Connection is fine when "Cluster" mode is checked, but Key list and Key hierarchy are empty and trying to execute e.g. GET <key> returns

Custom Redis commands not supported in cluster mode

https://github.com/dbeaver/dbeaver-ee/pull/1635

@IllusionaryX Hi, it looks like a different issue. Is it possible to create a new issue with the mentioned information?


[fix] #3269 Router not working in production

This PR fixes #3269, once you import $app/navigation on multiple places inside your app and it's included inside chunks/vendor.js the router would be set before the init function is called and would always be undefined.
Current Bundle:
/// vendor-c70aba79.js
let router$1;
function init(opts) {
  router$1 = opts.router;
}
/// ....
const router = router$1; // Router is undefined and doesnt change on init call
const goto = goto_;
const invalidate = invalidate_;
async function goto_(href, opts) {
  return router.goto(href, opts, []);
}

New Bundle:
let router;
function init(opts) {
  router = opts.router;
}
const goto = goto_;
const invalidate = invalidate_;
async function goto_(href, opts) {
  return router.goto(href, opts, []);
}

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Don't know why the test is failing seems not related to this change.

I don't understand how this PR changes anything. If the router is not present when init is called, won't that still be the case?
Also, I'm not sure if it helps, but Vite is removing the vendor chunk: https://github.com/vitejs/vite/pull/6534

The router const is assigned with the undefined router$1 and the init call only reassigns the router$1 with the actual router. But the const router stays always undefined. This PR removes the const so the reassignment in init works as expected.


Basic support for LogLevel

May resolve #54

@byxorna : Updated !

I wonder if defining a log_crit(), log_emerg(), log_info() would be better than passing another parameter.  What do you think?

I'd honestly prefer a single log method. For backends that don't support severity, it doesn't make sense to have many copy pasted methods for log_crit and log_warn when critical and warning don't even make sense for this fictional logging system. Optional parameters keep api surface lean and understandable imho

lgtm


Cannot read property 'labelColor' of undefined

hi
i installed the package using yarn
but got this error

version i'm using  :
"react-native-speedometer": "^1.0.2",
thank you a lot for helping me ! :-)

Hello @ph98 ,
Can you post the code that you implemented using this package?
Thanks

i also see that there is an error in import statement

i used this code ( tried with and without props ) :
`
<RNSpeedometer value={this.state.temp} size={200}
        defaultValue={50}
        minValue={0}
        maxValue={100}
        easeDuration={500}
        labels= {[{
          name: 'Pathetically weak',
          labelColor: '#ff2900',
          activeBarColor: '#ff2900'
        }, {
          name: 'Very weak',
          labelColor: '#ff5400',
          activeBarColor: '#ff5400'
        }]}

    />
  </SafeAreaView>`

Here's a working snack expo link with the almost same code, not sure what might be wrong with your code

Please run this code:
`import * as React from 'react';
import { TextInput, View, StyleSheet } from 'react-native';
import RNSpeedometer from 'react-native-speedometer';
export default class App extends React.Component {
state = {
value: 100,
};
onChange = value => this.setState({ value: parseInt(value) });
render() {
return (

<RNSpeedometer value={this.state.value}
size={200}
defaultValue={50}
minValue={50}
maxValue={100}
easeDuration={500}
labels= {[{
name: 'Pathetically weak',
labelColor: '#ff2900',
activeBarColor: '#ff2900'
}, {
name: 'Very weak',
labelColor: '#ff5400',
activeBarColor: '#ff5400'
}]}
/>

);
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
},
textInput: {
borderBottomWidth: 0.3,
borderBottomColor: 'black',
height: 25,
fontSize: 16,
marginVertical: 50,
marginHorizontal: 20,
}
});
`

Please run this code:
import { TextInput, View, StyleSheet } from 'react-native';
import RNSpeedometer from 'react-native-speedometer';

export default class App extends React.Component {
  state = {
    value: 100,
  };

  onChange = value => this.setState({ value: parseInt(value) });

  render() {
    return (
      <View style={styles.container}>
        <TextInput placeholder="Speedometer Value" style={styles.textInput} onChangeText={this.onChange} />
        <RNSpeedometer value={this.state.value}
        size={200}
        defaultValue={50}
        minValue={50}
        maxValue={100}
        easeDuration={500}
        labels= {[{
          name: 'Pathetically weak',
          labelColor: '#ff2900',
          activeBarColor: '#ff2900'
        }, {
          name: 'Very weak',
          labelColor: '#ff5400',
          activeBarColor: '#ff5400'
        }]}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
  },
  textInput: {
    borderBottomWidth: 0.3,
    borderBottomColor: 'black',
    height: 25,
    fontSize: 16,
    marginVertical: 50,
    marginHorizontal: 20,
  }
});

You will get the same error mentioned above.

Thanks,
I'll take a look as soon as possible.
On Wed, Aug 7, 2019 at 4:40 PM bilalseh<EMAIL_ADDRESS>wrote:

Please run this code:
import { TextInput, View, StyleSheet } from 'react-native';
import RNSpeedometer from 'react-native-speedometer';
export default class App extends React.Component {
state = {
value: 100,
};
onChange = value => this.setState({ value: parseInt(value) });
render() {
return (

<RNSpeedometer value={this.state.value}
size={200}
defaultValue={50}
minValue={50}
maxValue={100}
easeDuration={500}
labels= {[{
name: 'Pathetically weak',
labelColor: '#ff2900',
activeBarColor: '#ff2900'
}, {
name: 'Very weak',
labelColor: '#ff5400',
activeBarColor: '#ff5400'
}]}
/>

);
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
},
textInput: {
borderBottomWidth: 0.3,
borderBottomColor: 'black',
height: 25,
fontSize: 16,
marginVertical: 50,
marginHorizontal: 20,
}
});
You will get the same error mentioned above.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pritishvaidya/react-native-speedometer/issues/3?email_source=notifications&email_token=AEYFRTNW67NBHAFUOTCUVY3QDKUTLA5CNFSM4G3I6WO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3YBR4A#issuecomment-519051504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEYFRTKJU6MRRFYFGHITWM3QDKUTLANCNFSM4G3I6WOQ
.


Tiled Geosearch/Geoahashed aggregation : return an empty featureCollection when a tile/geohash is disjoint from pwithin bbox

In gitlab by @MohamedHamouGisaia on Oct 3, 2017, 17:36

In gitlab by @MohamedHamouGisaia on Oct 3, 2017, 17:38
changed title from {-When a tile/geohash is disjoint from pwithin bbox, return an empty featureCollection-} to {+Tiled Geosearch/Geoahashed aggregation : return an empty featureCollection when a tile/geohash is disjoint from pwithin bbox+}

In gitlab by @MohamedHamouGisaia on Oct 3, 2017, 17:40
mentioned in commit<PHONE_NUMBER>955c8bb52a0aabc58065f50fab55dc

In gitlab by @MohamedHamouGisaia on Oct 3, 2017, 17:40
mentioned in merge request !101

In gitlab by @mbarbet on Oct 4, 2017, 12:18
reopened

In gitlab by @mbarbet on Oct 4, 2017, 12:21
This fix doesn't work if the longitude of the top left corner is greather than the longitude of the bottom right. In this case we never return any feature. example : bbox from china to france

In gitlab by @MohamedHamouGisaia on Oct 6, 2017, 17:05
mentioned in commit 23a5825de75b1831c0fcd3a9f703c36390630161

In gitlab by @MohamedHamouGisaia on Oct 6, 2017, 18:13
mentioned in commit 7ec1bf365407a3980d31c2b89235ed8a72e6e47b

In gitlab by @MohamedHamouGisaia on Oct 9, 2017, 09:40
mentioned in commit 256624026ec7d235a6e404bb65571ffc53f14500

In gitlab by @MohamedHamouGisaia on Oct 9, 2017, 09:54
mentioned in merge request !103

In gitlab by @sylvaingaudan on Oct 9, 2017, 10:02
closed via merge request !103

In gitlab by @sylvaingaudan on Oct 9, 2017, 10:34
mentioned in commit 4e05b66e29053efd93d8536a8588c17e88d5332b

In gitlab by @sylvaingaudan on Oct 9, 2017, 10:34
mentioned in commit 5db89288e58afd83df69f097b9cf825cbbbd3cf4


Automaticly disable high availability mode for 1 replica alertmanager

AlertManager in a single-node setup will try to broadcast silences and notification logs to itself. The messages are queued forever, leading to the error message when it reaches the max queue size.
More info

https://github.com/prometheus/alertmanager#high-availability
https://github.com/prometheus/alertmanager/issues/1814

Fixes #3196

Looks like there are some problems in CI

@brancz fixed

Thanks a lot!


Add ability to display the version as a footnote

I thought this could be an interesting little addition, that's why I added it.
Feel free to make the changes you seem necessary.

Hi @Tibimac,
Thanks for your PR! 👍
Adding a footer / footnote below the buttons is a great idea.
However, in my opinion the implementation should be more flexible to support various views, not only a version number, as use cases may vary.
What do you think?

@SvenTiigi if you have other cases in mind feel free to adjust the implementation for more various cases, now or later. It may be interesting to add this use case now and add more flexibility in a future addition. WDYT ?

Merged in feature/footer branch


Uncaught TypeError: ng_bootstrap_ng_bootstrap__WEBPACK_IMPORTED_MODULE_2_.NgbPopoverModule.forRoot is not a function

Simply adding the following to app.module.ts causes the Uncaught TypeError.
import { TourNgBootstrapModule } from 'ngx-tour-ng-bootstrap';
TourNgBootstrapModule.forRoot(),
Uncaught TypeError: ng_bootstrap_ng_bootstrap__WEBPACK_IMPORTED_MODULE_2_.NgbPopoverModule.forRoot is not a function
at Module../node_modules/ngx-tour-ng-bootstrap/fesm2015/ngx-tour-ng-bootstrap.js (ngx-tour-ng-bootstrap.js:182)
at webpack_require (bootstrap:79)
at Module../src/app/app.module.ts (app.component.ts:10)
at webpack_require (bootstrap:79)
at Module../src/main.ts (main.ts:1)
at webpack_require (bootstrap:79)
at Object.0 (main.ts:12)
at webpack_require (bootstrap:79)
at checkDeferredModules (bootstrap:45)
at Array.webpackJsonpCallback [as push] (bootstrap:32)
I'm running the following versions.
Angular CLI = 8.1
TypeScript = 3.4.5
WebPack = 4.35.2
Any help is much appreciated. Thanks!

I am running into the same error. , looks like if you remove .forRoot() it kinda works. But then there is still an error when clicking start twice or clicking next to the popup. Also reproducible in the demo page of ng-bootstrap implementation. Clicking twice throws this error:
main-es2015.83a5758b6d0fd81ebc2f.js:1 ERROR TypeError: Cannot read property 'step' of undefined
But nice library btw

Fixed in<EMAIL_ADDRESS>

@isaacplmann Could you publish 5.0.0 on npm?

Any plans on publishing it?


Move loop register into BlockAnnotations

convert_bhive_to_llvm_exegesis_input before this patch stored the loop_register separately. Having the annotators add the loop register to the annotations gives more flexibility down the line for exactly specifying how the block was executed in the annotator/should be benchmarked. Additionally, a register chosen for use as a loop counter is fundamentally an annotation, so placing it there makes more sense from the abstraction perspective.

This is a stacked PR on top of #165.


how config client change configuration value

I see spring-cloud-config-client-.1.4.5.RELEASe source code. I think the flow is:
1ConfigClientWatch
2ContextRefresher
3ConfigurationPropertiesRebinder
ConfigurationPropertiesRebinder.rebind(String name) method will recreate  bean  and new configuration value will be inject into bean.  I don't  really know where configuration values are changed in Environment.   I think may be in ContextRefresher.addConfigFilesToEnvironment().
if (target.contains(name)) { 	target.replace(name, source); }
But it is wired, target and source are from the same context, and no configuration from remote config server.

I am not sure what the question is, can you elaborate?

Embarrassed. Could you give an architecture guide for configserver.


ensure python versions are sorted

We may want to add a build step to automatically populate SUPPORTED_PYTHON_VERSIONS.
We will need to provide a custom comparison function if we want to non-uniform version numbers (e.g. 3 and 3.9.5).

Could someone link the issue? I want to reproduce to ensure the issue is actually fixed. 😆

@0x00b1 I think the order is messed up because we're using Object.entries() in the React component. The array SUPPORTED_PYTHON_VERSIONS is technically already sorted, but the result of Object.entries() is not guaranteed:
https://github.com/chanzuckerberg/napari-hub/blob/75e867e90878e48cec4b2d0382cb8c9acfa76e17/client/src/components/PluginSearch/PluginFilterByForm.tsx#L67-L74

hey @0x00b1 do you think you can land this or should @codemonkey800 or @kne42 pick it up?

Previous Behavior:
The order of the array returned by Object.entries() does not depend on how the object is defined.
Current Behavior:
The ordering of the properties is the same as that given by looping over the property values of the object manually.
PR Updating the Docs:
https://github.com/mdn/content/pull/6937


Client generation with required sanitization

Purpose
Client generation with required sanitization for jira connector. Related to #7035
Examples
Checklist

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

I'll close this PR as this PR https://github.com/ballerina-platform/module-ballerinax-jira/pull/3 contains all the necessary code.


chore(Algebra/Polynomial/Degree): split Definitions.lean

This file was very big and contained many more things than just the definitions of Polynomial.degree et al. This PR splits off the following files:

Degree/Operations.lean: lemmas to compute the degree for various ring operations (this is probably the file to import if you're missing something after merging this PR)
Degree/Domain.lean: Polynomial.instIsDomain instance and its consequences
Degree/Monomial.lean: lemmas to compute the degree for monomials
Degree/SmallDegree.lean: lemmas where the degree is a specific small number such as 2 or 3
Degree/Support.lean: lemmas about writing polynomials as sum over the support
Degree/Units.lean: lemmas about the degree of units

maintainer merge


Document how to add a new operation

Start with the simple case of adding a new local operation.

Depends on #670


Repo name

Hi all :wave:
What do you think about changing the name of this repo to simply server?
or something really cool like dataflow

Sure! I agree with you. Also, dataflow sounds pretty cool !

agree


Update RunDbtDag's optional upload_artifacts logic to run the increme…

…ntal dbt_artifacts models before running seeds.

One thing to note: the incremental dbt_artifacts models are run twice if upload_artifacts is True: before the seeds, and during the main run step. If not run before seeds, the uploads will fail the first run, as these artifact tables won't exist. The dbt_artifacts models are incremental and empty, only setting/updating the schema of these tables, so they're not computationally-expensive to run twice.


Add missing species

I was missing 3 new species, added back in now.

Polluted from another PR, clsoing and remaking


[multikueue] Retry on remote wl creation failure

What type of PR is this?
/kind bug
/kind cleanup

What this PR does / why we need it:
Retry on remote workload creation failure and extend unit tests with a secondary worker client.
Which issue(s) this PR fixes:

Relate to #693
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/retitle [multikueue] Retry on remote wl creation failure
I think the part about extending unit tests is not that important for the title, the assumption is that every change extends tests

/hold for nit

done
/unhold

/lgtm


Fix initialization of index_array

index_array should be initialized when self.batch_index is zero.

This will crash if flow is called when self.batch_index is not 0 (i.e. if you are reusing the same generator more than once, which is common).

This will crash if flow is called when self.batch_index is not 0

I don't think so, because:

self.batch_index is initialized when flow is called in the first time.
https://github.com/fchollet/keras/blob/master/keras/preprocessing/image.py#L278
index_array is initialized when flow is called in the first time, and index_array persists in the scope (i.e. _flow_index).
https://github.com/fchollet/keras/pull/2590/files#diff-93850fa46a789f2e5905894ad0e7bee4R253
self.batch_index is incremented as flow is called.
https://github.com/fchollet/keras/blob/master/keras/preprocessing/image.py#L262
If N < current_index + batch_size is true, self.batch_index will be set 0.
https://github.com/fchollet/keras/blob/master/keras/preprocessing/image.py#L265

In other words, self.batch_index loops from 0 to N / batch_size, and index_array is initialized at an appropriate timing (i.e. index_array persists in _flow_index).

No, with the modification you made, if flow is called when self.batch_index is not 0 (i.e. if flow is called twice with the first time only flowing for n < N) then index_array is not initialized, causing the program to crash. Just try it...

I agree with @henry0312, the change to the order of initialization of the index_array is causing incorrect behavior:
gen = image.ImageDataGenerator()
q = gen._flow_index(16, batch_size=5, shuffle=True)
print(next(q)[0])
print(next(q)[0])
print(next(q)[0])
print(next(q)[0])
print(next(q)[0])

produces:
[ 5  0  7 10 14]
[5 6 7 8 9]
[10 11 12 13 14]
[15]
[ 8  3 11  7 15]

Note that after the first next() call the array is reinitialized to the un-shuffled range.
While the previous version was correctly not reinitializing the index_array every time the _flow_index generator was called by next().

I tried.
Before
» ipython
Python 3.5.1 (default, Feb 13 2016, 10:15:45)
Type "copyright", "credits" or "license" for more information.

IPython 4.2.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import keras
Using Theano backend.

In [2]: from keras.preprocessing.image import ImageDataGenerator

In [3]: gen = ImageDataGenerator()

In [4]: q = gen._flow_index(16, batch_size=5, shuffle=True)

In [5]: print(next(q)[0])
[ 5 14  7  9  0]

In [6]: print(next(q)[0])
[5 6 7 8 9]

In [7]: print(next(q)[0])
[10 11 12 13 14]

In [8]: print(next(q)[0])
[15]

In [9]: print(next(q)[0])
[ 2  9 13  4  5]

After
if this PR is adapted,
» ipython
Python 3.5.1 (default, Feb 13 2016, 10:15:45)
Type "copyright", "credits" or "license" for more information.

IPython 4.2.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import keras
Using Theano backend.

In [2]: from keras.preprocessing.image import ImageDataGenerator

In [3]: gen = ImageDataGenerator()

In [4]: q = gen._flow_index(16, batch_size=5, shuffle=True)

In [5]: print(next(q)[0])
[11  1 13  5  2]

In [6]: print(next(q)[0])
[ 6 15  9 10  0]

In [7]: print(next(q)[0])
[12  8  4  3  7]

In [8]: print(next(q)[0])
[14]

In [9]: print(next(q)[0])
[12  2 10  0  9]

In [10]: q = gen._flow_index(16, batch_size=5, shuffle=True)

In [11]: print(next(q)[0])
---------------------------------------------------------------------------
UnboundLocalError                         Traceback (most recent call last)
<ipython-input-11-2a5d870822b2> in <module>()
----> 1 print(next(q)[0])

/usr/local/var/pyenv/versions/3.5.1/lib/python3.5/site-packages/Keras-1.0.2-py3.5.egg/keras/preprocessing/image.py in _flow_index(self, N, batch_size, shuffle, seed)
    265                 self.batch_index = 0
    266             self.total_batches_seen += 1
--> 267             yield (index_array[current_index: current_index + current_batch_size],
    268                    current_index, current_batch_size)
    269

UnboundLocalError: local variable 'index_array' referenced before assignment

This PR will fix the initialization of index_array, however, as @fchollet pointed out, it could lead to cause crashes if flow is called when self.batch_index is not 0
I'll fix it 😀

@MaCaki thanks for your support!

Updated

If the desired behavior is for the image generator to completely reset ( batch_index=0, index_array reinitialized) each time flow() is called, then could you just do that before the while loop in the generator:
    def _flow_index(self, N, batch_size=32, shuffle=False, seed=None):
      + index_array = np.arange(N)
        while 1:
        ...

Since flow() calls reset() before creating another index generator, there doesn't seem to be any issue;
x = np.array([1]*16)
y = np.array([0]*16)
gen.flow(x,y, batch_size=5, shuffle=True)
q = gen.flow_generator
print(next(q)[0])
print(next(q)[0])

gen.flow(x,y, batch_size=5, shuffle=True)
r = gen.flow_generator
print(next(r)[0])
print(next(r)[0])

gives
[11  8 12 10  0]
[14 15  4  1 13]
[ 7  8 10  9 14]
[12  5  2  0  6]

@MaCaki I think you are almost right (also, I think so. cf. https://github.com/fchollet/keras/pull/2590#issuecomment-216723917), but not all of the users use flow.
Some users may call _flow_index directly...

@henry0312
Well as a 'weakly internal' function shouldn't some risk be tolerated?
And even if it's called directly, it won't crash, it just won't reset batch_index=0.  If this is the desired behavior, then I see no issue with just doing:
 def _flow_index(self, N, batch_size=32, shuffle=False, seed=None):
      + index_array = np.arange(N)
      + self.batch_index = 0
         while 1:

or, if someone really wanted to use a _flow_index() generator independently of the image generator, they could just call reset() on the ImageDataGenerator object first.

okay, updated again.

Added a test case for _flow_index

Updated

The test is incorrectly written and therefore tests are failing.

I re-read the PR, and it doesn't make any sense to me.

the "new" behavior of flow is 100% identical to what it is was before.
the test is testing something that is never meant to be used (a specific private method that is actually a utility function of the public flow method, which itself is tested as part of the ImageDataGenerator test.

@fchollet I don't think that the behavior of flow is identical. Here is what's happing under the current master:
# current master
x = np.asarray([ [[[i]]*4] for i in range(16)])
y = np.array([1]*16)

gen = image.ImageDataGenerator()
gen.flow(x,y, batch_size=5, shuffle=True)
for i in range(4):
    batch = next(gen)[0].transpose()[0][0]
    print("batch {:d}: {}".format(i, str(batch)))

gives
batch 0: [[  2.   9.  13.   7.   6.]]
batch 1: [[ 5.  6.  7.  8.  9.]]
batch 2: [[ 10.  11.  12.  13.  14.]]
batch 3: [[ 15.]]

I'm printing out the labeled elements of a simpulated batch.  Note that after the first batch the generator is no longer shuffling, because the index_array keeps getting reset.  Consequently, the generator will repeat images, or omit them during an epoch of training. Does this test miss something that is happening in practice?
After simply moving the initialization index_array = np.arange(N) to before the while loop, the behavior is correct:
batch 0: [[  2.   7.   3.  11.   4.]]
batch 1: [[ 14.  13.  12.  10.   8.]]
batch 2: [[  1.   0.  15.   5.   6.]]
batch 3: [[ 9.]]

I fail to see how this is identical.

Are you serious?😲
Please check carefully:

https://github.com/fchollet/keras/pull/2590#issuecomment-217072816
https://github.com/fchollet/keras/pull/2590#issuecomment-217292824
https://github.com/fchollet/keras/pull/2590#discussion_r61984214

https://github.com/fchollet/keras/pull/2590#issuecomment-217279599

the test is testing something that is never meant to be used (a specific private method that is actually a utility function of the public flow method, which itself is tested as part of the ImageDataGenerator test.

Do I just remove test codes?

Do you mean I just remove test codes?

Yes please. I don't think they serve any purpose atm.

I removed test codes.

Thanks, merged.


BREAKING(log): remove NOTSET LogLevel

Changes
This PR removes the NOTSET LogLevel.
Reasoning
Instead of NOTSET loggers should be initialized with the default set LogLevel (which is INFO).

The log module is not stable, so breaking changes for v1 should not be a dealbreaker imo.
To me this seems to be a question of principal: Does NOTSET as a loglevel make sense in the ts/js context? I would argue no. WDYT?

The created logger doesn't have any handler. It means the logger doesn't do anything. I wonder if this change would impact the user in any meaningful way..


Update the twitter logo to X

Solves #48

@Priyanshu-su30 please, rebase your branch on main to fix the deploy issue


filtering by 66%

Some info around this logic.
Currently in the bulk ui, we return sets of 5.
The percentage shown is a percentage within the set of 5 eg:
score = (document score/max(score in set of 5)) * 100.
This is still being shown.
Under the hood of the UI we do some filtering.
We calculate another column under the hood which is:
under the hood score =(document score/max(score of the full results across sets)) * 100.
We then take under the hood score and filter it if it's greater than or equal to 66%.
This is to remove relatively bad match results.


Rellax + Nuxt: wokrs at page load, not at page change/transition

Not sure if off-topic, but I'm not sure where to ask for support, so I try here :)
Rellax seems not working on a Nuxt application when I pass from one page to another.
I mean: my Nuxt application is made by 2 pages, call them A and B.
I've added Rellax as a global plugin.
I put a small Rellax animation on both pages A and B.
If I load directly page A, all good.
If I load directly page B, all good.
But if I call page A and then page B (clicking on link from page A to B), Rellax is not working anymore (and no console error or warnings.)
I guess it's related on how Nuxt handles page transition/changes and probably destroy or not re-init Rellax.
I've used different times Nuxt and loaded plugins as global ones (on client side), this is the first time I experience a similar issue.
Anyone could support me?

Where are you initializing rellax in vue?
If you initialize rellax on the mounted hook you should be all good. ``
export default {
...
  mounted() {
    // eslint-disable-next-line
    const rellax = new Rellax(this.$refs.parallaxImg)
  }
}
...

Hope this helps.

Thanks for the tip, it works :)


Basic tutorial

When running the Basic Tutorial, I get an error when I try to load the data from Zenodo:
Tomo_Alps_full = load_GMG("https://zenodo.org/records/10738510/files/Paffrath_2021_SE_Pwave.jld2?download=1")

┌ Warning: type JLD2.SerializedDict does not exist in workspace; reconstructing
└ @ JLD2 ~/.julia/packages/JLD2/IsVcY/src/data/reconstructing_datatypes.jl:605
ERROR: MethodError: Cannot `convert` an object of type JLD2.ReconstructedMutable{:SerializedDict, (:kvvec,), Tuple{Any}} to an object of type Dict{String, String}

To me, this seems to be rather JLD2 related, but as it occurs in the first line of the basic tutorial, I thought it'd be good to see why this happens. Anybody else had that issue?

I agree that this should work as it is very discouraging otherwise.
This works fine for me:
julia> using GeophysicalModelGenerator
julia> Tomo_Alps_full = load_GMG("https://zenodo.org/records/10738510/files/Paffrath_2021_SE_Pwave.jld2?download=1")
GeoData
  size      : (162, 130, 42)
  lon       ϵ [ -13.3019 : 35.3019]
  lat       ϵ [ 30.7638 : 61.2362]
  depth     ϵ [ -606.0385 : 31.0385]
  fields    : (:dVp_Percentage,)

Few things we can try to do:

Add some of the key tutorials to the CI (for example the ones that go into the JOSS paper)
We often have related failures in the CI system because there are issues with downloading data (happens a lot with ImportTopo and sometimes with load_GMG. We could perhaps add an automatic retrial and try again another few times to see if that is the issue
Is it an issue with your internet speed?

It works for me as well. Perhaps using an old JLD2 version? I'm on 0.4.46

I had used v0.4.45 for that. I did an update and now it worked. It does seems weird though as I would not thinkf that these two version should differ by that much. It could be related to downloading data. However, internet speed should not be that bad I think. In any case, it works now. I'll see if it fails again when retrying and reopen the issue if necessary.

Note the PR #94 does several download attempts which seem to have largely resolved the issue with CI/CD


Support configuring PingFederate Identity Provider with Rancher's Shibboleth Service Provider

Rancher's Shibboleth access control uses an external go-saml library. Shibboleth and Ping are different implementations of saml. Rancher's access control had only been tested with Shibboleth Identity Provider. For Ping Identity Provider, the integration would return these errors:
Caused by: com.pingidentity.common.util.xml.InvalidXmlException: Invalid XML - errors: [error: cvc-complex-type.2.1: Element 'NameIDPolicy@urn:oasis:names:tc:SAML:2.0:protocol' with empty content type cannot have text or element content.]

and
2017-05-03 23:50:52,685 tid:WktR2mAgSdliSfeYuW1le459MpA ERROR [org.sourceid.saml20.profiles.idp.HandleAuthnRequest] Exception occurred during request processing
org.sourceid.saml20.profiles.StatusResponseException: ProtocolBinding:  disallowed for transport of SSO response.

These were because of the external go-saml library being used.
The first error of invalidXMLException was fixed changing the NameIDPolicy struct's field tags.
For the second error, a field called ProtocolBinding was added to a struct called AuthnRequest.
The referenced PR contains Rancher's fork of the saml library having the above fixes.

@mrajashree Please start working with @sangeethah or @soumyalj on the testing scenarios

Per @vincent99 the UI should be updated to show that it supports Ping Identity. @mrajashree follow up with @vincent99 on this. The feature shouldn't be considered done until that's updated (but obviously can be tested without that change)

I did a validation test pass on the PingFederator auth service, all the test cases passed and will be written in  #8845


Overdue Tasks

Hi,
I saw the earlier enhancement post (#71) where the duplicate overdues are mentioned. I partially agree with the solution suggestion.  Depending on which calendar view you use you will oversee overdue tasks due to this. I use the weekly view and overdue tasks from last week are not displayed anymore. Sure I can manually drag them now, but the risk of forgetting something persists.
I think the standard behaviour should be to display overdue tasks only on today's date, therefore avoiding duplicates and the risk of overseeing/forgetting to drag a task. #71's suggestion should be kept as an additional option though - this way we can drag selected overdue tasks to some point in the future (though this was something that I was doing simply by changing the deadline/schedule).
Let me know what you think! Cheers

Thanks for the feedback, dashboard and sidebar will always show overdue tasks to avoid omission. Will this meet your needs?

It's true that overdue tasks are shown in the dashboard, but don't you think there should also be some overview in the calendar view? I personally only use the calendar view, that's why I ask, but of course the dashboard does the job.


[GLUTEN-6887][VL] Daily Update Velox Version (2024_09_29)

Upstream Velox's New Commits:
42940c8bb by Pedro Eugenio Rocha Pedreira, Properly report lazy loaded inputBytes (11097)
d5fb0d8bd by Xiaoxuan Meng, Remove the task from the task list at the end of task destruction (11117)
97bf4db80 by rui-mo, Enable decimal fuzzer test in experimental workflow (10948)

@JkSelf seems it has a conflict, unit tests are not running


add delete list: ‘/Library/Application Support/CleverFiles’ for uninstall Disk Drill’

there was un-delated files when uninstall Disk Drill app even using zap.
i add the files to delete list.

Thank you for the contribution. It was merged directly as f5f45a807d9a5ba956594d27b114442c8ef41996 to keep commit history cleaner. Your contribution is still credited to you.


Module parse failed: Unexpected token

Hi there!
Trying to run NODE_ENV=production node build/build.js  and got this error
ERROR in ./node_modules/vuetify-image-input/index.js
Module parse failed: Unexpected token (1:16479)
You may need an appropriate loader to handle this file type.

Using this env:

node: v14.19.1
yarn: 1.22.18
"vuetify-image-input": "^19.2.2",
"vuetify": "^2.6.4",

Any ideas?
Thanks a lot!

Webpack.. in this case I ended up removing the module, it actually wasnt been used in the project..
You can close if u wish!
thanks


Downgrade to 2.12.3 to avoid infinite loop.

I tried to track down what is causing the infinite loop in completions but haven't been able to nail down exactly what it is except that downgrading to 2.12.3 seems to fix the issue.

Pending fix in https://github.com/scalameta/scalameta/pull/1184 still gonna merge to fix master now, won't have time to get that PR into a release until


What is "period"

Yo

period is the number of seconds to be watching if there's more than max_calls calls on the function.

period is the number of seconds to be watching if there's more than max_calls calls on the function.

Thanks bro


Enable Light Adjustment settings doesn't keep its settings upon restart

Type of Error
Incorrect Behaviour
Description
All of the settings will always set to their default initial states upon startup. I am running Quilt 0.19.1 on Minecraft 1.20.1. It's a bit of a hassle to change them everytime I boot up Minecraft.
Mod Version
dynamic-fullbright-1.0.1.jar
Minecraft Version
1.20.1
Mod Loader
Quilt
Steps to Reproduce
1. Launch Minecraft
2. Go to Mods -> Dynamic Fullbright settings
3. Modify settings
4. Re-launch Minecraft
5. Settings are back to their default states

Crash Log
No response

I tried recreating the issue as described, but everything is working as intended for me. I'll need some more information to so I can solve the problem:
Are all of the settings failing to save, or is it only the Enable Lighting Adjustment option?

I tried recreating the issue as described, but everything is working as intended for me. I'll need some more information to so I can solve the problem: Are all of the settings failing to save, or is it only the Enable Lighting Adjustment option?

My bad, upon further testing it seems like my initial report was correct. Only the Enable Lighting Adjustment option is affected. Everything else saved fine.
I dug a little bit further and found the config file and I think I understand why the option isn't saved.
dynamic-fullbright.json
{
	"separate entity lighting": false,
	"scaling": true,
	"min block": 3,
	"max block": 15,
	"min entity": 3,
	"max entity": 15,
	"min sky": 3,
	"max sky": 15
}

It seems like the option for the Enable Lighting Adjustment isn't there. Even though I have set it to "Yes" in the in-game mods settings.


Why does deserializing slightly different structs from the same bytes work?

I have two similar types that I ser/de with bincode:
pub type SstIndex = BTreeMap<Bytes, IndexVal>;

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct SstMetadata {
    index: SstIndex,
    seq_num: u64,
}

During a refactor I realized that the following deserialization code does not error out:
rdr.seek(SeekFrom::End(offset))?; // rdr is BufReader<File>
let mut buf = vec![0u8; meta_sz as usize];
rdr.read_exact(&mut buf)?;
let meta: SstMetadata = bincode::deserialize(&buf)?;
let index: SstIndex = bincode::deserialize(&buf)?;

I'm wondering why the SstIndex deserialization works? Is this behaviour documented somewhere?
Thanks
EDIT: I went ahead a did a simple reproduction:
use serde::{Deserialize, Serialize};
use std::collections::BTreeMap;

pub type SstIndex = BTreeMap<usize, usize>;

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct SstMetadata {
    index: SstIndex,
    seq_num: u64,
}
fn main() {
    let index: SstIndex = (0..100).map(|i| (i, i)).collect();
    let meta = SstMetadata {
        index,
        seq_num: 0u64,
    };
    let buf = bincode::serialize(&meta).expect("ser failed");
    let index: SstIndex = bincode::deserialize(&buf).expect("deser failed");
    println!("index {:?}", index);
}

cargo run produces:
   Compiling serde v1.0.190
   Compiling bincode v1.3.3
   Compiling bintest v0.1.0 (..)
    Finished dev [unoptimized + debuginfo] target(s) in 7.16s
     Running `target/debug/bintest`
index {0: 0, 1: 1, 2: 2, 3: 3, 4: 4, 5: 5, 6: 6, 7: 7, 8: 8, 9: 9, 10: 10, 11: 11, 12: 12, 13: 13, 14: 14, 15: 15, 16: 16, 17: 17, 18: 18, 19: 19, 20: 20, 21: 21, 22: 22, 23: 23, 24: 24, 25: 25, 26: 26, 27: 27, 28: 28, 29: 29, 30: 30, 31: 31, 32: 32, 33: 33, 34: 34, 35: 35, 36: 36, 37: 37, 38: 38, 39: 39, 40: 40, 41: 41, 42: 42, 43: 43, 44: 44, 45: 45, 46: 46, 47: 47, 48: 48, 49: 49, 50: 50, 51: 51, 52: 52, 53: 53, 54: 54, 55: 55, 56: 56, 57: 57, 58: 58, 59: 59, 60: 60, 61: 61, 62: 62, 63: 63, 64: 64, 65: 65, 66: 66, 67: 67, 68: 68, 69: 69, 70: 70, 71: 71, 72: 72, 73: 73, 74: 74, 75: 75, 76: 76, 77: 77, 78: 78, 79: 79, 80: 80, 81: 81, 82: 82, 83: 83, 84: 84, 85: 85, 86: 86, 87: 87, 88: 88, 89: 89, 90: 90, 91: 91, 92: 92, 93: 93, 94: 94, 95: 95, 96: 96, 97: 97, 98: 98, 99: 99}

SstMetadata has more bytes than SstIndex, so you can deseiralize SstIndex just fine. If you want this to be a runtime error, you can set Options::reject_trailing_bytes
For more information on how the bincode format works you can check the spec

Thank you.


wrong symmetrized Hamiltonian with vasp

Dear WannSymm developers,
I'm currently facing a problem when running the code. I've used Vasp (5.4.1) with the wannier90 interface. I've used the seedame_hr.dat and POSCAR files in order to run wannsymm with the following input:
%%%%%%%%
DFTcode  = VASP
Spinors  = T
SeedName ='wannier90'
Use_POSCAR = 'POSCAR'
begin projections
Pt: s; px; py; pz; dz2; dx2-y2; dxy; dyz; dxz
end projections
nk_per_kpath = 101
begin kpath
X 0.500000  0.000000  0.500000  Y  0.500000  0.250000  0.750000
Y 0.500000  0.250000  0.750000  L  0.500000  0.500000  0.500000
L 0.500000  0.500000  0.500000  G  0.000000  0.000000  0.000000
end kpath
%%%%%%
In the above case I tested Pt with that given projection, however after the running the bands obtained for the symmetrized and original cases don't match. Is there any other flag I'm missing?.
Best regards,

Dear WannSymm developers,
I'm currently facing a problem when running the code. I've used Vasp (5.4.1) with the wannier90 interface. I've used the seedame_hr.dat and POSCAR files in order to run wannsymm with the following input: %%%%%%%% DFTcode = VASP
Spinors = T
SeedName ='wannier90'
Use_POSCAR = 'POSCAR' begin projections Pt: s; px; py; pz; dz2; dx2-y2; dxy; dyz; dxz end projections
nk_per_kpath = 101 begin kpath X 0.500000 0.000000 0.500000 Y 0.500000 0.250000 0.750000 Y 0.500000 0.250000 0.750000 L 0.500000 0.500000 0.500000 L 0.500000 0.500000 0.500000 G 0.000000 0.000000 0.000000 end kpath %%%%%%
In the above case I tested Pt with that given projection, however after the running the bands obtained for the symmetrized and original cases don't match. Is there any other flag I'm missing?.
Best regards,

Change the order of orbitals in the projections block to this one may fix this problem. If the problem is not fixed, please let me know.
begin projections
Pt: s; pz; px; py; dz2; dxz; dyz; dx2-y2; dxy
end projections

The explanation:
In Wannier90 code, cubic harmonics orbitals (such as pz, px, py) are always in pre-defined order which is independent of the orbital order in the Projections block in the wannier90's input file.
[ I have checked this feature in Wannier90 v2.1.0 and v3.1.0 ]
For example, the order of the three p (or five d) orbitals in Wannier90 code is
pz; px; py

dz2; dxz; dyz; dx2-y2; dxy

However, in our WannSymm code, the order of orbitals is exactly that order of orbitals written in the input file.
Therefore, if WannSymm is used as post-processing code of Wannier90 code, the order of orbitals should follows Wannier90's definition.

Thank you very much for the reply. I think the problem was VASP(whether this version or the actual compilation in the cluster) because everything worked perfect with QE.
Best regards,


Adding modules

I want to add Gorilla/Mux which is HTTP router, Ebiten, which is a game engine to make 2D games. Can I?

Sure!

For Ebiten. you are welcome to create a new tag: GAME_ENGINE Tag = "Game Engine"