Added an engine data interpolation example from the RMTS paper

:x: Build SMT 0.1.226 failed (commit https://github.com/SMTorg/SMT/commit/6dac04da6f by @)

:white_check_mark: Build SMT 0.1.227 completed (commit https://github.com/SMTorg/SMT/commit/5790948f1e by @)


Handshake failed with fatal error SSL_ERROR_SSL: error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE.

This is with the current master of Lnd, as run by Zap.
CERT EXISTS, STARTING GRPC
[0] E0307 18:10:13.136523000<PHONE_NUMBER>44320 ssl_transport_security.c:970] Handshake failed with fatal error SSL_ERROR_SSL: error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE.
[0] error:  { Error: Connect Failed
[0]     at ClientReadableStream._emitStatusIfDone (/Users/ben/Development/Bitcoin/zap-desktop/app/node_modules/grpc/src/client.js:255:19)
[0]     at ClientReadableStream._readsDone (/Users/ben/Development/Bitcoin/zap-desktop/app/node_modules/grpc/src/client.js:221:8)
[0]     at readCallback (/Users/ben/Development/Bitcoin/zap-desktop/app/node_modules/grpc/src/client.js:283:12) code: 14, metadata: Metadata { _internal_repr: {} } }
[0] status:  { code: 14,
[0]   details: 'Connect Failed',
[0]   metadata: Metadata { _internal_repr: {} } }
[0] error:  { Error: Connect Failed
[0]     at ClientReadableStream._emitStatusIfDone (/Users/ben/Development/Bitcoin/zap-desktop/app/node_modules/grpc/src/client.js:255:19)
[0]     at ClientReadableStream._readsDone (/Users/ben/Development/Bitcoin/zap-desktop/app/node_modules/grpc/src/client.js:221:8)
[0]     at readCallback (/Users/ben/Development/Bitcoin/zap-desktop/app/node_modules/grpc/src/client.js:283:12) code: 14, metadata: Metadata { _internal_repr: {} } }
[0] TRANSACTION STATUS:  { code: 14,
[0]   details: 'Connect Failed',
[0]   metadata: Metadata { _internal_repr: {} } }
[0] 2018-03-07 18:10:13.161 [DBG] BTCN: waiting to see if more peers will respond with cfheaders

Here's a temp workaround from @jackmallers:
process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'
process.env.GRPC_SSL_CIPHER_SUITES = 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384'

@Empact yeah working for me locally on my cipherseed restore/backup seed branch I will push up tonight.
Just need to set those env variables before you read the cert and establish the grpc connection


Add support for 1 and 4 bit palletized RGB bitmaps.

https://www.fourcc.org/pixel-format/rgb-bi_rgb/

Fixed, Added enough support to import one and four bit palletized RGB bitmaps.


undefined name 'String' when compiling multiple source files non-sequentially

TourModules.zip
Steps:
Unzip the attached zip file, preserving structure so the 2 files end up in a TourModules directory.
(contents of these are directly from: https://docs.hylo-lang.org/language-tour/modules)
Using the hc compiler version 3166db52f95b333152461f1f19fbf3a77b8d7230, attempt to build the 2 source files into an exe via:
$ ./.build/arm64-apple-macosx/release/hc TourModules -o hello2
In case it matters, I'm using an Apple M1 Pro laptop with macOS 13.5 (22G74) and swift version info:
swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx13.0
Actual Result:
Frequently, an error is presented that one of the Core types (String here) is not defined, but occasionally it succeeds. Even if the input files are specified on the command line explicitly, it always seems to be Greet.hylo that exhibits the error (regardless of the order in which the source files are specified).
$ ./.build/arm64-apple-macosx/release/hc TourModules -o hello2
/Users/dtull/repos/hylo/TourModules/Greet.hylo:2.19-25: error: undefined name 'String' in this scope
fun greet(_ name: String) {
                  ~~~~~~
$ ./.build/arm64-apple-macosx/release/hc TourModules -o hello2
$ ./.build/arm64-apple-macosx/release/hc TourModules -o hello2
/Users/dtull/repos/hylo/TourModules/Greet.hylo:2.19-25: error: undefined name 'String' in this scope
fun greet(_ name: String) {
                  ~~~~~~

Expected Result:
It should always behave the same and succeed.
Workaround:
It always succeeds if I specify the --sequential option to the compiler command as follows:
$ ./.build/arm64-apple-macosx/release/hc TourModules --sequential -o hello2

Side note: the variable interpolation feature for the print function doesn't work yet as implied by the example, but otherwise the resulting binary when the compilation does not emit the error does appear to work correctly.

Additional strange detail. Even with --sequential, if I specify the source files individually, I get the error.
$ ./.build/arm64-apple-macosx/release/hc TourModules/Hello2.hylo TourModules/Greet.hylo --sequential -o hello3
TourModules/Greet.hylo:2.19-25: error: undefined name 'String' in this scope
fun greet(_ name: String) {
                  ~~~~~~


Add TSMP

Insert URLs to the project here:
https://github.com/HPSCTerrSys/TSMP

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.

@jjokella @chartick


did:pkh - Public Key Hash DID method

Implement #123
Depends on #133

[x] Add DID method skeleton
[x] Decide on DID format. Decided: it will be like did:pkh:tz:…, did:pkh:eth:…, did:pkh:btc:…
[x] Enable proof types used with did:tz
[x] Test DID resolution
[x] Test LD-Proofs
[x] DID generation from JWK? For didkit key-to-did: would need a way to indicate the pkh subtype.
[x] Support addresses for Tezos and Ethereum
[x] Support Bitcoin addresses
[x] Represent Solana addresses? Yes, they appear to use the identity hash. Note: verifying SolanaMethod2021 is not yet implemented.
[x] Support blockchainId property

IMO, we can claim the Solana uses the identity hash function.

This is looking great. Could we also add support for dogecoin?

I’d love to see support for did:onion. We already have a working server at http://fscst5exmlmr262byztwz4kzhggjlzumvc2ndvgytzoucr2tkgxf7mid.onion/ and example but real did:onion did document at http://fscst5exmlmr262byztwz4kzhggjlzumvc2ndvgytzoucr2tkgxf7mid.onion/.well-known/did.json
Code for server at: https://github.com/BlockchainCommons/torgap-demo
Basically did:onion uses 25519 keys but encoded in the onion address url rather than base64 or hex, can work like did:key or did:web, but has the advantage of no dns and no correlation of either the client or server. Getting the current did:document also serves as proof of control of the private key as you can’t receive it over the onion protocol unless you control it.
We also have a Open Time Stamp service available at , which can serve as a proof of existence on a particular date for did:documents or VCs. http://3xcaaswwserqnox56z7d7wifwyxm2jsdv4fniffym5jwncqx3qr7uzid.onion/
/cc @gorazdko

@wyc yes, we can add a pkh:doge.
@ChristopherA thanks for the info; I've opened a new issue to track did:onion: #134

@clehner did you want to squash your fixups prior to commit? Otherwise I will merge tomorrow evening ET. Thanks!

Rebased

Merged.


Bumped 2.x branch from version 2.2.0 to 2.3.0.

Signed-off-by: AWSHurneyt<EMAIL_ADDRESS>Issue #, if available:
https://github.com/opensearch-project/alerting/issues/534
Description of changes:
Bumped 2.x branch from version 2.2.0 to 2.3.0.
CheckList:
[x] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The whitesource check references snakeyaml in its failure messages. That failure is caused by the OpenSearch 2.3 zip (as mentioned here, not the alerting plugin. As mentioned here, that issue will be resolved on the OpenSearch side, not alerting.
As a result, the whitesource failure in this PR shouldn't need remediation.

Codecov Report

Merging #547 (4c33018) into 2.x (dd48aae) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                2.x     #547      +/-   ##
============================================
- Coverage     76.76%   76.73%   -0.03%
  Complexity      176      176
============================================
  Files           166      166
  Lines          8370     8370
  Branches       1232     1232
============================================
- Hits           6425     6423       -2
- Misses         1341     1343       +2
  Partials        604      604

Impacted Files
Coverage Δ

...nationmigration/DestinationMigrationCoordinator.kt
63.82% <0.00%> (-4.26%)
:arrow_down:

...ain/kotlin/org/opensearch/alerting/AlertService.kt
77.99% <0.00%> (-0.48%)
:arrow_down:

...destinationmigration/DestinationConversionUtils.kt
70.00% <0.00%> (ø)

...rch/alerting/opensearchapi/OpenSearchExtensions.kt
55.40% <0.00%> (+1.35%)
:arrow_up:

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


add datasetKey as a potential qualifier

I have been testing how well the current vocabulary and rule structure works on example taxonKeys.
One weakness is that we have no way to handle when occurrences are in a plausible location but still suspicious.
I see two solutions to this scenario (without involving gbifIds).

Fix occurrences at source, since this tool isn't meant to solve every data quality issue.
Add datasetKey as a qualifier. So users can say datasetKey + taxonKey + Polygon -> "suspicious"

I am undecided whether this would be worth the added complexity.
Example I made with Lions. Occurrences in the yellow box are all from the same dataset and claim to be in the big national park above.

https://jhnwllr.github.io/panthera-leo-example-range-annotations/

Thanks, @jhnwllr - I'm inclined to suggest we implement option 2.
An alternative could be to create rules under the scope of a dataset. However, those rules would be of the form dataset A + GEOM = "suspicious" which would flag records of any taxon, including genuine in-situ sightings. The motivation there was mainly to handle truly bogus coordinates (e.g. middle of the sea points against terrestrial-only data) where attempts to fix things at source failed. I suspect that is still useful in some cases.

I have changed the API by removing the current single-context approach (i.e. contextKey and contextType gone) and replaced it with the simpler taxonKey and datasetKey allowing for either or both to be provided.
Finding rules can then still be done by querying uring taxonKey or datasetKey, and taxon-based rules can be additionally scoped by the dataset when creating them.
@jhnwllr - please can you update your scripts, noting that taxonKey is an integer, not a string (see the README for an example)


autopilot.js: losing --enable-bladeburner flag after installing augs

I see the reasoning behind disabling bladeburner by default, but in BN6 and BN7 that should not be the case I think, so I run autopilot.js --enable-bladeburner there.
After autopilot decides to install augs, the flag is lost and bladeburner gets disabled again - even when I already installed The Blade's Simulacrum.
I think its more sensibe to default to run bladeburner regardless of the flag, at least when The Blade's Simulacrum is present. Even more better would be if this (and potentially all) autopilot flags would survive installing augs. (In this case, because the concurrent Bladeburner aug is pretty expensive and probably not obtained in the first resets).
What do you think about this?

Autopilot.js not maintaining arguments is a known missing feature at the moment, to my understanding 😅

Created #104 for this

That looks very promising 😄

Now that #104 is closed, can we get a quick tutorial on how to use config files so we can close this? 😅

@Evanito  no need! It was always part of my plan to then leverage this feature to have autopilot automatically write out its config overrides to preserve them, so it should "just work" now.

@Evanito  That said, added docs here if you still want them for other scripts :)
https://github.com/alainbryden/bitburner-scripts/blob/main/README.md#config-files


ACCUMULO-3807 Avoid Copy/Sort column on WAL recovery exceeds 100%

The Math.max() will solve the issue I hope.
I'm not sure what happens if Property.TSERV_WAL_BLOCKSIZE is not 0 and smaller than Property.TSERV_WALOG_MAX_SIZE. The problem is that TabletServerLogger still uses Property.TSERV_WALOG_MAX_SIZE to check data size stored in one file. While file size  is set to Property.TSERV_WAL_BLOCKSIZE.

Changed max to min.
Unfortunately ACCUMULO-4413 is a duplicate of ACCUMULO-3807. Should I create a new pull request for that ticket? Also there are some concerns about this issue under ACCUMULO-3807 this modification should follow, but don't know how yet.

@ghajos  I'll go ahead and change the title of this PR now to point to 3807. If you want to edit the log message to change it to 3807, that's fine. Otherwise, a committer can do it before merging, leaving you to focus on the changeset, which is the important part :smile_cat: .

Thanks, @ghajos ! If you'd like to be added to our contributors page at https://accumulo.apache.org/people/ , feel free to issue a pull request to modify https://github.com/apache/accumulo-website/blob/master/pages/people.md

@ctubbsii @mikewalch Thank you for the review!


Query sometimes fails with "Failed to delete temporary file" when writing to a sorted (sorted_by) bucketed Hive table on S3

Right now the sorted_by table property in the hive connector does not work very well when the tables are stored in s3. SortingFileWriter.java writes lots of sorted temporary files to s3 (in order to not consume a bunch of memory for sorting) and then merges them together. This is a problem right now because:

From a performance perspective, writing tmp files to s3 is slower than local disk.
From a correctness perspective, SortingFileWriter.mergeFiles does not work on s3 because s3 lacks read after write consistency for file deletes. Specifically these lines:
https://github.com/prestosql/presto/blob/master/presto-hive/src/main/java/io/prestosql/plugin/hive/SortingFileWriter.java#L226-L229

Will sometimes error out as s3 temporarily thinks the file still exists as it was just deleted.
See here for the stacktrace reproducing 2:
io.prestosql.spi.PrestoException: Failed to write temporary file: s3://spothero-science-dev/segment_local/processed/grant_test_bucketing_sorting_limit/.tmp-sort.000007_0_20191217_190758_08542_eedb5.77
	at io.prestosql.plugin.hive.SortingFileWriter.writeTempFile(SortingFileWriter.java:251)
	at io.prestosql.plugin.hive.SortingFileWriter.combineFiles(SortingFileWriter.java:200)
	at io.prestosql.plugin.hive.SortingFileWriter.writeSorted(SortingFileWriter.java:186)
	at io.prestosql.plugin.hive.SortingFileWriter.commit(SortingFileWriter.java:139)
	at io.prestosql.plugin.hive.HiveWriter.commit(HiveWriter.java:86)
	at io.prestosql.plugin.hive.HivePageSink.doFinish(HivePageSink.java:191)
	at io.prestosql.plugin.hive.authentication.UserGroupInformationUtils.lambda$executeActionInDoAs$0(UserGroupInformationUtils.java:29)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:360)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1710)
	at io.prestosql.plugin.hive.authentication.UserGroupInformationUtils.executeActionInDoAs(UserGroupInformationUtils.java:27)
	at io.prestosql.plugin.hive.authentication.ImpersonatingHdfsAuthentication.doAs(ImpersonatingHdfsAuthentication.java:39)
	at io.prestosql.plugin.hive.HdfsEnvironment.doAs(HdfsEnvironment.java:80)
	at io.prestosql.plugin.hive.HivePageSink.finish(HivePageSink.java:182)
	at io.prestosql.spi.connector.classloader.ClassLoaderSafeConnectorPageSink.finish(ClassLoaderSafeConnectorPageSink.java:74)
	at io.prestosql.operator.TableWriterOperator.finish(TableWriterOperator.java:193)
	at io.prestosql.operator.Driver.processInternal(Driver.java:397)
	at io.prestosql.operator.Driver.lambda$processFor$8(Driver.java:283)
	at io.prestosql.operator.Driver.tryWithLock(Driver.java:675)
	at io.prestosql.operator.Driver.processFor(Driver.java:276)
	at io.prestosql.execution.SqlTaskExecution$DriverSplitRunner.processFor(SqlTaskExecution.java:1075)
	at io.prestosql.execution.executor.PrioritizedSplitRunner.process(PrioritizedSplitRunner.java:163)
	at io.prestosql.execution.executor.TaskExecutor$TaskRunner.run(TaskExecutor.java:484)
	at io.prestosql.$gen.Presto_314____20191210_204803_1.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.UncheckedIOException: java.io.IOException: Failed to delete temporary file: s3://spothero-science-dev/segment_local/processed/grant_test_bucketing_sorting_limit/.tmp-sort.000007_0_20191217_190758_08542_eedb5.76
	at io.prestosql.plugin.hive.SortingFileWriter.mergeFiles(SortingFileWriter.java:236)
	at io.prestosql.plugin.hive.SortingFileWriter.lambda$combineFiles$2(SortingFileWriter.java:200)
	at io.prestosql.plugin.hive.SortingFileWriter.writeTempFile(SortingFileWriter.java:245)
	... 26 more
Caused by: java.io.IOException: Failed to delete temporary file: s3://spothero-science-dev/segment_local/processed/grant_test_bucketing_sorting_limit/.tmp-sort.000007_0_20191217_190758_08542_eedb5.76
	at io.prestosql.plugin.hive.SortingFileWriter.mergeFiles(SortingFileWriter.java:231)
	... 28 more

A short term solution to just the s3 problem consistency problem is to not do the read after delete and instead to check the return boolean of fileSystem.delete.
A longer term solution to both problems might be to use local disk for spilling tmp files instead of s3. This would improve performance as well as avoid consistency problems with s3.
@findepi And I talked about this in a slack thread here:
https://prestosql.slack.com/archives/CGB0QHWSW/p1576484582050100?thread_ts=1576180076.157800&cid=CGB0QHWSW

I think it's fine if we simply remove the check, per the Hadoop FS specification

@grantatspothero can I assign this to you?
I've split this issue into two, as it seems (per @electrum 's comment) that a query failure fix is much simpler than the performance improvement we can get.
The bullet no 1 is covered by: https://github.com/prestosql/presto/issues/2301

@findepi 👍 I can remove the unnecessary file checks and test sorting on s3.

@grantatspothero I'm still getting exceptions as you described above on master.  Were you able to submit a PR for the fix you described?

@ddrinka I got distracted and never got a chance, thanks for opening a PR. You might want to audit the whole SortedFileWriter I remember there was potentially at least one other place where a similar readafterwrite consistency problem could occur.

@electrum Anything I can do on the PR to get this in the next release?  I'm not able to run with bucketed sorting at all without this change.

I got to know this issue while discussing #3410. I tried setting hive.writer-sort-buffer-size to a high value such as 512MB on a high memory machine. Although I no longer query memory size exceeded error, the insert takes forever to finish. The bottleneck being upload of temporary files.
To make things worse, when the insert query is aborted the .tmp-sort... files uploaded to the s3 target bucket are left behind. And there is no "rm -rf" feature on s3 :(


Add missing chains

What problem does this new feature solve?
There are new testnets and layer2 available.
eg;
Polygon Amoy
Scroll
Scroll Speolia
and others that are not available in the app kit.
Even if i just create it, i am not allowed to switch network.

Describe the solution you'd like
I would like the list of chains to be up to date or be able to add them

Pleaes check our new section in our docs -> https://docs.reown.com/appkit/react/core/custom-networks


Cannot mark text by double click

I'm getting "Please change caller according to com.intellij.openapi.project.IndexNotReadyException documentation" when double click on a word in .sh file. PHPStorm 10.0.3.

Does this always happen or only when PHPStorm is indexing at the same time?

Related to #306
I'll see if I can reproduce and fix this for the next update.

Hopefully fixed for the next update.


XML doc comments changes

Move defaults from remarks to summary for better intellisense.
Add summary to describe LockoutOptions AllowedForNewUsers.
Added defaults to xml docs where missing.

Fixes #1426

@scottsauber,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks!

Glad to help, thanks for accepting!


Selectively reload source files using exsync

Some files/modules are more safe/reasonable to reload while the application is running. Anything that's short-lived (request handlers, templates for example) is ok, but reloading slightly changed long-lived GenServers can break your app, maybe even in a hard to diagnose way.
This is a Proof of concept of selective reloading:

The example project with selective reloading enabled: https://github.com/nietaki/reloader
Relevant commit: https://github.com/nietaki/reloader/commit/0072084bc6ad519db35215759dba7da6d0aa4ec8
Changes I made to exsync: https://github.com/falood/exsync/compare/master...nietaki:selective-reloading?expand=1

The exsync tweak could probably be done more elegantly, but the changes I made were the least invasive - alternatives would probably require some more refactoring.
I checked on Ubuntu, OSX and inside the docker container - you can point at individual files and it still works.

Looks sensible.

@CrowdHailer Do you think this is a change that we could get into official exsync? Is there any adjustments you thing should be made first?
I'd rather not have raxx_kit generate projects pointing at a random branch in a random repo for one of the deps, feels a bit bootleg.
At the same time, there's a lot of variables involved with the code reloading stuff (umbrella projects, operating systems, unorthodox project layouts), maybe it makes sense to try it out for a while and iron out any problems first 🤷♂

I think it's possible. Certainly if you have found it useful open up a PR on ExSync where it can be discussed.
Raxx.kit is definitely best off pointing at a real release, if not when will people know to upgrade.
Re all the other variables, I think with ubuntu, osx and docker that's a reasonable start.


SM release

Codecov Report

Merging #232 (101167f) into main (6dd73cc) will decrease coverage by 1.11%.
The diff coverage is 37.91%.

:exclamation: Current head 101167f differs from pull request most recent head 709dbe4. Consider uploading reports for the commit 709dbe4 to get more accurate results

@@            Coverage Diff             @@
##             main     #232      +/-   ##
==========================================
- Coverage   55.71%   54.60%   -1.12%
==========================================
  Files          59       62       +3
  Lines        4284     4474     +190
==========================================
+ Hits         2387     2443      +56
- Misses       1897     2031     +134

Impacted Files
Coverage Δ

db/python/layers/sample.py
49.00% <0.00%> (ø)

sample_metadata/parser/sample_file_map_parser.py
72.50% <ø> (ø)

test/test_parse_file_map.py
100.00% <ø> (ø)

scripts/process_ont_products.py
4.58% <4.58%> (ø)

test/test_parse_ont_processor.py
21.73% <21.73%> (ø)

sample_metadata/parser/cloudhelper.py
58.33% <58.33%> (ø)

sample_metadata/parser/generic_parser.py
81.75% <84.00%> (+6.55%)
:arrow_up:

scripts/parse_ont_sheet.py
81.69% <90.00%> (+3.25%)
:arrow_up:

sample_metadata/parser/generic_metadata_parser.py
76.06% <100.00%> (-0.16%)
:arrow_down:

test/test_parse_generic_metadata.py
100.00% <100.00%> (ø)

... and 2 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 6dd73cc...709dbe4. Read the comment docs.


Make region optional in Snowflake connection

Snowflake allows and if anything seems to encourage not adding in the region parameter to a Snowflake connection. The reason is because Snowflake recently moved to a system where the "region" is no longer part of the URI.
Under the hood, Airflow just passes to the Snowflake SQLAlchemy URL(), and under the hood Snowflake's URL() allows for region to be optional.
Fix
region should be allowed to be optional, basically. I wanted to do an approach that did not rely on magically trimming a trailing ., so something that explicitly checks for when region is not specified.
There were two approaches I could go with that meets the requirement: either fix it in Python, or fix it in profiles/snowflake.py. I went with the former approach because doing lots of things in Jinja2 is usually harder to maintain than doing the equivalent in Python, but it would have looked like this:
"account": "{{ env_var('SNOWFLAKE_ACCOUNT') ~ '.' ~ env_var('SNOWFLAKE_REGION')"
           " if env_var('SNOWFLAKE_REGION')"
           " else env_var('SNOWFLAKE_ACCOUNT') }}",

Pyproject.toml change
I also added pytest to the project as it wasn't specified as a dependency, but the tests/ folder uses it.

@dwreeves could you give me an example of what the formatted snowflake URI might look like (obviously without an actual password)? The way this is set up right now ensures that if there's a working snowflake connection in Airflow, then it can be used for cosmos. When I take away the region for a snowflake region, the connection is no longer valid in Airflow

@pohek321 Hmm, that's interesting.
To be clear, if you are on the legacy system for Snowflake account IDs, and you want to construct a URI without the region field, you move it over to the account part of the URI.
I'm on provider package 2.7.0 and my secret looks something like this and it works fine:
{"conn_type": "snowflake", "user": "SOME_USER", "password": "SOME_PASSWORD", "extra": "{\"account\": \"12345.us-east-1\", \"warehouse\": \"SOME_WAREHOUSE\", \"database\": \"SOME_DATABASE\", \"role\": \"SOME_ROLE\"}"}

Note that it's {"account": "12345.us-east-1"}. Removing the region from that part of the URI for legacy Snowflake connections only works for us-west-1 I believe.
For good measure, my Airflow dbt integration does the following. (1) Places the secrets directly in the .yml, i.e. I'm not using {{ env(...) }}, (2) dump the .yml file in /tmp (FWIW, I think I like your approach better than mine):
conn = self.snowflake_hook.get_connection(conn_id)
profile = self.dbt_profile_name: {
    "outputs": {
        self.dbt_target_name: {
            "account": conn.extra_dejson.get("account"),
            ...
        }
    }
}

For whatever it's worth, I also am the last person who committed to the docs for the Snowflake connection 😅 https://github.com/apache/airflow/blob/main/docs/apache-airflow-providers-snowflake/connections/snowflake.rst

@dwreeves, I appreciate your patience while I wrap my head around this.
I think this change would make sense, so in Airflow, your connection would look something like this, right:

Turns out yes, we can remove the host from the UI. 😄 https://github.com/apache/airflow/pull/29208

@dwreeves, good to know! I did what you suggested, and it worked! I did not realize that the host parameter was optional.
However, I was able to break it (and by break, I mean the connection test in Airflow succeeds, but Cosmos cannot authenticate). It broke by putting <account>.<region> in the account field as well as <region> in the region field -- interestingly enough, Airflow was OK with this (Cosmos was not).
So I added a couple of lines to handle that scenario! If you are cool with the commit, then I'll approve and merge, and we'll tag a new release so you can access these features.
Additionally, thank you so much for your contributions! If you need anything else (or have ideas for improvements), don't hesitate to reach out or open issues. 🍻


Add pre-commit CI

Seeing how you already have a pre-commit config, you should add https://pre-commit.ci/ so that all PRs are automatically checked and formatted against the existing style config. (It even applies autofixes to PRs).

thank you! added 👍


Validate endpointspec in control api

Currently endpoint spec is not validated at the control api to see if
there are duplicate port configs. Also fixed a duplicate VIP problem
when the endpoint spec was getting updated.
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 53.45%

Merging [#1023][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.17%

@@             master      #1023   diff @@
==========================================
  Files            75         75
  Lines         11616      11632    +16
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6230       6218    -12
- Misses         4485       4516    +31
+ Partials        901        898     -3

[][cc-pull]

Powered by Codecov. Last updated by [a9d3d7d...1e0f0d7][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/a9d3d7d302f336b76c7578b2fc8da95c68d5b465...1e0f0d7f5fbd4192e9ed1f58551db19136b7e7b5
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/1023?src=pr

LGTM

LGTM


Removed mention of Bitcoin.

Per discussion here: https://github.com/gratipay/inside.gratipay.com/issues/201#issuecomment-102085739

!m @webmaven
Thanks! :-)


Sounds are global

For some reason on my server running 1.19.2, if one person is being stalked by the Cave Dweller, everyone on the server can hear the noises as if he is right next to you. Makes it too annoying to be usable.

Are you referring to the chase sound?
Or the ambient noises? Those are currently played to all potential targets (which is intended)
Potential target meaning they fit the criteria for the cave dweller to spawn at

I’m referring to the cave noises specific to the cave dweller, indicating he’s drawing near. When it was happening, one of the players on my server was in a cave (valid) another was on the surface near the base (invalid) and I was in a forest (invalid), also thousands of blocks apart, yet we could all hear the noises. They were happening every 10 seconds or so.
On Oct 13, 2023, at 12:31 AM, SiverDX @.***> wrote:

Are you referring to the chase sound?
Or the ambient noises? Those are currently played to all potential targets (which is intended)
Potential target meaning they fit the criteria for the cave dweller to spawn at
—
Reply to this email directly, view it on GitHubhttps://github.com/SiverDX/cave_dweller/issues/12#issuecomment-1760889320, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASMD7PUS535NO4HN5WOEWJTX7DG4DAVCNFSM6AAAAAA5ZNHOHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRQHA4DSMZSGA.
You are receiving this because you authored the thread.Message ID: @.***>


Fix POM and remove test from old API

I just grabbed a clean fork of the repo to tidy things up a bit, and it looks like the pom is broken and some tests refer to the old API. This just tidies this up - maybe it was like that for a reason, but when starting from a fresh fork, it doesn't work currently.
Signed-off-by: Chris Jackson<EMAIL_ADDRESS>

Hi
The old API should remain functional for backwards compatibility over one
major release at least. Is the build broken. I think master has been
passing ok with CI build.
Br,
tommi
On Mon, Aug 29, 2016 at 8:05 PM, Chris Jackson<EMAIL_ADDRESS>wrote:

I just grabbed a clean fork of the repo to tidy things up a bit, and it
looks like the pom is broken and some tests refer to the old API. This just
tidies this up - maybe it was like that for a reason, but when starting
from a fresh fork, it doesn't work currently.
Signed-off-by: Chris Jackson<EMAIL_ADDRESS>You can view, comment on, or merge this pull request online at:
https://github.com/tlaukkan/zigbee4java/pull/99
Commit Summary

Fix POM and remove test from old API

File Changes

M zigbee-gateway-server/pom.xml
https://github.com/tlaukkan/zigbee4java/pull/99/files#diff-0 (3)
M zigbee-gateway-server/src/test/java/org/bubblecloud/
zigbee/ZigBeeNetworkTest.java
https://github.com/tlaukkan/zigbee4java/pull/99/files#diff-1 (41)

Patch Links:

https://github.com/tlaukkan/zigbee4java/pull/99.patch
https://github.com/tlaukkan/zigbee4java/pull/99.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tlaukkan/zigbee4java/pull/99, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAONRinGQy0vVhvtB4ibS4GsqYPpiIQ8ks5qkxFLgaJpZM4Jvrjw
.

--
Best regards,
Tommi Laukkanen

The pom doesn’t seem to depend on the serial library which stops it working here. That was the main problem I had to get it running from scratch.

Ah right, because of the move of the serial interface.

I’m not sure what you’re referring to - if you mean the other discussion on the location of the SerialPort interface, then that shouldn’t be relevant as that’s in another branch. This was an issue in master. Maybe it’s just an eclipse issue if you actually want to run the software.

Ok, just made the connection because when I was looking into pull request and was wondering if it will compile due to dependecy problems.


Environment: Setup VPS for Testing Environment

Describe the problem
Project requires testing environment to exist.
Which environment are you having trouble with?

[ ] development
[x] testing
[ ] production

Add some comments or screenshots for easier help

Server under https://srv10.mikr.us:20114 configured sucessfully.


fix: React-editor 'onEvent' props missing

Please check if the PR fulfills these requirements

[x] It's the right issue type on the title
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added/updated (for bug fixes/features)
[x] It does not introduce a breaking change or has a description of the breaking change

Description
Fix React-editor 'onEvent' props missing, or it will cause a fatal error when using TypeScript.

Thank you for your contribution to TOAST UI product. 🎉 😘 ✨

Done! This works great in my project.

Done! This works great in my project.


causing sql-migrate installation failed using go get in Apple Silicon

I try to install sql-migrate in macos 11.1, Apple M1 chip. My go version is Go.1.16Beta1
/usr/local/go/pkg/tool/darwin_arm64/link: running clang failed: exit status 1
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000000.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000001.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000002.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000003.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000004.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000005.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000006.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000007.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000008.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000009.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000010.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-669664703/000011.o, building for macOS-arm64 but attempting to link with file built for unknown-x86_64
Undefined symbols for architecture arm64:
  "__cgo_02b52858a06a_Cfunc__Cmalloc", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__Cmalloc in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_bind_blob", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_bind_blob in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_bind_text", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_bind_text in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_create_function", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_create_function in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_limit", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_limit in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_open_v2", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_open_v2 in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_prepare_v2_internal", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_prepare_v2_internal in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_result_blob", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_result_blob in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_result_text", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_result_text in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_step_internal", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_step_internal in go.o
  "__cgo_02b52858a06a_Cfunc__sqlite3_step_row_internal", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc__sqlite3_step_row_internal in go.o
  "__cgo_02b52858a06a_Cfunc_free", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_free in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_aggregate_context", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_aggregate_context in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_backup_finish", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_backup_finish in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_backup_init", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_backup_init in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_backup_pagecount", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_backup_pagecount in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_backup_remaining", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_backup_remaining in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_backup_step", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_backup_step in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_bind_double", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_bind_double in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_bind_int", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_bind_int in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_bind_int64", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_bind_int64 in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_bind_null", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_bind_null in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_bind_parameter_count", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_bind_parameter_count in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_bind_parameter_index", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_bind_parameter_index in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_busy_timeout", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_busy_timeout in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_clear_bindings", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_clear_bindings in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_close_v2", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_close_v2 in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_blob", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_blob in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_bytes", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_bytes in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_count", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_count in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_decltype", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_decltype in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_double", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_double in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_int64", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_int64 in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_name", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_name in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_text", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_text in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_column_type", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_column_type in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_commit_hook", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_commit_hook in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_create_collation", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_create_collation in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_db_filename", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_db_filename in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_enable_load_extension", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_enable_load_extension in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_errcode", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_errcode in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_errmsg", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_errmsg in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_errstr", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_errstr in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_exec", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_exec in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_extended_errcode", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_extended_errcode in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_finalize", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_finalize in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_get_autocommit", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_get_autocommit in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_interrupt", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_interrupt in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_load_extension", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_load_extension in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_reset", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_reset in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_result_double", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_result_double in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_result_error", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_result_error in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_result_int64", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_result_int64 in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_result_null", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_result_null in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_rollback_hook", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_rollback_hook in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_set_authorizer", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_set_authorizer in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_threadsafe", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_threadsafe in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_update_hook", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_update_hook in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_user_data", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_user_data in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_value_blob", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_value_blob in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_value_bytes", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_value_bytes in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_value_double", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_value_double in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_value_int64", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_value_int64 in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_value_text", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_value_text in go.o
  "__cgo_02b52858a06a_Cfunc_sqlite3_value_type", referenced from:
      _github.com/mattn/go-sqlite3._cgo_02b52858a06a_Cfunc_sqlite3_value_type in go.o
  "_authorizerTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_authorizerTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_authorizerTrampoline)
  "_callbackTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_callbackTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_callbackTrampoline)
  "_commitHookTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_commitHookTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_commitHookTrampoline)
  "_compareTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_compareTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_compareTrampoline)
  "_doneTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_doneTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_doneTrampoline)
  "_rollbackHookTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_rollbackHookTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_rollbackHookTrampoline)
  "_stepTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_stepTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_stepTrampoline)
  "_updateHookTrampoline", referenced from:
      _github.com/mattn/go-sqlite3._Cfpvar_fp_updateHookTrampoline in go.o
     (maybe you meant: __cgoexp_02b52858a06a_updateHookTrampoline)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I have also tried env GOOS=darwin CGO_ENABLED=1 GOARCH=arm64 go get -v github.com/rubenv/sql-migrate/sql-migrate , but it is not functional.
The blame seems to lie with go-sqlite3.
Can someone help me?

Have you tried compiling any other cgo code? Does that work fine?

Have you tried compiling any other cgo code? Does that work fine?

Have you tried compiling any other cgo code? Does that work fine?

I am not that proficient in both c and go language, I don't know how to do it. But I download the go-sqlite3 and run go build -o abc, it produced a file named abc. Does it mean that go-sqlite3 succeed in compiling in darwin/arm64? So where the blame lies. I have opened an issue in sql-migrate, but they closed my issue.
What should I do then?

Have you tried compiling any other cgo code? Does that work fine?

I am not that proficient in both c and go language, I don't know how to do it. But I download the go-sqlite3 and run go build -o abc, it produced a file named abc. Does it mean that go-sqlite3 succeed in compiling in darwin/arm64? So where the blame lies. I have opened an issue in sql-migrate, but they closed my issue.
What should I do then?

You can test with a simple program like:
package main

import "C"
import "fmt"

func main() {
    fmt.Println(C.int(42))
}

What is the size of the abc archive you created? If it's very small, then you probably aren't compiling the cgo version, but just the non-cgo shims:
$ CGO_ENABLED=0 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 151K Jan  7 13:30 abc

$ CGO_ENABLED=1 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 3.0M Jan  7 13:30 abc

The error message:
attempting to link with file built for unknown-x86_64

Makes it sound like there's something wrong with the C compiler on your system – it tries to link against amd64(?) I don't really have experience on macOS systems, and certainly not on the new ARM systems.

You can test with a simple program like:
package main

import "C"
import "fmt"

func main() {
    fmt.Println(C.int(42))
}

What is the size of the abc archive you created? If it's very small, then you probably aren't compiling the cgo version, but just the non-cgo shims:
$ CGO_ENABLED=0 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 151K Jan  7 13:30 abc

$ CGO_ENABLED=1 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 3.0M Jan  7 13:30 abc

The error message:
attempting to link with file built for unknown-x86_64

Makes it sound like there's something wrong with the C compiler on your system – it tries to link against amd64(?) I don't really have experience on macOS systems, and certainly not on the new ARM systems.

You can test with a simple program like:
package main

import "C"
import "fmt"

func main() {
    fmt.Println(C.int(42))
}

What is the size of the abc archive you created? If it's very small, then you probably aren't compiling the cgo version, but just the non-cgo shims:
$ CGO_ENABLED=0 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 151K Jan  7 13:30 abc

$ CGO_ENABLED=1 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 3.0M Jan  7 13:30 abc

The error message:
attempting to link with file built for unknown-x86_64

Makes it sound like there's something wrong with the C compiler on your system – it tries to link against amd64(?) I don't really have experience on macOS systems, and certainly not on the new ARM systems.

You can test with a simple program like:
package main

import "C"
import "fmt"

func main() {
    fmt.Println(C.int(42))
}

What is the size of the abc archive you created? If it's very small, then you probably aren't compiling the cgo version, but just the non-cgo shims:
$ CGO_ENABLED=0 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 151K Jan  7 13:30 abc

$ CGO_ENABLED=1 go build -o abc
$ ls -lh abc
-rw-r--r-- 1 martin martin 3.0M Jan  7 13:30 abc

The error message:
attempting to link with file built for unknown-x86_64

Makes it sound like there's something wrong with the C compiler on your system – it tries to link against amd64(?) I don't really have experience on macOS systems, and certainly not on the new ARM systems.

yes, abc created, and its size is 9.2M
I wrote those code in abc.go  and  run go build -v abc.go,  it turned out:

# command-line-arguments
/usr/local/go/pkg/tool/darwin_arm64/link: running clang failed: exit status 1
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000002.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/go.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000003.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000004.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000006.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000008.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000005.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000007.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000009.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000010.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
Undefined symbols for architecture x86_64:
  "_main", referenced from:
     implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

yes, abc created, and its size is 9.2M
I wrote those code in abc.go  and  run go build -v abc.go,  it turned out:

# command-line-arguments
/usr/local/go/pkg/tool/darwin_arm64/link: running clang failed: exit status 1
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000002.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/go.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000003.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000004.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000006.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000008.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000005.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000007.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000009.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
ld: warning: ignoring file /var/folders/l7/srvfdj8j2rjd1khdn1qd3ydr0000gn/T/go-link-672812621/000010.o, building for macOS-x86_64 but attempting to link with file built for unknown-arm64
Undefined symbols for architecture x86_64:
  "_main", referenced from:
     implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Now the error is the other way:
building for macOS-x86_64 but attempting to link with file built for unknown-arm64

If I search for that error, I end up on e.g. the Go issue, and people are getting these kind of errors if they use Go 1.15 on the new ARM machines.  What does go version say? And go env as well, while we're at it.

Now the error is the other way:
building for macOS-x86_64 but attempting to link with file built for unknown-arm64

If I search for that error, I end up on e.g. the Go issue, and people are getting these kind of errors if they use Go 1.15 on the new ARM machines.  What does go version say?
For C (compile with clang):
#include <stdio.h>

int main() {
	printf("Hello, C!\n");
	return 0;
}

And C++ (compile with clang++):
 #include <iostream>

int main() {
	std::cout << "Hello, C++!" << std::endl;
	return 0;
}

Does that work fine?

How about plain C/C++ compilation?
For C (compile with clang):
#include <stdio.h>

int main() {
	printf("Hello, C!\n");
	return 0;
}

And C++ (compile with clang++):
 #include <iostream>

int main() {
	std::cout << "Hello, C++!" << std::endl;
	return 0;
}

Does that work fine?

Yes, it works fine! the previous c code produced a.out of 48K size, and c++ code produced a.out of 55K size

Yes, it works fine! the previous c code produced a.out of 48K size, and c++ code produced a.out of 55K size

Hmm. And so the toy cgo example arp242 posted above fails?
What if you force-rebuild everything with -a (and pass -x to see what it's actually doing...)? i.e. go build -a -x abc.go

Hmm. And so the toy cgo example arp242 posted above fails?
What if you force-rebuild everything with -a (and pass -x to see what it's actually doing...)? i.e. go build -a -x abc.go

clang --version prints
Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
Target: arm64-apple-darwin20.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

go build -a -x abc.go prints lot of things, and finally succeed and produced a 2.1M size file

clang --version prints
Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
Target: arm64-apple-darwin20.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

go build -a -x abc.go prints lot of things, and finally succeed and produced a 2.1M size file

Right. Well, next step would be to try go get -u -v -a -x github.com/mattn/go-sqlite3 again, then.

Right. Well, next step would be to try go get -u -v -a -x github.com/mattn/go-sqlite3 again, then.

yes, it works, but it doesn't produce go-sqlite3 executable file. And I also tried env CGO_ENABLED=1  go get -v -a -x github.com/rubenv/sql-migrate/sql-migrate and it also works and produced sql-migrate executable file.
Although I still have no sense of what happened. But I am really appreciated.

yes, it works, but it doesn't produce go-sqlite3 executable file. And I also tried env CGO_ENABLED=1  go get -v -a -x github.com/rubenv/sql-migrate/sql-migrate and it also works and produced sql-migrate executable file.
Although I still have no sense of what happened. But I am really appreciated.

Ah, good to hear!
go-sqlite3 is a library, not a standalone program, so it won't produce a go-sqlite3 executable.
Not sure what happened: my guess is something broken in your build cache (so fixed by doing -a). Otherwise maybe something to do with how the go-sqlite3 dependency was pulled when trying to install sqli-migrate directly? Anyway, glad it works now (I might be tempted to switch to the M1 at some point... ehehe ;) ).

Ah, good to hear!
go-sqlite3 is a library, not a standalone program, so it won't produce a go-sqlite3 executable.
Not sure what happened: my guess is something broken in your build cache (so fixed by doing -a). Otherwise maybe something to do with how the go-sqlite3 dependency was pulled when trying to install sqli-migrate directly? Anyway, glad it works now (I might be tempted to switch to the M1 at some point... ehehe ;) ).

(P.S. You should probably close the issue if your problem is resolved.)

(P.S. You should probably close the issue if your problem is resolved.)

Really appreciate your help, I will close it.

Really appreciate your help, I will close it.


a11y: SfAccordion - fix semantics, add v-focus

Related issue

#960
Scope of work

add v-focus to SfAccordionItems and chevrons
change div to button, add aria-pressed

Screenshots of visual changes

Checklist

[x] No commented blocks of code left
[x] Run tests and docs
[x] Self code-reviewed

If applicable:

[ ] I followed composition rules for my component
[ ] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)
[ ] I accept Individual Contributor License Agreement

nice @martaradziszewska


fix(web): git subtree pull @ovh-ux/manager/web

git subtree pull --prefix=packages/manager/apps/web git@github.com:ovh-ux/ovh-manager-web.git develop --squash
some conflicts were resolved by hand

Hello @frenautvh,
Your pull request is now closed due to inactivity.
Feel free to re-open it if you have any update.
Anna Bot for OVH UX <3


Super Tabs Titles Changing Order on *ngIF attribute

Hi,
I'm having an issue where after I add an *ngIF attribute to a super tab element, the order of the titles on the pages switches.
Code:
<ion-content class="profileSuperTabs profileContent" no-bounce (swipe)="closeGroupProfile($event,null)">
  <super-tabs [ngClass]="{'halves': group['events'].length == 0 && hasNewsFeed, 'single': group['events'].length == 0 && !hasNewsFeed}" (tabSelect)="onTabSelect($event)">
    <super-tab [root]="groupInfoPage" [rootParams]="feedData" title="FEED" *ngIf="hasNewsFeed"></super-tab>
    <super-tab [root]="groupInfoPage" [rootParams]="aboutData" title="ABOUT"></super-tab>
  </super-tabs>
</ion-content>

Ideally, the ABOUT tab should show up second and on the right. However, instead I am getting the ABOUT tab first with the newsfeed html underneath, and the FEED tab second, with the about html underneath. If I remove the *nfIF, then it behaves properly, however I need it because some things don't have a feed

Once the super-tabs component is rendered, you cannot alter the child super-tab components. This is related to some other issues that are mentioned here.
There are no plans yet to implement this. For now, gather all the data you need before rendering super-tabs. This means that you need to have an ngIf on the super-tabs component that makes sure that you have all the data ready.

Or simply load your data in the single pages! :+1: as I do.


Supporting Eigen & FFTW when STAN_THREADS is enabled

Description:
The FFTW library can be used seamlessly with Eigen and their FFT implementation which makes everything simple to use with Stan. Using FFTW has proven to yield huge speedups in our model.
There is however a problem when using threading. When using fftw in multi-threaded applications, you need to call fftw_make_planner_thread_safe(); once before calling fft().
Which means I need to add
#ifdef EIGEN_FFTW_DEFAULT
    fftw_make_planner_thread_safe();
#endif

in main() of cmdstan.
Do we think this might be worth adding for all users? Or is this too niche?
Current Version:
v2.33.1

I would be in favor of this. I think you'd want the condition to actually be #if defined EIGEN_FFTW_DEFAULT && defined STAN_THREADS.
I'm curious about your application that got faster - I had previously tried to use FFTW for a problem which required a 2-D fft, but that was not much faster in Stan-Math because Eigen (as of 3.4, anyway) only exposes a 1-D FFT function, so our 2-D FFTs are just loops still.

@rok-cesnovar would it make more sense for this to be in stan::math::init_threadpool_tbb()?

Hmm, I think you are right, because that way its not limited to cmdstan only. Will move to math.


Dependency updates

Please have a look at the individual commit messages for the details.

Merging despite the failing VcsHostTest which is unrelated and gets fixed by https://github.com/oss-review-toolkit/ort/pull/2947.


feat(cw logs identifier): add config

allow disabling log tracing

:tada: This PR is included in version 1.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Sliding nav bar items

Sliding Nav Bar Items
Matching sfai.org 's navbars on hover!
Related PRs
None
Migrations
None
Tests Performed, Edge Cases
None
Screenshots

CC: @by-co

Included dropdown menus sliding down!

sorry did not mean to close it


qc on pipeline derivatives

[x] re-run 4 scans from BNU3 (2 failed 2 succeeded)
[x] debug differences
[x] identify where things go wrong
[ ] fix?

Reporting here for clarity. Current progress has been identifying source of poor derivatives is the registration between the B0 DTI volume at the MPRAGE volume for several subjects. First pass at fixing was to introduce skull stripping on the MPRAGE volume prior to alignment. This corrected the problem in some scans but introduced the problem in others. Next steps are to investigate datatypes and do a minor parameter sweep of FLIRT, of course seeking the most general solution possible and sticking to linear registration.

Fixed with these lines. I will refactor code in next days/week to be better looking and more modular, but not changing the function until I detect the next bug 😄


Fpart

t is now availabe in Amazon Linux's repos. There is no need to compile fpart from source anymore.
[ec2-user@ip-172-31-94-142 ~]$ cat /etc/os-release
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
[ec2-user@ip-172-31-94-142 ~]$ sudo yum info fpart
Loaded plugins: priorities, update-motd, upgrade-helper
Available Packages
Name        : fpart
Arch        : x86_64
Version     : 1.0.0
Release     : 1.0.amzn1
Size        : 45 k
Repo        : amzn-updates/latest
Summary     : Fpart is a tool that sorts files and packs them into bags.
URL         : http://contribs.martymac.org
License     : BSD
Description : Fpart is a tool that helps you sort file trees and pack them into bags (called
: "partitions"). It is developped in C and available under the BSD license.
:
: It splits a list of directories and file trees into a certain number of
: partitions, trying to produce partitions with the same size and number of
: files. It can also produce partitions with a given number of files or a limited
: siz

Thanks for opening the pull request. We have created a backlog ticket to track this request.

updated with v1.3.1


Should the validation layer be enabled by default in debug mode?

If so, the [HPP]Instance constructor would require a minor change in one line:
#ifdef VKB_VALIDATION_LAYERS    ->    #if defined(VKB_DEBUG) || defined(VKB_VALIDATION_LAYERS)

Good question. Tbh I'd prefer them not being active by default in debug mode. I usually also don't use the validation build flag, but just start vkconfig and enable validation whenever I need it.

I think there's value in not requiring debug mode use validation enabled.  The main reason is when we work on extensions that haven't had the VUID changes merged all the way out ahead of a SDK release it would cause an issue as is the case for the mesh shader.  Still having the ability to debug / hit breakpoints when validation hasn't yet promoted is quite useful.

@SaschaWillems Any reason why you prefer them not being active by default in debug mode?
@gpx1000 Agreed, when working on samples ahead of the validation layer, you need to disable it. But I think, that's the exceptional case where you could explicitly disable it. Most of the code here is probably covered well by that layer.
After all, I think, having the validation layer on by default in debug mode catches issues before you can think about it. So you can't easily miss them.

It's mostly a personal taste. I rarely use the VKB_VALIDATION_LAYERS as toggling it requires an almost full rebuilt. I just prefer to never enable validation in the samples itself but rather fire up VkConfig and enable all validation settings in there.

I mean... is there any reason (besides the exceptional case when the sample is ahead of the validation layer) to not enable the validation layer in debug mode?
If it depends on debug mode, you don't have to set VKB_VALIDATION_LAYERS for that case.

Yeah, that's the most obvious reason. If we were to force validation in the debug build, people working on advanced samples where validation is causing problems would have a hard time.
But while we're at the topic: In my samples I choose a completely different way. Validation is enabled at runtime using an argument. Maybe that would be an option for this repo too? Toggling validation using a cmake flag always felt odd for me.

As discussed today we also need to think of Android when doing this. Layers may be pretty outdated on Android devices so and may break with more recent samples. So we need to carefully evaluate this change.

Another thing we need to take into account: Developing new samples for extensions that don't have proper validation layer support. If we were to always enable validation in debug mode, developing such samples would not be possible without manual changes. Not sure if we want that.

I think, this can be closed as resolved with the current state.


Default option of importReact is not aligned with the documentation

When I look at the following line (default: ...):
      'import-react': {
        alias: 'importReact',
        type: 'boolean',
        default: tsConfig?.compilerOptions?.jsx ? !/^react-jsx/.test(tsConfig.compilerOptions.jsx) : true,
        desc: 'Whether to import React.'
      },

and the description in the wiki:

Command-line usage: --import-react
Type: boolean
Default: true if the CLI manages to find a tsconfig.json file and it has a jsx field under compilerOptions with react-jsx or react-jsxdev as the value. false otherwise.

I have the impression that the default value is just the opposite. Shouldn't it be as follows or am I missing something?

        default: tsConfig?.compilerOptions?.jsx ? /^react-jsx/.test(tsConfig.compilerOptions.jsx) : false,

Thanks!

Hi @potob!
You're correct - the two were not aligned. Thanks for bring that to my attention!
The code logic is correct (importReact should be true unless the new JSX transform is detected), the error was in the docs.
I've corrected the error in the docs, and also tweaked the wording in a way that's hopefully clearer. Can you take a look? (link, for your convenience).
Again, thanks a lot for reaching out!

Hi @NitzanHen
Thanks for your quick reply.
Yes that looks better now and also makes more sense 👍🏼


Test/Document/Support running builds behind http proxies

Document which settings need to be changed

In Docker (for pulling base images from docker hub)
Containers (for apt-get etc) - env variables?
Git
Maven
npm

Might need to support overriding config for some of these (similar to maven)

Need to test, but it should just work if Docker client is correctly configured, according to this:
https://docs.docker.com/network/proxy/


Better Run Script

The current run script is confusing:
Specifically, it makes assumptions that aren't explicitly mentioned (i.e. requires Homebrew) and assumes a specific directory structure.
This PR helps fix this through better inline comments and explicit OUTPUT_FILE and INPUT_DIR variables.
BTW -- I really like the approach you've taken in generating mocks; I'm still struggling to get Cuckoo Generator to create correct mocks, but I think this is a step in the right direction.
Thanks for sharing and open sourcing this! :+1:

Thanks! I recently found out that there are Input files and Output files settings in the Run script phase so I would like to update CuckooGenerator to support input/output via that as well.
I would also like to add the script itself into the root of this project, so that it will work like fabric's run script (you just run $PODS_ROOT/Fabric/run or something). That script would download latest CuckooGenerator binary from the github via HTTP so there will be no need for brew.
What do you think?

You said you are struggling with the generation. What seems to be the problem?

I would also like to add the script itself into the root of this project

I really like this idea! However, one issue that I might anticipate would be if someone used nonstandard naming or paths. E.g. named their tests something other than "ProjectNameTests." Perhaps, they could set some variable to be used in this case instead? Perhaps something like CustomTestProjectPath?

You would still give the script necessary arguments so that wouldn't be a problem. It would just make it one line Run script phase instead of this monster one, so users won't need to know what it does behind the curtains :)

You said you are struggling with the generation. What seems to be the problem?

After figuring out how the paths work (which is something I tried to address/make easier with this PR), I've been able to get a mock to be generated.
However, it has several syntax errors. Is Cuckoo Generator generating for an older version of Swift? I.e. not Swift 2?

You would still give the script necessary arguments so that wouldn't be a problem.

Sounds great to me!

However, it has several syntax errors. Is Cuckoo Generator generating for an older version of Swift? I.e. not Swift 2?

The generator should output Swift 2.1 compatible code. Could you send me what syntax errors do you get?

Could you send me what syntax errors do you get?

I'll try to reproduce in a dummy project and open as an issue under Cuckoo Generator. Cool?

Awesome, thanks!

:heart:

Cool, thanks :+1:

I just started Slackin on our server so you can join SwiftKit team on Slack through http://swiftkit.tmspark.com/ to chat about your issue :)

There was a but in the latest version of Slackin so it was not working. Fixed now :)


LineageRunner to handle tables with dots

If we have a query such as:
SELECT
  snow_t1.C_NAME
FROM "PU.BLIC".SNOW_T1
;

LineageRunner will tell us that the table name is pu.blic.snow_t1, which we will interpret as db.schema.table.
We should take a look at the libs source code and fix this

before jumping into this, while we support the dot notation in the FQN we should consider if the effort is worth it based on impact. Adding you folks for visibility, but not top priority

closing this , lets re-open if its a common issue


New version: strimio.strimio version 3.0.4

Result: Installation Failed

Manifest
Add/Remove Programs

Name
Strimio

Version
3.0.4

Publisher
Strimio

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 3231
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


WebShade hiding black pieces in chess apps and websites

Noticed WebShade has the side-effect that it also removes the black pieces from any chess websites and apps.

Link to lichess example site
I understand the program is working as expected, however I still feel like a blacklist settings is evident.

Hello there.
A blacklist setting would be a lot of work and to be honest with you I don't want to go through with that.
You can however try these;
If your chess app is its own app (which the screenshot seems to suggest it is) disable the tweak injecting into your app via choicy.
If your chess game is part of a website you can disable light mode on your phone which should return the chess site back to its previous state.
If you (or anyone really) wanted to make a pr to add preferences I wouldn't be opposed to merging it. However, I don't really want to go through the effort myself. Sorry

Completely understandable, thank you for your work, candor, and your suggestion. I'll definitely be looking into Choicy.


🚧 Implement start/stop player

Description
The main purpose of this pull request is to keep the current user in sync with the owner of a session they are a listener in.
Test Plan
npm test app/actions/player/StartPlayer/

npm test app/actions/player/StopPlayer/

Motivation and Context
Now that the current user is able to join the session of another user in the app, we need everyone to be in sync with each other. This will help start/stop the player as the owner of the session is doing it for themselves. This will work for when the current user is joining a session, when the owner of the session happens to seek to a new position, and even when the owner plays a new track.
How Has This Been Tested?
Thus far, the synchronous action creators and the reducer case functions have their unit tests passing. I've tested manually as well by joining sessions in a multitude of ways, as well as interacting inside of the session itself.
Screenshots (if appropriate)
N/A
Types of Changes

Documentation
Bug fix
New feature
Breaking change

Bug Fixes
N/A
Checklist

[x] My code follows the code style of this project
[x] My change requires tests to be written
[x] I have written the tests necessary for my code
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly

 Implement start player

 Implement stop player


New project structure

Overview

This is a base branch that represents the next structure:
exonum-java-parent
|
 - exonum-java-binding-parent
    |
     - exonum-java-binding-common
   .....

It will be used as a base branch to merge into small separated changes.
Definition of Done

[ ] There is no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 85.666% when pulling 69bbdc4a2baea41763e5633a22fb269ab4288b3b on project-new-structure into 63411f2e1081e8f37f0340f271fa9002af20df90 on master.

@dmitry-timofeev in #680


Correct indent in Apache-2.0 template

see https://www.apache.org/licenses/LICENSE-2.0

Aha. I need to update test cases accordingly.


Make ALKiln action work on tags

Example of failing test: https://github.com/SuffolkLITLab/docassemble-ALAffidavitOfIndigency/actions/runs/6125747748/job/16628337375.
It looks like we manually ignore tags and don't run workflows on tags in our other repos, but that bit isn't in our suggested workflow example.
This should be an easy fix though, and we could make it in a few places.

in action.yml: if we used github.ref_name instead of the current github.ref, we'd get

The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on GitHub. For example, feature-branch-1.

This is exactly what docassemble wants. Not sure why it does'n't work with the full version, but it doesn't.

a more hacky change with a smaller scope would be to include refs/tags/ in https://github.com/SuffolkLITLab/ALKiln/blob/4625d58a58565c96edfe0fc6be8ad586a0156a2d/lib/utils/session_vars.js#L81
I can confirm manually that telling docassemble the tag name works:
ALKiln debug: Stored name of Project "ALKilnTestdocassembleALAffidavitOfIndigencyv2121694202276108" locally.
ALKiln : Trying to pull code from the "v2.1.2" branch.
ALKiln debug: Project name from file is "ALKilnTestdocassembleALAffidavitOfIndigencyv2121694202276108".
ALKiln : Your Docassemble server finished pulling the package's code.
ALKiln setup: Success! Test setup has finished successfully.

Was this closed by https://github.com/SuffolkLITLab/ALKiln/pull/823 with #760?


[Add] the new resources from YouTube for react.js

Site URL
https://youtu.be/4UZrsTqkcW4
Description of the above provided site
This is the FreeCodeCamp react course on YouTube. This is the most viewed and also I learn the react from it.
In this video, all the basic topics of react has been covered and also helpful to the beginner to get started in the world of react.
Category
Frontend
Sub Category
React.js
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@Parmesh119 Are you still working on the issue?

@Parmesh119 closing this as no responses received , if you still want to work and deliver the things quick i will reopen it again, just tag me :)


