Package path not exported error - error when running react-native rnx-start

What happened?
Trying to set up an existing project to work with rnx-kit. I am getting errors from the metro server when I run yarn react-native rnx-start --reset-cache. I have no problem whatsoever when I run yarn react-native start --reset-cache.
The errors look like this:
error: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './package.json' is not defined by "exports" in /REPO//node_modules/node-html-parser/package.json
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:729:3)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at /REPO/node_modules/@rnx-kit/tools-react-native/lib/platform.js:77:46
    at Array.forEach (<anonymous>)
    at getAvailablePlatformsUncached (/repo/node_modules/@rnx-kit/tools-react-native/lib/platform.js:76:7)

I'm currently getting it for 'node-html-parser'. I was also getting the same error for a local package devDependency before, which is only configured to compile an ESM module. I removed it temporarily but immediately ran into the same error in node-html-parser.
I'm assuming it's an esm vs. Common module thing? Which would make sense, except that the normal 'react-native start' command is working fine.
I'm also getting this warning about the blocklist, but I'm unsure if it is related.
● Deprecation Warning:

Warning: Metro config option `blacklistRE` is deprecated.
         Please use `blockList` instead.

● Validation Warning:

  Unknown option "blockList" with value

I'd like some help getting it working for rnx-start if possible.  I'm not sure if I missed a config option somewhere, but I've tried various minor permutations of configs to no avail.
After looking around existing issues, I think this may be related to #805 or #1046.
Affected Package
@rnx-kit/metro-config
Version
1.2.29
Which platforms are you seeing this issue on?

[X] Android
[X] iOS
[ ] macOS
[ ] Windows

System Information
info Fetching system and libraries information...
System:
    OS: macOS 12.2.1
    CPU: (8) arm64 Apple M1
    Memory: 77.95 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 1.22.17 - ~/.yarn/bin/yarn
    npm: 6.14.15 - ~/_/REPO/node_modules/.bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.11.2 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
    Android SDK:
      API Levels: 23, 27, 28, 29, 30
      Build Tools: 29.0.2, 29.0.3, 30.0.2, 31.0.0
      System Images: android-30 | Google APIs ARM 64 v8a, android-31 | Google APIs ARM 64 v8a
      Android NDK: 22.1.7171670
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7784292
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.14 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.65.1 => 0.65.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to Reproduce
Unfortunately this is in a very large work repo. I can paste relevant snippets? I cobbled together the config files from what I had before in the repository with what was in the /test-app package.json in the rnx-kit repo.
I left the rn-cli.config.js file pretty empty except one line I copied over from the old version I had, because I couldn't find documentation on it and the order of precedence between the rn-cli and metro config files. Adding the command line flags for rnx-kit and the rnx-kit fields in pacakge.json, I had no idea what would be applied first so I just tried to keep everything in metro.config.
relevant package.json bits
{
  "dependencies": {
    "react": "17.0.2",
    "react-dom": "^17.0.2",
    "react-native": "0.65.1"
},
 {
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/eslint-parser": "^7.17.0",
    "@babel/runtime": "^7.12.5",
    "@rnx-kit/cli": "^0.11.1",
    "@rnx-kit/metro-config": "^1.2.29",
    "@rnx-kit/metro-plugin-cyclic-dependencies-detector": "^1.0.21",
    "@rnx-kit/metro-plugin-duplicates-checker": "^1.2.15",
    "@rnx-kit/metro-resolver-symlinks": "^0.1.16"
},
 "rnx-kit": {
    "reactNativeVersion": "^0.65",
    "kitType": "app",
    "capabilities": [
      "animation",
      "babel-preset-react-native",
      "core",
      "core-android",
      "core-ios",
      "datetime-picker",
      "filesystem",
      "gestures",
      "hermes",
      "jest",
      "modal",
      "navigation/native",
      "netinfo",
      "react",
      "react-dom",
      "react-test-renderer",
      "screens",
      "svg",
      "webview"
    ]
  }
}

metro.config.js
const defaultSourceExts = require("metro-config/src/defaults/defaults").sourceExts;
const { exclusionList, makeMetroConfig } = require("@rnx-kit/metro-config");
const MetroSymlinksResolver = require("@rnx-kit/metro-resolver-symlinks");

const blockList = exclusionList([
  /node_modules\/node-html-parser\/package\.json/, // this didn't seem to make a difference
  /react-native\/local-cli\/core\/__fixtures__.*/,
  /node_modules\/.*\/node_modules\/react-native\/.*/,
  /.yalc\/.*\/package\.json/,
]);

module.exports = makeMetroConfig({
  projectRoot: __dirname,
  resolver: {
    sourceExts: process.env.RN_SRC_EXT
      ? process.env.RN_SRC_EXT.split(",").concat(defaultSourceExts)
      : defaultSourceExts,
  },
  blacklistRE: blockList,
  blockList,
});

rn-cli.config.js
module.exports = {
  getAssetExts() {
    return ["jsx"];
  }

babel.config.js
module.exports = {
  presets: ["module:metro-react-native-babel-preset"],
};

Will try to make a minimal repro project later if necessary.
Code of Conduct

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

Thanks for the super detailed issue description! I found the bug, and have a fix ready (I just need to add some more tests).


Use zlib instead of iltorb

Fixes #3.
Note that this requires a major version bump because the options that could be passed are completely different. Here are the new ones.
P.S. cc @unrelentingtech

Thanks! Released 2.0.0.


Connection management issues with Java SDK

Expected Behavior
When I re-deploy my Temporal cluster, I expect workers and workflow run initiators to not even notice that the topology of the cluster has changed, or that some hosts have gone away and others have reappeared.  Any connection failures due to these changes should be transparently "fixed up" by the SDK.
Actual Behavior
During cluster deployments I see timeouts and periods of unavailability (with many log error messages with the GRPC UNAVAILABLE error in the activity poller).  Sometimes workflow run invocations fail as well with timeout errors.
Steps to Reproduce the Problem

Build a temporal cluster with, say, 6 nodes.
Add some worker nodes implementing a simple workflow, set up to invoke the workflow fairly often, like once every 5 seconds.
Redeploy the entire Temporal cluster.  (In our case, we do a rolling deploy, where we put a new node in, wait for it to join the cluster [checking by polling the cluster metadata endpoint], wait an additional 2 minutes to allow things to settle, and then take the old node out.)
Watch metrics/logs on the worker nodes, and notice errors in the worker/activity pollers, as well as some failures to start workflows.

Specifications

Version: 1.0.5
Platform: Linux x86_64

More Information
Our network topology uses a service mesh sidecar to communicate between hosts.  A Temporal worker (or workflow-run-invoker) is instructed to talk to Temporal by connecting to a port on localhost that is backed by Envoy running in HTTP2 mode.  Envoy will then (over HTTP2+TLS) connect to Envoy running on the Temporal server, which will then connect to the Temporal server itself (again using HTTP2).
In order to accommodate low-traffic workers, initially server-to-server and client-to-Envoy timeouts were set very long, on the order of 10 minutes.  However, that caused up to 10 minute periods of unavailability during deployments.  More recently I have dropped the timeouts down to 65 seconds, and have instructed Envoy to retry transparently on GRPC UNAVAILABLE and DEADLINE-EXCEEDED errors.  However, we still see intermittent failures during Temporal cluster deployments.
On the workers, we have left all the default timeouts alone in the Temporal client (as they seem fairly sane and short).

Some logs with stack traces:
io.grpc.StatusRuntimeException: UNAVAILABLE: transport is closing
	at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:262)
	at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:243)
	at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:156)
	at io.temporal.api.workflowservice.v1.WorkflowServiceGrpc.pollWorkflowTaskQueue(WorkflowServiceGrpc.java:2658)
	at io.temporal.internal.worker.WorkflowPollTask.poll(WorkflowPollTask.java:77)
	at io.temporal.internal.worker.WorkflowPollTask.poll(WorkflowPollTask.java:37)
	at io.temporal.internal.worker.Poller.run(Poller.java:273)
	at io.temporal.internal.worker.Poller.run(Poller.java:242)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

and
io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason
	at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:262)
	at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:243)
	at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:156)
	at io.temporal.api.workflowservice.v1.WorkflowServiceGrpc.pollWorkflowTaskQueue(WorkflowServiceGrpc.java:2658)
	at io.temporal.internal.worker.WorkflowPollTask.poll(WorkflowPollTask.java:77)
	at io.temporal.internal.worker.WorkflowPollTask.poll(WorkflowPollTask.java:37)
	at io.temporal.internal.worker.Poller.run(Poller.java:273)
	at io.temporal.internal.worker.Poller.run(Poller.java:242)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

There are two potential issues that can cause this:

gRPC backoff keeps increasing if the underlying backend is unavailable and can go up to 2 minutes per retry. We've addressed this by periodically resetting gRPC backoff every 10 seconds.
Connections are abruptly closed on the server side and client things that they are still active until TCP timeout occurs. For this issue, in the latest release (1.0.6), we've added simple connection management improvement in #351 which would re-establish connections to the server periodically. Also we've added a keep-alive checking on the client side, but it is currently disabled by default as server doesn't have keep-alive friendly configuration yet. Feel free to experiment with the configuration though (see #367 for the list of config parameters).

