Inconsistent behavior between WebMMuxer and Mp4Muxer

Hi,
Thank you for all the work on webm-muxer and mp4-muxer!
I am using the libraries to record canvas animation frames. I've noticed each library behaves a little differently when used in the same way.
In the example below, I'm recording the total of 30 frames.
In the resulting WebM video, the last frameCount is 29, which is accurate. It also has the correct fps of 30.
But in the mp4 video, the last frameCount shows up as 28, missing the very last frame. What's also strange is that when I manually scrub the Quicktime timeline, I sometimes do see 29 displayed but it seems this frame doesn't have any duration. Also, the frame rate is displayed as 31.03 instead of 30.
I'm wondering if I need to handle frame recording differently with mp4-muxer.
Below is a simple demo to illustrate my issue. You can click the mouse inside the canvas to initiate the recording of both videos:
import * as Mp4Muxer from "mp4-muxer";
import * as WebMMuxer from "webm-muxer";

const canvas = document.createElement("canvas");
document.body.appendChild(canvas);
canvas.width = 400;
canvas.height = 400;
const ctx = canvas.getContext("2d")!;

let mp4Muxer: Mp4Muxer.Muxer<Mp4Muxer.ArrayBufferTarget> | null = null;
let webmMuxer: WebMMuxer.Muxer<WebMMuxer.ArrayBufferTarget> | null = null;
let mp4VideoEncoder: VideoEncoder | null = null;
let webmVideoEncoder: VideoEncoder | null = null;
let startTime: number | null = 0;
let recordingState: "start" | "recording" | null = null;
let lastKeyFrame = -Infinity;
let frameCount = 0;
let fps = 30;

const startRecording = async () => {
  mp4Muxer = new Mp4Muxer.Muxer({
    target: new Mp4Muxer.ArrayBufferTarget(),
    video: {
      codec: "avc",
      width: canvas.width,
      height: canvas.height,
    },
    fastStart: "in-memory",
  });
  webmMuxer = new WebMMuxer.Muxer({
    target: new WebMMuxer.ArrayBufferTarget(),
    video: {
      codec: "V_VP9",
      width: canvas.width,
      height: canvas.height,
      frameRate: 30,
    },
  });

  mp4VideoEncoder = new VideoEncoder({
    output: (chunk, meta) => mp4Muxer!.addVideoChunk(chunk, meta),
    error: (e) => console.error(e),
  });
  mp4VideoEncoder.configure({
    codec: "avc1.42001f",
    width: canvas.width,
    height: canvas.height,
    bitrate: 1e6,
  });

  webmVideoEncoder = new VideoEncoder({
    output: (chunk, meta) => webmMuxer!.addVideoChunk(chunk, meta),
    error: (e) => console.error(e),
  });
  webmVideoEncoder.configure({
    codec: "vp<IP_ADDRESS>",
    width: canvas.width,
    height: canvas.height,
    bitrate: 1e6,
  });
};

const encodeVideoFrame = () => {
  let elapsedTime = (frameCount * 1e6) / fps;
  let frame = new VideoFrame(canvas, {
    timestamp: (frameCount * 1e6) / fps, // Ensure equally-spaced frames every 1/30th of a second
  });

  // Ensure a video key frame at least every 10 seconds for good scrubbing
  let needsKeyFrame = elapsedTime - lastKeyFrame >= 10000;
  if (needsKeyFrame) lastKeyFrame = elapsedTime;

  mp4VideoEncoder?.encode(frame, { keyFrame: needsKeyFrame });
  webmVideoEncoder?.encode(frame, { keyFrame: needsKeyFrame });
  frame.close();
};

const endRecording = async () => {
  recordingState = null;

  await mp4VideoEncoder?.flush();
  mp4Muxer?.finalize();
  let mp4Buffer = mp4Muxer?.target.buffer!;
  downloadBlob(new Blob([mp4Buffer]), "test.mp4");

  await webmVideoEncoder?.flush();
  webmMuxer?.finalize();
  let webmBuffer = webmMuxer?.target.buffer!;
  downloadBlob(new Blob([webmBuffer]), "test.webm");

  mp4VideoEncoder = null;
  mp4Muxer = null;
  webmVideoEncoder = null;
  webmMuxer = null;
  startTime = null;
};

const downloadBlob = (blob: Blob, filename: string) => {
  let url = window.URL.createObjectURL(blob);
  let a = document.createElement("a");
  a.style.display = "none";
  a.href = url;
  a.download = filename;
  document.body.appendChild(a);
  a.click();
  window.URL.revokeObjectURL(url);
};

canvas.addEventListener("click", () => {
  recordingState = "start";
});

function run() {
  if (recordingState === "start") {
    frameCount = 0;
    startRecording();
    recordingState = "recording";
  }

  draw();

  if (recordingState === "recording") {
    encodeVideoFrame();
  }

  frameCount++;

  if (recordingState === "recording" && frameCount === 30) {
    endRecording();
    frameCount = 0;
    recordingState = null;
  }

  window.requestAnimationFrame(run);
}
window.requestAnimationFrame(run);

function draw() {
  ctx.fillStyle = "gray";
  ctx.fillRect(0, 0, canvas.width, canvas.height);

  ctx.font = "100px monospace";
  ctx.fillStyle = `white`;
  ctx.fillText(frameCount.toString(), 200, 200);
}

Thanks for the full reproduction, I really appreciate it! Even better would be a finished setup on StackBlitz (with Vite or something), so I can just open it and see it immediately. But that's for next time :)
MP4 and WebM work a little different; in WebM, video frames only have a timestamp. In MP4, the timing of frames is determined by the delta between frames, so duration matters more. A simple fix in your code made the MP4 file play back correctly:
  let frame = new VideoFrame(canvas, {
    timestamp: (frameCount * 1e6) / fps, // Ensure equally-spaced frames every 1/30th of a second
+   duration: 1e6 / fps,
  });

Without this field, the frame implicitly gets a duration of 0. With the proper duration set, the last frame of the video shows correctly (this is in Finder):

https://github.com/Vanilagy/mp4-muxer/assets/1696106/d358ae9f-34e5-4ad2-81ae-3b79bb2b47fb
It has to be noted that this also depends heavily on the player, Chromium properly showed the last frame even for the "incorrect" file.
The 31.03 frame rate can be explained like so: Since the original video had 0-duration frames, its duration was equal to the timestamp of the last frame, which is at $\frac{29}{30}$ seconds. But the video still had 30 frames, so it comes out to a frame rate of
$$
\frac{30}{\frac{29}{30}} \approx 31.03448
$$
With the frame duration set, it correctly has a duration of exactly 1 second and a frame rate of 30.
I hope this clears things up. If you still have any questions, feel free to ask!

That solved the issue! Thank you for the kind explanation. I will be keep in mind to include a live environment next time. 🙏

@Vanilagy, just to clarify? fixing the duration solves the problem on all players? specially interested in browsers

@Pensarfeo It was the case for me, but I only tested Chromium and QuickTime. I attached a fixed file in my reply in this thread, so you can try that out.

Ill check! :)

Worked for me, thanks @Vanilagy!

Awesome! I think this is partially on me since I don't set the duration in my demo script. I should!


Add support for basic key usage

Signed-off-by: Yuri Schimke<EMAIL_ADDRESS>

MainTest output
CN: 	www.google.com
SHA256:	de0b6d30100e9a69a10c29a7c3806e7d865ace12c278ab197f85a80b285951d8
SAN: 	www.google.com
Key Usage: DigitalSignature
Valid: 	2020-08-11T08:59:33Z..2020-11-03T08:59:33Z
CA: false

CN: 	GTS CA 1O1
SHA256:	6193e04d9fb0a0d0820885b72c7d82c5078bcc1ff59b8d907024c149d81aca3b
SAN: 	<N/A>
Key Usage: DigitalSignature, KeyCertSign, CRLSign
Valid: 	2017-06-15T00:00:42Z..2021-12-15T00:00:42Z
CA: true Max Intermediate: 0

CN: 	GlobalSign (signed by locally-trusted root)
SHA256:	8a27b5557b4bec7cc0305fbf3d53d1f71cd3f34910c5d65e27ecddb82077ba3d
SAN: 	<N/A>
OU: 	GlobalSign Root CA - R2
Key Usage: KeyCertSign, CRLSign
Valid: 	2006-12-15T08:00:00Z..2021-12-15T08:00:00Z
CA: true

Verified against https://report-uri.com/home/pem_decoder


DraggableView start closeToRight() / closeToLeft()

Hello.
I am using draggableView in my project. At the initializeDraggableView method, I already set the visibility to gone and closeToRight() which I hope when I first time click the list item, the draggableview will show an animation from right to top. But the draggableView just appear on top of the list item which is not so animated. But when I minimized the draggableView and close the draggableView by myself, and click at the other list item, the animation went well.
Thank you.

Could you find any solutions to this issue? Tried several methods but no luck

Hi there,
Nope, still no solution.
On 5 May 2016 22:43, "Tunca Ulubilge"<EMAIL_ADDRESS>wrote:

Could you find any solutions to this issue? Tried several methods but no
luck
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/pedrovgs/DraggablePanel/issues/88#issuecomment-217172594

This is made by design, not a bug.

@ppamorim Any suggestions on how to change this? I can fork your project for this feature.

You need to do some workarounds to pervent this problem. I solved this on my app doing this: start the view hidden -> call to move to close to right -> only show the view only the method to expand the view is called.

Found an ugly but working solution for this issue.
The trick is, the draggableView has to be visible when you can call minimize(). In my layout, I made draggableView visible with both drag views invisible.
When the draggableView global layout is called, I minimize the view and set it to invisible again in a delayed runnable. This way, when I want to display the views with maximize, the animation plays from bottom to top.
Here is the code:
 playerView.getViewTreeObserver().addOnGlobalLayoutListener(
                new ViewTreeObserver.OnGlobalLayoutListener() {
                    @Override public void onGlobalLayout() {
                        // gets called after layout has been done but before display
                        playerView.getViewTreeObserver().removeOnGlobalLayoutListener(this);
                        playerView.minimize();
                        Handler handler = new Handler();
                        handler.postDelayed(new Runnable() {
                            @Override public void run() {
                                playerView.setVisibility(View.INVISIBLE);
                                playerView.setChildViewsVisible();
                            }
                        }, 10);
                    }
                });

Afterwards, when I want to display the player, I just set it to VISIBLE and call maximize()

