Contributing

How could I contribute to this project?
I have made a simple example which allows to stream the camera frames into pngs very quickly. there are other applications online, but they are either bulky or very slow.

Thanks so much for the feedback!
I always like examples, and I would like to add it. Either make a fork and send me a pull request, or write the code somewhere and I will add it.
Did you use the Camera and ImageWriter?
JP

U used Camera and ImageEncoder. I do not know about ImageWriter.

I saw your request, getting my PI from my pile and I will try!

I just added another commit, to solve the problem of the buffer length on the stream. Here is a code snippet from the sample application that I am building
    var ws = require('stream').Writable();
    var recBuffer = null;
    ws._write = function (chunk, enc, next) {
        var nextPart = chunk;
        if (chunk.onBufferDone) {
            if (chunk.usedLength !== undefined && chunk.usedLength < chunk.length) {
                // console.log("Getting buffer to smaller size")
                nextPart = chunk.slice(0, chunk.usedLength);
            }
            if (!recBuffer) {
                recBuffer = nextPart;
            } else {
                recBuffer = concat([recBuffer, nextPart]);
            }
            riseCore.emit("omx-camera-frame", recBuffer);
            recBuffer = null;
            chunk.onBufferDone();
        } else {
            if (recBuffer) {
                recBuffer = Buffer.concat([recBuffer, chunk]);
            } else
                recBuffer = Buffer.from(chunk);
        }
        next();
    };

I merged it, however it does not work for me, _write isn't called.

Hi,
I am using the code of npm 1.6.0
I went to the node_modules/openmax/dist/perf, and copied there the
CameraEncode.js example and run it there. It works for me. I run it after
running CameraPipe
Regards,
Santi.
On Tue, Sep 12, 2017 at 7:14 PM, Jean-Philippe Bergeron <
<EMAIL_ADDRESS>wrote:

I merged it, however it does not work for me, _write isn't called.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jean343/Node-OpenMAX/issues/7#issuecomment-329036826,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGf-VhLaU-yAeRxZ_AcBe_8xsSkavm7lks5shzpvgaJpZM4PVVZJ
.

Hi
Could you make it work?
I post you a screenshot of what I'm doing right now. I am using 4 raspberry
pis and websockets. I get around 25 fps sending jpg frames and around 6%
cpu in the raspberry pi.
Would you be so kind to publish a new version of the module with the latest
change? It is needed for the jpg transmission because otherwise the system
cannot know if a frame has finished or not when encoding using discrete
frames coming out of the Encoding component.
Regards,
Santi.
On Tue, Sep 12, 2017 at 7:20 PM, Santiago Ledesma<EMAIL_ADDRESS>wrote:

Hi,
I am using the code of npm 1.6.0
I went to the node_modules/openmax/dist/perf, and copied there the
CameraEncode.js example and run it there. It works for me. I run it after
running CameraPipe
Regards,
Santi.
On Tue, Sep 12, 2017 at 7:14 PM, Jean-Philippe Bergeron <
<EMAIL_ADDRESS>wrote:

I merged it, however it does not work for me, _write isn't called.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jean343/Node-OpenMAX/issues/7#issuecomment-329036826,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGf-VhLaU-yAeRxZ_AcBe_8xsSkavm7lks5shzpvgaJpZM4PVVZJ
.

I did not get it to work, I get an invalid parameter exception... It might be a problem with my PI.
Your stats are pretty impressive, PIes are cool!
No problem, I just did push 1.6.1
JP

Txs!
On Thu, Sep 14, 2017 at 4:04 PM, Jean-Philippe Bergeron <
<EMAIL_ADDRESS>wrote:

Closed #7 https://github.com/jean343/Node-OpenMAX/issues/7.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jean343/Node-OpenMAX/issues/7#event-1250170102, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGf-VsT1QWNPlzFGxvTVSAcOmdYoUC8Sks5sibEYgaJpZM4PVVZJ
.


- operator support NULL constants

Which issue does this PR close?

Closes #1192 .
Rationale for this change

Reproducer:
> select -null;
Internal("(- 'Literal { value: Utf8(NULL) }') can't be evaluated because the expression's type is Utf8, not signed numeric")

The result comes out NULL with this pr
What changes are included in this PR?

NegativeExpr accepts NULL input then return ScalarValue::Int32(None) as NULL
do is_signed_numeric type check when NegativeExpr evaluates

Are there any user-facing changes?

@alamb @xudong963 plz have a review, thank you.

My opinion for this feature or new dialect https://github.com/apache/arrow-datafusion/issues/1192#issuecomment-1100830964

Close this pr since more conservative opinions of introducing -NULL SQL dialect, see #1192


exploitdb: 2021-09-21 -> 2021-09-22

Motivation for this change
update to 2021-09-22
add searchsploit as mainProgram
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 138902 run on x86_64-linux 1

1 package built:

exploitdb


Add LBaaS support for Cluster API Provider OCI.

What this PR does / why we need it:
This PR adds support for Load Balancer as a Service (LBaaS) for the Cluster API Provider OCI. LBaaS provides an alternative load balancing solution compared to the existing Network Load Balancer (NLB). With this feature, users will have the option to choose between NLB and LBaaS when creating their clusters, giving them more flexibility and better control over their infrastructure.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #236

Added LoadBalancerType field to the LoadBalancer struct in the api/v1beta1 and api/v1beta2 package.
Implemented necessary changes in the cloud/services/loadbalancerservice packages to support the new load balancer type.
Updated relevant controller logic to handle the new load balancer type.
Implemented LBaaS reconcile in the cloud/scope package.
Updated cluster, client_cluster, and machine to include the new LoadBalancerType field.
Updated the conversion function for version conversion between api/v1beta1 and api/v1beta2.
Updated the base crd YAML file by adding the LoadBalancerType field.
Added a new template templates/cluster-template-loadbalancerservice.yaml for users to utilize the LBaaS feature.
Added new unit tests to ensure all code changes are working correctly and maintain compatibility with the existing implementation.

