Automatically label resources

Issue: https://github.ibm.com/IBMPrivateCloud/roadmap/issues/62014
Automate the resources labelling for Backup and Restore, following the document: https://www.ibm.com/docs/en/cloud-paks/foundational-services/4.6?topic=fsbr-cloud-pak-foundational-services-backup-restore-multiple-instances-foundational-services#add-labels-to-resources
Resources include:

CatalogSource (default and private)
Namespaces and OperatorGroups
global pull secret and ibm-entitlement-key
ConfigMaps
Subscriptions
OperandRequests
OperandConfig
CommonService CR and CRD

Instruction to run the script:

Manually type in the required variables in the local.properties and save it.
Note: operator and services namespaces are a must to pass in, other variable has default values, and optionally to change them
run to script: ./label-common-service.sh

I am about to run a test using just this script to labels resources and see how it goes. Before then, the only other comment I have is maybe to make it more flexible with the services namespace. It's possible a user does not use SOD topology and therefore would not need to enter in a value for the services namespace but the script fails without this value.

Something about the operandrequest logic is not working as intended. I tried to run the restore but it got hung up on waiting for resources after restoring operandrequests. I checked the backup cluster and don't see the labels on any operandrequests so I re-ran the script and got this output (not labeled means the label already existed with the same value):
<EMAIL_ADDRESS>common-service]# ./label-common-service.sh
# Start to validate the parameters passed into script...
[✔] oc command logged in as system:admin
# Start to label the catalog sources...
catalogsource.operators.coreos.com/opencloud-operators-cd not labeled
catalogsource.operators.coreos.com/ibm-operator-catalog-latest not labeled
catalogsource.operators.coreos.com/cloud-native-postgresql-catalog not labeled
catalogsource.operators.coreos.com/ibm-cert-manager-catalog not labeled
catalogsource.operators.coreos.com/ibm-licensing-catalog not labeled
catalogsource.operators.coreos.com/ibm-operator-catalog-latest not labeled
catalogsource.operators.coreos.com/opencloud-operators-cd not labeled
# Start to label the namespaces, operatorgroups and secrets...
namespace/cs not labeled
operatorgroup.operators.coreos.com/cs-ptjvd not labeled
operatorgroup.operators.coreos.com/cs-ptjvd not labeled
namespace/ibm-cert-manager not labeled
operatorgroup.operators.coreos.com/ibm-cert-manager-p627s not labeled
namespace/ibm-licensing not labeled
operatorgroup.operators.coreos.com/ibm-licensing-vnhhc not labeled
secret/ibm-entitlement-key not labeled
secret/pull-secret not labeled
# Start to label the ConfigMaps...
configmap/common-service-maps not labeled
configmap/platform-auth-idp not labeled
# Start to label the Subscriptions...
subscription.operators.coreos.com/ibm-common-service-operator not labeled
subscription.operators.coreos.com/ibm-cert-manager-operator labeled
subscription.operators.coreos.com/ibm-licensing-operator-app labeled
# Start to label the CommonService CR...
commonservice.operator.ibm.com/common-service not labeled
customresourcedefinition.apiextensions.k8s.io/commonservices.operator.ibm.com not labeled
operandconfig.operator.ibm.com/common-service not labeled

And I do not see operandrequests at all.

Hi @bluzarraga I have updated script as per your comments above

Set the services namespace as non-required. If the topology is not SOD, it will be automatically assigned as operator namespace
Add a success message at the end of the script.
Update singleton-subscription label updated for singleton services
Fix the issue of OperandRequests not being labeled
Add zen services label command

Thanks

/lgtm

looks great @YCShen1010 thank you!


[Proposal] Improve DisplayData support in PTransform API

This PR proposes a new PTransform API, setDisplayData, for adding DisplayData items to the transform.
Motivation: Adding DisplayData is easy to do via the HasDisplayData#populateDisplayData method that most transform-like types inherit. However, as a user and library owner, I don't always have access to the construction of the PTransform or DoFn and can't override populateDisplayData. For example, it would be difficult to add custom displayData labels to any of these transforms unless I wrapped them into new PTransforms:
    pipeline
        .apply(Create.of(1, 2, 3))
        .apply("Map Elements", MapElements.via(...))
        .apply("GBK", GroupByKey.create())

This PR adds a method setDisplayData that can be invoked on any PTransform instance.
Note: I followed the convention of other setter methods in the PTransform class, i.e. setResourceHints, but it might be more intuitive to make it a withDisplayData method that returns the PTransform instance, so that users can use it like pipeline.apply(Create.of(1, 2, 3).withDisplayData(...)) ?
Let me know what you think! :)

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

assign set of reviewers

Checks are failing. Will not request review until checks are succeeding

It looks like skipped checks (i.e. Java Wordcount Dataflow) are getting registered as "failing"  🤔


License type- Ubuntu to Ubuntu Pro values added

License type- Ubuntu to Ubuntu Pro values added
Related command
az vm update -g myResourceGroup -n myVmName --license-type UBUNTU_PRO
az vm update -g myResourceGroup -n myVmName --license-type UBUNTU
Description
This will allow Ubuntu images to change billing model to Ubuntu Pro
Testing Guide
az vm update -g myResourceGroup -n myVmName --license-type UBUNTU_PRO
az vm update -g myResourceGroup -n myVmName --license-type UBUNTU

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

[Y ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ Y] I adhere to the Command Guidelines.

[ Y] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.


Add files via upload

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 1
Score: 0%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 0
Score: 0%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 1
Score: 0%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 1
Score: 0%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 1
Score: 0%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 105
Score: 97.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 106
Score: 98.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 107
Score: 99.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 107
Score: 99.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 107
Score: 99.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 11
Score: 91.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 107
Score: 99.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 12
Score: 100.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 108
Score: 100.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 12
Score: 100.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 108
Score: 100.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 12
Score: 100.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 108
Score: 100.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 12
Score: 100.00%

Good Job!!!   @Minderheiten
Python homework:

Total questions: 108
Correct answers: 108
Score: 100.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 12
Score: 100.00%

leetcode扩展作业
LeetCode_homework.md

leetcode编程扩展作业 :D
LeetCode_homework.md
@iphysresearch


There is a large grey area at the bottom of the screen

Steps to reproduce:
View the browse boats page with all boats shown
Expected behaviour: site common footer is shown immediately below the boat register bottom navigation
Actual behaviour: there is a large grey area.

fixed by eliminating iframe

fixed by eliminating iframe


Link to the latest gem.  https://github.com/kitsched/japr

Hey, can you link to the current asset pipeline gem https://github.com/kitsched/japr repo instead of leaving this to confuse everyone?  This gem only works with Jekyll 0.12.1.  Wasted a few hours of my life.

:+1:, I also wasted time on this.

FYI, I just updated my fork to be compatible with Jekyll 3.5.

JAPR has been merged back here.


Update README.md

Removed unnecessary white-space. Fixed spelling, punctuation, and grammar errors.

Thank you @HaroldPetersInskipp
will get it merged shortly.


Fix survey timings

This branch implements relative and absolute delivery timings.
I also implemented static typing and brought code more in line with PEP 8.

Thanks for the PR! We haven't discussed this before but it'd be great if you could push these changes directly to a feature branch in the Forest repo (i.e., onnela-lab/fix_survey_timings) and then use that branch to open a PR. It would make working on this a bit easier.

That's done. Closing this request.

Thank you!


fix sklearn dependency in mape, mase and smape

This fixes sklearn dependency in #330 (same fix as #345).
cc @kashif

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Syslog spam about unchanged Router Advertisement in 8.1.2 as used by Raspberry Pi (rpi)

Current version of dhcpcd5 package installed: 8.1.2-1+rpt8
As you can see, the router advertisement has not changed but it keeps being logged at info severity.
2022-10-17T10:38:18.649029+01:00 unseen info dhcpcd[9164]: eth0: Router Advertisement from fe80::3223:3ff:feae:9cc0
2022-10-17T10:39:40.247326+01:00 unseen info dhcpcd[9164]: eth0: Router Advertisement from fe80::3223:3ff:feae:9cc0
2022-10-17T10:41:43.105189+01:00 unseen info dhcpcd[9164]: eth0: Router Advertisement from fe80::3223:3ff:feae:9cc0
2022-10-17T10:43:29.352860+01:00 unseen info dhcpcd[9164]: eth0: Router Advertisement from fe80::3223:3ff:feae:9cc0

