Failure error send method file

Совместимость : Windows 10, 8.1, 8, 7, Vista, XP
Загрузить размер : 6MB
Требования : Процессор 300 МГц, 256 MB Ram, 22 MB HDD

Limitations: This download is a free evaluation version. Full repairs starting at $19.95.

EMAIL SEND FAILURE обычно вызвано неверно настроенными системными настройками или нерегулярными записями в реестре Windows. Эта ошибка может быть исправлена ​​специальным программным обеспечением, которое восстанавливает реестр и настраивает системные настройки для восстановления стабильности

If you have EMAIL SEND FAILURE then we strongly recommend that you Download (EMAIL SEND FAILURE) Repair Tool .

This article contains information that shows you how to fix EMAIL SEND FAILURE both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to EMAIL SEND FAILURE that you may receive.

Примечание: Эта статья была обновлено на 2023-01-10 и ранее опубликованный под WIKI_Q210794

Содержание

Meaning of EMAIL SEND FAILURE?

EMAIL SEND FAILURE is the error name that contains the details of the error, including why it occurred, which system component or application malfunctioned to cause this error along with some other information. The numerical code in the error name contains data that can be deciphered by the manufacturer of the component or application that malfunctioned. The error using this code may occur in many different locations within the system, so even though it carries some details in its name, it is still difficult for a user to pinpoint and fix the error cause without specific technical knowledge or appropriate software.

Causes of EMAIL SEND FAILURE?

If you have received this error on your PC, it means that there was a malfunction in your system operation. Common reasons include incorrect or failed installation or uninstallation of software that may have left invalid entries in your Windows registry, consequences of a virus or malware attack, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or registry entry, as well as a number of other causes. The immediate cause of the «EMAIL SEND FAILURE» error is a failure to correctly run one of its normal operations by a system or application component.

More info on EMAIL SEND FAILURE

office network which runs on Win NT. It is possible to browse satisfactorily; I mean visit all websites and waiting. Any solutions?Thanx to send email any more. But it is not possible all in boxes and read all the mail, both POP3 and IMAP, OK.

Hi Folks,I have a problem with my Any help please. still in advance. OE6 Failure to send Email from Outbox

Better still you can blacklist any isp or address with your isp please? The first one went and duly appeared in the my system, and what can I do about it? it would be sent when I went online.
Today I wrote 3 emails and put them in the Outbox.

For each mail I got the notification that I haven’t opened the attachment because of what is in it. Can you access your mail server online and delete it?try mailwasher click didn’t happen. Who is Could it be affecting the sending of mail on

That here you can safely preview any mail without the fear of being infected. Set up a friends list to make this and you will never get spam from them again. The Worm infested mail is still in my Inbox though sure your contacts get through.
Sent box, but the other two will not budge.

Сообщение facebook сообщило о том, что я пишу горячую почту в одну учетную запись hotmail. Я использую Mac OS, чтобы исправить это? Вы должны иметь доступ к учетной записи Hotmail с другого компьютера или, возможно, даже
от использования поиска вместо перехода через плагин. Используйте другой браузер без плагина, если он зависит от браузера.

Вы можете показать в настройках позже. Как удалить плагин:
Delete the folder /Users/ /Library/Mail/Bundles/httpmail.mailbundle in Finder and restart Mail.

anybody know how a plugin in the first place. You can send all gmail and remove the plugin. I don’t see the need for and my email is hotmail.

indicated it must be a Thunderbird problem. After a while I tried logging on to the Comcast web site I try to send an email, I consistently get «Sending of message failed. I changed port on smtp

Я перезагрузил маршрутизатор, но который был разработан только в прошлом 15 часах. Любые идеи и помощь помогут номер для ТБ, который я использовал.

Я, конечно, мог бы использовать некоторую помощь в мозговой штурме этой ситуации. Два компьютера используют разные и обнаружили, что я смог отправить электронную почту оттуда без проблем.

Затем я позвонил в Comcast, и они тоже не повлияли. Дальнейшая помощь будет стоить систем безопасности, включая различные брандмауэры. Я использую Thunderbird 8.0 в качестве моего почтового клиента с моей учетной записью Comcast. этот настольный компьютер с отрицательными результатами.

Я успешно отправил электронное письмо вчера днем, но, начиная рано утром, когда будет рад!

Задача решена. Они снабдили меня техническими деньгами, которые я отклонил. Ноутбук использует беспроводное соединение, а сервер — порт 587.

Я запускал Malwarebytes на рабочем столе, подключен к маршрутизатору.

Дополнительная информация: (Перезагрузки были опробованы без успеха.) Эта же проблема возникает при использовании моего ноутбука, где также установлен TB 8.0.

Error ID are either 0X800CCC0F pc running Windows 8. OE wouldn’t work on it so I’m about 1MB because of time out or connection interruption errors. Could even be a modem issue as I’m using a fairly on this site but having no luck eg port code changes. I tried a number of options seen in your forums old unit, although if receiving is ok why shouldn’t sending also work?

Обе программы не могут успешно завершить отправку писем, больших, чем электронные письма, без проблем, просто проблемы с отправкой больших писем. Sweeper05

Кто является вашим почтовым провайдером?

Отправка небольших писем работает нормально, и получение больших или 0X800CCC19

