Contribute to Open Source. Search issue labels to find the right project for you!

Updating records with latest information

US-CBP/GTAS

The system isn’t updating tables with the most recently received APIS information. i.e. if a second APIS is received with updated middle name, it is not reflected in the database.

<!— @huboard:{“order”:3.4545188612881303e-11,“milestone_order”:4.428393788681684e-09} –>

Updated 14/12/2017 21:59

Analysis of old targets that were associated with individual data collection records

mercycorps/mcta

We have a number of targets associated with individual data collection records, that I’ll refer to as OLD_TARGET. We no longer display the individual targets in TolaActivity, but need to figure out what to do with their values, if anything.

The .csv file is attached. OLD_PERIODIC_TARGETS.xlsx

For an example of the output we need from this ticket, please see https://docs.google.com/a/mercycorps.org/document/d/1Uvvu-51Qf2UzSR7oqJ-GaN5a3RLdYJ6d-AXns48tCmQ/edit?usp=sharing

These are the questions we need to answer: 1. How many data records have old_targets associated with them? (Column B.) 1.1. How many indicators are these records associated with? 1.2. How many programs are these records associated with? 2. In what percentage of cases is the OLD_TARGET value identical to the LOP target? (Column B equals column F.) 2.1. These are the records we can ignore, since there is nothing to convert into periodic targets. 3. In what percentage of cases is the OLD_TARGET value identical for every record associated with the indicator? 3.1. These are records that might present opportunities for batch-processing.

Updated 14/12/2017 18:43

neo4j | keylines

US-CBP/GTAS

https://neo4j.com/blog/keylines-graphing-github/

<!— @huboard:{“order”:3.455900876117596e-11,“milestone_order”:4.4301654119184984e-09} –>

Updated 14/12/2017 18:37

Analysis of indicators: non-numeric entries for LoP target and baselines

mercycorps/mcta

We have two fields in the Indicators setup dialogue that we hope to change so that they only accept integers – no letters or special characters. We need to do some analysis on existing indicators to figure out how many have non-integer values that need to be updated.

The .csv file is attached. It includes all indicators currently in the system: indicators.xlsx

For an example of the output we need from this ticket, please see https://docs.google.com/a/mercycorps.org/document/d/1Uvvu-51Qf2UzSR7oqJ-GaN5a3RLdYJ6d-AXns48tCmQ/edit?usp=sharing

These are the questions we need to answer: 1. How many indicators have a Baseline entry that is not an integer? 1.1. What are the formatting conventions of these non-integer entries? (See examples in notes.) 1.2. How many indicators use each of these formats? 2. How many indicators have a LOP target entry that is not an integer? 2.1. What are the formatting conventions of these non-integer entries? (See examples in notes.) 2.2. How many indicators use each of these formats?

NOTES 1. Here are some examples of formatting conventions: 01, 40%, number and unit of measure, N/A, description of calculation, $50,000, 0.2. 1.1. The goal of cataloguing formatting conventions is to consider how we could batch-convert some of these. For example, the convention $50,000 could be converted to 50,000 in the LOP target field and “currency” in the unit of measure field. 2. The goal of counting the frequency of each formatting convention is to identify those with the highest frequencies that would be most worthwhile to address with batch processing scripts and such.

Updated 14/12/2017 18:26

Create factory "Bildung für sozial benachteiligte Kinder in Deutschland" and assign to new users

toladata/TolaActivity

Story

We need to have a new Project for German demo users, so they can test Activity.

Current ID: 65 Name: Bildung für sozial benachteiligte Kinder in Deutschland

Check database to see it’s structure and subobjects.

Acceptance criteria

GIVEN I look to loadinitialdata command THEN I see a new workflowlevel1 factory called “Bildung für sozial benachteiligte Kinder in Deutschland” AND other factories depending on it

GIVEN I register as a new Demo user THEN I am added to this new project

Updated 14/12/2017 15:00

Research and implement an alternative to Glyphicons

mercycorps/mcta

As it turns out, our icon font is incompatible with open source licenses – even the paid version. Glyphicon explicitly says, “You must not include icons in open-source projects, since this license is not compatible with most of the open-source licenses.”

See: See http://glyphicons.com/license/

I did a very cursory search and found Fontawesome – http://fontawesome.io/license/ – fully open source and GPL friendly

GitHub also has some resources we could check out: https://github.com/topics/icon-fonts

Since we don’t use tons of icons in TolaActivity, it will (hopefully?!) not be too painful to swap out our icon font service and update our icons.

Updated 14/12/2017 18:47

Collected data form: Display periodic targets

mercycorps/mcta

Story: After I configure periodic targets, the target names appear in Collected Data records form.

ACCEPTANCE CRITERIA The following criteria need to be tested for all varieties of periodic targets we release. 1. After I save periodic targets for an indicator, those targets appear in the Collected Data form as options in the Periodic target menu. 2. Only the name of the target is included. We do not want to display the target values. (They were presented in an earlier iteration of the design, and we received feedback that seeing the target value is confusing and unnecessary in this context.) 3. The menu syntax is as follows:

STILL WORKING ON THIS ONE!!!

