GitHub integration branch functionality broken when using remotes with default auth.email.template.*.content_path values

Describe the bug
When attempting to use a persistent branch with remotes values for auth.email.template.*.content_path in config.toml, the GitHub integration breaks on PRs with a Invalid config for (name): open (path): no such file or directory error.
To Reproduce

Create a monorepo with a Supabase config.toml in one package
In the config.toml, set values for auth.email.template.*.content_path. For example:[auth.email.template.confirmation]
subject = "Confirm Your Signup"
content_path = "./supabase/templates/confirmation.html"

Set up a persistent branch via CLI
In the config.toml, add a remotes entry. For example:[remotes.staging]
project_id = "some-project-id-here"

Create a GitHub PR using the persistent branch
GitHub Supabase integration fails with an error around the auth.email.template.*.content_path setting

Expected behavior

GitHub Supabase integration should work as expected, either by using the given file (which exists) or ignoring it

Screenshots
If applicable, add screenshots to help explain your problem.
System information

Rerun the failing command with --create-ticket flag: n/a
Versions of services:        SERVICE IMAGE      │      LOCAL       │  LINKED
─────────────────────────┼──────────────────┼────────────
  supabase/postgres      │ <IP_ADDRESS>        │ <IP_ADDRESS>
  supabase/gotrue        │ v2.164.0         │ v2.164.0
  postgrest/postgrest    │ v12.2.2          │ v12.2.2
  supabase/realtime      │ v2.33.58         │ -
  supabase/storage-api   │ v1.14.4          │ v1.14.4
  supabase/edge-runtime  │ v1.65.3          │ -
  supabase/studio        │ 20241202-71e5240 │ -
  supabase/postgres-meta │ v0.84.2          │ -
  supabase/logflare      │ 1.4.0            │ -
  supabase/supavisor     │ 1.1.56           │ -

Additional context
n/a

Thanks for reporting this issue. It's apparently working only if supabase directory is at top level of your repo. I will push a fix for monorepo setups where supabase directory is nested somewhere.


Integrate relay dashboard

To make component reuse possible between ultrasound.money and relay.ultrasound.money possible, this PR integrates existing relay dashboard to this repo. Here's the high level idea:

Relay dashboard gets its own next page relay.tsx
Relay specific code goes into src/relay. The code uses existing components and these could be moved into a shared dir later
middleware.ts contains a redirect and a url rewrite, so that the relay page can be hosted at the root of the relay subdomain
The relay subdomain is pointing to our MEV boost cluster, so we need to host a separate deployment of the frontend there

Some things to pay extra attention to:

Make sure this change doesn't break caching / invalidate static objects in next for main site
Make sure the middleware doesn't have any unintended consequences for main site requests
Metadata/scripts defined in _document.tsx can't be overwritten by child components, so to define some data differently for the relay dashboard, i had to move those to page level. Not too happy about this, let's make sure this doesn't have any SSR or caching consequences.

There's no huge rush to merge this branch into main. I can deploy new relay dashboard features from this branch until everything checks out for main site.

Looks good.
I did spot one issue, next is complaining now that the plausible script is added in the head section:

They link to this explainer: https://nextjs.org/docs/messages/no-script-tags-in-head-component
Can you fix that still?


GetImageAsJpgAsync throwing NRE

This code was working fine on 2.0.5 but now throws a NRE
        private async void ProfileImage_Success (object sender, FFImageLoading.Forms.CachedImageEvents.SuccessEventArgs e)
        {
            if (ProfileImage != null && _viewModel != null)
                _viewModel.ImageRaw = await ProfileImage.GetImageAsJpgAsync();
        }

I think we didn't change anything related to this method in 2.0.6.

Could you provide more details?
What platform?
Any stack trace?

looks like it was getting executed on a background thread and crashing out.
        private void ProfileImage_Success (object sender, FFImageLoading.Forms.CachedImageEvents.SuccessEventArgs e)
        {
            Device.BeginInvokeOnMainThread(() =>
                {
                    try
                    {

                        _viewModel.ImageRaw = ProfileImage.GetImageAsJpgAsync().Result;
                    }
                    catch (Exception ex)
                    {
                        Debug.WriteLine(ex);
                    }
                });

        }

seems to have fixed it. Thanks!

@highplains But could you tell me what platform is this? I can change that it'll be executed on main thread by default to avoid Device.BeginInvokeOnMainThread in future releases.

The platform I was testing on was iOS. Thanks!

Callbacks should be invoked on main thread. So we should change that

Success callback is now ALWAYS invoked on main thread.
Remark: Error callback and Finish callback do not enforce the main thread


Slashable message propagation post-deneb

The existing gossip rules mean we can propagate two (or more) slashable messages so long as they are not both blocks, or both sidecars of the same index. I don't think this is necessarily a bad thing in itself but I do think it makes things unnecessarily more complicated in implementation.
This has implications in the block production endpoint for example:
https://ethereum.github.io/beacon-APIs/#/Beacon/publishBlockV2
According to existing rules, clients should return 202 and publish (if broadcast_validation = gossip) when receiving a message consisting of a block and a blob sidecar containing a slashable block header, even though this is immediately identifiable as slashable.
Related to this, the existing rules force clients to build caches tracking slashability not just across all block components (which clients must in slasher implementations and also to support broadcast_validation = consensus_and_equivocation), but also at lower levels of granularity (blob index and message type). For example we have to differentiate between the following scenarios when signed_header_a and signed_header_b are slashable:
Scenario 1
Message 1: (signed_header_a, blob_index_1)
Message 2, not propagated: (signed_header_b, blob_index_1)
Scenario 2
Message 1: (signed_header_a, blob_index_1)
Message 2, propagated: (signed_header_b, blob_index_2)
The suggestion here is to split the blob gossip rule related to slashability into two rules, one that's just about de-duplication, and one that's related to slashability more generally. And to add a general slashability rule to block gossip.

I would only do this if you have sent or have seen a slashing message on gossip related to this. Otherwise, this could artificially prevent slashers from getting it!
I think we've talked about things directionally like this in the past but not integrated. One reason might be the implication of having to track "slashable" which not all clients have that notion beyond the external slasher. Obviously with blocks, it's a bit of an easier map than getting surrounds for attestationa

I would only do this if you have sent or have seen a slashing message on gossip related to this. Otherwise, this could artificially prevent slashers from getting it!

Do you mean with regard to the publish in the beacon API? I guess still publishing even if its slashable is reasonable, but I don't see how it'd be beneficial to the network. Maybe punishing one bad actor, but on the other hand if the block was never published they didn't do any damage.

But moving the condition to be "seeing or sending a slashing related to this" makes it less important that each client is a baseline double-block slasher

To try to keep it in this direction we could do something like this:
- _[IGNORE]_ The sidecar is the first sidecar for the tuple (`hash_tree_root(block_header)`, blob_sidecar.index) with valid header signature, sidecar inclusion proof, and kzg proof.
- _[IGNORE]_ The sidecar's block header is the first with valid signature received for the proposer for the slot block_header.slot.

This gets rid of the quirky scenario in the PR description. But we do still need to separately track slashing with blocks and blobs. I think tracking a single idea of a "slashable block" is still very simple. But I guess technically you could get away with fewer caches if you didn't care about slashability anywhere else.

I've been thinking about this in the opposite direction: that we should propagate slashable messages - this enables them to reach a slasher, which makes the mechanism more fair (and potent) and removes a cache rule that otherwise clients have had problems with.

that we should propagate slashable messages - this enables them to reach a slasher, which makes the mechanism more fair (and potent) and removes a cache rule that otherwise clients have had problems with.

so my suggestion tries to find the best of both world -- you don't drop/IGNORE on slashable, you ignore if you seen or created a slashing for that validator (or maybe honed in on slot) on gossip. Thus you get to anti-dos as long as you or someone else has raised the alarm to the network -- trading N potential DoS messages for a 1 slashing message

I also would like the slashable messages to reach the slasher.

I guess still publishing even if its slashable is reasonable, but I don't see how it'd be beneficial to the network. Maybe punishing one bad actor, but on the other hand if the block was never published they didn't do any damage.

They actually do some damage. If you don't forward the slashable blocks, the views can be split across the network.
Let's say the proposer proposes two slashable blocks: block1 and block2. If the nodes don't forward a block when they have already seen the other one, half of the nodes in the network will have only block1 in their view and the other half have only block2 and the network is now split. I think it's better to have all the nodes have both blocks in their views since both of the blocks are already published.
Please let me know if there is anything I misunderstood.

Adding https://github.com/ethereum/consensus-specs/pull/3257 for reference

If the nodes don't forward a block when they have already seen the other one, half of the nodes in the network will have only block1 in their view and the other half have only block2 and the network is now split.

Just because messages don't make it there on the gossip, does not mean messages don't make it to all peers eventually due to message-dependency lookup filled by req/resp.
E.g. if you didn't get a block on gossip, but get attestations about that block, you'll look up the dependency from your neighbors
There is a trade-off between preventing short-term view splits and hardening the gossip to an adversary that is willing to be slashed.


Test Lighthouse in Travis

We’re breaking Lighthouse too often, this enables Lighthouse
deployment testing on all PRs.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

Failing with:
scripts]$ kubefedctl federate namespace default --kubefed-namespace kubefed-operator
F0220 09:25:05.284081    1546 federate.go:151] Error: no matches for kind "FederatedTypeConfig" in version "core.kubefed.k8s.io/v1beta1"

@skitt @vthapar can you have a look at this: https://travis-ci.com/submariner-io/submariner-operator/builds/149780723#L2048
Why isn't it deployting the federation stuff?

