Load testing with locust.io

Description
This PR implements load testing with the locust.io load testing framework. The application code relies on using the Yelp Bravado Swagger Client which uses our applications own swagger files to create API calls.
The load testing demo implements these things:

Anon User: Touching home page only
Service Member App: PPM Flow only
Office App: Queue and Move Inspection (no move modification)
TSP App: Queue and Move Inspection (no move modification)

To enable load testing these PRs had be merged in transcom/mymove:

#1685 - automated creation of devlocal users
#1823 - don't return nil for dutystation
#1824 - rework devlocal methods for signin
#1861 - logout should use POST (See #1858 and #1830)
#1905 - devlocal create and login as any user
#2071 - Authentication POST issues
#2072 - Unique Devlocal Users
#2073 - Fix Swagger Office Queue Spec
#2074 - Remove 'format: string' from spec
#2081 - Enable devlocal auth from flag
#2187 - Fix move queue last modified date and name
#2213 - Fix missing swagger payloads
#2241 - Devlocal login using email
#2268 - Return 404 for missing PPM Discount information
#2269 - Fix entitlement calculator with missing weight estimate
#2299 - Remove troubleshooting queue item
#2306 - Fix nil error bug for TSP API
#2319 - Missing 422 errors

And these changes had to be made in transcom/ppp-infra:

https://github.com/transcom/ppp-infra/pull/532 - Make Experimental env match Staging/Prod

As part of load testing these PRs were created to fix our systems:

#2324 - Set DB Pool size

Reviewer Notes
I feel as though this ought to be a separate repository from MilMove. I can easily move this and maintain the history if folks would like it.
Setup
Local Development
First install the requirements:
cd load_testing
virtualenv .venv
source .venv/bin/activate
pip install -r requirements.txt
cd ../

Then in one terminal make sure the application is running:
make server_run

From another terminal you can run in the browser with:
locust -f load_testing/locustfile.py

And then visit http://localhost:8089. Or you can run without the web interface here:
locust -f load_testing/locustfile.py --no-web --clients=50 --hatch-rate=5 --run-time=120s

Here is an example of the load testing output: https://gist.github.com/chrisgilmerproj/7f542d94d90dfd515b076ef10771b1a3
Experimental Environment
To load test the experimental environment you must modify the DEVLOCAL_AUTH environment variable and deploy the code to the experimental environment.
Then you can use the same steps as the development as above as long as you change the host parameter in the locustfile.py test classes and point them to the experimental domains:

https://my.experimental.move.mil
https://office.experimental.move.mil
https://tsp.experimental.move.mil

Code Review Verification Steps

[ ] Test against Experimental
[ ] Request review from a member of a different team.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

There's a "60 day rule" that means we don't guarantee data more than 60 days out. So the load test should enforce dates be within that 60 days.

@pjdufour-truss @rdhariwal @tinyels - I think the next step here is to get this approved. Instead of merging it I'll open a new git repository and make this the initial commit (I can keep the commit history when I copy it over). Then folks can start making changes to that code as they see fit.

I have moved the code to a new repository: https://github.com/transcom/milmove_load_testing


[5pt] Update Shapely Python Package calls

