Fix bulk workflow action

Propose:
Fixed the issue where new list items could not be selected. Batch operations have been re-enabled.
fix #2918
Change:
Adding a new button to the user workflow interface. Clicking it enters batch selection mode. In this mode, clicking an item selects the corresponding workflow instead of navigating. A blue border highlights selected workflows. A red indicator appears next to the activation button when batch selection mode is active. A notification pops up whenever the mode is enabled or disabled.
Demo:
https://github.com/user-attachments/assets/7555bae8-f065-4e57-a447-3693c5e097d4

@GspikeHalo Just to clarify, are you asking me or @bobbai00 to review the PR?

Thanks for the PR! @GspikeHalo @sixsage Can you achieve this experience? I feel like it is unnatural to let users click a button to allow a multi-selection.
You can see Kaggle or Gmail's experience.

@GspikeHalo Just to clarify, are you asking me or @bobbai00 to review the PR? yes

@bobbai00 I have completed the modifications. When the user hovers over an item, the checkbox is displayed, and it can be selected by clicking. I also added the 'Select All' and 'Deselect All' functionality. I have uploaded a new demo video as a reference.


Updated the changelog for the v4 release

Preparing for the v4 release. Condensed the changes/additions but kept the deprecated removals for user reference.

The only comment I have is keep this diff handy. I think people doing migrations to v4 will want to reference some of the details you removed from the Changes section.


List of offline validators during an upgrade

We should build a tool that allows querying for a list of offline validators ranked by voting power (highest to lowest) by name for upgrades. This should help with upgrade coordination

existing art https://github.com/Kava-Labs/kvtool/blob/master/cmd/launch-blame.go

Note this one pulls the validator info from a genesis file, if the RPC is online we can use q staking validators instead.

This should help with upgrade coordination

We would get this by just inspecting the latest block. It'd be great to also allow passing in a historical block (or block range). This could enable report generation for downtime events and other use-cases. I'll probably pick up this ticket.

https://github.com/blockpane/pvtop does a fairly excellent job of this


Add RoAlgo and Kilonova

RoAlgo is the biggest Romanian competitive programming and algorithmics Discord server, with almost 2700 members. Kilonova is a new but very popular competitive programming platform.

Thank you for your PR. Merged.


Fix: Wrong fuel consumption in summarys

Fix for: https://github.com/DurgNomis-drol/mytoyota/issues/287
The metric was converted from a bool to a string when the self variables was declared.
This meant that simple conditions such as if self._metric no longer worked and the conversion of the fuel consumption failed, or rather the value for gallons was always returned.
self._metric is now a bool again and a new variable self._distance_unit was introduced, which is used for the conversion of distances.

During testing, I came across another problem.
For example, a monthly statistic for December 2023 returns the following values
pp.pprint(
            f"Summary: {[[x] for x in await car.get_summary(date(2023, 12, 1), date(2023, 12, 31), summary_type=SummaryType.MONTHLY)]}"  # noqa: E501
        )

("Summary: [[average_speed=41.09 countries=['DE'] duration=16:52:14 "
 'distance=693.167 ev_duration=5:34:22 ev_distance=197.999 '
 'from_date=2023-12-01 to_date=2023-12-31 fuel_consumed=44.157]]')

But I definitely didn't consume 44 litres per 100 km 🤯
The app also shows me a more realistic 6.4l/100km. So it seems to calculate the values differently somehow.
This is not directly due to a problem with the conversion or processing of the values, as 44157.0 ml are also returned in the original _SummaryBaseModel used:
{
  "length": 693167,
  "duration": 60734,
  "duration_idle": 2125,
  "countries": [
    "DE"
  ],
  "max_speed": 132.0,
  "average_speed": 41.09,
  "length_overspeed": 66006,
  "duration_overspeed": 3493,
  "length_highway": 59361,
  "duration_highway": 2255,
  "fuel_consumption": 44157.0
}


s.ok() could not find cudnnCreate in cudnn DSO

Problem with underlying cudnn install -- I think asking an experienced cuda user or googling is your best bet.

Thank you. I've resolve it.


Autoupgrade fixes

depends on #1823
This further prevents Docker Hub from being assumed for auto-upgrade apps. From the previous PR, some of the validation was done client-side, leading to the ability to deploy an auto-upgrade app with Docker Hub as the default registry if done by applying a YAML manifest directly to the cluster.
This PR also ensures that auto-upgrade apps will prefer remote images over local images, including on the initial deployment. (Prior to this there was a problem where an auto-upgrade app would prioritize local images at first, and then the daemon would prioritize remote images. This fixes that.)
Checklist

[x] The title of this PR would make a good line in Acorn's Release Note's Changelog
[ ] The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
[x] All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
[x] Commits follow contributing guidance
[x] Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
[x] Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
[ ] PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

Squashed everything down to one commit to make it easier to rebase.


Add cgroup bind mount by default

Libcontainer already supported mount container's own cgroup into
container, with this patch, we can see container's own cgroup info
in container.
Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

ping @crosbymichael, @LK4D4

ping

ping @crosbymichael @ewindisch
Do we want to expose this info to containers?

I don't know of a direct security impact here, although it does open the surface area in that vulnerabilities in the kernel could potentially allow remounting this directory.
More generally, however, I question if we should break the fourth-wall here. There is a line of thought that containers need not know that they're containers, nor know what their cgroup configuration is. What is the value of this to users / developers?

@ewindisch One thing for clear is that this PR doesn't make containers know that they're containers, but make them more like they are hosts which have no sub cgroups. Maybe the RO makes it a bit weird.

Collective review with @jfrazelle @crosbymichael @calavera
We're fine making this a default as long as the security team gives a green flag on this (which apparently @ewindisch already does). Ping @diogomonica @NathanMcCauley for other opinions.

LGTM

LGTM

LGTM

Do we need docs anywhere for this?

@icecrime It only affect applications in the container, and there are no UI yet, I don't think we have docs for this, like fs specs in the container, do we?

@hqhq this looks good.  Do you think you could add a test to ensure that it is RO and we don't regress on that point?

LGTM

@crosbymichael Test case added, PTAL.

LGTM

Having an issue when running Docker in Docker and bisected the problem it to this commit.
Cannot start container <omitted>: [8] System error: Error found less than 3 fields post '-' in "262 261 0:85 / /sys/fs/cgroup rw,nosuid,nodev,noexec,relatime - tmpfs  rw,seclabel"

This is a known bug on master it's fixed in runc

On Jul 15, 2015, at 17:37, Derek McGowan<EMAIL_ADDRESS>wrote:
Having an issue when running Docker in Docker and bisected the problem it to this commit.
Cannot start container : [8] System error: Error found less than 3 fields post '-' in "262 261 0:85 / /sys/fs/cgroup rw,nosuid,nodev,noexec,relatime - tmpfs  rw,seclabel"
—
Reply to this email directly or view it on GitHub.


Bump crossbeam-utils to 0.7

@alex Have you actually tried building with crossbeam 0.7? It appears to break the build.

I did not, since it was Windows only, and I don't have a Windows machine. I
did my best to check by hand, but it looks like I missed something. Sorry
about that :-(
On Sat, Dec 7, 2019 at 7:48 AM Hrvoje Nikšić<EMAIL_ADDRESS>wrote:

@alex https://github.com/alex Have you actually tried building with
crossbeam 0.7? It appears to break the build
https://travis-ci.org/hniksic/rust-subprocess/jobs/620837860?utm_medium=notification&utm_source=email
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hniksic/rust-subprocess/pull/31?email_source=notifications&email_token=AAAAGBFFE4OUU2VUWY56PA3QXOLTBA5CNFSM4JVNANR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGGGGLQ#issuecomment-562848558,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAGBGMVUECDZU2XGEPDX3QXOLTBANCNFSM4JVNANRQ
.

--
All that is necessary for evil to succeed is for good people to do nothing.

I did not, since it was Windows only, and I don't have a Windows machine.

Good that we have Windows CI. :) Just out of curiosity, why did you submit the PR if you're not using the functionality?
Regarding the error itself, it seems that crossbeam changed its API incompatibly. Judging by the compilation output, it should be straightforward to fix; would you like to try?

I try to keep my cargo.lock from bloating with too many versions of the same package, even if they're not actually being used in my builds.

