Clean up Kubelet RESTful APIs

More and more external systems, such as Heapster is using Kubelet RESTful API, and we are stabling Kubernetes API, now it is the time to clean up Kubelet's.

Kubelet should also use the apiserver infrastructure.

In order to properly secure the kubelet, we'll want to reuse the same authentication / authorization interfaces we have in the master.  We also want to have a consistently structured API.  The initial work here would be to replace the Kubelet server with a true apiserver object, with a versioned beta, and begin evolving that API.

My name is Nataliia and I am student who plan to apply for GSoC for this round.
I have some thoughts on the proposal and it would be glad to discuss it with someone before submitting.
Unfortunately, there are few development docs and issues are formulated in the way, to be understandable for internal person, so without background it is really hard to understand what is going on.
My current understanding of it is like this:
There is primary/master API of the kubernetes, that are versioned and like more-or-less stable (spread among many files, cannot find single file with it).
There is also API of the individual Kubelet (that lies in the /pkg/kubulet/server.go), that now is 'unofficial' state, it just exposes what it exposes. Like implementation is the only documentation for it. So the idea is to structure it, make more predictable and stable. To do it, first you should migrate to the same libraries that master API uses (like apiserver and all supporting auth stuff). And then make it more consistent and predictable.
So the questions are:

in general understanding right?
is apiserver general enough or is it too connected to the master API and should be also changed during the migration of Kubelet API?
what about versioning? How versions of master and kubelet api regard to each other or should they just follow one version?
stuff like conversions.go and types.go are dealing with representation of the objects, and probably I should not deal with them, but they are version specific...., here I am totally confused.

Sorry if questions are too far away from the reality :)

Nataliia,
I think you got it pretty much exactly right.  We should re-use the code
that is in pkg/apiserver/... as much as possible to replace/re-implement
the code that is in kubelet/server.go.
We can do this piece by piece, replacing one http handler at a time.
I wouldn't worry too much about conversions.go and types.go, they are
basically the files necessary to implement the various versioned APIs, but
unless you need to add new API objects (and I'm not sure you will), you can
basically just use a Codec.encode/decode and assume that everything "just
works"
Please feel free to join us on IRC at #google-containers and we can give
you help in realtime.
Many thanks for your interest!
--brendan
On Tue, Mar 17, 2015 at 7:06 AM, Nataliia Uvarova<EMAIL_ADDRESS>wrote:

My name is Nataliia and I am student who plan to apply for GSoC for this
round.
I have some thoughts on the proposal and it would be glad to discuss it
with someone before submitting.
Unfortunately, there are few development docs and issues are formulated in
the way, to be understandable for internal person, so without background it
is really hard to understand what is going on.
My current understanding of it is like this:
There is primary/master API of the kubernetes, that are versioned and like
more-or-less stable (spread among many files, cannot find single file with
it).
There is also API of the individual Kubelet (that lies in the
/pkg/kubulet/server.go
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go),
that now is 'unofficial' state, it just exposes what it exposes. Like
implementation is the only documentation for it. So the idea is to
structure it, make more predictable and stable. To do it, first you should
migrate to the same libraries that master API uses (like apiserver and all
supporting auth stuff). And then make it more consistent and predictable.
So the questions are:

in general understanding right?
is apiserver general enough or is it too connected to the master API
and should be also changed during the migration of Kubelet API?
what about versioning? How versions of master and kubelet api regard
to each other or should they just follow one version?
stuff like conversions.go and types.go are dealing with
representation of the objects, and probably I should not deal with them,
but they are version specific...., here I am totally confused.

Sorry if questions are too far away from the reality :)
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/2098#issuecomment-82370949
.

@AAzza Welcome! Yes, as @brendandburns also responded, you have the right idea.
The apiserver library is used by at least one other component, the Openshift master, so there's some hope that it's general enough, but we won't really know until we try. We may need a new generic registry implementation, though, since the master components both use etcd-backed registries.
Though hopefully you won't need to do much with the representation conversions, we do have a brand new documentation that explains how the API machinery works:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/devel/api_changes.md

BTW: handlers are registered here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go#L118
Note that we're in the progress of eliminating many of these handlers. Kubelet will send information to apiserver. #4561 #4562
I would eventually like Kubelet to export the same pod API as apiserver, though.
Also note that we're in the process of moving to v1beta3 for all components, though kubelet currently only supports v1beta1. #5475

And there is #4685 which attempts to replace '/stats' end point.
On Tue, Mar 17, 2015 at 10:18 PM, Brian Grant<EMAIL_ADDRESS>wrote:

BTW: handlers are registered here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go#L118
Note that we're in the progress of eliminating many of these handlers.
Kubelet will send information to apiserver. #4561
https://github.com/GoogleCloudPlatform/kubernetes/issues/4561 #4562
https://github.com/GoogleCloudPlatform/kubernetes/issues/4562
I would eventually like Kubelet to export the same pod API as apiserver,
though.
Also note that we're in the process of moving to v1beta3 for all
components, though kubelet currently only supports v1beta1. #5475
https://github.com/GoogleCloudPlatform/kubernetes/issues/5475
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/2098#issuecomment-82745685
.

The logs and remote execution endpoints are somewhat special - I would save those for last, because https://github.com/GoogleCloudPlatform/kubernetes/issues/3481 will change how they behave on the apiserver and we're likely to want the kubelet API to be consistent (same options).  @csrwng
----- Original Message -----

And there is #4685 which attempts to replace '/stats' end point.
On Tue, Mar 17, 2015 at 10:18 PM, Brian Grant<EMAIL_ADDRESS>wrote:

BTW: handlers are registered here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go#L118
Note that we're in the progress of eliminating many of these handlers.
Kubelet will send information to apiserver. #4561
https://github.com/GoogleCloudPlatform/kubernetes/issues/4561 #4562
https://github.com/GoogleCloudPlatform/kubernetes/issues/4562
I would eventually like Kubelet to export the same pod API as apiserver,
though.
Also note that we're in the process of moving to v1beta3 for all
components, though kubelet currently only supports v1beta1. #5475
https://github.com/GoogleCloudPlatform/kubernetes/issues/5475
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/2098#issuecomment-82745685
.

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/2098#issuecomment-83058956

Thanks you for the replies! It really help to understand what is going on and what to do. I just have last concern.
The GSoC will be during summer. Till that, I hope, some of the issues/pull requests will be solved/merged (surely, a lot of others will appear). But the question is how does it correlate with the any planned releases? Like this project could be not-very-trivial change (if Kubelet API will be changed or whatever) and if there will be 1.0 release around that time, probably there could be problems with that. Just have no clue, what the release plans are and haven't found anything except roadmap and versioning. And there is no specific dates/milestones, only description how releases should look like when they are done.

@AAzza If the work can be decomposed into small enough pieces, we'd prefer to just merge them into the master branch. If that's too hard to do, we may need to keep the work in a branch in your fork until we create a 1.0 branch, which should happen sometime in June.
As part of this, we should ensure our generic API client library is capable of targeting Kubelet. In fact, I'd like kubectl to be able to target Kubelet directly, as well. (Assuming the node is reachable from wherever the tool is invoked.)

Additional details:

port Kubelet to apiserver/go-restful
ensure the API client can target Kubelet
ensure auth for the API is set up in an acceptable way
auto-generate Swagger-based documentation for the APIs, similar to that exposed by the master
expose at least readonly Pod and Node APIs (identical to the master's) and remove deprecated /podinfo and /nodeinfo, if that hasn't been done yet -- these should be mainly for debugging by summer and won't be targeted by the master
expose versioned APIs only, supporting the same versions as the master (esp. the latest version -- currently v1beta3)
make supported versions and paths discoverable in a manner similar to the master (via GET / and GET /api)
move cadvisor to its own versioned API prefix if it's still exposed directly
perhaps some consolidation/cleanup of other API endpoints

@bgrant0607  Thank you for so detailed answer! If the 1.0 release will be around middle June, we probably will not be able to do stable transition to apiserver, so probably it will be merged after branch creation. Before this we probably can do simple tasks, like remove deprecated endpoints if they will exists still.
About client library. For now I understand for kubelet it leaves in separate file  https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/client/kubelet.go  but after the unification it probably could work with client's main code for nodes and pods. Thank you for pointing this, didn't notice it from the beginning :)
So we want to make (/stats)[https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go#L656] and (/spec)[https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go#L356] to be also versioned?
They return something that still doesn't have a proper type, so probably a little work with types and conversions should be done?
Just crazy idea to evaluate: is it worth to spend a week to change url scheme before moving to apiserver and before release of 1.0. It will be a little bit ugly to do without go-restul for pods and nodes, see the code for /stats endpoint from previous paragraph, where the url is parsed directly. But the benefits is that in 1.0 Kubelet will expose at least some sort of consistent API, that later will be rewritten to the apiserver and more elegant code. Is it worth or I overesitimate the importness of kubelet api for 1.0? :)

@AAzza the half-way point with internal improvements sounds like a good idea. It sounds like you want to do the public-facing changes first (before 1.0) to allow for the internal cleanups to happen in between. This should give us flexibility going forward. One concern would be how documented that versioned API would be. Initially we could do it manually before we move onto swagger-based docs.
Let's see what @bgrant0607 thinks :)

Yes, cleaning up the API is more important/urgent than improving/changing the implementation, but changing the implementation would be less controversial and less design-intensive. We could try to hash out the API details first and then decide which way to go based on how much progress is made.

We should close this and open new issues on Kubelet's API(s)

This is fairly out of date at this point.

Was kubelet rest api auth[n/z] ever completed? Is there some doc/issues that discuss this?

There is an authz/n filter in place, @liggitt
On Tue, Jul 12, 2016 at 2:18 PM, Mike Danese<EMAIL_ADDRESS>wrote:

Was kubelet rest api auth[n/z] ever completed? Is there some doc/issues
that discuss this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes/issues/2098#issuecomment-232133308,
or mute the thread
https://github.com/notifications/unsubscribe/ABG_p2t3MPDvYbUYJRToqoiPrErWCjESks5qU9pfgaJpZM4C1iQv
.

