TransactionLookup get stuck - Long-lived read transaction has been timed out open_duration

Describe the bug
Scenario:

I have started to sync a few days ago. the process is stuck on TransactionLookup.
There is no progress, and reth process CPU seem pretty idle.
I have 4.5 TiB, 8 CPU cores and 64 GiB of RAM on AWS.

Version
I have started the sync using reth 1.0 rc2 up to (including) the Execution stage. then moved to 1.0 (GA).
Attempts

Killed reth and lighthouse, attempted to refresh
Tried to drop the stage and refresh the processes (kill and re-run)
I have modified the reth.toml to reduce the chunk sizes to notice if it still progresses or silent due to work. but it's been few hours and no report on 500k entries so it seem stuck (also CPU is pretty idle..):

[stages.transaction_lookup]
chunk_size = 500000

I have enable traces.
I tried to run it multiple times, like 5 or 6.

Logs
On first attempts, I see the log progresses on some transaction ranges. it does not get stuck at the same range every time so it's not deterministic in that way.
On some attempts, I see a timeout.
reth_traces.txt
Steps to reproduce
Run sync
Node logs
Usually it starts well and get stuck after some transaction batches:
`
024-06-29T09:03:58.306137Z  INFO reth::cli: Transaction pool initialized
2024-06-29T09:03:58.306781Z  INFO net::peers: Loading saved peers file=/mnt/raid/reth/known-peers.json
2024-06-29T09:03:58.346297Z  INFO reth::cli: StaticFileProducer initialized
2024-06-29T09:03:58.346556Z  INFO reth::cli: Pruner initialized prune_config=PruneConfig { block_interval: 5, segments: PruneModes { sender_recovery: None, transaction_lookup: None, receipts: None, account_history: None, storage_history: None, receipts_log_filter: ReceiptsLogPruneConfig({}) } }
2024-06-29T09:03:58.346750Z  INFO reth::cli: Consensus engine initialized
2024-06-29T09:03:58.346781Z  INFO reth::cli: Engine API handler initialized
2024-06-29T09:03:58.348813Z  INFO reth::cli: RPC auth server started url=<IP_ADDRESS>:8551
2024-06-29T09:03:58.348832Z  INFO reth::cli: RPC IPC server started path=/tmp/reth.ipc
2024-06-29T09:03:58.348855Z  INFO reth::cli: RPC HTTP server started url=<IP_ADDRESS>:8545
2024-06-29T09:03:58.348860Z  INFO reth::cli: RPC WS server started url=<IP_ADDRESS>:8546
2024-06-29T09:03:58.348869Z  INFO reth::cli: Starting consensus engine
2024-06-29T09:03:58.349382Z  INFO reth_node_events::node: Preparing stage pipeline_stages=1/12 stage=Headers checkpoint=20153551 target=None
2024-06-29T09:03:58.349389Z  INFO sync::stages::headers: Target block already reached checkpoint=20153551 target=Hash(0xfb03b489f5158dc9c3ff4eb83181c6e0aba4da9f5356da81c9ae84f508bc1af9)
2024-06-29T09:03:58.349418Z  INFO reth_node_events::node: Executing stage pipeline_stages=1/12 stage=Headers checkpoint=20153551 target=None
2024-06-29T09:03:58.349445Z  INFO reth_node_events::node: Finished stage pipeline_stages=1/12 stage=Headers checkpoint=20153551 target=None stage_progress=100.00%
2024-06-29T09:03:58.349492Z  INFO reth_node_events::node: Preparing stage pipeline_stages=2/12 stage=Bodies checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349503Z  INFO reth_node_events::node: Executing stage pipeline_stages=2/12 stage=Bodies checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349512Z  INFO reth_node_events::node: Finished stage pipeline_stages=2/12 stage=Bodies checkpoint=20153551 target=20153551 stage_progress=100.00%
2024-06-29T09:03:58.349554Z  INFO reth_node_events::node: Preparing stage pipeline_stages=3/12 stage=SenderRecovery checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349566Z  INFO reth_node_events::node: Executing stage pipeline_stages=3/12 stage=SenderRecovery checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349577Z  INFO reth_node_events::node: Finished stage pipeline_stages=3/12 stage=SenderRecovery checkpoint=20153551 target=20153551 stage_progress=100.00%
2024-06-29T09:03:58.349617Z  INFO reth_node_events::node: Preparing stage pipeline_stages=4/12 stage=Execution checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349628Z  INFO reth_node_events::node: Executing stage pipeline_stages=4/12 stage=Execution checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349642Z  INFO reth_node_events::node: Finished stage pipeline_stages=4/12 stage=Execution checkpoint=20153551 target=20153551 stage_progress=100.00%
2024-06-29T09:03:58.349684Z  INFO reth_node_events::node: Preparing stage pipeline_stages=5/12 stage=MerkleUnwind checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349693Z  INFO sync::stages::merkle::unwind: Stage is always skipped
2024-06-29T09:03:58.349695Z  INFO reth_node_events::node: Executing stage pipeline_stages=5/12 stage=MerkleUnwind checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349705Z  INFO reth_node_events::node: Finished stage pipeline_stages=5/12 stage=MerkleUnwind checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349750Z  INFO reth_node_events::node: Preparing stage pipeline_stages=6/12 stage=AccountHashing checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349764Z  INFO reth_node_events::node: Executing stage pipeline_stages=6/12 stage=AccountHashing checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349777Z  INFO reth_node_events::node: Finished stage pipeline_stages=6/12 stage=AccountHashing checkpoint=20153551 target=20153551 stage_progress=100.00%
2024-06-29T09:03:58.349822Z  INFO reth_node_events::node: Preparing stage pipeline_stages=7/12 stage=StorageHashing checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349850Z  INFO reth_node_events::node: Executing stage pipeline_stages=7/12 stage=StorageHashing checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349859Z  INFO reth_node_events::node: Finished stage pipeline_stages=7/12 stage=StorageHashing checkpoint=20153551 target=20153551 stage_progress=100.00%
2024-06-29T09:03:58.349901Z  INFO reth_node_events::node: Preparing stage pipeline_stages=8/12 stage=MerkleExecute checkpoint=20153551 target=20153551
2024-06-29T09:03:58.349912Z  INFO reth_node_events::node: Executing stage pipeline_stages=8/12 stage=MerkleExecute checkpoint=20153551 target=20153551
2024-06-29T09:03:58.350603Z  INFO reth_node_events::node: Finished stage pipeline_stages=8/12 stage=MerkleExecute checkpoint=20153551 target=20153551 stage_progress=100.00%
2024-06-29T09:03:58.350650Z  INFO reth_node_events::node: Preparing stage pipeline_stages=9/12 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:03:58.350664Z  INFO sync::stages::transaction_lookup: Updating transaction lookup tx_range=0..=20153551
2024-06-29T09:03:58.350665Z  INFO reth_node_events::node: Executing stage pipeline_stages=9/12 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:03:58.353539Z  INFO sync::stages::transaction_lookup: Calculating transaction hashes tx_range=0..500004
2024-06-29T09:03:58.628738Z  INFO sync::stages::transaction_lookup: Calculating transaction hashes tx_range=500004..1000008
2024-06-29T09:03:58.799806Z  INFO sync::stages::transaction_lookup: Calculating transaction hashes tx_range=1000008..1500013
2024-06-29T09:03:58.948613Z  INFO sync::stages::transaction_lookup: Calculating transaction hashes tx_range=1500013..2000043
2024-06-29T09:04:01.347425Z  INFO reth::cli: Status connected_peers=0 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:04:26.347479Z  INFO reth::cli: Status connected_peers=4 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:04:51.348131Z  INFO reth::cli: Status connected_peers=5 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:05:16.347786Z  INFO reth::cli: Status connected_peers=11 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:05:29.122925Z  INFO reth_node_events::node: Received forkchoice updated message when syncing head_block_hash=0x42dfcc859705f022b1f27501dd49ecaaba447e23c55e58c22d48a63c8617b2a0 safe_block_hash=0xb7b46e8a6b5cd5fa8b2e1ac084f4dda23c1c1d959e1c477d2d0932f0dc5bacbb finalized_block_hash=0x5aa17c903ae6c7247037a05be6a16c6c3987919d462669e8f8df675c10b0422b
2024-06-29T09:05:41.348024Z  INFO reth::cli: Status connected_peers=19 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:06:06.347783Z  INFO reth::cli: Status connected_peers=25 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:06:31.348221Z  INFO reth::cli: Status connected_peers=29 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:06:56.348128Z  INFO reth::cli: Status connected_peers=30 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:07:21.347629Z  INFO reth::cli: Status connected_peers=36 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:07:46.347555Z  INFO reth::cli: Status connected_peers=38 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:08:11.347982Z  INFO reth::cli: Status connected_peers=39 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:08:36.347850Z  INFO reth::cli: Status connected_peers=42 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:09:01.347745Z  INFO reth::cli: Status connected_peers=45 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:09:26.347290Z  INFO reth::cli: Status connected_peers=45 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:09:51.347633Z  INFO reth::cli: Status connected_peers=48 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:10:16.348034Z  INFO reth::cli: Status connected_peers=48 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551
2024-06-29T09:10:41.347647Z  INFO reth::cli: Status connected_peers=50 freelist=20 stage=TransactionLookup checkpoint=0 target=20153551

Platform(s)
Linux (ARM)
What version/commit are you on?
[user@hostname]# ./reth --version
reth Version: 1.0.0
Commit SHA: 31e2470
Build Timestamp: 2024-06-24T10:20:28.659283017Z
Build Features: jemalloc
Build Profile: maxperf
What database version are you on?
[user@hostname]# ./reth db version
2024-06-29T10:59:20.072749Z  INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/mainnet
Current database version: 2
Local database version: 2
Which chain / network are you on?
mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
none
If you've built Reth from source, provide the full command you used
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

Adding gdb thread apply all bt
gdb_bt.txt
It appears that sometimes in some of my re-run attempts, 'cast block-number' is stuck.
It usually returns me 0, but on the attempts with the timeout, it times out as well:
the last one with the trace with the timeout messages
`
[user@hostname]# cast block-number
Error:
error sending request for url (http://localhost:8545/)
Context:

Error #0: error sending request for url (http://localhost:8545/)
Error #1: operation timed out

[user@hostname]# netstat -tulpn |grep 8545
tcp        3      0 <IP_ADDRESS>:8545          <IP_ADDRESS>:*               LISTEN      466703/./reth
`

OK, first thanks in advanced. it seem like it got resolved.
I did multiple attempts as I had to unblock my development, sorry for the RCA was not nailed down.
Overall I did notice I had some files permissions weirdness (since I have executed sometimes reth as root and sometimes as lower priv user, even though I don't think that was the problem, I also tried as root).
I can't point specifically what was the issue, but I did try the below:

Manual attempt of stage run (I have issues with it in the "to" block), so left it.
Drop stage (using --datadir flag)
Reboot the machine, refresh lighthouse and reth processes.

On my last attempt, I got it work when I set 10000 (10k) jumps on this stage:
[stages.transaction_lookup]
chunk_size = 500000

For the first time, I saw this message on this stage:
2024-06-30T11:09:17.145676Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=10.00%
2024-06-30T11:10:52.693843Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=20.00%
2024-06-30T11:12:28.836599Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=30.00%
2024-06-30T11:14:04.413551Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=40.00%
2024-06-30T11:15:41.220433Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=50.00%
2024-06-30T11:17:17.938675Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=60.00%
2024-06-30T11:18:53.909134Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=70.00%
2024-06-30T11:20:30.092529Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=80.00%
2024-06-30T11:22:06.039709Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=90.00%
2024-06-30T11:23:41.815407Z  INFO sync::stages::transaction_lookup: Inserting hashes append_only=true progress=100.00%

And thanks for the efforts, I hope I will get the honor to contribute to the project as well.

I was experiencing the same problem on reth 1.0.0 & Ubuntu Server 22 (x86_64) and the following solved it for me!

[stages.transaction_lookup]
chunk_size = 10000

Thanks @EranAs


Broken link and fixes required for OSBA references

The document refers to OSBA which seems to be no longer maintained by Microsoft. Perhaps this now needs to point to Azure Service Operators.
Additionally the links on setting up word press at the end of the page points to AKS integrate website instead of specific example.
Kindly consider fixing that as well.

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

ID: 6bcc6011-3106-e7fc-ff36-02bd9dcce057
Version Independent ID: 0b5ab39e-cacb-fb6a-0924-cc77028f391e
Content: Connect to Azure Kubernetes Service - Azure Database for MySQL
Content Source: articles/mysql/concepts-aks.md
Service: mysql
GitHub Login: @ajlam
Microsoft Alias: andrela

@kk-src   Thanks for the feedback. We will engage the content development team for further investigation, they will verify and perform necessary changes in the document as needed.
@ajlam Can you please look into this ?

Yep seems like they have switched to the alternative as evidenced here

This project is no longer being maintained by Microsoft. Please refer to https://github.com/Azure/azure-service-operator for an alternate implementation.

Consequently then the Wordpress guide could be removed then, or the page might have to be restored and updated to use ASO.

We are working with on engineering teams to understand the future integration between managed services like Azure DB for MySQL and AKS. No short term fix at the moment, but I will look into how to improve the documentation.

Hi all, our team is removing the OSBA documentation in the short term. We are working with the AKS team to figure out how to proceed.
#please-close


Empty ResultSet And ResultSetLog output Total: 1

it 's very confused，the log tells me that there has one record Total: 1, actually , nothing, the ResultSet is Empty
So i debugged, found this

and this

that's make me crazy, i am read the source code , hope to find the reason, solve my problem.
finally,  i am fixed my problem, it was caused by MySQL high level Driver need specify a serverTimezone
But i wasted too much time on read source code,  and noting help to solve problem
we should fix this, make the log clearly and correctly

Hello @kilowang ,
Please fill out the bug report template.
We need these information to reproduce the problem.
## MyBatis version
3.x.x

## Database vendor and version

## Test case or example project

## Steps to reproduce

## Expected result

## Actual result

And please use text instead of images.

sorry for that, but i am already figure out what happened, there is no need to provide any Test case or example project, just do that like below

prepare a MySQL DB Server (my MySQL Server version is 5.7.29 and 5.6.36 )
create table , empty table is alright

CREATE TABLE `TestTable` (
  `id` int(11) NOT NULL DEFAULT '0',
  `column1` int(11) DEFAULT '0',
  `column2` int(11) DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci

set debug level : DEBUG
and execute query ,

@Select("SELECT SUM(column1),SUM(column2) FROM TestTable WHERE id = #{id}")
Test sum(@Param("id") int id);

and will find  below in log file
==> Parameters: 10(Integer)
<==      Total: 1

but the method sum  return a null Object
the result is true, very correctly, both are correct.
if you execute this query on mysql client directly, will got this
+---------------+----------------+
| SUM(column1)  |  SUM(column2)  |
+---------------+----------------+
|    NULL       |     NULL       |
+---------------+----------------+

yes, we queried one record , so when we enable debug, we got log like this Total: 1, that's true.
private boolean applyAutomaticMappings(ResultSetWrapper rsw, ResultMap resultMap, MetaObject metaObject, String columnPrefix) throws SQLException {
  List<UnMappedColumnAutoMapping> autoMapping = createAutomaticMappings(rsw, resultMap, metaObject, columnPrefix);
  boolean foundValues = false;
  if (!autoMapping.isEmpty()) {
    for (UnMappedColumnAutoMapping mapping : autoMapping) {
      final Object value = mapping.typeHandler.getResult(rsw.getResultSet(), mapping.column);
     //  look here plz
     //  all value is null , so `foundValues` alway be false
     //  look here plz
      if (value != null) {
        foundValues = true;
      }
      if (value != null || (configuration.isCallSettersOnNulls() && !mapping.primitive)) {
        // gcode issue #377, call setter on nulls (value is not 'found')
        metaObject.setValue(mapping.property, value);
      }
    }
  }
 // return false;
  return foundValues;
}

private Object getRowValue(ResultSetWrapper rsw, ResultMap resultMap, String columnPrefix) throws SQLException {
  final ResultLoaderMap lazyLoader = new ResultLoaderMap();
  Object rowValue = createResultObject(rsw, resultMap, lazyLoader, columnPrefix);
  if (rowValue != null && !hasTypeHandlerForResultObject(rsw, resultMap.getType())) {
    final MetaObject metaObject = configuration.newMetaObject(rowValue);
    boolean foundValues = this.useConstructorMappings;
    if (shouldApplyAutomaticMappings(resultMap, false)) {
      foundValues = applyAutomaticMappings(rsw, resultMap, metaObject, columnPrefix) || foundValues;
    }
    foundValues = applyPropertyMappings(rsw, resultMap, metaObject, lazyLoader, columnPrefix) || foundValues;
    foundValues = lazyLoader.size() > 0 || foundValues;
    // look here plz
    // rowValue will be null, and finally return a null
    // look here plz
    rowValue = foundValues || configuration.isReturnInstanceForEmptyRow() ? rowValue : null;
  }
  return rowValue;
}

I agree that 'Total: 1' seems to be the right output.
So, there is no bug to fix and we can close this issue, right?

yeah, it's very hard to say that is a bug and the scenario is rare, i am not  sure if you guys can do something make it clearly - keep ResultSetLog output and Mapper Method returnObj consistent, if Total: 1, return object not null, otherwise null
i know it's not a big deal,  if we do nothing about that , that's ok  !
tell me what's your decision, please

I think you should try enabling returnInstanceForEmptyRow.
The documentation is here:
https://mybatis.org/mybatis-3/configuration.html
Then you will receive an instance of Test instead of null when all columns in the result set are NULL.
This is the behavior you expect, isn't it?

Ok,  i will try enable returnInstanceForEmptyRow ,  and close this issue.  But i still thought that is difference,  enable this configure  is a little trick  :-)

@harawata I want to know why returnInstanceForEmptyRow's default value is false?
I think it's strange for some scenario, such as list contains null element, which will lead to npe probably.

@Alice52
returnInstanceForEmptyRow was added recently (version 3.4.2) and we wanted to keep backward compatibility.
Besides, MyBatis does not add null to a list even if returnInstanceForEmptyRow is not enabled.

@harawata

returnInstanceForEmptyRow was added recently (version 3.4.2) and we wanted to keep backward compatibility.

Yep, I have great understand about default value, thx.

Besides, MyBatis does not add null to a list even if returnInstanceForEmptyRow is not enabled.

It's do will put null value to list in below scenario:

data in database

id
a_column
others columns

1
NULL
...

this is raw SQL:
-- and the response is Entity list, a_column is null value
select a_column from table_a where id=1

then I get the response list, which size is 1 and just have null element in list. [It's more prosible for npe]

I had to search about it by debugging, and get the core logic about handle rowvalue
private Object getRowValue(ResultSetWrapper rsw, ResultMap resultMap, String columnPrefix) throws SQLException {
    final ResultLoaderMap lazyLoader = new ResultLoaderMap();
    Object rowValue = createResultObject(rsw, resultMap, lazyLoader, columnPrefix);
    if (rowValue != null && !hasTypeHandlerForResultObject(rsw, resultMap.getType())) {
        final MetaObject metaObject = configuration.newMetaObject(rowValue);
        boolean foundValues = this.useConstructorMappings;
        if (shouldApplyAutomaticMappings(resultMap, false)) {
            foundValues = applyAutomaticMappings(rsw, resultMap, metaObject, columnPrefix) || foundValues;
        }
        foundValues = applyPropertyMappings(rsw, resultMap, metaObject, lazyLoader, columnPrefix) || foundValues;
        foundValues = lazyLoader.size() > 0 || foundValues;
        ////////////////////////////
        // rowValue will be assigned to null here in this scenario`[the selected value is all null value]`
        // , then it will be put in list in calller method.
        ////////////////////////////
        rowValue = foundValues || configuration.isReturnInstanceForEmptyRow() ? rowValue : null;
    }
    return rowValue;
}

so, i have a proposal to change returnInstanceForEmptyRow default value to true, should we do this?

@Alice52 ,
Ah, you're right. In that case, null will be added to the list.
If we change the default value, existing applications that expect null element in the list will stop working.
So, we will not change the default value.
Adding comments on closing issue is not appropriate.
If you have something to discuss, please use the mailing list.
If you have technical question, ask it on the mailing list or Stack Overflow with the details.


NIFI-10360 VOLUME declaration prevents updating flow from CI

Summary
NIFI-10360
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[x] JDK 11
[x] JDK 17

Licensing

[] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Hello, @exceptionfactory !
Thanks for your work and fast answer!
Can we suppose, that this best practice on official site has a mistake?
Opinion in the internet are different for using VOLUME in Dockerfile. Same opinion.
Maybe we should discuss about use cases?

The associated NiFi Jira issue shows copying the contents of the conf directory into the image itself, which is not the best approach for mutable and sensitive configuration files.

If user want to store data on host filesystem, he can use volume declaration in runtime.

An alternative solution might include creating an alternative base image

I want to make this project some better (10M images downloaded * 50 MB ~ 500 TB disk space)  and don't want to multiply entities beyond necessity

Thanks for the reply @vitalyzhakov!
That post provides a helpful summary of the problems with declared volumes in Dockerfiles.
Taking a look at some of the official Docker images, however, it seems that the use of VOLUME is common for mutable locations. The MongoDB and MySQL templates use VOLUME for the data and configuration directories.
I agree that providing an optimal configuration in the standard community image is the best solution. With that being said, NIFI-5438 introduced volumes several years ago, so this approach has been the standard for several years.

Thanks for fast reply, @exceptionfactory !

I agree that providing an optimal configuration in the standard community image is the best solution. With that being said, NIFI-5438 introduced volumes several years ago, so this approach has been the standard for several years.

Maybe this was a mistake?
Users in NIFI-5799 also have problems for 4 years, caused by adding VOLUME instruction in Dockerfile.
Can your help me, executing mvn clean install -P contrib-check is enough for properly testing my changes?
Or I must make some additional tests?

@vitalyzhakov The standard Maven build does not create the Docker images, so testing the changes would require running a build with the -P docker profile activated.
Unless other contributors offer a different perspective, removing these volume declarations does not look like something that should be changed in light of other common examples.

Hello, @exceptionfactory !

Unless other contributors offer a different perspective
Can you invite people, who will help make right decision?

Thanks for following up on this @vitalyzhakov.
@kevdoran is familiar with these Docker configurations, so he should be able to provide some additional perspective.

Thanks for your proposal and reasoning @vitalyzhakov.
For now, I agree with @exceptionfactory that there are more benefits than downsides to defining the VOLUME inside the Dockerfile. The main downside is when trying to extend the image, but the current images for Apache NiFi are not optimized to be used as base images. Many other people in the community have come up with alternatives images for Apache NiFi that reuse some of the same Dockerfile commands, but do not inherit from apache/nifi.
That said, I'm planning to devote some time this fall to refactoring our approach to Docker images for the project, including separating out the base image from the final image, and also change our approach to sourcing external configurations, which will likely require re-evaluating our use of volumes. If you would like to offer suggestions for changes you would like to see in the Apache NiFi Docker images, we are collecting them here: https://cwiki.apache.org/confluence/display/NIFI/NiFi+Docker+Container+Improvements. You can request write access to the wiki on our developer mailing list or reply here and I'll be happy to add them to the wiki (with attribution).
Thanks!

Thanks for perspective @kevdoran, that is helpful.
@vitalyzhakov It seems like the best approach at this point would be to close the pull request and following Kevin's recommendation to provide suggestions for the proposed Docker Container Improvements.

@kevdoran , hello!
Thanks for your comment!

there are more benefits than downsides to defining the VOLUME inside the Dockerfile

Can you describe also benefits?

@vitalyzhakov The use of VOLUME separates the data in the the configuration, state, and nifi repository directory from the rest of the container. This adds operational flexibility, for example, the volume can be mounted on another container, for example, for taking backups [1]. For example, someone might want to run this nightly:
docker run --rm --volumes-from <container-id> --volume ~/backup:/backup ubuntu bash -c "cd <path/to/volume/data> && tar -cvf /backup/<volume-backup>.tar ."

Source: https://www.ionos.com/digitalguide/server/security/docker-backup/
That said, as stated above, we are curerntly reevaluating our current approach to Docker images for the project, and a major area for improvement is making it easier to use bind mounts or named volumes for configuration or writeable storage. So I'd expect some changes and improvements in this area in the near future, but for now I'd prefer to keep the use of VOLUME in these Dockerfiles.
[1] https://docs.docker.com/storage/volumes/#backup-restore-or-migrate-data-volumes

@kevdoran , hello!
I'm OK, thank you!

Closing per discussion. Will revisit as part of larger changes, planned tentatively for sometime in the next couple of months.


No icon for ToolButton node

There's no icon for the ToolButton node. It shows empty in Create dialog and a generic one in the Scene Tree.

(Calling @djrm for the rescue :wink:)

oh yes will check that.
By the way there are other missing node icons

Interpolated camera
Hinge joint
Cone twist joint
Generic 6 DOF joint

but some of them are trippy


Doesn't compile with RN 0.53.

My project is not compiling when I upgrade to RN 0.53.0, here is the error:
'RCTTextField.h' file not found
#import "RCTTextField.h"
        ^~~~~~~~~~~~~~~~
1 error generated.

** BUILD FAILED **

Anyone having this?

Same problem here. I think RCTTextField does not exist in RN 0.53

Any fix upcoming??

It looks like the module was renamed to RCTUITextField: https://github.com/facebook/react-native/commit/19a9c5e41da0aa6ee28a54772edcb92daa498561

+1

+1

I fixed the compilation issue myself and opened a PR.
For those who wants to compile against RN 0.53., replace the dependency line to
"react-native-text-input-mask": "github:leoneparise/react-native-text-input-mask#fix-build-issue-rn-53",
and run yarn install.
When they merge my PR and update the library, you can switch the version back.

It doesn't compile yet if you are using Cocoapods, I thing, something wrong with Header Search Path

@leoneparise thanks for the PR
I tested on RN 0.53.0, please use 0.6.2 version


PHP 5.5 (PPA) is deprecated/EOL

Since PHP 5.5 is EOL, the PPA is also deprecated.
If we upgrade PHP, should we upgrade to PHP 7 ?
dev :: /vagrant » php -v
PHP 5.5.37-1+deprecated+dontuse+deb.sury.org~trusty+1 (cli) (built: Jun 24 2016 08:29:49)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend Technologies
dev :: /vagrant »

I also can't install PHPUnit due to the version constraint
dev :: /vagrant » composer require --dev phpunit/phpunit
Using version ^4.8 for phpunit/phpunit
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - sebastian/version 2.0.0 requires php >=5.6 -> your PHP version (5.5.37) does not satisfy that requirement.
    - sebastian/version 2.0.0 requires php >=5.6 -> your PHP version (5.5.37) does not satisfy that requirement.
    - sebastian/version 2.0.0 requires php >=5.6 -> your PHP version (5.5.37) does not satisfy that requirement.
    - Installation request for sebastian/version (locked at 2.0.0) -> satisfiable by sebastian/version[2.0.0].

Installation failed, reverting ./composer.json to its original content.
dev :: /vagrant »

We are in the process of making sure everything works on PHP7 to migrate our servers, sounds like a good place to start.

See https://github.com/heybigname/ansible/pull/18
Can we make overrides in our configuration to point to php7.1 ?

https://github.com/AmsterdamPHP/meetup-raffle-machine/pull/29/commits/f5865a24b7047217febdd8d5a5f4d6149e3ba086
This commit uses the updated submodule, so it's now running PHP 5.6 using the deprecated 5.6 repository (at least no 5.5 anymore).
If the heybigname/ansible project points to the latest PPA repository, we should somehow be able to pick 7.x instead of the default 5.6. (not too familiar with ansible though, not sure if we can specify overrides?)


UF-227: More dock resize fixes (see below)

This fixes the following two issues:

When opening an editor with east docks (i.e. data modeller) the
editor's initial horizontal size is incorrect (it's too wide and
part of its content is hidden behind the docks)

When switching to the source tab after expanding a dock, the
source view isn't properly resized and is limiting its horizontal
size by the width of the dock that is no longer displayed

This also needs to be cherry-picked to 0.7.x.

Merged! Thanks!
master: https://github.com/uberfire/uberfire-extensions/commit/93ebf904f3b90d2ad62f3e6ab0886520257d5eac
0.7.x: https://github.com/uberfire/uberfire-extensions/commit/d6e84248884077a30efe84ee065070139c276495


Webtorrent renderer process reliably crashes in Windows 7

What version of WebTorrent Desktop? (See the 'About WebTorrent' menu)
0.6.0 (released, but not yet in the autoupdater)
What operating system and version?
Windows 7 Home 64-bit
Steps to reproduce

Start WebTorrent Desktop with all torrents turned off
Open the webtorrent renderer process
Start a single torrent

Webtorrent renderer process immediately dies:

@feross before we send 0.6.0 to the auto updater, I think we should:

Verify that the windows version works in your VM. It would also be nice to know whether this bug happens on all Windows 7 computers, or whether there's something specifically wrong on my x220.
npm publish

It works great on Mac as far as I can tell, including the autoupdater. (After testing, it successfully downgraded itself to 0.5.1 lol)

Weird. Checking this out now.

Root cause: https://github.com/electron/electron/issues/5629

This was fixed by temporarily disabling WebRTC on Windows to get WebTorrent Desktop v0.6.1 out the door.
This will be undone in v0.7.0.


[nodejs] Release update 18

https://nodejs.org/en/about/releases/
https://github.com/nodejs/node/releases/tag/v18.0.0

use commenting with # instead of using html form because this file is rended by tools and it will fail if you use
something like <!--


tests/eas/acceptance: fix missed rename of config value

An EXPECTED_BIG_BUSY_TIME_PCT got missed out from the recent renaming commit.

Oops, this is in the wrong test, need a different config name I think.

No, wait, I was right the first time :doughnut:


wstool init and merge

Hello, I followed the readme instrutions and clone the package. And i used wstool wstool init . ./mavros_swarm/dependencies.rosinstall and i got this error: Error:There already is a workspace config file .rosinstall at ".". Use wstool install/modify.  So i changed the wstool merge wstool merge . ./mavros_swarm/dependencies.rosinstall  Then i got this error Error: Too many arguments. wstool merge [URI] [OPTIONS]
Could you help me to fix it?
Thank you!

If you want to do a merge, you can do merge -t

And then I got this wstool merge -t . ./mavros_swarm/dependencies.rosinstall  Merge caused no change, no new elements found I don’t know what's wrong with my steps?

@Wayne-xixi It means you already got everything you need with wstool merge

@Wayne-xixi You can get geodetic_utils from here: https://github.com/ethz-asl/geodetic_utils

@Jaeyoung-Lim thanks! It works! I can run the .launch file roslaunch formation_control sitl_multiuav_swarm.launch And I can see three uavs in  gazebo. But they cant fly to 2 m. The result in the console like below:
[ERROR] [1573815428.077148743, 6.000000000]: MODE: Unsupported FCU [ INFO] [1573815428.078621696, 6.000000000]: Setting to Offboard [ INFO] [1573815428.080062312, 6.004000000]: Setting to Offboard INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set) INFO  [ecl/EKF] EKF commencing GPS fusion INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set) INFO  [ecl/EKF] EKF commencing GPS fusion [ INFO] [1573815433.775949897, 11.612000000]: HP: requesting home position INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set) INFO  [ecl/EKF] EKF commencing GPS fusion [ERROR] [1573815434.185476136, 12.000000000]: MODE: Unsupported FCU [ INFO] [1573815434.187234041, 12.004000000]: Setting to Offboard [ INFO] [1573815434.188780956, 12.004000000]: Setting to Offboard [ WARN] [1573815434.191301877, 12.008000000]: CMD: Unexpected command 176, result 1 [ WARN] [1573815434.195280246, 12.012000000]: CMD: Unexpected command 176, result 1 [ INFO] [1573815434.840522424, 12.644000000]: HP: requesting home position [ INFO] [1573815438.879485409, 16.612000000]: WP: item #0* F:2 C:178 p: 1.000000 5.000000 -1.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1573815438.879711835, 16.612000000]: WP: item #1  F:3 C: 22 p: 15.000000 0.000000 0.000000 nan x: 47.397705 y: 8.546729 z: 5.000000 [ INFO] [1573815438.879889092, 16.612000000]: WP: item #2  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.398804 y: 8.544907 z: 50.000000 [ INFO] [1573815438.880062298, 16.612000000]: WP: item #3  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.397778 y: 8.542441 z: 50.000000 [ INFO] [1573815438.880236273, 16.612000000]: WP: item #4  F:2 C: 20 p: 0.000000 0.000000 0.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1573815438.880360171, 16.612000000]: WP: mission received [ INFO] [1573815439.935559998, 17.644000000]: WP: item #0* F:2 C:178 p: 1.000000 5.000000 -1.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1573815439.935938887, 17.644000000]: WP: item #1  F:3 C: 22 p: 15.000000 0.000000 0.000000 nan x: 47.397705 y: 8.546729 z: 5.000000 [ INFO] [1573815439.936269097, 17.644000000]: WP: item #2  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.398804 y: 8.544907 z: 50.000000 [ INFO] [1573815439.936606011, 17.644000000]: WP: item #3  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.397778 y: 8.542441 z: 50.000000 [ INFO] [1573815439.936921484, 17.644000000]: WP: item #4  F:2 C: 20 p: 0.000000 0.000000 0.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1573815439.937089173, 17.644000000]: WP: mission received [ERROR] [1573815440.305010471, 18.000000000]: MODE: Unsupported FCU [ INFO] [1573815440.306481957, 18.004000000]: Setting to Offboard [ INFO] [1573815440.307864116, 18.004000000]: Setting to Offboard [ERROR] [1573815446.399883918, 24.000000000]: MODE: Unsupported FCU [ INFO] [1573815446.401100134, 24.000000000]: Setting to Offboard [ INFO] [1573815446.402472865, 24.004000000]: Setting to Offboard [ WARN] [1573815446.410362276, 24.012000000]: CMD: Unexpected command 176, result 1 [ WARN] [1573815446.410568727, 24.012000000]: CMD: Unexpected command 176, result 1 [ERROR] [1573815452.446849248, 30.000000000]: MODE: Unsupported FCU [ INFO] [1573815452.448344201, 30.004000000]: Setting to Offboard [ INFO] [1573815452.449943566, 30.004000000]: Setting to Offboard [ERROR] [1573815458.551689117, 36.000000000]: MODE: Unsupported FCU [ INFO] [1573815458.553385631, 36.000000000]: Setting to Offboard [ INFO] [1573815458.555101352, 36.004000000]: Setting to Offboard [ WARN] [1573815458.558208870, 36.008000000]: CMD: Unexpected command 176, result 1 [ WARN] [1573815458.567839564, 36.016000000]: CMD: Unexpected command 176, result 1 [ERROR] [1573815464.640697712, 42.000000000]: MODE: Unsupported FCU [ INFO] [1573815464.642277243, 42.000000000]: Setting to Offboard [ INFO] [1573815464.643935065, 42.004000000]: Setting to Offboard [ERROR] [1573815470.720931588, 48.000000000]: MODE: Unsupported FCU [ INFO] [1573815470.722514471, 48.000000000]: Setting to Offboard [ WARN] [1573815470.724108599, 48.004000000]: CMD: Unexpected command 176, result 1 [ INFO] [1573815470.724762453, 48.004000000]: Setting to Offboard [ WARN] [1573815470.732463781, 48.012000000]: CMD: Unexpected command 176, result 1 [ERROR] [1573815476.794223451, 54.000000000]: MODE: Unsupported FCU [ INFO] [1573815476.795596181, 54.000000000]: Setting to Offboard [ INFO] [1573815476.796866105, 54.004000000]: Setting to Offboard [ERROR] [1573815482.868577599, 60.000000000]: MODE: Unsupported FCU [ INFO] [1573815482.869880837, 60.000000000]: Setting to Offboard [ WARN] [1573815482.873403632, 60.004000000]: CMD: Unexpected command 176, result 1 [ INFO] [1573815482.873556584, 60.004000000]: Setting to Offboard [ WARN] [1573815482.879556369, 60.012000000]: CMD: Unexpected command 176, result 1 [ERROR] [1573815488.946480313, 66.000000000]: MODE: Unsupported FCU [ INFO] [1573815488.948493139, 66.004000000]: Setting to Offboard [ INFO] [1573815488.950309012, 66.004000000]: Setting to Offboard [ERROR] [1573815495.022773953, 72.000000000]: MODE: Unsupported FCU [ INFO] [1573815495.023886106, 72.000000000]: Setting to Offboard [ INFO] [1573815495.024993020, 72.004000000]: Setting to Offboard [ WARN] [1573815495.033209708, 72.012000000]: CMD: Unexpected command 176, result 1 [ WARN] [1573815495.033499828, 72.012000000]: CMD: Unexpected command 176, result 1 [ERROR] [1573815501.089543687, 78.000000000]: MODE: Unsupported FCU [ INFO] [1573815501.091818837, 78.004000000]: Setting to Offboard [ INFO] [1573815501.093540844, 78.004000000]: Setting to Offboard [ERROR] [1573815507.182310582, 84.000000000]: MODE: Unsupported FCU [ INFO] [1573815507.184225839, 84.000000000]: Setting to Offboard [ INFO] [1573815507.186152970, 84.004000000]: Setting to Offboard [ WARN] [1573815507.192278469, 84.012000000]: CMD: Unexpected command 176, result 1 [ WARN] [1573815507.200717531, 84.020000000]: CMD: Unexpected command 176, result 1 [ERROR] [1573815513.257569524, 90.000000000]: MODE: Unsupported FCU [ INFO] [1573815513.259029346, 90.000000000]: Setting to Offboard [ INFO] [1573815513.260410877, 90.004000000]: Setting to Offboard [ERROR] [1573815519.312002493, 96.000000000]: MODE: Unsupported FCU [ INFO] [1573815519.313356576, 96.000000000]: Setting to Offboard [ INFO] [1573815519.314502672, 96.004000000]: Setting to Offboard [ WARN] [1573815519.318461555, 96.008000000]: CMD: Unexpected command 176, result 1 [ WARN] [1573815519.318644539, 96.008000000]: CMD: Unexpected command 176, result 1
Unsupported FCU means I have unsupported versions or I just made wrong settings?

May be you have the wrong firmware version or the firmware has not been build properly.
Can you run PX4 SITL properly? How were you running it?

@Jaeyoung-Lim yes, I can run it, and I can control the uav to fly and land.

@Wayne-xixi Please share the full log of your output. I suspect that you are not able to run SITL properly

@Jaeyoung-Lim ok, like below.
`make px4_sitl_default gazebo[2/6] Performing configure step for 'sitl_gazebo'
-- install-prefix: /usr/local
-- Using C++14 compiler
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   system
--   thread
--   filesystem
--   chrono
--   date_time
--   atomic
-- Boost version: 1.58.0
-- Building klt_feature_tracker without catkin
-- Building OpticalFlow with OpenCV
-- catkin DISABLED
Gazebo version: 7.16
-- Configuring done
-- Generating done
-- Build files have been written to: /home/fapsros/Firmware/build/px4_sitl_default/build_gazebo
[3/6] Performing build step for 'sitl_gazebo'
ninja: no work to do.
[6/6] cd /home/fapsros/Firmware/build/...apsros/Firmware/build/px4_sitl_default
SITL ARGS
sitl_bin: /home/fapsros/Firmware/build/px4_sitl_default/bin/px4
debugger: none
program: gazebo
model: none
src_path: /home/fapsros/Firmware
build_path: /home/fapsros/Firmware/build/px4_sitl_default
empty model, setting iris as default
GAZEBO_PLUGIN_PATH :/home/fapsros/Documents/gazebo_plugin_tutorial/build/:/home/fapsros/Firmware/build/px4_sitl_default/build_gazebo:/home/fapsros/Firmware/build/posix_sitl_default/build_gazebo:/home/fapsros/Firmware/build/px4_sitl_default/build_gazebo:/home/fapsros/Firmware/build/px4_sitl_default/build_gazebo
GAZEBO_MODEL_PATH :/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/models:/home/fapsros/catkin_ws/src/avoidance/avoidance/sim/worlds:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/catkin_ws/src/realsense_gazebo_plugin/models:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/Firmware/Tools/sitl_gazebo/models:/home/fapsros/Firmware/Tools/sitl_gazebo/models
LD_LIBRARY_PATH /home/fapsros/catkin_ws/devel/lib:/opt/ros/kinetic/lib:/opt/ros/kinetic/lib/x86_64-linux-gnu:/home/fapsros/Firmware/build/px4_sitl_default/build_gazebo:/home/fapsros/Firmware/build/posix_sitl_default/build_gazebo:/home/fapsros/Firmware/build/px4_sitl_default/build_gazebo:/home/fapsros/Firmware/build/px4_sitl_default/build_gazebo
Gazebo multi-robot simulator, version 7.16.0
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
[Msg] Publicized address: <IP_ADDRESS>
[Wrn] [gazebo_barometer_plugin.cpp:66] [gazebo_barometer_plugin] Using default home altitude of 488 m
[Dbg] [gazebo_mavlink_interface.cpp:135] <joint_name> not found for channel[0] no joint control will be performed for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:135] <joint_name> not found for channel[1] no joint control will be performed for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:135] <joint_name> not found for channel[2] no joint control will be performed for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:135] <joint_name> not found for channel[3] no joint control will be performed for this channel.
[Wrn] [gazebo_mavlink_interface.cpp:124] joint [zephyr_delta_wing::propeller_joint] not found for channel[4] no joint control for this channel.
[Wrn] [gazebo_mavlink_interface.cpp:124] joint [zephyr_delta_wing::flap_left_joint] not found for channel[5] no joint control for this channel.
[Wrn] [gazebo_mavlink_interface.cpp:124] joint [zephyr_delta_wing::flap_right_joint] not found for channel[6] no joint control for this channel.
[Dbg] [gazebo_mavlink_interface.cpp:135] <joint_name> not found for channel[7] no joint control will be performed for this channel.
[Msg] Connecting to PX4 SITL using TCP
[Msg] Lockstep is enabled
[Msg] Speed factor set to: 1
SITL COMMAND: "/home/fapsros/Firmware/build/px4_sitl_default/bin/px4" "/home/fapsros/Firmware"/ROMFS/px4fmu_common -s etc/init.d-posix/rcS -t "/home/fapsros/Firmware"/test_data
INFO  [px4] Creating symlink /home/fapsros/Firmware/ROMFS/px4fmu_common -> /home/fapsros/Firmware/build/px4_sitl_default/tmp/rootfs/etc
0 WARNING: setRealtimeSched failed (not run as root?)

