test: fix unstable test test_node_merge_write_data_to_source_region_after_m…

…erging
Signed-off-by: linning<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close #7909
Problem Summary:
the test test_node_merge_write_data_to_source_region_after_merging first split then merge and then split at the same split_key again, the test panic because failed at the second split.
In the test, after the first split and before merge commit, the leader of the new region s1 that generated by splitting, is isolated, but it keeps sending region epoch to PD with epoch { conf_ver: 2, ver: 3 }, the conf_ver increased because it is the source region.  The second split generated region s2 which has the same start and end key with s1, and has epoch { conf_ver: 1, ver: 5 }, also sending region heartbeat to PD. But if s1's request arrives before s2 then s2's request will be rejected and hence the test panic at must_split.
What is changed and how it works?
What's Changed:
Changing how check_stale_region check epoch, let ver have higher priority than conf_ver, so that epoch { conf_ver: 1, ver: 5 } >= epoch { conf_ver: 2, ver: 3 }.
Tests

Integration test

Release note

No release note

I think maybe it's better to separate the same regions and the different regions.
If they are different regions, just check the version and panic if two versions are equal because it should not happen.
If they are the same, the check order is unnecessary because the epoch should be unique.

The changes to check_stale_region are not for the case where version equal and conf_ver not, but to define order for cases like epoch { conf_ver: 2, ver: 3 } and epoch { conf_ver: 1, ver: 5 } where a.ver > b.ver but b.conf_ver > a.conf_ver.

I think maybe it's better to separate the same regions and the different regions.
If they are different regions, just check the version and panic if two versions are equal because it should not happen.
If they are the same, the check order is unnecessary because the epoch should be unique.

The changes to check_stale_region are not for the case where version equal and conf_ver not, but to define order for cases like epoch { conf_ver: 2, ver: 3 } and epoch { conf_ver: 1, ver: 5 } where a.ver > b.ver but b.conf_ver > a.conf_ver.

It's not possible if these two regions are the same.

Depend on how you define two regions is the same. By the key range (which is also how test_raftstore::TestPdClient do), it's exactly what happens on test_node_merge_write_data_to_source_region_after_merging, checkout the abovementioned detail. @gengliqi

Depend on how you define two regions is the same. By the key range (which is also how test_raftstore::TestPdClient do), it's exactly what happens on test_node_merge_write_data_to_source_region_after_merging, checkout the abovementioned detail. @gengliqi

The definition of two same regions is based on region id. If two regions are different, their epoch version can be compared if and only if their key ranges are overlapped.

The definition of two same regions is based on region id. If two regions are different, their epoch version can be compared if and only if their key ranges are overlapped.

That is what I mean depend on key range. In normal cases, both confchange and split/merge that can change epoch will show up in raft log, one by one in order, so incoming epoch should >= exist epoch on both ver and conf_ver, but when applying prepare_merge both ver and conf_ver of the source region will be increased, that is how the case where a.ver > b.ver but b.conf_ver > a.conf_ver happens.

/run-integration-common-test

/run-all-tests

/run-integration-common-test


feature: Prerender using webpack

Prerender fails when webpack specific stuff is in js code (described here #43, here #39, here #62 and possibly other places).
This fixes that by creating separate webpack bundle just for prerender with commonjs2 target.
This adds some overhead when building, but I couldn't use webpack's multiple compiler with two configs because some plugins failed. :cry:
WIP because I must fully test this & wanted to hear early feedback.

A thought I had:  could we produce a UMD bundle that would be usable in both the client and the server?

If you don't mind I might also take a stab at this with the UMD approach.  Might not work at all so I don't want to waste your time :D

@developit go ahead! :smile:
Also, I'm thinking about using some in memory file system (memfs for example) for webpack builds so that there won't be some magic folder called in npm module (+using normal fs breaks concurrency) :smile:

@developit I didn't see your first comment.

A thought I had: could we produce a UMD bundle that would be usable in both the client and the server? Definitely interested in any way to avoid the overhead of 2 concurrent builds. I think the closest prior art I know of here would be static-site-generator-webpack-plugin - maybe their technique would work. Or maybe a webpack bundle that can detect if its running under node/cjs and do a module.exports, otherwise performs a client render.

Technically possible. Passing two configs to webpack with two entries (sth like webpack([{ entry: 'index.js', rules: ... }, { entry: 'App.js', rules: ... }]) doesn't add overhead and webpack doesn't seem to process same file twice (at least based on time it takes to compile). However, there is a problem with some plugins (just a guess) that are applied twice and throw errors. I want to investigate that and possibly exclude those plugins in SSR build.

I've been able to pinpoint location of the erroneous plugin :smile:, this: goldhand/sw-precache-webpack-plugin#78 will enable us to use single webpack compiler pass & reduce overhead. :tada:

All wrapped up & tested.
Chosen not to use any memory filesystem (require doesn't work) and webpack creates ssr-build folder with bundle for SSR - this will be convenient when we will be working for server-side integration of rendering routes.
@developit if you haven't started yet & have some ideas for further work on this, feel free to work on this branch. :smile:
I'm thinking about writing some tests that would be able to verify the CLI works correctly (not only running builds, but running built bundles & watch mode).

@rkostrzewski I think we should bump the sw-precache dependency now that your PR there has been merged.

I haven't tried the code yet, but is polyfilling history and location enough? Where do the other things Preact uses (such as document.createElement) come from?

@kurtextrem During SSR, only h() is actually invoked from Preact. It knows to avoid any DOM mutation :)

How can I help move this PR forward? I'm looking to use prerendering with Sass.

just an fyi, i just debugged
#42 is also being caused due to prerender, i am trying to dig deeper, will post if any finding comes up

I just tried this branch on my site and I got the following error:
(undefined) Template execution failed: Error: Cannot find module '/Users/mypath/build/ssr-build/ssr-bundle.js'
(undefined)   Error: Cannot find module '/Users/mypath/build/ssr-build/ssr-bundle.js'

  - module.js:20 require
    internal/module.js:20:19

  - prerender.js:17 prerender
    [website]/[preact-cli]/lib/lib/webpack/prerender.js:17:10

  - webpack-client-config.js:156 Object.ssr
    [website]/[preact-cli]/lib/lib/webpack/webpack-client-config.js:156:54

  - template.html:109 EM6I.module.exports
    [website]/[preact-cli]/lib/resources/template.html:109:37

  - index.js:265
    [website]/[html-webpack-plugin]/index.js:265:16

  - util.js:16 tryCatcher
    [website]/[html-webpack-plugin]/[bluebird]/js/release/util.js:16:23

  - promise.js:512 Promise._settlePromiseFromHandler
    [website]/[html-webpack-plugin]/[bluebird]/js/release/promise.js:512:31

  - promise.js:569 Promise._settlePromise
    [website]/[html-webpack-plugin]/[bluebird]/js/release/promise.js:569:18

  - promise.js:606 Promise._settlePromiseCtx
    [website]/[html-webpack-plugin]/[bluebird]/js/release/promise.js:606:10

  - async.js:138 Async._drainQueue
    [website]/[html-webpack-plugin]/[bluebird]/js/release/async.js:138:12

  - async.js:143 Async._drainQueues
    [website]/[html-webpack-plugin]/[bluebird]/js/release/async.js:143:10

  - async.js:17 Immediate.Async.drainQueues
    [website]/[html-webpack-plugin]/[bluebird]/js/release/async.js:17:14

LGTM! I just went through and tested this super thoroughly. Also tried using the few config options differently for templates and such. :)

teaaaam let's put this in master yo

@hassanbazzi +1 but looks like tests are failing?

Seems like snapshots have different sizes on CI.

LGTM :)