The code to log the message is here:
https://github.com/NetworkConfiguration/dhcpcd/blob/9095f26ae1f2879231fdb25cd1c5822ae0c4947b/src/ipv6nd.c#L1103
The desire not to log too much seems to be captured in the comment slightly above:
https://github.com/NetworkConfiguration/dhcpcd/blob/9095f26ae1f2879231fdb25cd1c5822ae0c4947b/src/ipv6nd.c#L1058
To be clear, the issue is the repeated logging of seemingly unchanged Router Advertisement and I think it would be better if there was no logging unless the advert received is from a new source.

FWIW: you've raised a reasonable question I think, and I would suggest that you submit a pull request against version 8.
However:  if you want to get the code that you actually use in 8.1.2 on your RPi changed, you will need to do that through the archive.raspberrypi.org repo.
This is the upstream repo for dhcpcd, and it is currently at version 9+. I know this because I made this mistake recently :). Roy accepted my pull request, but of course only the RPi organization can determine what goes in their repo; and they are stuck on version 8 for reasons only they can explain.


How to handle access_denied: AADB2C90091: The user has cancelled entering self-asserted information.

If we initiate a password reset from the application and at the b2c reset page user clicks on cancel and subsequently gets redirected to the app, at that point, it seems to be user is not authenticated anymore. "<EMAIL_ADDRESS>: Error - Guard - error while logging in, unable to activate". None of the routes works, nor API calls.
this error is also logged.

I was able to handle it like this. Not sure if it's correct.

this.msalBroadcastService.msalSubject$
      .pipe(
        takeUntil(this._destroying$)
      )
      .subscribe((result: EventMessage) => {
        if (result.eventType === EventType.ACQUIRE_TOKEN_FAILURE && result.error.message &&
          result.error.message.includes("access_denied")) {
          this.logger.debug("access_denied ask to login");
          let signUpSignInFlowRequest = this.getLoginRequest();
          this.login(signUpSignInFlowRequest);
        }
        if (result.eventType === EventType.LOGIN_SUCCESS) {
          const payload = result.payload as AuthenticationResult;
          this.logger.debug("msalSubject$", payload);
          let idtoken = payload.idTokenClaims as IdTokenClaimsWithPolicyId;

          if (idtoken.acr === b2cPolicies.names.signUpSignIn || idtoken.tfp === b2cPolicies.names.signUpSignIn) {
            this.authService.instance.setActiveAccount(payload.account);
          }

          if (idtoken.acr === b2cPolicies.names.resetPassword || idtoken.tfp === b2cPolicies.names.resetPassword) {
            let signUpSignInFlowRequest = this.getLoginRequest();
            this.login(signUpSignInFlowRequest);
          }
        }
      });

Hi @patolax, thanks for raising this. I managed to reproduce the issue. There's no issue with the way that you're handling the error in the code that you shared, but we will need further debugging to figure out what is causing this behavior.


Make the kragen-flask-server image launch via docker-compose (instead of docker run)

Fixed by commit 8389159a641eec85a2313b1c8c19b3df8d8c89d9


Deprecation warning wrt Gradle 9

Build output:
The org.gradle.util.ConfigureUtil type has been deprecated. This is scheduled to be removed in Gradle 9.0. Consult the upgrading guide for further information: https://docs.gradle.org/8.1.1/userguide/upgrading_version_7.html#org_gradle_util_reports_deprecations         at build_2my6sz9nofhu09ycuu5xrzoww$_run_closure2$_closure19$_closure26.doCall(/Users/raimundklein/development/GitHub/spring-boot-mvc-hexagonal-template/service/build.gradle:114)         (Run with --stacktrace to get the full stack trace of this deprecation warning.)         at build_2my6sz9nofhu09ycuu5xrzoww$_run_closure2$_closure19.doCall(/Users/raimundklein/development/GitHub/spring-boot-mvc-hexagonal-template/service/build.gradle:113)         (Run with --stacktrace to get the full stack trace of this deprecation warning.)
Referenced section in the build file:
spotbugsMain {
    reports {
        html {
            required = true
        }
    }
}

Duplicate of #616


Unity Web Request and Json Utility

Unity is adding support for REST and JSON and it would be better to adopt the built-in methods therefore removing the need for external dependencies or plugins.

http://docs.unity3d.com/Manual/UnityWebRequest.html
http://docs.unity3d.com/ScriptReference/JsonUtility.FromJson.html

UnityWebRequest is marked experimental status - waiting for release before implementing this.

UnityWebRequest is now out of experimental status in current version of Unity (5.4), but reports that there are problems using the HTTP PATCH method on Android.

First going to using try custom override header: "X-HTTP-Method-Override": "PATCH", otherwise things might get tricky...

Related Articles:
http://stackoverflow.com/questions/19797842/patch-request-android-volley
http://answers.unity3d.com/questions/1230067/trying-to-use-patch-on-a-unitywebrequest-on-androi.html

Switching over to UnityWebRequest & JsonUtility will bring in a number of changes to the library...
But I ran into a couple of issues / gotyas with Unity's JsonUtility -

JsonUtility can't parse a top level json array atm. The easiest workaround is to add property with the array as value see http://forum.unity3d.com/threads/how-to-load-an-array-with-jsonutility.375735/
Be careful with using properties with shorthand {get; set;}with JsonUtility - I had to remove this from my data model for parsing to work correctly, otherwise I got back empty objects without any parse error info.

One the plus side it supports the class attribute [Serializable] and property attributes [SerializeField], [NonSerialized]

https://docs.unity3d.com/Manual/JSONSerialization.html

Another thing I would like with UnityWebRequest is to not have to wrap everything with StartCoroutine(), but atm this still seems like the cleanest way of starting an async request - I'm open to other suggestions...

Status update: This is working on Mac/Window Unity Editor, iOS and Android. But I appear to be hitting JsonUtililty deserialization issues when running as a W10 universal app. Holding this release as a feature branch until this issue is resolved. I've tried to keep external interfaces as similar as possible, so it should not be too much hassle to update. The main changes will involved:

wrapping async callbacks with StartCoroutine()
changed from <List> to T[]

The Unity JsonUtility parse error on Windows Store App happens when you try to parse an array of objects... But I've found a couple of work-around solutions when running on UWP:

Opt for using Newtonsoft.Json; WSA plugin within UNITY_WSA directive.
https://github.com/SaladLab/Json.Net.Unity3D/blob/master/docs/UwpWorkaround.md
https://github.com/SaladLab/Json.Net.Unity3D/releases/download/8.0.3/JsonNet-UwpWorkaround.8.0.3.zip

#if UNITY_WSA
  using Newtonsoft.Json;
#endif

#if UNITY_WSA
  T[] array = JsonConvert.DeserializeObject<T[]>(json);
  return array;
#endif

Opt for using Windows.Data.Json; WinRT API within NETFX_CORE directive.
https://docs.unity3d.com/Manual/windowsstore-scripts.html

#if NETFX_CORE
  using Windows.Data.Json;
  using System.Collections.Generic;
  using System.Linq;
#endif

#if NETFX_CORE
  JsonArray array = new JsonArray();
  if (JsonArray.TryParse(json, out array)) {
    List<T> list = new List<T>();
    foreach(var x in array) {
      T item = JsonUtility.FromJson<T>(x.ToString());
      list.Add(item);
    }
    return list.ToArray();
  }
  return default(T[]);
#endif


vxlan id leak

Short description
Sometimes after network deletion vxlan id isn't released back.
Description
Our system uses overlay networks in swarm cluster. Workflow procedure:

create an overlay network
add some containers into it
do some operations with that containers
remove containers
and finally remove network