Updated 14/12/2017 18:47

Rule Hit / WL hit bug

US-CBP/GTAS

If a passenger hits on a rule hit and a WL, both flags are displayed on the passenger grid, but the case doesn’t include the WL hit, and the Pax details does not show the WL hit.

<!— @huboard:{“order”:3.456592090851828e-11,“milestone_order”:4.431051489302536e-09} –>

Updated 14/12/2017 06:09 1 Comments

Indicators > Targets: Select target frequency option and sub-options

mercycorps/mcta

Story: When I select a target frequency option, the system asks me for any additional details it needs to generate the appropriate periodic targets.

ACCEPTANCE CRITERIA

  1. In the Targets tab, underneath the Baseline field, is a Target frequency selection menu. 1.1. I can type the first character (or ideally multiple characters) to quickly select the option I want. 1.2. Target frequency is a required field.
  2. The menu contains 8 target frequency options: Life of Program (LoP) only; Midline and endline; Annual; Semi-annual; Tri-annual; Quarterly; Monthly; and Event.
  3. Depending on the option I select, the system either accepts the field as complete or generates additional required fields.
  4. When I select Life of Program (LoP) only, the system accepts the target frequency field as complete. 4.1. Please spell out the full phrase followed by the acronym – “Life of Program (LoP)” – because the acronym is unfamiliar to many users, especially newer employees.
  5. When I select Midline and endline, the system accepts the target frequency field as complete.
  6. When I select Annual, the system requests the following: 6.1. First annual period begins: Month and year 6.2. Number of : This field is auto-populated with a 1. 6.3. All of these fields are required. If I leave one empty, I’m prompted to “Please complete this field.”
  7. When I select Semi-annual, the system requests the following: 7.1. First semi-annual period begins: Month and year 7.2. Number of semi-annual periods: This field is auto-populated with a 1. 7.3. All of these fields are required. If I leave one empty, I’m prompted to “Please complete this field.”
  8. When I select Tri-annual, the system requests the following: 8.1. First tri-annual period begins: Month and year 8.2. Number of tri-annual periods: This field is auto-populated with a 1. 8.3. All of these fields are required. If I leave one empty, I’m prompted to “Please complete this field.”
  9. When I select Quarterly, the system requests the following: 9.1. First quarterly period begins: Month and year 9.2. Number of quarters: This field is auto-populated with a 1. 9.3. All of these fields are required. If I leave one empty, I’m prompted to “Please complete this field.”
  10. When I select Monthly, the system requests the following: 10.1. First monthly period begins: Month and year 10.2. Number of months: This field is auto-populated with a 1. 10.3. All of these fields are required. If I leave one empty, I’m prompted to “Please complete this field.”
  11. When I select Event, the system requests the following: 11.1. First event name: Open text field 11.2. Number of events: This field is auto-populated with a 1. 11.3. All of these fields are required. If I leave one empty, I’m prompted to “Please complete this field.”
Target frequency options Illustration
Frequency options menu image
Life of Program (LoP only) image
Midline and endline image
Annual annualconfig
Semi-annual semiannualconfig
Tri-annual triannualconfig
Quarterly quarterlyconfig
Monthly monthlyconfig
Event image
Updated 15/12/2017 00:11

Indicators: Add --All-- option to Programs menu

mercycorps/mcta

Affects: The Programs filter menu at the top of the Indicators page.

Problem: 1. Go to indicators 2. Open the Programs filter menu at the top of the page. 3. Filter on a program. 4. Now try to get the full list of indicators back. 4.1. Expected: I can select –All– in the Programs filter menu, just like I can in the Indicators menu next to it. (This is a common convention in many of the filter menus in the app.) 4.2. Observed: There is no –All– option, so I have to reload the Indicators page to get the full list.

Requested fix: Add the –All– option to the Programs filter menu

scrap

Updated 14/12/2017 18:47

Indicator dialogue > Targets > Life of Program field is required

mercycorps/mcta

User stories: 1. When configuring an indicator, I should be required to enter a Life of Program (LoP) target because it is an essential value for calculating progress in indicator tracking reports. 2. When I enter a LoP target, the system should only accept a numeric value so that it can be used for calculations. 3. As a new user to Tola, I should not be expected to know what LOP means.

Background: A LOP field already exists in the Targets tab, but it is optional and accepts non-numeric values. LOP is not a familiar acronym outside of Tola.

ACCEPTANCE CRITERIA 1. The Life of Program target is required. 1.1. The field label is “Life of Program (LoP)” instead of “LOP”. 1.2. An asterisk identifies the field as required. 2. The field only accepts a numeric value. It does not accept letters or special characters such as %. 2.1. If you attempt to save with a non-numeric value, you receive a prompt near the field, “Please enter a number.” 2.2. Any existing Life of Program value that does not meet the criteria is preserved. 2.3. However, if you attempt to edit a non-numeric LoP value, you are only allowed to replace it with a numeric value. 3. If you attempt to save without completing the Life of Program, you are prompted: “Please complete this field.”

loprequired

Updated 14/12/2017 18:47

Pull currency names from some data source to have display names for all crypto currencies without hard coding