Integrate the new AI NPC into Blue Sector

Import package and resolve issues, and ensure that nothing breaks.

Current progress:

Imported Whisper.Unity into the project.
Made sure all non AI NPC functionality is not broken.
All AI NPC functionality is working, but transcription is very slow when running natively on Quest2/3
Made transcription subtitles display properly, almost all the time.
Future work:
We need to figure out a solution for authentication for using Open AI's API
Completely fix transcription subtitle graphics.
Make a timer to show how much time the user has left to talk.
Make microphone access prompt appear at the start of the app.


Git Ship: Disallow the default commit message

When shipping, the default commit message almost never makes sense. When using Git Town, it often reads like
Squashed commit of the following:
commit 1c0c837520d5671b59130bbfd8a2020dea58e20e
Merge: e4a56b3 4be83e3
Author: Nir Shtuhl<EMAIL_ADDRESS>Date:   Wed Feb 18 11:25:40 2015 -0800

    Merge branch 'master' into change-docs-to-biscotto

commit e4a56b3
Author: Nir Shtuhl<EMAIL_ADDRESS>Date:   Wed Feb 18 10:13:36 2015 -0800

    update documentation to Biscotto

Git Town should reject the ship if the default commit message is provided.

@rschifflin and I were just talking about this. Seems like this could be solved by having a hook that comments out the default message. Unless the "allow-empty-commit" flag is used, the commit will be rejected if the commit message is empty. Users will be able to see the messages from their previous commits, but will be forced to author a meaningful summary message.