Sorry guys but this is the original behaviour of the library. As this is not a bug I'm closing the issue.


Added Data Ingest Breakdown

A new dashboard that has some example of queries for data ingest source investigations.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


SyntaxError: invalid syntax--On Line number 61

$ python --version
Python 3.6.4 :: Anaconda, Inc.
File "", line 61
html_content = opened_request.read()
^
SyntaxError: invalid syntax

The current version do not support python3.
However, there is a pull request to make it compatible with python3 #20


VisualD installer doesn't detect Visual Studio 2022 installation when it has a nickname

Recent versions of Visual Studio allow multiple parallel installations for the same version (for example, 2022 Pro and 2022 Enterprise can be installed at the same time, see [1]). The installer prompts the user for a nickname for any additional installation, which cannot be changed later [2]. This nickname gets appended in paranthesis to the DisplayName key in the corresponding uninstaller registry key. For example, I have an installation named "Microsoft Visual Studio Enterprise 2022 (2)" because it was a secondary installation at some point in the past. At least VS2022 and VS2019 support this feature. I don't know if support goes back further.
The VisualD installer script looks for Visual Studio 2022 comparing the last 4 characters of the display name with "2022". This fails with a nickname present and the Visual Studio 2022 checkbox gets disabled. I think a better algorithm is to ignore anything after the first " (" in the display name. Of course, this has the unpleasant side effect that the user would ultimately need to get a choice of installing VisualD for each parallel Visual Studio installations if this side-by-side installation situation is to be supported properly.
Unfortunatenly, my NSIS scripting skills are not good enough to fix this issue myself. Otherwise, I'd be working on a patch already :(.
[1] https://learn.microsoft.com/en-us/visualstudio/install/install-visual-studio-versions-side-by-side?view=vs-2022#install-different-editions-of-the-same-major-visual-studio-version-side-by-side
[2] https://developercommunity.visualstudio.com/t/rename-microsoft-visual-studio-2-to-microsoft-visu/1016860

