Bug: routes not work in ci 4.3.5

PHP Version
7.4
CodeIgniter4 Version
4.3.5
CodeIgniter4 Installation Method
Composer (using codeigniter4/appstarter)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
No response
What happened?
Hi ci team my project routes working stopped we didn't figure out what happened previous two day ago working fine today we add new route didn't work simply throw a 404 Can't find a route for
we have try
clear cache
clear log
clear browser history
but did not succeed another we have checked php spark routes in present routes but in debugger did not shown this issue in local
this project upload to server then worked perfect
Steps to Reproduce
$routes->get('test', function () {
    return 'Test route works!';
});

Expected Output
not works
Anything else?
No response

Cannot reproduce.
v4.3.5 is no longer supported. Upgrade to the latest v4.5.3.

We use GitHub issues to track BUGS and to track approved DEVELOPMENT work packages. We use our forum to provide SUPPORT and to discuss FEATURE REQUESTS.


Failed to open Cargo.toml: Os

[!] Selected Process to Suspend: notepad.exe
[] Encrypting Shellcode Using AES Encryption
[] Shellcode Encrypted
[*] Created new Rust project: 1
thread 'main' panicked at 'Failed to open Cargo.toml: Os { code: 3, kind: NotFound, message: "系统找不到指定的路径。" }', build\src/build.rs:30:10
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

me too

Need more context, please provide me the command line arguments you used, that caused this error.

Need more context, please provide me the command line arguments you used, that caused this error.

D:\Freeze.rs-main>Freeze-rs_windows_amd64.exe -E AES -I payload.bin -O 1.exe
___________
\_   _____/______   ____   ____ ________ ____     _______  ______
 |    __) \_  __ \_/ __ \_/ __ \\___   // __ \    \_  __ \/  ___/
 |     \   |  | \/\  ___/\  ___/ /    /\  ___/     |  | \/\___ \
 \___  /   |__|    \___  >\___  >_____ \\___  > /\ |__|  /____  >
     \/                \/     \/      \/    \/  \/            \/
                                    (@Tyl0us)
Soon they will learn that revenge is a dish... best served COLD & Rusty...

[!] Selected Process to Suspend: notepad.exe
[] Encrypting Shellcode Using AES Encryption
[] Shellcode Encrypted
[*] Created new Rust project: 1
thread 'main' panicked at 'Failed to open Cargo.toml: Os { code: 3, kind: NotFound, message: "系统找不到指定的路径。" }', build\src/build.rs:30:10
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

@Burden-xy it is because of the file name. There are certain program names rust doesn't like such as just a number (like you have) or the word "test") try a word like payload.exe and I am sure it will work.

root@ubuntu:~/oscp/Freeze.rs# ./Freeze-rs_linux_amd64 -E AES -I ./payload.bin -O pay.exe

    ___________
    \_   _____/______   ____   ____ ________ ____     _______  ______
     |    __) \_  __ \_/ __ \_/ __ \\___   // __ \    \_  __ \/  ___/
     |     \   |  | \/\  ___/\  ___/ /    /\  ___/     |  | \/\___ \
     \___  /   |__|    \___  >\___  >_____ \\___  > /\ |__|  /____  >
         \/                \/     \/      \/    \/  \/            \/
                                        (@Tyl0us)
    Soon they will learn that revenge is a dish... best served COLD & Rusty...

[!] Selected Process to Suspend: notepad.exe
[*] Encrypting Shellcode Using AES Encryption
[*] Shellcode Encrypted
[*] Created new Rust project: pay
[*] Added dependency to Cargo.toml
error: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the 'stable-x86_64-pc-windows-gnu' toolchain
Error: 'cargo build' failed

@Tylous What should I do with this report?

@stuacct071 run rustup component list if you do not see stable-x86_64-pc-windows-gnu as (installed) then you need to do a rustup target add x86_64-pc-windows-gnu

@Burden-xy it is because of the file name. There are certain program names rust doesn't like such as just a number (like you have) or the word "test") try a word like payload.exe and I am sure it will work.

This way, it can indeed be used normally. Thank you

@stuacct071 run rustup component list if you do not see stable-x86_64-pc-windows-gnu as (installed) then you need to do a rustup target add x86_64-pc-windows-gnu @stuacct071 运行 rustup component list ，如果您没有看到 stable-x86_64-pc-windows-gnu 为 (installed) ，则需要执行 rustup target add x86_64-pc-windows-gnu

root@ubuntu:~/test/Freeze.rs# rustup target add x86_64-pc-windows-gnu
info: component 'rust-std' for target 'x86_64-pc-windows-gnu' is up to date

It doesn't work.

If you can't add that target with rustup, then the problem is with your install of rust. I'd suggest you reinstall rust and try again.

C:\Users\lol\Desktop>Freeze.exe --Encrypt AES --Input ./Payload.bin --Output Payload.exe

    ___________
    \_   _____/______   ____   ____ ________ ____     _______  ______
     |    __) \_  __ \_/ __ \_/ __ \\___   // __ \    \_  __ \/  ___/
     |     \   |  | \/\  ___/\  ___/ /    /\  ___/     |  | \/\___ \
     \___  /   |__|    \___  >\___  >_____ \\___  > /\ |__|  /____  >
         \/                \/     \/      \/    \/  \/            \/
                                        (@Tyl0us)
    Soon they will learn that revenge is a dish... best served COLD & Rusty...

[!] Selected Process to Suspend: notepad.exe
[*] Encrypting Shellcode Using AES Encryption
[*] Shellcode Encrypted
thread 'main' panicked at 'Failed to create a new Rust project: Error { kind: NotFound, message: "program not found" }', build\src/build.rs:23:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I don't know what's going on , it's look like a same issues

@white-coffee this could because of some old lingering folders from previous attempts. Pleas make sure you clear all old artifacts and try again. If that fails let me know.

不能使用数字作为输出文件的名称。 用字母就好了。

C:\Users\lol\Desktop>Freeze.exe --Encrypt AES --Input ./a.bin --Output Payload.exe

    ___________
    \_   _____/______   ____   ____ ________ ____     _______  ______
     |    __) \_  __ \_/ __ \_/ __ \\___   // __ \    \_  __ \/  ___/
     |     \   |  | \/\  ___/\  ___/ /    /\  ___/     |  | \/\___ \
     \___  /   |__|    \___  >\___  >_____ \\___  > /\ |__|  /____  >
         \/                \/     \/      \/    \/  \/            \/
                                        (@Tyl0us)
    Soon they will learn that revenge is a dish... best served COLD & Rusty...

[!] Selected Process to Suspend: notepad.exe
[*] Encrypting Shellcode Using AES Encryption
[*] Shellcode Encrypted
thread 'main' panicked at 'Failed to create a new Rust project: Error { kind: NotFound, message: "program not found" }', build\src/build.rs:23:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

After deleting the old file and recompiling the tool, an error is still reported during generation
OS version：win10 x64、win7 x64

C:\Users\lol\Desktop>Freeze.exe --Encrypt AES --Input ./a.bin --Output Payload.exe

    ___________
    \_   _____/______   ____   ____ ________ ____     _______  ______
     |    __) \_  __ \_/ __ \_/ __ \\___   // __ \    \_  __ \/  ___/
     |     \   |  | \/\  ___/\  ___/ /    /\  ___/     |  | \/\___ \
     \___  /   |__|    \___  >\___  >_____ \\___  > /\ |__|  /____  >
         \/                \/     \/      \/    \/  \/            \/
                                        (@Tyl0us)
    Soon they will learn that revenge is a dish... best served COLD & Rusty...

[!] Selected Process to Suspend: notepad.exe
[*] Encrypting Shellcode Using AES Encryption
[*] Shellcode Encrypted
thread 'main' panicked at 'Failed to create a new Rust project: Error { kind: NotFound, message: "program not found" }', build\src/build.rs:23:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

After deleting the old file and recompiling the tool, an error is still reported during generation
OS version：win10 x64、win7 x64

@white-coffee your missing some dependencies or have old/stale files. It works fine for me on Windows 10 x64


Uniswap V2 QA (Ethereum) Schema Version 1.2.1 Subgraph Version 1.0.2 Methodology Version 1.0.0

The TVL graph looks like a step function to a huge abnormally large value. Perhaps caused by wonky price data. The first issue that should be fixed is this, as this might resolve other issues.
More detail: https://docs.google.com/spreadsheets/d/1R3GvDHbv8hNfqgmZ0NbkQNS0raBsLtbuJ20Kk_bOwtM/edit#gid=617964580

This has been fixed


[WFCORE-2938] Ensure the SSLContext from an injected legacy security realm is used for a remote outbound connection regardless of whether or not a username is specified

https://issues.jboss.org/browse/WFCORE-2938
https://issues.jboss.org/browse/JBEAP-10860

Core - Full Integration Build 5215 outcome was FAILURE using a merge of 1b1f67ef3538459764e4e53c0536c569a02eb078
Summary: Execution timeout (new); tests passed: 3872, ignored: 113 Build time: 01:25:21

Retest this please


Simplify object destructuring in argument

Hello,
when doing some prototyping and playing with object destructuring in function argument I've noticed that I must duplicate identifier names in type information and if there are many variables it looks heavier:
function mainLayoutComponent({banners, profile, cart}: { banners: Component, profile: Component, cart: Component }): any { }
Proposal:
My suggestion would be that destructuring in function argument position would allow type information definition if object type is not explicitly defined:
function mainLayoutComponent({banners: Component, profile: Component, cart: Component}): any { }
It would be handy. I don't know how that sounds from language design perspective as it feels like it will be possible to define a function which argument identifier is "unknown" but with given type information.
Compiler could translate that kind of construct into destructuring syntax before compilation.
Note: I've seen propsal with :: operator (https://github.com/Microsoft/TypeScript/issues/13471) which was rejected, but this "special treatment" of destructuring in argument space looks ES6, ES7 compatible.

Sorry, seems  like : is reserved in ES6 for variable rename. What a loss.. Haven't reasoned to add some compiler flag enableES6DestructuringRename to bypass default?
https://github.com/Microsoft/TypeScript/issues/7576

The flag name --enableES6DestructuringRename suggests the current behavior would be disabled by default, an inherently problematic suggestion but, regardless, I can't think of a situation where the proposed behavior should reasonably be used.
It would mean that a function could have two completely different meanings depending on the value of the flag.  Either represents a dramatic change to the lexical environment. I realize that it would likely result in errors but it still seems dangerous.
I understand your frustration with the current behavior. In addition to being ugly, I would say that the parameter destructuring renaming provided by : pollutes a function's interface with its implementation details for source level consumers. In addition to the typing issues I tend to avoid parameter destructuring for this reason as well.
Sadly, I don't think there's any getting around it.

