Exported makefile style improvement respect 80 column char limit and alphabetize

In this exported makefile we see a few things that could be improved.
The SRSC, LOCAL_INCLUDE_PATHS lists and probably others could be set such that the exported list has less than 80 chars per line, adding a \ at the end of each line to carry over to the next line.  Also it'd be nice if that list was alphabetized.
## Haiku Generic Makefile v2.6 ##

## Fill in this file to specify the project being created, and the referenced
## Makefile-Engine will do all of the hard work for you. This handles any
## architecture of Haiku.

# The name of the binary.
NAME = BeMobile

# The type of binary, must be one of:
#	APP:	Application
#	SHARED:	Shared library or add-on
#	STATIC:	Static library archive
#	DRIVER: Kernel driver
TYPE = APP

# 	If you plan to use localization, specify the application's MIME signature.
APP_MIME_SIG =

#	The following lines tell Pe and Eddie where the SRCS, RDEFS, and RSRCS are
#	so that Pe and Eddie can fill them in for you.
#%{
# @src->@

#	Specify the source files to use. Full paths or paths relative to the
#	Makefile can be included. All files, regardless of directory, will have
#	their object files created in the common object directory. Note that this
#	means this Makefile will not work correctly if two source files with the
#	same name (source.c or source.cpp) are included from different directories.
#	Also note that spaces in folder names do not work well with this Makefile.
SRCS =  Pattern.cpp Matcher.cpp santa/BetterScrollView/BetterScrollView.cpp santa/ColumnListView/CLVColumnLabelView.cpp santa/ColumnListView/CLVEasyItem.cpp santa/ColumnListView/CLVListItem.cpp santa/ColumnListView/ColumnListView.cpp santa/Cursors/Cursors.cpp santa/NewStrings/NewStrings.cpp santa/PrefilledBitmap/PrefilledBitmap.cpp santa/ScrollViewCorner/ScrollViewCorner.cpp phonelist.cpp callregslotview.cpp phonelistslotview.cpp bemobile.cpp dialabout.cpp dialeditpbook.cpp dialnewsms.cpp dialcalevent.cpp dialcalendar.cpp gsm.cpp main.cpp mainwindow.cpp workview.cpp calview.cpp pbbynameview.cpp pbview.cpp smsview.cpp smsboxview.cpp smsinboxview.cpp statusview.cpp mobileview.cpp initwindow.cpp

#	Specify the resource definition files to use. Full or relative paths can be
#	used.
RDEFS =

#	Specify the resource files to use. Full or relative paths can be used.
#	Both RDEFS and RSRCS can be utilized in the same Makefile.
RSRCS =

# End Pe/Eddie support.
# @<-src@
#%}

#	Specify libraries to link against.
#	There are two acceptable forms of library specifications:
#	-	if your library follows the naming pattern of libXXX.so or libXXX.a,
#		you can simply specify XXX for the library. (e.g. the entry for
#		"libtracker.so" would be "tracker")
#
#	-	for GCC-independent linking of standard C++ libraries, you can use
#		$(STDCPPLIBS) instead of the raw "stdc++[.r4] [supc++]" library names.
#
#	- 	if your library does not follow the standard library naming scheme,
#		you need to specify the path to the library and it's name.
#		(e.g. for mylib.a, specify "mylib.a" or "path/mylib.a")
LIBS =  libbe.so libroot.so libdevice.so libstdc++.r4.so

#	Specify additional paths to directories following the standard libXXX.so
#	or libXXX.a naming scheme. You can specify full paths or paths relative
#	to the Makefile. The paths included are not parsed recursively, so
#	include all of the paths where libraries must be found. Directories where
#	source files were specified are	automatically included.
LIBPATHS =

#	Additional paths to look for system headers. These use the form
#	"#include <header>". Directories that contain the files in SRCS are
#	NOT auto-included here.
SYSTEM_INCLUDE_PATHS =  /boot/develop/headers/be /boot/develop/headers/cpp /boot/develop/headers/posix /boot/develop/lib /boot/beos/system/lib

#	Additional paths paths to look for local headers. These use the form
#	#include "header". Directories that contain the files in SRCS are
#	automatically included.
LOCAL_INCLUDE_PATHS =  regexp santa/BetterScrollView santa/ColumnListView santa santa/Cursors santa/NewStrings santa/PrefilledBitmap santa/ScrollViewCorner

#	Specify the level of optimization that you want. Specify either NONE (O0),
#	SOME (O1), FULL (O2), or leave blank (for the default optimization level).
OPTIMIZE := FULL

# 	Specify the codes for languages you are going to support in this
# 	application. The default "en" one must be provided too. "make catkeys"
# 	will recreate only the "locales/en.catkeys" file. Use it as a template
# 	for creating catkeys for other languages. All localization files must be
# 	placed in the "locales" subdirectory.
LOCALES =

#	Specify all the preprocessor symbols to be defined. The symbols will not
#	have their values set automatically; you must supply the value (if any) to
#	use. For example, setting DEFINES to "DEBUG=1" will cause the compiler
#	option "-DDEBUG=1" to be used. Setting DEFINES to "DEBUG" would pass
#	"-DDEBUG" on the compiler's command line.
DEFINES =

#	Specify the warning level.
WARNINGS =

#	With image symbols, stack crawls in the debugger are meaningful.
#	If set to "TRUE", symbols will be created.
SYMBOLS :=

#	Includes debug information, which allows the binary to be debugged easily.
#	If set to "TRUE", debug info will be created.
DEBUGGER :=

#	Specify any additional compiler flags to be used.
COMPILER_FLAGS = -Woverloaded-virtual -funsigned-bitfields -Wwrite-strings

#	Specify any additional linker flags to be used.
LINKER_FLAGS =

#	(Only used when "TYPE" is "DRIVER"). Specify the desired driver install
#	location in the /dev hierarchy. Example:
#		DRIVER_PATH = video/usb
#	will instruct the "driverinstall" rule to place a symlink to your driver's
#	binary in ~/add-ons/kernel/drivers/dev/video/usb, so that your driver will
#	appear at /dev/video/usb when loaded. The default is "misc".
DRIVER_PATH =

## Include the Makefile-Engine
DEVEL_DIRECTORY := \
	$(shell findpaths -r "makefile_engine" B_FIND_PATH_DEVELOP_DIRECTORY)
include $(DEVEL_DIRECTORY)/etc/makefile-engine

Also to note, the RDEFS = wasn't populated when exporting.

I think a lot of this could be improved once compilation flag generation happens consistently. Until it exports Paladin's Makefile consistently I'll keep this issue open.


StackOverflowException in Logger.isEnabled with Spring Boot 3 + Tomcat

Description
Tomcat calls Logger.isEnabled at the beginning of its ClassLoader#loadClass implementation.
If the method requires to load additional classes (e.g. org.apache.logging.log4j.core.Filter.Result) an infinite recursion occurs.
Reproduction

configure Tomcat to use Log4j 2.x as server's logging framework,
add a Spring Boot 3 application without Log4j2 jars,
a stack overflow occurs.

Details
This issue was first reported in this StackOverflow question.
The problem occurs because:

If no logger context exists for a given classloader and configLocation == null the ClassLoaderContextSelector returns the logger context for the parent classloader. This is what happens in most LogManager.getContext calls;
Spring Boot adds a class from the webapp classloader as global filter to the logger context's configuration;
Tomcat calls Logger.isEnabled at the beginning of ClassLoader#loadClass hence it triggers the loading of all classes used by the global filter. This process uses the webapp classloader, hence the recursion.

I think this problem is more general than you are making it out to be. Anytime there is a sequence of
app-> jul -> log4j -> 3rd party -> jul
there will be an infinite loop. We need to prevent that by detecting recursion in ApiLogger.

I am closing this, since it was fixed in Spring Boot 3.1.11 and 3.2.5.


Support changelog for monorepos