Propagation labels are not optional

Documenation says propagation labels are optional, but because of a bug - this is currently not the case. I created this ticket so if anyone else encounters this, they know we have this issue as well.
We currently just pass the "all" label by default, as we don't need the propagation labels in our integrations.

without the Computed: true option on the propagation_labels attribute the provider was unable to set the value received from the API in the state, creating the inconsistent result. please pull the latest commit and see if this resolves your issue.

Have confirmed just now, this fixes the bug we were having! Thanks for the quick response!
Thank you for the explanation for your fix as well, this helps me understand the issue and fix it myself in the future 😊. All this provider development in Go is still quite new for me...


illustrate a message

Hello !
I apologize for my rudimentary English, I am a French-speaking Belgian. I have tried to understand the changes requested, and apart from my "payload.concat()", I am almost sure of myself.
I'll check this function later. ;)

Just seen changes, all looks good apart from the README.
The note about how color has to be hexadecimal should be with the bit which talks about the custom function.

And now ? 😃

Looks good to me, just need to update this with the new stuff on master. Then I'll test it out.

I'm currently testing this and neither the image in custom or image is working? Am I calling this correctly:
> x.custom("test", "test", "test", null, "https://josephbanks.me/background1.jpg")
> x.image("test", "test", "test", "https://josephbanks.me/background1.jpg")

Yes

Not appearing in my tests

I've forgot a 's' to "embeds" https://gist.github.com/Birdie0/78ee79402a4301b1faf412ab5f1cdcf9

It's normally work now

So what I did didn't work out?
If so, do you have the API documentation used?

https://api.slack.com/docs/message-attachments

Damn :D https://birdie0.github.io/discord-webhooks-guide/other/slack_formatting.html

That's awesome! Thank you for your contribution. I'll merge this and then push the new version to NPM!

Thank you! I will pull some other cool features in the future. Thank you for this project. 😉


unfurl: command not found

Hi,
I think there is one unresolved dependency here. It says unfurl: command not found. Can you please guide which unfurl are we exactly talking about?
Thanks,

Thanks @robre,
Maybe add that as a dependency? https://github.com/robre/scripthunter/pull/6


Refactor saving denied dialog

whenever there is an error when trying to open/save a file a dialog is shown
contains a couple of refactorings

Steps to reproduce:

Open a file
Remove it from disc
Click on disabled save button.

So there are two issues to fix:

No error message for Error: ENOENT: no such file or directory (IMO to fix in this PR)
Calling save callback for disabled button (separate issue #1010)

Closes #977

@philippfromme any update about this?

Unfortunately not. I have it on my list but won't be able to work on it until tomorrow at least. Bear with me.

Rebased on top of latest next branch.

@barmac How to reproduce error N.1, now as https://github.com/camunda/camunda-modeler/issues/1010 is fixed?
If there are no other concerns with the implementation I'm inclined to simply get this merged and create follow up issues for what is missing.
I guess there is more important downstream issues, i.e. fixing dirty state checking (which prevents us from saving at all right now).

@nikku Indeed, the save button is disabled after the file is deleted. I agree that it's time to merge it.


bump osmosis to v13.1.0

refs.
https://www.mintscan.io/osmosis/blocks/7241500
https://www.mintscan.io/osmosis/proposals/370
https://raw.githubusercontent.com/osmosis-labs/osmosis/main/networks/osmosis-1/upgrades/v13/v13_binaries.json
https://github.com/osmosis-labs/osmosis/releases/tag/v13.1.0

Already been updated


Android: Allow the use of user certificates for nightly builds

Task/Issue URL: https://app.asana.com/0/414730916066338/1202500711374963/f
Description
Allowed user certificates for internal builds.
Steps to test this PR

checkout this branch
build the release versions for play (./gradlew assemblePR), fdroid (./gradlew assembleFR), internal (./gradlew assembleIR)
install each of them and have Charles proxy configured
verify you can see traffic in Charles only for the internal build

NO UI changes

Rather than having 3 network configs (fdroid, play, and internal) could we only add the internal override, and let it pick up the existing one otherwise? or are you forced to add it for the build types?

Rather than having 3 network configs (fdroid, play, and internal) could we only add the internal override, and let it pick up the existing, default one otherwise? or are you forced to add it for all the build types?

This is the general approach when different configs are needed for different flavours. I'm not aware of a way to overcome the duplication.


Incorrect url in section Track your message center tasks in Planner

In the section Track your message center tasks in Planner
The link  Track your message center tasks in Planner. point to url https://docs.microsoft.comoffice365/planner/track-message-center-tasks-planner. This url is incorrect and showing an error.
The correct url is https://docs.microsoft.com/en-us/office365/planner/track-message-center-tasks-planner

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

ID: 29f3771a-247c-4f85-992a-e671285c70bd
Version Independent ID: f3c2890a-2470-9349-ff77-924cf8566365
Content: Manage messages in Message center - Microsoft 365 admin
Content Source: microsoft-365/admin/manage/manage-messages.md
Service: o365-administration
GitHub Login: @Sirkkuw
Microsoft Alias: sirkkuw

@nikki-c Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3862
Thanks
Sri

@nikki-c Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3862
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @nikki-c Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @nikki-c Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Adding Better Support for Specification Version Linking

Publication Specification
Generally for all versioned IHE tech framework publications (both supplements and TF volumes).
Specifically (for this issue) the profiles.ihe.net/DEV/SDPi supplement versions
Priority
Medium - Companies have workarounds by replicating all spec revisions in their in-house repositories, but that is a company-specific solution.
Issue
Many companies have requirement management tools (e.g., DOORS) as part of their product tool chains, and these often require permalinks for identifying the specific version of a document in which the referenced requirement is located.  Given the typical multi-year lag between specification revisions and product releases (specifications are updated far faster than product implementations), there is a need to be able to reliably retain published versions of a specification to which a link may point.  Currently, profiles.ihe.net only publishes the most current version, with previous releases retained only in Github.
Proposed Change
A similar issue is addressed in HL7 FHIR by providing a Publication (Version) History page.
Taking this approach, it would be relatively simple to:

Add subdirectories for each published release (e.g., profiles.ihe.net/DEV/SDPi/1.0.1/index.html)

NOTE:  The subdirectory can simply use the Github release label for its name

Link the "current" publication from the domain page to the most recent version
Add a published revisions page (a la the FHIR example above) with a table that we simply add to for each iteration)

