Fix bug where config file was not being loaded.

An incorrect file existence check resulted in the config file never actually
being loaded.
In testing this functionality, we also realized that the goal of having
explicit CLI options take precedence over the config file is not currently
possible. We can’t distinguish between explicitly specified CLI options and
their default values because ember-cli pre-applies the default values and
passes us the merged result.
In light of this and in order to provide a consistent experience, this commit
updates the behavior and documentation to make options specified via the
config file take precedence over explicit CLI options and their default
values.

In particular, if an end-user was to specify a CLI option that matches a default value (e.g. --strategy=semver), its impossible to distinguish this from leaving that option off altogether.

I think that we could preserve the original intent, by removing the default values from the availableOptions hash and just keep track of defaults in a separate hash (instead of this).
We could keep the default option values on the object in a simple format to make it easier to do the merging:
defaultOptionValues: {
  local: true,
  remote: 'origin',
  message: 'Released %@',
  // .....
}

Thoughts?

@rwjblue We considered this, but we would lose the benefit of ember-cli tooling showing you the defaults. Seems like something that would be better to "fix" in ember-cli, by somehow providing commands with the information about what options were set explicitly, and which from defaults.

Well, we can configure how ember-cli prints the help for our command (see here), but inlining all that code here would be pretty annoying.
Ideally (for our case at least) would be if the option processing was its own function (which itself used smaller functions like this.getOptionDefault(option) or this.getOptionName ) to allow simpler customization of just the option output.

Just chatted with @lukemelia in Slack, and suggested using a getter for availableOptions so that we can get the behavior that we originally wanted.
We can use the config/release.js files values for each option as the actual default and then still get the proper precedence order (higher to lower: command line, config file, default). We can indicate that the default value came from config/release.js in the options description.
I'd really like to preserve the order of precedence if possible, and if the above suggestion works that would be awesome...

We should close this in favor of https://github.com/lytics/ember-cli-release/pull/12, which subsumes it.


Update create-and-publish-websocket-api.md

@tharindu1st , please send this fix to other branches if it is applicable.


Uncontrollable camera while flying with "Do a barrel roll" mod, one more issue and a small question

I was taking a look at the mod page and saw model editing ss, the camera position doesn't seem to show in the preview tab of model viewing menu.
https://github.com/user-attachments/assets/16d46ff0-d3db-460f-9324-6fb9c188c1f2
The other issue:
Certain bindings tend to override the camera, I've posted a sc of what I mean cuz tbh I don't know how to explain it.
These are the bindings I used, very similar to the "skin_head_2" config

Below is sc of what is happening, for context I'm using the "Fresh Moves" resourcepack. While flying I moved my mouse left and right to try to roll mid-air but camera just went hay-wire, those random movements are from the "Real Camera" mod. I've confirmed that everything works fine with other configs of the mod and while it's deactivated.
https://github.com/user-attachments/assets/7fd4f56d-5c84-4354-a75f-d98a1a9e7210
The small question: What do the forward and upward vectors do? I know the target is where the camera is centred at, but I can't tell what the other two do to the camera

UPDATE: I think figured out why this is happening. Ofcourse I could be wrong, but I believe this mod works by doing some sort of projection from the "Up Vector" to an imaginary vector perpendicular to the "Forward Vector" which then, I think, based on how long the pojection is, determines the degree of shake or "intensity" of the camera. I'll attach videos of what I mean. What I think is happening, is that because the projected vector is very long in my last video, it's effects when rotating the player are VERY noticable, and therefore it spazes out unctontrollably. But I think a fix might be possible, just like the config to stop rendering when holding a certain item, you could add a config to stop rendering when gliding, or rather, flying.
Here's what I mean:
https://github.com/user-attachments/assets/fc13eb15-b0ea-472c-aa82-bd696bf91a4d
First "skin_head" config:
https://github.com/user-attachments/assets/d6ffd099-3c3d-42c8-ae5d-bcf7acdf868b
"skin_head_2" config:
https://github.com/user-attachments/assets/13796ebd-90b4-4efb-a84e-829a65f0fda6
The camera is highly affected by ANY rotation done by the player model, which I like. I know how to replicate both instances.
Normal camera normal: The angle formed by the "Forward vector" and the "Up vector" is <10 degrees
Violent camera movement: The angle formed by the "Forward vector" and the "Up vector" is >10 degrees

These are rough esitmates based on my eye, if the "Up vector" is set below the red lines relative to the "Forward vector" then the camera is normal (as approach the red lines you'll notice more considerable sway caused by any model animating mod -I'm using Epic Fight mod in this case-)
If the "Up vector" is set above the red lines the camera becomes more violent as it aproches 90 degrees relative to the "Forward Vector"
Sorry for long ass comment, I'm still not quite sure where to post this, but I saw other submissions by other people here so I did the same.


Error 1003 when deploying for LinuxRT 64 bit (duplicated names on vi.lib)

Describe the bug
I can compile engine build distribution but I've error 1003 when deploying
To Reproduce
Steps to reproduce the behavior:

Compile Engine Release build distribution under RT CompactRIO Target - Linux x64 target
Deploy a VS sysdef on a linux rt target

Details
Looking to the target CD folder, there's the llb and 2 folders for the VIs with duplicated names. These are:

each of them having these 2 files:

Please complete the following information:

