notable | Track notable requests and background jobs | REST library

It works fine for me.

It seems that you have a cache configuration issue with stimulus_reflex gem when you run the rspec command:

Stimulus Reflex requires caching to be enabled. Caching allows the session to be modified during ActionCable requests. To enable caching in development, run: rails dev:cache

If you know what you are doing and you want to start the application anyway, you can create a StimulusReflex initializer with the command:

bundle exec rails generate stimulus_reflex:config

Then open your initializer at

/config/initializers/stimulus_reflex.rb

and then add the following directive:

StimulusReflex.configure do |config| config.on_failed_sanity_checks = :warn end

No examples found.

Try replacing this part of config/environments/test.rb:

You need to do:

It seems that the newest version of Flask (currently 2.0.1) has problem with dependencies.

The problem was resolved after downgrading it to 1.1.2 via the following command:

There is indeed a difference between the patterns that are accepted by -S (strings by default, can be changed to a regexp using --pickaxe-regexp) and -G (always interpreted as regexp), but, while both these options build on "searching for that pattern in the diff of each commit", they have a deeper difference :

• -G will report any commit where at least one of the diff chunks contains a line matching
• -S will count the total numbber of added lines which match, count the total number of deleted lines which match, and will report a commit only if these two counts are different.

There is a pretty explanatory paragraph about the differences between -S and -G in git documentation :

To illustrate the difference between -S --pickaxe-regex and -G, consider a commit with the following diff in the same file:

If you showed your code in full, then I see the following problems in it:

1. You are setting the value incorrectly for the DrawingCommands property. In this property, you do not raise PropertyChanged. The binding in the Button is initialized in the InitializeComponent() method. At this point, the property is empty, and when you set a value to it, the binding cannot find out.

There are two ways to fix this:

• Raise PropertyChanged in the property;
• If you set the property value once in the constructor, then set it immediately in the initializer. Make the property "Read Only". This way, in my opinion, is better.

Thanks to @Gert Arnold's suggestion of disabling proxy creation, I was able to pinpoint that as the smoking gun which fixed the problem.

Working with proxies - EF 6 Microsoft Docs

I found that with proxy creation disabled, it was not necessary to override the SaveChanges() method with the Transaction wrapper. That should match the default EF behavior anyway.

For completeness and for those finding themselves here in the future:

You can disable proxy creation in the initializer of your DbContext class as such:

I found the PHP equivalent of the getSignedUrl method.

You can directly modify the Sound data while playing it, preventing the need to call .play() every frame.