See related email thread between @d-gregorczyk  & @MaryLJ  + comments from @JohnMoehrke.

I think we need to differentiate between Trial-Implementation and Final-Text.
ITI does support version specific publications for Trial-Implementation phase; but not for Final-Text. For Final-Text our goal is to support only the current publication, allowing tagged github for historic. To support versions on Final-Text is to endorse our readers to use version specific Final-Text; which is very much against the principle of IHE Final-Text. ITI has seen very bad behavior and outcomes from this kind of version specific Final-Text; we do not want to encourage it.
see https://github.com/IHE/publications/wiki/Revision-Management
along with the other wiki articles on publications - https://github.com/IHE/publications/wiki

@JohnMoehrke  - agree that there is a difference between TI and FT (integrated into the TF).  disagree that this would unduly "endorse" use of outdated / superseded versions, though I'm sure you have some pretty good "you gotta be kidding me" stories around this area.
Reality is that products often lag "current" spec versions by years - and on a national basis, sometimes for a VERY long time (e.g., HL7 V2 nationally mandated versions in various countries).   There
We could take a similar approach to FHIR (as with the link at the top of this thread) where what you see when you look at the publications are the most recent (current state) specifications.  But then you provide a separate location where the previously published versions are kept.
Github release links won't work for our purposes, since those resolve to a package (compressed) and not to individual files.

If your dominant use-case is FHIR.. Please see the maturity model efforts going on in the IHE Documentation Workgoup. The stages before Final-Text are indeed version specific. IHE should resist allowing an IHE-Profile to go Final-Text when the standards it is profiling are not yet Normative. We should not be shooting our own foot. ITI has been very strict on keeping Supplements Trial-Implementation until the standard it is based is Normative.

The Gemini team will take care of this need using another non-IHE site.


Some changes

I have made this changes to repo:

Added config file for custom cache key : user can publish config and change cache key name in sessions and cookies.

While initiating user instance sometimes $this->request->cookie() return null and while inserting to db we have an error, so I initiated user id in a variable before setting in cookie and used it for session. so If cookie return null, instanced will save in db and set to session correctly.

I used md5 for user id for saving as instance for hiding ip address in end of it.

Thanks

:+1:  appreciated updates

Thanks.


Some smal code refactorings

refactorings broken out from #1722 and #1725

Codecov Report
Patch coverage: 57.14% and project coverage change: -0.05 :warning:

Comparison is base (54d4ec0) 39.26% compared to head (ee36d04) 39.22%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1727      +/-   ##
==========================================
- Coverage   39.26%   39.22%   -0.05%
==========================================
  Files         169      169
  Lines       10814    10815       +1
==========================================
- Hits         4246     4242       -4
- Misses       6292     6297       +5
  Partials      276      276

Impacted Files
Coverage Δ

server/model/secret.go
48.07% <0.00%> (ø)

server/model/const.go
44.44% <66.66%> (ø)

