ZFS tests hang when run by TravisCI occasionally

Issue Description
When TravisCI is running the test suite for zfs, it occasionally hangs until a TravisCI timeout is triggered and it kills the build. Rerunning the exact same build in such a case usually succeeds. Figure out the cause and fix.
Steps to Reproduce (If applicable):

Make a new branch
Make any commit
Push to github
Follow the TravisCI build progress for the push ( https://travis-ci.org/cerana/cerana/builds )
If a build doesn't hang, rerun the build until it hangs.
Rerun the build after a hang until it passes.

Acceptance Criteria (How do we know when this is done?)
A valid code state, one that should pass, always passes in TravisCI whether it's the first or nth rebuild. The zfs tests should not hang.
Environment (physical, VM, cloud provider, etc.):
TravisCI Ubuntu Trusty VM
spl <IP_ADDRESS>
zfs github.com/ClusterHQ/zfs 2c9b2d6bf312d0ffb4a14c0570fcb8150196
See ./Makefile for the test building and running via docker container
Other Relevant Info:
Hangs at
BUILD zfs/zfs.test
RUN   zfs/zfs.test

Should be
BUILD zfs/zfs.test
RUN   zfs/zfs.test
+++ zfs/zfs.test +++
=== RUN   TestSuiteInternal
=== RUN   TestClone
... (more test cases) ...
PASS

It's not a problem with the tests themselves. When setting a timeout on the tests it still hangs. When running docker exec with timeout it still hangs. Trying to get more information out of it by running the tests in the background, sleeping in a loop until a timeout or until it's finished, and if they're still running, print out process info and dmesg.

Got some logging out of zfs while hanging.
https://s3.amazonaws.com/archive.travis-ci.org/jobs/122349712/log.txt


Pydantic v2

More Contributions are welcome

Hey, just want to add a few things:

In the next release (and currently on main branch of pydantic), there will be pydantic.v1 which will have everything from pydantic v1 without modifications (though may be slower as it will not be cython-compiled). This may help you transition more incrementally
One of the things I changed in my original PR was to get rid of the custom __init__ in favor of root validators and some other weird things. But we went back on that change and have since added support for custom __init__, so you might be able to undo those changes and keep the custom __init__ unmodified. I haven't confirmed that.

We are nearing the feature-freeze "beta" release, hopefully happening within the next week. Once that happens I'll be happy to take another pass.

Yes I agree with your points too David! When I saw your branch changes I realised that the way I was attempting to refactor was probably not the ideal future compatibility like you added.
Am happy to do as you suggest in terms of changes if I can help (as I do have an interest of getting this working too) although if the new release is soon then also happy to wait and help how I can later if needed!

I was also thinking after the refactor, that there were quite a few classes that had a lot of repeated pydantic code. For the sake of maintenance, future integration, and debugging one thing we could do is have a set of generic Validator classes that implement a standard config, and common classes inherit from them. There are also some validators that may need proper implementation I think with usage of some plugins as input parameters usage from what I remember being involved too.

Hi David and Joaqin,
I have done anotehr clean go at the porting using the migration protocol described in https://github.com/pydantic/pydantic/issues/5771 which I think seems to work.
It mostly involved changing the imports from pydantic to pydantic.v1 as David suggested. I am doing it so I can get my project fully integrated. It works from the latest github pydantic v2 version and I reckon this has already been deployed to PyPi, but I did un the migration_v1.sh script provided in my environment and I don't know if that is already automated on PyPi install.
In any case, in case it is useful, I have made a pull request here https://github.com/gdsfactory/gdsfactory/pull/1718. Pytest seems to complete and not dissimilar from the current main pytest.


REPL fails in git bash in Windows #406

This seems to fix #406

that seems like a good idea - thanks

:shipit:


I'm sorry I've triggered an error in mxnet source code, how can I debug it? It seems like a check failure on custom operators, how can I find more details?

So far I'm working in linux dockers, the mxnet was built from source code
When I was running RoITransformer project with fpn training, the following error emerged.

File "experiments/fpn/fpn_end2end_train_test_RoITransformer.py", line 21, in <            module>
train_end2end_rotbox_RoITransformer.main()
File "experiments/fpn/../../fpn/train_end2end_rotbox_RoITransformer.py", line             188, in main
config.TRAIN.begin_epoch, config.TRAIN.end_epoch, config.TRAIN.lr, config.TR            AIN.lr_step)
File "experiments/fpn/../../fpn/train_end2end_rotbox_RoITransformer.py", line             181, in train_net
arg_params=arg_params, aux_params=aux_params, begin_epoch=begin_epoch, num_e            poch=end_epoch)
File "experiments/fpn/../../fpn/core/module.py", line 989, in fit
self.update_metric(eval_metric, data_batch.label)
File "experiments/fpn/../../fpn/core/module.py", line 1081, in update_metric
self._curr_module.update_metric(eval_metric, labels)
File "experiments/fpn/../../fpn/core/module.py", line 672, in update_metric
self._exec_group.update_metric(eval_metric, labels)
File "experiments/fpn/../../fpn/core/DataParallelExecutorGroup.py", line 481,             in update_metric
eval_metric.update(labels, texec.outputs)
File "/usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/metri            c.py", line 364, in update
metric.update(labels, preds)
File "experiments/fpn/../../fpn/core/metric.py", line 53, in update
pred_label = mx.ndarray.argmax_channel(pred).asnumpy().astype('int32')
File "/usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/ndarr            ay/ndarray.py", line 2506, in asnumpy
ctypes.c_size_t(data.size)))
File "/usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/base.            py", line 254, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [13:42:48] src/operator/custom/custom.cc:417: Check faile            d: reinterpret_cast(params.info->callbacks[kCustomOpBackward])(             ptrs.size(), const_cast<void**>(ptrs.data()), const_cast<int*>(tags.data()), rei            nterpret_cast<const int*>(req.data()), static_cast(ctx.is_train), params.in            fo->contexts[kCustomOpBackward]):
Stack trace:
[bt] (0) /usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/li            bmxnet.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x43) [0x7fd12dfa0133]
[bt] (1) /usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/li            bmxnet.so(+0x16d265f) [0x7fd12e65365f]
[bt] (2) /usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/li            bmxnet.so(+0x16db4f9) [0x7fd12e65c4f9]
[bt] (3) /usr/local/lib/python2.7/site-packages/mxnet-1.6.0-py2.7.egg/mxnet/li            bmxnet.so(std::thread::_State_impl<std::thread::_Invoker<std::tuple<mxnet::op::c            ustom::CustomOperator::SetNumThreads(int)::{lambda()#1}> > >::_M_run()+0xde) [0x            7fd12e66305e]
[bt] (4) /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xbd66f) [0x7fd174e7866f]
[bt] (5) /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7fd17b9786db]
[bt] (6) /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fd17aefc88f]

I've viewed the source code mentioned above, it looks like this:
  CustomOperator::Get()->Push(     [=]() {       CHECK(reinterpret_cast<CustomOpFBFunc>(params.info->callbacks[kCustomOpBackward])(         ptrs.size(), const_cast<void**>(ptrs.data()), const_cast<int*>(tags.data()),         reinterpret_cast<const int*>(req.data()), static_cast<int>(ctx.is_train),         params.info->contexts[kCustomOpBackward]));     }, ctx, false, ctx.is_train, cpys, tags, output_tags, outputs, "_backward_" + params.op_type);
I cannot figure out what does this mean or which custom operator caused this.
Can any one give an advice on how to debug this???

This may be related to https://github.com/apache/incubator-mxnet/issues/16365 . As a workaround. Can you please remove declare_backward_dependency for the custom op that is getting called and check : https://github.com/dingjiansw101/RoITransformer_DOTA/blob/master/fpn/operator_py/

This may be related to #16365 . As a workaround. Can you please remove declare_backward_dependency for the custom op that is getting called and check : https://github.com/dingjiansw101/RoITransformer_DOTA/blob/master/fpn/operator_py/

Hey, I'm on the way!
I'll post the result minutes after!

Can you tell how this happened?

It may be an issue with how storage type is assigned after invoking declare_backward_dependency callback : https://github.com/apache/incubator-mxnet/blob/master/src/operator/custom/custom.cc#L474 . I haven't had the time recently to dig deeper into this.

Can you tell how this happened?

It may be an issue with how storage type is assigned after invoking declare_backward_dependency callback : https://github.com/apache/incubator-mxnet/blob/master/src/operator/custom/custom.cc#L474 . I haven't had the time recently to dig deeper into this.

Ok, I'll quote all the declarations, it seems there is a lot of them...


Set javafmtOnCompile := false by default

It seems like this was already decided in https://github.com/sbt/sbt-java-formatter/pull/70#issuecomment-593421099 but was deferred to enable a smooth transition.

I agree, it is time to finally do this switch. Please update even the instructions in the Readme.

In aa2f583 I made an on-compile-true and on-compile-false test from the old on-compile.


Are pretrained models available?

Best

Hi, we have released the pre-trained Timer on HuggingFace. A notebook example is also provided here.


Can't import MapView.

Hi. First I had this problem: http://stackoverflow.com/questions/38095524/cannot-evaluate-module-react-native-maps-configuration-with-name-default-n
and tried fix it by follow steps in that topic.
Finally I fixed that problem, build was successful but new problem appeared.
I try import MapView but system doesn't recognize this component.

