Unable to build docker image

Thanks for your work on this operator!
I am trying to build the docker image for the operator (on master), using the following command:
docker build https://github.com/GoogleCloudPlatform/spark-on-k8s-operator.git

It fails with the following error:
...
Step 11/18 : RUN go generate && CGO_ENABLED=0 GOOS=linux go build -o /usr/bin/spark-operator
 ---> Running in 633bf25e146b
Generating deepcopy funcs
Generating clientset for sparkoperator.k8s.io:v1alpha1,v1beta1 at github.com/GoogleCloudPlatform/spark-on-k8s-operator/pkg/client/clientset
Generating listers for sparkoperator.k8s.io:v1alpha1,v1beta1 at github.com/GoogleCloudPlatform/spark-on-k8s-operator/pkg/client/listers
Generating informers for sparkoperator.k8s.io:v1alpha1,v1beta1 at github.com/GoogleCloudPlatform/spark-on-k8s-operator/pkg/client/informers
pkg/client/clientset/versioned/scheme/register.go:24:2: cannot find package "github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1alpha1" in any of:
	/go/src/github.com/GoogleCloudPlatform/spark-on-k8s-operator/vendor/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1alpha1 (vendor tree)
	/usr/local/go/src/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1alpha1 (from $GOROOT)
	/go/src/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1alpha1 (from $GOPATH)
pkg/client/clientset/versioned/scheme/register.go:25:2: cannot find package "github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1beta1" in any of:
	/go/src/github.com/GoogleCloudPlatform/spark-on-k8s-operator/vendor/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1beta1 (vendor tree)
	/usr/local/go/src/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1beta1 (from $GOROOT)
	/go/src/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v1beta1 (from $GOPATH)
../../googlecloudplatform/spark-on-k8s-operator/pkg/client/clientset/versioned/typed/sparkoperator.k8s.io/v1alpha1/scheduledsparkapplication.go:26:2: cannot find package "k8s.io/apimachinery/pkg/apis/meta/v1" in any of:
	/usr/local/go/src/k8s.io/apimachinery/pkg/apis/meta/v1 (from $GOROOT)
	/go/src/k8s.io/apimachinery/pkg/apis/meta/v1 (from $GOPATH)
../../googlecloudplatform/spark-on-k8s-operator/pkg/client/clientset/versioned/typed/sparkoperator.k8s.io/v1alpha1/sparkoperator.k8s.io_client.go:26:2: cannot find package "k8s.io/apimachinery/pkg/runtime/serializer" in any of:
	/usr/local/go/src/k8s.io/apimachinery/pkg/runtime/serializer (from $GOROOT)
	/go/src/k8s.io/apimachinery/pkg/runtime/serializer (from $GOPATH)
../../googlecloudplatform/spark-on-k8s-operator/pkg/client/clientset/versioned/typed/sparkoperator.k8s.io/v1alpha1/scheduledsparkapplication.go:27:2: cannot find package "k8s.io/apimachinery/pkg/types" in any of:
	/usr/local/go/src/k8s.io/apimachinery/pkg/types (from $GOROOT)
	/go/src/k8s.io/apimachinery/pkg/types (from $GOPATH)
../../googlecloudplatform/spark-on-k8s-operator/pkg/client/clientset/versioned/typed/sparkoperator.k8s.io/v1alpha1/scheduledsparkapplication.go:28:2: cannot find package "k8s.io/apimachinery/pkg/watch" in any of:
	/usr/local/go/src/k8s.io/apimachinery/pkg/watch (from $GOROOT)
	/go/src/k8s.io/apimachinery/pkg/watch (from $GOPATH)
../../googlecloudplatform/spark-on-k8s-operator/pkg/client/clientset/versioned/typed/sparkoperator.k8s.io/v1alpha1/scheduledsparkapplication.go:29:2: cannot find package "k8s.io/client-go/rest" in any of:
	/usr/local/go/src/k8s.io/client-go/rest (from $GOROOT)
	/go/src/k8s.io/client-go/rest (from $GOPATH)

It seems that the error is related to camel vs lower case, since after running the intermediate image, I found that /go/src/github.com/GoogleCloudPlatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v 1alpha1 exists, but /go/src/github.com/googlecloudplatform/spark-on-k8s-operator/pkg/apis/sparkoperator.k8s.io/v 1alpha1 does not.
Do you know what the fix is for this?

This is a known issue with the code generator. See https://github.com/kubernetes/code-generator/issues/20. Right now the workaround is to discard changes made by code gen to files under pkg/client/clientset/versioned/.

Thanks for the quick response!
I ended up resolving it by adding a sed command in the Dockerfile to fix the capitalization (in between go generate and the go build command):
RUN go generate
RUN find ${GOPATH}/src/github.com/GoogleCloudPlatform/spark-on-k8s-operator/pkg -type f -print0 | xargs -0 sed -i  's/github\.com\/googlecloudplatform\/spark-on-k8s-operator/github\.com\/GoogleCloudPlatform\/spark-on-k8s-operator/g'
RUN CGO_ENABLED=0 GOOS=linux go build -o /usr/bin/spark-operator

Thanks again!

@liyinan926 what about adding comment inside the Dockerfile on this quick fix from @deliahu ?

@deliahu @mrow4a the issue with go generate and container image building has been resolve in #305.

Thanks @liyinan926 for the fix!
I was able to get it working now. I just wanted to let you know that for some reason dep ensure -vendor-only was hanging for me, but I was able to get past it by dropping the -vendor-only


[Autocomplete] Checkbox label inside paper component is causing blur when clicked

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/tender-tree-xzql42?file=/demo.js
Current behavior 😯
I have two elements inside the paper component aside from the options, one is a button and another one is a checkbox. To prevent the autocomplete from triggering blur when the user interacts with these elements, I've called event.preventDefault() on event onMouseDown. Each element is clickable and would not trigger blur but unfortunately, clicking the label of the checkbox causes it to blur.
Expected behavior 🤔
Clicking the checkbox label would just toggle the checkbox checked state and the blur method should not be called.
Context 🔦
What I'm trying to accomplish is I have two sets of options and when I tick the checkbox it would display another set of options. Clicking on whether the checkbox or label should not trigger the blur.

  Output from `npx @mui/envinfo` goes here.

@trronaldbasco This is the expected behavior for the Paper component inside Autocomplete. To achieve your design, you could try customizing the Listbox component instead, it should automatically handle these events.
Here's a working sandbox: https://codesandbox.io/s/https-github-com-mui-material-ui-issues-36619-1fofhq
PS - here's some specific docs about customizing the Autocomplete's inner Listbox: https://mui.com/material-ui/react-autocomplete/#listboxcomponent

@mj12albert that looks good. I did not try the  Listbox knowing that it's the unordered list component and putting other elements inside that aside from li is not semantic, but, that would work.
PS.
tried putting the button and checkbox inside li, it has the same issue tho it is not that consistent.

@trronaldbasco You are right that it breaks the semantics, replacing the Listbox with a div, and then putting a ul around {props.children} could take of that though. (It's not particularly more convenient than manually handling mouseDown on the Paper)

It is still happening. Try clicking the checkbox label.

It could be an issue related to the checkbox itself, I will have a look and may open a separate issue

@mj12albert was there any update on the checkbox side?


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for thunderous-brigadeiros-23902d processing.

Name
Link

🔨 Latest commit
b1ea7f0d75cc81a03cecd1046fec1d3cecfaea41

🔍 Latest deploy log
https://app.netlify.com/sites/thunderous-brigadeiros-23902d/deploys/6331a7154b18bb0008a55c28


Brackets in "if" statement break syntax highlighting

I have the following if-condition:

The syntax highlighting brakes because of the multiple brackets opening and closing
EDIT:
works when adding a space between the two opening brackets:

This bug persists after updating to 1.6.17. I checked it again with the code from the screenshots, same results. Here's the code in text format, so you can copy & paste it and try it out yourself:

    @if(($foo1 == true or $foo2 == true) and $bar == false)

foobar

    @endif


Matrix multiplication on GPU in JAX is 4 times slower than in PyTorch

Description
I originally posted it as a discussion, but now I have a small reproducible example, so re-posting it as a bug.
I test multiplication of 2 matrices on GPU:
import jax
rng = jax.random.PRNGKey(0)
x = jax.random.normal(rng, (8, 4096))
w = jax.random.normal(rng, (4096, 1024))

Also jitted version:
def f(x, w):
    return x @ w

jit_f = jax.jit(f)

And compare it to the PyTorch version:
import torch
import numpy as np
def jax2pt(x):
    return torch.from_numpy(np.asarray(x).copy())

pt_x = jax2pt(x).to(torch.device("cuda"))
pt_w = jax2pt(w).to(torch.device("cuda"))

As expected, normal and jitted versions in JAX perform on the same level. However, PyTorch version is somehow 4 times faster:
In [18]: %timeit (x @ w).block_until_ready()
99.3 µs ± 2.98 µs per loop (mean ± std. dev. of 7 runs, 10,000 loops each)

In [19]: %timeit jit_f(x, w).block_until_ready()
92.9 µs ± 3.32 µs per loop (mean ± std. dev. of 7 runs, 10,000 loops each)

In [20]: %timeit pt_x @ pt_w
24.7 µs ± 2.51 ns per loop (mean ± std. dev. of 7 runs, 10,000 loops each)

I checked that both JAX arrays are on GPU, but as I mentioned in the discussion, the code might be actually executed on CPU.
What jax/jaxlib version are you using?
jax v0.4.20, jaxlib v0.4.20+cuda11.cudnn86, torch v2.1.1
Which accelerator(s) are you using?
GPU
Additional system info?
1.26.2 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] uname_result(system='Linux', node='6ccb2569044d', release='5.15.0-1051-azure', version='#59~20.04.1-Ubuntu SMP Tue Oct 17 16:45:08 UTC 2023', machine='x86_64')
NVIDIA GPU info
NVIDIA A100
Driver Version: 525.147.05
CUDA Version: 12.0
Base Docker image: nvidia/cuda:12.0.1-cudnn8-devel-ubuntu22.04

Screenshot of the profiler:

For a fair comparison, you should wait PyTorch cuda stream as block_until_ready do. So, try to use
%timeit pt_x @ pt_w; torch.cuda.synchronize()

Even though, on my side, JAX is slower than PyTorch by around two times. I guess the reason is either a different kernel or different dispatch cost?

Indeed, synchronization in PyTorch reduces the difference to 2-2.5x:
In [16]: %timeit pt_x @ pt_w; torch.cuda.synchronize()
38.7 µs ± 94.3 ns per loop (mean ± std. dev. of 7 runs, 10,000 loops each)

