feat: Genesis - [merged]

Merges genesis -> development
create the base site template.
Requirements

[ ] Base HTML templates

/cc @jasonpagetas, this is the repo that will have the django app i was talking about.

marked the checklist item Base HTML templates as completed

mentioned in commit 1a8861846bb16255c204729438057e42b3c81d7a

mentioned in commit 81b170cabf2398304861fa5b68fadb962630d4cb

marked the checklist item Base HTML templates as incomplete

Site Layout

@jasonpagetas, Thoughts? colours aren't correct, the random ones are for clarity during dev

mentioned in commit 2670b64d60bf112ef2144916e96eb07768c09f87

added 3h 55m of time spent

added 3 commits
2670b64d - chore: add boilerplate81b170ca - feat(django): add organizations app1a886184 - feat(template): add base template
Compare with previous version

mentioned in commit 9092445d0bcbe3215f675eb5e4794cfefb710913

added 1 commit
f3c9e2f7 - chore: default repo files inc ci
Compare with previous version

mentioned in commit 5ef2b9a685852f17359f472be12494547068154a

added 1 commit
85b46034 - chore: default repo files inc ci
Compare with previous version

mentioned in commit f3c9e2f78ff76873acf1e3b58bdd51995476f5f1

added 4 commits
5ef2b9a6 - chore: formating updates including template names to html.j29092445d - feat(app): Add new app structure for organizations and teamsdd54eae8 - feat(structure): View Organizations7cdfdab1 - feat(structure): Select and View an individual Organization
Compare with previous version

mentioned in commit dd54eae8d747ab0a17e71797d675a45eeaaae813

mentioned in commit 85b46034e301036c94e65d447507ca31645f4ff7

mentioned in commit 7cdfdab1fc966f3c92e69baf1162033c7d2e9bc4

mentioned in commit 0e0cd6fe9d7de06ed0688c866e87a91e2d3dc206

added 1 commit
e0225339 - feat: Dyno-magic build navigation from application urls.py
Compare with previous version

marked the checklist item Base HTML templates as completed

marked the checklist item Base HTML templates as incomplete

mentioned in commit e02253398e85f4cbc1dc7f481febd4e6ffe06bb0

added 1 commit
0e0cd6fe - feat: Dyno-magic build navigation from application urls.py
Compare with previous version

mentioned in commit f36efe05bc10706d80ad1a994f381b36e8929016

added 4h 28m of time spent

Organizations view

An Organization with accompanying teams

mentioned in commit 25dadd81904f7ebec956192108bd7f230fbf9b10

mentioned in commit 96a99c9df181367498e3f8d8031a0c1e4304a312

added 1 commit
25dadd81 - feat: Dyno-magic build navigation from application urls.py
Compare with previous version

added 1 commit
f36efe05 - feat: Dyno-magic build navigation from application urls.py
Compare with previous version

mentioned in commit 71bcd192b3e9d6616ff8dca5d8b5745ad371de92

added 11h 33m of time spent

mentioned in commit dae7f3c47a3c511ac30decb647461902e0dc248f

mentioned in commit 65bd32dfad3d7f8f867aea84dd4ad31133aa8fc1

added 1 commit
71bcd192 - feat: Dyno-magic build navigation from application urls.py
Compare with previous version

mentioned in commit 850468f65a32a7ac8eee02cb8d17a89ee59cc663

added 8h 45m of time spent

added 5 commits
283ef9a7 - feat(auth): Setup Login required65bd32df - feat(auth): Add User Account Menu96a99c9d - feat(auth): Custom Login Pagedae7f3c4 - feat(structure): unregister admin pages from organization app not required850468f6 - test: interim unit tests
Compare with previous version

mentioned in commit aeaeba3413db0f157e9c37d301272894391235d7

mentioned in commit 283ef9a7145d424bca2c898935e08cdc83038fff

added 1 commit
e9aaf988 - test: interim unit tests
Compare with previous version

mentioned in commit e9aaf988c42d1c2e362c686a5d708d1a313b0382

marked the checklist item Base HTML templates as incomplete

marked the checklist item Base HTML templates as completed

added 1 commit
f7bbb122 - feat(account): Add user password change form
Compare with previous version

added 1 commit
a6de3209 - test: interim unit tests
Compare with previous version

mentioned in commit a196d42bba5613943f6b4d0475e0ebed874976f3

added 1 commit
aeaeba34 - test: interim unit tests
Compare with previous version

mentioned in commit 5ca58f18838b7abc9ce5e5975d22c5dcbf844d76

mentioned in commit 789777a270bbd46e0a3126026e7236222f38da35

mentioned in commit af5175c4e198f5431d3f7b0d5b94f78818366053

mentioned in commit a6de3209d75b6dc5ac40d87d6d0226b1fcbb8d4d

mentioned in commit f7bbb122e6651635a4cb8e74246a8e155be6dcd1

added 2 commits
789777a2 - feat(urls): provide option to exclude navigation items5ca58f18 - test: interim unit tests
Compare with previous version

added 25m of time spent

added 3 commits
af5175c4 - feat(access): rename structure to access and remove organization app in favour...c0212178 - feat(development): added the debug django appa196d42b - feat(account): show admin site link if user is staff
Compare with previous version

mentioned in commit 0446d39190406fb54baf85bc031708a03473e020

mentioned in commit c0212178111f000c20b0b60426d3542dd704e8ce

mentioned in commit 4391e4e2f7828b285521963b65906f423d71892f

added 23h 29m of time spent

wtf

added 1 commit
4391e4e2 - feat(account): show admin site link if user is staff
Compare with previous version

added 1 commit
0446d391 - feat(account): show admin site link if user is staff
Compare with previous version

marked the checklist item Base HTML templates as incomplete

mentioned in commit 2b5047db2db18bfb10ccaadbf9adce12802b9c11

requested changes

not needed as it aint called

added 10m of time spent

move styles to css class

not needed as it's not called

marked the checklist item Base HTML templates as completed

mentioned in commit d715038a884cad87fba0a55f0d30ea66fda322b0

data and content are the same thing

marked the checklist item Base HTML templates as completed

added 3 commits
d715038a - feat(access): add mixin to check organization permissions against user and object2b5047db - feat(access): add views for each action for teamsaf858dcc - feat(access): add org mixin to current views
Compare with previous version

mentioned in commit c9f147d805d7d2e94cb9177b61fcb608efd5deb8

added 1 commit
8a62c3f6 - feat: user who is 'is_superuser' to view everything and not be denied access
Compare with previous version

mentioned in commit ca68c2589a8cabdc11fbe7e95b0a5d58f5fd8a0e

added 1 commit
266544d7 - refactor(views): move views to own directory
Compare with previous version

mentioned in commit c7986328f7c36ae6a817c4e7321d41daaa9423bd

mentioned in commit fa5703cb794b010d46dfdce1bd03243ca260cde1

mentioned in commit 9d507d82df745a057f7903d76bf439b142e71494

mentioned in commit 86046d6e923a32145869c1cb6cc0661eec9bd1d6

added 2 commits
9d507d82 - feat(style): format check boxesca68c258 - feat(access): add permissions to team and user
Compare with previous version

mentioned in commit 266544d72d3fc51aea68d82f63645e1a53f0e691

added 4 commits
c7986328 - refactor(views): move views to own directoryfa5703cb - feat(view): new user86046d6e - refactor(access): dont use inline formset7445d880 - feat(access): delete team user form
Compare with previous version

mentioned in commit 7445d8807ce7e995fdb2f7443e59b407e1cf92dd

changed this line in version 26 of the diff

mentioned in commit ab07fa6bcfc9401e1a7ee698957f7342bb6040dc

changed this line in version 26 of the diff

changed this line in version 26 of the diff

changed this line in version 26 of the diff

added 1 commit
eb9eeff4 - ci(coverage): add test coverage to ci
Compare with previous version

mentioned in commit eb9eeff4ed63e09a4670c3b3ac07f98f2575694b

mentioned in commit 0edfba604aba7f7810dbb038b836770b888f9d15

changed this line in version 26 of the diff

added 2 commits
0edfba60 - refactor: rename app from itsm -> appab07fa6b - chore: remove apps used for debugging from navigation menu
Compare with previous version

mentioned in commit 8e2542f9a50e64a2bc966d85a96d561cc1de8e67

mentioned in commit 30e7c8de42eafeacba02c221ad855ca0fb68f50d

ToDo

[ ] confirm only user with change_organization can change org.

mentioned in commit 0d1b31f9f03960f2cb18e6d6809c58f022f12c38

added 1 commit
30e7c8de - refactor(access): remove inline form for org teams
Compare with previous version

ToDo

[x] when a user is added to a team, add them to the group

added 1 commit
8e2542f9 - ci: correct test path
Compare with previous version

added 1 commit
0d1b31f9 - chore: template cleanup
Compare with previous version

mentioned in commit 047c8b8df411066c7d5beed553180a2aae950674

mentioned in commit a0433c75d9148118c238d586b3f8bbb09421ac84

added 1 commit
047c8b8d - docs: update and include permissions
Compare with previous version

added 1 commit
a0a8159e - docs: update and include permissions
Compare with previous version

mentioned in commit a0a8159e4e898f5d8473151f6a9818a5b8c69119

ToDo

[ ] confirm user with perm access.change_team or is a team manager is the only one who can change team
[ ] only manager can change members
[ ] change team perm can edit permissions

added 1 commit
db5d7e18 - docs: update and include permissions
Compare with previous version

added 1 commit
a0433c75 - docs: update and include permissions
Compare with previous version

mentioned in commit db5d7e18ad77c7402a8d73495ddaa9bbe626754b

mentioned in commit 070ba47de284d912fc86aabb323a1639e4328d4a

added 3 commits
44044d85 - chore: drop requirements.tx list to only required appsa0f4940a - feat(auth): include python social auth django application070ba47d - feat(access): when modifying a team ad/remove user from linked group
Compare with previous version

mentioned in commit b3b12638ad85fe1b3744561a2220d255cf9e105c

done 070ba47de284d912fc86aabb323a1639e4328d4a

added 1 commit
b3b12638 - feat: Build docker container for release
Compare with previous version

mentioned in commit 44044d8510f9dbba9c26db2c7c990b96627bf8ba

mentioned in commit a0f4940a09fb00486ed8280eb17ec35811839947

mentioned in commit<PHONE_NUMBER>3a07db1409d5ce66360bd63c7a40d0

mentioned in commit 00ec20d20e11103ea3ba6f087afd74e8e13fffac

added 1 commit
33569435 - fix(docker): build wheels then install
Compare with previous version

added 1 commit
69aec7ba - fix(docker): build wheels then install
Compare with previous version

mentioned in commit 857aa7af72f9e92be04d9cc258fc5875e4223ffd

added 1 commit
00ec20d2 - fix(docker): build wheels then install
Compare with previous version

