 - "Failed to start API Mocking"

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.16.0
Amplify CLI Version
10.6.2
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
added resources to graphQL schema and ran "amplify mock api"
Describe the bug
attempting to run "amplify mock api", I receive an unknown error.
Expected behavior
launch mock api as I have been using it locally
Reproduction steps

make change to graphql schema, eg.) add model or field to existing model
run "amplify mock api"

Project Identifier
686f8d7fabdbbdcdf584a874e1f2007d
Log output

# Put your logs below this line
amplify mock api
✅ GraphQL schema compiled successfully.

Edit your schema at .\amplify\backend\api\appName\schema.graphql or place .graphql files in a directory at **directory path**

Failed to start API Mocking. Running cleanup tasks.
🛑 Failed to start API Mocking.. Reason: The request processing has failed because of an unknown error, exception or failure.

Project Identifier: 686f8d7fabdbbdcdf584a874e1f2007d

Additional information
Have no issue running "amplify push" and changing cloud DB
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @zachegnermh :wave: thanks for raising this! While we begin to investigate this issue in more depth, do you experience this after deleting the mock database at amplify/mock-data?

@josefaidt Thanks for getting back to me, I have not deleted anything from that folder as far as I am aware.

Hey @zachegnermh can you try removing that folder and restarting mock?

Hi @josefaidt, that worked, it is running properly now. Thank you!


