String.IndexOf does not work properly for overload IndexOf(sub, startIndex, StringComparison)

Steps To Reproduce
https://deck.net/8798011b32415b49eccd55aec3da43a7
public class Program
{
    public static void Main()
    {
        var msg = "Hello, World!";

        int i = msg.IndexOf("world", 3, StringComparison.InvariantCultureIgnoreCase);

        Console.WriteLine(i);
    }
}

Expected Result
var i = System.String.indexOf(msg, "world", 3, msg.length - 3, 3);

Result: 7
Actual Result
var i = System.String.indexOf(msg, "world", 3, msg.length, 3);

Result:

System.Exception: Uncaught System.ArgumentOutOfRangeException: Index and length must refer to a location within the string
Parameter name: length
Error: Index and length must refer to a location within the string
at $ctor4.ctor (https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:91540)
at $ctor4.$ctor1 (https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:92638)
at $ctor4.$ctor3 (https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:572272)
at new $ctor4 (https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:573754)
at Function.indexOf (https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:287507)
at Function.Main (https://deck.net/RunHandler.ashx?h=1139229282:11:35)
at https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:42576
at HTMLDocument.i (https://deck.net/resources/js/bridge/bridge.min.js?17.2.0:7:6515)
at i (https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js:2:27151)
at Object.add [as done] (https://cdnjs.cloudflare.com/ajax/libs/jquery/2.2.4/jquery.min.js:2:27450)

Thanks for the report!
Deck with assert: https://deck.net/946f0c17f93ea351bd6bf822cb03b6fd
Dotnetfiddle: https://dotnetfiddle.net/ueBdiW

Fixed! The fix will make it to the next Bridge release! (check milestone)


any suggestions for fuzzy search?

how can i do a fuzzy search? such as increase, discrease, no change?

Seems like iGameGod/iGameGuardian/iMemEditor can not do a range search such as -2000~-1000, i would like to finish this feat using h5gg,  any suggestions for this?
btw, Range Search in h5gg don't support from negative to positive, for example, -1~1 is not support till now.

thanks a lot

range search fixed. and h5gg is not design for fuzzy search.

What do you mean by fixed? There is a new version of H5GG after 7.9?


Refactor method of applying K8s resource files

As more complex K8s workloads are being created, teams would like to separate out their K8s resource manifests to be more maintainable.
cc @yunzhu-li.
Idea
Currently template: points to a single file for filling vars: variables.
The suggestion is to allow template: to point to a directory that could containing 0-n K8s manifests for filling vars: variables.
The resulting filled templates would be in some output: directory (default to workspace.Path + /drone-gke-output/*.yml).
Then kubectl apply -f would be performed on the entire output: directory.
Implications

The same thing pattern need to be followed for K8s Secrets manifests (for filling vars:*, secrets:, and secrets_base64 variables), but also output to the same output: directory.

*note vars: is not being filled into .kube.sec.yml today, but is a desired feature https://github.com/NYTimes/drone-gke/issues/8.

The debug of these files will not be accessible via the verbose: parameter as it could/would have difficulty filtering out the "rendered" .kube.sec.yml file(s) in the output: directory. We want to avoid leaking secrets.

A solution (work around) for 2. is that since all files are writen to the output: directory, those files can be uploaded to GCS or S3 for viewing/redeployment/replication at a later time. This is detailed in https://github.com/NYTimes/drone-gke/issues/29.

*note the output: directory may need to create a new temp directory in workspace.Path
(/drone/src/github.com/org/repo/drone-gke-output) instead of something in the workspace.Root
(/drone/drone-gke/).
It may be problematic if the temp directory contains non K8s manifest files, but it cannot error (see the next point for a use case).
This is to support restrictions other plugins have on the directory tree that can be accessed (see https://github.com/drone-plugins/drone-google-cloudstorage/issues/10).
There are further implications of this method, please see https://github.com/NYTimes/drone-gke/issues/29.

An output: directory will also enable other plugins to speak Kubernetes. One use case is for a vault-k8s plugin to write to the output: folder a Vault specific K8s resource for drone-gke to kubectl apply -f dir/.

Following this issue https://github.com/NYTimes/drone-gke/issues/28, this would also allow the same pattern to be followed for creating and deploying into namespaces with labels and names that are templated with vars: variables. However controlling that the Namespace is created first (before other resources) is still TBD.

For those that want to wait until the rollout of some resource to be complete using kubectl rollout status (https://github.com/NYTimes/drone-gke/issues/26), that feature can be implemented with the -f and -R flags to manage all resources in the output: directory, versus specifying the exact resource. Specifics of that feature should be continued in that issue.

Releasing
There may be a way to implement these changes without break changes (transparently for plugin consumers).
If not, we may have to 1) create a new tag for the Docker container, 2) update the existing container to add a very clear DEPRECATION message, and 3) announce a limited support period.
Next steps
This is an RFC, soliciting comments and implications.

Why does it need to take a full directly? Can it take a list of files (comma separated?) instead?

@msuterski I took a few days to think about that and here's what I have to say about that:

Providing a list interface would certainly work, however the final manifest files will be output into a directory anyway (because I want to avoid manipulating the template files in place), and this would keep to the same ux
I don't see any use cases or benefits of referring to files to apply one-by-one (vs having them in a dir). The spec for list would look like this for example:

templates:
  - deploy/app.yml
  - deploy/redis.yml
  - deploy/ingress.yml
  - somedir/xyz.yml
output: drone-gke-output/

vs
template: deploy/
output: drone-gke-output/

Something else I failed to mention in the original RFC comment is that template: currently defaults to .kube.yml, which is safe to assume most people won't specify it.
With the changes in this RFC, we can still default to .kube.yml unless something else is specified. This would prevent a BC in this regard.

I thought that maybe having them as a list would not necessitate for having an output as a directory (and not leak secrets), but I guess those are unrelated.
Maybe I would ask a different question, then, why does output need to be a directory and not a single file (that would not include kube.sec.yml)?

Good question! I want the output to match the input so that if the files are uploaded/reviewed/verbosely printed, they match the organization of the original input manifest templates.

Re 1 and 2:
Is "same thing pattern" some pattern I should know about? If not this seems like an awkward sentence. Also, does the same pattern really need to be followed for secrets? Could that be left as one file to make it easier to filter out secret values from verbose output?
Code that renders templates is aware of vars and secrets. Secrets could be selectively filtered out and replaced with something like a hash of the original value before being printed as verbose output. Very crudely:
for each secret in secrets:
  verbose_output.replace(secret, hash(secret))

What about specifying template_dir and secret_template_dir which get rendered out into specific subdirectories, then run kubectl apply -f -R $parent on a directory that contains both subdirectories?


fix: outputs UTF-8 characters in ProtocolBuffer format

This fixes #170 . As you can see in the changes of the test file, this PR keeps the output still valid in text proto format but modifies indent and delimiter (from <> to {}).

By the way, I have a trouble with the CLA signing. I tried a few times but the site always gives me the server error 😞 . Could someone let me know where to file this issue?

@triplequark @igorbernstein2 Could you review this PR?


Is there any chance not auto load the uia mode.

I am test on the xp machine on some reason, and if the windows xp is complete there is not problem, but if I in the some kind ghost xp system, maybe the system is not complete, then load pywinauto 3.6.5 module on python 3.4 cause a error.
based on the error info , that is becasue of pywinauto auto load the UIA mode , but lately i am not use the UIA mode at all . so , is there any chance the pywinauto module not auto load the UIA mode .
Here if i change the UIA_support = False and everything goes fine.
try:
    # Disable 'INFO' logs from comtypes
    log = logging.getLogger('comtypes')
    log.setLevel('WARNING')
    import comtypes  # noqa: E402

    UIA_support = False
except ImportError:
    UIA_support = False

Or maybe give a option give user a handler to turn it on . I am not familar with the pywinauto moduel inside.

@a358003542 My os is XP. Could you please help me. Which version of pywinauto do you use in Windows XP? And which version of pywin32?


ephemeralStorage computation for instance types doesn't work with AWSNodeTemplate that uses launchTemplateName

Version
Karpenter Version: 0.26.1
Kubernetes Version: v1.23.14-eks-ffeb93d
Expected Behavior
Our LaunchTemplates are quite complex, so our AWSNodeTemplate points to a LaunchTemplate that we create, e.g.
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: karp-prov1-nt
spec:
  detailedMonitoring: false
  launchTemplate: my-complicated-launch-template
  subnetSelector:
    aws-ids: ...

This ends up with the amifamily.DefaultEBS.VolumeSize (20Gi) being applied for my instances.
Actual Behavior
This works well until a pod requests ephemeral-storage and then the pods won't schedule. I tracked this down to the assumption in computeCapacity that the AWSNodeTemplate has blockDeviceMappings defined.
Here's a diff of a hack I added to get this working (which should illustrate the issue):
diff --git a/pkg/cloudprovider/instancetype.go b/pkg/cloudprovider/instancetype.go
index e718bd68..4f85d55d 100644
--- a/pkg/cloudprovider/instancetype.go
+++ b/pkg/cloudprovider/instancetype.go
@@ -55,7 +55,7 @@ func NewInstanceType(ctx context.Context, info *ec2.InstanceTypeInfo, kc *v1alph
                Name:         aws.StringValue(info.InstanceType),
                Requirements: computeRequirements(ctx, info, offerings, region, amiFamily, kc),
                Offerings:    offerings,
-               Capacity:     computeCapacity(ctx, info, amiFamily, nodeTemplate.Spec.BlockDeviceMappings, kc),
+               Capacity:     computeCapacity(ctx, info, amiFamily, nodeTemplate, kc),
                Overhead: &cloudprovider.InstanceTypeOverhead{
                        KubeReserved:      kubeReservedResources(cpu(info), pods(ctx, info, amiFamily, kc), eniLimitedPods(info), amiFamily, kc),
                        SystemReserved:    systemReservedResources(kc),
@@ -131,12 +131,19 @@ func getArchitecture(info *ec2.InstanceTypeInfo) string {
 }

 func computeCapacity(ctx context.Context, info *ec2.InstanceTypeInfo, amiFamily amifamily.AMIFamily,
-       blockDeviceMappings []*v1alpha1.BlockDeviceMapping, kc *v1alpha5.KubeletConfiguration) v1.ResourceList {
+       nodeTemplate *v1alpha1.AWSNodeTemplate, kc *v1alpha5.KubeletConfiguration) v1.ResourceList {
+
+       var storage resource.Quantity
+       if nodeTemplate.Spec.LaunchTemplateName != nil {
+               storage = resource.MustParse("1000Gi")
+       } else {
+               storage = *ephemeralStorage(amiFamily, nodeTemplate.Spec.BlockDeviceMappings)
+       }

        return v1.ResourceList{
                v1.ResourceCPU:               *cpu(info),
                v1.ResourceMemory:            *memory(ctx, info),
-               v1.ResourceEphemeralStorage:  *ephemeralStorage(amiFamily, blockDeviceMappings),
+               v1.ResourceEphemeralStorage:  storage,
                v1.ResourcePods:              *pods(ctx, info, amiFamily, kc),
                v1alpha1.ResourceAWSPodENI:   *awsPodENI(ctx, aws.StringValue(info.InstanceType)),
                v1alpha1.ResourceNVIDIAGPU:   *nvidiaGPUs(info),

Obviously, the storage = resource.MustParse("1000Gi") was just for my env.
Steps to Reproduce the Problem
try to schedule any pod with ephemeral-storage requests > 20Gi and Karpenter won't match it to a instance.
    resources:
      requests:
        cpu: "4"
        ephemeral-storage: 30Gi
        memory: 16Gi

Resource Specs and Logs
Bunch of log messages like this:
2023-03-10T21:19:14.289Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "karp-prov1", no instance type satisfied resources {"cpu":"4600m","ephemeral-storage":"20Gi","memory":"17536Mi","pods":"1"} and requirements topology.kubernetes.io/zone In [us-west-2b], karpenter.k8s.aws/instance-size In [12xlarge 16xlarge 24xlarge 2xlarge 4xlarge and 3 others], karpenter.sh/capacity-type In [on-demand], kubernetes.io/os In [linux], karpenter.sh/provisioner-name In [karp-prov1], kubernetes.io/arch In [amd64], karpenter.k8s.aws/instance-family In [c5 c6i m6i r5 r6i

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

@thelabdude Do you have the ability to migrate away from using the launch template value and use the fields that Karpenter uses to discover some of this info i.e. blockDeviceMappings? We are thinking about deprecating the launchTemplate field in the AWSNodeTemplate as part of the upgrade to v1beta1 so we're generally recommending that users move to the new format if they can.

The reason I'm using launchTemplate is our userData section is quite complicated to construct (3-4 cloud-init scripts + several shell scripts). We already have infra that contructs a LaunchTemplate with all the necessary userData sections. Maybe my use case is unique in this regard? Ability to point to an existing LaunchTemplate in my infra seemed like a nice feature of Karpenter.
I guess I'm missing why Karpenter can't just call into the AWS API to get the blockDeviceMappings from the LT? Looking at the EC2 API, seems like it would just be a call to describe-launch-template-versions for the $Latest or $Default version. What other "sharp edges" (mentioned in the link you provided) exist when using LaunchTemplates (I've only encountered this one).
The blockDeviceMapping approach in AWSNodeTemplate may not be quite right anyway because the EBS root volume size (+ IOPS, throughput, etc) are somewhat dependent on the size of the instance that gets provisioned. One can fit a lot more pods on a 16xlarge than on an xlarge (obviously), so it follows that I'd need a bigger root EBS vol to service more emptyDir requests. I wouldn't want to provision a 1TB gp3 with 16000 IOPS for an xlarge but I may need that for a 16xlarge instance. How does Karpenter address this problem today?

A couple of the other "sharp edges" that maybe aren't mentioned in that doc are the lack of multi-architecture support with launch templates. We are limited to only support whatever architecture that the launch template specifies.
Maybe we could discover the architecture that the launch template AMI uses to constrain any provisioners that use that launch template, but you are still limited in the workloads that you can deploy through the launch template.

The blockDeviceMapping approach in AWSNodeTemplate may not be quite right anyway because the EBS root volume size
For scaling the EBS volume size, we are tracking a feature request to be able to scale the ephemeral-storage requests based on the pod requests that are needed #2394. You could imagine that we could potentially add a fixed overhead to this blockDeviceMapping size in the future if it was needed.

yes, I hit the arch issue today but solved with a separate provisioner for graviton ... however, I think I've solved my complex userData problem and am going to migrate away from LaunchTemplate and specify all my needs in the AWSNodeTemplate directly.

I actually spoke too soon, trying to construct the userData string from Pulumi is proving to be a bit challenging :-( this is why we have data structures vs. just a string blob!

Can you share more details about what specific issues you are hitting that aren't great/workable in the userData string section?

I'm not constructing the AWSNodeTemplate YAML manually, trying to use Pulumi's k8s.apiextensions.CustomResource and the resulting YAML looks to have all the \n escaped improperly, etc. I'm not sure the correct approach for trying to take a big string clob and fit into a YAML string.
Ideally, AWSNodeTemplate would just take a base64 encoded value for userData as an option and then decode it in Karpenter's eksbootstrap.go. Maybe as another option in the CRD, such as userDataBase64?

@thelabdude I'm pretty against adding additional api-surface, giving users two paths to the same solution if there isn't a big technical hurdle that's causing us to need to do this. Is the main pain-point here that you will have to go back and escape all of the \n values to make it work? Is there any technical limitation to the current string format for userData?

I think allowing base64 encoded would be a nice addition. Other than the giant ugly chunk of multi-line string in my YAML, I actually tracked the problem down to Karpenter expecting:
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="PULUMI_MIME_BOUNDARY"

but our userData had:
Content-Type: multipart/mixed; boundary="PULUMI_MIME_BOUNDARY"
MIME-Version: 1.0

What's weird is EC2 LaunchTemplates have no issue with the order of those being swapped, the userData section works either way, so I'm not sure if this a bug in our infra (I don't control the code that generates userData like this) or if the order doesn't actually matter?
Swapping the order of those two header lines gets this working, so I'll close this issue for now.

fwiw ~ I heard from some internal Pulumi experts that our userData section is:
They are rendered using the Go stdlib package for mime

so this requiring userData to start with MIME-Version: 1.0 might actually be a Karpenter bug!


[FLINK-33694][gs-fs-hadoop] Support overriding GCS root URL (backport to 1.17)

This is a backport of #23836 to 1.17.

@flinkbot run azure

@XComp having trouble getting a clean CI run for this one. First failure appeared to be a transient connectivity issue; second time, the task "Test - connect_1" failed with:
Jan 18 11:23:52 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.4.1:shade (shade-flink) on project flink-sql-connector-hbase-1.4: Error creating shaded jar: /__w/1/.m2/repository/commons-codec/commons-codec/1.15/commons-codec-1.15.jar (No such file or directory) -> [Help 1]

Is it possible for jobs to step on each other's local Maven repos?
@flinkbot run azure

I checked the logs. We had disk space issues with runners today (FLINK-34135, FLINK-34098). I suspect that the failures where caused by this (all of it is kind of related to IO issues). :thinking:


app.bundle.js Failed to load resource: the server responded with a status of 404 (Not Found)

Hello, i followed the steps you wrote, when opening the app on my mobile, i get white screen. After ionic serving on my desktop, i get the error from the title:
http://localhost:8100/build/js/app.bundle.js Failed to load resource: the server responded with a status of 404 (Not Found)

Hi @skater19, The steps on the repo are now outdated (since Ionic RC4 is released now). But seeing that some people are still using it, I'll update it today to the latest version and ping you when it done!

@skater19 I suggest you try, please follow the steps again for a clean install and let me know how it goes


Publish v16.0.0-rc.1

All custom exceptions are marked as obsolete
Animation inherits from FileBase

/azp run develop


Timeout poll global

Pull Request Test Coverage Report for Build 589396305

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 27.811%

Totals

Change from base Build 587525433:
0.0%

Covered Lines:
1558

Relevant Lines:
5602

💛  - Coveralls


external dictionary, PSQL: No message received

┌─version()─┐
│ 18.12.17  │
└───────────┘

/etc/odbc.ini
[DEFAULT]
Driver = NAME

[NAME]
Description         = PostgreSQL connection to NAME db
Driver              = PostgreSQL Unicode
Database            = DBNAME
Servername          = HOST
UserName            = USER
Password            = PASSWORD
Port                = 5432
Protocol            = 10.03
ReadOnly            = No
RowVersioning       = No
ShowSystemTables    = No
ConnSettings        =
SSLmode             = require

/etc/odbcinst.ini
[PostgreSQL ANSI]
Description=PostgreSQL ODBC driver (ANSI version)
Driver=psqlodbca.so
Setup=libodbcpsqlS.so
Debug=0
CommLog=1
UsageCount=1

[PostgreSQL Unicode]
Description=PostgreSQL ODBC driver (Unicode version)
Driver=/usr/lib/x86_64-linux-gnu/odbc/psqlodbcw.so
Setup=libodbcpsqlS.so
Debug=0
CommLog=1
UsageCount=1

Еrrors appear in the log
/var/log/clickhouse-server/clickhouse-server.log
2018.10.11 23:37:42.175835 [ 43 ] {7f266ad7-8ae8-4b85-8678-7cc80afe44ac} <Error> ExternalDictionaries: Cannot create external dictionary 'campaigns' from config path /etc/clickhouse-server/psql_dictionary.xml: Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = No message received, e.what() = No message received
2018.10.11 23:37:52.206453 [ 43 ] {7f266ad7-8ae8-4b85-8678-7cc80afe44ac} <Error> ExternalDictionaries: Cannot create external dictionary 'advertisers' from config path /etc/clickhouse-server/psql_dictionary.xml: Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = No message received, e.what() = No message received

ii  clickhouse-client                   18.12.17                                   all          Client binary for ClickHouse
ii  clickhouse-common-static            18.12.17                                   amd64        Common files for ClickHouse
ii  clickhouse-server                   18.12.17                                   all          Server binary for ClickHouse
ii  clickhouse-server-base              18.12.17                                   amd64        DEPRECATED PACKAGE (use clickhouse-common-static): Server binary for clickhouse

No problem only in version 18.4.0. In the versions 18.5.1, 18.6.0 errors are different. At the same time, nothing changed between the versions.

ii  libiodbc2:amd64                     3.52.9-2                                   amd64        iODBC Driver Manager
ii  libodbc1:amd64                      2.3.1-4.1                                  amd64        ODBC library for Unix
ii  odbc-postgresql:amd64               1:10.03.0000-1.pgdg16.04+1                 amd64        ODBC driver for PostgreSQL
ii  odbcinst                            2.3.1-4.1                                  amd64        Helper program for accessing odbc ini files
ii  odbcinst1debian2:amd64              2.3.1-4.1                                  amd64        Support library for accessing odbc ini files
ii  unixodbc                            2.3.1-4.1                                  amd64        Basic ODBC tools
ii  unixodbc-dev                        2.3.1-4.1                                  amd64        ODBC libraries for UNIX (development files)

Solution: enable the ability to connect to PSQL without SSL and remove from config
/etc/odbc.ini line:
SSLmode = require

But in the old version, it works with SSL:
SELECT version()

┌─version()─┐
│ 18.4.0    │
└───────────┘

Through isql also works without problems.

We've figured out the root cause and the way to fix it.


No way to attach preventDefault modifier to Form component.

When using the Form component, hitting enter will trigger an on:submit but since there is no way to attach a |preventDefault to the event, it will cause a reload. The relevant errors are:
Event modifiers other than 'once' can only be used on DOM elementssvelte(invalid-event-modifier)
Argument of type '"submit|preventDefault"' is not assignable to parameter of type '"submit"'.ts(2345)

@jaeming Is there any specific reason why you want to use <Form> instead of the <form>?

@laxadev I assumed I should use the Form component since it was available. I can just use native <form> in this case. But maybe since this component does exist it would be useful if there was some documentation around the submit event, like that you will need to invoke your own preventDefault in most cases for your submit handler. It looks like it's a limitation of Svelte when it comes to using modifiers on events on custom components. Another alternative is providing a prop for invoking preventDefault. I found this Stackoverflow here on the topic: https://stackoverflow.com/questions/69630422/svelte-how-to-use-event-modifiers-in-my-own-components
I like this 2nd option: <Form preventDefault on:submit={handleSubmit}>
If that is something the maintainers would consider I am happy to put in a PR for it.


Video extract

If we use our own video dataset, or directly use openpose to extract the 2D joint positions to generate a json format file, can we replace the original json file and directly perform style transfer? How many bone points does the json file extracted from your video dataset contain?

Thanks for your interest! Our code deals with json files generated using OpenPose with --hand option. Here we convert the raw OpenPose output to a 2D skeleton corresponding to the CMU skeleton we used in training. Note that you may want to set reasonable mean and std poses and replace the default mean/std pose here.

Thanks for your interest! Our code deals with json files generated using OpenPose with --hand option. Here we convert the raw OpenPose output to a 2D skeleton corresponding to the CMU skeleton we used in training. Note that you may want to set reasonable mean and std poses and replace the default mean/std pose here.

Thank you very much for your reply! I would like to ask what do you mean and STD mean? And how did you get the NPZ format file you used in the folder 'data/ readmill_norm/test2d.npz'?

Thank you very much for your reply! I would like to ask what do you mean and STD mean? And how did you get the NPZ format file you used in the folder 'data/ readmill_norm/test2d.npz'?

During training, our motion input is normalized ((X-mean(X))/std(X)) before being fed into the network. Here mean(X) and std(X) are computed over the training dataset. Ideally mean(X) would be an "average pose" w/o bias from any style.
The normalization step is also done for the test inputs. Our test2d.npz is computed over all extracted 2D skeletons in this youtube video using the code here

During training, our motion input is normalized ((X-mean(X))/std(X)) before being fed into the network. Here mean(X) and std(X) are computed over the training dataset. Ideally mean(X) would be an "average pose" w/o bias from any style.
The normalization step is also done for the test inputs. Our test2d.npz is computed over all extracted 2D skeletons in this youtube video using the code here

Question 1: I want to experiment with my own video, because I am not very familiar with openpose, you already have a very mature and powerful operation technology process, so can you please share the specific method of extracting video joint points using openpose or related websites? ?
Question 2: The result of your style transfer synthesis action is a BVH format file. Is there any visual code? Just like the generated result on your article homepage? Could you please share with me?
Thank you very much!

Question 1: I want to experiment with my own video, because I am not very familiar with openpose, you already have a very mature and powerful operation technology process, so can you please share the specific method of extracting video joint points using openpose or related websites? ?
Question 2: The result of your style transfer synthesis action is a BVH format file. Is there any visual code? Just like the generated result on your article homepage? Could you please share with me?
Thank you very much!

Sure. The way to get json files is to simply run
./build/examples/openpose/openpose.bin --video examples/media/video.avi --hand --write_json output_json_folder/

as specified in the OpenPose repo
For BVH visualization, you can directly use blender for a quick visualization. For rendering, please refer to the relevant section here in our repo.

Sure. The way to get json files is to simply run
./build/examples/openpose/openpose.bin --video examples/media/video.avi --hand --write_json output_json_folder/

as specified in the OpenPose repo
For BVH visualization, you can directly use blender for a quick visualization. For rendering, please refer to the relevant section here in our repo.

Thank you very much for your reply! Does the visualization of the BVH file generated in the demo_results folder require a GPU? Is it necessary to run the code under Linux operating system?

Thank you very much for your reply! Does the visualization of the BVH file generated in the demo_results folder require a GPU? Is it necessary to run the code under Linux operating system?

You're welcome :)
GPU is not required. But the visualization code is only tested under Linux & maxOS. I'm not sure whether it works under Windows.

You're welcome :)
GPU is not required. But the visualization code is only tested under Linux & maxOS. I'm not sure whether it works under Windows.

Which version of Openpose did you use to extract 2D nodes of human body and then generate JSON files? Is it running under Windows? Do you need a GPU?

We used OpenPose 1.5.1, but I don't think the version matters here since the output formats are the same. The latest version should also work. We ran it on Ubuntu w/ a GPU. The step is basically the following in my previous comment. There are no other steps other than this.
./build/examples/openpose/openpose.bin --video examples/media/video.avi --hand --write_json output_json_folder/

If you go over OpenPose's readme you should find a similar script here. For more details, you can consult their doc.


Can you provide a sample Json of grafana dashboards?

Can you provide a sample Json of grafana dashboards?

Hi :wave:
Sorry I don't, it's been a while since I last used this library and I didn't think of saving my previous dashboards.
If you create a dashboard with ginprom as its datasource, I'll gladly accept a pull request to add it as an example in the repository :smile: Otherwise I'll try to recreate one with an example app when I'll have some time.


Where can I upload and get JSon and JSON schema file?

I have no experience with JSON and trying to understand this project.
can you help me with following questions?

Where can I upload my own JSON file (myJson.json)?
which particular file in the this project generating the JSON schema and after completion Where does the JSON Schema file goes?

Thanks,

For usage questions please use mailing list:
https://groups.google.com/g/jackson-user
But as to your question; did you actually go through README?
This is not a command-line tool but rather tool to create JSON Schema that represents given Java object type(s).
So you cannot upload anything.
As README says:
Example Usage

ObjectMapper mapper = new ObjectMapper();
// configure mapper, if necessary, then create schema generator
JsonSchemaGenerator schemaGen = new JsonSchemaGenerator(mapper);
JsonSchema schema = schemaGen.generateSchema(SimpleBean.class);

This will yield a java POJO representing a JSON Schema, which can itself easily be serialized with jackson, or configured with java.

So you get a Java object and then if you want JSON version, use Jackson ObjectMapper like so:
String json = new ObjectMapper().writeValueAsString(schemaObject);


Remind users to notice update resources permission

When use new SP to update Cluster credentials , it might not update related resources in diff RG automatically and caused access issue, remind users do not forget to do the steps manually if those resources not put in the same resource group.

@newgamer1117 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

hi there :
Just want to know if there is any concern about the merge request.

@mlearned - Hi, could you review the proposed changes to your article? Thanks.

#please-close

#please-close

doc has now evolved , will take feedback separately

doc has now evolved , will take feedback separately

Got it, expect the doc will update to provide better description and correct information for user asap.

Got it, expect the doc will update to provide better description and correct information for user asap.


[BackgroundAudioTask Sample] Why remove handlers when App suspends?

Hey,
Is there any particular reason why the handlers get removed when the App suspends?
What would happen if you don't remove them?
Kind Regards,
Stefan

I would have thought that it was because it could cause memory leaks and cause your application to get terminated quicker due to memory constraints.

If the app is suspended, it cannot respond to the events immediately. The events will buffer up, and then when the app resumes, all the events will get spit out at once. This will overwhelm the app with stale information. This can cause the app to try to react to things that happened a long time ago, display error messages for things that aren't applicable any more, etc. Better is simply to turn off the faucet.

Thank's for the information!

If I remember correctly there is one more thing that is particular to background audio, which is that a background task can sometimes be canceled while an app is suspended. If that happens then when the app resumes the foreground may get a different proxy the next time it calls BackgroundMediaPlayer.Current and so events might fire for a stale instance. There is a picture of the architecture in this document that may be helpful.
https://msdn.microsoft.com/en-us/library/windows/apps/mt282140.aspx
There were are also cases in the past where the process lifetime manager would terminate a suspended foreground application if a background task sent messages to it and that is one of the reasons the sample goes out of its way to track the state of the foreground application through isolated storage.


3.6 Compatibility

In the README, it says compatibility with puppet < 3.5.
Is this module known to not work with Puppet? Why not? What kind of work would have to be done?

@maxbucknell This actually works with all Puppet versions since 2.7, closing this.

@tPl0ch Will you update the README to indicate this compatibility? I came upon this issue with the same question.


I cannot access

Hi,
I wanted to test https://zzzcode.ai/javascript/code-explain. My script was about 8000 chars so I logged in using my GitHub account. Once logged in, I was redirected to https://sqlfiddle.com/???
I think this is a bug.
BR,
Glenn

Hello @GlennBonde ,
Thank you for reporting. I indeed have the same behavior.
I'm currently working on it.
Best Regards,
Jon

Hello @GlennBonde ,
The issue should be fixed.
Let me know if the login is now working as expected (redirecting to the right website).
Best Regards,
Jon


[drone] repo connector missing org. prefix

When passing a token to drone import, the org-level SCM connector is created . The resulting connectorRef is missing the org. prefix.
The repo connector currently downgrades to:
  properties:
    ci:
      codebase:
        build: <+input>
        connectorRef: github
        repoName: drone-testing

But since it's at the org level, it should be:
  properties:
    ci:
      codebase:
        build: <+input>
        connectorRef: org.github
        repoName: drone-testing

Fix in #84


Write: Kernelised linear regression

(to add to the gp.tex)
Consider linear regression with a basis function
y = w^\top \phi(x) + b
and recall the kernel trick:
k(x_i, x_j) = \dotprod{\phi(x_i)}{\phi(x_j)}
Derive the resulting predictor for a test point, and compare with the GP regressor.

Make a note about heteroscedastic data.

Aim is to prove equivalence of predictions with GP.

Completed in 3afeb3b.


Documents lost in Consumer during target Solr restart.

This modified test illustrates a scenario when target Solr node(s) go missing (for example due to a crash, a forced restart, or connectivity issues) BUT at the same time the Zookeeper remains online.
The test fails because it looks like some of the documents are lost by the Consumer, even though the failed_resubmit code path should resubmit them back to Kafka and they should be picked up later when Solr is back online.

Taking a look.

Good catch, big hole that that test only tests dropping zk and not Solr.
I'm just wrapping up a fix.
Appears to be caused by batching multiple Kafka records to a SolrRequest to send to Solr, but on failure, adding back just the last Kafka record, so of course you loose the previous records in the batch.

If I'm not mistaken this has been fixed in PR 75? if so then this can be closed.


Audit compatibility dates/flags

Which Cloudflare product does this pertain to?
Workers
Existing documentation URL(s)
https://developers.cloudflare.com/workers/configuration/compatibility-dates/
What changes are you suggesting?
At least one is missing http_headers_getsetcookie (https://github.com/cloudflare/workerd/blob/c6c5445358cb6e34387dcd5cb3015b9d5c2e44c8/src/workerd/io/compatibility-date.capnp#L275-L278).
Additional information
No response

Also urlsearchparams_delete_has_value_arg, it seems #9235 just never happened. I couldn't understand why I was getting new TS types that didn't correspond to any published compatibility date.


fixup the api-approved annotation

The previous pr in our api-approved.kubernetes.io annotation did not include a review from the members of the sig-network-api-approvers group.  This PR is the original API implementation PR that was reviewed/approved by Tim Hockin, the core of the API hasn't really chaged since then. For future releases with major API changes we will ensure that the API is properly reviewed.
Please see https://github.com/kubernetes-sigs/network-policy-api/pull/143#issuecomment-1759926132 for more information on this
cc @thockin @liggitt

/hold
Until Tim/Jordan look at this

Poke @thockin @liggitt

@liggitt we've spoken with the chairs and will not cut an official release without an ACK from them 👍

@astoycos : Any updates on this one? I'd love a minor release since now nodes has merged and I plan on getting cidrs merged as well. If not I can continue using the commitID not a big deal.

@tssurya If you could LGTM it I think we're good to go!!


Stack memory don't work

Describe the bug
Regiter r16 is not a array but the Stack Pointer
The stack is another memory in the IC
In your debug r16 is a array

In the IC you have
Device: d0 at d5
Register: r0 at r17
Stack: array length 512
you can see here https://stationeering.com/tools/ic

SP value 5

We can see where is the SP in the Stack
To Reproduce
This code must put -1301215609 in r0
# Tutorial: stack
# Alias Register
alias Hash r0
alias Choose r1 # Dial setting
start:
yield
move Choose 5
jal getValues
s db Setting Hash
j start

getValues:
move sp 0
push<PHONE_NUMBER> # Lead Ingot
push 252561409 # Charcoal
push -404336834 # Copper Ingot
push -929742000 # Silver Ingot
push 226410516 # Gold Ingot
push -1301215609 # Iron Ingot
push -1406385572 # Nickel Ingot
push -290196476 # Silicon Ingot
push -654790771 # Steel Ingot
push 502280180 # Electrum Ingot
push -82508479 # Solder Ingot
push<PHONE_NUMBER> # Constantan Ingot
push -297990285 # Invar Ingot
push 412924554 # Astroloy Ingot
push -787796599 # Inconel Ingot
push 156348098 # Waspaloy Ingot
push<PHONE_NUMBER> # Hastelloy Ingot
push -1897868623 # Stellite Ingot
add sp Choose 1 # Add 1 to read value
pop Hash
j ra

becareful with stack command

To put a value at the index 0:
move sp 0
push 1234

To read a value at the index 0 you must move the pointer index+1:
add sp 0 1
pop r0

Thank, for your feedback, i was stupid :). I update Stack system and add foreach to icX.

hi
that work fine :)


modify rnn_train.py script, vad_gru and denoise_gru will use relu as …

…activation, so it matches the paper

Doing so will prevent the kernel from using cuDNN version of GRU, defaulting to the generic implementation. That in turn will severely slow down the training (assuming you're using GPU for the training).


Add support for shield mounted ds18b20

Add support for shield mounted ds18b20 temperature sensor.  Marked T on the OpenTherm Master Shield.

I don't think there are any changes needed in this component to support that. You can already add the Dallas sensor to the configuration and use that as the sensor in the pid climate (for example).
Sidenote: I have tried using the shield mounted sensor, but since my "thermostat" (the ESP8266 and shield running ESPHome with this component) is now located next to the boiler, the readings weren't actually that useful to me. I instead scattered a few inexpensive zigbee thermometers throughout the house, so that we no longer run the heater based on the temperature in just one room.

Thanks you for the information.  I'll take the opportunity to thank you for creating this module too, works incredibly well.  Very much appreciated.


[Bug Report] When seeking an MKV format video on iOS, the error "Seek failed" occurs.

plugin version：
media_kit: ^1.1.8
media_kit_video: ^1.2.1
media_kit_libs_video: ^1.0.3

[MacOS,IOS]
When playing MKV videos (1080P or 2160P) on iOS, there is a high probability of encountering the error "Seek failed" when trying to seek. It keeps buffering for about 20 seconds or even longer before starting playback, and sometimes it gets stuck and doesn't play at all. This issue does not occur with MP4 videos. Could you please explain what might be causing this? Thank you!
log：
flutter: player.stream.log :PlayerLog(prefix: ffmpeg, level: error, text: Seek failed (to<PHONE_NUMBER>2, size -78))
flutter: player.stream.log :PlayerLog(prefix: mkv, level: error, text: Corrupt file detected. Trying to resync starting from position<PHONE_NUMBER>8...)
flutter: player.stream.log :PlayerLog(prefix: mkv, level: error, text: Cluster found at<PHONE_NUMBER>7.)

Corrupt file detected


Can't commit a container inside which Docker has been installed: no space left on device

Hi all,
I just stumbled upon an issue with committing containers while going through the process of building a Docker image. I have been through that process in the past and it worked, so this sounds like a regression (post 0.9, unfortunately can't be more precise at this point).
The problem is that Docker is installed inside the container, and this creates a /var/lib/docker/devicemapper/devicemapper/data file that is 100G big (a fake file of course, but not in the eyes of docker commit it seems). When exiting the container and then committing it, it will start using up all the available disk space on the host and eventually fail with a no space left on device error.
If I manually remove /var/lib/docker from within the container, the docker commit succeeds. Note that this problem does not appear when Docker is installed in non-privileged mode, supposedly because Docker cannot start at the end of the install to create the devicemapper file. So this doesn't happen unless you use RUNP apt-get install lxc-docker, or installing Docker from within a container started with --privileged.
I think this is a problem with docker commit and whatever it does to create the image, which I'm guessing is not much more than making a tarball of some sort out of the rootfs of the container. Maybe some missing options to the tar command being used to avoid tripping itself on a "fake" 100GB file?
Host is Ubuntu Trusty, running Docker 1.2.0 on a 3.13.0-35 kernel.

ok, so DinD has tricky caveats and while it stays as a goal and we work toward it, there are plenty of permutations that are yet to be confirmed as supported. With devicemapper allocating a block device by default there are things, like space allocation, that can go awry. I'll go ahead and close this, but encourage the conversation to continue so we can get a working example of DinD with devicemapper. Some resources/configurations you'll want to look at is the dm.loopdatasize and dm.loopmetadatasize storage options (https://github.com/docker/docker/blob/master/daemon/graphdriver/devmapper/README.md) or some other combination of configurations. Until then, happy hunting.


Make sure everything gets a name

check instances and volumes

In  885bc75 I've gone through the list on http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html and added a "Name" tag to everything that allows it: It seems like only Instances give this special treatment in the UI.


Python syntax highlighting

I would like to add python syntax highlighting using. rich text for beautiful formatting in the terminal. - This would make it easier to read from the console.

@Timfrazer cool idea, looking forward to the PR

I worked on this issue as I had never used rich and syntax highlighting before.
PR #3 ready!

Sweet thanks @jarviscodes, I will review later ...

@bbelderbos I think this can be closed now since #3 got merged!


Issue with tf.estimator.export.ServingInputReceiver()

System information

I run my project on a Jupyter Notebook on GCP
TensorFlow version: 1.15
Python version: 3.5.3

Describe the current behavior
I followed every instruction to build a serving_input_receiver_fn(). Valliappa Lakshmanan provides his solution to me but it still does not work. I believe it is not the problem of the codes but some unknown issue.
Describe the expected behavior
I do not expect any error in creating and exporting this simple serving function. But when I run it, there are error messages. Despite the errors, I can still use the exported model for prediction.
Code to reproduce the issue
def serving_input_receiver_fn():
inputs = {
'job' : tf.compat.v1.placeholder(dtype = tf.string, shape = [None]),
'marital' : tf.compat.v1.placeholder(dtype = tf.string, shape = [None]),
......
}
return tf.estimator.export.ServingInputReceiver(inputs, inputs)
Other info / logs
INFO:tensorflow:'serving_default' : Classification input must be a single string Tensor; got {'job': <tf.Tensor 'Placeholder:0' shape=(?,) dtype=string>, 'marital': <tf.Tensor 'Placeholder_1:0' shape=(?,) dtype=string>, ...
WARNING:tensorflow:Export includes no default signature!

@psyyip
This issue is more suitable for TensorFlow Serving repo. Please post it on Serving repo from here. Thanks!

moved to TensorFlow Serving repo


Roman Numeral Converter

Project title
Roman_Numeral_Converter
Project Description
A Converter that changes roman to numeral.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript
[ ] ReactJS

/assign


Forms and Pickers don't seem to be working

Documentation says there should be picker and form components:
https://dev-int.teams.microsoft.com/storybook/main/index.html?path=/story/ui-templates-forms--kitchen-sink
https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/design/design-teams-app-basic-ui-components#picker
https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/design/design-teams-app-ui-templates#form
Are these not available in the SDK? If so, it should probably be noted in the documentation.
If they are available, could you post a quick example?
Much thanks!

Hi @BrendanAndrade, apologies for the delay.
The Form component doesn’t yet implement the picker designs you linked, though that may come in a future release. It does implement single- and multi-select dropdowns with simple string options. The example for Form available in the “Playground” linked in the Readme demonstrates all the types of input Form currently supports.
Essentially this library implements most of the UI Templates designs seen in the Microsoft Teams UI Kit in Figma's Community: https://www.figma.com/community/file/916836509871353159/Microsoft-Teams-UI-Kit


feat(AListItem): add classes when there is click event

This change avoids adding class="states:10 cursor-pointer" or value props to AListItem to make it highlightable.
See here this comment.

Hi,
This PR additionally adds the hover feedback on each list item including those that shouldn't be clickable.

I studied how vue handles this and the best way to resolve this is by letting vue handle the events.
In the latest commit, AListItem no longer emits a custom event, click on the list item will emit a native click event (docs).
Moreover, we will gracefully handle this change in AList so that we get the expected behavior.
Thanks for bringing this detail to light 🙏🏻


multiple query start same time

for some reason one of the following snippets works and the other does not
does not work:
func acronymHandler(_ req: Request) throws -> Future<View> {
    return try req.parameter(Acronym.self).flatMap(to: View.self) { acronym in
        return try flatMap(to: View.self, acronym.creator.get(on: req), acronym.categories.query(on: req).all()) { creator, categories in
            let context = AcronymContext(title: acronym.long, acronym: acronym, creator: creator, categoires: categories)
            return try req.leaf().render("acronym", context)
        }
    }
}

works:
func acronymHandler(_ req: Request) throws -> Future<View> {
        return try req.parameter(Acronym.self).flatMap(to: View.self) { acronym in
            return acronym.creator.get(on: req).flatMap(to: View.self) { creator in
                return try acronym.categories.query(on: req).all().flatMap(to: View.self) { categories in
                    let context = AcronymContext(title: acronym.long, acronym: acronym, creator: creator, categoires: categories)
                    return try req.leaf().render("acronym", context)

                }
            }
        }
    }

thinking maybe this is caused by MySQL not supporting starting two queries at once?

This still seems to be an issue. MySQL state machine blows up if two queries are started at the same time.

Yep just retested this and hit the same issue

Shouldn't the PushStream prevent the 2 queries from being executed at the same time?

So hitting this in another place that wasn't happening before when doing return try flatMap(to: HTTPStatus.self, req.parameter(Acronym.self), req.parameter(Category.self)) { acronym, category in - this returns the error [ ERROR ] FluentError.modelNotFound: No model with ID 1 was found (Model.swift:267)
An important thing to note is that any subsequent requests never get fulfilled, every one just hangs and times out, even simple Fluent .all() functions
I'm assuming this is all about to be rewritten with the NIO changes however!


[M] DUP Facility-specific messaging in JOFFRE EMAILS: confirmation and reminder

Description:
We need to create facility specific messaging in confirmation emails for JOFFRE DUP bookings via GC Notify. Since Joffre has 1 facility  this will only require an update to the text
Acceptance Criteria:

[ ] Update text as shown in the the figma
[ ] Revise confirmation emails for Joffre according to approved plain text found in this figma file: https://www.figma.com/design/2lQW8InOa0lEiUiMeGmeNC/Day-Use-Pass?node-id=4789-1888

Trail Pass wording updates - figma links
Joffre:
Confirmation Email
Reminder Email -Note: this covers all trails
Development Checklist:

[ ] ...
[ ] ...
[ ] ...

Dependencies

Blocked by #344
Blocking

Relevant documentation as reference
Definition of Ready

[ ] Acceptance criteria are included
[ ] Wireframes are included (if applicable)
[ ] Design / Solution is accepted by Product Owner (if applicable)
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

confirmation email messaging needs to be simplified

@ndelraye  Could you please review this ticket and let me know if it makes sense? I wasn't 100% what the templates referred to (should that be in a diff ticket? Is that the same thing as the messaging??)

Developer note - to hurry this change along we have updated two GCN templates:

Sample Trail Pass: since Joffre is the only Trail Pass in PROD, Joffre users are the only people who will receive this email
Sample Reminder email: all users receive this email but the changes are minor so it was deemed acceptable.

To clarify, we haven't implemented any kind of facility-specific messaging. Our GCN templates currently differ whether or not the pass is for parking or for trail use. Cleverly, since Joffre is the only trail pass, we've changed the trail pass to be Joffre specific. We will implement facility specific messaging in a future ticked once the DUP SAM changes are complete.
@manuji I have currently only made the changes in TEST. Once you approve test I will copy the changes into PROD and you can test again. thanks

@cameronpettit  missing the following line under "Visitor Guidelines" section.

Tested on TEST: Passed

This change is ready to be done on the PROD environment @cameronpettit .
Passing to PO review.

Thank you!.

Taking the ticket back to QA until we finish updating the PROD.

Tested on PROD: Passed

verified that this task has been completed.
Passing to PO review.

FYI @cameronpettit

Moving to done.


Backport "HBASE-28346: Expose checkQuota to Coprocessor Endpoints (#6066) (addendum) (#6350)" to branch-2

Add default implementations of the new methods so that a custom implementation of RegionCoprocessorEnvironment will not fail to compile after upgrade.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  0s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 35s

branch-2 passed

+1 :green_heart:
compile
3m 36s

branch-2 passed

+1 :green_heart:
checkstyle
0m 42s

branch-2 passed

+1 :green_heart:
spotbugs
1m 51s

branch-2 passed

+1 :green_heart:
spotless
1m  0s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 20s

the patch passed

+1 :green_heart:
compile
3m 33s

the patch passed

+1 :green_heart:
javac
3m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 43s

the patch passed

+1 :green_heart:
spotbugs
2m  3s

the patch passed

+1 :green_heart:
hadoopcheck
23m 25s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m  9s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 15s

The patch does not generate ASF License warnings.

50m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6351/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 7538a8c4a7c6 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f13d42345fa28bc27e78428c0cb8644fc91e9f5f

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

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

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 17s

branch-2 passed

+1 :green_heart:
compile
0m 57s

branch-2 passed

+1 :green_heart:
javadoc
0m 28s

branch-2 passed

+1 :green_heart:
shadedjars
5m 56s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  6s

the patch passed

+1 :green_heart:
compile
0m 57s

the patch passed

+1 :green_heart:
javac
0m 57s

the patch passed

+1 :green_heart:
javadoc
0m 27s

the patch passed

+1 :green_heart:
shadedjars
5m 55s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
208m 11s

hbase-server in the patch passed.

234m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6351/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 57baa278d71c 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f13d42345fa28bc27e78428c0cb8644fc91e9f5f

Default Java
Eclipse Adoptium-17.0.11+9

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

Max. process+thread count
4365 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 54s

branch-2 passed

+1 :green_heart:
compile
1m  6s

branch-2 passed

+1 :green_heart:
javadoc
0m 40s

branch-2 passed

+1 :green_heart:
shadedjars
7m  3s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 47s

the patch passed

+1 :green_heart:
compile
0m 59s

the patch passed

+1 :green_heart:
javac
0m 59s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed

+1 :green_heart:
shadedjars
7m  0s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
248m 33s

hbase-server in the patch passed.

279m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6351/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 06f49878dd2f 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f13d42345fa28bc27e78428c0cb8644fc91e9f5f

Default Java
Eclipse Adoptium-11.0.23+9

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

Max. process+thread count
4255 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

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

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.


CONSOLE-3654: console-plugin-template repository should support localization

Links to: https://issues.redhat.com/browse/CONSOLE-3654
Adds possibility to generate locales in the console-plugin-template repo.

/retest-required

  1) Console plugin template test
       "before all" hook for "Verify the example page title":
     CypressError: `cy.exec('cd ../../console-plugin-template && /tmp/helm upgrade -i console-plugin-template charts/openshift-console-plugin -n console-plugin-template --create-namespace --set plugin.image=registry.build01.ci.openshift.org/ci-op-q9b5jsxw/pipeline@sha256:619b1c4b96723afa7f5e21994f8c8c2abf7ca8450b508a07aee2a9aeac392061')` timed out after waiting `60000ms`.
https://on.cypress.io/exec
Because this error occurred during a `before all` hook we are skipping the remaining tests in the current suite: `Console plugin template test`
Although you have test retries enabled, we do not retry tests when `before all` or `after all` hooks fail

/retest

/retest

/test e2e-aws-plugin-template

/retest

{Operator unavailable (null): operator is not reporting conditions  Operator unavailable (null): operator is not reporting conditions}
{  openshift cluster install failed with cluster creation}
{  openshift cluster install failed overall}

/retest

QE Approver:
/assign @yanpzhan
Docs Approver:
/assign @opayne1
PX Approver:
/assign @RickJWagner

/label px-approved

/label docs-approved

I run the plugin using a local development environment by:
In one terminal window, run:
yarn install
yarn run start
In another terminal window, run:
oc login
yarn run start-console
Then access "localhost:9000/example?pseudolocalization=true&lng=en", could see contents are marked for i18n.

@Mylanos If there others I need to check for the US?

I run the plugin using a local development environment by: In one terminal window, run: yarn install yarn run start In another terminal window, run: oc login yarn run start-console Then access "localhost:9000/example?pseudolocalization=true&lng=en", could see contents are marked for i18n.  @Mylanos If there others I need to check for the US?

I'm sorry but I'm not sure if I understand correctly, could you please clarify the question?

@Mylanos I mean except the check in above screenshot , if there are any other checkpoints I need to test for the feature from the pr code.

@Mylanos I mean except the check in above screenshot , if there are any other checkpoints I need to test for the feature from the pr code.

That's pretty much it, other than that the features that this PR brings is the locale/translations files and contents get automatically generated from source codes via yarn i18n, so you can check if all the strings inside the source code get translated after you remove the locale files. But that is closely tied with the check if all the strings on the example page are marked for i18n.


Bitbucket commit URL has typo

with setting gitblame.commitUrl = "guess" it takes the following URL pattern at my bitbucket repos:
https://bitbucket.org/{repoTeam}/{repoName}/commit/{commitHash}
but it's "commits"
https://bitbucket.org/{repoTeam}/{repoName}/commits/{commitHash}
I tried to setup a custom URL but there is no variable for the repository name or team.
Would be nice to either have the "commits" fixed or these additional variables available in the commitUrl settings :)

Greetings Fabian.
You are looking for the gitblame.isWebPathPlural setting.


Create an environment with an adversarial setting

The implementation of these environments is an essential part of the project.
Several configurations may be available:

1 vs 1 symmetrical
n vs m symmetrical
1 vs 1 asymmetrical
n vs m asymmetrical

It will also be interesting to consider the possibility of making the environment partially observable and/or with incomplete information.


Transactions

Hello!!
I'm trying to use with transactions, but it seens that every time i call the execute function, the statment is committed.
The following code is not giving any error in the statment "BEGIN TRANSACTION". However the "COMMIT" statment is not running, it says that need to start a transaction first.
const ADODB = require('node-adodb');
const connection = ADODB.open('Provider=Microsoft.ACE.OLEDB.12.0;Data
 Source=Database1.accdb;Persist Security Info=False;');`

const testTransaction = async() => {
    try {
        await connection.execute("BEGIN TRANSACTION");
        await connection.execute("COMMIT");
    } catch (err) {
        console.log(err);
    }
};

testTransaction();

Is there any other way to do this?
Thank you and congrats for the package, awesome!

Up
I also hitting a snag on this one. My current project requre me to connect to old school foxpro rather than mdb.  Connecting to vfpolede and query is very crisp. But, things not really goes well when executing insert.  The solution is we need to alter null on each columns (which is not permited by my client) or SET NULL OFF before executing the INSERT. I tried but fail.
async exec ()  {
try {
await conn.execute("SET NULL OFF")
await conn.execute("INSERT INTO employees('code', 'name') VALUES ('123', 'test')")
} catch (err) {
console.log(JSON.stringify(err))
}
}
When run no error, but value not inserted to table.
I aslo tried:
await conn.execute("SET NULL OFF; INSERT INTO employees('code', 'name') VALUES ('123', 'test')")
but no luck.
Hope there is other way todo this?

Hello!!
I'm trying to use with transactions, but it seens that every time i call the execute function, the statment is committed.
The following code is not giving any error in the statment "BEGIN TRANSACTION". However the "COMMIT" statment is not running, it says that need to start a transaction first.
const ADODB = require('node-adodb');
const connection = ADODB.open('Provider=Microsoft.ACE.OLEDB.12.0;Data
 Source=Database1.accdb;Persist Security Info=False;');`

const testTransaction = async() => {
    try {
        await connection.execute("BEGIN TRANSACTION");
        await connection.execute("COMMIT");
    } catch (err) {
        console.log(err);
    }
};

testTransaction();

Is there any other way to do this?
Thank you and congrats for the package, awesome!

@franciscojunqueiralima  Try this fork. anasyy/node-adodb  Come with transactions.

@franciscojunqueiralima Try this fork. anasyy/node-adodb Package come with transactions. Work great!
 let inserts = []
 await conn.executeTrans(inserts)

Awesome man, i'm going to check it out. Thank you!

Sorry, the lib not yet support transaction, but it a good suggest.


Handle insertReplacementText input event

I hadn't any trouble in my local test. When the insertReplacementText input event is fired, the editor already had the new content, we only need to update the new content from the rust model.
Sadly, I can't use the replace_text method, the browser handles the selection and the new string differently in the spellchecking case.


Fix ME conduit crash on NeoForge

Description
Due to a bug, older versions of NeoForge never called onCreated, so we had to do it manually. Now that the bug is fixed, the code is instead calling onCreated twice. This PR just ignores further calls to onCreated if onRemoved hasn't been called.
Details on the crash are in the linked issue:
Resolves #569

Checklist:

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you).
[x] I have performed a self-review of my own code.
[x] I have commented my code in areas it may be challenging to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes are ready for review from a contributor.

Does this break support for Forge? If so we should ensure that we are running in neoforge before changing the behaviour. I think for 1.20 we should remain focussed on forge as a target for modpack sakes

Does this break support for Forge?

Forge is unaffected because it calls onCreated and onRemoved the correct amount of times. The other change in getGridNode is just because it makes more sense to return null than make a new node that won't ever be create()d.

Actually, looking through it again there might be an issue: mainNode.create() is never going to be called if the node was created in deserializeNBT()...
I'm not sure how I should go about fixing that, any ideas?

Checking mainNode.isReady() doesn't work because that's only updated next tick, maybe a boolean needsCreate to check inside onCreated?

could we maybe make extendedconduitdata an abstract class, let it store a boolean, add a final create method that checks the boolean and sets it, and keep onCreated as the method to override. you can then reset the boolean in a final remove method and let it call onRemoved. That would be breaking for addons, but we are in alpha and I'm not aware of any mods that will be affected as of yet as I know of only the enderio kubejs addon that uses the conduits api, but they don't touch ExtendedData.
or, we could check if in ConduitBundle#addType there are no types currently in the bundle, so we know  it was just placed, so we just don't call onCreated there if we are in a neoforge env

make extendedconduitdata an abstract class, ... or, we could check if in ConduitBundle#addType

I'm not sure which of those would be better, especially now that EnderIO is moving to NeoForge, so I'll leave the decision to you. I'm happy to implement any changes you suggest, or you could make the changes to this PR yourself if you think that'd be easier.
Sorry making a half-broken PR, if that deserialize issue had slipped through it might've caused a lot of debugging headaches.

Superseded by #574.


Missing Wyoming Module - Causes Fatal Error

ModuleNotFoundError: No module named 'wyoming'
from wyoming.server import AsyncServer
There should be a wyoming folder that has server.py somewhere. but I couldnt find it. This is why it is causing fatal error.
I couldn't even get it local wake word service started.
Did Author removed the folder or files? Please help.
May 10 00:56:50 satellite1 systemd[1]: Started Wyoming openWakeWord.
May 10 00:56:50 satellite1 run[938]: Traceback (most recent call last):
May 10 00:56:50 satellite1 run[938]:   File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
May 10 00:56:50 satellite1 run[938]:     return _run_code(code, main_globals, None,
May 10 00:56:50 satellite1 run[938]:   File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
May 10 00:56:50 satellite1 run[938]:     exec(code, run_globals)
May 10 00:56:50 satellite1 run[938]:   File "/home/user/wyoming-openwakeword/wyoming_openwakeword/main.py", line 9, in
May 10 00:56:50 satellite1 run[938]:     from wyoming.server import AsyncServer
May 10 00:56:50 satellite1 run[938]: ModuleNotFoundError: No module named 'wyoming'
May 10 00:56:51 satellite1 run[937]: Traceback (most recent call last):
May 10 00:56:51 satellite1 run[937]:   File "/home/user/wyoming-openwakeword/script/run", line 12, in
May 10 00:56:51 satellite1 run[937]:     subprocess.check_call([context.env_exe, "-m", "wyoming_openwakeword"] + sys.argv[1:])
May 10 00:56:51 satellite1 run[937]:   File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
May 10 00:56:51 satellite1 run[937]:     raise CalledProcessError(retcode, cmd)
May 10 00:56:51 satellite1 run[937]: subprocess.CalledProcessError: Command '['/home/user/wyoming-openwakeword/.venv/bin/python3', '-m', 'wyoming_openwakeword', '--uri', 'tcp://<IP_ADDRESS>:10400']' returned non-zero exit status 1.

found the reason for this and fixed it completely. closing thread

found the reason for this and fixed it completely. closing thread

You didn't close it


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.447

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.447


Windows 11: VScode crashed (reason: 'oom', code: '-536870904'

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.92.2
OS Version: Windows 11 Pro, Version 23H2, OS build: 22631.4037
System RAM: 64GB
GPU: NVidia GeForce RTX 3080, Driver: 560.81

Steps to Reproduce:

Start writing code.

Attempted Fixes:

Verified that VScode folders are not being uploaded to OneDrive (or any other cloud backup providers)
Deleted all VScode and Project cache files
Deleted VScode backups
Deleted .vscode from App folder
Deleted Windows temp files
Removed all extensions
Excluded VScode from Windows Defender
Verified Large File Optimizations
Changed paging file size from 4096 (Windows auto manage) to 9216 (min) - 196609 (max)
Disabled hardware acceleration

Here is one of the many .dmp files:
c0eba4c2-10ff-48ec-94c9-66b49dd2fdfd.dmp
Crash report preview:

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fffbb82fabc (KERNELBASE!RaiseException+0x000000000000006c)
ExceptionCode: e0000008
ExceptionFlags: 00000081
NumberParameters: 1
Parameter[0]:<PHONE_NUMBER>b1b1c7
PROCESS_NAME:  Code.exe
ERROR_CODE: (NTSTATUS) 0xe0000008 -
EXCEPTION_CODE_STR:  e0000008
EXCEPTION_PARAMETER1:<PHONE_NUMBER>b1b1c7
STACK_COMMAND:  ~0s; .ecxr ; kb
SYMBOL_NAME:  code+b55379
MODULE_NAME: Code
IMAGE_NAME:  Code.exe
FAILURE_BUCKET_ID:  APPLICATION_FAULT_e0000008_Code.exe!Unknown
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
IMAGE_VERSION:  <IP_ADDRESS>
FAILURE_ID_HASH:  {203dc02c-fd4a-1c4e-3e48-6581c93eb6d2}

I have started seeing this issue periodically as well. I can't tell if it's an extension leaking, debug window filling up, or something else. I'm guessing it's not a real oom, since when I see the crash dialog my machine has tons of free ram available, (some) vscode process is still running, and none of the vscode specific processes look oversized in task manager. There's no indication of a crash in windows event viewer either. I see this issue happen when I leave my machine for a while / overnight and return to do further work - this hasn't happened to me while actively using VSCode.

This keeps happening to me whenever I interact with the terminal window
Version: 1.96.0-insider (user setup)
Commit: 28f7008e9b2799e3004c48c26fff3d02ec8f13d8
Date: 2024-11-15T05:04:10.294Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

@carschandler can you attach the crash dump https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

Thanks for the dump file @carschandler , the oom is from the javascript heap limit. Can you try this as next step to get a heap snapshot,

Close any open instances of the application
Start the application with code --js-flags="--heap-snapshot-on-oom" --verbose
When the window closes due to oom you should see a log line Wrote heap snapshot to ..
Please attach the generated file to this issue

@deepak1556
Most of the time, the issue presents itself as a frozen window, followed by the option to reload it or exit. Eventually I did get the oom error again but did not get a message about writing the snapshot... is there a standard Windows directory it would be written to for me to check?
I have been unable to reproduce it for the past several hours but I'll update this if I get it again with a successful snapshot dumped.
Here's the output around the time I got the message (I think)

It should write to the current directory where the executable was run. I am not sure why you don't see the log line, let me confirm on my side as well and get back.


Changes to better sync with the mkiocccentry repo

If MKIOCCCENTRY_USE is defined, then code will compile as if it was
under the mkiocccentry repo:
https://github.com/ioccc-src/mkiocccentry

These changes sync with mkiocccentry's iocccsize v28.8 2022-02-20.
In particular, the following files are after applying these
mkiocccentry repo commits:
mkiocccentry commit 407979f97257b0093c900cd4697d35ce897c979a
mkiocccentry commit a50f486f68301cf1d16035a2896ae825afd4dc61
mkiocccentry commit 59bc18cf550b5471a74d153f9e3fb496008df515
mkiocccentry commit d5d46d506aa447adabc8e72f8929a9c85b58b369
mkiocccentry commit e35269401d6bbe4825895ac7e1367c5b18a13bb8
mkiocccentry commit 8786f03538cda741f5fe59cabedc3f464e982936

and the following files in this pull request will be identical
in both repos.
iocccsize-test.sh
iocccsize.c
iocccsize.h
iocccsize_err.h
rule_count.c

While the default for DIGRAPHS and TRIGRAPHS remains defined (true)
as far as iocccsize.h, in this pull request, code was added to
iocccsize-test.sh and detect if there exists limit_ioccc.sh.  The
iocccsize-test.sh has been modified to test if DIGRAPHS and/or
TRIGRAPHS are defined.  The Digraph and Trigraph tests now work
both with and without DIGRAPHS / TRIGRAPHS being defined.
The test directory used by iocccsize-test.sh was changed from
test to test-iocccsize.  This is consistent with mkiocccentry repo
where a number of tools have their own test-xxx directory.
The iocccsize-test.sh script will exit 0 if all is well,
or exit 1 if at least 1 test failed.
The err.h file was renamed iocccsize_err.h.
The iocccsize_err.h include file was modified so that if iocccsize
is compiled with dbg.c and dbg.h (and linked with dbg.o), then the
mkiocccentry error, warning and debug facility is used.  In this
pull request, no dbg.c nor dbg.h is supplied.  The makefile does
not link with dbg.o.  Unless MKIOCCCENTRY_USE is defined, dbg.h is
not included.
In order to avoid name space conflicts, the code uses the following
function name:
iocccsize_warnx(...)
iocccsize_errx(ex, ...)
iocccsize_dbg(level, ...)

The iocccsize_err.h, if MKIOCCCENTRY_USE is defined translates those
iocccsize_xxx() functions into mkiocccentry error, warning and debug
facility.  If MKIOCCCENTRY_USE is not defined, then those iocccsize_xxx()
functions are translated into portable fprintf() and fputc() calls.
Removed macros for unused error, warning and debug calls.
The iocccsize command line is now:
usage: iocccsize [-h] [-i] [-v level] [-V] prog.c
usage: iocccsize [-h] [-i] [-v level] [-V] < prog.c

-i		ignored for backward compatibility
-h		print usage message in stderr and exit 2
-v level	set debug level (def: none)
-V		print version and exit 3

The iocccsize -v command line flag was changed to "-v level" in order
to be consistent with all of the other mkiocccentry tools.
By default,the Rule 2b count is written to stdout.
If the debug level is > 0, then the Rule 2a, Rule 2b,
and keyword count is written to stdout instead.
Moved the rule_count() function set was moved from iocccsize.c
into a new rule_count.c file.  This is to allow the mkiocccentry
repo to call the rule_count() function directly.
The iocccsize tool no longer writes its input to output.
The iocccsize-test.sh no longer assumes the source file
will be written to stdout.  The stand-alone iocccsize now
only prints Rule 2b size by default.
The iocccsize-test.sh no longer prints 'Nothing to be done for'
lines during the test.
The rule_count() function, unless the '-v level' is given on
the command line, does not print anything.  This is consistent
with how mkiocccentry tools uses the rule_count() function.
Broke up the usage message string into two parts in order
to be compatible with C compilers that do not support string
constants longer than 511 characters.
Exit codes have been changed to:
0 - source code is within Rule 2a and Rule 2b limits
1 - source code larger than Rule 2a and/or Rule 2b limits
2 - -h used and help printed
3 - -V used and version printed
4 - invalid command line
>= 5 - some internal error occurred

The usage message documents these exit codes.
Updated README.md to reflect the new usage message.
Updated the Rule 2a constant (was MAX_SIZE. now RULE_2A_SIZE), and
the Rule 2b constant (was MAX_COUNT, now RULE_2B_SIZE) to be
consistent with the values from limit_ioccc.h in the mkiocccentry
repo.  If MKIOCCCENTRY_USE is defined, then limit_ioccc.h (not
included in this repo) defines will cause RULE_2A_SIZE and RULE_2B_SIZE
values from limit_ioccc.h to be used instead.
The word buffer size was expanded to 256.
The RuleCount typedef includes warning booleans used by
the mkiocccentry tool.  The iocccsize.c code will issue
warnings (via iocccsize_warnx()) accordingly.
The iocccsize version, by default is "unofficial iocccsize version".
When compiled with MKIOCCCENTRY_USE, the iocccsize version
takes on the version defined by the mkiocccentry repo.
Fixed a case where some user's system did not correctly
reopen stdin as the file argument stream.  The iocccsize.c
now does an fopen() on the file argument and passes that stream
to setvbuf() and rule_count().
Added /ooo/ to support the seqcexit tool.
Fixed use of non-standard %zu format.
While the makefile is not part of the mkiocccentry repo,
we added a clobber rule as a alias for distclean.
Added a ${WERROR} to make is easy to compile with -Werror
(however the default remains to not use -Werror),
The make distclean clobber rule removed macOS *.dSYM cruft.
In order to compile on several system platforms, including macOS,
we had to comment out the #${PROJ}$E rule lines and instead
use a iocccsize rule to compile.  These lines are marked with:
# XXX - gross hack - fix me - XXX

Without those lines, for example, macOS would fail to make.
For example, the original makefile would fail as follows:
$ make distclean all
rm -f iocccsize.i iocccsize.o *.stackdump *.core 2>/dev/null
rm -fr iocccsize test a.out VERSION 2>/dev/null
cc -g -std=c11 -Wall -Wextra -Wno-char-subscripts -pedantic  -DWITH_MAIN -o .c
clang: error: no input files
make: *** [iocccsize] Error 1

Fixed various typos and hopefully did not add many more.  :-)

Expect a followup pull request to address some minor compiler portability and testing issues we discovered.

Updated pull request:
Changes to better sync with the mkiocccentry repo #2
These changes sync with mkiocccentry's iocccsize v28.9 2022-02-23.
Fixed a number if shellcheck discovered issues (portability and shell
script safety related).
Corrected a problem where iocccsize-test.sh in non-verbose mode
failed on some platforms.
Changed -v to -v level to be compatible with mkiocccentry repo use.
Fixed and updated the usage message.
Added -h option to iocccsize-test.sh to print help / usage message.
Documented iocccsize-test.sh exit codes.
Added -V to be compatible with mkiocccentry repo use.
Avoided problematic C symbols that start with __.
Minor comment and whitespace cleanup.

Whoa.   Lots to digest and I think I'll be addressing the above in multiple comments as we discuss.  I can't accept the Pull Request as a whole, since I have some concerns.
First a simple one:
%zu does appear in C11 standard onwards, not sure about C99 since I only have C89, C11, and C2x draft (2019) to check against.  I am assuming iocccsize and related tools will be built with current compilers that default to current (or current-1) standard.  How far back are we to maintain standard compatibility?  While C89 is great milestone over K&R, I think C11 should be the minimum now and that the code should avoid as much history (technical debt) cruft.  As the tools move forward, maybe git tag the commit / version where minimum support changes, rather than try be all-in-one for all time.

Is it your intent to change Rule 2b from 2053 to 2503 for the next contest?

Is it your intent to change Rule 2b from 2053 to 2503 for the next contest?

Yes, 2053 ==> 2503.

Whoa. Lots to digest and I think I'll be addressing the above in multiple comments as we discuss. I can't accept the Pull Request as a whole, since I have some concerns.
First a simple one:
%zu does appear in C11 standard onwards, not sure about C99 since I only have C89, C11, and C2x draft (2019) to check against. I am assuming iocccsize and related tools will be built with current compilers that default to current (or current-1) standard. How far back are we to maintain standard compatibility? While C89 is great milestone over K&R, I think C11 should be the minimum now and that the code should avoid as much history (technical debt) cruft. As the tools move forward, maybe git tag the commit / version where minimum support changes, rather than try be all-in-one for all time.

As for %zu, due to problems with implementations that we encountered, we switched away from its use.
Please understand that we are proving you with this pull request as a courtesy: to help you understand the differences between our official code base and your repo.
You might consider, applying it to this alternate non-master branch.  Alternately you might wish to clone the mkiocccentry repo and just track that if you wish.
If you are not interested in there pull requests, let us know.  It is not our intent to bother you with code changes you might not be interested in.
Thanks again for the iocccsize concept!

I've accepted the majority of the changes, but reimplemented many.  I think you'll approve.  You should see an updated branch tonight or tomorrow.

Thanks, we will be happy to look at the result.  Let us known when it is ready by adding a comment to this pull request, if you please.

You are free to accept or reject the pull request, of course, as you wish.  While some of the items you mention in the comment above are interesting, enough of differences won't be implemented in our mkiocccentry repo so as to not warrant a further merge.
We will keep a diff should there be a further need to sync later on.
Thanks again and best wishes.