Great, thank you @vitarb!  We'll be upgrading and doing some experiments over the next couple days.

Ok, we've tried 1.0.6 and enabled the keepalive (with a 30 second interval), and things do definitely seem to be better.  We've been unable to repro the issue (so far) with new workflow run invocations failing, though we still do see a bit of log noise from the activity poller threads.  It does appear that all workflows and activities do end up getting run, though I don't have numbers yet on if there's any increase in latency.

Things have been a lot better over the past few weeks, and we've gone through several Temporal cluster deployments without incident.  We've been using the keepalive mechanism with a 30-second ping.
One thing that has been a bit frustrating is that the logging in Poller.java is causing our pagers to go off, even though the poller reestablishes its connection and recovers on its own.  We end up with 15-20 instances of this error message[0] logged per worker host during the cluster deployment (some coming from WorkflowPollTask and some coming from ActivityPollTask).
I've considered adding custom rules to avoid paging in this case, but anything I can come up with feels brittle (and also possibly not safe, and could mask real issues), and these custom rules would have to be manually applied to every new service that starts using Temporal.
I think what would help us most is if the logging logic could log at WARN for an issue that could be transient, and then only escalate to ERROR if it's unable to re-establish a connection within a reasonable amount of time.  (In general we only page for some smallish number of occurrences of ERROR logs; some teams do page for WARNs but only in cases where there are a significantly large number of them.)
[0] We see several different exception messages on this:

UNAVAILABLE: upstream connect error or disconnect/reset before headers. reset reason: connection termination
UNAVAILABLE: transport is closing
DEADLINE_EXCEEDED: deadline exceeded after 69.999973290s. [remote_addr=<IP_ADDRESS>/<IP_ADDRESS>:17233]
UNAVAILABLE: Network closed for unknown reason
UNAVAILABLE: Subchannel shutdown invoked


Replace JamesIves/github-pages-deploy-action by actions/deploy-pages

Probably better to use the official Github actions, which does not involve the use of another branch anymore.

[ ] In .github/workflows/on-merge-to-develop.yml
[ ] In our README.md example if it works correctly

Perhaps this solution will help you figure out the problem click

I'd be interested in contributing here.
Using the deploy-pages action might need some configuration in the pages-settings of the repository which I'd not be able to do myself though (I think the steps needed are configuring "GitHub Actions" as build & deployment source for pages and I'm not sure whether this happens automatically after configuring that or if it has to be done manually, but one might need to create an environment named "github-pages".

Cool!
Yes you can submit a PR and then I'll update these settings:

I'll switch to "Use GitHub Actions"
Thank you for your help


When generated the parameter of type "object" turns into type "unknown". Type "any" would be preferred.

it would be great if the type object would translate to type any instead of unknown. I cant use the type object right now, because when it transforms to unknown it gives me a ton of ts errors, wich would be solved if the type any would be used. Or maybe a way yo configure it would be nice.

@hugokemme7
This library uses @hey-api/openapi-ts for type generation from the OpenAPI spec, so I recommend creating an issue there.


WIP(iox-10891): patched df upgrade 202-05-24

⚠ This will not be merged. ⚠

Bringing us up to datafusion to 2024-05-24

This PR is based on May 20, 2024 https://github.com/apache/datafusion/commit/3ebc31d2c26e6ff02d3cc79e5e4786d4ed029710

git co -b chunchun/update-df-may-week-4 3ebc31d2c26e6ff02d3cc79e5e4786d4ed029710

Applied the following patch(es):

cherry picked https://github.com/apache/datafusion/pull/10655 / https://github.com/apache/datafusion/commit/0f994afff27a6240c7ad0831eda4e957bc55e7c4
commit 0f994afff27a6240c7ad0831eda4e957bc55e7c4
Author: Andrew Lamb<EMAIL_ADDRESS>Date:   Sat May 25 06:13:41 2024 -0400

    Support field access for literal Null (#10655)

Closing since the update is done


_phase2gray

Hello,
I have a question for the _phase2gray() method in the slm.py file. There, we pass self.display as the out variable, and self.display has (depending on the SLM bit-resolution) a data-type np.unint8 or np.uint16.
Later, the float -> int conversion gets enforced with np.copyto(*args, casting="unsafe").
Two questions:

When out in np.copyto has 8-bit unsigned integer types, I think the subsequent call of np.bitwise_and() becomes irrelevant.
np.copyto casts e.g. 1.9 -> 1. Shouldn't 2 be desired?
Also, casting negative integers to unsigned types can lead to unexpected behavior, e.g. -162 -> 256 - 162 = 94

I hope I got this right. Is the reason for using np.copyto speed because it's in-place? Otherwise, it seems a bit unsafe to do.

Hi @LeoKonzett , thanks for this great question.

The np.bitwise_and() performs the action of np.mod() in the case when self.phase_scaling == 1. This is super fast compared with np.mod(). However, you're completely right that this call is unnecessary in the case where you have an 8-bit or 16-bit SLM, as the type casting already performs the and. I have added a check to not do this in those cases (6ece4bb297ea63ed0664cf1d2f03470002586bd8).
The intent was to avoid np.around overhead. We could accomplish the same thing by adding .5 before type-casting, but I'm uncertain whether it's worth the overhead for this fractional change. I have added documentation (6ece4bb297ea63ed0664cf1d2f03470002586bd8) specifying the floor()ed behavior.
In testing, I wasn't able to find a case where unsafe casting didn't behave like floor(), but if you can find one then I agree that a better solution is needed. I agree that the ironic "unsafe" flag correctly implies lack of safety, but I think it's deterministic in our case. Note that this line makes sure that all numbers are negative. The example that you gave is desired behavior, because this is the effect of mod by 256.

To answer your last question, yes the reasoning is speed. While something similar to this could be faster (like the ultimate solution for speed: going full-C and writing directly to some integer buffer and never touching floats), this solution was able to maintain both the 60 Hz operation in testing and the user-friendly 2pi float submission that we wanted to have. np.mod() was a main limitation for other implementations. Of course, we welcome any contributions to make the package better. If you have any ideas for how to improve this while still maintaining speed, feel free to discuss or add something! Let me know if you have any comments on the mentioned changes (6ece4bb297ea63ed0664cf1d2f03470002586bd8), we'll probably pull request this within a week.

I'm closing this issue as these changes were pulled under request #24.
Please feel free, @LeoKonzett, to reopen it or to contact us about anything else! Looking forward to see what you do with the package.


[wip] V2 Webpack

[ ] test it

Closing for now. It's not easy to force typescript to compile when interfaces changes.


Refactor [Navigator] Logger

Perfect Structured logging
$ go run debug.go
2023-12-24T01:02:58.903+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 1"}
2023-12-24T01:02:58.903+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 1"}
2023-12-24T01:02:58.904+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 1/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 1, "max_retries": 3, "task_name": "c check pods running 1"}
2023-12-24T01:02:58.904+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 1/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 1", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:00.905+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 1"}
2023-12-24T01:03:00.905+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 1"}
2023-12-24T01:03:00.905+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 2/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 2, "max_retries": 3, "task_name": "c check pods running 1"}
2023-12-24T01:03:00.905+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 2/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 1", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:02.915+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 1"}
2023-12-24T01:03:02.915+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 1"}
2023-12-24T01:03:02.915+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 3/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 3, "max_retries": 3, "task_name": "c check pods running 1"}
2023-12-24T01:03:02.915+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 3/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 1", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:04.917+0700    INFO    navigator/logger.go:38  ❌ Failed to complete task check pods running 1 after 3 attempts        {"ships_namespace": "default", "task_name": "check pods running 1", "error": "Failed to complete task check pods running 1 after 3 attempts"}
2023-12-24T01:03:04.917+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 2"}
2023-12-24T01:03:04.917+0700    INFO    K8sBlackPearl/debug.go:104      Received result: Failed to complete task check pods running 1 after 3 attempts
2023-12-24T01:03:04.917+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 2"}
2023-12-24T01:03:04.917+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 1/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 1, "max_retries": 3, "task_name": "c check pods running 2"}
2023-12-24T01:03:04.917+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 1/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 2", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:06.921+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 2"}
2023-12-24T01:03:06.921+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 2"}
2023-12-24T01:03:06.921+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 2/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 2, "max_retries": 3, "task_name": "c check pods running 2"}
2023-12-24T01:03:06.921+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 2/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 2", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:08.927+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 2"}
2023-12-24T01:03:08.927+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 2"}
2023-12-24T01:03:08.927+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 3/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 3, "max_retries": 3, "task_name": "c check pods running 2"}
2023-12-24T01:03:08.927+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 3/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 2", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:10.935+0700    INFO    navigator/logger.go:38  ❌ Failed to complete task check pods running 2 after 3 attempts        {"ships_namespace": "default", "task_name": "check pods running 2", "error": "Failed to complete task check pods running 2 after 3 attempts"}
2023-12-24T01:03:10.935+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 3"}
2023-12-24T01:03:10.936+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 3"}
2023-12-24T01:03:10.935+0700    INFO    K8sBlackPearl/debug.go:104      Received result: Failed to complete task check pods running 2 after 3 attempts
2023-12-24T01:03:10.936+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 1/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 1, "max_retries": 3, "task_name": "c check pods running 3"}
2023-12-24T01:03:10.936+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 1/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 3", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:12.941+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 3"}
2023-12-24T01:03:12.941+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 3"}
2023-12-24T01:03:12.941+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 2/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 2, "max_retries": 3, "task_name": "c check pods running 3"}
2023-12-24T01:03:12.941+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 2/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 3", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:14.945+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 3"}
2023-12-24T01:03:14.945+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 3"}
2023-12-24T01:03:14.945+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 3/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 3, "max_retries": 3, "task_name": "c check pods running 3"}
2023-12-24T01:03:14.945+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 3/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 3", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:16.949+0700    INFO    navigator/logger.go:38  ❌ Failed to complete task check pods running 3 after 3 attempts        {"ships_namespace": "default", "task_name": "check pods running 3", "error": "Failed to complete task check pods running 3 after 3 attempts"}
2023-12-24T01:03:16.949+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 4"}
2023-12-24T01:03:16.949+0700    INFO    K8sBlackPearl/debug.go:104      Received result: Failed to complete task check pods running 3 after 3 attempts
2023-12-24T01:03:16.949+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 4"}
2023-12-24T01:03:16.950+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 1/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 1, "max_retries": 3, "task_name": "c check pods running 4"}
2023-12-24T01:03:16.950+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 1/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 4", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:18.954+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 4"}
2023-12-24T01:03:18.954+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 4"}
2023-12-24T01:03:18.954+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 2/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 2, "max_retries": 3, "task_name": "c check pods running 4"}
2023-12-24T01:03:18.955+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 2/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 4", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:20.963+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 4"}
2023-12-24T01:03:20.963+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 4"}
2023-12-24T01:03:20.963+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 3/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 3, "max_retries": 3, "task_name": "c check pods running 4"}
2023-12-24T01:03:20.964+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 3/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 4", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:22.974+0700    INFO    navigator/logger.go:38  ❌ Failed to complete task check pods running 4 after 3 attempts        {"ships_namespace": "default", "task_name": "check pods running 4", "error": "Failed to complete task check pods running 4 after 3 attempts"}
2023-12-24T01:03:22.974+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 5"}
2023-12-24T01:03:22.974+0700    INFO    K8sBlackPearl/debug.go:104      Received result: Failed to complete task check pods running 4 after 3 attempts
2023-12-24T01:03:22.975+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 5"}
2023-12-24T01:03:22.975+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 1/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 1, "max_retries": 3, "task_name": "c check pods running 5"}
2023-12-24T01:03:24.983+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 5"}
2023-12-24T01:03:24.983+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 5"}
2023-12-24T01:03:24.983+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 2/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 2, "max_retries": 3, "task_name": "c check pods running 5"}
2023-12-24T01:03:24.984+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 2/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 5", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:26.997+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Fetching pods     {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 5"}
2023-12-24T01:03:26.997+0700    INFO    navigator/logger.go:38  🏴☠  invalid parameters       {"sailing": "FetchPods", "shipsnamespace": "default", "task_name": "check pods running 5"}
2023-12-24T01:03:26.997+0700    INFO    navigator/logger.go:38  🏴☠  Crew Worker 0: Retrying task 3/3 {"sailing": "FetchPods", "shipsnamespace": "default", "crew_worker": 0, "attempt": 3, "max_retries": 3, "task_name": "c check pods running 5"}
2023-12-24T01:03:26.997+0700    INFO    navigator/logger.go:38  ❌ Error during task, attempt 3/3: invalid parameters: labelSelector, fieldSelector, or limit   {"task_name": "check pods running 5", "error": "invalid parameters: labelSelector, fieldSelector, or limit"}
2023-12-24T01:03:29.008+0700    INFO    navigator/logger.go:38  ❌ Failed to complete task check pods running 5 after 3 attempts        {"ships_namespace": "default", "task_name": "check pods running 5", "error": "Failed to complete task check pods running 5 after 3 attempts"}
2023-12-24T01:03:29.009+0700    INFO    K8sBlackPearl/debug.go:104      Received result: Failed to complete task check pods running 5 after 3 attempts


