Visual QA Coverage Pool -- Part: the Second

Starting the next round of review here that needed testnet KEEP. Let's get to it... 🚗  🌬
Browser: Chrome
Deposit Flow

REFRESH REQUIRED TO SHOW BALANCE
When making a deposit the dashboard doesn't return me the information until refresh. So I have deposited 3,000 KEEP but my balance is the same and no deposits to show. Upon refresh then the Balance shows. It shows a Success message, however. Is confusing:

SUCCESS MODAL IS MISSING
Post deposit, the dApp does not prompt me with a success modal in the end.

REWARDS RATE
For testing with users, showing a ">999%" rewards rate if that's not accurate would be misleading

INPUT FIELD
Unexpected quirk of numeric inputs: you can't backspace the 0 and have a cleared input field. Also won't let me insert either a . or a , - I would recommend allowing that. Though I do see that it auto-formats with the ,.

LOADING INDICATOR MISSING
When things are loading, we display 0 in some areas. We should present a "loading" spinner or indicator on TVL, Balance and Available to Withdraw instances so we don't scare our users that they have a zero balance or that the pool was liquidated while things are loading.

COV KEEP DOESN'T EQUAL KEEP
This may clear up later but currently, the value of KEEP is not close to the value of covKEEP. Right now it appears to be 0.

Withdraw Flow

MAX AMOUNT BUTTON DOESN'T WORK
Max amount button doesn't work in the withdrawal flow

.

UNCLEAR ERROR MESSAGE FOR INPUT
Getting an error message for input when there shouldn't be one. My entered amount matches the amount I have available to withdraw.

WITHDRAW FLOW DOESN'T WORK
Withdraw flow doesn't work. Unable to enter an amount of KEEP that works to allow you to proceed with withdraw flow.

Deposit Flow

WRONG AMOUNT OF KEEPS IN CONFIRMATION MODAL AFTER SUCCESFUL DEPOSIT

Look like the amount shown in the confirmation modal shows the amount of covKEEPs that user received instead of KEEPs that user deposited

Deposit flow - Success Modal - Chrome
After the Deposit the token amount is shown in covKEEP instead of KEEP. This needs to be changed.

Success Toast - let's make this auto-dismissable after 5 seconds

Withdraw flow - Chrome
In the withdraw card instead of showing the KEEP amount we are showing covKEEP. Please change to KEEP.

Withdraw Flow - Chrome
After the Withdraw action from the withdraw card is triggered in the dialog box the amount is shown correctly in KEEP.

Claiming tokens error - chrome
Even though the claiming tokens it's triggered immediately there is a token contract error in metamask which keeps me off from claiming the tokens, because in the end the transaction fails.

After this transaction fails and this is what we get in the console

Claim Tokens - Success Modal - Firefox, Chrome
Issue with the token amount - I have had 24,999 KEEP but it says 240,000,999 KEEP


Hi! The lib is giving some error ;) [interceptable-http.js:6Uncaught ReferenceError: __extends is not defined]

interceptable-http.js:6Uncaught ReferenceError: __extends is not defined
at interceptable-http.js:6
at Object. (interceptable-http.js:19)
at webpack_require (bootstrap 01c23fe…:52)
at Object. (main.bundle.js:53937)
at webpack_require (bootstrap 01c23fe…:52)
at Object. (main.bundle.js:74782)
at webpack_require (bootstrap 01c23fe…:52)
at Object. (main.bundle.js:74739)
at webpack_require (bootstrap 01c23fe…:52)
at Object. (main.bundle.js:53991)

Duplicate of #89


kubo: remove openssl from the build

Description of changes
We removed openssl support from go-libp2p and thus Kubo:

https://github.com/libp2p/go-libp2p/issues/1952

Now we exclusively on the options provided by the golang std librairy.
The openssl tag is now a noop, having it does not cause any harm except
making nixos install openssl for no reason while using kubo but I guess
many systems already build openssl but might as well not have it.
Things done

I do not have nix installed on my system, I caught this while investigating https://github.com/ipfs/kubo/issues/10056, I would hope such small change would be testable by CI.

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I do not have nix installed on my system, I caught this while investigating https://github.com/ipfs/kubo/issues/10056, I would hope such small change would be testable by CI.

Yes, it will. Thank you very much for your contribution and insight in the upstream project!


gRPC connection is closed right after a request is done

Bug description
gRPC connection is closed right after a request is done.
Below is the response got on client side:

Below is the request log from istio gateway:
{
"requested_server_name": "-",
"bytes_received": "12",
"istio_policy_status": "-",
"bytes_sent": "18",
"upstream_cluster": "outbound|80||k8s-demo-grpc.stage-c1.svc.cluster.local",
"downstream_remote_address": "<IP_ADDRESS>:37632",
"authority": "k8s-demo-grpc.internal.unicareer.com:80",
"path": "/greeter.Greeter/sayHello",
"protocol": "HTTP/1.1",
"upstream_service_time": "0",
"upstream_local_address": "-",
"duration": "1",
"downstream_local_address": "<IP_ADDRESS>:80",
"upstream_transport_failure_reason": "-",
"response_code": "200",
"user_agent": "grpc-node/1.24.2 grpc-c/8.0.0 (linux; chttp2; ganges)",
"response_flags": "-",
"start_time": "2020-01-02T10:55:56.172Z",
"method": "POST",
"request_id": "b327ccac-5643-4d20-9d44-ca07dfede9cd",
"upstream_host": "<IP_ADDRESS>:50051",
"x_forwarded_for": "<IP_ADDRESS>"
}

Expected behavior
The client can get data normally and connection keeps open.
Steps to reproduce the bug
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: gateway-isolated
  namespace: default
spec:
  selector:
    istio: ingressgateway
  servers:
    - hosts:
        - k8s-demo-grpc.internal.sample.com
      port:
        number: 80
        name: grpc
        protocol: GRPC

---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: k8s-demo-grpc-isolated
  namespace: stage-c1
spec:
  hosts:
    - k8s-demo-grpc.internal.sample.com
  gateways:
    - default/gateway-isolated
  http:
    - route:
        - destination:
            host: k8s-demo-grpc

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
~ istioctl version --remote
client version: 1.2.7
grafana version:
citadel version: 1.2.7
galley version: 1.2.7
ingressgateway version: 1.2.7
ingressgateway version: 1.2.7
pilot version: 1.2.7
pilot version: 1.2.7
pilot version: 1.2.7
pilot version: 1.2.7
pilot-gateway version:
policy version: 1.2.7
policy-gateway version:
sidecar-injector version: 1.2.7
telemetry version: 1.2.7
telemetry version: 1.2.7
telemetry version: 1.2.7
telemetry-gateway version:
kiali version:
prometheus version:

~ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T19:44:19Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.6-aliyun.1", GitCommit:"8cb561c", GitTreeState:"", BuildDate:"2019-05-23T11:28:17Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Aliyun ACK, Operator
Environment where bug was observed (cloud vendor, OS, etc)
Aliyun ACK, CentOS 7

Could anyone help on this issue?

Hi @xiaozhongliu sorry this didn't get much attention. Istio 1.2 is now out of support, https://istio.io/news/support/announcing-1.2-eol/, so we can only address issues from 1.5+. If this is still present, can you reopen with some steps on how we can reproduce this? I have not been able to. Thanks!

Hi John,
we are getting same issue with Istio 1.6 and an issue has been created for the same.
https://github.com/istio/istio/issues/26628

we are also getting similar issue. different than singhdeepu


Metal shader questions

I added both the alloy and metal shaders to my app, the former is working fine, but the latter is not behaving as expected. First, a check: should I read the docs as saying that either the ior array needs to be provided, OR, eta and k arrays both (looking at pathtracer/materials/Metal.cpp that seems to be the case)?
Secondly, I'm getting status messages ospray::pathtracer::Metal: found unused parameter 'eta' (and same for k). I think I'm committing where needed and set the arrays in the right way. The roughness value is coming through.
Here's the relevant code:
        material = ospNewMaterial(current_renderer_type.c_str(), "Metal");

        const float eta_gold[] = { 0.07, 0.37, 1.5 };
        const float k_gold[] = { 3.7, 2.3, 1.7 };

        OSPData eta_data = ospNewCopiedData(1, OSP_VEC3F, eta_gold);
        ospCommit(eta_data);
        OSPData k_data = ospNewCopiedData(1, OSP_VEC3F, k_gold);
        ospCommit(k_data);

        ospSetObject(material, "eta", eta_data);
        ospSetObject(material, "k", k_data);
        ospSetFloat(material, "roughness", settings.roughness());
        ospCommit(material);

        ospRelease(eta_data);
        ospRelease(k_data);

// For now, as I haven't looked into using shared data yet (and keeping it alive)
inline OSPData ospNewCopiedData(size_t numItems,
                          OSPDataType type,
                          const void *source)
{
    OSPData src = ospNewSharedData(source, type, numItems);
    OSPData dst = ospNewData(type, numItems);
    ospCopyData(src, dst);
    ospRelease(src);
    return dst;
}

Dang, it's easy to make these mistakes. I just submitted a pull request #373 to clearify that "unused" could actually also mean "wrong data type". That probably would have pointed me in the right direction here.


Atari training score stuck at approximately 10.

I have used tf==2.3.1 and I have used the ipynb file provided on Keras website but it is stuck at a score of 10.

Hi @anurag0singh ,
We are in process of going through backlogs.
Could you please point us to exact tutorial you are referring and attach a gist if the problem still persists?
Thanks!