It looks like simply unwrap()ing the Result would match the behavior of 0.5 (https://docs.rs/crossbeam-utils/0.5.0/crossbeam_utils/thread/fn.scope.html#panics). Would you like that implementation, or to attempt to turn the Err into an IoResult::Err?

Also, crossbeam-utils is no longer a dependency.


Multiple values from text search

That would suit me too.  I have a bunch of entries for running in the form of 'run:: 5.32 @ 6.21'.  This means that I ran 5.32km at a pace of 6.21 minutes per km.  I would love to be able to plot that as two lines on a chart.  At the moment I'm doing this by recording the string directly in the body of my daily note rather than in the front matter.  Can I get the two values using a text search target and regular expression ?  I'm struggling to understand the syntax of how to do that.
Thanks
Originally posted by @dcoales in https://github.com/pyrochlore/obsidian-tracker/issues/13#issuecomment-838922228

Version 1.5.0 just released.
You can find a example of this here.

Will close this issue.


rewrite pausing to support enabling individual functions per wrapped token

I might just be confused, but are we testing all 4 potential paths in the enable/disable code? From my understanding there's:

Well since you’re both saying the same thing, I’ll add it.
There is an implicit test for the enabled state since we have successful swap tests, just not wrapped in the enable/disable calls.

I was actually a bit more worried about whether we explicitly test what happens if someone who isn't authorized attempts to call the enable/disable stuff.


Binary Compatible gRPC for Alpine Linux

https://github.com/grpc/grpc/pull/10407
Allowed gRPC to compile on Alpine Linux (musl libc).
It would be nice if gRPC was cross compatible when built against glibc.  This would require getting around sched_getcpu and swapping memcpy with memmove.

This is fundamentally impossible, GRPC_MSG_IOVLEN_TYPE is incompatible.
On musl (and mac), it conforms to the posix standard as being an int.  But for glibc, it is a size_t.

What if we used writev in tcp_posix.c?
On Fri, May 12, 2017 at 3:42 PM kpayson64<EMAIL_ADDRESS>wrote:

This is fundamentally impossible, GRPC_MSG_IOVLEN_TYPE is incompatible.
On musl (and mac), it conforms to the posix standard as being an int. But
for glibc, it is a size_t.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/10560#issuecomment-301202029, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJpudfWi3Dv9B9wdziY2k2M1i3wWr_sMks5r5OBygaJpZM4M5Uqu
.

@ctiller
Scanning the linux/posix documentation, it looks like that might work.

I think this works now, feel free to reopen if more work needs to be done.


PolyG trimming?

Hello,
Thanks for the program. I'm working with NovaSeq data currently and would like to try out the polyG trimming. After trimming, it looks like fastp still retains reads with 8 or less Gs at the ends of reads. Is that a default set by fastp and what is the reason for doing so? Any way I can change the number of G's fastp lets through its filter?
Cheers,
Mun

With the latest version in the master branch, you can use --poly_g_min_len to change the minimum length requirement for polyG detection. By default it's 10.

Any update? Have you tried the new fastp from http://opengene.org/fastp/fastp ?


Update D:\Git\winget-pkgs\manifests\a\Apple\ProResRAWforWindows\1.3

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114176&drop=dogfoodAlpha

@wingetbot run

Automatic Validation ended with:

Installation failed with exit code -1978335226
2023-08-03 09:37:22.542 [CLI ] ShellExecute installer failed: 1603 CustomAction +_88A6ECE3EAA6D1032B49CA3AF8E62694 returned actual error code -2147024770 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (74:F0) [09:37:21:959]: Product: ProRes RAW for Windows -- Error 1904. Module C:\Program Files\Apple\ProRes RAW for Windows\PRRawDebayer.dll failed to register.  HRESULT -2147024770.  Contact your support personnel. Error 1904. Module C:\Program Files\Apple\ProRes RAW for Windows\PRRawDebayer.dll failed to register.  HRESULT -2147024770.  Contact your support personnel. Property(S): ErrorDialog = ErrorDialog
MSI (s) (74:F0) [09:37:22:146]: Product: ProRes RAW for Windows -- Installation failed.
MSI (s) (74:F0) [09:37:22:162]: Windows Installer installed the product. Product Name: ProRes RAW for Windows. Product Version: 1.3. Product Language: 1033. Manufacturer: Apple. Installation success or error status: 1603.


CrossGeolocator timestamp is 1 hour off in iOS

Bug
Version Number of Plugin: 3.0.4
Device Tested On: iPhone 7 10.3.1
Simulator Tested On: 10.3
Expected Behavior
Position.Timestamp should be UTC
Actual Behavior
It's UTC -1
Steps to reproduce the Behavior
CrossGeolocator.Current.StartListeningAsync(5, 10, false);
CrossGeolocator.Current.PositionChanged += Current_PositionChanged;
private void Current_PositionChanged(object sender, Plugin.Geolocator.Abstractions.PositionEventArgs e)
{
// Observe that e.Position.Timestamp is off by one hour
}

I believe fixed in the new beta.


Don't exit route/middleware when it continues to match current/next path

What is the preferred functionality here?
A) When the middleware still matches, the exiting promise given last time still won't resolve, but the middleware function is still called again.

You might have duplicate handlers then, since the first ones never got cleaned up.

B) When the middleware still matches, it doesn't get called again.

This would require caching intermediate results and only running the functions that differ. I think this is a no-go, considering the assumptions it makes about your middleware functions' behavior.

Perhaps the problem is the time gap between the exiting promise resolution and the function being called again? I'm pretty sure I can reduce that time gap, perhaps even to having the middleware called before the exiting promise resolves. Would that help the use case you were thinking of?


Importing import React, { Component } from 'react' gives runtime warning

TypeScript Version:

2.9.2
3.1.0-dev.20180726:

Search Terms:
React.PropTypes, Warning: Accessing PropTypes
Code:
tsconfig.json
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true
  }
}

index.ts
import React, { Component } from 'react';
console.log(React as any, Component as any);

Expected behavior:
"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
var react_1 = require("react");
var react_1_default = __importDefault(react_1);
console.log(react_1_default.default, react_1.Component);

Actual behavior:
"use strict";
var __importStar = (this && this.__importStar) || function (mod) {
    if (mod && mod.__esModule) return mod;
    var result = {};
    if (mod != null) for (var k in mod) if (Object.hasOwnProperty.call(mod, k)) result[k] = mod[k];
    result["default"] = mod;
    return result;
};
Object.defineProperty(exports, "__esModule", { value: true });
var react_1 = __importStar(require("react"));
console.log(react_1.default, react_1.Component);

Which gives following message in console
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs
It is React.PropTypes deprecation message in getter.
Unfortunately we cannot upgrade to React 16 and not all scripts can be updated to allow warnings in tests (which itself is not a good idea).

before posting this issue I used google.com and github's TypeScript/issues and TypeScipt/search.

Playground Link:
https://agentcooper.github.io/typescript-play/?esModuleInterop=true&target=1#code/JYWwDg9gTgLgBAJQKYEMDGMA0cDecDCE4EAdkifAL5wBmURcA5FKhowNwBQapAzhABskAOgEQA5gApk6eCl5wUJAJ7ZCxMhUUKlygJTsgA
Related Issues:
The only similar problem I found is for Flow: https://github.com/facebook/flow/issues/4673

While in the following cases TypeScript there is no deprecation warning:
import React from 'react'
"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
var react_1 = __importDefault(require("react"));
console.log(react_1.default, react_1.default.Component);

import { Component } from 'react';
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
var react_1 = require("react");
console.log(react_1.Component);

Similar to https://github.com/babel/babel/issues/5705 , "fixing" this requires copying setters and getters without invoking them in the helper.

__importStar implementation:

in TypeScript/blob/master/src/compiler/transformers/module/module.ts
in tslib/tslib.js

So, I assume it should be fixed in the same way as it was implemented here, but taking into account target: es3 compiler option.
If yes - do you accept PRs on this issue?


Correct readme to use verify method name

No worries, thanks for this package! Just what I needed 🙂


Peek Suggestion

Description of the new feature / enhancement
When right-clicking on a file, there should be a peek shortcut in the context menu
Scenario when this would be used?
it would make it easier to peek files and it's better for some  people who use the mouse more than the keyboard
Supporting information
No response

/dup #27754


⚠ Bofrost.at has degraded performance

In a95b94e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2149 ms

Resolved: Bofrost.at performance has improved in 8457361.


day2ops-draft

What are your changes?
What is the urgency level of this change?

[ ] Blocker
[ ] High
[ ] Medium

I have completed these items:

[ ] I have built locally and tested for broken links and formatting.
[ ] If appropriate, I have added redirects.

Are we waiting for the hero illustration and header to be done before merging this?

@daveyheuser How are we doing on this one? It's also due on launch day (the 14th)


not found qsci

Traceback (most recent call last):
File ".\pyeditor.py", line 56, in
from PyQt5.Qsci import QsciScintilla, QsciLexerPython
ImportError: DLL load failed: not found require oprogram file

Hello.
You have to delete the Pyqt5 folder in the ida installation, and replace it with the one i shipped.


Fix travis

Fixes a bunch of issues in the travis config that were preventing the tests from passing. Also tweaks a couple of lines in the latest PRs that broke on Python 3.

Coverage increased (+0.1%) to 80.585% when pulling 4d33eddc0014c3219596a9e83eba61ce8f15ee03 on fix-travis into c920bedf5dc38bcfd2b5dc10a2a093bdc8f7087b on master.

Coverage increased (+0.1%) to 80.585% when pulling 4c958348f7b3f92cce0f60289324dc8d785f219a on fix-travis into c920bedf5dc38bcfd2b5dc10a2a093bdc8f7087b on master.


To add calculator for calculating Biggest Reuleaux Triangle inscribed within a square which is inscribed within an ellipse

Is your feature request related to a problem? Please describe.
To add calculator for calculating Biggest Reuleaux Triangle inscribed within a square which is inscribed within an ellipse

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018


Update fluent-bit to v1.7.0.

Tested:
logs showed up

metrics showed up

Seems like the auto-assigner did not kick in. Assigning manually.


add executeTakeFirstRow(...) & executeTakeFirstRowOrThrow(...) @ RawBuilder.

closes #212.

[x] implement.
[x] unit tests.

