has-error class when validation

Hi all,
I'm using react-form in my project, but i can't see class 'has-error' append when form validate like example of React-form below:

My form just display error message only and not append any class error. Please help me for this issue.
I'm missing something config?

The code on the example pages does not include the presentational logic.
You should read the complete example source:
https://github.com/erikras/redux-form/blob/gh-pages/5.2.5/src/examples/SubmitValidationForm.js

Thanks @ooflorent :)


Documentation Error (which can cause dev issues)

Describe the bug
Go to the documenation on this page:
https://platform.openai.com/docs/api-reference/chat/create?lang=node.js
Select the model and the language to be Node.
You will see in the instructions the following line:
  messages: [{"role": "system", "content": "You are a helpful assistant."}, {role: "user", content: "Hello world"}],

clearly in the first object, the property role is wrapped in "" as well as the property content. But not in the second object
To Reproduce
Go to the documentation
Code snippets
N/A

OS
Windows 11
Node version
Node 18.12.1
Library version
v3.3.0

That's valid JavaScript.

Yeah probably - typescript of course had kittens. Magic string stuff for javscript - not sure that it is appropriate either way to show it like that.


Fuzzer found an error in deserialization

base64 of a module
AGFzbQEAAAABAAAABAQEBAQEBAQEBCoKBA0EBAQEBAQEBAQEBAQKCg==
thread '<unnamed>' panicked at 'attempt to subtract with overflow', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/parity-wasm-0.20.0/src/elements/section.rs:221:28

https://github.com/paritytech/parity-wasm/blob/a597cdb15d6d9a62c4e8856e9c884543449a18f5/src/elements/section.rs#L221

This is funny payload
With release optimizations it does not panic but leads to 4GB allocation


Migration of userEvent.type events to fireEvent.change

Background
userEvent library introduces errors when triggering type events on inputs of type="date". Currently the SimpleReport application cannot upgrade the userEvent dependency to the latest because 4 unit tests get broken.
Action requested
Migrate the userEvent.type event to fireEven.change to avoid the new introduced issues in the latest version of userEvent dependency
Acceptance Criteria
All frontend unit test must pass

@fzhao99 a potential workaround for this


added parameters

Added docstring and additional parameters as per api specs.

Does this close #2? If so, should update PR description with "Closes #2"


Get webpage to work fine in mobile browsers

Is your feature request related to a problem? Please describe.
Currently though the webpage works, some parts like Konveyor logo and others don't display right.
Describe the solution you'd like
Clean up and fix UI
Describe alternatives you've considered
The page is usage.

I have updated the Konveyor logo. Looks like the issue is resolved now.

Can you please check it once @ashokponkumar?

Yes, I don't closed this issue after meeting your pr. Good work. Thanks

Thank you. :-)


Feat: Switch on order import and my collection flag for android

The type of this PR is: Feature

This PR resolves []
Description

Switch on AREnableMyCollectionAndroid
Switch on AREnableMyCollectionOrderImport
Add echoflag key for AREnableSplitIOABTesting

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Switch on order import and my collection flag for android - kizito

This PR contains the following changes:

Dev changes (Switch on order import and my collection flag for android - kizito)

  Generated by :no_entry_sign: dangerJS against 11efcd63cdd4a6744bf2ddd2b17d365b94c64e86


Packaging captive runtime: If separate section is not created for platform, it packages as shared runtime

Or in another words, it seems like this line from wiki:

When an application uses captive runtime, we can create separate sections for each platform to specify different options.

should be: we should/must create ?
Because, if you have this in asconfig.json:
"airOptions": {
		"output": "bin/MainBundleFolder", // this way only Shared Runtime package is available
		/*
                this way one has package as Captive Runtime task AND as Shared Runtime
                "windows": {
			"output": "bin/MainBundleFolder"
		}, */
		"signingOptions": {
			"storetype": "pkcs12",
			"keystore": "C:\\dev\\cert\\my-selfsigned-2048-RSA-cert.p12"
		}
	}

there is no Captive Runtime task available:

and released package name is output + ".air" added. In this case "MainBundleFolder.air" appears in bin folder. So, one must/needs to create separate section per platform to have Captive Runtime task.
Also, related issue, if one creates separate section, in order to have package as Captive Runtime, like this:
"airOptions": {
		"windows": {
			"output": "bin/MainBundleFolder"
		},
		"signingOptions": {
			"storetype": "pkcs12",
			"keystore": "C:\\dev\\cert\\my-selfsigned-2048-RSA-cert.p12"
		}
	}

and opens Tasks -> Run task, this is visible:

and if Shared Runtime is selected, this error appears:

no such file C:\dev\my-project\Main.swf

Yes, if one sets asconfig for Captive Runtime, why it would click Package Shared Runtime, but maybe that task should not be visible? So no confusion can happen.

In that statement, "can" is correct because you are supposed to be able to specify the target field in the root of airOptions, and set it to "bundle" (it's better to have separate windows and mac sections, but it's not required). However, it appears that I've accidentally removed target as a valid property at the root of of airOptions in the asconfig.json schema, so this doesn't work at the moment. I'll get it fixed, and that statement will be correct again.

and if Shared Runtime is selected, this error appears:

I'll investigate and get this fixed.


Reconstruction result

Dear authors, thanks for your work. I tested the two models on my pictures, but the results seems not good. Is there anything wrong? thanks for you attention. Here are the two original pictures.

And the reconstruction using the IN128_Base:

And the reconstruction using  the IN256_Base:

Also, as describe in the README, the model achieves 0.39 rFID for 8x downsampling, but it seems the provided model is 4x downsample? There is no 8x downsample model in the links. Thanks for your help!

Thanks for your interest in our work. We would like to make a further clarification that when training $128 \times 128$ imagenet, our model has three downsampling layers, which means the image will be processed into $16 \times 16$. $16 \times 16$ for quantization is utilized in VQGAN and MAGVIT. Here, as stated in the caption, we use the 8x downsampling model to directly test on $256 \times 256$ images without finetuning, which means it has $32 \times 32$ 2D tokens to align with the paper that adopts 8x downsampling ratio.
The facial reconstruction is quite hard if only trained on imagenet. But with the increase of tokens, it will get better results like directly testing on $512 \times 512$ images directly using the 8x downsampling model.

Thanks for your quick reply, I will close the issue.


Add Nordic Uart Service (NUS) peripheral to examples

Add generic peripheral implementation of Nordic Uart Service (NUS) and add example of it to nrf-sdc.
Has still some TODOs

what hardware do I need to try this out?

are you blocked by anything on finishing this PR that we can help with @plaes?

Cool, no worries, I'll see about taking a look!


Change buildOutDegree to buildOutDegrees

Accommodate change to canonical names:

https://github.com/senzing-garage/knowledge-base/blob/main/proposals/SDKs-for-V4/canonical-names.md#szengine

Pull requests:

https://github.com/senzing-garage/sz-sdk-go/pull/180


Trust Registry Protocol 2.a. #1

credential type URI

Vitor P: Credential Types for shipped COVID credentials might not be URIs and in some cases might not be present.
e.g. EU doesn't have Credential Types.
e.g. W3C VCs allows any string as Credential Type.
Antti K: It's a requirement for GA's to require this from issuers (See 7.a above). As this spec requires compliance with ToIP, then we can and should require the use of credential type URI.
To my knowledge, it is a requirement in ToIP spec to have credential types stored in the utility ledger and have a URI to refer to.
Darrell O: agreed, though Utility "Layer" is more correct.

comments from v1 draft - closing


cost too much memory

i deploy  disk_usage_expoter in k8s cluster. I want to collect disk usage of dir  /var/lib/docker.
my ds is:
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: disk-usage-exporter
spec:
  selector:
    matchLabels:
      app: disk-usage-exporter
  template:
    metadata:
      labels:
        app: disk-usage-exporter
        name: disk-usage-exporter
      name: disk-usage-exporter
      annotations:
        prometheus.io/scrape: "true"
    spec:
      containers:
        - name: disk-usage-exporter
          args:
            - -p=/host/var
            - -l=0
          image: disk-usage-exporter:v0.2.0
          ports:
            - containerPort: 9995
              name: scrape
          volumeMounts:
            - mountPath: /host/var/lib/docker
              mountPropagation: HostToContainer
              name: docker
              readOnly: true
            - mountPath: /host/root
              name: root
              mountPropagation: HostToContainer
              readOnly: true
            - mountPath: /host/proc
              name: proc
      serviceAccountName: default
      tolerations:
        - effect: NoSchedule
          key: node-role.kubernetes.io/master
      volumes:
        - hostPath:
            path: /proc
            type: ""
          name: proc
        - hostPath:
            path: /var/lib/docker
            type: ""
          name: docker
        - hostPath:
            path: /
            type: ""
          name: root

i think the pods use too much  mem .
command ：kubectl  top  pod
disk-usage-exporter-h9d97                   363m          9248Mi
disk-usage-exporter-jfh2p                     2457m        2106Mi
disk-usage-exporter-wvx9c                   2886m        1659Mi

when i curl podIP:9995/metrics , it takes seconds  to get metrics
[root@master]# curl <IP_ADDRESS>:9995/metrics | grep var
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6470    0  6470    0     0    417      0 --:--:--  0:00:15 --:--:--  1449
node_disk_usage_bytes{path="/host/var"} 6.3816163328e+10

and the pod disk-usage-exporter-h9d97  which  cost mem shows  9248Mi   doesn't work, its log is:
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600"
time="2022-04-22T03:25:10Z" level=info msg="setting GC percent to 3, alloc:<PHONE_NUMBER>, free: 318873600

can any one give some help?

@dundee

@Cosrider I have added explicit attempt to free OS memory. Could you try again with the version from master?

ok.

With limited resource
    resources:
      limits:
        cpu: "1"
        memory: 2000Mi
      requests:
        cpu: 100m
        memory: 100Mi

always OOM
# kubectl -n system-monitoring get pod  | grep disk
disk-usage-exporter-4jts8                   0/1     CrashLoopBackOff   215        20h
disk-usage-exporter-nk7sx                   0/1     CrashLoopBackOff   169        20h
disk-usage-exporter-pg782                   1/1     Running            154        20h

without resource limits：
➜  ~ kubectl -n system-monitoring  top pod | grep disk
disk-usage-exporter-7smnl                   3006m        1647Mi
disk-usage-exporter-lf7hs                      12m          156Mi
disk-usage-exporter-qchqc                   1087m        2109Mi

is it possible to lower cpu and memory cost when  analysing ?

These numbers look little bit more reasonable. I am afraid we cannot go much lower right now.
There will be possibility to run with storing the data to disk instead of RAM when https://github.com/dundee/gdu/issues/118 is implemented, but it will take some time.

thanks a lot


Constraints for arrays with non-object types are not validated

The type constraints for the item type is not checked given the schema:
    ArraySchema:
      type: array
      items:
        type: integer
        minimum: 5

