let configure check for supported c++11 flags and set -DVCL_CAN_STATIC_CONST_INIT_FLOAT accordingly

created autoconf based configure script.

What do think about using the configure script? This also makes the Makevars generation more CRAN compliant. And the test whether to use DVCL_CAN_STATIC_CONST_INIT_FLOAT =0 or 1 is done by trying to compile some example code.

first - i am thrilled that you have this working and i am making another attempt to address the unexplained OS X failure on travis though i am not hopeful.  i've looked this over a couple of times.  i don't know enough (near nil) about autoconf to understand what is happening here.  so i have a few questions:
(1)  are there other benefits to having this autoconf functionality available?
(2)  how challenging is this to maintain?  let us suppose i want to change the ants tag ( e.g. https://github.com/stnava/ANTsR/commit/bad1901d1ea0436e27e3510884136a983c55548b ), is this still a change that must be made in only one location?  or does it become two?
(3) what is the likelihood that these issues will continue in the future?
(4) i am not sure this is possible but is it better (i.e. easier to maintain, fewer lines of code ) to just generate a brief Makevars given detected  linux version?
(5)  what is the new src/m4/vcl_cxx_static_const_init_float.m4?  why is this necessary?
anyway, forgive me if these are ignorant questions.

(1) Maybe if there are more compatibility challenges, tests will be easier to implement
(2) simply replace the tag in configure.ac (https://github.com/zarquon42b/ANTsR/blob/autoconf-test/configure.ac#L39) and run autoreconf (on OSX you can run
brew install autoconf to install it)
(3) No idea, the issue is dependant on users and their config. At the moment the build, however, is broken for current Linux distributions.
(4) the issue is not linux or osx but the compiler version and its configuration: E.g. on ubuntu 14.04 with the clang3.4 it works with DVCL_CAN_STATIC_CONST_INIT_FLOAT =1 but fails on ubuntu 12.04 with the same clang version. I could not figure out a simple way to determine which flag to use other than to compile some example code.
(5) this is simply to keep configure.ac cleaner (using autoconf you usually create m4 files containing your  custom tests)
Nevermind, I only know about this stuff because CRAN forced me to do this in order to get my package Rvcg submitted.

One thing: you never edit configure, only configure.ac (you can add posix compliant shell code as you like and on top can use a lot of handy macros  - e.g. check for header availability, etc)

ok - my fear is that this change will make antsr nearly impossible to maintain/compile for anyone other than dedicated people (me, you).   it also means additional system changing dependencies ( home-brew ).  perhaps i am in the minority, but i try to avoid home-brew as much as possible ...
i am interested in learning these tricks but am not sure of the impact it will have on general usability.  i suppose the best deal would be to just auto-generate binaries on both OS X and linux via travis.
anyway, i need to think more about this ... @jeffduda  - do you have any opinions on this?
almost seems like some of this is consequence of a clang bug/inconsistency.
so it would seem unfortunate to add this complexity to antsr due to something that is likely to go away in the future.

I understand your fear, however autoconf is a very commonly used and not that excentric ;). About homebrew: As I am not a OS X user (only running a VM for testing purposes), this was the fastest way to set up autoconf to fix the OS X issues (actually finding the typo).
The issue we are dealing with is not a bug, it is owed to simply different compiler configurations/versions regarding this feature (therefore the test whether it is supported properly, which would be the "clean" way to do this). However, if you do not want to use autoconf, you should cheat travis like that in .travis.yml (at least as long as travis uses 12.04):
- if [ "$TRAVIS_OS_NAME" == "linux" ]; then sed -i '-DVCL_CAN_STATIC_CONST_INIT_FLOAT=1|-DVCL_CAN_STATIC_CONST_INIT_FLOAT=0|' ANTsR/src/Makevars
fi

instead of breaking the install for the Linux users using current distributions (probably most of them). I will test other distributions like fedora next week. That way, the dirty hack is only in the travis config instead of in the packages Makevars file.

I implemented the travis-cheat here: https://github.com/zarquon42b/ANTsR/tree/cheat-travis-vcl-can-static  and it builds correctly: https://travis-ci.org/zarquon42b/ANTsR/jobs/102560521.
However, I would suggest to add a note to README that compilers that do not support DVCL_CAN_STATIC_CONST_INIT_FLOAT=1 are not working and document the manual workaround (editing src/Makevars)

i suppose the best deal would be to just auto-generate binaries on both OS X and linux via travis.

This is not a good idea for linux because there is no such thing as the linux OS (but many), as linux is only the kernel and the distributions ship with a large variety of system specific libraries/compilers etc.. E.g. ANTsR on recent Ubuntu versions do not compile with your ITKR binary. This is one cause why there are no linux binaries on CRAN.

I also try to avoid homebrew whenever possible and I definitely agree that
this further complicates maintenance/development, but it seems like this
(autoconf) might be a necessary evil in this case. I think at this point,
we definitely need to put together a developers manual that describes these
various issue and why thing are done the way they are. It would also help
for less complicated things like naming conventions, etc. It's much easier
to read one doc, than search though a bunch of old emails trying to figure
out what's going on.
On Thu, Jan 14, 2016 at 10:46 AM, stnava<EMAIL_ADDRESS>wrote:

ok - my fear is that this change will make antsr nearly impossible to
maintain/compile for anyone other than dedicated people (me, you). it also
means additional system changing dependencies ( home-brew ). perhaps i am
in the minority, but i try to avoid home-brew as much as possible ...
i am interested in learning these tricks but am not sure of the impact it
will have on general usability. i suppose the best deal would be to just
auto-generate binaries on both OS X and linux via travis.
anyway, i need to think more about this ... @jeffduda
https://github.com/jeffduda - do you have any opinions on this?
almost seems like some of this is consequence of a clang
bug/inconsistency.
so it would seem unfortunate to add this complexity to antsr due to
something that is likely to go away in the future.
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTsR/pull/70#issuecomment-171678444.


chore: connect_params refactoring

How it was in earlier version:
You can pass min_connections and max_connections but you cannot pass minsize and maxsize. You can pass connection_timeout which converts to timeout param in aiopg.create_pool and connect_timeout param in aiomysql.create_pool. autocommit param is always true for mysql db. enable_json and enable_hstore is always False for NoExt PostresqlDatabase. enable_json is always True  and enable_hstore depends on register_hstore for PostgresqlExtDatabase

#276


HBASE-26074: Fix testLogLevelByHttps/testLogLevelByHttpsWithSpnego

See the jira for context.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 42s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
10m  5s
branch-1 passed

+1 :green_heart:
compile
0m 41s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
compile
0m 45s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
checkstyle
1m 44s
branch-1 passed

+1 :green_heart:
shadedjars
3m  2s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
branch-1 passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 41s
branch-1 passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+0 :ok:
spotbugs
3m  5s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m  2s
branch-1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 51s
the patch passed

+1 :green_heart:
compile
0m 39s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javac
0m 39s
the patch passed

+1 :green_heart:
compile
0m 44s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
javac
0m 44s
the patch passed

+1 :green_heart:
checkstyle
1m 31s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
2m 50s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 36s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 30s
the patch passed with JDK Azul Systems, Inc.-1.8.0_262-b19

+1 :green_heart:
javadoc
0m 42s
the patch passed with JDK Azul Systems, Inc.-1.7.0_272-b10

+1 :green_heart:
findbugs
2m 52s
the patch passed

_ Other Tests _

-1 :x:
unit
135m 42s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 39s
The patch does not generate ASF License warnings.

183m 47s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestAdmin1

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3466/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3466

JIRA Issue
HBASE-26074

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 39509f3bcfd7 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-agent/workspace/Base-PreCommit-GitHub-PR_PR-3466/out/precommit/personality/provided.sh

git revision
branch-1 / 5ece9cef

Default Java
Azul Systems, Inc.-1.7.0_272-b10

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:Azul Systems, Inc.-1.8.0_262-b19 /usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_272-b10

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3466/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3466/1/testReport/

Max. process+thread count
4181 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3466/1/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


⚠ Bofrost.lu has degraded performance

In 7de8760, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1068 ms

Resolved: Bofrost.lu performance has improved in ed75985 after 8 minutes.


Add Elizabeth line, etc

This adds the Elizabeth line, along with renaming a few stations to be exactly like the Tube map (https://content.tfl.gov.uk/standard-tube-map.pdf). This is generated with https://github.com/mohawk2/p5-Map-Metro-London/blob/main/examples/graph-make
This does remove the fast-track from Moor Park to Harrow-on-the-Hill plus one other. My rationale for this is that the fast line isn't really a choice as it's only certain times of day, and you're still passing through the intermediate stations, so I thought it not a useful thing to have in your data.

I have been thinking of doing this (Elizabeth Line) for so long. Thanks for your contributions. @mohawk2

@mohawk2 with your recent change, do you think this needs updating too?
https://github.com/manwar/Map-Tube-London/blob/master/lib/Map/Tube/London/Line/Overground.pm

Thanks for the merge!
The Overground got renamed to 6 individual lines: https://tfl.gov.uk/info-for/media/press-releases/2024/february/london-s-overground-lines-to-be-given-new-names-and-colours-in-historic-change-to-capital-s-transport-network
I won't be making those sub-packages because I don't see the benefit of having them, and I will be using the time I can dedicate to this public-transport modelling to making the implementation better (using the Graph module more, etc). I think the top Map::Tube::London might hyperlink to "TfL information" and leave it at that.

(And Street and Tunnel were because that was an easier way to capture the current other_link stuff while staying fairly generic)

Speaking of separate packages, I will mention one more time: I think you should incorporate into the main Map::Tube:

Map::Tube::Cookbook
Test::Map::Tube
Map::Tube::Plugin::FuzzyFind

You are creating an unnecessary dependency mess between these things which requires extra releasing work and management, for no benefit I can see.

@mohawk2 I have added Map::Tube::Cookbook to the main Map::Tube. With regard to Map::Tube::Plugin::FuzzyFind, it is owned by fellow contributor Gisbert W. Selke. About Test::Map::Tube, I will think about it before adding it. I would see if I can rename it to something like Map::Tube::Test to make it part of the main distribution. Just to make sure, if I do then nobody screams.

For FuzzyFind, you'd need to ask GWS to transfer ownership of the distro, since only having co-maint would cause problems for future M:T maintainers (or at least, that's the approach I'm taking with PDL).
For Test::Map::Tube, why rename it? It's very well named - it's just that conceptually it belongs within the Map::Tube distro. Test::Moose is within Moose: https://metacpan.org/pod/Test::Moose. The main work involved would just be to bump the T:M:T version (now 0.60 as I'm sure you know) as you incorporate it, probably switching it to track the M:T version (3.something, so that works great).

@mohawk2 That would be a big help if you can please. I am wondering if the move would affect others who has Test::Map::Tube as direct dependent e.g. Map::Tube::Moscow, Map::Tube::Prague.

@mohawk2 That would be a big help if you can please. I am wondering if the move would affect others who has Test::Map::Tube as direct dependent e.g. Map::Tube::Moscow, Map::Tube::Prague.

It will not affect them at all. The dependency-resolver will simply see two dependencies (Map::Tube, Test::Map::Tube) satisfied by a single distro. I promise this is a zero-impact thing!

@mohawk2 Thanks for the assurance, then please go ahead and create pull request for the move. Also can you please add couple of lines about the move in the main pod so that new user would be aware of the changes.

I've just made https://github.com/manwar/Map-Tube/pull/11 - I don't know how the POD should be changed so I'll leave that with you. If it were me, I'd just put the note in Changes and leave it at that, since it's a user-invisible change?

@manwar Please could you release this? One of the things fixed by this update is to put Elephant and Castle on the Northern line, which caused me great confusion in making my M:T:P:Graph update till I realised I was using the latest released version, and checked it.

@mohawk2 Just released v1.38.
https://metacpan.org/release/MANWAR/Map-Tube-London-1.38


Nucleus Setupperms No longer working with newer updates

I've tested a few versions.
4.3.8 On ore appears to be the last working version
4.3.75 Also on ore is where the breakage begins.
I also tested the latest and oldest available versions on Jenkins (that I could manage to find)
4.4.4 and 4.3.108 and neither of those worked.
Tested with
Nucleus: 1.9.2-S7.1
Sponge: 7.1.6-RC3616
Steps to reproduce:
/lp creategroup mod
/nucleus setupperms mod mod
/lp group mod permission list -> just for listing perms, also doesn't show up in editor either.

Thanks for reporting - sorry it took a while for me to get to fixing it! :)