Example: babel (https://github.com/babel/babel/tree/master/packages)

Waiting on #381


Add support for MAX7321

This PR adds support for the MAX7321 I2C Port Expander.
This chip is very similar to the already implemented PCF8574.

Ah yes of course, I must have missed a last cargo fmt before pushing. Should be fixed now.


Describe how to run admin in the development

describe:

linking
yarn types
yarn build
yarn bundle
yarn bundle:globals

describe the distinction in production/development build
Also, write a script which runs all things together.

Ready in https://github.com/SoftwareBrothers/adminjs/pull/1017 by improving https://github.com/SoftwareBrothers/adminjs-dev


Add Features to Docs.rs & Inline Re-exported Crates

Also updates some presumably out-of-date docs.

The cargo.toml change is fine. For the lib.rs:

I prefer the flat module layout (For a project in this phase of maturity I usually avoid renames/moves unless it's a substantial improvement in clarity. I think we might just go in circles otherwise.)
I would keep the first doc comment explaining how to generate full docs. (Even with the feature flags in the cargo.toml, it's still not really complete since the end-user can pick other docs.)
What does the doc(inline) do? Again for this phase of the project, I'm not too concerned with what rustdoc looks like, and default behavior I saw previously seemed fine. I'm open to this change, just again for a project that is still not mature and likely to change, I err towards avoiding purely cosmetic changes unless one way is clearly better than another.

Just looked up doc(inline). I think the way it presents in rustdoc now is fine (but if you want to paste a screenshot of what it would look like after the change, happy to look with an open mind!)
FYI while rafx-api did get a pretty decent pass on rustdoc (as I think rafx-api is pretty mature and unlikely to change significantly, there is little to no rustdoc comments in the higher-level code, and I don't plan on making a pass to improve this until it is more mature.

I prefer the flat module layout (For a project in this phase of maturity I usually avoid renames/moves unless it's a substantial improvement in clarity. I think we might just go in circles otherwise.)

Makes sense. 👍

I would keep the first doc comment explaining how to generate full docs. (Even with the feature flags in the cargo.toml, it's still not really complete since the end-user can pick other docs.)

There I put that back in there.I'll put that back in there.

Just looked up doc(inline). I think the way it presents in rustdoc now is fine (but if you want to paste a screenshot of what it would look like after the change, happy to look with an open mind!)

Here's with the inlined docs:

And here's without:

It's subjectively "nicer" looking without the re-exports section and you also get the descriptions of the re-exported modules. For instance, with the framework module, you can see the description of it in the inlined version, but you would have to click on it in the re-exports section.
The biggest reason to inline the docs, though, is for searching. If you search RafxApi on docs.rs/rafx right now it will not find anything because RafxApi is in the api re-export. If you inline the docs, though, you can search RafxApi and it will it in rafx::api::RafxApi because it treats api like an inline module instead of a separate crate.

FYI while rafx-api did get a pretty decent pass on rustdoc (as I think rafx-api is pretty mature and unlikely to change significantly, there is little to no rustdoc comments in the higher-level code, and I don't plan on making a pass to improve this until it is more mature.

OK, sounds good.

Sorry for the delay on this, I've been busy with prototyping a blender export workflow for models and scenes and not looking at GitHub, and I forgot about this :)


[WIP] Test general-ci - DO NOT MERGE

Test new ngraph-ci-premerge.groovy changes on branch chrisl/test-general-ci

No longer needed.  Closing and deleting the branch.


Better dependency documentation for GPU Aware Scheduling

Minor logging improvement and a lot of dependency yamls to simplify setup for newbies.

LGTM

squashed, merging after checks are ok


Go to top button isn't working in Assets selector list

Describe the bug
Go to top button isn't working in Assets selector list
To Reproduce
Steps to reproduce the behavior:

Go to Receive modal
Open assets selector list
Click on button
See error

Expected behavior
It should work on all screens
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: macOS
Browser FF
Version 122

Additional context
Reproducible on dev branch
https://github.com/superhero-com/superhero-wallet/assets/69896204/6f0bc45f-867a-4a6c-af7d-409549348fb0

LGTM


add clean stateful checkpoint handler into tcontroller

This PR added the clean stateful checkpoint handler into tcontroller. Stub method in tmaster will be updated in later pr.

Looks good to me


Dart should allow invalid scalar values for string literals

The spec currently (as of 2013-09-24) states:
===
\u{HEX_DIGIT_SEQUENCE} is the unicode scalar value represented by the HEX_DIGIT_SEQUENCE. It is a compile-time error if the value of the HEX_DIGIT_SEQUENCE is not a valid unicode scalar value.
===
We should remove this limitation since users can create these strings dynamically anyway. In most cases it just makes testing more difficult.

Dupe of #26620.


Update bigquery_reader_ops.py

Fix example code in comments by replacing tf.training.string_input_producer with tf.train.string_input_producer

Can one of the admins verify this patch?

I signed it!

You have to git amend your commit to use the email you signed the CLA with.
https://patch-diff.githubusercontent.com/raw/tensorflow/tensorflow/pull/11760.patch shows that it is using the default github one, so you'll have to update it.  Either send a new PR for it or git commit --amend and then force push!

Jenkins, test this please.


macOS name in automated smapp releases

Change mac release title in smapp releases from Mac to macOS.

Closing due to #751


update dev.isrd to support various test cases

@robes please add the detail related to this issue..

With our revised plan for testing, I don't think this issue is valid anymore. That's my understanding.


MODBULKOPS-20

Purpose

Approach

TODOS and Open Questions

Learning

Pre-Merge Checklist:
Before merging this PR, please go through the following list and take appropriate actions.

Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] Were any API paths or methods changed, added or removed?
[ ] Were there any schema changes?
[ ] Did any of the interface versions change?
[ ] Were permissions changed, added, or removed?
[ ] Are there new interface dependencies?
[ ] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 4
Violation: Property 'bulkOperationRules' not supported in a OAS 3.0 example node
Violation: Property 'totalRecords' not supported in a OAS 3.0 example node
Violation: Property 'header' not supported in a OAS 3.0 example node
Violation: Property 'rows' not supported in a OAS 3.0 example node
--------
validationResult.conforms: true
validationResult.results.length: 6
Warning: should NOT have additional properties
Warning: should NOT have additional properties
should have required property 'header'
should have required property 'rows'

Warning: should NOT have additional properties
Warning: should NOT have additional properties
should have required property 'bulkOperationRules'
should have required property 'totalRecords'

Warning: should NOT have additional properties
Warning: should be boolean
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 4

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'bulkOperationRules' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/bulkOperationRuleCollection
  Property:
  Range: [(2,3)-(16,4)]
  Location: file://./src/main/resources/swagger.api/examples/bulk_operation_rule_collection.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'header' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/unifiedTable
  Property:
  Range: [(2,4)-(128,5)]
  Location: file://./src/main/resources/swagger.api/examples/unified_table.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'totalRecords' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/bulkOperationRuleCollection
  Property:
  Range: [(17,3)-(17,19)]
  Location: file://./src/main/resources/swagger.api/examples/bulk_operation_rule_collection.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'rows' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/unifiedTable
  Property:
  Range: [(129,4)-(217,5)]
  Location: file://./src/main/resources/swagger.api/examples/unified_table.sample

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 6

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
should have required property 'bulkOperationRules'
should have required property 'totalRecords'

  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/expects/request%2FrequestBody/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/expects/request%2FrequestBody/payload/application%2Fjson/examples/example/default-example
  Range: [(69,0)-(70,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
should have required property 'header'
should have required property 'rows'

  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Range: [(116,0)-(117,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(347,0)-(348,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(355,0)-(356,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(363,0)-(364,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 4
Violation: Property 'bulkOperationRules' not supported in a OAS 3.0 example node
Violation: Property 'totalRecords' not supported in a OAS 3.0 example node
Violation: Property 'header' not supported in a OAS 3.0 example node
Violation: Property 'rows' not supported in a OAS 3.0 example node
--------
validationResult.conforms: true
validationResult.results.length: 6
Warning: should NOT have additional properties
Warning: should NOT have additional properties
should have required property 'header'
should have required property 'rows'

Warning: should NOT have additional properties
Warning: should NOT have additional properties
should have required property 'bulkOperationRules'
should have required property 'totalRecords'

Warning: should NOT have additional properties
Warning: should be boolean
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 4

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'bulkOperationRules' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/bulkOperationRuleCollection
  Property:
  Range: [(2,3)-(16,4)]
  Location: file://./src/main/resources/swagger.api/examples/bulk_operation_rule_collection.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'header' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/unifiedTable
  Property:
  Range: [(2,4)-(128,5)]
  Location: file://./src/main/resources/swagger.api/examples/unified_table.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'totalRecords' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/bulkOperationRuleCollection
  Property:
  Range: [(17,3)-(17,19)]
  Location: file://./src/main/resources/swagger.api/examples/bulk_operation_rule_collection.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'rows' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/unifiedTable
  Property:
  Range: [(129,4)-(217,5)]
  Location: file://./src/main/resources/swagger.api/examples/unified_table.sample

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 6

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
should have required property 'bulkOperationRules'
should have required property 'totalRecords'

  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/expects/request%2FrequestBody/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/expects/request%2FrequestBody/payload/application%2Fjson/examples/example/default-example
  Range: [(69,0)-(70,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
should have required property 'header'
should have required property 'rows'

  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Range: [(116,0)-(117,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(347,0)-(348,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(355,0)-(356,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(363,0)-(364,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 4
Violation: Property 'bulkOperationRules' not supported in a OAS 3.0 example node
Violation: Property 'totalRecords' not supported in a OAS 3.0 example node
Violation: Property 'header' not supported in a OAS 3.0 example node
Violation: Property 'rows' not supported in a OAS 3.0 example node
--------
validationResult.conforms: true
validationResult.results.length: 4
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should be boolean
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 4

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'bulkOperationRules' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/bulkOperationRuleCollection
  Property:
  Range: [(2,3)-(16,4)]
  Location: file://./src/main/resources/swagger.api/examples/bulk_operation_rule_collection.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'header' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/unifiedTable
  Property:
  Range: [(2,4)-(128,5)]
  Location: file://./src/main/resources/swagger.api/examples/unified_table.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'totalRecords' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/bulkOperationRuleCollection
  Property:
  Range: [(17,3)-(17,19)]
  Location: file://./src/main/resources/swagger.api/examples/bulk_operation_rule_collection.sample

- Constraint: http://a.ml/vocabularies/amf/parser#closed-shape
  Message: Property 'rows' not supported in a OAS 3.0 example node
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/declares/example/unifiedTable
  Property:
  Range: [(129,4)-(217,5)]
  Location: file://./src/main/resources/swagger.api/examples/unified_table.sample

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 4

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(343,0)-(344,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(351,0)-(352,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fdownload/supportedOperation/get/downloadFileByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(359,0)-(360,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.


[Bug] When creating a DBT model to replace the refreshing of an existing Athena table DBT is deleting historic data in the S3 path

Is this a new bug in dbt-athena?

[X] I believe this is a new bug in dbt-athena
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Text from Slack db-athena:
I'm using Athena and trying to move my historical reports to DBT, but I've hit a snag. My current config is using incremental materialization with insert_overwrite strategy, partitioned by day and hour, and pointing to an external S3 location.
The problem is it's deleting past data in S3. I want to keep the table's history intact while moving to DBT for incremental updates. Also, some reports get updated at the end of the day for earlier hours within the same day.
I'm aiming to:
Keep existing historical data in S3
Use DBT for new incremental updates
Only affect the intended day and hour partitions in each run

and
A bit of discovery on my end: If a table doesn't exist  dbt.adapters.athena.constants adapter: Deleting table data: path= shows up in the logs, clearing out the existing S3 data.
If the table does exist, it will produce the desired increment update in the location I wanted.

Expected Behavior

Keep existing historical data in S3
Use DBT for new incremental updates
Only affect the intended day and hour partitions in each run

Steps To Reproduce
Model Config:
{{ config(
    materialized='incremental',
    incremental_strategy='insert_overwrite',
    format='parquet',
    partitioned_by=['day', 'hour'],
    external_location='s3://bucket/key/existing-data'
) }}

run the model and observe the data in external_location
Examine the log files
[Thread-1 (]: dbt.adapters.athena.constants adapter: Deleting table data: path='s3://bucket/key/existing-data', bucket='bucket', prefix='key/existing-data/'

Environment
- OS: 14.3.1 and also in AWS MWAA
- Python: 3.11
- dbt: 1.8.1
- dbt-athena-community: 1.8.1

Additional Context
Anders pointed me to creating a bug ticket for this on Slack. I think I covered it pretty well, but please contact me if there is any additional needed information. Thanks!

It's hard to reproduce the issue if you don't post the SQL code used in your transformation.
insert_overwrite works as intended, and it's covered by functional tests that verify that the behvior is correct.
I believe that issue that you are facing is due to how you refresh the data incrementally in your model. Therefore please post your full model SQL in order for us to help you to fix the issue properly.
Also, as a possible hint, it looks to me that you might benefit from an iceberg table, and not a classic hive table for what you want to achieve.

I recommend to have a look here https://docs.getdbt.com/docs/build/incremental-models
In your model you need to add this conditional if
{% if is_incremental() %}

where event_date >= current_date - interval '1' day

{% endif %}

doing so in your first run, all the data is processed, but in the 2nd run only "the partitions" produced by your where condition will be overwritten by the model doing so you can achieve what you state as Only affect the intended day and hour partitions in each run

Based on the discussion that happened in Slack, looks like the issue is because of an attempt to modify a table created outside dbt.
Seems like that due to a mismatch on the schema (most probably due to the generate_schema_macro), dbt doesn't find the existing table, and therefore it deletes the data in the specified location, to then re-create the table.
I believe that this is not a bug itself but mostly an issue of the user configuration.


Add Duration support

It would be great to allow custom java.time.Duration formatting that can produce:

02:30
01:02:30
2h3m
1d2h3m
2 hours and 3 minutes
1 hour and 3 minutes
1 day and 5 hours
1 day, 5 hours and 1 minute

Possible solutions:

Allow to extract specific part of the duration just by including default decomposition rules (e.g. hours {duration.hours} {hour,hours#duration.hours}) - easy solution, but this alone does not allow dynamic range and would result in things like "0 days, 4 hours, 1 minute".  Good start anyway - would integrate okay with current pluralization. A bit long to write. Can even support leading zeros using the number formatting feature. Very flexible with the formatting and the different approaches languages can have for such constructs.

Added in https://github.com/OkaeriPoland/okaeri-placeholders/commit/3827585f35789a1e3aa05097243a95b9b1c3e119

Expected
Pattern
Note

02:30
{%02.0f#duration.hours}:{%02.0f#duration.minutes}
use f with zero decimal places as number formating in okaeri-placeholders converts to double

01:02:30
{%02.0f#duration.days}:{%02.0f#duration.hours}:{%02.0f#duration.minutes}
use f with zero decimal places as number formating in okaeri-placeholders converts to double

2h3m, 1d2h3m
{duration} or {duration(m)}
1st param = precision, s by default

2 hours and 3 minutes, also 1 hour and 3 minutes
{duration.hours} {hour,hours#duration.hours} and {duration.minutes} {minute,minutes#duration.minutes}
-

1 day and 5 hours
{duration.days} {day,days#duration.days} and {duration.hours} {hour,hours#duration.hours}
-

1 day, 5 hours and 1 minute
{duration.days} {day,days#duration.days}, {duration.hours} {hour,hours#duration.hours} and {duration.minutes} {minute,minutes#duration.minutes}
-


Feature Request: Adding Neurons balance to Ledger Live

Hello!
I am reaching out to the team to request consider adding the locked ICP balance to the ledger live application.
Something similar to what is available in the Multiversx app, indicating the locked EGLD balance, would be a good UX improvement, as it would be easier to track portfolios for ICP users.
So for instance, its readily available in the NNS [Network Nervous System]as in the image below👇

I look forward to hearing the team's thoughts on this.
Best,
Ishaaq

Hi @ishaaqziyan ,
We are working on this already. And more. We also want to enable users to stake directly from Ledger Live application and manage their neurons.

Hello @lmuntaner
Thank you for the prompt response.
Looking forward to seeing what you guys are cooking for the IC.
I will now go ahead and close this issue.
Best,
Ishaaq


Input and a Wrapper customizing

Thank you for the library!
I want to customize the ColorPicker component with svelte MUI. But trying to wrap with SMUI components (in my case it's MenuBar) doesn't work. The color picker doesn't open. I also get an error Uncaught TypeError: wrapper.contains is not a function when I click on the color picker and then somewhere out of its ColorPicker container (it seems to me it changes isOpen but isn't shown on the screen thus the logic breaks down). Thus, I'd like to know if wrapping ColorPicker with components from other libraries is possible.
By the way, moving away from this approach. What is the best way to change the styling to the one I need? Is that via overwriting CSS rules or via wrapping items but with a plain div with styles?
Thank you in advance!

I haven't tested integration with a component library, but the library has been designed to be customizable.  It can be achieved by applying :global styles, overridden components or css variables.
Can you please make a reproduction repository with the problem you're having (Uncaught TypeError: wrapper.contains is not a function)?

Hi! Sorry for the late response. Thanks a lot for striving to help!
The error happens on the smui's side. Didn't notice it at first. Anyway, here's the link in case you want to have a look:
https://github.com/KlashReik/color-picker-smui

Hi!
Thanks for sharing the link.
Did you solve your issue?
Don't hesitate to pin this issue in any issue you may open in the smui repository as it may helps someone else facing the same issue.

Hi! I've copied SMUI styles to a div and added it as a wrapper, but I couldn't wrap it with the SMUI Menu component.
Wrapping the slot with List helped to get rid of the error, but the menu appears and disappears after clicking on the change color. Not sure why this exactly works so. But when I tried to bind the state of the menu and color picker, I saw that the menu changed its open state and that's the reason why it "flashes on the screen". Unfortunately, I couldn't find a way to fix it. (Hope this info will help someone in the future)


updating link in readme to gh repo

Tiny, (tiny) update to README to update the "how to use this" instructions with the correct link to this repo.
Also, updated references in the License portion of the README

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


[Bug Report] Installation of pyRTE+RRTMGP fails tests

Describe the bug
I am attempting to install pyRTE+RRTMGMP.   When I follow the build instructions on the readme for installation via conda, I get this error, when I run
conda build conda.recipe
=================================== FAILURES ===================================
________________________________ test_lw_solver ________________________________

request = <FixtureRequest for <Function test_lw_solver>>

    def test_lw_solver(request):
        path = os.path.dirname(request.path)
        with open(f'{path}/lw_solver_input.json', 'r') as f:
            data = json.load(f)

        for key in data:
            values = data[key]
            if isinstance(values, list):
                values = np.array(values)
                data[key] = values

        args = list(data.values())

        py.rte_lw_solver_noscat(*args)

        test_data = np.load(f"{path}/lw_solver_output.npy")

>       assert(np.allclose(test_data - data['broadband_up'], 0.))
E       assert False
E        +  where False = <function allclose at 0x7fc2724e6fb0>((array([345.43212164,<PHONE_NUMBER>5,  40.22612771,   8.80242324,\n<PHONE_NUMBER>2,<PHONE_NUMBER> ,  56.30870811,  12.32...374.10298773,<PHONE_NUMBER>3,<PHONE_NUMBER>3,<PHONE_NUMBER>3,\n<PHONE_NUMBER>8,<PHONE_NUMBER>8,<PHONE_NUMBER>8,<PHONE_NUMBER>8]) - array([172.71606082,<PHONE_NUMBER>7,  20.11306386,   4.40121162,\n<PHONE_NUMBER>1,<PHONE_NUMBER> ,  28.15435405,   6.16...187.05149387,<PHONE_NUMBER>7,<PHONE_NUMBER>7,<PHONE_NUMBER>7,\n<PHONE_NUMBER>9,<PHONE_NUMBER>9,<PHONE_NUMBER>9,<PHONE_NUMBER>9])), 0.0)
E        +    where <function allclose at 0x7fc2724e6fb0> = np.allclose

tests/lw_solver_test/noscat_test/lw_solver_noscat_test.py:24: AssertionError
____________________________ test_lw_solver_noscat _____________________________

    def test_lw_solver_noscat():
        rrtmgp_gas_optics = kdist.gas_optics.load_atmosferic_conditions(rfmip)

        _, solver_flux_up, solver_flux_down, _, _ = lw_solver_noscat(
            tau=rrtmgp_gas_optics.tau,
            lay_source=rrtmgp_gas_optics.lay_src,
            lev_source=rrtmgp_gas_optics.lev_src,
            sfc_emis=rfmip["surface_emissivity"].data,
            sfc_src=rrtmgp_gas_optics.sfc_src,
            sfc_src_jac=rrtmgp_gas_optics.sfc_src_jac,
        )

>       assert np.isclose(solver_flux_up, ref_flux_up, atol=ERROR_TOLERANCE).all()
E       assert np.False_
E        +  where np.False_ = <built-in method all of numpy.ndarray object at 0x7fc2581774b0>()
E        +    where <built-in method all of numpy.ndarray object at 0x7fc2581774b0> = array([[False, False, False, ..., False, False, False],\n       [False, False, False, ..., False, False, False],\n      ...alse],\n       [False, False, False, ..., False, False, False],\n       [False, False, False, ..., False, False, False]]).all
E        +      where array([[False, False, False, ..., False, False, False],\n       [False, False, False, ..., False, False, False],\n      ...alse],\n       [False, False, False, ..., False, False, False],\n       [False, False, False, ..., False, False, False]]) = <function isclose at 0x7fc2724eb130>(array([[144.78141419,<PHONE_NUMBER> ,<PHONE_NUMBER>8, ...,<PHONE_NUMBER>2,\n<PHONE_NUMBER>2,<PHONE_NUMBER>9],\n       [150....3.2440728 ],\n       [143.73562813,<PHONE_NUMBER>5,<PHONE_NUMBER>2, ..., 217.92762   ,\n<PHONE_NUMBER>3,<PHONE_NUMBER>3]]), array([[289.56284, 289.63196, 289.696  , ..., 456.19498, 461.8384 ,\n        478.21   ],\n       [300.46246, 300.51285, ...    446.48816],\n       [287.47125, 287.55185, 287.61502, ..., 435.85526, 437.16132,\n        439.44656]], dtype=float32), atol=0.0001)
E        +        where <function isclose at 0x7fc2724eb130> = np.isclose

tests/test_python_frontend/test_lw_solver.py:43: AssertionError
=========================== short test summary info ============================
FAILED tests/lw_solver_test/noscat_test/lw_solver_noscat_test.py::test_lw_solver
FAILED tests/test_python_frontend/test_lw_solver.py::test_lw_solver_noscat - ...
======================== 2 failed, 54 passed in 15.09s =========================
Tests failed for pyrte_rrtmgp-0.0.6-py39h3fd9d12_0.tar.bz2 - moving package to /global/homes/a/amahesh/conda-bld/broken
WARNING:conda_build.build:Tests failed for pyrte_rrtmgp-0.0.6-py39h3fd9d12_0.tar.bz2 - moving package to /global/homes/a/amahesh/conda-bld/broken
TESTS FAILED: pyrte_rrtmgp-0.0.6-py39h3fd9d12_0.tar.bz2

To Reproduce
I ran git clone git@github.com:earth-system-radiation/pyRTE-RRTMGP.git
cd pyRTE-RRTMPG/
conda install conda-build conda-verify
conda build conda.recipe
Expected behavior
I'd expect the build tests to succeed so that I can use the package in conda
Software Versions:

OS: Linux on NERSC Perlmutter: AMD EPYC 7763 (which is based on x86-64 I think)
Version (or most recent commit hash) of RTE+RRTMGP: 1f9205c635197199a56c1fda933e6ebf616ed546
Also, I get this same failure when I try to build locally, on a Mac with Apple Silicon (which I know is not officially supported, according to the README).  The macOS is Sonoma 14.4.  (Note on the Mac with apple silicon I had to change gfortran_osx-64 in the conda.recipe/meta.yaml to gfortran_impl_osx-arm64)

Also, I get this same failure when I try to build locally, on a Mac with Apple Silicon.  The macOS is Sonoma 14.4.  (Note on the Mac with apple silicon I had to change gfortran_osx-64 in the conda.recipe/meta.yaml to gfortran_impl_osx-arm64)

After searching the Github repo, I also came across this pull request: https://github.com/earth-system-radiation/pyRTE-RRTMGP/pull/52.  I tried cloning into this branch.  I had to change the tests/test_python_frontend/test_sw_solver.py to use the rsu and rsd files from rrtgmp-data, just as was done for test_lw_solver.py in the github repository..  However, this still leads to errors with passing the test cases:
________________________________ test_lw_solver ________________________________

request = <FixtureRequest for <Function test_lw_solver>>

    def test_lw_solver(request):
        path = os.path.dirname(request.path)
        with open(f'{path}/lw_solver_input.json', 'r') as f:
            data = json.load(f)

        for key in data:
            values = data[key]
            if isinstance(values, list):
                values = np.array(values)
                data[key] = values

        args = list(data.values())

        py.rte_lw_solver_noscat(*args)

        test_data = np.load(f"{path}/lw_solver_output.npy")

>       assert(np.allclose(test_data - data['broadband_up'], 0.))
E       assert False
E        +  where False = <function allclose at 0x10229ccb0>((array([345.43212164,<PHONE_NUMBER>5,  40.22612771,   8.80242324,\n<PHONE_NUMBER>2,<PHONE_NUMBER> ,  56.30870811,  12.32...374.10298773,<PHONE_NUMBER>3,<PHONE_NUMBER>3,<PHONE_NUMBER>3,\n<PHONE_NUMBER>8,<PHONE_NUMBER>8,<PHONE_NUMBER>8,<PHONE_NUMBER>8]) - array([172.71606082,<PHONE_NUMBER>7,  20.11306386,   4.40121162,\n<PHONE_NUMBER>1,<PHONE_NUMBER> ,  28.15435405,   6.16...187.05149387,<PHONE_NUMBER>7,<PHONE_NUMBER>7,<PHONE_NUMBER>7,\n<PHONE_NUMBER>9,<PHONE_NUMBER>9,<PHONE_NUMBER>9,<PHONE_NUMBER>9])), 0.0)
E        +    where <function allclose at 0x10229ccb0> = np.allclose

tests/lw_solver_test/noscat_test/lw_solver_noscat_test.py:24: AssertionError
____________________________ test_lw_solver_noscat _____________________________

    def test_lw_solver_noscat():
        rrtmgp_gas_optics = kdist.gas_optics.load_atmosferic_conditions(rfmip)

        _, solver_flux_up, solver_flux_down, _, _ = lw_solver_noscat(
            tau=rrtmgp_gas_optics.tau,
            lay_source=rrtmgp_gas_optics.lay_src,
            lev_source=rrtmgp_gas_optics.lev_src,
            sfc_emis=rfmip["surface_emissivity"].data,
            sfc_src=rrtmgp_gas_optics.sfc_src,
            sfc_src_jac=rrtmgp_gas_optics.sfc_src_jac,
        )

>       assert np.isclose(solver_flux_up, ref_flux_up, atol=ERROR_TOLERANCE).all()
E       assert False
E        +  where False = <built-in method all of numpy.ndarray object at 0x16e27fb10>()
E        +    where <built-in method all of numpy.ndarray object at 0x16e27fb10> = array([[False, False, False, ..., False, False, False],\n       [False, False, False, ..., False, False, False],\n      ...alse],\n       [False, False, False, ...,  True,  True, False],\n       [False, False, False, ...,  True,  True, False]]).all
E        +      where array([[False, False, False, ..., False, False, False],\n       [False, False, False, ..., False, False, False],\n      ...alse],\n       [False, False, False, ...,  True,  True, False],\n       [False, False, False, ...,  True,  True, False]]) = <function isclose at 0x10229e1b0>(array([[289.95776422,<PHONE_NUMBER>1,<PHONE_NUMBER>4, ...,<PHONE_NUMBER>7,\n<PHONE_NUMBER>6,<PHONE_NUMBER> ],\n       [300....6.47711207],\n       [287.8319806 ,<PHONE_NUMBER>5,<PHONE_NUMBER>8, ...,<PHONE_NUMBER>4,\n<PHONE_NUMBER>5,<PHONE_NUMBER>3]]), array([[289.56674, 289.63577, 289.69986, ..., 456.19098, 461.83554,\n        478.21   ],\n       [300.46246, 300.51276, ...    446.48813],\n       [287.47003, 287.55054, 287.6137 , ..., 435.85275, 437.15918,\n        439.44656]], dtype=float32), atol=0.0001)
E        +        where <function isclose at 0x10229e1b0> = np.isclose

tests/test_python_frontend/test_lw_solver.py:44: AssertionError

The second test can be passed by changing this to 1.8.1, to reflect the updated files in the rrtmpg-data github repository.  I will submit a PR with this change.
However, the first test, where the results appear to be off by a factor of 2, is still not fixed.

@ankurmahesh Thank you for filing this bug report! Things have been a bit slower than usual over the past weeks, but we are planning to get back to this soon!

They were fixed, but found that there is an inconsistency in the results of the LW problem in Apple Silicon.

The new implementation of the frontend also solves this issue and should be merge in the next weeks


Add support for metadata component

Part of #6
Signed-off-by: Artem Smotrakov<EMAIL_ADDRESS>

Thanks for the PR @artem-smotrakov. We're in the process of a notable update at present to support the forthcoming CycloneDX 1.4 schema - so please forgive us if we wait for that work to stabilise before we look at merging your PR.
Cheers!

Thanks for the PR @artem-smotrakov. We're in the process of a notable update at present to support the forthcoming CycloneDX 1.4 schema - so please forgive us if we wait for that work to stabilise before we look at merging your PR.
Cheers!

enabled CI to run CT/QA.
@artem-smotrakov could you check that all tests pass?
see https://github.com/CycloneDX/cyclonedx-python-lib/blob/main/CONTRIBUTING.md for more.

Hmm, I read the contributing guidelines and ran tests and poetry run autopep8 --in-place -r . before opening the PR. They passed. Let me check again.

I've fixed several formatting and typing issues. poetry run tox passed. Please re-run the CI/CD jobs.

Hi @artem-smotrakov - we've just merged changes for CycloneDX 1.4 - are you willing to rebase this branch from main?
Thanks, Paul

@madpah I've rebased it -- please rerun CI/CD and have a look at the updates.
I am not sure about this one:
https://github.com/CycloneDX/cyclonedx-python-lib/pull/118/files#diff-9c84a99c5332704dd6a90a4defadfd9df437336f07b79b91033e0a96bbd8fbf1R95
I've noticed that if a BOM doesn't have components, _specialise_output_for_schema_version() fails with a key error. I've updated it to always add components element. That is how XML encoder behaves.

@madpah I've addressed your comments -- thanks for the review!


tidy HTML

Tidy HTML by adding indentations.

looks ok to me. Nice job

@danieldelacruz01  thanks all fixed!

Hey @oliver-jk-redding is there any chance you could add me as a collaborator so I can accept your changes?


Prompts inconsistently require pressing 'Enter'

🔑
New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Some prompts require you to enter input and then press 'Enter', and others just require you to enter 'y' or 'n' and will continue without you pressing 'Enter'. This caused me some confusion when running fastlane init today because it was the first time using fastlane on this machine, so I needed to go through the full setup process. I had to enter my Apple ID (type it and press 'Enter'), then select my iTunes Connect team (enter the team number and press 'Enter'), but when it detected that the app did not exist in the Developer Portal or iTunes Connect, it asked me whether I wanted to create them. I typed 'y' and pressed 'Enter', but it kept failing because it would read that 'Enter' as my response to the prompt for the App Name. So, it would keep trying to create an app with an empty name.
I think it'd probably be more consistent to require an 'Enter' after all prompts.
Complete output when running fastlane, including the stack trace and command used

MacBook-Pro-2:ios justin$ fastlane init
...output
[14:35:49]: Checking if the app 'com.xxxxxx.xxxxxx' exists in your Apple Developer Portal...
[14:35:50]: It looks like the app 'com.xxxxxx.xxxxxx' isn't available on the Apple Developer Portal
[14:35:50]: for the team ID 'xxxxxx' on Apple ID<EMAIL_ADDRESS>[14:35:50]: Do you want fastlane to create the App ID for you on the Apple Developer Portal? (y/n)
y
+----------------+--------------------------+
|        Summary for produce 2.93.1         |
+----------------+--------------------------+
| username       |<EMAIL_ADDRESS>      |
| team_id        | xxxxxx               |
| itc_team_id    | xxxxxx                   |
| platform       | ios                      |
| app_identifier | com.xxxxxx.xxxxxx |
| skip_itc       | true                     |
| sku            | xxxxxx               |
| language       | English                  |
| skip_devcenter | false                    |
+----------------+--------------------------+
[14:35:55]: App Name: [14:35:55]: Creating new app '' on the Apple Dev Center
[14:35:56]: ["Apple provided the following error info:", "There were errors in the data supplied. Please correct and re-submit.", "No value was provided for the parameter 'appIdName'."]
[14:35:56]: It looks like something went wrong when we tried to create your app on the Apple Developer Portal
[14:35:56]: Would you like to try again (y)? If you enter (n), fastlane will fall back to the manual setup (y/n)
...output

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.4

Ruby
2.2.4

Bundler?
false

Git
git version 2.14.1

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.13.4 (17E199)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Push a new beta build to TestFlight"
  lane :beta do
    increment_build_number(xcodeproj: "xxxxxx.xcodeproj")
    build_app(scheme: "xxxxxx")
    upload_to_testflight
  end
end

`./fastlane/Appfile`
app_identifier("BUNDLE_ID") # The bundle identifier of your app
apple_id("APPLE_ID") # Your Apple email address

itc_team_id("ITC_TEAM_ID") # iTunes Connect Team ID
team_id("DEV_TEAM_ID") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.93.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.2

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.5

xcodeproj
1.5.7

rouge
1.11.1

xcpretty
0.2.6

unicode-display_width
1.1.3

terminal-table
1.7.3

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

commander-fastlane
4.4.6

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

gh_inspector
1.1.3

json
1.8.1

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

naturally
2.1.0

simctl
1.6.4

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

logging
2.2.2

jwt
1.5.6

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.13.6

emoji_regex
0.1.1

highline
1.7.10

excon
0.62.0

CFPropertyList
3.0.0

libxml-ruby
3.0.0

plist
3.4.0

fastimage
2.1.1

generated on: 2018-04-30

@diakonos Heyyy 👋 Thanks for feedback! I can totally see where you are coming from here. We definitely like to have things consistent and fastlane can have a lot of user interaction and we like to make it as easy to use for everyone 😊
TBH, at first I was gunna be like "I think things are fine" but the more I thought about it the more I think this has actually happened to me 🤔
The fix would be to remove the true parameter on this line - https://github.com/fastlane/fastlane/blob/master/fastlane_core/lib/fastlane_core/ui/implementations/shell.rb#L134
I'm a bit hesitant to make this change (even though easy) as this changes a lot of behavior (since a lot of tools use this) for a lot of people. It definitely isn't a change that could "break" things but it does offer a different user experience. Imma let this one simmer in my mind for a bit 💭

Totally understand the concern! It's actually somewhat odd, because I've used fastlane on and off for years and don't remember noticing this. I don't think I've ever gone through this exact scenario where I was setting up fastlane before the app had been created in iTunes Connect yet, but I imagine I must've run across the y/n questions at some point. Pressing 'Enter' afterwards doesn't always have this effect though, depending on if there is another prompt and what it is.
I can definitely see this going both ways, since I guess there is a small speed / convenience benefit for y/n questions if you don't have to press 'Enter', as well as not wanting to impact everyone.
Thanks for taking the time to consider the suggestion!


Day 292

Good morning! Here's your coding interview problem for today.
This problem was asked by Twitter.
A teacher must divide a class of students into two teams to play dodgeball. Unfortunately, not all the kids get along, and several refuse to be put on the same team as that of their enemies.
Given an adjacency list of students and their enemies, write an algorithm that finds a satisfactory pair of teams, or returns False if none exists.
For example, given the following enemy graph you should return the teams {0, 1, 4, 5} and {2, 3}.
students = {
    0: [3],
    1: [2],
    2: [1, 4],
    3: [0, 4, 5],
    4: [2, 3],
    5: [3]
}

On the other hand, given the input below, you should return False.
students = {
    0: [3],
    1: [2],
    2: [1, 3, 4],
    3: [0, 2, 4, 5],
    4: [2, 3],
    5: [3]
}

My solution requires a connected graph. Otherwise, a deterministic answer isn't possible.
Take for example the following test case:
map[int]map[int]struct{}{
			0: {1: struct{}{}},
			1: {0: struct{}{}},
			3: {4: struct{}{}},
			4: {3: struct{}{}},
		},

There are 2 valid solutions: team1: [0, 3] team2: [1, 4] OR team1: [0, 4] team2: [1, 3] when deterministically sorting by the first ID. team1[0] < team2[0]


Question about Async Api

So with SQLiteAsyncConnection, it does not implement IDisposable. Therefore, do we instantiate this object once only?
Then call .CloseAsync when done? I'm trying to go for a multi threaded approach but I'm a little bit confused on how it works. If I created a new instance every time and then close the connection on query/insert done, would it wait for all other jobs to finish before closing or will it kick them out?
Also does async need to worry about the multithreaded inserts or is it all handled in the background? The official documentation on github doesn't really explain much but I'd assume it does if it uses the thread pool queue.

SQLiteAsyncConnection is not an actual connection. it is just a "coordinator" that maintains a Dictionary<connectionstring,sqliteconnection> global dictionary.
you can have ten threads/tasks that try to open the same database file via SQLiteAsyncConnection, but actually SQLiteAsyncConnection will create just one single plain SQLiteConnection (not async) and give access to this single connection to just one thread/task at a time.
The main job of SQLiteAsyncConnection is to just coordinate the access of multiple tasks to the same underlying SQLiteConnection, and to serialize transactions: just one task at a time can gain access to the underlying connection and write data, and it must conclude its transaction (by committing or rollbacking) before another task gets access to the same connection.


Is it able to detach this repo from original truthcoin-cpp ?

I have tried to search src of this repo but according to current Github specification, It's not possible until it becomes standalone repo.
Is it OK to detach it?

You'd be much better off using grep and reading the hivemind docs in the
docs folder honestly.
Since we are a fork of bitcoin, and I'll be rebasing / updating the
hivemind source on top of upstream bitcoin I don't know if we should detach
the repo. Maybe we should all get together and discuss this on slack some
time soon?
On Mar 29, 2017 5:52 PM, "Joe Miyamoto"<EMAIL_ADDRESS>wrote:
I have tried to search src of this repo but according to current Github
specification, It's not possible until it becomes standalone repo.
Is it OK to detach it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bitcoin-hivemind/hivemind/issues/86, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHu1Nt3BrB3zZ1KThgrYzrmOWf7WCp-Xks5rqvzTgaJpZM4Mtu_6
.

I got It. Thanks!

Also, if you're trying to find something in parricular or anything is
confusing you can ask me on slack or email (add at g mail dot com to my
github name).
Here's one of the more useful files in the docs folder I mentioned:
https://github.com/bitcoin-hivemind/hivemind/blob/master/doc/notes_hivemind.txt
On Mar 29, 2017 11:00 PM, "Joe Miyamoto"<EMAIL_ADDRESS>wrote:

Closed #86 https://github.com/bitcoin-hivemind/hivemind/issues/86.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bitcoin-hivemind/hivemind/issues/86#event-1021682345,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHu1Nvtk18ikh8qbBWa2KSbUyQMDRMjvks5rq0IYgaJpZM4Mtu_6
.

Thanks! I'd better take time to understand Automated Market Maker more thoroughly.


Problem with input validation attribute binding (minlength, maxlength and pattern)

I'm submitting a bug report

Library Version:
1.0.1

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
5.1.0

NPM Version:
3.5.0

JSPM OR Webpack AND Version
none, I'm using AureliaCLI

Browser:
Chrome 51

Language:
TypeScript 1.9

Current behavior:
pattern attribute binding not work fine. If value is undefined aurelia sets pattern="undefined" and input is always invalid.
minlength and maxlength attribute binding sets 0 if binding source is null or undefiend.
Expected/desired behavior:
You can see a demo here: http://plnkr.co/edit/pLIM83?p=preview

What is the expected behavior?
If source of pattern binding is undefined, aurelia shouldn't set pattern attribute, like required.
The same for minlength and maxlength.

What is the motivation / use case for changing the behavior?
You can build custom inputs elements and enable to set or not validations attributes.

Issue moved to aurelia/validatejs #115 via ZenHub

I think it isn't related with validations, I don't use validatejs ...
I thought it was related with the binding or template-binding but never with validatejs.
Ok, thanks anyway.


Leetcode Question Number 2

Leetcode Question Number 2 soultion needs to be added in the repo .
The link for the question is this.
Accepted Languages C++ / JAVA .
You Only need to add the  class Solution in the file.
Make Sure you have read the contributions guidelines before creating an PR.

I want to contribute this solution, please assign me.


Update assembly loader

Related to issue #750.
We need the ability to load task-containing assemblies from arbitrary
locations on disk determined at run time, along with thei dependencies.
It is assumed that their dependencies will be located next to them in
the file system, or in some well-known location.
Ideally we would handle the dependencies by hooking the Resolving
event on the default AssemblyLoadContext. However, due to
https://github.com/dotnet/coreclr/issues/5837 we can't currently do
this. Instead, we need to implement our own AssemblyLoadContext.
This is what we currently do. However, we run into a problem when a task
assembly depends on, say, Microsoft.Build.dll (which is pretty much
guaranteed). Microsoft.Build will already be loaded into the default
AssemblyLoadContext, but since our task assembly was loaded into our
context, we are likely to be asked to load it again when the task needs
it. We currently handle this by looking for it in the app's base
directory, which seems like a good bet.
So we may end up loading this assembly twice, in two different
contexts--not great, but everything still works. Issue #750 comes into
play when Microsoft.Build.dll has been CrossGen'd to a native assembly.
Both contexts will find and try to load the native assembly--and this is
currently not allowed.
So to work around these other issues in assembly loading, we need to
maintain our own AssemblyLoadContext for the time being. However, we
now ask the default AssemblyLoadContext to first try satisfying the
load. If it succeeds, the load will occur in that context. Only if it
can't find the assembly in question do we attempt to find and load the
assembly ourselves (putting it in our context).

@AndyGerlicher @cdmihai @rainersigwald @jeffkl Could you please take a look?
I haven't yet verified that this actually fixes #750--I'm still figuring out how to generate the proper native images. However, if this doesn't work then we're out of options for working around the bugs in the runtime. :-)

:shipit:

@dotnet-bot test OSX Build for CoreCLR please

LGTM


Undefined error when invoking OAuthManager constructor with app name

Going through the example, the following code throws the error: undefined is not a constructor(evaluating 'new _reactNativeOauth.OAuthManager:
import { OAuthManager } from 'react-native-oauth';
const manager = new OAuthManager('RedFish')
manager.configure({
  facebook:{
    client_id: 'MY_ID',
    client_secret: 'MY_SECRET'
  }
});

Stack trace - apologies for the poor format. Couldn't copy/paste:

My issue was that the import line should read import OAuthManager from 'react-native-oauth'; I'm new to react; apparently the braces make all the difference. Apologies!

@msciotti Thanks, your solution really helped


[Proposal] Move interfaces to Storage.Net.Abstractions

Move interfaces IBlobStorage, IKeyValueStorage, IMessagePublisher, IMessageReceiver and deps to the Storage.Net.Abstractions package
Storage.Net.Abstractions has no dependencies to other libs

Tasks:

[ ] Change namespace of interfaces and classes in the new project to "Storage.Net.Abstractions"

Closes #85

So doing this is out of question?


Migrate upgrade script to package and update logic

The logic of the scritp was updated to account for the fact that PiWeatherRock will now be installed via pip3 instead of via a git clone. The readme was also updated as part of this packaging work

@metaMMA If you have time to look at the modifications to the upgrade script I would appreciate your thoughts.


Versions for dnspy, map, SysAnalyzer and 010Editor needs to be fixed

Versions for dnspy, map, SysAnalyzer and 010Editor needs to be fixed
dnspy
010Editor
map
SysAnalyzer

We've pushed a new update addressing these broken packages, please let use know if you encounter additional broken packages going forward


StoreRouterConnectingModule --> Outlet is not Activated

Hi, I'm encountering a weird issue that I was hoping I could get some help with.
Without adding the Connecting module, my app works fine. The second I add it, I get the "Outlet is not activated" error along with a large error stack.
My application is lazily loading a feature module, complete with feature state as well. It's internal so I can't share it, trying to provide as many details as possible.

StoreModule.forRoot(appReducer,

{
initialState : { app: appInitialState },
metaReducers : !environment.production ? [storeFreeze] : []
}),
EffectsModule.forRoot([]),
!environment.production ? StoreDevtoolsModule.instrument() : [],
StoreRouterConnectingModule

The outlet is not activated error is thrown from store devtools


This is not an issue, just a question sir.

Is there a way to highlight specific segment when viewDidLoad? Like a default segment is highlighted or just the first one.
Thank you so much sir!

My bad.
—————
Problem resolved by using
segmentedControl.selectedSegmentIndexl = 0


Donate to CNCF

Description
What problem are you trying to solve?
As one of the top 5 Kubernetes autoscaler of the market, being a project in the CNCf will incentive other providers to adopt this awesome product. More provider, means more devs contributing to it and more features for the users. Big quick-win.
How important is this feature to you?
Being in the CNCF provides more guarantees that it will be maintained in time and also compatibility with other providers in case our companies decide to change it.

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

See: https://github.com/kubernetes/org/issues/4258. This was done for the upstream library (kubernetes-sigs/karpenter). There's no current plans to donate the specific providers since they are CloudProvider-specific implementations and can be owned by the CloudProvider.
Are you interested in the upstream repo or the CloudProvider repo being donated?

Thanks for the answer and sorry for the misunderstanding. I did not know that the core was donated. Great job done


@set problem

The example from the doc fails
julia> using OhMyThreads: @set, @tasks, @init

julia> using OhMyThreads.Tools: taskid

julia> @tasks for i in 1:10
           @set scheduler=DynamicScheduler(; nchunks=2)
           @init x::Vector{Float64} = zeros(3) # TLV

           x .+= 1
           println(taskid(), " -> ", x)
       end
ERROR: UndefVarError: `DynamicScheduler` not defined
Stacktrace:
 [1] macro expansion
   @ ~/.julia/packages/OhMyThreads/N9muZ/src/macro_impl.jl:45 [inlined]
 [2] top-level scope
   @ REPL[6]:1

using OhMyThreads: DynamicScheduler
Where is this in the docs?
Minor comment: Note that technically you don't need to load @set and @init. They're fake macros :)

Ah it's in the docstring. There I kind of assumed using OhMyThreads but we should probably clarify this.

Fixed. Thanks for the issue.

Thanks, Here is another one. Was it fixed too? Setting ntasks is something I need.
julia> function mc_parallel_macro(N; ntasks=nthreads())
           M = @tasks for i in 1:N
               @set begin
                   reducer=+
                   ntasks=ntasks
               end
               rand()^2 + rand()^2 < 1.0
           end
           pi = 4 * M / N
           return pi
       end
ERROR: LoadError: ArgumentError: Unknown setting "ntasks". Must be ∈ (:scheduler, :reducer, :collect).
Stacktrace:
  [1] _handle_set_single_assign!(settings::OhMyThreads.Implementation.Settings, ex::Expr)
    @ OhMyThreads.Implementation ~/.julia/packages/OhMyThreads/N9muZ/src/macro_impl.jl:159
  [2] _broadcast_getindex_evalf
    @ ./broadcast.jl:709 [inlined]
  [3] _broadcast_getindex
    @ ./broadcast.jl:682 [inlined]
  [4] getindex
    @ ./broadcast.jl:636 [inlined]
  [5] copyto_nonleaf!(dest::Vector{…}, bc::Base.Broadcast.Broadcasted{…}, iter::Base.OneTo{…}, state::Int64, count::Int64)
    @ Base.Broadcast ./broadcast.jl:1098
  [6] copy
    @ ./broadcast.jl:950 [inlined]
  [7] materialize(bc::Base.Broadcast.Broadcasted{…})
    @ Base.Broadcast ./broadcast.jl:903
  [8] _maybe_handle_set_block!(settings::OhMyThreads.Implementation.Settings, args::Vector{Any})
    @ OhMyThreads.Implementation ~/.julia/packages/OhMyThreads/N9muZ/src/macro_impl.jl:141
  [9] tasks_macro(forex::Expr)
    @ OhMyThreads.Implementation ~/.julia/packages/OhMyThreads/N9muZ/src/macro_impl.jl:21
 [10] var"@tasks"(__source__::LineNumberNode, __module__::Module, args::Vararg{Any})
    @ OhMyThreads ~/.julia/packages/OhMyThreads/N9muZ/src/macros.jl:53
in expression starting at REPL[3]:2
Some type information was truncated. Use `show(err)` to see complete types.

IIRC, ntasks has only been added very recently and will only arrive with v0.5 (in the next couple of days). That is to say, you are probably on a stable version which doesn't know ntasks for the dynamic scheduler yet.
That said, note that for the dynamic scheduler (default), ntasks is just an alias for nchunks. As a workaround, you can therefore use
function mc_parallel_macro(N; ntasks=nthreads())
    M = @tasks for i in 1:N
        @set begin
            reducer = +
            scheduler=DynamicScheduler(; nchunks=ntasks)
        end
        rand()^2 + rand()^2 < 1.0
    end
    pi = 4 * M / N
    return pi
end

FYI: I've just triggered the v0.5 release. Should be in General in a few minutes.


ES6+ linting

I have a component which uses ES6+ features e.g.
myComponent extends React.Component { static propTypes = {
This throws a syntax error as expected because it is an ES6+ feature. In the past I have installed the relevant npm modules e.g. ("babel-preset-stage-0":) and altered the babel.rc file and it has been successful but even with these additions in this setup, i'm still getting syntax errors:
My babel.rc file looks like this
{
  "presets": [
    ["env", {
      "targets": {
        "node": true
      }
    }],
    "react",
    "stage-0",
    "es2015"
  ]
}

Package.json:
"babel-preset-es2015": "^6.24.1",
"babel-preset-react": "^6.24.1",
"babel-preset-stage-0": "^6.24.1",

I have a similar issue whilst trying to use ES7 decorators. I managed to get it running on development by adding  transform-decorators-legacy and transform-class-properties to /kit/webpack/browser.js, but couldn't figure out a way that would work for production as well.
Having these in .babelrc didn't work at all.
Any tips appreciated.

Thanks for reporting. I'll add ES7 support to the next release, hopefully tomorrow.
.babelrc is solely to kick-start the Webpack build process; all code-level syntax is handled inside the browser.js and server.js Webpack config files in kit/webpack, so that's where plugins and transforms need to go.
Will report back here when decorator and static support is added.

I'm all for supporting some esnext features, but I would recommend only enabling specific transforms that are popular instead of setting stage-x presets. There's some talk among the Babel contributors on removing stage-x presets in the next version anyways due to the danger of their use and difficulty maintaining.

Agreed @jtmthf - presets like stage-0 are too broad, and would defeat the purpose of the more selective env preset. This enhancement would be specifically about adding static class properties and decorators.

Moving this to https://github.com/reactql/kit/issues/2

Decorators and static properties have been now added to the kit

Thanks a million! Off topic, but is there an official way to upgrade an existing project created with the CLI?

@hellojere - my pleasure. Upgrading-- unfortunately not. Please see my comment here for some more thoughts on upgrading.
TL;DR- Since this is a starter kit rather than an imported framework, kit + custom code live side-by-side, making it tricky to upgrade without overwriting changes. The easiest way to upgrade is to create a new project, copy over src and then manually make any changes to the kit that may have changed between versions.


Regenerate JavaDoc.i and PythonDocstring.i on OSX

Change-Id: Iff201c1c139431f55d2353921af6d428fb3f61c5

This appears to have too many "See:" added.


any idea how to make this library work with pubg mobile can't use mic while record

Hello,
If microphone is still in use by other app you can't do anything. You only can use microphone in an app at same time


Logged in business gets a 404 when clicking

1. Severity:
medium
2. Reported by:
Abdelrahman El Meniawy
3. Description:
Logged in business, clicking  from the drop down menu in the navbar gets a 404 page.
4. Steps to reproduce the issue:

Login as a business
Click on my account drop down menu in the navbar
Choose my page
get a 404 not found
5. Expected result:
Expected redirecting to my business page

@ameniawy Does this happen every-time or only the first time after logging in?


[QA] check adaptions related to new roles

New roles have been accepted.
Check whether adaptsion should be done

fixed at 1.2.0


Check Pod and PVC namespace while rendering

Name of the PVC can be the same in different namespaces, in this
scenario an application pod is connected to multiple PVC.

Add adjacency between Pod and PVC when claim name and namespace are same.

Signed-off-by: Akash Srivastava<EMAIL_ADDRESS>

@bboreham would you mind reviewing this one?


Replace satori/go.uuid by gofrs/uuid (#611)

Fixes #611

This makes sense. Must seems a bit weird, are there any ways we could get around this? Should we follow up on that at some point? Could create an issue for now, it's not blocking

@JoelSpeed the other alternative is to do the traditional error handling. Something like:
uuid, err := uuid.NewV4()
if err !=nil {
//handle the error here
}
//do something with uuid.String()

A bit more verbose, but if you have a strong feeling about using Must, I can do the refactor. Wdyt?

It would be more correct to take the error and return a 500 I would say

@JoelSpeed ready for another round.


Unable to scroll up when notebook cell has streaming output

Testing #177719

Run the following in a Jupyter notebook cell
Try to scroll upwhile the cell is executing
:bug: I keep getting scrolled back down to the latest output. The debug / output consoles do not behave like this

import time
for i in range(200):
    time.sleep(1)
    print(i)

https://user-images.githubusercontent.com/30305945/226661821-5fef66bc-ab61-4d70-aafa-f189c3418a5f.mp4

Duplicate https://github.com/microsoft/vscode/issues/177721, I just noticed this was in the Known issues section of the TPI at the time that the TPI was created, but scrolling behavior was also listed as something that I should test in the test plan item, which doesn't make sense to me.


Create databases for the countries

All countries present need databases

We seem to be able to create draft datasets on Mendeley and download them from there. This then allows users with the link to access the data but not anyone outside of the group. To do this 1) create the repository (already exists), 2) upload the datasets in country folders, 3) click preview and copy the links to a dictionary that is read in and used for downloading.
Doing this allows us to download the data as we do in the current notebook for Ghana.
For the dictionary we can use a yml file:
import yaml

with open('example.yml', 'r') as file:
    data = yaml.safe_load(file)

Code snippet above does not require any additional packages
Before reading in the yml we can create a cell with roll-down menus of available options (keys)

For unprocessed data we can give:

Livestock
Temperature
GHS urban


Generated Eclipse .classpath contains lib entries for 'build/classes/main' and 'build/resources/main'

These 2 entries should not be added to the .classpath file of Eclipse:

This seems to be a flaw in the eclipse plugin: If you create a reference from a configuration to a source set's output like so:
dependencies {
    integrationTestCompile sourceSets.main.output
}

Then the eclipse plugin will add extra "lib" entries for the main source set to the .classpath file. This is rather silly, because that source set is already contained via "src" entries.
So until this is fixed, I included a "workaround" in the testsets-plugin that removes these superfluous entries. It is equivalent to:
eclipse {
    classpath.file.whenMerged { classpath ->
        // Get all output directories for other source sets' classes and resources.
        def outputPaths = eclipseClasspath.project.sourceSets*.output
                .collect { [ it.classesDir, it.resourcesDir ]}
                .flatten { file -> Paths.get(file as String) } as Set
        classpath.entries.removeAll { ClasspathEntry entry ->
            entry.kind == 'lib' && Paths.get(entry.path) in outputPaths
        }
    }
}


Temporary gonzales

Due to the issue here https://github.com/tonyganch/gonzales-pe/issues/149 gonzales-pe can no longer be installed on windows. As a temporary stop gap I've removed the post install script and just updated a few things and republished to npm as gonzales-pe-sl.
This PR replaces it in sass-lint and runs all our tests fine. If we could test this on a windows machine now that would be great.. I dont have access or time to one tonight!

Coverage remained the same at 96.871% when pulling f5744ec226e770b63de3846debb45082ec0418c0 on DanPurdy:feature/temp-gonzales into c44337bcec05c463e502be830d32c348a070fa76 on sasstools:feature/gonzales-3-develop.

We can switch back to the official gonzales-pe once it's updated to remove the bash-centric post install script

Installed just fine for me on:
Windows 7
NPM v2.14.20
Node v4.4.0

Thanks @mven!

Verified to be installable on windows and non bash systems.. Made me aware of some Sass format windows issues though, mostly look to be AST related again though..


Make blockquote attention recognize more syntaxes

Fix #31214

Also see discussion in https://github.com/go-gitea/gitea/pull/31231. Personally I'm fine with more GitHub compat.