bundle error in rails

Fetching gem metadata from https://rubygems.org/Retrying fetcher due to error (2/4): Errno::EACCES Permission denied @ rb_sysopen - /home/rajan/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/info/treetop
Retrying fetcher due to error (3/4): Errno::EACCES Permission denied @ rb_sysopen - /home/rajan/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/info/treetop
Retrying fetcher due to error (4/4): Errno::EACCES Permission denied @ rb_sysopen - /home/rajan/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/info/treetop
--- ERROR REPORT TEMPLATE -------------------------------------------------------

What did you do?
I ran the command /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/exe/bundle install

What did you expect to happen?
I expected Bundler to...

What happened instead?
Instead, what actually happened was...

Error details
Errno::EACCES: Permission denied @ rb_sysopen - /home/rajan/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/info/treetop
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `initialize'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `open'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `open'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `update'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:63:in `update'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:72:in `update_info'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:42:in `block in dependencies'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/fetcher/compact_index.rb:83:in `call'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/fetcher/compact_index.rb:83:in `block (3 levels) in compact_index_client'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/worker.rb:65:in `call'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/worker.rb:65:in `apply_func'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/worker.rb:60:in `block in process_queue'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/worker.rb:57:in `loop'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/worker.rb:57:in `process_queue'
  /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/worker.rb:29:in `block (2 levels) in initialize'

Environment
Bundler   1.12.0.rc.3
Rubygems  2.2.2
Ruby      2.1.5p273 (2014-11-13 revision 0) [x86_64-linux-gnu]
GEM_HOME  /home/rajan/.gem
GEM_PATH
Git       2.5.0
  Bundler settings

path
Set for the current user (/home/rajan/.bundle/config): "/home/rajan/.gem"
disable_shared_gems
Set for your local app (/home/rajan/app/.bundle/config): true
Set for the current user (/home/rajan/.bundle/config): "true"
orig_path
Set via BUNDLE_ORIG_PATH: "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
--- TEMPLATE END ----------------------------------------------------------------
Unfortunately, an unexpected error occurred, and Bundler cannot continue.
First, try this link to see if there are any existing issue reports for this error:
https://github.com/bundler/bundler/search?q=Permission+denied+%40+rb_sysopen+-+%2Fhome%2Frajan%2F.bundle%2Fcache%2Fcompact_index%2Frubygems.org.443.29b0360b937aa4d161703e6160654e47%2Finfo%2Ftreetop&type=Issues
If there aren't any reports for this error yet, please create copy and paste the report template above into a new issue. Don't forget to anonymize any private data! The new issue form is located at:
https://github.com/bundler/bundler/issues/new
run  bundle exec spring binstub --all
/var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/resolver.rb:356:in block in verify_gemfile_dependencies_are_found!': Could not find gem 'rails (= 4.2.6)' in any of the gem sources listed in your Gemfile or available on this machine. (Bundler::GemNotFound) 	from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/resolver.rb:331:in each'
from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/resolver.rb:331:in verify_gemfile_dependencies_are_found!' 	from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/resolver.rb:200:in start'
from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/resolver.rb:184:in resolve' 	from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/definition.rb:200:in resolve'
from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/definition.rb:140:in specs' 	from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/definition.rb:185:in specs_for'
from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/definition.rb:174:in requested_specs' 	from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/environment.rb:19:in requested_specs'
from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/runtime.rb:14:in setup' 	from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler.rb:95:in setup'
from /var/lib/gems/2.1.0/gems/bundler-1.12.0.rc.3/lib/bundler/setup.rb:19:in <top (required)>' 	from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'

Seems similar in nature to #4431. Might want to follow that issue's resolution course.

@rajan30 does following the resolution course (changing file permissions appropriately) in #4431 resolve your issue?

yes man it did thanks a lot


Fixed issue #27: replace dev PURLs; and recategorized 'US Census trac…

…t region role', 'US county region role', and 'US state region role'.

For some reason, lake, sea, and ocean have redundant classes with different PURLs.

Although we removed 'deontic role' as a parent, the class definitions still mention it, of US census tract region role, US state region role, and US county region role.

@hoganwr what file are you seeing those duplicates in?

I believe it was geo.all
On Thu, Feb 8, 2024 at 12:40 PM Matthew Diller @.***>
wrote:

@hoganwr https://github.com/hoganwr what file are you seeing those
duplicates in?
—
Reply to this email directly, view it on GitHub
https://github.com/mcwdsi/geographical-entity-ontology/pull/28#issuecomment-1934725309,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJR55UA2A26QEPLGW3XTOTYSUL3TAVCNFSM6AAAAABCWXZWPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUG4ZDKMZQHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

also do you plan to fix the textual definitions as I mentioned above?

Yes, I already have fixed them in my local copy of us-integral-geography.owl.


Expose type via SQL adapter

Closes #6208
Exposes type as an UUID columns of every table, including when using FROM ONLY (and we are compiling SQL to load data from tables that actually do not have the __type__ column).
If using SQL adapter only, values of __type__ are useless, as there is not way to query which type is associated with this id, as we don't expose schema::ObjectType (or anything from schema module) over SQL.
TODO:

[x] add introspection

@msullivan this is now ready

If using SQL adapter only, values of __type__ are useless, as there is not way to query which type is associated with this id, as we don't expose schema::ObjectType (or anything from schema module) over SQL.

Oh, lol. Maybe we should not have bothered with this.


pandas-profiling does not support latest version of matplotlib

Missing functionality
Support for latest version of matplotlib, version 3.6.x
Proposed feature
Update dependencies to support latest version of matplotlib
Alternatives considered
No response
Additional context
No response

#1064 appears to fix this issue

Thanks for your quick response @fabclmnt


add .gitignore to application generator

Maybe it makes sense to add .gitignore file in the application generator? In order to node_modules folder was not included in the repository.

I thought we had this. I'm pretty sure I had this at some point but maybe it was removed. I'll add it back.

It is in https://github.com/feathersjs/generator-feathers/tree/master/generators/app/templates/static but I ran into this before. For some weird reason Yeoman does not copy .gitignore files. It has to be called something else and renamed when copying it over.

It's actually not a yeoman issue. It's npm. I fixed it somewhere before. Maybe it was in the plugin generator.

Fixed with e8b0719f45c643227f4139ae545fe00b5ee3ece9


WIP add ica.get_components

closes #3536
@agramfort @mmagnuski @agostontorok

looks good!

Current coverage is 87.28% (diff: 100%)

Merging #3573 into master will decrease coverage by <.01%

@@             master      #3573   diff @@
==========================================
  Files           341        341
  Lines         60139      60139
  Methods           0          0
  Messages          0          0
  Branches       9186       9186
==========================================
- Hits          52495      52493     -2
- Misses         4898       4899     +1
- Partials       2746       2747     +1

Powered by Codecov. Last update 7cd5d0e...39e5cf8

@agramfort okay?

@jona-sassenhagen you need a rebase. Will you have time for it in the next couple of days so it makes it into the release?

Jona is on holidays until next week but I may have time to take over.
On Fri, 16 Sep 2016 at 16:09, Eric Larson<EMAIL_ADDRESS>wrote:

@jona-sassenhagen https://github.com/jona-sassenhagen you need a
rebase. Will you have time for it in the next couple of days so it makes it
into the release?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-247610173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fivi0Co4J96N2y7ahEHmq8M4K08bRks5qqqM1gaJpZM4J3bwt
.

This one might need to be pushed out of 0.13, which I think is okay

Removing MRG tag, feel free to put back when it's good to go again

Thanks Eric, I'll try to get back to it soon.

Shouldn't we try to harmonize this kind of method to a SpatialFilterMixin? This is related to get_filters/get_patterns isn't it?

Good point. Is the API settled there?

I think we need to ensure that the spatial filters have a filters_ (and potentially a patterns_), which are either stored, or retrievable from estimator.coef_.
In your ICA case, would it make sense to change your get_components() method into a filters_ attribute?

I think so.

Here get_components returns the mixing matrix so it would be a better fit for patterns_ attribute, right?

Does anything speak against precomputing the mixing matrix, instead of computing it on demand? @dengemann ?

Here get_components returns the mixing matrix so it would be a better fit for patterns_ attribute, right?

yes

Does anything speak against precomputing the mixing matrix, instead of computing it on demand? @dengemann ?

I would precompute it, it's not very costy. Else you'd need to store the data, wouldn't you?

No need to store the data actually - mixing matrix is the inverse of unmixing matrix and the computation done by get_components is just to get rid of the split into the mixing matrix and PCA components.
Unless I'm missing something :)

No you got it. The data isn't required. I was just asking because it's not precomputed right now, and maybe there's a reason for that ..?

can someone take this over?

I think we're not 100% sure over the API yet. Do I understand correctly

ICA should pre-compute the components
these should be accessible under either .filters or .patterns

?

Why the heck all this?
On Fri, 25 Nov 2016 at 18:09, jona-sassenhagen<EMAIL_ADDRESS>wrote:

I think we're not 100% sure over the API yet. Do I understand correctly

ICA should pre-compute the components
these should be accessible under either .filters or .patterns

?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-262999561,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fink1SjJ9GpZcNR0HGdIlkwE3dQDsks5rBxZIgaJpZM4J3bwt
.

See discussion above- I actually pinged you on Oct 14th :)

Ok I see. Can we chat for a second?
On Fri, 25 Nov 2016 at 18:13, jona-sassenhagen<EMAIL_ADDRESS>wrote:

See discussion above- I actually pinged you on Oct 14th :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263000071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0filWFyA9NWb6fxBecl2OSC_--wMP5ks5rBxdBgaJpZM4J3bwt
.

Ok guys, I'm fine with this. But to me we should carefully think about
whether to have a function or not.
We already expose the components (As in sklearn) and the added value is
having the matrix that undoes the PCA-ICA transform and gives you sensor
maps. If there is anything related to prewhitening/scaling that could be
essentialn and optional, a function would be API-safe. An attribute not. If
we are 1000% sure that this is the one and only way to expose the maps,
.patterns_ or so should be fine.
To me we should only do one thing, not an attribute and a function.
On Fri, Nov 25, 2016 at 6:17 PM Denis-Alexander Engemann <
<EMAIL_ADDRESS>wrote:

Ok I see. Can we chat for a second?
On Fri, 25 Nov 2016 at 18:13, jona-sassenhagen<EMAIL_ADDRESS>wrote:
See discussion above- I actually pinged you on Oct 14th :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263000071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0filWFyA9NWb6fxBecl2OSC_--wMP5ks5rBxdBgaJpZM4J3bwt
.

as I said above. A get_components or get_filters method is fine with me. I
am fine it returns a plain array if it's compatible with the ica.info
attribute eg mne.EpochsArray(components, ica.info, ...) works

While we are at it, get_components would be sort of wrong, the ICA object
exposes them already. get_filters seems wrong as you actually want to show
the patterns and for this invert the PCA-ICA pipeline -- get_patterns?
On Fri, 25 Nov 2016 at 20:37, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

as I said above. A get_components or get_filters method is fine with me. I
am fine it returns a plain array if it's compatible with the ica.info
attribute eg mne.EpochsArray(components, ica.info, ...) works
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263014844,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fitbC-Q581a6NLipEfjzaLUx8qXFBks5rBzj7gaJpZM4J3bwt
.

the ICA object exposes them already.

to me it does not. You have a plot_components but you don't have access to
arrays

The ICA components have been available as attributes already for years.
Plot components is plotting them by reversing the transforms to sensor
data.
On Fri, 25 Nov 2016 at 20:48, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

the ICA object exposes them already.

to me it does not. You have a plot_components but you don't have access to
arrays
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263015796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fioh4VPhBV7ytT5ZGDDVuqzOZl_TLks5rBzt3gaJpZM4J3bwt
.

I seriously doubt this. See the complexity of plot_ica_components code...

Yes this is what I am trying to tell you. And the raw ICA components are
already available as such. Plot components is in this regard not a good
name. But what wan we do? I agree though that get_
and plot should have related names, so
get_components would be ok.
On Fri, 25 Nov 2016 at 20:54, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

I seriously doubt this. See the complexity of plot_ica_components code...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263016348,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fimYUZMNxbyH7XslG-EGdNxcrng4dks5rBzz5gaJpZM4J3bwt
.

get_components would be ok.

glad you agree :)

As I said adding a method would be more API-safe, hence, sustainable. So we
have a preference for the method option it seems. With get_components both
names are at least equal.
On Fri, 25 Nov 2016 at 22:08, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

get_components would be ok.

glad you agree :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263022628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fiqS2YzfSz5JiGgv6tieSWLDBGrDsks5rB05ngaJpZM4J3bwt
.

@kingjr @mmagnuski are you happy with this solution (method rather than attribute)?

no strong opinion

Let's just make it public then as initially discussed, seems to have the
highest total consensus.
On Tue, Nov 29, 2016 at 5:00 PM Jean-Rémi KING<EMAIL_ADDRESS>wrote:

no strong opinion
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263611719,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fivXgUHifv6ix8ipGElBvZvx-V6F6ks5rDEwrgaJpZM4J3bwt
.

I'm ok with public method. Would it be get_patterns or get_components?
get_components is more intuitive in the context of ICA, although less consistent with filters vs patterns general distinction.

We agreed on .get_components it seems. It emphasizes that it is the same
thing as .plot_components
On Tue, Nov 29, 2016 at 8:55 PM Mikolaj Magnuski<EMAIL_ADDRESS>wrote:

I'm ok with public method. Would it be get_patterns or get_components?
get_components is more intuitive in the context of ICA, although less
consistent with filters vs patterns general distinction.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3573#issuecomment-263680169,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fivLqnG8bFQBgL95lmBEJeCqZy4UTks5rDIMmgaJpZM4J3bwt
.

Closing for a new PR cause we had a lot of discussion.


addEventListener not a function!

is this module not maintained anymore? when I want to use the addEventListener method, it throws an error that it's not a function!

This module returns either the window if you are in a browser or the global object in node.
Since global in node has no method called addEventListener, it will throw error.
$> node -pe 'global.addEventListener'
undefined

We won't simulate the window in node, nor the global in the browser.


IN PROGRESS: Do not crash when wallet is down

Today, when a bitcoind is down the api just crashes and returns html.
For some endpoints, like balance it could still return whatever data it can find, while for others it can instead return a nice json message.

For my understanding, it needs a better exception handling.
After having a short investigation on

python-bitcoinrpc - https://pypi.python.org/pypi/python-bitcoinrpc/1.0 (currently we use).
bitcoin-python, https://github.com/laanwj/bitcoin-python

What I have found:

Bitcoin-python have a better exception handling implemention.
Bitcoin-python supports Python 3.

Conclusion: I should go for bitcoin-python.
I will do an experimental implementation.

Looks like https://github.com/laanwj/bitcoin-python is not actively maintained and instead it recommends
https://github.com/petertodd/python-bitcoinlib

Added exception handling for all endpoints when the node client that the call is connecting to is down.


Add AIO function to echo scm prompt char and info

Refactor common code into scm_prompt_info_common
Add AIO function to echo scm prompt char and info.
Invoking the scm_char and scm_prompt_info functions separately for PS1
duplicates calls to the scm and scm_prompt_char functions to check what
${SCM}, if any, we currently reside in. This problem was exacerbated
when working outside of any repo as we had to go through all the
conditionals twice just to determine we're not in any scm repo. Unnecessary
conditionals slows down the prompt so this adds a new function that
streamlines printing out both the scm char and scm prompt info with one
invocation.
Add prefix and suffix capability to SCM char
Update bobby theme to use scm_prompt_char_info.
The bobby theme now uses scm_prompt_char_info to print out the SCM char
and SCM prompt info. This also required fixing the
SCM_THEME_PROMPT_PREFIX to match GIT_THEME_PROMPT_PREFIX.

Good stuff! This means that themes would have to switch to calling the new scm_prompt_info_common function, right?
This would only work for themes that have both of these parts immediately next to each other. Bobby for example has this:
$(scm_char)${green}$(scm_prompt_info)

The ${green} in the middle means that the new all-in-one function can't be used, right?

Every theme can continue calling $(scm_char) and $(scm_prompt_info) and no functionality would change so this is backwards compatible. Only those themes that wanted to take advantage of this would just change to call $(scm_prompt_char_info) instead of $(scm_char) and $(scm_prompt_info).
You're right that this benefits mostly those themes, or future themes, that have these parts somewhat close or next to each other. Doesn't everybody want these next to each other? ;) All that they would have to do is change to call $(scm_prompt_char_info) instead of both $(scm_char) and $(scm_prompt_info) to get the extra speed.
The Bobby theme should probably not be using:
$(scm_char)${green}$(scm_prompt_info)

but instead should define the
SCM_THEME_PROMPT_PREFIX=" |"

to include ${green} before it just like it does for the suffix:
SCM_THEME_PROMPT_SUFFIX="${green}|"

Then Bobby could call $(scm_prompt_char_info) directly without any issues.
In fact, Bobby seems to have a discrepancy because it defines the git version of these variables correctly while the scm versions are not:
GIT_THEME_PROMPT_PREFIX=" ${green}|"
GIT_THEME_PROMPT_SUFFIX="${green}|"

Bobby's SCM_THEME_PROMPT_* equivalent of these variables should be set up to match the GIT_THEME_PROMPT_* ones. Another reason for consolidating SCM_* and GIT_* variables. :)
So to answer your question, Bobby's theme could use the AIO function immediately, but it would only work correctly for git repos until the above discrepancy is fixed.
In the end, I think almost any theme could really use the new AIO as long as they set up their PREFIX and SUFFIX variables correctly. Before creating this PR I had thought about adding a prefix and suffix capability to scm char because I felt like it was missing. I think I will do that so the char and info can be even more flexible. Then, any other theme could potentially define many things between the scm_char and scm_prompt_info stuff.

OK, sounds good. Feel free to add the prefix/suffix functionality in here before I merge.
It would also be good to have one theme using this functionality, so people can see how to apply it.

@nwinkler Do you think you have time to review my last 2 commits and merge this?

@nwinkler Is there somebody else that could merge this? I'd like to get this PR closed so I could submit a new theme PR that would depend on it. Thanks!

Really sorry about the delay... Thanks for the reminder, this is now merged.

@nwinkler Not a problem, thanks!


Adding a new SN prefix for V2 device

Just received a V2 device (manufactured in Dec 2022) and it wasn't being recognized. I added the included changes to the config_flow.py and manifest.json files and it was able to pull the data into HomeAssistant via the esphome ble proxy.
Thanks for the great work! Let me know if I need to update anything else.

It worked on the first update but now it stopped updating after the first one, seemingly related to this issue: https://github.com/jdeath/rd200v2/issues/11

Looks good. I will merge and make a release in a couple days.
Are your ESPHome proxies up to date and running the esp-idf framework? After 2022;12.4 , that bug should be gone. You need to serial flash the first time after changing the framewrork. Also, remove any built in BT adapters from home assistant, apparently Raspberry PI ones have this bug too.
If all else fails, remove the peak and uptime calls from the parser.


to discuss with the team -> challenges = generations of improvements to get to a full prediction model

Our objective is to get notoriety. To have hundreds of submissions and become a source of truth for DeFi traders, among other things
I would suggest that to help DeFi traders make money we need a full comprehensive model of trading.
A comprehensive model of trading includes useful libraries, good data, sound trading strategies, effective backtesting strategies, etc.
We are well positioned and we have different challenges of predict-Eth. So I would like to suggest that we first agree on all that would be needed (a list of our model of trading) and then focus on one theme per challenge. May be we can even repeat the theme down the line to reinforce it (for example, backtesting strategies second edition, etc.)
In my experience a competition can start small but if it improves and is useful it can quickly gain momentum, we had the first run, that was the introduction, the "hello world" so to speak, may be we can discuss where are we focusing on for the coming second round?

We often discuss topics like this in the standup. It's ongoing. Closing this issue.


[FLINK-23305][table]Support semi/anti interval joins

What is the purpose of the change
To support interval joins for semi/anti joins.
Brief change log

Allow converting semi/anti joins to interval joins
When meets semi/anti joins, StreamExecIntervalJoin will translate to corresponding transformations
Add semi/anti interval function in operations

Verifying this change
Many test cases are added to verify this change.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: (no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? not documented

Thanks for your comment, @beyond1920 ! These comments are useful to me. I think the changes in planner are small and the main changes are in runtime operators, and maybe I can split them in the following commits.

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure


Update cmd to check heap after each line

The lomem value does not prevent an executed program from allocating memory into the cmd buffer below $6000.  So after each program line, check the the himem value at the bottom of the heap and abend if it goes below $60.

Updated with check and tested.


Explore Rustls and create an example

Initially we can use RustCrypto to create a Rustls-Crypto-Provider (and later use HW-acceleration) to provide an alternative to mbedtls in cases where embedded-tls isn't enough (e.g. mutual authentication, server functionality etc.)

I have been really busy working on https://github.com/rustls/rustls/pull/2200 to enable building rustls for this kind of target. This is almost ready, with a few remaining XXX / TODO items that I would like to resolve soon. And I have a similar update for rustls-rustcrypto provider working here: https://github.com/brodycj/rustls-rustcrypto/pull/1
Bad news is that there may be some resistance due to the requirement for Rust nightly & issue with the built-in rustls providers: https://github.com/rustls/rustls/issues/2068#issuecomment-2541589795

requires Rust nightly version

Perhaps this isn't a feature ready for mainline Rustls in this case?

One issue is that I had some trouble building the built-in aws-lc-rs & ring providers with the no atomic ptr targets.

I have similar feelings here. If this only works with rustls-rustcrypto, and not the two mainline crypto providers, is it ready to ship?

If they would reject my proposal or put it on hold, this would continue to block progress here.
I personally cannot see why they should reject a feature that could help some people in the embedded Rust community, even if the feature is clearly documented as an "unstable" feature that should only affect those who want to use the feature.
I would really appreciate it if anyone could help support my case to get my proposal accepted and included.
I would surely hate it if we could not use rustls without forking it.

Please note my questions shouldn't be read as intent to reject the proposal. I'm only one maintainer and don't set the project direction. I also haven't made a personal conclusion of whether it should/shouldn't be accepted, I'm only asking questions I think are relevant to evaluating the state of the work as part of a broader discussion.

Thanks @cpu, sorry I didn't see your comment before commenting in the other thread - https://github.com/rustls/rustls/issues/2068#issuecomment-2541917807 - quoting most of it here:

I was hoping to contribute this feature as an unstable feature, and I think there is plenty of precedence for supporting unstable feature options. Here are a couple prime examples that I found from a very quick search, which happen to be within the Rust ecosystem:

https://doc.rust-lang.org/cargo/reference/unstable.html - unstable features in Rust itself
https://docs.deno.com/runtime/reference/cli/unstable_flags/

Yes there would be some special requirements for those who wish to start using this proposed feature, which I don't think should affect anyone else not using this feature.
The one minor caveat I can think of is that someone building rustls with --all-features flag would be affected by this feature. But considering that rustls is a library, I think this could only be an issue with someone building rustls as a stand-alone library build, NOT someone including rustls as a dependency for a higher-level application or library.

@cpu @bjoernQ I don't know which thread would be best for us to continue discussion in, or if it may be better to continue discussion in the PR itself - rustls/rustls#2200
I think the biggest impact could be in the following kinds of stand-alone rustls library builds:

build with all features - I would love to find a way to enable building with all stable features
build with proposed critical-section feature - this would require --cfg option to get the required support from portable-atomic-util::Arc

Alternative could be to use an unstable cfg feature, like I did in this released contribution: https://github.com/taiki-e/portable-atomic/pull/195

I don't know which thread would be best for us to continue discussion in, or if it may be better to continue discussion in the PR itself - https://github.com/rustls/rustls/pull/2200

Let's continue in Rustls#2200 - I just wanted to add context here before anyone got too worked up about an outcome that isn't decided.


Creating an upgradable contract creates 3 transactions

Hello,
When I deploy the Box.sol contract, it creates 3 transactions. I follow these instructions: https://docs.openzeppelin.com/learn/deploying-and-interacting#local-blockchain
Is it normal? I expect only one transaction to be deployed with 1 address. What are the other 2 addresses?

What you are likely seeing is the following three contracts:

The proxy itself
The implementation contract, that is the target of the proxy
A ProxyAdmin contract, that is used to upgrade the proxy

Many Thanks


Changing Orientation Causes Banner to Cover Up Screen

I am using Ionic/Cordova and am adding a banner to the bottom center of my app according to the instructions here:
https://github.com/floatinghotpot/cordova-admob-pro/wiki/01.-How-to-Use-with-Cordova-CLI
I am compiling it to iOS.
When the app is first loaded, the banner appears correctly and pushes the rest of the app upwards to make room for it.
However, if I change my orientation (to landscape), the banner then overlaps the rest of the app. There is no way to get the banner to reappear below the app content without killing the app. This is especially problematic for apps with tabs on the bottom, as the banner will completely cover them.
--
As a workaround:
Does anyone know if removing/re-adding the banner when the orientation changes will work?
Or positioning it at x/y?

If you app is not fixed orientation, you need set option orientationRenew: true when creating the banner.
Explain: orientationRenew, boolean, re-create the banner on web view orientation change (not screen orientation), or else just move the banner.
See more options in the wiki:
https://github.com/floatinghotpot/cordova-admob-pro/wiki/1.2-Method:-AdMob.setOptions()

Thank you! It worked. : )


feat(User): #refreshSessionToken

https://github.com/leancloud/paas/issues/871

Current coverage is 65.51% (diff: 100%)

Merging #435 into master will increase coverage by 0.01%

@@             master       #435   diff @@
==========================================
  Files            32         32
  Lines          2661       2659     -2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           1743       1742     -1
+ Misses          918        917     -1
  Partials          0          0

Powered by Codecov. Last update b1fa63f...1bfaba8


Merge create_update branch

Hello @ericrochow! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file resumeapi/controller.py:

Line 223:80: E501 line too long (86 > 79 characters)
Line 305:80: E501 line too long (84 > 79 characters)
Line 346:80: E501 line too long (81 > 79 characters)
Line 387:80: E501 line too long (86 > 79 characters)
Line 441:80: E501 line too long (83 > 79 characters)
Line 443:80: E501 line too long (82 > 79 characters)
Line 482:80: E501 line too long (82 > 79 characters)
Line 485:80: E501 line too long (85 > 79 characters)
Line 523:80: E501 line too long (84 > 79 characters)
Line 560:80: E501 line too long (84 > 79 characters)
Line 566:80: E501 line too long (84 > 79 characters)
Line 608:80: E501 line too long (84 > 79 characters)
Line 679:80: E501 line too long (86 > 79 characters)
Line 708:80: E501 line too long (81 > 79 characters)
Line 776:80: E501 line too long (87 > 79 characters)
Line 790:80: E501 line too long (84 > 79 characters)
Line 845:80: E501 line too long (80 > 79 characters)
Line 856:80: E501 line too long (86 > 79 characters)
Line 929:80: E501 line too long (87 > 79 characters)
Line 948:80: E501 line too long (82 > 79 characters)
Line 969:80: E501 line too long (84 > 79 characters)
Line 982:80: E501 line too long (84 > 79 characters)
Line 993:80: E501 line too long (82 > 79 characters)
Line 999:80: E501 line too long (84 > 79 characters)

In the file resumeapi/main.py:

Line 91:80: E501 line too long (84 > 79 characters)
Line 403:80: E501 line too long (85 > 79 characters)
Line 414:80: E501 line too long (86 > 79 characters)
Line 578:80: E501 line too long (80 > 79 characters)
Line 595:80: E501 line too long (83 > 79 characters)
Line 606:80: E501 line too long (84 > 79 characters)
Line 612:80: E501 line too long (80 > 79 characters)
Line 691:80: E501 line too long (81 > 79 characters)

In the file resumeapi/schema.py:

Line 109:80: E501 line too long (82 > 79 characters)
Line 297:80: E501 line too long (81 > 79 characters)
Line 298:80: E501 line too long (83 > 79 characters)
Line 299:80: E501 line too long (85 > 79 characters)
Line 300:80: E501 line too long (81 > 79 characters)


error formatting when modifying yaml

There is a small problem with formatting when making changes on the web page
          ports:
            -
              name: http
              containerPort: 80
              protocol: TCP
            -
              name: https
              containerPort: 443
              protocol: TCP

Hey @GounGG. Thanks for using k8dash and for filing the issue. I'm so sorry, but I'm not seeing the issue. It looks like valid YAML to me. Would you mind pointing out where the issue is? Thx!

Closing for now. Please reopen and add a comment if I missed something :)


Advanced deferred customization

This PR extends the DeferredContentExecutorCustomization with two new capabilities:

It can return any other type than Func<IServiceProvider, object>.
It can accept a delegate*<IServiceProvider, object> builder parameter instead of a Func<IServiceProvider, object> one.

Both changes aim to reduce allocations for deferred content. See the upcoming Avalonia PR for details.
.NET 8 has been added as an extra target, because it now handles function pointers in System.Reflection, which requires targeted code.
Corresponding unit tests have been added.
~Note: only the last commit in this PR is relevant, the previous one comes from #106. I've built on that PR due to conflicts, and will rebase to have a clean diff when it gets merged.~ Edit: now rebased

I fought a bit with Mono, but the tests now run correctly:

Updated XUnit runner
Used IntPtr instead of a function pointer to avoid a crash on Mono SRE
Set "shadowCopy": false for the GuiLabs tests to run correctly on Mono

Pipelines have been updated to run net8.0+net6.0+net47.

Rebased onto master.
@kekekeks I'd appreciate your feedback when you have some time, this is the last change remaining before I can open https://github.com/AvaloniaUI/Avalonia/pull/15070


  added to onChange output value

Hi.
<ReactQuill
	onChange={handleDescriptionChange}
	value={stateTextEditor.value}
	formats={formats}
/>

The outputted value is always encapsulated in <p> </p>, even if it contains nothing.
How to do away with this?
Very easy to fix by adding:
value.substring(3, value.length - 4);
on outputted data but this is perhaps still not desired behaviour.
Thanks

Hi. is there another solution by default for that? I want to upload to database without this  tag

Hi. is there another solution by default for that? I want to upload to database without this
tag

same issue. need to help 🤷♀


Use /bigdata/dataloader

Per https://github.com/superphy/backend/issues/187#issuecomment-352147515

Looks like the /bigdata/dataloader API only accepts a xml file with links to the actual rdf graph files https://wiki.blazegraph.com/wiki/index.php/REST_API. This is problematic as it's not a true REST api (the database has to have access to the files on disk, and the files can't be embedded in the POST request). We can work around this by writing some form of a hack, but this would be quite messy.

Abandoned at https://github.com/superphy/backend/commit/5fd3ce884983a9c0cfe3fd79d1a9a72fe598aa4f


feat(cheatcode): startDebugTraceRecording, stopDebugTraceRecording, and getDebugTraceByIndex for ERC4337 testing

Motivation
ERC4337 (account abstraction) has several rules/restrictions on what the UserOperation can do (see: ERC7562). Specifically, it has rules on what opcodes it can access and limitations on certain storage access as well.
These limitations are quite implicit and might not be easily identified during contract development. We want to provide an easier way for developers and security researchers to check/test if the rules are being followed. We aim to enable these checks by running forge test after writing specific tests for that purpose.
Solution

To support this, we need new cheatcodes that can record the debug traces during EVM execution so we can know the opcodes and storages being accessed. With this cheatcode, we will be able to have a helper contract that checks whether the test executions comply with ERC4337 restrictions.
In this solution, we added two cheatcodes:

startDebugTraceRecording: This starts the recording of the debug trace data.
stopAndReturnDebugTraceRecording: This stops and returns the recording of the debug trace data.

Test

An ERC4337 checker tool and its tests are in the repo: https://github.com/boolafish/erc4337-checker/blob/main/test/ERC4337Checker.t.sol

This sounds related to https://github.com/foundry-rs/foundry/issues/6704, tagging it here
Would like to make sure this PR covers the design goals of #6704

@DaniPopes @klkvr just tagging as I am not sure if re-open a PR from WIP will trigger notifications or not. This should be ready and has accommodated the previous review comments. Sorry for taken so long due to OOO and fixing some OOM bugs on my side.

Sorry for the failed CI, have fixed those and tested in my own repo workflow: https://github.com/boolafish/foundry/actions/runs/10535493491?pr=1

@klkvr thanks for the review, should have fixed all comments aside from the one re: more traces were filled than started.

we can try working around this by creating a fake trace node in this situation

Might need a bit more elaboration on this. Not exactly sure how to do this on my end. But will also wait to see if that is the preferred approach I guess.

Hi @klkvr @DaniPopes , just a slight nudge on the review or feedbacks

Hi team, a slight nudge for review again 🙏

bounce this PR again @klkvr @DaniPopes

Looks like the failed CI is from flaky one, I rebased to get the commit from this PR: https://github.com/foundry-rs/foundry/pull/8859.

bump again

bounce again for review 🙏 @klkvr @DaniPopes @mattsse @Evalir

thanks for the review!
Personally I think it will be great to have a way to specify like a --tracer flag to turn on, or, specify tracer config without -vvv. With current limitation, I would imagine project interested to use this will need to isolate the tests by folder and run those separately in CI as verbose mode indeed prints too many stuff.

bounce for review again 🙏

bounce for a review 🙏 @DaniPopes @klkvr

friendly ping again @DaniPopes @klkvr

thanks @klkvr have fixed for the comments. Please take a look when available 🙏

thanks @klkvr for a fast turn-around!!
Have fixed the comment regarding node-step issue. Please take a look when available again 🙏
Can @DaniPopes also help take a look as well for the requested change part 🙏

slight nudge for the review 🙏 (cc @DaniPopes @grandizzy which were tagged by @/klkvr )

Thanks @boolafish! Merging

Thanks all!!


v1.15 Backports 2024-08-12

[ ] #34277 (@aanm)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 34277

/test-backport-1.15


Color flag seems incorrect in the Usage instructions

The Usage section says to do --color=scala-compilation when you run Flamegraph, but that makes it all black and it's hard to distinguish the flamegraph segments:

If I remove that flag, we get nicer colors:

--color= doesn't seem to be a valid flag in the version of Flamegraph I used, so maybe it used to be?
Either way, I'm proposing removing that line from the docs.

Hey @acloudmovingby. I wasn't able to reproduce the issue. I followed these steps:

Cloned the scalacenter/scalac-profiling repository: git clone git@github.com:scalacenter/scalac-profiling.git
cd into the external/Flamegraph directory
Executed the git submodule update --init (an important part)
Run the command including --color=scala-compilation:

/flamegraph.pl \
    --hash --countname="μs" \
    --color=scala-compilation \
    /Users/.../implicit-searches-global.flamegraph > compile-all-modules.svg

I got my coloured graph painted as expected:


Remove unused package property from AndroidManifest.xml files

Since Android Gradle Plugin 8.0, it is recommended to set the namespace in the module's build.gradle file, rather than in its AndroidManifest.xml file.
The namespaces were already set in the build.gradle files, but the package equivalent were still present in the AndroidManifest.xml files.

I have tried removing the package name a while ago during our internal clean-up week, but ran into the following error:
Manifest merger failed: manifest:package attribute is not declared
There might be some setup that prevents us from doing this for now. @icbaker?

We use Blaze internally (which is what Bazel is based on, though it's different) - and yeah these package properties seem to still be needed there.
I think it would be possible to craft some copybara in-line comments that would keep the package properties in the internal version of the code while removing them from this version, but unless there's an issue with them being present I'm afraid it doesn't seem worth the time to make this change in ~100 files.

As an aside, unfortunately merging PRs is a somewhat heavyweight process for us, because we have to run them backwards through Copybara and manually re-insert anything internal-only that was stripped from the touched files. For small changes/clean-ups like https://github.com/androidx/media/pull/1213, https://github.com/androidx/media/pull/1215, and https://github.com/androidx/media/pull/1216 it's actually much quicker if you just file an issue to let us know the problem and we can make the change directly on the internal version of the code. I understand this means you're not as clearly credited in the commit history, so if you would like us to merge these PRs then we can do so, but if you don't mind too much then I can just close them and make equivalent changes directly internally (I've already sent the Guava one for review, but for the others).

Sure, if it's easier to do all the changes internally, go ahead, that's fine for me 🙂

I'm going to close this, because it's too fiddly to merge this while keeping our internal build system working, and there doesn't seem to be a concrete benefit to doing so.


Periodic disconnect when running component continously

Hi all
I can successfully run the component, streaming the RTSP source with no issue.
However, when running the component continously I run into an issue of hitting MAX_CONNECTION_DURATION_REACHED from a putMedia API call every 45 minutes.
The error code Im given looks like this:
2023-04-19 22:13:47 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699718, fragmentNumber='91343852333182056854203719613486539101319954320', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}. {scriptName=services.aws.iot.EdgeConnectorForKVS.lifecycle.Run.Script, serviceName=aws.iot.EdgeConnectorForKVS, currentState=RUNNING}.
From reading through the java code for the SDK, that error should happend when hitting a 10 second timeout on uploading the fragment, but the 45 minute space between each error seems too 'scheduled' to be internet issues. I experience no internet issues in any other part of the setup.
The SiteWise component is configured with the follow setup:
CaptureDurationInMinutes: 15
CaptureStartTime: * * * * *
LiveStreamingDurationInMinutes: 15
LiveStreamingStartTime: * * * * *
LocalDataRetentionPeriodInMinutes: 60
If configured through SiteWise to stream fx 10 minutes every 30 minutes, I experience no issues. It is only when hitting the 45 minute mark.
Any inputs?
Logs:
Log takeout
A log takeout from successfully pushing a fragment to kvs --> the issue happening --> recovering --> succesfully pushing new fragments to kvs looks like this:
...
2023-04-19 22:13:45 INFO  VideoUploaderClient:Fragment pushed to KVS<PHONE_NUMBER>3182056844300199299203496231998391907.
2023-04-19 22:13:45 INFO  VideoUploaderClient:Fragment pushed to KVS<PHONE_NUMBER>3182056849251959456345017676253794223.
2023-04-19 22:13:45 INFO  VideoUploaderClient:onComplete.
2023-04-19 22:13:45 INFO  VideoUploaderClient:putMedia end from latch.
2023-04-19 22:13:47 INFO  Monitor:Monitor removes task: uploadLiveVideo-edge-kvs-stream..
2023-04-19 22:13:47 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699718, fragmentNumber='91343852333182056854203719613486539101319954320', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-19 22:13:47 INFO  LiveVideoStreamingController:InputStream is flushing.
2023-04-19 22:13:47 INFO  LiveVideoStreamingController:Waiting for toggling recorder off.
2023-04-19 22:13:47 INFO  VideoRecorderBase:Recorder0 is unbinding branch branchOutputStreamPath..
2023-04-19 22:13:47 INFO  RecorderBranchBase:Tee and queue unlinked..
2023-04-19 22:13:47 INFO  RecorderBranchBase:Tee pad is releasing..
2023-04-19 22:13:47 INFO  RecorderBranchBase:Tee pad is removed..
2023-04-19 22:13:47 INFO  RecorderBranchBase:Waiting for queues detaching.
2023-04-19 22:13:47 INFO  RecorderBranchBase:All queues are detached..
2023-04-19 22:13:47 INFO  Monitor:Monitor removes task: Recorder0_branchOutputStreamPath..
2023-04-19 22:13:47 INFO  RecorderBranchApp:AppBranch is waiting for EOS..
2023-04-19 22:13:48 WARN  RecorderBranchApp:AppBranch doesn't receive EOS..
2023-04-19 22:13:48 INFO  RecorderBranchBase:Branch queue and branch entry unlinked..
2023-04-19 22:13:48 INFO  RecorderBranchBase:branch queue is stopping..
2023-04-19 22:13:50 INFO  Monitor:Monitor pops up task: Recorder0_branchFilePath..
2023-04-19 22:13:50 INFO  Monitor:Monitor runs task: Recorder0_branchFilePath..
2023-04-19 22:13:50 INFO  Monitor:Monitor has new task: Recorder0_branchFilePath..
2023-04-19 22:13:50 INFO  Monitor:Monitor sends signal to start checking..
2023-04-19 22:14:08 INFO  RecorderBranchBase:branch queue is removed..
2023-04-19 22:14:08 INFO  RecorderBranchBase:branch entry pad is releasing..
2023-04-19 22:14:08 INFO  RecorderBranchBase:branch entry pad is removed..
2023-04-19 22:14:08 INFO  RecorderBranchApp:AppBranch stops muxer.
2023-04-19 22:14:08 INFO  RecorderBranchApp:AppBranch stops appsink.
2023-04-19 22:14:08 INFO  RecorderBranchApp:AppBranch unlink muxer and appsink.
2023-04-19 22:14:08 INFO  RecorderBranchApp:AppBranch removes pipeline.
2023-04-19 22:14:08 INFO  RecorderBranchApp:AppBranch sets null.
2023-04-19 22:14:10 INFO  LiveVideoStreamingController:InputStream is flushed.
2023-04-19 22:14:10 INFO  LiveVideoStreamingController:Toggling recorder off.
2023-04-19 22:14:10 INFO  VideoRecorderBase:Recorder0 is unbinding branch branchOutputStreamPath..
2023-04-19 22:14:10 WARN  RecorderBranchBase:Branch is already unbound..
2023-04-19 22:14:10 INFO  LiveVideoStreamingController:Connected streams for KVS Stream: edge-kvs-stream.
2023-04-19 22:14:10 INFO  VideoRecorderBase:Recorder0 is going to bind branch branchOutputStreamPath..
2023-04-19 22:14:10 INFO  RecorderBranchBase:Branch binds to recorder..
2023-04-19 22:14:10 INFO  RecorderBranchBase:Recorder tee and branch queue linked..
2023-04-19 22:14:10 INFO  RecorderBranchBase:Branch queue and branch entry linked..
2023-04-19 22:14:10 INFO  Monitor:Monitor has new task: Recorder0_branchOutputStreamPath..
2023-04-19 22:14:10 INFO  Monitor:Monitor sends signal to start checking..
2023-04-19 22:14:10 INFO  LiveVideoStreamingController:Turned on outputStream in recorder and start uploading!.
2023-04-19 22:14:10 INFO  Monitor:Monitor has new task: uploadLiveVideo-edge-kvs-stream..
2023-04-19 22:14:10 INFO  VideoUploaderClient:Uploading from input stream, timestamp:<PHONE_NUMBER>581.
2023-04-19 22:14:10 INFO  MergeFragmentVisitor:Wrote segment to output stream.
2023-04-19 22:14:32 INFO  VideoUploaderClient:Fragment pushed to KVS<PHONE_NUMBER>3182061266222019626581847829356139302.
2023-04-19 22:14:32 INFO  VideoUploaderClient:Fragment pushed to KVS<PHONE_NUMBER>3182061271173779783723369228232578654.
...
Complete log
I have edited the above bit for readibility, and uploaded a complete 1 hour log with the issue happening twice here:
https://github.com/SBJakobsen/kvserror/blob/main/aws.iot.EdgeConnectorForKVS_2023_04_19_22_0_edit.log
Test time
After leaving it running overnight it happened the following times from 22.00 to 07.00 :
2023-04-19 22:13:47 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699718, fragmentNumber='91343852333182056854203719613486539101319954320', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-19 22:59:16 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2698720, fragmentNumber='91343852333182071709484191038050571469351590471', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-19 23:44:50 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699279, fragmentNumber='91343852333182086564764662462614603484474608119', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 00:30:28 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699275, fragmentNumber='91343852333182101420045133887178636187613658407', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 01:16:16 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699280, fragmentNumber='91343852333182116275325605311742669922213025474', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 02:01:58 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2698996, fragmentNumber='91343852333182131130606076736306706088129017027', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 02:47:47 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699280, fragmentNumber='91343852333182145985886548160870741166968388705', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 03:33:30 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2700000, fragmentNumber='91343852333182160846118779742576298747019813246', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 04:19:22 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699800, fragmentNumber='91343852333182175696447491009998816193074707273', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 05:05:23 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699878, fragmentNumber='91343852333182190551727962434562857493838125633', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 05:52:28 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699475, fragmentNumber='91343852333182205407008433859126912862319047342', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.
2023-04-20 06:39:38 ERROR LiveVideoStreamingController:Failed to upload stream: AckEvent{ackEventType=ERROR, fragmentTimecode=2699471, fragmentNumber='91343852333182220262288905283690972363804007367', errorCode=MAX_CONNECTION_DURATION_REACHED, errorId=4003}.

Hi SBJakobsen@,
Thanks for reaching out!
The 45 minutes disconnection issue is due to the component is using KVS Client to do the constantly uploading. Due to the restriction of the KVS service, for every 45 minutes, KVS server will terminate the connection for every 45 minutes to refresh the streaming token for most PutMedia/GetMedia use cases.
For more information you can check the link in here: https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/limits.html
So for now this will be the behavior we will run into.
Thanks!

Hi @liyuanqian, thanks for your response.
As my project requires constant livestreaming, I have forked the repo and am working on creating a custom component in order to get around this 45 minute limit.
Im attempting to recover whenever I encounter the MAX_CONNECTION_DURATION_REACHED, by implementing different solutions in the source code. I have primarely been testing solutions in VideoUploaderClient.java, in the actual .doUploadstream() function. It seems, however, that once the error has happened, the inputstream is left in an invalid state, leaving no easy way to just restart sending.
I will be looking into starting a new input stream and connecting this to the outputstream from the recorder as a recovery method, but I feel it's quite likely I will run into issues with the logic surrounding the rest of the component.
Does anyone have any experience with recovering ? Any inputs on easier ways to recover, or perhaps a different solution for a constant livestream to KVS, is greatly appreciated !


Updated and fixed JSDocs

There were a lot of problems with the JSDocs; missing parameters, parameters that didn't exist, references to types that didn't exist, that sort of thing. I fixed most or all of them. Some parameters may need better explanations, but I did the best I could on that end.

Thanks @AMorporkian, really appreciate this work. Sorry for all the comments XD

No problemo. Your fixes have been incorporated.

Hey @AMorporkian v4.0.0 branch is no longer in use  - we merged it into dev branch a couple of weeks back. Appreciate your efforts though man! Can we apply this PR the the dev branch instead? Cheers man! 👍


iOS and browser only: link to privacy and terms on about page

Does not apply to desktop since we link from the menu bar

The menu at the bottom of the page does have the links to privacy and terms


feat: Add docker configs to create-ponder

Adds dockerfile to create-ponder
TODO

[ ] Configure env variables
[ ] Test it out locally
[ ] Test it out deploying docker image to railway/render
[x] Support Postgresql in the docker compose
[ ] Add documentation?

.dockerignore
Copy pasted a dockerignore file.  This helps context be smaller when docker builds which speeds up docker
docker-compose.yaml
This allows us to configure how docker runs in a yaml file instead of command line.  The configuration runs a dev server where if the user changes the code locally the docker container will hot reload
Dockerfile

We optimize the speed of the docker build by only copying lockfile for pnpm so we only rebuild node modules when they change.
The default command is ponder start.
The docker-compose.yaml (since it's used by devs not prod usually) overrides the default with yarn dev while mounting the users filesystem into the docker container.
We chose the node slim image because it's the smallest official node image.  Alpine image would likely work and be smaller but in my experience alpine is way more of a headache to maintain while node-slim "just works"

@eliobricenov added a Docker example project in https://github.com/0xOlias/ponder/pull/293 - thanks for your work on this @roninjin10 🖖

Nice better to show folks how to do it themselves than add it to the template in hindsight


No guidance (nor build infrastructure) to note when rule options are added in specific versions of ESLint

Prelude
I'm aware that we don't specifically want to be strict about noting when rule options are added or changed in particular release versions. I am not advocating that we try to retrofit the entire site with version information. What I want to do is to make individual updates/notes possible (while providing a uniform UX).
Proposal
I would love to see some options for prefixing a paragraph/list option with a "new in version x" icon/text, in such a way that it's uniform across the site. This could simply be text conventions, or it could be something that would get replaced with an icon or otherwise styled during site generation.
The purpose of this would be to allow the team or the community to respond to user confusion when an issue comes in for an option that "does not yet exist" on the rule in the version the user is using. The team or community could add this information only in the place it was needed, without feeling obligated to try to document the ESLint version added for every rule option ever.
Progressing Further
It could be nice to have an option for developers of new features to include a "new in this version" tag/icon/text/whatever, which would transform into "new in version x" during site generation during release. This would allow contributors to note new functionality without making assumptions about what ESLint version will contain the new documentation.
Definitely out of scope for initial implementation.

I think this is a problem, in general, with our documentation. We've never done a good job (or made any attempt) of nothing version differences. That was mostly because we just never sat down and figured out a scaleable way of doing this.
That said, there are a couple of approaches that could work:

Release a version-specific site for each version. The header should probably show the current version and then you can switch between them. We'd end up with URLs like eslint.org/v5.0.0/docs instead of just eslint.org/docs. The problem we'd have to figure out here is how to scale this, because shipping 30 different versions of the site will make cloning/updating the repo a big pain (not to mention confusing for the Algolia search).

We could add a placeholder like "$LATEST$" in the docs where we want the latest version to be added during deploy of the website. As we don't know what the next version will be until deployment, that would have to happen at build time. There is some hairiness around updating the docs and pushing back to the eslint repo, but should be mostly straightforward. The downside of this is that it's totally manual and we'd need to check each PR (though maybe probot could help?).

I personally think the first option is the right way to go even though it's technically more difficult.

Not necessarily advocating for this, but I know Babel moved to Docusaurus a little while ago. Maybe @hzoo can comment on how that's been for the the Babel team.


Misc changes from arch board review meeting for python

• Unify the constructor parameters across languages
• Remove partition_count from the result of get_properties()
• Remove the from_* except for from_connection_string.  Use a different credentials object
• Auto_reconnect should be default=true (this should probably be hidden as well) - ditto for keep_alive_interval - it should be hidden
• In receiver, consumer_group is required - it should be optional (with a default value of $default)
• Consider removing open() in the receiver - just manage the link in .receive() - if not removing open(), then add it to other languages.
• Implement __repr() and __str() for the events that are received
• Support custom decoders on events that we can pass into json decoder
• Remove the receiver.subscribe() for preview - discuss with Johan about design before inclusion
• Rename partition to partition_id (to sync with other languages)

Consider hiding queue_messages() / send_pending_messages() - it's covered by send()

All done except the the following two deferred items.

repr()
"Support custom decoders on events that we can pass into json decoder"

Two separate issues were created for them.


chore(tool): Using semantic release for publishing npm package

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


This script contains malicious content and has been blocked by your antivirus software.

https://github.com/microsoft/azure-pipelines-task-lib/blob/5adadaedd70e68a4130f339e0faf8b8a9a72d273/powershell/VstsTaskSdk/ServerOMFunctions.ps1#L1
At ServerOMFunctions.ps1:1 char:1
+ <#
+ ~~
This script contains malicious content and has been blocked by your antivirus software.

I have no current working theory behind the cause. The agent returns this message during Windows Machine File Copy task. I put in a request for an exemption on this specific script but knowing a theory as to why it became an issue could be helpful.
Thanks.

Hi @kaburkett could you please advise what antivirus software you have and the version of agent?

Carbon Black Cloud : Version <IP_ADDRESS>8

Hi @kaburkett, we have checked the script with www.virustotal.com and nothing suspicious was found. We cannot say why your anti-virus considers it as malicious, maybe you could contact the vendor.

Thanks for your reply.
I followed a Microsoft article on antivirus agent directory exemptions after my initial post.
I will see if the error is still occurring and report back if I uncover any helpful information for future users of windows file copy task.


TypeError: Cannot read property 'length' of undefined

Node version: 4.3.1
OS: Mac EL Captain (10.11.3)
Error is thrown while using grunt-nodemon which has a dependency with "es6-promise" package. Error details are given below,
TypeError: Cannot read property 'length' of undefined
at lib$es6$promise$$internal$$fulfill (/Users/kt/node_modules/grunt-nodemon/node_modules/nodemon/node_modules/es6-promise/dist/es6-promise.js:303:31)
at lib$es6$promise$$internal$$resolve (/Users/kt/node_modules/grunt-nodemon/node_modules/nodemon/node_modules/es6-promise/dist/es6-promise.js:285:9)
at lib$es6$promise$$internal$$invokeCallback (/Users/kt/node_modules/grunt-nodemon/node_modules/nodemon/node_modules/es6-promise/dist/es6-promise.js:396:9)
at /Users/kt/node_modules/grunt-nodemon/node_modules/nodemon/node_modules/es6-promise/dist/es6-promise.js:166:11
at lib$es6$promise$asap$$flush (/Users/kt/node_modules/grunt-nodemon/node_modules/nodemon/node_modules/es6-promise/dist/es6-promise.js:119:9)
at doNTCallback0 (node.js:419:9)
at process._tickDomainCallback (node.js:389:13)
at Function.Module.runMain (module.js:469:11)
at startup (node.js:136:18)
at node.js:963:3

Same issue on node 0.12.4 with the latest version. Let me know how I can help.

Same issue on node 0.10.25. I guess could be realted with https://github.com/karma-runner/karma/issues/1946 not es6-promise.

@wen96 I confirm, same error
TypeError: Cannot read property 'length' of undefined
at lib$es6$promise$$internal$$fulfill (.\node_modules\grunt-ts\node_modules\csproj2ts\node_modules\es6-promise\dist\es6-promise.js:273:31)
at lib$es6$promise$$internal$$resolve (.\node_modules\grunt-ts\node_modules\csproj2ts\node_modules\es6-promise\dist\es6-promise.js:255:9)
at lib$es6$promise$$internal$$invokeCallback (.\node_modules\grunt-ts\node_modules\csproj2ts\node_modules\es6-promise\dist\es6-promise.js:366:9)
at .\node_modules\grunt-ts\node_modules\csproj2ts\node_modules\es6-promise\dist\es6-promise.js:891:13
at lib$es6$promise$asap$$flush (.\node_modules\grunt-ts\node_modules\csproj2ts\node_modules\es6-promise\dist\es6-promise.js:125:9)    at doNTCallback0 (node.js:408:9)
at process._tickCallback (node.js:337:13)

I moved Karma up before Promise and it solved the issue

for me it's related to core-js wich is a transitive dependency of karma. I pinned core-js at 2.1.1 and this way it worked for me.

The issue is indeed related to core-js 2.1.2.
I was able to get rid of the error by adding an npm-shrinkwrap.json along with the package.json, so as to control the version of any package in the dependency tree (documentation):
npm-shrinkwrap.json:
{
  "name": "<your app name>",
  "dependencies": {
    "karma": {
      "version": "0.13.21",
      "dependencies": {
        "core-js": {
          "version": "2.1.1"
        }
      }
    }
  }
}

It's a bug in es6-promise. In feature detection, core-js detected @@species constructor pattern support in Promise#then. es6-promise not supports it and throws an error. Feature detection wrapped in try / catch, but an error throws async.
Reproducible example:
require('es6-promise');
var p = Promise.resolve();
p.constructor = function(it){ it(function(){}, function(){})};
p.constructor[Symbol.species] = function(it){ it(function(){}, function(){})};

try {
  var f = p.then(function(){});
  console.log('works: ', f instanceof p.constructor[Symbol.species]);
} catch(e){
  console.log('caught error');
}

+1

@zloirock I can believe it is an issue with es6-promise, but as a note I think your reproduction is also in error.
I believe as an amendment @@species is no longer available as a static member, only as instance. So Promise.constructor[Symbol.species] will end up just getting ignored.
http://www.ecma-international.org/ecma-262/6.0/#sec-promise.all vs https://tc39.github.io/ecma262/#sec-promise.all

@stefanpenner it's detection @@species in Promise#then

@zloirock are you not placing it on p.constructor[Symbol.species] = function(it){ it(function(){}, function(){})};?

@stefanpenner ?

@zloirock sorry, my point was i don't believe p.constructor[Symbol.species] = <anything> has any impact after the latest amendment to the spec.
The latest iteration of the spec only checks for @@species on the instance (not constructor) see here

the bug described here is totally in es6-promise, although I do believe core-js's detection is also in-error.

@stefanpenner https://github.com/zloirock/core-js/commit/0a144de375c6f14510a127f5abb866847361d179#commitcomment-16290552

@zloirock in the latest iteration of the spec i do not see any reference to constructor[@@species], if memory serves it was actually removed. And only per-instance @@species remains.

@stefanpenner https://tc39.github.io/ecma262/#sec-speciesconstructor

huh, then I think the spec concern wasn't addressed. Ignore me for now

Nothing about removing this.constructor[@@species] - https://gist.github.com/allenwb/8c50729c4c1c158fa8eb https://github.com/rwaldron/tc39-notes/blob/master/es7/2015-11/nov-18.md#improving-consistency-of-species-kevin-smith

Yes these discussion were side-channel, specifically awb and myself discussing this in person. I'll reach out and see if I merely misunderstood our conversation.
Regardless its good that both these issues have been brought to light. I'll work to address both.

+1. Pinning Karma to 0.13.19 seems to work for me

I am most likely going to provide a quick-fix targeting this exact issue shortly, and then circle back with a proper fix later.

+1 for pinning karma to 0.13.19 AND core-js to 2.1.1. Tried just pinning karma alone and that didn't work with our env but the combo of both of them seems to get Jenkins happy for us.

merge a interim solution, will address the larger subclass + constructor tampering problem next.


Integrate BundleBuilder

Integrate bundle builder inside reth: https://github.com/bluealloy/revm/pull/649
comment: https://github.com/paradigmxyz/reth/pull/3512#discussion_r1326447552

I can take it

I can take it

go for it!

Is this still relevant? If so, I can work on it.


What went wrong: A problem occurred evaluating project ':@terrylinla_react-native-sketch-canvas'. > Could not find method provided() for arguments [com.facebook.react:react-native:+] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Please fix this issue in the newest release, i have to change the "provided" to "implementation" every time i run yarn install

patch-package allows you to automate this.
Simply make the change once manually and then run npx patch-package @terrylinla/react-native-sketch-canvas.
This will create a patch file under a new folder patches in the root of your project.
In your package.json, under scripts, add
{
  // ... the rest of your scripts
  "postinstall": "patch-package"
}

This will apply the patch each time you yarn install


Fix #26857: separate stdout from stderr in AzureCliCredential

This PR fixes https://github.com/Azure/azure-sdk-for-python/issues/26857 in the way proposed in https://github.com/Azure/azure-sdk-for-python/issues/26857#issuecomment-1281134407. Essentially, AzureCliCredentials now treats stderr separately from stdout, and therefore if for some reason the call to az was successful but with some warnings, AzureCliCredentials will still work.
I have manually tested that the various error code paths still works like it does currently, by using a mocked az binary.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

Hi @pvaneck - this has been addressed, please review.


Wrong linebreaking

Hi @AndreKoepke,
there's still an issue here. Didn't see that the first time unfortunately. Please have a look again at the "excelLike.pdf" file: In the last line on the cell on the right, the line should not be justified and what is of more importance: the second to last cell in the middle has a strange line breaking – just compare this with the image in the README file.
I am currently working on an automatic comparison of the generated PDF files so that such differences will be detected early on and not only by having a look manually ...
As soon as I'm done I will put all the generated files from the latest version before this change under version control and we will hopefully see that there's a change in the rendered PDF documents.
Best,
Stefan
Originally posted by @vandeseer in https://github.com/vandeseer/easytable/pull/79#issuecomment-599201065

I found the error. If there is only a dot or something as first char, then it breaks.

And found the other bug. With my new wordbreak-algo it shows up. Fix is on the way.

First bug:

Second bug:

Now there is something wrong with the cells-background. But I have no idea what's going wrong.
@vandeseer can you have a look?

(I wrote it in a old-version of easytable, because we are using the old version in a project)

Thanks for your effort @AndreKoepke!
I changed the files accordingly on the current develop branch. Also did I check the issue with the background: It doesn't happen on the most recent version, so that's fine :+1: :smiley:
I will close this issue as soon as I have released the new version.

Version 0.6.3 is published now.


Webpack 4 Deprecation Warning

Hi, i have 2 warning when i use the plugin with webpack 4 :

DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead
webpack-md5-hash\plugin\webpack_md5_hash.js:29:14)

DeprecationWarning: Chunk.mapModules: Use Array.from(chunk.modulesIterable, fn) instead
webpack-md5-hash\plugin\webpack_md5_hash.js:31:52

Using webpack >=4.3, you don't need this plugin anymore.
Just use [contenthash] in your output names.
You can also specify hashes more granular like this: [md5:contenthash:hex:20]

user [md5:contenthash:hex:20], but have the error:
> cross-env NODE_ENV=production webpack --progress --hide-modules -p --config webpack.config.js
     1          2           95% emittingError: ENOENT: no such file or directory, open 'D:\Repo\**\dist\js\chunk\[md5:contenthash:hex:20].js'

@simbo that's specific to the ExtractText plugin. Could you link me to the documentation where [contenthash] is found?

It's also for webpack itself.
Can't find this in the probably outdated docs...
There you go: https://github.com/webpack/webpack/releases/tag/v4.3.0
See also the "unofficial docs": https://survivejs.com/webpack/optimizing/adding-hashes-to-filenames/#placeholders

Thanks man, I appreciate it! Can't find anything on the webpack website itself.


Fix most warnings (especially in 8.13)

I used Pierre-Marie Pédrot's script to add explicit locality to hints (otherwise, there is a warning in 8.13). I also fix or ignore some other warnings that are standard. This lessens the noise generated in CI considerably.

There seems to be a lot of warnings  of the form «  Unused variable x catches more than one case » , for instance in definitions like
Fixpoint mult (alpha beta : T1) :T1 :=
match alpha,beta with
|  zero, y  => zero
|  x, zero => zero
|  ocons zero n _, ocons zero n' _ =>
ocons zero (Peano.pred((S n) * (S n'))) zero
|  ocons a n b, ocons zero n' b' =>
ocons a (Peano.pred((S n) * (S n'))) b
|  ocons a n b, ocons a' n' b' =>
ocons (a + a') n' ((ocons a n b) * b')
end
where  "alpha * beta" := (mult alpha beta) : t1_scope.
Is giving a name to an unused variable (in the right hand side of a match clause) bad style ?
If so, I can replace a lot os such occurrences by the anonymous variable _.
But, as readability is concerned, the second clause of the match looks like the equation x * zero = zero.

Le 5 janv. 2021 à 13:51, Karl Palmskog<EMAIL_ADDRESS>a écrit :
I used Pierre-Marie Pédrot's script to add explicit locality to hints (otherwise, there is a warning in 8.13). I also fix or ignore some other warnings that are standard. This lessens the noise generated in CI considerably.
You can view, comment on, or merge this pull request online at:
https://github.com/coq-community/hydra-battles/pull/18 https://github.com/coq-community/hydra-battles/pull/18
Commit Summary
add explicit hint locality using PMP script to avoid warnings in 8.13
fix double induction deprecation
ignore MathComp-related warnings in _CoqProject and dune
File Changes
M _CoqProject https://github.com/coq-community/hydra-battles/pull/18/files#diff-7bc0f432942f548a20da329bb4e45e21faeeb897fe1d7e0bc26d20210a6e38f1 (3)
M theories/additions/Dichotomy.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-b47ac7d99a5dc506f1467066dd71fdfe19db6d2f295912bb043e5b884df3db67 (2)
M theories/additions/Euclidean_Chains.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-33c0f5d237ab37b1a325af7f3ba6d384707be80760e4e7c3b3f327be3cda4a5f (8)
M theories/additions/Monoid_instances.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-80a19156be5ce150462e7cad6757d78c07c07f81aba618538f5cfcf0fa1c7aa9 (8)
M theories/additions/More_on_positive.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-68e107b85f9e20ed6b72e6627fa1d2a4f276c2755e926c5f327886c6a966cc53 (8)
M theories/additions/dune https://github.com/coq-community/hydra-battles/pull/18/files#diff-a65f793256e07fbc65724fbad7aaf1f2d23c26758b41e740110f98ce6e4c4407 (3)
M theories/ordinals/Epsilon0/Canon.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-a3c461509071085720be95b0eff989e81ad80e2286b8d0d08f41570fbb7dcbe3 (2)
M theories/ordinals/Epsilon0/E0.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-c5af3c921dd03001f94a65d541d4deec780a7f1ab00d3824c742b00f407eea26 (14)
M theories/ordinals/Epsilon0/Epsilon0rpo.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-523f1a085d9d1f2b2337fc4b759cb08255b5463557d6a5f0f0d3c65702ec3f1f (18)
M theories/ordinals/Epsilon0/F_alpha.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-d029435a2aa0c96fc1d0a7b48b287beb3580aad1c9856fb1b9cd456a3bff591e (4)
M theories/ordinals/Epsilon0/H_alpha.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-7a5de3758ace9509337f8e90adb5edef2b7a513d45042f380f726c99b6ce915d (4)
M theories/ordinals/Epsilon0/L_alpha.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-00ece1474a8443838722f48a0c5deb8497cee745697c2e947e75a38d26e4a4db (2)
M theories/ordinals/Epsilon0/Large_Sets_Examples.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-c7026aff7fa26a0240c8e17840dd995dea5f244c93977dd07b8875fa2ed0c227 (2)
M theories/ordinals/Epsilon0/T1.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-cb1a336f3b87bd98e1d8723883ed887d63b1a6a8d4b740a55bb7fea744242a12 (30)
M theories/ordinals/Gamma0/Gamma0.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-98864be563c31d95297a9f311976d5337008bbe2ba6fabaa0ad39e61f9668845 (32)
M theories/ordinals/Gamma0/T2.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-2b991ee7ed06357b17ce15204fae24bf4e08b5bd3a89a7e9533939c07ce82284 (8)
M theories/ordinals/Hydra/Epsilon0_Needed_Free.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-81df98a10d0f01edbbba99dd48bd01112e69d09806c7f95577707118b414de9b (2)
M theories/ordinals/Hydra/Epsilon0_Needed_Generic.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-08e9ceae459dfdc3fd911877774e8594c2439a711e2da472ead8f3d46c885d0e (2)
M theories/ordinals/Hydra/Hydra_Termination.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-4e6c87b8a125f79b1d6b2162df367e808dded503f4edacfc11e1c0fed539cc70 (2)
M theories/ordinals/Hydra/Omega2_Small.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-e2856306d4d8c6c9896c772c233a808a038a952d7337863b780227dff0c28b0b (10)
M theories/ordinals/Hydra/Omega_Small.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-a87f4ba93a5a043a96f9d916ef680a40fc26d5657c7794359e28a16ee22523cd (2)
M theories/ordinals/OrdinalNotations/ON_Generic.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-b6fdbdc73a9fb963e353dd8f13beacfeba9b0cd5c1de810d365fc2b99e3c17cc (2)
M theories/ordinals/OrdinalNotations/ON_Omega2.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-87a5b1dd4c8061d2daa8ee765a522e6dcf566e7ea3e63323e8008581e724b0ba (4)
M theories/ordinals/OrdinalNotations/ON_mult.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-f27db2e205878a8a4a6c3bee4c7b6c06acb2ae4a90917774010b1da187cbb7eb (4)
M theories/ordinals/OrdinalNotations/ON_plus.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-2812a6353f847c1cd11ed782dd67195d93b5fdf2c8ea44b4fc0d6b5c8de61034 (4)
M theories/ordinals/Prelude/MoreLists.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-0659422298e21526e03c893fd0475c72a53034bd1064a00bd99b1a1d46b30986 (2)
M theories/ordinals/Prelude/Sort_spec.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-6cfcfcbcb03df382d7326c3ff99d5966189a657de4308527ae6364501bf1368f (2)
M theories/ordinals/Schutte/AP.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-eebbd06164415dc9298ee3f2e18b30f81a0c2ba24a63c4a6cff0a817f5adedad (4)
M theories/ordinals/Schutte/CNF.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-59d5cf7fdf342381341c40b8fa7a462bd4635d5657a3da976d603b2a555744c2 (4)
M theories/ordinals/Schutte/Ordering_Functions.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-02b4875c36dfa3aa6be37f6dcdbdc075e6fb0b068ff96960da910c7990c99b29 (18)
M theories/ordinals/Schutte/Schutte_basics.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-67d263a508dca5da9bc29ad35f77e3c027c8350535f0356346b9e5befb5263d5 (28)
M theories/ordinals/Schutte/Well_Orders.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-748bd8981ca713c72e71886adc819d0732c81574d4ff3173f4c0d4d3455f2ca4 (2)
M theories/ordinals/primrec/primRec.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-82767788342d2644cb888af55ebd24b85be211ac765428c3e795b5af2f370eca (2)
M theories/ordinals/rpo/list_permut.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-f1ca29f4b0d94949add0649072a9a86628815dd99ca47ee51c44c98c1c582c5d (4)
Patch Links:
https://github.com/coq-community/hydra-battles/pull/18.patch https://github.com/coq-community/hydra-battles/pull/18.patch
https://github.com/coq-community/hydra-battles/pull/18.diff https://github.com/coq-community/hydra-battles/pull/18.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/coq-community/hydra-battles/pull/18, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJW6FCSUQZTW6JGKNFORH7TSYMDNTANCNFSM4VVCD3MA.

There seems to be a lot of warnings  of the form «  Unused variable x catches more than one case » , for instance in definitions like
Fixpoint mult (alpha beta : T1) :T1 :=
match alpha,beta with
|  zero, y  => zero
|  x, zero => zero
|  ocons zero n _, ocons zero n' _ =>
ocons zero (Peano.pred((S n) * (S n'))) zero
|  ocons a n b, ocons zero n' b' =>
ocons a (Peano.pred((S n) * (S n'))) b
|  ocons a n b, ocons a' n' b' =>
ocons (a + a') n' ((ocons a n b) * b')
end
where  "alpha * beta" := (mult alpha beta) : t1_scope.
Is giving a name to an unused variable (in the right hand side of a match clause) bad style ?
If so, I can replace a lot os such occurrences by the anonymous variable _.
But, as readability is concerned, the second clause of the match looks like the equation x * zero = zero.

Le 5 janv. 2021 à 13:51, Karl Palmskog<EMAIL_ADDRESS>a écrit :
I used Pierre-Marie Pédrot's script to add explicit locality to hints (otherwise, there is a warning in 8.13). I also fix or ignore some other warnings that are standard. This lessens the noise generated in CI considerably.
You can view, comment on, or merge this pull request online at:
https://github.com/coq-community/hydra-battles/pull/18 https://github.com/coq-community/hydra-battles/pull/18
Commit Summary
add explicit hint locality using PMP script to avoid warnings in 8.13
fix double induction deprecation
ignore MathComp-related warnings in _CoqProject and dune
File Changes
M _CoqProject https://github.com/coq-community/hydra-battles/pull/18/files#diff-7bc0f432942f548a20da329bb4e45e21faeeb897fe1d7e0bc26d20210a6e38f1 (3)
M theories/additions/Dichotomy.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-b47ac7d99a5dc506f1467066dd71fdfe19db6d2f295912bb043e5b884df3db67 (2)
M theories/additions/Euclidean_Chains.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-33c0f5d237ab37b1a325af7f3ba6d384707be80760e4e7c3b3f327be3cda4a5f (8)
M theories/additions/Monoid_instances.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-80a19156be5ce150462e7cad6757d78c07c07f81aba618538f5cfcf0fa1c7aa9 (8)
M theories/additions/More_on_positive.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-68e107b85f9e20ed6b72e6627fa1d2a4f276c2755e926c5f327886c6a966cc53 (8)
M theories/additions/dune https://github.com/coq-community/hydra-battles/pull/18/files#diff-a65f793256e07fbc65724fbad7aaf1f2d23c26758b41e740110f98ce6e4c4407 (3)
M theories/ordinals/Epsilon0/Canon.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-a3c461509071085720be95b0eff989e81ad80e2286b8d0d08f41570fbb7dcbe3 (2)
M theories/ordinals/Epsilon0/E0.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-c5af3c921dd03001f94a65d541d4deec780a7f1ab00d3824c742b00f407eea26 (14)
M theories/ordinals/Epsilon0/Epsilon0rpo.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-523f1a085d9d1f2b2337fc4b759cb08255b5463557d6a5f0f0d3c65702ec3f1f (18)
M theories/ordinals/Epsilon0/F_alpha.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-d029435a2aa0c96fc1d0a7b48b287beb3580aad1c9856fb1b9cd456a3bff591e (4)
M theories/ordinals/Epsilon0/H_alpha.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-7a5de3758ace9509337f8e90adb5edef2b7a513d45042f380f726c99b6ce915d (4)
M theories/ordinals/Epsilon0/L_alpha.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-00ece1474a8443838722f48a0c5deb8497cee745697c2e947e75a38d26e4a4db (2)
M theories/ordinals/Epsilon0/Large_Sets_Examples.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-c7026aff7fa26a0240c8e17840dd995dea5f244c93977dd07b8875fa2ed0c227 (2)
M theories/ordinals/Epsilon0/T1.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-cb1a336f3b87bd98e1d8723883ed887d63b1a6a8d4b740a55bb7fea744242a12 (30)
M theories/ordinals/Gamma0/Gamma0.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-98864be563c31d95297a9f311976d5337008bbe2ba6fabaa0ad39e61f9668845 (32)
M theories/ordinals/Gamma0/T2.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-2b991ee7ed06357b17ce15204fae24bf4e08b5bd3a89a7e9533939c07ce82284 (8)
M theories/ordinals/Hydra/Epsilon0_Needed_Free.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-81df98a10d0f01edbbba99dd48bd01112e69d09806c7f95577707118b414de9b (2)
M theories/ordinals/Hydra/Epsilon0_Needed_Generic.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-08e9ceae459dfdc3fd911877774e8594c2439a711e2da472ead8f3d46c885d0e (2)
M theories/ordinals/Hydra/Hydra_Termination.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-4e6c87b8a125f79b1d6b2162df367e808dded503f4edacfc11e1c0fed539cc70 (2)
M theories/ordinals/Hydra/Omega2_Small.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-e2856306d4d8c6c9896c772c233a808a038a952d7337863b780227dff0c28b0b (10)
M theories/ordinals/Hydra/Omega_Small.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-a87f4ba93a5a043a96f9d916ef680a40fc26d5657c7794359e28a16ee22523cd (2)
M theories/ordinals/OrdinalNotations/ON_Generic.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-b6fdbdc73a9fb963e353dd8f13beacfeba9b0cd5c1de810d365fc2b99e3c17cc (2)
M theories/ordinals/OrdinalNotations/ON_Omega2.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-87a5b1dd4c8061d2daa8ee765a522e6dcf566e7ea3e63323e8008581e724b0ba (4)
M theories/ordinals/OrdinalNotations/ON_mult.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-f27db2e205878a8a4a6c3bee4c7b6c06acb2ae4a90917774010b1da187cbb7eb (4)
M theories/ordinals/OrdinalNotations/ON_plus.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-2812a6353f847c1cd11ed782dd67195d93b5fdf2c8ea44b4fc0d6b5c8de61034 (4)
M theories/ordinals/Prelude/MoreLists.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-0659422298e21526e03c893fd0475c72a53034bd1064a00bd99b1a1d46b30986 (2)
M theories/ordinals/Prelude/Sort_spec.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-6cfcfcbcb03df382d7326c3ff99d5966189a657de4308527ae6364501bf1368f (2)
M theories/ordinals/Schutte/AP.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-eebbd06164415dc9298ee3f2e18b30f81a0c2ba24a63c4a6cff0a817f5adedad (4)
M theories/ordinals/Schutte/CNF.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-59d5cf7fdf342381341c40b8fa7a462bd4635d5657a3da976d603b2a555744c2 (4)
M theories/ordinals/Schutte/Ordering_Functions.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-02b4875c36dfa3aa6be37f6dcdbdc075e6fb0b068ff96960da910c7990c99b29 (18)
M theories/ordinals/Schutte/Schutte_basics.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-67d263a508dca5da9bc29ad35f77e3c027c8350535f0356346b9e5befb5263d5 (28)
M theories/ordinals/Schutte/Well_Orders.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-748bd8981ca713c72e71886adc819d0732c81574d4ff3173f4c0d4d3455f2ca4 (2)
M theories/ordinals/primrec/primRec.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-82767788342d2644cb888af55ebd24b85be211ac765428c3e795b5af2f370eca (2)
M theories/ordinals/rpo/list_permut.v https://github.com/coq-community/hydra-battles/pull/18/files#diff-f1ca29f4b0d94949add0649072a9a86628815dd99ca47ee51c44c98c1c582c5d (4)
Patch Links:
https://github.com/coq-community/hydra-battles/pull/18.patch https://github.com/coq-community/hydra-battles/pull/18.patch
https://github.com/coq-community/hydra-battles/pull/18.diff https://github.com/coq-community/hydra-battles/pull/18.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/coq-community/hydra-battles/pull/18, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJW6FCSUQZTW6JGKNFORH7TSYMDNTANCNFSM4VVCD3MA.

@Casteran indeed this seems like a very nitpicky warning, and it was only introduced in 8.13. Perhaps we should simply suppress/ignore it? This is quite simple to do by editing _CoqProject/dune. Personally, I also prefer using x or similar rather than _ in these situations.
Perhaps @Zimmi48 knows why this warning was introduced.

@Casteran indeed this seems like a very nitpicky warning, and it was only introduced in 8.13. Perhaps we should simply suppress/ignore it? This is quite simple to do by editing _CoqProject/dune. Personally, I also prefer using x or similar rather than _ in these situations.
Perhaps @Zimmi48 knows why this warning was introduced.

See https://github.com/coq/coq/issues/12762 for the rationale. Feel free to ignore this warning if you do not find it useful. Maybe the warning message should explain why it is considered a bad practice though.

See https://github.com/coq/coq/issues/12762 for the rationale. Feel free to ignore this warning if you do not find it useful. Maybe the warning message should explain why it is considered a bad practice though.

@Casteran what do you think of the rationale in coq/coq#12762? I'm fine with either suppressing the warning or changing the code to use underscores.

@Casteran what do you think of the rationale in coq/coq#12762? I'm fine with either suppressing the warning or changing the code to use underscores.

I understand the rationale.  Tomorrow, I can replace in master the catch-all variables with underscores.

Le 5 janv. 2021 à 17:13, Karl Palmskog<EMAIL_ADDRESS>a écrit :
@Casteran https://github.com/Casteran what do you think of the rationale in coq/coq#12762 https://github.com/coq/coq/issues/12762? I'm fine with either suppressing the warning or changing the code to use underscores.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/coq-community/hydra-battles/pull/18#issuecomment-754735635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJW6FCTW3F2WUFZIGLBBYJLSYM3ELANCNFSM4VVCD3MA.

I understand the rationale.  Tomorrow, I can replace in master the catch-all variables with underscores.

Le 5 janv. 2021 à 17:13, Karl Palmskog<EMAIL_ADDRESS>a écrit :
@Casteran https://github.com/Casteran what do you think of the rationale in coq/coq#12762 https://github.com/coq/coq/issues/12762? I'm fine with either suppressing the warning or changing the code to use underscores.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/coq-community/hydra-battles/pull/18#issuecomment-754735635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJW6FCTW3F2WUFZIGLBBYJLSYM3ELANCNFSM4VVCD3MA.

OK, since the variable name change is orthogonal to this PR, I will then take the liberty to merge. The only remaining warnings were those related to the Coq issue.

OK, since the variable name change is orthogonal to this PR, I will then take the liberty to merge. The only remaining warnings were those related to the Coq issue.


Add reproducer integration test for #23576

https://github.com/gradle/gradle/issues/23576

@bot-gradle test AFT

I've triggered the following builds for you:

AllFunctionalTestsPullRequestFeedback build

@bot-gradle test AFT

I've triggered the following builds for you:

AllFunctionalTestsPullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Remove usages of outdated uuid libraries.

What this PR does / why we need it: This PR fixes potential errors that may arise due to conflicts during dependency resolution.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: tariq1890 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


add support from clip board

@im6h can you add a new commit that increases the extension version? I forgot abt that

reases the extension version? I forgot

sorry guys, this feature still doesn't work on macos. Maybe you need to revert the commit?

Sure, lets revert it. I cant test it either because im not using mac


[AIRFLOW-2718] Backfill reset_dagrun option allows user to specify ce…

…rtain tasks
Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2718
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
When user provides -t "task_regex" and --reset_dagrun options for backfill, backfill should be able to clear the task_regex instead of all the tasks.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
trivial change.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

PTAL @kaxil @Fokko

jenkins pass at my repo: https://travis-ci.com/feng-tao/incubator-airflow/builds/78245048

hey @Fokko , sorry, just updated the commit message.

PTAL @Fokko

Nice one @feng-tao
I've merged the commit to master!


Support Azure Workload Identity in RabbitMQ scaler

Proposal
RabbitMQ introduced generic OIDC support in version 3.11. I would like to use it in combination with Azure workload identity
Use-Case
AKS cluster with enabled Workload identity can be used to authenticate against RabbitMQ.
This can (partialy) solve https://github.com/kedacore/keda/issues/2513 for users within AKS.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response

Implemented in https://github.com/kedacore/keda/pull/4657. This implementation can be extended to another IdP, but I'm not able to test it - see https://github.com/kedacore/keda/issues/4694