OS: Linux RT 64 bit
Release Version: latest commit (#124)

Additional context
Fix is pretty easy (e.g. adding NI_Data Type lvlib to the project items and renaming conflicting items during build) but it's sort of manual and impact user productivity

Hey Fabio,
          Please make sure to have the following token added to your LabVIEW.ini file: "NI_AppBuilder_SDist_ExcludeEditTime=True".

          The final build should like this (without any extra files):

This should eliminate the issue that you are facing.
Sincerely yours,
Denis

Assumed fixed


proposal: add method ValidateProvisiongParameters in the ServiceManager interface

Hi, in the ServiceManager interface, only ValidateUpdatingParameters is specified. Symmetrically, we should also have a method ValidateProvisioningParameters, and there does exist the scenario where parameter schema and CustomPropertyValidator are not enough. How do you think about it?

We used to have such a method, but we eliminated it (and ValidateUpdatingParameters) when we switched to doing schema driven validation. We added ValidateUpdatingParameters back in when we discovered that during an update, there were some cases where we couldn't validate only on the basis of parameter values, but had to weigh those values against existing values in order to detect invalid changes. We haven't run into a case yet that compelled us to put ValidateProvisioningParameters back, but we'd certainly consider it if some valid use case for it were presented.

Hi @krancour , I met a case where ValidateProvisiongParameters is needed, that is, two provisioning parameters, say P1 and P2, are both optional parameters, and P2 can only occur when P1 occurs, but P2 doesn't always occur when P1 occurs. Currently, we don't have a elegant way to do this judgement, one possible way is to do the verfication in a provisioning step, but it's better to find the error before any provisioning step is executed.

Glad to send a PR if you think it's OK to add ValidateProvisiongParameters in the ServiceManager interface.

This can be done, I believe with a custom validation on the schema object that contains both P1 and P2.

Oh ya... you're right, thanks for the tips!

No problem. I'm going to close this for now because I think we're mutually convinced that we don't need to add this to the ServiceManager interface at this point in time. I'm very happy to have this re-opened and re-considered in the future if the need presents itself.

Reopen via #628 . That PR adds a parameter accountType. If accountType is set to "Premium_LRS", only "Hot" can be used in accessTier. accountType and accessTier are not related tiggtly, so it's not proper to merge these two parameters into an object, and thus the constraint is not detectable using schema. In this case, ValidateProvisiongParameters can help.


TabNine leaks inotify and epoll file descriptors

Output of ls /proc/$(pgrep TabNine)/fd: https://gist.github.com/tbodt/45803e2b9cac6086361532b84e329361
There are a few slightly strange looking things in the logs, such as a ton of these:
[2019-05-24][09:34:40][server::pipeline::walk][ERROR] error unwatching "[redacted]": invalid input parameter
[2019-05-24][09:34:40][server::pipeline::walk][ERROR] error unwatching "[redacted]": No watch was found.

and also a ton of these, a few hours later:
[2019-05-24][11:06:00][server::pipeline::walk][ERROR] TabNine will not work properly because the filesystem watcher couldn't be created due to an error: other os error

I'm on version 1.0.14.

Does this still reproduce for you?

Will close since I've stopped using tabnine


Protonmail automatically inserting "Reply-To" field

When I send an email from Gmail, the recipient will see a "From" field.
When I send an email from Protonmail, the receipient will see a "From" field and a "Reply-To" field, both of them pointing to the same email address (email of the sender).
I thought it was a bug with Protonmail bridge but I tried it also with the webmail and from 2 different accounts and it always inserts "Reply-To". Emails look less clean like that, is there a way to disable that?

I forget the details but we do this for compatibility with some email service providers, and as headers are not usually shown in email clients unless they are relevant. Which client are you having trouble with? Or do you just not like the presence of the redundant header?

I just don't like the presence of this redundant header, as it's not pure and I notice it when it comes from someone else. And Gmail doesn't need to set the "Reply-To" field to be compatible with every providers, so I don't get why Protonmail would need this field to be compatible.


Sync default init script with latest upstream changes

Description
This syncs the default (debian/ubuntu) init script with the one included
in version 1.7.6 of the PPA package. The changes should work fine with
older haproxy versions as well.
Changes include:

Remove the ENABLED option and corresponding check
Create the run directory needed by the stats socket if missing (which
can happen after a reboot, since /run is on a tmpfs)
Handle multiple PIDs properly

Contribution Check List

[x] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

This change is

The linter warnings in the travis build don't appear related to my changes.

Can you update your branch please?
This should be fixed by #236

Done, build passed!

thanks @jbarbuto for your submission. I will cut a new release when the other PR gets merged

@rshade I just noticed something you may want to account for before release. It looks like changes to the init script template aren't applied by poise_service after initial script install (possibly because it sets action :create_if_missing). That means those who upgrade their cookbook won't get the init script changes, which could cause breakage since it'll still have the ENABLED option check though /etc/default/haproxy will be updated to remove that option.
You may want to see if poise_service has an option to apply template updates, and otherwise keep the ENABLED option in /etc/default/haproxy.

I am going to bump the minor version, also the cookbook doesn't remove/create it so they should be good. I forgot to get you to update the changelog. Can you do that and do another PR? sorry man

@rshade Sure thing, changelog updated in https://github.com/sous-chefs/haproxy/pull/238


upgrade the sdrf-pipelines 0.0.29 -> 0.0.30

Summary by CodeRabbit

New Features

Added new command-line options for ms2rescore to specify regex patterns for spectrum and PSM files.
Introduced cross-validation checks for spectrum IDs in the PSH sub-table to enhance data integrity.

Bug Fixes

Improved error handling for missing files in the conversion script.

Improvements

Updated dependency versions to enhance performance and compatibility, including sdrf-pipelines, setuptools, and scikit-learn.
Enhanced the performance of precursor mass calculations through optimized data processing.
Updated module version number for clarity.

Related with https://github.com/bigbio/quantms/issues/427


Fix webhooks part of integration-guide.

Automated message from Dropbox CLA bot
@TomaszKolek, it looks like you've already signed the Dropbox CLA. Thanks!

You seem to have missed some of the references to test_hooks.  I fixed them and merged this as 7df50cee34465acb5c3e11a718f7d7a3cb7feec4.

(Thanks for working on this @TomaszKolek!)


stty: standard input: Inappropriate ioctl for device

Description
Since e86200e7aad9d4ccbabd34222ffcded3f52c6f65, prezto will execute stty -ixon on startup. On my system, this results in the following error:
stty: standard input: Inappropriate ioctl for device

It might be because I am using Powerline10k with its instant prompt. I think Standaard input and output is redirected if you use it.
I have had this in my .zshrc for a while, which does work:
stty -F/dev/tty -ixon -ixoff

However, I'm not sure /dev/tty is correct in all cases. Maybe add on option to disable the stty command or specify the tty explicitly?
Expected behavior
No errors during the start of zsh.
Actual behavior
The error: stty: standard input: Inappropriate ioctl for device
Steps to Reproduce

Start zsh

Versions

Prezto commit: e86200e7aad9d4ccbabd34222ffcded3f52c6f65
ZSH version: zsh 5.7.1 (x86_64-ubuntu-linux-gnu)
OS information: Ubuntu 19.10

Hi, to say iI got the same zsh stack as you and got the same error.

Fixed by #1771

Should be fixed now. Thanks for the report!


Update translations based on the August 30th English strings

See #23055
commit 9f19a2cc5eda25abf8bb0437aa7e260a6d9e368b
Update English Translations 2024-08-30T21:13:15Z

Backported to radjabov in commit a89653a898bacdfb257e69f5ea383e03c58b6ab1.
commit a89653a898bacdfb257e69f5ea383e03c58b6ab1
Author: Jason Frey<EMAIL_ADDRESS>Date:   Thu Sep 5 10:22:18 2024 -0400

    Merge pull request #23174 from jrafanie/update_translations_based_on_august30_english

    Update translations based on the August 30th English strings

    (cherry picked from commit 34335f9ec5f2adb7180668db28b4ae0441b5700e)


Update egui to 0.8.0

This update comes alongside https://github.com/hasenbanck/egui_wgpu_backend/pull/7 to update egui and everything else.

Ah! Lazy me didn't check for existing PRs like this one.. https://github.com/hasenbanck/egui_winit_platform/pull/4

Closing in favor of https://github.com/hasenbanck/egui_winit_platform/pull/4


How to access to registers?

Hello,
I would like to restore from a snapshot file format for a zx spectrum emulator. I need to set the registers to restore snapshot. I could not find a way to access to registers. How to access and set the registers?
Thanks

@cool2apps you can create an instance of Z80CPU and use the state getter/setter to change the register set.
https://pub.dev/documentation/z80/latest/z80/Z80CPU-class.html
https://pub.dev/documentation/z80/latest/z80/Z80State/state.html

Still not able to access to the registers. I guess setters and getters for the registers are missing.


Search bar missing, leaves blank space

I know the settings icon was already referenced in another issue. I tried deleting and reinstalling - the search bar showed up the first time I opened up the reinstalled version, then disappeared the next few times I opened the app.

Fixed in #103


getImage() timeout after third image acquisition

I have created a ImageAcquirer Object and am getting Images from the camera. But after the third acquisition I am getting a TimeOut Error and have to start the camera again. Is there a way to solve this by, f.e. change the trigger to manual?

What kind of device are you using? Could you try to grab the image in the following way:
for x in range (0,20):
    ia.start()
    with ia.fetch() as buffer:
        pass
    print(f'Grabbing image {x} / 20')
    ia.stop()

Could you also try to change the BandwidthReserve setting?
ia.remote_device.node_map.BandwidthReserve.value = 90 # default is 10 I guess?

What device are you using to grab the images? On lower end devices bandwith sometimes is a problem (or with wrong cables / switches)

I ran into the same issue using:
ia.start()
for _ in range(4):
    buffer = ia.fetch()
    component = buffer.payload.components[0]
    np_array = np.copy(component.data.reshape(component.height, component.width))
ia.stop()

The solution is to use a context manager, like indicated by MathijsNL:
ia.start()
for _ in range(4):
    with ia.fetch() as buffer:
        component = buffer.payload.components[0]
        np_array = np.copy(component.data.reshape(component.height, component.width))
ia.stop()

It should probably raise an error when using fetch without the context manager.


Warning: Functions are not valid as a React child

Using solid and trying to use them in some provider, throws this error:
 ERROR  Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.
    in provider (created by provider_ReactBridge)
    in provider_ReactBridge (created by SessionProvider_Solid)
    in SessionProvider_Solid (at App.tsx:12)
    in RNCSafeAreaView (at SafeAreaView.tsx:14)
    in Unknown (at App.tsx:11)
    in LoftyApp (at renderApplication.js:50)
    in RCTView (at View.js:32)
    in View (at AppContainer.js:92)
    in RCTView (at View.js:32)
    in View (at AppContainer.js:119)
    in AppContainer (at renderApplication.js:43)
    in LoftyApp(RootComponent) (at renderApplication.js:60)

My provider:
// @solid
import React from 'react';
import {View} from 'react-native';
import {createSignal} from 'solid-native';
import * as solid from 'solid-native';

export interface SessionContextData {
  session: User | null;
}

export interface User {
  name: string;
  email: string;
}

export const SessionContext = solid.createContext<SessionContextData>({} as SessionContextData);

const SessionProvider: React.FC = ({children}) => {
  const [user, setUser] = createSignal<User | null>(null);

  return (
    <SessionContext.Provider
      value={{
        session: null,
      }}>
      {children}
    </SessionContext.Provider>
  );
};

export default SessionProvider;

This error is because solid's Context is not currently supported – you should use React's context instead.

Oh thank you, i will check. Sorry for didn't read it fully.


bug: inventory resources are not updates after reserve release

Node resources are not updated on reserver event. same seem to happens with unreserve signal.
note: will be fixed as part of the SDL update

@troian  it looks like this may have been fixed here https://github.com/ovrclk/akash/commit/a64ca04ad9218d06dab286c94c76b40f6606346f#diff-2b3feaa73af2b179a1fd81234bc35deed01d35995e53d5ee772470d193edccdfR325 . Do you agree?

yah, that change fixed it

Alright I'm going to go ahead and close this then since it doesn't look like there is anything left to do.


JSON output

It would be helpful to have the option of JSON output from analysis commands. We want to run automated analyses on the results, so it would be preferable to parsing the text output.
I can try to implement it if you agree to it.

@aelij Yes, please feel free to create PRs


[prism] New port

[x] Changes comply with the maintainer guide
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

@microsoft-github-policy-service agree

2023-10-04T07:12:26.7883193Z Time to determine pass/fail: 16 s
2023-10-04T07:12:26.7890980Z Installing 1/1 prism:x64-windows...
2023-10-04T07:12:26.7898316Z Building prism:x64-windows...
2023-10-04T07:12:26.7905520Z -- Downloading https://github.com/nocanstillbb/prism/archive/48ba3101e668878cab2a5f56e13b238d4f7ea5eb.tar.gz -> nocanstillbb-prism-48ba3101e668878cab2a5f56e13b238d4f7ea5eb.tar.gz...
2023-10-04T07:12:26.8025913Z -- Extracting source D:/downloads/nocanstillbb-prism-48ba3101e668878cab2a5f56e13b238d4f7ea5eb.tar.gz
2023-10-04T07:12:26.9301552Z -- Using source at D:/buildtrees/prism/src/8d4f7ea5eb-2ddfd0cfd0.clean
2023-10-04T07:12:26.9453740Z -- Found external ninja('1.11.0').
2023-10-04T07:12:26.9516386Z -- Configuring x64-windows
2023-10-04T07:12:28.5584588Z CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
2023-10-04T07:12:28.5591715Z     Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
2023-10-04T07:12:28.5599243Z     Working Directory: D:/buildtrees/prism/x64-windows-rel/vcpkg-parallel-configure
2023-10-04T07:12:28.5605918Z     Error code: 1
2023-10-04T07:12:28.5612929Z     See logs for more information:
2023-10-04T07:12:28.5619987Z       D:\buildtrees\prism\config-x64-windows-dbg-CMakeCache.txt.log
2023-10-04T07:12:28.5626474Z       D:\buildtrees\prism\config-x64-windows-rel-CMakeCache.txt.log
2023-10-04T07:12:28.5633008Z       D:\buildtrees\prism\config-x64-windows-out.log
2023-10-04T07:12:28.5636233Z
2023-10-04T07:12:28.5642653Z Call Stack (most recent call first):
2023-10-04T07:12:28.5651791Z   scripts/cmake/vcpkg_configure_cmake.cmake:314 (vcpkg_execute_required_process)
2023-10-04T07:12:28.5658350Z   ports/prism/portfile.cmake:16 (vcpkg_configure_cmake)
2023-10-04T07:12:28.5664613Z   scripts/ports.cmake:168 (include)
2023-10-04T07:12:28.5667630Z
2023-10-04T07:12:28.5670642Z
2023-10-04T07:12:28.5716768Z error: building prism:x64-windows failed with: BUILD_FAILED
2023-10-04T07:12:28.5723382Z Elapsed time to handle prism:x64-windows: 1.9 s
2023-10-04T07:12:28.5729787Z Total install time: 1.9 s
2023-10-04T07:12:28.5732805Z
2023-10-04T07:12:28.5739306Z Triplet: x64-windows
2023-10-04T07:12:28.5746302Z RESULTS
2023-10-04T07:12:28.5752954Z   prism:x64-windows: BUILD_FAILED: 1.9 s

How do i see the error log details?
I can install in my local repository,
Does the header only port require additional settings, before creatoed pr

https://github.com/microsoft/vcpkg/issues/34284
catch2 has installed to  top level/vcpkg_installed,  prism build still error after catch2 installed,

There is not a problem with catch2 but
FAILED: CMakeFiles/tst_prism.dir/tests/test_prism.cpp.o
/usr/bin/c++  -I/mnt/vcpkg-ci/buildtrees/prism/x64-linux-dbg -I/mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean -isystem /mnt/vcpkg-ci/installed/x64-linux/include -fPIC -finput-charset=UTF-8 -g -std=gnu++17 -Wall -Wextra -MD -MT CMakeFiles/tst_prism.dir/tests/test_prism.cpp.o -MF CMakeFiles/tst_prism.dir/tests/test_prism.cpp.o.d -o CMakeFiles/tst_prism.dir/tests/test_prism.cpp.o -c /mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean/tests/test_prism.cpp
In file included from /mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean/tests/test_prism.cpp:1:
/mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean/include/prism.hpp: In member function ‘bool Prism::Enum::CompareCharPointers::operator()(const char*, const char*) const’:
/mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean/include/prism.hpp:722:25: error: ‘strcmp’ is not a member of ‘std’
  722 |             return std::strcmp(a, b) < 0;
      |                         ^~~~~~
/mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean/include/prism.hpp:724:25: error: ‘strcmp’ is not a member of ‘std’
  724 |             return std::strcmp("", b) < 0;
      |                         ^~~~~~
/mnt/vcpkg-ci/buildtrees/prism/src/12d8f70d10-35bca27bd1.clean/include/prism.hpp:726:25: error: ‘strcmp’ is not a member of ‘std’
  726 |             return std::strcmp(a, "") < 0;
      |                         ^~~~~~

Check the vcpkg CI logs: https://github.com/microsoft/vcpkg/discussions/31357
Please do more CMake cleanup.
And please do disable tests (or make them optional) in the portfile.

Note: I will be converting your PR to draft status. When you're ready, please revert to "ready for review".

Note: I will be converting your PR to draft status. When you're ready, please revert to "ready for review".
Since I want to integrate multiple libraries into a multi-component package, this merge request is temporarily


[SPARK-33339][PYTHON] Pyspark application will hang due to non Exception error

What changes were proposed in this pull request?
When a system.exit exception occurs during the process, the python worker exits abnormally, and then the executor task is still waiting for the worker for reading from socket, causing it to hang.
The system.exit exception may be caused by the user's error code, but spark should at least throw an error to remind the user, not get stuck
we can run a simple test to reproduce this case:
from pyspark.sql import SparkSession
def err(line):
  raise SystemExit
spark = SparkSession.builder.appName("test").getOrCreate()
spark.sparkContext.parallelize(range(1,2), 2).map(err).collect()
spark.stop()

Why are the changes needed?
to make sure pyspark application won't hang if there's non-Exception error in python worker
Does this PR introduce any user-facing change?
No
How was this patch tested?
added a new test and also manually tested the case above

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Just curious. Why would you run system.exit? You should better just throw a proper exception. Calling system.exit inside the UDFs wouldn't terminate user applications as intended.

Just curious. Why would you run system.exit? You should better just throw a proper exception. Calling system.exit inside the UDFs wouldn't terminate user applications as intended.

Below is the case I encountered, and it's cause by the code had a method named 'testUdf' and a udf obj also named 'testUdf', then worker exit. And I think the application should not hangup without any information anyway
import pyspark.sql.functions as F
from pyspark.sql.types import *
from pyspark.sql import SparkSession

def testUdf(x):
    return x+1

spark = SparkSession.builder.appName("test").getOrCreate()
testUdf=F.udf(lambda x: testUdf(x),DoubleType())

df = spark.sql("select float(2.145025959889993) as a")
df.withColumn("test", testUdf(df.a)).show()

@li36909 Could you update the description? Currently it's misleading.
@HyukjinKwon Actually system.exit is throw because user writes some incorrect code (e.g. try to create a SparkContext in a executor task while no SPARK_HOME is available on that node, or the udf case @li36909 mentioned). We have found several such cases from unskilled Spark customers.
It would be better for Spark to throw an exception to the user, rather than hanging and making users not know what to do.

@li36909 Could you update the description? Currently it's misleading.
@HyukjinKwon Actually system.exit can happen when user writes some incorrect code (e.g. try to create a SparkContext in a executor task while no SPARK_HOME is available on that node, or the udf case @li36909 mentioned).
We have found several such cases from unskilled PySpark customers.
It would be better for Spark to throw an exception to the user, rather than hanging and making users not know what to do.

updated

ok to test

jenkins, test this please

Test build #130646 has started for PR 30248 at commit fb8d325.

Test build #130646 has finished for PR 30248 at commit fb8d325.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130646/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35256/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35257/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35256/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35256/
Test FAILed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35257/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35257/
Test PASSed.

@HyukjinKwon @wzhfy

LGTM

I'm ok with the change, but since I'm not very familiar with pySpark, @HyukjinKwon could you take another look?

Test build #130852 has started for PR 30248 at commit 8863dbb.

Test build #130852 has finished for PR 30248 at commit 8863dbb.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130852/
Test FAILed.

Test build #130854 has started for PR 30248 at commit e5c33f0.

Test build #130854 has finished for PR 30248 at commit e5c33f0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130854/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35462/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35460/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35460/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35460/
Test PASSed.

Merged to master, branch-3.0 and branch-2.4.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35462/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35462/
Test PASSed.

It has a conflict in branch-2.4. It's sort of a corner case so I think we don't bother porting it back. @li36909, please go ahead and open a PR to backport if you're willing to do.

It has a conflict in branch-2.4. It's sort of a corner case so I think we don't bother porting it back. @li36909, please go ahead and open a PR to backport if you're willing to do.

ok, I will open a PR at branch-2.4, thank you!


Added JSX typings

Added JSX typings.
Fixes https://github.com/Microsoft/TypeScript/issues/3679

@janb87 fyi left a review comment a few days ago if you don't mind taking a look.

@cantide5ga somehow I don't seem to find the comment inside the web interface. Did see it as an e-mail notification.
To come back at your remark. I was thinking to put the "JSX" typings in a separate file but this is not so easy as there is indeed a circular dependency between React and JSX. Don't know how this can be achieved actually. Putting it in the same file seems to be the only option I think.

@janb87 Ok. This is actually failing some of my projects (I've never needed JSX definitions in this way), but it's probably because of some improvements in the type def we got for free due to your improvements here.
This is needed by a lot of folks, so I'll merge and update the registry ASAP.  I might circle back on this to see if we can externalize it and include you on the review if I come up with anything.
Thanks again!  Standby...


Use spiceai-runners for running benchmark tests

Closed by: https://github.com/spiceai/spiceai/pull/3514


dead link(s) on the web site

issue
the link to download the win version on the website (https://murmele.github.io/Gittyup/) is:
https://github.com/Murmele/Gittyup/releases/download/stable/Gittyup-win64-1.1.0.exe
the link is not available. only the newer release:
https://github.com/Murmele/Gittyup/releases/download/stable/Gittyup-win64-1.1.1.exe
is available.
probably the links for the other platforms are also invalid (did not check)

suggestion
remove the version from the downloads on the website and just link to
https://github.com/Murmele/Gittyup/releases
that way you dont need to update your site every time

Hi @alexn-s thanks. I pushed it to ghpages, so it will be deployed soon. Was just not updated, because no new release since those updates was created


Add tile display to the UI

It appears you also need the following PHP extensions: php8.1-xml, php8.1-mbstring and php8.1-curl.
You need to document them and/or add a Makefile target to install them.

Otherwise I've tested the webapp and it works fine, well done! :muscle:


add async support

This PR adds embedded-hal-async support if async feature flag is enabled.

Changed the order and removed duplicated doc comments.

Indeed such cfg trick did not work and I added duplicated docs back for async.


Xargo doesn't respect rustc path set in .cargo/config

I have a local .cargo/config file which sets the path to rustc:
$ cat .cargo/config
[build]
rustc = "/home/cactus/prog/rust/rust-avr/build/build/x86_64-unknown-linux-gnu/stage1/bin/rustc"
target = "avr-atmega328p.json"

It seems that Xargo doesn't pick this up:
$ strace -f -eexecve xargo build
...
[pid 31801] execve("/home/cactus/.cargo/bin/rustc", ["rustc", "-vV"], [/* 62 vars */]) = 0
...

Of course, invocations of rustc via cargo (as run by xargo) pick up the right rustc; but Xargo it self runs the wrong rustc for its own purposes.

Whoops, I don't think I ever tested this setup.
In the meantine you could use rustup to create a custom toolchain that points to your stage1 rustc. That's known to work.
$ cd /home/cactus/prog/rust/rust-avr/build/build/x86_64-unknown-linux-gnu/stage1
$ rustup toolchain link avr-toolchain .
$ rustup default avr-toolchain
$ rustc -V
# should say dev channel

BTW in a similar vein, it also doesn't respect the target setting from .cargo/config.

it also doesn't respect the target setting

which target setting exactly? AFAIK build.target is respected.

Sorry, yes, you're right, that was caused by including the .json suffix in my target name.


Are there Findlibrealsense.cmake provided?

Required Info

Camera Model
R200 / F200 / SR300 / ZR300 / D400

Firmware Version

Operating System & Version

Kernel Version (Linux Only)

Hi @csuwp
That's a great question, at the moment we do not provide one, but we should and will.
@zivsha has previously provided a sample for CMake integration here. This is not quite what you want but it might help you get started.

Thanks for reply, but I am using the this lib in ubuntu16.04.The cmake you provide seems don't work

librealsense2 installs
/usr/local/lib/cmake/realsense2/realsense2Targets.cmake
/usr/local/lib/cmake/realsense2/realsense2Targets-noconfig.cmake
/usr/local/lib/cmake/realsense2/realsense2Config.cmake

In your CMake you can have
set(LIBREALSENSE_INSTALLATION_DIR "" CACHE PATH "librealsense installation directory")
if(LIBREALSENSE_INSTALLATION_DIR STREQUAL "")
    find_package(realsense2 REQUIRED)
else()
    find_package(realsense2 REQUIRED PATHS ${LIBREALSENSE_INSTALLATION_DIR} NO_DEFAULT_PATH)
endif()

...

target_link_libraries(my-target PRIVATE realsense2::realsense2)

For 1.0 I am not sure if you can do that.

I have one question @sogartar
I followed this document to install librealsense2 and find_package(realsense2) works smoothly
However when I check
/usr/local/lib/cmake/realsense2/realsense2Targets.cmake
/usr/local/lib/cmake/realsense2/realsense2Targets-noconfig.cmake
/usr/local/lib/cmake/realsense2/realsense2Config.cmake

There are no such things
Also I searched those three files from root to bottom but I failed to find them.
Then how my cmake can find realsense2?
dpkg -l showed realsense libraries however I couldn't find any connection between find_package function and dpkg

Use following template for realsense intergartion in CMake
`cmake_minimum_required(VERSION 2.8)
project(project_name)
set(CMAKE_EXPORT_COMPILE_COMMANDS 1)
include(CheckCXXCompilerFlag)
CHECK_CXX_COMPILER_FLAG("-std=c++11" COMPILER_SUPPORTS_CXX11)
CHECK_CXX_COMPILER_FLAG("-std=c++0x" COMPILER_SUPPORTS_CXX0X)
if(COMPILER_SUPPORTS_CXX11)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -std=c11")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
elseif(COMPILER_SUPPORTS_CXX0X)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++0x")
endif()
find_package(realsense2 REQUIRED )
add_executable( target_name src/source.cpp )
include_directories(include ${realsense_INCLUDE_DIR})
target_include_directories(target_name PRIVATE ${realsense_INCLUDE_DIR})
target_link_libraries(rs-align ${realsense2_LIBRARY})`


Derive Eq and Ord for Msaa

Objective

Msaa already implements the partial relation traits, but there isn't much of a reason to not implement the total ones.

Solution

Add Eq and Ord to the derive list.

Msaa already implements the partial relation traits, but there isn't much of a reason to not implement the total ones.

The question shouldn't be "why not" when adding derives, it should be "why". They add to the compilation time and to the binary size.
If you have a practical use for them, no problem, but that doesn't seem the case here from your description

I'm writing an editor that allows editing enums like this with a function
fn edit_enum<T: fmt::Debug + Eq + Clone>(&mut self, value: &mut T, choices: &[T])

This does not currently work with Msaa because it does not implement Eq. I could relax the bound to PartialEq, but that would be semantically incorrect.
Rust's API guidelines also recommend eagerly implementing all applicable core traits.


Autocrop

Detect where the maze is in an image and then crop the image accordingly.

Example of contour finding:
https://www.pyimagesearch.com/2020/08/10/opencv-sudoku-solver-and-ocr/


Use woodpecker plugin instead of drone one

Let's see if it works.
Would also profit from an actual semver.

I don't know but do we use this in other repos? (Just checked the main repo there it's the old one)

I guess it's not used anywhere yet but (most likely) because nobody updated it yet?
@anbraten @6543 ?


Error handling and DLQ support for IO operation failures.

Adding error handling and DLQ support for file(IO) operation failures.

@ohadbitt Please take a look.


terminate backend on each phase

Enables to terminates phases on each phase so shutdown could be grateful

Depends on https://github.com/Azure/ARO-RP/pull/153 outcome

This seems like a much bigger change than the PR title "terminate backend on each phase" - is it all required?  Can the PR be spit into smaller bits so we can proceed piece by piece?  This is hard to review without context.

@jim-minter done. It was just cosmetic changes.


Security Notice & Bug Bounty - Cross-site Scripting (XSS) - huntr.dev

Overview
radiant is a simple and powerful publishing system designed for small teams.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to a lack of sanitization. It affects Personal Preferences (Name and Username), Configuration (Site Title, Dev Site Domain, Page Parts, and Page Fields), and the admin/pages/*/edit resource via crafted Markdown input in the part_body_ content parameter.
Bug Bounty
We have opened up a bounty for this issue on our bug bounty platform. Want to solve this vulnerability and get rewarded 💰? Go to https://huntr.dev/
We will submit a pull request directly to your repository with the fix as soon as possible. Want to learn more? Go to https://github.com/418sec/huntr 📚
Automatically generated by @huntr-helper...

Bug Bounty
We have opened up a bounty for this issue on our bug bounty platform. Want to solve this vulnerability? Go to https://huntr.dev/
We will submit a pull request directly to your repository with the fix as soon as possible. Want to learn more? Go to https://github.com/418sec/huntr 📚
Automatically generated by @huntr-helper...


Setup unit testing

Just setup some minimal unit testing to get this started, preferably using gtest.

Resolved by: #99


Hindi language translation mentioned twice in README.md

Hindi language translation mentioned twice in README.md and both of those mentions are from different users with different repositories.

Yes, Hindi language translation mentioned twice but only one did its job so then by Vikas Chauhan translates given list and Instruction in

Hindi language by other just open a copy of Main ReadMe.md file which is unnecessary.
Possible Solution: Removing the Other mentioned link which just open the copy of main branch which is by - Mahima Chauhan

/attempt


Set filters not showing in applied filters list for some charts

I'm trying to filter a dashboard but when I apply a filter, for some of the charts, the filter is set but does not appear in the applied filters list. The filters work as usual, they just don't appear as "applied filters".
For instance, two of the charts use the same dataset: in the bar chart I can see this behavior and in the big number everything works fine.
How to reproduce the bug
I'm not sure how to reproduce that because it seems to happen just for some charts and some filters.
Expected results
The filters applied appear in the "applied filters" list
Actual results
The filter I set is in the "unset list"
Screenshots
In the first image, I applied "Período" and "Porte" filters but only one of them appear as applied:

In the second image I tested another filter:

In the third image, I added another filter and the four of them appear as applied:

Environment
(please complete the following information):

browser type and version: Google Chrome 112.0.5615.165
superset version: 2.1.0
python version: python --version
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

I'm not sure if this is still an issue in current versions of Superset (3.x). If it is, we can re-open this, or feel free to open a new issue with updated context and a reproducible case using example data. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale.


DCOS-42035: Invalid Environment variables have no error and are simply ignored (1.10 backport)

backport for https://github.com/dcos/dcos-ui/pull/3234 with some minor fixes
Half of https://jira.mesosphere.com/browse/DCOS-42035
This branch was created using @DanielMSchmidt 's tool https://github.com/DanielMSchmidt/backporter which works great.
Testing

Switch to branch 1.10 and set up node to use version 4.4.7 and npm to use version 3.9.6
I recommend using a new copy of the dcos-ui repository.
Setting up node is easy: just use a node version manager (I used https://github.com/creationix/nvm) and run (if you are using nvm) nvm install 4.4.7 in the directory. Setting up npm is a bit trickier - navigate to the nvm directory, for example cd ~/.nvm/versions/node/v4.4.7/lib and run npm install<EMAIL_ADDRESS>Then run npm install.
Test the changes
Click on Services Tab
Click + or Run a Service to add a new service
Click on Single Container
Click on Environment
Click on Add Environment Variable
Enter a Value without entering Key
Verify that an error message is shown
Test the same thing for a Multi-Container

Trade-offs
None
Dependencies
None
Screenshots
Before

After

After with css change

run system tests

Same question https://github.com/dcos/dcos-ui/pull/3299/files#r218788984

run system tests

run system tests

run system tests

run system tests


panzoom demo stutters when trying to zoom

Exactly like the title says: it zooms for a moment, then stops. Panning still works fine though. I made a little screencapture to show the effect:
https://youtu.be/UlrHnesO2nA
As you can see the demo used to work just fine in Vega 2.x.
Tested in both Chrome and Firefox, with both trackpad and USB mouse, on an Ubuntu 16.04 distro.

Thanks! The culprit appears to be missing "force": true directives that ensure that wheel events are processed regardless if the zoom signal value changes or not. I pushed a fix in b7c0dfa9c3e11b2d1642e59f78b4812ac04b34cd.
I was able to replicate the error and verify a solution using Chrome within a Windows 10 virtual machine. If the fix does not work for you, please feel free to re-open the issue.

Yep, it works here as well! Just a heads-up: I got this (seemingly unrelated) test error after running git pull, npm install
 not ok 13 ValidationError: Data does not match any schemas from "oneOf"
  ---
    operator: ok
    expected: true
    actual:   false
    at: Test.<anonymous> (/home/job/Dev/LinnarssonLab/vega/test/schema-test.js:67:9)
  ...

Yes, a bunch of modules are still being updated, so periodically flushing the node_modules can help (unless you have local npm link connections between repos). I just pushed a significant update that also affects the Vega 3 JSON syntax, so you will want to do this again now.


Test ember-alpha in CI.

Also tweaked a test to use willDestroyElement instead of willClearRender (after discovering that the glimmer renderer wasn't calling the hook). I submitted https://github.com/emberjs/ember.js/pull/14090 to fix that upstream, but it seems good to change our usage also (since willClearRender doesn't make conceptual sense any longer).

Thanks @rwjblue!


'Unknown storage driver "ephemeral"' after installation

Description of problem
I followed the developer hand build/install instructions for the runtime/proxy/shim/osbuilder as per https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#initial-setup , and upon doing a test docker run --rm -it --runtime=kata-runtime busybox sh, I got the following:
$ docker run --rm -it --runtime=kata-runtime busybox sh
docker: Error response from daemon: OCI runtime create failed: rpc error: code = InvalidArgument desc = Unknown storage driver "ephemeral": unknown.

I expect this is an installation problem at my end, but I am logging it in an issue so if somebody else runs into the same, they can search the github project for clues.
I will post results if/when I figure out what the issue is.
Expected result
Expected to run to a busybox shell prompt.

Meta details
Running kata-collect-data.sh version 1.0.0 (commit ca9f7abba96e5c4db734673b9e7d870076d715e2) at 2018-06-13.10:43:14.553600677+0100.

Runtime is /usr/local/bin/kata-runtime.
kata-env
Output of "/usr/local/bin/kata-runtime kata-env":
[Meta]
  Version = "1.0.12"

[Runtime]
  Debug = false
  [Runtime.Version]
    Semver = "1.0.0"
    Commit = "ca9f7abba96e5c4db734673b9e7d870076d715e2"
    OCI = "1.0.1"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 2.7.0, Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-lite-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  Msize9p = 8192
  Debug = false

[Image]
  Path = "/usr/share/kata-containers/kata-containers-2018-06-13-10:29:25.914995186+0100-3375e73"

[Kernel]
  Path = "/usr/share/kata-containers/kata-vmlinuz-4.14.22.container"
  Parameters = ""

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.0.0-a69326b63802952b14203ea9c1533d4edb8c1d64"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = false

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.0.0-087a5371680f069d45baed8544a09b4e6353c06e"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = false

[Agent]
  Type = "kata"

[Host]
  Kernel = "4.4.0-104-generic"
  Architecture = "amd64"
  VMContainerCapable = true
  [Host.Distro]
    Name = "Ubuntu"
    Version = "16.04"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz"

Runtime config files
Runtime default config files
/etc/kata-containers/configuration.toml
/usr/share/defaults/kata-containers/configuration.toml

Runtime config file contents
Config file /etc/kata-containers/configuration.toml not found
Output of "cat "/usr/share/defaults/kata-containers/configuration.toml"":
# Copyright (c) 2017-2018 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/usr/bin/qemu-lite-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
#initrd = "/usr/share/kata-containers/kata-containers-initrd.img"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = ""

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 1

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 0

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
#default_memory = 2048

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is either virtio-scsi or
# virtio-blk.
block_device_driver = "virtio-scsi"

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
#enable_hugepages = true

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
#enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

[proxy.kata]
path = "/usr/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[shim.kata]
path = "/usr/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[agent.kata]
# There is no field for this section. The goal is only to be able to
# specify which type of agent the user wants to use.

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
#enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
internetworking_model="macvtap"

Image details
unknown

Initrd details
No initrd

Logfiles
Runtime logs
Recent runtime problems found in system journal:
time="2018-06-13T10:37:21.954488162+01:00" level=warning msg="shortening QMP socket name" arch=amd64 name=kata-runtime new-name=mon-d7ad8ce5-aedd-4e51-a123-97 original-name=mon-d7ad8ce5-aedd-4e51-a123-974bdfd11d0a pid=6860 source=virtcontainers subsystem=qemu
time="2018-06-13T10:37:21.954527646+01:00" level=warning msg="shortening QMP socket name" arch=amd64 name=kata-runtime new-name=ctl-d7ad8ce5-aedd-4e51-a123-97 original-name=ctl-d7ad8ce5-aedd-4e51-a123-974bdfd11d0a pid=6860 source=virtcontainers subsystem=qemu
time="2018-06-13T10:37:23.110753334+01:00" level=error msg="rpc error: code = InvalidArgument desc = Unknown storage driver \"ephemeral\"" command=create name=kata-runtime pid=6860 source=runtime

Proxy logs
No recent proxy problems found in system journal.
Shim logs
No recent shim problems found in system journal.

Container manager details
Have docker
Docker
Output of "docker version":
Client:
 Version:       17.12.1-ce
 API version:   1.35
 Go version:    go1.9.4
 Git commit:    7390fc6
 Built: Tue Feb 27 22:17:40 2018
 OS/Arch:       linux/amd64

Server:
 Engine:
  Version:      17.12.1-ce
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   7390fc6
  Built:        Tue Feb 27 22:16:13 2018
  OS/Arch:      linux/amd64
  Experimental: false

Output of "docker info":
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 113
Server Version: 17.12.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: kata-runtime runc cc-runtime
Default Runtime: runc
Init Binary: docker-init
containerd version: 9b55aab90508bd389d7654c4baf173a981477d55
runc version: 9f9c96235cc97674e935002fc3d78361b696a69e
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-104-generic
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 31.31GiB
Name: bignuc
ID: ROOX:AUAH:KW7J:BADM:E3PW:ORDN:KL42:FKXQ:77LD:VGKO:ZFY4:OG64
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 20
 Goroutines: 33
 System Time: 2018-06-13T10:43:14.801182099+01:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

WARNING: No swap limit support

Output of "systemctl show docker":
Type=notify
Restart=on-failure
NotifyAccess=main
RestartUSec=100ms
TimeoutStartUSec=infinity
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestamp=Wed 2018-06-13 10:11:09 BST
WatchdogTimestampMonotonic=10111613
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=1129
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Wed 2018-06-13 10:11:07 BST
ExecMainStartTimestampMonotonic=8722491
ExecMainExitTimestampMonotonic=0
ExecMainPID=1129
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -D --add-runtime cc-runtime=/usr/local/bin/cc-runtime --add-runtime kata-runtime=/usr/local/bin/kata-runtime --default-runtime=runc ; ignore_errors=no ; start_time=[Wed 2018-06-13 10:11:07 BST] ; stop_time=[n/a] ; pid=1129 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/docker.service
MemoryCurrent=1204461568
CPUUsageNSec=32484930738
TasksCurrent=44
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitCPUSoft=18446744073709551615
LimitFSIZE=18446744073709551615
LimitFSIZESoft=18446744073709551615
LimitDATA=18446744073709551615
LimitDATASoft=18446744073709551615
LimitSTACK=18446744073709551615
LimitSTACKSoft=8388608
LimitCORE=18446744073709551615
LimitCORESoft=18446744073709551615
LimitRSS=18446744073709551615
LimitRSSSoft=18446744073709551615
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=18446744073709551615
LimitASSoft=18446744073709551615
LimitNPROC=18446744073709551615
LimitNPROCSoft=18446744073709551615
LimitMEMLOCK=65536
LimitMEMLOCKSoft=65536
LimitLOCKS=18446744073709551615
LimitLOCKSSoft=18446744073709551615
LimitSIGPENDING=128104
LimitSIGPENDINGSoft=128104
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=18446744073709551615
LimitRTTIMESoft=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=system.slice docker.socket sysinit.target
Wants=network-online.target
WantedBy=multi-user.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=sysinit.target system.slice docker.socket systemd-journald.socket basic.target network-online.target firewalld.service
TriggeredBy=docker.socket
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/docker.service
DropInPaths=/etc/systemd/system/docker.service.d/clear-containers.conf
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Wed 2018-06-13 10:11:09 BST
StateChangeTimestampMonotonic=10111614
InactiveExitTimestamp=Wed 2018-06-13 10:11:07 BST
InactiveExitTimestampMonotonic=8722514
ActiveEnterTimestamp=Wed 2018-06-13 10:11:09 BST
ActiveEnterTimestampMonotonic=10111614
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Wed 2018-06-13 10:11:07 BST
ConditionTimestampMonotonic=8722147
AssertTimestamp=Wed 2018-06-13 10:11:07 BST
AssertTimestampMonotonic=8722147
Transient=no
StartLimitInterval=60000000
StartLimitBurst=3
StartLimitAction=none

No kubectl

Packages
Have dpkg
Output of "dpkg -l|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"":
ii  linux-container                     4.14.22-86                                  amd64        linux kernel optimised for container-like workloads.
ii  qemu-block-extra:amd64              1:2.5+dfsg-5ubuntu10.24                     amd64        extra block backend modules for qemu-system and qemu-utils
ii  qemu-kvm                            1:2.5+dfsg-5ubuntu10.24                     amd64        QEMU Full virtualization
ii  qemu-lite-bin                       741f430a960b5b67745670e8270db91aeb083c5f-30 amd64        bin components for the qemu-lite package.
ii  qemu-lite-data                      741f430a960b5b67745670e8270db91aeb083c5f-30 amd64        data components for the qemu-lite package.
ii  qemu-system-common                  1:2.5+dfsg-5ubuntu10.24                     amd64        QEMU full system emulation binaries (common files)
ii  qemu-system-x86                     1:2.5+dfsg-5ubuntu10.24                     amd64        QEMU full system emulation binaries (x86)
ii  qemu-utils                          1:2.5+dfsg-5ubuntu10.24                     amd64        QEMU utilities

Have rpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"":

That was easy....
The agent being copied into my osbuilder image had not been updated, so was somewhat 'old'. Updating and rebuilding the agent and adding that into the osbuilder image fixed the issue.
@sboeuf @egernst @jodh-intel - a thought - is our agent API versioned? Do we think it will be possible for us to add a version check between the runtime and the agent to ensure they are compatible, and error out better if they are not. This might avoid us getting strange failures and obscure error messages due to runtime/agent/image incompatibilities in the future?

Hi @grahamwhaley - see:

https://github.com/kata-containers/kata-containers/issues/17
https://github.com/kata-containers/agent/pull/176

Also kind of related: https://github.com/kata-containers/agent/pull/180.


Change cdn start script

Signed-off-by: Gaius<EMAIL_ADDRESS>
Description

change bash to sh

Related Issue

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[x] Code compiles correctly.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #383 (c2573cd) into main (7e634c4) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #383      +/-   ##
==========================================
- Coverage   42.16%   42.11%   -0.05%
==========================================
  Files          74       73       -1
  Lines        5657     5654       -3
==========================================
- Hits         2385     2381       -4
+ Misses       2925     2923       -2
- Partials      347      350       +3

Flag
Coverage Δ

unittests
42.11% <ø> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/net/iputils/ip_utils.go
61.22% <0.00%> (-4.09%)
:arrow_down:

client/daemon/peer/peertask_stream_callback.go
62.50% <0.00%> (-2.50%)
:arrow_down:

client/daemon/peer/peertask_stream.go
56.98% <0.00%> (-1.14%)
:arrow_down:

client/daemon/peerhost_stub.go

client/daemon/peer/peertask_base.go
33.49% <0.00%> (+0.72%)
:arrow_up:


Implements staking

Staking rewards are added to returning transaction from bots. Since GradeCoin does not have any decimals, I have decided to ceil the reward.
Fixes #2

Thank you for your contribution! I'm assuming the T seconds after aspect you talked about in #2 is not required in practice?

It may or may not be required, however this implementation surely creates most amount of transactions in my opinion.
For example, in the regular staking, only the staked amount is updated after every reward period. But this does not create any transactions in the system, which is the purpose of these bots. Therefore we can tweak definitions.


Error with fonts?

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior
Material fonts /icons aren't loaded correctly

Error issued in the console
index.html:1 Failed to decode downloaded font: http://<IP_ADDRESS>:5500/build/font/MaterialIcons-Regular.ttf
index.html:1 OTS parsing error: invalid version tag
Expected behavior

No errors
Environment
Browser:

- [ x] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:

- Live Server: 5.1.1
- Platform:  Windows
- Visual Studio Code: 1.24.1

Others
I've rechecked the same project with a XAMPP Installation, there are no errors displayed in the console
I think there is a txt/binary mismatch for those files

Nothing changes, (the cache is always disabled in my settings)
Failed to decode downloaded font: http://<IP_ADDRESS>:5500/build/font/MaterialIcons-Regular.woff2
index.html:1 OTS parsing error: invalid version tag
index.html:1 Failed to decode downloaded font: http://<IP_ADDRESS>:5500/build/font/MaterialIcons-Regular.woff
index.html:1 OTS parsing error: invalid version tag
index.html:1 Failed to decode downloaded font: http://<IP_ADDRESS>:5500/build/font/MaterialIcons-Regular.ttf
index.html:1 OTS parsing error: invalid version tag

Can you please share a demo project with this issue?
And kindly check, if your issue is related to https://stackoverflow.com/questions/34288778/failed-to-decode-downloaded-font-ots-parsing-error-invalid-version-tag-rails

After creating a dummy, it works... so the error was on my side:
I misinterpreted (actually i didn't rtfm) "liveServer.settings.file" as the startup file for the live server...
So the font-errors are simply none-existing files with the contents of my index.html (-: interpreted as fonts (which crashes)
After i deleted "liveServer.settings.file" they are shown as 404
So thanks for your time, fast reply and this very useful extension!


Change out sqlite to mariadb

Turns out we need a real database for the level of parallel
access. Changes out the database to an instance of mariadb
that is configured upon start-up if necessary with a random
password and unrelated database rights are removed.

Build FAILURE, see build http://<IP_ADDRESS>:8080/job/dev-tools/375/

@dtantsur  dnsmasq and httpd are being moved out, and I think we should keep mysql with the two base services as otherwise we're going to have to do password orchestration and handling.

You mean, have separate mariadb processes for ironic and ironic-inspector? How does it play with the request to have one service per container in #13?

Well, if we split to one service per container, We're just going to have to pre-bake credentials in or use none... Which seems like a security issue to me.

Bottom line, I was on a call where people expressed they were borderlined blocked on hitting the locking issues with sqllite, so if we take the approach for perfection at  the moment, we're going to continue to block their ability to deliver.
On a plus side, I just got my local environment up with the container built from this change and I do have a working ironic \o/

@dtantsur  I think we should only need this. The activity on inspector should be minimal.... should be.

Should be :)

since #16 has been merged, you can separate the db service and use a runmariadb.sh script instead of integrating all in runironic.sh
just not sure if we want to use the same image, but we can split them later if needed

Build FAILURE, see build http://<IP_ADDRESS>:8080/job/dev-tools/414/

merging, CI failed but it had gotten passed the ironic part so this patch should be ok.


EmbedMolecule with CoordMap Incorrectly translates final coords to the origin?

Describe the bug
When EmbedMolecule is used with the coordMap option, the call appears to correctly perform the embedding, but then it seems to translate the molecule to the origin as a final step. Since I supplied explicit coordinates, it is unexpected that the final coordinates are centered around the origin instead of the supplied coordMap.
To Reproduce
from rdkit import Chem
from rdkit.Chem import AllChem
from rdkit.Chem import rdChemReactions
from itertools import chain
from rdkit.Chem.Draw import IPythonConsole
from rdkit.Chem import Draw

#pyrrole with specific coordinates that are not centered around the origin
mol = Chem.MolFromMolBlock("""
  TESTER           3D

  5  5  0  0  0  0  0  0  0  0999 V2000
  -59.3708  -20.9320  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  -60.7208  -20.4930  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  -61.5558  -21.6420  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  -60.7208  -22.7910  -51.5546 N   0  0  0  0  0  0  0  0  0  0  0  0
  -59.3708  -22.3520  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  1  2  1  0  0  0  0
  1  5  2  0  0  0  0
  2  3  2  0  0  0  0
  3  4  1  0  0  0  0
  4  5  1  0  0  0  0
M  END
""")

#transform that ring expands the pyrrole ring into benzene
rxn = AllChem.ReactionFromSmarts('[o,s,nX3;r5;R1:1]:[ar5:2]>>[c:1]:[c]:[*:2]')
output = rxn.RunReactants((mol,))
prod = list(chain(*output))[0]

#peek at the product and notice that the unchanged atoms have the expected coords
#however the new C atom has coords at the origin (unwanted, but expected) -- we will fix  using EmbedMolecule()
prod
print(Chem.MolToMolBlock(prod))

#set the coord map using the coords from the starting material
cmap = {}
for i,atom in enumerate(prod.GetAtoms()):
    d = atom.GetPropsAsDict()
    react_atom_idx = d.get('react_atom_idx', None)
    if react_atom_idx:
        cmap[atom.GetIdx()] = mol.GetConformer().GetAtomPosition(react_atom_idx)

#print the coordMap and notice that the points correctly match the starting pyrrole
[(i,j.x,j.y,j.z) for i,j in cmap.items()]

#Embed the product and observe the final coordinates. The new embedding looks good, but is centered in the wrong spot
AllChem.EmbedMolecule(prod,coordMap=cmap)
print(Chem.MolToMolBlock(prod))
prod

Output Snippets:
>>> prod
---See first image pasted below the output box---
>>> print(Chem.MolToMolBlock(prod))
...
 6  6  0  0  0  0  0  0  0  0999 V2000
  -60.7208  -22.7910  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.0000    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
  -61.5558  -21.6420  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  -59.3708  -22.3520  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  -59.3708  -20.9320  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
  -60.7208  -20.4930  -51.5546 C   0  0  0  0  0  0  0  0  0  0  0  0
...
>>> [(i,j.x,j.y,j.z) for i,j in cmap.items()]
[(0, -60.7208, -22.791, -51.5546),
 (2, -61.5558, -21.642, -51.5546),
 (3, -59.3708, -22.352, -51.5546),
 (5, -60.7208, -20.493, -51.5546)]
>>>print(Chem.MolToMolBlock(prod))
...
 6  6  0  0  0  0  0  0  0  0999 V2000
   -0.8916    0.3801    0.0593 C   0  0  0  0  0  0  0  0  0  0  0  0
   -1.3282   -0.3931   -0.7829 C   0  0  0  0  0  0  0  0  0  0  0  0
   -0.1387   -0.6914   -0.6724 C   0  0  0  0  0  0  0  0  0  0  0  0
   -0.0148    0.9505    0.8585 C   0  0  0  0  0  0  0  0  0  0  0  0
    1.2741    0.3817    0.7552 C   0  0  0  0  0  0  0  0  0  0  0  0
    1.0992   -0.6277   -0.2176 C   0  0  0  0  0  0  0  0  0  0  0  0
...
>>>prod
---See second image pasted below the output box---

Expected behavior
I expect the final coords to have the same relative positions as what is produced by the above example, however I expect the molecule to be centered closer to (-60,-20,-50) than (0,0,0).
Configuration (please complete the following information):

RDKit version:  2022.03.1
OS: Windows 11
Python version (if relevant): 3.7.7
Are you using conda? Yes
If you are using conda, which channel did you install the rdkit from? conda-forge

@paconius I believe this is the expected behavior.
This topic has come up previously on the mailing list and Greg has published a dedicated blog post:
http://rdkit.blogspot.com/2019/01/more-on-constrained-embedding.html
Check in particular the notebook cell [9] and the explanation above it.
For other use cases you might not be interested in the placement of the embedded molecule relative to the original coordMap coordinates, which is why the molecule is not realigned by default.
I would therefore close this bug report; please feel free to reopen if needed.

This topic has come up previously on the mailing list and Greg has published a dedicated blog post:
http://rdkit.blogspot.com/2019/01/more-on-constrained-embedding.html

Thank you @ptosco for posting that link. I think it is certainly relevant. The point about using AlignMol to cleanup after EmbedMolecule seems to be one that could work (although the extra MCS and Alignment are comparatively expensive time-wise).
Even after reading Greg's blog post, I am still of the opinion that EmbedMolecule isn't working correctly. Greg's post seems to claim that due to the forecefield contraints set by EmbedMolecule, it isn't expected that the final embedding will match the provided coordMap exactly. This seems reasonable and expected given the method.
However, this cannot explain how a molecule that should be centered near [-60,-20,-50], ends up being centered around [0,0,0]. To my mind this can only be explained by a deliberate (and unwanted) translation to the origin. I'm not a C++ person, but within the C++ code for EmbedParameters I see references to "Center in Volume" -- which suggests that the code might indeed be centering the molecule and it might be using a false assumption that things should be centered around [0,0,0] -- since default conformer generation in RDKit produces [0,0,0] centered conformers. This assumption about how conformers are centered will not necessarily be true for confomations generated outside of RDKit.
TLDR: I beleive the EmbedMoelcule procedure makes a false assumption that conformers are centered around [0,0,0] and that this is a bug.


Issue#501:Catch Errors in addition to Exceptions to terminate service properly

Any reason for not exposing API to handle java.lang.Errors. With this change, we can expose that API

Thanks!

Any reason for not exposing API to handle java.lang.Errors. With this change, we can expose that API

If an Error occurs there's something seriously wrong with your service that needs to be fixed, I don't think it's healthy to create tools for handling them as if they were normal occurrences.

This has been released as part of 2.8.0 now: https://javalin.io/news/2019/03/26/javalin-2.8.0-released.html


error: nuxt instance unavailable at Module.useAsyncData #8826

Environment
Nuxi 3.0.0-rc.14-27796957.b60f136
Nuxt 3.0.0-rc.14-27796957.b60f136 with Nitro 0.6.1-27791756.086802d
Reproduction
https://github.com/Maxp777/nuxt4
Describe the bug
error: nuxt instance unavailable at Module.useNuxtApp
Additional context
No response
Logs
[log error] Error: nuxt instance unavailable
    at Module.useNuxtApp (/home/user/Downloads/nuxt-error-7-main/node_modules/nuxt/dist/app/nuxt.mjs:162:13)
    at Module.useAsyncData (/home/user/Downloads/nuxt-error-7-main/node_modules/nuxt/dist/app/composables/asyncData.mjs:28:38)
    at Module.useFetch (/home/user/Downloads/nuxt-error-7-main/node_modules/nuxt/dist/app/composables/fetch.mjs:52:43)
    at Proxy.updateList (/home/user/Downloads/nuxt-error-7-main/store/list.store.ts:25:27)
    at Proxy.<anonymous> (file:///home/user/Downloads/nuxt-error-7-main/node_modules/pinia/dist/pinia.mjs:1365:30)
    at update (/home/user/Downloads/nuxt-error-7-main/pages/index.vue:43:23)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async setup (/home/user/Downloads/nuxt-error-7-main/pages/index.vue:55:83) {} setup function
[Vue Router warn]: No match found for location with path "/api/test"

I had the same issue in my component setup function, and using defineNuxtComponent to wrap the export default fixed it


add intuit account selection and password after mfa

tried this pull request and seems to have resolved my issue.
I run my custom mintapi script on a ubuntu srv at home via cron (daily), it looked like it was failing with the following error for the last few days.
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-sign-in-mfa-password-collection-current-password"]"
With this PR the above issue seems to have been resolved.
so +1 for this PR from my perspective.

i'm not sure but it looks like master built failed...

i'm not sure but it looks like master built failed...

Yeah, noticed it's been failing for 5 months
https://travis-ci.org/github/mrooney/mintapi/builds/735886735
Likely why we haven't gotten the last couple of fixes pushed up for pip.

ok got it - i should just get the repository directly from here then (instead of relying on pip install command)
thanks

The pip releases are all done manually, it isn't related to CI. This isn't
on pip yet as I'm on vacation and don't have access to a machine with those
credentials :) It should be up next week! In the meantime please do test
the latest from here.
On Tue, Mar 23, 2021 at 10:26 PM areagu @.***> wrote:

ok got it - i should just get the repository directly from here then
(instead of relying on pip install command)
thanks
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mrooney/mintapi/pull/252#issuecomment-805432460, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA6GRMQODOJO6ZR4IPDVGLTFFEW7ANCNFSM4ZL4373Q
.


zmq.error.Again: Resource temporarily unavailable

Hi,I'm using zeroapi in kubernates and I get an annoying issues:

And the issues happened randomly.
my zmq version is pyzmq-22.3.0.
Could you please help me how to solve my problems?

There is a timeout parameter in the client, the default is 2000ms (2s) https://github.com/Ananto30/zero/blob/main/zero/client.py#L42
If you think your program can take more time (seems like from your error), please set the timeout while creating the client like this -
client = ZeroClient("<HOST>", 8000, default_timeout=10000)

There is a timeout parameter in the client, the default is 2000ms (2s) https://github.com/Ananto30/zero/blob/main/zero/client.py#L42
If you think your program can take more time (seems like from your error), please set the timeout while creating the client like this -
client = ZeroClient("<HOST>", 8000, default_timeout=10000)

Thanks to reply.And I had set the timeout parameter like this:

Is there another possible reason to cause this issues?

Are you facing the issue even after setting the timeout?

Are you facing the issue even after setting the timeout?

Yes.

Add test for timeout and "Resource temporarily unavailable"

Hi,Is there something I can help to do?
By the way,my app started flask server and rpc server at the same time.May this be a reason to cause the issue?

It would be really amazing if you can help on the above issue #12 🙏 I couldn't manage time yet.
Btw how are you running two servers at the same time? Are you using a process manager like supervisord?

Yes.I start rpc server on main thread and flask server on fork thread.

Hi,I tried this script and repeate the issue:
server code:
import time

from zero import ZeroServer

def echo(msg: str) -> str:
    # mock do someing
    time.sleep(5)
    return msg

if __name__ == "__main__":
    app = ZeroServer(port=5559)
    app.register_rpc(echo)
    app.run()

client code:
from zero import ZeroClient
from threading import Thread

def test(index):
    zero_client = ZeroClient("localhost", 5559, 20)
    data = zero_client.call("echo", f"{index}")
    print(data)

if __name__ == "__main__":
    # mock for multi user call,and server worker number is just 16.
    for i in range(16):
        Thread(target=test, args=(i,)).start()

Yes.I start rpc server on main thread and flask server on fork thread.

Then you use the zero client inside the function of flask server?

@ACEGuiPeng any update on this? Or I will close the issue as solved.

Usually happens for timeout issues, otherwise connection issues. So I made two different ZeroExceptions - TimeoutException and ConnectionException in this pr https://github.com/Ananto30/zero/pull/29


PMA51XX/PMA71xx support

Hello,
Is it possible to add support for PMA7105?
Links:

https://www.digikey.com/en/products/detail/rochester-electronics-llc/PMA7105/12127669
https://eu.mouser.com/datasheet/2/196/PMA71xx_PMA51xx_Function_Library_Guide_V1_5-2322507.pdf

I have the key and I can provide with saved dumps.
Thanks!

Hi @mgrybyk
looks very tricky for such a small app.
As I understand it, there are rolling codes, unfortunately this application does not support such codes and will not support in the future


Fix MLE vs MCMC biomass plot (Fig 34)

The MLE was determined to be double for all model runs just before the SRG meeting. This is fixable by re-running the models with nsexes = -1 in the data file but does not explain why the MCMC biomass in the MLE vs. MCMC biomass plot is also double what it should be. The other MCMC biomass plots are correct.

Kelli fixed in #653.


javaScript ES6

Use ES6 Arrow functions instead of ordinary functions.   https://github.com/cosywasswa/To-Do-List/blob/b28ece97bdd3d00a9c693f3cb16a95204255224b/src/script.js#L52-L60.

I would like to work on this issue.


Retrying without Guava

So one thing to consider is with this change, potentially every flow will make api calls to EMR. If we have 100 flows waiting for the same cluster, we could hit the rate limit.
A big improvement would be to have a single thread monitor clusters for all flows

After adding the synchronization to make it thread safe it LGTM

lgtm


Detect special multicause exceptions

This commit fixes an issue where test reports and build scans didn't capture
all the causes of an exception, in case the "multi-cause" exception isn't
a type known of the daemon. By that, we mean a type which is not available
at runtime in the daemon process, but is used in the worker process.
Typically, the org.opentest4j.MultipleFailuresError type used by
JUnit is such an example: the type is used in a test process, but
not loaded in Gradle. In such cases, Gradle builds a placeholder
exception type which collects the root cause. But in case the
exception is actually collecting multiple causes like in this test
class, Gradle lost some information in the process.
Therefore, this commit introduces a heuristic to figure out if an
exception is collecting multiple causes instead of a single one.
The heuristic is kept very simple: one has to find a method which
name is either getCauses (like for Gradle's own default multi
cause exception) or getFailures (like in opentest4j), and it
has to return a collection of failures.
This will not fix all problems but it should capture a good amount
of them.
Fixes #9487

Fixes #?
Context

Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

Thanks, @melix! 👍


Error with OBO via an MSAL.js Access token

Issue
I try to reproduce the sample with a msal.js acquired token (on SPA).
I can get an access token with AcquireSilentToken, then I transmit it to a server method.
This server method try to get a new access token with OBO token query (written in asp.net MVC / C#).
I got this error message :
AADSTS50013: Assertion failed signature validation
This issue is for the sample

    - [ ] 1-1) Sign-in with Azure AD
    - [ ] 1-2) Sign-in with Azure AD B2C
    - [ ] 2-1) Acquire a Token and call Microsoft Graph
    - [ ] 3-1) Protect and call a web API on Azure AD
    - [ ] 3-2) Protect and call a web API on Azure AD B2C
    - [X ] 4-1) Call a web API that calls Microsoft Graph on-behalf-of user
    - [ ] 4-2) Call a web API that calls another web API on-behalf-of user
    - [ ]   5) Deploy to Azure Storage and App Service

This issue is for a

    - [X ] bug report -> please search issues before submitting
    - [ ] question
    - [ ] feature request
    - [ ] documentation issue or request

Minimal steps to reproduce

Any log messages given by the failure

Here is full error
{
"error": "invalid_grant",
"error_description": "AADSTS50013: Assertion failed signature validation. [Reason - Key was found, but use of the key to verify the signature failed., Thumbprint of key used by client: 'xxxxxxxxxxx', Found key 'Start=10/02/2022 18:06:49, End=10/02/2027 18:06:49', Please visit the Azure Portal, Graph Explorer or directly use MS Graph to see configured keys for app Id '00000000-0000-0000-0000-000000000000'. Review the documentation at https://docs.microsoft.com/en-us/graph/deployments to determine the corresponding service endpoint and https://docs.microsoft.com/en-us/graph/api/application-get?view=graph-rest-1.0&tabs=http to build a query request URL, such as 'https://graph.microsoft.com/beta/applications/00000000-0000-0000-0000-000000000000'].\r\nTrace ID: be86f346-02cf-4139-a9e2-036c7a621900\r\nCorrelation ID: 108f1005-07ef-4a0e-aff2-4bf824c9ac1d\r\nTimestamp: 2023-06-15 15:01:38Z",
"error_codes": [
50013
],
"timestamp": "2023-06-15 15:01:38Z",
"trace_id": "be86f346-02cf-4139-a9e2-036c7a621900",
"correlation_id": "108f1005-07ef-4a0e-aff2-4bf824c9ac1d",
"error_uri": "https://login.microsoftonline.com/error?code=50013"
}

Expected/desired behavior

OBO token query OK

Library version

MSAL 2.0

Browser and version

Chrome

Mention any other details that might be useful

Thanks! We'll be in touch soon.

I acquire token via MSAL PublicClientApplication (common tenant).
For OBO token, I post here : https://login.microsoftonline.com/common/oauth2/v2.0/token

@guillaumeKoban hard to tell without seeing your app configuration(s) and a couple of snippets showing your MSAL usage. Feel free to share these.
In the meantime, please refer to the sample: Angular SPA calling an ASP.NET Core web API using the on-behalf-of(OBO)

Got it ! It was a problem linked to my personnal daemon api:/xxxxxxx scope in the msal.js call.
Thanks !


supports minLength/maxLength on string type

Note:
Number.isFinite" is used because "zod v3.19.1" has not yet been applied to "zod-to-openapi".
See below for details.
https://github.com/colinhacks/zod/commit/d78047e9f44596a96d637abb0ce209cd2732d88c

@wiz-kakiuchi I wanted to merge this so I opened a new PR where I resolved the conflicts. I made sure to use your commit so that you still get credit for your work. Thank you again for contributing!


Combine willPopScope and backButtonListener properties

A recently resolved Flutter issue (https://github.com/flutter/flutter/issues/47088) fixes the WillPopScope widget for all navigator types.
Still asking about any differences between using WillPopScope and BackButtonListener here: https://github.com/flutter/flutter/issues/82050
If there is a preferred way to listen to the back-button, I would combine these two into a detectBackButton option that uses the better options. Maybe it should just be left as-is to allow the developer to decide.

Leaving as is to support both modalities


Added Length validator to the String field class

I've added the marshmallow's Length validator to the String class in shared fields.
So, if an empty string is passed for a required string field, it will raise the length validation error.
from bioimageio.spec import rdf

author_schema = rdf.schema.Author()
valid = author_schema.validate({
    'name': '',
    'email'<EMAIL_ADDRESS>})
print(valid)
# {'name': ['Shorter than minimum length 1.']}

#512

Ok, I've made a simple change. Please check if this is what you have in mind.

The tests fail, because the URI fields inherites from String and does not implement len ...
I will either fix this later or the changes for the next release will supersede this entirely.

I've made an edit: for some the raw_nodes I implemented len methods and for some fields that are subclass of the String I removed the Length validator from the validation list (although this might be not the best solution).


⚠ Bofrost.be has degraded performance

In 98e29ef, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1314 ms

Resolved: Bofrost.be performance has improved in ce3d40d.