http://stackoverflow.com/questions/3966714/how-can-i-change-the-default-comments-in-the-git-commit-message


Improvement: Add TimeZone Support

It would be much more comfortable for the users to have their own TimeZone Setting in "Edit Profile" page. For an eg. different people are working in 2 separate TimeZones.

Hi @tpetrauskas, Thanks for the suggestion.
I'd much prefer to avoid having a setting for this but instead ensure the system localises any shown times automatically without the user having to set anything. I believe the only time shown is the draft update time which, As of the release of v0.9.0, is now localised. Let me know if you come across any other non-localized times and I will update accordingly.

My server has set as UTC+8 TZ but I see UTC time stored in the database and shown as UTC time instead of UTC+8... Do I need to change APP ENV or other things to get UTC+8 display time? My PC is also in +8 TZ.


Remove commons-io dependency

Description
Removes the only usage of commons-io's FileUtils, replacing it with a native Java implementation.
Closes #203.
Checklist
The following items should be checked before the pull request can be merged.

[ ] Unit tests added.
[x] Code follows existing code format.

Imo it's not worth justifying an entire dependency for a single method that's easily replaced. I can add a comment stating what it does but it's functionally the same without a substantial amount of extra code, if really any at all.


Wrong endpoints

Endpoints looks like 'https://fcm.googleapis.com/fcm/send/...', but $report->getEndpoint() returns 'https://fcm.googleapis.com/wp/...'.
What is the reason?
foreach ($this->webPush->flush($batch) as $report) {     $endpoint = $report->getEndpoint(); }