I guess vswhere (https://github.com/microsoft/vswhere) can detect all installations, so it would not be too hard to get a list of them all. Making NSIS show and execute this list dynamically is probably a nightmare, though.


Cli context class

Let's go through these changes after daily scrum.

Coverage increased (+1.8%) to 74.718% when pulling fbad270418c25c25038b10e6308c7a05b0de8623 on cli-context-aleksi into 9b4769f947c88e00199c4cbfe19d2d0ab87f377d on master.

Coverage increased (+1.5%) to 74.428% when pulling 144f4322081dddadbe3fef4d401d3e55443ff2c1 on cli-context-aleksi into 9b4769f947c88e00199c4cbfe19d2d0ab87f377d on master.

:+1: hot damn


:bug: server crashes when client closes connection before server

INFO    [HANDLER] REQUEST: /media/img/pigeonpost.png
VERBOSE [HANDLER] SENDING RESPONSE TO <IP_ADDRESS>:44564
VERBOSE [SERVER] CONNECTION FROM <IP_ADDRESS>:44570
VERBOSE [HANDLER] TREATING CONNECTION FROM <IP_ADDRESS>:44570 as HTTP request
DEBUG   [HANDLER] RAW PACKET:
b'GET /static/css/counter.css HTTP/1.1\r\nHost: localhost\r\nUser-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0\r\nAccept: text/css,/;q=0.1\r\nAccept-Language: en-US,en;q=0.5\r\nAccept-Encoding: gzip, deflate, br\r\nConnection: keep-alive\r\nReferer: http://localhost/\r\nSec-Fetch-Dest: style\r\nSec-Fetch-Mode: no-cors\r\nSec-Fetch-Site: same-origin\r\n\r\n'
INFO    [HANDLER] REQUEST: /static/css/counter.css
VERBOSE [HANDLER] SENDING RESPONSE TO <IP_ADDRESS>:44570
Traceback (most recent call last):
File "/home/lstuma/programming/projects/PigeonPost/demo/app.py", line 12, in
run()
File "/home/lstuma/programming/projects/PigeonPost/demo/app.py", line 6, in run
server.start(
File "/usr/lib/python3.11/site-packages/pigeon/core/server.py", line 32, in start
serve()
File "/usr/lib/python3.11/site-packages/pigeon/core/server.py", line 61, in serve
asyncio.run(handler.handle_request(client_sock, client_address))
File "/usr/lib/python3.11/asyncio/runners.py", line 190, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/asyncio/runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pigeon/core/handler.py", line 71, in handle_request
client_sock.shutdown(socket.SHUT_RDWR)
OSError: [Errno 107] Transport endpoint is not connected

fixed long ago - forgot to close ticket


[Refactor] Refactor some cloud native compaction logs

warning log when compact failed because of memory limit exceeded.
info log when adjust compaction concurrency.
add tablet id in compaction progress log.

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[ ] 2.5
[ ] 2.4

@Mergifyio backport branch-3.0

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.1

https://github.com/Mergifyio backport branch-3.1


[iOS] BleClient React/* headers can't be found

Running a iOS 10 targeted project with the pod headers added to the search settings and all setup instructions for this package followed. The following error appears on build:
React/Base/RCTBridgeModule.h:12:9: 'React/RCTDefines.h' file not found

I had the same issue change:
#import “RCTBridgeModule.h”
#import “RCTEventEmitter.h”
to:
#import <React/RCTBridgeModule.h>
#import <React/RCTEventEmitter.h>
it fix my problem.

That’s a completely different legacy react-native issue. Note that the title of this issue already shows “React/“

This issue should be resolved with version 0.6.2.

I've confirmed the issues still prevail after an npm install -S react-native-ble-plx and run of react-native link as well as doing a new clean before building in xcode.

I'm having the same problem on 0.6.2 as well

Can you paste an error? I created clean RN project with version 0.48.3. Did react-native link react-native-ble-plx and proceeded from step 7 as mentioned in documentation. Can't reproduce your issue on my machine. Can you check that?

I did the following steps on my machine (10.13 + XCode9 + react-native@0.48.4):
1.) react-native init rnbletest
2.) npm install --save react-native-ble-plx
2.5) fix this issue before carthage gets to the RxBluetoothKit.xcodeproj file.
3.) npm install
4.) react-native link react-native-ble-plx
At this point everything command works fine and no errors in output. However I try to do react-native run-ios I get an error during link:
ld: framework not found BleClientManager for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
Opening up the BleClientManager project and attempting to build it will result this error:
In file included from /Users/ztan/Projects/anova/reactnativeApp/rnbletest/node_modules/react-native-ble-plx/ios/BleClient.m:9: /Users/ztan/Projects/anova/reactnativeApp/rnbletest/node_modules/react-native-ble-plx/ios/BleClient.h:10:9: fatal error: 'React/RCTBridgeModule.h' file not found #import <React/RCTBridgeModule.h>         ^~~~~~~~~~~~~~~~~~~~~~~~~ 1 error generated.
Let me know if providing full logs/files would be helpful.

First of all, thank you for your detailed steps! Without them I coudn't help you.

I did the following steps on my machine (10.13 + XCode9 + react-native@0.48.4):
1.) react-native init rnbletest
2.) npm install --save react-native-ble-plx
2.5) fix this issue before carthage/compiler gets to the RxBluetoothKit.xcodeproj file.
3.) npm install
4.) react-native link react-native-ble-plx

With version 0.6.3 your 2.5) point shouldn't be necessary.

Every command up to this point works fine and there are no errors in output. However when I try to do react-native run-ios I get an error during link:
ld: framework not found BleClientManager for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

You didn't complete whole setup. react-native link is not sufficient to use this library. You should continue your setup from point 7 as it is stated in README.md file.

Opening up the BleClientManager project and attempting to build it will result this error:
In file included from /Users/ztan/Projects/anova/reactnativeApp/rnbletest/node_modules/react-native-ble-plx/ios/BleClient.m:9: /Users/ztan/Projects/anova/reactnativeApp/rnbletest/node_modules/react-native-ble-plx/ios/BleClient.h:10:9: fatal error: 'React/RCTBridgeModule.h' file not found #import <React/RCTBridgeModule.h> ^~~~~~~~~~~~~~~~~~~~~~~~~ 1 error generated.

You probably opened  ./node_modules/react-native-ble-plx/ios/BleClient.xcodeproj, not BleClientManager. There is no point in doing that. BleClient doesn't build as a standalone static library. It is injected into your RN xcodeproj with react-native link command.

Thank you for releasing 0.6.3. Everything seems to be working for me now!

Please reopen if you have any issues. Closing for now.

I'm running into same issue ('React/RCTBridgeModule.h' file not found #import <React/RCTBridgeModule.h>) on v0.6.3 ios v10 target. iphone.
Here are my steps:
git clone git@github.com:Polidea/react-native-ble-plx.git
cp -r react-native-ble-plx/examples/ReactBLEScanner .
cd ReactBLEScanner/
yarn add react-native-ble-plx
react-native link react-native-ble-plx
#open xcode, file > open > ~/ReactBLEScanner/ios/Sniffator.xcodeproj
#Do steps 7-11 in ios section of README.md (https://github.com/Polidea/react-native-ble-plx#ios)
react-native run-ios

I then get the error. macOS 10.13. xcode Version 9.0 (9A235)
here is a full log
Any idea what I'm doing wrong?

I had the same problem with the example app. I think the example app is outdated, as last commits were done over a year ago. Creating a new app with react-native init instead of copying the example app will work.

I ran into this issue too, somehow I skipped step 7. Double check the search path in frameworks is correct.


Mobile view cuts off title

If you check the page with mobile, webpage title is cut off and slighlty out of place.
Viewable with this or with any browser on android at least:
https://search.google.com/test/mobile-friendly
Example with https://mrmierzejewski.com/
This repo's README.md has screenshot of mobile view with title being :~# and actual title on mobile is mr:~#

This is a feature not a bug :)
You can disable cutting off the title by removing the following lines (below) from static/css/custom.css.
 .site-name {
        width: 2ch;
        overflow: hidden;
        display: inline-block;
    }

But it is a good idea to add cutting off the title for mobile view as a parameter.
I will add this.

Awesome. Appreciated!

I added titleCutting parameter.


[RemoteConfig] example link is broken on readme

Hi
The link in the readme https://pub.dev/packages/firebase_remote_config:

Is broken, it points to: https://github.com/FirebaseExtended/flutterfire/tree/master/packages/firebase_remote_config/example
I believe that it should be:
https://github.com/FirebaseExtended/flutterfire/tree/master/packages/firebase_remote_config/firebase_remote_config/example
I can't find where is this readme on the repository so I am not been able to contribute that change.

Closing as the latest version (0.10.x-dev) doesn't have this issue


is it possible to pass a canvas as the source rather than an image?

I have a game that I'm drawing to an html canvas, and I'd love to be be able to use this library to do post processing on it.

So, what stops you from doing that? :)

ahh, nice!
I think my confusion came from the wording in the readme:

apply them to an Image or Canvas element

I took this to mean that you could output to an image or canvas, but it wasn't clear to me that the input could be image or canvas.

by the way, amazing work on this library. It's rare that you find software developers that make tiny things that fit in almost a page and are both powerful and immediately understable. Well done!

If it would help I could send a PR that expands the usage instructions, and try to make this more explicit. Would that be useful/welcome?

Certainly! I'm not a native speaker, so any help improving the docs is appreciated :)


in layoutViews top layout guide does not include height of the status bar.

It starts to happen, after presenting view controller and hiding status bar, then when going back showing status bar again. Even after few refreshes, topLayoutGuide includes only height of the navigation bar (44px) but not the status bar.

Please check the latest on master, or wait for the cocoapods v0.10.0 release! This should be fixed then.


Batch query from python

Thanks for building NGT, this is excellent!
I'm wondering what would be the most efficient way to compute the approximate k nearest neighbours for all data points in the index in python. I see you have a batch_insert function but I do not see an equivalent batch_query function.
The equivalent code in e.g. scikit-learn would be
import sklearn.neighbors
distances, indices = sklearn.neighbors.NearestNeighbors(n_neighbors).fit(data).kneighbors(data)

Thank you for your interest.
Although NGT does not have batch_query you mentioned, you only have to iterate search() with all of the registered objects after constructing an index.


Provide a synchroneous GraphQL client without spring-webflux

It would be nice to have a synchroneous GraphQL client like org.springframework.web.client.RestClient (provided by spring-web-VERSION.jar).
The current org.springframework.graphql.client.HttpGraphQlClient is based on org.springframework.web.reactive.function.client.WebClient and, therefore, requires spring-webflux-VERSION.jar.

We could consider a GraphQlClient that does not depend on WebClient, but we would still depend on reactor-core because of the Mono and Flux signature types. This would not make the client synchronous as outlined in the issue title. Would this still work for you?

@bclozel sounds good. This way at least org.springframework:spring-webflux resp. org.springframework.boot:spring-boot-starter-webflux will become obsolete for GraphQL apps.

@juergenzimmermann we'll consider a synchronous GraphQlClient along the lines of having RestClient and WebClient side by side, but that only adds another choice. It does not make spring-webflux obsolete for GraphQL applications. GraphQL with it's scatter-gather style handling benefits from concurrent execution, and the same can also be quite useful on the client side too if processing multiple requests.

For testing we have GraphQlTester which has a synchronous API unless you are testing subscriptions but in that case you need Reactive Streams anyway with GraphQL Java.

This is now available in 1.3.0-SNAPSHOT from https://repo.spring.io/snapshot. You can review the updated Client section, including the HTTP Sync extension backed by RestClient, and the Requests section with code snippets.
As a general comment, you can now choose between a blocking (e.g. RestClient) and non-blocking (e.g. WebClient) stack for the underlying transport. At the top-level, the GraphQlClient remains as a shared, common workflow that offers both synchronous and non-blocking style of performing requests.
If you are able to give this a try and provide feedback, that would be much appreciated!

@rstoyanchev Thank you very much, also for the updated docs!. The snapshot works perfectly.


Register Plugin

https://exchange.nagios.org/index.php?option=com_mtree&task=search&Itemid=74&searchword=activemq

"Thank you for your submission. Your Listing will be reviewed shortly by our Administrator and added to our directory once it is approved." :)


when the pre-trained model going to be launched?

Hii, when the inference code and pre-trained model you are launching?

Hii, when the inference code and pre-trained model you are launching?

Hi, thank your appreciation of our work. Since our manuscript is still in peer review, we will release our code after acceptance as soon as possible.

Thank you for the update.

I'd wish you could have a notebook to run through.
Importantly, provide a requirements.txt with main package version e.g. torch.
waiting for your pretrained model
Many thanks
!git clone https://github.com/NerdFNY/PGVTON
!pip3 install -q -r /content/PGVTON/requirment.txt
!pip3 install -U gdown
!gdown 1MxCUvKxejnwWnoZ-KoCyMCXo3TLhRuTo
!tar -xzvf viton_resize.tar.gz > /dev/null

%cd /content/PGVTON
TEST_DIR="/content/viton_resize/test"
!python main.py --data_dir {TEST_DIR} --mode eval --submodel TPIM
!python main.py --data_dir {TEST_DIR} --mode eval --submodel PTM
!python main.py --data_dir {TEST_DIR} --mode eval --submodel RSIM
!python composition.py


Errors

Application error: a client-side exception has occurred (see the browser console for more information).

why is this happening ( i tried it on multiple platforms/Devices )

This is due to scrapping I guess, I am not getting the required data from the api,
Getting data as undefined.

Currently api error:

Current api streaming error:

Oh i see, so ig it will be like that for a while ( did u checked if the vercel instance for api isn,t rate limited ? )

Nah nah this issue is from the scrapper as the key have some kind of issue,
As the route /home /:page are still working,


change rocksdb compaction style from universal to level

Codecov Report

Merging #129 into develop will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           develop     #129   +/-   ##
========================================
  Coverage    35.76%   35.76%
========================================
  Files          148      148
  Lines        25684    25684
========================================
  Hits          9187     9187
  Misses       16497    16497

Impacted Files
Coverage Δ

util/src/kvdb.rs
69.84% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Networking Request type

Fixes #10

Current coverage for CombineSchedulers is 5.74%
✅ No files affecting coverage found

Current coverage for DesignSystem is 0.00%
✅ No files affecting coverage found

Current coverage for GitHubAPIClient is 97.14%

Files changed
-
-

OfficialGitHubAPIClient.swift
95.71%
:white_check_mark:

UnofficialGitHubAPIClient.swift
100.00%
:white_check_mark:

Current coverage for GitHubAPIClientTests is 97.40%

Files changed
-
-

OfficialGitHubAPIClient.swift
95.71%
:white_check_mark:

MockAPIClient.swift
100.00%
:white_check_mark:

UnofficialGitHubAPIClient.swift
100.00%
:white_check_mark:

OfficialGitHubAPIClientTests.swift
100.00%
:white_check_mark:

Current coverage for Model is 100.00%
✅ No files affecting coverage found

Current coverage for Networking is 87.34%

Files changed
-
-

LiveAPIClient.swift
75.00%
:warning:

Request.swift
93.33%
:white_check_mark:

APIClient.swift
100.00%
:white_check_mark:

Current coverage for NetworkingTests is 91.58%

Files changed
-
-

LiveAPIClient.swift
75.00%
:warning:

Request.swift
93.33%
:white_check_mark:

NetworkingTests.swift
94.92%
:white_check_mark:

APIClient.swift
100.00%
:white_check_mark:

Current coverage for Trending.app is 16.50%
✅ No files affecting coverage found

Powered by xcov

  Generated by :no_entry_sign: Danger


Queues are not respected

Agents will run any job regardless of queue.
I tried writing a job filter to overcome this issue but I think this is a larger problem. This is related to #289
Example:
I have two processing queues:

default
mongosh

I have two agents running. One agent is ONLY listening to the "default" queue and the other is only listening to the "reporting" queue.
Agents will attempt to pick up jobs in the "default" queue even if they are a "mongosh" queue member only.
I have defined these queues because some agents have software installed that is required by specific jobs. So when an agent picks up a job incorrectly this can cause spectacular failures.

Hi @PatrickBig,
Thanks for posting.
Let me try to reproduce.

I cannot reproduce your issue, here is the code I used.
I ran one producer process and two consumer1 processes where each consumer1 process was listening to a specific queue specified in input args.
Does the setup mirror yours?
github_issue.zip

Yeah, it seems pretty similar.
I'm hosting on an ASP.NET platform though and using dependency injection. I can't imagine that would matter.
When I get back to work on Monday I'll grab my startup code for the two queues and see if there is anything odd that sticks out.

If your jobs need to run a specific queue, you need to apply the [Queue("mongosh")] (or whatever queue you need) attribute to the given job. Else it will be run on the "default". The producer needs this information as this data will be added to the job meta data

I have a v0.7.25 release ready, please let me know your findings on Monday. If I need to fix something I can add it to that release.

If your jobs need to run a specific queue, you need to apply the [Queue("mongosh")] (or whatever queue you need) attribute to the given job. Else it will be run on the "default". The producer needs this information as this data will be added to the job meta data

Yes, I was applying the [Queue("mongosh")] attribute to my jobs that needed that queue.

ok,
I will update my test setup to use the attributes

Result is the same. I cannot reproduce.
Please make sure your consumers are configured like this:
default:
services.AddHangfireServer(options =>
{
    options.Queues = new[] {"default"};
});

mongosh:
services.AddHangfireServer(options =>
{
    options.Queues = new[] {"mongosh"};
});

@PatrickBig,
Do you have any updates on this?
Thanks!

Yes, I'm still having the problem.
I spent some more time this morning digging.
I have two consumers that are configured to process different queues.
Agent 1 (default only):
services.AddHangfire(config => config
                    .UseConsole()
                    .SetDataCompatibilityLevel(CompatibilityLevel.Version_170)
                    .UseSimpleAssemblyNameTypeSerializer()
                    .UseRecommendedSerializerSettings()
                    .UseMongoStorage(mongoClient.MongoClient, mongoClient.DatabaseName, new MongoStorageOptions
                    {
                        MigrationOptions = new MongoMigrationOptions
                        {
                            MigrationStrategy = new MigrateMongoMigrationStrategy(),
                            BackupStrategy = new CollectionMongoBackupStrategy(),
                        },
                        Prefix = "hangfire",
                        CheckConnection = false,
                    }));
services.AddHangfireServer();

Agent 2 (mongosh only):
services.AddHangfire(config => config
                    .UseConsole()
                    .SetDataCompatibilityLevel(CompatibilityLevel.Version_170)
                    .UseSimpleAssemblyNameTypeSerializer()
                    .UseRecommendedSerializerSettings()
                    .UseMongoStorage(mongoClient.MongoClient, mongoClient.DatabaseName, new MongoStorageOptions
                    {
                        MigrationOptions = new MongoMigrationOptions
                        {
                            MigrationStrategy = new MigrateMongoMigrationStrategy(),
                            BackupStrategy = new CollectionMongoBackupStrategy(),
                        },
                        Prefix = "hangfire",
                        CheckConnection = false,
                    }));

services.AddHangfireServer(options =>
            {
                options.Queues = new string[] { "mongosh" };
            });

Jobs are being consumed by either queue regardless of the jobs setting.
Job1:
[Queue("default")]
public void QueueTest()
{
    Console.WriteLine("This is a job test for default");
}

// Startup code:
RecurringJob.AddOrUpdate<DefaultQueueTesting>(c => c.QueueTest(), "*/3 * * * *");

// Just queue it
BackgroundJobClient.Enqueue<DefaultQueueTesting>(c => c.QueueTest());

I'll see this job get picked up by my "mongosh" agent.
Same for mongosh
Job2:
[Queue("mongosh")]
public void QueueTest()
{
    Console.WriteLine("This is a job test for mongosh");
}

// Startup code:
RecurringJob.AddOrUpdate<MongoShellQueueTesting>(c => c.QueueTest(), "*/3 * * * *");

// Just queue it
BackgroundJobClient.Enqueue<MongoShellQueueTesting>(c => c.QueueTest());

Both agents are consuming both jobs regardless of the queue attribute

hmm,
Everything looks OK to me.
Could you try to:
create two different classes, add the QueueAttribute on class level.
explicitly configure the queue on agent1 to "default" in your call to services.AddHangfireService.
Thanks.

I did decorate at the class level with the Queue attribute and added the default queue to the startup of the other agent.
Same results.
I can't really share my setup as it's a bit too large.

ok, thanks,
Could you try to create separate projects reproducing. You could alter the projects I added earlier?

I tried updating the src to run an aspnet core app with DI, same as you posted.
Could you try this?
github_issue-2.zip

I can't reproduce it outside of my project. So it's clearly some bug within my system. I'll have to keep digging.
This is the project I created to simulate the issue.... which is kind of useless since I can't reproduce it.
HangfireIssues.zip

ok, lets keep digging then. I'll create the v0.7.25 release, and if we find something I will release fix for that.

@PatrickBig,
Did you have any luck resolving this?


python310Packages.zope-i18nmessageid: 5.1.1 -> 6.0.1; rename

Description of changes
Changelog: https://github.com/zopefoundation/zope.i18nmessageid/blob/6.0.1/CHANGES.rst

rename from zope_i18nmessageid
refactor

relates to #245383

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

4 packages marked as broken and skipped:

devpi-client
devpi-client.dist
devpi-server
devpi-server.dist

222 packages built:

apache-airflow
apache-airflow.dist
awslimitchecker
awslimitchecker.dist
backblaze-b2
backblaze-b2.dist
buildbot
buildbot-full
buildbot-ui
buildbot.dist
bump2version
bump2version.dist
certbot (python310Packages.certbot)
certbot-full
certbot.dist (python310Packages.certbot.dist)
check-esxi-hardware
deja-dup
duplicity
duplicity.dist
duply
fusesoc
fusesoc.dist
giara
home-assistant-component-tests.google
home-assistant-component-tests.local_calendar
home-assistant-component-tests.openerz
home-assistant-component-tests.rainbird
home-assistant-component-tests.reddit
mailman
mailman-hyperkitty
mailman-hyperkitty.dist
mailman.dist
pdb2pqr (python310Packages.pdb2pqr)
pdb2pqr.dist (python310Packages.pdb2pqr.dist)
privacyidea
privacyidea.dist
python310Packages.aiohttp-apispec
python310Packages.aiohttp-apispec.dist
python310Packages.b2sdk
python310Packages.b2sdk.dist
python310Packages.certbot-dns-cloudflare
python310Packages.certbot-dns-cloudflare.dist
python310Packages.certbot-dns-google
python310Packages.certbot-dns-google.dist
python310Packages.certbot-dns-inwx
python310Packages.certbot-dns-inwx.dist
python310Packages.certbot-dns-rfc2136
python310Packages.certbot-dns-rfc2136.dist
python310Packages.certbot-dns-route53
python310Packages.certbot-dns-route53.dist
python310Packages.connexion
python310Packages.connexion.dist
python310Packages.cornice
python310Packages.cornice.dist
python310Packages.cypherpunkpay
python310Packages.cypherpunkpay.dist
python310Packages.deform
python310Packages.deform.dist
python310Packages.django-simple-captcha
python310Packages.django-simple-captcha.dist
python310Packages.gcal-sync
python310Packages.gcal-sync.dist
python310Packages.ical
python310Packages.ical.dist
python310Packages.logfury
python310Packages.logfury.dist
python310Packages.okonomiyaki
python310Packages.okonomiyaki.dist
python310Packages.openerz-api
python310Packages.openerz-api.dist
python310Packages.praw
python310Packages.praw.dist
python310Packages.prawcore
python310Packages.prawcore.dist
python310Packages.pykwalify
python310Packages.pykwalify.dist
python310Packages.pypugjs
python310Packages.pypugjs.dist
python310Packages.pyrainbird
python310Packages.pyrainbird.dist
python310Packages.pyramid
python310Packages.pyramid-jinja2
python310Packages.pyramid-jinja2.dist
python310Packages.pyramid.dist
python310Packages.pyramid_chameleon
python310Packages.pyramid_chameleon.dist
python310Packages.pyramid_exclog
python310Packages.pyramid_exclog.dist
python310Packages.pyramid_mako
python310Packages.pyramid_mako.dist
python310Packages.pyramid_multiauth
python310Packages.pyramid_multiauth.dist
python310Packages.pytest-golden
python310Packages.pytest-golden.dist
python310Packages.pywbem
python310Packages.pywbem.dist
python310Packages.scrapy
python310Packages.scrapy-deltafetch
python310Packages.scrapy-deltafetch.dist
python310Packages.scrapy-fake-useragent
python310Packages.scrapy-fake-useragent.dist
python310Packages.scrapy-splash
python310Packages.scrapy-splash.dist
python310Packages.scrapy.dist
python310Packages.simplesat
python310Packages.simplesat.dist
python310Packages.slack-bolt
python310Packages.slack-bolt.dist
python310Packages.sopel
python310Packages.sopel.dist
python310Packages.testfixtures
python310Packages.testfixtures.dist
python310Packages.webargs
python310Packages.webargs.dist
python310Packages.west
python310Packages.west.dist
python310Packages.zope-component
python310Packages.zope-component.dist
python310Packages.zope-i18nmessageid
python310Packages.zope-i18nmessageid.dist
python310Packages.zope_configuration
python310Packages.zope_configuration.dist
python310Packages.zope_lifecycleevent
python310Packages.zope_lifecycleevent.dist
python310Packages.zope_size
python310Packages.zope_size.dist
python311Packages.aiohttp-apispec
python311Packages.aiohttp-apispec.dist
python311Packages.b2sdk
python311Packages.b2sdk.dist
python311Packages.certbot
python311Packages.certbot-dns-cloudflare
python311Packages.certbot-dns-cloudflare.dist
python311Packages.certbot-dns-google
python311Packages.certbot-dns-google.dist
python311Packages.certbot-dns-inwx
python311Packages.certbot-dns-inwx.dist
python311Packages.certbot-dns-rfc2136
python311Packages.certbot-dns-rfc2136.dist
python311Packages.certbot-dns-route53
python311Packages.certbot-dns-route53.dist
python311Packages.certbot.dist
python311Packages.connexion
python311Packages.connexion.dist
python311Packages.cornice
python311Packages.cornice.dist
python311Packages.cypherpunkpay
python311Packages.cypherpunkpay.dist
python311Packages.deform
python311Packages.deform.dist
python311Packages.django-simple-captcha
python311Packages.django-simple-captcha.dist
python311Packages.gcal-sync
python311Packages.gcal-sync.dist
python311Packages.ical
python311Packages.ical.dist
python311Packages.logfury
python311Packages.logfury.dist
python311Packages.okonomiyaki
python311Packages.okonomiyaki.dist
python311Packages.openerz-api
python311Packages.openerz-api.dist
python311Packages.pdb2pqr
python311Packages.pdb2pqr.dist
python311Packages.praw
python311Packages.praw.dist
python311Packages.prawcore
python311Packages.prawcore.dist
python311Packages.pykwalify
python311Packages.pykwalify.dist
python311Packages.pypugjs
python311Packages.pypugjs.dist
python311Packages.pyrainbird
python311Packages.pyrainbird.dist
python311Packages.pyramid
python311Packages.pyramid-jinja2
python311Packages.pyramid-jinja2.dist
python311Packages.pyramid.dist
python311Packages.pyramid_chameleon
python311Packages.pyramid_chameleon.dist
python311Packages.pyramid_exclog
python311Packages.pyramid_exclog.dist
python311Packages.pyramid_mako
python311Packages.pyramid_mako.dist
python311Packages.pyramid_multiauth
python311Packages.pyramid_multiauth.dist
python311Packages.pytest-golden
python311Packages.pytest-golden.dist
python311Packages.pywbem
python311Packages.pywbem.dist
python311Packages.scrapy
python311Packages.scrapy-deltafetch
python311Packages.scrapy-deltafetch.dist
python311Packages.scrapy-fake-useragent
python311Packages.scrapy-fake-useragent.dist
python311Packages.scrapy-splash
python311Packages.scrapy-splash.dist
python311Packages.scrapy.dist
python311Packages.simplesat
python311Packages.simplesat.dist
python311Packages.sopel
python311Packages.sopel.dist
python311Packages.testfixtures
python311Packages.testfixtures.dist
python311Packages.webargs
python311Packages.webargs.dist
python311Packages.west
python311Packages.west.dist
python311Packages.zope-component
python311Packages.zope-component.dist
python311Packages.zope-i18nmessageid
python311Packages.zope-i18nmessageid.dist
python311Packages.zope_configuration
python311Packages.zope_configuration.dist
python311Packages.zope_lifecycleevent
python311Packages.zope_lifecycleevent.dist
python311Packages.zope_size
python311Packages.zope_size.dist
seahub
tribler
visidata
visidata.dist

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

8 packages marked as broken and skipped:

devpi-client
devpi-client.dist
devpi-server
devpi-server.dist
python310Packages.pyramid_beaker
python310Packages.pyramid_beaker.dist
python311Packages.pyramid_beaker
python311Packages.pyramid_beaker.dist

2 packages failed to build:

privacyidea
privacyidea.dist

220 packages built:

apache-airflow
apache-airflow.dist
awslimitchecker
awslimitchecker.dist
backblaze-b2
backblaze-b2.dist
buildbot
buildbot-full
buildbot-ui
buildbot.dist
bump2version
bump2version.dist
certbot (python310Packages.certbot)
certbot-full
certbot.dist (python310Packages.certbot.dist)
check-esxi-hardware
deja-dup
duplicity
duplicity.dist
duply
fusesoc
fusesoc.dist
giara
home-assistant-component-tests.google
home-assistant-component-tests.local_calendar
home-assistant-component-tests.openerz
home-assistant-component-tests.rainbird
home-assistant-component-tests.reddit
mailman
mailman-hyperkitty
mailman-hyperkitty.dist
mailman.dist
pdb2pqr (python310Packages.pdb2pqr)
pdb2pqr.dist (python310Packages.pdb2pqr.dist)
python310Packages.aiohttp-apispec
python310Packages.aiohttp-apispec.dist
python310Packages.b2sdk
python310Packages.b2sdk.dist
python310Packages.certbot-dns-cloudflare
python310Packages.certbot-dns-cloudflare.dist
python310Packages.certbot-dns-google
python310Packages.certbot-dns-google.dist
python310Packages.certbot-dns-inwx
python310Packages.certbot-dns-inwx.dist
python310Packages.certbot-dns-rfc2136
python310Packages.certbot-dns-rfc2136.dist
python310Packages.certbot-dns-route53
python310Packages.certbot-dns-route53.dist
python310Packages.connexion
python310Packages.connexion.dist
python310Packages.cornice
python310Packages.cornice.dist
python310Packages.cypherpunkpay
python310Packages.cypherpunkpay.dist
python310Packages.deform
python310Packages.deform.dist
python310Packages.django-simple-captcha
python310Packages.django-simple-captcha.dist
python310Packages.gcal-sync
python310Packages.gcal-sync.dist
python310Packages.ical
python310Packages.ical.dist
python310Packages.logfury
python310Packages.logfury.dist
python310Packages.okonomiyaki
python310Packages.okonomiyaki.dist
python310Packages.openerz-api
python310Packages.openerz-api.dist
python310Packages.praw
python310Packages.praw.dist
python310Packages.prawcore
python310Packages.prawcore.dist
python310Packages.pykwalify
python310Packages.pykwalify.dist
python310Packages.pypugjs
python310Packages.pypugjs.dist
python310Packages.pyrainbird
python310Packages.pyrainbird.dist
python310Packages.pyramid
python310Packages.pyramid-jinja2
python310Packages.pyramid-jinja2.dist
python310Packages.pyramid.dist
python310Packages.pyramid_chameleon
python310Packages.pyramid_chameleon.dist
python310Packages.pyramid_exclog
python310Packages.pyramid_exclog.dist
python310Packages.pyramid_mako
python310Packages.pyramid_mako.dist
python310Packages.pyramid_multiauth
python310Packages.pyramid_multiauth.dist
python310Packages.pytest-golden
python310Packages.pytest-golden.dist
python310Packages.pywbem
python310Packages.pywbem.dist
python310Packages.scrapy
python310Packages.scrapy-deltafetch
python310Packages.scrapy-deltafetch.dist
python310Packages.scrapy-fake-useragent
python310Packages.scrapy-fake-useragent.dist
python310Packages.scrapy-splash
python310Packages.scrapy-splash.dist
python310Packages.scrapy.dist
python310Packages.simplesat
python310Packages.simplesat.dist
python310Packages.slack-bolt
python310Packages.slack-bolt.dist
python310Packages.sopel
python310Packages.sopel.dist
python310Packages.testfixtures
python310Packages.testfixtures.dist
python310Packages.webargs
python310Packages.webargs.dist
python310Packages.west
python310Packages.west.dist
python310Packages.zope-component
python310Packages.zope-component.dist
python310Packages.zope-i18nmessageid
python310Packages.zope-i18nmessageid.dist
python310Packages.zope_configuration
python310Packages.zope_configuration.dist
python310Packages.zope_lifecycleevent
python310Packages.zope_lifecycleevent.dist
python310Packages.zope_size
python310Packages.zope_size.dist
python311Packages.aiohttp-apispec
python311Packages.aiohttp-apispec.dist
python311Packages.b2sdk
python311Packages.b2sdk.dist
python311Packages.certbot
python311Packages.certbot-dns-cloudflare
python311Packages.certbot-dns-cloudflare.dist
python311Packages.certbot-dns-google
python311Packages.certbot-dns-google.dist
python311Packages.certbot-dns-inwx
python311Packages.certbot-dns-inwx.dist
python311Packages.certbot-dns-rfc2136
python311Packages.certbot-dns-rfc2136.dist
python311Packages.certbot-dns-route53
python311Packages.certbot-dns-route53.dist
python311Packages.certbot.dist
python311Packages.connexion
python311Packages.connexion.dist
python311Packages.cornice
python311Packages.cornice.dist
python311Packages.cypherpunkpay
python311Packages.cypherpunkpay.dist
python311Packages.deform
python311Packages.deform.dist
python311Packages.django-simple-captcha
python311Packages.django-simple-captcha.dist
python311Packages.gcal-sync
python311Packages.gcal-sync.dist
python311Packages.ical
python311Packages.ical.dist
python311Packages.logfury
python311Packages.logfury.dist
python311Packages.okonomiyaki
python311Packages.okonomiyaki.dist
python311Packages.openerz-api
python311Packages.openerz-api.dist
python311Packages.pdb2pqr
python311Packages.pdb2pqr.dist
python311Packages.praw
python311Packages.praw.dist
python311Packages.prawcore
python311Packages.prawcore.dist
python311Packages.pykwalify
python311Packages.pykwalify.dist
python311Packages.pypugjs
python311Packages.pypugjs.dist
python311Packages.pyrainbird
python311Packages.pyrainbird.dist
python311Packages.pyramid
python311Packages.pyramid-jinja2
python311Packages.pyramid-jinja2.dist
python311Packages.pyramid.dist
python311Packages.pyramid_chameleon
python311Packages.pyramid_chameleon.dist
python311Packages.pyramid_exclog
python311Packages.pyramid_exclog.dist
python311Packages.pyramid_mako
python311Packages.pyramid_mako.dist
python311Packages.pyramid_multiauth
python311Packages.pyramid_multiauth.dist
python311Packages.pytest-golden
python311Packages.pytest-golden.dist
python311Packages.pywbem
python311Packages.pywbem.dist
python311Packages.scrapy
python311Packages.scrapy-deltafetch
python311Packages.scrapy-deltafetch.dist
python311Packages.scrapy-fake-useragent
python311Packages.scrapy-fake-useragent.dist
python311Packages.scrapy-splash
python311Packages.scrapy-splash.dist
python311Packages.scrapy.dist
python311Packages.simplesat
python311Packages.simplesat.dist
python311Packages.sopel
python311Packages.sopel.dist
python311Packages.testfixtures
python311Packages.testfixtures.dist
python311Packages.webargs
python311Packages.webargs.dist
python311Packages.west
python311Packages.west.dist
python311Packages.zope-component
python311Packages.zope-component.dist
python311Packages.zope-i18nmessageid
python311Packages.zope-i18nmessageid.dist
python311Packages.zope_configuration
python311Packages.zope_configuration.dist
python311Packages.zope_lifecycleevent
python311Packages.zope_lifecycleevent.dist
python311Packages.zope_size
python311Packages.zope_size.dist
seahub
tribler
visidata
visidata.dist

error: builder for '/nix/store/dzs66p45ls7pivh7jb3wr58vkl18agp7-python3.10-factory-boy-3.3.0.drv' failed with exit code 2;
       last 10 log lines:
       > tests/test_using.py:107
       >   /build/factory_boy-3.3.0/tests/test_using.py:107: PytestCollectionWarning: cannot collect test class 'TestModel' because it has a __init__ constructor (from: tests/test_using.py)
       >     class TestModel(FakeModel):
       >
       > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
       > =========================== short test summary info ============================
       > ERROR tests/test_alchemy.py
       > !!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
       > ================== 2 deselected, 5 warnings, 1 error in 1.11s ==================
       > /nix/store/rk3g4mxrs84bv1vanqnzpdkhm73ksr0z-stdenv-linux/setup: line 1596: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix-store -l /nix/store/dzs66p45ls7pivh7jb3wr58vkl18agp7-python3.10-factory-boy-3.3.0.drv'.
error: 1 dependencies of derivation '/nix/store/c8zhrsmp1gyjmavvb9b768sjiwsl4wrr-python3.10-pytest-randomly-3.13.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/5zdlh3dynawcy45m9pgwgqysa9j9450d-python3.10-httplib2-0.21.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/3jnwkr6ag5lkbnnyjqi3gl1cryqjqy4b-python3.10-oauth2client-4.1.3.drv' failed to build
error: 1 dependencies of derivation '/nix/store/wicwkmnvxy06knvj11bkkg19hd68xz72-python3.10-google-auth-2.21.0.drv' failed to build
error: 2 dependencies of derivation '/nix/store/993czsbc26a858gdwadjp2hzqkbr30md-python3.10-privacyIDEA-3.8.1.drv' failed to build


Fix human readable bytes calculation and unit

While in the standup I noticed I had the units the wrong way around. I quickly fixed that.


Missing documentation about the Fiori Elements Test libraries

Hi together,
It's great to now allow the whole community to improve the documentation around SAPUI5 and I want to do my part 😃.
I would like to contribute the missing documentation for the FioriElements Test libraries V2 and V4. These have, in my opinion, never been given proper documentation or announced publicly.
For that I just started to write down the first steps for the V2 integration on a fork. Here I might need some input from you to bring this forward:

Is it from your point of view at all wanted to add a documentation for these topics?
Is there any technical documentation of the available functions (especially for V2) other than the JSDoc documentation in the source code?

Best regards,
Simon

Hello Simon, thanks for your contribution! We really appreciate your contribution and will look into this .

Hi @Siolto,
thank you for taking the initiative!
Since you already have a fork with content proposals I think it would be best to discuss these changes in a pull request instead of in this issue (unless it is too early to discuss your proposal).
If you open a pull request, we could refer to this issue and close it as soon as the pull request is approved.
What do you think?

Thanks for the answer. I can improve my fork and create a pull request.
However, before I invest any more work I would like to know if the TestLibrary V2 should be published for customers and partners at all. I know that within SAP this library has been used for a long time and internally documentation already exists, which I could reuse and improve. But if it is not wanted to publish this library I would only care about the missing documentation for the TestLibrary V4 as this is already available for customers and partners.
Best regards,
Simon

Hi @Siolto ,
For V4, we have the following tutorial available: https://developers.sap.com/group.fiori-elements-mockserver-opa.html
Could you please check if this helps? If not, please let me know.
For V2, the colleagues are still in discussions but will get back to you.
Best regards,
JannaLisa

Hi @JannaLisa,
thanks for the Input. I will then start with the V4 test library. When you have updates on the V2 part, just let me know :)
Should we keep this issue open as long as the status with the V2 TestLibrary is unclear or should we already close this one? Both is fine for me.
Regards,
Simon

Hello,
I checked this concern with our development team and I was unfortunately informed that currently this activity is not planned. If in case the V2 test libraries are being published in the future, we will announce the same in our what's new.

Hello,
I am adding this comment on behalf of Rohith Deraje - PO for Fiori Elements LROP/ALP for Odata V2:
The existing V2 OPA test library was primarily created for internal usage. To make it available for public consumption, the current architecture would have to be changed and they have to be standardized. It involves a huge effort that is currently not planned.
As stated in my earlier comment, if the development team decides to publish this in the future, we will announce it in our what's new.

Hello,
as a Developer from a Partner Company, i was trying to find information about the V2 OPA Test library and found this issue.
I work mainly with V2 FE Applications and it would be very helpful for us, if the Library could get published for public consumption.

Hello,
As mentioned in my comment earlier, the existing V2 OPA test library was primarily created for internal usage. To make it available for public consumption, the current architecture would have to be changed and they have to be standardized. It involves a huge effort that is currently not planned.
Since this has been determined by our PO, we unfortunately cannot publish the OPA test library yet. If ever this activity is planned for the future, we will announce it in our what's new.
For now, I kindly request you to close this issue. Thank you!

Hello,
We have had a look at this issue, but we cannot provide a solution in the near future for the provided reasons. We are now closing this issue. If you’d like to check in again with us at a later point in time, please comment below. We'll review it and reopen the conversation if necessary.
Thank you!


[Request] linux-cachyos-lts

Link to the package upstream website/repository
https://github.com/CachyOS/linux-cachyos/tree/master/linux-cachyos-lts
Utility this package has for you
i'd like to use the cachyos patches but newer kernel release introduced multiple annoying regressions for my hardware in 6.9, 6.10 and 6.11
Do you consider the package(s) to be useful for every Chaotic-Nyx user?
YES!
Do you consider the package to be useful for feature testing/preview?

[ ] Yes

Are you sure the package isn't available upstream already?

[X] Yes

Does the package's license allow redistributing it?
YES!
Have you searched the issues to ensure this request is unique?

[X] YES!

Have you read the README to ensure this package is not banned?

[X] YES!

More information
No response

Sadly, I have to choose between two things now: I either build more kernels and stop building the current one's modules, or I don't add new kernels. Currently, building all kernel modules take twice the time to build the kernels themselves.

Sadly, I have to choose between two things now: I either build more kernels and stop building the current one's modules, or I don't add new kernels. Currently, building all kernel modules take (more than) twice the time to build the kernels themselves.
EDIT: I've added polls to know how to deal with this situation:

On Telegram: https://t.me/chaotic_nyx/64
On Matrix: https://matrix.to/#/!megIDZ8R7iPe1wQwdc:ubiquelambda.dev/$YK5u0f2oqxgw4nLO2uYNmTFw8psvg6BTZHsehh5hNa8?via=ubiquelambda.dev&via=matrix.org&via=puppygock.gay

How about removing hardened version of the kernel ? :)

