date format 'mm/dd/yyyy' always yields '10' for day values between 13 and 19

$input.inputmask("mm/dd/yyyy").val('10/19/2017');

Currently yields "10/10/2017".
Introduced in 3.3.8, works correctly in 3.3.7.

I have a similar issue in yii2 input mask. Please post your solution if you issue has been resolved thanks in advance

@oliverlangan ,  @ignatiusabraham ,
See https://github.com/RobinHerbots/Inputmask/projects/1

@RobinHerbots I'm interested in working on this issue. However, could you provide instructions about running the tests? When I npm install and then npm run test it fails due to errors and warnings in the eslint step. I tried running just grunt karma, but that shows 9 test failures. Figure I must be missing a build step (although I tried grunt build to no avail).

Hi @rmulhol ,
Don't worry about the 9 failures, those are issues yet to be resolved.
Are you interested in only solving the issue or in the new datetime project?
For the issue, you need to work on the 3.x branch, for the new datetime you use the 4.x branch.
Anyway, it would be great because I don't have much time free to spend.

This is fixed in the 3.x branch.  It was due to a pull request.  I reverted it. I will releasee 3.3.10 today or tomorrow.

@oliverlangan ,
Have a try with version 3.3.10

@RobinHerbots, verified fixed with 3.3.10. Thanks!


[CTD-264] create Vyos build

Vyos build required following changes:

Adjusted versions of package dependencies to match Vyos (Debian 6 level)
Added dependency on cron (which was CTD-205 but applies to Vyos as well)
updated build.sh to make 32 and 64 bit Debian builds using "etch" binaries
updated build.sh to allow a "tag" so we can have Debian packages with the same Debian architecture but different daemons inside to accommodate older OS

I have tested the 64-bit package on a Vyos AWS EC2 instance.
Checked interactive installer, bulk registration, and bulk scripting.

I undid the changes adding support for the Sys-V scripts so those are gone.
Vyos startup for bulk reg will use the Vyos-specific script as described in CTD-264.  I also got rid of the repetitive "tag" declaration but I don't know that it improved readability of the code.


Zoom box is not working in GHEtool v2.2.0

On the result page of GHEtool, the controls of the figure do not work properly.
This is related to https://github.com/tblanke/ScenarioGUI/issues/164 but it goes further within GHEtool. The zoombox, which is working within ScenarioGUI itself, does not seem to be working within GHEtool.

With matplotlib version 3.7.2 this function works. So I think this is an matplotlib issue.

Hi @tblanke
I think this indeed a problem of matplotlib ...
Best,
@wouterpeere


Error parsing YAML config

