I forgot the password any way to recover? 🥲 I have my personal family PICS in it.

Description
I forgot my password and I don't know what is it
To Reproduce
just forgot the password
Evidence
No response
App Version
<IP_ADDRESS>
OS Version
Win 11 PRO
Diagnostic information
No response

SecureFolderFS is designed to put the encryption keys in users' hands. In other words, there's no central entity to manage the encryption keys which would create distrust among the users. Your best bet in this situation would be to guess or brute-force the password.

SecureFolderFS is designed to put the encryption keys in users' hands. In other words, there's no central entity to manage the encryption keys which would create distrust among the users. Your best bet in this situation would be to guess or brute-force the password.

I do have some GPT custom created list of password which might be possibe combination? is there any way to try that on SecureFolderFS? like using bruteforce automation

There are probably UI tools available that'd help automate the copying and pasting process. However, if you're familiar with coding, this is the place where the encryption key is derived. (If the method .UnwrapKey() throws, it means that the password was incorrect)

There are probably UI tools available that'd help automate the copying and pasting process, though I'm not aware of any. However, if you're familiar with coding, this is the place where the encryption key is derived. (If the method .UnwrapKey() throws, it means that the password was incorrect)

Oh that's totally great, hey do you think I can reverse engineer this? 😬like Going thought code and other process since after encrypting it give use c_encryptionKey, c_macKey, salt and this too hmacsha256mac, using this can I do this? or is it impossible?

This is roughly the process that SFFS uses:
keystore = ReadDataFromFile("keystore.cfg");
kek = Argon2id.Derive(pass: password, salt: keystore.salt);

encKey = Rfc3394.Unwrap(key: kek, wrapped: keystore.c_encryptionKey);
macKey = Rfc3394.Unwrap(key: kek, wrapped: keystore.c_macKey);

Also, my friend has put together a simple console app that is a fork of this repo to help you with just that
https://github.com/taj-ny/SecureFolderFS/commit/ae3f40e89b2d862d67d4e946aab73f70abf50f64
You can clone their fork and build the project :)

Build with surface heuristics started at 23:20:20 Use build tool: C:\Users\soura\.dotnet\sdk\7.0.306\MSBuild.dll CONSOLE: MSBuild version 17.6.8+c70978d4d for .NET CONSOLE: Build started 22-08-2023 23:20:21. CONSOLE: Project "C:\Users\soura\AppData\Local\Temp\Nasobem.proj" on node 1 (default targets). CONSOLE: ControllerTarget: CONSOLE:   Run controller from C:\Program Files\JetBrains\Rider\r2r\2023.2.0R\5E757B832955A28ECC5806E9E8D5266\JetBrains.Platform.MsBuildTask.v17.dll 0>------- Started building project: SecureFolderFS.Shared 1>------- Started building project: SecureFolderFS.SourceGenerator SecureFolderFS.Shared -> C:\Users\soura\Downloads\Compressed\SecureFolderFS-bruteforce\SecureFolderFS-bruteforce\SecureFolderFS.Shared\bin\Debug\net7.0\SecureFolderFS.Shared.dll 0>------- Finished building project: SecureFolderFS.Shared. Succeeded: True. Errors: 0. Warnings: 0 2>------- Started building project: SecureFolderFS.Sdk.Storage 1>SecureFolderFS.SourceGenerator.csproj: Error NU1100 : Unable to resolve 'NETStandard.Library (>= 2.0.3)' for '.NETStandard,Version=v2.0'. 1>SecureFolderFS.SourceGenerator.csproj: Error NU1100 : Unable to resolve 'Microsoft.CodeAnalysis.CSharp (>= 4.6.0)' for '.NETStandard,Version=v2.0'. 1>SecureFolderFS.SourceGenerator.csproj: Error NU1100 : Unable to resolve 'Microsoft.CodeAnalysis.Analyzers (>= 3.3.4)' for '.NETStandard,Version=v2.0'. 1>SecureFolderFS.SourceGenerator.csproj: Error NU1100 : Unable to resolve 'PolySharp (>= 1.13.2)' for '.NETStandard,Version=v2.0'. 1>------- Finished building project: SecureFolderFS.SourceGenerator. Succeeded: False. Errors: 4. Warnings: 0 SecureFolderFS.Sdk.Storage -> C:\Users\soura\Downloads\Compressed\SecureFolderFS-bruteforce\SecureFolderFS-bruteforce\SecureFolderFS.Sdk.Storage\bin\Debug\net7.0\SecureFolderFS.Sdk.Storage.dll 2>------- Finished building project: SecureFolderFS.Sdk.Storage. Succeeded: True. Errors: 0. Warnings: 0 3>------- Started building project: SecureFolderFS.Core.FileSystem SecureFolderFS.Core.FileSystem -> C:\Users\soura\Downloads\Compressed\SecureFolderFS-bruteforce\SecureFolderFS-bruteforce\SecureFolderFS.Core.FileSystem\bin\Debug\net7.0\SecureFolderFS.Core.FileSystem.dll 3>------- Finished building project: SecureFolderFS.Core.FileSystem. Succeeded: True. Errors: 0. Warnings: 0 4>------- Started building project: SecureFolderFS.Core.Cryptography 4>SecureFolderFS.Core.Cryptography.csproj: Error NU1100 : Unable to resolve 'Konscious.Security.Cryptography.Argon2 (>= 1.3.0)' for 'net7.0'. 4>SecureFolderFS.Core.Cryptography.csproj: Error NU1100 : Unable to resolve 'Miscreant (>= 0.3.3)' for 'net7.0'. 4>SecureFolderFS.Core.Cryptography.csproj: Error NU1100 : Unable to resolve 'NSec.Cryptography (>= 22.4.0)' for 'net7.0'. 4>SecureFolderFS.Core.Cryptography.csproj: Error NU1100 : Unable to resolve 'RFC3394 (>= 1.0.0)' for 'net7.0'. 4>------- Finished building project: SecureFolderFS.Core.Cryptography. Succeeded: False. Errors: 4. Warnings: 0 Build completed in 00:00:04.158
Hey I'm getting this error? do you know why?

Do you have .NET 7.0 runtime installed? Or alternatively, you can try clearing nuget cache or clear the file found in %appdata%\NuGet\NuGet.Config

Do you have .NET 7.0 runtime installed? Or alternatively, you can try clearing nuget cache or clear the file found in %appdata%\NuGet\NuGet.Config

yea I have latest 7.0.4. though it wasn't installed, When I installed Jetbrain raider. I got 7.0.309 Version. and it wasn't detecting i guess. so I installed Manually 7.0.4 but still it was shoing same error.
and yea lemme try that.

yea I did. Nothing changed still same error

Did you clone recursively? Verify that folders inside the lib folder are not empty

Sure do that, Coz yea my lib was empty. so I reclone the repo. But I'm still getting same issue.

Can hou send me direct build release for brutforce? Please, seems I'm not able to do it

Sure! @uuc110
SecureFolderFS-bruteforce.zip

Thanks dude🙇🙏 I really appreciate your help. i gussed more than 500+ passwords still no reach. Seems I have to crack it, rather then guess it. by the way if there is a possible way to forgot password, by editing code or bypassing it. lemme know

as I said I have to crack it, can you tell me if I can know nonces ? it is require to decode it

I don't have any 'nonces' nor are there any backdoors to avoid the encryption

I don't have any 'nonces' nor are there any backdoors to avoid the encryption

Hey hi dude, I was trying to tinker with brutforcer, so was thinking does it support parallel Bruteforcing, or can i do something like that, like using rules and other stuff which we use in general for password cracking techniques


feat: Add Persist State Switch

Adds an optional Persist State Switch. When enabled, the switch allows the Stateful Scene switch to return to the last state just before restart whenever Home Assistant Restarts. However, if the entities related to an already on stateful scene changes between restarts, the off state (actual state) is shown on restart instead of unavailable or unknown state.

@hugobloem Could you kindly take a look at this? The new functionality to persist states only takes effect if the user enables the PersistStateAcrossRestarts switch for a Stateful Scene. Otherwise, they function as usual.

Thank you for this. I will have time over the weekend to look at this.

Thank you for this. I will have time over the weekend to look at this.

I have further added a check for the system to ensure the actual state before simply restoring to the last state. This should work properly now.


Running into state changes in policy when using All Severities

Describe the bug
I am using All Severities for the min_severity in our license and security policy. Every time I run terraform plan and terraform apply for code changes I see state changes to the security and license policy even though the resources were not touched.  Getting the license and security policy using the REST API shows that the min_severity value to be unknown when selecting All Severities in the UI. Instead of passing the string "All Severities" to the REST API the provider can pass the string "unknown" to avoid state changes on each terraform plan and apply when using All Severities for the min_severity of license or security policy.
Requirements for and issue
Example of state change.
  # module.xray_security_policy.security_policy will be updated in-place
~ resource "xray_security_policy" "security_policy" {
        id          = "security-policy"
        name        = "security-policy"
        # (6 unchanged attributes hidden)

      ~ rule {
            name     = "severity-rule"
            # (1 unchanged attribute hidden)

          + criteria {
              + fix_version_dependant = false
              + min_severity          = "All Severities"
            }
          - criteria {
              - fix_version_dependant = false -> null
              - min_severity          = "unknown" -> null
            }
            # (1 unchanged block hidden)
        }
    }

Expected behavior
There should be no state changes to a license or security policy if the resources have not been modified.
Additional context
Add any other context about the problem here.

@oallauddin Which version of Xray are you running? I am getting "All severities" from the API GET /xray/api/v2/policies and GET /xray/api/v2/policies/{name} with Xray 3.61.3
{
    "name": "Alex-Sec-Test",
    "type": "security",
    "author": "alexh",
    "rules": [
        {
            "name": "low-severity",
            "priority": 1,
            "actions": {
                "block_download": {
                    "unscanned": false,
                    "active": false
                }
            },
            "criteria": {
                "fix_version_dependant": false,
                "malicious_package": false,
                "min_severity": "All severities"
            }
        }
    ],
    "created": "2022-07-21T22:23:11.399Z",
    "modified": "2022-11-18T23:49:02.046Z"
}