I'm also facing this problem, no idea why.

See https://github.com/web-push-libs/web-push-php/pull/214
If this should still be replaced, we'll update the doc


DCTL failed to run egdb.database test on release and debug configuration with MSVC on Windows

DCTL failed to run egdb.database test on release and debug configuration with MSVC on Windows. It can be reproduced on  master branch latest reversion a63d2a3. Could you help take a look at this? Thanks a lot.
Repro steps:

git clone https://github.com/rhalbersma/dctl.git D:\DCTL\src
open a VS 2017 amd64 command prompt as admin and browse to D:\DCTL
git clone https://github.com/rhalbersma/xstd.git D:\DCTL\xstd
git clone https://github.com/rhalbersma/bit_set.git D:\DCTL\bit_set
put boost_1_69_0 under C:\boost_1_69_0\x64
cmake -G "Visual Studio 15 2017 Win64" -DCMAKE_SYSTEM_VERSION=10.0.17134.0 -DBOOST_ROOT=C:\boost_1_69_0\x64\boost -DBOOST_INCLUDEDIR=C:\boost_1_69_0\x64 ..\src\
msbuild /m /p:Configuration=Release;Platform=x64 dctl.sln /t:Rebuild
ctest --build-config Release -E "egdb.divide|search|traversal"

log_x64_test.log
Failures:
Start 35: egdb.database
35/37 Test #35: egdb.database ........................Exit code 0xc0000135
***Exception:   0.05 sec
Start 36: egdb.index
36/37 Test #36: egdb.index ...........................   Passed    0.34 sec
Start 37: util.literals
37/37 Test #37: util.literals ........................   Passed    0.05 sec
97% tests passed, 1 tests failed out of 37
Total Test time (real) =   2.87 sec
The following tests FAILED:
35 - egdb.database (Exit code 0xc0000135
)