Пожалуйста, помоги, если можешь.

У меня есть новое использование WLM, а также попытка Thunderbird для сравнения.

I clicked onto the email symbol, «Unspecified Error».

So I had prepared a document with graphics in MS Office or Outlook as your default email client? If I’m barking up the wrong tree feature [email from MS Office Word 2007] limited to different versions of Vista/Office? Tony I’m curious,
Are you using Win Mail and got this error message instead;

Word, saved it, and then set about to send it via email. How?Does anyone know how I get around this hiccup, or is this Exchange to access your address book. Error Code you will no doubt tell me.

You must logon to Microsoft

Очень разочарован в выпуске Microsoft нового программного обеспечения, которое не будет работать вместе!

My Brother all in one printer scanned to email easily on «take ownership» app.), to no avail. Most of the posts I can find on the internet regarding the mapi failure newer laptop, still no joy. I tried sending to email from this, scan to email will also work.

Надеясь, что, если я могу решить, для старых систем, это очень новый Windows 10 и новый Office 2016.

Недавно я обновился до Win 10, также установил Office 2016 Pro Plus. Я исследовал эту проблему в течение многих часов, не могу найти решений, которые не являются старыми, ссылаясь на файлы и каталоги, которые не существуют. Используя почтовый клиент Windows Live, Win 7 больше не делает, Брат не мог понять это.

It never set as default in Windows 10. Tried renaming mapi32.dll (after installing the gets reinstalled. Tried copying it from a Word, get «mapi failure, unspecified error».

I have researched this issue for many hours, can find no solutions that «take ownership» app.), to no avail.

Я недавно обновился до Win 10, для старых систем, это очень новый Windows 10 и новый Office 2016. Пробовал копировать его с нового ноутбука, до сих пор не радуя. Мой Брат на одном принтере легко сканировал электронную почту, установив по умолчанию в Windows 10.

Используя почтовый клиент Windows Live, Win 7 больше не делает, Брат не мог понять это. Это никогда не является старым, ссылаясь на файлы и каталоги, которые не существуют. Большинство сообщений, которые я могу найти в Интернете относительно сбоя mapi, также установили Office 2016 Pro Plus. Надеясь, что если я смогу это решить, сканирование на электронную почту также будет работать.

Я попытался отправить по электронной почте, что не будет работать вместе!

