[SMALLFIX]Convert semaphore to unfair

If a thread read, then it hold the read lock and don't unlock, then another thread want to write lock, as we all know, this thread will never get the lock, but a third thread want to get the read lock, it also never get the lock if we set the semaphore to fair. So i set it to unfair to let other read thread get read lock.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14137/
Test PASSed.

@maobaolong  if we set it to unfair, how do we avoid thread starving?
https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Semaphore.html

@apc999 Thank you for answer my problem.
And i see INode.mLock use the default constructor to new instance. mLock = new ReentrantReadWriteLock();, so mLock is unfair too, why don't set it to fair lock?

@maobaolong thanks for the explanation. From some testing result, it seems nonfair locks will slightly fav read locks, while fair locks  benefits write locks (as it approximates FIFO order and late-coming readers will not block previous writers).  That's why you can find for master journals we use fair locks to coordinate. In the case of ClientRWLock, this is on the worker side to coordinate block readers with operations like eviction (from one tier to another tier). In this case, we really want to minimize the eviction as it may be on the critical path of some other writers. I would stay with fair lock for this purpose, unless there are strong reasons this fair locks are bottlenecks and changing them to unfair can help. Have you done experiments for those workloads?

@apc999 Very grateful to receive your apply again.

That's why you can find for master journals we use fair locks to coordinate as it is write-heavy you want to say  master journals we use no fair locks ?
I want to convert to no fair lock because this situation:

A client read block and exception take place and the client never release the connection between client and worker, the effect is a session hold the read lock forever and give heartbeat as healthy, the worker's sessionCleaner never think this session timeout.
A shell cli command free the file which is reading by the bad client and master accept the request and tell the worker execute the free command when the worker heartbeat, the worker execute free command as normal, but it cannot get the write lock when free block.
A man who want to see the file's part content in web browse page, or execute cat command, even those are read operation, but because we use no fair lock here, so that those have to wait the previous command who want to free the file, and due to the bad client and the no fair lock, this block will never readable or writable.

@apc999 what do you think of this PR?

@maobaolong I think the explanation makes sense.
@yupeng9  I am good with this PR. One final request from me is to update this PR with comment explaining the reason we choose non-fair locks. Especially, you can state that "ALLUXIO-2636" is related to this. This will help us understand and recall the decision in the future:)
thanks for the improvement.

@apc999  PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14318/
Test PASSed.