Feature: Show current position

Implement a routine to display the current cursor position, i.e. line number and column number.

Implemented and working


Could we make retry options configurable?

I'm using Bypass in my test suite to intercept AWS calls:
# config/test.exs

use Mix.Config

config :ex_aws, sqs: %{
  scheme: "http://",
  host: "<IP_ADDRESS>",
  region: "us-east-1",
  port: 1234
}

# a test might look like

defmodule Test do
  use ExUnit.Case, async: true

  setup do
    port = Application.fetch_env!(:ex_aws, :sqs).port
    bypass = Bypass.open(port: port)
    {:ok, bypass: bypass}
  end

  test "when AWS is down", %{bypass: bypass} do
    Bypass.expect bypass, fn conn -> Plug.Conn.resp(conn, 500, "down") end

    assert_raise ExAws.Error, fn ->
      ExAws.SQS.list_queues |> ExAws.request!
    end
  end
end

But this test takes a long time to run due to all the retries with exponential backoff, which are hard-coded into ExAws: https://github.com/CargoSense/ex_aws/blob/11dcf1d45abd99c53e7665c67b4c7dcaae0392d8/lib/ex_aws/request.ex#L3-L5
If only for speeding up test suites, could we make the retry options configurable? It might also be useful for people who want to tweak the defaults.

Sounds good, any chance you're interested in making a PR to that effect?

Sure, doesn't seem like too much work. Lemme see what I can do!


Update version to 1.1.14-5 on staging

Update version to 1.1.14-5

🚀 Deployed to staging by @OSBotify in version: 1.1.14-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @AndrewGable in version: 1.1.15-15 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Error with folder with spaces

When trying create any project it will not succeed if the there is a space in it.

It should add spaced names in quotes.

Hi @sarsey-walker Thanks for reporting this issue.
It was fixed in the latest version of the extension, v2.0.0. The way I opt to fix was, if you type your project name with spaces it will concatenate the name to create the project, for example:
Command: Add Project (From context menu) or Create Project (from Main command)
Case 1:
Project name: My New App
Project is going to be created as: MyNewApp
Case 2:
Project name: My-New-App
Project is going to be created as: My-New-App
Case 3:
Project name: My_New_App
Project is going to be created as: My_New_App
Let me know if its all good at your end.
Check it out the news on v2 as well. Happy coding! :)


Fix varats bb config vals being overwritten

The failing test will be fixed by this: https://github.com/PolyJIT/benchbuild/pull/521


Panic in code_action()

initialized!
configuration changed!
stderr: thread 'main' panicked at src/server.rs:318:61:
stderr: called `Option::unwrap()` on a `None` value
stderr: stack backtrace:
stderr: 0: rust_begin_unwind
stderr: 1: core::panicking::panic_fmt
stderr: 2: core::panicking::panic
stderr: 3: core::option::unwrap_failed
stderr: 4: <vale_ls::server::Backend as tower_lsp::LanguageServer>::code_action::{{closure}}
stderr: 5: tower_lsp::jsonrpc::router::Router<S,E>::method::{{closure}}::{{closure}}::{{closure}}
stderr: 6: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
stderr: 7: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
stderr: 8: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll
stderr: 9: <core::pin::Pin<P> as core::future::future::Future>::poll
stderr: 10: <tower_lsp::service::LspService<S> as tower_service::Service<tower_lsp::jsonrpc::Request>>::call::{{closure}}
stderr: 11: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
stderr: 12: <futures_util::stream::futures_unordered::FuturesUnordered<Fut> as futures_core::stream::Stream>::poll_next
stderr: 13: <futures_util::stream::stream::buffer_unordered::BufferUnordered<St> as futures_core::stream::Stream>::poll_next
stderr: 14: <futures_util::stream::stream::map::Map<St,F> as futures_core::stream::Stream>::poll_next
stderr: 15: <futures_util::stream::stream::forward::Forward<St,Si,Item> as core::future::future::Future>::poll
stderr: 16: <futures_util::future::maybe_done::MaybeDone<Fut> as core::future::future::Future>::poll
stderr: 17: <futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
stderr: 18: tokio::runtime::context::runtime::enter_runtime
stderr: 19: tokio::runtime::runtime::Runtime::block_on
stderr: 20: vale_ls::main
stderr: note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Should be fixed now.
See also https://github.com/ChrisChinchilla/vale-vscode/issues/48

Updated in the latest pre-release 0.23.3


fix: properly close middleware using next()

Types of changes