Unable to create a physicsshape datablock from datablock editor.

Unable to create a physicsshape datablock from datablock editor.
<input> (0): preload failed for myTestPS: PhysicsShapeData::preload - No shape name defined..
tools/datablockEditor/datablockEditor.cs (716): Unable to find object: 'myTestPS' attempting to call function 'getId'
tools/datablockEditor/datablockEditor.cs (193): Unable to find object: '' attempting to call function 'getClassName'
tools/datablockEditor/datablockEditor.cs (201): Unable to find object: '' attempting to call function 'getId'
tools/datablockEditor/datablockEditor.cs (504): Unable to find object: '' attempting to call function 'getId'
Set::remove: Object "" does not exist in set

VS2015+Bullet+Windows7
tested in last commit 5fa8504568871e227c557a6a584f487b3bbce29f

Hi! besides rextimmy anyone review this PR #1690  ? :D This fix will allow to add a physics shape within a few clicks, I think was broken for some time now.


Extra YAML file incorrectly converted to HTML

I've .yaml file which I added as extra file, but rendered HTML is unreadable because it's not correctly rendered to HTML, for example newlines aren't converted to

Steps to reproduce

Create some .yaml file
Add it as extra
Generate documentation

Actual Output

html is

sudo: false
language: ruby
cache: bundler
rvm:

2.6.5
before_install: gem install bundler -v 2.0.2

Expected Output
yaml file rendered as HTML to look like
---
sudo: false
language: ruby
cache: bundler
rvm:
  - 2.6.5
before_install: gem install bundler -v 2.0.2

Environment details:

OS: Arch Linux
Ruby version (ruby -v): ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]
YARD version (yard -v): yard 0.9.22
Relevant software dependency/versions:

redcarpet (3.5.0)

YARD does not have built-in support for parsing and rendering YAML as HTML. By default, YARD only parses and renders Ruby code or a specific set of supported markup formats (markdown, rdoc, textile, etc).
That said, you can workaround this by adding #!pre to the top of your .yaml file (which should be YAML safe) which will force YARD to treat it as preformatted text rather than what it thinks is HTML.
One thing you can do is use {include:file:path/to/file.yaml} to embed it from another file in order to provide much needed context to the extra stuff you've added to the docs. This isn't strictly necessary but likely very helpful. You would still need the #!pre header using this method.
Another way to go about this would be to write a plugin or extension to register YAML as a markup format. If you're okay with just pre-formatting and not syntax highlighting the contents. Adding some kind of .rb file to your project with the following tiny snippet of code:
# place in a .rb file in your repo

YARD::Templates::Helpers::MarkupHelper::MARKUP_EXTENSIONS[:yaml] = ['yaml', 'yml']
YARD::Templates::Helpers::MarkupHelper::MARKUP_PROVIDERS[:yaml] = []

module YARD::Templates::Helpers::HtmlHelper
  alias html_markup_yaml html_markup_pre
end

Run this with yard -e path/to/ext.rb or add -e path/to/ext.rb to your .yardopts -- note however this method won't work on rubydoc.info since it modifies template logic.
Given how small this change is, you could also reformat the above code as a PR to this project and it would more than likely get accepted. You can take a look at markup_helper.rb to get started there.
Hope that helps!

Everything you said makes sense but I don't think that's best solution. It's unreasonable to expect that there will be plugin for every imaginable file format. I would say default for unrecognized file format should be that it's always outputted as is and thus HTML escaped. I just tested that there's same issue with XML, those tags are processed by browser even when they shouldn't be but should just be displayed.
Because implementing such default would be backward incompatible change, it could be under some flag to enable this behavior.

outputted as is

Then there's the question of whether a mono-spaced font should be used.  Given that YARD is often run in a script, it might be simplest to create md files from the YAML, XML, or JSON files...

It's unreasonable to expect that there will be plugin for every imaginable file format.

Plugins are not limited to small snippets. You could generalize the above or even write a plugin to treat all unrecognized formats as preformatted text if you truly think this is useful.
I think this ultimately comes down to how common the behavior is. Attaching an XML or YAML file directly as an extra file is relatively uncommon because doing so lacks prose-based context that you would expect to get alongside the file. This is why as pointed out above you should typically embed a file via {include:file:...} or do what @MSP-Greg said above and convert the files to md in order to attach that context there.
Fundamentally, YARD's goal is to attach context to source code (in the form of documentation) rather than simply displaying source code. If your use case is to show YAML/XML files in your repository for the purpose of code browsing, you may even have better luck linking to your source browser (GitHub?) which likely is a much better place to view those files because of the code highlighting, git blame, issue tracking, etc.
Hope that helps!

You could generalize the above and allow it to be customized to a set of user declared extensions or even write a plugin to treat all unrecognized formats as preformatted text if you truly think this is useful.

How it's implemented doesn't matter (if it's plugin or not), but yeah this is what I think would be useful and required.
My use case is that I've software which can be configured with .yaml (could be .xml or .ini). So I have example files which can be used as is or customized but I want to include them with documentation to be used as reference.  Creating separate documentation file for each seems overkill (imagine if I have 10 different examples). So I would want to just link them from documentation but because I want them to be together with documentation I don't want to link to external website. And because I'm lazy I rather just add them to extra files than embed each one inside.
I don't think this use case is that rare/unusual/special.

I don't think this use case is that rare/unusual/special.

This is fairly quantifiable. Going down the list of docs for the most popular gems, I haven't yet seen a project using extra files in the way you're describing in a pseudo-random sampling (ignoring projects that would obviously not require config) of the first 10 pages of results. I have however seen plenty of these projects describing their configuration files / syntax in README files, or by pointing to example directories in source control (e.g. httparty).
If you can show where this is commonly used in a place we might have missed, that can help YARD make better choices going forward.
That said, all information I've gathered (maybe 1-2 feature requests + actual doc project usage) since we started this project + running rubydoc.info leads me to believe that most people do in fact choose to embed contents into READMEs or other extra files with extra prose context explaining the purpose of including that configuration file.
I still highly recommend the route recommended above, as dropping a .yaml file into YARD's File List without context will more than likely be confusing to your users even if the files themselves are well annotated. Some questions I would ask as a user would be: why is this file highlighted above others? how do I use this file? what is the underlying specification for this file's format? where do I put this file? All of these answers are more than likely missing unless you're embedding these docs directly into the YAML file, at which point YARD's purpose of abstracting documentation away from actual source becomes very muddled. At the end of the day you can choose to structure your docs the way you best see it, but I would suggest looking at how other projects handle this problem as well as considering whether or not you need dedicated example .yaml files on disk as opposed to embedded in documentation.

This is fairly quantifiable. Going down the list of docs for the most popular gems, I haven't yet seen a project using extra files in the way you're describing in a pseudo-random sampling (ignoring projects that would obviously not require config) of the first 10 pages of results. I have however seen plenty of these projects describing their configuration files / syntax in README files, or by pointing to example directories in source control (e.g. httparty).

This isn't correct approach, you can't determine if feature would be useful based on current status quo, because I don't think anyone has implemented it for you to compare usage with. It's clearly not possible to do it with YARD so if you're using YARD, you can't currently do it this way even if you wanted. You could only argue that because no one has implemented it means it's not necessary/useful, but I would also say that's wrong way to think because there can be many different reasons why it's not implemented even if there would be many people who would want that.

I still highly recommend the route recommended above, as dropping a .yaml file into YARD's File List without context will more than likely be confusing to your users even if the files themselves are well annotated. Some questions I would ask as a user would be: why is this file highlighted above others? how do I use this file? what is the underlying specification for this file's format? where do I put this file? All of these answers are more than likely missing unless you're embedding these docs directly into the YAML file, at which point YARD's purpose of abstracting documentation away from actual source becomes very muddled.

That's not how I am doing it, I have a README which explains config file format/usage/options and so on, and there I have a sentence saying "take a look at provided config.yaml  as example" where I want this to be a link to that file but together with documentation not link to separate website. For example if you don't have internet connection and are browsing documentation locally. Embedding that file into README isn't good because it could be big and would clutter it too much.
Anyway I think this discussion is a waste of time for both of us. It seems you're not really against implementation of such feature and I see it as very useful. Also I think (of course just guessing) that other people might find it useful too. So the only thing left here is for someone to implement this feature and because it seems no one else besides me is really interested in it that means I'm probably only one who has enough willingness to implement it.

It's clearly not possible to do it with YARD so if you're using YARD, you can't currently do it this way even if you wanted.

This is not correct. I've demonstrated multiple methods in my very first response as to how you can workaround this to achieve the result you want (#!pre or custom plugin / extension) using standard YARD. The fact is that no projects that I can find are attempting to document configuration files in the way you're describing either with these possible workarounds, or via any other plugin / feature requests besides this one. Keep in mind also that many of the projects I referenced actually use Ruby configuration DSL formats (think Puppet, Bundler, Fastlane, etc), i.e., they are Ruby files, which YARD does support, and so if doc authors intended to add these as extra files they could easily do so. Instead, projects almost exclusively use the README file and embed alongside context, and, if they are truly just linking to source, they do so via external links to real source browsing tools.
Basically, if this were indeed a common use case, you would see that show up in workarounds or separate tooling. YARD has a pretty robust plugin ecosystem for many types of use cases but none for this one. Other tools like RDoc also have some ability to do this (see the old 4-frame templates for this), but you still don't see this used by users of RDoc either. Your hypothesis is that this is common, but I cannot find any examples. If your hypothesis is that this should be common, that's a very different discussion, one you can explore by creating such a plugin, presenting it to the community and seeing if it catches on.

That's not how I am doing it, I have a README which explains config file format/usage/options and so on, and there I have a sentence saying "take a look at provided config.yaml as example" where I want this to be a link to that file but together with documentation not link to separate website. For example if you don't have internet connection and are browsing documentation locally.

There are at least a few ways to make external file links work with YARD in a way that is both safe for online and offline viewing. One is to create a template customization to add extra JS to modify link locations in offline/online modes. Something like the following pseudocode might work for you:
if (window.location.protocol === 'file:') { // browsing locally
  findAllLinksWithGitHubSrc().forEach((link) {
    link.href = link.href.replace(/.*github\.com\/user\/project\//, 'rel-path/to/local-src');
  });
}

Another less intrusive but also less fancy way would be to use the --asset option in YARD to copy relevant source files as assets into the produced HTML directory (e.g. --asset test.yaml:src_test.yaml makes a file src_test.yaml available in the docs/ root directory). This doesn't link them up in any visible way in your template, but allows you to generate  links to the raw contents. Obviously this provides no type of source browsing and depending on the file type may not be marked up correctly by your browser either, though this seems to work for YAML files.
A hybrid approach could be to some kind of source browsing JavaScript library that you could add to the template that could load these assets via XHR and display them alongside docs and syntax highlight them. Or, alternatively, using the above link swapping code alongside --asset to point to the local assets when browsing locally (if you can't guarantee the source path locations).
Finally, repeating the initial suggestion by @MSP-Greg to add a pre-processing step to your rake tasks that generate documentation. You could use pandoc or some other library to process your extra files into highlighted HTML and add them as assets that you can link to, or alternatively just to markdown which you could annotate with such context. Automating this for gem releases would be extremely minimal overhead and would support all variants of YARD browsing including local access and rubydoc.info.
I am going to mark this issue as closed since we don't typically keep feature requests open. If you're interested, I would still look at a PR to address this for YAML files as described initially, otherwise I would recommend going down the plugin route-- if the plugin is indeed popular we can always revisit for its inclusion into core.


Investigate LevelDB shutdown failures on Travis CI

mostly causes it tests to fail such as this one.
error message is pthread lock: invalid argument from native code

pthread lock: Invalid argument
Exception in thread "Thread-161" Exception in thread "Thread-165" java.io.EOFException
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2601)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
	at sbt.React.react(ForkTests.scala:114)
	at sbt.ForkTests$$anonfun$mainTestTask$1$Acceptor$2$.run(ForkTests.scala:74)
	at java.lang.Thread.run(Thread.java:744)
java.io.EOFException
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2601)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
	at org.scalatest.tools.Framework$ScalaTestRunner$Skeleton$1$React.react(Framework.scala:906)
	at org.scalatest.tools.Framework$ScalaTestRunner$Skeleton$1.run(Framework.scala:895)
	at java.lang.Thread.run(Thread.java:744)

The problem is related to iterators that are still used by the read dispatcher. Tracking these iterators and closing them on event log shutdown however causes:

libc++abi.dylib: Pure virtual function called!
Exception in thread "Thread-77" java.io.EOFException
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2601)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
	at sbt.React.react(ForkTests.scala:114)
	at sbt.ForkTests$$anonfun$mainTestTask$1$Acceptor$2$.run(ForkTests.scala:74)
	at java.lang.Thread.run(Thread.java:744)