small QoL improvement for anyone executing result set returning queries using sql template tag or RawBuilder.
I'm not 100% sure about the naming..
On one hand, executeTakeFirst(...) & executeTakeFirstOrThrow(...) do align with our query builders, so it'll feel like home for our consumers.
On the other, the lack of context in RawBuilder.execute(...) does not allow us to return InsertResult/UpdateResult/DeleteResult (unless we go for sql string compilation - which is probably something we don't want for kysely), so adding Row to these methods removes any false expectations a consumer might have.

This PR introduces a breaking change for anyone who's using errorConstructor arguments in executeTakeFirstOrThrow(...) - it's underlying node's type is now QueryNode | RawNode.

Maybe we should also have something like executeTakeRows(...) (returning O[])?

Sorry, I think this is a bad idea and a weird API. Let's not add these methods to the raw builder.


Improve generation

What does this PR do?
Reworks downloading dependent repos (devworkspace-operator and devworkspace-crds) so that they are

Downloaded sparsely
Merged before generation (to ensure all resources are included in the CSV by default
Git clone/checkout happens in a script so that the makefile is simpler

This PR removes some of the manual patching process, still TODO is the include the alm-examples portion
Note that the csv diff looks significant but the changes should all be formatting/organization.
Is it tested? How?
CSVs in PR are generated using the new script + makefile changes
To get a better sense of yaml changes, you can use
# copy master manifests/web-terminal.clusterserviceversion.yaml to 'y1.yaml and
# pr-branch manifests/web-terminal.clusterserviceversion.yaml to 'y2.yaml'
colordiff -y -W 200 <(yq -Sy '.' y1.yaml) <(yq -Sy '.' y2.yaml)

Reworked this PR and updated PR description

Ideally we merge this PR after https://github.com/devfile/devworkspace-operator/pull/120 so I can regenerate CSVs to include the labels added there.

My only question is whether or not uninstalling the operator removes the web-terminal.service.yaml or does it stay around?

Good question!
The service is not removed when operator is removed. But what is worse - it prevents further operator installation without manual service removing before reinstalling.

Maybe it's expected but not good UX:

It makes sense to investigate if we can avoid it. Ideally - using webhooks configuration in CSV will help us... If no - controller deployment could create service for itself, and instead of using volumes mounts - it could watch to secret&configmap with certs and flush their contents to file system for WebHooks Server.

P.S. The changes related to reworking manifests generation are tested and merged in https://github.com/redhat-developer/web-terminal-operator/pull/3

Closing PR as it looks like the service stuff is going to be an issue.


Added CODEOWNERS and MAINTAINERS files

Signed-off-by: Toddy Mladenov<EMAIL_ADDRESS>This PR combines all the changes from the following PRs for updating the maintainers for notaryproject/notation sub-project:
Add Junjie Gao
Add Milind Gokarn
Add PatrickZheng
Add Pritesh Bandi
Add Rakesh Gariganti
Add Shiwei Zhang
To keep the balance of maintainers, I removed:
Add Yi Zha
The proposal is to abandon the above PRs and merge only this one.

Linking the related PRs: #515 #522 #523 #524 #530 #531 #532

Codecov Report

Merging #542 (9698649) into main (5732b76) will increase coverage by 3.19%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #542      +/-   ##
==========================================
+ Coverage   32.82%   36.01%   +3.19%
==========================================
  Files          25       29       +4
  Lines        1237     1530     +293
==========================================
+ Hits          406      551     +145
- Misses        819      960     +141
- Partials       12       19       +7

Impacted Files
Coverage Δ

cmd/notation/logout.go
44.11% <0.00%> (-10.05%)
:arrow_down:

cmd/notation/cert/show.go
29.31% <0.00%> (-1.46%)
:arrow_down:

cmd/notation/cert/delete.go
32.25% <0.00%> (-1.08%)
:arrow_down:

cmd/notation/verify.go
24.13% <0.00%> (-0.87%)
:arrow_down:

cmd/notation/login.go
41.86% <0.00%> (-0.83%)
:arrow_down:

cmd/notation/plugin.go
0.00% <0.00%> (ø)

pkg/configutil/once.go
100.00% <0.00%> (ø)

cmd/notation/cert/add.go
29.09% <0.00%> (ø)

cmd/notation/manifest.go
0.00% <0.00%> (ø)

cmd/notation/registry.go
0.00% <0.00%> (ø)

... and 14 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Linking the issu #514

Pinging @justincormack for a majority vote.


Unusual crash on 1.19.2

https://pastebin.com/XBPp2nYF
@GalievDev

This prevents me from creating a new world.

Unsupported version


Fix-412: Check UID before deleting PVC

Fix https://github.com/datastax/cass-operator/issues/412
Label the uid to each pvc and check uid before issuing deletion

Hi @srteam2020 as we're moving the on-going development of cass-operator to a new repo: https://github.com/k8ssandra/cass-operator/
We'd love to have this PR updated to target that repo.  Would you want to post a PR there to resolve this?
I've re-created the issue in the new repo already, it's at https://github.com/k8ssandra/cass-operator/issues/118

@burmanm  @jdonenine
Yes, we will create the PR on the new repo. Thanks for letting me know the change.


[.Net SDK, DirectLine] Reopening - Directline Task Cancelled Issue #4754

Bot Info

SDK Platform: .NET
SDK Version: <IP_ADDRESS>
Active Channels: Direct Line + websockets
Deployment Environment: Bot Channel registration + Azure App Service

Issue Description
We have been running our bot for more than a year now. We are starting to see the following error (randomly since 2 weeks now) when our bot tries to post async something back to our channel :
"System.Threading.Tasks.TaskCanceledException","Message":"A task was canceled."
which tends to indicate something is taking longer than expected ? Our bot channel registration plan is S1 and our app service is a Premium Large so dont think this is about scaling issue on our side...
This bot is running in PRODUCTION and this error is hurting us very badly.
We had the issue again today (June 26)
--> this is a reopening of the issue #4754
Actual Results
"System.Threading.Tasks.TaskCanceledException","Message":"A task was canceled."

Hi @Benabaka
Please see the response here: https://github.com/Microsoft/BotBuilder/issues/4738#issuecomment-401913696

Closing as no response


[FR] User sessions

Fixes #2327
This PR adds user sessions in the DB - the normal session behaviour is not changed but the user can see their active sessions in the settings and log out all other devices.
It also moves language settings to display settings.

@matmair looking good!
you just have to add the new db model here: https://github.com/inventree/InvenTree/blob/82d5952ddde9ad507b111d81230d0346e626fc9c/InvenTree/users/models.py#L57

Nice work @matmair very clean implementation :)

Nice work @matmair very clean implementation :)

Was quite easy, is a good standard package by jazzband. I will start on some of my 0.7.0 stuff till plugins are ready as I need them for my remaining 0.6.0 issues.

I'll have some time this week for another review of the plugin system :)


gdal: add libxml2 to build

Motivation for this change
gdal appears to already pull in libxml2 as a transitive dependency (via libspatialite), but it is never enabled in the build. This leads to certain functionality being disabled, like the ability to read OpenStreetMap XML files.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build gdal

Success on aarch64-linux (full log)
Attempted: gdal
Partial log (click to expand)
shrinking /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/lib/python2.7/site-packages/osgeo/_ogr.so
shrinking /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/lib/python2.7/site-packages/osgeo/_gnm.so
shrinking /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/lib/python2.7/site-packages/osgeo/_gdal_array.so
shrinking /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/lib/libgdal.so.20.4.2
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/lib  /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/bin
patching script interpreter paths in /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2
/nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2/bin/gdal-config: interpreter directive changed from "/bin/sh" to "/nix/store/017xymp5i03qzigafnfx7sgf6602gmzq-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2...
/nix/store/aryf33bg24vvzf0spvd14288wyzspwx6-gdal-2.3.2

Success on x86_64-linux (full log)
Attempted: gdal
Partial log (click to expand)
shrinking /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin/gdalsrsinfo
shrinking /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin/gdalinfo
shrinking /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin/gnmanalyse
shrinking /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin/gdal_rasterize
shrinking /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin/gdallocationinfo
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/lib  /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin
patching script interpreter paths in /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2
/nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2/bin/gdal-config: interpreter directive changed from "/bin/sh" to "/nix/store/nii7pk6pv4x4as7vsxbvwyzjn67vax6r-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/zsfwjakhhqxps96cdywxv37p71pc0bp8-gdal-2.3.2...

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: gdal
Partial log (click to expand)
               ^
               nullptr
extensions/gnm_wrap.cpp:4685:17: warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]
  void *argp3 = 0 ;
                ^
                nullptr
extensions/gnm_wrap.cpp:4689:21: warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]
  PyObject * obj0 = 0 ;
building of '/nix/store/0r66fji5gwv5y76p85v1mddszkjyrr7z-gdal-2.3.2.drv' timed out after 1800 seconds
error: build of '/nix/store/0r66fji5gwv5y76p85v1mddszkjyrr7z-gdal-2.3.2.drv' failed

Configure output says:

libxml2 support:           yes

Great :)


Pre-releases having precedence over releases

It seems that pre-releases have precedence over releases, i.e.:
result = satisfying(["1.1.1", "1.1.1-11", "1.1.1-111", "1.1.1-21"], "", output)
self.assertEqual(result, "1.1.1-111")  # Wrong, should be 1.1.1

where satisfying is just a small wrapper of max_satisfying to convert from the strings to SemVer(v, loose=True)
I have had a look to the code, but couldn't figure out a fix. Many thanks!

hmm.

memo
https://gist.github.com/podhmo/3a847bf5f6f97a10f8241fe697d571f0

Yes, you are right, it happens to be part of my expression, I am sorry.
But when I fix it, my tests fail because of this:
wanted = "1.2"
cands =  ["1.1.1", "1.2", "1.1.1-111", "1.1.1-21"]
result = max_satisfying(cands, "<=1.2", loose=True)
assert wanted == result, "result is %s" % result

I can't see in the semver specification the reason of this result. Am I missing something?
Many thanks, and thanks again for this useful library!