server/forge/configFetcher.go
95.23% <100.00%> (+0.04%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Verify hook names match for processing

#415

Thanks!

@tidwall, hey, when the fix is will be available in docker?
Thanks!


Update user and dev guides

Coverage remained the same at 85.72% when pulling f4f8f7f434eacd5e71f0c74a3112cfb15f074b54 on lancehaoh:master into adac2c7e607c783299a0bcf95d024bf477ecfdd3 on CS2103AUG2017-W11-B1:master.

Coverage remained the same at 85.72% when pulling 33920c94ebc341a3449bd8ce47e084417de7bc6d on lancehaoh:master into adac2c7e607c783299a0bcf95d024bf477ecfdd3 on CS2103AUG2017-W11-B1:master.

Sorry, dude for being too late.


Full User Registration

[x] Registration
[x] Login
[x] Logout
[x] Password Recovery

Bugs:

[ ] post-login should display proper flash message
[ ] Login should display errors in flash message
[ ] Successful password change should log in user


[Bug] Documentation of SPADE module requires more details

Describe the bug
The SPADE documentation requires more details on how to run the SPADE analysis, in particular the pattern filtering functions. Given the speed-optimized SPADE code, these should then also enter the corresponding tutorial.

@stellalessandra Would you be willing to help out in improvements to the docs for SPADE?

Regarding this topic, the description of the outputs also needs better clarification in the docs.
For instance, the output dictionary is complex, with elements that will be present depending on the parameters. The documentation of spade function refers to the output of concept_output_to_patterns in one case.
However, the documentation of the latter seems to be wrong with respect to the actual output. Namely, it mentions that the lags element is "lags (integers corresponding to the number of bins) between the spikes of the patterns. Actually, Quantity arrays are returned (floats with time units), and the entry in lags is the time of the bin with respect to the time in times list, i.e., the time lag with respect to the start of the pattern, not between the spikes (and not a bin number).


Fix allowable characters for AML workspace name.

Add underscores to the list of allowable characters for an Azure Machine Learning workspace name.

@tfitzmac

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


com.apple.m4a-audio is unrecognized ZTYPEUTI

OS: 	Ubuntu 18.04.1 LTS
Starting Apple Notes Parser at Fri Jun  3 15:44:02 2022
Storing the results in ./output/2022_06_03-15_44_02

Created a new AppleBackup from single file: /home/admin/src/NoteStore.sqlite
Guessed Notes Version: 15
com.apple.m4a-audio is unrecognized ZTYPEUTI, please submit a bug report to this project's GitHub repo to report this: https://github.com/threeplanetssoftware/apple_cloud_notes_parser/issues
Skipping Note ID 279 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 542 due to a missing folder or account, check the debug log for more details.
Traceback (most recent call last):
	21: from notes_cloud_ripper.rb:128:in `<main>'
	20: from /home/admin/src/apple_cloud_notes_parser/lib/AppleBackup.rb:157:in `rip_notes'
	19: from /home/admin/src/apple_cloud_notes_parser/lib/AppleBackup.rb:157:in `each'
	18: from /home/admin/src/apple_cloud_notes_parser/lib/AppleBackup.rb:159:in `block in rip_notes'
	17: from /home/admin/src/apple_cloud_notes_parser/lib/AppleNoteStore.rb:193:in `rip_all_objects'
	16: from /home/admin/src/apple_cloud_notes_parser/lib/AppleNoteStore.rb:506:in `rip_notes'
	15: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:193:in `execute'
	14: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:151:in `prepare'
	13: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:198:in `block in execute'
	12: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/resultset.rb:134:in `each'
	11: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:199:in `block (2 levels) in execute'
	10: from /home/admin/src/apple_cloud_notes_parser/lib/AppleNoteStore.rb:507:in `block in rip_notes'
	 9: from /home/admin/src/apple_cloud_notes_parser/lib/AppleNoteStore.rb:605:in `rip_note'
	 8: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:193:in `execute'
	 7: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:151:in `prepare'
	 6: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:198:in `block in execute'
	 5: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/resultset.rb:134:in `each'
	 4: from /var/lib/gems/2.5.0/gems/sqlite3-1.4.2/lib/sqlite3/database.rb:199:in `block (2 levels) in execute'
	 3: from /home/admin/src/apple_cloud_notes_parser/lib/AppleNoteStore.rb:631:in `block in rip_note'
	 2: from /home/admin/src/apple_cloud_notes_parser/lib/AppleCloudKitRecord.rb:31:in `add_cloudkit_sharing_data'
	 1: from /home/admin/src/apple_cloud_notes_parser/lib/AppleCloudKitRecord.rb:31:in `each'
/home/admin/src/apple_cloud_notes_parser/lib/AppleCloudKitRecord.rb:36:in `block in add_cloudkit_sharing_data': undefined method `[]' for nil:NilClass (NoMethodError)

Sorry for the delay, Github notifications haven't been reaching me and I didn't realize this was opened. I'm cleaning up a few ZTYPEUTI things and will try to get Audio support into the next push. Thanks for the poke, it also gave me the impetus to better do video as well.


[12.x] Let MassAssignmentExceptions support multiple unfillable attributes

This PR aims is to update the way MassAssignmentException works.

[x] Let MassAssignmentException support multiple guarded attributes
[x] Let MassAssignmentException support one or many attributes
[x] Let MassAssignmentException support passing the impacted model instead of the class name.

Probably does not bring much value


Backport tangerine whistle's gas constants

What was wrong?
Tangerine Whistle introduced a couple new gas constants. This cluttered the diff.
How was it fixed?
This PR backports them to older hard forks.
Cute Animal Picture

Codecov Report

Merging #417 (a59db95) into master (55d7fd7) will decrease coverage by 0.00%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #417      +/-   ##
==========================================
- Coverage   75.53%   75.53%   -0.01%
==========================================
  Files         152      152
  Lines        7943     7949       +6
==========================================
+ Hits         6000     6004       +4
- Misses       1943     1945       +2

Flag
Coverage Δ

unittests
75.53% <66.66%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/ethereum/dao_fork/vm/gas.py
0.00% <0.00%> (ø)

src/ethereum/dao_fork/vm/instructions/block.py
0.00% <0.00%> (ø)

...c/ethereum/dao_fork/vm/instructions/environment.py
0.00% <0.00%> (ø)

src/ethereum/frontier/vm/gas.py
100.00% <100.00%> (ø)

src/ethereum/frontier/vm/instructions/block.py
96.87% <100.00%> (ø)

...c/ethereum/frontier/vm/instructions/environment.py
99.06% <100.00%> (ø)

src/ethereum/homestead/vm/gas.py
100.00% <100.00%> (ø)

src/ethereum/homestead/vm/instructions/block.py
100.00% <100.00%> (ø)

.../ethereum/homestead/vm/instructions/environment.py
99.06% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 55d7fd7...a59db95. Read the comment docs.


Recording log slowly

stable run for long time ，what needs to be configured ?
LOG:
2017-11-09 15:14:45.5247   11  INFO EventNotificationsJob Auto completed EventNotificationWorkItem queue entry (bd4283622184461286352e5c8518ceae).
2017-11-09 15:14:45.5247   11  INFO EventNotificationsJob Processing EventNotificationWorkItem queue entry (dd3c6788020d4614bf6942062cf8c57c).
2017-11-09 15:14:45.5247   22 ERROR EventPostsJob Error processing EventPost queue entry (8dbf285f430a4439a1fe3a9fb9a514e3). System.Exception: Unable to remove item from the dequeued list.
   at Foundatio.Queues.InMemoryQueue`1.<CompleteAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Exceptionless.Core.Jobs.EventPostsJob.<>c__DisplayClass14_0.<<CompleteEntryAsync>b__0>d.MoveNext() in C:\projects\exceptionless\src\Exceptionless.Core\Jobs\EventPostsJob.cs:line 278
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Foundatio.Utility.Async.<>c__DisplayClass3_0`1.<<Using>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Foundatio.Utility.Async.<Using>d__0`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Foundatio.Utility.Async.<Using>d__0`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Exceptionless.Core.Jobs.EventPostsJob.<ProcessQueueEntryAsync>d__8.MoveNext() in C:\projects\exceptionless\src\Exceptionless.Core\Jobs\EventPostsJob.cs:line 188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Foundatio.Jobs.QueueJobBase`1.<ProcessAsync>d__17.MoveNext()
2017-11-09 15:14:45.5247   22 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to remove item from the dequeued list. System.Exception: Unable to remove item from the dequeued list.
   at Foundatio.Queues.InMemoryQueue`1.<AbandonAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Foundatio.Jobs.QueueJobBase`1.<ProcessAsync>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Foundatio.Jobs.QueueJobBase`1.<ProcessAsync>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Foundatio.Jobs.QueueJobBase`1.<RunAsync>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Foundatio.Jobs.JobExtensions.<TryRunAsync>d__0.MoveNext()`

What kind of behaviors are you seeing? From what I can tell you have a single node instance and you are using in memory versions. The error you are getting suggests either there was an error dequeueing an item from a concurrent queue or that there was no queue entries.  Looking at the code: https://github.com/FoundatioFx/Foundatio/blob/1c1d817d54c968484dffc536c6225fb8674b771c/src/Foundatio/Queues/InMemoryQueue.cs#L182
/I can see that it couldn't be removed or something already dequeued it. What version are you using? What happens if you restart the app (please note any enqueued items will not be processed, as the queue will be cleared)

this service run stable for a few months and today I found the log is slow , run one exceptionless (v4.1.0)  ,three es(v5.5) node ; when restart the exceptionless  server, i can run for a few minutes, and then log will be delayed, due to too much request ?

What is your throughput? How many events are you sending in per second? What is the resource usage on the web box?

I check the server throughput is not large,I think eventjob sends the request to es too slowly

Is elasticsearch on the same box as this web server? Task manager view would be better to see so we can see CPU, memory and IO

IIS:

ES：

All that looks great, what I would do is configure redis (https://github.com/exceptionless/Exceptionless/wiki/Self-Hosting#redis) within the web application and then also configure an events post job but also keep the jobs running in process (https://github.com/exceptionless/Exceptionless/wiki/Self-Hosting#running-jobs-out-of-process). Then you can scale out your event queue jobs to process more events. Can you try this and let us know if it's better.

I do this , run EventPostJob have a problem
2017-11-16 16:57:21.3969    1  WARN Bootstrapper StatsD Metrics is NOT enabled.  2017-11-16 16:57:21.4281    1  WARN Bootstrapper Azure Storage is NOT enabled.  2017-11-16 16:57:21.9437    1  INFO JobRunner Starting job type "Exceptionless.Core.Jobs.EventPostsJob" on machine "021YUN130067S"...  2017-11-16 16:57:23.9437    4  INFO EventPostsJob Starting continuous job type "EventPostsJob" on machine "021YUN130067S"...  2017-11-16 16:57:24.3969    5 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\d85eb62fc6494cccb5f253cc5eca2560.json'.  2017-11-16 16:57:24.3969    6 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\5f931e842d5c4fe1a14b19a34786b3ae.json'.  2017-11-16 16:57:24.4124    5 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\108d58e00dcb47b19c44165062569678.json'.  2017-11-16 16:57:24.4124    7 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\a6339f7fccd048f5b209e2e6347a7e02.json'.  2017-11-16 16:57:24.4124    4 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\6cd01fecec5545458eed4f112f9b32c8.json'.  2017-11-16 16:57:24.4437    7 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\6bcbf92123c846abb2a731d92fb75b5a.json'.  2017-11-16 16:57:24.7718    4 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\d55e51eff1c84f8193ae84457eb23b98.json'.  2017-11-16 16:57:26.1781    5 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\5dc0ea4b82e042de81b0f8d5fb1db7b2.json'.  2017-11-16 16:57:28.2563    7 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\fe4d33a50ea34f7e9f1525a0c0ee2867.json'.  2017-11-16 16:57:29.5218    4 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\5666255340ac48ee955d90c3349c23e6.json'.  2017-11-16 16:57:29.6000    5 ERROR EventPostsJob Job run "EventPostsJob" failed: Unable to retrieve post data info 'q\fd218c3561e74b969bc581a9ef483e9b.json'.

i update exceptionless on ssd , run five events post job ,but not working better well. Initially think either network or es  server problem（es did't use ssd）.

We recommend running elastic on SSD's but depending on your throughput you should have more than enough resources as is for efficient queueing. What is your throughput? How many events are you sending in per second/hour to the exceptionless service?

I cleaned up the all es data，it's work , most of the data?

Everything looks great from all the images you've sent. If you could let me know how it's acting slow. For example, I send in 10 events and it takes a minute to process them. If I have some numbers to go off of that would help.

Is this still an issue?

Were you able to resolve this issue and determine why it was periodically slowing down? I'm trying to remember why this issue was reopened.

This is using the inmemoryqueue and should be resolved with our latest round of Foundatio changes.

Please see the latest version 7.1.0 has these issues as we've done a bunch of perf work and bug fixes. If so please let us know and we'll reopen this issue.


KAFKA-3426; Improve protocol type errors when invalid sizes are received

LGTM

cc @ewencp @gwenshap

LGTM


docs(quickstart): put systemjs configuration outside verbose section

As it sits right now, if we hide the explanations, we hide the systemjs configuration and that is not good.
Fixes #1321

Merged with PR 1304 in commit 142ad5d


Added retries on incomplete downloads.

Hi.
First of all, thanks for the amazing project.
Secondly, as I was downloading the files, I noticed that due to some interruptions in my internet connection and the requests library's inability in handling such situations, I would sometimes get incomplete downloads. This would result in me having to find the incomplete files, removing them and downloading them all over again, which is obviously a lot of work. Therefore, I added a little retry feature to the download function, forcing it to retry downloading a max_retry (currently set to 5) number of times before giving up on a file.
Hopefully you'll find this PR helpful. :D

Thanks

I just noticed a small issue in my PR,
if failed_tries > 5: should be changed to if failed_tries > max_tries:  for consistency.
Just wanted to let you know so you could fix it in the next commit. :D
@yashrathi-git


Issue with Email OAuth 2.0 Proxy - Authentication Failure with O365 (CCG Flow)

Hi,
I'm trying to use email-oauth2-proxy to communicate with O365 using the client credentials flow (CCG), but I'm encountering an authentication failure. Below is a summary of my setup:
Configuration:
Here is my emailproxy.config file (anonymized):
[IMAP-8993]
server_address = outlook.office365.com
server_port = 993
local_address = my_public_ipv4

[SMTP-8587]
server_address = smtp-mail.outlook.com
server_port = 587
server_starttls = True
local_address = my_public_ipv4

<EMAIL_ADDRESS>documentation = *** O365 advanced account example ***
token_url = https://login.microsoftonline.com/$TENANT_ID/oauth2/v2.0/token
oauth2_scope = https://outlook.office365.com/.default
oauth2_flow = client_credentials
redirect_uri = http://localhost
client_id = $CLIENT_ID
client_secret = $CLIENT_SECRET

[emailproxy]
delete_account_token_on_password_error = True
use_login_password_as_client_credentials_secret = True
encrypt_client_secret_on_first_use = False
allow_catch_all_accounts = False

Note: The real config file contains the actual values for TENANT_ID, CLIENT_ID, and CLIENT_SECRET. These variables are just placeholders here.
Log Output:
2024-09-30 03:26:40: Initialising Email OAuth 2.0 Proxy (version 2024-09-24) in debug mode from config file /full-path/email-oauth2-proxy/emailproxy.config
2024-09-30 03:26:40: Starting IMAP server at my_public_ipv4:8993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-09-30 03:26:40: Starting SMTP server at my_public_ipv4:8587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)
2024-09-30 03:26:40: Initialised Email OAuth 2.0 Proxy - listening for authentication requests. Connect your email client to begin

2024-09-30 03:26:43: New incoming connection to IMAP server at my_public_ipv4:8993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-09-30 03:26:43: Accepting new connection from client_email_ipv4:60712 to IMAP server at my_public_ipv4:8993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) --> [ Client connected ]
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-> [ Starting TLS handshake ]
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-> [ TLSv1.2 handshake complete ]
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     <-- b'* OK The Microsoft Exchange IMAP4 service is ready. [QwBQADYAUAAyADgANABDAEEAMAAwADMANgAuAEIAUgBBAFAAMgA4ADQALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-- b'* OK The Microsoft Exchange IMAP4 service is ready. [QwBQADYAUAAyADgANABDAEEAMAAwADMANgAuAEIAUgBBAFAAMgA4ADQALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) --> b'W1 CAPABILITY\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     --> b'W1 CAPABILITY\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     <-- b'* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-- b'* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     <-- b'W1 OK CAPABILITY completed.\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-- b'W1 OK CAPABILITY completed.\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) --> b'W2 ID NIL\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     --> b'W2 ID NIL\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     <-- b'* ID ("name" "Microsoft.Exchange.Imap4.Imap4Server" "version" "15.20")\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-- b'* ID ("name" "Microsoft.Exchange.Imap4.Imap4Server" "version" "15.20")\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     <-- b'W2 OK ID completed\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-- b'W2 OK ID completed\r\n'
2024-09-30 03:26:44: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) --> b'W3 login [[ Credentials removed from proxy log ]]\r\n'
2024-09-30 03:26:46: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     --> b'W3 AUTHENTICATE XOAUTH2 '
2024-09-30 03:26:46: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993)     --> b'[[ Credentials removed from proxy log ]]\r\n'
2024-09-30 03:26:47: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993<EMAIL_ADDRESS>    <-- b'W3 NO AUTHENTICATE failed.\r\n'
2024-09-30 03:26:47: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993<EMAIL_ADDRESS><-- b'W3 NO AUTHENTICATE failed.\r\n'
2024-09-30 03:26:47: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993) <-- [ Server disconnected ]
2024-09-30 03:26:47: IMAP (client_email_ipv4:60712-{my_public_ipv4:8993}-outlook.office365.com:993<EMAIL_ADDRESS>--> [ Client disconnected ]
^C2024-09-30 03:27:27: Stopping Email OAuth 2.0 Proxy
2024-09-30 03:27:27: Stopping IMAP server at my_public_ipv4:8993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-09-30 03:27:27: Stopping SMTP server at my_public_ipv4:8587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)