I don't think it's caused by different dispatch because in the larger model the difference in execution speed is even more striking (see the linked discussion).
Regarding kernel, I assume you are talking about different CUDA kernels. Is there a way in JAX to use a different kernel?

Regarding your linked discussion, my "rule of thumb" is to wrap all your computation inside jax.jit (e.g., during training, the forward/backward/gradient update are typically all fused in one jit call). Without jit, JAX is undoubtly slower than PyTorch. But from my experience, when jit is properly used, JAX is typically 2x to 1000x faster than PyTorch (obvious for small but complex models, due to reduced dispatch cost and fusion).
I suspect that the problem revealed in this issue is different from that in your discussion (simply caused by missing jit).

And you are right! Setup with a more complex function:
def f(x, w):
    w = w / w.std()      # .std() for better stability
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    x = x @ w / x.std()
    return x

jit_f = jax.jit(f)

x = jax.random.normal(rng, (128, 4096))
w = jax.random.normal(rng, (4096, 4096))
pt_x = jax2pt(x).to(torch.device("cuda"))
pt_w = jax2pt(w).to(torch.device("cuda"))

Test:
In [1]: %timeit f(pt_x, pt_w); torch.cuda.synchronize()
4.68 ms ± 1.96 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

In [2]: %timeit f(x, w).block_until_ready()
3.46 ms ± 279 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

In [3]: %timeit jit_f(x, w).block_until_ready()
1.51 ms ± 1.32 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

Thanks for clarification!


Make brotli-size optional by styfle

Description

Remove brotli-size from dependencies
Add try-catch around require('brotli-size')
Warn if using brotli option but missing brotli-size

Motivation and Context
It turns out the brotli-size (#194) is quite big and doesn't install very nicely on Windows.
See the following issues:
Fixes #202
Fixes #213

@siddharthkp: I currently have downgraded bundlesize to 0.15. This should be squashed and merged ASAP.
Node.js 10.0.0 is out for quite some time.

@styfle Do you think the build should error out instead of passing if brotli-size is not installed?

@siddharthkp That's a good point since they specifically said they wanted to use brotli. Maybe the correct thing to do is fail fast and just throw instead of a warning:
throw new Error('Missing optional dependency. Install it with: npm install --save brotli-size')

Thoughts?

I agree with you guys
Requesting to check the size based on brotli compression and getting an OK return code seems wrong

@siddharthkp Ok the build is failing as expected now that there is a throw.
How should we fix the tests so that brotli-size is installed? Add to devDependencies?

how about running it once and checking for failure and then running npm i brotli-size and running again and check for success?

@eseliger That was my first thought but I don't see a test harness so I'm not sure how to assert that and error was thrown with the current test commands.

hmm maybe some script like this will work
bundlezise

if [ $? -eq 0 ]
then
  echo "Should have failed"
  exit 1
else
  exit 0
fi

Hey, guys. Any news? I'm still using a downgraded version due to no node.js 10.x support.

I this @siddharthkp still wanted to make a change here.
Another related issue worth pursuing is to get brotli support in Node Core.
Put a 👍 on this issue: https://github.com/nodejs/node/issues/18964

@siddharthkp: friendly ping!

Is the package abandoned @siddharthkp ?


Problem with deciphering.

Hey everyone, I need your help.
I overwrited all bytes to AA in whole trailer block 7 in sector 1 and I can't decipher it anymore.
Is there any option to make this sector work again? I really appreciate every advice.

maybe duplicate, let focus on  #234


Excuse me, does Coral support the conversion of Hive UDF?

I would like to inquire about the solution used to achieve Presto's compatibility with Hive UDF？
I tried the following example from the source code:
Sorry, I didn't look carefully. I got the answer: Additionally, it integrates with Transport UDFs to enable translation and executing user defined functions (UDFs) across Hive, Trino, Spark, and Pig

Sorry, I didn't look carefully. I got the answer: Additionally, it integrates with Transport UDFs to enable translation and executing user defined functions (UDFs) across Hive, Trino, Spark, and Pig


[mapping] Evaluate possibility of label mappings

Implemented in 0.7. This allows for sophisticated reconciling.


fix: outbound listener handle error response string

- What I did
- How I did it
- How to verify it
- Description for the changelog

Please add a couple of unit tests

Sure Gary. I have to introduce unit test for outbound message listener.
Currently facing an issue in end2end test but they are passing in my local.
error response in local run which has the fix on local server.
plookup verb response error:{"errorCode":"AT0015","errorDescription":"key not found : Exception: public:no-key@alice does not exist in keystore"}
error response in github actions ( I guess trunk version of server is used)
plookup verb response error:{"errorCode":"AT0011","errorDescription":"Internal server exception : Request to remote secondary @cicd5 at null:null received error response 'AT0015-Exception: public:no-key@cicd5 does not exist in keystore'"}


Add row param to solr queries for exports

We have noticed that collection and work type exports seemed to be limited to 10 even with a form limit of 0 or blank. The ActiveFedora::SolrService.query method uses the solr default limit of 10 unless the rows parameter is used, so I added a rows parameter with a value close to the maximum allowed integer value.

@smithjp codewise this looks great - Rubocop and Rspec are both failing. If you have a moment to fix those up, I'd appreciate it, if not, just let me know and I'd be happy to pull the branch down and do it. Either is good for me, I just don't want to step on your code ;-)

Sorry about that!  I'll fix the errors.


Drop Scala 2.12, update sbt-typelevel to 0.5.0-RC1

About this PR
📦 Updates

org.typelevel:sbt-typelevel
org.typelevel:sbt-typelevel-site

from 0.5.0-M10 to 0.5.0-RC1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: sbt-plugin-update, early-semver-pre-release, semver-spec-pre-release, version-scheme:early-semver, commit-count:n:2

This has run afoul of Scala 2.12.  Do we still need it?  We could add collection-compat, perhaps.

Superseded by #198.


assertion failure in async-coap/src/datagram/send_future.rs:275

handle_response() should only be called when self.state().is_waiting() == true.

In my environment, I can observe, that sometimes UDP response from coap.me/separate arrives several times. As I can see with Wireshark, in cases local endpoint receives 2 or even 3 similar looking CoAP messages with same token.
In such a case, the first one is handled properly, but when the subsequent one, reaches handle_response(), the assertion fails.

It looks like the UDP ResponseTracer does not remove "old" tokens when a response is matched on a token, and not on message-id. Problematic code is located around async-coap/src/datagram/response_tracker.rs:81.

It is generally acceptable to receive several response messages with the same token. Indeed, this ability is required to receive multiple multicast responses and for observing... But clearly there is still a bug here.
You are right that the handler should be removed from the tracker, but this shouldn't be assumed by the tracker—remove_response_handler needs to be called by the SendFuture when it is finished. In the existing code, that happens on line 475 of send_future.rs:
https://github.com/google/rust-async-coap/blob/master/async-coap/src/datagram/send_future.rs#L474-L476
But this clearly isn't good enough, as evidenced by you hitting the assert.
So I see two options:

Instead of asserting if we aren't waiting, just return Err(Error::Unspecified) or Err(Error::Reset). The idea here is that we are trusting that drop() will eventually be called on the future and clean things up properly then.
Somehow ensure that remove_response_handler gets called earlier.

#2 might seem like the ideal solution, but if we just do this naively (like calling it directly on the state transition) we deadlock because the mutex is already being held.
Perhaps the best solution would be to add a boolean return value to the method HandleResponse::handle_response that indicates if the handler can handle additional packets or not. Then we could check that return value and remove the entries directly from UdpResponseTracker::handle_response implementation.
Thoughts?

I will take a deeper look next days and reply with my thoughts. This week I've been away and had almost no time to work. :(

Sorry for the long silence. I agree that the second option is better. Will make a prototype and update the pull request.

The pull request is updated, according to the second option.

sorry for the delay. Having a look at the new changes.


angular-fusejs is not in the npm registry

Hi guy, i really interested in this and wanna to use it for my project.
But I can not install it from npm  ... and get 404 error here, please check it
Thanks so much!

Please fix it!

Probably too late, but done


Attempted fix at dependabot not seeing dependencies

As the title says, turns out gradle is difficult for depandabot

Might cause issues with the linting PR if I merge this first, but I'll fix that once that comes up.


[turbopack] Error resolving server relative import: not implemented yet

What version of Turborepo are you using?
Next: 13.4.2
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Mac
Describe the Bug

Expected Behavior
Relative imports to work
To Reproduce
Import an asset using relative import (/public/ prefix shouldn't be necessary according to Next docs, but that's a different issue)
Reproduction Repo
No response

Hi @panieldark, this appears to be a turbopack issue. I'll relabel it accordingly

Got it, thanks!

Hi @panieldark! Importing from /public/… directly isn't supported:
import foo from "/public/foo.png"

Instead, you'll need to use the actual path to the thing you're trying to import, eg "../public/foo.png" (or the appropriate number of ../s). Alternatively, you can configure TypeScript's compilerOptions.paths to alias an import of "public/foo.png" (notice that there's no leading /).
When we discussed this with the Next.js team, they expressed that this was an unintentional "feature" and isn't actually supposed to work by default. Instead, they recommend doing one of the above suggestions. The benefit of this is that if follows the conventions in the larger ecosystem, which is quickly adopting TS's paths, package.json's imports field, and import maps in general.

Good to know! Although, it seems a bit unexpected--Next.js use without turbopack allows for base imports (it's also in their docs, although I'm not in front of a computer at the moment). Since it's available in one, would love if it was consistent across the other!

The Static Assets page is specifically referencing the src property of an <img /> (or <NextImage /> component), or a background: url("…") inside of a CSS file. In both cases, this doesn't mean to actually import the file into the JS module graph, but to point the asset when it is served from a server.
When using the import foo from "/public/…" import syntax, you're telling the bundler that this asset is actually part of the JS module graph, and it has to be turned into a JS object that can be manipulated.
I've added this feedback to our internal issue tracker as WEB-363