Can you tell me what is wrong?
Thank you
My code:
Geo.js
`
import React, { Component } from 'react';
import {
AppRegistry,
StyleSheet,
Text,
Button,
View
} from 'react-native';
import MapView from 'react-native-maps'
export default class Geo extends Component {
constructor() {
super();
this.state = {
position:'none'
}
}
render() {
    return (
        <View>
            <MapView/>
            <Text>{this.state.position}</Text>
        </View>
    )
}

}
AppRegistry.registerComponent('Geo', () => Geo);`
Build.gradle
`def enableProguardInReleaseBuilds = false
android {
compileSdkVersion 23
buildToolsVersion "23.0.1"
defaultConfig {
    applicationId "com.kurs"
    minSdkVersion 16
    targetSdkVersion 22
    versionCode 1
    versionName "1.0"
    ndk {
        abiFilters "armeabi-v7a", "x86"
    }
}
splits {
    abi {
        reset()
        enable enableSeparateBuildPerCPUArchitecture
        universalApk false  // If true, also generate a universal APK
        include "armeabi-v7a", "x86"
    }
}
buildTypes {
    release {
        minifyEnabled enableProguardInReleaseBuilds
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}
// applicationVariants are e.g. debug, release
applicationVariants.all { variant ->
    variant.outputs.each { output ->
        // For each separate APK per architecture, set a unique version code as described here:
        // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
        def versionCodes = ["armeabi-v7a":1, "x86":2]
        def abi = output.getFilter(OutputFile.ABI)
        if (abi != null) {  // null for the universal-debug, universal-release variants
            output.versionCodeOverride =
                    versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
        }
    }
}

}
dependencies {
compile project(':react-native-vector-icons')
compile project(':react-native-push-notification')
compile 'com.airbnb.android:react-native-maps:0.6.0'
compile fileTree(dir: "libs", include: ["*.jar"])
compile "com.android.support:appcompat-v7:23.0.1"
compile "com.facebook.react:react-native:+"  // From node_modules
}
// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
from configurations.compile
into 'libs'
}
settings.gradlerootProject.name = 'kurs'
include ':react-native-vector-icons'
project(':react-native-vector-icons').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-vector-icons/android')
include ':react-native-push-notification'
project(':react-native-push-notification').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-push-notification/android')
include ':react-native-maps'
project(':react-native-maps').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-maps/android')
include ':app'
`
MainActivity.java
`package com.kurs;
import com.facebook.react.ReactActivity;
import com.facebook.react.ReactPackage;
import com.facebook.react.shell.MainReactPackage;
import java.util.Arrays;
import java.util.List;
import com.airbnb.android.react.maps.MapsPackage; //<- this line is important
public class MainActivity extends ReactActivity {
/**
 * Returns the name of the main component registered from JavaScript.
 * This is used to schedule rendering of the component.
 */
@Override
protected String getMainComponentName() {
    return "kurs";
}

  protected boolean getUseDeveloperSupport() {
    return BuildConfig.DEBUG;
  }

  protected List<ReactPackage> getPackages() {
    return Arrays.<ReactPackage>asList(
    new MainReactPackage(),
    new MapsPackage(this) //here you must be write the param this
    );
  }

}
`
MainAPlication.java
`package com.kurs;
import android.app.Application;
import com.facebook.react.ReactApplication;
import com.oblador.vectoricons.VectorIconsPackage;
import com.dieam.reactnativepushnotification.ReactNativePushNotificationPackage;
import com.facebook.react.ReactNativeHost;
import com.facebook.react.ReactPackage;
import com.facebook.react.shell.MainReactPackage;
import com.facebook.soloader.SoLoader;
import java.util.Arrays;
import java.util.List;
public class MainApplication extends Application implements ReactApplication {
private final ReactNativeHost mReactNativeHost = new ReactNativeHost(this) {
@Override
public boolean getUseDeveloperSupport() {
return BuildConfig.DEBUG;
}
@Override
protected List<ReactPackage> getPackages() {
  return Arrays.<ReactPackage>asList(
      new MainReactPackage(),
        new VectorIconsPackage(),
        new ReactNativePushNotificationPackage()
  );
}

};
@Override
public ReactNativeHost getReactNativeHost() {
return mReactNativeHost;
}
@Override
public void onCreate() {
super.onCreate();
SoLoader.init(this, /* native exopackage */ false);
}
}
`

have you open your project in android studio so the gradle load the module?

I don't use android studio so don't know what you ask.

in some cases (like mine) some library wont load to android when use 'react-native run-android'. And the lib  will be loaded by gradle when you open your project in android studio. Your case is the library / module not loaded in your project. So the solution is, delete the library and re-install it using npm or try open your project in android studio.

Finally was working when I install maps on fresh clean RN project. But in my proper project maps still not working.
I have got enough. I should write a code not fighting with issues. Why react native not support own maps any more?
And is there anyone who has no problems with this extension?

try re-install the lib

remove the library
npm install
@zuber303

@felipecsl I think this should be closed since now .babelrc is added to .npmignore


Enable and fix a couple junit vintage tests

Update TokenEncodingTest.testRefreshTokenEncoding considering extra valid minute added by encoder
Add surefire arg to run test using UTF-8 as default charset

LGTM


Change in  io_handler::get_output_directory to improve output directories

This changes allows to separate the directories:

with results from a simtool
temporary / intermediate files like model files, ray-tracing files, etc.

This is especially important for using simtools with the output_path and the use_plain_output_path option. In this case we are writing:

result to output_path
e.g. model files to output_path/model.
This should allow the CWL workflows to find the output files.

This pull request required a lot of repetitive changes (you know I like sed). I suggest to first look at simtools/io_handler.py and maybe start with tests/unit_tests/test_io_handler.py::test_get_output_directory. The unit test should cover all the logically allowed cases.
Note that some files also experienced a lot of re-formatting due to possible first-time application of black in the pre-commit stage.
(and I know that the name of the branch is not good).

Hi @GernotMaier. Thanks for these changes and for spotting the missing pre-commit from my side. I left some comments to improve the clarity of the code/doc.
I did not see how these changes are going to help us distinguish the output of the application/results from the all the other temporary files (as we discussed). It seems to me that all the files (and outputs) will land inside Path(f"{args_dict['output_path']}/output/model") (I did not have time yet to test the applications to confirm this). I think by addressing/responding to my comments, this will become clearer for me. Thank you. (For the record this review took me 1h30min.)

@VictorBarbosaMartins - thanks a lot the review!
I am trying to understand your comment above. Maybe it would have been better not to review and ask immediately  for clarification. This has been extensively tested and it provides a separation of the output files as outlined in the introduction to the pull request.
To make it clearer (as discussed also on Tuesday in our meeting):

The situation before this pull request is that we have a inconsistent path selection for output among the tools: this is hard to handle, as we need to know in which directories are the output files.

e.g., running  simtools-derive-mirror-rnda with --output_path ./output and --use_plain_output_path gives:

derived model parameters are on ./output/results
downloaded model files from DB are in ./output/
temporary files like photons from ray-tracing are in ./output

With this pull request we always have

derive model parameter in ./output
downloaded model files from DB are in ./output/model/
temporary files like photons from ray-tracing are in ./output/raytracing

This has been tested for several tools and is also consistently tested in the unit test.
I have put a lot of care in making sure that the default behavior of the tools is not changing. Meaning without --output_path and --use_plain_output_path it is the simtools-output/..date.../...tool..name etc output. We could discuss if this is needed, but this is not the goal of this pull request.
For using def get_output_directory(self, label=None, sub_dir=None, dir_type="simtools"):

nothing changed for the general case (giving label and sub_dir only
for testing, the boolean test is replaced by the feature parameter "test"
new: to force the output consistent with the schema outlined in 2. above: use the directory type "simtools-output" when getting/setting the directory of a simtools.

I think I've addressed the comments with the last commit.
Let me know about remaining issues.

Hi @GernotMaier , thanks a lot for the carefully reading and answering my comments. It is clearer to me now, and I understand that many of the comments are not directly related to the PR. I usually get a lot of those in my PRs as well, I thought it was fine. But I agree with you that it is probably better to focus on the PR and be more effective/faster.
I just have two remaining points, both with the dir_type parameter (see in the comments above), I am fine with the rest. Do you want to add something else @orelgueta ?
(1h02 min more for the re-review here)

I still think that
https://github.com/gammasim/simtools/blob/ffdc21416fba1602e030ed5123fe82eba5b14bea/simtools/io_handler.py#L92
is prone to errors unless you enforce dir_type to be exactly one of those three options 'simtools', 'test', 'simtools-result'. As a developer, if I just see the documentation with "e.g.," then I think I can provide anything.
A real world example would be corsika-data or simtel-data, for latter which I will get an output directory simtel-d.
So I see two options for this specific PR

You enforce only those three options for now and in the future we deal with other options when they come (probably me cause I will need to implement the corsika/simtel-data case).
You use regex to remove -result at the end of dir type and add a mention of that in the doscrting. The actual command would be re.sub(r"\-result$", "", dir_type) (I would vote for this option).

Good that we agree in this issue @orelgueta . I think we have to understand better the reason behind this line. Why do we want in the first place to cut out '-results' whenever dir_type is passed as 'simtools-results' (and allow all the remaining possibilities). I dont mind the regex but I still prefer the solution I mentioned before, i.e., instead of passing simtools-results in the argument, use the use_plain_output_path attribute to have the same effect.

As mentioned several time: this is to ensure that the tools behave exactly the same way as before if you don't give output_path and use_plain_output_path as options. I think this is a good motivation.
We can discuss (beyond this pull request) if we should give up the old-style directory naming completely.  This pull request was about adding functionality, not to remove or change existing beavior.

Tests are successful now, and I think I've addressed your comments (or we discussed them sufficiently).
Let me know if there is anything remaining to fix.

I didn't actually do a review in the end except that specific point so I let @VictorBarbosaMartins approve if he agrees.

Added one more unit test for dir_type=None. This should be the last commit.


[do not merge] Debug Adapter Protocol Support for variablesReference in OutputEvent

This issue describes Visual Studio Code’s output event variables reference behavior: https://github.com/microsoft/vscode/issues/83674


Add support for Sheng Siong

POST to https://www.allforyou.sg/Common/pinCodeSearch
with
{ "code": 438610, "pinStatus": 1 }

Can I take this? :) Sounds like a fun project

@ikanyu take it. :)

@ikanyu make sure to test the endpoint...sometimes, it don't work so we'll need to do a bit of digging to find out what works :D

@vincentpaca Can elaborate further on why sometimes, it don't work? What did you encounter?


fix(pyxis): dont init array with empty values

VULN4OS-136
Secure Coding Practices Checklist GitHub Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[x] Input Validation
[x] Output Encoding
[x] Authentication and Password Management
[x] Session Management
[x] Access Control
[x] Cryptographic Practices
[x] Error Handling and Logging
[x] Data Protection
[x] Communication Security
[x] System Configuration
[x] Database Security
[x] File Management
[x] Memory Management
[x] General Coding Practices

Codecov Report
Base: 37.31% // Head: 37.31% // No change to project coverage :thumbsup:

Coverage data is based on head (89420a9) compared to base (1a81505).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #110   +/-   ##
=======================================
  Coverage   37.31%   37.31%
=======================================
  Files          16       16
  Lines         796      796
=======================================
  Hits          297      297
  Misses        474      474
  Partials       25       25

Flag
Coverage Δ

unittests
37.31% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add inline code block extension

extend code block, support toggle without a selection

For more details, open the Copilot Workspace session.

Not necessary to rewrite a code plugin


feat: add native RtL css support

