JIRA collector is not gathering data in feature db collection

I have configured the JIRA collector, it did reflected the Project and Board Name. So the data was collected under "team" DB collection but the collector is not pulling data for issues.
These are the logs
2019-04-01 15:17:00,018 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 boards.
2019-04-01 15:17:01,348 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-01T15:16:00.017 0        1s
2019-04-01 15:17:01,357 INFO  c.c.d.collector.CollectorTask - Finished                         1s
2019-04-01 15:18:00,001 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-01 15:18:00,008 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-01 15:18:00,008 INFO  c.c.d.collector.CollectorTask - https://jira.com/
2019-04-01 15:18:00,008 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-01 15:18:00,008 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Board mode
2019-04-01 15:18:00,009 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 8. Collector is only collecting updated/new issues.
Can you please help me with this issue.
If you need more information please let me know.

Can you post properties

Even i had the same issue . here i am posting my properties file
Database Name
dbname=dashboarddb
Database HostName - default is localhost
dbhost=localhost
Database Port - default is 27017
dbport=27017
MongoDB replicaset
dbreplicaset=false
dbhostport=[localhost:27017,<IP_ADDRESS>:27017,127.0.0.:27017]
Database Username - default is blank
dbusername=dashboarduser
Database Password - default is blank
dbpassword=dbpassword
Logging File location
logging.file=./logs/jira.log
PageSize - Expand contract this value depending on Jira implementation's
default server timeout setting (You will likely receive a SocketTimeoutException)
feature.pageSize=100
Delta change date that modulates the collector item task
Occasionally, these values should be modified if database size is a concern
feature.deltaStartDate=2016-03-01T00:00:00.000000
feature.masterStartDate=2016-03-01T00:00:00.000000
feature.deltaCollectorItemStartDate=2016-03-01T00:00:00.000000
Chron schedule: S M D M Y [Day of the Week]
feature.cron=0 0/1 * * * *
ST Query File Details - Required, but DO NOT MODIFY
feature.queryFolder=jiraapi-queries
feature.storyQuery=story
feature.epicQuery=epic
feature.projectQuery=projectinfo
feature.memberQuery=memberinfo
feature.sprintQuery=sprintinfo
feature.teamQuery=teaminfo
feature.trendingQuery=trendinginfo
JIRA CONNECTION DETAILS:
Enterprise Proxy - ONLY INCLUDE IF YOU HAVE A PROXY
feature.jiraBaseUrl=https://iatvirtusa.atlassian.net/
feature.jiraQueryEndpoint=rest/api/2/
For basic authentication, requires username:password as string in base64
This command will make this for you:  echo -n username:password | base64
feature.jiraCredentials=SUFUVmlydHVzYUBnbWFpbC5jb206SUFUVmlydHVzYTEyMyQ=
OAuth is not fully implemented; please blank-out the OAuth values:
feature.jiraOauthAuthtoken=
feature.jiraOauthRefreshtoken=
feature.jiraOauthRedirecturi=
feature.jiraOauthExpiretime=
#############################################################################
In Jira, general IssueType IDs are associated to various 'issue'
attributes. However, there is one attribute which this collector's
queries rely on that change between different instantiations of Jira.
Please provide a string name reference to your instance's IssueType for
the lowest level of Issues (for example, 'user story') specific to your Jira
instance.  Note:  You can retrieve your instance's IssueType Name
listings via the following URI:  https://[your-jira-domain-name]/rest/api/2/issuetype/
Multiple comma-separated values can be specified.
#############################################################################
feature.jiraIssueTypeNames=Story,Task,Bug
#############################################################################
In Jira, your instance will have its own custom field created for 'sprint' or 'timebox' details,
which includes a list of information.  This field allows you to specify that data field for your
instance of Jira. Note: You can retrieve your instance's sprint data field name
via the following URI, and look for a package name com.atlassian.greenhopper.service.sprint.Sprint;
your custom field name describes the values in this field:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraSprintDataFieldName=customfield_10021
#############################################################################
In Jira, your instance will have its own custom field created for 'super story' or 'epic' back-end ID,
which includes a list of information.  This field allows you to specify that data field for your instance
of Jira.  Note:  You can retrieve your instance's epic ID field name via the following URI where your
queried user story issue has a super issue (for example, epic) tied to it; your custom field name describes the
epic value you expect to see, and is the only field that does this for a given issue:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraEpicIdFieldName=customfield_10018
#############################################################################
In Jira, your instance will have its own custom field created for 'story points'
This field allows you to specify that data field for your instance
of Jira.  Note:  You can retrieve your instance's storypoints ID field name via the following URI where your
queried user story issue has story points set on it; your custom field name describes the
story points value you expect to see:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraStoryPointsFieldName=customfield_10023
#############################################################################
In Jira, your instance will have its own custom field created for 'team'
This field allows you to specify that data field for your instance
of Jira.  Note:  You can retrieve your instance's team ID field name via the following URI where your
queried user story issue has team set on it; your custom field name describes the
team value you expect to see:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraTeamFieldName=
Set this to true if you use boards as team
feature.jiraBoardAsTeam=true

2019-04-02 16:45:00,062 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-02 16:45:00,063 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:45:00,092 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Team mode
2019-04-02 16:45:00,092 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 4. Collector is only collecting updated/new issues.
2019-04-02 16:45:00,680 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 projects.
2019-04-02 16:45:01,672 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-02T16:44:00.396 0        1s
2019-04-02 16:45:01,724 INFO  c.c.d.collector.CollectorTask - Finished                         1s
2019-04-02 16:46:00,001 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-02 16:46:00,370 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:46:00,370 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-02 16:46:00,370 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:46:00,371 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Team mode
2019-04-02 16:46:00,371 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 4. Collector is only collecting updated/new issues.
2019-04-02 16:46:00,492 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 projects.
2019-04-02 16:46:02,150 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-02T16:45:00.681 0        1s
2019-04-02 16:46:02,209 INFO  c.c.d.collector.CollectorTask - Finished                         1s
2019-04-02 16:47:00,002 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-02 16:47:00,303 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:47:00,304 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-02 16:47:00,304 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:47:00,304 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Team mode
2019-04-02 16:47:00,305 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 4. Collector is only collecting updated/new issues.
2019-04-02 16:47:00,463 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 projects.
2019-04-02 16:47:01,325 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-02T16:46:00.531 0        1s
2019-04-02 16:47:01,614 INFO  c.c.d.collector.CollectorTask - Finished                         1s
2019-04-02 16:48:00,000 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-02 16:48:00,145 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:48:00,145 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-02 16:48:00,146 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:48:00,146 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Team mode
2019-04-02 16:48:00,146 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 4. Collector is only collecting updated/new issues.
2019-04-02 16:48:00,235 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 projects.
2019-04-02 16:48:01,323 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-02T16:47:00.463 0        1s
2019-04-02 16:48:01,324 INFO  c.c.d.collector.CollectorTask - Finished                         1s
2019-04-02 16:49:00,001 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-02 16:49:00,005 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:49:00,005 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-02 16:49:00,006 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:49:00,006 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Team mode
2019-04-02 16:49:00,006 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 4. Collector is only collecting updated/new issues.
2019-04-02 16:49:00,041 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 projects.
2019-04-02 16:49:01,010 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-02T16:48:00.236 0        1s
2019-04-02 16:49:01,021 INFO  c.c.d.collector.CollectorTask - Finished                         1s

