jest occasionally tries to transform json files

Current Behavior
Once in while I get the following warnings when I run 'tsdx test' command:
ts-jest[jest-transformer] (WARN) Got a unknown file type to compile (file: /Users/smashercosmo/Documents/projects/tmp-babel-plugin/node_modules/@babel/core/package.json). To fix this, in your Jest config change the `transform` key which value is `ts-jest` so that it does not match this kind of files anymore.
ts-jest[jest-transformer] (WARN) Got a unknown file type to compile (file: /Users/smashercosmo/Documents/projects/tmp-babel-plugin/node_modules/resolve/lib/core.json). To fix this, in your Jest config change the `transform` key which value is `ts-jest` so that it does not match this kind of files anymore.
ts-jest[jest-transformer] (WARN) Got a unknown file type to compile (file: /Users/smashercosmo/Documents/projects/tmp-babel-plugin/node_modules/globals/globals.json). To fix this, in your Jest config change the `transform` key which value is `ts-jest` so that it does not match this kind of files anymore.

Expected behavior
jest shouldn't try transforming json files
Suggested solution(s)
Probably 'json' should be added to transformIgnorePatterns in jest config
Your environment

Software
Version(s)

TSDX
0.7.2

TypeScript
3.5.2

npm
6.9.0

Operating System
macOS Sierra 10.12.3

Is this still happening?

I'll check

Still getting this warnings with latest tsdx

I'm still finding this with v0.11.0. This usually occurs on the first run and then not again until the next build.

I am still seeing this issues in v0.12.3

Fixed by #513 . It will be out in the next release


Reset Apollo Store [WIP]

[ ] Test in example apps
[ ] Write documentation

I think this needs a lot more testing to find out what happens when a reset action is fired while someone is holding on to a watchQuery subscription, or the client is in the middle of a query/mutation. That's the part I'm most worried about - we should make sure the store doesn't end up borked, and there aren't unnecessary exceptions thrown, if there is an unexpected reset.

Yes definitely will test! One question should users be able to dispatch whatever reset value they want? Right now we make an assumption it resets to the empty objects.

Hmm, I feel like we should implement the simple thing first and see if people need that feature later.

Hey @stubailo im having trouble installing this specific branch into an example app? Any clues?

What troubles are you running into? It could be related to the new deploy script.

Im trying to use the module in the examples apps to try and break them. But i dont think im doing it right?

Are you using npm link? That's usually the way to do this stuff.

Just as you presumed @stubailo, it blows up! Time to fix

@abhiaiyer91 Are you still working on this PR? Or is it blocked by something else?

Hey @helfer was on vacay! Just need time!

I'll focus on this today since it is blocking Tim (he has a workaround for the timebeing but it can solved much more nicely).

I'll focus on this today and see if I can make some progress.

Closing this in favor of #314


Invalid positions error when trying to add 'Min Exposure' and 'Max Exposure' columns to player pool CSV

When I run the optimizer using a default CSV I get no errors.
I see in the documentation:
"You can add “Max Exposure” and “Min Exposure” columns with exposure percentage for some players to csv that will be parsed while players loading. "
So I've attempted to add exposure columns and use a CSV with this format:
Position,Name + ID,Name,ID,Roster Position,Salary,Game Info,TeamAbbrev,AvgPointsPerGame,Min Exposure,Max Exposure
PG,Luka Doncic (25007692),Luka Doncic,25007692,PG/G/UTIL,12000,DAL @ BKN 2022-10-27T23:30:00.0000000Z,DAL,60.23,0.2,0.4
PG,Ja Morant (25007695),Ja Morant,25007695,PG/G/UTIL,10200,MEM @ SAC 2022-10-28T02:00:00.0000000Z,MEM,55.67,0.15,0.25
SF/PF,Kevin Durant (25007698),Kevin Durant,25007698,SF/PF/F/UTIL,10000,DAL @ BKN 2022-10-27T23:30:00.0000000Z,BKN,48.26,0.05,0.2
PG,Stephen Curry (25007702),Stephen Curry,25007702,PG/G/UTIL,9900,MIA @ GSW 2022-10-28T02:00:00.0000000Z,GSW,52.67,0.05,0.14
PG/SF,Ben Simmons (25007747),Ben Simmons,25007747,PG/SF/G/F/UTIL,6400,DAL @ BKN 2022-10-27T23:30:00.0000000Z,BKN,28.96,0.05,0.2
...

This results in the invalid position constraints:
pydfs_lineup_optimizer.exceptions.GenerateLineupException: Can't generate lineups. Following constraints are not valid: positions_PG,positions_PG_SG,positions_PG_SF,positions_PG_SF_SG
Am I adding the columns to the CSV incorrectly, or making some other error here? If not, is there a way around this issue? Like I said, I don't get any error with my positions definition before trying to add the 'Min Exposure' and 'Max Exposure' columns to the end of the CSV. Any help would be appreciated, thanks.

Let's see your csv
On Thu, Oct 27, 2022, 7:45 PM Chris Miller @.***> wrote:

When I run the optimizer using a default CSV I get no errors.
I see in the documentation:
"You can add “Max Exposure” and “Min Exposure” columns with exposure
percentage for some players to csv that will be parsed while players
loading. "
So I've attempted to add exposure columns and use a CSV with this format:
Position,Name + ID,Name,ID,Roster Position,Salary,Game Info,TeamAbbrev,AvgPointsPerGame,Min Exposure,Max Exposure
PG,Luka Doncic (25007692),Luka Doncic,25007692,PG/G/UTIL,12000,DAL @ BKN 2022-10-27T23:30:00.0000000Z,DAL,60.23,0.2,0.4
PG,Ja Morant (25007695),Ja Morant,25007695,PG/G/UTIL,10200,MEM @ SAC 2022-10-28T02:00:00.0000000Z,MEM,55.67,0.15,0.25
SF/PF,Kevin Durant (25007698),Kevin Durant,25007698,SF/PF/F/UTIL,10000,DAL @ BKN 2022-10-27T23:30:00.0000000Z,BKN,48.26,0.05,0.2
PG,Stephen Curry (25007702),Stephen Curry,25007702,PG/G/UTIL,9900,MIA @ GSW 2022-10-28T02:00:00.0000000Z,GSW,52.67,0.05,0.14
PG/SF,Ben Simmons (25007747),Ben Simmons,25007747,PG/SF/G/F/UTIL,6400,DAL @ BKN 2022-10-27T23:30:00.0000000Z,BKN,28.96,0.05,0.2
...
This results in the invalid position constraints:
pydfs_lineup_optimizer.exceptions.GenerateLineupException: Can't generate
lineups. Following constraints are not valid:
positions_PG,positions_PG_SG,positions_PG_SF,positions_PG_SF_SG
Am I adding the columns to the CSV incorrectly, or making some other error
here? If not, is there a way around this issue? Like I said, I don't get
any error with my positions definition before trying to add the 'Min
Exposure' and 'Max Exposure' columns to the end of the CSV. Any help would
be appreciated, thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/385, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7WHNLY47FRTPRQLFDTWFMHYXANCNFSM6AAAAAARQRXNNE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Probably you set exposures in a way that lineups can't be built


Add note about bundled protos not needing import SwiftProtobuf.

@tbkka want me to pull this to 1.x also?


cardano-db-sync crashes & enters restart death-loop while starting at a certain epoch

OS
Your OS: Windows (WSL Ubuntu)
Versions
The db-sync version (eg cardano-db-sync --version): 12.0.2
PostgreSQL version: postgres:11.5-alpine (Docker Image)
Build/Install Method
The method you use to build or install cardano-db-sync: inputoutput/cardano-node:1.34.1 docker image running inside a Kubernetes Pod
Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): Docker
Additional context
Db-Sync container restarts many times during it's lifecycle, the cardano-node & cardano-db-sync are on the same server while cardano-db-sync connects to a remote Postgresql pod.
Problem Report
My cardano-db-sync docker container running in a Kubernetes Stateful deployment hangs while trying to insertShellyBlockl(Alonzo) after acouple seconds the container crashes and restarts only to crash again. My Postgres container logs the following line once db-sync crashes --> unexpected EOF on client connection with an open transaction
LOGS [ Before Crash ]
[db-sync-node:Info:57] [2022-06-08 02:13:50.90 UTC] Starting at epoch 178
[db-sync-node:Info:57] [2022-06-08 02:13:51.04 UTC] Handling 83242 stakes for epoch 178 slot 46632114, hash bd30a5f7391cc770c7c56531aaae66f1c628f28b5f9a08553669b1e105a813db
[db-sync-node:Info:57] [2022-06-08 02:14:05.88 UTC] insertShelleyBlock(Alonzo): epoch 178, slot 46632114, block 3200000, hash bd30a5f7391cc770c7c56531aaae66f1c628f28b5f9a08553669b1e105a813db
[db-sync-node:Info:57] [2022-06-08 02:14:12.18 UTC] insertEpochInterleaved: Epoch 178, 83242 stake addresses
/nix/store/4afrd31xx9iljzn2hd8i6b03h7v5gh1g-cardano-db-sync-testnet/bin/cardano-db-sync-testnet: line 3:    17 Killed                  /nix/store/51xj9nf405brglw1p42jwnx27n3z8sak-cardano-db-sync $@

Might be good to add docker tag to these, unfortunately lot of issues that are often related to resource/sizing/connectivity get mixed up here.

The Killed message usually indicates a problem with recourses. Maybe the out of memory killer killed db-sync? This should be apparent in kernel logs.

@kderme Could restricting container resources cause a crash like this?

It ended up being that docker wasn't giving enough resources to the container so at a certain point the cardano-db-sync would just crash. I got a new Linux Workstation and it's working really well with 64GB of ram on the host machine


[Improve][flink-api]extraction unified method

Purpose of this pull request

extraction unified method
Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

CI is error ,and i think it's because the JdbcPostgresIT and JdbcMysqlIT are unstable.and i tested it locally and the error also happen. so i fix it in #2907 .

CI is error ,and i think it's because the JdbcPostgresIT and JdbcMysqlIT are unstable.and i tested it locally and the error also happen. so i fix it in #2907 .

@EricJoy2048 please rerun CI,thanks. CC @ic4y

#2907

Ok, I will rerun the failed job after the https://github.com/apache/incubator-seatunnel/pull/2907 been merged.

Hi,please rerun CI. @EricJoy2048

please rerun CI. @EricJoy2048


FLAKE: cpp_macos_dbg_native.bins/dbg/bm_chttp2_transport --benchmark_filter=BM_StreamCreateSendInitialMetadataDestroy$  GRPC_POLL_STRATEGY=poll

https://source.cloud.google.com/results/invocations/bbca8bb1-4f47-4c61-9687-169e1a79f966/targets/github%2Fgrpc%2Frun_tests%2Fcpp_macos_dbg_native/tests
D0930 14:29:08.202689000<PHONE_NUMBER>75744 ev_posix.cc:174]              Using polling engine: poll
D0930 14:29:08.204061000<PHONE_NUMBER>75744 dns_resolver_ares.cc:485]     Using ares dns resolver
2019-09-30 14:29:08
Running bins/dbg/bm_chttp2_transport
Run on (8 X 2473 MHz CPU s)
CPU Caches:
  L1 Data 32K (x8)
  L1 Instruction 32K (x8)
  L2 Unified 262K (x8)
  L3 Unified 6291K (x8)
