Make sure all properties exist in appendix

https://microsoft.github.io/spring-cloud-azure/4.0.0-beta.4/4.0.0-beta.4/reference/html/appendix.html#_configuration_properties
For example: spring.cloud.azure.keyvault.secret.property-sources[].client.logging.allowed-header-names does not exist in appendix.

In the appendix, all configuration properties must be contained.
But in each section, area owner can decide which properties will be added in that section.

When the property prefix contains List or Map, the prefix in spring-configuration-metadata.json is not complete. The complete prefix needs to be added to additional-spring-configuration-metadata.json manually.

Fix PR: https://github.com/Azure/azure-sdk-for-java/pull/28589

Fix PR merged, now close this issue.


fix: check if mounted when trigger rerender

fix
Resolve #494
react exp version will warn setState calls when component is not mounted. on suspense mode, swr trigger revalidate and lead to call rerender when the component is not mounted yet.

would love to get a release with this fix in it! 🙏


isAuthenticated stays false - despite successful login

Describe the issue:
Hello together, i've tried to integrate @asgardeo/auth-react into my React project to handle the login functionality via WSO2. After calling the signIn function from the useAuthContext-Hook, i get correctly redirected to the login page where i can input the data. After successful login, i get redirected back to my application, where a token-Request is being sent out automatically - that works also. However the state.isAuthenticated variable always stays false - despite the sucessful login.
State during login:

State after login:

Sucessful token fetch:

How to reproduce:
const config = {
  signInRedirectURL: loginUrl,
  signOutRedirectURL: logoutUrl,
  clientID: process.env.WSO2_CLIENT_ID,
  baseUrl: process.env.WSO2_BASE_URL,
  scope: ['openid'],
}

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: 5.2.1
OS: MacOS
React: 18.3.1
Webpack: 5.93.0
Node: 20.12.2

Optional Fields
Related issues:
https://github.com/asgardeo/asgardeo-auth-react-sdk/issues/143

Found the issue - it turns out, the well-known endpoint of my instance was different that the default one.
All i had to do is to mention the URL of my endpoint as wellKnownEndpoint attribute inside the config object.


AttributeError: 'module' object has no attribute 'Proposal'

when i run bash script/additional_deps.sh, I get the following warning:
bash script/additional_deps.sh
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-dev is already the newest version.
python-matplotlib is already the newest version.
unzip is already the newest version.
python-pip is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 120 not upgraded.
The directory '/home/ubuntu/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/ubuntu/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Requirement already satisfied: cython in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: scikit-image in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: easydict in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: dask[array]>=0.5.0 in /usr/local/lib/python2.7/dist-packages (from scikit-image)
Requirement already satisfied: six>=1.7.3 in /usr/local/lib/python2.7/dist-packages (from scikit-image)
Requirement already satisfied: matplotlib>=1.3.1 in /usr/local/lib/python2.7/dist-packages (from scikit-image)
Requirement already satisfied: pillow>=2.1.0 in /usr/local/lib/python2.7/dist-packages (from scikit-image)
Requirement already satisfied: networkx>=1.8 in /usr/local/lib/python2.7/dist-packages (from scikit-image)
Requirement already satisfied: scipy>=0.9.0 in /usr/local/lib/python2.7/dist-packages (from scikit-image)
Requirement already satisfied: numpy; extra == "array" in /usr/local/lib/python2.7/dist-packages (from dask[array]>=0.5.0->scikit-image)
Requirement already satisfied: toolz>=0.7.2; extra == "array" in /usr/local/lib/python2.7/dist-packages (from dask[array]>=0.5.0->scikit-image)
Requirement already satisfied: cycler in /usr/local/lib/python2.7/dist-packages (from matplotlib>=1.3.1->scikit-image)
Requirement already satisfied: pyparsing!=2.0.0,!=2.0.4,!=2.1.2,>=1.5.6 in /usr/local/lib/python2.7/dist-packages (from matplotlib>=1.3.1->scikit-image)
Requirement already satisfied: pytz in /usr/local/lib/python2.7/dist-packages (from matplotlib>=1.3.1->scikit-image)
Requirement already satisfied: python-dateutil in /usr/local/lib/python2.7/dist-packages (from matplotlib>=1.3.1->scikit-image)
Requirement already satisfied: olefile in /usr/local/lib/python2.7/dist-packages (from pillow>=2.1.0->scikit-image)
Requirement already satisfied: decorator>=3.4.0 in /usr/local/lib/python2.7/dist-packages (from networkx>=1.8->scikit-image)
~/Zahraa/mxnet ~/Zahraa/mxnet/example/rcnn
Makefile:35: mshadow/make/mshadow.mk: No such file or directory
Makefile:36: /home/ubuntu/Zahraa/mxnet/dmlc-core/make/dmlc.mk: No such file or directory
Makefile:122: /home/ubuntu/Zahraa/mxnet/ps-lite/make/ps.mk: No such file or directory
make: *** No rule to make target `/home/ubuntu/Zahraa/mxnet/ps-lite/make/ps.mk'.  Stop.
~/Zahraa/mxnet/python ~/Zahraa/mxnet ~/Zahraa/mxnet/example/rcnn
Traceback (most recent call last):
  File "setup.py", line 21, in <module>
    LIB_PATH = libinfo['find_lib_path']()
  File "mxnet/libinfo.py", line 37, in find_lib_path
    'List of candidates:\n' + str('\n'.join(dll_path)))
RuntimeError: Cannot find the files.
List of candidates:
/home/ubuntu/Zahraa/mxnet/python/mxnet/libmxnet.so
/home/ubuntu/Zahraa/mxnet/python/mxnet/../../lib/libmxnet.so
/home/ubuntu/Zahraa/mxnet/python/mxnet/../../build/Release/libmxnet.so
libmxnet.so
/usr/local/cuda/lib64/libmxnet.so
~/Zahraa/mxnet ~/Zahraa/mxnet/example/rcnn
~/Zahraa/mxnet/example/rcnn
cd rcnn/cython/; python setup.py build_ext --inplace; rm -rf build; cd ../../
running build_ext
skipping 'bbox.c' Cython extension (up-to-date)
skipping 'cpu_nms.c' Cython extension (up-to-date)
skipping 'gpu_nms.cpp' Cython extension (up-to-date)
cd rcnn/pycocotools/; python setup.py build_ext --inplace; rm -rf build; cd ../../
Warning: Extension name '_mask' does not match fully qualified name 'rcnn.pycocotools._mask' of '_mask.pyx'
running build_ext

Later when I execute  bash script/vgg_voc07.sh 0,1
Called with argument: Namespace(begin_epoch=0, dataset='PascalVOC', dataset_path='data/VOCdevkit', end_epoch=10, frequent=20, gpus='0,1', image_set='2007_trainval', kvstore='device', lr=0.001, lr_step='7', network='vgg', no_flip=False, no_shuffle=False, prefix='model/e2e', pretrained='model/vgg16', pretrained_epoch=0, resume=False, root_path='data', work_load_list=None)
Traceback (most recent call last):
  File "train_end2end.py", line 184, in <module>
    main()
  File "train_end2end.py", line 181, in main
    lr=args.lr, lr_step=args.lr_step)
  File "train_end2end.py", line 30, in train_net
    sym = eval('get_' + args.network + '_train')(num_classes=config.NUM_CLASSES, num_anchors=config.NUM_ANCHORS)
  File "/home/ubuntu/Zahraa/mxnet/example/rcnn/rcnn/symbol/symbol_vgg.py", line 359, in get_vgg_train
    rois = mx.symbol.Proposal(
AttributeError: 'module' object has no attribute 'Proposal'
Namespace(dataset='PascalVOC', dataset_path='data/VOCdevkit', epoch=10, gpu=0, has_rpn=True, image_set='2007_test', network='vgg', prefix='model/e2e', proposal='rpn', root_path='data', shuffle=False, thresh=0.001, vis=False)
{'ANCHOR_RATIOS': [0.5, 1, 2],
 'ANCHOR_SCALES': [8, 16, 32],
 'FIXED_PARAMS': ['conv1', 'conv2'],
 'FIXED_PARAMS_SHARED': ['conv1', 'conv2', 'conv3', 'conv4', 'conv5'],
 'IMAGE_STRIDE': 0,
 'NUM_ANCHORS': 9,
 'NUM_CLASSES': 21,
 'PIXEL_MEANS': array([ 103.939,  116.779,  123.68 ]),
 'RCNN_FEAT_STRIDE': 16,
 'RPN_FEAT_STRIDE': 16,
 'SCALES': [(600, 1000)],
 'TEST': {'BATCH_IMAGES': 1,
          'CXX_PROPOSAL': True,
          'HAS_RPN': True,
          'NMS': 0.3,
          'PROPOSAL_MIN_SIZE': 16,
          'PROPOSAL_NMS_THRESH': 0.7,
          'PROPOSAL_POST_NMS_TOP_N': 2000,
          'PROPOSAL_PRE_NMS_TOP_N': 20000,
          'RPN_MIN_SIZE': 16,
          'RPN_NMS_THRESH': 0.7,
          'RPN_POST_NMS_TOP_N': 300,
          'RPN_PRE_NMS_TOP_N': 6000},
 'TRAIN': {'ASPECT_GROUPING': True,
           'BATCH_IMAGES': 2,
           'BATCH_ROIS': 128,
           'BBOX_MEANS': [0.0, 0.0, 0.0, 0.0],
           'BBOX_NORMALIZATION_PRECOMPUTED': False,
           'BBOX_REGRESSION_THRESH': 0.5,
           'BBOX_STDS': [0.1, 0.1, 0.2, 0.2],
           'BBOX_WEIGHTS': array([ 1.,  1.,  1.,  1.]),
           'BG_THRESH_HI': 0.5,
           'BG_THRESH_LO': 0.0,
           'CXX_PROPOSAL': True,
           'END2END': False,
           'FG_FRACTION': 0.25,
           'FG_THRESH': 0.5,
           'RPN_BATCH_SIZE': 256,
           'RPN_BBOX_WEIGHTS': [1.0, 1.0, 1.0, 1.0],
           'RPN_CLOBBER_POSITIVES': False,
           'RPN_FG_FRACTION': 0.5,
           'RPN_MIN_SIZE': 16,
           'RPN_NEGATIVE_OVERLAP': 0.3,
           'RPN_NMS_THRESH': 0.7,
           'RPN_POSITIVE_OVERLAP': 0.7,
           'RPN_POSITIVE_WEIGHT': -1.0,
           'RPN_POST_NMS_TOP_N': 2000,
           'RPN_PRE_NMS_TOP_N': 12000}}
Traceback (most recent call last):
  File "test.py", line 40, in <module>
    main()
  File "test.py", line 37, in main
    args.vis, args.shuffle, args.has_rpn, args.proposal, args.thresh)
  File "/home/ubuntu/Zahraa/mxnet/example/rcnn/rcnn/tools/test_rcnn.py", line 25, in test_rcnn
    sym = eval('get_' + network + '_test')(num_classes=config.NUM_CLASSES, num_anchors=config.NUM_ANCHORS)
  File "/home/ubuntu/Zahraa/mxnet/example/rcnn/rcnn/symbol/symbol_vgg.py", line 276, in get_vgg_test
    rois = mx.symbol.Proposal(
AttributeError: 'module' object has no attribute 'Proposal'

I got rid of this error when i installed glog. Now I am getting a new error:
undefined symbol: _ZN2ps4Meta6kEmptyE

I tried make -f Makefile clean but it didnt sovle problem. I also tried make -f Makefile clean_all but i will get the following error:
make: *** No rule to make target `clean_all'.  Stop.