@mikedanese https://github.com/kubernetes/kubernetes/issues/11816#issuecomment-148778046 mentions authn/authz for kubelet. https://github.com/kubernetes/kubernetes/pull/14700 added interfaces for authn/authz to the kubelet but didn't wire them to command line options yet. Some of the work around webhook authn and authz could allow the kubelet to use the same authn/authz as the master if we wanted it to.

@liggitt thanks for clairfying.


ui-scroll for ng2

is there any implementation of this directive for angular 2 ?

Expected question! we have plans to make it but currently the answer is "no".

The ngx-ui-scroll v0.0.1 for Angular 5+ has been just released.


[PrematureStopping] Refactor CSignal class to use RxCpp utilities.

This PR should contains the new CSignal implementation which will be using RxCpp. However, there are still some things that needs to be addressed (CSignal::cancel_computation, there is still Windows code etc.).

@geektoni can you write down a simple use case from an algorithm implementation perspective? Thx

@karlnapf Do you mean how this new CSignal will be used?

@karlnapf I made a small code and output example to show the basic behavior that CSignal will allow: https://gist.github.com/geektoni/1afd2daf69a813de64252a296997a8ea

	148 - unit-Signal (OTHER_FAULT)

a bit of a more information
Note: Google Test filter = Signal.*

[==========] Running 2 tests from 1 test case.

[----------] Global test environment set-up.

[----------] 2 tests from Signal

[ RUN      ] Signal.SIGINT_test

/opt/shogun/tests/unit/lib/Signal_unittest.cc:26: Failure

Death test: { CSignal tmp; tmp.enable_handler(); int on_next_v = 0; int on_complete_v = 0; auto sub = rxcpp::make_subscriber<int>( [&on_next_v](int v) { on_next_v = 1; }, [&]() { on_complete_v = 1; }); tmp.get_SIGINT_observable().subscribe(sub); tmp.get_SIGINT_observable().connect(); switch (0) case 0: default: if (const ::testing::AssertionResult gtest_ar_ = ::testing::AssertionResult((on_complete_v == 1))) ; else ::testing::internal::AssertHelper(::testing::TestPartResult::kNonFatalFailure, "/opt/shogun/tests/unit/lib/Signal_unittest.cc", 26, ::testing::internal::GetBoolAssertionFailureMessage( gtest_ar_, "on_complete_v == 1", "false", "true").c_str()) = ::testing::Message(); exit(0); }

    Result: died but not with expected exit code:

            Terminated by signal 6 (core dumped)

Actual msg:

[  DEATH   ] terminate called without an active exception

[  DEATH   ]

[  FAILED  ] Signal.SIGINT_test (286 ms)

[ RUN      ] Signal.SIGURG_test

