The Windows SDK version 10.0.14393.0 was not found.

I'm trying to build "SimpleMSAA_PC12" project but it doesn't work with any of my installed SDKs (10.0.19041.0, 10.0.18362.0, and 10.016299.0). From the looks of it (see image), VS installer doesn't have any options to install SDKs older than 10.016299.0, is there any way to install 10.0.14393.0 SDK? Is there any workaround to use later SDKs with the project?

You can upgrade the project to a newer Windows SDK and toolset.

Thanks Chuck. Retargeting the solution solved the issue.
I was only retargeting the project so that was probably what went wrong with my previous attempts.


Cryptographic review

Find reviewers, start review process

#320 and #321 should be mentioned in this context

Here's a review: https://blog.filippo.io/restic-cryptography/

Closing this. It'd be great with more technical reviews of restic and it's security, etc, but there's little point in having a five year old issue about it open :)


WIP - Porting service files from typescript to golang

Things to keep in mind:

Please only check the services/ directory porting from golang to typescript I have done so far (I still to need make more progress on network_context.ts)
This PR is only for reviewal reasons
I have made a bunch of TODO comments in service_context.ts to explain my thought-process, design decisions, or questions that I have (feel free to read them over if you want to read my thoughts)

Also, I changed package.json and package-lock.json since I uninstalled grpc-tools from my local repository, since I already have it installed globally

Project dependencies needed locally on the package.json:

npm install google-protobuf
npm install grpc


Add onServerResponseData to webRequest

Would there be any scope for adding an api for looking at server response data?
Something like:
session.webRequest.onServerResponseData(filter, (data, done) => {
  checkData(data);
  return done(data);
});

or perhaps a stream?
session.webRequest.onServerResponseData(filter, (istream, ostream) => {
  istream.pipe(spyStream).pipe(ostream);
});

cheers

The API provided by Chromium only allows us to modify the headers, if we want to add this API we need Chromium to provide related interface first. You can probably suggest adding this API to chrome.webRequest in Chromium's issues list, once it is added there we can port it to Electron.
Or you can just use the protocol module to try to similar things.


Excessive API polling?

Hello, looking at the log, I see hundreds of 429 errors per day.
poloLender is the only program I use on this IP address (and poloniex account) which accesses the poloniex API.
Here is a section of the log:
2017-07-30 19:08:29: notice: returnAvailableAccountBalances: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:29: notice: returnAvailableAccountBalances: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:30: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:30: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:30: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:34: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:34: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:34: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:34: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.
2017-07-30 19:08:54: notice: returnActiveLoans: Poloniex error 429: Too Many Requests. Please do not make more than 8 API calls per second.

Thanks.

@kevinlekiller,  it looks like Poloniex is fiddling again with their API call limits.
poloLender is trying to adhere strictly to the 8 API calls  per second limits, but it shows Poloniex is not adhering to own rules.
(On the positive note we have also seen that Poloniex API response times have been reduced drastically since a couple of days).
You can ignore the notice, as the app is handeling the "notice" correctly, or
to slow down the bot you can you can change the maxApiCallsPerDuration in your config file  to 7.

Thanks, will set it to 7.

poloniex isn't adhering to the it's 8 API calls per second limit.  It is very annoying and unethical.


Run Mutect WDL as part of Travis build

Just like we do for ACNV.

Blocked until the next version of cromwell.

mutect2-replicate-validation.wdl
mutect2_multi_sample.wdl
mutect2.wdl

And the corresponding templates should be used for each.

If this is complete, please close issue #915

Waiting on #916

If this is complete, please close issue #915 (shouldn't be needed if this one addresses mutect2-replicate-validation.wdl).

@LeeTL1220 does this affect me or Takuto or was it a note to self?

Closed by #949.


Add look-ahead optimization to VM

Changes

Add look-ahead optimization to VM

Codecov Report

Merging #233 (3972dfc) into main (d280719) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              main      #233     +/-   ##
===========================================
  Coverage   100.00%   100.00%
===========================================
  Files           54         1     -53
  Lines         1819        65   -1754
  Branches       110        29     -81
===========================================
- Hits          1819        65   -1754

Impacted Files
Coverage Δ

...la/codes/quine/labo/recheck/fuzz/FuzzChecker.scala

.../main/scala/codes/quine/labo/recheck/vm/Inst.scala

...cala/codes/quine/labo/recheck/vm/Interpreter.scala

...a/codes/quine/labo/recheck/vm/ProgramBuilder.scala

...main/scala/codes/quine/labo/recheck/cli/Main.scala

...rc/main/scala/codes/quine/labo/recheck/ReDoS.scala

...in/scala/codes/quine/labo/recheck/data/Graph.scala

...ala/codes/quine/labo/recheck/unicode/UString.scala

...ala/codes/quine/labo/recheck/util/RepeatUtil.scala

...s/quine/labo/recheck/automaton/EpsNFABuilder.scala

... and 43 more

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 d280719...3972dfc. Read the comment docs.


fix cves in v1.16.0-tetrate-v5

Fix following CVEs in master

Severity
Image
Exploitable
CVE
Package
Fix

HIGH
kubegres:v1.16.0-t
Unknown
PRISMA-2022-0227
github.com/emicklei/go-restful/v3
v3.9.0 -> v3.10.0

HIGH
kubegres:v1.16.0-t
Unknown
CVE-2023-44487
golang.org/x/net
v0.13.0 -> v0.17.0

HIGH
kubegres:v1.16.0-t
Unknown
CVE-2023-39325
golang.org/x/net/http2
v0.13.0 -> v0.17.0

We can create a new tag once this is merged.

If I'm not wrong, the latest image that we are using v1.16.0-tetrate-v5 is based on the https://github.com/tetrateio/kubegres/tree/release-v1.16.x branch. So this fix should likely point to that branch. cc @sergicastro

Thanks you for pointing out. Opened another  PR to fix cve in kubegres image used by TSB. We can  merge this as well to fix the cves in master?

We can merge this as well to fix the cves in master?

I think that master is just mirroring the upstream open-source project (https://github.com/reactive-tech/kubegres) and then we are back-porting fixes to the version that we are using in TSB in our private branch. The best would be to move this PR to the open source repo, just like we did in the past: first fixing our image internally and then fixing upstream https://github.com/reactive-tech/kubegres/pull/159

Yes, as @M4tteoP says these same fixes need to be done on the Kubegres repo and then update the dependency in the  monorepo, I will take care of that.

Sorry, I really missed the context, though I was looking into a different repo.
Yes, as @M4tteoP says, we'd like to not adding commits on the main branch on this repo that are not coming from upstream.
So I'll close this one.

Opened PR upstream, see:

https://github.com/reactive-tech/kubegres/issues/181
https://github.com/reactive-tech/kubegres/pull/182


In PredictService, allow handling data as a 1d array instead of 2d

When working with text, scikit-learn and others will sometimes expect the
input to be a 1d array of strings rather than a 2d array.  Setting the
new unwrap_sample to true will use this representation.

Coverage remained the same at 100.0% when pulling 059ef5f29c4208056b0c8d847b0d20806c66fb50 on feature/predict-service-unwrap-for-text into 190982726a18800747d09dccef34d100eb6b10de on develop.

Coverage remained the same at 100.0% when pulling 059ef5f29c4208056b0c8d847b0d20806c66fb50 on feature/predict-service-unwrap-for-text into 190982726a18800747d09dccef34d100eb6b10de on develop.


[Feature-14421][K8S Task] Configurable image pull policy

Purpose of the pull request

This PR closes https://github.com/apache/dolphinscheduler/issues/14421

Brief change log

Support to select image pull policy from IfNotPresent, Always, Never.

Verify this pull request

Can we add a new constant IfNotPresent here and return a select list from API replace defined this in the UI module?

Hi, @qingwli , thanks for your comment. I think image pull policies are relative static options, and it's still possible that user define a k8s task with wrong image pull policy by openAPI. In addition, we have already defined many option list in front-end codes, maybe for simplicity. Thus, considering interaction through UI page, do we have to make this change?

I agree with you @Radeity


Use your own wrapper function for register

You could do this before:
$book = new Cuztom_Post_Type('book')
After some strange bugs, I discovered this gave some problems, so now you need to do this:
function cuztom_content_types() {
    $book = new Cuztom_Post_Type('book');
}
add_action('init', 'cuztom_content_types');

Some of you already did this, that's no problem. Just keep using the new method :)

in which case you have the problem ? and ... what type of problem ? ...
i would understand in which case i have to use an action to register a new CPT ... :-)
thx

This isn't really a bug, it needs to be added to the wiki (see ticket label). You always need to wrap your own Cuztom code (registering stuff) within a add_action('init', ... )

i found out that this is the problem you can't use $post->ID to add into a default_value because init hook happens before anything. Maybe if the metaboxes could be added outside the init hook then we could access the $post->ID

Added to the docs


ISPN-12191 Remove GSON

https://issues.redhat.com/browse/ISPN-12191

Failures unrelated

Thanks @gustavonalle


GD-491: segmentation fault when closing godot editor

The used GdUnit4 version
4.3.1 (Latest Release)
The used Godot version
v4.2.2.stable.arch_linux
Operating System
Manjaro Linux
Describe the bug
We are using GdUnit in our build pipeline and after updating to GdUnit 4.3.0, the godot editor does not exit properly when closing the editor.
This is proplematic because we are checking for the exit status of the godot process during the build. We expirienced the same behaviour when using GdUnit 4.3.1
Steps to Reproduce
I was able to reproduce the error without the command line tools in a clean project.

Start godot via command line with godot . -e
Created a new project in Godot 4.2.2
Added gdUnit Plugin 4.3.1 and activate it under Project Settings -> Plugins
Close project

=> The terminal is showing "Unload GdUnit4 Plugin success", but it also shows a segmentation fault and the process exits with error code 139 and following console output is shown.

Loading GdUnit4 Plugin success
GdUnit4: Test server successfully started checked port: 31002
ERROR: Parent node is busy adding/removing children, remove_child() can't be called at this time. Consider using remove_child.call_deferred(child) instead.
at: remove_child (scene/main/node.cpp:1449)
ERROR: Condition "data.parent" is true.
at: ~Node (scene/main/node.cpp:3583)
ERROR: Parent node is busy adding/removing children, remove_child() can't be called at this time. Consider using remove_child.call_deferred(child) instead.
at: remove_child (scene/main/node.cpp:1449)
ERROR: Condition "data.parent" is true.
at: ~Node (scene/main/node.cpp:3583)
Unload GdUnit4 Plugin success
zsh: segmentation fault (core dumped)  godot . -e