How to use
Users can now specify the load balancer type in their OCICluster manifests like this:
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: OCICluster
metadata:
  name: my-oci-cluster
spec:
  networkSpec:
    apiServerLB:
      loadBalancerType: LBaaS

go test ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	31.455s
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	0.564s
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	198.407s
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancerservice	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancerservice/mock_lbs	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	1.643s
ok  	github.com/oracle/cluster-api-provider-oci/controllers	28.199s
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	23.763s
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	2.081s
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	3.919s
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]

go test ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	(cached)
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	(cached)
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/controllers	26.457s
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	(cached)
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]

go test ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	45.482s
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	0.955s
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	0.499s
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	198.010s
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	2.704s
ok  	github.com/oracle/cluster-api-provider-oci/controllers	28.091s
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	34.757s
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	1.105s
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	2.444s
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]

e2e test passed
SynchronizedAfterSuite] PASSED [533.836 seconds]
[SynchronizedAfterSuite]
/home/ubuntu/go/src/github.com/yimw/cluster-api-provider-oci/test/e2e/e2e_suite_test.go:252

  Timeline >>
  STEP: Tearing down the management cluster @ 04/07/23 14:31:03.804
  << Timeline
------------------------------

Ran 6 of 25 Specs in 2866.596 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 19 Skipped

go test ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	(cached)
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	(cached)
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/controllers	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	(cached)
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]

go test ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	(cached)
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	(cached)
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/controllers	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	(cached)
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	(cached)
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]


Speed up schedule()

Summary
Speed up ALAP and ASAP scheduling methods.
Details and comments
This PR improves the implementation of scheduling algorithms (ALAP and ASAP) without changing their interface. It constructs the resulting Schedule at once in order to avoid useless creation of intermediate Schedules, which made the original schedule() slow.

On hold until the benchmarking work is done as well as #3698.

This makes sense to me that this would result in a speedup. I imagine the improvements could be very tangible. Do you have some temporary benchmarks we could so that we might consider merging this in before the full benchmark suite is ready?

Here is the improvement of time taken for schedule() in my local environment by this PR for a RB circuit with n Clifford gates.
n=300: 22.656 seconds -> 0.937 seconds
n=200: 9.015 seconds -> 0.567 seconds
n=100: 2.076 seconds -> 0.282 seconds

We can see more improvements for deeper circuits as expected.
Benchmark code:
import numpy as np
from qiskit import transpile, schedule
from qiskit.ignis.verification import randomized_benchmarking as rb
from qiskit.test.mock.fake_openpulse_2q import FakeOpenPulse2Q

np.random.seed(10)
backend = FakeOpenPulse2Q()
rb_opts = {
    'length_vector': [n],
    'nseeds': 1,
    'rb_pattern': [[0, 1]]
}
rb_circs, xdata = rb.randomized_benchmarking_seq(**rb_opts)

qc_transpile = transpile(rb_circs[0], backend)

# measure the time taken only for schedule()
sched = schedule(qc_transpile, backend)

(Note: Please regard those circuits as random circuits for benchmark rather than RB circuits.)

One more thing: This fix #3678 as a by-product.

Yes, I agree this is a significant improvement! I will review this ASAP.


fish shell crashing with partial command entered

Your Windows build number:  (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.16296.0]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

Opened a new shell, pulled recent GitHub changes for a source repo, and then started typing node at which point fish crashed:

The text of the error is:
nod<E> fish: src/common.cpp:1810: failed assertion: pthread_mutex_unlock(lock_obj): errno 1 (Operation not permitted)
<E> fish: Backtrace:
<E> fish: 0   scoped_lock::unlock() + 81
<E> fish: 1   function_exists_no_autoload(std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, env_vars_snapshot_t const&) + 119
<E> fish: 2   highlighter_t::highlight() + 1588
<E> fish: 3   highlight_shell(std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::vector<unsigned int, std::allocator<unsigned int> >&, unsigned long, std::vector<std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, std::allocator<std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > > >*, env_vars_snapshot_t const&) + 300
<E> fish: 4   fish() [0x4c0026]
<E> fish: 5   std::_Function_handler<void (), int _iothread_trampoline<highlight_result_t>::perform<std::function<highlight_result_t ()>, void (*)(highlight_result_t)>(std::function<highlight_result_t ()> const&, void (* const&)(highlight_result_t))::{lambda()#1}>::_M_invoke(std::_Any_data const&) + 45
<E> fish: 6   fish() [0x49d5fb]
<E> fish: 7   /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f68123a76ba]
<E> fish: 8   clone + 109

What's wrong / what should be happening instead:

Obviously fish shouldn't be crashing here.

Hmm... there was another, probably unrelated issue with fish. I am beginning to wonder if these errors are also fish-related; I can't recall that many errors related to zsh or bash yet here. No idea whether the problem is within fish itself at pthread_mutex_unlock() or related to the windows interface. Perhaps someone at windows can give the fish shell a try though, it's a nice shell with some interesting ideas (imo); though I myself use bash, mostly due to laziness and having used it for so many years...