balancemymoney/balance-open

Right now we have some hard coded but there are way too many. We should have a lookup table in the database where we pull this info. Or potentially pull and cache it in the backend and pull down a data file like for exchange rates.

<!— @huboard:{“order”:36.9814911042491,“milestone_order”:36.92238540451231} –>

Updated 13/12/2017 23:43

Collected Data form: Update two labels

mercycorps/mcta

Affects: Collected Data form

ACCEPTANCE CRITERIA 1. The form field “Date collected” is changed to “Date submitted”. 1.1 Why? The original label is confusing because it implies that all data was collected on a single day. This often is not the case. 2. The form field Periodic target is changed to Measure against target. 2.1. Why? Not all targets are periodic. The original form label is confusing if you’re using midline, endline, or event-based targets that are not defined by date ranges. 3. The form field “Achieved” is changed to “Actual value”. 3.1 Why? “Achieved” is a confusing term in this context because it implies success or analysis of progress towards the LoP. “Actuals” is a more common term used in reports – i.e. target versus actual values.

collecteddataupdates

Updated 14/12/2017 21:52

Indicator dialogue > Targets tab: Add evidence to a baseline

mercycorps/mcta

Prioritization note: This is a lower priority feature. The need was inferred from conversations regarding best practices in associating evidence with data.

User story: When I identify a baseline value for my indicator, I want to attach evidence (such as a baseline survey) so that future reviewers know how we arrived at that number.

Background: We encourage teams to associate evidence with all of their indicator data. But currently it’s not possible to associate evidence with a baseline value. This solution allows data collection records to be associated with a baseline.

ACCEPTANCE CRITERIA 1. Next to the Baseline text box is a button labeled Add evidence. 1.1. The button has the same styling as the original Form Help / Guidance button. (We’re repurposing that style for strong calls to action.) 2. The link pops up a modified version of the Collected Data form. The differences are as follows: 2.1. The name of the form is Baseline Evidence instead of Collected Data. 2.2. The label Date collected is renamed Date submitted. We’re making this change to be consistent with Issue #10 . 2.3. There is no Periodic Targets dropdown, because a baseline does not have a target value associated with it. 2.4. The Achieved field is replaced with a non-editable field called Baseline that mirrors the baseline value in the Targets tab. (The baseline is your starting point, so there is no “achievement” to capture in this record. The purpose of the form is simply to associate evidence with your baseline value. We include that value for helpful reference.) 3. After saving the Baseline Data form, the following occurs: 3.1. The system gives you a success message, “Success: Your baseline data was saved. You can find it alongside other data records for this indicator.” 3.2. The baseline data record appears on the Indicators page, treated exactly like all of the others. 3.3. Opening a baseline data record from the Indicators page takes you back to the modified Baseline Data form, not the ordinary Collected Data form. 4. It is possible to associate multiple data records with your baseline, but you can only do this from the Targets tab. You cannot associate data with a baseline by clicking New Data on the Indicators page.

baselineevidence

Updated 14/12/2017 18:47

Indicator dialogue > Targets tab: Baseline field is required

mercycorps/mcta

User stories: 1. When I’m setting up an indicator, I should be required to enter a baseline value so that this important context is displayed in my indicator tracking reports. 2. When I enter a baseline, the system should only accept a numeric value so that it can be used for calculations.

Background: The Baseline field already exists in the Targets tab, but it is optional and accepts non-numeric values.

ACCEPTANCE CRITERIA 1. The Baseline field is required. 1.1. An asterisk identifies the field as required. 2. The Baseline field only accepts a numeric value. It does not accept letters or special characters such as %. 2.1. If you attempt to save with a non-numeric value, you receive a prompt near the field, “Please enter a number.” 2.2. Any existing baseline value that does not meet the criteria is preserved. 2.3. However, if you attempt to edit a non-numeric baseline value, you are only allowed to replace it with a numeric value. 3. If you attempt to save without completing the Baseline field, you are prompted: “Please complete this field. An indicator can have a baseline value of zero.”

baselinerequired

Updated 14/12/2017 18:47

Indicator dialogue: Make existing Unit of measure field required and mirror it in the Targets tab

mercycorps/mcta

Story: When I’m setting up an indicator, I should be required to provide a unit of measure so that this important context is displayed in indicator tracking reports.

Background details: The unit of measure is essential context for setting up and tracking indicators. The field is already included in the Performance tab of the Indicators dialogue, but it is not required. We should keep the original field in place because it follows the logical sequence of the program planning templates to which users have become accustomed. We are also adding it to the Targets tab. The field should be required in both tabs, and editing the value in either tab will update the other.

ACCEPTANCE CRITERIA 1. Unit of measure field appears in the Targets tab as the first form field. 2. Unit of measure field is required in the Targets tab. 2.1. An asterisk identifies the field as required. 2.2. If you attempt to save without completing this field, you get a “Please fill out this field.” prompt. 3. Unit of measure field is required in the Performance tab. 3.1. An asterisk identifies the field as required. 3.2. If you attempt to save without completing this field, you get a “Please fill out this field.” prompt. 4. Whenever I update the Unit of measure field in either the Targets tab or the Performance tab and click Save, the value is updated in both places.