@alexhung
Using Xray 3.57.6. Also it is a project based policy.
jf xr curl api/v1/system/version
{"xray_version":"3.57.6","xray_revision":"e1bb4e8"}

jf xr curl api/v2/policies/test-policy?projectKey=test
{"name":"test-policy","type":"security","author":"user","rules":[{"name":"test-rule","priority":1,"actions":{"block_download":{"unscanned":false,"active":false}},"criteria":{"fix_version_dependant":false,"min_severity":"Unknown"}}],"created":"2022-11-21T13:23:57.291Z","modified":"2022-11-21T13:26:13.919Z","project_key":"test"}

@oallauddin Odd. I wonder if Xray API is doing some strange thing where it uses "Unknown" if the min severity was default to "All Severity" (i.e. user never explicitly set it). I'll poke around some more.

@oallauddin So I can see that 'unknown' is in the payload sent to Xray UI API (POST /ui/api/v1/xray/ui/policies):
{
  "name": "Alex",
  "description": "",
  "type": "security",
  "rules": [
    {
      "name": "Alex",
      "criteria": {
        "malicious_package": false,
        "fix_version_dependant": false,
        "min_severity": "unknown"
      },
      "actions": {
        "webhooks": [],
        "mails": [],
        "block_download": {
          "active": false,
          "unscanned": false
        },
        "block_release_bundle_distribution": false,
        "fail_build": false,
        "notify_watch_recipients": false,
        "notify_deployer": false,
        "create_ticket_enabled": false
      },
      "priority": 1
    }
  ]
}

But when I use jf xr curl api/v2/policies/Alex I get 'All severities':
{
  "name": "Alex",
  "type": "security",
  "author": "alexh",
  "rules": [
    {
      "name": "Alex",
      "priority": 1,
      "actions": {
        "block_download": {
          "unscanned": false,
          "active": false
        }
      },
      "criteria": {
        "fix_version_dependant": false,
        "malicious_package": false,
        "min_severity": "All severities"
      }
    }
  ],
  "created": "2022-11-21T21:09:12.413Z",
  "modified": "2022-11-21T21:09:12.413Z"
}

Same with calling API directly.

@oallauddin Found the fix in the release note for 3.60.2.

XRAY-9271 | Fixed an issue whereby, Policy REST APIs returned the minimal severity criteria of all severities as "Unknown"  instead of "All Severities".


[Bug]: Value cannot be null. (Parameter 'id is a required property for CreateNotificationSuccessResponse and cannot be null')

What happened?
Getting the following error when trying to send a push notification
Value cannot be null. (Parameter 'id is a required property for CreateNotificationSuccessResponse and cannot be null')
public async Task SendNotificationToUser(string userid,string message)
{
Notification notification =new Notification(appId: "3bcfdf8e-d1aa-4fc1-9823-87fb8c19faa4");
//notification.AppId="3bcfdf8e-d1aa-4fc1-9823-87fb8c19faa4";
notification.Id=Guid.NewGuid().ToString();
notification.Contents =new StringMap();
notification.Contents.En=message;
notification.IncludeExternalUserIds=new List();
notification.IncludeExternalUserIds.Add(userid);
var result= await  _oneSignalApiService.SendNotification(notification);
return Ok(result);
}
Steps to reproduce?
Value cannot be null. (Parameter 'id is a required property for CreateNotificationSuccessResponse and cannot be null')

What did you expect to happen?
Value cannot be null. (Parameter 'id is a required property for CreateNotificationSuccessResponse and cannot be null')
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thank you for reporting we will look into this!


Update Emission and include routing

Adds the ability to have routes to some of our new Emission  VCs.

          1 Warning

:warning:
Needs testing on a Phone if change is non-trivial

  Generated by :no_entry_sign: Danger

Blocked on dep-ci, which I can live with


fix: regression in sensor.py

In fixing #70, the bug in the config_flow was fixed, but a change to the sensor introduced the exact same bug to entities. This PR reverts that sensor change.

Thanks!


Update apps.json: added Pocket Casts app

Adding Pocket Casts to the list of apps.

Thanks Paolo!

Hi, pocketcasts.png is missing in https://github.com/Podcastindex-org/web-ui/tree/master/server/assets

Thanks for the review.  We need to add a test for missing asset I suppose.

I'll open a new PR with the asset and I will also add open source 👍

Created a new PR here https://github.com/Podcastindex-org/web-ui/pull/357


3rd Party Data in Health Kit not pulling through API.

3rd Party Data in Health Kit not pulling through API. Even if Whoop data and/or Garmin data sits in Apple Health App, it cannot be pulled by the API
Reproduce: Connect Whoop or Garmin data into Apple Health Kit and try and view the data pulled in the API.
Does anyone else experience this issue?

@agwelford @mattshax I'm facing the same issue, do you have any progress on it?

@mattshax If you have actual Apple Health data as well as 3rd party data does it also fail to pull Apple Health data as well. I have a case where If a user has Oura ring sleep data + Apple health sleep data, their AH sleep data does not get pulled as well.


python3Packages.pyinsteon: init at 1.0.8

Motivation for this change
This is a Python package to interface with an Insteon Modem. It has been
tested to work with most USB or RS-232 serial based devices such as the
2413U, 2412S, 2448A7 and Hub models 2242 and 2245.
https://github.com/pyinsteon/pyinsteon
This is a Home Assistant dependency.
Things done

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

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

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

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109285 run on x86_64-linux 1

3 packages built:

python37Packages.pyinsteon
python38Packages.pyinsteon
python39Packages.pyinsteon

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109285 run on x86_64-linux 1

3 packages built:

python37Packages.pyinsteon
python38Packages.pyinsteon
python39Packages.pyinsteon


[SPAPRK-38192][CORE][TESTS] Use try-with-resources in Level/RocksDBSuite.java

What changes were proposed in this pull request?
countKeys method in LevelDBSuite use db.db().newIterator() to create a DBIterator instance, but there is no way to close it because the iterator not registered to LevelDB.iteratorTracker, and the similar issue also exists in RocksDBSuite, so  this pr use try-with-resources to ensure the iterator closed.
Why are the changes needed?
Bug fix.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA

cc @dongjoon-hyun

Thank you, @LuciferYang !

Thank you for update. Please make the PR description up-to-date too.

@LuciferYang . When you describe an issue, you had better put a bigger one first.
For example, LevelDB*.java was added via SPARK-20641 at Apache Spark 2.3.0 and everyone knows and is affected.
RocksDB*.java was added at master branch only and only active contributors (who are working on unreleased master branch) know.
The main different are

If you focus on RocksDB mainly in the PR description, we cannot backport this patch to the older release branches.
If you focus on LevelDB with the description and verification ways, we can backport this patch.

Could you refocus your PR description once more?

@dongjoon-hyun
At present, for RocksDBSuite, I can reproduce the issue stably, while for LevelDBSuite, I can only infer from the principle that it should have similar issue with RocksDBSuite.
Therefore, if the PR description focuses on LevelDBSuite, I can only speculate that it has issue in theory, and I can't provide the reproduction ways of LevelDBSuite for the time being.
Or should I change this pr back to the fix only for RocksDBSuite?

@dongjoon-hyun I updated the pr description to focus on LevelDBSuite first , but removed the manual test reproduction way. If need to change it again, please let me know.

Got it. Let me dig it more from my side. Thank you always.

Since the pr description has been updated, I copy a reproduction step for RocksDBSuite here:
I used Apple Silicon/M1 machine(MacBook Pro (13-inch, M1, 2020)) to reproduce this issue
The test steps are as follows：

clone a facebook/rocksdb code repository and switch to 6.29.fb branch, then build a rocksdbjni-6.29.1-osx.jar refer to RocksJava-Basics with WITH_LZ4 and WITH_ZSTD option enabled
change org.rocksdb:rocksdbjni in Spark pom.xml to use system scope and specify the path where systemPath is /xxx/rocksdb/java/target/rocksdbjni-6.29.1-osx.jar
delete assumeFalse(SystemUtils.IS_OS_MAC_OSX && SystemUtils.OS_ARCH.equals("aarch64")); in RocksDBSuite  condition and  ignore testCloseRocksDBIterator  because it has another issue.
run mvn commands:

 mvn clean test -pl common/kvstore -am -Dtest=org.apache.spark.util.kvstore.RocksDBSuite

Before
The VM crash as follows:
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd /spark-source/common/kvstore && /xxx/zulu8u312/zulu-8.jdk/Contents/Home/jre/bin/java -ea -Xmx4g -Xss4m -XX:MaxMetaspaceSize=2g -XX:ReservedCodeCacheSize=128m -XX:+IgnoreUnrecognizedVMOptions --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/sun.nio.cs=ALL-UNNAMED --add-opens=java.base/sun.security.action=ALL-UNNAMED --add-opens=java.base/sun.util.calendar=ALL-UNNAMED -Dio.netty.tryReflectionSetAccessible=true -jar /spark-source/common/kvstore/target/surefire/surefirebooter4807633958162555307.jar /spark-source/common/kvstore/target/surefire 2022-02-11T21-43-14_615-jvmRun1 surefire1545347115500361779tmp surefire_05480551952513893775tmp
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 134

After
[INFO] Running org.apache.spark.util.kvstore.RocksDBSuite
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.82 s - in org.apache.spark.util.kvstore.RocksDBSuite

At the same time, in order to verify whether leveldb will cause VM crash because DBIterator  is not closed, I try to delete some code related to resource release here and wait for the test results.

At the same time, in order to verify whether LevelDB will cause VM crash because DBIterator  is not closed, I try to delete some code related to resource release here and wait for the test results.

@dongjoon-hyun It seems that even if delete the registration process of iteratorTracker and delete the finalize() method in LevelDBIterator to not close LevelDBIterator at all, it will not cause VM crash on X86 platform, although it will certainly cause resource leak

At the same time, in order to verify whether LevelDB will cause VM crash because DBIterator  is not closed, I try to delete some code related to resource release here and wait for the test results.