Hey sorry for the late reply.
Here is my application.properties file
`# Database Name
dbname=dashboard
Database HostName - default is localhost
dbhost=<IP_ADDRESS>
Database Port - default is 27017
dbport=27017
MongoDB replicaset
dbreplicaset=false
dbhostport=<IP_ADDRESS>:27017
Database Username - default is blank
dbusername=dbuser
Database Password - default is blank
dbpassword=*********
Logging File location
logging.file=./logs/jira.log
#logging.level.com.atlassian.jira=INFO
logging.level.com.capitalone.dashboard=DEBUG
logging.level.com.capitalone.dashboard.collector=DEBUG
PageSize - Expand contract this value depending on Jira implementation's
default server timeout setting (You will likely receive a SocketTimeoutException)
feature.pageSize=50
Delta change date that modulates the collector item task
Occasionally, these values should be modified if database size is a concern
feature.deltaStartDate=2018-03-01T00:00:00.000000
feature.masterStartDate=2016-03-01T00:00:00.000000
feature.deltaCollectorItemStartDate=2016-03-01T00:00:00.000000
Chron schedule: S M D M Y [Day of the Week]
feature.cron=0 0/1 * * * *
ST Query File Details - Required, but DO NOT MODIFY
feature.queryFolder=jiraapi-queries
feature.storyQuery=story
feature.epicQuery=epic
JIRA CONNECTION DETAILS:
Enterprise Proxy - ONLY INCLUDE IF YOU HAVE A PROXY
feature.jiraProxyUrl=
feature.jiraProxyPort=
feature.jiraBaseUrl=https://jira.com/
feature.jiraQueryEndpoint=rest/api/2/
For basic authentication, requires username:password as string in base64
This command will make this for you:  echo -n username:password | base64
feature.jiraCredentials=*****************************************
OAuth is not fully implemented; please blank-out the OAuth values:
feature.jiraOauthAuthtoken=
feature.jiraOauthRefreshtoken=
feature.jiraOauthRedirecturi=
feature.jiraOauthExpiretime=
#############################################################################
In Jira, general IssueType IDs are associated to various 'issue'
attributes. However, there is one attribute which this collector's
queries rely on that change between different instantiations of Jira.
Please provide a string name reference to your instance's IssueType for
the lowest level of Issues (for example, 'user story') specific to your Jira
instance.  Note:  You can retrieve your instance's IssueType Name
listings via the following URI:  https://[your-jira-domain-name]/rest/api/2/issuetype/
Multiple comma-separated values can be specified.
#############################################################################
feature.jiraIssueTypeNames=Story,Epic
#############################################################################
In Jira, your instance will have its own custom field created for 'sprint' or 'timebox' details,
which includes a list of information.  This field allows you to specify that data field for your
instance of Jira. Note: You can retrieve your instance's sprint data field name
via the following URI, and look for a package name com.atlassian.greenhopper.service.sprint.Sprint;
your custom field name describes the values in this field:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraSprintDataFieldName=customfield_XXXXX
#############################################################################
In Jira, your instance will have its own custom field created for 'super story' or 'epic' back-end ID,
which includes a list of information.  This field allows you to specify that data field for your instance
of Jira.  Note:  You can retrieve your instance's epic ID field name via the following URI where your
queried user story issue has a super issue (for example, epic) tied to it; your custom field name describes the
epic value you expect to see, and is the only field that does this for a given issue:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraEpicIdFieldName=customfield_XXXX
#############################################################################
In Jira, your instance will have its own custom field created for 'story points'
This field allows you to specify that data field for your instance
of Jira.  Note:  You can retrieve your instance's storypoints ID field name via the following URI where your
queried user story issue has story points set on it; your custom field name describes the
story points value you expect to see:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraStoryPointsFieldName=
#############################################################################
In Jira, your instance will have its own custom field created for 'team'
This field allows you to specify that data field for your instance
of Jira.  Note:  You can retrieve your instance's team ID field name via the following URI where your
queried user story issue has team set on it; your custom field name describes the
team value you expect to see:
https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
#############################################################################
feature.jiraTeamFieldName=customefield_XXXX
Set this to true if you use boards as team
feature.jiraBoardAsTeam=true
#Additional Parameters
#feature.jiraSprintDataFieldName=customfield_10007
#feature.jiraEpicIdFieldName=customfield_10003
#feature.jiraStoryPointsFieldName=customfield_10004
#feature.jiraTeamFieldName=customfield_11248
#feature.collectorItemOnlyUpdate=false
#feature.maxNumberOfFeaturesPerBoard=8000
`

Go here https://<URL>/rest/api/2/issuetype and get the ids of the issuetypes that you want to pull.
Gor each issuetype execpt epic you need to add the following:
feature. jiraStoryIds[0]=<id_from_above>
feature. jiraStoryIds[1]=<next_id_from_above>
Get the epic id from step 1 and add it here:
feature.jiraEpicId=
Make sure each of the following are field out correctly:

feature.jiraSprintDataFieldName=
feature.jiraEpicIdFieldName=
feature.jiraStoryPointsFieldName=
feature.jiraTeamFieldName=

Once the above has be verified to be correct, delete the Team, Scope and Feature collections. Finally, in the collectors collection find the Jira collector and set lastRefreshTime and lastExecuted to 0

Thanks for a quick response.
So delete the Team, Scope and Feature collections from mongo DB correct? And when I re-run the collector will these collectors get created ?

Yes they will be recreated. But make sure you have updated the 1-4 correctly.

