Decoder init failed error on some AndroidTV devices

Version
ExoPlayer 2.18.5
More version details
I'm following this doc(https://developer.android.com/guide/topics/media/exoplayer/ad-insertion#client-using-third-party)
implementing a custom AdsLoader that wraps our ads SDK.
Previously, we implemented seamless content and ad switching using two ExoPlayer instances.
Now, we have achieved the same seamless switching using a custom AdsLoader with a single-player instance.
We tested this solution on the production environment and put it under an experiment. We noticed that this approach resulted in a significant increase in "Decoder init failed" errors on Android TV, roughly seven times more than before.
Error cause
Decoder init failed: OMX.amlogic.hevc.decoder.awesome2.secure, Format(1, null, null, video/hevc, hvc1.1.6.L90.90, 1205048, null, [854, 480, 23.974], [-1, -1])
Error message
com.google.android.exoplayer2.ExoPlaybackException: MediaCodecVideoRenderer error, index=0, format=Format(1, null, null, video/hevc, hvc1.1.6.L90.90, 1205048, null, [854, 480, 23.974], [-1, -1]), format_supported=YES
Below is the code I used to build the DrmConfiguration
val drmConfiguration = MediaItem.DrmConfiguration.Builder(C.WIDEVINE_UUID)
                        .setLicenseUri(videoResource.getLaUrl())
                        .setLicenseRequestHeaders(
                            mapOf(videoResource.getAuthHeaderKey() to videoResource.getAuthHeaderValue())
                        )
                        .setMultiSession(true)
                        .setPlayClearContentWithoutKey(true)
                        .build()

The error led to interruptions in playback for many users. It happened when switching from Widevine-encrypted video content to clear ads.
However, this error doesn't increase on Android phones.
The differing behavior between Android phones and TVs suggests a potential hardware-related issue.
I've observed a previous issue that might be related to the problem I'm experiencing now. The previous solution involved sleeping for 50ms when creating a decoder fails and then attempting to create it again.
I have a few ideas for addressing this issue, and I'd like to hear your thoughts:

Increase the sleep duration and make it a user-configurable parameter.
After a decoder initialization failure, attempt initialization multiple times, with the number of retries being a user-configurable parameter.

If these approaches are viable, I can submit a pull request (PR) to implement these changes.
Also, would you happen to have a better solution in mind?
Devices that reproduce the issue
Not a device specific issue:
SmartTV 4K, Hisense
Philips 4K A1
Smart TV, TCL
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
This issue is not 100% reproducible, but It should be reproduceable with the demo app.
I will try to reproduce it in the demo app.
Expected result
No PlaybackException with decoder init failed when switching from WideoVide video content to clear ad.
Actual result
Some times  there is an PlaybackException with decoder init failed when switching from WideoVide video content to clear ad.
Media
Any WideVine media stream
 {
        "name": "HD (cenc)",
        "uri": "https://storage.googleapis.com/wvmedia/cenc/h264/tears/tears.mpd",
        "drm_scheme": "widevine",
        "drm_license_uri": "https://proxy.uat.widevine.com/proxy?video_id=2015_tears&provider=widevine_test"
      }

Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Assigning to @icbaker to get his expertise regarding protected/clear content playback. Looks to me that the API use above is correct, but ibaker has more experience to tell.

I have a few ideas for addressing this issue, and I'd like to hear your thoughts:

Increase the sleep duration and make it a user-configurable parameter.
After a decoder initialization failure, attempt initialization multiple times, with the number of retries being a user-configurable parameter.

Have you tried to make these changes locally to confirm that they resolve the issue in your repro case?

It happened when switching from Widevine-encrypted video content to clear ads.

Have you tried using a secure decoder for the clear ads as well (to try and avoid switching decoders): https://developer.android.com/reference/androidx/media3/common/MediaItem.DrmConfiguration.Builder#setForceSessionsForAudioAndVideoTracks(boolean)

We don't have access to the devices you've reported reproduce the issue. Please can you take an adb bugreport after reproducing the issue in the demo app and send it to<EMAIL_ADDRESS>with subject Issue #936? Please update this issue to let us know you've done this.

Have you tried using a secure decoder for the clear ads as well (to try and avoid switching decoders):

I tried setForceSessionsForAudioAndVideoTracks locally, but that doesn't guarantee no switching decoders, I still see many times decoder switching from AnalyticsListener.onVideoInputFormatChanged() the decoderReuseEvaluation discardReasons are DISCARD_REASON_MAX_INPUT_SIZE_EXCEEDED, DISCARD_REASON_VIDEO_COLOR_INFO_CHANGED.

Have you tried to make these changes locally to confirm that they resolve the issue in your repro case?

Not yet, I'm trying to repro this issue locally, will try to make these changes, and send the adb bugreport once I find stable repro steps.

Hi @Hiwensen @marcbaechinger  any update for this bug to solved. actually I'm also face same issue on Android TV Hisense , can't play video with drm - widevine. let me know if any update here

Hi @Hiwensen @marcbaechinger any update for this bug to solved. actually I'm also face same issue on Android TV Hisense , can't play video with drm - widevine. let me know if any update here

Sorry for the late reply, we developed a solution by creating a custom MediaCodecFactory and RenderersFactory to override MediaCodec.createAdapter() and extend the sleep duration when a MediaCodec instance fails during the creation process. This approach significantly reduced the number of decoder init failed errors.
As described in this blog.
Do you still have this problem now, can't play any widevine DRM content on your TV？


Fixed DBLIB subdriver to get the right version number of SQL Server.

I was testing a feature and needing it using LIMIT / OFFSET and I had to make this fix, if you could include it in the core project, maybe it would help others.

A fix for ... what?
Also, even if you consider this to be a fix for anything, you can't call the function itself a "fix" in its docblock.

Hello Andrey,
I'm sorry for the branch "naming". I would like to help CI because I use
the framework on some occasions and just wanted to share the pain that I
felt.
Fix for get the right version number from Microsoft SQL Server Production
Version. Some functions like 'LIMIT' look for SQL Server VERSION and use
different ways to apply SQL Limit.
[image: Imagem inline 1]
Thank you.
2017-08-31 6:36 GMT-03:00 Andrey Andreev<EMAIL_ADDRESS>
A fix for ... what?
Also, even if you consider this to be a fix for anything, you can't call
the function itself a "fix" in its docblock.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcit-ci/CodeIgniter/pull/5243#issuecomment-326243646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAsA3x0LbnsjXLtWPzn2XjYQMsSteeBaks5sdn6agaJpZM4PH83A
.

--
Andrei Rosseti

Ah... Before the fix, $this->version() returns 'NULL', after returns the
wanted VERSION. Thanks!
2017-08-31 8:13 GMT-03:00 Andrei Rosseti<EMAIL_ADDRESS>
Hello Andrey,
I'm sorry for the branch "naming". I would like to help CI because I use
the framework on some occasions and just wanted to share the pain that I
felt.
Fix for get the right version number from Microsoft SQL Server Production
Version. Some functions like 'LIMIT' look for SQL Server VERSION and use
different ways to apply SQL Limit.
[image: Imagem inline 1]
Thank you.
2017-08-31 6:36 GMT-03:00 Andrey Andreev<EMAIL_ADDRESS>
A fix for ... what?
Also, even if you consider this to be a fix for anything, you can't call
the function itself a "fix" in its docblock.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcit-ci/CodeIgniter/pull/5243#issuecomment-326243646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAsA3x0LbnsjXLtWPzn2XjYQMsSteeBaks5sdn6agaJpZM4PH83A
.

--
Andrei Rosseti

--
Andrei Rosseti

Ok ... I've left some inline comments on things that need adjustments.

Thank you for the guides @narfbg

You're welcome; that's what I'm here for. Thank you for your contribution!


Toggle not displayed

I am using L.Minimap with the latest 1.2 stable Leaflet release. I have set toggleDisplay: true. However the toggle is not shown on the minimap. I checked with Google Developer tools and I can see that toggle.svg is being accessed by the browser with no errors (and why toggle.svg and toggle.png?). I am also using my own "custom" tile provider. The tiles are displayed correcly on on the minimap though.
Here is my code:
        var minimapLayer = new L.TileLayer('mytiles/{z}/{x}/{y}.png');
        var miniMap = new L.Control.MiniMap(minimapLayer, { toggleDisplay: true }).addTo(map);