We use shapely python package for a number of things and one of the parts we are using is deprecated. We need to hunt them all down and upgrade them. It can be seen at clip_vectors_to_wbd.py line 59/60.  Other files will need the same fix.
But it all still works.
It can be seen via gms_run_unit.sh as:
##########################################################################
Get Vector Layers and Subset 07080101
##########################################################################
Thu Aug  4 13:04:07 UTC 2022
/usr/local/lib/python3.8/dist-packages/geopandas/_compat.py:84: UserWarning: The Shapely GEOS version (3.10.2-CAPI-1.16.0) is incompatible with the GEOS version PyGEOS was compiled with (3.8.0-CAPI-1.13.1). Conversions between both will be slow.
  warnings.warn(
Subsetting NWM Lakes for HUC8 07080101
/foss_fim/src/clip_vectors_to_wbd.py:59: ShapelyDeprecationWarning: __len__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Check the length of the `geoms` property instead to get the  number of parts of a multi-part geometry.
  for i in range(len(nwm_lakes_fill_holes)):
/foss_fim/src/clip_vectors_to_wbd.py:60: ShapelyDeprecationWarning: __getitem__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Use the `geoms` property to access the constituent parts of a multi-part geometry.
  nwm_lakes.loc[i,'geometry'] = nwm_lakes_fill_holes[i]
/foss_fim/src/clip_vectors_to_wbd.py:60: ShapelyDeprecationWarning: __getitem__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Use the `geoms` property to access the constituent parts of a multi-part geometry.
  nwm_lakes.loc[i,'geometry'] = nwm_lakes_fill_holes[i]
/foss_fim/src/clip_vectors_to_wbd.py:60: ShapelyDeprecationWarning: __getitem__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Use the `geoms` property to access the constituent parts of a multi-part geometry.
  nwm_lakes.loc[i,'geometry'] = nwm_lakes_fill_holes[i]
/foss_fim/src/clip_vectors_to_wbd.py:60: ShapelyDeprecationWarning: __getitem__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Use the `geoms` property to access the constituent parts of a multi-part geometry.
  nwm_lakes.loc[i,'geometry'] = nwm_lakes_fill_holes[i]
/foss_fim/src/clip_vectors_to_wbd.py:60: ShapelyDeprecationWarning: __getitem__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Use the `geoms` property to access the constituent parts of a multi-part geometry.
  nwm_lakes.loc[i,'geometry'] = nwm_lakes_fill_holes[i]
Subsetting NLD levee lines for HUC8 07080101
/usr/local/lib/python3.8/dist-packages/geopandas/_vectorized.py:149: ShapelyDeprecationWarning: __len__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Check the length of the `geoms` property instead to get the  number of parts of a multi-part geometry.
  out[:] = [_pygeos_to_shapely(geom) for geom in data]
Subsetting NHD Headwater Points for HUC8 07080101
/usr/local/lib/python3.8/dist-packages/geopandas/array.py:175: ShapelyDeprecationWarning: The array interface is deprecated and will no longer work in Shapely 2.0. Convert the '.coords' to a numpy array instead.
  return vectorized.to_shapely(geoms.data)
Querying NHD Streams for HUC8 07080101
/usr/local/lib/python3.8/dist-packages/pandas/core/dtypes/cast.py:1479: ShapelyDeprecationWarning: __len__ for multi-part geometries is deprecated and will be removed in Shapely 2.0. Check the length of the `geoms` property instead to get the  number of parts of a multi-part geometry.
  result[:] = values
/usr/local/lib/python3.8/dist-packages/pandas/core/dtypes/cast.py:74: ShapelyDeprecationWarning: The array interface is deprecated and will no longer work in Shapely 2.0. Convert the '.coords' to a numpy array instead.
  values = construct_1d_object_array_from_listlike(values)
/usr/local/lib/python3.8/dist-packages/geopandas/array.py:175: ShapelyDeprecationWarning: The array interface is deprecated and will no longer work in Shapely 2.0. Convert the '.coords' to a numpy array instead.
  return vectorized.to_shapely(geoms.data)

The new extra shapely warnings created during the addition of psycop2 package, have now been reduced as part of a different PR which added boto3 (for AWS).  This reduces the urgency for fixing this.  However, there is an argument for getting Shapely and GeoPandas up to newer versions which is at the core of this problem.


Fix incorrect properties used in baggage section

@saisuryakat Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@saisuryakat Thank you for signing the Contributor License Agreement!


pnpm: could not install dependency packages at project root

Environment

ESLint 8.57.0
Node 20.11.1
eslint/config  1.0.1

What is happening
After selecting options, when I choosed package manager pnpm at project root and tried to instal packages, pnpm throw errors below.

ERR_PNPM_ADDING_TO_ROOT  Running this command will add the dependency to the workspace root, which might not be what you want - if you really meant it, make it explicit by running this command again with the -w flag (or --workspace-root). If you don't want to see this warning anymore, you may set the ignore-workspace-root-check setting to true.

Solution
pnpm workspace is enabled by pnpm-workspace.yaml existence.
reference: https://pnpm.io/ja/workspaces
I think these two steps below can solve this issue.

implements findPnpmWorkspaceYaml like findPackageJson in lib/npm-utils.js

if finds yaml, return true. if not, return null.

impletements like workspaceFlag and pass -w to spawn in installSyncSaveDev in lib/npm-utils.js

reference: https://github.com/eslint/create-config/blob/main/lib/utils/npm-utils.js
Could I create this solution's draft PR?

sure, PRs are welcome! 👍

@aladdin-add thx!

@aladdin-add I submitted PR of this issue, if you could permission to review, could you do that?


[next] keyCode values for KeyboardEvents created via KeyEvent in dartium are incorrect

Currently if you programmatically create a new KeyEvent, the underlying KeyboardEvent that gets created on Dartium has a keyCode and charCode of 0 istead of the desired value. We'll need to make the proper calls into v8/DOM to actually set the correct value.

It would be really nice to finally get a solution to this issue, especially since the recommended method (at the top of https://api.dartlang.org/1.13.1/dart-html/KeyEvent-class.html) appears to be broken in 1.13 (see below). Is there another workaround being considered or is there some kind of ETA on this?
Uncaught Unhandled exception:
InvalidStateError: Failed to execute 'dispatchEvent' on 'EventTarget': The event is already being dispatched.
#0      Blink_JsNative_DomException.callMethod (dart:_blink:17262)
#1      BlinkEventTarget.dispatchEvent_Callback_1_ (dart:_blink:4422)
#2      EventTarget.dispatchEvent (dart:html:17300)
#3      _CustomKeyEventStreamImpl.add (dart:html:44939)
#4      _KeyboardEventHandler.processKeyDown (dart:html:46680)
#5      wrap_event_listener.<anonymous closure>.<anonymous closure> (dart:html:1215)

After we roll Dartium forward to build 45/46 we'll re-look at all open Dartium bugs.

Just hit this in pageloader, which used this API for testing.
Should KeyEvent be deprecated in favor of KeyboardEvent?  That appears to be the new standard, but it's not quite there on all browsers though:
https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/KeyboardEvent

http://caniuse.com/#search=KeyboardEvent
Worth looking at the specific bits that are and aren't supported.

The important thing is probably KeyboardEvent.key, which would be an actual portable and standard way of identifying the key. If we're lucky, you'll even be able to set it when constructing the event. But it's only just gone into the bleeding edge of Safari. We may be able to hack around it by delegating that to keyIdentifier on Safari in the meantime.

I'm trying to unit test some keyboard handling in my app. Is there any work around for this at all? I'm willing to re-architect my app just so I can generate keyboard events artificially. I see a bunch of unit tests in Dart SDK but they are failing... :-1:
https://github.com/dart-lang/sdk/blob/master/tests/html/keyboard_event_test.dart
Is there something that does work?

@georgelesica-wf Thanks for the tips. What I ended up doing is abstracting even further:
class Input extends HtmlElement {
    StreamController<KeyEvent> controller = new StreamController<KeyEvent>(sync: true);
    Stream<KeyEvent> get onKeyEvent => controller.stream;
    Input.created(): super.created() {
        onKeyDown.listen((KeyboardEvent e) {
            controller.add(new KeyEvent.wrap(e));
        });
    }
}

When I want to listen for KeyEvents I can do it like so (added bonus is that handleKeyboard will get a KeyEvent object):
input.onKeyEvent.listen(handleKeyboard);

When I want to test:
input.controller.add(new KeyEvent('keydown', charCode: key));

So far this has worked pretty well.


update information for Typetalk action

update description option's help and author.

Coverage remained the same at 83.09% when pulling 35fda90bf89399750abf38276d9e977ec034a9dd on nulab:master into ed620c3ab28d22cc6e2a0aecfa58b9c7cd6dd6ec on KrauseFx:master.

Coverage remained the same at 83.09% when pulling d32ba8b9507898acae53f8395290d9636583f51f on nulab:master into ed620c3ab28d22cc6e2a0aecfa58b9c7cd6dd6ec on KrauseFx:master.

Coverage remained the same at 83.09% when pulling d32ba8b9507898acae53f8395290d9636583f51f on nulab:master into ed620c3ab28d22cc6e2a0aecfa58b9c7cd6dd6ec on KrauseFx:master.

Coverage decreased (-0.04%) to 83.06% when pulling 14019f81ee78fd242f6d81ebeeadc2bdff33e2f3 on nulab:master into ed620c3ab28d22cc6e2a0aecfa58b9c7cd6dd6ec on KrauseFx:master.

Thanks @dataich, looks great :+1: Will be in the next release.

thanks😀


CNVKit: Reference is missing 155434 bins

Hi,
I am trying to use CNVKit to call copy number variants in a population of 100 WGS samples. Reference genome size is ca 200MB, depth per sample varies 9X and 85X, average is 34X. Some samples have 100 bp PE reads, other 125bp PE reads.
I am using bcbio 1.0.3a and this is my YAML:
# Template for whole genome Illumina variant calling with FreeBayes
# This is a GATK-free pipeline without post-alignment BAM pre-processing
# (recalibration and realignment)
---
details:
  - analysis: variant2
    genome_build: my_genome
    description:
    # to do multi-sample variant calling, assign samples the same metadata / batch
    metadata:
      batch: Project_123_CNVKit
    algorithm:
      aligner: false
      mark_duplicates: false
      recalibrate: false
      realign: false
      svcaller: cnvkit
      ploidy:
          default: 2
      nomap_split_targets: 3000
      effects: false
      tools_off:
      - gemini
      # for targetted projects, set the region
      # variant_regions: /path/to/your.bed

I get the following CNVKit log and the error at the end.
I am kind of new to calling copy number variattions and using CNVKit. Does the above yaml make sense and is is possible to use CNVKit within bcbio to analyze a batch of 100 WGS samples?
Should I adjust some parameters like bin size to make this work?
How can I avoid the Reference is missing 155434 bins  error? I am running the analysis starting from BAM files and checked that the bam file and reference are compatible (i.e. bam header SQ lenght and fa.fai lenght entries match. ).
Thank you.
[2017-05-16T01:37Z] CNVkit background
[2017-05-16T01:37Z] Detected file format: bed
[2017-05-16T01:37Z] Calculating GC and RepeatMasker content in /data/prod/Tools/bcbio/latest/genomes/my_genome/my_genome/seq/my_genome.fa ..
.
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_01
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_02
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_03
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_04
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_05
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_06
[2017-05-16T01:37Z] Extracting sequences from chromosome Chr_07
[2017-05-16T01:37Z] Wrote /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmp7on8JT/ProviderX_701_03_background.cnn with 187646 regions
[2017-05-16T01:37Z] Resource requests: cnvkit; memory: 3.00; cores: 10
[2017-05-16T01:37Z] Configuring 1 jobs to run, using 10 cores each with 30.1g of memory reserved for each job
[2017-05-16T01:37Z] CNVkit fix
[2017-05-16T01:38Z] Processing target: ProviderX_601_01-ready-Project_756
[2017-05-16T01:38Z] Keeping 187646 of 187646 bins
[2017-05-16T01:38Z] Correcting for GC bias...
[2017-05-16T01:38Z] Correcting for density bias...
[2017-05-16T01:38Z] Processing antitarget: ProviderX_601_01-ready-Project_756
[2017-05-16T01:38Z] Wrote /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmp_3j6sG/ProviderX_601_01-ready-Project_756.cnr with 187646 regions
[2017-05-16T01:38Z] CNVkit segment
[2017-05-16T01:38Z] Dropped 6 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2        depth    weight
[2017-05-16T01:38Z] 0     Chr_04     43875     44872    -  3.82126   594.507000  0.665554
[2017-05-16T01:38Z] 1     Chr_04   3768574   3769577    -  4.71662  1107.270000  0.669559
[2017-05-16T01:38Z] 2     Chr_04  14962860  14963851    -  4.98888  1267.650000  0.661549
[2017-05-16T01:38Z] 3     Chr_04  19813663  19813919    - -5.78114     0.671875  0.170895
[2017-05-16T01:38Z] 4     Chr_04  21851750  21852747    -  6.08524  2786.990000  0.665554
[2017-05-16T01:38Z] 5     Chr_04  22659059  22660058    -  4.98365  1337.320000  0.666889
[2017-05-16T01:38Z] Dropped 9 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2        depth    weight
[2017-05-16T01:38Z] 0     Chr_02   2284274   2285278    -  5.18663  1418.500000  0.670227
[2017-05-16T01:38Z] 1     Chr_02   5373320   5374325    -  4.32901   777.542000  0.670895
[2017-05-16T01:38Z] 2     Chr_02   5729794   5730039    - -5.83922     0.738776  0.163551
[2017-05-16T01:38Z] 3     Chr_02   6635560   6636565    -  4.50737   947.006000  0.670895
[2017-05-16T01:38Z] 4     Chr_02   7422936   7422977    - -5.27897     1.000000  0.027370
[2017-05-16T01:38Z] 5     Chr_02  16275183  16276178    -  4.73816  1096.160000  0.664219
[2017-05-16T01:38Z] 6     Chr_02  17861712  17862713    -  5.42750  1728.420000  0.668224
[2017-05-16T01:38Z] 7     Chr_02  19148604  19149603    -  5.93644  2544.380000  0.666889
[2017-05-16T01:38Z] 8     Chr_02  21269849  21270056    - -6.54394     0.405797  0.138184
[2017-05-16T01:38Z] Dropped 4 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2     depth    weight
[2017-05-16T01:38Z] 0     Chr_05   6710716   6711711    -  5.26742  1612.370  0.664219
[2017-05-16T01:38Z] 1     Chr_05   6904285   6905286    -  4.31289   835.528  0.668224
[2017-05-16T01:38Z] 2     Chr_05  18637921  18638916    -  5.65862  2121.810  0.664219
[2017-05-16T01:38Z] 3     Chr_05  24385842  24386835    -  4.61168  1028.460  0.662884
[2017-05-16T01:38Z] Dropped 10 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2        depth    weight
[2017-05-16T01:38Z] 0     Chr_03   1288798   1289799    -  5.89180  2385.410000  0.668224
[2017-05-16T01:38Z] 1     Chr_03   1492974   1493971    -  4.47154   913.139000  0.665554
[2017-05-16T01:38Z] 2     Chr_03   4227015   4228014    -  5.08963  1369.540000  0.666889
[2017-05-16T01:38Z] 3     Chr_03  12813615  12814624    -  4.43577   864.906000  0.673565
[2017-05-16T01:38Z] 4     Chr_03  17191216  17191442    - -6.32083     0.530973  0.150868
[2017-05-16T01:38Z] 5     Chr_03  18034323  18035337    -  3.27861   401.201000  0.676903
[2017-05-16T01:38Z] 6     Chr_03  24316966  24317958    -  5.94889  2615.860000  0.662216
[2017-05-16T01:38Z] 7     Chr_03  28343571  28344573    -  4.12480   643.906000  0.668892
[2017-05-16T01:38Z] 8     Chr_03  29374854  29374900    - -5.35189     1.000000  0.030708
[2017-05-16T01:38Z] 9     Chr_03  34650526  34651514    -  5.83752  2409.550000  0.659546
[2017-05-16T01:38Z] Dropped 8 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2     depth    weight
[2017-05-16T01:38Z] 0     Chr_01   6853606   6853636    - -5.19398     1.000  0.020027
[2017-05-16T01:38Z] 1     Chr_01   9384097   9385096    -  3.58383   510.999  0.666889
[2017-05-16T01:38Z] 2     Chr_01  12859336  12859774    -  6.31799  3390.130  0.292390
[2017-05-16T01:38Z] 3     Chr_01  15806879  15807886    -  4.46807   903.364  0.672230
[2017-05-16T01:38Z] 4     Chr_01  19948931  19949931    -  5.05138  1383.190  0.667557
[2017-05-16T01:38Z] 5     Chr_01  20844956  20845956    -  4.53715   933.929  0.667557
[2017-05-16T01:38Z] 6     Chr_01  23036061  23037058    -  4.67662  1074.430  0.665554
[2017-05-16T01:38Z] 7     Chr_01  25571584  25571607    - -5.19406     1.000  0.015354
[2017-05-16T01:38Z] Dropped 7 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2        depth    weight
[2017-05-16T01:38Z] 0     Chr_07   3175442   3175533    - -5.40440     1.000000  0.060748
[2017-05-16T01:38Z] 1     Chr_07   7624629   7625411    -  4.53094   984.240000  0.522029
[2017-05-16T01:38Z] 2     Chr_07   8946397   8946398    -  6.27048  2826.000000  0.000668
[2017-05-16T01:38Z] 3     Chr_07   9690619   9690865    - -6.25141     0.556911  0.164219
[2017-05-16T01:38Z] 4     Chr_07  14884535  14885535    -  5.32291  1689.060000  0.667557
[2017-05-16T01:38Z] 5     Chr_07  15825118  15826121    -  4.88396  1200.100000  0.669559
[2017-05-16T01:38Z] 6     Chr_07  18109673  18110672    -  4.77358  1135.280000  0.666889
[2017-05-16T01:38Z] Dropped 9 outlier bins:
[2017-05-16T01:38Z]   chromosome     start       end gene     log2     depth    weight
[2017-05-16T01:38Z] 0     Chr_06   2021674   2022670    -  4.42288   906.738  0.664887
[2017-05-16T01:38Z] 1     Chr_06   5240098   5241101    -  4.89400  1159.750  0.669559
[2017-05-16T01:38Z] 2     Chr_06   6877458   6878460    -  5.57360  2013.810  0.668892
[2017-05-16T01:38Z] 3     Chr_06   8738273   8739273    -  4.84077  1212.390  0.667557
[2017-05-16T01:38Z] 4     Chr_06  16535804  16536806    -  6.13019  2833.090  0.668892
[2017-05-16T01:38Z] 5     Chr_06  20284285  20285280    -  3.60832   507.778  0.664219
[2017-05-16T01:38Z] 6     Chr_06  22816075  22817073    -  5.48555  1664.030  0.666222
[2017-05-16T01:38Z] 7     Chr_06  23621405  23622405    -  5.39556  1752.040  0.667557
[2017-05-16T01:38Z] 8     Chr_06  23834016  23834044    - -5.19636     1.000  0.018692
[2017-05-16T01:38Z] Wrote /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmpRXnmhE/ProviderX_601_01-ready-Project_756.cns with 42 regions
[2017-05-16T01:38Z] Sort and merge BED file : ProviderX_701_03
[2017-05-16T01:38Z] CNVkit coverage bin estimation
[2017-05-16T01:39Z] Targets will be ignored: /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/structural/ProviderX_701_03/cnvkit/ProviderX_701_03-coverage.callable-vrsubset-callableblocks-sortmerge.bed
[2017-05-16T01:39Z] CNVkit target
[2017-05-16T01:39Z] Detected file format: bed
[2017-05-16T01:39Z] Splitting large targets
[2017-05-16T01:39Z] Wrote /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmprpaXYo/ProviderX_701_03-coverage.callable-vrsubset-callableblocks-sortmerge-Project_756.target.bed with 187565 regions
[2017-05-16T01:39Z] CNVkit antitarget
[2017-05-16T01:39Z] Detected file format: bed
[2017-05-16T01:39Z] Detected file format: bed
[2017-05-16T01:40Z] Wrote /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmp2HgA1N/ProviderX_701_03-coverage.callable-vrsubset-callableblocks-sortmerge-Project_756.antitarget.bed with 0 regions
[2017-05-16T01:40Z] CNVkit background
[2017-05-16T01:40Z] Detected file format: bed
[2017-05-16T01:40Z] Calculating GC and RepeatMasker content in /data/prod/Tools/bcbio/latest/genomes/my_genome/my_genome/seq/my_genome.fa ...
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_01
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_02
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_03
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_04
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_05
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_06
[2017-05-16T01:40Z] Extracting sequences from chromosome Chr_07
[2017-05-16T01:40Z] Wrote /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmpWv8gEh/ProviderX_601_01_background.cnn with 187565 regions
[2017-05-16T01:40Z] Resource requests: cnvkit; memory: 3.00; cores: 10
[2017-05-16T01:40Z] Configuring 1 jobs to run, using 10 cores each with 30.1g of memory reserved for each job
[2017-05-16T01:40Z] CNVkit fix
[2017-05-16T01:40Z] Processing target: ProviderX_701_03-ready-Project_756
[2017-05-16T01:41Z] Traceback (most recent call last):
[2017-05-16T01:41Z]   File "/data/prod/Tools/bcbio/latest/anaconda/bin/cnvkit.py", line 13, in <module>
[2017-05-16T01:41Z]     args.func(args)
[2017-05-16T01:41Z]   File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/commands.py", line 553, in _cmd_fix
[2017-05-16T01:41Z]     args.do_gc, args.do_edge, args.do_rmask)
[2017-05-16T01:41Z]   File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/fix.py", line 19, in do_fix
[2017-05-16T01:41Z]     do_gc, do_edge, False)
[2017-05-16T01:41Z]   File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/fix.py", line 53, in load_adjust_coverages
[2017-05-16T01:41Z]     ref_matched = match_ref_to_sample(ref_cnarr, cnarr)
[2017-05-16T01:41Z]   File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/fix.py", line 123, in match_ref_to_sample
[2017-05-16T01:41Z]     % (num_missing, samp_cnarr.sample_id))
[2017-05-16T01:41Z] ValueError: Reference is missing 155434 bins found in ProviderX_701_03-ready-Project_756
[2017-05-16T01:41Z] Uncaught exception occurred
Traceback (most recent call last):
  File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 22, in run
    _do_run(cmd, checks, log_stdout, env=env)
  File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 102, in _do_run
    raise subprocess.CalledProcessError(exitcode, error_msg)