On Ubuntu 17.10 with the latest binary (22 Jan)(https://storage.googleapis.com/container-structure-test/latest/container-structure-test)
Using one of the config files in this repo (https://github.com/GoogleCloudPlatform/container-structure-test/blob/master/tests/debian_test.yaml)
The following command:
container-structure-test -test.v -image ubuntu:16.04 debian-test.yml
Returns the following error:
2018/02/22 17:48:51 Error parsing config file: Please provide valid JSON or YAML config file

umm the file name is in correct? should it be debian-test.yaml?

Yeah we should support .yml since that's also a valid YAML file extension

Yes I can confirm that using "yaml" works


when compiling i get

raylib/src/rcore.c:4955:22: error: ‘eglGetProcAddress’ undeclared (first use in this function)
4955 |     rlLoadExtensions(eglGetProcAddress);
|                      ^~~~~~~~~~~~~~~~~

i fixed it i needed to add
#include "external/glfw/src/internal.h"  // Adds eglGetProcAddress
to rcore.c
just put that line of code under
#include "raylib.h"                 // Declares module functions

i am now closing this issue


Column Ordering (DnD) not working on mobile device

material-react-table version
2.13.0
react & react-dom versions
18.1.0
Describe the bug and the steps to reproduce it
Column Ordering (DnD) is working properly on PC but on mobile i can't drag  & drop
Even in the documentation example on mobile it reproduce the same problem
Minimal, Reproducible Example - (Optional, but Recommended)
documentation example
Screenshots or Videos (Optional)
.
Do you intend to try to help solve this bug with your own PR?
None
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

duplicate of #577


Refreshed tokens?

How does one use the updates from #19  to request a new token?  It seems that OAuth2 isn't fully supported if token refresh isn't working.  There's no mention of refreshing token in the Readme.

@sxalexander this supports usage with refresh_tokens (mislabelled PR, sorry) & OAuth2 as a wrapper. I am working on integrating something that does the following: also takes in client_secret, then POSTS with necessary post_data (refresh_token, client_id, client_secret, and grant_type) to '/oauth2/token' and returns the json response. Locally, I have a cron job sending the requests which you might consider in the meantime (not sure when this will happen).

thanks @memmott, I thought perhaps I was missing something.  It sounds like there's not a way to do this currently using the library.  I'll handle it using a requests based workflow for now

In the move to support Harvest API v2, the authentication paradigm has been refactored. Currently supports two types of OAuth2 flows and in one of them supports refreshing tokens.


Control over writing behavior

There should be a dropdown on the Dialog properties to select different style of writing behavior (e.g. Write Immediate, Write Slowly, Fade In, ...).
Ideally, you could add new types of writer by creating a new class which implement a SayWriter interface.

Added in a previous version of Fungus


health_check: active healthchecking thundering herd during cluster warming

Title: health_check: active healthchecking during warming scalability concern
Description:
This issue is partly a theoretical issue as i've not yet directly observed issues this as a cause of issues, but i have seen it exacerbate existing ones. However, I believe it is possible for it to cause issues directly
In troubleshooting an active healthchecking issue, I noticed that jittering healthchecks does not apply to the initial healthchecks for cluster warming. In steady-state this is not an issue, but during startup or restart, this causes a pretty significant amount of healthcheck traffic.
Given that Envoy restarts are often correlated in time (e.g. a fleet restart), and that endpoints are frequently colocated with other endpoints, this can cause a thundering herd of healthcheck traffic against single servers.
My immediate thought is to allow for jittering cluster warmup checks. However, the tradeoff here would be that startup would take some time before clusters are marked healthy. (In fact, I believe this is what HAProxy does).
Perhaps we can have another two parameters. Something like unchecked_interval (is it really an interval?) and have this respect interval_jitter_percent. The difference here is that the base_time_ms would be 0 I think.
CC: @julia-stripe

Yeah I think it's fine to add optional jitter to the initial HC round for a cluster, with the caveat that startup itself might take longer. I would start here, but for larger clusters you might also need to program the ability for a subset of hosts to respond to the first check before continuing with init...

This may be contributing to an issue we're currently seeing with Envoy where sometimes we see upstream connect error or disconnect/reset before headers errors when a cluster changes size. My belief about what's happening is:

we add / remove a host from a cluster with many clients
when the new cluster is being warmed, CPU load increases significantly, presumably because many TLS connections are being established
some connections fail to be established, leading to that error message (?)

I'm not 100% sure that's what's happening but that's my current hypothesis.

@julia-stripe, I wasn't able to repro what you are describing, which (correct me if i'm wrong) seems to be that it re-healthchecks all the endpoints in the cluster when an endpoint is added. I had a cluster where I added an endpoint and only the new endpoint is healthchecked. Skimming https://github.com/envoyproxy/envoy/blob/master/source/common/upstream/upstream_impl.cc, this seems to be consistent with what I am seeing.
@mattklein123, the subsetting thing you are describing relates to my proposal in #4280. If the healthchecking is delegated to endpoint rather than the cluster, then we could have the cluster warming consist just of adding the references to endpoints, which may or may not have been healthchecked. As they become healthchecked, they enter the loadbalancing set. This would simplify the CDS update logic as well. Am i missing something?
I've also been running more tests with HAProxy (our current system) and it appears that they initially will route to the endpoints before the first healthcheck. This isn't documented AFAIK, but it is discussed on this thread. This is an interesting approach, and one that might be worth discussing. I'm honestly not sure what the "right" approach is.

@julia-stripe i think i misunderstood what you were saying. You're saying that adding a new endpoint to the clusters causes all the envoy clients to connect to it at the same time.
I definitely see this and it definitely is a problem

Will switch this to help wanted since I do think adding initial health checking jitter makes sense, though the implementation definitely needs some thinking.


Step Input Control - Resizing Not Supported

Hi everyone,
The Step Input control currently cannot be resized. To address this issue, I have opened a new Pull Request that introduces the ability to adjust its size. You can find the PR here: #1222.
Please review the changes and let me know if any modifications or additional information are needed.
Currently, the Step Input looks like this (in Demo 041):

After the change, we will be able to have something like this:

Thank you for your time and consideration.
Best regards,
Francisco Milán

good idea! thank you!


Marshmallow problems

Hi everyone,
I tried to use this library to stream camera and mic recording via rtsp but so far I haven't found a single config working.
I tried nearly all fixes I found on the net and none of them worked. I have a
Huawei Honor 5X with Android 6.0.1 and I'm trying to record at SD/720p/1080p at 30fps/24fps at 3/1 Mbps with MODE_MEDIACODEC_API_2 set as default streaming mode.
The problem is that when .debug() method is triggered the dummy frame is encoded but never decoded, every decoder found just return -1 (INFO_TRY_AGAIN_LATER) when dequeueOutputBuffer is called (I have increased all timeouts up to 1 minute), so it basically times out each time.
If I skip the .debug() method completely the encode starts, or at least I guess so, because I see that onBitrateUpdate is triggered (even if the value is very very small, like 100 Kbps max). But the preview seems very laggy, I cannot access the rtsp stream via VLC or ffplay and on the logcat I see that error: V/MediaCodecInputStream﹕ No buffer available...
So the main problem is that the MediaCodec seems to not decode anything. Maybe is it due to a synchronous implementation of MediaCodec? Have someone tried to use asynchronous callback from the object to read buffers? Is it working? What about update code to use camera2 api?
On the other hand with MODE_MEDIARECORDER_API I get another error:
E/MediaRecorder: start failed: -2147483648
W/System.err: java.lang.RuntimeException: start failed. W/System.err: at android.media.MediaRecorder.start(Native Method)
As far as I understand that error is throwed because the ParcelFileDescriptor is not seekable and since API 23 that it's no more allowed.
Is there a new workaround for this error?
Thanks in advance.

You can try with other library:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java

pedroSG94
Wow, that is exactly what I needed. Can you provide an example on how to use your library to stream audio and video via RTSP without a surfaceView (I need to use it on a Service and I don't need to show the playback to the user). I'm interested in the Camera2Base builder.


shanpshot typo in clean-up.md

there is shanpshot instead of snapshot
https://github.com/JetBrains/teamcity-documentation/blob/2019.1/topics/clean-up.md

Thank you for noting! The typo has been fixed.


add ecnu email domain for students

there is a ecnu.edu.cn in lib, but now the email domain for students has changed to ecnu.cn

unfortunately http://www.ecnu.cn/ doesn't open. Please somehow confirm that the domain belongs to the university.


[Ruutu] Fix extractor by attempting to authenticate video url

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Since spring 2019, most ruutu.fi videos require an authenticated video url. This pr attempts to authenticate the video url if the old unauthenticated method fails. Related issue: #21031

Current one no longer works.


Installing 1.6 - schematics/@angular peer dependency warning

Versions
Angular CLI: 1.6.0
Node: 8.9.2
OS: darwin x64
Angular:

Repro steps

npm install -g @angular/cli

Observed behavior
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Desired behavior
No Warnings about missing dependencies

Came here to say basically say the same. I'm running it on node 7.6.0 and macOs 10.11.6.

Duplicate of #8767


TS: Add missing getChildContext method

Fixes #1043

Coverage remained the same at 100.0% when pulling 59e02534c781aaaaf3665414744284f3154212c8 on marvinhagemeister:ts_child_context into 757113fc711ba68b407cde82f479293d7c5dd9bc on developit:master.


ejs code beautify failure

<!DOCTYPE html>

        <meta charset="utf-8">
        <title></title>

ctr-alt-b
<!DOCTYPE html>

        <meta charset="utf-8">
        <title></title>

I can reproduce this defect on Pretty Diff.  Two missing quotes.

Fixed in Pretty Diff v1.16.16.  The corrected code is at http://prettydiff.com/lib/jspretty.js
Until a new version of Atom Beautify is released you will need to update the Pretty Diff dependency to the latest version.

You can copy the corrected file over the current file in your local distribution.
You can also uninstall / reinstall Atom Beautify to get the latest dependencies


Update login page UI

Update login page UI

changed color scheme to minimal clean
Include animation with button that mirrors title text animation (hidden -> revealed)

Before and After


[ERROR] {0}: Not alive and dispose was called, filename: {1}

Describe the bug
Running mvn dependency-check:check produced the following log:
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< com.example:project >----------------------
[INFO] Building Example Project 1.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- dependency-check:8.4.2:check (default-cli) @ project ---
[INFO] Checking for updates
[INFO] Skipping NVD check since last check was within 4 hours.
[INFO] Skipping RetireJS update since last update was within 24 hours.
[INFO] Skipping Hosted Suppressions file update since last update was within 2 hours.
[INFO] Skipping Known Exploited Vulnerabilities update check since last check was within 24 hours.
[INFO] Check for updates complete (32 ms)
[INFO]

Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user’s risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.

   About ODC: https://jeremylong.github.io/DependencyCheck/general/internals.html
   False Positives: https://jeremylong.github.io/DependencyCheck/general/suppression.html

💖 Sponsor: https://github.com/sponsors/jeremylong

[INFO] Analysis Started
[INFO] Finished Archive Analyzer (5 seconds)
[INFO] Finished File Name Analyzer (0 seconds)
[INFO] Finished Jar Analyzer (1 seconds)
[INFO] Finished Dependency Merging Analyzer (0 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Created CPE Index (2 seconds)
[INFO] Finished CPE Analyzer (4 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
[INFO] Finished RetireJS Analyzer (2 seconds)
[INFO] Finished Sonatype OSS Index Analyzer (0 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Known Exploited Vulnerability Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Suppression Rule had zero matches: SuppressionRule{cve={CVE-2023-44487,}}
[INFO] Finished Unused Suppression Rule Analyzer (0 seconds)
[INFO] Analysis Complete (20 seconds)
[INFO] Writing report to: C:\project\target\owasp-reports\dependency-check-report.html
[WARNING]

One or more dependencies were identified with known vulnerabilities in Example Project:

xmlsec-2.2.4.jar<EMAIL_ADDRESS>cpe:2.3:a:apache:santuario_xml_security_for_java:2.2.4:*:*:*:*:*:*:*, cpe:2.3:a:apache:xml_security_for_java:2.2.4:*:*:*:*:*:*:*) : CVE-2023-44483

See the dependency-check report for more details.

[INFO] Cache event queue destroyed: {0}
[INFO] Cache event queue destroyed: {0}
[INFO] Cache event queue destroyed: {0}
[ERROR] {0}: Not alive and dispose was called, filename: {1}
[ERROR] {0}: Not alive and dispose was called, filename: {1}
[ERROR] {0}: Not alive and dispose was called, filename: {1}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  34.369 s
[INFO] Finished at: 2023-10-23T14:06:12+01:00
[INFO] ------------------------------------------------------------------------

Process finished with exit code 0

Version of dependency-check used
The problem occurs using version 8.4.2 of the maven plugin.
Log file
The following part of the debug log may be relevant:
[DEBUG] Error loading LogFactory
java.util.ServiceConfigurationError: org.apache.commons.jcs3.log.LogFactory: org.apache.commons.jcs3.log.Log4j2Factory Unable to get public no-arg constructor
    at java.util.ServiceLoader.fail (ServiceLoader.java:582)
    at java.util.ServiceLoader.getConstructor (ServiceLoader.java:673)
    at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService (ServiceLoader.java:1233)
    at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext (ServiceLoader.java:1265)
    at java.util.ServiceLoader$2.hasNext (ServiceLoader.java:1300)
    at java.util.ServiceLoader$3.hasNext (ServiceLoader.java:1385)
    at org.apache.commons.jcs3.log.LogManager$LogFactoryHolder.createLogFactory (LogManager.java:69)
    at org.apache.commons.jcs3.log.LogManager$LogFactoryHolder.<clinit> (LogManager.java:48)
    at org.apache.commons.jcs3.log.LogManager.getLogFactory (LogManager.java:121)
    at org.apache.commons.jcs3.log.LogManager.getLog (LogManager.java:151)
    at org.apache.commons.jcs3.engine.control.CompositeCacheManager.<clinit> (CompositeCacheManager.java:80)
    at org.apache.commons.jcs3.JCS.getCacheManager (JCS.java:116)
    at org.apache.commons.jcs3.JCS.getInstance (JCS.java:159)
    at org.owasp.dependencycheck.data.cache.DataCacheFactory.getPomCache (DataCacheFactory.java:155)
    at org.owasp.dependencycheck.analyzer.CentralAnalyzer.initialize (CentralAnalyzer.java:124)
    at org.owasp.dependencycheck.Engine.lambda$loadAnalyzers$1 (Engine.java:237)
    at java.util.ArrayList.forEach (ArrayList.java:1541)
    at org.owasp.dependencycheck.Engine.loadAnalyzers (Engine.java:236)
    at org.owasp.dependencycheck.Engine.initializeEngine (Engine.java:203)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:192)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:167)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:157)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.initializeEngine (BaseDependencyCheckMojo.java:2125)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1920)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:1112)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:52)
    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:161)
    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:73)