@yupeng9 PTAL. Thank you.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14333/Build result: FAILURE[...truncated 4161 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/pom.xml to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.5.0-SNAPSHOT/alluxio-examples-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.5.0-SNAPSHOT/alluxio-examples-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.5.0-SNAPSHOT/alluxio-examples-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/pom.xml to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/pom.xml to org.alluxio/alluxio-core-server/1.5.0-SNAPSHOT/alluxio-core-server-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/pom.xml to org.alluxio/alluxio-underfs/1.5.0-SNAPSHOT/alluxio-underfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/integration/pom.xml to org.alluxio/alluxio-integration/1.5.0-SNAPSHOT/alluxio-integration-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/dependency-reduced-pom.xml to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/target/alluxio-core-protobuf-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/target/alluxio-core-protobuf-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/pom.xml to org.alluxio/alluxio-keyvalue/1.5.0-SNAPSHOT/alluxio-keyvalue-1.5.0-SNAPSHOT.pomchannel stopped
Test FAILed.

Just found worker removeBlock method kept waiting hours from jstack... I'll try set back fair to see if it happens. FYI @apc999

"block-removal-service-9" #101 daemon prio=5 os_prio=0 tid=0x00007f08381d1800 nid=0x23428 waiting on condition [0x00007f07f0532000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x000000008092aaa8> (a java.util.concurrent.Semaphore$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at java.util.concurrent.Semaphore.acquireUninterruptibly(Semaphore.java:494)
at alluxio.worker.block.ClientRWLock$SessionLock.lock(ClientRWLock.java:92)
at alluxio.worker.block.BlockLockManager.lockBlock(BlockLockManager.java:114)
at alluxio.worker.block.TieredBlockStore.removeBlockInternal(TieredBlockStore.java:791)
at alluxio.worker.block.TieredBlockStore.removeBlock(TieredBlockStore.java:328)
at alluxio.worker.block.TieredBlockStore.removeBlock(TieredBlockStore.java:322)
at alluxio.worker.block.DefaultBlockWorker.removeBlock(DefaultBlockWorker.java:435)
at alluxio.worker.block.AsyncDeletionService$BlockRemover.run(AsyncDeletionService.java:91)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

@Reidddddd I think you should check which thread hold the semaphore<0x000000008092aaa8>

@Mitisky Checked of course, no other thread was holding 0x000000008092aaa8.

Checked Fair mode. Workers still have that problem, i'll file a JIRA for this.

@Reidddddd I met a similar situation,but waiting at different position.I changed the lock which solved my problem. may this help you.https://github.com/Alluxio/alluxio/pull/7296


Update FED readme to include typical workflow for working with statics

The current FED readme doesn't outline the typical workflow for making CSS/JS changes.

Workflow updated here https://github.com/praekeltfoundation/molo-gem/blob/feature/fed-workflow-webpack-implementation/FED.md


Remove the need of Authorization when X-...-Authorization is used

As discussed with @edewit and @gastaldi, our support for Gitea, as a workaround, use this Authorization to secure the request to Gitea (that uses impersonation with admin). We need to find a solution for this specific case and remove the need of it when X-...-Authorization is used.

This is not for Gitea only. Any Impersonation feature needs the logged user, including OpenShift


Issue with test

Package
filament/filament
Package Version
v3.0.19
Laravel Version
latest
Livewire Version
lateest
PHP Version
latest
Problem description
when running pest test it shows:
Call to a member function auth() on null (View: /home/ngoquocdat/Workspace/polycasts/storage/framework/views/a168b0ebcff266df6b662fc4b6d06e88.blade.php)

  at vendor/filament/filament/src/FilamentManager.php:50
     46▕     protected ?Model $tenant = null;
     47▕
     48▕     public function auth(): Guard
     49▕     {
  ➜  50▕         return $this->getCurrentPanel()->auth();
     51▕     }

my pest code:
it('can render page', function () {
    $this->actingAs(\App\Models\User::factory()->create());

    livewire(ListPosts::class)->assertSuccessful();
});

Expected behavior
pass
Steps to reproduce
Run the above Pest code and it wills show the error
Reproduction repository
https://github.com/datlechin/filament
Relevant log output
No response

No reproduction repo. Please don't be lazy

This worked for me:
Try adding this line to you config/app.php
App\Providers\Filament\AdminPanelProvider::class

I have the same issue.
this is my code:
<?php
namespace Tests\Feature;

use function Pest\Livewire\livewire;
it('creates admin',function () {
        livewire(\App\Filament\Resources\AdminResource\Pages\CreateAdmin::class)
        ->fillForm([

        ])
        ->call('create')
        ->assertHasNoFormErrors();
    }
);

and this is my repository:
https://github.com/amirrezashahidi83/risman-admin


Make Nautobot a general-purpose framework

As ...
P.D. - Plugin Developer
I want ...
Nautobot to be implemented as a "general-purpose" Python framework
So that ...
I can develop non-network infrastructure projects that do not include Network Infrastructure components ('dcim', 'ipam', 'virtualization', etc.).
I know this is done when...
Nautobot can be used as a general-purpose Python framework to develop ANY projects, including projects that do not include network components.
ADDITIONAL DETAILS
At the moment, few network components ('dcim', 'circuits', 'ipam', 'virtualization', etc.) are tightly "built-in" Nautobot framework, automatically making these components being part of any project that uses Nautobot. Separating these components "out" of the core framework (making them non-required "plugins" so to speak) - will allow Nautobot to become a "general-purpose" framework that can be used for any project implementation including non-network related projects.
This will significantly increase support and use of this framework - making it much more popular by attracting non-network Python development community.
Optional - Feature groups this request pertains to.

[X] Automation
[ ] Circuits
[ ] DCIM
[ ] IPAM
[X] Misc (including Data Sources)
[X] Organization
[X] Plugins (and other Extensibility)
[X] Security (Secrets, etc)
[X] Image Management
[X] UI/UX
[X] Documentation
[X] Other (not directly a platform feature)

Database Changes
Everything is already in place. All that's needed - is to make network components "pluggable", non-required components.
External Dependencies
No response

Thanks for the submission @vpogrebi. Do you have any example projects or use cases where you'd like to see Nautobot expand into as a more generic SoT platform?

Absolutely, @bryanculver !
My Nautobot experience started when I was part of NIDM (Network Infrastructure Domain Model) project team at BoFA (that contains few Network to Code developers) led by John Anderson - and I've come to love Nautobot. My contract at BoFA ended, and I got job at Paramount (its CBS Interactive part) - in a team that manages Paramount's Content Distribution Network (CDNs) and everything related to it. This is fully cloud-based infrastructure, so there is no internal network infrastructure to carry out content distribution.
I am trying to convince this team to rewrite its existing implementation (non-Django based, no UI, etc.) using Nautobot (which can perfectly be used for this - if not for built-in network components). My thought is that Nautobot in general can be used for ANY project implementation - where Django can be used.
BTW...

Please let me know if this can be done, and how son one can expect it to be implemented.
I would not want to use this framework for our team's CDN implementation - unless we can have home HTML and main menu void of network infrastructure related items (which we are not going to use).
On the other hand, if this is done and I succeed in convincing the team to use this framework - we may be able to contribute CDN (Content Distribution Network) plugin implementation.


[release-0.2] Updating versions, common files and dependecies

versions.yaml was updated so it contains versions from 0.1 release + the latest for 1.22, 1.23, 1.24
common files were updated from release-1.24
dependencies were updated from release-1.24
istio modules in go.mod were set to v1.24.1

/retest

@FilipB: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_release-0.2
df7b9faacdfd3a8d8c26e58bd672d82412791883
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


add PingCheck

This PR adds the PingCheck, it can be used to check if your application can reach other hosts. It can be configured like this
OK::checks([
    PingCheck::config()
        ->address('www.google.com')
        ->maxTimeout(100), // milliseconds
]);

If they are not set, address and the max timeout will be set to www.google.com and 100 by default respectively.

Lekker bezig @dulkoss!


Minimum go version - 1.14?

The go.mod indicates it requires go 1.14, but I see this was just added .
https://github.com/envoyproxy/protoc-gen-validate/blob/master/go.mod#L3
I'm curious if this is the only blocker to supporting earlier versions (1.12.7, in my case) ?

I think that's the only blocker. There was a PR out that would downgrade that to go 1.12 I think?

Ha, yeah, I made the PR. It's been merged :)
https://github.com/envoyproxy/protoc-gen-validate/pull/376


dart2js crash on co19 test

The following co19 test produces CRASH on dart2js. Output is
stdout:
tests/co19/src/LanguageFeatures/Constructor-tear-offs/mixin_A01_t01.dart:42:1:
Internal Error: The compiler crashed when compiling this element.
main() {
^
The compiler is broken.

When compiling the above element, the compiler crashed. It is not
possible to tell if this is caused by a problem in your program or
not. Regardless, the compiler should not crash.

The Dart team would greatly appreciate if you would take a moment to
report this problem at http://dartbug.com/new.

Please include the following information:

* the name and version of your operating system,

* the Dart SDK build number (build number could not be determined), and

* the entire message you see here (including the full stack trace
  below as well as the source location above).

The compiler crashed: Unsupported operation: Unexpected constant ConstructorTearOffConstant(C.named) (ConstructorTearOffConstant).
#0      ConstantImpactVisitor.defaultConstant (package:compiler/src/ir/impact.dart:759:5)
#1      VisitOnceConstantVisitor.visitConstructorTearOffConstant (package:kernel/visitor.dart:1041:7)
#2      _ConstantCallbackVisitor.visitConstructorTearOffConstant (package:kernel/visitor.dart:861:17)
#3      ConstructorTearOffConstant.accept (package:kernel/ast.dart:13103:42)
#4      VisitOnceConstantVisitor.visitConstant (package:kernel/visitor.dart:1006:12)
#5      ImpactBuilderBase.handleConstantExpression (package:compiler/src/ir/impact.dart:683:10)
#6      StaticTypeVisitor.visitConstantExpression (package:compiler/src/ir/static_type.dart:1799:5)
#7      ConstantExpression.accept (package:kernel/ast.dart:8188:44)
#8      StaticTypeBase.visitNode (package:compiler/src/ir/static_type_base.dart:78:18)
#9      StaticTypeVisitor.visitFunctionInvocation (package:compiler/src/ir/static_type.dart:997:32)
#10     FunctionInvocation.accept (package:kernel/ast.dart:5678:44)
#11     StaticTypeBase.visitNode (package:compiler/src/ir/static_type_base.dart:78:18)
#12     StaticTypeVisitor._processLocalVariable (package:compiler/src/ir/static_type.dart:1781:24)
#13     StaticTypeVisitor.visitVariableDeclaration (package:compiler/src/ir/static_type.dart:1791:5)
#14     VariableDeclaration.accept (package:kernel/ast.dart:10282:43)
#15     StaticTypeBase.visitNode (package:compiler/src/ir/static_type_base.dart:78:18)
#16     StaticTypeVisitor.visitBlock (package:compiler/src/ir/static_type.dart:1311:22)
#17     Block.accept (package:kernel/ast.dart:8736:43)
#18     StaticTypeBase.visitNode (package:compiler/src/ir/static_type_base.dart:78:18)
#19     StaticTypeVisitor.visitProcedure (package:compiler/src/ir/static_type.dart:1735:5)
#20     Procedure.accept (package:kernel/ast.dart:3036:40)
#21     KernelToElementMapImpl.computeWorldImpact (package:compiler/src/kernel/element_map_impl.dart:1437:12)
#22     KernelWorkItem.run.<anonymous closure>.<anonymous closure> (package:compiler/src/kernel/kernel_strategy.dart:403:47)
#23     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#24     KernelWorkItem.run.<anonymous closure> (package:compiler/src/kernel/kernel_strategy.dart:402:28)
#25     CompilerTask.measure (package:compiler/src/common/tasks.dart:66:51)
#26     KernelWorkItem.run (package:compiler/src/kernel/kernel_strategy.dart:377:26)
#27     Compiler.emptyQueue.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:574:70)
#28     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#29     Compiler.emptyQueue.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:574:32)
#30     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#31     Compiler.emptyQueue.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:572:28)
#32     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:863:15)
#33     Compiler.emptyQueue.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:570:18)
#34     ResolutionEnqueuer._forEach (package:compiler/src/enqueue.dart:449:12)
#35     ResolutionEnqueuer.forEach (package:compiler/src/enqueue.dart:465:5)
#36     Compiler.emptyQueue.<anonymous closure> (package:compiler/src/compiler.dart:566:16)
#37     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#38     Compiler.emptyQueue (package:compiler/src/compiler.dart:565:14)
#39     Compiler.processQueue.<anonymous closure> (package:compiler/src/compiler.dart:591:7)
#40     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#41     Compiler.processQueue (package:compiler/src/compiler.dart:584:14)
#42     Compiler.computeClosedWorld (package:compiler/src/compiler.dart:403:5)
#43     Compiler.compileFromKernel.<anonymous closure>.<anonymous closure> (package:compiler/src/compiler.dart:516:17)
#44     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#45     Compiler.compileFromKernel.<anonymous closure> (package:compiler/src/compiler.dart:515:44)
#46     CompilerTask.measureSubtask (package:compiler/src/common/tasks.dart:181:35)
#47     Compiler.compileFromKernel (package:compiler/src/compiler.dart:514:14)
#48     Compiler.runInternal (package:compiler/src/compiler.dart:321:15)

<asynchronous suspension>

--- Re-run this test:
python3 tools/test.py -n dart2js-hostasserts-strong-linux-x64-chrome --dart2js-batch co19/LanguageFeatures/Constructor-tear-offs/mixin_A01_t01

/cc @rakudrama - seems like our impact computation needs to be updated for the new nodes as well?

@sigmundch - who's the right owner for this?

Fixed by 81839ddcc1b.


Auto crafting gets ahead of itself

Issue description:
Auto crafting will try to craft 1 item in the middle of crafting another, and it halts the auto crafting process completely.
What happens:
When crafting a improved processor, I had no printed silicon and no printed improved processors. I started auto crafting an improved processor, and the system started making the printed silicon first, so it put the gold into the center slot of the solderer and started making the printed improved processor, then it put in the silicon and started making the printed silicon. About half way through the printed silicon it decided to start making the improved processor, and added the printed improved processor and redstone to the solderer. This completely stalled it as the center slot was filled with silicon and the recipe was no longer valid.
What you expected to happen:
I should be able to click start auto crafting and leave my system alone for 30 mins while I do other stuff and not come back to nothing having been auto crafted because it got stuck half way through (I have noticed it do it with other recipes too, I am a lazy man and usually just let the system create every component from complete scratch, the basest of base materials)
Steps to reproduce:

Put silicon, gold, and redstone in the system
Add an autocrafter facing a solderer with recipes to create the printed silicon, printed improved processor, and improved processor.
Craft a decent amount ( tested with 10+ )
Right click solderer and wait for it to mess up

Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>2
Refined Storage: 1.0.4

Does this issue occur on a server? [yes/no]
Single Player and LAN Server
Image of solderer inventory: https://i.imgur.com/qDlD7DK.png

Will fix this ASAP for the next release


Provide package on maven-central / package on jcenter outdated

Hello world,
I've learned about seq and serilogj in the last few month and I'm currently using it with a custom sfl4j-appender in my spring-boot projects.
I would really look forward (and gladly invest some time on my own) to see an updated package being available in maven-central.
Do you have plans for this in the near future?
If not - though I never have published a lib on my own - I could dig into this and we can use this ticket to drive this forward.
Cheers, Max

Hi @stampedev, thanks for the offer!
I think the best option for consuming this package with Maven is directly from GitHub Packages - see e.g.:
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry#installing-a-package
Does this help? I'm not familiar enough with Maven Central or the surrounding infrastructure to know whether this is a viable alternative so keen to know more.
Best regards,
Nick

Hi Max, thanks for your reply and all of the interesting info.
Looks like the groupid requirement would be handled using:

In the case of Github, Gitee, Bitbucket or similar groupIds (io.github.username), you must create a temporary, public repository named OSSRH-TICKETNUMBER. Check the details in the Coordinates document.

I have rights in the organisation to create the repo, if you're interested in working through the others details?
Best regards,
Nick

Hi Nick,
sure, I'll gladly help with the rest. I just found another good tutorial for orientation over here
Just to be sure, next steps would be

I create a request ticket for us on https://issues.sonatype.org/browse/OSSRH and report back with the repo URL
you create the public repo required for ownership verification
I create a fork, make changes to pom and github-actions accordingly, create a PR
you create/provide the secret for gpg-keypair/pwd as well as sonatype user/pwd and approve the PR
you test the workflow

Still some additional thoughts

as mentioned, in the end, you would be in charge of gpg and sonatype additionally, that ok with you?
groupId needs to change regardless, that ok for everyone?

Kind regs,
Max


libsqlite3-sys 0.24 has a CVE and needs to be upgraded

Bug Description
A CVE was posted on libsqlite3-sys <0.25:
error[vulnerability]: `libsqlite3-sys` via C SQLite CVE-2022-35737
    ┌─ /n/nvme1/nstinus/src/givre/Cargo.lock:130:1
    │
130 │ libsqlite3-sys 0.24.2 registry+https://github.com/rust-lang/crates.io-index
    │ --------------------------------------------------------------------------- security vulnerability detected
    │
    = ID: RUSTSEC-2022-0090
    = Advisory: https://rustsec.org/advisories/RUSTSEC-2022-0090
    = It was sometimes possible for SQLite versions >= 1.0.12, < 3.39.2 to allow an array-bounds overflow when large string were input into SQLite's `printf` function.

      As `libsqlite3-sys` bundles SQLite, it is susceptible to the vulnerability. `libsqlite3-sys` was updated to bundle the patched version of SQLite [here](https://github.com/rusqlite/rusqlite/releases/tag/sys0.25.1).
    = Announcement: https://nvd.nist.gov/vuln/detail/CVE-2022-35737
    = Solution: Upgrade to >=0.25.1
    = libsqlite3-sys v0.24.2
      └── sqlx-core v0.6.2
          ├── sqlx v0.6.2
          │   └── klb-givre-rime v0.11.0
          └── sqlx-macros v0.6.2
              └── sqlx v0.6.2 (*)

Minimal Reproduction
Configure a project with sqlx and invoke cargo deny.
Info

SQLx version: 0.6.2
SQLx features enabled: sqlite
Database server and version: sqlite 3.40.1
Operating system: centos 7
rustc --version: rustc 1.67.1 (d5a82bbd2 2023-02-07)

This has already been updated on the 0.7-dev branch. It can't be fixed in 0.6.x because updating libsqlite-sys is currently a breaking change

Why is that a breaking change for the 0.6 branch? I could not find anything in libsqlite3-sys or SQLite release notes that hint at a break.

See this comment
https://github.com/launchbadge/sqlx/pull/2094#issuecomment-1247312357

Fair enough. Thank you.


add tooltips to reduction parameters

Each parameter has a separate description field.  These can be fed through rst2html and provided as a list of html tags for each field that pops up when the user is entering values for the field.
This will allow users to see the deprecated notice on the join tolerance parameter.

I can do this pretty quick, but right now the client is only getting a plain description string for each module parameter as part of the instrument definition.  If you want to ship another string "description_html" or if you just want to replace what's in "description" with an rst2html output that might work.
The standard tooltip doesn't have html formatting anyway (it's just the title attribute of the html tag being hovered) so maybe it's not necessary to change.


Added WASM implementation to simde_mm_div_ps in SSE.h and all mm_div_…

…* functions of SVML.h

Merged, thanks!


Import task never begins

Trying to import user data...
My CSV (for testing) is as simple as this
email, username, highSchool
<EMAIL_ADDRESS><EMAIL_ADDRESS>PAULDING HIGH SCHOOL
<EMAIL_ADDRESS><EMAIL_ADDRESS>ROYAL CITY HIGH SCHOOL
<EMAIL_ADDRESS><EMAIL_ADDRESS>ENTERPRISE
<EMAIL_ADDRESS><EMAIL_ADDRESS>RIVERSIDE

Using emailAsUsername so including username data as a precaution, recommended on another issue. Everything seems to detect mapping correctly.

Upon starting the import, nothing happens. A task is created, but never starts. It will remain on "pending" indefinitely. No other tasks exist, so no stuck tasks preventing. There is nothing showing up in Craft logs (no log files for import plugin exist).
Craft 2.6.2797
Import 0.8.32

Looks like a Craft issue to me. Have you set runPendingTasksAutomatically to false?

I have not. Other tasks begin & run in entirety just fine.

As long as it's pending, the import hasn't even started. You should contact Craft support initially.

I tracked this down to being an issue with Laravel Valet, which I'm using for my development environment and some incompatibility with how the tasks kick off. Not quite sure what exactly is the difference is with Valet, or why some tasks work fine and others don't, but running the site through MAMP resolves my issue with Import.

Just an update: I've resolved the issue through a couple added lines in the plugin explained here: http://craftcms.stackexchange.com/questions/16096/tasks-either-dont-start-or-dont-run-as-background-processes-on-valet-caddy-se/16097
Given that Valet (and Caddy Server) are relatively new & gaining popularity, it might bea fix that could be added to core by P&T (unless it has some negative unrealized implications).


feat: merge version v1.0.0

Description
Merge bdjuno version v1.0.0

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

:exclamation: No coverage uploaded for pull request base (v2/cosmos/v0.44.x@0ce926f). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##             v2/cosmos/v0.44.x     #330   +/-   ##
====================================================
  Coverage                     ?   57.29%
====================================================
  Files                        ?       19
  Lines                        ?     1351
  Branches                     ?        0
====================================================
  Hits                         ?      774
  Misses                       ?      479
  Partials                     ?       98


[e2e]: container-based push main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7649702700
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Thu Jan 25 04:06:34 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7663811650
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Fri Jan 26 04:19:26 UTC 2024
Tests are passing now. Closing this issue.


Document all the new RESIN_  env vars from supervisor v2.5

RESIN_APP_NAME
RESIN_APP_RELEASE
RESIN_DEVICE_NAME_AT_INIT
RESIN_DEVICE_TYPE
RESIN_HOST_OS_VERSION
 Front conversations

closed by #395


SelectMenu ignoring initial object values

Environment

Operating System: Linux
Node Version:     v20.14.0
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Version
Pro 1.4.1
Reproduction
https://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue
Description
When using a v-model prop with some initial object values (such as fetched already selected data from backend), the <USelectMenu> component doesn't show these as selected and seems to ignore them completely.
Even when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.
Additional context
The behaviour changes when setting the by prop. In my case, I set it to id, after which I can see the object as selected, but only in the dropdown.
This also allows me to edit the data as normal. (Select/Deselect)
However the button itself still shows 0 selected.
Logs
No response

It seems like the same problem as issue 2028

I suggest using by when your v-model is an object or an array of objects. This is because this component currently doesn't work when comparing objectA === objectB.


Fix UI ( Large PR )

Categories were using Mudchipset which allowed them to visually indicate them as being 'selected'.
This is a feature we do not support and is a visual bug that is addressed in this PR.
Before:

After:

They are no longer selectable.

looks good 🤞🏽


Handle multiple Cloudflare DNS01 challenges for the same FQDN

Pull Request Motivation
The current implementation of the Cloudflare DNS01 challenge provider does not function as expected when validating multiple Let's Encrypt certificates simultaneously. The Present function deletes any existing TXT record under the FQDN; therefore, if there is another ongoing challenge under the same FQDN (e.g., by following CNAME), the newest challenge overwrites the previous challenge while it is still being validated by Let's Encrypt.
This MR removes the Cloudflare delete record API call from the Present function and always works with only the record matching the FQDN and value.
The fix was tested on our staging cluster with over 100 FQDNs. Challenge records were cleaned up, and all certificates were successfully validated by Let's Encrypt.
Kind
bug
Release Note
Fixed Cloudflare DNS01 challenge provider race condition when validating multiple domains

/kind bug
/ok-to-test

Looks good to me, I don’t think cloudflare is e2e tested so I will have to take your word for it that it works!


Pp 9466 send node internal metrics

WHAT
Add pay-metrics class based on the RFC in pay-decisions: https://github.com/alphagov/pay-frontend/pull/2792
The expectation would be to later extract this class into pay-js-commons for reuse among all node-apps.
One of the goals is to hide that it's statsd under the hood from the user of the metrics class so in future we could replace the metrics backend with something else.
The primary goal though right now is to reintroduce the node garbage collector and event loop stats, and replace the abandoned metrics npm module.
HOW
For now (while this is draft) the node tests should pass (which include the new tests added against the pay-metrics class.
Also the e2e tests should be relied upon to show the docker build is still ok after the changes to include the required dependencies to build the native modules for event-loop-stats and gc-stats, both of which require c++ native code.

Closing this PR as it's gone stale


Add a timeout mechanism?

This looks like a great package. I am considering using it but I think it lacks a key feature.
Have you considered adding a timeout mechanism to automatically close connections from the pool after a certain amount of time?
For example, a pool with a timeout of 30 seconds would automatically close connections that have been in the pool for more than 30 seconds.
Having such a mechanism would reduce the risk of getting stale connections from the pool and help decreasing the number of unused open connections with a server when the traffic slows down.
What do you think?

I think this can be done fairly with setting the various fields in net.Dialer and then creating connection according to those. Did you tried it ? There is no need to carry that logic into the pool mechanism itself.

I don't think you can do it with net.Dialer.
And even if it would be possible I think it would be nice for the stale connections to be automatically removed from the pool to avoid returning them to the user with Pool.Get.

The problem is that there is no single way of knowing what a stale connections is. The only way of doing it to try to read from it (peek) and then unread it. I really don't want to put this logic into it. What you need is to wrap it around another net.Conn interface implementation that supports it. Checkout the code, we already wrap the net.Conn.

I am not sure I made myself clear: I don't want a mechanism that check if a connection is stale.
I think what I want was better explained in my first post.
Basically I was thinking of something like a MaxAge parameter for the Pool. When you use PoolConn.Close() a deadline parameter of PoolConn is set to now + Pool.MaxAge.
And when you use Pool.Get, if it is past PoolConn.deadline. The PoolConn is automatically closed and you get the first PoolConn in the Pool which deadline has not passed. (This is a rough description, a background goroutine closing the PoolConn with a past deadline would be more appropriate).
Is it more clear?
If you don't think this is in the scope of this package, no problem!

I got what you mean but to implement this. We have to implement a timer that always runs in background and closes all connection inside the pool. That means first of all that we have to lock the channel (stop anyone to retrieve from it) and then check whether each connection has hit the 30 second timeout or not.  We close all connections that timed out and then release the lock.
I think this is not suitable and against the idea of having a pool. What's the idea of a pool if I close connections every 30 seconds ? This package just gives you a primitive, and that's it. Introducing logic into the primitive will make it just worse. You can always fork this and implement it yourself btw, it's pretty stable and I'm not interested to improve it anymore (Because there is not much anymore to improve).

Ok I understand.


jackson's byte[] -> base64 serialization breaks

Hi,
just found out that mongodb isn't able to handle the base64 encoded object that is produced out of byte[] by jackson.
I'd be happy to fix this right now. Could you give me a hint where and what I can do?
Cheers
Christian

Firstly write a unit test to reproduce.  There are two different parsers, the stream parser, that uses bson4jackson, and one that converts maps, and the unit tests automatically test both.  If it's not serialising properly, then write a new JsonSerializer, registered in the Serializers class, that handles byte[], and calls writeObject() on the generator (I think bson4jackson can handle this, but not sure).  If it's not parsing correctly, then you may need to register a new deserialiser for byte[].  I'm also happy to implement this myself, so if you'd rather me do it, just let me know.

Ok, have a look at my latest commit. It shows the same error message as our current project. I also found out that it only happens when calling getSavedObject() on the WriteResult. But I wasn't able to fix it myself, I'm still too much newbe in your code :-/
Commit:
https://github.com/CupSoftware/mongo-jackson-mapper/commit/04ead536f6fcd60d80951db55ad8e2764167dc1c
Error:
Tests in error:
testSaveAndReturnstream: Don't know how to parse type: class [B

WARNING: emptying DBPortPool to <IP_ADDRESS>:27017 b/c of error
java.io.EOFException
	at de.undercouch.bson4jackson.io.LittleEndianInputStream.readFully(LittleEndianInputStream.java:116)
	at de.undercouch.bson4jackson.io.LittleEndianInputStream.readFully(LittleEndianInputStream.java:108)
	at de.undercouch.bson4jackson.BsonParser.handleBinary(BsonParser.java:388)
	at de.undercouch.bson4jackson.BsonParser.nextToken(BsonParser.java:241)
	at org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:693)
	at org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:580)
	at org.codehaus.jackson.map.ObjectMapper._readValue(ObjectMapper.java:2695)
	at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1308)
	at net.vz.mongodb.jackson.internal.stream.JacksonDBDecoder.decode(JacksonDBDecoder.java:62)