CalledProcessError: Command 'set -o pipefail; export TMPDIR=/data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmplBSk1k && /data/prod/Tools/bcbio/latest/anaconda/bin/cnvkit.py fix -o /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/bcbiotx/tmplBSk1k/ProviderX_701_03-ready-Project_756.cnr /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/structural/ProviderX_701_03/cnvkit/raw/ProviderX_701_03-ready-Project_756.targetcoverage.cnn /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/structural/ProviderX_701_03/cnvkit/raw/ProviderX_701_03-ready-Project_756.antitargetcoverage.cnn /data/run/Projects/Organism/Project-945/CNVKit/Project_756_bam_table/work/structural/ProviderX_701_03/cnvkit/raw/ProviderX_601_01_background.cnn
Processing target: ProviderX_701_03-ready-Project_756
Traceback (most recent call last):
  File "/data/prod/Tools/bcbio/latest/anaconda/bin/cnvkit.py", line 13, in <module>
    args.func(args)
  File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/commands.py", line 553, in _cmd_fix
    args.do_gc, args.do_edge, args.do_rmask)
  File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/fix.py", line 19, in do_fix
    do_gc, do_edge, False)
  File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/fix.py", line 53, in load_adjust_coverages
    ref_matched = match_ref_to_sample(ref_cnarr, cnarr)
  File "/data/prod/Tools/bcbio/latest/anaconda/lib/python2.7/site-packages/cnvlib/fix.py", line 123, in match_ref_to_sample
    % (num_missing, samp_cnarr.sample_id))
ValueError: Reference is missing 155434 bins found in ProviderX_701_03-ready-Project_756
' returned non-zero exit status 1

Neill;
From the bcbio side it looks like you specified everything correctly, but I'm not sure what does wrong with the CNVkit fix step. I'll have to page @etal  Eric does this error point you in a useful direction to help debug further? Happy to investigate if there is something bcbio does wrong to cause this.

Sorry for the trouble. It looks like the CNVkit part of the pipeline worked for one sample, but then failed on the next. Relatedly, it would be reasonable to construct two separate references, one for 100bp-read samples and another for 125bp.
In general that ValueError means a reference was generated from bins other than the .targetcoverage.cnn and .antitargetcoverage.cnn that it's being compared to at that step. I'll have to look into the bcbio workflow a little more.

This is old and bcbio and cnvkit have been updated a ton, so it is unlikely this problem still exists, closing.


conda-forge feedstock?

Hi @cjdoris,
I'm eager to try porting PySR to PythonCall.jl from PyJulia. However, the last major hurdle is conda-forge support. Would it be possible to create a juliacall feedstock, similar to https://github.com/conda-forge/pyjulia-feedstock/? This would allow Python+Julia packages like PySR to depend on PythonCall in conda builds. (Similar to how other high-performance Python packages depend on a C++ backend)
For what it's worth, the conda-forge version of PySR has made up about 1/3rd of its total downloads while pip makes up 2/3rds. So I think conda, despite being slightly less popular, still captures a decent portion of Python users.
cc @mkitti
Thanks!
Miles

Did you want PythonCall.jl or juliacall in conda-forge?

juliacall (but it would have to package PythonCall.jl). I think it would have to depend on the julia-feedstock and use the Python that comes with the environment, rather than setting up its own CondaPkg.