We need to create a merged kubeconfig and use that when we join. (I’ll take care of this.)


DSD-764: Removing bad log messages from the Pagination and List components

Fixes JIRA ticket DSD-764
This PR does the following:

Fixes logic that logged messages that weren't always true for the Pagination and List components.

How has this been tested?
Storybook and unit tests.
Accessibility concerns or updates

N/A

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr861-3fnn3qisibmoevwljfbgxk8ijr2mpb2r.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6202c72c046a4b8d29ca9019


Move to terra & general clean up

This PR moves hyRefactor to terra and away from raster. Along the way general clean up was performed to ensure all tests pass with devtools::test(). While these all pass, the tests run through devtools::check() fail spectacularly.
On my machine this was the case pre-changes, so I am going to submit this. Other (unfortunately
non-exhaustive - bad note taking) things:

removedmagrittr dependency calling dplyr %>% instead
reduce some tidyr dependency
removed xml2 dependency calling rvest::read_html instead
removed ::: call to nhdplusTools check7z - this should be exported (currently copied here)
fixed some 'global' scoping calls
removed stringr dependency with explicit paste(..., collapse = ",")
cut methods::is call, I think we can remove methods::slot as well
moved CRS handling into reconcile. Also, raster, SpatRast and paths can be passed directly to fdr and fac
fixed data calls in tests using a more generic list.files. I think all data in inst should be moved to tests to if check is ever going to pass
removed rgdal calls everywhere!

This PR should close when I merge #25


Memory leak with $setValidity

If ng-model is used within a form and toggled with ng-if and $setValidity is called on the ngModelController, then a memory leak occurs.
Specifically, the $setValidity call in ngModel (line 3172) adds a validity entry to the parent form controller that keeps a reference to the ngModelController. There's nothing in place to remove this entry if that controller gets destroyed, so these references stick around. Worse, the $setValidity call is added to the ngModelController by creating a closure that wraps the ngModel's element, which can result in leaking quite a bit of memory in complex applications.
This plunker demonstrates the issue by printing out the number of ngModelController references maintained by the form controller each time you toggle a form input off/on.

Correct line number referred by @dlongley is in v1.3.7: https://github.com/angular/angular.js/blob/v1.3.7/src/ng/directive/input.js#L3172


Italiano to vitepress

huh i already did this why is it not conflicting https://github.com/Geoxor/Amethyst/commit/893d14683340fc4e4ed2cc8c18bae9257d6e1043


Allow remote source as input

See https://grips.semantic-web.at/x/eYRlB for details.
The API is already available.

It's a pity this was in backlog, since I did not notice it. Will get back to it in 4th iteration.


tf.contrib.factorization.python.ops.factorization_ops.WALSModel greedy parallelization

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Linux Ubuntu 16.04 and macOS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: n/a
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.12+
Python version: 3.5
Bazel version (if compiling from source): n/a
GCC/Compiler version (if compiling from source): n/a
CUDA/cuDNN version: 9.2
GPU model and memory: Titan

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
when trying to train a WALSModel in parallel (e.g. with n different parameter sets or any other tf model) using the python multiprocessing module (or in two different scripts), CUDA errors occur. It seems that WALSModel is written to automatically parallelize itself and in a greedy manner...
looking at the init, I can not see a way to specify to limit this...
def __init__(self,
               input_rows,
               input_cols,
               n_components,
               unobserved_weight=0.1,
               regularization=None,
               row_init="random",
               col_init="random",
               num_row_shards=1,
               num_col_shards=1,
               row_weights=1,
               col_weights=1,
               use_factors_weights_cache=True,
               use_gramian_cache=True,
               use_scoped_vars=False):

Describe the expected behavior
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@walidk  seems to work, I'll try putting it in my app's use case and see if that solves the problem

Thanks for the update. Closing this now.
Feel free to reopen if you run issues with the solution.


Figma variables integration

This PR includes the minimum necessary code to migrate to the new Figma variables export and also theming and viewport support.
The new export (design-tokens.tokens.json) includes the theming variables inside the semantic-tokens field (right now only dark and light) and the view ports variables inside the constraints field (right now only desktop and mobile). The rest are considered "independent" variables.
A custom style dictionary formatter (cssFigmaVariables.cjs) has been implemented to parse this information and organize it in a convenient way. And also to rename some of the output css variable names.
The returning string of the formatter is what is going to be written to the resulting design-tokens.css file. If you test it using this branch, you would get 5 "blocks" of css variables:

:root ---> css variables that are independent of a theme or viewport
.light ---> css variables for the light theme
.dark ---> css variables for the dark theme
@media (max-width: 480px) ---> css variables for the mobile viewport
@media (min-width: 481px) ---> css variables for the desktop viewport

The way the script works is by iterating through the information of design-tokens.tokens.json, but the version parsed by style dictionary (see docs). And we store each variable to the corresponding category.
In the end we just do some string manipulation with this data structure to generate the 5 blocks of css variables mentioned before.
The rest of the changes are the minimum necessary to not to break the existing components. The support to change the theme in story book is also added but components are not migrated to support the new dark theme. This will be implemented in a different PR.

Not sure whether I'm a fan of the new additional nesting in the font styles with "body" and "heading". Makes the variables longer and doesn't add any helpful information. I'll take it up with UX, we can keep it like this just so we get this PR done.

Where do we stand with this PR atm? I see that there is a lot of visual font changes, but that seems to be alright since we change the font face. Is there anything blocking still?

I just saw the way we include the font-faces. I solved this for my customer a little different and I could change this here too. The way we did it is reference the font as src: url('the-font.woff2').
This leads to vite not resolving this url but leaving it to the bundler that uses the library to bundle this font as it sees fit. The only additional change that this requires is in the storybook vite config we would have to make sure, that those fonts are loaded from /the-font.woff2. But no CSS changes required. That would make this a little easier. If you agree I'd implement this solution here too.

I just saw the way we include the font-faces. I solved this for my customer a little different and I could change this here too. The way we did it is reference the font as src: url('the-font.woff2'). This leads to vite not resolving this url but leaving it to the bundler that uses the library to bundle this font as it sees fit. The only additional change that this requires is in the storybook vite config we would have to make sure, that those fonts are loaded from /the-font.woff2. But no CSS changes required. That would make this a little easier. If you agree I'd implement this solution here too.

Yeah go ahead with it, sounds good to me.


Add custom telemetry event

Add the capability to define a custom telemetry event using SDK capability.
@garypretty - can you add details?

PR raised to add a new action into the SDK.  This action allows a user to specify an event name and, optionally, additional properties to be attached to the event.  The event is tracked using the registered IBotTelemetryClient and will be captured alongside the existing passive telemetry capture that is already present.


node and node-static-auth recipes are vulnerable to timing attacks

👋 thank you for making these recipes available, it’s been very helpful for me.
Just wanted to point out that both the node and node-static-auth examples are in theory vulnerable to a timing attack to determine the login/password.
Here is how express-basic-auth fixed this: https://github.com/LionC/express-basic-auth/pull/21
For further reference, see also how Rails fixed the same issue in their basic auth check, and how that CVE is classified: https://github.com/rails/rails/commit/a6fa3960c3a149e83eb2ff057be4472a82958e3d.

Hey @thibaudcolas, thank you very much for pointing this out and for all the info! I'll look into it asap.


License conflict MIT vs. Apache

monaco-editor version: 0.20.0
Browser: any
OS: any
monaco-editor is built with a number of submodules, which is described in CONTRIBUTING.md. One of the modules is monaco-typescript, which is released under MIT as well.
In one of my React projects I use the monaco-editor as an important part. The production build generated by Babel puts a file ts.worker.js.LICENSE in the output dir, which mentions that the license is Apache, not MIT. I would expect that the module and the worker use the same license (assuming here that the worker is actually implemented in that module).
Is this an oversight or do I misunderstand something here?