6.12 is around the corner, and it is expected to be the next LTS kernel version, once it's released bleeding edge repos like Arch and Nix will surely update their LTS base to it (no more 6.6).
I'd recommend reporting your bug to your distro/kernel mailing lists, if it's really a kernel problem.

Regressions happen in the kernel all the time. Next time you'll be saying this about 6.18 and 6.12, you know


Add support for cabal sandboxes

Would amount to detecting that a sandbox is present and passing in appropriate arguments to ide-backend. Could probably be added to some Cabal helper library actually.

Could probably be added to some Cabal helper library actually.

Yeah, sounds good.

The stackage sandbox package-db command may come in handy for this.


Add JVM computation for 3-core systems.

Rookie mistake, = instead of ==.  Thanks for cleaning that up.


Fix for NPE generated when the scheme would be ommited in

If the scheme would be omited in the gateway.config.xml this would result in a NPE message when trying to start the gateway

Thank you, I have changed the error message.


Instrumentation to track the timing of events or processes

Create instrumentation to track the timing of events or processes to determine when they started and ended in order to track the performance issues.

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-14890

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16151


io.sails and io.socket are undefined when connecting as cross-domain

I'm using Sails v0.12.3 and Node v6.2.1 and I'm developing a desktop client app with Electron, but I'm having limited support to sails sockets.
Including the io library script from the server (/js/dependencies/sails.io.js) or using a local copy yields the same results.
The main problem is after the io lib is loadded, my global io object doesn't have a sails or socket property. The only keys available on io are "managers", "protocol", "connect", "Manager" and "Socket".
I've succeeded connecting with a simple io.connect('http://<IP_ADDRESS>') and was able to receive messages back from the server.
I'm unable to io.socket.get or socket.get. The get method on socket is undefined.
The keys available to socket are "io", "nsp", "json", "ids", "acks", "receiveBuffer", "sendBuffer", "connected", "disconnected", "subs", "_callbacks" and "id".
I had no problems with io.socket.get in a test page served from my Sails app.
Is it an issue with sails.io or misconfiguration of my Sails app related to cross-domain?