File transfer optimization 2 Distributed file storage and transfer between nodes

Is your feature request related to a problem? Please describe.
The current cross-node tox scheme file transfer performance is too poor, the file storage is single point storage, unreliable
Describe the solution you'd like
Refer to the distributed file storage scheme to organize a supplementary scheme suitable for the storage and transmission of our chain file data
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Between nodes <->, file transfer considers P2P shared data block mode (refer to IPFS)
Suspend the task for now


libopae: fix metrics api memory leaks

Coverage increased (+0.03%) to 79.684% when pulling 44af5e3a3e2ccd6326e285a20bf575a57e62f0fa on aravuri/metrics_1 into 6e2b21688831e1025a0c367a5d31155bf31d8e5d on master.


High RAM usage for ESP32 port

Hi, as you can see in this https://github.com/MaJerle/lwcell/blob/355380a54aabda0279fcc9a7ac0bcd2df0d1f018/lwcell/src/system/lwcell_ll_esp32.c#L152, you are allocating 0x10000 ( ~ 65KB) of device ram for LWCELL memory, I checked the stm32 port also but you used only 0x1000 bytes for its memory,  is this intentional? or should we fix it? it is using about 80% of our device DRAM.
Thank you.

Thanks! That freed up a lot of memory! 😄


[Main Course] - Apache

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Post for Apache
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update

How Has This Been Tested?

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

感谢佳辉分享！LGTM！ 之后有没有打算选几个深入介绍？ ：）

看情况吧，碰到感兴趣的可以深入研究下。


Fix systemlib rule to support gRPC

Systemlib rules currently can't handle the systemlib build file appearing in the system link dictionary.
This occurs in the gRPC target here:
https://github.com/tensorflow/tensorflow/blob/a4dfb8d1a71385bd6d122e4f27f86dcebb96712d/tensorflow/workspace2.bzl#L639
Gentoo (the primary client of systemlib) only packages TF 2.4.0,
potentially explaining why the new systemlib logic hasn't been exercised
for gRPC.
This change fixes the issue with the systemlib logic.

@perfinion what do you think of this approach?


question regarding TDX

Hello!
I have a quick question!
Where can I find the TDX zkVM guest code for risc0? It seems that the zkVM guest only implements the SGX.
https://github.com/automata-network/tdx-attestation-sdk/blob/main/zk/risc0/methods/guest/src/main.rs
Thanks in advance!

I figured that verify_quote_dcapv4 implements the TDX. I got confused by these lines.
journal_output.extend_from_slice(&sgx_intel_root_ca_cert_hash);
journal_output.extend_from_slice(&sgx_tcb_signing_cert_hash);
journal_output.extend_from_slice(&sgx_intel_root_ca_crl_hash);
journal_output.extend_from_slice(&sgx_pck_crl_hash);

Hello!
I have a quick question!
Where can I find the TDX zkVM guest code for risc0? It seems that the zkVM guest only implements the SGX. https://github.com/automata-network/tdx-attestation-sdk/blob/main/zk/risc0/methods/guest/src/main.rs
Thanks in advance!

Currently Intel SGX v3 / v4 and Intel TDX v4 Quote Verification are located in dcap-rs. And in Risc0 and SP1 guest program use this for the verification.

I figured that verify_quote_dcapv4 implements the TDX. I got confused by these lines.
journal_output.extend_from_slice(&sgx_intel_root_ca_cert_hash);
journal_output.extend_from_slice(&sgx_tcb_signing_cert_hash);
journal_output.extend_from_slice(&sgx_intel_root_ca_crl_hash);
journal_output.extend_from_slice(&sgx_pck_crl_hash);

These wordings are coming from the official Intel SGX DCAP docs and SGXDataCenterAttestationPrimitives repo.


Add tests to client

The main part is the first commit, which adds base classes for the tests.
Generally, the tests are able to verify the client connects to end-points it is supposed to connect to, does not connect to anything else and that it has the correct output.
Since the client code is now included in the coverage measure, it is expected to drop a bit.

Looks good to me.
Well done.


3D bounding box orientation

Hello,
I am interested in using the Kitti360 dataset and I have some questions.
Firstly, what is the structure of the 3D Bounding Boxes? This is how I understand it: for every object, there is a matrix of vertices (basically the corner points of the bounding boxes). This gives us a Bounding box in the origin of the coordinate frame (camera). These bounding boxes are then translated and rotated using the transform matrix. Is this correct?
Are the 3D bounding boxes created using a convention? For example in 2D the DOTA dataset contains 4 points, where the first point represent the front left of the object (or at least in most cases). Does the order of vertices matter in this sense? Or does the transform matrix contain this information? (I am mostly interested if the Bounding Boxes are symmetrical or not? -- does it matter if the rotation is 0 or 180 degrees?)
Thanks

I made a few tests:
Basically, you can have the angle of rotation along the Z axis or each object from its rotation matrix. This rotation angle represents the direction of the front of the object (at least for most categories) in the global coordinate system. Then the cam2world rotation matrix can give you the rotation angle of the camera in the current frame (rotated 90 degrees), also in the global coordinate system. Subtracting one from the other results in the object direction angle compared to the current camera position.
This works for most vehicles (car, rider, bicycle, trucks, etc.), not so much for pedestrians. Building types seem to be oriented towards the street. There are a few mistakes (e.g. some motorcycles are wrongly annotated, especially if under blanket).
Waiting for a confirmation from the authors on my results.


Check presence of JDK Class before instanciating JdkProvider

Security needed, as Under Weblogic 10.3 Oracle Jdk 6, ClassNotFoundException is thrown only when current() is called, not at instanciation.

It appears there are one or more non-breaking spaces in the file:
[ERROR] /home/travis/build/dropwizard/metrics/metrics-core/src/main/java/com/codahale/metrics/ThreadLocalRandomProxy.java:[38,1] illegal character: '\u00a0'

I used the Github online editor, and copy / pasting in Notepad++, I don't see any special character.
I will try a full clone on my laptop.

Need to pull into 3.2 branch as well.

I made a PR for 3.2-development branch : https://github.com/dropwizard/metrics/pull/1131

Sorry it took so long to review. Thank you for testing the library under Weblogic! It's great to hear from users from different environments. Regarding the fix, I think a better approach would be to do the same as for LongAdderProxy and call jdkProvider.current(), this should trigger the class loading even in secure environments. We also could catch Throwable instead of NoClassDefFoundError to be more robust and not leave the INSTANCE variable as null.

I had not looked at LongAdderProxy (since no problem with it), but yes, it would be consistent to use the same code. So, will you fix ThreadLocalRandom (at least in 3.1-maintenance), or do you expect me to commit it ? Thanks.

Great! I will then prepare a pull request for the 3.1 branch and make a release!

Closed via #1136

I have release Metrics 3.1.5. It should be available in the Maven Central repository in a couple of hours.

OK, 3.1.5 is validated on Weblogic 10.3. Thanks !


iOS [feature request] Allow dark mode separate from system setting

I'd like to be able to set NNW to always use dark mode, independent of the system setting.
For whatever reason, I've developed a preference for reading light text on dark backgrounds for stuff like RSS, ebooks, etc. Though I generally prefer scheduled dark/light mode for the rest of the OS.

That is a feature that we did implement for iOS 5.0.1.  Sign up to test it to get early access.

@vincode-io Just installed 5.0.1. Looks great. Thanks!


update acorn depencency, add acorn options for import/export

As discussed in #21 I have updated the dependencies, and added some acorn options to allow for the parsing of import/export statements.
Let me know if you need me to make any changes!

Coverage remained the same at 96.8% when pulling 4d2f431d1b0d57258d508289a3306f46608edede on BenDiuguid:feature/update-acorn into a966115d1d443ea8a9c2f592a378a6b78fde1756 on MichaReiser:master.

Makes sense! Would you like me to Bump up the minor version in the package.json as well?

Coverage decreased (-0.1%) to 96.667% when pulling 75ea8a9a8d5676d761f4f7a0b5b4057491158a35 on BenDiuguid:feature/update-acorn into a966115d1d443ea8a9c2f592a378a6b78fde1756 on MichaReiser:master.

I updated the README.md with a little bit of documentation on working in the options with webpack v1 and webpack v2, and I have tested it locally in a webpack v2 project that I'm working on. I also updated the example and tested it with webpack v1.
I guess I need to update the tests to improve the coverage slightly 😃

Coverage increased (+0.06%) to 96.863% when pulling 88d21e3361e227702bd78ce5d8a7ced363bc7692 on BenDiuguid:feature/update-acorn into a966115d1d443ea8a9c2f592a378a6b78fde1756 on MichaReiser:master.

Tests updated, let me know what you think!

I have time to tackle these changes tomorrow!
And I agree with all your comments! I didn't know about loader-utils so that's really cool!
And I tried object assign and object spread, but I wasn't sure if the version of typescript supported it?
I have a lot of is experience, but very little typescript experience :smile:

Coverage increased (+0.08%) to 96.875% when pulling 6d8b28ec05bc913e9596316c375893ac15682ba0 on BenDiuguid:feature/update-acorn into a966115d1d443ea8a9c2f592a378a6b78fde1756 on MichaReiser:master.

I addressed your comments, and things should be good to go 👍

Thx for your pull request. I made some smaller adjustments, but is now merged and released!

Awesome! Thanks so much!


Next Page button results in unhandled error (web UI)

This is a Bug Report
Description
Clicking "Next Page" results in an error
For bug reports:

Description of the issue

[2017-01-24T22:59:29.665Z] INFO: Running forced "pageRoute" intent
[2017-01-24T22:59:29.665Z] DEBUG: running hook: pageRoute:pageRoute

  Type Error ---------------------------------------------

     context.button.value.split is not a function

Steps to reproduce

Ask davis "what happened yesterday?" in web UI
Click "Next Page" button

Desired behavior
Show next page of results
Actual behavior
Shows error

Already fixed


How to do the voting for May Constitutional Amendment

I think we can do email voting like last time.

that sounds good to me, maybe require that they include a specific string in the subject line so we can grep for all the votes as needed.
one potential drawback is that this isn't anonymous and we can see who cast which vote.

I confirm we can announce the modified information in the constitution by e-mail to the members in the mail list, and officially call for votes. After the voting period we can insert the changes. We can use three weeks as voting period.


How can I stop writing?

I write on page scrolling.
I need to stop writing when user see some element.
How can i stop writing even if actor write only half of sentence.

Hello @pagoad!
For now, TheaterJS doesn't provide neither a stop or pause method. It'd be probably interesting to think about implementing it.
What's your real need? You want to "pause" the animation, even half of sentence, and then be able to play from where it left? Or would you start from scratch again? Maybe just call "play" and type the whole sentence again?

When I scrol page i want to write in header some sentences.
Every section has his own.
When I scroll fast "Actor" has no chance to write sentence before next section will start.
And it is look strange when you are on bottom of page and you see he is writing  unaccomplished sentences one after the other

Thank you for the details @pagoad, I'm thinking about implementing such feature in TheaterJS. Do you have a link to your site so I'd have a look?

I'm coding this website right now, I have it only on localhost.
When i finish i will show you :)
When could you implement this feature? How much time? :)
Thx!

Hello @pagoad, the stop method is now implemented. Have a look at the documentation. Let me know when your project is available online :)

Thx!  ;)

It does not work :(
If I stop it, i cant resume with new text.
 headerTheater.stop();
 headerTheater.play();
 headerTheater.write('Header:' + h2, 100);

Nothing is happen.

I am not sure to understand what you are trying to do, could you please post the whole code relevant to your usage of TheaterJS?
Also, note that the write method implicitly calls play (unless you have set autoplay to false). So:
headerTheater.stop();
headerTheater.write("Header:" + h2, 100);

Should be enough.

For example:
$(window).on('scroll', function() {
    $('section:in-viewport(200)').each(function() {
            var h2 = $(this).data('h2');
            headerTheater.stop();
            headerTheater.write('Header:' + h2, 100);
    }
});

It doesnt work. Without .stop() it's work, but when I use this function text dont want to show.

Reopening as the play and stop methods are not working properly together.

The play method should now work as expected. Have a look at this fiddle, it will probably help you deal with your case. Let me know if you have any questions ;)


cant build openssl:x64-linux on Ubuntu 16.4

./vcpkg build openssl:x64-linux
Package: openssl:x64-linux
Vcpkg version: 0.0.113-unknownhash
install-x64-linux-dbg-out.log

Same issue here.

FWIW after messing a little bit if openssl portfile. I find this line cause  the error :
https://github.com/Microsoft/vcpkg/blob/master/ports/openssl/CMakeLists.txt#L104
CMake interprets "${CFLAGS}" as " " and Configure cannot understand it.

Fix in 1d52df8140104a969699f774dbae4fe25d2f6d00.


Release tags

Tag the commit that publishes a new version of r2env in pip otherwise git log is confusing to read.

Should be already considered.


Add @callback jsdoc tag

Fixes https://github.com/Microsoft/TypeScript/issues/7515
Example:
/**
  * @callback FooHandler
  * @param {string} [eventName]
  * @param eventName2 {number | string}
  * @param eventName3
  */

is the equivalent of TypeScript code:
type FooHandler = (eventName?: string, eventName2: number | string, eventName3: any) => void;

Types defined by @callback tag are block scoped, and will show up in the navigate to list.

@zhengbli please check with @sandersn on this PR and https://github.com/Microsoft/TypeScript/pull/10671

We should discuss which order to merge this vs #10671. As far as I can tell, they shouldn't overlap very much except

a few additions of skipWhitespace() in the parser (since #10671 makes jsdoc now track whitespace)
doc comments on callback parameters need to work, which means more tests and possibly some code changes too.

@zhengbli can you update his change?

closing this for now.

Note that once @typedef supports generics via @template, @callback should too.


Cursor is not changing in Alacritty

When I use Alacritty as terminal, and with the alacritty terminfo they provided, the cursor shape does not change in vi-mode.
The pertinent alacritty.yml lines are:
https://github.com/g6ai/dotfiles/blob/db16f7463092592dc347fc946f1e78ef711ecb32/alacritty/alacritty_macos.yml#L352-L378
And I use these zsh-vi-mode settings in my .zshrc:
ZVM_KEYTIMEOUT=0.05
ZVM_INSERT_MODE_CURSOR=$ZVM_CURSOR_BLINKING_BEAM
ZVM_NORMAL_MODE_CURSOR=$ZVM_CURSOR_BLINKING_BLOCK

I also use alacritty but it works for me

And in zsh-vi-mode I have only set
ZVM_LINE_INIT_MODE=$ZVM_MODE_NORMAL

@GiancarloAparicio Thanks for the info! Yes I'm using powerlevel10k as zsh theme. So I disabled it and use oh-my-zsh default theme (robyrussell), but the problem is still there. Could you provide your config so I can investigate?

My alacritty configuration is:
# Sorry, I don't have everything in a dotfile repository :(
env:
    TERM: xterm-256color

window:
    dimensions:
        columns: 115
        lines: 35
    padding:
        x: 0
        y: 0
    decorations: full

background_opacity: 0.88

dpi:
    x: 128.0
    y: 128.0

draw_bold_text_with_bright_colors: true

font:

    normal:
        family: 'MesloLGS NF'

    bold:
        family: 'MesloLGS NF'
    italic:
        family: 'MesloLGS NF'

    size: 9.0

    offset:
        x: 0
        y: 0

    glyph_offset:
        x: 0
        y: 0

    use_thin_strokes: false

debug.render_timer: false

colors:

    primary:
        background: '0x002635'
        foreground: '0xe6e6dc'
    normal:
        black: '0x00384d'
        red: '0xc43061'
        green: '0x7fc06e'
        yellow: '0xf08e48'
        blue: '0x1c8db2'
        magenta: '0xc694ff'
        cyan: '0x00cccc'
        white: '0x77929e'
    bright:
        black: '0x517f8d'
        red: '0xff5a67'
        green: '0x9cf087'
        yellow: '0xffcc1b'
        blue: '0x7eb2dd'
        magenta: '0xfb94ff'
        cyan: '0x00ffff'
        white: '0xb7cff9'
    cursor:
        text: '0x002635'
        cursor: '0xffcc1b'

key_bindings:
    - { key: V, mods: Command, action: Paste }
    - { key: C, mods: Command, action: Copy }
    - { key: Q, mods: Command, action: Quit }
    - { key: W, mods: Command, action: Quit }
    - { key: N, mods: Command, action: SpawnNewInstance }
    - { key: Home, chars: "\x1bOH", mode: AppCursor }
    - { key: Home, chars: "\x1b[1~", mode: ~AppCursor }
    - { key: End, chars: "\x1bOF", mode: AppCursor }
    - { key: End, chars: "\x1b[4~", mode: ~AppCursor }
    - { key: PageUp, mods: Shift, chars: "\x1b[5;2~" }
    - { key: PageUp, mods: Control, chars: "\x1b[5;5~" }
    - { key: PageUp, chars: "\x1b[5~" }
    - { key: PageDown, mods: Shift, chars: "\x1b[6;2~" }
    - { key: PageDown, mods: Control, chars: "\x1b[6;5~" }
    - { key: PageDown, chars: "\x1b[6~" }
    - { key: Left, mods: Shift, chars: "\x1b[1;2D" }
    - { key: Left, mods: Control, chars: "\x1b[1;5D" }
    - { key: Left, mods: Alt, chars: "\x1b[1;3D" }
    - { key: Left, chars: "\x1b[D", mode: ~AppCursor }
    - { key: Left, chars: "\x1bOD", mode: AppCursor }
    - { key: Right, mods: Shift, chars: "\x1b[1;2C" }
    - { key: Right, mods: Control, chars: "\x1b[1;5C" }
    - { key: Right, mods: Alt, chars: "\x1b[1;3C" }
    - { key: Right, chars: "\x1b[C", mode: ~AppCursor }
    - { key: Right, chars: "\x1bOC", mode: AppCursor }
    - { key: Up, mods: Shift, chars: "\x1b[1;2A" }
    - { key: Up, mods: Control, chars: "\x1b[1;5A" }
    - { key: Up, mods: Alt, chars: "\x1b[1;3A" }
    - { key: Up, chars: "\x1b[A", mode: ~AppCursor }
    - { key: Up, chars: "\x1bOA", mode: AppCursor }
    - { key: Down, mods: Shift, chars: "\x1b[1;2B" }
    - { key: Down, mods: Control, chars: "\x1b[1;5B" }
    - { key: Down, mods: Alt, chars: "\x1b[1;3B" }
    - { key: Down, chars: "\x1b[B", mode: ~AppCursor }
    - { key: Down, chars: "\x1bOB", mode: AppCursor }
    - { key: Tab, mods: Shift, chars: "\x1b[Z" }
    - { key: F1, chars: "\x1bOP" }
    - { key: F2, chars: "\x1bOQ" }
    - { key: F3, chars: "\x1bOR" }
    - { key: F4, chars: "\x1bOS" }
    - { key: F5, chars: "\x1b[15~" }
    - { key: F6, chars: "\x1b[17~" }
    - { key: F7, chars: "\x1b[18~" }
    - { key: F8, chars: "\x1b[19~" }
    - { key: F9, chars: "\x1b[20~" }
    - { key: F10, chars: "\x1b[21~" }
    - { key: F11, chars: "\x1b[23~" }
    - { key: F12, chars: "\x1b[24~" }
    - { key: Back, chars: "\x7f" }
    - { key: Back, mods: Alt, chars: "\x1b\x7f" }
    - { key: Insert, chars: "\x1b[2~" }
    - { key: Delete, chars: "\x1b[3~" }

mouse_bindings:
    - { mouse: Middle, action: PasteSelection }

mouse:
    double_click: { threshold: 300 }
    triple_click: { threshold: 300 }

selection:
    semantic_escape_chars: ',│`|:"'' ()[]{}<>'

My .zshrc is divided into several files, but the general configuration and that of zsh-vi-mode is:
if [[ -r "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" ]]; then
  source "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh"
fi

# Path to your oh-my-zsh installation.
export ZSH="$HOME/.oh-my-zsh"

plugins=(
    git
    asdf
    fzf-tab
    fzf
    zsh-autosuggestions
    zsh-vi-mode
)

source $ZSH/oh-my-zsh.sh
source $ZSH_CUSTOM/source/fzf.zsh
....
#-------------------------------------------------------------------

export MANPATH="/usr/local/man:$MANPATH"

# You may need to manually set your language environment
export LANG=en_US.UTF-8

# Preferred editor for local and remote sessions
# if [[ -n $SSH_CONNECTION ]]; then
#   export EDITOR='vim'
# else
#   export EDITOR='mvim'
# fi
export EDITOR='nvim'

#-------------------------------------------------------------------
# To customize prompt, run `p10k configure` or edit ~/.p10k.zsh.
[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh

#-------------------------------------------------------------------
# Always starting with normal mode for each command line
ZVM_LINE_INIT_MODE=$ZVM_MODE_NORMAL

# Define an init function and append to zvm_after_init_commands
function my_init() {
  [ -f ~/.fzf.zsh ] && source ~/.fzf.zsh
}
zvm_after_init_commands+=(my_init)

I have not configured much of zsh-vi-mode and it works for me, maybe it is the order in which the plugins are executed, I could not tell you the truth

@GiancarloAparicio Great, I'll try investigate this issue with your config. I only recently switched to Alacritty, I have to admit although it has some improvement on speed (which is under debate as some claims it's actually high throughput rather than low latency), it also has some problems that are really painful to solve. One small example is this issue which may or may not be my config problem.
I just tried kitty as an alternative. This issue is gone, and kitty also has some more subtle design as far as I can tell, e.g. their terminfo is called xterm-kitty, which avoided some problems because its prefix is xterm and hence recognizable by many shell tools. Alacritty's terminfo is named alacritty, so I had to deal with those problems when I ssh into other machine.
@jeffreytse I think this should be an Alacritty issue, should I close it?

Hi @g6ai
Could you try echo $TERM and tell me what it is? And @GiancarloAparicio thanks for your useful information, too. : )
Thanks and regards

@jeffreytse
echo $TERM
screen-256color

I just installed alacritty and its version is as below:

Hi @GiancarloAparicio
You said that you remember some things did not show well with zsh-vi-mode, could you tell me some details? : )
Thanks and regards

