Keep getting an error when downloading a video.

RangeError: Invalid array length
    at Object.parse (C:\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

I keep this error when trying to download a video. I have tried to download it to a custom path but it's also not working.

make sure you are using latest master
destreamer.js.zip
replace, rebuild and run, paste here the log

I can't open that file but I think I'm using the latest master. I've set up everything up 10 minutes before I posted this issue.

i don't what file is that, the attached one is a zip, use 7zip or something and extract destreamer.js
replace in src in destreamer folder

@joao44289 What's your Node version? node --version
I can't reproduce this problem on any of the following -

13.13.0
12.2.0
10.20.1
8.17.0

I also wonder if this is related to the HLS stream, what if the total length returns zero? Could we maybe add some console.logs to dump all the arguments that get passed into cli-progress and ask @joao44289 to give it another go?

i don't what file is that, the attached one is a zip, use 7zip or something and extract destreamer.js
replace in src in destreamer folder

Tried that, didn't work still same error.
@snobu The version is 12.16.2

Ok, we can rule out the Node version. Can you try it with a different video? Still no go?

Ok, we can rule out the Node version. Can you try it with a different video URL? Still no go?

Still the same. Tried two other videos from separate people just to be sure and still nothing. I don't know if this is useful information, but I am logging  in my university account to download lectures my professors have uploaded there.

ok, lets try something easier
add these lines yourself to destreamer.js
at line 148 add:
console.log(process.stdout.columns);
console.log(Math.floor(process.stdout.columns / 3));
console.log(i+" "+j+" "+l);
console.log(video.totalChunks)

@kylon still the same error but I have very little coding experience so just to make sure I added those lines correctly:
if (argv.verbose)
        console.log(outputDirectories);
		console.log(process.stdout.columns);
		console.log(Math.floor(process.stdout.columns / 3));
		console.log(i+" "+j+" "+l);
		console.log(video.totalChunks)

This is how the entire if statement is after adding the lines. Just to make sure I added them correctly.

add them before if (verbose)
this will not solve the error, i need more logs
add the lines, rebuild and run and paste the logs

How do I rebuild? After I make the changed all I did was open the program through the console, do I need to do anything else?

npm run -s build

    at Object.parse (C:\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

i need all the messages

Joao_@DESKTOP-GTRV89 MINGW64 /c/destreamer (master)
$ npm run -s build
Transpiling TypeScript to JavaScript...
TSFILE: C:/destreamer/build/src/Errors.js
TSFILE: C:/destreamer/build/src/CommandLineParser.js
TSFILE: C:/destreamer/build/src/Events.js
TSFILE: C:/destreamer/build/src/Types.js
TSFILE: C:/destreamer/build/src/Metadata.js
TSFILE: C:/destreamer/build/src/PuppeteerHelper.js
TSFILE: C:/destreamer/build/src/Thumbnail.js
TSFILE: C:/destreamer/build/src/TokenCache.js
TSFILE: C:/destreamer/build/src/Utils.js
TSFILE: C:/destreamer/build/test/test.js

Joao_@DESKTOP-GTRV89 MINGW64 /c/destreamer (master)
$ ./destreamer.sh
Options:
  --help                   Show help                                   [boolean]
  --version                Show version number                         [boolean]
  --videoUrls, -i          List of video urls                            [array]
  --videoUrlsFile, -f      Path to txt file containing the urls         [string]
  --username, -u                                                        [string]
  --outputDirectory, -o    The directory where destreamer will save your
                           downloads [default: videos]                  [string]
  --outputDirectories, -O  Path to a txt file containing one output directory
                           per video                                    [string]
  --noExperiments, -x      Do not attempt to render video thumbnails in the
                           console                    [boolean] [default: false]
  --simulate, -s           Disable video download and print metadata information
                           to the console             [boolean] [default: false]
  --verbose, -v            Print additional information to the console (use this
                           before opening an issue on GitHub)
                                                      [boolean] [default: false]

Joao_@DESKTOP-GTRV89I MINGW64 /c/destreamer (master)
$ ./destreamer.sh -i "https://web.microsoftstream.com/video/bb692e32-ef4e-44d1-a4ce-4cbeaf400bee?channelId=6ae8dfa1-03a4-4464-be0f-26d62498a61e"
Using ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers

Access token still good for 24 minutes.

Fetching metadata...
RangeError: Invalid array length
    at Object.parse (C:\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

Joao_@DESKTOP-GTRV89 MINGW64 /c/destreamer (master)
$ ^C

Joao_@DESKTOP-GTRV89 MINGW64 /c/destreamer (master)
$

move the new lines to line 152, before pbar
rebuild and run
you can just paste the logs when you run destreamer

Joao_@DESKTOP-GTRV34I MINGW64 /c/destreamer (master)
$ npm run -s build
Transpiling TypeScript to JavaScript...
TSFILE: C:/destreamer/build/src/Errors.js
TSFILE: C:/destreamer/build/src/CommandLineParser.js
TSFILE: C:/destreamer/build/src/Events.js
TSFILE: C:/destreamer/build/src/Types.js
TSFILE: C:/destreamer/build/src/Metadata.js
TSFILE: C:/destreamer/build/src/PuppeteerHelper.js
TSFILE: C:/destreamer/build/src/Thumbnail.js
TSFILE: C:/destreamer/build/src/TokenCache.js
TSFILE: C:/destreamer/build/src/Utils.js
TSFILE: C:/destreamer/build/test/test.js

Joao_@DESKTOP-GTRV34I MINGW64 /c/destreamer (master)
$ ./destreamer.sh
Options:
  --help                   Show help                                   [boolean]
  --version                Show version number                         [boolean]
  --videoUrls, -i          List of video urls                            [array]
  --videoUrlsFile, -f      Path to txt file containing the urls         [string]
  --username, -u                                                        [string]
  --outputDirectory, -o    The directory where destreamer will save your
                           downloads [default: videos]                  [string]
  --outputDirectories, -O  Path to a txt file containing one output directory
                           per video                                    [string]
  --noExperiments, -x      Do not attempt to render video thumbnails in the
                           console                    [boolean] [default: false]
  --simulate, -s           Disable video download and print metadata information
                           to the console             [boolean] [default: false]
  --verbose, -v            Print additional information to the console (use this
                           before opening an issue on GitHub)
                                                      [boolean] [default: false]

Joao_@DESKTOP-GTRV34I MINGW64 /c/destreamer (master)
$ ./destreamer.sh -i "https://web.microsoftstream.com/video/bb692e32-ef4e-44d1-a4ce-4cbeaf400bee?channelId=6ae8dfa1-03a4-4464-be0f-26d62498a61e"
Using ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers

Access token still good for 4 minutes.

Fetching metadata...
RangeError: Invalid array length
    at Object.parse (C:\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

and to make sure I did it correctly
const outDirsIdxInc = outputDirectories.length > 1 ? 1:0;
    for (let i=0, j=0, l=metadata.length; i<l; ++i, j+=outDirsIdxInc) {
		console.log(process.stdout.columns);
		console.log(Math.floor(process.stdout.columns / 3));
		console.log(i+" "+j+" "+l);
		console.log(video.totalChunks)
        const video = metadata[i];

yes, but i see no logs, maybe this is an unrelated error due to something else...
Metadata.ts
con you please add:
console.log('1') line 50
console.log('2') line 52
console.log('3') line 54
again rebuild and paste logs

The download command or the rebuild command?

when you run destreamer, add -v option

$ ./destreamer.sh -v -i "https://web.microsoftstream.com/video/fc7f80ea-e380-44db-8e2a-f34b64389a08?list=user&userId=82be014f-7d7f-4f3e-9079-d13113f1ade6"
Using ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers

Video URLs:
[
  'https://web.microsoftstream.com/video/fc7f80ea-e380-44db-8e2a-f34b64389a08?list=user&userId=82be014f-7d7f-4f3e-9079-d13113f1ade6'
]

Access token has expired.
Launching headless Chrome to perform the OpenID Connect dance...
Navigating to login page...
We are logged in.
Wrote access token to token cache.
At this point Chromium's job is done, shutting it down...

Fresh access token dropped into .token_cache
Video GUIDs:
[ 'fc7f80ea-e380-44db-8e2a-f34b64389a08' ]
Fetching metadata...
Calling https://euno-1.api.microsoftstream.com/api/videos/fc7f80ea-e380-44db-8e2a-f34b64389a08?api-version=1.4-private
1
2
3
[ 'videos' ]
RangeError: Invalid array length
    at Object.parse (C:\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

mmh
comment all the lines where you see pbar in destreamer.js inside the for loop
//const pbar = new cliProgress.SingleBar({
//            barCompleteChar: '\u2588',
 //           barIncompleteChar: '\u2591',
 //           format: 'progress [{bar}] {percentage}% {speed} {eta_formatted}',
 //           barsize: Math.floor(process.stdout.columns / 3),
 //           stopOnComplete: true,
 //           hideCursor: true,
 //       });

// pbar.stop();

 //pbar.start(video.totalChunks, 0, {
//            speed: '0'
//        });

//pbar.update(currentChunks, {
 //               speed: data.bitrate
//            });

//pbar.stop();

rebuild, run with -v

$ ./destreamer.sh -v -i "https://web.microsoftstream.com/video/fc7f80ea-e380-44db-8e2a-f34b64389a08?list=user&userId=82be014f-7d7f-4f3e-9079-d13113f1ade6"
Using ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers

Video URLs:
[
  'https://web.microsoftstream.com/video/fc7f80ea-e380-44db-8e2a-f34b64389a08?list=user&userId=82be014f-7d7f-4f3e-9079-d13113f1ade6'
]

Access token still good for 37 minutes.

Video GUIDs:
[ 'fc7f80ea-e380-44db-8e2a-f34b64389a08' ]
Fetching metadata...
Calling https://euno-1.api.microsoftstream.com/api/videos/fc7f80ea-e380-44db-8e2a-f34b64389a08?api-version=1.4-private
1
2
3
[ 'videos' ]
RangeError: Invalid array length
    at Object.parse (C:\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

this make no sense, please attach your destreamer.ts

destreamer.zip

can you also attach destreamer.js in build/src?
are you sure the build was successful?

Okay, I am very sorry but I just realized I was doing the changed to the wrong file. I was in the src folder not the build/src. I will try to add the lines now to the correct file.

the file was correct, you apply the changes in src folder
build/src is the file you obtain when you build
do all changes in src, not build/src
but i would like to see your build/src/destreamer.js because you still have a message that should not be there

I added these lines to the destreamer.js on build/src
console.log(process.stdout.columns);
console.log(Math.floor(process.stdout.columns / 3));
console.log(i+" "+j+" "+l);
console.log(video.totalChunks)

And this was the log after building and running. I hope I did everything correctly and I'm sorry for wasting your time preciously.
$ ./destreamer.sh -v -i "https://web.microsoftstream.com/video/fc7f80ea-e380-44db-8e2a-f34b64389a08?list=user&userId=82be014f-7d7f-4f3e-9079-d13113f1ade6"
Using ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers

Video URLs:
[
  'https://web.microsoftstream.com/video/fc7f80ea-e380-44db-8e2a-f34b64389a08?list=user&userId=82be014f-7d7f-4f3e-9079-d13113f1ade6'
]

Access token still good for 49 minutes.

Video GUIDs:
[ 'fc7f80ea-e380-44db-8e2a-f34b64389a08' ]
Fetching metadata...
Calling https://euno-1.api.microsoftstream.com/api/videos/fc7f80ea-e380-44db-8e2a-f34b64389a08?api-version=1.4-private
[ 'videos' ]
RangeError: Invalid array length
    at Object.parse (C:\Users\Joao_\destreamer\node_modules\cli-progress\lib\options.js:48:38)
    at new SingleBar (C:\Users\Joao_\destreamer\node_modules\cli-progress\lib\single-bar.js:8:24)
    at downloadVideo (C:\Users\Joao_\destreamer\build\src\destreamer.js:121:22)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Unhandled error!
Timeout or fatal error, please check your downloads directory and try again

no there is a misunderstanding, do all the changes in src folder
just attach build/src here

src.zip

ok, something is wrong, your build is old
do all changes in src folder and run npm run -s build in destreamer root folder
destreamer.js in build/src should reflect the changes

I've never tested this in MINGW, can we move all testing to pure cmd.exe please so we don't introduce even more variables?

I've never tested this in MINGW, can we move all testing to pure cmd.exe please so we don't introduce even more variables?

omg, missed that line o.o !
that could be the reason why cli-progress goes crazy, does it have a different terminal?

@kylon @snobu I changed to cmd and it's working well now

Cool, @kylon i wonder if we can detect MINGW and throw a panic from init()

ninja'd lol, i was asking you the same
we need to kill mingw or change barsize calculation so that it does crash
i see no special platform in node for mingw
i would like to see the colum size of mingw terminal, maybe we can just fix that and everything will work

I'll just add a note to the readme for now.

Just out of curiosity, any way of improving the download speed? Right now it's at 300kbits/s but my internet can do way more.

Yes, we're looking into ways to improve that, it's on our radar for sure.

Yes, we're looking into ways to improve that, it's on our radar for sure.


Mastodon and Gitlab do not show

The themes Alternative and Blog X do not show Mastodon and GitLab (new function socialNetworks()).

Fixed.


dependabot: add default label and get prs once a week

dependabot: add default label and get prs once a week

I don't think this will change much? Label is already applied by default btw.

 But I found out there's not much to configure in this config file :-). Still thought these changes would be good. Wouldn't want to have new PRs on daily basis. Once a week is enough to worry about those.
One thing that's difficult currently is how to test the PRs, especially if you want to test them together. Not sure if it's possible, but maybe we could create a dependy update branch or something where they keep getting updated. Every once in a while we could test that branch en merge into dev if succesful.

Should probably be closed in favor of #1943 ?

I would prefer weekly schedule instead of live

I don't have a strong opinion. Not sure if it'd help to switch to weekly.
Also, if in the meantime there is a newer version detected for a certain lib, dependabot is smart enough to detect there is a open PR for that lib, and updates that that PR instead of opening a new one.
Any other mods have a strong opinion here? I think @alles-klar was actually all about live updates. Not sure about the others.

The weekly thing is more that we don't get new PRs (for dependencies without an existing PR) every day. They pollute the default view when you go to the PR tab. But as I said it's more important to find a view that it doesn't go updating dependencies from from 1.x to 9999.x

Fixed both. But now I am just copying some parts from the dashboard to the config here. Might be better to copy all, or just forget about the yml file and only use the dashboard.

On second thought, copying everything into the file makes no sense. The @ignore this @ignore that comments in the PRs nicely integrate with the dashboard (I presume). So maybe just set it to weekly in the file manage the rest in the dash?

There was nothing to do on the dashboard. It is all out of the box.
I'd suggest we just move it to weekly if you like, and leave the rest as it was.

If you want this effective ASAP, you'd also have to put a PR up against master, as the default active branch is the one that triggers the thing.

If #2002 brings us in a stable/mostly up-to-date situation where dependabot doesn't create lots of PRs we might keep it at daily after all.

Dependabot has quieted down now, so let's leave it as is - closing.


A caral server cannot use multiple GPUs at the same time

A caral server cannot use multiple GPUs at the same time.
carla 0.9.11 docker+nvidia docker mod.
I can use one of the GPUs, which I can control, but I can’t use more than one at the same time, and the current GPU utilization rate is not high, only 30-40%.
command
sudo docker run -d -p 2000-2002:2000-2002 --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=0 carlasim/carla:0.9.11 /bin/bash -c 'SDL_VIDEODRIVER=offscreen SDL_HINT_CUDA_DEVICE=0 ./CarlaUE4.sh -ResX=800 -ResY=600 -nosound -windowed -opengl'

NVIDIA_VISIBLE_DEVICES
Does anyone have the same problem as me？
Platform:Ubuntu 20.04.1 LTS
Carla version: 0.9.11
NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.32.03  Sun Dec 27 19:00:34 UTC 2020
1d:00.0 VGA compatible controller: NVIDIA Corporation Device 2204 (rev a1)
1d:00.1 Audio device: NVIDIA Corporation Device 1aef (rev a1)
b4:00.0 VGA compatible controller: NVIDIA Corporation Device 2204 (rev a1)
b4:00.1 Audio device: NVIDIA Corporation Device 1aef (rev a1)

I have noticed that a single carla process cannot effectively use multiple GPUs at once.  I'm not sure if SLI is supported on Linux like it is on Windows with the underlying UnrealEngine, which would explain this.
Worse still, it will not automatically 'load balance' on multi-gpu systems and will just throw multiple server runs onto gpu 0, even if gpu 0 is pegged at 100% and the other GPUs are idle.  As you discovered, you can use docker or SDL environment variables (outside of docker) to manually restrict it when running with OpenGL.  Unfortunately, using environment variables appears broken with vulkan, at least when using UE 4.25 (which, to be fair, is unsupported by CARLA).
To be fair, I think this is more of an UnrealEngine thing than a CARLA thing.

I have noticed that a single carla process cannot effectively use multiple GPUs at once.  I'm not sure if SLI is supported on Linux like it is on Windows with the underlying UnrealEngine, which would explain this.
Worse still, it will not automatically 'load balance' on multi-gpu systems and will just throw multiple server runs onto gpu 0, even if gpu 0 is pegged at 100% and the other GPUs are idle.  As you discovered, you can use docker or SDL environment variables (outside of docker) to manually restrict it when running with OpenGL.  Unfortunately, using environment variables appears broken with vulkan, at least when using UE 4.25 (which, to be fair, is unsupported by CARLA).
To be fair, I think this is more of an UnrealEngine thing than a CARLA thing.

Okay, thank you for your answer. The bad thing is that it seems impossible to use multiple GPUs in a short time.

Might want to ask over at UnrealEngine Answers, they recently helped me with UnrealEngine GPU selection questions.

Okay.This is a good idea, I will try

@bernatx could you have a look at this please?

@yuexishuihan , did you discover anything about leveraging multiple GPUs for CARLA?  The closest we have come is just running multiple client/servers on the same GPU (i.e. larger number of independent simulations).

Not yet, I am currently exploring adding/modifying assets in carla, including cars,
Maps, weather, etc.

I'm very interested in multi GPU or multi computer CARLA simulation! If anyone has gotten multippe gpus to work or has tried to distribute the carla computing please let us know!!!!

any progress?
I am doing realtime 4 camera output in HIL, and I found it's impossible

I'm still very interested in this! Unreal doesn't seem to handle multi-GPU simulation very well, so solving this problem is non-trivial.

Still very interested in this feature and looking forward to https://github.com/carla-simulator/carla/tree/bernat/multi_gpu !!!


Feature/cwall 247 vp UI

@sanderPostma I merged in latest develop to resolve the conflicts

Hmmz I see my commits from last week were not pushed yet so I understand the ping's now...

This one still needs work now. A test in contact-entities is failing now after I merged in SDK-10

That is fixed in latest SDK-10


Cannot write to file 'C:\flutter' specified for property 'outputFiles' as it is a directory

that's the error message. it's been showing it since the upgrade.

that's my flutter doctor message.
please help.. thanks in advance

Hi @gourav-varma
could you provide flutter run --verbose log?
Please don't post screenshots of text, post the text instead.
Screenshots are not searchable and it's not possible to copy-past text out of it.

Hi @gourav-varma
could you provide flutter run --verbose log?
Please don't post screenshots of text, post the text instead.
Screenshots are not searchable and it's not possible to copy-past text out of it.

Yeah, will keep that in mind from the next time.
I installed my previous version and its working now.
Thanks


fix: Proxy to defineProperty in ApiFormState

Change Proxy in ApiFormState to defineProperty's get descriptor since v7.13.0

thanks for the PR, would you like to fix the conflict?


feat(docs/tests): EOF: Update tracker, add unimplemented tests

🗒 Description
Updates the EOF tracker to mark all implemented tests (and implement missing ones).
The only section covered so far by this PR is EIP-3540/Validation.
File tests/prague/eip7692_eof_v1/eip3540_eof_v1/container.py has also been deleted and all test cases are now incorporated into tests/prague/eip7692_eof_v1/eip3540_eof_v1/test_container_validation.py
@winsvega I think no coverage should be lost for this PR and actually it should increase.
🔗 Related Issues
None
✅ Checklist

[x] All: Set appropriate labels for the changes.
[x] All: Considered squashing commits to improve commit history.
[x] All: Added an entry to CHANGELOG.md.
[x] All: Considered updating the online docs in the ./docs/ directory.
[x] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[x] Tests: A PR with removal of converted JSON/YML tests from ethereum/tests have been opened.
[x] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[x] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

I thought just know if you hesitate to enable coverage check on each pr, lets keep it optional. So you need touch coverage file to trigger it

Here is the coverage run, using new coverage script:
https://github.com/ethereum/execution-spec-tests/pull/774

@pdobacz @shemnon I think this is good to go, could you approve if you think this is ok? thanks.


Merge feature/run-bundle into master: Add FBC support to run bundle and run bundle-upgrade commands

Closes #5593
Description of the change:

Add FBC support to run bundle and run bundle-upgrade commands by create a file-based catalog (FBC) on the fly by generating the bundle, package and channel blobs, if an index image is not provided by the user (i.e. for a default index image quay.io/operator-framework/opm:latest) and serve it over a gRPC port.
For run bundle: If an index image is provided through the flag, then bundle image will be inserted to the index by appending the bundle contents (rendered bundle image) to the index that's converted to a declarative config and this index containing the bundle will be served over a gRPC port.
If bundle already exists in the index, then we error out and not serve the index image (which is consistent with the existing SQLite behavior).
Generated FBC will be validated and converted to a string format.
Infer the label type on the index image and indicate there's an FBC label through registry pod for container creation.
Added a new container creation command for images that have FBC label on them. For images without the label, old commands (opm registry add and opm registry serve) that use SQLite under the hood will be called. So support for both (FBC/SQLite) exist at the moment. For more details, please refer to run bundle design proposal.

For run bundle-upgrade: Handle upgrade for both scenarios when an operator bundle is installed using run bundle command and also installed traditionally via OLM. For more details, please refer to run bundle upgrade design proposal.
Motivation for the change:
https://github.com/operator-framework/operator-sdk/issues/5593
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[x] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

Signed-off-by: rashmigottipati<EMAIL_ADDRESS>

@everettraven thanks for your review. e2e tests for upgrade are more involved as we need to create a local registry to be able to use for testing purposes. Will consider doing those in a follow-up. For now, I prefer not to block this PR on e2e tests.


solid-starts multiple adapters, explicit adapter configuration and build output

issue
by default start will build with the 'node' adapter.
Just adding an adapter package( solid-start-* ),  will change the adapter to one of the installed adapters.
with multiple adapters added, one will be picked *alphabetically
consideration

do not automatically pick adapter, make configuration explicit( at least when there are multiple adapters installed)

add ability to specify one or more adapters as build target as cli options
and/or configuration.

pnpm build --adapter=netlify
pnpm build --adapter=netlify --adapter=static

export default defineConfig({
  plugins: [solid(
    { adapters: {
      'solid-start-cloudflare-workers':{
        dist: './dist/cloudflare-workers'
      },
      'solid-start-static':{
        dist: './dist/static'
      }
    } }

  )],
});

isolate  and normalize build target for each adapter, so builds can easily be deployed to different targets
there is no convention to where adapters should output the build, so we can find overriding adapters and non conventional name target.

static => ./dist
solid-start-cloudflare-workers => ./dist
vercel => ./.vercel
netlify => ./netlify

repro (auto picking "random" adapter )
pnpm create solid
....
pnpm install

pnpm build            # will build with `node`

pnpm add solid-start-static
pnpm  build          # will build with 'static'

pnpm add solid-start-netlify
pnpm  build          # will build with 'netlify'

pnpm add solid-start-vercel
pnpm  build          # will still use 'netlify'   'n'>'v'

Yeah the reason for the automation was for build pipelines where they auto pick up and people didn't configure it. This was an added feature. There is an env variable you can set to pick adapter. I think it is START_ADAPTER.
I have definitely been hit unexpectedly by this behavior myself. I think in that case environment detection might be better default in the multi-adaptor case where it isn't specified. But that will probably take some doing.

Yeah the automatic detection is rarely helpful and more trouble than its worth. Also it should be explicit over implicit. And the env variable can be used to override I guess for temporarily changing what adapter is used

I would like to have more output configuration options too, I'm often using Nx monorepos and the standard place to put the build output is in a totally separate folder from the source. It's not just for aesthetics but it also makes it easier to hook into Nx's build caching system.
/dist
  /apps
    /my-solid-app <-- output folder
/apps
  /my-solid-app <-- source

Also I stumbled on the Vavite project recently, maybe it could be useful for the idea of configuring multiple adapters at the same time: https://github.com/cyco130/vavite/tree/main/packages/multibuild-cli

Ok removed the auto adapter thing.


Is there a sample for React Native App?

Hi @kenyasue , @ivoperic ,
Does Spika support React Native?
Can you give me a sample React Native app with Spika, please?
Supporting for React Native would be a nice feature.
Thank you very much.

Hi @ithieund
Unfortunately Spika doesn't support React Native.
Regards Ivo.


[Feature Request]: Allow decreasing of space around the plot

Hi,
Would it be possible to add a parameter that allows decreasing the white space in the margins?
Best
Manish

This feature may be a lot more complex, I don't have more time recently. If you must use this feature recently, I encourage you to implement the feature.
Thanks to use pheatmap！


Futher fixes for using with Yocto Morty

…el edison
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

What I got from Andy (see my wiki):

The following lines need to be changed since the keyword mmc has changed to raw.  Default the original image (on emmc) will boot. But I add (manually):
fw_setenv edsboot 'setenv bootargs ${bootargs_edsboot}; run load_edsboot; run boot_edsboot'
fw_setenv bootargs_edsboot 'tty1 console=ttyS2,115200n8 root=/dev/mmcblk1 rootfstype=ext4 systemd.unit=multi-user.target hardware_id=00'
fw_setenv load_edsboot 'load mmc 0:9 0x100000 bzImage-initramfs'
fw_setenv boot_edsboot 'zboot 0x100000'

And when I interrupt boot, I type run edsboot
Not sure what the best way would be. I do like that if something goes wrong, I can boot to a known good image.
Also, right now I just flipped the switch to core-i7. Everything compiles, but U-Boot won't link (that is as it compiles i386 image). Any ideas how we should add multilib to this recipy?

For now I removed U-Boot from the image on my morty-64 branch. Now it builds (without U-Boot) kernel + initramfs and rootfs image. As is you need to build U-Boot manually. The 64bit version seems to be booting fine but haven't tested everything.

The following lines need to be changed since the keyword mmc has changed to raw. For example inside u-boot:
Yeah, that's how we have it too https://github.com/resin-os/resin-edison/blob/master/layers/meta-resin-edison/recipes-bsp/u-boot/files/edison.env#L8 and https://github.com/resin-os/resin-edison/blob/master/layers/meta-resin-edison/recipes-bsp/u-boot/files/edison.env#L10

Will do that in a follow-up PR.
Does the current Pr make sense? Anything to change here? Or do you think it's inappropriate?

On a holiday now, will check when I return (in a week), thanks for the PR

Hi, have you had a chance to look over this?

Hi Florian, I have working on the 64bit branch, but will switch back to 32bits shortly and try your patches. Thanks for your patience. Ferry

Hi Florian, I merged your PR. I also reverted your change to edison.env and changed that in further commits as I want (for now) the default to be to boot Intel original kernel and rootfs, so at least something will boot when I screw up. To boot the vanilla kernel and morty rootfs I press  on boot and run 'run edsboot'.
So everything still builds, as before. And still U-Boot won't boot, also as before. I really don't know what is wrong. Let me know if you can flash U-Boot and if it boots. I really would like to know what I am doing wrong. Up to know I can only successfully update U-Boot by following the manual process as described on my wiki.

Hi. Thanks for merging it. I haven't found at that time what was wrong with that particular uboot version. I may revisit it soon, I am currently focusing on other things and we curently use an older kernel and uboot which suits our customers' needs for the time being. This being said, if I get to the bottom of it I will send PRs to your repository as before.


lcov report

Hi there,
I would love to use this tool with codecov.io but I think I will need a lcov report, can you tell me what needs to be done than I will try to have a look into it 👍

Hi @DanielMSchmidt, I totally agree with you: generating a report in the lcov format would be great, e.g. we would be able to use services as codecov.io to make a pull request to fail when the flow coverage trend is going down (as we do with regular code coverage).
Generating such a report is technically possible, the main issues that have currently identified are:

translating the coverage data (eg. convert the coverage data collected from being "expressions based", that is how flow provides this data, to a "line based" lcov file, I started to look into this and it is pretty simple to convert the expression ranges into a line by line report)

as described in #20, it seems that a regular lcov report is also supposed to contain a line by line report of the covered lines (which, as an example, exclude the lines that are inline comments and shouldn't impact the line by line coverage), and flow doesn't currently output the "covered expressions ranges", a patch has been proposed by @clarkbw in facebook/flow#3231 (and apparently imported here https://phabricator.intern.facebook.com/D4861141, but I've not a facebook account and I'm not sure if it is publicly accessible with a regular facebook account)

we could probably workaround facebook/flow#3231 by processing the AST and build our own knowledge of the covered expression ranges, but it would much simpler (and definitely faster and safer) if flow can optionally provide this data given that it has already collected this knowledge internally.
The proposed patch from facebook/flow#3231is pretty small and some time ago I tried it and I've been able to easily build a custom flow binary from the patched sources, and so it is totally possible to use the patch to start to prototype the feature in more details in the meantime, and I would be definitely more than happy to help you on it!
Let me know if the above info are useful to you as a starting point.
Thanks a lot for your interest and help on this project! :heart:

This will be out in the latest version of flow (woo!)

Appears to be available in flow v0.72.0

Not trying to be naggy, just honestly a bit lost in the above: where does that leave this? Can we get LCOV reports today? Or does this just mean it's possible to build now?

iirc means it's possible to build now


Couldn't bind to persistent volumes

After following all the instructions, I got the following error:
SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "wp-lv-claim", which is unexpected.
Typing "kubectl get pv" shows the two persistent volumes created - "local-volume-1" & "local-volume-2"

It looks like at least one of your persistent volumes is bounded to a deployment that is not from our example. Try to run kubectl get pv and make sure the persistent volumes are bounded to "mysql-lv-claim" and "wp-lv-claim".
If you don't want to delete your existing deployments and you ran out of persistent volumes to use, you can simply create another persistent volume with a different name and redeploy your Wordpress's PersistentVolumeClaim.
For example, you can modify and add the following code to your local-volumes.yaml file (Note each persistent volume should have a different name and hostPath). Then you should have enough persistent volumes for your Wordpress and MySQL after you run kubectl create -f local-volumes.yaml.
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: local-volume-x
  labels:
    type: local
spec:
  capacity:
    storage: 20Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: /tmp/data/lv-x
  persistentVolumeReclaimPolicy: Recycle

Hi, I tried it, still the same issue. the claim can't be binded to the storage.

If I deploy it to my free cluster (1 worker node), it actually worked. But previously, I was trying to deploy it to my paid cluster with 3 worker nodes, and it couldn't bind. Is it possible to make this work for multi-worker nodes deployment?

For Bluemix Paid Account, all your storage and network resources are managed in your SoftLayer account. The best way is to subscribe Auto Scale on your SoftLayer account. Then whenever you create a persistent volume claim, SoftLayer will auto-generate an persistent volume for you (and this volume will be deleted along with your persistent volume claim). So you don't have to do kubectl create -f local-volumes.yaml.
If you don't have administrator role to subscribe Auto Scale on your account, then you need to create a new file storage on your SoftLayer portal and Authorized it to your Kubernetes Subnet. Then you will able to bound your persistent volumes on your cluster.

Thanks @Tomcli. Maybe we should add a subheading 'Limitation' and add that this works on a 'Free' or 'Lite' cluster. Plus we can also add advanced steps if someone has paid cluster access

Thanks for all the comments and help! I will close this issue. It will be good if you can develop another tutorial to illustrate how to run in a multi-nodes high availability scenario. It will be very useful for larger deployment.


Video tutorial: how to build a Candoia app?

Create a video tutorial that describes the process to build a Candoia app. This tutorial could also use the same format, script that the web-based tutorial would use.

Video is available at: https://www.youtube.com/watch?v=dgYM7zxhddc


Amplify Deployment Failing in CodeCatalyst due to Bootstrap Error

Environment information
System:
OS: Linux 4.14 Amazon Linux 2023
CPU: (2) x64 Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
Memory: 6.39 GB / 7.68 GB
Shell: /bin/bash
Binaries:
Node: 18.19.0 - /usr/local/bin/node
Yarn: undefined - undefined
npm: 10.2.3 - /usr/local/bin/npm
pnpm: undefined - undefined
NPM Packages:
@aws-amplify/auth-construct: 1.3.2
@aws-amplify/backend: 1.5.1
@aws-amplify/backend-auth: 1.2.0
@aws-amplify/backend-cli: 1.3.0
@aws-amplify/backend-data: 1.1.5
@aws-amplify/backend-deployer: 1.1.5
@aws-amplify/backend-function: 1.7.1
@aws-amplify/backend-output-schemas: 1.4.0
@aws-amplify/backend-output-storage: 1.1.2
@aws-amplify/backend-secret: 1.1.4
@aws-amplify/backend-storage: 1.2.1
@aws-amplify/cli-core: 1.1.3
@aws-amplify/client-config: 1.5.0
@aws-amplify/deployed-backend-client: 1.4.2
@aws-amplify/form-generator: 1.0.3
@aws-amplify/model-generator: 1.0.8
@aws-amplify/platform-core: 1.1.0
@aws-amplify/plugin-types: 1.3.0
@aws-amplify/sandbox: 1.2.3
@aws-amplify/schema-generator: 1.2.4
aws-amplify: 6.6.6
aws-cdk: 2.163.1
aws-cdk-lib: 2.163.1
typescript: 5.4.5
AWS environment variables:
AWS_CONTAINER_CREDENTIALS_FULL_URI = http://<IP_ADDRESS>:40133/codecatalyst/credentials/role/e7f9c211-5e3a-4163-91cf-474447206254
AWS_EXECUTION_ENV = AWS_ECS_EC2
AWS_BRANCH = main
AWS_APP_ID_STAGING = d3r7kyik0avkl4
AWS_REGION = us-west-2
AWS_APP_ID_PRODUCTION = d3druhmos9yuvs
AWS_CONTAINER_TOKEN_ENDPOINT = http://<IP_ADDRESS>:42727/caws/credentials/token/e337e182-3dfb-4adc-9b31-10d4d6a4e126
AWS_CA_BUNDLE = /codecatalyst/bootstrap/default-certs/cacert.pem
AWS_STS_REGIONAL_ENDPOINTS = regional
AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
No CDK environment variables

Describe the bug
I'm encountering a "BootstrapNotDetectedError" when deploying my Amplify app in a CodeCatalyst workflow, even though the cdk bootstrap command runs successfully and reports "Environment aws://{YOUR_ACCOUNT_ID}/{YOUR_REGION} bootstrapped (no changes)."
BootstrapNotDetectedError: This AWS account and region has not been bootstrapped.
Resolution: Run `cdk bootstrap aws://{YOUR_ACCOUNT_ID}/{YOUR_REGION}` locally to resolve this.
Cause: Has the environment been bootstrapped

Reproduction steps
Create a CodeCatalyst workflow from Amplify Gen 2 in the Cross-account deployments page
cross-account-deployments
    Configuration:
      Steps:
        - Run: npx aws-cdk@latest bootstrap aws://{YOUR_ACCOUNT_ID}/{YOUR_REGION}
        - Run: export CI=1
        - Run: npm ci
        - Run: npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID
        - Run: if [ $AWS_BRANCH = "main" ]; then curl -X POST -d {}
            "`webhookUrl`&operation=startbuild" -H
            "Content-Type:application/json"; fi

Hi @ddotx :wave: , thanks for raising this! When following the cross-account deployments guide, Step 2 involves deploying a fullstack Gen 2 app. When you deploy a Gen 2 app from the Amplify console for the first time in an AWS region, the service handles the bootstrapping process. I'm curious why you are re-running the bootstrap from the CodeCatalyst workflow?
A couple of additional notes:

Amazon CodeCatalyst is currently only available in two AWS regions i.e. us-west-2 and eu-west-1. Therefore, you can setup this pipeline in only those regions.
I'd recommend reviewing this thread to rule out a couple of issues:

Setting up an AWS profile for the correct region
SSM parameter named /cdk-bootstrap/hnb659fds/version exists in the AWS region

Thank you. After I added the environment variables AWS_ACCESS_KEY_ID ,  AWS_SECRET_ACCESS_KEY and AWS_REGION , the workflow worked.

I also created a custom policy using this link https://docs.aws.amazon.com/codecatalyst/latest/userguide/ipa-iam-roles.html


New problem candidates

@robertodr can you merge this, or alternatively, you can grant me write access

@ilfreddy think I invited you to own this repo

Maybe we can leave it here, then merge it with all new exercises after the semester is over? Then we can add the things that was successful and remove the things that was not as successful

@robertodr can you merge this, or alternatively, you can grant me write access

You were invited as an admin a couple of months ago, if I recall correctly. Check your email

Can you resend the invitation?


SEP-38 now requires a config file to indicate which contexts should be tested

What
SEP-38 now requires a config file to indicate which contexts should be tested.
Why
The SEP-38 GET /price and POST /quote request parameters have a new mandatory field called context, that can be set to "sep6" or "sep31". With the new configuration file, Anchors can choose which context(s) should be used in the tests.
Addresses https://github.com/stellar/stellar-anchor-tests/pull/86#discussion_r887137207.

Preview is available here:http://stellar-anchor-tests-pr87.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-anchor-tests-pr87.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-anchor-tests-pr87.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-anchor-tests-pr87.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-anchor-tests-pr87.previews.kube001.services.stellar-ops.com/


Smarter sources.list/.repo removal

Tests passed for this pull request.
Refer to this link for build results: http://jenkins.ceph.com/job/teuthology-pull-requests/834/


Update dependencies so that npy_array builds out of the box.

Update dsharlet/array to e2ce5b and use http_archive.
Update abseil-cpp to 20230802.1.

Remove gflags.
Remove glog.

Update googletest to 1.14.0.

Closing as it was merged by copybara.


Add support for mon_command input buffer

Implementation for https://github.com/ceph/go-ceph/issues/24

Cool, thanks!


Update footer

Description
Currently

© 2021 Your Company, Inc. All rights reserved.

Change to
© 2024 EddieHub

Screenshots
No response
Additional information
No response

Closing because a duplicate https://github.com/EddieHubCommunity/CreatorsRegistry/issues/23


Flaky Test: Kueue visibility server when A subject is bound to kueue-batch-admin-role Should return an appropriate error

What happened:
The End To End Suite: kindest/node:v1.30.0: [It] Kueue visibility server when A subject is bound to kueue-batch-admin-role Should return an appropriate error expand_less failed.
{Expected
    <v1.StatusReason>: Forbidden
to equal
    <v1.StatusReason>: NotFound failed [FAILED] Expected
    <v1.StatusReason>: Forbidden
to equal
    <v1.StatusReason>: NotFound
In [It] at: /home/prow/go/src/sigs.k8s.io/kueue/test/e2e/singlecluster/visibility_test.go:506 @ 07/11/24 16:47:21.333
}

What you expected to happen:
Never seen these errors.
How to reproduce it (as minimally and precisely as possible):
https://prow.k8s.io/view/gs/mkubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kueue/2584/pull-kueue-test-e2e-main-1-30/1811439474740039680
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Kueue version (use git describe --tags --dirty --always):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/kind flake

cc @PBundyra

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/directory/pull-kueue-test-e2e-main-1-27/1811394213485481984

/assign


Calling CreateDomain() with the same UUID concurrently would return error (V2)

InternalServiceError{Message: CreateDomain operation failed. Inserting into domains table. Error: gocql: not enough columns to scan into: have 1 want 4

This bug cannot be stable repro. We we fix it when it becomes an issue.
The test is in common/persistence/cassandraMetadataPersistenceV2_test.go#TestConcurrentCreateDOmain()

already fixed


chore(libsinsp): improve UX of plugin init schema validation

Signed-off-by: Jason Dellaluce<EMAIL_ADDRESS>What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area libsinsp
What this PR does / why we need it:
This improve the UX of the init config schema automatic validation as follows:

Parse the schema before the config string. This way, users will not get confused
about errors coming from their configuration if the plugin has development issues.
Stubbing empty configurations as empty json objects. This way, a default JSON value
is always provided, and is possible to pass empty configs to plugins with all-optional
schemas.

Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jasondellaluce
To complete the pull request process, please assign fntlnz after the PR has been reviewed.
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

/ok-to-test

LGTM label has been added.  Git tree hash: 196b8af7a5d2b4619289b3b2dba7aebdd323d29a

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
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:

OWNERS [leogr]

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


remote scheduler hangs...

RemoteScheduler#run will end up in an infinite loop if this flag is not set to true while returning from this if condition

Thanks for the fix. LGTM

merging if there is no more discussions


Added in the Rapsberry Pi and Linux info.

Still need to update for proper version and formatting!

@christinepham we've moved the docs project.
Pull this branch: https://github.com/MCGallaspy/ka-lite/tree/sphinx-docs
Make your changes there, and then open a PR on that repository.


Can't run extraterm on imac running Catalina

When I try to run extraterm, it says it needs at least MacOS 11.0, the problem is on older hardware there is not upgrade path towards 11.0. Is there a solution ?

If you are talking about "Extraterm" and not the "Extraterm Qt" version, then no, there isn't much I can do about it.

I meant ExtratermQT

Picture Paints a thousand words

I just had a quite look into this. Extraterm does declare its minimum version as 10.15 deep within its Info.plist file. So something else is tripping up. I suspect it might be the launcher executable. Building all the parts on a macOS 10.15 machine might be a solution, but GitHub Actions is completely removing support for building on 10.15 in a couple weeks. Given that I can't test this myself, it being a small set of affected users, and that macOS 10.15 (or earlier) support is drying up everywhere, I can't fix this problem.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit d319085:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-09-08-56-30 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-09-08-56-30

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


World Server Crash

Certain cases where the reagent banker is attempting to locate an item that no longer exists causes a world server crash.
AddGossipItemFor(player, GOSSIP_ICON_MONEY_BAG, GetItemIcon(itemEntry, 30, 30, -18, 0) + GetItemLink(itemEntry, session) + " (" + std::to_string(entryToAmountMap.find(itemEntry)->second) + ")", itemEntry, gossipPageNumber);
#2  0x0000000000ab009b in AddGossipItemFor (player=player@entry=0x7fad9c4fcd40, icon=icon@entry=6, text=<error: Cannot access memory at address 0x232d2d2d2d2d2d2d>, sender=0, sender@entry=11370, action=2206496960) at /home/x/azerothcore-wotlk/src/server/game/AI/ScriptedAI/ScriptedGossip.cpp:30

When you say an item no longer exists, do you mean that the item_template for this entry has been deleted from the database?

I'm assuming a little here but I think it's when the gossip menu is navigated very quickly and an item no longer exists within storage as it was recently withdrawn however gossip is attempting to locate it? Possibly a clause to handle events where an item cannot be located would help?


[BUG] : Submenu stays open if not clicked and closed manually

Issue:

When the submenu is not clicked and closed manually it stays open. And also when its open when clicked anywhere else it doesnt
close, instead it should close when clicked outside of that specific area.

Steps to Reproduce :

Click the windows button
Hover over to the side panel and Click the settings buttons
Now click directly outside anywhere except for the windows opened section
Click  again on the windows button
You will see the submenu for settings stayed open

Fix Plan :

To solve this issue, I will create a custom React hook that handles the following:

Detecting clicks outside the submenu area to trigger closing.

Properly managing the submenu state so that it closes when required (either when the user clicks outside or when manually interacted
with).

Additional Context :

Please refer to the attached video demonstrating the bug.

https://github.com/user-attachments/assets/dcf66240-cfc3-45c7-9b45-8af9494a839f

Please assign this issue to me under hacktoberfest

Hi @shreysachani  you can make a pr i'll merge it if it solves this issue

Will start working on this issue.

best of luck 🤞🏻

I see you one is assigned to this issue can you please assign this issue to me under hacktoberfest

you can directly start by making pr


_schema.then is not a function after upgrading

Version
4.0.4
Environment info
Environment Info:

  System:
    OS: macOS 10.15
    CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
  Binaries:
    Node: 12.11.1 - /usr/local/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.12.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 77.0.3865.120
    Firefox: 69.0
    Safari: 13.0.2
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
Run vue ui
What is expected?
Starts the UI
What is actually happening?
Output is
🚀  Starting GUI...
 ERROR  TypeError: _schema.then is not a function
TypeError: _schema.then is not a function
    at new ApolloServerBase (/Users/alex/.config/yarn/global/node_modules/apollo-server-core/dist/ApolloServer.js:209:46)
    at new ApolloServer (/Users/alex/.config/yarn/global/node_modules/apollo-server-express/dist/ApolloServer.js:59:9)
    at module.exports (/Users/alex/.config/yarn/global/node_modules/vue-cli-plugin-apollo/graphql-server/index.js:141:18)
    at ui (/Users/alex/.config/yarn/global/node_modules/@vue/cli/lib/ui.js:52:3)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

I've tried to remove .vue-cli-ui and .vuerc but the error still persists
Update: tried to remove and install @vue/cli again, no changes

I ran into this as well in a project that was configured to use Apollo Server.  I was able to install a matching version of graphql package (14.5.8) and then remove the nested node_modules/vue-cli-plugin-apollo/node_modules/graphql package.

I fixed it by upgrading yarn to v1.22

To update yarn isn't enough for me.

I manually delete yarn folder, restart the computer, and npm install --global --production windows-build-tools

the same problem, waiting for answer

I completely uninstalled vue-cli from my machine and installed it again. The error disappeared but then I got a version mismatch with the vue-template-compiler.
For solving this I deleted the node_modules folder in /Users/myuser/.config/yarn/global/ and the yarn.lock and then did a yarn global add @vue/cli again.
So the last step alone could already do the trick I guess :D
System:
    OS: macOS 10.15.3
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 12.12.0 - /usr/local/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.14.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 80.0.3987.149
    Firefox: 73.0
    Safari: 13.0.5

I'm not exactly sure what causes this issue. But it seems to be caused by graphql version mismatch according to https://github.com/apollographql/apollo-server/issues/3381.
Because of dependency hoisting by various other packages, such issues happens more often when the package is installed globally.
So it's worth trying to delete the global node_modules folder and reinstall.


makemkv broken after upgrade to 23.11 - "Failed to execute external program 'ccextractor' from location '/usr/local/bin/ccextractor'"

Describe the bug
I am using makemkv to rip a DVD to a series of mkv files. When I try to do so I get the following error for every file it tries to convert into an MKV:

...
Failed to execute external program 'ccextractor' from location '/usr/local/bin/ccextractor'
Failed to save title 1 to file /home/tom/Videos/MANNIX_S1_D2/B1_t01.mkv
...

This affects both the GUI and command-line versions (makemkvcon) of the app. There is a workaround for the GUI that's not great but no workaround for the command-line version.
Steps To Reproduce
Steps to reproduce the behavior:

Open `makemkv' gui on a computer with access to a DVD
For example, why not Season 1, Disc 1 of "Mannix". It's a really cool show.
Click on the button to convert the titles on the disc to mkv's.
Select the titles that you want using the check boxes and don't unselect any of their respective sub-check boxes.
Press the go button.

Expected behavior
1 MKV to be written to disc for each selected title.
Screenshots
n/a
Additional context
There is a workaround. When selecting the title checkboxes in the gui expand them and un-select the subtitles checkbox. This works around the issue but is a problem if you need subtitles.

Also, I tried fixing this by installing ccextractor but that didn't seem to have any effect.

Finally, there is no /usr/local/bin in the NixOS world, so it's not like I can just go out and create a symlink there :-)
Notify maintainers

@titanous
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.61-hardened1, NixOS, 23.11 (Tapir), 23.11.1494.b4372c4924d9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"home-manager-23.11.tar.gz, nixos-23.11"`
 - channels(tom): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Hi there, I'm trying to reproduce this but can't so far.
ccextractor seems vendored with makemkv and is compiled as mmccextr.
I tested running on your nixos-version commit b4372c4924d9 with makemkv debug mode enabled with a random dvd with an empty ~/.MakeMKV
subtitle info before clicking write
Track information
Type: Subtitles
Language: English
Codec: Closed Captions → Text
Output format: Text subtitles ( Lossy conversion )
MKV Flags: Default

Debug log with successful save:
CCX001: Launching /nix/store/plfmh0c191zsv7sj2pwhmgy9pmyc2xxi-makemkv-1.17.5/bin/mmccextr
001003:0020 DEBUG: Code 0 at z6jq?_t<B1y?.8j.EyG^=::29393631
001003:0020 DEBUG: Code 0 at z6jq?_t<B1y?.8j.EyG^=::29393631
CCX001: CCExtractor 0.88, Carlos Fernandez Sanz, Volker Quetschke.
CCX001: Teletext portions taken from Petr Kutalek's telxcc
CCX001: This is a reduced-functionality version optimised for DVD closed captions transcoding.
CCX001: --------------------------------------------------------------------------
CCX001: -----------------------------------------------------------------
CCX001: Reading from standard input
CCX001: Analyzing data in CCExtractor's binary format
CCX001: Sending captions to stdout.

Is app_ccextractor set in ~/.MakeMKV/settings.conf?
Was this working for you in 23.05? Is this the only disc that won't work?

That's so weird. When I look in my ~/.MakeMKV/settings.conf file I see the following:
app_Key = "somethingWeird"
app_ccextractor = "/usr/local/bin/ccextractor"

I have no idea how or why I had app_ccextractor defined. Also, I've used this app for well over a year with previous versions of NixOS and this config file hasn't been edited since December of 2022 :-).
So yes, this does appear to be a config issue on my side @qubitnano . Thank you for the help!


How to Change Humanoid Appearance or Config Using env.reset()?

Hi! I am currently using Habitat 3.0 to establish a social navigation task that involves multiple humanoid agents in the environment. I have generated several episodes, where each episode specifies the corresponding URDF and motion data files for each humanoid agent based on their IDs.
My goal is to utilize env.reset() to automatically switch to the next episode, updating the configurations for each humanoid agent (e.g., appearance and motion files) dynamically, similar to how other tasks operate. To achieve this, I attempted to update these configurations using habitat.get_config() and invoked sim.reconfigure() within the simulator to apply the changes. However, this approach did not succeed, as the humanoid agents’ appearances remained unchanged across episodes.
I suspect that the issue lies in my implementation of the sim.reconfigure() function, which is largely based on the settings from RearrangeSim.
Could you kindly advise on how to dynamically update these humanoid configurations during episode transitions? I would greatly appreciate any guidance or suggestions you can provide.
Thank you for your time and assistance.

Hi @wsakobe!
You may want to check out this early implementation: https://github.com/facebookresearch/habitat-lab/blob/9783e3d744175adc6bc93a58e8c182d2b83948a9/habitat-hitl/habitat_hitl/environment/avatar_switcher.py
The code is not yet factored in, but it should do the trick for handling your use case.


Closes #2378 add test for get_imputation_target_date()

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[ ] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[ ] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[ ] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[ ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[ ] Review the Cheat Sheet. Make any required updates to it by editing the file inst/cheatsheet/admiral_cheatsheet.pptx and re-upload a PDF version of it to the same folder.
[ ] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[ ] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[ ] Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[ ] Link the issue in the Development Section on the right hand side.
[ ] Address all merge conflicts and resolve appropriately
[ ] Pat yourself on the back for a job well done! Much love to your accomplishment!

@bms63 @millerg23 I was mistaken in that the internal functions weren't being loaded in the test suite, I probably had somethin wrong with my session, nothing needs to be done to address this, just regular ol' additional tests

I assume failing checks are around ERROR message updates. Happy to Approve this, once checks running clean.

@zdz2101 @millerg23 is this one good to merge?

@zdz2101 @millerg23 is this one good to merge?

Should be once cicd goes through!


add missing import for shark_sd.spec

L

do we need this for shark_sd_cli.spec ?

do we need this for shark_sd_cli.spec ?

It's already there in shark_sd_cli.spec. @powderluv


My db.py file doesn't contain an archive definition

My db.py file doesn't contain an archive definition.
What should I do?
This is the error:

And this is my db.py file:

My db.py file doesn't contain an archive definition. What should I do?

check all module names for any errors that they are correct and verify all modules are properly installed with the packages dependencies necessary for your project.

make sure there is no extra "PLUGINS/requirements/INSTRUMENTS/TOOLS etc that may be required for importing the archive module

fixed a few typos you had in there but now this should run correctly

`from dataclasses import dataclass
from pathlib import Path
This class represents a simple database that stores its data as files in a directory.
class DB:
"""A simple key-value store, where keys are filenames and values are file contents"""
def __init__(self, path):
    self.path = Path(path).absolute()
    self.path.mkdir(parents=True, exist_ok=True)

def __contains__(self, key):
    return (self.path / key).is_file()

def __getitem__(self, key):
    full_path = self.path / key
    if full_path.is_file():
        with full_path.open("r", encoding="utf-8") as f:
            return f.read()
    raise KeyError(key)

def get(self, key, default=None):
    try:
        return self[key]
    except KeyError:
        return default

def __setitem__(self, key, val):
    full_path = self.path / key
    full_path.parent.mkdir(parents=True, exist_ok=True)

    if isinstance(val, str):
        full_path.write_text(val, encoding="utf-8")
    else:
        # if val is neither a string nor bytes, raise an error.
        raise TypeError("val must be either a str or bytes")

dataclass for all dbs:
@dataclass
class DBs:
memory: DB
logs: DB
preprompts: DB
input: DB
workspace: DB
`

Thanks @uthpala1000


More parameter

When I'm writing the script, i have a question about the parameter.
In String.indexOf case,
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/indexOf
we can have two parameters with one optional.
In 1-liners script
https://github.com/1-liners/1-liners/blob/master/module/indexOf.js
We can have only one parameter.
People cannot use the second parameter

Yeah, we have a rule that every function has a fixed arity. If you really need a two-param variant of a function, just write a new function.
There are good reasons for this! Try this: [1, 2, 3].map(parseInt) and try to figure out why!

By given your example, we can rewrite them to
map(parseInt, [1, 2, 3])
I'm still not figure out why, but map(function something(v) {return v;}, [1, 2, 3]) make more sense than map([1, 2, 3], function something(v){ return v;}) (gut feeling)

hmm.. This must be a frequently asked question in this project.

The “data as last arg” convention comes from pure functional languages and makes lots of sense when partial application and currying are at stake. Even if it looks foreign to most of the JS community.
There’s some more reasoning at ramda which is a similar library but all-inclusive – with automatic currying among other things.

Good point. Let's thinking in functional.
Do you mind giving me some examples why currying is important to functional language?

Check out stoeffel/awesome-fp-js for awesome resources about fp in js :smiley:

Ok thanks @stoeffel

I can recommend  https://medium.com/@collardeau/intro-to-functional-programming-concepts-in-javascript-b0650773139cc as a starting point.

404 page?


283 cant compare offset naive and offset aware datetimes

Looks good to me

@bmihelac why didn't travis say anything?

Not sure why there is no info here, but it does pass:
https://travis-ci.org/django-import-export/django-import-export/builds/66177357


Polynomial

Hi! Sorry for posting that so late.
I think I have some bad lines of code, because my program doesn't print anything.

Ok, so before we worry about anything being printed or not, you need to work a lot more on your design

How's it going with this? Do you need any extra help?

I made some modifications ,but i think at least one function doesn't work properly.

At the polynomial problem I made some modifications at the swap function which didn't have any effect because of the pass-by-value rule in java.The main problem after debugging was that my function scalarMultiplication modifies the polynomials and I don't understand why.
I also push the both assignments at chapter 2 and some modifications at the second one.

I can't see the changes on the polynomial assignment - are you sure you committed them? Also, Java doesn't quite really pass things by value (only primitives!) however, it's more like.. passing a reference by it's value. Tricky, I know, but you'll get the hang of it

I 'm a little bit confused with this pull request.I think it will be better to close it and create a new one.

I will look over your code tomorrow (out of town today) and merge it after giving you some answersanswers.

I am merging this - your code looks a lot better, good work.

Thanks !Anyway I had a little bug.

What bug? tell me about it, I'll look into it

I put some comments into the code.The scalarMultiplication function affects the polynomial that it multiples.

Tell me if you have any other questions!
Also, because I merged this request, you'll need to create a new one - luckily it will make things easier for me as this one was already a bit messy :smile:


CI: execute for rendering

I cannot test this locally due to some install issues for healpy, so will use CI to iron out the issue. I'm sorry for the notification spams for those of you watching this repo.
We need to handle dependencies sensibly. At minimum:

[ ] deal with requirements centrally

[ ] cleanup and comment out pip install cells

[ ] if possible add all of them to the image we use

[ ] have failing job status when there are tracebacks in rendering. (It should still generate the HTML outputs so we are able to check things, but the job status should be a red one)

Current status:

🔴 All have issues with the install/import cells mentioned above

🔴 Forced photometry:

Errors out with:

---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
Cell In[23], line 2
     1 #proove we can do this for one object
----> 2 calc_instrflux(*paramlist[0][1:])
     4 #same thing, different syntax
     5 # calc_instrflux(paramlist[0][1], paramlist[0][2], paramlist[0][3], paramlist[0][4], paramlist[0][5], paramlist[0][6])

Cell In[21], line 54, in calc_instrflux(band, ra, dec, stype, ks_flux_aper2, img_pair, df)
    49 subimage, bkgsubimage, x1, y1, subimage_wcs = cutout.extract_pair(
    50     ra, dec, img_pair=img_pair, cutout_width=band.cutout_width, mosaic_pix_scale=band.mosaic_pix_scale
    51 )
    53 # find nearby sources that are possible contaminants
---> 54 objsrc, nconfsrcs = find_nconfsources(
    55     ra, dec, stype, ks_flux_aper2, x1, y1, band.cutout_width, subimage_wcs, df
    56 )
    58 # estimate the background
    59 skymean, skynoise = photometry.calc_background(bkgsubimage=bkgsubimage)

NameError: name 'find_nconfsources' is not defined

🔴  Light curve generator

Errors out with:

AttributeError: module 'numpy' has no attribute 'msort'

🟠 Light curve generate, large scale

Works, but rendering is really ugly. Too many progressbar and other broken line wrappings, etc.

🟢 Light curve classifier

Looks reasonable

🔴 AGN Zoo

errors out with

AttributeError: `np.Inf` was removed in the NumPy 2.0 release. Use `np.inf` instead.

I cannot test this locally due to some install issues for healpy

Do you know where the healpy requirement is coming from? I searched the whole repo but see no mention of it. I had thought we already switched everything to use hpgeom instead. (And we switched because of the install issues with healpy.)

Do you know where the healpy requirement is coming from?

Yes, it's coming from nway. The issue is that there are no wheels for older OSX with ARM chips, thus it tries to build it from the source and fails. I'm sure I could fix it by diving into the errors, but instead pinged the developers if they are willing to release more wheels
(Using CI to fix issues is I feel legit here, as we don't really need to support OSX and Windows for these notebooks; though this/similar issue will come up with lsdb/hipscat too when those pull in healpy as a dependency).

@bsipocz, how about using our fornax images in the CI? I did a little experiment to test that it can be done in this test-actions repo. It seems to work fine.
It pulls the images from the public aws ECR (in this case, tractor-develop) and use docker run code inside the image.
A few things may not run because we are outside the fornax system (e.g. restricted buckets etc.), but we can make the notebooks robust against that as part of their portability.

how about using our fornax images in the CI

Yes, I think this is a sensible idea, we may already have an issue about it. So far all the issues I run into while doing this PR are unrelated to the image (and e.g. the missing install of tractor; besides that I don't expect any image related problems).

Now this is placed on top of #318 and #321

The ML_AGNzoo notebook now runs into a file access issue: https://github.com/nasa-fornax/fornax-demo-notebooks/issues/322

Given #324, I'm adding that into the exclude list, too. So the scope of this PR will be scaled back to:

have execution infrastructure in place
perform the execution for those notebooks that work out of the box
leave all problematic ones out rather than hold back merging this.

The latest commit of da1ccc154cccb191f42057f26e0db7b957d70608 should close #331


JWT - Error with refresh token

Hi,
I've a problem with refresh token, I don't modify the code but I have this error:
2018-04-04T07:40:57.452Z - error: refreshJWTToken - Error: InvalidRefreshToken: E_INVALID_JWT_REFRESH_TOKEN: Invalid refresh token bf4c53cdd9dc51cdsfdf54df5d4f5df454fds6faf546764ed09253fb1211215752d0ec5e855b3aa0d8b1abtq+pMMXjR4C85sC/FOZjSTXYJYD4FD45FDSF4XgF8512asPY8uc8EKe
I've edited the example of error ;)
const jwt = await auth.newRefreshToken().generateForRefreshToken(params.refreshToken, true)

Hey @pirmax! 👋
Could you please provide a way to reproduce this issue?

Yup a repo will be nice

Closing since no answer from issue reporter.

Hi,
I use this repository https://github.com/gammpamm/plasma-nuxt
The problem become when the JWT token is expired (configured in auth.js in config directory).
The token is expired, so, the refresh token is in while refresh... I don't know why :/
Thanks.

Hi guys,
comming back to this issue ;)
Using the withRefreshToken works fine
await auth
  .withRefreshToken()
  .attempt(uid, password)

The token is created successfully in mongo db but
But when we want to ask a new refresh token (not expired yet for sure since we don't have the E_JWT_TOKEN_EXPIRED exception) we have instead
E_INVALID_JWT_REFRESH_TOKEN: Invalid refresh token

Digging into @adonijs/auth/src/Schemes/Jwt.js at generateForRefreshToken(line 328)
It seems the use is never found...
So using our proper models in this function resulted in successfully generate the new acces token.
Instead of using current implementation
async generateForRefreshToken (refreshToken, jwtPayload, jwtOptions) {
    const user = await this._serializerInstance.findByToken(this.Encryption.decrypt(refreshToken), 'jwt_refresh_token')
    if (!user) {
      throw CE.InvalidRefreshToken.invoke(refreshToken)
    }

    const token = await this.generate(user, jwtPayload, jwtOptions)

    /**
     * If user generated a new refresh token, in that case we
     * should revoke the old one, otherwise we should
     * set the refreshToken as the existing refresh
     * token in the return payload
     */
    if (!token.refreshToken) {
      token.refreshToken = refreshToken
    } else {
      await this.revokeTokensForUser(user, [refreshToken], true)
    }

    return token
  }

we just add our models to fetch the target token
async generateForRefreshToken (refreshToken, jwtPayload, jwtOptions) {

    const User = use('App/Models/User')
    const UserToken = use('App/Models/UserToken')

    const plainToken = await UserToken.findBy('token', this.Encryption.decrypt(refreshToken))
    const user = await User.find(plainToken.user_id)

    if (!user) {
      throw CE.InvalidRefreshToken.invoke(refreshToken)
    }

    const token = await this.generate(user, jwtPayload, jwtOptions)

    /**
     * If user generated a new refresh token, in that case we
     * should revoke the old one, otherwise we should
     * set the refreshToken as the existing refresh
     * token in the return payload
     */
    if (!token.refreshToken) {
      token.refreshToken = refreshToken
    } else {
      await this.revokeTokensForUser(user, [refreshToken], true)
    }

    return token
  }

Do you know why ?
Thanks for your awesome job and your time,
Cheers!

I still have this issue. code repo at https://bitbucket.org/saeedbiz9s/security/src/master/


if install python3.5 with add python to path setting. get ImportError: No module named 'prman'

Install python3.5 with add python to path setting.
Now has 2 environment:
C:\Users\litel\AppData\Local\Programs\Python\Python35-32\Scripts
C:\Users\litel\AppData\Local\Programs\Python\Python35-32\
Now install prman-for-blender plugins, Will get ImportError: No module named 'prman' error.
If temporary delete that 2 environment. Install has no broblem. and now add 2 environment back. Plugins still works fine.
This little bad user experience can be fix?

I'm assuming from that path above you have 32 bit version?  RenderMan is only 64 bit compatible.

Was that the issue?

python install setting.
enable add python to path.
now see environment:

now install plugin will get error message.
=============
if delete the 2 line environment, install plugin ok.
Now add 2 line environment back, plugin work no problem.
this only effect when plugin install step.
is can be fix?

my english not good, soo sorry.

No that's fine.  I understand.
Based on this path used:
C:\Users\litel\AppData\Local\Programs\Python\Python35-32\
This seems to imply you're using a 32 bit version of blender or python.
Renderman only works on 64 bit.
On Sun, Apr 24, 2016 at 9:39 AM, kokutoukiritsugu<EMAIL_ADDRESS>wrote:

my english not good, soo sorry.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/issues/243#issuecomment-213997766

--
<EMAIL_ADDRESS>508-274-8700


Support recurring monthly amount

Context
When connecting their wallet, users can opt-in for a recurring monthly amount.
Todos

[ ] When receiving the CONNECT_WALLET message (from popup to background) verify if the recurring property is true:

[ ] if true: generate a monthly repeating interval having the current date as a start date (ISO 8601);
[ ] if false do not generate the interval - meaning that the user opted in for a one time amount;

[ ] Make sure to specify the interval when requesting the outgoing payment grant (https://openpayments.guide/apis/auth-server/operations/post-request/#request-body);

Aiming to have this ready for review by the end of this week, 19 Apr.

On track to go into review tomorrow, Fri, 19 Apr.


missing variable name

Hello,
I am getting the exeception Caused by: net.sourceforge.htmlunit.corejs.javascript.EvaluatorException: missing variable name
but there is no missing variable, the website is up and running...

This is an error reporter from the JavaScript engine. At first call the same site with your browser and check in the developer console if there is the same error.
And please provide more details to give me a chance to reproduce the problem.

Hey, so the console shows the same error, but i can use the website normally...

Ok, means there is a bug in the web page.
Htmlunit tries to mimic the browser as good as possible. If you use an web client without setting any options. But there is one exception. Htmlunit was written as test tool an therefore the handling of is exceptions is different. You have to set the setThrowExceptionOnScriptError option to false to ignore is errors and proceed with the is execution like browsers do

Thank you very much

gerne


moon init breaking

karkowg@kepler:~/web$
uname -a && node --version && npm --version
Linux kepler 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
v6.10.3
3.10.10

karkowg@kepler:~/web$
moon init caroles
======= MOON =======
    [?] Author  Gustavo Karkow
    [?] Description  A Moon App
    [?] Moon Version  0.9.0

    ⣾ generating template fs.js:641
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/usr/lib/node_modules/moon-cli/template/config.json'
    at Error (native)
    at Object.fs.openSync (fs.js:641:18)
    at Object.fs.readFileSync (fs.js:509:33)
    at download (/usr/lib/node_modules/moon-cli/bin/moon:165:36)
    at /usr/lib/node_modules/moon-cli/node_modules/download-git-repo/index.js:43:29
    at /usr/lib/node_modules/moon-cli/node_modules/download/index.js:161:4
    at DuplexWrapper.callback (/usr/lib/node_modules/moon-cli/node_modules/each-async/index.js:33:4)
    at DuplexWrapper.onetime (/usr/lib/node_modules/moon-cli/node_modules/onetime/index.js:22:12)
    at emitOne (events.js:96:13)
    at DuplexWrapper.emit (events.js:188:7)

Hmm, it seems like the template wasn't downloaded correctly. Can you try running it again and seeing what happens? If the same thing happens, can you give me the output of:
$ cd /usr/lib/node_modules/moon-cli/; ls template

The template dir doesn't exist.

It didn't install the template correctly then 🤔
Did you try running the moon init command again? I've tried on my machine and it works, not sure why it isn't installing correctly on yours.

I did a local installation of moon-cli now and it worked. Maybe it's a permission issue with the global one.
Sorry for the trouble.

Alright cool! 👍


feature(emr-on-eks): implement emr on eks

Description of your changes
This change adds EMR on EKS feature to this provider.
Note:

For this to work, the EKS cluster must be configured to support it. Steps from 1 - 8 in this documentation must be followed.
These steps can be put into a composition; however, I believe it's out of scope for this PR.
AWS resources for this service are not explicitly removed. Instead, they transition into one of their end states. For example, Virtual Clusters are not removed when deleteVirtualCluster is called, it transitions into TERMINATED state. Therefore, hooks are necessary to handle them correctly.

Fixes #1564
I have:

[x] Read and followed Crossplane's contribution process.
[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Tested on my EKS clusters with required configurations.
# kubectl get jobrun
NAME           READY   SYNCED   EXTERNAL-NAME
test-job-run   True    True<PHONE_NUMBER>6b3pv4acb
# kubectl get virtualCluster
NAME           READY   SYNCED   EXTERNAL-NAME
test-cluster   True    True     bx8vka0gha35o8mds75qm4891

Nice one @nabuskey 🤘

@nabuskey  can you rebase to get rid of check-diff error ?

@haarchri done. Looks like lint failed because it reached timeout. Weird though. It passed fine last time. May need to increase the limit or concurrent runs.


Enable automated testing with Python 3.4

I think https://github.com/quantopian/zipline/pull/511 supercedes this now. I need to get 3.4 binaries up to the binstar and then 3.4 should run clean.


Add More Documentation

It would be great to add a bunch of documentation:

Design of each part of the system (from TableOperations to Expressions, etc.)
Tradeoffs taken in the design of the table format
Context bounds - what is and isn't in scope for Iceberg
What you need to do to replace Hive with your own metastore
Bootstrapping your own use of Iceberg
Reasoning for limiting what's possible with Avro schemas

@rdblue I think this may be the most pressing issue for the project, especially since it's now an Apache project (incubating). I'll be happy to take up some of it if you like.

@omervk, it would be great to have docs contributions! We just created a mkdocs site for the Iceberg incubator project, so you can add docs through pull requests to site on the Iceberg incubator project.


Set blank ipv4 and ipv6 in duckdns request if config is unset.

Fixes #1657
Issue is, when config values are unset, not present om config, bashio resolves them to "null".
This fix will pretty much ignore any configured value that does not look like an url.

I have to get back to this, i guess people might want the option to hard code an ip in some cases, even though this is a dynamic dns service


docs: Add description for multi-worker fluentd

I am adding a walkthrough of how to enable multi-worker fluentd.
The setup is opinionated and might be more generic, but at least it helped solve my problems.
Closes #1421

That's nice! Here some more things to add: https://github.com/kube-logging/logging-operator/issues/1421.
If you integrate those changes, you can mark this PR as resolving #1421. I'm currently testing a multiprocess setup and may have some more to add in the few next days too.

Thank you for the suggestion @aslafy-z . I added the configs that are mentioned in the issue and marked the issue to be solved by this PR.

I'm also thinking we should add the rootDir="/buffers" automatically if workers are configured, I'm not sure why we don't do that already...


Fix unit tests, variables were setup in the wrong order

I also cleaned up the code a fair bit.

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/626/ for details

No pylint warnings for pull request 6275:

Unit test changes for pull request 6275:

WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testWhiteBlackLists changed from failure to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCloseWorkTimeout changed from error to success


Feeding the focal length

Hi !
Thank you so much for implementing this node
By reading the paper and code, I could see that you can feed the focal length in pixel rather than estimating it. I feel that may improve the result especially for video.
It is a guess but would it be possible to expose the parameter ?

yes, added with https://github.com/spacepxl/ComfyUI-Depth-Pro/commit/2164e20feebf49fbb92164bff18cf3951b8d6838 along with helper nodes to convert focal length between px and mm

Awesome thank you !


added Water Closet by parallel realities

New Port for Water Closet
URL: https://www.parallelrealities.co.uk/games/wc/
Water Closet
Instructions:
DPAD = move
L2 = restart level
X = clone
B = use
A = jump
SELECT or START = menu
Controls can be altered in the menu.
Notes:
By default the resolution is set to 720x1280, but lower and higher resolutions can be selected.
Source code can be found here: https://github.com/stephenjsweeney/waterCloset
You can support them by doing an optional purchase over here https://parallelrealities.itch.io/water-closet
Tested on JELOS Powkiddy X55

I'm not seeing a screenshot or a .md file for the wiki entry. Can you add those?

added both a screenshot and a readme.

Thank you for the PR @a-dekker
I think we need to make the requirements for a PR a bit more clearer =)
We wrote some of it to https://portmaster.games/packaging.html# but need to add a more detailed section what is required for the PR.
Files look all in order.
Open:

Screenshot has to be in 640x480 or 4:3 resolution and ideally show gameplay. (The screenshot you chose would be okay because it shows the gameplay in the background)
We supply all devices and cfws at once so we have to test a mininmum set of resolutions and cfws.
For example Amberelec, ArkOS and Jelos and each of one of the resoltuions 480x320, 640x480 and a higher resolution one like you did with the x55. We do the testing on the various devices in our Discord under (testing-n-dev) https://discord.com/channels/1122861252088172575/1122885073507733625
There we create a thread, upload the version and let the users test.

The game has a bit of an odd resolution factor, so it does not match 3:4. But I now added some black bars to match 640x480.
And the PR demands are a bit unclear indeed, https://portmaster.games/packaging.html is not mentioned, I mainly base my input on other PR's as an example.
I am not on discord as we speak, so I have no idea what is going on over there.

The game has a bit of an odd resolution factor, so it does not match 3:4. But I now added some black bars to match 640x480.
And the PR demands are a bit unclear indeed, https://portmaster.games/packaging.html is not mentioned, I mainly base my input on other PR's as an example.
I am not on discord as we speak, so I have no idea what is going on over there.

We'd love to have you! Lot of WIP Ports are worked on by various people.
In fact we even have a testing thread for Water Closet.
They experimtend with different fonts and this was the current WIP package
https://cdn.discordapp.com/attachments/1157039888726769664/1157039889729192057/watercloset.zip

Tested on my RG351V (AmberELEC) works okay. But this one needs the font_replacement for 480x320 devices.
This font worked pretty well
ubuntu.condensed.ttf
https://cdn.discordapp.com/attachments/1157039888726769664/1157614669184372841/ubuntu.condensed.ttf
As base this was used
https://cdn.discordapp.com/attachments/1157039888726769664/1157039889729192057/watercloset.zip

Since it turned out there is a (tested) version already on Discord I don't think there is much use for this one. I tend towards closing this PR.


WIP: Set "root" property on Suite correctly

Any suite with an empty string text "" is marked as root suite. This can result in a deficient test tree with more than one root suite.
'use strict';

describe('suite1', function() {
  console.log(this.parent.title || '""', this.parent.root);
  console.log(this.title, this.root);

  describe('', function() {
    console.log(this.title || '""', this.root);
  });
  describe('', function() {
    console.log(this.title || '""', this.root);
  });
});

"" true
suite1 false
"" true              <<<<<<< second root
"" true              <<<<<<< third root

Description of the Change
Add an optional parameter "root" with default value false to the Suite constructor function.
Applicable issues
#2755

there's only one root suite ever... it's the same one across n different files.

that said #2755 is perfectly valid.  just wanted to clear up any confusion

@boneskull Thanks, but I'm confused now. Should I stop this PR, or go on?
In the sense of: "there should be only one root suite ever...

The PR is fine, I was just responding to your “can result in a tree with more than one root suite.” There can only be one root suite regardless of what reporters do with the title.

Coverage increased (+0.0007%) to 90.57% when pulling 6ec6c83c18244ec943717d794de9fdb1b2457000 on juergba:issue/2755 into a9f3526f3b29877b8769bcbe31ec2cc6af48f8f3 on mochajs:master.

This seems to be waiting on @plroebuck 	to approve changes


Adding CSS to Blog Page

Enhance the blog page by incorporating more CSS styles to improve its visual appearance and layout, ensuring a cohesive and visually appealing design that aligns with the overall website theme.
Please assign me this issue under GSSoC'23.

I can make it look attractive please assign it to me @bkrayaguru931 under GSSoC'23.

Enhance the blog page by incorporating more CSS styles to improve its visual appearance and layout, ensuring a cohesive and visually appealing design that aligns with the overall website theme.
Please assign me this issue under GSSoC'23.

Hii, I think it's been raised by #262

close this @bkrayaguru931


fix ctr delete images flag --sync

If we need delete two or more images, the --sync is not work to those imges except last image.
command:
ctr i rm docker.io/library/nginx:latest docker.io/library/nginx:1.21 --sync

I don't know wether there is other meanings there, please correct me if I understand this wrong.

/kind bug

If you look at when this was implemented in #1635 alongside the introduction of a GC plugin, this is not a direct synchronous delete of image resources associated with the image itself, but rather a triggering/scheduling of a GC run that will clean up orphaned resources. So, because of that, rather than forcing a garbage collector execution after each image in the loop, it makes sense to perform the image metadata removal for each image ref specified and then trigger GC only once at the end to clean up the resources for all the images that were just deleted from the store.


Custom graph resolution renders no datapoint

What did you do?
Created 2 graphs in prometheus:

up{job="cassandra", environment="stage"} leaving the default resolution - the calculated resolution shows 43s
same graph with a custom resolution of 43s

http:///graph?g0.range_input=3h&g0.end_input=2017-08-04+23%3A11&g0.expr=up%7Bjob%3D%22cassandra%22%2C+environment%3D%22stage%22%7D&g0.tab=0&g1.range_input=3h&g1.end_input=2017-08-04+23%3A11&g1.step_input=43&g1.expr=up%7Bjob%3D%22cassandra%22%2C+environment%3D%22stage%22%7D&g1.tab=0
What did you expect to see?
Both graphs should display the same data points
What did you see instead? Under which circumstances?
The first graph with no custom resolution correctly display the datapoints, while the second graph with the custom resolution (taken from the calculated resolution of first graph) doesn't show any datapoint.

Environment

System information:

Client (browser): Linux 4.11.8-200.fc25.x86_64 x86_64, Firefox 54.0 (64-bit) or Google Chrome 61.0.3163.13 (Official Build) dev (64-bit)
Server (prometheus):  Linux 4.4.0-89-generic x86_64

Prometheus version:

gc 1 @0.012s 0%: 0.22+0.72+0.084 ms clock, 0.66+0.23/0.58/0.42+0.25 ms cpu, 4->4->1 MB, 5 MB goal, 16 P
gc 2 @0.021s 1%: 0.051+0.62+0.33 ms clock, 0.36+0.10/1.0/1.1+2.3 ms cpu, 4->4->1 MB, 5 MB goal, 16 P
gc 3 @0.032s 1%: 0.052+0.45+0.11 ms clock, 0.63+0.042/1.0/0.55+1.4 ms cpu, 4->4->1 MB, 5 MB goal, 16 P
gc 4 @0.040s 1%: 0.039+0.75+0.13 ms clock, 0.55+0.10/1.3/0.30+1.8 ms cpu, 4->4->2 MB, 5 MB goal, 16 P
gc 5 @0.049s 2%: 0.012+0.44+0.14 ms clock, 0.19+0.11/1.1/1.5+2.3 ms cpu, 4->4->2 MB, 5 MB goal, 16 P
gc 6 @0.054s 2%: 0.013+0.48+0.15 ms clock, 0.21+0.068/1.4/1.3+2.4 ms cpu, 4->4->2 MB, 5 MB goal, 16 P
gc 7 @0.064s 2%: 0.012+0.87+0.17 ms clock, 0.19+0.11/1.8/1.5+2.7 ms cpu, 5->5->3 MB, 6 MB goal, 16 P
prometheus, version 1.7.1 (branch: master, revision: 3afb3fffa3a29c3de865e1172fb740442e9d0133)
  build user:       root@0aa1b7fc430d
  build date:       20170612-11:44:05
  go version:       go1.8.3

Possible dupe of https://github.com/prometheus/prometheus/issues/2827

Yes, this should already be fixed in master.


Upgrade dependencies and switch to modules

The main purpose of the change is to upgrade the dependencies, however whilst doing so I found that I needed to switch to a module to support the new version of ava and to do some other fixes for the changed default rules in xo/ESLint.

@kevva could you look at this PR and merge and update the NPM package if you're happy with it please?


Reputation is not being reduced for user when a reply with a favorite is being deleted.

Hi guys,
Let me elaborate this one:
In my project when the authenticated user favorites another users reply,  the authenticated user gets 1 point and the owner of the reply gets 3 points.
These points are not being reduced when the thread or reply gets deleted.
As for now i'm awarding and stripping reputation in the favorite() and unfavorite() methods, but I can't seem to wrap my head around how to go about it in the created and deleted in the boot methods, which would probably be where it should belong.
Can any one chime in on this one? :)

Ah, it was a rather easy fix as soon as I started to understand the morphTo() relationship.
I can be done with:
    /**
     * Boot the model.
     */
    protected static function boot()
    {
		parent::boot();

		static::created(function($favorite){
            Reputation::award(auth()->user(), Reputation::FAVORITE_REPLY);

			Reputation::award($favorite->favorited->user, Reputation::REPLY_WAS_FAVORITED);
		});

		static::deleted(function($favorite){
            Reputation::strip($favorite->user, Reputation::FAVORITE_REPLY);

			Reputation::strip($favorite->favorited->user, Reputation::REPLY_WAS_FAVORITED);
		});
    }

This is my first issue on Github. I apologise if i'm not doing it right :)


Request: Add Border Sizing and Background Color Changing Features

I'd like to propose the addition of two user-interface customization features to enhance the flexibility and visual appeal of the library. These features include the ability to adjust border sizing and change the background color of toasts.

If you need this feature let me assign or inform

You can do that via the style prop.

I tried this
<Toaster position="bottom-right" expand className="bg-red-500" />
and this
<Toaster position="bottom-right" expand style={{backgroundColor: "#025252", borderRadius: "64px"}} />
It didn't work


JSON dump model in python xgboost

Saw there is a function in R to dump models in json format. Not sure if python has similar functions, to save model in json format?

bst.get_dump(dump_format='json')