Caused by: java.lang.NoClassDefFoundError: org/apache/logging/log4j/message/MessageFactory
    at java.lang.Class.getDeclaredConstructors0 (Native Method)
    at java.lang.Class.privateGetDeclaredConstructors (Class.java:3137)
    at java.lang.Class.getConstructor0 (Class.java:3342)
    at java.lang.Class.getConstructor (Class.java:2151)
    at java.util.ServiceLoader$1.run (ServiceLoader.java:660)
    at java.util.ServiceLoader$1.run (ServiceLoader.java:657)
    at java.security.AccessController.doPrivileged (Native Method)
    at java.util.ServiceLoader.getConstructor (ServiceLoader.java:668)
    at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService (ServiceLoader.java:1233)
    at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext (ServiceLoader.java:1265)
    at java.util.ServiceLoader$2.hasNext (ServiceLoader.java:1300)
    at java.util.ServiceLoader$3.hasNext (ServiceLoader.java:1385)
    at org.apache.commons.jcs3.log.LogManager$LogFactoryHolder.createLogFactory (LogManager.java:69)
    at org.apache.commons.jcs3.log.LogManager$LogFactoryHolder.<clinit> (LogManager.java:48)
    at org.apache.commons.jcs3.log.LogManager.getLogFactory (LogManager.java:121)
    at org.apache.commons.jcs3.log.LogManager.getLog (LogManager.java:151)
    at org.apache.commons.jcs3.engine.control.CompositeCacheManager.<clinit> (CompositeCacheManager.java:80)
    at org.apache.commons.jcs3.JCS.getCacheManager (JCS.java:116)
    at org.apache.commons.jcs3.JCS.getInstance (JCS.java:159)
    at org.owasp.dependencycheck.data.cache.DataCacheFactory.getPomCache (DataCacheFactory.java:155)
    at org.owasp.dependencycheck.analyzer.CentralAnalyzer.initialize (CentralAnalyzer.java:124)
    at org.owasp.dependencycheck.Engine.lambda$loadAnalyzers$1 (Engine.java:237)
    at java.util.ArrayList.forEach (ArrayList.java:1541)
    at org.owasp.dependencycheck.Engine.loadAnalyzers (Engine.java:236)
    at org.owasp.dependencycheck.Engine.initializeEngine (Engine.java:203)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:192)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:167)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:157)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.initializeEngine (BaseDependencyCheckMojo.java:2125)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1920)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:1112)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:52)
    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:161)
    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:73)
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.message.MessageFactory
    at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass (SelfFirstStrategy.java:50)
    at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass (ClassRealm.java:271)
    at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass (ClassRealm.java:247)
    at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass (ClassRealm.java:239)
    at java.lang.Class.getDeclaredConstructors0 (Native Method)
    at java.lang.Class.privateGetDeclaredConstructors (Class.java:3137)
    at java.lang.Class.getConstructor0 (Class.java:3342)
    at java.lang.Class.getConstructor (Class.java:2151)
    at java.util.ServiceLoader$1.run (ServiceLoader.java:660)
    at java.util.ServiceLoader$1.run (ServiceLoader.java:657)
    at java.security.AccessController.doPrivileged (Native Method)
    at java.util.ServiceLoader.getConstructor (ServiceLoader.java:668)
    at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService (ServiceLoader.java:1233)
    at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext (ServiceLoader.java:1265)
    at java.util.ServiceLoader$2.hasNext (ServiceLoader.java:1300)
    at java.util.ServiceLoader$3.hasNext (ServiceLoader.java:1385)
    at org.apache.commons.jcs3.log.LogManager$LogFactoryHolder.createLogFactory (LogManager.java:69)
    at org.apache.commons.jcs3.log.LogManager$LogFactoryHolder.<clinit> (LogManager.java:48)
    at org.apache.commons.jcs3.log.LogManager.getLogFactory (LogManager.java:121)
    at org.apache.commons.jcs3.log.LogManager.getLog (LogManager.java:151)
    at org.apache.commons.jcs3.engine.control.CompositeCacheManager.<clinit> (CompositeCacheManager.java:80)
    at org.apache.commons.jcs3.JCS.getCacheManager (JCS.java:116)
    at org.apache.commons.jcs3.JCS.getInstance (JCS.java:159)
    at org.owasp.dependencycheck.data.cache.DataCacheFactory.getPomCache (DataCacheFactory.java:155)
    at org.owasp.dependencycheck.analyzer.CentralAnalyzer.initialize (CentralAnalyzer.java:124)
    at org.owasp.dependencycheck.Engine.lambda$loadAnalyzers$1 (Engine.java:237)
    at java.util.ArrayList.forEach (ArrayList.java:1541)
    at org.owasp.dependencycheck.Engine.loadAnalyzers (Engine.java:236)
    at org.owasp.dependencycheck.Engine.initializeEngine (Engine.java:203)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:192)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:167)
    at org.owasp.dependencycheck.Engine.<init> (Engine.java:157)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.initializeEngine (BaseDependencyCheckMojo.java:2125)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1920)
    at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:1112)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:52)
    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:161)
    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:73)
[DEBUG] Found LogFactory for slf4j
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Setting property [{0}] to [{1}].
[DEBUG] Creating DiskCache for attributes = {0}
[DEBUG] threadPoolName = [{0}] poolType = {1}
[DEBUG] Constructed: {0}

Certainly it appears the logging has not initialised correctly.
Expected behavior
No errors logged
Additional context
Upgraded from 8.4.0.

Following this post, since I am facing the same errors while running Dependency Check as GitHub Action. It does generate report and place in artifacts but logs show these error messages.
 "--format" "HTML" "--failOnCVSS" "7" "--out" "/github/workspace/reports" "--noupdate" "--disableOssIndex"
[INFO] Instance is null, returning unconfigured instance
[INFO] Using system property [[{0}] [{1}]]
[INFO] Setting default auxiliaries to "{0}"
[INFO] setting defaultCompositeCacheAttributes to {0}
[INFO] setting defaultElementAttributes to {0}
[INFO] initialized MemoryCache for {0}
[INFO] Constructed cache with name [{0}] and cache attributes {1}
[INFO] No cache event logger defined for auxiliary [{0}]
[INFO] Using standard serializer [{0}] for auxiliary [{1}]
[INFO] {0}: Set maxKeySize to: "{1}"
[INFO] {0}: Cache file root directory: {1}
[INFO] {0}: Indexed Disk Cache is alive.
[INFO] initialized MemoryCache for {0}
[INFO] Constructed cache with name [{0}] and cache attributes {1}
[INFO] No cache event logger defined for auxiliary [{0}]
[INFO] Using standard serializer [{0}] for auxiliary [{1}]
[INFO] {0}: Set maxKeySize to: "{1}"
[INFO] {0}: Cache file root directory: {1}
[INFO] {0}: Indexed Disk Cache is alive.
[INFO] initialized MemoryCache for {0}
[INFO] Constructed cache with name [{0}] and cache attributes {1}
[INFO] No cache event logger defined for auxiliary [{0}]
[INFO] Using standard serializer [{0}] for auxiliary [{1}]
[INFO] {0}: Set maxKeySize to: "{1}"
[INFO] {0}: Cache file root directory: {1}
[INFO] {0}: Indexed Disk Cache is alive.
[INFO] Parsed regions {0}
[INFO] Finished configuration in {0} ms.
[INFO]

Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user’s risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.

   About ODC: https://jeremylong.github.io/DependencyCheck/general/internals.html
   False Positives: https://jeremylong.github.io/DependencyCheck/general/suppression.html

💖 Sponsor: https://github.com/sponsors/jeremylong