unitofmeasure_newfield

Updated 14/12/2017 18:47

Indicator dialogue: UI improvements

mercycorps/mcta

The following changes apply globally across all tabs of the Indicator dialogue.

User story: When I’m setting up my targets, I’m guided through the process with clear calls to action each step of the way.

Background: The UI design of the current Indicator dialogue does not afford clear calls to action. The strongest visual element is the Form Help/Guidance button, and there is no way to visually differentiate target setting actions from the act of saving the entire dialogue.

ACCEPTANCE CRITERIA 1. Indicator name appears at the top of the dialogue: It’s a general usability best practice to clearly communicate where you are in the system. If you momentarily step away from the task, it would be easy to lose track of which indicator you’re working on. 2. Indicator names are capped at three lines with a … if it runs over. (Indicators names can get quite lengthy. We want to show enough of the name to make it instantly recognizable, but not so much that it pushes the important contents of the page too far down.) 2.1 Title is formatted [Indicator type]: [Indicator name] 2.2 Font color is standard MC gray #94979C. 3. A new footer area appears at the bottom of the dialogue: The footer visually differentiates the “save this entire dialogue” action from target configuration actions taken inside the dialogue. 3.1 Footer has the same fill color and font treatment as the global “sticky footer” in TolaActivity, but it should not be sticky. 4. The Save button is more visually prominent than the Reset action: We do this by lengthening the button label to Save changes and making the Reset button more muted. 5. The help link is relocated to the new footer: Today’s Form Help/Guidance button dominates the dialogue and is awkwardly positioned near the X icon. Also, Form Help/Guidance is a cumbersome label that may not be intuitive to a non-technical audience. Your essential activity here is not to fill out a form; It’s to set up an indicator. 5.1 The heavy blue button is replaced with a simple text link. 5.2 The button is renamed Help.

indicatordialogueuiimprovements

Updated 14/12/2017 18:47

Umgang mit PR, lokal testen

BugBuster1701/docs

in der .bashrc

#  Fetch a github pull request from <remote> and check it out locally in a branch named <remote>-pr-<pr number>
function gitpr ()
{
    if [ -z "$2" ]; then
        echo "Usage: gitpr <remote> <pr number>"
    else
        git fetch $1 pull/$2/head:$1-pr-$2 && git checkout $1-pr-$2
    fi
}
# You are on a feature branch which has been merged upstream, so checkout master, blast the old branch and sync up.
function gitpr-done ()
{
    cb=$(git rev-parse --abbrev-ref HEAD) # parse the ID of the current branch
    git checkout master
    git branch -D ${cb}
    git pull --ff-only upstream master && git push origin master --no-verify
}

oder als alias, über id PR id:

git config --global --add alias.pr '!f() { git fetch -fu ${2:-upstream} refs/pull/$1/head:pr/$1 && git checkout pr/$1; }; f'

git config --global --add alias.pr-clean '!git checkout master ; git for-each-ref refs/heads/pr/* --format="%(refname)" | while read ref ; do branch=${ref#refs/heads/} ; git branch -D $branch ; done'

Pull ein Pull Request: git pr <id>

Alle PRs löschen, die mit git pr .. angelegt wurden: git pr-clean

Updated 09/12/2017 17:36

Müködési teszt

edemo/elovalasztok2018
  1. néhány (10-20) szavazat felvitele (legyen köztük hiteles magyar és másmilyen is). Kézzel kiértékelni és ennek eredményét összevetni a gép által kihizottal (minden szavazat és csak hiteles magyar szavazatra is)
  2. Ha eltétrés van akkor a program javítása és vissza az 1.re
  3. nagy mennyiségű (50.000 - 200.000) szavazat generálása és a kiértékelő algoritmus tesztelése, lefutás memória és idő igénye
  4. Ha nem megfelelő program/hw/konfiguráció módosítása és vissza az 1.-re
  5. több ember (5-10), több gépről egszerre dolgozva adjon le szavazatokat, modositson szavazatot, kérjen le eredményt. Reakció idők megfigyelése.
  6. Ha nem megfelelő akkor program/hw/konfiguráció modosítás és vissza az 1. -re

<!— @huboard:{“order”:6.993178673556712,“milestone_order”:0.9981018986707314} –>

Updated 06/12/2017 17:23

Improve Target framework selection

dotnet/project-system

When using Visual Studio 2017, I would like the ability to change the target framework of a project without restriction. Currently, Visual Studio limits the framework options given to a user based on the initial project type. Since I am able to now edit a *.csproj and save a change to the <TargetFramework> node, shouldn’t the GUI allow me to do that same?

When I create a new project targeting the netstandard1.5 target framework moniker, the dropdown is limited to variants of .NET Standard.

The .csproj targeting netstandard1.5

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard1.5</TargetFramework>
  </PropertyGroup>
</Project>

image

Likewise, if I change this in the *.csproj to target net461 for example - the options are again limited to Full .NET Framework listings.

The .csproj targeting net461

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net461</TargetFramework>
  </PropertyGroup>
</Project>

