Add nightly build support for BishengJDK-11 and BishengJDK-8

Hi, I'm a member of the BishengJDK development team from Huawei. We are very interested in building and distributing binaries of BishengJDK via AdoptOpenJDK.
BishengJDK-8 aarch64 port was based on aarch64-port/jdk8u-shenandoah/ and BishengJDK-11 aarch64 port was based on jdk-updates/jdk11u/. Here is our open-sourced repo on Gitee:
BishengJDK-8: https://gitee.com/openeuler/bishengjdk-8 and BishengJDK-11: https://gitee.com/openeuler/bishengjdk-11. For more information, please refer to the WIKI.
Mirror on Github : https://github.com/openeuler-mirror/bishengjdk-11 and https://github.com/openeuler-mirror/bishengjdk-8
How should we get started? Is there anything we can do?
Look forward to your reply. thank you .

@kuenking Great news. I listed the most important points already in https://github.com/AdoptOpenJDK/openjdk-build/issues/2420#issuecomment-769747684. What you can do immediately is make the build scripts here compatible with Bisheng and then connect with the rest of the team to enable the pipelines. Might make sense to sign-up on Slack.
Some of the work for Bisheng was already done as part of https://github.com/AdoptOpenJDK/openjdk-build/pull/2485/files.

@kuenking Great news. I listed the most important points already in #2420 (comment). What you can do immediately is make the build scripts here compatible with Bisheng and then connect with the rest of the team to enable the pipelines. Might make sense to sign-up on Slack.
Some of the work for Bisheng was already done as part of https://github.com/AdoptOpenJDK/openjdk-build/pull/2485/files.

@aahlenst
Thank you for your acceptance and suggestions, we will launch a pr as soon as possible, thank you！

With https://github.com/AdoptOpenJDK/openjdk-build/pull/2523 having gone in to change the repo we pull the Bisheng code for RISC-V to the same one you mention above I'm reasonably sure this will be very easy to implement with minimal work :-)

@kuenking Should those platforms be build from the master branch of the repositories? We've currnetly fixed bisheng to be the risc-v branch but that's set here and easy enough to fix :-)

I've had a quick test and the build scripts seem capable of building from those repositories on x64 and aarch64. It will also need an adjustment to getOpenJdkVersion in build.sh to handle your JDK8 repository, correctly but otherwise builds with no significant problems in my development environment (I tested without debug symbols):
=JAVA VERSION OUTPUT=
openjdk version "11.0.10" 2021-01-19
OpenJDK Runtime Environment Bisheng (build 11.0.10+9-202103181725)
OpenJDK 64-Bit Server VM Bisheng (build 11.0.10+9-202103181725, mixed mode)
=/JAVA VERSION OUTPUT=

=JAVA VERSION OUTPUT=
openjdk version "1.8.0-internal"
OpenJDK Runtime Environment Huawei (build 1.8.0-internal-202103181751-b00)
OpenJDK 64-Bit Server VM Huawei (build 25.71-b00, mixed mode)
=/JAVA VERSION OUTPUT=

If consistent java version output is required, there needs to be a defined set of git "tags" which the build scripts determine the jdk build level from, or a version.txt file, like: https://github.com/feilongjiang/bishengjdk-11-mirror/blob/risc-v/version.txt
What is the theme for tags in : https://github.com/openeuler-mirror/bishengjdk-11/tags ? not sure I can see a consistent tagging theme?

FYI @kuenking  I think one of the kae commits from yesterday to the JDK8 repository has resulted in a compilation error. Thought I'd done something wrong but it seems to build ok again if I go back to the last ga tag :-)

What is the theme for tags in : https://github.com/openeuler-mirror/bishengjdk-11/tags ? not sure I can see a consistent tagging theme?

@andrew-m-leonard We have two branches in bishengjdk-11: master (for aarch64) and risc-v (for riscv64). The tag named as  bisheng_riscv is the release tag for risc-v, and others for master. Maybe use version.txt file is a better way to set the java version? @kuenking

@sxa @andrew-m-leonard
1、I'm sorry I didn't respond to the message in time for anything else.
2、For AArch64, add --disable-warnings-as-errors to JDK11 and --with-extra-cxxflags="-Wno-error" --with-extra-cflags="-Wno-error" to JDK8.
3、We have discussed that maybe use version.txt file is a better way to set the java version. PR has been integrated into the Gitee for Bisheng JDK. One day later, Github for Bisheng will complete code synchronization.
4、for bisheng jdk11 ,   version.txt  <IP_ADDRESS>.12    ----->  build 11.0.10+12
for bisheng jdk8,  version.txt  8.2<IP_ADDRESS>    -----> build 1.8.0_282-b12
Thanks all

Thanks. If you are able to add in a version.txt into each branch that would make things a lot less complex in the build scripts so that would definitely be my preferred option.

@sxa the version.txt has been merged into the github mirror of bisheng jdk.

@kuenking @feilongjiang I'm getting the following on JDK8/aarch64 but not on JDK8/x64 - is there a known build break in the code base just now? This is with GCC 7.5
In file included from /home/jenkins/openjdk-build/build-farm/workspace/build/src/jdk/src/solaris/native/org/openeuler/security/openssl/kae_cipher_aes.c:24:0:
/usr/include/openssl/evp.h:652:5: note: expected 'int *' but argument is of type 'unsigned int *'
 int EVP_CipherFinal_ex(EVP_CIPHER_CTX *ctx, unsigned char *outm, int *outl);
     ^~~~~~~~~~~~~~~~~~
/home/jenkins/openjdk-build/build-farm/workspace/build/src/jdk/src/solaris/native/org/openeuler/security/openssl/kae_cipher_rsa.c: In function 'Java_org_openeuler_security_openssl_KAERSACipher_nativeCreateRSAPrivateCrtKey':
/home/jenkins/openjdk-build/build-farm/workspace/build/src/jdk/src/solaris/native/org/openeuler/security/openssl/kae_cipher_rsa.c:301:9: warning: implicit declaration of function 'RSA_set0_key'; did you mean 'RSA_check_key'? [-Wimplicit-function-declaration]
     if (RSA_set0_key(rsa, bnN, bnE, bnD) <= 0 ||
         ^~~~~~~~~~~~
         RSA_check_key
/home/jenkins/openjdk-build/build-farm/workspace/build/src/jdk/src/solaris/native/org/openeuler/security/openssl/kae_keypairgenerator_rsa.c:49:5: error: 'RSA_get0_n' undeclared here (not in a function); did you mean 'RSA_verify'?
     RSA_get0_n,
     ^~~~~~~~~~
     RSA_verify

@sxa, could you tell me the version of openssl in your aarch64 environment. It requires at least 1.1.1a to build, which might be the problem, as it shows that it didn't find the function RSA_set0_key and RSA_get0_n belonging to openssl lib.

@sxa, could you tell me the version of openssl in your aarch64 environment. It requires at least 1.1.1a to build, which might be

That would likely explain it - none of our other builds require that so far. We build on CentOS7 which has 1.0.2k.

I've managed to get it to build using CFLAGS and CXXFLAGS with -I flags pointing to a separate OpenSSL111 installation so we need to determine the best way to get that available to the build.

For the vesion.txt parsing I'm currently using:
      if [ "${BUILD_CONFIG[OPENJDK_CORE_VERSION]}" == "${JDK8_CORE_VERSION}" ]; then
        local updateNum="$(cut -d'.' -f 2 <${bishengVerFile})"
        local buildNum="$(cut -d'.' -f 5 <${bishengVerFile})"
        version="jdk8u${updateNum}-b${buildNum}"
      else
        local minorNum="$(cut -d'.' -f 2 <${bishengVerFile})"
        local updateNum="$(cut -d'.' -f 3 <${bishengVerFile})"
        local buildNum="$(cut -d'.' -f 5 <${bishengVerFile})"
        version="jdk-11.${minorNum}.${updateNum}+${buildNum}"
      fi

Not sure if those are the values you want - in particular I'm not sure on the value you'd like at the end of jdk8u282- or if you want a different format for your other segments of version.txt

For the vesion.txt parsing I'm currently using:
      if [ "${BUILD_CONFIG[OPENJDK_CORE_VERSION]}" == "${JDK8_CORE_VERSION}" ]; then
        local updateNum="$(cut -d'.' -f 2 <${bishengVerFile})"
        local buildNum="$(cut -d'.' -f 5 <${bishengVerFile})"
        version="jdk8u${updateNum}-b${buildNum}"
      else
        local minorNum="$(cut -d'.' -f 2 <${bishengVerFile})"
        local updateNum="$(cut -d'.' -f 3 <${bishengVerFile})"
        local buildNum="$(cut -d'.' -f 5 <${bishengVerFile})"
        version="jdk-11.${minorNum}.${updateNum}+${buildNum}"
      fi

Not sure if those are the values you want - in particular I'm not sure on the value you'd like at the end of jdk8u282- or if you want a different format for your other segments of version.txt

You're so cool. That's exactly what we want!

@sxa, could you tell me the version of openssl in your aarch64 environment. It requires at least 1.1.1a to build, which might be

That would likely explain it - none of our other builds require that so far. We build on CentOS7 which has 1.0.2k.

Is there a chance that you could update the openssl version of the image? Otherwise, we have to disable the building of the feature as x64.

For the vesion.txt parsing I'm currently using:
      if [ "${BUILD_CONFIG[OPENJDK_CORE_VERSION]}" == "${JDK8_CORE_VERSION}" ]; then
        local updateNum="$(cut -d'.' -f 2 <${bishengVerFile})"
        local buildNum="$(cut -d'.' -f 5 <${bishengVerFile})"
        version="jdk8u${updateNum}-b${buildNum}"
      else
        local minorNum="$(cut -d'.' -f 2 <${bishengVerFile})"
        local updateNum="$(cut -d'.' -f 3 <${bishengVerFile})"
        local buildNum="$(cut -d'.' -f 5 <${bishengVerFile})"
        version="jdk-11.${minorNum}.${updateNum}+${buildNum}"
      fi

Looks ok to BishengJDK-11 risc-v. ;-)

Is it posssible that you could update the openssl version of the image? Otherwise, we have to disable the building of the feature as x64.

I tried some options yesterday bit couldn't really make it work. I put a copy of 1.1.1j in another directory but couldn't convince the build process to pick it up. My preferred option world be the first one on this list.

Have a configure option on your build to say where to pick up the openssl header files from
Use a general option such as CLAGS and LDFLAGS to point the build at the location of 1.1.1 (I tried a few options but couldn't make that work yesterday)
Build on a different distribution which has 1.1.1 by default
If there is an option for it in the build, disable OpenSSL for now until we figure out the best solution :-)
Trying to replace the default OpenSSL would likely have other problems as the automatic patching and dependency management on the system would not be able to occur and  on a quick test yesterday type such as curl on the machine did not work with the system OpenSSL being upgraded outside the package manager

It may still be possible to find a solution to the last one but if there was a way to direct it to another location for the openssl give that world be my preferred option.