This is also the case non-object additional properties


(Alpha) UI component - Circular progress indicator

As a: Full stack developer
I want: Use the "Circular progress indicator" from the UI library
so that: I can spend more time creating features or capabilities that will provide value to my users and stakeholders
Acceptance criteria

[x] Create web component
[x] Create React wrapper
[ ] Passing unit tests
[ ] Linting
[ ] Include in "canvas" web component storybook
[ ] Push to Alpha
[ ] Manual design review
[ ] Ensure that ui-component name and Figma component name are aligned

Presentable outcomes

[ ] I can show the ui-component in Storybook and provide the link to service teams so that they can view the component for themselves

Sprint Ready Checklist

Acceptance criteria defined
Team has defined steps to satisfy acceptance criteria
Acceptance criteria is verifiable / testable
External / 3rd Party dependencies identified

Related issues:
GitHub issue: Blocked by #355
Resources:
Mockups: Circular progress indicator
Testing URL: [If applicable a URL to the testing branch]

Hey @chrisolsen I am just assigning this to you since it looks like you've picked it up.


MudAutocomplete "Required" valiadtion failes when DebounceInterval is high enough and SearchFunc is slow.

Bug type
Component
Component name
MudAutocomplete
What happened?
Autocomplete fails to correctly validate non-empty field if it looses focus faster than DebounceInterval happens. It seems that entered changes are lost when the control looses focus before they applied the value.
The behaviour broke after migrating to 7.x.0. This is a critical bug, since it wrongly reports errors on a correct user input or even resets user input, if form validation is forced.
Expected behavior
MudAutocomplete should correctly validate value after losing focus, even if it happens before DebounceInterval triggered.
Reproduction link
https://try.mudblazor.com/snippet/mkwIOrFKTgrfPOHM
Reproduction steps

Run the example link provided
Type "aaa" in the "US States" field and immediatly click "Save" button.
The typed value will disappear and the field will go into the "Required" error state.

Relevant log output
No response
Version (bug)
7.2.0
Version (working)
6.x.x
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

@danielchalmers I kind of suspect this is the culprit PR https://github.com/MudBlazor/MudBlazor/pull/8787

Not able to reproduce this, could you post a video?

Here you go:
https://github.com/user-attachments/assets/e6a92d4e-7a2a-4c33-86f3-dc47e08a3f3b

Which exact version of 6.x.x does it work on? v6.21.0?

It works okay on 6.19.1. Also I believe it worked fine on other prior 6.x versions too.

I'm going back through commits and it's not working correctly all the way to at least 1d13ea6cdd08cb89148a98c73b1b35edbf4928b1 using the reproduction code provided.
Are you using Blazor Server or WASM? Might be something to do with the coercion.

I am using WASM. Honestly, I saw glitches like ignoring some characters typed before with longer DebounceInterval in 6.x as well. And I had to reduce it to minimize chances of it happenning. However, with 7.2 it definetely got worse by some reason. In the example I put 3 seconds to reproduce it easily. In my app I use 1 second and it almost always works normally with 6.19.1. But with 7.2 it fails near 100% of time with same parameters.

I am using WASM. Honestly, I saw glitches like ignoring some characters typed before with longer DebounceInterval in 6.x as well. And I had to reduce it to minimize chances of it happenning. However, with 7.2 it definetely got worse by some reason. In the example I put 3 seconds to reproduce it easily. In my app I use 1 second and it almost always works normally with 6.19.1. But with 7.2 it fails near 100% of time with same parameters.

Interesting. Something definitely needs to be reworked from the ground up.

The coerced value is set by the debounce timer, but OnBlur stop the timer.
I will try to fix it, by setting the value immediately (not on debounce) when the parameter Immediately is enable.

The v8 is the time to make a breaking change..

If first fixes a problem and it a proper fix, not a workaround like the second one, then defiantly the breaking change is better.

Associated to #9874


fix: managed rulesets changes

Added fixes to Managed Rulesets

:tada: This PR is included in version 0.46.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Compiling With trace_chrome Feature Fails to Select Version

Bevy version
0.12.1
Relevant system information
Running on macOS, but I'm not sure if it's related to that.
What you did
Execute cargo run --release --features bevy/trace_chrome as per the profiling doc.
What went wrong
Received cargo error:
error: failed to select a version for the requirement `profiling-procmacros = "^1.0.13"`
candidate versions found which didn't match: 1.0.8, 1.0.7, 1.0.6, ...
location searched: crates.io index
required by package `profiling v1.0.13`
    ... which satisfies dependency `profiling = "^1"` (locked to 1.0.13) of package `bevy_render v0.12.1`
    ... which satisfies dependency `bevy_render = "^0.12.1"` (locked to 0.12.1) of package `bevy_internal v0.12.1`
    ... which satisfies dependency `bevy_internal = "^0.12.1"` (locked to 0.12.1) of package `bevy v0.12.1`
    ... which satisfies dependency `bevy = "^0.12.1"` (locked to 0.12.1) of package `cjs_whole_new_world v0.0.5 ...`
perhaps a crate was updated and forgotten to be re-vendored?

Cargo.toml
I'll attach this even though I don't think there's anything wrong.
[dependencies]
bevy = "0.12.1"
bitvec = "1.0.1"
bevy_egui = "0.24.0"
leafwing-input-manager = "0.11.2"
noise = "0.8.2"
futures-lite = "2.2.0"
priority-queue = "1.3.2"
itertools = "0.12.0"

Try running cargo update first, then try again.

Deleting the ~/.cargo/registry and rerunning fixed the issue :|


[Keyvault] Remove unused core-arm dependency in keyvault-certificates

The @azure/core-arm dependency in @azure/keyvault-certificates is not being used and so can be removed

cc @sadasant, @jonathandturner


Support ISO-8601 dates

The currently accepted date format is 04/28/18, which requires URL encoding and is region-centric.
The de facto internet standard (and ipso facto international standard) is ISO-8601, e.g. 2018-04-28 or 20180428. Besides following a global standard, these look better in URLs (e.g. https://vacationaccrual.azurewebsites.net/?StartDate=2018-04-29), are unambiguous as to day/month order, and support 4 digit years to prevent bugs when when this software is of course still in use 82 years from now. ;)

Agreed! I will work on the enhancement.

New patch applied.


URGENT: Folder restructure 📢🛠

Description
Create 2 folders. One for python and another javascript.
Put all the python projects inside the python folder and same for js
Inside each language folder put a readme file having a table with the project name, description and author as columns in the table.
All the projects of that language must be listed in the table.

Hello I am interested can I do this?

Sure go ahead. Try to complete asap so that others can follow that style. 👍

I just changed the folder structure ...can you please look into it? then I will go ahead and make the readme file too
https://github.com/TestPrab/code-n-stitch/tree/155-folder-restructure
here is the link


[FEATURE]Scrapping user Ocr software

scrapping can be done from images using ocr software tool
This would extract all data from image present
new unique and optimized approach for extraction
This algorithm is cutting new edge tech way
ocr software is mostly used in Google lens

@RituKumari98 please assign me this issue


feat: onnx2mge add ConvTranspose

onnx2mge支持convtranspose算子

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yingsonglin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


function onactivate does no longer exist

I got the error message that "onactivate" does not exist with the latest HEAD Version. I therefore investigated and found out that since the on() function has been changed, I think this has been forgotten to also be changed in the Java file.

was this a compile-time or run-time issue?

Hey @rjames-acn
It was a run-time issue.

I installed
https://github.com/lkonzen-garupa/cordova-plugin-background-mode
and add the code for wake_lock
https://github.com/katzer/cordova-plugin-background-mode/issues/400#issuecomment-484077499

I installed
https://github.com/lkonzen-garupa/cordova-plugin-background-mode
and add the code for wake_lock
Is working for android 5, 7 and 10 :-)

Thanks


⚠ File access has degraded performance