The monaco-typescript project uses the TypeScript compiler. The TypeScript compiler is licensed under Apache. For development purposes (due to how we need to "massage" the .js files of the typescript compiler to make it compatible with AMD or ESM), we had to inline the typescript compiler sources inside monaco-typescript.
That is why there is an accompanying ThirdPartyNotices.txt file in the root of the monaco-typescript repository which credits the extra OSS present in the repository -- https://github.com/microsoft/monaco-typescript/blob/master/ThirdPartyNotices.txt
So to clarify, the monaco-typescript project uses the MIT license for all of its own sources (what is actually developed in that repository), but maintains and respects the license of the TypeScript project for the TypeScript compiler (which is inlined in the repository at https://github.com/microsoft/monaco-typescript/tree/master/src/lib ).

If you install the monaco-editor from npm, it will also come with a LICENSE file and a ThirdPartyNotices.txt file. The LICENSE file is MIT and the ThirdPartyNotices.txt lists the licenses of other OSS software that is bundled inside with the editor. e.g.:

nodejs path library (https://github.com/nodejs/node/tree/43dd49c9782848c25e5b03448c8a0f923f13c158)
string_scorer version 0.1.20 (https://github.com/joshaven/string_score)
chjj-marked
typescript
HTML 5.1 W3C Working Draft version 08 October 2015
JS Beautifier version 1.6.2
Ionic documentation version 1.2.4
vscode-swift version 0.0.1

The monaco-typescript project uses the TypeScript compiler. The TypeScript compiler is licensed under Apache. For development purposes (due to how we need to "massage" the .js files of the typescript compiler to make it compatible with AMD or ESM), we had to inline the typescript compiler sources inside monaco-typescript.
That is why there is an accompanying ThirdPartyNotices.txt file in the root of the monaco-typescript repository which credits the extra OSS present in the repository -- https://github.com/microsoft/monaco-typescript/blob/master/ThirdPartyNotices.txt
So to clarify, the monaco-typescript project uses the MIT license for all of its own sources (what is actually developed in that repository), but maintains and respects the license of the TypeScript project for the TypeScript compiler (which is inlined in the repository at https://github.com/microsoft/monaco-typescript/tree/master/src/lib ).

If you install the monaco-editor from npm, it will also come with a LICENSE file and a ThirdPartyNotices.txt file. The LICENSE file is MIT and the ThirdPartyNotices.txt lists the licenses of other OSS software that is bundled inside with the editor. e.g.:

nodejs path library (https://github.com/nodejs/node/tree/43dd49c9782848c25e5b03448c8a0f923f13c158)
string_scorer version 0.1.20 (https://github.com/joshaven/string_score)
chjj-marked
typescript
HTML 5.1 W3C Working Draft version 08 October 2015
JS Beautifier version 1.6.2
Ionic documentation version 1.2.4
vscode-swift version 0.0.1

I see, thanks for the explanation. Very useful info!

I see, thanks for the explanation. Very useful info!


Upgrade fails at kismatic-inspector

Attempting to upgrade a cluster created with v.1.2.2 using v1.3.0:
kismatic upgrade offline --dry-run
Every master, etcd, worker node fails with :
Error: error running inspector against remote node: server responded with non-successful status: "400 Bad Request"
running:
<path to>/kismatic-inspector client <etcd-node-ip>:8888 --upgrade --node-roles etcd
produces the same error.
From the logs on the node:
kismatic-inspector: 2017/04/03 17:36:19 error unmarshaling rules from JSON: rule with kind "freespace" is not supported
Looks to be an incompatibility between versions of inspector, I expect this could be worked around with a custom rules file, but I cannot find an example of this.
Any hints?

Hey @TimWoolford
You should not have to modify the inspector's rule set. This does seem to point to the possibility that an old inspector server is running on the node when we run the upgrade preflight checks.
Can you remove the inspector binary and service from one of the machines to see if the this resolves it?

Thanks @alexbrand, yes the new binary had been installed into /bin, but there was a running process left over from the 1.2.2 installation.

--dry-run passes now, but @swade1987 told me not to upgrade just yet ;-)

This is unexpected. Action to take here is to manually reproduce this issue, and change our inspector setup tasks to stop existing inspectors before starting the new one. From a quick glance at the ansible play, we should already be doing this, but seems like we are not.

I've retraced my steps and I can reproduce the issue by running kismatic install validate after the cluster had been built.
This fails due to port availability - obviously, but leaves the inspector running on the nodes.
Probably not many people will do silly things like this.

This was fixed by #525


Add example buttons for 3 calculators for Golden and Silver buttons , all calculators under Paraboloid

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018


[🐛] Cannot get image original name

Hello everyone, I am uploading an image, I need the original name of the image, but it does not give me the original name of the image

Hello everyone, I am uploading an image, I need the original name of the image, but it does not give me the original name of the image

use Document picker
https://www.npmjs.com/package/react-native-document-picker


Problem with the inclusion of dynamically generated PNG images in PDF generator

I've got an problem with dynamically generated images in PDF documents. I have two charts side-by-side in a one row, two column table like so:
|===
| P | K
| image:http://localhost:8080/chart/nmp/SoilIndexBarP/1[640,240]
| image:http://localhost:8080/chart/nmp/SoilIndexBarK/1[640,240]
|===

But the first image never renders. I just get text "[640,240]". And I see this error in the logs:
asciidoctor: WARNING: could not embed image: /tmp/image-20181019-7309-y6masx; No such file or directory @ rb_sysopen - /tmp/image-20181019-7309-y6masx

However this seems to happen only the first time that image is used in the document. Subsequent references to the same URL seem to work ok. So I can work around the problem by first rendering a 0x0 pixel version of the image. But it does cause unwanted vertical white space.
image:http://localhost:8080/chart/nmp/SoilIndexBarP/1[0,0]
image:http://localhost:8080/chart/nmp/SoilIndexBarK/1[0,0]

|===
| P | K
| image:http://localhost:8080/chart/nmp/SoilIndexBarP/1[640,240]
| image:http://localhost:8080/chart/nmp/SoilIndexBarK/1[640,240]
|===

I should have added I'm running Ubuntu 18.04 on amd64 arch.
Asciidoctor PDF 1.5.0.alpha.16 using Asciidoctor 1.5.5 [http://asciidoctor.org]
Runtime Environment (ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]) (lc:UTF-8 fs:UTF-8 in:- ex:UTF-8)

Thanks for reporting. The problem is that the behavior of Tempfile is incompatible with how we are using it. The temporary file gets deleted when the object is finalized, but we need it to stick around longer. Fortunately, a new method has been added on Tempfile that generates a temporary file but does not attach it to the finalizer. I switched to that method and implemented it for Ruby < 2.1.0.

FYI, you are writing the image macro incorrectly. The width and height are the second and third positional attribute, respectively. It should be:
image:http://localhost:8080/chart/nmp/SoilIndexBarP/1[,640,240]

or
image:http://localhost:8080/chart/nmp/SoilIndexBarP/1[Alt Text Here,640,240]

Thanks for the fast response and fix. I'll try out the patch later in the week. Joe.

Great! I look forward to hearing the result.
It's amazing we got this far and didn't realize how problematic that logic was. The documentation for Tempfile is super unclear. It wasn't until I read an article about Tempfile.create that I even realized Tempfile.new had the behavior it did. But I'm grateful the method now exists because it's really exactly what we want here.


Crystals + Respawn Anchors?

Could you implement Crystals and Respawn Anchors?

And also TNT

Respawn Anchors are actually a PVP Method. It's been used in many crystal servers, such as mcpvp.us.

Got crystals working! Although you have to register the explosion supplier to an instance for it to work, and I don't think there is a workaround for it

Respawn anchors and tnt are working too

tysm :D


TAMAYA-349: Ensure Tamaya builds on JDK 11

This updates the JaCoCo and Javadoc plugins so that Tamaya can be build on JDK 11.

mmmh - build seems to fail on various JDKs:
https://api.travis-ci.org/v3/job/431841974/log.txt
https://travis-ci.org/apache/incubator-tamaya-sandbox/jobs/431841974
Any connection to your changes?!

It seems that the failures are related to the Vertex tests, which I've seen to be inconsistent. That is, they often pass but sometimes fail for no apparent reason. I believe this has more to do with timing than the particular JDK the test is run on.

I've seen the Vertex tests be flaky in my own work on jdk 8, but I don't know much about what it's trying to do or why it's flaky.


Standardize kubelet working dir

As mentioned in #1644 and documented in #1690, the kubelet is started with a current working dir that is inconsistent across platforms, and non-standard in some cases.
On GCE the current working dir is /.  On CoreOS, I'm told it is CWD=/home/core.
This affects at least the location of the dockercfg, and may affect other things we haven't though of yet (where corefiles go, etc).
The root dir is almost certainly not the right place for various inputs and outputs of kubelet.  Is /root the right place?  If we change it, we should make a small announcement since it will affect a few users who are depending on the .dockercfg location.

Is this still an issue?  I thought it was fixed...

We look for dockercfg in several places.  Beyond that, I think that we
don't care what the kubelet working dir is.  Close it?
On Wed, Jul 8, 2015 at 10:26 PM, Tim Hockin<EMAIL_ADDRESS>wrote:

Is this still an issue? I thought it was fixed...
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/1691#issuecomment-119821954
.


✨ [Feature request]: Add Home Grown Testimonial for ReactPlay

Is your feature request related to a problem? Please describe.
It is not a problem. It's a feature request.
We have a section to post community speaks where we show static Tweets.

It doesn't scale due to the following reasons:

The Tweets are driven by the static ids
It renders slow
Twitter is making their APIs priced to query these

Hence the proposal is to create the functionality of homegrown testimonials.
Describe the solution you'd like.
Here are the expectations:

Provide an ability for users to authenticate and write testimonials about the platform.
User should be able to select a category like General, and event name(#2PlaysAMonth, Hack-R-Play, etc) to provide the testimonial. If nothing selected, Geberal selects by default.
Recent 10 testimonials should be shown on the home page where the tweets are shown now.
Each testimonial should have the message, category, date, and the event name shown.
There should be a link to take users to all testimonial page(/testimonials) route where all the testimonials must be listed in the date order(recent to old)
Provide a filter on the testimonials page to filter by the events.

Describe alternatives you've considered.
None.
Screenshot / Screenshare
Shall Share some design thoughts in the next comment.
Additional context
Talk to @atapas and @koustov for further discussions.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Here is an idea for the testimonial page:

Interesting! ✨
I will be working on this ASAP

Interesting! ✨
I will be working on this ASAP

Count me in if you need any help or got any questions. @koustov is doing the DB part but you can get started with UI with fake JSON data in the mean time.

@6km The tables are ready. Here is example fetch query
query MyQuery {
  testimonials {
    id
    quote
    user
    event
    user_id_map {
      avatarUrl
      displayName
    }
    event_map {
      name
    }
  }
}

The response to the above query:
{
  "data": {
    "testimonials": [
      {
        "id": "1e19f639-be73-42bb-8387-ba89277b7d4c",
        "quote": "ReactPlay community is awesome. So glad to be part of it.",
        "user": "0680f581-6584-4bc4-bbe9-aa7c97567e72",
        "event": "95063183-6a29-4c34-b08e-10cb306ea29c",
        "user_id_map": {
          "avatarUrl": "https://avatars.githubusercontent.com/u/3633137?v=4",
          "displayName": "Tapas Adhikary"
        },
        "event_map": {
          "name": "General"
        }
      }
    ]
  }
}

@6km The tables are ready. Here is example fetch query
query MyQuery {
  testimonials {
    id
    quote
    user
    event
    user_id_map {
      avatarUrl
      displayName
    }
    event_map {
      name
    }
  }
}

The response to the above query:
{
  "data": {
    "testimonials": [
      {
        "id": "1e19f639-be73-42bb-8387-ba89277b7d4c",
        "quote": "ReactPlay community is awesome. So glad to be part of it.",
        "user": "0680f581-6584-4bc4-bbe9-aa7c97567e72",
        "event": "95063183-6a29-4c34-b08e-10cb306ea29c",
        "user_id_map": {
          "avatarUrl": "https://avatars.githubusercontent.com/u/3633137?v=4",
          "displayName": "Tapas Adhikary"
        },
        "event_map": {
          "name": "General"
        }
      }
    ]
  }
}

I will be adding a title field as well and this will be mandatory

What do you think of this UI design?

@koustov What do you think of this UI design?

@koustov Do you have any further suggestion to this?
Also can we please add two more event details in the table?

Twitter Spaces(No start and end date)
ReactPlay Live(No start and end date)


Smart grouping for commits from renovate (e.g. branch automerge mode)

Currently, skipCommitsWithoutPullRequest: true is the default and hence skips all commits which haven't been merged through a PR.
This will skip all commits when using the branchautomerge setting in renovate.
While one can skipCommitsWithoutPullRequest: false, all of these commits won't have a label and will be automatically put into the "Misc" category.
After #182, I'd suggest to

group all renovate updates by default into the "Dependency" category
find a way correctly group renovate commits through branch automerge (should be doable through the commit title pattern)
Add an option to not ignore branch-automerge commits by default, e.g. something like AlwaysIncludeRenovateCommits: true. This would still skip "normal" commits but by default include branch-automerge renovate commits

(All of the above might not only apply to renovate but also to other dep automation tools like GHs dependency bot).

Example for branch-automerge commits (with skipCommitsWithoutPullRequest: false).
If renovate uses conventional commits, one could look for the chore(deps): pattern and automatically assign such commits to the "dependency" section.
Yet, first a logic to process based on commit messages would need to be added.
Another improvement that comes to my mind: Only keep the most recent commit for dependencies. I.e., it is not helpful to anyone to include every bump of a particular dependency, only the most recent one matters for the release notes. Could be done by some smart regex matching that

only processes entries that start with chore(deps):
Requires a minimum of characters to exactly match, e.g. "30". This should prevent false-positives to be processed/removed


Any plans to include Member to the LinkPicker?

I came across this number of times but cant seem to find a picker with Member included.
Are there any plans to include member picker?

@akeilox Can you tell some more about what you're trying to do? As members doesn't have a view or URL by default, I'm not sure how a member picker in the link picker would make sense.
Anyways, Umbraco comes with a build-in property editor for selecting (a single) member. Doesn't this do what you need, or do you need something more?


Customizable modal styling?

Are there any options for customizing the checkout modal styles or is that more of react-stripe-elements implementation?

+1

+1

+1
Would be really nice if the components had style customization. :)


chore: release v0.1.0

Automation failed because there was no previous tag. Will create it manually. Future ones should work.


Features - link to API doc & show JSON

Add API documentation link to About:
https://developer.android.com/google/play/integrity/overview
For people to learn what they are testing
It would be also nice to see JSON with verdict (like in YASNAC for SafetyNet)

The json doesn't give more info for device integrity from what it's already displayed but sure I'll add it

Thanks

Thanks, updated PI API Checker to v1.0 from Google Play - we have now Learn what the results mean (link to official Verdict doc) and Raw JSON response


Relay Modern support

This is an example of code of RelayModern
import AnotherComponent from './AnotherComponent';

const fragmentContainer = createFragmentContainer(
  Component, {
    viewer: graphql`
      fragment Component_viewer on Viewer {
        user(id: $id) {
          id
          ...AnotherComponent_user
        }
      },
    `
  },
);

it will get the fragment from the AnotherComponent, but this plugin is think the fragment AnotherComponent_user is undefined
Example of fragment declaration in another file:
export default createFragmentContainer(AnotherComponent, {
    user: graphql`
      fragment AnotherComponent_user on User {
        id
        name
        email
        active
      }
    `,
  },
);

+1.
I need this feature too, but I'm figuring if I can help to build it.
where or how can I find the knowledge to build this plugin?
@jimkyndemeyer could you pls hint some keyword to google~~

@jonirrings I think that implementing this issue requires quite a bit of experience with the IntelliJ Platform SDK. It cuts across the Virtual File system, PSI Files/Directories, CompletionContributor, Annotator, PSI References for go to definition etc., not to mention some kind of configuration or detection of Relay Modern when using the graphql tagged template litteral.
If you want to give it a try, the starting point is http://www.jetbrains.org/intellij/sdk/docs/
Also, to get this plugin up and running, see DEVELOPING.md
Unfortunately, due to other personal commitments, I don't have any spare time to work on this plugin until autumn at the earliest.
@asiandrummer is the work you're doing on integrating the GraphQL language service with IntelliJ of relevance to this issue?
Best regards,
Jim.

thanks for your reply, struggling with the SDK doc, hope I am ready before autumn:smile:

@jimkyndemeyer - I'm happy to make a monetary contribution ($100) if that would help get Relay 1.0 support.  Perhaps others would as well.
I just found this plugin and quite like it, but we just finished a switch to modern so it yields a couple of the some errors everywhere.  Please let me know.

@rosskevin Thanks for the support, but the limiting factor here is quite simply that I don't have the spare time to work on this project until autumn at the latest.
A PR would be great, but realistically it would require a working knowledge of the IntelliJ IDEA SDK.

@jimkyndemeyer the latest push to graphql-language-service supports Relay Modern, and I'm currently working to support it in the IntelliJ as well. I'll update my progress here as things move forward!

can we just enable graphql.experimental syntax highlighting for now?
is it an easy fix?

Merged graphql.experimental support for the 1.5.3 release. Pending approval in the Jetbrains plugin repo.

I've got 1.5.4 version and still have the same problem (described in first post). When can we expect support for Relay Modern?

Just give a status on this. I have made some progress on this, but the change cross-cuts all the major features such as completion, error highlighting, find usages, and go to definition.
This in combination with other personal commitments means that I don't have an expected ETA just yet, but I'll keep this issue updated.

@jimkyndemeyer is #76 the current status of this plugin?

@chadfurman See my latest commit.
I should be able to get fragment support for you guys within the next week or so.

Version 1.6 with Relay Modern fragment support has been uploaded to the plugin repository and is now pending approval by Jetbrains.

@jimkyndemeyer Super cool!  :)

@jimkyndemeyer it works great!  Thank you so much!

@chadfurman Glad to hear it :)

This is absolutely great, thank you for this!
I'm using and including fragments from a separate package as well, residing in node_modules. Is there a way to tell your plugin to scan for fragments in that package as well?
I guess it'd mean I'd need to be able to set multiple paths for fragment scanning, as well as make the plugin scan .js.flow-files in addition to .js files, as all the .js-files will have had their actual fragment definitions removed, but the .js.flow-files won't have.
Thanks in advance!

@jimkyndemeyer great work on this
I'll close
it is awesome enough for me, tks

Ahh, I'll go ahead and open a new issue instead. :)


Customize CLI command names

What are you trying to do?
Allow customizing how function names are translated into commands.
For example:
// +command=e2e
func (m *Ci) E2e() {
    // ...
}

Why is this important to you?
Function names are often translated to weird commands. For example E2e becomes e-2-e.
How are you currently working around this?
I call my end-to-end test function Etoe. 🙈

Rather than customizing the CLI name, we need to enable customizing the name in the API. Python and Typescript do that through the decorators:

Python: Name Overrides
TypeScript: Aliases

This would add paritity in Go, but probably with +name instead of +command.
However, if doing the same as Py or TS, does it lead to the same issue of e2e translating to e-2-e? I'll need to check where that's happening because we use two different Go utils in different places. One of those (I suspect strcase) is breaking numbers instead of just changes in casing.
The API uses the same naming convention as TypeScript (camelCase), which is similar to Go (PascalCase), in that both use casing to split words. Python's much simpler to break words into (snake_case), same as the CLI (kebab-case). So maybe using the CLI's convention is the more neutral and consistent way to override the names in all SDKs.
Think about acronyms. For example SSH translates to s-s-h unless you have a list of common acronyms (like we do). But overriding to +name=ssh would make it less ambiguous or easier to know how to convert consistently.


Control: address the backward driving stuck issue due to rough calib …

…table

What is the backward driving stuck issue here? Does it happen when backing a car?


[Improvised][3.1] Grammar & Lint Fixes to Index Page

Purpose
Grammar & Lint Fixes to the Index Page of 3.1.0 Branch.
Please find the respective PR for the master branch #1300

@shaniR , can you please review this PR.


Issue with vanishing MudText on mobile that is placed over a video via z-index

Bug type
Component
Component name
MudContainer
What happened?
I am facing a strange issue with one MudContainer: The container contains a embedded Video and a MudText element, the Video has a z-index of 10 and the MudText of 20. On Desktop the Text is displayed on the lower left of the video as it is intended, when I check mobile view during debugging via the browser debugging tools it also looks fine. However when I open the page deployed on a server via a mobile browser, does not matter if Safari, Firefox or Chrome, the text is gone.
I was able to reproduce the issue on try.mudblazor.com with the same issue.
Expected behavior
The MudText should remain visible on a Mobile Browser.
Reproduction link
https://try.mudblazor.com/snippet/QYQIYBYsJoCYHdGW
Reproduction steps

Open the Reproduction Link on a Mobile Browser and on the Desktop
Check if the text is visible on both

Relevant log output
No response
Version (bug)
7.0.0
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Safari
On which operating systems are you experiencing the issue?
iOS, Android
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

works on my mobile.

Working for me as well on Android 14 Edge. Is it possible you need to refresh your CSS cache?

I am seeing this issue on IOS with Safari, Firefox and Chrome and based on my Clients Feedback they have the issue on Android, although I do not know which Android Version they are running.


Controlling scroll behavior when clicking a

I am trying to use Route.ignoreScrollBehavior on each route to stop the jump-to-top effect when clicking a <Link> element. But it doesn't seem to do anything because on each page change, the scroll position moves to the top.
Full snippet here
Route.ignoreScrollBehavior
<Route name="all" handler={TodoApp} ignoreScrollBehavior />

Tried this from something I saw in the changelog
<Route name="all" handler={TodoApp}  scrollBehaviour="none" />

I tried setting the scrollBehaviour in Router.create but that doesn't seem to do anything. I also found this confusing because the documentation isn't clear on what to set the value as.
I found some documentation saying you can use strings. I assume this is actually for adding the scrollBehaviour property to a <Route> itself which is deprecated and removed. Strings don't work anyway because it complains about it not having a updateScrollPosition property.

'browser'
'scrollToTop'
'none'

I assume that it wants to use the modules/behaviors that are exported. In the tests, the behaviours are used.
var { ImitateBrowserBehavior, ScrollToTopBehavior } = Router;

Router.create({
	routes: routes,
	scrollBehaviour: ImitateBrowserBehavio // or `ScrollToTopBehavior`
});

Related to issue #432.

The string API is gone, you only have the two scrollBehaviors for Router.create and the option to add ignoreScrollBehavior to your <Route>s.
I think your problem is that the browser itself does the scrolling. With ignoreScrollBehavior, you just tell react-router to stay out of scrolling, but not that it should override the browser's default behavior.
Sadly, due to browser inconsistencies and the lack of an API, I don't think there's a good way to make a robust PreserveScrollPositionBehavior or something like that without browser sniffing.. Even the current behaviors aren't perfect in that way.
An option could be to relocate the scrollbar using css overflow, but that could also disable some wanted browser features such as "Scroll to top".

I am trying to use Route.ignoreScrollBehavior on each route to stop the jump-to-top effect when clicking a  element. But it doesn't seem to do anything because on each page change, the scroll position moves to the top.

It works within the route and its children. Applying it to leaf routes only makes transitions within each of them (e.g. param changes) ignoring scroll, but transitions between one and another of them will still reset scroll.
What you want is to put ignoreScrollPosition on the parent route of all routes you want to have this behavior when transitioning from or to each other.  Just tried it again it still jumps upward in Chrome and Firefox.
By placing it on individual routes I thought any transition to that route would not cause a change. It would be nice to have some of that granularity as a feature (although not needed in this case).

Any chance you're not immediately rendering the whole content? In this case page will collapse and there's no way for us to restore position afterwards.

By placing it on individual routes, I thought any transition to that route would not cause a change. It would be nice to have some of that granularity as a feature (although not needed in this case).

I'm afraid this would feel very arbitrary and too easy to misuse. It's really about “zones” in your app where scrolling doesn't switch, not individual routes. Route nesting allows us exactly that.

@gaearon When you click a <Link> it renders a new TodoApp with a different filter prop (check full snippet).
I also just put it on GitHub so we can discuss this easier. The only thing that doesn't work in the GitHub version is that you can't refresh or directly visit a filtered url.
Live Demo

As far as I can see, this is your problem: https://github.com/MadLittleMods/react-flux-todomvc/blob/master/js/app.js#L13
Each time you switch filter, you render a different class.
React bails out of reconciliation in this case and throws away the DOM: http://facebook.github.io/react/docs/reconciliation.html#different-node-types
You can probably change it to always use TodoApp and instead tweak render:
run(function (Handler, state) {
        var lastRoute = state.routes[state.routes.length - 1];
	React.render(<Handler filter={lastRoute.name} />, document.getElementById('todoapp'));
})

@gaearon In reality the run callback would have to be a lot more complicated to support the filters that way. This does solve the problem and I have updated the GitHub project with these changes. Looking at previous issues, etc when you could just pass props directly on the <Route>, this would of been much easier. The reasoning for removing was confusion but I think that would be great to add back. I ran into this use case right away.
How are others solving this problem more elegantly?
Link to source
run(function (Handler, state) {
	var filter = TodoConstants.TODO_FILTER_ALL;

	var lastRoute = state.routes[state.routes.length - 1];
	if(lastRoute === 'all') {
		filter = TodoConstants.TODO_FILTER_ALL;
	}
	else if(lastRoute === 'active') {
		filter = TodoConstants.TODO_FILTER_ACTIVE;
	}
	else if(lastRoute === 'completed') {
		filter = TodoConstants.TODO_FILTER_COMPLETED;
	}

	React.render(<Handler filter={filter} />, document.getElementById('todoapp'));
});

My goal: I can change the filter onClick of the link but I want the benefit of the url changing so someone could get back to their exact spot by sharing the url (even without the same tasks).

The reason for removal was that, unlike React normal props, those wouldn't be kept in sync. In fact, there would be no way to update them once set. This confused many people.
Why not use a param instead? Have one route, make filter a route parameter, and pass it as either a prop to Handler (state.params.filter) or read it inside TodoApp from this.getParams().filter using State mixin.

As you can see, you're now doing the rendering, not the router. So we can't just pass something as a prop. You need to do it yourself.

@gaearon Params are good for lots of situations but sometimes having it directly apart of the URL instead of a GET parameter is better.
For example many sites use the same structure I am trying to implement when showing tagged content:
http://stackoverflow.com/questions/tagged/react
http://stackoverflow.com/questions/tagged/javascript

http://www.deviantart.com/tag/valentinesday
http://www.deviantart.com/tag/red

Closing since this original issue is resolved. (And turned out to be unrelated to scroll behaviors.)

Currently the router doesn't manage scroll positions any more. Try https://github.com/taion/react-router-scroll if you stumble upon this issue while finding a solution for your scroll problem.


Bugfix - make 5 photos taken at max

Inside slock.c there are a few ifs where is the logic to take photos from camera, but sometimes it doesnt take 5 photos, other times it takes more..
Please refactor to take it at max 5 photos

https://github.com/andarilhoz/slock-with-lasers/pull/4

@bvbfan thats alright, but, it still taking more or less photos, depending on type velocity

@bvbfan  but, yah, its a start for what i asked (:

do you mean
take photo when someone entered a wrong password
if there are more than 5 wrong attempts, dont take photo

Yes @prprprpony  but, if you type too fast the fswebcam cant take all the pictures, so, sometimes it only takes 1 or 2 pictures instead of 5, maybe it will affect the filename as well (the picture name is based on seconds and not mileseconds)

if someone has already tried more than 5 times, click ESC, and restart entering passwords
do you want to take another round of 5 photos?

@prprprpony no, that would be a easy way to screw the HD xD
the whole purpose of these changes is prevent people from mess with the PC while is blocked, so, if it take endless photos would be a gap
buuut, that could be configurable in the future (: i could open a issue to that, thanks for the idea haha

#5
did this solve the problem?

I'll take a little bit longer to test it ( i have to reinstall linux on my notebook first) but in a few hours i'll test it (:

the problem is that you increase mistakes every keystroke excpet ESC
increase it only after the entered password is checked may solve the problem

@prprprpony i tryed your PR, and didnt take any photo at all :/
the mistakes var is increased 'cause everytime someone types an screenshot without disableing the program (hiting esc 3x) it will take a screenshot

@andarilhoz
I thought what you intended to do was to take photos when someone entered wrong passwords more than 3 times

@prprprpony , sorry, but no, the idea is to take photos to every key hited, unless you hit espace before, i'll update the README to make that clear

But if you key in the right password, you'll still be shot, which doesn't make sense

@prprprpony  after all, i think you are right, i'll just remove the condition where if mistakes was less then 4, cause that would make no sense too (:, thanks for the help, i'll mark this issue as closed


Add container images as children of hosts in details panel

have # containers running that image as a column.
Raised in #752

Fixed in #919


Link to official docs in media plugin is broken.

Link to official docs in media plugin is broken.  Should be:
https://github.com/apache/cordova-plugin-media

Could you include a pull request fixing the docs on this?


Anaconda Jupyter Notebook - Tensorflow ImportError: DLL load failed: The specified module could not be found

Hello Team,
Please see my issue below. I'm working in Jupyter Notebooks launched within Anaconda to work on a computer vision project.
Would it be helpful for me to share all the packages I have in my particular environment just in case there's a conflict that's not immediately obvious? I have 137 in total. I'm a casual user.

System information

Have I written custom code (as opposed to using a stock example script
provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
happens on a mobile device: None
TensorFlow installed from (source or binary): pip install
TensorFlow version (use command below): 2.2.0
Python version: 3.7.7
Bazel version (if compiling from source): Not installed
GCC/Compiler version (if compiling from source): Unsure
CUDA/cuDNN version: unsure
GPU model and memory: Intel(R) HD Graphics 520
Exact command to reproduce: import tensorflow as tf

Describe the problem
I cannot import tensorflow in my jupyter notebook. I have a specific environment created to within Anaconda Navigator to handle computer vision packages
Source code / logs

%pylab notebook
import cv2
import tensorflow as tf
import pytesseract as ptess

ImportError                               Traceback (most recent call last)
~\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow.py in
57
---> 58   from tensorflow.python.pywrap_tensorflow_internal import *
59
~\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py in
27             return _mod
---> 28     _pywrap_tensorflow_internal = swig_import_helper()
29     del swig_import_helper
~\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py in swig_import_helper()
23             try:
---> 24                 _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
25             finally:
~\anaconda3\envs\Tigers Football Image Processin\lib\imp.py in load_module(name, file, filename, details)
241         else:
--> 242             return load_dynamic(name, filename, file)
243     elif type_ == PKG_DIRECTORY:
~\anaconda3\envs\Tigers Football Image Processin\lib\imp.py in load_dynamic(name, path, file)
341             name=name, loader=loader, origin=path)
--> 342         return _load(spec)
343
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
ImportError                               Traceback (most recent call last)
 in
1 import cv2
----> 2 import tensorflow as tf
3 import dlib
4 import pytesseract as ptess
~\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow_init_.py in
39 import sys as _sys
40
---> 41 from tensorflow.python.tools import module_util as _module_util
42 from tensorflow.python.util.lazy_loader import LazyLoader as _LazyLoader
43
~\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python_init_.py in
48 import numpy as np
49
---> 50 from tensorflow.python import pywrap_tensorflow
51
52 # Protocol buffers
~\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow.py in
67 for some common reasons and solutions.  Include the entire stack trace
68 above this error message when asking for help.""" % traceback.format_exc()
---> 69   raise ImportError(msg)
70
71 # pylint: enable=wildcard-import,g-import-not-at-top,unused-import,line-too-long
ImportError: Traceback (most recent call last):
File "C:\Users\jimmy\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\jimmy\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\jimmy\anaconda3\envs\Tigers Football Image Processin\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\jimmy\anaconda3\envs\Tigers Football Image Processin\lib\imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\jimmy\anaconda3\envs\Tigers Football Image Processin\lib\imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.
Thank you,
Jimmy

I'm needing to download CUDA 10.1... Please see the below and let me know which installer type I should go with before downloading?

@JimmyJ2020
This issue is more suitable on Continuum Anaconda repo since its related to TF installation with Anaconda.
Please post it on Continuum Anaconda.
Thanks!
I did come across few issues you could refer to them:
#36986 #35749 link link1 link2  hope these help.


No matching checkpoint file found

你好，我训练时，一直提醒No matching checkpoint file found，请问有没有解决办法。

Hi, it is just normal rather than an error


Rework: Colors

The Colors have to be updated to the following Hex Codes:

Med: #26547c
Nat: #df6d07
InfIngPsy: #a32638
Math: #56aa1c
Beige: #a9a28d

Also, a new Color should be included as default Accent Color (default), the Main Color of Ulm University, which is #7d9aaa.

The Beige Color shouldn't be updated, the current one is a brighter Version of it.


Is the formula scale invariant?

Hello @JasperDekoninck ,
I wonder if the formula is scale invariant. For example, is 2 * M_1 + 1 * M_2 the same as 4 * M_1 + 2 * M_2? From the paper, I suppose it is. However, I wonder if it is true for the implementation. Thank you in advance!

The formula is indeed scale invariant, also in the implementation.
The normalization has to be done to avoid sampling from a distribution with a very high entropy. The normalization can be explained as some kind of temperature discount: if there was no normalization, then sampling from the first formula at temperature 1 / (1+2) would be equivalent to sampling from the second formula with temperature 1/(4+2). Therefore, if you need to have the unnormalized version of your formula, you can simply sample with temperature 3 and temperature 6 from the respective formulas. Note that this would lead to "garbage" output, since this would behave similar to sampling at these high temperatures from "normal" language models.

Got it. Thank you!

Hi @JasperDekoninck I am reading your code in details and I really like it! I have the following questions and I appreciate any help!
Question 1
Given two LLMs $\pi_1$ (M_1) and $\pi_2$ (M_2), Using model arithmetic formula M_1 + 2 * M_2 (and setting temperature = 1 during generation), my understanding (is it correct?) is that the code base implements the LLM $\pi'$ which satisfies
$$\log \pi'(y|x) =\frac{1}{3} \log \pi_1(y|x) + \frac{2}{3}\log \pi_2(y|x) + c(x).$$
I am wondering how to implement the following LLM $\pi$, without the normalization, using the codebase.
$$\log \pi(y|x) = \log \pi_1(y|x) + 2 \log \pi_2(y|x) + c(x)$$
Is the codebase directly applicable? For example, if I still use M_1 + 2 * M_2 but also use temperature = $\frac{1}{3}$ in generate_text, do I obtain $\pi$?
Question 2
Another related question is: My understanding is that when implementing M = M_1 + 2 * M_2, your codebase

Compute logits_1 and logits_2.
Apply log_softmax (with temperature=1) to them and obtain log_prob_1 and log_prob_2.
Compute logit_M = 1/3 * log_prob_1 + 2/3 * log_prob_2.
Apply log_softmax (with temperature=1) to logit_M and obtain log_prob_M.
Apply softmax (with temperature specified in generate_text) to log_prob_M to obtain the sampling distribution for next-token generation.

It seems that my understanding of the code is probably not correct, since it is not consistent with how a single LLM is implemented, where the temperature is applied to logit, not log_prob. I wonder what is the correct pipeline when implementing M = M_1 + 2 * M_2.
Thank you!!

Of course :)
Question 1
You are correct in your understanding that the code returns $\pi'$. As shown in our paper, this normalization is required to obtain the correct solution to the KL-minimization problem. If you want to obtain $\pi$, you should indeed run generate_text with temperature=1/3 (in my previous reply I accidentally claimed the equivalent of having to set temperature=3 in this case, but that was an error). Temperature is essentially an inverse multiplier of the log probabilities, so the results would be the renormalization of $3 \log \pi'$. Note that this is not exactly equal to your $\pi$ since the normalization $c(x)$ will be different between $\pi$ and $\pi'$, but this difference is always necessary to obtain a valid probability distribution.
Note that if you run it with temperature=1/3 you will get the feeling as if you were interacting with a model with a very low temperature (not a lot of variety). The distribution will be a lot more peaked than the individual models (that is why the normalization is useful).
Question 2
They are equivalent! It takes some vector calculus to work this out, but applying the temperature on the logits or the logprobs is equivalent, as long as you renormalize after (which we do). Instead of giving you the proof (which is a bit cumbersome), you can run the following code for some random vector to show that this is indeed the case!
import torch

logits = torch.rand(10)
temperature = 2
print(torch.log_softmax(logits / temperature, 0))
# -> tensor([-2.3891, -2.1712, -2.5899, -2.2133, -2.2057, -2.2683, -2.3315, -2.4400,  -2.1951, -2.2971])
print(torch.log_softmax(torch.log_softmax(logits, 0) / temperature, 0))
# -> tensor([-2.3891, -2.1712, -2.5899, -2.2133, -2.2057, -2.2683, -2.3315, -2.4400,  -2.1951, -2.2971])

@JasperDekoninck  Thank you!
Yep indeed I just realize that, mathematically logprob - logit = a constant vector. Therefore applying softmax using any temperature to both of them will have the same probability distribution. Thank you for pointing it out!


LFS-998: Refactor Variant upload and Somatic Variants form to use a FileResourceQuestion

Jira link
This refactors the somatic variants uploader in LFS to instead use a FileResourceQuestion. This means that people will be allowed to upload files from the SomaticVariants form, but it should otherwise behave the same way as before (besides a few other visual differences).

Clarification: downloading apparently works, but the file you get is the homepage HTML, not the actual file.

@sdumitriu

Bug: downloading the file fails, since the URL to download is wrong.

Fixed in f1a9d60 :heavy_check_mark:

I can attach the csv file in the form, however there is no way to upload it. In the screenshot shown below, I attached a wrong file to the XYZ/LUNG Somatic Variants form.

If we do not want Upload bttn here, we should change the text "Drag & drop or browse files for upload" to "Drag & drop or browse files".
If I do the same in the Variant option, there is an Upload button.

The variants uploader has a separate Upload button since the interaction is more complex: the user has to pick the file(s), adjust the subjects if needed, then Upload so that all the subjects get created and all the files get turned into Forms.
But, when you're editing an actual Somatic Variants form, the file picker is just another answer in the form, so the interaction follows the regular form interaction: pick an answer, then press the big Save button at the bottom. The file gets automatically uploaded since there's no need to adjust and create the subjects (the form's subject is the target), or create a new Form (you're already in one).
The missing Upload button is expected.

I can attach the csv file in the form, however there is no way to upload it. In the screenshot shown below, I attached a wrong file to the XYZ/LUNG Somatic Variants form. Should we prevent this type of action? Should there be an Upload button?

IMO the problem is that there is an upload button on the Variants upload page in a position that is very confusing. LFS-842 should also include moving and relabeling that button (spec changes in progress). Meanwhile this refactoring appears to have been completed successfully and seamlessly, and it did not alter the existing UI of the File Resource Question or the Variant Upload.


Created code to make navigation and access to the Limelight easy

Enabling fast development of advanced autonomous and teleoperated actions through simple helper functions

There are some variables related to system identification in Constants.kt that are not correct. We will need to perform the steps outline here to get these now that we have a gyroscope and encoders.


Instrument mp-rest-client

Resolves #82
The current proposed solution:
All clients are by default traced. Tracing could be disabled via Traced(false) on the client interface or method.
Issues to address:

[x] ~How to disable, enable tracing? Tracing could be enabled by default and disabled if @Traced(false) is present on the interface or vice-versa.  https://github.com/eclipse/microprofile-rest-client/issues/121~ Traced can be applied on interface or method
[x] ~Async integration probably would be leaking as AsyncInvocationInterceptor https://github.com/eclipse/microprofile-rest-client/blob/master/api/src/main/java/org/eclipse/microprofile/rest/client/ext/AsyncInvocationInterceptor.java#L40 does not have a callback to remove applied context. https://github.com/eclipse/microprofile-rest-client/issues/122~ done via AsyncInvocationInterceptor
[ ] Test the client if it is directly injected - without manually interacting with RestClientBuilder (@Inject @RestClient ServiceInterface) - not needed the loading of components (interceptors) should be the same as for manually created client
[x] tests for disabling tracing on method and class.
[x] test when executor service is overridden

SmallRye implementation https://github.com/smallrye/smallrye-opentracing/pull/28
Other links to blocking issues, mostly for testing (SmallRye):

https://github.com/smallrye/smallrye-rest-client/issues/11
https://github.com/smallrye/smallrye-rest-client/issues/6

hi @andymc12 could you please look at the linked issues for mp-rest-client?
https://github.com/eclipse/microprofile-rest-client/issues/122
https://github.com/eclipse/microprofile-rest-client/issues/121
Alternative to these two could be a listener similar to onNewBuilder. But it would be beforeClientCreated(builder, interfaceClass).

In <IP_ADDRESS> the RestClientBuilder is still not automatically instrumented with opentracing, so the called service does not get the span id, thus cannot be correlated in e.g. zipkin.
Is there a target date for this? Is there a mitigation, because mp RestClient is so much more convenient to program.

@fachat that's a question for OpenLiberty vs the specification (as I believe that's what the version you mention refers to).
It is most definitely resolved in the specification, but it's likely OpenLiberty doesn't implement that version yet


software bug: Incomplete sudo permission check

Describe the version
version about:

kubean v0.6.1
kubespray
kubenetes
what CNI and itsversion

Describe the bug
Context from https://github.com/kubean-io/kubean/pull/793/files#diff-9864c355f2595089183328d45da2d99c2b0d6802d78b1d58f8879b1c47aa227dR33.
But there is no sudo group in some OS(like CentOS 7.9).

/kind bug

ACK

fix by https://github.com/kubean-io/kubean/pull/809


MODE-2463 Fixed the logic behind determining the SNS index of session child references.

Looks good.


Share should be FALSE in gradio_web_demo.py

Feature request  / 功能建议
For security you should default the share to false in the gradio_web_demo.py script.
ie
    demo.launch(server_name="<IP_ADDRESS>", server_port=7870, share=False)
Motivation / 动机
Makes it more secure.
Your contribution / 您的贡献
N/A

This is a demo for HF space and it need to set share=True(as default, not set this parm), you can changed it to false for your case


Update improve-accessibility-of-audio-content-with-the-audio-element.…

…chinese.md
I found a word which is translated wrong in Chinese.

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for Hacktoberfest. We believe it does not follow the recommended guidelines:
Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

- PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
- PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
- PRs that are regarded by a project maintainer as a hindrance vs. helping.
- Something that's clearly an attempt to simply +1 your PR count for October.

Last but not least, one PR to fix a typo is fine. 5 PRs to remove a stray whitespace... not.

Learn more at https://hacktoberfest.digitalocean.com/details


Remove unused snippets for eventhub

Please remove these snippets or remove the #region Snippet:<snippet name> or use them in a markdown file.
eventhub: Snippet:EventHubs_ReadMe_ReadPartition
eventhub: Snippet:EventHubs_SamplesCommon_ProducerBasicConfig
eventhub: Snippet:EventHubs_Processor_Sample03_ErrorHandlerExceptionHandling

Thanks for this!    Out of curiosity, how did you mismatch them?

Thanks for this! Out of curiosity, how did you mismatch them?

It's an update to Snippet Generator (and Update-Snippets.ps1) https://github.com/Azure/azure-sdk-for-net/pull/22090


Add debug log level and instrument important internal events

When working on features that involves Session <-> ThreadClient interaction, like #422, I often put multiple puts/pp in different places to see what's happening in the debugger. And then I feel that they're mostly about:

Events being sent from ThreadClient.
Commands being sent to ThreadClient.
ThreadClient's mode change.
ThreadClient's suspend event.

So I figure maybe we can add the debug log level and instrument them in a more uniformed format. I think it'll help ourselves debug issues and also help anyone who's interested in learning the debugger internal. And in some cases, having this information can help us debugging user issues as well.
Example

Let's zoom in to the logs printed after the c command was entered.
DEBUGGER (INFO): leave_subsession
DEBUGGER (DEBUG): #<DBG:TC (sleep)@target.rb:1:in `<main>'> received Cmd { type: :continue, args: [] } from Session
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:1:in `<main>'> changed mode (waiting -> running)
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:1:in `<main>' (not under control)> was suspended for :return
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:20:in `forth_call' (not under control)> changed mode (running -> waiting)
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:20:in `forth_call'> sent Event { type: :suspend, args: [:breakpoint, ["/Users/st0012/projects/debug/target.rb", 20]] } to Session
DEBUGGER (INFO): enter_subsession

You can see that all messages' subject are thread client objects, as most of the "actions" in the debugger happen around them. And the rest of the messages are plainly described in English so it's easy to understand, even for first-time readers.

For the performance aspect, it should use block to skip building the message.
Current format is not clear for me. Messages should be more verbose.

@ko1 I've improved the log messages and it should be clearer now. I also adopted the "block" pattern for debug level helper. But I'm not sure if you'd like this pattern applied to other level's log helpers too?

I meant:
  def debug_loglevel? = @cached_debug_loglevel
  def self.debug msg = nil
    return unless debug_loglevel?

    log :DEBUG, (msg || yield)
  end

and I don't think other log messages do not need to use this technique.

I don't think other log messages do not need to use this technique.

If you mean this should also be applied to other log-levels, it's essentially optimizing the logging mechanism's memory footprint. Perhaps that deserves separate PR?
Also, what do you think about the current format?

Also, what do you think about the current format?

If the "current format" is fowling which on the PR description, I'm ok (and it can be modified easily).
DEBUGGER (INFO): leave_subsession
DEBUGGER (DEBUG): #<DBG:TC (sleep)@target.rb:1:in `<main>'> received Cmd { type: :continue, args: [] } from Session
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:1:in `<main>'> changed mode (waiting -> running)
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:1:in `<main>' (not under control)> was suspended for :return
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:20:in `forth_call' (not under control)> changed mode (running -> waiting)
DEBUGGER (DEBUG): #<DBG:TC (run)@target.rb:20:in `forth_call'> sent Event { type: :suspend, args: [:breakpoint, ["/Users/st0012/projects/debug/target.rb", 20]] } to Session
DEBUGGER (INFO): enter_subsession

This patch doesn't introduce block notation, so I work on it after merging it.

Yes the description contains the updated format.

@ko1 If you think the format is ok, I think it's ready for merge.

I'll merge it after v1.5.0.

@ko1 I happened to need this for debugging issues like https://github.com/ruby/debug/issues/630 as well. Can we merge it? Thx.


Integrating TailwindCss with Flask

Article checklist
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines

This fixes #2237

@hectorkambow I just made a new PR as requested

@hectorkambow This article is good for final review. The author resolved the merge conflicts and the article is good to go.

Thank you v much for your patience as we worked through our Repo re-structuring process.
The purpose behind this restructure - was to better allow us to handle more volume and allow students to publish more articles and get more involved with the community (with open-source contribution and suggestions).
With most of the changes coming to completion - we will be sure to get your article published asap.
Thank you again - and we are looking forward to more amazing articles.

hello, please whats the update on this

Hello @Curiouspaul1 - we were working on clearing out the queue - and should get this one published this week.
Thank you v much for your patience.
Placed the final review label to make sure it does not get overlooked.

@Curiouspaul1
Im sorry Im just noticing - that this PR is not ready to be merged or reviewed.
It has 76 files attached. Your PR should only have the files in your article - I think there was something done incorrectly with the git push/pulls.
cc @katungi
Please be sure to be checking for these type of issues.

@Curiouspaul1
Are you in the Slack channel ?

@Curiouspaul1
Are you in the Slack channel ?

Yes

@Curiouspaul1
Im sorry Im just noticing - that this PR is not ready to be merged or reviewed.
It has 76 files attached. Your PR should only have the files in your article - I think there was something done incorrectly with the git push/pulls.
cc @katungi
Please be sure to be checking for these type of issues.

I fixed this issue the last time and @katungi verified this . My PR only has 16commits

@Curiouspaul1
Im sorry Im just noticing - that this PR is not ready to be merged or reviewed.
It has 76 files attached. Your PR should only have the files in your article - I think there was something done incorrectly with the git push/pulls.
cc @katungi
Please be sure to be checking for these type of issues.

I fixed this issue the last time and @katungi verified this . My PR only has 16commits

I thought so as well - I recall that we did try to fix it.
Not sure why Im still seeing this @Curiouspaul1

Files changed 76. That is the # im looking at.

Again I think the best would be to make a fresh PR - after doing a Git pull on the forked master - create a new branch and include the files for your articles - your author files.
I'll be sure to review it and publish it today - it will not go the back of the queue  - Im trying to get this one published asap.

Hey @Curiouspaul1  , indeed we had the same problem and you fixed it sometime back. I agree with @hectorkambow , just close and make a new PR

okay ..thanks


Remove unnecessary ajax reqeusts

In the hotel search page when the user starts to type a destination name then the application is sending ajax request on every keyup. Which is not the efficient way as the user is not done with typing and the app keeps sending requests on every key pressed.
This can be optimized by using debounce, it will wait a certain time, and group all subsequent requests into one. In our scenario, when the user is typing the destination name and stopped for a certain time(300-500ms) only then it will send an ajax request. This will remove unnecessary API request and provide a better user experiences.
References:

Underscore - http://underscorejs.org/#debounce
Minified version - https://davidwalsh.name/function-debounce
Details - https://github.com/devbridge/jQuery-Autocomplete/issues/475

would be great if you could deliver a ready to use sample :-)

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @kairess, @aoxiong777, @Kuhoerk, @rcovery, @LOGOLFGODORD, @MocaWeb, @MaximKiselev

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @shubhamjw10, @phoenix2014, @naxmefy, @rayanfer32, @terrygm1957, @djgable, @xeanhort

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @qingwg, @coolsnake, @qrks, @mablue, @mguardarini, @icebergyy, @doublelou

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @BjoernSteinmetz, @KrakenAI, @Devilla, @uchitesplavat, @0ze3r0, @WeSpeakCrypto, @Victor-Choe, @furkankadioglu, @andreydang, @kafein, @currankbhatia, @kfivap, @starkindustries, @CapitanAlex, @axifive, @cheehong1229, @himanshubotadra, @haliskilic, @vipxlm, @AdamBouhmad

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
tshwangq, @PuTongjian, @labelexe, @Jann-R, @fastskyz, @kva1966, @dlanileonardo, @vdopython, @pedrodgfaria, @KryptoPolice, @nynevi, @ahmetbilici, @zap0xfce2, @ozturan, @Barca0412, @iamasrar011, @xdvpser, @yyolk, @NoasProject, @kashcode


Feature/66/ms sql

Fixes #66

Code looks good. Waiting for tests.

@paulpalamarchuk and @kopachevsky are there plans to merge this PR to master? We're also wanting to use this module to create SQL instances. Thanks!

@namusyaka Would you mind actually taking this PR over? If you do and fix up the changes you found I can merge quickly.

@morgante no, I'll do it next week.

These commits were merged in #112 . Thanks for your contribution @kopachevsky!


Command line option for using http pipelining

<EMAIL_ADDRESS>commented:

This is an enhancement for enabling http pipelining via a command line option.
patch against 1.6 attached

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #643.
:star2:   2 people had starred this issue at the time of migration.

I don't think this is a priority at all.


Move the config pages and Owen's paper-plugins page around

idk if changing existing urls is a good idea, god knows where they are linked, google doesnt like if you do that etc

I mean, I have correctly set the URL redirect for the one page who’s URL changed

I mean, I have correctly set the URL redirect for the one page who’s URL changed

oh, didnt see that


[Regression] Superscript not shown and duplicate calls even when focus is not present

This issue is fixed and resolution available here - you may refer to know the fix : @ArpithaSrinivas5 @arpithadev


Fixed GPU rendering on Dev

render.GetRenderTarget() returns nil instead of an invalid texture on Dev ( not pre-release yet ) if render target is not being overridden.

Wait so in the current version, render.GetRenderTarget() returns an invalid texture on failure, and in the new version which isn't released yet, it returns nil. if that's the case, why is this change required? In Lua, nil evaluates as false in if statements.

No, the issue here is that since render.GetRenderTarget() now returns nil instead of a invalid texture, self.ScreenRT will also be nil at the time when the render target needs to be reset (Line 179) and render.SetRenderTarget() will not be called. (Line 181)

Relevant issue on why the change was made: https://github.com/Facepunch/garrysmod-issues/issues/3086

oh right yeah nevermind I'm retarded. merging.


Could not build wheels for lxml, which is required to install pyproject.toml-based projects

Could not build wheels for lxml, which is required to install pyproject.toml-based

I have the same error.

@Phishacker I don't know why this error appears. I guess the problem is that Termux incorrectly installs XML. CamOver is not designed to run in Termux though.


Add multi-instance option support globally and per option

This PR continues on the work done in PR #594 and makes the following changes:

Renames the parser setting to AllowMultiInstanceByDefault
Add a per-option AllowMultiInstance option that can be set in the constructor (by default, each option looks at the AllowMultiInstanceByDefault parser setting)
Added 2 additional tests (1 for the AllowMultiInstance option)
Previously enabling AllowMultiInstance(ByDefault) would disable any 'EnforceSingle' check, now it will perform all checks again but at the final step we look at the AllowMultiInstanceByDefault parser setting and the AllowMultiInstance option

Any feedback is welcome.

While I'm not the maintainer, nullable boolean arguments don't fit with the code style. If you really have to have a three-valued bool (true, false, or not specified) for allowMultiInstance in OptionSpecification, I'd suggest using a Maybe<bool> instead and the appropriate Maybe-handling functions from Csharpx, as found in many other parts of the code. But my personal preference would be to just say "not specified = false" and use a regular boolean.

Doing the not specified = false would make it impossible to enable multi instance by default and opt-out per option though.

Ah, right. Then a Maybe<bool> is the right approach here.

Okay, looks like there's a bug in Maybe. The Return function is supposed to always return a Just instance instead of Nothing, but the way it was implemented, you're right that it would turn a false into a Nothing, incorrectly. To work around that, use Maybe.Just instead of Maybe.Return when you know the value should be Just.

I'll see if I can make the requested changes. I'm not the biggest fan of using Maybe for this, but I'll see if I can comply.

@rmunn Hmm, Maybe isn't public so I cannot use this type for the public AllowMultiInstance read-only option on OptionAttribute, should I make that property internal?

If it's a property on OptionAttribute, then it has to be public, since that's what library users will be accessing when they write Option("foo", AllowMultiInstance=false). BTW, I believe it should be a read-write property so that library users can set it on the options, like with the Min and Max properties in BaseAttribute. And yes, perhaps a nullable bool on the allowMultiInstance member of OptionAttribute would fly. For the property, though, I suggest that it should be a simple bool, whose getter should calculate the effective value (based on whether it was set or not, and based on the default setting if it wasn't set) and whose setter should set the member.

AllowMultiInstance cannot be a nullable bool then though (not allowed in attributes).
Making it only set the nullable bool internally on set could work (be it false or true) but only for writing.
For calculating the effective value, you will need the current parser' context to get that setting, not sure how you would feed that info to the option?


No window icon

Godot version
4.0 beta 4
System information
Windows 11
Issue description
No icon displays in the task bar when open godot 4 up or open project

Steps to reproduce
Open Godot.exe or double click a project
Idk
Minimal reproduction project
No response

Can you reproduce this on 3.5.1?

Turned the taskbar modifier off and use Godot 3.5.1

Does it work if you turn off the taskbar modifier and use 4.0.beta4? Does it work if you leave the taskbar modifier enabled and use 3.5.1?

The taskbar modifier doesn't effect the icon I tested both


feat: use updated clair-action/claircore

We have found^1 that the Red Hat VEX^2 data consistently contains the release date information, and the OVAL^3 data consistently does not. Recently^4 claircore introduced the Red Hat VEX updater and the clair-action was updated^5 to use that version.
This updates to clair-action 0.0.9 which updates claircore to 1.5.30 containing the needed Red Hat VEX support.
Resolves: https://issues.redhat.com/browse/EC-835

I'm putting this in draft until we figure out why we're missing some of the vulnerabilities. See https://github.com/quay/claircore/issues/1409

I'm going to put this out of draft. I'd like to see clair-action 0.0.10 release with the update to claircore 1.5.31. This change in particular would be useful for stability purposes, otherwise timeouts might occur when processing Red Hat VEX data. So the workaround here for now is to build and update the version of claircore to 1.5.31.
Other issues of note. With this version I can see different number of vulnerabilities reported for the same image. I'm using quay.io/zregvart_redhat/vuln as an example vulnerable image. It would be good if there were a set of images that we know the expected reported vulnerabilities so we can compare as we make changes here.
I've attached the condensed output of the two different versions (current and proposed here):

v0.0.8-report.txt (current)
v0.0.9-plus-report.txt (proposed here)

I've used the following jq filter to generate those text files:
jq -r '(["ISSUED", "SEVERITY", "NAME", "LINKS"] | (., map(length*"-"))), (.vulnerabilities[] | [.issued, .normalized_severity, .name, .links]) | @tsv'

The differences might be as expected, and it would be nice if they were double checked. For our use case in EC-835 I'm pretty happy that we now have the issue/release/public date present in the output.
There is room for improvement here, I think the clair-action and claircore tend to deal well with incremental updates, it might be a good idea to use the existing clair-in-ci image as a base for the second stage, when the database is updated, so it has access to the previous version of the database. I have not tried this.

Maybe @jencull can do a final review here?

Please let me know if there's anything else needed to have this merged :pray:

Please let me know if there's anything else needed to have this merged 🙏

@lcarva @jsztuka might be the best person for a final once over, in case you need anything else before merging. Returns to work tomorrow, I believe. I will raise it with him.