@jeffreytse My $TERM is alacritty.
@GiancarloAparicio I see you set the TERM to xterm-256color in your Alacritty config. Well I can also use zsh-vi-mode without a problem using xterm-256color terminfo. However, it is recommended to use alacritty terminfo in their instructions because otherwise you may lose some display feature.

Hi @g6ai
Thanks for the reporting and this issue has been addressed and settled down. Please update your plugin to the latest version.
Thanks and regards

@jeffreytse Sir you are most brilliant! Thanks for the fix!

@g6ai You are welcome, It's my honor to be able to help you! If you like my works, very welcome to be my prior sponsor, it will keep these open-source works sustainable and take one step towards make my new ideas come true. 😝


Share your feedback: What do you like, dislike, and wish to see in Boilerthing?

Hey everyone,
I appreciate your interest and contributions to Boilerthing! To help improving and tailoring this project to better meet your needs, I’d love to hear your feedback.
Please share:
What you like: Features, design patterns, or any aspect of the current version that you find useful or enjoyable.
What you dislike: Areas of the project that you think need improvement or cause you frustration.
Feature requests: Any new features or enhancements you’d like to see in future versions.
Your input is invaluable in helping making this project better for everyone. Thank you for your support and contributions!
Looking forward to your feedback!
Best regards,
Egor

The only thing I'm missing is an integration with Stripe or similar for payments and subscriptions. Other than that, it looks really good. Congrats!


typo: eceive -> receive

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/reference/biztalk-2016-fp1-rest-administration.json
:white_check_mark:Succeeded

his/core/initial-conversation-characteristics1.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Develop

Many issues with this PR and no explanation. I'm going to go ahead and close this. If you would like to reopen please add some justification for the PR>


Gracefully handle EC divering from F3

We will end up proposing base which will trigger backoff, giving us
chance to re-boostrap,

For some reason tests fail with what looks like OOM.