mentioned in commit 97fef070108a081546a6f2eaf0f5c5748d431535

mentioned in commit 30406ea083721227905a25fc2244260fbb5ec267

mentioned in commit 4582c955b823393b875ad9da00396cd3624f19ae

added 1 commit
97fef070 - chore: settings.DEBUG=False by default
Compare with previous version

added 1 commit
30406ea0 - fix(docker): build wheels then install
Compare with previous version

mentioned in commit 69aec7ba6a5ea43fb3ec7f359744e30ac4a945ed

added 3 commits
2fe15778 - fix(fields): correct autoslug field so it works857aa7af - feat(tenancy): Add is_ global field4582c955 - chore(style): add content tab formatting
Compare with previous version

mentioned in commit a17df35208b30c0cb0c5872dddf56413fd84ae1a

added 1 commit
39c4509e - feat(template): add header content icon block
Compare with previous version

mentioned in commit 39c4509ebdbff35b2046faff31cbb5ed8ccc0f94

added 1 commit
a17df352 - feat(api): initial work on API
Compare with previous version

mentioned in commit 2fe15778cb638eb420e5f3312ca24e33bfc601c5

mentioned in commit adbc5d8b48689aff2374fc6ed89e2d4fa4d442d4

mentioned in commit 50cc050adf4cfcf43303350850caa56bf649874b

added 1 commit
50cc050a - feat(template): add header content icon block
Compare with previous version

added 1 commit
102aa981 - feat(api): initial work on API
Compare with previous version

mentioned in commit 4a1d99f1c06fff24e3ce97641f5171e7e4cde41c

added 1 commit
4a1d99f1 - feat(api): initial work on API
Compare with previous version

added 1 commit
8cbc4b70 - feat(api): initial work on API
Compare with previous version

mentioned in commit 102aa981ce0a72fa263016139076e87778255226

mentioned in commit 8cbc4b70f2569d3de03798382c215a57c046a5f7

added 1 commit
adbc5d8b - feat(api): initial work on API
Compare with previous version

mentioned in commit d9e04a0364655b5dfb470c23aff2bc2ed1e58bdd

added 1 commit
d9e04a03 - feat(api): initial work on API
Compare with previous version

mentioned in commit 57f9a43f0f50661f2c74ae0be6e0cf672089de21

mentioned in commit 7e3492c4d14ef63dd52efe75a3050d5813f639b8

marked the checklist item Base HTML templates as completed

mentioned in commit c43f41d9587e060ea7f3c4e51a72f5c928c9384b

added 1 commit
7e3492c4 - chore: code review fixes
Compare with previous version

marked the checklist item Base HTML templates as incomplete

added 21h 39m of time spent

added 1 commit
c43f41d9 - docs: notate global object
Compare with previous version

added 1 commit
57f9a43f - chore code review fixes
Compare with previous version

added 3 commits
761afb6f - refactor: button to use same selection colouraaddfd0e - chore: open source projectde83d749 - ci: sync project to github
Compare with previous version

ToDo

[ ] test oauth

mentioned in commit 460f59d889376f4fc05e48ea86c124b022ca0a7a

mentioned in commit de83d7490b9e6118beaf2eec303d38ac49332d16

added 1 commit
50371267 - feat(access): adjustable team permissions
Compare with previous version

added 1h 2m of time spent

mentioned in commit 761afb6f2bc592f29870a8eaac86c70a32086af3

mentioned in commit 50371267c1fb02e066d9a4ac066f54128ce957ea

mentioned in commit aaddfd0eef1614bf177f42b2a2248424ea9d5823

added 1 commit
5a3450f3 - fix(access): correct team required permissions
Compare with previous version

mentioned in commit 736d3930dff9705c3d27f853ed9a5f0000108164

test placeholder written for when tests written

this'll be done later

mentioned in commit 903de5e33f12f420db2262f974cc89014b1d4a17

mentioned in commit 5a3450f3c0f84fc32781338ef0c644356072366e

added 1 commit
903de5e3 - chore: remove test urls
Compare with previous version

mentioned in commit 4b214d0b8cc10f43c708ef45ce5e20225f9b6c21

added 3 commits
460f59d8 - chore: disable the api until it is developed736d3930 - feat(admin): remove group management4b214d0b - feat(admin): remove team management
Compare with previous version

mentioned in commit 74953ab7d93a5b8c4b73cb12c15d77c3e31df25d

resolved all threads

enabled an automatic merge when the pipeline for 5a3450f3c0f84fc32781338ef0c644356072366e succeeds

added 1h 28m of time spent

mentioned in commit 9da9bb6c5972ec25c27cd9a8bfac7b5ab1efeb93

test placeholder written for when tests written

mentioned in commit 9370a4853a9860622b1b17f7edaada15882099ef

created #1 to continue this discussion

mentioned in commit f98e3bc9c2ff5f3627dc2f49df6eb7e6afdc974c

mentioned in commit d3cafe08aa7e817d5511d8f455cbd8efe5294be2

mentioned in commit 377c78d6b84398e2bbae01a91478a8ab8f94a0a2

mentioned in commit 2d67f93d882d1ebe7782d9425c915e31f3a16453


Add Alfa portal data

This change is

Reviewed 1 of 1 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

buildout.cfg, line 73 [r1] (raw file):

robot_tests.broker.aps          = git ${remotes:gh}openprocurement/robot_tests.broker.aps.git
robot_tests.broker.polonex      = git ${remotes:gh}openprocurement/robot_tests.broker.polonex.git
robot_tests.broker.alfa         = git ${remotes:gh}openprocurement/robot_tests.broker.alfa.git branch=eauction

Вирівняти branch по аналогії з рядками зверху.

Comments from Reviewable

Reviewed 1 of 1 files at r1, 2 of 2 files at r2, 1 of 1 files at r3, 1 of 1 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


[SP-4205][PDI-16942]-When using the Excel Input Step an org.apache.poi.POIXMLException error can result if the compression ratio of the file is too high

fixed

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/excelinput/ExcelInput.java
  engine/test-src/org/pentaho/di/trans/steps/excelinput/ExcelInputContentParsingTest.java
  engine/test-src/org/pentaho/di/trans/steps/excelinput/files/Balance_Type_Codes.xlsx
  engine/test-src/org/pentaho/di/trans/steps/fileinput/BaseParsingTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelinput.ExcelInput

Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelinput.jxl.XLSWorkbook

Instruction Change: -3.3% :small_red_triangle_down:
Line Change: -2.6% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelinput.poi.PoiWorkbook

Branch Change: -6.3% :small_red_triangle_down:
Instruction Change: -17.4% :small_red_triangle_down:
Line Change: -18% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.systemdata.SystemDataMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:
Line Change: -0.8% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/engine/test-src/org/pentaho/di/trans/steps/excelinput/ExcelInputContentParsingTest.java

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 5, expected level should be 4. at Line: 91

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 5, expected level should be 4. at Line: 92

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 5, expected level should be 4. at Line: 94

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 5, expected level should be 4. at Line: 96

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 5, expected level should be 4. at Line: 98

:heavy_exclamation_mark: 'method def' child have incorrect indentation level 5, expected level should be 4. at Line: 99

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/excelinput/ExcelInput.java
  engine/test-src/org/pentaho/di/trans/steps/excelinput/ExcelInputContentParsingTest.java
  engine/test-src/org/pentaho/di/trans/steps/excelinput/files/Balance_Type_Codes.xlsx
  engine/test-src/org/pentaho/di/trans/steps/fileinput/BaseParsingTest.java

Newly Fixed Tests:
org.pentaho.di.trans.steps.syslog.SyslogMessageConcurrentTest.concurrentSyslogMessageTest:
:large_blue_circle: org.junit.runners.model.TestTimedOutException
org.junit.runners.model.TestTimedOutException: test timed out after 10000 milliseconds
	at java.lang.ClassLoader.findBootstrapClass(Native Method)
	at java.lang.ClassLoader.findBootstrapClassOrNull(ClassLoader.java:1015)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:413)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:411)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at org.productivity.java.syslog4j.impl

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.2% :small_red_triangle_down:
Complexity Change: -7.7% :small_red_triangle_down:

org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelinput.ExcelInput

Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelinput.jxl.XLSWorkbook

Instruction Change: -3.3% :small_red_triangle_down:
Line Change: -2.6% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelinput.poi.PoiWorkbook

Branch Change: -6.3% :small_red_triangle_down:
Instruction Change: -17.4% :small_red_triangle_down:
Line Change: -18% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change: -3.4% :small_red_triangle_down:
Complexity Change: -3.1% :small_red_triangle_down:
Instruction Change: -1% :small_red_triangle_down:
Line Change: -1.5% :small_red_triangle_down:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.


Is there any user data that is either being collected or Tracked by the SkyFloatingLabelTextField