There have been PRs around for adding JuliaPkg and JuliaCall to conda-forge for a while, but they seem to have stalled: https://github.com/conda-forge/staged-recipes/pull/20379, https://github.com/conda-forge/staged-recipes/pull/20380.
I don't have the time to contribute to the PRs myself (it's not simple) but you could team up with mkitti to get them through. I'm happy to provide opinions though.

My main objections there was the name since conda-forge is supposed to be language agnostic. There is also an R package called juliacall, thus I think we should call the Python package pyjuliacall and the R package r-juliacall.
I will see about resubmitted those staged recipes with the naming scheme above.

Pinging this thread again. I should mention that I'm happy to maintain the feedstock once it's running. I just have no time to set up the initial build due to teaching this term. Maybe that makes things a bit easier to push through. Once it's running I can maintain it, as I would presumably be able to switch away from PyJulia at that point, and can support PythonCall instead.

cc @schlichtanders too.
@cjdoris if you could help in getting the initial conda-forge working, I can take over maintaining it (and perhaps @mkitti as well). I can also help you long-term in maintaining PythonCall.jl/juliacall because I would depend on those for PySR. I've been good about keeping PyJulia working as it is my key dependency (https://github.com/JuliaPy/pyjulia/commits/master/). I am basically offering I could do the same for PythonCall.jl once it is ready for me.
I really just need your help in making the initial scheme work because it requires deep knowledge of the internals!

I don't have the time to contribute to the PRs myself (it's not simple) but you could team up with mkitti to get them through. I'm happy to provide opinions though.

I can help with maintaining the ecosystem longer term, so if you can help now, I think would actually save net time.

Sure, what help do you need? The PR to add juliacall and juliapkg to conda-forge looks good to me.
Help maintaining PythonCall/JuliaCall is most welcome - my available time to spend on it fluctuates a lot over the year! I'm slowly working towards v1 but there's a lot to do.

Thanks! I think at this point, just helping get https://github.com/conda-forge/staged-recipes/pull/25097 pushed through as soon as possible would be best.

Here's the prototype
conda install julialang::pyjuliacall

Thanks to @mkitti, this is all done!


generate default test suite

Possible new feature:
As we're working on updating the websites, I was thinking it could be useful to have a default github template that people could fork, rename and use as a starting point for creating their test suites with Watir.
Then I got to thinking that maybe we could do it the same way jekyll does it:
jekyll new my_jekyll_site
and do:
watir new my_watir_testsuite
Which requires the things and creates RSpec examples. Maybe this would make more sense if we collaborated on a watir-sanctioned page object model. Either way, I wanted to throw this out there as an idea.

Revisiting this in a separate gem.


chore: release 1.1.7

📦 Release PR
1.1.7 (2024-02-03)
🪲 Bug Fixes

dates now getting parsed based on timezone #22 (6b00f31)

🔧 Code Refactoring

added babel as bundler for better builds (6b00f31)
added getters for status and statusText (a242c10)

⚙ Dependencies

migrated from date-fns to luxon (6b00f31)

🤖 This pull request was automatically generated. To publish the version, please merge the pull request.

:robot: Release is at https://github.com/Vertretungsapp/indiware-api/releases/tag/v1.1.7 :sunflower:


protonmail-bridge: 1.0.5-1 -> 1.0.6-1

Motivation for this change
Update protonmail-bridge
Things done

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

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

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

PS: In the version 1.0.6-1 the icon is missing from the deb file, so I temporarily deleted some lines.

PS: In the version 1.0.6-1 the icon is missing from the deb file, so I temporarily deleted some lines.

If you assume the icon will reappear in a future version it might be better to just comment them out.

@GrahamcOfBorg  build protonmail-bridge

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: protonmail-bridge
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: protonmail-bridge
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1
shrinking /nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1/lib/Desktop-Bridge
strip is /nix/store/gpc2wld1s0c6qzx9326cwn1wcx29xzsj-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1/lib  /nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1/bin
patching script interpreter paths in /nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1
/nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1/lib/Desktop-Bridge.sh: interpreter directive changed from "/bin/bash" to "/nix/store/56nrxy58wbhvs2sy3rir1jqa68p0kkm5-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1...
/nix/store/jfsljwash10xj9fhb7jyy91375kclcjc-protonmail-bridge-1.0.6-1

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: protonmail-bridge
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

I added again the lines for the icon and commented them

@GrahamcOfBorg build protonmail-bridge

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: protonmail-bridge
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: protonmail-bridge
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: protonmail-bridge
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1
shrinking /nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1/lib/Desktop-Bridge
strip is /nix/store/gpc2wld1s0c6qzx9326cwn1wcx29xzsj-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1/lib  /nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1/bin
patching script interpreter paths in /nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1
/nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1/lib/Desktop-Bridge.sh: interpreter directive changed from "/bin/bash" to "/nix/store/56nrxy58wbhvs2sy3rir1jqa68p0kkm5-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1...
/nix/store/f9nmq2xcv35rg0ngpq5h67fv4lnxqdi5-protonmail-bridge-1.0.6-1


Unit-test for pruning

Create unit tests for pruning to check for simple correctness
Benefit: Useful for regression testing in future
Cost: 3 hours

Complete with PR #218


Using the switched variable in an if statement causes an error.

TypeScript Version:  3.1
Search Terms: switch, if, switch this
Code
class MyClass{
  myString: string;

  setString() {
    this.myString = "c";
  }

  doSomeSwitching() {
    switch (this.myString) {
      case "a":
        this.setString();
        if (this.myString == "c") {

        }
        break;
      default:
        break;
    }
  }
}

Expected behavior:
I would expect no error.
Actual behavior:
An error is generated for the if statement.
if (this.myString == "c")
This condition will always return 'false' since the types '"a"' and '"c"' have no overlap.
The code above is the simplest form. In real use I was creating a parser. Using an instance variable to step through tokens. I check the token type with the case and then "eat" the token. The instance variable is then changed after which I want to check the token again.
Playground Link:
Link
Related Issues: I couldn't find anything that looked like this. Honestly I was mostly looking at the examples they gave since I'm not sure what many of the big words mean.

Nice, I didn't think of doing that. I found that any assignment will make it happy. So you don't even have to mess with the function.
class MyClass{
  myString: string;

  setString() {
    this.myString = "c";
  }

  doSomeSwitching() {
    switch (this.myString) {
      case "a":
        this.setString();
        this.myString = this.myString; // <-- Adding this takes the error away.
        if (this.myString == "c") {

        }
        break;
      default:
        break;
    }
  }
}

This is a design limitation. See discussion in #9998.

Is there any real-world benefit to the type being narrowed to a literal inside the cases?


Fine tune button sizes

Closes #1041

@razzeee Great  solution! Buttons don't get truncated any more!
Thanks!


added new supported items to EMS

This set of PRs is meant to limit some operations so that they can only be performed on EMSs that support them.
The operations in question all have to do with block-storage managers.

Add a new storage-system to the EMS
Add a new host-initiator to the EMS
Add a new volume-mapping
Currently the only manger that supports these operations is the manageiq-providers-autosde. But there's nothing to stop users from trying to perform these operations on other block-storage managers, such as Cinder.

So we add features to represent these operations, and we filter by them in the UI-forms for the operations.
Related PRs
https://github.com/ManageIQ/manageiq/pull/21387
https://github.com/ManageIQ/manageiq-ui-classic/pull/7837
https://github.com/ManageIQ/manageiq-providers-autosde/pull/77
The screenshot below shows one of the forms that would be affected.

@miq-bot cross_repo_test https://github.com/ManageIQ/manageiq-ui-classic/pull/7837 https://github.com/ManageIQ/manageiq-providers-autosde/pull/77 https://github.com/ManageIQ/manageiq/pull/21387

@miq-bot cross_repo_test manageiq-ui-classic#7837 manageiq#21387

@gregoryb-at-ibm any feature which is enabled by a subclass (e.g. https://github.com/ManageIQ/manageiq-providers-autosde/pull/77/files#diff-e563d6b0fc624d7cacb601a7e2cefeaec8a707d534362900e23888d0caa9e958R12-R14) has to have the disable in the base class.  This is what allows you to ask supports_add_storage? on any EMS without it raising an exception.
You'll need to add supports_not :add_storage, etc... here

@agrare Sorry I missed that. I fixed it now.

@agrare , do you think there are any tests I could add to cover this? Maybe a test that would have caught the missing supports_not?

@gregoryb-at-ibm I want to add a "common" spec that walks all supports features in subclasses and ensures the base class has the equivalent but that wouldn't have helped here since you're also adding the new features in the subclass.  In the end it is up to reviewers to catch this :)

@miq-bot lasker/yes?

@miq-bot add_label lasker/yes?

@miq-bot rm_label lasker/yes?

@miq-bot add_label morphy/yes?

@miq-bot remove_label lasker/yes?

@gregoryb-at-ibm A conflict occurred during the backport of this pull request to morphy.
If this pull request is based on another pull request that has not been marked for backport, add the appropriate labels to the other pull request. Otherwise, please create a new pull request direct to the morphy branch in order to resolve this.
Conflict details:
diff --cc app/models/ext_management_system.rb
index 78bf844151,20f297d112..0000000000
--- a/app/models/ext_management_system.rb
+++ b/app/models/ext_management_system.rb
@@@ -158,11 -162,20 +158,18 @@@ class ExtManagementSystem < Application

    serialize :options

++<<<<<<< HEAD
 +  supports :refresh_ems
++=======
+   supports_not :add_host_initiator
+   supports_not :add_storage
+   supports_not :add_volume_mapping
+   supports_not :admin_ui
++>>>>>>> 0d2cca8b8d... Merge pull request #21387 from Autosde/storage_support
    supports_not :assume_role
 -  supports_not :block_storage
 -  supports_not :change_password
 -  supports_not :cloud_object_store_container_create
 -  supports_not :cloud_subnet_create
 -  supports_not :cloud_tenant_mapping
 -  supports_not :console
 -  supports_not :create_host_aggregate
 -  supports     :create_security_group do
 -    unless SecurityGroup.class_by_ems(self).supports?(:create)
 +
 +  supports :create_security_group do
 +    unless SecurityGroup.class_by_ems(self).supports_create?
        unsupported_reason_add(:create_security_group, _('Security Group creation is not supported'))
      end
    end