@dongjoon-hyun It seems that even if delete the registration process of iteratorTracker and delete the finalize() method in LevelDBIterator to not close LevelDBIterator at all, it will not cause VM crash on X86 platform, although it will certainly cause resource leak

Merged to master for Apache Spark 3.3.

thanks all


Remove unused descriptor definition

Modified not to use Descriptor in cupy/cutensor.py while refactoring cutensor.py

pfnCI, test this please.

Jenkins CI test (for commit 646c46ac396ee3013c25f1d0741c8ff61817bb39, target branch master) failed with status FAILURE.

LGTM! Test failures are not related to this PR.


envoy doesn't support prefix_rewrite value as empty string value

Issue: envoy doesn't support prefix_rewrite value as empty string value
Steps to reproduce the issue

startup a http server on my local ip: <IP_ADDRESS>

# python3 -m http.server 8888
Serving HTTP on <IP_ADDRESS> port 8888 (http://<IP_ADDRESS>:8888/) ...

Wrote a envoy simple example configuration as below

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 10000
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          access_log:
          - name: envoy.access_loggers.stdout
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.access_loggers.stream.v3.StdoutAccessLog
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match:
                  prefix: "/foo"
                route:
                  prefix_rewrite: "/"
                  host_rewrite_literal: <IP_ADDRESS>
                  cluster: test_cluster

  clusters:
  - name: test_cluster
    type: LOGICAL_DNS
    # Comment out the following line to test on v6 networks
    dns_lookup_family: V4_ONLY
    load_assignment:
      cluster_name: test_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 8888

startup a envoy filter with above yaml

docker run --name=envoy-example -d -p 81:10000 -v /tmp/envoy.yaml:/etc/envoy/envoy.yaml envoyproxy/envoy:v1.23-latest

Access curl http://localhost:81/foo, it is ok, e.g.

# python3 -m http.server 8888
Serving HTTP on <IP_ADDRESS> port 8888 (http://<IP_ADDRESS>:8888/) ...
<IP_ADDRESS> - - [25/Aug/2022 11:42:19] "GET / HTTP/1.1" 200 -

Access  curl http://localhost:81/foo/a, reported 404

Serving HTTP on <IP_ADDRESS> port 8888 (http://<IP_ADDRESS>:8888/) ...
<IP_ADDRESS> - - [25/Aug/2022 11:42:19] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [25/Aug/2022 11:43:45] "GET //a HTTP/1.1" 404 -

the statusCode is correct, but from above log, the path is //a,  according to my assumption, there is an extra slash, my expectation of the path should be /

Try to solve it with configure the prefix_rewrite to empty string, e.g.

But unfortunately, it seems envoy doesn't have this prefix_rewrite: "" if  configure it as empty string.
So it doesn't work as expected, so i access curl http://localhost:81/foo again, the client reported
<IP_ADDRESS> - - [25/Aug/2022 11:50:11] "GET /foo HTTP/1.1" 404 -

We can see  prefix_rewrite: "" doesn't work.
Someone knows the reason why  prefix_rewrite: "" doesn't work for envoy?
If want to make  prefix_rewrite: "" works well, is it possible?
My goal as below if prefix_rewrite: "" works well
http://localhost:81/foo      -> http://<IP_ADDRESS>:8888
http://localhost:81/foo/a   -> http://<IP_ADDRESS>:8888/a
Then, the path changed from //a to /a

- match:
    prefix: "/foo"
  route:
    prefix_rewrite: "/"
    host_rewrite_literal: <IP_ADDRESS>
    cluster: test_cluster

Use only a single route will route "/prefix/a" to "//a" and forward it.  To route"/prefix/a" to "/a" and "/prefix" to "/", you need to handle all cases and use two routes.
Something like:
- match:
    prefix: "/foo/"
  route:
    prefix_rewrite: "/"
    host_rewrite_literal: <IP_ADDRESS>
    cluster: test_cluster
- match:
    prefix: "/foo"
  route:
    prefix_rewrite: "/"
    host_rewrite_literal: <IP_ADDRESS>
    cluster: test_cluster

Close as done


Unable to craft Machine Controller from Modular Machines

Recipe requires insulated gold cables which are produced in the multiblock.   Tech Reborn assembler no longer works.
Tech Reborn Electronic Circuit is also uncraftable
Version: 1.2.0 Beta

Nvm Tech Reborn Electronic Circuit is craftable my machine was gummed up with gold wires.  It seems only the different scaffoldings and the gold cables are currently not craftable in the tech reborn assembler when previously they were.

Thanks for the report, I'll be changing the advanced coil in the recipe!


HstWB Installer

Install instructions
https://github.com/henrikstengaard/hstwb-installer/wiki/Install-HstWB-Installer-for-Raspberry-Pi-OS-Lite
Git
https://github.com/henrikstengaard/hstwb-installer
Thanks

cant get that to work with all the other gui, and dealing with changing the kms and sound card. not going to mess with it


XGBoost example notebook uses deprecated dask-xgboost

This Dask Examples notebook uses the deprecated dask-xgboost rather than the native XGBoost integration.
Tweaking the notebook should be relatively straightforward by following the example code in this blog
import xgboost as xgb

# Create the XGBoost DMatrices
dtrain = xgb.dask.DaskDMatrix(client, X_train, y_train)
dtest = xgb.dask.DaskDMatrix(client, X_test, y_test)

# train the model
output = xgb.dask.train(
    client, params, dtrain, num_boost_round=4,
    evals=[(dtrain, 'train')]
)

# make predictions
y_pred = xgb.dask.predict(client, output, dtest)

From the dask-xgboost repo:
"Warning: Dask-XGBoost has been deprecated and is no longer maintained. The functionality of this project has been included directly in XGBoost. To use Dask and XGBoost together, please use xgboost.dask instead https://xgboost.readthedocs.io/en/latest/tutorials/dask.html."

I can make these changes and submit a PR

Thanks for surfacing this @rrpelgrim. A PR that updates that example to use xgboost.dask instead of dask_xgboost would be very welcome. Let me know if you know have any questions about that process


Passing extra data to VizPlugin

I have a custom viz plugin (https://superset.apache.org/docs/installation/building-custom-viz-plugins/).
Can i pass extra data to formData from python to this new plugin?

Form data is being controlled from the dashboard screen and cannot pass any additional props.


When you create a new room with visibility “private” it says there are 0 members

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app
Navigate to "+" > "New Room"
Select type Private and create

Expected Result:
Room owner should count as member too
Actual Result:
When you create a new room with visibility “private” it says there are 0 members
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.37-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Upwork URL: https://www.upwork.com/jobs/~0125be97d30995bc22
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1644001144118679
View all open jobs on GitHub

Triggered auto assignment to @francoisl (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

This also applies impacts "Restricted" rooms too fwiw

@MitchExpensify I didn't experience this when I created a restricted room. Are. you seeing it when you do?

Yes

User<EMAIL_ADDRESS>

I can reproduce too. The issue seems to be that the participants list is built with the function getParticipantEmailsFromReport,  which purposefully ignores the current user.

Triggered auto assignment to @trjExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Proposal
Here We can use isChatRoom() and if it's a room we will not remove currentUserEmail. It will fix the problem.
function getParticipantEmailsFromReport({sharedReportList, reportNameValuePairs}) {
    const emailArray = _.map(sharedReportList, participant => participant.email);
    return ReportUtils.isChatRoom(reportNameValuePairs) ? emailArray : _.without(emailArray, currentUserEmail);
}

Job on upwork here: https://www.upwork.com/jobs/~0125be97d30995bc22

I believe we also need to show the current user in members page as we will be counting ourself as a member and it will be confusing if we show 1 written outside but doesn't show any user inside members page. Here's a vid :-
https://user-images.githubusercontent.com/83179295/153244087-b90abfb7-e7d9-49db-9d4e-3fb1925458a1.mov

I believe we also need to show the current user in members page

Makes sense @thesahindia

🎀👀🎀 C+ reviewed
@puneetlath  I like @thesahindia's proposal.

@puneetlath, in one on one chats we don't wanna show current user in chat header so we don't include current user.

Ok got it. It makes more sense to me that the default behavior of getParticipantEmailsFromReport would be to return all participants on the report unfiltered. And then anyone that is using it can choose to remove the current user from the list if they want. Perhaps via a utility function that takes a list of emails and removes the current user's email from the list.

@puneetlath, will do the same. Should I update my proposal?

Yes please.

Updated Proposal
We can make a function like below and we can use it for getting participants emails excluding current user email.
 function removeCurrentUserEmail(participantEmails) {
    return _.without(participantEmails, currentUserEmail);
}

I thought about using a flag in getParticipantEmailsFromReport but for getting participants we don't call it directly we use it in getSimplifiedReportObject and we use getSimplifiedReportObject further in some other function so it would not be a good idea to do so.
I found we want to exclude current user literally everywhere where we are showing the users and we only need the current user in rooms so I think we should reconsider using isChatRoom() like I had proposed as it can solve this without making changes in all the components where we don't want current user.
cc: @puneetlath

📣 @thesahindia You have been assigned to this job by @puneetlath!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

👋 @thesahindia can you let me know once you've applied to the job on Upwork, please? (As a heads up, I'll be OoO next week, so I might be a tad slow to accept and finalise the offer)

@trjExpensify, I have applied to the job.

Done! 👍

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.39-3 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/7720

If no regressions arise, payment will be issued on 2022-03-02. :confetti_ball:

@thesahindia I've paid this out for you. @rushatgabhane, you hadn't applied, so I've sent you an offer for the C+. Let me know once accepted and then I'll settle and close this out. Thanks!

Haha, wow. That was suspiciously fast, @rushatgabhane. 😅 Settled, closing out!

I might have a bot 🤖 ;)


shortcut to switch preview on/off

Category

[x ] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[ ] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x ] bash
[ ] zsh
[ ] fish

preview is indeed very practical in many cases but when the file name is very long, it is hidden by the preview pane. an "online" key shortcut to switch the pane on/off would greatly help

I think --bind='F2:toggle-preview' is what you're looking for.
You can of course substitute F2 for whatever key (or key combo) you like.

Works like a charm. Thank you.


Update ACR to 2017-03-01

Codecov Report

Merging #1038 into master will increase coverage by 0.07%.
The diff coverage is 82.46%.

@@            Coverage Diff             @@
##           master    #1038      +/-   ##
==========================================
+ Coverage   57.58%   57.66%   +0.07%
==========================================
  Files        1961     1971      +10
  Lines       54243    54353     +110
==========================================
+ Hits        31238    31343     +105
- Misses      23005    23010       +5

Impacted Files
Coverage Δ

...rregistry/azure/mgmt/containerregistry/__init__.py
100% <ø> (ø)
:white_check_mark:

...ainerregistry/models/registry_update_parameters.py
100% <ø> (+42.85%)
:white_check_mark:

...inerregistry/models/registry_name_check_request.py
100% <ø> (ø)
:white_check_mark:

...re/mgmt/containerregistry/models/registry_paged.py
100% <ø> (ø)
:white_check_mark:

...ry/azure/mgmt/containerregistry/models/resource.py
100% <ø> (ø)
:white_check_mark:

...t/containerregistry/models/registry_name_status.py
100% <ø> (ø)
:white_check_mark:

...erregistry/container_registry_management_client.py
100% <100%> (+2.7%)
:white_check_mark:

...ry/azure/mgmt/containerregistry/models/__init__.py
100% <100%> (ø)
:white_check_mark:

...egistry/azure/mgmt/containerregistry/models/sku.py
100% <100%> (ø)

...ainerregistry/models/registry_create_parameters.py
100% <100%> (ø)

... and 26 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 d84552e...55090c2. Read the comment docs.


Unable to use custom scalar JSON fields

I am trying to use Pothos with Prisma and Apollo Server to replace usage of Nexus.
My builder looks like this:
import GraphQLJSON from "graphql-type-json";

export const builder = new SchemaBuilder<{
	Context: Context;
  PrismaTypes: PrismaTypes;
	Scalars: {
    Date: {
      Input: Date;
      Output: Date;
    };
		JSON: {
			Input: Prisma.JsonValue;
			Output: Prisma.JsonValue;
		}
  };
}>({
	plugins: [ PrismaPlugin ],
	prisma: {
		client: (ctx) => (ctx.prisma),
		dmmf: (prisma as unknown as { _baseDmmf: Prisma.DMMF.Document })._baseDmmf
	}
});

builder.scalarType("Date", {
	serialize: (date: any) => date.toISOString(),
	parseValue: (date: any) => new Date(date)
});
builder.addScalarType("JSON", GraphQLJSON, {});

Mutation looks like this
builder.mutationField("createUser", (t) =>
	t.prismaField({
		type: "User",
		nullable: false,
		args: {
			details: t.arg({ type: "JSON", required: true })
		},

But when I use it in a mutation argument and run it in Playground I get the below error:
TypeError: Cannot read properties of undefined (reading 'name')
    at isValidEnumValue (~/node_modules/@prisma/client/runtime/index.js:42821:61)
    at getGraphQLType (~/node_modules/@prisma/client/runtime/index.js:42770:7)
    at hasCorrectScalarType (~/node_modules/@prisma/client/runtime/index.js:48666:23)
    at scalarToArg (~/node_modules/@prisma/client/runtime/index.js:48962:7)
    at tryInferArgs (~/node_modules/@prisma/client/runtime/index.js:48890:14)
    at valueToArg (~/node_modules/@prisma/client/runtime/index.js:48752:16)
    at ~/node_modules/@prisma/client/runtime/index.js:49000:18
    at Array.reduce (<anonymous>)
    at objectToArgs (~/node_modules/@prisma/client/runtime/index.js:48980:28)
    at tryInferArgs (~/node_modules/@prisma/client/runtime/index.js:48882:40) {
  clientVersion: '4.0.0'
}

Is there something I'm doing wrong here?
I have a feeling it's related to the JSON scalar not being recognised

Hey, this error looks like it's coming from the prisma client.  It's hard to tell from the context provided, but it looks like the issue is that something being passed a prisma query is not valid.
I don't think this error is directly related to using a JSON scalar in pothos.
I don't see enough information to know what's going on here, but based in the question, one possibility is that you are using a JSON scalar field to pass a values directly into the prisma client from a json argument.  If this is the case, I would recommend trying to log out the value before passing it to prisma, to see if the value is what you expect.  If this is not the case, maybe providing a more complete example of what you are doing (and when the error is occurring  (start up, when running a specific query, etc) might be helpful.

It seems like it wasn't getting recognised as a JSON object until parsing and stringifying

glad you figured it out!


(Small) Make report download button download with the right pipeline version

Small change to download the right "pipeline version report" with the report download button.
Doesn't include the cookie changes.

Where does it consume the pipeline_version param? It seems to me like that part is missing

it's in
  def select_pipeline_run(sample)
    if params[:pipeline_version].blank?
      sample.pipeline_runs.first
    else
      sample.pipeline_run_by_version(params[:pipeline_version])
    end
  end

I see. I got thrown off by the that select_pipeline_run in the helper doesn't take params as an argument -- didn't realize it's a controller function


BUG: Make.md breaks 'Files: Reveal current file in navigation' function of Obsidian

ENVIRONMENT:
Windows 11 Home
Version 23H2
OS build 22631.2792
SYSTEM INFO:
Obsidian version: v1.4.16
Installer version: v1.4.13
Operating system: Windows 10 Home 10.0.22631
Login status: logged in
Catalyst license: none
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 1
Restricted mode: off
Plugins installed: 51
Plugins enabled: 2
1: MAKE.md v0.8.14
2: Excalidraw v2.0.8
Make.md breaks 'Files: Reveal current file in navigation' function of Obsidian
The plugin makes it so when the command 'Files: Reveal current file in navigation' is run it no longer shows where the note is in the note explorer.
To Reproduce
Steps to reproduce the behavior:

Install and enable Make.md obsidian plug in
Open Obsidian
Press "ctrl + p" to open command input window
Search "Files: Reveal current file in navigation" and run it

Expected behavior
The current note location will be revealed in the File Explorer and is highlighted.
But currently it takes the user to the Make.md Space Window without any action into showing the location of the current note/file being accessed.
Screenshots

Command to locate note in file explorer "Files: Reveal current file in navigation"

Bad Outcome: when command is run with Make.md plugin on (taken to Make.md Spaces window on the left without showing the location of the current note.

Good Outcome: when command is run without Make.md plugin on (taken to the folder with the current note being accessed on the left and highlighted!)
Additional Context
Finding files quickly and organizing them on Obsidian is very important to me and which is why I even downloaded Make.md in the first place. Please help me in placing a fix for this issue 😓

You can turn on “Compatibility Mode” in settings if you want to continue using the File Explorer as your main explorer

You can turn on “Compatibility Mode” in settings if you want to continue using the File Explorer as your main explorer

Thank you! This worked 😁


feat: miscellaneous linear algebra lemmas

Split out from https://github.com/leanprover-community/mathlib4/pull/7963

GitHub was flaking and bors crashed so we need to try this again
bors merge


Close Dropdown on click inside

I would like to be able to cause an open dropdown to close when an item inside it is clicked.
There does not seem to be a way to do that without managing the open state manually.

I can do document.body.click() in the onClick of Dropdown.Item as a workaround


add mshooting to exp03

It performed better on the Lorenz system compared to the PyTorch implementation in torchdyn. However, when it came to the GravitationalDataset, it was slower than the baseline odeint. One possible explanation is that the complexity of the get_hnn_dynamics function hinders parallelization with jax.vmap.
(deer) ~/qpert$ time python experiments/03_hnn_ode/mshooting.py

real    0m3.888s
user    0m5.202s
sys     0m1.004s

(dyn) ~/torchdyn$ time python /home/qzhu/torchdyn/tutorials/module4-model/m4c.py

real    0m6.906s
user    0m7.727s
sys     0m1.127s


substitute{,All,AllFiles}: move to pkgs/by-name.

Description of changes
RFC 140 will eventually move everything, but it's nice to move things that can be moved.
Things done

[x] nixpkgs-review rev HEAD (did no rebuilds).
[x] Fits CONTRIBUTING.md.

pkgs.substitute: This attribute defined by pkgs/by-name/su/substitute/package.nix is not a derivation
pkgs.substituteAll: This attribute defined by pkgs/by-name/su/substituteAll/package.nix is not a derivation
pkgs.substituteAllFiles: This attribute defined by pkgs/by-name/su/substituteAllFiles/package.nix is not a derivation

You know, I thought that this was allowed, but I was the one who CRed these changes!


Revert "Roll Engine from ced58ef9c13e to 86dacc0aad71 (9 revisions)"

This roll caused post-commit test failures like https://ci.chromium.org/p/flutter/builders/prod/Mac_android new_gallery__transition_perf/1556
Reverts flutter/flutter#84805
Investigation at https://github.com/flutter/flutter/issues/84813

Merging to green the build.


Duplicate and move pages ( coming soon )

Hi,
We are aware that we have an alternative to carry out these two actions, but what is the forecast for these two features to be working on pages list module?

FYI: These buttons should also obey CRUD ACL.

Please follow the progress on https://github.com/trilbymedia/grav-plugin-flex-objects/issues/81


Update README.md

Add anime into readme.
Could you also create a pull request in my repository? https://github.com/markxiaotao/AttractingContributors-Game/blob/main/README.md

LGTM

OK!
I create a PR later.

sorry.
conflict my repo after merge this PR.
Could you re clone my repo and make another branch?
Finally modify readme file in your branch and pull requests?


Make module runnable with python -m lama_cleaner

Closes #415

Thank you for the detailed explanation in the issue and your PR!


Unable to run tests

Unit tests fail on
cross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run
Error is
Error: Cannot find module "@/components/Hello"   at webpack:///test/unit/specs/Hello.spec.js:2:0 <- index.js:14309

At the moment, vue-datasource it does not contain unit tests, that's why it fails.
It's a priority feature 👍

Oh, too bad. I am looking for a VueJS project which has unit tests. I want to follow a good example.
On 2017-10-30, 3:03 PM, "Javier Diaz"<EMAIL_ADDRESS>wrote:
At the moment, vue-datasource it does not contain unit tests, that's why it fails.
It's a priority feature
👍
—
You are receiving this because you authored the thread.
Reply to this email directly,
view it on GitHub <https://github.com/coderdiaz/vue-datasource/issues/57#issuecomment-340551011>, or
mute the thread <https://github.com/notifications/unsubscribe-auth/AWmr9HVWVGgNtnd3lZLnufFWP2iFD0zSks5sxh2VgaJpZM4QLsI4>.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/coderdiaz/vue-datasource","title":"coderdiaz/vue-datasource","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/coderdiaz/vue-datasource"}},"updates":{"snippets":[{"icon":"PERSON","message":"@coderdiaz in #57: At the moment, `vue-datasource` it does not contain unit tests, that's why it fails.\r\nIt's a priority feature 👍 \r\n"}],"action":{"name":"View Issue","url":"https://github.com/coderdiaz/vue-datasource/issues/57#issuecomment-340551011"}}}


freezes while working in jupyter notebook

Does this issue occur when all extensions are disabled?: Didn't try

VS Code Version: 1.67.1
OS Version: windows 11

Steps to Reproduce:

Open new python Jupyter notebook
Write few lines of code
VS code  #freezes

more notebook issues. tried creating a python file and working in that but then get "Command 'pythonindent.newlineAndIndent' not found",  "command 'python.execSelectionInTreminal' not found". like god damn. install the daily updates and they just break more of the things!

This started happening to me today. Yesterday Notebooks were working fine.
On Windows, add a new cell then start adding code or add new lines to an old cell, get a dialog that says the app is not responding.
Was there an update yesterday?

Can anyone try disabling all extensions and see if you can stably reproduce? It would also help if we can get some logs by following https://github.com/microsoft/vscode/wiki/Performance-Issues , thank you all in advance

I also wonder if this is a duplicate of https://github.com/microsoft/vscode/issues/149412, can you try disable the Pylance extension and see if this still reproduces?

I disabled everything and step-by-step enabled the extensions. Unfortunately I could not reproduce the issue, i. e. now with all extensions back to enabled the issue did not persist.


[ParseableInterfaces] Short-circuit module loading in the PIML

Previously, the ParseableInterfaceModuleLoader relied on the assumption
that, if it returned errc::not_supported, it would fall through the
search paths and then move on to the SerializedModuleLoader. This did
not anticipate the possibility of a valid .swiftinterface coming later
in the search paths, which can cause issues for the standard library
which is in the resource-dir and should always be loaded from there.
Instead, make the module loading explicitly short-circuit when seeing
errc::not_supported, and document it.
Also add some more logging throughout discoverLoadableModule so we can
more easily catch issues like this in the future.
Fixes rdar://49479386
(Cherry-pick of #23857 to 5.1)

@swift-ci please test


Executable trace feature

Description of changes:
This PR adds the executable trace feature for improving users' debugging experience after verification failures. With the --gen-exe-trace flag, Kani will print out a Rust unit test that contains 1) concrete values for all calls to kani::any and 2) a call to the failed proof harness. The user can then debug their failing proof harness like they would with any normal Rust unit test. With an optional --add-exe-trace-to-src flag, Kani will even add the unit test directly to the user's source code.
To use this feature on a test crate:

Add this to your Cargo.toml:

[dev-dependencies]
kani = { path = "{path_to_kani}/library/kani", features = ["exe_trace"] }

Make sure your code isn't hidden under a cfg(kani) feature flag.

Resolved issues:
Implements recommended approach in #1388.
Call-outs:

New any_raw: After #1415, any_raw_internal will only be called on primitive types. These show up nicely in the CBMC output trace, removing the need for a complicated parser or changing the lowest level non-determinism to a byte array.
Performance:  On the verification side, performance should stay the exact same. On the post-processing side, we only add the --trace flag to CBMC when the user runs with --gen-exe-trace. This flag adds a bit more overhead to CBMC post-processing, which scales with the length of the trace. We have been able to run this feature on fairly large traces (100s of states) without much of a noticeable performance difference.
slice-formula: Currently, if a variable uses a kani::any assignment, but that variable isn't present in the verification conditions, CBMC doesn't have a concrete value for it in the output trace. To fix this, we would likely need to disable --slice-formula when we run CBMC with --trace. See #1252.
generic_const_expr: We needed this incomplete feature to take the size_of a generic type. However, after #1415, if we only call any_raw_internal using macros on primitive types, we could remove this and add the size as a type parameter to any_raw_internal.

Testing:
This change has an end-to-end UI test that checks to see if the correct concrete values are parsed and placed into a test case. We also manually tested this feature on a few different test harnesses. In the future, we plan to add the following tests:

A custom test that uses the --add-exe-trace-to-src feature and runs the unit test to verify that assertions actually fail. For now, we manually test this.
Unit tests for the exe_trace module in the kani-driver.

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[x] Methods or procedures are documented
[x] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

TODO: Match based on property IDs

TODO: In parsing, only add 1 failing assertion to det vals. For the others, add warning that we can only handle one assertion. For every failing things, add warnings too.

@adpaco-aws can you take a look at the changes to kani-driver/src/cbmc_output_parser.rs?


Share state between hook functions for directives

What problem does this feature solve?
In some situations it is necessary to share state between hook functions on directives. This is particularly useful for directives that attach and detach event listeners on elements.
Consider the following example of a v-drag directive: v-drag.
The listener that gets attached to the element requires access to values provided in the bind hook (eg element, modifiers etc.). This in itself is not a problem until that same listener has to be removed from the element in the unbind hook. In order to remove the event listener from the element I need to ensure I can get a reference to it from the unbind hook.
Perhaps I've gone about this the wrong way, but the only solution I could come up with is registering the listener against it's element in a persistent weakmap in bind and then finding the listener again in unbind using the element.
This problem would be alleviated by simply attaching the listener to this in the bind hook and detaching in unbind by getting the listener from this.
What does the proposed API look like?
Implement a data function on a directive to register (unreactive) state.
Vue.directive("sample", {

    data() {
        return {
            dragEnterListener: null
        };
    },

    bind(element) {
        this.dragEnterListener = (event) => {};
        element.addEventListener("dragenter", this.dragEnterListener);
    },

    unbind(element) {
        element.removeEventListener("dragenter", this.dragEnterListener);
    }

});

This is nice and neat, 👍, considering all my data-* attributes and temporary variables outside 😂.

Not sure I understand a need for that. Looking at your example, why not just wrap it in a component just handles drag events?
<template>

<slot></slot>

</template>

The goto solution is to save state in the HTML element, but as @sirlancelot said, we want to keep directives simple and limit their responsibility. If they become more complex, using a component is the way to go

Adding to what @posva said: Directive had this ability in Vue 1.0, and we deliberately removed it because essentially, custom directives in Vue 1.0 where too similar to components in their abilities, which made it unclear when to use what.
In Vue 2.0, we decided to make the destinction more clear: If you need state, you should generally use a component, not a directive. Directives' responsibilities are reduced to low-level DOM work. Higher level woirk should be done with components.
If the need for state in a directive arises in an edge case, you can use the element to store it as a workaround.

If you want to manage some semi-complicated state in your directive, you could use a solution like this:
const statefulDirective = (() => {
	const state = new WeakMap()
	return {
		bind(el) {
			const data = {}
			state.set(el, data)
		},
		update(el) {
			const data = state.get(el)
		},
		unbind(el) {
			state.delete(el)
		}
	}
})()

It's a slippery slope though so take care!

What about listeners or intervals/timeouts? It's not a state but we need to store them somehow so they could be cleared during unbind.

You can either store it directly on the element or save it in a Map, using the element as the key.

@cztomsik It's still on you to do cleanup, the code sample I provided only describes how to share a common state between different hook calls. You'll want to add your own cleanup during unbind.

I'm running into this issue for a drag and drop directives as well.  The reason we don't want to use a component is because a component forces you to add another div around everything.  You can't have a component just be a .  For example, if I have a  and I want to be able to drag and drop  elements, creating a whole new component isn't a good idea because that component is going to have to have a div or something wrapping the  elements which will mess it up.

creating a whole new component isn't a good idea because that component is going to have to have a div or something wrapping the
 elements which will mess it up.

You can use the component tag and the is property:
// MyWrapper.vue
<template>
  <component :is="is">
    <slot />
  </component>
</template>

// Somewhere else
<template>

    <MyWrapper is="ul">

some

    </MyWrapper>

</template>

@sirlancelot solution doesn't work for me because I need a separate state for each instance of the directive.

The only case where that wouldn't work is if you had multiple instances of the directive on the same element.  If you need to have multiple instances of the directive on the same element, consider making a compound key using the element and some other property.

Component has isolated scope.  Lets say you want to add simple drag and drop or some very generic feature, as soon as you create components for them you get into the scope mess. You now have to deal with all the props pass through and such. Directive IS the easy way to get around all that especially for features that should not have anything to do with scope. Otherwise, you should allow easy transparent component.

Component has isolated scope.  Lets say you want to add simple drag and drop or some very generic feature, as soon as you create components for them you get into the scope mess. You now have to deal with all the props pass through and such. Directive IS the easy way to get around all that especially for features that should not have anything to do with scope. Otherwise, you should allow easy transparent component.

And this was the power of AngularJS. I currently have some problems with custom directives, where we want to make it easy to do form validation WITHOUT needing to add all these component wrappers. So if we could add a custom directive that handles it, it will be solved, self-contained, and very easy and clear to add to a form. I understand that the decision is partly based on the fact that by allowing this, directives could get hard, but it's up to the consumer to decide how far to go, no?

Not sure this is the right way, but i've attached function directly to el
Vue.directive('scroll', {   inserted: (el, binding) => {     el.fnc = evt => {       binding.value(evt, el)     }     window.addEventListener('scroll', el.fnc, { passive: true })   },   unbind: el => {     window.removeEventListener('scroll', el.fnc);     delete el.fnc;   }, })

The ideal way to handle this is to use a symbol to store your state in the element.  That way you will avoid naming conflicts, your value will be encapsulated, and the entry will not get enumerated.
const key = Symbol()

Vue.directive('scroll', {
  inserted: (el, binding) => {
      el[key] = { foo: 'bar' } // <--- your state here
  }
}

I think being able to declare state in directives can be useful for many applications. More so with composition api in mind. Directives can be used to appropriately assign  attributes and events to elements of a layout that should contain a specialized behavior. Although the behavior can be implemented by the composition api, there is still a work to assign the variables and functions to the elements in the template of components. Libraries react that uses hook to power components such as react-table are examples of this problem.
Having state in directives means that fine-grained behavior can be implemented and inserted seamlessly into elements with losing control over your layout, as it can happen with components.
Today composition api and directives can be used together to provide such behaviors but there is still a need to use both in client code, whereas directives could handle the work with state alone.
Imagine for example useful directives for implementing a behavior for multiselects, such as v-select, v-option, v-search-input. That way we would have control over the layout and facilities to include behavior.

For comparison, Svelte directives are functions, and you can save state in a function closure.
For example, here is a directive for "click outside the element" event.
// click_outside.js
export function clickOutside(node) {
  const handleClick = (event) => {
    if (!node.contains(event.target)) {
      node.dispatchEvent(new CustomEvent("outclick"));
    }
  };
  document.addEventListener("click", handleClick, true);
  return {
    destroy() {
      document.removeEventListener("click", handleClick, true);
    }
  };
}

Usage:

{#if showModal}

 (showModal = false)}>
    Click outside me!

{/if}

It makes directive code less straightforward then in Vue, but you don't need to stuck data into the DOM element.
https://svelte.dev/tutorial/actions

Adding it to the element sounds like a good idea, but if we want directives with specified generic parameters (like HTMLElement), we have to manually cast to any before adding/removing. Consider the following example:
type Bindings = (width: number, height: number) => unknown;

const observerKey = Symbol('Key for ResizeObserver of the element');

export const vResized: Directive<HTMLElement, Bindings> = {
  mounted: (el, binding) => {
    const observer = new ResizeObserver((entries: ResizeObserverEntry[]) => {
      const rect = entries[0].contentRect;
      binding.value?.(rect.width, rect.height);
    });

    observer.observe(el);
    (el as any)[observerKey] = observer;
  },
  unmounted: (el) => {
    const element = el as any;
    const observer: ResizeObserver = element[observerKey];
    observer.disconnect();
    delete element[observerKey];
  }
};

We either have to cast from HTMLElement to any or use any instead of HTMLElement. Both kind of inconvenient.
As a side note, these kind of functionalities are better done by a directive instead of a component. As a mental model, directives are meant to be placed on elements, achieving easy composition. Can be worked around with components, but IMO directives are a better fit for these operations.

Thanks @csisy - This was a really helpful comment.
Note that if you want to avoid the as any with TypeScript you can extend HTMLElement like so:
interface HasResizeObserver {
	[observerKey]?: InstanceType<typeof ResizeObserver>;
}

export const vResized: Directive<HTMLElement & HasResizeObserver, Bindings> = {
    // ...
}


[Automation] Generate SDK based on TypeSpec 0.13.6

[Automation] Generate SDK based on TypeSpec 0.13.6

a patch release upon 0.13.5, mainly for bug fixes about union as extensible enum (see https://github.com/Azure/azure-rest-api-specs/pull/27687)

/check-enforcer evaluate


Add jetbrains to sponsors.json

@patrick91

[x] seeing that we have 4 platinum max, the last one now gets into the second line. Can we make each platinum logo bigger, occupying 2x2 instead?
[x] I am also messing up with the types of components/sponsor-tiers/sponsor-tiers.tsx

all done!


Additional fiat rates

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
https://github.com/JoinSEEDS/seeds_light_wallet/issues/478
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer

Keeping our main access on the EU Central Bank since fixer has an API key

🙈 Screenshots
👯♀ Paired with
nobody

wrong branch...


Sampling value for tracing configuration cannot be overriden by deployment metadata specification using proxy.istio.io/config annotation

Bug description
Related documentation:
https://istio.io/latest/docs/tasks/observability/distributed-tracing/configurability/#create-a-meshconfig-with-trace-settings
No tracing data of the pods that have been overriden by proxy.istio.io/config annotation could be sent to / viewed on jaeger, when sampling value is specified in deployment metadata specification using proxy.istio.io/config annotation. There is no problem when only meshConfig is used / configured.
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    defaultConfig:
      tracing:
        sampling: 20

Deployment metadata:
spec:
  template:
    metadata:
      annotations:
        proxy.istio.io/config: |
          tracing:
            sampling: 100

Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[X ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ X] Virtual Machine
[ ] Multi Control Plane
Expected behavior
The meshConfig sampling value (in this case 20) should be overridden by using proxy.istio.io/config annotation (100)  and tracing data should be collected by jaeger.
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
istioctl:
client version: 1.8.1
control plane version: 1.8.1
data plane version: 1.8.1 (5 proxies)
kubectl:
Client Version: v1.19.0
Server Version: v1.20.0
minikube
version: v1.16.0
How was Istio installed?
via istioctl
Environment where the bug was observed (cloud vendor, OS, etc)
Ubuntu 20.04
bug-report.zip

I can confirm this is broken. We took the productpage deployment from the bookinfo example and tried this setting. It looks like the annotation is replacing the tracing config, rather than being merged with it. When that happens, the cluster-level setting for the tracer endpoint goes away.
The "good" config (no custom annotation) configures the proxy like this:
            "PROXY_CONFIG": {
              "binaryPath": "/usr/local/bin/envoy",
              "concurrency": 2,
              "configPath": "./etc/istio/proxy",
              "controlPlaneAuthPolicy": "MUTUAL_TLS",
              "discoveryAddress": "istiod.istio-system.svc:15012",
              "drainDuration": "45s",
              "envoyAccessLogService": {},
              "envoyMetricsService": {},
              "parentShutdownDuration": "60s",
              "proxyAdminPort": 15000,
              "proxyMetadata": {
                "DNS_AGENT": ""
              },
              "serviceCluster": "productpage.bookinfo-example",
              "statNameLength": 189,
              "statusPort": 15020,
              "terminationDrainDuration": "5s",
              "tracing": {
                "zipkin": {
                  "address": "collector.jaeger:9411"
                }
              }
            },

Meanwhile once you add in the annotation, we get this new proxy config that is missing the zipkin address:
    "PROXY_CONFIG": {
              "binaryPath": "/usr/local/bin/envoy",
              "concurrency": 2,
              "configPath": "./etc/istio/proxy",
              "controlPlaneAuthPolicy": "MUTUAL_TLS",
              "discoveryAddress": "istiod.istio-system.svc:15012",
              "drainDuration": "45s",
              "envoyAccessLogService": {},
              "envoyMetricsService": {},
              "parentShutdownDuration": "60s",
              "proxyAdminPort": 15000,
              "proxyMetadata": {
                "DNS_AGENT": ""
              },
              "serviceCluster": "productpage.bookinfo-example",
              "statNameLength": 189,
              "statusPort": 15020,
              "terminationDrainDuration": "5s",
              "tracing": {
                "sampling": 100
              }
            },

I can confirm this is broken. We took the productpage deployment from the bookinfo example and tried this setting. It looks like the annotation is replacing the tracing config, rather than being merged with it. When that happens, the cluster-level setting for the tracer endpoint goes away.
The "good" config (no custom annotation) configures the proxy like this:
            "PROXY_CONFIG": {
              "binaryPath": "/usr/local/bin/envoy",
              "concurrency": 2,
              "configPath": "./etc/istio/proxy",
              "controlPlaneAuthPolicy": "MUTUAL_TLS",
              "discoveryAddress": "istiod.istio-system.svc:15012",
              "drainDuration": "45s",
              "envoyAccessLogService": {},
              "envoyMetricsService": {},
              "parentShutdownDuration": "60s",
              "proxyAdminPort": 15000,
              "proxyMetadata": {
                "DNS_AGENT": ""
              },
              "serviceCluster": "productpage.bookinfo-example",
              "statNameLength": 189,
              "statusPort": 15020,
              "terminationDrainDuration": "5s",
              "tracing": {
                "zipkin": {
                  "address": "collector.jaeger:9411"
                }
              }
            },

Meanwhile once you add in the annotation, we get this new proxy config that is missing the zipkin address:
    "PROXY_CONFIG": {
              "binaryPath": "/usr/local/bin/envoy",
              "concurrency": 2,
              "configPath": "./etc/istio/proxy",
              "controlPlaneAuthPolicy": "MUTUAL_TLS",
              "discoveryAddress": "istiod.istio-system.svc:15012",
              "drainDuration": "45s",
              "envoyAccessLogService": {},
              "envoyMetricsService": {},
              "parentShutdownDuration": "60s",
              "proxyAdminPort": 15000,
              "proxyMetadata": {
                "DNS_AGENT": ""
              },
              "serviceCluster": "productpage.bookinfo-example",
              "statNameLength": 189,
              "statusPort": 15020,
              "terminationDrainDuration": "5s",
              "tracing": {
                "sampling": 100
              }
            },

Ok - I see at https://istio.io/latest/docs/tasks/observability/distributed-tracing/configurability/#available-tracing-configurations this quote:

This probably needs to be called out more loudly - its very easy to gloss over that section and skip right to the https://istio.io/latest/docs/tasks/observability/distributed-tracing/configurability/#using-proxy-istio-io-config-annotation-for-trace-settings section.. :(

Ok - I see at https://istio.io/latest/docs/tasks/observability/distributed-tracing/configurability/#available-tracing-configurations this quote:

This probably needs to be called out more loudly - its very easy to gloss over that section and skip right to the https://istio.io/latest/docs/tasks/observability/distributed-tracing/configurability/#using-proxy-istio-io-config-annotation-for-trace-settings section.. :(

Thank you very much @diranged for clarifying the point. But there seems to be a risk to transfer all global mesh configs to pod level in order to change a specific configuration. It will be more useful and less error-prone when pod annotations just override "related" meshconfigs. And in this case, unrelated configurations that pods don't aware of would apply at all times.

Thank you very much @diranged for clarifying the point. But there seems to be a risk to transfer all global mesh configs to pod level in order to change a specific configuration. It will be more useful and less error-prone when pod annotations just override "related" meshconfigs. And in this case, unrelated configurations that pods don't aware of would apply at all times.

@mkaman Hello! Did you use VirtaulService or Ingress for testing?

Thanks for reporting! Looks like this is a doc issue. https://github.com/istio/istio.io/pull/8967 should make the warning more visible.


Framework Selection

Choose a programming language and framework for building the application.
Consider factors like platform compatibility, performance, and developer familiarity.

I have decided to go with C#, WPF application that will run on .net8
I have gone with this route as WPF can be integrated with other platforms more freely.


[WIP] OAP Core polish, especially storage level

There are a lot of if/else codes due to the differences of the storages, but I plan to merge them in a more elegance and consistent way.

Add length definition with reasonable default value.
content of @Column has been renamed to storageOnly . I add this to many fields as they are not being query in any case.
Merge H2 and MySQL columntype mapping back to consistent.
Remove @IDColumn.
Support @QueryUnifiedIndex.
Refactor the MySQL and H2 installers to use @Column and @QueryUnifiedIndex definitions to create indices automatically. But the index naming rule has been changed to entityseqIDX. seq is the Increment Interger for every entity.
Support @MetricsExtension and insertOnly in the MetricsPersistentWorker worker.
Optimize MetricsStreamProcessor

Codecov Report

Merging #4587 into master will increase coverage by 0.03%.
The diff coverage is 34.04%.

@@            Coverage Diff             @@
##           master    #4587      +/-   ##
==========================================
+ Coverage   26.43%   26.46%   +0.03%
==========================================
  Files        1253     1254       +1
  Lines       28989    28992       +3
  Branches     3952     3947       -5
==========================================
+ Hits         7663     7673      +10
+ Misses      20623    20614       -9
- Partials      703      705       +2

Impacted Files
Coverage Δ

.../java/org/apache/skywalking/oal/rt/OALRuntime.java
0.00% <0.00%> (ø)

...intrelation/EndpointRelationServerSideMetrics.java
0.00% <ø> (ø)

...ance/ServiceInstanceRelationClientSideMetrics.java
0.00% <ø> (ø)

...ance/ServiceInstanceRelationServerSideMetrics.java
0.00% <ø> (ø)

...tion/service/ServiceRelationClientSideMetrics.java
0.00% <ø> (ø)

...tion/service/ServiceRelationServerSideMetrics.java
0.00% <ø> (ø)

...er/core/analysis/manual/segment/SegmentRecord.java
0.00% <ø> (ø)

...oap/server/core/analysis/metrics/ApdexMetrics.java
100.00% <ø> (ø)

...g/oap/server/core/analysis/metrics/CPMMetrics.java
0.00% <ø> (ø)

...server/core/analysis/metrics/DoubleAvgMetrics.java
0.00% <ø> (ø)

... and 16 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 4474907...8d7a944. Read the comment docs.

@hanahmily @dmsolr @mrproliu @JaredTan95 @kezhenxu94 This PR is ready to review. Please feedback.
If you have more optimization idea, I am happy to know.
FYI @apache/skywalking-committers , this PR provides more elegance way for SQL storage and ES storage. But for InfluxDB, I have nothing to do. According to @dmsolr, it seems having different logic. Also, I have asked him to summarize those and we could discuss in another thread. InfluxDB is not a very production ready implementation today. I am still expecting the performance test.

Another update, if you has read my previous #4570, you may have noticed there is duplicated record in the endpoint_traffic index. In this PR, I also update the id()/hashcode()/equal() logic for it, therefore, every endpoint has an unique record, once it was deleted by TTL, it will regenerate when new request of this endpoint comes.
Notice the _id, no time bucket included anymore. Time bucket is only for time-related insert and TTL mechanism.

@hanahmily Recheck please.


Force React-table to reload

What version of React-Table are you using?
6.8.0
What bug are you experiencing, or what feature are you proposing?
I'd like to be able to force the Component to reload so the 'onFetchData' handler would trigger again, or be able to reuse the function implemented inside the 'onFetchData'.
The context is that I have a function that add a new object in my data base, which should appear in the table, but it needs to update to do so. I can't just insert it my state.data since my backend alter the object.
It's my first project with React, maybe I'm missing a simple concept.
Use https://codesandbox.io/s/X6npLXPRW (by clicking the "Fork" button) to reproduce the issue.
https://codesandbox.io/s/olo47vwo89
Thank you for your time

React refreshes based on properties on the component changing.
If you are using onFetchData you have to use this.setState to set a state variable with the data and then use that as the data prop for ReactTable.  This is how 99% of React components work.

@gary-menzel Thanks for your answer, but it's not solving the problem.
Maybe I didn't explain the problem the correctly.
I have a custom component which wrappe a ReactTable component. React-Table is to retrieve my data on database in the backend.
My custom component also has a handler to add an object in my database and upon success, I notify my user by altering the state of the custom component.
The problem is, upon successful add of an object, the component ReactTable becomes outdated and does not refresh, even though I change the state of my custom component.
My apologies for not being clear enough on the first post and thank you for your time. :)

If you search these github issues you will see that many people have asked for a "refresh" function - and there is not going to be one added because it just isn't the way React works.
It's not the state of your custom component that needs to change - it is the properties that are being used by ReactTable.  So, to get the data to update, you have to use this.setState to change the data prop in your wrapping components state.  That is how "React" does updates - that is the simple concept that you have to wrap your head around.
Even more so, ReactTable stretches those concepts even further (so if it is your first project, trying to get ReactTable to work like other JS packages you may have used with something like jQuery will be a challenge and you'll just have to work through it until you "get it" - no shortcuts).
Finally, everyone coming from that "call a function to do something" approach wants to use onFetchData - I think it is unnecessary 99% of the time (and usually only needed when you have hundreds of thousands of records).
The codesandbox you supplied doesn't actually work (it gets compilation errors) so I was unable to see what your component architecture looks like.  Feel free to post a "working" (aside from the problem you described) replacement.

Thank you, I was missing one point in React, the re render does not take effect on child components unless state changing.
Thank you for explaining this to me, now it works, following your instructions: when the creation succeed, I call my database to read the new object and manually add it to the data.
I was talking about the onFetchData because it's the one used in the example.
Thank you again for the great support.

Correct me if I am wrong. I think this only works when the length of data array has changed. If you just change one element in the array, for example, data[0].age = 3; then setState({data}), it will not update.

react-virtualized does provide a forceUpdate function to force the grid to update. It's useful because when the underlying data is changed frequently, we want to forceUpdate periodically (e.g. every second) instead of asynchronously (e.g. onUpdate).

@gary-menzel, earlier in this thread you responded with this:

"React refreshes based on properties on the component changing.
If you are using onFetchData you have to use this.setState to set a state variable with the data and then use that as the data prop for ReactTable. This is how 99% of React components work."

In my case I'm using redux for my data so I'm using this.props. vs this.state. In my testing it seems to make no difference which I use, but I'm having an issue where the state in ReactTable component is not updated...
I'm using redux to store multiple "views" of logging data, each view also stores the filtered object from table state based on what filters, if any are selected when that view is selected. If there are no filters set, filtered = [].  When I render ReactTable, I pass this.props.filtered (from redux mapStatetoProps) in via filtered and defaultFiltered props so the table renders with the filters for that view.
The problem I'm having is that if I have a view that DOES have filters (table state.filtered NOT empty), then I create a new view that has filtered = [], the next render still shows the filters of the last view, which I consider "stale". The new data is displayed as expected, it's just the filters from the last view displayed.
Any thoughts on why that is, and how I can assure the new view/filtered object are reflected in the next render?
Thanks in advance,
Paul

This answer is only satisfactory if you happen to have the data entity that was saved to your data store. If you made a POST call to a server, and it saves data, and that data is manipulated on the back end, you need to be able to update the table with the new field from the store. If you are using the onFetchData functionality, you have no way of forcing the table to call that function without artificially setting some state data to manipulate the react elements. You can't separate the data call function from the table, because then you will not have the tables state and instance data that it passes to onFetchData. The concept that this control does not need a refresh because "that's not how React works" is just false.

@cfalone, you are correct in your use case which is the very use case that is being taken into heavy consideration for v7.
@lloydw Yes.

What is a decent workaround for this, I need to get some refreshes to work yesterday. :)

OK, here it is for V6:

add a ref to react table

  constructor(props) {
    super(props);
    this.table = React.createRef();
    this.fetch = this.fetch.bind(this);
  }
  render() {
    return <ReactTable
       ref={this.table}
       onFetchData={this.fetch}
       ...
    />;
  }
  fetch(state){
    // make call -> then update state
  }
  onFinishedEditOrDelete(){
     this.fetch(this.table.current.state);
  }
}```

@cfalone Thank you so much for this.
A complementary piece to this that was helpful for me was that setState has a 2nd argument for a callback function to ensure that the fetch() call happens after the state change (if there are elements to your state that affect your fetch query).
So you can do:
this.setState({whatever state change}, this.fetch(this.table.current.state));

OK, here it is for V6:

add a ref to react table
create a function for onFetchData that receives table 'state' which will call your data and set data and paging, etc
get state from ref.current.state after your edit and call your fetch function with it, the state updates in your fetch calls promise return will update the table just like when it calls onFetchData itself.

  constructor(props) {
    super(props);
    this.table = React.createRef();
    this.fetch = this.fetch.bind(this);
  }
  render() {
    return <ReactTable
       ref={this.table}
       onFetchData={this.fetch}
       ...
    />;
  }
  fetch(state){
    // make call -> then update state
  }
  onFinishedEditOrDelete(){
     this.fetch(this.table.current.state);
  }
}

Legend! Wish I found this post about 7 hours ago!!

OK, here it is for V6:

add a ref to react table
create a function for onFetchData that receives table 'state' which will call your data and set data and paging, etc
get state from ref.current.state after your edit and call your fetch function with it, the state updates in your fetch calls promise return will update the table just like when it calls onFetchData itself.

  constructor(props) {
    super(props);
    this.table = React.createRef();
    this.fetch = this.fetch.bind(this);
  }
  render() {
    return <ReactTable
       ref={this.table}
       onFetchData={this.fetch}
       ...
    />;
  }
  fetch(state){
    // make call -> then update state
  }
  onFinishedEditOrDelete(){
     this.fetch(this.table.current.state);
  }
}

Man, you are a hero :D

Been using redux and had the same issue, to force update of the component and to trick it that new set of data is being retrieved (get around the referential checks)  I have resorted to recreating the data array by simply using JSON.parse() and JSON.stringify() before passing it to the action.
handleRemoveFile = id => {
    var files = this.props.download.files;
    _.remove(files, file => file.id === id);
    var newfiles = JSON.parse(JSON.stringify(files));
    this.props.setDownloadFiles(newfiles);
};

For now it works, really wishing to have a more decent way to force the reload/refresh.

@tannerlinsley , could you please refer to the change the was made in v7?  I'm having this issue in today (Nov 2021) and would love to update my pattern to the legit way :)

please reopen this issue


Add missing global id field on Type template

Fixes #25.

Current coverage is 82.67% (diff: 100%)

Merging #41 into master will not change coverage

@@             master        #41   diff @@
==========================================
  Files            13         13
  Lines           202        202
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            167        167
  Misses           35         35
  Partials          0          0

Powered by Codecov. Last update ca5e086...5a631fd

missing interfaces: () => [NodeInterface],


But without resolution option...

Solid, works flawlessly. But without option for choosing to record at less than full resolution, files are unacceptably large.

@Mahuco The file size of the recording can be reduced by lowering the video or audio bitrate (find it in settings) which is a better solution than lowering video resolution. You can't set it to specific bitrate for example 0.5 mbps but you can pick one of the preset available


chore(repo): upgraded storybook and cleaned up the css type

📝 Description
The current storybook version 6.5.3 has an emotion :first-child error and emotion 11 has been supported since storybook 6.5, which avoids the incompatibility of the css types defined globally by emotion with the css type of stitches.
⛳ Current behavior (updates)

Upgraded storybook to version 6.5.12.
Cleaned up the css prop of any type.
Fixed emotion :first-child warning by upgrading storybook.
Fixed Card shadow in stories.

💣 Is this a breaking change (Yes/No):
No

Hey @tianenpang, could you please fix the conflicts?

Hi @jrgarciadev fixed and upgraded storybook to the latest version.


unfreeze execution flow

Now when I apply redux-thunk and my custom middleware as a chain:
const createStoreWithMiddleware = applyMiddleware(thunk, catchPromise)(createStore);

And then dispatch promise:
export function fetchItems(folder) {
  return (dispatch, getState) => {
    return Promise((resolve, reject) => {
    // ...
    }
  };
};

I could not get control because redux-thunk doesn't continue execution flow for functions through next() callback:
export default function thunkMiddleware({ dispatch, getState }) {
  return next => action =>
    typeof action === 'function' ?
      action(dispatch, getState) :
      next(action);
}

This PR should resolve it and we can make middleware chains in right way.

Up!

I'm a bit confused. If you use redux-thunk, this:
export function fetchItems(folder) {
  return (dispatch, getState) => {
    return Promise((resolve, reject) => {
    // ...
    }
  };
};

is not how you dispatch.
This:
export function fetchItems(folder) {
  return (dispatch, getState) => {
    dispatch(Promise((resolve, reject) => {
      // ...
    })
  };
};

is how you do it.
But I don't see you using any features provided by redux-thunk itself, so maybe you don't need redux-thunk at all:
export function fetchItems(folder) {
  return Promise((resolve, reject) => {
    // ...
  });
};

If this doesn't make sense, let's discuss a more complete example.

To clarify: there is no meaning assigned to thunk's return result. This is by design. Return value is not meant to be interpreted by another middleware. It's just a convenience.
If we dispatched return value, we'd have to place restrictions on it, but we don't want to.

The real example is about dispatching async functions which I purposed in redux-catch-promise middlware. When I released it as a single middleware you said it would be better to use both middleware together.
Original example is:
export function fetchItems(folder) {
  return async function (dispatch, getState) => {
    await fetch(...);
  };
}

I'm closing for the same reason as https://github.com/gaearon/redux-thunk/pull/23#issuecomment-145363994. It's a breaking change for too many projects, and it's fundamentally different from how this current middleware works. I was wrong when I said it's better to use thunk in this case—this is a totally different behavior. Sorry I mislead you!


adding Setup member function in PollingPolicy

This fixes #1431.
implemented the PollingPolicy::Setup method and it can be used to setup deadlines in the context. it is cleaner version of #1878.

This change is

Crap, sorry, I missed it. No, I think it's fine.


ReverseDiff generality and avoid cross-fallbacks

Core

Gradient for 1d input and derivative for 1d output used to cross-call each other when the backend was in the wrong mode. Now it's all pushforwards and pullbacks

Extensions

ReverseDiff supports number input
Taped is fixed

Tests

Separate imports so that each test file is autonomous

Codecov Report
Attention: Patch coverage is 96.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 93.77%. Comparing base (efef587) to head (976df31).

Files
Patch %
Lines

...erfaceTapedExt/DifferentiationInterfaceTapedExt.jl
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
+ Coverage   93.69%   93.77%   +0.07%
==========================================
  Files          56       56
  Lines        1364     1381      +17
==========================================
+ Hits         1278     1295      +17
  Misses         86       86

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Pre select hook

Hey,
I was wondering whether it is possible to hook into getState before the @select decorator accesses the storage. I am using ImmutableJS but also another package that requires me to call an ensuring function (ensureState) before accessing the store. This of course makes it impossible for me to use the syntactic sugar in combination with ImmutableJS.
Example:
@select(s => ensureState(s).getIn(['counts', 'firstCount'])) firstCount$: Observable<number>;

Can I somehow hook into the state getter before the decorator fetches the store so I can by default have the state wrapped by the ensureState method (coming from https://github.com/mattkrick/redux-optimistic-ui).
Any help would be appreciated.
EDIT: ensureState is needed everywhere I access the store.
Cheers

Is this currently throwing an error? taking a quick look at the redux-optimisitc-ui, and the example snippet that you have, I don't see why this wouldn't work, as s is basically the value of getState().

There is no error in the upper construct. The idea was to make use of the syntactic sugar explained in https://github.com/angular-redux/ng2-redux/blob/master/docs/immutable-js.md. So basically transforming this:
@select(s => ensureState(s).getIn(['counts', 'firstCount'])) firstCount$: Observable<number>;

into this:
@select(['counts', 'firstCount']) firstCount$: Observable<number>;

Which currently is not possible because I have to call ensureState on my state in order for redux-optimistic-ui to return the proper state. Therefore I always have to use the longer syntax. My question was whether there is a possibility to have a general mechanism doing s => ensureState(s) so I can use the nice and clean syntax for the @select decorator.

@TobiasKrogh Thanks for clarifying - been thinking about this for a day or two, but haven't been able to come up with clean way of handling this, at least at a library level.
If I get a chance, I'll see if I can play around with an example decorator that hooks calls select after doing an ensureState.
One thing that I do suggest though, is placing your selectors along with your reducers, ie.
// some-feature.reducer.ts
export counts(state,action) {
    return state;
}
export firstCount = (state) => ensureState(s).getIn(['counts', 'firstCount'])

Then in your components that need to make use of it,
import { firstCount } from './your/reducers';

@Component({})
export class MyComponent {
    @select(firstCount) firstCount$:Observable<number>
}

This helps make it so your components need to know less about the structure of your state, allows your selectors to be reusable, and if you need to refactor your state/reducers - it limits the number of areas you need to refactor to address the change.

@e-schultz Thanks for your feedback. It would be great if we find a solution.
I did not yet thought about putting the selectors alongside the reducers, nice idea. Thanks. Seems definitely worth it.

@e-schultz Sorry for not responding for such a long time. I was not able to do the suggested optimization but I definitely will. For me this issue can be closed... still a general way to hook into the store somehow would be great

I gave this a thought too and agreeing with @e-schultz it is hard to think about something clean.
Having said that, @TobiasKrogh if what you want is that all @select calls first call ensureState sending down the state itself. You could decorate the decorator :P
export function selectEnsureState<T>(
  selector?: PropertySelector | PathSelector | FunctionSelector<any, T>,
  comparator?: Comparator): PropertyDecorator {
  return select(s => selector(ensureState(s)), comparator);
}

Basically you would instead use your own decorator that wraps ng2-redux's select decorator
I haven't tested this code, but it looks reasonable to me. Finally you could do:
class MyContainer {
  @selectEnsureState(s => s.getIn(['counts', 'firstCount'])) firstCount;
}

Actually I just realized that this is not what you want, since it is not going to be "before the @select decorator accesses the storage"

@e-schultz Hi, sorry (once again) for not responding for such a long time... been very busy lately. I took your advice and placed selectors along my reducers respectively migrated them stepwise. This is really clean and I feel it is fine to do the ensureState call there. Thanks for your time! Will close


DSP-9944: Add SBT Integration Tests using Spark Embedded Cassandra

Adds test Resources directory matching the 1.6 version of the Spark
Cassandra Connector and compatiblet template files for C* 2.1,2.2, and
3
Dse and OSS build files modified so these tests can be run and can be
run from within an IDE.

+1
@RussellSpitzer do we want to have those ported to Java and Maven/Gradle as well?

retest this please

test this please


New version: Splashtop.SplashtopBusiness version <IP_ADDRESS>

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

The version number in the duplicate ticket https://github.com/microsoft/winget-pkgs/pull/190727 is incorrect. It should be corrected from <IP_ADDRESS> to 3.7.203.