@fernandofranca it sounds to me like maybe there's a second socket.io library getting loaded in there somewhere (that's the only way I can think of that io.sails could go missing).  Any luck with that?  Also, it could possibly be an old version of the sails.io.js client  (run sails generate sails.io.js to get the latest)  Hope that helps!

I'll check as soon as I get back to that project. Thanks


How do I write a spec test for an API method provided by Grape?

Grape is not a controller or view. An example of how to write an rspec test would be great.

Daniel, any idea how to ensure that a helper method was called from an endpoint? I'm testing my helpers in a similar way you're describing, but I have a hard time testing that get('/api/v1/foo') actually calls helper method bar. Without this, I have a hard time doing good integration testing without repeating myself.

@johnyman: did you try stubbing the module method or using the regular rspec stuff that counts calls? afterall this is just a module

The problem is which module ends up getting stubbed? I've tried doing everything from MyApi.should_receive(:bar) to Object.any_instance.should_receive(:bar) to no avail. If you set a breakpoint in the test and run
Object.descendants.select{|o| o.instance_methods.include?(:bar)}

What you'll get are all dynamic classes. This makes setting up the expectation pretty tricky.

Ok. So I don't know the answer to this. The helpers get mounted and you can no longer stub them.
I think testing the fact that a helper is called is the same as stubbing in testing a controller. It's something I personally dislike in suggested rails testing practices. The important part of an API is to avoid regressions, ie. behave the same externally. So if the helper does something meaningful, it should have an impact either on the result or on the system. For example, I have an authenticated helper - so I make sure my APIs return 401 unless the user is logged in. I also have a logger helper, so I make sure it logged an entry to the database on every call. Etc. What does knowing that the helper is called actually test?