WARNING: emptying DBPortPool to <IP_ADDRESS>:27017 b/c of error
java.io.EOFException
	at de.undercouch.bson4jackson.io.LittleEndianInputStream.readFully(LittleEndianInputStream.java:116)
	at de.undercouch.bson4jackson.io.LittleEndianInputStream.readFully(LittleEndianInputStream.java:108)
	at de.undercouch.bson4jackson.BsonParser.handleBinary(BsonParser.java:388)
	at de.undercouch.bson4jackson.BsonParser.nextToken(BsonParser.java:241)
	at org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:693)
	at org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:580)
	at org.codehaus.jackson.map.ObjectMapper._readValue(ObjectMapper.java:2695)
	at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1308)
	at net.vz.mongodb.jackson.internal.stream.JacksonDBDecoder.decode(JacksonDBDecoder.java:62)


scrapper crashes on container

Followed the README for the container:
docker run --volume /data/:/phet/dist:rw openzim/phet:latest /bin/bash -c "cd /phet && npm i && npm start"

and got the following output:
npm WARN<EMAIL_ADDRESS>No repository field.

><EMAIL_ADDRESS>start /phet
> npm run setup && npm run get && npm run transform && npm run export

><EMAIL_ADDRESS>setup /phet
> node steps/setup.js