[ ] Chore (a non-breaking change which is related to package maintenance)
[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This fixes a bug where r19's Express middleware would prematurely close the response before it completed. The bug seems isolated to usage in h3 (tests in Express worked before this PR).
Checklist:

[ ] My change requires an update to the official documentation.
[x] All TSDoc comments are up-to-date and new ones have been added where necessary.
[x] All new and existing tests are passing.

Codecov Report
Base: 86.92% // Head: 86.96% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (e128e7f) compared to base (7d7d43a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
+ Coverage   86.92%   86.96%   +0.04%
==========================================
  Files           9        9
  Lines         650      652       +2
  Branches       58       58
==========================================
+ Hits          565      567       +2
  Misses         84       84
  Partials        1        1

Impacted Files
Coverage Δ

src/createRPCMiddleware.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add a new field callback to the option

Add a new field callback to the option in order to enable us to execute arbitrary instructions after jumping to the target location.

Usage
require('lspfuzzy').setup {
    callback = function ()
        vim.api.nvim_command("normal! zz")
    end,
}

Motivation
After jumping to the target location, I often would like to execute the normal! zz command in order to redraw the cursor line to be the center of the window, or make the line to be blinking by using another vim plugin.

Hello! Great feature, thank you very much :) I've refactored a bit your pull request to avoid code duplication.

@ojroques
Thank you for merging it!


Repair dev/clay streams with dropped anchor commits

Currently we can repair streams where the genesis has been successfully anchored, but a later tip has lost its anchor. This is done by locating the missing anchor commit CID in the logs, constructing the corresponding commit ID, and forcing the node to load the stream at that state. This leads to the node going looking for that CID, finding it, validating the anchor proof, and re-applies it to the node state.
However, a large chunk of the broken streams lost the anchoring of the genesis commit. This makes the stream load a bit differently in the ceramic node logic, which currently doesn't allow loading an anchor directly on a genesis commit. Spencer in the 3box team is currently fixing this path in the node, so we should be able to do this shortly.

Update:

Everything following June 10th has been recovered
Waiting for more missing commits from CAS, possibly healing the rest


Make use of the User0 permission?

I just noticed a comment in token_key_new that the User0 permission is reserved for possible future use by the allocator so is cleared on SKeys at the moment. I only noticed because I'm using an SKey as a handy sealing type capability in the ISA test and it slightly reduces the coverage of the candperms test. It's not a big deal but just noting it here for future reference and to discuss possible uses.

Notes on this:

SObj allocation and sealing are combined at the moment. This makes sense because we have to know we're allocating a sealed object so we reserve space for the allocator. However, it means there's no token_seal function so it doesn't really make sense to have separate 'allocate' permission in the SKey.
If you can unseal an SObj then (I think) you can free it at current so a separate deallocate permission is only useful for deallocating the ability to deallocate without the ability to unseal. This does sound potentially useful as it potentially avoids a call into the owning compartment for deallocation.


Should be able to remove PDFs from the list

There should be a way to remove a PDF from the list, and then it won't show in the list ever.

Do have any more detail or input for this issue and/or how are you thinking this functionality should be? Should the user be able to select something like an X icon in the list itself to remove an item? Will there need to be a list of excluded pdfs saved somewhere(maybe local storage) to check against. Would the user be able to come to options and delete an item from the do not show list to see it again in the list?


Make Global Request Volume display last not null instead of mean

https://github.com/istio/istio/issues/28730
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2e3cd579d0ee5cc5b0df5fd43e5f2e7b010656da
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
a34cb411a0d8d871c3b4fe45bccceece0bba206e
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Do we need to do this for the other stat boxes as well?

Do we need to do this for the other stat boxes as well?

Yes, I just checked, those might cause misleading as well. We should update those charts to reflect this change.

@carolynhu: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Verified in one stat chart: https://snapshot.raintank.io/dashboard/snapshot/kQfLCcPkRlUfDehkgnvJahKd07S4I1tL?orgId=2
which send some request in a short period of time, and waiting for 5min, the chart still showing the last not null value.

One thing strange to me, even if I display the last not null:
https://snapshot.raintank.io/dashboard/snapshot/5PJ0x6YS90tng5U6K5gQf7A1fXfhqf6u
as you can see this general section, still shows the 0ops, and as you can see Last not null is correctly populated to the chart.


Fix OLS-596: timeout in BAM provider

Description
Fix OLS-596: timeout in BAM provider
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[x] Fix for random test failures

Related Tickets & Documents

Related Issue #OLS-596
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/approve
/lgtm


Error when downloading pretrained resnet200

Downloading: "https://www.dropbox.com/s/tchq8fbdd4wabjx/fbresnet_200-37304a01b.pth?dl=1" to
/home/leow/.torch/models/fbresnet_200-37304a01b.pth
Traceback (most recent call last):
File "/home/leow/anaconda3/lib/python3.6/urllib/request.py", line 1318, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/home/leow/anaconda3/lib/python3.6/http/client.py", line 1239, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/home/leow/anaconda3/lib/python3.6/http/client.py", line 1285, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/home/leow/anaconda3/lib/python3.6/http/client.py", line 1234, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/home/leow/anaconda3/lib/python3.6/http/client.py", line 1026, in _send_output
self.send(msg)
File "/home/leow/anaconda3/lib/python3.6/http/client.py", line 964, in send
self.connect()
File "/home/leow/anaconda3/lib/python3.6/http/client.py", line 1400, in connect
server_hostname=server_hostname)
File "/home/leow/anaconda3/lib/python3.6/ssl.py", line 401, in wrap_socket
_context=self, _session=session)
File "/home/leow/anaconda3/lib/python3.6/ssl.py", line 808, in init
self.do_handshake()
File "/home/leow/anaconda3/lib/python3.6/ssl.py", line 1061, in do_handshake
self._sslobj.do_handshake()
File "/home/leow/anaconda3/lib/python3.6/ssl.py", line 683, in do_handshake
self._sslobj.do_handshake()
ConnectionResetError: [Errno 104] Connection reset by peer
It seems that the download link doesn't work.

That's a link to my own dropbox. It worked last time I tried, and still seems to work for me. Try manually if not. There are limits on how much can be downloaded so maybe they were hit. If anything I'll be stripping those links, not replacing them as I do not have a better or alternate hosting solution...

You can also re-create the pth if you use the https://github.com/clcarwin/convert_torch_to_pytorch  converter on the ResNet-200 t7 from https://github.com/facebook/fb.resnet.torch/tree/master/pretrained

When I run the torch converter on that file, I get an error because the t7
file has Cuda tensors in it:
AttributeError: type object 'torch.cuda.FloatStorage' has no attribute
'from_buffer'
Did you run into this issue?
Regards,
Leo
On Tue, Aug 29, 2017 at 4:18 PM, Ross Wightman<EMAIL_ADDRESS>wrote:

You can also re-create the pth if you use the https://github.com/clcarwin/
convert_torch_to_pytorch converter on the ResNet-200 t7 from
https://github.com/facebook/fb.resnet.torch/tree/master/pretrained
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rwightman/pytorch-planet-amazon/issues/1#issuecomment-325807382,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALkeSyPH_Q0WCa7kkZm_eRIGHePPMNQGks5sdIA9gaJpZM4PGXIQ
.

Right, that's a problem.
If you've got torch7 installed, from the th console you can do the following to convert it from a cuda model to a cpu float which will work with the conversion script...
th> import 'cudnn'
th> model = torch.load('./resnet-200.t7')
th> model = model:float()
th> torch.save('./resnet-200-cpu.t7', model)


When is the new release?

Hi! When is the new release?

The version 2 of the framework will be available soon. If you need one of the new features, you can migrate to the 2.0.0-beta.1 prerelease.


[eslint] use azure sdk eslint config helper

So that custom configurations won't override markdown rules
NO_CI

API change check
API changes are not detected in this pull request.

known unit test failures for several packages. not related to linting.  overriding.

/check-enforcer override


Option to enter seed phrase to recover breez SDK wallet

Implemented the issue #51

Summary of our design call:

[ ] Remove big button
[ ] Change "login with Phone or Email" links to "Restore Wallet"

[ ] Implement screen UX flow based on wireframe below
[ ] When logged in, add "Restore Wallet" Option in settings, which will delete the current wallet and restore one from seed phrase. IMPORTANT: need warning alert to let user know they will LOSE the current breez wallet!


Comment edit form: form_rest twig function instead of hardcoded token field name

I want use the FOSCommentBundle with a eZ Platform installation.
There it is a different token field name.
https://github.com/ezsystems/ezplatform/blob/master/app/config/config.yml#L66
In all other forms the token is set with the form_rest function.
So it would be nice to change it here also.

Could you re-open this PR against the 2.x branch?

I rebased the PR to the 2.x branch

:+1:

Thanks.


WIP: WRKLDS-1367: Bump(DeschedulerPolicy)=descheduler/v1alpha2

[x] migrate from v1alpha1 to v1alpha2
[x] drop bindata/assets/profiles as v1alpha2 is composed differently
[ ] update unit tests

/retest-required

/retest-required


Add a diagnostics accessor

Similar to the diagnosticCount accessor, provide an interface to get diagnostics from a given state.
Use Case
We want to implement and external Lint panel, similar to the Problems tab in VS-Code, that accumulates all linting messages accross different components. For this, we need a way to access the currently active Diagnostics in the Editor.