feat: Add optional path var for instance level bucket path

  # module.wandb_infra.module.wandb.helm_release.wandb will be updated in-place
  ~ resource "helm_release" "wandb" {
        id                         = "wandb-cr"
      ~ metadata                   = [
          - {
              ...
              - values         = jsonencode(
                    {
                      - name = "wandb"
                      - spec = <<-EOT
                            "values":
                              "app": {}
                              "global":
                                "bucket":
                                  "kmsKey": "arn:aws:kms:us-west-2:770934259321:key/c88a4da3-aabd-4265-a57d-e4f0115d04b8"
                                  "name": "levin-aws-subpath-testing-file-storage-unbiased-chimp"
                                  "path": ""
                                  "provider": "s3"
                                  "region": "us-west-2"
                                "cloudProvider": "aws"
                         ...
                        EOT
                    }
                )
              - version        = "0.1.0"
            },
        ] -> (known after apply)
        name                       = "wandb-cr"
        # (26 unchanged attributes hidden)

      - set {
          - name  = "spec" -> null
          - type  = "string" -> null
          - value = <<-EOT
                "values":
                  "app": {}
                  "global":
                    "bucket":
                      "kmsKey": "arn:aws:kms:us-west-2:770934259321:key/c88a4da3-aabd-4265-a57d-e4f0115d04b8"
                      "name": "levin-aws-subpath-testing-file-storage-unbiased-chimp"
                      "path": ""
                      "provider": "s3"
                      "region": "us-west-2"
                    "cloudProvider": "aws"

            EOT -> null
        }
      + set {
          + name  = "spec"
          + type  = "string"
          + value = <<-EOT
                "values":
                  "app": {}
                  "global":
                    "bucket":
                      "kmsKey": "arn:aws:kms:us-west-2:770934259321:key/c88a4da3-aabd-4265-a57d-e4f0115d04b8"
                      "name": "levin-aws-subpath-testing-file-storage-unbiased-chimp"
                      "path": "nested/path"
                      "provider": "s3"
                      "region": "us-west-2"
                    "cloudProvider": "aws"
 ...
            EOT
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

@levinandrew what was the driver of this change for context?
CC @wandb/delivery-tooling-team

The reason path is in the helm spec currently is because azure requires it for the storage account/ blob store.

Hey @zacharyblasczyk thanks for the review 🤜 🤛
This did come from a customer ask to be able to store all data at a path of the instance level bucket instead of its root. We are making similar changes for Azure and Google, and will handle the Azure case you commented on.

This PR is included in version 4.23.0 :tada:


[rmodels] Feature request: failure condition for LoadModel()

I want to support mesh generation with the macro SUPPORT_MESH_GENERATION set, But still be able to check if model has loaded successfully, like with IsModelReady(), which doesn't work since the failed mesh is set to a cube when SUPPORT_MESH_GENERATION is set.
I've considered doing a workaround by skipping the default cube generation. But then I'd have to include the modified library source in my project, which I'd rather not do.

@Boyfinn Not sure I understand.
1. `SUPPORT_MESH_GENERATION` is already enabled by default on the `config.h` file ([L206](https://github.com/raysan5/raylib/blob/master/src/config.h#L206)).

2. `IsModelReady()` _"is a very general model validation, many elements could be validated from a model..."_ ([L1119](https://github.com/raysan5/raylib/blob/master/src/rmodels.c#L1119)), so it may, or may not, suit your use case.

3. If you need some specific check, you probably could implement that inside your application logic, similar to `IsModelReady()` ([L1113-L1117](https://github.com/raysan5/raylib/blob/master/src/rmodels.c#L1113-L1117)).

4. Either way, I tested it right now with the `models/models_mesh_generation.c` [example](https://github.com/raysan5/raylib/blob/master/examples/models/models_mesh_generation.c), adding the following to [L48](https://github.com/raysan5/raylib/blob/master/examples/models/models_mesh_generation.c#L48):

[...]
models[8] = LoadModelFromMesh(GenMeshCustom());
if (IsModelReady(models[8])) printf("model is ready\n");
else printf("model is NOT ready\n");
[...]

And it worked fine. Output:
[...]
INFO: VAO: [ID 10] Mesh uploaded successfully to VRAM (GPU)
model is ready
INFO: TIMER: Target time per frame: 16.667 milliseconds
[...]

I should maybe have specified that i use LoadModel(), as it generates a cube when it fails at loading a mesh when SUPPORT_MESH_GENERATION is set.

@ubkp It was a fallback to somewhat show the model was not loaded correctly, it helped students and program did not crash on bad models. Drawing nothing was very confusing for them. Not sure what an alternative could be...

Would it be possible to get some-kind of solution to this? I'm currently overriding the default cube generation, but this isn't ideal, since I have to include the library & changes in my project repo for it, which significantly complicates the build process when initially cloning the project onto a new device.

@Boyfinn You could implement your own "customIsModelReady" inside your application, with model.meshCount > 1:
bool customIsModelReady(Model model)
{
    return ((model.meshes != NULL) &&           // Validate model contains some mesh
            (model.materials != NULL) &&        // Validate model contains some material (at least default one)
            (model.meshMaterial != NULL) &&     // Validate mesh-material linkage
            (model.meshCount > 1) &&            // Validate mesh count
            (model.materialCount > 0));         // Validate material count
}

Or without it:
bool customIsModelReady(Model model)
{
    return ((model.meshes != NULL) &&           // Validate model contains some mesh
            (model.materials != NULL) &&        // Validate model contains some material (at least default one)
            (model.meshMaterial != NULL) &&     // Validate mesh-material linkage
            (model.materialCount > 0));         // Validate material count
}

Note: the Model type is already provided by raylib.h (L392-L405).

the failed mesh is set to a cube when SUPPORT_MESH_GENERATION is set.

I think you need to create your own model validation, similar to what @ubkp suggests. Your use case is very specific to your implementation so changing Raylib to suit it seems inappropriate. In your case, when IsModelReady returns true, do a second check to see if

The model only contains exactly one mesh and
That mesh is exactly the mesh which GenMeshCube creates

This is the simplest solution, since the only risk it introduces is if a model which is identical to the generated cube is used, it will be incorrectly determined to have failed to load. I assume this isn't a problem, as it seems unlikely.

@AndrewHamel111 @ubkp I'm still thinking about the best approach to this issue...
One option is adding a flag to support the falback mechanism but it will increase a bit the build complexity... but I understand that advance users probably want avoid that fallback and manage any issue themselfs with IsModelReady()...
IsModelReady() was added recently and I did not consider this situation... maybe I should just remove the fallback mechanism? with IsModelReady() available now it can be checked on potential crashing points, that, after all, was the reason for the fallback mechanism.
Removing the fallback will also simplify the code...
What do you think?

@raysan5 If the fallback is not necessary then, IMHO, I think just a TRACELOG(LOG_WARNING... (L1060) on LoadModel() (L1032) would be enough.

Removed cube mesh fallback, code simplified, hopefully it won't crash somewhere else (I did a quick review).
Now it's up to the user to deal with models not properly loaded.


Cannot install @vue/cli-service on Linux aarch64 because "Failed at the<EMAIL_ADDRESS>install script."

Version
3.4.0
Environment info
OS: Linux 4.14.0-xilinx-v2018.2 aarch64 / arm64
User: root
Node: 10.15.1 (installed at /usr/bin/node)
npm: 6.4.1 (installed at /usr/bin/npm)

Steps to reproduce
From the command line, just do npm install @vue/cli-service.
What is expected?
The installation of @vue/cli-service is successful.
What is actually happening?
The installation fails with the following error message:
><EMAIL_ADDRESS>install /home/root/apps/config-manager/out/webapp/frontend/node_modules/yorkie
> node bin/install.js

internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module '/home/root/apps/config-manager/out/webapp/frontend/node_modules/yorkie/bin/install.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node bin/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

When inspecting the NPM debug logs:
22191 verbose stack Error<EMAIL_ADDRESS>install: `node bin/install.js`
22191 verbose stack Exit status 1
22191 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/nodejs/node-v10.15.1-linux-arm64/lib/node_modules/np
m/node_modules/npm-lifecycle/index.js:301:16)
22191 verbose stack     at EventEmitter.emit (events.js:189:13)
22191 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/nodejs/node-v10.15.1-linux-arm64/lib/node_modules/np
m/node_modules/npm-lifecycle/lib/spawn.js:55:14)
22191 verbose stack     at ChildProcess.emit (events.js:189:13)
22191 verbose stack     at maybeClose (internal/child_process.js:970:16)
22191 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
22192 verbose pkgid<EMAIL_ADDRESS>22193 verbose cwd /home/root/apps/config-manager/out/webapp/frontend
22194 verbose Linux 4.14.0-xilinx-v2018.2
22195 verbose argv "/usr/local/lib/nodejs/node-v10.15.1-linux-arm64/bin/node" "/usr/bin/npm" "install" "@vue/cli-service
"
22196 verbose node v10.15.1
22197 verbose npm  v6.4.1
22198 error code ELIFECYCLE
22199 error errno 1
22200 error<EMAIL_ADDRESS>install: `node bin/install.js`
22200 error Exit status 1
22201 error Failed at the<EMAIL_ADDRESS>install script.

The same error is encountered when doing:

npm install @vue/cli
npm install yorkie

I know that there is a similar issue posted at https://github.com/vuejs/vue-cli/issues/3056 ("Yorkie installation fails which causes Vue CLI to fail") but that was closed without any comments or solution, as indicated at https://new-issue.vuejs.org/?repo=vuejs/vue-cli ("open a new issue using the form below instead of commenting on the old issue").

Have you tried installing vue-cli globally as described here:
npm install -g @vue/cli
# OR
yarn global add @vue/cli

@caugner
I got the same error when I installed @vue/cli and @vue/cli-service globally.

I did some more testing:
I got it to install successfully when I downgraded my env's node version to v8.4.0.
(It's the base node package that comes with the OS.)
But Vue CLI will not run on this lower version:
You are using Node v8.4.0, but this version of vue-cli requires Node >=8.9.
Please upgrade your Node version.

This is mentioned in the Vue Installation docs, where it says "Vue CLI requires Node.js version 8.9 or above (8.11.0+ recommended).". But if I upgrade node, I'll get the same installation errors as I previously reported.
So.. I'm not familiar with what's inside Vue CLI or with yorkie, but it seems I'm stuck at being unable to use it on this Linux version.

What about npm install @vue/cli-service --unsafe-perm?

For security reasons, when you run npm install as root, npm will set the user to "nobody" when running postinstall scripts, which does not have access to the project directory, thus the error message.

Thanks for the tip @sodatea.
It looks like I got it to install successfully now.

I started off with the base node version v8.4.0.
I then updated to the ARMv8 version of node v10.15.1

from https://nodejs.org/en/download/, get node-v10.15.1-linux-arm64.tar.xz

npm install @vue/cli --unsafe-perm  (also works with -g)
npm install @vue/cli-service --unsafe-perm  (also works with -g)

Solved issue by using latest node image for container FROM node:latest

This error<EMAIL_ADDRESS>is related to the security attributes of the project-vuejs folder. So, create your projects outside the root / folder, make Linux updates (Ubuntu ...) and success to everyone!

So, create your projects outside the root / folder, make Linux updates (Ubuntu ...)

Can you clarify what you mean by "outside the root / folder"?
This is Linux, everything is under /.

Hi!
I suggest not creating projects inside the /root folder to avoid setting access permissions for your objects, unless this is a requirement for your development environment. For example, create a project folder inside the /home directory as /my-project and inside it create the vuejs project and execute it. If you are using an IDE editor such as Visual Studio Code (or Atom) to open and modify the project folder, you may need to give permissions to it (chmod). I successfully tested the host machine, VM and Docker-CE container (all with Ubuntu 18.04 and Vue-CLI 4.2.3).
Em sexta-feira, 3 de abril de 2020 09:06:18 BRT, Gino Mempin<EMAIL_ADDRESS>escreveu:
So, create your projects outside the root / folder, make Linux updates (Ubuntu ...)
Can you clarify what you mean by "outside the root / folder"?
This is Linux, everything is under /.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


HTTP Error

When uploading photo to Firebase Bucket, URL Error 401 is shown. Seems like it has some authorization issue. What to do, non of this two url does not work?
let url = "https://storage.googleapis.com/upload/storage/v1/b/(Config.googleStorageBucket)/o?name=(filename)"
let url = "https://www.googleapis.com/upload/storage/v1/b/(Config.googleStorageBucket)/o?name=(filename)"

Hmm!  Just throwing out something obvious, does that bucket's permissions allow for public uploads?


Where is the wallet? I can not open zen wallet.

The wallet can not open.

Hello,
We will be deprecating "zencash-mobile" soon. It won't be updated.
Please use any other wallet from the list: https://www.horizen.io/wallets/


Expose org_id, org_name, space_id, space_name and app_name for ContainerMetrics

See request at #1.

Implemented this at the cf_exporter. See the FAQ on how to merge labels from differents releases.


Tuples length

Looks like Tuples match for arrays with a length >= to the component length?  Shouldn't tuples need to match the length exactly?  See https://github.com/pelotom/runtypes/blob/master/src/types/tuple.ts#L235 .
Also, any reason not to have a Tuples of length 0 and 1?  Since arrays don't have a constraint on length it seems like a Tuples is better for these cases.

Looks like Tuples match for arrays with a length >= to the component length? Shouldn't tuples need to match the length exactly? See /src/types/tuple.ts@master#L235  .

Yes, you're right. Care to open a PR to fix it?

Also, any reason not to have a Tuples of length 0 and 1? Since arrays don't have a constraint on length it seems like a Tuples is better for these cases.

There are tuples of length 1 (although I've never had occasion to use them):
https://github.com/pelotom/runtypes/blob/3385f5e3a3e4d206029c565533d13b3f8c8619b1/src/types/tuple.ts#L6
Likewise tuples of length 0 don't seem very useful but I'm not opposed to adding them for completeness.

Seems like it's already resolved by #124. Closing.


Cleanse newly introduced but unused functions.

The ossl_param_bld_to_param_ex() function is a recent introduction that hasn't been in a release and is only called by the unit tests.
The OSSL_PARAM_construct_from_text() function is also a recent introduction that hasn't been in a release and isn't called from anywhere.
Given the lack of use, keeping these is akin to retaining dead code and needless complexity.

[x] documentation is added or updated
[x] tests are added or updated

Merged to master.  Thanks.


Move design pages to develop

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/toc.yml
:warning:Warning

Details

docs/automatically-open-a-task-pane-with-a-document.md
:white_check_mark:Succeeded

docs/develop/usability-testing.md
:white_check_mark:Succeeded

docs/toc.yml

[Warning] Invalid file link:(~/develop/automatically-open-a-task-pane-with-a-document.md).

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.

Added redirect for auto topic:
{
"source_path": "docs/design/automatically-open-a-task-pane-with-a-document.md",
"redirect_url": "docs/develop/automatically-open-a-task-pane-with-a-document.md",
"redirect_document_id": true
},


OSRM-bench mark first go

This focuses on setting a basic local OSRM server using the default bicycle profile. Anyone is free to go further to potentially explore the modification of profiles.

Sounds good!

The changes for setting up and benchmarking the local OSRM server have been committed directly to the main branch. You can view the commit here: b8d8929.

👍


Fix project URL

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixed project URL and bumped build number, then rerendered.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


fs_event_close_with_pending_delete_event fails on z/OS

Version: v1.x
Platform: z/OS

fs_event_close_with_pending_delete_event was newly introduced by https://github.com/libuv/libuv/pull/3542 for all platforms that support FS events but the only CI done on that was for SmartOS and the GH actions. The new test has been consistently failing for the z/OS CI since it was merged.
e.g. https://ci.nodejs.org/view/libuv/job/libuv-test-commit-zos-cmake/1237/
https://ci.nodejs.org/view/libuv/job/libuv-test-commit-zos-cmake/1237/BUILDTYPE=Release,nodes=zos-s390x/console
not ok 49 - fs_event_close_with_pending_delete_event
# exit code 3
# Output from process `fs_event_close_with_pending_delete_event`:
# Assertion failed in /u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/test/test-fs-event.c on line 74: 0 && "should never be called"
#  1: 0x1AE31006 abort
#  2: 0x1AF45116 fs_event_fail+0x62 [S0W1:/u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/test/test-fs-event.c:74]
#  3: 0x1AF44D32 os390_message_queue_handler+0x20a [S0W1:/u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/src/unix/os390.c:676]
#  4: 0x1AF3321C uv__io_poll+0x306 [S0W1:/u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/src/unix/os390.c:832]
#  5: 0x1AE33D70 uv_run+0x1a8 [S0W1:/u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/src/unix/core.c:405]
#  6: 0x1AE15FE6 run_test_fs_event_close_with_pending_delete_event+0x364 [S0W1:/u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/test/test-fs-event.c:937]
#  7: 0x1AE11BF2 run_test_part+0x122 [S0W1:/u
# /iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/test/runner.c:376]
#  8: 0x1B0D9ADE main+0x10e [S0W1:/u/iojs/build/workspace/libuv-test-commit-zos-cmake/BUILDTYPE/Release/nodes/zos-s390x/test/run-tests.c:81]
#  9: 0x1B0D9EFA CELQINIT+0x1aca [CELQINIT:]
# CEE5207E The signal SIGABRT was received.

cc @libuv/zos

I'll take a look into this when I get a chance


New menu item

I was wondering where should I add in js once I added new item in main menu? I have added new menu but I want to navigate to that div after click, as it works on other menus on theme.
Could someone give me a hint?

I have solved the problem. This issue could be closed

Hello,
perfect.
I suppose you could close the issue by yourself.
Isn't there a "Close issue" button for you?


info object returns empty string

Hi,
After reviewing the malmoenv code it appears that the info object obtained from taking a step returns coordinate positions which is useful for doing RL without video input.
I've noticed that every few steps it returns an empty string instead of the normal json object.
I'm not sure if this is a desync issue between the client and server or if there is some other cause to not yield the coords at every step.
Is the intent that the info object is present at every step? I'd prefer some kind of wait setting to get the data over an empty string since my Q tables get messed up without this data.

Small example
# ------------------------------------------------------------------------------------------------
# Copyright (c) 2018 Microsoft Corporation
#
# Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
# associated documentation files (the "Software"), to deal in the Software without restriction,
# including without limitation the rights to use, copy, modify, merge, publish, distribute,
# sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in all copies or
# substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
# NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
# DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
# ------------------------------------------------------------------------------------------------

import malmoenv
import argparse
from pathlib import Path
import time
from PIL import Image
import numpy as np
import json

xml = '''

<Mission xmlns="http://ProjectMalmo.microsoft.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <About>
         <Summary>Empty Info Object</Summary>
      </About>
      <ModSettings>
         <MsPerTick>5</MsPerTick>
      </ModSettings>
      <ServerSection>
         <ServerInitialConditions>
            <Time>
               <StartTime>0</StartTime>
               <AllowPassageOfTime>false</AllowPassageOfTime>
            </Time>
            <Weather>clear</Weather>
            <AllowSpawning>false</AllowSpawning>
         </ServerInitialConditions>
         <ServerHandlers>
            <FlatWorldGenerator generatorString="3;minecraft:bedrock,2*minecraft:dirt,minecraft:grass;1;village" forceReset="true" />
            <DrawingDecorator>
               <!-- Tricks to clean the map before drawing (avoid entity duplication on the map) -->
               <!-- coordinates for cuboid are inclusive -->
               <DrawCuboid type="air" x1="-24" x2="24" y1="4" y2="40" z1="-20" z2="20" />

            </DrawingDecorator>
            <ServerQuitFromTimeUp description="out_of_time" timeLimitMs="1000000" />
            <ServerQuitWhenAnyAgentFinishes />
         </ServerHandlers>
      </ServerSection>
      <AgentSection mode="Survival">
         <Name>Agent0</Name>
         <AgentStart>
            <Placement pitch="20" x="0.5" y="4" yaw="180" z="0.5" />
            <Inventory>
               <InventoryBlock quantity="1" slot="39" type="diamond_helmet" />
            </Inventory>
         </AgentStart>
         <AgentHandlers>
            <DiscreteMovementCommands>
            </DiscreteMovementCommands>
            <ObservationFromGrid>
               <Grid absoluteCoords="true" name="board">
                  <min x="0" y="3" z="0" />
                  <max x="4" y="3" z="-12" />
               </Grid>
            </ObservationFromGrid>
            <ObservationFromFullStats />
            <RewardForSendingCommand reward="-1" />
            <RewardForTouchingBlockType>
               <Block behaviour="onceOnly" reward="5" type="brick_block" />
            </RewardForTouchingBlockType>
            <RewardForMissionEnd rewardForDeath="-200">
               <Reward description="found_goal" reward="200" />
               <Reward description="out_of_time" reward="-100" />
            </RewardForMissionEnd>
            <AgentQuitFromReachingCommandQuota description="command_quota_reached" total="100" />
            <AgentQuitFromTouchingBlockType>
               <Block description="found_goal" type="brick_block" />
            </AgentQuitFromTouchingBlockType>
            <VideoProducer want_depth="false">
               <Width>800</Width>
               <Height>600</Height>
            </VideoProducer>
         </AgentHandlers>
      </AgentSection>
</Mission>
'''
env = malmoenv.make()

env.init(xml, 9000, server='<IP_ADDRESS>',
    server2='<IP_ADDRESS>', port2=9000, role=0, exp_uid=None,
    episode=0, resync=0,
    action_filter=['movenorth', 'moveeast', 'movesouth', 'movewest'])
env.reset()
steps = 0
while True:
    time.sleep(.05)
    _, reward, done, info = env.step(env.action_space.sample())
    steps += 1
    if len(info) == 0:
        env.close()
        print('info is empty after {}'.format(steps))

My solution was to remodel the environment ignoring all output from the env.step function. Effectively treating my maze as an ascii grid and the env.step function simply renders that representation.


Add class effective durability toggle to armors

Add toggle to Armors page to switch between regular effective durability and class effective durability.

.deploy to development

.deploy


Update Dokka to 1.4.30

A small update to Dokka 1.4.30, which improves output for multi-module documentation that this project uses. This also allows removing a workaround for the docs workflow, since index.html is now created directly.

Thanks @byencho !


Soft clipping and read splitting

HI - I have read through your docs/paper and previous issues but have not found a detailed description of how soft clipping and read splitting work. Could you please point me to the right place or answer here?
From my understanding you split long reads into 256mers and map these then join them together in a way the results in either; (1) the whole long read mapping continuously, (2) ~1half of the long read mapping contiguously in one genomic region and the other half mapping elsewhere or (3) a section of the long read maps and the rest is soft clipped. Is that right or can NGMLR create multiple secondary alignments? I work with cancer genomes and am concerned that I am loosing a lot of read depth to soft clipping due to high levels of genomic rearrangement.
Thanks in advance.
Liam

NGMLR can work with multiple splits within one read. We designed it during our work for SKBR3 breast cancer genome.
The split reads are reported as part of the read per entry indicated as soft clipping the part that was mapped elsewhere. Just to make sure that this is not what you are seeing. Other soft clipping can indicate novel insertions, but I assume that this should not happen too often here.
I hope that helps
Fritz


[NVIDIA TF] Fix an issue of empty output tensor when using bf16

While testing the conv+bf16, we noticed many tests would fail on the A100 GPUs with errors like AssertionError: 1.0 not less than 0.003. After some digging, it turns out that we should have passed the original address of the output tensor to the helper function where the address might be updated to point to a new allocated tensor. Instead, we mistakenly passed the address of a local cast tensor and this will leave the original output address unchanged no matter what.
This PR fixed this issue.
cc. @nluehr @pjannaty

Wow, good catch!


are svg icons the right thing?

I like them better than fontawesome, but the ones I have are TOO BIG and I have to do a lot of weird scaling that I don't understand.

I've replaced them, but still not sure it's the right thing. Closing for now.


Rename GIDUserAuth to GIDSignInResult

For improved API surface readability.  This new name should make the role of the class clearer.

Why do you want to change the name of UserAuth? I think we use this name because it is the result of sign-in and adding scopes.

Why do you want to change the name of UserAuth? I think we use this name because it is the result of sign-in and adding scopes.

As I mentioned in the PR description, I don't feel like the name GIDUserAuth does a good job conveying the roll of the class.


NTT-199 - Add mongo, repo controller and a basic integration test.

Compiles
Runs unit tests
Runs integration tests
starts

Added port: 9847

Once build is green, hapy to merge


Changed aria-live attribute value from polite to assertive

For ngMessages directive ngAria generates aria-live with value assertive and not polite.

Hi, thanks for the PR! Can you please sign the CLA?

Hi, i have signed the CLA.

"Assertive" was added for a reason: so that feedback would be given immediately as users type in text inputs. We talked about making this a configuration option, was that not considered?

I'm not sure if I follow; is this now incorrect? It was only a change in the docs to match the behavior in code, so I assumed it was safe.

Ah ha, I totally read that wrong! Disregard. :)


Reduce size of generated HTML

A recent blog post is 1.88 MB - that's too big!
It's time to look into deduplicating some of the metadata that ends up in the generated code.

Fixed by #115


Configuration to use Community Extensions

Hello,
I think it would be nice to have an option to enable the use of Community Extension in the docker-entrypoint.sh file.
Currently i'm using a custom entrypoint in my Dockerfile, it works but it just could be nicer i think !
Either way, thanks for your work !

Could you please provide an example of how you see it's implemented?

Something like this i think :
...
# Use community extensions or not
if [ "$USE_COMMUNITY_EXTENSION_PARAMETER" == "true" ]
then
    COMMUNITY_EXTENSION_PARAMETER="-a tc_core.app.App"
fi

...

THUMBOR_EXEC="thumbor ${PORT_PARAMETER} --conf=/usr/local/etc/thumbor.conf ${LOG_PARAMETER} ${NUM_PROCESSES_PARAMETER} ${COMMUNITY_EXTENSION_PARAMETER}"

Could you also provide the community extended which you want to use?
I need it to have the same environment as you are

Oh it's a custom plugin from our own that is not published anywhere, i think you can just create a dummy handler that will just call the ImagingHandler#get function, that will do it

Maybe you can provide some other extension that I can find opensource and try it on?

You can test it with tc_shortener, i think it's the one that best suit my case : https://github.com/thumbor-community/shortener

i want to use this setup to load images direct from aws but what value i should place in a LOADER variable tol use s3 as a loader


Premature end of Content-Length delimited message body

Hi,
We have been running Spark streaming jobs along with Delta Lake for past couple of months. But for last 2 days we have been getting the below error while writing to S3. Can you please let me know what we may be doing wrong here?
"org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 43,688; received: 28,617)"
Details of the streaming job:
Apache Spark: 3.0.1
Delta Lake: 0.7.0
Python: 3.7.9
Object Store: AWS S3
Can you let me know the probable cause of the error?
Pyspark Command used:
PYSPARK_DRIVER_PYTHON=ipython $SPARK_HOME/bin/pyspark --packages org.apache.spark:spark-sql-kafka-0-10_2.12:3.0.1,org.apache.spark:spark-avro_2.12:3.0.1,za.co.absa:abris_2.12:3.2.1,io.delta:delta-core_2.12:0.7.0,org.apache.hadoop:hadoop-aws:2.7.4,org.apache.hadoop:hadoop-common:2.7.4 --repositories https://packages.confluent.io/maven/ --conf spark.delta.logStore.class=org.apache.spark.sql.delta.storage.S3SingleDriverLogStore
Sample Code snippet used to replicate the error:
`
import boto3
from pyspark import SparkConf, SparkContext
from pyspark.sql import SparkSession, Window
import pyspark.sql.functions as F
spark = pyspark.sql.SparkSession.builder.appName("MyApp")
.config("spark.sql.extensions", "io.delta.sql.DeltaSparkSessionExtension")
.config("spark.sql.catalog.spark_catalog", "org.apache.spark.sql.delta.catalog.DeltaCatalog")
.getOrCreate()
spark.sparkContext._jsc.hadoopConfiguration().set("fs.s3a.endpoint", "s3.ap-south-1.amazonaws.com")
spark.sparkContext._jsc.hadoopConfiguration().set("spark.hadoop.fs.s3a.impl", "org.apache.hadoop.fs.s3a.S3AFileSystem")
spark.sparkContext.setSystemProperty("com.amazonaws.services.s3.enableV4", "true")
spark.conf.set("spark.databricks.delta.schema.autoMerge.enabled", "true")
spark.conf.set("spark.delta.merge.repartitionBeforeWrite", "true")
spark.conf.set("delta.compatibility.symlinkFormatManifest.enabled", "true")
from delta.tables import *
deltaTable = DeltaTable.forPath(spark, "s3a://BUCKET_NAME/STREAMING_PATH")
deltaTable.generate("symlink_format_manifest")
`

This may be a regression of S3. Could you try to reach AWS for this issue?

We hit this problem recently too after an apt update - when you type java -version what do you see? If it's openjdk version "1.8.0_272" you may need to rollback to openjdk version "1.8.0_265"
When we run the following on our linux machines the problem is resolved for us:
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jre_8u265-b01-0ubuntu2~18.04_amd64.deb
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jdk_8u265-b01-0ubuntu2~18.04_amd64.deb
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jdk-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jre-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jre-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jdk-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jre_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jdk_8u265-b01-0ubuntu2~18.04_amd64.deb

Thanks guys for the reply.
We tried upgrading from spark 3.0.0 to 3.0.1 and used hadoop version 3.2. This helped us to the fix the problem.
Post the upgrade we tried running the jobs on the same delta locations and haven't faced the problem so far.
Output of  "java -version" shows as
openjdk version "1.8.0_272"
OpenJDK Runtime Environment (build 1.8.0_272-8u272-b10-0ubuntu1~18.04-b10)
OpenJDK 64-Bit Server VM (build 25.272-b10, mixed mode)

If faced with the problem in future we will try to downgrade the same.

We hit this problem recently too after an apt update - when you type java -version what do you see? If it's openjdk version "1.8.0_272" you may need to rollback to openjdk version "1.8.0_265"
When we run the following on our linux machines, then restart spark, the problem is resolved for us:
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jre_8u265-b01-0ubuntu2~18.04_amd64.deb
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jdk_8u265-b01-0ubuntu2~18.04_amd64.deb
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jdk-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
wget https://launchpad.net/~openjdk-security/+archive/ubuntu/ppa/+build/19763089/+files/openjdk-8-jre-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jre-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jdk-headless_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jre_8u265-b01-0ubuntu2~18.04_amd64.deb
sudo dpkg -i openjdk-8-jdk_8u265-b01-0ubuntu2~18.04_amd64.deb

sudo wget --no-cookies --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" "http://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jdk-8u131-linux-x64.tar.gz"

sudo tar xzf jdk-8u131-linux-x64.tar.gz

sudo update-alternatives --install /usr/bin/java java /opt/jdk1.8.0_131/bin/java 2
#sudo update-alternatives --config java
sudo update-alternatives --set java /opt/jdk1.8.0_131/bin/java

sudo update-alternatives --install /usr/bin/jar jar /opt/jdk1.8.0_131/bin/jar 2
sudo update-alternatives --install /usr/bin/javac javac /opt/jdk1.8.0_131/bin/javac 2
sudo update-alternatives --set jar /opt/jdk1.8.0_131/bin/jar
sudo update-alternatives --set javac /opt/jdk1.8.0_131/bin/javac
cd -
java -version```
for ubuntu machines

Thanks a lot. I was using spark-2.4.4 built with java "1.8.0_292" and scala-2.12 along with  hadoop-2.6.5.
I changed the java run time version to openjdk version "1.8.0_265" and I was able to read from S3 bucket in spark.
(did not need to rebuild spark-2.4.4 with java "1.8.0_265")

output of java -version

openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-8u265-b01-0ubuntu2~18.04-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)


new features for yam_launcher

the development of mLauncher is finished, because the developer want to concentrate only in his project Easylauncher.
Can some of the features of mLauncher be used in yam_launcher?

What features are you interested in?
I can't directly use mLauncher code as that would require me to license YAM Launcher under GPL, which I do not wish to do. I can develop features myself when I shappen feel like it, though.

many thanks for your answer, I open some new tread to ask for new features 🙏


Fix for Structure Service: Removed Unnecessary thing_nodes Attribute and Added OpenAPI Documentation Availability Test

This PR fixes problems that were discovered after the merge of PR #201.
Removal of thing_nodes Attribute:
The thing_nodes attribute was removed from the StructureServiceElementType class as it was unnecessary and caused a TypeError: issubclass() arg 1 must be a class. This error occurred because, during schema generation, a string was used instead of the expected class type. In Pydantic or FastAPI, such issues can arise when forward references are not properly resolved.
Addition of OpenAPI Documentation Availability Test:
Introduced an test, test_openapi_docs_available, to verify that the OpenAPI documentation is accessible at /openapi.json. To suppress warnings about duplicate operation_ids (stemming from FastAPI's route registration behavior) pytest.mark.filterwarnings fixture was added. These warnings occur when the OpenAPI schema is requested, triggering validation of duplicate operation_ids. For more details, refer to FastAPI Issue #4740.

This pull request includes several hundred commits! @stnhdl : Please make sure it only contains the relevant commits.

Hello @stnhdl . I integrated your fix directly into develop, so this PR is now obsolete. Thank you!!