in node.js's semver 1.2 is invalid version expression. (implementation is changed)
current node's regexp
/^[v=\s]*([0-9]+)\.([0-9]+)\.([0-9]+)(?:-?((?:[0-9]+|\d*[a-zA-Z-][a-zA-Z0-9-]*)(?:\.(?:[0-9]+|\d*[a-zA-Z-][a-zA-Z0-9-]*))*))?(?:\+([0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?$/

python's one
re.compile('^[v=\\s]*([0-9]+)\\.([0-9]+)\\.([0-9]+)(?:-?((?:[0-9]+|\\d*[a-zA-Z-][a-zA-Z0-9-]*)(?:\\.(?:[0-9]+|\\d*[a-zA-Z-][a-zA-Z0-9-]*))*))?(?:\\+([0-9A-Za-z-]+(?:\\.[0-9A-Za-z-]+)*))?$')

detail
const semver = require('semver');
wanted = "1.2";
cands =  ["1.1.1", "1.2", "1.1.1-111", "1.1.1-21"];
console.log(semver.maxSatisfying(cands, "<=1.2", true))

// TypeError: Invalid Version: 1.2

const semver = require('semver');
wanted = "1.2";
cands =  ["1.1.1", "1.2.0", "1.1.1-111", "1.1.1-21"];
console.log(semver.maxSatisfying(cands, "<=1.2", true)) // 1.2.0

but, python's version is broken.
from semver import max_satisfying
wanted = "1.2"
cands = ["1.1.1", "1.2.0", "1.1.1-111", "1.1.1-21"]
result = max_satisfying(cands, "<=1.2", loose=True)
print(result)  # 1.1.1

fixed, and releasing ver 0.2.0, as soon as.

released

I am testing my codebase with 0.2.0, this issue has been fixed, but now, other tests that were passing for me now are failing, like if the behavior for other cases has been changed too. I am investigating, will report.

thx!

I'm closing this issue.  If new bug is found, could you create another issue.

I am fine with this fix, the tests that were failing where because of some workarounds I had in place, but the new behavior seems correct, not only for the pre-release issue, but also other corner cases have improved too. Thanks again!


Additional tests for "converters" module

Describe the solution you'd like
converters modules contain the core logic of the gateway and as such should be rigorously tested
Describe alternatives you've considered
Test should be done against json taken from transaction service API
Additional context
There are tests also missing for the multisig case that should be addressed see #69

We can probably close this issue after #106 is completed


OpenApi3 and "application/json;charset=UTF-8"

Thanks for you nice work!
We use application/json;charset=UTF-8 and not just application/json as it is assumed in types.d.ts and hence the response data type becomes unknown.
I wonder if it's possible to extend
Fetcher.for<paths>();
to optional
Fetcher.for<paths, 'application/json;charset=UTF-8'>();
and/or
fetcher.path('/xzy').method('get').create();
to optional
fetcher.path('/xyz').method<'application/json;charset=UTF-8'>('get').create();

JSON should always be utf-8 so specifying it as such is redundant. See eg: https://en.wikipedia.org/wiki/JSON#Character_encoding


Rename "cross-origin opener policy" to "opener policy"

As changed here: https://github.com/whatwg/html/pull/10579
As well as renaming our CrossOriginOpenerPolicy, we'll need to update any spec comments that refer to it. That'll involve a lot of looking through the changes in that PR, finding where we implement that part of the spec, and changing the text.

Is this issue still up for grabs?

Sure! Go ahead. :^)

I hope this was what is asked for. Almost forgot to change the comments tho. I looked at the links too, but seems like they haven't been updated and the old links point to the current spec.


It can't work in OS X!!

Hi @shimat .
I check your source codes,and some codes does not support OS X.
So How can I use it for Unity in OS X?
I'm sorry for my poor English.

Sorry but it is difficult to support Unity. Please consider using OpenCV for Unity (https://www.assetstore.unity3d.com/en/#!/content/21088).


feat(electric): Internal API for distributed tracing using OpenTelemetry

This PR adds OpenTelemetry libraries and covers parts of the initial shape sync process with tracing spans.
The E2E setup is modified to run an OpenTelemetry Collector with each test for collecting both client- and server-originating traces and exporting them to Honeycomb.io.
https://github.com/electric-sql/electric/pull/1371 is a follow-up that adds OT support in the client and also implements passing of the tracing context in client-originating RPC requests.

This looks useful!
A question regarding the implementation is if it could cause issues running PRs from external contributors.
The HONEYCOMB secret wouldn't be available, so a solution could be simply running the e2e tests without the OpenTelemetry in those situations.

@davidmartos96 We shall see. I think e2e tests will run fine but nothing will be sent to Honeycomb in such cases.


Fix(adaptor): Lambda@Edge GET/HEAD body error.

This PR addresses the issue where the exception Request with GET/HEAD method cannot have body. is raised when using the GET or HEAD method with Lambda@Edge.
import { Hono } from "hono";
import { handle } from "hono/lambda-edge";
app.get("/", (c, next) => {
    return c.json({}, 200);
});
app.post("/", (c, next) => {
    return c.json({}, 200);
});

export const handler = handle(app);

While POST requests work without any issues, sending a GET request results in an error.
Changes
Made sure that the request does not include a body when the method is GET or HEAD.
Author should do the followings, if applicable

[x] Add tests
[x] Run tests
[ ] yarn denoify to generate files for Deno

@trkbt10
Thanks for the correction. A bun run denoify after review will also resolve the CI

Hi @trkbt10
Thank you for the PR. The code is good! But, CI fails with a "denoify" matter.
The weird thing is that we wrote // @denoify-ignore in src/adapter/lambda-edge/handler.ts, so the code is not generated by the denoify command, so this CI should go through, but it fails.
@trkbt10 Could you run bun run denoify or yarn denoify on your side?

I ran bun run denoify in my local environment, but no errors occurred.
Here is the result:
> bun run denoify
$ rimraf deno_dist && denoify && rimraf "deno_dist/**/*.test.{ts,tsx}"
Denoify is reading sources files from src
Deno distribution will be generated at deno_dist

Additionally, This did not generate any new files or change any files.
If there is anything else I can do, I would be grateful if you could let me know.

@trkbt10
I found that the CI was caused by another issue, fixed it,  and the CI on main is passed.
So, everything is good. I'll merge now. Thanks!


Fix inaccurate language stats on the github repository

Removing noise from your Github language stats

Fixed in the latest commit.


Tool basement

--connection-string --git-repository (optional)
Auto: default brand & branch
Steps:
Blueprint???
Extract
Define
Adjust
Obsolete
Validate
Fix
Generate
Test
Release
After every step - commit
Also: Save command and Reverse
Disable/Enable --autocommit

For Auto:  --target-connection-string --target-host --target-sudouser

Use the last Zoran Horvat example with cancellation token and progress:
Also: consider parallelism to boost extracting and generating large projects. (And we know, that at least one is on the roadmap.)


Windows 10 StylusPressurePlugin.exe error at Utils.cpp line 77

Windows version: 10.0.14393.206

It works fine after I delete this line and rebuild it by visual studio 2015 community version.
My tablet is UGEE cv720 which uses wintab. I think it could be better if listening these two types of signal in one native program.

Fixed and updated the extension f218537e3d4109944d766c7d74d9592d108733c9


Fix sourcemaps for errors that don't contain column information

I stumbled upon a bug where no column number was given in an error which broke the source-maps.
Not sure if using NaN here as a column number is something you guys like and also the changes to the formatting are dubious. Would appreciate suggestion to improve those.

There were the following issues with your Pull Request

Commit: d4f8cb51f7725d1f0aff88695c510f403df66970
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at http://karma-runner.github.io/0.13/dev/git-commit-msg.html

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: 434513abd04e46331200bce3ccfb621ab801216f
Your subject line is longer than 70 characters

Guidelines are available at http://karma-runner.github.io/0.13/dev/git-commit-msg.html

This message was auto-generated by https://gitcop.com

I signed it!

Thanks, I left some comments inline

Changed the formatting, into your suggestion.

Thanks :octocat:


Fix/issue 25 - Created time logs for state changes of experiments

In this PR, whenever the state changes for the experiment (say from inactive to enrolling, from enrolling to enrollment complete, etc) we have added the time logs.

When the user changes the state of the experiment, it keeps track of every transition of state in the DataBase.
On clicking at the Time Logs in the UI, the modal lists transition from enrolling to enrollment-Complete and vice versa for the experiment.

Don't merge the PR, as there are still few enhancements left.

This PR, can now be merged.

@msandbothe @amurphy-cl Before merging this PR, please wait for additional comments from @YashilDepani. There is a non-buggy data inconsistency issue with this PR. Since it not a breaking change and can be fixed later and I can create a new 'extension' issue for that.


Refactor recipient drag and drop code

Contains changes as discussed in PR #2451

Is there a way to copy or edit email address?
Currently I am unable to edit or copy email when compose is opened from other app

It would be great to have the ability to edit or copying address, somehow.
When typing address manually clicking backspace allows for editing, but when compose opened directly with email mailto link, unable to do so

See https://github.com/k9mail/k-9/pull/2451#issuecomment-572222353


[Merged by Bors] - fix: to_additive translates constructors of inductive types

Zulip

maintainer merge

You seem to not be authorized

This is the first time I tried this on mathlib4 iirc, I've been a bit out of the loop recently! Is it intended that mathlib3 reviewers = mathlib4 reviewers right now?

It doesn't work yet on mathlib4. You can post in the maintainer merge thread manually. And indeed, that is the Scott bot.
Since this is a small change, I'll just merge it myself.
bors merge

I'm confused why it doesn't work yet though, the actions seem to be there, and it looks like kevin managed to trigger the bot to post in the reviewer stream the other day :shrug:
sounds good anyways

I'm confused why it doesn't work yet though, the actions seem to be there, and it looks like kevin managed to trigger the bot to post in the reviewer stream the other day 🤷 sounds good anyways

I think that was a manual comment by Yael (that also confused me).


Error running product detail link

I open the browser and delete the cache, then run the product details link as domain.com/iphone-6s-16gb, the application fails.
An unhandled exception occurred while processing the request.
InvalidOperationException: A second operation started on this context before a previous operation completed. Any instance members are not guaranteed to be thread safe.

Please guide me how to fix it. Thank you

The reason I am thinking about is that MediatR handles notification in parallel. https://github.com/jbogard/MediatR/blob/master/src/MediatR/Mediator.cs. To fix this issue, we have to create a class extend Mediator and override the PublishCore method to be something like
protected virtual Task PublishCore(IEnumerable<Task> allHandlers)
        {
            foreach(var handler in allHandlers) {
                    await handler;
            }
        }


Fix style picker in markup modal

Restore correct list of styles to markup modal
DRY lists of styles

Fix #1330

It looks like the page needs to load completely before the preview modal becomes responsive, which makes sense. It doesn't know to prioritize the preview image over the others.

@tooomm Thanks! Could you try it again once this deploys? I ran into a conflict with #1190 which I just resolved.

All good. Also double checked with Chromium and Edge.
I realized that the style-selection gets remembered though... I would expect it to reset back to the default to be honest. But one could consider this behavior a feature as well. :)

Yea, I thought about that. It seems like it'd be annoying to keep picking flat-square if that's what you prefer.

Thanks for the testing!

Also, I spotted that the adjusted link regarding your style choice is altered for all code boxes (like Markdown etc.), but not for the image link itself.
I didn't want to open even another issue regarding such small issues... ;)

I think it is supposed to be that way,
Due to the image being generated from the image link where you insert your own details and custom params

But there probably should also be a direct image link with all the options included.

Then it's a bit confusing in my opinion.
If you shouldn't copy that link there to use it in whatever form to integrate your badge, it should only be labeled custom parameter to allow a simple input of those.
Otherwise image implies that you get the link to the exact image you see/generated at the top.
Actually, I think both are helpful/needed.
This should be related to https://github.com/badges/shields/issues/701 and could be incorporated/tracked there.

Yeah I agree, and once something like #701 is implemented it shouldn't be a problem.
Sent from my iPhone
On 6/12/2017, at 1:02 PM, tooomm <notifications<EMAIL_ADDRESS>wrote:
Then it's a bit confusing in my opinion.
If you shouldn't copy that link there to use it in whatever form to integrate your badge, it should only be labeled custom parameter to allow a simple input of those.
Otherwise image implies that you get the link to the exact image you see/generated at the top.
Actually, I think both are helpful/needed.
This should be related to #701https://github.com/badges/shields/issues/701 and could be incorporated/tracked there.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/badges/shields/pull/1331#issuecomment-349483176, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG82Am_MVjVyL9YwYgFwkhuaTTzljLB_ks5s9dmDgaJpZM4Q2pv2.

Right, I think once we have #701 we won't need that image URL to be editable. I'd be fine adding an image URL display, too, between the style box and the markup.
We could repurpose #1311 to discuss frontend UX tweaks if you'd like.


Feature Request - import bike and swim schedules

I would love to be able to use this to plan my triathlon training.
That means I need to create bike and swim schedules as well as run ones.
Is it in your plans to add that anytime soon?
H

I'll take a look of how difficult is to support bikes and swimming workouts. Until then, the feature request can stay open.

Thanks - is there a 'contribution' link. I think this is a great tool, well worth supporting

The good news is that I've just bought a new MTB bike. So you can expect me to be more involved in the near future. On the other side a became a father a few weeks ago, so my spare time is not that wide any more.

Cycling workouts are supported now. #16 in release 0.2.3


Cdl2020 week2 group4

PR For Group 4 Week 2
Members:
Nick Allgood
Claudio Giampi'
Santanu Ganguly
Pooria Mandai

Your video was certainly the most fun to watch!  Keep up the great work


Controller action not found js request

Controller action not found from js request if the url has the controller name instead of base's url
Example
if url is: http://localhost:5733 -> it work just fine
else if url is: http://localhost:57337/Todo/Index -> action not found

Fixed in the next PR


[AMBARI-22995] Remove deprecated Upgrade Packs

What changes were proposed in this pull request?
Remove upgrade packs and config packs that all adhere to the old upgrade packs.  This is to make way for upgrade pack changes to support the Mpack world.
How was this patch tested?
Unit tests that don't break any more than what was already there in this feature branch.  Many tests were removed which ended up being an improvement of test results.
[ERROR] Tests run: 5027, Failures: 25, Errors: 19, Skipped: 37
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 27:55 min
[INFO] Finished at: 2018-02-14T16:52:58-05:00
[INFO] Final Memory: 100M/1902M
[INFO] ------------------------------------------------------------------------

There's something wrong with this pull request.  Working on a different one.


How to fix general cors error

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Solution 1: Configure the Backend to Allow CORS
Solution 2: Use a Proxy Server
Solution 3: Bypass the Error Using a Browser Extension
Please try this

I got other errors. but I followed your opinion.
please help me

please try on your hosting server
I think you tried on your local pc and this is wrong way

great!
thanks


Downloading empty files

Describe the bug
When I'm trying to download mod13q1 data for India region, receiving empty files.
To Reproduce
Steps to reproduce the behavior:
collection_client = CollectionApi(session=session)
collections = collection_client.query(short_name="MOD13Q1", version="006")
granule_client = GranuleApi.from_collection(collections[0], session=session)
granule_client = GranuleApi.from_collection(collections[0], session=session)
box_coords = [22.29219,103.99219, 24.96439, 105.82031]
custom_granules = granule_client.query(start_date="2020-01-01", end_date="2020-01-31", bounding_box=box_coords)
GranuleHandler.download_from_granules(custom_granules, session)

Expected behavior and actual behavior
Expect to receive hdf files filled with data, in reality receiving files filled with -3000 value.
hdf = SD('MOD13Q1.A2020017.h18v01.006.2020034145702.hdf', SDC.READ)

fig, ax = plt.subplots()
im = ax.imshow(hdf.select('250m 16 days NDVI').get())

Your Environment:

modis_tools version used: 1.1.0

Can't figure out the problem on which side, is it data provider or on modis-tools side.

The output is seems fine to me when corrected for one thing.
Your box coordinates are in wrong format. Try box_coords = [103.99219, 22.29219, 105.82031, 24.96439 ]

Closing this issue as it has become stale. If the recommended fix has not worked, feel free to open a new issue.


HTTP caching of segments

Is there any way to configure HTTP caching of segments in Shaka Player Embedded? If not, is it possible to get some pointers on how this could be implemented?
I'm trying to cater for the use case where a user plays the same content multiple times. By having a HTTP cache, preferably with a configurable size and a LRU eviction algorithm, we might not have to make any network calls for playing content a user has played recently, which would be beneficial for the user experience as playback start up time could be very short.

We don't handle any caching, but that should be something we can add.  If you're interested in adding it, you should look at the NetworkThread and XMLHttpRequest.


Initial release

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
no

Solution Details

Q
A

Solution requires premium license
no

Which connectors are used?
none

Solution uses on-premises connectors?
no

Solution uses custom connectors?
no

What's in this Pull Request?
A new sample power automate flow that shows how to apply XPath expressions on complex JSON structures.

More information can be found here

Power Automate Samples is not active or being monitored.


import information from MalwareBazaar

MalwareBazaar has information about various malware files, including various hashes (md5, sha1, sha256, ssdeep, imphash, tlsh). Though no CVE identifiers are linked it is an easy to process data format (CSV, with only very little cleanup needed) and it might be useful to import.
https://bazaar.abuse.ch/export/

As a template or inspiration please look at:
https://github.com/armijnhemel/binaryanalysis-ng/blob/master/maintenance/database/malwarebazaarimporter.py
https://github.com/armijnhemel/binaryanalysis-ng/blob/master/maintenance/database/README-malwarebazaar.md
(and no, don't worry about the license or creating a derivative work)


Run Arduino build process as a nightly CI action

This repository doesn't have any automated Arduino build checking. The source repo at https://github.com/tensorflow/tflite-micro does however, so I think it would be useful to port those scripts over here.

We have nightly and nightly and per PR checks: https://github.com/tensorflow/tflite-micro-arduino-examples/blob/main/.github/workflows/ci.yml
And the build badge from tflite-micro points to the nightly build from this repository.


Update aws-java-sdk-core to 1.12.556

About this PR
📦 Updates com.amazonaws:aws-java-sdk-core from 1.12.459 to 1.12.556
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #625.


No force layout of superview and contentSize recalculation if intrinsicContentSize not changed

Test Plan:
No need test.
Release Notes:
[IOS][ENHANCEMENT][RCTRootView] - No force layout of superview and contentSize recalculation if intrinsicContentSize not changed

I verified the original change that added this and I think it makes sense to move it up.


nfs-kernel-server.service appears "stopped"

I've noticed recently that the Puppet agent running on our NFS server nodes seems to think that nfs-kernel-server.service is not running, even though it is.  We're seeing this output from the agent each time it runs:
Notice: /Stage[main]/Nfs_server_exports/Service[nfs-kernel-server.service]/ensure: ensure changed 'stopped' to 'running' (corrective) Info: /Stage[main]/Nfs_server_exports/Service[nfs-kernel-server.service]: Unscheduling refresh on Service[nfs-kernel-server.service]
It doesn't look like anything actually happens though (there's no service restart as far as I can see).  I should say that this is also happening on our machines with a different, unrelated service.  So maybe it's not specific to the puppet-nfs module.   We are running Puppet Server 6.3.0, Puppet agent 6.4.0, on Debian 9.9.
This isn't a big problem, just thought it might be worth reporting.

Hey, thanks for the report.
Can you please add an info about the used version of this module?

Yes, sorry - we're using derdanne-nfs v2.1.2.
(Our Puppet server version is 6.3.0, the agent version is 6.4.2;  both are running on Debian 9.9).

Sorry, i could not reproduce this behaviour. Please reopen, when this issue is directly related to this module.


feat: acquit classes that are part of the project itself

If sbom parameter is passed, we get the root component from there and include that in our fingerprints.

We cannot detect the internal java classes until the SBOM tells us something about the java version. Thus, we need to hardcode some packages that be passed through even thought they have not been fingerprinted.


Add unpack function to archive module.

Add a helper function to unpack archives using 7zip. It supports a variety of archive formats by default: https://www.7-zip.org/

@hacktobeer PTAL.
Also, do we need to add 7z to the Dockerfile or is it installed by default?

Thanks for comments, PTAL.
Yes, we need 7zip in the container that wants to use this function. The PR in the plaso worker (adding task ExtractArchive) has 7z added to the Dockerfile, I can do the other containers after. I also added a check to the beginning of the function to see if it is available.

Yeah, let's add it to the template later.


feat: allow configuring cluster domain and use FQDN for upstream service targets

What this PR does / why we need it:
Make service upstream targets use FQDN with default cluster.local domain.
Add cluster-domain to allow changing this default.
Which issue this PR fixes:
Related to #6658
Special notes for your reviewer:

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

I believe this could be a breaking change for people who use a custom cluster domain, no? Shouldn't we introduce this as an optional parameter and only use the FQDN when it's set?

Yes, that's correct, thanks for catching that. To remediate that we can keep the implementation as is but just make the default an empty string and create an issue in 4.0 to change it to cluster.local. WDYT?

Yes, that's correct, thanks for catching that. To remediate that we can keep the implementation as is but just make the default an empty string and create an issue in 4.0 to change it to cluster.local. WDYT?

Yeah, that would make sense perhaps. I thought also about another proposal - we could do a DNS query on the KIC side to get the FQDN of the service and not require any configuration even if a custom domain is used, WDYT?

I thought also about another proposal - we could do a DNS query on the KIC side to get the FQDN of the service and not require any configuration even if a custom domain is used, WDYT?

Would it be something like proposed in https://github.com/Kong/kubernetes-ingress-controller/issues/6658#issuecomment-2488637301 or something else? If that's it then I'd say it's something that we can cover separately and just implement #6658 with what's currently in scope of this PR. WDYT?

Would it be something like proposed in #6658 (comment) or something else? If that's it then I'd say it's something that we can cover separately and just implement #6658 with what's currently in scope of this PR. WDYT?

If we intend to implement the automatic way eventually, we may as well do it now to avoid introducing an additional configuration knob and removing it in the future, no?
I'm also fine with leaving it a flag altogether and not aiming to implement the automatic way in the future. I believe only one approach should be picked here.

If we intend to implement the automatic way eventually, we may as well do it now to avoid introducing an additional configuration knob and removing it in the future, no?
I'm also fine with leaving it a flag altogether and not aiming to implement the automatic way in the future. I believe only one approach should be picked here.

👍 I'm fine with this approach. How about adding the automatic domain detection for the default flag value "", with a fallback in case of an error to empty cluster domain ( current status quo). When this flag is non empty then that value is used as cluster domain.
The latter of those 2 would change to cluster.local in 4.0 while the flag default would be kept as "" to keep the automatic domain detection on but with a new fallback value. WDYT?

I meant that we should rather go with the flag (as proposed, but default to an empty string before 4.0) OR implement the automatic detection and not introduce the flag at all (if the query fails, we could fall back to the current approach with no FQDN). Introducing both sounds like an overkill to me TBH.

ACK. I think (but I can be persuaded otherwise) that implementing the automatic detection without the possibility to set a concrete value might be limiting to some (that specifically want this to be set to a concrete value). WDYT?

I'm not sure what the background of this issue is (is it something a customer reported?), but if it's only to limit DNS queries on the proxy path, then I believe the automatic resolution of the FQDN at configuration time should satisfy it. Why would someone want to set it to anything different?

Why would someone want to set it to anything different?

I'm not sure but I do not want to put ourselves into a corner, needing to make a breaking change in the future to extend this.
Touching on the offline discussion we had on Slack: let's move forward with the option currently in this PR to have a flag that sets the domain, with the same value as we currently have for default: cluster.domain.
This PR is ready for review now.


Clarify Pantheon provider documentation for D6/7

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

Thanks for paying careful attention to this.


[NFR] Add redis queue adapter to replace beanstalkd

A noted in phalcon/cphalcon#13364 beanstalkd (may) be removed from phalcon in 4.0. I propose adding a redis queue adapter in place of beanstalkd. Otrher frameworks like Laravel have redis queue adapters and redis is well maintained (apart from on windows). For acheiving queues on redis RPOPLPUSH is recommended.
Proposed version: 4.0

Awkwardly enough this nfr is 6y old. Would love to try myself by contributing here, but contributing guidelines left me clueless. What would be your idea to execute this functionality. How should I proceed, to contribute in a good fashion way, allowing you to easily pull and publish?

Contributing to Phalcon (in general) is reasonably easy. All you will need is to ensure that there is an issue behind your contribution, whether this is a bug or a NFR etc. If it is a big piece of functionality such as a NFR, you can ping us on discord to discuss the implementation and then it will be up to you. The reason for that is we do not want to overload the framework with stuff that people would never use (been there done that), plus it is good to align how the framework will evolve with new functionality.
If you wish, send me a message on discord and we can discuss how to address this.
Finally, setting up an environment locally to work on phalcon only requires docker so it is quite simple.


fix typos

Fixes minor errors in comments and docs. Specifically, this commit corrects "Futhermore" to "Furthermore" and adds a comma after uses of "Furthermore" as an introductory phrase.

Thanks @m-vz


V2 of waitForStateCompletion API using synchronous update feature

The current implementation uses a sub workflow: https://github.com/indeedeng/iwf/pull/345  requires to provide WaitingForCompletionStateExecutionIds on starting workflow which is cumbersome to use. It's required because we want minimize the initiation of these sub workflows as optimization.
Additionally, it's not efficient because of the overhead of starting/signaling another workflow. It consume quite a lot of actions
A better way is:

Extend the stateExecutionCounter to track the completed state executionId
Use synchronous update with workflow.Await( ()-> stateExecutionCounter.stateExecuctionCompleted(stateExeId) ) in the handler to wait for the execution

Note that continueAsNew need to be handled properly:

In validator, it should check if the workflow has met continueAsNew threshold. If so, then return error
In the workflow.Await(...) should also check continueAsNew threshold to return error so that workflow can do a continueAsNew
The API service need to retry when continueAsNew interrupts the waiting
returning state completion output will not be supported

Also, it doesn't allow reuse workflowId for different executions, because of the RunID issues in Temporal. This v2 can solve the problems
Note that sync update feature is not prod ready in Temporal yet. We will start working on it when it is ready.

Above solution is really complicated to implement, a better workaround is https://github.com/indeedeng/iwf/issues/404

Implement waitForKey will need some trick to prevent too much data stored in workflow — probably start an empty workflow when the state is completed — the workflow just completes immediately after started. It will be used as a record for service api to check if the state execution is completed


Add type_caster classes for xt::xtensor, xt::xarray, and xt::xexpression.

They enable casing ndarray to xt::xexpression<xt::pyarray> and casing xt::xarray to ndarray.
With the following code,
struct Foo
{
  xt::xtensor<double, 1> x;

  template<class X>
  void set(const xt::xexpression<X> &x_)
  {
    x = x_.derived_cast();
  }

  xt::xtensor<double, 1>& get(void)
  {
    return x;
  }
};

py::class_<Foo>(m, "Foo")
  .def(py::init<>())
  .def("set", &Foo::set<xt::pyarray<double>>)
  .def("get", &Foo::get, py::return_value_policy::reference_internal);

the Foo.x can be modified from python as follows:
foo = Foo()
foo.set(np.array([1,2,3,4]))
x = foo.get()
print(foo.get())  # -> [ 1.  2.  3.  4.]
x[0] = 100
print(foo.get())  # -> [ 100.    2.    3.    4.]

Thanks @yoshipon, we really like this solution.

The main remark is about code formatting. Our convention is the following
Regarding formatting, here is the current convention:
namespace bar
{                                               // indent in namespace
    class Foo
    {                                           // new line before {
    public:
                                                // empty line after public /  private / protected
         Foo();
    };

    Foo::Foo()
    {
    }
}                                               // no use of PYBIND macros for NAMESPACE_END NAMESPACE_BEGIN

@yoshipon Not sure about that, but the errors may be due to the fact that we don't use the same versions of pybind11 (xtensor-python expects `pybind11 2.1.1).

@yoshipon Not sure about that, but the erros may be due to the facts that we do not use the same versions of pybind. The CI (travis and appveyor) install pybind11 2.1.1, which is not the last version of pybind.

@JohanMabille Exactly, my code could not be compiled with pybind11 2.1.1 due to the following two reasons:

move_cast_op_type does not exist
strides and shape have to be std::vector<size_t> (std::array was not supported yet)

I fixed these bugs.
However, even now there are several problems on Travis CI, I'm still working for debugging.

The Travis CI errors seem to be coming from the new miniconda that was released yesterday.
Downloading Miniconda2-4.3.21-Linux-x86_64.sh instead of latest might solve the issue.

@SylvainCorlay Thank you for the information. I re-pushed with a modified .travis.yml.

Success!
For your information, I have reported the issue in the new miniconda build.

Merging :tada: congrats on your first PR into xtensor!

@yoshipon regardin the xtensor/xarray to ndarray cast, one thing that we will probably try to do before the next release is not make use of pybind11::array, and use xt::pyarray instead.
It should probably be a matter of adding a constructor to xt::pyarray that is optimized in that it would reuse the buffer of xtensor/xarray.

@SylvainCorlay Thank you very much! Actually, this is my first PR. It was very impressive.
btw, it is a good idea. The current type_caster specifically for xarray/xtensor is not the best way.
With this extension, it will be more simplified.


Refactoring of Pruning Techniques in CostBasedRegionPlanGenerator

This PR refactors the current implementation of the two pruning techniques for the bottom up search framework:

Moved the code related to calculating chains and bridges outside of PhysicalPlan
Replaced method calls to getting chains/bridges with class variables to avoid repeated computation during search
Refactored bottom-up search's API to allow specifying different search parameters
Refactored bottom-up search's implementation to make different steps during the search clearer

General comments, although this is mainly refactoring,

we need some test cases to understand and test those optimizations. Otherwise, it is hard to know if it is effective or if the refactoring is correct. You need to at least unit test each function, e.g., getMaxChains, getBridges.
try to break huge functions. for example, the current RPGSearchPruningUtils.getMaxChains contains more than 10 levels of indentation, and more than 40 lines of code. try to flatten it, and use some helper functions to make it more readable.

And also, to avoid two copy issue with PhysicalPlan due to the other refactoring, can we avoid modifying physical plan for now?


Add a command that validators can use to see how much votes they need to get elected

Expected Behavior
Command that outputs the number of votes and shows validators in order.
Current Behavior
They can use election:run, but this doesn't show the number of votes, and it just shows the groups in order, not validators.

Closing due to age and no engineer willing to shepherd it over the line.


.travis.yml: skeleton for deployment to pypi

Coverage remained the same at 62.069% when pulling 56bc511df861dd2343f86e67809351cf9c6c2bda on kdebrab:master into 917f5115b1c75005eee5fd7decdf6fc3dd259206 on opengridcc:master.


Add mc

https://github.com/aquaproj/aqua-registry/issues/858

Duplicated https://github.com/aquaproj/aqua-registry/issues/880


UI Type checks for build

Fix type errors for prod building (npm run build)
Add type checking to CI

@vishnoianil double check knowledge/route submission at your leisure. Had to change them to pass type checking. Ty!

@vishnoianil double check knowledge/route submission at your leisure. Had to change them to pass type checking to get prod built. Ty!

@nerdalert tested skill/knowledge both, looks good.


added a getter method for the memoryStream property on TimeWeightedVectorStoreRetriever

Added a getter method so that we can access the memoryStream property on instances of the TimeWeightedVectorStoreRetriever class
I'm trying to port over the following experimental abstractions from the python library: GenerativeAgentMemory and GenerativeAgent. I'm essentially translating the python classes outlined here and here into typescript. However, I'm running into a problem when I want to access the memoryStream property on memoryRetriever: TimeWeightedVectorStoreRetriever as shown in the python implementation:
class GenerativeAgentMemory(BaseMemory) {
  #only relevant code shown

  memory_retriever: TimeWeightedVectorStoreRetriever
  """The retriever to fetch related memories."""

  def _get_topics_of_reflection(self, last_k: int = 50) -> List[str]:
        """Return the 3 most salient high-level questions about recent observations."""
        prompt = PromptTemplate.from_template(
            "{observations}\n\n"
            + "Given only the information above, what are the 3 most salient"
            + " high-level questions we can answer about the subjects in"
            + " the statements? Provide each question on a new line.\n\n"
        )
        observations = self.memory_retriever.memory_stream[-last_k:] #private property memory_stream is accessed
        observation_str = "\n".join([o.page_content for o in observations])
        result = self.chain(prompt).run(observations=observation_str)
        return self._parse_list(result)
}

However, when I try to implement the getTopicsOfReflection function in ts I get the following error because memoryStream is actually private:
Property 'memoryStream' is private and only accessible within class TimeWeightedVectorStoreRetriever.ts(2341)
This is why I've added .getMemoryStream to the TimeWeightedVectorStoreRetriever class -- so that we can access this property and work with generative agents in js/ts

my twitter by the way :) @dxlantxch

Hey @dylanintech, could you try rebasing this PR?

Looks like this will be part of #1489 - will close this and merge as part of that one!

Hey @dylanintech, could you try rebasing this PR?

Sorry, didn't see this! I know the issue is closed but is there still something weird going on with the diff?

This is what it looks like on my end - I'm taking a look at your other one now!

Alright I think what happened is that as I had to pull a lot of changes from origin to get my branch up to speed with the most recent version of the main branch, so it bulked a ton of commits with the actual changes I made.


posible bug deallocating memory

A toy stack implementation crashes when using rpmalloc not with default new/delete.
Link with the example: https://pccito.ugr.es/bug.txz

Running it with N=1 seems to work just fine
Running it with N>1 is unsafe since your stack class is not thread safe. In this case rpmalloc is not to blame for any issues.

In my computer the program fails with the following stack trace... just trying to be helpful with your project :)
(gdb) bt
#0  _memory_span_list_doublelink_remove (head=,
span=0x7efe735f0000) at rpmalloc/rpmalloc.c:736
#1  _memory_deallocate_to_heap (heap=0x7efe747e6000, span=0x7efe735f0000,
p=0x7efe735f0040) at rpmalloc/rpmalloc.c:1133
#2  0x0000000000402dd5 in operator delete (ptr=0x7efe735f0040)
at rpmalloc/new.cc:116
#3  0x00000000004025b8 in stack::pop (this=0x409258 ) at stack.h:29
#4  stack::~stack (this=0x409258 , __in_chrg=)
at stack.h:15
#5  0x00007efe742426c0 in __run_exit_handlers () from /lib64/libc.so.6
#6  0x00007efe74242800 in exit () from /lib64/libc.so.6
#7  0x00007efe7422bf3a in __libc_start_main () from /lib64/libc.so.6
#8  0x000000000040238e in _start () at stack.h:13