When disabling the plugin and closing the project, no error gets shown.
Minimal reproduction project
No response

https://github.com/godotengine/godot/issues/92727

@Krigu can you please check out the master and verify if it's working as expected now?

@Krigu can you please check out the master and verify if it's working as expected now? I have no Linux system to can test direct, but from the GitHub action it runs without crash.

@MikeSchulze Sorry for the late response, I was offline for a couple days.
I checked with the current master on my machine (Linux Manjaro) and everything seems to work as expected now. Thanks for fixing it so quickly!


Missing Illuminate\Contracts\Events\ShouldDispatchAfterCommit Interface

Laravel Version
10.27.0
PHP Version
8.1.21
Database Driver & Version
No response
Description
Expected Behavior:
The Illuminate\Contracts\Events\ShouldDispatchAfterCommit interface should be present and accessible in Laravel 10.x, as stated in the documentation.
Actual Behavior:
The Illuminate\Contracts\Events\ShouldDispatchAfterCommit interface seems to be missing from the Laravel 10.x codebase.
Steps To Reproduce
Navigate to the Laravel 10.x docs for Broadcasting
Observe the mention of Illuminate\Contracts\Events\ShouldDispatchAfterCommit as an available interface.
Expected Behavior:

The interface was added in 10.30.0 https://github.com/laravel/framework/commit/0525a8819db53bc66c878413829a4368d63c3d47


DocumentViewer PDF.js

How to update PDF.js?
Digital signatures do not show on the document.
Can someone help me?

Duplicate of https://github.com/primefaces-extensions/primefaces-extensions/issues/122
I don't think PDF.js supports signatures.  See this Stack Overflow if you need signature support: https://stackoverflow.com/a/61366654/502366
And this open PDF.js ticket: https://github.com/mozilla/pdf.js/issues/1076


Non-private methods detected

Hi everyone, I followed most of what was in the PA2 walkthrough, but I still got the error in the title. Has anyone encountered it and how did you fix it? (I tried to make most of the constructors and methods private, but still...)

Which are your public methods, if i may ask?

Which are your public methods, if i may ask?
I will consider all public methods and methods with no access modifiers.
In StateM, they are get, put, unit, toString, accept, flatMap.
In FuncStat, they are toString, in, out (implementations of in and out are in the video).

i had something like this too! maybe can check ur constructors, mine was because of that

i had something like this too! maybe can check ur constructors, mine was because of that

For StateM and FuncStat, each of these I believe that there must exist a constructor that cannot be declared private, as I follow the walkthrough closely.

what about the nothing class, the constructor should be private there if there is any.

what about the nothing class, the constructor should be private there if there is any.

I even did not declare any fields or constructors there...

Then should be ur StateM constructors? Are they private? As StateM does not need any public constructor only 3 static methods, toString and flatMap.

Then should be ur StateM constructors? Are they private? As StateM does not need any public constructor only 3 static methods, toString and flatMap.

But I should get what I want since I followed the walkthrough closely and the head TA did not declare the two constructors private there. The question does not ask us to declare the constructors private (only the helper methods).

Ok... For me, the only difference I can see between my code and your code is the constructors being not private. But, did you overwrite accept in StateM? If you did, maybe that is the reason.

Ok... For me, the only difference I can see between my code and your code is the constructors being not private. But, did you overwrite accept in StateM? If you did, maybe that is the reason.

Oh yes, I managed to solve it. I should have not override the accept method (which has already been in AbstractStateM), so that is the only method that I need to delete or change. Thank you very much!


Yeta Wrench particle effects

Description
Blocks broken by Yeta Wrench now have particle effects. Also removed redundant code.

Checklist:

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you).
[x] I have performed a self-review of my own code.
[x] I have commented my code in areas it may be challenging to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes are ready for review from a contributor.

Looks good to me, thanks!


Expose Terminal information outside module

A few changes to allow using the Terminal object from outside the SwiftTerm module.
You can read the following:

CharData for a given row and column
whether terminal is in application cursor mode or not
cursor location relative to visible screen
top visible row to help handle scrolling

Brilliant!   Thank you!
This aligns beautifully with this: https://github.com/migueldeicaza/SwiftTerm/issues/93


Support link detection for in notebook error output

@nfx commented on Sat Feb 27 2021
Issue Type: Bug

Let's imagine some hypothetical bad code that resulted in exception either because bad or unfamiliar third-party libraries and focus on speed of issue resolution:
import pandas as pd
pd.DataFrame(42)

Upon executing this, we get an exception. As professional IDE user, I expect a consistent behavior and exception stack trace rendered like a normal stack trace - something compact, with clickable lines, that get me to correct lines of code, causing the error. I do not want to open search bar in the project, then figure out that this is not the error in the project i'm working on, but rather in third-party dependency, because that way i have to go, figure out where the sources of that dependency are, open another editor, find references, etc etc. I also really don't want to see the same exception message for 3 times. Practically speaking, we can make hiding of stack traces as opt-out feature. If make with bottom-right notifications popup - even better :)
VSCode has a nice stack trace rendering widget in debug mode, so that one could be just re-used in this beautiful extension, so that I'd see consistent UX across different parts of the editor for the same type of things.
...
Extension version: 2021.3.600686576
VS Code version: Code - Insiders 1.54.0-insider (Universal) (e590188f17162393f50feec19263398e6fe02d13, 2021-02-26T20:39:12.763Z)
OS version: Darwin x64 19.6.0

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30263608
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30244315
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt875:30259475
pythonvspyt639:30264824
pythontb:30258533

@nfx commented on Sat Feb 27 2021
Must be part of microsoft/vscode#91987

@joyceerhl commented on Sat Feb 27 2021
Thanks for the feedback @nfx. Possible dupe of https://github.com/microsoft/vscode-jupyter/issues/4589

@nfx commented on Sun Feb 28 2021
@joyceerhl this one has more details 😜

@rebornix We get link detection in terminals today for Python stack traces in terminal outputs (handle by VSCode core). Hence I believe it can be done in core as well.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

Let's track it in https://github.com/microsoft/vscode-jupyter/issues/12285


Duckdns is not working any more for me

I have been running DuckDNS for a while, and it has been working fine.  However, recently, I upgraded from RPi3 to Ubuntu 18.04.  I restored from a snapshot, and everything is working fine except this.  I have uninstalled and reinstalled both DuckDNS and LetsEncrypt.  No joy.  Basically, it looks like I am having some sort of resolution problem  One more piece of the puzzle; I am running Pihole.  However, from the CLI of my server, I can resolve the domain in question just fine.  Any, here is the error I am getting from LetsEncrypt:
starting version 3.2.4
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
An unexpected error occurred:
ConnectionError: HTTPSConnectionPool(host='acme-v01.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f0da0d78550>: Failed to establish a new connection: [Errno -3] Try again',))
Please see the logfiles in /var/log/letsencrypt for more details.
Here is the error I am getting from DuckDNS:
starting version 3.2.4
INFO: Using main config file /data/workdir/config
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 6)
As I said, from the CLI, I can resolve acme-V0#.api.letsencrypt.org just fine.  Suggestions?

Fix with last version?


[mtl] hotfix for the buffer alignment

follow-up to #2340
PR checklist:

[ ] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:
[ ] rustfmt run on changed code

screwed up a bit...
bors r+


Use @ or % or ? or ('') after setting for something

Need this kind of syntax, if we have:
api('user/create', { query: 1 })
how to model that with weblang?
@api?user/create:
  query: 1

Use
=result@api:
  path: user/create
  params:
    query: 1


[BUG] Sub-fields naming collision

What is the bug?
For example, if a log line contains two sub-fields that have the same name, direct query would ignore the top level fields and think both fields are duplicated. For example, the sql query below will return one field ip, with the top level fields stripped. The PPL query won't return any results and won't raise errors either.
SELECT
     src_endpoint.ip,
     dst_endpoint.ip
FROM
securitylake.amazon_security_lake_glue_db_us_east_1.amazon_security_lake_table_us_east_1_vpc_flow_2_0
WHERE time_dt BETWEEN CURRENT_TIMESTAMP - INTERVAL '1' DAY AND CURRENT_TIMESTAMP
LIMIT 10

source = securitylake.amazon_security_lake_glue_db_us_east_1.amazon_security_lake_table_us_east_1_vpc_flow_2_0
| where time_dt > '2024-07-31 00:00:00 ' and region = 'us-east-1'
| fields src_endpoint.ip
| head 10

How can one reproduce the bug?
Steps to reproduce the behavior:

Go to Data sources -> securitylake -> query data -> open log explorer
Run the follow queries:

SELECT
     src_endpoint.ip,
     dst_endpoint.ip
FROM
securitylake.amazon_security_lake_glue_db_us_east_1.amazon_security_lake_table_us_east_1_vpc_flow_2_0
WHERE time_dt BETWEEN CURRENT_TIMESTAMP - INTERVAL '1' DAY AND CURRENT_TIMESTAMP
LIMIT 10

source = securitylake.amazon_security_lake_glue_db_us_east_1.amazon_security_lake_table_us_east_1_vpc_flow_2_0
| where time_dt > '2024-07-31 00:00:00 ' and region = 'us-east-1'
| fields src_endpoint.ip
| head 10

See returned results

What is the expected behavior?
Both fields are returned properly without the top fields stripped.
What is your host/environment?

OS: [e.g. iOS]
Version 2.13
Plugins

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

Related issue: https://github.com/opensearch-project/observability/issues/1854


Only one node from pointer must be decoded.

We always know if we want to go left or right branch of binary tree.
There is no need to decode both pointers every time.

Decoding only 1 pointer bumped speed from 81 to 89/s.
Exactly as I was expecting. The bottleneck is still lack of low level integer unpacking API.
I don't think code complication (switching between pointer space bytes decoding and bytes skipping depending on direction) is justified by such low boost.


Failures for skull-stripping heuristic

Tracking issue for failures in the skull-stripping heuristic.

ds000110 - sub-27

Reported in https://github.com/nipreps/fmriprep/issues/2318#issuecomment-723308541


New service tags section in troubleshooting article

Docs Build status updates of commit 2dab68f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Abstract storage API to access local fs storage