The interesting thing with this one is it isn't in fish, it's in libstdc++. It is possible fish is using C++11 scoped_lock  unusually or even improperly, but unless there is screeching from Real Linux™ users that's less likely. More likely fish recently started using scoped_lock, or stdlibc++ evolved and surfaced the bug. Or there's a WSL regression. It would be nice if someone still on Creators could give it a try (I don't have Creators handy).
An strace -ff fish 2> fish.strace (from bash) is a good place to start. But that's a library assert, which might or might not be due to a hard syscall fail. More likely it's a behavioural problem, along the lines of the pthread fails in the glibc tests. This is probably going to be a tough one, because futex(2) "works", as far as it goes; otherwise the whole edifice would be falling down, not just a given bleeding-edge release of fish.

@therealkenc I can verify that I've been using this version of fish on both OSX and Linux and this has never happened there.

failed assertion: pthread_mutex_unlock(lock_obj): errno 1 (Operation not permitted)

Whatever the unknown  problem with scoped_lock() on WSL1, it will be better with WSL2. Lots of people use fish and there wasn't much uptake on the fail. If anyone repro steps to manifest the error (contrast 'started typing node at which point fish crashed') for WSL1 I'll take a look at the strace for the academic value. It might even have been addressed in WSL1 along the way.


Cross compile to aarch64

Current dependencies on/for this PR:

main

PR #143   👈

This comment was auto-generated by Graphite.

This pr only setups the infrastructure to cross compile, but it's still not working unfortunately.


Azure certs not passed to docker-machine correctly

Impossible to use azure driver because https://github.com/rancher/go-machine-service/blob/cf443915492773a9c30154115e4e640b35d1d607/handlers/providers/azure.go attempts to write the cert data to a file and change the driver config to point at the filename, but it doesn't work.

This has been fixed.

@tfiduccia This also looks like the PR was merged, so just needs to be tested. I think @westlywright just spun up on Azure host recently so maybe you just need his confirmation on the certs.

Version - master UI 3/18
Verified fixed - able to setup Azure.


Time out the logger after 5 minutes of no motion

In manager, subscribe to carState. If we have valid wheel speeds and the car has not moved for 5 minutes, kill loggerd. Reset this timer whenever the car moves, and restart loggerd if the timer reached 0. This handles not uploading useless qlogs in 3 causes.

Cars stuck onroad due to issue
Cars sitting in park
Bodies standing around balancing

Restarting loggerd will just make this appear as a new route.

Meh, actually I don't like this. We should reject server side.


Flatnotes as a PWA

I noticed that Flatnotes can be a PWA when using the demo site (in Brave on mobile and on PC is says "Install Flatnotes"), but not when installed as my own app in docker.  This includes, when setting it up for external use with a similar sub-domain structure as the demo website.

Hi @effree. I believe an app needs to be served over HTTPS for it to be "installable". If you are serving it over plain HTTP then perhaps this is the problem?

@dullage thank you for your quick response.  I am serving the application over https, although i suppose there could be a minimum SSL encryption requirement, that i may not have with my basic Let's Encrypt SSL.  Another thing i was thinking, is that i am using Authelia for security, although, i don't think that should interfere.

@effree - Another thing to check would be the manifest tab in Chrome dev tools. That might give you a warning.
Also check your on the latest version of flatnotes as there were fixes to this recently.

@dullage I am on the latest version of Flatnotes.
I looked at the manifest, and it does have the following:
Note: id is not specified in the manifest, start_url is used instead. To specify an App Id that matches the current identity, set the id field to / .
I followed this page and it showed an example of adding /?homescreen=1 to your url, which i did and it actually allows me to install as PWA on my Macbook in Brave.
Doing the same on Android is still not working though.
I compared the demo to mine and they appear to have the same messages.  I wonder if the Demo site and this site, since they are almost identical cause one to be allowed to be PWA and the other is not based on browsing history or cache, because they don't have some sort of unique app_id.


Add decoding example

A simple standard and generalization decoding example. Could also compare SVM (SVC) with our MaxCorr implementation.

done in #6, may be later improved (xarray output for example)


Note visualizer is inverted

Cannot reproduce this on the sabotage-the-driver branch. Where did this happen?


Add ground_filter config for runtime_manager

Status
DEVELOPMENT
Description
I added runtime_manager configuration for ground_filter about this issue, #827.
Related PRs
#655
Todos

[x] Tests

Steps to Test or Reproduce

tested on Ubuntu 14.04 and 16.04


ORC-962: Add a test coverage for SargsApplier::findColumn case-sensitivity

This is removed from Milestone 2.0.0.


Doesn't work on Jupyter notebooks

I have tested the code on terminal and the package works as expected and with given example. The only issue so far is that the same code doesn't work on jupyter notebook.

I have not tried this for Jupyter notebooks. Could you share an example notebook, so I can check how it might work?

This is the error.
I was wondering if perhaps it has to do with the fact that there is actually no importation taking place eg  'import split_image'. Cuz I'm using this in a jupyter notebook on an python3 kernel.


Update to .NET Aspire Preview 5 stopped running projects in AppHost

I have update my  .NET Aspire version to Preview 5 and plugin starting AppHost with  Aspire.Hosting.Dcp.dcpctrl.ExecutableReconciler iterated.

If I start the AppHost without using the plugin, it work fine.

I think Aspire have changed API for connection in latest version, and plugin can`t connect to AppHost and start work.

Hi! Thanks! I'm already working on the next version. Will be available in a few days

@rafaelldi thanks for the update

Changelog.md:
Changed
https://github.com/rafaelldi/aspire-plugin/issues/109: Support for .NET Aspire preview 4
But its Preview 5 =)

@rafaelldi i have same problem, maybe it's not cause Preview 5?

@EarlJester

But its Preview 5 =)

I was in a rush to make a new version. Thank you!

i have same problem, maybe it's not cause Preview 5?

Quite strange environment variables. Are they generated in this way?

Yep, i specially recreate run configuration "Unnamed" for test purpose, and change only Build Project -> Build Solution

Its good idea, to clean variables. Now dashboard running, but not starts Microservice
And i don't know why its starts on http://localhost:18888

It starts on 18888 port because that is the default one. If you want something different, you can use ASPNETCORE_URLS: http://localhost:15162 something like that. Is the Aspire dashboard also empty?

Yes, Aspire dashboard empty

Also, there should be another environment variable "DOTNET_RESOURCE_SERVICE_ENDPOINT_URL": "http://localhost:20091"

Yep, now its all working. Here last variables and config

@rafaelldi thanks for your patience and help)
And for your plugin is great!


[FLOC-3038] Release Flocker 1.3.1

The broken link in linkcheck only affects Buildbot - the link itself is working.
There is a merge conflict in the NEWS file between this PR and master, due to 1.4.0dev1 having already been merged into master. It doesn't appear that this can be resolved before tagging, as we don't want the 1.4.0dev1 news in this release.

The NEWS and release notes seem fine.
There's a merge conflict with master caused by the ongoing 1.4.0.dev? releases, but I don't think there's much we can do about that. The process probably needs updating and documenting to handle this new situation.
We don't want any mention of 1.4.0.dev? in the NEWS or release notes of the 1.3.1 tagged tree.
So I guess we need to merge master into the release branch after we've tagged and released and before merging the release branch back into master.
The tests have all passed because Buildbot doesn't merge forward release branches.
The conflicts are:
<<<<<<< HEAD
Flocker 1.3.1 (2015-09-16)
=====================================

- Fixed a bug in previous fix where OpenStack Cinder volumes failed to mount. (FLOC-2991)
- Documentation change to support ZFS 0.6.5. (FLOC-3016)
=======
Flocker 1.4.0.dev1 (2015-09-08)
===============================

- Improved the error handling when Cinder volumes enter an unexpected state. (FLOC-2970)
>>>>>>> origin/master

Please proceed.

There's a merge conflict with master caused by the ongoing 1.4.0.dev? releases, but I don't think there's much we can do about that. The process probably needs updating and documenting to handle this new situation.

We don't want any mention of 1.4.0.dev? in the NEWS or release notes of the 1.3.1 tagged tree.
So I guess we need to merge master into the release branch after we've tagged and released and before merging the release branch back into master.

Not sure exactly how to resolve this.
If we merge master into release/flocker-1.3.1, then 1.3.2 will contain more changes than we want.
We could:

start the 1.3.2 branch using the tag 1.3.1 instead of the branch release/flocker-1.3.1,
merge the 1.3.1 changes into master and resolve the conflict using the command line, or
stop merging release branches into master.

Closing this PR in favour of #1950 which resolves merge conflict outside of release/flocker-1.3.1 branch.


MariaDB uuid migration fieldType

Laravel Version
11.16.0
PHP Version
8.2.0
Database Driver & Version
MariaDB 10.6.17
Description
When create a migration with fieldType 'uuid' it fail.
The field type uuid in mariadb is implemented from 10.10
Steps To Reproduce
enviroment : DB_CONNECTION=mariadb
On migration
$table->uuid('uuid')
launch php artisan migrate

Not sure what you're after here. You need 10.10 which you clearly aren't using?

@driesvints in the Laravel 11 documentation the minimum version of mariadb is 10.3,
So I think this is a bug in MariaDbGrammar

@Gioelinz but this is a MariaDB 10.10 feature. There's no way we can make it work in lower versions. There's really no action for us to take here.

Well, the documentation says it supports 10.3 so if version is older than 10.7  (when added; https://mariadb.com/kb/en/uuid-data-type/) it should act like mysql driver 😟
This took me ~2h to find that i should use DB_CONNECTION=mysql over DB_CONNECTION=mariadb.
I would suggest to add an helptext on the documentation page for the mariadb driver just like you have the sqllite section.
Mariadb >10.3 and < 10.7 seems to be supported perfectly if you use the mysql connection.
Just my 2 cents.


Missing roofs in Al Kharid Rooftop Course

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 10
Bug description
Some of the Al Kharid Rooftop Course roofs are missing. This is visible both from the ground and when you're on top of the roof. I made sure "hide roofs" in settings is not enabled. I also make sure the "roof removal" plugin is disabled. I confirmed the bug in safe mode. Vanilla and mobile work fine.
Screenshots or videos

RuneLite version
RuneLite: <IP_ADDRESS>
Launcher: 2.4.2
Logs
client.log
launcher.log

You have Low Detail on.

That's how it looks with low detail on, Jagex did not add any kind of non-textured floor beneath the roof decoration. Turn the plugin off while running rooftops if you don't want it to look like that.


Logging improvements

@ELENAGER I like the logging improvements in this PR. It looks good to me, and I recommend getting accustomed to it before making further modifications. We want to avoid the ramen log file appearing unfamiliar.
I have only one comment concerning CreateOrUpdateMModeManifestWork. Although you removed the log from that function, we are not logging before calling it, at least from one place.

@BenamarMk , thank you for the prompt review. I really tried not to change logs too much, checked with awk and sed, which lines are the longest and are repeated more times. So, I think, that for now it'll be okay. The next step is to pick the logs, that can be moved to DEBUG level.
Speaking about CreateOrUpdateMModeManifestWork, after is always comes "Creating Manifest work" of "Updating Manifest work log, so we are covered there:
Creating ManifestWork   {"DRPC": {"name":"busybox-drpc","namespace":"busybox-sample"}, "rid": "2589375f-0d15-4fb4-aebc-dfb3ce912514", "cluster": "dr2", "MW": {"namespace": "dr2", "name": "busybox-drpc-busybox-sample-vrg-mw"}}
or
Updating ManifestWork   {"DRPC": {"name":"busybox-drpc","namespace":"busybox-sample"}, "rid": "d8503dc3-682f-4535-a5e3-80d75c15bdb5", "name": "busybox-drpc-busybox-sample-vrg-mw", "namespace": "dr1"}


Select component

I'm having a little trouble with the select component.
The idea, was to make a dropdown, from a signal of some entities.  An "IlsEvent" has a name and an ID.
  def selectFromEvents(events: Signal[List[IlsEvent]], valueSignal: Signal[Option[HistoricalEventSetId]], valueUpdater: Observer[Option[HistoricalEventSetId]]): HtmlElement = {
    SelectTwo(
      _.slots.default <-- events.map{ aList =>
        aList.map{
          item => SelectOption(_.value := item.name, _.additionalText := item.id.value.toString())
        }
      }
    )
  }

I couldn't figure out how to use the slots... so I duplicated "Select" into "SelectTwo" and added the default slots. However, I now can't figure out how to set the text in the select option. The additional text field works however...
I feel like they may be related problems with my understanding!

@sherpal I haven't managed to make a select option display it's primary value... I can only get secondary text to work... would you have a hint?

Hmmm... I managed to get it working by adding a default slots object to SelectOption, and then feeding that slot a div... but I don't think it's idiosyncratic!


*: report unreachable in more cases

What have you changed? (mandatory)
Unreachable report is used to perform traffic control and potential down
node detection. This PR adds more unreachable report by hooking the
connection state and send error in raftstore layer. These can also be
useful when implementing hibernate regions as peers can be woken up when
failure is detected.
What are the type of the changes? (mandatory)

Improvement

How has this PR been tested? (mandatory)
unit tests
Does this PR affect documentation (docs) or release note? (mandatory)
No.
Does this PR affect tidb-ansible update? (mandatory)
No.

LGTM. PTAL @Connor1996

/test

/run-integration-tests


meltano run specific log format?

When running via meltano invoke we should default to a structlog config that contains standard fields like log level and timestamps:
Command 'help' could not be found. Utility 'airflow' supports the following commands: ui, scheduler, version, describe
(melty-3.8) ➜  extdev meltano invoke airflow:version
2022-08-02T17:11:56.587242Z [info     ] /Users/syn/projects/meltano-projects/extdev/.meltano/utilities/airflow/venv/lib/python3.8/site-packages/airflow/configuration.py:528: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
2022-08-02T17:11:56.587664Z [info     ]   option = self._get_environment_variables(deprecated_key, deprecated_section, key, section)
2022-08-02T17:11:56.642367Z [info     ] 2.3.3
2022-08-02T17:11:56.665383Z [info     ]

However, when called from meltano run this pretty annoying:
meltano run airflow:version
2022-08-02T17:13:04.668952Z [info     ] 2022-08-02 12:13.04 [debug    ] Loaded env config              env_config={'_WEBSERVER__WEB_SERVER_PORT': '8088', '_CORE__DAGS_ARE_PAUSED_AT_CREATION': 'true', '_CORE__SQL_ALCHEMY_CONN': 'sqlite:///$MELTANO_PROJECT_ROOT/.meltano/run/airflow/airflow.db', 'HOME': '/Users/syn/projects/meltano-projects/extdev/.meltano/run/airflow', 'CONFIG': '/Users/syn/projects/meltano-projects/extdev/airflow.cfg'} cmd_type=command name=airflow stdio=stderr
2022-08-02T17:13:05.766014Z [info     ] 2022-08-02T17:13:05.765438Z [info     ] /Users/syn/projects/meltano-projects/extdev/.meltano/utilities/airflow/venv/lib/python3.8/site-packages/airflow/configuration.py:528: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config. cmd_type=command name=airflow stdio=stderr
2022-08-02T17:13:05.766137Z [info     ] 2022-08-02T17:13:05.765839Z [info     ]   option = self._get_environment_variables(deprecated_key, deprecated_section, key, section) cmd_type=command name=airflow stdio=stderr
2022-08-02T17:13:05.823937Z [info     ] 2022-08-02T17:13:05.823689Z [info     ] 2.3.3 cmd_type=command name=airflow stdio=stderr
2022-08-02T17:13:05.849305Z [info     ] 2022-08-02T17:13:05.849067Z [info     ] cmd_type=command name=airflow stdio=stderr
2022-08-02T17:13:05.849407Z [info     ] 2022-08-02T17:13:05.849201Z [info     ] cmd_type=command name=airflow stdio=stderr
2022-08-02T17:13:05.863664Z [info     ] Block run completed.           block_type=InvokerCommand err=None set_number=0 success=True

We get levels and timestamps from both meltano run, and from the extension. Long term the fix is to have extensions log in json and then read/parse/display that - this way we can filter out unneeded fields. In the short term though, I wonder if we should allow enabling a special meltano run loggin flag that causes the extension to omit specific fields (like timestamp).

Closing - we by default actually don't print timestamps or level info in extension output now.


Increment package version after release of azure-template

Increment package version after release of azure-template

Closing this as it is just a test PR.


Add access-restriction fails for subnet under different subscription to web app

Describe the bug
When adding an access restriction to allow a subnet that resides under a different subscription than the web app, the command fails to find the subnet's resource group.
To Reproduce
Command that fails:
az webapp config access-restriction add `
  -g rg-webapps -n webapp-xfileupload `
  --priority 100 --rule-name 'devopsvnet2' `
  --vnet-resource-group rg-networking --subnet devops --vnet-name vn-shared

Fails with "(ResourceGroupNotFound) Resource group 'rg-networking' could not be found." when the VNet and it's resource group are in a different subscription to the web app.
Expected behavior
The access-restriction should be added to allow access to the webapp-xfileupload web app from the sub-devops subnet.
Environment summary
PowerShell on Windows with azure-cli 2.22.0.

route to service team

@madsd this is already supported right if the resourceId is used instead of name?

@cowinr If the subnet is in a different subscription, you will need to use the resource id of the subnet. the --subnet parameter accepts the full resource id. Also when vNet is in a different subscription you will need to use the -i switch to ignore subnet check. In 2.23 version of cli, this is explicitly called out in an error message if forgotten.
@panchagnula fyi

@madsd Thanks for the info. This works for me if I use the full subnet resource id and add the -i switch.


[FEATURE] password visibility toggle in signup as an user

Description
Toggle the visibility of the password in user signup page on button click.
Screenshots
After addition

🥦 Browser
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

Can you assign me this project for gssoc?

Hello Milan, I kindly request you to consider assigning this project to me. I am eager to contribute my knowledge and contribute to the success of this project.

Hey @SINJINI-G , great issue !
Would you like this to be assigned under GSSOC'23 ?

Hey @SINJINI-G , great issue ! Would you like this to be assigned under GSSOC'23 ?

Yes!! Thanks a lot for the opportunity!!


fix(wordpress): Fix link and displayed document in section on wordpress

Found a small bug on the kubernetes docs site, the displayed code was for mysql a second time instead of the wordpress deployment yaml. This fixes that.
Will i have to run ./update-imported-tutorials.sh as stated here https://github.com/kubernetes/kubernetes.github.io/edit/master/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md after this gets merged or is there a CI/CD thing thatll handle that?

@ahmetb that one is for you ;)