I have more than one route which calls the same helper which does a nontrivial amount of work. The simplest example that is close to what I'm doing is: you have two routes both return {:status => some_helper} as part of the response payload, and that some_helper can return one of 5 status messages based on different conditions. My goal is to make sure that neither one of these routes regress. I also want to avoid duplicating tests for these two routes by adding the 5 tests to the helper and then ensuring that the routes call the helper. This also seems suboptimal, it's somewhat of a "house of cards" test suite, I agree with you there.
How would you go about testing something like that? This logic doesn't belong in the model; it's specific to a version of the API.

I'd copy paste the crap out of tests :)
You can generate tests too if it feels like you're repeating yourself, if your input is X and your expected result is a 403 error and if given "Z" it's 200:
  { "X" => 403, "Z" => 200 }.each_pair { |input, output|
     it "given #{input} should produce #{output}" do
        get "/api/v1/method/name?q=#{input}"
        response.status.should == output
     end
  }

That's a longer discussion, we can take it offline dblock[at]dblock[dot]org - I am very interested in this since I am giving a talk on Grape at NYC.rb next week.


Add Boltzmann-Gumbel exploration policy and fix compatibility issue

Based on the paper Boltzmann Exploration Done Right.

Also fixes a nasty compatibility issue I was running into; if you want I can separate the two changes out into separate pull requests, though if you don't care it was easier for me to just throw both changes in one.

Looks good! Thanks for the contribution.


Custom Header and Response Status Check

Hi @OutdatedGuy,
I found that this package is awesome, but in my usecase I need custom headers and response callback to determine the connection status.
So I think it would be great to add those to this package.
Please help to review it.

Hi @tatashidayat, do you plan to follow up on this PR?

Hi @OutdatedGuy, I haven't seen this PR for a while.
Let address some comments.


proposal: support deno.json as import map

I've implemented support for imports within deno.json in https://github.com/denoland/fresh/pull/1188. It works by feeding denoPlugins() from this module either the deno.json or import map location (URL). When feeding it the Deno configuration file URL, resolveImportMap() prints:
an invalid top-level key was present in the import map.
Import map diagnostics:
  - Invalid top-level key "lock". Only "imports" and "scopes" can be present.
  - Invalid top-level key "tasks". Only "imports" and "scopes" can be present.
  - Invalid top-level key "compilerOptions". Only "imports" and "scopes" can be present.

In a way, I think deno.json is an import map, as it can contain the same imports property. I propose that either:

We remove these printed errors. Con: These errors may indeed be useful.
We add support for deno.json fields to accept them without error. Con: This will mean a little more maintenance in the future as the shape of deno.json evolves.