I am back to point zero. I started fresh with a working installation of mxnet and upgraded. With that I am getting the error: AttributeError: 'module' object has no attribute 'Proposal'
This is exactly what I did:
    1  cd mxnet
    2  git pull
    3  cd example/rcnn
    4  ls
    5  bash script/additional_deps.sh
    6  pip install matplotlib
    7  bash script/get_voc.sh
    8  bash script/get_pretrained_model.sh
    9  bash script/vgg_voc07.sh 0,1
   10  ls
   11  cd ..
   12  sed -i 's/EXTRA_OPERATORS =/EXTRA_OPERATORS = example\/rcnn\/operator/g' config.mk
   13  make -j"$(nproc)"
   14  cd example
   15  cd rcnn
   16  make
   17  bash script/vgg_voc07.sh 0,1

I have the same  error

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


Mutually exclusive features

In Windows API there is the notion of a family and partitions. Your choice of family is basically which platform you are targeting and there is a choice between WINAPI_FAMILY_DESKTOP_APP WINAPI_FAMILY_PC_APP WINAPI_FAMILY_PHONE_APP WINAPI_FAMILY_SYSTEM and WINAPI_FAMILY_SERVER. Your choice of family in turn enables certain partitions which enable access to certain functionality. At the moment I cannot use cargo features for this because they are not mutually exclusive, so two downstream dependencies could specify different families which is completely wrong. Even if I use a build script to ensure only one such feature is selected, it would be a nightmare to ensure that every single downstream dependency chooses the same family, threading the choice of family feature through long chains of transitive dependencies that shouldn't have to care about that choice.
What I think would work well here is some sort of feature selection that has to choose exactly one option from a closed set, and that choice is controlled by the root crate. All dependencies that are affected by that choice will then need some way to be informed of the choice so they can adjust which functionality to use depending on that choice.
At the moment the only workaround I see is for the user to pass an environment variable while building the project so winapi's build script can read that to choose the family followed by emitting key=value stuff which downstream dependencies can read via build scripts through the DEP_WINAPI_key=value environment variables to emit cfgs to control their own code.
Also, this can also apply to other choices, such as which version of Windows you want to target, newer versions have more functionality that dependencies might want to be able to take advantage of, but the user might also want them to target an older version instead so it can run on more systems.

I just had this idea, but haven't thought it through yet: To get mutually exclusive features couldn't you just add some piece of code to the crate that is gated on the features that should not be used together and make rustc output some error message that actually points to the problem (do we have something like #error in C, probably a macro?).
This could be considered an ugly workaround, but maybe it allows the greatest flexibility.

@Boddlnagg Suppose the user is working on their project apple which depends on banana which in turn depends on cat which in turn depends on winapi. Now cat is capable of supporting two different winapi families, so how does it deal with this? Suppose it decides to provide two features for each of these options so the user can decide, but wait the user is not the one depending on cat, it is banana. So banana is now responsible for re-exporting those features, even though it does not use winapi directly, and should not care at all which winapi family is being used. But now realize that winapi has a ton of reverse dependencies and the poor user's apple project ends up depending on a whole messy dependency graph with winapi up many of those branches. Do you really expect every single crate in between apple and winapi to diligently re-export features so that the user can choose which family they want?
Right now the way features work is that foo specifies which features it requires from bar and the user only has any say in this if foo provides its own features to control this, and every single transitive dependency downstream re-exports these features. What I really think we need instead is a way for foo to specify which features it could use from bar, but not necessarily require. Then the user can choose which of those features it wants and foo will be notified in some manner of which features it actually got so it can adjust its code appropriately. Imagine something like hyper where right now if you want to disable the ssl feature (due to that annoying openssl dependency) you have to hope every single crate which depends on hyper, even transitively, re-exports the option to not depend on the ssl feature. If instead each of the crates that directly depends on hyper said it merely could use the ssl feature if it was available, then the user could choose whether or not to enable ssl from a single point and all the reverse dependencies of hyper would be aware of this and adjust accordingly. Without a system like this, I don't think it would be possible to sanely have mutually exclusive features.

Maybe allow specifying feature conflicts in Cargo.toml, such as:
[dependencies.awesome]
version = "1.3.5"
features = ["!secure-password", "civet"]

Which means this package depends on "awesome" but requires the "secure-password" feature to be disabled.
Also,
[features]
go-faster = []
secure-password = ["!go-faster", "bcrypt"]

means that this package provides features "go-faster" and "secure-password". But if "secure-password" is enabled, "go-faster" must be disabled.

Is this still relevant?

Yes.

If so, what is blocking it?

Someone needs to come up with a good design for a better feature system that supports mutually exclusive features among other things.

Is it known what could be done to help move this forward?

Convince someone to work on such a design.

Someone needs to come up with a good design for a better feature system that supports mutually exclusive features among other things.

What's wrong with the design suggested by @mat8913? https://github.com/rust-lang/cargo/issues/2980#issuecomment-270554758
It doesn't cover "among other things", but seems to address the issue while being flexible. (Some consideration would need to be given for the --all-features flag, but an error is seems sufficient)

In inkwell, we currently support 9 different versions of LLVM. This is represented by feature flags which correspond to different versions of our dependency, the llvm-sys crate. We enforce that they are used exclusively though some macro trickery. But cargo has no understanding of this, and so cannot enforce it appropriately. So currently we have multiple branches which just have the slight difference of changing the version number, and version flag.
Mutually exclusive feature flags would allow us to deploy (also to crates.io) one single release where you specify a feature flag, and cargo builds a crate graph that is able to use different dependency versions depending on the flag.
Some previous discussions:
https://github.com/rust-lang/cargo/issues/5653#issuecomment-430489303
https://internals.rust-lang.org/t/mutually-exclusive-feature-flags/8601

What's wrong with the design suggested by @mat8913? #2980 (comment)

The second example in particular can end up being pretty verbose I think. As mentioned previously, in inkwell we have 9 features that we use exclusively for different LLVM versions. So it would look something like this:
[features]
llvm3-6 = ["!llvm3-7", "!llvm3-8", "!llvm3-9", ..., "!llvm8-0"]
llvm3-7 = ["!llvm3-6", "!llvm3-8", "!llvm3-9", ..., "!llvm8-0"]
...
llvm8-0 = ["!llvm3-6", "!llvm3-7", "!llvm3-8", ..., "!llvm7-0"]

I suppose this could be simplified a bit, ie if 3-6 has 3-7 excluded, then 3-7 doesn't need to list 3-6 explicitly. But this seems to be too implicit and potentially a maintenance headache.
It would be clearer to collect exclusions into named sets like so:
[mutually_exclusive_features]
llvm_versions = ["llvm3-6", "llvm3-7", "llvm3-8", ..., "llvm8-0"]

That way, we can keep verbosity down and the compiler can reference the set name in error messages. IE "llvm3-6 and llvm3-7 features cannot be combined as defined in the llvm_versions exclusion set"
To reformat @mat8913's examples:
[features]
go-faster = []
secure-password = ["bcrypt"]

[mutually_exclusive_features]
speed_or_security = ["go-faster", "secure-password"]

[dependencies.awesome]
version = "1.3.5"
features = ["civet"]
mutually_exclusive_features = ["secure-password"]

Some consideration would need to be given for the --all-features flag, but an error is seems sufficient

Agreed. --all-features flag should straight up error when mutually exclusive features are specified

Another way of doing this is to provide "values" for features.
[features]
llvm="9"
flate2="zlib"
winapi_family="desktop_app"

Features could default to true or 1.

hello guys, I've been waiting this for more than one year, any progress?

Still waiting on this, it would be very nice to have. :)

Disclaimer: I don't exactly know how to use below build systems, but here what I found on the topic in them:

Bazel: https://docs.bazel.build/versions/0.26.0/cc-toolchain-config-reference.html#feature-relationships
Gradle:

https://docs.gradle.org/current/userguide/feature_variants.html#sec::incompatible_variants
https://docs.gradle.org/6.0.1/userguide/dependency_capability_conflict.html

Would anyone on the cargo team be willing to mentor an implementation for this? I took a shot at it myself but didn't get much farther than adding an experimental cargo feature

Thanks for offering to help. There are many levels of things to work on for this. Eventually it will probably need an RFC. But given its complexity IMO the implementation should probably come first.
There is work to be done on adding syntax and hammering out the exact semantics. Do we just add a negative feature "!foo" or do we add a new "capability" structure? Then there is figuring out how this is stored in the index, and making sure old cargo do something reasonable. We don't want another misread the index cve. There are probably other things that need to be worked on that I have not thought of.
The part I can provide mentorship on is the dependency resolver. Someone may object that "doesn't this mean that determining witch dependencies have compatible feature requests will now be an SAT problem?" and the answer is Yes. But that is not such a big deal as witch dependencies have compatible dependencies is already an SAT problem. (There are several ways to express mutually exclusive features in terms of dependencies. To take the example from the OP, have a crate for each WINAPI_FAMILY_* each of witch has one published version and has the link attribute set to "WINAPI_FAMILY", then have winapi optionally depend on all of those crates. 🎉 only one of the optionals dependencies will be active.)
So adding support for this to the dependency resolver may be "just":

add a check for a bad set of features to activate
add a new kind of ConflictReason  for activate to return if it fails.
deal with how that interacts with other optimization, possibly by disabling them if negative features are involved.
add lots of test, and possibly add support for features to the existing framework, probably find preceding bugs with transitive features.