Let's wait until  https://github.com/kubernetes/kubernetes.github.io/pull/5086 gets in then you can submit the PR to the docs repo from now on. We'll remove the content from here.

@kaustavha FYI: https://github.com/kubernetes/kubernetes.github.io/pull/5086 has already been merged :)

Thanks for the PR, looks like this is already fixed in the docs repo.

Thanks @ahmetb.
@k8s-ci-robot Im curious if my CLA signing got registered, assuming its an automated process. Thought the other comments might trigger an update.

k8s-ci-robot added the cncf-cla: yes  label 15 days ago
@kaustavha yeah.


Error message:  code: -1021,enter code here msg: 'Timestamp for this request is outside of the recvWindow.'

Hi,
When I try to login, I got the following message:
code: -1021,enter code here msg: 'Timestamp for this request is outside of the recvWindow.'
I have searched for the reason, and found a few articles, for example:
https://stackoverflow.com/questions/69208437/binance-timestamp-error-timestamp-for-this-request-is-outside-of-the-recvwindow
I have also fix the code on my side, now it works well. Please, let me know if you wish the fix ?

Hello @vd3d,
I've encountered this error before, it is related to out-of-sync system times and it can be resolved by synchronizing your system's time with the network time. As per the link you provided, it's also possible to increase tolerance for out-of-sync system times by setting the recvWindow parameter to 60 seconds. I did a quick test, and it was successful. Nevertheless, I would be glad to see your code solution.