I have a similar issue using the @ardatan/sync-fetch  + graphql-tools/url-loader packages if you have any suggestions on how to fix.
`error - [resolve]
node_modules/@ardatan/sync-fetch
Error resolving server relative import: not implemented yet
unable to resolve server relative<EMAIL_ADDRESS><EMAIL_ADDRESS>node_modules/@ardatan/sync-fetch/index.js:41:10  Error resolving commonjs request
37 |   }
38 | }
39 |
40 | function sendMessage (message) {
|           v-----------------------------------------------------------
41 +   return exec(process.execPath, [path.join(__dirname, 'worker.js')], {
42 +     windowsHide: true,
43 +     maxBuffer: Infinity,
44 +     input: JSON.stringify(message),
45 +     shell: false
46 +   }).toString()
+-----^
47 | }
48 |
49 | function extractContentType (input) {
50 |   const request = new _fetch.Request(...input)
unable to resolve server relative<EMAIL_ADDRESS>or dynamic

<EMAIL_ADDRESS>node_modules/@graphql-mesh/utils/esm/defaultImportFn.js:3:24  Error resolving EcmaScript Modules request
1 | import { path as pathModule } from '@graphql-mesh/cross-helpers';
2 | async function defaultImportFn(path) {
|                         v-----------------------------
3 +     let module = await import(/* @vite-ignore */ path)
4 +         .catch(e => {
+-
5 |         if (e.code === 'ERR_REQUIRE_ESM') {
6 |             // eslint-disable-next-line no-new-func
7 |             return new Function(return import(${JSON.stringify(path)}))();
8 |         }
unable to resolve dynamic

<EMAIL_ADDRESS>node_modules/@graphql-tools/url-loader/esm/index.js:11:37  Error resolving EcmaScript Modules request
7 | import { defaultSyncFetch } from './defaultSyncFetch.js';
8 | import { buildGraphQLWSExecutor } from '@graphql-tools/executor-graphql-ws';
9 | import { buildHTTPExecutor, isLiveQueryOperationDefinitionNode, } from '@graphql-tools/executor-http';
10 | import { buildWSLegacyExecutor } from '@graphql-tools/executor-legacy-ws';
+                                      v---------------------v
11 + const asyncImport = (moduleName) => import(${moduleName});
+                                      ^---------------------^
12 | const syncImport = (moduleName) => require(${moduleName});
13 | export var SubscriptionProtocol;
14 | (function (SubscriptionProtocol) {
15 |     SubscriptionProtocol["WS"] = "WS";
unable to resolve dynamic

node_modules/@graphql-tools/url-loader/esm/index.js:12:36  Error resolving commonjs request
     8 | import { buildGraphQLWSExecutor } from '@graphql-tools/executor-graphql-ws';
     9 | import { buildHTTPExecutor, isLiveQueryOperationDefinitionNode, } from '@graphql-tools/executor-http';
    10 | import { buildWSLegacyExecutor } from '@graphql-tools/executor-legacy-ws';
    11 | const asyncImport = (moduleName) => import(`${moduleName}`);
       +                                     v----------------------v
    12 + const syncImport = (moduleName) => require(`${moduleName}`);
       +                                     ^----------------------^
    13 | export var SubscriptionProtocol;
    14 | (function (SubscriptionProtocol) {
    15 |     SubscriptionProtocol["WS"] = "WS";
    16 |     /**

unable to resolve dynamic

node_modules/node-gyp-build/node-gyp-build.js
node_modules/node-gyp-build/node-gyp-build.js:22:10  Error resolving commonjs request
18 |
19 | module.exports = load
20 |
21 | function load (dir) {
|           v-------------------------------
22 +   return runtimeRequire(load.resolve(dir))
23 + }
+-
24 |
25 | load.resolve = load.path = function (dir) {
26 |   dir = path.resolve(dir || '.')
27 |
unable to resolve dynamic`


Cover last test/material tests with leak tracking.

Description
This PR changes testWidgets by testWidgetsWithLeakTracking in number of flutter/test/material tests according to the https://github.com/dart-lang/leak_tracker/issues/134.
Tests

Updates material/input_date_picker_form_field_test.dart to use testWidgetsWithLeakTracking;
Updates material/search_test.dart to use testWidgetsWithLeakTracking;
Updates material/search_view_theme_test.dart to use testWidgetsWithLeakTracking;
Updates material/time_picker_theme_test.dart to use testWidgetsWithLeakTracking;
Updates material/tooltip_test.dart to use testWidgetsWithLeakTracking.

Pre-launch Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[X] I signed the [CLA].
[X] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is [test-exempt].
[X] All existing and new tests are passing.

cc @polina-c

@polina-c thanks a lot for the review!


added a responsive footer

Title and Issue number

Title :Added a responsive footer
Checklist:

[] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md
[] I have updated the Index.html file for my contribution

hey ! review my pr and add the hacktoberfest-accepted label


feat: add v4 license model and utility services

see https://gravitee.atlassian.net/browse/APIM-1685
BREAKING CHANGE: checking for feature enablement now relies on the NodeLicenseService

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 4.0.0-feat-v4-license-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 4.0.0-alpha.1 :tada:
The release is available on:

4.0.0-alpha.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Memory offset wraparound is not correct

With ds = 0, mov word [0xffff], 0xbeef should write bytes 0x0ffff and 0x00000: the offset should wrap around but not propagate its carry.  Instead it writes 0x0ffff and 0x10000.
To fix this, I think one needs to change inc_addr to take a segment and offset, instead of just a linear address.

Hey, it seems correct and incorrect at the same time for me :sweat_smile:
In some sense, it feels more correct to wrap the offset and not the final address, but in some other it feels correct to do the other way. I tried checking the manual, and can't find the description of addressing modes for this case at the  moment. Give me some time to think on this.
Also, if you know a reliable place where the addressing is described properly, can you share that?

The 8086 User's Manual does say on page 2-12:

Note that this addition process provides for modulo 64k addressing (addresses wrap around from the end of a segment to the beginning of the same segment).

That maybe doesn't directly address wraparound within one instruction, but I'm also looking at the 80386 Programmer's Reference Manual.  On page 14-6, discussing differences between 8086 and 80386, it says:

On the 8086, an attempt to access a memory operand that crosses offset 65,535 (e.g., MOV a word to offset 65,535) or offset 0 (e.g., PUSH a word when SP = 1) causes the offset to wrap around modulo 65,536.

In that case it should be indeed implemented that way.
Can you link both of the manuals in your comment (just so we have a ref)?
Thanks!


New files for pysimCoder

Summary
Files under board/arm/stm32f7/nucleo-144
f746-pysim/defconfig
include/board.h
src/nucleo-144.h
src/stm32_appinitialize.c
src//stm32_bringup.c
src/stm32_gpio.c
Configuration for a testing system with:
4 DI
4 DO
2 encoders
2 PWM + complementary channel
4 ADC
LAN
Impact
STM32F7 nucleo-144 board
Testing

I can't find out why the Build / macOS (macos) failed... The logs don't give any usable (for me) information...

I can't find out why the Build / macOS (macos) failed... The logs don't give any usable (for me) information...

it isn't your problem, some unknown reason trigger the server cancel macOS build, let's ignore this false alarm and merge your change.


vioinput high DPI mouse rubberbanding

I find this issue hard to describe so I made a video to demonstrate.
Essentially, with my mouse set to 1600 DPI, when I move it quickly enough, the mouse will "rubber band" left and right, instead of moving only rightward.

Host running Arch with Wayland/SwayWM
My mouse is a Zowie EC2-A and it is set to 1600 DPI / 500hz polling
In the video I set the Windows mouse sensitivity to the lowest it can go to more clearly demonstrate the issue

I've tried several configurations, and this only happens when I am using the virtio device with evdev, so I believe it is related to this driver.

It isn't happening on the host environment
It does not happen if I pass through the USB device itself

changing the libvirt input from "mouse" to "tablet" fixes the mouse movement (but breaks mouse clicks etc being in absolute movement mode)

Thank you for the report. If I understand correctly the device is able to work with different DPI settings. Several questions:

How exactly you set the mouse resolution? With which resolution setting the mouse works as expected?
Can you please provide 'evtest' output (supported events and properties) for this event device when it is in high DPI mode (will not work correctly) and in other mode(will work correctly)?
What is qemu command line parameters related to the input device? What is the diff between 'libvirt' input 'mouse' and 'tablet'?
Thanks

there's been a new development. I can set the mouse to different polling rates. as you lower the polling rate, the problem becomes more easily reproducible, and I can reproduce at the lowest DPI. at the highest polling rate, it becomes more difficult to reproduce, and is only reproducible at higher mouse speed on higher DPIs.
here's a totally subjective table of the speed of mouse movement required for reproducibility. n/r means not reproducible, i.e. I couldn't make move my arm fast enough to do it.

125hz
500hz
1000hz

400 dpi
high
n/r
n/r

800 dpi
medium
high
n/r

1600 dpi
low
medium
high

3200 dpi
lowest
low
medium

The mouse has a button on the bottom that changes DPI, with 400/800/1600/3200 options.
I chose to do the two extremes for evtest:

400 dpi @ 1000hz being the most difficult/impossible to reproduce
3200 dpi @ 125hz being the easiest to reproduce

This is how I can reproduce it:-device virtio-mouse-pci,id=input2,bus=pci.0,addr=0xb \
-object input-linux,id=mouse1,evdev=/dev/input/by-id/usb-Kingsis_Peripherals_ZOWIE_Gaming_mouse-event-mouse \

and I noticed that movement when defining it as a tablet does not reproduce in any case:-device virtio-tablet-pci,id=input2,bus=pci.0,addr=0xb \
-object input-linux,id=mouse1,evdev=/dev/input/by-id/usb-Kingsis_Peripherals_ZOWIE_Gaming_mouse-event-mouse \

I also tried adding an entry to local HWDB as described here and saw no change in behavior.
~ λ udevadm info /dev/input/event3 | grep MOUSE_DPI
E: MOUSE_DPI=400@500 800@500 1600@500 3200@500

I know basically nothing about mouse drivers, libinput or evdev. however, given the large differences in event values in the output I am seeing, and the sort of "oscillating" behavior of the mouse when it is happening, this feels like some kind of overflow error.

@tristanpemble Can you please provide the output of 'evtest /dev/input/event3'?

yep I provided in above:
https://gist.github.com/tristanpemble/ec1c7de47a4dded0575c65f2a33aeb05
https://gist.github.com/tristanpemble/6ba718017abb06acfa96029e7650bbc6

yes, I believe the values are overflowing at this typecast to UCHAR

Hey I just want to jump in on this thread and comment I ran into the same issue, and @tristanpemble DPI to polling rate table seemed to line up with my results as well

win8-64-fixed.zip
Finally getting to it (better than never)
Please confirm the attached driver solves the problem (test mode required to install it, i.e. "bcdedit /set testsigning on" + reboot)

the fix was released in build 175, please reopen if needed

I would like to ask for a re-open. The current fix is simply clamping the input, but the correct solution would not lose the relative input information. The implementation should probably generate multiple HID events (with some sane upper limit) for such an overflow case.
Since UCHAR is windows-specific (HID) limitation, I think doing it on hypervisor/libinput level would not be quite right.


feat: Tenth import [SOURCES]