It is normally, that such iteration are performed in parallel.
After some time our system running, we found leak of vxlanid. When all ids is consumed, our system failed to create new network (Swarm response: failed to allocate vxlan id : no bit available) and becomes useless. At the end, we have no overlay networks (According to output of docker network ls), and we cannot use new one even through cli:
# docker -H localhost:23750 network create -d overlay ssss3
2fc7f3e7346092a150592fe246eb84fcfd3e4e9508de41618a34c50acb033498
# docker -H localhost:23750 run -ti --network=ssss3 busybox sh
docker: Error response from daemon: Error response from daemon: couldn't get vxlan id for "<IP_ADDRESS>/24": failed to allocate vxlan id: no bit available.
# docker -H localhost:23750 network inspect ssss3
[
    {
        "Name": "ssss3",
        "Id": "2fc7f3e7346092a150592fe246eb84fcfd3e4e9508de41618a34c50acb033498",
        "Scope": "global",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/24",
                    "Gateway": "<IP_ADDRESS>/24"
                }
            ]
        },
        "Internal": false,
        "Containers": {},
        "Options": {},
        "Labels": {}
    }
]

Environment
AWS EC2 Centos 7.3
Master: c4.2xlarge
3 Nodes: r3.xlarge
Swarm 1.2.5
Zookeeper  3.4.9
Output of # docker info
Containers: 8
 Running: 4
 Paused: 0
 Stopped: 4
Images: 39
Server Version: 1.12.5
Storage Driver: devicemapper
 Pool Name: docker-202:0-1708215-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/vg-docker/data
 Metadata file: /dev/vg-docker/metadata
 Data Space Used: 29.52 GB
 Data Space Total: 69.79 GB
 Data Space Available: 40.27 GB
 Metadata Space Used: 40.24 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.107 GB
 Thin Pool Minimum Free Space: 6.979 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null overlay bridge host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.36.3.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 29.55 GiB
Name: node2.c5.codenvy-stg.com
ID: EMDA:WZ57:VTC2:KNIC:TDWE:I5AO:L2B2:MNS5:C3W7:KSWE:M4L2:ZIFH
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Labels:
Cluster Store: zk://ec2-52-91-105-228.compute-1.amazonaws.com:2181
Cluster Advertise: <IP_ADDRESS>:2375
Insecure Registries:
 codenvy-stg.com:5000
 <IP_ADDRESS>/8

Output of # docker version
Client:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:23:59 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:23:59 2016
 OS/Arch:      linux/amd64

Steps to reproduce
I've written bash script to reproduce our workflow without our system: vxlanid_leak.zip
Script requirements: curl, perl (perl-Archive-Tar lib), jq
vxlan id leak is reproduced with it as well. Just get free ids number, run ./launcher.sh 10 200, wait (~ an hour), and get free ids again. (1st parameter - number of threads, 2nd - number of iterations in each thread)
After launch the script (with parameters above) on our infrastructure 54 ids were leaked.
Additional info
We tried etcd 2.3.1, etcd 2.5.1, now zookeeper 3.4.9 but the result is the same.
KV storage is used by docker only.
After update docker to 1.12 the total number of available ids become much bigger, but leak is still remain.
We failed to reproduce it on pure docker.
We failed to reproduce it on pure docker which was connected to swarm.
To get number of free vxlanid we used this utility.
Related issue in docker: https://github.com/docker/docker/issues/29756

cc @docker/core-libnetwork-maintainers.

Thanks for the detailed explanation.
So looks like concurrent requests is what is needed to reproduce this.
Did not take this into account when I tried to reproduce the related docker issue.
I will take a look at it.

Thank you for quick response.
I thought so, but we've just ran the script in 1 thread for 500 iteration and 23 ids were leaked.

@aboch feel free to ping me if you fail to reproduce it. So far we can reproduce the bug only with pure swarm.

I think I have found a way to reproduce the issue with a parallel go test.

We moved to docker 1.12.5 and bits limit increased from 745 to 16776960 so that problem not such critical for us at the moment.
We still have that problem and after two days of running we got
Free 16776130 from 16776960

@aboch was this fixed in Docker? If it was, could you link to the fix?

Any news?
We switched to 17.04.0-ce and issue is still here.

cc @mavenugo do you know if this issue was fixed in Docker recently?


Force metadata to adhere to Google Dataset Search requirements

I decided to check how Google Dataset Search received our Datasets pages, such as with https://search.google.com/test/rich-results?utm_campaign=sdtt&utm_medium=message&url=https%3A%2F%2Fweed-ai.sydney.edu.au%2Fdatasets%2F54c0c5c4-0c15-44c7-9eeb-5affb7e8327e&user_agent=1
It told me I needed a @type specified on each creator, and that description was required.
Existing datasets will need to be migrated to the new requirements. @geezacoleman, are you okay with the description "Crop photography with weeds annotated." on all datasets for now?

Hmm. I think I forgot to update test cases.

@jnothman that works - I think that's an additional area we'll need to include for the metadata in the future. It gives more context around why the images were collected and the possible outcomes from the research.

This one needs to be in. I think it is low risk. Okay to merge, @ElevnLi?


[CSS] > Grid > Masonry

Acceptance criteria

[x] The listed features are documented sufficiently on MDN

[x] BCD is updated

[x] Interactive example and data repos are updated if appropriate

[ ] The content has been reviewed as needed

Features to document

CSS Grid Masonry experimental feature. @rachelandrew already wrote the docs for this, so this probably just involves checking the docs and updating the BCD for any browsers that have updated their support.

Related Gecko bugs

[ ] [css-grid-3] Enable masonry layout by default in Nightly

For folks helping with Firefox-related documentation features — make sure above AC have been done, but also:

Set bugs to dev-doc-complete
Add entry to Firefox release notes if feature is enabled in release
Add entry to Firefox experimental features page if feature is not yet enabled in release

@chrisdavidmills this was the work I did a couple of weeks ago, I just updated Experimental Features to flag it enabled in Nightly.
BCD for the new properties and values is awaiting review: https://github.com/mdn/browser-compat-data/pull/7249

Thanks @rachelandrew ! I reviewed the masonry pages before, so I think we can consider that done. Experimental features page looks OK. I think once the BCD gets reviewed, we can close this.

BCD merged


Digital currency- overview, types, how it works, advantages and disadvantages, risks

NOTE: We tend to stray away  or tend not to publish reviews/comparisons of commercial product offerings.
Brief Summary:
Describe the what, why, and how of your content idea in 2-5 sentences.
This articles aims to educate investors about digital currency. How digital currency works . The types that exists, possible risks, advantages and disadvantages.
Key Takeaways:
What are the 3-5 most important things the reader should understand or be able to do after reading this article?
An overview about digital currency
Different types of digital currency
How digital currency work
Risks involved
Advantages and disadvantages of digital currency
References:
Please list links to any published content/research that you intend to use to support/guide this article. (If none, please indicate 'N/A'.)

Thank you for your topic suggestion. Per the recent message posted in our EngEd Slack channel, we are pausing acceptance of new articles until further notice while we work through the backlog of submitted drafts. We will notify you when we are ready to accept new topic suggestions. Thank you for your patience.


Publish tests

To be able to run the tests prior to installation, as part of building a distro package.

Something like this may also be needed:
https://github.com/pexpect/ptyprocess/pull/22/commits/1fa2011142a200563a9b8fbf303a622ab643cff8


[6.4.x] RHBPMS-4166: BRMS Generates wrong source code for Guided Rules if using 'Formula'

See https://issues.jboss.org/browse/RHBPMS-4166
(cherry picked from commit 4e4b0ee16663b9adac23ebdfa838733a79461ac9)
This is the corollary of https://github.com/droolsjbpm/drools/pull/868 for 6.4.x.

DO NOT MERGE YET - NEED ACKs ON JIRA

@triceo Hi.. can you please ack the JIRA?

ACKs received.. OK to review...


Get an HTML element

Hi,
I am trying to get all  elements in a loaded page, to do that I tried the following query selector:
ElementHandle[] elements = await page.QuerySelectorAllAsync("a");
How can I then extract the "href=" property of each element ? I would like to get all URLs but I don't see how I can do it. I tried to call GetPropertiesAsync(); on each element but I don't see where I can find the element properties.
Thank you very much

I would do this instead:
EvaluateExpressionAsync<string[]>("Array.from(document.querySelectorAll('a')).map(a => a.href);");

@kblok thank you very much I appreciate your help.
Just for my information, is it possible to get the same result by calling page.QuerySelectorAll("a") and doing something with the result ?
Thank you

