Release: 0.1.8

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.45%. Comparing base (a01fef2) to head (3935964).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
- Coverage   60.49%   60.45%   -0.05%
==========================================
  Files          44       44
  Lines        4749     4749
  Branches      571      571
==========================================
- Hits         2873     2871       -2
- Misses       1633     1634       +1
- Partials      243      244       +1

Flag
Coverage Δ

pytest
60.45% <ø> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes


Recordset keeps refreshing content whenever you focus on the window

This issue is because of the $window.onfocus event handling for record add. We need to disable the event handling for recordset page.
To test it you can visit any recordset page and change your tab and come back to the recordset page again. The content gets refreshed. You can also try clicking the paging button, which again refreshes the content.

@shinyichen Will this problem be addressed by your latest pull request?

This is a duplicate of #831


Change extension folder structure to reduce file name conflicts

Which branch your pull-request should merge into?

2.1: BugFixes and Improvements for Current LTS branch

Describe your changes
Moved each extension into its own "src" folder.
Each extension CMakeList.txt now sets up the include paths for that extension.
LUA bindings generator updated, but this needs to be checked.
Fix issue with detecting Effekseer and DrawNodeEx extensions in cpp-tests.
Note that I manually updated the auto-generated lua bindings, so I haven't yet tested the changes to the LUA binding generator to see if it does generate the correct output. Hopefully that is the case, but if not, then any help with that specific part would be appreciated.
It seems that a few existing issues surfaced when the extension folder structure was changed, such as header files to inactive extensions being included when they shouldn't be.
FYI, the changes in this PR shouldn't break any existing code.  If anything, it would be a few include statements that would need to be fixed up in a project, assuming it uses extensions.
Issue ticket number and link
#1645
Checklist before requesting a review
For each PR

[ ] Add Copyright if it missed:
- "Copyright (c) 2019-present Axmol Engine contributors (see AUTHORS.md)."

[x] I have performed a self-review of my code.
Optional:

[x] I have checked readme and add important infos to this PR.
[ ] I have added/adapted some tests too.

For core/new feature PR

[ ] I have checked readme and add important infos to this PR.
[ ] I have added thorough tests.

The LUA binding generator should be working now. If there are any concerns or suggestions, then I'll get around to having a look at them in 2 days time.

lgtm

Hold off on any merging. One last thing to do, which is fixing the pre-built paths in AXLinkHelpers.cmake.

@rh101 the bot try override luabindings: https://github.com/axmolengine/axmol/pull/1648


repairing link to ModeDashboardExtractor in README

Cf. issue https://github.com/lyft/amundsen/issues/348
Summary of Changes
The last sentence of readme was:

To see in action, take a peek at ModeDashboardExtractor

The link was dead. I updated it with what seemed to be the right one: https://github.com/lyft/amundsendatabuilder/blob/master/databuilder/extractor/dashboard/mode_analytics/mode_dashboard_extractor.py

the cla check fails, normally it is due to you haven't configured your local github setting(email etc). Could you help to fix it?

Hi, it seems I had to sign the CLA (strange it didn't ask me to sign before submiting the PR). Now it seems fine. Sorry for the hurdle and thanks for the great work.

@fBedecarrats seems you closed the PR before it got merged. Can yo re-open?

thanks @jornh bringing it up, just reopen the pr :)

Hi, sorry @jornh but I'm confused. I see that @feng-tao  did somdthing an now the PR appears as successfully merged on my side. Do you still need me to re-open it ?

don't worry, i reopen your pr and merge it. Previously your pr is closed without merge which causes the confusion.

Yep exactly, @feng-tao simply grabbed it and did a few clicks before you could 🙂
Thanks both of you!


Add pytest ordering plugin

Allows having a test that just establishes a cluster
is up. So, if the cluster fails to come up, the user
will see waiting for the test_cluster_is_up and not
some arbitrarily chosen test

@cmaloney this is ready for review

:ship:

Manually checked / verified first test run is always the new "Test_cluster_is_up" -- https://teamcity.mesosphere.io/viewLog.html?buildId=395922&buildTypeId=ClosedSource_Dcos_IntegrationTests_CloudIntegrationTests_DcosOssCcmInstallTestAp&tab=buildLog#_state=37&focus=502

@cmaloney same gist, more specific implementation, PTAL

:ship: assuming the first thing comes first in all the tests we run

Confirmed: all runs had test_cluster_is_up as the first test


Rule rebuild on plyara.utils.rebuild_yara_rule using external variable as a part of loop condition - bug

Here is the case.
File test.txt:
test test test test test