Have an abstract layer to interact with the filesystem used in EncryptedFs. This helps us with having several implementations for desktop, wasm, mobile which handles the particularities on each platform.
Abstractization layer for API similar to https://doc.rust-lang.org/std/fs/struct.File.html , https://doc.rust-lang.org/stable/std/fs/ and https://doc.rust-lang.org/stable/std/io/ and implementation that uses the above ones for accessing local FS. Use that impl in EncryptedFs struct and crypto modules to access FS.
Structure of crypto module
crypto::storage::fs::OpenOptions
crypto::storage::fs::File
crypto::storage::fs
crypto::storage::io
crypto::storage::path::Path](https://doc.rust-lang.org/stable/std/path/struct.Path.html) this is because in exists method it uses local fs
crypto::storage::path::PathBuf this is because in exists method it uses local fs
We will have smth similar to how this is atomic Write to a File https://crates.io/crates/atomic-write-file
Flow is like this
lib-users > crypto::[fs, fs::OpenOptions, fs::File, io] > EncryptedFs -> crypto::storage::[fs, fs::OpenOptions, fs::File, io]

This issue corresponds to encrypted_storage::[fs, fs::File, io].

https://github.com/radumarias/rencfs/issues/97

@someotherself any progress on this?


${json-encode} support for rawValue

Fixes #2856
todo

[ ] xml-encode

What is the difference between this and ${event-properties:prop_key:format=@} ?

Remember that I have now restricted RawValue to only be primitive types, and not full objects.

yes, that is indeed an issue with the original idea after this.

${event-properties:prop_key:format=@}

good one. Haven't think of that

What is the difference between this and ${event-properties:prop_key:format=@} ?

after some thinking:

'@' won't work for XML
this should also work for GDC etc (but not now because of the change of IRawValue there)
This is needed to serialize ${exception} to JSON?

'@' won't work for XML

Nope it is a special format-option from the message-template-world.

this should also work for GDC

GdcLayoutRenderer also has support for the Format-parameter = '@'

This is needed to serialize ${exception} to JSON?

ExceptionLayoutRenderer also has support for the Format-parameter = '@'

close in favor of the current option (@ format)


Refactor page JS inclusion via Wagtail hooks

This changes the inclusion of page/streamfield media object into the jinja2 context. It just pulls the code from the CFGOVPage and puts it into a handler class for cleaner code.
Additions

Handler and JSHandler classes

Changes

Move JS handling logic into JSHandler class from CFGOVPage

Testing

tox

Review

@chosak
@Scotchester
@cfpb/cfgov-backends

TODO

Add tests for JSHandler.set_block_js method.

Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[x] Passes all existing automated tests
[x] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Generally, I like this approach. One question, though. What if there are other types of Wagtail blocks that are not defined under the v1.atomic_elements tree? For example, jobmanager has some of these now, and other apps may follow the same pattern of putting app-specific blocks outside of v1. Won't that cause problems with this line and this line if they have their own custom JS to be included?

@chosak thanks for all your helpful comments.

What if there are other types of Wagtail blocks that are not defined under the v1.atomic_elements tree?

This could probably be refactored to include those cases. I'll make some updates for this and the rest of the comments here.

@kurtrwall What is the status of this PR now that #2411 has been merged?

I'm currently catching this one up. Now that I have you though, I'm wondering what your thoughts are for the comment @chosak made just above.
I'm working on and enum class that should be updated for any JS that should be included. Here's an example:
class JSEnum:
    atoms     = []
    blocks    = []
    molecules = []
    organisms = [
        'BaseExpandable',
        'Expandable',
        'ExpandableGroup',
        'FilterControls',
    ]

I'm going to close this pull request for now, in light of the recent Wagtail upgrade PR. There might be other, easier ways to do this in the new version.


TypeScript Support

This adds partial TypeScript support and TSDoc to Lightning SDK. The focus areas of these types are as follows

Router plugin
Image plugin
Utils plugin
Platform settings
Typing for the Lightning export is available in PR rdkcentral/Lightning#407
Any untyped areas have been stubbed with any

No runtime code files (.js / .mjs) are modified or added in this PR
Automated Testing

See rdkcentral/Lightning#407

API Docs + Generation

See rdkcentral/Lightning#407

Still to-do in this PR

[x] Wait for release of rdkcentral/Lightning#407 and set the minimum version of the Lightning Core dependecy to that version.

Still to do in future PRs

See rdkcentral/Lightning#407

Updated with minimum dependency of version 2.7.0 of Core


lcov reporter crashes when a js file is changed and rerun during coverage with es2015 and stage-1 presets

See https://github.com/istanbuljs/nyc/issues/425 for more detail on what actually happens.
For some reason I've only been able to reproduce with babel-preset-es2015 and babel-preset-stage-1 active in my .babelrc.
Minimum repro repository: https://github.com/jedwards1211/istanbul-lcov-issue
git clone git@github.com:jedwards1211/istanbul-lcov-issue
cd istanbul-lcov-issue
npm install
npm test

This is an intermittent issue, possibly just due to ipc timing in this test, which I'm seeing about 80% of the time, so rerun npm test a few times if you don't see it.
Here's what the bug occuring looks like:
$ npm test

> istanbul-lcov-issue@ test /Users/andy/istanbul-lcov-issue
> NODE_ENV=coverage nyc --reporter=lcov --reporter=text mocha ./test/index.js

  lcov reporter
{ hello: 'world' }
{ hello: 'world' }
{ hello: 'world' }
    ✓ works for file that changes during test (4303ms)

  1 passing (4s)

/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-reports/lib/lcovonly/index.js:32
        writer.println('FN:' + [meta.decl.start.line, meta.name].join(','));
                                    ^

TypeError: Cannot read property 'decl' of undefined
    at /Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-reports/lib/lcovonly/index.js:32:37
    at Array.forEach (native)
    at LcovOnlyReport.onDetail (/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-reports/lib/lcovonly/index.js:30:28)
    at LcovReport.(anonymous function) [as onDetail] (/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-reports/lib/lcov/index.js:21:24)
    at Visitor.(anonymous function) [as onDetail] (/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-lib-report/lib/tree.js:34:30)
    at ReportNode.Node.visit (/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-lib-report/lib/tree.js:123:17)
    at /Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-lib-report/lib/tree.js:116:23
    at Array.forEach (native)
    at visitChildren (/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-lib-report/lib/tree.js:115:32)
    at ReportNode.Node.visit (/Users/andy/istanbul-lcov-issue/node_modules/nyc/node_modules/istanbul-lib-report/lib/tree.js:126:5)
npm ERR! Test failed.  See above for more details.

I'm seeing the same issue with the lcov report.  You can see here (scroll to bottom).
The html report also has a few files that have a similar Error as their content rather than the actual file contents:

@bcoe Is this an issue with the reporter(s) or are invalid .json coverage files being generated (due to the file contents changing) that are then being read by the reporter?
I know in our case, we have the same runtime files loaded on the server and then also in phantomjs after going through a module bundler.  We're not using sourcemaps, so I didn't expect things to work, but gave it a try anyways.  Initially it looked like things worked and the line hits in all the files that actually produce reports look correct.  What's confusing is why most are fine, but some aren't.

@mlrawlings are you using babel-plugin-istanbul?  If so I wouldn't expect there to be a problem, because the line numbers, function indexes, etc. generated by istanbul are based upon the source, not the transpiled code.

@jedwards1211 The code is definitely getting modified before going to istanbul, which is why I didn't expect it to work, but it does... for most of the files.

@mlrawlings Okay, well if it's possible to use babel, it would probably work for you.  I have a project with some modules that get run on the server with babel-node and on the client via webpack, and I've been able to merge the coverage from the two successfully.

@mlrawlings basically if you can instrument the code before bundling it, it should work.

@jedwards1211 I think I have my issues figured out (it was working in some cases because the line numbers were unchanged and only the first line had a character shift), I have another problem where the bundler is picking up a file based on the browser field in package.json but using the original filename, but that's not nyc/istanbul's fault.
In your case, I'm curious what you expect to happen.  How are you supposed to get accurate coverage of a file that is changing?

@mlrawlings it's definitely questionable whether it's a valid case to support, though perhaps the reporter could at least do something more reasonable than crashing.  On the other hand, it shouldn't be too difficult to merge coverage after adding a new function to a file.  But I probably could have tested hot reloading without adding an additional function or otherwise changing the code structure in the file.


fix ServerSpec flaky test

[X] I've read the CONTRIBUTING guidelines

It turned out that sbt "takes time" to pick-up the completions on user code even if the compilation is successful.
This should solve the flaky test especially on Jenkins.
I tested this modification with more than 100 executions on travis without a single failure.
cc. @eed3si9n

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4427/head
sbt/sbt@01c5779cff1120523d3b03e274e3b5cd73b3a167

zinc
develop
sbt/zinc@c8e1f5335552bae9a7623d92866a233598fad9fc

io
develop
sbt/io@e6529c010c32a93b66f96a027068b7cf160099a0

librarymanagement
develop
sbt/librarymanagement@910151d1939a38d3f5dd178daffb3b1399caf51c

util
develop
sbt/util@cd679591d068c9863919feea4f363070c74f2774

:x: The result is: FAILED
(restart)

the first failed test is sbt.ParseKey so possibly unrelated ...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4427/head
sbt/sbt@01c5779cff1120523d3b03e274e3b5cd73b3a167

zinc
develop
sbt/zinc@c8e1f5335552bae9a7623d92866a233598fad9fc

io
develop
sbt/io@e6529c010c32a93b66f96a027068b7cf160099a0

librarymanagement
develop
sbt/librarymanagement@910151d1939a38d3f5dd178daffb3b1399caf51c

util
develop
sbt/util@cd679591d068c9863919feea4f363070c74f2774

:x: The result is: FAILED
(restart)

[sbt212] [info] - return completions for user classes *** FAILED ***
[sbt212] [info]   java.util.concurrent.TimeoutException: Futures timed out after [90 seconds]
[sbt212] [info]   at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:255)
[sbt212] [info]   at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:259)
[sbt212] [info]   at scala.concurrent.Await$.$anonfun$result$1(package.scala:215)
[sbt212] [info]   at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53)
[sbt212] [info]   at scala.concurrent.Await$.result(package.scala:142)
[sbt212] [info]   at testpkg.TestServer.waitForString(ServerSpec.scala:302)
[sbt212] [info]   at testpkg.ServerSpec.$anonfun$new$27(ServerSpec.scala:136)
[sbt212] [info]   at testpkg.TestServer$.withTestServer(ServerSpec.scala:184)
[sbt212] [info]   at testpkg.TestServer$.$anonfun$withTestServer$1(ServerSpec.scala:161)
[sbt212] [info]   at sbt.io.IO$.withTemporaryDirectory(IO.scala:480)
[sbt212] [info]   ...
[sbt212] [info] ScalaTest
[sbt212] [info] Run completed in 3 minutes, 16 seconds.
[sbt212] [info] Total number of tests run: 9
[sbt212] [info] Suites: completed 1, aborted 0
[sbt212] [info] Tests: succeeded 8, failed 1, canceled 0, ignored 0, pending 0
[sbt212] [info] *** 1 TEST FAILED ***
[sbt212] [error] Failed: Total 9, Failed 1, Errors 0, Passed 8
[sbt212] [error] Failed tests:
[sbt212] [error] 	testpkg.ServerSpec
[sbt212] [error] (sbtProj / Test / test) sbt.TestsFailedException: Tests unsuccessful