@sxa, we use LD_LIBRARY_PATH to specify the openssl lib dir. You could have a try.
If it still doesn't work, add --disable-kae option when configuring to disable building the feature.

With --disable-kae it suceeds:
=JAVA VERSION OUTPUT=
openjdk version "1.8.0_282-internal"
OpenJDK Runtime Environment Huawei (build 1.8.0_282-internal-202103251619-b12)
OpenJDK 64-Bit Server VM Huawei (build 25.282-b12, mixed mode)
=/JAVA VERSION OUTPUT=

Just setting LD_LIBRARY_PATH didn't work (as that only affects runtime, not the linker process during the build) however if I use the full set of --with-extra-cflags=-I/usr/local/openssl-1.1.1/include  --with-extra-cxxflags=-I/usr/local/openssl-1.1.1/include --with-extra-ldflags=-L/usr/local/openssl-1.1.1/lib to point to the 1.1.1 version then the build completes without problems. I've added that into my PR at https://github.com/AdoptOpenJDK/openjdk-build/pull/2537/files. With all these tests I'm glad I'm using an aarch64 system that can build in 5 minutes ;-)
Thank you for the advice :-)

Great！Cheers！


Licensing

How should we license MPM? I, personally, am for permissive licensing such as the MIT license strategy, but we must consider compatibility with other licensing styles with which we must interoperate.

I generally agree with the MIT and BSD license strategies. As long as we don't have any libraries that are dependent on the GPLv2.

We'll go with MIT and begin to phase out any licenses that are not compatible when possible.

Added MIT license in c767e66db3e8cc2e5594978b5f701d668e655641.


feat: retain cli args when relaunching after update, closes #7402

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[x] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary

Other information

The argument list had a trailing ,  (using join() is better) that was being denied by one of the bundle targets (probably wix?). Remember to test it with the updater e2e test: cargo test --test '*' -- --ignored.

the test kept failing on my end because Windows defender kept flagging it as a virus and removing it, so I pushed to see if it works on CI and forgot about it

And I had to refrain from using .join because it is not implemented for OsString in 1.61

This needs to be audited. @tweidinger @chippers can this be exploited? I'll go ahead and do the one change I know you'll request, which is pulling from the cached args instead of reading it at update time.

@amrbashir can you add "change Env.args to pull from std::env::args_os instead of std::env::args" to the v2 breaking change list? :|

Start-Process : Missing an argument for parameter 'ArgumentList'. Specify a parameter of type 'System.String[]' and try again.
At line:1 char:276
+ ... projects\tauri\target\debug\app-updater.exe" -ArgumentList
+                                                             ~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Start-Process], ParameterBindingException
    + FullyQualifiedErrorId : MissingArgument,Microsoft.PowerShell.Commands.StartProcessCommand

can you change the updater to check if the argument list is empty and not add the -ArgumentList thing if so?

Another crate to downgrade on CI: memchr :(


reduce number of tests being run under Miri

With this (and an upcoming Miri PR), a number of tests are actually passing under Miri :D
cargo miri test --test i32_ops -- --skip cast --skip max --skip min --skip is_
cargo miri test --test f32_ops -- --skip cast --skip max --skip min --skip is_

I could also add a Miri job to CI? We probably want it to be 'allowed to fail' so that new intrinsics that Miri does not support yet can still easily be added, but it would be nice to somehow track whether the Miri state becomes worse.

Not sure, I would guess around 20-30min for the entire test suite -- but I can't say yet because not all of it passes yet. ;)

Ah, now Miri fails since it is still a day old and hence requires const_fn_trait_bound. ;) That should fix itself tomorrow though.

error: unsupported operation: unimplemented intrinsic: simd_ceil
  --> /home/runner/work/portable-simd/portable-simd/crates/std_float/src/lib.rs:91:18
   |
91 |         unsafe { simd_ceil(self) }
   |                  ^^^^^^^^^^^^^^^ unimplemented intrinsic: simd_ceil
   |

Interesting, that intrinsic is not even declared in https://github.com/rust-lang/portable-simd/blob/master/crates/core_simd/src/intrinsics.rs. :thinking:

But the tests that are now in there should work. It's a bit annoying to check this since "ignoring failures" means getting green checkmarks everywhere (with GHA there is no way to get a red checkmark for the job but still get a green checkmark for the PR as a whole) -- one has to look at the log to check if it actually failed. But that's the best we can do I guess.

Yes, that intrinsic is listed with the other "might libcall" floating point intrinsics.
https://github.com/rust-lang/portable-simd/blob/2d13059ae9162997c5b88997bda44443615f12ab/crates/std_float/src/lib.rs#L24-L44


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Created page for create password page

Change description
Created password change page with form. Fields are new password and confirm password.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense.
[ ] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[x] For UI changes, I have attached screenshots

@all-contributors please add @kumkum671  for code


Added the Food detector script

Description
I have added the food detector script to the deep learning folder. The code is in the Food Detector folder.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

(Add x in the [] to mark as completed.)
Related Issues or Pull Requests
(Link the Issue Number over here.)
closes #452

@khusheekapoor How do I do it?

Hey @khusheekapoor I have added the project link to the readme. Please check and merge


Render updates