terminate called without an active exception```


Mount directory to host option

Right one have to use a helper container to make backups of data in containers, which seams like a hacky way to compensate for a still to come feature in Docker.
I propose a mount option which will make directories available on the host. Example:
FROM fedora:22
RUN dnf -y install httpd
MOUNT ["/var/www/html:html:rw", "/var/log/httpd:logs:ro"]
CMD ["/usr/sbin/httpd", "-DFOREGROUND"]

Running
docker build -t test80 .
docker run -d test80

would make the following two directories on the host
/var/lib/docker/mount/test80/html
/var/lib/docker/mount/test80/logs

Here the mount option uses the volume syntax in array form.
This would making backups a lot easier and more intuitive and giving a kind of volume but with correct container file ownership.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

No, we cannot support this.
It would be incredibly dangerous for host security, and makes for potentially very inconsistent builds.
In addition there are already a number of proposals open for support volumes on build, so this would be a dup.


fyi: https://github.com/karolgorecki/goprove

this maybe be of interest to you
https://github.com/karolgorecki/goprove
$ goprove .
Passed tests: 7 of 11
---------------------------------------------------------------
[✔] README Presence: Does the project's include a documentation entrypoint?
[✔] Licensed: Does the project have a license?
[✔] gofmt Correctness: Is the code formatted correctly?
[✔] golint Correctness: Is the linter satisfied?
[✔] go tool vet Correctness: Is the Go vet satisfied?
[✔] Compiles: Does the project build?
[✔] Are the tests passing?
---------------------------------------------------------------
[✗] Contribution Process: Does the project document a contribution process?
[✗] Blackbox Tests: In addition to standard tests, does the project have blackbox tests?
[✗] Benchmarks: In addition to tests, does the project have benchmarks?
[✗] Directory Names and Packages Match: Does each package <pkg> statement's package name match the containing directory name?

Thanks, some good stuff in here that we'll keep in mind for future features. Going to close this out in favor of individual feature tickets.


Typings are broken after recent changes

Describe the bug
Some of urql typings are broken after #2607 was introduced.
To be precise, it is broken in next three files.

https://github.com/FormidableLabs/urql/blob/main/packages/core/src/utils/operation.ts (see line 8 and 14)
https://github.com/FormidableLabs/urql/blob/main/packages/react-urql/src/components/Query.ts (see line 7 and 19 for mismatch)
https://github.com/FormidableLabs/urql/blob/main/packages/react-urql/src/components/Mutation.ts (see line 13 and 29 for mismatch)

Reproduction
It is a typing issue
Urql version
@urql/core 3.0.2
urql 3.0.1
Validations

[x] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
[X] Read the docs.
[X] Follow our Code of Conduct

Hey,
Mind pointing out what is wrong with it, TypeScript in Strict mode isn't having any issues 😅 we ask for a reproduction or at the very least the error the error in question.
You are pointing at three files and telling us it's a typing issue but I can't really go off that as it's succeeding for me.

@JoviDeCroock
Apologize for providing not enough information at the first place 😢 Glad you understood it though.

No worries we got there 😅


feat(security-command-center): add v2 version of SetMuteUndefinedFinding.java

Description
Adds a v2 equivalent of security-command-center/snippets/src/main/java/muteconfig/SetMuteUndefinedFinding.java.
Checklist

[x] I have followed Sample Format Guide
[x] pom.xml parent set to latest shared-configuration
[x] Appropriate changes to README are included in PR
[ ] These samples need a new API enabled in testing projects to pass (let us know which ones)
[ ] These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
[x] Tests pass:   mvn clean verify required
[x] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[ ] This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
[ ] This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
[x] Please merge this PR for me once it is approved

Blocked until #9580 is merged.

Blocked until #9580 is merged.

That PR was merged, and this one is ready to review.

@telpirion Friendly ping.


More Filters

Hello,
Could you please tell me how to add theses filters :
1- Filter by ID-COMPUTER
2- Filter by ID-COMPUTER
3- Add custom SQL query ( select * from computers join company on.....etc )
Thank you in advance.

@HannahJSwystun this is just an example application. You can ask questions about it at the mailing list.


Unable to access my website

domain: rafaelcunha.is-cool.dev

Am i missing something?
Thanks

You need to setup an SSL certificate on your end, most likely. We cannot help with this as you are using NS records and we do not have access to the DNS zone.


Question

we can change android gradle build assembleDebug to assembleRelease?
if we can how idk

https://lime.openfl.org/docs/project-files/xml-format/#certificate

Use <certificate /> tags to add a keystore for release signing on certain platforms.
If you do not include the password attribute, you will be prompted for your certificate password at the command-line.
For Android, the alias will be set to the file name of your certificate by default, without the extension. If the alias name is different, you can use the alias attribute.
If you have set the password attribute, the alias_password attribute will default to the same value. Otherwise you can add an alias-password attribute to specify a different value.
<certificate path="to/certificate.crt" password="1234" alias="my-alias" alias-password="4321" />

i got this error

I assume you followed the instructions to generate a certificate?

I assume you followed the instructions to generate a certificate?

i not have pc i followed this

Well that's your problem. Gotta generate an Android-compatible certificate, and that means following the Android documentation. By searching for "generate Android certificate without Studio," it wasn't hard to find command-line instructions.
Also, making your passphrase public totally defeats the point and might get your app taken down. You gotta use encrypted secrets for security. It might look like this, assuming environment variables are in fact passed through:
- name: Compile
  run: haxelib run lime build android -armv7 -D no-compilation -D luajit_static -D macro-times -D analyzer-optimize -${{ matrix.arch }} --app-version="4.0.0-${{ github.run_id }}"
  env:
    cert_pass: ${{ secrets.cert_pass }}
    cert_alias_pass: ${{ secrets.cert_alias_pass }}

<certificate path="the.crt" password="${cert_pass}" alias="the" alias-password="${cert_alias_pass}" />

Well that's your problem. Gotta generate an Android-compatible certificate, and that means following the Android documentation. By searching for "generate Android certificate without Studio," it wasn't hard to find command-line instructions.
Also, making your passphrase public totally defeats the point and might get your app taken down. You gotta use encrypted secrets for security. It might look like this, assuming environment variables are in fact passed through:
- name: Compile
  run: haxelib run lime build android -armv7 -D no-compilation -D luajit_static -D macro-times -D analyzer-optimize -${{ matrix.arch }} --app-version="4.0.0-${{ github.run_id }}"
  env:
    cert_pass: ${{ secrets.cert_pass }}
    cert_alias_pass: ${{ secrets.cert_alias_pass }}

<certificate path="the.crt" password="${cert_pass}" alias="the" alias-password="${cert_alias_pass}" />

still not working check actions error,and here my current project.xml ig we cant do this i using termux for do certificate (no proot-distro)

You entered the secrets into GitHub, I assume?
I'm guessing Project.xml couldn't read the environment variables, but we can check to be sure:
- name: Compile
  run: haxelib run lime build android -armv7 -D no-compilation -D luajit_static -D macro-times -D analyzer-optimize -${{ matrix.arch }} --app-version="4.0.0-${{ github.run_id }}"
  env:
    test_value: 12345

<echo value="${test_value}" />

Assuming that's the problem, try going back to assembleDebug and using r0adkll/sign-android-release afterwards.

You entered the secrets into GitHub, I assume?
I'm guessing Project.xml couldn't read the environment variables, but we can check to be sure:
- name: Compile
  run: haxelib run lime build android -armv7 -D no-compilation -D luajit_static -D macro-times -D analyzer-optimize -${{ matrix.arch }} --app-version="4.0.0-${{ github.run_id }}"
  env:
    test_value: 12345

<echo value="${test_value}" />

Assuming that's the problem, try going back to assembleDebug and using r0adkll/sign-android-release afterwards.

i added allready on secrets

ig project.xml not reading the secrets

@player-03 i fixed pem file is cert keystore file is key gardle not allows cert file gradle wanrs key file

...And your password is public again, defeating the point. Might as well go back to assembleDebug.

nah bro it's just android port not needed password privacy and its 123456 so people can will reach my cert password lmao


NetKAN/TACLSMining.netkan - showing as incompatible in 1.0.4 despite presence of override

TACLSMining shows as incompatible in GUI for KSP 1.0.4. .netkan overrides for version show support for 1.0.2 through 1.0.4.
I compared this one to a few other working mods, and I can't spot an obvious difference. The only thing I can suspect is '"x_netkan_epoch" : "1",' on line 11 of NetKAN/TACLSMining.netkan

Thanks for spotting that, the epoch bump changes the version number and negates the override. It's happened a couple times, it's a weird interaction.


Add an API README

Signed-off-by: kagarmoe<EMAIL_ADDRESS>:nut_and_bolt: Description: What code changed, and why?
Makes instructions for API documentation easier to find.

[ ] I have read the CONTRIBUTING document.
[ ] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

It might not be a bad idea to put a symlink in dev-docs to the API readme.

That's what I was thinking of, too.


Enable image backends on macOS

Enable image backends on macOS because we have terminals with graphics support on macOS.
mlterm supports sixel:

kitty:

NOTE: iTerm2 also supports sixel but it shows broken output (I think it is a iTerm2 issue):

Enable image backends on macOS because we have terminals with graphics support on macOS.

Great! I don't have a machine running macOS so I couldn't test it for myself.
Your PR looks good. What would you think about replacing #[cfg(not(target_os = "windows"))] with #[cfg(not(windows))] ?

Your PR looks good. What would you think about replacing #[cfg(not(target_os = "windows"))] with #[cfg(not(windows))] ?

Applied in 0cf7398b.

iTerm2 also supports sixel but it shows broken output

Yes, that's weird. Have you tried onefetch -i /path/to/image --image-backend sixel

I've already tried. It is not a problem of image backend selection.

FYI: I've reported a issue on iTerm2 https://gitlab.com/gnachman/iterm2/-/issues/9204, which causes the broken output


Download VS Code shows SSL error

VS Code Version: latest
OS Version: Windows 11
Browser: Firefox (117.0.1), Chrome (117.0.5938.92), Edge (117.0.2045.41)

Steps to Reproduce:

Go to https://code.visualstudio.com/Download
Click any download link (blue buttons), which leads to page https://code.visualstudio.com/docs/?dv=win64 and directs to https://az764295.vo.msecnd.net/stable/abd2f3db4bdb28f9e95536dfa84d8479f1eb312d/VSCodeSetup-x64-1.82.2.exe

Error Behavior:
Browser shows following SSL error:

Beim Verbinden mit az764295.vo.msecnd.net trat ein Fehler auf. SSL hat einen Eintrag erhalten, der die maximal erlaubte Länge überschritten hat.
Fehlercode: SSL_ERROR_RX_RECORD_TOO_LONG

Can you update to the latest Firefox?

Can you update to the latest Firefox?
https://support.mozilla.org/en-US/questions/1222739

Yes, the error occures also with Firefox latest version 118.0 - and as mentioned also with Chrome and Edge.

Can you show me a screenshot of the error in Chrome?

Thats the error in Chrome (latest version 117.0.5938.150):

This is a system misconfiguration. Please talk to to your system administrator, since something is messing with SSL certificates between your machine and our servers.


Implement topics

Probably the main title is also the topic for the detail pages.
That is, the training page probably has a topic of Training.

Fixed with bafdc5a846ea74ef5892905a0cc5783f060a701b


Migrate stCelo from react-celo to rainbowkit

We're ready to go - just awaiting for v2 contracts addresses now that it's been voted, it'll go live tonight CET (July 3rd)


On Adding OIDC Config , Helm chart errors out

how to reproduce -
datahub-frontend:
...
  extraEnvs:
    - name: AUTH_OIDC_ENABLED
      value: true
    - name: AUTH_OIDC_CLIENT_ID
      value: "<change-me>"
    - name: AUTH_OIDC_CLIENT_SECRET
      value: "<change-me>"
    - name: AUTH_OIDC_DISCOVERY_URI
      value: "<change-me>"
    - name: AUTH_OIDC_BASE_URL
      value: "<change-me>"

helm install datahub datahub/datahub --values ./charts/datahub/values.yaml -n datahub

Error: Deployment in version "v1" cannot be handled as a Deployment: v1.Deployment.Spec: v1.DeploymentSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.Containers: []v1.Container: v1.Container.Env: []v1.EnvVar: v1.EnvVar.Value: ReadString: expects " or n, but found t, error found in #10 byte of ...|,"value":true},{"nam|..., bigger context ...|geEvent_v1"},{"name":"AUTH_OIDC_ENABLED","value":true},{"name":"AUTH_OIDC_CLIENT_ID","value":"f8bcbc|...

i believe , toYaml loosing double quote to be the issue
https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/subcharts/datahub-frontend/templates/deployment.yaml#L141

Hi, same issue here!
Put true in quotes
  extraEnvs:     - name: AUTH_OIDC_ENABLED       value: "true"

thanks @gcaride , that worked.


构建优化问题

#1 当vue-cli项目足够大的时候，整个项目全量构建的速度比较慢，我想通过增量构建的方式来发布部署，有比较好的解决方案吗
<!--

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server, gitter or StackOverflow.


WIP:Read only mode for dcr admin

Comment out links to put/post actions
Turn refresh timers off
Add read only note

Only want this for bxc3
See: https://github.com/UNC-Libraries/Carolina-Digital-Repository/pull/1109


how to extract the feature of image after training

after training, I want to use the trained model to extract the feature of input image

Please refer to https://github.com/michuanhaohao/reid-strong-baseline/blob/3da7e6f03164a92e696cb6da059b1cd771b0346d/engine/inference.py#L15


🐞[bug]: Button height alignment issues

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The height of the buttons present on the service pages were not the same, giving it a a no uniform look and making it look aesthetically unpleasing. It should be fixed in such a manner that all the buttons are on the same height and in line with each other.
Expected behavior
All the three buttons should be inline with each other in order to make them look uniform.
Add ScreenShots

What browsers are you seeing the problem on?
Safari
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@Anjaliavv51 Please check this out


support for remote COG

I have a project with a remote COG which works in QGIS but in MM app shows an error not being able to display the layer:
https://app.merginmaps.com/projects/saber/cog test/settings


[msi] uninstaller processes termination

The uninstaller tries to terminate some processes:
https://github.com/microsoft/PowerToys/blob/013be4bbb8745dfc7cde51401e6a5b0b95deb521/installer/PowerToysSetupCustomActions/CustomAction.cpp#L607-L611
The code needs to be reviewed since terminating PowerToys.exe should be enough to cause the other processes to quit as well.
See https://github.com/microsoft/PowerToys/pull/10241#issuecomment-800921405 that describes an issues when PowerToys is running as admin and the settings app is open then the uninstaller is exeecuted.

You sure? Looking at #11691...


How to change the directory where checkpoints are loaded?

I am currently using the pre-trained checkpoint for testing purposes, and during this process, I notice the message "Initialize tensorboard (log_dir=output/base2new/train_base/caltech101/shots_16/CoCoOp/vit_b16_c4_ep10_batch1_ctxv1/seed1/tensorboard)" being printed. I am interested in modifying the checkpoint source in the file directory. Could you kindly guide me on which .py file I should be looking into to make this change?
Thank you very much for your time and assistance. I am looking forward to your guidance.

Hi @SHIBOYA,
Thank you for showing interest in MaPLe!
Regarding your query, you can change the path of the checkpoint source by modifying the MODEL_DIR variable in the testing shell script located here..
Once you have configured the MODEL_DIR, your code will search for the model weights in that directory and perform the evaluation accordingly.
I hope your query get resolved now. Please let us know in-case there is any additional question!
Thank you and kind regards!

I hope this email finds you well. First of all, thank you for your previous guidance on changing the MODEL_DIR to configure the checkpoint source in MaPLe. It was very helpful and much appreciated.
As I continue to work with MaPLe, I have come across another issue that I would like to bring to your attention. Specifically, I noticed a discrepancy in the dimensions of token_suffix and token_prefix between the Base-to-Novel and Cross-dataset Evaluation scenarios.
In the Base-to-Novel scenario, the dimensions of token_prefix and token_suffix are ([50, 1, 512]) and ([50, 74, 512]), whereas in the Cross-dataset Evaluation scenario, they are ([397, 1, 512]) and ([397, 74, 512]). I'm wondering if you could shed some light on the following questions: What is the reason behind this dimension mismatch between the two scenarios? Is this an expected behavior, or should I be concerned about a potential issue? Are there specific settings or parameters I should consider when switching between these two scenarios?
Your insights would be invaluable for my ongoing research. I look forward to hearing from you soon.

Hi @SHIBOYA,
Regarding your query, please note that the first dimension of the tensor (which is 50 in the first case and 397 in the second case) corresponds to the number of classes present in the dataset. 397 corresponds to the SUN397 dataset while 50 could be the dimensions for the case of caltech dataset (in base-to-novel).
So in summary, you do not need to be concerned about this.
Thank you!

Thank you for your prompt and clear response. Your explanation regarding the first dimension of the tensor corresponding to the number of classes in the dataset clarifies the discrepancy I observed. I appreciate the time you took to address my query.
Thank you once again for your help.


The schedule(like events and holidays) registered in February 2021 is not loaded at the first display.

The schedule(like events and holidays) registered in February 2021 is not loaded at the first display.
If you press "Next" and return with "Previous", the schedule registered in February will be displayed.
The days off are getting loaded without any issues.
Can you fix this bug at the earliest..

I'm sorry. I can't fix it because I don't know how to use Git
master branch
　　src / TimeLib.ts
　　　Between lines 51 and 52
I found that adding the following line to the problem disappeared.
current.setDate (1);

We're closing old issues so we can get back to actively maintaining the extension. Feel free to reopen if this is still an issue for you.


Use ON and OFF for CMake booleans

Description
CMake supports a number of strings for truthy and falsey values. ON/OFF and TRUE/FALSE are the most popular but 1/0 is also supported. This is mostly a style choice but I'm inclined to believe that ON/OFF is the most popular option and I'm generally in favor of style choices that better align with the community at large.
Prior to this PR SFML used a mixture of various options so this PR also ensures we're internally consistent.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

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

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
11899

Relevant Lines:
19920

💛  - Coveralls


Error: Private key must be greater than 0 and Error: Bad Request

Working on mainnet, getting these two issues.
Creating WIF From Node Module :
var wif = require('wif');
var privateKey = new Buffer('btc_private_key', 'hex');
var key = wif.encode(128, privateKey, true)
console.log("WIF key",key);

What i'm doing wrong?
bitcoinTransaction.getBalance(from, { network: "mainnet" }).then((balanceInBTC) => {
	return bitcoinTransaction.sendTransaction({
		from: from,
		to: to,
		privKeyWIF: key,
		btc: 0.0002,
		fee:"hour",
		network: "mainnet"
	});
}).then((res) => {
	console.log(res.body);
	console.log("---------------------------------------------------------");
	console.log("Hash: ",res.body.tx.hash);
});

Is your private key of the form that looks like this? cNZi8iySqBToXMpcsQaHKD5uv7HExBQJBSi4dTg3ZPaEzeNAzvbj

Now able to send value (But only whole amount present on address, not specific ),Also Not getting HASH of transaction on mainnet. Thanks.


removing oc as a binary dependency since we now use the library

We now use oc via a library and not a binary dependency, so it makes sense to remove this from our container.
Motivations:

Relates: openshift/release#36183

Had a comment that we should keep the version in preflight and in our E2E automation the pinned to the same version. Since we don't really need this anymore I feel it makes more sense to remove it from our container. And then in the E2E tests.
What doesn't change:
It makes sense to keep oc in our vagrant file and in our Dev docs, since it's a nice to have to help with developer testing on while developing.

            },
            {
                "name": "ScorecardOlmSuiteCheck",
                "elapsed_time": 2577,
                "description": "Operator-sdk scorecard OLM Test Suite Check"
            },
            {
                "name": "DeployableByOLM",
                "elapsed_time": 48677,
                "description": "Checking if the operator could be deployed by OLM"
            },
            {
                "name": "ValidateOperatorBundle",
                "elapsed_time": 48,
                "description": "Validating Bundle image that checks if it can validate the content and format of the operator bundle"
            }
        ],
        "failed": [],
        "errors": []
    }
}

check container
 podman run \
  -it \
  --rm \
  --security-opt=label=disable \
  --privileged \
  --env PFLT_LOGLEVEL=trace \
  --env PFLT_ARTIFACTS=/artifacts \
  --env PFLT_LOGFILE=/artifacts/preflight.log \
  -v ./artifacts:/artifacts \
  quay.io/acornett/preflight:remove-oc check container quay.io/acornett/container-passes:dnfupdate
.
.
.
{
    "image": "quay.io/acornett/container-passes:dnfupdate",
    "passed": true,
    "test_library": {
        "name": "github.com/redhat-openshift-ecosystem/openshift-preflight",
        "version": "0.0.0",
        "commit": "e9a3abc0917d0623ce698a4e911723d2f8c9caca"
    },
    "results": {
        "passed": [
            {
                "name": "HasLicense",
                "elapsed_time": 0,
                "description": "Checking if terms and conditions applicable to the software including open source licensing information are present. The license must be at /licenses"
            },
            {
                "name": "HasUniqueTag",
                "elapsed_time": 0,
                "description": "Checking if container has a tag other than 'latest', so that the image can be uniquely identified."
            },
            {
                "name": "LayerCountAcceptable",
                "elapsed_time": 0,
                "description": "Checking if container has less than 40 layers.  Too many layers within the container images can degrade container performance."
            },
            {
                "name": "HasNoProhibitedPackages",
                "elapsed_time": 135,
                "description": "Checks to ensure that the image in use does not include prohibited packages, such as Red Hat Enterprise Linux (RHEL) kernel packages."
            },
            {
                "name": "HasRequiredLabel",
                "elapsed_time": 0,
                "description": "Checking if the required labels (name, vendor, version, release, summary, description) are present in the container metadata."
            },
            {
                "name": "RunAsNonRoot",
                "elapsed_time": 1,
                "description": "Checking if container runs as the root user because a container that does not specify a non-root user will fail the automatic certification, and will be subject to a manual review before the container can be approved for publication"
            },
            {
                "name": "HasModifiedFiles",
                "elapsed_time": 4209,
                "description": "Checks that no files installed via RPM in the base Red Hat layer have been modified"
            },
            {
                "name": "BasedOnUbi",
                "elapsed_time": 1721,
                "description": "Checking if the container's base image is based upon the Red Hat Universal Base Image (UBI)"
            }
        ],
        "failed": [],
        "errors": []
    }
}

shows oc isn't in container
[vagrant@fedora36 preflight]$ podman run -it --entrypoint=/bin/bash  quay.io/acornett/preflight:remove-oc
[root@989a4c9d75d9 /]# oc
bash: oc: command not found

Signed-off-by: Adam D. Cornett<EMAIL_ADDRESS>

Coverage: 81.792%. Remained the same when pulling 5dbddcf7bc2097012ac685325470ba8051ea5bde on acornett21:remove_oc into e9a3abc0917d0623ce698a4e911723d2f8c9caca on redhat-openshift-ecosystem:main.

/test 4.8-e2e

/lgtm


Add "follows you" tag to accounts that follow you

Is your feature request related to a problem? Please describe.
Not really a problem but it would be much more convenient to see if an account follows you just by clicking on their profile instead of scrolling through your followers list.
Describe the solution you'd like
A little tag beside the handle would be nice, kind of like on Twitter.
Describe alternatives you've considered
N/A
Additional context
N/A

@corrupteddrive Can you assign it to me please?

I will do this task could you please assign me

I believe this exists.

This should exist, and we've also added more social proof info to bios. Feel free to open though if wrong.


how to ignore a page from grunt

Hi ,
I am concatenating my .js file using grunt. but wanted to be ignore ajax request which all are made for .jsp extension.

Thank you for submitting this ticket!
This issue tracker primarily serves as the tool to report and track bugs, defects, and development tasks.
For general question, code review request, build problem, or other related discussion, please post it to either:

the official PhantomJS users mailing-list
Stack Overflow (with phantomjs tag)

If you have not read it yet, please check also a few tips on Effective Q&A.


UX feedback

As discussed today, I'll create a comprehensive UX issue. I'll outline specific feedback I've experienced or heard from the team, and I'll tag in folks for greater details where necessary.
Icons:

Icons use different colors, weight, and style
Pin icon isn't intuitive, maybe a hand, person, or map?

Focus:

The loudspeaker to focus is initially confusing - don't see any changes or message locally
Focus attention is wonky when using diffs - a different editor opens, and notification is heavy

@tyriar I believe you experienced this - do you have further details on which notification felt heavy / why?

Following:

Following can be disorienting - could a user set how closely they want to track?
Scrolling can feel aggressive - can we minimize following scrolls when the content is already on the other person's screen?

Language support, intellisense:

Live Share doesn't appear to provide non-selection highlights - can this be added, as it's important when reading code?

Other UI:

Live Share cursor can be misaligned

cc @derekbekoe @jramsay @nandiniYeltiwar @setaskin @isidorn @fubaduba

I think I was talking about these ones:


Test over OTP 27 and rebar3 3.23

All relevant tests pass, but it seems CI settings are still waiting for rebar3 3.22 to be used.


Weird behavior, cannot visit a specific website

I can visit most website except for linkedin.
This is a weird issue for me and I haven't found any solution yet. Maybe it's a simple mistake or configuration error on my end but I really couldn't figure it out myself so I'm hoping that I can get some help here.
Steps to reproduce the problem:

I installed ubuntu on my windows laptop using virtualbox. To replicate the problem, the following steps are done on a newly installed ubuntu.

sudo apt install python3-pip
sudo pip3 install -U pip
sudo pip3 install mitmproxy

After I installed mitmproxy like that, I ran mitmproxy or mitmweb to start a simple proxy. I used firefox, configured its proxy setting to <IP_ADDRESS>:8080, and visited google. Then I had the page that says software issue is preventing me from visiting google. I then went to mitm.it to install the certificate. After that I could visit google, and in fact a lot of other sites like facebook, pinterest, twitter, dmv, etc, but I just cannot visit linkedin. As soon as I hit enter in the address bar the webpage kinda refreshed and stayed at previous page. I tried google linkedin and visit them from there but it's still not responding and giving me blank pages if opened in a new tab.
Any other comments? What have you tried so far?
Part of the output from mitmweb looks like this when I tried visit linkedin.com:
<IP_ADDRESS>:47522: clientconnect
<IP_ADDRESS>:47524: clientconnect
<IP_ADDRESS>:47526: clientconnect
<IP_ADDRESS>:47528: clientconnect
<IP_ADDRESS>:47530: clientconnect
<IP_ADDRESS>:47532: clientconnect
::ffff:<IP_ADDRESS>:47510: HTTP/2 connection terminated by client: error code: 0, last stream id: 0, additional data: None
<IP_ADDRESS>:47510: clientdisconnect
::ffff:<IP_ADDRESS>:47508: HTTP/2 connection terminated by client: error code: 0, last stream id: 0, additional data: None
<IP_ADDRESS>:47508: clientdisconnect
::ffff:<IP_ADDRESS>:47518: HTTP/2 connection terminated by client: error code: 0, last stream id: 0, additional data: None
<IP_ADDRESS>:47518: clientdisconnect
::ffff:<IP_ADDRESS>:47514: HTTP/2 connection terminated by client: error code: 0, last stream id: 0, additional data: None
<IP_ADDRESS>:47514: clientdisconnect
::ffff:<IP_ADDRESS>:47512: HTTP/2 connection terminated by client: error code: 0, last stream id: 0, additional data: None

I have tried curl as well:
Connecting to google is fine:
~$ curl -V
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Release-Date: 2018-01-24
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL
~$ curl -Ikv --proxy <IP_ADDRESS>:8080 https://www.google.com
* Rebuilt URL to: https://www.google.com/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8080 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to www.google.com:443
> CONNECT www.google.com:443 HTTP/1.1
> Host: www.google.com:443
> User-Agent: curl/7.58.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
HTTP/1.1 200 Connection established
<

* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* (304) (OUT), TLS handshake, Client hello (1):
* CONNECT phase completed!
* CONNECT phase completed!
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS change cipher, Client hello (1):
* (304) (OUT), TLS Unknown, Certificate Status (22):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using unknown / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=www.google.com
*  start date: Jul  7 22:33:38 2019 GMT
*  expire date: Jul  8 22:33:38 2021 GMT
*  issuer: CN=mitmproxy; O=mitmproxy
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (OUT), TLS Unknown, Unknown (23):
* Using Stream ID: 1 (easy handle 0x55ab8f543580)
* (304) (OUT), TLS Unknown, Unknown (23):
> HEAD / HTTP/2
> Host: www.google.com
> User-Agent: curl/7.58.0
> Accept: */*
>
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Newsession Ticket (4):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Newsession Ticket (4):
* (304) (IN), TLS Unknown, Unknown (23):
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (IN), TLS Unknown, Unknown (23):
* (304) (IN), TLS Unknown, Unknown (23):
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (IN), TLS Unknown, Unknown (23):
< HTTP/2 200
HTTP/2 200

But connecting to linkedin is not successful:
~$ curl -Ikv --proxy <IP_ADDRESS>:8080 https://www.linkedin.com
* Rebuilt URL to: https://www.linkedin.com/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8080 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to www.linkedin.com:443
> CONNECT www.linkedin.com:443 HTTP/1.1
> Host: www.linkedin.com:443
> User-Agent: curl/7.58.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
HTTP/1.1 200 Connection established
<

* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* (304) (OUT), TLS handshake, Client hello (1):
* CONNECT phase completed!
* CONNECT phase completed!
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS change cipher, Client hello (1):
* (304) (OUT), TLS Unknown, Certificate Status (22):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using unknown / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=www.linkedin.com
*  start date: Jul  7 22:35:31 2019 GMT
*  expire date: Jul  8 22:35:31 2021 GMT
*  issuer: CN=mitmproxy; O=mitmproxy
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (OUT), TLS Unknown, Unknown (23):
* Using Stream ID: 1 (easy handle 0x56270c7f0580)
* (304) (OUT), TLS Unknown, Unknown (23):
> HEAD / HTTP/2
> Host: www.linkedin.com
> User-Agent: curl/7.58.0
> Accept: */*
>
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Newsession Ticket (4):
* (304) (IN), TLS Unknown, Certificate Status (22):
* (304) (IN), TLS handshake, Newsession Ticket (4):
* (304) (IN), TLS Unknown, Unknown (23):
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (IN), TLS Unknown, Unknown (23):
* (304) (IN), TLS Unknown, Unknown (23):
* (304) (OUT), TLS Unknown, Unknown (23):
* (304) (IN), TLS Unknown, Unknown (23):
* Connection #0 to host <IP_ADDRESS> left intact
curl: (16) Error in the HTTP2 framing layer

For all the websites I've tried so far, linkedin is the only website that cannot be visited.
I've also tried install mitmproxy on my original windows system and it can visit linkedin just fine.
System information

~$ mitmproxy --version
Mitmproxy: 4.0.4
Python:    3.6.8
OpenSSL:   OpenSSL 1.1.1  11 Sep 2018
Platform:  Linux-4.18.0-25-generic-x86_64-with-Ubuntu-18.04-bionic

Firefox version: Firefox Quantum 67.0.4 64bit

had to disable http2 to get it to work.


Fixed incorrect path generation for sprites in Rails 4

Before:
if subdirectory.nil?
  bust_cache_path = generated_images_path
else
  bust_cache_path = generated_images_path + "/" + subdirectory
end

subdirectory will never be nil? there.
It will be . in case path is icons-sXXXXXXXXXX.png and bust_cache_path becomes app/assets/images/.
Moving the sprited images into a deeper subfolder works around the problem, subdirectory becomes folder_name instead of ..
Fixes #94, #162, #187, #188

I'm seeing signs that the cache busting no longer works.  It appears that the sprockets_entries for those keys don't get deleted, even though that's crazy because they're just two hashes.
      entry = generated_images_dir.join(dir).to_s
      sprockets_entries.delete(entry)

      stat = generated_images_dir.join(path).to_s
      sprockets_stats.delete(stat)

I'm using compass 1.0.3, compass-rails 3.0.2, Rails 4.0.13, sprockets 3.7.0, sprockets-rails 2.3.3. Any thoughts?


Suggested additions to Mabel's PR

Moving VIM to the end of the Dockerfile.  The stuff at the beginning is more required - trying to keep optional stuff towards the end.
Updates the build and join scripts for docker management to be consistent with VRX and other projects.
Updates the VCS repo list to assist in environment setup.
Removing https://github.com/Field-Robotics-Lab/glider_hybrid_whoi from VCS list.  There seems to be a problem with - see https://github.com/Field-Robotics-Lab/glider_hybrid_whoi/issues/57

Does this PR replace #114?
I didn't realize there's a .repos file. Is this somewhere in the wiki? I'm thinking it should go somewhere on the Installation page, along with my comments in #119.

The use of vcs and the repos file was in the wiki, but the location was not obvious.  I moved the content here: https://github.com/Field-Robotics-Lab/dave/wiki/Clone-Dave-Repositories

Does this PR replace #114?

Apologies - I lost track of #114.  I think there are still outstanding issues in #114.  Let's address this PR, then we can merge your changes in #118.  Finally I'll rebase #114 and make any adjustments.

This is currently on hold - I expect that @M1chaelM 's work on a general docker image - and my work on VCS support - will alleviate the need for this PR.

Compile error resolved and merged at glider_hybrid_whoi repo. It should be ok to include.

The glider_hybrid_whoi repo include massive static bathymetry tiles of the Buzzards Bay. Since we don't want static data to be included in the mainstream dave repo (https://github.com/Field-Robotics-Lab/dave/issues/107), excluding the glider repo seems reasonable. I will make and host a dataset somewhere and make tutorials accordingly.

Docker related changes in this PR have been addressed elsewhere and are no longer needed.

Agreed - closing this b/c we have address the VCS and docker issues elsewhere.


ddev get should allow specifying optional settings

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Some ddev get add-ons can use minor configuration overrides. For example, the version of a redis image might want to be overridden.
Describe your solution
Use a flag, --environment?
Describe alternatives
People currently have to manually edit docker-compose.*.yaml and then remove the #ddev-generated from a file that is part of an add-on.
Additional context
No response

@gilzow This was

https://github.com/drud/ddev-platformsh/issues/28
It doesn't appear there's a way to do this, because the project ID is not available in this file at this time.

ddev pull takes environment variables on the command line. That might work here.

Some ideas:

a .ddev/.env file is already supported for docker-compose.*.yaml, it would probably work fine already.
docker-compose.*-extra.yaml already works.
config.*-extra.yaml already works.;
.env file could perhaps be applied to config.*.yaml as well

An extended flag to ddev get command would work. Something like this
$ ddev get ddev/ddev-redis --version $RELEASE_VERSION

It would be bound to the repo version, not the actual docker image in the plugin (if the plugin has one)

Thanks for the thinking @seebeen - but since ddev get has no idea whatever what things might want to be replaced/configured, how is that going to work out?
And what happens the next time they update the add-on and forget the argument?

I opened a draft PR:

#6406

Use a flag, --environment?

I added this flag to ddev get. It takes into account the .env.* files inside the `.ddev' folder.

