remove npm upgrade in .travis.yml

currently we run scripts/ensure-compatible.npm.sh to upgrade npm if it's old.  since we want to retain support for old npm versions (for now), let's not do that.

okay, this is not possible due to the coffee-script dev dep.

so, theoretically, we are fine with npm pre-1.3.7 in production--i.e., npm install mocha

cc @dougwilson

So, is coffeescript is only needed for development, or is it also needed to run the tests on Travis CI? If it is not needed to run tests, then you can always remove it before Travis CI does the install (similar to https://github.com/jshttp/mime-db/blob/master/.travis.yml#L13-L21).

And of course, if you actually do need coffeescript for running tests, you can always split tests in two parts (kinda like https://github.com/dougwilson/nodejs-depd/blob/master/.travis.yml#L13-L15 + https://github.com/dougwilson/nodejs-depd/blob/master/test/browserify.js#L9).

Looks like it is at least used in your test-compilers Makefile target https://github.com/mochajs/mocha/blob/master/Makefile#L55 We could probably jiggle things around to get it to work. If you are serious about removing the npm upgrade, let me know, and I can even perhaps work on a PR to do so instead of you feeling like the burden is on you :)

Is it a big deal though?  Do you need to develop Mocha on a system with an old npm version?

I have pushed code for 2.3.2 but haven't published yet

Is it a big deal though? Do you need to develop Mocha on a system with an old npm version?

I have to be able to install mocha to test on the systems that I support. I'm not developing on those systems, but mocha is the test runner, so without being able to install mocha, I cannot run any tests against the systems that will be running production code, which would make using mocha not very useful to me.

Well, you can still do that (in theory), you just can't git clone mocha and install its devdependencies.  Am I missing something?

No, you're not missing anything. The main problem right now is that if you cannot do the install on Travis with an old version of npm, you'll never notice when a change breaks the install process for production users.

In other words, it's generally in your favor for your CI process to prevent the need to make commits like https://github.com/mochajs/mocha/commit/c7a8fedd08c13315c2befcb99699abeda1a9f3b0 , but the current CI process in this repository does not assist in identifying breaking changes.

Right.
I'd consider a solution similar to what you posted above (https://github.com/dougwilson/nodejs-depd/blob/master/.travis.yml#L13-L15).  This is fine for CI, but if a user is running npm test locally, they will run into problems.  Two more ideas:

Have a prepublish script which installs coffee-script if the detected npm version is high enough (and if there's a env var that npm sets if it's installing in development mode?  failing that, presence of .git/ may be sufficient), and then have a conditional which skips the test if coffee-script is not present.

Tell Travis to upgrade npm (if necessary), install coffee-script, then downgrade it again, then npm install.  Because we know coffee-script would break an old npm, this is fine.  If any other dependency would break stuff, then the build would error.

I'm partial to #2 since it avoids modifying the dependencies or tests themselves.

This is fine for CI, but if a user is running npm test locally, they will run into problems.

What problem will they run into? If you clone that repo and run the tests, you'll see there is no issue running them at all (the suggestion consisted of two different areas).

and then have a conditional which skips the test if coffee-script is not present.

That's my original suggestion, the one you referenced with the link to the .travis.yml file :)

Tell Travis to upgrade npm (if necessary), install coffee-script, then downgrade it again, then npm install. Because we know coffee-script would break an old npm, this is fine. If any other dependency would break stuff, then the build would error.

I tried this in the past with my modules but was never able to get the downgrade to work. This means that I would not be successful in implementing this for you, so the implementation would have to be left on your shoulders :(

Sorry to interrupt the conversation, but now that 2.3.2 is finally published, I tried it out, and still no dice: 2.3.2 still does not install. The new version of jade in 2.3.0 now has multiple dependencies with ^: https://github.com/jadejs/jade/blob/1.11.0/package.json#L25-L36

Sorry, moved the above comment into the proper issue thread :)


Execution time for codes

Should we add execution time to our codes?

you can use time.time()

https://www.tutorialspoint.com/python/time_time.htm

you can use time.time()

Absolutely! thanks for the information.

Yes. would be better if we add it.


Implement emission for Call nodes

Only calling functions without type parameters

I can give this one a try, feel free to assign me!


Wrong Lambda Execution Role

Describe the bug
Hi!
I have a Function with full CRUD access configured to my Auth and API (GraphQL) resources.
My API has Cognito User Pools set as primary/default authentication method and IAM as an additional authentication method.
My API has a UserData model defined as follows:
type UserData
    @model(queries: {get: "getUserData", list: "listUsersData"}, subscriptions: null)
    @auth(rules: [
        {allow: private, provider: iam},
        {allow: owner, ownerField: "id", operations: [read update]}
    ]) {
        id: ID! @auth(rules: [{allow: private, provider: iam}]),
        firstName: String!,
        lastName: String!,
        email: String!,
        phone: String!,
        groups: [String!]! @auth(rules: [{allow: private, provider: iam}]),
        permissions: [String]! @auth(rules: [{allow: private, provider: iam}])
    }

And my Function is implemented as follows:
type Query {
    adminListUsersData(filter: ModelUserDataFilterInput, limit: Int, nextToken: String): ModelUserDataConnection
        @auth(rules: [{allow: groups, groups: ["admins"]}])
        @function(name: "userDataResolvers-${env}")
}

The problem is that when an admin user calls the adminListUsersData query, the AWS SDK inside the function acquires the calling user credentials and not the Lambda execution role credentials. So, when I try interact with my UserData model internally from the Lambda function it is as if the admin user was calling it directly instead of the function.
I've followed GraphQL from NodeJS guide to call the API from the Lambda function.
I've also tried to call AWS.config.update() method or to use AWS.EnvironmentCredentials() or AWS.Credentials() classes to generate new credentials for Signers.V4 with AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN from Lambda Runtime Environment Variables, but I still get unauthorized error.
I can't get my Lambda function to sign the API request using its own IAM credentials instead of the calling user ones. Please help!
Amplify CLI Version
4.24.2
To Reproduce
See bug description.
Expected behavior
I would expect the Lambda function to use its own execution role to authenticate with the AWS SDK or at least to allow me to choose which identity I would like to use.
Screenshots
None.
Desktop (please complete the following information):

OS: macOS 10.15.5
Node Version: 14.4.0

Additional context
None.

Any recommendation? This is very frustrating.

@djsmedes @yuth @attilah hi guys! Sorry to bother you and for being too insistent, but I saw that you've been working on similar issues. It has been days and I still can't sort this out. Could you please give me some inputs to be able to continue working with Amplify? I'm ready to provide further details if needed. Thank you very much!

The place I'd start is in the chunk of code that does this or similar (this code copy+pasted from the GraphQL from NodeJS you mentioned):
const signer = new AWS.Signers.V4(req, "appsync", true);
signer.addAuthorization(AWS.config.credentials, AWS.util.date.getDate());

Is that code executing? After that, does the req variable contain an Authorization header with a block of info that is semi-human-readable, complicated AWS signature? Or does it still contain the jwt?
Incidentally, are you following those docs closely and creating an entirely new request object, or are you reusing the request that comes in as a subkey somewhere in the object from the lambda's event parameter?

@djsmedes thank you very much for your answer. While logging some data to CloudWatch to verify what you asked, I realized something else, quite interesting:
The unauthorized error I was getting, specifically for id, permissions and groups fields, was only viewable at client side. I mean, the call to the API inside the Lambda function was successful!
The problem was that here:
type Query {
    adminListUsersData(filter: ModelUserDataFilterInput, limit: Int, nextToken: String): ModelUserDataConnection
        @auth(rules: [{allow: groups, groups: ["admins"]}])
        @function(name: "userDataResolvers-${env}")
}

I used ModelUserDataConnection as the return type, which is defined as:
type ModelUserDataConnection {
    items: [UserData],
    nextToken: String,
    scannedCount: Int,
    count: Int
}

It references UserData model and this made all the @auth rules from it to be applied to my custom query, but at response time, after function execution! I don't know if that is the intended behaviour, but could be useful sometimes. To solve the problem I just created a new normal type for the query output without any kind of directive.

Duplicate of #4889 that is being fixed by #5342 fixes it.


Azure driver is not coming in allowed molecule drivers list

Azure driver is not coming in allowed molecule drivers list so not able to create an azure scenario.
$ molecule drivers
name
---------
delegated
docker
ec2
podman

i have already installed the molecule-azure driver using pip

After installing the latest molecule version that had the fixed, resolved the issue.


added space-time levy area (for PR)

Hi Patrick,
This is a new PR with just the Brownian things. I tried to keep it as contained as possible.

Nice work fixing the SDE test. I think we can simplify it a little, but otherwise this looks good.
For next steps: so that we can merge this in, can you rebase on top of the current dev branch? This makes a few changes that mostly shouldn't affect you. (The changes are mostly twiddly things like renaming files + better type annotations + better formatting.)

As much as I am in favour of strong typing, this rebase was extremely fiddly. Yes, worth it, but I didn't expect so much resistance :)

Aaaaaand merged! This is now on the dev branch and will be part of the upcoming v0.5.0 release.
I know how fiddly a task this was. Thank you for all your hard work getting this together. :D

Excellent!! Thank you so much for guiding me through this so well, and for all your time and effort!


Make deps target public

rules_rust depends on this, and our stardoc build is sad if we don't have a dep on it.

If I could bother a maintainer for a release if/when this merges, that'd be handy, thanks!

I can't create releases at the moment, @meteorcloudy could you?

I'll be occupied for the next 2 hours, @Wyverald can you help?

Done. Waiting for publish-to-bcr now

The BCR release failed to access the release archive with a 404. We need to release again.

https://github.com/bazelbuild/bazel-central-registry/pull/2438

The BCR release failed to access the release archive with a 404. We need to release again.

Was that a bug in the publish-to-bcr bot or the release process?

Since the same process worked on the re-release, I would say it was a bug in GitHub. I saw similar failures in other CI pipelines.

Ah, thanks for the context!

@kormide Any easy way to retrigger publish-to-bcr in such cases? Does it work if we change the release to a prerelease and back?

Since the same process worked on the re-release, I would say it was a GitHub outage. I saw similar failures in other CI pipelines.

I didn't do a re-release; I created the BCR PR myself.
I wonder if it's a race condition between the hook to "upload release archive on release" and "publish-to-BCR on release". Maybe we could simply have publish-to-bcr retry with some long backoff on a 404. See also https://bazelbuild.slack.com/archives/C014RARENH0/p1720549041765859?thread_ts=1720549041.765859&cid=C014RARENH0

@kormide Any easy way to retrigger publish-to-bcr in such cases? Does it work if we change the release to a prerelease and back?

The only way to retrigger it currently is to delete then re-create the release. This will change in the next quarter or so as we migrate it to a GitHub Action to support provenance; you'll have more manual control over re-running it.

I wonder if it's a race condition between the hook to "upload release archive on release" and "publish-to-BCR on release". Maybe we could simply have publish-to-bcr retry with some long backoff on a 404. See also https://bazelbuild.slack.com/archives/C014RARENH0/p1720549041765859?thread_ts=1720549041.765859&cid=C014RARENH0

Publish To BCR does do retries with backoff, however it's recommended that you upload the release archive as part of publishing the release rather than uploading it afterward.


Strip parentheses in column type when set to column change options.

https://github.com/laravel/framework/commit/72d3febb752fb252148f8cd7a677587db8f20d04 broke changing columns of type bigint (and probably others) in v5.0.6. This change simply strips the parentheses when set in the column options during a change operation. Now both decimal and bigint change operations work.

Please indent with tabs, and fix your docblocks.

I'm not merging anything else related to this without some tests.

Updated tabs & docblock. Will try my hand at some tests.


[FAQ] Read a file

General Question
Is it possible to read the contents of a file and use it as a value?

I think you would be looking for something like the file package in combination with something else like the yaml package. So you could have something like:
# config.yaml file
foo: bar
struct:
  key: value

# main.k file
import file
import yaml

_config_filename: str = "${file.modpath()}/config.yaml"
_config = yaml.decode(file.read(_config_filename))

my_item = _config.foo
my_item2 = _config.struct.key

kcl run main.k
# Output:
# my_item = bar
# my_item2 = value

You can also combine it with with the template package, which uses handlebarsjs under the hood.

Extra:
This doesn't answer the question and it's a bit off-topic but I think it can be of interest for some people with my use case (And also I'm telling you because I blame you for making me fall in love with KCL through your videos :P):
I'm currently using KCL in combination with Crossplane and because of my use case I was really looking for these kind features that allowed me to split Compositions, Functions and inline code into multiple files in order to preserve syntax and improve the developer experience a little bit.
So thanks to these features you can do some crazy stuff like having a Compositon written in KCL, which uses a KCL Function which creates a Terraform Workspace with some TF code stored in a different file, while having a neat folder organization and preserving syntax:

Code here

Note: Untested
Folder structure:
composition/
├── composition.k
├── input.k
└── input.workspace.tf

Composition:
# composition.k
import file
import template

import crossplane.v1.apiextensions_crossplane_io_v1_composition as xp

_input_filename: str           = "${file.modpath()}/composition/input.k"
_input_workspace_filename: str = "${file.modpath()}/composition/input.workspace.tf"

composition = xp.Composition {
    metadata: {
        # ...
    }
    spec: {
        # ...
        pipeline: [
            {
                step: "kcl-render"
                functionRef.name: "function-kcl"
                input: {
                    apiVersion: "krm.kcl.dev/v1alpha1"
                    kind: "KCLRun"
                    spec: {
                        # Read the Function KCL code, use it as a template and insert the TF code:
                        source: template.execute( \
                            file.read(_input_filename), \
                            {
                                "TERRAFORM_INPUT": file.read(_input_workspace_filename)
                            } \
                        )
                        # ...
                    }
                }
            }
            # ...
        ]
    }
}

KCL Function code chunk:
# input.k

# ...
_tf_workspace = {
    apiVersion: "tf.upbound.io/v1beta1"
    kind: "Workspace"
    metadata: {
        # ...
    }
    spec.forProvider: {
        source: "Inline"
        varmap: {
            # ...
        }
        # Template variable substituted through template.execute(FILE, VARIABLES):
        module: '''{{{ TERRAFORM_INPUT }}}'''
    }
}
# ...

... And the Terraform code:
# input.workspace.tf

# ...
variable "whatever" {
    # ...
}
# ...

It's probably not the best of the approaches to take, but it's just an exampleof what I think as a great synergy between KCL and Crossplane in part thanks to these system packages :)

❤ 👋
@vfarcic Thank you for your feedback and attention.
@jgascon-nx Thank you for sharing your use case. I think it would be very helpful for the community.

@jgascon-nx Your use case is very similar to mine. I completely missed the "System Package" section in the docs. That's what I needed. Thanks a ton for the tips.
@Peefy You're doing a great job both with KCL and with the Crossplane function.

Hey @jgascon-nx, just FYI, here's how I deal with kcl and crossplane resources https://github.com/mindwm/mindwm-gitops/blob/b6adfdae54704e17a0e85751c9e52343755d2480/crossplane/xrd_kcl_function.k


Update to wgpu 0.16

addresses #27

Getting a failure when I try to run my project against this ambient build:
[2023-04-14T02:54:40Z INFO  ambient_network::server] Connecting to proxy server
[2023-04-14T02:54:40Z ERROR wgpu::backend::direct] Handling wgpu errors as fatal by default
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_shader_module
      note: label = `collect`

Shader 'collect' parsing error: expected global item ('struct', 'const', 'var', 'type', ';', 'fn') or the end of the file, found 'let'
  ┌─ wgsl:4:1
  │
4 │ let PI: f32 = 3.1415927;
  │ ^^^ expected global item ('struct', 'const', 'var', 'type', ';', 'fn') or the end of the file

    expected global item ('struct', 'const', 'var', 'type', ';', 'fn') or the end of the file, found 'let'

', /Users/kevzettler/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.15.1/src/backend/direct.rs:3024:5
stack backtrace:
   0:        0x10451ebb0 - std::backtrace_rs::backtrace::libunwind::trace::hf9c5171f212b04e2
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:        0x10451ebb0 - std::backtrace_rs::backtrace::trace_unsynchronized::h179003f6ec753118
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:        0x10451ebb0 - std::sys_common::backtrace::_print_fmt::h92d38f701cf42b17
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/sys_common/backtrace.rs:65:5
   3:        0x10451ebb0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hb33e6e8152f78c95
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/sys_common/backtrace.rs:44:22
   4:        0x10453d424 - core::fmt::write::hd33da007f7a27e39
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/fmt/mod.rs:1208:17
   5:        0x1045186b4 - std::io::Write::write_fmt::h7edc10723862001e
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/io/mod.rs:1682:15
   6:        0x10451e9c4 - std::sys_common::backtrace::_print::h5e00f05f436af01f
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/sys_common/backtrace.rs:47:5
   7:        0x10451e9c4 - std::sys_common::backtrace::print::h895ee35b3f17b334
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/sys_common/backtrace.rs:34:9
   8:        0x1045202d4 - std::panicking::default_hook::{{closure}}::h3b7ee083edc2ea3e
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:267:22
   9:        0x10452002c - std::panicking::default_hook::h4e7c2c28eba716f5
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:286:9
  10:        0x1045208f8 - std::panicking::rust_panic_with_hook::h1672176227032c45
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:688:13
  11:        0x104520718 - std::panicking::begin_panic_handler::{{closure}}::h0b2d072f9624d32e
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:579:13
  12:        0x10451f018 - std::sys_common::backtrace::__rust_end_short_backtrace::he9abda779115b93c
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/sys_common/backtrace.rs:137:18
  13:        0x104520474 - rust_begin_unwind
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:575:5
  14:        0x104668ee4 - core::panicking::panic_fmt::h23ae44661fec0889
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/panicking.rs:64:14
  15:        0x10436c34c - core::ops::function::Fn::call::hcf4cc58820ffc9ff
  16:        0x104371ef4 - wgpu::backend::direct::Context::handle_error::hc8fb7fa40876ed82
  17:        0x10437530c - <wgpu::backend::direct::Context as wgpu::context::Context>::device_create_shader_module::ha40b4b95ddecf3aa
  18:        0x10437fee8 - <T as wgpu::context::DynContext>::device_create_shader_module::h5e88704abec52aaa
  19:        0x1043acde4 - wgpu::Device::create_shader_module::h612550accd4e4354
  20:        0x103b02234 - ambient_gpu::shader_module::Shader::new::h7f39a8fad72456f2
  21:        0x103ab0d70 - ambient_renderer::collect::RendererCollect::new::h15d8471a408870e5
  22:        0x103a902cc - <ambient_renderer::renderer::RendererResourcesKey as ambient_asset_cache::SyncAssetKey<ambient_renderer::renderer::RendererResources>>::load::h8041c661e03bf98c
  23:        0x103ac5d98 - ambient_asset_cache::AssetCache::get_sync::h3f72b98d359b1591
  24:        0x103a9062c - ambient_renderer::renderer::Renderer::new::haec1d2530fdfad6a
  25:        0x1037ed960 - ambient_app::renderers::ExamplesRender::new::h20c64d5c0234be4d
  26:        0x1023a7990 - ambient_app::AppBuilder::build::{{closure}}::h4a8835e912a35e71
  27:        0x1023d7788 - tokio::runtime::park::CachedParkThread::block_on::hd76caf47e1724d7e
  28:        0x102112e30 - tokio::runtime::runtime::Runtime::block_on::h4d567e45fb7ca851
  29:        0x10222b290 - ambient::main::h7418a37aad211a2c
  30:        0x102097784 - std::sys_common::backtrace::__rust_begin_short_backtrace::h1d539524a38b1283
  31:        0x1022d3e9c - std::rt::lang_start::{{closure}}::h3d8df7b89561f540
  32:        0x10451235c - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::ha1c2447b9b665e13
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/ops/function.rs:606:13
  33:        0x10451235c - std::panicking::try::do_call::ha57d6d1e9532dc1f
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:483:40
  34:        0x10451235c - std::panicking::try::hca0526f287961ecd
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:447:19
  35:        0x10451235c - std::panic::catch_unwind::hdcaa7fa896e0496a
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panic.rs:137:14
  36:        0x10451235c - std::rt::lang_start_internal::{{closure}}::h142ec071d3766871
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/rt.rs:148:48
  37:        0x10451235c - std::panicking::try::do_call::h95f5e55d6f048978
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:483:40
  38:        0x10451235c - std::panicking::try::h0fa00e2f7b4a5c64
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:447:19
  39:        0x10451235c - std::panic::catch_unwind::h1765f149814d4d3e
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panic.rs:137:14
  40:        0x10451235c - std::rt::lang_start_internal::h00a235e820a7f01c
                               at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/rt.rs:148:20
  41:        0x10222c6a4 - _main

can't seem to find where this line:
let PI: f32 = 3.1415927;

is. I saw it in some shader files in my projects /tmp directory. I removed them but the error is still happening. I'm assuming this is form a shader. It needs to be const instead of let  Anyone know where the source is on this?

We could use a git dependency, through cargo patching.
Perhaps we should hold off just a little while longer as it seems they are still working out how to solve the Arced resources.
Good that they also fixed the usage of a depth buffer without a stencil bit, which is an issue we've encountered and worked around

Thanks for the PR

#168 is out of date right now (we've made some pretty significant changes to the renderer to get it on the web), so I wouldn't close this just yet

Ok I have reopened and added a commit to update the shader let statements. I can now build my game and examples successfully against this branch

Awesome, thanks. Can you try fixing the Linux build? Once that works, @ten3roberts can try using a Git version of wgpu and hopefully we won't run into any issues on the web, and this PR can be merged.

ok cargo nextest run --workspace passing for me locally.

Seems this upgrade has revealed some issues in some of the shaders. Going to take another pass and correct them.

Ok I went through and updated shaders that were having compatibility issues. I tested most of the examples with the main ambient executable and the executable from this branch and things are looking consistent.

Unfortunately it is not working on the web.

This also occurs with a small example project, and is mentioned in https://github.com/gfx-rs/wgpu/issues/3430
Using git does not work either as they have other breaking changes such as a quite reworked TextureFormat api, and those commits are from before the WasmAbi fix.
Unfortunately

How hard would it be to accommodate the breaking changes? I imagine we'll have to do that anyway for wgpu 0.16 or what have you

I updated a small example project, and it wasn't too many changes. However, it does clear the screen with a clear color, but nothing is rendered, while rendering with storage buffers worked on 0.14, haven't looked into exactly why it happens.
Other than that I am not sure how many more breaking changes are planned for 0.16, or when they are planning on releasing it.
Ambient does currently work on 0.14, and I fear that using the trunk will cause us to have to keep up even more when they break and unbreak things, rather than once for a stable release.
So I am not currently sure how to go about it

Heads-up - wgpu 0.16 is now out. Would it be possible to update this PR? That should make it possible to merge afaict 🙏

working on an update now

Awesome, thank you 🙏

Ok 2089caa9158c448bf198e40fd54813848c37b293 brings it up todate with 0.16.0 My test project looks good and I checked a bunch of the critical examples they look good. The github build is passing green.
I think this is unrelated. When I run  cargo nextest run --workspace locally I get the following errors from api_macros:
   Compiling ambient_api_macros v0.2.0-rc2 (/Users/kevzettler/code/Ambient/guest/rust/api_core/api_macros)
   Compiling wit-bindgen v0.4.0
error[E0277]: the trait bound `(Option<_>, std::string::String): AsRef<std::path::Path>` is not satisfied
   --> api_core/api_macros/src/main_macro.rs:104:29
    |
104 |             main_impl(body, (None, AMBIENT_TOML.to_owned()))
    |             ---------       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `AsRef<std::path::Path>` is not implemented for `(Option<_>, std::string::String)`
    |             |
    |             required by a bound introduced by this call
    |
note: required by a bound in `main_impl`
   --> api_core/api_macros/src/main_macro.rs:5:56
    |
5   | pub fn main_impl(item: TokenStream, ambient_toml: impl AsRef<Path>) -> anyhow::Result<TokenStream> {
    |                                                        ^^^^^^^^^^^ required by this bound in `main_impl`

error[E0277]: the trait bound `(Option<_>, std::string::String): AsRef<std::path::Path>` is not satisfied
   --> api_core/api_macros/src/main_macro.rs:136:29
    |
136 |             main_impl(body, (None, AMBIENT_TOML.to_owned()))
    |             ---------       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `AsRef<std::path::Path>` is not implemented for `(Option<_>, std::string::String)`
    |             |
    |             required by a bound introduced by this call
    |
note: required by a bound in `main_impl`
   --> api_core/api_macros/src/main_macro.rs:5:56
    |
5   | pub fn main_impl(item: TokenStream, ambient_toml: impl AsRef<Path>) -> anyhow::Result<TokenStream> {
    |                                                        ^^^^^^^^^^^ required by this bound in `main_impl`

@kevzettler Yeah I'll fix that

@ten3roberts Any reason to not merge this now?

I've dealt with the merge and looked through cargo cf example check-all. Web support's up to @ten3roberts .

Alrighty, all good from my end. Thanks so much for this, @kevzettler! Much appreciated 🚀


code sharing

I look forward to your code sharing.

@malzantot any update on this code?

@malzantot any update on this? I would like to try using your approach for a university project of mine, which will be due soon. Thanks in advance!

@malzantot Any update on this?

Hi everyone, we are sorry for the delay which is out of our hands due to being busy on other projects as well as on preparing a newer version of the paper. Preparing the code for public release would take us a few bit of time to make it easy for everyone to run and use. Please expect an update within the upcoming two weeks.
Thanks for your understanding.

Hi everyone, Sorry for the delay on our side due to being busy with a lot of projects. The repo is updated now with the code . The version in the code have more improvements than the algorithm described in our previous version of the paper, and the updated paper will also be released soon. Thanks!


Bug: build issue wrong path

Describe the bug
In all PRs the build is being broken due to wrong path based on my understanding.
here is the issue we got: npm ERR! path /home/runner/work/ai/ai/package.json
related to #143 and #141 and #101
Steps to reproduce

open a PR
you will see the issue
here is an example action: https://github.com/open-sauced/ai/actions/runs/5098790076/jobs/9166141097?pr=143

Affected services
browser-extension
Platforms
No response
Browsers
No response
Environment
No response
Additional context
No response
Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

Here is a simple clear case for only changing the readme: https://github.com/open-sauced/ai/pull/145

I have a fix. I didn't properly set up the workflow envinroment.


Add support for click_listener in GsiButtonConfiguration

Google has added a new click_listener option to the GsiButtonConfiguration that allows users to specify a function to be called when the Sign in with Google button is called. Adding support for this property enables users of the library to recognize the start of an authentication flow, based on which other components' state may be reset.
Refs https://developers.google.com/identity/gsi/web/reference/js-reference#click_listener
Closes https://github.com/MomenSherif/react-oauth/issues/40

Any maintainers here who can get this merged and released please? 🙂

Will check and release it tomorrow

Thank you @niksauer<EMAIL_ADDRESS>released 🎉


Race condition

Hi,
I have found a bug but I'm not sure how to fix it. I have a document that includes a title for a response, parsing the file with apib2json does not return the title in meta object. Looking at the code, this line has the test to decide if the title should be set or not https://github.com/o5/apib2json/blob/master/lib/apib2json.js#L114
if ('meta' in httpTransaction && 'title' in httpTransaction.meta) {
    item.meta.title = httpTransaction.meta.title;
}

The issue is that httpTransaction.meta is empty at this point, inside the closure httpTransaction.content.forEach((rContent) => {}
But if I print httpTransaction.meta just before entering the closure the value is there.
Sorry, I'm not really a nodejs developer, I know for sure is a race condition but not sure how to fix it, I hope you can help me with this.
Cheers,
Mario

@o5 Here is the same custom_api.apib.md, the account/me endpoint have 2 requests, one without a title and the second one with a title.
FORMAT: 1A

# Custom API

## API Blueprint
+ [Link to Apiary](http://docs.customapi1.apiary.io/)

# Group Backend

## Account [/backend/v1/account]
### Login [PUT /backend/v1/account/login]
+ Request Success (application/json)
    + Attributes
        + login: username (string, required)
        + password: pwd (string, required)

+ Response 200 (application/json)
    + Attributes
        + access_token: `xxx` (string)

+ Request Bad Credentials (application/json)
    + Attributes
        + login: username (string, required)
        + password: pwd (string, required)

+ Response 401 (application/json)
    + Attributes
        + code: `401` (number, required)
        + error: `AUTH_FAILED` (string, required)
        + message: `Invalid login or password` (string, required)

### Me [GET /backend/v1/account/me]
+ Request (application/json)
    + Headers

            Authorization: Bearer <access_token>

+ Response 200 (application/json)
    + Schema

            {
                "$schema": "http://json-schema.org/draft-04/schema#",
                "properties": {
                    "id": {
                        "type": "number"
                    },
                    "first_name": {
                        "minLength": 1,
                        "type": "string"
                    },
                    "last_name": {
                        "minLength": 1,
                        "type": "string"
                    }
                }
            }

+ Request Second request type (application/json)
    + Headers

            Authorization: Bearer <access_token>

+ Response 200 (application/json)
    + Schema

            {
                "$schema": "http://json-schema.org/draft-04/schema#",
                "properties": {
                    "id": {
                        "type": "number"
                    },
                    "first_name": {
                        "minLength": 1,
                        "type": "string"
                    },
                    "last_name": {
                        "minLength": 1,
                        "type": "string"
                    }
                }
            }
# Group Frontend

## Article [/frontend/v1/articles]
+ Attributes (object)
    + id: 250FF (string, required)
    + title: `Some title` (string, required)

### Retrieve articles [GET]
+ Response 200 (application/json)
    + Attributes (Article)

Here is the output just for those 2 requests
    "[GET]/backend/v1/account/me": [
        {
            "meta": {
                "type": "response",
                "title": null,
                "group": "Account",
                "statusCode": "200"
            },
            "schema": {
                "$schema": "http://json-schema.org/draft-04/schema#",
                "properties": {
                    "id": {
                        "type": "number"
                    },
                    "first_name": {
                        "minLength": 1,
                        "type": "string"
                    },
                    "last_name": {
                        "minLength": 1,
                        "type": "string"
                    }
                }
            }
        },
        {
            "meta": {
                "type": "response",
                "title": null,
                "group": "Account",
                "statusCode": "200"
            },
            "schema": {
                "$schema": "http://json-schema.org/draft-04/schema#",
                "properties": {
                    "id": {
                        "type": "number"
                    },
                    "first_name": {
                        "minLength": 1,
                        "type": "string"
                    },
                    "last_name": {
                        "minLength": 1,
                        "type": "string"
                    }
                }
            }
        }

Hi, sorry for not answering this before.
I did look more closely to issue and I found that when a Request has no attributes it is not rendered, no matter it has headers. I'm not sure if this is an issue for the way that I should expect the library to work.
Here is a reduced test case.
FORMAT: 1A

# Custom API

## API Blueprint
+ [Link to Apiary](http://docs.customapi1.apiary.io/)

# Group Backend

## Account [/backend/v1/account]
### Login [PUT /backend/v1/account/login]
+ Request Success (application/json)
    + Attributes
        + login: username (string, required)
        + password: pwd (string, required)

+ Response 200 (application/json)
    + Attributes
        + access_token: `xxx` (string)

+ Request Bad Credentials (application/json)
    + Attributes
        + login: username (string, required)
        + password: pwd (string, required)

+ Response 401 (application/json)
    + Attributes
        + code: `401` (number, required)
        + error: `AUTH_FAILED` (string, required)
        + message: `Invalid login or password` (string, required)

+ Request Ping (application/json)
    + Headers
        + Accept: application/vnd.creditar.v1+json

+ Response 200 (application/json)
    + Attributes
        + pong: `xxx` (string)

@mariochavez Could you check it in 0.3.0-4-g8ee2b48? Thanks!

I just tried the latest version with attached test case and looks ok to me. If not create new issue please.


Barreleye: CT Run, Evaluate logs and open issues accordingly

Maintained here.. https://github.com/openbmc/openbmc-test-automation/issues/220

Oops, We need to assign estimate to other issue #220 then (It should be disturbed between Barreley, Witherspoon and Palmetto. )

Probably add 2 Story point for each System per sprint.. if needed to accommodate as part of the sprint plan..


Fix print layout of DG

Just for cosmetics' sake. To be merged (to mark as non-draft) after the semester is over.

Codecov Report

Merging #560 (9a3d820) into master (479610a) will decrease coverage by 0.20%.
The diff coverage is 45.45%.

@@             Coverage Diff              @@
##             master     #560      +/-   ##
============================================
- Coverage     65.25%   65.05%   -0.21%
+ Complexity      737      736       -1
============================================
  Files           147      147
  Lines          2590     2598       +8
  Branches        282      285       +3
============================================
  Hits           1690     1690
- Misses          749      753       +4
- Partials        151      155       +4

Impacted Files
Coverage Δ

...main/java/seedu/foodrem/commons/core/Messages.java
0.00% <ø> (ø)

...seedu/foodrem/storage/JsonSerializableFoodRem.java
100.00% <ø> (ø)

...odrem/logic/commands/itemcommands/SortCommand.java
76.92% <33.33%> (-13.99%)
:arrow_down:

.../logic/commands/itemcommands/FilterTagCommand.java
88.88% <50.00%> (-11.12%)
:arrow_down:

...odrem/logic/commands/itemcommands/FindCommand.java
76.92% <50.00%> (-13.08%)
:arrow_down:

src/main/java/seedu/foodrem/model/item/Item.java
51.13% <0.00%> (-2.28%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature: Simple health checking

Create a an API-X component that performs basic health checks (e.g periodic HEAD requests) and removes unhealthy services from an LDP service instance registry.
The intent of this is to provide simple-to-use functionality out of the box for those who unable to leverage an existing infrastructure that offers health checking and registry maintenance, such as consul or zookeeper.
It should straightforward to use this or not use it.
This may be demonstrated in a Docker demo this by having the user run a local service (i.e. on their own machine) that self-registers, and is subsequently killed by the user via ctrl-c
So a demo might look like:

user starts API-X
runs local service on command line which self-registers itself as an extension
verify that it's working via API-X
Shut down local service
Should get 503 error if there are no available services to satisfy the request

Interesting that that's a 503. If you have time can you point me at the spec that details that?

@ajs6f There's nothing in the API-X design doc that spells that out, but this would be a good opportunity to do so.  503 just seemed logical because:

There's an extension definition (still) in place (from when the extension self-registered) which spells out the intent that API-X exposes the given service at a particular location, but
There are no services instances available to handle the request


Voyager doesn't load properly in IE 11 or Edge browser

Both in IE 11 and Edge, the  tag is empty and nothing is generated inside of it. No messages are displayed in the console indicating any sort of issue. The end result is that Voyager doesn't load or display on the page.

Voyager supports the following browsers:

Google Chrome, desktop and mobile
Mozilla Firefox, desktop and mobile
Apple Safari, OSX and iOS

IE11 is discontinued, and Edge currently doesn't support HTML Custom Elements. Future versions of Edge will support this feature (see https://caniuse.com/#search=custom elements).


Need to reevaluate ClusterRole access

Describe the bug
We may need to be able to do:
- apiGroups:
  - ""
  resources:
  - secrets
  - namespaces
  verbs:
  - 'get'
  - 'list'
  - 'watch'

I'm not sure offhand about what we need "namespaces" for, but the code was failing without it (see this issue).
Need to also see if anything else is missing.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.

@juliev0 I will have a PR to add namespace back, but this is totally configurable by any users for numaplane controller, right?

@juliev0 I will have a PR to add namespace back, but this is totally configurable by any users for numaplane controller, right?

Yeah, I’m thinking we should make the open source version whatever the basic expectation is for standard operability. Secrets is something that Numaplane is supposed to be able to read by default. I guess namespace probably is but I’m not sure offhand in what way. (Check namespace exists before writing to it?)


Fix close connection after usage.

Close connection after usage.
Due to offical documentation, use resp.Close = true .

Thanks!


Eloquent devel

launch bringup

Hi @youngday , thanks for pointing out the mismatch in README.md.
Currently, I'm working on foxy-devel. I found the latest NAV2 in Foxy is much more stable.  So I plan to change the default branch to foxy-devel as long as the slam_toolbox and some packages are ready and verified.
If you have any other suggestions, please let me know, thank you!


Use tox test runner rather than an unportable shell script

See https://tox.readthedocs.org/

Updated to do this. I had never heard of tox before. It is pretty cool. Thanks.


Login Page as first render.

Suggested Changes:
I think would be better if the login was the first thing to appear on the screen if the user has not been logged, currently the Available concerts is the first page to be rendered.
Current first rendered screen:

Sugested to be the first rendered screen:

This issue is not necessary anymore since the user cannot access the booking section, because the user has to be logged in first, we can assume not logged users can just browse available concerts, but they will not book unless they are logged in,
in conclusion, this issue has been solved on the pull https://github.com/Diegogagan2587/Book-a-concert-front-end/pull/94


Linux-3.17.0-rc1-armv7-x0.3 on CM-510 board, does not boot.

Hello,
I am trying to boot Linux 3.17 Kernel on CM-510 board, but it does not boot. The last output I am able to see is:
Booting kernel from Legacy Image at 00200000 ...
Image Name:   Linux-3.17.0-rc1-armv7-x0.3
Created:      2015-01-18  11:58:43 UTC
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3948368 Bytes =  3.8 MB
Load Address: 00008000
Entry Point:  00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
I have made different checks in order to find out what's wrong:

I have tried different tty console specification on bootargs : ttyS0, ttyS1, ttyS2, ttyS0 ... just to make sure the problem is not related to the standard output specification during booting process.

2)In order to recieve further information about the issue, I have activated "earlyprintk" in menuconfig.
CONFIG_EARLY_PRINTK=y
3)Lastly, I have actived Kernel Low Level Debugging
CONFIG_DEBUG_LL=y
But, always the same...
I print my used bootargs:
CM-A510>> printenv
loads_echo=0
rootpath=/mnt/ARM_FS/
mtdids=nand0=dove-nand
mtdparts=mtdparts=dove-nand:4m(boot),-(rootfs)
arcNumber=3020
CASset=min
MALLOC_len=5
bootargs_root=root=/dev/nfs rw
bootargs_end=:::dove:eth0:none
image_name=kernel.img
tftpbootcmd=tftpboot 0x2000000 ${image_name}; setenv bootargs ${console} ${mtdparts} ${bootargs_root} nfsroot=${serverip}:${rootpath}  ip=${ipaddr}:${se
standalone=fsload 0x2000000 ${image_name};setenv bootargs ${console} ${mtdparts} root=/dev/mtdblock0 rw ip=${ipaddr}:${serverip}${bootargs_end} usb0Mode;
bootnand=sflash read a0000 0x2000000 0x300000;setenv bootargs ${console} ${mtdparts} ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw usb0Mode=${usb0Mode};
disaMvPnp=no
usb0Mode=host
usb1Mode=host
lcd0_enable=0
lcd1_enable=1
lcd0_params=1280x768-24@60
lcd1_params=640x480-16@60
dnsip=<IP_ADDRESS>
loadaddr=0x200000
baudrate=115200
console=ttyS0,115200
ethprime=egiga0
ethaddr=00:01:c0:14:cd:d0
eth1addr=00:01:c0:14:cd:d9
serial#=CM-A510-C800-D1024-N512-E2-U4-I-A-V100-140302-0001c014cdd0-0001c014cdd9
ethact=egiga0
bootfile=bootscr.img
nemo_bootcmd=for j in 2 1 0; do
echo stepj $j;
mmc rescan $j;
for i in 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19; do
mmc rescan $j;
if fat load mmc $j:$i ${loadaddr} /uImage; then
bootm ${loadaddr};
fi;
if fat load mmc $j:$i ${loadaddr} /boot/uImage; then
bootm ${loadaddr};
fi;
if ext2load mmc $j:$i ${loadaddr} /uImage; then
bootm ${loadaddr};
fi;
if ext2load mmc $j:$i ${loadaddr} /boot/uImage; then
bootm ${loadaddr};
fi;
echo no device found in mmc $j partition $i;
done;
done
partition=nand0,0
mtddevnum=0
mtddevname=boot
filesize=2F0C44
fileaddr=200000
netmask=<IP_ADDRESS>
gatewayip=<IP_ADDRESS>
ipaddr=<IP_ADDRESS>
serverip=<IP_ADDRESS>
bootargs=root=/dev/nfs nfsroot=<IP_ADDRESS>:/home/devel/devel/cm-a510/a510 ip=dhcp console=ttyS0,115200 pm_disable useNandHal=4bitecc fbcon=rotate:1 usbe
stdin=serial
stdout=serial
stderr=serial
passDramInitTag=yes
mainlineLinux=yes
enaMonExt=no
pexMode=RC
disL2Cache=no
disL2Ecc=no
sata_dma_mode=yes
bootdelay=0
autoload=no
enaL2ExtraFeatures=yes
enaCpuStream=no
enaVpuPower=yes
enaGpuPower=yes
I would greatly appreciate your help in this matter
Thank you very much in advance.
GDobato

Don't you mean: "cm-a510" ?
http://www.compulab.co.il/products/computer-on-modules/cm-a510/
First, "Linux-3.17.0-rc1-armv7-x0.3" means you have a early branch, the current top of hte v3.17.x branch is "3.17.4-armv7-x3" so fix that first..
Second, this tree is device tree only, it looks like your just booting "uImage" so fix that..
Third, i don't have this device, and have disabled all Marvell devices by default.
Sorry, Good Luck! Not my bug.
Regards,

Ok,
Thank you very much for your suggestions.
Best regards,
GDobato
Ok,
Thank you very much for your suggestions.
Best regards,
GDobato


Upgrade to Ubuntu 20.04

Just a minor thing: the Dockerfile uses 16.04 which is now out its main Long Term Support support (although it will have maintenance for a few years yet).
Please would you upgrade to 20.04.

The reason Docker is used is precisely not to have to upgrade dependencies every few years.
Even if the apt repositories and mirror disappear and the build stops working, the docker image layers will still be available and work.

Of course, you're welcome to fork it and I'd add a reference in the README


Inserted "Hub" on multiple occasions

@DarrylvanderPeijl : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Log model weights and gradients

Hey,
I want to log the model weights and gradients and visualize them as part of my experiments. Can you suggest where should I start for this?
Thanks

Model weights are typically saved after each epoch finishes. Removing this line will help you keep all the checkpoints.
For gradients, I believe that you probably have to add custom hooks. You may need to refer to the official document from mmcv/mmdet. We do record the gradient norm using mmcv apis, you can definitely check how mmcv obtains these values.

thanks


pull request for e2e test at 11/09/2016 13:26:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Very high CPU load on gulp watch and kitchensink.

Gulp immediately causes the CPU on the VM to go to 140% (3 CPU), without gulp watch it's at 1-2%.
Same goes for kitchensink on chromium and safari. (Using compiles semantic-ui files).
I don't have this issue on gulp watch on bootstrap.
Core i5 3,7Ghz, 32GB RAM, GTX 670.

Gulp watch and Chrome behaviors are independent. Watch doesnt trigger anything like an auto-reloader.
It does seem your VM is going a bit nuts however. The watch script is fairly simple, https://github.com/Semantic-Org/Semantic-UI/blob/master/tasks/watch.js
It's just watching a single directory for changes to assets, javascript or css. Any more info would be helpful.

I know they are, but it would feel odd creating two issues..
It IS simple and there are not many files, i regularly watch a php project with more than 300 files.
But gulp only consume 10% CPU on one core there...
I'll try and re-install the whole VM and see if that helps.
I guess the kitchensink have too many moving parts right?
Having so many semantic-ui objects on one page would probably never happen, so let's just ignore the chromium issue.

Testing on my crappy VM getting 3% CPU usage with negligible memory usage.

That's kind of what i expected.
Can this have anything to do with it?
[12:36:31] Warning: gulp version mismatch:
[12:36:31] Global gulp is 3.8.11
[12:36:31] Local gulp is 3.8.10
[12:36:40] Using gulpfile /var/www/semantic/gulpfile.js
[12:36:40] Starting 'watch'...

Shouldnt be an issue

I don't get it...
Now i used the Laravel Homestead vagrant box and:

added the latest virtualbox guestadditions to it
use the semantic ui included gulp only

But the CPU is still 100% when using gulp watch.
So i though, maybe it's my desktop computer that is the issue!
But after installing the same Laravel homestead setup and installing semantic-ui via npm install semantic-ui and choosing all defaults then running gulp watch....
...It still uses 100% CPU.

The gulp task and output are appearing correctly (although you are at high cpu usage)? Or is the task also not working correctly?

The gulp task and output are working correctly, but the high CPU usage on both Gulp & Chromium on the kitchensink makes the computer go to a crawl, reloading kitchensink to see changes takes more than 10 seconds on each reload.

Since I'm unable to reproduce your issues, you will have to take debugging into your own hands somewhat.
I'd recommend opening up watch.js and removing portions of code incrementally until your CPU usage returns normal results, then reporting back results.

@jlukic I'm already on it. You can close this issue and I'll open a new one if i find what is wrong.

You might also want to check out this function in node_modules/require-dot-file/ which uses recursion to walk up your directory tree. I'm going to add forced exit conditions to it now.

@jlukic Ok, then leave this thread open. I guess it would be good if someone else want to fiddle.

Published new version of module with maxDepth to prevent recursion. I don't think that should be the issue though since it wouldn't make it to the watch scripts if requireDotFiles was failing

I found the issue.
Apple have disabled TRIM for all 3rd party SSD hard drives on OS X Yosemite, so my random read speed was at 0.5MB/s and many times even lower. Patching TRIM and then reconditioning the SSD sent the speeds up to the normal values. Now compiling takes less than 2 seconds even on the Virtualbox.

@tmikaeld I'm having the same issue, running gulp inside the vagrant guest sends CPU usage from 1% to 125%. What is that about TRIM? I have no idea what that is :P Any chance you have a link to some sort of guide on how to fix it?

@powerbuoy Do you run a real Mac or a Hackintosh?

@tmikaeld real

@powerbuoy And you're using an external SSD for the Virtualbox?

@tmikaeld no the built in one

Oh that sounds a bit scary :P Any way to check whether it's enabled already? Running the same gulp task on the host is super fast and doesn't burden the CPU at all. Running it on the guest sends VBoxHeadless to >100%.

Yes, open up System Report, then you'll find it here:

Hmm i couldn't find that app in Mojave but I switched to NFS and now things are much better. Thanks for helping out!


Sibling resolver [JIRA: RCS-249]

This is very well tested. Not really.

Good update of original script on timeout by Taka:
Fun = fun(Host, Port, B, K) ->
              {ok, Pid} = riakc_pb_socket:start_link(Host, Port),
              try
                  {ok, RiakObject} = riakc_pb_socket:get(Pid, B, K, [{r, all},{timeout, 60000*5}], 60000*5),
                  case lists:any(fun({_, <<>>}) -> true; ({MD, _}) -> dict:is_key(<<"X-Riak-Deleted">>, MD) =:= true end, riakc_obj:get_contents(RiakObject)) of
                      true ->
                          VClock = riakc_obj:vclock(RiakObject),
                          ok = riakc_pb_socket:delete_vclock(Pid, B, K, VClock);
                      false ->
                          {Meta, Block} = hd(riakc_obj:get_contents(RiakObject)),
                          RO1 = riakc_obj:update_metadata(RiakObject, Meta),
                          RO2 = riakc_obj:update_value(RO1, Block),
                          ok = riakc_pb_socket:put(Pid, RO2,[{timeout, 60000*5}],60000*5)
                  end
              after
                  riakc_pb_socket:stop(Pid)
              end
      end.

I would like to include Taka's awesome tool to this pull request. Pending to next sprint.

Updated this branch; I believe I've addressed all your comments ^^;.

testtest

Given that this function could be used via external scripts (not only console), I'll change all io:format to log output.

force-pushed :imp:

Updated

Simple and effective :+1:

@borshop merge

For release note: Add a generic function for manual operations to resolve siblings of manifests and blocks
[posted via JIRA by Kota Uenishi]


"this is undefined" on SingleDatePickerInput

Hi! I'm facing a problem with SingleDatePicker. My implementation for SingleDatePicker was working fine but now when I try to render the component I'm getting an error:

The error is occurring in the SingleDatePickerInput.js file from the library. I was analyzing my code but I think it's fine, please take a look:
import React, { Component } from 'react';
import { SingleDatePicker } from 'react-dates';
import validateBirthdate from '../utils/validateBirthdate';

class DatePicker extends Component {
  state = { focused: null };

  handleFocusChange({ focused }) {
    this.setState({ focused });
  }

  render() {
    const {
      label,
      placeholder,
      input: { value = null, onChange },
      meta: { error, touched }
    } = this.props;
    const { focused } = this.state;
    const invalidInput = touched && error;

    return (

        {label}
        <SingleDatePicker
          id="birthdatePicker"
          placeholder={placeholder}
          date={value}
          focused={focused}
          onDateChange={onChange}
          onFocusChange={this.handleFocusChange.bind(this)}
          isOutsideRange={validateBirthdate}
          showClearDate
          noBorder
          block
          hideKeyboardShortcutsPanel
        />
        {
          invalidInput &&

            {error} do_not_disturb_on

        }

    )
  }
}

export default DatePicker;

I'm working with the latest version (18.2.0) of the library.
What's wrong? Any suggestions?

I'm running into this same bug, it appears to be introduced in version version 16.7.1 of the library.

What version of react?

I had the same bug, saw that there was a fix in v18.1.0 by Maja Wichrowska
(commit e376d2fb9b27ee7dd8938881fd1a3dbc7d8fcdf8).
update the react-dates package and it will solve you the problem.


SQL Server respecting Kubernetes limits?

Hi team, we've had an interesting issue in the AKS repo from a customer:
https://github.com/Azure/AKS/issues/3457
Can you let me know if there is anything needed on your side for SQL server to respect limits on the pod ?

Any news on this issue? We are facing OOMTerminated problems since upgrading our AKS cluster with SQL Server.

Yes, this is an issue that we see because SQL Server currently does not work with cgroup v2. we are working on this and I dont have a timeline on when this will be fixed but this is work in progress. We will keep you updated.

Any updates on this issue?

@amitkh-msft Is the work still in progress? Will it be fixed at all?
SQL Server is simply unusable in latest Kubernetes because of this.

yes, we will prioritize this over other items in the backlog. I may soon have an update on the timeline


Embrace JSON-LD

I think it is inevitable that JSON-LD paves its way through the current quagmire of formats and establishes itself as the only relevant (and true; it's ratified in W3C) standard for linking within and between JSON documents (read "resources" if you're picky about it). So however bad anyone feels it is (I quite like it, but nonetheless), I think it's going to be hard to ignore it.
I also feel that JSON-LD requires a very light change to most existing JSON documents, however they are specified (in Siren, JSON API, API Blueprint, etc.) in order to make the documents JSON-LD compatible. Just replace identifying URI property names with @id and you're set. Basically.
So, I'm wondering, has any steps, thoughts or anything else been spent or done to make Siren JSON-LD compatible?

Thank you for your suggestion.  Siren will not be JSON-LD compatible at this time.  If you're looking for hypermedia controls on top of JSON-LD, I'd like to recommend Hydra by @lanthaler.
Cheers.

Thanks for the quick reply! I know about Hydra, but feel Siren is more mature and has more widespread use, which is why I'd like to use it in a new, large project.
But I also think JSON-LD is so valuable that I find myself in a little pickle and don't know how to compromise.
So yea. Back to the drawing board.

IMO, the spec is influenced by real world implementations.  If you find siren and json-ld valuable, it would best help siren if you do an implementation and report back your findings, what worked, what didn't, etc.

A few comments here.  First, it is now 2018 and, as far as I’m concerned, Siren is still better suited for my use cases than JSON-LD (not a knock against JSON-LD, just an observation).  However, I do find the curation or schemas on scheme.org quite interesting.  It would be very cool to be able to somehow tie these together with Siren classes.  The big problem, as far as I can tell, is that I don’t see an obvious way to transform the various “semantic web” formats used on scheme.org into something like JSON scheme so that validation would be possible.


A small number of Sierra bibs windows aren't working

$ python sierra_adapter/report_adapter_progress.py

===============================================================================
bibs windows
===============================================================================
1999-01-01T00:00:00 -- 2018-09-26T07:50:41.661400
2018-09-26T09:17:28.186653 -- 2018-10-01T10:32:10.389905

I've run the "build missing windows" script once already, and they all failed.

This is fixed, though I’m not sure why it worked on that attempt. (Was the Sierra API just having a bad moment? Have all the records updated in that window been updated again? Library gremlins?)
Anyway, it's sorted, and we have better progress reporting in Slack to let us know when it fails next time:


Rename "payment" and "payment request" to  "Invoice" throughout Hypha

We want to use generic terms throughout Hypha.

@frjo We touched on this during the last Monday check-in. While I understand how "invoice" applies to many scenarios, not every project submits an invoice when they need payment. They also submit receipts for payment.


MVP: Button Integration with Immich's Photos Page

[x] Explore Immich's Web Documentation and Existing Pages

Review Immich's web documentation thoroughly to understand their design principles, UI elements, and overall aesthetic.

Explore existing pages within the Immich website to understand the current layout, navigation, and design patterns.

[x] Design UI Mockups: Use a design tool (Figma) to create mockups or wireframes for the new button or dropdown option.

Ensure that the design aligns with Immich's existing design language and follows their brand guidelines.

Consider the placement of the button or dropdown within the existing UI and how it will interact with other elements on the page.

[x] UI Component Creation: The button component:

Create a basic styled button component using Svelte or HTML/CSS.

Implement event handling to handle interactions such as clicks or hover effects.

[Alternative] Consider a possible dropdown component instead: Develop the dropdown component according to Immich's design standards.

Ensure that the dropdown is accessible and easy to use on both desktop and mobile devices.

[x] Integration with Immich Photos Page: Once the button and dropdown components are created, integrate them into the Immich Photos page.

Test the integration to ensure that the components function correctly within the existing UI and layout.

[ ] Responsive Design: Make sure that the new UI components are responsive and adapt well to different screen sizes and devices.

Test the mockups across various viewport sizes to ensure they maintain usability and functionality.

Button Integration into Immich's UI has been completed.


[BUG] ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.

Logging
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
Additional debug info:
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
Describe the bug
I have Lenovo Legion Y540 laptop & I am trying to set up AWS Kinesis Video stream with gstreamer in my oracle virtual box with ubuntu 22.04 OS.
I have followed all the steps and the whole setup is complete without any problem.
I want to stream video from my laptop's integrated camera to AWS KVS via this cpp sdk.
I can use my camera properly inside my ubuntu in virtualbox with "cheese ."
I used this command from https://github.com/awsdocs/AWS-Kinesis-Video-Documentation/blob/master/doc_source/examples-gstreamer-plugin.md:-
Example 2: Encode and Stream Video from a USB Camera on Ubuntu:-
$ gst-launch-1.0 v4l2src do-timestamp=TRUE device=/dev/video0 ! videoconvert ! video/x-raw,format=I420,width=640,height=480,framerate=30/1 ! x264enc  bframes=0 key-int-max=45 bitrate=500 ! video/x-h264,stream-format=avc,alignment=au,profile=baseline ! kvssink stream-name="YourStreamName" storage-size=512 access-key="YourAccessKey" secret-key="YourSecretKey" aws-region="YourAWSRegion"
After using  v4l2-ctl --list-devices, my devices also show in output, but i am getting this error:-

Here is an output of gst-device-monitor-1.0:-

Please help me in resolving this issue.
OS:- Windows 11 with Oracle VirtualBox 6.1.40 with Ubuntu 22.04

@Karthiktmv ,
This is likely a source error and not related to KVS. Please try using your source in a GStreamer pipeline set up with other sinks to verify your source is able to reliably stream. Feel free to reopen if you face the issue only while using kvssink, but works with other sinks.

Hi Disa, I am new to this whole KVS and I am not that technically that aware about how it works, I just want to get it up and working so that i know it's working on my system. Can you kindly help me with the code as well to start the streaming. Also today when i again tried using "gst-device-monitor-1.0" I am getting this for the same intergrated laptop webacm :-

With the same command that I used for streaming earlier from AWS KVS documentation, again I got the internal streaming error.
Here is the output of "gst-inspect-1.0 kvssink" if that will help:-

I know I am sounding like a noob but please help me out.


nginx no ssl_certificate after migrate data to a new server

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Hello all,
I have recently started migrating Bookstack to a new server, as I wasn't quite in the Docker game before I didn't do a very good job of setting it up with the data accordingly, now I have a completely new system set up and wanted to migrate the data. So far all is well, the new data is now over there. However, as soon as I start the server I get the following error message: (Attention Docker environment) bookstack docker:
2022/11/08 06:06:12 [emerg] 1614#1614: no "ssl_certificate" is defined for the "listen ... ssl" directive in /config/nginx/site-confs/default.conf:3
Anyone of you a idea? I use the linuxserv docker image
Exact BookStack Version
inuxserver.io version:- v22.10.2-ls48 Build-date:- 2022-11-03T17:18:25+01:00
Log Content
2022/11/08 06:06:12 [emerg] 1614#1614: no "ssl_certificate" is defined for the "listen ... ssl" directive in /config/nginx/site-confs/default.conf:3f
PHP Version
8.0.25
Hosting Environment
Ubuntu 22.04.1 - Docker-Compose - Nginx Proxy Manager - Portainer
the old server:
Ubuntu 20.04 - Docker-Compose - Traefik - Portainer

Hi @michaelortnersanube,
I'm not overly familiar with the linuxserver container nginx setup, but I'd guess that maybe the old nginx config overrides are not compatible with the new setup.
Before anything, backup your old data first.
Within the mounted volume for the bookstack container, that maps to /config, you should have an nginx directory. You could try stopping the containers, delete that nginx directory to clear any old config, then restart your container setup. The nginx dir should be recreated upon restart with fresh files. I just gave this a test on my system to ensure that's that happens.
Let me know how that goes.

Hello @ssddanbrown ,
thanks! Now it works :)


Refactor of connector's constants

Refactor of the Hazelcast, Cassandra and ReThink connector constant’s keywords, so that they do not mention sink/source
Settings traits improved so that they do not need each constant to be declared when they are extended. Instead they only need connector's prefix to be declared.

@pedrobento988 Can you rebase and fix the merge conflicts?

Can you confirm me if the master's tests are working?
I was rebasing our code, but meanwhile I was having some weird test results.
So I run your master's tests and I had the same errors. The test report is attached below:
test_report.zip
Can you help me?

@pedrobento988 Fixing master now, we had some regression.

@pedrobento988 tests are fixed. Can you try again?

Rebase is complete. PR is updated


Fix Issue: App not launching when tapping on Push Notification

Summary:
This PR fixes an issue where tapping on a Push notification does not launch the app on Android.
Issue Details:

When the app is not completely closed, tapping on a Push notification opens the app as expected.
However, when the app is minimized and in the background, tapping the Push notification does not launch the app.

Fix:

The return value of onPushNotificationClicked was changed from true to false, ensuring that the app launches correctly when minimized and a Push notification is tapped.

Request for Feedback:
I would appreciate any feedback on potential side effects of setting the return value of onPushNotificationClicked to false. As of now, no major issues are anticipated, but please let me know if there are any concerns.

By submitting this PR, I hope to resolve the issue related to Push notifications not launching the app as expected.
Let me know if you need any further modifications!

Thank you for your contribution.

??
Although I push the Merge button,


Docs: Add 'Style Guide for Pull Requests' section in CONTRIBUTING.md

Category

[x] Documentation
[ ] Resource Addition

Description

We need to add a section named 'Style Guide for Pull Requests' in CONTRIBUTING.md and it should be located after the 'Style Guide for Commit Messages' section.
Suggested Markdown:
## Style Guide for Pull Requests

There can be three types of PRs for this repository:

- `Docs`: Changes related to documentation
- `Chore`: Changes related to the codebase, but unrelated to the UI of the website or adding a new feature
- `UI`: Changes related to the UI of the website
- `Feat`: Changes related to adding a new feature

When you are opening a PR, ensure that you are providing the correct type in the PR title in the below format:

```
Docs: Add MDN Web Docs
```

@Sriparno08  can you please assign it to me

@Sriparno08 please review the PR #85 and let me know if any changes is required.


luarocks make --pack-binary-rock creates architecture-dependant rocks

luarocks make --pack-binary-rock creates architecture-dependant stones while it seems to be not really necessary.
For example such rocspec:

package = "example-rock"
version = "1.0.0-1"
source = {
   url = "" -- Use `luarocks make`
}
description = {
 ...
}
supported_platforms = {
   "unix"
}
dependencies = {
}
build = {
   type = "none",
   install = {
      bin = {
         "bin/example-script"
      }
   }
}

use only shell script example-script which is not compilied by any means, though it is made in
example-rock-1.0.0-1.linux-x86_64.rock.

I think this could solve it, but I'm not sure if this isn't too general:
https://gist.github.com/1865176
It treats everything that starts with "#!" as arch-independent.

Hmm... I looked only at this patch and did not look at the LR source, and I have two questions: (1) what about Lua files without !# in them? And (2), is_actual_binary is probably not the best name for a function that decides arch-dependence...

Agreed, it is not the most inspired of names. I think I have to go backwards to explain this:
(2) This function is used in the context of the bin/ subdirectory only, and was created to tell apart compiled files from scripts and wrappers (right now I'm doubting the necessity of distinguishing the latter two, though).
(1) Since they're all from bin/, there should be no Lua files without !# in them. Other Lua files, such as modules, are not checked with fs.is_actual_binary.

The more I think about this, the more I believe that the behavior in that patch is okay. The may be some false positives still lingering, but I can deal with them when they come up.


cling (new formula)

Adds the cling C++ REPL of which there is no released version: https://root.cern.ch/cling

The build process involves cloning two extra dependencies (llvm and clang) into the source tree (https://github.com/vgvassilev/cling#building).
The reason for the manual install commands with the temporary install location is that several other clang and llvm binaries and libraries are produced as part of the build process, and I didn't want to include them. Instead I pick out only the specific resources that should end up in /usr/local.
The static clang library is required at runtime however, so this is installed to the lib folder.

Sure thing @dunn - change committed and squashed.


docker-compose up --build --detach seems to randomly pick either development or production mode

I followed the instructions in the Serverpod logs to start my server.
The step docker-compose up --build --detach seems to sometimes pick development or staging mode (where Postgres runs on port 5432), or development mode (where Postgres runs on port 8090). Which port it picks seems to be random.
Starting the server using dart run bin/main.dart defaults to development mode. So it can't find the Postgres server sometimes, because it is looking for Postgres on port 8090, but it started on port 5432.
I have no idea how to tell docker-compose up which Postgres config to use. It is not documented.

Actually docker ps tells me Serverpod attaches to <IP_ADDRESS>:8090->5432/tcp. So the inability of the client to connect to the server must be some other issue. I'll close this and re-open if I narrow down the actual issue.


Waffle.io test

example issue created !

testing comment capability of Waffle.io.
and markdown code.


Update to Chakra v1

Thanks for this missing Chakra Paginator.
Unfortunately it doesn't work with Chakra v1: Error: Cannot find module '@chakra-ui/core'.
I think it should work when changing the imports form @chakra-ui/core to @chakra-ui/react as described in the migration docs.

Hey! Thanks for reaching. You are completely right and I will be bumping Chakra version to v1 and fix any other API difference it might be. The fix will be available in the next few days!
Thanks for bringing this up. I'm glad you like it

Hey! Thanks for reaching. You are completely right and I will be bumping Chakra version to v1 and fix any other API difference it might be. The fix will be available in the next few days!
Thanks for bringing this up. I'm glad you like it


Align the vertx lib to whatever latest quarkus uses...

Fixes #

Proposed Changes

as per title using 4.4.4 (since our Quarkus 3.2 uses that)

FWIW, there is a newer version: 4.4.6, but that's not aligned with our version of Quarkus.....

Release Note

Docs

/retest

/test channel-integration-tests-sasl-ssl

/test reconciler-tests-namespaced-broker

/test reconciler-tests

/retest

/retest


Is this lib died?

I dont see any improvements in 2 years, i dont know if use this in production is a good idea.

It's not, may I suggest https://github.com/alexandre-fernandez/astro-i18n?

You could also check out my tiny package: https://github.com/e3stpavel/astro-nanointl

I think this lib had died.


When gulp is running, after few minutes it freezes my computer

When gulp is running, after few minutes it freezes my computer?

Did you try to build a minimal example and comment out some plugins? Is your code in a public repository?

Here is the code of the gulpfile.js.
'use strict';

var gulp = require('gulp');

// Installed Plugins
var autoprefixer = require('gulp-autoprefixer');
var sass = require('gulp-sass');
var scss = require('gulp-scss');
var minifycss = require('gulp-clean-css');

var jade = require('gulp-jade');
var pug = require('gulp-pug');
var kit = require('gulp-kit')

var coffee = require('gulp-coffee');
var uglify  = require('gulp-uglify');
var concat = require('gulp-concat')

var plumber = require('gulp-plumber');

var livereload = require('gulp-livereload')
var watch = require('gulp-watch');
var connect = require('gulp-connect');

// SASS

gulp.task('gulp_sass', function() {
	gulp.src('*.sass')
		.pipe(plumber())
		.pipe(sass())
		.pipe(autoprefixer({
			browsers: ['last 2 versions'],
			cascade: false
		}))
		.pipe(minifycss())
		.pipe(gulp.dest(''))
		.pipe(connect.reload());
});

// JADE

gulp.task('gulp_jade', function() {
	gulp.src('*.jade')
		.pipe(plumber())
		.pipe(jade({
			pretty: true
		}))
		.pipe(gulp.dest(''))
		.pipe(connect.reload());
});

// WATCHING

gulp.task('watch', function() {
	connect.server({
		root: '',
		livereload: true,
		port: 4000,
		host: 'localhost',
		https: false
	});
	gulp.watch('*.sass', ['gulp_sass']);
	gulp.watch('*.jade', ['gulp_jade']);
});

// DEFAULT TASK

gulp.task('default', ['gulp_sass', 'gulp_jade', 'watch']);

I see nothing unusual in your setup. Well, you should use return for each function task, but gulp 3.x should still work without. Does your computer freeze with any task or only default task? How about starting gulp gulp_jade or gulp gulp_sass only?

My machine run soothly until an unless I start the gulp (any task).

@mittalyashu sorry but this isn't a support forum.  Please direct support questions to StackOverflow.

I know that this is not a support forum. I have searched everywhere about this problem and there are lots of other people too, who are facing the same problem.
But the thing is, still I didn't found any solution, then I thought, there might be a problem in the gulp itself.


How can I disable render in docker container.

As the title mentioned, I require running the env in a docker container, so I hope to disable render function.

Have you tried using software rendering? OSMesa doesn't require a GPU or an X server, so it should work fine on a headless docker container. dm_control will automatically fall back on using OSMesa if it can't use either of the GPU backends, although you can also force it by setting the environment variable MUJOCO_GL=osmesa.

Rendering contexts are created lazily when the physics.contexts property is accessed, so provided that you're not actually creating Camera instances or calling physics.render() yourself then in most cases there will be essentially zero cost associated with software rendering support. In any case, creating an OSMesa context is quite cheap in comparison to the cost of compiling the model.

Closing this because I don't think there's a strong enough case for disabling rendering support entirely. Using the OSMesa backend and not calling physics.render should deliver almost the same performance since OSMesa context creation is fairly cheap, and only happens once per physics instance.


Failed to load plugin "obsidian-icon-folder"

Upon opening my vault, I got that error. I checked for plugin updates, updated what I could, restarted it, & still got the same error. I disabled it and tried enabling it, but I get the same error when I try to enable it. Even upon uninstalling it and reinstalling it, I still get that error.

Seems like it is related to #566.


Data Template Update (version 2)

following on from #49 and #239

vocab changes implemented and linked to format;
@cmspinto to send latest version of template to Joana; and also inform Nikki when ready to update data standard;

@cmspinto @pcrjoana I am just updating the JCDP data standard in line with the latest version of the data format template - The data right holds contact field still seems to exist in the template? We discussed removing that contact, and just having the contact for the data custodian, mainly to remove the need for data owners to be in EDMO as this may be off putting and reduce data submissions. The data custodian contact description also still referenced the previous field label - 'DataOriginator' so could that please be amended?
Second point - under 'Cue' we have 'breach' but under 'behaviour' we have 'breaching clear out of the water' which isn't supported by the description in the data standard - can the behaviour vocab be the same as cue, and just have 'breach'?

new version (2.0) is published on website https://www.ices.dk/data/Documents/Cetaceans/Cetaceans_data_template.zip

@neil-ices-dk Just sent it over! We will have to sort out the labels in the Behaviour  vocab, as some of the codes have a "cetaceans" prefix, which is coming from the ESAS project. This issue will be raised with the vocabulary management group.

@pcrjoana Joana - as long as we can keep the simplified header in the data standard and the data template i'm not too worried - we have already adjusted the breaching category to not show 'clear of the water' as it is in the vocab.

@neil-ices-dk @pcrjoana @cmspinto @NikiClear so are we essentially ready for the system to go live to accept data?? Our next meeting isn't until the 28th, I am on leave next week - it would be great if we could open the system up this week and flag it's ready. Need to make sure:

the template on the landing page is ok (@pcrjoana - do we need to wait for the vocab meeting outcome?)
the system is clear of any test data @cmspinto
JCDP data standard is made available (we can circulate via email in advance of it getting published online) @NikiClear
Anything else?

@neil-ices-dk @pcrjoana @cmspinto @NikiClear so are we essentially ready for the system to go live to accept data?? Our next meeting isn't until the 28th, I am on leave next week - it would be great if we could open the system up this week and flag it's ready. Need to make sure:

the template on the landing page is ok (@pcrjoana - do we need to wait for the vocab meeting outcome?)
the system is clear of any test data @cmspinto
JCDP data standard is made available (we can circulate via email in advance of it getting published online) @NikiClear
Anything else?

There is need to wait for the vocab meeting but we can't open submissions yet. I'll work on the basic data validation tomorrow, which Carlos has already started.
Do you have any checks that need to be added that aren't related to the format? These would be related to species distribution or numbers, basically things that aren't biologically possible.
Carlos will know better, but I think we can start accepting data after the data validation is in place.

Hi @neil-ices-dk @pcrjoana @NikkiTaylorJNCC @cmspinto
I’m afraid I have some bad news. We’ve had a message from Lucy with some questions about the format and it looks like there may be some points mentioned during the workshop which might have fallen through the net. I’m sorry these weren’t picked up on before, I hope they won’t cause too much of a headache!!
Q: Unable to record multiple precipitations e.g. rain and fog - Joana said this is possible and it will be added, is this still the case?
From my understanding, it isn’t currently possible to record multiple precipitation types. Would it be possible to allow multiple options to be entered?
Q: Will Sleet be added as a precipitation option?
Would it be possible to add ‘ Sleet’ as an additional option for the precipitation vocabulary, please?
Q: Radial distance - does this now accept decimal places?
@pcrjoana  – is there any update on progress of getting the new ORCA shipcodes approved? Have you had any others come forward to get their shipcodes added?

Q2: Yes, it can be. Can you compile a list of all codes needed to be added to the precipitation vocabulary (see Q1)?

Hi @pcrjoana. Here is a list for the precipitation codes as requested. I'll also update the data standard accordingly.

Code
Description

NR
Not recorded

N
None

F
Fog

H
Hail

R
Rain

S
Snow

St
Sleet

RF
Rain and Fog

HF
Hail and Fog

SF
Snow and Fog

StF
Sleet and Fog

Hi Nikki,
both checks are possible.
a) It is possible to check that the coordinates are not on land
b) It is also possible to have a warning if a value seems unlikely. Like if species = "wales" and NoIndividuals > 100
@pcrjoana  has been working on the checks and you can see them here: http://datsu.ices.dk/web/rptChk.aspx?Dataset=149

Hi Nikki,
both checks are possible.
a) It is possible to check that the coordinates are not on land
b) It is also possible to have a warning if a value seems unlikely. Like if species = "wales" and NoIndividuals > 100
@pcrjoana has been working on the checks and you can see them here: http://datsu.ices.dk/web/rptChk.aspx?Dataset=149

Thank you for this and for the link to the checks.
Lets include the coordinates no on land check.
Nikki and myself will think about other appropriate biological validation rules when Nikki is back. It's very useful to have a warning for these.

MaxGroupSize and MinGroupSize; optional but conditional; if they are not filled, a warning is to be made saying this is missing.

Q2: Yes, it can be. Can you compile a list of all codes needed to be added to the precipitation vocabulary (see Q1)?

Hi @pcrjoana. Here is a list for the precipitation codes as requested. I'll also update the data standard accordingly.
Code 	Description
NR 	Not recorded
N 	None
F 	Fog
H 	Hail
R 	Rain
S 	Snow
St 	Sleet
RF 	Rain and Fog
HF 	Hail and Fog
SF 	Snow and Fog
StF 	Sleet and Fog

to add to new version of data format template (v 2.01)

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

Great! Yes to all of the above. Thanks.

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

The data standard has been updated. Can I confirm that the updated version of the template will be v2.02?

Hi Nikki, yes the version will be 2.02 as 2.01 was formally published.

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

@neil-ices-dk @pcrjoana @NikkiTaylorJNCC @cmspinto What is the timeframe to make these changes? We're hoping to notify the data providers that the database is ready in the next couple of days if possible.
This is not as urgent as the changes to the vessel speed and platform height fields to be made optional. But we add 'Lagenorhynchus' AphiaID 137020 to the species vocab please?

The code is added to the vocabulary, and the changes to the format are made. Is there a common name for Lagenorhynchus so I can add it to the template?

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

@neil-ices-dk @pcrjoana @NikkiTaylorJNCC @cmspinto What is the timeframe to make these changes? We're hoping to notify the data providers that the database is ready in the next couple of days if possible.
This is not as urgent as the changes to the vessel speed and platform height fields to be made optional. But we add 'Lagenorhynchus' AphiaID 137020 to the species vocab please?

The code is added to the vocabulary, and the changes to the format are made. Is there a common name for Lagenorhynchus so I can add it to the template?

There isn't a common name for this genus. But if you need one, perhaps something like white-beaked/white-sided dolphin. @NikkiTaylorJNCC do you have any thoughts?

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

@neil-ices-dk @pcrjoana @NikkiTaylorJNCC @cmspinto What is the timeframe to make these changes? We're hoping to notify the data providers that the database is ready in the next couple of days if possible.
This is not as urgent as the changes to the vessel speed and platform height fields to be made optional. But we add 'Lagenorhynchus' AphiaID 137020 to the species vocab please?

The code is added to the vocabulary, and the changes to the format are made. Is there a common name for Lagenorhynchus so I can add it to the template?

There isn't a common name for this genus. But if you need one, perhaps something like white-beaked/white-sided dolphin. @NikkiTaylorJNCC do you have any thoughts?

If there is none, we can leave it blank. :-)

sounds good, so we need an update to:

data standard (Nikki)
data template (Joana/Neil)
database (Carlos)
DATSU (Joana)

@neil-ices-dk @pcrjoana @NikkiTaylorJNCC @cmspinto What is the timeframe to make these changes? We're hoping to notify the data providers that the database is ready in the next couple of days if possible.
This is not as urgent as the changes to the vessel speed and platform height fields to be made optional. But we add 'Lagenorhynchus' AphiaID 137020 to the species vocab please?

The code is added to the vocabulary, and the changes to the format are made. Is there a common name for Lagenorhynchus so I can add it to the template?

There isn't a common name for this genus. But if you need one, perhaps something like white-beaked/white-sided dolphin. @NikkiTaylorJNCC do you have any thoughts?

If there is none, we can leave it blank. :-)

Happy to leave this blank

Joana has sent the completed template v2.02 which will be uploaded straight after the meeting

@NikkiTaylorJNCC v2.02 live on web


test: adjust SILGen/magic_identifier_file_conflicting.swift.gyb for…

… python 3
This test has inline python which requires byte-to-text conversions.
Avoid that by using the io module.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @tachoknight @drexin @tbkka

@swift-ci please test


Clarify when affine needs to be called.

Only convert points to affine form when necessary (after calls to _add or _sub), and not every time a pairing is computed.
resolves #8

Codecov Report

Merging #24 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
+ Coverage   76.55%   76.58%   +0.02%
==========================================
  Files          21       21
  Lines         994      995       +1
  Branches       59       59
==========================================
+ Hits          761      762       +1
  Misses        213      213
  Partials       20       20

Impacted Files
Coverage Δ

src/internal/schnorr.c
89.92% <ø> (ø)
:arrow_up:

src/amcl-extensions/pairing_BN254.c
100% <ø> (ø)
:arrow_up:

src/credential_BN254.c
45.78% <100%> (+1.33%)
:arrow_up:

src/signature_BN254.c
45.33% <100%> (+0.73%)
:arrow_up:

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 c5f1b9f...56b3bc6. Read the comment docs.


NullPointerException getIdDelegate() & getBuilderClass()

Library version: 5.0
Device OS version: 4.4.2
Device Manufacturer: softwinner
Device Name: unknown

We are getting some NPEs through crashlytics for a specific group of test devices (all the same devices). Both the below NPEs seem to relate to 2 cache methods (getBuilderClassCache() & getIdProxyCache()).
As a side note, the same devices are weirdly reporting an error relating to the database name being null (error detailed below). Is there a chance that the instance has been destroyed and this is the cause of all of the errors?
Inquiry.newInstance(this, INQUIRY_DB_NAME)
		.instanceName(INQUIRY_INSTANCE)
		.databaseVersion(INQUIRY_DB_VERSION)
		.build();

Fatal Exception: java.lang.NullPointerException
       at com.afollestad.inquiry.Inquiry.getIdDelegate(Inquiry.java:64)
       at com.afollestad.inquiry.Query.run(Query.java:444)
       at com.afollestad.inquiry.Query$2.run(Query.java:607)
       at java.lang.Thread.run(Thread.java:841)

Fatal Exception: java.lang.NullPointerException
       at com.afollestad.inquiry.Inquiry.getBuilderClass(Inquiry.java:88)
       at com.afollestad.inquiry.Query.run(Query.java:439)
       at com.afollestad.inquiry.Query$2.run(Query.java:607)
       at java.lang.Thread.run(Thread.java:841)

Fatal Exception: java.lang.IllegalStateException: You must initialize your Inquiry instance with a non-null database name.
       at com.afollestad.inquiry.Inquiry._getDatabase(Inquiry.java:50)
       at com.afollestad.inquiry.Query.run(Query.java:468)
       at com.afollestad.inquiry.Query$2.run(Query.java:607)
       at java.lang.Thread.run(Thread.java:841)

Hmm, yeah that looks like it's due to the instance being destroyed, so the caches don't exist

I had assumed that was the case but thought I'd flag it up anyway.

Should these exceptions be catchable by a try catch? Haven't been able to track down the cause of this issue.

Any thoughts? We were using 3.2.1 with no issues but would rather not go back due to all the nice new features.

They are catchable, you catch NullPointerException anywhere you execute a Query (.run()).

Is a bit strange as they don't appear to getting caught, there was one call which wasn't surrounded in a try catch but has since been added. Crashlytics is still reporting NPEs, unfortunately I've found it impossible to reproduce on any of my devices.

I think the GC is destroying the instance as the device in question doesn't have a lot of RAM.

FYI we've started seeing this on more devices during a staged rollout
Fatal Exception: java.lang.IllegalStateException: You must initialize your Inquiry instance with a non-null database name.

Any thoughts on this one?


Todo List

Describe the project
A Todo List is a digital tool designed to help users manage their tasks and stay organized. With this app, users can easily add tasks to their list, edit and update them, and delete tasks as needed.
Overall, a Todo List app is a valuable tool for anyone looking to stay organized and manage their tasks more effectively. Whether you are a student, a professional, or just someone who wants to stay on top of their daily to-do list, this app can help you achieve your goals and stay productive.
Note - This component can also be used in any React project.
Issue Type:

[x] New Project

Screenshots

Hello https://github.com/Rishav1707
I want to work on this issue can you assign it to me. Thanks

Can I start working on this issue.

Yeah no worries, you upload it we will also made some changes and become the contributors in it Simple.

Yeah no worries, you upload it we will also made some changes and become the contributors in it Simple.

Yaah sure

Can i take these project??

In recent 2 to 3 days I will push my changes
On Fri, May 26, 2023, 9:06 AM Atharv Powalkar @.***>
wrote:

Can i take these project??
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/issues/739#issuecomment-1563768132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV435I54ARGVPO4PZULYZIDXIAQLJANCNFSM6AAAAAAYKGS2KQ
.
You are receiving this because you commented.Message ID:
@.***>

Create a fresh issue after 1st June

ok sir