Problem:
After connecting successfully to the O365 IMAP server, the authentication (AUTH XOAUTH2) fails with a NO AUTHENTICATE failed message, despite using correct client_id and client_secret.
I've double-checked my TENANT_ID, CLIENT_ID, and CLIENT_SECRET, and confirmed they are correct using a shell script to fetch the tokens. The same credentials work outside of the proxy when using OAuth2 with other tools.
Could you provide guidance on what might be causing the failure during the authentication process or suggest any additional steps for debugging?
Thanks in advance for your support!
Best regards,
Neco

The only thing that immediately stands out is that you've set use_login_password_as_client_credentials_secret = True but also provided a client_secret value. This will lead to this option being ignored, and the value you've provided in the configuration file will be used instead of the login password.
Typically when there are problems with a CCG flow setup there is an issue with the Azure / Entra configuration (for example, not granting permission for the required scopes, or missing admin approval, etc). So, just to be clear, when you say the credentials work outside of the proxy, do you mean they work with IMAP/SMTP when you authenticate manually? Or are you referring to other services?


user groups

As an administrator I want to be able to manage users and groups
As an administrator I want to be able to add users to the trusted user group
https://staging.healthsites.io/admin/social_users/trusteduser/
As an administrator I want to be able to define permission levels for a specific group

