Xhamster Favorites

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I'm running yt-dlp version 2023.01.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Russia
Example URLs
https://xhamster.com/users/cubafidel/favorites/videos
Provide a description that is worded well enough to be understood
Please add a function to download xhamster favorites playlist
Now extractor download user videos instead of user favorites videos
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://xhamster.com/users/cubafidel/favorites/videos']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.01.06 [6becd25] (pip)
[debug] Python 3.10.9 (CPython arm64 64bit) - macOS-13.2-arm64-arm-64bit (OpenSSL 1.1.1s  1 Nov 2022)
[debug] exe versions: ffmpeg 5.1.2 (setts), ffprobe 5.1.2
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1760 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2023.01.06, Current version: 2023.01.06
yt-dlp is up to date (2023.01.06)
[XHamsterUser] Extracting URL: https://xhamster.com/users/cubafidel/favorites/videos
[download] Downloading playlist: cubafidel
[XHamsterUser] cubafidel: Downloading page 1
[XHamsterUser] cubafidel: Downloading page 2
[XHamsterUser] cubafidel: Downloading page 3
[XHamsterUser] cubafidel: Downloading page 4
[XHamsterUser] cubafidel: Downloading page 5
[XHamsterUser] cubafidel: Downloading page 6
[XHamsterUser] cubafidel: Downloading page 7
[XHamsterUser] cubafidel: Downloading page 8
[XHamsterUser] Playlist cubafidel: Downloading 227 items of 227
[download] Downloading item 1 of 227
[XHamster] Extracting URL: https://xhamster.com/videos/large-saggy-hangers-2-3388122
[XHamster] 3388122: Downloading webpage
[XHamster] 3388122: Downloading m3u8 information
[XHamster] 3388122: Downloading m3u8 information
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] 3388122: Downloading 1 format(s): hls-1287-1
[debug] Invoking hlsnative downloader on "https://video3.xhcdn.com/key=mO2N1VaXbV4ctCJbKzGm7A,end=1674583200/data=<IP_ADDRESS>-dvp/media=hls4/003/388/122/720p.h264.mp4.m3u8"
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 305
[download] Destination: Large Saggy Hangers 2 [3388122].mp4
[download]   3.2% of ~ 193.21MiB at  843.00KiB/s ETA 03:44 (frag 9/305)^C
ERROR: Interrupted by user

this would be great


new notebooks / examples

Here a list of examples / notebooks for new functions that we need add @giovp :
To update