@malves Not with QuerySelectorAll but you could do this with QuerySelectorAllHandleAsync which returns a JSHandle that points to that array on Chromium.
await page.QuerySelectorAllHandleAsync("a").EvaluateFunctionAsync<string[]("elements => elements.map(a => a.href)");

My first approach uses only one call to chromium, whereas this second approach needs two calls. Any method using QuerySelectorAllAsync would involve X + 1 calls (being X the number of elements).

Perfect, thank you for this explanation :) Let me know if I can help you in anyway


Disable filters in Recent topics for logged out users

The "Included muted", "Unread" and "Participated" filters are not useful to logged out users. We should disable them.
The alternative would be to remove them altogether, but it seems reasonable to advertise that we have this filtering functionality.

@amanagr I think we discussed this one at some point; transcribing to an issue so that we don't lose track of it.

@zulipbot claim

The experience if you click on a filter can be quite confusing, so bumping up the priority.


Expose more methods on Webamp

@durasj Is this what you need for your native media session api work?

Hey @durasj, did you ever see this? I forget where we landed.

Hi @captbaritone, this looks good to me. Later on, it would be good to have access to more stuff, but for now this is perfect.
I've opened an issue https://github.com/durasj/webamp-desktop/issues/11 in the desktop repo for this. That D-Bus mpris module shows pretty well what we could eventually add.

Rather than rebase, I just redid this here c4282817dbd85921d9f9e155e077a3a2a3c067ac


#22 circle ci selenium

adding support for multiple browsers, on circle ci, modified tests to run with chrome on circle ci
configuring circle ci to store test results and artifacts from junit-tests/target

unit tests modification are dirty, but in the light of the open issue to refactor - should not create any difficulties, will update the branch from master to be able to merge


Kiali is showing erroneous traffic

I have two services running and neither interact with each other. I then have a third external service that I've created a service entry for that one of the services talks to over TLS. In Kiali I was expecting it to look like this:
connect-dev -> connectors-example-dev.azurewebsites.net
sts-dev (no traffic either of the above services)
But what Kiali shows is traffic going to the external service which I know is not the case.

Expected behavior
Traffic between sts-dev and connectors-example-dev.azurewebsites.net should not be there.
Steps to reproduce the bug
Deploy two services one that calls an external service that is defined as a service entry.
Version (include the output of istioctl version --remote and kubectl version)
istioctl
client version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.4-10-g9b6d31b"}
citadel version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b-dirty", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.4-10-g9b6d31b"}
egressgateway version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.4-10-g9b6d31b"}
galley version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b-dirty", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.4-10-g9b6d31b"}
ingressgateway version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.4-10-g9b6d31b"}
pilot version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b-dirty", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.4-10-g9b6d31b"}
policy version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b-dirty", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.4-10-g9b6d31b"}
sidecar-injector version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b-dirty", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.4-10-g9b6d31b"}
telemetry version: version.BuildInfo{Version:"1.1.5", GitRevision:"9b6d31b74d1c0cc9358cc82d395b53f71393326b-dirty", User:"root", Host:"3e29fde4-6c3f-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.4-10-g9b6d31b"}
kubectl
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.7", GitCommit:"6f482974b76db3f1e0f5d24605a9d1d38fad9a2b", GitTreeState:"clean", BuildDate:"2019-03-25T02:41:57Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
Helm charts
Environment where bug was observed (cloud vendor, OS, etc)
Azure Kubernetes Service
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[X ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ X] User Experience
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.
istio-dump.tar.gz
Another image showing other services showing up in Kiali as having traffic to the external service:

It looks like this only happens with external hosts using https. If it's just http then I don't see the problem.
I've tested it using httpbin as the external service with the following configuration:
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: httpbin-ext
spec:
  hosts:
    - httpbin.org
  ports:
    - number: 443
      name: https
      protocol: TLS
  resolution: DNS
  location: MESH_EXTERNAL
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: httpbin-virtualservice
spec:
  hosts:
    - httpbin.org
  tls:
    - match:
        - port: 443
          sni_hosts:
            - httpbin.org
      route:
        - destination:
            host: httpbin.org
            port:
              number: 443
          weight: 100

@jmazzitelli any ideas here?

Kiali builds the graph from the telemetry data, from the image it looks like Kiali found more than one time-series for istio_tcp_sent_bytes_total that have destination_service="connectors-example-dev.azurewebsites.net"
Could you query prometheus to check what time-series are being stored there?
istio_tcp_sent_bytes_total{destination_service="connectors-example-dev.azurewebsites.net"}

Sorry I had my cluster in a slightly different state so I'm working from a setup that is slightly changed.
This is what I currently see:

What is interesting is connect-connectors-example-dev... now only shows traffic from connect-dev as expected. But as you can see I have httpbin.org as another external service which was added first. Neither connect-dev or sts-dev call httpbin.org for anything yet Prometheus and therefore Kiali show traffic.
From Prometheus for httpbin.org:

From Prometheus for connect-connectors-example-dev...:

If I remove httpbin.org as an external service I then see all traffic going to connect-connectors-example-dev again even though I haven't changed anything else:

How do you have your ServiceEntry, Gateway and VirtualService configured?
For example, with this configuration, every external request points to my external-svc (en.wikipedia.com)
travels.v1 is running:
watch "curl https://www.google.com | grep -o '<title>.*</title>'"
hotels.v1 is running:
watch "curl https://en.wikipedia.org/wiki/Main_Page | grep -o '<title>.*</title>'"
discount.v1 is running:
watch "curl https://www.apple.com | grep -o '<title>.*</title>'"
But as you can see in the screenshot below, all is going to en.wikipedia.com.

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: external-svc
  namespace : travel-agency
spec:
  hosts:
    - en.wikipedia.com
  exportTo:
    - "."
  location: MESH_EXTERNAL
  ports:
    - number: 443
      name: https
      protocol: HTTPS
  resolution: DNS
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: istio-egressgateway
  namespace: travel-agency
spec:
  selector:
    istio: egressgateway
  servers:
    - port:
        number: 443
        name: http
        protocol: HTTP
      hosts:
        - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: gateway-routing
  namespace: travel-agency
spec:
  hosts:
    - en.wikipedia.com
  exportTo:
    - "*"
  gateways:
    - mesh
    - istio-egressgateway
  http:
    - match:
        - port: 443
          gateways:
            - mesh
      route:
        - destination:
            host: istio-egressgateway.istio-system.svc.cluster.local
    - match:
        - port: 443
          gateways:
            - istio-egressgateway
      route:
        - destination:
            host: en.wikipedia.com
            port:
              number: 443

Is your case similar? I'm going to play with the VirtualService/Gateway to see if i can find anything. Maybe @douglas-reid would know.

The configuration I was using is below. I originally just tried it using a ServiceEntry and no virtual service as well.
I haven't tried configuring it to use an egress gateway although I do have one running.
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: httpbin-ext
spec:
  hosts:
    - httpbin.org
  ports:
    - number: 443
      name: https
      protocol: TLS
  resolution: DNS
  location: MESH_EXTERNAL
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: httpbin-virtualservice
spec:
  hosts:
    - httpbin.org
  tls:
    - match:
        - port: 443
          sni_hosts:
            - httpbin.org
      route:
        - destination:
            host: httpbin.org
            port:
              number: 443
          weight: 100

I repeated the test with only one unrelated ServiceEntry [1], and they all still generate metrics to that ServiceEntry. My workloads are still doing requests on google, apple and wikipedia.
[1]
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: external-svc-netflix
  namespace : travel-agency
spec:
  hosts:
    - "www.netflix.com"
  exportTo:
    - "."
  location: MESH_EXTERNAL
  ports:
    - number: 443
      name: https
      protocol: HTTPS
  resolution: NONE

[2]

@dbarentine I created a separate github issue with a reproducer https://github.com/istio/istio/issues/15038. I think that this is affecting you.
The workaround here would be to create ServiceEntry for all the external calls you make, so they are routed appropriately.
You can block external traffic better understand where are external calls. This will block all external calls, except the ones that are backed by a ServiceEntry.
Check this doc.