Report
App
ℹiOS 14 App Tracking Transparency Framework Query
As part of the iOS 14 /AppTracking Transparency framework, would like to know if any kind of the user data is collected or Tracked by the SkyFloatingLabelTextField.
As mentioned in the Apple (Ref: https://developer.apple.com/support/app-privacy-on-the-app-store/),
below were some of the examples for Tracking:

Sharing device location data or email lists with a data broker.
Placing a third-party SDK in our app that combines user data from the app with user data from other developers’ apps to target advertising or measure advertising efficiency, even if we don’t use the SDK for these purposes. For example, using a login SDK that repurposes the data it collects from the app to enable targeted advertising in other developers’ apps.

The following situations are not considered tracking:

When the data is linked solely on the end-user’s device and is not sent off the device in a way that can identify the end-user or device.
When the data broker uses the data shared with them solely for fraud detection or prevention or security purposes, and solely on our behalf.

Nope nothing like that


Update text on the "start" page of each cloud's Getting Started guide

The current text on the first page of each cloud's Getting Started guide does not do a good job of communicating what the user is going to do. We should be more verbose in our copy and explain to the user what they are going to do and what to expect. Some suggestions:

Tell the user what exactly they are going to do. For example in the AWS flow, explain that they will deploy an S3 bucket and then modify it to have a KMS key.
Explain if there is any potential cost to the user.

Pages:

[ ] /docs/get-started/aws
[ ] /docs/get-started/azure
[ ] /docs/get-started/gcp
[ ] /docs/get-started/kubernetes

Working doc w/ copy: https://docs.google.com/document/d/1TbVGzXvwqZX1Oq2X8isdUwC3qhieDP_adyNnwMRNFhc/edit?usp=sharing

It seemed like we had universal consensus to switch the tutorials to something more "exciting." Specifically, to serve a website out of the bucket rather than enabling encryption, for AWS, which would then allow us to make the initial text more exciting. Do we plan on doing that?

Filed a new issue for that here: https://github.com/pulumi/docs/issues/3243
It's worth an A/B test (and continued testing) so we can figure out exactly what is "best" content to show the user.


Knowledge distillation

Hi,
Do you have the output of knowledge distillation 'npz' or 'tfrecord' file in a link, please?
$ CUDA_VISIBLE_DEVICES='0' ./data_distiller.py -M subcenter-arcface-logs/r100-arcface-msfdrop75/model,0 -D /datasets/faces_casia_112x112_folders/ -b 32 --use_fp16
Output: faces_casia_112x112_folders_shuffle_label_embs_normed_512.npz

Sorry but I'm not keeping that either. How about using the ported h5 models instead of the MXNet one?

Noted will do
Thanks!


[BUG-BE][MASTER-9729]fix process instance global param not include to task instance when master executing

Purpose of the pull request
close https://github.com/apache/dolphinscheduler/issues/9729
Brief change log
close https://github.com/apache/dolphinscheduler/issues/9729
Verify this pull request
have test locally.

Codecov Report

Merging #9730 (aa2d2f1) into dev (3e85194) will increase coverage by 0.00%.
The diff coverage is 59.52%.

:exclamation: Current head aa2d2f1 differs from pull request most recent head faf7de5. Consider uploading reports for the commit faf7de5 to get more accurate results

@@            Coverage Diff            @@
##                dev    #9730   +/-   ##
=========================================
  Coverage     40.01%   40.01%
+ Complexity     4475     4474    -1
=========================================
  Files           835      835
  Lines         33550    33579   +29
  Branches       3710     3715    +5
=========================================
+ Hits          13426    13438   +12
- Misses        18876    18886   +10
- Partials       1248     1255    +7

Impacted Files
Coverage Δ

.../org/apache/dolphinscheduler/common/Constants.java
80.95% <ø> (ø)

...e/dolphinscheduler/server/master/MasterServer.java
0.00% <0.00%> (ø)

...er/server/master/runner/FailoverExecuteThread.java
0.00% <0.00%> (ø)

...r/server/master/runner/MasterSchedulerService.java
0.00% <ø> (ø)

...er/server/master/runner/WorkflowExecuteThread.java
8.28% <0.00%> (ø)

...lphinscheduler/service/task/TaskPluginManager.java
0.00% <ø> (ø)

...e/dolphinscheduler/server/worker/WorkerServer.java
0.00% <0.00%> (ø)

...nscheduler/service/process/ProcessServiceImpl.java
30.85% <59.09%> (+0.30%)
:arrow_up:

...r/api/service/impl/ProcessInstanceServiceImpl.java
60.10% <66.66%> (-0.12%)
:arrow_down:

.../dolphinscheduler/common/utils/ParameterUtils.java
72.72% <100.00%> (ø)

... and 4 more

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 3e85194...faf7de5. Read the comment docs.


Semicolon position fixation issue

https://github.com/commandiron/WheelPickerCompose/issues/43
This is an issue that existed in the previous WheelPickerCompose library, but it's still occurring in the TimePicker. I was wondering if you could help solve this problem

WheelTimPicker code in project
              WheelTimePicker(
                  modifier = Modifier
                      .fillMaxWidth()
                      .padding(horizontal = 15.dp),
                  startTime = uiState.mateRecruitTime.parseToLocalTime(),
                  minTime = Clock.System.now().toLocalDateTime(TimeZone.of("Asia/Seoul")).time,
                  maxTime = kotlinx.datetime.LocalTime(23, 59),
                  timeFormat = TimeFormat.AM_PM,
                  rowCount = 5,
                  textStyle = Large20_Mid,
                  textColor = Gray001,
                  selectorProperties = WheelPickerDefaults.selectorProperties(
                      enabled = true,
                      shape = RoundedCornerShape(10.dp),
                      color = Gray010,
                      border = BorderStroke(2.dp, Gray010),
                  ),
              ) { snappedTime -> run { selectedTime = snappedTime.formatToTime() } }

thx for reading :)

Thanks for catching this bug. I really appreciate you taking the time to report it. I'm planning to dive in and fix it soon.
But until then, here's a quick workaround you could try: avoid using Modifier.fillMaxWidth() for now. There are plenty of other ways to center stuff in layouts that should sidestep this issue. Hope this temp fix helps you out while I work on squashing the bug for good. And your feedback is helpful in making this project better!

As you mentioned, I confirmed that the position of ":" was correctly placed when I removed the fillMaxWidth() option from the Modifier. However, it doesn't seem to be vertically centered. Thank you for your quick feedback. I'm looking forward to the updated version :)

You can try v1.0.1 now


Support for H5051 and H5071

Hi,
I have two Govee temp/humidity sensors, the H5051 and H5071. They both advertise over BLE and I can see them from my RPI when I scan for BLE devices.
I have this plugin installed for Homebridge, and when debug is checked it spits out a series of “invalid peripheral” messages as it presumably discovers things it doesn’t understand.
Would it be possible to add support for these two devices? Happy to help if I can.
Thanks!
Dan

Here's output for the two devices from running a scan w/ bluetoothctl:
[NEW] Device E0:12:1C:60:1C:75 Govee_H5071_1
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Key: 0xec88
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x00
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0xe6
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x08
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0xde
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x12
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x16
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x1f
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x00
[CHG] Device E0:12:1C:60:1C:75 ManufacturerData Value: 0x01
[NEW] Device E3:60:59:21:24:B1 Govee_H5051_24B1
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Key: 0xec88
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x00
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0xbb
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x08
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x5f
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x12
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x33
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x1f
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x01
[CHG] Device E3:60:59:21:24:B1 ManufacturerData Value: 0x01
I assume my actual ask here is adding support to govee-bt-client for these two devices

Here's what the homebridge console outputs for the two devices:
discovered e0121c601c75 e0121c601c75 e0:12:1c:60:1c:75 disconnected -81 invalid peripheral, manufacturerData=[88ec00e008fb12171f0001]
discovered e360592124b1 e360592124b1 e3:60:59:21:24:b1 disconnected -82 invalid peripheral, manufacturerData=[88ec00cc086712331f0101]

This morning it managed to detect one of the devices and briefly added it. The console showed "[Govee] Adding new accessory: GoveeH5051_24B1" and I saw the device in the Home app for a few minutes before it disappeared.
That said, the temperature was showing 147 degrees F, with 54% humidity (which of course did not match the physical device)

The console keeps spitting out "invalid peripheral" even though it added the H5051 into Home (although the temp and humidity are wrong). The H5071 shows up in the console too as "invalid peripheral" and that device does not get added to Home.

In the latest version of the plugin both devices now show up (as GoveeH5051_24B1 and GoveeH5071_1C75), but the temperature and humidity values are still wrong. The 5051 reports 147F and 53%, and the 5071 shows 121F and 92%.
They are in the same room about 5 feet apart.

What would have been the correct temp/humidity for them?

For the 5051, right now it reads 62.6F and 62.3% humidity. In the Home app it shows 147F and 53%.
For the 5071 it’s 64.1F and 62.2%, and 121F and 92%


[Feature Request] Increasing/decresing GPA indicator

Overview
This idea may need some refinement but ideally there should be a way to tell how the GPA for a search result has been changing across semesters. Without having to check through each semester in the filter.
Proposal
This could be a graph of the GPA over time or just an trending up/down icon based on some math to tell if the GPA has been increasing.
Supplementary Information
Since this will be a greater use of semester by semester data, it would be good to indicate from how many semesters each results data is coming from, maybe just another item below the graph on each down that says "Semesters: x"

Don’t show the indicator for every result, just significantly changing ones


pdk

Coverage decreased (-64.6%) to 8.333% when pulling 4d66734420a945f94edc17e2ca7be9f24695baf1 on raphink:pdk into cf548f551004a39fd04ef24f85190b301701f980 on hercules-team:master.


Get Koji from osg-internal-development in OSG series > 3.6

Hm. The build results don't make sense. The matrix says "el7" but the "al8" image is getting pulled, and despite the --build-arg arg being right there, my if statement doesn't match.


Folder structure, modules/ducks, best practices

Thank you so much for putting together this awesome project. As a fresh set of eyes, I have a bit of feedback. Maybe it's just me but I found the project's folder structure to be a little confusing....
Proposed folder structure:
This is overly simplified as I didn't want to put the entire file tree into this discussion, but hopefully you get the idea. Components are contained within folders, aggregated and exported from root for destructured imports (similar to material-ui components).
./react-redux-universal-hot-example
├── bin
├── src
│   ├── components // eg. import { InfoBar } from '../components'
│   │   ├── CounterButton
│   │   ├── GithubButton
│   │   ├── InfoBar
│   │   ├── MiniInfoBar
│   │   ├── SurveyForm
│   │   ├── WidgetForm
│   │   └── __tests__
│   ├── containers // more descriptive, used in official docs/examples...
│   │   ├── About
│   │   ├── App
│   │   ├── Home
│   │   ├── Login
│   │   ├── LoginSuccess
│   │   ├── NotFound
│   │   ├── RequireLogin
│   │   ├── Survey
│   │   ├── Widgets
│   │   └── __tests__
│   │       └── routes.js // routes defined in root
│   ├── redux
│   │   ├── init.js
│   │   ├── middleware
│   │   │   └── clientMiddleware.js  // etc
│   │   └── modules // (action/creator/reducer/selector bundles)
│   │       ├── auth.js
│   │       ├── counter.js
│   │       ├── reducer.js
│   │       ├── info.js
│   │       └── widgets.js
│   ├── server
│   │   ├── middleware
│   │   └── actions // proxy to separate REST api...
│   └── utils
│   │   ├── validationUtility.js // utility only (component-level definitions inside respective dir)
│       └── createDevToolsWindow.js  // etc
├── static
│   ├── dist
│   └── images
└── webpack

As you can see, the structure is pretty clean and self-documenting. The only downside is the additional folder nesting, but I think it's well worth it for the sake of maintainability. It may be a little contrived for an example project, but for those using this as a "starter" it will pay dividends down the road. I am setting up webpack aliases so make things easier and reduce some of the import boilerplate. The folder structure above is working in a branch on my local machine, let me know I'd be happy to submit a PR!
Modules/Ducks
I love the concept of encapsulating reducer tuples (plus selectors) into bundles. I know ducks is your project and I totally did not mean to torpedo the name with the proposed folder structure above! I really think "module" or "redux-module" encapsulates the idea in a coherent way that doesn't make newcomers feel like they have to learn even more (imo ducks kinda sounds like another framework or something that would require additional cognitive overhead, but it's really just bundling reducer logic).
Server
On a separate note, what's your opinion on the included server—should we be interacting directly with database from express, or using it to process incoming commands to call other RESTful services? Does it matter? I like the idea of an action- or command-based API a la CQRS (such as nexus-flux), but most of us will be contending with REST.
Misc...
Please let me know if you would any separate PRs for the following, which are also done...