rule:
rule sanity_check_external_variables {
    meta:
        author = "Rakovskij Stanislav / disasm.me"
        date = "22.08.2020"
    strings:
        $a = "test"
    condition:
        for count_of_test i in (1..#a) : ( @a[i] < 100 )
}

Sanity check using yara engine:
/testing_rules> yara d6.yar -d count_of_test=1 test.txt
sanity_check_external_variables test.txt
/testing_rules> yara d6.yar -d count_of_test=3 test.txt
sanity_check_external_variables test.txt
/testing_rules> yara d6.yar -d count_of_test=5 test.txt
sanity_check_external_variables test.txt
/testing_rules> yara d6.yar -d count_of_test=6 test.txt

Test case using plyara 2.1.1:
m = """rule sanity_check_external_variables {
    meta:
        author = "Rakovskij Stanislav / disasm.me"
        date = "22.08.2020"
    strings:
        $a = "test"
    condition:
        for count_of_test i in (1..#a) : ( @a[i] < 100 )
}
"""

parser = plyara.Plyara()
parser.parse_string(m)

y = plyara.utils.rebuild_yara_rule(parser.rules[0])
print(y)

Output:
rule sanity_check_external_variables
{
	meta:
		author = "Rakovskij Stanislav / disasm.me"
		date = "22.08.2020"

	strings:
		$a = "test"

	condition:
		for count_of_testi in (1..#a) : (@a[i]<100)
}

Expected condition: for count_of_test i in (1..#a) : (@a[i]<100)
I think the error is here - https://github.com/plyara/plyara/blob/master/plyara/utils.py#L470
To solve this problem you should check is this condition a part of for ... ... in block or not.

@rakovskij-stanislav Thanks for the report. I'll get this fixed.

@rakovskij-stanislav I severely dislike the rebuild_yara_rule function. It is basically impossible to maintain or improve. Plyara 3.0 will solve all rule rebuilding problems because it will be a real compiler rather than a kludge formatter like this function. I have no timeline for releasing 3.0, however.
That being said, what you have reported is a bug. The amount of code needed to do it right in all cases is just to much. However, I have fixed this particular bug with a simple fix. I have verified that the resulting yara rules are valid yara. There are now a few more spaces in the rebuilt output. I hope you're able to deal with that. This broke the unit test for test_rebuild_yara_rule but I adjusted that expected result to accomodate all the extra spaces. I also caught a typo in the test rule for that unit test (git blame: wasn't me!).
This should be an adequate bandaid until 3.0 is ready. Side note: if you would like to join the project and have time, let me know. Maybe you can tackle fixing this function properly. I don't use rule rebuilding, so I have no driver to spend the time on it.


add .nojekyll to generated docs folders

Is your feature request related to a problem? Please describe.
I'm trying to serve up the docs folder for js on github and I have to add a .nojekyll empty file to the /docs folder every time for it to work on github pages
Describe the solution you'd like
Add .nojekyll to docs folders

This still needs resolution


Podcast Feed Loader: Code shouldn't directly access environment variables

Directly accessing environment variables makes it so the setting can't be test appropriately.
Accessing the environment variables should be secluded into a single (humble object) file.
Also, may want to consider prefixing the environment variables to reduce the chance of collision.

The podcast-feed-loader now checks for a .env file by default, and it will fallback to environment variables: #242
Everything is hidden behind a settings file so the code doesn't care where it comes from


Github link does not exists

Link to template does not exists.

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

ID: b1de5eda-9c2f-0f5d-13c0-84a229d84673
Version Independent ID: 5466271b-030f-951d-65aa-3f596e1d2640
Content: Create an Microsoft Azure Confidential Ledger by using Azure Resource Manager template
Content Source: articles/confidential-ledger/quickstart-template.md
Service: azure-resource-manager
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

The broken link for the Deploy to Azure button is affected by a pending pull request, Azure/azure-quickstart-templates#9633.

The template's pull request was merged. Verified that the article's Deploy to Azure button opens the template.

#please-close


problem with ion-select RTL v3.5.3

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

ion-select doesn't show radio buttons correctly

Expected behavior:

Steps to reproduce:
<!-- If you are able to illustrate the bug or feature request with an example, please provide steps to reproduce and if possible a demo using one of the following templates:
any ion-select component with RTL project
![screen shot 2017-07-18 at 4 29 24 am](https://user-images.githubusercontent.com/3624441/28296627-01d720e0-6b72-11e7-8432-b3c40d4a8dd4.png)

**Ionic info:** (run `ionic info` from a terminal/cmd prompt and paste output below):

```
global packages:

    @ionic/cli-utils : 1.5.0
    Cordova CLI      : 7.0.1
    Gulp CLI         : CLI version 1.3.0 Local version 3.9.1
    Ionic CLI        : 3.5.0

local packages:

    @ionic/app-scripts              : 2.0.2
    @ionic/cli-plugin-cordova       : 1.4.1
    @ionic/cli-plugin-gulp          : 1.0.2
    @ionic/cli-plugin-ionic-angular : 1.3.2
    Cordova Platforms               : android 6.2.2 browser 4.1.0 ios 4.4.0
    Ionic Framework                 : ionic-angular 3.5.3

System:

    Node       : v7.10.0
    OS         : macOS Sierra
    Xcode      : Xcode 8.0 Build version 8A218a
    ios-deploy : 1.9.0
    ios-sim    : 5.0.13
    npm        : 5.3.0```

Hey @AmitMY , would you be able to take a look at this one?

solution is here: https://github.com/ionic-team/ionic/issues/10685#issuecomment-315991739
sorry


CloudFormation Lambda function ARN with substitution support

Currently the validator do not support lambda function arn that contains CloudFormation substitution.
if lambda arn in json code look like arn:aws:lambda:${AWS::Region}:${AWS::AccountId}:function:${LambdaName}
the  result is:
✕ State machine definition is invalid:
data.States['Test'] should NOT have additional properties
data.States['Test'] should NOT have additional properties
data.States['Test'] should NOT have additional properties
data.States['Test'] should NOT have additional properties
data.States['Test'] should NOT have additional properties
data.States['Test'].Resource should match pattern "^arn:aws:([a-z]|-)+:([a-z]|[0-9]|-):[0-9]:([a-z]|-)+:[a-zA-Z0-9-.]+(:($LATEST|[a-zA-Z0-9-]+))?$"
Support for CloudFormation arn format allow to create json file with ASL code that is later injected into an auto generated CloudFormation file using a development language, and run ASL validation test into a CI/C pipeline prior the injection into CloudFormation template.
May I suggest replacing existing regex in src/schemas/task.json with:
^(arn:aws:([a-z]|-)+:(${[a-zA-z:-]+}|([a-z]|[0-9]|-)):(${[a-zA-z:-]+}|[0-9]{12}):([a-z]|-)+:(${)?[a-zA-Z0-9-.]+(})?(:($LATEST|[a-zA-Z0-9-]+))?$)|(\${.\})
this will allow support for lambda arn with formats:
arn:aws:lambda:us-east-1:999999999999:function:Lambda-test
arn:aws:lambda:${AWS::Region}:${AWS::AccountId}:function:${LambdaName}
arn:aws:lambda:us-east-1:999999999999:function:Lambda-test:$LATEST
and will make the test successful even when Lambda arn includes CloudFormation substitutions.

sorry just saw it was aded to version 1.9.6. works fine after i updated.


Not able see the data of Pods/Deployment/Statefulset on the pre-configured grafana.

What did you do?
I have just installed the kube-prometheus on my cluster.
What did you expect to see?
Pre-Configured Dashboard for the Pods/Deployment/Statefulset/etc
What did you see instead? Under which circumstances?
I can see node related graph, but when it comes to pods related workload not able to see anything. Its just giving NA.
Environment
Pre-Prod

Prometheus Operator version:
insert image tag or Git SHA here

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.1", GitCommit
:"1dc5c66f5dd61da08412a74221ecc79208c2165b", GitTreeState:"clean", BuildDate:"201
7-07-14T02:00:46Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.7", GitComm
it:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2
018-08-20T09:56:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
insert how you created your cluster: acs-engine.

Manifests:

insert manifests relevant to the issue

Prometheus Operator Logs:

insert Prometheus Operator logs relevant to the issue here

Node Exported Logs

time="2018-09-26T11:32:58Z" level=info msg="Listening on :9100" source="node_exporter.go:111"
time="2018-09-26T11:34:37Z" level=error msg="ERROR: infiniband collector failed after 0.000680s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:34:37Z" level=error msg="ERROR: infiniband collector failed after 0.001399s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:34:43Z" level=error msg="ERROR: infiniband collector failed after 0.000661s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:34:43Z" level=error msg="ERROR: infiniband collector failed after 0.000999s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:35:13Z" level=error msg="ERROR: infiniband collector failed after 0.021550s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:35:13Z" level=error msg="ERROR: infiniband collector failed after 0.000814s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:35:43Z" level=error msg="ERROR: infiniband collector failed after 0.020590s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:35:43Z" level=error msg="ERROR: infiniband collector failed after 0.001209s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:36:13Z" level=error msg="ERROR: infiniband collector failed after 0.022243s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:36:13Z" level=error msg="ERROR: infiniband collector failed after 0.041703s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:36:43Z" level=error msg="ERROR: infiniband collector failed after 0.000838s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:36:43Z" level=error msg="ERROR: infiniband collector failed after 0.001064s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:37:13Z" level=error msg="ERROR: infiniband collector failed after 0.001676s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"
time="2018-09-26T11:37:13Z" level=error msg="ERROR: infiniband collector failed after 0.001240s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"```

* Kube state Metrics Logs
```I0926 11:33:07.800467       1 main.go:186] Starting metrics server: <IP_ADDRESS>:8080
E0926 11:33:07.902006       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list secrets at the cluster scope
E0926 11:33:07.903804       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Namespace: namespaces is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list namespaces at the cluster scope
E0926 11:33:07.999175       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.ConfigMap: configmaps is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list configmaps at the cluster scope
E0926 11:33:07.999687       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v2beta1.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list horizontalpodautoscalers.autoscaling at the cluster scope
E0926 11:33:08.000150       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Endpoints: endpoints is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list endpoints at the cluster scope
E0926 11:33:08.000194       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list persistentvolumes at the cluster scope
E0926 11:33:08.904261       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list secrets at the cluster scope
E0926 11:33:08.905088       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Namespace: namespaces is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list namespaces at the cluster scope
E0926 11:33:09.101081       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.ConfigMap: configmaps is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list configmaps at the cluster scope
E0926 11:33:09.101081       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v2beta1.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list horizontalpodautoscalers.autoscaling at the cluster scope
E0926 11:33:09.101286       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Endpoints: endpoints is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list endpoints at the cluster scope
E0926 11:33:09.203038       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list persistentvolumes at the cluster scope
E0926 11:33:09.999401       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list secrets at the cluster scope
E0926 11:33:10.000321       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Namespace: namespaces is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list namespaces at the cluster scope
E0926 11:33:10.103061       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.ConfigMap: configmaps is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list configmaps at the cluster scope
E0926 11:33:10.200734       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v2beta1.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list horizontalpodautoscalers.autoscaling at the cluster scope
E0926 11:33:10.201435       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.Endpoints: endpoints is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list endpoints at the cluster scope
E0926 11:33:10.300657       1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/collectors.go:91: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:serviceaccount:monitoring:kube-state-metrics" cannot list persistentvolumes at the cluster scope```

How did you install the stack?

I have used this one year before on k8s version 1.7.2. And cloned that repo that time, so that i can use it later. So the same repo i have used and not cloned the latest one as there are many changes happened.
So on that version we have hack/cluster-monitoring/deploy, so i have used that script to do that.
But in this case, we have the k8s version as 1.10.7

Yes there are lots of changes that are necessary as there were breaking changes in Kubernetes, so you will have to use the latest version of the stack.

Even in the new repo, the pod data is not coming through.
Checked the log for the kube-state-metrics, didn't find anything wrong.

I deployed with the latest images today and I get the same errors as above.
Running kubernetes 1.11.3 in Azure AKS.

I deployed using coreos helm charts in azure aks with kubernetes 1.9.11
time="2018-10-26T12:57:00Z" level=info msg="Listening on <IP_ADDRESS>:9100" source="node_exporter.go:76"
time="2018-10-26T12:57:15Z" level=error msg="ERROR: infiniband collector failed after 0.000851s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:123"
time="2018-10-26T12:57:30Z" level=error msg="ERROR: infiniband collector failed after 0.025460s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:123"

Seems to be solved in the latest version of node-exporter. Tested with node-exporter v0.17.0-rc.0 and I then don't get the errors. So I guess we'll have to wait for the release and for the coreos helm charts to be updated.

Happens still when installing through kube-prometheus/manifests both AKS 1.13.10 and 1.14.6


Super slow iteration with trivial custom transform

Describe the bug
Dataset is 10X slower when applying trivial transforms:
import time
import numpy as np
from datasets import Dataset, Features, Array2D

a = np.zeros((800, 800))
a = np.stack([a] * 1000)
features = Features({"a": Array2D(shape=(800, 800), dtype="uint8")})

ds1 = Dataset.from_dict({"a": a}, features=features).with_format('numpy')

def transform(batch):
	return batch

ds2 = ds1.with_transform(transform)

%time sum(1 for _ in ds1)
%time sum(1 for _ in ds2)

CPU times: user 472 ms, sys: 319 ms, total: 791 ms
Wall time: 794 ms
CPU times: user 9.32 s, sys: 443 ms, total: 9.76 s
Wall time: 9.78 s

In my real code I'm using set_transform to apply some post-processing on-the-fly for the 2d array, but it significantly slows down the dataset even if the transform itself is trivial.
Related issue: https://github.com/huggingface/datasets/issues/5841
Steps to reproduce the bug
Use code in the description to reproduce.
Expected behavior
Trivial custom transform in the example should not slowdown the dataset iteration.
Environment info

datasets version: 2.18.0
Platform: Linux-5.15.0-79-generic-x86_64-with-glibc2.35
Python version: 3.11.4
huggingface_hub version: 0.20.2
PyArrow version: 15.0.0
Pandas version: 1.5.3
fsspec version: 2023.12.2

Similar issue in text process

tokenizer=AutoTokenizer.from_pretrained(model_dir[args.model])
train_dataset=datasets.load_from_disk(dataset_dir[args.dataset],keep_in_memory=True)['train']
train_dataset=train_dataset.map(partial(dname2func[args.dataset],tokenizer=tokenizer),batched=True,num_proc =50,remove_columns=train_dataset.features.keys(),desc='tokenize',keep_in_memory=True)

After this train_dataset will be like
Dataset({
    features: ['input_ids', 'labels'],
    num_rows: 51760
})

In which input_ids and labels are both List[int]
However, just iter on dataset cost 7.412479639053345s ……？
for j in tqdm(range(len(train_dataset)),desc='first stage'):
    input_id,label=train_dataset['input_ids'][j],train_dataset['labels'][j]

The transform currently replaces the numpy formatting.
So you're back to copying data to long python lists which is super slow.
It would be cool for the transform to not remove the formatting in this case, but this requires a few changes in the lib

This also affects iterable datasets, making map unusable for data with large arrays, unless there is some workaround?

For iterable datasets you should be able to do this without slow downs
ds = ds.with_format("arrow").map(...)

I haven't tried with "numpy" though, maybe there is a step that does Arrow -> List -> NumPy instead of Arrow -> NumPy directly. If it's the case it would be cool to avoid that

Thanks! this works for me
However, it raises an error if batched=False due to map's batch_size affecting the batch size of the RebatchedArrowExamplesIterable - is this a bug?

Thanks for fixing @alex-hh !

opened a new issue for the numpy slowdown #7206


RDKTV-5283: Add power_led on/off index

Reason for change: To add powerled on/off index for frontpanel plugin
Test Procedure: Verify if the powerLedOn/powerLedOff requests are returning true
Risks: Low
Signed-off-by: bp-athoms139<EMAIL_ADDRESS>

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Wrong results with prange on Linux with Numba 0.55.1

Hello,
I have observed an issue with version 0.55.1 which seems to be related to one of the previously resolved issues involving a race condition. Interestingly, I only observe it on Linux and not on macOS. Here is a simple code snippet that reproduces it:
import numba as nb
import numpy as np

def func_fail(arr):
    res = np.zeros(arr.shape[1])
    for i in nb.prange(arr.shape[0]):
        for j in range(arr.shape[1]):
            res[j] += arr[i][j]
    return res

func_fail_numba = nb.njit(fastmath=True, parallel=True)(func_fail)

def func_success(arr):
    res = np.zeros(arr.shape[1])
    for i in nb.prange(arr.shape[0]):
        res += arr[i]
    return res

func_success_numba = nb.njit(fastmath=True, parallel=True)(func_success)

if __name__ == "__main__":
    assert nb.__version__ == "0.55.1"
    np.random.seed(42)
    arr = np.random.uniform(0, 1, (20, 40))
    assert np.allclose(func_success(arr), func_success_numba(arr))
    assert np.allclose(func_fail(arr), func_fail_numba(arr))

Even though func_success_numba and func_fail_numba should have the same output, only func_success_numba returns the same result as the pure Python implementation. In my observations, the final assert statement only passes on macOS and not on Linux, even though both have the same llvmlite version (0.38.0).

Thanks for the report @msuruzhon. I cannot seem to reproduce this on branch main using linux. When it "fails" what is the magnitude of the difference of the results?

Thanks @stuartarchibald. It seems that the value provided by func_fail_numba is non-deterministic, but in one of the cases, I had a mean absolute error of 4.7 between both arrays, so much larger than e.g. 1e-8. Also, I ran the pip version and not the one from main, so I am not sure if that makes any difference. I would also not be surprised if this error had some platform dependence, so it might be difficult to reproduce.

@msuruzhon thanks for checking the magnitude of the discrepancy, this is indeed unlikely to be numerical error, especially if it's non-deterministic too.
@DrTodd13 do you recall if the use case above is supported?

Both cases should work.  I can't think of a reason why the observed behavior should happen and if we can't reproduce then I wouldn't know where to even suggest to resolve the problem.


0.10.0 upgrade guide

Changes: https://github.com/ramda/ramda/compare/v0.9.1...v0.10.0
Name changes:

R.mixin → R.merge #783
R.foldl → R.reduce #769 #775
R.foldr → R.reduceRight #769 #775
R.foldlIndexed → R.reduceIndexed #775
R.foldrIndexed → R.reduceRightIndexed #775
R.lPartial → R.partial #775
R.rPartial → R.partialRight #775
R.mapAccumL → R.mapAccum #775
R.mapAccumR → R.mapAccumRight #775
R.scanl → R.scan #775
R.unfoldr → R.unfold #775
R.pCompose → R.composeP #775
R.pPipe → R.pipeP #775

Improvements:

R.construct and R.constructN now support the Date constructor #761
R.invert now ignores inherited properties #795
R.lift now works with Fantasy Land Applicatives #782
R.memoize now reuses cached "false" values #785
R.memoize once again works with nullary functions #787
:curry: R.merge (formerly R.mixin) is now curried op-style #745
:warning: R.of no longer takes an optional second argument #784
R.reject now dispatches to "filter" method if present #799
R.sortBy now preserves object identity #789

Additions:

:new: R.defaultTo #788
:new: R.dissoc #781
:new: R.mergeAll #778

Thanks for the awesome work. I like ramda and use it in some product now.
But please don't remove apis directly like this. Maybe use some warning will be better, and keep them as  alias.
( That's true, we just need to rename for upgrading. howerever, not user-friendly enough. is it? :-)

We've been trying to incorporate Ramda into our codebase but with the latest updates it's getting pretty scary (reduce randomly removed, mixin renamed to merge). As Morlay said it would be nice, until a major version is released, to at least maintain some aliases so we can spend more time using Ramda and less time fixing broken methods.

I get that it still isn't technically a full release, but the changes get kind of crazy with the loss of the api without alias. I agree with @morlay . Could you guys/gals at least alias while providing a deprecation flag until the next release. That way people know to start changing their stuff. It is starting to make me not want to use Ramda until it is in at a full version release.

I ask you to reconsider #786

I think we may well have to reconsider something like that, @TheLudd.
But I also think we're almost at the end of this.  We're hoping to hit a 1.0 release in a few months, and after that we expect to be following semver scrupulously.  At the moment, we're trying to make sure our API is actually in shape to be released as a 1.0 version.  Some of that involves the kind of normalization that's gone on in the last two releases.  We've chosen to do this without the safety net of aliases or deprecation warnings, because, as @davidchambers points out, it should generally be easy to incorporate such changes with a global search-and-replace.
I know it's not ideal.  And if we have another major round of it, we'll reconsider the approach.  But I do think we're almost done with it.
Sorry.

I agree with @Aourin. @CrossEye - I understand that you are working towards a 1.0 version but you should definitely follow semver now as many of your users are incorporating this library into their projects. Please consider keeping aliases until you reach a major version.

you should definitely follow semver

We do. From the spec:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

@davidchambers Before I say anything, let me take a moment to thank you for all you do to make ramda an awesome library. However...
If you are going to quote the spec, please do not do so out of context:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a
stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot
about backwards compatibility, you should probably already be 1.0.0.

TL:DR Don't diss us who love ramda enough to be using it in production already. Aliasing is a simple solution.

I'd say we meet1/3 of these requirements:

your software is being used in production :heavy_check_mark:
you have a stable API on which users have come to depend :x:
you're worrying a lot about backwards compatibility :x:

My apologies for the growing pains, but we really need the pre-1.0 time to tinker with things and get them as right as we can.

@buzzdecafe:
I think that list was supposed to be: "If any of these conditions is true..."
I think you and I are having a harder time because although we are the initial authors of the library, we are not using it in our day job yet.  I suspect @davidchambers is doing so but that his process lets him very easily migrate versions.
This is making me rethink temporary aliases as at least a short-term solution, either on our own or by promoting Aourin's Ramda-Aliases.

I'm thrilled to hear, @Luckvery, that I'm not the only one using Ramda in production. :)
I've been using Ramda in production since 0.2.x. We now use it in more than a dozen projects at Plaid. In the past 48 hours I opened 29 pull requests upgrading Ramda in these projects (some were still on 0.7.x or 0.8.x so required multiple upgrades). These upgrades took ten minutes each, on average.
I find a ten-minute upgrade acceptable for Ramda at this point in its life. Since upgrading is voluntary, we're free to continue to use whichever version we're currently using until we can devote some time to upgrading. When we decide to upgrade, the task should not be onerous.
Upgrading from 0.n.x to 0.(n + 1).x should never be done blindly. Even in a release in which no functions are renamed there could be any number of breaking changes. The upgrade process is thus very similar regardless of whether a release includes name changes:

Preparation:
$ cd path/to/project
$ git checkout master
$ git pull origin master
$ git checkout -b ramda
$ vim package.json  # update Ramda dependency
$ rm -r node_modules
$ npm install  # install the new version

Read the upgrade guide one line at a time, making any necessary changes. ack and sed -i '' are very useful here.

Run tests, if present:
$ npm test

Address any issues discovered in the previous step.

Commit and push:
$ git add .
$ git commit -m<EMAIL_ADDRESS>$ git push origin ramda

Open a pull request. Include a link to the upgrade guide in the description to provide context for reviewers.

What would including aliases for renamed functions buy us? It would reduce the number of changes required in step 2.
Renaming functions is the easiest part of this step:
$ find lib -name '*.js' -print0 | xargs -0 sed -i '' 's/R[.]mixin/R.merge/g'

Replace mixin and merge with the next old–new pair and repeat.
Other sorts of change require more attention. For example, the order of arguments to R.propOr changed in 0.9.0. Easily the scariest changes are semantic changes. When R.isEmpty was updated to return false when applied to null/undefined, we had to review every call site to ensure the function is only ever applied to an array-like object, and add xs == null || in sites which required the old behaviour.
To me, having to rename functions with each minor release until we reach 1.0.0 is not a big cost in absolute terms, nor is it a big cost relative to the other code changes upgrades sometimes require.
Does one of you have an open-source project using an old version of Ramda? I'm interested in understanding what it is that's making upgrading a daunting task in some cases. If you provide a link to the project I'll submit a pull request and we can discuss the pain points.

@davidchambers that answer might be useful boilerplate for future upgrade guides

@davidchambers
I think you make a valid point about upgrading when you feel like it. Also, changes to our projects flow very similar to yours.

In the past 48 hours I opened 29 pull requests upgrading Ramda in these projects (some were still on0.7.x or 0.8.x
so required multiple upgrades). These upgrades took ten minutes each, on average.

So if my math serves me that is 29 X 10 minutes totaling 290 minutes or just under 5 hours. If that works for you than I don’t think I am skillful enough to construct an argument that would sway your opinion anyway lol.

Easily the scariest changes are semantic changes.

I couldn’t agree with you more. Aliasing just means that I would only have to focus on these semantical changes. We currently have ramda in production in 2 small projects (including tests) and are now using it in our largest project for our most demanding (read we want changes yesterday type) client.

To me, having to rename functions with each minor release until we reach 1.0.0 is not a big cost in absolute terms, nor
is it a big cost relative to the other code changes upgrades sometimes require.

When managing several projects  in (what some would consider) a fast paced environment the frequent changes to ramda aren’t daunting they are just a pita i’d like to avoid if I could.
oh well.  I'm still going to use ramda anyway.

Thank you for elaborating your thoughts, @Luckvery.

I think you make a valid point about upgrading when you feel like it.

The main problem with this defence (if I may undermine my own defence) is that we don't yet expose documentation for old versions (see #821). A mismatch between API and documentation is no fun.

When managing several projects in (what some would consider) a fast paced environment the frequent changes to ramda aren’t daunting they are just a pita i’d like to avoid if I could.

Fair point. There's a trade-off between ease of upgrading and simplicity of Ramda's internals. Aourin/ramda-alias keeps the aliases out of Ramda and makes upgrading easier. It seems like a good solution until we hit 1.0.0.

It's the early adopter cost of working with a pre 1.0 lib. Ramda has been pre 1.0 since 2013 so users should be used to this kind of shift and change. Libs need the freedom to adjust in their pre 1.0 period to iron things out and create a better experience for their users without having the back-compat burden.

There's something to be said about sitting behind the pre-1.0 safety net for multiple years though. I'm not complaining, and we'll still continue to use Ramda in our production environments, but imagine if Node took a similar approach and started introducing massive breaking changes just because they're pre-1.0. Early adopters of Ramda will make do because they want to use Ramda, so they'll make the appropriate adjustments to the API updates. The argument is more about general reliability and ease-of-upgrade than anything.

You can't really compare Node as it has it's own versioning scheme and doesn't follow semver. Early adopters are generally super fans which follow the project's changes and activity closely and as such should cut the maintainers some slack. As an early adopter of a lib that's been unstable for ~2 years you've chosen style over stability and part of that means dealing with breaking changes. Ramda could as a courtesy bump the minor version when introducing breaking changes so the ~ version range would work (they may already be doing that).

Ramda could as a courtesy bump the minor version when introducing breaking changes so the ~ version range would work (they may already be doing that).

That's our approach, yes. I use 0.9.x, 0.10.x, etc. when specifying my Ramda dependencies.

The plan is to hit 1.0 fairly soon.
Ramda started as a personal project, a way to learn this stuff, by @buzzdecafe and me, with an earlier library back in April 2013.  By that June, we'd learned a lot and realized that if we were going to have a practical library, we were going to have to sacrifice much of the FP elegance.  So we created Ramda in June, 2013.  But it was still just our own playground for quite some time.  There were a few GitHub watchers, mostly our friends, but no real activity except that piqued by our own interests.
Then last May, @buzzdecafe and I were in Frontend Masters' course, Hardcore Functional Programming in JavaScript only to find that they were using our library for the main examples!
  And it's been a wild ride ever since.
Sometime around either the second anniversary of the birth of Ramda (in June) or the first anniversary of its announcement (May), I'm hoping that we can be ready to release a 1.0 version.  We seem to be getting pretty close right now, due to the hard work of all our contributors, but most especially to @davidchambers' eye for detail.
We seem to be converging on a very useful and clean API, our performance is in line with other similar libraries, and there is clearly a desire for this sort of tool.
So I don't think we'll be in this sort of limbo much longer.

Are you guys not adding the release notes to the release page anymore? Is there another easier-than-searching-the-issues place to find them?

Is there any particular reason for not to add the new names and simply deprecate the old ones It doesn't add that much to the size of the library, but keeps a lot of breakages from happening until we all catch up.

@kedashoe (sorry, too much activity, and missed this a few days ago): If we haven't been keeping up the release page, it's been an oversight.  I think we're going to try to keep that up as well as a changelog.
@elijahdorman: The parable presented a while ago convinced most of us that aliases were to be used very sparingly, if at all.  We have seemed to agree to run a version or two with a deprecation warning for a function that's due to be replaced.  (We haven't really talked about whether we'd use an alias during this transition.)  But we're really trying to reach the point where none of this makes much of a difference, as we've stopped significant API churn.


[FEATURE]

Description of new feature
e.g. I would like the ZTE 1234 XYZ v2.5 router to be supported
Describe alternatives you've considered
e.g. I have tried using --payload xxx but I get the following error < error >
Additional context
Add any other context or screenshots about the feature request here.
Attach config.bin for your device
Optional, but will help anyone trying to add support for the device.

Looks to have been opened in error.


Not useable as a standalone without GORM

The definitions for the Enter and Exit functions have the following the signatures:
func (state *State) Enter(fc func(value interface{}, tx *gorm.DB) error) *State
func (state *State) Exit(fc func(value interface{}, tx *gorm.DB) error) *State

As the second argument is explicitly typed as a gorm.DB pointer, there is no way to implement these functions without import the gorm package.

I enjoy the core functionality but also do not want GORM or unnecessary dependencies imported into my projects. I've created a fork over here that rips out the database functionality and includes passing tests.
I'll gladly port any patches that come up if other folks find issues.
https://github.com/cheapRoc/transition


OCPBUGS-40906: Add encapsulation flag to IPsecConfig struct

Add encapsulation flag to IPsecConfig struct.
This flag allows UDP encapsulation of IPsec related packets for things like firewall and NAT traversal
See RFC  3948 for specific uses

Please re-open this PR for IPSec encapsulation on IBM VPC cloud.

/reopen

/jira refresh

/assign @JoelSpeed @trozet @jcaamano

New user facing features should have an enhancement and a feature gate for their introduction. Do you have any design docs for this yet, or thoughts on feature gating this and what you'll need to do to be able to declare this stable?

This is a minor change w.r.t implementation and addressing this for a bug OCPBUGS-40906, do you still recommend to have feature gate and design doc update for this ?

/remove-lifecycle rotten

/retest-required

/retest

/assign @huiran0826

/test all
/lgtm

Thanks @JoelSpeed and @everettraven for the reviews and merging it finally !
It was a good exercise for me from API perspective.


add Cython and Java version

as requested :)

@zocker-160 Ahh very nice thank you! I'll take a look later tonight or tomorrow but merge it now.

@zocker-160 Cython version looks very cool! I haven't had the opportunity to play around with Cython yet, but I'll definitely look into it in more detail when I have more time. Thank you for your contributions!

@Matt-London sure no problem 👍
Cython is great actually, you get C performance with a syntax more similar to pyhton and you can flawlessly integrate it into existing python code

@zocker-160 Yeah, I'll definitely take a look!


Add NeonHelper.ParseNullableBool() and TryParseNullableBool()

We need this for cluster setup and it seems generally useful, so I'm going to add this to Neon.Common.  We'll also add TryParseNullableBool() for completeness.

DONE for v2.2.0


Allow subclassing of ListViewDataSource

I use immutable JS throughout my codebase and created an Immutable ListViewDataSource by subclassing ListViewDataSource. Currently cloneWithRowsAndSections creates a new instance of ListViewDataSource instead of cloning my subclass.
This pull request changes the hard coded ListViewDataSource to this.constructor.
https://www.npmjs.com/package/react-native-immutable-listview-datasource

Isn't a data source immutable already? In general we don't support subclassing classes in the public API.

Yes it's immutable, I'm being lazy, I mean Immutable JS data source. ListViewDataSource only works with plain JS.
It was easier to subclass, but I guess I could use composition instead of inheritance to solve my use case if subclassing is not supported.
I do think calling this.constructor is better for a clone method regardless of my use case thou.

I tried composition but now i'm left with a propType warning since
dataSource: PropTypes.instanceOf(ListViewDataSource).isRequired,

So the only way to provide an alternative DataSource is subclassing.


Add support for dark theme

Adding support for dark theme also described in this issue (Control does not account for dark theme #20)

The originally supported light theme remains mostly the same, except a few minor changes which are the following:

Hover color is lighter in both dark/light themes
Hover color is the same for selected and unselected items (that's why I removed .row:not(.selected):hover ruleset, but if there was any specific reason to differentiate these two hover states, let me know and I fix it)

I also had to update "vss-web-extension-sdk" to support applyTheme option for VSS.init(), so I changed it to the latest (at the moment of creating this PR). Regarding the used css variables, they are the same colors used by azure devops and are injected into the iframe by enabling the applyTheme option.

Sorry, but this code in this repo is not currently being maintained.


info about OrdMap

Hi @sabiwara,
I'm a master student in computer science and i'm working on benchmarking in elixir (using benchee) for my master thesis.
I'm benchmarking performances about your ordmap module and I want ask you where the need to develop this module came from and if you can suggest me some project where ord map have been used (searching on github i didn't get any significative result).
Thanks in advance,
Michele

Hi @micheleintrevado,
Unfortunately I'm not aware of any particular project using OrdMap, although people might be using it I don't really have a way to know.
It's been a while since I developed it so I don't recall accurately, but I found myself in a situation where I cared about both insertion order and key access, which I solved by using two data structures as accumulator. I came from Python which had an OrderedDict (later regular dicts got ordered too), my headspace back then was in immutable data structures, and I wondered how I could implement such a data structure efficiently and elegantly in Elixir. But it was more about trying to extend the capabilities of the language and intellectual curiosity than a concrete "need".
Good luck with your thesis, seems like a very interesting topic!


[Automation] Automatically merge dependabot changes and other maintenance work

Is your feature request related to a problem? Please describe.
There are an increasing number of automated tools and small changes that don't need as much attention from maintainers, such as version bumps where CI is sufficient to ensure the quality of the build.  These pull requests are often distracting and easy to ignore and they tend to pile up, it would be great if changes of this type could be automated.
Describe the solution you'd like
It would be great if there was a tool that checked after all CI checks had passed and would then automatically merge changes.
Describe alternatives you've considered
Keep depending on manual reviews by maintainers to merge changes.

With the status of the CI system this doesn't like much of a value to prioritize, of 10/18 CI only seems to be passing 25% of the time.


[e2e]: delegator-lowperms create main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v46.0.17
Run: https://github.com/slsa-framework/example-package/actions/runs/5727193474
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Trigger: create
Branch: v46.0.17
Date: Tue Aug  1 13:13:13 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v46.0.18
Run: https://github.com/slsa-framework/example-package/actions/runs/5739235834
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Trigger: create
Branch: v46.0.18
Date: Wed Aug  2 13:13:16 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v46.0.19
Run: https://github.com/slsa-framework/example-package/actions/runs/5744763789
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Trigger: create
Branch: v46.0.19
Date: Wed Aug  2 23:26:56 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v46.0.20
Run: https://github.com/slsa-framework/example-package/actions/runs/5744799767
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-lowperms.create.main.default.slsa3.yml
Trigger: create
Branch: v46.0.20
Date: Wed Aug  2 23:36:57 UTC 2023
Tests are passing now. Closing this issue.


⚠ SkipTheCommericals has degraded performance

In bb99baa, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 10008 ms

Resolved: SkipTheCommericals performance has improved in 28f13f8.


update the configuration

the cluster-token must be set to the new member, which will be add to the cluster.
otherwise, the new member will having a different cluster-id, treated as a member from other cluster.

I just tested it and it works fine with original guide.
Could you describe your problem in details first?

oh, sorry, I think this problem has been fixed.
issue 2836
I got the output like etcdserver: conflicting cluster ID with the target cluster.....
my version is 2.0.5, must set the cluster_token to avoid it.
the latest version maybe ok, but I haven't use it yet.

cluster_token is mostly used for bootstrap stage, and not required for join.
The issue you mentioned has been fixed, and it will print warning instead of fatal. But it is not change the clusterID logic.
Please list your steps and configuration, and say explicitly what succeeds and what fails.

Thanks a lot.  I find the root reason when I try to reproduct the situation.
I forgot to remove the new member's data-dir, it having old data in it. so the clusterID conflicted.
it has no relation with cluster-token. my fault,  thank you.


cmd/link: loading N packages takes O(N²) time

There are some deduplication scans in the linker to avoid loading the same package (same import path) multiple times. These use a linear scan over all packages already loaded, so loading N packages takes O(N²) time (even with no duplicates). These scans should be replaced by map checks, cutting the time for N packages to O(N).
I have a CL and will send it.

Hmm, how come gobot didn't close this issue when CL https://go-review.googlesource.com/c/44852/ was merged into master as https://github.com/golang/go/commit/51711d1429cb592c9ddc772e6362e74ac8545dc8.

Maybe because Github has been having problems today? https://status.github.com/messages

Ah, gotcha.


Fix: Resolve race condition in MoveGroupSequenceAction

Description
Replaced ReentrantCallbackGroup with MutuallyExclusiveCallbackGroup in MoveGroupSequenceAction::initialize to prevent race conditions during stress testing.
This change ensures sequential execution of callbacks, avoiding issues caused by concurrent execution.
Reference: https://github.com/moveit/moveit2/issues/3117
Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] Extend the tutorials / documentation reference
[ ] Document API changes relevant to the user in the MIGRATION.md notes
[ ] Create tests, which fail without this PR reference
[ ] Include a screenshot if changing a GUI
[ ] While waiting for someone to review your request, please help review another open pull request to support the maintainers

@sea-bass

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 45.44%. Comparing base (d962501) to head (9da70e4).
Report is 152 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3125      +/-   ##
==========================================
- Coverage   50.74%   45.44%   -5.30%
==========================================
  Files         392      482      +90
  Lines       32553    40431    +7878
==========================================
+ Hits        16517    18370    +1853
- Misses      16036    22061    +6025

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

I don't know what started causing these humble-ci failures, but it's not unique to this PR

Humble backport is in https://github.com/moveit/moveit2/pull/3127, and CI seems to be passing there.


Update to Node16

The node12 is not supported on macOS ARM64 platform. Use node16 instead.

Currently getting the above error on a macOS M1 runner, do we foresee any issues if we were to update this action to using node 16 instead? 👀

TIL : Github will decommission node12 from Runners by mid August

hey guys, apologies for the delay here. I've just bumped this action to run with node20. Let me know if you have any other issues!


Use Message Broker to Publish User Input to Multi Services

Amazon MQ – Managed Message Broker Service for ActiveMQ
https://aws.amazon.com/tw/blogs/aws/amazon-mq-managed-message-broker-service-for-activemq/
Services

[ ] Log
[ ] Database
[ ] Recombee

Done
color change from #DCDFE5  to #838FA8


Add char length check for Sos statements in XML output

Let's discuss how much effort this would be as we could improve the local government submission process to check character length upon submission so this would only be an issue for existing records.


Warning from StyledComponents when moving vertices too many times

When moving the vertices in the ShapePreview, a warning pops up.
To Reproduce
Steps to reproduce the behavior:

Click Add Shape button and open up the modal
Drag the vertices of the polygon many times until the warning pops up in the console

Expected behavior
No warning in the console
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I would like to take this up. Could you please assign it to me?


Add oldest versions of OCaml that support arm64, ppc64le and s390x

Speculative PR to produce oldest ARM64, ppc64le and s390x images.
https://github.com/avsm/ocaml-dockerfile/pull/94
https://github.com/ocurrent/ocaml-version/pull/47

Upstream PRs merged - @tmcgilchrist, would you be able to rebase this and update the submodules (I'm having trouble doing that locally for some reason)


feat: add brazilian portuguese language

Pull request from ptocular branch to Ocular's main branch to provide Portuguese (Brazil) as a language option.
Both Contributing Guidelines and "turkish" pull request have been followed to the extent of all guidance provided, except by test:ci routine which did not respond to move build as a PR. Please advise if additional steps are required.

@simonwep, I'm double-checking the pt-br.json file for any issues, but so far the CI / build routine yet throws an error from the ESLint rules, specifically at the file Draggable.vue which I'm still looking into.
The weird part is that GH suggests ln. 130 col. 7 as the culprit, but... it's just CSS styling. So, maybe reviewing the CI/CD pipeline or maybe skipping Vue's attr-orders altogether?

@simonwep, I'm double-checking the pt-br.json file for any issues, but so far the CI / build routine yet throws an error from the ESLint rules, specifically at the file Draggable.vue which I'm still looking into.
The weird part is that GH suggests ln. 130 col. 7 as the culprit, but... it's just CSS styling. So, maybe reviewing the CI/CD pipeline or maybe skipping Vue's attr-orders altogether?
Edit 1: Debug just shows that the issue is an invalid character \", which it's not present in Draggable.vue (since I did not edit it), but of course, is present in pt-br.json to escape double quotes. It should still work, but I'll try removing them if the next CI workflow does not work.
Edit 2: Just fixed a syntax error in pt-br.json where page > header had a missing comma. If this is the culprit, GH was pointing to the wrong file and line.

No worries :) I changed and force-pushed a few things, since I'm currently setting up contributing guidelines and tinkering what others need to successfully contribute:

There was a typo in your localization file, unknownError vs unkownError - yeah, the TS error message is pretty crappy.
Please use conventional commits, as already mentioned in the contributing guidelines.
I squashed all your commits since fixes usually don't need an extra commit.

In the coming days I'll merge this one, thank you so much for your contribution ❤

@simonwep, I'm double-checking the pt-br.json file for any issues, but so far the CI / build routine yet throws an error from the ESLint rules, specifically at the file Draggable.vue which I'm still looking into.
The weird part is that GH suggests ln. 130 col. 7 as the culprit, but... it's just CSS styling. So, maybe reviewing the CI/CD pipeline or maybe skipping Vue's attr-orders altogether?
Edit 1: Debug just shows that the issue is an invalid character \", which it's not present in Draggable.vue (since I did not edit it), but of course, is present in pt-br.json to escape double quotes. It should still work, but I'll try removing them if the next CI workflow does not work.
Edit 2: Just fixed a syntax error in pt-br.json where page > header had a missing comma. If this is the culprit, GH was pointing to the wrong file and line.

No worries :) I changed and force-pushed a few things, since I'm currently setting up contributing guidelines and tinkering what others need to successfully contribute:

There was a typo in your localization file, unknownError vs unkownError - yeah, the TS error message is pretty crappy.
Please use conventional commits, as already mentioned in the contributing guidelines.
I squashed all your commits since fixes usually don't need an extra commit.

In the coming days I'll merge this one, thank you so much for your contribution ❤

Immediately after the CI success notification from GH, I noticed the stupid br.json calling in locales where the file was actually named pt-br.json. 😅 Thank you for spotting that, and I'm glad to help! 🤩


[Issue/Bug]: DRG RPC not showing in discord (using windows 11 and default discord client, with demo project)

What happened?
the RPC doesnt show in discord either on linux nor windows 11
Version
1.3.1
Godot Version
4.2.1
Exact steps to reproduce this error

Launch demo project
Check activity on discord

GDScript
none

Godot output
No response
Additional information
No response
Checks

[X] I tried reinstalling the addon or tried to fix it myself with other methods.
[X] I tried restarting Discord and Godot completely.
[X] I did read the documentation https://vaporvee.com/docs/discord-rpc-godot/

so how exactly should you show an activity rpc when you don't even have written a single line of gdscript

the reason you should submit a ticket here is that i want to look at your code but its not that easy when you don't provide any

and if it still also doesn't work on the demo please check the activity privacy setting in your discord