Problem ... @Sbrenthughes
The restarted the collector with the change mentioned by you.
getting null pointer errrr
2019-04-02 16:01:00,000 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-02 16:01:00,010 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:01:00,010 INFO  c.c.d.collector.CollectorTask - https://mountdiablo.jira.com/
2019-04-02 16:01:00,010 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-02 16:01:00,010 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Team mode
2019-04-02 16:01:00,010 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 5. Collector is only collecting updated/new issues.
2019-04-02 16:01:00,016 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 2 projects.
2019-04-02 16:01:01,398 ERROR c.c.d.collector.FeatureCollectorTask - Failed to collect jira information
java.lang.NullPointerException: null
at com.capitalone.dashboard.collector.DefaultJiraClient.lambda$getFeaturesFromQueryURL$1(DefaultJiraClient.java:365) ~[jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at java.util.ArrayList.forEach(ArrayList.java:1257) ~[na:1.8.0_201]
at com.capitalone.dashboard.collector.DefaultJiraClient.getFeaturesFromQueryURL(DefaultJiraClient.java:356) ~[jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.DefaultJiraClient.getIssues(DefaultJiraClient.java:322) ~[jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.FeatureCollectorTask.lambda$updateStoryInformation$6(FeatureCollectorTask.java:256) [jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at java.util.ArrayList.forEach(ArrayList.java:1257) ~[na:1.8.0_201]
at com.capitalone.dashboard.collector.FeatureCollectorTask.updateStoryInformation(FeatureCollectorTask.java:252) [jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:153) [jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:46) [jira-feature-collector.jar!/:3.0.2-SNAPSHOT]
at com.capitalone.dashboard.co

@Sbrenthughes The changes mentioned by you are as per the latest commits with respect to the multiple jira Ids. I have an instance where I have setup Hygieia on the older version (before 12 days). Can you guide me on it.
Can you help me with the JIRA Apis through which I can verify the customfield IDS  ?

https://github.com/Hygieia/Hygieia/blob/gh-pages/pages/hygieia/collectors/feature/jira.md shows how you can find custom fields

still getting the same , i updated above all
2019-04-03 16:40:00,016 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-03 16:40:00,017 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-03 16:40:00,017 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-03 16:40:00,033 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Board mode
2019-04-03 16:40:00,035 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 0. Collector is only collecting updated/new issues.
2019-04-03 16:40:00,091 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 boards.
2019-04-03 16:40:05,259 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-03T16:37:57.167 0        5s
2019-04-03 16:40:05,273 INFO  c.c.d.collector.CollectorTask - Finished                         5s
2019-04-03 16:41:00,000 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-03 16:41:00,024 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-03 16:41:00,025 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-03 16:41:00,025 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-03 16:41:00,026 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Board mode
2019-04-03 16:41:00,026 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 0. Collector is only collecting updated/new issues.
2019-04-03 16:41:00,030 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 boards.
2019-04-03 16:41:00,892 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-03T16:40:00.091 0        0s
2019-04-03 16:41:00,896 INFO  c.c.d.collector.CollectorTask - Finished                         0s
2019-04-03 16:42:00,001 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2019-04-03 16:42:00,031 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-03 16:42:00,031 INFO  c.c.d.collector.CollectorTask - https://iatvirtusa.atlassian.net/
2019-04-03 16:42:00,033 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2019-04-03 16:42:00,033 INFO  c.c.d.collector.FeatureCollectorTask - JIRA Collector is set to work in Board mode
2019-04-03 16:42:00,033 INFO  c.c.d.collector.FeatureCollectorTask - Hours since last run = 0. Collector is only collecting updated/new issues.
2019-04-03 16:42:00,038 INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 boards.
2019-04-03 16:42:01,040 INFO  c.c.d.collector.CollectorTask - Story Data Collected since 2019-04-03T16:41:00.030 0        1s
2019-04-03 16:42:01,046 INFO  c.c.d.collector.CollectorTask - Finished                         1s

The collector says that it’s collecting from today. Did you delete the collections mentioned?

@Sbrenthughes The changes mentioned by you are as per the latest commits with respect to the multiple jira Ids. I have an instance where I have setup Hygieia on the older version (before 12 days). Can you guide me on it.
Can you help me with the JIRA Apis through which I can verify the customfield IDS ?

feature.jiraTeamFieldName=customefield_XXXX  make this blank if you want to use board mode and for older versions
feature.jiraStoryId=xxxxx. should be set
it will collect only stories. the new master has code for all. it worked for me thank you.

https://github.com/Hygieia/Hygieia/issues/2979#issuecomment-519777039

what happens if i delete feature collection from mongodb manually? will it be recreated after i rub the command for jira collector?

yes it will recreate again feature collection.

thanks @continuum-vikrant-tyagi

i am able to fetch type=story ,i am not able to get all tasks that are epics .though i have configured properties
feature.jiraIssueTypeNames=Story,Task,Epic
feature.jiraIssueTypeID=Story
feature.collectorItemOnlyUpdate=false
feature.jiraSprintDataFieldName=customfield_10020
feature.jiraEpicIdFieldName=customfield_10014
feature.jiraStoryPointsFieldName=customfield_10016
feature.jiraTeamFieldName=
feature.jiraBoardAsTeam=true
what may be the issue?
can anyone help

The same question
2019-12-17 15:00:00,652 [taskScheduler-1] INFO  c.c.d.collector.FeatureCollectorTask - Refreshing issues for Team ID:10502
2019-12-17 15:00:00,741 [taskScheduler-1] INFO  c.c.dashboard.client.RestClient - makeRestCall op=GET url=http://<IP_ADDRESS>:8080/rest/agile/1.0/team/10502/issue?jql=issueType in ('Task') and updatedDate>='2019/11/17 15:00'&fields=id&startAt=0 status=404 duration=68
2019-12-17 15:00:00,742 [taskScheduler-1] ERROR c.c.d.collector.DefaultJiraClient - Error in calling JIRA API: http://<IP_ADDRESS>:8080/rest/agile/1.0/team/10502/issue?jql=issueType in ('Task') and updatedDate>='2019/11/17 15:00'&fields=id&startAt=0
2019-12-17 15:00:00,745 [taskScheduler-1] INFO  c.c.d.collector.CollectorTask - Team Issues Refreshed            0s
2019-12-17 15:00:00,748 [taskScheduler-1] INFO  c.c.d.collector.FeatureCollectorTask - Collected 0 teams and 21 projects
2019-12-17 15:00:00,754 [taskScheduler-1] INFO  c.c.d.collector.FeatureCollectorTask - Collecting 1 of 1 projects.
2019-12-17 15:00:01,605 [taskScheduler-1] INFO  c.c.dashboard.client.RestClient - makeRestCall op=GET url=http://<IP_ADDRESS>:8080/rest/api/2/search?jql=project=10502 and issueType in ('Task') and updatedDate>='2019/11/17 15:00'&fields=id,key,issuetype,status,summary,created,updated,project,issuelinks,assignee,sprint,epic,aggregatetimeoriginalestimate,timeoriginalestimate,,customfield_10000,customfield_10002,customfield_10003&startAt=0 status=200 duration=850
2019-12-17 15:00:01,620 [taskScheduler-1] ERROR c.c.d.collector.FeatureCollectorTask - Failed to collect jira information
java.lang.NullPointerException: null
at com.capitalone.dashboard.collector.DefaultJiraClient.lambda$getFeaturesFromQueryURL$1(DefaultJiraClient.java:402) ~[jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at java.util.ArrayList.forEach(ArrayList.java:1249) ~[na:1.8.0_131]
at com.capitalone.dashboard.collector.DefaultJiraClient.getFeaturesFromQueryURL(DefaultJiraClient.java:393) ~[jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at com.capitalone.dashboard.collector.DefaultJiraClient.getIssues(DefaultJiraClient.java:359) ~[jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at com.capitalone.dashboard.collector.FeatureCollectorTask.lambda$updateStoryInformation$6(FeatureCollectorTask.java:262) [jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at java.util.ArrayList.forEach(ArrayList.java:1249) ~[na:1.8.0_131]
at com.capitalone.dashboard.collector.FeatureCollectorTask.updateStoryInformation(FeatureCollectorTask.java:258) [jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:159) [jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:48) [jira-feature-collector.jar!/:3.1.2-SNAPSHOT]
at com.capitalone.dashboard.collector.CollectorTask.run(CollectorTask.java:63) [core-3.1.9.jar!/:3.1.2-SNAPSHOT]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.2.5.RELEASE.jar!/:4.2.5.RELEASE]
at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) [spring-context-4.2.5.RELEASE.jar!/:4.2.5.RELEASE]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_131]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_131]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_131]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]

feature.deltaCollectorItemStartDate=2008-01-01T00:00:00.000000
feature.deltaStartDate=2015-03-01T00:00:00.000000
feature.masterStartDate=2008-01-01T00:00:00.000000
feature.cron=0 * * * * *
feature.queryFolder=jiraapi-queries
feature.storyQuery=story
feature.epicQuery=epic
feature.jiraBaseUrl=http://<IP_ADDRESS>:8080
feature.jiraQueryEndpoint=rest/api/2/
feature.jiraCredentials=ZHkteGppbnl1OlpoYW53YW5nMDAw
feature.jiraOauthAuthtoken=
feature.jiraOauthRefreshtoken=
feature.jiraOauthRedirecturi=
feature.jiraOauthExpiretime=
feature.jiraIssueTypeNames=Task
feature.jiraSprintDataFieldName=customfield_10000
feature.jiraEpicIdFieldName=customfield_10002
feature.jiraStoryPointsFieldName=customfield_10003
feature.jiraTeamFieldName=
feature.collectorItemOnlyUpdate=true
feature.maxNumberOfFeaturesPerBoard=1000
feature.refreshTeamAndProjectHours=1
feature.jiraStoryIds[0]=3

This is my configuration，It's a problem there

Anybody help!!!!

any updates on this?


Favi Icon for Mobile Bookmarks

As a user, I'd like to customize the fave-icon of my ha-fusion page.
Why?  I've bookmarked my ha-fusion on the homepage of my iOS device, and iOS takes the favi-icon of a webpage when bookmarking it.

as a workaround, add your own favicon through the docker compose
- /path/to/your/favicon.png:/app/build/client/favicon.png


Add other execution types

Added R, Bash and Custom execution types by introducing ExecutionType enum.
Still have to resolve which images will be used for the R and Custom types. Each image would have to contain at least gcloud. Currently it just resolves to the DRIVER_IMAGE.

We might consider users providing their own container, but it also means they can run arbitrary code without code review on production data. Maybe "test" could run any image, and standard must use an image from a specific artefact registry?

Any thoughts on this first draft implementation?

One image is easy! More than happy to do that :)

Closing in favour of #82.


Update "Getting started" section.

Update the Getting Started section to enable users with a Microsoft alias (including employees and contractors) to reach out to internal community channels and join community meeting invites. The internal links will be eventually updated (as a separate PR) in the private cpp_client_telemetry_modules repository.

Only document update, skipping the tests for merge.


Share my profile through a direct link so people can start talking to me

So people can start talking to me.
https://www.sketch.com/s/aa87e1e9-2fa2-46fb-b2c7-5414cdf07cb3/a/YZYZVGL

Maybe at first we can do a simpler version with a "public link" (no unique link) we can use the same link and scan the same QR code

I understood it that way. Basically I am sharing my account invite link which is pseudo private (it is 40+hex numbers which is hard to guess but always the same)

I understood it that way. Basically I am sharing my account invite link which is pseudo private (it is 40+hex numbers which is hard to guess but always the same)

Can you please describe the flow in a bit more depth so that I can understand?
@filoozom feel free to also add your ideas, for example I would be interested if we could use a version of short codes?

It might be possible to use short codes, but I'm not sure how secure my implementation actually is. For now I'd take the simplest route and have either a long link that contains all the useful info (maybe encoded in base64 or something to make it a bit shorter than a hex address) or some sort of on-chain registry to have shorter links. That would depend on the chain we'd use and the associated cost.

Can you please describe the flow in a bit more depth so that I can understand?

It was a response to @david-gauquelin suggestion to start with a non-unique link. So essentially the link being my ETH address.


Message centre data on the Relay

Messaging centre data structure in app
Updating methods interacting with the messaging and notifications data

-Closig this issue as discussed with dev.


Integrate Re-Cite into CitationGecko, and/or vice versa?

Hopefully obvious enough from the title. Here, a link to Re-Cite:
https://github.com/recite/propagation_of_error

https://github.com/recite/propagation_of_error/issues/3

recite/propagation_of_error#3


⚠ Turnos 24x7 has degraded performance

In 438e212, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1082 ms

Resolved: Turnos 24x7 performance has improved in 52ac5ee.


[Responsive Navigation] Vertical menu bug in safari when resizing

When I resize the Safari window such that all items in menu are under each other and then resize the window back two first items get stucked and won't return to horizontal position.
After resizing:

You should be able to reproduce it easily by just resizing window as I described above. The bug occurs on documentation page (here)
My Safari version: 9.0.1.

Confirmed in Safari 8 too. It's because it still has the display: table-cell; when sized back to large.

Not sure what the fix is short of a float based menu. Anyone deal with this table based menu issue before?

Closing in favor of https://github.com/zurb/foundation-sites/issues/7235 . We're trying some different things and still looking for suggestions.


Could you add the URL to your blog in the 'About' section?

It would be great to be able to find it from Github :-)