a .ddev/.env file is already supported for docker-compose.*.yaml, it would probably work fine already.

I chose not to write to .ddev/.env because it may contain sensitive information and people usually don't want to commit that file.
Instead, I used a file name according to the add-on, such as .ddev/.env.<addon-name>, e.g. .ddev/.env.redis.
All .env.* files that end in .example will be ignored.

And what happens the next time they update the add-on and forget the argument?

This .ddev/.env.redis is automatically expanded when running docker-compose config, this allows you to run ddev get without arguments that are already saved and taken into account.
All environment variables in add-ons (which can be overridden) should have default values, for example ${REDIS_VERSION:-6-bullseye}, not ${REDIS_VERSION} - this will allow the add-on to work with older DDEV versions, and .ddev/.env.redis is completely optional when env has a default value.

I chose not to write to .ddev/.env because it may contain sensitive information and people usually don't want to commit that file.
Instead, I used a file name according to the add-on, such as .ddev/.env.<addon-name>, e.g. .ddev/.env.redis.

The point of .env files is that they're for that specific environment - I probably wouldn't want to commit .env.<addon-name> files any more than I'd want to commit .env, but that might just be me.

Thanks for the input @GuySartorelli.

I probably wouldn't want to commit .env.<addon-name> files any more than I'd want to commit .env