Group in admin site is group for accessing admin, like change database, add database
I think we don't need to use it, because what permission we use now just:

User can access admin? Just tick is_staff and is_superuser in the user admin page
User can upload data? Just register user in Trusted Useradmin


Regex

closes #14

The use of fnmatchcase is a nice improvement :+1:. I was not aware of this function.


Reward token

Many farms provide additional reward token. It would be great to consider the price evolution of this token too in the compare function.

just add all APR rewards as one unique APR in input function


Constant Timeouts

Features that worked before are suddenly timing out on a new server with nobody on and with 20 tps...
Randomly getting request timeout exceeded API errors...
[10:23:10] [qtp850058231-77/WARN] [webapi]: <IP_ADDRESS> has exceeded the rate limit when requesting /api/info/stats
[10:23:10] [qtp850058231-78/WARN] [webapi]: <IP_ADDRESS> has exceeded the rate limit when requesting /api/servlet
[10:23:11] [qtp850058231-78/WARN] [webapi]: <IP_ADDRESS> has exceeded the rate limit when requesting /api/servlet
[10:23:16] [qtp850058231-152/WARN] [webapi]: <IP_ADDRESS> has exceeded the rate limit when requesting /api/info
[10:23:40] [qtp850058231-152/WARN] [webapi]: <IP_ADDRESS> does not have permission to access /api/history/chat

They keep happening. These were taken 4 minutes ago from writing this but they keep happening. Also my IP is on the include list which is why I can login. Even refreshing the page it randomly works but its randomly having issues..
Possibly relevant chrome logs:
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
raven.js:1058 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
(anonymous) @ raven.js:1058
t @ konva.js:9880
_bindContentEvents @ konva.js:10257
___init @ konva.js:9934
Konva.Stage @ konva.js:9924
value @ react-konva.js:387
commitLifeCycles @ react-dom.production.min.js:149
t @ react-dom.production.min.js:158
_ @ react-dom.production.min.js:169
O @ react-dom.production.min.js:168
batchedUpdates @ react-dom.production.min.js:171
Z @ react-dom.production.min.js:54
Ie @ react-dom.production.min.js:71
r @ raven.js:360
main.3dc02ae0.js:1 [Violation] 'readystatechange' handler took 674ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 150ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 75ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 55ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 53ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 52ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 53ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 53ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 55ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 59ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 79ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 56ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 57ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 56ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 57ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 60ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 56ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 60ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 59ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 57ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 78ms
main.3dc02ae0.js:1 [Violation] 'readystatechange' handler took 248ms