Sorry for completely forgetting about this issue! Can you create a jsFiddle to deomonstrate it? What browser? (toggle as svg and png is a workaround for IE, not sure if it's needed anymore.)

Hi, i have the same issue as aludin, the toggle is here ( a litle white square) but not the arrow (picture).
It's work on :  Firefox : 58.0.2
But not with : Google Chrome Version 64.0.3282.186
I am currently using leaflet 1.2.0
Thanks in advance

Sorry for being late again! I'm not seeing this problem in the minimap examples using Chrome 65. Do you have a jsFiddle that demonstrates it?

This problem exists. The toggle buttons is not shown.The example one loads but when used in a project it doesn't.

toggleDisplay is set to true.

Im sorry the node module does not link the css directly .
If anyone is loading this through node modules do
require('../../node_modules/leaflet-minimap/dist/Control.MiniMap.min.css');
This should work.

Hello :slight_smile:
So I’m pretty pleased with the progress of my personal portfolio site, even if it is taking me forever to do. Of course, I want the fixed navbar to collapse and be toggle-able on smaller screens. At the moment, my navbar is collapsing and the toggle button is appearing. However, nothing happens when I click the hamburger button. I’m sure that my menu items are supposed to appear. I can’t find what’s wrong. I did link the bootstrap css and js files as well as jQuery in the relevant sections of my codepen.
Could somebody please look at this navbar markup and tell me what is wrong? Do I have to somehow activate this with some jQuery/ JavaScript that I write myself or what? From all the tutorials I’ve read or watched it seems like it should work from this markup alone…

Toggle navigation

About

Portfolio

Contact


Running shell apps from textual

Any hints on execute shell app, like vim, from key event method?
Now using os.system or subprocess or asyncio.create_subprocess_shell, when I close vim, textual app stops, I even cannot close it with Ctrl-c

would you mind posting this in the discussions tab?  you will get more/faster responses there

ok, thank you for advice, will close it.


Error while placing order in Testnet

Press Ctrl-Q to stop the script
Kraken Daily Market Report for April 25 2021
OKEx Insights + Catallact : Bitcoin Market Witness the Growth of Retail Participation as Institutional Investors Continue to Lead
Bitcoin Banned in Turkey | This Week in Crypto – Apr 26, 2021
Mercurial on crypto: Will India’s latest stance lead to positive regulation?
OneLedger Announces “Gem Hunt” Mining and Validator Competition
AMA with Harsh Rajat and Richa Joshi (EPNS): Summary
Blockchain Object Storage Company Filebase Raises $2M, Aims to Incorporate Filecoin and Arweave Networks
Why Are Athletes Demanding To Be Paid In Bitcoin?
Could not parse http://Bitcoinist.com/feed error is: unbound prefix: line 57, column 2
Unmarshal's MARSH token lists on AscendEX
A Glimpse Into The Future Of Bitcoin At $200,000
Giant American Wine Seller Now Accepts Bitcoin, Dogecoin, and Ethereum
Verifying your 2FA disable requests and other security tips from CEX.IO
Embrace the Explosion of Colors in the Festive Hot Fiesta Slot
Could not parse https://www.mycryptopedia.com/feed/ error is: mismatched tag: line 135, column 2
Ampleforth.org Airdrop Review: The FORTH token has arrived
Stellar Lumen (XLM) Price Primed For A Fresh Rally Above $0.45
XRP Price Analysis: XRP Continues To Fall As Price is Stuck In Descending Channel
Turkey’s Central Bank: Crypto Regulation Will Come In Two Weeks
Dogecoin [DOGE] Struggles Near Support Despite An Uptick of 5%
Solana Hits All-Time High Amid Market Calm
Bit-flash.biz Review: PAYING or SCAM?
Could not parse https://botsfolio.com/crypto_news/feed error is: 'NoneType' object has no attribute 'text'
Nem szeretnek adót fizetni a multik – több milliárd dollár kötött ki adóparadicsomokban
Satoshi Nakamoto Identity Case Takes a New Turn
Could not parse http://bitcoinmxn.com/feed error is: 'NoneType' object has no attribute 'text'
Crypto News Cast For April 25th 2021 ?
XRP Ripple Returns – Long ETH and XRP
OKEx Insights + Catallact : Bitcoin Market Witness the Growth of Retail Participation as Institutional Investors Continue to Lead
Bitmain Teasing With the Upcoming AntMiner E9 Ethereum Miner
Top 5 Peterborough United F.C. Forums, Discussions and Message Boards You Must Follow in 2021
Neo Price Analysis: NEO Breaks Downtrend as Bulls Target $100
Could not parse https://coinpress.io/feed/ error is: 'charmap' codec can't decode byte 0x9d in position 22517: character maps to <undefined>
More Projects joining Polygon (MATIC) amidst rising Layer-2 adoption
Apple, MicroStrategy and Microsoft Stock Tokens Are Coming To Binance
Could not parse http://www.investorideas.com/rss/feeds/iimain.xml error is: time data 'Fri, 23 Apr 2021 14:10:00 EST' does not match format '%a, %d %b %Y %H:%M:%S %z'
How to Buy Real Estate with Cryptocurrency?
Traceback (most recent call last):
  File "D:/FinanceRepos/Binance-News-Sentiment-Bot/news-analysis.py", line 473, in <module>
    buy(compiled_sentiment, headlines_analysed)
  File "D:/FinanceRepos/Binance-News-Sentiment-Bot/news-analysis.py", line 368, in buy
    test_order = client.create_test_order(symbol=coin + PAIRING, side='BUY', type='MARKET',
  File "D:\Anaconda3\envs\pyt12\lib\site-packages\binance\client.py", line 1633, in create_test_order
Time it took to parse feeds:  24.928550800000004

BUY CHECKS:
Sentiment not positive enough for XRP, or not enough headlines analysed or already bought: -0.125, 2
preparing to buy 0.001876 BTC with USDT at 53294.93000000
    return self._post('order/test', True, data=params)
  File "D:\Anaconda3\envs\pyt12\lib\site-packages\binance\client.py", line 295, in _post
    return self._request_api('post', path, signed, version, **kwargs)
  File "D:\Anaconda3\envs\pyt12\lib\site-packages\binance\client.py", line 242, in _request_api
    return self._request(method, uri, signed, **kwargs)
  File "D:\Anaconda3\envs\pyt12\lib\site-packages\binance\client.py", line 220, in _request
    kwargs['data']['signature'] = self._generate_signature(kwargs['data'])
  File "D:\Anaconda3\envs\pyt12\lib\site-packages\binance\client.py", line 175, in _generate_signature
    m = hmac.new(self.API_SECRET.encode('utf-8'), query_string.encode('utf-8'), hashlib.sha256)
AttributeError: 'NoneType' object has no attribute 'encode'

Got this error, i have the API keys as mentioned in the blog, can you tell me what might be the issue here?

I have exactly the same error when API keys aren't provided to the program correctly.
How do you provide the keys? (but obviously don't share them if you want show example)
Also do you use correct ones? API keys for testnet and live are seperate, you can get them in 2 different places

I only have the test keys not live keys. Let me see if environment variables are the issue here

Ok so if i put the keys directly not using the os.getenv it seems to work, maybe some issue from environment setup from my side.

If that would help anyone using Windows, this is a bat file I am using:
`SET "binance_api_stalkbot_testnet=key"
SET "binance_secret_stalkbot_testnet=key"
SET "binance_api_stalkbot_live=key"
SET "binance_secret_stalkbot_live=key"
python news-analysis.py`
Just replace "key" word with your API keys and save it in bot's folder


Fix ack receipt version support logic

Motivation
if (conf.isAckReceiptEnabled() &&
                    Commands.peerSupportsAckReceipt(clientCnx.getRemoteEndpointProtocolVersion())) {
                log.warn("Server don't support ack for receipt! " +
                        "ProtoVersion >=17 support! nowVersion : {}", clientCnx.getRemoteEndpointProtocolVersion());
            }

the ack receipt version support logic Commands.peerSupportsAckReceipt(clientCnx.getRemoteEndpointProtocolVersion()) should add not.
Modifications
add not !Commands.peerSupportsAckReceipt(clientCnx.getRemoteEndpointProtocolVersion()

We don't have ack receipt in branch-2.7, so don't need to cherry-pick this fix to branch-2.7


Sync with upstream repo

Please be sure to check out our contributing guidelines
before submitting your pull request.
Fixes #
Proposed Changes

Sync with upstream repo


Extract search_list_with_dicts

Pull Request Test Coverage Report for Build 196

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 169:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Pull Request Test Coverage Report for Build 171

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 169:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Problem with video-streaming

When I run the command provided ''python -m demo.app --resume_from_checkpoint chenjoya/videollm-online-8b-v1plus''. In the demo, I pick camera mode, but the model seems not capture the video streaming.

When I ask it what am doing now, it will ask it is ai and can not know what am doing now.


can't use in .net4.8

when use in .net 4.8 will report error:
Fody: Unable to find type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute' in assembly 'System.Runtime'

OS: windows 11 [e.g. Windows 10, macOS 12.0.1, Ubuntu 20.04]
Platform: .net framework 4.8 [e.g. .NET Framework 4.8, .NET Core 3.1, .NET 5]
PrismCommands.Fody Version:2.0.6 [e.g. 1.0.0]

[ ] I have searched the existing issues to ensure that this issue has not already been reported.
[ ] I have provided a clear and concise description of the issue, including any error messages, screenshots, or logs that may be relevant.
[ ] I have provided steps to reproduce the issue.
[ ] I have provided information about my environment that may be relevant to the issue.
[ ] I have provided any additional information that may be helpful in resolving the bug.
[ ] I have reviewed my issue for accuracy and completeness.

@asine I think I fixed it in the last commit. Please check

BlankApp2.zip

@vitkuz573 thanks,2.0.7 is ok.

The release is out!


Use pam_faillock

Current situation
The previously used pam_tally2 module got deprecated and was removed in https://github.com/kinvolk/baselayout/pull/12 but we didn't migrate to pam_faillock yet.
Impact
The use case of pam_tally2/pam_faillock might not be covered now in the next Alpha release, since in our baselayout/pam.d/system-auth file we don't have a setting for pam_faillock.
Ideal future situation
pam_faillock works
Implementation options
Update the https://github.com/kinvolk/baselayout/blob/flatcar-master/pam.d/system-auth file to be adapted from https://github.com/gentoo/pambase/blob/3f36e2c3de28b3cde25a27d05e49d354e098c368/templates/system-auth.tpl without being a template and by leaving out things that don't apply
Additional information

PR in https://github.com/kinvolk/baselayout/pull/17

and in https://github.com/kinvolk/coreos-overlay/pull/911

Will be part of the next major Alpha


BoneAttachment node does not work in one of the Skeleton bones

Symptom: one of the BoneAttachment nodes, with red material, does not work. MeshInstance don’t follow bone movement with SkeletonIK node. It was working in Godot 3.2.1.
Operating system: Windows 10
Godot version: 3.2.2 stable official
Steps to reproduce: run the provided minimal project in Godot 3.2.2. BoneAttachment node, in red material, does not follow bone rotation.

minimal project.zip

CC @AndreaCatania @TwistedTwigleg

I can confirm this is still an issue with Godot 3.2.3 Beta 1 on Linux. From what I can tell when running this project, the first bone in the SkeletonIK chain does not appear to be taken into account when solving.


Added Natasha's First Post

This should be in the _posts directory.  My mistake during the walkthru (but the class notes have it right).  We'll fix on Monday


Xblanchot/sca 1066/clean sca models

Codecov Report

Merging #766 (bb82afa) into main (df9bf2e) will increase coverage by 0.03%.
Report is 2 commits behind head on main.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #766      +/-   ##
==========================================
+ Coverage   92.42%   92.45%   +0.03%
==========================================
  Files         155      153       -2
  Lines        6351     6259      -92
==========================================
- Hits         5870     5787      -83
+ Misses        481      472       -9

Flag
Coverage Δ

unittests
92.45% <100.00%> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

ggshield/cmd/sca/scan/prereceive.py
83.72% <100.00%> (ø)

ggshield/cmd/sca/scan/sca_scan_utils.py
77.77% <100.00%> (-0.25%)
:arrow_down:

ggshield/verticals/sca/collection/collection.py
96.55% <100.00%> (ø)

ggshield/verticals/sca/file_selection.py
91.42% <100.00%> (ø)

ggshield/verticals/sca/output/schemas.py
100.00% <100.00%> (ø)

ggshield/verticals/sca/output/text_handler.py
96.20% <100.00%> (ø)

@agateau-gg I modified the doc for make-pipfile-lock in the first commit, can you just check that I did not propose any mistake ?


Limit forward construction interface in template classes

Brief feature description
Variadic forward construction in methods such as emplace are not possible to certify due to their unbounded permutations. To handle this, forward construction should be restricted to:

const lvalue references
rvalue references

Detailed information
The following classes need to be modified:

[ ] optional.hpp

Not needed.
Variadic functions such as emplace are in fact bound by the function signature of the constructors they call. Therefore, limiting the APIs of these functions is not required.
Additionally, the idea to limit to the signature to const lvalue references and rvalue references means that these functions will not work with non-movable non-copyable types which is not acceptable.


typo there

Saw a typo there, "remote blog storage" should be "remote blob storage"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 58b18e9a-c7a8-e1a0-889b-80c7d35db286
Version Independent ID: 73b90d6d-7af2-0899-960a-801c19397720
Content: Best practices for upgrading from SharePoint 2010 to SharePoint 2013
Content Source: SharePoint/SharePointServer/upgrade-and-update/best-practices-for-upgrading-from-sharepoint-2010-to-sharepoint-2013.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: kirks

@officedocsbot assign @scanum


Update base.py

MutableMapping should be imported from collections.abc as said in documentation https://docs.python.org/3.9/library/collections.abc.html#collections.abc.MutableMapping
Mainly we need it because its fix #65 (python3.10 compatibility)

Thanks @bobuk  !
But since I haven't had time to really working on dropping Python 2.7, can we have something like
if sys.version_info[0] == 3:
    from collections.abc import MutableMapping
else:
    from collections import MutableMapping

Just for the time being ?

NVM, I'll just merge this as is for now, thanks :)


PLANNER-618 Workbench: Use org.jboss.errai.ioc.client.api.ManagedInstance instead of BeanManager where possible

@mcimbora a concern above about the PlannerDomainHandler being application scoped and never destroying domain editors. If that's desired, +1.

ok, +1 (merging once build green)

jenkins retest this.

@csadilek This requires https://github.com/droolsjbpm/drools-wb/pull/243  to be integrated.


Exceeding the octokit quota results in a broken page

Describe the bug
Exceeding the octokit quota will result in pages containing gists getting stuck while loading. The worst part is that the quota is really low, so it takes almost no effort to exceed it.
To Reproduce
Repro is here.

Remove mdx() integration so the project could start;
Start dev mode from the terminal;
Open the preview in a different tab (it tends to show "Too much redirect" error);
Refresh the page about 10 times;
Notice Request quota exhausted for request GET /gists/{gist_id} log in the terminal. The page also won't load.

I've also tried checking the preview mode, but I can't build the project:
07:05:03 [build] Building static entrypoints...
07:05:08 [ERROR] [vite] x Build failed in 5.26s
[vite]: Rollup failed to resolve import "fsevents" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
  Stack trace:
    at viteWarn (file:///workspaces/workspace/node_modules/.pnpm/vite@5.1.4/node_modules/vite/dist/node/chunks/dep-jDlpJiMN.js:67078:27)
    at onwarn (file:///workspaces/workspace/node_modules/.pnpm/vite@5.1.4/node_modules/vite/dist/node/chunks/dep-jDlpJiMN.js:66810:13)
    at Object.logger [as onLog] (file:///workspaces/workspace/node_modules/.pnpm/rollup@4.12.0/node_modules/rollup/dist/es/shared/node-entry.js:19965:9)
    at ModuleLoader.resolveDynamicImport (file:///workspaces/workspace/node_modules/.pnpm/rollup@4.12.0/node_modules/rollup/dist/es/shared/node-entry.js:18967:58)

The project itself is the Astro codesandbox official template fork with two integrations installed with astro add.
Expected behavior
I suppose this behavior is expected, but it also makes the package almost impossible to use. You'll never know when the quota will be exceeded, and when it is, pages containing gists will simply break.
Edit: I also noticed that in repro everything works without GitHub personal token.

I was unable to click into your reproduction... But I only encountered this error when i did not have a token assigned.  Octokit does allow you to use it without a token but it is HEAVILY limited.  The only solution for me to solve it was by adding the setup for the access token.  I have a empty token that i was using for DEV that i was able to refresh 100s of times without facing any errors... so this is really weird and i'd love a chance to investigate!

I'm pretty sure I tried both with and without the secret. I'll give it another try tomorrow and get back with results.

Just in case its something to do with the code sandbox, I've also implemented some better logs to verify that it can see your .env defined token.  As well as just trying to keep my own sanity and verify things are working the way they should 😄

Also just to clarify according to GitHub:
Primary rate limit for unauthenticated users
You can make unauthenticated requests if you are only fetching public data. Unauthenticated requests are associated with the originating IP address, not with the user or application that made the request.
The primary rate limit for unauthenticated requests is 60 requests per hour.
Primary rate limit for authenticated users
You can use a personal access token to make API requests. Additionally, you can authorize a GitHub App or OAuth app, which can then make API requests on your behalf.
All of these requests count towards your personal rate limit of 5,000 requests per hour. Requests made on your behalf by a GitHub App that is owned by a GitHub Enterprise Cloud organization have a higher rate limit of 15,000 requests per hour. Similarly, requests made on your behalf by a OAuth app that is owned or approved by a GitHub Enterprise Cloud organization have a higher rate limit of 15,000 requests per hour if you are a member of the GitHub Enterprise Cloud organization.
So if the Token is properly present, there should be no reason that Octokit should throttle... since it just uses the RestAPI

Seems like you're right. But if there's a quota, then there's a possibility of it being exceeded. I think some explicit logs and rendering the link to the gist when this happens will be a good solution here.

#18 will include those logs.
But again... If your using a token (Like explicitly mentioned in the Readme and if you don't have it the console will yell now as well) you should not be facing any issues with request limits in the first place as the request limit is quite high.  and there are available options from github to raise said limit as well.

You're right, but any external quota, no matter how high, is the potential breaking point. Let's say you have 15000 requests per hour. Suppose you have a blog with 10 articles, each with 10 gists. You have 15000 / (10 * 10) = 150 page views per hour until the quota is exceeded. It's a rough approximation, but the seemingly high limit can shrink very quickly, and there's no way to raise it any higher (if there is, fine, but you should be somehow aware that you are almost there). Also, you can never rule out a DDoS, which will drain 15000 requests in a couple of minutes, and the remaining time of an hour everything sill be broken.
That's why I suggested having a fallback with a link to the gist, because that way the component will fail gracefully and the user will still get the information they want, just in a different view.

Just saw your code sandbox, and noticed the .env file is supposed to be at the root of the project, not within the /src directory.  That would be why your hitting the rate limit so quickly. It is not seeing your token at all.
Page views per hour would only be applicable with Astro in SSR mode, in SSG mode the HTML is directly rendered and NOT using API requests every single poll of the webpage.  So if you are building a SSG(Static, the default for Astro) website the only time Octokit would be called is during build time.  Now for SSR I could see this as a problem.  And there are plans on my notepad to include such fixes for that type of situation.  BUT in general most Astro users will not face this issue as most Astro projects are statically built.

Sandbox didn't allow me to save .env at all so I checked it locally. It worked as expected, no issue here.
Point about SSG is valid. Some info about potential problems in SSR mode in the package README.md would be useful though.

This issue is now complete, as of #24


add settings for custom system prompt

Add a section in addon settings to customize system or assistant prompt

Hurry up, I can't wait to use this feature!


⚠ Spryr has degraded performance

In 0a21d8b, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3580 ms

Resolved: Spryr performance has improved in ae6a615 after 7 minutes.


chore: remove styfle/cancel-workflow-action usage

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency

https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency

The fully-formed ref of the branch or tag that triggered the workflow run. For workflows triggered by push, this is the branch or tag ref that was pushed. For workflows triggered by pull_request, this is the pull request merge branch. For workflows triggered by release, this is the release tag created. For other triggers, this is the branch or tag ref that triggered the workflow run. This is only set if a branch or tag is available for the event type. The ref given is fully-formed, meaning that for branches the format is refs/heads/<branch_name>, for pull requests it is refs/pull/<pr_number>/merge, and for tags it is refs/tags/<tag_name>. For example, refs/heads/feature-branch-1.

https://docs.github.com/en/actions/learn-github-actions/contexts#github-context

@mcansh Only new commits on the same branch should cancel previous runs of a specific workflow (just like it did with styfle/cancel-workflow-action)


Fix typo

Fixes #836

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/data-guide/technology-choices/search-options.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Ligatures=NoTeX

This is easy in LuaTeX but not sure about XeTeX at present.

This will be happening in the next release.

Was this actually implemented in a newer version? I’m using version 2.6, but it doesn’t work with this version. As an alternative I’m currently using RawFeature=-tlig.
I also have to related issues (please let me know if I should open a separate issue):

Using Ligatures=TeXReset and Ligatures=ResetAll gives me an Argument of \__fontspec_swap_plus_minus_aux:Nq has an extra }. error. (I understood (from #82) that Reset was modified around the same time the issue should have been addressed.)
The documentation is confusing to me. The features environment states that “options can be disabled with ..Off variants.” However, (at least for Ligatures) the options should be disabled with No.. variants, right?

Ah, sorry, I see in your revision history that you’ve probably already fixed the issue with Reset in v2.6a.


Calling Workflows from Services

https://github.com/ManageIQ/manageiq/issues/22311
We need to be able to run either an Automate Class or a Workflow for the various entrypoints of a service, namely:

Dynamic Dialogs
Provision/Reconfigure/Retire

Dynamic Dialogs are run via the DynamicDialogFieldValueProcessor.values_from_automate method which runs deliver_to_automate_from_dialog_field on the ResourceAction.  The ResourceAction has the ae_namespace/ae_class/ae_instance/ae_message/ae_attributes properties.  We could add a Workflow reference to ResourceAction and run one-or-the-other based on type/presence.
The Provisioning entrypoint is called by ServiceOrder#process_checkout -> ServiceTemplateProvisionRequest#call_automate_event_queue("request_created").  There is a ResourceAction created for the ServiceTemplate action: Provision but it doesn't appear to be used directly unless I'm missing it.  There is a :workflow_settings=>{:resource_action_id=>2, :dialog_id=>1}, in the options on the MiqRequest.  We could change this to call some other method and then decide if we call a workflow or automate based on the request definition.
Reconfigure: TBD
The Retire entrypoint is via the ServiceRetireRequest#post_create method

Not directly related to Improving the Service experience, but custom buttons also use ResourceAction in a similar way to DialogField and could probably be updated to work with workflows in a similar way.

I forgot about custom buttons.  There's also event handling actions.

This is the basic idea for entrypoints as per our discussion @Fryguy . please advise if anything seems missing
We can change the naming convention if needed ..

Moving conversation re: entry points in the UI to #8715


Collect retry statistics from the S3 filesystem

This PR makes two changes:

Collect the number of retries made at the s3 file system level for the read(), getMetadata(), and getObject() calls.
Fix a bug which causes one less retry than the set hive.s3.max-client-retries parameter. The reason is this parameter was used by the s3 filesystem to set the number of attempts instead of the number of retries (in other words the very first attempt was considered a retry).

Merged, thanks!


What is "d" param in popup url?

I am trying to open my own popup without using the client side oauth.min.js file
I have oauthd daemon running at (i.e) http://myserver.com
so i do something like:
window.open('http://myserver.com/auth/facebook?k=71Pwcj45vuO9DQ450a2BovAIRXpM&d=http://localhost:8100&opts={%22state%22:%229Jv1wh4i9X3eroDnnKyn2GnvNyQ%22,%22state_type%22:%22client%22}%22', 'Authorization', 'target=self');

I just don't understand what is the "d" url param and what is used for?

Ok gotcha, is the list of authorized domains!
thanks


Add 'Featured' section to the Apps & Marketplace Charts page

See UX ticket: https://github.com/rancher/dashboard/issues/5007
Update the Charts view in 'Apps and Marketplace" as per the following:

Specifically:

Add a toggle switch in the top-right 'Browse | Featured' - the default will be 'featured', but this should be persisted in a user preference, so that the choice is remembered across logins

Choosing 'Browse' will present the page as is - i.e. just showing the list of charts available with the filtering controls - e.g.

Choosing 'Featured' will show a new section above the existing content - this is shown as the carousel in the design mentionned at the top of this ticket - for this ticket, JUST add the4 carousel for featured charts, NOT the recent list below.

For now, create a method 'getFeaturedCharts' which will should return at mot 5 charts to show in the featured carousel. For development, you can hard code this function to select any 5 charts from those installed - once the chart annotations are in place, we an update the function to use real data to get the actual featured charts to display. The function should arrange the 5 charts, so that the most recently added/updated chart is shown in the middle

Charts in the carousel should be shown in order 5 3 1 2 4 from a list of featured charts which is ordered from most recently added/updated to least - i.e. the newest chart of interest should be in the middle (1)

If there are no features charts available, the code should be smart enough to not display anything different to the user from what they currently see.

The carousel should cope with there being between 1 and 5 featured charts

Please update the size label on this issue with the estimate for how long you think this will take (in work days)

@richard-cox is there a related backend ticket for getting data? I can't find a ticket that indicates what they need to do.

Not sure, Richa stated the dashboard PR was blocked waiting for actual data (https://github.com/rancher/dashboard/pull/5585#issuecomment-1150964061). @bisht-richa was there a backend ticket?

I checked with backend folks and they weren't aware of anything. I'll push this out to 2.7.1 unless there's something actionable since the schedule for 2.7.0 is fast approaching.

@gaktive we can talk about this one - it's driven by chart annotations / so doesn't need backend, just partner charts updates

There is the ticket for Featured Charts: Wire in annotation support https://github.com/rancher/dashboard/issues/6664

this isn't ready for test
not seen in 2.7-head commit ID 4092002
saw in 2.7.0-rc3, but no functionality tied to the featured toggle.

@richard-cox I'm not able to use that repo. at what point will the work be merged so that i can see it in 2.7.0?

@nwmac should be able to provide more detail on the chart uptake. this is probably a chicken and egg scenario

logged bug for dup tiles: https://github.com/rancher/dashboard/issues/7243

testing complete 2.7.0-rc8
test repo: https://nwmac.github.io/rancher-charts
test cases:

toggle switch between browse and featured - passed
choice should be persistend as a user setting after logout / login - failed; shows featured when log out and return having set to browse
choosing featured shows the carousel (not the recent list) - passed
create a method 'getFeaturedCharts' which will should return at most 5 charts to show in the featured carousel - passed
If there are no features charts available, the code should be smart enough to not display anything different to the user from what they currently see - passed
The carousel should cope with there being between 1 and 5 featured charts - passed - tested with 1, 4 and 5

additional testing:
general click throughs; clicked ui components (direction arrows, position dots under featured carousel); inspected console for ui errors; installed various featured/non-featured charts; toggling multiple times


Implement pagination for consumers page

Is your proposal related to a problem?
Following issue #856
In some of the clusters I use I have a lot of consumers: the largest cluster on this point has 582 consumers.
Loading the consumers page can take a long time (58s here) and some users asked me if the UI is failing or not.

Describe the solution you'd like
Set a pagination on consumers page would be very helpful.
This would lower the global response time, improve the user experience and not let the user wondering if it is failing or not.

Hey @giom-l,
thanks for reporting this issue.
This seems like a really important thing to have, we'll implement this within the next release.

Consider implementing #928 within single PR.

Pending frontend


[simulation] simulate energy scan

This commit implements energy scan in simulation platform.
Verified locally
> ifconfig up
Done
> scan energy 100
| Ch | RSSI |
+----+------+
| 11 |  -79 |
| 12 |  -92 |
| 13 |  -57 |
| 14 |  -64 |
| 15 |  -91 |
| 16 |  -75 |
| 17 | -100 |
| 18 |  -66 |
| 19 |  -53 |
| 20 |  -91 |
| 21 | -100 |
| 22 |  -57 |
| 23 |  -67 |
| 24 |  -42 |
| 25 | -100 |
| 26 |  -72 |
Done

@bukepo , do we still want to continue with this PR?
Per https://github.com/openthread/openthread/pull/7393#discussion_r801147969 I think the mian intention was to be able to debug the posix and RCP timeout issue which I think we found the root cause (from https://github.com/openthread/openthread/issues/7429).

@bukepo , do we still want to continue with this PR? Per #7393 (comment) I think the mian intention was to be able to debug the posix and RCP timeout issue which I think we found the root cause (from #7429).

I think this still can improve the code coverage. I can add a few tests later. Thoughts?

@abtink I've updated the code to share RSSI simulation and added a test for energy scan enabled on RCP. Could you please take another look?


Wallet API implementation

** WIP **
test currently fails because delete_wallet requires a signature and there's no python lib implementing this, pending a PR on https://github.com/petertodd/python-bitcoinlib

The wallet  functionality in  this python library will be very useful to me,   so be aware of my bias  in the following comment:
There is currently not much of a dependency on outside code,  but this P.R. will introduce a dependency on python-bitcoinlib, which has a dependency on openssl,  on recent version of  fedora openssl  is broken (missing ECC).
Im not sure what you mean by signature,  but code signing  transactions  in python is already available,  see here:  https://github.com/vbuterin/pybitcointools/blob/3213b0a99ab41a06125e45276258437e7ea8d178/bitcoin/transaction.py#L333 ,
But pardon my ignorance since  in delete_wallet  i do not expect that its transactions that are being  signed.  So what exactly do you mean by signature?  and who much work would be required to get something done in pure python without pulling in   python-bitcoinlib?

Hey @thebookworm101 that's very valuable feedback to know that openssl is broken on fedora!
When you want to delete a wallet you need to use your private key to sign a message to prove you really have the private key, to avoid someone being able to delete a wallet if they get your API key.
So there we need to sign a message with a privatekey, but in a bit of a different way than normal transaction signing (compatible with the signmessage and verifymessage from bitcoind).
I actually tried using pybitcointools and pycoin first before using python-bitcoinlib, the reason for choosing python-bitcoinlib over pybitcointools is that when I tried pybitcointools I ran into a few bugs and I'm also not very comfortable with the relatively low amount of unittests.
And to top it all off it seems that the lead maintainer isn't very active or interested anymore in this library, judging but the activity of commits and the lack of response to the pull requests I did for that library; https://github.com/vbuterin/pybitcointools/pulls
However, if using python-bitcoinlib means that our SDK doesn't work on fedora then I think I'll spend some extra time to see if I can fix the issues in either of the other libraries.

Ok,
if i get you right  then it must be something along these lines:
https://github.com/jackjack-jj/jasvet/blob/master/jasvet.py#L407
im i thinking what you intended?
If  iv got you right i could extract the code (from pybitcointools/this link) into an independent module so it can be used separately.

yea, that's the stuff, nice find!
the biggest problem I see right now is that both pycoin and pybitcointools are very slow in responding to pull requests and for either one of them I will need to do a few pull requests to fix some small bugs they have ...
Another option is adding support for using https://github.com/bitcoin/secp256k1 to python-bitcoinlib, which would probably be the best / coolest solution since then we'll be using the same code as bitcoin core for signing / verying.
The hard part is that users need to build it first ...

Its not that hard, especially if we  package it together  as some libraries do,  since setups/pip can do actual builds, this may not be a problem.  My biggest worry would be dependencies,  and as it stands,
python-bitcoinlib's  dependency on openssl which is missing ECC on fedora (the tests segfault, its that bad).  But also,  should you choose to send PRs to one of the two  (python-bitcoinlib, pybitcointools)  it may  have to be one or the  other, since they both send up in the same package namespace (https://github.com/vbuterin/pybitcointools/issues/78 ),  clobbering each other.
Another suggestion for easing users pain in compiling is to create a  .deb and .rpm + others for common operating systems.


Fix/line endings

fix remaining line-endings (undesired CRLF) and improve .gitattributes.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.772%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4587

Relevant Lines:
7389

💛  - Coveralls


Improve hashes view

A few things that could be improved here:

The hashes don't need to be in entries, since you don't need to edit them and there's a button for copying. I'd just use regular title/subtitle rows, with the hash as subtitle
Hashes might be easier to read if they had spaces in regular intervals, e.g. every 4 characters

Looks much better to me, and I think not having overflow is also functionally better.
One thing I'd maybe still try here is using a monospace font for the hashes.


added my_heart when...

i tried adding a new meme template.. pls verify its working..

yo poggers

https://discord.com/channels/746202728031584358/746229113496403978/870223057799757864


./routes file is missing from Server Rendering Guide

On https://github.com/rackt/react-router/blob/master/doc/00 Guides/Server Rendering.md, both the client and server import something from a ./routes file, but there's no example of what ./routes exports.

just a temp solution, the ./routes is an array of the routes you have.
[
        <Route path="/" component={Main}>
          <Route path="home" component={Home}/>
          <Route path="about" component={About}/>
        </Route>,
        <Redirect from="*" to="home"/>
]

its just your route config, as used everywhere else:
var routes = (
  <Route>
    <Route/>
    <Route/>
  </Route>
)


strict types in CreatePlanSubscriptionFeaturesTable

Status
READY
Migrations
YES
Description
Missing declare(strict_types=1); in one of migrations

👍


SCB-1374 support fsm redis channel

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-2.08%) to 80.741% when pulling b94f1b609b1f9e807e14f18cf9b54b4985004917 on cmonkey:feature/1317 into fa608a2b660f21bde6870d6dc80a6f2ccc75ef89 on apache:master.

When Alpha cluster, only one RedisMessageSubscriber should be allowed at the same time. Otherwise, it will repeat consumption.
You can use the following method to determine whether the current node is the master node.
@Autowride
NodeStatus nodeStatus;

if(nodeStatus.isMaster()){
  // Is master
}


offline: expose ability to get pending state without closing container

Fix AB#4181
Expose existing ability to stash pending local changes from Container.closeAndGetPendingLocalState() but without closing the container.
This increases the risk of stash blob misuse. In addition to not reusing stash blobs, callers of this API must be careful not to use them after the container has reconnected, i.e. when it emits a "connected" event.

Can we do anything to detect misuse faster? It's already easy to misuse it, this opens even more floodgate.
I'd strongly recommend putting experimental tag on getPendingLocalState() and a big warning on API itself why it's dangerous. Someone not knowing much about internal implementation details could start using it, without understanding danger.

Can we do anything to detect misuse faster? It's already easy to misuse it, this opens even more floodgate. I'd strongly recommend putting experimental tag on getPendingLocalState() and a big warning on API itself why it's dangerous. Someone not knowing much about internal implementation details could start using it, without understanding danger.

The current usage requires turning on a feature flag, and casting the container to IContainerExperimental, and only then is the getPendingLocalState available. The method in the interface has a big scary comment warning.
We should additionally give the method a scarier name, like EXPERIMENTAL_getPendingLocalState? but i'm not sure what else we could do?


Unauthenticated?

Hi!
I have been following this guide: https://developers.google.com/assistant/sdk/develop/grpc/
And everything was going great until I actually tried to use "googlesamples-assistant-pushtotalk".
(found here: https://github.com/googlesamples/assistant-sdk-python/tree/master/google-assistant-sdk)
I have made sure everything on the "Activity Controls page" is as it should, and I can see failed attempts to connect from my computer on my API dashboard.
Do you have any tips or suggestions for solving this one?
Thanks!
C:\Users\Mediadator>google-oauthlib-tool --client-secrets C:\Heidi\client_secret
_425569872344-ah7ohkh6hb8s02rii.apps.googleusercontent.com.json --scope
https://www.googleapis.com/auth/assistant-sdk-prototype --save

Please visit this URL to authorize this application: https://accounts.google.com
/o/oauth2/auth?response_type=code&client_id=425569872344-ah7ohvkh6hb8s07882
f3o452rii.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8080%
2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fassistant-sdk-prototype&state
=0ZV85EvczQG862ZQde1lSeVe&access_type=offline

credentials saved: C:\Users\Mediadator\AppData\Roaming\google-oauthlib-tool\credentials.json

C:\Users\Mediadator>pip install --upgrade google-assistant-sdk[samples]
Requirement already up-to-date: google-assistant-sdk[samp..... (abv.)
..............................
Installing collected packages: urllib3
  Found existing installation: urllib3 1.22
    Uninstalling urllib3-1.22:
      Successfully uninstalled urllib3-1.22
Successfully installed urllib3-1.21.1

C:\Users\Mediadator>googlesamples-assistant-pushtotalk
AsioDrv::: CAsioDrv()...
AsioDrv::: InitWdmDrv()...
INFO:root:Connecting to embeddedassistant.googleapis.com
Press Enter to send a new request...
INFO:root:Recording audio request.
Traceback (most recent call last):
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\runpy.py", line 193, in
_run_module_as_main
    "__main__", mod_spec)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\runpy.py", line 85, in
_run_code
    exec(code, run_globals)
  File "C:\Users\Mediadator\AppData\Local\Programs\Python\Python36-32\Scripts\googlesamples-
assistant-pushtotalk.exe\__main__.py", line 9, in <module>
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\googlesamples\assistant\grpc\pushtotalk.py", line 317, in main
    continue_conversation = assistant.converse()
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\tenacity\__init__.py", line 87, in wrapped_f
    return r.call(f, *args, **kw)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\tenacity\__init__.py", line 235, in call
    do = self.iter(result=result, exc_info=exc_info)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\tenacity\__init__.py", line 194, in iter
    return fut.result()
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\concurrent
\futures\_base.py", line 425, in result
    return self.__get_result()
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\concurrent
\futures\_base.py", line 384, in __get_result
    raise self._exception
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\tenacity\__init__.py", line 238, in call
    result = fn(*args, **kwargs)
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\googlesamples\assistant\grpc\pushtotalk.py", line 110, in converse
    self.deadline):
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\grpc\_channel.py", line 348, in __next__
    return self._next()
  File "c:\users\mediadator\appdata\local\programs\python\python36-32\lib\site-packages
\grpc\_channel.py", line 342, in _next
    raise self
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNAUTHENTICATED,
Request is missing required authentication credential. Expected OAuth 2 access token,
login cookie or other valid authentication credential.
See https://developers.google.com/identity/sign-in/web/devconsole-project.)>

I actually had everything working just fine... it's been giving me no trouble for the past few weeks and just today it seems to have un-authenticated itself and now gives me the same message it's giving you.  It may or may not be related... wish I could be of some help though.

Looks similar to
https://github.com/googlesamples/assistant-sdk-cpp/issues/12#issuecomment-349841929

Same here. To reproduce just run one of your examples - pushtotalk.py. It's not working anymore.

Yes we became aware of this issue last night and are rolling out a fix. Thanks for reporting.

The fix should be fully rolled out now.

Confirmed working!  Thank you for the prompt resolution!

It's working, Thank you!

It's working, Thank you!

The issue started happening again for me. Anyone else in the same boat? It was working for a while though, which is nice.

@Taconut what error are you getting? It seems to work fine for my test case.

It started working a few minutes before you posted and it's been working ever since... I'll post on here if it stops again.

@Fleker Can you please help me with this issue .
GoogleAdsException: (<_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAUTHENTICATED
details = "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential.


Delay Node config issue - milliseconds

So I've been using delay node and stumbled across an issue:
If you have Action set to Delay Message, and For set to "Milliseconds" the scroll up counter stops at 60 rather than 1000.
Node-RED version: v0.11.1-git
Node.js  version: v0.10.36

oops well spotted.. thanks


DBZ-4824 Expect the null value with snapshot CapturedTables metric when skipping snapshotting

https://issues.redhat.com/browse/DBZ-4824

LGTM, thanks!


docs: improve error message when multiple events with same name defined

What I did

fixes: #751
How I did it
Well, it does not actually resolve their error but gives more detail on how to fix it.
It seems problematic to have two events with the same name so I am guessing it is probably best to raise an error.
An alternative is to rename the events to Initialized_0 and Initialized_1 and so on (plus a WARNING), but that seems not ideal from the project's perspective.
Any other ideas? Is  veYfi able to rename Gauge.Initialized event?
How to verify it

Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

I am really trying to think if there is a better solution to do.. Like are we able to detect if the event is coming from an outside source?


ArangoSearch refactor

HTTP docs:

there is no attribute "properties": { ... } expected, but rather the View properties directly (same level as name and type). This needs to be fixed (pointed out by Vadim).
there are multiple places where the response object is described, but without code and error
result is not mentioned / described as containing the important query result
globallyUniqueId is not mentioned and missing a description - it's an internal attribute as per Vadim, which collections have as well.


Feedback RC1 release

Feedback will be appreciated!

Congrats on getting this out!
Just a note, after pulling our hair out for a while we settled on Serilog.Extensions.Logging for the Serilog version of the provider, after the framework package was renamed to .Extensions.
(This mimic's Autofac's move to Autofac.Extensions.DependencyInjection - figured they'd set a precedent.)
Posting this in case it saves you from a bit of churn, and it'd be great for all of the providers to have some consistency. HTH, and best of luck!

@nblumhardt Thanks! I agree, consistency is nice. Missed that with the rename at Microsoft. (as their repos isn't renamed)

Hey, thanks for the release. I am not sure this is an issue, but I found following;
Nlog writes everything from Asp.Net such as initialization etc. however, I didn't see it writing anything from my application for example logger.LogDebug("User {0} trying to login", userName");.
After a bit investigation, I managed to get it write by setting loggerFactory.MinimumLevel = LogLevel.Debug; inside public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)() method.
However, now the log writes with level TRACE, eventhough logger.LogDebug() were used.
Much appreciated your efforts to provide us this great framework.

Hi, that looksike a bug. How is logger created here?

Configured as below;
        public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {
            //loggerFactory.AddConsole(Configuration.GetSection("Logging"));
            //loggerFactory.AddDebug();
            loggerFactory.AddNLog();
            loggerFactory.MinimumLevel = LogLevel.Debug;

            env.ConfigureNLog("NLog.config");
.... // more code
}

and logger created using DI as below;
        public AccountController(
            UserManager<LoginUser> userManager,
            SignInManager<LoginUser> signInManager,
            ILogger<AccountController> logger)
        {
....
}

Thanks!
This is not a bug. Will write some more about it.

Thank you, that clarifies the issue.

It's now time for RC2 :)


Add waste-collection-erding to latest

Please add my adapter ioBroker.waste-collection-erding to latest.
This pull request was created by https://www.iobroker.dev c0726ff.

@klein0r
@Sickboy78
Does the existing adapter trashschedule (https://github.com/klein0r/ioBroker.trashschedule) already support "erding"?
If  not, wouldn't it be an option to integrate this supplier into trashschedule? I assume that klein0r will accept a PR for this.
Do we need another waste adapter dedicated to a region?
@Apollon77
Some general oppinion?

Imho Erding is currently not supported since LK Erding does not provide an ICAL calender (only ICS and CSV for download) and the API portal.awido.de is not integrated into trashschedule.
But it would totally make sence to integrate it, if this is possible. Need to take a closer look though ...

I would suggest that you take a look if you have time and eventually discuss a solution with klein0r. Let's wait for the result.
Thanks for you cooperation.

If the adapter can be integrated independently and not in Trashschedule, I would ask you to migrate the adapter to jsonConfig.

@klein0r @mcm1957
While digging into the Awido API for integration with trashschedule, I found that it is used by nearly 50 districts and cities, i.e. it would add hundreds of cities to be available in trashschedule.
So heres the PR:
https://github.com/klein0r/ioBroker.trashschedule/pull/285

Functionality was integrated with trashschedule, therfore canceling this PR.


FR: Icon property descriptions are not clear about the icon weight/size

What happened?
Hello, by deafult the icon weight is set to outline while the docs says otherwise. What's the truth?

Thanks 🙌
Version
Live website (5.5 i presume)
React and ReactDOM version
No response
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct

[X] I've searched across open and closed issues for similiar bug reports

Ready to be released
https://github.com/wonderflow-bv/wanda/pull/88

Thanks, indeed the issue arised from the property description of weight, now everything is clear 🙌


Device can be created with VK_KHR_push_descriptor and without VK_KHR_get_physical_device_properties2

It looks like dependent extensions are not checked when creating the device - creation of device with VK_KHR_push_descriptors but without VK_KHR_get_physical_device_properties2 that it depends on succeeds without warnings/errors.
When trying to use vkCmdPushDescriptorSetKHR, the validation does error if VK_KHR_get_physical_device_properties2 isn't specified but this check seems like it should be performed earlier.

This actually seems to crash hard inside the validation layers now during vkCreateDevice (enabling VK_KHR_push_descriptor without VK_KHR_get_physical_device_properties2), which isn't really better :)

PR 2586 fixes this.


Cloudflare support

I had no success in making my cloudflare signed certificates work with Syncplay. I couldn't find an equivalent for cert.pem that was mentioned in the documentation.
I have tried using Cloudflare Origin CA — RSA Root but the server kept trying to reconnect and displayed the following error OpenSSL.SSL.Error: [('x509 certificate routines', 'X509_check_private_key', 'key values mismatch')]
As Syncplay server does not specifically ask for any DNS, I was wondering how it did guess the DNS and eventually if it supported subdomains.
If someone could tell me what I am missing here I would greatly appreciate it.

Hi, I read the Cloudflare link you posted here, but it is not clear to me how many and which files the Crypto app provides to you by default.
By looking at the Apache guide linked in Step 2 (even though that guide seems made for Digicert and I am not sure if that exactly applies to Cloudflare as well), it seems that three files are provided. I quote:

SSLCertificateFile is your DigiCert certificate file (e.g., your_domain_name.crt).
SSLCertificateKeyFile is the .key file generated when you created the CSR (e.g., your_private.key).
SSLCertificateChainFile is the DigiCert intermediate certificate file (e.g., DigiCertCA.crt)

If this is true, I would just use the SSLCertificateFile as cert.pem, the SSLCertificateKeyFile as privkey.pem, and the SSLCertificateChainFile as chain.pem. Is that what you did?

Syncplay is not DNS aware in any way. It doesn't know or care what DNS your operating system is using to resolve domain names.
Syncplay requirements are pretty simplistic:

cert.pem needs to be a PEM format file containing single leaf certificate - this is the bit that you get back from whoever signs your certificate after you sent them request with your public key. If you look at it with tools that can understand PEM format you'll see Common Name (CN) with your domain name.
privkey.pem is the file with your private key (that matches to the public key you sent). It generally is generated along with public key in the very beginning of the process of getting your valid TLS certificate
chain.pem contains intermediate certificate that was used to sign your leaf certificate. Its name always (I think so?) tells you which certificate authority has signed your certificate. In your case it will be Cloudflare.

The error you have seems to point towards something being wrong with the files. Either they don't have the contents Syncplay expects, or they are in wrong format.
That said - from glancing at your link it seems that Cloudflare Origin certificates are supposed to be used for encrypting communications between your server and Cloudflare proxies (which have the actual certificates that clients will see). Cloudflare Origin Root CA isn't trusted by normal clients so I'm unsure what exactly are you trying to achieve here? Unless you want to proxy your Syncplay connections over Cloudflare infrastructure for some reason? Even if you manage to provide this certificate to Syncplay in right format, you'd still have to manually add Cloudflare CA to trust roots of all the clients (which is almost certainly not what you are supposed to do).

If my reading of https://support.cloudflare.com/hc/en-us/articles/200169156-Which-ports-will-Cloudflare-work-with- is correct then Cloudflare does not support non-HTTP/HTTPS traffic and so will not be compatible with Syncplay.

Thanks you all for your quick responses.
As @daniel-123 pointed out, I was not sure about what I wanted to accomplish. I was trying to proxy HTTPS communications on an app that didn't use HTTP(S) to begin with.
For that I would need Cloudflare Spectrum proxying which is only available in the enterprise plan as denoted above by @Et0h.
Everything is now more clear in my head!


Support Conditional Gatekeeper Configuration

Please describe the problem you have:
Detect whether gatekeeper is running in the cluster and automatically install the relevant validation configuration for Contour and Envoy.
/cc @jpeach

There are at least a couple categories of Gatekeeper policies that the operator could manage:

Policy for Contour CRDs: https://projectcontour.io/guides/gatekeeper/

Policy for Service APIs CRDs: https://github.com/kubernetes-sigs/service-apis/issues/404

Gatekeeper project and documentation are here:  https://github.com/open-policy-agent/gatekeeper
This would be post-v1alpha1.


Have to touch the testsuite.at to make the tests work on MSYS2

I have just created a matio-package for MSYS2, see https://github.com/Alexpux/MINGW-packages/pull/2296
So far my mileage is pretty good, but in order to make test test suite work, I have to use a strange
workaround: I have to touch test/testsuite.at before executing make check. Is thee some logic
that uses the file date for something related to the tests? If yes, is there a better, cleaner solution
then to touch the file?

Sorry, I have no idea, since I am not a GNU tools expert.


GH-4: Add Map support and some error handling

Fixes spring-cloud-stream-app-starters/field-value-counter#4

Provide a Map payload type support for field extraction
Add error logging when field isn't available in the payload
Log info when value is null - nothing to count though

LGTM.
Merged.


Disable runtime error "Error: Missing AWS Lambda trace data for X-Ray. Expected _X_AMZN_TRACE_ID to be set"

Hi, we're using AWS X-Ray SDK in Lambda, and when it attempt to trace code running on function initialization we're getting error
Error: Missing AWS Lambda trace data for X-Ray. Expected _X_AMZN_TRACE_ID to be set

We understand that Lambda context is being set at function invocation and expect this error. We're trying to suppress it, but whether we try
process.env.AWS_XRAY_CONTEXT_MISSING = 'LOG_ERROR';

or
AWSXRay.setContextMissingStrategy(() => {});

it still throws this error - including full stack trace. How can we suppress this error?

I might be mistaken, but I believe because this override is being set, when I call setContextMissingStrategy() - it is being ignored.
So the workaround I found is to tap directly into context_utils.js:
const contextUtils = require('aws-xray-sdk-core/lib/context_utils.js');

contextUtils.contextMissingStrategy.contextMissing = (message: string) => {
  console.warn(`AWS X-Ray error: ${message}`);
};

This kinda feels like a hack - is it ok to use it like this? Could this potentially break?

@alexandre-bonfim yes, and solution is two-fold: first is to properly disable default error messaging, second is to create your own context to run custom trace. Basically it comes down to this:
delete process.env.AWS_XRAY_CONTEXT_MISSING;

AWSXRay.setContextMissingStrategy((message: string): void => {
  const logError = {
    error: `${message} If this is Lambda init event you need to explicitly setup X-Ray to run in isolated context.`,
    stack: new Error(message).stack,
    highbondCleansed: true,
  };

  console.log(JSON.stringify(logError));
});

/** Runs function {func} and traces it in isolated X-Ray context
 * @param segmentName {string} name of the X-Ray segment to create
 * @param func {()=> void} code to run in isolated context
 * @param annotations {Record<string, string>} optional annotations to attach to segment
 */
export function traceInIsolatedContext(
  segmentName: string,
  func: () => void,
  annotations?: Record<string, string>,
): Segment {
  const segment = new AWSXRay.Segment(segmentName);

  if (annotations) {
    for (const key in annotations) {
      if (annotations.hasOwnProperty(key)) {
        segment.addAnnotation(key, annotations[key]);
      }
    }
  }

  const ns = AWSXRay.getNamespace();
  ns.enter(ns.createContext());
  AWSXRay.setSegment(segment);

  func();

  segment.close();

  return segment;
}

So if you need to run some code and trace it in Lambda init event you can do something like this:
traceInIsolatedContext(
  'lambda-init',
  () => {
     // your traced code
     // runs here
  },
  {
    purpose: 'Lambda initialization',
    servicesUsed: 'S3, DynamoDB'
  },
)


Unexpected/unsupported platform 'linux2'

When I execute npm start, I receive
Python: Traceback (most recent call last):   File "./run_map.py", line 7, in <module>     import check_prereqs   File "/home/ivomarsan/tests/PokemonGo-DesktopMap/app/check_prereqs.py", line 30, in <module>     raise Exception(err) Exception: Unexpected/unsupported platform 'linux2'.
Help

@ivomarsan npm start is trying to execute your npm modules but this release has python and git issues on linux as you've seen. Could you execute git gud at the command line and post the output?

`$ git gud
git: 'gud' não é um comando git. Veja 'git --help'.
Você quis dizer isso?
add
`
git gud is not a git command

@ivomarsan It looks like your installation of Git is either out of data or corrupted. Its not safe to work with a corrupted version. I'd suggest that you remove Git entirely from your system and then re-execute git gud as it should fix your issues.

I'm not getting


ALM register not present in adis1649x register map

ALM register not present in adis1649x register map

Hi,
I've purposely left out the alarm registers since I didn't need to use them for my examples. If you were to add them, I would be happy to merge your pull request.


Please consult Mendelian randomization：gestational diabetes

Mendelian randomization: I did a two sample Mendelian randomization randomization study, and the outcome indicator was gestational diabetes. The data for outcome indicators were obtained from the Finnish database version R9. But now the result of Mendelian randomization is negative. I am thinking about the reasons that led to a negative outcome. My research object is pregnant women. Do I need to screen out those who have given birth in the downloaded data? How to exclude people who have not been pregnant or had children from Finnish databases？So how to filter? Can you give me some guidance? Thank you.

Hello, thanks for your question.
Accessing individual-level data — such as pregnancy status for each FinnGen participants — is only possible with a so called FinnGen "red" account.
You can find more infomation here about accessing FinnGen data here: https://finngen.gitbook.io/finngen-handbook/where-to-begin.../how-to-request-an-account
Hope this helps!


Script tags not stripped from feed titles on /feeds endpoint

I believe I have discovered an XSS issue in Stringer (the most recent version pushed to Docker Hub).
Here's a POC for it:

Run Stringer using the instructions in https://github.com/swanson/stringer/blob/master/docs/docker.md (The SQLite and Docker Compose instructions instructions both work.)
Serve an RSS feed that has an entity-encoded script tag in its title. (i.e. <script>alert('xss')</script> )
Add your webserver for that feed to Stringer
Go to the /feeds endpoint in your browser. You should see the alert.

I have created an example RSS feed that demonstrates this at https://gist.github.com/rwhogg/1a7b9e9f82db6fdfb266af2cd09cfb9a

Thanks for the report. Here is the relevant section of the code: https://github.com/swanson/stringer/blob/master/app/repositories/story_repository.rb#L106-L117
We are using the loofah gem for sanitization: https://github.com/flavorjones/loofah but it sounds like this case is not being caught. Not sure if there is a problem with the library or our usage of it.
We should be able to add a failing test for this scenario as well: https://github.com/swanson/stringer/blob/master/spec/repositories/story_repository_spec.rb

Thanks Victor!


Add h3ToCenterChild and getPentagonsAtRes

Resolves #263.

Coverage remained the same at 100.0% when pulling 88309e89582742603fd4cc51b86791bcc2c2e1ad on zachasme:feature-add-h3tocenterchild into f6106a9e88789f28acc34a70cbd7b3f0a0354a42 on uber:master.

What are your thoughts on naming?
The atRes suffix is not used anywhere else, perhaps getPentagonalIndexes/pentgonalIndexCount would be better?

What are your thoughts on naming?
The atRes suffix is not used anywhere else, perhaps getPentagonalIndexes/pentgonalIndexCount would be better?

We also don't use pentagonal anywhere :). I don't mind atRes but could see just getPentagons or getPentagonIndexes. No strong preference.

Thank you for all the feedback! I believe I've addressed it all. Please let me know if I've missed something.
I've added static bool _isValidChildRes(int, int) which is now used in h3ToChildren, maxH3ToChildrenSize, h3ToCenterChild, uncompact and maxUncompactSize as per your suggestion.


acl enhancement.

acl enhancement.

@suraj-webkul
There are some conflicts in the PR hence unable to merge them. Please resolve and assign for testing.


Sensu Server is not working, restart does not work

The Sensu Server isn't working. The Clients send the data to the server, but he doesn't recognize them.
But there are no keepalive Error Messages.
A Try to restart the server ends in a timeout
Try to restart:
/etc/init.d/sensu-server restart
configuration is valid
 * Stopping sensu-server
 * Timed out waiting for sensu-server to stop

Excerpt of server-log:
{"timestamp":"2016-08-16T10:52:42.721104+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2016-08-16T10:52:42.721230+0000","level":"warn","message":"stopping"}
{"timestamp":"2016-08-16T10:52:42.721317+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2016-08-16T10:52:42.721561+0000","level":"warn","message":"resigning as leader"}
{"timestamp":"2016-08-16T10:52:42.721599+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":0}}
{"timestamp":"2016-08-16T10:52:57.730058+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2016-08-16T10:52:57.730183+0000","level":"warn","message":"stopping"}
{"timestamp":"2016-08-16T10:52:57.730219+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2016-08-16T10:52:57.730371+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":0}}
{"timestamp":"2016-08-16T10:53:13.740482+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2016-08-16T10:53:13.740608+0000","level":"warn","message":"stopping"}
{"timestamp":"2016-08-16T10:53:13.740644+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2016-08-16T10:53:13.740766+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":0}}
{"timestamp":"2016-08-16T10:53:28.750240+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2016-08-16T10:53:28.750365+0000","level":"warn","message":"stopping"}
{"timestamp":"2016-08-16T10:53:28.750398+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2016-08-16T10:53:28.750515+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":0}}
{"timestamp":"2016-08-16T11:30:06.813612+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2016-08-16T11:30:06.813718+0000","level":"warn","message":"stopping"}
{"timestamp":"2016-08-16T11:30:06.813751+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2016-08-16T11:30:06.813864+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":0}}

strace:
/home/ubuntu# strace -p 28489
Process 28489 attached
select(11, [7 9 10], [], [], {0, 380714}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 93044850}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 93161833}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 93218948}) = 0
select(11, [7 9 10], [], [], {0, 49737}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 143289156}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 143392469}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 143477307}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 143547709}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 143609675}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 143659261}) = 0
select(11, [7 9 10], [], [], {0, 442269}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 586599263}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 586720860}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 586777276}) = 0
select(11, [7 9 10], [], [], {0, 6384}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 593430505}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 593509387}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 593572888}) = 0
select(11, [7 9 10], [], [], {0, 49820}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 643680988}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 643801988}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 643874839}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 643940620}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 644002249}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322238, 644049465}) = 0
select(11, [7 9 10], [], [], {0, 449460}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC_RAW, {4322239, 94215137}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322239, 94363336}) = 0
clock_gettime(CLOCK_MONOTONIC_RAW, {4322239, 94419900}) = 0
select(11, [7 9 10], [], [], {0, 49382}) = 0 (Timeout)