.env.* is much easier for users to understand and use instead of using the yaml file syntax, and it is natural for docker-compose config to accept it with the --env-file flag.
As an alternative, I can only see doing similar to web_environment, like db_environment or redis_environment, or converting everything to:
environment:
  - service: web
    variables:
      - ENV1=foo
      - ENV2=bar
  - service: db
    variables:
      - ENV1=foo
      - ENV2=bar
  - service: redis
    variables:
      - ENV1=foo
      - ENV2=bar

But users can already define the environment in their respective docker-compose.*.yaml files, so I think this will only add more confusion, and .env.* seems like a good solution for me.
The other way is to read the individual docker-compose.*.yaml files and parse them, but this is an unknown area because after everything is merged into one file, the structure may change, and it's similar to the chicken-and-egg problem where I need to read something before adding env variables to it, but it may already be overridden in another *override.yaml file. I thought about it a lot and gave it up for now.
If only we had a docker-compose SDK for Go, it would be much easier.


tf.nn.embedding_lookup works fine in CPU mode, but lacks constraint checking in GPU mode

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
binary
TensorFlow version
tf2.14.0
Custom code
Yes
OS platform and distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
11.8
GPU model and memory
No response
Current behavior?
When calling tf.nn.embedding_lookup with an input that does not meet the constraints, the input error will be correctly determined in CPU mode, but the calculation will be completed normally in GPU mode and a result of all 0s will be obtained.
import os