@timreichen, gently pinging. WDYT?

Fair points. Another possible solution is add an ignoreErrors = true argument to the function. This would be non-breaking, maintain spec behaviour (by default) and offer the desired functionality. WDYT?

Actually, I may have a way around the need for any changes. I'll keep you updated.

Or why not just extract scopes and imports and pass them instead of the whole object?

Yeah, I thought the same. Fresh uses esbuild_deno_loader, so the change must be made there.

Can this be closed?

Yep. I don't think the cause of my issue lies in this module. Thanks!


Update list of prod secrets

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against 7489257b45cc8d5c24d0f1f9aa590f1302d76a64

None of this necessarily needs to block this change, but reading this document for the first time, I have a couple of thoughts..

This documentation is for the use of maintainers, rather than end-users, right? i.e: this document describes the setup of shields.io only. It would be helpful for us to clarify this. Maybe we should even store our own internal documentation for shields.io separate from documentation that is applicable to contributors or self-hosting users.
It seems like there are some other services which can consume tokens or credentials which aren't listed here (e.g: JIRA, Jenkins) which are relevant for self-hosting users but which aren't in use on shields.io. As far as I can see we don't have this list fully documented in either https://github.com/badges/shields/blob/master/secret.tpl.json or https://github.com/badges/shields/blob/master/doc/self-hosting.md#server-secrets or here. This seems like something we should improve.

It seems like there are some other services which can consume tokens or credentials which aren't listed here (e.g: JIRA, Jenkins) which are relevant for self-hosting users but which aren't in use on shields.io. As far as I can see we don't have this list fully documented in either https://github.com/badges/shields/blob/master/secret.tpl.json or https://github.com/badges/shields/blob/master/doc/self-hosting.md#server-secrets or here. This seems like something we should improve.

Agreed! The self-hosting doc is excellent, but one area I found it lacking while running my own instance was which services supported tokens, what those tokens were, etc. I think #923 is requesting something along the same lines


stamp_changelog: stamp_date does not support a user passed in date time string

For my changelogs I'm looking to include the time along with the date in the form of 2020-12-08T21:51Z. Can support for passing a string for dates be added?
So for example:
"stamp_date": "2020-12-08T21:51Z", <- takes false, true or a string..

@donileo just released in https://github.com/pajapro/fastlane-plugin-changelog/releases/tag/v0.16.0


remove duplicated CRD

duplicated CRD also defined in crd-11.yaml;
without removing one
istio-master-20190318-09-16$ kubectl create -f install/kubernetes/istio-demo.yaml hit below error in latest master branch -
Error from server (AlreadyExists): error when creating "install/kubernetes/istio-demo.yaml": customresourcedefinitions.apiextensions.k8s.io "sidecars.networking.istio.io" already exists

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
If they are not already assigned, you can assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
7113bbc4ed6610eccb6d420b9616a254ad5feecd
link
/test e2e-simpleTests-cni

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

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
7113bbc4ed6610eccb6d420b9616a254ad5feecd
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
7113bbc4ed6610eccb6d420b9616a254ad5feecd
link
/test istio-integ-k8s-tests

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

/assign @ostromart for installer owner approval.


Introducing initramfs based installer

This is a somewhat larger PR than I typically do -- but I don't think I can come up with any good way of breaking this up given how entangled the functionality of a RAW and ISO installers are. My only excuse is that it consists of 7 well structured commits that you may want to review separately (as opposed to reviewing the entire PR at once).
At any rate, what this PR accomplishes is transitioning us towards an Alpine-based initramfs installers that has a few advantages over linuxkit-based one:
0. We can finally resurrect the ARM build

We are getting to me much more efficient in the installer size
We get to get rid of annoying issues of the current installer failing with rootfs timeouts
We are no longer carrying over annoying, installer-specific boot menu options into the installed image
When running our ARM images under qemu we no longer need static device trees -- we always use whatever device tree your current qemu configuration represents dynamically
Installer itself gets to be much more flexible with things like debug_init allowing you to debug the entire process or single allowing simply booting into a single user image
Running the installer without building any physical image at all by simply running off of your host filesystem under dist//installer