For now it is also my solution, I changed the recvWindow.
If I understand the timestamp is important because if I have network delays, I can buy/sell at a different price than the one I expect. On a consumer PC I cannot sync the machine time with binance, but I suppose that there are other solutions.


[WFLY-4916] Adds the Red Hat Support Lib as well as the Insights Subsystem

This pull request is for the addition of the Red Hat Support Lib and the Insights subsystem.
The Red Hat Support Lib is a Java API to the Red Hat subscriber REST services on redhat.com. Developers interested in leveraging redhat.com REST services can easily integrate them into a web application with this API.
The Insights subsystem is a service that allows the user to send the JDR to insights periodically. Red Hat will analyze the information and provide results related to security vulnerabilities, misconfigurations, performance issues, and other problems discovered in the received metadata. The service is disabled by default and must be manually enabled by the user.
Enabling Insights subsystem from the CLI:

Add subsystem to extensions in standalone.xml
<extension  module="org.jboss.as.insights"/>
Add subsystem to submodules in standalone.xml
<subsystem xmlns="org.jboss.as.insights:1.0"/>
Start standalone server and connect to CLI
To enable execute the following command from the CLI
./subsystem=insights:enable(rhnUid=[RHN-UID],rhnPw=[RHN-PASSWORD])
To change the frequency that the report is sent off
./subsystem=insights:write-attribute(name=frequency,value=[NUMBER-OF-DAYS]) where NUMBER-OF-DAYS is the amount of time that passes between each occurrence.