I think one of the things that has been mentioned in other places as well as above was, that, to avoid misuse of negative features that'd lead to actually-bad SAT problems, the mutually exclusive features should be possible to set only from the top-level binary crate configuration.
With this in mind, mutually-exclusive features probably don't require any change to the solver other than refusing to set them from library crates, and having some syntax to set them properly in the binary crates. Now, I'm saying this without ever having had a look at cargo's feature solver, so I may be completely wrong :)

To contribute my small part to this conversation, I've recently come across a case where the right outcome seems like it'd be to compile two independent copies of a crate if mutually exclusive features are used. Essentially, treat "exclusive" features are constructing a unique version of the crate in question that is distinct from the same version of the crate without the feature. In theory (though maybe not in practice), cargo should be able to compile multiple instances of one crate, since it already allows building multiple major versions of the same crate. Could we perhaps re-use that logic here?

At least in my view of what mutually exclusive features are used for, building a crate twice with different mutually exclusive features seems not particularly useful. Typically the most common sort of mutually exclusive option is things like choosing 1. which backend or implementation to use for some crate or 2. how to link to some library. Both of those situations aren't decisions that their direct reverse dependencies typically care about, but it does matter to the top level binary crate and the user building it. Therefore what I think the solution should be is adding support for features that are chosen by the top level crate and not the direct reverse dependencies and allowing mutually exclusive features as part of them. As well there should probably be some way for crates to learn what features are enabled in their dependencies so they can automatically adapt to the situation.

Possibly, though I think both use-cases are common. In the example I linked above for example, the feature enables a different resizing strategy for hash tables. You could imagine that one "part" of an application needs the performance characteristics of that alternative strategy, but another "part" would use prohibitively much memory if that alternative strategy is used. At the moment, users can only opt into the feature on a global basis, if any part of their dependency tree uses the feature, which seems unfortunate.

Why not let features provide some kind of functionality/capability/tag? If a feature does, it must be the only one in that category:
The following is just an example:
[features]
foo = []
bar = []

[features.foo]
provides = ["impl"]

[features.bar]
provides = ["impl"]

Only one provides=impl must be active at a time. Everything else would be a build failure.
This could be done on a global, or local level:
[features]
foo = []
bar = []

[features.foo]
provides = ["impl"]
provides-globally = ["global-impl"]

[features.bar]
provides = ["impl"]
provides-globally = ["global-impl"]

In the latter example, it would be possible for a different crate in the build tree to provide impl", while only one crate in the build tree may provide global-impl.

That's not a bad proposal, but I think it would need an RFC to hash out all the details and gain consensus before it's really implementable.

That's not a bad proposal, but I think it would need an RFC to hash out all the details and gain consensus before it's really implementable.

Yes, I think this should be though through a bit more. I can prepare an RFC in a fork of the https://github.com/rust-lang/rfcs repository, for previewing, if that helps.

I can prepare an RFC in a fork of the https://github.com/rust-lang/rfcs repository, for previewing, if that helps.

Once you have a rough draft, you may also want to consider opening a discussion over at the Language Internals forum. Thank you for being willing to work on this.

@thomcc @tapeinosyne I started to work on an RFC. It is a work in progress, and still has some "to be written" markers. Thus I think it is too early to share it with the forum. I would welcome some early feedback though and will continue on this in the next few days.
Link: https://github.com/ctron/rfcs/tree/feature/cargo_feature_caps_1

I made some more progress on the RFC. I think it is a rough enough draft to post it to the forum now.

@jonhoo I have a very similar use-case.
For spin we have an optional std features that does thread yielding instead of spinning to prevent priority inversion. The problem with this is that crates that that require spinning and cannot correctly perform yielding may have this feature arbitrarily enabled by other instances of the crate in the dependency tree. In this case, it makes the most sense for different instances of the crate with different feature sets to be compiled into the final binary.

@jonhoo it seems to me that generics are a more appropriate solution for such scenario although admittedly more tedious to implement. However, generics can offer much better outcome - they can still share some reasonable code such as error types.
If this happens often and there's a specific problem with generics I'd suggest to improve generics instead.

If this happens often and there's a specific problem with generics I'd suggest to improve generics instead.

I think the only proposal that would be of sufficient conciseness is module level generics.
I agree that most likely we will not need both mutually exclusive features and module level generics. But at least one of them is necessary to preserve some sanity for library developers when offering implementation options that are very orthogonal to other code, since adding a generic flag to almost every single type in a module is somewhat maddening.

I think the only proposal that would be of sufficient conciseness is module level generics.

I agree, note the author of that pre-RFC. ;)
IMO generics should be used for algorithm tuning while mutually-exclusive features would make sense for choosing e.g. library linking. One property of mutually-exclusive features that should be present is being able to set them from the binary crate without intermediate dependencies having to reexport it.
In other words, if A depends on B which depends on C, which has a mutually exclusive features foo and bar, then A must be able to set these features without B having to write any supporting code at all. B should completely ignore that C even has mutually exclusive dependencies. Possibly with the exception of tests in B.

Any progress? It is really helpful to address the problem of selecting an async runtime for a lib.

Of course, this would be a very useful thing to have, but for your case, if you already have the code for the different options or are planning to write it, why make it mutually exclusive? What is the argument against making both available conditionally? Unless you're using library-global state, it shouldn't really make a difference, right? Or am I missing something obvious here?
-------- Original Message --------
On Sep 30, 2021, 05:26, Zan Pan wrote:

Any progress? It is really helpful to address the problem of selecting an async runtime for a lib.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Another motivating use case here is that in the absence of a way for cargo to know that two features are mutually exclusive, there's no way to express the multiple-dependency-versions pattern (e.g. https://github.com/TrueLayer/reqwest-middleware/blob/main/reqwest-tracing/Cargo.toml) with a package that specifies the links field in Cargo.toml.

Summary
Use cases

In Windows API there is the notion of a family and partitions. Your choice of family is basically which platform you are targeting and there is a choice between WINAPI_FAMILY_DESKTOP_APP WINAPI_FAMILY_PC_APP WINAPI_FAMILY_PHONE_APP WINAPI_FAMILY_SYSTEM and WINAPI_FAMILY_SERVER. Y
Controlling vendored or system library
Rendering backend
Classic C implementation vs Rust rewrite
Backend version (LLVM, Lua, etc)
Async runtimes
As an alternative to module level generics.

inlining size
Some use cases like this would be better handled by allowing multiple instances of a crate, rather than unifying them (comment)
See also spin

Other discussions

https://github.com/rust-lang/cargo/issues/5653
https://internals.rust-lang.org/t/mutually-exclusive-feature-flags/8601
https://github.com/ctron/rfcs/blob/feature/cargo_feature_caps_1/text/0000-cargo-mutex-features.md

Related prior art

https://docs.bazel.build/versions/0.26.0/cc-toolchain-config-reference.html#feature-relationships
https://docs.gradle.org/current/userguide/feature_variants.html#sec::incompatible_variants
https://docs.gradle.org/6.0.1/userguide/dependency_capability_conflict.html
https://kotlinlang.org/docs/reference/platform-specific-declarations.html

Proposals
Conflicting features
https://github.com/rust-lang/cargo/issues/2980#issuecomment-270554758
[dependencies.awesome]
version = "1.3.5"
features = ["!secure-password", "civet"]

Feature values
https://github.com/rust-lang/cargo/issues/2980#issuecomment-587584817
[features]
llvm="9"
flate2="zlib"
winapi_family="desktop_app"

Provides
https://github.com/rust-lang/cargo/issues/2980#issuecomment-700687022
[features]
foo = []
bar = []

[features.foo]
provides = ["impl"]

[features.bar]
provides = ["impl"]

Only one provides=impl must be active at a time. Everything else would be a build failure.

See also https://github.com/ctron/rfcs/blob/feature/cargo_feature_caps_1/text/0000-cargo-mutex-features.md

Did a recent brainstorming discussion on this.
A key aspect we narrowed in on is that most of the use cases are really meant to be decided by the final binary and it is not ergonomic to bubble these up to the final binary.  I've experienced this myself where cargo release had to add expose a vendored-openssl feature because a dependency used git2 with openssl and users of the binary need to control vendoring (or not).  See also #9094.
We had the idea of "global features".
Care abouts

Mutually exclusive feature
Not piping up features through the entire stack
Coarse and fine-grained control (vendor all vs vendor specific)

High level

Defaulting so as not require each target to set it

Ideal: don't require app author to set the value
Ideal: don't require the user to set the value

Questions

How do we do coarse grain support?
Are mutually exclusive features open set (provides, requires) or closed set (variants)
What degree of error reporting (undefined features, undefined variants) do we support?
Distributed definition or a crate specifically defines a global feature?

If distributed, how does default variant work?
If crate-specific, how do we handle migrations across breaking changes?
If crate-specific, how much of a pain will it be to handle multiple crate versions within the dependency graph

... I feel like there were more points but I'm not finding it in my notes.

For vendoring/system libs choice, I think the use case deserves a first-class feature. This is partially solved by being able to override build scripts. The missing part is that build scripts may need to also generate code (bindgen), so disabling them entirely doesn't help.

Keep in mind that currently feature values are Vec<InternedString>, so feature values approach would prevent feature dependencies from being used AFAICT and be prone to user error:
my_feature = "dep:bytemuck" # unintended wrong use
my_feature = ["dep:bytemuck"] # what was intended

And this would effectively be the same as passing rustc-cfg from a build script except maybe being more trustworthy?
I think provides covers most current and future use cases where feature values would be:
#[derive(Default)] // default is the current `[]`
struct FeatureDetails {
  /// list of
  dependencies: Vec<FeatureValue>,
  /// Name for mutual exclusion
  provides: Option<InternedString>,

  // ... future details ...

  /// List of features and dependencies disabled when this feature is active
  // disable: Vec<FeatureValue>,
}

And constructor could take arguments currently passed to build_feature_map in a form of fn new(deps: impl AsRef<Dependencies>, value: toml::value::Value) and then match for backwards compatibility.

I've created a Pre-RFC for mutually-exclusive, global features.


I'm using the a2dp_sink from ESP_IDF, How to use esp_avrc_feature_flag_t function? (IDFGH-10648)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I'm already made a pre-configuration for this example work fine, but my objective is bring this data from cell phone:
ESP_AVRC_FEAT_FLAG_COVER_ART_GET_IMAGE_PROP = 0x0080     //  Cover Art GetImageProperties
ESP_AVRC_FEAT_FLAG_COVER_ART_GET_IMAGE = 0x0100     //  capa Art GetImage */
ESP_AVRC_FEAT_FLAG_COVER_ART_GET_LINKED_THUMBNAIL = 0x0200      //  Cover Art GetLinkedThumbnail
Every help is welcome!

