Errors after upgrading from 4.3.0 to 4.3.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- bootstrap, javascript, ruby
Research direction
Start by reproducing the error in the RSpec/Capybara test flow at the visit call, comparing gem versions 4.3.0 and 4.3.1. Use the provided JavaScript stack trace, including Tooltip and sanitizeHtml, to trace the regression; done means identifying why the console errors appear and confirming the test run no longer logs them.
Written by the indexing model from the issue text.
Description
I upgraded this gem from 4.3.0 to 4.3.1. Now when running my tests I am getting errors logged such as:
jQuery.Deferred exception: null is not an object (evaluating 'createdDocument.body') sanitizeHtml@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:15965:49
_getConfig@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:16578:39
Tooltip@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:16107:36
http://localhost:41065/assets/application-7de341d...8b5bd36839.js:16643:29
each@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:355:23
each@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:190:21
_jQueryInterface@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:16633:23
http://localhost:41065/assets/application-7de341d...8b5bd36839.js:66417:41
mightThrow@http://localhost:41065/assets/application-7de341d...8b5bd36839.js:3535:34
http://localhost:41065/assets/application-7de341d...8b5bd36839.js:3603:22 undefined
These errors happen when running rspec using capybara and during a visit command to visit a page.
All the tests seem to be passing, but I am trying to figure out what is causing these errors being logged to the console as the tests are running.
- Dominant language
- SCSS
- Stars
- 2k
- Forks
- 437
- Avg merge
- 1h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from twbs/bootstrap-rubygem
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
twbs/bootstrap-rubygem#294 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
twbs/bootstrap-rubygem#291 · 2 comments · 7 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
twbs/bootstrap-rubygem#289 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
twbs/bootstrap-rubygem#288 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
twbs/bootstrap-rubygem#284 ·
All issues in twbs/bootstrap-rubygem
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
feature:LinkChecker
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
digitalfabrik/integreat-cms#4594 ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MHSanaei/3x-ui#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
Twake Drive picker: closePicker() never destroys the intent (stop() is on the promise returned by start(), not by create())Possibly taken @chibenwa claimed this today. Openclaude
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1498 · 1 comment ·
Maintainers usually reply within 1 day