Why
It was decided the I18nManager.forceRtL(true) does nothing on Web, hence rendering RtL handling between native/non-native very difficult using properties like margin-left/margin-right (mobile flips whereas web doesn't).
With this change, we can write RtL sensitive properties that will work across native (i.e. Mobile) and non-native (i.e. Web) platforms and allow for the components be re-used with the same strategy (more on that below) since RN does not understand marginInlineStart for example.
<HeadingContainer style={{ marginInlineStart: 10, start: 5}}>

Proposition
This PR would essentially allows us to write non-native css properties like so:
const HeadingContainer = styled.View`
  margin-inline-start: 20;
  inset-inline-start: 5 ;
`;

which would in turn be converted to accepted native css and applied like so:
<HeadingContainer style={{ marginStart: 10, start: 5}}>

It is worth nothing that this works without any code change but is in no way an acceptable suggestion to mix native with non-native css:
const HeadingContainer = styled.View`
  margin-start: 20;
  start: 5 ;
`;

Strategy

For Web, it is then possible to set RtL on RtL sensitive css by applying dir="rtl" on a highest top level RN parent in the tree which will force all children to take on rtl.
On mobile, continue using  I18nManager.forceRtL(true)

Notes
Minimal code change/tests since the root issue is still be discussed

The spec for this isn't yet a candidate recommendation - https://www.w3.org/TR/css-logical-1/
I'm fine to merge this if we add a note to the readme saying it's not considered stable, and behaviour may change without a major version bump

The spec for this isn't yet a candidate recommendation - https://www.w3.org/TR/css-logical-1/
I'm fine to merge this if we add a note to the readme saying it's not considered stable, and behaviour may change without a major version bump

Closing this one for now as never got around to properly test it across devices our end. We can always revisit this later should it find more interest


Client: Connect to websocket and create chat box

We need a chat-box for sending and receiving information with our backend.

Completed in https://github.com/Christopher-Stolfa/multi-user-dungeon/pull/4


Add Application Packages via ARM Template for Azure Marketplace

Feature Request Description
We're trying to use ARM templates to dynamically create Batch accounts, Pools, and Applications attached to pools; however, it doesn't look like there's a way to deploy application packages (stored in Blob storage) to the Account via an ARM template. This would be incredibly helpful
Describe Preferred Solution
Be able to create a new Account, Pool, and Application Packages (also attached to pools) via an ARM template.
Describe Alternatives Considered
N/A - for using Batch Accounts with Azure Marketplace, there aren't alternatives...Marketplace ONLY supports ARM templates.
Additional Context
N/A

Also - being able to create Job Schedules via ARM would be incredibly helpful as well

@matthchr is this on your roadmap by any chance? :)

Any update on this feature.  I need this too.  Looks like it is not possible.


VWMess is not called

On desktop switch function VWMess(wParam, lParam, msg, hwnd) is not called. As a result of that after desktop switch window is not focused.

Works for me. Are you running on OS build 17763.348? And using this DLL: https://github.com/Ciantic/VirtualDesktopAccessor/raw/master/x64/Release/VirtualDesktopAccessor.dll
I know that Windows is having a patch tuesday, and I think I haven't yet downloaded that.


Reorganize into subdirectories

Close #101
cc @Michael-F-Bryan

Going to merge because this has a high chance of bitrot


Merge release 3.3 to develop.

lgtm

Closing this PR. We can simply add the new accesslog file to develop.

@sagarkapare Could you add that file then, if its needed?
Thanks.

@anwar6953 I don't see usage of that file in the project.
@sreevatsanraman Can you please let us know whether we need to add accesslog.txt file in develop which was added as a part of https://github.com/caskdata/cdap-apps/commit/3fd0e54d7e401337f1e2774e3d4ddd8f72fa3983 in release 3.3 compat branch?


Support AzDevOps Feed Management

Is your feature request related to a problem? Please describe.
Attempting to manage Nuget feeds.
Describe the solution you'd like
Add base commans:
feed             : Manage Azure artifact feeds.

Describe alternatives you've considered
Using raw REST APIs described here.
https://docs.microsoft.com/en-us/rest/api/azure/devops/artifacts/feed  management?view=azure-devops-rest-6.0
Additional context
CLI support would be helpful in fixing security vulnerability: critical Nuget package substitution attack.

Opened issue under CLI extensions: https://github.com/Azure/azure-devops-cli-extension/issues/1089

Opened issue under CLI extensions: https://github.com/Azure/azure-devops-cli-extension/issues/1089


Finish setting up OTA updates for firmware. ($200)

Is your feature request related to a problem? Please describe.
From the app I should be able to update to new firmware versions.
Describe the solution you'd like
There should be a device settings in the app, that determines current firmware vs somewhere hosted maybe github, and tells if there's a new firmware version available.
Then should download that zip file, and use dfu.dart (which already works) to do the firmware restart on the device for the user.
Additional context
dfu.dart was commented, because the dependency was causing building issues for iOS and android (this should be fixed too)

To manage and pull versions, we could certainly use the releases API, but that would require us to maintain releases properly.
https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#get-the-latest-release
The other option could be to use something like Firebase (since we already have it integrated)

@mdmohsin7 does it still work ?

Yes it does @beastoin with dk1. If the dk2 firmware supports OTA updates, then I can change some changes to the endpoint to support dk2 releases as well


chore: release v2.7.0

Upgrade to OpenTelemetry 1.21.0 / 0.48.0. #874
GraphQL instrumentation: spans for resolvers are no longer generated. This brings in significant performance improvements for queries hitting lots of resolvers. SPLUNK_GRAPHQL_RESOLVE_SPANS_ENABLED=true environment variable can be used to unignore resolve spans.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ce51170) 86.22% compared to head (ebe24ff) 86.22%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #875   +/-   ##
=======================================
  Coverage   86.22%   86.22%
=======================================
  Files          19       19
  Lines         668      668
  Branches      153      153
=======================================
  Hits          576      576
  Misses         92       92

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


update ScrollToTop component style

pls make sure to request a reviewer to speed up the process, @zzq0826 - here maybe @Holybasil ?


R3nzSkin Status not activating

It doesnt work anymore

Read 14.9 patch notes and also it was also this when Vanguard was only in PBE


Fix navigation not closing on large screens

Fixes https://github.com/mattermost/docs/issues/7590

Summary

Ticket Link

Hello @minkyngkm,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

@hanzei - Added you as a reviewer via @core-reviewers. Please reassign as needed.


Can't connect dialogflow with mysql

I've been trying too many days to connect mysql database with dialogflow and
I have not idea how make my code, please help me

Look at this glitch project and you'll have a great start point
https://glitch.com/edit/#!/free-mysql?path=server.js:29:0

and this code can be paste in te index.js of the inline editor?


[Constraint solver] Check conditional requirements for type erasure.

Rather than wantonly dropping the conditional requirements when checking
for type erasure, add them in the same way we do for (e.g.) conformance
checking for generics. Fixes rdar://problem/35480860.

@swift-ci please test and merge


Added Judging timer and popup

The judging timer looks like this:

and when the timer hits 4 minutes, the timer pauses and triggers a popup reminding judges about the time:

The timer resets when a project score is submitted or when it is skipped so that every new project that the judges see will start at 0 minutes and 0 seconds.

Great work Nic!


Add a sequence

Can you add the arithmetic sequence?

Yeah sure, I can give it a try. :)

@fandongo1 Done! Thanks for the idea!


Native Editor - Cell command state (blue) - Support output toolbar

Current understanding is that the toolbar needs to appear under EACH output that can occur from one input cell. This complicates the UI substantially, which is why it is more costly than the toolbar on the input.
§ Move output command toolbar to bottom of each output
□ Will require hacks like plot viewer
□ 3 days

Moving back to triage, I thought we agreed with the designers to not have this.

Yes we did.


Create Useful Labels for issues in this org

Katy has a cool script for adding issue labels that are useful.

closed by @sskutnik !


Enable reusing the same subdirectory for model resumes only if it is resuming the latest epoch file

This adds logic to reuse the same training session ID on resuming training, under the precondition that the model is resuming the newest epoch weight file. This is to avoid weird problems with Tensorboard logs when resuming from an earlier epoch.
This also refactors all .format() in hourglass.py to use f formatting.

I've just tested the logic locally to make sure everything works. :)


SteamVR update broke it?

SteamVR updated and I'm pretty sure it broke the whole thing.  Whenever I run the exe and open SteamVR it fails, but it opens fine without me running the exe.

Move Oculus and Oculus_legacy out of steamvr folder. It launches after that.
Workaround.

Move Oculus and Oculus_legacy out of steamvr folder. It launches after that.
Its under "Drivers" in steamvr folder
Workaround.

Any other work arounds? It does not work for me.

You'll see this should be fixed now with the latest release :)

You'll see this should be fixed now with the latest release :)

its still broken for me


Content: CSS V2

Discussion and planning around CSS V2 badges

## CSS3/Current
*W3 Complete to Testing* https://www.w3.org/Style/CSS/current-work
## After CSS3
*W3 Refining to Exploring* https://www.w3.org/Style/CSS/current-work
	- https://www.smashingmagazine.com/2013/01/sneak-peek-future-selectors-level-4/
	- http://css4-selectors.com/selectors/
	- http://css4.rocks/selectors-level-4/```

for flexbox: http://flexboxfroggy.com/

I'm about to work on this, since I just finished the JS category content.

https://medium.com/statuscode/the-14-most-popular-css-links-of-2016-so-far-96a6e64378d5#.o8vrky6tf

BTW, i have this nearly complete.

This is complete, and has been merged to master as an active badge


Error using LandmarkBasedTransformInitializer with BSpline transform

Hello,
I am aware of sitk.BSplineTransformInitializer(image1, transformDomainMeshSize, order) for performing BSpline registrations, but I am trying to initialize the registration using LandmarkBasedTransformInitializer.
Following is how I attempt to obtain a landmark-based transform for a 'rigid', 'affine' or 'bspline' transform:
def GetLandmarkTx(FixIm, MovIm, FixPts, MovPts,
                  Transform='rigid', NumControlPts=8):
    import SimpleITK as sitk

    if Transform == 'rigid':
        SitkTransform = sitk.VersorRigid3DTransform()
    elif Transform == 'affine':
        SitkTransform = sitk.AffineTransform(FixIm.GetDimension())
    elif Transform == 'bspline':
        SitkTransform = sitk.BSplineTransform(FixIm.GetDimension())
    else:
        msg = "Transform must be either 'rigid', 'affine' or 'bspline'."
        raise Exception(msg)

    if Transform == 'bspline':
        LandmarkTx =sitk.LandmarkBasedTransformInitializer(transform=SitkTransform,
                                                           fixedLandmarks=FixPts,
                                                           movingLandmarks=MovPts,
                                                           referenceImage=FixIm,
                                                           numberOfControlPoints=NumControlPts)
    else:
        LandmarkTx = sitk.LandmarkBasedTransformInitializer(transform=SitkTransform,
                                                           fixedLandmarks=FixPts,
                                                           movingLandmarks=MovPts,
                                                           referenceImage=FixIm)

    return LandmarkTx