@gregoryb-at-ibm hold off on fixing this one just yet - working with @agrare and @chessbyte to see if we should backport the dependent PRs or not (namely https://github.com/ManageIQ/manageiq/pull/21046 )

Skipping backport to morphy, because it is already in the branch.

Backported to morphy in commit a1482c63f263ce586239ce88d52751b4b250c21b.
commit a1482c63f263ce586239ce88d52751b4b250c21b
Author: Adam Grare<EMAIL_ADDRESS>Date:   Tue Aug 24 12:52:31 2021 -0400

    Merge pull request #21387 from Autosde/storage_support

    added new supported items to EMS

    (cherry picked from commit 0d2cca8b8db570535b942705cae09c023d33c662)

@Fryguy Please update me if I need to fix something for the sake of the backport.


[SQL] Support show users from tenant_name

What this PR does:
Which issue(s) this PR fixes:

Fixes #614
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report
Base: 36.76% // Head: 36.76% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (e5035df) compared to base (a690f63).
Patch coverage: 0.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #632      +/-   ##
==========================================
- Coverage   36.76%   36.76%   -0.01%
==========================================
  Files         201      201
  Lines       22394    22394
==========================================
- Hits         8234     8233       -1
- Misses      13244    13245       +1
  Partials      916      916

Impacted Files
Coverage Δ

pkg/runtime/ast/ast.go
71.02% <0.00%> (ø)

pkg/runtime/ast/proto.go
53.33% <ø> (ø)

pkg/runtime/ast/show.go
28.29% <0.00%> (ø)

pkg/dataset/priority_queue.go
76.11% <0.00%> (-1.50%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


feat: radio component page

What is not solved (but I would solve it outside of this PR as the design is not ready), is having several source files.


Performance drag in needle animation

as pointed by reddit's user mahade in his own words:
It looks really cool, but the performance seems to be not so good. I can't debug it currently, but the tooltips and the arrows that animate seem to not reach their maximum FPS.
I see you use requestAnimationFrame a plenty but I'm wondering what properties you're animating. Perhaps diving into CSS paint/composite/layout might clear some things up and make it all feel buttery smooth.
But awesome effort man!

Revisited all render process, result:


Convert project to typescript

this could be interesting thing that I can do

I want to first finish every issue that is not lowpriority first

Will do after #116 is merged.


PHP 7 reserved words - Object - Concrete\Core\Foundation\Object

"Object" is a reserved word since PHP 7 and should not be used as class, interface or trait name.

AFAIK this is a "soft reserved word" and doesn't raise any errors at this time. https://3v4l.org/7Tfbp
What "soft reserved word" means is essentially the use of the name as a classname is deprecated and may be removed sometime in the future. This class is baked in pretty deep and I don't expect this to be removed anytime soon so lets revisit this issue in the next major release after version 8 which will be version 9.


Unable to use with Docker

Describe the bug
Running yarn install gives me the following error:
#11 0.432 yarn install v1.22.22
#11 0.534 [1/5] Validating package.json...
#11 0.540 [2/5] Resolving packages...
#11 1.288 [3/5] Fetching packages...
#11 1.570 error Error<EMAIL_ADDRESS>Request failed "401 Unauthorized"
#11 1.570 at ResponseError.ExtendableBuiltin (/nix/store/hn80x7lgvfxs8zvzlvk3wmhq7qdifv4p-yarn/lib/cli.js:696:66)
#11 1.570 at new ResponseError (/nix/store/hn80x7lgvfxs8zvzlvk3wmhq7qdifv4p-yarn/lib/cli.js:802:124)
#11 1.570 at Request. (/nix/store/hn80x7lgvfxs8zvzlvk3wmhq7qdifv4p-yarn/lib/cli.js:66750:16)
#11 1.570 at Request.emit (node:events:517:28)
#11 1.570 at module.exports.Request.onRequestResponse (/nix/store/hn80x7lgvfxs8zvzlvk3wmhq7qdifv4p-yarn/lib/cli.js:142287:10)
#11 1.570 at ClientRequest.emit (node:events:517:28)
#11 1.570 at HTTPParser.parserOnIncomingClient (node:_http_client:700:27)
#11 1.570 at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
#11 1.570 at TLSSocket.socketOnData (node:_http_client:541:22)
#11 1.570 at TLSSocket.emit (node:events:517:28)

Source:
=> Found "<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#web#@nuxtjs#seo#nuxt-og-image#vanilla-jsoneditor" depends on it
   - Hoisted from "_project_#web#@nuxtjs#seo#nuxt-og-image#vanilla-jsoneditor#@fortawesome#free-regular-svg-icons"

Reproduction
No response
System / Nuxt Info
No response

I think you may have a NPM relation set up to point @fortawesome to npm.fontawesome.com, the package should point to https://www.npmjs.com/package/@fortawesome/free-regular-svg-icons.


Docs: Document excluded_methods property.

Re: teracyhq/flask-classful#57

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

Coverage remained the same at 98.012% when pulling 247ea65536e77ee137c02b580404f2a089d7af63 on hjc:patch-1 into ee88fb3bca4f782b485f851e156f7edfd0df26e1 on teracyhq:develop.

My pleasure!


Switch helper to logger for boarding

Helper is not used in boarding.
Fixes https://github.com/fastlane/boarding/issues/66

:evergreen_tree: :deciduous_tree:


nixos/onlyoffice: Fix initial permissions for the documentserver data

Description of changes
Change the permissions of /var/lib/onlyoffice/documentserver from rwx------ to rwx--x--x so that nginx can access files under /var/lib/onlyoffice/documentserver/App_Data and that onlyoffice works out of the box.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

cc @SuperSandro2000

cc @RaitoBezarius

I had wider permissions on that directory left from testing and didn't notice this. Thanks!


Stryker config in vuejs

How to make stryker recognize in vue?

Stryker environment

+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>

+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>
Additional context
I've been trying to configure stryker with vue for days, but I get this error, and I don't know what else to do...
Test runner crashed. Tried twice to restart it without any luck. Last time the error message was: Error: : Configuration error:

Could not locate module @/assets/img/${this.errorHandler.img}.svg mapped as:
/home/marks/Desktop/projects/ServicosAdministrativos/.stryker-tmp/sandbox8065358/src/assets/img/${this.errorHandler.img}.svg.

Please check your configuration for these entries:
{
  "moduleNameMapper": {
    "/^@\/(.*)$/": "/home/marks/Desktop/projects/ServicosAdministrativos/.stryker-tmp/sandbox8065358/src/$1"
  },
  "resolver": null
}

Hi @marcos-roberto-dev thanks for opening this issue.
The answer is: it should work. Sometimes the issue is that copying your source code to the sandbox directory is enough to get these errors because of webpack plugins, jest plugins, transpiler plugins, etc
Could you try to run with --inPlace
Did you follow this guide?
https://stryker-mutator.io/docs/stryker-js/guides/vuejs
Can you confirm that @/assets/img/${this.errorHandler.img}.svg is part of your code? Of so: Could you create a small reproduction example?


fix: maintain ordering of return value witnesses when constructing ABI

Related issue(s)
Resolves #1174
Description
Summary of changes
This PR switches the evaluator to track the witnesses for the return value in a Vec<Witness> rather than a BTreeSet<Witness>. While it's correct to store them as a set inside the Circuit, we rely on the ordering of these witnesses for proper ABI decoding and so we need to maintain this when we're constructing the ABI.
See #1174 for an example of this causing improper ABI decoding.
Dependency additions / changes

Test additions / changes

Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[x] I have linked this PR to the issue(s) that it resolves.
[x] I have reviewed the changes on GitHub, line by line.
[x] I have ensured all changes are covered in the description.

Documentation needs

[ ] This PR requires documentation updates when merged.

Additional context

Can you also add an example to ensure we don't regress?

how did we regress in the first place? I think this is new to v0.4 - curious how it happened.

The issue is the integration tests make use of the "prove then immediately verify" feature so we're not loading the public inputs from Verifier.toml. We switched to this to cut down CI times but I can revert that.

The issue is the integration tests make use of the "prove then immediately verify" feature so we're not loading the public inputs from Verifier.toml. We switched to this to cut down CI times but I can revert that.

Was it a large effect on CI times?

It was a pretty sizable percentage afaik, i.e. double digits.

I've made the changes to integration tests in #1179 as that dwarfs the changes in this PR.

It was a pretty sizable percentage afaik, i.e. double digits.

oof RIP productivity, lets try to get a larger github runner to counteract this


Fix for sandbox app build.gradle

Description
Looks like the build.gradle defining the sandbox application was excluded when the modules were repackaged. This PR recreates it, allowing people to once again build the sandbox app.
Also incidentally fixes a minor typo in the navigation application id.
I don't think this warrants a changelog update.
Check list

[ ] I have updated CHANGELOG.md if required.
[ ] I have updated documentation if required.

huh yeah, weird that I had issues... ok, reducing the scope to just fixing the typo


fix lint errors from #524

Description
fix lint errors from #524
Testing instructions
No errors in the unit test linting

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage
[ ] {more steps here}

Agile board tracking

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.08%. Comparing base (695842e) to head (171a041).

Additional details and impacted files
@@            Coverage Diff            @@
##           develop     #545    +/-   ##
=========================================
  Coverage    94.08%   94.08%
=========================================
  Files           63       63
  Lines        17863    17863
  Branches      2438     2087   -351
=========================================
  Hits         16807    16807
- Misses        1050     1054     +4
+ Partials         6        2     -4

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


Prepare doc to publish in website

Connected to https://github.com/vaadin/components-team-tasks/issues/205

This change is

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

docs/ng-cli-webpack.adoc, line 18 at r1 (raw file):

In this document we will describe all the modifications you have to make to your Angular CLI project to use Polymer elements.

[[vaadin-angular2-polymer.ng2cliwebpack.sysjs-note]]

Could this be systemjs-note? webpack isn't abbreviated either.

docs/ng-cli-webpack.adoc, line 118 at r1 (raw file):

----

Finally, change the main entry point of the application to load the new loader script. Edit the [filename]#angular-cli.json# file in the project root and  replace the line `"main": "main.ts",` with  `"main": "main-polymer.ts",`.

Can you change Finally word to something more appropriate?  There are still few chapters remaining and in there we use the word finally.

docs/ng-cli.adoc, line 21 at r1 (raw file):

.Note for the Angular CLI Webpack Version Users
====
If you are using the webpack version of the Angular CLI tool, please use the link:ng-cli-webpack.adoc[Using Polymer Elements in Angular CLI Webpack Applications] guide.

Can you remove Applications word? The title of the other page is now just Using in Angular CLI Webpack

Comments from Reviewable

I think, it’s better to publish the webpack guide instead of the SystemJS one, rather then in addition to.
Looks like npm install -g angular-cli installs the webpack version, currently. Also, in the latest angular-cli version number (1.0.0-beta.14), the -webpack suffix was dropped.
The other guide is not needed that much anymore. We can remove the docs webside data header from the old guide, and the cross references between them.

Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

the systemjs guide include how to deal with karma tests shouldn't we add that to the webpack guide ?

Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

@manolo the tests worked for me, those instructions were not required by the time I wrote the webpack guide. Please try if they still work.

Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

@platosha  When I run ng test after adding polymer elements I get these errors in console:
Chrome 52.0.2743 (Mac OS X 10.11.5) App: MyProject should create the app FAILED
	Can't bind to 'label' since it isn't a known property of 'vaadin-combo-box'.
	1. If 'vaadin-combo-box' is an Angular component and it has 'label' input, then verify that it is part of this module.
	2. If 'vaadin-combo-box' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.
...
...

Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 3 unresolved discussions.

docs/ng-cli-webpack.adoc, line 18 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Could this be systemjs-note? webpack isn't abbreviated either.

Done.

docs/ng-cli-webpack.adoc, line 118 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Can you change `Finally` word to something more appropriate?  There are still few chapters remaining and in there we use the word `finally`.

Done.

docs/ng-cli.adoc, line 21 at r1 (raw file):
Previously, samiheikki (Sami Suo-Heikki) wrote…
> Can you remove `Applications` word? The title of the other page is now just `Using in Angular CLI Webpack`

Removed this fil

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 4 unresolved discussions.

docs/ng-cli-webpack.adoc, line 312 at r3 (raw file):

----

=== Testing Polymer Elements

I would leave this chapter out. The text itself says this is discouraged and should not be done..

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 4 unresolved discussions, all commit checks successful.

docs/ng-cli-webpack.adoc, line 312 at r3 (raw file):
Previously, Saulis (Sauli Tähkäpää) wrote…
> I would leave this chapter out. The text itself says this is discouraged and should not be done..

Done.

Comments from Reviewable

Reviewed 1 of 2 files at r2, 1 of 1 files at r4.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable


Injection via delegate

I think that a really nice thing that can be done in Kotlin when it comes to dependency injection is that dependencies can be injected with delegates. I made a small thing that works like this, and essentially, this is what it would look like
fun main(args: Array<String>) {
    Injekt.configure {
        bind<DataSource> to {
            // get a data source here.
        }
    }
}

// OtherFile.kt
class OtherFIle {
    val ds: DataSource by inject()

}

The syntax doesn't have to be exactly like that, but I feel like something similar to that, where you can get dependencies with a delegate instead of passing a singular kodein instance to every class would be nice.

Hi,
have a look at https://salomonbrys.github.io/Kodein/#_the_god_complex_one_true_kodein
Salomon.


ln: failed to create symbolic link ‘/etc/nginx/nginx.conf’: File exists

Summary
Upgrade issue
Branch or installer

Installer: 0.16a3

Traceback or server.log snippet
pi@raspberrypi:~ $ sudo apt-get install ka-lite-raspberry-pi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libdrm-freedreno1 libdrm-nouveau2 libdrm-radeon1 libelf1 libllvm3.5
Use 'apt-get autoremove' to remove them.
The following packages will be upgraded:
  ka-lite-raspberry-pi
1 upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
Need to get 0 B/32.4 MB of archives.
After this operation, 58.3 MB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 139414 files and directories currently installed.)
Preparing to unpack .../ka-lite-raspberry-pi_0.16~a3-0ubuntu1_all.deb ...
Leaving 'diversion of /etc/nginx/nginx.conf to /etc/nginx/nginx.conf-ka-lite-raspberry-pi by ka-lite-raspberry-pi'
ln: failed to create symbolic link ‘/etc/nginx/nginx.conf’: File exists
dpkg: error processing archive /var/cache/apt/archives/ka-lite-raspberry-pi_0.16~a3-0ubuntu1_all.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/ka-lite-raspberry-pi_0.16~a3-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Fixed in #367


metadata-only-sync

Changes for performing metadata only sync using shunting yard.

Pull Request Test Coverage Report for Build 253

24 of 25 (96.0%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.1%) to 73.066%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shunting-yard-common/src/main/java/com/hotels/shunting/yard/common/event/ListenerEvent.java
2
3
66.67%

Totals

Change from base Build 250:
1.1%

Covered Lines:
765

Relevant Lines:
1047

💛  - Coveralls


XR Controllers not tracking at all

Godot version
4.1.1-stable
System information
Godot v4.1.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 (NVIDIA; <IP_ADDRESS>23) - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)
Issue description
Hello, I've been trying to make a VR game in Godot recently, and I've got an issue with the controllers. The problem is that the controllers aren't tracking at all (they always stay in the same position/rotation, no matter how I move them physically). I can move and rotate around the scene with the HMD, and the game starts properly, but the controllers aren't tracking no matter what I do. I also want to add that I'm using a custom SteamVR controller driver, but it works in other games.
Steps to reproduce