JIRA: https://issues.jboss.org/browse/WFLY-4916

Can one of the admins verify this patch?

can you please squash this commits into something more reasonable? maybe have 5 commits that are logical units of work not 10+ commits that are "fixing merge conflicts"
see http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html for help on how to do it.

this is ok to test

Linux Build 7031 is now running using a merge of ca9537b6160a295d5e8a1aa2639d563aaa96a5a7

Windows Build 2086 is now running using a merge of ca9537b6160a295d5e8a1aa2639d563aaa96a5a7

Linux with security manager Build 1908 is now running using a merge of ca9537b6160a295d5e8a1aa2639d563aaa96a5a7

Linux Build 7031 outcome was FAILURE using a merge of ca9537b6160a295d5e8a1aa2639d563aaa96a5a7
Summary: Exit code 1 (new) Build time: 0:00:31
Build problems:
Process exited with code 1

Windows Build 2086 outcome was FAILURE using a merge of ca9537b6160a295d5e8a1aa2639d563aaa96a5a7
Summary: Exit code 1 (new) Build time: 0:00:36
Build problems:
Process exited with code 1

Linux with security manager Build 1908 outcome was FAILURE using a merge of ca9537b6160a295d5e8a1aa2639d563aaa96a5a7
Summary: Exit code 1 (new) Build time: 0:00:37
Build problems:
Process exited with code 1

build failure:
[11:51:13][Step 2/3] [ERROR] The build could not read 2 projects -> [Help 1]
[11:51:13][Step 2/3] [ERROR]
[11:51:13][Step 2/3] [ERROR]   The project org.wildfly:wildfly-insights:10.0.0.Alpha5-SNAPSHOT (/opt/buildAgent/work/a31d203e70e89f90/insights/pom.xml) has 1 error
[11:51:13][Step 2/3] [ERROR]     'dependencies.dependency.version' for commons-net:commons-net:jar is missing. @ org.wildfly:wildfly-insights:[unknown-version], /opt/buildAgent/work/a31d203e70e89f90/insights/pom.xml, line 78, column 21
[11:51:13][Step 2/3] [ERROR]
[11:51:13][Step 2/3] [ERROR]   The project com.redhat.gss:wildfly-redhat-support-lib:10.0.0.Alpha5-SNAPSHOT (/opt/buildAgent/work/a31d203e70e89f90/redhat-support-lib/pom.xml) has 1 error
[11:51:13][Step 2/3] [ERROR]     'dependencies.dependency.version' for commons-net:commons-net:jar must be a valid version but is '${version.commons-net}'. @ com.redhat.gss:wildfly-redhat-support-lib:[unknown-version], /opt/buildAgent/work/a31d203e70e89f90/redhat-support-lib/pom.xml, line 66, column 26

Also on top of all this, I think this shouldn't be part of WildFly codebase.
It would be much better if it would be a feature pack that WildFly/EAP distribution would just pull in.
So it can be maintained in separate repository and have its own release cycle.

subsystem is missing test cases.