Good morning @xiongweichao.
So this this function exists on ESP_IDF but isn't usefull yet?
I'm just trying to understand.
graciously.

@leonardokucarz  ESP-IDF does not support OBEX temporarily, so this function is not supported.

@xiongweichao thank you for this explanation.

Did anything change regarding the support of cover art?

@drabaioli I'm very sorry that this feature is still not supported.

Hi, @leonardokucarz @drabaioli
AVRCP cover art feature is now supported as of commit https://github.com/espressif/esp-idf/commit/cda2846558d10cd8a8190e69a2facfb4e57bec54 in the esp-idf master branch. This feature will be included in the upcoming 5.4 release. For usage instructions, you can refer to examples/bluetooth/bluedroid/classic_bt/a2dp_sink demo.
esp_avrc_feature_flag_t is a set of bit masks defined according to the Bluetooth AVRCP specification, used to determine whether the remote device supports specific features:
https://github.com/espressif/esp-idf/blob/3c99557eeea4e0945e77aabac672fbef52294d54/examples/bluetooth/bluedroid/classic_bt/a2dp_sink/main/bt_app_av.c#L473-L477
If you have any other questions, please feel free to ask.

Thanks for reporting, feel free to reopen.


Reference request

I'm a maplestory fan from china, I create a website about maplestory's music, and need some data about this database, so can i use?

Sure, feel free to use the database! I am currently using the database to power my site.

Sure, feel free to use the database! I am currently using the database to power my site.

Great & THX!


Set database=False in SynapseRelation.include_policy instead of overriding ref macro

Hi! I'm one of the folks who helps maintain dbt-core.
We noticed while debugging some failures in our automated tests that dbt-synapse overrides the ref macro here:
https://github.com/microsoft/dbt-synapse/blob/8f4a6a3ab82ea20652bc162b0acbaee461702445/dbt/include/synapse/macros/materializations/models/materialized_view/create_materialized_view_as.sql#L1-L5
This isn't the right way of achieving the desired behavior (rendering relations without the database identifier), and it precludes users from being able to specify two-argument ref.
Instead, if the goal is to render relations without a three-level hierarchy — schema.identifier instead of database.schema.identifier — dbt-synapse should do what dbt-spark does. Something like:
@dataclass
class SynapseIncludePolicy(Policy):
    database: bool = False
    schema: bool = True
    identifier: bool = True

@dataclass(frozen=True, eq=False, repr=False)
class SynapseRelation(BaseRelation):
    include_policy: Policy = field(default_factory=lambda: SynapseIncludePolicy())

@prdpsvs would you be able to take a look at this?

so I found out why ref was overridden and why within create_materialized_view_as.sql of all places.
The Create Materialized View as Select (CMVAS) statement in Azure Synapse does not support three-part names in either the name of the materialized view or any table or view mentioned within the SELECT statement.
Materialized Views in Azure Synapse cannot re I get the following error when executing TestMaterializedViewsBasicSynapse:

Names must be in two-part format