Fixed :)


Support for questionnaire-item-control = "radio-button" oder "drop-down"

The Extension http://hl7.org/fhir/R4/extension-questionnaire-itemcontrol.html allows for choice-types the choosing between radio-buttons and drop-down menus. Currently, the app uses always radio-buttons if there is a
Even though it allows not for new use-cases, this is a common option in most EDC systems, as depending of the length of the questionnaire and the length of the list of choices, drop-down menus can be more clear.

See possible implementation in branch "extend-extension-support"

Should be implemented with https://github.com/NUMde/compass-numapp-frontend/commit/301d57506c307d7f3ca207680b2b31a4545b730e. As radio buttons are the default, only the drop-down extension was explicitly considered


Update README.md

VirusInfection
Group Member: Reed, Skylar and Omar
Leader: Skylar
Part I: (Reed)
Part II: (Skylar)
Once we found a good computer repair shop to take the computer to, I immediately took it over. We picked Spotts Professional Computers. When I got there at about 5:30, the employee was very nice. He first asked what was going on with the computer, so I told him that when I turned the computer on, it immediately opened the command prompt, which in turn opened more command prompts, eventually shutting down the computer. He then quickly hooked the computer up to a monitor to check out the situation. Meanwhile, I filled out a piece of paper that asked for my personal information so they could contact me for any further information. He then told me the outrageous price to just LOOK at the computer, which was a base price of $79.99. He asked me how long the computer had been malfunctioning, so I told him I didn’t know. He asked if I had noticed any differences before today, and I told him I didn’t think so. Once the computer started up and started opening the command prompts, he looked super puzzled and even made the statement “well, this is strange”. He asked how long it took before the computer shut itself off, and I told him about 5-10 minutes. He kept working on the computer, and assured me that they would have it figured out by the next day, so I left. The next day, I received a phone call at about 12 o’clock to pick up the computer.
Part III: (Omar)
I was the one that picked up the computer at the repair shop after it was fixed. The computer shop our group used was called “Spotts Computer Repair.” It is a small shop located at 180 W University Parkway. The pick-up process was pretty straight forward. I went in, they asked me what my name was and what I needed. I told them I was picking up a computer dropped off by Skylar Argo. She was the group member that chose the place and took the computer there. She let them know before-hand that I was picking up the computer instead of her, so they weren’t very skeptic. After I mentioned her name, they confirmed that she was indeed a costumer and directed me towards the computer. They then proceeded to show me that it was fully working and explained the problem to me. Everything seemed to be fine as they had claimed. At this point I was ready to check out. This is the part where things started going down-hill. They charged me $80 dollars for simply removing a virus that we looked up from google. I’m not sure what other places are charging but $80 for something so simple is hands down ridiculous. Anyway, the job was done and there was no option but to pay, so I did. For that price you would imagine they would at least give you a fancy bag or something... That wasn’t the case at all. They straight up gave me the computer in hand and said good day. I signed their copy of the receipt and left. I wouldn’t recommend this place to anyone. I’m sure other places would do the same for way less.