Option to open Redux Devtools in a new window (it's so annoying in the application)
Minimize bootstrapped data in SSR production mode, and other little optimizations

I will help write some some documentation when I have time.
Looking forward to your thoughts. Cheers!

I like this a lot. Especially the use of a water-based weapon to kill ducks. You are probably right, that "ducks" should be only a slang term to refer to the modular tuples. Sure, go ahead and submit a PR.
Yes, both of those additional PRs would be great!
Thanks for putting so much thought and effort into this. :+1:

i like this too, i'd been structuring my folder structure similarly in my fork

@bdefore thanks for the feedback! i'm planning on wrapping this up later tonight

Hi @justingreenberg and @erikras,
At the risk of sounding rather naive about some Webpack or ES6 (or other?) things, I have a question about how your path-less import statements work.
@justingreenberg, in his original post above, mentioned that (italics added are mine)

"Components are contained within folders, aggregated and exported from root for destructured imports".

This seems to have been implemented in this repo in places like src/components/index.js:

Is that all that is needed to enable the path-less import mentioned in the code comments?  Or do you also need to set something up an alias or something in the Webpack config?  Perhaps Webpack's resolve.modulesDirectories?

I see that you do specify src for that property in your webpack config:

Is it the combination of what you did in places like src/components/index.js, as well as specifying src in the webpack config's resolve.modulesDirectories that enables the path-less import statements?

@jasonkylefrank yes, but the recommended method of resolving project paths is to use resolve.root instead of resolve.modulesDirectories (which i did not know about at the time)
see:
https://github.com/webpack/webpack/issues/472#issuecomment-55706013
https://github.com/webpack/webpack/issues/1574#issuecomment-157520561

@justingreenberg Great, thanks for the info!


Wind vector rotation troubles (rotate_vector)

I am currently working with a gridded data set that has its wind vectors already in an earth-relative frame.  When looking to rotate the wind vectors appropriately for plotting on a Basemap projection I've run into a strange problem where the vectors, quite simply, look rather odd.  I ran a few  tests with simple test points to make sure the rotate_vector routine appeared to be working correctly, and it seemed fine.  But when I run a whole model output grid through the rotate_vector routine, it seems to produce wind fields which don't look quite right (see below).

Here are some stats associated with the point that has the red star on the plot with the title 'Rotated vectors'
Lat and Lon: 39.11, -70.0144

Original U and V:     1.30,  7.14
Rotated U and V:    -1.33 , 7.13

Now note how the rotated wind at this point is aligned along the -70 meridian, which would suggest that in earth relative terms we might expect the wind components to be more along the lines of u=0 and v=7.  However, judging from above that's certainly not the case.
Now, if I rotate that same vector, by itself, I get the following rotated wind:
Rotated U and V: -0.03 7.26
And see the second plot for a visual:

It would seem desirable to have the same behavior for the single point that we have for the gridded set of winds.
The only thing special about the gridded data, that I have noticed, is that the latitudes can vary in a non-standard way with increasing x dimension, west to east (e.g. 35.5N, 34.2N, 33.1N, 36.2N, etc.).  It wasn't clear if this was okay within rotate_vector.  In some simple tests it didn't seem to be a problem.
It would be nice to be able to use this routine for not only a set of gridded data, but observations as well. It's worth noting that observations wouldn't necessarily be ordered in a nice, regular way given the nature that observations tend to be irregularly spaced (e.g. surface stations co-located with airports).
Unfortunately I don't have any suggestions for a solution, but am hopeful others may have an idea.
Below is the snippet of code used to generate the first plot above.
Thanks!
Jacob
import nemsio
import numpy as np
import matplotlib.pyplot as plt
from mpl_toolkits.basemap import Basemap

# Get the input file
f='restart_file'
nio=nemsio.nemsfile(f)

skip=25
u10=u[::skip,::skip,0]
v10=v[::skip,::skip,0]
lats=nio.lats[::skip,::skip]
lons=nio.lons[::skip,::skip]

# Create the figure
fig=plt.figure(figsize=(18, 6))

# Domain covers NE CONUS
llcrnrlon=-84.0
llcrnrlat=35.0
urcrnrlon=-60.0
urcrnrlat=49.0
res='l'

m = Basemap(llcrnrlon=llcrnrlon,llcrnrlat=llcrnrlat,urcrnrlon=urcrnrlon,urcrnrlat=urcrnrlat,\
          rsphere=(6378137.00,6356752.3142),\
          resolution=res,projection='lcc',\
          lat_1=25.0,lon_0=-95.0)

#The vector rotation to the Basemap projection just specified
u10_rot, v10_rot, x, y = m.rotate_vector(u10, v10, lons, lats, returnxy=True)

parallels = np.arange(-80.,90,5.)
meridians = np.arange(0.,360.,5.)

# - First sublot is without rotation
ax = fig.add_subplot(121)
ax.set_title('Without rotation')

m.drawmapboundary(fill_color='aqua')
m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
m.drawcoastlines(color = '0.15')

m.drawparallels(parallels)
m.drawmeridians(meridians)

m.barbs(x, y, u10, v10, pivot='middle', barbcolor='black',zorder=10)

# - Second subplot is with rotation

ax = fig.add_subplot(122)
ax.set_title('Rotated vectors')

m.drawmapboundary(fill_color='aqua')
m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
m.drawcoastlines(color = '0.15')
m.drawparallels(parallels)
m.drawmeridians(meridians)
m.barbs(x, y, u10_rot, v10_rot,
    pivot='middle', barbcolor='black',zorder=10)

m.scatter(-70.0144,39.11,s=175,color='red',marker='*',latlon=True)

How would someone go about installing the nemsio package?

Hi Micah,
It's a local package put together for reading files associated with a model I work with.  Unfortunately, it's not in a form which is community friendly (and the file associated with it is large, ~28G).
However, I can provide a numpy.savez_compressed file that contains only the necessary fields along with the associated python to open and read it.  Would this be suitable?  The file comes out to about 36M in size.  The plotted winds are from a different date, but issue is still present.
-Jacob

Yes @jrcarley, it would be great )) I think there is lots of people who would like to look at it.
Cheers

Alrighty - thanks for looking into this!
GitHub seems to prefer file sizes <10MB so I've tossed it onto DropBox.  To get the file, use the following link:
https://www.dropbox.com/s/nyr5gta8bqoyash/rotate_vector_inputs.npz?dl=0
I've updated the code I pasted in my previous post below so that the data at the link above may be read and plotted:
import numpy as np
import matplotlib.pyplot as plt
from mpl_toolkits.basemap import Basemap

# Read the npz file
dat=np.load('rotate_vector_inputs.npz')
u=dat['u']
v=dat['v']
nio_lons=dat['lons']
nio_lats=dat['lats']

# Skip factor so we do not overwhelm the plot (this is ~ a 3 km grid)
skip=25
u10=u[::skip,::skip,0]
v10=v[::skip,::skip,0]
lats=nio_lats[::skip,::skip]
lons=nio_lons[::skip,::skip]

# Create the figure
fig=plt.figure(figsize=(18, 6))

# Domain covers NE CONUS
llcrnrlon=-84.0
llcrnrlat=35.0
urcrnrlon=-60.0
urcrnrlat=49.0
res='l'

m = Basemap(llcrnrlon=llcrnrlon,llcrnrlat=llcrnrlat,urcrnrlon=urcrnrlon,urcrnrlat=urcrnrlat,\
   	      rsphere=(6378137.00,6356752.3142),\
   	      resolution=res,projection='lcc',\
   	      lat_1=25.0,lon_0=-95.0)

#The vector rotation to the Basemap projection just specified
u10_rot, v10_rot, x, y = m.rotate_vector(u10, v10, lons, lats, returnxy=True)

parallels = np.arange(-80.,90,5.)
meridians = np.arange(0.,360.,5.)

# - First sublot is without rotation
ax = fig.add_subplot(121)
ax.set_title('Without rotation')

m.drawmapboundary(fill_color='aqua')
m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
m.drawcoastlines(color = '0.15')

m.drawparallels(parallels)
m.drawmeridians(meridians)

m.barbs(x, y, u10, v10,
    pivot='middle', barbcolor='black',zorder=10)

# - Second subplot is with rotation

ax = fig.add_subplot(122)
ax.set_title('Rotated vectors')

m.drawmapboundary(fill_color='aqua')
m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
m.drawcoastlines(color = '0.15')
m.drawparallels(parallels)
m.drawmeridians(meridians)
m.barbs(x, y, u10_rot, v10_rot,
    pivot='middle', barbcolor='black',zorder=10)

m.scatter(-70.0144,39.11,s=175,color='red',marker='*',latlon=True)
plt.show()

Have you tried appending .copy() to each array after subsampling, so
that you will have C-contiguous arrays?  There is a bug that is fixed in
master but not in 1.07 involving arrays that are not in C order.

@jrcarley:  It seems like the plots with the data from dropbox are different? Or is it because my version of basemap is different (I am using the latest master)? Could you please, also specify the indices corresponding to the star (i, j)?
https://github.com/guziy/PyNotebooks/blob/master/basemap_issue_%23269.ipynb
Cheers

I've figured out the indices, and the plot for 1 point looks very similar to the field plots...
https://github.com/guziy/PyNotebooks/blob/master/basemap_issue_%23269.ipynb

@guziy, Sorry I had meant to mention that the date corresponding to the data I had provided is different from the date in the first example.  What is important, though, is that the problem remains.  My apologies for not specifying the i,j location.  On the thinned/subsampled array the points are: i=64, j=40.  For the example I attached, at the point of the star we have:
I and J of the thinned/subsampled grid:  (i=64, j=40)
Lat and Lon: 39.11, -70.0144

Original U and V:     7.39,  4.12
Rotated U and V:     6.17,  5.80

Though the problematic barbs are eastward of the red star for the example data provided here.
@efiring, I did attempt .copy() after your suggestion and unfortunately did not see a change in the behavior.  I have also tried passing the full set of winds through the rotation prior to subsampling and the issue remained.
To update: I've a routine that is separate from Basemap which will do the rotation correctly - but it's not general and depends upon the projection being Lambert Conic Conformal or Polar Stereographic.  Below is an example with comparisons of un-rotated (leftmost), Basemap rotated (center), and the alternate rotation method (far right):