This will return the diagnostics with their initial positions, though, which may not be accurate when the document has changed in the meantime. For your use case, would defining an update handler that listens for transactions with the setDiagnosticsEffect and pushes them out to your list not also work?

would defining an update handler that listens for transactions with the setDiagnosticsEffect and pushes them out to your list not also work?

Yes, I have not thought about that. I just tried it our and this will solve our problem.
Thank you for your input and the quick response 🏆


[Robust] Clicking is broken

Is this fixed by https://github.com/wixoaGit/OpenDream/commit/5e41d12409a0b051928777227ca56d457dbf2573 ?

Is this fixed by 5e41d12 ?

No. Clicking itself is not broken, Click() is currently called whenever you click an atom. The real issue is that none of the click parameters are passed to the proc at the moment (icon-x, shift, ctrl, etc). SS13 codebases do not like this.
https://github.com/wixoaGit/OpenDream/blob/RobustToolbox/OpenDreamRuntime/Input/MouseInputSystem.cs#L37
//TODO: click params ("icon-x", "icon-y", "screen-loc", "shift", "ctrl", "alt")

The real issue is that none of the click parameters are passed to the proc at the moment

A quick look revealed that this was not the real reason that clicking wasn't working in ss13 codebases. usr was null when calling /client.Click(), leading to an exception when attempting to call a proc on it. This was fixed in 0b79bf13b715772b04c71728dc7a2249bc2e7cc0.


Incorrect type defs for launch fields

While using the LaunchFind function in the GraphiQL application, I am unable to find 'launch_success' or 'land_success'. In the documentation, they are listed as being of String type, but in the API they are of Boolean type.
I've tried setting my query variable to a String type: "true" or "false". No errors are thrown, however the query returns empty.
I expect to be able to use the LaunchFind function on these two fields: 'launch_success' and 'land_success', however, I'm unable to because the default type defs are incorrect.
`
query launches($success: String) {
launches(find: {launch_success: $success}) {
id
}
}
{
"success": "true"
}
`

I am facing the same problem, any update on this?
{   launchesPastResult(find: {launch_success: "true"}) {     data {       mission_name       launch_success     }   } }
this returns empty array


Sprint 1: Develop a single Linux persistence method with root access

https://github.com/Nekrosis-ISS-Capstone/Nekrosis/commit/ba541b69011577e6010c7fafb35d31f8b546b053


Prog bundle - fix #88

This adds support for Record as a super-class of Bundle for Module.io
NOTE - This includes #89 in order to facilitate testing.

@jackkoenig I'm a little concerned about the fact that these changes are required.  I thought the Record/Bundle changes would be more transparent.  But I'd rather get stuff out there and figure out if there's other problems

I'm not sure what you mean by the changes being more transparent, but the purpose of Record was to change the type hierarchy of Bundle such that it is now a more specialized case of a more general thing (ie. a Bundle is simply a Record that automatically populates the elements via reflection and attempts to implement cloneType automagically). I'm not sure if there could have been any other way to do it.

I should have said less API changing, but then again chisel-testers is kind of a special case when it comes to API usage.  I'm for moving forward

I see, yeah. Unfortunately, the very nature of Record is API changing so there wasn't much of a choice :(


ValueError: 'box_aspect' and 'fig_aspect' must be positive

Hello all,
I've run this software in a similar format and have gotten results, but I am having this error this time. Do you happen to have any examples of how to fix this?
The code that I have used is below and it has worked in another instance.
#%% Begin object creation for pyWGCNA
allGeneExp = PyWGCNA.WGCNA(name = 'all', species='bacteria', geneExpPath='/gene_Exp.csv', outputPath='/pyWGCNA_Files/', save=True)

allGeneExp.updateSampleInfo(path = '/sample_Meta.csv')

allGeneExp.setMetadataColor('Depth', {'Deep': 'green', 'Shallow': 'yellow'})
allGeneExp.setMetadataColor('Treatment', {'C': 'thistle', 'M': 'plum', 'A': 'violet', 'R': 'purple'})

allGeneExp.updateGeneInfo(path = '/gene_meta.csv', sep = ',')

#%% Perform initial analysis
allGeneExp.preprocess()

allGeneExp.findModules()

allGeneExp.analyseWGCNA()

allGeneExp.top_n_hub_genes(moduleName="brown", n=100)

Short examples of the files are below
sample_Meta.csv
Sample_number,Depth,Treatment
1,Shallow,C
2,Shallow,A
3,Deep,R
4,Deep,C
5,Shallow,A

gene_Meta.csv
New_ID,circRNA_type,gene_id,circ_len
LjG1.1_chloro:100061-100456,ciRNA,LotjaGiC1v0009300,395
LjG1.1_chloro:100061-100478,ciRNA,LotjaGiC1v0009300,417
LjG1.1_chloro:100918-101092,ciRNA,LotjaGiC1v0009400,174
LjG1.1_chloro:100918-101265,ciRNA,LotjaGiC1v0009400,347

gene_Exp.csv
Sample_number,LjG1.1_chloro:100061-100456,LjG1.1_chloro:100061-100478,LjG1.1_chloro:100918-101092,LjG1.1_chloro:100918-101265,LjG1.1_chloro:100918-101341
1,0.0,0.0,0.0,0.0,0.0
2,0.0,0.0,0.0,0.0,0.0
3,0.0,0.0,0.0,0.0,0.0
4,0.0,0.0,0.0,0.0,1529.6449005845536
5,0.0,0.0,0.0,0.0,0.0

Would love to know how to fix this as I think that the visuals this package provides are very nice.
Hoping to hear from you soon.
Best,
Kirtley

Just to follow up. I'm getting this error running in VS code. I tracked the error to the "source" code and manually changed the fix_aspect and box_aspect to be 1 and it still did not work. I also attempted renaming columns without underscores as I saw that might be a fix.

Hi @BKAmos,
would you mind sending your full error?

Hi all.
@nargesr I got a similar error running analyseWGCNA()
Details

Analysing WGCNA...
Calculating module trait relationship ...

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[26], line 1
----> 1 pywgcna_scak.analyseWGCNA()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/PyWGCNA/wgcna.py:388, in WGCNA.analyseWGCNA(self, order, geneList, show)
    385         self.moduleTraitPvalue.loc[i, j] = tmp[1]
    387 if self.save:
--> 388     self.module_trait_relationships_heatmap(metaData=self.datExpr.obs.columns.tolist(),
    389                                             show=show,
    390                                             file_name='module-traitRelationships')
    391 print("\tDone..\n")
    393 print(f"{OKCYAN}Adding (signed) eigengene-based connectivity (module membership) ...{ENDC}")

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/PyWGCNA/wgcna.py:2775, in WGCNA.module_trait_relationships_heatmap(self, metaData, show, file_name)
   2769 labels = (np.asarray(["{0}\n({1})".format(cor, pvalue)
   2770                       for cor, pvalue in zip(tmp_cor.values.flatten(),
   2771                                              tmp_pvalue.values.flatten())])) \
   2772     .reshape(self.moduleTraitCor.T.shape)
   2774 sns.set(font_scale=1.5)
-> 2775 res = sns.heatmap(self.moduleTraitCor.T, annot=labels, fmt="", cmap='RdBu_r',
   2776                   vmin=-1, vmax=1, ax=ax, annot_kws={'size': 20, "weight": "bold"},
   2777                   xticklabels=xlabels, yticklabels=ylabels)
   2778 res.set_xticklabels(res.get_xmajorticklabels(), fontsize=20, fontweight="bold", rotation=90)
   2779 res.set_yticklabels(res.get_ymajorticklabels(), fontsize=20, fontweight="bold")

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/seaborn/matrix.py:459, in heatmap(data, vmin, vmax, cmap, center, robust, annot, fmt, annot_kws, linewidths, linecolor, cbar, cbar_kws, cbar_ax, square, xticklabels, yticklabels, mask, ax, **kwargs)
    457 if square:
    458     ax.set_aspect("equal")
--> 459 plotter.plot(ax, cbar_ax, kwargs)
    460 return ax

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/seaborn/matrix.py:340, in _HeatMapper.plot(self, ax, cax, kws)
    337 plt.setp(ytl, va="center")  # GH2484
    339 # Possibly rotate them if they overlap
--> 340 _draw_figure(ax.figure)
    342 if axis_ticklabels_overlap(xtl):
    343     plt.setp(xtl, rotation="vertical")

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/seaborn/utils.py:84, in _draw_figure(fig)
     82 """Force draw of a matplotlib figure, accounting for back-compat."""
     83 # See https://github.com/matplotlib/matplotlib/issues/19197 for context
---> 84 fig.canvas.draw()
     85 if fig.stale:
     86     try:

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/backends/backend_agg.py:388, in FigureCanvasAgg.draw(self)
    385 # Acquire a lock on the shared font cache.
    386 with (self.toolbar._wait_cursor_for_draw_cm() if self.toolbar
    387       else nullcontext()):