Please talk about it in classroom.


Add docker file for application distribution

Dockerfile will have to download latest release of Factorio server manager.  Then download headless server files and extract to a directory.  Dockerfile will specify ports for the Factorio game server and UI server.  Launch command will start Factorio Server Manager in order to allow user to start Factorio server from the UI.

#8 Linking pull request.

Would be interesting if the updater could be integrated into this docker image/server somehow.
https://github.com/narc0tiq/factorio-updater
Its currently used by https://github.com/Bisa/factorio-init

I'm not sure if the auto updater is actually needed. The container from #8 exposes mods and savegames as volumes. Once a new factorio version is released, you can basically just change the version in the Dockerfile, rebuild the image and run a new container with volumes mounted to the same place than the last one.
If you want to make it pretty, use a data-only container for mods and saves volumes.
Factorio update would be done in... I guess 4 simple commands?

Once a new factorio version is released, you can basically just change the version in the Dockerfile, rebuild the image and run a new container with volumes mounted to the same place than the last one.
Yeah I get that.  I suppose one of the benefits of the web ui though is I can allow my friends to manage saves and mods without me having to manually do so.  It would be nice if they could also update the factorio version from the web ui.

It now occurs to me that this is really a feature request that doesn't necessarily relate to this docker issue.

Yeah an update feature could be implemented in the UI.
It would only have to download the latest Factorio binary and replace it with the existing one.


Introduce an img2bricks script that converts a bitmap to a TikZbricks wall

Here's something you're welcome to include in TikZbricks: a Python script that reads a bitmapped image (in any of a variety of formats) and produces a LaTeX document that uses TikZbricks to render the image as a wall.  This is a lot easier than trying to produce images like the following by hand:

Wow! That's completely amazing! Thanks a lot!


data: StarKnightt

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Looks good, thanks 🎉
I have added tags, but where are my tags?

Hey StarKnightt, don't worry, your tags will be shown once this PR is merged and deployed.

Hey StarKnightt, don't worry, your tags will be shown once this PR is merged and deployed.

Thank you


.NET Core 2.1 SignalR reconnect from .NET Client 1.0.2 Closed not called

I am using .NET Client for SignalR 1.0.2.
I am trying to automatically reconnect when I lost connection to server.
My Connection closed method is never called even if I shutdown server completely.
The code is like this:
 private async Task<bool> OpenSignalRConnection()
        {
            Log.Information("Creating SignalR connection");
            SignalRConnection = new HubConnectionBuilder()
           .WithUrl(BaseUrl + "/hubs/integrationserver", options =>
           {
                options.Headers.Add("Authorization", "Basic " + Header);
           })
           .Build();

            SignalRConnection.On<string, string>("ReceiveMessage", (entityName, json) =>
            {
                var intSrvArgs = new IntSrvEventArgs
                {
                    EntityName = entityName,
                    Json = json
                };
                _entityAddedUpdated?.Invoke(this, intSrvArgs);

            });

            await SignalRConnection.StartAsync();
           // **here I am subscribing to Closed event**
            SignalRConnection.Closed += SignalRConnection_Closed;
            return true;
        }

And then code for closed:
 private async Task SignalRConnection_Closed(Exception arg)
        {
            Log.Information("Connection is closed");
            await SignalRConnection.StopAsync();
            await SignalRConnection.DisposeAsync();
            TimeSpan retryDuration = TimeSpan.FromSeconds(30);
            DateTime retryTill = DateTime.UtcNow.Add(retryDuration);

            while (DateTime.UtcNow < retryTill)
            {
                bool connected = await OpenSignalRConnection();
                if (connected)
                {
                    Log.Information("Connection Re-Created");
                    return;
                }
            }
        }

Connection Closed is never called.
Does someone have a example of proper way to reconnect from C# Client?

Can you collect client and server logs as described in the Diagnostics Guide? In particular, the logs from around the time you shut down the server would be best.
Also please include the following information as requested by the Issue Template:

The Server you are using (Kestrel/HttpSysServer/IIS/IIS Express/Azure Web App/etc.):
The Operating System on the Server (Windows/Linux/macOS):
The Operating System on the Client (Windows/Linux/macOS):

The Server: IIS 8
Operating system on server: Windows Server 2016
Operating system on client: Windows 10
Can you point us to the article what is the proper way to implement reconnect from C# client?
It seams that this is impossible to do in this version of SignalR?