This should solve the flaky test especially on Jenkins.

On Travis CI we cache the Ivy cache, so maybe it takes time to revolve things, including the compiler bridge. Unless we can come up with a better way to test this, let's comment the test out for now.

A validation involving this pull request is in progress...

A validation involving this pull request is in progress...

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4427/head
sbt/sbt@9fa24a85d22a2046b13f0e68324034f03c4df470

zinc
develop
sbt/zinc@c8e1f5335552bae9a7623d92866a233598fad9fc

io
develop
sbt/io@e6529c010c32a93b66f96a027068b7cf160099a0

librarymanagement
develop
sbt/librarymanagement@910151d1939a38d3f5dd178daffb3b1399caf51c

util
develop
sbt/util@cd679591d068c9863919feea4f363070c74f2774

:x: The result is: FAILED
(restart)

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/4427/head
sbt/sbt@88077ce328a10650716df5fedc2950faa701023e

zinc
develop
sbt/zinc@c8e1f5335552bae9a7623d92866a233598fad9fc

io
develop
sbt/io@e6529c010c32a93b66f96a027068b7cf160099a0

librarymanagement
develop
sbt/librarymanagement@910151d1939a38d3f5dd178daffb3b1399caf51c

util
develop
sbt/util@cd679591d068c9863919feea4f363070c74f2774

:x: The result is: FAILED
(restart)


[FLINK-30396][table]make alias hint take effect in correlate

What is the purpose of the change
make alias hint take effect in correlate relnode and make hint case insensitive.
Brief change log

in org.apache.flink.table.planner.hint.FlinkHintStrategies, alias hint should support correlate.
org.apache.flink.table.planner.alias.ClearJoinHintWithInvalidPropagationShuttle、org.apache.flink.table.planner.alias.ClearJoinHintWithInvalidPropagationShuttle.ClearOuterJoinHintShuttle and org.apache.flink.table.planner.hint.FlinkHints.CapitalizeJoinHintShuttle should support both correlate and join relnode.
org.apache.flink.table.planner.hint.JoinStrategy#isJoinStrategy should be case insensitive

Verifying this change
This change added tests and can be verified as follows:
Added test org.apache.flink.table.planner.alias.ClearLookupCorrelateHintWithInvalidPropagationShuttleTest that validates that join hint which from outer query block will be cleared.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@lincoln-lil Hi, the ci has finished successfully, please check the pr again when you're free

@godfreyhe hi, could u check this pr again? I've add a new test case to verify the change.

@godfreyhe @lincoln-lil Hi, is there any problem with this pr?

@Mulavar as suggested by @godfreyhe before, more correlate query related test cases need to be added for Correlate node changes, e.g., "select ... from t, lateral table(tableFunc1(f1)) as T(t1)" or "SELECT ... FROM MyTable, UNNEST(MyTable.c) as A (s)" and etc.

@flinkbot run azure

@lincoln-lil @godfreyhe hi, please check the latest commit, I've added UNNEST and LATERAL TABLE cases for the pr.

@Mulavar there's some compilation error need to be fixed first, please take a look.

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@Mulavar  the e2e failure phase "Prepare E2E run" has been fixed by FLINK-30972, you can rebase the code and update this pr

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@Mulavar could you also create a backport pr to release-1.17 branch?


Update tasks/sep/006-X

Similar to the description in https://github.com/ethereum-optimism/superchain-ops/pull/208, this task was previously executed. Then, we decided to install the DeputyGuardianModule on a new 1/1 Safe, so that execution was reverted. This PR modifies the original task to work for this new architecture, and is nearly identical to the version of this task we will use on Mainnet (we will need to update addresses, etc.)
This PR is in draft until https://github.com/ethereum-optimism/superchain-ops/pull/208 is executed, since the postChecks rely on state from that task

Closing. Once https://github.com/ethereum-optimism/superchain-ops/pull/215 is merged, I will open a new PR for this task


Add conditional if else tests

This PR needs: https://github.com/antmicro/yosys/pull/177

moved to https://github.com/antmicro/yosys/pull/182


Add documentation for the implemented methods in csv data preprocessor

Description

Document the methods present in the csv_preprocess.py abiding by the Sphinx Documentation examples

Would like to work on this issue as a GSSOC'21 participant. If you can then please assign it to me.

@Sibasish-Padhy Thank you for your interest. Currently we can assign only one issue per student. We can always find additional issues to contribute to.

@Siddharth1006 Thank you for your interest. Please email us at<EMAIL_ADDRESS>for futher clarification.

Hello, I would like to work on this issue as a GSSOC'21 participant. If you could assign to me.

@acankshajain, thank you for your interest. Currently, we are restricting one issue per student. We will be adding more issues shortly. You can additionally try adding your own issues by referring the generic issues which can be assigned to you.

@Siddharth1006 Could you please join the Slack channel - here. We would like to have an update from you on the progress of the issue.

Is there any progress on this issue , if not please can you assign me this issue ?
I would like to contribute to this issue @Ask149 .
Thanks.


Add deoplete source

Hi, I split deoplete source from racer.
It should be integrated with vim-racer.

Ping.

Thanks @Shougo

Thanks!


Shorten description

Shorten the description even more.
Along the way, removing the reference to GitHub for 2 reasons:

There are also BitBucket, GitLab, Savannah, etc.
The real pearls are often in some very old folders on someone's hard disk, and BHNT might encourage them to cleanup and publish them in the first place.

This is an additional proposal to #224.


Logout function problem + Background image bug?

https://github.com/RetherSzu/valorant-daily-shop/assets/62782800/ad19ecbc-75e9-421b-871f-80e73a34625b
I can't log out with the logout button. And even though I didn't check 'Stay sign in', if I press the logout button and log in with another account, I automatically continue to log in with my old account.

I think the background image behind Outlaw looks weird.

I can't log out with the logout button. And even though I didn't check 'Stay sign in', if I press the logout button and log in with another account, I automatically continue to log in with my old account.

I was wrong.
The app always keep signed in.

Hello @scottjsh
I tried to solve the disconnection problem without success, so I opened an issue on the GitHub repository of the API I use.
Issue: link
and thank you for your feedback

Hello @scottjsh ,
Thank you for your patience. I wanted to follow up on the logout problem. I'm pleased to inform you that the issue has been resolved in the Latest Release of the app.
If you experience any further issues or have additional feedback, please don't hesitate to let me know.
Thank you again for your valuable feedback and support.


Problem integrating this control with google mutant

Hi I was using your control with no problems with tileLayers, but when I started using this plugin:
https://gitlab.com/IvanSanchez/Leaflet.GridLayer.GoogleMutant, and try to load layers generated by that plugin, I get an error:

L.Control.Layers.Minimap.js:290 Uncaught Unknown layer, cannot clone this layer. Leaflet-version: 1.0.3

This is how I use it:

var trafficMutant = L.gridLayer.googleMutant({
			maxZoom: 24,
			type:'roadmap'
		});
trafficMutant.addGoogleLayer('TrafficLayer');
 L.control.layers.minimap({
            'Open street map': tileLayer1,
            'Stamen.Watercolor': tileLayer2,
            'OpenStreetMap.BlackAndWhite': tileLayer3,
            'OpenStreetMap.BlackAndWhite.HOT': tileLayer4,
            'Traffic':trafficMutant // This causes trouble

        }, null, {
            collapsed: true
        }).addTo(this.mymap);

Note the referenced plugin works well if I use standard control for choosing between base and tile layers. Can you help?