It looks like after some time we cannot stop sensu anymore. It receives the TERM signal according to the logs and stops processing events. But the sensu server process stays alive and does not fully terminate.
@portertech Is this a known bug?

@cwjohnston or @portertech what are these "in_progress" events?
I am thinking about putting something like kill -9 in the sensu init script. But this problem should be better solved in the sensu process...

Hi @kabakakao @runningman84, can you please provide some additional context? e.g.:

Sensu version used?
Operating System and version? (e.g. Ubuntu 14.04)
Transport and runtime versions? (e.g. RabbitMQ 3.6.2 on Erlang 18.2)
Which versions of community plugins and/or extensions are in use on the Sensu server (e.g. handlers)?

@runningman84 Sensu 0.24 added an internal in_progress hash for keeping count of work in progress, e.g. number of checks being processed, events being mutated, events being handled, etc.
The output @kabakakao provided gives us some idea that the sensu-server process is waiting for two check results to be processed before shutting down:
{"timestamp":"2016-08-16T11:30:06.813864+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":0}}
But we lack context to know what the content of those check results might be, or at what point they seem to be stuck in processing.

@cwjohnston the problem happens in all 0.25.x versions right now we use 0.25.7. The problem does not occur on 0.23.x, we haven't used 0.24.x here. We have seen this problem with redis, rabbitmq and snssqs transports. We are using Ubuntu 14.04
The problem even occurs in a small kitchen demo.
We use this cookbook to setup sensu:
https://github.com/runningman84/chef-monitor
I have modified the init script to execute a kill -9 if the normal kill does not work. Here you can see that in 3 out of 5 cases the server did not stop because of in_progress events:
grep -n -A 5 TERM sensu-server.log
60:{"timestamp":"2016-08-23T10:54:43.377518+0000","level":"warn","message":"received signal","signal":"TERM"}
61-{"timestamp":"2016-08-23T10:54:43.377878+0000","level":"warn","message":"stopping"}
62-{"timestamp":"2016-08-23T10:54:43.378281+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
63-{"timestamp":"2016-08-23T10:54:43.378789+0000","level":"warn","message":"resigning as leader"}
64-{"timestamp":"2016-08-23T10:54:43.378983+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":0,"events":0}}
65-{"timestamp":"2016-08-23T10:54:43.880208+0000","level":"warn","message":"stopping reactor"}
--
864:{"timestamp":"2016-08-23T11:50:53.022504+0000","level":"warn","message":"received signal","signal":"TERM"}
865-{"timestamp":"2016-08-23T11:50:53.022636+0000","level":"warn","message":"stopping"}
866-{"timestamp":"2016-08-23T11:50:53.022691+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
867-{"timestamp":"2016-08-23T11:50:53.022830+0000","level":"warn","message":"resigning as leader"}
868-{"timestamp":"2016-08-23T11:50:53.022870+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":1,"events":0}}
869-{"timestamp":"2016-08-23T11:51:02.796952+0000","level":"warn","message":"loading config file","file":"/etc/sensu/config.json"}
--
2006:{"timestamp":"2016-08-23T13:12:44.052386+0000","level":"warn","message":"received signal","signal":"TERM"}
2007-{"timestamp":"2016-08-23T13:12:44.052620+0000","level":"warn","message":"stopping"}
2008-{"timestamp":"2016-08-23T13:12:44.052697+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
2009-{"timestamp":"2016-08-23T13:12:44.052864+0000","level":"warn","message":"resigning as leader"}
2010-{"timestamp":"2016-08-23T13:12:44.053089+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":1,"events":0}}
2011-{"timestamp":"2016-08-23T13:12:53.641294+0000","level":"warn","message":"loading config file","file":"/etc/sensu/config.json"}
--
3660:{"timestamp":"2016-08-24T07:34:53.489185+0000","level":"warn","message":"received signal","signal":"TERM"}
3661-{"timestamp":"2016-08-24T07:34:53.489515+0000","level":"warn","message":"stopping"}
3662-{"timestamp":"2016-08-24T07:34:53.489696+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
3663-{"timestamp":"2016-08-24T07:34:53.490218+0000","level":"warn","message":"resigning as leader"}
3664-{"timestamp":"2016-08-24T07:34:53.490373+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":1,"events":0}}
3665-{"timestamp":"2016-08-24T07:35:03.769136+0000","level":"warn","message":"loading config file","file":"/etc/sensu/config.json"}
--
3848:{"timestamp":"2016-08-24T07:43:36.676217+0000","level":"warn","message":"received signal","signal":"TERM"}
3849-{"timestamp":"2016-08-24T07:43:36.676428+0000","level":"warn","message":"stopping"}
3850-{"timestamp":"2016-08-24T07:43:36.676521+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
3851-{"timestamp":"2016-08-24T07:43:36.676760+0000","level":"warn","message":"resigning as leader"}
3852-{"timestamp":"2016-08-24T07:43:36.676869+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":0,"events":0}}
3853-{"timestamp":"2016-08-24T07:43:37.177480+0000","level":"warn","message":"stopping reactor"}

