Phil Pirozhkov

Results 79 issues of Phil Pirozhkov

Adapt the code from `rubocop-rspec` that does that. fixes #3904 There is a huge problem with this approach. [LibYAML is not capable of parsing and emitting comments](https://github.com/yaml/libyaml/issues/42) for our `config/default.yml`,...

Hey @djezzzl ! :wave: Cascade deletion is sometimes a very expensive operation. In case the association is defined as `dependent: :delete`, it is possible to rely on the database to...

Does it make sense to do so? https://www.postgresql.org/docs/13/citext.html has a good rationale for using citext. It's a useful feature for columns like, e.g. emails. Regarding performance - should be faster...

The problem only becomes apparent when `prepared_statements:` option is set to `false`. This is typical and [recommended by Rails when connecting via PgBouncer](https://guides.rubyonrails.org/configuring.html#configuring-a-postgresql-database). ``` ActiveRecord::StatementInvalid: PG::UndefinedFunction: ERROR: operator does not...

Hey @djezzzl ! :wave: I have the following in `db/schema.rb`: ```ruby enable_extension "citext" create_table "groups", force: :cascade do |t| t.citext "name", null: false t.index ["name"], name: "index_groups_on_name", unique: true ```...

Currently we have filtering logic literally hardcoded here: [`lib/crystalball/map_generator/helpers/path_filter.rb`](https://github.com/toptal/crystalball/blob/master/lib/crystalball/map_generator/helpers/path_filter.rb). We need it to be a bit more flexible so we can specify a list of directories\files to filter out of...

feature request
help wanted

Crystalball needs to be able to list predicted examples without actually running them. It's useful for further load balancing with Knapsack\whatever. Proposed interface: `crystalball --dry-prediction` which outputs a list of...

feature request
help wanted

Add a `--watch` that would run tests as Crystalball finds the changes in the source code. - Use guard (or similar) - Lookup needs to be faster - Only run...

feature request
help wanted

Redis? Neo4j (or another graph database)? Pros: - Would allow things like levels of proximity between files and affected specs, as well as reduce redundancy of spec file data Cons:...

feature request
help wanted

The way lookup works now: ```ruby examples_to_run = [ ] changed_files.each do |file| # n examples.each do |ex| # n * n examples_to_run

feature request
help wanted