and if it still also doesn't work on the demo please check the activity privacy setting in your discord

This fixed it, I didn't have one of the settings checked 😅

yeah i should probably add that to the faq lol


Update to 1.20

I will definitely update to 1.20 in weekends.
Thank you for using the mod :)

https://github.com/Toshimichi0915/Thymine/releases/tag/v1.8.3
The mod has been updated to 1.20.1 (1.20.0 is untested. I might work on that later).


fix(metrics): flush metrics when data points array reaches max size

Description of your changes

As reported in the linked issue prior to this PR the Metrics utility allowed to add a number of data points greater than the current 100 limit set by the EMF specification. This PR fixes the issue by ensuring that when a new data point is added and the limit is reached, all the stored metrics are flushed right away.
Related issues, RFCs

Issue number: fixes #1529
Checklist

[x] My changes meet the tenets criteria
[x] I have performed a self-review of my own code
[x] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my change is effective and works
[x] The PR title follows the conventional commit semantics

Breaking change checklist
Is it a breaking change?: NO

[ ] I have documented the migration process
[ ] I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Successful integration tests run: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/5350268096


Zoom does not hold

When I zoom in  using a box and then pick a class to doodle, it zooms back out. When I use the +/- icons to zoom, then pan, then pick the drawing tool, I get to draw one line, then it zooms back out. Any way to turn of automatic zooming?