This is the full log
https://gist.github.com/runningman84/e2b4d8d3c1c276490b96361c8f662148
There are no special handlers active, only the debug and deregistration handlers are active...

@calebhailey any chance to get this fixed soon?
There is another report of this issue in the user group:
https://groups.google.com/forum/m/#!topic/sensu-users/gcx4FJHcMQI

Tagging this for review w/ the impending 0.26.2 release.

I can't definitely say we if saw this in 0.23 and 0.24.  Our internal bug was filed Jun 17th and I'm sure we saw it well before then.  One of our servers show the gem creation times as -
drwxr-xr-x. 4 root root 4.0K Jun  9 21:07 ./ruby/gems/2.3.0/gems/sensu-0.23.3
drwxr-xr-x. 4 root root 4.0K Jun 20 17:43 ./ruby/gems/2.3.0/gems/sensu-0.24.1
drwxr-xr-x. 4 root root 4.0K Jul 27 01:26 ./ruby/gems/2.3.0/gems/sensu-0.25.3

Which should correlate with when those versions were in use.  We have have ~8 sensu installations, some of which have multiple sensu-server processes in them.
We have also added a kill -9 to our deployment scripts to work around the problem.

But we lack context to know what the content of those check results might be, or at what point they seem to be stuck in processing.

If you have a suggestion of how I can debug it further, or a patch to apply to process.rb, to gain that context I'd be happy to try it.  Its been quite easy for me to reproduce in the past, though erratic in how long it takes to happen.  That is, sometimes if I restart after 5 minutes it happens again, sometimes it takes a few hours.
I was thinking about adding some debugging lines every time something is added to in progress, and another when its removed.  Then I can look through to see what was added and never removed.  Thoughts?