Load Average: 6.32, 6.16, 5.51
***WARNING*** Library was built as DEBUG. Timings may be affected.
third_party/benchmark/src/benchmark_runner.cc:120: RunInThread: Check `st.iterations() >= st.max_iterations' failed. Benchmark returned before State::KeepRunning() returned false!

All of the failures are in bm_chttp2_transport. The failure is due to an issue with how the benchmark is written. The issue is that we were exiting the benchmark before the work was actually done. This was happening because the closures were getting scheduled on the executor thread, which meant that the main thread could exit. The fix was to add a simple cond var wait to not exit till the benchmark work is done.


knife help environment shows wrong example

Description
knife help environment shows following example

Examples
To add an environment using data contained in a JSON file:
$ knife environment create devops from file "path to JSON file"

knife-environment.1
should be
knife environment from file "path to JSON file"
Chef Version
chef-12.14.77-1.el7.x86_64
Platform Version
RHEL7
Replication Case
knife help environment
search for the following string
/environment create devops from file

Closed by #5684


RFC: track modules as git submodules

This is a request for comments from all potential users regarding the following question:
Should glyph modules be tracked as submodules?

Pros

Allows identifying every file in your archive by a hash/path combination
Clarifies which version of which file was meant in links etc.
Git native → less vendor lock-in
When commits in the top repo are signed, they convey a chain of trust down to the deepest nested repo.
Allows seeing all changes just by using git log -p --submodule → easier to look at changes in retrospective

Cons

A very large count of 'updated submodule' commits that don't convey useful information
Higher probability of git submodule merge conflicts

Another idea would be to use the glyph config to track which glyph modules that exist in the archive and use the glyph cache to save which of these modules are initialized. This would also allow updating the modules more automatically.

@masukomi I'd especially like input from you, as you showed interest in the general idea before.

After some consideration I decided to keep glyph modules as git submodules and add a new type of glyph module called “user scripts” which are tracked directly in the main repo.
Together with a custom .gitignore users can use these scripts to implement all the additional content management they need.

well. i 100% missed this, and it's obviously too late, BUT... as much as i dislike the implementation of git submodules I think this is the right call.

After testing the git submodule approach, I decided to take a new approach I'm creatively calling "Glyph 2.0" (it's more like a 0.2.0, long live 0ver).
Glyph modules will be tracked as independent git repos wholly managed by their module script, glyph only sits in the middle and manages their location, CLI interaction, and sync.  The goal for glyph is more of a very simple platform that exposes a few useful functions like a global file based config to other modules.
For devices like android phones, an approach using git work trees will also be supported.
This change will also improve the integration with external tools like Git Journal, Obsidian and Co significantly.
I will also carry over this change in philosophy into the example modules.
Important to note here that the biggest disadvantages of this change are performance and maybe security.

Performance is lost mostly during sync as the sync complexity changes from $O(1)$ git fetch operations to $O(n)$ fetches
Security in the form of only having the trust the (maybe signed) commits in the main repo is also lost


85 update docs due to integration with heroku

Closes #85

Codecov Report

Merging #86 (c21da27) into release-candidate (29e6228) will not change coverage.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           release-candidate       #86   +/-   ##
===================================================
  Coverage             100.00%   100.00%
===================================================
  Files                     58        58
  Lines                   1560      1560
===================================================
  Hits                    1560      1560

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


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_dc68a3a7-c26e-4b72-a618-d7f1765537cc/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_dc68a3a7-c26e-4b72-a618-d7f1765537cc.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-02-21-03-50-21 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-02-21-03-50-21

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


v4.7.0 introduces instance variables that do not play well with ActiveSupport's to_json

Starting in  6f7b94b159078dcf0a4c832e42ffc256f90e5253 and released in 4.7.0, the ActiveModelDirtyBackport module is injected into classes that don't respond to clear_changes_information. As suggested by the name, this covers classes that have nothing to do with ActiveModel.
Unfortunately, this conflicts with ActiveSupport's implementation of as_json / to_json, as it falls back to using all the instance variables.
This demo should help explain:
require 'factory_girl'

require 'active_support/core_ext/object/json'
require 'active_support/hash_with_indifferent_access'
require 'active_support/json'

class Customer
  attr_accessor :id
end

FactoryGirl.define do
  factory :customer
end

customer = FactoryGirl.build_stubbed(:customer)
puts customer.to_json
# => {"id":1001,"previously_changed":{},"changed_attributes":{}}

customer = Customer.new
puts customer.to_json
# => {}

When constructed through factory_girl, the unexpected attributes previously_changed and changed_attributes now show up.

One workaround is to explicitly ignore these attributes when generating JSON. This only really makes sense when directly doing so in a test, and not scattering this throughout the production code.
foo.as_json(except: ['previously_changed', 'changed_attributes'])

@shepmaster that's... frustrating. I can see the line of reasoning that makes instance variables seem appealing as an implementation for #to_json, but in this case, I see your point that it's causing problems.
Seems like it might be better to override the offending method with the behavior you want instead of managing a list of attributes you don't, e.g. defining to_json on your object and exposing only what you want on the class?

e.g. defining to_json on your object

Could be a reasonable solution for some people, but in this case it's a third-party class from a gem. When they (and most people?) designed their class, I assume they believed they'd be in control of which instance variables would be present in their own class, thus saying "all instance variables" is reasonable.
Is there a way to disable the monkey-patched dirty tracking for a given class / factory?

Could be a reasonable solution for some people, but in this case it's a third-party class from a gem. When they (and most people?) designed their class, I assume they believed they'd be in control of which instance variables would be present in their own class, thus saying "all instance variables" is reasonable.

Excellent point, I hadn't thought about that. I was operating under the assumption the factory was for something the developer controls and not an external library.

Is there a way to disable the monkey-patched dirty tracking for a given class / factory?

Currently, now. @quadule, do you have any thoughts here having dug through some of the intricacies of the dirty handling? Since this is dependent on ActiveModel, I wonder if we can look at the object's ancestors (versus checking to see if it responds to #dirty?, whose interface could be present but not come from ActiveModel) and conditionally include based on that as well?

This seems like the simplest solution:
def clear_changes_information
  if defined?(@previously_changed) && defined?(@changed_attributes)
    @previously_changed = ActiveSupport::HashWithIndifferentAccess.new
    @changed_attributes = ActiveSupport::HashWithIndifferentAccess.new
  end
end

I'm a little unclear on the purpose of using build_stubbed on something besides an ActiveRecord model, but if that should be supported then @sgrif's solution looks good.
It could check for ActiveModel::Dirty ancestry instead, but the stub strategy doesn't check for ActiveRecord ancestry before stubbing the persistence methods.
clear_changed_attributes_on_result(instance) if instance.kind_of?(ActiveModel::Dirty)


Preserve multiindex

Fix for #215

[x] test added
[ ] whatsnew
[ ] pre-commit

@pre-commit autoupdate

LGTM. Thanks. I'll deal with pre-commit later and there's no whats-new needed :)


Add statuspage_io pack

statuspage io
Status

new pack, work in progress

Description
A pack for interacting with the statuspage.io service.
Checklist (tick everything that applies)

[X] Metadata: pack.yaml, icon, structure (required for new packs)
[ ] Code linting (required, can be done after the PR checks)
[ ] Tests (not required but really recommended)

Please can you squash your commits before this can be merged

@tonybaloney :laughing:

@Kami ¯_(ツ)_/¯

@jjm new rules. didn't you get the memo?

@tonybaloney I don't think I can get it to 20+ commits ;-P so your most likely safe in 3rd place for commits.

@jjm one of my packs has a bug, pretty sure I can fix that in <50 commits

I've not had time to work on finishing this pack and it's sometime before I will be able to get it into a useful & merge-able state....
So I think I'll just when we get to the point of StackStorm Exchange being ready.

Thanks fine.
If you don't mind, I will close this PR and you can open a new one against a new StackStorm-Exchange repo once it's up.

Closing, I'll come back to it later when StackStorm-Exchange is live.


Use _get_distribution_strategy only when it is available.

The changes introduced in https://github.com/tensorflow/tensorflow/commit/06d8f77bcc43826eb2b30209a73f3c833079edbc are not compatible with standalone Keras (they are compatible with tf.Keras). a keras.Model does not have a _get_distribution_strategy method, which is now assumed for the Tensorboard callback.
These kind of differences are usually not an issue, but Keras is using tf.keras.callbacks.Tensorboard instead of implementing its own.
This PR checks if _get_distribution_strategy exists and uses it if it does, making it compatible with a keras.Model.

Done :+1:

@hgaiser Can you please check reviewer comments and keep us posted. Thanks!

Apologies, I forgot to update the PR. It is updated now though :+1:

@rchao Can you please take a look on this PR? Thanks!

I cant get Tensorboard to work when using https://github.com/fizyr/keras-retinanet. @hgaiser is it fixed with this commit?

I cant get Tensorboard to work when using https://github.com/fizyr/keras-retinanet. @hgaiser is it fixed with this commit?

Should be, yes.

I cant get Tensorboard to work when using https://github.com/fizyr/keras-retinanet. @hgaiser is it fixed with this commit?

Should be, yes.

I am experiencing the same error as here: https://github.com/fizyr/keras-retinanet/issues/1239
Should have the latest version installed.
Just to get it right: Is the commit not merged yet? And is that why the error is still occurring?

It's not merged yet, so unless you applied this branch yourself you're not using this fix.

It's not merged yet, so unless you applied this branch yourself you're not using this fix.

It works - Thank you!

Still happening. I am using a pip installed version.
!pip freeze | grep -iE "tensorflow|keras"
gives
Keras==2.3.1
Keras-Applications==1.0.8
Keras-Preprocessing==1.1.0
tensorflow==2.1.0
tensorflow-estimator==2.1.0

Am I not using the latest??
$ pip search tensorflow
tensorflow (2.1.0)                                - TensorFlow is an open source machine learning framework for everyone.
  INSTALLED: 2.1.0 (latest)
tensorflow-qndex (0.0.22)                         - tensorflow-qnd x tensorflow-extenteten

A Tensorflow update is missing for tid to work, so you need to go edit the callbacks.py file with the edit of this commit to get it to work at the moment. In your local Tensorflow installation just replace the entire callbacks.py file.

thank you for your reply. I download tensorflow-master from here:
https://github.com/tensorflow/tensorflow
and I replaced the callbacks.py file but now get this error:
ImportError: cannot import name 'profiler_v2' from 'tensorflow.python.profiler' (/home/stefan/miniconda3/envs/TFg/lib/python3.7/site-packages/tensorflow_core/python/profiler/__init__.py)

I found profiler v2 and copied it over. Now I get this error
ImportError: cannot import name '_pywrap_profiler' from 'tensorflow.python.profiler.internal' (/home/stefan/miniconda3/envs/TFg/lib/python3.7/site-packages/tensorflow_core/python/profiler/internal/__init__.py)
There is an init.py file inside 'internal'

Now, when I get to this step
#train for 50 epochs
autoencoder.fit(x_train, x_train,
                epochs=50,
                batch_size=256,
                shuffle=True,
                validation_data=(x_test, x_test),
                verbose=1)

I get this error
`ImportError: cannot import name '_pywrap_profiler' from 'tensorflow.python.profiler.internal' (/home/stefan/miniconda3/envs/TFg/lib/python3.7/site-packages/tensorflow_core/python/profiler/internal/init.py)
notice there are no callbacks to tensorboard-this is just running the simple VAE
`

Nope not merged yet.

AttributeError: 'Model' object has no attribute 'run_eagerly'

AttributeError: 'ResourceVariable' object has no attribute '_distribute_strategy'


ci: don't parse lean-toolchain twice

For some reason that is not clear to me, the current code ends up with the empty string for the version. Easier than figuring out why that is, is using the environment variable that we'd set up earlier in this job.

bors r+


HTTPServer stop crash

it same like crash with deallock，anyone has the same crash？
Operating system: iOS
12.0.1 16A404
CPU: arm64
2 CPUs
Crash reason:  EXC_BREAKPOINT / EXC_ARM_BREAKPOINT
Crash address: 0x1bdae5930
Process uptime: 4802 seconds
Thread 35 (crashed)
0  libdispatch.dylib!DISPATCH_WAIT_FOR_QUEUE + 0x1bc
1  libdispatch.dylib!_dispatch_sync_f_slow + 0x8c
fp = 0x000000017071a860    lr = 0x00000001bdae54cc
sp = 0x000000017071a7d0    pc = 0x00000001bdae54cc
Found by: previous frame's frame pointer
2  libdispatch.dylib!_dispatch_sync_f_slow + 0x8c
fp = 0x000000017071a8a0    lr = 0x00000001006d29e8
sp = 0x000000017071a870    pc = 0x00000001bdae54cc
Found by: previous frame's frame pointer
3  XXX!-[HTTPServer stop:] [HTTPServer.m : 442 + 0x8]
fp = 0x000000017071a8d0    lr = 0x00000001006d0ec0
sp = 0x000000017071a8b0    pc = 0x00000001006d29e8
Found by: previous frame's frame pointer
4  XXX!-[HTTPServer dealloc] [HTTPServer.m : 113 + 0xc]
fp = 0x000000017071a8f0    lr = 0x00000001007dbaa0
sp = 0x000000017071a8e0    pc = 0x00000001006d0ec0
Found by: previous frame's frame pointer
5  XXX!_destroy_helper_block [GCDAsyncSocket.m : 2035 + 0x4]

me too ！how can I fix it?

I'm getting the same crash. This started recently and I cannot reproduce it on my Mac:
Crashed Thread:        5  Dispatch queue: HTTPServer
Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [291]
Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: dispatch_sync called on queue already owned by current thread
[...]
Thread 5 Crashed:: Dispatch queue: HTTPServer
0   libdispatch.dylib             	0x00007fff5d8f9cec DISPATCH_WAIT_FOR_QUEUE + 392
1   libdispatch.dylib             	0x00007fff5d8f98cf _dispatch_sync_f_slow + 171
2   com.incident57.CodeKit3       	0x0000000101720a37 -[HTTPServer stop:] + 79
3   com.incident57.CodeKit3       	0x000000010171eef0 -[HTTPServer dealloc] + 89
4   com.incident57.CodeKit3       	0x0000000101736d75 -[LPHTTPServer dealloc] + 177
5   com.incident57.CodeKit3       	0x000000010168e7f0 _destroy_helper_block.253 + 24
6   libsystem_blocks.dylib        	0x00007fff5d987bfe _Block_release + 109
7   libdispatch.dylib             	0x00007fff5d8eddcf _dispatch_client_callout + 8
8   libdispatch.dylib             	0x00007fff5d8f4124 _dispatch_lane_serial_drain + 618
9   libdispatch.dylib             	0x00007fff5d8f4bdc _dispatch_lane_invoke + 388
10  libdispatch.dylib             	0x00007fff5d8fd090 _dispatch_workloop_worker_thread + 603
11  libsystem_pthread.dylib       	0x00007fff5db2e60b _pthread_wqthread + 409
12  libsystem_pthread.dylib       	0x00007fff5db2e405 start_wqthread + 13

I have the same crash as well. It happens when device is in background.
Crashed: HTTPServer
0  libdispatch.dylib              0x239347f30 DISPATCH_WAIT_FOR_QUEUE + 444
1  libdispatch.dylib              0x239347ad4 _dispatch_sync_f_slow + 140
2  KTVCocoaHTTPServer             0x102b0404c -[HTTPServer stop:] (HTTPServer.m:472)
3  KTVCocoaHTTPServer             0x102b02384 -[HTTPServer dealloc] (HTTPServer.m:122)
4  CocoaAsyncSocket               0x10222ddc4 _destroy_helper_block.306 (GCDAsyncSocket.m:2035)
5  libsystem_blocks.dylib         0x2393f4a44 _Block_release + 152
6  libdispatch.dylib              0x2393997d4 _dispatch_client_callout + 16
7  libdispatch.dylib              0x239342320 _dispatch_lane_serial_drain$VARIANT$mp + 592
8  libdispatch.dylib              0x239342e3c _dispatch_lane_invoke$VARIANT$mp + 428
9  libdispatch.dylib              0x23934b4a8 _dispatch_workloop_worker_thread + 596
10 libsystem_pthread.dylib        0x239579114 _pthread_wqthread + 304
11 libsystem_pthread.dylib        0x23957bcd4 start_wqthread + 4

Same Crash. Does anyone can fix it

Unfortunately this project is definitely dead. Nobody has committed anything in years. If you're able to, I'd suggest checking out one of the open source Swift HTTP server projects. If I were starting a new project today, I would not use CocoaHTTPServer. It's on my list of things to extricate from my existing projects when I have time.


Deprecated Twig functions

DEPRECATED - Using an instance of "Twig_Function_Method" for function "knp_menu_get" is deprecated. Use Twig_SimpleFunction instead.

DEPRECATED - Using an instance of "Twig_Function_Method" for function "knp_menu_render" is deprecated. Use Twig_SimpleFunction instead.

 DEPRECATED - Twig Test "sameas" is deprecated. Use "same as" instead in knp_menu.html.twig at line 5.

This is already fixed in the dev version of the library


neo4j-composite-sync-tool

neo4j-composite-sync-tool

Codecov Report

Merging #468 into release-2.1.0 will increase coverage by 0.01%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             release-2.1.0     #468      +/-   ##
===================================================
+ Coverage            31.98%   31.99%   +0.01%
  Complexity            1209     1209
===================================================
  Files                  172      172
  Lines                15112    15112
  Branches              2395     2395
===================================================
+ Hits                  4833     4835       +2
+ Misses                9557     9555       -2
  Partials               722      722

Impacted Files
Coverage Δ
Complexity Δ

...org/ekstep/graph/engine/router/ActorBootstrap.java
57.61% <0%> (+1.32%)
16% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Equation preview doesn't work with commands defined in other files

Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version
IntelliJ 2019.1
TeXiFy IDEA version
v0.6.4
What I did (steps to reproduce)
Create a file "External-commands.tex" which contains the following
\newcommand{\externalCommand}{foo-bar}
Create a file called "Test.tex" which contains
\documentclass[11pt]{article}
\include{External-commands}

\begin{document}
    This fails: $\externalCommand$.
\end{document}

Place the cursor in the $$ area and attempt to preview the equation.
Expected behavior
The equation preview window should open and preview foo-bar.
Actual behavior
Equation preview opens and displays an exception rather than the expected preview. (see next section for exception details)
(if applicable) The full stacktrace of the exception thrown
pdflatex exited with 1
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(/tmp/tmp3879625923063515736.tmp/equation.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 3 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amscls/amsthm.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def))
No file equation.aux.
(/usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
! Undefined control sequence.
<recently read> \externalCommand

l.8                     $\externalCommand
                                         $
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on equation.log.

The key thing to note is "Undefined control sequence." which indicates this is probably an issue involving not including "External-commands.tex" in the list of files to be compiled

Are you sure this works when you place your command definition in your main file? afaik it shouldn't, because that's the whole point of the equation preview: it compiles with a minimal preamble. If you want to use the preamble as you have in your document, you can just as well compile the whole document anyway.

I placed this in the main document and it did not work, as you predicted. I suppose this was more of an issue of understanding the features rather than a malfunction.

Yeah maybe that should be clarified more, thanks for noticing.


[core] Fix straight quote use

The objective of this change is to:

To enforce non-straight quotes. It's a convention that we have followed since https://groups.google.com/a/mui.com/g/shared-accounts/c/wMZm8Fkzfp0/m/SlBNUsLBAQAJ but without an actual check, it's too easy to regress.
To set up the first custom rule linting our markdown. It's similar to our custom eslint rules. We might get more ideas going forward. For example, GitHub has written this one https://unpkg.com/browse/<EMAIL_ADDRESS>One that I would like to implement is to guarantee that the git diff format is correct, I have seen it done wrong so many times 😁.
Make it possible to remove the duplication in https://github.com/mui/mui-x/blob/next/.markdownlint.jsonc and https://github.com/mui/mui-toolpad/blob/master/.markdownlint.jsonc. It's painful to keep in sync with this repository. The solution is to use a JavaScript configuration over a JSON one so we can then do direct imports.

I had to move from markdownlint-cli to markdownlint-cli2.

Great idea, we started a discussion about it in https://www.notion.so/Style-guide-2a957a4168a54d47b14bae026d06a24b?d=aff8a8dc579c48f8a2500de4253c6949#b17ab6d6eb6f4589ba084207caf33443.
In the worse case, if we don't want to enforce this style rule, point 2. and 3. are still wins :)

To enforce non-straight quotes.

Do you mean "enforce straight quotes"? It looks like that's what this is doing—replacing all curly quotes with straight quotes. I'm cool with that. 👍


Error from other files show in status bar

I have 38 issues in my _styles.scss file, but the error count shows even for the unlinted .md file.

You can always configure the scope of the status indicator in linter.statusIconScope config

I'm not sure I understand. The scope of the status indicator is not the active file?

Yeah. It's set to scope by default.

So why would the errors displayed not change to the error count of the active window?

What's your linter version by the way?

Never mind! I see my error. I had the scope set to project. Let my try it as File.
I have v1.8.1.


Run polyfill on IE/Edge because they have non-standard values

IE/Edge browsers have some non-standard 'key' values,
such as 'ArrowDown', 'ArrowUp' ... events become 'Down', 'Up' ...
So I think it's reasonable to polyfill this property on IE/Edge.
Tested on IE9/10/11, Edge 14

sorry for not seeing this. thanks for the contribution!


Travis package installs not working

The package installation specified lines in .travis.yml are being ignored. This is easily verifiable by noting that the section "Installing package dependencies" is conspicuously absent from recent (any?) build logs.

resolved by #20


Include stacktraces on rp2040 port

Adds stacktraces to the rp2040 port by default. Like other ports they may be excluded by the cmake option -DAVM_CREATE_STACKTRACES=off.
Closes #1107
These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

Sure. I only added it to the Fixed section because there was an option issue about it.

Sure. I only added it to the Fixed section because there was an open issue about it.

I see the point, the distinction between Fixed and Changed is quite blurred indeed, but in my opinion it belongs more to Changed since we are changing a default instead of fixing a real bug, but anyway it's not a big deal.

Moved the changelog entry to Changed.


char driver CAN: add tx_confirm ability in upperCAN driver.

Summary
add tx_confirm ability in upperCAN driver.
Impact
Testing

[Experimental Bot, please feedback here]
This PR summary needs substantial improvement to meet the NuttX requirements. Here's a breakdown of what's missing and how to address it:
Summary:

Insufficient Detail:  Simply stating "add tx_confirm ability" is too vague.

What is tx_confirm?  Explain the functionality in plain English. Is it about confirming successful transmission of CAN messages?
Why is this change necessary? What problem does it solve?  Is it a new feature request?  Does it improve performance or reliability?
What code is affected?  Be specific about the driver name and the files modified.  For example, "Modifies the upperCAN driver (drivers/can/uppercan.c) to..."

Impact:

All sections are blank. You must address each impact area.  Even if the answer is "NO", state it explicitly. For example:

Is new feature added? YES - Adds tx_confirm functionality to the upperCAN driver.
Impact on user? YES - Users can now leverage the tx_confirm API for... [explain how they use it and the benefits]
Impact on build? NO
Impact on hardware? [Depends on the change. Does it require specific hardware support?]
Impact on documentation? YES - Documentation needs to be updated to describe the tx_confirm feature, its usage, and any API changes.
Impact on security?  [Consider if the change introduces any new security considerations]
Impact on compatibility?  [Does it break compatibility with previous versions? Does it introduce compatibility concerns with certain hardware?]

Testing:

Provide Specifics:

Build Host(s): List the operating system, CPU architecture, and compiler used.  For example: "Linux (Ubuntu 20.04), x86_64, GCC 9.4.0".
Target(s): Specify the target architecture(s) and board configurations tested on.  Use clear identifiers. For example:

"sim:qemu-arm"
"ARM: STM32F4 Discovery board"

Testing Logs: You must provide actual testing logs both before and after your changes. These logs demonstrate the issue you're fixing or the functionality you're adding.

Example (Improved Summary):
## Summary

This PR implements a message transmission confirmation mechanism (`tx_confirm`) within the upperCAN driver (`drivers/can/uppercan.c`). The `tx_confirm` feature allows applications to receive explicit confirmation from the driver when a CAN message has been successfully transmitted to the CAN bus. This addresses the need for reliable message delivery tracking in applications sensitive to CAN bus communication issues.

This change introduces a new API function, `uppercan_tx_confirm()`, which applications can use to register for transmission confirmation callbacks.

Related NuttX Issue: #[Insert issue number if applicable]


Add async support

This PR introduces asynchronous APIs and refactors existing HTTP handling to improve performance and flexibility in LayoutPDFReader. Key changes include:

Unit Tests: Added tests for read_pdf (from URL) to ensure my changes aren't breaking anything.
Refactor to httpx: Replaced urllib3 with httpx in _download_pdf and _parse_pdf for support of asynchronous operations.
Async Alternatives: Added _download_pdf_async, _parse_pdf_async, and read_pdf_async, allowing non-blocking operations for both HTTP requests and local file reading.

This PR resolves issue #44.

Hi @ansukla, I hope this is helpful and implemented in the spirit of my project. As this is my first open-source contribution I welcome any feedback!
Best,
Phil


Provide a way to describe default propdefinitions

Open questions

default for properties
what about # for arrays
¿ somehow default to maybe by default?

Proposed API
I propose that instead of doing it like this (from can-define):
class MyThing extends DefineClass {
  static define = {
    "*": {
      type: String
    }
  }
}

We instead add a defaults option:
class MyThing extends DefineClass {
  static defaults = {
    type: String
  }
}

I like this, but I think people might confuse static defaults with the default on a PropDefinition so maybe we want to use a different property name.

I like defaults too, but what would it be for DefineArray?  Currently # is for index properties and * is for all properties.

How could one specify "maybe by default"?

Decided to go with propertyDefaults and items.


Move the "send" button on mobile to the same line in the ALDocument.send_button_html() method

We can reduce the size of the email input to make that possible.

I think #175 resolved this


400: The request specifies an invalid filter parameter.

I'm getting a 400 error when running consecutively get_playlist_videos and videos methods, like so:
uploads = await self.ytb_api.get_playlist_videos(playlist_id=self.channel.uploads_playlist_id, limit=100)
raw_videos = await self.ytb_api.videos([u.id for u in uploads], parts=Part.ALL_PUBLIC())

Complete error message:
Status: 400
Reason: {
  "error": {
    "code": 400,
    "message": "The request specifies an invalid filter parameter.",
    "errors": [
      {
        "message": "The request specifies an invalid filter parameter.",
        "domain": "youtube.parameter",
        "reason": "invalidFilters",
        "location": "parameters.",
        "locationType": "other"
      }
    ]
  }
}

I looked into it. Turns out that the objects returned from a playlist have a distinct ID from the video, and a few other small differences. A new version has been published that will fetch and set id to the video ID for playlist items, which should fix the issue in this case.

Thank you for your prompt responses!

Still getting this error, though

Is the playlist longer than 50 videos? It appears that this also gives an error. I have added logic to batch videos into groups of 50 for this method and published it.


Fix alert header

Why:
The alert header does not match with the description.
Closes: #35413

What's being changed (if available, include any code snippets, screenshots, or gifs):
The alert header has been changed from tip to note.

Check off the following:

[ ] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
[x] The changes in this PR meet the docs fundamentals that are required for all content.
[x] All CI checks are passing.

@akordowski Merging this now! Thank you for this fix ✨


Add version and checksum to Dropbox.app - 11.4.20

Checklist

[X] The commit message includes the cask’s name and version.
[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} left no offenses.

The dropbox cask does not need to be an unspecified latest with no checksum because the version number is readily available at from the OSX download page redirect.
The following curl shows the download location and version as a redirect from Dropbox within the Location header:
curl -sI "https://www.dropbox.com/download?plat=mac&full=1"

Latest and last version links to show that specific versions are readily available:

https://clientupdates.dropboxstatic.com/client/Dropbox 10.4.26.dmg
https://clientupdates.dropboxstatic.com/client/Dropbox 11.4.20.dmg

I am not sure about this change - my installed version of Dropbox is 10.4.26, and how would one find newer versions to update the Cask, would you have to run curl -sI "https://www.dropbox.com/download?plat=mac&full=1" to check?

I use https://github.com/buo/homebrew-cask-upgrade

Ah, you mean for Cask updates? Version numbers are available on the dropbox forum "changelog"

To get just the version number: curl -sI "https://www.dropbox.com/download?plat=mac&full=1" | grep 'Location' | sed -E 's/.*%20(.+).dmg/\1/'.
Though 11.4.26 isn’t there, so this method seems to produce outdated results. In addition, I’m ambivalent to this change as well. Dropbox is one app where we want to be sure we’re getting the real deal, so having a sha256 (and a version) is useful. However, not only is this method of getting the latest version obtuse and in need to be explicitly run, Dropbox (unlike most auto-updating apps) updates silently.
This all means in the end this change might actually be harmful to security. Since we have no easy method to know a new version is available, this cask will probably become dangerously outdated. Seems like an outlier case where :latest and :no_check is actually more secure.

Wouldn't mind a revert if you feel strongly one way or another. I have no strong opinion on this one.

My vote would be for a revert.

https://github.com/caskroom/homebrew-cask/pull/25015.

Sorry I meant to reply on this earlier as it was my commit.
I made this because I feel more comfortable with the idea of a checksum on versions but I can see the reasoning here.
Is it worth making a comment within the cask itself to reflect this determination so that no one else makes the same update that I did?

I made this because I feel more comfortable with the idea of a checksum on versions

As do most users and we do prefer that, but this is indeed a special case.

Is it worth making a comment within the cask itself to reflect this determination so that no one else makes the same update that I did?

No, because I don’t recall it having happened before in all the time the cask exists.

Thanks Vítor


Segmentation fault 11

When running certain functions with bustools, I repeatedly get segmentation fault 11. One example is inspect, which fails with one file, but passes with another. I should clarify that the file inspect failed with works with every other function.
I have also gotten the seg fault for counts and project.

If you run into segfaults we would appreciate getting more information, especially if it can be reproduced using public data. Please report the command used and the command line paramers, along with the datasets used if publicly available.

The files are here: https://github.com/galaxyproject/tools-iuc/pull/2473/files?file-filters[]=.bus&file-filters[]=.ec&file-filters[]=.txt
Failed commands:
* On mac:
* bustools inspect -o inspect.json -e matrix.ec -w whitelist.txt testbus.bus
* In a linux environment:
*  bustools count -g txg.txt -e matrix.ec -t transcripts.txt testbus.bus
*  bustools project -g txg.txt -e matrix.ec -t transcripts.txt testbus.bus


"Error: Error encountered resolving symbol values statically." when console.log called from a forRoot static method.

I am not sure if this is an error in my understanding, an ionic error, an angular error, or a typescript error.
Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x ] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

$ ionic cordova build android --prod
generates the following error:
Error: Error encountered resolving symbol values statically. Calling function 'TestModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule

Expected behavior:

I expected the app to build.
Steps to reproduce:

ionic start TestBuild tabs
Create directory src/modules.
Create a module, TestModule in src/modules/test.module.ts with contents:
import {
  NgModule,
  ModuleWithProviders
} from '@angular/core';

export interface ITestConfig {
  value: string;
}

export class TestConfig implements ITestConfig {
  value: string;
}

@NgModule({

  declarations: [
  ],

  imports: [
  ],

  entryComponents: [
  ],

  providers: [
  ],

  exports: [
  ]

})

export class TestModule {

  // -----------------------------------------------------------------------------

  /**
  * test set configuration
  */

  static forRoot( config: ITestConfig ): ModuleWithProviders {

    console.log( "This is a test" );

    return {
      ngModule: TestModule,
      providers: [

        { provide: TestConfig, useValue: config }

      ]
    };
  }

} // end of TestModule

Include module test module in src/app/app.module.ts
import { TestModule, TestConfig } from '../modules/test.module';

let config: TestConfig = {
  value: 'test'
}

....

  imports: [
    BrowserModule,
    IonicModule.forRoot(MyApp),
    TestModule.forRoot( config )
  ],

Run the build and notice the error.
Now remove the "console.log()" call and re-run the build.
Note that it builds.
Why would a call to console.log there cause the build to fail with this error?
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):

global packages:

    @ionic/cli-utils : 1.4.0
    Cordova CLI      : 6.4.0
    Ionic CLI        : 3.4.0

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.4.0
    @ionic/cli-plugin-ionic-angular : 1.3.1
    Cordova Platforms               : android 6.0.0
    Ionic Framework                 : ionic-angular 3.4.2

System:

    Node       : v7.10.0
    OS         : Linux 4.4
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed
    npm        : 4.2.0

Thanks for the very detailed information. From looking at your code, I don't see anything specifically relevant to ionic, and I suspect it is an angular issue (when compiling with AoT).

Hello everyone! I agree with @AmitMY here that this looks more like an Angular issue than an Ionic specific issue. The code all looks correct to me. I will say that I don't think it is common to call console.log() in a ngModule declaration, but I would think it should work. I would recommend you open an issue here on the angular repo. Also, since this seems to be an Angular issue and not an Ionic specific issue I am going to close this issue for now.

Thank you for the prompt reply. Submitted here: https://github.com/angular/angular/issues/17663