Been trying to figure this one out. Will have another look at this issue today. I may end up enforcing no zoom, to make sure people use smaller imagery. Zooming in and out is really time consuming

zoom does work and takes some getting used to ... see this blog post https://dbuscombe-usgs.github.io/dash_doodler/blog/2021/07/08/Doodler-Zoom
closing for now


Updates on Image #2895

Adding new Graphics and sources on Issue #2895

Solving Issue #2895

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LanaChin PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@LanaChin Hi Lana, following up on this PR. Please let me know if there are any updates. Thanks

The text in the image is too hard to read.  Please submit an art request to re-create the image. Thank you.

Hi @LanaChin On the Onedrive are the sources of both .VS and .PDF
https://onedrive.live.com/redir?resid=5FC5BC3B89F7C2C0!382873&authkey=!AHlVOgkt8BmRl4M&e=bDSYTm

@j0rt3g4 , @scanum - please check with neonix on the art guidelines. The image needs to be re-created so that the text is clear and easy to read. Thanks.

@nenonix  The images and the VS are on the onedrive above. Would you please be son kind in checking it?

@nenonix Hi Nicole, could you help out on this? Thanks!!

hi @nenonix, @scanum - any updates on having this image redone?  Thank you

@scanum - assigned this back over to you. thank you.