@josejulio Thank you for all your work on this. I read through the other bug and your reproducer looks exactly like what I'm seeing. When I move to REGISTRY_ONLY and define ServiceEntries for external services than the problem goes away.
So, it appears to just be Https traffic when ALLOW_ANY is enabled which I think is already pointed out in the other bug.

You're welcome. Glad that you were able to resolve your issue!


Fixed ordering of platform macro's.

As discussed on #30

Thanks for the fix! :+1:

No worries :christmas_tree:


For a 0.2.3 release

Enhance the options for specifying type coercion in tables (#13)

Codecov Report

Merging #16 into master will decrease coverage by 0.94%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
- Coverage   99.50%   98.55%   -0.95%
==========================================
  Files           7        7
  Lines         201      208       +7
==========================================
+ Hits          200      205       +5
- Misses          1        3       +2

Impacted Files
Coverage Δ

src/schema.jl
96.96% <ø> (-3.04%)
:arrow_down:

src/coerce.jl
97.67% <100.00%> (+0.45%)
:arrow_up:

src/convention/coerce.jl
98.30% <0.00%> (-1.70%)
:arrow_down:

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 a9f9f85...fc4f486. Read the comment docs.


fix(checkbox): Fix buildDom to use correct class name for mixedmark.

@traviskaufman PTAL!

Eek! Good catch! You'll need to update the unit test as well. Once you do that and CI passes LGTM

Oops! Tests :) Let's see if that builds now.

Looks like it's good to go. Merging in a bit, if there are no objections.

Merge away
On Thu, Aug 18, 2016 at 10:39 Sérgio Gomes<EMAIL_ADDRESS>wrote:

Looks like it's good to go. Merging in a bit, if there are no objections.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/google/material-design-lite/pull/4680#issuecomment-240743839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIV9bcz9yMfIcGWBJvHxcN4V8tweengks5qhG6xgaJpZM4JncWA
.


TEST: make NoMethodError message check compatible with ruby3.3.0dev

ruby3.3.0dev changes the error messages on NoMethodError with the following commit / issue:
https://github.com/ruby/ruby/pull/6950
https://bugs.ruby-lang.org/issues/18285
So make NoMethodError message check on rspec testsuite compatible with this change.
Fixes #2458 .

Thanks for catching this!


put content in after instead of before for accessibility

Currently you have the content of the tooltip in the before element. This isn't great for accessibility as people using screen readers will hear the content of the tooltip before hearing the inline text of the button etc.
I've just made a simple change to reverse the styling of the before and after pseudo elements. It works just the same visually, but now screen reader users will know what the tooltip text relates to.

@lukehaas Thanks for the contribution! However the project now uses both SASS and LESS for source files. As both should always stay in sync, do you think you could also port your code to the LESS version too?

Thanks, I've now applied those updates to the less file as well.

@kazzkiq I've brought in you latest updates so this is all still good to go in

Perfect. Thanks!


parentWikiId not handled properly

Also recently reported by user:
https://www.synapse.org/#!Synapse:syn5902559/discussion/threadId=219


error

Thanks for developing the plugin. When I try to run the plugin I get this error:
cd /usr/share/redmine/apps/redmine/htdocs && /usr/share/redmine/ruby/bin/bundle exec rake autoclose:autoclose RAILS_ENV=production 2>&1
rake aborted!
You have already activated rake <IP_ADDRESS>, but your Gemfile requires rake 10.1.0. Using bundle exec may solve this.
(See full trace by running task with --trace)
If I run:
cd /usr/share/redmine/apps/redmine/htdocs && bin/rake autoclose:autoclose RAILS_ENV=production > /tmp/log.txt 2>&1
I get no error but the issues are not closed.
How can I fix it? How can I make the plugin appy to all projects, is there a wildcard for the projects configuration?
Thanks.

Hello.
Thank you for trying using the plugin. First error seems like as an error with redmine installation, maybe with Gemfile.lock which needs bundle install run but I am not sure.

Could you please check what is logged by the plugin to standard output (/tmp/log.txt for your run)?
How you configured the plugin?

Nice idea about the wildcarding of all projects, I'll implement it a little later.

Thanks, the script does not produce any output in stdout or stderr. In all cases, standard output and standard error are empty (and therefore log.txt is empty). I ran:
./gem update rake
cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:autoclose RAILS_ENV=production 2>&1
But this lead to the same error than before, but changing the installed version, so then I ran:
./gem uninstall rake
./gem install rake -v 10.1.0
cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:autoclose RAILS_ENV=production 2>&1
This last commands made the plugin to run without giving an error but the plugin does not close any solved issue.
Is there any debugging options to tell what does the plugin do?

There is no extra debug information, I can add a few.
Are you sure there are any issues in project Y that have been resolved more than X days ago where X is a "check interval " setting and Y is a project identifier specified in "Identifier" field in project settings (usually it is a alphanumeric string without spaces)?

Thanks, I have almost 20 issues in state "resolved" with more than 90 days of resolution in all the projects, My settings are:
check interval: 90
User Who closes: Mario (Administrator account)
Note text: Issue is closed.
Included projects: TREMé,Cliente Automotive,Produtora De Comercio
The names of the projects have accents and spaces, do that influence the processing of incidents?

You need to specify project identifiers not names. They can be found in
project settings page.

Best regards,
Eugene Seliverstov
On 28 Jul 2016 7:11 a.m., "javier marcon"<EMAIL_ADDRESS>wrote:

Thanks, I have almost 20 issues in state "resolved" with more than 90 days
of resolution in all the projects, My settings are:
check interval: 90
User Who closes: Mario (Administrator account)
Note text: Issue is closed.
Included projects: TREMé,Cliente Automotive,Produtora De Comercio
The names of the projects have accents and spaces, do that influence the
processing of incidents?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/theirix/redmine_autoclose/issues/1#issuecomment-235796197,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdYRyQXv0sT8Vbz94AIMe5HuEeb6hD7ks5qaCvdgaJpZM4JVlTj
.

Thanks, I changed the included projects option filling it with project identifiers, but I running the command doesn't close the issues (and does not produce any output to stdout or stderr).
The command I run is:
cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:autoclose RAILS_ENV=production 2>&1

Thank you for the information. Please run the plugin version from 'debug' branch and provide the stderr output.

Sorry, I added changes just now. Check the 'debug' branch.

Thanks, I ran it in debug mode but it still leaves unclosed the resolved incidents.
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ git branch

master
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ git fetch
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 5 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (5/5), done.
From https://github.com/theirix/redmine_autoclose
[new branch]      debug      -> origin/debug
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ git checkout debug
Branch debug set up to track remote branch debug from origin.
Switched to a new branch 'debug'
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ git pull
Already up-to-date.
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:preview RAILS_ENV=production 2>&1
redmine_autoclose: interval 2016-04-30 14:21:17 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:autoclose RAILS_ENV=production 2>&1
redmine_autoclose: interval 2016-04-30 14:21:55 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$

In the mmain project is treme (id treme, name TREMé), the other listed projects like treme-generales are subprojects of treme.
In treme-generales for example I have many resolved icidents from 2014, 2015, 2016, etc.

I added a few more debug statements. Could you please update and run again? Also what is your redmine version and was it installed manually or via package manager?