Yes, with  --enableES6DestructuringRename  would be completed different universes and know that TypeScript philosophy wouldn't let anybody to drift off the ES standards, so, that nonsensical "variable renaming" will stay till official deprecation.
Currently, I see only one solution - to not use object destructuring:
function mainLayoutComponent(args:{banners: Component, profile: Component, cart: Component}): any { }
Or introduce some "Interface Spread To Variables" operator which could be used as such:
function mainLayoutComponent(...{banners: Component, profile: Component, cart: Component}): any { }
function mainLayoutComponent(...LayoutOptions): any { }

https://github.com/facebook/flow/issues/235
The guys at flow had a bit of a discussion about this same issue.
I'm partial to this syntax:
const MyComponent = ({
  ( aProp: string ),
  ( someOther: number ),
  ( zethIs: Object ),
  ( onClick: (event: Event) => void ),
  ( onSubmit: (event: Event) => void ),
}) =>
  ... {onClick} ...

The syntax is highlighted in VSCode correctly which is nice, and it's invalid JS to use an expression inside destructuring, which means it won't conflict with backwards compatibility.
I think it looks readable enough except for the implication you're defining a self-calling object or something as in a ts.d

As noted in https://github.com/Microsoft/TypeScript/issues/7576#issuecomment-198443953, the TC39 choice of syntax for this feature is unfortunate, and I feel your pain using it day in and day out. However, adding new non-standard syntax is not a good solution either. We would like to keep expression-level syntax as close as possible to the standard JS syntax.

Also I would say this is a duplicate of #7576,  with just new syntax proposal.


Fix typo

GitHub action -> GitHub Action

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@georgewallace,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.


Comparators should be Serializable.RSPEC-2063

https://rules.sonarsource.com/java/RSPEC-2063

This should also schedule AddSerialVersionUidToSerializable since we already have a recipe in place to do this work.
This will also need to consider any instance variables in the comparator (to make sure those are serializable).
You could probably call this method and make any non-serializable fields as transient:
https://github.com/openrewrite/rewrite/blob/main/rewrite-java/src/main/java/org/openrewrite/java/cleanup/FixSerializableFields.java


after installing it with  "yo meanjs" why do i get the .git  file already in there ?

IIRC, this is due to the meanjs generator doing a git clone to build the framework.
This question is probably better suited for the issues at https://github.com/meanjs/generator-meanjs


[Custom operationIds]

On the swagger spec the operationIds are very long

This results in very long auto generated code

We need away to reduce it.

You can rename your operation_id for example:
#[endpoint(operation_id="AAAAAAA", tags("todos"), status_codes(200, 404))]
pub async fn update_todo(id: PathParam<u64>, updated: JsonBody<Todo>) -> Result<StatusCode, StatusError> {
...
}

@chrislearn yes indeed but it’s also on objects like return types; would be nice to config the root so it’s smaller across the whole project automatically :-)

You can use your custom Namer to define your rename rule globally.
https://github.com/salvo-rs/salvo/blob/main/crates/oapi/src/naming.rs
I just don't have time to polish the documentation. PRs for documentation are welcome.


Job timers 2

Some notes because I picked this PR up and corners were cut