[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
raven.js:1058 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive.  Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
(anonymous) @ raven.js:1058
t @ konva.js:9880
_bindContentEvents @ konva.js:10257
___init @ konva.js:9934
Konva.Stage @ konva.js:9924
value @ react-konva.js:387
commitLifeCycles @ react-dom.production.min.js:149
t @ react-dom.production.min.js:158
_ @ react-dom.production.min.js:169
O @ react-dom.production.min.js:168
batchedUpdates @ react-dom.production.min.js:171
Z @ react-dom.production.min.js:54
Ie @ react-dom.production.min.js:71
r @ raven.js:360
main.3dc02ae0.js:1 [Violation] 'readystatechange' handler took 674ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
[Violation] 'requestAnimationFrame' handler took <N>ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 150ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 75ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 55ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 53ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 52ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 53ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 53ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 55ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 59ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 79ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 56ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 57ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 56ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 54ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 57ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 60ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 56ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 60ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 59ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 57ms
main.3dc02ae0.js:1 [Violation] 'requestAnimationFrame' handler took 78ms
main.3dc02ae0.js:1 [Violation] 'readystatechange' handler took 248ms

Can you send me your users.conf file? Please remove the password in it for security.
Also the permissions.conf file would be useful. You can also replace any sensitive information in there before posting it. Thank you!

[root@mc-server-dev webapi]# cat user.conf
users {
    quantomworks {
        password="[omitted]"
        permissions="*"
    }
}
# Config file version, used to update correctly
version=1
[root@mc-server-dev webapi]# cat permissions.conf
# The access control origin header that is sent with each request. This is useful if you want to prevent CORS, but remember that it must at least include the server where the AdminPanel is running
accessControlOrigin="*"
# The servers which are allowed to pass the X-Forwarded-For header indicating that they are forwarding a request for a client and are themselves a proxy
allowedProxies=[
    "<IP_ADDRESS>"
]
# Add the IP addresses that are NOT allowed to connect to the Web-API to this list
blacklist=null
# These are the default permissions that a client without a key receives
default {
    # All the valid permissions are listed on the redoc endpoint. You can also use the "*" to grant access to all endpoints. Check GitHub for more information about permissions _EXAMPLE_
    permissions {
        info="*"
    }
    # The rate limit specifies how many operations per second a client with no key can execute
    rateLimit=10
}
# This is an array of keys, defining which keys give access to which endpoints.
keys=[
    {
        # Set to true to enable this permission. Remember to change the key to something secure first
        enabled=false
        # The key can be any token/password, but should probably be randomly generated and 16 or more characters long.
        key=USER
        # The permissions array accepts the same permissions as the default permissions array above.
        permissions {
            cmd {
                "*"=true
            }
            history {
                "*"=true
            }
            info {
                "*"=true
            }
            player {
                "*"=true
            }
            plugins {
                "*"=true
            }
            world {
                "*"=true
            }
        }
        # The number of operations per second that a client with this key can execute
        rateLimit=100
    },
    {
        # Set to true to enable this permission. Remember to change the key to something secure first
        enabled=false
        # The key can be any token/password, but should probably be randomly generated and 16 or more characters long.
        key=ADMIN
        # The permissions array accepts the same permissions as the default permissions array above.
        permissions {
            "*"=true
        }
        # No rate limit or zero = unlimited requests
        rateLimit=0
    }
]
# Set this to true to enable the blacklist, false to turn it off
useBlacklist=false
# Set this to true to enable the whitelist, false to turn it off
useWhitelist=true
# Config file version, used to update correctly
version=5
# Add IP address that are allowed to connect to the Web-API to this list
whitelist=[
    "<IP_ADDRESS>",
    "<IP_ADDRESS>"
]

Did this occur while you were on the "map" page of the AdminPanel?

Sorry for the delay.
This occurs on random pages at random loads/reloads. Will fetch version soon.

So generally all user accounts get a request limit of 10/second, which should be more than enough. You could try adding rateLimit=100 to your users.conf file after the permissions entry.
This wouldn't really fix the problem though, as it shouldn't be happening in the first place...

Any updates on this? Otherwise I would close this issue.


how do i change the background color?

maybe you can add backgroundColor constructor too, for the customization, thankyou :)

Hi,
I added two props for you in the new version 1.3.4
    backgroundColor: {       type: String,       default: "#FFFFFF",     },     iconColor: {       type: String,       default: "#0000008A",     },
I would if you like it, give it a star :)


Uncaught Error: Module did not self-register.

[Enter steps to reproduce:]

...
...

Atom: 1.50.0 x64
Electron: 5.0.13
OS: Unknown macOS version
Thrown From: Atom Core
Stack Trace
Uncaught Error: Module did not self-register.
At electron/js2c/asar.js:138

Error: Module did not self-register.
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:881:18)
    at Object.func [as .node] (electron/js2c/asar.js:147:18)
    at Module.load (internal/modules/cjs/loader.js:701:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:633:12)
    at Function.Module._load (internal/modules/cjs/loader.js:625:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:14:16)
    at customRequire (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:1:695414)
    at get_KeyboardLayoutManager (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2715520)
    at get_manager (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2715622)
    at Object.getCurrentKeyboardLayout (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2715748)
    at e.keystrokeForKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:1047867)
    at KeymapManager.keystrokeForKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1228085)
    at KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1226070)
    at WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:284829)

Commands
  2x -0:56.1.0 core:paste (input.input-text.native-key-bindings)
     -0:53.4.0 core:undo (input.input-text.native-key-bindings)
     -0:35.1.0 core:select-all (input.input-text.native-key-bindings)
  2x -0:34.3.0 editor:consolidate-selections (input.input-text.native-key-bindings)
     -0:30 core:select-all (input.input-text.native-key-bindings)
     -0:29.2.0 core:paste (input.input-text.native-key-bindings)
     -0:18.8.0 core:save (input.hidden-input)
  4x -0:16.3.0 editor:consolidate-selections (input.hidden-input)
     -0:06.0 script:run (input.hidden-input)

Non-Core Packages
script 3.26.0

Thanks for taking the time to contribute!
We noticed that this is a duplicate of #20222. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Add's Zookeeper, Valkey, and ETCD3

I added a few more examples but may be worth breaking into more groupings. For example, HBase is a column oriented store that uses Zookeeper (a key value store) for orchestration.

Looks good! I am planning on organizing it a bit more, once I am done with a few more papers. I will merge this for now. Thanks for contributing and suggestions!


[Portuguese] - keywords "próximo" and "que vem" not interpreted

Hi guys,
first of all, thanks for this wonderfull work that you're doing here.
I'm missing the understanding of the keywords listed above. Here in brazil they're often used.
They express something like "next ..." .
For example : "próximo mês" or  "mês que vem" might be recognized as " next month" , it fits for years, weeks and months the same way.
thk a lot