image

Finally, the same is true for netcoreapp2.0 - targeting .NET Core.

The .csproj targeting netcoreapp2.0

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>
</Project>

image

Updated 06/12/2017 22:15 2 Comments

Override User.internal_admin_user

mysociety/belgium-theme

(Bug not currently reproducible in production)

If the user does not already exist (which in production on a pre-existing site, it should do) a new one will be created and will fail validation, raising an ActiveRecord::RecordInvalid error during any attempt to access the Summary (main) page of the admin tool.

The overridden version needs to supply a value for province now that this is a required field so that the new user will pass the validation check allowing save! to work

Updated 06/12/2017 16:21 2 Comments

FOP data model correction

US-CBP/GTAS

Form of payment is stored at the PNR level. This is incorrect. A PNR can have a different form of payment for different flights–i.e. the first flight was misc. (bought on points) and the second was credit card. Right now only one FOP is stored.

<!— @huboard:{“milestone_order”:4.43725899525776e-09,“order”:6.921484566944501e-11} –>

Updated 05/12/2017 22:06

make sure model errors are handled properly

magwas/zenta-tools

<check title=“Model Errors” referencemodel=“Aquacore.rich” modelfile=“Aquacore.rich” modelbasepath=“//error” modelnamepath=“@type” modelvaluepath=“concat(//element[@id=current()/@element]/@name,‘ ’,@name)” modelerrorid=“$p1/object/error/@errorID” inputfile=“Aquacore.rich” inputbasepath=“//nonexistent” inputnamepath=“” inputvaluepath=“” inputerrorid=“$p1” errorURL=“concat(‘http://example.com/model.html#’,$p1)” errortitlestring=“zenta:modelErrorTitle($p1,$p4)” errordescription=“zenta:modelErrorDescription($p1,$p4)” iinputnamepath=“replace(replace(child::para,‘.{’,‘’),‘}.’,‘’)” /> </checks>

<!— @huboard:{“order”:0.9995001499650069,“milestone_order”:0.9988007796361366} –>

Updated 04/12/2017 13:45

wrapper around zentatools:verbatim

magwas/zenta-tools

Maybe the java function should be rewritten such that returns empty for empty

<xsl:function name="zenta:ifVerbatim">
    <xsl:param name="t"/>
    <xsl:if test="$t">
        <xsl:copy-of select="zentatools:fromVerbatim($t)"/>
    </xsl:if>
</xsl:function>

<!— @huboard:{“order”:0.9998000299960005,“milestone_order”:0.9991004498350495} –>

Updated 04/12/2017 13:41

includeFile property for folders

magwas/zenta-tools
    <xsl:template match="folder[property[@key='includeFile']]" mode="varlist">
            <section>
                    <xsl:copy-of select="@id"/>
                    <title>
                            <xsl:value-of select="@name"/>
                    </title>
                    <para>
                            <xsl:copy-of select="documentation/(*|text())"/>
                    </para>
                    <para>
                            <xsl:apply-templates select="element[@xsi:type='zenta:ZentaDiagramModel' or @xsi:type='zenta:SketchModel']" mode="figure"/>
                    </para>
                    <xsl:apply-templates select="folder" mode="varlist">
                            <xsl:sort select="@name"/>
                    </xsl:apply-templates>
                    <xsl:apply-templates select="." mode="varlistList"/>
                    <xsl:variable name="includeFile" select="property[@key='includeFile']/@value"/>
                    <xsl:copy-of select="document($includeFile)/*/*"/>
            </section>
    </xsl:template>

<!— @huboard:{“order”:0.9999000099990001,“milestone_order”:0.999200359880033} –>

Updated 04/12/2017 13:40

channels for children.

Picolab/wrangler

wrangler creates a channel for children communication. this should be a subscription. also any channel look ups should check channel types.

<!— @huboard:{“order”:0.15618751562187552,“milestone_order”:1.8576230413256944e-09} –>

Updated 30/11/2017 18:29

"Job not found" when trying to get result from job with error

daisy/pipeline-cli-go
$ cli/dp2 status 92e04aa2-c64e-42a8-b19c-079fc9a5f200 

Job Id: 92e04aa2-c64e-42a8-b19c-079fc9a5f200
Status: ERROR
Priority: medium

$ cli/dp2 results --output /tmp/out 92e04aa2-c64e-42a8-b19c-079fc9a5f200
Error:
    Job 92e04aa2-c64e-42a8-b19c-079fc9a5f200 not found

At the very least, the output should be something other than “not found”. I think it would be better to print “Job {…} has no results” and probably also a return code of 0 instead of 255.

Updated 30/11/2017 14:39

[ERROR] request#show (NoMethodError) "undefined method `is_pro?' for nil:NilClass\nDid you mean...

mysociety/alaveteli
A NoMethodError occurred in request#show:

  undefined method `is_pro?' for nil:NilClass
Did you mean?  is_a?
  app/models/ability.rb:77:in `block in initialize'