| ___ \ \ \ / /   /   |
| |/ /  \ V /   / /| |
|  __/   /   \  / /| |
| |     / /^\ \ ___  |
_|     /   /     |_/
px4 starting.
INFO  [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
INFO  [dataman] Unknown restart, data manager file './dataman' size is 11798680 bytes
INFO  [simulator] Waiting for simulator to connect on TCP port 4560
INFO  [simulator] Simulator connected on TCP port 4560.
[Msg] Using MAVLink protocol v2.0
Gazebo multi-robot simulator, version 7.16.0
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
[Msg] Publicized address: <IP_ADDRESS>
INFO  [init] Mixer: etc/mixers/quad_w.main.mix on /dev/pwm_output0
INFO  [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 14570 remote port 14550
INFO  [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540
INFO  [logger] logger started (mode=all)
INFO  [logger] Start file log (type: full)
INFO  [logger] Opened full log file: ./log/2019-11-15/14_14_56.ulg
INFO  [mavlink] MAVLink only on localhost (set param MAV_BROADCAST = 1 to enable network)
INFO  [px4] Startup script returned successfully
pxh> [Wrn] [Publisher.cc:141] Queue limit reached for topic /gazebo/default/iris/motors, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:141] Queue limit reached for topic /gazebo/default/iris/motor_speed/0, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:141] Queue limit reached for topic /gazebo/default/iris/motor_speed/1, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:141] Queue limit reached for topic /gazebo/default/iris/motor_speed/2, deleting message. This warning is printed only once.
[Wrn] [Publisher.cc:141] Queue limit reached for topic /gazebo/default/iris/motor_speed/3, deleting message. This warning is printed only once.
INFO  [ecl/EKF] EKF aligned, (pressure height, IMU buf: 22, OBS buf: 14)
INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set)
INFO  [ecl/EKF] EKF commencing GPS fusion
`

Not sure. Do you get mavlink from all three vehicles? It seems like there is only one SITL instance starting

ok, thank you, I try to fix it.

@Wayne-xixi Actually, the second log you have posted are not from launching the launchfile, but you are running make px4_sitl_gazebo default. That would only launch one vehicle. Is this the outcome you are aiming for?

@Wayne-xixi any updates?

@Jaeyoung-Lim hello Jaeyoung, sorry for the late reply. I had just roslaunch formation_control. And I still met the same problem.  The console is below. Please see the error ist unsupported FCU. Thank you.
[ INFO] [1574172713.551307367, 5.936000000]: VER: 3.1: Board hardware:      00000001 [ INFO] [1574172713.551343684, 5.936000000]: VER: 3.1: VID/PID:             0000:0000 [ INFO] [1574172713.551379862, 5.936000000]: VER: 3.1: UID:                 4954414c44494e51 [ERROR] [1574172713.616550440, 6.000000000]: MODE: Unsupported FCU [ INFO] [1574172713.618836904, 6.004000000]: Setting to Offboard [ INFO] [1574172713.620773533, 6.004000000]: Setting to Offboard [ERROR] [1574172719.733157307, 12.000000000]: MODE: Unsupported FCU [ INFO] [1574172719.734766800, 12.000000000]: Setting to Offboard [ INFO] [1574172719.736418756, 12.004000000]: Setting to Offboard [ WARN] [1574172719.739376464, 12.008000000]: CMD: Unexpected command 176, result 1 [ WARN] [1574172719.752630734, 12.020000000]: CMD: Unexpected command 176, result 1 INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set) INFO  [ecl/EKF] EKF commencing GPS fusion INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set) INFO  [ecl/EKF] EKF commencing GPS fusion INFO  [ecl/EKF] EKF GPS checks passed (WGS-84 origin set) INFO  [ecl/EKF] EKF commencing GPS fusion [ INFO] [1574172722.754687490, 14.936000000]: HP: requesting home position [ERROR] [1574172725.889395262, 18.000000000]: MODE: Unsupported FCU [ INFO] [1574172725.891604412, 18.004000000]: Setting to Offboard [ INFO] [1574172725.893095174, 18.004000000]: Setting to Offboard [ INFO] [1574172727.240498919, 19.328000000]: WP: item #0* F:2 C:178 p: 1.000000 5.000000 -1.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1574172727.240698385, 19.328000000]: WP: item #1  F:3 C: 22 p: 15.000000 0.000000 0.000000 nan x: 47.397705 y: 8.546729 z: 5.000000 [ INFO] [1574172727.240877738, 19.328000000]: WP: item #2  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.398804 y: 8.544907 z: 50.000000 [ INFO] [1574172727.241038792, 19.328000000]: WP: item #3  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.397778 y: 8.542441 z: 50.000000 [ INFO] [1574172727.241176100, 19.328000000]: WP: item #4  F:2 C: 20 p: 0.000000 0.000000 0.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1574172727.241253414, 19.328000000]: WP: mission received [ INFO] [1574172727.865257207, 19.936000000]: WP: item #0* F:2 C:178 p: 1.000000 5.000000 -1.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1574172727.865488800, 19.936000000]: WP: item #1  F:3 C: 22 p: 15.000000 0.000000 0.000000 nan x: 47.397705 y: 8.546729 z: 5.000000 [ INFO] [1574172727.865661658, 19.936000000]: WP: item #2  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.398804 y: 8.544907 z: 50.000000 [ INFO] [1574172727.865824108, 19.936000000]: WP: item #3  F:3 C: 16 p: 0.000000 0.000000 0.000000 nan x: 47.397778 y: 8.542441 z: 50.000000 [ INFO] [1574172727.865990121, 19.936000000]: WP: item #4  F:2 C: 20 p: 0.000000 0.000000 0.000000 0.000000 x: 0.000000 y: 0.000000 z: 0.000000 [ INFO] [1574172727.866073372, 19.936000000]: WP: mission received [ERROR] [1574172732.020664399, 24.004000000]: MODE: Unsupported FCU [ INFO] [1574172732.022558146, 24.008000000]: Setting to Offboard [ INFO] [1574172732.024183143, 24.008000000]: Setting to Offboard [ WARN] [1574172732.033572116, 24.020000000]: CMD: Unexpected command 176, result 1 [ WARN] [1574172732.033963507, 24.020000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172738.134785616, 30.000000000]: MODE: Unsupported FCU [ INFO] [1574172738.136377787, 30.000000000]: Setting to Offboard [ INFO] [1574172738.139064162, 30.004000000]: Setting to Offboard [ERROR] [1574172744.306227459, 36.000000000]: MODE: Unsupported FCU [ INFO] [1574172744.308335548, 36.004000000]: Setting to Offboard [ INFO] [1574172744.309724203, 36.004000000]: Setting to Offboard [ WARN] [1574172744.315069785, 36.012000000]: CMD: Unexpected command 176, result 1 [ WARN] [1574172744.318692312, 36.016000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172750.424044466, 42.000000000]: MODE: Unsupported FCU [ INFO] [1574172750.425602765, 42.004000000]: Setting to Offboard [ INFO] [1574172750.427261496, 42.004000000]: Setting to Offboard [ERROR] [1574172756.561030811, 48.000000000]: MODE: Unsupported FCU [ INFO] [1574172756.562810716, 48.004000000]: Setting to Offboard [ WARN] [1574172756.563334805, 48.004000000]: CMD: Unexpected command 176, result 1 [ INFO] [1574172756.565291339, 48.004000000]: Setting to Offboard [ WARN] [1574172756.572777766, 48.012000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172762.700785734, 54.000000000]: MODE: Unsupported FCU [ INFO] [1574172762.702183677, 54.004000000]: Setting to Offboard [ INFO] [1574172762.703409741, 54.004000000]: Setting to Offboard [ERROR] [1574172768.820045243, 60.000000000]: MODE: Unsupported FCU [ INFO] [1574172768.821398418, 60.000000000]: Setting to Offboard [ WARN] [1574172768.822245383, 60.004000000]: CMD: Unexpected command 176, result 1 [ INFO] [1574172768.823232241, 60.004000000]: Setting to Offboard [ WARN] [1574172768.830366039, 60.012000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172774.967022244, 66.000000000]: MODE: Unsupported FCU [ INFO] [1574172774.968760943, 66.004000000]: Setting to Offboard [ INFO] [1574172774.970188848, 66.004000000]: Setting to Offboard [ERROR] [1574172781.109528774, 72.000000000]: MODE: Unsupported FCU [ INFO] [1574172781.111526234, 72.004000000]: Setting to Offboard [ WARN] [1574172781.112949670, 72.004000000]: CMD: Unexpected command 176, result 1 [ INFO] [1574172781.117257480, 72.004000000]: Setting to Offboard [ WARN] [1574172781.126830834, 72.016000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172787.260705750, 78.000000000]: MODE: Unsupported FCU [ INFO] [1574172787.265330011, 78.000000000]: Setting to Offboard [ INFO] [1574172787.267361764, 78.004000000]: Setting to Offboard [ERROR] [1574172793.479196872, 84.000000000]: MODE: Unsupported FCU [ WARN] [1574172793.482079781, 84.000000000]: CMD: Unexpected command 176, result 1 [ INFO] [1574172793.482235946, 84.000000000]: Setting to Offboard [ INFO] [1574172793.484862327, 84.004000000]: Setting to Offboard [ WARN] [1574172793.486894080, 84.008000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172799.669452002, 90.000000000]: MODE: Unsupported FCU [ INFO] [1574172799.671202504, 90.000000000]: Setting to Offboard [ INFO] [1574172799.672624263, 90.000000000]: Setting to Offboard [ERROR] [1574172805.838140283, 96.004000000]: MODE: Unsupported FCU [ INFO] [1574172805.839887921, 96.004000000]: Setting to Offboard [ INFO] [1574172805.841261420, 96.004000000]: Setting to Offboard [ WARN] [1574172805.846671116, 96.008000000]: CMD: Unexpected command 176, result 1 [ WARN] [1574172805.851077682, 96.008000000]: CMD: Unexpected command 176, result 1 [ERROR] [1574172811.954936700,<PHONE_NUMBER>00]: MODE: Unsupported FCU [ INFO] [1574172811.956455049,<PHONE_NUMBER>00]: Setting to Offboard [ INFO] [1574172811.957686491,<PHONE_NUMBER>00]: Setting to Offboard

@Jaeyoung-Lim This is my screen shot

@Wayne-xixi You might have not set your environment properly see: https://github.com/PX4/Firmware/issues/12038

@Jaeyoung-Lim Hello, update! Today when I roslaunch, i got this error.
px4 starting. NFO  [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0 Error: Unknown model '' ERROR [px4] Startup script returned with return value: 256
I have checked the launch file:
So I cant open the models. Do you know the reason?
Thank you!

Did you set the environment variables properly?

@Jaeyoung-Lim Yes, I follow your instructions.  cd src/Firmware
source Tools/setup_gazebo.bash $(pwd) $(pwd)/build/px4_sitl_default
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)/Tools/sitl_gazebo

@Jaeyoung-Lim And
roslaunch px4 mavros_posix_sitl.launch was ok.

@Jaeyoung-Lim Yes make px4_sitl_default gazebo was also ok.

@Wayne-xixi Did you fix this issue?
@Jaeyoung-Lim I have the same issue. roslaunch formation_control sitl_multiuav_swarm.launch runs the gazebo with 3 drones but not arming and hovering. QGC shows "Not ready to fly" and does not even fly them manually.


Sprint 2 - CSA Objectives

Sprint 2 Blog: Link

Assignment
Points
Grade
Evidence

Pull Request (Integration)
2
2

Relevancy Checklist (Peer)
2
1.64
Link

Lesson (Group)
1
0.92

Homework, Popcorn Hacks
1 x 8
7.19
0.94+0.93+0.91+0.87+0.85+0.9+0.9+0.89

Individual Contribution
1
0.86
Link

Personal Notebooks / Blogs
1
0.89
Link

Total
15
13.5

Skill
Points
Grade
Evidence

Work Habits (Analytics)
1
0.9
Link

Team Planning (Issue)
1
0.88
Link

Presentation Memories
1
0.88

Grading and Feedback
1
0.85

Beyond Perfunctory
1
0.9
Link

Total
5
4.41

I looked at your personal blog.  Navigation on it is kind of messed up with submenus and I got some 404s

Blog - in association with Units and Teaching
Memory - something to recall your individual presentation
Relevancy - something impactful you learned
Beyond Perfunctory - something that shows you want to learn
Started blog.  Talked about a challenge hack.   A lot of people fell into chatgpt traps.  Remade a program from Python to Java.  Made a game that represented units.

Memory- Doing the chatgpt grading memory, which allowed him to make his test cases and homework chatgpt proof. Also complained about semicolons.
Personal Blog- Made a game in python but used the Java syntax to make him get practice with java
Relevancy- Talked about the inheritance unit, and how he learned lots of stuff there
Beyond Perfunctory making the game

I like how your blog is organized I think its very different and organized.

Hi Ian,
I liked how you made your homework ChatGPT proof and went above and beyond with the game you made! Your organization was also unique.
Thanks
Dinesh Sahai

I liked your memory about the chatgpt grading memory. I thought your personal blog and it included all the team teaches. Talked about the other units and stuff and showed it by making a game.

The python game is a good way to remember the lesson you taught.

Your blog is very organized and very easy to follow. You showed how you worked effectively with your team.

Making your homework ChatGPT proof reminds me of how the engineering teacher here always made sure we knew his quizzes were ChatGPT proof. The game you added was great and your work is easy to follow.

I loved how you made a game that incorporates all the topics we were taught, and think that really demonstrates that you are skilled in these topics.

I really like the innovation with the ChatGPT memory feature as it is a good way to use AI to simplify normal tedious tasks. The python game was interesting and good use of java orientation.

Memory: I liked your work, especially the GPT hack. Your Python recreation program was quite interesting, particularly the anti-ChatGPT hack. I remember trying to do it with ChatGPT, but it didn’t work no matter what I tried, so I had to fix it manually. It seems like it was quite enticing for you as well.
Personal Blog: I liked that you made a game in Python but used Java syntax.
Relevance: Talking about inheritance.
Beyond Perfunctory: Very organized.

Hi Ian,
I liked the implementation of an anti-GPT hack, and we were trying to do the same for our own team teach as well.

I really liked the organization of your blog. I think creating a ChatGPT proof hack was really smart as it is a good reminder that we have to check the code outputted by ChatGPT because it may not be accurate.


Create a content-card-8.html

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

After building the component please raise a PR with a screenshot of the component and add the component in `seamless-ui/Content card/src/content-card-8.html.
If you need to use any icon please use it from Hero Icons
Good luck.

