Support for hypre mixedint

This PR should add support for hypre built with the option --enable-mixedint, e.g. allow local sizes to use 32bit integers and global sizes to use 64bit integers.
I added an initial guess of changes and I hope that we get a group of contributors that go through a group of files and check for errors or add changes.
Right now the code branch does not compile without changes. What I did locally was commenting out the complex operator files. With that ex1p runs fine in serial and parallel.
If you participate and want to compile individual files, I recommend using the makefile build system and specifying the file you are working on with
make fem/pfespace.o

this way you only get the errors from the file you are looking at.
I'd especially like to see someone help with the complex stuff, since I'm not comfortable just churning through the files. @dylan-copeland @mlstowell @psocratis
TODO:

[x] In INSTALL, document that mixed-int support requires hypre >= 2.20.0

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1583
@jandrej
@tzanio
@v-dobrev + @dylan-copeland + @psocratis
04/20/21
⌛due 04/27/21
⌛due 04/30/21

@jandrej , I think I found all of the BigInt changes in complex_operator and complex_fem.  If you notice any other issues I'd be glad to help.
Thanks or tackling this!

Thanks! Compiles fine, make test shows problems with HypreParMatrixBlocks and
    NURBS miniapp [ mpirun -np 4 nurbs_ex11p ... ]: FAILED  (0.13s 17768kB)
Options used:
   --mesh ../../data/star.mesh
   --refine-serial 2
   --refine-parallel 1
   --order '0'
   --num-eigs 5
   --seed 75
   --no-visualization
Mesh::GeneratePartitioning(...): edgecut = 39
Mesh does not have FEs --> Assume order 1.
Number of unknowns: 1361

===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 18902 RUNNING AT dyro.llnl.gov
=   EXIT CODE: 11
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault: 11 (signal 11)

This is not testing problems larger than MAX_INT yet.

That looks like something @dylan-copeland will want to take a look at. I'm not familiar with HypreParMatrixBlocks but I see a couple places where row and column offsets are treated as integer arrays.  The number of non-zeros might also cause a problem.

This branch doesn't seem to compile with HYPRE version 2.12.0 because HYPRE_BigInt was not defined back in 2017.  Is there a plan to support these older versions of HYPRE or do we require a new minimum HYPRE version (the current minimum is 2.10.0b)?  Asking for a friend...

This branch doesn't seem to compile with HYPRE version 2.12.0 because HYPRE_BigInt was not defined back in 2017. Is there a plan to support these older versions of HYPRE or do we require a new minimum HYPRE version (the current minimum is 2.10.0b)? Asking for a friend...

I think this will be easy to add: for older versions of hypre (checked using MFEM_HYPRE_VERSION), we can typedef HYPRE_BigInt to be the same as HYPRE_Int and define HYPRE_MPI_BIG_INT as HYPRE_MPI_INT.

The issue with HypreParMatrixFromBlocks may be resolved by merging master into this branch -- there was an update to that function recently in #1521.

I pulled from master and checked that the unit tests pass, so @v-dobrev is right.

Great, lets wait for the merge and then I try some large problems and report back what breaks.

It turns out --enable-mixedint disables some features in hypre:
  --enable-mixedint       Use long long int for HYPRE_BigInt and int for
                          HYPRE_Int (default is int for both). Note: This
                          option disables Euclid, ParaSails, pilut and CGC
                          coarsening.

Because of this and how the makefiles work, building on Mac with --enable-mixedint (using configure and make) fails with an error like this:
ar -rcu libHYPRE.a
ar: no archive members specified
usage:  ar -d [-TLsv] archive file ...
	ar -m [-TLsv] archive file ...
	ar -m [-abiTLsv] position archive file ...
	ar -p [-TLsv] archive [file ...]
	ar -q [-cTLsv] archive file ...
	ar -r [-cuTLsv] archive file ...
	ar -r [-abciuTLsv] position archive file ...
	ar -t [-TLsv] archive [file ...]
	ar -x [-ouTLsv] archive [file ...]

One workaround for this is to combine the following lines: https://github.com/hypre-space/hypre/blob/b075d642550c9947b758201f41f5d38dabfe7a51/src/lib/Makefile#L82-L84 with the previous line, so that the list of files is not empty.