Thanks, this is the result:
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ git pull
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 5 (delta 2), reused 5 (delta 2), pack-reused 0
Unpacking objects: 100% (5/5), done.
From https://github.com/theirix/redmine_autoclose
8d6c037..4a1eb2d  debug      -> origin/debug
Updating 8d6c037..4a1eb2d
Fast-forward
lib/redmine_autoclose/autoclose.rb |    2 ++
1 file changed, 2 insertions(+)
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:preview RAILS_ENV=production 2>&1
redmine_autoclose: interval 2016-04-30 15:17:06 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
redmine_autoclose: issues #<IssueStatus id: 1, name: "Nueva", is_closed: false, is_default: true, position: 1, default_done_ratio: 0>#<IssueStatus id: 2, name: "En curso", is_closed: false, is_default: false, position: 2, default_done_ratio: 50>#<IssueStatus id: 3, name: "Resuelta", is_closed: false, is_default: false, position: 3, default_done_ratio: 80>#<IssueStatus id: 4, name: "Feedback", is_closed: false, is_default: false, position: 4, default_done_ratio: 90>#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>#<IssueStatus id: 6, name: "Rechazada", is_closed: true, is_default: false, position: 6, default_done_ratio: 0>, choosen:
redmine_autoclose: looking to 9
redmine_autoclose: looking to 16
redmine_autoclose: looking to 17
redmine_autoclose: looking to 18
redmine_autoclose: looking to 19
redmine_autoclose: looking to 20
redmine_autoclose: looking to 22
redmine_autoclose: looking to 23
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:autoclose RAILS_ENV=production 2>&1
redmine_autoclose: interval 2016-04-30 15:17:29 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
redmine_autoclose: issues #<IssueStatus id: 1, name: "Nueva", is_closed: false, is_default: true, position: 1, default_done_ratio: 0>#<IssueStatus id: 2, name: "En curso", is_closed: false, is_default: false, position: 2, default_done_ratio: 50>#<IssueStatus id: 3, name: "Resuelta", is_closed: false, is_default: false, position: 3, default_done_ratio: 80>#<IssueStatus id: 4, name: "Feedback", is_closed: false, is_default: false, position: 4, default_done_ratio: 90>#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>#<IssueStatus id: 6, name: "Rechazada", is_closed: true, is_default: false, position: 6, default_done_ratio: 0>, choosen:
redmine_autoclose: looking to 9
redmine_autoclose: looking to 16
redmine_autoclose: looking to 17
redmine_autoclose: looking to 18
redmine_autoclose: looking to 19
redmine_autoclose: looking to 20
redmine_autoclose: looking to 22
redmine_autoclose: looking to 23
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$

Thank you. It seems a problem is with resolved status name. Could you please check issue names at http://YOUR_HOST/issue_statuses ? Is there a 'Resolved' issue status? What about Redmine version?

Ruby is 1.9.1, I don't find redmine version, but I think is Bitnami Redmine 2.4

Thanks, issue_statuses gives me a number: 406

Oh, 2.4 is an extremely old version and I had not tested plugin for 2.4.
About issue_statuses - seems it is a different url for Redmine 2.4. I meant a settings page where you are configuring issue statuses. Could you check it?

Thanks, I will try to chek it.

Thanks. According to the log of your plugin, the resolved state is Resuelta:
#<IssueStatus id: 1, name: "Nueva", is_closed: false, is_default: true, position: 1, default_done_ratio: 0>
#<IssueStatus id: 2, name: "En curso", is_closed: false, is_default: false, position: 2, default_done_ratio: 50>
#<IssueStatus id: 3, name: "Resuelta", is_closed: false, is_default: false, position: 3, default_done_ratio: 80>
#<IssueStatus id: 4, name: "Feedback", is_closed: false, is_default: false, position: 4, default_done_ratio: 90>
#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>
#<IssueStatus id: 6, name: "Rechazada", is_closed: true, is_default: false, position: 6, default_done_ratio: 0>
I changed Resolved for Resuelta in lib/redmine_autoclose/autoclose.rb and now I have this output:
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake autoclose:autoclose RAILS_ENV=production 2>&1
redmine_autoclose: interval 2016-04-30 17:29:09 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
redmine_autoclose: issues #<IssueStatus id: 1, name: "Nueva", is_closed: false, is_default: true, position: 1, default_done_ratio: 0>#<IssueStatus id: 2, name: "En curso", is_closed: false, is_default: false, position: 2, default_done_ratio: 50>#<IssueStatus id: 3, name: "Resuelta", is_closed: false, is_default: false, position: 3, default_done_ratio: 80>#<IssueStatus id: 4, name: "Feedback", is_closed: false, is_default: false, position: 4, default_done_ratio: 90>#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>#<IssueStatus id: 6, name: "Rechazada", is_closed: true, is_default: false, position: 6, default_done_ratio: 0>, choosen: Resuelta
redmine_autoclose: looking to 9
rake aborted!
undefined method detail_for_attribute' for #<Journal:0x000000064f4358> /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activemodel-3.2.16/lib/active_model/attribute_methods.rb:407:in method_missing'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/attribute_methods.rb:149:in method_missing' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:7:in block in when_issue_resolved'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/associations/collection_proxy.rb:91:in reverse_each' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/associations/collection_proxy.rb:91:in method_missing'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:6:in when_issue_resolved' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:19:in block (2 levels) in enumerate_issues'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:18:in block in enumerate_issues' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:16:in enumerate_issues'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:40:in autoclose' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/tasks/autoclose.rake:7:in block (2 levels) in <top (required)>'
Tasks: TOP => autoclose:autoclose
(See full trace by running task with --trace)
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$