Fixes a bunch of issues in rendering, started using the gerbv test files to check rendering, its not an automated test (since we don't support everything they do yet)  but an easy way to catch rendering issues. The biggest change to the rendering side is that primitives, macros, etc. are rendered to a mask and then that mask is painted to the image, which prevents holes from clearing primitives below them, per the spec.
I'm gonna keep working on rendering issues until our output looks close enough to gerbv's

Coverage increased (+1.02%) to 80.581% when pulling c1b29035218467b496fffed76ea85390461150c7 on render_updates into 521fe89150c6aaa0ff0954cc8d32e4b6f8009324 on master.

Looks good, using gerbv was always a goal for me, hope we can automate it in the future.


Point cloud process

❓ Questions & Help

Hi,
I tried to use the default pytorch dataloader to load point clouds. I have reshaped the point tensors to [B * N, 3] and create a batch-vector [B*N] and feed them to the pointnet++.
I get error at
x = F.relu(self.local_sa1(None, pos, edge_index))
as follows:
File "build/bdist.linux-x86_64/egg/torch_geometric/nn/conv/point_conv.py", line 46, in forward
File "build/bdist.linux-x86_64/egg/torch_geometric/nn/conv/message_passing.py", line 86, in propagate
File "build/bdist.linux-x86_64/egg/torch_geometric/utils/scatter.py", line 33, in scatter_.
Thanks in advance.

Are you sure there is no other error message? This is kinda meaningless. It would help if you could print pos and edge_index size, dtype, and device before calling local_sa1.

There are the information of those tensor and the missing error message
('pos', (32768, 3), torch.float32, device(type='cuda', index=0))
('edge_index', (2, 576249), torch.int64, device(type='cuda', index=0))
THCudaCheck FAIL file=/opt/conda/conda-bld/pytorch_1549614443593/work/aten/src/THC/generated/../THCTensorMathCompare.cuh line=82 error=11 : invalid argument

This seems to be an indexing problem. Can you run again with CUDA_LAUNCH_BLOCKING=1?
Additionally, please report the output of
print(edge_index.min().item(), edge_index.max().item())

When i reduce the range of the radius, the size of edge_index reduce to (2, 117343) and the code is work

Ah, I see. You can alternatively increase the max_neighbors arg in the radius call. However, this should not crash and I will fix it.

Fixed in master and v1.1.1! Thank you.
Problem:
The radius call expects a max_num_neighbors argument, which may result in ignoring a lot of points when the range of the radius is set to a large value. Hence, a bipartite graph is constructed where possibly not all nodes have an edge to a sampled node. Before this bugfix, we took an initial guess of the bipartite graph size (given by edge_index[0].max() and edge_index[1].max()), which could yield a wrong size for reasons mentioned above. Hence, the PointConv does now additionally expect a size argument which takes in the adjacency matrix size as a tuple. If set to None, its size is given by the initial guess.

Thank you for clarification.


Setting converter options to prevent metadata loss?

Hi Marijn,
I want to prevent that my images looking washed out, because of a missing color profile and thats why I wonder if there is a solid way to pass options through to the converter?
For example:
"metadata" => "all" as option array to disable this -strip command, which is removing color profiles and other metadata.
https://github.com/rosell-dk/webp-convert/blob/master/src/Convert/Converters/ImageMagick.php#L154
The -strip command is decribed here:
https://imagemagick.org/script/command-line-options.php#strip
This -strip command is also running in the default Kirby "ImageMagick" thumb driver. I made a copy of this, removed the -strip command and moved it in a simple plugin. The Kirby generated images/jpegs are looking better now, but the webp images are still loosing their color profile.
Thank you for your time and help.
Tim

Hi Tim, I am working on the implementation for passing through the conversion options. I have this working via the plugin options. Only I am running into some problems in verifying that it is working correctly.
With the 'metadata' => 'all' option enabled, I see that Adobe Bridge lists the WebP file as Color Profile: Untagged, while the source file lists as sRGB IEC61966-2.1. When I use command line tools I see the following:
With exiftool:
> exiftool test.webp | grep -i profile
[...]
Profile Description             : sRGB IEC61966-2.1

With Imagemagick identify:
> identify -verbose test.webp | grep -i icc
identify: CorruptImageProfile `test.webp' (XMP) @ warning/profile.c/ValidateXMPProfile/1916.
    Profile-icc: 3144 bytes
    icc:copyright: Copyright (c) 1998 Hewlett-Packard Company
    icc:description: sRGB IEC61966-2.1
    icc:manufacturer: IEC http://www.iec.ch
    icc:model: IEC 61966-2.1 Default RGB colour space - sRGB

My knowledge of colour profiles is limited. Is this the desired functionality?

Hi Marijn,
To be honest, I don't know either, if this is the correct behavior.
Somehow it looks like it's fine that way. Both commands return a color profile, but "Imagemagick identify" also shows an error at the same time?! identify: CorruptImageProfile test.webp' (XMP) @ warning/profile.c/ValidateXMPProfile/1916.`
So far I had checked it only visually.
Can I somehow test a first draft or can support this in another way?

I am still working on some tests. It seems that the ICC profile is only present if it is explicitly included when exporting the image (from Photoshop, for example).
When minifying jpg files, this metadata is also removed.
If no profile is present in the image, it is assumed that it is an sRGB file.
I have also verified the converted webp files. This seems to work correctly, despite the strange message in Imagemagick identify.
> webpinfo test.webp
File: test.webp
RIFF HEADER:
  File size:  13936
Chunk VP8X at offset     12, length     18
  ICCP: 1
  Alpha: 0
  EXIF: 1
  XMP: 1
  Animation: 0
  Canvas size 1022 x 704
Chunk ICCP at offset     30, length   3152
Chunk VP8  at offset   3182, length   7864
  Width: 1022
  Height: 704
  Alpha: 0
  Animation: 0
  Format: Lossy (1)
Chunk EXIF at offset  11046, length     94
Chunk XMP  at offset  11140, length   2796
No error detected.

I can also report that the other metadata like EXIF and XMP is preserved with 'metadata' => 'all'.


Speed up "Refine > Associate Proteins"

The AssociateProteinsDlg was really slow when the document contained tens of thousands of peptides, especially when using a FASTA file.
This change speeds up finding which peptides are contained in a protein sequence by using a Trie data structure (in the new class "SubstringFinder"). Also, it now does that string matching on multiple threads using ParallelEx.
Also, moving the peptides to different parents is made faster by just changing the Identity objects (Peptide, etc) instead of calling ChangeSettings on DocNode's.

Did you consider building an Aho-Corasick trie for all peptides then running all the proteins (in parallel) through it? I ported a C# Aho-Corasick implementation to C++ and it worked quite well so I expect you could re-use the original C# implementation: http://tomasp.net/blog/ahocorasick.aspx/


Submitting the assignment

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Submission of the assignment

Added two ERDs
Update the md with answers

What did you learn from the changes you have made?
I learnt how to create an ERD from scratch.
I also learnt about Slowly Changing Dimensions (SCD)
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
N/A
How were these changes tested?
N/A
A reference to a related issue in your repository (if applicable)
Checklist

[x] I can confirm that my changes are working as intended

Assignment marked.


Font size should be able to be set once for a diagram

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
I am always frustrated when editing text on an arrow connection, within a shape, or directly on the grid. Tee app always defaults to 12pt font, which is tiny (but I'm not here to complain about the default font size). What I think should be the standard behaviour is if I change the font size, any subsequent text added to the diagram should be the same font size that I initially selected. That way I won't have to constantly change the font sizes when labeling my diagrams.
Describe the solution you'd like
Persist the font size I select, and use it for all new text elements in a diagram.
Describe alternatives you've considered
The alternative is everything continuously defaults to 12pt, which is not ideal.

Try https://github.com/jgraph/drawio/discussions/3312

Perfect, thank you!


Object#timeout is deprecated

with ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15].
The warning says: Object#timeout is deprecated, use Timeout.timeout
instead.

would be great to see this merged to remove the warning messages.

👍

Yes please. Seeing this error as well.

I'm +1 to merge this as well.  We'll have to identify whomever is currently maintaining this at Puppet to get it released.

@haus Ping?  Is there a chance you (or someone) could cut a small release of this gem to get rid of the warning?  I'd also be happy to take over maintenance of it going forward if that's easier for you.

@jeffmccune let me ping the RE netdev folks and hand it off to them. /cc @shermdog @ScottGarman

I'll jump on this later today.

Thanks!

v0.2.2 of the gem has been release to rubygems now. Thanks for the contribution!


Handle IPv6 KUBERNETES_SERVICE_HOST

Fixes two cases where KUBERNETES_SERVICE_HOST is used without proper handling for it potentially being an IPv6 address. The changes are derived from the third case in fluent-plugin-kubernetes-metadata-filter/lib/fluent/plugin/filter_kubernetes_metadata.rb where IPv6 is handled properly.

The workaround for this issue is setting the Kubernetes URL directly. (fluentd.apiServerUrl in sumologic-kubernetes-collection.)
However, I've hit further problems with fluentd starting which may indicate there is a deeper incompatibility:
2022-05-13 04:27:38 +0000 [info]: adding match in @FLUENT_LOG pattern="**" type="null"
2022-05-13 04:27:38 +0000 [info]: adding filter in @DATAPOINT pattern="prometheus.metrics**" type="record_modifier"
c2022-05-13 04:27:38 +0000 [info]: adding filter in @DATAPOINT pattern="prometheus.metrics**" type="enhance_k8s_metadata"
a2022-05-13 04:27:38 +0000 [info]: #0 cache_ttl: 7200, cache_size: 10000, cache_refresh: 3600, cache_refresh_variation: 900
2022-05-13 04:27:38 +0000 [info]: #0 Initializing Kubernetes API clients
2022-05-13 04:27:38 +0000 [info]: #0 create client with URL: https://[fdfc:54c1:9cb2::1]:443/api and apiVersion: v1
2022-05-13 04:27:38 +0000 [info]: #0 create client with URL: https://[fdfc:54c1:9cb2::1]:443/apis/apps and apiVersion: v1
2022-05-13 04:27:38 +0000 [info]: #0 Will refresh cache every 00h 57m 58s
2022-05-13 04:27:38 +0000 [info]: adding filter in @DATAPOINT pattern="prometheus.metrics**" type="prometheus_format"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.apiserver**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.container**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.control-plane**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.controller-manager**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.kubelet**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.node**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.scheduler**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics.state**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match in @DATAPOINT pattern="prometheus.metrics**" type="copy"
2022-05-13 04:27:38 +0000 [info]: adding match pattern="fluentd.pod.healthcheck" type="relabel"
2022-05-13 04:27:38 +0000 [info]: adding match pattern="prometheus.metrics**" type="datapoint"
2022-05-13 04:27:38 +0000 [info]: adding source type="prometheus"
2022-05-13 04:27:38 +0000 [info]: adding source type="prometheus_output_monitor"
2022-05-13 04:27:38 +0000 [info]: adding source type="http"
2022-05-13 04:27:38 +0000 [info]: adding source type="http"
2022-05-13 04:27:38 +0000 [info]: #0 starting fluentd worker pid=286 ppid=7 worker=0
2022-05-13 04:27:38 +0000 [info]: #0 Starting watching for service changes
2022-05-13 04:27:38 +0000 [info]: #0 fluentd worker is now running worker=0
#<Thread:0x00007f2506679800@watch_endpoints /usr/local/bundle/gems/fluentd-1.14.6/lib/fluent/plugin_helper/thread.rb:70 run> terminated with exception (report_on_exception is true):
/usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `initialize': failed to connect: getaddrinfo: Name or service not known (HTTP::ConnectionError)
	from /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `open'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `connect'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/connection.rb:43:in `initialize'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:71:in `new'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:71:in `perform'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:31:in `request'
	from /usr/local/bundle/gems/kubeclient-4.9.1/lib/kubeclient/watch_stream.rb:21:in `each'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:21:in `block (3 levels) in start_service_monitor'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:19:in `tap'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:19:in `block (2 levels) in start_service_monitor'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:13:in `loop'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:13:in `block in start_service_monitor'
	from /usr/local/bundle/gems/fluentd-1.14.6/lib/fluent/plugin_helper/thread.rb:78:in `block in thread_create'
/usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `initialize': getaddrinfo: Name or service not known (SocketError)
	from /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `open'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `connect'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/connection.rb:43:in `initialize'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:71:in `new'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:71:in `perform'
	from /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:31:in `request'
	from /usr/local/bundle/gems/kubeclient-4.9.1/lib/kubeclient/watch_stream.rb:21:in `each'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:21:in `block (3 levels) in start_service_monitor'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:19:in `tap'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:19:in `block (2 levels) in start_service_monitor'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:13:in `loop'
	from /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:13:in `block in start_service_monitor'
	from /usr/local/bundle/gems/fluentd-1.14.6/lib/fluent/plugin_helper/thread.rb:78:in `block in thread_create'
2022-05-13 04:27:38 +0000 [warn]: #0 thread exited by unexpected error plugin=Fluent::Plugin::EnhanceK8sMetadataFilter title=:watch_endpoints error_class=HTTP::ConnectionError error="failed to connect: getaddrinfo: Name or service not known"
2022-05-13 04:27:38 +0000 [error]: #0 unexpected error error_class=HTTP::ConnectionError error="failed to connect: getaddrinfo: Name or service not known"
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `initialize'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `open'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/timeout/null.rb:21:in `connect'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/connection.rb:43:in `initialize'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:71:in `new'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:71:in `perform'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/http-4.4.1/lib/http/client.rb:31:in `request'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/kubeclient-4.9.1/lib/kubeclient/watch_stream.rb:21:in `each'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:21:in `block (3 levels) in start_service_monitor'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:19:in `tap'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:19:in `block (2 levels) in start_service_monitor'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:13:in `loop'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/fluent-plugin-enhance-k8s-metadata-2.0.0/lib/sumologic/kubernetes/service_monitor.rb:13:in `block in start_service_monitor'
  2022-05-13 04:27:38 +0000 [error]: #0 /usr/local/bundle/gems/fluentd-1.14.6/lib/fluent/plugin_helper/thread.rb:78:in `block in thread_create'
2022-05-13 04:27:38 +0000 [error]: #0 unexpected error error_class=HTTP::ConnectionError error="failed to connect: getaddrinfo: Name or service not known"
  2022-05-13 04:27:38 +0000 [error]: #0 suppressed same stacktrace
2022-05-13 04:27:39 +0000 [error]: Worker 0 finished unexpectedly with status 1

@swiatekm-sumo the URL used is included in the log messages above: https://[fdfc:54c1:9cb2::1]:443/api
$ kubectl get service kubernetes
NAME         TYPE        CLUSTER-IP          EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   fdfc:54c1:9cb2::1   <none>        443/TCP   55d

I tested it with curl from inside a pod and received a 403, so it resolved. There appear to be similar cases where IPv6 & fluentd don't play nice:
https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/issues/158#issuecomment-617909880
The thread above starts with a similar IPv6 URL construction issue to the one this PR is designed to address.
If this project is intended to support IPv6 K8S clusters (particularly AWS EKS, where IPv6 has significant networking advantages) then I think it makes sense to fix the IPv6 URL construction even if there are additional IPv6 issues to resolve.
I just can't guarantee that if you try confirming the patch on a IPv6 cluster that it's going to work first time. 🙂

@tjdett I'm fine merging this PR (maybe with a simple unit test for the url transformation?), but if it doesn't actually solve the problem, then we should track it in a separate issue.

@swiatekm-sumo the SumoLogic support request tracking my IPv6 issue is #72345 if that helps. I included a link to this PR in it, but last status was "checking with kubernetes team" so it might not have reached you yet.
I'm going to leave adding tests to your team. I didn't see any existing coverage for KUBERNETES_SERVICE_HOST URL construction in the sub-projects I modified, and this is an open source project that exists to support use of a commercial product.
I expended a day trying to get sumologic-kubernetes-collection as a whole to work without success, and I don't have a business justification I can make to go further. If you want to close the PR, I'm OK with that.


[5.3] Allow the Notifiable to specify the channel it should broadcast…

I don't like to expose the User.id in my public JavaScript files.
I use Hashid's to hash the user id but then i came across the issue that my Notifiable object could not specify a custom channel it should use to broadcast on. This change allows the Notifiable specify a custom channel.
This is a re-submit of #15593

Tests?

i will add a tests as soon as get back home from work

This whole idea is a little weird to me. There is no major security concern to showing a user their own ID that I know of. I don't really like the method name here currently either.

Respectfully disagree @taylorotwell, it can be used to guess the number of users the site has, which can be useful information for competitors.

I was just trying to add some "flexibility" in how notifications are pushed to my public frontend.
It would give the great feeling of not being "bound" to only one standard.

Maybe @taylorotwell could reconsider with another approach/another function name with tests?


Investigate adding ability to control loot being added to bots via config

bot.json / "spawnBotWithLoot": { "assault": true, "pmc": false}

Originally written by chomp

https://github.com/sp-tarkov/server/commit/673256e5fac0685963d466df8bf7f8001c677936

Originally written by chomp


Antigen interferes with completion in weird ways

bindkey "${terminfo[kcbt]}" reverse-menu-completion

The above should make shift-tab go backward after you start tabbing through completion options. Without antigen, this works as expected. If you source bin/antigen.zsh, however, it doesn't work right; shift-tab will do nothing but stop completion.
From what I can gather, it's trying to restart completion instead of move backward through the current completion list. Since the completion options are put onto the command line as you tab through them, this just ends completion (because it tries to start completion with a full match on the line).
I tried commenting out some of the compinit related lines in bin/antigen.zsh and that made the issue go away, but I haven't been able to narrow it down past that.

Managed to narrow it down a bit. Problem goes away when I comment out the following:
In function -antigen-env-setup: ```
# Setup antigen's own completion.
autoload -Uz compinit
if $_ANTIGEN_COMP_ENABLED; then
compinit -C
compdef _antigen antigen
fi

And in function `antigen-apply`: ```
    # Load the compinit module. This will readefine the `compdef` function to
    # the one that actually initializes completions.
    autoload -U compinit
    if [[ -z $ANTIGEN_COMPDUMPFILE ]]; then
        compinit -i
    else
        compinit -i -d $ANTIGEN_COMPDUMPFILE
    fi

I'll take a look later today.
Meanwhile could you post your .zshrc configuration?, Zsh version and OS?

A .zshrc capable of reproducing the issue is in the first post. One line. Zsh version is 5.2, OS is Arch Linux. But actually now that I'm poking at this more, it looks like loading compinit at all -- with or without antigen -- is enough to cause this screwup... :S

You should probably try rm -f ~/.zcompdump*. Tried with latest antigen on zsh 5.2, worked as expected.

Closing this up for now. Comment if you see it's still behaving in this way and it's effectively related to antigen.
Thanks for reporting.


NoSuchMethodException: CraftMetaSkull.setProfile in EcoEnchants with Minecraft 1.21.1

Describe the bug
When reloading EcoEnchants on Paper 1.21.1, the server logs a NoSuchMethodException related to the setProfile method in CraftMetaSkull. This seems to affect the setting of skull textures through EcoEnchants.
To Reproduce
Steps to reproduce the behavior:

Install EcoEnchants on Paper 1.21.1.
Reload the plugin or server.
Observe the error in the server logs: java.lang.NoSuchMethodException: org.bukkit.craftbukkit.inventory.CraftMetaSkull.setProfile(com.mojang.authlib.GameProfile)

Log
latest.log: https://paste.helpch.at/ufakoxufuq.makefile
Expected behavior
The plugin should set skull textures properly without throwing an exception during reloads or when accessing skull-related functionality.
Actual Behavior
The server throws a NoSuchMethodException in the logs when EcoEnchants attempts to use the setProfile method, resulting in a warning but no visible impact on gameplay. The skull textures do not apply as expected.
Plugin List
EcoEnchants 12.18.7
eco-6.74.1-all
Software brand
Backend: Paper 1.21.1-77-4ff58c4 (MC: 1.21.1)
Additional Information
This issue appears to be related to changes in the internal methods of Minecraft or Paper, affecting how skull textures are handled in the plugin. The plugin may require updates to accommodate these changes.

++++


[MB-9050] update certs in demo

Description
This adds new tls_vars for each environment in circle ci
Reviewer Notes
Unclear if the changes to deploy-app-client-tls will break in stg/prd since this was hard-coded to use exp keys.
Code Review Verification Steps

[x] If the change is risky, it has been tested in experimental before merging.

We still have some bugs on the Prime side. It's in Slack here. Can't summarize now but I can focus on this fix later in the afternoon ET if necessary.

I think this is ready for a last review/merge.


Added TweenSequence, TweenSequenceItem, ConstantTween

Make it possible to define an animation by stringing together a sequence of tweens.

CurveTween is an Animatable, which is the superclass of Curve. I think if TweenSequenceItem were to take an Animatable instead of a Curve, we'd be able to get rid of the curve property and use composition instead.

This is great, I love it.

Although I left the name "TweenSequence", since that's likely to be the only use case, I changed the type of TweeSequenceElement<T>.tween to Animatable<T>, and removed the curve parameter.
To evaluate an Animatable at t I used the same approach as the implementation of Animatable.chain:
tween.evaluate(new AlwaysStoppedAnimation<double>(t));

Guys, maybe also update https://flutter.io/animations/staggered-animations/ to reflect this update?


Do you have any plan to support lower versions of Python?

When Python is packaged into exe, it can use ctypes to raise the system dialog. Using ctypes can reduce the size of file, and reduce the startup time of running this program.
Therefore, I learnt how to use ctypes and found your project, which is very useful, and I like it so much.
But the library need version above PY39. But I learnt the source code and find no features were uesd in PY39. What is your consider for this restrict?
Further, developer using other versions of Python may have the same needs, such as platforms that do not support type checking or f-string? Do you have any plan to support lower versions of Python?

Thank you for your message.
Regarding your question, we do not plan to support lower versions.
The reason for limiting the supported version to PY39 or later is that the environment in which we developed and tested the software was PY39, not PY38 or lower versions.


Create theme command

I would like if possible to have a command to manage the themes of the application.

any solution?


Evaluation output persistence framework

The RRE current implementation outputs a JSON file as result of the evaluation process.
The issue is about creating a persistence framework for binding in a pluggable way several persistence strategies (e.g. database, Cassandra, Solr, Elasticsearch).
Once the data will be persisted, it could be queried/used by some Reporting/BI tool.

Hi Andrea,
I was wondering if you had made progress with this? I've started work on a persistence framework here: https://github.com/mattflax/rated-ranking-evaluator/tree/persistence - I'd be interested to read your thoughts on my approach (if any). I'm planning to create any number of PersistenceHandlers, all managed by a PersistenceManager class. A JsonPersistenceHandler will act in place of the current default output.
I've tried to bear in mind the conversation you had with @binarymax in the comments for #56 regarding using a timestamp in place of a version key, but I haven't got as far as implementing anything solid yet.
Thanks,
Matt

Hi @mattflax sorry again for my delay in response. I think the approach your idea is in the right direction. I just merged your PR #66 which should be about this.
Do you think the io.sease.rre.persistence content covers the goal of this issue (i.e. the persistence contract interfaces + the JSON binding)?
If so, we could close this issue and later open dedicated issues for the persistence providers we want to support.
Andrea

Hi Andrea,
I think the framework as it stands does cover this issue - I've successfully used it to build an Elasticsearch persistence handler (as I'm sure you've seen).
Do let me know if I can help with documentation for these additions too - I've been adding README files with details of how to use things, but you have to dig a bit to find them.
Matt

Hi Matt, great to hear and sorry for such delay in response.
So I think we can close this and then, as mentioned, we can open new issues dedicated (when and if we want to add a new persistence provider).
The documentation, yeah, nice point. I'm not sure if you already have permissions for the Wiki, I have to check; in any case, README is good as well. When I will be able to find a decent amount of time I'll try to get the point about the current state (of software and doc).
Thanks again,
Andrea


⚠ Inventory API Endpoint has degraded performance

In 2002891, Inventory API Endpoint (https://inventory.roblox.com/v1/users/82738847/assets/collectibles?limit=10&sortOrder=Asc) experienced degraded performance:

HTTP code: 500
Response time: 1150 ms

Resolved: Inventory API Endpoint performance has improved in 869b9bf after 44 minutes.


[Marketplace] Search word and Type selections are saved if to return to chat and reopen My applications

EPAM AI DIAL chat version
0.18.0
What happened?

Click on + New conversation
Click on Search on My applications
Select several boxes in Type, enter any search_word in Search
Click on Back to Chat
Click on Search on My applications -> note that Type selection and search_word are still set -> bug

Expected result: Type selection and search word should be saved if to switch between Home page and My applications (not it works), but should be skipped if to back to chat (type should be unchecked, search word should be cleared)
Confidential information

[X] I confirm that do not share any confidential information

Verified on staging env successfully


Controlling execution (infinite loops)

Hi,
I've been investigating duktape for a replacement to V8, but I'm not able to understand the mechanism used to detect infinite loops.
In the cmdline utility I can see the ajsheap_start_exec_timeout and ajsheap_clear_exec_timeout calls being made, but I can't see where the ajsheap_exec_timeout_check() is fired from - it doesn't seem to be referenced.
Is there a more complete guide or resource on how to detect infinite loops?
James

There's some documentation here:

https://github.com/svaarala/duktape/blob/master/doc/feature-options.rst#duk_opt_exec_timeout_check
https://github.com/svaarala/duktape/blob/master/doc/sandboxing.rst#bytecode-execution-timeout-details

Closing as inactive.


This is a great book!

Just wanted to say I really like your book! It makes Rcpp a lot less intimidating for newbies. I also learned about C++11!

Hi, woodwards!
I’m really pleased to hear that. Thank you!

It's a really great book I just read the first chapter and I already love it


Cache flushing issue

What steps will reproduce the problem?
Configure schema caching or add some caching logic in controller only for frontend/ part of website (advanced yii2 template), then try to flush schema through console command: ./yii cache/flush-all
What is the expected result?
frontend cache is flushed
What do you get instead?
frontend cache is remain, actually only console cache is flushed.
Additional info
this may be critical, b/c once some changes are deployed, exception may be thrown till cache will be cleared.

Q
A

Yii version
<IP_ADDRESS>.

PHP version
7.1.2

Operating system
Linux Mint

Keeping components configuration in sync is a developer's responsibility.
In case you have the same component configuration for both frontend and console application, you can move the definition into a separate file, e.g. common.php and include it in your configs


Support enum discriminator

fixes https://github.com/Azure/autorest.python/issues/2102, https://github.com/Azure/autorest.python/issues/2152
pending on:

[x] https://github.com/Azure/typespec-azure/pull/3541

move to https://github.com/Azure/autorest.python/pull/2188


[bullet3] Add support for BulletRobotics & Extras

Is your feature request related to a problem? Please describe.
The current port explicitly disables building and linking the Extras(-DBUILD_EXTRAS), which means the BulletRobotics code is not built, which cuts off a relatively big chunk of the library, and makes it significantly harder to use.
Proposed solution
Configure the library to optionally build BulletRobotics and other Extras.
Describe alternatives you've considered
Building outside vcpkg is a relatively painful solution, one that often results in hard to maintain projects.
Additional context
Look at the difference in complexity between the InverseKinematics example and the RobotSimulator/HelloBulletRobotics example.

Hi @Spirit532
Thanks for posting this issue.
I submitted a PR #10821 to add this feature.
Could you please help confirm if this can work for you?

Hi @NancyLi1013
Just including extras appears to not work, as it creates a lot of linking errors.
Specifically a mismatch between MD_DynamicRelease(which the library appears to be stuck on) and MDd_DynamicDebug(which the project is built for).
This is additional issue, because Bullet in general does not officially support dynamic linking, and when installed using x64-windows-static exclusively, results in many missing files.
Please attempt to build it yourself and reproduce the issue. Create a new project, install bullet3[*]:x64-windows-static, try including LinearMath/btTransform.h, bullet_robotics/b3RobotSimulatorClientAPI_NoGUI.h, and then compiling the following:
b3Vector3 test1 = b3MakeVector3(1, 1, 1);
b3Vector4 test2 = b3MakeVector4(1, 1, 1, 1);
b3RobotSimulatorClientAPI_NoGUI test3;

Thanks for your test and feedback.
I will try to reproduce on my local.

The error like this:
1>bullet3Project.obj : error LNK2019: unresolved external symbol "public: __cdecl b3RobotSimulatorClientAPI_NoGUI::b3RobotSimulatorClientAPI_NoGUI(void)" (??0b3RobotSimulatorClientAPI_NoGUI@@QEAA@XZ) referenced in function main
1>bullet3Project.obj : error LNK2019: unresolved external symbol "public: virtual __cdecl b3RobotSimulatorClientAPI_NoGUI::~b3RobotSimulatorClientAPI_NoGUI(void)" (??1b3RobotSimulatorClientAPI_NoGUI@@UEAA@XZ) referenced in function main
1>C:\Users\v-ruil\source\repos\bullet3Project\x64\Debug\bullet3Project.exe : fatal error LNK1120: 2 unresolved externals
1>Done building project "bullet3Project.vcxproj" -- FAILED.

It seems that b3RobotSimulatorClientAPI_NoGUI is from the source code listed in example  folder.
I removed b3RobotSimulatorClientAPI_NoGUI test3;, the project can build successfully.
I also tried to build example and set
-DBUILD_BULLET2_DEMOS=ON
-DBUILD_BULLET3=ON

but there were still some errors like this:
LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/OPT:ICF' specification
   Creating library examples\ExampleBrowser\App_ExampleBrowser.lib and object examples\ExampleBrowser\App_ExampleBrowser.exp
Error copying directory from "F:/test/vcpkg/buildtrees/bullet3/src/2.89-eb26871ed5/data" to "F:/test/vcpkg/buildtrees/bullet3/x64-windows-static-dbg/data".
[902/903] cmd.exe /C "cd . && F:\test\vcpkg\downloads\tools\cmake-3.14.0-windows\cmake-3.14.0-win32-x86\bin\cmake.exe -E vs_link_exe --intdir=examples\SharedMemory\CMakeFiles\App_PhysicsServer_SharedMemory_VR.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x64\mt.exe --manifests  -- "E:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.25.28610\bin\Hostx64\x64\link.exe"  @CMakeFiles\App_PhysicsServer_SharedMemory_VR.rsp  /out:examples\SharedMemory\App_PhysicsServer_SharedMemory_VR.exe /implib:examples\SharedMemory\App_PhysicsServer_SharedMemory_VR.lib /pdb:examples\SharedMemory\App_PhysicsServer_SharedMemory_VR.pdb /version:0.0  /machine:x64 /OPT:REF /OPT:ICF /INCREMENTAL:NO /debug /INCREMENTAL /subsystem:console  && cmd.exe /C "cd /D F:\test\vcpkg\buildtrees\bullet3\x64-windows-static-dbg\examples\SharedMemory && F:\test\vcpkg\downloads\tools\cmake-3.14.0-windows\cmake-3.14.0-win32-x86\bin\cmake.exe -E copy_if_different F:/test/vcpkg/buildtrees/bullet3/src/2.89-eb26871ed5/examples/ThirdPartyLibs/openvr/bin/win64/openvr_api.dll F:/test/vcpkg/buildtrees/bullet3/x64-windows-static-dbg/examples/SharedMemory/openvr64pi.dll && cd /D F:\test\vcpkg\buildtrees\bullet3\x64-windows-static-dbg\examples\SharedMemory && F:\test\vcpkg\downloads\tools\cmake-3.14.0-windows\cmake-3.14.0-win32-x86\bin\cmake.exe -E copy_directory F:/test/vcpkg/buildtrees/bullet3/src/2.89-eb26871ed5/data F:/test/vcpkg/buildtrees/bullet3/x64-windows-static-dbg/data""
Microsoft (R) Incremental Linker Version 14.25.28612.0

I'm not sure why the files cannot be copied successfully.

Well, yes, that is the issue that needs fixing. b3RobotSimulatorClientAPI_NoGUI  is a crucial part of the easier to use API.

The link error is due to that BUILD_SHARED_LIBS  is disabled in Windows platform. Please see here https://github.com/bulletphysics/bullet3/issues/1794
It will be fixed by the PR https://github.com/bulletphysics/bullet3/pull/2389
So in my opinion, we can continue solving this issue after the link error is fixed by upstream.


Tesla component: Account banned, forced to do password reset

Home Assistant release with the issue:
0.103.3

Last working Home Assistant release (if known):
Unknown
(This has happended twice)
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Integration:

https://www.home-assistant.io/integrations/tesla
Description of problem:
The tesla component spam the API service and forces an account password reset when starting hassio and there intermittent connectivity.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
tesla:
  username: !secret tesla_username
  password: !secret tesla_password

Traceback (if applicable):
2020-01-13 10:45:21 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from x.x.x.x
2020-01-13 10:45:21 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from x.x.x.x

Additional information:

The logs for http.ban are not related to the component. However, this is a duplicate of #29922 which should be resolved in 104.

Duplicate of #29922 which has been resolved by #30217.


--only-show-errors should be added to the docs in the global parameter list

Some individual commands include this option, but according to https://github.com/Azure/azure-cli/issues/6341 the option was added globally. It should be added to the 'Global Parameters' section included in every command documentation

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

ID: eeedb9a7-2aed-6727-4cfb-1515809d676e
Version Independent ID: 2c83180d-22ad-db42-e2eb-f27f11977963
Content: az
Content Source: src/azure-cli/azure/cli/command_modules/profile/_help.py
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

hi @jiasli  pls have a look, thanks

add to S169

This is known issue of doc generation. We are internally working with doc team to fix it. Thanks for your patience.

This issue has been fixed in the doc generation and will go live in next CLI release.


Add student CPO numbers to their profiles

We need to pull a student CPO number from Tracy with all the other student info and display it on the student's profile.

 Add student CPO numbers to their profiles.


feat(ast_tools): Default enums to rename_all = "camelCase"

Part of #6347

#6933  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ottomated and the rest of your teammates on  Graphite

Merge activity

Oct 27, 9:38 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


OmniSharp Agenda » Meeting Thursday October 5th, 2017 @ 18:00 UTC

PST (UTC-8)
EST (UTC-4)
London (UTC+1)
Zürich (UTC+2)
Helsinki (UTC+3)
Sydney (UTC+11)

11:00 AM
2:00 PM
7:00 PM
8:00 PM
9:00 PM
5:00 AM

Meeting info
Join Skype Meeting ( https://meet.lync.com/microsoft/dustinca/RRJCBN81 )
Trouble Joining? Try Skype Web App ( https://meet.lync.com/microsoft/dustinca/RRJCBN81?sl=3D1 )
Join by phone
Toll-free number: +1<PHONE_NUMBER>, access code: 96135890 (Dial-in Number)                   English (United States)
Toll number:         +1<PHONE_NUMBER>, access code: 96135890 (Dial-in Number)                   English (United States)
Find a local number ( https://dialin.lync.com/22f12fa0-499f-435b-bc69-b8de580ba330?id=3D96135890 )
Conference ID: 96135890 (same as access code above)
Forgot your dial-in PIN? ( https://mysettings.lync.com/pstnconferencing ) | Help ( http://go.microsoft.com/fwlink/?LinkId=3D389737 )
Welcome to Skype for Business Online Meetings. All participants who use the Join by Phone option must dial the full number for call access..
Agenda
If you can think of any more agenda items, feel free to edit the issue (if you have permissions) or just comment on this thread and we'll make sure to group them up before the meeting.
Also feel free to discuss any agenda items early as part of this issue, we can make sure to recap during the start of the meeting, and may cut down on the time we have to spend on some of them.
Language Server Protocol

Off of kestrel (by default)
Started work on LSP

OmniSharp-atom

Will most likely sunset this in favor of ide-csharp cc @damieng

OmniSharp-node-client

Once Lsp lands in OmniSharp we may not need to do anything more here.
Are there any other dependencies on this outside atom / lsp that I'm not aware of?

OmniSharp-vscode

Updates? Progress? Goals?
Looking at LSP as a possible option in the future

OmniSharp-vim

Any information / updates?

OmniSharp-emacs

Any information / updates?

cc @OmniSharp/all
Additional agenda items?
Either update the issue, or add them in the comments below!

Added meeting info

unfortuantely due to a last minute issue I will need to skip today 😥

https://github.com/OmniSharp/csharp-language-server-protocol/blob/master/src/Lsp/LanguageServer.cs


LLM (LANGCHAIN GEN AI) folder

Have you read the Contributing Guidelines ?
yes, I do have.
Description
I have added the folder "LLM (LANGCHAIN GEN AI)" under Artificial Intelligence folder. This pack consists of 4 projects in it. The readme file has been provided for the clear guidance.
Fixes #1001

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Any suggestion regarding this contribution is welcomed.

@Kushal997-das, please check the pull request and let me know if change is required.

@Kushal997-das , hey, the project is related to AI. Should I still add it in ML and Data Science folder??

Sure, here's the revised version of the sentence:
@VarsaGupta Things you need to change:

Add your project here.
Provide clear, step-by-step instructions in the README.md file. Make it simple and easy to understand for the user.
Ensure you fetch the updated version of project-guidance.

Please do the required changes

@VarsaGupta Kindly update on this.


api-reference shortcode + links in Concepts/Reference/Taks

This PR adds an api-reference shortcode to create link to the new API reference introduced in https://github.com/kubernetes/website/pull/23294.
The PR also changes links into the Concepts/Tasks/Reference sections from the old API reference to the new API reference.
api-reference shortcode
A shortcode has been created, to help creating links to sections of the API Reference.
Attributes of the shortcode:
page
page indicates the page to link to, by specifying the suffix of the URL after docs/reference/kubernetes-api/:
{{< api-reference page="workloads-resources/container" >}} will create a link to the page https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/reference/kubernetes-api/workloads-resources/container/
anchor
an optional anchor indicates a fragment of the page to point to (the fragment can be the name of a Definition defined in this page, or a section):

link to the ResourceRequirements definition:  {{< api-reference page="workloads-resources/container" anchor="ResourceRequirements" >}} will link to the fragment of the page https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/reference/kubernetes-api/workloads-resources/container/#ResourceRequirements
link to the Entrypoint section: {{< api-reference page="workloads-resources/container" anchor="entrypoint" >}} will link to the fragment of the page https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/reference/kubernetes-api/workloads-resources/container/#entrypoint

text
By default, the text of the link is derived from the name of the linked page. For example, the shortcode {{< api-reference page="workloads-resources/pod-v1" >}} will generate a link with the text Pod.
You can specify the text of the link with the text attribute. For example, the shortcode {{< api-reference page="workloads-resources/pod-v1" text="the Pod resource" >}}  will generate a link with the text the Pod resource.

@feloy , Are you separating out the work from the original PR?

@feloy , Are you separating out the work from the original PR?

@feloy , Are you separating out the work from the original PR?

@kbhawkey I discussed with @sftim, we won't merge now the changes of links from the old to the new API reference, and so I'm saving the changes into another PR.

@feloy , Are you separating out the work from the original PR?

@kbhawkey I discussed with @sftim, we won't merge now the changes of links from the old to the new API reference, and so I'm saving the changes into another PR.

@feloy , Are you separating out the work from the original PR?

@kbhawkey I discussed with @sftim, we won't merge now the changes of links from the old to the new API reference, and so I'm saving the changes into another PR.

Oh, OK. I guess I missed that discussion.

@feloy , Are you separating out the work from the original PR?

@kbhawkey I discussed with @sftim, we won't merge now the changes of links from the old to the new API reference, and so I'm saving the changes into another PR.

Oh, OK. I guess I missed that discussion.

/hold
I / we want to discuss this change with SIG Architecture first. But I really want it to land!

/hold
I / we want to discuss this change with SIG Architecture first. But I really want it to land!

/approve

/approve

Hi @feloy could you please rebase the PR?

Is this PR ready to move forward?
Several of the directory name shortcode parameters need updating.
It would be useful to navigate (and test the navigation) from concept and task pages to the resource pages in the reference section.
If further changes are required, it should be straightforward to remove or update the shortcode.

TBH, I'm still not big fan of the "grouping" of kinds. It is pretty difficult for me to remember that pod-v1 is a workload-resources. I'm not aware of any consensus on how to group them.
{{< api-reference page="workloads-resources/pod-v1" >}}

TBH, I'm still not big fan of the "grouping" of kinds. It is pretty difficult for me to remember that pod-v1 is a workload-resources. I'm not aware of any consensus on how to group them.

I'm going to bring this up at the next SIG Architecture meeting too.

Sorry! Misclicked.
/reopen

TBH, I'm still not big fan of the "grouping" of kinds. It is pretty difficult for me to remember that pod-v1 is a workload-resources. I'm not aware of any consensus on how to group them.
{{< api-reference page="workloads-resources/pod-v1" >}}

Understood. The grouping helps with the left hand nav tree.

Hi @feloy . What is the status of this PR?
@sftim do you have any feedback from SIG Architecture?
Are there other questions and concerns? Should these changes remain held for further discussion?
I'll take another look at the changes.

I think this shortcode is OK to go in.
Separately, it would be good to make the paths to API reference pages reflect the API groups / API paths for the relevant resources. That can be addressed in a completely different package of work.
Sorry for not updating sooner.
/hold cancel

I'm working on the linkchecker.py script to make it check the targets of the {{< api-reference >}} links.

nit: I would prefer to split this into 2 commits

Add the shortcode
Use the shortcode

Separating mechanisms from their use helps localizers spot which changes to adopt.
@feloy I'd be happy to LGTM this if you split it into 2 commits. I'm also open to be persuaded that it's better as just 1 commit.
/hold
but anyone who feels confident that it shouldn't be held, is welcome to /unhold

@sftim I split into 3 commits. The third one is for the modifications to the script checking the api-reference links.

/unhold
Thanks @feloy

Hi @feloy
Can we offer you any help to move this PR forward?

TBH, I'm still not big fan of the "grouping" of kinds.

I think addressing that is really a completely separate issue.

Thanks @feloy!
I'll see about getting this reviewed.

Hi @feloy. Thanks for splitting up the original PR. The changes look okay.
Since this is a new shortcode, what do you think about using this shortcode in the docs test page (/docs/content/en/docs/test.md) or adding the shortcode to one of the shortcode contrib pages (/docs/content/en/docs/contribute/style/hugo-shortcodes/index.md)?

Page preview:
https://deploy-preview-26151--kubernetes-io-main-staging.netlify.app/docs/contribute/style/hugo-shortcodes/#links-to-api-reference

Thanks @feloy .
Let's get the shortcode and link checker additions pushed in.
/lgtm


Footer - Need Help icon missing at bottom right corner of footer

https://athletex.atlassian.net/browse/AX-645
Environment
Device model: All
OS version: All
Software version: All
Browser version: All
Stage: All
Account: N/A
Precondition
Given, user has gone to the website
Steps to reproduce
Go to AthleteX dApp
Scroll down to footer and you will see Need Help icon is missing compare to design
Current behavior
Currently, Need Help icon is missing at bottom right corner of footer
Expected behavior
Need Help with help text popup should appear as per design

@pearlson16 was this completed?


fix: added bugfix for date parsing in datepicker widget 2

Description
There was a bug in the parseDate method of the Datepicker widget component where we were not passing the date format correctly, which resulted in resetting of date values to today's date whenever the user types in the date input.
Fixes #11837
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Added a unit test for parseDate function
Manually

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
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: fix/datepicker-resets-today-11837-2

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
app/client/src/utils/WorkerUtil.ts
88.98 (-0.78)
70.59 (-1.96)
100 (0)
92.38 (-0.95)

:green_circle:
app/client/src/widgets/DatePickerWidget2/component/index.tsx
30 (2.22)
3.08 (0.09)
6.25 (0)
28.99 (1.85)

:sparkles: :new:
app/client/src/widgets/DatePickerWidget2/component/utils.ts
85.71
50
100
80

:sparkles: :new:
app/client/src/widgets/DatePickerWidget2/widget/constants.ts
100
100
100
100

/ok-to-test sha=3f0450e

/ok-to-test sha=3f0450e

/ok-to-test sha=d5afbd4

/ok-to-test sha=d5afbd4

/ok-to-test sha= a20cabf

/ok-to-test sha=a20cabf

@ankurrsinghal Tested and working fine.


no log messages received

I installed the CEF-plugin using the .deb-package, restarted graylog and defined a new input. However, no matter if I am using UDP or TCP, no logmessages are shown in graylog, although tcpdump is showing traffic, netstat shows, that the port is open. I entered 2 syslog-servers into the device I want to get the messages from, 1 points to the CEF-input, the other points to a raw-input.
In the graylog-server.log I can just see complains about the raw-message, but no other message regarding the CEF-plugin.
2016-09-08T21:34:31.211+02:00 ERROR [DecodingProcessor] Error processing message RawMessage{id=438f88a0-75fb-11e6-a200-0050569e73a3, journalOffset=128801836, codec=CEF, payloadSize=672, timestamp=2016-09-08T19:34:31.210Z, remoteAddress=/<IP_ADDRESS>:47863}
I have no idea how to look further.
Kind regards,
Mira
I am using graylog 2.1

Hi,
no I got some error messages:
2016-09-09T13:04:45.969+02:00 ERROR [DecodingProcessor] Unable to decode raw message 37bfb900-767d-11e6-a200-0050569e73a3 (journal offset 128832740) encoded as CEF received from /<IP_ADDRESS>:47863.
2016-09-09T13:04:45.969+02:00 ERROR [DecodingProcessor] Error processing message RawMessage{id=37bfb900-767d-11e6-a200-0050569e73a3, journalOffset=128832740, codec=CEF, payloadSize=672, timestamp=2016-09-09T11:04:45.968Z, remoteAddress=/<IP_ADDRESS>:47863}
org.graylog.plugins.cef.parser.CEFParser$ParserException: This message was not recognized as CEF and could not be parsed.
at org.graylog.plugins.cef.parser.CEFParser.parse(CEFParser.java:71) ~[?:?]
at org.graylog.plugins.cef.codec.CEFCodec.decode(CEFCodec.java:59) ~[?:?]
at org.graylog2.shared.buffers.processors.DecodingProcessor.processMessage(DecodingProcessor.java:143) ~[graylog.jar:?]
at org.graylog2.shared.buffers.processors.DecodingProcessor.onEvent(DecodingProcessor.java:86) [graylog.jar:?]
at org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(ProcessBufferProcessor.java:58) [graylog.jar:?]
at org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(ProcessBufferProcessor.java:35) [graylog.jar:?]
at com.lmax.disruptor.WorkProcessor.run(WorkProcessor.java:143) [graylog.jar:?]
at com.codahale.metrics.InstrumentedThreadFactory$InstrumentedRunnable.run(InstrumentedThreadFactory.java:66) [graylog.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
The message which could not be recognized as CEF was this:
<158>CEF:0|Trend Micro|Deep Discovery Inspector|3.83.1170|1537|Unsuccessful logon to Kerberos|4|dvc=<IP_ADDRESS> dvcmac=aa:bb:cc:dd:ee:ff dvchost=host deviceExternalId=234234234-56456456-234243423 rt=Sep 09 2016 12:22:53 GMT+02:00 app=KERBEROS deviceDirection=1 dhost=host2 dst=<IP_ADDRESS> dpt=23423 dmac=ff:ee:dd:cc:bb:aa shost=host3 src=<IP_ADDRESS> spt=88 smac=ab:cd:ef:fe:dc:ba fileType=-65536 fsize=0 act=not blocked cn3Label=Threat Type cn3=2 destinationTranslatedAddress=<IP_ADDRESS> sourceTranslatedAddress=<IP_ADDRESS> suid=user cnt=4 cat=Authentication cs6Label=pAttackPhase cs6=Lateral Movement flexNumber1Label=vLANId flexNumber1=1111
Hope this helps any further.
Kind regards,
Mira

I'm having the same issue with Graylog 2.1.1+01d50e5, OSSEC 2.8.3 and latest release of this plugin on CentOS 6 boxes.  Exact same errors.  Any help troubleshooting would be great. I've done the same verification as the poster and am using a CEF UDP input.  Tcpdump shows the traffic is reaching the server just fine, but the plugin fails to recognize the message as CEF.
2016-10-05T05:12:24.158-05:00 ERROR [DecodingProcessor] Unable to decode raw message 35d2e8d1-8ae4-11e6-b3b7-1262a9e4007f (journal offset 262713) encoded as CEF received from /<IP_ADDRESS>:45205.
2016-10-05T05:12:24.158-05:00 ERROR [DecodingProcessor] Error processing message RawMessage{id=35d2e8d1-8ae4-11e6-b3b7-1262a9e4007f, journalOffset=262713, codec=CEF, payloadSize=318, timestamp=2016-10-05T10:12:24.157Z, remoteAddress=/<IP_ADDRESS>:45205}
org.graylog.plugins.cef.parser.CEFParser$ParserException: This message was not recognized as CEF and could not be parsed.
at org.graylog.plugins.cef.parser.CEFParser.parse(CEFParser.java:71) ~[?:?]
at org.graylog.plugins.cef.codec.CEFCodec.decode(CEFCodec.java:59) ~[?:?]
at org.graylog2.shared.buffers.processors.DecodingProcessor.processMessage(DecodingProcessor.java:143) ~[graylog.jar:?]
at org.graylog2.shared.buffers.processors.DecodingProcessor.onEvent(DecodingProcessor.java:86) [graylog.jar:?]
at org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(ProcessBufferProcessor.java:58) [graylog.jar:?]
at org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(ProcessBufferProcessor.java:35) [graylog.jar:?]
at com.lmax.disruptor.WorkProcessor.run(WorkProcessor.java:143) [graylog.jar:?]
at com.codahale.metrics.InstrumentedThreadFactory$InstrumentedRunnable.run(InstrumentedThreadFactory.java:66) [graylog.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101]
Thanks,
Jay

Same issue here, trying to send in CEF logs from OSSEC v2.9R3, and from auditd using the audisp-cef plugin. Both give the "This message was not recognized as CEF and could not be parsed." message.

@lennartkoopmann  The 1.1.1 release fixed this issue for me.  My guess is it was the additional whitespace cause it to not recognize the message as valid DEF.  Sweet!!  Thanks
Jay

Hi,
unfortunatly version 1.1.1 was not helpful for me, I am still getting this error:
org.graylog.plugins.cef.parser.CEFParser$ParserException: This message was not r                                                     ecognized as CEF and could not be parsed.
at org.graylog.plugins.cef.parser.CEFParser.parse(CEFParser.java:71) ~[?                                                     :?]
at org.graylog.plugins.cef.codec.CEFCodec.decode(CEFCodec.java:59) ~[?:?                                                      I don't want to encapsulate my logs in syslog - I want them to be transported in CEF format but instead these bungholes over at Trend give me CEF via Syslog... Anyways, I'm in the same boat as everyone else. Now, I just read in this plugin's readme file that I can fix it with a preprocessor rule. Obviously that's the road I'll need to travel but on a Thurday night when I'm already working late and need to get home this doesn't sound like a quick task. So thank you Trend Micro.

Same problem . Any solution for this problem?

I am in the same boat. It would be helpful to maybe show us how we could use the pipeline feature since I gave it a try and obviously am not using the parse_cef function correctly. I think we are all in the same boat here.

Please post an example message and the rule you are trying to run on it and I can help.

hello
the cef message:
Apr 26 10:00:41 CEF:0|Trend Micro Inc.|OSSEC HIDS|v2.9.0|30315|Invalid URI (bad client request).|5|dvc=ossec2-9
cs2=ossec2-9->/var/log/apache2/error.log cs2Label=Location classification= apache,invalid_request,
src=<IP_ADDRESS> spt=46160 shost=<IP_ADDRESS> cs3Label=SrcCity cs3=RFC1918 IP msg=[Wed Apr 26 10:00:39.401335 2017]
[core:error] [pid 29766:tid<PHONE_NUMBER>95104] [client <IP_ADDRESS>:46160] AH00126: Invalid URI in request GET . HTTP/1.0
and i use the graylog-plugin-cef, nothing more !
thanks

@marcRBD You have to extract the CEF string out of the message (the message is not CEF format compliant) in a pipeline and then run the parse_cef function over the extracted String to add all the fields to your message with set_fields().
The CEF string is this:
CEF:0|Trend Micro Inc.|OSSEC HIDS|v2.9.0|30315|Invalid URI (bad client request).|5|dvc=ossec2-9
cs2=ossec2-9->/var/log/apache2/error.log cs2Label=Location classification= apache,invalid_request,
src=<IP_ADDRESS> spt=46160 shost=<IP_ADDRESS> cs3Label=SrcCity cs3=RFC1918 IP msg=[Wed Apr 26 10:00:39.401335 2017]
[core:error] [pid 29766:tid<PHONE_NUMBER>95104] [client <IP_ADDRESS>:46160] AH00126: Invalid URI in request GET . HTTP/1.0

I'm see this issue too. According to the latest ArcSight CEF guide the proper header format for CEF is:
Jan 18 11:07:53 host CEF:Version|Device Vendor|Device Product|Device Version|Device Event Class ID|Name|Severity|[Extension]
Here is a copy of a log from one of my honeypots:
2017-08-31T20:31:26.325068 CEF:0|ThreatStream|MHN|1.0|dionaea.connections|Connection to Honeypot|10|deviceDirection=0 cs2=network cs2Label=ids_type cs3=dionaea cs3Label=app src=xxx.xxx.xxx.xxx cs1=Dionaea cs1Label=vendor_product dpt=1433 spt=4579 dst=xxx.xxx.xxx.xxx proto=tcp
If your plugin is only looking at the log starting at CEF:0 then that is incorrect. It should be looking for the timestamp and host as well.

I have a Fortinet FortiGate firewall and couldn't get it to work either. The firewall sends the CEF messages in the format mentioned by @hackdefendr. The currently used regex definitely does not work with Syslog envelopes/CEF headers containing a hostname or IP address.
https://github.com/graylog-labs/graylog-plugin-cef/blob/0bcb91c628ae07c54c3ff7d98f54e6e536259a0a/src/main/java/org/graylog/plugins/cef/parser/SyslogCEFParser.java#L22
I made the following changes to the current regex for better compliance to RFC 3164.
^(?:<\\d+>)?([a-zA-Z]{3}\\s+\\d{1,2} \\d{1,2}:\\d{1,2}:\\d{1,2}) (?:\\p{Graph}+)? ?(CEF:.+)$

Shouldn't be much different performance-wise, but can propably be improved. Works with all currently supported formats and the one specified in the ArcSight CEF Guide.

Please give the latest version of the plugin a try (depending on your Graylog version):

2.2.0-beta.1 (for Graylog 2.2.x)
2.3.0-beta.1 (for Graylog 2.3.x)

You might have to re-create your CEF input depending on your message sources, e. g. a "CEF TCP/UDP input" for ArcSight instead of a "CEF Syslog TCP/UDP input".
While not all issues are fixed, these new releases might work better for you than the old ones.

My graylog is v2.3.1 and will not start with graylog-plugin-cef-2.3.0-beta.1.jar in the plugins folder.

@hackdefendr This has been fixed in version 2.3.0-beta.2.

Confirmed beta2 fixes the startup issue.

The message parsing does still not work for me in the new versions. I'm pretty sure it's because the Syslog parser always looks for the priority part (<\\d+>) of the message as in the RFC.
The log messages though have the following format (captured with nc):
Sep 21 17:07:40 hostname CEF:0|Fortinet|Fortigate|v5.6.2|00015|traffic:forward start|3|FTNTFGTlogid=0 cat=traffic:forward FTNTFGTsubtype=forward FTNTFGTlevel=notice FTNTFGTvd=root FTNTFGTlogtime=0 src=<IP_ADDRESS> spt=0 deviceInboundInterface=x FTNTFGTsrcintfrole=x dst=<IP_ADDRESS> dpt=0 deviceOutboundInterface=x FTNTFGTdstintfrole=undefined FTNTFGTpoluuid=x externalId=0 proto=0 act=start FTNTFGTpolicyid=0 FTNTFGTpolicytype=policy app=HTTPS FTNTFGTdstcountry=United States FTNTFGTsrccountry=Reserved FTNTFGTtrandisp=snat sourceTranslatedAddress=<IP_ADDRESS> sourceTranslatedPort=0 FTNTFGTduration=0 out=0 in=0 FTNTFGTsentpkt=0 FTNTFGTappcat=unscanned

I think they implemented it according to the example in the ArcSight guide and therefore it's not strictly following the RFC for the Syslog header.

@githubuserx That's not syslog. Syslog messages always start with the priority field (<\\d+>), see https://tools.ietf.org/html/rfc3164 and https://tools.ietf.org/html/rfc5424.

Sep 21 17:07:40 hostname CEF:0|Fortinet|Fortigate|v5.6.2|00015|traffic:forward start|3|FTNTFGTlogid=0 [...]

If that line is exactly what's going over the wire, you have to use a Raw (Plaintext) CEF input.

I just tried again all different types of CEF inputs without success and seems obvious to me that it can't work with the current regex in both parsers, since the raw CEF input can only start with whitespace characters (^\\s*).
I know that it's not Syslog, but it seems to be the same header execpt the priority part. I could use pipelines to extract only the (CEF:[...]) part but then I'd lose the header information. Since the CEF guide explicitly mentions the format as the "Syslog" header for CEF messages I thought it would be nice to support this format directly in the parser.
Excerpt from the ArcSight Guide PDF, page 5:

So I think they intended to omit the priority prefix of the Syslog header and still called it Syslog.
Best regards

Next plugin iteration:

https://github.com/Graylog2/graylog-plugin-cef/releases/tag/2.2.0-beta.2
https://github.com/Graylog2/graylog-plugin-cef/releases/tag/2.3.0-beta.3

And even more (only fixes AMQP and Kafka CEF inputs):

https://github.com/Graylog2/graylog-plugin-cef/releases/tag/2.2.0-beta.3
https://github.com/Graylog2/graylog-plugin-cef/releases/tag/2.3.0-beta.4

Just tested the latest version and it seems to work perfectly so far 👍 - thank you for the effort!

as this looks solved, i'll close this.
If you do not feel, please reopen the issue.


Add to readme

Added install instructions and resources to Readme.

Thanks @laras126 — you're the best!


Capture TEENY when looking for first 2.3+ Ruby

Otherwise, we would try to install '2.3', which may be newer than
the one pre-installed on the image. This is kind of OK on Ruby jobs,
because we install whatever the alias 2.3 resolves to, but on non-Ruby
jobs, this causes the addon to fail entirely.

TESTED https://staging.travis-ci.org/BanzaiMan/travis_staging_test/jobs/730688#L92


Gradle plugin unconditionally assumes that a clean tasks exists

In
https://github.com/jreleaser/jreleaser/blob/e4a487d85d5901bf2b46b45cc46cbcf8f512dd33/plugins/jreleaser-gradle-plugin/src/main/groovy/org/jreleaser/gradle/plugin/internal/JReleaserProjectConfigurer.groovy#L78-L88
a cleantask is (re-)configured to close the logger. However, when applying the JReleaser plugin (for ChangeLog generation only) to the root project (of a multi-project with multiple application projects), no clean task exists.
Is this code even legit? Why should the logger (only) be closed if the clean task is executed?

I was under the impression such task is always there as it's very likely that a root project includes a base plugin that provides the task, even if the root has no sources at all.

Well, all I can say is that in a build file like this no clean task is available.

I don't know what you were expecting to gain with this remark.

I was simply wondering whether, instead of fixing the code to not assume the clean task to exist, the code could simply be removed.

More context https://github.com/jreleaser/jreleaser/issues/1074

Thanks.

I was simply wondering whether, instead of fixing the code to not assume the clean task to exist, the code could simply be removed.

Then I'd suggest you lead with more explanation as you just did instead of what you wrote on the first message.
Clarity always wins.

And no, the code cannot be removed. The logger must be closed no matter what otherwise a file descriptor will be left open on Windows, leading to other problems.
What could happen is adding a check for the existence of a clean tasks but IIRC that is what the Gradle API offers by registering a lazy action matching tasks by name.


floydhub acces

Hi! Floydhub just updated and now the cpde provided to run the notebook on floydhub does not work

Closing this as we are not using Floydhub anymore.


Fix link to grid staggering

The link is currently broken as the documentation uses IDs for sections.

Change to #gridStaggering to make it work again.

link name has a typo too:
"starrering" instead of "staggering"


Does it support any integration with Alamofire?

Hello there,
I am trying to implement SSL pinning for my project but I couldn't manage to work on Alamofire. Can I use this with Alamofire lib. or do you have some experience? Thanks for your help!

Alamofire comes with its own SSL pinning mechanism but I think it is also possible to use GCXTrustPolicy for pinning.
You will have to create a SSL pinning policy (e.g. Certificate/ Public Key / ... ) and perform your remote call. Then, on authentication challenge, validate the remote trust against your previously defined policy.
Refer the readme for more details: https://github.com/grandcentrix/GCXTrustPolicy/blob/master/README.md


[Monitor] Enable AI for web app

Details in https://github.com/Azure/azure-cli/issues/14789
Commands:
az monitor app-insights component connect-webapp –ids resource-id-for-webapp --enable-profiler false --enable-snapshot-debugger
az monitor app-insights component connect-webapp -g rg -n myApp --enable-profiler --enable-snapshot-debugger

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Monitor


Support *args in component callbacks

closes #18
I think this works pretty well, but I want to write some more tests tomorrow when my brain works to be sure.

tests are fine


documentation

Hello,
Could there be some examples of usage somewhere, starting from an already generated compile_commands.json ? (especially since headerdb doesn't exist anymore).
Thanks !

The absence of documentation is on purpose for now, as things move and will continue to move, sorry about that.
If you want a header database, at the moment the solution, I will demonstrate the use with irony-server, a simple CMake-project.
pip install --user compdb
compdb version
git clone git@github.com:Sarcasm/irony-mode.git
cd irony-mode/server
mkdir build
cd build
cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON ..
cd ..
cat <<'EOF' > .compdb                                                                                (master)
[compdb]
build-dir = build/
complementers = headerdb
EOF
compdb update
compdb list >compile_commands.json

Thanks a lot, this is working well, even on a big project. Still can't make YCM work with headers added anyway, I'll investigate further.

What do you mean by "header added"?

I mean the compile_commands.json that now includes every header of my project. YCM still can't do completion on code inside headers, but this is another issue I guess.

Ok, don't hesitate to tell me about this issue if you understand it, this is something headerdb is trying to solve, any edge cases interest me.

No problem, I'll post the solution if I find it :)

For starter, you can do something like:
$ compdb list path/to/my/header.h
[
      { "directory": ....
....
]

Copy-paste the compile command, change the compiler to Clang if that's not already the case see if that compiles.

Why is there not something extremely simple like doing
$ compdb path/to/compile_commands.json > path/to/compile_commands_with_headers.json

Because there is an explicit "index" step right now, and because auto-detection of the main compilation database is not yet implemented.
However, I agree this should the be goal.

Apologies for my ignorance, but when you talk about the "main" compilation database, are you suggesting one can have a hierarchy of databases? All I've seen in practice is a single JSON file being generated by pretty much every build tool out there. Also, nice job on this project!

I meant the initial database generated by the build tool.
However, I refrained talking about this, but one of the goal of compdb may also to aggregate compilation databases.
For example, in the ROS community. they have one build directory per CMake project, but a workspace is composed of multiple CMake projects.
It is sometime convenient to see the workspace as one thing, and compdb can concat the compilation databases into one.

Just FYI, in the latest commit I have reworked/simplified a few things, hopefully it will be a saner base for futur development.
I will now try to maintain a section in the README to explain how to generate a compilation database for headers:

https://github.com/Sarcasm/compdb#generating-a-compilation-database-including-header-files

@rwols:
I have implemented a simple usage as you recommended, here is how you can generate a compilation database with headers:
compdb list -p build/ > path/to/compile_commands_with_headers.json


[TW#28664] SDKCONFIG variables marked as error in Eclipse IDE

I'm using Ubuntu and after following all the steps given in Build and Flash with Eclipse IDE everything is OK and I'm able to build and flash my projects properly.
But there is an issue that is bothering me. The case is that eclipse does not find all the "variables" defined in "sdkconfig" file and so, shows as if my project is full of errors:

Is there any way to solve that?
Thanks!

Can you please right click the source file in project tree, and use "Create parser log file" option (somewhere under Index), then attach the file here?
Also, if you add #include "sdkconfig.h" to your source file, and then control-click on the include line, does it open the correct sdkconfig.h file (of the project you are working with)?

Thanks @igrr .
I solve that issue adding this include path:


⚠ SceneTime has degraded performance

In 3a3e477, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3141 ms

Resolved: SceneTime performance has improved in 971b9cd after 9 minutes.


Bug 1910459: redeploy CSI Controller Deployment when secret changes

This PR uses changes from https://github.com/openshift/library-go/pull/976 to redeploy the Controller Deployment when the secret changes.
CC @openshift/storage

/hold cancel

/hold cancel

/hold
https://github.com/openshift/library-go/pull/976 needs to be reviewed/approved/merged first.

/hold
https://github.com/openshift/library-go/pull/976 needs to be reviewed/approved/merged first.

/hold cancel
openshift/library-go#976 has been merged.

/hold cancel
openshift/library-go#976 has been merged.

/refresh

/refresh

@openshift/storage PTAL

@openshift/storage PTAL

/refresh

/refresh

/retest

/retest

/retest

/retest

/retest

/retest

/refresh

/refresh

E0114 13:21:32.061339   94245 test_context.go:485] Failed to setup provider config for "gce": Error building GCE/GKE provider: unexpected response listing zones: googleapi: Error 403: Quota exceeded for quota group 'ListGroup' and limit 'List requests per 100 seconds' of service 'compute.googleapis.com' for consumer 'project_number:1053217076791'., rateLimitExceeded
/test e2e-gcp

E0114 13:21:32.061339   94245 test_context.go:485] Failed to setup provider config for "gce": Error building GCE/GKE provider: unexpected response listing zones: googleapi: Error 403: Quota exceeded for quota group 'ListGroup' and limit 'List requests per 100 seconds' of service 'compute.googleapis.com' for consumer 'project_number:1053217076791'., rateLimitExceeded
/test e2e-gcp

/lgtm

/lgtm


Ability to view Helm Charts deployed by YAML manifest with helm CLI

Is your feature request related to a problem? Please describe.
Yes, cannot use the helm CLI to view Helm Charts that were deployed using a HelmChart manifest. For example, if I put this file in /var/lib/rancher/k3s/server/manifests -
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: cert-manager
  namespace: kube-system
spec:
  chart: cert-manager
  repo: https://charts.jetstack.io
  targetNamespace: cert-manager
  version: v0.9.1

It will deploy the cert-manager helm chart. But if I run this in the helm CLI, I don't see it:
root@ip-10-0-11-20:~# helm list -a --all-namespaces
NAME                	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART          	APP VERSION
root@ip-10-0-11-20:~#

Tested with helm 3.0.0:
root@ip-10-0-11-20:~# helm version
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

Describe the solution you'd like
Would be nice to if you can run helm list and helm status commands against k3s when deployed with a k3s helm chart manifest. Might also be nice to include the helm binary in a similar fashion to how kubectl and crictl are included.

I've verified this using k3s v1.18.9+k3s1. I used both the helm chart above and another random one:
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: grafana
  namespace: kube-system
spec:
  chart: stable/grafana
  targetNamespace: monitoring
  set:
    adminPassword: "NotVerySafePassword"
  valuesContent: |-
    image:
      tag: master
    env:
      GF_EXPLORE_ENABLED: true
    adminUser: admin
    sidecar:
      datasources:
        enabled: true

Neither show up using helm list -a -A. The chart for traefik does show up, however, as this is one of the default charts with k3s. More details of commands run and their results below:
$ k get pods -A
NAMESPACE     NAME                                     READY   STATUS              RESTARTS   AGE
kube-system   coredns-7944c66d8d-5dmzs                 0/1     Running             0          22s
kube-system   helm-install-grafana-88sxl               1/1     Running             0          22s
kube-system   local-path-provisioner-6d59f47c7-jk8js   1/1     Running             0          22s
kube-system   metrics-server-7566d596c8-qnpln          1/1     Running             0          22s
kube-system   traefik-758cd5fc85-zhn4b                 0/1     ContainerCreating   0          2s
kube-system   svclb-traefik-b85xx                      0/2     ContainerCreating   0          2s
kube-system   helm-install-traefik-d96gc               0/1     Completed           0          22s

$ helm list -a -A
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
NAME   	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART         	APP VERSION
traefik	kube-system	1       	2020-10-14 15:13:44.820636261 +0000 UTC	deployed	traefik-1.81.0	1.7.19

I don't know how Helm finds things to display in the list, but the packaged Traefik chart and the user chart from your example end up deployed the exact same way.
@rancher-max I see that your helm-install-grafana pod is still Running, not Completed. That means the Helm chart isn't done installing yet. Can you give it a little longer, and confirm your helm list output AFTER the install pod is done running?

Helm looks for owner=helm label on secrets when running a list:
# helm list -a -A -v=6
I1014 23:35:36.234691  706174 loader.go:375] Config loaded from file:  /etc/rancher/k3s/k3s.yaml
I1014 23:35:36.239524  706174 loader.go:375] Config loaded from file:  /etc/rancher/k3s/k3s.yaml
I1014 23:35:36.257633  706174 round_trippers.go:443] GET https://<IP_ADDRESS>:6443/version?timeout=32s 200 OK in 3 milliseconds
I1014 23:35:36.258304  706174 loader.go:375] Config loaded from file:  /etc/rancher/k3s/k3s.yaml
I1014 23:35:36.275689  706174 round_trippers.go:443] GET https://<IP_ADDRESS>:6443/api/v1/secrets?labelSelector=owner%3Dhelm 200 OK in 16 milliseconds

The kubectl equivalent of the GET https - kubectl get secrets -A -l owner=helm

This looks to be working in both k3s v1.18.9 and the default installation of v1.19.13 in both centos and ubuntu. I also tried helm v3.0.0 and the current available version via snap of v3.4.1.
I installed certmanager chart using:
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: cert-manager
  namespace: kube-system
spec:
  chart: cert-manager
  repo: https://charts.jetstack.io
  targetNamespace: cert-manager
  version: v1.1.0

I had to also run kubectl create namespace cert-manager for this after installing k3s, but then it installed successfully and was available to helm:
$ helm list -a --all-namespaces
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /etc/rancher/k3s/k3s.yaml
NAME        	NAMESPACE   	REVISION	UPDATED                                	STATUS  	CHART              	APP VERSION
cert-manager	cert-manager	1       	2020-11-30 17:45:03.328403456 +0000 UTC	deployed	cert-manager-v1.1.0	v1.1.0
traefik     	kube-system 	1       	2020-11-30 17:44:08.584097278 +0000 UTC	deployed	traefik-1.81.0     	1.7.19

I'm going to close this out for now, but if it's noticed again, maybe it's something to do with versions of the charts deployed and not getting the secret label correctly populated as mentioned above.