--> 388     self.figure.draw(self.renderer)
    389     # A GUI class may be need to update a window using this draw, so
    390     # don't forget to call the superclass.
    391     super().draw()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/artist.py:95, in _finalize_rasterization.<locals>.draw_wrapper(artist, renderer, *args, **kwargs)
     93 @wraps(draw)
     94 def draw_wrapper(artist, renderer, *args, **kwargs):
---> 95     result = draw(artist, renderer, *args, **kwargs)
     96     if renderer._rasterizing:
     97         renderer.stop_rasterizing()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/artist.py:72, in allow_rasterization.<locals>.draw_wrapper(artist, renderer)
     69     if artist.get_agg_filter() is not None:
     70         renderer.start_filter()
---> 72     return draw(artist, renderer)
     73 finally:
     74     if artist.get_agg_filter() is not None:

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/figure.py:3143, in Figure.draw(self, renderer)
   3139     return
   3141 with self._render_lock:
-> 3143     artists = self._get_draw_artists(renderer)
   3144     try:
   3145         renderer.open_group('figure', gid=self.get_gid())

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/figure.py:231, in FigureBase._get_draw_artists(self, renderer)
    229 for ax in self._localaxes:
    230     locator = ax.get_axes_locator()
--> 231     ax.apply_aspect(locator(ax, renderer) if locator else None)
    233     for child in ax.get_children():
    234         if hasattr(child, 'apply_aspect'):

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/axes/_base.py:1928, in _AxesBase.apply_aspect(self, position)
   1926 if self._box_aspect is not None:
   1927     pb = position.frozen()
-> 1928     pb1 = pb.shrunk_to_aspect(self._box_aspect, pb, fig_aspect)
   1929     self._set_position(pb1.anchored(self.get_anchor(), pb), 'active')
   1930     if aspect == "auto":

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/transforms.py:534, in BboxBase.shrunk_to_aspect(self, box_aspect, container, fig_aspect)
    524 """
    525 Return a copy of the `Bbox`, shrunk so that it is as
    526 large as it can be while having the desired aspect ratio,
   (...)
    531 ratio of the absolute dimensions, not the relative dimensions.
    532 """
    533 if box_aspect <= 0 or fig_aspect <= 0:
--> 534     raise ValueError("'box_aspect' and 'fig_aspect' must be positive")
    535 if container is None:
    536     container = self

ValueError: 'box_aspect' and 'fig_aspect' must be positive

Error in callback <function _draw_all_if_interactive at 0x151c08839040> (for post_execute):

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/pyplot.py:197, in _draw_all_if_interactive()
    195 def _draw_all_if_interactive() -> None:
    196     if matplotlib.is_interactive():
--> 197         draw_all()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/_pylab_helpers.py:132, in Gcf.draw_all(cls, force)
    130 for manager in cls.get_all_fig_managers():
    131     if force or manager.canvas.figure.stale:
--> 132         manager.canvas.draw_idle()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/backend_bases.py:1893, in FigureCanvasBase.draw_idle(self, *args, **kwargs)
   1891 if not self._is_idle_drawing:
   1892     with self._idle_draw_cntx():
-> 1893         self.draw(*args, **kwargs)

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/backends/backend_agg.py:388, in FigureCanvasAgg.draw(self)
    385 # Acquire a lock on the shared font cache.
    386 with (self.toolbar._wait_cursor_for_draw_cm() if self.toolbar
    387       else nullcontext()):
--> 388     self.figure.draw(self.renderer)
    389     # A GUI class may be need to update a window using this draw, so
    390     # don't forget to call the superclass.
    391     super().draw()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/artist.py:95, in _finalize_rasterization.<locals>.draw_wrapper(artist, renderer, *args, **kwargs)
     93 @wraps(draw)
     94 def draw_wrapper(artist, renderer, *args, **kwargs):
---> 95     result = draw(artist, renderer, *args, **kwargs)
     96     if renderer._rasterizing:
     97         renderer.stop_rasterizing()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/artist.py:72, in allow_rasterization.<locals>.draw_wrapper(artist, renderer)
     69     if artist.get_agg_filter() is not None:
     70         renderer.start_filter()
---> 72     return draw(artist, renderer)
     73 finally:
     74     if artist.get_agg_filter() is not None:

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/figure.py:3143, in Figure.draw(self, renderer)
   3139     return
   3141 with self._render_lock:
-> 3143     artists = self._get_draw_artists(renderer)
   3144     try:
   3145         renderer.open_group('figure', gid=self.get_gid())

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/figure.py:231, in FigureBase._get_draw_artists(self, renderer)
    229 for ax in self._localaxes:
    230     locator = ax.get_axes_locator()
--> 231     ax.apply_aspect(locator(ax, renderer) if locator else None)
    233     for child in ax.get_children():
    234         if hasattr(child, 'apply_aspect'):

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/axes/_base.py:1928, in _AxesBase.apply_aspect(self, position)
   1926 if self._box_aspect is not None:
   1927     pb = position.frozen()
-> 1928     pb1 = pb.shrunk_to_aspect(self._box_aspect, pb, fig_aspect)
   1929     self._set_position(pb1.anchored(self.get_anchor(), pb), 'active')
   1930     if aspect == "auto":

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/transforms.py:534, in BboxBase.shrunk_to_aspect(self, box_aspect, container, fig_aspect)
    524 """
    525 Return a copy of the `Bbox`, shrunk so that it is as
    526 large as it can be while having the desired aspect ratio,
   (...)
    531 ratio of the absolute dimensions, not the relative dimensions.
    532 """
    533 if box_aspect <= 0 or fig_aspect <= 0:
--> 534     raise ValueError("'box_aspect' and 'fig_aspect' must be positive")
    535 if container is None:
    536     container = self

ValueError: 'box_aspect' and 'fig_aspect' must be positive

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/IPython/core/formatters.py:340, in BaseFormatter.__call__(self, obj)
    338     pass
    339 else:
--> 340     return printer(obj)
    341 # Finally look for special method names
    342 method = get_real_method(obj, self.print_method)

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/IPython/core/pylabtools.py:152, in print_figure(fig, fmt, bbox_inches, base64, **kwargs)
    149     from matplotlib.backend_bases import FigureCanvasBase
    150     FigureCanvasBase(fig)
--> 152 fig.canvas.print_figure(bytes_io, **kw)
    153 data = bytes_io.getvalue()
    154 if fmt == 'svg':

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/backend_bases.py:2158, in FigureCanvasBase.print_figure(self, filename, dpi, facecolor, edgecolor, orientation, format, bbox_inches, pad_inches, bbox_extra_artists, backend, **kwargs)
   2155     # we do this instead of `self.figure.draw_without_rendering`
   2156     # so that we can inject the orientation
   2157     with getattr(renderer, "_draw_disabled", nullcontext)():
-> 2158         self.figure.draw(renderer)
   2159 if bbox_inches:
   2160     if bbox_inches == "tight":

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/artist.py:95, in _finalize_rasterization.<locals>.draw_wrapper(artist, renderer, *args, **kwargs)
     93 @wraps(draw)
     94 def draw_wrapper(artist, renderer, *args, **kwargs):
---> 95     result = draw(artist, renderer, *args, **kwargs)
     96     if renderer._rasterizing:
     97         renderer.stop_rasterizing()

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/artist.py:72, in allow_rasterization.<locals>.draw_wrapper(artist, renderer)
     69     if artist.get_agg_filter() is not None:
     70         renderer.start_filter()
---> 72     return draw(artist, renderer)
     73 finally:
     74     if artist.get_agg_filter() is not None:

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/figure.py:3143, in Figure.draw(self, renderer)
   3139     return
   3141 with self._render_lock:
-> 3143     artists = self._get_draw_artists(renderer)
   3144     try:
   3145         renderer.open_group('figure', gid=self.get_gid())

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/figure.py:231, in FigureBase._get_draw_artists(self, renderer)
    229 for ax in self._localaxes:
    230     locator = ax.get_axes_locator()
--> 231     ax.apply_aspect(locator(ax, renderer) if locator else None)
    233     for child in ax.get_children():
    234         if hasattr(child, 'apply_aspect'):

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/axes/_base.py:1928, in _AxesBase.apply_aspect(self, position)
   1926 if self._box_aspect is not None:
   1927     pb = position.frozen()
-> 1928     pb1 = pb.shrunk_to_aspect(self._box_aspect, pb, fig_aspect)
   1929     self._set_position(pb1.anchored(self.get_anchor(), pb), 'active')
   1930     if aspect == "auto":

File /nfs/turbo/umms-kykwan/projects/alex_kwan/py_scwgcna/env/lib/python3.9/site-packages/matplotlib/transforms.py:534, in BboxBase.shrunk_to_aspect(self, box_aspect, container, fig_aspect)
    524 """
    525 Return a copy of the `Bbox`, shrunk so that it is as
    526 large as it can be while having the desired aspect ratio,
   (...)
    531 ratio of the absolute dimensions, not the relative dimensions.
    532 """
    533 if box_aspect <= 0 or fig_aspect <= 0:
--> 534     raise ValueError("'box_aspect' and 'fig_aspect' must be positive")
    535 if container is None:
    536     container = self