In b627f5a, File access (https://fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 4202 ms

Resolved: File access performance has improved in 78e764b after 8 minutes.


renderdoc: 1.1 -> 1.2

Motivation for this change
Routine update
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build renderdoc

Looking at the Release Notes i think at least the python extensions need testing.

That would be welcome, but should it block the update?

IMHO updates should be quality assured if deemed necessary.


requirements.txt is missing "pytz"

Chatterbot requires pytz, but it is not installed with pip.
Running the first example new users currently see this:
ModuleNotFoundError: No module named 'pytz'

which version of chatterbot are you using, try to upgrade to latest version ```pip3 install --upgrade chatterbot``

The master branch. pytz is missing in requirements.txt

I was also missing pytz when I installed chatterbot (latest) with pip.

Yes it seems to me the conversion required pytz, meanwhile you could install through pip install pytz

I did install manually, I am reporting the error so you can fix it.

@i3games I proposed a fix in #1670. It was a matter of a quick edit to requirements.txt on the GitHub editor!


Support mutable meta queries in a cluster

Fixes #5612, #5573 and #5518. Partially #2755
Adds support in a multi-node cluster for the following commands:

DROP DATABASE;
DROP MEASUREMENT;
DROP RETENTION POLICY;
DROP SERIES.

The approach is as follows. Queries that involve modifying data on Data Nodes will be handed off by the QueryExecuter to the MetaExecutor. The MetaExecutor will then build appropriate messages and make RPC calls to all data nodes in the cluster.
The node that received the query will apply any commands to its own tsdb.Store locally—they will not be sent over the network.
Errors encountered from remotely executed commands will be collected by the MetaExecutor and the first of these (if any) returned to the user.
Assuming no errors were returned by any data nodes, the node executing the original query will then make any calls necessary to the Meta Store.
Detailed Flow for DROP DATABASE:

HTTP API receives query
HTTP API passes query to cluster.QueryExecutor
cluster.QueryExecutor confirms database exists
cluster.QueryExecutor deletes database on local tsdb.Store
cluster.QueryExecutor tells cluster.MetaExecutor to execute the statement
cluster.MetaExecutor creates an executeStatementRequestMessage RPC command which is sent to cluster.Service on all other data nodes.
cluster.Service dispatches command to cluster.Service.processExecuteStatementRequest
cluster.Service.processExecuteStatementRequest unmarshals the request, parses the statement, and passes it to cluster.Service.executeStatement
cluster.Service.executeStatement switches on the statement type and calls appropriate tsdb.Store.DeleteDatabase.

Errors propagate back from each node through RPC to the node that executed the statement on the cluster and that node returns failure if any node fails to execute.

cluster.QueryExecutor tells meta.Client to delete the database

TODO

[x] Provide more useful errors?
[x] Fix some broken tests.
[x] Remove logging / println / commented out litter.
[x] Update CHANGELOG.
[x] Squash stuff down.

Minor comments, otherwise lgtm :+1:

:trophy:


Allowing files to have . in name

I had some trouble with files with "." in name so I made a fix.
>>> import os
>>> text_filepath = "/foo/bar/other.some.txt"
>>> os.path.basename(text_filepath).split('.')[0]
'other'
>>> os.path.splitext(os.path.basename(text_filepath))[0]
'other.some'

Thanks for the fix!


Syntax highlighting for nested /* */ broken

Currently this doesn't highlight correctly:
/*

/* This function does something*/
let someCode () => {
  ()
}
*/

The inner comment breaks the highlighting

The quick fix would be just allow multiline comments to contain mutliline comments. but iirc it has a side effect. I'll take a look

The quick fix would be just allow multiline comments to contain mutliline comments. but iirc it has a side effect. I'll take a look


MRN Mac

Hi All, hi @Z-H-Sun,
The patcher for MRN mac doesn't seem to work anymore. I tried on the 14.1.2 that was working before and on the new 14.2. After patching using a sudo command, the software starts and then closes immediately... Not sure why!
Any idea how to solve that issue?
Thanks a lot!

Well it is probable that the patch has been intentionally blocked by the developer. C’est la vie. But without running a test I cannot identify what happens. Unfortunately I have been quite busy recently. So I would suggest that you revert to 14.1 for now. I will keep you posted once I get a chance to work on it

Thanks a lot! I did try to revert to 14.1 and now get the same issue... maybe because I upgraded my iOS to the last one? I get a “kill:9” issue when I try to launch the software through the terminal.
Anyway, I’d be more than grateful for any help :)

De : CS_CCME<EMAIL_ADDRESS>Envoyé : Sunday, November 15, 2020 10:46:36 PM
À : Z-H-Sun/CS_CCME_Posts<EMAIL_ADDRESS>Cc : klfaustbe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [Z-H-Sun/CS_CCME_Posts] MRN Mac (#3)
Well it is probable that the patch has been intentionally blocked by the developer. C’est la vie. But without running a test I cannot identify what happens. Unfortunately I have been quite busy recently. So I would suggest that you revert to 14.1 for now. I will keep you posted once I get a chance to work on it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Z-H-Sun/CS_CCME_Posts/issues/3#issuecomment-727650610, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYPGBHZ665NEB2EM5QQ22LSQBK4ZANCNFSM4TWOMKZQ.

Ok, I might know what is happening. Please uninstall and reinstall MNova, first of all. DO NOT use the patcher! Run MNova once and see if it can be opened (at this time, it is not activated yet, but it is okay and we need this step). THEN, try running the patcher followed by MNova.
This is because MacOS will check the digital signature of the app. After modifying the binary executable, the signature will be of course corrupted. If you do not allow macOS to run the check before patching , it will block the “untrusted” app.
Let me know if this works out. If not , please attach a screenshot of the patcher

Hi,
I did actually run Mnova alone first.
So here is what is happening now :
With 14.2 and 14.1.2 – once Mnova is patched, the red opening sign comes up then immediately closes.
With 14.1.0 and sometimes 14.1.2 too, patched MNova opens but then seems to freeze, I can move the windows around but I can’t click on anything – it’s irresponsive. Then if I try to reopen it it doesn’t work anymore.
Again, a huge thank for your help, this is really helpful in these stressful times!
<EMAIL_ADDRESS>De : CS_CCME<EMAIL_ADDRESS>Répondre à : Z-H-Sun/CS_CCME_Posts<EMAIL_ADDRESS>Date : lundi 16 novembre 2020 à 01:43
À : Z-H-Sun/CS_CCME_Posts<EMAIL_ADDRESS>Cc : klfaustbe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [Z-H-Sun/CS_CCME_Posts] MRN Mac (#3)
Ok, I might know what is happening. Please uninstall and reinstall MNova, first of all. DO NOT use the patcher! Run MNova once and see if it can be opened (at this time, it is not activated yet, but it is okay and we need this step). THEN, try running the patcher followed by MNova.
This is because MacOS will check the digital signature of the app. After modifying the binary executable, the signature will be of course corrupted. If you do not allow macOS to run the check before patching , it will block the “untrusted” app.
Let me know if this works out. If not , please attach a screenshot of the patcher
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Z-H-Sun/CS_CCME_Posts/issues/3#issuecomment-727684754, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYPGBHLUYNQ6FEJ2AJUYYDSQB7TLANCNFSM4TWOMKZQ.

I’m not sure if that helps,
But if I try to run the MestRenova (patched) through the terminal I get the following messages.
For 14.1.0
<EMAIL_ADDRESS>For 14.1.2 I get a “killed 9” what ever that is
<EMAIL_ADDRESS>Again, thank you!
De : CS_CCME<EMAIL_ADDRESS>Répondre à : Z-H-Sun/CS_CCME_Posts<EMAIL_ADDRESS>Date : lundi 16 novembre 2020 à 01:43
À : Z-H-Sun/CS_CCME_Posts<EMAIL_ADDRESS>Cc : klfaustbe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [Z-H-Sun/CS_CCME_Posts] MRN Mac (#3)
Ok, I might know what is happening. Please uninstall and reinstall MNova, first of all. DO NOT use the patcher! Run MNova once and see if it can be opened (at this time, it is not activated yet, but it is okay and we need this step). THEN, try running the patcher followed by MNova.
This is because MacOS will check the digital signature of the app. After modifying the binary executable, the signature will be of course corrupted. If you do not allow macOS to run the check before patching , it will block the “untrusted” app.
Let me know if this works out. If not , please attach a screenshot of the patcher
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Z-H-Sun/CS_CCME_Posts/issues/3#issuecomment-727684754, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYPGBHLUYNQ6FEJ2AJUYYDSQB7TLANCNFSM4TWOMKZQ.

I finally had a chance to run a quick check on the new versions of MNova. The logic of verification process has changed in recent versions, unfortunately. The latest version that can be patched is 14.1.0 (tested on my macOS 10.14). Please try 14.1.0 and LMK if it works.
I can't guarantee of coming up with a workable patch for 14.2 in the near future. Maybe it would be simple. Who knows?

It is also possible that the MNova team also modified the contents of previous version. So I am attaching a copy of 14.1.1 that I downloaded earlier. It is this version that I tested successfully with the patch. This copy is authentic and is not modified (not patched), and you can verify its digital signature. You can then try if the patch is successful.
https://drive.google.com/file/d/1EjpmGG6G2W7XJ2kLO_u1UMGSyugIEBmw/view?usp=sharing

Also FYI, direct reply to the email does not include attachments such as images correctly. If you want to show me some pictures, please comment here on GitHub.

Thanks a lot for your help! I really appreciate it! Let’s hope that the V14.2 will be patchable :)

De : CS_CCME<EMAIL_ADDRESS>Envoyé : Saturday, November 21, 2020 4:34:54 AM
À : Z-H-Sun/CS_CCME_Posts<EMAIL_ADDRESS>Cc : klfaustbe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [Z-H-Sun/CS_CCME_Posts] MRN Mac (#3)
Also FYI, direct reply to the email does not include attachments such as images correctly. If you want to show me some pictures, please comment here on GitHub.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Z-H-Sun/CS_CCME_Posts/issues/3#issuecomment-731507326, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYPGBCILZP5M5MBYRQLYL3SQ47O5ANCNFSM4TWOMKZQ.

Sooooo I tried it on 14.1 and MNova does open this time! However, after a few seconds, if you try to do anything (open a file, draw a structure, etc.) it freezes completely and I have to kill the process to get out.

That is weird. I have not been met with such issues on my end. I think maybe we can do the following: We exchange our patched MestReNova executable (Show package contents -> Contents -> MacOS -> MestReNova), and find 1) if they have difference 2) what will happen if replacing our own with each other's (you may need to chmod +x <path/to/>MestReNova after downloading).
Mine (patched) is shared through this link: https://drive.google.com/file/d/16uPDLkEpsLBelv3Nhi6n4Hk4yp5pquxt/view?usp=sharing

That's strnage! I have two macs and both have the same issue... Also they both had the 14.2 patched with the "old" patch from your website and it was working even though the patch showed an error when run.
I wonder if this is because both mac have been upgraded to the new iOS... I'm attaching my file here.
MestReNova.zip

I do experience the same freeze with your file... I think this must be an issue with MacOs Big Sure

I checked the hash values and your file is exactly the same as mine. That means the patch is working properly. It is possible that older versions of MNova is not compatible with the latest macOS. The "error messages" you mentioned seems not a huge issue: I had those as well, and they are more of warning messages from QT instead of errors.
To quickly check the compatibility, please try running the unpatched version:
cd /Applications/MestReNova.app/Contents/MacOS
chmod +x MestReNova.bak
./MestReNova.bak

Now, it is not activated. Ignore verification errors, try drawing a molecule (should work like activated version) and opening an NMR spectrum file (should prompt that you do not have activated NMR plugin), and see if the window freezes.

It's working fine :) So the issue seems to be between the patched version and MacOs Big Sure... We are narrowing it down :) Again thanks for your help!

How about replacing the broken digital signature?
sudo codesign --force --deep --sign - /Applications/MestReNova.app
You need to have XCode installed first of all.

Let me download that and try! :)

To install xcode, try running the following in the terminal:
xcode-select --install

Same issue.
It's strange because I could use the top menu (although not everything works, I can't open a file using the open option, but I can open a file that is in the "recently opened" option)

However if I try to click on the tab in the software itself, nothing is responding to my clicks. I can't even switch tabs. And as I said, I have the exact same issue on two different macs.

Could this be the issue?
rocess:               nmrpredict-server [1297]
Path:                  /Applications/MestReNova.app/Contents/Resources/NMRPredict/nmrpredict-server
Identifier:            nmrpredict-server
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        MestReNova [1290]
Responsible:           MestReNova [1290]
User ID:               501
Date/Time:             2020-11-21 18:13:06.624 +0000
OS Version:            macOS 11.0.1 (20B29)
Report Version:        12
Anonymous UUID:        D1CE56AE-15DA-B298-E2FD-C1ACCBFE4CDD
Sleep/Wake UUID:       D8147604-C4F7-40C4-975B-46FC314181D5
Time Awake Since Boot: 1200 seconds
Time Since Wake:       320 seconds
System Integrity Protection: disabled
Crashed Thread:        0
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Reason:    DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
dyld: No shared cache present
Library not loaded: /usr/lib/libSystem.B.dylib
Referenced from: /Applications/MestReNova.app/Contents/Resources/NMRPredict/nmrpredict-server
Reason: image not found
Binary Images:
0x100c6b000 -        0x101880fff +nmrpredict-server (???)  /Applications/MestReNova.app/Contents/Resources/NMRPredict/nmrpredict-server
0x11a6d4000 -        0x11a7f2fff +libgfortran.3.dylib (0) <39851E49-D973-36C6-9B95-9004CE8498B3> /Applications/MestReNova.app/Contents/Resources/NMRPredict/libgfortran.3.dylib
0x11a866000 -        0x11a89dfff +libquadmath.0.dylib (0)  /Applications/MestReNova.app/Contents/Resources/NMRPredict/libquadmath.0.dylib
0x7fff5eeb2000 -     0x7fff5ef4dfff  dyld (832.7.1) <2705F0D8-C104-3DE9-BEB5-B1EF6E28656D> /usr/lib/dyld

I'm attaching the different log files I got.
Archive.zip

That is very likely the reason. When it is not activated, the plugin won't run, so the issue was not revealed until you activated the app. (That being said, that issue is indeed due to compatibility issues between MNova and the latest macOS instead of the patch.) However, there is little I could help, because I actually do not own a physical macbook, and I cannot debug on the latest macOS. I might try my friend's mac but it will take a while. Thanks for the detailed info.

So I think I have found the issue:
https://www.techradar.com/how-to/macos-11-big-sur-problems-how-to-fix-the-most-common-issues
They moved the libraries to another location on the new MacOS - I guess one would have to make that change on the patch but I don't know how to do it sadly.

Sorry, here is the link:
https://news.ycombinator.com/item?id=23612772

This could help to:
https://github.com/urllib3/urllib3/pull/1905

Awesome. We are getting close. It will take a while for me to find a solution. The temporary workarond, I think, is to disable the nmrpredict plugin. Can you delete the corresponding license file(s), NMRPredictDesktop.lic and Random Forest NMR Predictor.lic, and try if it works or if it produces new error log entries?

bingo... it works without these licences!

okie dokie. I actually dont find the prediction function very useful. Anyways, let me find if there is any way to make the predictor functionable.

Ok best news ever:
If you install the latest version 14.2, open it, close it, patch it and then fix the signature with sudo codesign --force --deep --sign - /Applications/MestReNova.app... IT WORKS! including the predictor, etc.

Good. I assume that they rewrote the code a little bit, so the assembly code I saw was changed, but the patch somehow still works. I will update the post and close the issue. Thank you a lot for testing and sharing.

That’s cool! Thanks for helping!

Hello, AFTER I run the MestReNovaCrack patch on the Window computer, it shows an error and cannot be cracked. I would like to ask your method. The version I installed is "mestrenova-12.0.4-22023_x64". The error code is as follows:
Processing D:\MNN\MestReNova.exe...
This file might have already been patched [Press Y' to override]. Found pattern, JNZ -> JMP: 75 .. .* 0B 00 00 80 .* 0B 00 00 80 Error occurred: #<Errno::EBADF: Bad file descriptor - D:\MNN\MestReNova.exe> ["MestReNovaCrack.rb:34:in seek'", "MestReNovaCrack.rb:34:in patch'", "MestReNovaCrack.rb:19:in loop'", "MestReNovaCrack.rb:19:in patch'", "MestReNovaCrack.rb:103", "MestReNovaCrack.rb:101:in each'", "MestReNovaCrack.rb:101"]
Releasing .LIC files in D:\MNN\licenses...
All .LIC files have been created.

Hello, AFTER I run the MestReNovaCrack patch on the Window computer, it shows an error and cannot be cracked. I would like to ask your method. The version I installed is "mestrenova-12.0.4-22023_x64". The error code is as follows:
Processing D:\MNN\MestReNova.exe... This file might have already been patched [Press Y' to override]. Found pattern, JNZ -> JMP: 75 .. .* 0B 00 00 80 .* 0B 00 00 80 Error occurred: #<Errno::EBADF: Bad file descriptor - D:\MNN\MestReNova.exe> ["MestReNovaCrack.rb:34:in seek'", "MestReNovaCrack.rb:34:in patch'", "MestReNovaCrack.rb:19:in loop'", "MestReNovaCrack.rb:19:in patch'", "MestReNovaCrack.rb:103", "MestReNovaCrack.rb:101:in each'", "MestReNovaCrack.rb:101"]
Releasing .LIC files in D:\MNN\licenses... All .LIC files have been created.

plz do not leave irrelevant comments under this issue. all replies will be addressed in #8


Update index.html: Improve button for creating notes and update searc…

…h box style

Merging this PR but the issue will be open due to not the best similarity.


Very many error reports when in production

I was trying to use this plugin, because it is free and has no ad share. I am using ionic, I had a hard time trying to make it work, but I am able to run it using Crosswalk.  I am using Google Analytics to log when an ad is receved, shown or retruns an error, because AdMob was not logging the amout of impressions I would expect. While it does works in my phone flaweslessly, when in production, it logs a lot of errors. Using  cordova-plugin-admob-simple also gives me many many erros also, but I got no error when using cordova-admob-pro. However, cordova-admob-pro is evil, it has remote control and ad share. Anybody is logging data in Analytics and experiencing the same resutls? I tried to look the code, but my Java and Android skills are not very good, I can only make some tests... :-(

Hi @oangelo
could you give us details of the errors that are reported?
Thank you

I wish I have more time to improve this plugin, but supporting features which I don't use is hard and time consuming.
Good to hear that you are willing help on testing, most issues does not include clear steps how a problem occurs, some are more difficult as they (looks) happen randomly.
I will look into some issues this weekend, but could not guarantee anything.

Hi @becvert
As I said, I can't reproduce the problem in my own phone when testing, I think it is an intermittent problem, because I only noticed it when the app is in production. I did not logged the problem description, only how many times it happened. I am not an expert in this field... But I am now using  https://github.com/floatinghotpot/cordova-admob-pro and no error is been logged.
I had the same problem when using sunnycupertino/cordova-plugin-admob-simple, see:
https://github.com/sunnycupertino/cordova-plugin-admob-simple/issues/13. But he had no idea of what it could be.
The code I was using is this:
var adReady = false;
var adTimer = true;
var adPluginLoaded = false;
var adBannerShown = false;
var lastCardName = 'none';

function initAd(){
  if ( window.plugins && window.plugins.AdMob ) {
    adPluginLoaded = true;
    var ad_units = {
      ios : {
        banner: '*****',       //PUT ADMOB ADCODE HERE
        interstitial: '*****'  //PUT ADMOB ADCODE HERE
      },
      android : {
        banner: '*****',       //PUT ADMOB ADCODE HERE
        interstitial: '*****'  //PUT ADMOB ADCODE HERE
      }
    };
    var admobid = ( /(android)/i.test(navigator.userAgent) ) ? ad_units.android : ad_units.ios;

    window.plugins.AdMob.setOptions( {
      publisherId: admobid.banner,
      interstitialAdId: admobid.interstitial,
      adSize: window.plugins.AdMob.AD_SIZE.LARGE_BANNER,  //use SMART_BANNER, BANNER, IAB_MRECT, IAB_BANNER, IAB_LEADERBOARD
      bannerAtTop: false, // set to true, to put banner at top
      overlap: false, // banner will overlap webview
      offsetTopBar: false, // set to true to avoid ios7 status bar overlap
      isTesting: false, // receiving test ad
      autoShow: false // auto show interstitial ad when loaded
    });

    registerAdEvents();
    window.plugins.AdMob.createInterstitialView();  //get the interstitials ready to be shown
    window.plugins.AdMob.requestInterstitialAd();

  } else {
    //alert( 'admob plugin not ready' );
  }
}
//functions to allow you to know when ads are shown, etc.
function registerAdEvents() {
  document.addEventListener('onReceiveAd', function(){});
  document.addEventListener('onFailedToReceiveAd', function(data){
    //alert("fail to receive");
    setTimeout( function() {
      window.plugins.AdMob.createInterstitialView();          //REMOVE THESE 2 LINES IF USING AUTOSHOW
      window.plugins.AdMob.requestInterstitialAd();
    }, 1000*30);
    window.analytics.trackEvent('Ad', 'Interstetial', "Error");
  });
  document.addEventListener('onPresentAd', function(){});
  document.addEventListener('onDismissAd', function(){ });
  document.addEventListener('onLeaveToAd', function(){ });
  document.addEventListener('onReceiveInterstitialAd', function(){
    //alert("inter receive");
    adReady = true;
    window.analytics.trackEvent('Ad', 'Interstetial', "Received");
  });
  document.addEventListener('onPresentInterstitialAd', function(){ });
  document.addEventListener('onDismissInterstitialAd', function(){
    //alert("inter dimiss");
    window.plugins.AdMob.createInterstitialView();          //REMOVE THESE 2 LINES IF USING AUTOSHOW
    window.plugins.AdMob.requestInterstitialAd();           //get the next one ready only after the current one is closed
    adReady = false;
    window.analytics.trackEvent('Ad', 'Interstetial', "Closed");
  });
}

//display the banner
function showBannerFunc(){
  //alert('show banner');
  if (adPluginLoaded && !adBannerShown){
    window.plugins.AdMob.createBannerView({autoShow: true,});
    window.plugins.AdMob.prepareInterstitial({autoShow: false,})
    adBannerShown = true;
  }
}

//display the interstitial
function showInterstitialFunc(){
  if (adPluginLoaded){
    if (adReady && adTimer){
      setTimeout( function() {
        adTimer = true;
      }, 1000*60);
      adTimer = false;
      window.plugins.AdMob.showInterstitialAd();
      window.analytics.trackEvent('Ad', 'Interstetial', "Show");
    }
  }
}

function closeBannerFunc(){
  if (adBannerShown && adPluginLoaded){
    window.plugins.AdMob.destroyBannerView();
    adBannerShown = false;
  }
}

And this is what I got on a typical day:

Hope this helps

You're calling prepareInterstial in showBannerFunc. Is that normal?
Maybe it is. Maybe it does not matter. I'm just trying to understand the code.

@becvert, take a look at #27. There is explained why I am doing this.

As v0.6 is out, I am closing this. Feel free to reopen if the problem still exists.


feat(auto-instrumentation-node): add undici instrumentation

Which problem is this PR solving?

auto-instrumentations-node is expected to include all instrumentations in js and js-contrib, but didn't yet have the newly created and published undici

Short description of the changes

add undici instrumentation to auto-instrumentations-node package

Note: As I understand it, we haven't had an official "release" of undici instrumentation, but we recently found that new packages like this still got published on npm due to a misconfiguration in our workflows.
Also, I couldn't recall if there was a reason to delay adding this to the package (like since it's still so new), but figured I'd open the PR either way because I didn't see it otherwise.

Thanks @JamieDanielson , can you please resolve the conflicts so this can merge?

I think this is good to go, but unsure if I should hold off for a maintainer to merge as they are assigned component owners (I am but a lowly approver 😃 )

I think this is good to go, but unsure if I should hold off for a maintainer to merge as they are assigned component owners (I am but a lowly approver 😃 )

Not sure about the formalities, but since it already has 3 approves and is open for more than a week, I think it's safe to merge 👍


Enhance Accounts Feature and Enable Ticket Acquisition for Registered Users

Organizer can view their order at /control area

New dropdown for organizer account

Summary by Sourcery
Allow organizers to buy tickets by removing customer account management features and simplifying the order processing and email sending logic. Introduce a new dropdown for organizer accounts to enhance navigation.
New Features:

Introduce a new dropdown for organizer accounts to enhance navigation.

Enhancements:

Remove customer account management features, including customer login, registration, and related views and forms.
Simplify email sending logic by removing organizer-specific SMTP settings and customer-related email handling.
Refactor the order processing logic to remove customer-specific handling and dependencies.
Update the UI to remove customer account-related elements and improve the organizer's navigation experience.

Please also fix isort tests.


Multidomain with same properties

I had several domain with the same configuration, can I combine them into one with anyOf schema?

Good Idea :). I have to tell you I'm not really into it at the moment. I have less spare time as I want to.


security/openconnect: add pin-sha256 to certificate hash

Closes #1355

Nice catch, fixed

Merged, thanks! ❤


Problems Converting Keras-Contrib Capsule Layer to .Onnx Format

Hello,
I have keras-contrib installed as a PyPi package and I am using a capsule layer (linked the code below) in one of my models.
https://github.com/keras-team/keras-contrib/blob/master/keras_contrib/layers/capsule.py
Previously I was converting my model to a .h5 file. When I was converting my model to an .h5 file I had to add some custom objects code when I was loading the model (code shown below):
clf = keras.models.load_model('7nn_model.h5', custom_objects={'Capsule':Capsule, 'squash': squash})
In order to get the same inference time performance from my model as I did while the model was being trained. I think I am running into a similar issue with the .onnx format in that I am now getting different inference time performance (after loading my .onnx file) of my model compared to when it was originally trained.
I was hoping someone would be able to shed some light on if they think the discrepancy in training / inference time performance I am seeing is in fact due to something with the capsule layer not being properly saved in the .onnx format? Any suggestions on how to address this are appreciated.

It looks like you have two onnx models and they have different inference time? what is the difference between these two onnx models?

It looks like you have two onnx models and they have different inference time? what is the difference between these two onnx models?

@jiafatom Sorry if it was unclear David, I do not have two .onnx models. Hopefully this clears things up. I have one file, in which I train a neural network (which contains a capsule layer from keras-contrib) -- and then once it is trained I save that neural network as a .onnx file. I then have a second file where I load the .onnx file I just saved and then evaluate the performance of the model for a second time (just for verification purposes). The issue I am having looks like this ... when the model is originally being trained it will get train_score = 95% validation score = 93%. On the other hand when I load the .onnx file which contains the trained model and try to evaluate it again, I am getting train_score = 60% validation score = 58% and test score = 57%.
When I was previously using .h5 instead of .onnx I was having this same type of issue with models that included a capsule layer. I resolved the issue by including the custom objects line of code I posted in my original post.

So you have a keras model with custom layer, and then convert using keras2onnx to get onnx model. And your inference result keras vs. onnx mismatch? Then seems like a converter issue. Can you pull latest keras2onnx master and onnxconverter-common master and see if the issue still exists? If it does, can you share a simple model which repro your problem?

@jiafatom Hi David -- Sorry for the delay. I'm not an expert on git based version control systems but to try and do what you asked I deleted all my onnx related packages off my machine...then I made sure I upgraded pip, and then I re-downloaded all the pip packages that I needed. I am still having an issue.
I used the MNIST dataset to make a couple scripts that can recreate this issue. As long as you have the required packages installed you should be able to simply run the two scripts and encounter the same problem (if of course there is a problem, and I didn't just make a mistake). The issue is occurring when I use a model that also includes causal padding on 1D convolutional layers. Is causal padding supported by onnx? If the causal padding is removed then the issue goes away it seems.
The script I made uses the MNIST dataset but only digits 0,2 and 6 to make for a simpler classifier.
CapsuleModelSaver.py
https://drive.google.com/file/d/13ZbIJh0s7thmk43Iu1dupvpJjoxHHsdx/view?usp=sharing
CapsuleOnnxTester.py
https://drive.google.com/file/d/1UFeFekpuly9MmVlvDOs5GXNMb1U8h21B/view?usp=sharing
When CapsuleModelSaver.py is run the training performance is 80% and the testing performance is 78%. When CapsuleOnnxTester.py is run the training performance is 33% and the testing performance is 33%.
Please let me know if you cannot use the google drive links do to permissions issues and I will fix asap. Thank you.

@jiafatom I just wanted to follow up. Were you able to reproduce the error I am experiencing? Thank you.

@MattWard97 currently I am working on some other projects, so I am afraid that I don't have bandwidth looking at this issue. Thanks for your understanding.


FIX: The 3D mesh does not appear when one opens the AI tab for the first time.

The 3D mesh does not appear when one opens the AI tab for the first time. It does appear when we click on the button that toggles between gestational week and hormones.

Possibly related to:

This is related with latest version of sklearn (1.6.0).
Fixing it.
If you need to run it meanwhile, install sklearn==1.5.2.

Closing as https://github.com/luisfpereira/polpo/commit/a5b908abaf9065303cd73a9d821e2d60cf6a93c1 solves the issue. @ninamiolane , please reinstall polpo and, if the problem persists, reopen the issue.


Fix text highlight breaking cursor movements

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15310/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15310/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15310/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15310/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15310/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15310/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15310/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15310/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15310/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15310/merge/testResults/webgpuplaywright/index.html


Chinese audio for less than 15 seconds

I used a Chinese speech model to generate audio, and the generated audio can never exceed 15 seconds. How can I solve this problem?

你能告诉我模型生成的音频质量如何吗

Bark good at English but terrible at other languages

With chinese model you probably mean a chinese speaker and for generation you used Swap Voice? Otherwise there is no 15s limitation in this fork?!?

So how do I solve the loss of text in the audio when Chinese is generating speech

Are you sure you're using this fork? As I wrote previously I don't have a audio limit.

Bark good at English but terrible at other languages

I disagree, you just have to find a good speaker voice. At least for the languages I know, it might be different for chinese 😏

I tried many times to use Chinese for audio output, but the results are not satisfactory, Could you please give me some solutions

Is it this problem?
https://github.com/suno-ai/bark/issues/324


Guide to contribute translations

We need a guide on how to contribute translations.
We should probably mention that we don't accept community-contributed translations yet as we want some done professionally first.

Wasn't there . specific translation integration service you recommended before? I can't remember what it was called but it looked like it would make management much easier.

It was CrowdIn.
It's free for open source: https://github.com/marketplace/crowdin/plan/MDIyOk1hcmtldHBsYWNlTGlzdGluZ1BsYW40MjM=#pricing-and-setup

I think it looks really good.


Does not build with GHC 9.0

I don't understand what's going on well enough to debug this myself, but it could be related to https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0287-simplify-subsumption.rst.
$ cabal build
Build profile: -w ghc-9.0.1 -O1
In order, the following will be built (use -v for more details):
 - Rasterific-<IP_ADDRESS> (lib) (file src/Graphics/Rasterific/MicroPdf.hs changed)
 - Rasterific-<IP_ADDRESS> (exe:rastertest) (dependency rebuilt)
 - Rasterific-<IP_ADDRESS> (exe:doc_builder) (dependency rebuilt)
Preprocessing library for Rasterific-<IP_ADDRESS>..
Building library for Rasterific-<IP_ADDRESS>..

on the commandline: warning:
    -Wnoncanonical-monadfail-instances is deprecated: fail is no longer a method of Monad
[27 of 29] Compiling Graphics.Rasterific.MicroPdf ( src/Graphics/Rasterific/MicroPdf.hs, /Users/lukeworth/bump-diagrams/Rasterific/dist-newstyle/build/x86_64-osx/ghc-9.0.1/Rasterific-<IP_ADDRESS>/build/Graphics/Rasterific/MicroPdf.o, /Users/lukeworth/bump-diagrams/Rasterific/dist-newstyle/build/x86_64-osx/ghc-9.0.1/Rasterific-<IP_ADDRESS>/build/Graphics/Rasterific/MicroPdf.dyn_o )

src/Graphics/Rasterific/MicroPdf.hs:1139:25: error:
    • Couldn't match type ‘InnerRenderer’
                     with ‘m0 () -> [DrawOrder px]’
      Expected: PdfConfiguration -> m0 () -> [DrawOrder px]
        Actual: PdfConfiguration -> InnerRenderer
    • In the first argument of ‘asks’, namely ‘_pdfConfToOrder’
      In a stmt of a 'do' block: toOrders <- asks _pdfConfToOrder
      In the expression:
        do toOrders <- asks _pdfConfToOrder
           let orders :: [DrawOrder px]
               orders = toOrders . liftF $ SetTexture prevTexture subDrawings ()
               ....
           after <- recurse next
           this <- recurse . fromF $ F.fold placedDrawings
           ....
    • Relevant bindings include
        next :: Free (DrawCommand px) ()
          (bound at src/Graphics/Rasterific/MicroPdf.hs:1138:48)
        subDrawings :: Drawing px ()
          (bound at src/Graphics/Rasterific/MicroPdf.hs:1138:36)
        recurse :: Free (DrawCommand px) () -> PdfEnv Builder
          (bound at src/Graphics/Rasterific/MicroPdf.hs:1154:7)
        com :: DrawCommand px (Free (DrawCommand px) ())
          (bound at src/Graphics/Rasterific/MicroPdf.hs:1049:50)
        prevTexture :: Texture px
          (bound at src/Graphics/Rasterific/MicroPdf.hs:1049:38)
        go :: Bool
              -> Transformation
              -> (FillMethod -> Builder)
              -> Texture px
              -> DrawCommand px (Free (DrawCommand px) ())
              -> PdfEnv Builder
          (bound at src/Graphics/Rasterific/MicroPdf.hs:1049:3)
     |
1139 |        toOrders <- asks _pdfConfToOrder
     |                         ^^^^^^^^^^^^^^^
cabal: Failed to build Rasterific-<IP_ADDRESS> (which is required by exe:rastertest
from Rasterific-<IP_ADDRESS> and exe:doc_builder from Rasterific-<IP_ADDRESS>)

@endgame helped me fix this up :)


Add onInitialize handler to be called immediately after runtime upgrade

When perform a runtime upgrade, it will be useful to be able to perform some work immediately after the upgrade.
This onInitialize handler can be used to do initialization work for the new runtime. e.g. migrate storage from old format to new format
It could be wasm code / smart contract style attached to the setCode method.
Or have onInitialize part of the wasm runtime interface, this does means have to store this one time used code in storage alone with rest of the runtime.
It should also call some the native client code handler to notify the runtime change to allow native client code to perform some other work. e.g. Reset metadata cache

Should be manageable by a standard block OnInitialise and a boolean storage item to check for whether upgrade has happened. Anything more complex (e.g. to be able to determine whether an upgrade has happened) is quite complex and not as flexible.


[Bug] Off rail

Describe the Bug
I made track with monorail tracks from steam 'n' rails but then train keeps sending messages and stops "train has gone off track".
Reproduction Steps

Download create unlimited 0.6.3 for 1.20.1, download steam 'n' rails 1.6.7 for 1.20.1, download Minecraft forge 1.20.1, download create 0.5.1.j for 1.20.1.
Make a singleplayer world.
Build a monorail track with big curves or drops(using create unlimited).
Make a monorail(train)
Assemble and drive around
...

Expected Result
I expected it to just ride through
Screenshots and Videos
No response
Log
Nothing in logs
Operating System
Windows 11 Home
Mod Build
0.6.3
Minecraft Version
1.20.1
Modloader
Forge
Modloader Version
47.3.11
Other Mods
Sodium, many optimization mods, eureka ships for valkryien skies, valkryien skies, addons for create like steam 'n' rails.
Additional Context
No response

Try changing the extendedDriving config value. See the wiki for more information.

thx

ill try rq

still after setting it to 0.001 it was still saying that went offrail on some sharp upclimbs

Can you share a video of what you're doing to make this happening?

umm i can only tomorrow

That's alright, whenever you have the time. If you have a discord account you can also join our server, I might respond a little faster there.

That's alright, whenever you have the time. If you have a discord account you can also join our server, I might respond a little faster there.

ok then we will continue the talk on discord


support alter table for hashdata format

support hashdata table format alter table rewrite routine, move the actuall rewrite to qe,  and create a new statement message  to distribute work to qe.

Hi @wangliang03, thanks for your contribution. Could you rewrite your commit title and body following our commit conventions?


RUN in one layer to reduce disk use

Docker's layered file system means the RUN rm -rf node_modules in 0425d10 will not actually reduce your disk use. You've got to put all RUN commands in a single statement.
The RUN command structure follows: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#run
This PR creates less layers, saving 3MB. I added rm -rf ~/.npm to get another 12MB.
Before: The data from the original node install is still in the 1cae88f535ba layer
$ docker image history gcg
IMAGE               CREATED             CREATED BY                                      SIZE                COMMENT
afe1e0b4a10c        2 minutes ago       /bin/sh -c #(nop)  CMD ["npm" "start"]          0 B
ae868226e58d        2 minutes ago       /bin/sh -c #(nop)  EXPOSE 3000/tcp              0 B
9785207d3ddf        2 minutes ago       /bin/sh -c npm install                          3.02 MB
8d9023b407b7        2 minutes ago       /bin/sh -c #(nop)  ENV NODE_ENV=production      0 B
3d56d185aa79        2 minutes ago       /bin/sh -c rm -rf node_modules                  0 B
ff70f7df4774        2 minutes ago       /bin/sh -c npm run build                        9.39 kB
aa6285597e4f        2 minutes ago       /bin/sh -c #(nop) COPY dir:d4c38682dc7b17e...   44.3 kB
1cae88f535ba        2 minutes ago       /bin/sh -c npm install                          22.4 MB
28a0a256a4ee        3 minutes ago       /bin/sh -c #(nop) COPY file:b81722d739e394...   677 B
8800bc6f04a5        3 minutes ago       /bin/sh -c #(nop) WORKDIR /usr/src/app          0 B
3298c17e38c8        3 minutes ago       /bin/sh -c mkdir -p /usr/src/app                0 B
24bfe70a1361        7 months ago        /bin/sh -c apk add --no-cache nodejs            27.8 MB
<missing>           7 months ago        /bin/sh -c #(nop)  MAINTAINER ZZROT LLC <d...   0 B
<missing>           9 months ago        /bin/sh -c #(nop) ADD file:5300ce254c0bf1d...   4.8 MB

After:
$ docker history gcg-edit
IMAGE               CREATED             CREATED BY                                      SIZE                COMMENT
abafdd30e718        2 minutes ago       /bin/sh -c #(nop)  CMD ["npm" "start"]          0 B
a1b848f1fcc6        2 minutes ago       /bin/sh -c #(nop)  ENV NODE_ENV=production      0 B
8d31d00bb757        2 minutes ago       /bin/sh -c #(nop)  EXPOSE 3000/tcp              0 B
3ad76ea7d663        2 minutes ago       /bin/sh -c npm install  && npm run build  ...   10.7 MB
3060678434be        3 minutes ago       /bin/sh -c #(nop) COPY dir:f78b1c910b1e8bf...   47.1 kB
9a44e39f4d2e        51 minutes ago      /bin/sh -c #(nop) WORKDIR /usr/src/app          0 B
24bfe70a1361        7 months ago        /bin/sh -c apk add --no-cache nodejs            27.8 MB
<missing>           7 months ago        /bin/sh -c #(nop)  MAINTAINER ZZROT LLC <d...   0 B
<missing>           9 months ago        /bin/sh -c #(nop) ADD file:5300ce254c0bf1d...   4.8 MB

$ docker images
REPOSITORY               TAG                 IMAGE ID            CREATED              SIZE
gcg-edit                 latest              abafdd30e718        About a minute ago   43.3 MB
gcg                      latest              afe1e0b4a10c        About an hour ago    58.1 MB

Hmm... I've realized an issue that's better decided by you. It is only possible to remove the development node_modules from the image is if it is done in the same RUN command as it is installed. This requires the codebase be available for the build... which stops layer caching.
The only (I think?) way to do the build with caching is to use the build container pattern and have separate build and production containers. Thoughts?

Actually, I was at DockerCon this week, and learned about the new multi-stage feature. What do you think of https://github.com/Philmod/google-container-gulp/pull/3 ?

Closing to defer to #3


Nuget push is broken on mono

Symptom
NuGetPush fails when trying to publish packages on mono.
Cake Task
Task("Publish")
    .Does(() =>
{
    Information($"WorkingDir: {Context.Environment.WorkingDirectory}");
    foreach (var packageFile in GetFiles(OutputPath + "**/*.nupkg"))
    {
        Information($"FullPath: {packageFile.FullPath}");
        NuGetPush(p, settings);
    }
});

Result
========================================
Publish
========================================
Executing task: Publish
WorkingDir: /Workspaces/appature/git/ImsHealth.Automation
FullPath: /Workspaces/appature/git/ImsHealth.Automation/.artifacts/Debug/ImsHealth.Automation.1.1.2.nupkg
Directory '/Workspaces/appature/git/ImsHealth.Automation/Workspaces/appature/git/ImsHealth.Automation/.artifacts/Debug' not found.
An error occured when executing task 'Publish'.
Error: NuGet: Process returned an error (exit code 1).

Cause
NuGetPusher.GetArguments currently generates an absolute path to the .nupkg file to be pushed.
55:            builder.AppendQuoted(packageFilePath.MakeAbsolute(_environment).FullPath);

Apparently, this is a problem when running nuget on mono (tested with both 2.8.5 and 3.X.X).
Running Nuget With Absolute Package Path
$ mono .tools/nuget.exe push "/Workspaces/appature/git/ImsHealth.Automation/.artifacts/Debug/ImsHealth.Automation.1.1.2.nupkg"
Directory '/Workspaces/appature/git/ImsHealth.Automation/Workspaces/appature/git/ImsHealth.Automation/.artifacts/Debug' not found.

Notice how it tries to append the absolute path it's given to the current working directory:

'**/Workspaces/appature/git/ImsHealth.Automation/**Workspaces/appature/git/ImsHealth.Automation/.artifacts/Debug' not found.

Running Nuget With Relative Package Path
$ mono .tools/nuget.exe push "./.artifacts/Debug/ImsHealth.Automation.1.1.2.nupkg"
Pushing ImsHealth.Automation 1.1.2 to the NuGet gallery (https://www.nuget.org)...

Great success!
Suggestion
File a bug in Nuget
I did this: https://github.com/NuGet/Home/issues/2167
Workaround in Cake
Fumbling around in NuGetPusher.cs trying to figure out how to pass a relative path when on Unix.
This isn't really working, so i'm hoping someone has suggestions about how to work around this.
            FilePath envSpecificPackageFilePath;
            if (_environment.IsUnix())
            {
                // BUG: Nuget on mono doesn't work with absolute file paths.
                envSpecificPackageFilePath =
                    packageFilePath.GetRelativePath(_environment.WorkingDirectory).GetFilePath(packageFilePath);
            }
            else
            {
                envSpecificPackageFilePath = packageFilePath.MakeAbsolute(_environment);
            }

            builder.AppendQuoted(envSpecificPackageFilePath.FullPath);

@andycmaj this was recently discussed in the Gitter Chat Room: https://gitter.im/cake-build/cake?at=56a88fdb80ad69394a7ab567
With a potential workaround here: https://gitter.im/cake-build/cake?at=56aa2119586242210ae01122 suggested by @Redth
The workaround will depend on whether you are using a nuspec, or driving everything from NuGetPackSettings.
Thanks for filing the issue with NuGet though, hopefully something will come from that.

Hmm, actually, what I linked to above was with the NuGetPack command, and I have just realised that you are talking about NuGet Push.  Sorry, I saw the similarity in the comments, and didn't read properly.

no problem... actually the response i got on the nuget bug was, "use nuget.exe 3.4 from the CI feed".
so i did that, and it works.
the next problem i ran into was that 3.4 tries to automatically push your .sybmols.nupkg along with a push of a normal package, and this seems to fail... so still following up on https://github.com/NuGet/Home/issues/2167. i'll close this one and feel free to follow that issue


@Externalized annotation to take values from application.yml file

Hello,
I have a Spring Boot Application. I am using spring Modulith and I want events to be externalized to AWS SQS. Everything works fine but the @Externalized annotation doesn't seem to be taking values from application.yml file. Below is the sample code.
@Externalized("${aws.order-completion-queue}")
public record OrderCompletedEvent(
        String prefix,
        String companyName,
        String firstName,
        String lastName,
        String email,
        String contactNumber,
        String orderId
) {
}

application.yml
aws:
 order-completion-queue: order-completion-dev-queue.fifo

FYI - I have verified the indentation and also that the queue exists. I am using the same placeholder on @SqsListener in my application and that works fine.
Also hardcoding the queue name works.
Please suggest if I am doing something wrong, if not what would be the best way to use the yml file properties in @Externalized annotation
Edit 1 - This is the error that I am getting
Caused by: java.util.concurrent.CompletionException: io.awspring.cloud.sqs.QueueAttributesResolvingException: Error resolving attributes for queue ${aws.order-completion-queue} with strategy CREATE and queueAttributesNames []
	at java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:368) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:377) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1152) ~[na:na]
	... 42 common frames omitted
Caused by: io.awspring.cloud.sqs.QueueAttributesResolvingException: Error resolving attributes for queue ${aws.order-completion-queue} with strategy CREATE and queueAttributesNames []
	at io.awspring.cloud.sqs.QueueAttributesResolver.wrapException(QueueAttributesResolver.java:90) ~[spring-cloud-aws-sqs-3.2.0.jar:3.2.0]
	at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:990) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:974) ~[na:na]
	... 42 common frames omitted
Caused by: software.amazon.awssdk.services.sqs.model.SqsException: Can only include alphanumeric characters, hyphens, or underscores. 1 to 80 in length (Service: Sqs, Status Code: 400, Request ID: eb9ee289-d753-4a3c-84b6-22cd769ffc29)
	at software.amazon.awssdk.services.sqs.model.SqsException$BuilderImpl.build(SqsException.java:104) ~[sqs-2.25.70.jar:na]
	at software.amazon.awssdk.services.sqs.model.SqsException$BuilderImpl.build(SqsException.java:58) ~[sqs-2.25.70.jar:na]

I am using Spring 3.3.4 and below is a snippet of my pom consisting of modulith specific dependencies
<dependency>
            <groupId>org.springframework.modulith</groupId>
            <artifactId>spring-modulith-starter-core</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.modulith</groupId>
            <artifactId>spring-modulith-starter-test</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.springframework.modulith</groupId>
            <artifactId>spring-modulith-actuator</artifactId>
            <scope>runtime</scope>
        </dependency>
        <dependency>
            <groupId>org.springframework.modulith</groupId>
            <artifactId>spring-modulith-observability</artifactId>
            <scope>runtime</scope>
        </dependency>
        <dependency>
            <groupId>org.springframework.modulith</groupId>
            <artifactId>spring-modulith-events-aws-sqs</artifactId>
        </dependency>

        <dependency>
            <groupId>org.springframework.modulith</groupId>
            <artifactId>spring-modulith-starter-jpa</artifactId>
        </dependency>

The routing target declared in an annotation is currently not processed at all, but used as is. You can currently already work around this limitation by providing a programmatic routing lookup by declaring a bean of type EventExternalizationConfiguration using the route(Class<T>, Function<T, RoutingTarget>) method.
That said, we could pipe the routing target through the SpEL processing we already apply for the routing key. You'd have to use a SpEL expression such as #{env['aws.order-completion-queue']}. Would that be okay for you?

I was able to do that with EventExternalizationConfiguration. While I was struggling with this I did try SpEL #{environment['aws.order-completion-queue']}. I noticed I have to use env instead of environment, but yeah this will work for me. Will try and let you know
By the way love the work. Thanks for a great project 👍🏻

This in place now. The latest snapshots should support SpEL expressions in the target definitions as well.


sbom: fix an inverted boolean check

When checking if sbom was already previously generated we inverted the boolean condition check.

/lgtm


datetime(changelog): initial commit for datetime component experiments

This is a work in progress mainly focused on exploring the possiblity of adding a datetime component which supports date ranges, time and localisation.

That component wasn't imported yet but fixed the typos. Did not solve the problem.

Thanks for the note, I'll take a look at this branch later tonight and resolve the issue.

Codecov Report

Merging #1240 into master will increase coverage by -0.55%.

@@            Coverage Diff             @@
##           master    #1240      +/-   ##
==========================================
- Coverage   95.89%   95.35%   -0.55%
==========================================
  Files         880      882       +2
  Lines        4901     4928      +27
==========================================
- Hits         4700     4699       -1
- Misses        201      229      +28

Impacted Files
Coverage Δ

src/modules/Datetime/Datetime.js
26.31% <26.31%> (ø)

src/modules/Datetime/CalendarMonth.js
42.85% <42.85%> (ø)

src/modules/Datetime/DayCell.js
9.09% <9.09%> (ø)

...tions/Table/States/TableExampleWarningShorthand.js
100% <ø> (ø)
:white_check_mark:

src/collections/Table/Table.js
100% <ø> (ø)
:white_check_mark:

...modules/Dropdown/Types/DropdownExampleInlineTwo.js
100% <ø> (ø)
:white_check_mark:

src/modules/Dimmer/Dimmer.js
100% <ø> (ø)
:white_check_mark:

src/collections/Table/TableHeaderCell.js
100% <ø> (ø)
:white_check_mark:

src/collections/Grid/Grid.js
100% <ø> (ø)
:white_check_mark:

src/collections/Table/TableCell.js
100% <ø> (ø)
:white_check_mark:

... and 29 more

Continue to review full report at Codecov.

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

Fixed:
-static PropTypes
+static propTypes

I also pushed a lot of cleanup so I could browse the code a little easier.

Looks like we'll need to reabse this branch to master to get the commits in order.  All the typings were moved from index.d.ts files to individual component files such as Button.d.ts.  There is still an index.d.ts file but it just exports the default component file from the directory.
This is 1:1 with how the JS files are setup as well.  LMK if you run into any issues with the rebase cleanup and I'll help out.

No worries. I rebase periodically anyway so this will be just one more link in the chain. Didn't do much over the last few days because of life but i'm back at it this week.

I've pushed some cleanup and a rebase to the latest master.
I think we should start breaking this PR down into small shipments and releasing it.  This will allow us to focus on one chunk at a time and do a good job on just that.  As we polish and release each piece, we can bring it back into this branch and prepare the next release.
Do you think we could somehow release Date only as the first component, the Time, and Datetime?  I'm wondering if it makes sense to break these down that way API wise as it does release wise.  Let me know your thoughts.

Heads up, I'll be pushing some more refactors and cleanups for a bit here.

OK, after pushing the latest I think we can ship Datetime with basic support first, then perhaps follow-up with the range support.
DateTimeGrid
I pushed a generic DateTimeGrid that is used in all but the Month view.  It allows an easier construct the table cells, just pass a single array of as many cells as you want and tell the DateTimeGrid how many columns to fit them into.  It will chunk out the Rows for you.
This will also give us the ability to handle different layouts, since the DateTimeGrid just takes a single array of cell props objects.  We can use this array to build any layout.  We can even, later on, expose a renderGrid prop and allow the user to render their own calendar grids if we wanted to.
TODO
I'd like to factor out the DayCell into the DateTimeGrid but am not 100% sure on how yet.  I'd also like to move the dateUtils to the Datetime directory and perhaps remove more, if possible (I removed some already).

That's all I got for now, thanks for all the work on this and the patience dealing with my limited availability.  We're getting close to something here 👍

Whats the status of this issue?

I'm also interested in this feature and can dedicate some time this week to test/code/document/brainstorm or whatever is needed.

It's coming together, late stage development. There are a few things that
require feedback - in particular the momentjs branch which decouples date
handling to support both native js dates as well as moment/moment-timezone
dates (or any other time framework).
On Mon, Apr 24, 2017 at 10:19 AM, Gregory Potdevin<EMAIL_ADDRESS>
wrote:

I'm also interested in this feature and can dedicate some time this week
to test/code/document/brainstorm or whatever is needed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Semantic-Org/Semantic-UI-React/pull/1240#issuecomment-296591011,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8Lena3iGagJIwWgDbL6GfmgN1rX2FXks5rzGkzgaJpZM4LwH1O
.

Hi guys, how is it going :)

Any update on this?

good work guys!

Update:
This branch has some failing conformance tests that need resolved.  Once those are resolved, I want to trim any non-functioning parts and ship it.
If anyone cares to dive in, please do!  Fork this branch and run yarn test:watch to see what is left to fix.
I continue to trickle work here as often as I can, which tends to be about once a week.

OMG, this component is finally conformant!

We should be ready for some user testing here shortly :)

Can't wait, any progress ? Do you need help testing it?

Let me know if there is anyway I can help push this forward.

Waiting eagerly for this to be completed. This is a very frequently used component in forms. Available for helping push this out soon.

Same here, count me in if you need anything

If anyone would like to hop in here's some more info.  Conformance tests are passing and there are plenty of doc site examples.  What's needed is to run the doc site, try the examples, and fix the bugs.  Bug fixes should also have tests written for them.
As soon as all the doc site examples are working with passing tests, this can be shipped. 🎉

How is it going guys ? Any news on this ?

Patiently waiting. Anything I can do to speed this up?

This is the final piece missing for all my forms using SUI. Can't wait!

All I want for Christmas is SUI datepicker 🎄 🎁 📆 😆

Hey everyone! I think we are all excited to ship this. At the same time, there is only so much bandwidth that main contributors to this project have to give to open source work. The nice thing is that it's open source and we are happy to accept pull requests from anyone that moves this project/feature forward.
Per @levithomason's comment above, as soon as doc site examples are working and tests are passing for the reported bugs, this can be shipped. @Gallevy you asked if there is anything you can do to move this forward... we welcome any time you can dedicate to fixing any of the remaining bugs. Anyone else who has commented wanting to know what is going on, you are also welcome to help out. <3

@brianespinosa When will we be able to use this? :)

If you'd like to contribute to the development of this feature, please email me[at]levithomason.com.  This thread produces too much noise and distracts from the focus.

A few collaborators have emailed me and pushed this work forward.  You are amazing ❤.
I've ported this branch to our repo for easier management.  I'm merging any well authored PRs against this effort.
See #2821 for the Datetime branch on the main repo
See #2813 as an example of how you can help in making PRs against the feature branch


Setup a basic page and use evolutions API

Let's get started with creating a basic page and using the API, UI/UX modifications can be done as we proceed.

Cool!. I'll work in this. @anshumanv is it OK to assign this to myself?

Feel free to assign it to yourself if you need, and send a PR once done, others can collaborate or suggest changes in the PR itself.

@anshumanv @sneakycr0w please take a look at this screenshot: https://imgur.com/a/f3j3l
Let me know what you think before I commit :)

Woah !
Looks so amazing !
Infact i think that Evolutions in the middle can even be used as a Logo for this app.
Please add your reviews @sneakycr0w

Wow that looks great @collinsnji! The only gripe I'd have (and it's super minor) is just maybe a little magnifying glass icon aligned to the right side of the input box. 😄

Right @sneakycr0w that will look appealing :mag_right: :smile:
What say @collinsnji ?

Sure! I'll add that right away 😄

Awaiting for your PR @collinsnji once done :smiley:

btw make a gitter channel, follow up for any discussion https://gitter.im/evolutions-webapp/Lobby#


[EN] Feedback for: http://www.html5rocks.com/en/tutorials/indexeddb/todo/

This page
http://www.html5rocks.com/en/tutorials/indexeddb/todo/
does not work, but it is linked i.e. from here:
https://developer.chrome.com/apps/app_storage
I have found it only in internet archive:
https://web.archive.org/web/20150217065724/http://www.html5rocks.com/en/tutorials/indexeddb/todo/

broken link =>
working link =>
I'm reported a content bug. Thanks @luxlux

Please file issues for HTML5Rocks at https://github.com/html5rocks/www.html5rocks.com


For a 0.18.8 release

#559 #558

Codecov Report

Merging #560 (a66f29f) into master (f04698b) will decrease coverage by 5.60%.
The diff coverage is 90.00%.

:exclamation: Current head a66f29f differs from pull request most recent head 5e96939. Consider uploading reports for the commit 5e96939 to get more accurate results

@@            Coverage Diff             @@
##           master     #560      +/-   ##
==========================================
- Coverage   84.92%   79.31%   -5.61%
==========================================
  Files          36       36
  Lines        3038     2369     -669
==========================================
- Hits         2580     1879     -701
- Misses        458      490      +32

Impacted Files
Coverage Δ

src/resampling.jl
75.78% <90.00%> (-12.53%)
:arrow_down:

src/composition/learning_networks/arrows.jl
0.00% <0.00%> (-73.34%)
:arrow_down:

src/utilities.jl
61.11% <0.00%> (-15.98%)
:arrow_down:

src/data/datasets.jl
88.88% <0.00%> (-11.12%)
:arrow_down:

src/composition/models/_wrapped_function.jl
22.22% <0.00%> (-11.12%)
:arrow_down:

src/composition/learning_networks/inspection.jl
76.31% <0.00%> (-9.96%)
:arrow_down:

src/composition/models/methods.jl
48.71% <0.00%> (-8.73%)
:arrow_down:

src/interface/data_utils.jl
86.95% <0.00%> (-7.49%)
:arrow_down:

src/measures/loss_functions_interface.jl
73.68% <0.00%> (-7.27%)
:arrow_down:

... and 24 more

Continue to review full report at Codecov.

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


InfoWindow reopens after clicking a marker-cluster

Issue description
Upon clicking a marker cluster, all infoWindow that were previously opened while the cluster was "collapsed" will reopen.
Steps to reproduce and a minimal demo of the problem
Given the following code
import { Component } from '@angular/core';

// just an interface for type safety.
interface Marker {
  lat: number;
  lng: number;
  label?: string;
  draggable: boolean;
}

@Component({
  selector: 'app-root',
  template: `
  <agm-map style="height: 800px; width: 100%;" [latitude]="markers[0].lat" [longitude]="markers[0].lng" [zoom]="5" [maxZoom]="18">

    <agm-marker-cluster averageCenter="true" minimumClusterSize="2" [imagePath]="">
      <agm-marker *ngFor="let m of markers; let i = index" [latitude]="m.lat" [longitude]="m.lng">

        <agm-info-window #infoWindow [latitude]="m.lat" [longitude]="m.lng" [isOpen]="i === selectedIndex">
          <p>{{m.label}}</p>
        </agm-info-window>

      </agm-marker>
    </agm-marker-cluster>
  </agm-map>

  <button (click)="changeSelectedIndex(0)">A</button>
  <button (click)="changeSelectedIndex(1)">B</button>
  <button (click)="changeSelectedIndex(2)">C</button>
`,
  styles: ['']
})
export class AppComponent {

  selectedIndex = -1;

  markers: Marker[] = [
    {
      lat: 51.273858,
      lng: 7.815982,
      label: 'A',
      draggable: true
    },
    {
      lat: 51.273858,
      lng: 7.855982,
      label: 'B',
      draggable: false
    },
    {
      lat: 51.273858,
      lng: 7.895982,
      label: 'C',
      draggable: true
    }
  ];

  changeSelectedIndex(index: number) {
    this.selectedIndex = index;
  }
}

Current behavior
Upon loading the app, we can see a cluster with 3 marker.  (Sorry barely visible)
Under the map, there's 3 buttons which will toggle the markers infoWindow on and off.
Click the A and C button.
Close the C infoWindow
Click the cluster.
We are now zoomed in and an Info window is currently opened for A and C.
Expected/desired behavior
No infoWindow should be opened.
angular2 & angular-google-maps version
@angular/core": "^5.2.0",
    "@agm/core": "^1.0.0-beta.2",
    "@agm/js-marker-clusterer": "^1.0.0-beta.2",

Other information

Anyone?


Supply optional webgl-enabled parameter

webgl-enabled 1.0.3 introduces an optional parameter to avoid creating an unnecessary canvas
Also delete src/core/graphics/index.js as it appears to be an unintentional duplicate of src/core/index.js

:+1:

Looking at this now, this actually will break a lot of stuff. If we do this, then the next context we try to get will ignore our options and return the context that was created in this step. See:
var canvas = document.createElement('canvas');

// create a context with no params
var gl1 = canvas.getContext('webgl');

gl1.getContextAttributes().stencil; // false

// create another from the same canvas with params
var gl2 = canvas.getContext('webgl', { stencil: true });

gl2.getContextAttributes().stencil; // false

// create another from a fresh canvas with params
var gl3 = document.createElement('canvas').getContext('webgl', { stencil: true });

gl2.getContextAttributes().stencil; // true

So if we use the one passed in by the user, we can't actually use any options that are not default. I have to revert this.


Mark v1alpha4 CRDs as Deprecated and Unserved

CAPI v1.6 has v1alpha4 types marked as deprecated and unserved. To stay in sync, we are doing the same. With v1.7 these will be removed entirely and we will follow suit when we update to v1.7.

/hold cancel

/retest


Support for custom entry points

webpack Version: 5
karma-webpack Version: 5

Feature Proposal
Let webpack bundle custom entries along with the karma-webpack default bundles.
Feature Use Case
I tried to upgrade from version 4 to version 5 and noticed that it's no more possible to have custom webpack entries with karma-webpack. My test setup relies on these entries in addition to the main test bundle as I test different parts of the application loaded into iframes that in turn should load their respective bundle.

It's possible to actually override webpack config :
let DefaultWebpackOptionsFactory = require('karma-webpack/lib/webpack/defaults');

DefaultWebpackOptionsFactory.create = () => {
    return webpackConfig;
};

require.cache[require.resolve('karma-webpack/lib/webpack/defaults')].exports = DefaultWebpackOptionsFactory;

it's a hack, but it allow the setting of entries and outputs

Thanks @lk77  for the input. @rorymichele could you try and see if that is an option for us?

Sorry for the late reply! I had tried the hack from @lk77 but didn't suceed. I used a different workaround instead, and as the problem seems to persist, I would like to share it here:
for the tests affected I first run webpack with a specific output directory
webpack.config.js
...
if (process.env.npm_lifecycle_event.startsWith('test:sdk')) {
    PATH = 'dist-test';
}
...

with test:sdk being the name of my npm script, and tell karma to serve this directory
karma.conf.js
...
if (process.env.npm_lifecycle_event.startsWith('test:sdk')) {
  webpackConfig.output.publicPath = 'base/dist-test/';
}
...
module.exports = function(config) {
  ...,
  config.set({
    ...
    files: [
      'src-test/index.ts',
      {
        pattern: 'dist-test/**/*',
        included: false
      }
    ],
    ...

. In order to achieve hot reloading for test driven development, I use https://github.com/open-cli-tools/concurrently in a js starter script
run-sdk-test.js
const concurrently = require('concurrently');
const { result, commands } = concurrently(
  [
    { command: 'rm -rf dist-test; NODE_OPTIONS=--no-deprecation webpack --watch;', name: 'webpack' },
    { command: 'karma start  --browsers ChromeCI --singleRun false', name: 'karma'},
  ],
  {
    prefix: 'name',
    killOthers: ['failure', 'success'],
    successCondition: 'first',
    restartTries: 3
  }
);

commands[1].kill('SIGTSTP');
console.log(`paused ${commands[1].name} process until ${commands[0].name} compile successfully`);
commands[0].stdout.subscribe(o => {
  if (o.toString().match(/compiled .{0,10}successfully/)) {
    console.log(`resuming ${commands[1].name} process`)
    commands[1].kill('SIGCONT');
  }
  if (o.toString().match(/compiled with .{0,10} error/)) {
    console.log(`kill ${commands[1].name} process`)
    commands[1].kill('SIGKILL');
  }
});

result.then(res => console.log(`exited with ${JSON.stringify(res.map(p => p.exitCode))}`));

For completeness my package.json scripts section:
  "scripts": {
    ...
    "test:sdk": "rm -rf dist-test; NODE_OPTIONS=--no-deprecation webpack; karma start",
    "test:sdk-tdd": "node run-sdk-test.js",
    ...
  },

I hope this might help someone and that I haven't forgotten anything

As karma is now deprecated and coming up on EOL, we are no longer planning on any significant enhancements to this project and are instead going to focus on security updates, stability, and a migration path forward as karma's lifecycle comes to an end.
Thank you for supporting and using this project!

I have solved this issue by upgrading karma dependencies
for example:
"karma": "^2.0.0",
"karma-chrome-launcher": "^3.1.0",
"karma-coverage": "^1.1.1",
"karma-coverage-istanbul-reporter": "^2.1.1",
"karma-firefox-launcher": "^0.1.6",
"karma-jasmine": "^1.1.0",
"karma-ng-html2js-preprocessor": "^0.1.2",
"karma-sourcemap-loader": "^0.3.7",
"karma-spec-reporter": "0.0.32",
"karma-webpack": "^4.0.2",
to

"karma": "^6.3.4",
"karma-chrome-launcher": "^3.1.0",
"karma-coverage": "^2.0.3",
"karma-coverage-istanbul-reporter": "^3.0.3",
"karma-firefox-launcher": "^2.1.2",
"karma-jasmine": "^4.0.2",
"karma-ng-html2js-preprocessor": "^1.0.0",
"karma-sourcemap-loader": "^0.3.8",
"karma-spec-reporter": "^0.0.34",
"karma-webpack": "5.0.1",

in addition to update frameworks in karma.config.js to be
  frameworks: ['jasmine', 'webpack'],


editOnFileSave uses new workspace.onWillSaveTextDocument event

p4 edit command completes prior to completing save.
fix issue #16

Not a huge fan of Promise stuff and onFufill() spam but it works.


why

why do u not wanna help ppl set this up, if u put it on github dont expect everyone to know how to

its so basic just
npm run build
npm run start
use chatgpt


Initializing timeout box is missing from HealthCheck tab

Rancher Version:
v0.63.0
We've introduced the ability to set an initializing time out so that if a service is stuck in initializing state, it will start to recreate the containers.

Are there any plans (I couldn't find an existing issue) to give better feedback on the "initializing forever" issues? Off the top of my head, I've run into:

Registry not configured.
Registry 401
No hosts available to schedule container
Image / tag does exists on registry

It would be great to bubble up these states. Not critical, but it seems like the majority of my user questions are always "Hey, it is stuck in Initializing forever".

@andyshinn In v0.63.0, we've added this issue to address a lot of what you mentioned.
https://github.com/rancher/rancher/issues/3630
Containers can now have an "Error" state.

The service will be stuck in "Activating" but if you click on the containers, you can see the error state of the container and the message of why it failed.

Ah, great. I didn't see that in the release notes. I'll try and get upgraded soon.

Version - master 3/16
Verified Added and posting