For proper mixedint support, we need to use the latest HYPRE master (any commit after https://github.com/hypre-space/hypre/commit/13e2cad4835ad3d07d661b9019687bdb20d272c1). We should document this in INSTALL.

Running clang-tidy and using it in general is an excellent idea.
My personal feeling is that testing ex1p, ex2p, ex3p and ex4p should be sufficient. We can add maybe ex8p, ex11p and ex13p to that, but I don't think we need to run every single parallel example.

clang-tidy -checks=-*,bugprone-too-small-loop-variable runs clean.

Lets resolve conflicts and 🚢 it!

Codecov Report

Merging #1583 (a9ea9cb) into master (80c5c07) will decrease coverage by 0.00%.
The diff coverage is 72.69%.

@@            Coverage Diff             @@
##           master    #1583      +/-   ##
==========================================
- Coverage   61.57%   61.56%   -0.01%
==========================================
  Files         397      397
  Lines      116670   116680      +10
==========================================
- Hits        71837    71835       -2
- Misses      44833    44845      +12

Impacted Files
Coverage Δ

fem/complex_fem.hpp
40.00% <ø> (ø)

fem/hybridization.cpp
0.00% <0.00%> (ø)

linalg/complex_operator.cpp
16.27% <0.00%> (-0.10%)
:arrow_down:

linalg/complex_operator.hpp
87.50% <ø> (ø)

linalg/handle.hpp
100.00% <ø> (ø)

mesh/pmesh.hpp
80.95% <ø> (ø)

miniapps/electromagnetics/maxwell_solver.hpp
100.00% <ø> (ø)

miniapps/electromagnetics/tesla_solver.hpp
0.00% <ø> (ø)

fem/complex_fem.cpp
44.44% <50.00%> (ø)

mesh/pmesh.cpp
56.61% <50.00%> (ø)

... and 33 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #1583 (7b46602) into master (80c5c07) will increase coverage by 0.64%.
The diff coverage is 71.31%.

@@            Coverage Diff             @@
##           master    #1583      +/-   ##
==========================================
+ Coverage   61.57%   62.22%   +0.64%
==========================================
  Files         397      399       +2
  Lines      116670   115887     -783
==========================================
+ Hits        71837    72107     +270
+ Misses      44833    43780    -1053

Impacted Files
Coverage Δ

fem/complex_fem.hpp
40.00% <ø> (ø)

fem/hybridization.cpp
0.00% <0.00%> (ø)

general/hash.cpp
0.00% <0.00%> (ø)

general/hash.hpp
91.07% <ø> (ø)

linalg/complex_operator.cpp
16.56% <0.00%> (+0.19%)
:arrow_up:

linalg/complex_operator.hpp
87.50% <ø> (ø)

linalg/handle.hpp
96.77% <ø> (-3.23%)
:arrow_down:

linalg/vector.hpp
90.67% <ø> (-3.54%)
:arrow_down:

mesh/pmesh.hpp
88.23% <ø> (+7.28%)
:arrow_up:

miniapps/electromagnetics/maxwell_solver.hpp
100.00% <ø> (ø)

... and 178 more

Continue to review full report at Codecov.

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

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

TODO:

[ ] merge master and resolve conflicts
[ ] document limitations
[ ] update CHANGELOG

Should these be also changed?
miniapps/adjoint/adjoint_advection_diffusion.cpp:   HYPRE_Int global_vSize = fes->GlobalTrueVSize();
fem/ceed/algebraic.cpp:         HYPRE_Int global_tdof_number;
tests/unit/mesh/test_pmesh.cpp:               HYPRE_Int globalMin, globalMax;

LGTM

LGTM

@dylan-copeland and @psocratis, can you please take a quick look?

@dylan-copeland and @psocratis, can you please take a quick look?

I will need some to test it first, by tomorrow maybe?

Merged in next for testing...

There are number of errors from tonight's autotest (due to older version of hypre?):
linalg/hypre.cpp: In member function ‘void mfem::HypreParMatrix::PrintHash(std::ostream&) const’:
linalg/hypre.cpp:1642:16: error: ‘struct hypre_CSRMatrix’ has no member named ‘big_j’
       if (csr->big_j == nullptr)
                ^
linalg/hypre.cpp:1648:29: error: ‘struct hypre_CSRMatrix’ has no member named ‘big_j’
          hf.AppendInts(csr->big_j, csr_nnz);
                             ^

See tux426/next/baseline and toss3/next for more details.

There are number of errors from tonight's autotest (due to older version of hypre?):
linalg/hypre.cpp: In member function ‘void mfem::HypreParMatrix::PrintHash(std::ostream&) const’:
linalg/hypre.cpp:1642:16: error: ‘struct hypre_CSRMatrix’ has no member named ‘big_j’
       if (csr->big_j == nullptr)
                ^
linalg/hypre.cpp:1648:29: error: ‘struct hypre_CSRMatrix’ has no member named ‘big_j’
          hf.AppendInts(csr->big_j, csr_nnz);
                             ^

See tux426/next/baseline and toss3/next for more details.

Ah, yes, forgot about older versions. I'll fix it.

Re-merged in next for testing ...

@tzanio I started doing some large tests, to verify this branch for examples other than ex1p, but it is going to take a while to get that done due to the large number of nodes required to exceed the max int without also running out of memory. Let's proceed with the CHANGELOG just claiming to support ex1p.

Thanks @dylan-copeland. I will merge as is.


Add fallback strategy to balancer

Some users may have a faster but unstable server as the main outbound and a slower but stable server as a backup, therefore it will be great to have a fallback strategy of the balancer to automatically choose the backup when the main server is down.
In this PR, users may configure balancers like this, where maxAttempts is the max number of failed attempts. If the Process() method of an outbound throws an error with higher severity than Info, it will be regarded as a failed attempt. If the number of failed attempts of an outbound exceeds the limit, the balancer will choose the next tag in the list. If all tags are marked dead, it will reset the state and choose the first tag again.
{
  "routing": {
    "domainStrategy": "IPOnDemand",
    "balancers": [
      {
        "tag": "proxy",
        "strategy": "fallback",
        "selector": [
          "server1",
          "server2",
          ...
        ],
        "fallbackSettings": {
          "maxAttempts": 3
        }
      }
    ]
    ...

Please feel free to comment. For the next step, do you think it's necessary to add a health check strategy, which is checking the connectivity of a server periodically by doing tcping or fetching a test website?

no update?

Could you port this to a newer version of v2ray, like v2fly/v2ray-core? Thanks!


Can't reboot Teensy 3.2 Ty 0.9.8 on Ubuntu 22.04

After a long hiatus I am back to using Tycommander 0.9.8 on Ubuntu 22.04. The reset button always draws the error "failed to reboot board 'XXXXXXXX-Teensy', but sometimes it does actually reboot. I'm loading manufacturing test code which has a 3 second timeout waiting for the Serial port to open, then prints some information about the code - so that's what I expect to see after clicking on the reset button.
Trying to understand this more, the serial port connection indicators are not reliable. When showing the port open it sometimes isn't.  Also if I click reset repeatedly it goes through a repeatable cycle of connecting to the 'bootloader', then 'running' (with serial port indication not always correct). Eventually it will display the expected serial output. If I cause a hardware reset (i can do this on our custom board) that works as expected. It's just the reset over USB that is flaky.

I have a similar problem. Did you find any solution in the end?


Didn't countdown, When didn't stay on page.

Countdown would stop working, When  didn't stay on page and set interval was not 1000.
<countdown v-if="counting" :time="count" :interval="100"  tag="p" @countdownend="bidEnd" ref="countdownBid">
    <template scope="props">

{{ props.seconds }}

    </template>
</countdown>

@fengyuanchen I think this problem didn't fix with last commit.
Because countdown will stop when you leave or hide the page. But if you go back to the page it will continue working. And with last commit you fix it to check end time init() when go back to the page that not all of problem in this case.
It have one thing, If you set interval != 1000. When you leave the page countdown timer will stop working at all and if you waiting for countdownend event you will not get it because it timer was stop. You will get countdownend event when you go back to the page and now() > endtime.
But if you set interval == 1000 you will not get this problem. May be this problem about seconds in float case?


diamondhands pos mempool review 2023 09 23

Closing PR since comments have been addressed in https://github.com/deso-protocol/core/pull/578


Add new watermill handlers that get or refresh entities by properties and call another handler

Summary
These will be used in webhook handlers instead of calling the property
service directly. The handlers follow the same base logic, just with
"pluggable" ways of retrieving the entity, converting the entity to
properties and which handler to call next.
The test coverage is not great yet, but I did test the handlers manually
outside the tests I have in another branch and they seemed to work well.
I will be adding more tests as this PR is reviewed.
Related: #4327
Change Type

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
some unit tests are added in this PR, but I'll add more. Most of the testing has been manual as part of another branch.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 52.446% (-0.2%) from 52.673%
when pulling 965442a6309cb2685c1c0391310a85d65da7fad6 on jhrozek:webhook_generic_handler
into b8fefb400819c3372f41ca46f0dfc3a77bdd5701 on stacklok:main.

I split the code into multiple sub-packages with smaller files so it's easier to digest

There are no functional changes in the latest push, just beefing up the test coverage. Almost there!


Pre-RFC: Investigate switching to intrusive waker lists by default

This needs a more formal write up, but the root issue is that:

The current waker infrastructure of embassy-sync uses an "AtomicWaker" style waker
AtomicWakers only support storing the waker of a single task at a time
This means that if two tasks are interested in the same thing, the tasks will constantly "churn", fighting for the waker spot

As one potential fix to this is using the primitives from maitake-sync:

It's possible to use maitake-sync in a no-std configuration
maitake-sync is extensively tested, with both miri (for UB checking) and loom (for atomic ordering checking).
maitake-sync has a WaitCell type, suitable for a single waker, for owned items that won't (or shouldn't) have two tasks waiting on it
maitake-sync has a WaitQueue type, which is an intrusive linked list configuration. It requires a blocking mutex for adding/removing nodes from the queue

There is however one major blocker: maitake-sync currently uses a spinlock mutex for its blocking mutex, and is not generic over different blocking mutex, like the RawMutex trait of embassy-sync. The author of maitake-sync, @hawkw (I am also a maintainer, but Eliza has done the vast majority of heavy lifting), has mentioned that she is open to parameterizing the maitake-sync collections similarly to how embassy-sync does it.
So my concrete proposal would be:

Split out the RawMutex traits into a separate crate (embassy-sync-mutex, or something?), to allow for both embassy-sync and maitake-sync to rely on this
Implement support for RawMutex parameterization of maitake-sync primitives
Replace embassy-sync's current AtomicWaker-like primitives with EITHER WaitCell or WaitQueue from maitake-sync, as appropriate

This will require a fair bit of work, but should IDEALLY not have any publicly breaking interface changes for users of embassy-sync, though it may have some (mostly benefitial, ideally) functional changes.
I expect this change would:

Make "single waiter" cases slightly slower, at least in cases where a WaitQueue was used because it is potentially possible to await from two tasks
Make "multiple waiter" cases in a single executor significantly more efficient, as there is no burned CPU churning on waking
Make "multiple waiter" cases in an interupt executor configuration significantly more efficient and predictable, as a churning high prio waker will not starve lower prio executor tasks

Overall, I think this is worth investigating/discussing, as it has come up a number of times in chat (not a ton! But enough now that it is a semi-known failure mode).
Some open questions include:

Should embassy-sync use maitake-sync, or fork/copy the primitives used there, to allow "in-project" maintenance
How do we avoid burdening a "somewhat unrelated" project with embassy's concerns? by forking? by adding embassy folks to the maitake-sync owners?
Do we expose/re-export maitake's other concurrency primitives? They are likely useful, but having another (particularly non-1.0) crate in embassy-sync's public API always is a little dicey, due to versioning maintenance

CC: @hawkw @ivmarkov @Dirbaio

Split out the RawMutex traits into a separate crate (embassy-sync-mutex, or something?), to allow for both embassy-sync and maitake-sync to rely on this

Splitting out RawMutex into its own micro-crate (ala embassy-time-driver and embassy-net-driver) might have use-cases beyond your idea of re-using it in maintake-sync so that embassy-sync can depend on maintake-sync rather than fork it.
For example, that would give "easier time" to RawMutex implementor code that lives outside the embassy-sync crate. esp-idf-hal is currently such one, by providing two separate mutex implementations - one - based on "disable all interrupts (+ spinlocks for multi-core)" and another - based on regular FreeRTOS mutexes.
The thing is, the "one size fits all" approach of critical-section just does not work for traditional RTOSes, where you might need different types of blocking mutexes, depending on the context where you would like to use those. Abstracting by using RawMutex instead (and sure - by introducing generics that way) is one way to solve that in driver crates.
Currently, esp-idf-hal depends directly on embassy-sync, which is a bit painful. For example, our next release would be a breaking one, because embassy-sync currently went from 0.5 to 0.6. That's definitely not the only reason but could've been the only reason to issue a breaking release, which is not ideal.

Splitting out RawMutex into its own micro-crate (ala embassy-time-driver and embassy-net-driver) - that is - if you decide against forking a subset of maintake-sync into embassy-sync - might have use-cases beyond your idea of re-using it in maintake-sync so that embassy-sync can depend on maintake-sync rather than fork it.

Just confirming that I agree 100%! I didn't spell this out, but I definitely think this is a positive.

Regarding abstracting over raw mutex types, I would encourage investigating whether the lock_api crate can be used for that purpose --- it's pretty widespread in the non-embedded world, as parking-lot uses lock-api, but it also claims to have no-std support. I would look into whether its traits are suitable for our purpose. If they are, it's probably better to use the commonly-used trait rather than inventing a new version of it.

This would be great as this would also fix #1204 when using multiple executor with different interrupt priorities which would make embassy better equipped when users needs to do real time operations.

I'm just leaving a comment here to express interest in using WaitQueue as well. Presumably it would simplify the type signatures of the PubSubChannel and Watch channels since the number of senders/receivers would no longer need to be defined at compile time, and obtaining a receiver would always succeed.


Adding Walltime specification

Hi @AndresOrtegaGuerrero , thank you!
However, this is still not working with the qe-app version we deliver in the docker (tag: v24.10.0a0). This broke my live demo of the tutorial today (no worries).
To solve this, I think is time to start doing releases and add tests which work with the qe-app released version (not the main branch).
I will work on this in the next few days as it is a bit crucial. I will open an issue

let's then remove this pr , because i will break it for other users , i didnt realize this


disable Xdebug when not needed

Hey!
Thanks for the patch! Maybe you noticed that I've just removed this line a couple of days ago after a discussion in issue #9.
When looking at the PHP 5.6 build for my recent commit (https://travis-ci.org/woohoolabs/harmony/jobs/129048700) and yours (https://travis-ci.org/woohoolabs/harmony/jobs/129045688) I can't really see a big difference in performance:
Without XDebug:

composer install is faster by 4 s and takes 18 s to finish
phpunit is faster by 0.06 s and takes 0.14 s to run

However these numbers aren't really representative because Travis isn't reliable.
Meanwhile I noticed that Travis runs compose self-update automatically (I believe they didn't do it in the past!), so I removed it from the before_install section, creating a conflict with your PR. :S
Although it seems that there is not a big need for disabling XDebug, if you resolve the conflict, I'll merge your PR. :) Sorry for the inconvenience.

@sagikazarmark I gained some insights about Xdebug and realized that composer self-install is not needed anymore in the Travis config!

The reason why I usually have it is that composer gets new features from time to time, however it takes a considerable amount of time for Travis to update composer. This way you always have a fresh one. Is there anything new on this front I don't know about?

Yes, I also thought that Travis doesn't update Composer often, but check my first comment where you can see on the linked build status report (https://travis-ci.org/woohoolabs/harmony/jobs/129120809#L135) that composer self-update runs twice: on line 135 and line 162.
The first one is when Travis provisions the container, and the second one is when I run it in the before_install section. After I removed this section, Composer doesn't get updated twice: https://travis-ci.org/woohoolabs/harmony/jobs/129120810

Ah, cool, good to know. Thanks for the heads up.

@kocsismate Yes, it doesn't save you much time with the current test suite (the differences between the several builds are mainly related to the load of the underlying machines that Travis uses I guess). Though it doesn't hurt and has positive effects in case the test suite is expanded in the future. :)

And at least I could discover that composer self-update can also be omitted! So thank you for your PR!


[PDI-14781] Empty log file gets created when job runs on carte server

write logs to file from carte server

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

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

Changed files
  engine/src/org/pentaho/di/job/entries/job/JobEntryJob.java
  engine/test-src/org/pentaho/di/job/entries/job/JobEntryJobIT.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.14%:small_red_triangle_down:
Complexity Change: -7.69%:small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.01%:small_red_triangle_down:
Complexity Change: -1.06%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.job.entries.ftpsget.JobEntryFTPSGet

Branch Change: -.53%:small_red_triangle_down:
Complexity Change: -.56%:small_red_triangle_down:
Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.job.entries.job.JobEntryJob

Branch Change: -.24%:small_red_triangle_down:
Complexity Change: -.20%:small_red_triangle_down:
Instruction Change: -.45%:small_red_triangle_down:
Line Change: -.37%:small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.87%

org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change:  + 8.70%
Complexity Change:  + 3.08%
Instruction Change:  + .75%
Line Change:  + .89%

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

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -.05%:small_red_triangle_down:

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

Instruction Change:  + .04%

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

Branch Change: -3.12%:small_red_triangle_down:
Complexity Change: -3.16%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:
Line Change: -.74%:small_red_triangle_down:

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

Instruction Change:  + .06%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.18%:small_red_triangle_down:
Complexity Change: -1.35%:small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change:  + .07%

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

Instruction Change:  + .10%

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

Instruction Change:  + .18%

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change:  + 3.33%
Complexity Change:  + 1.85%
Instruction Change:  + .28%

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

Instruction Change:  + .04%

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change:  + .91%
Complexity Change:  + .82%

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change:  + .18%

@mchen-len-son @mbatchelor @pamval please review.


3D view in Projections

Original author: Nikhil Jain
Original issue: https://charm.cs.illinois.edu/redmine/issues/21

Java based 3D view in projections is buggy - fix it.

Original date: 2013-08-28 18:57:48

A longer list of what buggy means would be helpful.

Original author: Nikhil Jain
Original date: 2014-01-06 04:19:50

Difficult to describe - In general, for various core counts (especially large), the view is not rendered correctly.

Original author: Nikhil Jain
Original date: 2014-01-06 04:21:07

We need a lead for Projections!

Original author: Yanhua Sun
Original date: 2015-02-19 22:54:04

This is about the 3D projections display.  We need to re-examine all the design and see how we want to proceed.  The old implementation by the undergraduate intern is pretty rush and he did it himself.


Vite and Vitest inconsistency using Preact

Describe the bug
I'm having trouble with using usehooks-ts on a Vite (Preact + TypeScript) project. Running vite works without a problem but vitest fails to run.
Here is the error
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.

I suspect this might be because usehooks-ts has react-dom peer dependency. However, I'm not sure if this is the culprit.
Reproduction
Stackblitz didn't ran vitest so here is the reproduction repo.
Just run npm test to see this problem
System Info
System:
    OS: macOS 13.3.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 13.81 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 19.7.0 - /opt/brew/bin/node
    npm: 9.5.0 - /opt/brew/bin/npm
  Browsers:
    Chrome: 114.0.5735.90
    Firefox: 111.0.1
    Safari: 16.4

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Vitest doesn't alias imports inside packages, you need to add preact packages to deps.inline or enable deps.experimentalOptimizer.

Okay, I've applied the following change to my Vite config but now it complains for another error:
TypeError: Cannot read properties of undefined (reading '__H')

--- a/vite.config.ts
+++ b/vite.config.ts
@@ -6,6 +6,12 @@ import { defineConfig, splitVendorChunkPlugin } from "vite";
 export default defineConfig({
     plugins: [preact(), splitVendorChunkPlugin()],
     test: {
+        deps: {
+            experimentalOptimizer: {
+                include: ["usehooks-ts"],
+                enabled: true,
+            }
+        },
         setupFiles: ["./tests/setup.ts"],
         coverage: {
             all: true,

Is this related to Preact or Vitest?

Is this related to Preact or Vitest?

I can only assume preact has separate instances because it failed to duplicate. Try adding preact packages to optimizer? I cannot look into it yet, but that would be my guess.

I see you already opened an issue for this but I have tried your suggestion as well and it didn't made any difference as well. It's possible that I might have done it wrong though.
--- a/vite.config.ts
+++ b/vite.config.ts
@@ -8,7 +8,13 @@ export default defineConfig({
     test: {
         deps: {
             experimentalOptimizer: {
-                include: ["usehooks-ts"],
+                include: [
+                    "usehooks-ts",
+                    "preact/jsx-runtime",
+                    "preact/jsx-dev-runtime",
+                    "preact/test-utils",
+                    "preact/compat"
+                ],
                 enabled: true,
             }
         },


tell on open file seems to interfere with buffering simulation

import pyfakefs.fake_filesystem
import os
fs = pyfakefs.fake_filesystem.FakeFilesystem()
fs.CreateDirectory('/Volumes')
fs.CreateDirectory('/Volumes/ramdisk')
fs.CreateDirectory('/Volumes/ramdisk/test')
os0 = pyfakefs.fake_filesystem.FakeOsModule(fs)
opener0 = pyfakefs.fake_filesystem.FakeFileOpen(fs)
component0 = "alpha"
path0 = "/Volumes/ramdisk/test"
path0 += "/" + component0
str0 = ""
str0 += 'a'
str0 += 'a'
str0 += 'a'
file0 = opener0(path0,'w')
file0.write(str0)
str0 += 'a'
str0 += 'a'
str0 += 'a'
str0 += 'a'
str0 += 'a'
str0 += 'a'
str0 += 'a'
str0 += 'a'
str0 += 'a'
file0.write(str0)
result = file0.tell()
result = os0.path.getsize(path0)
print result
0 vs. 15
the tool produced a bunch of variants of this overnight, but they all seem to have the same pattern of a tell followed by a getsize.  Not quite sure why normalization isn't making them all the same (or shorter, the 'a's don't seem all needed, but I just copied them over from an arbitrary bug).

Will have a look tomorrow.

Hm, I get size 0 both on Windows and in pyfakefs, but 15 under Linux. Sems that tell() does a flush under Unix, but not under Windows.


Prototype Using Commit Characters for JS and TS Completions

Part of #7326
Adds a prototype for using specific characters to complete TS/JS completion items automatically.
Work to do:

[ ] Add setting to disable this (and only apply in TS files perhaps to match existing behavior)
[ ] Get this to play nicely with typescript.useCodeSnippetsOnMethodSuggest (not a regression actually)
[x] Improve completions for paths and module names

Add setting to disable this (and only apply in TS files perhaps to match existing behavior)

Unsure about that. I am in favour of an editor-wide setting that allows to control this.


[operator] bump operator version to v0.103.0

The test failure looks transient, they pass locally for me.

@swiatekm-sumo need to solve conflicts~


Compiled crcmod required for restores using multi-part uploads from google_storage

What happened?
When the medusa-restore init container attempts a restore from a GCS backup created using multipart uploads, timeouts and ultimately failure occur. This is likely due to the medusa docker image (k8ssandra/medusa:0.13.4) not having compiled crcmod installed, which was confirmed via error logs in the outputted gsutil manifest file in the medusa-restore init container as well as checking gsutil version -l which yielded compiled crcmod: false.
Did you expect to see something different?
Expected a functioning restore similar to the example case in the documentation, which succeeded for me.
How to reproduce it (as minimally and precisely as possible):
Restore from a backup that contains files backed up using multipart uploads.
Environment

K8ssandra Operator version: v1.5.2
v1.5.2

Kubernetes version information:
v1.26.0

Kubernetes cluster kind:
kind, via the setup-kind-multicluster.sh script.

Hi @yuraymondl,
good to know. If you feel like pushing a PR to the thelastpickle/cassandra-medusa repo, it would be fantastic 🙏


FAQ update

FAQ update

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

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6650b857b84e232ab1649529--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6658bdf83975c95087ea3a74--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66b617fb46bbbc74647c8535--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66ba0f7bf0653b990df2c355--harness-developer.netlify.app


State Changes

States can be create without constructor and super prop

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

State can be created without constructor

@sadeeqaji I'm going to close this for now so we can move some files around. Could you open a new pull request related to this that incorporates @RandellDawson's advice?


[Eval,Arch] Update GPTQ eval and add headless_mode for Controller

What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?

Give a summary of what the PR does, explaining any non-trivial design decisions

Add thought argument to AgentFinishAction for CodeAct.

Update GPQA inference code to be more aligned with the actual experiment we run in the paper by applying changes from this reproducible patch https://huggingface.co/spaces/OpenDevin/evaluation/blob/main/outputs/gpqa/reproducibility.patch

Add a headless_mode for controller (mainly for evaluation, default to False).

When headless_mode is True, we will stop the whole run when the delegated agent (e.g., BrowsingAgent in the CodeAct -> Browsing delegation) hits the max iteration limit. Currently, the behavior is the delegated agent will wait for the user to hit the continue button, which puts an evaluation into an infinite loop since it is running headless.
I can apply changes to all evaluation's run_infer.py if people like this idea!

Other references

@xingyaoww this made my day: 🤣 :
"Again you are being told a million times to first report the answer in the requested format"

@tobitege This was original written by @1jsingh in that reproducibility patch 😆


Clean up Failure handling

In order to be more future-proof and clean up the IFailuedFuture interface we will:

get rid of everything except .value from the interface
provide txaio.failure_message(failure) which returns a unicode
provide txaio.failure_traceback(failure) which returns a traceback object

For the record, we've had an extensive discussion about this on slack, above is the result, and I think it's very reasonable. +1

I also made txaio.failure_format_traceback(failure) which returns a string (the formatted traceback) for convenience.


[Duplicate of #5365] Introduction to Kernel Methods in Machine Learning

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[ x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[ ] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[ ] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #4567

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

hello @paulodhiambo changes requested are in place

@paulodhiambo
If any other edits are needed - we will be closing the PR.

Plagiarism check complete

hello @Jethro-magaji  changes requested are in place

Hi! @Brian3811
Please change the current hero image to a high resolution free stock image of 600x400 PX.
Change the PR branch name to something readable, like this "introduction-to-kernel-methods-in-machine-learning"


Rename the container instance

Is it possible to change the name of the NAV instance when creating the container?
For example:
I have a machine in Azure with a single name, if I change the name of
the instance I could install several containers
xxxxx.cloudapp.azure.com/NAV
xxxxx.cloudapp.azure.com/NAV2
Thanks

You cannot rename the instance and even if you could, you wouldn't be able to do what you are asking.
But... - this is what the traefik feature was made for:
https://www.axians-infoma.de/techblog/traefik-support-for-navcontainerhelper-the-nav-arm-templates-for-azure-vms-and-local-environments/
You should try that.

Thanks @freddydk
I will try it!!!

Lyder godt.
Jeg sidder i Grækenland uden mit NEMID, men er tilbage Torsdag morgen (hvis ikke Christian har godkendt den inden).
/Freddy
From: Neoduende<EMAIL_ADDRESS>Sent: 21. juli 2019 20:00
To: microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: Freddy Kristiansen<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/navcontainerhelper] Rename the container instance (#522)
Thanks @freddydkhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffreddydk&data=02|01|freddy.kristiansen%40microsoft.com|8fbdb06b5e7943fa3e5c08d70e05337f|72f988bf86f141af91ab2d7cd011db47|1|0|636993287806004107&sdata=D%2FSnKBHKHt2Kf2BG5yy8qbGDrKgNcDCbBDzRmKyBW%2Bw%3D&reserved=0
I will try it!!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fnavcontainerhelper%2Fissues%2F522%3Femail_source%3Dnotifications%26email_token%3DACSGUA2LJDZZBYEYNMBG6PTQASPYXA5CNFSM4IFOK6U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OIPXA%23issuecomment-513574876&data=02|01|freddy.kristiansen%40microsoft.com|8fbdb06b5e7943fa3e5c08d70e05337f|72f988bf86f141af91ab2d7cd011db47|1|0|636993287806004107&sdata=ZHr4ppGFmQ0Owbaaf1EGvecuRBnlQ9I0%2F73oPbvKxLU%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACSGUA7ZDUU4UB3RXEJG5BLQASPYXANCNFSM4IFOK6UQ&data=02|01|freddy.kristiansen%40microsoft.com|8fbdb06b5e7943fa3e5c08d70e05337f|72f988bf86f141af91ab2d7cd011db47|1|0|636993287806004107&sdata=fetGxYQiiwnse5Wm%2FlzQC0OchFH8rLpKX9oceisqIBg%3D&reserved=0.


server(ticdc): implement diagnosticsService in cdc

What problem does this PR solve?

Issue Number: close #10263
What is changed and how it works?
implement diagnosticsService in cdc to support searching logs via tidb dashboard.
Check List
Tests

Manual test (add detailed scripts or steps below)
Query logs via unit test:

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

/test all


calculate hash of PK question

Hopefully this should be a easy question to answer.
I have a X509 certificate that i want parse, and then calculate a hash of the Public Key (PK) in the certificate to compare it to a known hash value.  Since the PK is held in the mbedtls_pk_context struct, is it sufficient for me to some something like below (pseudo code) to calculate the hash of the PK?
mbedtls_x509_crt_init(&xCert);
mbedtls_x509_crt_parse(&xCert, xCert_ptr, xCert_size);
hash_type = MBEDTLS_MD_SHA384;
md_info = mbedtls_md_info_from_type(hash_type);
mbedtls_md(md_info, xCert.pk.pk_ctx, mbedtls_pk_get_len(&xCert.pk), md_hash);

I am closing this issue because it is an answered support request, not a bug report or an enhancement request.


Diff comparison unexpectedly fails with output

2 -1 5
1 5 2 2
2 6 -1 5

From https://vjudge.net/contest/655412#problem/F
Debug solution: https://vjudge.net/solution/54200991

Fixed by https://github.com/sam20908/vscode-fastolympiccoding/commit/18fe79a6a6b6ab4539b999bfb5d8e474c236f842


Add pre-commit hook to disallow improper comparison to _nxver

_nxver was updated to either be a 2-tuple or 3-tuple in https://github.com/rapidsai/nx-cugraph/pull/15, and we needed to update some comparisons to properly handle nx 3.4.1 and nx 3.4.2. The new pre-commit enforces sane comparisons when using _nxver.

/merge


fix: let core handle 'workspace/didChangeConfiguration' after init

Since https://github.com/neovim/neovim/pull/18847 there's no need to send the workspace/didChangeConfiguration manually after initialization, since neovim will automagically do it.
This PR removes documentation references recommending this behaviour, together with the implementation handling the redundant action (I might have missed places so please review carefully).

Do not change server_configurations.md directly. Edit the lua source file instead. See https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#generating-docs

Okay bot idk what to tell you, I didn't modify that file.

Do not change server_configurations.md directly. Edit the lua source file instead. See https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#generating-docs

Okay bot idk what to tell you, I didn't modify that file.

https://github.com/neovim/nvim-lspconfig/commit/7122c443579b069d06df61acc0fd784997a3f9d9 changes doc/server_configurations.txt only. The force push that clobbered it, 8421089a969aafca9f1832388d8697ec6072daea, changes doc/server_configurations.md only. Change both files in the same commit and I bet you'll see green.

Do not change server_configurations.md directly. Edit the lua source file instead. See https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#generating-docs

7122c44 changes doc/server_configurations.txt only. The force push that clobbered it, 8421089, changes doc/server_configurations.md only. Change both files in the same commit and I bet you'll see green.

I don't think that's correct; you should never edit these files and instead let automation handle it.

The comment from the bot is misleading, apparently you're not supposed to change doc/server_configurations.md or doc/server_configurations.txt. I'll make a PR to clarify this point.


Added support for beaglebone boards

Signed-off-by: Marek Belisko<EMAIL_ADDRESS>

Thanks for review. I'll push fixup shortly (it's ok with commit on top or should I squash?). thx

Squash and force push is prefererad.

Seems like a "merge commit" sneaked in :)

I will clean that up so do no worry about it

Yes something like that but resolved already ;)

Yeah what mean is that you did a "git merge sumo" right? And you now got an "extra commit" saying that you did that which will follow your other commit if I was to merge this.
The more "clean" way would be to run "git rebase sumo", if there where changes on sumo that you want to include in your branch to avoid having "merge commits" in your PR.

Oh yes right. I'll do it.

Not it should be 100% :100:  :)


hotfix: Moving average docs 수정 및 관리자 code owner 추가

Summary
Write the summary about this PR.

moving average example의 불필요한 개행 삭제

before

after

code owner에 관리자 두명 추가

Changes
Write changes in detail.

How to Test?
Write a way to test the changes.

Checklist

[ ] Do you pass all the tests?
[ ] Do you write the changes on document such as README?

Codecov Report

Merging #104 (ae5df66) into main (70a5a33) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #104   +/-   ##
=======================================
  Coverage   81.07%   81.07%
=======================================
  Files          24       24
  Lines         560      560
=======================================
  Hits          454      454
  Misses        106      106

Flag
Coverage Δ

unittests
81.07% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

onebone/signal/smoothing.py
75.00% <ø> (ø)

Continue to review full report at Codecov.

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


Add the output fields of wallet subcommand list

Issue summary

Add output fields "Default" and "Balance" to cli wallet list
❯ ./forest wallet list
Address                                    Default  Balance
t1ss6z757xy46h2qhxgnk4rummmjwmpbtwcnkdcki  X        0

Other information and links

Done.


flash: remove obsolete FLASH_DRIVER_NAME

Replace seldom occurrences of FLASH_DRIVER_NAME by equivalent
and commonly used FLASH_DEV_NAME.
Fixes #5919.
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

Codecov Report

Merging #6000 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6000   +/-   ##
=======================================
  Coverage   52.51%   52.51%
=======================================
  Files         406      406
  Lines       39683    39683
  Branches     7715     7715
=======================================
  Hits        20839    20839
  Misses      15663    15663
  Partials     3181     3181

Continue to review full report at Codecov.

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

I'm good with this, but would like @mbolivar or @d3zd3z to verify @carlescufi comment about not breaking mcuboot


Add Normalize.css as optional item

add normalize.css as a feature enabled in theme-variables.css

Added in my latest pull request


added code for mjcf postprocessing to make it work better in brax

based on pawel's code, refactored slightly, add's things like floor, contact, etc. Collision should still be added manually but its very quick

@budzianowski some condim and conaffinity stuff seemed to be a bit wonky for the visual meshes, i updated it now in the code, not sure if this code is being used any where else but worth taking a look at
Working:
visual_geom = ET.Element("default", {"class": "visualgeom"})
        geom_attributes = {"material": "visualgeom", "condim": "3", "contype": "0", "conaffinity": "0"}
        ET.SubElement(visual_geom, "geom", geom_attributes)

Before:
visual_geom = ET.Element("default", {"class": "visualgeom"})
       geom_attributes = {"material": "visualgeom", "condim": "1", "contype": "1", "conaffinity": "0"}
       ET.SubElement(visual_geom, "geom", geom_attributes)

made all the changes requested - i'll open a separate issue for automatically populating collisions


fix: link error in NextStep component

Summary
Fix #365
Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

❤


Segmentation fault when reading string variable over DAP4

Hello Unidata/NetCDF folks! A few of us at NASA GES DISC are running into a failure in netcdf-c when accessing string variable over DAP4 from NASA's cloud-hosted OPeNDAP server. This seems to be an issue only when reading via DAP4, using netcdf to read the data on disk directly is not an issue.
Authentication
If not already set up, an account is needed at https://uat.urs.earthdata.nasa.gov/ and the following line added to ~/.netrc in the user's home folder:
machine uat.urs.earthdata.nasa.gov login <username> password <password>

Issue
We came across this issue when accessing the following DAP4 URL via netcdf-python dap4://opendap.uat.earthdata.nasa.gov/collections/C1256351857-GES_DISC/granules/SNDRSNML2RMS.3%3ASNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc
import netCDF4 as nc4
f = nc4.Dataset("dap4://opendap.uat.earthdata.nasa.gov/collections/C1256351857-GES_DISC/granules/SNDRSNML2RMS.3%3ASNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc")

One of the variables causing issues is obs_id, which is an array of strings.
In [3]: f['obs_id']
Out[3]:
<class 'netCDF4._netCDF4.Variable'>
vlen obs_id(atrack, xtrack)
    long_name: earth view observation id
    coverage_content_type: referenceInformation
    description: unique earth view observation identifier: yyyymmddThhmm.aa[a]Exx .  Includes gran_id plus two- or three-digit along-track index (01-45 or 001-135) and 2-digit cross-track index (01-96).
vlen data type: <class 'str'>
unlimited dimensions:
current shape = (135, 96)

Trying to access the data from obs_id results in a segmentation fault:
In [4]: f['obs_id'][:]
Assertion failed: ((p)->offset+(size) <= (p)->limit), function NCD4_incr, file d4util.c, line 421.
[1]    17238 abort      ipython

Resources:
OPeNDAP landing page for this file: https://opendap.uat.earthdata.nasa.gov/collections/C1256351857-GES_DISC/granules/SNDRSNML2RMS.3%3ASNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc.html
Raw file (in case of authentication issues or for local testing): SNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc.zip
I hope this is enough information but please let me know if anything else is needed.
Tagging @j-m-adams @eni-awowale

I'm not really sure if this is some issue of DAP4 encoding on the server-side, or decoding proper DAP4 on the client side (or some combination of both). Any input would be greatly appreciated. Thanks!

Forgot to include my versions:

netcdf library version 4.9.2 of Jul  5 2023 23:51:08 $
Python: 3.11.9
netcdf-python: 1.6.5

I am also getting the same error with these versions:

netcdf-c: '4.9.3-development of Oct 24 2023 19:20:46 $'
netcdf4-python==1.6.5
Python: 3.12.5

And

netcdf-c: '4.8.1 of Oct 10 2024 19:24:58 $'
netcdf4-python==1.6.5
Python: 3.12.7

Unfortunately, my attempt register fails repeatedly on a recapture invalid key failure.
So I will not be able to help. Sorry.

Hi, Dennis -- I'm not sure what a recapture invalid key failure means, but it might be because the URL we provided was in our testing environment (".uat." in the URL), which may not be publicly accessible. Could you please try again with the production version of the URL copied below? Note that the opendap.earthdata.nasa.gov endpoint always requires authentication with an Earthdata Login. We are struggling to support some newer data types that are not DAP2 compatible and we'd really like to promote the dap4:// protocol to our opendap users. Thank you for your help. --Jennifer Adams
dap4://opendap.earthdata.nasa.gov/collections/C2559919298-GES_DISC/granules/SNDRSNML2RMS.3%3ASNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc

I finally got the urs login problem solved.
I tried to replicate you problem but failed.
I tried several different commands using ncdump from the current main branch.
All of these appear to work:

.ncdump -v obs_id 'dap4://opendap.uat.earthdata.nasa.gov/collections/C1256351857-GES_DISC/granules/SNDRSNML2RMS.3:SNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc'
ncdump 'dap4://opendap.uat.earthdata.nasa.gov/collections/C1256351857-GES_DISC/granules/SNDRSNML2RMS.3:SNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc?dap4.ce=obs_id'
ncdump 'dap4://opendap.uat.earthdata.nasa.gov/collections/C1256351857-GES_DISC/granules/SNDRSNML2RMS.3:SNDR.SNPP.ATMS.20111210T0154.m06.g020.L2_RAMSES2_RET.std.v03_21.G.231124163951.nc?dap4.ce=obs_id[0][0]'

Do any of these commands correspond with what you are doing?

Very glad to see that ncdump is working! We are using python packages (xarray/datatree and netCDF4) to open those dap4:// urls, but are struggling to find anything that is linked with the 4.9.3 release candidate. Is there a dev version of any of these python packages that we can test the 4.9.4 release candidate?

I am not alll that familiar with the python/netcdf community. My guess is that there is a way to install 4.9.3
and have python/netcdf4 use that installation. But do not know the details.

I will second Dennis' comment; @dopplershift can you provide any guidance as to how to easily hook the latest netCDF-C release candidate into a python ecosystem?

As we've discussed previously, the first step is to get a build of the RC up on the conda-forge feedstock. When I attempted this previously, I ran into numerous build issues that we didn't get solved before the official release. Happy to be a part of getting that going over there if someone is prepared to look at any issues we encounter in doing so.
Depending on how tightly pinned the conda-forge version of netcdf4-python is to a version of libnetcdf, we may be able to just install the RC and have netcdf4-python use it, but I'm not sure about that yet.

Thanks @DennisHeimbigner and everyone for the engagement! We built the netcdf-c library in main and we are no longer getting segfaults with the 4.9.4-development version  🎉. We were able to link it to the python library by pip installing it.
With python
>>> import netCDF4 as nc4
>>> nc4.getlibversion()
'4.9.4-development of Oct  7 2024 10:41:37 $'

With ncdump
$ ncdump -h
ncdump [-c|-h] [-v ...] [[-b|-f] [c|f]] [-l len] [-n name] [-p n[,n]] [-k] [-x] [-s] [-t|-i] [-g ...] [-w] [-F] [-Ln] file
...
...
netcdf library version 4.9.4-development of Nov 13 2024 20:48:37 $

I am guessing that netcdf4-python library is pulling from our built version of the netcdf-c library but I wanted confirm that this is correct? Additionally, do you all know when the python library is going be released with the 4.9.4-development version of the netcdf-c library? Happy to contribute time to help with this.
Thanks again everyone!


Alt titles are rendered in a single line in tablets

Steps to reproduce

Open a manga with alt titles
Observe the alt titles list

Expected behavior
Alt titles should be rendered in multiple lines for better readability
Actual behavior
Alt titles are rendered in a single (sometimes VERY long) line
Crash logs
No response
Neko version
2.13
Android version
11 with OneUI 3.1
Device
Galaxy Tab S5e
Other details
This is a problem with overly long titles (things in the style of "I was reincarnated and then this happened, and then that happened, and then other things happened", for example), especially since I only care for the english alt title(s), not the other languages (this may be helped with some configurable language filter for alt titles)
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to the newest version Latest.
[X] I have filled out all of the requested information in this form.

Can you add a screenshot

I got Neko v2.13.1 which is supposed to incorporate the fix for this, but it keeps showing the alt titles the same way. Is there a configuration somewhere that I have to change?

Changed this to an option in the main appearance settings


Update collections, command, completion, ... to 1.9.9

About this PR
📦 Updates

org.scala-sbt:collections
org.scala-sbt:command
org.scala-sbt:completion
org.scala-sbt:core-macros
org.scala-sbt:main
org.scala-sbt:main-settings
org.scala-sbt:sbt
org.scala-sbt:task-system
org.scala-sbt:util-logging
org.scala-sbt:util-position

from 1.4.9 to 1.9.9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

💡 Applied Scalafix Migrations

org.scala-sbt:sbt:1.5.0 (created no change)

https://gist.githubusercontent.com/eed3si9n/57e83f5330592d968ce49f0d5030d4d5/raw/7f576f16a90e432baa49911c9a66204c354947bb/Sbt0_13BuildSyntax.scala
Documentation: https://eed3si9n.com/syntactic-scalafix-rule-for-unified-slash-syntax

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, scalafix-migrations, commit-count:1

Superseded by #249.


Add user prompt when removing a project. Resolves #90

I suspect your non-related changes is due to the PR being from master? I make the mistake of using master for PRs too, and end up submitting unintended changes as a result.


Make install - Pip subprocess error

Describe the bug
When trying to install quants-lab on macOs (m1), im getting an error after running make install
 ~/github/hummingbot/quants-lab/main-ql > make install                                                                                 ✔
conda env create -f environment.yml
Channels:
 - defaults
 - conda-forge
Platform: osx-arm64
Collecting package metadata (repodata.json): done
Solving environment: done

Downloading and Extracting Packages:

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
Installing pip dependencies: / Ran pip subprocess with arguments:
['/Users/rapcomia/miniconda3/envs/quants-lab/bin/python', '-m', 'pip', 'install', '-U', '-r', '/Users/rapcomia/github/hummingbot/quants-lab/main-ql/condaenv.o6vxfe4k.requirements.txt', '--exists-action=b']
Pip subprocess output:
Collecting hummingbot (from -r /Users/rapcomia/github/hummingbot/quants-lab/main-ql/condaenv.o6vxfe4k.requirements.txt (line 1))
  Using cached hummingbot-20241125.tar.gz (6.7 MB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'error'

Pip subprocess error:
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [25 lines of output]
      Warning: passing language='c++' to cythonize() is deprecated. Instead, put "# distutils: language=c++" in your .pyx or .pxd file(s)
      Traceback (most recent call last):
        File "/Users/rapcomia/miniconda3/envs/quants-lab/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/rapcomia/miniconda3/envs/quants-lab/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/rapcomia/miniconda3/envs/quants-lab/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 334, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
          self.run_setup()
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 522, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 320, in run_setup
          exec(code, locals())
        File "<string>", line 169, in <module>
        File "<string>", line 157, in main
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 979, in cythonize
          module_list, module_metadata = create_extension_list(
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 821, in create_extension_list
          for file in nonempty(sorted(extended_iglob(filepattern)), "'%s' doesn't match any files" % filepattern):
        File "/private/var/folders/7d/kmb517_17k5d_t08kzp9x4lm0000gn/T/pip-build-env-aq8eo4ps/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 116, in nonempty
          raise ValueError(error_msg)
      ValueError: 'hummingbot/**/*.pyx' doesn't match any files
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

failed

CondaEnvException: Pip failed

make: *** [install] Error 1

Used latest commit e19f9f4cb0c4324c17cbd8e405c6bc26de5a6d3c

Steps to reproduce bug

Clone quants-lab on a macOs (m1)
Run make install

same happening to me- I had a different issue I tried re-installing the repo and now I get this same error

same error trying to install quants-lab on windows, using windows command prompt

Same error.

Hey it was related to hummingbot installation via pip. I fixed it by changing the environment.yml (line 11) to

hummingbot=20241124


log path relative to root

1. What version of Caddy are you running (caddy -version)?
0.8.3
2. What are you trying to do?
specify logfile path relative to root.
3. What is your entire Caddyfile?
davidak.binary.lan.davidak.de {
  root /var/www/davidak/web/
  gzip

  log /var/www/davidak/log/access.log {
    rotate {
      age 96
      keep 10
    }
  }

  errors {
    log ../log/error.log {
      age 96
      keep 10
    }
  }
...
}

4.  What did you expect to see?
caddy starts and log errors to /var/www/davidak/log/error.log
6. What did you see instead (give full error messages and/or log)?
caddy[1531]: 2016/07/17 02:42:39 open ../log/error.log: no such file or directory
7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
reproduce the caddyfile with your paths.

We intentionally made log files relative to current working dir because log files don't necessarily belong in the root of the site; they aren't a part of the site, so it doesn't make sense to make their paths relative to the site root.


Sync loading with Webpack

I was looking into preloading a few locales so that async loading wouldn't be required (I'm using this in cordova so it wouldn't make much sense) and I came up with this:
  function getInjectedLocale() {
    var localInjector = angular.injector(['ngLocale']);
    return localInjector.get('$locale');
  }

  // put de-de language into cache
  require('angular-i18n/de-de');
  tmhDynamicLocaleCache.put('de-de', getInjectedLocale());

  // put en-gb language into cache
  require('angular-i18n/en-gb');
  tmhDynamicLocaleCache.put('en-gb', getInjectedLocale());

  // later on:
  tmhDynamicLocale.set('en-gb'); // or de-de

Seems to work very well, I'm leaving this here as a possible addition to the readme. A possible improvement might be to create a method in tmhDynamicLocale, like tmhDynamicLocale.cacheLastLoadedLocale('de-de') for instance, which can be called right after the require.

@andreialecu thanks!

@andreialecu This is something I need as well, but could you please elaborate further on how to achieve this or point me to a working plunker / ? I am sure I might wrap my head around it, but if you have any clues (where (files), when (phase) to use your above code), that would be helpful...

@ChristianUlbrich The above code assumes you're using webpack.
You can just put it inside a .run call like this:
app.run(function(tmhDynamicLocale, tmhDynamicLocaleCache) {
  ...
});

If you're not using webpack, then I'm not sure how this helps you or why you would need it. Care to elaborate?

@andreialecu Thanks! That's all I needed. Sorry, for using "elaborate" :) Actually I can only guess, why your approach works, but do I care? No! Works like a charm.
And yes we are using webpack and I need to pre-bundle the available locales, just like you wanted to.
If I were to wish for something, I think that the localeCache should be synchronously set by a provider.

 English is not my first language but I don't think there's anything wrong with the word "elaborate", I just wasn't sure what you were asking. :)

This chunk of code was helpful to get started but I took another path with webpack to tackle async issues. It's using ui-router.
In webpack make a bare copy of the locals so they are packaged but not (yet) imported.
var copyStatic = new CopyWebpackPlugin([
  {from: './node_modules/angular-i18n/angular-locale_de-de.js', to: path.resolve(APP_ROOT, appConfig.buildDir + '/i18n')},
  {from: './node_modules/angular-i18n/angular-locale_en-gb.js', to: path.resolve(APP_ROOT, appConfig.buildDir + '/i18n')},
]);

Set the path to the locales in the angular config.
tmhDynamicLocaleProvider.localeLocationPattern('i18n/angular-locale_{{locale}}.js');

Finally created a ui-router hook to make sure that the locale is always set before your logic starts executing.
$transitionsProvider.onBefore({}, setLocale, { priority: 20 });

function setLocale(transition) {
  const tmhDynamicLocale = transition.injector().get('tmhDynamicLocale');
  return tmhDynamicLocale.set('fr')
    .catch((err) => {
      console.warn('Error setting locale. Using default locale.', err);
    });
}

Here is how I did it with dynamic imports:
    let inject = (lang) => tmhDynamicLocaleCache.put(lang, angular.injector(['ngLocale']).get('$locale'));

    $q.all([
        System.import('angular-i18n/angular-locale_de')
            .then(() => inject('de')),
        System.import('angular-i18n/angular-locale_en')
            .then(() => inject('en')),
        System.import('angular-i18n/angular-locale_es')
            .then(() => inject('es')),
        System.import('angular-i18n/angular-locale_fr')
            .then(() => inject('fr')),
        System.import('angular-i18n/angular-locale_pl')
            .then(() => inject('pl')),
        System.import('angular-i18n/angular-locale_pt')
            .then(() => inject('pt'))
    ]).then(() => tmhDynamicLocale.set('en'));


Block cursor for popup filter

Make the cursor in popup filter block-shaped when g:clap_popup_cursor_shape == ''.
I feel it deserves to be default, so make it default.
I noticed <Del> does not work in popup filter, so make it work as it works on neovim.

before:

after:

This looks nice!
P.S. I notice a glitch in your screencast. The highlight of fuzzy matched items, e.g., clap, are shifted two chars to the right. I don't see this issue locally. Are you using the latest version?

P.S. I notice a glitch in your screencast. The highlight of fuzzy matched items, e.g., clap, are shifted two chars to the right. I don't see this issue locally. Are you using the latest version?

Yes. This occurs from before my first PR. I'm using Windows Vim, so that may be a cause.

This glitch of highlights also seems to occur in neovim if candidates include multi-byte characters. It looks similar to that the cursor in popup filter had not been highlighted properly if the cursor includes multi-byte characters.

So it's a GUI related issue? I see no problem with kitty, iterm2 and alacritty using both neovim and vim on macOS.

I firstly encounter this problem when I was introducing the icon support and adjusted them manually. Try to adjust the offset https://github.com/liuchengxu/vim-clap/blob/master/autoload/clap/highlight.vim#L1-L38. I never test windows, so I don't know if these tweaks also work in your case.

Well, I'm still not sure why this happen, but I gathered some clues.

With maple, the glitch in the above gifs does not occur. Glitches still occur for multi-byte candidates.
The glitch seems to occur only on "files" and "gfiles". Note that they does not show icons if maple is not available.
When I make s:builtin_fuzzy_idx_offset() always returns 0, the glitch was dismissed on "files" and "gfiles". However on other providers highlights shift in the opposite direction.

I believe the root cause is the current fuzzy filter(whether the Python or Rust implementation) can't handle the multi-byte chars appropariately.
Icon support is not added to the vimscript implementation, see https://github.com/liuchengxu/vim-clap/issues/337#issuecomment-590853187.
Since that glitch is not clear yet. We could merge this first and resolve it in future. Thanks for this PR, the block-style cursor looks great!

@Bakudankun  I rewritethe icon highlight offset in #389, you can try it if you still see the misordered fuzzy matched highlights.


Use timestamps in the logs

Timestamps give more information about the analysis and build
process than the current log levels. Resolves #465

I think in case of an error the log level should still be displayed.

I've updated and log levels are kept for error, warning and critical messages.


Duplicate tabs opened when running 'yarn run serve'

Version
3.8.2
Reproduction link
https://github.com/kuretru/Bug-demo
Environment info
Environment Info:

  System:
    OS: macOS 10.14.5
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Binaries:
    Node: 12.3.1 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 74.0.3729.169
    Firefox: Not Found
    Safari: 12.1.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.0.0
    @vue/babel-preset-app:  3.8.0
    @vue/babel-preset-jsx:  1.0.0
    @vue/babel-sugar-functional-vue:  1.0.0
    @vue/babel-sugar-inject-h:  1.0.0
    @vue/babel-sugar-v-model:  1.0.0
    @vue/babel-sugar-v-on:  1.0.0
    @vue/cli-overlay:  3.8.0
    @vue/cli-plugin-babel: ^3.8.0 => 3.8.0
    @vue/cli-plugin-eslint: ^3.8.0 => 3.8.0
    @vue/cli-service: ^3.8.0 => 3.8.0
    @vue/cli-shared-utils:  3.8.0
    @vue/component-compiler-utils:  2.6.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^5.0.0 => 5.2.2 (4.7.1)
    vue: ^2.6.10 => 2.6.10
    vue-eslint-parser:  5.0.0 (2.0.3)
    vue-hot-reload-api:  2.3.3
    vue-loader:  15.7.0
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.10 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

yarn install
yarn run serve
Chrome open a tab -> "http://localhost:8080/", this is wrong
Chrome open another tab -> "http://localhost:8080/admin/", this is right

What is expected?
Chrome only open "http://localhost:8080/admin/" .
What is actually happening?
Chrome open two tabs, and one is wrong.

You can see an error in the console.

11% building 9/16 modules 7 active .../client/utils/getCurrentScriptSource.jsURIError: Failed to decode param '/%3C%=%20BASE_URL%20%%3Efavicon.ico'

Remove 'publicPath' in vue.config.js can fix this, but two tabs still appeared.

I think #4067 is also had this problem, but is was closed.

I have this problem, too.

I meet this same problem , too.
In vue-cli 3.0, it uses webpack-dev-server and this module will call a method named runOpen to open a new browser tag.
'use strict'

const open = require('opn')

function runOpen(uri, options, log) {
  let openOptions = {}
  let openMessage = 'Unable to open browser'

  if (typeof options.open === 'string') {
    openOptions = { app: options.open }
    openMessage += `: ${options.open}`
  }
  return open(`${uri}${options.openPage || ''}`, openOptions).catch(() => {
    log.warn(`${openMessage}. If you are running in a headless environment, please do not use the --open flag`)
  })
}

module.exports = runOpen

In addition to this, vue-cli 3.0 includes another module named cli-service. In serve.js, it will check whether this is the first time to compile the project. If isFirstCompile is true, then it will call a method named openBrowser in cli-shared-utils to open another browser tag.
/**
 * Reads the BROWSER environment variable and decides what to do with it. Returns
 * true if it opened a browser or ran a node.js script, otherwise false.
 */
exports.openBrowser = function(url) {
  const { action, value } = getBrowserEnv()
  switch (action) {
    case Actions.NONE:
      // Special case: BROWSER="none" will prevent opening completely.
      return false
    case Actions.SCRIPT:
      return executeNodeScript(value, url)
    case Actions.BROWSER:
      return startBrowserProcess(value, url)
    default:
      throw new Error('Not implemented.')
  }
}

function startBrowserProcess(browser, url) {
  // If we're on OS X, the user hasn't specifically
  // requested a different browser, we can try opening
  // Chrome with AppleScript. This lets us reuse an
  // existing tab when possible instead of creating a new one.
  const shouldTryOpenChromeWithAppleScript = process.platform === 'darwin' && (typeof browser !== 'string' || browser === OSX_CHROME)

  if (shouldTryOpenChromeWithAppleScript) {
    try {
      // Try our best to reuse existing tab
      // on OS X Google Chrome with AppleScript
      execSync('ps cax | grep "Google Chrome"')
      execSync('osascript openChrome.applescript "' + encodeURI(url) + '"', {
        cwd: __dirname,
        stdio: 'ignore',
      })
      return true
    } catch (err) {
      // Ignore errors.
    }
  }

  // Another special case: on OS X, check if BROWSER has been set to "open".
  // In this case, instead of passing the string `open` to `open` function (which won't work),
  // just ignore it (thus ensuring the intended behavior, i.e. opening the system browser):
  // https://github.com/facebook/create-react-app/pull/1690#issuecomment-283518768
  if (process.platform === 'darwin' && browser === 'open') {
    browser = undefined
  }

  // Fallback to open
  // (It will always open new tab)
  try {
    var options = { app: browser }
    open(url, options).catch(() => {}) // Prevent `unhandledRejection` error.
    return true
  } catch (err) {
    return false
  }
}

Does vue make a mistake ?

I have got the same problem under Win 10 after I update cli version from 3.4.1 to 3.8.0. What is weird is that problem is not fixed when I revert the update

Fixed in 3.8.3


Add invocation to  BuildConfig

Fixes ##84

Adds invocation details to the BuildConfig
Adds a new example config TOML file (build.toml)
Updates the provenance generation logic

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

No longer relevant.


Maven repo https://www.matthewo.tech/maven/ is offline

We'd like to try out fast-load, but it looks like the Maven repo https://www.matthewo.tech/maven/ in the Installation instructions is currently offline. Are you still supporting this library?

fast-load is still supported. As far as I'm aware the Maven repo is up and running. Would you please confirm that this works on your development computer.

This turned out to be a network configuration issue on my end that was blocking dependency resolution. Apologize for the confusion! Thanks for your efforts supporting this library for the FIRST community.


On styled-components for React Native, Picker throws a console warning

styled-components for React Native imports Picker from react-native (source code where this happens) and not from the recently recommened package @react-native-community/picker. Because of that this React Native code fires a warning:
Warning: Picker has been extracted from react-native core and will be removed in a future release. It can now be installed and imported from '@react-native-community/picker' instead of 'react-native'. See https://github.com/react-native-community/react-native-picker
Every time styled.Picker is used it will throw the warning on console. As soon as you stop using the Picker styled component the warning is gone.
This happens on a project with:

"react": "16.13.1"
"react-native": "0.62.0"
"styled-components": "5.1.0"

Same behaviour for PickerIOS.
I think the warning started happening after updating to React Native 0.62.

I've the same warning

Use this workaround:
`
import { Picker } from "@react-native-picker/picker";
const StyledPicker = styled(Picker)``
`

Closing due to inactivity.
This isn't really an issue I think we should resolve, unless we make the React Native version a separate package of the mainline one, because currently the implementation is pretty much frozen in place. See: #1617


Support for mSpot

https://market.android.com/details?id=com.mspot.android.aria
It lets you listen to music in cloud.

App is gone from market.
@klinacz has this app changed names or do you have a different app you'd like support for?
Otherwise this issue is CLOSED


replace gplot with ggplot2 ?

Pipelines to convert are sb_simulate and sb_param_scan__single_perturb.
The pipeline sb_param_scan__double_perturb must be converted from matlab to R using ggplot2.
The legends must be converted.

NOTE 1: For deterministic simulation, only 1 simulation is needed, not two as wrongly inserted in the configuration file.
NOTE 2: Create time courses vs experimental data with ggplot2. There should be two variants for this: model vs raw data points AND model vs mean+sd data points.
Finally, the dependency gplot can be removed from the project.

It would be worth applying this to sb_simulate too.

Converted gplot to ggplot2 for sb_simulate pipeline.

Need to add labels to the legend.
Need to add a new test set including over-expression and test the resulting legend.


The operator at the beginning of update() must be || instead of `…

At the beginning of update(), there is a  validation for options.dataViews, and the operator must be || instead of &&, otherwise, if the input is not valid, evaluating the second operand will fail with:
Uncaught TypeError: Cannot read property '0' of undefined

Hi @kiewic, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@kiewic, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thank you Gilberto! @kiewic


upstream status of the mod_ssl patch

In the hope this module could be soon massively used, I'd be interesting to know whether the mod_ssl patch has been upstreameed.
In Debian it has not yet been integrated to the binary package ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877341 / https://anonscm.debian.org/cgit/pkg-apache/apache2.git/tree/debian/patches?h=stretch ).
What's the status of Apache's httpd w.r.t?

We just released 2.4.29, still without it. I will propose it for backporting into the next release.

More precision:
http://svn.apache.org/viewvc?view=revision&revision=1820075
https://fisheye.apache.org/changelog/httpd?cs=1820075
Hopefully in 2.4.30 : https://www.apachelounge.com/Changelog-2.4.html


Record pointer of view instead of parent

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@d8d050c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #198   +/-   ##
=======================================
  Coverage        ?   79.16%
=======================================
  Files           ?       13
  Lines           ?     2741
  Branches        ?        0
=======================================
  Hits            ?     2170
  Misses          ?      571
  Partials        ?        0

Continue to review full report at Codecov.

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


[3] Tutorial: Compliant Kubernetes on OVH Managed Kubernetes

Acceptance criteria:

https://compliantkubernetes.io/operator-manual/lifecycle/ovh-kubernetes contains prose and code which allows someone to set up Compliant Kubernetes on OVH Managed Kubernetes
Said document contains code that can be copy-pasted.
Said code has all "hard-coded" file locations, paths, key names, cluster names, etc. in shell variables.

@cristiklein I'm guessing https://compliantkubernetes.io/operator-manual/lifecycle/ovh-kubernetes actually means https://compliantkubernetes.io/operator-manual/ovh-kubernetes ?

@Xartos You are guessing correctly. :smile: Thanks for noticing.


fix: correct the formatting of the package.json for some snippets

It appears these issues were never resolved in another PR that I had reviewed (and missed! :frowning_face:), so I'm raising this PR to fix the formatting.

Will re-open once the current set of PRs land.