Thanks, this is the run with --trace:
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake --trace autoclose:autoclose RAILS_ENV=production 2>&1
** Invoke autoclose:autoclose (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute autoclose:autoclose
redmine_autoclose: interval 2016-04-30 17:34:32 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
redmine_autoclose: issues #<IssueStatus id: 1, name: "Nueva", is_closed: false, is_default: true, position: 1, default_done_ratio: 0>#<IssueStatus id: 2, name: "En curso", is_closed: false, is_default: false, position: 2, default_done_ratio: 50>#<IssueStatus id: 3, name: "Resuelta", is_closed: false, is_default: false, position: 3, default_done_ratio: 80>#<IssueStatus id: 4, name: "Feedback", is_closed: false, is_default: false, position: 4, default_done_ratio: 90>#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>#<IssueStatus id: 6, name: "Rechazada", is_closed: true, is_default: false, position: 6, default_done_ratio: 0>, choosen: Resuelta
redmine_autoclose: looking to 9
rake aborted!
undefined method detail_for_attribute' for #<Journal:0x00000004fd4810> /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activemodel-3.2.16/lib/active_model/attribute_methods.rb:407:in method_missing'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/attribute_methods.rb:149:in method_missing' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:7:in block in when_issue_resolved'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/associations/collection_proxy.rb:91:in reverse_each' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/associations/collection_proxy.rb:91:in method_missing'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:6:in when_issue_resolved' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:19:in block (2 levels) in enumerate_issues'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:18:in block in enumerate_issues' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:16:in enumerate_issues'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:40:in autoclose' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/tasks/autoclose.rake:7:in block (2 levels) in <top (required)>'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:236:in call' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:236:in block in execute'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:231:in each' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:231:in execute'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:175:in block in invoke_with_call_chain' /usr/share/redmine/ruby/lib/ruby/1.9.1/monitor.rb:211:in mon_synchronize'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:168:in invoke_with_call_chain' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:161:in invoke'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:149:in invoke_task' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in block (2 levels) in top_level'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in each' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in block in top_level'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:115:in run_with_threads' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:100:in top_level'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:78:in block in run' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:165:in standard_exception_handling'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:75:in run' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/bin/rake:33:in <top (required)>'
/usr/share/redmine/ruby/bin/rake:23:in load' /usr/share/redmine/ruby/bin/rake:23:in '
Tasks: TOP => autoclose:autoclose
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$

Great, I see the problem. Please check the 'debug' branch again.

Thanks, I got another error:
mzito@mail:/usr/share/redmine/apps/redmine/htdocs/plugins/redmine_autoclose$ cd /usr/share/redmine/apps/redmine/htdocs/ && /usr/share/redmine/ruby/bin/bundle exec /usr/share/redmine/ruby/bin/rake --trace autoclose:autoclose RAILS_ENV=production 2>&1
** Invoke autoclose:autoclose (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute autoclose:autoclose
redmine_autoclose: interval 2016-04-30 17:58:54 UTC, ids ["treme", "acs-automotive", "aerolom", "bodegas-salentein", "compass-group", "treme-conector", "treme-generales", "suma-consultora"]
redmine_autoclose: issues #<IssueStatus id: 1, name: "Nueva", is_closed: false, is_default: true, position: 1, default_done_ratio: 0>#<IssueStatus id: 2, name: "En curso", is_closed: false, is_default: false, position: 2, default_done_ratio: 50>#<IssueStatus id: 3, name: "Resuelta", is_closed: false, is_default: false, position: 3, default_done_ratio: 80>#<IssueStatus id: 4, name: "Feedback", is_closed: false, is_default: false, position: 4, default_done_ratio: 90>#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>#<IssueStatus id: 6, name: "Rechazada", is_closed: true, is_default: false, position: 6, default_done_ratio: 0>, choosen: Resuelta
redmine_autoclose: looking to 9
redmine_autoclose: checking issue 74 of project '9' with date 2014-05-20 19:47:43 UTC => true
Autoclosing issue #74 (Blog tremé)
redmine_autoclose: checking issue 258 of project '9' with date 2014-12-29 18:24:42 UTC => true
Autoclosing issue #258 (Fecha de registros en el tablero)
redmine_autoclose: checking issue 261 of project '9' with date 2014-12-30 23:02:01 UTC => true
Autoclosing issue #261 (Que aparezca rotulo de campo en csv en lugar de aparecer la property)
redmine_autoclose: checking issue 274 of project '9' with date 2015-01-27 14:26:14 UTC => true
Autoclosing issue #274 (Ocultar campos en Vista del registro)
redmine_autoclose: checking issue 279 of project '9' with date 2015-04-21 14:13:31 UTC => true
Autoclosing issue #279 (Al seleccionar registros de hoy en producción no aparecen.)
rake aborted!
undefined method <' for []:Array /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:20:in block (2 levels) in enumerate_issues'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:18:in block in enumerate_issues' /media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each'
/media/datos/redmine/apps/redmine/htdocs/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:6:in each' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:16:in enumerate_issues'
/media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/redmine_autoclose/autoclose.rb:40:in autoclose' /media/datos/redmine/apps/redmine/htdocs/plugins/redmine_autoclose/lib/tasks/autoclose.rake:7:in block (2 levels) in <top (required)>'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:236:in call' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:236:in block in execute'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:231:in each' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:231:in execute'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:175:in block in invoke_with_call_chain' /usr/share/redmine/ruby/lib/ruby/1.9.1/monitor.rb:211:in mon_synchronize'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:168:in invoke_with_call_chain' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:161:in invoke'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:149:in invoke_task' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in block (2 levels) in top_level'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in each' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in block in top_level'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:115:in run_with_threads' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:100:in top_level'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:78:in block in run' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:165:in standard_exception_handling'
/usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:75:in run' /usr/share/redmine/ruby/lib/ruby/gems/1.9.1/gems/rake-10.1.0/bin/rake:33:in <top (required)>'
/usr/share/redmine/ruby/bin/rake:23:in load' /usr/share/redmine/ruby/bin/rake:23:in '
Tasks: TOP => autoclose:autoclose
mzito@mail:/usr/share/redmine/apps/redmine/htdocs$

Also in that last run, issue #74 should be closed by the plugin but checking in redmine it is still on resolved state.
Thanks.

Do you need more information about issue #279 that is causing the error?

Thank you, I found a problem with the #279, please update and check again.
Also if you have 'Closed' issue state with name other than 'Closed' please change it in plugin too.

Thanks, I will change it ald check, because my redmine is in spanish so Closed is Cerrada.
#<IssueStatus id: 5, name: "Cerrada", is_closed: true, is_default: false, position: 5, default_done_ratio: 100>

Thanks, now it worked.

Glad to hear that! I have also update 'master' branch without debugging info. Do not forget to change issue status names.

Thanks, I switched to that branch and changed the names, but now I don't have older resolved issues to test the plugin.

It's okay, I just moved changes between branches so they should be the same except of loigging.


Where has YSlow gone in Chrome?

Up and disappeared from my extensions list, can't get it to install from the links on the site, nor can I find it on the Chrome extensions site.
What has happened here?

Same here

Judging by the underwhelming response rate and lack of any development for years, I'm going to guess this is a dead/abandoned project.

I have test to modify the plugin on chrome, it work well but i have to get rid of all the inline onclick .. but it work with direct input in the javascript console
it appear that the way the plugin grab the tab url is obsolete also :/
i will upload the custom yslow when i have the time to tweak it a little ;)

Same thing happened for me.


Support Healthcheck specification at container launch time or a wait strategy for a command

docker container run supports different arguments for an alternative healthcheck at launch time:

> * --health-cmd

Command to run to check health

--health-interval |   | Time between running the check (ms|s|m|h) (default 0s)
--health-retries |   | Consecutive failures needed to report unhealthy
--health-start-period |   | Start period for the container to initialize before starting health-retries countdown (ms|s|m|h) (default 0s)
--health-timeout |   | Maximum time to allow one check to run (ms|s|m|h) (default 0s)

This can be useful for images that don't themselves implement the HEALTHCHECk instruction or for just altering the healthcheck of an existing image.
It looks like the Docker Java client com.github.dockerjava.api.model.HealthCheck supports it.
It would be useful to be able to leverage a wait strategy either at launch time or with something like Wait.forCommand(...)  that executes a command similar to how the Docker HEALTHCHECK instruction and docker container run CLI work.

I believe this shouldn't be marked as stale.

👍 sorry @mkobit, you're right that we should keep this open.
If anybody would like to contribute a PR for this we'd be very happy to review.

@rnorth, I would like to take this up. Regarding the implementation, would this take place in the GenericContainer class or as a Wait strategy like suggested by @mkobit ?

@glefloch sorry for the slow response. Please could you give me a little more time to think about this?
I’d like to be sure that we implement this because we need to, not just because we can. If we really are doing it to address a real need, the implementation probably varies according to the use cases.
Sent with GitHawk

@rnorth, thanks for the answer.
I actually started working on a basic implementation in the Container interface by adding this method:
SELF withHealthCheck(HealthCheck healthCheck)
I can open a pull request so we can discuss about the implementation.
I still have some tests to write.

@glefloch Any update?

FYI there is withCreateContainerCmdModifier for anything that is not directly supported by GenericContainer:
withCreateContainerCmdModifier(it -> {
    it.withHealthcheck(new HealthCheck().withTest(Arrays.asList("doCheck")));
})

Given my previous comment and as discussed in #2126, healthcheck is a bit too specific to have a first class support in Container interface. However, there is a not-so-difficult way of setting it with withCreateContainerCmdModifier, so I will close the issue :)

I felt on this close issue but feels it could still be useful. I have a healthcheck in my dockerfile. And I want testcontainers to test if the container is healthy so I am testing my health command at the same time. The problem is that the interval is 30 seconds.  It's ok for a container in production but not for a test. However, my understanding is that if I add a new HealthCheck, it will replace the entire check on the container including the command to launch. If I do getHealthCheck, it returns null. Do we have a solution to that?


Add camel-ignite wrapper

no ignite feature, so added a dependency, had to wrap it as it is a regular jar
left the comment in place as not sure that it is relevant for build phase

There is a conflict to resolve


Rolling streams to roll on a schedule

I'd like to be able to specify that a rolling stream rolls on a schedule (maybe via a cron value)
Currently they only roll on frequency.
I'd like it to still roll if it hits the size limit before the schedule

This is the standard cron schedule mechanism used throughout Stroom as per ...
minute hour day, e.g. * * * to roll every minute


Plugin setup

Plugin setup description for calculate GMHI function

I can merge if you're ok with my comments

Sure, I corrected everything :)


Restore wallet using local grin node if possible

I thought it shipped with a local node now. Does it still use the central server?

yes, when local node got synced.
when it don't fully synced, it will use remote server

https://github.com/grinfans/Niffler/commit/7d99cb072c57381bb2275d25cdc49657beb1ee78


Antivirus exclusions not needed/recommended for Windows Defender

Hi there,
the antivirus exclusions on this page includes several executable files (*.exe and *.sys): these exclusions are not needed (and against recommendations) in a native Windows client with Windows Defender.
WD has built-in logic to deal with 1st party executables.
Ruud

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

ID: 6386653c-9f82-1ea7-8f29-377be4e5e3b7
Version Independent ID: a5db2b47-afaf-5917-40cd-740168cad8b6
Content: FSLogix for the enterprise - Azure Architecture Guide
Content Source: docs/example-scenario/wvd/windows-virtual-desktop-fslogix.yml
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @christiaanbrinkhoff
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 436611

We updated these exclusions. Please review: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop-fslogix#antivirus-exclusions