can i work on this?

No need of this one right now. You can focus more on improving the existing components. @nik132-eng


use the OCI containers to distribute camel-k artifacts

Open Container Initiative (OCI) has defined specs to enable the creation of interoperable tools for building, transporting, and preparing a container image to run, however - in practice - registries have a little to do with container images and we can think about them as a content addressable storage.
In camel-k we have been struggling a lot about find an easy way to provide artifacts/blobs to the runtime (i.e. https://github.com/apache/camel-k/issues/1821) and I think experimenting about leveraging OCI compatible registries could be a way to improve the situation.
This is not a brand new novel idea as:

some discussion about leveraging container images have been happened already in the camel-k community
solo.io leverages container images to distribute WASM
there has been a recent talk about hacking the registry at kubecon

Since each layer is essential a blob (often a tar.gz) and that the layer definition has an optional annotations property that can hold arbitrary key/value paris, we can leverage it to identify camel-k artifacts (i.e. additional dependencies, resources, kamelets repositories, etc):
{
  "schemaVersion": 2,
  "layers": [{
      "mediaType": "application/vnd.oci.image.layer.v1.tar+gzip",
      "size": 16724,
      "digest": "sha256:3c3a4604a545cdc127456d94e421cd355bca5b528f4a9c1905b15da2eb4a4c6b",
      "annotations": {
        "camel.apache.org.dependency": "com.acme:foo:1.0"
      }
    }, {
      "mediaType": "application/vnd.oci.image.layer.v1.tar+gzip",
      "size": 73109,
      "digest": "sha256:ec4b8955958665577945c89419d1af06b5f7636b4ac3da7f12184802ad867736",
      "annotations": {
        "camel.apache.org.kamelets.repository": "acme-kamelets"
      }
    }
  ]
}

NOTES:

solo.io has introduced a set of additional mediaType values but that may not work with some registries or tools so IMHO, at this stage, it would be better not to introduce a custom media type and leverage annotations.
A further evolution would be to implement a Kubernetes Container Storage Interface (CSI) to mount OCI layers to a POD
kamel run can be enahanced to package a container image - ko alike - and generate a minimal Integration that points to that container image
a Maven Wagon  can be implemented to be able to read directly from a registry (similar to the s3 wagon)
container images can be used as a dependency kamel run -d container:docker.io/foo/bar

/cc @nicolaferraro @astefanutti

It seems like it would be the right level to abstract our needs for packaging and distributing artifacts.
From the performance standpoint, interaction with the container registry is now the major contributor to "TTFB" (Camel K equivalent) on average. And it does not scale well with the number of nodes. I'd be eager to research how it could use in combination with some initiatives / approaches like the above to improve performance, especially for the serverless use case:

https://medium.com/nttlabs/startup-containers-in-lightning-speed-with-lazy-image-distribution-on-containerd-243d94522361
https://stevelasker.blog/2019/10/29/azure-container-registry-teleportation/

It seems like it would be the right level to abstract our needs for packaging and distributing artifacts.
From the performance standpoint, interaction with the container registry is now the major contributor to "TTFB" (Camel K equivalent) on average. And it does not scale well with the number of nodes. I'd be eager to research how it could use in combination with some initiatives / approaches like the above to improve performance, especially for the serverless use case:
* [medium.com/nttlabs/startup-containers-in-lightning-speed-with-lazy-image-distribution-on-containerd-243d94522361](https://medium.com/nttlabs/startup-containers-in-lightning-speed-with-lazy-image-distribution-on-containerd-243d94522361)

* [stevelasker.blog/2019/10/29/azure-container-registry-teleportation](https://stevelasker.blog/2019/10/29/azure-container-registry-teleportation/)

There is also this one that may be interesting https://cloud.google.com/blog/products/containers-kubernetes/introducing-container-image-streaming-in-gke

This may be interesting https://oras.land/

Hi @lburgazzoli,
As an immediate solution, it is possible to distribute camel-k artifacts as images using the wagon-docker-registry (e.g mvn deploy to docker.io) which is already integrated with camel-k via the registry trait. This works with Maven artifacts but also any kind of "blob".


Auto width editor Not Working in v0.20.0

I have an html element that can change the width and the Monaco editor inside the div. When I resize the container dynamically version 0.20.0 doesn't automatically width.
monaco-editor version: 0.20.0
Browser: Chrome, Firefox
OS: Windows 10

seems to be alot of issue with this release 0.20. same issue on my side.

We've similarly had this issue and reverted to 0.19.3. Our implementation has a user-resizeable pane that contains the editor. On 0.19.3 this would resize the editor correctly, but bumping the dependency broke that.

Likely related: https://github.com/microsoft/monaco-editor/issues/1855


Spike | Study how to use poetry

Description
Since we are trying to create a lib was decided to use the poetry to make the connection with our application and the pip (package-management). So in this task should be commented the process to create a lib with poetry
Output
A POC using the code already created in the project where the function receive a yaml and return the data mentioned in the yaml
Checklist

[x] Understand how to use dependencies
[ ] Create the structure to receive a yaml
[x] The lib return the data mentioned in the yaml

Study about Poetry
It is a complete tool, is lib for management all dependencies, packaging the project and upload your build for PyPi.
Use dependencies

In pyproject.toml file, Poetry save all dependencies and your version:

The Poetry use the virtual env, but you dont have one, already create a virtual env for the project in your computer.

For include one dependency, we use the command:
poetry add pytest
For include dependency in dev development environment:
poetry add --dev pytest
After the include all dependencies if you want, is necessary install all this:
poetry install

To take a look
Poetry documentation
Poetry cli
Poetry basic-usage
Video about Poetry
Gerenciando pacotes e ambientes com Poetry

Talking About Project organization:

PiPy account will own the library
We'll need to create an account for the project where the lib will be hosted

@Bruno-Felix I know that we talked about the other organizations projects using poetry, can you list here some examples and one proposal to that structure in our project (this proposal can be a pull request with the modifications already implemented)
Thinking about it, I guess your job is done in this task, since this is a spike, I think we can use here just to finish the conversation about the project structure and the commands! but here we go with some questions:

Did you see any example about the planning to build a library?
Could you list the steps to build the library? (This will use to make the tasks)
Did you think it's enough work for the time that we have here in the project?

Poetry Scripts (Cli)
In pyproject.toml file, we can set the tool.poetry.scripts], can be set what functions and name we can call on poetry cli.
After this, is gonna be necessary to understand how we can use this scripts for builds a cli project lib


Blog posts

How do I create a new blog post of my own? Should I enter the name of the new blog in some other file?

Do you want to create a post or a new 2nd blog on the same site? To create a post, just follow the template pages and replace all the pertinent placeholders. It should automatically show everything in the _posts folder.


2 questions

1
https://github.com/bloc97/Anime4K/blob/master/Java_Instructions.md
how do you get the default upsampling scale first, by bicubic? or bilinear?of other methods? And then use the enhancement Anime4K method.
2
https://github.com/bloc97/Anime4K/blob/master/results/Graph.png?raw=true
how do you get the perceptual quality?

1

the image can be upscaled in advance with any algorithm the user prefers
-- https://github.com/bloc97/Anime4K/blob/master/Preprint.md

2
https://github.com/bloc97/Anime4K/blob/master/Preprint.md#analysis

More exactly, Mean Opinion Score from a dozen people comparing all the different algorithms, a few tests were to choose the best of 2, and a few were to rate all the algorithms from 0 to 10. The tests were double blind but we do know this is not rigorous enough to be considered a serious publication.

@bloc97 how to set the Push_Strength and Push_Grad_Strength parameters when using?

Available parameters:
java -jar Anime4K.jar [File_In] [File_Out] (Scale) (Push_Strength) (Push_Grad_Strength)
is what the instructions say. What are you having troubles with?

@bloc97 Actually, am I overlooking something or is the documentation wrong about the order of the (Push_Strength) and (Push_Grad_Strength)
https://github.com/bloc97/Anime4K/blob/3d75fd642a7de50676f434a7fc8c5005c01399bf/java/src/main/java/com/bloc97/anime4k/Main.java#L45-L53

I mean that I don't know what does these two parmeters mean, how to set these two parameters to make the output image better?

@stefnotch You are right, they are wrong. I must have overlooked the change when writing the md.

@splinter21 You can play around with the settings and see what they do, but to put it simply, Push_Stength thins black lines.  Push_Grad_Strength is the edge refinement strength. The higher it is, the sharper the edges. Put it too high and you lose texture detail.

I know. Thanks！


Incompatibility between torsocks and Cosmopolitan

It seems that the Cosmopolitan binary can be wrapped into torsocks. I think that torsocks introspects some syscalls but Cosmopolitan obfuscates syscalls.

@reynir said that we probably provide a socks implementation and ocaml-socks is a good candidate for that. I will try to discuss about ownership of this library to be able to keep the control of all dependencies needed by bob.

I took the ownership on ocaml-socks which means that I'm able to provide something for SOCKSv4/v5 now and let people to redirect the Bob connection into a Tor node!

Fixed by #49


improve consistency of displayed length units

I've been noticing that there are a few places which display length measurements in either metric or imperial units (meters/km or feets/miles):

map scale
measurement info box
speed limit preset field (default selection)
intersection size selector in turn restriction editor

Currently, some of them can be switched between the two unit systems (map scale and measurement info box), but independently from each other. I believe it would be better if there were synchronized in the UI (e.g. if I switch the scale to metric, I'd like to get the results in the measurements info box also in meters) and remembered between different editing sessions (in a cookie or local storage).
While the speed limit preset field defaults to either metric or imperial units by checking the location of the street with the data in imperial.json, the rest seems to default on some heuristics based upon the user's locale. This makes sense, even though it's a bit unfortunate that it defaults to imperial for people using (generic) english locale outside of the US/Britain – maybe it could improved a bit by looking at other factors like the full list of browser's locales and the starting coordinates of the editing session (using the aforementioned imperial.json data)?

I agree it would be great to have more consistency here.
Because all these controls only redraw when needed, we'd probably need to use an evented approach, like where they subscribe to events that are dispatched whenever a user changes their unit preference.
Another thing to consider is that the user might not be mapping in a place that uses their preferred unit.  So they might want to see feet/miles on the scale bar (because that's what they're used to), but see km/h in the maxspeed field (because that's what's on the local street signs).

So they might want to see feet/miles on the scale bar (because that's what they're used to), but see km/h in the maxspeed field (because that's what's on the local street signs).

As it happens, Puerto Rico officially measures road distances in kilometers but speeds in miles per hour.

All I know is I am editing the map here in Taiwan.
Several times today I have had to change the scale bar at the bottom of the window, from feet to meters (by clicking on it.)
I am guessing that because my browser is set to English(US), somehow feet are coming back over and over.

For sure, iD should remember your preference with a cookie and be consistent regardless of your browser’s language settings. The only place that should probably differ by default is the unit textbox in fields like maxspeed, since the mapper typically gets the value from a sign posted in the local units.

Its crazy. Even though I only edit Taiwan, and connect from Taiwan, every day I have to click the darn scale bar to change it from Feet back to Meters.
Why not give the Feet people a taste of their own medicine on every odd numbered month instead.

All I know is the editor is smart enough to put my picture in the upper right corner.
Why can't it remember that I don't like smelly Feet?!

@jidanni You sound frustrated, but as I have asked you before, please assume good faith and don't write like iD is trying to spite you. There are more professional ways to convey your urgency. We are aware of this request and will implement a solution in time. Understand that we are a very small team and features that sound easy might not be.

Yes.
Also in the Measurement panel, the choice "Metric" seems to need to be clicked more than once per day as it does not stay put for long.


Subsetting: SCORE SM bug in Country filter

Bug hit when subsetting SCORE S. mansoni Cluster Randomized Trial by Country
If I select Kenya or Tanzania, the filtering looks fine

When I select Cote d'Ivoire, ALL data is filtered out (there should be 75 households with data remaining)
When I select all countries, ALL data is filtered out (there should be 449 households with data remaining)

the subsetting service needs to clean string inputs for sql

this is confirmed fixed on dave's dev site


Element not selected then navigating with keyboard through  results

Hey everybody!
First of all: great project!!
I discovered a behaviour that's different from original Semantic UI.
If you navigate through the results of <sui-select> with keyboard up and down arrow keys, the current element is not selected. Hence the result list is not scrolling and you can not see where you are in the result list if you select anything out of the visible result range.
The original Semantic UI behaviour is different. If you navigate through the results with up and down key, the element is selected and the list is scrolling if you reach the upper or lower end of the visible range.
http://semantic-ui.com/modules/dropdown.html#search-selection --> select dropdown and navigate with keyboard keys
http://edcarroll.github.io/ng2-semantic-ui/#/components/select --> won't work here
You can argue about whether or not it's a good idea to directly select the item when navigating with keyboard. But it's absolutely essential to scroll the list.
Thank you!

Hi there, apologies for the delay getting back to you on this one. I've been thinking about how to implement this within the new dropdown & select implementations, and can be done from within the dropdown menu. I'll have a look at getting this sorted in the next few weeks, but can't promise anything I'm afraid.

I've just merged a change that contains a fix for a part of this issue (0.7.0) - specifically, as you rightly say, that the keyboard navigation should auto-scroll the select whenever the highlighted item is out of the viewport.
Now, the behaviour is that it is scrolled automatically when navigating with the keyboard. However, I have opted to not add the auto-selection when navigating - let me know if that is something you are really keen to see in the project.


Image metadata lookup credentials handling

The image metadata "cache" stores its data with keys that include a username, with the idea being that this will avoid leaking information when images have different authentication.
As things stand, however, the username is always an empty string when putting image metadata in the cache, because it's derived from an unassigned Credentials field in the cache warmer. And it's always an empty string when looking up image metadata, because it is given a literal empty Credentials value.
Either these should be fixed to use the actual credentials (e.g., by always finding the imagePullSecret when looking up controllers), or we should just remove the username from the key (or otherwise give up on segregating image metadata).

This will be fixed as part of the https://github.com/weaveworks/flux/pull/851/files (image-reg-caching branch)


Motion detection doesn't work

The adapter seems working.
Lists all cams in objects and shows all objects of the cams
But motion detection object is allways false and not been updated. If i restart the adapter i got new timestamp for all object.
But "last update" date is from 5 days ago - may be the install date from the adapter.
I set motion detection in synology survilence state for those cams just today. synology survile recognize the motions.
But i cant recognize motion detection under objects: object > synology > SurvilanceStation > cameras > CamName > motionDetected

concretized in new issue


Some docker containers never stopped after kernel generator execution

After the execution of kernel_generator.py some docker containers are still executed and are never stopped.
user@ubuntu-server:~/tuxml$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
02301babf9d9        tuxml/tuxml:dev     "bash"              40 minutes ago      Up 40 minutes                           nostalgic_antonelli
2aa85aad75a9        082c903f5449        "bash"              5 hours ago         Up 5 hours                              ecstatic_liskov
3bb5d42f3411        082c903f5449        "bash"              6 hours ago         Up 6 hours                              infallible_galois

I think this is linked with #23, try without the --logs option to see if the container keeps running

What I want to say is that I think it occurs when the script crashes and cannot stop the container.


Triemap rework

Handle cases where TrieMap getOrElseUpdate fails (most likely due to prometheus metrics already existing)

Codecov Report

Merging #22 into master will decrease coverage by 0.47%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   84.39%   83.91%   -0.48%
==========================================
  Files          17       17
  Lines         391      398       +7
  Branches       40       43       +3
==========================================
+ Hits          330      334       +4
- Misses         61       64       +3

Impacted Files
Coverage Δ

...a/akka/monitor/instrumentation/RouterMonitor.scala
64.7% <100%> (ø)
:arrow_up:

...ala/com/workday/prometheus/akka/ActorMetrics.scala
100% <100%> (ø)
:arrow_up:

...la/com/workday/prometheus/akka/RouterMetrics.scala
83.33% <60%> (-16.67%)
:arrow_down:

...la/akka/monitor/instrumentation/ActorMonitor.scala
87.83% <75%> (-1.21%)
:arrow_down:

Continue to review full report at Codecov.

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


Optimistic Sync

This PR introduces a specification for optimistic sync.
Optimistic sync provides a way for consensus engines (beacon nodes) to follow the head of the chain without verifying execution payloads. The requirement for this is based upon the premise that execution engines can sync most effectively if they are able to see the payload hashes from blocks at the immediate head of the beacon chain.
I have created an accompanying Opt. Sync Spec: Reading Companion to help explain some of my decisions.
Opt sync is a fairly tricky mechanism and it comes with some tangible risks to liveness. I would appreciate anyone who takes the time to cast a critical eye across this.
Thanks to @mkalinin, @ajsutton and @djrtwo for providing substance and feedback.

Should a previously synced / full beacon node revert back to optimistic sync if it's behind N blocks of the head? If so, what would be an appropriate number for N?

Should a previously synced / full beacon node revert back to optimistic sync if it's behind N blocks of the head? If so, what would be an appropriate number for N?

I'm not sure I completely understand the question, but after a post-merge (execution-enabled) block is justifed then the node may optimstically import a block at any time. If the node optimistically imports a block and that block becomes the head, then that node is considered "optimistic". Does that make sense, or did I miss your question?

what do you think about splitting this document into specification and rationale sections and moving your accompanying doc and fork choice poisoning description to the rationale part? This distinction should make the specification cleaner.

Yep, this makes sense. I imagine this is the same format as the current p2p-interface doc. I'll do this.

And it probably worth updating p2p-interface with the changes allowing for sending optimistic blocks via gossip and req/resp.

I hadn't considered if nodes that don't follow the optimistic spec should allow invalid payloads or not. I assume that's what you're suggesting by updating the p2p spec?
Presently, I prefer updating the Bellatrix p2p-interface spec to allow invalid payloads on gossip for all core-spec-compliant nodes (as you suggested).

Presently, I prefer updating the Bellatrix p2p-interface spec to allow invalid payloads on gossip for all core-spec-compliant nodes (as you suggested).

I think that changes to p2p-interface are necessary for the health of the network if a portion of nodes that use optimistic sync is relatively high. Imagine the case when non-optimistic-sync node drops and descores a remote peer that is in optimistic sync thus can't verify a payload of blocks it is propagating.

I have added the "Design Decision Rationale" section. Thanks everyone for the comments, I believe I have addressed them all.

I believe I have addressed all comments from @ajsutton and @djrtwo. Thanks for your review!

With the new status code (ACCEPTED and IGNORED) introduced in https://github.com/ethereum/execution-apis/pull/165, should we update them here as well?

With the new status code (ACCEPTED and IGNORED) introduced in ethereum/execution-apis#165, should we update them here as well?

Perhaps @djrtwo or @mkalinin have an opinion on if https://github.com/ethereum/execution-apis/pull/165 will merge before this PR? I don't mind either way.

Let's merge this now and patch the semantics in an updated PR.
We're aiming to merge and release the engine api changes tomorrow (1/25).
@paulhauner , can you cut a minor PR with the semantics changes to match?


Multiple code improvements: squid:ForLoopCounterChangedCheck, squid:S1066

This pull request is focused on resolving occurrences of Sonar rules
squid:ForLoopCounterChangedCheck - "for" loop stop conditions should be invariant.
squid:S1066 - Collapsible "if" statements should be merged.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:ForLoopCounterChangedCheck
https://dev.eclipse.org/sonar/rules/show/squid:S1066
Please let me know if you have any questions.
George Kankava

@georgekankava, I thought much more, or this is the first pull?
These changes are obviously ok.

@davideas Yes this is the first one.


Add quirks for _tz3210 TS011F socket

This PR adds quirks for the Mercator IKUU TS011F AC 1- and 2-gang sockets.
Fixes https://github.com/zigpy/zha-device-handlers/issues/1403

The tests are failing due to this error:
AssertionError: assert (61184 in {0: <class 'zigpy.zcl.clusters.general.Basic'>, 1: <class 'zigpy.zcl.clusters.general.PowerConfiguration'>, 2: <class 'zigpy.zcl.clusters.general.DeviceTemperature'>, 3: <class 'zigpy.zcl.clusters.general.Identify'>, ...} or False)
 +  where {0: <class 'zigpy.zcl.clusters.general.Basic'>, 1: <class 'zigpy.zcl.clusters.general.PowerConfiguration'>, 2: <class 'zigpy.zcl.clusters.general.DeviceTemperature'>, 3: <class 'zigpy.zcl.clusters.general.Identify'>, ...} = <class 'zigpy.zcl.Cluster'>._registry
 +    where <class 'zigpy.zcl.Cluster'> = zcl.Cluster
 +  and   False = <function test_signature.<locals>._check_range at 0x7f5124e9f7a0>(61184)

I'm not sure what this assert is doing so not sure how to fix this.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 80.323%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
5376

Relevant Lines:
6693

💛  - Coveralls

Codecov Report

Merging #1460 (ba11db3) into dev (bbc69c0) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #1460      +/-   ##
==========================================
+ Coverage   80.30%   80.32%   +0.01%
==========================================
  Files         227      227
  Lines        6687     6693       +6
==========================================
+ Hits         5370     5376       +6
  Misses       1317     1317

Impacted Files
Coverage Δ

zhaquirks/tuya/ts011f_plug.py
100.00% <100.00%> (ø)

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 bbc69c0...ba11db3. Read the comment docs.


Home page responsive(background img )

I've done some  changes in CSS  (@media , background image & other property)   as to make it more responsive at screen width of 868px to 1053px and also at 434px to 530px  .and also at screen width 516px to 983px "wid-main container" div box moving out of the background image that is also fixed

LGTM 🥳 Thanks for your valuable contribution!!


houdini preset-cli

It would be nice to have a preset to add houdini to an existing sveltekit app.

I didnt even know about npx houdini init, no idea how i missed that.
I´ve tested the init command with a new sveltekit project, it seems like the init command just adds the houdini.config.js and houdiniClient.js files. With a svelte-adder or preset the preprocessor, watch-and-run plugin and the houdini alias could be added aswell.
In addition an option to use either js or ts would be pretty nice, or maybe even autodetect that by looking for a tsconfig.json.
A little off topic, it would be nice to set the pull headers in the houdini.config.js and make use of env vars.

FYI 1/ new SvelteKit (after .359);

Has a problem with fetch POST
Change some config files (vite.config.js will be needed now)
=> Let's keep this out of this issue.

FYI 2/ we will update the KitQL doc to simplify the installation process with npx houdini init

We already started improving the onboarding with: https://github.com/HoudiniGraphql/houdini/pull/381
And your inputs are very valuable, thx 👍
If we manage to do the preprocessor & co directly with npx houdini init, we don't need svelte-adder or preset, correct?

If we manage to do the preprocessor & co directly with npx houdini init, we don't need svelte-adder or preset, correct?

Yes there is no need for multiple setup tools.
The init command should just create a completely working setup.


Copyright in footer doubles information

The Site.Copyright variable is used in the default RSS feed. So I have added this to my config:
copyright = "© Copyright Robert van Bregt 2003-2021"

which shows up nicely in /index.xml as
<copyright>© Copyright Robert van Bregt 2003-2021</copyright>

However, in the Ananke page footer, it now shows as
© © Copyright Robert van Bregt 2003-2021 2022

Since I think out of the box functionality should always work, my suggestion would be to modify the footer template.
I understand that this removes the functionality to show an automatically updated year number.

More changes for copyright: #449

Hi @metbril and thank you for this.
This would introduce a breaking change as most users would lose the © character from their footer. We'll probably address this is a future major release.


Error when trying to quantize GGUF.

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
pandas-stubs <IP_ADDRESS>814 requires numpy>=1.25.0; python_version >= "3.9", but you have numpy 1.24.4 which is incompatible.
tensorflow-metadata 1.14.0 requires protobuf<4.21,>=3.20.3, but you have protobuf 4.25.3 which is incompatible.
torchaudio 2.2.1+cu121 requires torch==2.2.1, but you have torch 2.1.2 which is incompatible.
torchtext 0.17.1 requires torch==2.2.1, but you have torch 2.1.2 which is incompatible.
torchvision 0.17.1+cu121 requires torch==2.2.1, but you have torch 2.1.2 which is incompatible.
Successfully installed einops-0.7.0 gguf-0.6.0 numpy-1.24.4 nvidia-cublas-cu12-<IP_ADDRESS> nvidia-cuda-cupti-cu12-12.1.105 nvidia-cuda-nvrtc-cu12-12.1.105 nvidia-cuda-runtime-cu12-12.1.105 nvidia-cudnn-cu12-<IP_ADDRESS> nvidia-cufft-cu12-<IP_ADDRESS> nvidia-curand-cu12-<IP_ADDRESS> nvidia-cusolver-cu12-<IP_ADDRESS> nvidia-cusparse-cu12-<IP_ADDRESS> nvidia-nccl-cu12-2.18.1 nvidia-nvjitlink-cu12-12.4.127 nvidia-nvtx-cu12-12.1.105 protobuf-4.25.3 torch-2.1.2 triton-2.1.0
WARNING: The following packages were previously imported in this runtime:
[numpy]
You must restart the runtime in order to use newly installed versions.

I understand that the wrong version of several dependancies are being installed from the requirements.txt of llama.cpp. Is there any way to manually set the dependancy version myself in the collab code?

Yes, you can add a line after the installation of the requirements:
!pip install your-library
On Sat, Apr 20, 2024, 17:39 Samdoses @.***> wrote:

I understand that the wrong version of several dependancies are being
installed from the requirements.txt of llama.cpp. Is there any way to
manually set the dependancy version myself in the collab code?
—
Reply to this email directly, view it on GitHub
https://github.com/mlabonne/llm-course/issues/64#issuecomment-2067724807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATL5EGS4AOHWEOI37WJH6BLY6KK33AVCNFSM6AAAAABGQTW3QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXG4ZDIOBQG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I tried installing the dependencies, but they seem to be uninstalled immediately. Is there a way to prevent this and force the code to use the updated versions instead of those specified in the requirements file?
Attempting uninstall: protobuf
Found existing installation: protobuf 3.20.3
Uninstalling protobuf-3.20.3:
Successfully uninstalled protobuf-3.20.3
Attempting uninstall: numpy
Found existing installation: numpy 1.25.2
Uninstalling numpy-1.25.2:
Successfully uninstalled numpy-1.25.2
Attempting uninstall: torch
Found existing installation: torch 2.2.1+cu121
Uninstalling torch-2.2.1+cu121:
Successfully uninstalled torch-2.2.1+cu121

Hi, have you considered using venv or conda? Looks like you got some existing deps that are unhappy with the requirements.txt that you are trying to install


more granular error reporting in Maintenance

Scope & Purpose
Add more granular error reporting to reportInCurrent maintenance function, and add lots of assertions.
This is not a bugfix, but a vehicle to simplify debugging and bug hunts.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.

Link to Jenkins PR run:
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13495/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13498/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13498/


On Paypal window close  - no onCancel event is received

When using web drop in, clicking on the paypal button opens a new window. Closing it shortly after results in the web drop in button stuck in a non-functional state. This is a smilar/if not the same issue mentioned in https://github.com/Adyen/adyen-web/issues/290 hence the same steps can be used to reproduce;

Load the web drop in with PayPal
Click the PayPal button
Wait for the window to open
Close the window

Expected behavior
At least an event to be triggered so that we can refresh the web drop in state and the user can attempt the payment flow again
Experienced on desktop Mac OSX Chrome

Hi @kappy904
Thanks for reaching out. The Paypal onCancel on adyen-web goes through the onError callback. As documented here,  onError manages different types of errors, which one of them is the CANCEL one.
When PayPal triggers the onCancel on its SDK, adyen-web will trigger the onError with that error type.
Regardless of that, I discussed with the team and we are going to update the docs to make it clear how is the flow for this case. I hope it helps!


Fix get features from hologres error.if primay key type is not string…

…, so convert it

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.丁静 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Not updating width until mouse move

I am switching between tabs and populating them with different information. I call the update function but it doesn't seem to 'update' until I move the mouse over the scrollbar. The scrollbar doesn't seem to properly 'initialize' until i move the mouse as well?
Just wondering if there is anything I should be doing differently?
It is controlling an angular app but don't think that part of it should be a problem.
Thanks
Dan

Try this "add-on directive":
.directive('psMouseOver', function () {
return {
link: function(scope, element) {
element.bind("mouseover", function(e){
e.stopPropagation();
e.preventDefault();
element.perfectScrollbar('update');
});
}
}
});
Just apply it as an attribute on the  ...

@sorenhoyer Thanks. It helps


test(bench): Auto-detect iterations by default and per framework

Current coverage is 98.27% (diff: 100%)

Merging #931 into master will decrease coverage by 1.72%

@@           master       #931   diff @@
========================================
  Files          31         31
  Lines        1975       1975
  Methods         0          0
  Messages        0          0
  Branches      325        311    -14
========================================
- Hits         1975       1941    -34
- Misses          0         26    +26
- Partials        0          8     +8

Powered by Codecov. Last update 12ddc48...97a2646