Upgrade neon and use the new direct HTTP call method

@cramforce They released another version where they also speak about pooling: https://github.com/neondatabase/serverless/commits/main do you want to clean this PR and re-upgrade?


Add wrapper for easy conversion to/from PyTorch Tensors

Add JaxToTorchWrapper in to_torch.py, which converts DeviceArrays into
PyTorch Tensors without transfering them to CPU.
Add "backend" argument to GymWrapper constructor.

Signed-off-by: Fabrice Normandin<EMAIL_ADDRESS>

@googlebot  I signed it!

Thanks for proposing this - I think it's going to be helpful to a lot of other users.  I'll do a review of this PR in the next few days.

This is really great! Do you have an example colab that ties this all together? If so, I'd be happy to incorporate it into notebooks and link to it in the README. I could see this being useful for a lot of folks. Nice work!

Sure! I've added it under notebooks/gym_pytorch.ipynb. Would you like me to keep it as part of this PR, or create another one for it?

Hey @erikfrey, would you mind check if the type error is fixed now?
I also reverted the changes to the formatting.

The error is fixed.  Thanks for this awesome improvement!


setFanSpeed

Hi, whenever I turn the fan on, it instantly goes to 100% in the Home App. By default, on the actual fan itself, when you turn it on it goes to a speed of 10% and then allows you to increase as necessary.
Is there anyway to have it so that when I turn the fan on in the Home App, the speed is set to 10% and not 100%? Have tried looking for the setFanSpeed and getFanSpeed code, but i'm not having much luck

I was about to post the same issue. My fan when turned on defaults to fan speed 3 out of 6 and was wondering if there was a ‘set default speed’ like how there is ‘set default brightness’ for the light accessory.

@Iprhodes is this something that could be added to a future update or maybe already is a part of it?

Here you go:
https://github.com/lprhodes/homebridge-broadlink-rm/releases/tag/3.5.9


ssh_accounts module

Cool feature. I think it's good to have a docs page or blog post on this.