Exception in thread "Thread-81" java.io.EOFException
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2601)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
	at org.scalatest.tools.Framework$ScalaTestRunner$Skeleton$1$React.react(Framework.scala:906)
	at org.scalatest.tools.Framework$ScalaTestRunner$Skeleton$1.run(Framework.scala:895)
	at java.lang.Thread.run(Thread.java:744)


Add addSlicingPattern option

Fix bug with nested object lists

@ErikWittern I adapted the following specification. Does this change your opinion?

See #155


Fix focus ring/keyboard interaction on fullscreen button

Currently the fullscreen button has no focus ring. I can activate it with space in Chrome, but not Safari.

As part of this, I'm going to sort out all our focus styles (aside from the game board, that comes later).
I'm going to use https://github.com/WICG/focus-visible/blob/master/src/focus-visible.js, but probably adjust it so it can be lazy-loaded.

cc @robdodson 🎉

oh nice! cc @alice
let us know if you hit any bumps and we can help sort them.

😁


Ramda Hard Dependency

Sanctuary is very cool.
However, what if a user wants to use sanctuary, but does not want the hard dependency on Ramda?
Is there a plan at some point to make this lib standalone?

Initially Sanctuary was a stand-alone library. Ramda was added as a dependency in #21. The reasons given in that pull request's description remain valid.
Although I'm not opposed to duplicating some of Ramda's internals, there are two features I'm unwilling to relinquish:

Placeholder support
Since Sanctuary functions are curried by R.curry they support the R.__ placeholder value. The current implementation of R.curry relies on an identity check to determine whether any given argument is the placeholder value.
Sanctuary could duplicate curryN.js and replace the identity check with an equivalence check (the current value of R.__ is {ramda: 'placeholder'}). In ramda/ramda#1052 @paldepind proposed an approach which would allow libraries to respect one another's placeholder values in a more general manner.

Recursive string representations
The fact that S.match(/(good)?bye/, 'bye').toString() evaluates to 'Just([Just("bye"), Nothing()])' is extremely useful. Without a useful toString method one must resort to logging the value itself and making sense of the output ({ value: [ { value: 'bye' }, {} ] } in this case).
Duplicating _toString.js doesn't seem a good option, but if Ramda were to provide a ramda-tostring package Sanctuary could depend on it rather than ramda.

I'm curious that you're interested in using Sanctuary without Ramda. Are you writing front-end JavaScript and seeking to keep the file size of your dependencies under control, or are you using another library such as Underscore or lodash?

but if Ramda were to provide a ramda-tostring package Sanctuary could depend on it rather than ramda.

What about doing something like this?

@paldepind, that's a good option for those using Browserify, CommonJS Everywhere, or a similar tool. :)

And a browser build could be made as well. If you are not using Ramda then including the Ramda functions inside the built is what one wants?

And a browser build could be made as well.

That's a good idea, if we decide to go down this path.

Maybe it's because I only work server-side but I don't really have an issue with a dependency on Ramda, it seems strange to me to be be duplicating work that's already been done there. And it seems like a lot of effort to modularise the dependencies down to the function level when Ramda minified is only 32kb.

@davidchambers I am writing both server and client side JS, so file size is somewhat of a concern.
More than that though, I work in an environment that is very sensitive to dependencies. Any new deps are heavily scrutinized.
I am in the process of removing lodash in favor of an in house functional lib. As such I was interested in your thoughts of making this dep free as it would be one less dependency I would not need to include in my project.
In the end though, I think I am going to use a safe check function that will return a default result for arguments that don't meet it's criteria.
Thanks for your consideration. I'm not sure if other's want this for different reasons but if everyone is satisfied feel free to close.

ramda/ramda#1156 would make it possible for Sanctuary to provide its own :curry: function which respects R.__ and other compatible placeholders. That said, Sanctuary makes heavy use of Ramda internally—and the source code is clearer as a result—so I don't foresee removing the Ramda dependency in the near future.


Showing Recent Messages Command PhaseScriptExecution failed with a nonzero exit code

Description
I have been getting this error on my Xcode 14.0.1 I have tried updating pods, integrating pods and deintegrating multiple times but still getting the same error again and again
Steps to reproduce
When I create build of my project from xcode it gives me this error
I was able to solve this 2 months ago but now its like never going error
React Native Version
0.73
Affected Platforms
Runtime - iOS, Build - MacOS
Output of npx react-native info
warn Package react-native-sqlite-storage contains invalid configuration: "dependency.platforms.ios.project" is not allowed. Please verify it's properly linked using "react-native config" command and contact the package maintainers about this.
info Fetching system and libraries information...
System:
    OS: macOS 12.6
    CPU: (8) x64 Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz
    Memory: 1.37 GB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 21.5.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 9.8.1 - ~/Desktop/ArmFitness(No Ads)/ArmFitness_IOS/node_modules/.bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.15.2 - /Users/zeeshankhan/.rvm/gems/ruby-2.7.5/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
  Languages:
    Java: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: ^0.71.6 => 0.71.6
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found
(node:52095) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
zeeshankhan@192 ArmFitness_IOS %

Stacktrace or Logs
Showing Recent Messages
Command PhaseScriptExecution failed with a nonzero exit code

Reproducer
nop
Screenshots and Videos

Without a repro we can't help.
Also please check other existing issues before opening a new one:
https://github.com/facebook/react-native/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+"Command+PhaseScriptExecution+failed+with+a+nonzero+exit+code"


Support for additional Homekit Accessories

Home Assistant release with the issue:
0.77.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
Homekit
Description of problem:
There are some difficulties on Homekit setup for some accessories. The Nest protect for example, reports Carbon Monoxide, but HASS supports only Carbon Dioxide. I've checked Homekit documentation and both seem identical, so should be relatively ease to implement?
I am trying to currently create a binary sensor and expose this as a CO2 sensor instead, but then there is the second problem: Template Binary sensor won't accept co2 or co as device classes, and that's the only way Homekit component accepts it. Could we accept also the string on the entity_id ?