Actually I think I fixed this issue, by changing something in your plugin
function cloneLayer (layer) {
    var options = cloneOptions(layer.options);

    // we need to test for the most specific class first, i.e.
    // Circle before CircleMarker

    if(layer instanceof L.GridLayer)
        return L.gridLayer();

But can you make this update so that it is available on NPM?

That line of code is from jieter/leaflet-clonelayer, it should be fixed there.

@jieter Do you have idea how to fix it? Like I said the solution I used above doesn't completely fix it. The minimap of the gogle mutant layer shows a gray area inside the control after I applied that fix.
Yeah strangely the cloneLayer function exists inside this plugin source and also inside clone layer plugin.

@giorgim yes I know how to fix this. The question is, should leaflet-clonelayer support plugins like this?
in this line, leaflet-clonelayer is required, I think you are looking at the built version in L.Control.Layers.Minimap.js.

@jieter OK maybe you can write here how to fix that in that case, I would at least copy locally your plugin and amend the change there. Also could be useful for others if they encounter this page.

Yes, but it would be better if others can use it too. If I show you how to fix it, can you try to open a PR to contribute it to leaflet-clonelayer? I'll make sure it gets released on npm then.
Basically, what you need to do is:

check if L.GridLayer.GoogleMutant is defined (to make sure leaflet-clonelayer still works when not used together with Google Mutant.
check if the layer is a Google Mutant layer: layer instanceof L.GridLayer.GoogleMutant.
return a cloned version of the Google Mutant layer: return L.gridLayer.googleMutant(layer.options);

Even with https://github.com/jieter/leaflet-clonelayer/pull/6#, this still doesn't work perfectly.


Entity is non numeric

Random error message from the Sol-ark sensors.
My setup is RS485 to a USB converter that is plugged right into the HA PC.
This was previously connected to Solar Assistant on a Pi and I have never seen this error on SA.
Seems like data is missing when I zoom up on the graph for the sensor.
Entity is non-numeric: sensor.solark_1_pv_input_power - shows up for a few seconds then disappears again.

Looks like a problem with your polling subsystem to me.  This integration depends on pymodbus as that subsystem.  You might want to discuss it with the maintainer(s) of that package.  I am closing this issue because I think data errors like this are likely outside the scope of this integration.  If you learn otherwise please re-open this issue.


fix: duplicated events when using aws-sdk in a layer

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


unsupported operand type(s) for +: 'datetime.datetime' and 'dict'

Do I need to change anything?
name: test
type: frequency
index: apm-*-transaction-*
exponential_realert:
  hours: 1
num_events: 10
timeframe:
  minutes: 1
summary_table_fields:
  - "@timestamp"
aggregation_key: "service.name"
filter:
- term:
    http.response.status_code: "200"
alert:
- debug
alert_text_type: aggregation_summary_only

2021-01-21 15:10:49,021     INFO        elasticsearch GET http://<IP_ADDRESS>:9200/elastalert_status_test/_search?size=1 [status:200 request:0.004s]
2021-01-21 15:10:49,023    ERROR                 root Traceback (most recent call last):
  File "/usr/local/python36/lib/python3.6/site-packages/elastalert/elastalert.py", line 1269, in handle_rule_execution
    num_matches = self.run_rule(rule, endtime, rule.get('initial_starttime'))
  File "/usr/local/python36/lib/python3.6/site-packages/elastalert/elastalert.py", line 949, in run_rule
    self.add_aggregated_alert(match, rule)
  File "/usr/local/python36/lib/python3.6/site-packages/elastalert/elastalert.py", line 1807, in add_aggregated_alert
    alert_time = ts_now() + rule['aggregation']
TypeError: unsupported operand type(s) for +: 'datetime.datetime' and 'dict'

2021-01-21 15:10:49,023    ERROR                 root Uncaught exception running rule test: unsupported operand type(s) for +: 'datetime.datetime' and 'dict'
2021-01-21 15:10:49,023     INFO           elastalert Skipping writing to ES: {'message': "Uncaught exception running rule test: unsupported operand type(s) for +: 'datetime.datetime' and 'dict'", 'traceback': ['Traceback (most recent call last):', '  File "/usr/local/python36/lib/python3.6/site-packages/elastalert/elastalert.py", line 1269, in handle_rule_execution', "    num_matches = self.run_rule(rule, endtime, rule.get('initial_starttime'))", '  File "/usr/local/python36/lib/python3.6/site-packages/elastalert/elastalert.py", line 949, in run_rule', '    self.add_aggregated_alert(match, rule)', '  File "/usr/local/python36/lib/python3.6/site-packages/elastalert/elastalert.py", line 1807, in add_aggregated_alert', "    alert_time = ts_now() + rule['aggregation']", "TypeError: unsupported operand type(s) for +: 'datetime.datetime' and 'dict'"], 'data': {'rule': 'test'}}

The following pull requests that have not yet been merged may be relevant
https://github.com/Yelp/elastalert/pull/2759

The following pull requests that have not yet been merged may be relevant
https://github.com/Yelp/elastalert/pull/2759

The following pull requests that have not yet been merged may be relevant
#2759
Currently, it is hardly maintained, so it seems unlikely that it will be merged.

Is there no other solution?

The following pull requests that have not yet been merged may be relevant
#2759
Currently, it is hardly maintained, so it seems unlikely that it will be merged.

Is there no other solution?

Do not know

Do not know

No one answers. Search for past issues.

No one answers. Search for past issues.

Few people answer elastalert issues anymore, so if you can't find past issues or do something about yourself, I think you should consider another tool.

Few people answer elastalert issues anymore, so if you can't find past issues or do something about yourself, I think you should consider another tool.

Why don't you look it up yourself when you can find it?
https://github.com/Yelp/elastalert/issues/1727

Why don't you look it up yourself when you can find it?
https://github.com/Yelp/elastalert/issues/1727

Why don't you look it up yourself when you can find it?
#1727

I found this issue, but the problem is different

Why don't you look it up yourself when you can find it?
#1727

I found this issue, but the problem is different

You shouldn't expect support from oss.

You shouldn't expect support from oss.

You shouldn't expect support from oss.

You shouldn't expect support from oss.

When fixing the program
Execute the process where the error occurs only in the case of datetime type
elastalert/elastalert.py
before
alert_time = ts_now() + rule['aggregation']

after
if isinstance(rule['aggregation'], datetime):
   alert_time = ts_now() + rule['aggregation']

When fixing the program
Execute the process where the error occurs only in the case of datetime type
elastalert/elastalert.py
before
alert_time = ts_now() + rule['aggregation']

after
if isinstance(rule['aggregation'], datetime):
   alert_time = ts_now() + rule['aggregation']

elastalert/elastalert.py ・・・elastalert 0.2.4
「alert_time = ts_now() + rule['aggregation']」 is error
if rule.get('aggregate_by_match_time', False):
    match_time = ts_to_dt(lookup_es_key(match, rule['timestamp_field']))
    alert_time = match_time + rule['aggregation']
else:
    alert_time = ts_now() + rule['aggregation']

Specify aggregation
https://elastalert.readthedocs.io/en/latest/ruletypes.html#aggregation
example1
aggregation:
  hours: 2

example2
aggregation:
  schedule: '2 4 * * mon,fri'

elastalert/elastalert.py ・・・elastalert 0.2.4
「alert_time = ts_now() + rule['aggregation']」 is error
if rule.get('aggregate_by_match_time', False):
    match_time = ts_to_dt(lookup_es_key(match, rule['timestamp_field']))
    alert_time = match_time + rule['aggregation']
else:
    alert_time = ts_now() + rule['aggregation']

Specify aggregation
https://elastalert.readthedocs.io/en/latest/ruletypes.html#aggregation
example1
aggregation:
  hours: 2

example2
aggregation:
  schedule: '2 4 * * mon,fri'


RFP - cadzinho

Checklist

[X] The package I am requesting does not already exist on https://community.chocolatey.org/packages;
[X] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[X] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://github.com/zecruel/CadZinho
Direct download URL for the software / installer : https://github.com/zecruel/CadZinho/releases/tag/0.2.0
Software summary / short description: Minimalist computer aided design (CAD) software

Direct download URL for the software / installer : https://github.com/zecruel/CadZinho/releases/download/0.2.0/windows.zip

@laberts Can you add to the original message above?

Checklist
The package I am requesting does not already exist on https://community.chocolatey.org/packages;
There is no open issue for this package;
The issue title starts with 'RFP - ';
The download URL is public and not locked behind a paywall / login;
Package Details
Software project URL : https://github.com/zecruel/CadZinho
Direct download URL for the software / installer : https://github.com/zecruel/CadZinho/releases/download/0.2.0/windows.zip
Software summary / short description: Minimalist computer aided design (CAD) software


[Bug]: Transaction service fails when sending money to Mpesa from KCB bank

Description
No transaction message is received when sending money to self from KCB bank to Mpesa
Steps to reproduce

Open the Stax app.
On the home screen, click on the send money icon.
On the “pay with” input field, select the bank.
On the “recipient network” input field, select Mpesa.
On the “send money to” radio button, select myself, enter the desired amount and click on the continue button.
When prompted with “finish importing account” click the connect now button.
Pay attention to the transaction details page.

Expected result
A confirmation message is received and transaction details are displayed on the screen.
Actual result
A confirmation message is not received nor are the transaction details displayed on the screen.
Link to screenshots/screen recordings
https://drive.google.com/file/d/1eBVSETNaQ3XlOL1uy3h-muacDuxmVtJs/view?usp=sharing
Device name
Nokia 3.2
Android OS
11
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this test?
Safaricom
Stax device ID or email address
ae3a4fb4d6502412

@larrymiami this should be fixed now with release 1.18.2

@johnswekenyi got it, nice work!


FIX Docker compose up not working (#7153)

Motivation and context

I cloned the repository and ran docker-compose up, but the existing application failed to start. I checked the commit history and found that the traefik command was modified. I believe that restoring the original command will fix the issue.
https://github.com/opencv/cvat/commit/6ae1cffdabcd4b3aeae30f07cb1236807c3a2d15
https://github.com/opencv/cvat/issues/7153

How has this been tested?

Ubuntu 20.04.6 LTS

Checklist

[X] I submit my changes into the develop branch
[ ] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[X] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[X] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

This would undo the effect of #7109. I have prepared a proper fix in #7170.

Okay thanks


Typo in docs

[Enter feedback here]
A few spaces missing in this sentence.
Backups
Azure Database for PostgreSQL takes full, differential, and transaction log backup

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

ID: 9664ac97-ad76-df45-3833-c927b098ab95
Version Independent ID: 5f7c02b5-5454-509c-5681-8a4c1cdbb62b
Content: Backup and restore in Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-backup.md
Service: postgresql
GitHub Login: @rachel-msft
Microsoft Alias: raagyema

@rodrigoviola Thanks for reaching out. The un-rendered raw text (which you can access here) shows:

The spaces are there, but may not show as clearly because of the font of the website.

@rachel-msft Thanks for the confirmation.
@rodrigoviola We will be going ahead and closing this issue.

@rachel-msft That's weird. It seems to be a Safari issue, on macOS and iOS. Other browsers display the text correctly.
macOS:

iOS:

@rachel-msft actually @rodrigoviola was right - there were some characters instead of spaces 👀 I created a PR to fix this

Thank you @rodrigoviola and @Potapy4. We appreciate your contributions.


New unrecoverable error?

I was switching from playing with Angels Mods to just the regular game without Angels, but when I loaded up my save for that, this is the error I got.
https://gyazo.com/d1e97e91f33e7ef5f8f9fe5bd160925e
Aside from updating the mod, I only disabled the Angels mods I have. Any ideas what might've caused this?
EDIT: Also not sure how to upload my save if/when you need that, though...

that's a very specific combination of update on an old game. i'll release a fix in a few minutes

thanks for the report
fixed version is up :)

Alright, so that fix helped me get to starting it up. However, when I was trying to re-do some of the monitor (I loaded said base mod without YARM at the time, and I just got back to my computer), I got a new error.
https://gyazo.com/1a37f496bd65f2eb1db2a877e458ba6c
The tags I had from the previous use of YARM were still there, but the actual monitoring was gone; I had no stats in the top-left corner of my screen at all despite having over a dozen sites on this save. So as I was attempting to re-do these site, this error came up at about the 5th or 6th one.
So far this hasn't popped up again on a second attempt, so I guess I must've just accidentally tried to YARM the wrong thing or something.

hmm, definitely something to address, let me look

weird, that points at
    local max_dist = settings.global["YARM-grow-limit"].value
can you share the save pre-migration?


Updated methods and interface

have decided to change to a major release

Coverage decreased (-0.5%) to 98.065% when pulling 6461c6b9f4a722d8b2daba593cbcbc0ff6e617e6 on upd-methods into 2debf77b06d395dcfed7fdc4a8c8bee99c250d19 on dev_v0.1.0.


Need documentation tool for component

Each UI component should have documentation/help.
The UI component document should contain a short description, parameters to pass into, etc

Firedoc looks promissing:
https://github.com/fireball-x/firedoc

on hold


TypeError: element.summernote is not a function

I'm using Yeoman Angular-Fullstack generator, this is my first time using webpack.
This error has given me headaches for a lot of hours:
angular.js:13920TypeError: element.summernote is not a function
It is supposed to appear when the dependencies aren't loaded in the right order. I can't get it to work even with my app.ts looking like this:
var $ = require('jquery');

import 'bootstrap/dist/css/bootstrap.css';
const bootstrap = require('bootstrap');

const codemirror = require("codemirror");

import 'summernote/dist/summernote.css';
const summernote = require('summernote');

const angular = require('angular');
// import ngAnimate from 'angular-animate';
const ngCookies = require('angular-cookies');
const ngResource = require('angular-resource');
const ngSanitize = require('angular-sanitize');

const uiRouter = require('angular-ui-router');
const uiBootstrap = require('angular-ui-bootstrap');

const ngSummernote = require('angular-summernote');

const lodash = require('lodash');`

The answer could be something pretty simple but I'm running out of ideas. Any help would be appreciated

same issue with webpack

I solved it by adding $() to the element before activate is called (also, $ is an alias for jQuery in webpack config).
//Directive in angular-summernote.js

if (!ngModel) {
            transclude(scope, function(clone, scope) {
              // to prevent binding to angular scope (It require `tranclude: 'element'`)
              element.append(clone.html());
            });
              console.log(element);
            summernoteController.activate(scope, $(element), ngModel);
          } else {
            var clearWatch = scope.$watch(function() { return ngModel.$viewValue; }, function(value) {
              clearWatch();
              element.append(value);
                console.log(element);
              summernoteController.activate(scope, $(element), ngModel);
            }, true);
          }

This is my first attemp on using webpack so maybe there's a way of solving it without changing wrapper code.

Does anybody have proper solution, or explanation why it doesn't work ?

I've found solution using the following webpack configuration
webpack.config.js
entry: {
    bundle: [
        'script!jquery/dist/jquery.min.js',
        './app/app.js'
    ]
},

/* some other code */

externals: {
    'jquery': 'jQuery'
},

/* some other code */

plugins: [
    new webpack.ProvidePlugin({
        $: 'jquery',
        jQuery: 'jquery'
    })
],

The problem for us was a missing bower.json file. Adding this file corrected the problem.

{
  "name": "summernote",
  "homepage": "https://github.com/summernote/summernote",
  "version": "0.8.9",
  "main": [
        "./dist/summernote.js",
        "./dist/summernote.css"
  ],
  "_release": "0.8.9",
  "_resolution": {
    "type": "version",
    "tag": "v0.8.9",
    "commit": "55ce8b405ab1ff4fd86ae147af7e74d97fd9d738"
  },
  "_source": "https://github.com/summernote/summernote.git",
  "_target": "~0.8.0",
  "_originalSource": "summernote"
}

Same problem with angular version6.


An incremental way to add new class members

One of the frustrating parts, at least I imagine, of changing the Dart core libraries is that in strong-mode not implementing all interfaces/abstract classes' instance members is considered a build error. Imagine that someone wanted to add the whoop method to List:
abstract class List<T> implements ... {
  /// Returns the best element in the list.
  T whoop();
}

Now, every single class that either implements or extends List has a compile error.
One strategy would be creating a transitional mix-in:
abstract class ListWithWhoop<T> implements List<T> {
  /// Returns the best element in the list.
  T whoop();
}

... and adding it to every List implementation, and once a code-base is entirely "whoop-ified" (and assuming no new implementations of List are added), you can then try to add whoop to List. But wait, that's also an error in some build systems (i.e. Google's Bazel), because you omitted the @override annotation.
... so now you need to add @override to ListWithWhoop, and then cleanup and remove the ListWithWhoop class from the entire code base. I imagine for something like List or Iterable or anything else common with lots of pub packages/third party dependencies this will certainly take some time.
Proposal
Add an optional, @notImplemented (name is terrible, but accepting suggestions) annotation to dart:_internal for the entire purpose of instructing the frontend(s) to ignore this method, and pretend it doesn't even exist. For example, this would be valid, warning/error-free code:
abstract class List<T> implements ... {
  @notImplemented
  T whoop();
}

...

class BetterList<T> implements List<T> {
  // ... every method implemented but whoop() ...
}

An alternative could be to implement a default implementation, i.e. it would compile to:
class BetterList<T> implements List<T> {
  // ... every other method implemented ...
  T whoop() => throw new UnsupportedError('Not implemented');
}

Once all classes that implement List implement whoop, then @notImplemented could be removed, and the implementation added to the base class (if it is abstract/meant to be extended or mixed in)

If I understand this correctly, we want a way to mark an instance member declaration as "auto-implement" so that every class inheriting the member in its interface, but not having an implementation for it yet, would be considered a warning instead of an error (and the error-recovery would add a matching member that throws when used, e.g., an UnimplementedError).
I can see the lure. It's not something you want to have around forever, but then, you should probably opt in to the feature to begin with (if you don't, it's still an error).
It's an interesting transition strategy. It allows part of an Opt-in, Opt-out, Mandatory transition chain (where Opt-in means implementing the member, Opt-out is when you remove the annotation and means you do have to explicitly implement the member to throw, and Mandatory just means that everybody else thinks you're broken if you don't implement it).

A @notImplemented annotation would definitely be an option, but it has to hook much deeper into the language.
Either it is similar to default methods (like in Java interfaces), which is a full-fledged language change, or it allows abstract methods to be implemented (which is also a major language change wrt strong mode).
The willOverride annotation has the advantage that it is completely language independent. The override check is something that is not enforced by the language and only looked at by a linter. Modifying the linter is much easier.

That assumed we want to add this annotation to hundreds of internal
libraries. I'm not convinced we do.
On Tue, Nov 14, 2017, 9:57 AM Florian Loitsch<EMAIL_ADDRESS>wrote:

A @notImplemented annotation would definitely be an option, but it has to
hook much deeper into the language.
Either it is similar to default methods (like in Java interfaces), which
is a full-fledged language change, or it allows abstract methods to be
implemented (which is also a major language change wrt strong mode).
The willOverride annotation has the advantage that it is completely
language independent. The override check is something that is not enforced
by the language and only looked at by a linter. Modifying the linter is
much easier.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/30811#issuecomment-344343228,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKQ7uQ8vWHgrGRqF__kbNfGWa-8XZdfks5s2dSJgaJpZM4PdS1N
.

I was going to close this, but if implemented properly (and behind a flag, so its not part of the spec), it would make it much much easier for non-stable releases to add temporary stub APIs without doing giant refactors.

I thought about this some more - what about a @stub or stub keyword?
abstract class Base {
  void a();
}

OK, 6 weeks later, I want to add b:
abstract class Base {
  @stub
  void b();
}

This would basically generate:
void b() => throw UnimplementedError();

... it could even just call super.noSuchMethod(), if you really wanted, similar to the forwarders.

The problem here is that annotations do not change the language. It's still a language error to not implement the interface, and no amount of annotations should be able to change that.
(That said, if it only works for the platform libraries, I guess we could find a way around it, by technically saying that we pre-process your input program, and it isn't the program we actually compile and run)
The proper solutions to this issue is either (or both of)

Interface default methods. An interface can declare a method implementation to be "default". All classes implementing the interface, and which do not have an implementation for that name already, will automatically "mix in" the default method. It's still breaking to have an incompatible member with the same name, but it's not a problem to not have anything. Default methods can only access the public interface of the class it's declared in.
Extension methods: Static methods declared on a class, selected by the static type of the expression they are called on. That would allow future.catchErrorOnly to be added without breaking any interfaces, because it's really just a static function with a fancy way of selecting it. It also means that the method cannot be intercepted in, say, DelegatingFuture. (There are multiple possible variants of extension methods, all of them would work here).

We could also get something like C#'s new/override distinction, which allows existing members with the same name to not conflict, because they are "new" (but that's tricky because we currently write nothing, and it means both "new" and "override").

Closing in favor of https://github.com/dart-lang/sdk/issues/30416 then.


Base Tokens Not Showing Price

Tokens on the Base chain aren't correctly showing prices, like on other chains, despite being listed on CoinGecko. Prices do show for other tokens manually added via contract address, as long as they're listed on CoinGecko, so I believe this is a bug with the Base layer specifically. For me personally, I have this issue with $DEGEN.
CoinGecko Listing: https://www.coingecko.com/en/coins/degen-base
Price not showing:

This issue has also been reported by other users on the Telegram:

It's the exact same issue for me!
Please fix so we can see the prices, this is necessary for me to keep using it

Thanks for reporting, the issue has been fixed
$DEGEN and other popular tokens from this list https://www.coingecko.com/en/categories/base-ecosystem should already be available in the app, and their prices should be displayed as well.
Tokens previously added manually should update automatically after restarting the app.
If this is not the case, please delete them from the app and re-add them using the 'Manage tokens' screen.
If the issue persists, please contact technical support via email

Thank you for the quick fix @m3g0byt3. Will prices also be shown for tokens on the Base network that are listed on CoinGecko but need to be added manually on the Tangem app in the future?

@QuixThe2nd
All tokens are imported from CMC/CoinGecko in a semi-automatic fashion, with some moderation (e.g. filtering due to low scores on antirug checkers, etc) being applied before a particular token becomes available on the 'Manage tokens' screen in the app. This is the case for all supported networks, not something Base-specific.
If a particular token (on a supported network) is already listed on CMC/CoinGecko but not yet available in the app, please contact support via email for details. There may be some issues (again, like low antirug checker score, for example) preventing it from being added to the list of tokens on the 'Manage tokens' screen.


What is a 'silenced rule?'

I'm doing some testing with elastalert 0.0.80.   I made some changes to my test alert and then started seeing stderr output like this.  I think I did change the aggregation originally from a schedule to 15 minutes before this first started happening:
INFO:elastalert:Starting up
INFO:elastalert:Queried rule Monitor - TEST from 2016-05-19 16:13 EDT to 2016-05-20 16:13 EDT: 8454 hits
INFO:elastalert:New aggregation for Monitor - TEST. next alert at 2016-05-19 20:28:57.650000+00:00.
INFO:elastalert:Ignoring match for silenced rule Monitor - TEST
INFO:elastalert:Ignoring match for silenced rule Monitor - TEST
INFO:elastalert:Ignoring match for silenced rule Monitor - TEST
INFO:elastalert:Ignoring match for silenced rule Monitor - TEST
INFO:elastalert:Ignoring match for silenced rule Monitor - TEST
...
How did my rule get 'silenced' and what does that mean?    I tried to reset this condition by renaming the rule and deleting the elastalert_status index and recreating it but it still gives me these messages.
This is my rule:
name: Monitor - TEST
type: frequency

index: logstash-%Y.%m.%d
use_strftime_index: true

num_events: 1
timeframe:
    minutes: 15
aggregation:
    minutes: 15
filter:
- query:
    query_string:
      query: 'type:userlog AND userName:montest*'
alert:
- email
email:
- testmon

By default, you will only get one alert per rule per minute. This is because the default value for realert is minutes: 1. You can set this to 0 to get every alert.

Thank you!


tips on debugging?

in node v8.4.0, one of our test cases for our node native add is failing: https://github.com/nickdesaulniers/node-nanomsg/issues/183
it seems that node is exiting from a call to abort().
From gdb, I found that the abort() is coming from libuv: https://github.com/nanomsg/nanomsg/issues/926#issuecomment-340316253
In order to find which abort is being triggered, do I need to compile libuv myself w/ debug symbols, then run node in GDB but have have it link in my libuv?
v8.4.0 is not necessarily the first version of node that fails, so I code bisect on difference versions of node to see what versions of libuv this changed in, then narrow down the change sets.

I was able to fix the issue, but next time I'll try what I suggested above.  sorry for the noise


Reduce fields in new task/method

I suggest to reduce fields that a user is requested to fill out for a new task or method. As a user I am very lazy. I understood that for methods I need to fill out Name, Full Name and Description to be able to make a submission, but to do so, I generally copy-paste the same word in all fields, also because I am unsure of what to put in the description (see #435), i.e. whether I should add comments on the specific device of the submission or more generally about the method.
My laziness would suggest eliminating the full name option (can we allow one to edit the full name on the Task/method page?) and say that descriptions are optional. However I don't know the implication of this for the system. Maybe full names and descriptions could be shown as optionally to add in the pages of the Method or Task that get created. This adds another (optional) step, but simplifies the task of adding a metric, which requires adding a submission, a task and method first.

+1

I'd suggest automatically copying "full name" from "name," if a member doesn't provide one, and making it immediately obvious at a glance that "name" is the only required field. (I fill all three fields out, with different values, but I see your point.) So long as the user can immediately see that all that's required is the name, I think we accomplish the intent of this issue.


Store experiment when it was created

Signed-off-by: cwen0<EMAIL_ADDRESS>What problem does this PR solve?

Fix #657 #557
What is changed and how does it work?

store experiment when it was created
add archived field to archive_eperiment struct, when some experiment was deleted and update archived to true

Codecov Report

Merging #662 into master will decrease coverage by 0.05%.
The diff coverage is 25.49%.

@@            Coverage Diff             @@
##           master     #662      +/-   ##
==========================================
- Coverage   55.78%   55.72%   -0.06%
==========================================
  Files          68       68
  Lines        4383     4400      +17
==========================================
+ Hits         2445     2452       +7
- Misses       1768     1778      +10
  Partials      170      170

Impacted Files
Coverage Δ

controllers/networkchaos/ipset/ipset.go
37.14% <0.00%> (ø)

pkg/store/experiment/experiment.go
30.64% <0.00%> (-8.14%)
:arrow_down:

pkg/utils/chaosdaemon.go
51.21% <0.00%> (ø)

pkg/utils/grpc.go
0.00% <0.00%> (ø)

controllers/twophase/types.go
54.20% <40.00%> (-1.68%)
:arrow_down:

controllers/networkchaos/netem/types.go
47.27% <50.00%> (ø)

controllers/podchaos/containerkill/types.go
64.38% <100.00%> (ø)

controllers/timechaos/types.go
61.44% <100.00%> (ø)

pkg/webhook/config/watcher/config.go
100.00% <100.00%> (+58.33%)
:arrow_up:

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 699993e...58f426c. Read the comment docs.

TBH I don't think it is a good choice. The experiment object can be updated/changed after it is created. Then do we want to update the archive experiment in db every time?

TBH I don't think it is a good choice. The experiment object can be updated/changed after it is created. Then do we want to update the archive experiment in db every time?

Yes, I think we can update it in DB every time.

@YangKeao @yeya24 PTAL, thanks!

/merge


Document: Billable trait method createAsStripeCustomer()

https://laravel.com/docs/5.4/billing
https://github.com/laravel/cashier/blob/7.0/src/Billable.php#L530
This method is useful if you want to add a card before subscribing.  Or if you want to have some customers that have cards but no subscriptions. Source code is easy to understand but more people should know about this.

Sent in a pr for this: https://github.com/laravel/docs/pull/4622


[bug] Desync between Spark theme and Design specs on color scheme

There is a difference of tokens between figma & tailwind config viewer for onBackground :

in tailwind config viewer, onBackground is #000000
in figma & spark-tokens repo onBackground is #1D1F2A

--> onBackground should use the following color: BlackAdevinta 900 (#1D1F2A)
slack thread : https://adevinta.slack.com/archives/C04LNCEMMUN/p1696583537959389

@elisa-hery if you want to have a look on fixed color scheme: https://spark-o877om9g0-spark-team.vercel.app/viewer/

@soykje ok ✅ (I didn't check every token, just checked the one you updated)

@solygambas Just for you to know, we can wait for you if you want to have a final look on this? 🙂


add publisher topic parameter to forward_position_controller

In general isn't this what remapping is for?

In general isn't this what remapping is for?

actually no in this case. It would be better that we enable setting of argument in YAML file to give path to custom configuration. This way users don't have to copy the launch file and adjust it, but just include it and set new configuration. Also convinient for CMD calls.

Ok I agree, config file is good!


Revised "overlooked asset" detection; tesselinclude hinting. Fixes gh-644

This revision fixes some annoyances and garbage that I overlooked in the first implementation:

This revised warning is never shown for --full, because that makes no sense, all files will be pushed every time.
Takes into consideration that asset files and directories might indeed be directly required by the program.
Doesn't display such an awful message, no more file list, etc.
Puts the information in the --help text (both run and push)

Signed-off-by: Rick Waldron<EMAIL_ADDRESS>

cc @johnnyman727 @HipsterBrown

r+

Very smart system. Nice that we can scan the dependency graph like that. Great update. :+1:

Thanks everyone


feat: accept 'dialog' as a method

Catching up with the ever-improving standards, I propose adding 'dialog' as an accepted form method. See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form#method

I'll try to do a release over the weekend 🥂

Thanks for merging so fast. Take your time with the release 🙌


CodeGen: add Vuejs support

[x] add Component codegen
[x] add spec file codegen
[x] add HTML codegen
[x] add styles codegen
[x] add readme codegen
[ ] add export to stackblitz
[ ] add unit test
[x] add entry to the editor menu

I will look for this impl.

Unfortunately, VueJS 2 can't be used in Stackblitz. 😫

Fixed in #148


Liability Waiver Update + CheckBox Fix

Our Milestone: Liability Waivers stay updated
We want to make sure when admins change their liability waiver or add a new document for caregivers to sign, that change should appear to all users (new and previous users). Currently, changes are only reflected when you make a new account, but we want to implement that for old users as well.
Your Task:  When a user logs out of the account and logs in again, if any new documents are unsigned or documents have been edited, they must go through the liability waiver process of the onboarding screens again after logging in but before viewing the rest of the app.

In addition, for ALL checkboxes, (in liability, item requests, etc), please also add the href/"clicked" tag to when the text is tapped as well. The current implementation of selecting an option on mobile is it you directly click the checkbox, but that is not super accessible, so we must also include the text! In HTML, this is done with the label tag — that might help in finding out how to do it in React Native. Imagine trying to tap that little checkmark with your thumb!
Important Information

An admin will add a new document or change the waiver in the settings tab
New users creating accounts will go through onboarding with updated documents (already implemented)
Old users (only if they log out and have to log back in) must see the liability waiver screens if the new documents haven't been completed by this user's account.
Text should also act as a toggle when selecting checkboxes. Please fix this for all mobile screens having this UX behavior.
There are multiple ways to do this:

Compare the timestamps of created/updated to when the caregiver signed
Create a hash of the data that was stored with the caregiver, and then check if they're the same
Or another way. Either way, don't do this check all the time. Only when they log in is fine, and if there's updates it should tell the caregiver that there are updates to the waiver process.

Never hesitate to reach out for help!

Abandoning React Native mobile app so changes aren't needed


model evaluation & two error messages

Great script!!!
After loading german.model the evaluation yielded nice results:
nouns: SI/PL: 26.8% (134/500), 60.0% (300/500), 100.0% (500/500)
nouns: PL/SI: 21.2% (106/500), 53.8% (269/500), 100.0% (500/500)
adjectives: GR/KOM: 40.8% (194/475), 69.9% (332/475), 95.0% (475/500)
adjectives: KOM/GR: 36.1% (170/471), 64.1% (302/471), 94.2% (471/500)
adjectives: GR/SUP: 10.3% (27/262), 31.3% (82/262), 52.4% (262/500)
adjectives: SUP/GR: 7.6% (21/276), 21.4% (59/276), 55.2% (276/500)
adjectives: KOM/SUP: 23.4% (60/256), 55.1% (141/256), 51.2% (256/500)
adjectives: SUP/KOM: 31.6% (83/263), 54.4% (143/263), 52.6% (263/500)
verbs (pres): INF/1SP: 78.0% (320/410), 95.6% (392/410), 82.0% (410/500)
verbs (pres): 1SP/INF: 71.8% (296/412), 93.7% (386/412), 82.4% (412/500)
verbs (pres): INF/2PP: 56.7% (208/367), 74.4% (273/367), 73.4% (367/500)
verbs (pres): 2PP/INF: 65.5% (237/362), 76.2% (276/362), 72.4% (362/500)
verbs (pres): 1SP/2PP: 54.4% (185/340), 65.3% (222/340), 68.0% (340/500)
verbs (pres): 2PP/1SP: 62.3% (223/358), 76.5% (274/358), 71.6% (358/500)
verbs (past): INF/3SV: 49.2% (210/427), 91.1% (389/427), 85.4% (427/500)
verbs (past): 3SV/INF: 40.3% (173/429), 92.8% (398/429), 85.8% (429/500)
verbs (past): INF/3PV: 78.4% (352/449), 97.1% (436/449), 89.8% (449/500)
verbs (past): 3PV/INF: 84.6% (369/436), 97.0% (423/436), 87.2% (436/500)
verbs (past): 3SV/3PV: 78.1% (356/456), 93.4% (426/456), 91.2% (456/500)
verbs (past): 3PV/3SV: 85.3% (390/457), 95.6% (437/457), 91.4% (457/500)
total correct:  52.0% (4114/7906)
total top 10:   75.4% (5960/7906)
total coverage: 79.1% (7906/10000)
However, when I tried: model.similarity(‘wort’,’klang') and got: KeyError("word '%s' not in vocabulary" % word). doing: python vocabulary.py DEmodel DEmodel.vocab got me: 'ascii' codec can't encode character u'\u2020' in position 0: ordinal not in range(128).

model.similarity(‘wort’,’klang')

Try to capitalize the input (e.g. model.similarity(‘Wort’,’Klang'))

python vocabulary.py DEmodel DEmodel.vocab got me: 'ascii' codec can't encode character u'\u2020' in position 0: ordinal not in range(128).

it seems you are using python2, use python3 instead.

khewl, thx a bunch!


[E2E]: Policy Hub Contract Reference dropdown field

Current Behavior
Contract Reference Option does appear in Policy Hub, but the field type is a dropdown one.
Although there is a note that the bilateral contract name should be added in the right operand there is no field to do it in.
Issue now it is not possible to add the Bilateral contract name.
Contract Reference is a dropdown field. Only Option is {bilateralContractName}

Expected Behavior

The ContractReffrence dropdown should contain possible Contract Reference names (as it is for UsagePupose or FrameworkAgreement)
ContractReffrence should be a text field where the bilateral contract name is writeable

Steps To Reproduce
Create a policy using Policy Hub

@ciprianherciu  can you please add a better description. It is not possible to understand what you want.
We can not support such tickets.
On top of that, please use screenshots where possible.

@jjeroch The Contract Reference field is present.
Type of the field is a Dropdown.
Only Dropdown option is {bilateralContractName}.
Is this is how it supposed to work?
Other Dropdown fields from Policy Hub have options

@ciprianherciu what do you mean with dropdown, the contract reference is not a dropdown field. The contractReference is a bilateral contract name which is created on paper between two parties. We can off course not know the contract name; the right operand is a free-text-field

@jjeroch
To use the Policy Hub, we have categorized  the fields based on the attributes:
•	If the attribute is static than the field will be a dropdown field
•	If the attribute is Regex than it will be an input field
f.e.:

Since ContractReffrence has the attribute Static which will be represented in SDE as a dropdown field.
If it is expected that the bilateral contract name should be written in a text field, could we adjust the attribute to Regex, as it is for the BPNL?

@ciprianherciu it is always a huge risk which you take if you implement an logic which is not supported/not shared/proposed by the actual data provider. You implemented based on own assumptions of type meanings. Thats not recommended.
For me the regex is not making sense since there are no limitations; regexes are important if you have a fix given set of characters. However leaving the decision for @MaximilianHauer

relates to https://github.com/eclipse-tractusx/policy-hub/issues/176

@ciprianherciu we should not adjust the policy configuration only that it fits your needs. if you notice that the implementation of yours is not fitting then this is the place to improve on and not the setup of the policy.


E2E tests fail in VSCode version 1.93.0 with "target window already closed" when running "Developer: Reload Window"

Hi WDIO Team,
I'm working on the Salesforce Extensions for VSCode.  Our E2E tests are built using the WDIO framework.  After the release of VSCode version 1.93.0, my team started to notice that our E2E tests are failing with a "target window already closed" error.  We are using the latest version v6.1.0 of wdio-vscode-service.
Here's an example of a failed test run on 1.93.0: https://github.com/forcedotcom/salesforcedx-vscode/actions/runs/10779098563/job/29891858831
Currently, we have pinned our E2E tests to run on VSCode version 1.92.2, which is a temporary workaround.  However, we do want to keep up with the times and run E2E tests on stable VSCode version.
I was able to reproduce the issue when running my E2E test locally.  I found that the issue happens when running Developer: Reload Window in the target VSCode window.  As soon as I hit Enter after selecting Developer: Reload Window from the command palette, the target VSCode window gets closed.  I tried several other commands, and they ran fine in the target window.
Here's a short video of the issue: https://vimeo.com/1008588498

Thanks for reporting the issue @daphne-sfdc. To get ahead of @christian-bromann, any contributions would be much appreciated!
I'm not familiar with the specifics, but I would expect the Developer: Reload Window command to behave differently from other commands since it will close the VS Code / Electron / Browser window that it is connected to so we'd no longer be able to communicate with the target window. You'd have to detect the new window and update the reference in all the selectors. With some luck, other maintainers have already encountered this problem here or in the Electron service too.

Hi @seanpoulter,
Thank you for getting back to us. My team and I are looking into the issue further and were wondering if you could provide any additional details about what changed in VSCode version 1.93.0. Specifically, we are interested in understanding what might be causing the selectors to no longer detect the new target window after a reload.
We have already reviewed the VSCode release notes but didn't find any information regarding changes to selectors. Any insights or pointers you could share would be greatly appreciated, as they would help us in addressing and potentially fixing the bug.
Thank you!

FYI: a workaround is to install wdio tools at version 8 and wdio-vscode-service at version 6.0.3. If either was a later version I got the same error, but with those version everything ran fine.

Hi @haberdashPI,
Thank you for suggesting the workaround. Unfortunately, it didn't resolve the issue for me. I was already using all WDIO tools at version 8, and downgrading wdio-vscode-service to v6.0.3 still resulted in the "target window already closed" error after running the Developer: Reload Window command.

You might want to check through the errors above that, that is usually the product of some problem further upstream, so that might have more clues

Out of curiosity I looked through your tests: I don't think it has anything to do with my problems.
[0-0] Reloading window

After that message, the test never recovers; seems like the root issue is about how the service re-attaches when reloading the app.

Hello @seanpoulter,
I followed your suggestion to check the selectors but found during my investigation that the selector for the entire VSCode window (.monaco-workbench) did not change between VSCode versions 1.92.2 and 1.93.0.
I then probed deeper into the code to check how wdio-vscode-service handles Developer: Reload Window and was quite surprised to find that reload doesn't seem to be handled at all in the code. I also put console.log() statements all over the code that handles opening VSCode at the beginning of the E2E test (in src/service.ts and src/launcher.ts), figuring a reload would be handled the same way as the first time VSCode is opened, but none of my logs got printed during a successful reload that I ran with 1.92.2.
This leads us to believe that the issue is not with the selectors but rather a larger design issue in wdio-vscode-service. It appears that reloads were never handled in the first place.
We would appreciate your guidance on how to proceed with this. It seems like a significant change might be required to properly handle window reloads in wdio-vscode-service.
Thank you for your assistance.

Hi @haberdashPI, Do you have examples of tests containing Developer: Reload Window that you can share with us?  We'd like to take a look to see how that works in VSCode version 1.93.  Thanks!

I do not. I have not tried to use this package under that scenario.

Hi @seanpoulter, I was wondering if you had any comments about what @daphne-sfdc mentioned above. Thanks again in advance for your help.


Configuring Timeout for Graceful Shutdown

Version
latest
Description
I'm currently working with tonic for implementing gRPC services in Rust, and I've encountered a situation where the server might not shut down gracefully due to long-running or unresponsive RPC connections.
I tried this code:
I have updated the bi-directional streaming example with custom shutdown logic, where the server shutdown is expected to be triggered based on a signal. This works as expected until a stream connection remains active indefinitely, causing the server to not shutdown.
async fn shutdown_signal(
    mut shutdown_on_err: mpsc::Receiver<()>,
) {
    let ctrl_c = async {
        signal::ctrl_c()
            .await
            .expect("failed to install SIGINT handler");
    };

    let terminate = async {
        signal::unix::signal(signal::unix::SignalKind::terminate())
            .expect("failed to install SIGTERM handler")
            .recv()
            .await;
    };

    let shutdown_on_err_future = async {
        shutdown_on_err.recv().await;
    };

    tokio::select! {
        _ = ctrl_c => {},
        _ = terminate => {},
        _ = shutdown_on_err_future => {},
    }
    println!("shutdown signal received");
}

#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
    let (shutdown_tx, shutdown_rx) = mpsc::channel(1);
    let shutdown_signal = shutdown_signal(shutdown_rx);

    tokio::spawn(async move {
        sleep(Duration::from_secs(30)).await;
        println!("Shutting down the server after 30s");
        shutdown_tx.send(()).await.unwrap();
    });

    let server = EchoServer {};
    Server::builder()
        .add_service(pb::echo_server::EchoServer::new(server))
        .serve_with_shutdown("[::1]:50051".to_socket_addrs().unwrap().next().unwrap(), shutdown_signal)
        .await
        .unwrap();

    Ok(())
}

However, if some RPC is abnormally pending for a long time, the server has to wait.
Can I set a timeout for the graceful shutdown?

That isn't directly supported right now, but would be possible to add. I think I hesitate to say "lets just add it" because the ecosystem for hyper servers is pretty unstable right now, hence tonic currently implements its own graceful shutdown.
You could also implement it yourself by wrapping around Server. You'd want a future which waits for your shutdown signal, then waits for the timeout. Then you'd use tokio::select! on that + the server, and bail as soon as either future finishes, dropping the server, cancelling any remaining futures.

We've run into a slightly different case for being able to configure a timeout on graceful shutdowns. We're seeing cases where the accept loop exits (for us due to this), but the the server enters the graceful shutdown path and waits indefinitely. This leads to having a server which hasn't exited and thus still appears "alive", but is not accepting any further connections. Unlike the graceful shutdown signal path, there doesn't appear to be an obvious workaround here, as that path lives entirely inside tonic.
It'd be pretty useful for our use case to be able to set a timeout that we're willing to wait for connections to shut down gracefully before abandoning them in the event of a shutdown due to a listener error or the like.

Same issue as @PDXKimani