The same occurs to "semana passada", "mês passado", that express something like "past month", "past week".

Just sent a pull request #199 fixing it.

Some of the rules expected a prefix that wasn't necessary, breaking some use cases. The tests also had the prefix, hiding the issue.
Examples:
next week
semana passada - failed
na semana passada - worked
next month
mês que vem - failed
no mês que vem - worked


Missing CORS Response Header

I want to use your server but can't use it from browers directly as your service does not respond with a CORS-header.
Now I would have to resort to something like cors-anywhere proxy-server which is only really a workaround for the missing header.
The fix would be to just return a Access-Control-Allow-Origin: * header.
This should be possible via a @CrossOrigin(origins = "*", allowedHeaders = "*") annotation in Spring (i guess, I have no experience with it).

Almost the same problem here, i can accesss ferien-api.de via the browser.
My little webapplication unfortunately can't due to CORS Restrictions.
Chrome Error Message is:
"Access to XMLHttpRequest at 'https://ferien-api.de/api/v1/holidays/BE/2021' from origin 'http://<IP_ADDRESS>:4200' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

Is someone working on this already? I could try to make a PR but have no to little experience with Kotlin.

This is only my personal opinion, but CORS only matters if you'd use ferien-api directly in the frontend. I'd always proxy the API in my backend system and most importantly cache it heavily, since the data is fairly static. This way the (possibly thousand) users of my application would result in just a singular request per day.
I don't think the ferien-api server could not handle the full load, it would just feel wasteful to me, and I'd consider this better etiquette.

I don't agree with you fully. Why should I take the effort to set up a proxy or my backend, when my Angular HTTP lib can cache and handle it directly? In our case it makes sense to use it directly in the frontend.

@muuvmuuv Not knowing your use case I cannot say, if that's appropriate or not. I've build applications intended to be only use by me in my home, and apps used by a team of 50 daily. In the first case the proxied use clearly is more effort than it might be worth, but in the second it could already be reasonably worth it.

I would really need it too. Go for it @muuvmuuv :)

@paulbrejla does not work yet :( If i call: https://ferien-api.de/api/v1/holidays/BY/2021
reponse is Access to XMLHttpRequest at 'https://ferien-api.de/api/v1/holidays/BY/2022' from origin 'http://<IP_ADDRESS>:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

@maxleistner it is not released yet I'll push the latest release asap.

@maxleistner can you verify against https://preview.ferien-api.de/api/v1/holidays?

@paulbrejla the header is not sent. Therefore there is still a CORS error. short: not working :)

The cors header is sent back on this request:
curl -v --request GET  'https://preview.ferien-api.de/api/v1/holidays' --header 'Origin: http://localhost' --header 'Access-Control-Request-Method: GET'

Response:
< HTTP/2 200
< date: Wed, 14 Sep 2022 17:21:24 GMT
< content-type: application/json
< vary: Origin,Access-Control-Request-Method,Access-Control-Request-Headers
< access-control-allow-origin: *

Are you sure that you are sending the proper headers?


Create Bulk File job to Validate File Generation

Requirements

Create Bulk File Process to ensure that all files have been generated.
Job will run after current generation process.
Notification process when there is an error in the number of files being generated.
Potentially one of the quartz maintenance jobs

Need to define requirements for Emissions, Allowance, and Compliance
Emissions:
-Run a query to ensure all states/files have been generated and the correct # of files have been generated.
Allowance:
Compliance:

Moved till after May Beta

Moved till after May Beta

Is this necessary anymore or is there a better way to confirm this? The goal is to ensure that all bulk files are generated correctly after their initial creation (does not need to track each update but there should be a way to know if an updating job failed).

Moved to new tickets to discuss- Would addressing this help with tickets like #6219


Use fetch package.json for deps from node_modules.

Hi,
That is an attempt to resolve deps package.json from local filesystem. It uses read-installed, which is library used for "npm ls" command.

do not try to guess package link, it can be very misleading
use read-installed to get package.json for all installed dependencies
remove semver validation, because read-installed handles it

Need to take a deeper look at this. Will take of this next weekend.
npm is update to date with previous PR

Had a look, all and all I like it since it makes for less code, however, my use case still requires me to be able to operate in an environment where just the package.json file exists and nothing else.
Maybe we can do two seperate implementation with a single interface (registry vs local disk) ?

Hi, it doesn't look like we concluded our discussion about operating using a package.json and nothing else. Any thoughts on that?


Pricing missing for Cloufflare Images 'Resizing' and 'Polish' add-ons

Which Cloudflare product(s) does this pertain to?
Images
Subject Matter
pricing is missing
Content Location
there's no providing for CLoudflare images Resizing or Polish
https://developers.cloudflare.com/images/pricing/
https://developers.cloudflare.com/images/image-resizing/
https://developers.cloudflare.com/images/polish/activate-polish/
Additional information
For years I've had a hard time getting pricing from Cloudflare. even talking to someone on live chat it was just impossible. This has gotta be hurting your sales cycle! I just don't get it.

For example, you can read here how other visitors complain that Resizing pricing is "opaque." I confer!
https://community.cloudflare.com/t/webp-images/511638/6

Hi @Maxhodges, thanks for opening the issue and sharing the confusion around pricing.
There are some changes coming soon to Images that I think might help. There's a blog post titled Image optimization made simpler and more predictable: we’re merging Cloudflare Images and Image Resizing that I think you might find helpful about some upcoming changes to the pricing, and the docs will definitely be updated to reflect the changes mentioned.


Remove trailing whitespace

Close #1433

trailing whitespace的检查和注释中的空格会产生冲突。目前没有较好的解决方式。

Why do we need end-of-line spaces in comments?

Why do we need end-of-line spaces in comments?

My mistake.  We don't need end-of-line spaces.


Multiple frontend logger design

Check safe parallel recovery
Truncate all frontend loggers
GetmaxflushID from all frontend loggers
Test with checkpoints
Test with same table updates in multiple psqls


Section on the PID Mint and possible PID services

Luis, please check if you have pulled the current version. The documentation was restructured quite a lot after the Brugges meeting and for example the dmc folder is no longer there... It's hard to merge your commits to main branch then...

Yes please. Currently I see it in your branch under dmc folder. Which is not existing in the main branch now. In the architecture design there is currently no standalone component called Persistent Identifier Mint. In fact it is missing, but I will add it to the Harvester component (now you can see a chapter on Persistence identification there see).

I moved the file to the technical_components folder. The definition of PID currently in the Hasvester document is not canonical.