Open the minimal reproduction project
Run the game
Move the controllers

Minimal reproduction project
Minimal Reproduction Project.zip

Fixed the issue by changing the Prop_ControllerType_String in the SteamVR driver to vive_controller


Array.prototype.find() not listed

Hello! First time suggesting something here. First of all nice work, I frequently visit this page for reference!
I stumbled upon a function that is not found when searched, and it's this one: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find
Especially since IE does not support it.
Cheers, and any feedback on how to better format a request is greatly appreciated!
Daniel S.

duplicate of #1960

Thanks for the kind words, @dsegovia90 ! As mentioned, this request is already covered by #1960.


async https request (enable threads)

OS: Ubuntu bionic
    resolver_.async_resolve(
        host,
        port,
        beast::bind_front_handler(
            &session::on_resolve,
            shared_from_this()));
}

using meson build system (https://mesonbuild.com/).
After attaching the header files and libraries, I am unable to make a http request inside https://github.com/openbmc/phosphor-health-monitor/blob/master/healthMonitor.cpp

Attached Dependencies:

Version of Beast = 306

Has this program worked previously, or is this a new program that doesn’t work?


[FEATURE REQ] Cosmos per-request consistency level

Is your feature request related to a problem? Please describe.
We're getting ready to start using different levels of consistency based on what type of work we're doing. It does not seem like I can specify the level on the operation, though.
Describe the solution you'd like
It would be nice to be able to override the level for specific operations while still maintaining a default level at the client level.
Describe alternatives you've considered
In the absence of this feature, I will probably be using multiple clients which is not advisable for performance reasons according to you own documentation.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

@allenhumphreys Cosmos SDK do allow overriding to weaken the account consistency. Currently its scoped to the client instance.
As a work-around application can can maintain per consistency client instances and use appropriately.

As a work-around application can can maintain per consistency client instances and use appropriately.

@kirankumarkolli Yes, I know that. That's what I said in my post. This feature request is specifically to support per-request specification of the consistency level.

@allenhumphreys - Can you please explain more on your scenario with an example ?
Also, on a side note, SDK can only weaken the consistency which is specified at the account level.

@kushagraThapar We have applications that need to make both strongly consistent requests as well as session based consistent requests.
The split is between HTTP/user client operations and asynchronous events operations. The asynchronous event chains can cross regions resulting in a situation where the previous steps actions will not be available to the current step. However, for HTTP calls, the users location is static and will generally always be routed to the same region. For those calls, we'd like to lower our RU cost.
To achieve this in code, I was hoping to use the same CosmosAsyncClient instance but with different request options. That would be the most convenient for our code.
Thank you for letting me know that SDK can only weaken consistency levels, that seems like a pretty major limitation of the service, no? You might want to call that out in the documentation here https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels since you have to choose account-level strong consistency in order to use strong consistency anywhere.

@allenhumphreys thanks for the feedback.
We shall update/refresh the documentation.

@allenhumphreys - we do mention it here : https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#override-the-default-consistency-level
We are also planning to update the consistency level docs, thanks for your input.

@anfeldma-ms - I started an internal conversation with you and @SnehaGunda, Can you please follow up on this ?

@kushagraThapar are the docs refreshed?

@kirankumarkolli - yes the main conceptual doc now refers to the updated docs which highlight the part that account consistency can only be weaken through clients.

Since docs are refreshed, closing this issue now.


A11y_Azure Data Studio Nov2023_Files_Add Database File_ScreenReader: Name is not defined descriptively for Path section "More Option" button.

"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility or the Divisional Driver."
Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
GitHub Tags:
#A11yTCS; #A11yMAS; #A11ySev2; #DesktopApp; #WCAG4.1.2; #NameRoleValue; #FTP; #SH_Azure Data Studio_Nov2023_Linux_Dec2023; #SQL Azure Data Studio; #Linux; #ORCA;
Environment Details:
Application Name: Azure Data Studio
OS Name: Ubuntu 22.04.2 LTS
Azure data studio 1.47.0
Screen Reader: ORCA
Repro Steps:

Install Azure data studio application and open it
Make sure to enable "Preview" feature in settings.
Turn on ORCA.
Tab till "Database" and press ENTER to expand the tree.
Tab till any database and pressF10 to open context menu.
Tab till "Properties Preview" and press ENTER.
Tab till "Files" tab and press ENTER.
Tab till "Database files" table and press ENTER to select the row.
Tab till "Add" button and press ENTER.
"Add Database File" dialog will appear.
Tab till " more option" button in Path Section.
You will observe that voice over is announcing as "..., button" for more option button.

Actual Result:
ORCA is announcing as "..., button" for more option button present in "Path" section of "Add Database File" dialog.
Note: Similar issue is observed for Edit Database File ->Path section "More Option" button.
Expected Result:
ORCA should announce as "Path More option button" for button present in "Path" section of "Add Database File" dialog. The name for "more option" button should be described clearly to understand the purpose of control.
User Impact:
Screen Reader users will face difficulties to understand the purpose of the button if name is not descriptive enough.
Attachment:
25212.zip

Addressed by https://github.com/microsoft/azuredatastudio/pull/25233

@Swati1700 This has been fixed in the latest Ubuntu Insiders build of ADS here. Can you verify that the issue is fixed?

Verified the issue in the above build Version: 1.47.1
Issue is still reproducing, please find the repro attachment below.
Repro.zip

@Swati1700 can you please try testing with the latest insiders build? The build you tried did not yet have the fix.

Verified the issue in the below environment Version: 1.49.0- insider
Issue is fixed and does not repro. Please find the closing attachment below.
https://github.com/microsoft/azuredatastudio/assets/86710888/49997300-46a4-41c5-8403-1ef097c281cc


wrong link to access in v2.3.0 Release Notes

The link to access in the v2.3.0 Release Notes points to esda, not access.

Good catch

Good catch


Project: Project & Members Management System

Project name
ProjectEase
Description
ProjectEase is a project management application that helps us in managing project details, team members, and allocation of resources. It consists of three main components: Dashboard, Add/Edit Form, and Members Details.
Project Repository URL
https://github.com/GipsonRahul/ProjectEase
Project video
https://technorucs365-my.sharepoint.com/:v:/g/personal/gipsonrahul_j_technorucs_com/EWz_8g1LgpNPqDe3RM3943QBfpfSX-xSPfEe6byX7ZTQfQ?e=N3Z3W2
Team members
@GipsonRahul ,@Leowilson17 ,@DevarajP2713

Thank you for your project submission @GipsonRahul, we are looking forward to checking out your project! Would you and your teammates be willing to fill out the feedback survey? That'd help us learn from your experience and improve the hackathon next time: https://aka.ms/hack-together-teams/survey

Hi @GipsonRahul. thank you for your project submission. We cannot find your teammates @Leowilson17 ,@DevarajP2713 information in the registration list. Can you please make sure they register to the hackathon, otherwise they won't be eligible for the digital badge and other prizes. Registration can be completed from https://aka.ms/hack-together-teams/register

@aycabas Hi, should I register again with my teammates information or else they should register separately ?


Modify portfolio

Coverage remained the same at 85.83% when pulling fca57949159f4046164154192d6aa8e90e996b0d on JYL123:update_portfolio into 918947bafa4a2d01310427bd780679e3301b424f on CS2103AUG2017-W11-B1:master.


SITL test failures to investigate

https://github.com/PX4/Firmware/pull/15892/checks?check_run_id=1215051101

The failure seems intermittent: re-running the tests can make the tests fail / pass on different tests

The failure seems intermittent: re-running the tests can make the tests fail / pass on different tests

"Have you trying turning it off and on again?"

We should fix the ulg upload in these.

@dagar What do you mean by off/on? - I run the same tests in sitl_gazebo, and running it 3-4 times make it pass.

We need to investigate this, but not sure where to start

@julianoes what do you think about extending the mavsdk test runner (python) to also upload logs to flight review (with all metadata)? I think it would help debug failures if we could trivially compare flight review runs side-by-side (failure and last success).


URIError: Failed to decode param '%web_protocol%://<IP_ADDRESS>:%web_port%/webui/'

after installation I get the following error:
URIError: Failed to decode param '%web_protocol%://<IP_ADDRESS>:%web_port%/webui/'     at decodeURIComponent (<anonymous>)     at decode_param (/opt/iobroker/node_modules/express/lib/router/layer.js:172:12)     at Layer.match (/opt/iobroker/node_modules/express/lib/router/layer.js:148:15)     at matchLayer (/opt/iobroker/node_modules/express/lib/router/index.js:585:18)     at next (/opt/iobroker/node_modules/express/lib/router/index.js:226:15)     at compression (/opt/iobroker/node_modules/compression/index.js:220:5)     at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)     at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)     at /opt/iobroker/node_modules/express/lib/router/index.js:286:9     at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)
Versions:
ioBroker.webui: v0.11.0
ioBroker.admin: v6.10.1
ioBroker.docker: v8.1.0
Node.js: v18.17.1
NPM: 9.6.7