Looks like your stack object destructor is being run in the global exit handler, which could potentially be run after the rpmalloc finalization has occurred. You need to take care with global data to ensure memory is deallocated before the allocator has finalized.

ok, thank you for your help.
I can correct my code but the problem was not very obvious...
Any way to avoid this problem with global objects?
How can we assure rpmalloc finalization is called at the right time?

When the stack is local in main the problem still exists...
Core was generated by `./stack'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  _memory_span_list_doublelink_remove (head=,
span=0x7f76113f0000) at rpmalloc/rpmalloc.c:736
736			prev_span->next_span = next_span;
(gdb) bt
#0  _memory_span_list_doublelink_remove (head=,
span=0x7f76113f0000) at rpmalloc/rpmalloc.c:736
#1  _memory_deallocate_to_heap (heap=0x7f76125b9000, span=0x7f76113f0000,
p=0x7f76113fe840) at rpmalloc/rpmalloc.c:1133
#2  0x0000000000402d05 in operator delete (ptr=0x7f76113fe840)
at rpmalloc/new.cc:116
#3  0x000000000040233a in stack::pop (this=0x7ffe6154fba0) at stack.h:36
#4  stack::~stack (this=, __in_chrg=)
at stack.h:19
#5  main () at stack.cc:42

Code available at https://pccito.ugr.es/bug2.zip

I can't seem to reproduce the error, works just fine here on both Linux and Windows systems

In your original makefile you had transactional memory, I'm not sure rpmalloc is compatible with that as I've never used that extension.
Also, to me your makefile is missing c++ standard declaration in order to make it compile successfully, which indicates to me you're compiling with some other flags than what the makefile indicates?

Here is a copy of the binaries: https://pccito.ugr.es/bug2.zip
I use Fedora 30.

bug is random... I can trigger it in a loop


Find next or previous error

Implements #97

Thanks JJK96. I think this PR needs to be rebased or squashed.

Done

Thank you for implementing this! Unfortunately, I'm not good at shell scripting to do thorough review, but I tested it and it works well.
Few improvements which would be nice to have as a part of this feature:

Fix typo in the docstring: "pervious".
Add command description to the README.
Add command as a subcommand of lsp command.
Add bindings for both next and previous error to lsp user mode.

Last two things are still not documented, but good to keep them up-to-date now, and I'm going to document them for the next release.

Thank you for implementing this! Unfortunately, I'm not good at shell scripting to do thorough review, but I tested it and it works well.
Few improvements which would be nice to have as a part of this feature:
1. Fix typo in the docstring: "pervious".

2. Add command description to the README.

3. Add command as a subcommand of `lsp` command.

4. Add bindings for both next and previous error to `lsp` user mode.

Last two things are still not documented, but good to keep them up-to-date now, and I'm going to document them for the next release.

Thank you for implementing this! Unfortunately, I'm not good at shell scripting to do thorough review, but I tested it and it works well.
Few improvements which would be nice to have as a part of this feature:
1. Fix typo in the docstring: "pervious".

2. Add command description to the README.

3. Add command as a subcommand of `lsp` command.

4. Add bindings for both next and previous error to `lsp` user mode.

Last two things are still not documented, but good to keep them up-to-date now, and I'm going to document them for the next release.

Fixed these things

I've made a thorough review about POSIX compliance and it just disappeared LOL
I remade all the comments.

Probably your git wasn't fully up to date

Maybe...
It's because of those things that I find more and more fond of email-based patch reviews.

@skrps thanks for the detailed code review

Big thanks to everyone involved in the review! Is PR ready to merge? What's left otherwise (i.e. echo -> printf replacement)?
Btw, I'm using echo in few other places in lsp.kak, should it be replaced? And in general, I'd be grateful for lsp.kak review, feel free to raise issues/PRs if you notice any non-portable or non-safe stuff.

Some things pointed out by @skrps still need to be applied, i.e. unnecessary quoting, printf instead of echo. I can do that tomorrow.

I'm using echo in few other places in lsp.kak, should it be replaced?

Depends on what you're using variables when calling echo.
I can review the shell script portions of lsp.kak; I should raise a PR soon if need be.


Google phishlets work perfectly fine.

          **Google phishlets work perfectly fine.**

You do not need anything fancy or evilpuppet. You can even just extract the necessary data via custom js per the official documentation, that's why Kuba put it there. There is no need to use all of extra tools or even the pro version. Google rolled out the new v3 login, I highly doubt they patch it or change it anytime soon. (Look at v3 release notes & recaptcha notes).
https://cloud.google.com/recaptcha/docs/release-notes
Google phishlets for Evilginx 3.0 work fine. Google sign-in redirects instantly to myaccount as normal, even switching apps will not prompt re-authentication via the main account.

Originally posted by @simplerhacking in https://github.com/kgretzky/evilginx2/issues/1094#issuecomment-2276917924

https://github.com/kgretzky/evilginx2/issues/1094#issuecomment-2278669847

@rickyrik001 You are vastly incorrect.
This is outside of your depth of understanding. How could "some accounts work" and "other accounts not work" that logically doesn't even compute. The idea that some accounts would work with a Google phishlet while others wouldn't is inconsistent with how Google's infrastructure is built. Google's authentication mechanisms, particularly Oauth 2.0, are standardized across their services, ensuring that all accounts follow the same authentication flow. Any deviation would lead to significant issues across their suite of applications.
Google phishlets operate at the network level, capturing and proxying traffic without needing to emulate full browser behaviors. "Puppeteer" obviously doesn’t solve the core issues related to phishlets, such as intercepting and parsing OAuth flows or managing cookies, which are obviously critical to capturing credentials. Therefore, your magical claims make zero sense both logically and technically.
Please refrain from spreading misinformation and attempting to present yourself as knowledgeable when this topic so clearly exceeds your expertise. Public forums are for learning and sharing accurate information, not for misleading others for financial or reputational gain.
Also you're not included in BreakDev Red, the private Discord, you do not have an Evilginx Pro license or have access to EvilPuppet or anything Kuba has put out privately for red teamers.
Please try again lol.

@simplehacking i think you haven't watch that last tweet by kuba in which he is using evilPuppet for intercepting request (https://x.com/mrgretzky/status/1808468862058295631) =)

@simplehacking the response i gave on last issue was about App or browser is not secured because of google anti phishing protection , but about reCAPTCHA i haven't write any thing ,and about the issue of App or browser is not secured for that you have to use some sort of hidden browser which replace original request for that you can use go/rod, evilpuppet or anything ,kuba also explained this in his status link attached (https://x.com/mrgretzky/status/1808468862058295631) and make your course public and free so that other people can benefit for it ,as paid version of kuba is already available =)

This guy is a well-known scammer like the gypsy scum on telegram selling fake phishlets for thousands of dollars.  Just a bunch of AI generated powerpoint slides being read verbatim by an AI voice.
Bypassing Google v3 reCAPTCHA is tricky but not impossible. Every site that uses it has a sitekey which is easy to find in html of their login page. That site key corresponds to a 'co' parameter which is a base64 encoded string of the of the actual sites domain 'www.example.com:443'. When you proxy a site you also proxy it's site key. However, your 'co' parameter will not match the site key since your domain is 'www.example-fake.com:443'. You have to figure out a way to modify all requests to Google's recaptcha site to make it seem like they're coming from the actual site. This will send the matching 'co' parameter which will result in google sending back a successful reCAPTCHA token.
I have had mixed success with bypassing this. For some sites i can just use js_inject to modify the html of the login page so that the reCAPTCHA iframe's src url for the request to google contains the actual site's 'co' parameter instead of the fake one. Other website though seem to send continuous requests to the Google reCAPTCHA api at set intervals and the second one get through that uses the fake site's 'co' parameter the reCAPTCHA fails.

@simplehacking ...

It seems that the solution to this is modifying core/http_proxy.go and updating the GET queries directly for them to contain the right base64 encoded string.

@simplehacking ...

It seems that the solution to this is modifying core/http_proxy.go and updating the GET queries directly for them to contain the right base64 encoded string.
Solution is being described here: https://github.com/An0nUD4Y/Evilginx2-Phishlets/blob/master/README.md#google-recaptcha-bypass-by-desire

@simplehacking ...

It seems that the solution to this is modifying core/http_proxy.go and updating the GET queries directly for them to contain the right base64 encoded string.
Solution is being described here: https://github.com/An0nUD4Y/Evilginx2-Phishlets/blob/master/README.md#google-recaptcha-bypass-by-desire

It doesn't work for me. It seems like any time I modify http_proxy.go the changes never work. The solution doesn't make sense anyway. You have to replace the co parameter values with the actual domain and the phishing domain of the phishlet you're currently using. Why would you modify source code with hardcoded values for the co parameter so that it only applies to a single phishlet? If you're going to modify http_proxy.go, instead of hardcoding the co parameters, the function should base64 encode the actual domain(https://www.example.com:443) and the phishing domain(https://www.example-fake.com:443) dynamically. Someone familiar with GO should modify the function and share. Sadly my knowledge of GO is next to non-existent.
I'm not completely useless though! Since the co parameters need to be overwritten on a per-phishlet basis it makes more sense  to do so using js_inject(see below). I have not been able to bypass greCAPTCHA v3 with this but i have been able to replace the co parameter. As a result the greCAPTCHA iframe should load on the page with the recaptcha logo instead of the sitekey error message.  However, even with replacing the co parameter I still get an 'invalid recaptcha' error when submitting log in. I have no clue what's going on though or how to reach the final endpoint. It's either detecting that the co parameter has been re-written or it's comparing the co parameter to the actual header If the case of the latter we'd have to modify our js_inject to not only replace the co parameter but also the request headers. so that they appear to be coming from the original domain. As far as I know, evilginx is not capable of rewriting http request headers.
Someone smarter than me is going to have to take it from here. Hit me up on telegram if want to talk more @thuggish_ruggish_bone. Don't try and sell me anything.
  document.addEventListener('DOMContentLoaded', function() {
      // Function to modify the co parameter in the reCAPTCHA iframe's src
      function modifyRecaptchaCoParam(iframe) {
          if (iframe && iframe.src) {
              let modifiedSrc = iframe.src.replace('<phishing_co_parameter>', '<original_co_parameter>');
              if (iframe.src !== modifiedSrc) {
                  iframe.src = modifiedSrc;
                  console.log('ReCAPTCHA src modified:', modifiedSrc);
              }
          }
      }
      // MutationObserver to monitor the entire document for new or modified iframes
      let observer = new MutationObserver(function(mutations) {
          mutations.forEach(function(mutation) {
              mutation.addedNodes.forEach(function(node) {
                  if (node.tagName === 'IFRAME' && node.src.includes('recaptcha/api2/')) {
                      modifyRecaptchaCoParam(node);
                  }
              });
              if (mutation.target.tagName === 'IFRAME' && mutation.target.src.includes('recaptcha/api2/')) {
                  modifyRecaptchaCoParam(mutation.target);
              }
          });
      });
      // Start observing the document for changes
      observer.observe(document.body, { childList: true, subtree: true, #attributes: true });
      // Modify the co parameter for any existing reCAPTCHA iframe
      document.querySelectorAll('iframe[src*="recaptcha/api2/"]').forEach(modifyRecaptchaCoParam);
  });

@simplehacking ...

It seems that the solution to this is modifying core/http_proxy.go and updating the GET queries directly for them to contain the right base64 encoded string.
Solution is being described here: https://github.com/An0nUD4Y/Evilginx2-Phishlets/blob/master/README.md#google-recaptcha-bypass-by-desire

@simplehacking ...

It seems that the solution to this is modifying core/http_proxy.go and updating the GET queries directly for them to contain the right base64 encoded string.
Solution is being described here: https://github.com/An0nUD4Y/Evilginx2-Phishlets/blob/master/README.md#google-recaptcha-bypass-by-desire

It doesn't work for me. It seems like any time I modify http_proxy.go the changes never work. The solution doesn't make sense anyway. You have to replace the co parameter values with the actual domain and the phishing domain of the phishlet you're currently using. Why would you modify source code with hardcoded values for the co parameter so that it only applies to a single phishlet? If you're going to modify http_proxy.go, instead of hardcoding the co parameters, the function should base64 encode the actual domain(https://www.example.com:443) and the phishing domain(https://www.example-fake.com:443) dynamically. Someone familiar with GO should modify the function and share. Sadly my knowledge of GO is next to non-existent.
I'm not completely useless though! Since the co parameters need to be overwritten on a per-phishlet basis it makes more sense to do so using js_inject(see below). I have not been able to bypass greCAPTCHA v3 with this but i have been able to replace the co parameter. As a result the greCAPTCHA iframe should load on the page with the recaptcha logo instead of the sitekey error message. However, even with replacing the co parameter I still get an 'invalid recaptcha' error when submitting log in. I have no clue what's going on though or how to reach the final endpoint. It's either detecting that the co parameter has been re-written or it's comparing the co parameter to the actual header. In the case of the latter we'd have to modify our js_inject to not only replace the co parameter but also the request headers so that they appear to be coming from the original domain. As far as I know, evilginx is not capable of rewriting http request headers.
Someone smarter than me is going to have to take it from here. Hit me up on telegram if want to talk more @thuggish_ruggish_bone. Just don't try and sell me anything.
  document.addEventListener('DOMContentLoaded', function() {
      // Function to modify the co parameter in the reCAPTCHA iframe's src
      function modifyRecaptchaCoParam(iframe) {
          if (iframe && iframe.src) {
              let modifiedSrc = iframe.src.replace('<phishing_co_parameter>', '<original_co_parameter>');
              if (iframe.src !== modifiedSrc) {
                  iframe.src = modifiedSrc;
                  console.log('ReCAPTCHA src modified:', modifiedSrc);
              }
          }
      }
      // MutationObserver to monitor the entire document for new or modified iframes
      let observer = new MutationObserver(function(mutations) {
          mutations.forEach(function(mutation) {
              mutation.addedNodes.forEach(function(node) {
                  if (node.tagName === 'IFRAME' && node.src.includes('recaptcha/api2/')) {
                      modifyRecaptchaCoParam(node);
                  }
              });
              if (mutation.target.tagName === 'IFRAME' && mutation.target.src.includes('recaptcha/api2/')) {
                  modifyRecaptchaCoParam(mutation.target);
              }
          });
      });
      // Start observing the document for changes
      observer.observe(document.body, { childList: true, subtree: true,  attributes: true });
      // Modify the co parameter for any existing reCAPTCHA iframe
      document.querySelectorAll('iframe[src*="recaptcha/api2/"]').forEach(modifyRecaptchaCoParam);
  });

Other issue that most people encounter is google anti phishing protection, After enter email it will show Browser or App may not be secured

To Bypass this issue you have to tweak Post Request,you can use EvilPuppet or any other tool that uses Puppeteer in the background to capture and stream HTML content to a target browser.

@simplehacking the response i gave on last issue was about App or browser is not secured because of google anti phishing protection , but about reCAPTCHA i haven't write any thing ,and about the issue of App or browser is not secured for that you have to use some sort of hidden browser which replace original request for that you can use go/rod, evilpuppet or anything ,kuba also explained this in his status link attached (https://x.com/mrgretzky/status/1808468862058295631) and make your course public and free so that other people can benefit for it ,as paid version of kuba is already available =)

This guy is a well-known scammer like the gypsy scum on telegram selling fake phishlets for thousands of dollars.  Just a bunch of AI generated powerpoint slides being read verbatim by an AI voice.
Bypassing Google v3 reCAPTCHA is tricky but not impossible. Every site that uses it has a sitekey which is easy to find in html of their login page. That site key corresponds to a 'co' parameter which is a base64 encoded string of the actual sites domain 'www.example.com:443'. When you proxy a site you also proxy it's site key. However, your 'co' parameter will not match the site key since your domain is 'www.example-fake.com:443'. You have to figure out a way to modify all requests to Google's recaptcha site to make it seem like they're coming from the actual site. This will send the matching 'co' parameter which will result in google sending back a successful reCAPTCHA token.
I have had mixed success with bypassing this. For some sites i can just use js_inject to modify the html of the login page so that the reCAPTCHA iframe's src url for the request to google contains the actual site's 'co' parameter instead of the fake one. Other website though seem to send continuous requests to the Google reCAPTCHA api at set intervals and the second one get through that uses the fake site's 'co' parameter the reCAPTCHA fails.

totally agreed with @stackerofwheat ,the guy @simplerhacking is scammer

          **Google phishlets work perfectly fine.**

You do not need anything fancy or evilpuppet. You can even just extract the necessary data via custom js per the official documentation, that's why Kuba put it there. There is no need to use all of extra tools or even the pro version. Google rolled out the new v3 login, I highly doubt they patch it or change it anytime soon. (Look at v3 release notes & recaptcha notes).
https://cloud.google.com/recaptcha/docs/release-notes
Google phishlets for Evilginx 3.0 work fine. Google sign-in redirects instantly to myaccount as normal, even switching apps will not prompt re-authentication via the main account.

Originally posted by @simplerhacking in #1094 (comment)

How did you come to this?

Okay

telegram https://github.com/kgretzky/evilginx2/issues/1119

Reached to a conclusion yet? :)

stop wasting your time check this group on telegram https://t.me/nextgenerationphishing


Add nested example

I think it would be nice to have this example separated from the backend changes required to make it work

Superseded by #99


Ignore access denied on HcsTerminateProcess

When calling HcsTerminateProcess on a process that has exited, but we still have open handles to, an ERROR_ACCESS_DENIED may be returned.
https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminateprocess#remarks
Fixes: https://github.com/microsoft/hcsshim/issues/1251

This looks good to me; though I am not sure why TestPseudoConsolePowershell is timing out.
Can you try revendoring tests and push again?
@dcantah, thoughts?

This looks good to me; though I am not sure why TestPseudoConsolePowershell is timing out. Can you try revendoring tests and push again? @dcantah, thoughts?

That one is addressed by: https://github.com/microsoft/hcsshim/pull/1253

@helsaawy My assumption for how long powershell should take to launch and execute one command was off hahah https://github.com/microsoft/hcsshim/pull/1253 Here's a "fix"

Oop @gabriel-samfira beat me to it

make sure to cd test && go mod vendor and repush.

make sure to cd test && go mod vendor and repush.

done! Thanks!

@dcantah @jsturtevant do you know whether we can pick this fix in docker?

@dcantah @jsturtevant do you know whether we can pick this fix in docker?

Rather than this PR, I suggest looking at: https://github.com/microsoft/hcsshim/pull/1275
Actually, I would suggest to have a look at all the fixes merged in 0.9.2: https://github.com/microsoft/hcsshim/releases/tag/v0.9.2
if those fixes are not currently present in docker.


bigquery can't access

The trust certificate obtained according to the guide is a trust certificate for your own GCP, not for public access to projects.

Hi,
bigQuery-public-data is publicly accessible to all users. As long as you have created an account, you can access them directly.
What issues have you encountered?

Sorry, I modified the external certificate file but forgot to update the certificate file in the internal examples, which caused the error.


[docs] Fix type in website/docs/engine-flink/ddl.md

Purpose
Fix typo in docs.

Tests

API and Format

Documentation

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