Some mind changes might be funky but I got lazy with roles
Autosave frequency is 15 minutes in case of server crashes
It detects AFK players crappily and tries to not write to DB when people go AFK. If we don't care about server crashes I can just write on round restarts / shutdown and remove autosave entirely.
I used semaphoreslims around the role timers dictionary to try and avoid threading issues. It looks like role bans might be susceptible to it if a role ban is added soon enough after someone joins the server but I don't think this has ever come up? Either way timers should okay but babby's first actually threaded code (parallel.for doesn't count).

:cl: Veritius & metalgearsloth

add: Added role timers. Players will have a 1 week grace period to fufill the requirements for their roles of choice.

Screenie

I updated the locks to stripeback and it looks a bit better.

Ike > Veritius > Sloth > ???

pleae..,,. i am goingto cry now

#9978


Remove invalid ProjectReference

This BLE Sample project will not build as the 'shared' reference appears to be missing. A search of other samples shows that this is the only project containing this reference so I believe it is outdated and should have been removed. The sample builds and deploys successfully after removing this reference.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

This fix has been folded into v5.0.3.


When is action() actually called?

The doc says:

For a single interaction, the router only runs once. That means, after you've visit a route, first it will call triggers, then subscriptions and finally action. After that happens, none of those methods will be called again for that route visit.

This isn't quite true. For a same route (same route name), calling setQueryParams() will call action again.

It's true.
Calling setQueryParams() changes the URL. Actually, it's a way to change the URL. That's a change in route.

What is a route? Is it a URL? Or is it what you define by calling FlowRouter.route()?
Those are two very different things and your doc is unclear because it uses the first definition in some cases and the other definition in other cases.
Consider this route declaration:
FlowRouter.route("/blog/:nb", {
    name: "myRoute",
    action: function(params) {
        //...
    }
});

Now consider these two URLs: https://www.abc.com/blog/333, https://www.abc.com/blog/666. They have the same route name "myRoute". But to you, do they refer to the same route or not?
If you clarify your vocabulary, I can issue a PR to update your doc.


[Bug] OOM on running pulsar-perf

Search before asking

[X] I searched in the issues and found nothing similar.

Version
OS：Linux version 3.10.0-1160.el7.x86_64
Pulsar： apache-pulsar-2.10.1
Minimal reproduce step
1）benchmark test：
bin/pulsar-perf produce -r 8000 -n 1 -threads 3 -c 10 -s 1024 persistent://my_tenant/my_tomcat_mulstag/threads-topic-08
What did you expect to see?
always right send
What did you see instead?
org.apache.pulsar.common.allocator.PulsarByteBufAllocator - Exiting JVM process for OOM error: failed to allocate 4194304 byte(s) of direct memory (used:<PHONE_NUMBER>4, max:<PHONE_NUMBER>0)
io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 4194304 byte(s) of direct memory (used:<PHONE_NUMBER>4, max:<PHONE_NUMBER>0)
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Cannot reproduce locally. I suspect it's about configuration issues or your local env restrictions. Moved to the Q&A form.


cephfs: remove snapshot protect/unprotect

Describe what this PR does
This commit eliminates the code for protecting and unprotecting
snapshots, as the functionality to protect and unprotect snapshots
is being deprecated.
Is there anything that requires special attention
Is the change backward compatible? Yes
Are there concerns around backward compatibility? No
Fixes: #4169

/test ci/centos/mini-e2e/k8s-1.27

@mergifyio rebase

/retest ci/centos/mini-e2e/k8s-1.26


[autodock-vina] update to boost 83

Fix autodock-vina when we update to boost 1.83.
boost/process.hpp is deprecated and now it's obligatory to use <boost/timer/progress_display.hpp>
Also we have to use boost::timer namespate instead of only boost namespace.
This should fix one automatic ci-fail detected in pull request #33597 ([boost] update to v1.83.0)

[X] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

This update port is deprecated by last boost 1.83 update.
Thank you very much.


TileJSON file too big

I have a large number of unique properties, each associated with a different feature, which is causing the tileJSON file to bloat, and causing my mapbox upload to fail. Is there a workaround that allows me to have these properties, but still keeps the tilejson size low without having to split the files?
If this is not possible, tippecanoe should issue a warning when the tileJSON size is too large.

Agreed. I no longer work at Mapbox so I can't just make this change to the repository here, but you can use --no-tile-stats to keep from generating the tilestats that are bloating the TileJSON, or --tile-stats-attributes-limit=20, say, to generate tilestats about only 20 attributes.

Thank you so much for continuing to respond here to queries! This doesn't seem to work, unfortunately. I continue to have a bloated TileJSON in spite of trying both --no-tile-stats and --tile-stats-attributes-limit=20. When I run tippecanoe-decode on the file, properties.json.vector_layers.fields` has ~109k keys (since I have 109k features, each with a unique property), which is the cause of the problem I think. Is there some way to reduce the size of this obj?

There isn't an existing option to do that, since I was always under the impression that it was a requirement for vector uploads to have a complete vector_layers. The loop that prepares it is here:
https://github.com/mapbox/tippecanoe/blob/master/mbtiles.cpp#L435
so if you are comfortable editing the code, you could add a count like this:
size_t count = 0;
for (auto j = fk->second.file_keys.begin(); j != fk->second.file_keys.end(); ++j) {
    count++;
    if (count > 100) {
        break;
    }

to stop after the first 100 attributes.


Proposed solution to issue #404

This is a proposed solution to issue #404.
The problem:
task = Task.find(1)
# => #<Task(tasks/1) title="Test" created_at="2016-08-04T20:03:42.612Z" updated_at="2016-08-06T17:00:35.649Z" id=1>
task.changes
# => {}

task = Task.all[0]
# => #<Task(tasks/1) title="Test" created_at="2016-08-04T20:03:42.612Z" updated_at="2016-08-06T17:00:35.649Z" id=1>
task.changes
# => {"title"=>[nil, "Test"], "created_at"=>[nil, "2016-08-04T20:03:42.612Z"], "updated_at"=>[nil, "2016-08-06T17:00:35.649Z"]}

Now:
task = Task.find(1)
task.changes
# => {}

task = Task.all[0]
task.changes
# => {}
task.title = 'New title'
task.changes
# => {"title"=>["Test", "New title"]}

👍

hi @tiagogodinho @lucasrenan  I've just got commit access on this repo and plan to get back on track with maintenance over time - will be in touch soon!

Fixed by #298. Thanks for your help on this @tiagogodinho!


Environment directory is not locked when environments are populated

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
[project]
name = "requirements-3.10.13"
version = "0.1.0"
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64"]

[tasks]

[dependencies]
python = "==3.10.13"
pip-tools = ">=7.3.0,<7.4"

pixi update
pixi run --frozen --manifest-path pixi.toml echo | pixi run --frozen --manifest-path pixi.toml cat

Issue description
This is a follow-up to https://github.com/prefix-dev/pixi/issues/1004 -- even though it was closed, the issue is still there. I've simplified reproduction steps, and tested that it's still present with the latest release.
The command fails with:
  ⠁ installing packages  [00:00:00] [━━──────────────────]     2/24 libffi                                                                                × failed to link libffi-3.4.2-h3422bc3_5.tar.bz2
  ├─▶ failed to link 'share/man/man3/ffi_prep_cif_var.3'

Expected behavior
Environment dir is locked for the update.
Relevant code: https://github.com/conda/rattler/blob/40803042b829346ed7522f797d70fd4da20fc12e/crates/rattler_repodata_gateway/src/utils/flock.rs#L204

Thanks for the reproducer! I was now indeed able to reproduce it. Will have to get back to this. It's not the highest priority to me. But PR's are always welcome!


Scala plugin's scaladoc task broken with Scala 2.13.0

Expected Behavior
When gradle scaladoc is run, Scaladoc should be generated.
Current Behavior
When using Scala 2.13.0:
  Execution failed for task ':scaladoc'.
  java.net.MalformedURLException

Context
When publishing to JCenter, I include Scaladoc jar - which is impossible to generate with Scala 2.13.
Steps to Reproduce
In the attached project gradle-scaladoc-bug.zip
  $ gradle scaladoc -PscalaVersion=2.13.0

Reason:
https://github.com/gradle/gradle/blob/master/subprojects/scala/src/main/java/org/gradle/api/internal/tasks/scala/AntScalaDoc.java#L53 assumes presence of scala/tools/ant/antlib.xml, which was removed:   https://github.com/scala/scala/pull/6255; see also  https://users.scala-lang.org/t/scala-2-13-0-ant-support/4694/11
Your Environment
Build scan URL: https://scans.gradle.com/s/7wmsskmoua3uu

I have encountered the same problem using Scale 13.1 and gradle 4.10.2

Gradle 6.0 will have improvements, including better support of Scala 2.13.
When 6.0 RC1 is out, could you test again?

@ljacomet :

Gradle 6.0 will have improvements, including better support of Scala 2.13.
When 6.0 RC1 is out, could you test again?

I did; it breaks the same way. "Better support for Scala 2.13" is not going to fix this issue; Gradle Scala plugin needs to be reworked to NOT use scala/tools/ant/antlib.xml (removed in Scala 2.13.0) to generate Scaladoc.

Scala 2.13 indeed broke everyone by removing the Ant support. We looked into fixing the issue by executing the work directly inside a worker action (https://github.com/gradle/gradle/tree/lacasseio/scala-doc-fix-for-2.13) however we hit an issue with the classloader which makes it impossible to run the action hence doesn't fix the issue.
At the moment, it would be recommended to build https://github.com/cigaly/scala-ant and adding that JAR to the ScalaDoc task's scalaClasspath property. We didn't confirm nor wrote a sample for this workaround, however, it should be the path forward to unblock users immediately.
We will look into the classloader issue with the worker API to see what needs to be fixed so we can move forward with a proper fix to handle 2.13 breakage.

We will look into the classloader issue with the worker API to see what needs to be fixed so we can move forward with a proper fix to handle 2.13 breakage.

Thank you!!!


iOS banner ad errors

Hello, when I run my app with banner ads on a physical iOS device I get the following errors:
Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
WF: _userSettingsForUser mobile: {
    filterBlacklist =     (
    );
    filterWhitelist =     (
    );
    restrictWeb = 1;
    useContentFilter = 0;
    useContentFilterOverrides = 0;
    whitelistEnabled = 0;
}
WF: _WebFilterIsActive returning: NO

Code:
OrientationBuilder(
  builder: (BuildContext context,
      Orientation orientation) {
    if (orientation != oldOrientation) {
      bannerAdController.load(force: true);
      WidgetsBinding.instance!
          .addPostFrameCallback((_) {
        setState(() {
          oldOrientation = orientation;
        });
      });
    }
    return Align(
      alignment: Alignment.bottomCenter,
      child: BannerAd(
        controller: bannerAdController,
        builder: (context, child) {
          return Container(
            child: child,
            color: Theme.of(context).primaryColor,
          );
        },
        loading: Container(
          width:
              MediaQuery.of(context).size.width,
          height: _bannerAdHeight,
          color: Theme.of(context).primaryColor,
        ),
        error: Container(),
        size: BannerSize.ADAPTIVE,
        nonPersonalizedAds: true,
        unitId: AdHelper.bannerAd,
      ),
    );
  },
);

The ad still shows up and works even though I'm receiving this error.

It's probably just a warning

Admob uses a webview to display banner ads in both Android and iOS. There are some people having this issue with the webview (WkWebView) in iOS (See this). Again, if the banner ad is displaying without problems, there's no issue here.
This is not just an issue with banner ads, it also happens with full-screen ads (rewarded and interstitial)
There is also an open issue in google's official admob plugin for unity: https://github.com/googleads/googleads-mobile-unity/issues/1138


chore: have release builds use secrets from KeyVault rather than pipeline variables

Description of changes
Previously, the release build for the package was using its own copy of GH_TOKEN and NPM_TOKEN specified as secret variables on the private release build pipeline. This updates them to instead use the variables from the KeyVault-backed variable group, to make rotating the secrets easier in the future.
Pull request checklist

[x] PR title respects Conventional Commits (starts with fix:, feat:, etc, and is suitable for user-facing release notes)
[x] PR contains no breaking changes, OR description of both PR and final merge commit starts with BREAKING CHANGE:
[n/a] (if applicable) Addresses issue: #0000
[n/a] Added relevant unit tests for your changes
[x] Ran yarn precheckin
[n/a] Verified code coverage for the changes made

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Turned on the rails 3 asset pipeline.

Fixed a few minor bugs found during testing:
non-js version of image voting didn't work
Image#process_image wasn't running in the background(!)
/ajax/create_image_object wasn't reporting the error back to the browser
Removed last vestiges of old TESTING, PRODUCTION and DEVELOPMENT switches.
Used .erb to insert some config constants directly into javascripts, e.g. max image upload size.
Combined several common javascripts into a single "application.js":
jquery, jstz, jquery_extensions, autocomplete, validate_file_upload, etc.
See the "require" directives at the top of application.js to see which.
Removed the unit test testing perf_monitor script as it is no longer used and very slow.
Some assets had to move around:
all the icons (static non-user images) moved to app/assets/images
name_list_data.js moved into /public (it's not managed by the asset pipeline)
Nginx should start to serve all static assets on the production server now, with proper caching.

Great. This was on my todo list.
On Sunday, February 1, 2015, Jason Hollinger<EMAIL_ADDRESS>wrote:

Fixed a few minor bugs found during testing:
non-js version of image voting didn't work
Image#process_image wasn't running in the background(!)
/ajax/create_image_object wasn't reporting the error back to the browser
Removed last vestiges of old TESTING, PRODUCTION and DEVELOPMENT switches.
Used .erb to insert some config constants directly into javascripts, e.g.
max image upload size.
Combined several common javascripts into a single "application.js":
jquery, jstz, jquery_extensions, autocomplete, validate_file_upload, etc.
See the "require" directives at the top of application.js to see which.
Removed the unit test testing perf_monitor script as it is no longer used
and very slow.
Some assets had to move around:
all the icons (static non-user images) moved to app/assets/images
name_list_data.js moved into /public (it's not managed by the asset
pipeline)
Nginx should start to serve all static assets on the production server
now, with proper caching.
You can view, comment on, or merge this pull request online at:
https://github.com/MushroomObserver/mushroom-observer/pull/57
Commit Summary

Turned on the rails 3 asset pipeline.

--
Ray Suelzer
Mobile:<PHONE_NUMBER>


It's not possible to open Tx details when user do a swap from weth to eth

Describe the bug
It's not possible to open Tx details when user do a swap from weth to eth, it will open for ages
To Reproduce
Steps to reproduce the behavior:

Go to uniswap
Do swap weth to eth'
Go to wallet and try to open Tx details
See error: wallet will open this tx for ages

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: mac os
Browser chrome
Version 126

Additional context
reproducible on dev branch
https://github.com/superhero-com/superhero-wallet/assets/69896204/0289bfdf-2447-41fe-8923-397f04719790
https://sepolia.etherscan.io/tx/0x4b7577691e019a53fd3e0c4fc016c7d2030a6c4b9370b85e12524c6ffeae9fcf
https://sepolia.etherscan.io/tx/0xa3bda888cf143ab41788c8f4eca93ce83b42fb50bd35c8919eb66dccb817c063
https://sepolia.etherscan.io/tx/0x2525fb87b3130dfe6ce23b886cc85c5751028f72426cc8389c25d76a4720cff5

LGTM


Support for registering & discovering applications using AWS CloudMap

Type: Feature
Support for registering & discovering applications using AWS CloudMap
Is your feature request related to a problem? Please describe.
We have an application which is currently deployed in both ECS and EKS cluster that would need AWS CloudMap integration to enable service discovery. But depending upon where you deploy the CloudMap integration may vary, like below:

For applications deployed in ECS we need to enable cloudmap integration via ECS task or Service.
For applications running on EKS we need to deploy an EKS operator and then integrate it via kubespec

This makes it difficult to have a single codebase for both services that can control the CloudMap integration and makes it DevOps heavy
Describe the solution you'd like
Similar to other Spring-boot AWS integration we can have the registry and discovery defined part of application or bootstrap yaml/properties file like below:
aws
 cloudmap
  registry
   namespace: cloudmap-namespace #Creates Cloudmap namespace - "API calls and DNS queries in VPCs"
   service: cloudmap-service #Create service if not exists
   healthcheck: /health
  discovery
   namespace: cloudmap-discovery-namespace
   service: cloudmap-discovery-service
   filterAttributes:
   	- key: name
          value: value

This will help application developers to control most aspects of the CloudMap integration part of their application code, instead of defining them in CDK, CloudFormation or k8s deployment files
Describe alternatives you've considered
Other alternative is to have the individual applications register themselves to AWS CloudMap service using AWS SDK. This leads to lot of code & logic duplications which would become difficult to manage
Additional context
If you guys like this please let me know. I am currently working on a pull request will submit it for review once it's ready.

@hariohmprasath thanks for offering your support for this feature. After reading about cloudmap it makes sense to have this integration which allows registry and discovery. I think a good example to follow the implementation is spring-cloud-consul

Do we have any working example of spring boot integration with this new repository. Seems like whatever I do none of the integrations like parameter store is working with the new repo. Can you please help me out with this?

Do we have any working example of spring boot integration with this new repository. Seems like whatever I do none of the integrations like parameter store is working with the new repo. Can you please help me out with this?

@hariohmprasath do you mind to open a discussion with category Q&A about it, please?

@hariohmprasath do you mind to open a discussion with category Q&A about it, please?

@hariohmprasath do you mind to open a discussion with category Q&A about it, please?

Thanks. I have opened a discussion

@hariohmprasath do you mind to open a discussion with category Q&A about it, please?

Thanks. I have opened a discussion


feat: Add Quart as currency

This commit adds the unit "Quart" as a currency.
Pull request
Proposed changes

Types of changes

[ ] New feature (non-breaking change which adds functionality).
[ ] Enhancement (non-breaking change which enhances functionality)
[ ] Bug Fix (non-breaking change which fixes an issue).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist

[ ] I have read the README document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Same as #313 but without plural forms.


update dgoss to support imported goss files

Currently, dgoss doesn't seem to support importing gossfiles via the gossfile test. This happens because dgoss copies goss.yaml  but does not copy any imported files to the container. One way to fix this would be to render goss.yaml and copy the rendered result to the container.
Steps to reproduce
Create the following files in the aelsabbahy/goss project root directory.
# file: goss.yaml
gossfile:
  ./included.yaml: {}

# file: included.yaml
process:
  nginx:
    running: true

Then run goss.
./extras/dgoss/dgoss run nginx

Expected result
~$ ./extras/dgoss/dgoss run nginx
INFO: Starting docker container
INFO: Container ID: ab483077
INFO: Sleeping for 0.2
INFO: Running Tests
Process: nginx: running: matches expectation: [true]

Total Duration: 0.001s
Count: 1, Failed: 0, Skipped: 0
INFO: Deleting container

Actual result
~$ ./extras/dgoss/dgoss run -it nginx
INFO: Starting docker container
INFO: Container ID: dafb62d8
INFO: Sleeping for 0.2
INFO: Running Tests
Error: found 0 tests, source: /goss/goss.yaml
INFO: Deleting container

I like this, the only downside is that it breaks dgoss for OSX, since goss doesn't run on there.
Maybe for now it would make more sense to establish a convention maybe something like:
goss.yaml
goss.d/whatever.yaml

Have dgoss copy goss.yaml and any goss.d stuff over, then run goss validate on the container.

@aelsabbahy the convention idea is interesting, but it wouldn't really help with the use case I had in mind.
I'm on a team where we have a base docker image and several child docker images that are built from the base image. We have tests for the base image that we also want to hold true in the child images, so we have things set up like this.
~/projects/docker-images/
    base-image/
        Dockerfile
        goss.yml
    child-image1/
        Dockerfile
        goss.yml
    child-image2/
        ....

Then in our child images' goss.yml we have:
gossfile:
  ../base-image/goss.yml: {}

# child-specific tests

We've had issues where installing/configuring something in the child Dockerfile unintentionally reverts a change made in the base Dockerfile and we weren't detecting it until very late in the development cycle (e.g. removing custom certs from java keystore by upgrading java and not re-installing the custom certs).
For now we're working around this issue via a script that basically runs goss render | dgoss run ..., which is working just fine for us now.
On a side note, you mentioned goss doesn't run on OS X. I've got a mac at home and perhaps this is something I could help with. Are there any specific limitations you've encountered with getting goss to work on OS X?

On a side note, you mentioned goss doesn't run on OS X. I've got a mac at home and perhaps this is something I could help with. Are there any specific limitations you've encountered with getting goss to work on OS X?

The main issue is that goss runs locally on the target machine or the machine under test. So when using dgoss you're running goss in the Linux container. So it's a version of goss that's compiled for linux-amd64 which won't run on OSX.
Today goss doesn't support OSX, I haven't looked into adding OSX support personally. I'm not against the idea so long as it doesn't complicate the code too much to do so. Even then, when using dgoss, you would use OSX goss to run the goss render and linux-amd64 goss to run the goss validate in the container.
Unfortunately, I'm not 100% sure I have a good clean solution that would work for OSX at this point.
The goss render | dgoss run.. approach doesn't seem too bad, I should probably add that to the documentation.
If you have any thoughts on a better approach please let me know.
Thanks,
Ahmed

Closing this PR since this won't work with OSX.
Updating the documentation with a goss render | dgoss run.. is probably the best approach for now.


add topic tags

I suggest adding the topics economics, macroeconomics in the About section, as explained at https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics

Great suggestion, thanks!


Can't import AxisLabel

Thanks for this module, animation works very well!
Can you also add an AxisLabel component, that you mention in a README file?

This might help you, so you can create your own: https://github.com/margelo/react-native-graph/issues/3

@skeie : Can you show the code of how you created your label?

Something like this @Angelk90 :
function AxisLabel() {
    const x =
        (INDEX_OF_YOUR_MAX_OR_MIN_VALUE / LENGTH_OF_YOUR_POINTS_ARRAY) *
        GRAPH_WIDTH;

    return (
        <View style={{ transform: [{ translateX: Math.max(x - 22, 5) }] }}>
            <Text color='darkPurple'>
                {YOUR_MAX_OR_MIN_VALUE}
            </Text>
        </View>
    );
}

Will close this, as the example from @skeie should be enough to make it work :)


Fy2019q3 Refresh

Fix links in all three slide decks
Update instructions for all three exercises
Update project files for all three exercises

manually merged


Update crate version to 0.2.114

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

My specific reason: ip_mreqn code is currently released with #2625, but #2642 is merged, which fixes e.g. socket2 since their https://github.com/rust-lang/socket2/pull/284 is released.

@bors r+

:pushpin: Commit b566c54f04a2c43ad611a6d0a411f1007877d394 has been approved by Amanieu

:hourglass: Testing commit b566c54f04a2c43ad611a6d0a411f1007877d394 with merge 3dd61509056707101d231053867d515ee5dd262e...

@Amanieu Thank you for your approval. Can you bump on crates.io?

Published.


change AnimatedScale Class to NeumorphicAnimatedScale to resolve conflict AnimatedScale class which have been reccently to flutter

…filect with AnimatedScale class of flutter

Import is missing in the PR
Add the  import 'animation/animated_scale.dart' ; to switch.dart file

Import is missing in the PR
Add the import 'animation/animated_scale.dart' ; to switch.dart file

It is already there .

Can we get this merged? This is blocking me to move to flutter 2.5.

Dup of #240 which was already merged. Thank you!


ATLAS ERROR: Reports not generated completely on Incidence Rates

@Yaswitha-MU , would you try running desiging and running an incident  rate analysis?

@Yaswitha-MU, I was able to preview incident rate of a pariticular analysis. Would you check if you have designed the study correctly?


Remove DiskResourceState registeration

Codecov Report

Merging #2103 (d0f56c9) into master (8c04acf) will decrease coverage by 3.93%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2103      +/-   ##
============================================
- Coverage     73.83%   69.90%   -3.94%
+ Complexity    10067     9576     -491
============================================
  Files           721      721
  Lines         54742    54736       -6
  Branches       6767     6766       -1
============================================
- Hits          40418    38261    -2157
- Misses        12181    14357    +2176
+ Partials       2143     2118      -25

Impacted Files
Coverage Δ

...b/ambry/clustermap/HelixClusterManagerMetrics.java
100.00% <ø> (+1.09%)
:arrow_up:

...java/com/github/ambry/notification/UpdateType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...thub/ambry/notification/BlobReplicaSourceType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../cloud/LeaderStandbyHelixVcrStateModelFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...om/github/ambry/named/MySqlNamedBlobDbFactory.java
0.00% <0.00%> (-94.74%)
:arrow_down:

...ry/accountstats/AccountStatsMySqlStoreFactory.java
0.00% <0.00%> (-93.34%)
:arrow_down:

...y/network/http2/Http2ClientStreamStatsHandler.java
0.00% <0.00%> (-90.48%)
:arrow_down:

...ava/com/github/ambry/network/http2/Http2Utils.java
0.00% <0.00%> (-90.00%)
:arrow_down:

.../github/ambry/account/mysql/MySqlAccountStore.java
0.00% <0.00%> (-87.50%)
:arrow_down:

...mbry/network/http2/Http2ClientResponseHandler.java
0.00% <0.00%> (-87.50%)
:arrow_down:

... and 106 more

Continue to review full report at Codecov.

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


Update; remove past events from upcoming, add grant #'s

Removed past events from upcoming, updated grant numbers on main page (index.html)

@melanieganz I think we could do with more updates to this as it seems like it's a bit sparse, but we could just merge it and take care of that in a later PR.


Unable to install and don't want to use sudo

$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.0/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  7766  100  7766    0     0  25429      0 --:--:-- --:--:-- --:--:-- 25462
=> Downloading nvm from git to '/usr/local/nvm'
=> mkdir: cannot create directory ‘/usr/local/nvm’: Permission denied
fatal: could not create work tree dir '/usr/local/nvm': Permission denied
bash: line 72: cd: /usr/local/nvm: No such file or directory
bash: line 73: cd: /usr/local/nvm: No such file or directory

=> Source string already in /home/michael-heuberger/.zshrc
=> Close and reopen your terminal to start using nvm

Do I really have to use sudo? Not looking good and it's not mentioned in the readme. Am I doing something wrong here?

You absolutely should never have to use sudo with nvm. Perhaps you have $NVM_DIR set to /usr/local/nvm? If so, unset that and remove all references to it from your shell profile files - then try reinstalling.

@ljharb yep, i figured out i had a horrible mess with environment variables. cleaned them all, all good now. would be good if nvm prints warnings ...


User activation logic does not follow docs

According to the docs, a user is "required to click activation link sent in email" after updating their email.
This is not happening and further research into the code reveals this different logic:
https://github.com/sunscrapers/djoser/blob/c5a6f85efb55bc569529c45d98d3992f7ff7fc8b/djoser/views.py#L152
Could you please either patch this or update the docs?

@dekoza since you've labeled this as a bug does this mean that this should be adjusted to match the docs, that is a user should receive an activation link when they update their email.

@dekoza a follow up question say if SEND_ACTIVATION_EMAIL has been set to True. Does it mean if a user updates their email then they should be deactivated and activated once the click on the activation link.

@joshua-s this seems to be working as expected with the docs. Is this still an issue?

@oma0256 sorry for the delay. Yes, this is still an issue because the email is only sent when the user is inactive and the user is not set to inactive when their email is updated.

same issue for me. no activation email for the new email

After some investigation i've found the tests that already guards against such issue occuring.
https://github.com/sunscrapers/djoser/blob/de199e9997bb59cc0df09de8b09d0af40be408bb/testproject/testapp/tests/test_user_view.py#L45
Could you give more details on the problem?


CI configuration for repo

We should decide on a CI service to use for this repository and the piedpiper-*-faas repositories. Something like Travis would be good for now, however something like Zuul would also be nice to allow for multi-repo gating

Implemented in #26


Support Aggregation/Faceting on tags

What is Aggregation or Faceting?
Aggregations/Facets provides a statistics (unique terms, range, counts) along a column or tag data. Statistics such as min and max price range, available color/category/size values provide the user with additional data about the current search result. These are useful and mandatory in the current e-commerce search applications because they enable further filtering of the search results without having to reformulate the search query or guess the available tags. It's a necessary drill down tool to reduce the number of search results in case the number of results are overwhelming. Having aggregation data also allows the front end to be more flexible and tailor the search results display to indicate some properties of the search result such as

low number of results -> show alternate queries or query reformulations
high number of queries -> highlight filters with high number of choices for drill down
divide the search results into multiple grids

https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations.html
https://lucidworks.com/post/faceted-search-with-solr/
https://lucene.apache.org/core/4_0_0/facet/org/apache/lucene/facet/doc-files/userguide.html

We will reopen this issue later if community specifically needs it


[bug] SHOW FIELD KEYS missing results

Bug report
System info:
[lab@test ~]$ uname -a
Linux test.local 3.10.0-514.21.1.el7.x86_64 #1 SMP Thu May 25 17:04:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[lab@test ~]$ influx
Connected to http://localhost:8086 version 1.2.4
InfluxDB shell version: 1.2.4

Kapacitor 1.3.1
Telegraf v1.3.1 (git: release-1.3 f93615672b02a41d9bc867bd92bf31c1d777989b)

Steps to reproduce:

I use telegraf's snmp plugin to store interface metrics in DB telegraf, measurement interface (Retention policy raw)
InfluxDB streams this data to Kapacitor; Kapacitor performs some calculations and stores the results in measurement interface_norm (Retention policy store30d)
I want to display the scheme of interface_norm:

> USE telegraf.store30d
Using database telegraf
Using retention policy store30d
> FORMAT json
> SHOW FIELD KEYS FROM interface_norm
{"results":[{}]}
>

Expected behavior:
> USE telegraf.store30d
Using database telegraf
Using retention policy store30d
> FORMAT json
> SHOW FIELD KEYS FROM interface_norm
{"results":[{"series":[{"name":"interface","columns":["fieldKey","fieldType"],"values":[["ifOutDiscards","integer"],["ifOutErrors","integer"],["ifOutMulticastPkts","integer"],["ifSpeed","integer"]
...

Actual behavior:
> USE telegraf.store30d
> SHOW MEASUREMENTS
name: measurements
name
----
[...]
interface
interface_norm
[...]

> SHOW FIELD KEYS FROM interface_norm
[nothing!]

> SELECT ifName, rx_bps FROM interface_norm WHERE "hostname" = 'qfx5100-01' AND "ifName" = 'ge-0/0/45' LIMIT 1
name: interface_norm
time                 ifName    rx_bps
----                 ------    ------
2017-07-05T16:34:02Z ge-0/0/45 2914.6666666666665

Additional info:

There is actual data in interface_norm (SELECT returns data)
There are many series in interface_norm:

[lab@test ~]$ influx -database telegraf -execute 'SHOW SERIES' | egrep '^interface_norm' | wc -l
203

Possibly the issue arises as measurement interface_norm only exists in retention policy store30d
I cannot select a RP with SHOW FIELD KEYS

Additional info

We have tags and fields. Displaying tags works:

> SHOW TAG KEYS FROM interface_norm
name: interface_norm
tagKey
------
agent_host
host
hostname
ifAlias
ifDescr
ifName
kapacitor

There are 1.8M rows:

> SELECT COUNT(rx_bps) FROM interface_norm
name: interface_norm
time                 count
----                 -----
1970-01-01T00:00:00Z 1845537

I suspect there's some funny interaction between the CLI's use statement, SHOW FIELD KEYS, and the default retention policy. Do you get the correct result if you specify the fully qualified measurement, i.e. SHOW FIELD KEYS FROM my_db.my_rp.my_measurement?

Yes, that could act as a workaround. Manually selecting an RP in the SHOW FIELD KEYS query displays the correct fields.
> USE telegraf
Using database telegraf
> SHOW RETENTION POLICIES
name     duration shardGroupDuration replicaN default
----     -------- ------------------ -------- -------
raw      168h0m0s 24h0m0s            1        true
store30d 720h0m0s 24h0m0s            1        false
> SHOW FIELD KEYS FROM raw.interface
name: interface
fieldKey                   fieldType
--------                   ---------
ifConnectorPresent         integer
ifAdminStatus              integer
[...]
> SHOW FIELD KEYS FROM raw.interface_norm
> SHOW FIELD KEYS FROM store30d.interface
> SHOW FIELD KEYS FROM store30d.interface_norm
name: interface_norm
fieldKey      fieldType
--------      ---------
ifAdminStatus integer
ifOperStatus  integer
[...]

(the middle two results are empty)
But this is still quite surprising:
SHOW FIELD KEYS

always shows the field keys of the series in the default RP (not the one currently selected using USE my_db.my_rp)
(it actually doesn't even display the measurements not existing in the default RP)
So, in order to get the whole picture, one needs to iterate through all RPs and measurements.... probably even the shards as according to the docs, different shards can have different field types.

Any updates on this?

The internal iterators used for several of the show commands has been changed on master to re-use more code from the query engine. We should re-test this on master.

@rbetts this is still not working on tip. I'll add to 1.4 milestone and we can review if we have enough time to fix?

This looks related or similar root issue as #7404

+1


Add compiletest infrastructure

Also includes a few basic tests.

Blocked by https://github.com/laumann/compiletest-rs/issues/114.

I've unblocked this by working around the upstream issue. Merging.


fix: Fix auto-teleport modal on mobile

PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #8176

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI;

Copilot Summary

🤖[deprecated] Generated by Copilot at 0986fb0
Improved mobile UI for AutoTeleportWelcomeModal component. Adjusted modal width and grid layout to fit smaller screens.

🤖[deprecated] Generated by Copilot at 0986fb0

AutoTeleportWelcomeModal is the gate to a new world
But on mobile devices it was broken and unfurled
We fixed the width and the grid to make it shine
Now you can travel anywhere with your phone in line

bento boxes

🍱 fixed 🙌

ref #8133 might change again

yep ic

lets wait for https://github.com/kodadot/nft-gallery/pull/8136, since @Jarsen136 is doing a superb work of unifying mobile modals

thanks!
pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 5.14 USD/DOT ~ 3.891 $DOT
🧗 13QUj3pZyFNfYj4AM336hRdyLQbevj5H3sR4PKmLEXLdwZhh
🔗 0xae43b46bdcfbcfbdc062b1ec0649aa19959b93cabfbc09e607affc2513b942a4
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


[Feature] Peer over ingress

Hello, thanks for liqo, it looks fantastic.
I have a question about peering, currently, it seems like you need peer over a NodePort/LoadBalancer, is it possible to be able to spin up and ingress in front of the relevant services (liqo-auth, liqo-gateway etc) and connect that way? We already use an underlying gke loadbalancer (used by nginx-ingress), so it's seems weird to expose more endpoints than required. Thanks!

Hi @tom-asmblr, it is possible to use an ingress to expose the liqo-auth service. Instead the liqo-gateway cannot be exposed through a common ingress (proxies like nginx which works with http only) because it uses UDP.
You can enable ingress for liqo-auth with these values:
https://github.com/aleoli/liqo/blob/04059c16d0e00543cbc979a6cbf196d9d857eb25/deployments/liqo/values.yaml#L258-L268

@tom-asmblr Please feel free to suggest how to improve the documentation here: https://docs.liqo.io/en/v0.8.3/installation/requirements.html#connectivity
(the ingress option was mentioned but, given your question, it may not 100% clear)

Thanks for thelp @cheina97 and @frisso - I missed this because we're using the liqoctl install command to install liqo, which doesn't seem to support that network flag. Probably best to use --only-output-values, modify the values, then apply from that?

@tom-asmblr when you use liqoctl install you can use the --set flag to override a helm value. Consider that liqoctl install uses helm to install liqo.
https://docs.liqo.io/en/v0.8.3/installation/install.html#customization-options


KAFKA-14912:Add a dynamic config for remote index cache size

As https://issues.apache.org/jira/browse/KAFKA-14912 described, add a dynamic config for remote index cache size.

Hi, @divijvaidya @satishd If you have time, help to review this pr, thanks.

Continuing discussion on Jira at https://issues.apache.org/jira/browse/KAFKA-14912?focusedCommentId=17756886&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17756886
We would prefer to have the cache eviction based on size since based on number of entries is not deterministic.

Hi, I have updated the cache to use weigher to evict based on bytes size. @divijvaidya

reminding here @divijvaidya

I'll take a look this week. Thanks for the PR.

I am yet to look into the part about why we need @volatile var remoteLogManagerOpt and why we need to modify tests but leaving some intermediate comments meanwhile.

Thanks for your review, @divijvaidya . Adding the volatile flag to remoteLogManagerOpt is just consistent with the _logManager next to it to increase readability. In fact, I think the volatile flags of these two variables can be removed. Please reconfirm this.

Like the unit test you all mentioned to verify that the cache contents are cleared after resizing, I have fixed and updated it, thanks! @showuon @divijvaidya

@hudeqi we have a few TS related tests failing such as https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-14243/14/testReport/junit/org.apache.kafka.tiered.storage.integration/EnableRemoteLogOnTopicTest/Build___JDK_17_and_Scala_2_13___executeTieredStorageTest_String__quorum_kraft/
Can you please check on them?

@hudeqi we have a few TS related tests failing such as https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-14243/14/testReport/junit/org.apache.kafka.tiered.storage.integration/EnableRemoteLogOnTopicTest/Build___JDK_17_and_Scala_2_13___executeTieredStorageTest_String__quorum_kraft/
Can you please check on them?

The strange thing is that I can pass this test locally. @divijvaidya

@hudeqi we have a few TS related tests failing such as https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-14243/14/testReport/junit/org.apache.kafka.tiered.storage.integration/EnableRemoteLogOnTopicTest/Build___JDK_17_and_Scala_2_13___executeTieredStorageTest_String__quorum_kraft/
Can you please check on them?

The strange thing is that I can pass this test locally. @divijvaidya

I'll try merging the latest trunk branch firstly.

Thanks @hudeqi for the PR. I will start reviewing it in the next couple of days.

@hudeqi
Can you rebase your branch against trunk instead of merge? With rebase, we can review the changes easily.

@hudeqi
Can you rebase your branch against trunk instead of merge? With rebase, we can review the changes easily.

Do you mean to merge these temporary commits into one commit? @kamalcph

@hudeqi
Can you rebase your branch against trunk instead of merge? With rebase, we can review the changes easily.

Do you mean to merge these temporary commits into one commit? @kamalcph

No, not squashing the commits. If you rebase your branch with trunk, then all your commits will be on the top of the tree which will be easy for the reviewers to review the change-set and follow the comments posted on this PR.

This PR was closed by me deleting the branch by mistake. It seems that I cannot reopen this PR. :)

test reopen.

Sorry, all. I've reopened a PR here

1


Reinit tooltipster and destroy troubles

I have problem with reinit tooltipster. If you call the method destroy and then initialize tooltipster on the same element, tooltip will no longer be shown. Method open doesn't help.
And the another problem is:
if by clicking on the button to call the method destroy i get the following error:
Uncaught TypeError: Cannot read property 'trigger' of null
Сan anyone help me with this?
Thanks.

The second problem is solved. Just set interactive: true.

Hi, it seems to work fine : https://jsfiddle.net/5xqqmrt6/14/

Yes, it really works. I figured out what was my mistake. Thank you.
I have a last question:
By clicking on the button changes content of the button tooltip and then tooltip is closed. To see a new tooltip, I have to re-hover over the button. How I can see new tooltip without re-hover?
Here example:  https://jsfiddle.net/5xqqmrt6/16/

You're welcome. It's the originClick trigger that closes the tooltip when the button is clicked. You can deactivate that trigger (see doc).

Many thanks for the help!


Remote messaging - download and parse config (1)

Task/Issue URL: https://app.asana.com/0/72649045549333/1199214002677571/f
Description
This PR is one of the parts of the Remote Messaging implementation.
In here, the reviewer will find:

Remote messaging modules created
Logic to schedule Remote Config worker to fetch remote config
Parse remote Json config  as Data models
Map Data Models into Domain models (includes some business logic rules to discard messages if mandatory information is missing)
Creates a new DB to store Remote Config info (as version, last evaluation, etc.)

Steps to test this PR
This PR does not include any UI component or user interactions.

Ensure tests are green

Ensure workers downloads config

Fresh install
Open the app
Ensure we have downloaded the remote config (checking logs you should see "RMF: Scheduling remote config worker")

UI changes
No UI changes

Closing. Merging https://github.com/duckduckgo/Android/pull/1741 instead.


Misleading documentation

https://github.com/avenga/couper/tree/master/docs#the-api-block-

You can add more than one api block to a server block

This is wrong.
The label for server is documented as optional, but is required.
time="2020-10-08T07:05:18Z" level=fatal msg="Failed to load configuration bytes: loadBytes.hcl:1,8-9: Missing name for server; All server blocks must have 1 labels (name)." type=couper_daemon

The label for api, files and spa is documented as optional, but if it is set there is an error. This may be the case for other blocks too. I only tested these three.
time="2020-10-08T07:00:27Z" level=fatal msg="Failed to load configuration bytes: loadBytes.hcl:6,7-15: Extraneous label for spa; No labels are expected for spa blocks." type=couper_daemon

Issue for multiple api blocks: #48
Issue for label in blocks: #49


Seeing an unhandled exception when installing via SRM

Built my SharpShell Property Sheet app with Visual Studio 2019. I upgraded the solution that I had started on Visual Studio 2017 and an earlier version of SharpShell.
When I use srm install as per the documentation, I get the log below.
Version of SharpShell used: 2.7.2
**Related type(s) of SharpShell-Server:2.7.2
SharpSellTools 2.2.0
Log Messages
2021-03-07 18:10:41.097Z - srm - error: SharpShell - Unhandled Exception in the AppDomain
2021-03-07 18:10:41.109Z - srm - error: System.ComponentModel.Composition.CompositionContractMismatchException: Cannot cast the underlying exported value of type 'SharpShell.SharpShellServer (ContractName="SharpShell.ISharpShellServer")' to type 'SharpShell.ISharpShellServer'.
at System.ComponentModel.Composition.ExportServices.CastExportedValue[T](ICompositionElement element, Object exportedValue)
at System.ComponentModel.Composition.ExportServices.GetCastedExportedValue[T](Export export)
at System.ComponentModel.Composition.ExportServices.<>c__DisplayClass12_01.<CreateStronglyTypedLazyOfT>b__1()    at System.Lazy1.CreateValue()
at System.Lazy1.LazyInitValue()    at System.Lazy1.get_Value()
at ServerRegistrationManager.Application.b__2(Lazy1 st)    at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext()
at ServerRegistrationManager.Application.InstallServer(String path, RegistrationType registrationType, Boolean codeBase)
at ServerRegistrationManager.Application.Run(String[] args)
at ServerRegistrationManager.Program.Main(String[] args)
Message: SharpShell Diagnostics Initialised. Process srm.
Message: Started the Server Registration Manager.
Message: SharpShell Diagnostics Initialised. Process srm.
Message: Started the Server Registration Manager.
Message: SharpShell Diagnostics Initialised. Process srm.
Message: Started the Server Registration Manager.

AFAIK, the SharpShellTools 2.2.0 contains an SRM for SharpShell 2.2.0.
So your exception could relate to a version mismatch between the SRM version and the version of the SharpShell assembly you are building against. SRM version and SharpShell version needs to be the same.

Hmmm, the only versions of SharpShellTools I could find were 2.2.0 and 2.2.1?
If you look at this page: https://github.com/dwmkerr/sharpshell#installation
It shows the version of SharpShellTools to be 2.2.0 while the versions of the other two packages is 2.7.2.

There is no nuget package for the SharpShellTools targeting SharpShell 2.7.2
For testing and development, I build SharpShell 2.72. from the source here on my local machine and use the resulting SRM.
If this is not an option for you, you can downgrade the referenced SharpShell NuGet back to 2.2.x.

Strange. I built SharpShell from source at the Master branch and did not get an srm.exe that I can find ...

Ah okay. I never used srm.exe, so I was not aware of it. Checked my local build, and yes, it is not there.
For testing, I use the ServerRegistrationManager
Regarding the SharpShellTool NuGet, you can also check out issue #269

Does the ServerRegistrationManage have the same functionality/commands as srm.exe?
Also, I tried building the SharpShareTools under Visual Studio 2019 and it does not build srm.exe so I am getting confused.
Should I be using Visual Studio 2017?
I will check out the issue you mentioned.
Thanks for your help.

What I see from the code, it provides the same functionality.
The Solution files are targeting Visual Studio 2017. You can either use VS2017 or upgrade to VS2019, depending on your setup and preferences.


Remove event succeeded log from EventConsumerLogger

CHANGES
Removing log.Info().Msgf("%s succeeded", evName) from EventConsumerLogger() middleware since it is generating an excessive number of logs on behalf of our services.

Closing this PR since we dealt with the issue locally within our service!


Unable to configure Remote Resource Store behind https

The ResourceFactory doesn't allow for configuring a remote resource store that is accessed via an https URL.
PR with fix to follow.

Fixed by PR #434


add usdt test button

to capture interests.

Also disable usdt from coin list due to usdt approval requires  setting allowance to 0 before increase it, which is incompatible with our current flow.


Add color picker to unitframe border

Add color picker to unitframe border, currently the "Dark Mode" option isn't dark enough for my taste and would love if you could implement a color picker instead 👌

Found a quick workaround how to color my unit frame borders by making a macro containing this:
/run PlayerFrameTexture:SetVertexColor(0, 0, 0, 1)
/run TargetFrameTexture:SetVertexColor(0, 0, 0, 1)
/run TargetofTargetTexture:SetVertexColor(0, 0, 0, 1)
/run PetFrameTexture:SetVertexColor(0, 0, 0, 1)
More or less all set for the fresh server now with this and the latest update! 👌
Again, thanks a lot for making this addon! :)


Require chainId not 0

Enforce this in the bridge contract, add corresponding tests
Use truffleAssertions fail instead of utils.expectThrow, as truffle Assert checks that the error is revert while the expectThrow consider a success any kind of failure, giving false positives

Coverage increased (+0.6%) to 95.662% when pulling 704cdccad86947ce66ae2cc7eead7a62dd49fb16 on require-chainid-not-zero into e54ac1f8c2a1547cc7a3d55884cff4fb00d5c386 on nftbridge-rebased.


Support Desktop and WasmJs Kotlin multiplatform

Hi
Please add support for Desktop and WasmJs.

Hi @mahramane, I have plans to include support for both Desktop and WasmJs within the next few months.
Thank you :)


Added Sourcemaps

Sourcemaps don't work with a minified CSS file so that is commented out
during development.

Is ut possible to use Gulp with a flag? It would be great to use this like gulp --minify-css-off for sourcemap support/minify css off. I'm just afraid I'll forget to uncomment the minifycss during deployment. Any thoughts on that?

Yargs and gulpif?

Also, should probably add the source map to .gitignore.


fix: don't fail cleanup if internalrequests not installed

This is the case on the new Fedora Cluster run by the Konflux+Fedora SIG

/test all

/test all


FW: rewrite wait_for_child() as wait_for_children()

We only start one child for now, but now we can wait for more than one.

This looks good. Cannot tell for the Windows part though.

"It works" suffices for me. We will need to get back to it when we get more than 64 child processes.


Update in Maven

Hello, you should update this library in Maven, the version differs from the source code hosted in GitHub.
Thanks.

I was making some breaking changes to the API, I was waiting until I finished with those to release a new version. I'll get it updated as soon as I can!

v0.2.1 has been uploaded to bintray and is being processed at maven central.


Access Logging setup causes logging loop.

After #645 being merged, Terragrunt is setting up Access_Logging on terraform state buckets, logging access to the prefix TFStateLogs/ in the same bucket.  This causes an access logging loop causing there to be lots of logs. It's also against Amazon's recommendations:
https://aws.amazon.com/premiumsupport/knowledge-center/s3-server-access-logs-same-bucket/
https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerLogs.html#server-access-logging-overview
I'd suggest the "skip_bucket_accesslogging" option should default to false on bucket creation.
If I PR'ed that change, would it be likely to be merged?

So you're saying that if you send access logs for bucket X to bucket X, AWS gets in an infinite loop where it seems the access logs themselves as a new "access" and logs that too, and so on, infinitely?

According to Amazon, That's what happens.
Replication recipe:
Spin up a new bucket by running a terragrunt apply on any minimal terraform stack.
list the bucket in the aws console.  No TFStateLogs will be present initially (not sure why this is, maybe there's a setup delay or something).
Inspect the bucket in an hour's time.  We're seeing logs being continually written to that bucket, despite to additional access.

Yikes 😮  Thanks for reporting.
I think then we'd want to change the logic to use a separate bucket for access logging. Perhaps we pick some name pattern by default (xxx-access-logs where xxx is the original bucket name?) and allow it to be overridden via config. A PR to fix this is VERY welcome.

With derived bucket names, there's an edge case around the lengths of bucket names (63 characters max), so long bucket names could result in illegally long access bucket names (which would assumedly fail creation), or would need to be truncated before adding the logging suffix (which would result in possibly non-unique names).
It might be better to have a single logs bucket with a predictable name, and a unique prefix (say /TFStateLogs/{tfstate-bucket-name}/) for each.

Ah, that makes sense. In that case, let's make access logging off by default, and allow it to be turned with one config parameter, that also requires you to set the access logs bucket name in another param.

I'l try to get a PR in for that in the next couple of days.

Thank you!

It would be good if access log is disabled by default 👍

Hey @tony-harverson-moonpig @michelzanini Thought I'd give you a heads up that I'll be picking this up. I've read thought the comments, so will be able to share some more details as I dive into this a bit more. 🙂

Hello, first of all thanks for this improvement to the access logging setup. It would be handy to have an ability to specify also the target prefix to override targetPrefix := "TFStateLogs/" for example to be able to send access logs from multiple terraform state buckets to single logging bucket and not mix them together. Is there any chance to add such option?

@dsecik Please file a separate issue for that! PR to support it is welcome too.

Hi @brikis98, I created #1437. Sadly can't help with submitting PR as I have no experience with Go.

This was fixed in #1400 and released in https://github.com/gruntwork-io/terragrunt/releases/tag/v0.26.0.

This was fixed in #1400 and released in https://github.com/gruntwork-io/terragrunt/releases/tag/v0.26.0.


Option allowUnionTypes is ignored

Hello,
since I made the update to the latest version of ajv, I get the following warning in the browser, even if I set the appropriate options.
strict mode: use allowUnionTypes to allow union type keyword at "#/definitions/etpSetter/properties/value" (strictTypes)

What version of Ajv are you using? Does the issue happen if you use the latest version?
Version: 7.0.2
Happens with latest version: yes
Ajv options object
{strict: false, allowUnionTypes: true}

Is this a bug or am I making some kind of mistake here?
Thanks in advance.

Please post the executable code sample, as small as possible, that demonstrates the issue - ideally to runkit.com or here. It’s difficult to say why this is reported when the option is present.

closing here, please reopen with code example id needed

closing here, please reopen with code example id needed


Test Automation IDs

As we are trying to roll out end to end testing on our frontend assets using webdriver.io and selenium we find it increasingly challenging to target elements from our underlying UI library, material-ui.
There is no easy single solution to this problem. Adding data-test attributes to all elements would be the optimal solution, with an option to parameterize per component to avoid conflicts.
Please consider automated testing on your next iteration of your awesome library.

Following https://material-ui.com/customization/themes/#properties you can already set attributes on a per component basis.
This is currently only missing an option for all components.
Depending on your target you could fake this with a Proxy. Checkout this codesandbox: https://codesandbox.io/s/zp0jrmkox
This is just something hacked together in a few minutes so use this with caution.

Please consider automated testing on the next iteration of your awesome library.

@thanpolas We have, we are writing a lot of end to end tests at work. There are different layers of answers to this problem.

The first layer is about promoting best practices. The default way of writing e2e tests should be about using accessibility. If a screen reader can make sense of your page, so your e2e tests. It's a win for everybody. Your tests are closer to what's happening, your tests are less likely to break, it ensures your site stays accessible. However, there are rare cases where directly targeting an element can be much simpler, it what the data-test attribute can be used for. So by design, the dynamic CSS classes prevent developers from writing brittle assertions.
The second layer is about having deterministic class names. There are always people that won't agree with the previous vision. They can use the dangerouslyUseGlobalCSS option.

Are you referring to the aria-* tags that some elements have and traverse using those?

Not necessarily. I'm referring to the usage of selectors like 'input[name="email"], 'button[type="submit"]', button with text foo or [role="menu"] > div.

< MuiButton > Could directly assign a data-test attribute
< IconButton> Could directly assign a data-test attribute
 Had to define MenuProps and SelectDisplayProps to target the two elements

You can use the theme.props feature of Material-UI for that.

@oliviertassinari and @thanpolas I am new to this topic. So far by reading these I understood that I can use css selectors like:

Accessibility selectors: input[name="email"], button[type="submit"]', button, [role="menu"] > div, select[name="country"], etc
Or assign data-test whenever needed; MuiButton, IconButton

So is this the final saying in the matter: "Use accessibility CSS selectors AMAP to bridge the gap between your tests and screen readers and if it is not really practical use data-tests."
Did I manage to summarize it the way you intended it?
I have read this article too and it seems the way to go for me.


Documentation: Discussion of possible metadata entries for nursery rules

I took some time today to try and locate some techniques within the nursery being used in the wild, and relevant writeups to reference as well. I cannot guarantee they are all the most stellar examples (or even necessary for some rules) but I put emphasis on the general quality of their writeups, and I hope some will prove to be useful additions.
I have compiled 24 which I will post below with their SHA-256 hash.
[enumerate-browser-history.yml]
https://www.proofpoint.com/us/threat-insight/post/microsoft-word-intruder-integrates-cve-2017-0199-utilized-cobalt-group-target
24973014fa8174ffff190ae7967a65307a23d42386683dc672babd9c6cf1e5ee
[access-the-windows-event-log.yml]
https://www.microsoft.com/security/blog/2018/03/01/finfisher-exposed-a-researchers-tale-of-defeating-traps-tricks-and-complex-virtual-machines/
b035ca2d174e5e4fd2d66fd3c8ce4ae5c1e75cf3290af872d1adb2658852afb8
[check-for-process-debug-object.yml]
https://blog.talosintelligence.com/2019/01/what-we-learned-by-unpacking-recent.html
3bc0ae9cd143920a55a4a53c61dd516ce5069f3d9453d2a08fc47273f29d1cf3
[connect-network-resource.yml]
https://download.bitdefender.com/resources/files/News/CaseStudies/study/200/Bitdefender-Whitepaper-RADrat-crea2645-A4-en-EN-interactive.pdf
4786fa468111632ea66f03dfd868ca95fb91d4472b2c332d46d8444c19c75624
[decrypt-data-via-sspi.yml]
https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/03/09133534/The-Slingshot-APT_report_ENG_final.pdf
2a51ef6d115daa648ddd57d1e4480f5a18daf40986bfde32aab19349aa010e67
[encode-data-using-base64-via-winapi.yml]
https://kc.mcafee.com/resources/sites/MCAFEE/content/live/CORP_KNOWLEDGEBASE/92000/KB92415/en_US/McAfee_Labs_Threat_Advisory_Maze.pdf
b345697c16f84d3775924dc17847fa3ff61579ee793a95248e9c4964da586dd1
[encrypt-data-using-salsa20-or-chacha.yml]
https://www.sophos.com/en-us/medialibrary/PDFs/technical-papers/sophoslabs-matrix-report.pdf
13c0fd18c602dd6aa71d78072ad6617a1871cf24b366a12c8c3f2f278f301f5c
[encrypt-data-via-sspi.yml]
https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/03/09133534/The-Slingshot-APT_report_ENG_final.pdf
2a51ef6d115daa648ddd57d1e4480f5a18daf40986bfde32aab19349aa010e67
[enumerate-browser-history.yml]
https://www.proofpoint.com/us/threat-insight/post/microsoft-word-intruder-integrates-cve-2017-0199-utilized-cobalt-group-target
24973014fa8174ffff190ae7967a65307a23d42386683dc672babd9c6cf1e5ee
[enumerate-graphical-windows.yml]
https://www.ccn-cert.cni.es/informes/informes-ccn-cert-publicos/4805-ccn-cert-id-09-20-guloader-english/file.html
5d91ff8d079c5d890da78adb8871e146749872911efe2ebf22cfd02c698ed33d
[enumerate-system-firmware-tables.yml]
https://infosec.cert-pa.it/analyze/4a7b3ead2eff0b8dee43337a652084e5.pdf
8e37833af9c07877aa9a0fb9f1fe82f0fc0187d8ac4457714b12d2fb1204c384
[enumerate-threads.yml]
https://vk-intel.org/2018/09/10/lets-learn-dissecting-dridex-banking-malware-part-1-loader-and-avast-snxk-dll-hooking-lib/
916781bc62be8073748af7d1ca301f0ff27e6dd8069d859a003b6eb6a9c305a4
[get-comspec-environment-variable.yml]
https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/03/07180722/Report_Shamoon_StoneDrill_final.pdf
69530d78c86031ce32583c6800f5ffc629acacb18aac4c8bb5b0e915fc4cc4db
[get-file-size.yml]
https://www.crowdstrike.com/blog/guloader-malware-analysis/
bfa5dba46db1253587058b0392c04c8403846fa55d7dcf1044e94e6a654d4715
[get-file-version-info.yml]
https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/03/09133534/The-Slingshot-APT_report_ENG_final.pdf
2a51ef6d115daa648ddd57d1e4480f5a18daf40986bfde32aab19349aa010e67
[get-mac-address.yml] (Possibly for different use than what the rule outlines)
https://blog.malwarebytes.com/threat-analysis/2017/05/the-worm-that-spreads-wanacrypt0r/
24d004a104d4d54034dbcffc2a4b19a11f39008a575aa614ea04703480b1022c
[get-routing-table.yml]
https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2012/08/20083155/bencsathPBF11duqu.pdf
f1ee026692c8458bdd698884183150eb2b898a576bc1d94668bf9e0ec1bb7507
[get-system-firmware-table.yml]
https://www.proofpoint.com/us/threat-insight/post/new-modular-downloaders-fingerprint-systems-part-2-advisorsbot
9dd12d3a32d2ba133bac8747f872f649b389a9cf3f4baaa9fad69a43d2e4f982
[get-thread-local-storage-value.yml]
https://vk-intel.org/2018/10/
306e515018f3f43a8edd98f29097b8a340f48920c74e127994a7f164f7385684
[get-token-membership.yml]
https://www.cybereason.com/blog/the-sodinokibi-ransomware-attack
ad6b1c258c45d7661ef929a5250a69f1a1c7898e90d782772671f3398cb875fb
[hash-data-with-md5.yml]
https://unit42.paloaltonetworks.com/unit42-dragonok-updates-toolset-targets-multiple-geographic-regions/
82f028e147471e6f8c8d283dbfaba3f5629eda458d818e1a4ddb8c9337fc0118
[hide-thread-from-debugger.yml]
https://www.crowdstrike.com/blog/guloader-malware-analysis/
bfa5dba46db1253587058b0392c04c8403846fa55d7dcf1044e94e6a654d4715
[move-file.yml]
https://medium.com/threat-intel/emotet-dangerous-malware-keeps-on-evolving-ac84aadbb8de
aa0cbe599839db940f6cc2f4ca1383dbb9937b8c7dd6460847c983523cd63c39
[packaged-as-a-nsis-installer.yml]
https://www.mcafee.com/blogs/other-blogs/mcafee-labs/ransomware-families-use-nsis-installers-to-avoid-detection-analysis/
1a06e44df2fcf39471b7604695f0fc81174874219d4226d27ef4453ae3c9614b

This looks good.  Also tied to https://github.com/fireeye/capa-rules/issues/55

Very cool, thank you @0x262D

looks like the user has since deleted their account :-(


ONVIF PTZ improvements

Adds get_position command and redirects move_* output to /dev/null to prevent their output being injected as HTTP headers in ONVIF responses.

The get_position command needs to be supported in order for Frigate (and perhaps other similar systems) to enable PTZ control
The output of the move_* commands gets dumped into the HTTP response (before/in the HTTP headers), which leads to errors being logged by Frigate whenever it requests PTZ moves as it sees them as invalid/malformed headers

I like the idea but maybe removing motors output under -v flag would be a better solution to silence the app? @gtxaspec please chime in.

Silencing the motors output (either by default or via a new flag - maybe -q for "quiet") would definitely be tidier - and if that's happening, adding a new flag to get the position in simple x,y format would save us from using sed to extract them from the JSON output.  This PR was just the result of a quick attempt at enabling PTZ in Frigate by adjusting onvif.conf - if we can improve motors to make this cleaner, I'm definitely in favour of that.

I've popped in a PR for the motors tool to add a -q flag to suppress output and a -p flag to get the plain x,y position output.  If that gets merged (or an alternative), I'll update this PR to use the new commands.

@pauln i merged your pr in the motors repo, i think you can refactor this a bit.  check the latest commits i pushed also regarding onvif.

@gtxaspec Since you've already added get_position, I've rebased and replaced the redirection to /dev/null with the new -q option on the move commands.


fix(core): move generator not updating paths correctly

Issue
project.json paths weren't being updated correctly
Steps to reproduce

nx g @nx-dotnet/core:lib my-lib
nx g @nx-dotnet/core:move --projectName my-lib --destination a/b/c
nx g @nx-dotnet/core:move --projectName a-b-c --destination my-lib

Expected result

sourceRoot, outputPaths, etc should be pathed correctly

Actual result

Note: when this issue was discovered we noted $schema was also incorrect following the generator.  This hasn't been reproducible but does show itself in the added unit test.

Lgtm, can you take care of the sonar code smell?

Awesome, thanks for the contribution 🎉


tests: Use libvmi instead of NewRandomVMIWithEphemeralDisk

What this PR does
Use libvmi instead of NewRandomVMIWithEphemeralDisk
Before this PR:
After this PR:

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

/test pull-kubevirt-e2e-k8s-1.27-sig-compute

/ok-to-test
I can vouch for Bell

/ok-to-test
I can vouch for Bell

Please, see a change:
PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

@xpivarc oh gotcha, makes sense.
@bell-lev feel free to ping me offline once you will be ready to run the tests.


Make sure to relink executables after linker script changes

The linker script is passed in ldflags, which isn't tracked
automatically, so incremental builds don't re-trigger linking correctly
when it changes.
Add it to inputs to force a re-link if the timestamp changes.

@mspang @msandstedt ?

@andy31415 ?


[travis-ci] add CI configuration file

you can look at it here http://travis-ci.org/#!/formapro/BadaBoom


Lookup asserted tuples by key

Current behavior:
There isn't a way to check if a tuple with a certain key has already been asserted
What is the motivation / use case for changing the behavior?
In some cases it is necessary to be able to access previously asserted tuples by their keys from from action functions
Additional information you deem important (e.g. I need this tomorrow):

Merged #9


Outline slides for each subsection

Hi! I use Touying a lot to make presentations :) thank you for developing it, it has done a lot for me.
I would like a feature where I can automatically have a mini-outline for each section, showing the subsections that will come up in this section. In that way, I can give my audience a very short preview at the beginning of every section. Is there a way to automatically do this?
Thanks,
Thijs

Related to this ?

While it's not fully automated yet, I managed to create an example that might help. You can check it out here: https://typst.app/project/wW4El9k64GTdQPe5WZRDyu.
I hope this helps.

@enklht Awesome! thanks for the quick reply :)
I think @eusebe's request is still valuable to take into account for a future version of Touying.

I think improving the custom outline is a good idea.
I will try to implement features like Beamer's sectionstyle and subsectionstyle. Thanks!


Ridgeplots - split long gene names to multiple lines and replace _ with whitespaces

Added a 'wrap' function in the d3-charts package to do this

Do the same for heatmap


Perform strict resolution of Configuration, so that attribute matching can be resolved exactly

Expected Behavior
When resolving a Configuration it is possible to strictly resolve based on the provided attributes.
When attribute values are mismatched, Gradle will not silently resolve random files.
If such issues occur when multiple Configurations extend each other, it's exceptionally easy to track down and diagnose the issue.
Current Behavior (optional)
When resolving a Configuration it is not possible to strictly resolve based on the provided attributes.
When attribute values are mismatched, Gradle will silently resolve random files.
If such issues occur when multiple Configurations extend each other, it's exceptionally difficult to track down and diagnose the issue.
As investigated in https://github.com/gradle/gradle/issues/27594 it is not possible to manually filter using an ArtifactView in a configuration-cache compatible way. Even if it was, the workaround is very verbose and repetitive, inviting further bugs.
Investigating mismatches is exceptionally complicated, as tools like dependencyInsight basically require you know what the issue is before you know it, and have UX issues, or are incompatible with composite builds.
Context
Example: it is impossible to protect against mistakes
When an attribute value has a mistake, it's not easy to see what the problem is. Gradle will run without error and resolve unrequested files.
In the following example the attributes of demoConfWindowsDebugResolver and demoConfWindowsDebugProvider appear to match, so it's not clear why Gradle wouldn't resolve the correct file.

Create a Gradle project with the following build.gradle.kts
// build.gradle.kts

@file:Suppress("UnstableApiUsage")

plugins {
  kotlin("multiplatform") version "2.0.0"
}

repositories {
  mavenCentral()
}

kotlin {
  jvm()
  iosX64()
  iosArm64()
}

object DemoAttributes {
  val demo =
    Attribute("demo")
  val target =
    Attribute("demo.target")
  val buildType =
    Attribute("demo.buildType")

  private fun Attribute(name: String): Attribute<String> =
    Attribute.of(name, String::class.java)
}

project.dependencies.attributesSchema {
  attribute(DemoAttributes.demo)
  attribute(DemoAttributes.target)
  attribute(DemoAttributes.buildType)
}

val compilationTaskWindowsDebug by project.tasks.registering(Sync::class) {
  description = "Dummy task that represents a Windows Debug compilation task"
  temporaryDir.resolve("input").resolve("windows-debug.txt").apply {
    parentFile.mkdirs()
    writeText("Windows Debug file")
  }
  from(temporaryDir.resolve("input"))
  into(temporaryDir.resolve("output"))
}

val demoConf: Configuration by configurations.creating {
  declarable()
}

val demoConfWindowsDebugResolver: Configuration by configurations.creating {
  description = "Resolve Windows Debug compiled files"
  resolvable()
  extendsFrom(demoConf)
  attributes {
    attribute(DemoAttributes.demo, "true")
    attribute(DemoAttributes.target, "windows")
    attribute(DemoAttributes.buildType, "debug")
  }
}

val demoConfWindowsDebugProvider: Configuration by configurations.creating {
  description = "Provide Windows Debug compiled files"
  consumable()
  attributes {
    attribute(DemoAttributes.demo, "true")
    attribute(DemoAttributes.target, "Windows")
    attribute(DemoAttributes.buildType, "debug")
  }
  outgoing {
    artifact(compilationTaskWindowsDebug)
  }
}

val incomingFilesResolverTask by tasks.registering {
  val incomingFiles = demoConfWindowsDebugResolver.incoming.files
  inputs.files(incomingFiles)
  doLast {
    val fileNames = incomingFiles.asFileTree.map { it.name }
    println("artifactViewFiles: ${incomingFiles.asFileTree.map { it.name }}")
    if (fileNames.singleOrNull() != "windows-debug.txt") {
      error("Invalid resolution. Expected [windows-debug.txt] by was $fileNames")
    }
  }
}

val artifactViewFilesResolverTask by tasks.registering {
  val artifactViewFiles = demoConfWindowsDebugResolver.incoming.artifactView { lenient(false) }.files
  inputs.files(artifactViewFiles)
  doLast {
    val fileNames = artifactViewFiles.asFileTree.map { it.name }
    println("artifactViewFiles: ${artifactViewFiles.asFileTree.map { it.name }}")
    if (fileNames.singleOrNull() != "windows-debug.txt") {
      error("Invalid resolution. Expected [windows-debug.txt] by was $fileNames")
    }
  }
}

dependencies {
  demoConf(project)
}

//region utils
fun Configuration.consumable(
  visible: Boolean = false
) {
  isVisible = visible
  isCanBeResolved = false
  isCanBeConsumed = true
  isCanBeDeclared = false
}

fun Configuration.resolvable(
  visible: Boolean = false
) {
  isVisible = visible
  isCanBeResolved = true
  isCanBeConsumed = false
  isCanBeDeclared = false
}

fun Configuration.declarable(
  visible: Boolean = false
) {
  isVisible = visible
  isCanBeResolved = false
  isCanBeConsumed = false
  isCanBeDeclared = true
}
//endregion

Run ./gradlew artifactViewFilesResolverTask or ./gradlew demoConfWindowsDebugResolver.

Observer that the resolved files do not match the expected value.
> Invalid resolution. Expected [windows-debug.txt] by was [test-jvm.jar, kotlin-stdlib-2.0.0.jar, annotations-13.0.jar]

Ideally it would be possible to tell Gradle to match (all? some?) attributes exactly. This would trigger a resolution error, because "Windows" != "windows".
The mismatch can be even more obscured when the attribute values are derived from non-String values. E.g. if an attribute value is supposed to be an enum, a plugin might accidentally do FooEnum.Windows.lowercase() in one location, but not in another.

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

I think there might be a few issues tied up in this:

ArtifactView doesn't distinguish between "expected" missing matches and failures. This makes it hard to express "I want exactly one" match
We try to fallback to "default" artifacts. I think this is where the jar is coming from.
Mismatches that do not fail resolution are hard to diagnose/notice

We want to make this better, but I'm not sure if a different resolution mode is what we want to do.  We've added the appropriate labels for this, but we're not going to directly work on this right now.


File object becomes a basic js object

Description
When we use the From component in a wrapper component and pass formData via props., the Form component transforms Props to State in componentWillReceiveProps  . Problem is when we use a custom widget with an input file, the File object is transformed to a basic object in mergeObjects function because the  File object is detected as an object.
I guess the solution is to exclude File from isObject function.
Do you think it's the way to go? I don't see any exception than File object which could be bad detected.
Steps to Reproduce

Open https://codesandbox.io/s/n4mlxwq3ml
Open the browser console
Choose a file
See in the console onChange event is triggered twice and the File object changes.

Expected behavior
The File object stays a File object
Actual behavior
The File object becomes a basic js object
Version
1.3.0

@oterral , yes, that makes sense, you can just add a check to see if the input is an instance of File. I'd merge a PR that does this!

@epicfaace sorry to bother you with this. When is the next release planned ?

@oterral Likely next week. For now, you could just do npm install -S git+https://github.com/mozilla-services/react-jsonschema-form.git#0f4889c22457edeb57991f48a88d8d32b2a93ca7 to get the changes from the latest commit.


Does this monitors data which was used by hotspot

I did not check.
Also it does not work well with VPNService (VPN or Firewall apps) as it counts traffic twice