ioBroker.web was installed and everything is working.


feat: #5105 add pathname at the end of dropdown language url

Added pathname to keep the consistency of reading while changing language.
Closes https://github.com/webpack/webpack.js.org/issues/5105

Really nice feature. However there is one problem, say I'm browsing /concepts/plugins/#usage and want to check the respective Chinese version, clicking the button would bring me to chinese-site/concepts/plugins/ instead of chinese-site/concepts/plugins/#usage.
I think we should retain the URI fragment as well, just like how we did when changing the version of webpack documentation:

Here's the code https://github.com/webpack/webpack.js.org/blob/master/src/components/Sidebar/Sidebar.jsx#L25 just in case you want to take a look.

Btw, can you sign cla here https://cla.js.foundation/webpack/webpack.js.org?pullRequest=5108?

@chenxsan I've signed! 😀

Really nice feature. However there is one problem, say I'm browsing /concepts/plugins/#usage and want to check the respective Chinese version, clicking the language button would bring me to chinese-site/concepts/plugins/ instead of chinese-site/concepts/plugins/#usage.
I think we should retain the URI fragment as well, just like how we did when changing the version of webpack documentation:

Here's the code https://github.com/webpack/webpack.js.org/blob/master/src/components/Sidebar/Sidebar.jsx#L25 just in case you want to take a look.

Good catch! what if I pass location.hash as a prop to use it on Navigation?

I just found a bug in the current implementation.
Here's how to reproduce:
Open https://webpack-js-org-git-fork-cs09g-feature-issue-bdc88a-webpack-docs.vercel.app/concepts/entry-points/#multi-page-application, then change the version. You'll see the URI fragment is missing.

@chenxsan Hmm, the hash is missing. Is that based on the last commit on this PR? Or is something different on the build with on localhost?

We have this preview https://github.com/webpack/webpack.js.org/pull/5108#issuecomment-867109431 synced with the latest commit of current pull request, so the preview should be up to date.
The build is actually a server-side rendered first, then hydrated on client-side app. So, yes, it's not the same as the dev one on localhost.

@chenxsan I've pushed one more commit after the preview generated. I guess it's fine with the next deployment. check this out. https://webpack-js-org-1ozc7s86g-webpack-docs.vercel.app/

Neither does it work. You can open https://webpack-js-org-1ozc7s86g-webpack-docs.vercel.app/concepts/entry-points/#multi-page-application to inspect.
But I did notice the discrepancy here:

The href prop in React virtual DOM is up to date, however the real DOM is stale.
So the problem could be hash is client side only, and it's not hydrated on client side causing the issue. How about handling it with useEffect?