Yes to both, I will try to figure out the docs integration in this PR and a blog post will come after we have at least two other modules (the three I'm thinking off are: a module to manage systemd services, a module to manage apt packages, and a module to manage docker containers. Docker is definitely priority number one in that list, but not sure which of the other two to tackle next. Also feel free to take any of these or suggest your own. I figured something that replicates top could be useful, too?)

Just a general question... why do specific commands such as rm, mkdir, etc... and not just simply allow to execute any generic command?

So, two reasons:

Those are actually following the sftp protocol, which should make it very slightly more efficient than passing it through a shell to re-parse the commands (though users can certainly do so by literally just running ssh_exec('<servername>', 'ls') for example)
The more important reason is that anything coming out of ssh_exec is only an unparsed string that you'd have to format yourself, while ssh_ls immediately returns a table with useful columns you can query on, like this:


[Bug: Navigation timeout 30000 ms exceeded

Minimal, reproducible example
const browser = await puppeteer.launch({
			headless: true,
			args: ["--no-sandbox", "--font-render-hinting=none"],
		});
		const page = await browser.newPage();

		await page.setContent(html ,{waitUntil:"domcontentloaded"});
		const pdfBuffer = await page.pdf(options);

		// Close browser
		await browser.close();

Error string
Navigation timeout 30000 ms exceeded
Bug behavior

[ ] Flaky
[X] PDF

Background
Getting Navigation timeout error 30000 ms exceeded when i deploy code to server
When I removed external resources from html i am able to generate the pdf.
But if HTML has external scripts this error throws up in server Navigation timeout error 30000 ms,
Expectation
PDF should be generated with no issues
Reality
Getting Navigation timeout error 30000 ms exceeded when i deploy code to server
When I removed external resources from html i am able to generate the pdf.
But if HTML has external scripts this error throws up in server Navigation timeout error 30000 ms,
Puppeteer configuration file (if used)
No response
Puppeteer version
21.9.0
Node version
16.20.0
Package manager
npm
Package manager version
8.19.4
Operating system
Linux

Does the issue reproduce for you locally? If so could you either provide a fully reproducible example with variables included.
Or if its only after deploying collect logs via setting DEBUG=puppeteer:* (Debugging) and share them here or via a GitHub Gist.
Note if you use any sensitive data with puppeteer that may show in the logs, so make sure to remove it before posting.

Consider using the dumpio: true flag when launching Puppeteer on the server to make sure the browser does not crash and has all required dependencies. Additionally, make sure the server has sufficient memory and cpu resources to run the browser or increase the navigation timeout. If your HTML content references subresources make sure they are accessible from the server.

I have the same error message, but in another case. I load a page and want work with it. The error comes random. In a previous version 19.11.1 the error message was:

(C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\common\LifecycleWatcher.js:174
return new Errors_js_1.TimeoutError(errorMessage);
^
TimeoutError: Navigation timeout of 30000 ms exceeded
at LifecycleWatcher._LifecycleWatcher_createTimeoutPromise (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\common\LifecycleWatcher.js:174:12)

in latest version 22.6.0 of puppeteer its now:

C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\Deferred.js:59
this.#timeoutError = new Errors_js_1.TimeoutError(opts.message);
^
TimeoutError: Navigation timeout of 30000 ms exceeded
at new Deferred (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\Deferred.js:59:34)
at Deferred.create (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\Deferred.js:21:16)
at new LifecycleWatcher (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\LifecycleWatcher.js:65:60)
at CdpFrame.goto (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\Frame.js:136:29)
at CdpFrame. (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\decorators.js:98:27)
at CdpPage.goto (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\api\Page.js:590:43)
at scrape (C:\Users\username\myscript.js:27:16)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async C:\Users\username\myscript.js:76:35

I have the same error message, but in another case. I load a page and want work with it. The error comes random. In a previous version 19.11.1 the error message was:

(C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\common\LifecycleWatcher.js:174
return new Errors_js_1.TimeoutError(errorMessage);
^
TimeoutError: Navigation timeout of 30000 ms exceeded
at LifecycleWatcher._LifecycleWatcher_createTimeoutPromise (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\common\LifecycleWatcher.js:174:12)

in latest version 22.6.0 of puppeteer its now:

C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\Deferred.js:59
this.#timeoutError = new Errors_js_1.TimeoutError(opts.message);
^
TimeoutError: Navigation timeout of 30000 ms exceeded
at new Deferred (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\Deferred.js:59:34)
at Deferred.create (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\Deferred.js:21:16)
at new LifecycleWatcher (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\LifecycleWatcher.js:65:60)
at CdpFrame.goto (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\Frame.js:136:29)
at CdpFrame. (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\util\decorators.js:98:27)
at CdpPage.goto (C:\Users\username\node_modules\puppeteer-core\lib\cjs\puppeteer\api\Page.js:590:43)
at scrape (C:\Users\username\myscript.js:27:16)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async C:\Users\username\myscript.js:76:35

Any solutions? I have the same error when deploy in server:
Logging in...
/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/util/Deferred.js:59
this.#timeoutError = new Errors_js_1.TimeoutError(opts.message);
^
TimeoutError: Navigation timeout of 30000 ms exceeded
at new Deferred (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/util/Deferred.js:59:34)
at Deferred.create (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/util/Deferred.js:21:16)
at new LifecycleWatcher (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/LifecycleWatcher.js:66:60)
at CdpFrame.goto (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Frame.js:136:29)

Same error.. when deploying to AWS Apprunner (containers)
Randomly it works..  literally, I copied/pasted the code from where it wasn't working to a healthcheck endpoint where it suddenly worked..  deffo seems to be some randomness/intermittency to it when running in the cloud for some reason

Just to add some stuff..

I used http module to hit the same site before pupeteer to ensure DNS working and a valid internet route
When I try/catch puppeteer page.gotos..  and allow the process to run..  it will literally fail 2/3 of the time with 'navigation timeout 30000 ms exceeded' but then succeed some of the time too.

Totally intermittent issue that only happens on containerised (headless: true) setups in the cloud.

Yes, I have the same issues, when run on ubuntu server; puppeteer seem can not connect to the Internet

Yes, I have the same issues, when run on ubuntu server; puppeteer seem can not connect to the Internet

Its foo, my server is too slow, modify timeout to 60s, then its ok!

If any of you are wasting days debugging Puppeteer crashes, I'm creating a new service to make it easier: Buglesstack. It's currently in beta, so I'd be glad if any of you tried it out!


Improve branching process for updating release docs

The current process around latest_release_doc_updates is poorly understood and error prone, and the circular merging a concern (at the very least it leads to a confusing commit history). I propose a new scheme:

When the documentation for a specific release needs to be corrected, we create on demand a branch X.Y.Z_doc_updates from the release tag vX.Y.Z. The desired updates are made on this branch; pushing to the branch triggers the CI to build and update the documentation for release X.Y.Z.
X.Y.Z_doc_updates is then immediately merged into the X.Y bugfix branch and from there into master, so that the updates are incorporated into the next bugfix and mainline releases
Periodically remove old _doc_updates branches

This has the following benefits and characteristics:

The circular merging is eliminated. All changes flow from the most specialised branches in towards master
It is possible to correct the documentation for arbitrary historic documentation versions (the current process only supports updating the latest release)

Tasks:

[ ] Update CI/site build and release script to pattern match and process $TAG_doc_updates branches
[ ] Document process

Do we ever actually make doc changes on a X.Y branch that cannot go live straight away? It would have to be something quite exceptional.
So perhaps we could do away with the X.Y.Z_doc_updates branches and simply publish whatever is on the X.Y branch.

Indeed, the branches are mainly required to allow you to publish updates in advance of a bugfix release (they have the side effect of letting you correct historic versions too, but I don't think we've ever needed that really). We would lose the ability to document changes that only made sense in conjunction with an as yet unreleased change of functionality, but we are talking about maintenance branches so it's probably not a big deal - it's a big win in terms of process simplicity though, so I'm for it. Any thoughts @bboreham?

Yes, I think we can assume we won't queue up a behavioural change that needs doc changes on a patch version branch; we'll either release it immediately or queue it up on a major release.

In the exceptional event that we do want to queue up a doc change for a patch release, we can create a branch for that, and merge it into X.Y just before the release. Much as we have been doing for README changes.

Closed by #2212.


switch to @enalmada/bun-externals

Current dependencies on/for this PR:

main

PR #14   👈

This comment was auto-generated by Graphite.


Gamepad: Update to fix xiao pin-height issue

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
If you're unsure about the format, make sure to check out the Orpheuspad example and follow the format there.
If this PR isn't a submission, that's okay too! If there's anything about this PR template that seems confusing, let me know in #hackpad on the slack!

thanks for making these updates! looks good to me, merging this now


Errors adding a billing project

When logged in as<EMAIL_ADDRESS>I get the following error when I try to add a new billing project (click on the New button):

IIRC, I was able to add billing projects in Firecloud. I'm not 100% sure though but I wanted to highlight in case something has changed.

Is it possible you declined to grant us the scopes to view billing accounts associated with your google identity?
If not, are you running a privacy blocker that may be interfering?

Disregard. The 3 billing projects I have ownership with my google account were all created for me by someone else. I've only been able to create billing projects using my personal account<EMAIL_ADDRESS>and I just confirmed that all is working properly with that.


Fix creating workspace section of build instructions

Updating build instructions to correct the directory path when creating the workspace.

If your PR closes/resolves/fixes an issue, follow the instructions at https://help.github.com/en/articles/closing-issues-using-keywords to use a keyword in your comment to auto-close the issue. For example, this one resolves #113


Namespace defined in decorators are not merged

in lib1.js
export function $lib1(contect) {}
setDecoratorNamespace("Foo", $lib1);

in lib2.js
export function $lib2(contect) {}
setDecoratorNamespace("Foo", $lib2);

In main.cadl
import "./lib1.js";
import "./lib2.js";

using Foo;

@lib1
@lib2
op test(): string;

This is currently preventing openapi and openapi3 library to have their decorators in the same namespace.

nvm, add another issue that was causing this.


Choose a Good Name

Currently, due to my lack of creativity, we have named this project s3d. That is an incredibly boring name. It stands for S3 Deploy. Again, very boring. We would love to give it a new name that sounds good. If you have an idea, feel free to comment below!
These are the requirements for the name:

Short. Less than 5 characters. The shorter the better.
Available on NPM.
Available domain name. (That sounds good)
Shouldn't conflict with any preinstalled binaries.

Here's an idea! maxup! It's 5 characters, available on NPM, and maxup.sh is available. Also, we can alias the binary so max works as well.


Fix bug where last few bytes on socket go unread

Issue:
aws-c-s3 is occasionally seeing errors when the server sends an HTTP response with a Connection: close header (meaning it intends to close the connection after the response is sent). The server is sending the full response, then immediately hanging up. But the last few bytes of the response never make it to the HTTP client.
Diagnosis:
If a peer closed their socket immediately after the last few bytes were sent, our socket code wasn't always reading those last few bytes.
On Linux, if a socket has unread data AND the peer has closed their side, the event from epoll has 2 flags set: EPOLLIN|EPOLLRDHUP. This means "the socket is has data to read AND the other side is closed (or half-closed) and won't be sending any more data".
Our socket handler code kinda did the right thing by "attempting" to read from the socket before shutting down the channel. But if the downstream read window reached 0, that "attempt" wouldn't read all the data.
Description of changes:
The socket handler no longer shuts down the channel in response to an error event. Instead, the error event queues more reads to happen. And only when read() reports that the socket is finished (due to error or EOF), will the socket handler shut down the channel.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Attention: Patch coverage is 94.11765% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 80.12%. Comparing base (e762fd2) to head (11e6267).

Files
Patch %
Lines

source/socket_channel_handler.c
90.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #642   +/-   ##
=======================================
  Coverage   80.11%   80.12%
=======================================
  Files          28       28
  Lines        5965     5967    +2
=======================================
+ Hits         4779     4781    +2
  Misses       1186     1186

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


Batch message processing

Add ability to process messages in batch in the Track 2 SB library client - ServiceBusProcessor.
See https://github.com/Azure/azure-sdk-for-net/pull/7110 for Track 1 WIP.

https://github.com/Azure/azure-sdk-for-net/issues/6440

In Track 2, we are not currently exposing a way to settle messages in a batch. This would probably be a prerequisite to adding a batch processing feature.


fix: issue in partial notes API

When refactoring the token contract I realized that we incorrectly populate ovpk in partial notes. This PR fixes it.

#9555  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @benesjan and the rest of your teammates on  Graphite


Salvage links to gitorious.org

The certificate of gitorious.org expired. It should be read-only. We need to check all the links to gitorious.org/.. especially if there are still repositories linked.
See WP Gitorious for background.

The Archive Team saved gitorious back in 2015 (https://www.archiveteam.org/index.php?title=Gitorious) and put gitorious in read-only mode. However, modern browsers just don't access gitorious.org. It's offline. Contact the Archive Team and ask what the status is. If that fails, ask on Reddit.

I wrote a message to the Archive Team.

I got a reply. Apparently they run the server now and it hanged, but they could reboot it. After allowing an exception for the expired certificate, the valhalla of Gitorious can be accessed again.
Will reply and ask if they can also offer it as a download, similarly to gna.org.

I can clone with Git from the Gitorious archive again (disabling the verification of the certificate)
Example

git init
git config sslVerify false
git remote add origin https://gitorious.org/turious/turious.git
git fetch origin
git checkout master

[ ] Card Stories (check if gitorious and github version are equal)
[ ] Heroes of Wesnoth (check https://gitorious.org/heroes-of-wesnoth/mainline)
[ ] Turious (including Rosethorn)

I checked Card Stories and the Github versions seems to include the Gitorious version.

I checked Heroes of Wesnoth and the Gitorious Git as well as the Launchpad Bzr repositories seem to be identical.

I downloaded the repositories for Turious and will upload them at Gitlab soon.

Gitorious is offline again. This time I will rest it for good and not ask them to revive it. For Turious, the code is also on Gitlab, so I removed links to gitorious. For Card stories, since the Git versions were contained, I removed the link to gitorious as well. For Heroes of Wesnoth, there is a Bazaar and SVN repository given. Will check that everything is also available as Git, before removing.


Ground truths?

Thank you for sharing the preprocessed reports and your code. It's a very helpful resource.  I am however unable to find the ground truth labels. You mention in your paper that they are part of the metadata but I am unable to find them. Would appreciate any guidance.

I was able to find them


How to sorter file upload DESC

How do I sorter the new upload logs to the top of the newest creation date.
Sorry for my bad english!!!

@daolvcntt Use usort() from here.

@g0110280 thank you


feat(typescript): convert to typescript

This PR aims to convert this package to Typescript, allowing for both Javascript and Typescript projects to use it with added types for type-checking and IntelliSense.
Typescript was added as a dev dependency
File structure was changed to include src and build directories
tsc is used to transpile ts to js because of the package's simple output
Jest was updated in dev dependencies due to the previous version causing type errors
ESLint was updated

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ali587 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


"%23" is transformed into "#" for physical path, nuget or msbuild?

In case I got a VisualStudio-solution with several projects (by email or from somewhere else) and within the solution one or more projects are in physical directories which include "%23" in there path, e.g.

C:\users\someuser\source\repos_1.12%231986\A-Serie-XYZ

During Solution-load the following error raise up in VisualStudio's error pane:

Because "%23" is transformed to "#" which is physically not available.
Host: VisualStudio 2019 Preview, 16.2.0 Preview 3.0
(moved from https://github.com/NuGet/Home/issues/8273)

@cbries (original poster)
MSBuild does have some bugs like this where we overzealously normalize strings using URI escaping/unescaping. This is likely one. At the moment, the workaround is to not use paths like that.


Added wishlist functionality changed minor spelling mistakes

Can you heck the UI of wishlist icon (before and after) @HimanshuNarware, is it ok?

We will create a separate issue for designing part
This issue was only for functionality

Issue #106 and #107 solved under this

@rajat99-default Can you align all the cards horizontally in wishlist section , also make icon size on card bit larger and give some spacing from top and side, Is there any functionality to remove those cards from wishlist section , by again clicking those heart icons?


Opaque type completely erased

If I have the input:
#include <string>

extern std::string *into_cpp(const char *cstr, size_t len);
extern size_t str_len(const std::string *str);

And generate a binding with:
bindgen mystring.h --enable-cxx-namespaces --generate types,methods,functions --whitelist-function=into_cpp --whitelist-function=str_len --whitelist-type=str::string '--opaque-type=.*' -- -x c++ -std=gnu++14

I get the output:
/* automatically generated by rust-bindgen */

pub mod root {
    #[allow(unused_imports)]
    use self::super::root;
    pub mod std {
        #[allow(unused_imports)]
        use self::super::super::root;
        pub mod namespace {
            #[allow(unused_imports)]
            use self::super::super::super::root;
        }
    }
    pub mod __gnu_cxx {
        #[allow(unused_imports)]
        use self::super::super::root;
    }
    extern "C" {
        #[link_name = "_Z8into_cppPKcm"]
        pub fn into_cpp(cstr: *const ::std::os::raw::c_char, len: u64)
         -> *mut [u64; 3usize];
    }
    extern "C" {
        #[link_name =
              "_Z7str_lenPKSt14basic_fbstringIcSt11char_traitsIcESaIcESt13fbstring_coreIcEE"]
        pub fn str_len(str: *const [u64; 3usize]) -> u64;
    }
}

std::string is completely erased, replaced with [u64; 3usize], and not even a pub type ... left.
(Hm, on Macos using the Brew version of clang, it segfaults with what appears to be infinite recursion.)

This is sort of expected, we use opaque to replace layouts we can't handle.
For example, if we have a type like:
template<typename ...Args>
struct Baz {
    // Something we can't handle with Args...
};

struct Foo {
    Baz<i32, Foo> whatever;
};

The only way to get a correct layout is making Baz opaque, in which case we'll detect it's a specialization of an opaque type we know the layout and alignment of, and generate a bunch of bytes to ensure the correct layout for Foo.
This should be better documented though.
The solution to hide types is general to use --blacklist-type.

Isn't this backwards? --blacklist-type adds the pattern to options.hide_type, but --opaque-type goes into options.opaque_type.

Yes, blacklist does that, but opaque doesn't do that when there's template parameters for said reason... (note that std::string is really a subclass with template params).
Though you're right we should improve that actually.
We should only fall back to that behavior if the type is opaque and it's layout is unknown (and potentially and if referencing it would incur in no applicable template arguments).
Will see if I can come up with something.

Actually my comment may be misleading, we may not have specific code for template parameters.

Sometimes I can get it to produce pub type string = [u64; 3usize], but I forgot to note the options and I haven't managed to get it back.

Hmm... Yeah, that'd be possible. I think right now we stop tracing opaque types, which would make string not appear, but I guess what we want is not tracing the children.
That'd explain that.

sorry, got sidetracked, I think I know what this is.

#387 should do it :)

Then there's the code generated for strings, which needs to be tweaked too. This may be a bit more complex because there are chances to break stuff, so it'll take a bit more time to test it properly.

Mainly, I don't think we should go ahead and generate a placeholder when we know the layout of that opaque type, which is the problem the placeholder is trying to solve.
In order to do that, we can as an initial step just chec for template parameters in the type, which would be ok for this case because it's an alias, and that could not break stuff I think (because we should know the layout of everything non-dependent on template params).

Added a few more fixes to #387 that should also fix the pub mod namespace thing (modern stdlibs are using inline namespaces, that we didn't handle, and makes your example work as you expect for me.

This should be fixed now, thanks for reporting it!


Handling for MSBReference properties

Adds a decorator for properties that have a MSBReference row, with some extra info and a context menu with a search, heavily inspired by param reference rows.
Also makes the 'Referenced' and 'Referenced By' menus more dynamic, refreshing when changing a property on the object.

Very nice.

Okay, I made a mistake in handling array rows in imgui, currently fixing it


[Bug]: Issue with Omnibar navigation--> widgets that donot belong to my branch are also showing up

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Issue with Omnibar navigation--> widgets that donot belong to my branch are also showing up under Navigate option
Steps To Reproduce

Create a GIT connected app.
create one branch and switch to that branch from Master
Click on Navigation--> navigate
You will be able to see the Unwanted widgets appearing over there that might belong to some other branch

Loom-->https://www.loom.com/share/c01e25f1a26a499288f1dda6d1efb8fa
Public Sample App
No response
Version
Production

@kocharrahul7  - Are we killing the omni bar? If yes, then can we close this?

@infinitetrooper Not killing the omnibar, removing snippets and documentation from it. Navigation will remain for the foreseeable future


A few minor X and Y additions

Refs issue #27

Looking good, don't forget to follow https://twitter.com/NextBigThingBot.
Thanks for the PR!

Looking good, don't forget to follow https://twitter.com/NextBigThingBot.
Thanks for the PR!


Ensure main.spec exists before removing

Also don't remove all *.spec files bc we might be removing files we don't want

CC @gjreda

Is rm -f main.spec not preferred? I don't really care just curious if there's a reason to prefer the touch approach here...

Is rm -f main.spec not preferred? I don't really care just curious if there's a reason to prefer the touch approach here...

@hammer the original code was using a wildcard rm *.spec that don't work with -f. We need to use rm -f "*.spec" if we use the *.
Now that we only remove the main.spec file we can use rm -f main.spec. Will add this fix to #99 (also related with scripts)


packSCMP Continued

After my comments are addressed, it should be ready to merge on the original SCMP branch


Deprecated modules not shown when colorized

Deprecated+Colorized modules should have some sort of diagonal striping like their uncolorized counterparts.  Currently they don't ...
Uncolorized:
Colorized:

I think the only solution to this would be to add a second path to overlay the base one.
Alternatively we can move the style to the border

Closing.  'Not worth worrying about.


controller: update condition reason when upgrade job crashes

the current code will only update the condition reason when the job
fails, but if the job crashes the reconcile loop will stay stuck in the
migration in progress state and never recreate the upgrade job.
this fixes the problem by always updating the condition reason to
migrations failed after having checked that the job is neither active
nor succeeded.
relates to PROJQUAY-1812

/cherry-pick redhat-3.6


authors-transform.txt issue

Please note that the result from the PowerShell command is simply a list of usernames.
The instructions are slightly confusing when it explains the format as it does not match.
(i.e. you would get willys instead of willys = willys <willys>)
This is unlike the Unix command from https://john.albin.net/git/convert-subversion-to-git which actually outputs the specified format (i.e. willys = willys <willys>)
svn log -q | awk -F '|' '/^r/ {sub("^ ", "", $2); sub(" $", "", $2); print $2" = "$2" <"$2">"}' | sort -u > authors-transform.txt
Further, the PowerShell command seemed to create a text file with Windows encoding rather than UTF-8.
As a result, Git couldn't parse it properly.

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

ID: edd6cbc8-5e3b-c3a1-4672-d42510cc058b
Version Independent ID: 8fe81fb5-7c2d-2562-5659-55fccbb3126c
Content: Perform the migration from SVN to Git
Content Source: docs/articles/perform-migration-from-svn-to-git.md
Service: unspecified
GitHub Login: @hkamel
Microsoft Alias: hkamel

+1 to that.
To make it work in the meantime you can use Git-Bash on windows and enter the exact command suggested by cpboyd -
svn log -q | awk -F '|' '/^r/ {sub("^ ", "", $2); sub(" $", "", $2); print $2" = "$2" <"$2">"}' | sort -u > authors-transform.txt

This also works
svn.exe log --quiet | ? { $_ -notlike '-*' } | % { "{0} = {0} <{0}>" -f ($_ -split ' | ')[1] } | Select-Object -Unique > authors-transform.txt


Describe the bug ✍
Currently, the README.md file of the Anime_Clicker project includes a link instead of an embedded screenshot, which could be improved for better user experience and presentation. It would be beneficial to replace this link with an actual screenshot of the game.
Steps to Resolve:

Capture a screenshot of the Anime_Clicker game.
Update the README.md file to embed this screenshot directly.
Ensure the screenshot is clear and representative of the game.

Screenshot:

Please assign me this issue under gssoc'24.
Provide step by step information reproduce the bug 📄

Steps to Reproduce the Bug
Clone Repository
Navigate to Repository Directory
Open README.md
Identifying the Issue
Locate Screenshot Link
Steps to Fix the Issue
Capture Game Screenshot
Add Screenshot to Repository
Update README.md
Finalizing Changes
Save and Commit

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Bindusree1515 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @Bindusree1515 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Fixed meson build

Fixed an error which would make meson and ninja unable to build src/drv_wmr. src/ext-deps/nxjson.c was not included before.

Thanks! The missing nxjson.c in wmr sources in Meson builds was never noticed because the vive driver also pulls it in. This patch actually contains fixes for two more issues, only one of them specific to Meson:

It fixes resetList to actually clear the complete returnList array, and not only its first element.
It generates the .pc file and installs the header even when building a static library. This part is
identical to #190.


Models with PBR texture maps and lightmap are dimly lit and have pale colors.

Environment
Gazebo Garden
Ubuntu 22.04
Ogre2
Built from source
Description
I'm running a simulation in an environment with PBR textures and light map (baked in Blender using SimpleBake). However, I can't get it to look vibrant. All colours are more greyish wrt how they render in Blender.
Not sure if this is a bug, a 'known limitation' or rather just ignorance on my side.
This is Blender (cycles):

This is gazebo sim:

(the distortion of the checker pattern is not relevant; it is due to a wrong UV mapping)
The Blender model is lit from the pendant lights (emissive white surface). The Gazebo world has the .dae with PBR textures, light map and at each pendant one spot light (without shadows). Both the Blender and Gazebo lights are pure white (RGB 255).
I can't share that model but I made this test repository that shows similarly dull colors. It holds the blender project file, as well as the derived PBR and light map images, .dae and .sdf files:

I think the lightmap demo world also looks rather dimly lit, so it seems that this is a more general issue?
I could obviously manually  tweak the saturation of the colours in the albedo map, but e.g. the white part of the walls is already pure white (close to max RGB values) so I can't get that to look less grey.
I also tried to add a bright light, which obviously makes the scene more clearly lit, but:

It does not augment the saturation of the yellow colour,
It yields uneven lighting (e.g. objects close to the light are too bright).

I also tried to change the <ambient> and <ambient_light> values in the sdf and gui.config respectively, but that does not seem to have an influence.
So I wonder if there is some way to augment the general lighting in a scene?

The <ambient> tag should increase overall scene brightness. I do notice differences with other game / rendering engines. Another thing to try is lower the metalness values to make objects brighter.
@ColeOSRF do you have any tips on tuning the PBR materials in gazebo to look more like other engines?

Here is what I was able to get with some adjustments

The main issue is that your textures are 16bit. This is what causes the saturation issues with the albedo maps. They should be 8bit. For the dimness I increased the range of the point light. It's range was short to the point that it wasn't really affecting anything. You will almost certainly want some kind of dynamic light in the scene for specularity, normal maps, etc since a lightmap cannot reproduce these. A soft, large range point light without shadows is great for this. You may need more than one to create more even lighting.
You can also play around with the light parameters like linear, constant, and quadratic to achieve a softer more even lighting. The lightmaps are just images, not hdr maps, so think of them more as shadow maps. Great for shadows and reproducing ambient occlusion, not so much for adding brightness. The dynamic lights will still be needed for to achieve a brighter environment.
Also just as an extra note. You have a lot of textures that are one solid value. Feel free to use numeric values in the SDF instead of textures in these cases. For instance 0.5 will equate to a texture map with 50% grey.
I also lowered the ambient to zero as this can lead to the image appearing washed out and isn't usually necessary with lightmaps.
Hope this helps!

 :-D
Thank you so much! I would have never found that it is due to the images being 16 bit!
I had enabled 16 bit output since the SimpleBake doc states: "16 bit export should probably be enabled unless file size is an issue¨.
Thanks also for the suggestions wrt the lighting.
And you are right about the solid value textures; the original idea was to apply real textures to all parts, but as I am alredy rather pleased with the current result I might indeed change the texture maps for numeric values.


Illuminate\Http\Response - Attribute "original" contains string instead of View object.

Laravel Version: 5.2.45
Homestead version '3.0.2'

Description:
I am returning a View from a controller's method as follows:
return view('Main::pages.content-page', compact('content'));

View renders correctly however, when I dd the response object I see that the attribute "original" of the response object is a string whereas it should have been the View Object.
Response {#385 ▼
  +original: """
    <!DOCTYPE html>\n
    <html lang="en">\n
        <head>\n
        <meta charset="utf-8">\n
        <meta http-equiv="X-UA-Compatible" content="IE=edge">\n
        <meta name="viewport" content="width=device-width, initial-scale=1">\n
        <meta name="author" content="">\n
        <meta name="csrf-token" content="2CQirHnZ7isCBRfkhOYkzPAWOzNIqJISrbb1mfDv">\n
            <meta name="description" content="">\n
        <meta name="keywords" content="">\n
        <title id="page_title">    Découvrir\n
    </title>\n
    \n
        <!-- Default CSS -->\n
    <link type="text/css" media="all" rel="stylesheet" href="http://tesdiq.dev/build/main/css/all-5f07666915.css">\n
    \n
    \n
    <link href='https://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,800italic,400,300,600,700,800' rel='stylesheet' type='text/css'>\n
    <link href='https://fonts.googleapis.com/css?family=Merriweather:400,300,300italic,400italic,700,700italic,900,900italic' rel='stylesheet' type='text/css'>\n
    \n
        <!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->\n
        <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->\n
        <!--[if lt IE 9]>\n
.....

Is this expected behavior because my tests are actually failing because of it, since in my test am essentially doing
$this->get(route('main.page', ['content' => $content->slug]))
        ->assertResponseOk()
        ->assertViewHas('content', $content);

Am getting the following failure
F                                                                   1 / 1 (100%)

Time: 179 ms, Memory: 20.00MB

There was 1 failure:

1) IndexControllerTest::testGetPageMethod
The response was not a view.
Failed asserting that false is true.

Looking at the structure of the assertViewHas() method we can see why

/**
     * Assert that the response view has a given piece of bound data.
     *
     * @param  string|array  $key
     * @param  mixed  $value
     * @return $this
     */
    public function assertViewHas($key, $value = null)
    {
        if (is_array($key)) {
            return $this->assertViewHasAll($key);
        }

        if (! isset($this->response->original) || ! $this->response->original instanceof View) {
            return PHPUnit::assertTrue(false, 'The response was not a view.');
        }
        ......

The condition ! $this->response->original instanceof View fails because original is a string but should have been a View Object.
So am at a lost here. Is this expected behavior if so why the condition in the assertViewHas method ?
I am on Laravel Homestead version '3.0.2'
Laravel 5.2.45

Steps To Reproduce:

Return a view from a controller.
Create a test that makes a get request to the controller.
Use the assertViewHas method in the test.

$this->get(route('main.page', ['content' => $content->slug]))
        ->assertResponseOk()
        ->assertViewHas('content', $content);

Please upgrade to laravel 5.3 since 5.2 is not supported anymore, please feel free to ping me if you ever encountered the same issue on a 5.3 instance.

@themsaid, thank you for your response. This issue does not occur in 5.3. However am a little bit skeptical about upgrading my app to 5.3 yet as I don't feel 5.3 is mature enough for production, I want to wait until next year to change to 5.3. I might be wrong though but it's just my gut feeling.
Thank you anyways for thanking the time to answer my question.

@themsaid I ran into the same issue above at version 5.6.
When Controller returns return response()->view('name');, $response->original will be string as html content in an unit test. How can I get view object instead of string?


mediapipe.Image crashes or gives weird results

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
Yes
OS Platform and Distribution
Windows 10
Mobile device if the issue happens on mobile device
No response
Browser and version if the issue happens on browser
No response
Programming Language and version
Python 3.11.6
MediaPipe version
0.10.8
Bazel version
No response
Solution
Object detection
Android Studio, NDK, SDK versions (if issue is related to building in Android environment)
No response
Xcode & Tulsi version (if issue is related to building for iOS)
No response
Describe the actual behavior
For some images, program crashes when creating Image, or gives no detections, or bad results with high scores, while JavaScript package works fine.
Describe the expected behaviour
Get fine results, similar to the JavaScript package.
Standalone code/steps you may have used to try to get what you need
Link to repo demonstrating the issue: mediapipe-image-issue. Code, images, model, screenshot are included.
Other info / Complete Logs
No response

Hi @tuhm1,
The expected behavior aligns with our anticipation, as both platforms support distinct graph structures. Python utilizes the CPU graph, while JavaScript employs the GPU graph, resulting in slightly improved performance. We would like to inform you that we have recently introduced GPU support via Pip for Linux and macOS in Python, potentially offering performance comparable to JavaScript.
Thank you

Hi @kuaashish
The results differ very much, not just slightly. For example:

JavaScript
Python (file)
Python (ndarray)

Crash

Crash

The results when creating a mediapipe Image from ndarray and when using Image.create_from_file also differ.

@tuhm1 Could you try this notebook out and verify Image loading and Object Detection works fine for you?
https://colab.research.google.com/drive/1CzhynQzpxzPDfZMUE4whG9jgjieMmRvX?usp=sharing

Here is my result:

Runtime logs

Timestamp
Level
Message

Dec 15, 2023, 6:40:58 PM
WARNING
WARNING:root:kernel b113adbf-4690-4236-b0ae-02bc085c4f6c restarted

Dec 15, 2023, 6:40:58 PM
INFO
KernelRestarter: restarting kernel (1/5), keep random ports

Dec 15, 2023, 6:40:56 PM
WARNING
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.

Dec 15, 2023, 6:40:56 PM
WARNING
I0000 00:00:1702640456.581241    3672 task_runner.cc:85] GPU suport is not available: INTERNAL: ; RET_CHECK failure (mediapipe/gpu/gl_context_egl.cc:84) egl_initializedUnable to initialize EGL

Dec 15, 2023, 6:40:56 PM
WARNING
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR

Dec 15, 2023, 6:40:54 PM
WARNING
2023-12-15 11:40:54.139232: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT

Dec 15, 2023, 6:40:52 PM
WARNING
To enable the following instructions: AVX2 AVX512F FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.

Dec 15, 2023, 6:40:52 PM
WARNING
2023-12-15 11:40:52.057603: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.

Dec 15, 2023, 6:40:52 PM
WARNING
2023-12-15 11:40:52.035051: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered

Dec 15, 2023, 6:40:52 PM
WARNING
2023-12-15 11:40:52.032142: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered

Dec 15, 2023, 6:40:52 PM
WARNING
2023-12-15 11:40:52.032072: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered

Dec 15, 2023, 6:40:28 PM
INFO
Kernel started: b113adbf-4690-4236-b0ae-02bc085c4f6c, name: python3

Dec 15, 2023, 6:25:57 PM
INFO
Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).

Dec 15, 2023, 6:25:57 PM
INFO
http://<IP_ADDRESS>:9000/

Dec 15, 2023, 6:25:57 PM
INFO
Jupyter Notebook 6.5.5 is running at:

Dec 15, 2023, 6:25:57 PM
INFO
Serving notebooks from local directory: /

Dec 15, 2023, 6:25:57 PM
INFO
Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).

Dec 15, 2023, 6:25:57 PM
INFO
http://<IP_ADDRESS>:9000/

Dec 15, 2023, 6:25:57 PM
INFO
Jupyter Notebook 6.5.5 is running at:

Dec 15, 2023, 6:25:57 PM
INFO
Serving notebooks from local directory: /

Dec 15, 2023, 6:25:54 PM
INFO
google.colab serverextension initialized.

Dec 15, 2023, 6:25:54 PM
INFO
google.colab serverextension initialized.

Dec 15, 2023, 6:25:54 PM
INFO
Authentication of /metrics is OFF, since other authentication is disabled.

Dec 15, 2023, 6:25:54 PM
INFO
Writing notebook server cookie secret to /root/.local/share/jupyter/runtime/notebook_cookie_secret

Dec 15, 2023, 6:25:54 PM
WARNING
/root/.jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:54 PM
WARNING
/root/.local/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:54 PM
WARNING
/usr/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:54 PM
WARNING
/usr/local/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:54 PM
WARNING
/usr/local/etc/jupyter/jupyter_notebook_config.d/panel-client-jupyter.json

Dec 15, 2023, 6:25:54 PM
WARNING
/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
INFO
Authentication of /metrics is OFF, since other authentication is disabled.

Dec 15, 2023, 6:25:53 PM
INFO
Writing notebook server cookie secret to /root/.local/share/jupyter/runtime/notebook_cookie_secret

Dec 15, 2023, 6:25:53 PM
WARNING
/root/.jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
/root/.local/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
/usr/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
/usr/local/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
/usr/local/etc/jupyter/jupyter_notebook_config.d/panel-client-jupyter.json

Dec 15, 2023, 6:25:53 PM
WARNING
/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.510 NotebookApp] Loaded config file: /root/.jupyter/jupyter_notebook_config.py

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.504 NotebookApp] Looking for jupyter_notebook_config in /root/.jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.504 NotebookApp] Looking for jupyter_notebook_config in /root/.local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.504 NotebookApp] Looking for jupyter_notebook_config in /usr/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.504 NotebookApp] Loaded config file: /usr/local/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.501 NotebookApp] Looking for jupyter_notebook_config in /usr/local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.501 NotebookApp] Loaded config file: /etc/jupyter/jupyter_notebook_config.py

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.497 NotebookApp] Looking for jupyter_notebook_config in /etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.493 NotebookApp] Looking for jupyter_config in /root/.jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.493 NotebookApp] Looking for jupyter_config in /root/.local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.493 NotebookApp] Looking for jupyter_config in /usr/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.488 NotebookApp] Looking for jupyter_config in /usr/local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.486 NotebookApp] Looking for jupyter_config in /etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.485 NotebookApp] Searching ['/root/.jupyter', '/root/.local/etc/jupyter', '/usr/etc/jupyter', '/usr/local/etc/jupyter', '/etc/jupyter'] for config files

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.460 NotebookApp] Loaded config file: /root/.jupyter/jupyter_notebook_config.py

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.456 NotebookApp] Looking for jupyter_notebook_config in /root/.jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.456 NotebookApp] Looking for jupyter_notebook_config in /root/.local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.455 NotebookApp] Looking for jupyter_notebook_config in /usr/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.455 NotebookApp] Loaded config file: /usr/local/etc/jupyter/jupyter_notebook_config.json

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.453 NotebookApp] Looking for jupyter_notebook_config in /usr/local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.453 NotebookApp] Loaded config file: /etc/jupyter/jupyter_notebook_config.py

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.451 NotebookApp] Looking for jupyter_notebook_config in /etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.449 NotebookApp] Looking for jupyter_config in /root/.jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.449 NotebookApp] Looking for jupyter_config in /root/.local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.448 NotebookApp] Looking for jupyter_config in /usr/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.444 NotebookApp] Looking for jupyter_config in /usr/local/etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.441 NotebookApp] Looking for jupyter_config in /etc/jupyter

Dec 15, 2023, 6:25:53 PM
WARNING
[D 11:25:53.441 NotebookApp] Searching ['/root/.jupyter', '/root/.local/etc/jupyter', '/usr/etc/jupyter', '/usr/local/etc/jupyter', '/etc/jupyter'] for config files

I am certain the crash happened at mp.Image(...) because I tried running it separately.

@kinaryml
Here is my result:

Runtime logs
Timestamp	Level	Message
Dec 15, 2023, 6:40:58 PM	WARNING	WARNING:root:kernel b113adbf-4690-4236-b0ae-02bc085c4f6c restarted
Dec 15, 2023, 6:40:58 PM	INFO	KernelRestarter: restarting kernel (1/5), keep random ports
Dec 15, 2023, 6:40:56 PM	WARNING	INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
Dec 15, 2023, 6:40:56 PM	WARNING	I0000 00:00:1702640456.581241 3672 task_runner.cc:85] GPU suport is not available: INTERNAL: ; RET_CHECK failure (mediapipe/gpu/gl_context_egl.cc:84) egl_initializedUnable to initialize EGL
Dec 15, 2023, 6:40:56 PM	WARNING	WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
Dec 15, 2023, 6:40:54 PM	WARNING	2023-12-15 11:40:54.139232: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Dec 15, 2023, 6:40:52 PM	WARNING	To enable the following instructions: AVX2 AVX512F FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Dec 15, 2023, 6:40:52 PM	WARNING	2023-12-15 11:40:52.057603: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
Dec 15, 2023, 6:40:52 PM	WARNING	2023-12-15 11:40:52.035051: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
Dec 15, 2023, 6:40:52 PM	WARNING	2023-12-15 11:40:52.032142: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
Dec 15, 2023, 6:40:52 PM	WARNING	2023-12-15 11:40:52.032072: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
Dec 15, 2023, 6:40:28 PM	INFO	Kernel started: b113adbf-4690-4236-b0ae-02bc085c4f6c, name: python3
Dec 15, 2023, 6:25:57 PM	INFO	Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
Dec 15, 2023, 6:25:57 PM	INFO	http://<IP_ADDRESS>:9000/
Dec 15, 2023, 6:25:57 PM	INFO	Jupyter Notebook 6.5.5 is running at:
Dec 15, 2023, 6:25:57 PM	INFO	Serving notebooks from local directory: /
Dec 15, 2023, 6:25:57 PM	INFO	Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
Dec 15, 2023, 6:25:57 PM	INFO	http://<IP_ADDRESS>:9000/
Dec 15, 2023, 6:25:57 PM	INFO	Jupyter Notebook 6.5.5 is running at:
Dec 15, 2023, 6:25:57 PM	INFO	Serving notebooks from local directory: /
Dec 15, 2023, 6:25:54 PM	INFO	google.colab serverextension initialized.
Dec 15, 2023, 6:25:54 PM	INFO	google.colab serverextension initialized.
Dec 15, 2023, 6:25:54 PM	INFO	Authentication of /metrics is OFF, since other authentication is disabled.
Dec 15, 2023, 6:25:54 PM	INFO	Writing notebook server cookie secret to /root/.local/share/jupyter/runtime/notebook_cookie_secret
Dec 15, 2023, 6:25:54 PM	WARNING	/root/.jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:54 PM	WARNING	/root/.local/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:54 PM	WARNING	/usr/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:54 PM	WARNING	/usr/local/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:54 PM	WARNING	/usr/local/etc/jupyter/jupyter_notebook_config.d/panel-client-jupyter.json
Dec 15, 2023, 6:25:54 PM	WARNING	/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	INFO	Authentication of /metrics is OFF, since other authentication is disabled.
Dec 15, 2023, 6:25:53 PM	INFO	Writing notebook server cookie secret to /root/.local/share/jupyter/runtime/notebook_cookie_secret
Dec 15, 2023, 6:25:53 PM	WARNING	/root/.jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	/root/.local/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	/usr/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	/usr/local/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	/usr/local/etc/jupyter/jupyter_notebook_config.d/panel-client-jupyter.json
Dec 15, 2023, 6:25:53 PM	WARNING	/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.510 NotebookApp] Loaded config file: /root/.jupyter/jupyter_notebook_config.py
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.504 NotebookApp] Looking for jupyter_notebook_config in /root/.jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.504 NotebookApp] Looking for jupyter_notebook_config in /root/.local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.504 NotebookApp] Looking for jupyter_notebook_config in /usr/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.504 NotebookApp] Loaded config file: /usr/local/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.501 NotebookApp] Looking for jupyter_notebook_config in /usr/local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.501 NotebookApp] Loaded config file: /etc/jupyter/jupyter_notebook_config.py
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.497 NotebookApp] Looking for jupyter_notebook_config in /etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.493 NotebookApp] Looking for jupyter_config in /root/.jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.493 NotebookApp] Looking for jupyter_config in /root/.local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.493 NotebookApp] Looking for jupyter_config in /usr/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.488 NotebookApp] Looking for jupyter_config in /usr/local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.486 NotebookApp] Looking for jupyter_config in /etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.485 NotebookApp] Searching ['/root/.jupyter', '/root/.local/etc/jupyter', '/usr/etc/jupyter', '/usr/local/etc/jupyter', '/etc/jupyter'] for config files
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.460 NotebookApp] Loaded config file: /root/.jupyter/jupyter_notebook_config.py
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.456 NotebookApp] Looking for jupyter_notebook_config in /root/.jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.456 NotebookApp] Looking for jupyter_notebook_config in /root/.local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.455 NotebookApp] Looking for jupyter_notebook_config in /usr/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.455 NotebookApp] Loaded config file: /usr/local/etc/jupyter/jupyter_notebook_config.json
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.453 NotebookApp] Looking for jupyter_notebook_config in /usr/local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.453 NotebookApp] Loaded config file: /etc/jupyter/jupyter_notebook_config.py
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.451 NotebookApp] Looking for jupyter_notebook_config in /etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.449 NotebookApp] Looking for jupyter_config in /root/.jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.449 NotebookApp] Looking for jupyter_config in /root/.local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.448 NotebookApp] Looking for jupyter_config in /usr/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.444 NotebookApp] Looking for jupyter_config in /usr/local/etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.441 NotebookApp] Looking for jupyter_config in /etc/jupyter
Dec 15, 2023, 6:25:53 PM	WARNING	[D 11:25:53.441 NotebookApp] Searching ['/root/.jupyter', '/root/.local/etc/jupyter', '/usr/etc/jupyter', '/usr/local/etc/jupyter', '/etc/jupyter'] for config files
I am certain the crash happened at mp.Image(...) because I tried running it separately.

@tuhm1 I believe from the logs you're getting this error here: I0000 00:00:1702640456.581241 3672 task_runner.cc:85] GPU suport is not available: INTERNAL: ; RET_CHECK failure (mediapipe/gpu/gl_context_egl.cc:84) egl_initializedUnable to initialize EGL
You would want to run it using the CPU only Colab VM and try it out. If you really want to run the notebook with GPU support you'd have to install a Headless X Server for the NVIDIA GPU.

@kinaryml I tried running it using CPU runtime, the result is still the same.

@kinaryml I tried running it using CPU runtime, the result is still the same.

I'd suggest using the following notebook to load the image and run the task using CPU/GPU as follows:
img = Image.open('66d001c4-bf9d-4883-be03-0fa230669838.jpg')
mp_image = mp.Image(image_format=mp.ImageFormat.SRGB, data=np.uint8(img))

...
base_options=mp.tasks.BaseOptions(
    model_asset_path="efficientdet_lite0.tflite",
    delegate=mp.tasks.BaseOptions.Delegate.GPU
)
...

It should also set the headless X server for you. Just run all the cells in the notebook.
https://colab.research.google.com/drive/1CzhynQzpxzPDfZMUE4whG9jgjieMmRvX?usp=sharing#scrollTo=9q7tszgsFxdZ

And I believe the model you're using ('model.tflite') might have some issues while running in GPU mode and I can't comment on what's exactly wrong there but do use the official MediaPipe model if you can @tuhm1

@kinaryml Your notebook runs without crashing, but the image seems corrupted.
See my notebook here, I don't even create a detector or do any detecting, just create and show mp.Image. Sometimes it crashes, sometimes it shows corrupted image.
By the way, I don't really need GPU support right now.

@kinaryml Your notebook runs without crashing (maybe it just hasn't happened yet?), but the image seems corrupted. See my notebook here, I don't even create a detector or do any detecting, just create and show a mp.Image. Sometimes it crashes, sometimes it shows corrupted image. By the way, I don't really need GPU support right now.

@tuhm1 I would suggest loading the image like this instead:

import mediapipe as mp
mp_image = mp.Image.create_from_file('66d001c4-bf9d-4883-be03-0fa230669838.jpg')

Please check the notebook out and I hope it works out for you.
https://colab.research.google.com/drive/1YFidEh3xOEtGUAZawrxZzzjQrPXYZVXz?usp=sharing

And I found out what's exactly going wrong too btw. Apparently the image data loaded by Pillow isn't exactly usable by MediaPipe at this point of time and when I tried to use OpenCV to do the same it's all good.
img = cv2.imread("66d001c4-bf9d-4883-be03-0fa230669838.jpg")
img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
mp_image = mp.Image(image_format=mp.ImageFormat.SRGB, data=np.uint8(img))

Check out this notebook too.
https://colab.research.google.com/drive/1CzhynQzpxzPDfZMUE4whG9jgjieMmRvX?usp=sharing

@kinaryml Thank you. Creating mp.Image from cv2 works.
But the detection results when using mp.Image.create_from_file seem random.

cv2
create_from_file

The notebook: https://colab.research.google.com/drive/1YQ3KS2Sr_knhGqC1xfTT7BuDl_5wqQa5?usp=sharing
Maybe the docs should recommend using cv2 for now.


SD Colab not working

I have deleted all my SD folders and started fresh. I use free colab so I can't run 2.0 models so I'm only interested in 1.5 features etc. Is there any way you can put the old colab version back that you don't need to update, and start a new one for 2.0 compatible? Merging them sounds unnecessarily complicated.
Final cell output:

you are using an outdated colab, safetensors dependency was added a few hours ago

Refresh got me the new version.
Generated an error when running with update repo.
Deleted all again, disconnected runtime. Now working.


Private Key Format should be human readable

Background
CovenantSQL Private Key is encrypted with user inputted master key with a key hash suffix but stored in binary. It's not suitable for copy & paste or backup.
Goal
Private Key serialization and format can be identical with Bitcoin：

https://en.bitcoin.it/wiki/Private_key
https://en.bitcoin.it/wiki/Mini_private_key_format

this maybe a broken change, is it acceptable? Or do I need to implement a compatible version for the original private key file loading function LoadPrivateKey?

a compatible is better


BAM ingest

BAM could be streamed for single reads but FIFOs are unreliable for paired file input to Minimap2 due to multiple passes of input files? Review later


Correction in the main of the utils.py file

There was a small mistake, where you didn't consider the decoder_input. I corrected it by adding it and it works !
Thank you

Did someone else test this? What does it do exactly?


cudaErrorNoKernelImageForDevice does not produce async error

Bug summary
When compiling for a CUDA target not supported by the available hardware, kernels are simply not executed, without any notification.
To Reproduce
When I compile this program for sm_86 and run it on a RTX 2070 (sm_70), I get no error message whatsoever:
syclcc --hipsycl-targets="cuda:sm_86" test.cpp -o test && ./test
#include <sycl/sycl.hpp>
int main() {
    sycl::queue q{sycl::gpu_selector_v};
    q.parallel_for(sycl::range<1>(10), [](sycl::id<1> idx) {
        printf("hello %lu\n", idx[0]);
    });
    q.wait_and_throw();
}

Running through compute-sanitizer reveals the issue:
compute-sanitizer ./test
========= COMPUTE-SANITIZER
========= Program hit cudaErrorNoKernelImageForDevice (error 209) due to "no kernel image is available for execution on the device" on CUDA API call to cudaLaunchKernel.

Yeah, this is a known issue. The core problem is that in the cuda and hip compilation flows, we never see the cudaError_t object returned from cudaLaunchKernel, because the cudaLaunchKernel call is auto-generated by clang's CUDA/HIP driver.
And for whatever reason, the error then does not show up in the CUDA runtime error state either, so I'm not sure how to retrieve this information.
The generic SSCP compiler --hipsycl-targets=generic does not have this problem, so if you need better validation you could give it a try.

Yeah, this is a known issue.

I figured as much, I just wanted to document it somewhere.

The generic SSCP compiler --hipsycl-targets=generic does not have this problem, so if you need better validation you could give it a try.

I did actually briefly try it for the first time today to see if it would resolve this issue, but it exploded in other ways (on the sm_86 machine with "'+ptx86' is not a recognized feature for this target (ignoring feature)" followed by "cuda_executable_object: could not load module (error code = CU:218)", on the sm_70 machine just with the latter message).

Other causes can be calls to functions that are not yet supported on SSCP, such as printf or SYCL 2020 group algorithms.

Ah yes, I was compiling the above example (which uses printf).


Hatching egg not working

Hatching egg not working..
Because
https://elb.seeddao.org/api/v1/egg/me?page=1
Response
{
  "data": {
    "total": 1,
    "page": 1,
    "page_size": 20,
    "items": [
      {
        "id": "3b17d482-6bbs-415d-a976-cb75f62e3dea",
        "owner_id": "8b97d472-6bba-815d-a976-bb35f63e3bfa",
        "status": "in-inventory",
        "type": "basic"
      }
    ]
  }
}

this api check how many egg you have,
I think you have to check line 172 in tapper.py

Its just hatch egg for new account after claim first egg


Add lifecycle to Whitehall MySQL backup bucket

I already opened this two weeks ago 😞  https://github.com/alphagov/govuk-terraform-provisioning/pull/71


Fix incorrect relative path for package.json

This is causing DefinitelyTyped CI builds to fail.
Updating the relative path to match the one used on line 45 fixed this for me locally.
This seems to have been unintentionally been broken in https://github.com/microsoft/DefinitelyTyped-tools/pull/403

Thanks for the effort, but the path wasn’t wrong per se; the output structure of the package was.


Allow local terminal on live share

Issue Type: Feature Request
Real Case Scenario: Me and my partner are working on an Electron app and we need to use the terminal to test the app and look for bugs. just screen sharing 1 screen and having the guest tell you where to navigate to in the app is just too much.
A good solution will be the ability to open a local terminal on the Live Share folder, so back to the real case: The guest will open a local terminal and run electron appcore.js. it will work because the guest has electron installed on his computer too.
(Sorry if I made it over complicated)

Hey @somuchgoldy we do provide shared terminal in live share session. You can check it out at : https://docs.microsoft.com/en-us/visualstudio/liveshare/use/vscode#share-a-terminal
Is this what you are looking for?

No, I am looking for a local terminal. one that guests can run commands on with the root directory available to use in it. so like 1 user can run Electron if he has it and it will work and for the other, that has no Electron installed, it will error because they have no electron installed.

Closing this as a duplicate of #3524.


Use nslsii.configure_base(...)

Resolves #52.
This PR contains commits from #53, so that one should be merged prior to this PR.

Thanks for your review, @ambarb! I did not see any questions. Did you submit them with your review? Or was everything answered during my visit on Monday?

It was tested thoroughly at the beamline by @ambarb, merging.


{AttributeError} 'Certificate' object has no attribute 'sha256_fingerprint'

show_Certificate(cert, short=False) in apk.py raises AttributeError.
print("SHA512: {}".format(cert.sha256_fingerprint)) call should be in try-catch.
Besides, there is an inconsistency in the print (label vs. value): SHA512 vs. sha256_fingerprint.
System Information

Androguard Version: master (3.2.0)
Python Version: 2.7
Operating System: macOS

Sample file (md5: 615fe78f3a644cb63df8b7918fb8d503)

you are right, this is a bug caused by #486
But sha256_fingerprint should be accessible on the certificate.
Can you check what version of asn1crypto you are using?

@gurol have you checked your asn1crypto version? I also changed the setup.py to download a version which should work.

Yes, it was 0.22.0. It is OK with 0.24.0 (the latest now).

okay thanks for the confirmation!


feat(state): enable fee granting

Resolves https://github.com/celestiaorg/celestia-node/issues/3256
Tested on mocha:

Run funded light node and grant unlimited fee to the newly created FN:
celestia state grant-fee celestia12psg90lwvxdktnqerr2p5mxuw2v3je497uv6tj 2000 1000000 --node.store ~/.celestia-light-mocha-4/

Run FN and submitted blob:
celestia blob submit 0x42690c204d39600fddd3 'gm' --node.store ~/.celestia-full-mocha-4/
Result: blob was successfully submitted:

{
  "result": {
    "height": 1562820,
    "commitments": [
      "IXg+08HV5RsPF3Lle8PH+B2TUGsGUsBiseflxh6wB5E="
    ]
  }
}

Run revoke-fee cmd on the LN:
celestia state revoke-grant-fee celestia12psg90lwvxdktnqerr2p5mxuw2v3je497uv6tj 2000 1000000 --node.store ~/.celestia-light-mocha-4/

Submitted blob from the FN and got an error back:

{
  "result": ": insufficient funds"
}

Run grant fee with a very small limit:
celestia state grant-fee celestia12psg90lwvxdktnqerr2p5mxuw2v3je497uv6tj 2000 1000000 --amount 10 --node.store ~/.celestia-light-mocha-4/

Submitting blobs now returns an error:

{
  "result": ": fee limit exceeded"
}

Codecov Report
Attention: Patch coverage is 13.93443% with 105 lines in your changes are missing coverage. Please review.

Project coverage is 44.90%. Comparing base (2469e7a) to head (29d4916).
Report is 21 commits behind head on main.

Files
Patch %
Lines

nodebuilder/state/cmd/state.go
18.36%
40 Missing :warning:

state/core_access.go
17.02%
33 Missing and 6 partials :warning:

nodebuilder/state/mocks/api.go
0.00%
18 Missing :warning:

nodebuilder/state/state.go
0.00%
4 Missing :warning:

nodebuilder/state/stub.go
0.00%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3304      +/-   ##
==========================================
+ Coverage   44.83%   44.90%   +0.07%
==========================================
  Files         265      271       +6
  Lines       14620    15024     +404
==========================================
+ Hits         6555     6747     +192
- Misses       7313     7513     +200
- Partials      752      764      +12

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

Can you try this approach and see if this works? 🙏
https://github.com/celestiaorg/celestia-node/issues/3284

Hey @Bidon15
Please find all info below:
celestia-appd tx feegrant grant \
  celestia1ly7vmh26hffvau52ktnxff557t4u8thh0gwtyc celestia12psg90lwvxdktnqerr2p5mxuw2v3je497uv6tj \
   --home ~/.celestia-light-mocha-4/keys \
   --node public-celestia-mocha4-consensus.numia.xyz:26657 \
   --spend-limit 1000000utia \
   --allowed-messages "/cosmos.bank.v1beta1.MsgSend,/celestia.blob.v1.MsgPayForBlobs" \
   --chain-id mocha-4 \
   --keyring-backend test \
   --fees 20000utia \
   --broadcast-mode block \
   --yes

https://mocha-4.celenium.io/tx/4a317410cf3a0ccc86169a1774d796fc3f37a47f109f7a00664ea155fcc86e9b
https://mocha-4.celenium.io/tx/165865c66fa785bae7b9e73b21abe20b1c0cff97ad1a80dbde0b3a6ee29f4003

Will node API eventually support all transactions that can be submitted to the Celestia state machine?

I would say so, considering merge and API unification efforts

Thoughts or objections?

I like the general principle of it doesn't matter which node you talk to, they all have the same API


fisher broke my shell...

Broke install... again.  Shouldn't it be a goal to... keep something as someones shell/terminal/console in a working state.  I had this problem with oh-my-fish and thought fisherman was greener pastures.  I should just expect this with fish frameworks?
I did a fisher update, got a bunch of errors, opened-a-new terminal to not have a fisher command at all, and not have a theme.  I manually source the ~/.local/share/fisher/fisher.fish file (yes which IS in the config.fish) in order to see the fisher command again.
Ran fisher update again and seemed to have worked. I see fisher and theme opening a new terminal. Only now it cries about a non-standard setup detected when trying to update.  Exactly what is non-standard now that has been perfectly fine for the last 6+ months, and was perfectly fine when i did fisher update 3 days ago. The update doesn't warn of these changes, doesn't explain the changes, doesn't aide in what the user needs to change, likes to say ARGH a lot.
I see nothing in the repo, or past issues that would raise awareness of "you are going to break everything".
> pwd
/Users/context/.local/share/fisherman
 > git show HEAD
commit ca735556eec3a816a851725110bbae6fa1a163ec
Merge: 57fdbd6 bd6b63f
Author: detailyang<EMAIL_ADDRESS>Date:   Tue Apr 19 11:53:37 2016 +0800

    Merge pull request #199 from detailyang/thanks

    add new contributor to the THANKS.md

> fisher --version
fisher version 1.4.0
> fisher update
9 ⠧
cat: /Users/context/.local/share/fisherman/VERSION: No such file or directory
Aye! Fisherman updated from 1.4.0 to  (5s)
fish: Unknown command '__fisher_plugin_validate'
~/.local/share/fisherman/functions/fisher_update.fish (line 1): __fisher_plugin_validate $item
                                                                ^
in command substitution
	called on line 0 of file ~/.local/share/fisherman/functions/fisher_update.fish

in function 'fisher_update'
	called on line 1 of file -

from sourcing file -
	called on line 60 of file /usr/local/Cellar/fish/2.2.0/share/fish/functions/eval.fish

in function 'eval'
	called on line 51 of file ~/.local/share/fisherman/functions/fisher.fish

in function 'fisher'
	called on standard input
	with parameter list 'update'

fisher: '' is not a valid plugin
fish: Unknown command '__fisher_plugin_validate'
~/.local/share/fisherman/functions/fisher_update.fish (line 1): __fisher_plugin_validate $item
                                                                ^
in command substitution
	called on line 0 of file ~/.local/share/fisherman/functions/fisher_update.fish

in function 'fisher_update'
	called on line 1 of file -

from sourcing file -
	called on line 60 of file /usr/local/Cellar/fish/2.2.0/share/fish/functions/eval.fish

in function 'eval'
	called on line 51 of file ~/.local/share/fisherman/functions/fisher.fish

in function 'fisher'
	called on standard input
	with parameter list 'update'

fisher: '' is not a valid plugin
fish: Unknown command '__fisher_plugin_validate'
~/.local/share/fisherman/functions/fisher_update.fish (line 1): __fisher_plugin_validate $item
                                                                ^
in command substitution
	called on line 0 of file ~/.local/share/fisherman/functions/fisher_update.fish

in function 'fisher_update'
	called on line 1 of file -

from sourcing file -
	called on line 60 of file /usr/local/Cellar/fish/2.2.0/share/fish/functions/eval.fish

in function 'eval'
	called on line 51 of file ~/.local/share/fisherman/functions/fisher.fish

in function 'fisher'
	called on standard input
	with parameter list 'update'

fisher: '' is not a valid plugin

Opening a new terminal
context@zephyr ~> fisher update
fish: Unknown command 'fisher'
context@zephyr ~> source .local/share/fisherman/fisher.fish
context@zephyr ~> fisher update
WARN Non-standard setup detected.
INFO Updating 6 plugins
ARGH Fetching conf.d
ARGH Fetching cache
ARGH Fetching completions
ARGH Fetching man
ARGH Fetching functions
ARGH Fetching scripts
OKAY Done in 707ms

@zacheryph
Here is the relevant issue and history of how we went from 1.5 to 2.0: https://github.com/fisherman/fisherman/issues/204
The change from 1.5 to 2.0 was massive, so that should explain all the problems you were / are having.
To upgrade to 2.0 correctly you need to remove the old fisherman, and then follow the instructions on the README to install the new one.
If you don't want to do that and don't mind running a script I wrote for this, there's also:
curl -L git.io/fisher-up-me | fish

@zacheryph Let me know if the above instructions don't work or you still other help troubleshooting the upgrade.

Yes this got this working.  Just a little frustrating to constantly have this happen. ;)  It might be helpful to others to make a note of the breaking change in the README. there is an install section but no upgrade/upgrading one.

@zacheryph The 1.5 -> 2.0 upgrade was too reckless, but after working so much on this thing, I am quite confident it was for the best. Please keep me posted if you encounter any further problems.

It might be helpful to others to make a note of the breaking change in the README. there is an install section but no upgrade/upgrading one.

A (temporary) note on how to upgrade from 1.5 deserves some mention indeed. I'll get around that in a bit.


Service Unavailable

Not able to connect

did u have same problem like me in #46 ?

Can you provide more information? Please, next time use one of the issue templates provided.


github.action description is wrong

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Context and expression syntax for GitHub Actions
What part(s) of the article would you like to see updated?
github.action description to match my GitHub Action execution results.
Additional information
No response

@alvinseville7cf Sorry about that! I am triaging the PR for the writer's review 👀 ⚡

Hi @emilyseville7cf, the documentation seems to match your output to me. Can you clarify the specific differences you're seeing? Thanks!

@lecoursen, instead of run I see __run (value of github.action) and instead of run2 I see __run_2 .


Patch notes link doesn't wrap on main page

The patch notes link on http://streamus.com/ currently doesn't wrap on small screens. Specifically chrome on android. The link overflows and makes the entire main page horizontally scrollable.

This belongs in the website repo


Minimal video corpus for training

How much minimal video corpus size for training? For testing purpose and low quality result? Minutes? Hours?

Sorry, please forgive me that I can't understand your question...

Sorry for my terrible english.
For training and testing you suggest Kinetics-400 dataset. This is way too big for my hardware but I am can download and use small subset of it. How small?

Sorry for my terrible english.
For training and testing you suggest Kinetics-400 dataset. This is way too big for my hardware but I am can download and use small subset of it. How small?

You can probably do a decent test run with ~20, 000 video clips. I recommend processing the videos first (decoding, resizing) and then loading that preprocessed dataset for training to save resources. Along with setting a low resolution and frame count, as well as reducing the number of model parameters, should make training a VAE possible on maybe ~16-24GB VRAM cards, optimistically.
I'm not related to the paper's authors, however, and I don't know what the training efficiency of their VAE is.


Big lag when Subscriptions section is loading then crash when feed section selected

Describe the bug
I have around 750 subscriptions.There is a bug lag when I choose the subscription section. Then, if I click on the feed section after that Fritter crash
To Reproduce
Steps to reproduce the behavior:

Have more than 700 subscriptions
Click on subscription -> lag
Click on feed -> crash

Device
Your devixe : Honor 6X, 3Go of Ram, Android 7
Fritter : v2.13

Exactly the same here, only with fewer subscriptions -- around 550. It hardly ever manages to get past this and display any tweets, probably because something times out. After many attempts over several days, today it made it once, and it looks fantastic. This seems to mean it fails under certain conditions, but it can actually manage 500+ subscriptions and it's not fundamentally broken.
Moto G4, Android 7, Fritter 2.13


Will the RFT builder block work in a galacticraft space station dimension?

I am trying to build the giant sphere basis for the death star using the builder, i have it set up correctly and the preview blocks display exactly what i want but it refuses to build anything even when supplied with materials, power and redstone

How are you giving it the materials? Chest has to be on top or below

i tried both

Ok, first I need your version of RFTools. Then show me some pictures of your setup and the gui as well as the configuration of the card

1.7.10 RFTools 4.23
http://imgur.com/a/njaIz

A button will not work. You have to keep giving it a redstone signal. A button only gives a redstone pulse. Use a lever instead

Oh right derp. thanks


To Update the basics to 1.15

mongo monkey patch
require "mongo"
add to lib_mongo.cr
fun mongo_init = mongoc_init (Void*)
fun mongo_cleanup = mongoc_cleanup (Void*)
add to mongo module after set log handler
LibMongoC.mongo_init(nil)
at_exit { LibMongoC.mongo_cleanup(nil) }

@washu Thank you for your support and interest in helping to improve the library. This afternoon the changes you mention will be added.

In this commit the change was added Commit @washu


Upgrade pulumi-terraform-bridge to v3.88.0

This PR was generated via $ upgrade-provider pulumiverse/pulumi-unifi --kind=bridge --target-bridge-version=latest.

Upgrading pulumi-terraform-bridge from v3.86.0 to v3.88.0.

Superseded by #205


Implementation of OCSVM with SGD (Online OCSVM)

Recent update in sklearn 1.0 implements an online OCSVM:
https://scikit-learn.org/stable/auto_examples/release_highlights/plot_release_highlights_1_0_0.html#online-one-class-svm
I tried to implement the online OCSVM in PyOD format and confirmed that it could significantly reduce the time complexities while keeping its detection performances.
https://gist.github.com/tam17aki/539dc31257c1fba18bc2da6975793ad7
https://gist.github.com/tam17aki/bd491aeb6050cabe28b2542c7cc5b1cd#file-benchmark_ocsvm-ipynb
So the issue is to consider whether to add a new option to the existing OCSVM module for switching a batch type optimization and an online optimization or add a new API, like the "svd_ocsvm" module.
We have only "ocsvm" module in the former case.
We have the existing "ocsvm" and a new "svd_ocsvm" modules in the latter case.
In any case, PyOD needs to support sklearn 1.0 :)
Best regards,
Akira

This is great! Maybe a seperate file/class called OOCSVM? online OCSVM? So that we do not need to break the current OCSVM. thanks!


Transform subscriptions ruin animation sync

Having a transform subscription on an Actor will cause its animations be extremely jittery. This issue does not appear until multiple users join a session. The first user to join will not experience the issue.

Thanks for the report. Sounds like a regression.

Updated Information: The animations in question are from a gltf and the jitteriness occurs on child objects attached to the gltf with the active animation.
This is not limted to jitter, it can cause child objects to spawn in the the wrong location.

Needs investigation

After talking with Steven further I believe it is because gltf animation sync has not been implemented.


Pre-rendered site serves some routes as generic index

As an example, my generated site yields:
index.html
news.html
/news
  news-article-1.html

When I point a basic HTTP server at the generated files, /news/ resolves to a generic HTML index of the /news directory. This is because the news directory takes precedence over the news.html file, so news.html is ignored and there is no /news/index.html so it uses a generic index.
My suggestion would be to just name all HTML files index.html in directories with their identifiers. This should lead to more predictable routing.

I had issue with that in the past: some static deploy tools don't understand one of the two formats (I don't remember if it was path/index.html or path.html which was problematic). If I remember correctly it was GitHub pages who was buggy about it. What's your experience on that?
I'll implement your suggestion, worst case we'll see when users complain about it.

I've never had issues with index.html based file trees, but I haven't used a great variety of static hosting services (I mostly use S3). You could make this a configuration option in case some deployments want it the other way?

Yes that's the plan.


Doesn't work with declined permissions

For both modes List and Dialog SPPermissions doesn't open alert, when I declined permission at the first usage.

You don't forget override method for alert?

I talked about the example app

Please, read section about alert in readme. All ok with example.


refactor: add timeouts with retries to runTaskFunction()

This adds 30s timeouts with 3 retries to the async places inside
runTaskFunction that might be causing the zero concurrency bug.
We now get a warning every time such place timeouts and a hard
failure after 3 retries.
Related: #997

30s is way too breaking. The default retry in client is 500ms and it exponentially backs off 8 times. So that's way more than 30s.
So fetchNextRequest, marking handled and other operations need to timeout after at least the max time for exp back off.
session function and handleFailedRequest are custom functions of users. I wouldn't be too surprised if especially the session function could sometimes take a few minutes, e.g. when solving a captcha inside it.

What would you suggest? Making it something like 5 min, and maybe make it configurable too?

30s is way too breaking. The default retry in client is 500ms and it exponentially backs off 8 times. So that's way more than 30s.

So 0.5+1+2+4+8+16+32+64=127,5s?

Maybe handleRequestTimeout for each?
Dunno, but this should not break anything because it respects whatever the User expects as maximum time for completion.

Merging so I can test it on the platform before shipping new stable.


doc dependencies

docker uses node8
node version 8.x
npm version ?
truffle version 4+?
solidity version 0.4.21+

yep, it should be fix in docker, docker compose, package file

all dependencies is presented in package lock file, docker file, config file.


Incorrect permissions on weights google drive link

Hi, I think you have to allow your google drive weights link to be open, they are currently not accessible publicly.

Thanks for reminding us. We just changed the permission so that anyone should be able to access it.
Training a new model using the default configuration should result in a similar performance to the example weights.

Much thanks. Very grateful for this paper and code.


CloudFormation on AWS for deploying the REST API for a developer

Use SSL certificates for client authentication instead of Cognito.
ALB is desirable.
Swagger is also desirable but is more interesting as it should be behind User Authentication (e.g. Cognito) but should be communicating to the REST API with SSL certs.

This work is being done in https://github.com/Senzing/aws-cloudformation-dev-rest


plugin_reload to write logfile

plugin_reload does not write anything to /mnt/store0/log/ thus is unknown when / how what the output of this is.
make sure the output gets written into a logfile

fixed
fmadio/fmadio20@7642581


Loss is nan on training  RefineDet using LISA traffic dataset

I used LISA traffic dataset as the training dataset and translated all images and annotations to VOC format.
But when training, the AL, AC and OL are nan:
Epoch:1 || epochiter: 220/694|| Total iter 220 || AL: 3.7427 AC: 4.2145 OL: 2.7985 OC: 3.4148||Batch time: 0.8865 sec. ||LR: 0.00100000
Epoch:1 || epochiter: 230/694|| Total iter 230 || AL: nan AC: nan OL: nan OC: 518.2673||Batch time: 0.7096 sec. ||LR: 0.00100000
Epoch:1 || epochiter: 240/694|| Total iter 240 || AL: nan AC: nan OL: nan OC: 0.8749||Batch time: 0.6676 sec. ||LR: 0.00100000
My platform is Pytorch v0.4, cuda9.2.
I have modified the code in refine_multibox_loss.py because the dimensions of tensors(loss_c and pos ) are not matched. Is that reason?
The source code:
#Hard Negative Mining
loss_c[pos] = 0
My code:
loss_c[pos.view(-1,1)] = 0
Could you help me ?
@lzx1413

I am working on the version 0.4 now. I will test the performance soon on 0.4. more details can be seen in branch 0.4.


The 2nd note on limits is incorrect

The 2nd note on this page has incorrect information on the number of Speech resources that can be created.  ALL Cognitive Services resources are limited by the information here:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-cognitive-services-limits

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

ID: c8162cca-9883-c168-a631-bb6a06d979d2
Version Independent ID: 8f9d41d1-79c7-ff5f-25d2-318c506877e2
Content: What is the Speech service? - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/overview.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @trevorbye
Microsoft Alias: trbye

@dfulcer Thanks for the feedback. We are investigating the issue and will update you shortly.

The incorrect information is on this page:
https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/overview
The 2nd purple colored note reads:

This is incorrect.

Thanks for the details. I have assigned to the content author for the document update. @trevorbye Could you please update the following purple colored note.

Fixed in a PR and the content goes live on 9/22.
#please-close

This is still not correct.  A user cannot create an unlimited number of standard tier subscriptions in one or multiple regions.  Please refer to the original issue report and the reference URL I included. A user can only create 100 Speech resources (not subscriptions) in a single region OR a total of 200 resource per Azure subscription across ALL regions.
Maybe the note should be updated to something like this?
!Note
You can create up to 100 Speech resources in a single Azure region per Azure subscription or a total of 200 resources of any type of Cognitive Service across all Azure regions per Azure Subscription.  See Azure Cognitive Services limits for more information. However, you can create only one free-tier Speech resource.  Model deployments on the free-tier that remain unused for 7-days will be decommissioned automatically.


UIBULKED-314 Remove "New bulk edit" button

Purpose

UIBULKED-314
Remove code related to "New bulk edit" button
Approach

TODOS and Open Questions

Learning

Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.

[ ] I've added appropriate record to the CHANGELOG.md
Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
[ ] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

@vashjs please increase test coverage. But still LGTM

Please add this ticket to CHANGELOG.

@vashjs please increase test coverage. But still LGTM

New functionality wasn't added, nothing to cover here.


Don't use deprecated GetContainerLogsAsync

Tried to get rid of the deprecation warning. The encoding is the same as in the deprecate function.

Coverage increased (+0.05%) to 83.721% when pulling 5aa9ec341c9bed25512167bd8786d4aeed93f375 on TheConstructor:feature/LogReading into 04cd8d6a786d27cf126dbf490b5592542779f4b8 on testcontainers:master.

Removed redundant using


ContainerServices.generateContainerServicesRequestHandler does not return the container service if it doesn't implement IComponentRouter

Describe the bug
If a container service doesn't implement IComponentRouter, it doesn't returned by the generateContainerServicesRequestHandler function.
After a bit investigation the issue seems to be in the RequestParser.createSubRequest() function, the condition startingPathIndex > this.pathParts.length is not correct.
But I'll leave it to your guys to fix it since I'm not super familiar about the impact.
   /**
     * Creates a sub request starting at a specific path part of this request's url
     *
     * @param startingPathIndex - The index of the first path part of the sub request
     */
    public createSubRequest(startingPathIndex: number): IRequest | undefined {
        if (startingPathIndex < 0 || startingPathIndex > this.pathParts.length) {
            return undefined;
        }
        const path = this.pathParts.slice(startingPathIndex).join("/");
        return {
            url: path + this.query,
            headers: this.headers,
        };
    }

Closing this bug because the larger plan is to remove the Aqueduct Container Services code in October. It has been deprecated and replaced by the Providers pattern.
#3799