Found the cause https://github.com/sensu/sensu/pull/1455

@kabakakao we think we've identified the source of the incomplete check result processing as being related to check results with an invalid signature. Possibly related to #1435 and #1452.
Closed by #1455 which will be released in 0.26.2 shortly.

Still seeing issued using 0.26.3-1
{"timestamp":"2016-09-28T20:24:07.738290+0000","level":"warn","message":"received signal","signal":"TERM"} {"timestamp":"2016-09-28T20:24:07.738549+0000","level":"warn","message":"stopping"} {"timestamp":"2016-09-28T20:24:07.738657+0000","level":"warn","message":"unsubscribing from keepalive and result queues"} {"timestamp":"2016-09-28T20:24:07.738822+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":0,"events":3}}
[root@d5fbe29b96ba kitchen]# /opt/sensu/bin/sensu-server --version 0.26.3

@dcrawkstar we need more detail on this, specifically if you are loading any extensions. Will you please open a new issue, using the template to provide context with regard to your environment and configuration?

We're still experiencing this issue.  We're running 0.26.3 and have no extensions on centos 6.
Our deployments now automatically kill -9 the sensu-server process if it can't stop, but going back through our logs, the last 5 deployments over the last three weeks have had to the kill -9.
The logs from a recent one
{"timestamp":"2016-10-26T00:08:06.817550+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2016-10-26T00:08:06.820421+0000","level":"warn","message":"stopping"}
{"timestamp":"2016-10-26T00:08:06.820501+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2016-10-26T00:08:06.821092+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":2,"events":1}}