Database Error in model my_mv (models/my_mv.sql)
  ('42000', "[42000] [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]
Cannot schema bind view 'test.my_mv' because name 'dbtmsft.azsyn.cipool.test.my_seed' is invalid for schema binding.
Names must be in two-part format and an object cannot reference itself.
(4512) (SQLExecDirectW)")

another update -- this isn't just a limitation of materialized view. it's all of Azure Synapse.
Accordingly, there are in this adapter

10 instances of relation.include(database=False) and
4 instances of [{{relation.schema}}].[{{relation.identifier}}]

Once the Relation class is properly implemented, all 14 of those can simply be relation. More to come tomorrow


[LocalNav] Resize content window based on LocalNav expanded state

is it possible to automatically resize the main content window if the LocalNav is in expanded state?
maybe by providing UIShell with the state of the LocalNav

Hi there. That actually is exactly what the UI Shell does. You would be able to see it in Storybook, except the Local Nav no longer has pin open functionality in the latest release where it was redesigned, 1.10.x, so this is no longer relevant.


Delete Event Notification to have tag name

I tried configuring the notifications with Docker Registry 2.4.0 and ab able to capture the events but the delete event is having the digest and does not have any reference to the tag name. Is there any way to get the tag name in the delete event? I am looking for capturing this from audit logging standpoint as users may be more familiar with the tag name than digest.

The delete API operates on digests, not tags.  The only information available at the event time is the digest.

Understandable. Is there anyway you can think of to get the tag name for delete event(Anyway using the sha to get it from registry)? Just trying to see if this can be captured for audit logging.

Manifest Put events will tell you when the tag has changed and give the digest for it.  If you track this data you can reconcile it with the hash in the delete event.


feat (tools): additional tools in sql toolkit

Which issue(s) does this pull-request address?
https://github.com/i-am-bee/bee-agent-framework/issues/182
Description
This feature proposal introduces a toolkit for SQL and data analysis, by enhancing current SQL tool and introducing few other concepts
It adds excel and csv support for SQLTool in order to perform advanced querying on these type of files.
It also adds the ability to provide few shot examples for the connect db, useful for bigger complex dbs.

TODO:
tests
improve search values action
add embedding based schema linker
correction

Checklist

[x] I have read the contributor guide
[x] Linting passes: yarn lint or yarn lint:fix
[x] Formatting is applied: yarn format or yarn format:fix
[x] Unit tests pass: yarn test:unit
[x] E2E tests pass: yarn test:e2e
[x] Tests are included
[ ] Documentation is changed or added
[ ] Commit messages and PR title follow conventional commits

Closing in favor of https://github.com/i-am-bee/bee-agent-framework/pull/212


Notifier: smtp_config tls boolean not respecting 'false' when creating through api/terraform

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Create a basic email notifier, with tls boolean set to false:
 resource "rancher2_notifier" "email" {
   name = "email"
   cluster_id = "c-cmwc8"
   description = "test snmp notifier"
   smtp_config {
     default_recipient =<EMAIL_ADDRESS>     host = "<IP_ADDRESS>"
     port = 587
     sender = "test"
     password = "test"
     tls = false
   }
 }

Result:
Notifier TLS is still set to its default 'true', in UI and api
"smtpConfig": {

    "defaultRecipient"<EMAIL_ADDRESS>    "host": "<IP_ADDRESS>",
    "password": "test",
    "port": 587,
    "sender": "test",
    "tls": true,
    "type": "/v3/schemas/smtpConfig"

},

Other details that may be helpful:
Environment information

Rancher version: v2.3.5
Installation option (single install/HA): both

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

> kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T17:01:15Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:22:30Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:34 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

This issue is affecting rancher/types client. It's related with golang Marshal function from encoding/json that omits false bool if omitempty is set in the field definition, https://github.com/golang/go/issues/13284#issuecomment-157288425
Submitted PR https://github.com/rancher/types/pull/1083 to fix it.

I reproduced the issue in Rancher master-head (06/04/2020) 7e5b59b4e. I will check in a more recent build and then work in the v2.4-head build.

This is still setting tls = true in Rancher v2.4.5-rc2 shown in API and UI.
"smtpConfig": {
"defaultRecipient"<EMAIL_ADDRESS>"host": "<IP_ADDRESS>",
"port": 587,
"sender": "test",
"tls": true,
"type": "/v3/schemas/smtpConfig"
},

Basically I used the same terraform rancher2_notifier resource as described in this issue:
 resource "rancher2_notifier" "email" {
   name = "email"
   cluster_id = rancher2_cluster.foo-do2.id
   description = "test snmp notifier"
   smtp_config {
     default_recipient =<EMAIL_ADDRESS>     host = "<IP_ADDRESS>"
     port = 587
     sender = "test"
     password = "test"
     tls = false
   }
 }

@izaac , you can't test this issue using terraform provider, due it's not patched yet. You should use rancher API to test it

Patched rancher2 terraform provider on PR https://github.com/terraform-providers/terraform-provider-rancher2/pull/362

@rawmind0 I didn't notice this was a two part fix for the terraform provider.
This is working building the provider from the PR you mentioned in Rancher v2.4.5-rc2 I will check Rancher master next.

Yes, building tf provider from PR should work fine for every Rancher version

Working also in Rancher master-head (06/05/2020) commit 9f6da9ed1

I will validate the other three fields that where fixed in the PRs
https://github.com/rancher/types/pull/1083
https://github.com/rancher/types/pull/1149

IgnoreDockerVersion on rke_types
UseInternalIPAddress on NodeCommonParams and IgnoreDaemonSets on NodeDrainInput on machine_types
Compress on FluentForwarderConfig on logging_types

I was able to validate the three other fields fixed in the Rancher types PRs.
Terraform Provider build locally from: https://github.com/rancher/rancher/issues/25321#issuecomment-639582364
Rancher versions used:

v2.4.5-rc2
master-head (06/05/2020) commit 9f6da9ed1

Fields validated using Terraform Provider:

IgnoreDockerVersion on rke_types
UseInternalIPAddress on NodeCommonParams
Compress on FluentForwarderConfig on logging_types

Fields validated using API directly (I couldn't find a way to do so with the TF provider).
-IgnoreDaemonSets on NodeDrainInput on machine_types
This field is in the cluster object:
"upgradeStrategy": {
    "drain": false,
    "maxUnavailableControlplane": "1",
    "maxUnavailableWorker": "10%",
    "nodeDrainInput": {
        "deleteLocalData": false,
        "force": false,
        "gracePeriod": -1,
        "ignoreDaemonSets": false,
        "timeout": 120,
       "type": "/v3/schemas/nodeDrainInput"
    },
},

I was able to switch the boolean values.


Research: Persistent state support options for fuseml-core components

We need to store the state stored in the fuseml core service in a form of persistent storage, to avoid problems that will occur when the fuseml-core service is restarted and the rest of the runtime state stored in the other components (gitea, tekton, docker-registry) doesn't match anymore.
This research should summarize the available options and prepare a high-level proposal (blueprint) based on which implementation stories will be created.
Options to be explored:

relational database
key-value stores
a combination of the previous two
file-system / persistent volume
kubernetes resources (e.g. secrets, configmaps)
kubernetes backed (i.e. re-designing the fuseml core as a k8s controller/operator)

Other considerations:

upgrades incl. schema migration
backwards-compatibility necessity
scalability
high-availability

Moving out of MVP scope due to time constraints and the fact that this is not a must have for MVP.

Next steps: @flaviodsr to update the research status, results and agreed approach.


Fix Uncaught TypeError: Cannot read property 'trim' of undefined

In one input I use react-autosuggest to display suggestions BEFORE the user start typing.
If this case if the user press down, I get:
Uncaught TypeError: Cannot read property 'trim' of undefined

This small change  the problem.

@ChrisCinelli I tried to reproduce the error you are getting here, but no luck.
Which version of react-autosuggest are you using?
Could you please create a Codepen that demonstrates the issue?

Closing for now, but happy to reopen once a reproducible Codepen is provided.

I'm having the same issue on<EMAIL_ADDRESS>with the same line of code as ChrisCinelli, when first typing into the input.
Uncaught TypeError: Cannot read property 'trim' of undefined
var renderSuggestionData = {
  query: (valueBeforeUpDown || value).trim()
};```

Sorry but I don't have a codepen to reproduce and don't have time to make one right now. If I discover the cause I will update this.


removes a warning that occurs under XCode 8.3.1 regarding using a nil…

… value as a non-nil required argument

@Darkseal Any plans to merge this?


autopan centres clicked marker rather than moving map just enough for infobubble to be visible

Under the current infobubble.js code the 'autoPan' feature is very basic - simply centering the selected / clicked marker, rather than moving the map just enough to make the infobubble visible.
Compare the following jsfiddles :

Using the standard google.maps.InfoWindow() - http://jsfiddle.net/goredwards/3r7r1zkq/
Using the current infobubble.js code - http://jsfiddle.net/goredwards/v9934fqm/

...you may have to move the map to have the marker near the edge to see the autopan effects.
The part of the code that's problematic is the panToView() function which contains code to
effectively centre the map on the selected pin.
This might be fine for very small maps, but on larger maps is completely unnecessary and frankly has an annoying effect that can't be useful in many circumstances.
Was there a plan to update this part of the code to be more in line with the far superior performance of the standard google.maps.InfoWindow() autoPan feature ?

PR #14 updates the autopan functionality to bring it inline with (ahead of ?) the standard google.maps.InfoWindow() autopan:

so map is only panned enough for the infobubble window to be visible with an edge margin - as per
adds an autopanMargin option to set the margin between the map edge and the infobubble window (with default = 10px)

see updated code working here: http://jsfiddle.net/goredwards/2cs4puaz/
...feel free to modify the autopanMargin: 15 option in the infobubble definition to see how the margin works (you can even put negatives)

I know that this repository is unmaintained but autopanMargin seems like a very useful option -
does anyone know if there are plans to incorporate such an option in the main Google Maps InfoWindowOptions object?
I'm seeing an excessive amount of left margin and would love to be able to minimize that:

Thanks.


Histograms and plotting

This should in principle obviate histbook.  Consider the Hist definition and filling implementation somewhat stable.

@nsmith- when you've got your gallery notebook setup lemme know. I want to poke at it.

So currently slices on dense axes can only be integrated out, any other operation will de synchronize the axis definition with the ndarray.  I'll fix it, but for now we have at least a working demo of most of the things we need.

Ok I'm happy with the functionality here.  I think the core class is stable enough to be put to work.
No complaints, I'll merge

Nope no complaints. I played around with the notebooks, this is a very good direction.
I'll definitely be switching once I get the ggHbb more or less implemented.
Currently working on the muon control region, jet systematics after that.


convert tests from #file to using #filePath

I wandered in an saw a variety of warnings, this iterates through and cleans them up. I wasn't sure of dependencies for supporting older versions of swift for this project, so offering this up as cleanup work.

converted the use of #file to #filePath in the tests

I guess this won't work because Package.swift still has // swift-tools-version:5.1. I've attempted to work around that in #303 previously, but I think the consensus was that we just wait for next 5.3 snapshots that will no longer have the warning.

@swift-ci please test

No need to close it yet, I may have been wrong, let's see if CI passes.

Our CI only tests with master swift, but we want to support building with the latest released toolchain as well as much as possible for convenience. We should be able to land this PR once 5.3 is released.

The Swift project moved the default branch to main and deleted master branch, so GitHub automatically closed the PR. Please re-create the pull request with main branch.
More detail about the branch update - https://forums.swift.org/t/updating-branch-names/40412

rebased and re-opened as #326 against branch main


Spanner C# Driver - NPE Exception.

Code:
var spannerCommand =  spannerConnection.CreateInsertCommand("TableNameHere", spannerParameterCollection);
return await spannerCommand.ExecuteNonQueryAsync();
Error:
at Google.Cloud.Spanner.V1.TransactionPool.SessionInfo.d__21.MoveNext() in C:\Users\benwu\spanner\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Spanner.V1\Google.Cloud.Spanner.V1\TransactionPool.cs:line 273
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Google.Cloud.Spanner.V1.TransactionPool.d__5.MoveNext() in C:\Users\benwu\spanner\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Spanner.V1\Google.Cloud.Spanner.V1\TransactionPool.cs:line 82
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Google.Cloud.Spanner.Data.SpannerConnection.<>c__DisplayClass68_0.<b__0>d.MoveNext() in C:\Users\benwu\spanner\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Spanner.Data\Google.Cloud.Spanner.Data\SpannerConnection.cs:line 728
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Google.Cloud.Spanner.Data.ExecuteHelper.d__21.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Google.Cloud.Spanner.Data.EphemeralTransaction.<>c__DisplayClass5_0.<<ExecuteMutationsAsync>b__1>d.MoveNext() in C:\Users\benwu\spanner\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Spanner.Data\Google.Cloud.Spanner.Data\EphemeralTransaction.cs:line 64 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Google.Cloud.Spanner.Data.ExecuteHelper.<WithErrorTranslationAndProfiling>d__21.MoveNext() in C:\Users\benwu\spanner\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Spanner.Data\Google.Cloud.Spanner.Data\ExecuteHelper.cs:line 70
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Google.Cloud.Spanner.Data.SpannerCommand.d__53.MoveNext() in C:\Users\benwu\spanner\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Spanner.Data\Google.Cloud.Spanner.Data\SpannerCommand.cs:line 420
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at NG.EntityFramework.Spanner.Storage.SpannerDatabase.d__7.MoveNext() in C:\Users\alyaros\Downloads\main-20171224_orleans2\Data\NG.EntityFramework.Spanner\Storage\SpannerDatabase.cs:line 84

Thanks for the report. Any other relevant information? What parameters are you supplying, for example?

(I'll let Ben assign a priority when he's looked at it. Please bear with us if it takes a bit longer to diagnose over the holiday period... I know I'm not working again until January; I don't know if Ben is in the same situation.)

looks like this problem arise only when I'm trying to perform multiple inserts. (It fails on the second insert)

Hey,
We changed our EF driver to use ADO for Read path and V1 for Write Path.
The problem I mentioned in this ticket was related to the Write Path via ADO which I'm no longer using - so I have no new input on this issue. If it does not occurred for others and based on the inputs above I think we close this ticket.

Fine by me - we can always reopen it if anyone else reports a similar issue. Thanks for getting back to me.


Antique Mall results for 'kearney'"

More Info
Source URL: https://www.antiquemalls.com/search?SearchTerm=kearney
BrowserChrome 57.0.2987.133Screen Size1920 x 1080Viewport Size1936 x 1056Zoom Level100%Pixel Ratio@1xOSWindows 10User AgentMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

This is intended behavior. It's showing the metro area result even though there are no malls. Estate Sales does the same thing. https://www.estatesales.net/search/Kearney

https://www.estatesales.net/search/Kearney

I just realized this issue is opened in the wrong repo anyway. Closing...


Wrong/Broken links

The link to install .NET Core 3.1 SDK leads to the WINDOWS installer. It should be the cross-platform installation.

The link to "set up the environment" (which points to https://review.docs.microsoft.com/en-us/azure/media-services/live-video-analytics-edge/detect-motion-emit-events-quickstart?branch=release-preview-media-services-lva#set-up-the-environment ) is broken.

NEW- there is not information on how to obtain and where to copy the camera-300s.mk file, so the sample doesn't run.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bd4faa47-7e66-b3f5-1100-eeed4222fece
Version Independent ID: 5de49fd7-8242-f5bd-0e1c-a2e24bae777d
Content: Event-based video recording to the cloud and playback from the cloud tutorial - Azure - Live Video Analytics on IoT Edge
Content Source: articles/media-services/live-video-analytics-edge/event-based-video-recording-tutorial.md
Service: media-services
Sub-service: lva-edge
GitHub Login: @Juliako
Microsoft Alias: juliako

@lokijota Thanks for the feedback! We are currently investigating and will update you shortly.

Added note:
NEW- there is not information on how to obtain and where to copy the camera-300s.mk file, so the sample doesn't run.

@lokijota Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

https://docs.microsoft.com/en-us/azure/media-services/live-video-analytics-edge/event-based-video-recording-tutorial currently 404s, same behavior for the GitHub source file as well.
In https://docs.microsoft.com/en-us/azure/azure-video-analyzer/video-analyzer-docs/edge/record-event-based-live-video the .NET link goes to a cross-platform page and

"set up the environment"  is no longer a link on the page

There is still no guidance for camera-300s.mk and where to retrieve it from

#please-close see https://docs.microsoft.com/en-us/azure/azure-video-analyzer/video-analyzer-docs/transition-from-video-analyzer


penman.EncodeError: Invalid graph; possibly disconnected.

Hi,
during prediction I met this error, have you met it before?

File "/home/yaosw/anaconda3/envs/stog/lib/python3.6/site-packages/penman.py", line 250, in encode
return self._encode_penman(g, top=top)
File "/home/yaosw/anaconda3/envs/stog/lib/python3.6/site-packages/penman.py", line 493, in _encode_penman
raise EncodeError('Invalid graph; possibly disconnected.')
penman.EncodeError: Invalid graph; possibly disconnected.

Hi! I do think I recall encountering this error about a week back.
As stated it is about format of the AMR-graph. Are you using your own dataset? I think my error arose from these two reasons:

I had a white-space at the beginning of one of my amr-graphs. (in stog/data/AMR//data/amrs/split/dev/dev.txt)

I had an amr-graph with more than one root/top/head. E.g.
Incorrect:
(g / give-01
:ARG1 (e / email-address-entity)
:ARG2 (i / i))
(p / person :name (n / name :op1 "Allan" :op2 "Rickman")
:poss-of e)
Correct:
(g / give-01
:ARG1 (e / email-address-entity
:poss (p / person :name (n / name :op1 "Allan" :op2 "Rickman")))
:ARG2 (i / i))

Yes, I use the data generated by my model... so it may because the model generates something wrong. I will check it, thank you!


[Question]: ERROR: No matching distribution found for Aspose.Slides==24.2.0

Describe your problem

ERROR: Ignored the following versions that require a different python version: 21.11 Requires-Python >=3.5,<3.10; 22.1 Requires-Python >=3.5,<3.10; 22.10.0 Requires-Python >=3.5,<3.11; 22.11.0 Requires-Python >=3.5,<3.11; 22.12.0 Requires-Python >=3.5,<3.11; 22.4.0 Requires-Python >=3.5,<3.10; 22.6.0 Requires-Python >=3.5,<3.11; 22.7.0 Requires-Python >=3.5,<3.11; 22.8.0 Requires-Python >=3.5,<3.11; 22.9.0 Requires-Python >=3.5,<3.11; 23.1.0 Requires-Python >=3.5,<3.11; 23.10.0 Requires-Python >=3.5,<3.12; 23.11.0 Requires-Python >=3.5,<3.12; 23.12.0 Requires-Python >=3.5,<3.12; 23.2.0 Requires-Python >=3.5,<3.11; 23.3.0 Requires-Python >=3.5,<3.11; 23.4.0 Requires-Python >=3.5,<3.11; 23.5.0 Requires-Python >=3.5,<3.12; 23.6.0 Requires-Python >=3.5,<3.12; 23.7.0 Requires-Python >=3.5,<3.12; 23.8.0 Requires-Python >=3.5,<3.12; 23.9.0 Requires-Python >=3.5,<3.12; 24.1.0 Requires-Python >=3.5,<3.12; 24.2.0 Requires-Python >=3.5,<3.12; 24.3.0 Requires-Python >=3.5,<3.12; 24.4.0 Requires-Python <3.12,>=3.5; 24.5.0 Requires-Python <3.12,>=3.5
ERROR: Could not find a version that satisfies the requirement Aspose.Slides==24.2.0 (from versions: 24.6.0)
ERROR: No matching distribution found for Aspose.Slides==24.2.0

When I start ragflow locally according to the following command, I encounter the above error, should I adjust the version of python?
$ git clone https://github.com/infiniflow/ragflow.git
$ cd ragflow/

$ conda create -n ragflow python=3.11.0
$ conda activate ragflow
$ pip install -r requirements.txt

my conda version = 24.4.0

What about: python -m pip install --upgrade pip

We've replaced pip with poetry. Poetry is much better on dependency management and download speed.


This provider isn't production ready / this provider has big issues

Terraform Version
Terraform v0.15.4
on linux_amd64

Namecheap provider version
robgmills/namecheap 1.7.0
My goal
The goal is not to be mean, but to make the maintainers realise (if they don't already) how bad this provider is, from the perspective of a user.
Also, this does not look like some sort of open source project with maintainers that work for free, this is direct from the namecheap github org, so I expect much better than this.
Issues

Why do I need to give my IP ? Can't the namecheap server figure it out ?!
Why do I have to create terraform.sh:NAMECHEAP_IP="$(curl -s ifconfig.me)" terraform $@

Could not find the record with hash 123456789 happens all the time ! I can't trust this thing to run unsupervised, it's faster to use the web app because at least I know it won't crash !
Why do I need to use robgmills/namecheap ? Isn't the git repo namecheap/terraform-provider-namecheap ?
Why am I running v1.7.0 when the latest release on namecheap/terraform-provider-namecheap is 1.6.0 ?
Knowing how buggy this thing is, why is it at 1.7.0 and not 0.1.7 ? Why isn't there a disclaimer "not ready for production use" ?

Hi @awoimbee
Thanks for interest and report. Much appreciated.
We just transfered this repo under our support in less than 1 week and just about to start a complete revision, refactoring, wrapping with a correct tests and general stabilisation.
Please bear with us, we will update you ASAP. Probably @StyleT will add a few words

(Speaking as an individual, I'm not affiliated with Namecheap)
I started this project after needing to set a couple DNS records with namecheap. I found a Go library someone else wrote, adopted it and built this provider to my personal needs. After a couple years of volunteering support on nights and weekends I offered it to Namecheap who accepted it last week because my day job needed most of my energy. Namecheap is working on making the provider awesome, but you'll need to give them patience and come with a better attitude.

Thanks for the quick and professional responses. I changed the title for something more suitable (the original one did its job of getting a reaction).
Thanks for creating this provider. While I think it's not ready yet, I still think it's very cool that it exists.
The original issue about this provider working 1/3 times, having no disclaimer that it's not ready, and the weird situation with the README telling users to install robgmills/namecheap still stands tho.

@awoimbee Anyway, thanks for reporting any issues, that will help us to figure out faster and understand the current state of things

I suppose that some/all of the issues should be addressed in #46

@awoimbee thanks for your patience and report.
We have been published our new v2 major release, please have a look
https://registry.terraform.io/providers/namecheap/namecheap/latest/docs
The only issue from your list that requires additional consideration is the client IP address exposure. We will return to this point soon.
Right now I'm closing the issue.

@ifree92 did you end up returning to the IP issue? The IP issue is really a problem since we can't run in a CI/CD. We had to completely disable + delete Namecheap from our state, because of this :(


fix method typo in The Things I Do For Love

returnCardsToHand() -> returnCardToHand()
Fixes THRONETEKI-XS

closing as already fixed by @ystros in #1134


Signal to docs repository on release

Workflow that triggers our documentation workflow in our other repo on release. This will automate one more step of the release process.

@ifranda Hey Ian, I thought the VaporDocumentationWebsite watched this repository for new releases in order to trigger the docs rebuild.  Is that not true?  If true, why is this needed?

Unfortunately I think the way actions are set up means that an action can only watch for a trigger in its own repository, so if we want to run the documentation workflow automatically we'll need a workflow here to pass along the signal.
But automating this doesn't save that much time -- we can always run the documentation workflow manually just by clicking a button and it takes just ~5 minutes to run. And if we want to manually review the PR it creates it'll take some manual work anyway. What are your thoughts on this?

Unfortunately I think the way actions are set up means that an action can only watch for a trigger in its own repository, so if we want to run the documentation workflow automatically we'll need a workflow here to pass along the signal.

Interesting.  I thought the docs were auto-generated in this commit by the GHA[bot] since you were on PTO.  So I guess this was manually generated by yourself?

But automating this doesn't save that much time -- we can always run the documentation workflow manually just by clicking a button and it takes just ~5 minutes to run. And if we want to manually review the PR it creates it'll take some manual work anyway. What are your thoughts on this?

I'd say always automate stuff like this.  If the work is a one-off job then sometimes doing it manually is easier, but we will be needing to do this repeatedly on each release.  We'll still need to add an action item to verify the website, so I'll do that now.
Another helpful contribution Ian.  Thank you :)

Interesting. I thought the docs were auto-generated in this commit by the GHA[bot]

I manually went in to trigger the workflow and merge the PR for this but it only takes a few minutes.
On a side note, we can also manually trigger the documentation workflow to generate the docs when we make a documentation update! There might be cases where this is beneficial since it's generated on a remote linux machine and always uses the latest conda releases for the sphinx packages.


User put fix

Q&A, Review, Note pen_name when not anonymous, changes when author's user_name updates.

Why does the branch name not follow the coding guideline?

The review-card-share branch

Included this work in #211 PR


Remove any chance of incorrect score handling due to missing entries in score_process_queue

While working through the import process today to ensure we have everything covered, I realised that the previous fix I made for  ensuring scores are processed was insufficient due to the null allowance. Because score submission in web-10 is not done within a transaction, there's a window of time where rows are in osu_scores_high but not in score_process_queue.
To resolve this, we need to assume two modes of operation:

Batch processing, when StartId is non-null, which will now process from the specified ID up to the last entry in osu_scores_high which doesn't have a score_process_queue entry (generally two days before current time, due to partition cycling).
Live mode, when StartId is null, which will now process only entries with a score_process_queue entry.

I haven't tested this yet, PRing for feedback in the mean time.

Just so I understand, I basically need to now specify --start-id=0 every time I need to do processing? i.e. https://github.com/smoogipoo/diffcalc-sheet-generator/blob/170990b323cb421e0a969d14c3a6ee3730858abc/docker/importer/start.sh#L29-L38

Just so I understand, I basically need to now specify --start-id=0 every time I need to do processing?

Yep, and remove exit-on-completion.


Fix wrong wording

Was saying:
"This is the approach that we will use for building our OS kernel"
if my understanding is correct, should say:
"This is not the approach that we will use for building our OS kernel"

I agree that the wording is a bit confusing there. What I meant to say is that we will use a bare-metal target instead of passing certain linker arguments (the next section). So we do use that approach, with a slight variation (a custom target).

Closing because I think that the current wording is correct. I'm happy to merge a PR to make this less confusing though.


Typo "Azure File storage"→"Azure File Storage"

https://docs.microsoft.com/en-us/biztalk/core/configure-the-file-adapter
#PingMSFTDocs

Duplicate #688 .
Closed #690 .


add context-linking to url links on code of conduct and add mailto links...

... on about page
Creates a context based link for the code of conduct page and adds the mailto links for the email addresses on the about page

Perfecto! :spaghetti:


[Page Layout] constrained-class does not work

constrained-class passes to AppContainer but the component does not use it in the template.
Layout:
https://github.com/nuxt-themes/docus/blob/1237388f0038efe11b85271578c2358638199d5c/layouts/page.vue#L7
Component:
https://github.com/nuxt-themes/docus/blob/dev/components/app/AppContainer.vue

@bdrtsky Indeed maxWidth solved the issue.

How should I pass this value for specific page? in front-matter?
---
container:
  maxWidth: ??
---

And what are the accepted values?

Interesting request, I am afraid modifying tokens from front-matter is not possible. And I am not sure you suppose to do that in general. Why would you change app container width per route? It feels weird when your layout jumps in width when you navigate. What you think @Tahul
As for accepted properties, it's all values CSS supports: 1028px, 50rem etc.


add fixation correction plugin

Hello! Please add this plugin for fixation correction. We are routinely using it in our lab. I hope it will be useful to someone else as well

Thank you for your contribution! 😊🙏
I am sure other users would find it valuable


Clarify the bs-callout on multiple open modals

[Fix #16502] Clarify the bs-callout on multiple open modals
Currently it states overlapping modals, this isn't the only case as this truly applies to any instance when a user would want to open multiple modals at the same time. For this reason, I have modified the title of the callout to make this more clear.

Fixed @cvrebert

Wanted to follow up on this and see if it was missing anything.


Parallelize tests

This is a follow-up to #58, where we found that we need some work done to xdist to make it usable for running Flintrock's acceptance tests in parallel.
Once that work is done, we'll be able to add a few options here and we should be all set.
Depends on https://github.com/pytest-dev/pytest-xdist/issues/18.

Another approach to parallelizing the acceptance tests -- which currently take upwards of 1 hour -- is to launch all the clusters we need in parallel within a shared fixture or something.
Upside: We can do this ourselves right now; no dependency on pytest-dev/pytest-xdist#18.
Downside: Running one acceptance test will spin up all the test clusters required by all the acceptance tests.


ROU-3076: Updating Namespace

This PR updates our API namespace to start having OutSystems.

Fixed most code smells. The ones still present are false positives, due to a known issue for sonar with Typescript:
https://github.com/SonarSource/SonarTS/issues/906


Game keeps crashing :(

Hi there! This appears to me after playing for about 10-15 minutes (one game day). I use some skin mods inside the world.img file.
I activated "CustomMemoryMgr = 1" to be able to see what type of error it was.
Without mods I get the same error but after an hour or so. I have Windows 10 64-bit.
How can i fix it?

Bully.exe.20210404213739.zip

I can't use any of these mods:

Mod selector
Not another selector
Without the game crashing all the time.
Nor can I play Bully without mods but with new skins because it also crashes.
I cannot make any modifications to the files:
PedPop
pedstats
Because the game also crashes.
Hey man, this game is an unstable cr@p ¯ \ _ (ツ) _ / ¯
In Windows 10 I can only play it without any mod but after an hour or more it crashes as usual.
I love this game very much but it makes me sick every time it crashes.

Will there be a patch in the future to correct these crashes?
Anyone there?

Hey there! amzy here, I do support for this patch.
A large part of your issue here is using mods - most of the mods you've mentioned are unstable/buggy in a lot of ways that can cause crashes, just due to bad script management.
Pedpop and Pedstats mods override base values and as such can cause issues as well.
Despite the readme saying Texture mods are okay, there's still quite a few that have issues. The AE Hud Mod is notorious for doing such a thing, and so I wouldn't be surprised if others are the same. I'm looking into testing everything that I have uploaded on bullymodding.xyz and eventually adding a "Compatible with SilentPatch" marker on each download in the future.
As for the crashes without any modifications, make sure you're running a completely vanilla retail 1.200 install, cracked or pirated versions can still cause a lot of issues, make sure that your copy is genuine.
Make sure you're also not running in any compatibility mode, or any weird sandbox form, this can also have adverse effects from previous testing.
If you still crash once these checks are in place, please upload the then most recent crashdump, and we'll look into your issue more deeply.
Many thanks,
amzy.

Oh hi amzy!
First of all I wanted to tell you that I have the Steam version of the game and that I had forgotten to mention that I also had the "HUD of the anniversary edition" mod installed as well: P
This time I reinstalled the game and just put the "Alex RK800" mods on it replacing the characters with their alpha / beta textures and I was able to play without problems.
In brief, the game crashed again as soon as I added:

The HUD of the AE, (Even if it's only the files that go in the TXD folder, not the ones that go in world.img.)
Any script mod. (especially to switch characters)
When I added my modified pedpop and pedstats files there were also crashes.
Even when I added my lightly modified trigger.img (population) file back the same thing happened.
When I placed my ide.img file with the bosses using their special moves.

Too bad, how I wish I could play the game without errors with all those modifications. At least for 10-15 minutes I can enjoy even for a little while.
I'll be uploading the dump files if it's useful to you :D
Thanks for answering me, best regards!

dump files.zip

Hello again!
I'm not surprised that it crashed considering the AE HUD mod, but I'm glad you could rectify that with the info provided.
I can't say I've ever heard of the game crashing that frequently with mods installed. One that doesn't crash the game for example, is my "OneHitKO" mod which you can download here
So please do try running completely Vanilla and giving that a shot.
The thing is with this game, is that by overloading it with a lot of mods, it can become unstable, especially where population is involved.
Your case is certainly unique, and considering you're able to provide crashdumps, I can probably safely assume you've installed it correctly (Although do make sure you're on Build 3, and not using an outdated build)
I'll continue to help look into this, and see if we can arrive at a conclusion, if not a solution.
Many thanks for the in-depth information!
Stay safe :)

Hello amzy!
I was finally able to find the cause of my constant crashes.
Unfortunately the cause is only any "script mod" (eg: not another selector mod, supermod, faction selector mod, selector mod remake).
What could I do to be able to use at least one mod that allows me to change to another character and to be able to modify the respect of the cliques without crashes?
Thanks a lot for helping me 😊


Incorrect version string in "Show RA Version" output

Using the latest rust-analyzer release (installed through .vsix, see Background), the "Show RA Version" command simply shows nightly, with no further details.
Background:
I'm using the OSS version of VSCode, which does not support the official marketplace. The alternate marketplace always gets the RA updates late, so I always use the .vsix file on the GitHub Releases page to install the latest version of rust-analyzer when it comes out.
VSCode OSS version info:
Version: 1.54.3
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-24T18:27:15.725Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.11.10-arch1-1

Rust-analyzer version (according to Rust Analyzer Client log): INFO [3/29/2021, 6:16:49 PM]: Extension version: 0.2.538
See https://github.com/rust-analyzer/rust-analyzer/issues/8224 for the discussion leading up to this issue.

What do the client logs say about the server version?

What do the client logs say about the server version?

The only information I can find regarding server version is
INFO [3/29/2021, 6:16:49 PM]: PersistentState: {
  lastCheck: undefined,
  releaseId: undefined,
  serverVersion: '0.2.538'
}

It's the same as the extension version. Is it supposed to be?

It is supposed to be the same yes and I think I know the problem. I imagine if you run the server with the --version flag yourself you will get the proper stable tag but we slice it too much in the vscode plugin so it disappears.

See #8495 for some additional information. It seems that the distributed RA executable simply reports "nightly" with the --version flag


refactor: moving to notebook

Moving all flow to a notebook and using the new experimental feature, rb.listeners, it works like a charm

Nice!! I will try to turn this into a small tutorial


TinyBMS Register Macros and STM32 CAN1 + USART2 Peripheral Driver Enable

Added Library header and source files for the TinyBMS to the project directory. In the Library header file, I created macros for all register and event messages found in Chapters 3 and 4 of the TinyBMS_Communication_Protocols.pdf manual. Adjusted the indentation and spacing to make TinyBMS.h more readable on GitHub. Edited the SHL_Pod_SecondaryBMS.ioc file (STM32 CubeMX software) to enable the CAN1 and USART2 peripherals for the STM32 Nucleo-F746ZG board (including those drivers in our project directory).

Looks great!


Change connection to connectivity, .lower on notebook

Fixes bug found in bug bash where SQL MIAA create is blocked by typo in notebook. Also convert connectivity mode to lowercase before comparison in case users have deployed instances that have capitalized connectivity mode in their configs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.121%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
28179

Relevant Lines:
62526

💛  - Coveralls


Webpack function in config is not called

I am trying to add "graphql-tag" to the webpack loaders, but the webapck function in the nextjs config is not being called.
Here's my next.config.js:
const withPlugins = require('next-compose-plugins'),
  withImages = require('next-images')

module.exports = withPlugins([withImages()], {
  i18n: {
    locales: ['en-US', 'hu'],
    defaultLocale: 'hu'
  },
  webpack(config, options) {
    config.module.rules.push({
      test: /\.(graphql|gql)$/,
      use: [
        {
          loader: require.resolve('graphql-tag/loader')
        }
      ]
    })

    return config
  }
})

The missing loader error is still being thrown:
error - ./queries/products.gql 1:6
Module parse failed: Unexpected token (1:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> query {
|   allProducts {
|     id

Why hasn't this been addressed? Makes this library nearly unusable.


[BUG] No Bloxstrap Menu

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
I downloaded bloxtrap and searched for the menu, it does not exist, i tried reinstalling and still does not appear to me.
 i don't know if i downloaded it incorrectly or something.

Noticed something, i can open the menu if i go to configurations, then apps and search for bloxstrap then i click on modify, it will open the menu which kinda resolves my problem but there is no menu app tho

there, if i click modify on app configurations of my pc, i can open it, thats enough for now so i'll leave for now and come back later to see if someone clarified my situation, see ya.

Try looking for it in the Start menu yourself instead of searching for it.


Move generated code to src directory

Moved the generated code to the source directory so IDEs have an easier time finding definitions

I can understand making things easier for IDEs, however cargo publish becomes really sad when the build script modifies the source directory. If I read https://doc.rust-lang.org/cargo/reference/build-script-examples.html correctly, this can actually cause breakage:

In general, build scripts should not modify any files outside of OUT_DIR. It may seem fine on the first blush, but it does cause problems when you use such crate as a dependency, because there's an implicit invariant that sources in .cargo/registry should be immutable. cargo won't allow such scripts when packaging.

Oh, well, damn. I had no idea.

What are you using? I heard about rust-analyzer and there is already an open issue there for this kind of thing: https://github.com/rust-analyzer/rust-analyzer/issues/1964
Another option would be to change the way code is generated in x11rb.
Right now, code is generated by build.rs in $OUT_DIR.
Instead, one could ship the generated code with x11rb and get rid of build.rs. However, I do not want generated code in Git, so this option would be a little complicated. It needs some magic so that the generated code is picked up by cargo publish and shipped together with the other code. However, at the same time something (outside of cargo?) would need to generate the code when building from git.
Basically... this option would mean that building x11rb from git would become more complicate since cargo build would fail and instead something like make build would be necessary.
These are the two options that I can think of for this right now. Nothing is "obviously nice". However, it would still be nice to get rid of the python dependency when building from crates.io....

I've been using CLion lately. Haven't tried it out on VSCode as yet. Is there a reason the code is generated at all?

Is there a reason the code is generated at all?

Well, what is the alternative?
My preferred solution would be "no generated code in Git" (as is now; otherwise it is too easy to have things get out of sync and diffs become huge and noisy) but "generated code in the download from crates.io (and no build.rs)". However, I do not think this is possible.

Just generate the code once and don't bother doing it for each build?


feat: Introduce deep.StaticMetadata

feat: Introduce deep.StaticMetadata
feat: Salesloft with deep.StaticMetadata

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1073  👈
#1072
#1071
#1070
#1069
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Cobalt0s and the rest of your teammates on  Graphite

Spike completed.


Cache NetworkInterfaces to reduce the time taken to access network card information

This is an improvement issue.
java.net.NetworkInterface.getNetworkInterfaces() is a heavyweight operation, this pull request will cache NetworkInterfaces to reduce the time taken to access network card information

@ShannonDing  Can anyone merge this request?

@ShannonDing Can anyone merge this request?

Please create a PR.

Hi, I created a PR #2634, but the code that Travis CI runs is not my code, can you help me find out why?

@ShannonDing Can anyone merge this request?

Please create a PR.

Hi, I created a PR #2634, but the code that Travis CI runs is not my code, can you help me find out why?

@ShannonDing Can anyone merge this request?

Please create a PR.

Hi, Travis CI check fixed.


✅ Scli List Agent Checkpoints

✅ Task

The ability for the CLI to give a list of checkpoints for an agent.
Motivation

Gives nice information for when we do want to rollback to a checkpoint.
Details

Effects:

scli
snops

scli env agent foo list-checkpoints
Related to #183 and #181.

Should be a find-by-height, find-by-span, or find-by-timestamp RPC on the agent & node (because the node has an active checkpoint manager)


NPC AI draft

Basic pathfinding and steering. Behavior tree testing.

[ ] Setup 2D Navigation server with 2D Nav Agents
[ ] Add beehave to project, test functionality

https://docs.godotengine.org/en/stable/classes/class_navigation2dserver.html
https://github.com/bitbrain/beehave

[ ] Add behavior tree composite node for selecting an action based on probability distribution.


Error building libgpu on macOS-arm64

Description
> make build
curl -L https://github.com/spacemeshos/gpu-post/releases/download/v0.1.21/macos.zip -o /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   617  100   617    0     0   2227      0 --:--:-- --:--:-- --:--:--  2219
100 15.0M  100 15.0M    0     0  1125k      0  0:00:13  0:00:13 --:--:--  933k
mkdir -p /Users/user/go-spacemesh/build/
unzip -o /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip -d /Users/user/go-spacemesh/build/ libgpu-setup.dylib
Archive:  /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip
  inflating: /Users/user/go-spacemesh/build/libgpu-setup.dylib
touch /Users/user/go-spacemesh/build/libgpu-setup.dylib
mkdir -p /Users/user/go-spacemesh/build/
unzip -o /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip -d /Users/user/go-spacemesh/build/ libMoltenVK.dylib
Archive:  /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip
  inflating: /Users/user/go-spacemesh/build/libMoltenVK.dylib
touch /Users/user/go-spacemesh/build/libMoltenVK.dylib
mkdir -p /Users/user/go-spacemesh/build/
unzip -o /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip -d /Users/user/go-spacemesh/build/ libvulkan.1.dylib
Archive:  /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip
  inflating: /Users/user/go-spacemesh/build/libvulkan.1.dylib
touch /Users/user/go-spacemesh/build/libvulkan.1.dylib
mkdir -p /Users/user/go-spacemesh/build/
unzip -o /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip -d /Users/user/go-spacemesh/build/ MoltenVK_icd.json
Archive:  /Users/user/go-spacemesh/libgpu-setup-macos-0.1.21.zip
  inflating: /Users/user/go-spacemesh/build/MoltenVK_icd.json
touch /Users/user/go-spacemesh/build/MoltenVK_icd.json
go build -o /Users/user/go-spacemesh/build/go-spacemesh -ldflags "-X main.version=v0.0.0-unreleased -X main.commit=ca00a3860410a96ac7831ee815d8f35ed2ff282a -X main.branch=develop-dirty"  .
# github.com/spacemeshos/post/gpu
ld: warning: ignoring file /Users/user/go-spacemesh/build//libgpu-setup.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
Undefined symbols for architecture arm64:
  "_scryptPositions", referenced from:
      __cgo_255ad663c373_Cfunc_scryptPositions in _x002.o
     (maybe you meant: __cgo_255ad663c373_Cfunc_scryptPositions)
  "_spacemesh_api_get_providers", referenced from:
      __cgo_255ad663c373_Cfunc_spacemesh_api_get_providers in _x002.o
     (maybe you meant: __cgo_255ad663c373_Cfunc_spacemesh_api_get_providers)
  "_spacemesh_api_stop_inprogress", referenced from:
      __cgo_255ad663c373_Cfunc_spacemesh_api_stop_inprogress in _x002.o
     (maybe you meant: __cgo_255ad663c373_Cfunc_spacemesh_api_stop_inprogress)
  "_stop", referenced from:
      __cgo_255ad663c373_Cfunc_stop in _x002.o
     (maybe you meant: __cgo_255ad663c373_Cfunc_stop, __cgo_255ad663c373_Cfunc_spacemesh_api_stop_inprogress )
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [go-spacemesh] Error 2

Steps To Reproduce

Run make install on Mac M1

Environment
Please complete the following information:

OS: macOS 11/arm64
Node Version: ca00a3860410a96ac7831ee815d8f35ed2ff282a

I can build go-spacemesh and run the binary on macOS/M1 from develop branch w/o errors and it also links with the AMD64 gpu-post dylib at runtime just fine. Maybe you were trying to build another branch?

What command are you using to build? Is it running natively or in
compatibility mode?
On Mon, 16 Aug 2021 at 08:45, Aviv Eyal @.***> wrote:

I can build go-spacemesh and run the binary on macOS/M1 from develop
branch w/o errors and it also links with the AMD64 gpu-post dylib at
runtime just fine. Maybe you were trying to build another branch?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spacemeshos/go-spacemesh/issues/2642#issuecomment-899480259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZJWNDDLIA2MTUCSIVQ2RLT5EB6LANCNFSM5BYVYXSQ
.

I'm using make - I checked and you are right - the built go-spacemesh binary is intel arch. I'm not even sure if you can build go-spacemesh for ARM regardless of gpu-lib support.

I couldn't get this to work, see #2643


imageview are oval in shape

Most of the time imageview are oval rather than circular.

Please provide more details and code samples.


X509_NAME_cmp fix for empty name

The leaf certificate in our certificate chain currently has an empty subject.
This was verifying fine always until we updated alpine linux to version with OpenSSL 3.0.8 (from 1.1.1q).
It is also still validating fine on debian linux with OpenSSL 3.0.8.
Root cause analysis indicated that following commit caused the issue: https://github.com/openssl/openssl/commit/72ded6f2a93085f536b4a820ab42b2da26fecf1c
Reason is the empty subject is now always seen as an issue and returns -2.  In both cases when empty subject is a or b.  Which of course invalidates the compare invariant: "" < "anything" and "anything" < "".
We have a certificate chain that exactly triggers issue on alpine linux qsort that the correct certificate is not found anymore in verification.
Checklist

[ ] tests are added or updated

It would be also nice to have a test case but that would make the PR outside of things acceptable with CLA: trivial.

Added the CLA and Fixes to commit message.  Also in process to submit CLA, but that can take time for corporate approvals.

This pull request is ready to merge

@tmshort Are you OK with CLA: trivial?

@t8m, if the nit I mentioned were fixed, then no; but as-is, I'm ok with (cla:trivial).

Merged to master, 3.1, and 3.0 branches. Thank you for your contribution.


LS151177 GE Fridge Interior Light

All of my sensors on all appliances (fridge, oven, dishwasher, opal icemaker) lose connection from time to time but they come back up after I reload. The most annoying is the interior Backlight of the fridge turns off every time it loses connection. Any ideas on what is causing this? I have to reset it via smartHQ app each time.
Thank you

I also have this same issue, thought it might be due to 2024.10.1 but rolled back to 2024.10.0 and it persists.

I figured it out. I had a script to turn off kitchen lights that just worked by area so it was including the fridge light in the area. Had to change it to individual devices so it only turns off overhead lights.


Add option to set anything directly to mongo db in model schema

I mean it could be better if we can do like this:
afterInitModel: function (collection) {
   collection.ensureIndex({ "loc" : "2dsphere" });
   // or
   collection.ensureIndex({ "fbuid": { unique: true, sparse: true }})
}

MyModel.native(function(err, collection) {
  collection.ensureIndex({ "loc" : "2dsphere" });
});

It's deprecated now, is there any replacement?


Auto complete even the remote directory name is not exist on local(development) machine.

Since I am developing Azure Function application using Python,
I usually create a custom class file and put them in the __app__ folder of the function app, but the autocomplete is not working for __app__ as it does not really exist on my development machine, but the code below will works fine when I deploy it to Azure Function App host.

I want a feature that VSCODE can autocomplete even the __app__ folder is not exist on my development machine, the solution can be adding some mapping to the .vscode/settings.json like
"pathMappingRemote": "__app__",
"pathMappingLocal": "/path/to/my_proj/"

@fiveisprime Thank you for the guess, I think I may have to create a ticket in Azure Portal and let Microsoft work from there or maybe I have to post an issue at https://github.com/Azure/Azure-Functions since this is specific when I develop the Azure Function only.

I'd recommend reaching out to the folks that work on the python extension first, open an issue here: https://github.com/Microsoft/vscode-python


python3Packages.pymata-express: init at 1.19

Motivation for this change
Python Asyncio Arduino Firmata Client
https://mryslab.github.io/pymata-express/
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

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

3 packages built:

python37Packages.pymata-express
python38Packages.pymata-express
python39Packages.pymata-express

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

3 packages built:

python37Packages.pymata-express
python38Packages.pymata-express
python39Packages.pymata-express

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109970 run on x86_64-linux 1

3 packages built:

python37Packages.pymata-express
python38Packages.pymata-express
python39Packages.pymata-express

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109970 run on x86_64-linux 1

3 packages built:

python37Packages.pymata-express
python38Packages.pymata-express
python39Packages.pymata-express


Improved Repository page

Sorry, I can note make a code suggestion on part that have not be changed. Could you please update the first comment? The bulleted list is not the purpose of this component anymore. If you prefer I can also commit directly on the PR.
It could for example be something like this:
Create a table representing an external repository.
The component get the sources from the `versioning.json` file of the repo.
The url argument must be of the form "https://paperback-ios.github.io/extensions" without a trailing slash.

Done

Sorry, I can note make a code suggestion on part that have not be changed. Could you please update the first comment? The bulleted list is not the purpose of this component anymore. If you prefer I can also commit directly on the PR.
It could for example be something like this:
Create a table representing an external repository.
The component get the sources from the `versioning.json` file of the repo.
The url argument must be of the form "https://paperback-ios.github.io/extensions" without a trailing slash.

Done