Note the differences in the barbs east of the red star.  The Basemap rotation indicates the winds are mostly southerly while the the alternate approach suggests more a southwesterly wind.  The simplified, working code for the alternate rotation is as follows:
def alt_rotate(true_lat,lov_lon,earth_lons,uin,vin,proj,inverse=False):
  #  Rotate winds from LCC relative to earth relative (or vice-versa if inverse==true)
  #
  # Input args:
  #  true_lat = True latitidue for LCC projection (single value in degrees)
  #  lov_lon  = The LOV value (e.g. - -95.0) (single value in degrees)
  #                              "Lov = orientation of the grid; i.e. the east longitude value of
  #                              the meridian which is parallel to the Y-axis (or columns of the grid)
  #                              along which latitude increases as the Y-coordinate increases (the
  #                              orientation longitude may or may not appear on a particular grid).
  #
  #  earth_lons = Earth relative longitudes (in degrees)
  #  uin, vin     = Input winds to rotate
  #
  # Returns:
  #  uout, vout = Output, rotated winds
  #-----------------------------------------------------------------------------------------------------

  if lov_lon > 0.: lov_lon=lov_lon-360.
  dtr=np.pi/180.0             # Degrees to radians

  # Compute rotation constant which is also
  # known as the Lambert cone constant.  In the case
  # of a polar stereographic projection, this is one.

  if proj.lower()=='lcc':
    rotcon_p=np.sin(true_lat*dtr)
  elif proj.lower() in ['stere','spstere', 'npstere']:
    rotcon_p=1.0

  angles = rotcon_p*(earth_lons-lov_lon)*dtr
  sinx2 = np.sin(angles)
  cosx2 = np.cos(angles)

  # Steps below are element-wise products
  if inverse==False:
    # Return the earth relative winds
    uout = cosx2*uin+sinx2*vin
    vout =-sinx2*uin+cosx2*vin
  elif inverse==True:
    # Return the grid relative winds
    uout = cosx2*uin-sinx2*vin
    vout = sinx2*uin+cosx2*vin

  return uout,vout