><EMAIL_ADDRESS>get /phet
> node_modules/ts-node/dist/bin.js steps/getCategory.ts

Starting build
Got list of 0 simulations to fetch... Here we go!
 Linux 4.16.12
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "export"
npm ERR! node v6.10.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>export: `node_modules/typescript/bin/tsc && node_modules/browserify/bin/cmd.js res/js/index.js  -t babelify --presets [es2015] -o res/js/dist.js && node_modules/ts-node/dist/bin.js steps/export.ts`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>export script 'node_modules/typescript/bin/tsc && node_modules/browserify/bin/cmd.js res/js/index.js  -t babelify --presets [es2015] -o res/js/dist.js && node_modules/ts-node/dist/bin.js steps/export.ts'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phetscraper package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node_modules/typescript/bin/tsc && node_modules/browserify/bin/cmd.js res/js/index.js  -t babelify --presets [es2015] -o res/js/dist.js && node_modules/ts-node/dist/bin.js steps/export.ts
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs phetscraper
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls phetscraper
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /phet/npm-debug.log

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'npm run setup && npm run get && npm run transform && npm run export'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phetscraper package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run setup && npm run get && npm run transform && npm run export
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs phetscraper
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls phetscraper
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /phet/npm-debug.log

As suggested in the above logs, I tried to update node and npm before starting the process
docker run --volume /data/:/phet/dist:rw openzim/phet:latest /bin/bash -c "cd /phet && npm cache clean -f && npm install -g n && n stable && npm install -g npm@latest && npm i && npm start"

Got the following output
npm WARN using --force I sure hope you know what you are doing.
/usr/local/bin/n -> /usr/local/lib/node_modules/n/bin/n
/usr/local/lib
└──<EMAIL_ADDRESS>

     install : node-v10.15.3
       mkdir : /usr/local/n/versions/node/10.15.3
       fetch : https://nodejs.org/dist/v10.15.3/node-v10.15.3-linux-x64.tar.gz
   installed : v10.15.3

/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
/usr/local/bin/npx -> /usr/local/lib/node_modules/npm/bin/npx-cli.js
+<EMAIL_ADDRESS>added 54 packages from 9 contributors, removed 15 packages and updated 47 packages in 29.877s
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No repository field.

up to date in 19.97s

><EMAIL_ADDRESS>start /phet
> npm run setup && npm run get && npm run transform && npm run export

><EMAIL_ADDRESS>setup /phet
> node steps/setup.js

fs.js:136
    throw new ERR_INVALID_CALLBACK();
    ^