ValueError: 'box_aspect' and 'fig_aspect' must be positive

<Figure size 2000x0 with 2 Axes>

Hi @ofarrelle,
Can you send me your PyWGCNA object as well?
you can email me if that's easier for you<EMAIL_ADDRESS>

Hi @nargesr,
Attached is my error output as a whole.
pyWGCNA_error.log
I'll send you what I think is the PyWGCNA object through email.
Let me know how else I can help.
Best,
Kirtley

Hi @ofarrelle,
I don't see any information you have about your samples (basically self.datExpr.obs is empty) and that's why you got this error.
I just released a new version of PyWGCNA(1.20.3) to avoid giving you this error and skip the plots that need this kind of information. Please let me know if you have any problems.

hi @BKAmos
your self.datExpr.obs has two columns but both of them have Nan values. Please try to fix this and rerun the function and let me know if you have any errors.
here's the output of self.datExpr.obs as a reference:

HI @nargesr,
Problem solved!
So, I just added an _C/_A/_R/_M to the sample numbers and it worked great.
For example
This:
SampleNumber,Depth,Treatment 1_C,Shallow,C 2_A,Shallow,A 3_R,Deep,R 4_C,Deep,C 5_A,Shallow,A 6_R,Shallow,R 7_C,Deep,C
Instead of this:
SampleNumber,Depth,Treatment 1,Shallow,C 2,Shallow,A 3,Deep,R 4,Deep,C 5,Shallow,A 6,Shallow,R 7,Deep,C
I'm not sure where in the code this might be the problem. Maybe a string vs integer interpretation of sample ID?
Anway, I can close this comment unless @ofarrelle would like to keep it open.
Best,
Kirtley

Thanks for the info folks! I’ll get back to you when I’m back at my machine on Monday.

So sorry for the delay.
Thank you @nargesr for the update! Version 1.20.3 avoided the error for me.
Populating self.datExp.obs was also an effective solution.
Happy to close this issue. Cheers


feat(client): expose BitcoinTransactionData in onchain deposit

fixes #3324

This would be a great one to backport. But it's backwards-incompatible. Can we build a database migration for it?

We don't currently have the framework setup for client side db migrations. Most of the work is done, we just need to add an equivalent call to apply_migrations on the client side.
Are we sure we want db migrations for states within the state machines? It's not clear to me if these will always be backwards compatible (i.e if the execution semantics of a state have changed, do we want to restart the client in this state without having executed the previous states?)
Perhaps we should make a separate issue to discuss

@m1sterc001guy https://github.com/fedimint/fedimint/issues/3417
@Maan2003 needs rebase to fix flake self-check


World Time app

I want to add my Worldtime app to your repo under hacktoberfest 2023.

@kaushal1717 here you go


Bump haskell language server to <IP_ADDRESS>

[x] Bump haskell language server from <IP_ADDRESS> to <IP_ADDRESS>

Hopefully more stable
Requires haskell.nix bump

Comments

Issue Number

Some CI HLS check failing with:
 getIdeGlobalExtras, no entry for DisplayTHWarning

Closing for now.


Mailchimp Integration With Current Form Blocks Available

Recently, I tried to integrate MailChimp API to already existing form block from ReflexJS in my blog, however I'm not able to display success and error message on Submission.
Here's what I've done so far.

Installed the plugin and setup in gatsby-config.js

Created a New Subscribe Component in src/@reflexjs/components. Here's my Subscribe.js file:

import addToMailchimp from "gatsby-plugin-mailchimp"
import React from "react"
import { Flexbox, P, Form, Label, Input, Button, VisuallyHidden, H4, Div } from "@reflexjs/components"

export default class Subscribe extends React.Component {
  constructor() {
    super()
    this.state = { name: '', email: '', result: null }
  }

  handleSubmit = async (e) => {
    const result = await addToMailchimp(this.state.email, { FNAME: this.state.name })
    if (result.result === 'error') {
      alert(`Whoops, ${this.state.name} you're already subscribed!`)
    } else {
      alert(`Thank you for subscribing ${this.state.name}!`)
    }
    this.setState({ result: result })
  }

  handleEmailChange = (event) => {
    this.setState({ email: event.target.value })
  }

  handleNameChange = (event) => {
    this.setState({ name: event.target.value })
  }

render() {
    return (
    <Flexbox flexDirection="column" textAlign="center">

Sign up for The Best Bits

      A weekly round up of the best content from In Plain English, handpicked by our Founder

      <Form d="grid" col="2|auto auto" gap="4" onFinish={this.handleSubmit}>
      <VisuallyHidden>
          Email
          Name
        </VisuallyHidden>
        <Input
          type="email"
          id="form-04-email"
          name="email"
          placeholder="Type your email"
          variant="md"
          onChange={this.handleEmailChange}
          rules={[{ required: true, message: 'Please input your email.' }]}
        />
        <Input
          type="name"
          id="form-04-name"
          name="name"
          placeholder="Type your name"
          variant="md"
          onChange={this.handleNameChange}
          rules={[{ required: true, message: 'Please input your name.' }]}
        />
        <Button
          variant="primary md"
          label="Submit"
          type="submit"
        > Join
        </Button>
      </Form>

      </Flexbox>
    )
  }
}

And I imported import Subscribe from "../components/Subscribe" and called <Subscribe /> in my post.js.
Now, when I press Join Button, the values get appended to address, no result. I attempted with gatsby build as well, same result. Can you help me figure it out please?