The implementation here is pretty straightforward aside from one aspect: in the attempt to keep this PR small (and easy to review) we now have mkimage-iso-efi package assume two additional responsibilities:
1. building an actual initrd.img that gets loaded as a initramfs image
2. storing the resulting initrd.img in its final Docker container
The last point is especially important since it allows us to cross-assemble ARM images on x86 (and vice versa -- but who'll be doing that?).
Ultimately, the installer now consists of the following files in any filesystem that can be understood by EFI firmware:
* EFI (EFI boot entry point)
* initrd.img
* rootfs.img
* config.img
Finally, there's tons of further clean up possible now that the framework is in place. But! That will be submitted in further PRs.

Yeah, you aren't kidding about its size. Well, not the size, as much as the complexity and number of things changed. I did a first read now, but too much for a 22:20 brain. Will review again on the morrow.

Thanks @rvs for spending time on Friday explaining this to me.
Now that I understand it, I think there are 2 parts that throw me the most and that, if possible, it would be good to simplify.
mkinit
We basically are downloading two files, customizing them, and then building. Ideally, we would just upstream our patches (or variants with sufficient flexibility to meet our needs) directly to alpine. That would make the first two commits go away entirely.
We already have quite a bit of stuff that is our local modifications, which increases our maintenance cost. I have interacted with the Alpine team; Natanael and folks are pretty open to good requests, and quick to implement them.
As far as I can tell (I didn't dig very deeply into the .c code), it really is just about adding support for a rootfs. I don't know yet what it is doing, but if we can make it generic enough to upstream, that would be really good. It would be worth delaying this by a bit (and it wouldn't be too much time).
grub.cfg
As far as I can tell, you restructured the grub cfg in the third commit to make it more robust, but also included some grub changes in the fourth commit. These are not (again, as far as I could tell, so please correct me) entirely for the initramfs installer, but more robust in general, and then also add support for initramfs installer.
My questions are:

can we break the grub.cfg robustness into its own PR (yes, I am stealing a page from @eriknordmark's book; imitation is the sincerest form of flattery and all that... and he was right), and have this one just add the support for initramfs?
why are the grub changes in both 3rd and 4th commit? Or are they in different packages? Trying to understand that part.

@deitch I agree with the comment on upstreaming and I already started the process: https://github.com/alpinelinux/mkinitfs/pull/60 but that'll take time and we still need a bit of a better understanding of what parts of bigger functionality will survive. However, you make a good point that we should keep an eye on this. I've added a section to the UPSTREAM document.
On rootfs.cfg -- with enough time it may be possible to really cleanly separate what's needed for the installer from a few other changes -- but I think the benefit here doesn't really justify the cost. I can help walking anyone through the logic though -- but I think at this point I'd rather let it stay in the PR.

@rvs your initial patch to mkinitfs already has been merged in by Natanael; they really are that nimble and quick. Is there an open patch for the new features we are requesting? That might take a bit longer, but shouldn't be too much.

Hey @glguida -- super useful feedback -- all makes sense. I'll provide an updated PR tomorrow.


add space token to output files in mv mover

Thanks David - but please make the pull request to the Next branch instead (closing this)


Few details are missing

Section: Enable user delete and password update
(At this point is not that clear for "new" people)
Select the User administrator role.
(Probably something changed, but "Add assignments" is available only if you select first the ellipsis on the right side of the item.)
Select Add assignments.
In the Select text box, enter the name of the application you registered earlier, for example, managementapp1. Select your application when it appears in the search results.
I had bad experience with "search by name", but search by Application (client) ID always returns correct result.

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

ID: 45fe2896-2630-fcfa-97ed-c11f5bcdeb26
Version Independent ID: fa30e08e-3f8e-0305-a061-6d3e74bbd5de
Content: Register a Microsoft Graph application - Azure AD B2C
Content Source: articles/active-directory-b2c/microsoft-graph-get-started.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@Bro75
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the feedback. I'm updating the article with the relevant information. The article will be publish later today, and this GitHub issue will be closed automatically. If you have any questions or need further information, please open new GitHub issue.
With regard to the "Select the User administrator role", you don't have to select first the ellipsis on the right side of the item. Just click on the item opens the role page.
#please-close


Resolve 'invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE' error with boost 1.5x

https://github.com/bitcoin/bitcoin/issues/6113#issuecomment-298234393
Compilation fails on Ubuntu 16.04 using Boost 1.54 and 1.58. Fixing this single line allows for compilation to succeed. The resulting devcoind runs correctly on 64-bit linux without any other changes.

thank you


Node page need more detail info

In GitLab by @yhua123 on Sep 28, 2017, 10:31

In GitLab by @yhua123 on Nov 8, 2019, 07:38
LGTM

In GitLab by @sokril on Nov 8, 2019, 08:12
closed

In GitLab by @sokril on Nov 8, 2019, 08:12
assigned to @wknet123


ArrayBuffer Equals

describe("describe1", () => {
  it("test1", () => {
    const buf1 = new ArrayBuffer(334);
    const buf2 = new ArrayBuffer(334);
    new DataView(buf2).setInt32(0, 111);

    expect(buf1).not.toEqual(buf2);
  });
});

As the documentation says, toEqual looks at the object's fields. In the case of ArrayBuffer, looks like there's only 1 field, that is byteLength, and both objects have the same value for this field. That's why you got this result.
I think you'll need to write a custom matcher for this to work.

This issue does not have enough details to be actionable. Please open up a new issue following the reproduction steps


A segmentation fault

#11 0x0000561c765115db in Midi_Synth_Instrument::audio_callback(float*, unsigned int, void*)
    (output=0x40, nframes=2348887296, user_data=0x7fda8c03ab80) at sources/player/instrument.cc:284
#12 0x0000561c76514c64 in Audio_Device::process_cycle(float*, unsigned int)
    (this=0x7fda8c0021b0, output=0x7fda8c012010, nframes=512) at sources/player/adev/adev.cc:45
#13 0x0000561c76515201 in Audio_Device_Jack::jack_audio_callback(unsigned int, void*) (nframes=512, user_data=0x7fda8c0021b0)
    at sources/player/adev/adev_jack.cc:81

It happened while opening another JACK client as the synth played in the background.


Unable to get working

When I follow the installation instructions and try to run lua require'neuron/telescope'.find_zettels() I get the following error
Error executing vim.schedule lua callback: .../site/pack/packer/start/neuron.nvim/lua/neuron/utils.lua:27: Vim(echoerr):An error occured from running neuron query: ^[[90m   Plugins enabled: links, tags, neuronignore, uptree^[[0m

This seems to match the output I see when I run neuron new in my terminal. Is stdout being interpretted as stderrr?
$ neuron new
   Plugins enabled: links, tags, neuronignore, uptree
   Loading directory tree (1 .md files) ...
   Building graph (1 notes) ...
/home/orlando/neuron/f6d7abe3.md
$

Which version of Neuron are you using? neuron --version
The master branch is targeting neuron v1. The unstable is for neuron 1.9.4 (if I remember correctly)
See my pull request for a version for neuron 1.9.7.x

Which version of Neuron are you using? neuron --version
The master branch is targeting neuron v1. The unstable is for neuron 1.9.4 (if I remember correctly)
See my pull request for a version for neuron 1.9.7.x

Yeah the newest version installed (1.9.7)

Tested out your branch @frandsoh and the error did go away.

I have moved to version <IP_ADDRESS> of neuron and everything is working. It seems like this is the intended version that should be used.


[SPARK-27080][SQL]bug fix: mergeWithMetastoreSchema with uniform lower case comparison

What changes were proposed in this pull request?
When reading parquet file with merging metastore schema and file schema, we should compare field names using uniform case. In current implementation, lowercase is used but one omission. And this patch fix it.
How was this patch tested?
Unit test

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@xuanyuanking

Looks plausible, given the map keys are definitely lower-case. This doesn't modify the names that are returned in the schema. Maybe @cloud-fan ?

ok to test

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8651/
Test PASSed.

Test build #103207 has started for PR 24001 at commit dec978d.

Test build #103207 has finished for PR 24001 at commit dec978d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103207/
Test PASSed.

thanks, merging to master/2.4/2.3


API error when using github_team data resource causes hard error.

Terraform Version
0.9.11
Affected Resource(s)
The github_team data resource.
Terraform Configuration Files
variable "GITHUB_TOKEN" {}

provider "github" {
  token        = "${var.GITHUB_TOKEN}"
  organization = "krux"
}

data "github_team" "ci" {
  slug = "ci"
}

output "name" {
  value = "${data.github_team.ci.name}"
}

Panic Output
https://gist.github.com/joestump/540e3ce37156715f0e08f38419c3c4c5
Expected Behavior
It should pull in the team's info.
Actual Behavior
TF crashes.
Steps to Reproduce
I haven't been able to 100% nail this down other than it works for teams when I'm an owner of an organization, but doesn't for another organization that I'm just a member of.
However...
When I use the same token GITHUB_TOKEN I pass to Terraform via curl it works:
# Returns a 200 and a list of teams. Identical request above in TF fails.
curl -H "Authorization: token $GITHUB_TOKEN" https://api.github.com/orgs/krux/teams

Important Factoids
I think what's happening is that the API call to list teams is failing for an unknown reason and then TF fails hard when it hits this line:
https://github.com/terraform-providers/terraform-provider-github/blob/master/github/data_source_github_team.go#L84
I don't believe team is defined there? It should probably be return nil, err? (Sorry, I'm not great at Go, so ignore if it's a red herring.)

Hi @joestump
thanks for the report and sorry for the delay in processing it.
This appears to be a crash caused by the fact that we tried to dereference description which was nil (i.e. we expected a team to always have a non-empty description).
https://github.com/hashicorp/terraform/blob/v0.9.11/builtin/providers/github/data_source_github_team.go#L55
This was addressed in https://github.com/terraform-providers/terraform-provider-github/pull/2 which shipped last year as 0.1.0 (first release after the provider split).
For that reason I believe it's fixed and I'm going to close this issue. Let us know if the problem persists.


Add tmp dir to the .npmignore.

https://github.com/ember-cli/ember-cli/issues/4199

like: https://github.com/ember-cli/ember-cli/commit/6ac18227ea571988fa9d9950e9a1051fdd990c7c

but i actually see that tmp/ exist in .npmignore
https://github.com/HappySale/ember-cli-cloudinary-images/blob/master/.npmignore#L3
am i missing something?

Has there been a release since then?

yep you right. i did upgrade some stuff including this, but haven't release version since.
new version will be release sooner, now.
thanks!

published new version to NPM.
thanks!


Support async connection

Almost library support async operation. So please support async.
Ref: https://github.com/khuey/bb8

Try https://github.com/importcjj/mobc


[Question] After fine-tuning the LLavA model using the script finetune_lora_task.sh. How do I check the inference of the model.

Question
After using finetune_lora_task.sh I stored everything under /Output directory. How do I check the inference of this fine-tuned model?

hi @AI-Aether have you figured this out?

I'm curious too.

@AI-Aether  can you describe how to run the finetune_lora_task.sh? I have made my own dataset.
Thank


Runtime failure - cannot find module, but

Did you see the documentation relating to installation?
Yes
Have you ensured the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime?
Yes
Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
Yes, 0.30.1
If you are using npm v6 or earlier and installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
using npm v8.4.1
If you are using npm v7 or later, does the user running npm install own the directory it is run in?
Yes, running as root
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
Not using it, but tried anyway!
What is the complete output of running npm install --verbose sharp? Have you checked this output for useful error messages?
install succeeds; verbose only shows download details & expected fsevents fail (Linux container).
What is the output of running npx envinfo --binaries --system?
  System:
    OS: Linux 5.10 Alpine Linux
    CPU: (5) arm64 unknown
    Memory: 1.12 GB / 1.94 GB
    Container: Yes
    Shell: 1.34.1 - /bin/ash
  Binaries:
    Node: 17.5.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.4.1 - /usr/local/bin/npm

I'm using a node:17-alpine image running on M1 macbook.  My docker build runs without error, but once I launch my node server, I see the error below indicating the binary is missing.  However, when I check on the filesystem, I see the file referenced!
Filesystem:
/app/node_modules/sharp/build/Release # ll
total 300
drwxr-xr-x    5 root     root          4096 Feb 10 21:32 ./
drwxr-xr-x    3 root     root          4096 Feb 10 21:32 ../
drwxr-xr-x    3 root     root          4096 Feb 10 21:32 .deps/
drwxr-xr-x    2 root     root          4096 Feb 10 21:32 node-addon-api/
-rw-r--r--    1 root     root          1076 Feb 10 21:32 nothing.a
drwxr-xr-x    5 root     root          4096 Feb 10 21:32 obj.target/
-rwxr-xr-x    1 root     root        278928 Feb 10 21:32 sharp-linuxmusl-arm64v8.node*

Error message:
  ...
  /app/node_modules/sharp/lib/sharp.js:30
   throw new Error(help.join('\n'));
   ^

 Error:
 Something went wrong installing the "sharp" module

 Cannot find module '../build/Release/sharp-linuxmusl-arm64v8.node'
 Require stack:
 - /app/node_modules/sharp/lib/sharp.js
 - /app/node_modules/sharp/lib/constructor.js
 - /app/node_modules/sharp/lib/index.js
 - /app/node_modules/multer-sharp-s3/dist/main.js
 - /app/node_modules/multer-sharp-s3/index.js
 - /app/dist/utils/multer-options.js
 - /app/dist/routes/asset.js
 - /app/dist/routes.js
 - /app/dist/app.js
 - /app/dist/server.js

 Possible solutions:
 - Install with the --verbose flag and look for errors: "npm install --ignore-scripts=false --verbose sharp"
 - Install for the current runtime: "npm install --platform=linux --arch=arm64 sharp"
 - Consult the installation documentation: https://sharp.pixelplumbing.com/install
     at Object.<anonymous> (/app/node_modules/sharp/lib/sharp.js:30:9)
     at Module._compile (internal/modules/cjs/loader.js:1085:14)
     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
     at Module.load (internal/modules/cjs/loader.js:950:32)
     at Function.Module._load (internal/modules/cjs/loader.js:790:12)
     at Module.require (internal/modules/cjs/loader.js:974:19)
     at require (internal/modules/cjs/helpers.js:101:18)
     at Object.<anonymous> (/app/node_modules/sharp/lib/constructor.js:8:1)
     at Module._compile (internal/modules/cjs/loader.js:1085:14)
     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
 npm ERR! code ELIFECYCLE
 npm ERR! errno 1
 npm ERR<EMAIL_ADDRESS>start: `node ./dist/server.js`
 npm ERR! Exit status 1
 npm ERR!
 npm ERR! Failed at the<EMAIL_ADDRESS>start script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

 npm ERR! A complete log of this run can be found in:
 npm ERR!     /root/.npm/_logs/2022-02-10T21_35_38_807Z-debug.log

Yeah, that's the root of my issue - so I'm explicitly forcing 0.30.1 before multer-sharp-s3 comes in, with the intent of getting up to latest.
npm ls sharp shows me:
/app # npm ls sharp
<EMAIL_ADDRESS>/app
+--<EMAIL_ADDRESS><EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

This might be a question for the maintainers of the multer-sharp-s3 fork.
Perhaps you could create a minimal, standalone repo with the specific dependencies you're using that might allow someone else to reproduce.

Looks like there's a new version of https://github.com/ikhsanalatsary/multer-sharp-s3 with the latest sharp so closing as this was a downstream/fork issue.


Copy Paste?

Anyone know how to enable copy paste within this UITextView?
Can't seem to come up with the solution, editable, userInteractionEnabled, responder chain...
Am probably missing something simple but would appreciate a hand.
Cheers
Nik

pls ignore this.
My issue was with another class using makeKeyAndVisible when adding a subview. It knocked out the responder chain events.


obi-generated files are missing trailing newlines

Even if the template file in a project template has a trailing newline, the file generated by Obi lacks it.  This causes diff churn and real problems in git (in particular, our buildbot assumes trailing newline in all files for try builds in order for the patching to succeed).
To reproduce, I installed the gspeak-headless template, and then ran obi new gspeak-headless foo.  If I catted src/main.cpp in the generated project, it was missing a trailing newline, looking like this in my terminal:

jinja2 has an option keep_trailing_newline, see http://jinja.pocoo.org/docs/dev/api/

also, lol: https://gcc.gnu.org/ml/gcc/2003-11/msg01568.html

This might need to be fixed in every template, unless obi can set that value in some global way that all jinja2 environments inherit.

Solving this at the template level for now.