@nenonix Please what would be the guidelines or how can I change it to align it?

@JohanFreelancer9 Hi Johan! Is this something that you maybe can help us with? Thanks!

@scanum Hi Manuella. I am sorry but I cannot be of much help when it comes to images and artwork.


fix warnings from IDEA

Coverage decreased (-0.008%) to 82.51% when pulling 21562c59dea558f829e0f6f36273881bc1e39e49 on Tantalor93:obe-minor into 5254493dec1d140284b95a3e719737b07891dc49 on martiner:master.

And the :trophy: Christmas Housekeeping Award goes to...


Allow timestamp of 0 to be included in selectedDates

The timestamp 0 refers to the date 1970-01-01, which is a valid date.
Exluding timestamps of 0 stops the onValueUpdate hook from firing on
init if the date is 1970-01-01.

:+1:


SAK-48362 ProfileWC Removed unused profile-popup code from library

https://sakaiproject.atlassian.net/browse/SAK-48362

I love PRs that delete old code!!!


add type to asset

issue #139 - specifically requests a required mime type to be added to assets.  This is what this PR does
issue #138 - Asks about a format field in the catalog.  I've removed this from the catalog as it doesn't make sense to repeat this information from the item assets

Still needs to update all the examples.
I'd also like to see a table of common mime-types, for recommendations on the types people will actually use.
But will merge and we can continue these on dev.


Padding arrays with NaNs

We want to be able to pad arrays with NaN values (/ zarr array fill_value) because some kerchunk use cases involve padding data (e.g. satellite swathes that produce slightly differently shaped data each day such as NASA SWOT).

We should probably be able to make the xarray .pad method work, at least with very specific arguments, e.g. ds.pad(x=1, mode='constant'). We would then intercept the arguments and re-interpret the padding operation for however the underlying manifest actually works.

satellite swathes that produce slightly differently shaped data

How will this work, since each chunk will require a different padding (presumably)? Are you going to add a new codec?
For example consider three arrays with shapes (1,1), (1,2), (1,3), stacked along axis=0.

I did use kerchunk for SWOT but I wasn't able to pad them so I only used the granules with the most common swath length. This was for a demo though and ideally there is some way to pad with nan's.

For example consider three arrays with shapes (1,1), (1,2), (1,3), stacked along axis=0.

To be concrete, if the chunksize for all these three arrays is (1,1), then empty(/nonexistent) chunks can be padded to each array in turn no problem such that the shapes match and the stacking becomes possible. I agree that if the chunksizes are actually (1,1), (1,2), (1,3) then it's a lot harder.

I agree that if the chunksizes are actually (1,1), (1,2), (1,3) then it's a lot harder.

IIRC this is a good model for the swath problem. I think the (only?) solution is a new codec since we need to transform the chunk itself.  Something like:
chunk: zarr.Array
out = np.full_like(new_shape, fill_value=chunk.fillvalue)
slicer = tuple(slice(size) for size in chunks.shape)
out[slicer] = np.array(chunk)

think the (only?) solution

I guess in this case even variable-length chunks wouldn't save us because this would actually require "ragged" chunks (i.e. no longer a rectilinear array of chunks)...

IIRC this is a good model for the swath problem. I think the (only?) solution is a new codec since we need to transform the chunk itself. Something like:

I don't really understand what that code snippet is meant to do but my understanding of your suggestion is to add a codec which records the new padded shape of the chunk, then so when the chunk is read if you're indexing into the unpadded part it indexes into the normal zarr array, but if you're indexing into the padded part it just returns the fillvalue. But isn't the problem with that idea that you would need only certain chunks to have that codec, but codecs are set on a per-array basis, not a per-chunk basis?

I guess in this case even variable-length chunks wouldn't save us because this would actually require "ragged" chunks

Yes exactly.

my understanding of your suggestion is to add a codec which records the new padded shape of the chunk

The "new padded shape" is just the regularized chunk shape, it should be inferred from the array metadata.

when the chunk is read if you're indexing into the unpadded part it indexes into the normal zarr array, but if you're indexing into the padded part it just returns the fillvalue.

At read time, all chunks are processed to a regular chunk shape so the rest of Zarr does not care about what it is actually indexing.


[Bug]: Got error said "icon file not found" although the icon is inside the bala file.

Description
We are trying to push our package into the Ballerina Central. However we keep getting the error said ballerina: failed to push the package: 'ip2locationio/ip2locationio:1.0.0' reason:icon file not found. When we inspected the bala file, the icon file is under the /docs/. Can we get help on this? We attached my package file with the bala file into the zipped file here.
ip2locationio.zip
Steps to Reproduce

Run bal pack.
Run bal push or bal push target\bala\ip2locationio-ip2locationio-any-1.0.0.bala.

Affected Version(s)
Ballerina 2201.9.0
OS, DB, other environment details and versions
Ballerina 2201.9.0 (Swan Lake Update 9)
Language specification 2024R1
Update Tool 1.4.2
OS: Windows 10.
Related area
-> Central
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

@ip2location I tried pushing the package and I couldn't reproduce the issue. I was able to publish the package successfully under my organization.

We were able to reproduce the issue in a Windows machine. The issue is with the icon path in package.json in .bala file.
The path is as below in windows.
"icon": "docs\\icon.png",

Where is should be
"icon": "docs/icon.png",

We will add a fix for this. As a workaround you can manually modify the package.json file in the .bala file and push it to Central.

Hi @anuruddhal,
Thanks for the tips, we had manually edit it in our Bala file and managed to push to the Central. Hope to see the fix.

When we do a bal pack on a package from a Windows machine, the icon path would be recorded in the Package.json file as "docs\icon.png" using the file separator specific for Windows.
But when we try to push this package to Central, validations to check the icon path fails as the OS is different from the Central side and the icon path recorded is no longer a proper file path.
We are looking into the best way to fix this and will provide a fix in a release soon to come.

https://github.com/ballerina-platform/ballerina-release/issues/2699

This issue has been fixed in #42843 and will be available in release 2201.9.1

https://github.com/ballerina-platform/ballerina-release/issues/2631


Smart-select doesn't update when form is loaded from JSON

Seems like method formFromJSON() currently works with normal form elements only. The method does update selected option from <select> but not the value inside