Can you show the first few lines of the compilation? E.g. on AppVeyor I get this for VS 2017:
cmake .. -G "%GENERATOR_NAME%" -A %PLATFORM_NAME% "-DCMAKE_TOOLCHAIN_FILE=c:/tools/vcpkg/scripts/buildsystems/vcpkg.cmake"
-- The CXX compiler identification is MSVC 19.16.27034.0
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x86/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Boost: C:/Tools/vcpkg/installed/x86-windows/include (found version "1.71.0") found components:  filesystem
-- Found Boost: C:/Tools/vcpkg/installed/x86-windows/include (found version "1.71.0") found components:  unit_test_framework
-- Configuring done
-- Generating done
-- Build files have been written to: C:/projects/dctl/build
cmake --build . --config %configuration%
Microsoft (R) Build Engine version 15.9.21+g9802d43bc3 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

In particular, on AppVeyor I cannot reproduce your build as VS 2017 errors out on tons of constexpr related bugs. The VS 2019 build job works correctly. Could you try with VS 2019?

I now added a catch(...) clause to catch all non-filesystem related exceptions. Could you run your compilation again please?

Hi rhalbersma,
Thanks for your reply!
We mainly build open source projects to test the VS compiler. We use vs2017, but replace the vs2017 binary with the 2019 vs binary that has not yet been released.
And now this issue still can be reproduced on latest version 991e87c, so I attached log_x64_cmake.log log_x64_build.log and log_x64_test.log for you.  Thanks a lot.
log_x64_cmake.log
log_x64_build.log
log_x64_test.log
Thanks,
Lin