It looks like you are looking for something that is yet to be implemented.  Please do not use the github issues to file a feature request, they need to go in the appropriate place in the forums.
https://community.home-assistant.io/c/feature-requests


is there a method to know

the message input has no trigger defined, and will use the default ones:

I'm not sure I understand you fully.
Please go on.
That is interesting. Please continue.
Tell me more about that.
Does talking about this bother you?

I just want to know in the code once the input will be replied with the 'default' ones.
thanks.

The * trigger has the lowest matching priority, so it only matches the user's message when there was no better trigger that matched it. The bot sorts all the triggers internally (regardless of their location in the source .rive files) in a "most specific first" ordering, where longer/more specific triggers are tested first.
For example if you started with this:
+ hello
- Hello human!

+ *
- I didn't understand that.

A user saying "hi" instead of "hello" would get the "I didn't understand that." reply. But as soon as you make it so a trigger would match "hi":
+ (hello|hi)
- Hello human!

- *
- I didn't understand that.

Now "hi" would get the "Hello human!" response.

hi kirsle, thanks for the comment!
sorry i didnot make it clear.
what i want to do is, i want to check before getting the reply whether the bot will tigger the * trigger.
i.e.
msg = getUserMsg()
has_meaningful_reply = checkTrigger(msg)
if has_meaningful_reply:
reply = chatbot.reply(msg)
else:
#do something else here
thanks again for you quick response.

I have two ideas:
You can get the reply normally, and then check the last_match() function to see if they had matched the * trigger. This should probably be okay if your bot doesn't change any user variables in the * trigger.
reply = bot.reply(username, message)
if bot.last_match(username) != '*':
    send_reply(username, reply)
else:
    # do something else here

Or, if your bot might change user variables and you want to avoid the side effects of variables getting changed, you can do a "test flight" reply using the freeze_uservars() and thaw_uservars()
# Snapshot the user's variables
bot.freeze_uservars(username)

# Test the reply
reply = bot.reply(username, message)
is_wildcard = bot.last_match(username) == '*'

# Roll the user vars back so it's as if the reply() never happened.
bot.thaw_uservars(username)

# now you have is_wildcard bool
if is_wildcard:
    do_something_else()
else:
    reply = bot.reply(username, message)  # for real this time
    send_reply(username, reply)

hi kirsle,
got it.
many thanks for the details.


RuntimeError: Maximum number of steps reached before convergence for ignition case 0

Hi, I was trying to reduce a big model
model: 9.2blend2.cti
targets:
  - C7H10(705)
  - C7H16(37)
  - O2(2)(38)
retained-species:
  - N2(35)
method: DRGEP
error: 10.0
sensitivity-analysis: False
autoignition-conditions:
  - kind: constant volume
    pressure: 1.0
    temperature: 1000.0
    fuel:
      C7H10(705): 1.0
      C7H16(37): 1.0
    oxidizer:
      O2(2)(38): 1.0
      N2(35): 8
    equivalence-ratio: 1.0

  - kind: constant volume
    pressure: 1.0
    temperature: 1200.0
    fuel:
      C7H10(705): 1.0
      C7H16(37): 1.0
    oxidizer:
      O2(2)(38): 1.0
      N2(35): 8
    equivalence-ratio: 0.5

and got the Runtime error:
Traceback (most recent call last):
  File "/home/shenghuiqin/anaconda2/envs/spam/bin/pymars", line 12, in <module>
    sys.exit(main())
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/__main__.py", line 10, in main
    pymars(args)
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/pymars.py", line 319, in pymars
    path=args.path, num_threads=args.num_threads
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/pymars.py", line 186, in main
    threshold_upper=upper_threshold, num_threads=num_threads, path=path
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/drgep.py", line 387, in run_drgep
    model_file, ignition_conditions, phase_name=phase_name, num_threads=num_threads, path=path
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/sampling.py", line 305, in sample
    results.append(simulation_worker(job))
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/sampling.py", line 64, in simulation_worker
    sim.run_case(stop_at_ignition)
  File "/home/shenghuiqin/anaconda2/envs/spam/lib/python3.7/site-packages/pymars/simulation.py", line 216, in run_case
    'Maximum number of steps reached before '
RuntimeError: Maximum number of steps reached before convergence for ignition case 0

need help.

also,  I don't know how to understand this,
species with the same mole fraction but different phi value?
(screenshot from pyMARS usage documentation)
https://niemeyer-research-group.github.io/pyMARS/usage.html

another question is when creating a YAML file, how many auto-ignition conditions are appropriate?
the example file uses two (1atm phi=1 and 1000K; 1atm phi=0.5 and 1200K)(see screenshot above),
I want to use the reduced model to simulate the corresponding exp condition of T range from 650 -1500K, P range from 10--40 bar. How to distribute autoignition-conditions? will keep P constant, every 100K do a simulation from 650 make sense?

Hello,

It looks like your run time error occurs because your model did not ignite under the first set of initial conditions in the auto-ignition simulation in the given number of steps.  Maybe the error message could be easier to understand.

The equivalence ratio and mole fractions given are passed to the set_equivalence_ratio function from Cantera here.  See the documentation here.

You can certainly set up your initial conditions like this!  Every 100K sounds like a reasonable step in temperature.  The trade-offs you need to consider are more initial conditions mean that the reduction will take longer and will be less effective, but the benefit is that the error in the reduced model will be consistent across a wider variety of conditions.

@shenghuiqin to clarify about the mole fraction/equivalence ratio, the values in the fuel and oxidizer fields are the mole fractions in the fuel/oxidizer mixture. (So, in the example given, the oxidizer is the typical representation for air of 1.0 O2 + 3.76 N2.) Then, as @xMestas mentioned, the equivalence ratio specified will be used to find the appropriate ratio of fuel and oxidizer.
Alternatively, you can leave out equivalence-ratio, fuel, and oxidizer and specify the molar amounts of each reactant:
reactants:
  CH4: 1.0
  O2: 2.0
  N2: 7.52

thank you both!
I changed the simulation condition which I can get IDT using cantera,
model: 9.2blend2.cti
targets:
  - C7H10(705)
  - C7H16(37)
  - O2(2)(38)
retained-species:
  - N2(35)
method: DRGEP
error: 10.0
sensitivity-analysis: False
autoignition-conditions:
  - kind: constant volume
    pressure: 20.0
    temperature: 800.0
    reactants:
      C7H10(705): 1
      C7H16(37): 1
      O2(2)(38): 21
      N2(35): 60

but on pyMARS I still get the RuntimeError, I tried on several T and P, still did not work.
what else could be the reason to have this error?

@shenghuiqin is the ignition delay time you got with Cantera quite long? It may be that the low temperature and extremely lean mixture takes too long to ignite for the default pyMARS parameters.
As mentioned in the Usage docs, you can override these defaults with either a maximum integration time (using an end-time: field) or a larger number of steps (max-steps:, beyond the default of 10000). This would be needed for each autoignition condition with this issue.

yeah, really loong on cantera, that's why I want to reduce it.
thank you, I will try that again

It works! setting   max-steps: 18000


Migration not creating with Startup project if an UWP project already exists