.

I believe a recent commit from @nolimits4web should have resolved this


transport: QueryInfo contents inaccessible

QueryInfo contains only unexported fields:
// QueryInfo represents data required for host selection policy to create query plan.
// Token and strategy are only necessary for token aware policies.
type QueryInfo struct {
	tokenAware bool
	token      Token
	topology   *topology
	strategy   strategy
	offset     uint64 // For round robin strategies.
}

This creates a problem that its impossible to create a custom HostSelectionPolicy outside of transport package that would make any use of QueryInfo

Also wouldn't QueryInfo benefit from holding keyspace (which has a strategy) instead of strategy?


Added link to extra icon requirement

Docs Build status updates of commit 60d9504:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:warning:Warning
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md

Line 39: [Warning] Invalid file link:(~/concepts/build-and-test/apps-package#icons).

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

Hi @EmilyyC. Can you fix the invalid file link on line 39 so that I can merge your changes?

Docs Build status updates of commit b246268:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded
View

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


added missing rights for setting up replication in system database

what about 3.3, 3.2 ?

PRs here:

3.3: https://github.com/arangodb/arangodb/pull/4513
3.2: https://github.com/arangodb/arangodb/pull/4512
Sorry for the confusion. Took me half a day to create the PRs for three branches


Fix gapcursor style path

This corrects the path to the CSS file (style/gapcursor.css) in the documentation.

Thanks!


Website is broken

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
https://facebook.github.io/jest/ displays
Error: Error: Requiring unknown module "./i18n/af.js". It may not be loaded yet. Did you forget to run arc build? at /home/ubuntu/jest/website/node_modules/react-page-middleware/src/guard.js:27:12 at onOutputGenerated (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/index.js:96:9) at Object.done (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/DefaultRouter.js:345:7) at renderReactPage (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/renderReactPage.js:130:17) at renderComponentPackage (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/DefaultRouter.js:331:3) at routePackageHandler (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/DefaultRouter.js:274:5) at onComputePackage (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/index.js:100:9) at /home/ubuntu/jest/website/node_modules/react-page-middleware/src/guard.js:29:10 at onWarmed (/home/ubuntu/jest/website/node_modules/react-page-middleware/src/Packager.js:270:9) at /home/ubuntu/jest/website/node_modules/async/lib/async.js:116:25

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
Open https://facebook.github.io/jest/
What is the expected behavior?
https://facebook.github.io/jest/ should display the jest documentation.

Working to resolve this right now.

PR is here: https://github.com/facebook/jest/pull/3395

This still didn't solve the issue so I am reverting.

lol maybe need use some tests?

@zoxon HAHA.  I wonder if @facebook-github-bot thinks its funny.  2017 is the year of humor in AI. If it wasn't FB I would think thats in bad taste.  Too funny.


Fixed #31608 -- Added releaes note to declare forms.DateTimeField retain timezone information of input datetime.

Added release note for ticket 31608

Thanks! What about also adding a note in the USE_TZ setting documentation?

Thanks! What about also adding a note in the USE_TZ setting documentation?

@claudep Thanks! Note added!

Great, let's see what @carltongibson thinks about that.


Show a strange activity log after deleting multi files at one time from one file share in zh-CN

Storage Explorer Version: 1.11.0
Build: 20191127.2
Branch: master
Language: Chinese(zh-CN)
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Open 'Settings' -> Application (Regional Settings) -> Select 'Chinese (simplified)' -> Restart Storage Explorer.
Expand File Shares -> Create one file share -> Upload 2 files.
Select the 2 files and delete them.
Observe the activity log.

Expect Experience:
Show a right activity log.
Like: Delete 1 file

Actual Experience:
Show a strange activity log.

More Info:
In zh-TW:

@v-xianya Is it possible to provide ENU screenshot ?

This is caused by the swapped order of the two languages. We should be specifying the order of the placeholders.

@lukaschal   ENU screenshot

File: loc\en\src\Standalone\resources\Activities.json
ID: 0; "MessageFileDeletedMultiple"
SRC: Deleted %s files/directories from '%s'
TGT: 已从 "%s" 中删除 %s 个文件/目录

"Deleted %s files/directories from '%s'": The first placeholder should be a number, and the second placeholder should be a path.

String changes have been merged. Ready for translation/verification.

Verified on build 20200216.2. This issue has been fixed. So we close it.


Features

Does this library support search and copy text from PDF?

Hi @pavelpoley, No it does not as this library renders pdf pages as images to maintain library size.


docs: remove error url in concepts.md

不知道这链接地址是删除了还是修改了？

Checklist

[ ] npm test passes
[ ] tests are included
[x] documentation is changed or added
[ ] commit message follows commit guidelines

Description of change

any feature?
close https://github.com/dvajs/dva/ISSUE_URL

Coverage remained the same at 86.493% when pulling e1566bb2563d6266a688f759d2f61e186678d183 on xhwgood:patch-1 into a5e4ca58b8d40685545cc5bff6a92736afc94d24 on dvajs:master.


Issue with SWF file for downloading Data to Excell,pdf

Hello Mr.@mcintyre321 ,
hope you are doing well,
as you know that Adobe is not supporting flash player any more and we used mvc.jquery.datatables library
and you have used CDN for SWF file
options["oTableTools"] = new JRaw("{ 'sSwfPath': '//cdn.datatables.net/tabletools/2.2.1/swf/copy_csv_xls_pdf.swf' }");
and after December when Adobe Leave Support of Flash palyer, button are not working
how we can customize it to HTML5 button, or do you have any other Idea to solved the issue.
WB Regards,
Olfath

From looking at the TableTools plugin page (
https://datatables.net/extensions/tabletools/) it seems that it has been
'retired', in favour of Buttons (https://datatables.net/extensions/buttons/
).
I'm not really maintaining this plugin at the moment, as I'm not working on
any projects that use it, but if you submit a PR which uses the Buttons
plugin, and removes TableTools, I will happily merge it.
Here is all the code I wrote to integrate TableTools:
https://github.com/mcintyre321/mvc.jquery.datatables/search?q=tabletools
Similar code is required to use Select
On Mon, 18 Jan 2021 at 07:35, Javed Ahmad Olfath<EMAIL_ADDRESS>wrote:

Hello Mr.@mcintyre321 https://github.com/mcintyre321 ,
hope you are doing well,
as you know that Adobe is not supporting flash player any more and we used
mvc.jquery.datatables library
and you have used CDN for SWF file options["oTableTools"] = new JRaw("{
'sSwfPath': '//
cdn.datatables.net/tabletools/2.2.1/swf/copy_csv_xls_pdf.swf' }");
and after December when Adobe Leave Support of Flash palyer, button are
not working
how we can customize it to HTML5 button, or do you have any other Idea to
solved the issue.
WB Regards,
Olfath
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mcintyre321/mvc.jquery.datatables/issues/185, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDJ6RYL4537R22JGBBO43S2PQDVANCNFSM4WG324VQ
.

From looking at the TableTools plugin page (
https://datatables.net/extensions/tabletools/) it seems that it has been
'retired', in favour of Buttons (https://datatables.net/extensions/buttons/
).
I'm not really maintaining this plugin at the moment, as I'm not working on
any projects that use it, but if you submit a PR which uses the Buttons
plugin, and removes TableTools, I will happily merge it.
Here is all the code I wrote to integrate TableTools:
https://github.com/mcintyre321/mvc.jquery.datatables/search?q=tabletools
Similar code is required to use Select
On Mon, 18 Jan 2021 at 07:35, Javed Ahmad Olfath<EMAIL_ADDRESS>wrote:

Hello Mr.@mcintyre321 https://github.com/mcintyre321 ,
hope you are doing well,
as you know that Adobe is not supporting flash player any more and we used
mvc.jquery.datatables library
and you have used CDN for SWF file options["oTableTools"] = new JRaw("{
'sSwfPath': '//
cdn.datatables.net/tabletools/2.2.1/swf/copy_csv_xls_pdf.swf' }");
and after December when Adobe Leave Support of Flash palyer, button are
not working
how we can customize it to HTML5 button, or do you have any other Idea to
solved the issue.
WB Regards,
Olfath
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mcintyre321/mvc.jquery.datatables/issues/185, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDJ6RYL4537R22JGBBO43S2PQDVANCNFSM4WG324VQ
.

Hi Olfath @JaAfghan
Did you do something with this? We will also start migrating this; just fighting with GitHub as it's our first GitHub project and contribution to opensource.


StreamAssist Making Multiple Connections

I have an android device connected to StreamAssist using the IP WebCam app which is running in Audio Only mode. StreamAssist the only thing connected to it, but somehow StreamAssist keeps making multiple connections (20 is what i usually see) to IP Webcam resulting in the application restarting and everything going haywire. I dont know for certain if its StreamAssist not gracefully closing the previous connections, or IP Webcam doing something weird, but i think since StreamAssist is making the connection i figure i'd start here first. Has anyone else seen this and if so, @AlexxIT would you have any idea why this is happening or if there is something that can be modified in StreamAssist?

I do have an automation that keeps the microphone on and im curious if when thats ran, it makes a new connection to ipwebcam even though the previous connection is still established or something?

Same here, but I thought it was because of (combination of) IP Webcam and Fire OS (Fire HD10+)

Coincidentally i am also seeing this on the hd10+. lol. I am testing out tinycam pro on that device currently. StreamAssist is working with it so far, but there is a bit more config that i needed to do. If you want to test that apk out, you can get the audio stream from: http://[ip]:8083/axis-cgi/audio/receive.wav?user=[username]&pwd=[pwd] You are also required to configure the webserver but thats pretty straight forward.  Tinycam looks to lose access to the microphone as well.

@tbrasser So i de-unbloated the tablet in order to register it so i could create a new kids profile on it to test out their workaround but the problem is, im running WallPanel which i downloaded from google play and it doesnt show up in the apps section of the child profile settings as an app i can approve. Lol. FK also doesnt show up there. Bummer


Properly handle reviewing ahead

https://docs.ankiweb.net/filtered-decks.html#reviewing-ahead

Anki algorithm (source):
def _earlyReviewIvl(self, card: Card, ease: int) -> int:
        assert card.odid and card.type == CARD_TYPE_REV
        assert card.factor
        assert ease > 1

        elapsed = card.ivl - (card.odue - self.today)
#// elapsed: number of days that have passed since you reviewed the card
#// card.ivl: card's given interval
#// card.odue: card's original due date
#// self.today: today date

        conf = self._revConf(card)

        easyBonus = 1
        # early 3/4 reviews shouldn't decrease previous interval
        minNewIvl = 1

        if ease == BUTTON_TWO:  #// if you press hard
            factor = conf.get("hardFactor", 1.2)
#// hardFactor: should
            # hard cards shouldn't have their interval decreased by more than 50%
            # of the normal factor
            minNewIvl = factor / 2
        elif ease == BUTTON_THREE:  #// if you press good
            factor = card.factor / 1000
        else:  # ease == BUTTON_FOUR:  #// if you press easy
            factor = card.factor / 1000
            ease4 = conf["ease4"]
#// ease4: should be the ease bonus (review tab in deck options) not sure tho
            # 1.3 -> 1.15
            easyBonus = ease4 - (ease4 - 1) / 2

        ivl_1 = max(elapsed * factor, 1)
#// card.factor: if ease = 250%, card.factor = 2500
#// factor: if ease = 250%, factor = 2.5

        # cap interval decreases
        ivl_2 = max(card.ivl * minNewIvl, ivl_1) * easyBonus

        ivl_3 = self._constrainedIvl(ivl_2, conf, prev=0, fuzz=False)
#// self._constrainedIvl -> applies fuzz,checks for maximum interval cap,
#// checks for previous interval and does one more thing that i honestly don't understand :/
#// for review ahead, fuzz is false (no fuzz applies)
#// previous interval = 0, maximum is always the interval that this function gives it
#// so i'll just assume that it has no effect on the interval and just use this function in my example (:|)

        return ivl_3
#// returns new interval for the card

if you press hard:
card.ivl = 20 (days)
elapsed = 9 (days)

easyBonus = 1
minNewIvl = 0.55 (factor = conf.get("hardFactor", 1.2 | then minNewIvl = factor / 2) (my hard factor is 110% -> anki stores it as 1.10 => 1.10/2 = 0.55)
factor = 1.1

ivl_1 = 10
ivl_2 = 11
final interval on hard button = 11 (days)

if you press good:
elapsed = 9 (days)

easyBonus = 1
minNewIvl = 1
factor = 2.5

ivl_1 = 22.5
ivl_2 = 22.5
final interval on good button = 22 (days)

if you press easy:
card.ivl = 20 (days)
elapsed = 9 (days)

easyBonus = 1.15 (check out #NOTE)
minNewIvl = 1
factor = 2.5

ivl_1 = 22.5
ivl_2 = 25.8
final interval on easy button = 26 (days)

#NOTE -> how easyBonus was calculated:
ease4 = conf[“ease4”] -> this is the easy bonus that you set on deck options -> review tab | if it’s 130%, anki stores it as 1.3

easyBonus = ease4 - (ease4 - 1) / 2

so if ease4 = 1.3 -> easyBonus = 1.3 - (0.3)/2 => 1.3 - 0.15 = 1.15


Sentinel update rc

Prevent exec of update-rc.d at each puppet run

It wasn't a real issue but the exec was run at each puppet run and then appeared as a change on puppetboard...

+1 Was just about to PR this one myself.  Pretty please merge this.

Merged.
Thanks!


python3Packages.class-registry: 2.1.2 -> 3.0.5

Motivation for this change
Update to latest upstream release 3.0.5
Change log: https://github.com/todofixthis/class-registry/releases/tag/3.0.5

Enable tests
Cleanup

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 133343 run on x86_64-linux 1

1 package failed to build:

backblaze-b2

2 packages built:

python38Packages.class-registry
python39Packages.class-registry

Result of nixpkgs-review pr 133343 at 503009b6 run on x86_64-linux 1

1 package failed to build:

backblaze-b2

2 packages built successfully:

python38Packages.class-registry
python39Packages.class-registry

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

backblaze-b2 fails with:
              >   phx-class-registry 3.0.5 (/nix/store/100fngyf29gkfpn8r7g7jhldx1aa82rq-python3.9-class-registry-3.0.5/lib/python3.9/site-packages)
              >   phx-class-registry 3.0.5 (/nix/store/cbn8saxr2zmca801dbzxlqllcw11rn3k-python3.9-phx-class-registry-3.0.5/lib/python3.9/site-packages)


Make BrowserSync webpack plugin customizable

Status
READY
Description
A developer should be able to customize BrowserSync configurations. Right now the plugin is added in the base extension, but it should be on its own extension.
See #19
Impacted Areas in Application

base config
plugins

Codecov Report

Merging #23 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #23   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      5    +1
  Lines           9     10    +1
=====================================
+ Hits            9     10    +1

Impacted Files
Coverage Δ

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

src/browserSync.js
100% <100%> (ø)

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 a3d2e75...71ace5f. Read the comment docs.


Recognize .mjs as JavaScript files

This is a quick and dirty fix for https://github.com/Polymer/tools/issues/736.

What's blocking this? @bicknellr @justinfagnani @rictic @aomarks @usergenic


UWP In VS2022 Release Mode dont work

When i start the UWP project in releasemode it throws a "Platform is not supported"
in Debug mode it starts with no Problem.

.net or c++?
May I ask you to try manually set target CPU architecture to x64?

@TheGrumpyT I was able to reproduce the issue.

Yes, i set it to x64. ( was that a mistake? )
I use always x64 for UWP. (for Testing on my XBOX ONE)
On Any CPU it throws this error
The BaseOutputPath/OutputPath property is not set for project 'RbfxTemplate.UWP.csproj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='Debug'  Platform='AnyCPU'.  This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform.

@TheGrumpyT by the way how did you discover the template?

I have searched with google for an Urho3d template that I can also use with C# and then landed here.
I am looking for a small and fast 3d engine that I can also use on my XBOX.
And this template looks very interesting.

Thank you!
I've fixed the issue you mentioned, you'll need to update Urho3DNet package when it's ready. But there is one more problem down the line with custom component creation. I'll update the issue when I fix it too.

Thank you!

@TheGrumpyT  It seems I made it work except some .NET Native tool breaks rbfx'es .net glue code. Do you know if it's possible to publish a game to store that isn't compiled with native tool chain?

I think a release in the store requires a native compilation.

@TheGrumpyT ugh... Then I have to fix the issue.
The problem is that
extern Urho3D_CSharpCreateObjectCallback Urho3D_CSharpCreateObject;
callback gets screwed if NativeAOT compilation is enabled. I'll try a different way of passing the callback to native code, hopefully it will work.
Also this issue corelates to a bigger problem we have with AOT compilation for Web. If we tackle that one we'll have web as one of the targets for .net. Just thinking out loud.

@TheGrumpyT I'm sorry it took me so long. The problem is fixed now. I re-enabled native tools for the UWP Release.


clean-up: delete unnecessary 'before' in Utilization specs

Minor clean-up extracted from #96.
The other before blocks already set up everything needed without regards of previous contents.

Looks good, but would benefit from explaining why it is not needed (ie. other before blocks already set up everything needed without regards of previous contents).

Yes, it's in the commit description.

IFTFY in the PR description.

bors r+

bors retry


TODO Feature: add pino for logger

Feature :
This feature needs to be added to the project.
Helplful resources :
https://github.com/iamolegga/nestjs-pino
Need to be completed

[x] Implementing the feature
[x] Completion of the task

Done


Incorrect light value at tall grass block after placing a block above it

The tall grass block appears to be fully lit when it shouldn't be:

See https://bugs.mojang.com/browse/MC-2399


update clease app 🏊

Based on what Jack said, it does seem like a problem with accessing the ASE database a number of times. For some reason, this wasn't happening before I implemented error handlers, so I wondered if it might have something to do with implementing the error handlers. I'm testing the workflow now with only 2 error handlers (rather than all of them) and it's no longer having the issue. This might indicate that each error handler is accessing the database separately, causing it to lock up. I don't need to use all the error handlers, so I'm going to test only the ones I need.

The error handlers never interact with the ASE database, so I don't think this is the issue. Are you using the directory input parameter when you run your workflow? My guess is that you locking up your ASE database somehow, and then a new workflow run is trying to reuse the broken ASE database. You need to either delete the old corrupted ASE file or start from a clean directory every time
This line sets the database so that it's written inside your simmate directory:
https://github.com/laurenmm/simmate-1/blob/ddb32b02c93730c79cbce90a5b63b4f2a660fa61/src/simmate/apps/clease/workflows/cluster_expansion.py#L84

@laurenmm any luck figuring out what was happening?

I have not. I think I accidentally closed this yesterday when I was cleaning off my in-lab desktop, but the scripts are still on Warwulf. I was doing some testing with and without error handlers before I left for Greece, and I haven't gotten anything to work with error handlers. Thursday is my last day in lab so I likely won't be able to figure out this issue before I leave; I will get @SWeav02 up to speed and we'll see what he can do.

lol no worries. And congrats on your last day! Enjoy Greece 🥳🥳🥳