There's no article at the moment (see https://github.com/aspnet/Docs/issues/6757). There's a sample in JavaScript available here: https://github.com/davidfowl/UT3/blob/dac409886c1bb7aec7c150b74d4ce9a3e246f03c/UTT/wwwroot/js/utt.js#L141-L153
Your logic is mostly correct, however, you should not call DisposeAsync until you are completely finished with the connection and do not intend to reconnect. Just calling StopAsync is sufficient to clean up per-connection resources.

@anurse I managed to implement my own version which works correctly on .NET Client.
I wrote a blog post about it https://www.radenkozec.com/net-core-signalr-automatic-reconnects/
so if someone has a similar problem it can check out the code in the blog post.
Thanks.

The HubConnection is reusable so your implementation isn't quite the recommended way. If you take a look at the link @anurse provided you'll see the HubConnection is created once for the client and any callbacks (.on, close, etc.) are applied once so you don't have to keep re-registering for callbacks.
The link is for the TS client, but the implementation should behavior very similarly to the .NET client.

@BrennanConroy Thanks for feedback. I will improve my code to re-use HubConnection.


GTRepositoryCloneOptionsCheckout are missing

@tiennou, we have lost GTRepositoryCloneOptionsCheckout constant — it's declared in the GTRepository.h file, but nowhere else, so if any third-party code attempts to use it, we get a link error saying it's not defined anywhere. Not sure if the relevant code is also gone or substituted by GTCheckoutOptions struct.

IIRC I removed it in favor of some other option. If that's the case, it can go away.


MatSpinner making scroll bars bounce

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/fork/components-issue
https://stackblitz.com/edit/angular-ohvkwv
Steps to reproduce:

Create a spinner
Place in an element with overflow: auto

Expected Behavior
What behavior were you expecting to see?
See the mat spinner, spinning, inside a div.
Actual Behavior
What behavior did you actually see?
The spinner spins, but the div has scroll bars bouncing around.
Fix (?)
Playing with the CSS, it seems like this can be fixed once and for all (I keep hitting this all the time) if:

The spinning animation is moved from the host to the actual svg
The host is given the style overflow: hidden

Environment

Angular: "8.0.0"
CDK/Material: "8.1.4"
Browser(s): Version 76.0.3809.100
Operating System (e.g. Windows, macOS, Ubuntu): Debian GNU/Linux rodete

This happens because the spinner actually rotates:

In its rotated position, it's larger than its container. Any fix here will need to ensure that it doesn't cause any breaking layout changes, potentially by making the actual spinning portion position: absolute.
As a temporary workaround, you can increase the size of the container either via height or padding.


check problematic lexemes and orthography

Okay, the final step, to run you through our workflow, @Maunus, is to convert your specific orthographies to IPA.
Step 1: as our format does not allow to have comments in the form itself, we have an automated way of identifying those. I have written them in the file etc/lexemes.tsv. You have the form, a description o fthe error, and in second position a question mark. There, the form without comment (without modifying it further) needs to be provided. Basically, this is just copy-pasting and deleting the PUA, SUA (similar to what you did in the wordlist.tsv file, although this file is automatically generated and will be overwritten, so it should not be edited now).
Step 2: in the file etc/orthography.tsv, I have automatically assembled a first conversion of your orthography to plain IPA (which will also segment the sounds automatically). Easiest cases are all cases with y, where the IPA equivalent is j. But open questions remain: geminates should be written with a length marker, not with two consonants, same for long vowels, etc. The file has been automatically generated and contains already a lot of suggestions.
Let me know, once you have corrected the cases, then I'll run the code again, and you'll see that we may even align the data.

I will take a look. I already corrected some segmentation issues in the main file where kw was segmented as k w and tl as t l  for example - and where vowel and vowel/seminvowl sequences were all interpreted as diphthongs. There is also a difference between actual geminates and double consonants.

How do I correct it? For example hw and lw are consonant sequences not phonemes (same with several others).

Another set of difficult ones are the vowels with tone marks and the vowels with glottalization in Cora (o'o, u'u etc.) I think they should ideally be considered a single long vowel with glottalization.

Yes, I saw this. The new orthography is better for this purpose, as it is independent of the actual data, and you only correct each segment once. If segment combinations are not found there, you should add them in an extra row (tl, for example), and provide an IPA equivalent (kw is probably k+superscript-w, right?)

if you see "lw" proposed as one sound, but you want to have it as two, you can either delete the line, or you can write "l w" (with space) in the IPA column.

a glottalized vowel in IPA should be written with a glottalization mark (see here, our reference list of permissible IPA sequences).

So oˀ for example, with length marker if it is long.

Ok, how about tone? Also is the verbal description strictly necessary? With the sequences it becomes complicated.

Can I basically delete all the lines that are sequences?

Hmm, some of them are ambiquous, so kw can be either /kw/ or /kʷ/ and /ty/ can be either /tʲ/  or /tj/. And acute accent can be tone or accent depending on the language.

Also sometimes ai is a diphthong and sometimes a sequence depending on language (and sometimes depending on the word).

We need the first two columns, nothing more. The other columns are a
reference, so you unerstand what the computer makes of the sounds it is
given. So you can see that "y" is interpreted as a vowel, although it is
a consonant. This helps you to correct it. You can also see that we
autocorrect errors resulting from wrong IPA symbols. You write a:, but
you use the colon ":", although it is anohter Unicode: "aː". This all is
for consistency and we'll double check. By now, however, just the first
two columns need to be provided.

we recommend to annotate tone properly, not on the vowel, by using chao
numbers, but you can leave the tone on the sounds as well, it will then
be rendered as "XXX vowel with high tone". You an also write í/i, so you
say: í is the i with tone in my data, but the computer should only read
the "i", as this is the thing without tone that the computer will accept.

I prefer you tell explicitly that they are two sounds, by inserting a "
" (space).

Well if things are ambiguous, it already shows why this is in fact
important to do, and why it is useful to use IPA as a reference and not
use original orthographies. For now, you could provide two lines and
mark the language in the column for "languages". So we can see if we can
just disambiguate them,

For dipthongs, etc., I recommend: if you have ambigious words, count
them in your data. But you place  If there are many, place them in
"lexemes.tsv", where you can convert them. So you take the value in yoru
original cell, and provide the form that we should use (unsegmented).

Also sometimes ai is a diphthong and sometimes a sequence depending on language (and sometimes depending on the word).

Take the word that is ambigious and uses ai not as a dipthong from your original spreadsheet (wod document). Copy-paste it into "lexemes.csv" (in etc/). Then provide a replacement, where you add a dot to to the dipthong, like a.i. This will do the trick.

Same can be done for k.w.