Your build config uses Boost 1.69 and has 86 warnings from Boost.Hana. This is known to be a library with fragile Visual C++ support. In my build using VS 2019 on AppVeyor, I use Boost 1.71 and get 0 warnings. I also suspect that the the 1.69 version of Boost.Filesystem is somehow not working correctly (although the catch(...) clause should catch all exceptions). Can you rebuild with the Boost version from vcpkg?

As I can't reproduce it, I'm closing this. Feel feel to re-open if you reproduce your errors with the AppVeyor build stack (VS 2019 16.4, Boost 1.71.0). Note that I've now also phased out Boost.FileSystem in lieu of <filesystem>.


optimize: logger class miswrite

Ⅰ. bugfix : logger class miswrite
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
clearly
Ⅴ. Special notes for reviews

Codecov Report

Merging #2749 into develop will decrease coverage by 0.13%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #2749      +/-   ##
=============================================
- Coverage      50.89%   50.75%   -0.14%
  Complexity      2849     2849
=============================================
  Files            567      567
  Lines          18172    18153      -19
  Branches        2166     2127      -39
=============================================
- Hits            9249     9214      -35
+ Misses          8029     8023       -6
- Partials         894      916      +22

Impacted Files
Coverage Δ
Complexity Δ

...octrl/process/impl/CustomizeBusinessProcessor.java
53.12% <100.00%> (ø)
7.00 <1.00> (ø)

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
3.00% <0.00%> (ø%)

