On the Prevalence, Impact, and Evolution of SQL code smells in Data-Intensive Systems

ABSTRACT: Code smells indicate software design problems that harm software quality. Data-intensive systems that frequently access databases often suffer from SQL code smells besides the traditional smells. While there have been extensive studies on traditional code smells, recently, there has been a growing interest in SQL code smells. In this paper, we conduct an empirical study to investigate the prevalence and evolution of SQL code smells in open-source, data-intensive systems. We collected 150 projects and examined both traditional and SQL code smells in these projects. Our investigation delivers several important findings. First, SQL code smells are indeed prevalent in data-intensive software systems. Second, SQL code smells have a weak co-occurrence with traditional code smells. Third, SQL code smells have a weaker association with bugs than that of traditional code smells. Fourth, SQL code smells are more likely to be introduced at the beginning of the project lifetime and likely to be left in the code without a fix, compared to traditional code smells. Overall, our results show that SQL code smells are indeed prevalent and persistent in the studied data-intensive software systems. Developers should be aware of these smells and consider detecting and refactoring SQL code smells and traditional code smells separately, using dedicated tools

R-Locker: Thwarting Ransomware Action through a Honey le-based Approach

Ransomware has become a pandemic nowadays. Although some proposals exist to fight against this increasing type of extorsion, most of them are prevention like and rely on the assumption that early detection is not so effective once the victim is infected. This paper presents a novel approach intended not just to early detect ransomware but to completly thwart its action. For that, a set of honeyfiles are deployed around the target environment in order to catch the ransomware. Instead of being normal archives, honeyfiles are FIFO like, so that the ransomware is blocked once it starts reading the file. In addition to frustrate its action, our honeyfile solution is able to automatically launch countermeasures to solve the infection. Moreover, as it does not require previous training or knowledge, the approach allows fighting against unknown, zero-day ransomware related attacks. As a proof of concept, we have developed the approach for Unix platforms. The tool, named R-Locker, shows excellent performance both from the perspective of its accuracy as well as in terms of complexity and resource consumption. In addition, it has no special needs or privileges and does not affect the normal operation of the overall environment

Software citation principles

Software is a critical part of modern research and yet there is little support across the scholarly ecosystem for its acknowledgement and citation. Inspired by the activities of the FORCE11 working group focused on data citation, this document summarizes the recommendations of the FORCE11 Software Citation Working Group and its activities between June 2015 and April 2016. Based on a review of existing community practices, the goal of the working group was to produce a consolidated set of citation principles that may encourage broad adoption of a consistent policy for software citation across disciplines and venues. Our work is presented here as a set of software citation principles, a discussion of the motivations for developing the principles, reviews of existing community practice, and a discussion of the requirements these principles would place upon different stakeholders. Working examples and possible technical solutions for how these principles can be implemented will be discussed in a separate paper

STEM classification of CBO-2002 occupations and Brazillian HEC fields of education

We provide .csv tables classifying CBO-2002 occupations (Classificação Brasileira de Ocupações) into STEM and non-STEM occupations, as well as INEP’s HEC's (Higher Education Census) fields of education classification of STEM degrees in Brazil. In addition to the tables, we also provide reports in .pdf format with a guide and full disclosure of the classification processes. In Brazil, there is no official taxonomy of STEM jobs or educational fields. As a result, the few existing analysis of STEM jobs and education in Brazil use their own, generally vague, classifications and are not transparent about the classification criteria. We seek to fill this gap in the STEM taxonomy and literature by providing unprecedented classification of STEM occupations and higher-education degrees in Brazil

Lime

toolkit explains the predictions of any machine learning classifie

behr-github/Lightning-NOx-Lifetime: Version 1.0.0 in support of Nault et al. GRL 2017

Relevant analysis code used in Nault et al. GRL 201

pgRouting/pgrouting: v3.5.1

pgRouting 3.5.1 Release Notes To see all issues & pull requests closed by this release see the Git closed milestone for 3.5.1 Documentation fixes Changes on the documentation to the following: pgr_degree pgr_dijkstra pgr_ksp Automatic page history links using bootstrap_version 2 because 3+ does not do dropdowns Issue fixes #2565: pgr_pgr_lengauerTarjanDominatorTree triggers an assertion SQL enhancements #2561: Not use wildcards on SQL pgtap tests #2559: pgtap test using sampledata Build fixes Fix winnie build Code fixes Fix clang warnings Grouping headers of postgres readers Attachments File | Contents | --- | --- | | doc-v3.5.1-en-es.tar.gz | English and Spanish documentation. Redirection to English | doc-v3.5.1-en.tar.gz|English documentation. Redirection to English | doc-v3.5.1-es.tar.gz|Spanish documentation. Redirection to Spanish | pgrouting-3.5.1.tar.gz | tar.gz of the release | pgrouting-3.5.1.zip| zip of the releas