Summary:
Fixes #71: First data import
This PR adds the tenth part of first data import for the GTFS Schedule sources in the catalogs.
Changes:

The GTFS Schedule Sources catalog is extended with 50 new sources.

Expected behavior:
Same as before but with more sources.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with pytest to make sure you didn't break anything
[x] Format the title like "" (for example - "Check for null value before using field")
[x] Linked all relevant issues
[ ] ~Include screenshot(s) showing how this pull request works and fixes the issue(s)~

Fixed in #101, closing the PR.


Bump Prometheus client to v1.11.0

What this PR does / why we need it:
I've checked it doesn't have any kind of negative impact on PipeCD.

https://github.com/prometheus/client_golang/releases
https://github.com/protocolbuffers/protobuf-go/releases

Also, I've checked that metrics exposing goes well locally.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Should we seperate protobuf version update with this prometheous version update PR. 👀

Truthfully, I want to do so, but go mod tidy doesn't allow us it.

@khanhtc1202 Where are you now? Sent your comment from Hokaido? 😄

Nice.
It looks fine for other updates as well.
/approve

@khanhtc1202 Where are you now? Sent your comment from Hokaido? 😄

yeh, I'm super bored in a running bus near by Sapporo 🙈

@khanhtc1202 Where are you now? Sent your comment from Hokaido? 😄

Seriously? 🙄

@khanhtc1202 Where are you now? Sent your comment from Hokaido? 😄

Seriously? 🙄

yep 🙌


chore: vertx-cloud-events to 1.0.10

chore: Promote vertx-cloud-events to version 1.0.10

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

Needs approval from an approver in each of these files:

OWNERS

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


Building in Visual Studio using cmake fails

I tried building OpenEXR using Visual Studio (both 2019 and 2022), by following these guidelines in the VS documentation about bulding CMake-based projects: https://docs.microsoft.com/en-us/cpp/build/cmake-projects-in-visual-studio?view=msvc-170
Both VS2019 and VS2022 gave me the same error:
C:\Users\ivanl\Projects\OpenEXR\out\build\x64-Debug\ninja : error : 'zlib-install/lib/zlibstatic.lib', needed by 'bin/OpenEXR-3_2_d.dll', missing and no known rule to make it

We haven't tested Visual Studio's cmake integration as described in that link, but we always test building OpenEXR for Windows with Visual Studio from an x64 tools command prompt, using cmake. Perhaps start there and first verify you are able to build OpenEXR in the supported manner. After that, if you are able to determine why the build doesn't work when trying to use the VS cmake IDE integration, perhaps we can discuss solutions to make it work.

I have since managed to build OpenEXR by using CMake-gui to run their VS solution generator, then opening the generated solution and building the generated BUILD_ALL and INSTALL projects. I was initially confused about what the cmake in the INSTALL instructions for Windows meant and so my intuition led me to google "Visual Studio cmake" and arrive at the VS docs linked in OP. Perhaps the INSTALL instructions could be more detailed in describing how exactly cmake is supposed to be used with VS in a way that OpenEXR supports for people like me who are not familiar with the usual cmake conventions.

Glad to hear you got a build, and a workflow that works. Your suggestion to improve the build documentation is a good one.


Add regressor prefix to columns generated by TimeFlagsTransform

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

Related Issue
#124.
Closing issues
Closes #124.

Codecov Report

Merging #126 (6303d53) into master (9d4f55f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #126   +/-   ##
=======================================
  Coverage   88.03%   88.04%
=======================================
  Files          55       55
  Lines        2541     2543    +2
=======================================
+ Hits         2237     2239    +2
  Misses        304      304

Impacted Files
Coverage Δ

etna/transforms/datetime_flags.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Contradicting bazel versions suggested

URL(s) with the issue:
https://www.tensorflow.org/install/source_windows#install_bazel
Description of issue (what needs changing):
It should be Bazel <0.23.0, not 0.24.1
Clear description
First and last sentence contradict each other:
Install Bazel 0.24.1,
Ensure you install Bazel 0.23.0 or lower.
Correct links
Parameters defined
Returns defined
Raises listed and defined
Usage example
Request visuals, if applicable
Submit a pull request?
No

@gadagashwini This issue seems to have been fixed and can be closed. Bazel 0.24.1 or greater is required and is correctly mentioned on the site.
Could I be added as a collaborator on this project? Then I'll be able to self assign tasks and do much more. Thanks.

@boraca  Proceeding to close this issue as its resolved


Create project logo

Jade:
This was an idea I found for the logo. Any thoughts on this?

Jon
It looks great. You should add it to the project if you want.


Doctest example code in haddocks

Closing this because it doesn't seem like doctest supports this functionality. I don't want the example code to be run; just type checked. It would also be nice if I could inline a snippet of code from the example program instead, but it doesn't seem like this can be done.
Closing for now, but it would be nice to revisit this in the future.


Spring Cloud Vault with Spring Cloud Config

I'd like to know if it's possible to use spring cloud vault with the dependency
spring-cloud-starter-vault-config and spring-cloud-config-client
I mean I've been trying to use Kubernetes service account with vault and spring cloud-config, but when I activated the cloud-config I have an error because the header X-Vault-Token doesn't arrive to spring cloud-config. I want to know if it's possible to work as you work with the token vault when you sent from the client and config server sent to vault.
Client dependency
spring-cloud-config-client.
spring-cloud-starter-vault-config.

It's possible to combine both, but each component will have their own authentication scope. The only way to reuse the same token is to specify a token externally.

The thing is that when I active the server config and vault the authentication with Kubernetes doesn't arrive at the server config,  I got the next exception on the  server config
m.m.a.ExceptionHandlerExceptionResolver : Resolved [java.lang.IllegalArgumentException: Missing required header: X-Config-Token]
But if I use the token authentication works normally.
https://cloud.spring.io/spring-cloud-vault/reference/html/#vault.config.authentication.kubernetes

That is by design.
If you have Spring Cloud Vault on your class path, then what's the point to additionally propagate the authentication to Config server using Vault? You have access to Vault anyway so you can fetch the secrets directly without Config server.

Ok  I thought so thanks @mp911de


AssociatedModelMetadataProvider can get confused when dealing with properties eclipsed via the "new" operator

https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.ModelBinding/Metadata/AssociatedMetadataProvider.cs#L120
When dealing with a property that is hidden via new, the property info shows up twice, once for the base type and once for the new property. They are looked up by name, and consequently, we could end up setting the property on the base type rather than the new one.
Super edgy case, but might be worth tracking

Addressed by acb657d9


Makes start services idempotent

ocd run https://ocd.appscale.com:8080/job/Daily Build/982/

precise OCD run https://ocd.appscale.com:8080/job/Daily Build/993/

Previous OCD ran out of resources: OCD https://ocd.appscale.com:8080/job/Daily Build/995/


Refs #12690 -- Removed unneeded BaseSpatialOperations.truncate_params

Unless a regression test is missing, things seem to now work on Oracle without this.
Original commit: 474ce51ffd9e7f0963d666bdb429f00b04cdaee3

buildbot, test on oracle.

This removal is incorporated in https://github.com/django/django/pull/6493.


add the list and cancel database operations

add the list and cancel database operations under 2017-03-01-preview, there's no issue in autorest validation

@jiawang003,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@ravbhatnagar new APIs

Other than that it looks fine.

@sergey-shandar Swapping this with you since I took the other one, let me know if that doesn't work for you 😉


Update merge_sort.md

Added Java implementation of Merge Sort Algorithm

The document structure got distorted please fix them

Yes, fixed them.


How do require.resolve and require in dependencies work with our Webpack configuration?

Passing string paths to dependencies that use require.resolve() or require()
I'm having a recurring issue with various dependencies that use require.resolve() or require() to resolve string paths. I believe there is a mismatch in assumptions between our Webpack config and the requires in dependencies.
I'm wondering:

Is there a config change I can make in our Webpack to make these dependencies work?
OR
Is there a tweak to code in the dependencies that makes them play nicely with Electron projects that use our Wepback setup?

The problematic dependencies have a similar pattern: They ask me to provide a string file path, then they turn around and use the string file path to call require.resolve() or require() and things don't work as expected.
Here's what's happening in one case:
I'm trying to use the electron-remote repo to automatically run code in worker renderer processes.
Code in my renderer that uses electron-remote:
    // This code is in app/components/Home/index.jsx
    // Renderer task pool (electron-remote)
    const backendPath = require.resolve('../../backend/index');
    // Should resolve to app/backend/index.js
    log.info(`backendPath is ${backendPath}`);
    const backend = requireTaskPool(backendPath);
    backend.work()
      .then(result => {
        log.info('Done doing work, time elapsed is ${result.timeElapsed}');
      });

Error in console:
[21:02:59.269] backendPath is ./app/backend/index.js
Uncaught Error: Cannot find module './app/backend/index.js'
 at Module._resolveFilename (module.js:470)
at Function.Module._resolveFilename (/Users/ben/code/tesla/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/comm…:35)
at Function.resolve (internal/module.js:27)
at /Users/ben/code/tesla/app/node_modules/electron-remote/lib/renderer-require.js:26

The corresponding code in electron-remote: https://github.com/electron-userland/electron-remote/blob/master/src/renderer-require.js#L44
let fullPath = require.resolve(modulePath);

(this line is identical after being run through Webpack)
My assumptions:

The dependency uses require.resolve() because it's assuming that Node.js is the environment.
The authors of electron-remote (i.e. Slack) don't use Webpack, because they're okay with writing require.resolve.
It seems that require.resolve() is a Node.js API that is for whatever reason incompatible with Webpack. See this thread..
Other libraries do a similar thing:

node-migrate, which accepts a string path that is meant to identify an ES6 module for a migration, tries to require dynamically. See this thread.mod = require(path.join(migrationsDirectory, file))

Error: Uncaught Error: Cannot find module "."

I'm pretty confused about the nuanced conflicts in how Node.js does requires, how Webpack does them, how Babel does them, and how dependencies we may use utilize them.
Are my assumptions off? Am I missing something basic about the requires or file paths? How can we get electron-remote or node-migrate working with this project? Any help of feedback on this problem would be greatly appreciated.
Also, the real problem I'm trying to solve is to create an extra renderer process that can do work without tying up the main process or renderer process. If there are any dependencies you know work "out of the box" with this repo to solve that problem, I'd happily switch to "whatever works".
Thanks for the time you spend helping people by publishing this project.

I got electron-remote working with electron-react-boilerplate in a basic way here: https://github.com/aguynamedben/electron-react-boilerplate/pull/1
This depends on a change to electron-remote that gets rid of the usage of requires.resolve(): https://github.com/electron-userland/electron-remote/pull/42
From what I can tell, the comment here nails the root cause: https://github.com/webpack/webpack/issues/1554#issuecomment-158679844