@ctomc Thanks for taking a detailed look at the changes. I am working on making the corrections to the issues pointed out in your comments. I agree that it would be better if the Red Hat Support Lib lived outside of WildFly. The codebase already exists on GitHub [1] but the changes specific to WildFly will need to be added to it. I'm not sure how to import it into WildFly. How should I go about doing this?
[1] https://github.com/redhataccess/redhat-support-lib-java

The fundamental question here is why is the subsystem configuration not being persisted to the configuration document, but instead is written to a separate file? What led to this choice?

Once the various questions are sorted, this is going to need to be squashed down to a reasonable number of commits. By chance Jason Greene had a pretty good comment on a different PR re: multiple commits, so I'll quote it here:
In general I think its ok if there are multiple commits as long as

1) They can pass the test suite in isolation, such that git bisect works
2) They are discrete well contained units of work
3) There is a very small number of them
4) They are related

We're not exactly rigid about that, but that's the general spirit and our commit history very much reflects that.

Linux Build 7085 is now running using a merge of 438f43e1066ffe8adca32f2dc04b4179927b43b8

Linux with security manager Build 1960 is now running using a merge of 438f43e1066ffe8adca32f2dc04b4179927b43b8

Windows Build 2139 is now running using a merge of 438f43e1066ffe8adca32f2dc04b4179927b43b8

Linux with security manager Build 1960 outcome was FAILURE using a merge of 438f43e1066ffe8adca32f2dc04b4179927b43b8
Summary: Exit code 1 Build time: 0:00:18
Build problems:
Process exited with code 1

Linux Build 7085 outcome was FAILURE using a merge of 438f43e1066ffe8adca32f2dc04b4179927b43b8
Summary: Exit code 1 Build time: 0:00:29
Build problems:
Process exited with code 1

Windows Build 2139 outcome was FAILURE using a merge of 438f43e1066ffe8adca32f2dc04b4179927b43b8
Summary: Exit code 1 Build time: 0:00:34
Build problems:
Process exited with code 1

Windows Build 2296 is now running using a merge of b3be6e0f6d71111ca1a8494084b4ae1740b30df8

Linux with security manager Build 2112 is now running using a merge of b3be6e0f6d71111ca1a8494084b4ae1740b30df8

Linux Build 7243 is now running using a merge of b3be6e0f6d71111ca1a8494084b4ae1740b30df8

Linux Build 7243 outcome was FAILURE using a merge of b3be6e0f6d71111ca1a8494084b4ae1740b30df8
Summary: Exit code 1 Build time: 0:00:25
Build problems:
Process exited with code 1

Linux with security manager Build 2112 outcome was FAILURE using a merge of b3be6e0f6d71111ca1a8494084b4ae1740b30df8
Summary: Exit code 1 Build time: 0:00:24
Build problems:
Process exited with code 1

Windows Build 2296 outcome was FAILURE using a merge of b3be6e0f6d71111ca1a8494084b4ae1740b30df8
Summary: Exit code 1 Build time: 0:00:34
Build problems:
Process exited with code 1

Linux with security manager Build 2139 is now running using a merge of 8613010e2bb232e2aef2acc813f2d6d06f89b203

Linux Build 7270 is now running using a merge of 8613010e2bb232e2aef2acc813f2d6d06f89b203

Windows Build 2323 is now running using a merge of 8613010e2bb232e2aef2acc813f2d6d06f89b203

Linux with security manager Build 2139 outcome was FAILURE using a merge of 8613010e2bb232e2aef2acc813f2d6d06f89b203
Summary: Exit code 1 Build time: 0:00:23
Build problems:
Process exited with code 1

Linux Build 7270 outcome was FAILURE using a merge of 8613010e2bb232e2aef2acc813f2d6d06f89b203
Summary: Exit code 1 Build time: 0:00:24
Build problems:
Process exited with code 1

Windows Build 2323 outcome was FAILURE using a merge of 8613010e2bb232e2aef2acc813f2d6d06f89b203
Summary: Exit code 1 Build time: 0:01:02
Build problems:
Process exited with code 1

Windows Build 2381 is now running using a merge of 1652a96690a664e2a6754da5997d4036d289495d

Linux Build 7333 is now running using a merge of 1652a96690a664e2a6754da5997d4036d289495d

Linux with security manager Build 2196 is now running using a merge of 1652a96690a664e2a6754da5997d4036d289495d

Linux Build 7333 outcome was FAILURE using a merge of 1652a96690a664e2a6754da5997d4036d289495d
Summary: Exit code 1 Build time: 0:00:26
Build problems:
Process exited with code 1

Windows Build 2381 outcome was FAILURE using a merge of 1652a96690a664e2a6754da5997d4036d289495d
Summary: Exit code 1 Build time: 0:00:28
Build problems:
Process exited with code 1

Linux with security manager Build 2196 outcome was FAILURE using a merge of 1652a96690a664e2a6754da5997d4036d289495d
Summary: Exit code 1 Build time: 0:00:35
Build problems:
Process exited with code 1

Linux Build 7628 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7628 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:27

Linux Build 7629 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7629 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7630 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7630 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7631 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7631 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7632 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7632 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7633 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7633 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7634 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7634 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:22

Linux Build 7635 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7635 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:32

Linux Build 7636 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7636 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7637 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7637 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7638 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7638 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:13

Linux Build 7639 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7639 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7640 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7640 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7641 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7641 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7642 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7642 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7643 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7643 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7644 is now running using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6

Linux Build 7644 outcome was FAILURE using a merge of 7d6e4e4ba715c1322de248ef4ec7cc28c2b1bec6
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7645 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7645 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7646 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7646 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7647 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7647 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7648 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7648 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:19

Linux Build 7649 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7649 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7650 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7650 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7651 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7651 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7652 is now running using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c

Linux Build 7652 outcome was FAILURE using a merge of 0a2a779581c4ed68be43149e775f09c57d100d9c
Summary: Exit code 1 Build time: 00:00:16

Linux Build 7653 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7653 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7654 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7654 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7655 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7655 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:16

