- 11 7月, 2019 7 次提交
-
-
由 Ryuta Kamizono 提交于
Merge pull request #36647 from giraffate/fix_exists_with_distinct_and_offset_and_order_in_postgresql Fix `relation.exists?` with giving `distinct`, `offset` and `order` for joined table
-
由 Yuji Yaginuma 提交于
MySQL: Check error number instead of a message
-
由 Jacob Bednarz 提交于
A HTTP feature policy is Yet Another HTTP header for instructing the browser about which features the application intends to make use of and to lock down access to others. This is a new security mechanism that ensures that should an application become compromised or a third party attempts an unexpected action, the browser will override it and maintain the intended UX. WICG specification: https://wicg.github.io/feature-policy/ The end result is a HTTP header that looks like the following: ``` Feature-Policy: geolocation 'none'; autoplay https://example.com ``` This will prevent the browser from using geolocation and only allow autoplay on `https://example.com`. Full feature list can be found over in the WICG repository[1]. As of today Chrome and Safari have public support[2] for this functionality with Firefox working on support[3] and Edge still pending acceptance of the suggestion[4]. #### Examples Using an initializer ```rb # config/initializers/feature_policy.rb Rails.application.config.feature_policy do |f| f.geolocation :none f.camera :none f.payment "https://secure.example.com" f.fullscreen :self end ``` In a controller ```rb class SampleController < ApplicationController def index feature_policy do |f| f.geolocation "https://example.com" end end end ``` Some of you might realise that the HTTP feature policy looks pretty close to that of a Content Security Policy; and you're right. So much so that I used the Content Security Policy DSL from #31162 as the starting point for this change. This change *doesn't* introduce support for defining a feature policy on an iframe and this has been intentionally done to split the HTTP header and the HTML element (`iframe`) support. If this is successful, I'll look to add that on it's own. Full documentation on HTTP feature policies can be found at https://wicg.github.io/feature-policy/. Google have also published[5] a great in-depth write up of this functionality. [1]: https://github.com/WICG/feature-policy/blob/master/features.md [2]: https://www.chromestatus.com/feature/5694225681219584 [3]: https://bugzilla.mozilla.org/show_bug.cgi?id=1390801 [4]: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/33507907-support-feature-policy [5]: https://developers.google.com/web/updates/2018/06/feature-policy
-
由 yuuji.yaginuma 提交于
To be able to check regardless of locale.
-
由 Ryuta Kamizono 提交于
Share the Arel dispatch cache between connections
-
由 Ryuta Kamizono 提交于
Share the column and table name quote cache between connections
-
由 Eileen M. Uchitelle 提交于
Fix query cache when using shared connections
-
- 10 7月, 2019 7 次提交
-
-
由 Takayuki Nakata 提交于
The error happens in PostgreSQL when using `relation.exists?` with `distinct`, `offset` and `order` for joined table. However, the error does not happen if either `distinct` or `offset` is removed. This behavior is confusing. Fixes #36632
-
由 Jean Boussier 提交于
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
This is a first draft only, needs polishing for final.
-
- 09 7月, 2019 7 次提交
-
-
由 Jean Boussier 提交于
-
由 Yuji Yaginuma 提交于
Make "bin/setup" works when using PostgreSQL with locales other than en locale
-
由 Ryuta Kamizono 提交于
update example url for add_source [ci skip]
-
由 Ryuta Kamizono 提交于
Fix indentation
💇 ♀️ [ci skip] -
-
由 ultrawebmarketing 提交于
http://code.whytheluckystiff.net is now just a spam site. Use http://gems.github.com as an example instead.
-
由 Guillermo Iguaran 提交于
Add database_exists? method to connection adapters
-
- 08 7月, 2019 8 次提交
-
-
由 Guillermo Iguaran 提交于
-
由 Eileen M. Uchitelle 提交于
When DATABASE_URL is specified don't trample envs that use a url: key
-
由 Heinrich Lee Yu 提交于
Enables the query cache on the correct connection when shared connections across threads are enabled
-
由 Will Jessop 提交于
fixes #36610
-
由 Ryuta Kamizono 提交于
Do not use aliases in GROUP BY clause
-
由 George Claghorn 提交于
Fixes that file attachments without captions would not be represented in plain text generated from rich-text content, causing ActionText::RichText#present? to return false. Closes #36607.
-
由 Ryuta Kamizono 提交于
It is for agnostic test case, since quoted table name may include `.` for all adapters, and `[` / `]` for sqlserver adapter.
-
由 Ryuta Kamizono 提交于
It appears that Oracle does not allow using aliases in GROUP BY clause unlike ORDER BY clause. Fixes #36613.
-
- 07 7月, 2019 4 次提交
-
-
由 yuuji.yaginuma 提交于
The PostgreSQL adapter uses an error message to determine if a database exists or not. https://github.com/rails/rails/blob/74ef67b16de67d2ae2f996e50a18a93aebf68fe6/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb#L49 However, this message is properly converted according to the locale. So this check does not work correctly for non-en locales. As a result, `db:prepare` cannot correctly determine if a database exists, and `bin/setup`, which depends on the task, does not work correctly if the database does not exist. It checks to exist if the "does not exist" exists, but that message is also used in other error messages(e.g. "role does not exist"). So cannot check correctly also in en locale. https://github.com/postgres/postgres/blob/master/src/backend/po/ja.po#L10542 It would be fine could check the status, but in my understanding, when a connecting fails, only the status `CONNECTION_BAD` be used, and it seems that details cannot be checked. https://www.postgresql.org/docs/11/libpq-status.html#LIBPQ-PQSTATUS I fixed to check whether the error message contains a database name. This is probably not accurate but can check it better now.
-
由 John Hawthorn 提交于
Set process title of parallelized test workers
-
由 John Hawthorn 提交于
Fix Browser#preload for older Selenium
-
由 Ryuta Kamizono 提交于
MySQL: Fix schema dumping `enum` and `set` columns correctly
-
- 06 7月, 2019 2 次提交
-
-
由 Ryuta Kamizono 提交于
Update docs on dirty.rb [ci skip]
-
由 John Gesimondo 提交于
`previously_changed` seems to actually be `previous_changes`
-
- 05 7月, 2019 5 次提交
-
-
由 Ryuta Kamizono 提交于
`enum` and `set` are typed cast as `:string`, but currently the `:string` type is incorrectly reused for schema dumping. A cast type on columns is not always the same with `sql_type`, this fixes schema dumping `enum` and `set` columns to use `sql_type` instead of `type` correctly.
-
由 John Hawthorn 提交于
Since #36424, we need an newer version in order to pass.
-
由 John Hawthorn 提交于
Older versions of selenium had driver_path on ::Selenium::WebDriver::Chrome directly, not on Service. This avoids errors on those old versions and will preload properly if webdrivers is installed.
-
由 John Hawthorn 提交于
Preload browser driver_path to fix system testing under parallelism
-
由 jacobherrington 提交于
-