TypeError [ERR_INVALID_CALLBACK]: Callback must be a function
    at makeCallback (fs.js:136:11)
    at Object.mkdir (fs.js:721:14)
    at /phet/steps/setup.js:10:16
    at FSReqWrap.args [as oncomplete] (fs.js:140:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>setup: `node steps/setup.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-05-15T08_48_26_722Z-debug.log

Is the container broken or am I using it wrong?

This line is suspicious: Got list of 0 simulations to fetch... Here we go!
When I run without Docker I get 1675 simulations to fetch
When I run in Docker I get the same thing you get

Will try to fix that today

@ISNIT0 I have updated to nodejs12 and last version of modules.  It is commited on git master. The stuff works for me locally but I alway s get the following error in the Docker container:
res/js/index.ts(13,9): error TS2687: All declarations of 'languages' must have identical modifiers.

Any idea?
 Linux 4.15.0-48-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "export"
npm ERR! node v6.10.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>export: `node_modules/typescript/bin/tsc && node_modules/browserify/bin/cmd.js res/js/index.js  -t babelify --presets [es2015] -o res/js/dist.js && node_modules/ts-node/dist/bin.js steps/export.ts`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>export script 'node_modules/typescript/bin/tsc && node_modules/browserify/bin/cmd.js res/js/index.js  -t babelify --presets [es2015] -o res/js/dist.js && node_modules/ts-node/dist/bin.js steps/export.ts'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phetscraper package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node_modules/typescript/bin/tsc && node_modules/browserify/bin/cmd.js res/js/index.js  -t babelify --presets [es2015] -o res/js/dist.js && node_modules/ts-node/dist/bin.js steps/export.ts
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs phetscraper
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls phetscraper
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /phet/npm-debug.log

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'npm run setup && npm run get && npm run transform && npm run export'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phetscraper package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run setup && npm run get && npm run transform && npm run export
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs phetscraper
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls phetscraper
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /phet/npm-debug.log

Building a docker image with the latest code and running seems to be working fine.
@kelson42 Can we try re-publishing a docker image?

👍 starts properly for me as well. @kelson42 ?

great, new image built on Docker hub


[BUG] Trapezohedron rounding adjusted_scale issue.

Describe the bug
Trapezohedrons are not being rescaled after adding a 'rounding=' parameter. The other polyhedra behave as expected.
Code To Reproduce Bug
include <BOSL2/std.scad>
include <BOSL2/polyhedra.scad>

$fn=$preview ? 12 : 40;

difference(){
    regular_polyhedron("trapezohedron",faces=10, side=8, longside=18, anchor=BOTTOM);
    regular_polyhedron("trapezohedron",faces=10, side=8, longside=18, anchor=BOTTOM, draw=false)
        down(.3) linear_extrude(height=1)
        text(str($faceindex),size=8,halign="center",valign="center");
}

right(30)
difference(){
    regular_polyhedron("trapezohedron",faces=10, side=8, longside=18, anchor=BOTTOM, rounding=2);
    regular_polyhedron("trapezohedron",faces=10, side=8, longside=18, anchor=BOTTOM, draw=false)
        down(.3) linear_extrude(height=1)
        text(str($faceindex),size=8,halign="center",valign="center");
}

back(30) {
    difference(){
        regular_polyhedron("octahedron", side=22, anchor=BOTTOM);
        regular_polyhedron("octahedron", side=22, anchor=BOTTOM, draw=false)
            down(.3) linear_extrude(height=1)
            text(str($faceindex),size=8,halign="center",valign="center");
    }

    right(30)
    difference(){
        regular_polyhedron("octahedron", side=22, anchor=BOTTOM, rounding=2);
        regular_polyhedron("octahedron", side=22, anchor=BOTTOM, draw=false)
            down(.3) linear_extrude(height=1)
            text(str($faceindex),size=8,halign="center",valign="center");
    }
}

Expected behavior
In the example above I expect the rounded trapezohedron to be the same size as the non-rounded version, and be flush with z=0. The increased size also obscures text added to faces.

There was a bug with computation in inradius, outradius and midradius for trapezohedron which affected rounding.  Now fixed.

There was a bug with computation in inradius, outradius and midradius for trapezohedron which affected rounding.  Now fixed.


Smart contract  deployment and testing

Description

 Created Helpers
Utils Tx, Constants, Deployment Funtions
Removed files js  because they can't deploy we will  look at it and refactor
Changed Solidity Version, Default Named Count
Worked On Deploy Mocks

Smart contract deployment and testing

Fixed Merge Conflict


[FEATURE] Support attrs in RUF008 and RUF009

These rules guard against using mutable default values in dataclasses. It would be nice if these rules also supported attrs,  which is the (more feature-rich) predecessor which is also pretty widely used.
If this is something that you'd be open for, I think I can get some time to potentially contribute a patch myself.

Makes sense!

@alanhdu - Do you mind if I assign this one to you?

No problem! I am busier than I thought and it'll probably at least another week before I get to this, but do plan on getting to this "soon".

Cool, thanks! No worries and no rush.

I was recently bit by the lack of these rules working with attrs. So I also wish to see this implemented please. Thanks.

Ah yes, sorry -- I have gotten distracted by other things at work. I hopefully will still get to this "at some point", but if anyone else has time they should feel free to implement it themselves.


[build-iso] Add "latest" tag if not specified

If there is no specific tag for the container image,
add "latest" as tag version.
Fixes #219
Signed-off-by: Michal Jura<EMAIL_ADDRESS>

I believe this will break build-iso command. The behavior of this command is based on the logic found in
https://github.com/rancher/elemental-cli/blob/1554b61fd1642611bb7517196b873156377171b5/pkg/utils/common.go#L439-L455

@davidcassany I agree, I was confused after reading source code and finding that elemental build-iso can take Image|Directory|Channel. It seems that we have update also documentation because it says that https://github.com/rancher/elemental-cli/blob/main/docs/elemental_build-iso.md elemental build-iso IMAGE
Ok, I will rework this change. Thank you for your comment

I'd just wait for @davidcassany to have a look as he reviewed that from the beginning and had some comments. Otherwise looks good to go for me, I'm just guessing some parts of CI might need to be adapted? but I might be wrong

@davidcassany I have implemented this according to your ideas, fixed tests and it seems that it works fine. Please review once again


Added Spanish translation

@jamiew pretty sure this can work, but we may want a native speaker to give it a once over and make sure everything is idiomatically correct.
As an example, I used the word "intervalo" for time "slot", but native speakers may have better slang for it.

Note I preserved the existing punctuation for consistency's sake.

Holy cow, you are amazing. Testing this out now


Kubernetes secrets

I believe I am having a similar issue as this discussion
This is my setup :

React + Vite;
Docker;
Kubernetes;

So my application is using secrets from Kubernetes and passes them as arguments to Docker using the secret flag.
That's where my issue is, my env variables are not defined and therefore cannot be accessed by import-meta-env.
Any help would be much appreciated

You should NEVER expose secrets to clients.

Hey sorry, i wasnt clear, my env doesnt contain secrets but anyway, i managed to solve the issue.
I had an issue with your docker example, the bash script was throwing an error saying it couldn't find import-meta-env-alpine even though it was present.
I managed to make it work with your docker-compose example>
Thanks for the tool, it's great !


Fail on AESDD data

Hi @Neclow,
I failed to build AESDD dataset using your recipe
(serab) bagus@pc-omen:aesdd$ tfds build
2022-11-16 16:56:17.762030: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-11-16 16:56:17.850300: E tensorflow/stream_executor/cuda/cuda_blas.cc:2981] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2022-11-16 16:56:18.243007: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/home/bagus/miniconda3/envs/serab/lib/:/var/lib/docker/overlay2/b2c6c735b823297983b5e6d11c64147f8307a4ece255c7f36276dd9066cf8142/diff/usr/lib/x86_64-linux-gnu/
2022-11-16 16:56:18.243052: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/home/bagus/miniconda3/envs/serab/lib/:/var/lib/docker/overlay2/b2c6c735b823297983b5e6d11c64147f8307a4ece255c7f36276dd9066cf8142/diff/usr/lib/x86_64-linux-gnu/
2022-11-16 16:56:18.243059: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2022-11-16 16:56:19.449061: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:980] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2022-11-16 16:56:19.454121: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudnn.so.8'; dlerror: libcudnn.so.8: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: :/home/bagus/miniconda3/envs/serab/lib/:/var/lib/docker/overlay2/b2c6c735b823297983b5e6d11c64147f8307a4ece255c7f36276dd9066cf8142/diff/usr/lib/x86_64-linux-gnu/
2022-11-16 16:56:19.454137: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1934] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
INFO[build.py]: Loading dataset  from path: /home/bagus/github/SERAB/tensorflow_datasets/aesdd/aesdd.py
2022-11-16 16:56:19.457076: W tensorflow/core/platform/cloud/google_auth_provider.cc:184] All attempts to get a Google authentication bearer token failed, returning an empty token. Retrieving token from files failed with "NOT_FOUND: Could not locate the credentials file.". Retrieving token from GCE failed with "FAILED_PRECONDITION: Error executing an HTTP request: libcurl code 6 meaning 'Couldn't resolve host name', error details: Could not resolve host: metadata".
INFO[build.py]: download_and_prepare for dataset aesdd/1.0.0...
INFO[dataset_builder.py]: Generating dataset aesdd (/home/bagus/tensorflow_datasets/aesdd/1.0.0)
Downloading and preparing dataset Unknown size (download: Unknown size, generated: Unknown size, total: Unknown size) to /home/bagus/tensorflow_datasets/aesdd/1.0.0...
INFO[download_manager.py]: Reusing extraction of /home/bagus/tensorflow_datasets/downloads/manual/Acted Emotional Speech Dynamic Database.zip at /home/bagus/tensorflow_datasets/downloads/extracted/ZIP.Acted Emotional Speech Dynamic Database.zip.
Extraction completed...: 0 file [00:00, ? file/s]
Generating splits...:   0%|                                       Traceback (most recent call last):                                                          | 0/3 [00:00<?, ? splits/s]
  File "/home/bagus/miniconda3/envs/serab/bin/tfds", line 8, in <module>
    sys.exit(launch_cli())
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/scripts/cli/main.py", line 126, in launch_cli
    app.run(main, flags_parser=_parse_flags)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/absl/app.py", line 308, in run
    _run_main(main, args)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/absl/app.py", line 254, in _run_main
    sys.exit(main(argv))
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/scripts/cli/main.py", line 121, in main
    args.subparser_fn(args)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/scripts/cli/build.py", line 199, in _build_datasets
    _download_and_prepare(args, builder)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/scripts/cli/build.py", line 355, in _download_and_prepare
    builder.download_and_prepare(
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/dataset_builder.py", line 439, in download_and_prepare
    self._download_and_prepare(
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/dataset_builder.py", line 1155, in _download_and_prepare
    split_info_futures = [
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/dataset_builder.py", line 1156, in <listcomp>
    split_builder.submit_split_generation(  # pylint: disable=g-complex-comprehension
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/split_builder.py", line 291, in submit_split_generation
    return self._build_from_generator(**build_kwargs)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/split_builder.py", line 361, in _build_from_generator
    utils.reraise(e, prefix=f'Failed to encode example:\n{example}\n')
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/split_builder.py", line 359, in _build_from_generator
    example = self._features.encode_example(example)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/features/features_dict.py", line 198, in encode_example
    utils.reraise(
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/features/features_dict.py", line 196, in encode_example
    example[k] = feature.encode_example(example_value)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/features/audio_feature.py", line 97, in encode_example
    utils.reraise(e, prefix=f'Error for {filename}: ')
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/features/audio_feature.py", line 95, in encode_example
    return self._encode_file(audio_f, file_format)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/tensorflow_datasets/core/features/audio_feature.py", line 75, in _encode_file
    audio_segment = lazy_imports_lib.lazy_imports.pydub.AudioSegment.from_file(
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/pydub/audio_segment.py", line 728, in from_file
    info = mediainfo_json(orig_file, read_ahead_limit=read_ahead_limit)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/site-packages/pydub/utils.py", line 279, in mediainfo_json
    info = json.loads(output)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/bagus/miniconda3/envs/serab/lib/python3.8/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Failed to encode example:
{'audio': '/home/bagus/tensorflow_datasets/downloads/extracted/ZIP.Acted Emotional Speech Dynamic Database.zip/Acted Emotional Speech Dynamic Database/anger/a16 (2).wav', 'label': 'anger', 'speaker_id': '2'}
In <Audio> with name "audio":
Error for /home/bagus/tensorflow_datasets/downloads/extracted/ZIP.Acted Emotional Speech Dynamic Database.zip/Acted Emotional Speech Dynamic Database/anger/a16 (2).wav: Expecting value: line 1 column 1 (char 0)

I am wondering what tensorflow version you used to build the dataset. Mine used TF 2.10. Also, the requirement of tensorflow is not stated in serab.yaml

Hi @bagustris
SERAB does not use tensorflow. It requires tensorflow-datasets==4.3.0 and tensorflow-hub==0.12.0 to load datasets and pretrained models, but its DL framework is pytorch==1.9.0.
I just checked using the demo notebook and had no problem with AESDD (link to the Colab notebook: https://colab.research.google.com/drive/1LoLQxMxJ9tEdSvRwofhV1bTeY_YHV-Wx?usp=sharing).
Is your error only related to AESDD, or do you end up with the same error with other datasets?
I hope this can be of some help.

Thanks @Neclow,
I can reproduce your Colab without error.
Seems there are different configurations on local and Colab.
I got the following error when running tfds build (tensorflow_datasets=4.3.0) locally, complaining
about tensorflow (but no error on using Colab):
Failed to import TensorFlow. Please note that TensorFlow is not installed by default when you install TFDS.
This allow you to choose to install either `tf-nightly` or `tensorflow`.
Please install the most recent version of TensorFlow,
by following the instructions at https://tensorflow.org/install.

Then I installed the newest tensorflow, TF2.1
Finally I can solve this issue for aesdd by creating new venv using python3.7 (looking python version on the colab).
As shown in my first report, the error is related to json in python3.8.
I also have an error with emovo with the following message:
...
    shape1.assert_same_rank(shape2)
  File "/home/bagus/miniconda3/envs/pt1.9-py37/lib/python3.7/site-packages/tensorflow/python/framework/tensor_shape.py", line 1043, in assert_same_rank
    (self, other))
ValueError: Failed to encode example:
{'audio': '/home/bagus/tensorflow_datasets/downloads/extracted/ZIP.emovo.zip/EMOVO/m3/gio-m3-n2.wav', 'label': 'happiness', 'speaker_id': 'm3'}
In <Audio> with name "audio":
Error for /home/bagus/tensorflow_datasets/downloads/extracted/ZIP.emovo.zip/EMOVO/m3/gio-m3-n2.wav: Shapes (139264, 2) and (None,) must have the same rank

I believe this error is related to tensorflow version since I use the newest TF2.1 as the default installation via pip install tensorflow.

It might be worth comparing your current installation of Tensorflow with the one in Colab?
Currently, Colab uses TF 2.9.2 (cf. the link to the Colab notebook in my previous message).
Otherwise, I do remember having one "faulty" or irregular sample in a dataset, but I can't remember which sample/dataset.
For your errors, while I'm not sure it's the "prettiest" fix, a solution would be ensure that all samples in a dataset are all mono or stereo (this is what I get from your error messages in EMOVO and RAVDESS. For instance, in RAVDESS, some samples are mono (shape: (None,)), and some are stereo (shape: (203403, 2)).
I've uploaded a quick gist to convert stereo files to mono files in case you need one, but I haven't used in a while so it might be buggy: https://gist.github.com/Neclow/c0c0531137f98ec05deac3740d8a8329.
Hope that helps!

Thanks for providing the clue @Neclow,
I previously suspect this error since the SUBESCO code contains the suffix "_mono" (in subesco.py). I can confirm now the building of all datasets by tfds has success. Some modifications are needed, especially to collect that path and the speaker information after appending "_mono" to the original file names.

Thanks for the comment! Could you please indicate what changes you would make?
I guess the easiest is to:

In the README, indicate that the user should ensure that all samples for a given dataset are all mono or stereo, and add the stereo_to_mono in SERAB.utils.py as an example of how to do that
Remove the "_mono" suffix in subesco.py (maybe confusing)

I will make a PR if you allow it.
The idea is like this:
Download the original dataset as it is --> do some pre-processings --> run SERAB.
It will be easy to reproduce.

Yes please feel free to do a PR!

I'm closing this issue as it has been inactive for over a month. I updated the README with a comment on how to preprocess the audios before using TFDS + added the stereo_to_mono gist in SERAB.utils.


Add CI for upgrades between all supported minor versions

What would you like to be added:
Add CI to test upgrades from 0.12.x to 0.13.y to 0.14.z to devel. There are a number of different ways this could be built for slightly different coverage.

0.x.0 to 0.y.0
0.x.latest to 0.y.latest
0.x.0...latest to 0.y.0...latest (every release from the first release of 0.x to the latest of 0.y)

This should likely be a periodic job, to supplement the 0.x.latest to 0.x.devel jobs currently run on PRs.
Why is this needed:
While writing docs about upgrades for submariner-io/submariner-website#625, it became clear we don't test many upgrades users are likely to actually do.

https://github.com/submariner-io/get.submariner.io/issues/23 will be helpful, but it would also be nice if we could somehow leverage the API URL sort order trick and subtract 1 or 2 from the version to enable other upgrade tests without maintaining versions in CI.

We might be able to use PR's target branch as a signal to know which versions to test dynamically.


Major Package Refactor

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


"make flash monitor" doesn't work till manual reboot

If i use the command make flash monitor to flash and after monitor the UART, the serial monitor only starts to spit out something after I manually reattached the ESP32 board.
In menuconfig, I configured to reset the board after flashing.
I use the the following ESP32 breakout board from Watterott.
Does anyone have an idea how to fix this behavior?

Hi elia,

What host OS are you running on?
Does anything happen if you press and release the "EN" button on the board, instead of manually removing and reattaching?

I use macOS 10.12.3.
The EN button doesnt work either to make the UART start spitting out data.

I am hitting a similar issue on macOS 10.11.6. Pressing EN and boot hasn't been working recently.
Physically reattaching the usb and then doing the normal Boot > EN button dance reliably allows the board to flash. To be clear this issue occurs before the board has successfully flashed.

As of yesterday there's a new tool, "idf monitor", which adds some new features around monitoring & resetting devices:
http://esp-idf.readthedocs.io/en/latest/idf-monitor.html
This may help with these issues. (For one, the new idf_monitor explicitly tries to reset the board each time it starts up.)

I just tried the new idf monitor. (its very nice 💯 )
The problem however stays. If I hit ctrl-T ctrl-F, the new firmware gets compiled, flashed and then the promt outputs Leaving... Hard resetting...
After that, now serial output gets displayed until I manually reattach the dev board.

Thansk @eliabieri . That's bad news.
Unfortunately in that case this sounds like a problem with the reset circuit wiring on the board you have. Our Espressif boards don't have any problem soft-resetting (including from macOS, a number of developers use this OS). Please ask the hardware manufacturer to review their design.
(If you happen to find a modification to the monitor tool which works and doesn't break other boards, we'd be happy to look at merging it.)

You are right. I try the ESPRESSIF DEV-KIT C now. Thanks for the help anyway.

@eliabieri @projectgus The problem is a CP2102N driver issue under MacOS and Silabs is currently looking after it. Here are further infos: http://community.silabs.com/t5/Interface/CP2102N-Strange-Issue/td-p/190476

Thanks for filling us in @awatterott. Very glad it's been tracked down.

The CP2102N issue happens (on Mac and Linux), when the serial port is closed and re-opened immediately. As workaround a short pause between the uploading and monitoring seems to fix it and the waiting can be done in the esptool.py upload tool: https://esp32.com/viewtopic.php?f=13&t=1287#p7637

I had the same problem on Windows 10. It's for sure a CP2102N driver issue. I detailed the problem and the solution/workaround (same as for Linux/MacOS) at https://www.silabs.com/community/interface/forum.topic.30.15.html/cp2102n_strange_issu-Sd3I

Hi @mlinaje,
Sorry this got a bit lost on this closed issue. If you're still needing to patch esptool.py with the latest SiLabs Windows drivers then can you please open an issue with some more details on the esptool repo: http://github.com/espressif/esptool/issues
The forum post suggests that introducing a 0.1s delay was enough to work around the issue with the older MacOS drivers, in which case we can probably add this in esptool without causing any major inconveniences.


Use relative URLs for GEOS-ESM packages

I'll wait to see if the CircleCI test succeeds before making a label...

It worked! Huzzah!


fix: omit default replicas on Kubernetes Deployment

What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes: #2807

What if I set replicas at EnvoyProxy CR and enabled HPA too, we should have a priority over them.

What if I set replicas at EnvoyProxy CR and enabled HPA too, we should have a priority over them.

it is described in https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#migrating-deployments-and-statefulsets-to-horizontal-autoscaling, that's why I add a note on the docs string @Xunzhuo

@ardikabs can we also add a CEL validation to disable hpa and replicas from being set at the same time ?
this can alway be overriden using the patch field in case someone really wants to

@ardikabs can we also add a CEL validation to disable hpa and replicas from being set at the same time ?

if we add CEL validation, are we not trying to match Kubernetes behavior?


What optimizer is used to replace the FusedEmaAdam on the NPU device?

System Info / 系統信息
I am trying to sft on NPU device. However, the FusedEmaAdam relies on cuda, which is not available on NPU device.
So, what optimizer is used to replace the FusedEmaAdam on the NPU device?
Information / 问题信息

[X] The official example scripts / 官方的示例脚本
[ ] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
AttributeError: 'FusedEmaAdamBuilder' object has no attribute 'multi_tensor_ema_adam'
Expected behavior / 期待表现
Run sft successfully on NPU device

I am not very familiar with the acceleration of ADAM on NPU and have not tried it, so we may not be able to provide an effective equivalent operation. @tengjiayan20 Can you give some idea?

@tengjiayan20 Thanks，I tried，it's okay.But I have another question.Now, I have four cards, i want ask for some help, how can i run sft for  multi card in  single machine. How to modify  the envs in finetune script? Such as WORLD_SIZE=1 RANK=0 LOCAL_RANK=0 LOCAL_WORLD_SIZE=1。

@tengjiayan20 Thanks，I tried，it's okay.But I have another question.Now, I have four cards, i want ask for some help, how can i run sft for multi card in single machine. How to modify the envs in finetune script? Such as WORLD_SIZE=1 RANK=0 LOCAL_RANK=0 LOCAL_WORLD_SIZE=1。 @tengjiayan20 @zRzRzRzRzRzRzR

Should I run 4 different finetune process with different LOCAL_RANK in 4 device?

If you are using SAT, you can directly control it with CUDA_VISIBLE_DEVICES=0,1,2,3. The rank will default to 0.


ALCS-2325 Tag/Category entities and cruds

Created Category and Tag entities
Basic API CRUD functions

Looking good overall! Impressed you took on such an ambitious ticket this early. My only sort of general comment would be to use more type annotations in the services and controllers. I feel like the majority of the issues I encounter day-to-day are due to ambiguous typing.


[RFC] Assets hashing

As I said on Discord, I wanted to write a ppx for static assets hashing and cache bursting.
The idea is like this:
let css_url = [%assets "style.css" ]

In normal mode: return the string as is.
In release mode: Copy style.css to style.content_hash.css and return style.content_hash.css
Ppx would throws when file isn't exists

However after careful consideration, I decided that it would be a runtime library rather than build time.
Here are some reasons I can think of:

Decoupled between backend and frontend build.
-> Parallel build
-> Re-deploy frontend codes without compiling the backend again
It's really annoying during development when I have a watcher to re-generate assets and build fails because the file isn't exists.
This allows us to easily using CDN/ switching CDN at runtime.

What I am proposing would be configuration file in JSON format like this:
{
  prefix: "/" // this could be CDN URL or absolute path to where you mount your static assets
  assets: {
    "style.css":  "style.content_hash.css",
    "script.css": "script.content_hash.css"
  }
}

How is this loaded is up to the implementor, could be a file during application start up, could be via POST request.
TODO:

[ ] Write the runtime script
[ ] Figure out the hashing algorithm to do content hashing (look at what webpack/rollup is using). Prefer something that's written in pure OCaml for easy packing
[ ] Write asset hashing executable
[ ] Publishing

What do you think?

On the other hand, using a build time approach, one could inline the content of small images directly to string like webpack/rollup does.
Or one could write a ppx that does different things based on the arguments. But I don’t know how to write ppxes that is more complex than replacing a string with a string 😂

On the topic of hashing, rollup uses

xxhash (32/64): https://github.com/314eter/ocaml-xxhash
metrohash (no ocaml bindings that I can find)

It all looks feasible. It looks largely independent from Dream itself. We would basically just call out from templates (or anywhere else) to some library to figure out the real name of an asset, right? I guess that library would need to know how to read the output of the hasher, and serve as the "runtime library" linked into server deployments.

@aantron yes. It should work independent of dream but I only interested in build for dream right now. So I want to open discussions here and looking for comments/feedbacks on the design


anticlockwise tangents for void

Hi, I imported a .iges format file and defined a void. In the void I see the orientation of tangents in clockwise direction. How can I make them anticlockwise to run simulation? Thanks

V1_D25-20-8Trennwand.igs.txt
V1_D25-20-8Trennwand.geo.txt
?

I am able to create tangents in anticlockwise direction by deleting and creating new curves but still I get below error in .OUT file:

VOID # 1
It is made of   76 frontiers.

ERROR from subroutine PROPVOID.
This void has a frontier described clockwise.
Only Counter clockwise description is allowed.

Did you look at the Issue https://github.com/gmsafir/gmsafir/issues/5 ?
Please, upload your .g4s file

yes. Infact, after reading it I changed the the orientation of tangents to counter clockwise. In attachment there are new files
V1_D25-20-8Trennwand.geo.txt
V1_D25-20-8Trennwand.igs.txt
V1_D25-20-8Trennwand.g4s.txt
.

when displaying the normals, you can see on image below that there are 2 problems:

the zone marked in yellow is not defined as a surface (no label when displaying the elementary tags in surface labels);
the surfaces 2 and 3 at frontier of the void are not in the anticlockwise orientation

ok I need to make changes again.  Isnt there a direct way of flipping the directions of normals?

When you start a geometry from scratch in .geo file and you know there are voids, you can care at initial stage of a correct orientation of the neighbouring surfaces and of the void perimeter. Unfortunately, when you import a geometry (igs...) you need to correct by flipping one by one the uncorrect normals

I modified the geometry. The arrow pointing in direction as yours but getting the error.

VOID # 1
It is made of   80 frontiers.

ERROR from subroutine PROPVOID.
This void has a frontier described clockwise.
Only Counter clockwise description is allowed.

V1_D25-20-8Trennwand.g4s.txt
V1_D25-20-8Trennwand.geo.txt

The message that appears in SAFIR talks about VOIDS and then SAFIR stops, because the check on the VOIDS is made in SAFIR before the check on the finite elements.
But, in this case, the problem comes first from the definition of the finite elements in several surfaces (I mean, those which contain material and will be meshed). You can detect the problem:

either in GmSAFIR when you see that the normal to some surfaces are not pointing in the same direction as others. SAFIR can not run if this is the case because the finite elements will be numbered correctly in some surfaces and not in others. I don't see the axes of coordinates in the picture above but, in GmSAFIR, the normal to the surface must point in the positive direction of Z in a 2D  Thermal problem.
or in DIAMOND after you ran SAFIR. Plots the mesh (make it as crude as possible) and the node numbers. Put the mouse in one finite element, watch in the spy the 3 nodes that define the element and see if the order is counter clockwise (OK) or clockwise (not OK). All finite elements that belong to the same surface of GmSAFIR will have the same orientation in Diamond, either OK or not OK.

If you don't define the surfaces that contain material properly, there is very little hope that the definition of the VOID can be correct.
Indeed, the void is defined in SAFIR by the borders of the finite elements, either border 1, 2 or 3 in triangular elements. Even if the void is defined in GmSAFIR by lines which are in the appropriate direction, the borders of the finite elements in the mesh will be in the wrong direction if the finite elements are defined in the wrong order.
=> Solve the problem of orientation of the normal in all surfaces before you come back to the definition of the VOIDS.

In order to simplify the life of the users, a new version of SAFIR has been created (2022.a.3) in which the frontier that define the VOID can be listed in any order, anticlockwise or clockwise. These frontier don't even have to be adjacent to each other.
This version will be released probably tomorrow (13/09/2022).


config.services.xserver.dpi

A new rebuild gave a error regarding config.services.xserver.dpi (sorry can't remember, but the message mentioned setting the option.
It is not (at least yet) in the options search. Instead services.xserver.upscaleDefaultCursor is returned.

https://search.nixos.org/options?channel=unstable&show=services.xserver.dpi&from=0&size=50&sort=alpha_asc&type=packages&query=services.xserver.dpi ?


Optimize and refactor the link insertion

The steam-insert-org-* functions are now several orders of magnitude faster (improvement from about half a minute, to not even a second with about 1000 games). Additionally both functions were refactored with the code duplication removed.
Note: While the image links don't render for me, I left the markup unchanged and didn't touch it in case the problem is on my side. Please confirm the markup was correct in the first place.

Excellent, thank you! The images has been working for me, but I discovered now that they do not. My guess would be that it is a change in one of the latest org-mode versions. Perhaps something like that a link can not have an image as description, not sure. I'll see if I can find a solution for this.
I noticed that you missed documentation for steam-insert-link, so I'll add that in another commit. You also do need to autoload it, since it isn't a command (interactive).


Cloud code doesn't automatically parse File objects

Issue Description
When uploading a ParseFile as a parameter to cloud code it does not automatically parse the object and transform it into the ParseFile on the cloud code side. On parse.com it would do this automatically. Essentially I could save a file on the client and then pass the ParseFile as a parameter in a cloud call and then on the cloud side it would show up as a ParseFile. Documented here: https://parse.com/docs/rest/guide#objects-data-types . Instead the cloud side just sees a normal JSON object that would represent a ParseFile. Even using the Parse Client JS SDK has the same problem.
To further muck up the situation, parse-server allows these JSON objects to be saved in File columns but when they are retrieved they are still a basic JSON object and calling .url() causes the server to spin forever and never complete the request.

Was this functionality intentionally removed?
While its fine that it doesn't automatically convert to a ParseFile, the Parse SDK doesn't provide a way to create a Parse.File manually from such a JSON structure. Any thoughts?

Steps to reproduce

Run code such as:

var parseFile = new Parse.File("theFile", document.getElementById("theFile").files[0]);
parseFile.save().then(function(file){
   Parse.Cloud.run("cloudFunction", {file:file})
})

Expected Results
Parse.Cloud.define("cloudFunction", function(request, response) {
 response.success(request.params.file instanceof Parse.File);
})

request.params.file instanceof Parse.File === true;
Actual Outcome
request.params.file instanceof Parse.File === false;
Environment Setup

Server

parse-server version: 2.2.14
Localhost or remote server? Azure

Database
N/A -- Completely parse-server software issue

Logs/Trace
Outcomes above should be detailed enough.

That seems to be valid, do you want to try to fix it?

Ha, didn't see that coming. I haven't actually compiled the source myself.
I could have a look if you can give me an idea which file deals with parsing the request parameters?

@smassin this is a community project :)
We already have a parse for Dates, https://github.com/ParsePlatform/parse-server/blob/master/src/Routers/FunctionsRouter.js#L63
Need to add a new Parser for files.

I can give it a go, that seems pretty straight forward

Thanks I appreciate it.

Confirmed working. Thanks a lot @flovilmart :+1:


Alamofire can't execute the request in conjunction with AlamofireImage

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
import UIKit
import Alamofire
import AlamofireImage

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    let sessionManager = Alamofire.SessionManager.default

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {

        // ** Comment this line out to see that the request can be executed **
        UIImageView.af_sharedImageDownloader = ImageDownloader(sessionManager: sessionManager)

        sessionManager.request("https://httpbin.org/get").responseJSON { response in
            switch response.result {
            case .success(let value):
                print(value)
                break
            case .failure(let error):
                print(error)
                break
            }
        }

        return true
    }
}

What did you expect to happen?
Request is completed.
What happened instead?
No request is made.
Alamofire Environment
Alamofire version: 4.5.1
Xcode version: 9.0
Swift version: 4.0
Platform(s) running Alamofire: iOS
macOS version running Xcode: 10.12.6
Demo Project
The code is shown above. Comment out the line with UIImageView.af_sharedImageDownloader = ImageDownloader(sessionManager: sessionManager) to see that the request can complete.

Yes, ImageDownloaders set the SessionManager to not start its requests immediately, so you'd have to manually resume the request made. It's an unfortunate side effect. However, you should be able to configure to SessionManagers identically if you need the same behaviors on both sides. Or just manually start your requests. We'll be refactoring AFI as a whole once we release Alamofire 5, so this may change in the future.


Dropped tables can not be physically removed if syncAllSchema is trigger frequently

Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)

Run the following SQLs repeatedly
CREATE TABLE if not exists test_range_1 (id INT,name VARCHAR(20))
PARTITION BY RANGE (id) (PARTITION p0 VALUES LESS THAN (10),PARTITION p1 VALUES LESS THAN (20),PARTITION p2 VALUES LESS THAN (30),PARTITION p3 VALUES LESS THAN (40),PARTITION p4 VALUES LESS THAN (50);

CREATE TABLE if not exists test_swap_1 (id INT,name VARCHAR(20));
ALTER TABLE test_range_1 EXCHANGE PARTITION p0 WITH TABLE test_swap_1;
DROP TABLE test_swap_1;

2. What did you expect to see? (Required)
The dropped table can be successfully removed from tiflash instances
3. What did you see instead (Required)
The dropped tables' IStorage instances remain in TiFlash even after the gc_safepoint is exceed than the drop timepoint + gc_lifetime.
More and more ".sql" files of the dropped tables' remain in TiFlash instance disk. TiFlash sync all schema become more and more slower.
4. What is your TiFlash version? (Required)
v6.5.10

In the previous versions

Repeatedly execute the given SQLs. The rapidly swap and dropped table_id will lead to some warnings like "miss table" or "miss partition table in TiKV" with "Errors::DDL::StaleSchema"
https://github.com/pingcap/tiflash/blob/28a2314dd36fc1e990b9d8a3a6aec89ba8a220b8/dbms/src/TiDB/Schema/SchemaBuilder.cpp#L871-L877

When tiflash meet exception in tryLoadSchemaDiffs, tiflash will fallback to loadAllSchema to fetch all tables info from TiKV.
https://github.com/pingcap/tiflash/blob/28a2314dd36fc1e990b9d8a3a6aec89ba8a220b8/dbms/src/TiDB/Schema/TiDBSchemaSyncer.h#L159-L164

In SchemaBuilder::syncAllSchema, each table that does not exists in tikv but still in the tiflash instance. TiFlash will execute applyDropPhysicalTable for each table, wich will update the "tombstone_ts" of the table in its ".sql" file.
Even if the table is already "tombstone", the function will update the "tombstone_ts" by a newer tso from PD. This make the IStorage instance still exist even after the gc_safepoint is exceed than the drop timepoint + gc_lifetime.
https://github.com/pingcap/tiflash/blob/28a2314dd36fc1e990b9d8a3a6aec89ba8a220b8/dbms/src/TiDB/Schema/SchemaBuilder.cpp#L1437-L1451
https://github.com/pingcap/tiflash/blob/28a2314dd36fc1e990b9d8a3a6aec89ba8a220b8/dbms/src/TiDB/Schema/SchemaBuilder.cpp#L1240-L1268

/report customer

Close as it will be fixed in the next patch version of release-6.5 and release-7.1. v7.5 or later are not affected.


FixAVX 512 build under VS2015

Related to #421

:tada:

@JohanMabille green again! I feel like the green vador of AVX512

Should we go ahead and merge this?

Not yet.

I feel like the green vador of AVX512

cc @JohanMabille https://github.com/xtensor-stack/xsimd/pull/451/commits/28e1b625837274c3911bb038fee7118728c4a8a2 passes validation, which validates the AVX512 implementation fallbacks, according to me.
Once you confirm, I'll revert that one last commit and we should be ready to merge.

I confirm!

Awesome!

This seems to have fixed our build issues. Thank you!


Configure the git mirror service and use it

Ok, this fails, so don't merge yet. Doing some more testing.

Ok, with the above commits I have tested that it all works.


Wrong data after restore.

vuex-persistedstate version: 4.1.0
node version: 14.15.4
npm (or yarn) version: 6.14.10

Relevant code or config:
export const state = () => ({
  colorScheme: {
      base: {"bg-color-primary": true},
      light: {"bg-color-primary-light": true},
      dark: {"bg-color-primary-dark": true}
    }
})

export const mutations = {
  changeColor(state, colorName) {
    state.colorScheme.base = {"bg-color-orange": true};
    state.colorScheme.light = {"bg-color-orange-light": true};
    state.colorScheme.dark = {"bg-color-orange-dark": true}
  }
}

What you did:

Install package and use default plugin from readme (Example with Nuxt.js)
Called mutation
Reloaded browser

What happened:

Localstorage restored after window reload, BUT, it has following states:

{
  "base": {
    "bg-color-primary": true,
    "bg-color-orange": true
  },
  "light": {
    "bg-color-primary-light": true,
    "bg-color-orange-light": true
  },
  "dark": {
    "bg-color-primary-dark": true,
    "bg-color-orange-dark": true
  }
}

// Following data was in localstorage before reload
{
  "base": {
    "bg-color-orange": true
  },
  "light": {
    "bg-color-orange-light": true
  },
  "dark": {
    "bg-color-orange-dark": true
  }
}

Problem description:

Store being restored, but it has merged default objects in store with restored ones.

May I say:
U are using a mutation to do three updates, consider using an action
Next of, u are setting a default state, that state will always be used on start, and if you have updates, things will get merged. If they were not, a lot of other use cases would fail.
Is your localstorage updated with the default, or does it live in you vuex object?
In any way, you could use sometinhg like the overwrite attribute of the API.  Or look for another option, if the "error" is in the plugin, you could find the fix for your case there.