Unfortunately for a few of the languages the sources are old enough that they don't give a good phonological analysis - for example we don't really know if Huichol and Cora has tone, and how it works if they do. And it is not consistently noted. Same for questions of vowel sequences and diphthongs etc. That is why I have used the original ortography in the data (also because I wasn't planning to do any phonological analysis).

Ok.

Oh, should I always add a period instead of a space when I reinterpret sequences? Does it screw up the alignment if I add spaces between phonemes in the second row?

Second column (cell), right? Alignmetns depend on the segmentation. Your decisions have a direct impact on this.  But you best learn that when you see the alignments. So for now, I say it does not really make a big difference, as long as it is consitent. And uncertainty doesn't bother us: distinctivity counts in structural lingusitics, right? So one should not lose distinctivity but if something is mis-interpreted, we can live with that: original data are there, an interpretation can be revised, etc.
So I'd say: for a first test here, we need a pragmatic first version, so you see the principle of the orthography profiles. You can even test it yourself. Just go to digling.org/calc/profile/, paste the current profile (file orthography.tsv) in the text field, press okay, and you can type in text from your data and see how it converts.

Is there a way I can test it on the entire document (i.e. producing a new version of wordslist.tsv) ? I think I have got it now and want to see what it produces.

Do you want to run the full workflow? That would require:

having python3 (version 3.5 and higher) installed
having access to a terminal application (on Windows, you can run Python now also from the terminal, but you will need fiddle a bit around with it, on Mac it is easier, but they have often broken Python implementations)
being prepared to learn how to make a virtual environment, to make sure that you only use the most appropriate versions for the code
installing git (as a major requirement for getting a specific version of a specific piece of code, again, easier on Mac)

If it's for a next checking, I can also run the code again and point you to some things I observe, etc.

Ah, ok, I didn't realize all that would be necessary, that is perhaps a bit more than I could realistically do myself.


Font size different in different terminals even though the same in points

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.17128.1] (Swedish). I use most updated (using apt-get update and dist-upgrade) Ubuntu from Store.

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

WSLtty version 1.8.4 has font size 9 pt and Cmd.exe has font size 14, but they look the same size on screen.

What's wrong / what should be happening instead:
I don't know if WSLtty or Cmd.exe is right about font sizes, but I think a font size in points should be the same on screen in different programs.

I learned that the font-size in Cmd.exe is measured in pixels -- not points, but it doesn't say that in the GUI.

Pixels is right! This is by design, but look for changes in font handling for Windows Terminal.

Were there ever any changes done to this? For ages I've been using Consolas size 10 (for things like Notepad) which almost perfectly matches size 14 in the Windows console. Lately though, console size 16 has started to grow on me, but in Windows Terminal it's simply not possible to achieve the equivalent appearance. Especially in bold it looks entirely different.

is there a way to do the old "by pixel" font sizes like in cmd but in windows terminal?


Spaces in route parameters

Describe the bug
Spaces in route parameters are encoded as plus signs.
To Reproduce
    @Test
    public void spacesInRouteParamArePercentEncoded() {
        HttpRequest<?> request = Unirest.get("https://en.wikipedia.org/wiki/{pageName}")
                .routeParam("pageName", "Mosaics of Delos");
        System.out.println(request.getUrl());
        Assertions.assertTrue(request.asEmpty().isSuccess());
    }

Expected behavior
Spaces in route parameters must be encoded as %20 sequence.
Screenshots
Not applicable.
Environmental Data:

Java 1.8
Unirest 3.4.00

Additional context
The unirest uses URLEncoder class to encode route parameters, but it should be used for HTML form encoding, not for path encoding.

fixed in 3.4.02


Throwable in extended fallback is null for timeouts

Hi,
I've been using the extended fallbacks made in #828 (which are great) and I've seen that when the execution times out the Throwable is null as the execution didn't actually fail. It would be nice to have some kind of TimeoutException there to know the real reason and don't have to dead with nulls. Looking at the code, probably the same thing happens with rejected executions.
Thanks!

Is this specific to hystrix-javanica, or are you using Hystrix directly?

hystrix-javanica

@dmgcodevil Could you take a look at this one also, please?

Yes, I'll take a look
On 16 Nov 2015 12:31 p.m., "Matt Jacobs"<EMAIL_ADDRESS>wrote:

@dmgcodevil https://github.com/dmgcodevil Could you take a look at this
one also, please?
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/Hystrix/issues/974#issuecomment-157110552.

@mattrjacobs btw, it largely relates to hystrix core, to get exception javanica uses getFailedExecutionException(), do you have any clue why it returns null in the case of timeout error ?

Thanks for taking a look, @dmgcodevil.  I'll dive in and see what's happening in hystrix-core.

@victormferrara The existing semantics here are fairly subtle.  The getFailedExecutionException() only refers to exceptions that arose during the execution of the work in the HystrixCommand / HystrixObservableCommand.
So in the timeout case, the execution of the command never threw a timeout, the surrounding Hystrix machinery did when it timed out that work.  Likewise, in a rejection case, the execution of a command never happened, so there is no execution exception to report.
What problem are you trying to solve with this value?  I know that there are other ways to query the command (isResponseTimedOut() / isResponseRejected()) that should give you the same information without giving you the actual Exception instance.

@mattjacobs, he is complaining because javanica passes null in extended
fallback method that is really annoying and can facilitate bogus code and I
agree with it. So the question is what we can do in order to avoid passing
null in fallback if a command fails because of timeout or rejected. I think
I can use the methods that you suggested and create exception with
corresponding text and pass it to fallback using additional argument. So
your answer helped, I guess
On 17 Nov 2015 4:46 p.m., "Matt Jacobs"<EMAIL_ADDRESS>wrote:

@victormferrara https://github.com/victormferrara The existing
semantics here are fairly subtle. The getFailedExecutionException() only
refers to exceptions that arose during the execution of the work in the
HystrixCommand / HystrixObservableCommand.
So in the timeout case, the execution of the command never threw a
timeout, the surrounding Hystrix machinery did when it timed out that work.
Likewise, in a rejection case, the execution of a command never happened,
so there is no execution exception to report.
What problem are you trying to solve with this value? I know that there
are other ways to query the command (isResponseTimedOut() /
isResponseRejected()) that should give you the same information without
giving you the actual Exception instance.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/Hystrix/issues/974#issuecomment-157519144.

@mattrjacobs yeah, it's exactly what @dmgcodevil explained. Thanks!

hystrix-core itself is generating these Short-Circuit and Timeout exception instances.  Are we missing a feature where hystrix-core exposes these exceptions, so javanica does not need to?

@mattrjacobs it could be better if we had an abilitty to get such exceptions within a command

@dmgcodevil Agreed.  I just added #998 to add this to hystrix-core.  Once it's there, hystrix-javanica can leverage this.  Will note the PR in these comments so you can review

Now merged via #1008 / #1003

This should be fixed in #1167


Does not work on mobile.

As title says it all, tried on Chrome Android but nothing happened after clicking on one of the providers to sign in.

Works fine on Chrome 47.0.2526.83 Android 6.0

@motss which version are you using so I can reproduce? I did not test on Android, so it's a good opportunity! Thanks for the report!