Linux Build 7656 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7656 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7657 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7657 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7658 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7658 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7659 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7659 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7660 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7660 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:16

Linux Build 7661 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7661 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7662 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7662 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7663 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7663 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7664 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7664 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7665 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7665 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:22

Linux Build 7666 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7666 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7667 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7667 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7668 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7668 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:16

Linux Build 7669 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7669 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:18

The issue is you're parent is still set to 10.0.0.Alpha6-SNAPSHOT and master is on 10.0.0.Beta2-SNAPSHOT. Please update the parent so it will build.

Linux Build 7670 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7670 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7671 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7671 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Thanks, James. Will do.
----- Original Message -----

From: "James R. Perkins"<EMAIL_ADDRESS>To: "wildfly/wildfly"<EMAIL_ADDRESS>Cc: "Josh Kinlaw"<EMAIL_ADDRESS>Sent: Thursday, August 20, 2015 4:09:03 PM
Subject: Re: [wildfly] [WFLY-4916] Adds the Red Hat Support Lib as well as the Insights Subsystem (#7752)
The issue is you're parent is still set to 10.0.0.Alpha6-SNAPSHOT and
master is on 10.0.0.Beta2-SNAPSHOT. Please update the parent so it will
build.

Reply to this email directly or view it on GitHub:
https://github.com/wildfly/wildfly/pull/7752#issuecomment-133157059

Linux Build 7672 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7672 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7673 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7673 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7674 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7674 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7675 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7675 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7676 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7676 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7677 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7677 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:18

Linux Build 7678 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7678 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7679 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7679 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7680 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7680 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7681 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7681 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Linux Build 7682 is now running using a merge of dae28ee050a57610d7181d669a793aa6039a2f68

Linux Build 7682 outcome was FAILURE using a merge of dae28ee050a57610d7181d669a793aa6039a2f68
Summary: Exit code 1 Build time: 00:00:17

Hi Josh,
This PR is messing with our CI job, somehow triggering continual tries to test it. Please open a new PR once you have a version that's squashed and builds locally and that Emmanuel can build locally as well.


How to train a model by myself

Hello, I have a few questions that I would like to ask you:

Open source code only provides prediction and fine-tuning code, without providing training code, right? If I want to train my own model, it's best to make one by myself?
The reason why we can see all the technical details is because when the model predicts, it predicts by reading the downloaded model parameters. Is this understanding correct?
"Training low resolution random models", I mean the fine-tuning code for the last part of the official Notebook instance. How did he implement it? It seems that he did not download the training data，is it just randomly adjusting the parameters in the parameter file?

Thank you very much!

Excuse me, have you implemented training a new graphcast model yourself?

Thanks for your message, the open source code provides a "loss" function, which you can use to both train and fine-tune the model if you can fit it in your hardware. However you would need to provide your own data iterators, and implement batch parallelism (to train on multiple devices simultaneously and this way reduce training time) for your specific platform.

Thank you very much for your answer, I'm a beginner and it's hard for me to reproduce such a complex model as GraphCast. I want to learn such a good model, but the training details are not mentioned in the paper, which is not enough for me to complete the reproduction independently. So could you please provide an example of training from scratch that I can use as a reference.

but the training details are not mentioned in the paper
To the best of our knowledge all training details for minimizing the loss (optimizer, batch size, trajectory sampling, learning rate schedules, etc) are provided in the supplementary materials of the paper (sections 4.4 and 4.5).

If there is something you find is missing, please let us know we will more than happy to clarify!

Hello, I have some questions about model training. Have you tried training models with different resolutions, GraphCast_small (13levels, 1°) and GraphCast (37levels, 0.25°)? How much time and memory does it take to train these two models?
I look forward to your response. Thank you.
Best regards！

@zhongmengyi I have replied in your separate issue https://github.com/google-deepmind/graphcast/issues/77


Cannot Upload IPA Files Anymore

What App Center service does this affect?
AppCenter -> 'Distribute'
Describe the bug
After uploading an IPA file (a Xamarin iOS app) to the app center, the page stays at 'Upload a build' even though the progress bar has run to the end. Cannot proceed to the next step.
To Reproduce
Steps to reproduce the behavior:

Go to AppCenter -> 'Distribute'
Select a group
Click 'New release'
Drag & drop an IPA file below 'Upload a build'
See bug description

Expected behavior
The upload should be finished once the progress bar runs to the end and the 'Next' button should become available.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Pro Version 1903 OS build 18362.175
Browser: Edge Insider Version <IP_ADDRESS> (Official build) dev (64-bit), also Opera Version 60.0.3255.170

Additional context
The same files could be uploaded without problems last week, but not anymore now.

We have an ongoing incident affecting uploading iOS builds. Please follow our status page for any updates https://status.appcenter.ms/

Thanks for the quick response.

Hi,
I am experiencing this issue again today.


Connection with sql server too long after updating dbeaver 22.1.0 on macos

System information:
Operating system (distribution) and version: macos High Sierra
DBeaver version: Version 22.1.0
Hi! I'm a new user to DBeaver.
I had the previous version installed of dbeaver community and connected with sql server (using Docker) and I was working fine. Today I've installed the latest version and I'm trying to connect with database (master) but is loading for a quite time and still the Connect to master shows 0%. I cannot see my projects or tables I've created on my database or the ER diagram. For example when I try to open ER diagram  the error failed message displays "Datasource master entities cannot be downloaded-no entity container found".
Does anyone had this issue?
Thank you!

Could you please send me the log files? You can find instructions here: https://dbeaver.com/docs/wiki/Log-files/. Thank you.

Could you please send me the log files? You can find instructions here: https://dbeaver.com/docs/wiki/Log-files/. Thank you.

Thank you for your reply. I can't find any log files only a file that contains steps from the update. Can I send you a direct email?

Hello @Ndysa
Can you please check your connection view?
If it is custom, can you please set it to "Advanced"?

Maybe it's connected to https://github.com/dbeaver/dbeaver/issues/16657

There have been no updates for a long time.
If the issue is still actual - feel free to reopen it