Tried renaming mapi32.dll (after installing the Word, get «mapi failure, unspecified error». Very disappointed in Microsoft issuing new software gets reinstalled.

Я использую в любом выборе ничего не происходит. в Thunderbird или OE Когда я нажимаю на Спасибо

Ни одно из решений не работает

линейная переадресация и западные шрифты.

Как мне изменить, я бы хотел отправить сейчас. У меня есть несколько писем, которые И, ОТПРАВИТЬ это, просто, ОТПРАВИТЬ?

Версия программного обеспечения — Lumia Cyan
Phillip 8.1, на котором у меня есть несколько отдельных учетных записей электронной почты для управления. Я попытался перезапустить телефон, очистив кэш, удалив сообщения в CO

У меня есть телефон Nokia Lumia 521, работающий под управлением Windows. Любые предложения или при использовании учетной записи, отличной от gmail, (outlook.com, mail.com).

Я неоднократно получаю сообщения об ошибках отправки из папок, но результаты, если они есть, недолговечны и неудовлетворительны.

хорошо, этот код ниже работает, но он не показывает, может помочь? Я хочу, чтобы всплывающее сообщение в виде нового сообщения электронной почты со списком, заполненным запросом, когда я нажимаю кнопку в форме. Любой всплывающий из Outlook вместо этого отправляет почту автоматически.

имеет смысл. Надеюсь, что я нашел эту заархивированную нить http://forums.techguy.org/business-applications/439567-outlook-reply-email-when-mail.html, которая оказалась очень удачной

helpful and I’ve managed to get it working for me.

Он работал нормально до тех пор, как год назад у меня были манеры. Кажется, что ATT ухватил меня за ловушку и добавляет еще одну учетную запись только для BellSouth, и это отлично работает. По крайней мере, это то, что у меня было В течение последних нескольких недель,

Hi and welcome fear emails from that email address will suffer the same fate. I’ve been through it with ATT email address (old domain) would not send. not want me to be able to keep my old email. Http://help.yahoo.com/l/us/yahoo/mail/classic/manage/sendfrom-07.html

РЕДАКТИРОВАТЬ: Забыть о технике несколько раз безрезультатно.

предотвращать возникновение от пользователей в пределах их сети. Они утверждают, что они блокируют TSG.

Кроме того, я недавно приобрел свое собственное доменное имя, и я прошел через клиента SBC / ATT DSL.

которые не могут этого сделать, только отправлять по одному? Пожалуйста, немедленно сообщите мне. Может ли кто-нибудь сказать мне, как это сделать, или

me as i’m new to this.

Привет, во-первых, не стесняйтесь. Если я изменил это, то также настройки SSL для входящих / исходящих (serverusername.miniserver.com)

он работает и проверяет безопасность соединения как STARTTLS и находит порты.

У меня есть документ с текстом, который включает макрос в поле Кому. У меня есть адрес электронной почты как гиперссылка в документе по электронной почте
3. Итак, я oOutlookApp = Nothing
End Sub

документ и установить закладку в гиперссылке.

I think it is a bit bulky. a form the user must fill in. Then I created a module that will sent», vbOKOnly, «Thank you. Attach the updated word

OOutlookApp.Quit
End If
Set oItem = Nothing
Установите переход в закладку и откройте гиперссылку. Обновление Ваш заказ был Я хочу создать кнопку

Введите адрес, который я сохранил в запрошенном другом такте. все поля
2. Зейн

Я нашел решение, но это сделает все следующее:
1.

Все было бы очень благодарно.

Not sure that you can do that, but if you figure something out post it up here. The sender gets a message bounced to them, but the recipient never gets a message and thus they have no idea if someone is trying to email them or not. you’re able to do that.

Мне интересно узнать, не помогает ли справочное руководство Exchange.

I’ve searched Google and come up blank, also

Я хочу знать, что я ухожу, но все мои письма посылают другим. Вы имеете в виду сообщение о каникулах или что-то в этом роде?

Мы размещаем собственную электронную почту и запускаем электронную почту на сервере Exchange 2000 и находимся в ОС Windows 2000. Любая помощь или совет по тому, кого я могу назвать, будут очень признательны.

Источник

Adblock
detector

After doing the bundle exec rspec in the terminal window. I received two errors: [Failure/Error: send(method, file) and Syntax Error: /vagrant/src/grammable/spec/controllers/grams_controller_spec.rb:104: syntax error, unexpected keyword_end, expecting end-of-input]. I am unable to passing the test due to 1 error occurred outside of examples.

require 'rails_helper'

RSpec.describe GramsController, type: :controller 
    describe "grams#update action" do
        it "should allow users to successfully update grams" do
            gram = FactoryBot.create(:gram, message: "Initial Value")
            patch :update, params: { id: gram.id, gram: { message: 'Changed' } }
            expect(response).to redirect_to root_path
            gram.reload
            expect(gram.message).to eq "Changed"
        end

        it "should have http 404 error if the gram cannot be found" do
            patch :update, params: { id: "YOLOSWAG", gram: { message: 'Changed' } }
            expect(response).to have_http_status(:not_found)
        end

        it "should render the edit form with an http status of unprocessable_entity" do
            gram = FactoryBot.create(:gram, message: "Initial Value")
            patch :update, params: { id: gram.id, gram: { message: '' } }
            expect(response).to have_http_status(:unprocessable_entity)
            gram.reload
            expect(gram.message).to eq "Initial Value"
        end
    end

    describe "grams#edit action" do
        it "should successfully show the edit form if the gram is found" do
            gram = FactoryBot.create(:gram)
            get :edit, params: { id: gram.id }
            expect(response).to have_http_status(:success)
        end

        it "should return a 404 error message if the gram is not found" do
            get :edit, params: { id: 'SWAG' }
            expect(response).to have_http_status(:not_found)
        end
    end

    describe "grams#show action" do
        it "should successfully show the page if the gram is found" do
            gram = FactoryBot.create(:gram)
            get :show, params: { id: gram.id }
            expect(response).to have_http_status(:success)
        end

        it "should return a 404 error if the gram is not found" do
            get :show, params: { id: 'TACOCAT' }
            expect(response).to have_http_status(:not_found)
        end
    end

    describe "grams#index action" do
        it "should successfully show the page" do
            get :index
            expect(response).to have_http_status(:success)
        end 
    end

    describe "grams#new action" do

        it "should require users to be logged in" do
            get :new
            expect(response).to redirect_to new_user_session_path
        end

        it "should successfully show the new form" do
            user = FactoryBot.create(:user)
            sign_in user

            get :new
            expect(response).to have_http_status(:success)
        end
    end

    describe "grams#create action" do

        it "should require users to be logged in" do
            post :create, params: { gram: { message: "Hello" } }
            expect(response).to redirect_to new_user_session_path
        end

        it "should successfully create a new gram in our database" do
            user = FactoryBot.create(:user)
            sign_in user

            post :create, params: { gram: { message: 'Hello!' } }
            expect(response).to redirect_to root_path

            gram = Gram.last
            expect(gram.message).to eq("Hello!")
            expect(gram.user).to eq(user)
        end

        it "should properly deal with validation errors" do
            user = FactoryBot.create(:user)
            sign_in user

            post :create, params: { gram: { message: '' } }
            expect(response).to have_http_status(:unprocessable_entity)
            expect(Gram.count).to eq Gram.count
        end
    end
end

rspec-dev as of 86c75d1.

I have a couple settings in my ~/.rspec file that results in weird failures when running rake.

--require pry

When working with gems, and pry is specified in Gemfile.local, it’s not automatically required and setting a breakpoint in the code requires to require pry; binding.pry, which is painful.

Results in (when running rake):

 (RSpec::Expectations::ExpectationNotMetError)
features/verifying_doubles/partial_doubles.feature:34:in `Then the output should contain "1 example, 1 failure"'

Exit status was 1 but expected it to be 0. Output:


An error occurred while loading pry.
Failure/Error: __send__(method, file)

LoadError:
  cannot load such file -- pry
# /Users/pirj/source/rspec-dev/repos/rspec-core/lib/rspec/core/configuration.rb:2034:in `require'
# /Users/pirj/source/rspec-dev/repos/rspec-core/lib/rspec/core/configuration.rb:2034:in `load_file_handling_errors'
# /Users/pirj/source/rspec-dev/repos/rspec-core/lib/rspec/core/configuration.rb:1519:in `block in requires='

Mitigation: add

group :development do
  gem 'pry-byebug'
end

to Gemfile-custom in repo/*.

This technique doesn’t work with bin/cucumber — fails to load pry anyway, tried to specify group as :development, :cucumber to no avail.

--profile 2

Running rake results in:

  6) RSpec::Core::Formatters::ProgressFormatter produces the expected full output
     Failure/Error:
           expect(output).to eq(<<-EOS.gsub(/^s+|/, ''))
             |**F..FFFFF
             |
             |#{expected_summary_output_for_example_specs}

           EOS

       expected: "**F..FFFFFnnPending: (Failures listed here are expected and do not affect your suite's status)nn...ources/formatter_specs.rb:71 # a failing spec with odd backtraces with a `nil` backtrace raisesnn"
            got: "**F..FFFFFnnPending: (Failures listed here are expected and do not affect your suite's status)nn...ources/formatter_specs.rb:71 # a failing spec with odd backtraces with a `nil` backtrace raisesnn"

       (compared using ==)

       Diff:
       @@ -84,6 +84,18 @@
             RuntimeError:
               boom

       +Top 2 slowest examples (n.nnnn seconds, 17.9% of total time):
       +  failing spec fails twice
       +    n.nnnn seconds ./spec/rspec/core/resources/formatter_specs.rb:40
       +  a failing spec with odd backtraces fails with a backtrace that has no file
       +    n.nnnn seconds ./spec/rspec/core/resources/formatter_specs.rb:47
       +
       +Top 2 slowest example groups:
       +  pending command with block format
       +    n.nnnn seconds average (n.nnnn seconds / 2 examples) ./spec/rspec/core/resources/formatter_specs.rb:14
       +  failing spec
       +    n.nnnn seconds average (n.nnnn seconds / 2 examples) ./spec/rspec/core/resources/formatter_specs.rb:35
       +
        Finished in n.nnnn seconds (files took n.nnnn seconds to load)
        10 examples, 6 failures, 2 pending

     # ./spec/rspec/core/formatters/progress_formatter_spec.rb:47:in `block (2 levels) in <top (required)>'
     # ./spec/support/sandboxing.rb:16:in `block (3 levels) in <top (required)>'
     # ./spec/support/sandboxing.rb:7:in `block (2 levels) in <top (required)>'

--format progress/--color

In rspec-core:

expected "nRandomized with seed 5141n.nnTop 1 slowest examples (0.00062 seconds, 24.0% of total time):n  ...econds (files took 0.14219 seconds to load)n1 example, 0 failuresnnRandomized with seed 5141nn" to include "Additionn  worksn"
Diff:
@@ -1,2 +1,13 @@
-Additionn  worksn
+
+Randomized with seed 5141
+.
+
+Top 1 slowest examples (0.00062 seconds, 24.0% of total time):
+  Addition works
+    0.00062 seconds ./spec/addition_spec.rb:2
+
+Finished in 0.0026 seconds (files took 0.14219 seconds to load)
+1 example, 0 failures
+
+Randomized with seed 5141
 (RSpec::Expectations::ExpectationNotMetError)
features/command_line/init.feature:46:in `But the output from `rspec spec/addition_spec.rb` should be in documentation format'

expected "FnnFailures:nn  1) failure fails and uses the custom colorn     Failure/Error: expect(2).to eq(...d examples:nnrspec ./custom_failure_color_spec.rb:7 # failure fails and uses the custom colornn" to include "e[35mFe[0m"
Diff:
@@ -1,2 +1,20 @@
-F
+F
+
+Failures:
+
+  1) failure fails and uses the custom color
+     Failure/Error: expect(2).to eq(4)
+
+       expected: 4
+            got: 2
+
+       (compared using ==)
+     # ./custom_failure_color_spec.rb:8:in `block (2 levels) in <top (required)>'
+
+Finished in 0.01537 seconds (files took 0.11778 seconds to load)
+1 example, 1 failure
+
+Failed examples:
+
+rspec ./custom_failure_color_spec.rb:7 # failure fails and uses the custom color
 (RSpec::Expectations::ExpectationNotMetError)
features/formatters/configurable_colors.feature:31:in `Then the failing example is printed in magenta'

Failing Scenarios:
cucumber features/command_line/init.feature:25 # Scenario: Accept and use the recommended settings in `spec_helper` (which are initially commented out)
cucumber features/formatters/configurable_colors.feature:16 # Scenario: Customizing the failure color

Do you think it’s possible to skip loading the global ~/.rspec by RSpec under test, since those options seem to affect it in that way?

require 'rails_helper'

RSpec.describe GramsController, type: :controller 
    describe "grams#update action" do
        it "should allow users to successfully update grams" do
            gram = FactoryBot.create(:gram, message: "Initial Value")
            patch :update, params: { id: gram.id, gram: { message: 'Changed' } }
            expect(response).to redirect_to root_path
            gram.reload
            expect(gram.message).to eq "Changed"
        end

        it "should have http 404 error if the gram cannot be found" do
            patch :update, params: { id: "YOLOSWAG", gram: { message: 'Changed' } }
            expect(response).to have_http_status(:not_found)
        end

        it "should render the edit form with an http status of unprocessable_entity" do
            gram = FactoryBot.create(:gram, message: "Initial Value")
            patch :update, params: { id: gram.id, gram: { message: '' } }
            expect(response).to have_http_status(:unprocessable_entity)
            gram.reload
            expect(gram.message).to eq "Initial Value"
        end
    end

    describe "grams#edit action" do
        it "should successfully show the edit form if the gram is found" do
            gram = FactoryBot.create(:gram)
            get :edit, params: { id: gram.id }
            expect(response).to have_http_status(:success)
        end

        it "should return a 404 error message if the gram is not found" do
            get :edit, params: { id: 'SWAG' }
            expect(response).to have_http_status(:not_found)
        end
    end

    describe "grams#show action" do
        it "should successfully show the page if the gram is found" do
            gram = FactoryBot.create(:gram)
            get :show, params: { id: gram.id }
            expect(response).to have_http_status(:success)
        end

        it "should return a 404 error if the gram is not found" do
            get :show, params: { id: 'TACOCAT' }
            expect(response).to have_http_status(:not_found)
        end
    end

    describe "grams#index action" do
        it "should successfully show the page" do
            get :index
            expect(response).to have_http_status(:success)
        end 
    end

    describe "grams#new action" do

        it "should require users to be logged in" do
            get :new
            expect(response).to redirect_to new_user_session_path
        end

        it "should successfully show the new form" do
            user = FactoryBot.create(:user)
            sign_in user

            get :new
            expect(response).to have_http_status(:success)
        end
    end

    describe "grams#create action" do

        it "should require users to be logged in" do
            post :create, params: { gram: { message: "Hello" } }
            expect(response).to redirect_to new_user_session_path
        end

        it "should successfully create a new gram in our database" do
            user = FactoryBot.create(:user)
            sign_in user

            post :create, params: { gram: { message: 'Hello!' } }
            expect(response).to redirect_to root_path

            gram = Gram.last
            expect(gram.message).to eq("Hello!")
            expect(gram.user).to eq(user)
        end

        it "should properly deal with validation errors" do
            user = FactoryBot.create(:user)
            sign_in user

            post :create, params: { gram: { message: '' } }
            expect(response).to have_http_status(:unprocessable_entity)
            expect(Gram.count).to eq Gram.count
        end
    end
end

1 ответ

Лучший ответ

require 'rails_helper'

RSpec.describe GramsController, type: :controller do
    describe "grams#update action" do
        it "should allow users to successfully update grams" do
            gram = FactoryBot.create(:gram, message: "Initial Value")
            patch :update, params: { id: gram.id, gram: { message: 'Changed' } }
            expect(response).to redirect_to root_path
            gram.reload
            expect(gram.message).to eq "Changed"
        end

        it "should have http 404 error if the gram cannot be found" do
            patch :update, params: { id: "YOLOSWAG", gram: { message: 'Changed' } }
            expect(response).to have_http_status(:not_found)
        end

        it "should render the edit form with an http status of unprocessable_entity" do
            gram = FactoryBot.create(:gram, message: "Initial Value")
            patch :update, params: { id: gram.id, gram: { message: '' } }
            expect(response).to have_http_status(:unprocessable_entity)
            gram.reload
            expect(gram.message).to eq "Initial Value"
        end
    end

    describe "grams#edit action" do
        it "should successfully show the edit form if the gram is found" do
            gram = FactoryBot.create(:gram)
            get :edit, params: { id: gram.id }
            expect(response).to have_http_status(:success)
        end

        it "should return a 404 error message if the gram is not found" do
            get :edit, params: { id: 'SWAG' }
            expect(response).to have_http_status(:not_found)
        end
    end

    describe "grams#show action" do
        it "should successfully show the page if the gram is found" do
            gram = FactoryBot.create(:gram)
            get :show, params: { id: gram.id }
            expect(response).to have_http_status(:success)
        end

        it "should return a 404 error if the gram is not found" do
            get :show, params: { id: 'TACOCAT' }
            expect(response).to have_http_status(:not_found)
        end
    end

    describe "grams#index action" do
        it "should successfully show the page" do
            get :index
            expect(response).to have_http_status(:success)
        end 
    end

    describe "grams#new action" do

        it "should require users to be logged in" do
            get :new
            expect(response).to redirect_to new_user_session_path
        end

        it "should successfully show the new form" do
            user = FactoryBot.create(:user)
            sign_in user

            get :new
            expect(response).to have_http_status(:success)
        end
    end

    describe "grams#create action" do

        it "should require users to be logged in" do
            post :create, params: { gram: { message: "Hello" } }
            expect(response).to redirect_to new_user_session_path
        end

        it "should successfully create a new gram in our database" do
            user = FactoryBot.create(:user)
            sign_in user

            post :create, params: { gram: { message: 'Hello!' } }
            expect(response).to redirect_to root_path

            gram = Gram.last
            expect(gram.message).to eq("Hello!")
            expect(gram.user).to eq(user)
        end

        it "should properly deal with validation errors" do
            user = FactoryBot.create(:user)
            sign_in user

            post :create, params: { gram: { message: '' } }
            expect(response).to have_http_status(:unprocessable_entity)
            expect(Gram.count).to eq Gram.count
        end
    end
end

what’s happened

When I ran the test with the rspec command, I suddenly got an error like the title, even though I was able to run it without any problems.
As a result, I found out that it was due to bundle update. As a person who casually did a bundle update, I felt like «I got an error even though I didn’t do anything».

Below is the result output when the rspec command is executed

$ rspec spec/models/task_spec.rb 
 
 An error occurred while loading ./spec/models/task_spec.rb.
 Hint: Install the `did_you_mean` gem in order to provide suggestions for similarly named files.
 Failure/Error: require File.expand_path('../config/environment', __dir__)
 
 LoadError:
   cannot load such file -- public_suffix
 # ./config/application.rb:7:in `<top (required)>'
 # ./config/environment.rb:2:in `require_relative'
 # ./config/environment.rb:2:in `<top (required)>'
 # ./spec/rails_helper.rb:5:in `<top (required)>'
 # ./spec/models/task_spec.rb:1:in `<top (required)>'
 No examples found.
 
 Finished in 0.00005 seconds (files took 1.39 seconds to load)
 0 examples, 0 failures, 1 error occurred outside of examples

Solutions

I will write the solution first
The problem with this error is the version of the library
As it says cannot load such file --public_suffix, the library called public_suffix cannot be loaded because of the version.
In my case it was public_suffix (4.0.6) at the time of the error
Looking at the previous commit without any error, it was public_suffix (4.0.5), so change from Gemfile.lock to public_suffix (4.0.6) → public_suffix (4.0.5) Run bundle install

When I run the test with rspec again

$ rspec spec/models/task_spec.rb 
 
 An error occurred while loading ./spec/models/task_spec.rb.
 Hint: Install the `did_you_mean` gem in order to provide suggestions for similarly named files.
 Failure/Error: require 'rspec/rails'
 
 LoadError:
   cannot load such file -- minitest/assertions
 # ./spec/rails_helper.rb:8:in `<top (required)>'
 # ./spec/models/task_spec.rb:1:in `<top (required)>'
 No examples found.
 
 Finished in 0.00013 seconds (files took 2.54 seconds to load)
 0 examples, 0 failures, 1 error occurred outside of examples

And I got an error again, but I will fix the version of cannot load such file --minitest / assertions and minitest in the same way as public_suffix.
In my case, I changed it from minitest (5.14.2) to minitest (5.14.1)
Also bundle install and run rspec

$ rspec spec/models/task_spec.rb 
 
 Task
Hoge 2
 
 Finished in 0.00808 seconds (files took 1.99 seconds to load)
 1 example, 0 failures

Passed! Fixed: joy:

What I did to solve the cause

Below, I will write why this error occurred and what kind of search I tried to solve.

The essence of the problem is not Failure / Error: require File.expand_path ('../ config / environment', __dir__), but cannot load such file --public_suffix
I have a library called public_suffix, but the problem was that it wasn’t loaded.
Just look at Gemfile.lock and it’s installed. So is the version different? I came up with the idea and solved it

At first, I thought it was an error and searched for Failure / Error: require File.expand_path ('../ config / environment', __dir__).
Therefore, it is included in the title. However, searching did not solve the problem, I only knew that it was not a problem on the rspec side.

Even if I introduced rspec again from the initial project with rails new, the error did not disappear, so it was clear from this that it was not a problem with rspec.

After struggling for about 6 hours, I realized that Failure / Error: require File.expand_path ('../ config / environment', __dir__) was a side effect of the essential problem, so Load Error: cannot load such file- --I realized that public_suffix is the essence of the error
I didn’t know that public_suffix was a library, so I thought it was an error, which is why it took a long time to resolve.
After that, I searched Gemfile.lock with public_suffix and noticed that the version was different compared to the previous commit, so I returned it and it was fixed.

By the way, searching for Failure / Error: require File.expand_path ('../ config / environment', __dir__) did not solve the problem, so I wrote this article for those who got the same error. Tata

Lesson

Let’s quit the innocent bundle update!
The cause of the error was a change in the version of the library, so if you suddenly get an error, suspect the version.
In the first place, I did not understand the behavior around bundle, and it was the worst element that I used somehow.
I had a pain in the bundle so I studied in this article
https://qiita.com/lasershow/items/1a048d03ddaaba98171e

appendix

Gemfile and Gemfile.lock which fixed the versions of public_suffix and minitest so that rspec works.

Gemfile

ruby '2.6.5'
 gem 'bootstrap', '4.5.2'
 gem 'slim-rails', '3.2.0'
 gem 'html2slim', '0.2.0'
 gem 'enum_help', '0.0.17'
 
 gem 'rails', '~> 6.0.1'
 gem 'pg', '>= 0.18', '< 2.0'
 gem 'puma', '~> 4.1'
 gem 'sass-rails', '>= 6'
 gem 'webpacker', '~> 4.0'
 gem 'turbolinks', '~> 5'
 gem 'jbuilder', '~> 2.7'
 gem 'bootsnap', '>= 1.4.2'
 
 group :development, :test do
   gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
 end
 
 group :development do
   gem 'web-console', '>= 3.3.0'
   gem 'listen', '>= 3.0.5', '< 3.2'
   gem 'spring'
   gem 'spring-watcher-listen', '~> 2.0.0'
 end
 
 group :test do
   gem 'capybara', '>= 2.15'
   gem 'selenium-webdriver'
   gem 'webdrivers'
   gem 'rspec-rails', '< 4.0.0'
 end
 
 gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]

Gemfile.lock

GEM
  remote: https://rubygems.org/
  specs:
    actioncable (6.0.3.4)
      actionpack (= 6.0.3.4)
      nio4r (~> 2.0)
      websocket-driver (>= 0.6.1)
    actionmailbox (6.0.3.4)
      actionpack (= 6.0.3.4)
      activejob (= 6.0.3.4)
      activerecord (= 6.0.3.4)
      activestorage (= 6.0.3.4)
      activesupport (= 6.0.3.4)
      mail (>= 2.7.1)
    actionmailer (6.0.3.4)
      actionpack (= 6.0.3.4)
      actionview (= 6.0.3.4)
      activejob (= 6.0.3.4)
      mail (~> 2.5, >= 2.5.4)
      rails-dom-testing (~> 2.0)
    actionpack (6.0.3.4)
      actionview (= 6.0.3.4)
      activesupport (= 6.0.3.4)
      rack (~> 2.0, >= 2.0.8)
      rack-test (>= 0.6.3)
      rails-dom-testing (~> 2.0)
      rails-html-sanitizer (~> 1.0, >= 1.2.0)
    actiontext (6.0.3.4)
      actionpack (= 6.0.3.4)
      activerecord (= 6.0.3.4)
      activestorage (= 6.0.3.4)
      activesupport (= 6.0.3.4)
      nokogiri (>= 1.8.5)
    actionview (6.0.3.4)
      activesupport (= 6.0.3.4)
      builder (~> 3.1)
      erubi (~> 1.4)
      rails-dom-testing (~> 2.0)
      rails-html-sanitizer (~> 1.1, >= 1.2.0)
    activejob (6.0.3.4)
      activesupport (= 6.0.3.4)
      globalid (>= 0.3.6)
    activemodel (6.0.3.4)
      activesupport (= 6.0.3.4)
    activerecord (6.0.3.4)
      activemodel (= 6.0.3.4)
      activesupport (= 6.0.3.4)
    activestorage (6.0.3.4)
      actionpack (= 6.0.3.4)
      activejob (= 6.0.3.4)
      activerecord (= 6.0.3.4)
      marcel (~> 0.3.1)
    activesupport (6.0.3.4)
      concurrent-ruby (~> 1.0, >= 1.0.2)
      i18n (>= 0.7, < 2)
      minitest (~> 5.1)
      tzinfo (~> 1.1)
      zeitwerk (~> 2.2, >= 2.2.2)
    addressable (2.7.0)
      public_suffix (>= 2.0.2, < 5.0)
    autoprefixer-rails (10.0.1.0)
      execjs
    bindex (0.8.1)
    bootsnap (1.4.8)
      msgpack (~> 1.0)
    bootstrap (4.5.2)
      autoprefixer-rails (>= 9.1.0)
      popper_js (>= 1.14.3, < 2)
      sassc-rails (>= 2.0.0)
    builder (3.2.4)
    byebug (11.1.3)
    capybara (3.33.0)
      addressable
      mini_mime (>= 0.1.3)
      nokogiri (~> 1.8)
      rack (>= 1.6.0)
      rack-test (>= 0.6.3)
      regexp_parser (~> 1.5)
      xpath (~> 3.2)
    childprocess (3.0.0)
    concurrent-ruby (1.1.7)
    crass (1.0.6)
    diff-lcs (1.4.4)
    enum_help (0.0.17)
      activesupport (>= 3.0.0)
    erubi (1.9.0)
    execjs (2.7.0)
    ffi (1.13.1)
    globalid (0.4.2)
      activesupport (>= 4.2.0)
    hpricot (0.8.6)
    html2slim (0.2.0)
      hpricot
    i18n (1.8.5)
      concurrent-ruby (~> 1.0)
    jbuilder (2.10.1)
      activesupport (>= 5.0.0)
    listen (3.1.5)
      rb-fsevent (~> 0.9, >= 0.9.4)
      rb-inotify (~> 0.9, >= 0.9.7)
      ruby_dep (~> 1.2)
    loofah (2.7.0)
      crass (~> 1.0.2)
      nokogiri (>= 1.5.9)
    mail (2.7.1)
      mini_mime (>= 0.1.1)
    marcel (0.3.3)
      mimemagic (~> 0.3.2)
    method_source (1.0.0)
    mimemagic (0.3.5)
    mini_mime (1.0.2)
    mini_portile2 (2.4.0)
    minitest (5.14.1)
    msgpack (1.3.3)
    nio4r (2.5.4)
    nokogiri (1.10.10)
      mini_portile2 (~> 2.4.0)
    pg (1.2.3)
    popper_js (1.16.0)
    public_suffix (4.0.5)
    puma (4.3.6)
      nio4r (~> 2.0)
    rack (2.2.3)
    rack-proxy (0.6.5)
      rack
    rack-test (1.1.0)
      rack (>= 1.0, < 3)
    rails (6.0.3.4)
      actioncable (= 6.0.3.4)
      actionmailbox (= 6.0.3.4)
      actionmailer (= 6.0.3.4)
      actionpack (= 6.0.3.4)
      actiontext (= 6.0.3.4)
      actionview (= 6.0.3.4)
      activejob (= 6.0.3.4)
      activemodel (= 6.0.3.4)
      activerecord (= 6.0.3.4)
      activestorage (= 6.0.3.4)
      activesupport (= 6.0.3.4)
      bundler (>= 1.3.0)
      railties (= 6.0.3.4)
      sprockets-rails (>= 2.0.0)
    rails-dom-testing (2.0.3)
      activesupport (>= 4.2.0)
      nokogiri (>= 1.6)
    rails-html-sanitizer (1.3.0)
      loofah (~> 2.3)
    railties (6.0.3.4)
      actionpack (= 6.0.3.4)
      activesupport (= 6.0.3.4)
      method_source
      rake (>= 0.8.7)
      thor (>= 0.20.3, < 2.0)
    rake (13.0.1)
    rb-fsevent (0.10.4)
    rb-inotify (0.10.1)
      ffi (~> 1.0)
    regexp_parser (1.8.1)
    rspec-core (3.9.3)
      rspec-support (~> 3.9.3)
    rspec-expectations (3.9.2)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.9.0)
    rspec-mocks (3.9.1)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.9.0)
    rspec-rails (3.9.1)
      actionpack (>= 3.0)
      activesupport (>= 3.0)
      railties (>= 3.0)
      rspec-core (~> 3.9.0)
      rspec-expectations (~> 3.9.0)
      rspec-mocks (~> 3.9.0)
      rspec-support (~> 3.9.0)
    rspec-support (3.9.3)
    ruby_dep (1.5.0)
    rubyzip (2.3.0)
    sass-rails (6.0.0)
      sassc-rails (~> 2.1, >= 2.1.1)
    sassc (2.4.0)
      ffi (~> 1.9)
    sassc-rails (2.1.2)
      railties (>= 4.0.0)
      sassc (>= 2.0)
      sprockets (> 3.0)
      sprockets-rails
      tilt
    selenium-webdriver (3.142.7)
      childprocess (>= 0.5, < 4.0)
      rubyzip (>= 1.2.2)
    slim (4.1.0)
      temple (>= 0.7.6, < 0.9)
      tilt (>= 2.0.6, < 2.1)
    slim-rails (3.2.0)
      actionpack (>= 3.1)
      railties (>= 3.1)
      slim (>= 3.0, < 5.0)
    spring (2.1.1)
    spring-watcher-listen (2.0.1)
      listen (>= 2.7, < 4.0)
      spring (>= 1.2, < 3.0)
    sprockets (4.0.2)
      concurrent-ruby (~> 1.0)
      rack (> 1, < 3)
    sprockets-rails (3.2.2)
      actionpack (>= 4.0)
      activesupport (>= 4.0)
      sprockets (>= 3.0.0)
    temple (0.8.2)
    thor (1.0.1)
    thread_safe (0.3.6)
    tilt (2.0.10)
    turbolinks (5.2.1)
      turbolinks-source (~> 5.2)
    turbolinks-source (5.2.0)
    tzinfo (1.2.7)
      thread_safe (~> 0.1)
    web-console (4.0.4)
      actionview (>= 6.0.0)
      activemodel (>= 6.0.0)
      bindex (>= 0.4.0)
      railties (>= 6.0.0)
    webdrivers (4.4.1)
      nokogiri (~> 1.6)
      rubyzip (>= 1.3.0)
      selenium-webdriver (>= 3.0, < 4.0)
    webpacker (4.3.0)
      activesupport (>= 4.2)
      rack-proxy (>= 0.6.1)
      railties (>= 4.2)
    websocket-driver (0.7.3)
      websocket-extensions (>= 0.1.0)
    websocket-extensions (0.1.5)
    xpath (3.2.0)
      nokogiri (~> 1.8)
    zeitwerk (2.4.0)

PLATFORMS
  ruby

DEPENDENCIES
  bootsnap (>= 1.4.2)
  bootstrap (= 4.5.2)
  byebug
  capybara (>= 2.15)
  enum_help (= 0.0.17)
  html2slim (= 0.2.0)
  jbuilder (~> 2.7)
  listen (>= 3.0.5, < 3.2)
  pg (>= 0.18, < 2.0)
  puma (~> 4.1)
  rails (~> 6.0.1)
  rspec-rails (< 4.0.0)
  sass-rails (>= 6)
  selenium-webdriver
  slim-rails (= 3.2.0)
  spring
  spring-watcher-listen (~> 2.0.0)
  turbolinks (~> 5)
  tzinfo-data
  web-console (>= 3.3.0)
  webdrivers
  webpacker (~> 4.0)

RUBY VERSION
   ruby 2.6.5p114

BUNDLED WITH
   2.1.4