In that log snippet above, the sensu installation has three sensu-server processes.  They were all restarted and 2 of 3 failed.
I don't know how to reproduce this, however I can pretty much find it on one of our servers every day.
If you have some debugging steps, I'd be happy to try them

Also seeing the same on 0.25.5
[root@sensu3 ~]# /etc/init.d/sensu-server restart
configuration is valid
Stopping sensu-server{"timestamp":"2017-01-04T17:41:45.420798+0000","level":"warn","message":"received signal","signal":"TERM"}
{"timestamp":"2017-01-04T17:41:45.420977+0000","level":"warn","message":"stopping"}
{"timestamp":"2017-01-04T17:41:45.421045+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2017-01-04T17:41:45.421268+0000","level":"info","message":"completing work in progress","in_progress":{"check_results":0,"events":138}}
```\


makemkv: 1.14.1 -> 1.14.3

Motivation for this change
Changelog:
https://www.makemkv.com/download/
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@grahamcofborg build makemkv


Update event-trigger.yaml

Add namespace attribute to spec.subscriber.ref section so that the Trigger shows in the UI under the Service.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Fix with another workaround.

Fix with another workaround.

How did you end up fixing this differently, @jcawley5?

How did you end up fixing this differently, @jcawley5?

The uri was set with a fqdn
https://github.com/SAP-samples/kyma-runtime-extension-samples/blob/master/api-mssql-go/k8s/event-trigger.yaml

The uri was set with a fqdn
https://github.com/SAP-samples/kyma-runtime-extension-samples/blob/master/api-mssql-go/k8s/event-trigger.yaml


Flow CLI not detecting flow.json[BUG]

Current Behavior
Im trying to get the project to build, but whenever Im in the root directory and run flow emulator start I get an error stating:
🙏 Configuration is missing, initialize it with: 'flow init' and then rerun this command., even though there is  a flow.json file in the root directory.
I then attempt to run flow init command as suggested by the error and then I get the following error:
❌ Command Error: configuration already exists at: flow.json, if you want to reset configuration use the reset flag
Here is my current FCL version:
Version: v0.45.1-cadence-attachments-3
Commit: 1b24e6a50e7c0e3c17e1424ef2ec1000a5a7c423

Any thoughts on how to proceed?
Expected Behavior
The flow emulator should recognize the flow.json file and run as normal.
Steps To Reproduce

Clone project
cd into project root
run flow emulator start

Environment
- OS: Mac OS 13.1 Beta
- Node: v14.18.2
- npm: 6.14.15

What are you currently working on that this is blocking?
Trying to understand how this project works for the hackathon.

Thanks for the flag @cryptobank04
As the main flow.json references two additional files, you should make sure they exist and the correct values are added/updated based on your environment and account/key info. If files referenced from flow.json don't exist you will get that warning.
You can run the following to create emulator.private.json and testnet.private.json
// copy emulator.private.json.example and testnet.private.json.example files and update with your own key data.

cp emulator.private.json.example emulator.private.json
cp testnet.private.json.example testnet.private.json


MongoDB authentication failure.

Is anyone experiencing mongoDB authentication failure issues ? I am using mongolabs

me too !!

I guess this is because of the outdated mongoose version, try with mongoose 3.8.39.

I had the same problem. Updating mongoose solved it. thx @GlennGeenen

May be your are trying to connecting to a mongo instance without authentication. In that case use
connectionString: mongodb://localhost/uptime

Thanks, this solved it for me!


Windows opens dialog to pick best app for .env file

I have a student who just ran into this bizarre issue on Windows.  We're using run.env like this in an npm script:
"release": "run.env release-it --"

We run it with npm run release and he gets this dialog on Windows:

I looked around for others discussing this, and can't find any reference.  I have no idea what's causing it for him on that machine, but I thought I'd make you aware of it.

Thanks @humphd for bringing this to my attention.
No one else has reported similar issue.
Unfortunately, I don't have a Windows machine with me at this time to check this.
But, it looks like the run.env script is not being associated with Node.js command.
Can you run the script with npx - npx run.env release-it --.
HTH.


fix typos

Fix solidity_examples/rubixi.sol
Fix tests/testdata/input_contracts/rubixi.sol

 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.snoppy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


monitor disk usage in _influxdb

Here is the list of current measurements (query_indb_df(auth, "SHOW MEASUREMENTS", database='_influxdb')):
              measurements.name
0           server_batchWriteRx
1     server_broadcastMessageRx
2     server_broadcastMessageTx
3                  server_build
4                   server_diag
5                     server_go
6                 server_memory
7           server_pointWriteRx
8        server_queriesExecuted
9              server_queriesRx
10         server_shardsCreated
11                server_system
12  server_writeSeriesMessageTx
13             shardGroups_diag
14             shard_shardBytes
15             shard_shardWrite
16   shard_writeSeriesMessageRx
17                  shards_diag

It would be useful to record current disk usage (remaining bytes perhaps) in server_system or server_diag or somewhere more appropriate (I think broker nodes also need something like this)

_influxdb no longer exists as a queryable database.


Fix skinny device styling

iPhone 5/SE simulator on chrome looks bad 😢

fixed in 63110693b207380b5fcca694e49c2dc2afc5b2a0, thanks @Oisin-M !!!!!!!!!!!!!!!


BL3P: move supporting classes to ExchangeBL3PAPI class

On PR #475 I made all these classes internal. :thinking:

I'm okay with either way. I'll leave it up to @jjxtra


EdgeEvent - Point on constrained edge not supported yet

What steps will reproduce the problem?
1. Input data has constraints intersecting points of data not at endpoints

What is the expected output? What do you see instead?
I know its a TODO, but what can be done to handle this :)
'Exception: EdgeEvent - Point on constrained edge not supported yet'

What version of the product are you using? On what operating system?
Latest C# version

Please provide any additional information below.
The library works great by the way! So kudos to the developers. I would just
love to not get the above exception on our users data.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 22 Nov 2010 at 10:44

hello,
Can you please describe what you changes in java version. can you share java code. or link where it is provided.
Thank you.


REST: Make it possible to set body's easily for any request type

It would be useful if it was easy, from within the REST handlers, to set the body of a response (according to the media_type as well), such that if a client asks for application/json a callback will be called for serving the client application/json.

I am not sure what this ticket is about anymore... :-)

Closing until I know more. Please reopen or comment when you can! Thanks.