Tested  and not working on my device with Android 5.0 on both Chrome Dev 48.0.2564.36 and Chrome Stable 47.0.2526.83

Thanks, I'll try to find the origin of the problem!


Allow developers to customize Android notifications text

What's New?

Where added two properties to the ScreenRecordingOptions called SetNotificationContentTitle and SetNotificationContentText
Now users can set those properties to customize the notification text for android.

Related Issue
Fixes #8
Visuals
https://github.com/jfversluis/Plugin.Maui.ScreenRecording/assets/23615129/a4da1b10-6b94-4639-aa2e-8b2ddc308dc4

Also, did you make the screen recording in this post with this plugin?! :P

Hahahahaha, daaammm, I forgot to use it to do that, I used the Sniping Tools
PD: All comments successfully completed

Couple of minor things... Thank you for this!

hoping this one won't be the last one, I think there are some more issues that I could handle

i cloned you repo, but i can not push my branch to create a PR

i cloned you repo, but i can not push my branch to create a PR

But what do you really try to do man? do you want me to change something on my PR? or you said you want to start your PR from my repo ??

Thank you for your contribution! Here is a virtual high five! ✋

Thank you for your contribution! Here is a virtual high five! ✋

✋(see you on the next one)


[BUG] v0.8.1 release manifest is wrong

Manifest points to ghcr.io/keptn/lifecycle-operator:klt-v0.8.1 and that is invalid. It should be ghcr.io/keptn/lifecycle-operator:v0.8.1
The name changed from klt-manifest.yaml to manifest.yaml (see #1699)

I updated the manifest, but in the future we will only release Helm Charts and the manifest installation won't be possible anymore.


[BUG]Tabular Classification Error

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Local
Interface Used
UI
CLI Command
No response
UI Screenshots & Parameters

Error Logs
FileNotFoundError: [Errno 2] No such file or directory: 'python'
raise child_exception_type(errno_num, err_msg, err_filename)
File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 971, in init
process = subprocess.Popen(cmd, env=env)
File "/usr/local/lib/python3.10/dist-packages/autotrain/utils.py", line 55, in run_training
training_pid = run_training(params, task_id, local=True, wait=self.wait)
File "/usr/local/lib/python3.10/dist-packages/autotrain/backends/local.py", line 11, in create
return runner.create()
File "/usr/local/lib/python3.10/dist-packages/autotrain/project.py", line 63, in create
job_id = project.create()
File "/usr/local/lib/python3.10/dist-packages/autotrain/app/ui_routes.py", line 624, in handle_form
return await dependant.call(**values)
File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 191, in run_endpoint_function
raw_response = await run_endpoint_function(
File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 278, in app
response = await func(request)
File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 72, in app
await app(scope, receive, sender)
File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 53, in wrapped_app
raise exc
File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 64, in wrapped_app
await wrap_app_handling_exceptions(app, request)(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 77, in app
await self.app(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 297, in handle
await route.handle(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 776, in app
await self.middleware_stack(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 756, in call
await app(scope, receive, sender)
File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 53, in wrapped_app
raise exc
File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 64, in wrapped_app
await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/exceptions.py", line 65, in call
await self.app(scope, receive, _send)
File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 164, in call
raise exc
File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 186, in call
await self.middleware_stack(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/starlette/applications.py", line 123, in call
await super().call(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/fastapi/applications.py", line 1054, in call
return await self.app(scope, receive, send)
File "/usr/local/lib/python3.10/dist-packages/uvicorn/middleware/proxy_headers.py", line 70, in call
result = await app( # type: ignore[func-returns-value]
File "/usr/local/lib/python3.10/dist-packages/uvicorn/protocols/http/httptools_impl.py", line 399, in run_asgi
Traceback (most recent call last):
ERROR: Exception in ASGI application
INFO | 2024-06-01 01:36:05 | autotrain.commands:launch_command:387 - {'data_path': 'autotrain-c41wh-jf5zc/autotrain-data', 'model': 'xgboost', 'username': 'uisikdag', 'seed': 42, 'train_split': 'train', 'valid_split': 'validation', 'project_name': 'autotrain-c41wh-jf5zc', 'token': '*****', 'push_to_hub': True, 'id_column': 'autotrain_id', 'target_columns': ['autotrain_label'], 'categorical_columns': None, 'numerical_columns': None, 'task': 'classification', 'num_trials': 10, 'time_limit': 600, 'categorical_imputer': 'most_frequent', 'numerical_imputer': 'median', 'numeric_scaler': 'robust'}
INFO | 2024-06-01 01:36:05 | autotrain.commands:launch_command:386 - ['python', '-m', 'autotrain.trainers.tabular', '--training_config', 'autotrain-c41wh-jf5zc/training_params.json']
INFO | 2024-06-01 01:36:05 | autotrain.backends.local:create:8 - Starting local training...
Saving the dataset (1/1 shards): 100%|██████████| 2/2 [00:00<00:00, 1136.82 examples/s]
Saving the dataset (1/1 shards): 100%|██████████| 2/2 [00:00<00:00, 1190.72 examples/s]
Saving the dataset (0/1 shards): 0%| | 0/2 [00:00<?, ? examples/s]
Saving the dataset (1/1 shards): 100%|██████████| 8/8 [00:00<00:00, 4346.43 examples/s]
Saving the dataset (1/1 shards): 100%|██████████| 8/8 [00:00<00:00, 4562.13 examples/s]
Saving the dataset (0/1 shards): 0%| | 0/8 [00:00<?, ? examples/s]
INFO | 2024-06-01 01:36:05 | autotrain.app.ui_routes:handle_form:590 - Column mapping: {'id': 'id', 'label': ['target']}
INFO | 2024-06-01 01:36:05 | autotrain.app.ui_routes:handle_form:589 - Task: tabular_multi_class_classification
INFO | 2024-06-01 01:36:05 | autotrain.app.ui_routes:handle_form:483 - hardware: local-ui
Additional Information
The dataset
id,category1,category2,feature1,target
1,A,X,0.3373961604172684,1
2,B,Z,0.6481718720511972,0
3,A,Y,0.36824153984054797,1
4,B,Z,0.9571551589530464,1
5,B,Z,0.14035078041264515,1
6,C,X,0.8700872583584364,1
7,A,Y,0.4736080452737105,0
8,C,Y,0.8009107519796442,1
9,A,Y,0.5204774795512048,0
10,A,Y,0.6788795301189603,0

requires python 3.11 to solve the problem

please share problem so i can solve it


Possiblity to make text information in other color

Anyone interested to be able to make the text information surrounding the symbol in another color then the default icon frame color? If so let me know, I have some ideas but I don't want to implement options that won't be used.

This can now be done using the infoColor property.


Allow multiple select queries

mainly to reduce the number of HTTP requests by bundling the results in a single JSON object

maybe not an issue