I got it. I could check this out with `yarn build-test' on localhost. By the way, It's a class component. It needs to be refactored.

@cs09g Seems the CLA is not signed, can you double check?

@chenxsan I did. Some of my commits pushed as different emails with Github. Should I re-commit with the email that I signed in CLA?

@chenxsan I did. Some of my commits pushed as different emails with Github. Should I re-commit with the email that I signed in CLA?

Yeah, the bot is not that smart to handle it.

@chenxsan Thanks for the warm review!


Use all fields in DnsCovertChannel and TorConnection event

aicers/hog#404
There is a Triage process in PT project, and it requires all fields of detected event in the processing.

Add fields to

DnsCovertChannel, TorConnection from Hog
HttpThreat from REconverge

Migration function for the changed fields

Superseded by #48 and #49, which contain more information about tasks.


add use_autoscaler config for AutoSaler prod rollback

Signed-off-by: guo-shaoge<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: close #6701
Problem Summary:

https://github.com/pingcap/tiflash/pull/6588 removed proxy when node is in tiflash_compute mode, so all tilfash_compute nodes will be managed by AutoScaler instead of PD.
AutoScaler is not stable for now, we want to add switcher to help roll back.

What is changed and how it works?

Check if use_autoscaler corresponding to each change in https://github.com/pingcap/tiflash/pull/6588

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/merge


chore: release 1.1.0

:robot: I have created a release *beep* *boop*
1.1.0 (2022-09-30)
Features

add helpers that handle string (3023a2b)
support block helpers (1a4e54f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/handlebars-ramda-helpers/releases/tag/v1.1.0 :sunflower:


update_admin_profile fails in the presence of managed Opportunity Record Types

To reproduce, install a package (such as rC_Giving) which contains managed Opportunity Record Types in a scratch org. Then, run
cci task run update_admin_profile

ensuring that the default CCI admin_profile.xml is used.
Obtain as result, for example,
Error: Update of BusinessProcess Opportunity.rC_Giving__Donation: Error on line 60, col 24: Required field is missing: values

Update of BusinessProcess Opportunity.rC_Giving__Membership: Error on line 96, col 24: Required field is missing: values

Update of BusinessProcess Opportunity.rC_Giving__Outright Gift: Error on line 100, col 24: Required field is missing: values

Update of BusinessProcess Opportunity.rC_Giving__Pledge: Error on line 105, col 24: Required field is missing: values

Update of BusinessProcess Opportunity.rC_Giving__Pledge Payment: Error on line 110, col 24: Required field is missing: values

Update of BusinessProcess Opportunity.rC_Giving__Purchase: Error on line 131, col 24: Required field is missing: values

Update of BusinessProcess Opportunity.rC_Giving__Transaction: Error on line 135, col 24: Required field is missing: values

As the package contains other, custom objects with managed record types that do not cause errors, and seeing a BusinessProcess-related message, the issue appears to be specific to those sObjects whose Record Types have associated Business Processes:

Opportunity
Lead
Case
Solution

This issue as written is a misdiagnosis of the problem. The actual underlying issue is that packages are permitted to deploy in a state where their metadata is rejected upon an update by the Metadata API.
The issue can be generated with the following circumstances:

Package A includes a Record Type, say Opportunity.Donation, on an sObject that uses Business Processes.
The associated Business Process includes only values that are not part of the standard value set for StageName (or the relevant field).
The package is installed directly via link or CCI task, and does not deploy any unpackaged metadata to update the StandardValueSet.

In that situation, the package installation succeeds, yielding a Business Process with no values:

However, the metadata for this Business Process and its associated Record Type are not redeployable once extracted, as is practiced by update_admin_profile.
Possible remedies:

Detect an empty values list on a Business Process and raise an exception.
Avoid directly installing package versions.


Add configurable data stores to the server.

This (large) PR implements a new --store option to the server.
The option defaults to memory, which stores logs and checkpoints in memory which will be lost when the server shuts down.
With the postgres feature enabled, it also supports a postgres store option which requires the DATABASE_URL environment variable to point at the PostgresSQL server to use.
The postgres store supports restarting the server and recreating the necessary data structures for the transparency service to work.
See crates/server/README.md for information on how to setup a persistent PostgresQL store.

@Kylebrown9 want to sync up tomorrow to do a high-level review walk-through before you dive into it?


Fix console syntax for highligting

minor
@bgrant0607

That's totally obscure. We're going to need to document all of these tricks at some point.

Actually, this didn't fix the problem, at least not when I view it.

Yeah, the commands are just as blue as the output:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/user-guide/debugging-services.md


Midi out?

Do you implemt in future midi out
Like midi note or cc?
Would be helpful!

While I agree that this could be useful, it wouldn't be just a matter of implementing this in the plugin (the original of version of Rack does not support MIDI out) -- I'd also have to develop a new Rack module.
Besides, since none of the DAWs I use support MIDI out from VSTs, I have no plans for developing this.
There are some workarounds, though:

In a DAW like Reason, it is easy to convert one or more plugin audio outputs to "CV" signals (e.g. via "Thor") (and then to MIDI if necessary)
There might be a VST plugin that does a similar thing in other DAWs (i.e. audio to MIDI -- but not of the pitch detection variety)
You could use the trowaSoft.cvOSCcv OSC (open sound control) module, in combination with maybe https://github.com/fred-dev/OSC_MIDI_OSC for the MIDI conversion


txfunc.py output

The output from txfunc.py should be sure to include mean adjusted total income for each year in the budget window.  We need this to get our scaling factor in the OG model correct.
cc @rickecon

@jdebacker . OK, I'll add a 10-element numpy array with average total income to the dictionary in the pickle that txfunc.py outputs. That will be in my next PR.

@jdebacker . Should we compute average income with the outliers removed, as we do to estimate the functions? Or should we leave them in. My inclination for computing average income is to leave the outliers in.

@rickecon That's right, with outliers in.  I thought we only censored with negative and very tiny income amounts, so that we didn't have extremely large positive or negative AETRs (i.e., we left in large income values).  In any case, yes, let's calculate average adjusted total income in each tax year over the full sample.

@jdebacker. In my most recent pull request, the average total incomes are computed and saved in a pickle. We can close this issue if you are satisfied with the output.


Implemented Cron Job source

Used Deployment as receive adapter instead of CronJob because of
the batched job side car issue.
https://github.com/kubernetes/kubernetes/issues/25908
If this issue is resolved in the future, we can switch to use CronJob.
Proposed Changes

Provide Cron based event source support without external dependencies.

.

I signed it!

/ok-to-test
On Fri, Nov 30, 2018 at 4:32 PM googlebot<EMAIL_ADDRESS>wrote:

We found a Contributor License Agreement for you (the sender of this pull
request), but were unable to find agreements for all the commit author(s)
or Co-authors. If you authored these, maybe you used a different email
address in the git commits than was used to sign the CLA (login here
https://cla.developers.google.com/ to double check)? If these were
authored by someone else, then they will need to sign a CLA as well, and
confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull
request author add another comment and the bot will run again. If the bot
doesn't comment, it means it doesn't think anything has changed.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/knative/eventing-sources/pull/134#issuecomment-443380830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHlyN11lv1CEl-vBt8jqiozr_YLqOrHvks5u0c4agaJpZM4Y8lZG
.

--
Evan Anderson<EMAIL_ADDRESS>

Sorry, I'll fix the CLA issue and re-send the PR.


Support for comments inside JSDoc @example comments

Suggestion
🔍 Search Terms:
comments inside jsdoc, jsdoc inception
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
I am writing a custom helper type that allows me to provide JSDoc comments for properties of any other object or interface that is inaccessible for changes.
I need to document the feature and usage, but I can't close a comment section inside JSDoc comment's.
Code:

/**
 * This type allows to add JSDoc annotation to any type without causing conflicts.
 *
 * @example
 * type IconButtonProps =
 *  & JSDoc
 *  & ShorthandVariantsAndSizes
 *
 * type JSDoc = Documentation<ShorthandVariantsAndSizes, {
 *  /**
 *   * **variant**: Color theme for the button.
 *   * - `light` variant is white on all themes.
 *   \*\/
 *   variant?: unknown  // <- note: this `?: unknown` optional type is important
 * }>
 */
type Documentation<T, TargetType extends { [K in keyof T]?: unknown }> = TargetType

JSDoc invoked:

💻 Use Cases
Desired:

Result:

📃 Motivating Example
const sizeKeys = ['small', 'karge',] as const

// this is a mapped type and therefore doesn't allow to add JSDoc comments
type ExplodedSizes = { [key in typeof sizeKeys]?: boolean }

type JSDoc = Documentation<ExplodedSizes, {
  /**
   * **size**: Button size.
   * - `64px`
   */
  large?: unknown
  /**
   * **size**: Button size.
   * - `32px`
   */
  small?: unknown
}>

// this merges the jsdoc annotation with correct types
export type IconButtonProps =
  & JSDoc
  & ExplodedSizes

export const IconButton: React.FC<IconButtonProps> = (props) => <> </>

// later when using the component
const render = <IconButton /> // <- gets correct intellisense with JSDoc comments here

https://github.com/microsoft/TypeScript/issues/47679 is related. https://github.com/microsoft/TypeScript/pull/50677 has a tenative fix, but we haven't discussed it much recently. I don't recall if it supports \ escaping.

@DanielRosenwasser I don't think it does, but it was the most intuitive solution for the reader when I accept that it doesn't work. Using non-functioning escaping still conveys the message to the next developer who reads the documentation, so it was the best solution.
I tried various different combinations with spaces, multiple * or multiple /, etc.

Heads up, I found a neat workaround that is not ideal due to syntax highlight, but it does produce a little clearer output.
/**
 * This type allows to add JSDoc annotation to any type without causing conflicts.
 *
 * @example
 * type IconButtonProps =
 *  & JSDoc
 *  & ShorthandVariantsAndSizes
 *
 * type JSDoc = Documentation<ShorthandVariantsAndSizes, {
 *  /★★
 *   * **variant**: Color theme for the button.
 *   * - `light` variant is white on all themes.
 *   ★/
 *   variant?: unknown  // <- note: this `?: unknown` optional type is important
 *   // ... other props
 * }>
 */
type Documentation<T, TargetType extends { [K in keyof T]?: unknown }> = TargetType

The result is that the "comment" now looks weird with that syntax highlight, but the important bit, "variant?: unknown" doesn't look as a comment as in original screenshot and looks as a property.

See prior discussion https://github.com/microsoft/tsdoc/issues/166#issuecomment-809883492 .


Correct doc for VirtualOutput

pyecodevices-rt2 version: all
Python version:
Operating System:

Description
Doc for VirtualOuput shows a sensor, but it is a switch.
What I Did
Take this example:
from pyecodevices_rt2 import EcoDevicesRT2, VirtualOutput

ecodevices = EcoDevicesRT2('<IP_ADDRESS>','80',"mysuperapikey")
print("# ping")
print(ecodevices.ping())

# Relay number 1
test = VirtualOutput(ecodevices, 1)
print("Current status: %r" % test.status)
test.off() # Change relay to off
test.on() # Change relay to on
test.toggle() # Invert relay status
test.status = True # Change relay to on

Resolved in #5


Yep that's me -- please file an issue with vim-language-dept/css-syntax.vim

    Yep that's me -- please file an issue with `vim-language-dept/css-syntax.vim`

Originally posted by @jsit in https://github.com/vim/vim/issues/11472#issuecomment-1301081649

Oops, created by miskatke.