[INFO] Analysis Started
[INFO] Finished Archive Analyzer (0 seconds)
[INFO] Finished File Name Analyzer (0 seconds)
[INFO] Finished Assembly Analyzer (0 seconds)
[WARN] dependency skipped: node module esbuild-android-arm64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-darwin-64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-darwin-arm64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-freebsd-64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-freebsd-arm64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-32 seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-arm seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-arm64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-mips64le seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-ppc64le seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-riscv64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-linux-s390x seems optional and not installed
[WARN] dependency skipped: node module esbuild-netbsd-64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-openbsd-64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-sunos-64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-windows-32 seems optional and not installed
[WARN] dependency skipped: node module esbuild-windows-64 seems optional and not installed
[WARN] dependency skipped: node module esbuild-windows-arm64 seems optional and not installed
[WARN] dependency skipped: node module fsevents seems optional and not installed
[WARN] Unable to find node module: /github/workspace/node_modules/<EMAIL_ADDRESS>[WARN] Unable to find node module: /github/workspace/node_modules/<EMAIL_ADDRESS>[WARN] dependency skipped: node module fsevents seems optional and not installed
[WARN] Unable to find node module: /github/workspace/node_modules/node-fetch/node_modules/whatwg-url/node_modules/tr[46](https://github.com/EonHealth/eon_dashboard/actions/runs/6624129603/job/17992489281#step:5:47)/package.json
[WARN] Unable to find node module: /github/workspace/node_modules/node-fetch/node_modules/whatwg-url/node_modules/webidl-conversions/package.json
[INFO] Finished Node.js Package Analyzer (39 seconds)
[INFO] Finished Dependency Merging Analyzer (10 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Created CPE Index (2 seconds)
[INFO] Finished CPE Analyzer (9 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
[INFO] Finished Node Audit Analyzer (1 seconds)
[INFO] Finished Yarn Audit Analyzer (0 seconds)
[INFO] Finished RetireJS Analyzer (187 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Known Exploited Vulnerability Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (239 seconds)
[INFO] Finished Unused Suppression Rule Analyzer (0 seconds)
[INFO] Analysis Complete ([49](https://github.com/EonHealth/eon_dashboard/actions/runs/6624129603/job/17992489281#step:5:50)0 seconds)
[INFO] Writing report to: /github/workspace/reports/dependency-check-report.html
[INFO] Element event queue destroyed: {0}
[INFO] In DISPOSE, [{0}] fromRemote [{1}]
[INFO] In DISPOSE, [{0}] auxiliary [{1}]
[INFO] In DISPOSE, [{0}] put {1} into auxiliary [{2}]
[INFO] In dispose, destroying event queue.
[INFO] Cache event queue destroyed: {0}
[INFO] {0}: Saving keys to: {1}, key count: {2}
[INFO] {0}: Finished saving keys.
[INFO] {0}: Shutdown complete.
[INFO] In DISPOSE, [{0}] disposing of memory cache.
[INFO] Memory Cache dispose called.
[INFO] In DISPOSE, [{0}] fromRemote [{1}]
[INFO] In DISPOSE, [{0}] auxiliary [{1}]
[INFO] In DISPOSE, [{0}] put {1} into auxiliary [{2}]
[INFO] In dispose, destroying event queue.
[INFO] Cache event queue destroyed: {0}
[INFO] {0}: Saving keys to: {1}, key count: {2}
[INFO] {0}: Finished saving keys.
[INFO] {0}: Shutdown complete.
[INFO] In DISPOSE, [{0}] disposing of memory cache.
[INFO] Memory Cache dispose called.
[INFO] In DISPOSE, [{0}] fromRemote [{1}]
[INFO] In DISPOSE, [{0}] auxiliary [{1}]
[INFO] In DISPOSE, [{0}] put {1} into auxiliary [{2}]
[INFO] In dispose, destroying event queue.
[INFO] Cache event queue destroyed: {0}
[INFO] {0}: Saving keys to: {1}, key count: {2}
[INFO] {0}: Finished saving keys.
[INFO] {0}: Shutdown complete.
[INFO] In DISPOSE, [{0}] disposing of memory cache.
[INFO] Memory Cache dispose called.
[INFO] In dispose, destroying event queue.
Error:  {0}: Not alive and dispose was called, filename: {1}
[INFO] In dispose, destroying event queue.
Error:  {0}: Not alive and dispose was called, filename: {1}
[INFO] In dispose, destroying event queue.
Error:  {0}: Not alive and dispose was called, filename: {1}

All of the errors appear to be noise that can be ignored. I'll look into configuring the logging for JCS so that these are not logged.

@OrangeDog the logging is being initialized correctly - but we are using logback instead of log4j. The error is reported by JCS - see https://github.com/apache/commons-jcs/pull/120/files#diff-8652be40fdaa2e76e5b081eb526e4d421de9dd5a5f32a52ed7a31149ba30997dR86-R90
Also the line below the stack trace [DEBUG] Found LogFactory for slf4j. Yeah, we likely should not have put the entire stack trace in the log like that... Suggesting changes to JCS has taken a long time - I'll see what I can do about fixing that.

@jeremylong all the {0} and {1} suggests something is not expecting the SLF4J API, because it doesn't use numbered parameters. Are you missing a bridge plugin perhaps?

Probably ;)

See https://github.com/jeremylong/jcs3-slf4j/pull/1. I will publish the updated version of the log adapter shortly and then update ODC.

While the log formatting is fixed, the actual problem is still there:
[ERROR] Region [NODEAUDIT] : Not alive and dispose was called, filename: NODEAUDIT
[ERROR] Region [CENTRAL] : Not alive and dispose was called, filename: CENTRAL
[ERROR] Region [POM] : Not alive and dispose was called, filename: POM

i.e. this has not been done

I'll look into configuring the logging for JCS so that these are not logged.


Per category evaluation

Hello there,
is it possible to run the coco evaluation per category or class?

You can refer to https://github.com/cocodataset/cocoapi/issues/276

It will do per class but for a specific AP threshold.
How would we do per class for<EMAIL_ADDRESS>?

@Robotatron Have you tried it? I think it will give the AP for<EMAIL_ADDRESS>

@Robotatron Have you tried it? I think it will give the AP for<EMAIL_ADDRESS>
I figured it out. By default it prints per class AP50:
https://github.com/cocodataset/cocoapi/blob/master/PythonAPI/pycocotools/cocoeval.py#L461
Set iouThr  to None to get<EMAIL_ADDRESS>


Avoid use of aspect-ratio for prominent simulator run button

From photos on twitter, some folks are using old enough Edge that they don't have aspect-ratio (pre v88).
We only use it for the run button and can probably avoid it so let's try that at some point.
Not urgent, it's just a flat oval and there may well be other issues with a browser that old too.

Also affects Safari 13.


Fix ratelimiter

For some reason the checks are failing because of the following problem

@romeq Probably fixed by #82, try a merge?

yeah I just don't want to cope with this pr's problems anymore
I'll just close this as is and create a new one with the same commits and newest base


Error while storing scores

While looking at #174, we can see in the logs a constraint violation while storing the score:
ERROR: duplicate key value violates unique constraint "scores_pkey"

org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint [scores_pkey]
[...]
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "scores_pkey"

@alecharp  Hi, I would like to work on this bug and make some valuable contribution. Is this issue about to get closed or needs some testing.

I incorrectly linked this issue with another pull requests.

Hi @alecharp I have installed java, maven, node and yarn on my system but failed to run the mvn spring-boot:run -Dskip.yarn command. Could you help me figure out the reason, I reckon it might be due to the environment variables which is not clear from the contributing documentation. Alternatively can I create a beginner friendly issue and work on it to update the contributing documentation once I am able to build and run the project.

I incorrectly linked this issue with another pull requests.

Hi @alecharp, Also just to confirm the status of this issue.

which is not clear from the contributing documentation

I'm sorry about that. Could you join https://gitter.im/jenkinsci/GSoC-Plugin_Health_Score so we can discuss it here? Just to keep this issue about the database problem. Thanks.

Alternatively can I create a beginner friendly issue and work on it to update the contributing documentation once I am able to build and run the project.

This is an excellent idea! Please do so that we improve the contribution guide. This would be marvelous.

I'm working back on this issue because it is blocking plugins scores from being updated.

Thanks to @lemeurherve, I got an SQL dump of the database and I found something odd.
The scores.id is set using the sequence scores_seq, which is incremented automatically. Normally. However, I can see that the current nextval of the sequence is 3451 when there is already a 3451 id.
The id sequence seems to have to reset to 1 around the 6th of december of 2022, as they go from 345668 to 1 at that date.

The time of the reset looks like it occurs with the release 1.3.1, probably during its deployment.
As the method to persist scores was not marked as transactional at this moment
https://github.com/jenkins-infra/plugin-health-scoring/blob/678b36e8320a43f190136b785c0c4c1edbf02dc8/src/main/java/io/jenkins/pluginhealth/scoring/service/ScoreService.java#L44-L46
It is possible that the deployment occurred during a insertion and the sequence was incorrectly managed.
This was fixed in 1.6.1 with https://github.com/jenkins-infra/plugin-health-scoring/commit/4a69af7829ead5260a8bfffd1528f1553007a4f0
There are two potential solutions:

move ID of scores to UUID which would hide this kind of reset
using a pooled low strategy for the id sequence

The current strategy for the sequence is AUTO which let use the "best" one for the provider (postgresql here). And it is the pooled low strategy.
However, in order to get out of the current situation, we need to clear the table from any entry and reset the sequence.
This would be the same if we wanted to change to UUID for the primary key.
Next steps:

[ ] Ask to clear the scores table and reset the sequence nextval to 1.


F7 with React without AJAX

Hi, I'm trying to build a glorious combo of Meteor, React, Framework7. My only problem is combining Framework7 with React without using AJAX loaded pages. What I do is having a onClick listener on all links that have "data-page" attribute. On clicking I load some very simple page markup to a view:

    $$(document).on('click', 'a[data-page]', function(e) {
      var link = $$(e.target);
      if (!link.is('a[data-page]')) {
        link = link.parents('a[data-page]');
      }

      var page = link.attr('data-page');
      var view = link.attr('data-view');
      var container;
      if(view){
        if(view == 'leftView'){
          container = leftView;
        } else {
          container = mainView;
        }
      } else {
        container = mainView;
      }
      container.router.load({
          content: '

'
        });
    }, true);

Then on F7 pageInit event I hooked a React render functions that renders a React Class into the already loaded page markup.
f7.onPageInit('*', function(page) {
      if(page){
        ReactDOM.render(Utils.pages.getPage(page.name), page.container);
      }
    });

This approach works. However it has issues.There are many things happening in F7 app.router._load() function that can't apply to the not yet fully created DOM at the time of load() call (because React element renders after it). So, stuff like navbars is not handled correctly.
Do you have any idea how could this be done in a better way? Any way to "reinitialize" the page after React renders? Thanks!

Yes, it won't work, as the navbar should be presented for correct routing. I don't know does the React provide such opportunity, but in F7 router's content parameter you can pass already rendered DOM not only HTML

Hi, I tried to pass to "content" property an already rendered DOM and a pushState error came. You put the whole content into the state and when it is a DOM, it gives error. When I disable the pushState option, it works. However React is not able to update the DOM anymore, because app.router._load() manipulates the DOM and React gives error in that case. React does not expect anything other to manipulate the DOM. :( Any ideas are really, really welcome!

Can you give me a small demo app example, the basic things from what you have set up, so i can play with it and check more deeply?

Hi, I prepared a good code for tests here: https://github.com/mishoboss/meteor-react-framework7/
Please, install Meteor, put the contents somewhere and run "meteor" command. It will get and install all necessary components and will run Meteor. Inside the app I've described the problem and there is a showcase. Thanks!

Ok, the issue when loading DOM is because of F7 detach it from React thing. So i've found a workaround, need to get back to loading it by HTML string and then render Navbar and Page separately:
app.jsx:
$$(document).on('click', 'a[data-page]', function(e) {
  var link = $$(e.target);
  if (!link.is('a[data-page]')) {
    link = link.parents('a[data-page]');
  }

  var page = link.attr('data-page'); //.replace('/', '_');
  var view = link.attr('data-view');
  var container;
  if(view){
    if(view == 'leftView'){
      container = leftView;
    } else {
      container = mainView;
    }
  } else {
    container = mainView;
  }

  $$(document).once('pageBeforeInit', '.page[data-page="' + page + '"]', function (e) {
    var page = e.detail.page;
    // Render Page Content
    ReactDOM.render(Utils.pages.getPage(page.name), page.container);

    // Do the same separate rendering of Navbar Inner using React, e.g.:
    // ReactDOM.render(Utils.navbars.getPage(page.name), page.navbarInnerContainer);

    // Example with plain HTML:
    $$(page.navbarInnerContainer).html(
      '
' +
        '' +
          '' +
        '' +
      '
' +
      '
Settings
'
    );

  });
  // Load pummy navbar + page
  container.router.load({
    content: '

'
  });
}, true);

Settings.jsx:
render () {
  return (

Settings

          {this.renderPages()}

  );
}

Also make sure you have the same page name, you have it "Settings" and "settings", i guess should be the same case

Thanks. I'll check it now. What about the pushState issue when passing DOM in "content" property? Please, set pushState:true and you will see the error.
I was thinking if it is possible to develop the F7 in a way to respect React life cycle naturally? You have made it for Template7. It would be really cool to also handle React out of the box. This will have a major positive reaction for F7. Do you think it is possible? I'm ready to help with wathever I could.

What about the pushState issue when passing DOM in "content" property? Please, set pushState:true and you will see the error.

It is already fixed

It would be really cool to also handle React out of the box

No much chances at the moment. I'm not too familiar with it, and there are a lot of different libs that people want to see instead of React, i can't please everyone :)

So far, so good. I'm organising now the code in a beautiful and logical "framework". One thing though. I saw you have added "page.navbarInnerContainer", which is good. But can we also have "page.navbarContainer"? The idea is that React's Class render function can have just one root tag. So, I have to add a wrapping DIV element right below .navbar-inner element and this breaks some CSS. I can get it programatically, but it would be more beautiful if it is provided in the page object. Thanks!

There were problems with React hooking on navbarContainer and looks like having a nested
 is not a problem for F7. So the above is solved. However, another issue came and I would like to take a look as it is F7 related. Please, pull the changes from the repo. Run the app and click the "gear icon"in the upper right corner. Then click "Back". The navbar disappears. Do you have any idea why?

The navbar disappears

I guess this is because double navbar-inner you had there. You need to avoid that

Unfortunately no way to avoid it. React wants only one root element. In case of multiple elements, it expects them to be wrapped in a parent element: https://facebook.github.io/react/tips/maximum-number-of-jsx-root-nodes.html
Any ideas are welcome.

I don't know then as not too familiar with React. But anyway, it is just a Navbar, do you expect much of data-bindings there? Maybe you can just leave it to F7, like in my example which returning plain HTML that doesn't handled by React

It was good to be handled by React and have reactivity in cases with toolbar buttons with submenus in popovers. If its not possible, static HTML is always a fallback possibility.

Also, have you checked this app? https://github.com/philipshurpik/framework7-react-base They use some kind of wrapper for navbar inner https://github.com/philipshurpik/framework7-react-base/blob/master/src/contact/contactView.js#L76

Thanks for the hint. I know this app, but they use custom router and requireJS. However they did a nice trick by introducing a .navbar-wrapper class that solves the style issues:
.navbar .navbar-wrapper {
  position: absolute;
  left: 0;
  top: 0;
  width: 100%;
  height: 100%;
  padding: 0 8px;
  -webkit-box-sizing: border-box;
  -moz-box-sizing: border-box;
  box-sizing: border-box;
  display: -webkit-box;
  display: -ms-flexbox;
  display: -webkit-flex;
  display: flex;
  -webkit-box-pack: justify;
  -ms-flex-pack: justify;
  -webkit-justify-content: space-between;
  justify-content: space-between;
  -webkit-box-align: center;
  -ms-flex-align: center;
  -webkit-align-items: center;
  align-items: center;
}

The problem withe the dissapeared navbar on Back now is gone! :) Thanks for the hint! :)

Ok, cool then ;)

Another issue found and I'm not sure why it happens. When going back in router, it only shows just one page back. Then it shows blank pages. I have pushed changes to the repo and you can reproduce it easily: https://github.com/mishoboss/meteor-react-framework7/

I guess you have to enable domCache for views

You nailed it! :)

But this means that all the DOM stays forever in the browser. It would be a problem for huge apps. Why does the router needs to cache DOM in order to be able to goes back?

No, not forever, only for the previous page and while they are set as previous pages. Otherwise, F7 will detach it and your React/Meteor implementation will be broken

Closing due to inactivity


cilium-operator delete CEC cilium-ingress when other ingressclass resources are created

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Having cilium up and running using its ingress feature all works fine. We have several ingress objects serving different services.
We are also running other ingress controller listening for ingress resources with a specific ingressclass.
When we create an ingress resources with an ingressclass does not belong to cilium, the ciliumEnvoyConfig resource in kube-system called cilium-ingress is deleted making all ingress routing by cilium fail.
This CEC resource is recreated only if the cilium-operator pod is restarted
In addition, we have also noticed that the cilium-ingress CEC is deleted and created every time cilium-operator is restarted. Could it be safer mantain a reconcilation loop with this object and just update it in case it already exists instead delete? Furthermore being a managed resource, I would expect it being recreated in case of accidental deletion or manipulation.
Cilium Version
cilium image (running): v1.14.1
Kernel Version
5.15.128
Kubernetes Version
v1.27.4-eks-2d98532
Sysdump
No response
Relevant log output
level=debug msg="Handling ingress added event" ingress=test k8sNamespace=default subsys=ingress-controller

level=debug msg="Generated model for ingress" forcedShared=false ingress=test k8sNamespace=default model="REDACTED" subsys=ingress-controller

level=debug msg="Translated resources for ingress" ciliumEnvoyConfig=REDACTED endpoint=nil ingress=test k8sNamespace=default service=nil subsys=ingress-controller

level=debug msg="Deleted object which was no longer tracked" obj="&{{ } {cilium-ingress  kube-system  [....] subsys=ingress-controller

level=debug msg="Skipping ingress as it is not the cilium class or default" ingress=test k8sNamespace=default subsys=ingress-controller

Anything else?
example ingress triggering the issue
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  creationTimestamp: null
  annotations:
    kubernetes.io/ingress.class: core
  labels:
    app: example
  name: example-ingress
  namespace: default
spec:
  rules:
  - host: example.com
    http:
      paths:
      - backend:
          service:
            name: serviceA
            port:
              number: 443
        path: /test
        pathType: ImplementationSpecific

Code of Conduct

[X] I agree to follow this project's Code of Conduct

In addition, we have also noticed that the cilium-ingress CEC is deleted and created every time cilium-operator is restarted. Could it be safer mantain a reconcilation loop with this object and just update it in case it already exists instead delete? Furthermore being a managed resource, I would expect it being recreated in case of accidental deletion or manipulation.

Hi, @aanm Can i pick up this task?

@chaunceyjiang sure, go ahead

In addition, we have also noticed that the cilium-ingress CEC is deleted and created every time cilium-operator is restarted.

Hi, @ese I have tried many times but cannot reproduce this issue. Can you provide more detailed reproduction steps?

In addition, we have also noticed that the cilium-ingress CEC is deleted and created every time cilium-operator is restarted.

Hi, @ese I have tried many times but cannot reproduce this issue. Can you provide more detailed reproduction steps?

This happens when you have in your cluster ingress objects that ara not ingless.class cilium
To reproduce it:
1 Create ingress objects as ingress.class "cilium"
2 Create ingress objects with another ingress.class
Example:
apiVersion: v1
items:
- apiVersion: networking.k8s.io/v1
  kind: Ingress
  metadata:
    annotations:
      kubernetes.io/ingress.class: core
    creationTimestamp: "2023-10-16T14:26:14Z"
    generation: 1
    labels:
      app: example
    name: example-ingress
    namespace: default
    resourceVersion: "12042537"
    uid: 69ba8733-6b9a-4db3-82b2-5df80e153837
  spec:
    rules:
    - host: example.com
      http:
        paths:
        - backend:
            service:
              name: details
              port:
                number: 443
          path: /test
          pathType: ImplementationSpecific
  status:
    loadBalancer: {}
- apiVersion: networking.k8s.io/v1
  kind: Ingress
  metadata:
    creationTimestamp: "2023-08-25T15:37:31Z"
    generation: 1
    name: tls-ingress
    namespace: default
    resourceVersion: "49570"
    uid: c2d77c80-d026-4381-b621-1c13da523e90
  spec:
    ingressClassName: cilium
    rules:
    - host: hipstershop.cilium.rocks
      http:
        paths:
        - backend:
            service:
              name: productcatalogservice
              port:
                number: 3550
          path: /hipstershop.ProductCatalogService
          pathType: Prefix
        - backend:
            service:
              name: currencyservice
              port:
                number: 7000
          path: /hipstershop.CurrencyService
          pathType: Prefix
    - host: bookinfo.cilium.rocks
      http:
        paths:
        - backend:
            service:
              name: details
              port:
                number: 9080
          path: /details
          pathType: Prefix
        - backend:
            service:
              name: productpage
              port:
                number: 9080
          path: /
          pathType: Prefix
    tls:
    - hosts:
      - bookinfo.cilium.rocks
      - hipstershop.cilium.rocks
      secretName: demo-cert
kind: List
metadata:
  resourceVersion: ""

@ese Thank you very much, I will continue to research this issue.


2 MousePlatform's in device module

Describe the bug
There are 2 MousePlatform definitions in the device module that were probably created separately for ephys_rig and behavior. However, this is confusing and could be causing errors for child models.
To Reproduce
Steps to reproduce the behavior:

Go to aind-data-schema device module line 530
Go to aind-data-schema device module line 608

Expected behavior
Clean this up (redefine the names and inheritance to ensure it's as expected).

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Originally posted by @jtyoung84 in https://github.com/AllenNeuralDynamics/aind-data-schema/pull/403#pullrequestreview-1517640710

This is resolved in #425


Refactor code in hypervisor.go

Remove dom0handle and use bool enabled to speficy if that hypervisor is enabled on this device. For kvm and kubevirt we also use base.IsHVTypeKube() to differentiate.
Cleaned up GetAvailableHypervisors()

The go tests failuire is already in master and needs to be fixed separately.


Feature/data uploader gem

Integrates the data uploader gem.

This is a PR for the gem: https://github.com/ClimateWatch-Vizzuality/climate-watch-gems/pull/6


[docs]: translate hertz/reference/config/

config:
zh web page：https://www.cloudwego.io/zh/docs/hertz/reference/config/
zh doc：https://github.com/cloudwego/cloudwego.github.io/blob/main/content/zh/docs/hertz/reference/config.md
en folder：https://github.com/cloudwego/cloudwego.github.io/tree/main/content/en/docs/hertz/reference
Notes:
Do not change the original layout, code style or content sequence.
Software Translator is a tool, not god, do not use the result as the final result.
Translation principle: faithfulness, expressiveness and elegance.
Submit your PR here in this repo.

hello, I want to try this issue, thank you.

Well done!


Make it lazy load pagination for huge data?

Should be next page only

Or get total data then paginate for request

It was my mistake I didn't think about huge amount of data when I first developed it. Probably I will implement them both, according to (http://uxmovement.com/navigation/avoid-the-pains-of-pagination/) that sometimes, when the number of pages is too big, it's not necessary to show the current page number because it doesn't encourage the user to view until the last page. However, if the number of pages is considered small (probably around less than 20), it is still accepted to show the current page number.
As for the data request, I feel like it's way better to separate the functions that send HTTP request from this component (ie. using Redux, for separation of concerns), so that these functions are passed as props to this component.
Thanks for the idea! I will probably implement it one or two versions after this one.

Fixed with https://github.com/Imballinst/react-bs-datatable/pull/40.


Notifying a C# application whenever something in the database has been changed or added

My co-workers and I have tried sqldependency() but in order to use that we need to enable service broker on the database. Which apparently is not allowed on azure

Thank you for the question! In order to best address your question, could you provide us with the URL of the MS Doc that you were following, if any?

@kevduong1 Can you please provide the documentation which you are following so we can help you out better.
Thanks.

@kevduong1 We will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


How to build a VQA labeling page with a lot of questions, with the image at the left and a rolling QA at the right?

I want to build a VQA (Visual Question Answering) labeling page with a lot of questions, and displaying the image on the left and a rolling QA (Question-Answer) interface on the right. I used the default VQA page, but the image cannot be seen when the question is quite a lot, which really confuses me. I am wondering how could I build a page with a FIXED image on the left, and a ROLLING QA part on the right. Thank you.

Can you share your labeling interface with us, and a diagram of what you're looking for? We need a bit more information to know how to write up the feature request.


New Rule: HTML smuggling sign-in prompt

This will need some FP testing (and maybe a better name 😛)

it looks like this will hit on legit sign-in pages, eg "Secure Message" sharing applications, so we're going to go ahead and close this but let us know if you'd like to discuss further!


Different state_dic in pre-trained model

Hello,
Thank you for sharing your code. This is such an excellent work.
I am trying to get the pre-trained model working on my computer. I did the change on SparseConvnet according to your README and rebuild the SparseConvnet. However, when I try to run evaluation with your pre-trained model, I got the following error:

From my understanding, this is caused by different names between the current convnet middle layer and the pretrain model. So I cannot load the pretrain model on convnet middle layer. I tried to load the pre-trained model with "load_state_dict(state_dict, strict=False)" but clearly all conv layers are still not loaded. This is verified by the source code. What would you suggest to do to fix it? I am thinking about opening the voxelnet-204270.tckpt file somehow and edit the state_dict but no succeeding.
Thanks for your time.
Vince

Found it and going to fix it.
The following link shows that some parameters' name is changed. I am going to change those back and rebuild the SparseConvNet.
https://github.com/facebookresearch/SparseConvNet/commit/55d55a6a9fc3f7c1c8b92317772ccf7955712a6e
Thanks a lot. This issue will be closed after I successfully run the pre-train model.


Improved GitHub commit status

Builds that error will now have the following commit message: 💥 An error occurred during the build
Builds that fail will now have the following commit message: ⚠ There were num_failed_tests that failed
Failed builds in GitHub will now have the "details" link to the failed tests instead of the build detail page layout.

I'm unsure of the best way to test metacirepository.utils.create_status:

If I attempt to make the build a mock object, then I end up needing to recreate getter methods (like get_status) on the mock object. Seems like a lot of work to get the mock object to work properly.
If I attempt to use BuildFactory, the given build object has a bad value for build.repo.github_api. I'm also unable to set the attribute on the build object to mock.Mock().
Should I mock out all the necessary github3 responses and attempt to mock nothing at all?

@davisagli - I believe the code here is ready to go. The only other reference to .github_api I see in the codebase is inmetaci/repository/tasks.py and is on a Branch object, not a Repository.
I still need to figure out how to QA this in GitHub with my local.


Enable collision detection between actors

Likely most will be circle collisions? Will need to add a size vector for the actor.

Insight: On every frame, we loop through dynamic actors (characters, traps, teleport door, etc) and detect for collision.
Here's my quick thought on the structure: Each actor has a onCollide(&Actor otherActor) method that runs conditional code based on what the type of the other actor is. There is a contact listener that calls the onCollide method for the actors.
See how Aaron implemented the idea using a sexy listener object in Parryt: https://github.com/GDC-WM/Parryt/blob/main/src/contact_listener.cpp

@aaronamk what are the pros and cons of using circles, and of using rectangles?

Here's a very relevant file from the homegrown physics branch of Parryt. For whoever completes this issue, please refer to this for how to  implement the actual math of the collisions.

@aaronamk what are the pros and cons of using circles, and of using rectangles?

There's no real "pro's" or "cons." Both systems are very simple to implement and we will likely have to use both. For each actor, just use the shape that most closely approximates the shape of that actor. Walls will be rectangles, characters will likely be circles (for a top-down view game).


Leveraged tokens?

It seems that the leveraged token api (https://binance-docs.github.io/apidocs/spot/en/#blvt-endpoints) is not supported, is there any plan to get it supported? Or can I get some guidelines how to extend the api by myself?
Thanks.

Never mind, looks like I can trade the leveraged token just using spot api.

How did you manage to do it?

@Fo3nix If you just need to trade the token, use the spot api.

Sorry I don't really get what you mean. Are there differences in api?
My current code gave this error: binance.exceptions.BinanceAPIException: APIError(code=-2010): This action disabled is on this account.
How can I fix that?

This might help
https://github.com/freqtrade/freqtrade/issues/3945

Thanks for helping me this fast! I'll look into it tomorrow. Thanks again


Vocab size while fine tuning language model

Hi, I used around 8000000 text sentences while fine tuning the language model but the newly added vocabulary size is only 50000. My data have atleast around 1000000-2000000 tokens to be added. Can, I explicitly change the vocab size while fine tuning? Thanks

@Sagar1094 can you please share the code that you are using for lm fine tuning ? thanks

Hi,
I have followed the tutorial for the same.
Regards,
Sagar
On Wed, Jun 10, 2020, 5:06 PM krannnn<EMAIL_ADDRESS>wrote:

@Sagar1094 https://github.com/Sagar1094 can you please share the code
that you are using for lm fine tuning ? thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kaushaltrivedi/fast-bert/issues/223#issuecomment-641943784,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANALH756XKDACY35YAOXHRDRV5V3LANCNFSM4NNUHYQQ
.

Hi,
My data is little different, I have indian addresses for example "i 32
mangol puri delhi", "b-8/205 rohini delhi", "kormangalam bengaluru". I want
to create a address classifier. These addresses have labels assosiated to
them as well like "26-0", "23-2".
Using BERT pre trained  I think it is impossible to train this kind of data
as most of the words would be out of vocab. Can you please help me and
suggest an alternative approach. I have tried training a bert, electra,
roberta models from scratch with huge size of vocab - 2800000 words but it
is failing. So i tried fine tuning fast-bert which aslo dosent work.
Please help 🙏😊
Regards,
Sagar Gupta
+91<PHONE_NUMBER>
On Wed, Jun 10, 2020, 5:12 PM Sagar Gupta<EMAIL_ADDRESS>wrote:

Hi,
I have followed the tutorial for the same.
Regards,
Sagar
On Wed, Jun 10, 2020, 5:06 PM krannnn<EMAIL_ADDRESS>wrote:

@Sagar1094 https://github.com/Sagar1094 can you please share the code
that you are using for lm fine tuning ? thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kaushaltrivedi/fast-bert/issues/223#issuecomment-641943784,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANALH756XKDACY35YAOXHRDRV5V3LANCNFSM4NNUHYQQ
.


Indexing for the edges

Hi,
I know how to do indexing on the vertices, is there any solution for doing it for the edges?
--Omid

As mentioned before (https://github.com/mpollmeier/gremlin-scala/issues/50):
GremlinScala only provides a wrapping layer where it makes sense. In this case it looks like you're just using the main tinkerpop Graph interface, so Gremlin-Scala isn't involved.

yes, I know that gremlin scala is not involved, I just ask it as a general question.

Sorry, I dont know and guess that it's graph db specific
On 2 February 2015 04:58:10 Omid Bakhshandeh<EMAIL_ADDRESS>wrote:

yes, I know that gremlin scala is not involved, I just ask it as a general
question.

Reply to this email directly or view it on GitHub:
https://github.com/mpollmeier/gremlin-scala/issues/60#issuecomment-72370260


Make Jörmungandr tests pass again

Issue Number

Overview

3665332826066b1935d603db418ea1c8cedafcff
Disable STAKE_POOLS_* tests due to #2140

6e276af1c97ee31f4d2b7c7aadf5d206f75526c2
Remove hard-coded mnemonics in case not necessary in integration tests

038c36594579dce16a42f895bda3d60c4e2db132
Remove Shelley specific transaction suite. Add few more basic transaction tests to Jormungandr suite.

6e98d4b10829b4b732c755273d9e9449ca4ee52f
BYRON_MIGRATE_01 - make Jormungandr big wallet for migration smaller (the same as Shelley one) and adjust to pass on both backends

e3d6a55bbafcc9734c5e5baccc1403db63fbbfa4
adjust genMnemonics to be more standard

Comments

bors r+

bors try

bors try-

bors try

bors try

bors r+

bors try

bors merge


Module fails to load in my create-react-app project

I get this
./node_modules/handsfree/src/handsfree.js 321:36
Module parse failed: Unexpected token (321:36)
File was processed with these loaders:
 * ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|
|     Object.keys(this.config.plugin).forEach(plugin => {
>       if (typeof this.config.plugin?.[plugin]?.enabled === 'boolean' && this.config.plugin[plugin].enabled) {
|         this.plugin[plugin].enable();
|       }

any ideas?

Oh thanks for creating this issue! I've been using the optional chaining operator ?. as a shortcut when writing out if statements, and I didn't think about whether ?. is widely supported yet. It looks like optional chaining is still a fairly new feature so I'm going to go through and get rid of these but it may take me a few days to get to.
However in the mean time you can try adding optional chaining to your Babel. Are you using React < 3? I'm not familiar with React myself but depending on your version of React this link may help: https://medium.com/@adostes/enabling-optional-chaining-in-a-create-react-app-a9f626a515d9

I think the typescript transpiler probably doesnt support optional chaining by default and its why it fails. I have a way around this which is to include the minified module in the public folder and access it via the global object, but it is not pretty

I'm glad to hear you were able to work around it for now! I totally agree and in fact not only should it work across frameworks but environments too without any config (like within Node or Electron).
It'll take a little more iteration to get there, but I appreciate you raising these points!

Yo, just to provide feedback.
I had an old React application bundled with webpack 3 on which I wanted to add Handsfree (hands/gesture).
I had to upgrade to webpack 5 and add "@babel/plugin-proposal-optional-chaining": "^7.13.8" as devDep in package.json + .babelrc

well ideally I think it would be great if the library itself gets transpilled in a way that allows it to be used without having to set up extra stuff in the projects where it is used :)

Oh...I didn't think about transpiling thank you for mentioning that! I was so intimidated by this issue thinking I would have to rewrite the library (I use optional chaining everywhere) but I didn't realize that I can just keep the code and transpile. Right now I'm just using Rollup, so I think this should be easy to do
I will do this either tonight or tomorrow. Thanks for being patient with me 🙏

Okay should be all set! You'll need to npm update handsfree to get the latest version. I'm not familiar with React so I don't know what best practices are, but I created a CodeSandbox to demonstrate it working: https://codesandbox.io/s/create-react-app-handsfree-s9xx4?file=/src/index.js

Thank you Oz, it's works.


device: Make device variables global

Allow to access to device structures from the code.
With this change is it possible to statically initialize
pointer to the device.
Removing static allows to get access to the device pointer and initialize it statically during compilation when device that will be used is known. Sample:
extern struct device DEVICE_NAME_GET(temp_nrf5);
const struct my_struct foo = {
  .dev = DEVICE_GET(temp_nrf5)
}

It might be against standard approach but has following advantages:

less code
significantly reduces startup time and it is critical in certain applications. After enabling few drivers on nrf52840 device_get_binding takes 20 ms. Just few calls will take 100ms.

There is of course risk of name collision but drivers are unique and any collision can be easily avoided.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

extern struct device DEVICE_NAME_GET(temp_nrf5);
const struct my_struct foo = {
.dev = DEVICE_GET(temp_nrf5)
}

I get the point, but I would be against it now.
Mostly because this goes against all the work which is being done in DTS. It's not yet there, but in the future (when, I don't know) there will be such statically linked device pointer everywhere
no more device_get_binding() runtime etc etc...
Right now, such patch is imo a hack which would also generate misuse (people pushing driver code, with hardcoded device name because "it works for my board/SoC" etc...)

@tbursztyka

but in the future (when, I don't know)

Any rough estimates? I also see it as a hack but also enabler for shortened startup time so it's good to hear that it will be fixed.

I think the active entry-point is #20253.  We'd better make progress toward that in 2.2, though it's not listed in #20348.

Any rough estimates?

trick question. The work tries to tackle many issues at once: unique ids, power management dependencies, getting rid of the device name (so static linking of devices, for perf and ram gain) etc...
@galak started a quick draft https://github.com/zephyrproject-rtos/zephyr/pull/20253 for unique ids based on DTS, which in turn could be used on further work.
Really, I don't know. I did a prototype of static device linking + getting rid of the device name (and more) 2 years ago already. But that was hacking around Kconfig (dts was barely used at that time).
Doing such thing today is not going to be trivial.


Readme refers to nuget package Elmish.XamarinForms - which does not appear to exist

The readme.md refers to downloading Elmish.XamarinForms from nuget, but there does not appear to be any package of that name on the public nuget feed
Does this refer to a separate nuget feed?

Exists now


domain work

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/edit
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

HI @jomarca24, can you please elaborate on the issue you encountered on the linked page?

No response, not actionable.
Thanks @stevepentland for helping us push on bug reports!


Add new markline type median

There are only 3 markLine types:

max
min
average
~median~

But there is another important type in data analysis, called median.
It can also be achieved by customize markLine option after calculate the median locally. But I think median should be a build-in markLine type for echarts.

Changelog:

add median markLine supported.
add the demo of markLine in scatter named scatter-markline.html.
update .gitignore.

Preview:

Thanks for the contribution!! The dist files should be excluded in the pull request

@pissang Done!


Wrong Typo Class Name AutocompleteDemo.java

in the sample code, the class name is Auto'c'ompleteDemo but file name is Auto'C'ompleteDemo!
fix it please ^^

True. I'm using Windows, which is case-insensitive. Gonna fix it asap :)

done


Add link to TranslateExtension doc

The TranslateExtension doc needs a link to the LocalizationResourceManager helper doc, once written.

I've removed the empty link (because the helper doc doesn't exist).

I've removed the empty link (because the helper doc doesn't exist).


State log incompatibilities between 0.9.10 and older Carla versions

Problem Description
When I start a Carla 0.9.10 or <IP_ADDRESS> server, load a state log generated with an older Carla version (e.g. Carla 0.9.9) and then use the latest Carla Rosbridge with Carla 0.9.10 or <IP_ADDRESS>, the Rosbridge crashes and shows a missing bounding box error:
  File "/home/catkin_ws/src/ros-bridge/carla_ros_bridge/src/carla_ros_bridge/traffic_participant.py", line 101, in get_object_info
    self.carla_actor.bounding_box.extent.x * 2.0,
AttributeError: 'ServerSideSensor' object has no attribute 'bounding_box'

Here is the full output: bounding_box_error.zip
Here is an example state log for which the problem happens: carla_log-0.zip
ServerSideSensor is a C++ class in LibCarla (here is its reference) and does not appear in the Rosbridge code, i.e. searching for ServerSideSensor in the repository files gives no result. Therefore I assume that the problem is related to the Carla server and/or client API.
How to Reproduce

Start the official 0.9.10 Carla server docker container (alternatively run Carla 0.9.10 on the host)
Start a client docker container with ROS (e.g. noetic), the Carla API and latest Carla Rosbridge installed, and connect it to the server container with the --net container:<carla server container> argument
Start a replay with the example state log linked above
Execute following command (in the container with the Rosbridge): roslaunch carla_ros_bridge carla_ros_bridge_with_example_ego_vehicle.launch

The problem does not occur with Carla 0.9.9 (and PPA Rosbridge version).
Furthermore, it only happens when I have loaded a replay of a state log file which I generated with Carla 0.9.9 or older, and there exist state log files for which the problem does not happen.
Additional Information
The problem happens with several versions of Carla, the Rosbridge and ROS
Carla versions: 0.9.10 (docker image), <IP_ADDRESS> (docker image), <IP_ADDRESS> (from releases, running on host)
Rosbridge versions: ee524bb50a, cb83740c5af49f, 959039ad9d84d167fe9
ROS versions: melodic, noetic
Platforms: A Docker image based on ros:noetic-robot for the clients, the official Carla docker images, and the host OS Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-45-generic x86_64)

@joel-mb could you follow up on this please?

The problem no longer happens with CARLA 0.9.11.


Java/Scala API for converting an existing Parquet table to Delta in-place

Tracking a new feature for converting an existing Parquet table to Delta without reading and writing the whole table to a new location.

This has been merge already.


Feauture request: Recieve state of the port or bank.

Feauture request: Recieve state of the port or bank.
The PCA9535 for example can easyly glitch with some minor overvoltage. En extra command to recieve the state of the banks (inputs / outputs) it is easy to  check if settings are still in place. If not, settings can be pushed before port commands.

Hi, sorry for the late reply. Do you mean adding a feature to read if the port/bank is input or output?

Currently, there's no plan for this. If you still need help, please feel free to reopen this issue.


[Update Request]: MongoDB server version 7.0.9

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
MongoDB.Server
Package Version
7.0.9
Please describe the changes you would like to see
There is a new release (<IP_ADDRESS>) available. Download page URL: https://fastdl.mongodb.org/windows/mongodb-windows-x86_64-7.0.9-signed.msi
The current version offered by winget is v6.0.6.

MongoDB has added the version 6.0.6 into archived released due to critical issues.

[Policy] In PR


[New game]: want to add monster maker game

🎮 Game Request
We can design our own monster through this game .
Point down the features
Game points
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Kalivarapubindusree !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Assign

/assign

Assign me this issue under GSSoC'23 label

Hello @Kalivarapubindusree, Time's Uppp!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗

Hey @Kalivarapubindusree ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Allow @query to be redefined if in main (notebook) scope

It's a 1-line change. I don't see an easy way to test it, unfortunately; we'd have to simulate notebook scope somehow (maybe we can file that away as a future problem)

This change is


update cookiecutter template for modules v2

stage on a branch, don't put on master until this is ready for prime-time

The branch issue/3100-create-v2-modules was created on the inmanta-module-template repository. However, the tests do not succeed since pytest-inmanta is incompatible with v2 modules. I will add the dependency on pytest-inmanta to this ticket.


Add shivaylamba to org

Requesting org membership for Kubeflow Release Team 1.7

@DomFleischmann

Please follow https://github.com/kubeflow/internal-acls#joining-kubeflow-github-organization


Account Balance

When i try to get account balance:
It should be:
$ cleos get account tester
{
  "name": "tester",
  "eos_balance": 0,
  "staked_balance": 1,
  "unstaking_balance": 0,
  "last_unstaking_time": "1969-12-31T23:59:59",
  "permissions": [{
      "name": "active",
      "parent": "owner",
      "required_auth": {
        "threshold": 1,
        "keys": [{
            "key": "EOS7d9A3uLe6As66jzN8j44TXJUqJSK3bFjjEEqR4oTvNAB3iM9SA",
            "weight": 1
          }
        ],
        "accounts": []
      }
    },{
      "name": "owner",
      "parent": "owner",
      "required_auth": {
        "threshold": 1,
        "keys": [{
            "key": "EOS4toFS3YXEQCkuuw1aqDLrtHim86Gz9u3hBdcBw5KNPZcursVHq",
            "weight": 1
          }
        ],
        "accounts": []
      }
    }
  ]
}

But this is my output:
MacBook-Air:eos quocle$ cleos get account tester
{
  "account_name": "tester",
  "permissions": [{
      "perm_name": "active",
      "parent": "owner",
      "required_auth": {
        "threshold": 1,
        "keys": [{
            "key": "EOS7cSsCsdL9SPfBGhEXvKDLME2jA9Ugs59mY2DnsHa9AfvfKvA15",
            "weight": 1
          }
        ],
        "accounts": []
      }
    },{
      "perm_name": "owner",
      "parent": "",
      "required_auth": {
        "threshold": 1,
        "keys": [{
            "key": "EOS7cSsCsdL9SPfBGhEXvKDLME2jA9Ugs59mY2DnsHa9AfvfKvA15",
            "weight": 1
          }
        ],
        "accounts": []
      }
    }
  ]
}

There is no account balance in my computer. Anyone know why?

To check the servant accounts created by an account (control account)
The output should be like this:
$ cleos get servants inita
{
  "controlled_accounts": [
    "tester"
  ]
}

Here is my output:
$ cleos get servants inita
{
  "controlled_accounts": []
}

Balances are no longer intrinsic to an account.  They are managed by a contract in the system, and are therefore kept in separate tables.  Use ./cleos get currency balance eosio.token <query-account> to retrieve balances.  Note the token contract must be deployed and a currency created and issued before there are tokens of any kind in the system.


Field: Support serialized value formatting

Environment

react-advanaced-form: 1.2.0

What
Add support to pre-format the serialized value of a field.
Why
This feature can be used in multiple scenarios:

Encrypt the entered password upon serialization (before sending/accessing the data).
Format date input value to match the desired date format.
General value normalization (casing, characters stripping)

How

As a part of createField options (not preferable)
Would be nice to have it as serialize method on the instance of a custom component wrapped in createField

Specification
General statements

Serialization formatting affects only the returned serialized value. It has no affect over the actual field's value, or field's state, in general.
It is possible to provide a custom serialization formatter in two ways:

Upon the field's composition.
As a dedicated prop to the field's instance.

When no custom formatter function is provided, a field's value is returned during the serialization (as it is now)

Syntax
type SerializeFunc<ValueType> = (value: ValueType) => ValueType

Draft
Specification

Field's serialized value can be controlled using onSerialize prop of the respective field, or upon the field's construction via createField options.
onSerialize prop accepts a function that returns the serialized field's value
onSerialize function can return nothing, which makes the field skipped during the serialization

Usage
This:
export default createField({
  onSerialize({ value, fieldProps, fields, form }) {
    return 'bar'
  }
})(Input)

This implies that all instances of Input field will have the provided serialized value transformer.

And this:
<Input
  name="fieldOne"
  value="foo"
  onSerialize={({ value, fieldProps, fields, form }) => {
    return 'bar'
  }} />

This implies that only this very Input field has the provided serialized value transformer.

Both declaration examples will be serialized into the following JSON:
{
  "fieldOne": "bar"
}

[ ] Need to adjust flattenDeep to properly handle plain objects. There is an issue with passing iterable instances, as it would iterate deeply through its private keys (i.e. __ID).


Dewey pr

Current coverage is 73.58%

Merging #13 into master will increase coverage by +12.21% as of c154dd6

@@            master     #13   diff @@
======================================
  Files           55      12     -43
  Stmts         2799     708   -2091
  Branches         0       0
  Methods          0
======================================
- Hit           1718     521   -1197
  Partial          0       0
+ Missed        1081     187    -894

Review entire Coverage Diff as of c154dd6

Powered by Codecov. Updated on successful CI builds.

I thought you meant ReusableXibView sorry. It doesn't really make sense to override ChatInputBar.nibName since that nib defines all the constraints and subviews that are needed for that ChatInputBar to work. Changing the nibName would likely break it, so it'd be better to make that final actually.