The alternate method/routine is just a point of reference and not a suggested modification to Basemap, especially since it's not terribly general.  To use the routine in the example I've provided, simply call as follows (and update the other fig.add_subplot() settings from 12x to 13x:
  u10_rot_alt, v10_rot_alt = alt_rotate(lat_1,lon_0,lons,u10,v10,'lcc',inverse=True)
  ax = fig.add_subplot(133)
  ax.set_title('Alternate Rotated vectors')

  m.drawmapboundary(fill_color='aqua')
  m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
  m.drawcoastlines(color = '0.15')
  m.drawparallels(parallels)
  m.drawmeridians(meridians)

  m.barbs(x, y, u10_rot_alt, v10_rot_alt,
      pivot='middle', barbcolor='black',zorder=10)
  m.scatter(-70.0144,39.11,s=175,color='red',marker='*',latlon=True)
  plt.show()

Hi all,
I don’t know if I can reopen this issue.
I was recently doing some tests with Basemap’s rotate_vector utility on my WRF simulation data. I plan to plot the 10-m wind barbs on a map that has the same projection as the model grid. In my understanding, if someone is plotting wind vectors/barbs from a WRF on a map with the same projection as the model itself, then no rotation needs to be done to the model u and v wind components since they are already grid relative (Please correct me if I am wrong on this).
Out of curiosity, I converted my model u and v from grid-relative to Earth-relative using the following formula according to this website: https://www-k12.atmos.washington.edu/~ovens/wrfwinds.html
Uearth = Ucosalpha - Vsinalpha
Vearth = Vcosalpha + Usinalpha
, where cosalpha and sinalpha are given in the WRF output used for converting grid-relative winds to Earth-relative. Then I tried to rotate the Earth-relative u and v back to model-grid-relative using Basemap’s rotate_vector, after creating a map object with the same projection properties as the model itself. Theoretically, I should arrive back at the same grid-relative u and v components. However, when I plotted the grid-relative barbs rotated back from the Earth-relative u and v using rotate_vector on my map, I found some major differences between these barbs and the original model grid-relative barbs (see attached Fig. 1. Darkred barbs=original grid-relative; Green barbs=grid-relative rotated from Earth-relative using rotate_vector-“batch”-mode). Interestingly, the grid-relative barbs rotated back from Earth-relative winds behave similarly to the strange-looking barbs that Jacob got when rotating the barbs using rotate_vector. At some points, the winds are inconveniently from the due east or due south, where the u and v printout from the model output clearly suggests otherwise.
After finding this error, I tried the alt_rotate vector code provided by Jacob, with a few modifications to allow two reference latitudes. The modifications were based on the formula on WRF-Python’s website: https://wrf-python.readthedocs.io/en/latest/user_api/generated/wrf.uvmet.html?highlight=cone#wrf.uvmet
The modified alt_rotate code is also attached.
The grid-relative winds calculated from the Earth-relative winds using alt_rotate (by setting inverse=True) appear to closely match the original grid-relative winds from the model, with the largest difference only being ~1 cm/s. The plotted barbs also match well with the original grid-relative winds on the map (see attached Fig. 2. Darkred barbs=original grid-relative; Blue barbs=grid-relative rotated from Earth-relative using alt_rotate. The blue barbs cover the darkred barbs.).
I also conducted another test similar to the one that Jacob performed before where the rotation from Earth-relative back to grid-relative using rotate_vector was done element-wise for each point using nested for loops. Using this method, the derived grid-relative winds appear to be correct and match the original grid-relative winds well (see attached Fig. 3. Darkred barbs=original grid-relative; Green barbs=grid-relative rotated from Earth-relative using rotate_vector-element-wise. The green barbs cover the darkred barbs). The largest difference between the grid-relative winds rotated back from the Earth-relative winds and the original grid-relative winds is also ~1 cm/s.
Can someone familiar with Basemap provide an explanation as to why there is a difference between the resulting u and v components when rotate_vector is called in “batch” mode (supplying 2D inputs) versus called in element-wise mode?
To reproduce the above, I have attached my script and test data to this thread. I was using Basemap version 1.2.1.
Any help would be greatly appreciated,
David

test_data.zip
wrf_windbarb_rotation_TEST.txt
alt_rotateVec.txt

Hi David,

In my understanding, if someone is plotting wind vectors/barbs from a WRF on a map with the same projection as the model itself, then no rotation needs to be done to the model u and v wind components since they are already grid relative

This is correct.
As for why the basemap vector rotation routine behaves strangely - unfortunately I never arrived at a satisfactory conclusion. The alternative rotation you've tried, that I also use(d), does work. For what it's worth I think most folks have moved on to cartopy https://scitools.org.uk/cartopy/docs/latest/
-Jacob

Hi Jacob,
OK. No problem. Thank you for your response.
Since all of my plots were done in Basemap, I will just stick with Basemap for now but use the alt_rotate routine whenever I need to convert Earth-relative winds back to WRF (or map) grid-relative winds.
Cheers,
David

Thanks for the feedback, @Chun-ChihWang! The issue may stay here open until an appropriate solution is found. I do not use the barbs plotting regularly and I do not have the knowledge, but please feel free to provide any necessary feedback and I will try to take a look when I have some time slot free.

Hi, all. I just have some updates after working on this for a while. Another quick fix to the strange-looking vectors when rotating Earth-relative winds back to grid-relative winds using Basemap's rotate_vector is to recast the input Earth-relative U and V components from float32 to float64 before passing them to the rotate_vector function. The resulting U and V are very similar (within 1 cm/s) to the native grid-relative U and V components given by the WRF model. I don't know why there is a sensitivity to the input array data type (i.e., float32 vs float64). Maybe the Basemap developers will have a better idea of why that is.
I was making a transition from Basemap to Cartopy. However, it appears that Cartopy has its own issues with vector rotation, as described in David Oven's plotting WRF model winds plotting in Cartopy example (https://www-k12.atmos.washington.edu/~ovens/wrfwinds.html) and this post in wrf-python forum here (https://groups.google.com/a/ucar.edu/g/wrfpython-talk/c/5Kcz-qFQXAE/m/l0hX0JpLGwAJ). I also checked WRF-Python's plotting example of 500 mb heights and barbs using either Cartopy or Basemap (https://wrf-python.readthedocs.io/en/latest/plot.html) and the barbs do look off in the Cartopy plot. The resulting figures should look the same between Cartopy vs. Basemap, but obviously, they don't.
There is a code to correct the vector rotation issue with Cartopy described in David Oven's example and it seems to fix the problem, if I use Cartopy to plot my barbs. Plotting the resultant U and V from the correction function in Basemap still didn't give me the same result, so it appeared that the problem was specific to Cartopy.
It seems in Cartopy (I use v0.23.0), if I want to plot the barbs in the same map projection as the WRF model itself, the code below is the way to do it,
To get the Cartopy projection instance using WRF-Python
map_proj = wrf.get_cartopy(wrfin=input_wrf)    # create a Cartopy projection instance, which will be the same as the WRF
# simulation
A bunch of codes to read in the lon, lat, and native grid-relative U and V. I will call the WRF grid-relative U as Ua and grid-relative V as Va.
fig = plt.figure()
ax = fig.add_subplot(projection=map_proj)
x, y, _ = map_proj.transform_points(ccrs.PlateCarree(), lon, lat).T
This will transpose the resultant x, y, so transpose them back to the same shape as the original lon and lat fields
x=x.T
y=y.T
ax.barbs(x, y, Ua, Va, transform=map_proj)     # my way
note this is different from what other people have done. They did the below instead:
ax.barbs(lon, lat, Ua, Va, transform=ccrs.PlateCarree())   # other people's way
which I don't think is correct because when transform=ccrs.PlateCarree() is specified, I think it is telling Cartopy that the input U and V are Earth-relative, but they are not. Again, I might be wrong on this.
The plotted barbs using "my way" in Cartopy produced the same result as plotting them using Basemap in the same map projection. That's why I think "my way" is correct unless I plotted the wind barbs in Basemap incorrectly.
I will also consult with the folks in the WRF-Python forum and see what they have to say about this. At this point, I am confused about what approach I should take to plot the barbs correctly. It seems like nobody has a definitive answer yet.


scrollThreshold not unbound when container is removed from dom

I use pjax to swap out parts of the page body content without a full pageload.  When I have a page with infinite scroll on it and then pjax it out with other content, bindings seem to persist.  When I scroll on the new "page" that has no infinite scroll on it anymore, I still get "[InfiniteScroll] scrollThreshold" in the console.
Since pjax loads in new content dynamically that may or may not replace existing infinite scroll, handling this manually is undesirable.  infinite-scroll should detect when its container has been removed from the dom and unbind its events.
Test case: https://s.codepen.io/adam-lane/debug/qYGEbd/XxMVwaZBNeOr
I am hoping that infinite-scroll could have something like this in it...
$('.container').bind('DOMNodeRemoved', function(event) {
    destroy();
});

infinite-scroll should detect when its container has been removed from the dom and unbind its events

Add a 👍  reaction to this issue if you would like to see this feature added. Do not add +1 comments — They will be deleted.
Hmm, maybe. But I think this behavior it better suited for client-side code, rather than in Infinite Scroll.

Straightforward solution is to trigger destroy on the client side on page exit.

I'm closing this issue as this feature request did not get a lot of interest.


Error while deploying Kubo Cluster

Hello Team,
I am facing issue while deploying the kubo cluster on bosh
We have provided the region as us-east-1
Please refer to the attached screenshot

Hi @lordcf,
Looks like you lost network connectivity to your AWS cluster and BOSH could no longer communicate. So it failed to create VMs can you verify your network connectivity.
Thanks

@bstick12
My bad!!
There was a N/W issue we got sorted now.
But now while deploying the kubo-cluster on my bosh
I am getting this following issue

@lordcf Could we see the logs of the worker node to see why the kubelet failed to post as started. Possibly due to it not being able to contact the master node.

Thankyou !! @bstick12
There was an issue with the master node which is now good!
I am able to deploy the kubo-cluster on Bosh but not able to see the Kubo-Dashboard
It says not able to connect to the site

While accessing the Kubo-Dashboard, I am facing this issue whenever hitting the url:
User "system:anonymous" cannot get services/proxy in the namespace "kube-system".: "No policy matched."

@lordcf How are you trying to reach the dashboard? Are you using kubectl proxy ?

@lordcf Is this still an issue?


Update Facebook botton to not use any Facebook SDK

Just to remove the privacy unfriendly Facebook SDK with a simple button:

The number is just static for now. Not sure if number separators have a comma in Norwegian. It should be in Dutch.

Consider using i18n right away

Using the helper now, done.


Add print quality to renderer

An extra argument to ˙render()˙.

@deakjahn hello
can you provide an example / description of what it can be used for?

Yes. To render a PDF for printing. It depends on the native PdfRenderer and the Pdfium code behind it, but the bitmap it creates is supposedly slightly different from the bitmap created for display. I never checked the source code, frankly, but I think the difference is in how it handles aliasing of the edges. Printing has different requirements than displaying.

I checked in the meantime. FOR_DISPLAY uses LCD display specific aliasing techniques. This is clearly unwanted when rendering for print.

@deakjahn thanks for your contribution!


chore(ci): Handle external libraries in compilation timing report

Description
Problem*
Resolves #6722
Summary*
Just pushing a draft for now to see that things are working
Additional Context
Documentation*
Check one:

[X] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

We'd also like to track memory usage for the protocol circuits which we can pretty easily add in the same way in this PR.

Had a bit of a deeper look at this PR. Looks like you're trying to pass around a single compilation report from job to job and append to it?
If so have you considered having all the individual reports being generated in parallel and then having a single step to merge them all? This could just be a simple jq call.

If so have you considered having all the individual reports being generated in parallel and then having a single step to merge them all? This could just be a simple jq call.

Yeah I was hoping to switch to something like this. I wanted to get the basics of the github action working first and then look at how it can be done better.

Nice, I'll close all the performance issues :p

Yeah not sure why this started displaying such times...


feat: add bslint

@mason-org/triage notify(Reason::NewPullRequest)
This comment ensures a notification is delivered to maintainers.
 🤖 This is an automated comment.    📖 Source code


vdb-config AWS configuration challenge

Hi there,
I'm using prefetch version 3.0.0.  and I'm trying to download some dbGAP data. within vdb-config, I have selected

remote access (main tab)
accept charges (aws tab)

I also read trough https://github.com/ncbi/sra-tools/wiki/04.-Cloud-Credentials which describes, how the AWS IAM credentials can be retrieved. I've tried to format the credentials in various ways, ie pointing to to the downloaded csv file, changing read permissions etc -- however  when I try to run prefetch it fails with this error:
2022-02-26T02:12:17 prefetch.3.0.0 int: file unauthorized while opening file within network system module - cannot open remote file: https://sra-ca-run-odp.s3.amazonaws.com/sra/phs001963.c1/SRR15467117/SRR15467117
Interestingly, when deselecting the "accept charges" option in AWS tab of vdb-config, the download works OK.
This seems to indicate that the authentication with the AWS IAM credentials is the issue here. I'm trying to use AWS as I prefer to download directly from S3, rather than via the slower https.
Questions:

Can you please update the documentation on how to configure the AWS credentials file used by vdb-config and provide an example format ? ( the standard AWS credentials format seems to not work for me )
The vdb-config ui does not allow to select specific files - how will the config identify the correct file ? does it have to be named in a certain way ? (would be great if the Amazon cloud credentials page  gets updated)
Does the IAM user, which I am using,  require certain permissions ?

Did you select "report cloud instance identity"?
Were you using an NGC file or JWT cart to access the dbGaP data?

Did you select "report cloud instance identity"?
Were you using an NGC file or JWT cart to access the dbGaP data?

I encountered the same error as the original poster, no matter "report cloud instance identity" is checked or not. I was using NGC file. Could you help? Thanks

@zhangguy please write to<EMAIL_ADDRESS>to open a ticket. We will want to ask you to provide some additional details for the exact commands and configuration you are using and some of the output may provide more info that I am comfortable asking you to post in a public forum.


Provide example of sending nested form data

It would be great to have an example of how to properly form a request with nested data.
endpoint = "http://localhost:8080/form"
headers = ["User-Agent": "Mozilla/5/0...",  "Content-Type": "application/x-www-form-urlencoded"]

HTTPotion.post endpoint, [body: [model: [attribute_one: value_one, attribute_two: value_two]], headers: headers]

It's not entirely clear why this doesn't work. This is the resulting error message:
(Protocol.UndefinedError) protocol String.Chars not implemented for %HTTPotion.ErrorResponse

You have to run the form encoding function yourself.
I wonder how you got the idea that you can pass various objects as the body — all examples in the readme are clearly passing strings, there's even this example: "hello=" <> URI.encode_www_form("w o r l d !!")
Is there a way to make this clearer in the readme?

Ah ok, thanks for the response. I would have been helped by what you just said now. Thanks


Add overlay diagram to README.md

Signed-off-by: Rostyslav Fridman<EMAIL_ADDRESS>

Thanks for working on this.
I think it may be helpful if you change the wording from "NAT 10.x.x.0/16" to "SNAT to eth IP address". On the same lines, change "NAT services to endpoints" to "DNAT services to endpoints".
I think the 2 lines connecting "OVS" to "K8s switch" and "External switch" is a little confusing. What were you trying to express out there?

It may also help if you add multiple "K8s switch" connected to router (as we created one per host). And for each switch, you can have a mgmt interface and multiple pods connected.  And remove the connection from OVS to OVN block, that way we keep the logical topology seperate.

Good point about NAT. I renamed these lines.
Regarding the lines connecting OVS to OVN, I was trying to show IP flow.
It might be clearer if the flow lines are named:
http://i.imgur.com/qRki95i.png

Regarding the lines connecting OVS to OVN, I was trying to show IP flow.
It might be clearer if the flow lines are named:

Instead of getting those lines from OVS block, how about a different colored line that starts before the pod interface and external interface joins the OVS block and name those colored lines as "logical connections".

Updated the diagram to this one: https://i.imgur.com/i7sci9O.png

Thanks, merged.


Upgrade to reaction 0.23.4

0.23.1 includes the changes below since 0.21.0:

https://github.com/artsy/reaction/pull/516
https://github.com/artsy/reaction/pull/527

It seems like Mocha is still not recognizing *.graphql.ts as a TS file. I'll investigate further.

The CI is back to green so I'll just go ahead and merge this PR.

🎉 🎉 🎉 🎉


Update material.py

ignore some charset error cause by codec decode error

Thanks. I agree that this is better than crashing, although in the longer run it would probably be better to try to do something structured about the codec errors rather than ignoring them.


Improving on Filesystem

Currently the Filesystem class is only used by JsonReporter.
However I'd like to suggest extracting an interface from it and letting any scanner related classes use that.
I think it will definitely come in handy with the git version. For example you could avoid checking out entire working directories before scanning them. Instead just implement a GitFilesystem that has access to a repository and implements at least read and fileExists.
That way, scanning huge histories should become quite easy. Use getModifiedFiles of Gitter\Repository to find changed files only. Then use GitFilesystem to retrieve only modified files.
Should there be files that were not changed but still need analyzing (like super classes), GitFilesystem can easily fetch them when this is implement: #73
I'm not too set on "not checking the repository" out, so an alternative could be letting GitFilesystem handle the checkout or clone to a temp directory.
What do you think?

I'm not too sure I see how that example you gave would work. My guess is that checking out a full git branch is probably more easy/effective than pulling out a list of files from a specific commit.
Overall, I don't see what we'd gain. If you can expose your idea a little more, maybe I'll understand what you're trying to achieve with it.

Assuming that

you want to analyze long histories of active projects
generally fewer files are modified than there are stale/untouched files
repositories could be of any size or age, might contain binaries, documentation, assets etc.

Analyzing those in one go, that's a lot of disk writes that are wasting time and I/O.
For example here: https://github.com/tomzx/gitter/blob/php-semver-checker/lib/Gitter/Repository.php#L628-L639
You're already using this to prepare a list of modified files. But then you check out everything anyway, read the whole working directory and filter it again.
Keeping the assumptions in mind, I'm sure running git diff-tree and a few git shows is more effective as you're only reading and git is pretty good at that.
Adding --name-status to git diff-tree lets you know whether a file was added, modified or deleted.
If it was added, we only need to get it out of R2. Deleted: get it out of R1. If it was modified we retrieve both versions, then parse and forget them.

Added bonus: Users can analyze without modifying their working directory at all making it friendlier.
Anyway, I'm more interested in allowing to do that by using a tiny Filesystem interface/abstraction so that I'm not forced to work with actual files.

First, the reason I ask for the list of modified files is not to save time on checking out (which is generally very fast with git). The goal is to avoid READING/SCANNING all the files in the repository, which would take a lot of time and is essentially why this was put in place. On project like Symfony it would save a considerable amount of time from not having to parse ~5k files per compare operation.
Your idea sounds interesting in theory, but I'm skeptical we'll see any performance improvement in practice. It also seems to put a lot of burden on us to have to code a system which will do all these git operations while we can "already" just checkout the desired commits.
I'm however open to the idea, but I'd have to see it implemented and benchmarked.
Although, reading your last sentence, it sounds like you want to replace the Filesystem wrapper by something like Flysystem. Is that correct?

Well, it doesn't need to be a whole abstraction layer like Flysystem. I'll think about it some more and  mess around with the -git version to see what might make sense.

The goal is to avoid READING/SCANNING all the files in the repository, which would take a lot of time and is essentially why this was put in place.

But by checking them out, you are reading all the files from the repository AND writing them to disk. On a related note: IMO both findFromString calls in git-checker's CompareCommand could be dropped right now for example. Can be expensive without exclude-* configuration and it should be enough to rely on getModifiedFiles.

I should probably make it more clear that when I said read/scan, I meant the process of actually opening the file for reading and using PHPParser to parse its content.
I do think you are right that there could probably be some improvement done in order not to scan all the files in the included directory, but only those that are modified. We currently rely on the Finder to take care of exclusion for us, since the modified files can obviously return us an immense list of files we have no interest in.


Is it possible to use onchange method like this?

Description:
Is it possible to use onchange (or other) method like this? I don't want to use m.withAttr() method. When I use this approach, todo.vm.onchange() method is not firing.
<!doctype html>
<title>Todo app</title>
<script src="//cdnjs.cloudflare.com/ajax/libs/mithril/0.2.5/mithril.min.js"></script>
<body>
<script>

var todo = {};
todo.vm = (function() {

    var vm = {}

    vm.init = function() {
        vm.description = m.prop("");
        vm.click = function() {
            console.log("click", vm.description())
        };
        vm.onchange = function() {
            console.log("onchange", vm.description())
        };
    }
    return vm
}())

todo.controller = function() {
    todo.vm.init()
}

//here's the view
todo.view = function() {
    return m("html", [
        m("body", [
            m("input", {
                //this is from example
            	//onchange: m.withAttr("value", todo.vm.description),
                onchange: todo.vm.onchange, // <------
            	value: todo.vm.description()
            }),
            m("button", {
            	onclick: todo.vm.click
            }, "Add")
        ])
    ]);
};

//initialize the application
m.mount(document, {controller: todo.controller, view: todo.view});

</script>
</body>

Your code is working fine for me.
https://jsbin.com/rohile/1/edit?js,console,output

Note that for the change event you need to "commit" the value before it fires, I do so by clicking outside of the <input> element. https://developer.mozilla.org/en-US/docs/Web/Events/change

@tivac, As you see onchange method is called only when button clicked. Not when the input change. Is this expected behaviour?

The change event only fires when the field is blurred, yes. Check out the MDN link I provided.
If you want the event to fire every time the value changes you should use the input event instead.

Thanks!


clang-tidy complains of virtual function dispatch bypass

If you run clang-tidy test_pstreams.cc you get this complaint:
.../pstream.h:1621:7: note: Call to virtual method 'basic_pstreambuf::sync' during destruction bypasses virtual dispatch

I'm not sure what it's babbling about since sync() isn't virtual. Is clang-tidy stoned, or has it actually got a point here?

Bypassing virtual dispatch is actually exactly what we want here, so the code is correct. But I'll change it to call basic_streambuf::sync(); to make that explicit.

Confirmed in the real-world case where I originally found it. Thanks for the fix!


Source Strapi v5 doesn't contain any fields in types

Describe the bug
I'm using the Strapi v5 version of gatsby-source-strapi (#478) with yarn link.
The collection and single Strapi types configured in my gatsby-config.js are found but they do not contain any fields.
Even though the fields exist and are populated in my Strapi instance. When I use<EMAIL_ADDRESS>the fields on the same types are found.
This is the error I'm getting:
 ERROR #12100  API.TYPESCRIPT.TYPEGEN

There was an error while trying to generate TS types from your GraphQL queries:

    Error: GraphQL Document Validation failed with 1 errors;
  Error 0: Cannot query field "Titel" on type "STRAPI_IMMO_LEADS_PAGE".
    at GraphQL request:6:11

See our docs page for more info on this error: https://gatsby.dev/graphql-typegen

failed Generating GraphQL and TypeScript types - 0.161s

The result from the stapi api when fetching the same single type:

The type in the GraphiQL explorer:

To Reproduce
Steps to reproduce the behavior:

Create a single type in strapi
Add content to the single type and publish it
Connect gatsby-source-strapi with the strapi instance.
Check out the types in GraphiQL workbench.
The types are there but edges -> node doesn't contain any fields.

Expected behavior
The Strapi types should contain fields.
System Info
Please provide information about your site via these means as possible:
gatsby info:
System:
   OS: macOS 15.0
   CPU: (10) arm64 Apple M1 Pro
   Shell: 5.9 - /bin/zsh
 Binaries:
   Node: 18.20.3 - /private/var/folders/sg/7qlzh78n07d0n3v6bzh_twch0000gn/T/xfs-aa16fd5b/node
   Yarn: 4.0.2 - /private/var/folders/sg/7qlzh78n07d0n3v6bzh_twch0000gn/T/xfs-aa16fd5b/yarn
   npm: 10.7.0 - ~/.nvm/versions/node/v18.20.3/bin/npm
 Browsers:
   Chrome: 129.0.6668.70
   Safari: 18.0
 npmPackages:
   gatsby: ^5.13.7 => 5.13.7
   gatsby-plugin-emotion: ^8.13.1 => 8.13.1
   gatsby-plugin-google-gtag: ^5.13.1 => 5.13.1
   gatsby-plugin-image: ^3.13.1 => 3.13.1
   gatsby-plugin-manifest: ^5.13.1 => 5.13.1
   gatsby-plugin-mdx: ^5.13.1 => 5.13.1
   gatsby-plugin-schema-snapshot: ^4.13.0 => 4.13.0
   gatsby-plugin-sharp: ^5.13.1 => 5.13.1
   gatsby-plugin-sitemap: ^6.13.1 => 6.13.1
   gatsby-source-filesystem: ^5.13.1 => 5.13.1
   gatsby-source-strapi: ^3.3.3 => 4.0.0
   gatsby-transformer-sharp: ^5.13.1 => 5.13.1
 npmGlobalPackages:
   gatsby: 5.13.7

The update flag in gatsby-plugin-schema-snapshot is set to true.

@AlexanderProd if you came from 1.0.3, you came from Strapi v3. Are you sure you ment that?
We debug endpoints on the command line, are you sure these calls are returning your data correctly?
I don't know about gatsby-plugin-schema-snapshot, maybe that clashes? Did you fully clean all caches?
Did you set version: 5 on your config?

I had the same problem, and the solution was to set version: 5 in strapiConfig.


[Feature Request] Give a prompt when the user chose native provider

Need to give prompt info when the user chose native provider.
like: native provider only supports create and join.

UI 样式


[Bug] Setting ExternalCameraEmissiveColor to a different color creates a strange effect

Setting ExternalCameraEmissiveColor to a different color causes the posterization effect to mess with the camera a bit
(vanilla behaves normally and the posterization effect doesn't mess with the ship camera)
Or maybe it's just the vanilla emissive color that's showing on top of the custom color
Edit: After some more testing it seems like it only happens with some colors
ExternalCameraEmissiveColor = 0.05, 0.13, 0.05
https://github.com/Zaggy1024/LC_OpenBodyCams/assets/77690119/580b980b-2dcd-4736-ac64-b96be02310b7
https://github.com/Zaggy1024/LC_OpenBodyCams/assets/77690119/aaa39efb-8f30-41b1-9470-73658e8b72a9

Unfortunately, this is not a bug. It's just the nature of how the posterization filter works, you can see it in the shading on the wall in dark areas as well.
The option is there for people that want to spend the time to tweak that screen, but I don't have any values to recommend for it.
It's possible that there are other values that could be adjusted to make it appear more similar to the body cam, but that would take some experimentation.

Unfortunately, this is not a bug. It's just the nature of how the posterization filter works, you can see it in the shading on the wall in dark areas as well.

I kinda figured that it was just the posterization being weird after doing some more testing.

It's possible that there are other values that could be adjusted to make it appear more similar to the body cam, but that would take some experimentation.

yea that's pretty much what I was trying to achieve. I actually just used the same emission color as the bodycam.
tho I haven't been able to see how close it looks because I don't have a second player to test it.

It's pretty easy to test out the body cams if you spawn in some radar boosters with LethalDevMode or a similar mod.
If you have LethalConfig and enable the DisplayOriginalScreenWhenDisabled option, you can switch between the external camera and the body cams with the EnableCamera option.


coverage-summary.json for the lastcommit files only

How to get the coverage-summary.json for the last-commit files only from the jest?
Thank you in advance !

@edward

Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.


Adding the option to switch to burp collaborator

Can you please add the feature to switch to bup collaborator in the extension itself?

could you create a version by default with burp collaborator? dnslog.cn doesn't work, thanks for your BURP plugin

could you create a version by default with burp collaborator? dnslog.cn doesn't work, thanks for your BURP plugin

I uploaded a specially compiled version, please go to the release page and download for burpcollaborator version package

Thanks a lot.

thanks for this version too

version v0.8 add dnslog platform change panel.


member_of_research_project

member_of_research_project is a field in the diagnosis table of CDA.
If we want to pull all members of a research project, then probably we would want to do this via the query, and so I think this may not be something we need to store in the phenopacket.
Thoughts?

member_of_research_project is a field in the diagnosis table of CDA. If we want to pull all members of a research project, then probably we would want to do this via the query, and so I think this may not be something we need to store in the phenopacket.
Thoughts?

I think we are going to want to include this because people may want to use the study as a variable.  Or they may want to pull out subsets of a cohort they already have a set of phenopackets for rather than redoing the query & conversion.


Error: 'md5sum' not installed

~$ atfile upload tools.csv
Error: 'md5sum' not installed

Perhaps list this as a prerequisite?

~$ atfile upload tools.csv
Error: 'md5sum' not installed

Perhaps list this as a prerequisite?

There's a few progs dotted around that it needs, as well as some optional ones (which trigger when required). But I guess there's no harm in sticking it in the README :+1:

@archiewood Added requirements to the README: https://github.com/ziodotsh/atfile?tab=readme-ov-file#-requirements


Deployments show resources from other namespaces in the cluster explorer

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create two namespaces
In each namespace create a deployment with

  selector:
    matchLabels:
      app: deployment

and equivalent mod spec fields
3. Open the cluster explorer
4. Select "Only user namespaces" in the namespaces dropdown
5. View one of the two deployments
Result:
In the pods tab you will see all of the pods for both deployments. That tab should be scoped to the namespace that the deployment is in
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.5
Installation option (single install/HA): Hosted Rancher

gz#14889

Ran a quick test on v2.5.5. Created alpha deployment with replica of one and beta deployment with replica of one. Both have "app: myapp" selector. Looks like Cluster Manager view correctly shows one pod in the deployment, Cluster Explorer shows pods that do not belong to the deployment:


NFFS file system does no build when newlib libc is used

The NFFS file system does not build when newlib libc is used due to type conflicts in NFFS os specific function  implementations. This is caused due to the fact that NFFS uses uint32_t (defined as unsigned long in case of newlib) in the prototypes but zephyr uses u32_t (defined as unsigned int) in the implementations.

Shouldn't the fix in #5468 be the other way around, fixing the declaration of u32_t to match uint32_t?  (I never bought the argument for these short types, but... pick your battles, I guess.)

@lpereira  Actually that was my first fix where I update zephyr/types.h to typedef uint32_t to u32_t but I thought this was a bit to intrusive.


Styling of snippets (Mozilla anoncements at bottom of start page)

Thanks @batisteo! Should be fixed

Perfect, thanks!!


Primitive includes don't work with JsonApiSerializer

I use the version 0.17.0 and  my transformer has code like that
public function includeAssigned($course)
{
       return $this->primitive((int)$course['assigned']);
}

Every time I try to serialize my data I get an exception
If I use another serializer say ArraySerializer I will get normal result.
Warning: array_key_exists() expects parameter 2 to be array, integer given in /var/www/l***/vendor/league/fractal/src/Serializer/JsonApiSerializer.php:316
#0 /var/www/***/vendor/league/fractal/src/Serializer/JsonApiSerializer.php(182): League\Fractal\Serializer\JsonApiSerializer->isNull(1)

Primitives don't work with the JsonApiSerializer because this serializer requires the transformed values to match a specific format so that they can appropriately be packed into the jsonapi format.
A proper transformed data array will look like this:
[
  'id' => 1
]

And of course a primitive shouldn't ever look like this. Instead just use an Item instance:
public function includeAssigned($course)
{
    return $this->item(['id' => $course['assigned'], function($data) { return $data; }, 'course');
}

That all said, we could change the JsonApiSerializer to just use the primitive type data as the ID by default, but I'd argue that that is a little confusing.


Add support for feed generation

Hey, love your work. Wanted to subscribe to your blog via a feed, but there wasn't one, so here's a minimal implementation that oughta get the ball rolling.
Some caveats:

This punts most responsibility for the actual feed template onto the user to be provided in a feed.xml template, and assumes that it contains an Atom template, not an RSS one.
For the in-feed URLs to be generated correctly, a --base-url param must be passed at build time, given that feeds expect their URLs to be in absolute, not relative form. Not doing so won't cause errors, but will use http://localhost as the base which is kinda weird. (When running the non-frozen server, I believe the base URL is inferred from the request anyway.)
During build time, flask_frozen prints a warning about the MIME type not matching for the .xml file.

Nevertheless, I hope this is acceptable for inclusion. Imma open a PR against krystalgamer.github.io with the necessary template changes in a minute – that said, they won't have any effect until this is merged.

Thank you so much for the PR! I'm not super into feeds (even though I ought to do it), but from the looks of seems great! The only change I'd do is to not generate the feed.xml if no base-url is passed to prevent non-functional feeds from being created.

I'll merge them now! I also made a little change include a <summary> with the post description.


Dummy issue to test doc - Please do not close - Metrics Advisor

Dummy issue to test doc - Please do not close

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

ID: 548ca45c-5034-0fab-43a7-e2365083fd82
Version Independent ID: 1dacf768-16ee-2621-6544-c1a8cf1f31e5
Content: What is the Azure Metrics Advisor service? - Azure Applied AI Services
Content Source: articles/cognitive-services/metrics-advisor/overview.md
Service: applied-ai-services
Sub-service: metrics-advisor
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

Dummy issue - Not to close

#please-close. Test successful.


Condensed endpoint declaration macro

There's a lot of repetition in the endpoint declarations.  Would you accept a PR that introduced a macro for making these easier to define?

It's a little DSL-y, but it sure cuts down on a ton of boilerplate, IMO
Still generates all the same code and documentation:

(I still have to update it to handle parameters like {pool_id}, but you get the idea)

It's a good idea, I have two questions with regards to it:

Some endpoints require different types in the path parameters:

Requires Integer:
https://docs.blockfrost.io/#tag/Cardano-Blocks/paths/~1blocks~1slot~1{slot_number}/get
Requires String:
https://docs.blockfrost.io/#tag/Cardano-Accounts/paths/~1accounts~1{stake_address}/get
Require Integer and String:
https://docs.blockfrost.io/#tag/Cardano-Blocks/paths/~1blocks~1epoch~1{epoch_number}~1slot~1{slot_number}/get
Would this add too much complexity to the macro? I'm concerned this makes it complex and more weirder to maintain than the current implementation.

If default query parameters were to be implemented, and order is set to Descending at the creation of the BlockFrostApi, the suffix "?order=desc" should be added in every request? Even those who do not expect the count parameter?

If this is not desirable, we would need some way of telling each function what parameters should be inserted in the final URL. The easiest way would be using docs.rs/bitflags, and the macro would need to handle it too.

Here it is with added parameters:

You just specify the list of parameters and types, and it expands out into parameters to the method, and arguments to the format!
As an escape hatch, any that require particularly custom handling could be declared as normal, and wouldn't need to use the DSL.
If you wanna see what the code looks like with all the current methods converted:
https://github.com/blockfrost/blockfrost-rust/compare/master...SundaeSwap-finance:pi/pagination?expand=1

Nice!
(I'm kinda convinced we are not gonna worry about filtering out query parameters (that second question), unexpected parameters are always ignored anyway.)
so you have the greenlight, PR is welcome :slightly_smiling_face:.

Awesome; I'm gunna get some sleep now, but expect a PR tomorrow!  (Also, Rust's macro system is unruly, but amazing... lol)

(on a side note, while you're here... I know this isn't the right avenue for this, but how hard would it to get a /pool/{pool_id}/delegators/{epoch} endpoint, to find out the exact set of delegators for a given epoch snapshot in the past?

(on that side note, I'm not sure, I'll redirect the question to @mmahut and we'll answer you when possible :+1:)

hey @Quantumplation! :)
I think you are looking for /epochs/{number}/stakes/{pool_id}. But it is true this endpoint would make also sense in the /pools list, we will add an alias to it there as well. Thank you!

@mmahut Ohhhh, perfect! Yea, I totally missed that! Thank you! <3


Bump minSdkVersion to 26 in the docs

This should've been added in
https://github.com/hotwired/turbo-android/pull/293

Thank you @kyrylo 👍


logging changes

PR Branch
#ADD LINK TO THE PR BRANCH
Motivation and Context
Checklist:

[ ] Unit tests added

[ ] Integration tests added

[ ] Test names are meaningful

[ ] Feature manually tested

[ ] Branch build passed

[ ] No 'package.*' in the imports

[ ] Relevant Wiki page updated with clear instruction for the end user

[ ] Not applicable. This was only a refactor change, no functional or behaviour changes were introduced

[ ] Http test added to http-testing module(if applicable) ?

[ ] Not applicable. The changes did not affect HTTP automation flow

[ ] Kafka test added to kafka-testing module(if applicable) ?

[ ] Not applicable. The changes did not affect Kafka automation flow

Thanks @IshaJ721 ,
Looks like there is 1 error in the PR. See screenshots beelow. Can you please fix this please?
CI Build Link:
https://github.com/authorjapps/zerocode/actions/runs/5365766051/jobs/9740988963

Thanks @IshaJ721 , Looks like there is 1 error in the PR. See screenshots beelow. Can you please fix this please?
CI Build Link: https://github.com/authorjapps/zerocode/actions/runs/5365766051/jobs/9740988963

A fix for this was pushed into the logging branch more than a week ago. I replaced error() with warning(). Can you rebuild?

I built using intelliJ and the log is below.
There are no errors as shown in the intelliJ log below...
Clearing build system data...
Executing pre-compile tasks...
Cleaning output directories…
Running 'before' tasks
Checking sources
Copying resources... [zerocode-tdd-jupiter]
Copying resources... [zerocode-tdd]
Copying resources... [zerocode-maven-archetype]
Copying resources... [kafka-testing]
Copying resources... [http-testing]
Parsing java… [zerocode-tdd]
java: source value 8 is obsolete and will be removed in a future release
java: target value 8 is obsolete and will be removed in a future release
java: To suppress warnings about obsolete options, use -Xlint:-options.
Writing classes… [zerocode-tdd]
Updating dependency information… [zerocode-tdd]
Adding nullability assertions… [zerocode-tdd]
Adding threading assertions… [zerocode-tdd]
Adding pattern assertions… [zerocode-tdd]
Parsing java… [tests of zerocode-tdd]
Writing classes… [tests of zerocode-tdd]
Updating dependency information… [tests of zerocode-tdd]
Adding nullability assertions… [tests of zerocode-tdd]
Adding threading assertions… [tests of zerocode-tdd]
Adding pattern assertions… [tests of zerocode-tdd]
Parsing java… [zerocode-tdd-jupiter]
Writing classes… [zerocode-tdd-jupiter]
Updating dependency information… [zerocode-tdd-jupiter]
Adding nullability assertions… [zerocode-tdd-jupiter]
Adding threading assertions… [zerocode-tdd-jupiter]
Adding pattern assertions… [zerocode-tdd-jupiter]
Parsing java… [tests of zerocode-tdd-jupiter]
Writing classes… [tests of zerocode-tdd-jupiter]
Updating dependency information… [tests of zerocode-tdd-jupiter]
Adding nullability assertions… [tests of zerocode-tdd-jupiter]
Adding threading assertions… [tests of zerocode-tdd-jupiter]
Adding pattern assertions… [tests of zerocode-tdd-jupiter]
Parsing java… [kafka-testing]
Writing classes… [kafka-testing]
Updating dependency information… [kafka-testing]
Adding nullability assertions… [kafka-testing]
Adding threading assertions… [kafka-testing]
Adding pattern assertions… [kafka-testing]
Parsing java… [tests of kafka-testing]
Writing classes… [tests of kafka-testing]
Updating dependency information… [tests of kafka-testing]
Adding nullability assertions… [tests of kafka-testing]
Adding threading assertions… [tests of kafka-testing]
Adding pattern assertions… [tests of kafka-testing]
Parsing java… [http-testing]
Writing classes… [http-testing]
Updating dependency information… [http-testing]
Adding nullability assertions… [http-testing]
Adding threading assertions… [http-testing]
Adding pattern assertions… [http-testing]
Parsing java… [tests of http-testing]
Writing classes… [tests of http-testing]
Updating dependency information… [tests of http-testing]
Adding nullability assertions… [tests of http-testing]
Adding threading assertions… [tests of http-testing]
Adding pattern assertions… [tests of http-testing]
Running 'after' tasks
javac 20.0.1 was used to compile java sources
Finished, saving caches…
Executing post-compile tasks...
Finished, saving caches…
Synchronizing output directories...
7/8/2023 6:41 PM - Build completed successfully with 180 warnings in 1 min, 10 sec

Hello All, I am making some minor changes to the PR to make it better.
e.g. the following:

Remove the "id=null" printing in the log/console
Some INFO level --> updating to WARN, as few dependent libs printing lot of debug-info/noise at INFO level
Some WARN level --> updating to INFO or DEBUG etc
Trying to run few Kafka and Multi-step tests so see everything hanging together as expected in the log
etc


Unable to install on latest Nest.js

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nestjs/common
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^7.0.0 || ^8.0.0 || ^9.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@nestjs-packages/sqs
npm ERR!   @nestjs-packages/sqs@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/ahernandez2/.npm/_logs/2024-06-26T16_44_59_392Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /Users/ahernandez2/.npm/_logs/2024-06-26T16_44_59_392Z-debug-0.log

can get around this with
"overrides": {
"@nestjs/sqs": {
"@nestjs/common": "^10.0.0"
}
},
but unsure if safe