The above works fine for 'rigid' and 'affine', but the following error occurs for 'bspline':

Exception thrown in SimpleITK LandmarkBasedTransformInitializer: C:...\ITK\Modules\Core\Common\src\itkMultiThreader.cxx:395:
itk::ERROR: MultiThreader(0000025C4E20D020): Exception occurred during SingleMethodExecute

Any advice would be much appreciated.

Question addressed on ITK discourse: https://discourse.itk.org/t/using-landmarkbasedtransforminitializer-for-bspline-registrations/4096


(PUP-5262) Wait for services to finish state transitions in Solaris

When stopping, starting, and restarting services, SMF tracks state
transitions through through two states: state for the
current state, and nstate for the next state. Because of this,
Puppet would occasionally encounter race conditions when attempting
to act on a service that was in the middle of a state transition.
This is due to the asychronous nature of service management in Solaris,
and the fact that state transitions are not atomic.
This commit adds a 60 second timeout when stopping or starting services
to ensure that the state transition has completed before continuing
operatings.

Retargeted version of https://github.com/puppetlabs/puppet/pull/4412

/cc @branan

So despite svcadm having a dedicated option to imply a synchronous action, it still returns before the service enters the desired state?  I'm just ಠ_ಠ

@peterhuene I actually just found https://blogs.oracle.com/SolarisSMF/entry/synchronous_actions which says synchronous actions for svcadm became available in Solaris 11.2. However, all of our VMs are 10.10 or 11.1, so we get the following:
Stopping:
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
disabled       -
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
offline        online
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
offline        online
...
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
online         -

Starting:

...
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
offline        online
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
online         -

Restarting:

root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
online         -
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
offline        online
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
offline        online
root@wqgnn154xvgygoi:~# svcs -H -o state,nstate puppet
online         -

@peterhuene, Branan is taking this PR over.

Ah, didn't realize they shipped a service administration tool that didn't initially have a way of waiting on the action.  That's double ಠ_ಠ

@peterhuene Updated to use the splat syntax

:+1: will merge after CI is green.