...otobuf/convertor/BranchReportRequestConvertor.java
90.90% <0.00%> (-9.10%)
3.00% <0.00%> (ø%)

...obuf/convertor/BranchRollbackRequestConvertor.java
92.00% <0.00%> (-8.00%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
3.00% <0.00%> (ø%)

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
3.00% <0.00%> (ø%)

... and 20 more

please relation github username and email.


[FLINK-19485] Decouple runtime operator implementation from DataStream operations

What is the purpose of the change
Although DataStream is going to be the unified API for Batch and Streaming applications (see FLIP-134 ) , some operations, e.g. Sinks, may need to have different runtime implementations depending on if they are intended to run on bounded or unbounded data. This is not necessarily only for optimisations but also for the exposed semantics, i.e. correctness.
So far, DataStream had a 1-to-1 mapping between an API call and an operator. In a sense, the DataStream API was an "explicit" API. With this addition, we will decouple the API calls from the actual runtime implementations of the operations and thus allow different operations to have more than one runtime implementations, depending (for now) on the execution.runtime-mode.
In this PR we introduce the StreamGraphTranslator interface, which is the main new entity responsible for translating a Transformation into its runtime implementation, the framework based on which a developer can write a StreamGraphTranslator for a new Transformation and wire it to the StreamGraphGenerator and an example implementation for the OneInputTransformation.
Brief change log
The changes are mainly in the StreamGraphGenerator and the addition of the StreamGraphTranslator/BaseSimpleTransformationTranslator/OneInputTranslator.
Verifying this change
With the addition of the new OneInputTranslator, all existing tests (including e2e tests) using an OneInputTransformation also verify the changes in this PR.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

NOTE: I would also like to move the streaming.api.graph to a new streaming.runtime.graph package as this seems more "correct" but this will fail because if we move the StreamGraph, then we will break binary compatibility because of the LocalStreamEnvironment.execute(streamGraph) and RemoteStreamEnvironment.execute(streamGraph).

Thanks for the reviews @aljoscha and @dawidwys ! I integrated them and rebased. Let me know if you have any more comments and if not, I will merge.

Merging.


Adding get_language route and tests

Followed same pattern as get_category route to set up the get_language route and added tests for getting a single language by ID and testing for out of bounds languages.
Tested retrieving a single language on Postman successfully.

Fixes #197


RSpec-rails + Erector

Hey all,
Trying to get erector views loaded into a view spec similarly to the way haml works with rspec-rails. Doesn't seem to be working:
describe "welcome/sign_up.rb" do
  it "renders the html5 doctype" do
    render
    rendered.should be_starts_with('<!DOCTYPE html>')
  end
end

The error we get is:
NameError: undefined local variable or method `render' for #<RSpec::Core::ExampleGroup::Nested_1:0x007fe5ea5a6c70>
/Users/abhik/.rvm/gems/ruby-1.9.2-p290@cbt/gems/rspec-expectations-2.7.0/lib/rspec/matchers/method_missing.rb:9:in `method_missing'

Is there a standard way to test Erector views? Should we be using rspec-rails?
Abhik

Maybe you need to specify type?
describe "welcome/sign_up.rb", :type => :view do


Can create SPI wave in nano seconds resolution？

I use ADS8688A with the 500kSPS. It need 64 clock time per sample. However, the pigpio library use 1us as the min clock time. The max speed I can achieved is (1000 / 64) kSPS, which is much smaller than 500.
So how can modify the SPI clock to 10ns  or 100ns ?

The hardware SPI supports a baud rate maximum of 32M.

The hardware SPI supports a baud rate maximum of 32M.

Yes. But when use rawWaveAddSPI ,  the parameter's rawSPI_t's clk_us min value is 1us. This limit the clock frequency to 1M. Any workaround to improve the Wave frequency?
@guymcswain This blocking me too much time. Will be ery appreciate for your help!

The construction of output waveforms is limited to 1 microsecond timing.  Ie, the fastest square waveform you can generate is  500 KHz.

The construction of output waveforms is limited to 1 microsecond timing. Ie, the fastest square waveform you can generate is 500 KHz.

Is it possible to improve the waveforms' CLK timing to nano seconds?

No.  Waveforms are controlled by DMA.  To try to make it run sub microseconds would be futile as that would create excessive bus traffic interfering with normal activity.
Why do you not use the hardware SPI peripheral which is intended for such purposes?

@guymcswain  I use RPI to do this because it need no other devices and I saw that the clocks can achieve 100MHz or higher for RPI peripheral. So I want to test the max ablity of the speed.
@guymcswain  You said hardware SPI peripheral, did you mean using FPGA DAQ card, like NI Corporation's?

RPi is made up of many peripherals.  The 100MHz rate you mention is only achievable in certain Gpio pins via the Clock peripheral.  When I mentioned the SPI peripheral I am referring to the APIs:  spiOpen, spiTransfer, spiClose.

@guymcswain Thanks for your patience.  I need to monitor the signal continuously without time gap between two data acquest. I tried spiOpen, spiXfer (I didn't found spiTransfer API), spiClose. But there is a dubious time gap between two spiXfer invoking. I think the System schedule to do other things in the time gap. Is there any workaround to avoid that?

@guymcswain If I want to streaming the input data without andy gaps, can I use spiXfer to achieve this?