is addToMailchimp not called at all?
Can you try with:
handleSubmit = async (e) => {
+ e.preventDefault()

Its working now, I removed the plugin and reinstalled everything with above change, and is now successfully delivering the details.
So, my other question is:
Can I import and add it to a separate page (for instance, /newsletter)?
I'm getting path error while trying to import and use <Subscribe />.
Subscribe.js is located in src/@reflexjs/components and /newsletter is a normal page.

You don't really need to place it inside src/@reflexjs/components. Your custom components can go inside src.
Place your file at src/Subscribe.js.
Then include it in your page as follows:
---
title: Title of page
---

import Subscribe from "../../src/Subscribe"

<Subscribe />

Thanks, it worked :+1:


Import bug using vite

Hello,
Using version 0.18 and vite with svelte plugin. If I use this import syntax (as suggested in components docs page):
<script>
  import { Button } from "carbon-components-svelte";
</script>

<Button>Primary button</Button>

... then I have this bug shown up on chrome:
Uncaught SyntaxError: The requested module<EMAIL_ADDRESS>does not provide an export named 'default'

If use this syntax, everything works.
<script>
  import { Button } from "carbon-components-svelte/src/Button";
</script>

<Button>Primary button</Button>

See https://github.com/IBM/carbon-components-svelte/issues/249
The workaround is to create a vite.config.js and add flatpickr to the list of optimizable dependencies:
// vite.config.js
module.exports = {
  optimizeDeps: {
    include: [
      "flatpickr",
      "flatpickr/dist/l10n/index.js",
      "flatpickr/dist/plugins/rangePlugin",
    ],
  },
};

That worked, thanks. Somehow I missed it, I apologize.

No worries – that's on me. It needs to be documented.
Btw, since version 0.16, the "flatpickr/dist/l10n/index.js" import can be omitted, thanks to @weaseldotro


enable support for shebangs

node.js allows the use of UNIX shebangs in scripts:
#!/path/to/node

Is it possible to support these by option in parse-js?

I guess they always appear at the top of the program? If so, it'd be possible to simply have some wrapper skip them before passing the stream/substring on to parse-js.


use translatable keys instead of plain text

after this merge you should create a 1.0 version an change 0.2-dev to ```1.0````
thank you

great thanks


Update harness-platform-faqs.md

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ X] Feature

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d5af73b1e8ef6af4808f82--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d5fc21d64de6ac5a33fe2c--harness-developer.netlify.app


Version range parsing

When using something like this: [1.9.1,4) it throws and invalid version error.
dependencies: [       {id: "jQuery", version: "[1.9.1,4)"},       {id: "FontAwesome", version: "4.7.0"}     ],
That version range is from bootstrap v3 nuget specification file.

I got it to work with this regex expression: ^(\[[0-9\,\.]+\)|\]|\(|\[[0-9\,\.]+\)|\]|\([0-9\,\.]+\]|\)|[0-9]+\.[0-9]+)$


Derive Clone to Config and InitParams

There are some situations in which someone might need to use grammers_client::client::client::Client::Connect multiple times (or at least I do), for example, when using multiple sessions/clients, or when changing the connection's datacenter (via an edit of config.session).
Deriving Clone for grammers_client::client::client::Config might be helpful in this regard (Connect takes a Config), allowing those who want, to write something like:
let config1 = Config {
    *fields,
};
let mut client1 = Client::connect(config1.clone()).await?;

let config2 = Config {
    session: Session::load_file_or_create("file.session")?,
    ..config1
};
let mut client2 = Client::connect(config2).await?;

instead of:
let config1 = Config {
    *fields,
};
let mut client1 = Client::connect(config1).await?;

let config2 = Config {
    *fields,
};
let mut client2 = Client::connect(config2).await?;

The same applies to grammers_client::client::client::InitParams, that would benefit from deriving Clone in a similar way (other than being needed to derive Clone on Client).

My main concern here is that the config includes the Session, which is not intended to be used by multiple clients at once. Misbehaviour is likely to occur if the same session is reused. However, the InitParams can definitely derive Clone. Would that alleviate the problem in any meaningful way?
I'd recommend creating a closure which you can call over and over to create new distinct Config, or even a standalone fn give_me_config() -> Config.

What you're saying is of course true, and I agree with you to a certain degree. But this would work without any problems if done correctly.
In any case, there's no current way to prevent a user from writing this and running in misbehaviour:
let session1 = Session::load_file_or_create("file.session")?;
let config1 = Config {
    session: session1,
    *fields,
};
let mut client1 = Client::connect(config1).await?;

let config2 = Config {
    session: session1,
    *fields,
};
let mut client2 = Client::connect(config2).await?;

Anyway, if deriving Clone to Config truly concerns you, it would still be nice to derive Clone to InitParams.
I'll follow your suggestion and I'll write a specific function to generate the config.

It's true the library can't fully mitigate misuse (well, without global shenanigans), but I still feel more comfortable not having Clone. A .clone() call is far easier to type than the full Session::load_file_or_create. We can add Clone to InitParams. Feel free to send a PR for that.
If the function to generate config turns out to be too annoying to write for whatever reason we could argue about that a bit more and maybe I'd change my mind, but we'd have to document against the potential misuse (and documentation is harder to enforce).

Alright, thanks for the PR and understanding my POV.


doxygen generation removed

Summary: Doxygen generation removed from github pages yaml
Type: Fix
Test Plan: UT
Jira: RIALTO-272

https://jenkins.code.rdkcentral.com/job/github-triggered/35385/ started

https://jenkins.code.rdkcentral.com/job/build-component/73405/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/3206/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/6189/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/35387/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/3207/ started

https://jenkins.code.rdkcentral.com/job/build-component/73406/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/6190/ started.

build-brcm-refboard Console Log uploaded to Gist URL: https://gist.github.com/rdkcmf-jenkins/0fc72f61b9cb8f0f62630cf8fea2ecaf

Sanity tests for ['RPI3 Hybrid/MC'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/14397/

Sanity tests for ['RPI3 Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/14396/

Sanity tests for ['RPI3 Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/14398/

Sanity tests for ['RPI3 Hybrid/MC'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/14399/


Cannot access environment variables in useRuntimeConfig using source .env && node server.mjs

Environment

Operating System: Darwin
Node Version:     v20.1.0
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devtools, runtimeConfig
Runtime Modules:  -
Build Modules:    -

Reproduction

Clone https://github.com/xuzuodong/nuxt-source-test
run pnpm i
run pnpm dev, open localhost:3000, and then console will print runtime config object, including environment variable testEnv, which is accessible:

{
  app: { baseURL: '/', buildAssetsDir: '/_nuxt/', cdnURL: '' },
  nitro: { envPrefix: 'NUXT_', routeRules: { '/__nuxt_error': [Object] } },
  public: {},
  testEnv: '12345678asdf'
}

quit the dev process and run pnpm build, then pnpm start
open localhost:3000, and then console will print runtime config, and value of environment variable testEnv is missing:

{
  app: { baseURL: '/', buildAssetsDir: '/_nuxt/', cdnURL: '' },
  nitro: {
    envPrefix: 'NUXT_',
    routeRules: { '/__nuxt_error': [Object], '/_nuxt/**': [Object] }
  },
  public: {},
  testEnv: ''
}

Describe the bug
According to the doc, runtime config values are automatically replaced by matching environment variables at runtime. This works in development mode, but different behavior happens when I build and run the output with .env file sourced.
According to the env doc, after server is built, environment variables should be set before server running, one recommended way is to source env file using source .env && node .output/server/index.mjs.
However, such script cannot successfully inject environment variables declared in .env.
Is there something I missed?
Additional context
A temporary workaround I'm using now is manually assign environment variables to runtimeConfig in nuxt.config.ts:
  runtimeConfig: {
    testEnv: process.env.NUXT_TEST_ENV
  }

Logs
No response

You're right, running source .env won't work, though this is not a Nuxt issue but a documentation point for how to load environment variables into a shell.
Here are two ways of loading in variables correctly:
NUXT_TEST_ENV=thing node .output/server/index.mjs
# or
export NUXT_TEST_ENV=thong
node .output/server/index.mjs

A PR to improve the docs here would be welcome, perhaps with details on Windows, Linux + MacOS 🙏
And, as always, note that running nuxi preview will handle this automatically if you are wanting simply to preview your site locally.

@danielroe Hi, thank you for prompt response to my issue. And I'm willing to help improving the docs!
Though I still have a question:
We still need a way to load all environment variables defined in .env. These two ways you mentioned is only suitable for a small number of environment variables in project, and users may have large numbers of environment variables defined in a .env file and it's certainly not elegant to explicitly define them all in scripts in package.json.
So after doing some research, I found a simple way to load all environment variables defined in .env, and seems to work perfectly:
# instead of this
source .env && node server.js
# do this
export $(cat .env | egrep -v '#|^$' | xargs) && node server.js

Do you think this is a proper way and can go into docs?

what about ?
import 'dotenv/config'

export default defineNuxtConfig({
  ...your config
})


Issue with mAP metric during training

There is an issue with the mAP calculation (technically with the bbox postprocessing) in the training script. This should at the very least be resolved by shortly removing the mAP calculation (such that training can continue). On the longer term a solution should be found for this issue alltogether.

A workaround of commenting out the breaking code has been implemented. I should check out why this even happens in the first place.


Unable to change download path in config.toml

Describe the bug
I'm trying to download manga to a specific folder, but mangal keeps downloading to some temporary folder instead regardless of what I put in the download path. I am using the default config file (from config init) with only the download path changed to
download_path = '/mangal/someFolder'
Reproduction steps

Change download_path in config.toml
Download manga chapter (currently using chapter 1 of one piece on manganelo)
Chapter is downloaded to a folder called 'private/var/folders/0m/zj0991.../T'

Expected behavior
Chapter should be downloaded to the specified filepath.
Additional context
No response
Operating System
macOS
Checks

[X] I've used mangal doctor and it didn't help

Hello! Try this download_path = '$HOME/mangal/someFolder

Yeah that was the issue, was pressing r. Thank you!


it support put the comment input box in the top/ get the count of the comments?

it support put the comment input box in the top?
and provided a function to call to get the count of the comments?

duplicate of #182

thx,
it seem not merge the pull requests,
and the second question:
can provided a function to call to get the count of the comments?


Flatten policy version in rode_policy

No benefit to nesting it under policy and it adds some complexity

Addressed in https://github.com/alexashley/terraform-provider-rode/commit/2527cb1667be799befcb0547fabb0bf68676d9fb


A <marquee> feature for 1.10

I was tossing and turning last night because I knew the release of 1.10 was coming up, but I was disappointed that we didn't have a really huge feature for it.
I mean, sure, there's that nice performance improvement @davekaro contributed that allows Phlex to render at 1.4 Gbps on an M3 chip.
And there is also that new Phlex::Kit feature that @joeldrapper cooked up that makes it easier than ever to render component. You don't even have to say render now!
And I guess we also are adding CSV rendering support with Phlex::CSV, which improves our output format rendering capacity by 33.3%.
And those are cool and all, but there's just no big... marquee feature, you know? Something that stands out above the rest and declares "This is why this release is happening NOW".
Well, I think I may have found it. The year was 1995, and Internet Explorer 2 was about to release. But they also were missing a standout feature to commemorate their version change achievement.[^1] What was their solution? The <marquee> element!
[^1]: I have taken some liberties with the history here, as I was two years old at the time and not actively subscribed to any web standards mailing lists.
So we too can follow in the inimitable footsteps of the Internet Explorer team. We can add support for the <marquee> element in Phlex! We can become true internet explorers ourselves!
def view_template
  header do
    marquee { "Phlex 1.10 has arrived!" }
    time(datetime: "2024-04-01") { "April 1, 2024" }
  end

  main do
    # TODO: write announcement
  end
end

LGTM


Macbook

NOTE
Please verify that the base repository above has the intended destination!
Github by default opens Pull Requests against the parent of a forked repository.
If this is your personal fork and you didn't intend to open a PR for contribution
to the original project then adjust the base repository accordingly.

merge

_`
/`_

what is your purpose of this PR?


Import - Error at Line 18

mp3 files containing  ' in their name cause the xml file to be not correctly formatted and therefore not readable by FCPX. Removing the above mentioned character solves the problem.

mp3 files containing ' in their name cause the xml file to be not correctly formatted and therefore not readable by FCPX. Removing the above mentioned character solves the problem.

Thanks for your suggestion. The file name encoding problem has been ignored by me...
The bug will be fixed soon, thanks again 😄


Broken Circuit

Fixes #
Describe the changes you have made in this PR -
Screenshots of the changes (If any) -
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

@shubhankarsharma00 I think this might be a cause of projects getting corrupted (not sure).