This doesn't work.
require.resolve returns the module identifier according to CommonJS. In node.js this is the filename. In webpack this is a number.

From what I can tell, any Electron/Node.js dependency that uses require.resolve() is going to have this problem, and the only fix or workaround is to get the dependency to get rid of all their require.resolve(). :(
Has anybody run into this issue before?


Reference change in log.debug?

We want to encapsulate log.debug with additional functionality, but for the reference seems to change, which breaks our code:
const ref = log.debug;
console.log(ref===log.debug); // true
log.debug("Hello World");
// some more logging
console.log(ref===log.debug); // false

Is this intended functionality and a wrong assumption to make that the reference stays the same? Or must there be some other issue in our code?
We are using loglevel 1.6.1 in the browser.

Can you put together a standalone reproduction so I can see this in action? It'd also be useful if you could be more specific about which browser you're using when you see this - a https://www.whatsmybrowser.org/ link would be perfect.
For now, using just the code above I can't seem to reproduce this. Skimming the code, the only time that calling log.debug would ever change the definition of log.debug is if console wasn't defined initially. That's designed to handle issues in IE (either old IE, or newer IE with compatibility modes set badly), and if you're not using IE I don't think this should ever happen.
One way you could see this effect is if you're calling setLevel between the two checks. Calling setLevel does redefine every log method, either creating it afresh or replacing it with a no-op, depending on the level selected.

The browser is Firefox 67, the link is www.whatsmybrowser.org/b/S9N79PS. We do indeed use setLevel, I will investigate whether this solves the problem.

Yes, setLevel was indeed the problem, that solved it, thanks!

Great to hear, glad I could help! :+1:


Ignoring documents if not present

Is your feature request related to a problem? Please describe.
I have a boilerplate setup for my projects and codegen is a part of it. But when you start a new project codegen errors cause it is not able to find any gql files which makes sense, but I would like to silently ignore it and proceed with the remaining part of type generation.

Also, typedDocumentNode results in error when compiling if there are no operations since the import import { TypedDocumentNode as DocumentNode } from '@graphql-typed-document-node/core'; exists but there are no operations which use the import as I am yet to write the operations:

Both the errors are valid cause there are no gql files in the specific directories which I typically add as and when I work on new operations. But, is there any way to ignore it and let the codegen generate types for the operations when they are available?
As of now, I am commenting out the documents statement in the codegen yaml file for every new service that I create and then uncommenting it when I have my new operation ready.
Describe the solution you'd like
Ability to silently ignore this error if no gql files/documents are present and then start generating types for them when they are available and only generating import statements if they are being used.
Describe alternatives you've considered
Commenting out the line in yaml till I have new operations.

Hi @tvvignesh !
I think the best way to go is to remove documents section from your boilerplate.
The reason we are throwing an error is because loading documents is not so simple- it might comes from a simple .graphql file, but there are cases we are extracting it from .js files as AST, or require file and look for exports. That's why it's important for us to notify the user that something is wrong with the configuration.
Regarding typed-document-node - I can apply a fix to remove the import in case there a are no operations, if that helps.

@dotansimha Makes sense. Just asking though, can't the error level be warning rather than terminating the codegen. That way, the user will still be notified but the codegen will still work even if there are no documents. I may be wrong, but if people prefer the codegen to fail on not finding documents, then maybe that can be a config.
Regarding typed-document-node - Please take your own time. I know you have a lot of priorities.

This could work. @ardatan maybe this is related to graphql-tools as well. I think the exception is originally coming from there.
What do you think?
Btw, I fixed the issue with in typed-document-node here: https://github.com/dotansimha/graphql-code-generator/pull/5035

@tvvignesh the fixed i mentioned above is available in<EMAIL_ADDRESS>

Awesome. Will try it out now.


Custom app name.

Hi,
It is a great tool! Thanks for creating it! I would like to request that it works with app name different than 'app'. My app named differently and I get the error message below. However, when I rename my app to app (I'll get a lot of error message due to broken module dependencies) but the graph is working.
"Uncaught Error: [$injector:nomod] Module 'app' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument."

Hi Sayusi.
Thank you. Are you bootstraping your app manually? ie. with angular.bootstrap(...)? It should work for any app name as long as you use "ng-app" tag somewhere. I'll fix it for apps that are bootstraped manualy

No, I do not do any bootstrapping. I'll create a simple app and put it into a git repo in the a next a few days.

Do you use 'ng-app' tag then somewhere?

I have this in my index.html:
Doesn't matter whether I use data-ng-app or ng-app
<!DOCTYPE html>

    <title>Digital Library</title>
    <meta charset="utf-8" />

my app.js file
(function () {
    'use strict';

    angular.module('dilib', [
        // Angular modules
        'ngAnimate',
        'ngRoute',

        // Custom modules
        'dilib.layout',

        // 3rd Party Modules
        'LocalStorageModule',

    ])

do you load app.js asynchronously after all files are loaded by any chance? Do you use any AMD, like RequireJS? I used a bit naive approach to load modules, releasing patch soon.
Thanks for feedback!

Thanks for dealing with this issue!
No, just angular. But, here is the current index.html file:
<!DOCTYPE html>

    <title>Digital Library</title>
    <meta charset="utf-8" />

Woops... I forgot about x- and data- prefixes. If you want a quick fix, you can use ng-app instead of data-ng-app now, this will be fixed in next release 0.2.5.

Ok 0.2.5 is just being published in web store. Hope it works well!

Nice, nice, and nice! Thanks for the fix! :)


Retrieve CAPI/CAPA from release image

What this PR does / why we need it:
Retrieves the CAPI and CAPA image components from the release image rather than registry.ci.openshift.org/hypershift/cluster-api:v1.0.0 and registry.ci.openshift.org/hypershift/cluster-api-aws-controller:v1.1.0 respectively
Which issue(s) this PR fixes:
Fixes HOSTEDCP-577
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

This change is causing a huge number of GETs from the hypershift-operator
=== RUN   TestEtcdChaos/EnsureAPIBudget/hypershift-operator_read
    util.go:604: over budget: budget: 5000, actual: 100247

This change is causing a huge number of GETs from the hypershift-operator
=== RUN   TestEtcdChaos/EnsureAPIBudget/hypershift-operator_read
    util.go:604: over budget: budget: 5000, actual: 100247

I think this might be due to the change I made in order to delete the AWS machine sets. I'll try reworking that and see if that resolves the problem.

@bryan-cox let's move forward with and ship this:

This change seems to have come from https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/2271. Specifically from the changes in machine.go in UseSecretsManager and the changes in awsmachine_controller.go in reconcileDelete.

Can you share logs from capa you are having when trying to delete the secret before the awsMachine?
Let's address https://github.com/openshift/hypershift/pull/1826#discussion_r1009210462
then should be good to go.

@bryan-cox let's move forward with and ship this:

This change seems to have come from kubernetes-sigs/cluster-api-provider-aws#2271. Specifically from the changes in machine.go in UseSecretsManager and the changes in awsmachine_controller.go in reconcileDelete.

Can you share logs from capa you are having when trying to delete the secret before the awsMachine?
Let's address #1826 (comment) then should be good to go.
Orthogonally kubernetes-sigs/cluster-api-provider-aws#3805

Ok I think I've addressed  #1826 (comment)
I included a snippet of the error log messages in here

Dropped 2 more nits.
This is great, thanks @bryan-cox!
/approve
will ship after https://github.com/openshift/hypershift/pull/1868

/test e2e-aws

/test e2e-aws

This seems to be failing consistently @bryan-cox, did you have the chance to test it?

/test e2e-aws

/test e2e-aws

This PR keeps failing leaking resources, have you seen it working locally?
Can you please bump the timeout for the PR here https://github.com/openshift/hypershift/blob/9878207a11d99c2280f438d85e85311b7b90ae94/test/e2e/util/fixture.go#L290
If that still fails then failure is legit.

/lgtm

/test e2e-aws

The job that tests ocm-2.6 (ocp 4.11) is still trying to use registry.ci.openshift.org/hypershift/cluster-api:v1.0.0.
For some reason, the above image no longer exists (since Jan 25)
/cherry-pick release-4.11


review-1: Fix the code based on the suggestions from teammates (https://github.com/manoa-inspire/MATP/issues/65)

feedback at https://github.com/manoa-inspire/MATP/issues/65
Make sure to pull from main first and make a separate branch instead of working on the reivew-1 branch.


Godot Mac - freezes after open any projects

Tested versions
stable 4.2
Stable 4.1x
System information
Godot v4.2.stable - macOS 14.0.0 - Vulkan (Mobile) - integrated Intel(R) Iris(TM) Plus Graphics - Intel(R) Core(TM) i7-1060NG7 CPU @ 1.20GHz (8 Threads)
Issue description
after downloading Mac Binars from the official source, after launching the Godot app, a window for selecting a project will open. If the project exists, just open any project or create a new one. Then the editor will open and godot will stop responding to any imputation to the editor.
The godot editor process does not freeze, but it does not react to strange input from the keyboard or mouse.
Default lang was selected [SK] Slovak after clean first start by app.
Steps to reproduce
clean install / create new project
in project window is as default lang [SK] slovak
after open any project or create one and open editor stop responding or accept any input.
The godot editor process does not freeze, but it does not react to  input from the keyboard or mouse.
this happened always when godot is opened.
when is editor terminated and godot reopen select lang [EN] English and problem is resolved , you can open project , after restart is posible to select again SK and all is ok
Default lang was selected [SK] Slovak after clean first start by app.
Solution to workaround : in the introductory window where the project is selected because the project is created it is necessary to select - switch to ENGLISH if ENGLISH is not selected as the language of the editor, with the language Slovak in my casegodot stops responding after selecting the project.
then the problem was fixed and it is possible to select SK Slovak again and the editor responds correctly
Minimal reproduction project (MRP)
clean install / create new project
in project window is as default lang [SK] slovak
after open any project or create one and open editor stop responding or accept any input.
when is editor terminated and godot reopen select lang [EN] English and problem is resolved , you can open project , after restart is posible to select again SK and all is ok

Same here, happens also on English
2023-12-09 14:43:34.166 Godot[58610:22553444] WARNING: Secure coding is automatically enabled for restorable state! However, not on all supported macOS versions of this application. Opt-in to secure coding explicitly by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState:.
Godot Engine v4.2.stable.official.46dc27791 - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
Using "default" pen tablet driver...
OpenGL debugging not supported!
Shader 'CanvasSdfShaderGLES3' SHA256: 8f59e1abc53821dc71f55825dd994e9106dfc38d5442f7d55b04888345944576
Shader 'SkeletonShaderGLES3' SHA256: 16dfad218510b4d2e3fe46356e03b52b19127542a763e0cb2b9d217b5a268fe2
Shader 'ParticlesShaderGLES3' SHA256: 45d3bcde954be91e8fa34d0456acd2e586cdfd780c61f2b9d068ba89f6a749e8
Shader 'ParticlesCopyShaderGLES3' SHA256: cc791fe902fa71b56d0ecadc0e083d85b6c8600bb53c3d9762b973ae82e45333
Shader 'CopyShaderGLES3' SHA256: b1699bc68b041170f99dc83ea34cde3c9efdca0f4c973f8120e974c0ddbba0e6
Shader 'CanvasShaderGLES3' SHA256: fc509a8e90df0e551157cd3c44ab7901be0a9b6436a42ab199be246a9b6020c3
Shader 'CanvasOcclusionShaderGLES3' SHA256: e8ee82476cb438df9fea1666640aca7f2ac718dd5d359b6e0060a8b3aa064d56
Shader 'SceneShaderGLES3' SHA256: 8186d06a877b5a7f2898d7e2d7d1f32c072b29bb2ac913993876f73b57b62a46
Shader 'SkyShaderGLES3' SHA256: c9c1821bdc417b6054796496cc265508f492ac1b35d5b623e6066b3f2db2b372
Shader 'CubemapFilterShaderGLES3' SHA256: 6d89c63ff4861b6707bf8064906c7bcf69683361ad111c8262a8fa0b549855d3
OpenGL API 4.1 Metal - 88 - Compatibility - Using Device: Apple - Apple M1 Pro
CoreAudio: detected 2 channels
CoreAudio: audio buffer frames: 512 calculated latency: 11ms

TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
2023-12-09 14:43:34.596 Godot[58610:22553444] WARNING: AVCaptureDeviceTypeExternal is deprecated for Continuity Cameras. Please use AVCaptureDeviceTypeContinuityCamera and add NSCameraUseContinuityCameraDeviceType to your Info.plist.
CameraServer: Registered camera FaceTime HD Camera with ID 1 and position 0 at index 0
CameraServer: Registered camera Meyer’s iPhone Camera with ID 2 and position 0 at index 1
CORE API HASH:<PHONE_NUMBER>
EDITOR API HASH:<PHONE_NUMBER>
EditorSettings: Load OK!
Loaded system CA certificates
EditorSettings: Save OK!
Editing project: /Users/fm/src/game/test3
EditorSettings: Save OK!
XR: Clearing primary interface
XR: Removed interface "Native mobile"
XR: Removed interface "OpenXR"

The Project Manager window freezes for me the moment I open a project.  Godot fires up with the project, but the project manager is stuck and the beach ball of death appears the moment I hover over the Project Manager.

Happening for me on 4.2 mono with an M1 pro - I'm not seeing anything notable in the Console.

Same problem here with 4.2.1 on an M1 Pro MacBook Pro.

Same problem here with 4.2.1 on an M1 Pro MacBook Pro.

Fixed it by opening Xcode and letting it update.

Same problem here with 4.2.1 on an M1 Pro MacBook Pro.

Fixed it by opening Xcode and letting it update.

I had the same issue. Opening XCode and then re-opening the Godot project seemed to have resolved it.

Same problem here with 4.2.1 on an M1 Pro MacBook Pro.

Fixed it by opening Xcode and letting it update.

Also solved for me. Thanks for sharing!

same here, has this issue been solved for Mac ?


RuTracker: add year

Year is not added intentionally as it's not reliable on RuTracker.

Year is not added intentionally as it's not reliable on RuTracker.

Can you elaborate a bit, please?

They don't follow imdb's years standard so it's not reliable  to search by imdb's year.


Eyedropper color picker not working with XWayland

Tested versions

This bug is doable on every version since at least 4.0 as long as you're on wayland linux
Tested on Fedora, Arch, Debian, multiple different computers too

System information
Godot v4.2.1.stable - Fedora Linux 39 (Workstation Edition) - Wayland - Vulkan (Forward+) - integrated Intel(R) UHD Graphics 620 (WHL GT2) () - Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz (8 Threads)
Issue description
When trying to chose a color with the eyedropper, it immediately goes black and starts pumping out error messages
platform/linuxbsd/x11/display_server_x11.cpp:1108 - Unhandled XServer error: BadMatch (invalid parameter attributes)
Major opcode of failed request: 73
Serial number of failed request: 0
Current serial number in output stream: 41303
I am not knowledgeable enough to know if this is a Xwayland or a Godot problem
Steps to reproduce
Try to chose a color with the eyedropper on wayland linux
Screencast from 2024-02-19 14-20-16.webm
Minimal reproduction project (MRP)
This is a global issue and doesn't need a MRP

I wonder a little bit of why it doesn't happen with 3.x?
Maybe X11 display on 3.x is simple enough that XWayland can cover it all?

ColorPicker in 3.x reads from the editor window by queriying the viewport data, without relying on any OS-specific API. The upside is that this works regardless of sandboxing, but it won't work outside the editor window.
I guess we need to bring back the 3.x ColorPicker eyedropper as a fallback when using OS APIs isn't feasible due to sandboxing.

We seem to be on a similar distro, but I get a slightly different problematic behavior that I already commented about here.

Trying to use this does effectively crash my pc like @eobet has said. Hopefully it can be disabled on incompatible platforms or the old picker has a fallback.

i use 4.3 on nixos hyprland 0.42 has same problem, but my hypr has no response. it seems like hibernate


PWA-334 e2e productpage

Pull Request Test Coverage Report for Build 715

4 of 60 (6.67%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 33.633%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pages/Product/components/VariantSelects/index.jsx
1
2
50.0%

pages/Product/components/Options/index.jsx
1
2
50.0%

e2e/integration/ProductPage.js
0
54
0.0%

Totals

Change from base Build 713:
-0.4%

Covered Lines:
1254

Relevant Lines:
3644

💛  - Coveralls


Rampart Certificates are Invalidated.

We need to change the certificates in rampart module to have longer validity periods. Invalidated certificates cause build failures with the following exception.
org.apache.ws.security.WSSecurityException: The signature or decryption was invalid (The provided certificate is invalid); nested exception is:
        java.security.cert.CertificateExpiredException: NotAfter: Tue Mar 20 05:29:59 IST 2018
        at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:509)
        at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:124)
        at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:332)
        at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:249)
        at org.apache.rampart.RampartEngine.process(RampartEngine.java:217)
        at org.apache.rampart.RampartEngineTest.testValidSOAP12Message(RampartEngineTest.java:118)
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Tue Mar 20 05:29:59 IST 2018
        at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
        at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
        at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
        at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:506)
        ... 27 more

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Draw LTN cells as outlines, not areas with confusing colors