[x] update ImageContainer example (setting layers with img['layer'], and changes introduced by https://github.com/theislab/squidpy/pull/324 ) -> #64
[x] update processing example with Dask image changes -> #64
[x] update feature extraction examples
[x] update segmentation example with pointers to how borders between chunks are handled. Also update image tutorials with this
[x] building a spatial graph with new functionalities
[ ] update Napari tutorial with pointers to z-stack functionalities (low prio) @giovp
[x] update visium tutorials

New examples

[x] add an example for img.show which now has some nice functionalities @giovp
[x] add example for sq.pl.extract @giovp
[x] example showing how to chain cropping and scaling functions (dummy data) -> in image container overview tutorial #64
[x] examples for new spatial stats (ripleys, moran/geary and sepal)
[ ] example for using apply function with custom functions @hspitzer -> in new pr
[ ] example for using spot generator for custom feature extraction workflows @hspitzer -> in new pr
[x] example of img.subset -> in compute_crops.py #64

New tutorials

[ ] one tutorial analysis for each dataset
[x] tutorial on using and visualising zstacks (with feature extraction)
[x] tutorial on plot graph stats on 3D data
[x] external tutorial for cell-segmentation with stardist
[x] external tutorial for cell segmentation with cellpose
[x] external tutorial for image features with cell profiler -> #63

hey, sorry just saw this, really nice, added couple of more.
Here's some comments:

example showing how to chain cropping and scaling functions (dummy data)

this to me is key, needs to be really clear how cropping/uncropping/subset works

tutorial on plot graph stats on 3D data

good reminder

one tutorial analysis for each dataset

Yes? boring/tedious but I guess we can't really escape it.

add an example for img.show which now has some nice functionalities @giovp

shall I use mibitof instead of fluorescent crop data? cause the latter I can only show different channels etc. and not segmentation masks, not sure how interesting...

add an example for img.show which now has some nice functionalities @giovp

shall I use mibitof instead of fluorescent crop data? cause the latter I can only show different channels etc. and not segmentation masks, not sure how interesting...

Yes, good idea! We were going to use diverse data in the examples / tutorials anyways. Have a look at my mibitof tutorial in #64  to see how I concatenate the images in the image container.

@giovp @hspitzer think this can be also closed, or?

I think @hspitzer has still some examples in mind but I don't think we'll include it in this relase.

correct, there are still 2 open TODOs, we can open a new issue for this, or keep this open until I have time to make the examples. They don't need to be included in the release though.

@dineshpalli as discussed:

function to show example for: https://squidpy.readthedocs.io/en/latest/classes/squidpy.im.ImageContainer.apply.html
example to use as backbone: https://squidpy.readthedocs.io/en/latest/auto_examples/image/compute_gray.html and not rendered: https://github.com/theislab/squidpy_notebooks/blob/master/examples/image/compute_gray.py

You can check out contributing guides in the link I sent you and you should be good to go. Feel free to reach out for anything, Giovanni


Async execution yields wrong results

Hello, I did a small test based on net.javacrumbs.completionstage.load.LoadTest with all chaining methods switched to *Async variant + I removed combineEither to avoid uncertainty.
Here is a test:
package net.javacrumbs.completionstage.load;

import net.javacrumbs.completionstage.CompletableCompletionStage;
import net.javacrumbs.completionstage.CompletionStageFactory;
import org.junit.Test;

import java.util.List;
import java.util.Random;
import java.util.concurrent.CompletionStage;
import java.util.concurrent.CopyOnWriteArrayList;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.atomic.AtomicInteger;

import static org.assertj.core.api.Assertions.assertThat;

public class LoadTestAsync {
    private final ExecutorService executor = Executors.newFixedThreadPool(50);
    private final CompletionStageFactory factory = new CompletionStageFactory(executor);
    private final Random random = new Random();
    private final List<String> errors = new CopyOnWriteArrayList<>();
    private final AtomicInteger processed = new AtomicInteger();

    @Test
    public void testLoad() throws InterruptedException {
        for (int i = 0; i < 100_000; i++) {
            this.doTest();
        }
        assertThat(errors).isEmpty();
        System.out.println(processed.get());
    }

    public void doTest() {
        int value = random.nextInt(Integer.MAX_VALUE / 3);
        delayedCompletionStage(value)
                .thenCombineAsync(delayedCompletionStage(value), (a, b) -> a + b)
                .thenApplyAsync(i -> i / 2)
                .thenApplyAsync(i -> i - value)
                .thenAcceptAsync(i -> {
                    processed.incrementAndGet();
                    if (i != 0) {
                        errors.add("Error from " + value + " result " + i);
                    }
                });
    }

    private <T> CompletionStage<T> delayedCompletionStage(T value) {
        CompletableCompletionStage<T> completionStage = factory.createCompletionStage();
        completionStage.complete(value);
        return completionStage;
    }
}

Obviously, System.out.println(processed.get()) should print a number of the iterations in the for loop deined here:
    @Test     public void testLoad() throws InterruptedException {         for (int i = 0; i < 100_000; i++) {...}
However, starting from some reasonably high number (in my case, approx. 70_000) the test starts to produce random results, like 49731, 51237 etc.
So I guess smth. is broken with async chains under high contention.
Btw, tests hangs if I try smth. like 10_000_000 iterations, while original "synchronus" test works OK with 100_000_000 iterations....

Ineresting, when I use other thread pool, namely
private final ExecutorService executor = Executors.newWorkStealingPool(50);
there is no such issues -- result is correct and test doesn't hangs on extra large number of iterations (100_000_000)...

Closing issue -- it was my fault, correct test should looks like
package net.javacrumbs.completionstage.load;

import net.javacrumbs.completionstage.CompletableCompletionStage;
import net.javacrumbs.completionstage.CompletionStageFactory;
import org.junit.Ignore;
import org.junit.Test;

import java.util.List;
import java.util.Random;
import java.util.concurrent.CompletionStage;
import java.util.concurrent.CopyOnWriteArrayList;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.atomic.AtomicInteger;

import static org.assertj.core.api.Assertions.assertThat;

public class LoadTestAsync {
    private final ExecutorService executor = Executors.newFixedThreadPool(50);
    private final CompletionStageFactory factory = new CompletionStageFactory(executor);
    private final Random random = new Random();
    private final List<String> errors = new CopyOnWriteArrayList<>();
    private final AtomicInteger processed = new AtomicInteger();

    @Test
    //@Ignore
    public void testLoad() throws InterruptedException {
        for (int i = 0; i < 1_000_000; i++) {
            this.doTest().toCompletableFuture().join();
        }
        assertThat(errors).isEmpty();
        System.out.println(processed.get());
    }

    public CompletionStage<Void> doTest() {
        int value = random.nextInt(Integer.MAX_VALUE / 3);
        return delayedCompletionStage(value)
                //.applyToEitherAsync(delayedCompletionStage(value), i -> i * 2)
                .thenCombineAsync(delayedCompletionStage(value), (a, b) -> a + b)
                .thenApplyAsync(i -> i / 2)
                .thenApplyAsync(i -> i - value)
                .thenAcceptAsync(i -> {
                    processed.getAndIncrement();
                    if (i != 0) {
                        errors.add("Error from " + value + " result " + i);
                    }
                });
    }

    private <T> CompletionStage<T> delayedCompletionStage(T value) {
        CompletableCompletionStage<T> completionStage = factory.createCompletionStage();
        completionStage.complete(value);
        return completionStage;
    }
}

I.e. it's necessary to wait till tests completion before reporting results

I would call .toCompletableFuture().join() after the for loop, but it's irrelevant. Do you need any help from me? I have been thinking about the Managed use-case and one  possible solution might be to wrap the Executor (or not?)

No. Just verified myself that ManagedExecutorService handles context switches on it's own:

Tasks are run in managed threads provided by the Java™ EE Product Provider and are run within the application component context that submitted the task
https://docs.oracle.com/javaee/7/api/javax/enterprise/concurrent/ManagedExecutorService.html

So my only task is to create wrapper for ManagedExecutorService like I did for ExecutorService (though, this time it's more involved).
Btw, I've checked performance between CallbackRegistry that I included in the pull request and your implementation -- indeed, your implementation is 40-45% faster.
P.S. I were expecting that non-async methods of CompletionStage will be faster than *Async ones, but... The Async version according to my test is approx 15 times slower than synchronous one (745 seconds vs 49 on my hardware).

Lukáš, could you please make a release with recent changes?

I will release it tonight.

2016 7:37, 7:37, Valery Silaev<EMAIL_ADDRESS>napsal/a:

Lukáš, could you please make a release with recent changes?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/lukas-krecan/completion-stage/issues/6#issuecomment-221477472

Released version 0.0.7, it will take few hours to get to central repo.


How to cleanly disconnect from a logs stream?

I'm trying to stream logs from a container over WebSockets. I've got it mainly working but I'm struggling to workout how to cleanly disconnect the stream when the WS is closed.
wss.on('connection',function(ws, req){
  console.log(req.url);

  const containerId = req.url.substring(1);
  const container = docker.getContainer(containerId);
  const logStream = new stream.PassThrough();

  logStream.on('data', (chunk) => {
    ws.send(chunk);
  })

  container.logs({stdout: true, stderr: true, follow: true, tail: 20})
  .then(logs => {
    container.modem.demuxStream(logs, logStream, logStream);
  });

  ws.on('close', function(){
    logStream.end();
  });
})

If I close logStream then container.modem.demux() throws an async error because the underlying stream is close.

worked it out:
	//should do authentication here
	wss.handleUpgrade(req, socket, head, function (ws) {
    wss.emit('connection', ws, req);
  });
});

wss.on('connection',function(ws, req){
	const containerId = req.url.substring(1);
	const container = docker.getContainer(containerId);
	var inStream;
	const logStream = new stream.PassThrough();

	logStream.on('data', (chunk) => {
		ws.send(chunk);
	})

	container.logs({stdout: true, stderr: true, follow: true, tail: settings.logHistory })
	.then(logs => {
		inStream = logs;
		return container.modem.demuxStream(logs, logStream, logStream);
	})
	.catch( err => {
		console.log("err");
	});

	ws.on('close', function(){
		if (inStream) {
			inStream.destroy();
		}
		logStream.end();
	});

})


can't create new project

I have a problem with creating a new project (bug in the attachment). I use Visula studio profesional 2015 and have installed cs-sscript by:
C: > choco install cs-script

I have moved your post to a more appropriate thread: https://github.com/oleg-shilo/CS-Script.VSIX/issues/1
I have posted the fix suggestion there.


Compile a  scss file wrong

I had add sass.js and sass.worker.js in my project,here is my code:
var sass = new Sass();
var base = '../../furnace/';
var directory = '';
var files = [
	'audio/sass/audio.scss'
];
sass.preloadFiles(base, directory, files, function() {
	sass.listFiles(function callback(list) {
		console.log(list);
		sass.readFile(list[0], function callback(content) {
			if(content){
				sass.compile(content, function(result) {
					console.log(result);
				});
			}
		});
	});
});

I got the content of 'audio/sass/audio.scss',but because the first line is @import "../../sass/_base";,there is a wrong look like:
File to import not found or unreadable: sass/_base↵Parent style sheet: stdin
How do i fix it?thanks for your response

see working with files

yeah,I know what you mean,but i use compile() in readFile()'s callback.And i have tested compileFile() looks like:
        sass.preloadFiles(base, directory, files, function() {
			sass.listFiles(function callback(list) {
				console.log(list);
				sass.compileFile(list[0],function(result){
					console.log(result);
				})
			});
		});

then i get the same wrong message.I think the first line of 'audio/sass/audio.scss' caused the problem.Here is it:
@import "../../sass/_base";

Can you give me some advise?

My god,I found the solution.Here is my code:
        var base = '../../furnace/';
		var directory = '';
		var files = [
			'audio/sass/audio.scss',
			'sass/_base.scss'
		];
		sass.preloadFiles(base, directory, files, function() {
			sass.compileFile('audio/sass/audio.scss',function(result) {
				console.log(result.text);
			});
		});

As i said above,first line of 'audio/sass/audio.scss' is:
@import "../../sass/_base";

I need preload ‘_base.scss’ before @import it.Thanks a lot.


new themes and minimap

minimap

adds a basic minimap to the right side of the editor. Activated with the minimap option
pulls colors from editor
no "click to scroll" functionality yet like Sublime Text's
no indication of currently visible section (similar to above)
add documentation for minimap
note: can slow down editor, needs to be optimized fixed
note: minimap.js does not shrink the actual editor, so text will pass behind the minimap (see below)

themes

fix a typo in solarized.css
added 3 new themes: seti dracula yeti
added themes/meta.js, to allow for lazy loading themes, and so that new themes can easily be integrated into applications by simply referencing meta.js
added mode dropdown in the "themes" demo to show how the themes highlight tags, qualifiers, etc.

Pretty interesting! How performant is the minimap on larger documents?

since it pulls all of the information from CodeMirror's viewport, which only shows a snippet of larger documents for performance reasons, it's pretty good.
The only disadvantage of this is that it can't show large parts of the file (only what is rendered by CodeMirror), but the performance gains are worth it.

I've pushed the themes (f52e64d095db6a8bbb) and the Brainfuck mode (84c8c92968174df). I don't consider the linenumbers-for-runmode or the minimap implementations to be production-ready. Next time, please create one pull request per feature, clean up your patch history, and only submit code that is done. This saves me a lot of time.


Integration test need to be generalized for inputs and input nodes

Integration tests suffer from:

Assuming all models have the same input node name (which is incorrect)
Assuming all models operate on a cat image (which is also incorrect)

This needs to be fixed.

Closing in favor of #340


Cow: Watch bsslaptoprepaircenter.com

Cow requests the watch of the watch_keyword bsslaptoprepaircenter\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bsslaptoprepaircenter\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


"1024" numeric with seperator issues

hi
i am using numeric with seperators.
when i input 1.024 saving db. after opening it shown 1,024 but
123.123 after opening it it shown 123.123 do i making mistakes? please help.
opening : sending a input text from db.

@serlogo53 ,
Can you make a jsfiddle for it.  The exact mask implementation with the values.
Robin

hi. i think the problem is mysql locale. i am using  format(value/1024,0, 'en_GB').
when i remove format it's ok. thanks.


Crash on expressionProperties if 'templateOptions.options' stream source is a subject

Description
For templateOptions.options!
When the observable is interval or from works perfectly, but when we adjust to Subject or BehaviourSubject it crashes, because the JSON.stringify crashes on circular references.
Super short crashing snippet:
expressionProperties: {
  'templateOptions.options': modal => new Subject()
}

When we target other templateOptions like templateOptions.label it is working fine.
Minimal Reproduction
https://stackblitz.com/edit/ngx-formly-observable-options-crash

Angular version: stackblitz with 9.x, we use 11.x
Formly version: 5.10.21

Find it a nice way to recreate the observable when the target module path value is changing, therefore we would like to use with difference sources and map / filter based on the model actual values.

Have you tried returning
new Subject().asObservable()?
On Fri, Jul 9, 2021, 12:33 PM Greegko @.***> wrote:

Description
For templateOptions.options!
When the observable is interval or from works perfectly, but when we
adjust to Subject or BehaviourSubject it crashes, because the
JSON.stringify crashes on circular references.
Super short crashing snippet:
expressionProperties: {
'templateOptions.options': modal => new Subject()
}
When we target other templateOptions like templateOptions.label it is
working fine.
Minimal Reproduction
https://stackblitz.com/edit/ngx-formly-observable-options-crash

Angular version: stackblitz with 9.x, we use 11.x
Formly version: 5.10.21

Find it a nice way to recreate the observable when the target module path
value is changing, therefore we would like to use with difference sources
and map / filter based on the model actual values.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ngx-formly/ngx-formly/issues/2922, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADB4XNMVE6P6W3JOM3KGSVTTW4XFBANCNFSM5ADFGLTA
.

Have you tried returning new Subject().asObservable()?

Sure I am not using pure Subject in general, we are always doing some operations, therefore pipe would create an observable anyway, but even with asObservable it won't change the fact the source is a Subject, just hide the interfaces to emit values. But for fun, tried but doesn't help.

This issue has been fixed and released as part of v5.10.22 release.
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!


Added Support for result export to JSON file

Fixes : #2
I have added a new function in utils.go file WriteToJsonFile & correspondingly added -j flag if the user wants to export the data to json file else the data will be exported to a text file .
If the user enter's the file to which he wants to export , it will check entered file name's extension , if it is .json it will call WriteToJsonFile method else WriteToTextFile is called.
https://user-images.githubusercontent.com/44670961/136663334-74a0a7d2-02f2-48c9-91d7-4e07c8dee8d7.mp4

Thankyou @souvikinator for giving me opportunity to do this task . I was aware of the syntax but not completely implemented anything . This helped me practise what I have learned. 🙏🏻


python310Packages.plugwise: 0.19.0 -> 0.19.0

Description of changes
https://github.com/plugwise/python-plugwise/releases/tag/v0.19.0

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 176806 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.plugwise
python310Packages.plugwise
python39Packages.plugwise


Still opens a window with ctrl+alt+t even after uninstalling.

I uninstalled the deb but even after that it still opens the todoist window when ctrl+alt+t is pressed
what kind of sorcery is this? :)

Hi @NinjaTurtle007,
Uninstalling the deb package isn't closing the app. The app is definitely still running.
You can find it with ps -A | grep -i todoist and then kill it by PID.
The app actually has to be in your tray where you can close it. If it's not there then it's another bug.

yup, that worked, thank you!


OOTB log4j-config.xml and gateway-config.xml improvements are needed (does not document MaxBackupIndex, etc)

Our OOTB log4j-config.xml file needs some improvements:

[x] remove obsolete definition: appender EventsFile.
[x] document MaxBackupIndex in comments in the appender definitions using RollingFileAppender (as pointed out in ticket#68)
[x] in order to facilitate use of Identity Logging, we should add the  element to the  element inside  in our OOTB gateway-config.xml file:

\<security>
...
   <realm>
     <name>demo</name>
     <description>Sample realm for file-based authentication</description>

     <!-- Include user name in log messages and make visible in JMX beans -->
     <user-principal-class>
        org.kaazing.gateway.security.auth.config.UserConfig
     </user-principal-class>

     <authentication>
       <http-challenge-scheme>Application Basic</http-challenge-scheme>
...

(see also issue #773)

@sbadugu @robinzimmermann Robin wants to make sure we bump the minor release version (2nd version digit) for this since if customers uptake the updated OOTB log4j-config.xml they will see a change in behavior (no more access.log and proxy.log files generated, up to 2 error.log.x files up to 50MB each instead of a single one up to 10MB).

Closing, fixed by PR https://github.com/kaazing/gateway/issues/779


BUG: Milvus docker quits after idling

When starting with docker-compose, the Milvus dockers starts well and is functional for hours. But if let to idle for a few hours, the docker quits, with a LOT of messages. What seems relevant is
[2022/11/27 13:41:02.401 +00:00] [WARN] [sessionutil/session_util.go:389] ["session keepalive channel closed"]
[2022/11/27 13:41:02.401 +00:00] [INFO] [server/rocksmq_impl.go:315] ["Rocksmq Info"] [topic=by-dev-rootcoord-dml_5] ["consumer num"=0] ["min position group names"=] ["min positions"=-1] ["page sum"=0] ["last page size"=319802]
[2022/11/27 13:41:02.401 +00:00] [WARN] [sessionutil/session_util.go:624] ["connection lost detected, shuting down"]

Note sure if this is a feature or a bug. Regardless, everything works if I restart. So one solution is to keep it alive (auto restart) in docker-compose file.

duplicated in #8. Closing


switched direct requests call to use of session instance

Coverage increased (+0.02%) to 92.434% when pulling 9a8f012d7a794a0bb47cd3095232185687f87716 on guyzmo:feature/requests_session into 4bbc50e9ce736f78d45da06d600cafc9d7f6d95e on unfoldingWord-dev:master.

This patch is necessary for unit tests of guyzmo/git-repo, as the betamax library hijacks a requests session to record and replay HTTP calls.
Basically, what is needed is to be able to use and extract:
gogs = gogs_client.GogsApi(url)
do_stuff_with_session(gogs._requestor.session)

A cleaner approach (to avoid exposing private API), would be to change the entry point object:
session = requests.Session()
gogs = gogs_client(url, session=session)
do_stuff_with_session(session)

but first way (which I currently implemented so it's frictionless) is good enough.

I like the suggestion; I'm a big fan of injection!
However, in order to expose the session object in a clean way, doesn't the constructor of the GogsApi object need to take a (perferably optional) session argument to pass along to RelativeHttpRequestor?

Coverage increased (+0.02%) to 92.434% when pulling 7a6378d4ce954ecd5f70a9d4624156ded42369da on guyzmo:feature/requests_session into 4bbc50e9ce736f78d45da06d600cafc9d7f6d95e on unfoldingWord-dev:master.

Coverage increased (+0.02%) to 92.434% when pulling c88f31771f136150fa1096809b429a6ad8b8546c on guyzmo:feature/requests_session into 4bbc50e9ce736f78d45da06d600cafc9d7f6d95e on unfoldingWord-dev:master.

LGTM


ROCm installation fails on Debian buster/sid

On Debian/testing, apt install rocm-dkms fails with
Error! Bad return status for module build on kernel: 4.18.0-3-amd64 (amd64)
Consult /var/lib/dkms/amdgpu/1.9-307/build/make.log for more information.
dpkg: error processing package rock-dkms (--configure):
installed rock-dkms package post-installation script subprocess returned error exit status 10
I attach the file
make.log

Works also with kernel 4.19.5

ROCm is not officially supported on Debian. However, as @valeriob01 notes, you should be able to use the upstream kernel. To do that, do not install the rocm-dkms module. Instead, install just the rocm-dev module and follow the directions in that link to set up your udev rules.

ROCm is not officially supported on Debian. However, as @valeriob01 notes, you should be able to use the upstream kernel. To do that, do not install the rocm-dkms module. Instead, install just the rocm-dev module and follow the directions in that link to set up your udev rules.

I have followed the standard procedure: installed rocm-dkms and libnuma-dev.

@valeriob01 That's somewhat surprising. I guess what might be happening is that your rock-dkms installation silently fails but all of the other packages work correctly. At that point, the upstream amdgpu and amdkfd drivers will still be installed, and all your user-level software will work with them.
I would wager if you run dkms status, you will find that the amdgpu/1.9-307 package will not be listed as "installed".
@kochd Yes, that error is because you are trying to use a kernel newer than 4.15, which our rock-dkms package does not support. If you are running a newer kernel (as noted above) you can likely skip this step. You will lose some of our features that have not been upstreamed yet, but our user-level ROCm software should work.

@valeriob01 That's somewhat surprising. I guess what might be happening is that your rock-dkms installation silently fails but all of the other packages work correctly. At that point, the upstream amdgpu and amdkfd drivers will still be installed, and all your user-level software will work with them.
I would wager if you run dkms status, you will find that the amdgpu/1.9-307 package will not be listed as "installed".

dkms status  shows
amdgpu/1.9-307: added
So what to do at this point ?

@valeriob01 That means the DKMS driver provided by rock-dkms was added, but the build failed and it was not installed. As such, you are using your upstream 4.19 driver. That's what I expected. I don't think that's a problem, since you've said ROCm user-level tools are working for you. Things like this are one of the main reasons we worked to upstream our driver. :)
That said, there are some features that have not been upstreamed yet. If you want those features, you may need to either wait until our rock-dkms module supports newer kernels, or you may need to downgrade your kernel to 4.15.

The program run fine, maybe the performance is inferior.

ROCm is not officially supported on Debian. However, as @valeriob01 notes, you should be able to use the upstream kernel. To do that, do not install the rocm-dkms module. Instead, install just the rocm-dev module and follow the directions in that link to set up your udev rules.

Ah, indeed, that works. Thanks a lot!
(Next thing on my agenda: Try to find out why GEGL still doesn't enable image support.)

I tried modifying the dkms code for debian buster 4.19, but when starting X I get an error message of AMDGPU Flip failed.  Changes at https://github.com/Infro/ROCK-Kernel-Driver/commit/864174b9ead77cbb596baa422a175fa8525b76ae

Yes, debian with kernel 4.19.x (latest strech-updates) with latest ROCm 2.0.1 not work if i install with  rocm-dkms.
But after install with rocm-dkms - all is works!
And not forget to modified os-release file to ubuntu before run update-initramfs -u
Works rocminfo and etc.
But after reboot - not work, just reboot after several seconds after boot, and it is also in recover mode.
It is latest screen before reboot.

If not use rocm-dkms - works after reboot.
But what different in this 2 way?

Thank you all for the verification and confirming that issue is no more observed.
I am closing this now.
Request to open a new issue, if any, in future.
Thank you.

Thank you all for the verification and confirming that issue is no more observed.
I am closing this now.
Request to open a new issue, if any, in future.
Thank you.

the reason rocm does not install on Debian 10/Buster is a dependency on libpython3.8. I manually installed python3.8 but apt does not check /usr/local/lib to find the dependency exists there already for libpython3.8

@commandline-be Had the same problem when trying to install rocm-dev as described in the installation nodes  You have to choose version rocm-dev in version 3.7 on Debian buster (for all later versions rocm-gdb has the dependecy on libpython3.8) You can do that by requiring a specific version in /etc/apt/sources.list.d/rocm.list:
deb [arch=amd64] http://repo.radeon.com/rocm/apt/3.7 xenial main

It probably also works to install all packages that rocm-dev depends on despite rocm-gdb for later versions. Have not really checked that.


[R-package] remove blank lines and not-really-comments from .Rbuildignore

I saw this really interesting discussion on the r-pkg-devel mailing list: https://stat.ethz.ch/pipermail/r-package-devel/2020q3/005894.html
Basically, the .Rbuildignore file does not support comments. Lines that start with # will be evaluated as patterns that could match a file.
It also does not skip blank lines, so having blank lines just increases the time it takes to build a package.
This PR should slightly reduce the build time for the R package, and should avoid the unlikely but not impossible case where one of the "commented" lines matches and ignores a file that should not be ignored.
Since I'm touching this file, I also took the opportunity to rearrange it so that it is in alphabetical order (ignoring non-alphanumeric characters).

Maybe blank line after cran-comments.md in #3298 caused problems?

Maybe blank line after cran-comments.md in #3298 caused problems?

ooooo maybe! now that I know the exact R code that checks .Rbuildignore, I can probably come back in a follow-up PR and populate that file correctly. Might allow us to remove some rm statements from https://github.com/microsoft/LightGBM/blob/1804fd12ea240af438a8c2d6c67d6a0f9bdf4c5e/build-cran-package.sh#L33-L35


ISO didn't recognized the HDD

Rancher Version:
v0.8.1
OS and where are the hosts located? (cloud, bare metal, etc):
Cloud (KeyWeb: https://www.keyweb.de/de/)
Issue:
The IT team of KeyWeb wasn't able to install RancherOS from ISO because the ISO didn't recognized the HDD.

@mrmunch can you please tell us more information? how was this install done? what commands where run, and what was the output...


Fix honest shrinking by keeping the last point of adversary schedules

This fixes the shrinking for the test failure I encountered. But I could not advice if it affects other things without further familiarizing with the code. I'm tagging @Niols for review.

Merged and squashed this to 38b866e.


Glossary term with long FQN can be used for tagging but fails in the client

If we keep creating terms with long names as children, we can end up with a rather long glossary term.
The issue is:

tagLabel is 128 characters https://github.com/open-metadata/OpenMetadata/blob/main/openmetadata-spec/src/main/resources/json/schema/type/tagLabel.json#L11
We can tag from the UI with terms with FQN longer than 128
The validation only happens when picking up the data from the client, which fails

>>> metadata.get_by_name(entity=Table, fqn="sample_data.ecommerce_db.shopify.raw_customer",fields=["tags"])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/pmbrull/projects/OpenMetadata/venv/lib/python3.9/site-packages/metadata/ingestion/ometa/ometa_api.py", line 590, in get_by_name
    return self._get(
  File "/Users/pmbrull/projects/OpenMetadata/venv/lib/python3.9/site-packages/metadata/ingestion/ometa/ometa_api.py", line 623, in _get
    return entity(**resp)
  File "pydantic/main.py", line 342, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for Table
columns -> 0 -> tags -> 0 -> tagFQN -> __root__
  ensure this value has at most 128 characters (type=value_error.any_str.max_length; limit_value=128)

The backend/UI should verify if we are using a tag that follows the spec

from https://openmetadata.slack.com/archives/C02B6955S4S/p1681307084042099

yes this will work in fqnHash

@harshach to be closed along with size increases for names and fqnHash.


How to enable performance tracing on moleculer-sentry?

Hi, I have tried to configure moleculer-sentry on my moleculer api service. These are what I added so far, but the performance tracing is still not showing on my dashboard.
// Sentry config
dsn: Config.sentry.dsn,
options: {
  environment: env,
  integrations: [
    new Sentry.Integrations.Http({ tracing: true }),
  ],
  tracesSampleRate: 1.0
},

Am I missing something? Also my dashboard is showing that the sdk is outdated. Will there be future update on this plugin? Thank you!

Tracking is shown on my dashboard, this is my config.
moleculer.config.js
    tracing: {
        enabled: true,
        exporter: [
            "Console"
            {
                type: "Event",
                options: {
                    eventName: "$tracing.spans",
                    sendStartSpan: false,
                    sendFinishSpan: true,
                    broadcast: false,
                    groups: null,
                    interval: 5,
                    spanConverter: null,
                    defaultTags: null
                }
            }
        ]
    },


Meeting times are not in the calendar

Currently, the calendar is showing as empty

Thanks Rob, looks like I pointed this to an absolute url instead of the redirect. Pushing a fix shortly.

Thanks Rob, looks like I pointed this to an absolute url instead of the redirect. Pushing a fix shortly.


move malfeasance proof validation outside db transaction

Motivation
Closes #4556
Changes
rely on mutex to atomically save data and malfeasance proof

bors try

bors try

bors merge


pomodoro-gtk: init at 1.4.1

Description of changes

Closes https://github.com/NixOS/nixpkgs/issues/299041
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofBorg build

Oops

Result of nixpkgs-review pr 302852 run on aarch64-linux 1

1 package built:

pomodoro-gtk

aarch64-darwin build is stuck for two days. It should skip the same way as x86_64-darwin:
https://github.com/NixOS/nixpkgs/blob/1042fd8b148a9105f3c0aca3a6177fd1d9360ba5/pkgs/development/interpreters/spidermonkey/common.nix#L195


Regarding - Decoders

Hello @Zzh2000 @pengsongyou,
First and foremost, thanks a lot for your NICE project :)
I have a question regarding the decoders,

Could you provide any further instruction/code for the Point Cloud Encoder-Decoder network that is trained
for obtaining the pretrained decoder part?

[I can't find/figure out] the part of the code where you fixed the weights for Mid-&Fine-level decoders, as given in the paper.

Any pointers will be helpful.

I am sorry if these questions are naive or if the answer already appears on the git but I could not find a clear solution.
Thank you very much.

Hi,
thanks for your interest in our work!

The Point Cloud Encoder-Decoder network is modified upon the ConvOnet, you can check https://github.com/autonomousvision/convolutional_occupancy_networks and our supplementary for more details.
There is no explicit code for fixing the decoder weights. We fix the weight just by not adding it to the optimizer.

Best,
Zihan


menulibre: init at 2.2.3

Description of changes
MenuLibre is an advanced menu editor that provides modern features in a clean, easy-to-use interface.
Homepage: https://bluesabre.org/projects/menulibre
Repo: https://github.com/bluesabre/menulibre
Fixes: #84652
Currently is does not seem to fill all icons for categories correctly, but that also happens in the flatpak version.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 264513 run on x86_64-linux 1

2 packages built:

menulibre
menulibre.dist

Result of nixpkgs-review pr 264513 run on x86_64-linux 1

2 packages built:

menulibre
menulibre.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2850

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1393

Updated the derivation to only use a single call substituteInPlace on the setup script.
The data_dir still works the same. The .desktop file now only has Exec=menulibre instead of Exec=/nix/store/*/bin/menulibre, which should be fine, right? There's many other packages with .desktop files like this.

Result of nixpkgs-review pr 264513 run on x86_64-linux 1

2 packages built:

menulibre
menulibre.dist


Revised both linux script.

I added linux binary "aaptlinux", since most distro didn't provide android build tools and some users don't want spending his time searching "aapt".
I added switch, if aapt and apksigner packages is not present, script will use aaptlinux file and run java -jar apksigner.jar ... instead.
I removed unused space in update-files.bat.
I tested it on all 3 major distros(Arch, Fedora and OpenSUSE) and Termux, and they all worked great.

This is pretty cool - it works like the Windows version now ^^


Use local model loader as submodule to cut dependency volume in half

Description
Just a proposal, probably not necessary.
I came up with this, because i was debugging some docker related issues (unexpected exits on some hardware).
But as of now, it might not be some cpu-flag specific compilations on github runners.
So this is for reference and discussion if there are any benefits.
It does something good: It reduces the interference of providers loaded on startup. (Maybe it's too late, but it seems e.g. sentence transformers is doing some stuff even if not used, only because the agent provider is registered.)
Current state: Still docker-testing both variants. Default-full-blown and with modules.
Note: Given we want the submodule (like autoGPTQ does with llama and triton) - it is described as "runtime addon dependencies" in poetry - we can still build any wanted version with docker: small (roundabout 1.ish GB) and full (roundabout 2.5ish GB).
PS: Such dependency updates always go by poetry lock --no-update to prevent unwanted bugs/changes in this fast-moving space. Keeps the lockfile changes still readable also.
Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of changes

Changes visible to users:

[ ] Bug fix (prefix: fix - non-breaking change which fixes an issue)
[ ] New feature (prefix: feat - non-breaking change which adds functionality)
[ ] Breaking change (prefix: feat!! or fix!! - fix or feature that would cause existing functionality to not work as expected)

Internal changes:

[ ] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[ ] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)
[ ] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Checklist

[ ] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[ ] My change works!

refs https://github.com/Josh-XT/AGiXT/issues/462

refs https://github.com/Josh-XT/AGiXT/issues/462

@Josh-XT I faced weird docker errors, specifically exited with 132 errors. After hours of debugging, i can guess its about the sentence transformers.
Doing a lightweight build without the additional deps needed for local runs makes it run for me.
Background: Docker just uses the CPU directly. My CPU seems too new, so some cpu features have changed. The provider deps rely on some instructions forcing my docker to exit. Reducing CPU-dependent libs in those builds would help a lot

Sentence transformers is our primary embedding method with Chroma

Sentence transformers is our primary embedding method with Chroma

So what is supposed to happen when the dependencies are changed like proposed?


QueryInvoke implementation

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (a2233eb) 61.41% compared to head (3b6e279) 63.24%.

Files
Patch %
Lines

internal/tezos/exec_query.go
95.45%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #29      +/-   ##
==========================================
+ Coverage   61.41%   63.24%   +1.83%
==========================================
  Files          22       22
  Lines         863      906      +43
==========================================
+ Hits          530      573      +43
+ Misses        327      326       -1
- Partials        6        7       +1

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


Fix VS crash when error points to a missing file

Fix #2816 VS crash when error points to a missing file
Here's the fix in action:
---------------------------
Visual Studio - Python support
---------------------------
The document cannot be opened. It has been renamed, deleted or moved.
---------------------------
OK
---------------------------

Should I have just caught everything that's not a critical exception instead?

Maybe there's a narrower place to handle that error inside the function?
Since this crashes, I'd add a handler that uses the ReportUnhandledException extension method to display the dialog that lets people copy the error for us. But keep the specific message.

VS was catching it and putting up the activity log error message, so not technically a crash.
Trying it again I found that the behavior was slightly different based on whether you delete the file from project or from file explorer, so I adjusted the fix for that.

👍


In tsx/jsx, some local define 'Component' are not in the completion list

Bug Report

🔎 Search Terms
react, intellisense
🕗 Version & Regression Information
version: 4.2.3
I just test in recent vscode and the playground link.
⏯ Playground Link
Playground link with relevant code
💻 Code

import React, { ReactElement } from 'react';
import {InputNumber as RawInputNumber} from 'antd';

function Test2()
{
    var a = [/*a*/];
    var b = <div>
        /*b*/
    </div>;
    var c = <>
        /*c*/
    </>
}

function InputNumber():ReactElement<any,any>|null
{
    return null;
}

class ClassComponent extends React.Component
{
    render()
    {
        return null;
    }
}

function FunctionComponent(props: any): ReactElement<any, any> | null
{
	return null;
};

Please try to input the <InputNumber/>, <ClassComponent/> and <FunctionComponent/> at comment a,b and c.
🙁 Actual behavior
In the comment a: all things are correct.
In the comment b and c:
When you start to input <, the completion list doesn't contains InputNumber, ClassComponent and FunctionComponent. But RawInputNumber(the import one) is in the list.
And in vscode, it will be worse: it tries to import {InputNumber} from 'antd', and make the local defined InputNumber conflit.
🙂 Expected behavior
Make the local define component in the completion when input <

This happens due to the parser being unable to recover from the unmatched < in those positions. This might be tricky.

ok. I know what you mean. When input < all code after it will be invalid.
But I find that { and ( will not cause this problem. Maybe you should improve this.
Or I think like the auto complete the close brace function: when input character " ( [ it will auto close it. You could auto generate <></> and insert two cursor between the <>, when input the <.(Of course if I press backspace, it should delete all)


fix memory leak in var expasion

🌈 minishell$ $USER
expansion: vscode
🌈 minishell$ exit
expansion: exit
exit

🌈 minishell$ <<OF
> ^C
🌈 minishell$ echo $?
expansion: echo 130
130
🌈 minishell$ exit
expansion: exit
exit

==3320== 7 bytes in 1 blocks are definitely lost in loss record 2 of 79
==3320==    at 0x48407B4: malloc (vg_replace_malloc.c:381)
==3320==    by 0x10BB25: concat_strings (parser_var_expansion_utils_test.c:79)
==3320==    by 0x10BBE7: join_str_r (parser_var_expansion_utils_test.c:126)
==3320==    by 0x10B84E: replace_var_with_val (parser_var_expansion_test.c:166)
==3320==    by 0x10B92E: expand_variables (parser_var_expansion_test.c:208)
==3320==    by 0x10B54E: parse_tokens (parser_test.c:37)
==3320==    by 0x109760: main (main_test.c:70)`

mh, no memory leaks whatsoever here...? did I change sth during signaling?
I'll implement the current signal processing anew here and check for leaks every step on the way


fix(Authentification): un mot de passe vide ne fait pas planter le login

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


Implement tty-dectorator for test errors, plug-in decorators and formatter into reporters

[ ] We should pass user-provided errorDecorator to the format, currently it's called formatter in the runner and reporter
[ ] If decorator is not provided fallback to the tty or plain-text decorators (depends on the type of the output stream)
[ ] Put decorators into the decorators dir in the sources
[ ] Consider moving src/test-error content to the src/reporters/errors
[ ] Rename src/test-error/index.js to the src/reporters/errors/format.js
[ ] Test error diffs and viewportWidth since we have a wordwrap for text (https://github.com/superroma/testcafe-phoenix/blob/master/src/reporters/base.js#L140). Seems like we will need more complicated logic for the errors to consider indents.

And we should add special comment (see: https://github.com/superroma/testcafe-phoenix/blob/master/src/runner/test-run/command.js#L1) to all files which will be used by the client as well (e.g. type.js)

Closed via #45 and #63


Fix CLI readme

add missing code to example 'final CLI application' so that it compiles
removed slice(2) from process.argv
removed no longer correct explanation about slicing process.argv

@wmaurer - thank you very much for helping us keep the docs up-to-date :) I'll merge as soon as CI succeeds.


nuxt3 uses npm run build to package, sending pictures, word and other file types more than 10KB will report 500 errors

Environment
Operating System: Liunx
Nuxt: 3.2.2;
Nuxi: 3.2.2
Nitro: 2.2.3
Node: 18.16.0
npm:  9.5.1
Builder: vite
Reproduction
(https://github.com/taishuai110/nuxt3-error/blob/main/微信图片_20230708191820.png)
(https://github.com/taishuai110/nuxt3-error/blob/main/3.png)
(https://github.com/taishuai110/nuxt3-error/blob/main/2.png)
Describe the bug
After I package the project, I use useFetch to send FromData requests. Files smaller than 10kb can be sent to the server, but files larger than 10kb cannot be sent. This is not the case with the development environment and only happens after you have officially packaged it, whether you deploy it to the server or not.
Additional context
No response
Logs
[nuxt] [request error] [unhandled] [500] fetch failed (API Url)
0|NuxtAppName  |   at sendProxy (./node_modules/h3/dist/index.mjs:468:20)
0|NuxtAppName  |   at Object.handler (./node_modules/h3/dist/index.mjs:1196:19)
0|NuxtAppName  |   at Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1271:7)

I found that degrading node to version 16.15.0 would solve the problem, although it would solve the problem, I still want to know why nuxt3 needs to downgrade node to version 16 to use some of the features, is nuxt3 not yet perfect or node18 is not stable enough?

Would you see if you can reproduce this with pure Nitro and raise an issue at https://github.com/unjs/nitro ? 🙏

@danielroe
What do you mean, I tried to change my node18.16.0 to 16.18.0 so I could send large files with fromData, but when I did, the images I sent and the images I responded to were not rendered, as if they were corrupted.

@danielroe Give me a break. I looked at your warehouse, and I couldn't understand it. There's no entry app.vue. Can I provide my github repository to you, can you download it and help me have a look


Merge prTesting_201904211034 branch to master branch

Docs Build status updates of commit 4f07fa3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Base installation fail

Ubuntu 16.04
Meteor <IP_ADDRESS>
As per installation instructions, run npm install
npm install
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
extract:oauth-sign → gunz ▐ ╢████████████████████████████████████░░░░░░░░░░░░░╟
Killed
... any ideas??

I have the same OS, same Meteor version and had some similar issues too. Now it works fine.
I went back to the history of my commands in the Terminal, and found out that after this first failure, all what I have done is the following ( first make sure you're in base directory ):
1: npm update
2: meteor update
3: meteor update dburles:factory (I think this one could be skipped, but I've done it)
4: meteor  => it worked now just fine.
Hope this helps.

Thanks so much for the response. To get around this:

meteor update
sudo npm update

Make sure to use sudo for privileged access to node files.

While there are still some warnings Base does start OK.
Warnings/Errors still present include:
UNMET PEER DEPENDENCY<EMAIL_ADDRESS><EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>

UNMETPEER DEPENDENCY<EMAIL_ADDRESS>
@notgoodwithpowertools NPM 3+ does not automatically install peerDependencies. Because of this, eslint-plugin-jsx-a11y was not installed. To fix this you only need to install eslint-plugin-jsx-a11y.

Thanks for the response. Sorry to be vague but tried the npm install eslint-plugin-jsx-a11y --save
... but it didn't seem to install leaving the following warning...
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
Should I worry about this?

@notgoodwithpowertools this should be corrected in Base 4.2.0.


AngularJS => Angular migration and ng-annotate

🚀 Feature request
Description
Pretty much these other issues explain the motivations for my feature request: https://github.com/angular/angular-cli/issues/6873 by @yjaaidi and https://github.com/angular/angular-cli/issues/3722 by @Itrulia
I'm migrating an app from AngularJs to Angular, and even when building for production I'm needing to specify --optimization=false because otherwise, the AngularJs parts of my app won't work. The reason is when using Angular CLI there is no way of including ng-annotate as part of the pipeline for the AngularJs bits.
What is the 2021 way of using ng-annotate for hybrid applications?
Thanks.
Describe the solution you'd like
I would like a "plugins" section where I could specify "ng-annotate" and only for files that match a regex (the AngularJs files).
Describe alternatives you've considered
I've considered:

Ejecting the configuration and not using ng-cli. I don't like this solution as I want to use Angular CLI and reduce customizations (so upcoming upgrades are smoother).
Running ng-annotate on each of the Angular files by hand, and permanently replacing the original files. But it's rather involved, I'd need to write a script that:

Removes the imports from the top of my files (because ng-annotate doesn't like "imports/exports" in non-module files).
Runs ng-annotate in each one, redirecting the output to a file, then swapping the files.

Continuing to use the non-optimized version of my product in production. My company's product is quite large, and it is taking several seconds to download and bootstrap, so this is exactly what I want to avoid.
Using a custom webpack config prepended to ng-cli's one. I found it here.

So far it looks like number 4 is what I'm going to try, otherwise doing number 2. Unless there is already a better solution I have not considered.

After looking around, I found the best solution for me was to use babel-plugin-angularjs-annotate, which does something similar to what I mentioned before in option 2, but better:

Create a new project
Install babel and babel-plugin-angularjs-annotate
Execute npx babel src -d output

That's it, it will take the files from src, add the annotations, and put the result in the folder output.
For others needing the complete solution, this is what I exeucted:

mkdir babel-setup-with-babel-cli && cd babel-setup-with-babel-cli
npm init -y
npm install -D babel-cli babel-plugin-angularjs-annotate
Add this to .babelrc:

{
  "presets": [],
  "plugins": [ "angularjs-annotate" ]
}

npx babel src -d build

Hi,
You can use 3rd party solutions such as https://github.com/manfredsteyer/ngx-build-plus and https://www.npmjs.com/package/@angular-builders/custom-webpack to extend the Angular CLI and add custom Babel and Webpack plugins in the build pipeline.
While, we extending the CLI is allowed, this is not supported by the Angular tooling team.

Hi,
You can use 3rd party solutions such as https://github.com/manfredsteyer/ngx-build-plus and https://www.npmjs.com/package/@angular-builders/custom-webpack to extend the Angular CLI and add custom Babel and Webpack plugins in the build pipeline.
While, we extending the CLI is allowed, this is not supported by the Angular tooling team.


Logs:
395fcae9_K8sUpdates_Updating_Cilium_stable_to_master.zip

Note that the app pods are in CrashLoopBackOff:
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath			Type		Reason			Message
  ---------	--------	-----	----			-------------			--------	------			-------
  5m		5m		1	default-scheduler					Normal		Scheduled		Successfully assigned app2-2809035625-fkcb0 to k8s1
  5m		5m		1	kubelet, k8s1						Normal		SuccessfulMountVolume	MountVolume.SetUp succeeded for volume "app2-account-token-g1wv6"
  5m		5m		1	kubelet, k8s1		spec.containers{app-frontend}	Warning		Failed			Error: failed to start container "app-frontend": Error response from daemon: {"message":"cannot join network of a non running container: 7ef20977854990da7179fc0539b9b0c2061be8314a19301f2c82c7092038f6f8"}
  4m		4m		1	kubelet, k8s1		spec.containers{app-frontend}	Warning		Failed			Error: failed to start container "app-frontend": Error response from daemon: {"message":"cannot join network of a non running container: 12361b8f1d72267da1756928f7a930a7a2a9a7a7b4675239d3fff39f0011fdbd"}
  4m		4m		1	kubelet, k8s1		spec.containers{app-frontend}	Warning		Failed			Error: failed to start container "app-frontend": Error response from daemon: {"message":"cannot join network of a non running container: 743398eeae6d8303f0a27227a1ec3d8acd70020378d2091414105b5753e26ca1"}
  3m		3m		1	kubelet, k8s1		spec.containers{app-frontend}	Warning		Failed			Error: failed to start container "app-frontend": Error response from daemon: {"message":"cannot join network of a non running container: 9a9f316e05c6bfb2f0140b0c8c5e3204f8778e3e03639d13b7511fd8a3573b5c"}
  3m		3m		1	kubelet, k8s1		spec.containers{app-frontend}	Warning		Failed			Error: failed to start container "app-frontend": Error response from daemon: {"message":"cannot join network of a non running container: b819e979ad36d4f9ff5d2e3dec2f7c522f1a77227c1fbea0657b4c4003911a13"}
  5m		1m		6	kubelet, k8s1		spec.containers{app-frontend}	Normal		Pulling			pulling image "docker.io/cilium/demo-client"
  1m		1m		1	kubelet, k8s1		spec.containers{app-frontend}	Warning		Failed			Error: failed to start container "app-frontend": Error response from daemon: {"message":"cannot join network of a non running container: 930b195519aeed97f9ff723abc7e23a0ba2428657b2f0aa69c5edc6b369687b5"}
  5m		1m		6	kubelet, k8s1		spec.containers{app-frontend}	Normal		Pulled			Successfully pulled image "docker.io/cilium/demo-client"
  5m		1m		6	kubelet, k8s1		spec.containers{app-frontend}	Normal		Created			Created container
  5m		1m		32	kubelet, k8s1						Normal		SandboxChanged		Pod sandbox changed, it will be killed and re-created.
  4m		12s		14	kubelet, k8s1		spec.containers{app-frontend}	Warning		BackOff			Back-off restarting failed container
  5m		12s		53	kubelet, k8s1						Warning		FailedSync		Error syncing pod

cilium-wrlx4 is the cilium pod which is on the same node (k8s1) as the app pods, but Cilium isn't managing them. The logs for cilium-wrlx4 are riddled with messages like the following:
2018-07-31T10:32:30.611639134Z level=debug msg="Waiting for endpoint representing container to appear" containerID=fcbf41b206 maxRetry=20 retry=8 subsys=workload-watcher willRetry=true
2018-07-31T10:32:30.6593194Z level=debug msg="Queueing container event" containerID=ea6991ee87 event=stop subsys=workload-watcher
2018-07-31T10:32:30.783370255Z level=debug msg="Unable to inspect container after container create event" containerID=a3df933a2e error="unable to inspect container 'a3df933a2e9fe5b8e4b52e407af819f2bd11b603900c999698bdd6baa3f6ddca': Error: No such container: a3df933a2e9fe5b8e4b52e407af819f2bd11b603900c999698bdd6baa3f6ddca" maxRetry=20 retry=5 subsys=workload-watcher willRetry=true

@rlenglet and I noted while doing paired debugging that we are dumping and parsing the BPF LB maps, which use golang's unsafe pointers. Thus, we may be improperly using these pointers and corrupting memory.
We see that right before we try to allocate an identity for the prometheus pod, we sync the BPF LBMaps, which involve dumping:
2018-07-31T10:31:00.963130361Z level=info msg="Syncing BPF LBMaps with daemon's LB maps..."
2018-07-31T10:31:00.96314726Z level=debug msg="parsing service mapping" bpfMapKey="<IP_ADDRESS>:9090" bpfMapValue="<IP_ADDRESS>:9090 (2)"
2018-07-31T10:31:00.963150116Z level=debug msg="converting ServiceKey and ServiceValue to frontend and backend" obj="<IP_ADDRESS>:9090 (2)" serviceID="<IP_ADDRESS>:9090"
2018-07-31T10:31:00.963152342Z level=debug msg="creating L3n4Addr for ServiceKey" serviceID="<IP_ADDRESS>:9090"
2018-07-31T10:31:00.963154324Z level=debug msg="created new L3n4Addr" ipAddr="{<IP_ADDRESS> {TCP 9090}}"
2018-07-31T10:31:00.963156173Z level=debug msg="created new LBBackend" backend="{{<IP_ADDRESS> {TCP 9090}} 0}"
2018-07-31T10:31:00.963158008Z level=debug msg="adding frontend and backend to SVCMap" backend="<IP_ADDRESS>:9090, weight: 0" backendIndex=1 frontend="<IP_ADDRESS>:9090"
2018-07-31T10:31:00.963165186Z level=debug msg="parsing service mapping" bpfMapKey="<IP_ADDRESS>:443" bpfMapValue="<IP_ADDRESS>:6443 (9)"

The next log shows the allocated identity for the endpoint. The labels are intact :
2018-07-31T10:31:00.963167409Z level=debug msg="Resolved identity" identity=33870 identityLabels="k8s:app=prometheus,k8s:component=core,k8s:io.cilium.k8s.policy.serviceaccount=prometheus-k8s,k8s:io.kubernetes.pod.namespace=prometheus" isNew=false

We perform more LBMap dumping / parsing-related operations after this:
2018-07-31T10:31:00.96399917Z level=debug msg="converting ServiceKey and ServiceValue to frontend and backend" obj="<IP_ADDRESS>:6443 (9)" serviceID="<IP_ADDRESS>:443"
2018-07-31T10:31:00.964001489Z level=debug msg="creating L3n4Addr for ServiceKey" serviceID="<IP_ADDRESS>:443"
2018-07-31T10:31:00.964003427Z level=debug msg="created new L3n4Addr" ipAddr="{<IP_ADDRESS> {TCP 443}}"
2018-07-31T10:31:00.964007122Z level=debug msg="created new LBBackend" backend="{{<IP_ADDRESS> {TCP 6443}} 0}"
2018-07-31T10:31:00.964009144Z level=debug msg="adding frontend and backend to SVCMap" backend="<IP_ADDRESS>:6443, weight: 0" backendIndex=1 frontend="<IP_ADDRESS>:443"
2018-07-31T10:31:00.964011176Z level=debug msg="parsing BPF revNAT mapping" bpfMapKey=2 bpfMapValue="<IP_ADDRESS>:9090"
2018-07-31T10:31:00.964013051Z level=debug msg="created new L3n4Addr" ipAddr="{<IP_ADDRESS> {TCP 9090}}"
2018-07-31T10:31:00.964014926Z level=debug msg="parsing BPF revNAT mapping" bpfMapKey=9 bpfMapValue="<IP_ADDRESS>:443"
2018-07-31T10:31:00.964016814Z level=debug msg="created new L3n4Addr" ipAddr="{<IP_ADDRESS> {TCP 443}}"
2018-07-31T10:31:00.964018668Z level=debug msg="iterating over services read from BPF LB Map and seeing if they have the same ID set in the KV store"
2018-07-31T10:31:00.964726467Z level=debug msg="Resolving service" l3n4Addr="{IP:<IP_ADDRESS> L4Addr:{Protocol:TCP Port:9090}}"
2018-07-31T10:31:00.964733592Z level=debug msg="Updated controller" name="sync-identity-to-k8s-pod (31680)" subsys=controller uuid=d1c787ab-94ac-11e8-855e-08002707f0ef
2018-07-31T10:31:00.964735967Z level=debug msg="Updated controller" name="sync-IPv4-identity-mapping (31680)" subsys=controller uuid=d1c8214b-94ac-11e8-855e-08002707f0ef
2018-07-31T10:31:00.964738038Z level=debug msg="Updated controller" name="sync-IPv6-identity-mapping (31680)" subsys=controller uuid=d1c8224b-94ac-11e8-855e-08002707f0ef

Now, the labels for the endpoint are corrupted:
2018-07-31T10:31:00.964740114Z level=info msg="Identity of endpoint changed" containerID=1864f0935d endpointID=31680 identity=33870 identityLabels="k8s:app=prometheus,k8s:component=core,k8s:io.kubernetes.pod.namespace=prometheus,k8s:\xda\x02\x00\x00\xda\x02\x00\x00m.k8s.policy.serviceaccount=prometheus-k8s" ipv4=<IP_ADDRESS> ipv6="f00d::a0a:0:0:7bc0" k8sPodName=":" oldIdentity=33870 policyRevision=0

@rlenglet and I also checked to see if there was a mismatch between the BPF Map definitions in the BPF code vs. in the cilium-agent userspace code, but could not find any for the IPv4 / IPv6 RevNat or LBMaps.

@joestringer faced a similar issue here:
https://github.com/cilium/cilium/issues/4886#issuecomment-407815290

\xda\x02\x00\x00\xda\x02\x00\x00 translates to 55810 or 730, but we couldn't find anything using those numbers in the logs :(

The log message iterating over services read from BPF LB Map and seeing if they have the same ID set in the KV store occurs right after all of the maps are dumped:
https://github.com/cilium/cilium/blob/b22cc7c90cc7abda785deb36378139a2fe4c3c3f/daemon/loadbalancer.go#L535-L561
I am highly suspicious that the Dump function is corrupting memory in userspace.

One point to keep in mind here is that the failure is during an "upgrade" test, where latest was installed and then 1.1.1 has been installed over the top. This issue is observed after the downgrade, and is on Cilium 1.1.1 ( git commit 6094010).
For a while I was concerned that perhaps a map with key/values defined in one version might be somehow dumped from a subsequent version, and cause corruption via invalid sized dump. This should be prevented by the map upgrade logic though, and it appears that the map upgrade logic should be triggered if necessary for the LB Maps via OpenOrCreate().  FWIW in the logs there is no evidence that a map upgrade happens for LB map types (and upon manual inspection, it doesn't seem like LB maps have changed structure at all between these versions).
However, looking closer at the logs I see no evidence that the 1.1.1 version is performing map "upgrade" for the CT map, which has been changed between 1.1.1 and master. This is a bit concerning and could explain the corruption we see, via the CT map dump rather than the LB map dumps.

FWIW we don't seem to print any debug logs for CT dump window so I'm not sure we could know when the ct dump is occurring and how it might impact the timeline presented by @ianvernon above:
$ git grep log pkg/maps/ctmap/
pkg/maps/ctmap/ctmap.go:        "github.com/cilium/cilium/pkg/logging"
pkg/maps/ctmap/ctmap.go:        "github.com/cilium/cilium/pkg/logging/logfields"
pkg/maps/ctmap/ctmap.go:        log = logging.DefaultLogger.WithField(logfields.LogSubsys, "map-ct")
pkg/maps/ctmap/ctmap.go:                                log.WithError(err).Errorf("Unable to delete CT entry %s", currentKey.String())
pkg/maps/ctmap/ctmap.go:                log.WithError(err).WithField("interrupted", interrupted).Warning(
pkg/maps/ctmap/ctmap.go:                                log.WithError(err).Errorf("Unable to delete CT entry %s", currentKey.String())
pkg/maps/ctmap/ctmap.go:                log.WithError(err).WithField("interrupted", interrupted).Warning(
pkg/maps/ctmap/ctmap.go:                // FIXME: GH-3239 LRU logic is not handling timeouts gracefully enough

Looking closer at the logs I see no evidence that the 1.1.1 version is performing map "upgrade" for the CT map, which has been changed between 1.1.1 and master. This is a bit concerning and could explain the corruption we see, via the CT map dump rather than the LB map dumps.

Great point. Is it feasible for us to do migration of the conntrack map?

We don't seem to print any debug logs for CT dump window so I'm not sure we could know when the ct dump is occurring

I'll add these logs and post a PR so we can have more data if this occurs again.

The CT table is created exclusively from the kernel part so there is no upgrade. We'll have to delete the table manually if we want to force a re-creation.

Even if the CT table is created in the kernel, can't we migrate it nonetheless? I do not understand why the fact that the map is created in the kernel affects whether or not we can upgrade it.

Yeah, since it is still being modified by the datapath (i.e., new connections being added / removed), then is there a concern we may lose newly added info that was added while we migrate the data? Thanks for answering my questions - I am not too familiar with this area of things.

Probably worth clarifying, inside Cilium right now, the deletion/recreation of maps is referred to as "updating" the map. @ianvernon , is this what you mean or do you mean actual migration of the full map including contents?
The map property update logs for ipcache are there in this failure, as an example:
2018-07-31T10:30:59.677360299Z level=info msg="Map type mismatch for BPF map" file-path=/sys/fs/bpf/tc/globals/cilium_ipcache new="Longest prefix match trie" old=Hash
2018-07-31T10:30:59.677409228Z level=info msg="Flags mismatch for BPF map" file-path=/sys/fs/bpf/tc/globals/cilium_ipcache new=1 old=0
2018-07-31T10:30:59.677414691Z level=info msg="Removing map to allow for property upgrade (expect map data loss)" file-path=/sys/fs/bpf/tc/globals/cilium_ipcache

I expect that in this situation we should delete and recreate the CT map as well, but we do not appear to be doing so. I don't know why.

Two reasons that we didn't delete the CT so far:

We never broke compatibility up to now so there was no reason to cause connection breakage on upgrade
The map is always created from kernel space so far so the existing logic in OpenOrCreate() does not work.

Fixing this for the global CT model is simple, we can:

Rename the old global CT map if it exists and create a new one with the new format
Restore all endpoints
Delete the old map

Fixing this for the per endpoint CT map requires the same logic as above to be done for each endpoint restored given the endpoint is using per endpoint CT.


fixed split [vh], small memory leak, unescape_strings handle \xnn

split vh was passing unaltered arugments into _do_split which wanted no arguments.
frees container names now.
unescape handles a few more things \' \" \xnn \\

unescape is not actually used for anything right now, fwiw.


Bring back keyboardType

After the conversion to Swift 3, the keyboardType property somehow disappeared. This PR just brings it back.
If you want, I can also do the preparation needed to bump the version to 0.8.2.
Best regards!

@gskbyte Thank you!

Nice, thanks for merging the PR! Do you plan to make a release soon?

Oh, I just saw you did it already :) Thanks!


Fix various issues

Check types when adding qubits/bits to a circuit and raise a TypeError if an incorrect type is passed to the method.
Rename label to name for operations.
Fix inconsistent spacing in primitive object representations. (#17)
Fix sequential qubit/bit labelling when adding new registers.
Update operation representations to use repr() for hashables. (#17)
Adds Circuit.get_bit method (should've been in #23).
Formats all files using black/isort (mainly affecting operation_generation).
Ignore operation_generation.py in coverage since it's already indirectly tested in the simulator tests.

Fixes #17

Codecov Report

Merging #24 (7bd7d3b) into master (377deed) will increase coverage by 0.25%.
The diff coverage is 85.71%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
+ Coverage   90.87%   91.12%   +0.25%
==========================================
  Files          16       16
  Lines        1293     1307      +14
  Branches      207      214       +7
==========================================
+ Hits         1175     1191      +16
+ Misses        118      116       -2

Impacted Files
Coverage Δ

dwave/gate/simulator/operation_generation.py
0.00% <0.00%> (ø)

dwave/gate/circuit.py
100.00% <100.00%> (ø)

dwave/gate/mixedproperty.py
100.00% <100.00%> (+6.45%)
:arrow_up:

dwave/gate/operations/base.py
100.00% <100.00%> (ø)

dwave/gate/primitives.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Permissions

Update documentation, without sudo it won't work if the user is not root user, It should be
sudo pip install djauto
sudo djauto PROJECT_NAME APP_NAME
Otherwise it gives error on os.chdir(project_name) because it does not have root permission.

Thanks, I will mention that. Though, I was planning to suggest to use virtualenv for development. Please check Todos.

I've updated it. Feel free to contribute if you see any error in it.

yeah, sure.
On 26 August 2015 at 05:23, Vikas Parashar<EMAIL_ADDRESS>wrote:

Closed #1
https://github.com/vikas-parashar/django-project-generator/issues/1.
—
Reply to this email directly or view it on GitHub
https://github.com/vikas-parashar/django-project-generator/issues/1#event-392270665
.


Fix vector builder when building sparse vector with unique indices

Hello @dlwh can you take a look?

sorry about that!


Failed to build on Ubuntu 22.04: missing lib avresample

OS Platform and Distribution
Ubuntu 22.04
Compiler version
gcc 11.4
Programming Language and version
C++ (mediapipe version)
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
0.10.9
Bazel version
6.1.1
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
4.5.4
Describe the problem
Compilation fails: -lavresample missing
Dependencies specified in https://developers.google.com/mediapipe/framework/getting_started/install are all installed.
Note that the package libavresample-dev is not available on Ubuntu 22.04 anymore.
Complete Logs
INFO: Analyzed target //mediapipe/python:_framework_bindings.so (87 packages loaded, 3290 targets configured).
INFO: Found 1 target...
ERROR: /root/src/mediapipe-debian/deb_dist/mediapipe-0.10.9/third_party/BUILD:154:6: Foreign Cc - CMake: Building opencv_cmake failed: (Exit 1): bash failed: error executing command (from target //third_party:opencv_cmake) /bin/bash -c bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/wrapper_build_script.sh

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
rules_foreign_cc: Build failed!
rules_foreign_cc: Keeping temp build directory and dependencies directory for debug.
rules_foreign_cc: Please note that the directories inside a sandbox are still cleaned unless you specify --sandbox_debug Bazel command line flag.
rules_foreign_cc: Printing build logs:
_____ BEGIN BUILD LOGS _____

Bazel external C/C++ Rules. Building library opencv_cmake

Environment:______________
BUILD_SCRIPT=bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/build_script.sh
EXT_BUILD_ROOT=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe
BUILD_LOG=bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/CMake.log
PWD=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe
BUILD_WRAPPER_SCRIPT=bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/wrapper_build_script.sh
PYTHON_BIN_PATH=/usr/bin/python3
TMPDIR=/tmp
EXT_BUILD_DEPS=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.ext_build_deps
BUILD_TMPDIR=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir
SHLVL=2
INSTALLDIR=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake
PATH=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe:/root/.cache/bazelisk/downloads/sha256/651a20d85531325df406b38f38a1c2578c49d5e61128fba034f5b6abdb3d303f/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/src/mediapipe-debian
_=/usr/bin/env
__________________________
+ /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/external/cmake-3.23.2-linux-x86_64/bin/cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_LIST=calib3d,core,features2d,highgui,imgcodecs,imgproc,video,videoio -DBUILD_TESTS=OFF -DBUILD_PERF_TESTS=OFF -DBUILD_EXAMPLES=OFF -DBUILD_SHARED_LIBS=OFF -DWITH_ITT=OFF -DWITH_JASPER=OFF -DWITH_JPEG=ON -DWITH_PNG=ON -DWITH_TIFF=ON -DWITH_OPENCL=OFF -DWITH_WEBP=OFF -DCV_ENABLE_INTRINSICS=ON -DWITH_EIGEN=ON -DWITH_PTHREADS=ON -DWITH_PTHREADS_PF=ON -DOPENCV_SKIP_VISIBILITY_HIDDEN=ON -DOPENCV_SKIP_PYTHON_LOADER=ON -DBUILD_opencv_python=OFF -DENABLE_CCACHE=OFF -DCMAKE_TOOLCHAIN_FILE=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/crosstool_bazel.cmake -DCMAKE_INSTALL_PREFIX=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake -DCMAKE_PREFIX_PATH=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.ext_build_deps -DCMAKE_RANLIB= -DCMAKE_MAKE_PROGRAM=/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt-exec-50AE0418/bin/external/rules_foreign_cc/toolchains/make/bin/make -G 'Unix Makefiles' /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/external/opencv
-- The CXX compiler identification is GNU 11.4.0
-- The C compiler identification is GNU 11.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/gcc
-- Check for working CXX compiler: /usr/bin/gcc - broken
CMake Error at /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/external/cmake-3.23.2-linux-x86_64/share/cmake-3.23/Modules/CMakeTestCXXCompiler.cmake:62 (message):
  The C++ compiler

    "/usr/bin/gcc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/CMakeFiles/CMakeTmp

    Run Build Command(s):/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt-exec-50AE0418/bin/external/rules_foreign_cc/toolchains/make/bin/make -f Makefile cmTC_21db3/fast && /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt-exec-50AE0418/bin/external/rules_foreign_cc/toolchains/make/bin/make  -f CMakeFiles/cmTC_21db3.dir/build.make CMakeFiles/cmTC_21db3.dir/build
    make[1]: Entering directory '/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/CMakeFiles/CMakeTmp'
    Building CXX object CMakeFiles/cmTC_21db3.dir/testCXXCompiler.cxx.o
    /usr/bin/gcc   -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 -D_FORTIFY_SOURCE=1 -DNDEBUG -ffunction-sections -fdata-sections -std=c++0x -fno-canonical-system-headers -Wno-builtin-macro-redefined -D__DATE__=\"redacted\" -D__TIMESTAMP__=\"redacted\" -D__TIME__=\"redacted\" -w -std=c++17  -fPIE -o CMakeFiles/cmTC_21db3.dir/testCXXCompiler.cxx.o -c /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
    Linking CXX executable cmTC_21db3
    /root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/external/cmake-3.23.2-linux-x86_64/bin/cmake -E cmake_link_script CMakeFiles/cmTC_21db3.dir/link.txt --verbose=1
    /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 -D_FORTIFY_SOURCE=1 -DNDEBUG -ffunction-sections -fdata-sections -std=c++0x -fno-canonical-system-headers -Wno-builtin-macro-redefined -D__DATE__=\"redacted\" -D__TIMESTAMP__=\"redacted\" -D__TIME__=\"redacted\" -w -std=c++17  -fuse-ld=gold -Wl,-no-as-needed -Wl,-z,relro,-z,now -B/usr/bin -pass-exit-codes -Wl,--gc-sections -lstdc++ -lm -ljpeg -lpng -lz -ltiff -lImath -lIlmImf -lIex -lHalf -lIlmThread -ldc1394 -lavcodec -lavformat -lavutil -lswscale -lavresample -ldl -lpthread -lrt  -rdynamic CMakeFiles/cmTC_21db3.dir/testCXXCompiler.cxx.o -o cmTC_21db3
    /usr/bin/ld.gold: error: cannot find -lavresample
    collect2: error: ld returned 1 exit status
    make[1]: *** [CMakeFiles/cmTC_21db3.dir/build.make:99: cmTC_21db3] Error 1
    make[1]: Leaving directory '/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/CMakeFiles/CMakeTmp'
    make: *** [Makefile:127: cmTC_21db3/fast] Error 2

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:106 (enable_language)

-- Configuring incomplete, errors occurred!
See also "/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/CMakeFiles/CMakeOutput.log".
See also "/root/.cache/bazel/_bazel_root/1ac7877a3928a8f5f6c80864df2c2a3e/sandbox/processwrapper-sandbox/364/execroot/mediapipe/bazel-out/k8-opt/bin/third_party/opencv_cmake.build_tmpdir/CMakeFiles/CMakeError.log".
_____ END BUILD LOGS _____
rules_foreign_cc: Build wrapper script location: bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/wrapper_build_script.sh
rules_foreign_cc: Build script location: bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/build_script.sh
rules_foreign_cc: Build log location: bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/CMake.log

Target //mediapipe/python:_framework_bindings.so failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /root/src/mediapipe-debian/deb_dist/mediapipe-0.10.9/mediapipe/python/BUILD:21:17 Linking mediapipe/python/_framework_bindings.so failed: (Exit 1): bash failed: error executing command (from target //third_party:opencv_cmake) /bin/bash -c bazel-out/k8-opt/bin/third_party/opencv_cmake_foreign_cc/wrapper_build_script.sh

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
INFO: Elapsed time: 122.712s, Critical Path: 120.86s
INFO: 527 processes: 167 internal, 360 processwrapper-sandbox.
FAILED: Build did NOT complete successfully
Command '['bazel', 'build', '--compilation_mode=opt', '--copt=-DNDEBUG', '--action_env=PYTHON_BIN_PATH=/usr/bin/python3', '//mediapipe/python:_framework_bindings.so', '--define=MEDIAPIPE_DISABLE_GPU=1', '--define=OPENCV=source']' returned non-zero exit status 1.
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1
make[1]: Leaving directory '/root/src/mediapipe-debian/deb_dist/mediapipe-0.10.9'
make: *** [debian/rules:7: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

I've 'solved' the problem by removing -lavresample from BUILD. mediapipe seems to build fine without it on Ubuntu 22.04.

In my case it was on the mediapipe/third_party/BUILD.

I actually fail differently on Ubuntu 22.04:

Unable to locate package libdc1394-22-dev
When running setup_opencv.sh

Following from here
It seems that libdc1394-22-dev does not exist but is expected, while there is a possible alternative package libdc1394-dev


Small update and duplication removal

I updated Property Manager location, and I think there's no need to repeat the location of Property Manager after just three lines.

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

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


Implement queueing search events until a listener appears

This PR replaces the normal EventEmitter that's returned from Client.search() with a compatible "corked" version that will not start emitting events until a listener appears. It eliminates a race condition where some early events could be missed, preventing the user of the method from seeing the first few search results or, in extreme cases, the end boundary of the search.
For #602

I intend to issue a release soon. Hopefully in the next few days.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Readme doesn't explain how it is used

Sure you can run it, which the readme writes a lot about, but what does it actually do?
The why could also be explained more thoroughly. Why would you want to use this, which problems does it solve?
Thanks a lot!

Hi,
you are absolutely right about that. We'll try to explain the concept and setup in detail in the following days.
Thanks for reporting.

I've finally had time to create the Background section in the README. Feel free to open other another issue if some aspect is left in the dark.


Unable to connect SAM model with label studio

Validation error
Can't connect to ML backend http://localhost:9090/, health check failed. Make sure it is up and your firewall is properly configured.

I have used below docker_compose file to run the services.
version: "3.8"
services:
redis:
image: redis:alpine
container_name: redis
hostname: redis
volumes:
- "./data/redis:/data"
expose:
- 6379
label_studio:
image: heartexlabs/label-studio:1.8.1
container_name: label_studio
ports:
- 8082:8080
volumes:
- "./data/mydata:/data"
networks:
- label_server_net  # Connect to the custom network
server:
container_name: server
build: .
environment:
- MODEL_DIR=/data/models
- RQ_QUEUE_NAME=default
- REDIS_HOST=redis
- REDIS_PORT=6379
- LABEL_STUDIO_USE_REDIS=true
- TEST_WITH_CPU=${TEST_WITH_CPU}
ports:
- 9090:9090
depends_on:
- redis
volumes:
- "./data/server:/data"
- "./logs:/tmp"
networks:
- label_server_net  # Connect to the custom network
volumes:
mydata:
networks:
label_server_net:  # Define the custom network
please help to resolve the issue

some problems


Location !!

There is  a location indicator on launcher but because it's reporting the new buggered location from the server it's just a useless piece of screen clutter and can/should go away

https://github.com/Apostolique/Agar.io-bot/issues/597 already acknowledged


Release 0.13.1

Modify deprecated function

Issue: #543

Codecov Report
Patch coverage is 64.28% of modified lines.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files Changed
Coverage

src/graphql/export.rs
ø

src/graphql/network.rs
ø

src/graphql/statistics.rs
ø

src/ingest/tests.rs
ø

src/publish/tests.rs
ø

src/storage/migration.rs
ø

src/storage.rs
58.33%

src/graphql/packet.rs
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


The font name in onlyoffice does not support the Chinese language.

If the font name was changed into  Chinese name. Then its name will be shown as "????"


Duplicate entries in subscribers DB table

I don't know if it's an issue for you now, but it seems that you will have duplicate entries if someone subscribes multiple times for some reason (I did for scientific purposes).
Just wanted to point that out in case you missed it.

Thanks a lot for letting us know! I just fixed it.


why i can not find  this function: setThumbInCustomProject  ? Can you help me ?

There is no setThumbInCustomProject function.
See demo, ImageloaderActivity, and pick your imageloader function.


Fixed link to Request Unit (RU) Description

Have the link of "Request Unit RU" point to description of Request Units (documentdb-request-units.md). Originally it linked to programming of document DB, which has no information about the RUs.

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

@apollak : Thanks for your contribution to the Azure documentation! The author, @ArnoMicrosoft, has been notified to review your proposed change.

@apollak, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

#sign-off

@arno756 looks like you've used another account and your sign-off didn't go through

@arno756 Sorry to ask, but your profile doesn't have enough information to identify you. Automation assigned this pull request to @ArnoMicrosoft. I can't reconcile the two aliases. Can you confirm that @arno756 is the author of the article? If so, it would be good to update the metadata in the article after this pull request is merged. Please advise. Thanks.

#sign-off

@apollak @ArnoMicrosoft Thanks for the contribution and review. Merging now.


support.9oo91e.qjz9zk is blocked

Hi I'm getting the aw snap! message on a lot of normal sites all the time (on Archlinux), then if I click learn more then I see:
support.9oo91e.qjz9zk is blockedRequests to the server have been blocked by an extension.
Try disabling your extensions.
ERR_BLOCKED_BY_CLIENT
any help appreciated

A recent update to ffmpeg brok chromium, an update is on the way.

The patch is https://git.archlinux.org/svntogit/packages.git/tree/trunk/chromium-ffmpeg-4.3.patch?h=packages/chromium&id=d7ba6a0893c85d15faea19e9fdf5f04d18a8e449 or https://gitweb.gentoo.org/repo/gentoo.git/tree/www-client/chromium/files/chromium-84-mediaalloc.patch?id=fd3c6eeae58085ad2248e99ad67d8eba0f3a25ff, it seems to work even with (ungoogled) chromium version 83.

Is this already fixed on Arch Linux?

Yes, it should be this patch.

Closing then.
support pages being broken is discussed in another issue.

Binary version 87.0.4280.141 on Linux.. Same error.

Binary version 87.0.4280.141 on Linux.. Same error.

Arch Binary Version 115.0.5790.110 still the same issue.


Data Scrapping/ Data Exploration

Explore Datasets that we can use. (Kaggle, Github, Open Source)
If not available or does not fulfill our requirements scrape data.

Emergency (last Resource) - Fake data

Good Job Folks


SwarmMemberAddressProvider access to Docker Engine

Hello,
Having first tried DNSRR I am now looking into SwarmMemberAddressProvider for cluster node discovery.
I asked our infrastructure people to provide the necessary parameter value for ${swarmMgrUri} and received the following response:
“I've had a look at this, and if it's connecting to the docker daemon over https to get information on the swarm it would require a massive rearchitecting of the swarm setup, as we'd have to open up some dangerous access, and then make sure we secured it properly, and we'd need to generate certificates for all the servers, and get them injected into the containers at run time.  This isn't the right way to approach this issue.”
if SWARM_MGR_URI is overriding DOCKER_HOST, perhaps it is an optional parameter after all?
I’m hoping that things are actually simpler than I have made them out to be, but at this stage I lack a route forward to achive hazelcast cluster node discovery.
Thanks, Robin.

If you are not using the DNSRR method, the "swarmMgrUri" is simply a variable name that represents an endpoint (socket or http/s endpoint) to directly get the peer level information needed to form a cluster. In order to work this needs access to some endpoint that presents the Docker API for swarm services/tasks/network information etc. There are numerous ways access to this can be secured or proxied, republished etc (i.e. such as https://github.com/Tecnativa/docker-socket-proxy). If your infrastructure team is not willing to work with you on getting access to that information, then there simply is no other way for hazelcast to discover your services overlay network "peers" and you are SOL. You might have to start looking at another hazelcast discovery SPI other than this one.


How to access StreamBuf?

How can I access the StreamBuf object to use in this example:
var buf = new StreamBuf()
workbook.xlsx.write(buf)
  .then(function() {
    var data = buf.toBuffer();
  });

@diakonovm did you find out a way?


Provide required call flags and allowed triggers in interop descriptions.

Closes #1029 .

This one needs to be rebased now.