Thanks for the follow-up!
I noticed the document still recommends these exclusions for Defender for Cloud - are you sure these are needed?
Defender for Endpoint/Servers has built-in exclusions for 1st party solutions such as FSLogix, so I expect these exclusions aren't necessary there?

Looking at the AV exclusions, it states:
"\$Storageacct.file.core.windows.net$ShareName*.VHD", `
Should it not be:
"\$Storageacct.file.core.windows.net$ShareName**.VHD", `
Due to each FSLogix VHD being within a folder for each user?


index out of bounds

Any suggestions what is happening here ?

Hashed contents of 629159 out of 636515 files, 7356 remaining
Hashed contents of 636511 files with 5 errors, ignored 629843 with fresh hashes
Extent hash: /var/www/vhosts/redacted.url/.cache/dconf/user
thread 'main' panicked at 'index out of bounds: the len is 128 but the index is<PHONE_NUMBER>3709551615', /build/rustc-1.24.1+dfsg1/src/liballoc/vec.rs:1551:10
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: std::panicking::default_hook::{{closure}}
at src/libstd/sys_common/backtrace.rs:68
2: std::panicking::rust_panic_with_hook
at src/libstd/panicking.rs:397
at src/libstd/panicking.rs:577
3: std::panicking::begin_panic
at src/libstd/panicking.rs:538
4: std::panicking::begin_panic_fmt
at src/libstd/panicking.rs:522
5: core::panicking::panic_fmt
at src/libstd/panicking.rs:498
6: core::panicking::panic_bounds_check
at src/libcore/panicking.rs:58
7: btrfs::linux::operations::fiemap::get_file_extent_map
8: btrfs_dedupe::commands::dedupe_command::dedupe_command
9: btrfs_dedupe::main
10: std::rt::lang_start::{{closure}}
11: main
12: __libc_start_main
13:

I was able to narrow it down to btrfs::get_file_extent_map_for_path failing for a 1 byte file. I removed this file and up to now the error is so far gone.
Maybe someone is able to change the extent_hasher to a skip broken files (or whatever the cause) and  instead just skip the file(s)


Specify VersionId when possible on multipart downloads

This addresses #86 for versioned buckets

Thank you for taking a look!

How is this different than using VersionId in the extra_args parameter?

To clarify, are you proposing that the s3transfer library plumbs the VersionId from the HEAD request it already makes to get object size? Or that the s3transfer users themselves are responsible for making the HEAD request outside the s3transfer library and passing it to download_file()?

One useful feature is grabbing the version id at the beginning (if available) and using that version id throughout the multipart download.

Yes, agreed. This PR is adding the feature.

Thank you for taking a look!

FYI, I do not have any permissions to do any sort of approval on this repo.

How is this different than using VersionId in the extra_args parameter?

To clarify, are you proposing that the s3transfer library plumbs the VersionId from the HEAD request it already makes to get object size? Or that the s3transfer users themselves are responsible for making the HEAD request outside the s3transfer library and passing it to download_file()?

Looking at the code the real bug is that extra_args are not passed along in MultipartDownload.  If that is fixed, then VersionId can be passed as an extra_arg.

One useful feature is grabbing the version id at the beginning (if available) and using that version id throughout the multipart download.

Yes, agreed. This PR is adding the feature.

Looking at the documentation for VersionId this would be a breaking change because GetObjectVersion permission is required.  A non-breaking change would be to extract the ETag from the head_object and use it with the IfMatch header.


rename signing/verifying key to private/public key

As per https://github.com/bigchaindb/bigchaindb/issues/746#issuecomment-257279092

Can we close? @sohkai


Merge answerfile options

Hi there 👋
This is my first PR here and it adds code, tests and docs for merging copier settings from multiple yaml documents included into copier.yml.
Example
Given the following project layout

|-- copier.yml
|-- foo.txt
|-- component
     |-- component.yml
     |-- bar.txt

and the files
# copier.yml
...
_skip_if_exists:
  - foo.txt
---
!include ./component/component.yml

# component.yml
...
_skip_if_exists:
  - component/bar.txt
...

the resulting value for _skip_if_exists will be the concatenated values from both documents i.e. ["foo.txt", "/component/bar.txt"] instead the latest document overwriting the previous value i.e. ["/component/bar.txt"].
Details
This PR only adds logic for merging settings that are not order dependent i.e. skip_if_exists, jinja_extensions, secret_questions and exclude. For order dependent settings (such as  tasks or migrations) it would have to be decided what the order of execution should be. Do tasks from multiple document run in the order the documents are defined or in reverse? In any case this should probably go in another PR and I'd be happy to work on this.

Thanks for the contribution. May I am what's the problem you find with current behavior? It seems more advanced to me at first sight.

Codecov Report

Merging #846 (4788e05) into master (92955cf) will decrease coverage by 17.56%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master     #846       +/-   ##
===========================================
- Coverage   96.57%   79.00%   -17.57%
===========================================
  Files          41       41
  Lines        2976     2953       -23
===========================================
- Hits         2874     2333      -541
- Misses        102      620      +518

Flag
Coverage Δ

unittests
79.00% <100.00%> (-17.57%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

copier/template.py
95.75% <100.00%> (-0.37%)
:arrow_down:

tests/test_config.py
99.09% <100.00%> (ø)

tests/test_vcs.py
20.33% <0.00%> (-79.67%)
:arrow_down:

tests/test_prompt.py
10.40% <0.00%> (-79.49%)
:arrow_down:

tests/test_complex_questions.py
29.72% <0.00%> (-70.28%)
:arrow_down:

tests/test_tools.py
50.00% <0.00%> (-42.00%)
:arrow_down:

tests/test_updatediff.py
61.11% <0.00%> (-38.89%)
:arrow_down:

tests/test_templated_prompt.py
71.18% <0.00%> (-28.82%)
:arrow_down:

tests/conftest.py
71.42% <0.00%> (-24.03%)
:arrow_down:

copier/user_data.py
82.24% <0.00%> (-12.28%)
:arrow_down:

... and 16 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks for the contribution. May I am what's the problem you find with current behavior? It seems more advanced to me at first sight.

A limitation of the current behavior (that this PR partially addresses) is that you cannot split a large copier.yml into multiple modular files where settings are concerned. You can split questions across multiple files but settings have to be globally defined.
At work I use copier to define base templates for our infrastructure from modular components (that are used in multiple such base templates). The top level copier.yml then just includes all the components' copier.yml files.
|-- copier.yml
|-- componentA  #
|     |-- copier.yml
|     |-- ...
|-- componentB
|     |-- copier.yml
|     |-- ...
|-- ...
|-- componentN

A concrete problem we have is that each component may use different jinja extensions and that with the current behavior one needs to maintain the list of extensions needed in the top level copier.yml instead of each component defining the extensions it needs. This is also true for files we like to exclude or skip. Some definitions make sense at a global level (say excluding all readme.md files) but for component specific files it gets messy if they all need to maintained in the global copier.yml. This is especially true when components change (and multiple people are responsible) for some of the components.
I hope that explanation makes sense? I also spotted an issue with the PR where the auto formatter seems to have messed up the docs changes I added. I will try and fix this tomorrow. Just let me know if you have any other questions and/or see any issue with the PR?

Ah sorry, I seem to have understood your initial comment on the contrary. So, you mean that the current behavior is to replace lists, whereas the new behavior is to concatenate them, right?

Ah sorry, I seem to have understood your initial comment on the contrary. So, you mean that the current behavior is to replace lists, whereas the new behavior is to concatenate them, right?

Yes, that is correct. The new behavior is to concatenate the lists for the settings jinja_extensions, exclude, skip_if_exists and secret_questions. For other settings the current behavior of replacing the settings is retained. I'd like to add merging of other settings, especially tasks and migrations in another PR if this one is accepted.

I've fixed the docs formatting and added clearer language and an example for merging settings from multiple files. I've also changed the test slightly so that it checks that options are concatenated in the order they were given.

@yajo thank you for your review and sorry to bother you again but could you trigger a rerun of the CI? Some of the required checks raise
Error: Codecov: Failed to properly upload: The process '/Users/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 255
It appears there is no clear cause for this issue and I hope this is just a fluke that disappears on a rerun.

Ah yes... codecov fails all the time, sorry. Retrying.