The LTN tool's cell coloring makes it extremely obvious when a filter successfully splits a cell into two pieces:
https://user-images.githubusercontent.com/1664407/163010928-fb201f67-e6ed-4cfb-a950-eb948d2ee6be.mp4
But the colors are an accessibility nightmare (and previous attempts to pick better ones haven't worked so far), the coloring is probably too visually dominant, and worst of all -- the colors themselves are meaningless. Above you'll see multiple yellow and purple cells. There's no significance; we're just drawing adjacent cells with different colors, and reusing a handful of colors. This is definitely confusing.
This PR attempts to calm things down and show cell outlines only, without any extra color:
https://user-images.githubusercontent.com/1664407/163011365-98401226-caf6-410e-bcda-02fc6b0334f4.mp4
But the grey/black lines (I was trying to create a drop shadow effect) feels too weak to me. This diagram found online strikes, IMO, a better balance:

But I've yet to make that work with the basemap's styling.
I'm also toying around with drawing the cell outlines as dashed lines, to emphasize that "disconnected" idea.
@dingaaling, @XaranDeBruregor -- thoughts?

Here's dashed outlines, done in the most horrible way possible. Maybe this could work, with different color / thickness / etc?
https://user-images.githubusercontent.com/1664407/163013062-0f3030e2-8306-4d17-b4ae-9fb2a30f83e5.mp4

I agree with you that the example you found of the boundary outlines in different colors might be the best compromise! Because otherwise, in the 1st change you've made it's hard to even notice the boundaries


Some tensors share memory, this will lead to duplicate memory on disk and potential differences when loading them again: [{'pretrained_model.base_model.model.lm_head.weight', 'pretrained_model.base_model.model.transformer.output_layer.weight'}].

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
WANDB_DISABLED=1 NCCL_P2P_DISABLE=1 NCCL_IB_DISABLE=1 deepspeed --num_gpus 2 --master_port=9527 /workspace/projects/LLaMA-Factory/src/train_bash.py
--stage rm
--do_train
--deepspeed xxxxxxxx/ds_z3_offload_config.json
--model_name_or_path xxxxxxx/chatglm3-6b
--adapter_name_or_path /xxx/chatglm_exp_sft_lora_llamafactory
--create_new_adapter
--dataset comparison_gpt4_zh
--dataset_dir xxx/data
--template chatglm3
--finetuning_type lora
--lora_target query_key_value
--output_dir xxx/chatglm_exp_rm_lora_llamafactory
--overwrite_cache
--overwrite_output_dir
--cutoff_len 1024
--preprocessing_num_workers 4
--per_device_train_batch_size 2
--per_device_eval_batch_size 1
--gradient_accumulation_steps 4
--lr_scheduler_type cosine
--logging_steps 10
--warmup_steps 20
--save_steps 10
--eval_steps 20
--evaluation_strategy steps
--learning_rate 1e-5
--num_train_epochs 2.0
--max_samples 5000
--val_size 0.1
--plot_loss
--fp16
可以正常训练，但是保存checkpoint时候提示如下错误：
[INFO|trainer.py:3305] 2024-04-23 16:56:46,579 >> Saving model checkpoint to /workspace/models/huggingface/chatglm32k_rm_sft_lora_llamafactory/checkpoint-10
[INFO|trainer.py:3319] 2024-04-23 16:56:46,587 >> Trainer.model is not a PreTrainedModel, only saving its state dict.
Traceback (most recent call last):
File "/workspace/projects/LLaMA-Factory/src/train_bash.py", line 14, in
main()
File "/workspace/projects/LLaMA-Factory/src/train_bash.py", line 5, in main
run_exp()
File "/workspace/projects/LLaMA-Factory/src/llmtuner/train/tuner.py", line 35, in run_exp
run_rm(model_args, data_args, training_args, finetuning_args, callbacks)
File "/workspace/projects/LLaMA-Factory/src/llmtuner/train/rm/workflow.py", line 50, in run_rm
train_result = trainer.train(resume_from_checkpoint=training_args.resume_from_checkpoint)
File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 1859, in train
return inner_training_loop(
File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 2278, in _inner_training_loop
self._maybe_log_save_evaluate(tr_loss, grad_norm, model, trial, epoch, ignore_keys_for_eval)
File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 2673, in _maybe_log_save_evaluate
self._save_checkpoint(model, trial, metrics=metrics)
File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 2752, in _save_checkpoint
self.save_model(output_dir, _internal_call=True)
File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 3239, in save_model
self._save(output_dir, state_dict=state_dict)
File "/opt/conda/lib/python3.10/site-packages/transformers/trainer.py", line 3321, in _save
safetensors.torch.save_file(
File "/opt/conda/lib/python3.10/site-packages/safetensors/torch.py", line 284, in save_file
serialize_file(_flatten(tensors), filename, metadata=metadata)
File "/opt/conda/lib/python3.10/site-packages/safetensors/torch.py", line 480, in _flatten
raise RuntimeError(
RuntimeError:
Some tensors share memory, this will lead to duplicate memory on disk and potential differences when loading them again: [{'pretrained_model.base_model.model.lm_head.weight', 'pretrained_model.base_model.model.transformer.output_layer.weight'}].
A potential way to correctly save your model is to use save_model.
More information at https://huggingface.co/docs/safetensors/torch_shared_tensors
Expected behavior
能够保存rm的checkpoints并顺利完成训练
System Info
Copy-and-paste the text below in your GitHub issue and FILL OUT the two last points.

transformers version: 4.40.0
Platform: Linux-5.15.0-101-generic-x86_64-with-glibc2.31
Python version: 3.10.11
Huggingface_hub version: 0.22.2
Safetensors version: 0.4.3
Accelerate version: 0.29.3
Accelerate config:    not found
PyTorch version (GPU?): 2.0.1 (True)
Tensorflow version (GPU?): not installed (NA)
Flax version (CPU?/GPU?/TPU?): not installed (NA)
Jax version: not installed
JaxLib version: not installed
Using GPU in script?:
Using distributed or parallel set-up in script?:

Others
无

--save_safetensors False

谢谢，有效。但是有资料提示 这样做就没办法利用 safetensor的有点
Looking at the code I see there's a workaround to set save_safetensors=False. Seems to work, but then we lose whatever benefits safetensors are supposed to give us.

有资料显示可以通过保存之前clone tensor 解决，不知道 这种方式在我们这个场景下是否合适。

你好，--save_safetensors False设置后保存的模型如何进行模型加载并推理

上网查了一下好像是transformers的问题，不知道更新有没有用，我也遇到了https://discuss.huggingface.co/t/saving-model-in-safetensors-format-through-trainer-fails-for-gemma-2-due-to-shared-tensors/109451


Setup Github Actions workflow to deploy vaadin-flow-sockjs classifiers

Setup a workflow that builld vaadin-flow-sockjs jar for specific Vaadin versions and deploy them to a public remote repository.
To build and deploy we can use the existing script build_flow_widgetsets.sh in tools directory.
Remote repository may be JFrog, since JCenter and Bintray will no more work after May 2021.
The workflow may be scheduled once per week, but it should also be possible to launch it manually.

Is there a reason to use a script? I tried this 1 hour ago in my fork and deploy it to GitHub packages. But it fails because it can't find the parent pom. I'm not familiar with CircleCI, is there anything to consider?

A ./mvnw -N install must be launched before the script in order to install the parent pom.
The script performs the following tasks:

check the Vaadin version in use from the root pom (property vaadin.platform.version)
get the list of "compatible" Vaadin version by querying search.maven.org
for each Vaadin version detect the corresponding flow-client version
for each distinct *flow-clienté version build and deploy vaadin-flow-sockjs artifact with a classifier reflecting Vaadin version

If you have a better solution in mind, I'll be glad to discuss and potentially refactor the process.

I was trying it with a maven docker image. I haven't known, that the maven wrapper is doing some more stuff.
I can't find the script which describes your workflow, can you supply a ref?
For the moment I don't have another workflow in mind. I think your workflow has been proven as stable.

Perhaps we had a misunderstanding: I was talking about the script build_flow_widgetsets.sh in the tools directory, not about maven wrapper.
The ./mvnw -N install command should be launche before ./tools/build_flow_widgetsets.sh because the script only build the vaadin-flow-sockjs module

BTW I added a workflow on spikes/github-actions branch,if you want to have a look and give some advice.

Ah ok, this was the file I was skipping, cause I thought that there is nothing important. I will take a look again.
I saw the branch, there are just tests at the moment?

Yes, I'm doing some workflow test on that branch, and it seems to work as expected.
I will then squash and merge the changes into vaadin-18 branch, scheduling the workflow once a week.
If all works fine next step will be porting the workflow on all other release branches

Sounds great 👍

Scheduled workflow is running every night for test. If no problems arise the schedule will change to run once a week.

The build_flow_widgetsets.sh has been improved to only build classifiers not yet deployed on JFrog; this means that the workflow can have a daily schedule, since most of times it will complete in short time without building anything.

This is even better. This allows updating one day after an update is published.

Is it right to name it build_flow_widgetsets.sh, even if there are actually no widget sets anymore?

The widgetset (here intended as GWT compiled resources) is already present, but it is limited to the communication stack.
I'm going to close this issue since the workflow seem to work correctly


feat(core): add the --watch-files arg to the devCommand

Summary
support devCommand specify the configuration files to listen to restart the dev server.
Related Links
https://github.com/web-infra-dev/rsbuild/discussions/3021

Checklist

[x] Tests updated (or not required).
[x] Documentation updated (or not required).

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

This CLI option has the same name as dev.watchFiles but has different functionality.
I tend to look for other more reasonable solutions, such as automatically analyzing the modules that rsbuild.config.ts depends on and watching them.

This CLI option has the same name as dev.watchFiles but has different functionality.
I tend to look for other more reasonable solutions, such as automatically analyzing the modules that rsbuild.config.ts depends on and watching them.

I've found three possible ways to make it a plugin for rsbuild, a plugin for rspack, or a built-in feature for rspack, can you give me some advice, please?

Do you mean analyzing the module graph via a custom plugin?

Do you mean analyzing the module graph via a custom plugin?

Yes,but I don't know if that's possible, I hope to get your guidance🙏

I think this could be a feature that @rsbuild/core has built-in support for, but we need to understand how other frameworks implement it first.


Assemblytics output to vcf

Hi,
Thank you so much for your effort to maintain this wonderful software.
I'd like to ask how to use ID for SURVIVOR option.
My goal is to convert Assemblytics output (bed) to a vcf file for SURVIVOR_ant, then use SURVIVOR_ant to annotate my structural variation. So, first I tried ./SURVIVOR bedtovcf assemblytics.output.bed DEL output.vcf to convert bed to vcf, but it changed all variant types into deletion. I tried ALL, All, all, etc., but it showed
Bed file
Type
Output vcf file
repeatedly. I would be grateful if you added other explanations how to use it properly, which part should I change, or what Type I can use, etc.
Second, I tried to use ./SURVIVOR ID, so I replaced ID to the number 11: Convert SV calls from Assemblytics: ./SURVIVOR 11 However, it didn't show any informative error message, but showed the same message with typing ./SURVIVOR. Could you explain how to use ./SURVIVOR properly?
Yours sincerely,
Thank you.
Jun.

Hi Jun,
thanks I have just added the Assemblytics parser to the new interface. The IDs are currently not lift over. I can work on that if you need that.
Please clone the code and compile.
Cheers
Fritz

Sorry I answered just one of you questions. I am behind on documentation, but I changed the interface recently to have less options and to have a similar interface like samtools and other methods.
So if you type:
`
./SURVIVOR convertAssemblytics
`
now shows you the 3 parameter that are necessary.

It worked really well. Thank you so much! I appreciate it.


Error in swift 3.0

im using swift 3.0 Xcode 8.0
i have an Error:
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

Please elaborate on the error by using the provided issue template. I can't help anybody without being able to reproduce the issue...

Is this still an issue?

I don't believe it is.  If you are using the current version, then Xcode automatically wants to update CVCalendar to Swift 3.  The code is already updated for Swift 3 though.  Once you do Edit > Convert... then you can build the project when added with CocoaPods.

@bdparrish Thank you for letting me know. It's weird because I just checked did a clean setup with the pod and haven't had that problem. Anyway, seems to be resolved -> closed.


FEAT: create gpu feature on dashboard

create gpu usage and gpu memory usage column on xorbits web dashboard.

Previously, the dashboard of our websites only showing the CPU and usage and CPU memory usage. However, the CPU memory usage is actually calculating the sum of GPU and CPU memory usage. This update distinguishes the CPU and GPU memory usage and adds the GPU information on dashboard. Now the dashboard will display CPU usage, CPU memory usage, GPU usage, and GPU memory usage.

Check code requirements

[ ] tests added / passed (if needed)
[ ] Ensure all linting tests pass

Can you please attach some screenshots on this pull request to let us see the frontend changes?

Regarding GPU information, do you think it would be best if we don't display it when users are using the UI on a machine without a GPU card? What do you think?

After running 3 times of print(np.sort(np.random.rand(100_000_000, gpu=True))):
The usage have been changed:

I believe if users don't have to GPU, then our backend code will return an default value which should represents that their gpu usage is dummy, which should not be too misleading.

Most recent update on May 31st:
Update and fix the Workers and Supervisor -> resources page on the dashboard. Here are the result running with GPU available machine:

Latest update on June 1st:
Resolved the multiple GPU cases:
When the user uses machines with more than 1 GPU, our website will always support every display reflecting every GPU resource usage. Here are the results:
When running with Machine in Hangzhou HQ with 2 GPU cards present, after calling xorbits.init()

And then calling:
import xorbits.numpy as np
a = np.random.randint(100, size=1000000, chunk_size=100000, gpu=True)
print(a)
The GPU displays indicate the changes in usage as shown below:

The results should verify that now our website will support multiple GPU cases.

Please add some screenshots for this case: There are two GPUs  on the machine, but user only uses one of them.
xorbits.init(cuda_devices=[1])

Please add some screenshots for this case: There are two GPUs on the machine, but user only uses one of them. xorbits.init(cuda_devices=[1])

When running with only the "second" GPU (1 means the second in GPU) in the init process, the backend still transfers all the GPU information to the front end.
Yet when we run further computations as below:
In [5]: import xorbits.numpy as np
In [6]: a = np.random.randint(100, size=1000000, chunk_size=100000, gpu=True)
In [7]: a
Only the GPU-1 usage shows differences, which is exactly the indicated GPU in our cases. The results are shown below:

Please add some screenshots for this case: There are two GPUs on the machine, but user only uses one of them. xorbits.init(cuda_devices=[1])

When running with only the "second" GPU (1 means the second in GPU) in the init process, the only GPU shows up now, regardless of there are 2 GPU in the machines, is GPU-1, the one we indicated:
When we run further computations as below:
In [5]: import xorbits.numpy as np In [6]: a = np.random.randint(100, size=1000000, chunk_size=100000, gpu=True) In [7]: a
the results shown like this:
The supervisor page remains shows every GPU available for users, regardless of users using or not. The results are here. NOTICE that when user want to only use GPU-1, the GPU-1 is still the only one to be modified.

Supervisor never uses GPU. So I think GPU-related info can be only showed on Worker page. What do you think?

Please add some screenshots for this case: There are two GPUs on the machine, but user only uses one of them. xorbits.init(cuda_devices=[1])

When running with only the "second" GPU (1 means the second in GPU) in the init process, the only GPU shows up now, regardless of there are 2 GPU in the machines, is GPU-1, the one we indicated:
When we run further computations as below:
In [5]: import xorbits.numpy as np In [6]: a = np.random.randint(100, size=1000000, chunk_size=100000, gpu=True) In [7]: a
the results shown like this:
The supervisor page remains shows every GPU available for users, regardless of users using or not. The results are here. NOTICE that when user want to only use GPU-1, the GPU-1 is still the only one to be modified.

Supervisor never uses GPU. So I think GPU-related info can be only showed on Worker page. What do you think?

Updated in the newest version:
This is the results running on AWS machine with simple GPU presents.

GPU usage shows what data? Based on screenshots, it has been 0 all the time.

GPU usage shows what data? Based on screenshots, it has been 0 all the time.

It seems like it will never turn to 1 until GPU is fully used. The data conveys from the backend always shows 0. I believe it may be a minor issue on the backend that deserves a new issue addressing it!

GPU usage shows what data? Based on screenshots, it has been 0 all the time.

It seems like it will never turn to 1 until GPU is fully used. The data conveys from the backend always shows 0. I believe it may be a minor issue on the backend that deserves a new issue addressing it!

I think for GPU, displaying the amount of memory usage is sufficient. The usage value does not seem to be valuable.

So open an issue about the GPU usage, we can address it in another PR.

So open an issue about the GPU usage, we can address it in another PR.

A New issue has already been submitted with an example screenshot.


Using dictionary keys direcly in function call crashes the game

The function findNearestTargetZombie() returns a dictionary that is properly filled with two non-null values.
When accessing the key directly in the function call to sendProjectile(), as in this example below, the game crashes without an error message (except Debug Process Stopped).
If I assign these two dictionary valus to two separate vars before using them, everything works fine.
			var targetZombieIntel = findNearestTargetZombie()

			if (targetZombieIntel["targetZombie"] != null):
				sendProjectile(currentWeapon, targetZombieIntel["shortestDistance"])

The function returns a dictionary:
func findNearestTargetZombie():
	var heroPos = self.get_translation() + self.get_parent_spatial().get_translation()

	var targetZombie = null
	var shortestDistance = null

        # code for finding zombies

	var found = {"targetZombie": targetZombie, "shortestDistance": shortestDistance}
	return found

Can you still reproduce this issue in the current master @ScyDev? And still only in your own project, or could you manage to reproduce it in a simple project?

Closing as there as not been activity since Dec 2014, and it will be hard to debug if it's project specific. The bug might still be there, but there's not much that can be done to isolate it without further input from the OP.


which TURN server is being used?

Is Licode still using the old turn server implementation or the more advanced ones like coTurn etc?

Licode does not use any turn server per-se. It should be compatible with any rfc compliant turn server.
If it doesn't, please feel free to open a new issue and we'll look into it

Thanks for a quick response.
I am new to WebRTC but I fail to understand what Licode exactly is. If it works with any server then is it a client library like Adapter.js or something else? What does the server component do when its not a TURN/STUN server. Where in the WebRTC stack does Licode sit?
I've looked into client API and server API docs but not sure where Licode is used.
What I understood from your reply is that Licode can be configured to use any TURN server or multiple TURN servers (for load balancing etc). I was referring to http://lynckia.com/licode/turn.html.
Please clarify.

licode support p2p and  server relay.  if you use the server relay, it does not need turn.

Thanks notedit.
Is there a reason why its no supported  on FF? Is it not the same as WebRTC?


Drag&drop leaves frozen void when interrupted

If drag&drop gets interrupted (e.g. right click) the tile gets teleported to 0, 0 and the original space has nothing but also - we cannot move anything there.

Old, with current changes, might be not up to date. Closing.


affinity and toleration patch for certgen

What type of PR is this?
helm:  certgen : adds support for configuring tolerations and affinity of in the helm chart
What this PR does / why we need it:
By adding this fix, we should be able to configure on which k8s node the job should run on.
Fixes (https://github.com/envoyproxy/gateway/issues/4193)

thanks @ncsham !

can we also add empty values into the Charts values

    affinity: {}
    tolerations: []
    nodeSelector: {}
    ```
https://github.com/envoyproxy/gateway/blob/main/charts/gateway-helm/values.tmpl.yaml

* can we also add a test in https://github.com/envoyproxy/gateway/tree/main/test/helm/gateway-helm ?

Have added the empty values in values template & also have added helm tests.

/retest

@arkodg  I have updated the manifests by removing pod: and kept tols & affis inside job: itself.
I forgot to sign the commit off while pushing and when rebased & merged and pushed back , others commits also came into the same pr.
Let me know if thats okay , or i can delete the pr & recreate again.

@arkodg I have updated the manifests by removing pod: and kept tols & affis inside job: itself.
I forgot to sign the commit off while pushing and when rebased & merged and pushed back , others commits also came into the same pr. sorry this is my first oss pr
Let me know if thats okay , or i can delete the pr & recreate again.

please rebase main branch, then git push -f

hey @zirain thanks , the issue was my main branch not in sync with actual repo ,now i synced the fork and rebased and force pushed.


VMAP issue in Combinatorial optimization benchmark

Hello!
The error is the following.
Note I tried multiple versions of dependencies and multiple people tried the same things.
new_x, state, acc = stp_burnin(
ValueError: vmap got inconsistent sizes for array axes to be mapped:
  * most axes (8 of them) had size 1024, e.g. axis 0 of argument rng of type uint32[1,2];
  * some axes (6 of them) had size 1, e.g. axis 0 of argument model_param['edge_weight'] of type float32[1024,64]

I also have encountered the same issue when I use multiple GPUs (even for a single GPU, there is an error with a different message).
I found the configuration of num_models is duplicated (in the experiment and model config).
I've resolved this issue by making the two configurations the same.

add num_models in experiment config (I guess the default value is 1)
change num_models to 1 in model config

It works regardless of the number of GPUs. Good luck.


Video poster disappears after putting app in background for audio files

Bug
poster disappears with audioOnly after app goes into background
Platform
iOS & Android
Which player are you experiencing the problem on:

iOS
Android

Environment info
React native info output:
 System:
    OS: macOS 12.5
    CPU: (10) arm64 Apple M1 Max
    Memory: 3.70 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.15.1 - /opt/homebrew/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.1 AI-211.7628.21.2111.8309675
    Xcode: 13.4/13F17a - /usr/bin/xcodebuild
  Languages:
    Java: 18.0.1 - /opt/homebrew/opt/openjdk/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.68.1 => 0.68.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 5.2.0
Steps To Reproduce

Instantiate a Video with just audio.
Set poster
Put app in background
Go back into app

Expected behaviour

Poster should remain

Poster management is fully done in JS (see Video.js file).
By reviewing the code I don't find the root cause, but I am sure you can find it ! :) ( and provide a pull request to fix it :D )

I removed audioOnly prop as it bring unexpected JS code ...
I advise to move poster management on application side to ensure the behavior is the expected one with your app

linked PR merged, let's close this issue


[Thumbnails] Load images via reva gateway instead of the webdav api

In other services, like the ocs service, we are already using the reva gateway to access files. Maybe we should adopt that too to have consistency in the services.

ping @C0rby, is it still the case? :)

ping @C0rby, is it still the case? :)

Yes, this hasn't changed yet.

Yes, this hasn't changed yet.


Ensure @node/types is available

I cloned this and used PNPM instead of NPM and it doesn't find @node/types because it's not a devDependency.
(I assume it's installed as a dependency of something else, but PNPM isn't as lax as NPM when it installs things. )

adds @node/types

That's rather surprising. I just did a fresh clone of the master branch, and at least for me pnpm it and pnpm run test:types succeed without any issue, and the transitive @types/node dependency does show up in node_modules.
Could you add instructions for reaching the error case that prompted this PR?

Even though this smells like it might be a @microsoft/rush bug, there are a few places in the sources that do admittedly refer to Node.js types, so adding the dev dependency is valid. Done now, including an update to the lockfile.


add handlebars like tag for uuid insertion into bodies

Some kinds of requests need some kind of unique ID in the body of a request and need that to be unique no matter how many times in the body, and unique from request to request.
Something like:
{hey_uuid}

I've possibly implemented it here:
https://github.com/markFromMST/hey/commit/99677b9f99932a0fbf948f2bfbc7a5d752e3b136
However, I haven't been able to test it yet and this is literally the first thing I have done in go and so I have no idea if it is the most efficient way or not yet.


Redis support

Is anybody already working on that?
We're currently switching our cache backend to redis and I like to use that as queueing backend too. But I also like to stick with SlmQueue. If no work is done yet, I can start to write that. But I'm not yet very familiar with Redis. So I need to glimpse at the php-resque(-ex) and Laravel implementations and may need some help as well as a review.

Hi,
No work has been done, but maybe @juriansluiman can open a SlmQueueRedis ? :)

No, no work has been done yet but a while ago I gave it some thought. @stefankleff if you want we can collaborate on a Redis backend for SlmQueue.
A few things worthy I have thought about:

Check the slides from Ross Tuck about Redis and esp. from slide 154 and on about queues.
Redis has a PHP extension (fast!) and a php library (slower, installable via composer). We should support both via an adapter & interface, so you can swap those around
Like we do with SQL, you need a "pending" queue and a "running" queue, with BRPOPLPUSH you can atomically switch jobs from queue "pending" to queue "running". It's blocking, so it waits for a new job to come by automatically

Sounds good! I hope that I can start working on that within next week

See juriansluiman/SlmQueueRedis#1 for the issue I opened to get started. I have made a small outline, but if you have alternative ideas you can completely ignore those.