os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'

os.environ['CUDA_VISIBLE_DEVICES'] = '0'

os.environ['TF_FORCE_GPU_ALLOW_GROWTH'] = 'true'

import tensorflow as tf
import random
import numpy as np

print(f"TensorFlow git version is {tf.version.GIT_VERSION}")
print(f"TensorFlow version is {tf.version.VERSION}")

result={}
random.seed(4399)
np.random.seed(4399)
tf.random.set_seed(4399)
try:
    with tf.device('/CPU:0'):
        unamed_0 = tf.random.uniform([4, 3], dtype=tf.float32)
        unamed_1 = tf.random.uniform([3], minval=0, maxval=256, dtype=tf.int32)
        result["CPU_res"] = tf.nn.embedding_lookup(unamed_0, unamed_1, ) # this should results into error, and it does so
except Exception as e:
    result["CPU_err"] = str(e)
print(f"CPU input 1 is {unamed_0}")
print(f"CPU inptu 2 is {unamed_1}")
print(f"CPU result is {result}")

result = {}
random.seed(4399)
np.random.seed(4399)
tf.random.set_seed(4399)
try:
    with tf.device('/GPU:0'):
        unamed_0 = tf.random.uniform([4, 3], dtype=tf.float32)
        unamed_1 = tf.random.uniform([3], minval=0, maxval=256, dtype=tf.int32)
        result["GPU_res"] = tf.nn.embedding_lookup(unamed_0, unamed_1, ) # this should results into error, but it does not
except Exception as e:
    result["GPU_err"] = str(e)
print(f"GPU input 1 is {unamed_0}")
print(f"GPU inptu 2 is {unamed_1}")
print(f"GPU result is {result}")

I have also reproduced this bug in colab.
Standalone code to reproduce the issue
https://colab.research.google.com/drive/1YqG7jHpMCLjrE8VqQlBSZtz_lRNgT4rU?usp=sharing

Relevant log output
TensorFlow git version is v2.14.0-rc1-21-g4dacf3f368e
TensorFlow version is 2.14.0
CPU input 1 is [[0.35562682 0.13057125 0.9950352 ]
 [0.27489936 0.9225844  0.87167037]
 [0.44606853 0.45545673 0.3351872 ]
 [0.6091548  0.7782723  0.10762429]]
CPU inptu 2 is [144 161  30]
CPU result is {'CPU_err': '{{function_node __wrapped__GatherV2_device_/job:localhost/replica:0/task:0/device:CPU:0}} indices[0] = 144 is not in [0, 4) [Op:GatherV2] name: '}
GPU input 1 is [[0.35562682 0.13057125 0.9950352 ]
 [0.27489936 0.9225844  0.87167037]
 [0.44606853 0.45545673 0.3351872 ]
 [0.6091548  0.7782723  0.10762429]]
GPU inptu 2 is [144 161  30]
GPU result is {'GPU_res': <tf.Tensor: shape=(3, 3), dtype=float32, numpy=
array([[0., 0., 0.],
       [0., 0., 0.],
       [0., 0., 0.]], dtype=float32)>}

Hi @EgodPrime ,
This is due to the tf.gather Op, which is called internally by embedding_lookup. tf.gather Op never validate indices on GPU and on CPU indices always be validated.Hence on GPU there is no exception as raised by CPU. This is known issue and also documented in the tf.gather doc here.
Please also refer Developer comment on same.

Hi @EgodPrime ,
This is due to the tf.gather Op, which is called internally by embedding_lookup. tf.gather Op never validate indices on GPU and on CPU indices always be validated.Hence on GPU there is no exception as raised by CPU. This is known issue and also documented in the tf.gather doc here.
Please refer to the argument description of validate_indices under args section of tf.gather which is below.

Caution: On CPU, if an out of bound index is found, an error is raised. On GPU, if an out of bound index is found, a 0 is stored in the corresponding output value.

Please also refer Developer comment on same.

Thanks for replying. I totally understand the consideration that you try telling, but I think it would be better if you can directly add some argument description about the constraints to the tf.nn.embedding_lookup :)

This is true for most ops that use indicies - it's too expensive to do constraint checking over the input on GPU, so we always just ignore bad indices.  It's still an invalid model that will result in undefined behavior.

@EgodPrime,
The related PR which was raised for adding the caution not for the current behaviour has been merged and also please take a look at the above comment from the Developer for the same.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/embedding_ops.py#L310
https://github.com/tensorflow/tensorflow/pull/62734
Thank you!