Issue: If you already have an existing UWP project in the solution and create a dummy startup project to ensure the migrations tools work, you will get a referencing error where it tells you that the dummy startup project should reference the UWP project too besides the Model project.
Solution: Remove the UWP project from the solution (you don't need to remove the entire project folder). Once you've done that the migration tooling now works. Once you get the migrations add back the UWP project to the solution.
Additional Info: This is the error you get when the UWP project isn't referenced but exists in the solution: Could not load assembly 'ProjectName.UWP'. Ensure it is referenced by the startup project 'ProjectName.Startup'.

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

ID: 439f9dd7-6fff-f3af-15a3-c4f407e2c041
Version Independent ID: 2779bb58-f0af-c9ee-cf40-50e24371a7fc
Content: Getting Started on UWP - New Database - EF Core
Content Source: entity-framework/core/get-started/uwp/getting-started.md
Product: entity-framework
GitHub Login: @rowanmiller
Microsoft Alias: divega

Duplicate of #481


CodeView debug info support for Windows

It looks like cg_clif doesn't support debug info on Windows. It would be nice if we could do that!
Some pdb files are generated but I'm not sure what's in them (see: https://github.com/bjorn3/rustc_codegen_cranelift/issues/1249#issuecomment-1262034841).
I've been looking into this mostly because I have no idea how any of this works. I found two crates that seem to produce pdb files (bao-pdb, pdb_wrapper), but I'm not sure how complete they are or if they work for our use case.
A more interesting approach is what LLVM does for generating CodeView. LLVM apparently only emits CodeView line tables, and DWARF debug info (which we already know how to do!)  And lets link.exe convert it into a PDB file, this seems like a much easier solution and maybe implementing only that part of CodeView would be easier.
Edit: Re-reading the rust issue, it looks like this doesn't get us variable and type information, only line information.
Edit 2: That information is also out of date, LLVM now has full CodeView support, but its good to know that that's how they started out.
Additional links:

Rust thread about windows debug info
Rust PR that enables windows debug info
Microsoft has published some documentation regarding pdb's
Clang MSVC compatibility
CodeView In LLVM (pdf)

I found two crates that seem to produce pdb files (bao-pdb, pdb_wrapper), but I'm not sure how complete they are or if they work for our use case.

They are both licensed under Unlicense and from the same author. I'm not sure if Unlicense is allowed.

Edit: Re-reading the rust issue, it looks like this https://github.com/rust-lang/rust/issues/19533#issuecomment-115827953, only line information.

cg_clif already only supports line information anyway. I couldn't quite get the Cranelift integration for value tracking working reliably last time I tried.


QPID-8563: [Broker-J] Purge all queues

Hi Marek,
could you please add unit tests regarding purging all queues?


Add Chapter 6 - Closing

Fade to black and back in on start using panorama overlay and css animation
Spawn some NPCs while faded out
Make sure Slacks and SUNSfan are invisible in the start and become visible while faded out

TODO

Show UI panels when you walk close to npcs (probably using part of #236)

I think we can get this in now, as there is a lot to add to it later anyway as we are getting the audio files in.

Haven't tested it, but the code looks fine, no weird stuff there.


Explorer Drawer

[ ] #86
[ ] #85
[ ] #87
[ ] #88

A- this is a set of tool that will be used to control the Explorer's drawer, for example sorting, filtering or searching the notebooks it also contain an control to pin open or closed the drawer
B- this is the library title and should be limited to 2 lines of text the ":" total pole with call up a context menu to rename (and possibly delete depending on admin)
C- I an in focus accordion layer, all layer will have an Icon (editable in the future) a notebook name, and the ":" icon (see I)to call up a context menu to rename, delete or other tool tdb
D -is the Tree view within the active accordion TDB if multiple accordion layers can be open at one (note if multiple can be open at one we will need a "close all " functionality down the line, more details of the tree view to come
E- is a Add notebook icon that is pinned to the the bottom of an/the active/open layer this is to help the user in the case that the "G" icon has fallen off the screen, pressing this will add a notebook directly below the active layer
F - is an out of focus, or inactive layer of the accordion
G- is a add notebook icon that is pinned to the bottom of the the accordion at all times and add a new notebook to the bottom og the accordion
H- the "<" button will collapse the Explorer drawer (design are available) when the drawer is closed the button will change orientation to ">" point out.
J & K see documentation for the tree (see D)


Add support to opt-in for using ENI's primary IP for allocations

Recently ENI's primary IP has been removed from pool of IPs available
for allocations on the node. This has been done to make sure SNAT works
correctly when kube-proxy is used. See https://github.com/cilium/cilium/pull/15453/commits/bc0a748021f5234880fdede51cf04e4fe6d1833b
for more details. However this can lead to IP wastage in large clusters.
The SNAT case does not apply when cilium runs in kube proxy replacement
mode.
This commit adds a new flag called --aws-use-primary-address to the
operator and new field in ciliumnode CRD ENI spec called
UseENIPrimaryAddress to opt in for using the ENI primary address. Azure
IPAM mode already has a flag like this.
Signed-off-by: Hemanth Malla<EMAIL_ADDRESS>

/test

/test

/test

Marking as ready to merge since we have reviews from ipam and kubernetes. GKE failures are not relevant.


Prl 637 manage documents

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-637
Change description
Manage documents
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Closing temporarily as we are seeing space issues in preview, it will be reopened to merge to master

closing the PR and creating a new one.

https://github.com/hmcts/prl-ccd-definitions/pull/126 new one


Executors and partly reenable futures crate

This needs careful review. I'm not entirely sure what I did ^^' All I can say is that it builds now and some of the tests run.
Notes:

futures-core subcrate does not yet reexport from core
executor.spawn_obj(Box::new(future).into()) looks ugly ^^' I think we should introduce an IntoTaskObj trait. Unless there's going to be a simpler API layered on top of course.
The doc tests seem to require #![feature(arbitrary_self_types)]. Can this be done? Didn't seem to work for me. Maybe I just did it the wrong way.
Various places require Executor to be Sized. Should it become the default, so that we don't need to type it everywhere?
The Rust compiler is genius. It reports new errors blazing fast and the error messages are extremely helpful
[x] The Task structs should probably be renamed to something like TaskContainer { task_obj, ... }.

Because this PR is so big and requires careful vetting, https://github.com/rust-lang-nursery/futures-rs/pull/1034 should be reviewed an merged first. I will then rebase on top of it once it landed.

In this recent commit I renamed Task to TaskContainer.  Previously we had two things called task:

TaskObj: The root future wrapped in a custom trait object
Task: The environment { task, exec, wake_handle } that contains it and other stuff

Calling both things "task" would be too confusing.
Alternative to what I implemented:

Rename TaskObj to something else. It's only a stopgap solutions until dyn can be passed by value after all. One possible good name would be RootFutureObj
Rename TaskContainer back to Task

I quite like the alternative. What do you think?

Okay here are some updated thoughts on this:
What about we rename TaskObj to TaskFutureObj:

"Task" signifies that it's for a task and should have Output = ()
"Future" signifies that it can be polled. TaskFutureObj should therefore also implement Future to make this perfectly clear: Currently it just implements a method call poll_task() (which I already suggested to rename to poll). But we should go the extra mile and make it a real future type. Because it is Unpin executors will be able to call poll_unpin
"Obj" signifies that it's a custom trait object
The trait will be called UnsafeTaskFuture

@cramertj
@aturon

executor.span_obj(Box::new(future).into()) looks ugly ^^' I think we should introduce an IntoTaskObj trait. Unless there's going to be a simpler API layered on top of course.

The plan was originally to add a method to Context that would take a generic future, box it, and spawn it. However, that impl needs std and Context is defined in core, so I think we should add it via an extension trait here instead.

Various places require Executor to be Sized. Should it become the default, so that we don't need to type it everywhere?

No-- the executor inside of task::Context is &mut dyn Executor.

I now think we should stick with calling the top level future "task".

I rebased and updated it

I've split FuturesUnordered into multiple files. Whenever a file is large I spend most of my time scrolling and trying to find stuff instead of getting things done ^^'

@cramertj To make reviewing easier, look at the "Future + !Unpin support for FuturesUnordered" commit directly. I split the file in the preceding commit. This PR seems a bit bigger than it really is (it's still big of course)

@MajorBreakfast Looks great! Thanks for being so patient with all the changes.

🎉


osmosisd start

Background
We can't make enough RPC nodes.  It is impossible.  Plus, we want to make "the signal" unstoppable.  This means that eventually, Osmosis and its related DAOs need to ship onto user machines, as desktop apps.
Currently those of us on the "technical side" of the house have all shared the experience of guiding someone through hunting down genesis and seeds.
In fact, many of us have spent days of our lives doing the same.  This is counter-productive and bad.
Suggested Design
Osmosis should download its own genesis state by default, and state sync by default, using addresses from the cosmos chain registry. Here's the code:
import "github.com/notional-labs/get"

get.Get(filepath, cid)

Acceptance Criteria

State sync needs to work
Users should approve of downloading genesis state as a part of the chain binary
It should work seamlessly, hundreds of times
osmosisd init should no longer be necessary except for validators and others doing "fancy things" with their nodes
Need to communicate with Keplr team about wallet security in the context of an electron app.
Teams developing applications on Osmosis should be contacted and alerted to the infrastructure-free deployment option

why isn't get.osmosis.zone the goal we target here?

...where get.osmosis.zone gives you a .dmg ;)

Unfortunately, this is blocked by this:
https://github.com/cosmos/cosmos-sdk/pull/11414


fixed style prop in Table

We will revert table style prop instead of wrapping it in unnecessary div.


Message content shows through in compose area

Reported by @zbenjamin, who's been seeing this on 25.0.114 and for a while before that (presumably 24.0.113, which was the latest beta for some time.)

That's on an iPhone 7. I was also able to reproduce it, on an iPhone 7 in 25.2.116:

It doesn't always happen. Zev suggested

I think it happens when you open the compose box while messages are still loading

I found that hard to pull off at first, and as I played around with narrowing to various streams and opening the compose box I didn't see it for a while. I first reproed it after following a link in a message, navigating back from the resulting browser view, and quickly opening the compose box again.
Then once it had started happening, it seemed to persist indefinitely (at least in a given narrow): even though it was a conversation where we had all the messages already, if I opened the compose box, I got this symptom every time.
Another time I saw it: I'd followed a link in a message; navigated back from the resulting browser view; the message list was showing the loading animation; I opened the compose box; and the symptom appeared.

@jainkuniya did some investigation described in #3536, and it looks like this is a bug in the version of react-native-webview we use (which was spun out of React Native itself.)
Later versions of react-native-webview seem to have fixed the bug, so we should upgrade. Filed that specific task as #3550 .

(Didn't mean to close this with that commit -- it's only "expected to fix" this issue.)
@jainkuniya , were you able to find a way to reproduce this reliably? Would you try reproducing it now that #3550 is fixed, to confirm whether this is fixed?

yup, it got fixed .

Thanks @jainkuniya for confirming, and for the fix!
@zbenjamin This fix was included in v25.8.122, which went out this morning to the iOS beta. If you see it after upgrading, please let us know!


#41 - Filter team endpoint based on user roles

Closes #41
This PR adds filtering on the /api/v1/teams endpoint to only show the teams and environments to which a user belongs.  The behavior is now this:

If the user is a superuser, all teams and environments will be shown.
If the user has a role on a team, that team and all of its environments will be shown.
If the user has a role on an environment, that environment's team will shown, but only the environments that the user has a role on will be shown for that team.

There's also a fix to the unique constraint on user roles.  The intent was that a user should have only a single role assigned per team or environment.  That is now properly enforced.

Two things I noticed, the error message when the team/user/role constraint is violated in the admin could be worded better, not sure if that's an easy thing to do or if it's something to be addressed later for an admin ui. Also I wanted to switch my default team environment and had to unset the default for the team so it didn't have one, then set the new one. We probably need add an operation on the Team in the future to allow this change and ensure consistency.

I agree with both of these observations.

I don't expect the django admin UI to be a thing that's user facing.  In my experience on past projects, you run into the limits of what the admin UI does out of the box pretty quickly.  Especially as your models and related functionality start to grow in complexity.  You can actually customize the admin UI quite a lot, but the amount of effort to do that is not worlds apart from what it would take to just build some administrative pages into your actual application UI in many cases.  So for now I'm just viewing the admin UI as a convenience tool for us to setup data in our dev environments.

Yes, there needs to be some helper for setting the default environment.  I recognized this too, but I punted on implementing such a thing for now because there's a few ways to go about it and I figure which route to go might be more obvious once we have a context where it'll actually be used.


Added the ability to run image optimizations in a background thread.

I've added a new setting in the Settings window for running image optimizations in the background. If disabled, there's basically no changes, other than some failsafe code in the OptimizeGame function which makes sure the Game being worked on is the same as the one currently in the item database.
If the background option is enabled, then a ConcurrentQueue is used to handle the optimization requests in a FIFO order. It has a backing file which it uses to make sure that it continues optimizing even if Playnite gets closed and reopened.
There's also a new Main Menu option added if optimization is currently happening, giving users the ability to cancel it.

That is a leftover comment I forgot to strip. No, there's nothing too on
that line
On Wed, 21 Feb 2024, 08:19 UrbanCMC, @.***> wrote:

@.**** commented on this pull request.
In src/MetadataImageOptimizer/MetadataImageOptimizer.cs
https://github.com/UrbanCMC/PlayniteExtensions/pull/7#discussion_r1497076066
:

@@ -121,26 +184,43 @@ private void OptimizeGame(ItemUpdateEvent change, MetadataImageOptimizerSe
var coverChanged = optimizerSettings.AlwaysOptimizeOnSave || change.OldData.CoverImage != change.NewData.CoverImage;
var iconChanged = optimizerSettings.AlwaysOptimizeOnSave || change.OldData.Icon != change.NewData.Icon;

       OptimizeGame(game, optimizerSettings, backgroundChanged, coverChanged, iconChanged);

       if (backgroundChanged || coverChanged || iconChanged)

       {

           if (optimizerSettings.RunInBackground)

           {

               // todo

Is there actually anything left to do here?
—
Reply to this email directly, view it on GitHub
https://github.com/UrbanCMC/PlayniteExtensions/pull/7#pullrequestreview-1892358705,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCCAX3WJVQCMVALXEFU4HLYUWUYRAVCNFSM6AAAAABDR672YCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQOJSGM2TQNZQGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Different css for different page?

Hi. I have 2 sources of data and they are very different from each other. My question is, how can i make use of Carousel to render 2 different styles on each page?
Page 1: Timely promotion
Page 2: Static information of eatery
Data for page 2 always exist, but i want my renderItem to check if 2 records exist (or not) and render the styles accordingly. I am not sure how to make use of the index./what should be used . Is anyone able to enlighten me?
Not sure if what i'm asking is doable. I'm new to react native

After trying out for two days, i finally managed to get things working.


should not open the database to the whole internet

I'd like to remove this bit of code from the external SQL:
     authorized_networks = [         {           name  = "all"           value = "<IP_ADDRESS>/0"         },       ]
There are a few ways to do this. First is that we should create NAT instances for externally bound traffic. This implies other changes. Secondly we could wait until Cloud SQL can do internal IPs and fix it then. Opening this for discussion.

@matthewfischer - can we try working in the private IPs first and then when NAT GWs become a thing introducing those? Seems like at least the Private IPs would be more secure in the short term.
Would you be open to making a PR for this?

Wouldn't a shorter fix be to use the public ip assigned to the opsman instead since terraform knows it?


Random crash with mrcrayfishvehicle.blockBlockVehicleCrate

Random crash with mrcrayfishvehicle.blockBlockVehicleCrate
Crashes to Windows
1.Random crash when opening inventory
2.
3.
...

Minecraft:1.12.2
Forge:2468
Refined Storage:refinedstorage-1.6.11
crash-2019-02-23_18.47.57-client.txt

Does this issue occur on a server? [yes/no] Dont know
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

Hi, this is a MrCrayfishVehicle bug. Please report it to them, thanks.


How to auto detect langauge using speechsdk

Our Language Detection feature hasn't made it into the JavaScript / TypeScript based library yet. It's in our backlog to do so, but I don't have a firm date I can share for when it'll be done.

Our Language Detection feature hasn't made it into the JavaScript / TypeScript based library yet. It's in our backlog to do so, but I don't have a firm date I can share for when it'll be done.

Is there any support with C# or Python? The main motive is auto detection of spoken language by speaker.

The C# HowTo is here:
https://docs.microsoft.com/azure/cognitive-services/speech-service/how-to-automatic-language-detection?pivots=programming-language-csharp
From there you can also select to see the samples in Python.

The C# HowTo is here:
https://docs.microsoft.com/azure/cognitive-services/speech-service/how-to-automatic-language-detection?pivots=programming-language-csharp
From there you can also select to see the samples in Python.
Alright! Thanks.

The C# HowTo is here:
https://docs.microsoft.com/azure/cognitive-services/speech-service/how-to-automatic-language-detection?pivots=programming-language-csharp
From there you can also select to see the samples in Python.

AutoDetectSourceLanguageConfig not working as expected. I have added two source languages i.e. hi-IN and en-US but it is always recognizing en-US. But when I set hi-IN only, it works fine. Kindly help what I need to do more?

I am also getting the same problem .When passing multiple languages parameter it is not working correct for spanish and indian languages

I am also getting the same problem .When passing multiple languages parameter it is not working correct for spanish and indian languages

I am having the same problem with auto detection using en-US and ja-JP. I found out that you need to pause for a while about 10 secs, before speaking in another language for it to detect properly. Is there anyway I could perform language auto detection per every line of speech without any pause?

@paulchua-pc3 Thanks for the question, reopening the case.

The latest Speech SDK @ 1.17.0 (announced today) has support for this. We will be talking about the new features in the SDK at our upcoming //Build conference. Also updated developer documentation will be available mid next week

This is the example of how to do continuous language detection and speech recognition with multiple languages in Carbon 1.17.0:
sample code

This is the example of how to do continuous language detection and speech recognition with multiple languages in Carbon 1.17.0:
sample code

Thanks for the assistance, I was able to get it working using the V2 endpoint.


Mod shortcut crashing

Type
Crash/Error/Exception
Version
Beta (v2024.24.0)
Description of the bug
Open game, immediately open mods (F1) and press W repeatedly.
Boom, crashed.
Screenshots/Video
Video was too big... So...
https://youtu.be/mw3F2Mi6r3k

Apparently this causes it too:
https://youtu.be/ASd6phVGA9Y
Map used:
https://quavergame.com/mapset/map/147576
Same procedure.

Completely unrelated to mods, this happens because the currently selected song does not have a title.

That's how it looks in the file:

And that's in Quaver:

The "No title" is intentional, as seen here:
https://www.youtube.com/watch?v=_q-J3QYT98g
That's the video from the artist themselves.


release-tool: removal of entries that share the same category

Title: release-tool: removal of entries that share the same category
Description:
The release tool (bazel run //tools/project:release) removes entries in the changelog if multiple entries belong to the same category.
Example:
https://github.com/envoyproxy/envoy/pull/22227/commits/27e7a013cfc601a7239792d37f69a283a00ecfe8
We should either force a category for each individual entry, or fix the tool to support multiple entries per category.

was this not just my bad commit here https://github.com/envoyproxy/envoy/pull/22204/files#diff-6f9c718224c533c13c2c0ba1d5abaab86be9d0cc73808749c77934e9f9b0d5d0L243
i think we just need to lint it better (#22222 )


Alina-Student bio

Checklists
General Checks

[x] the branch is up to date with main/master
[x] the code works when pulled and run locally
[x] All CI checks pass
[x] all conflicts are resolved (if any)
[x] PR has a descriptive title
[x] PR has appropriate labels and milestones for easy identification
[x] PR it is assigned to the owner
[x] reviewers are assigned
[x] the PR contributes only one focused change
[x] It is in the appropriate column in the project board (if necessary)
[x] has short and clear description
[ ] is linked to an issue (if it is related)
[x] feedback is addressed (if any and if it is appropriate feedback.)

Markdown

[x] the markdown source is formatted
[x] spelling and grammar is correct in all text
[x] The markdown looks correct when you preview the file
[x] all links and images work
[x] any embedded code snippets are formatted

Hi @gelilaa
I renamed alina.md to AlinaTaoRao.md, but PR shows "all checks have failed". I can't find where the problem is, could you help me?


CLI flags are inconsistent some use --organization-id and others use --org-id

Describe the bug
CLI flags are inconsistent some use --organization-id and others use --org-id
How to Reproduce
See nexd and nexctl usage.
Expected Behavior
commands should use the same flag name for organizatinos.
Deployment Environment
No response
Additional Context
No response

@russellb we can close this issue

@russellb we can close this issue

Thanks!  If you put Closes #1179 in your PR description, it should automatically close the issue for you. Just FYI for the future!


Replace unneeded back ticks (`) with single quotes (')

Much of the output from these samples contain unnecessary backticks for string output. We should replace the unneeded backticks with single quotes.

I'm surprised the linter didn't catch those ...


v2 ConsensusVersion + migrations

For chains that integrated packet-forward-middleware/v2, a migration is necessary to the GenesisState to add the InFlightPackets map.

unnecessary change, the root cause was due to the rename of the module from packetfowardmiddleware to packetforwardmiddleware


x/build/cmd/relnote: document RELNOTE marker rules

As far as I know at this time, the RELNOTE marker isn't documented anywhere.
I suspect this causes it to be used less often and not to its full potential.
For example, it's possible to write a string other than yes or y and then the entire string will be included in the generated notes. This means it's possible to write a part of release notes via the RELNOTE marker, not just say "yes". I only learned this today when reading cmd/relnote code, and it's possible more people would take advantage of this if they knew it also.
Perhaps it is already documented somewhere and then this bug is about making me learn that. I've looked in the package documentation and the wiki, with no luck. I've only found https://groups.google.com/d/msg/golang-dev/edmMTXNukjE/V2bh9Vt3CAAJ and #20102 where it was originally announced by @bradfitz, but those aren't good sources for long-term documentation.
/cc @golang/osp-team

To be honest, I would rather we discourage the use of RELNOTE anyway. The RELNOTE marker makes it easy to add essentially a TODO for someone else to write a release note later, but doesn't actually assign anyone in particular to do it.
I think it's fine to defer writing the release notes — particularly if the CL author isn't comfortable writing English prose for publication — but in that case I would prefer that we add an explicit TODO to the release notes (with more context and a specific person assigned to fill it in), or to file a release-blocker+Documentation issue with an explicit assignee.

I agree that that is the ideal, but we should raise writing a release note, even a TODO note, as a blocker for external contributors who may not be familiar with our conventions.  For those cases, it's easy for a maintainer to add a RELNOTE tag to the CL.

@ianlancetaylor, it seems nearly as easy for a maintainer to add an open issue, which would allow significantly more visibility into the context. (For example, the issue can have a specific assignee and would be more visible in milestone tracking.)
Or, for that matter, it's easy enough for a maintainer to immediately send a followup CL to add the release note. I understand why it can be useful to separate the release-note writing from the contributor's CL, but I don't see the benefit in deferring the release notes as technical debt until the end of the cycle, and that is (empirically) how the RELNOTE tag tends to play out.

You are assuming that a core team member is involved with every CL, and that is not the case.  I really do not want to raise additional barriers to contribution.  I agree that RELNOTE is not ideal, but it's not impossible to work with.

@ianlancetaylor I’m not sure I agree that it’s an unacceptable burden to place on a contributor. There are circumstances that may warrant an exception (english is not their primary language, for example), but as we would expect someone to add adequate documentation next to the code they’ve written, asking them to update an html file as well doesn’t seem too onerous.
It increases the barrier to contribution, but not by much. I’d rather have the effort spread across all authors and not on a select few who should be focused primarily on getting a reliable release out on time rather than collating and writing notes for functionality they may not be familiar with.

Your stance is entirely reasonable.  Still, I hold to my position: by all means encourage writing release notes where appropriate, but don't require them.

I’d say we should strongly encourage writing release notes, taking into account the circumstances, of course. Right now it’s the exception. I’d like to move it more toward the norm, especially for long-time contributors.

It also doesn't seem onerous to ask contributors who are +2'ing and merging a CL without a core team member involved to file an issue for someone else to follow up with documentation.
That's only a bit more overhead than making a RELNOTE= comment, and would only affect well-established contributors who presumably have an interest in the health of the project anyway.

Actually, could GopherBot open an issue as soon as the CL is merged? That might combine the best of both workflows...

(See previously https://github.com/golang/go/issues/26419#issuecomment-501945160.)

Yes, gopherbot can do that, but it'll have to take care not make the mistake of no longer finding an issue it previously created, and entering a loop where it starts creating issues non-stop. While it can be humorous at first, that would not be good.
I suggest filing a separate issue for that, since it's not a completely trivial task and it would be helpful to agree on a high-level approach first. Writing the code to implement it should be easy.

Here's a drive-by idea. If a commit on master results in a change in api/next.go compared to its parent, it should be marked for inclusion in the release notes.


Circumvent potential file size limit of generated config

Describe Request:
On behalf of the team @bionicstork:

When using dynamic configuration and the orb "circleci/continuation" the created config file has a size limit since the orb is passing the config using command line arguments and not files.

We fixed this by copying your code and changing it so it will split the config file, stringify the yaml and join all the parts back together.

Examples:
CONFIG_PATH=<<parameters.configuration_path>>
PARAMETERS=<<parameters.parameters>>

if [ -z "${CIRCLE_CONTINUATION_KEY}" ]; then
echo "CIRCLE_CONTINUATION_KEY is required. Make sure setup workflows are enabled."
exit 1
fi

if [ -z "${CONFIG_PATH}" ]; then
echo "CONFIG_PATH is required."
exit 1
fi

PARAMS=$([ -f "$PARAMETERS" ] && cat "$PARAMETERS" || echo "$PARAMETERS")

if ! jq . >/dev/null 2>&1 \<<<"$PARAMS"; then
echo "PARAMETERS aren't valid json"
exit 1
fi

echo "{\"config\":\"" > final
split -l 1000 "$CONFIG_PATH" part

parts=$(ls | grep part)

for p in $parts
do
content=$(cat $p)
jq -n --stream \
--arg config "$content" \
'{"part": $config}' > jsoned

partStr=""
split -l 1 jsoned line
line=$(cat lineab)
line=${line:11}
line=$(echo "$line" | sed 's/.$//')

current=$(cat final)
echo "${current}\n${line}" > final
done

current=$(cat final)
echo "${current}\"}" > final

JSON_BODY=$( jq -n --stream \
--arg continuation "$CIRCLE_CONTINUATION_KEY" \
--slurpfile config final \
--arg params "$PARAMS" \
'{"continuation-key": $continuation, "configuration": $config[0].config, parameters: $params|fromjson}'
)

echo "$JSON_BODY" > json_body

cat json_body

[[ $(curl \
-o /dev/stderr \
-w '%{http_code}' \
-XPOST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
--data @json_body \
"https://circleci.com/api/v2/pipeline/continue") \
-eq 200 ]]

for the https://github.com/CircleCI-Public/continuation-orb/blob/master/src/scripts/continue.sh script.
Supporting Documentation Links:

Having run into this, I've also created a custom continue command - however the only difference is that parameters is required to be a file (as I didn't need it to work as a string, but that would need handling in the orb proper), so that I can use the following jq command:
                jq -n \
                    --arg continuation "$CIRCLE_CONTINUATION_KEY" \
                    --slurpfile params "$PARAMETERS" \
                    --slurpfile config /tmp/circleci/config-string.json \
                    '{"continuation-key": $continuation, "configuration": $config|join("\n"), "parameters": $params[0] }' > /tmp/circleci/continue_post.json

We are not sure how this could be solved only on the orb side. It will possibly require some API changes. Would you mind creating a canny for it? I'm closing this for now


Update: Meltytech.Shotcut version 20.04.12

Removing old versions to reduce clutter
Microsoft Reviewers: Open in CodeFlow

/azp run


Error DefaultAddressSpace

I think code in Application.cs line 87 should be changed from:
AddressSpaceTable[new NodeId(UAConst.BaseDataType)].References.Add(new ReferenceNode(new NodeId(UAConst.Organizes), new NodeId(UAConst.DataTypesFolder), false));
to:
AddressSpaceTable[new NodeId(UAConst.BaseDataType)].References.Add(new ReferenceNode(new NodeId(45), new NodeId(UAConst.DataTypesFolder), true));
(Should probably also have been moved to line 829, but it is possible that there is some auto generation that makes it difficult)

UInteger should be under Number not under Integer
Thanks for a good OPC UA library

Glad you like the library.
This address space is automatically generated from the OPC UA specification. It looks like unsigned integer is a subtype of regular integers, so I will leave it there. I only see 3 root categories in the original definition: double, float and integer.


Add force-non-ssl to registry operations

I've been running registries locally and/or temporarilly and it's practical to be able to disable the SSL when querying it.
While I'm at it, would it make sense to you to switch to https://github.com/heroku/docker-registry-client, which seem to be almost the same registry API that implemented here?

IIRC when I looked at herokus the last time there was not all the same functions...

This needs a rebase but I also would like to see this in reg. I use it to query what repositories are available from an insecure registry.

oh good to know thanks justin :)
On Wed, Sep 19, 2018 at 1:40 PM Justin Garrison<EMAIL_ADDRESS>wrote:

This needs a rebase but I also would like to see this in reg. I use it to
query what repositories are available from an insecure registry.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/genuinetools/reg/pull/102#issuecomment-422894066, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYNbLdjoDE2SHP7G8j3BFQa-EYQzYb7ks5ucoGVgaJpZM4U6EQu
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

Rebased if needed

thanks!


Can't find a LAT/LON which works on api

https://airapi.airly.eu/v2/measurements/point?indexType=AIRLY_CAQI&lat=54.32009&lng=18.63646 - does return proper value
sensor:

platform: airly
name: 'Air Quality'
api_key: '---------------------'
latitude: '54.32009'
longitude: '18.63646'
language: 'pl'

Sat Nov 23 2019 09:41:57 GMT+0100 (Central European Standard Time)
Can't retrieve data: no Airly sensors in this area

I used your configuration and integration works as usual.
sensor:
  - platform: airly
    name: 'dawiduniec'
    api_key: 'redacted'
    latitude: '54.32009'
    longitude: '18.63646'

I just did removed docker, purge images, fetched last stable and issue is still there:

Same with new api key

Remove integration and config from configuration.yaml and add it once again via config_flow.

No response


Added Projects Section. Modified other secion titles and minor updates.

Confirmed changes. Push to Prod.


Variables cannot be named "product", "value" or "country" in balassa_index

I just wanted to make you aware of an issue I recently faced with the function balassa_index:
R gives you the error message "Error in [.data.frame(x, r, vars, drop = drop) : undefined columns selected", whenever your variables/columns used are named product, value or country. This probably arises because the three options named in the function itself for the selection of these three variables is exactly named like this.
Once you rename the variables the function works normally. Maybe this is already stated somewhere in the help file, but I just wanted to make you aware of this.

@fabianscheifele apologies for the delayed response, I totally missed this notification.
this works for me
d <- world_trade_avg_1998_to_2000
names(d) <- letters[1:3]

bi1 <- balassa_index(d,
                     country = "a", product = "b", value = "c")

bi2 <- balassa_index(world_trade_avg_1998_to_2000)

all.equal(bi1, bi2)

This is what I documented years ago
#' @param country (Type: character) the column with the countries.
#' By default this is set to \code{"country"}. Used only if the input is a data.frame.
#' @param product (Type: character) the column with the products.
#' By default this is set to \code{"product"}. Used only if the input is a data.frame.
#' @param value  (Type: character) the column with the metric for
#' country-product pairs.
#' By default this is set to \code{"value"}. Used only if the input is a data.frame.


[Bug] ModuleNotFoundError: No module named 'projects.BEVFusion' when the pytorch3d is installed

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (dev-1.x) or latest version (dev-1.0).

Task
I have modified the scripts/configs, or I'm working on my own tasks/models/datasets.
Branch
main branch https://github.com/open-mmlab/mmdetection3d
Environment
sys.platform: linux
Python: 3.8.10 (default, Nov 22 2023, 10:22:35) [GCC 9.4.0]
CUDA available: True
numpy_random_seed:<PHONE_NUMBER>
GPU 0: NVIDIA GeForce RTX 3080 Ti
CUDA_HOME: /usr/local/cuda-11.3
NVCC: Cuda compilation tools, release 11.3, V11.3.58
GCC: x86_64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
PyTorch: 1.11.0+cu113
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.0 Product Build 20191122 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v2.5.2 (Git Hash a9302535553c73243c632ad3c4c80beec3d19a1e)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 11.3
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86
  - CuDNN 8.2
  - Magma 2.5.2
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.3, CUDNN_VERSION=8.2.0, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.11.0, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=OFF, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF,

TorchVision: 0.12.0+cu113
OpenCV: 4.7.0
MMEngine: 0.10.1
MMDetection: 3.0.0
MMDetection3D: 1.1.1+bef772a
spconv2.0: True

Reproduces the problem - code sample
None
Reproduces the problem - command or script
None
Reproduces the problem - error message
Traceback (most recent call last):
  File "/home/hkd/.local/lib/python3.8/site-packages/mmengine/utils/misc.py", line 77, in import_modules_from_strings
    imported_tmp = import_module(imp)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'projects.BEVFusion'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/hkd/.local/lib/python3.8/site-packages/mmengine/config/config.py", line 462, in fromfile
    import_modules_from_strings(**cfg_dict['custom_imports'])
  File "/home/hkd/.local/lib/python3.8/site-packages/mmengine/utils/misc.py", line 84, in import_modules_from_strings
    raise ImportError(f'Failed to import {imp}')
ImportError: Failed to import projects.BEVFusion.bevfusion

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "tools/deployment/test.py", line 987, in test_mmdet3d
    cfg = Config.fromfile(args.config)
  File "/home/hkd/.local/lib/python3.8/site-packages/mmengine/config/config.py", line 474, in fromfile
    raise ImportError(err_msg) from e
ImportError: Failed to import custom modules from {'imports': ['projects.BEVFusion.bevfusion'], 'allow_failed_imports': False}, the current sys.path is:
    /home/hkd/calibration/catkin_ws/devel/lib/python3/dist-packages
    /opt/ros/noetic/lib/python3/dist-packages
    /usr/lib/python38.zip
    /usr/lib/python3.8
    /usr/lib/python3.8/lib-dynload
    /home/hkd/.local/lib/python3.8/site-packages
    /home/hkd/.local/lib/python3.8/site-packages/transforms3d-0.4.1-py3.8.egg
    /home/hkd/.local/lib/python3.8/site-packages/sklearn-0.0.post4-py3.8.egg
    /home/hkd/.local/lib/python3.8/site-packages/SharedArray-3.2.3-py3.8-linux-x86_64.egg
    /home/hkd/.local/lib/python3.8/site-packages/easydict-1.11-py3.8.egg
    /home/hkd/.local/lib/python3.8/site-packages/rabbitvcs-0.19-py3.8.egg
    /home/hkd/fusion/mmdetection3d
    /home/hkd/packages/fvcore
    /home/hkd/packages/iopath
    /home/hkd/packages/pytorch3d
    /usr/local/lib/python3.8/dist-packages
    /usr/lib/python3/dist-packages

You should set `PYTHONPATH` to make `sys.path` include the directory which contains your custom module

Additional information
I have developed a project using BEVFusion based on MMDet3D without any problem or error from now on.
I installed the PyTorch3D to use the specific operation of it.
But, after installing it, the error of ModuleNotFoundError: No module named 'projects.BEVFusion' raises when running any script which is based on MMDet3D.
This is the commands to install the pytorch3d (I referred to here)
$ https://github.com/facebookresearch/pytorch3d && cd pytorch3d
$ pip install -e .

Can you assume the reason?
Thank you in advance!

@eugenebak solved how ?

@eugenebak solved how ? I had this error locally and running python projects/BEVFusion/setup.py develop solved the issue but doesnt solve it on Docker

I met same problem and run your command but I met new error like that:
/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/utils/cpp_extension.py:476: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
warnings.warn(msg.format('we could not find ninja.'))
warning: no files found matching '.cpp' under directory 'mmdet3d/.mim/ops'
warning: no files found matching '.cu' under directory 'mmdet3d/.mim/ops'
warning: no files found matching '.h' under directory 'mmdet3d/.mim/ops'
warning: no files found matching '.cc' under directory 'mmdet3d/.mim/ops'
writing manifest file 'bev_pool.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
File "projects/BEVFusion/setup.py", line 70, in
zip_safe=False,
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/init.py", line 155, in setup
return distutils.core.setup(**attrs)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 148, in setup
return run_commands(dist)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 163, in run_commands
dist.run_commands()
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands
self.run_command(cmd)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
cmd_obj.run()
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/command/develop.py", line 34, in run
self.install_for_development()
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/command/develop.py", line 114, in install_for_development
self.run_command('build_ext')
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
cmd_obj.run()
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 499, in build_extensions
_check_cuda_version(compiler_name, compiler_version)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 382, in _check_cuda_version
torch_cuda_version = packaging.version.parse(torch.version.cuda)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/pkg_resources/_vendor/packaging/version.py", line 49, in parse
return Version(version)
File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/pkg_resources/_vendor/packaging/version.py", line 264, in init
match = self._regex.search(version)
TypeError: expected string or bytes-like object
Do you have any suggestions for me?

@eugenebak solved how ? I had this error locally and running python projects/BEVFusion/setup.py develop solved the issue but doesnt solve it on Docker

I met same problem and run your command but I met new error like that: /home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/utils/cpp_extension.py:476: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend. warnings.warn(msg.format('we could not find ninja.')) warning: no files found matching '.cpp' under directory 'mmdet3d/.mim/ops' warning: no files found matching '.cu' under directory 'mmdet3d/.mim/ops' warning: no files found matching '.h' under directory 'mmdet3d/.mim/ops' warning: no files found matching '.cc' under directory 'mmdet3d/.mim/ops' writing manifest file 'bev_pool.egg-info/SOURCES.txt' running build_ext Traceback (most recent call last): File "projects/BEVFusion/setup.py", line 70, in zip_safe=False, File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/init.py", line 155, in setup return distutils.core.setup(**attrs) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 148, in setup return run_commands(dist) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 163, in run_commands dist.run_commands() File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands self.run_command(cmd) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/command/develop.py", line 34, in run self.install_for_development() File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/command/develop.py", line 114, in install_for_development self.run_command('build_ext') File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 79, in run _build_ext.run(self) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 339, in run self.build_extensions() File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 499, in build_extensions _check_cuda_version(compiler_name, compiler_version) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 382, in _check_cuda_version torch_cuda_version = packaging.version.parse(torch.version.cuda) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/pkg_resources/_vendor/packaging/version.py", line 49, in parse return Version(version) File "/home/lacie/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/pkg_resources/_vendor/packaging/version.py", line 264, in init match = self._regex.search(version) TypeError: expected string or bytes-like object
Do you have any suggestions for me?

@lacie-life Hi, I met the same error. Did you solve it? Thanks!

I solved that by clear everything and reinstall by this link

I solved that by clear everything and reinstall by this link

@lacie-life Thanks for your quick reply! My situation is a little different but I have solved it!


WebSocketTransports are not disabled  for dev-portal profile when using profile optimizer

Need to change "api-store" to "api-devportal" in  infer.json in repository/resources/conf to disable unused transports.

tagging: https://github.com/wso2/product-apim/issues/7228