Run gslint on all go files of same package (solves issue #10)

This modification to the gslint behaviour runs the gslint command on all files of the same package in the directory of the file in the current view.
It only draws the boxes around found problems in the current file. Problems in other files are currently ignored.
When the sublime-project API arrives this code should probably be rewritten to use it.

i'll try and look at pulling this tomorrow

i don't think this works because we can't pass the current file's filename as we're checking the unsaved buffer. Gotype does't support passing anything on stdin as an extra file, our only option is probably to just write a temp file with the live source and call the command with a list of all the go file with our temp file in place of the real file(to avoid 'x redclared' errors). the only downside i can see without testing is the additional disk activity, but i don't forsee it being a problem(fingers crossed)


Ripper and Unit test for Tubex6.com.  Closes digitalnoise/ripme#1

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[ ] a bug fix (Fix #...)
[x] a new Ripper
[ ] a refactoring
[ ] a style change/fix
[ ] a new feature

Description
New ripper and unit test for Tubex6.com.  Builds and tests clean locally.
Testing
Required verification:

[x] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[x] I've verified that this change works as intended.

[x] Downloads all relevant content.
[x] Downloads content from multiple pages (as necessary or appropriate).
[x] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[x] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[x] I've added a unit test to cover my change.

Coverage increased (+0.1%) to 41.331% when pulling 3f5920b780b4cdd20890f8a35748f67ad222db57 on digitalnoise:master into e24d8f6853073e56ea9c305dd740032290573926 on RipMeApp:master.

Wow, that's a first for me.  @cyian-1756 - you were right about switching to AbstractSingleFileRipper - much cleaner and no CI issues (so far).


fix(ci): Docker master builds fail while checking version

SUMMARY
In https://github.com/apache/superset/pull/27055, I broke the master
builds while making the run_cmd method raise if it gets a non-zero exit
status. Turned out to only fail while in the pull_request context.
This is the change: https://github.com/apache/superset/pull/27055/files#diff-3cf86f687684a2c690521532de75a831def641338f5a9ec1da8add94714def4cR44-R45
This is the observed error in master build
Traceback (most recent call last):
 {...REDACTED...}
  File "/home/runner/work/superset/superset/./scripts/build_docker.py", line 76, in is_latest_release
    output = run_cmd(f"./scripts/tag_latest_release.sh {release} --dry-run") or ""
  File "/home/runner/work/superset/superset/./scripts/build_docker.py", line 45, in run_cmd
    raise subprocess.CalledProcessError(process.returncode, command, output)
subprocess.CalledProcessError: Command './scripts/tag_latest_release.sh master --dry-run' returned non-zero exit status 1.
Error: Process completed with exit code 1.

This disregards the exit code the tag_latest_release.sh since it seems
to be return error codes in expected situations.

@dpgaspar I'll merge this buts let's look at OWNERs for all the docker-related stufff


Ignore Package.resolved

This PR removes and ignores Package.resolved from the repository. Package.resolved is automatically generated, and adds noise to the Git history. Additionally, with the file tracked, carton's dependencies have to be updated manually every time before it's built, and when/after Package.swift changes. With the file removed, Package.swift can serve as a single source of truth for all SwiftPM-managed dependencies.
package-lock.json probably should be removed and ignored as well, but I'm not entirely sure.

Thanks for the PR! I'd rather keep Package.resolved, as it guarantees that people installing it via Homebrew or on Linux from sources get the exact same list of dependencies that the developers of carton use to test things on their machines. Same for package-lock.json. Hypothetically, if any of our dependencies accidentally publish something breaking (which is especially possible as some of them are on 0.x versions, which aren't guaranteed to stricitly conform to semver), it won't unexpectedly break things for our users.
We then can discover breakages on our side by updating Package.resolved, submitting it as a PR, and re-testing it on CI, which is basically what our update-deps.yml workflow does automatically every week when any updates are available. And we also make sure that our CI uses the same dependencies too in every other PR.
It may add some noise to commit logs, but not very significant, especially as our dependencies don't have that many updates. At least safety from unexpected breakages outweighs the noise in commit logs I think.
@swiftwasm/carton-team WDYT?

it guarantees that people installing it via Homebrew or on Linux from sources get the exact same list of dependencies that the developers of carton use to test things on their machines. Same for package-lock.json.

This is a good point. I didn't think of this before.
I wonder if there is a way to have GitHub generate Package.resolved without having Git track it?  This way users who build from source can still get the exact same dependencies for each carton release, while pulling/cloning from GitHub won't get the Package.resolved. Maybe it's not worth it, and I'm thinking too much into it.

Closing this PR because it doesn't seem like the right direction.


Populate need a test for schema:function(){}

A reminder for eddyystop.

The new schema validity check needs to allow a function.
The above passed tests likely because a missing test for schema:function(){}

https://github.com/feathersjs/feathers-hooks-common/pull/119


Add bug report and feature request GitHub issue templates

This PR suggests template formats for bug reports and feature requests, inspired somewhat by the Kafka issue structure: https://cwiki.apache.org/confluence/display/KAFKA/Reporting+Issues+in+Apache+Kafka

I added a feature request template as well

I'll merge this without TC passing - it seems broken and will need to look into that separately. The things it's complaining about are not relevant to this PR, which doesn't change code.


phase of an assignment when poll is created?

Should a newly created assignment poll change the assignment's phase to '1 (voting phase)'? If so, it would be best to do this server side.
(From #4537)

I checked, apparently, it still works (as soon as a poll is created, phase jumps to '1')


support user-provided annotations

This PR:

allows extra annotations to be added to the controller deployment via the values file.

tested - works fine. annotations are added if provided and ignored if the array is left empty.


Set git defines for firmware version

When running SIL GIT_VERSION_HASH and GIT_VERSION_STRING were not set. Now the firmware version shows up in output of rosflight_io.
PS, do you see anything wrong with updating the rosflight_firmware/firmware submodule to master? Or at least 1.2.0?

Just saw #90.

I'm going to merge this and rebase #90 on top

waiting for CI, but then this is good to go.


Cache: Add immutable input to allow writing to cache

I've been needing this for a long time, really since the Cache task was still in beta. I've been looking through the issues and the docs, and I've concluded that this kind of functionality really needs to be here, in a dedicated form.
The docs compare and contrast Artifacts with Caching, saying Artifacts are for necessary outputs from one stage/pipeline to another, and Caching is for dependencies which might be acquirable elsewhere. It seems to me there is a third type, and that is actual file caching of compiled output.
In looking around, I saw this comment which mentions a "rolling" cache idea, but the poster seems to be out-thinking themselves with regards to the keys. Most build systems (e.g. make, msbuild, etc) already check for outdated output and do incremental recompiling. I see no need for any kind of commit sha checking. Simply allow users to save the data, and let the build systems handl the rest.
I also saw an aside about security concerns. I can't really imagine how or why that's an issue, but at least by adding an input that is defaulted to read-only, there shouldn't be any worries about issues popping up for various pipelines.
Let me do my best to emphasize that this is desperately needed. Build times are absurd without caching. I wish msbuild had a more robust solution than what it has now, but we can't even use that without a mutable cache. The fallback key system is too clumsy, and it can lead to odd behavior (if we write to a specific key, and read from a general key, then we have to import all previous caches. If those caches have the same files, which files wind up being used?).
Please give this PR some consideration, I would really appreciate it.
p.s. I was unable to build either side of this, so it isn't tested. If it is wildly wrong, I will gladly work to get it right.
Cross PR: https://github.com/microsoft/azure-pipelines-tasks/pull/13459

The agent guidelines don't mention anything, but the tasks contributing guidelines say to tag whoever has commits on the files, so here goes: @fadnavistanmay
(I'm sorry if I'm not supposed to ping, hope it's not a bother 😄)

@JohnHolmesII Unless I am missing something, the task already has the functionality that you need with restoreKeys:
inputs:
    key: 'NumberOfTimesIHadToResetTheCache=0 | KeepRolling | $(Build.SourceVersion)'
    restoreKeys: |
       NumberOfTimesIHadToResetTheCache=0 | KeepRolling

When there is not exact match for the key, the cache will restore the most recent entry from NumberOfTimesIHadToResetTheCache=0 | KeepRolling | *

microsoft/azure-pipelines-tasks#13459

This is not the same as having a mutable cache. With the current implementation, when there's a hit, the cache won't get updated.
A use case for a mutable cache is a build system caching its results, ie. I'm using nx with its output cache. Whenever I run a command (lint or build), nx stores the result in its cache. The cache will fill itself up with pipeline runs as various parts of the code get modified, making each subsequent run faster until it's fully built up. When specific files are changed, the cache would get cleared.
I'm not sure about the implementation, but the motivation and described features would fit us perfectly.


Complete Docs Punch-Out List

[x] Fully collapse navigation when site loads
[ ] Fix navigation jumping around around when you click links
[x] Add index pages so we do not have duplicates and overviews
[x] Verify dark mode is default (and update the Moloch v3 docs too)

Revisited this again -- Nextra v2 isn't on a stable release and I upgraded to test it. There are a good bit of breaking changes -- we can wait until the minor version bump (which'll resolve this issue).
We can keep this open until then or close out and likely capture this in a larger Nextra v2 refactor ticket @earth2travis

Yeah. Let's do that since upgrading to a v2 beta broke a lot and is unstable. I'm hoping that they do a minor version bump that includes this fix

We can close this out since we merged in Plor's PR https://github.com/HausDAO/sdk-docs/pull/47


Configure Alloy to be used as a self-service too for logs (source files)

Towards: https://github.com/giantswarm/roadmap/issues/3518

Still needs to implement the tenant name override from label, like its done here https://github.com/giantswarm/logging-operator/pull/233/files#diff-405f451506c2146b4cf915863a848d9a42f39a3b292a9b6f9ada78b4eac32598R85

Not following this route as it would not allow to override the tenant when using labels on namespaces, due to the namespaces labels not being available when using discovery.kubernetes.
Trying to discover those labels using a sidecar container also does not work, the idea was to fetch the namespace label and produce a list of namespace_A:tenant_name_A;namespace_B:tenant_name_B; and then extract the tenant name using the following relabel rule
rule {
        source_labels = concat(["__meta_kubernetes_namespace"], split(local.file.namespaces_tenant.content, ";"))
       regex         = "(.+);.*(\1):([0-9]+);.*"

        target_label  = "tenant_namespace"
}

Unfortunately there is no support for backreference (\1) in Alloy/Prometheus regex RE2 engine


registerForNotify BLEUUID("0x2902") ERROR: UUID value not 2, 4, 16 or 36 bytes

I am using the example of the BLE_client collecting data from a BLE server, which supports only "notify" characteristic, but it crashes in registerForNotify().
I am using the latest code in esp32-snippets, and I have found the wrong point as follow.
BLERemoteCharacteristic.cpp
Line 504: BLERemoteDescriptor *desc = getDescriptor(BLEUUID("0x2902"));
length("0x2902") is always 6, which leads to the error "UUID value not 2, 4, 16 or 36 bytes".
Here is the log:

Found our characteristic
[D][BLERemoteCharacteristic.cpp:484] registerForNotify(): >> registerForNotify(): Characteristic: uuid: 49535343-1e4d-4bd9-ba61-23c647249616, handle: 42 0x2a, props: broadcast: 0, read: 0, write_nr: 0, write: 0, notify: 1, indicate: 0, auth: 0
[E][BLEUUID.cpp:115] BLEUUID(): ERROR: UUID value not 2, 4, 16 or 36 bytes
[D][BLEDevice.cpp:143] gattClientEventHandler(): gattClientEventHandler [esp_gatt_if: 4] ... ESP_GATTC_REG_FOR_NOTIFY_EVT
[D][BLERemoteCharacteristic.cpp:364] getDescriptor(): >> getDescriptor: uuid:
[D][BLEUtils.cpp:1377] dumpGattClientEvent(): GATT Event: ESP_GATTC_REG_FOR_NOTIFY_EVT
[D][BLERemoteCharacteristic.cpp:372] getDescriptor(): << getDescriptor: Not found
[Guru Meditation Error: Core  1 panic'ed (LoadProhibited)
. Exception was unhandled.

Hi, i will check it but for now you can change it to:
BLERemoteDescriptor *desc = getDescriptor(BLEUUID((uint16_t)0x2902));

Thanks! Now it can work most of the time, but yet there is a problem.
As I have five BLE servers to read data from by turns, I try to connect and disconnect for many times, but it stuck after a few minutes.
The log:
E (106920) BT_GATT: application already registered.
E (106920) BT_APPL: Register with GATT stack failed.
E (106981) BT_APPL: bta_gattc_process_api_open Failed, unknown client_if: 0
It seems that the program is stuck in:
BLEClient.cpp
Line 99: esp_err_t errRc = ::esp_ble_gattc_app_register(0);

Should the cast fix from chegewara be implementet in the codebase?

Could you try BLEUUID("2902")?

Its taken literally, each digit is converted to ascii, which is wrong.
What do you mean check for callbacks? No, the isn't any loop.

My BLE device can both serve READ and NOTIFY on the same characteristic. So its a bit confusing.
I mean, after i do the registerForNotify(), how to i display the value (content) coming from the notification packet?
pRemoteCharacteristic->readValue(); is for direct READ, do i use the same function for NOTIFY?
(Sorry, this is probably hijacking og the thread)
But back to the topic. Do you have any conserns about your uint16_t type cast fix?

You can have registerForNotify() for each remote characteristic that is serving notify or indicate, and you can in addition setCallbacks() for each characteristic that can be read/write. You can also find examples about it.
https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/tests/BLETests/SampleRead.cpp#L25-L46

Fixed in here:
https://github.com/chegewara/esp32-snippets-enchancements-test/blob/multi_connect_test/components/cpp_utils/BLEUUID.cpp#L71-L126


Fenrir - Natural Weapons (wolf) reduced damage even though no damage was dealt

Fenrir was in wolf form with Natural Weapons and The Pale Moon Pendant in play. Osiris made Fenrir deal 1 psychic damage to himself, which was reduced to 0 by the Pendant, but it still applied the damage reduction effect to Fenrir. The same thing happened with the damage caused by Jump Scare.

Just a simple check to add in, silly me

Just a simple check to add in, silly me


cargo generate-lockfile doesn't give a working lockfile in some situations

Problem
For some crates running generate-lockfile does not result in a working lockfile, whereas running fetch does.
Steps
$ cargo download -x alcro==0.1.4
INFO: cargo-download v0.1.2
INFO: Crate `alcro==0.1.4` downloaded successfully
INFO: Crate content extracted to ./alcro-0.1.4/
$ cd alcro-0.1.4/
$ cp Cargo.lock Cargo.lock.orig
$ cargo fetch --locked
error: the lock file /tmp/tmp.Uh4w4Ih9yF/alcro-0.1.4/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, use the --offline flag.
$ cargo generate-lockfile
    Updating crates.io index
       Fetch [                                                       ]   0.00%
$ diff Cargo.lock Cargo.lock.orig
244c244
<  "proc-macro2 1.0.18",
---
>  "proc-macro2 1.0.17",
# [...] other just version changes
$  cargo fetch --locked
error: the lock file /tmp/tmp.Uh4w4Ih9yF/alcro-0.1.4/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, use the --offline flag.
$ cargo fetch
$ diff Cargo.lock Cargo.lock.orig
10c10
<  "futures",
---
>  "futures 0.1.29",
# [...] lots more structural changes
$ cargo fetch --locked
# works

Thanks for the report!
It doesn't matter which command is run.  Building a lock file with any command, and then running any command with --locked will fail.
This seems similar to #7753.  alcro specifies two different cfg dependencies on futures:
[target."cfg(unix)".dev-dependencies.futures]
version = "^0"
[target."cfg(windows)".dev-dependencies.futures]
version = "^0.1"

I think that is a use case that Cargo never really considers, and it doesn't seem to work properly.  As mentioned in https://github.com/rust-lang/cargo/issues/7753#issuecomment-569763022, it would be very difficult to determine that these two expressions are mutually exclusive.  I would lean towards forbidding that as a duplicate dependency for now.  @Eh2406 wdyt?

Note that the final cargo fetch --locked worked after having run cargo fetch, that did a much bigger rewrite of the Cargo.lock whereas the cargo generate-lockfile call only appeared to update the version numbers.

I believe that it is currently treated as being mutually true. I get a lockfile that just has version = "0.1.29", that satisfies both requirements. That being said I was unable to reproduce the error.

I originally noticed this on the latest nightly since that's what docs.rs uses, the repro I posted above was when using cargo 1.45.0-nightly (cb06cb269 2020-05-08) locally.

@Eh2406 it is probably because you are on windows (and the cfg(windows) has a different selection).  Here is an isolated test that should trigger on all platforms:
#[cargo_test]
fn mixed_targets_same_dependency() {
    Package::new("bar", "0.1.0").publish();
    Package::new("bar", "0.2.0").publish();
    Package::new("zoo", "1.0.0")
        .dep("bar", "0.1")
        .publish();

    let p = project()
        .file("Cargo.toml",
            r#"
                [package]
                name = "foo"
                version = "0.1.0"

                [dependencies]
                zoo = "1.0"
                bar = "^0"

                [target.'cfg(does_not_exist)'.dependencies]
                bar = "^0.1"
            "#)
        .file("src/lib.rs", "")
        .build();

    p.cargo("generate-lockfile").run();
    p.cargo("check --locked").run();
}

I haven't checked, but I suspect this is relatively common, so rejecting it outright might not be the right thing.

I'm a bit surprised by this behavior, I thought we fixed this some time ago! I don't think we necessarily want a special case to reject this in the manifest, it seems like it would be pretty difficult to detect overlapping ranges. The resolver, however, should be trying to solve both version constraints and realize there's one solution. Currently it seems like it's picking the first for generate-lockfile and the second for a target-specific resolution, which is not great.

I took a little look at this.  It seems to be unique to this situation where one version req is a superset of another. If you change ^0 to ^0.2, then it works fine.
What happens is that when it is locking the summary, both bar deps get locked to =0.1.0.  This happens here, where it is iterating over the locked entries.  It picks the first entry it finds that matches, and for ^0 it matches 0.1.0 because it appears in the list before 0.2.0.
I don't know how to fix that.  Perhaps it should pick the dep with the greatest matching version?  Iterate in reverse order?

Hm this seems like it's even more evidence that the current implementation of locking is not really up to par. We should know that if a crate has two versions in a lock file exactly which one you should be locked to for each dep.
This sounds like we're basically not keeping track of that information, only what's available to lock. I don't think iteration order can solve this, because you should be able to construct situations where there's as many versions in play as you need, and the lock should always be able to pick the one the lock file indicates.
In any case this seems like a more fundamental issue in how lock files are handled. This doesn't really ever come up much in practice because 99% of version requirements are "semver compatible" which means there's no overlap across major versions.


Powershell

Hello,
How to assign phone number by Powershell ?
[Tapez vos commentaires ici]

Détails du document
⚠ Ne pas modifier cette section. C’est obligatoire pour docs.microsoft.com ➟ Liaison des problèmes GitHub.

ID: 69c67496-cace-f833-7cfc-dca7722fef3e
Version Independent ID: 5a14f81c-529c-4971-5ce8-39633834d4d3
Content: Affectation, modification ou suppression du numéro de téléphone d’un utilisateur
Content Source: Teams/assign-change-or-remove-a-phone-number-for-a-user.md
Service: skype-for-business-online
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@CallMeByMyName thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.
@officedocsbot close

@officedocsbot close

How to do this is the new team admin centre? We cant do it in the legacy portal now

Hey everyone. So, you are just looking for the cmdlet? If so, here it is  https://docs.microsoft.com/en-us/powershell/module/skype/set-csonlinevoiceuser?view=skype-ps
@rramdoyal - I'm checking with my PMs to see when TNM: Assigning phone numbers is going live. Please hold.

@rramdoyal - Can you explain why you can't find it in the legacy portal? Can you please be specific about your click path please?

For me it concern ressource account
From the legacy portal it says that we should  do it on the new team admin centre
But on the new team portal when we try to add the phone number to says it's not available  but have been able to assign the phone number using powershell.
Set-csonlinevoiceapplicationinstance

@officedocsbot assign @scanum

@rramdoyal are you trying to assign a phone number to an Auto Attendant or Call queue?

Auto attendant

@rramdoyal - ok. The intital requested started out with editing a different doc (Assigning numbers topic) above. So, for auto attendants, here is the topic you need to assign phone numbers to auto attendants using Resource Accounts. We released a call routing update for AAs and CQs that now use Resource Accounts and will no long support phone numbers directly. See if this articled helps. It has the steps for using PS:  https://docs.microsoft.com/en-us/microsoftteams/manage-resource-accounts


Create Account method call fails with NotEnoughBalance error, even though there is enough

Describe the bug While trying to create a new account using the API of:
await fundingAccount.functionCall({
  contractId: "near",
  methodName: "create_account",
  args: { new_account_id: newAccountId, new_public_key: publicKey, },
  gas: new BN("300000000000000"),
  attachedDeposit: new BN(toNear("0.19")),
});

In this situation the fundingAccount has exactly 0.3 NEAR inside of it- and as you can see we are trying to create and fund a new wallet with 0.19 NEAR (which still leaves more than 0.1 NEAR in the funding account).
We are getting the following error:
 Sender c747a14dc953fda7b3b795164676d85599805ae1bf8cdd6ada53275ff84de062 does not have enough balance 0.3 for operation costing 0.379272583759051470676888

The error object looks like this:
   {
        "type": "NotEnoughBalance",
        "context": {
            "transactionHash": "BYpkwyVjRj27UJvnnaVGwEkXewot1s8JsGY72pV5cDAz"
        },
        "balance": "300000000000000000000000",
        "cost": "379272583759051470676888",
        "signer_id": "c747a14dc953fda7b3b795164676d85599805ae1bf8cdd6ada53275ff84de062",
        "kind": {
            "balance": "300000000000000000000000",
            "cost": "379272583759051470676888",
            "signer_id": "c747a14dc953fda7b3b795164676d85599805ae1bf8cdd6ada53275ff84de062"
        }
    }

To Reproduce Steps to reproduce the behavior:

Create an implicit account
Transfer 0.3 NEAR to that account
Try and use that account to create a new account with only 0.19 NEAR as the initial deposit
Notice that it fails because the operation now says it needs the funding account to have 0.379272583759051470676888 NEAR

Expected behavior Account is created just fine, because we are leaving 0.1 NEAR in the old account and we are adding the gas for the transaction to succeed, and the initial deposit of only 0.19 NEAR.
Additional Testing
I did bring the deposit amount down to exactly 0.1 NEAR (which means that this unexpected "required amount" should be met) and once the transaction was complete, there was exactly 0.1 NEAR in the new account, and 0.1988161 NEAR in the funding account- hence the total "cost" of the operation from the old account (including the deposit) was (0.3 - 0.1988161) = 0.1011839 NEAR. Hence, it is very strange that the first attempt of using 0.19 NEAR to fund the new wallet failed- as that should have cost around (0.19 + 0.0011839) ~ 0.1911839 NEAR, and the wallet had 0.3 NEAR.

btw seems like your bot here exalate-issue-sync is editing issues and messing with the layout of code and things.

This is because pessimistic gas accounting. Sender c747a14dc953fda7b3b795164676d85599805ae1bf8cdd6ada53275ff84de062 does not have enough balance 0.3 for operation costing 0.379272583759051470676888 You need  0.379272583759051470676888 to complete this tx.

This is because pessimistic gas accounting.

Could you please explain the numbers behind this if possible? How could we calculate this on our side? We need to be able to give users exact feedback if certain actions are possible or not.
If you look at my calculations- it seems like the "pessimism" is going above and beyond, as I've already accounted for breathing room. It appears that the expected extra "gas" is around 0.1 NEAR, which seems very high considering gas pricing.

 So sorry if its not very clear, I did spend a lot of time formatting but seems it was in vein (it keeps re-messing it up if I edit it).

@MaximusHaximus @BenKurrek Do you have an explanation on gas accounting from our docs?


Tree and list onMiddleMouseClick

fixes #58442
This PR exposes onMouseMiddleClick events on the tree and list.
It also adopts this in the explroer and open editors view such that the behavior there is no longer broken.
Please note that there is still one wrong usage in quick open here
However I was not sure how was that even working before so for now I made no changes there.
fyi @joaomoreno

Sooooo, it's now not possible to middle click in quick open to open file in background?

@usernamehw that was broken before the PR. This PR simply did not fix it. I can look into adding that also

@usernamehw oh Ben already fixed it via 48eaee42b799805b1eb4dd3f01950fa34ea94893


Show only Day name

Hi
I want to show only the day's name , can I do it ?
Like this picture.

This falls outside the scope of intended use. You could possibly override CSS variables used in paper-date-picker.html and use display:none to hide the parts you don't want.

Thank you.


feat(ci): create GitHub release workflow

Creates GitHub release workflow and build-cross dist Makefile target
Signed-off-by: Johnson Shi<EMAIL_ADDRESS>

Builds binaries in top-level ./_dist directory.
~/dev/osm-health$ ls _dist/**
_dist/darwin-amd64:
osm-health

_dist/linux-amd64:
osm-health

_dist/windows-amd64:
osm-health.exe

Linux testing:
~/dev/osm-health$ ./_dist/linux-amd64/osm-health
10:30AM INF osm-health version: dev; 9ac94e4a93ab1e3d59710c3f46fd0b6adf8f0898; 2022-01-03 file=main.go:65 module=main
The osm-health cli enables you to
        (1) check osm health status
        (2) debug osm issues

Usage:
  osm-health [command]

Available Commands:
  connectivity  Checks connectivity between Kubernetes resources
  control-plane Checks the osm control plane
  help          Help about any command
  ingress       Checks ingress to Kubernetes resources

Flags:
  -h, --help                   help for osm-health
      --osm-namespace string   namespace for osm control plane (default "osm-system")

Additional help topics:
  osm-health validate      Validates YAML files including SMI policies

Use "osm-health [command] --help" for more information about a command.

Windows testing:
PS > .\_dist\windows-amd64\osm-health.exe
10:31AM INF osm-health version: dev; 9ac94e4a93ab1e3d59710c3f46fd0b6adf8f0898; 2022-01-03 file=main.go:65 module=main
The osm-health cli enables you to
        (1) check osm health status
        (2) debug osm issues

Usage:
  osm-health [command]

Available Commands:
  connectivity  Checks connectivity between Kubernetes resources
  control-plane Checks the osm control plane
  help          Help about any command
  ingress       Checks ingress to Kubernetes resources

Flags:
  -h, --help                   help for osm-health
      --osm-namespace string   namespace for osm control plane (default "osm-system")

Additional help topics:
  osm-health validate      Validates YAML files including SMI policies

Use "osm-health [command] --help" for more information about a command.

Codecov Report

Merging #121 (29475e3) into main (b4f79df) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #121   +/-   ##
=======================================
  Coverage   42.51%   42.51%
=======================================
  Files          29       29
  Lines        1249     1249
=======================================
  Hits          531      531
  Misses        718      718

Flag
Coverage Δ

unittests
42.51% <100.00%> (ø)

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

Impacted Files
Coverage Δ

pkg/envoy/parse.go
57.14% <ø> (ø)

pkg/kubernetes/podhelper/endpoints.go
75.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Failing to change the stage mid song

Describe your problem here.
Hello, I've recently made a fanmade for the mod Funkin Aside and I wanted to chart it in the mod. During the song, after the big drop, I wanted to change the stage using this code:

And for some reason, after the character changes, it doesn't change the stage. I checked if I typed everything correctly and I really don't see where the issue is...
EDIT: I changed the script because I realized that none of the stages were in LUA files but it still doesn't work:

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

None of those functions exist and there isn't a native one to change stage
See #3137


Does not work. Jobs do not start automatically

Hello
I use
Rails 6.1.4
Redis 6.2.6
Sidekiq v6.4.1
Sidekiq-cron 1.3.0
Tasks are launched without problems from Web UI. But they don't start automatically. There are no errors in the logs.
I create job :
Sidekiq::Cron::Job.create(name: 'Send report', cron: '*/5 * * * *', class: 'VihoCms::Reports::SummaryReportJob', args: [ENV['REPORT_EMAIL'], 12])
and like this
array = [
      {
        'name'  => 'Send report'',
        'class' => 'VihoCms::Reports::SummaryDonationsReportJob',
        'cron'  => '0/5 * * * *',
        'args'  => [[ENV['REPORT_EMAIL'], 12]
      }
]
Sidekiq::Cron::Job.load_from_array! array

But it doesn't affect. Sidekiq process works correctly. And I will repeat the tasks are launched and work correctly when they are started from Web UI.

How often are you running this set of commands?
I see you're using the bang (!) method, and from the docs:

Bang-suffixed methods will remove jobs that are not present in the given hash/array, update jobs that have the same names, and create new ones when the names are previously unknown.

How often are you running this set of commands?
I see you're using the bang (!) method, and from the docs:

Bang-suffixed methods will remove jobs that are not present in the given hash/array, update jobs that have the same names, and create new ones when the names are previously unknown.

No i run this command only one time. I know  I know that restarting deletes jobs with the same name. On web UI admin I see jobs, and I can run this jobs manually, but they don't start automatically

No i run this command only one time. I know I know that restarting deletes jobs with the same name. On web UI admin I see jobs, and I can run this jobs manually, but they don't start automatically

What's your use case exactly? I usually load the jobs from a YML file and seems to work fine for me.

I checked two variants
Sidekiq::Cron::Job.create(name: 'Send report', cron: '*/5 * * * *', class: 'VihoCms::Reports::SummaryReportJob', args: [ENV['REPORT_EMAIL'], 12])
and like this
array = [
      {
        'name'  => 'Send report'',
        'class' => 'VihoCms::Reports::SummaryDonationsReportJob',
        'cron'  => '0/5 * * * *',
        'args'  => [[ENV['REPORT_EMAIL'], 12]
      }
]
Sidekiq::Cron::Job.load_from_array! array

Both variants are create jobs, I see jobs on Web UI. I can run jobs manually, but automatically they don't run.

Faced the same problem
cron = '0/5 * * * *'
Fugit.do_parse_cron(cron)
@cron_s=nil,
@hours=nil,
@minutes=[0],
@monthdays=nil,
@months=nil,
@original="0/5 * * * *",
@seconds=[0],
Fugit::Nat.parse('every 5 minutes').to_cron_s
=> "0,5,10,15,20,25,30,35,40,45,50,55 * * * *"
cron = "0,5,10,15,20,25,30,35,40,45,50,55 * * * *"
Fugit.do_parse_cron(cron)
@cron_s=nil,
@hours=nil,
@minutes=[0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55],
@monthdays=nil,
@months=nil,
@original="0,5,10,15,20,25,30,35,40,45,50,55 * * * *",
@seconds=[0],
use Fugit::Nat.parse().to_cron_s to get a valid cron

@galievruslan We are having the same issues here, have you found a fix yet since April? We found that being explicit (i.e. status: enabled) solves the issue

To start running jobs, don't forget to start the Sidekiq workers: https://github.com/ondrejbartas/sidekiq-cron#how-to-start-scheduling.

Hello 👋🏼 going to close this one, as no new info or some reproducible scenario was provided...
Since v1.6 we support autoloading the config/schedule.yml and it just works 👌🏼. To start scheduling jobs, don't forget to start the Sidekiq workers.
On the other side, we have a bunch of related tests ensuring this functionality is working well:
https://github.com/ondrejbartas/sidekiq-cron/blob/7acecdea4ef8b17b27ae635fc8698704aa1a0773/test/unit/job_test.rb#L1155
So we can't do more without a failing test/scenario. Thanks!


Issue with k8s.io/docs/concepts/services-networking/ingress/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
LInks are broken:  https://git.k8s.io/ingress/controllers/nginx#running-multiple-ingress-controllers
all git.k8s.io links on this page is broken.
Page to Update:
https://kubernetes.io/docs/concepts/services-networking/ingress/

@sahilsk Can you check again? All the git.k8s.io links are working fine, including https://git.k8s.io/ingress/controllers/nginx#running-multiple-ingress-controllers.

Good morning @sahilsk - I double checked the links and per @nikhita they all appear to be working correctly. Since they are functional, I'm going to close this PR for now, please re-open it if there is a specific documentation issue we can help resolve


Change default AlertDialog to custom app theme AlertDialog

Issue Fixes #73 🔐
Are you a part of GSSOC' 21 ❓

[x] Yes ✔
[ ] No ✖

Describe the changes you've made 🏆

Now theme of app looks consistent with all alertDialogBox looks identical.
Add alert_dialog_box.xml

Type of change 🖇

[x] Bug fixing (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: 📋

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if required) 📷
Add screenshots of the changes you have made.

Original
Updated

@krayong satisfied with the changes in alertDialog.
The code seems to be working fine.

Great work @codeDamon


Add benchmark for findRenderedReport

Description
Added benchamark for findRenderedReport in order to measure its performance.
Type of change

Benchmarks (no changes in the code)

Testing steps
Run benchmarks.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

you don't have to stop and start timer

Removed, I didn't understand their purpose in other benchmarks, I get it now.


Exposures can depend on metrics

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/docs/build/exposures
https://docs.getdbt.com/reference/exposure-properties
What part(s) of the page would you like to see updated?
exposures:
  - name: my_exposure
    depends_on:
      - ref('some_model')
      - ref('some_seed')
      - source('name', 'table')
      - metric('some_metric')

While we're here: Should an exposure ever depend on a source directly, without at least a staging model in between? Our recommendation should be: probably not! / likely never!
Still, it should be possible.
To quote @joellabes from Slack ~a month ago:

Agree that it is an antipattern, but also want to note that part of the docs' job is also to say what is possible so would advise against removing that source example.
Add a note in the docs to say "you can but you shouldn't" would be useful though!

Additional information
https://github.com/dbt-labs/dbt-core/pull/6342

resolved by #2657


Remove class viewer

try to remove the class viewer, see more details on https://github.com/cweijan/vscode-office/issues/15, https://github.com/redhat-developer/vscode-java/issues/1741#issuecomment-746128965.

Lower class viewer priority at version 1.8.9.


[Feature] support avro format

added avro format and UT
kafka support avro format and e2e test

Purpose of this pull request
close #4821
same pr with https://github.com/apache/seatunnel/pull/5064

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[x] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[x] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

pls re-trigger the CI, no failed job, only one cancelled job

Run mvn spotless:apply and fix code style error.

can we retrigger the CI as we has fix the code style error

run successful when disable on flink 1.15 https://github.com/liunaijie/seatunnel/actions/runs/5617980130

merge the conflict, pls re-trigger the CI

https://github.com/liunaijie/seatunnel/actions/runs/5676004114/job/15382134463
this pr run successful in my repo's CI. But get NPE in this CI.
And also can't repet the error in local.

@liunaijie Great commit! Now we just need to resolve the conflicts.

Once PRs #5303 and #5222 are merged, they will resolve the e2e testing issue.

please help review the pr @liugddx @ic4y @ruanwenjun
the CI run successed.
https://github.com/liunaijie/seatunnel/actions/runs/6322524273/job/17501939403

@liunaijie good pr, please fix the conflict

@hailin0  Done. PTAL, thanks.

Basically LGTM, wait ci pass

Basically LGTM, wait ci pass

@ruanwenjun  PTAL

hi I found some issues in kafka avro e2e testing. My configuration is as follows
source {
  Kafka {
    bootstrap.servers = "kafkaCluster:9092"
    topic = "test_avro_topic"
    result_table_name = "kafka_table"
 // When configured this will pull the consumption from kafka's starting offset kafka.auto.offset.reset = "earliest" does not take effect
    **start_mode = "earliest"**
    format = avro
    format_error_handle_way = skip
    schema = {
      fields {
        id = bigint
        c_map = "map<string, smallint>"
        c_array = "array<tinyint>"
        c_string = string
        c_boolean = boolean
        c_tinyint = tinyint
        c_smallint = smallint
        c_int = int
        c_bigint = bigint
        c_float = float
        c_double = double
        c_decimal = "decimal(2, 1)"
        c_bytes = bytes
        c_date = date
        c_timestamp = timestamp
      }
    }
  }
}

sink {
  Console {
    source_table_name = "kafka_table"
  }
  Assert {
    source_table_name = "kafka_table"
    rules =
      {
        field_rules = [
          {
            field_name = id
            field_type = long
            field_value = [
              {
                rule_type = NOT_NULL
              },
              {
                rule_type = MIN
                rule_value = 0
              },
              {
                rule_type = MAX
                rule_value = 99
              }
            ]
          }
        ]
      }
  }
}

@liunaijie


0.1.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/63392
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" cc577f2dd9e29ffd54f0539186fde842530a4b09
git push origin v0.1.2


Removed un-wanted code, we will add when required

@narkarum , lets remove un-wanted code as of now, we will add when required. this will be easy to review and make our framework good

Removed the unused and kept the remaining.

iam code is needed
vpc/test/ is the test code for server.


Additional actions

          2 Errors

:no_entry_sign:
ScreenCallAction.swift#L19 - Sources/Addons/URL/Call/ScreenCallAction.swift#L19: variable used within its own initial value
        let phoneNumber = phoneNumber

:no_entry_sign:
ScreenPopoverPresentationAnchor.swift#L26 - Sources/Screen/Decorators/Modal/Popover/ScreenPopoverPresentationAnchor.swift#L26: variable used within its own initial value
    public static let center = center(permittedArrowDirections: nil)

  Generated by :no_entry_sign: Danger

          2 Errors

:no_entry_sign:
ScreenCallAction.swift#L19 - Sources/Addons/URL/Call/ScreenCallAction.swift#L19: variable used within its own initial value
        let phoneNumber = phoneNumber

:no_entry_sign:
ScreenPopoverPresentationAnchor.swift#L26 - Sources/Screen/Decorators/Modal/Popover/ScreenPopoverPresentationAnchor.swift#L26: variable used within its own initial value
    public static let center = center(permittedArrowDirections: nil)

  Generated by :no_entry_sign: Danger

          2 Messages

:book:
iOS: Executed 1 test, with 0 failures (0 unexpected) in 0.006 (0.013) seconds

:book:
tvOS: Executed 1 test, with 0 failures (0 unexpected) in 0.010 (0.018) seconds

  Generated by :no_entry_sign: Danger

          2 Messages

:book:
iOS: Executed 1 test, with 0 failures (0 unexpected) in 0.005 (0.006) seconds

:book:
tvOS: Executed 1 test, with 0 failures (0 unexpected) in 0.008 (0.017) seconds

  Generated by :no_entry_sign: Danger


Crash on startup when running as a service on Windows

Hello,
After upgrading go-re2 in crowdsec to the latest version, we saw a crash when running as a service in Windows (and only as a service, everything was fine when running the binary directly from the command line).
After some investigation, it turns out the issue was introduced in this commit, more specifically this line.
When windows starts a service, it looks like stdout and stderr are forcefully closed by the system, which makes them unusable (I cannot find any actual documentation about this, but according to my tests, they are).
os.Stdout and os.Stderr are passed to InstantiateModule, and because they are invalid, this call fails, which in turn makes go-re2 panic.
I have a minimal reproduction available in this gist (there's a bit of fluff to install/remove the service to make it easier to use).
To reproduce:

Build the code above
Install the service (from an admin shell): ./repro.exe install.
Attempt to start the service (from an admin shell): Service-Start testService
Observe the error returned by windows (if you have procmon running at the same time, you'll see the program exiting the status code 2, which is the code used by panic)
Remove the service (from an admin shell): ./repro.exe remove

Unfortunately, it's quite hard to get any logs about this error (because the panic occurs in init(), so it will crash before my program can run any code), but patching wazero with various debug logging shows:
time="2024-09-12T00:48:03+02:00" level=info msg="InitFSContext(stdin=<nil>, stdout=*os.File, stderr=*os.File, fs=[], guestPaths=[], tcpListeners=[])"
time="2024-09-12T00:48:03+02:00" level=error msg="stdioWriterFileEntry(stdout, *os.File) failed: GetFileType /dev/stdout: The handle is invalid."

Which confirms stdout is indeed invalid.
I was not able to reproduce the issue on linux by running things like ./repro 1>&-, but I guess it should be doable by setting FD_CLOEXEC on stdout before calling execve on a program that uses go-re2.
As a side note, have you ever thought about removing the use of init() (or at the very least, not calling panic in init() and somehow find a way to return the error to the user) ? I understand that it's needed for go-re2 to be a drop-in replacement for regexp, but it makes it very hard (and confusing) to debug issues like this (it took me some time to realize that go-re2 was calling panic()).

Hi @blotus - thanks for the report and sorry for the trouble, that's a gnarly issue. I think with regards to panic, we won't change the behavior since indeed being a drop-in replacement for regexp, presumably that was also important when introducing to crowdsec :) And module initialization is irrecoverable, making the whole go-re2 package unusable so it feels somewhat natural to me.
If there's some way to improve the panic message we could do that, I would figure the stack trace makes it relatively straightforward to find go-re2 is the cause though. Was there something specifically confusing about it that we could improve? Thanks

Thanks for the merge !
The hard part was getting the stacktrace (as stdout/stderr are closed, nothing can get outputted anywhere, and due to the way go resolves import order, go-re2 init was called before I could replace stderr with a valid handle or setup a recover call, and go-re2 was not my first suspect for the crash).
I've given some thoughts about this, and something that could probably be a good middle ground would be to replace the panic calls with something that sets an error flag inside go-re2, and check its value during the calls to Compile/MustCompile/.... or Match/MatchString and return an error/panic here.
This would technically change the behaviour compared to the standard regexp module, as this would be a new error type but it's probably acceptable (this is even something that could be hidden behind a build flag)
Admittedly, this is probably a niche issue (although I haven't spent the time trying to understand all the possible failure reasons during initialization), so maybe it's not actually worth spending the time of reworking this part, but if you are interested let me know, I'll open another issue to track this.

go-re2 init was called before I could replace stderr with a valid handle

Ah, thanks for this example, indeed I can see why it was tricky. I like your idea a lot of propagating the error to read in the entry point functions rather than panicing during init, feel free to open an issue on it, I think we can make that change.


Doc comment maintenance

Fixed doc comments issues:

Fixed mistyped param doc comments (/**< is OK, /** < is not).

Put special characters (e.g., pipe, backslash, etc.) in quotes, as they can
confuse doxygen and it will print lots of various warnings.

Added missing @{s, removed extra @}s.

Ensured same style for doc groups everywhere:

Where \addtogroup, @{, and @} doxygen commands are used, the order to be
followed is: license, #ifndef guards (in headers), includes, \addtogroup
and @{, main code content, @}, #endif guards (in headers).

Multiple \addtogroups or multiple @}s should be in the same doc comment.

First \addtogroup should be on the very first line of a doc comment, i.e.,
/** \addtogroup.

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss<EMAIL_ADDRESS>

There is a doc comment fix in my in-progress PR too. Could you add that small fix to this? It fits better here. https://github.com/Samsung/jerryscript/pull/985/files#diff-809091506ab5ef21bfcf6883f66a2ddbR748

@LaszloLango , Of course. Added, updated.

LGTM

Updated to current master. Moreover, I've added an extra patch on top of the originally proposed one that adds consistency to the quoting of special characters in re-bytecode.h . (If this also gets accepted, then it can be squashed. If not, it will be easier to drop.)

Still LGTM

LGTM


After few Hours stop Working

System Health details

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
After few Hours stop Working Lock i'm trying Unlock/Lock and nothing, only help me remove battery from Lock.
Sometimes after few minutes, or Lock State is not Sync with HA, Lock is Locked and i'm click UnLock (IRL Lock start Locking even when it is Locked and hear the engine sputter), where is the problem in Lock or Integration?, i think in integration from phone i don't have any issues.
Lock is front of ESP.
Reproduction steps

Debug logs
[02:22:02][I][bluetooth_proxy:282]: [0] [7A:7A:46:44:77:44] Connecting v3 without cache
[02:22:02][D][esp32_ble_tracker:215]: Pausing scan to make connection...
[02:22:02][I][esp32_ble_client:069]: [0] [7A:7A:46:44:77:44] 0x00 Attempting BLE connection
[02:22:03][D][esp-idf:000]: W (43157) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

[02:22:04][D][esp-idf:000]: W (44173) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

[02:22:07][D][esp-idf:000]: W (47207) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

[02:22:07][D][esp-idf:000]: W (47551) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x3e

[02:22:07][D][esp-idf:000]: W (47556) BT_APPL: gattc_conn_cb: if=4 st=0 id=4 rsn=0x3e

[02:22:07][D][esp-idf:000]: W (47558) BT_APPL: gattc_conn_cb: if=5 st=0 id=5 rsn=0x3e

[02:22:07][D][esp-idf:000]: W (47562) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

[02:22:07][W][esp32_ble_client:139]: [0] [] Connection failed, status=133

Diagnostics dump
No response

Possible duplicate of #9

Where are the debug logs for Yeelock from HA?
Per here, it looks like this is either a range or interference issue.

Where are the debug logs for Yeelock from HA?
Per here, it looks like this is either a range or interference issue.

Range is Very good
home-assistant_yeelock_2024-04-30T20-29-53.414Z.log


Xcode12.0  error

The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

public static func easeInQuint(_ t: Float, _ b: Float, _ c: Float, _ d: Float = 1.0) -> Float {
        return {
            var a = c * $0
            a = a * $0
            a = a * $0
            a = a * $0
            a = a * $0
            return a + b
//            return c * $0 * $0 * $0 * $0 * $0 + b
        }(t / d)
    }

Fixed in the latest commit.
Thank you, @jseanj


[svg] Configure eslint in svg

Current Behavior

Desired Behavior

Implementation

Acceptance Tests

Mockups

Contributor Guide

🎨 Wireframes and designs for Layer5 site in Figma (open invite)

Done here: https://github.com/layer5io/sistent/pull/82


Feat.wards zambia

@gulfaraz I don't see your announced changes in here yet right?

@jannisvisser Right. I made the changes but they conflicted with the other PRs. So it made sense to first merge your changes then refactor on the merged branch.


Effects Panel not appearing

I'm sure I'm doing something wrong here. I installed this module, set the permissions on both fields to Player though I'm the GM. Selected one of the tokens on the canvas and nothing.
To start, I'm using PF1e. Is this a 5e-only module?

I am pretty sure that this is the byproduct of a typo in the module.json.  Dfred, I think you left in the system version field even though theres no system defined, so its adversely effecting non dnd system users since pathfinders got a low version number vs what you left in:

Nah, this is because of something else. Should be fixed in v2.0.4 though. Thanks for the report!


HSEARCH-2075 ShardIdentifierProvider should allow customization of sh…

…ards for deletion
https://hibernate.atlassian.net/browse/HSEARCH-2075

Needs some clarifications: being discussed on the JIRA issue.

merged, thanks!


Ethernet compatibility

Hello!
I would like to know if is your library compatible with LAN8720, or other Ethernet controllers?

The library is listening the port you want, so any lpwip interface is compatible.

Thanks!!!
I have only other question!! As it’s forbidden to use Delay and yield, may I use the mutex to interact with variables from other threads? Because causas a little delay in the callbacks

if the delay is too long that may block the main process causing a reboot. For that cases a good option is to use a queue, look a FreeRtos documentation.

Thanks for the explanation


Increase lint timeout from 5m to 10m

The golangci-lint-action has a history of being slow. We've observed the tool timeout on several occasions now and its possibly due to a defecft in the action.
https://github.com/golangci/golangci-lint-action/issues/297

/approve


Rewrite a part of OpsController::Db#db_list a bit

Looks slightly more readable now, does it?
Let me know if I should squash commits together.

@matthewd Please review

:+1: squash please

@matthewd done!

Thanks @DNNX, looks much better!


Remove createJSModules @ovveride - RN 0.47 compatibility

https://github.com/facebook/react-native/issues/15232

Thank you!

Can you please release new version with this fix? @kraffslol