-------------------------------
Request:
-------------------------------

  * URL        : https://www.whatdotheyknow.com/request/homeless_stats_7
  * HTTP Method: GET
  * IP address : [FILTERED]
  * Parameters : {"controller"=>"request", "action"=>"show", "url_title"=>"homeless_stats_7"}
  * Timestamp  : 2017-11-29 15:56:46 +0000
  * Rails root : [FILTERED]/www.whatdotheyknow.com/alaveteli-2017-11-28T15-06-55
  * Process: 15625

-------------------------------
Backtrace:
-------------------------------

  app/models/ability.rb:77:in `block in initialize'
  lib/themes/whatdotheyknow-theme/lib/views/request/_sidebar.html.erb:12:in `_lib_themes_whatdotheyknow_theme_lib_views_request__sidebar_html_erb___81792862452503128_70023289000160'
  lib/themes/whatdotheyknow-theme/lib/views/request/show.html.erb:115:in `_lib_themes_whatdotheyknow_theme_lib_views_request_show_html_erb___1407790278222032256_70023434871540'
  app/controllers/request_controller.rb:133:in `block (3 levels) in show'
  app/controllers/request_controller.rb:132:in `block in show'
  lib/alaveteli_localization.rb:43:in `with_locale'
  app/controllers/request_controller.rb:83:in `show'
  app/controllers/application_controller.rb:115:in `record_memory'
  lib/strip_empty_sessions.rb:13:in `call'
Updated 04/12/2017 16:53 1 Comments

cChocoSource, cChocoFeature and others

chocolatey/cChoco

These would need to run choco -v one time to ensure that a config file exists. Otherwise when they hit a line like

https://github.com/chocolatey/cChoco/blob/6b8f5a5b56709c58c4b40b0290ff6e75e9c02898/DSCResources/cChocoSource/cChocoSource.psm1#L152

And it doesn’t return any files, so when they call the next line https://github.com/chocolatey/cChoco/blob/6b8f5a5b56709c58c4b40b0290ff6e75e9c02898/DSCResources/cChocoSource/cChocoSource.psm1#L154

It errors on converting NULL into XML.

Workarounds

Run choco one time prior to setting configuration, perhaps just after the install in your installation script.

Updated 29/11/2017 19:48

Adwords landing pages

mysociety/whatdotheyknow-theme

This is something we’ve considered before because it allows us to hold the user’s hand to an extent, by explaining a bit about what the site is and how to use it, rather than throwing them straight onto a page where they might not understand exactly what they were seeing.

There’s now an extra reason to do this, which is that our ads pointing to the Department of Health’s authority page keep getting banned. After a bit of back and forth I’ve learned that it’s the mention of a specific drug in one of the requests currently showing on the page that is triggering this.

Obviously we can’t do what Google advise, which is to remove that request, and equally obviously, we can’t control what requests might appear at any time in the future. So until Google get a bit smarter about why they ban ads, I think landing pages are our answer.

Updated 04/12/2017 16:54

epub3-to-daisy202: resulting ncc.html is invalid

daisy/pipeline-scripts

Steps to reproduce: - convert a type 4 DAISY 2.02 book to EPUB 3 using the daisy202-to-epub3 script - check that EPUB is valid with epub3-validator - convert EPUB 3 to DAISY 2.02 using epub3-to-daisy202 script

The ncc is based on the EPUB 3 nacigation document, however, it is not properly converted. Most of the metadata is missing, and the content is mostly the same as in the EPUB 3 navigation document.

input ncc: html <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="no" lang="no"> <head> <title>Title</title> <meta name="dc:title" content="(Title)" /> <meta name="dc:creator" content="(Author)" /> <meta name="dc:identifier" content="625904" /> <meta name="dc:format" content="Daisy 2.02" /> <meta name="dc:publisher" content="NLB" /> <meta name="dc:date" content="2017-10-02" scheme="yyyy-mm-dd" /> <meta name="dc:language" content="no" /> <meta name="ncc:charset" content="utf-8" /> <meta name="ncc:narrator" content="(Narrator)" /> <meta name="ncc:producer" content="NLB" /> <meta name="ncc:sourcePublisher" content="Gyldendal" /> <meta name="ncc:pageNormal" content="80" /> <meta name="ncc:pageSpecial" content="0" /> <meta name="ncc:pageFront" content="0" /> <meta name="ncc:maxPageNormal" content="81" /> <meta name="ncc:tocItems" content="95" /> <meta name="ncc:depth" content="1" /> <meta name="ncc:totalTime" content="00:39:48" /> <meta name="ncc:setInfo" content="1 of 1" /> <meta name="ncc:multimediaType" content="audioFullText" /> <meta name="ncc:files" content="77" /> <meta name="ncc:generator" content="Hindenburg ABC Studio 1.26.2164" /> <meta http-equiv="Content-type" content="application/xhtml+xml; charset=utf-8" /> </head> <body> <h1 id="d1574e37-0" class="title"><a href="s001.smil#d1574e37-0">Title</a></h1> <h1 id="d1574e46-0"><a href="s002.smil#d1574e46-0">Lydbokavtalen</a></h1> <h1 id="hix00392"><a href="s003.smil#hix00392">Bokinformasjon</a></h1> <h1 id="hix00393"><a href="s004.smil#hix00393">Informasjon om DAISY-boka</a></h1> <span id="page-2" class="page-normal"><a href="s004.smil#page-2">2</a></span> <span id="page-3" class="page-normal"><a href="s004.smil#page-3">3</a></span> <span id="page-4" class="page-normal"><a href="s004.smil#page-4">4</a></span> <span id="page-5" class="page-normal"><a href="s004.smil#page-5">5</a></span> <span id="page-6" class="page-normal"><a href="s004.smil#page-6">6</a></span> <h1 id="d1574e122-0"><a href="s005.smil#d1574e122-0">Baksidetekst</a></h1> <span id="page-7" class="page-normal"><a href="s005.smil#page-7">7</a></span> <h1 id="h1_2"><a href="s006.smil#h1_2">Innhold</a></h1> <span id="page-8" class="page-normal"><a href="s006.smil#page-8">8</a></span> <span id="page-9" class="page-normal"><a href="s006.smil#page-9">9</a></span> <h1 id="h1_3"><a href="s007.smil#h1_3">Den store sydenturen</a></h1> ... </body> </html>

output ncc: html <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="no"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="dc:identifier" content="625904" /> <title>(Title)</title> </head> <body> <div id="toc" class="nav"> <ol xmlns:epub="http://www.idpf.org/2007/ops"> <li><a id="d1574e37-0" href="625904.html#d1574e37-0">(Title)</a></li> <li><a id="d1574e46-0" href="625904.html#d1574e46-0">Lydbokavtalen</a></li> <li><a id="hix00392" href="625904.html#hix00392">Bokinformasjon</a></li> <li><a id="hix00393" href="625904.html#hix00393">Informasjon om DAISY-boka</a></li> <li><a id="d1574e122-0" href="625904.html#d1574e122-0">Baksidetekst</a></li> <li><a id="h1_2" href="625904.html#h1_2">Innhold</a></li> <li><a id="h1_3" href="625904.html#h1_3">Den store sydenturen</a></li> ... </ol> </div> <div id="page-list" class="nav"> <ol xmlns:epub="http://www.idpf.org/2007/ops"> <li><a id="page-2" href="625904.html#page-2">2</a></li> <li><a id="page-3" href="625904.html#page-3">3</a></li> <li><a id="page-4" href="625904.html#page-4">4</a></li> <li><a id="page-5" href="625904.html#page-5">5</a></li> <li><a id="page-6" href="625904.html#page-6">6</a></li> <li><a id="page-7" href="625904.html#page-7">7</a></li> <li><a id="page-8" href="625904.html#page-8">8</a></li> <li><a id="page-9" href="625904.html#page-9">9</a></li> </ol> </div> </body> </html>

Updated 29/11/2017 11:42 1 Comments

Slow download of DAISY 2.02 fileset using "Download all results" link

daisy/pipeline-webui

When using the EPUB 3 to DAISY 2.02 script, the “Download all results” link takes a long time to ZIP and send the resulting fileset. Not sure if the slowness is in the Web UI, the engine, or both. Probably due to the size of the fileset and not due to the specific script. On one of our servers, this slowness results in a timeout and inability to download the fileset.

Updated 29/11/2017 11:14

provide/share createChannel

Picolab/wrangler

wrangler does not currently share or provide createChannel. Is this a security feature or incomplete module API.

<!— @huboard:{“order”:0.15620313437343772,“milestone_order”:1.85799458451019e-09} –>

Updated 28/11/2017 20:14 1 Comments

QBRB | Ability to find PNRs with specific flight leg

US-CBP/GTAS

Current state has Airport Origin and Country. We will need to capture more flight information so that a query can be written to find passengers on a PNR with two or more specific flight legs. i.e. find PNR Passengers where Flight Leg X is LHR>IAD and Flight Leg Y is IAD>IAH.

<!— @huboard:{“order”:5.538295146458189e-10,“milestone_order”:0.15027607298308482} –>

Updated 04/12/2017 18:10

make project system to automatically refresh reference if missing dll shows up once solution is opened

dotnet/project-system

From @heejaechang on February 23, 2016 20:4

Current project system doesn’t track missing metadata dlls (I mean real metadata dll, not cross-language p2p dll). since it doesnt know where the dll is (msbuild doesnt give back resolved path), it won’t register file change tracker nor let us know about the dll.

right now, we have 2 workarounds for it. one is doing rebuild inside of VS or clicking reference node in solution explorer.

both of action tells VS to refresh all references which will make VS to go thorough those missing dlls to see whether they exist now.

it would be nice if VS can detect situation where missing dlls are available now, and do reference refresh automatically rather than waiting for explicit user action such as “build” as long as we have some way to guess missing dlls location (since we dont have resolved path). ex, hint path, reference name in path format.

Copied from original issue: dotnet/roslyn#9067

Updated 27/11/2017 22:33 7 Comments

Añadir proteccion anti clickjacking y anto csrf

andresordport/todoList

// Protección anti ClickJacking: no permitimos que esta página se pueda llamar desde un frame header(“X-Frame-Options: DENY”);

Añadir anti CSRF, creo que era dentro del form type el la funcion de abajo (function configureOptions) - public function configureOptions(OptionsResolver $resolver) { $resolver->setDefaults(array( ‘data_class’ => Task::class, ‘csrf_protection’ => true, ‘csrf_field_name’ => ‘_token’, // a unique key to help generate the secret token –> creo que es opcional ‘csrf_token_id’ => ‘task_item’, )); }

<!— @huboard:{“order”:0.9988007796361366,“milestone_order”:0.9979023082300623} –>

Updated 27/11/2017 15:58

NoMemoryError: failed to allocate memory

mysociety/alaveteli

Seen a few of these NoMemoryError: failed to allocate memory since we moved server.

/usr/bin/env XAPIAN_MAX_CHANGESETS=10 run-with-lockfile -n /…/change-xapian-database.lock "/…/alaveteli/script/update-xapian-index verbose=true" >> /…/alaveteli/log/update-xapian-index.log || echo "stalled?"

rake aborted!
NoMemoryError: failed to allocate memory
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/marshal.rb:6:in `getbyte'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/marshal.rb:6:in `load'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/marshal.rb:6:in `load_with_autoloading'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/open4-1.3.4/lib/open4.rb:125:in `propagate_exception'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/open4-1.3.4/lib/open4.rb:101:in `do_popen'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/open4-1.3.4/lib/open4.rb:34:in `popen4'
/…/alaveteli-2017-11-21T12-40-42/commonlib/rblib/external_command.rb:101:in `run'
/…/alaveteli-2017-11-21T12-40-42/lib/alaveteli_external_command.rb:33:in `run'
/…/alaveteli-2017-11-21T12-40-42/lib/mail_handler/mail_handler.rb:86:in `get_attachment_text_one_file'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:701:in `block in _extract_text'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:700:in `each'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:700:in `reduce'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:700:in `_extract_text'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:708:in `_get_attachment_text_internal'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:671:in `get_attachment_text_full'
/…/alaveteli-2017-11-21T12-40-42/app/models/incoming_message.rb:713:in `get_text_for_indexing_full'
/…/alaveteli-2017-11-21T12-40-42/app/models/info_request_event.rb:242:in `search_text_main'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:842:in `single_xapian_value'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:835:in `xapian_value'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:956:in `block in xapian_index'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:953:in `each'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:953:in `xapian_index'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:670:in `run_job'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:650:in `block (2 levels) in update_index'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:220:in `transaction'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:639:in `block in update_index'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:636:in `each'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/acts_as_xapian.rb:636:in `update_index'
/…/alaveteli-2017-11-21T12-40-42/lib/acts_as_xapian/tasks/xapian.rake:12:in `block (2 levels) in <top (required)>'
/…/alaveteli-2017-11-21T12-40-42/vendor/bundle/ruby/2.3.0/gems/rake-12.1.0/exe/rake:27:in `<top (required)>'
/opt/rbenv/versions/2.3.5/bin/bundle:22:in `load'
/opt/rbenv/versions/2.3.5/bin/bundle:22:in `<main>'
Tasks: TOP => xapian:update_index
(See full trace by running task with --trace)
Updated 04/12/2017 16:58 2 Comments

Add coinmarketcap and cryptocompare as exchange rate sources so we can support all new tokens

balancemymoney/balance-open

Right now we use some major exchanges to get pricing information. Coinmarketcap, CryptoCompare, and other aggregators have APIs that allow access to their price ticker info just like exchanges, but they show ALL of the tokens, and all of the new ones. I had added Kucoin to get more new tokens, but adding one of the aggregators–or even better, multiple–would fill in the gaps better.

<!— @huboard:{“order”:36.99537555493525,“milestone_order”:36.981505548705265,“custom_state”:“”} –>

Updated 02/12/2017 21:33 2 Comments

Shihai: add snapshots

perkowitz/issho

Snapshots save the current state of module mutes, beatbox track mutes, and tempo. Saving snapshots will require Shihai to have its own memory. Memory will consist of sessions, which store the snapshots per session. Session also remembers which snapshot was selected. Shihai will also have to implement save/load.

Tasks - Create ShihaiMemory, ShihaiSession, ShihaiSnapshot - Implement save/load of ShihaiMemory, incl “save” button in usual spot - Move tempo to settings screen (incl more tempo range?) - Make right-side buttons into 8 snapshot controls - Q: how to save snapshot? - Q: should current pattern be incl in session, or left to modules?

Updated 23/11/2017 21:22

AutoTrack

Codealike/Codealike-Jetbrains

Allow to immediately use Codealike even if a token is not present. User will be able to update API token at any moment and Codealike should update tracking information accordingly at server.

<!— @huboard:{“order”:0.9994002099440126,“milestone_order”:0.9994002099440126} –>

Updated 23/11/2017 17:31

Auto Tracking

Codealike/Codealike-Eclipse

Allow to immediately use Codealike even if a token is not present. User will be able to update API token at any moment and Codealike should update tracking information accordingly at server.

<!— @huboard:{“order”:0.9996000999800034,“milestone_order”:0.9996000999800034} –>

Updated 23/11/2017 17:20

Fork me on GitHub