VTOL: fix front transition rate publication (enable FW attitude contr…

Fixes https://github.com/PX4/Firmware/issues/13030
With the changes in this PR the FW attitude controller is publishing rate sp also during first second of transition:

Can you get commander to update immediately?
https://github.com/PX4/Firmware/blob/190c817a9e2e37c99111e249b5b23fd076ddfed3/src/modules/commander/Commander.cpp#L1601-L1643
Setting status_changed = true will cause the vehicle_status to publish immediately, otherwise it publishes at 1 Hz.
https://github.com/PX4/Firmware/blob/190c817a9e2e37c99111e249b5b23fd076ddfed3/src/modules/commander/Commander.cpp#L2328-L2374

thanks for the tip @dagar . I've noticed that if the vehicle_status_poll() is done before the vehicle_control_mode_poll() it works (such that during the vehicle_control_mode_poll() it already knows if in transition mode).
Do you see any problems with that change?

thanks for the tip @dagar . I've noticed that if the vehicle_status_poll() is done before the vehicle_control_mode_poll() it works (such that during the vehicle_control_mode_poll() it already knows if in transition mode).
Do you see any problems with that change?

I think that's much better. I'd either add a comment to make it clear the ordering is important or even consider merging them to prevent the possibility of screwing it up.

thanks for the tip @dagar . I've noticed that if the vehicle_status_poll() is done before the vehicle_control_mode_poll() it works (such that during the vehicle_control_mode_poll() it already knows if in transition mode).
Do you see any problems with that change?

I think that's much better. I'd either add a comment to make it clear the ordering is important or even consider merging them to prevent the possibility of screwing it up.

Added a comment.


Include original class in schema for z.instanceof()

It'd be great if the original class (e.g. Uint8Array for z.instanceof(Uint8Array)) could be included in the schema to allow for more flexibility.

Hi, can I work on this

What do you mean by "include the original class"? Could you provide some pseudo code that shows how you would like to use this?

@JacobWeisenburger sorry for the late response but i meant that the original class (in this example Uint8Array) should be somewhere included in the object of the schema (so if you log z.instanceof(Uint8Array) to console you can actually know that it should be the specified class).
This would allow other libraries to further analyze the schemas. No longer sure whether this is even needed.
As I personally don't have a use case for this any longer I'm closing this as completed, but feel free to re-open it if this should become a feature.


Add support for /docker-entrypoint-initdb.d/

It would be great if the image could support initializing the database upon startup via a /docker-entrypoint-initdb.d/ folder, like done in
https://github.com/docker-library/mysql/blob/master/8.0/docker-entrypoint.sh
If the db is not yet initialized (/var/lib/mysq is empty), all *.sql scripts in /docker-entrypoint-initdb.d/ are executed in order.

Added a script cmd initdb (also as a make target) to source the scripts from /etc/mysql/initdb.d.
Depending on the sql or shell scripts in there, we can initialize as well as reset the database to a preset state.

Closing due to no activity since.


iou metrics

Hi,
Where can I change the iou for the metrics?

Hi. At the moment, during the training/validation it cannot be changed as it used pycocotools and it is quite difficult to do so.


Use logging module instead of print for logging messages

These changes implement the logging module instead of prints to log messages, so that applications using the library can filter / choose the messages that are printed to the console.

Hi, I appreciate your help. It's approved. Please merge it.


🐛 Bug Report: Configuration Help/Examples

Reproduction steps
I have been able to setup the pocketid app and configure users and add passkeys as well as log in.  I'm have an issue setting up an initial client and looking for more configuration help and examples.  I'm using pgadmin as my first configuration client.  One reason is that it allows for configuring multiple OIDC providers.  I currently have pgamdin successfully configured for Authentik.
Expected behavior
I'm able to configure pgadmin and other clients to use pocketid
Actual Behavior
I'm not able to configure pgadmin as a client.
Current pocketid configuration for pgadmin client:
callback URL : https://pgadmin.domain.org/oauth2/authorize
pgadmin config:
'OAUTH2_NAME': 'PocketID',
'OAUTH2_DISPLAY_NAME': 'PocketID',
'OAUTH2_CLIENT_ID': ',
'OAUTH2_CLIENT_SECRET': '',
'OAUTH2_TOKEN_URL': 'https://pocketid.domain.org/api/oidc/token/',
'OAUTH2_AUTHORIZATION_URL': 'https://pocketid.domain.org/authorize/',
'OAUTH2_SERVER_METADATA_URL': 'https://pocketid.domain.org/.well-known/openid-configuration',
'OAUTH2_PKCE': False,
'OAUTH2_API_BASE_URL': 'https://pocketid.domain.org/',
'OAUTH2_USERINFO_ENDPOINT': 'https://pocketid.domain.org/api/oidc/userinfo/',
'OAUTH2_SCOPE': 'openid email profile',
'OAUTH2_BUTTON_COLOR': '#0000ff',
'OAUTH2_USERNAME_CLAIM': 'preferred_username',
'OAUTH2_AUTO_CREATE_USER': True,
#'OAUTH2_ADDITIONAL_CLAIMS': {'email'},
'OAUTH2_ADDITIONAL_CLAIMS': None,
#'OAUTH2_LOGOUT_URL': 'https://auth.domain.org/application/o/pgadmin/end-session/',
'OAUTH2_SSL_CERT_VERIFICATION': True
After I successfully authenticate with pocketid, the following error is returned in the browser:
{"success":0,"errormsg":"Invalid JSON Web Key Set","info":"","result":null,"data":null}
I'm not convinced I'm setting the correct callback url.  I'm using the same url for what authentik calls the redirect URI.
There is no setting in pgadmin for the Certificate URL and I'm assuming OAUTH2_SERVER_METADATA_URL is the same as OIDC Discovery URL.
Any configuration help would be appreciated.

Pgadmin uses the library "autlib" and I have found a issue that might be related (https://github.com/lepture/authlib/issues/462). Which version of pgadmin are you using?

I'm running docker image dpage/pgadmin4, specifically:
Version 8.10
Application Mode Server
Commit: ab25238f17bd52aa361db487a94435e97beb62c6 2024-07-29
Browser Chrome <IP_ADDRESS>
Operating System Alpine Linux v3.20, Linux-6.1.21-v8+-aarch64-with
8.10 appears to be the latest version

Ok thanks, then this is probably not the issue. I'm looking into it further tomorrow.

Does pgadmin log anything when you do this request in the container logs?

I've found the issue, I'll keep you up to date.

The issue should be resolved now. I’ll release the fix ASAP after completing some additional testing. However, if you’d like to try it out immediately, you can use the stonith404/pocket-id:development image, where the update is already available.

This should be fixed in the latest version.

Thanks, the development image seems to work for pgadmin.  I've tested with 4 other clients and can't get them to work. Should I create a separate issue for each one?


Vim network session microsoft sysmon

Required items, please complete
Change(s):
Added vim parser for Sysmon Event ID 3 (both Event and WindowsEvent)

Hi @goosvorbook please check the comments and make required changes, thanks

Hello @goosvorbook any updates on the above

Hello @goosvorbook please provide your update

For now, consider this PR as a draft.

ok @goosvorbook please mark it as draft

Hi @goosvorbook, We wanted to check on the status of PR https://github.com/Azure/Azure-Sentinel/pull/7136  . PR is pending for more than expected days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation

Since we have not received a response in the last 7 days, we are closing your PR #7136 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.
If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation


Add badges

This helps promotion/adoption of cargo-fuzz. Also, I wanted to ask a few quick questions but couldn't discover a chat room very quickly (e.g., Google search, README). I'm sure you are all on IRC ... But I hope you agree the Gitter channel won't hurt: non-maintainers can answer each other's questions that way as well.

Thanks for the pull request! I don't think the badges are super necessary, in particular the API docs and gitter links (which are both broken) and the license is already mentioned in the README. But I don't feeel particularly strongly about this so someone else in this GitHub org can decide

I find it wasteful how this contributions was handled and the motivation is unclear (‘don’t think they are super necessary’). But I’m sorry to say, not going to spend more energy on it.


Use Winit as windowing backend for three-d

well, I didn't add the code for webgl1 or such details. but just wanted to show a basic working sample with winit.
basically, just remove glutin_window and canvas modules. and instead use a (almost copy of glutin_window mod) winit_window module.
I need to look through canvas and see if web specific stuff needs to be merged into winit_window.

Looks really good 🎉
three-d actually doesn't support webgl1 (all major browsers support webgl2) so don't worry about that 🙂

I need to look through canvas and see if web specific stuff needs to be merged into winit_window.

I think the only thing is that now you create the canvas in Rust instead of getting the canvas from the document body. Is there a reason for that? This makes it less flexible since you cannot specify a specific canvas (you could before using the set_canvas method) and you cannot specify the CSS for the canvas (as was done in index.html previously). Instead of a set_canvas method, maybe an optional canvas could be specified in the window settings?

Is there a reason for that? This makes it less flexible since you cannot specify a specific canvas (you could before using the set_canvas method)
no reason. i simply was not aware that manually specifying canvas had any advantage :)
winit already has  https://docs.rs/winit/latest/wasm32-unknown-unknown/winit/window/struct.WindowBuilder.html#method.with_canvas .

as for CSS, i thought we would with the eframe's like index.html which places a style block inside head to center canvas and use a background color based on user preference of light / dark mode.
although i am not sure how to enable this.

ask users for a &str and use document.get_element_by_id(&str) ?
just check for document.get_element_by_id("three_d_canvas") and if it exists use that. it means, user needs set that id attribute on their canvas.
ask user to provide a HtmlCanvasElement, which means they will need to use web_sys too.

I went with option 2 now. before this, three-d just searched for canvas elements in DOM and used the first found child. now, three-d will search for canvas element with id three_d_canvas_id and use that.
if found
use that canvas element for winit window
else
let winit create a new canvas for the window and add that canvas to DOM.
The code could be cleaned up more to cleanly separate wasm32 and native stuff eventually as it evolves in future.

It should be option 3 just as it is today 🙂 But you could add a Option< HtmlCanvasElement> to WindowSettings instead of having a set_canvas method, that would be cleaner I think. If nothing is specified, it should just use the first canvas it can find as today. I see no point in changing that logic. However, you're welcome to add that if it can't find any canvas, then a canvas is added.

ah, its the merge conflict thing. let me quickly fix that and change the canvas behavior to option 3.

should be okay now. added an optional canvas setting for users to explicitly provide one. if they don't, we use the first canvas element in DOM.

Super nice, thanks for the contribution 👍💪🙏 I especially like all of my hacky canvas.rs file just disappeared 😄


Update README to use the name "WASI SDK" consistently

Closes #383

Perhaps also?
-Use a toolchain file to setup the *wasi-sdk* platform.
+Use a toolchain file to setup the *WASI SDK* platform.

Perhaps also?
-Use a toolchain file to setup the *wasi-sdk* platform.
+Use a toolchain file to setup the *WASI SDK* platform.

The reason I didn't update that is the next line of text says, "or the wasi-sdk-thread platform", suggesting it's being used as a technical term in that situation rather than a name.

@sunfishcode the failures look unrelated to the PR.


Update metaphysics schema

Greetings human :robot: this PR was automatically created as part of metaphysics' deploy process.

on no peril is not working again 😭


update README.md and package.json

Updating the README file with project data and starting a table of contents.

ok. Update.


Allowing custom values for vertical-align

Addressing issue #60
@renatoi, please review

CLA is valid!

fyi @hankhsiao

Coverage remained the same at 100.0% when pulling 79e5ae763f3e870259368aa0ee93c6ce82493b56 on Va-custom into de080d29d466e61eefb456d3d6b92e8a971a00c1 on master.

Coverage remained the same at 100.0% when pulling 79e5ae763f3e870259368aa0ee93c6ce82493b56 on Va-custom into de080d29d466e61eefb456d3d6b92e8a971a00c1 on master.

LGTM

Thanks


Page Should (Not) Contain Button keywords don't work with buttons created like <input type="button">

Originally submitted to Google Code by @pekkaklarck on 14 Jan 2010

These keywords work only with buttons created using <button> tags. A
workaround is using Page Should (Not) Contain Element.
See also  issue 6  about similar (opposite) problem with Click Button and
 issue 30  that requested these keywords to be added.

Originally submitted to Google Code by @yanne on 9 Feb 2010

Fixed in 310


[e2e]: container workflow_dispatch branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8422583454
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.workflow_dispatch.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.workflow_dispatch.branch1.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Mar 25 15:30:24 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/8430171081
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.workflow_dispatch.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.workflow_dispatch.branch1.default.slsa3.yml
Trigger: workflow_dispatch
Branch: branch1
Date: Tue Mar 26 03:05:17 UTC 2024
Tests are passing now. Closing this issue.


KHR_lights_punctual management in importer

Basic implementation is done in own branch for now

Seems it has been merge into master ...


Implicit dependency on vue-template-compiler

Version
v5.3.0
Reproduction link
https://github.com/nuxt/now-builder/issues/42
Steps to reproduce

What is expected ?

What is actually happening?

Additional comments?
This module has an implicit dependency on vue-template-compiler here. All direct dependencies like this should be specified in dependencies section of package.json.  When using nuxt-start (a serverless) build of nuxt, this dependency is not available.
It is also better to only require build related deps on build:before nuxt hook to prevent additional overhead when running in production mode.

This bug report is available on Nuxt community (#c237)

This code is running when generating extra locale routes.
Nuxt generates routes in this order:

generate default routes
call build:extendRoutes hook
process routes returned from options.router.extendRoutes function (if defined)

This module uses ModuleContainer.extendRoutes(fn) to hook into processing of options.router.extendRoutes.
So even when no actually using a hook (because build:extendRoutes would happen at wrong time for this module anyway), I think it's OK to keep using ModuleContainer.extendRoutes(fn) as then the function shouldn't be called on start of built app, right?

@pi0 you think #298 is a good solution to both problems?

@rchl yes, that totally makes sense. Thanks for the PR.

@pi0 @paulgv I have just noticed a problem with this change.
With<EMAIL_ADDRESS>version at least, I see this error when trying to build:
Vue packages version mismatch:

-<EMAIL_ADDRESS>(/Users/rchlodnicki/workspace/tidal-com/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/Users/rchlodnicki/workspace/tidal-com/node_modules/nuxt-i18n/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

  Error:

  Vue packages version mismatch:

  -<EMAIL_ADDRESS>(node_modules/vue/dist/vue.runtime.common.js)
  -<EMAIL_ADDRESS>(node_modules/nuxt-i18n/node_modules/vue-template-compiler/package.json)

  This may cause things to work incorrectly. Make sure to use the same version for both.
  If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
  If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

  at Object.<anonymous> (node_modules/nuxt-i18n/node_modules/vue-template-compiler/index.js:10:9)
  at Generator.next (<anonymous>)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)

   ╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
   │                                                                                │
   │   ✖ Nuxt Fatal Error                                                                                │
   │                                                                                │
   │   Error:                                                                                │
   │                                                                                │
   │   Vue packages version mismatch:                                                                                │
   │                                                                                │
   │   -<EMAIL_ADDRESS>(/Users/rchlodnicki/workspace/tidal-com/node_modules/vue/dist/vue.runtime.common.js)                                                 │
   │   -<EMAIL_ADDRESS>(/Users/rchlodnicki/workspace/tidal-com/node_modules/nuxt-i18n/node_modules/vue-template-compiler/package.json)   │
   │                                                                                │
   │   This may cause things to work incorrectly. Make sure to use the same version for both.                                                           │
   │   If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.                                                                         │
   │   If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.                    │
   │                                                                                │
   │                                                                                │
   ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

It seems like versions of vue and vue-template-compiler must match exactly. I think this line is responsible for that:
https://github.com/vuejs/vue/blob/1137e415c9e8701d1b0a25e5812f8c4dffeeeaaa/packages/vue-template-compiler/package.json#L29
Given that vue comes from nuxt, I don't know how to ensure that those are always synchronized. Any idea?

@rchl we can either come back to implicit dependency (and only require for build time) or use this.nuxt.resolver.requireModule to require vue-template-compiler.

@pi0 thanks. Created #305. Please double check I did the right thing.


Fixes parameters not being added to querystring

When specifying parameters like page, pageSize and depth they were not being added to the querystring.
This PR fixes that.
I've also update the parameter types since they were specified as string even tho they are numbers. Culture is also marked as optional since it's not a required argument
fixes #12

Looks good to me
:shipit:


Add benchmark stresscli scripts

Description
Add stresscli benchmark tool for OPEA workloads and components

Profile based multi-run stress tool
Locust based benchmark script for chatQnA and TGI
HW/SW Spec and Metrics collection
Stress report generation

Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
None.
Tests
None.

@lvliang-intel @chensuyue
All Checks have passed, please help to arrange review.


config options chosen_file_path and events_file_path required on Windows

If you don't specify the configuration options chosen_file_path and events_file_path, yazi will fail to launch successfully because Windows doesn't normally have a /tmp directory, so Yazi can't find /tmp/yazi_filechosen. or redirect to /tmp/yazi.nvim.events.
After adding the following to my config:
            opts = {
                chosen_file_path = vim.fn.tempname(),
                events_file_path = vim.fn.tempname(),
            },

The extension seems to work correctly.

Hi! I think you might be running an old version of yazi.nvim. Is it possible for you to update to the most recent version?
Using /tmp/ as the default directory was removed back in May in this commit https://github.com/mikavilpas/yazi.nvim/commit/95eb780cab5f8535a217a9d9dc611f17226eab8d
Now vim.fn.tempname() is used as the default. Also note that events_file_path no longer exists because ya (the yazi command line utility that's bundled with yazi) is used to read events now.

Lazy was telling me I had the latest, but that was for the master branch. I switched to main and that seems to have been it.


Add support for Polish (pl)

Hi, I've added support for Polish, along with couple basic tests.
Would appreciate review 🙂

Looks good; thanks for contributing and for including tests. 👍🏼
I'll add Polish to the README.md and push a new release to PyPI


MTAR Build issues : Unable to build CAP Java Spring V4 Project

Do you want to request a feature or report a bug?
Report Bug

Please search existing issues to avoid creating duplicates. https://github.com/SAP/cloud-mta-build-tool/releases.
Also please test using the latest version build to make sure your issue has not already been fixed:

Please provide the following info:

MBT Version:
OS Version:
If possible, provide a link to the project.
https://github.wdf.sap.corp/itscb/VMSCAP/tree/master/vms
Steps to Reproduce:
I followed https://sap.github.io/cloud-mta-build-tool/download/ & install all pre-requisites
I tried to Build MTAR using below commands, all commands are giving same error

C:\Users\i311690\git\VMSCAPGithub\vms>

mbt build
mbt build -p=cf
3.mbt build -p=cf -t .

ERROR could not build the "vms-st-db" module: could not execute the "npm install --production" command: exec: "npm": executable file not found in %PATH%
make: *** [vms-st-db] Error 1
Error: could not build the MTA project: could not execute the "make -f Makefile_20191210153839.mta p=cf mtar= strict=true mode=" command: exit status 2
i think issue is with vms-st-db module in yaml . Please refer my yaml file & suggest if something is incorrect
https://github.wdf.sap.corp/itscb/VMSCAP/blob/master/vms/mta.yaml
Thanks,
Showkath.

It seems that you are missing npm (which is pre-requisite for building node modules) on your machine or it isn't configured properly, try to run npm install under the module path. or npm -v.

npm -v
Hi ,

i ran npm -v & version is 6.13.1

I think you have an issue with your environment as I was able to build your project successfully. just added .npmrc under the db module with sap registry: @sap:registry=https://npm.sap.com/
[INFO] Replacing main artifact with repackaged archive
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:31 min
[INFO] Finished at: 2019-12-11T13:42:16+02:00
[INFO] ------------------------------------------------------------------------
.[2019-12-11 13:42:16]  INFO the build results of the "vms-st-srv" module will be packed and saved in the "/Users/i056926/Projects/VMSCAP/vms/.vms_mta_build_tmp/vms-st-srv" folder
[2019-12-11 13:42:16]  INFO finished building the "vms-st-srv" module
[2019-12-11 13:42:16]  INFO generating the metadata...
[2019-12-11 13:42:16]  INFO generating the MTA archive...
[2019-12-11 13:42:18]  INFO the MTA archive generated at: /Users/i056926/Projects/VMSCAP/vms/mta_archives/com.sap.cap.vms.srv_0.0.1.mtar

Hi,
I am closing the issue as not active for a few weeks.
Please re-open if the issue is still reproducible.
Regards
Natalia


#27 Add --dry-run flag argument on clean unused-translations command

Codecov Report

Merging #30 (8b0c863) into main (1a61a07) will increase coverage by 1.61%.
The diff coverage is 61.53%.

@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   83.79%   85.40%   +1.61%
==========================================
  Files          15       16       +1
  Lines         364      370       +6
==========================================
+ Hits          305      316      +11
+ Misses         59       54       -5

Files
Coverage Δ

lib/src/exceptions/exceptions.dart
33.33% <33.33%> (ø)

lib/src/babel.dart
41.66% <70.00%> (+12.68%)
:arrow_up:


This template is compatilble with jquery 3?

Currently it resolves to "v2.2.4" so it's not compatible.

Any chance of an upgrade coming?

Hi there @GWSB ,
We will take it into consideration, thank you !

@hugogoncalves, please close the ticket If you don't have any further questions.


Add feature to expose pricing

In Google Cloud each vCPU and each GB of RAM have a fixed price. Kube Eagle can easily aggregate the allocatable and in use CPU & RAM and add a pricing metric for that.
This way one could get an overview how expensive a namespace or deployment is and what saving potential it has (usage compared to allocatable resources).
Challenges:

How to define the CPU / RAM pricing? Each zone, provider and machine type (e. g. spot instances, on demand, preemptible, commitment) may have a slightly different CPU & RAM pricing

Hi @weeco, we've recently done this across multiple cloud providers in the Kubecost project (https://github.com/kubecost/cost-model). It could be really cool to collaborate on this if you're interested! Let me know if you want to talk some about it --<EMAIL_ADDRESS>

This is really nice to have a combination of this 2 into one.  Looking forward to this.
Thx!


Calender Not showing

Hi,
nothing shows when adding data-date-slider-picker directive, just this ### [[object HTMLDivElement]]
This my code :
 <data-date-slider-picker total-days="90" date-select-var="Sat Jan 23 2016">
        </data-date-slider-picker>

One issue that I can instantly notice is the date-select-var is set to a value instead of a variable in a controller.  Have a look at the documentation and also on the following examples page:
https://github.com/Pranay92/ionic-date-slider/blob/master/demo/blank/www/templates/tab-calendar.html

@Pranay92 , Still the same problem even with a variable, the blank project contains directive.js which i see the implementation of data-date-slider-picker, do I have to include that code ? could give me a brief guide on how to set use the ionic-date-slider ?

@Pranay92 it's seems your plugin don't work on device. I tested the blank app with android it gives [[object HTMLDivElement]] tho it works fine in browser..


[AUTOTVM] acceptance probability definition

While looking at the simulated annealing code for AutoTVM, I noticed that we do a minimum with 1 before exponentiating the scaled difference: https://github.com/dmlc/tvm/blob/30242d5c46059939e0327e48fd3a3c6377a637b6/python/tvm/autotvm/tuner/sa_model_optimizer.py#L90. My understanding is that this will cause a "probability" bound of (0, 2.71828] when the following call to np.random.random will only generate values in (0, 1).
I think the minimum has no effect and can just be removed, as np.random.random will only generate values in (0, 1) anyway. Similarly, if we switch the order to be min(exp()), the additional operation will not do anything.
CC @merrymercy

It is used to prevent overflow in np.exp.
You can try
np.exp(1/(1e-5))

Then you will see the warning.


How to create a workflow that opens an application with a parameter?

Hello, thanks for this lib. I already use it for searching and opening bookmarks and it works great.
I would like to create a workflow, that opens a directory with intellij or vscode.
e.g. idea /path/to/repository or IntelliJ IDEA Ultimate.app /path/to/repository
The Modifier-class seems to change arguments, but I don't see how I can specifly which application/command to execute. When I look at other workflows, it looks like I have to change the info.plist.
Could you help me out? Do you have an example?
thanks in advance and best regards
Joscha

Hi @sejoharp, a script filter workflow might not be the best option for this 🤔. I'm guessing you've tried all the built-in Actions provided by Alfred for workflows?

Hi @rossmacarthur, Thanks for your answer. I did not try to create a simple workflow and looked at the plist file.
I found this example: https://github.com/jason0x43/alfred-toggl
I‘ll try to build my use case this way.