Appveyor seems to be hanging again... :(


Support proxying with TLS client certificates in Nginx

@grkvlt Can you add a test as well please - see https://github.com/apache/brooklyn-library/blob/67a4dda36fcc0eaa628a5a887bdb07f953e06610/software/webapp/src/test/java/org/apache/brooklyn/entity/proxy/nginx/NginxHttpsSslIntegrationTest.java for existing nginx tests that are similar.

@aledsage not sure how easy the test will be, since will need to configure tomcat (?) for client certificate auth, as well as generating a client certificate for the server that is running the test, so that it validates. I have tested this many times as a proxy to a Docker Swarm that uses client certificate authentication, but not sure how to replicate that in a test.

LGTM, but I agree with Aled that testing would be beneficial. Andrew did you investigate further how to do this?

jenkins build failure is unrelated - @grkvlt is kicking it off again:
Parsing POMs
Downloaded artifact http://repository.apache.org/snapshots/org/apache/brooklyn/brooklyn-parent/0.10.0-SNAPSHOT/maven-metadata.xml
Downloaded artifact http://repository.apache.org/snapshots/org/apache/brooklyn/brooklyn-parent/0.10.0-SNAPSHOT/brooklyn-parent-0.10.0-20160719.223024-76.pom
Downloaded artifact http://repository.apache.org/snapshots/org/apache/brooklyn/brooklyn-server/0.10.0-SNAPSHOT/maven-metadata.xml
Downloaded artifact http://repository.apache.org/snapshots/org/apache/brooklyn/brooklyn-server/0.10.0-SNAPSHOT/brooklyn-server-0.10.0-20160719.223502-76.pom
Failed to transfer Could not find metadata org.apache.brooklyn:brooklyn-parent:0.10.0-SNAPSHOT/maven-metadata.xml in clojars.org (http://clojars.org/repo)
Failed to transfer Could not find metadata org.apache.brooklyn:brooklyn-server:0.10.0-SNAPSHOT/maven-metadata.xml in clojars.org (http://clojars.org/repo)
Failed to transfer Could not find metadata org.apache.brooklyn:brooklyn-parent:0.10.0-SNAPSHOT/maven-metadata.xml in oracle (http://download.oracle.com/maven)
Failed to transfer Could not find metadata org.apache.brooklyn:brooklyn-server:0.10.0-SNAPSHOT/maven-metadata.xml in oracle (http://download.oracle.com/maven)
Modules changed, recalculating dependency graph
Build timed out (after 40 minutes). Marking the build as aborted.
Build was aborted
Putting comment on the pull request
Finished: ABORTED

@grkvlt I agree this is too hard to write a test here for! We'd need to generate a certificate for the specific IP address of the server that the test is running against, then have some software component (e.g. etcd or swarm-node) that requies tls, and then configure our nginx to talk to that.
This is being tested in a downstream project. The pragmatic thing to do is to merge this, and rely on the downstream project to regression test it for us. It's a fairly niche use-case anyway.
Merging now that jenkins has completed.


First pass of basic operators finished

I have to update my tests, but this seems to be a good first pass on these operators.
Just looking for basic feedback on the impl here

Pull Request Test Coverage Report for Build 265

200 of 257 (77.82%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.546%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/datasources/csv.rs
0
12
0.0%

src/types.rs
0
17
0.0%

src/exec.rs
136
164
82.93%

Totals

Change from base Build 263:
0.0%

Covered Lines:
3511

Relevant Lines:
4359

💛  - Coveralls


I cant do the hand presentation event tho i turned it on

Thank you for feedback,
I cannot point out the cause, but the issue might be fixed in latest version so please try v1.2.0.
Also note that, VMagicMirror supports windows 10 only. The OS looks Windoes 8 (or 8.1) and this might be the cause. Because VMagicMirror uses many Windows API and other native APIs based on latest Windows OS, so older OS can cause some issues.

I am closing this issue, because there are no additional action.


include whitelist-good-actors in the default http collection

https://hub.crowdsec.net/author/crowdsecurity/collections/whitelist-good-actors should be included in the default http collection

Agreed. Today I made it an optional, false by default, option in the ansible role  https://github.com/buanzo/crowdsec-plus-console


Bring back HTML reports

New feature motivation
Pulling down the findings and running a dashboard for them isn't viable for many of my customers. Please keep the HTML report format.
Solution Proposed
Keep the HTML report format.
Describe alternatives you've considered
I have tried the dashboard but it isn't viable for my customers.
Additional context
No response

Hi! @Outrun207 HTML outputs are already in master! We'll release the changes on mondays!


get_or_create_imagestream: retry on conflict

409 responses seen in production:
{
  "kind":"Status",
  "apiVersion":"v1",
  "metadata":{},
  "status":"Failure",
  "message":"imagestreams.image.openshift.io \"[...]\" already exists",
  "reason":"AlreadyExists",
  "details": {
    "name":"[...]",
    "group":"image.openshift.io",
    "kind":"imagestreams"
  },
  "code":409
}

Signed-off-by: Tim Waugh<EMAIL_ADDRESS>Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[x] Pull request includes link to an osbs-docs PR for user documentation updates
[x] New feature can be disabled from a configuration file

Added release note:

the import_image plugin is more robust when ensuring an image stream is present


Make runner compatible with wide range of SDK revisions

When I started regenerating the corpus of stats, I realized that the runner and loadgen did not run correctly against both older and newer SDK revisions (I was working against a somewhat outdated version).
In particular:

Newer SDKs do not provide sufficient RUN/BLD to pay for Zoe fees and let the loadgen complete multiple cycles
When killing the chain while under load (middle of a mailbox delivery), the validator node would stall on restart (https://github.com/Agoric/agoric-sdk/issues/4115)
The stats of shorter stages would be impacted by increasing setup time that was performed during stage 1, causing these stats to be unreliable

The first issue is fixed by provisioning and starting the local-solo manually, which required hooking into the cli to figure out the right path to use across revisions.
The second issue is addressed by winding down the loadgen before shutting everything down. The issue has since been fixed in the agoric-sdk (https://github.com/Agoric/agoric-sdk/pull/4116), but the workaround is left for older revisions, and is made configurable if we want to test for regressions.
For the last issue, the default config moves the wallet and loadgen deployments to stage 0, which is now truly a full setup stage.
As always, best reviewed commit-by-commit.
Stacks on top of the stats work (#36).

@michaelfig I addressed your feedback in https://github.com/Agoric/testnet-load-generator/pull/37/commits/ec6244195b03ad5287de9d421d57f2a113a05ca8 and made a small further change in https://github.com/Agoric/testnet-load-generator/pull/37/commits/1e66f9ec839038234d73b09093ed81a213feaad6.
Will carry your previous approval, squash and merge.


give a tip when config is missing output.filename

#1094

:+1:

Good idea.
But make sure that webpack without config still prints the help screen.
In addition to that you should point the user in your error message to the --help option (if the user want to pass the output file as CLI parameter)

Merged something similar.


fix(featured-media): Fix media caption size with different image size - OEL-910

I am not sure about this approach. If width of the figcaption can now be set by the width of text. ex:

Is this correct?


Why delivery_handler, not interceptor?

Is there a specific reason that mail-gpg has been implemented as a delivery_handler, instead of an interceptor?
The latter seems more appropriate to me. And it would also enable to chain it with other custom code that modifies messages, while with the delivery_handler I must implement my own code as delivery_handler that wraps mail-gpg.
Would it be an option to maybe rebuild mail-gpg as an interceptor?
Background: I want to handle specific headers in a certain way (remove them from the encrypted message) in order to protect headers as suggested by https://github.com/autocrypt/memoryhole

Actually I have a long-standing item on my todo list that says "look into action mailer interceptors". So if you want to give it a try, I'd be happy to get that done.

Ok, I'll try.

I have some working code now,  but there is one big difference in behaviour of which I'm not sure if you're OK with: As an interceptor, mail-gpg must work on the very object, not a copy of it. That means, delievering a Mail::Message-object changes it:
mail = Mail.new { subject 'test'; body 'blabla'; from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>}
mail.gpg encrypt: true
puts mail.body.to_s
=> "blabla"
mail.deliver
puts mail.body.to_s
=> "----- BEGIN PGP MESSAGE -----\n ..."

People who use mail-gpg in loops, e.g. to send a message to multiple recipients, would run into problems, because the lose the original message.

 But the behvaiour is rather surprising, I think.

On the other hand, mail-gpg changes some state during encryption already: it deletes `:encrypt` from the gpg-options (By the way: why's that?).

On the positive side: as an interceptor, mail-gpg doesn't have to copy headers.

What do you think about this?

ping.

Sorry for the late reply.
In general I think if we made it clear in the changelog that the message object will be modified and make it a new major version such change in behavior would be ok. However there's a couple more things to consider.
I just found a (quite old) blog post which outlines another problem:

using deliver! [instead of deliver] will call any registered Mail Observers, but not Interceptors - meaning that your mail will be sent unaltered.

https://joshmcarthur.com/howto/2011/10/06/action-mailer-interceptors.html
I am not sure whats the reasoning behind this or if it maybe was just a bug in Rails that's already fixed now, but surely something to keep in mind. I wouldn't want to have such an inconsistency in behavior.
Another change for users will be that they will have to register the interceptor manually because the order multiple interceptors are registered in will matter. Will give the user more control (i.e. only enable it in production...) though.
Regarding the Memory Hole project - isn't what they advertise (putting the headers into the encrypted part) exactly what mail-gpg already does? All that is left to do in order to fully implement this would be formalizing a way to define what headers are sensitive and should be moved into the signed/encrypted part, and which probably should just be copied. The latter might make sense when signing only - leaving headers in the main message will help with clients unaware of the memory hole standard.
That would give you a way to move sensitive headers into the encrypted part, and it might also help with cases like #53 where people explicitly want no headers in there.
The header copying has been a problematic area of mail-gpg all the time, moving from a hard-coded list that had to be maintained to 'encrypt them all' which then made users ask why that is the case. I think implementing a flexible way that probably not only supports header names but also regexps to catch i.e. all X-Redmine-.+ Headers would be a good thing regardless of the Interceptor / DeliveryHandler issue.
What do you think?

Alright, so I'll clean up the interceptor-code.
Regarding the other topics:

Since 2012-01-24, deliver! calls interceptors (released in mail v2.4.2)
I would opt to register the Interceptor on inclusion of mail-gpg, and document how to un-register and re-register it in case of the need.
Memoryhole wants the headers /moved/ in some circumstances, yes. For encryption it's only a little bit more than mail-gpg currently does. For decryption it would raise the question how to communicate to the surrounding code, which headers had been protected (#45). If you're interested, we could tackle that and implement a memoryhole-option in mail-gpg, too! But's (for decryption) it would be more work than just to change a few lines of code, I'm afraid.
Regardless of memoryhole, I think it would be good to allow surrounding code to influence, which headers will be copied.

@jkraemer Ping ... :)


Added missing space to make :white_check_mark: visible as a pic

Problem
In the Build . - Default / . - Default summary section of an action results I see :white_check_mark: instead of :white_check_mark::

Solution
separate a number and the smile by a space:

"$($appPassed) :white_check_mark:"
"$($appFailed) :x:"
"$($appSkipped) :white_circle:"

This must be a change in the markdown rendering of GitHub - this definitely used to work...
Thanks


debug:info is sensitive to directory name, not pyproject.toml name

[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: macOS 10.14.2
Poetry version: 0.12.11
Link of a Gist with the contents of your pyproject.toml file pyproject.toml follows:

[tool.poetry]
name = "foo"
version = "0.1.0"
description = ""
authors = [""]

[tool.poetry.dependencies]
python = "^3.6"

[tool.poetry.dev-dependencies]

[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

Issue

This project is named foo, and when it's present in a directory named foo, poetry debug:info prints the following:
Poetry
======

 * Version: 0.12.11
 * Python:  3.6.4

Virtualenv
==========

 * Python:         3.6.4
 * Implementation: CPython
 * Path:           /path/to/user/directory/Library/Caches/pypoetry/virtualenvs/foo-py3.6
 * Valid:          True

System
======

 * Platform: darwin
 * OS:       posix
 * Python:   /usr/local/Cellar/python/3.6.4_3/Frameworks/Python.framework/Versions/3.6

but if you change the directory name as mv foo bar, it loses track of the virtual environment:
Poetry
======

 * Version: 0.12.11
 * Python:  3.6.4

Virtualenv
==========

 * Python:         3.6.4
 * Implementation: CPython
 * Path:           NA

System
======

 * Platform: darwin
 * OS:       posix
 * Python:   /usr/local/Cellar/python/3.6.4_3/Frameworks/Python.framework/Versions/3.6

That's the intended behavior.
Poetry calculates the name of the virtual environment based on the containing folder name and the python version used for the project. If you change the folder's name, poetry won't be able to find the virtual environment because it will use the same formula that it used before:
foo
├── foo_pkg
│   └── __init__.py
├── poetry.lock
├── pyproject.toml
├── README.rst
└── tests
    ├── __init__.py
    └── test_foo_pkg.py

The first time you run poetry install and poetry debug:info, poetry will use foo and the python version to generate the virtualenv name: foo-py3.6
Later, when you mv (rename) your containing folder to "bar":
bar
├── foo_pkg
│   └── __init__.py
├── poetry.lock
├── pyproject.toml
├── README.rst
└── tests
    ├── __init__.py
    └── test_foo_pkg.py

Poetry will again use the folder_name + python-version to figure out the name of the created venv for the project, which in turns does not exist. You either run poetry install again to generate a new virtual environment with the new containing folder's name or rename the directory back to its original name.

Maintainers: what is the expected behavior here?

@seansfkelley Poetry uses the full path of the project to create the virtualenv, especially in the upcoming 1.0 release. So if you rename your directory the virtualenv name will also change.


Update .gitignore

This PR removes the exclusion of the generated source code files from the git repository. The rationale is to enable the project to be built without any Ruby setup in the developer's machine.

So I think the idea is good of making it so it can be built on a machine without Ruby, but I don't want to go this way with it. We gitignored those files because it was really hard to review pull requests with so much noise any time one of those files changed.
I think another way to go would be to release the shared library itself as a package on the various native package managers (e.g., apt-get) and also maybe as a homebrew tap. That way folks could get the library with everything already templated but wouldn't have to have Ruby.


Add the number of Molecular events to the report for Reactome loads

@dustine32 is creating a report for @deustp01 and me that contains statistics for each Reactome load. Since one of the goals of the project is to resolve any issues with molecular events that are created during the import, we would like to have the number of molecular events in each model added as a column in the report.

@dustine32 Is this minerva code and which project is this in?

I'm pretty sure @dustine32 did this and sent me a report this morning. We narrowed the request to only signaling pathways.


[BUG] S3 Backup fails with "failed to put object"

Describe the bug
Backing up a 50 GB Volume fails after a few minutes. (Actually every time, after a few percent, but on a different block each time)
To Reproduce
Steps to reproduce the behavior:

Schedule a Backup or click "Create Backup" in the GUI
Backup Starts
After a few minutes, progress stops and the Error is shown on MouseOver

Expected behavior
Backup works
Log (longhorn-manager)
time="2020-11-10T09:20:55Z" level=debug msg="Backup backup-31c0bda2335c4035 created for volume pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a snapshot 04e13c5d-fa83-41c1-a3f8-2127f7502641"
time="2020-11-10T09:20:55Z" level=debug msg="Backup snapshot 04e13c5d-fa83-41c1-a3f8-2127f7502641 with label map[KubernetesStatus:{\"pvName\":\"pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a\",\"pvStatus\":\"Bound\",\"namespace\":\"kube-prometheus-stack\",\"pvcName\":\"prometheus-kube-prometheus-stack-prometheus-db-prometheus-kube-prometheus-stack-prometheus-0\",\"lastPVCRefAt\":\"\",\"workloadsStatus\":[{\"podName\":\"prometheus-kube-prometheus-stack-prometheus-0\",\"podStatus\":\"Running\",\"workloadName\":\"prometheus-kube-prometheus-stack-prometheus\",\"workloadType\":\"StatefulSet\"}],\"lastPodRefAt\":\"\"}] for volume pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a"
time="2020-11-10T09:25:53Z" level=error msg="Failed to updated volume LastBackup for pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a due to backup error failed to put object: backupstore/volumes/d5/23/pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a/blocks/cc/c7/ccc7cdd2862e274459533024d5f8339cac5ec3c9583cd2ac85272d66a1b924c7.blk response: {\n\n} error: AWS Error:  RequestError send request failed Put https://s3.eu-central-1.amazonaws.com/longhorn-backup.testconnex.com/backupstore/volumes/d5/23/pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a/blocks/cc/c7/ccc7cdd2862e274459533024d5f8339cac5ec3c9583cd2ac85272d66a1b924c7.blk: read tcp <IP_ADDRESS>:42994-><IP_ADDRESS>:443: read: connection reset by peer\n"
its a different Block every time:
time="2020-11-10T09:02:54Z" level=error msg="Failed to updated volume LastBackup for pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a due to backup error failed to put object: backupstore/volumes/d5/23/pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a/blocks/ec/6c/ec6c08b505ed8ccc2f1afbb4bc32a291caa99af07723ab62e85a81e5157d5b02.blk response: {\n\n} error: AWS Error:  RequestError send request failed Put https://s3.eu-central-1.amazonaws.com/longhorn-backup.testconnex.com/backupstore/volumes/d5/23/pvc-8aaaaebf-ebd3-4443-8b41-9eb1b92ae54a/blocks/ec/6c/ec6c08b505ed8ccc2f1afbb4bc32a291caa99af07723ab62e85a81e5157d5b02.blk: read tcp <IP_ADDRESS>:47580-><IP_ADDRESS>:443: read: connection reset by peer\n"
Environment:

Longhorn version: v1.0.2
Kubernetes version: v1.19.3
Node OS type and version: CentOS Linux release 7.8.2003

Additional context

It seems your S3 endpoint is unstable.
AWS Error: RequestError send request failed

That means the send request to the S3 failed.

Its the standard EU Central (Frankfurt) Endpoint for S3, i don't think it becomes unstable.
There is a Status at https://status.aws.amazon.com/ - no service disruption etc.
Plus we are using S3 all the time, doing backups using restic for example - no problems there.
Checked again today, the problem persists.
I think that it's a problem in the client (see https://github.com/aws/aws-sdk-go/issues/1242 and the comment from AWS at https://forums.aws.amazon.com/thread.jspa?threadID=111195).
Imho a single failed upload of a block should not stop the backup, it should be retried, either manually or using retryer or via the s3manager api. (If i could write that code i would do it but i'm not fluent in go..)

@wwu-cx Make sense. There seems still a connectivity issue but we do need to retry.

@wwu-cx I couldn't reproduce the problem. Please let me know if your setup has something different. Here is what I have tried:
**Scenario 1: **

Install Longhorn v1.0.2.
Create a volume of size of 50GB.
Setup a backup target pointing to an S3 bucket in EU Central (Frankfurt) - eu-central-1 region.
Write 16GB of data to the volume.
Take a backup using Longhorn UI.
I observe that the backup successfully finishes in ~ 2 hours (it is a bit long because my cluster is in California and the S3 bucket is in EU Central)

**Scenario 2: **

Install Longhorn master.
Create a volume of size of 50GB.
Setup a backup target pointing to an S3 bucket in EU Central (Frankfurt) - eu-central-1 region.
Write 26GB of data to the volume.
Take a backup using Longhorn UI.
I observe that the backup successfully finishes in ~ 3 hours and 9 mins (it is a bit long because my cluster is in California and the S3 bucket is in EU Central)

Even though I couldn't reproduce the problem, I agree with you that a single failed upload of a block should not stop the backup. We will add a MaxRetries=3 to S3 service to allow 3 retries up on failure.
@yasker
Regarding to aws-go-sdk, we currently are using v1.25.16 which was released on 10/2019. I think that it should be ok.

@PhanLe1010 I think @wwu-cx 's issue is likely caused by the local ISP rather than AWS. So it's possible some packet dropped on it's way to the AWS.

Thanks @yasker for the info!

Test steps:
Make sure that this PR does break the backup and restore feature

Test steps:
Goal: we want to verify that Longhorn does actually attempt to retry the failed request to S3 and the maximum number of retries is 3

Install Squid

Copy the following file to ~/squid.conf in your VM

#
# Recommended minimum configuration:
#

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src <IP_ADDRESS>/8	# RFC1918 possible internal network
acl localnet src <IP_ADDRESS>/12	# RFC1918 possible internal network
acl localnet src <IP_ADDRESS>/16	# RFC1918 possible internal network
acl localnet src fc00::/7       # RFC 4193 local private network range
acl localnet src fe80::/10      # RFC 4291 link-local (directly plugged) machines

#acl longhorn src <LONGHORN-WORKER-NODE-1-IP>
#acl longhorn src <LONGHORN-WORKER-NODE-2-IP>
#acl longhorn src <LONGHORN-WORKER-NODE-3-IP>

acl SSL_ports port 443
acl SSL_ports port 6443
acl Safe_ports port 80		# http
acl Safe_ports port 21		# ftp
acl Safe_ports port 443		# https
acl Safe_ports port 70		# gopher
acl Safe_ports port 210		# wais
acl Safe_ports port 1025-65535	# unregistered ports
acl Safe_ports port 280		# http-mgmt
acl Safe_ports port 488		# gss-http
acl Safe_ports port 591		# filemaker
acl Safe_ports port 777		# multiling http
acl Safe_ports port 6443        # k8s
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#
# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# Control requests from longhorn to S3
# http_access deny longhorn

# And finally deny all other access to this proxy
http_access allow all

# Squid normally listens to port 3128
http_port 3128

# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/cache/squid 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /var/cache/squid

#
# Add any of your own refresh_pattern entries above these.
#
refresh_pattern ^ftp:		1440	20%	10080
refresh_pattern ^gopher:	1440	0%	1440
refresh_pattern -i (/cgi-bin/|\?) 0	0%	0
refresh_pattern .		0	20%	4320

Install Squid using the above config file:docker run -d -v /home/$USER/squid.conf:/etc/squid/squid.conf -p 3128:3128 wernight/squid

Docker exec into the squid container
See the traffic that goes through the proxy by runningtail -f /var/log/squid/access.log

Punt the validation to v1.1.1. As long as there is no side effect for the v1.1.0 release (which we can observe from the nightly test), I am fine with including the fix now.

Validated with Longhorn master - 01/15/2021
Validation - Pass
Followed the test steps from https://github.com/longhorn/longhorn/issues/1967#issuecomment-736955281, on blocking the S3 traffic on proxy, Longhorn retries 4 times.

Validated with Longhorn master - 01/15/2021
Validation - Pass
Followed the test steps from https://github.com/longhorn/longhorn/issues/1967#issuecomment-736955281, on blocking the S3 traffic on proxy, Longhorn retries 4 times.


Errors whilst trying to build Web Assembly

Hi Guys,
I followed these instructions here:
https://github.com/dotnet/corert/blob/master/Documentation/how-to-build-WebAssembly.md
I finally got to the end part for building the web assembly using build.cmd wasm but I got these errors:
"
JIT - TOTAL: 15 PASSED: 15
CPP - TOTAL: 6 PASSED: 6
WASM - TOTAL: 0 PASSED: 0
C:\corert>build.cmd wasm
Checking pre-requisites...

** Visual Studio 2019 Developer Command Prompt v16.6.4
** Copyright (c) 2020 Microsoft Corporation

Commencing CoreRT Repo build
Commencing build of native components for WebAssembly.wasm.Debug

** Visual Studio 2019 Developer Command Prompt v16.6.4
** Copyright (c) 2020 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x86_x64'
configure: C:\Program Files\CMake\bin\cmake.exe -DCMAKE_TOOLCHAIN_FILE=C:/Users/david/source/repos/emsdk/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake -DCLR_CMAKE_TARGET_ARCH=wasm -DCMAKE_BUILD_TYPE=Debug -G NMake Makefiles C:\corert\buildscripts..\src\Native -DCMAKE_CROSSCOMPILING_EMULATOR="C:/Users/david/source/repos/emsdk/node/12.18.1_64bit/bin/node.exe"
-- The ASM compiler identification is unknown
-- Found assembler: C:/Users/david/source/repos/emsdk/upstream/emscripten/emcc.bat
-- Warning: Did not find file Compiler/-ASM
CMake Error at gc/unix/configure.cmake:97 (check_library_exists):
check_library_exists Macro invoked with incorrect arguments for macro
named: CHECK_LIBRARY_EXISTS
Call Stack (most recent call first):
Runtime/CMakeLists.txt:150 (include)
-- Configuring incomplete, errors occurred!
See also "C:/corert/bin/obj/Native/WebAssembly.wasm.Debug/CMakeFiles/CMakeOutput.log".
See also "C:/corert/bin/obj/Native/WebAssembly.wasm.Debug/CMakeFiles/CMakeError.log".
Failed to generate native component build project
Native component build failed. Refer C:\corert\buildscripts..\bin\Logs\Native_WebAssembly__wasm__Debug.log for details.
C:\corert>"
The full log from CMakeError.log is below:
"Checking whether the ASM compiler is GNU using "--version" did not match "(GNU assembler)|(GCC)|(Free Software Foundation)":
emcc (Emscripten gcc/clang-like replacement) 1.39.19 (f45bea21f3a8f74a68ed4e3e3d7e290807ee2aff)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Checking whether the ASM compiler is Clang using "--version" did not match "(clang version)":
emcc (Emscripten gcc/clang-like replacement) 1.39.19 (f45bea21f3a8f74a68ed4e3e3d7e290807ee2aff)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Checking whether the ASM compiler is AppleClang using "--version" did not match "(Apple LLVM version)":
emcc (Emscripten gcc/clang-like replacement) 1.39.19 (f45bea21f3a8f74a68ed4e3e3d7e290807ee2aff)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Checking whether the ASM compiler is ARMClang using "--version" did not match "armclang":
emcc (Emscripten gcc/clang-like replacement) 1.39.19 (f45bea21f3a8f74a68ed4e3e3d7e290807ee2aff)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Checking whether the ASM compiler is HP using "-V" did not match "HP C":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Checking whether the ASM compiler is Intel using "--version" did not match "(ICC)":
emcc (Emscripten gcc/clang-like replacement) 1.39.19 (f45bea21f3a8f74a68ed4e3e3d7e290807ee2aff)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Checking whether the ASM compiler is SunPro using "-V" did not match "Sun C":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Checking whether the ASM compiler is XL using "-qversion" did not match "XL C":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Checking whether the ASM compiler is MSVC using "-?" did not match "Microsoft":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Checking whether the ASM compiler is TI using "-h" did not match "Texas Instruments":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Checking whether the ASM compiler is IAR using "" did not match "IAR Assembler":
emcc:WARNING: no input files
Checking whether the ASM compiler is ARMCC using "" did not match "(ARM Compiler)|(ARM Assembler)":
emcc:WARNING: no input files
Checking whether the ASM compiler is NASM using "-v" did not match "(NASM version)":
clang version 11.0.0 (C:swircachegitchromium.googlesource.com-external-github.com-llvm-llvm--project 7bf299c8d8d59304fb821f8811618cdeb1d1f1fd)
Target: x86_64-pc-windows-msvc
Thread model: posix
InstalledDir: C:/Users/david/source/repos/emsdk/upstream/bin
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 1.39.19
shared:INFO: (Emscripten: Running sanity checks)
Checking whether the ASM compiler is YASM using "--version" did not match "(yasm)":
emcc (Emscripten gcc/clang-like replacement) 1.39.19 (f45bea21f3a8f74a68ed4e3e3d7e290807ee2aff)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Checking whether the ASM compiler is ADSP using "-version" did not match "Analog Devices":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Checking whether the ASM compiler is QCC using "-V" did not match "gcc_nto":
emcc: error: no input files
note that input files without a known suffix are ignored, make sure your input files end with one of: ('.c', '.i', '.cpp', '.cxx', '.cc', '.c++', '.CPP', '.CXX', '.C', '.CC', '.C++', '.ii', '.m', '.mi', '.mm', '.mii', 'nul', '.S', '.bc', '.o', '.obj', '.lo', '.dylib', '.so', '.a', '.ll', '.s', '.h', '.hxx', '.hpp', '.hh', '.H', '.HXX', '.HPP', '.HH')
Determining if files sys/time.h exist failed with the following output:
Change Dir: C:/corert/bin/obj/Native/WebAssembly.wasm.Debug/CMakeFiles/CMakeTmp
Run Build Command(s):nmake /nologo cmTC_2b95d\fast && 	C:\Program Files (x86)\GnuWin32\bin  -f CMakeFiles\cmTC_2b95d.dir\build.make /nologo -L                  CMakeFiles\cmTC_2b95d.dir\build
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'C:\Program' : return code '0x1'
Stop.
Source:
/* */
#include <sys/time.h>
int main(void){return 0;}
Determining if files sys/mman.h exist failed with the following output:
Change Dir: C:/corert/bin/obj/Native/WebAssembly.wasm.Debug/CMakeFiles/CMakeTmp
Run Build Command(s):nmake /nologo cmTC_6e999\fast && 	C:\Program Files (x86)\GnuWin32\bin  -f CMakeFiles\cmTC_6e999.dir\build.make /nologo -L                  CMakeFiles\cmTC_6e999.dir\build
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'C:\Program' : return code '0x1'
Stop.
Source:
/* */
#include <sys/mman.h>"
There is more of the log but I do not have enough space to post here...
So looks like a version conflict somewhere? Is this to do with Emscripten?
Any help would be greatly appreciated thank you! :)
Cheers
D.

Looks like the build is finding your GnuWin32 installation before Visual Studio.  For example you have
Run Build Command(s):nmake /nologo cmTC_6e999\fast && C:\Program Files (x86)\GnuWin32\bin -f CMakeFiles\cmTC_6e999.dir\build.make /nologo -L CMakeFiles\cmTC_6e999.dir\build

Where are I have
Run Build Command(s):nmake /nologo cmTC_4af50\fast && 	"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.26.28801\bin\HostX86\x64\nmake.exe" -f CMakeFiles\cmTC_4af50.dir\build.make /nologo -L                  CMakeFiles\cmTC_4af50.dir\build

How are you starting the command prompt from Win, then "cmd", or from the "x64 Native Tools Command Prompt for VS 2019" command prompt?

Hi, thanks for getting back to me, I tried as you suggested running "x64 Native Tools Command Prompt for VS 2019" prompt but produced the same result... any other ideas? thanks. :)
Is there any other suggestions?

hmm, not sure.  What version of cmake do you have?

One other thing.  When you run build wasm from "x64 Native Tools Command Prompt for VS 2019", delete the bin and obj folders first in case it has cached some duff build file.

Ok thanks will try Tomorrow... 🙂
Get Outlook for Androidhttps://aka.ms/ghei36

From: yowl<EMAIL_ADDRESS>Sent: Thursday, August 20, 2020 8:34:27 PM
To: dotnet/corert<EMAIL_ADDRESS>Cc: David Ellams<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dotnet/corert] Errors whilst trying to build Web Assembly (#8258)
One other thing. When you run build wasm from "x64 Native Tools Command Prompt for VS 2019", delete the bin and obj folders first in case it has cached some duff build file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcorert%2Fissues%2F8258%23issuecomment-677859437&data=02|01||a599c3b067e14ba68a9308d845400d5e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637335488680701950&sdata=o8X3Hts0FxxVSaSSZ1jKmG6uyeH6uZxTysQuzOFPwb0%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA236SWIIJGVVPB22WJ6VUDSBV3EHANCNFSM4PX7RESQ&data=02|01||a599c3b067e14ba68a9308d845400d5e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637335488680701950&sdata=xCrcmXhUR7QYaqZ4h7KEOxG%2FTNY7XA2K9wVF%2BWhi3AI%3D&reserved=0.


WIP Yubicosign

It works on my box!
Signed-off-by: Dan Lorenc<EMAIL_ADDRESS>Ref #108

Not sure how these hardware work, but would this apply to public-key command too?

Yes, added!

I assume the private key is never extracted from the device? If so, why do we implement generate-key-pair (and write to the file)? I don't think we do that in -kms?
We have to create the key initially. I need to add some TODOs here to pin protect this and handle that other stuff (the admin pin, the pin for the touch).

Also, how does it apply to "verify" cmds? Would anyone actually verify with Yubikey?

Yeah, it works there too. You can verify either with the extracted pub or with the key itself.

Does this work with Yubico gnubby we get at Google? I have one plugged  but getting error: no yubikey found. (I'll try to find my personal yubikey and try that too.)

I tried again with these two keys and piv.Cards() still return nil.

Does this work with Yubico gnubby we get at Google? I have one plugged but getting error: no yubikey found. (I'll try to find my personal yubikey and try that too.)

I actually couldn't get that to work either. I think they might be firmware flashed, but my Yubikey was actually pretty old so I didn't try too hard.
I ordered a few of these: https://www.yubico.com/product/yubikey-5c/


Create wiki with full documentation

This needs to be done, a section in README.md just doesn't suffice. And with v3.1.0 almost done it needs to be written up pretty quickly. Any help would be amazing!
Even if I write all of the actual documentation, user submitted examples would be really helpful, even links to projects in which you have used it.

Heres the first page. EventEmitter.addListener documentation. All the rest will follow suit. Any help would be great. I am just adapting the JSDoc found in the source.

Done. Wouldn't be surprised if someone found a typo or something. Let me know if you do!


Fix: Build only the specified artifact library when multiple types are available

What does this PR try to resolve?
Fixes #12109.
TL;DR:
A crate bar exposes it's library as both a staticlib and a cdylib. A second crate foo specifies an artifact dependency of type staticlib on bar, meaning cargo should build bar as a staticlib and expose certain environment variables (e.g. CARGO_STATICLIB_FILE_BAR). However, due to a bug, cargo ends up building (and exposing the associated environment variables) for both the staticlib and cdylib.
The same happens if foo specifies an artifact dependency of type cdylib; both artifact types are built.
How should we test and review this PR?
The first commit introduces a test which reproduces the issue, the second commit introduces the fix. This setup was recommended by @ehuss.
Additional information
Artifact dependencies: https://rust-lang.github.io/rfcs/3028-cargo-binary-dependencies.html
TL;DR
If a crate foo requests an artifact dependency of kind <artifact_kind> from a crate bar then the following happens:

bar is built with crate-type <artifact_kind> and a directory is created at target/<profile>/deps/artifact/bar-<build_hash_or_something>/<artifact_kind>. The binary artifact is placed in this directory.
Cargo exposes certain environment variables, the most important for this PR is CARGO_<artifact_kind>_FILE_BAR, which points to the binary artifact that was specified. This environment variable is available at compile time for normal dependencies and at runtime for build-dependencies.

If multiple artifact-kinds are requested cargo will create a unit for each, and so they will all be built separately.

Thank you for the patch!
@bors r+

:hourglass: Testing commit 9a5cfbcbb9b5a73272a595c65f529de1e5ad9377 with merge 4e59631d9468c33eb8727adac91eb6e3eff2762a...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 4e59631d9468c33eb8727adac91eb6e3eff2762a to master...


decimal matches link without scheme

Hi I noticed a number with a decimal point is picked up as a link as long as it's preceded by whitespace.
not a link
1.0

is a link
 1.0

This seems like a false positive. Particularly because of the whitespace thing. Also I don't know why "1.0" would be a link but it also matches "1.2.3" regardless of whitespace and I'm not so sure about that one either.
edit okay so my understanding is something like 1.1 isn't really a valid address. it works sometimes ... like you can ping 1.1 and it will try pinging <IP_ADDRESS> because of a quirk in networking stacks ... but it's like an accident or something.  ipcalc 1.1 will tell you "bad IPv4 address"; cool. But then url::Url::parse("http://1.1") parses that as a URL with <IP_ADDRESS> as the host. So now nothing makes sense.

Not the issue creator, but I think that a separate feature for IP addresses would make the most sense.

like you can ping 1.1 and it will try pinging <IP_ADDRESS> because of a quirk in networking stacks ... but it's like an accident or something.

For a fun journey down the rabbit hole, read this article.
The gist is that if an octet gets omitted, it is set to 0. Sometimes.
As per the article, these are all things that will ping <IP_ADDRESS>:

ping 127.0.0.
ping 127.0.1
ping 127.1
ping 0x7f.1
ping<PHONE_NUMBER>

So, yeah, we should stay on the more conservative end of the spectrum I guess.
Demanding 4 octets is what Python requires.
>>> import ipaddress
>>> ipaddress.IPv4Address('127.1')

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.7/ipaddress.py", line 1301, in __init__
    self._ip = self._ip_int_from_string(addr_str)
  File "/usr/lib/python3.7/ipaddress.py", line 1135, in _ip_int_from_string
    raise AddressValueError("Expected 4 octets in %r" % ip_str)
ipaddress.AddressValueError: Expected 4 octets in '127.1'

(By now I quoted almost the entire article, but I hope it helped.)
In summary, I'd go with exactly 4 octets and a separate feature for IP addresses.

We could exclude them and make it an option that can be enabled if it's really wanted.

IPv4 addresses shorter than four octets are surprising/unexpected for most people so they shouldn't be parsed by default.
But the original point was that 1.0 was not matched on its own but it did if it had a space before it. I don't have strong feelings about how addresses are parsed. I don't use that feature of linkify.

Changed in 0.10.0, IP addresses now require exactly 4 parts: https://github.com/robinst/linkify/blob/main/CHANGELOG.md#0100---2023-06-24


feat: route README.md => index

Summary
feat: route README.md => index
links: vuepress route README.md => index
Related Issue

Checklist

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

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

Thank you for your submission! Can you sign CLA to let CI pass?

I think we should document how to handle conflicts with index.md and add an e2e test case to cover this feature.

Hi @ruochuan12 , there are some points to discuss with you about this feature:

We do not want to introduce this default behavior to affect the original users since the default route of readme.md is not a standardized behavior and many other frameworks do not do this, like Vitepress and Docusaurus.
A more appropriate approach is to enable this behavior through a configuration,  which is not a easy work, changes in PR should be far from enough. We need complete tests to ensure that route generation, sidebar generation, link href, etc. work properly in all scenes like all files use index / all files use readme / files use mixed readme&index. And how to deal the conflict of two files should be mainly concerned.

Okay, let's not deal with it for now. I look forward to having such a feature in the future.


consider removing rxjs-observable

i copy and pasted undux into my src folder, removed undux and rxjs-observable from package.json, then replaced rxjs-observable with rxjs. bundle size 18kb smaller according to webpack. rxjs version 6.5.2. I'm only doing webpack --production --optimizie-minimize, nothing fancy

Thanks for the feedback!
RxJS is really big, unless you use a tree shaking bundler or tag RxJS as an external dependency in your build system. I want to try and strike a balance between small bundle sizes for people that use tree shaking bundlers and for people that don't.
To that end, RxJS-Observable was a bit of a hack to support both use cases. For people that don't use a tree shaking bundler, Undux comes with a minimal RxJS-compatible Observable implementation out of the box; for people that do tree shake, they have to eat the cost of a slightly larger bundle.
We could maybe ship two versions, one that uses RxJS directly and one that uses RxJS-Observable. I worry that it may not be obvious to people which one to use, though.
Any ideas? :)

i think at some point in the v6 release they restructured the folders so that importing observable shouldn't bring in the whole lib , even without tree shaking, unless you manually import something deep into the folders.
A workaround though, would be to put rxjs as a peer dependency and put some instructions on how to shim rxjs with rxjs-obserable by installing it as rxjs:'git://bcheryn/rxjs-observable' in the package json. this also ensures users only have 1 copy of their choosing.

i think at some point in the v6 release they restructured the folders so that importing observable shouldn't bring in the whole lib , even without tree shaking, unless you manually import something that's deep into the folders.

Unfortunately, not quite. https://github.com/ReactiveX/rxjs/issues/4011, https://github.com/ReactiveX/rxjs/issues/3971#issuecomment-408696661
We could add it as a peer dependency, potentially. That said, rxjs-obserable is really small -- are you noticing real performance issues in your app while using it?

No, its not a big deal honestly, i just thought that the duplication was unneccessary and 2 copies could lead to wierd things happening. Also, in my unionformed opinion, i dont know why anyone would use an rx observable without rx operators


ENG-3178: adding benchmark scripts

How to:
go to /benchmark folder and run:
./runTests.sh 1000 - the first argument is the quantity of pages you want to generate.
you might need to set permission with chmod on script

@gReis89 I've refactored these scripts with the following changes:

break apart test data generation from actual test run
added build + rebuild scenarios
cleaned up page templates to remove usage of external components like 'Layout'

Could you review my last commit?


Code formatting/style

I've got a couple of suggestions, let me know if you agree and I'll create a pull request.

Only use tabs - no spaces for indentation
Don't use IEnumerable.ForEach, use foreach instead
Put switch break; statements inside the scope regions if present

Cheers

@MendelMonteiro it you think you could make the code cleaner the pleanse go for it and I will happily accept your contribution.


Implement __add__ for cirq.Moment

I'd like to be able to write circuit[index] += cirq.X(qubit) to append an operation into a moment inside a circuit. This requires defining an __add__ operation for moment.
Note that moments are immutable, so do not implement __iadd__; just __add__.

Hi. I would like to work on it.


Is there a way to not expand

I want to keep the outline tree clean and concise. Whenever I click to jump to one method, codeline will expand that method. Is there a way to not expand?

Sorry, this is how tree views currently work in VS Code. Please see https://github.com/Microsoft/vscode/issues/34130 for an upstream bug.


[ERROR]: Failed to package reproducible

Description
Hello
I want to use the "-gui" command to see the "drc" errors. The drc problem is under review in #1553 . The current problem is because no matter what design I am running when I added "-gui" an error occurs and the reproducible package is not created. The original error cannot be solved because there is no reproducible material.
To reproduce the problem:

Clone and make the latest version of openlane

cd $HOME
git clone https://github.com/The-OpenROAD-Project/OpenLane
cd OpenLane
make

Run OpenLane environment
make mount

Execute any design by adding the -gui flag.

e.g. ./flow.tcl -design inverter -gui
Expected Behavior
OpenLane Container (73bc7f8):/openlane$ ./flow.tcl -design inverter -gui
OpenLane 73bc7f8a736d6f2a2d68168daea3e7718d4b6208
All rights reserved. (c) 2020-2022 Efabless Corporation and contributors.
Available under the Apache License, version 2.0. See the LICENSE file for more details.
[INFO]: Using configuration in 'designs/inverter/config.json'...
[INFO]: PDK Root: /home/baungarten/OpenLane/pdks
[INFO]: Process Design Kit: sky130A
[INFO]: Standard Cell Library: sky130_fd_sc_hd
[INFO]: Optimization Standard Cell Library: sky130_fd_sc_hd
[INFO]: Run Directory: /openlane/designs/inverter/runs/RUN_2022.12.09_17.55.51
[INFO]: Preparing LEF files for the nom corner...
[INFO]: Preparing LEF files for the min corner...
[INFO]: Preparing LEF files for the max corner...
[ERROR]: during executing openroad script /openlane/scripts/openroad/gui.tcl
[ERROR]: Log: ../dev/null
[ERROR]: Last 10 lines:
13# 0x00007FC47F4D73F8 in /lib64/libglib-2.0.so.0
14# g_main_context_iteration in /lib64/libglib-2.0.so.0
15# QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) in /lib64/libQt5Core.so.5
16# QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) in /lib64/libQt5Core.so.5
17# QThread::exec() in /lib64/libQt5Core.so.5
18# 0x00007FC4875DC3B5 in /lib64/libQt5DBus.so.5
19# 0x00007FC4838F8E71 in /lib64/libQt5Core.so.5
20# 0x00007FC48705DEA5 in /lib64/libpthread.so.0
21# clone in /lib64/libc.so.6
child killed: SIGABRT
[ERROR]: Creating issue reproducible...
[INFO]: Saving runtime environment...
OpenLane TCL Issue Packager
EFABLESS CORPORATION AND ALL AUTHORS OF THE OPENLANE PROJECT SHALL NOT BE HELD
LIABLE FOR ANY LEAKS THAT MAY OCCUR TO ANY PROPRIETARY DATA AS A RESULT OF USING
THIS SCRIPT.

[ERR] 0 not found.
[ERROR]: Failed to package reproducible.
[INFO]: Saving current set of views in 'designs/inverter/runs/RUN_2022.12.09_17.55.51/results/final'...
[INFO]: Generating final set of reports...
[INFO]: Created manufacturability report at 'designs/inverter/runs/RUN_2022.12.09_17.55.51/reports/manufacturability.rpt'.
[INFO]: Created metrics report at 'designs/inverter/runs/RUN_2022.12.09_17.55.51/reports/metrics.csv'.
[INFO]: Saving runtime environment...
[ERROR]: Flow failed.
Environment report
python3 ./env.py issue-survey
Kernel: Linux v5.15.0-56-generic
Distribution: ubuntu 20.04
Python: v3.8.10 (OK)
Container Engine: docker v20.10.21 (OK)
OpenLane Git Version: 73bc7f8a736d6f2a2d68168daea3e7718d4b6208
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

73bc7f8 2022-12-09T13:20:53+02:00 Add new community guide for using RgGen (#1561) - Cra2yPierr0t -  (HEAD -> master, origin/master, origin/HEAD)
772a224 2022-12-05T15:31:29+02:00 [BOT] Update PDK (#1551) - Openlane Bot -  (tag: 2022.12.06)
010f5ad 2022-12-04T12:20:40+02:00 Add PDK_FAMILY for `volare enable` (#1545) - Kareem Farid -  (tag: 2022.12.05)
---
Git Remotes

origin	https://github.com/The-OpenROAD-Project/OpenLane (fetch)
origin	https://github.com/The-OpenROAD-Project/OpenLane (push)

Reproduction material

No reproducible material

Relevant log output
[ERR] 0 not found.
[ERROR]: Failed to package reproducible.
[INFO]: Saving current set of views in 'designs/inverter/runs/RUN_2022.12.09_17.55.51/results/final'...
[INFO]: Generating final set of reports...
[INFO]: Created manufacturability report at 'designs/inverter/runs/RUN_2022.12.09_17.55.51/reports/manufacturability.rpt'.
[INFO]: Created metrics report at 'designs/inverter/runs/RUN_2022.12.09_17.55.51/reports/metrics.csv'.
[INFO]: Saving runtime environment...
[ERROR]: Flow failed.

This should print out an error now:
[ERROR]: CURRENT_ODB is unset.

Exception handled in #1625


create loginPage.jsx

create page for logging in with login form component

https://github.com/jjackson0228/Pawsitive-Connection/pull/52


Add IDE section to the guide

Mention some popular IDE's that can be used to code in the servers (VSCode, Atom, PyCharm).
I will emphasize VSCode since that is what I use but I will list other popular options. Eventually include the jupyter info in here.

Great idea!  Maybe this should go under computational tools section


2.1.1 fails to open databases after upgrade

This is a pre-emptive bug against which we can de-duplicate issues that get filed in the future.
"When starting up my CouchDB after upgrading from 2.0.0 or 2.1.0 to 2.1.1, I get either a No DB shards could be opened. error in couch.log, or a "This database failed to load" error in Fauxton."
The fix:
Edit your etc/vm.args file and change the line that reads -name<EMAIL_ADDRESS>to -name couchdb@localhost.
This is outlined in our release notes here: http://docs.couchdb.org/en/2.1.1/whatsnew/2.1.html#upgrade-notes

When upgrading from 2.x to 2.1.1, if you have not customized your node name in vm.args, be sure to retain your original vm.args file. The default node name has changed from couchdb@localhost to<EMAIL_ADDRESS>which can prevent CouchDB from accessing existing databases on the system. You may also change the name option back to the old value by setting -name couchdb@localhost in etc/vm.args by hand. The default has changed to meet new guidelines and to provide additional functionality in the future.
If you recieve errors in the logfile, such as internal_server_error : No DB shards could be opened. or in Fauxton, such as This database failed to load. you need to make this change.

Here's a sample of what this might look like in the logs:
[error] 2017-11-08T00:26:55.849333Z<EMAIL_ADDRESS><0.259.0> -------- Error opening view group `_auth` from database `shards/40000000-5fffffff/_users.1497652572`: {'EXIT',{{badmatch,{error,read_failure}},[{couch_mrview,get_info,2,[{file,"src/couch_mrview.erl"},{line,332}]},{couch_compaction_daemon,maybe_compact_view,3,[{file,"src/couch_compaction_daemon.erl"},{line,253}]},{couch_compaction_daemon,maybe_compact_views,3,[{file,"src/couch_compaction_daemon.erl"},{line,227}]},{couch_compaction_daemon,'-compact_loop/1-fun-0-',3,[{file,"src/couch_compaction_daemon.erl"},{line,141}]},{couch_server,'-all_databases/2-fun-0-',4,[{file,"src/couch_server.erl"},{line,278}]},{filelib,do_fold_files2,8,[{file,"filelib.erl"},{line,185}]},{filelib,do_fold_files2,8,[{file,"filelib.erl"},{line,195}]},{couch_server,all_databases,2,[{file,"src/couch_server.erl"},{line,267}]}]}}

It also makes external HTTP requests return 500 responses like:
{"error":"internal_server_error","reason":"No DB shards could be opened.","ref":123456789}

i'm having this error and i think is related with this issue

Already updated vm.args and still facing this. Here's the logs:
[notice] 2017-11-08T15:33:52.716998Z<EMAIL_ADDRESS><0.1989.1> -------- Failed to ensure auth ddoc _users/_design/_auth exists for reason: read_failure
[error] 2017-11-08T15:34:21.377307Z<EMAIL_ADDRESS><0.238.0> -------- Error opening view group `_auth` from database `shards/40000000-5fffffff/_users.1509985194`: {'EXIT',{{badmatch,{error,read_failure}},[{couch_mrview,get_info,2,[{f$
[error] 2017-11-08T15:34:21.398207Z<EMAIL_ADDRESS><0.238.0> -------- Error opening view group `_replicator` from database `shards/80000000-9fffffff/_replicator.1509985194`: {'EXIT',{{badmatch,{error,read_failure}},[{couch_mrview,get$

This is not a catch-all ticket for "My personal upgrade to 2.1.1 didn't work". I am locking this issue down to further replies.
If you need help with your specific upgrade scenario, please first reach out to our mailing list or our Slack/IRC channel before filing a ticket here.