RuntimeError: CUDA error: no kernel image is available for execution on the device

sys.platform: linux
Python: 3.6.8 (default, Aug  7 2019, 17:28:10) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
CUDA available: True
GPU 0,1: Tesla V100-PCIE-32GB
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.0, V10.0.130
GCC: gcc (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5)
PyTorch: 1.6.0
PyTorch compiling details: PyTorch built with:

GCC 5.3
C++ Version: 201402
Intel(R) Math Kernel Library Version 2019.0.1 Product Build 20180928 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v1.5.0 (Git Hash e2ac1fac44c5078ca927cb9b90e1b3066a0b2ed0)
OpenMP 201307 (a.k.a. OpenMP 4.0)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 10.0
NVCC architecture flags: -gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_52,code=sm_52;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_75,code=compute_75
CuDNN 7.6.4
Magma 2.5.2
Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL-fopenmp -DNDEBUG -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=ON, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.7.0
OpenCV: 4.4.0
MMCV: 1.2.7
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 10.0
MMDetection: 2.10.0+eaf42fa

inference_detector(model, 'demo/demo.jpg')
/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/datasets/utils.py:68: UserWarning: "ImageToTensor" pipeline is replacedby "DefaultFormatBundle" for batch inference. It is recommended to manually replace it in the test data pipeline in your config file.
'data pipeline in your config file.', UserWarning)
Traceback (most recent call last):
File "", line 1, in
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/apis/inference.py", line 141, in inference_detector
results = model(return_loss=False, rescale=True, **data)
File "/usr/local/lib64/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/usr/local/lib64/python3.6/site-packages/mmcv/runner/fp16_utils.py", line 84, in new_func
return old_func(*args, **kwargs)
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/models/detectors/base.py", line 183, in forward
return self.forward_test(img, img_metas, **kwargs)
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/models/detectors/base.py", line 160, in forward_test
return self.simple_test(imgs[0], img_metas[0], **kwargs)
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/models/detectors/two_stage.py", line 199, in simple_test
proposal_list = self.rpn_head.simple_test_rpn(x, img_metas)
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/models/dense_heads/rpn_test_mixin.py", line 36, in simple_test_rpn
proposal_list = self.get_bboxes(*rpn_outs, img_metas)
File "/usr/local/lib64/python3.6/site-packages/mmcv/runner/fp16_utils.py", line 164, in new_func
return old_func(*args, **kwargs)
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/models/dense_heads/anchor_head.py", line 582, in get_bboxes
scale_factors, cfg, rescale)
File "/opt/meituan/cephfs/zhangjunjian/mmdetection/mmdet/models/dense_heads/rpn_head.py", line 234, in get_bboxes
cfg.nms)
File "/usr/local/lib64/python3.6/site-packages/mmcv/ops/nms.py", line 296, in batched_nms
dets, keep = nms_op(boxes_for_nms, scores, **nms_cfg)
File "/usr/local/lib64/python3.6/site-packages/mmcv/utils/misc.py", line 310, in new_func
output = old_func(*args, **kwargs)
File "/usr/local/lib64/python3.6/site-packages/mmcv/ops/nms.py", line 157, in nms
inds = NMSop.apply(boxes, scores, iou_threshold, offset)
File "/usr/local/lib64/python3.6/site-packages/mmcv/ops/nms.py", line 19, in forward
bboxes, scores, iou_threshold=float(iou_threshold), offset=offset)
RuntimeError: CUDA error: no kernel image is available for execution on the device

help me! i have try to debug my code one weak!!!!

Hi, you can refer to #4335


Introduce isEncrypted in PutRequestOptions for clients to not encrypt self key/shared key data

Is your feature request related to a problem? Please describe.

Currently isEncrypted in metadata is set to false even though data is encrypted.
Client don't have control if they choose not to encrypt data for self key/shared key

Describe the solution you'd like

Introduce a flag isEncrypted in PutRequestOptions which will be true by default
New client can still see old data which can be encrypted with isEncrypted=false. Handle this scenario while decrypting

Describe alternatives you've considered
No response
Additional context
No response

@gkc
Existing data for self key /shared key
data will be encrypted. metadata.isEncrypted = false.
Once we merge the changes for this feature, there are two scenario while decrypting
i) new data - data will be encrypted. metadata.isEncrypted = true
ii) old data - data will be encrypted. metadata.isEncrypted = false
I have implemented the below approach for backward compatibility in GetResponseTransformer
i) if key is public, do not call decryption service
ii) if metadata.isEncrypted=true, call decryption service
iii) if metadata is not set or metadata.isEncrypted=false, try decrypting the data(may be old data). if decryption passes, then return decrypted value.  If decryption fails, then return actual value.
https://github.com/atsign-foundation/at_client_sdk/pull/1398/files#diff-4565ef50d8f9949de083fc75b9212acc31ae9463627cac423497f138664565d3
Another implementation which I had i mind (but yet to implement). If decryption passes for scenario iii) update metadata.isEncrypted = true in metadata. So old keys with isEncrypted=false, will eventually be migrated.

Discussed on call


Reader part is not working as it should

I received the following error while testing with reader.js. I created fruits.parquet using writer.js from the example.
(node:21836) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'num_values' of null
    at decodeDataPage (/home/ubuntu/memNode/node_modules/parquetjs/lib/reader.js:312:44)
    at decodeDataPages (/home/ubuntu/memNode/node_modules/parquetjs/lib/reader.js:301:20)
    at ParquetEnvelopeReader.readColumnChunk (/home/ubuntu/memNode/node_modules/parquetjs/lib/reader.js:245:12)
(node:21836) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:21836) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Can you past the exact code you ran?    Did you close the writer after writing data?

It is the exact same code of writer.js from examples folder.

same trouble. Have you resolve the problem?

What node version?    It's important that you are on a version that supports async/await

same problem with node v8.4.0


Small update to README wording to beta

Stack from ghstack:

-> #305

Confirmed the updated linking works in this branch

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


As a project, I want to archive my data to a DAAC so that my data can be preserved in perpetuity and i can fulfill my requirements

Needed as part of the Atmospheric SIPS in the cloud use case from 24.3 - 25.1.
High level goal: Take forward stream data being produced and be able to send it to an archive (either a UAT or PROD archive - probably configurable). Idea is to do this as a service and update granules in the catalog with this status, alert projects/venues of errors. Handle retries due to connection or transient issues, report back data/validation level errors to user/operators.

Implemented by https://github.com/unity-sds/unity-project-management/issues/177

Closing this ticket in favor of #177 - design work (#172 ) + implementation work = this ticket.


up to and including migration as finders

up to and including migration as finders (to the Context and Migration grammars), so they can be disabled by omitting from the config.
This hasn't been tested by me -- @kwalcock I have to run, do you have an easy way to test this?
fyi @MihaiSurdeanu @zupon @maxaalexeeva

Cool!  I hadn't realized how that worked.  Probably I should remove my garbage around the keepMigrationEvents setting.  This looks like the right way to do it.

A bunch of tests failed, the first ones related to migration.  I suspect it has to do with the test configuration file overwriting the value for entityFinders.  I can figure it out as long as you don't do it at the same time.

A bunch of tests failed, the first ones related to migration. I suspect it has to do with the test configuration file overwriting the value for entityFinders. I can figure it out as long as you don't do it at the same time.

it's all yours! :) thanks!!

Among the many things I don't understand are Finders and how their rules differ from the rules used by the ExtractorEngine.  We just moved the migration rules out of a file used by the ExtractorEngine and put it into a file used by an Extractor.  It seems like the Finders all run just once, in EidosSystem.mkMentions.  They run in the order specified in the config file, independent of priority, and they are used for the initial state.   Thereafter, there is a components.engine.extractFrom that runs.  My impression is that this runs through all the rules from master.yml, in priority order, multiple times, because a rule could make use of something that is figured out by a later rule or by an earlier running of itself.  This all loops until nothing changes anymore.  I don't know the context and migration rules that have been moved from one place to another.  It doesn't seem like just any rule could be moved.  They would have to work when only one pass of the context rules had been made.

Among the many things I don't understand are Finders and how their rules differ from the rules used by the ExtractorEngine.

In principle they don't, we could (and maybe should make everything a Finder), but I went through migration so there would be an easy way to disable them.

We just moved the migration rules out of a file used by the ExtractorEngine and put it into a file used by an Extractor. It seems like the Finders all run just once, in EidosSystem.mkMentions. They run in the order specified in the config file, independent of priority, and they are used for the initial state. Thereafter, there is a components.engine.extractFrom that runs. My impression is that this runs through all the rules from master.yml, in priority order, multiple times, because a rule could make use of something that is figured out by a later rule or by an earlier running of itself.

Yes, but about the multiple times, IDK if it does by default, we'd have to ask @marcovzla or someone.  I thought I remembered that if you wanted an Odin rule to run over and over you had to make the priority something like 2+ vs 2 or something...

This all loops until nothing changes anymore. I don't know the context and migration rules that have been moved from one place to another. It doesn't seem like just any rule could be moved. They would have to work when only one pass of the context rules had been made.

This is true -- and perhaps I should dig into this to make sure that it's not the source of the problem... Using the thing above I could probably make them run several times if they aren't already.  But in both the Finder I made and the main "master" rules we use for causality, there is an Odin extractor engine doing the extraction, so they should be equivalent.

Thanks @BeckySharp.  Lacking time to look at it carefully, I was just grasping at straws.  For the record, here's the description of priority below.  Since you are having a new ExtractionEngine running the OdinFinders, it seems like the rules would be run multiple times as usual.  Migration is priority 2 and that used to be shared with entityQuantification and temporalAttachment in master.yml.  Now those two would be running separately from and after migration, which runs before them.  Could that be a problem?
priority The iterations in which this rule should be applied. Note that the
Odin runtime system continuously applies the given grammar
on a given sentence until no new rule matches (this allows grammars
that use recursive events, such as the one in Example 1
to work). Each of these distinct runs is called an “iteration”,
and they are all numbered starting from 1. Through priorities,
a developer can specify in which iteration(s) the corresponding
rule should run. Specifying priorities is not required, but it may
have an impact on run time, by optimizing which rule should
be applied when. A priority can be exact (denoted by a single
number), a range (two numbers separated by a dash), an infinite
range (a number followed by a plus +), or a list of priorities (a
comma separated list of numbers surrounded by square brackets.

i don’t think it’s the problem or a problem, but good to point out, thanks!
On Friday, March 13, 2020, Keith Alcock<EMAIL_ADDRESS>wrote:

External Email
Thanks @BeckySharp https://github.com/BeckySharp. Lacking time to look
at it carefully, I was just grasping at straws. For the record, here's the
description of priority below. Since you are having a new ExtractionEngine
running the OdinFinders, it seems like the rules would be run multiple
times as usual. Migration is priority 2 and that used to be shared with
entityQuantification and temporalAttachment in master.yml. Now those two
would be running separately from and after migration, which runs before
them. Could that be a problem?
priority The iterations in which this rule should be applied. Note that the
Odin runtime system continuously applies the given grammar
on a given sentence until no new rule matches (this allows grammars
that use recursive events, such as the one in Example 1
to work). Each of these distinct runs is called an “iteration”,
and they are all numbered starting from 1. Through priorities,
a developer can specify in which iteration(s) the corresponding
rule should run. Specifying priorities is not required, but it may
have an impact on run time, by optimizing which rule should
be applied when. A priority can be exact (denoted by a single
number), a range (two numbers separated by a dash), an infinite
range (a number followed by a plus +), or a list of priorities (a
comma separated list of numbers surrounded by square brackets.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/786#issuecomment-598802810, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCLXP57RLA57I6XLI4TRHJMF5ANCNFSM4LFLK5BA
.

@BeckySharp @kwalcock, another fun finding:
In the as_finders branch, numbers are found as just concepts, while in other branches (master, our old migration_schema-zupon), they were found as concepts and entities, and migration rules are written such that groups have to be entities. Do you know why numbers stopped being entities? If that was intentional, then changing migration rules to accept Concepts for group will fix some of the tests (still not the expansion-related ones). If that was not intentional, I can keep looking for why that happened.

Thank you for the detective work!  (That's about all I can say about it just now.)

Ill look, this is prob important
On Sat, Mar 14, 2020 at 2:23 PM Keith Alcock<EMAIL_ADDRESS>wrote:

External Email
Thank you for the detective work! (That's about all I can say about it
just now.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/786#issuecomment-599136456, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCIC6DNOMYDGSJIM37TRHPYU3ANCNFSM4LFLK5BA
.

Thanks for digging into this.  Those look like some things I should have noticed or maybe even I caused them.

I disagree - I feel like I should have found it waaay sooner, but if you want to dig into something :) you can look at the current errors -- with JLD serialization? I don't think they were errors before...? so maybe I broke something...

I can probably check a little later today.  JLDSerializer sounds like a job for me.

It may be broken.  In each case the exception is thrown because there was no "rule" that can be used for the "foundBy" parameter of a Mention.  Is that enough of a hint?
  "extractions" : [ {
    "@type" : "Extraction",
    "@id" : "_:Extraction_1",
    "type" : "concept",
    "subtype" : "entity",
    "labels" : [ "Concept", "Entity" ],
    "text" : "300 refugees",

*** there should be a rule here ***

    "canonicalName" : "refugees",
    "provenance" : [ {
      "@type" : "Provenance",
      "document" : {
        "@id" : "_:Document_1"
      },
      "documentCharPositions" : [ {
        "@type" : "Interval",
        "start" : 0,
        "end" : 11
      } ],
      "sentence" : {
        "@id" : "_:Sentence_1"
      },
      "sentenceWordPositions" : [ {
        "@type" : "Interval",
        "start" : 1,
        "end" : 2
      } ]
    } ],

how is that possible?
On Thu, Apr 2, 2020 at 11:24 AM Keith Alcock<EMAIL_ADDRESS>wrote:

External Email
It may be broken. In each case the exception is thrown because there was
no "rule" that can be used for the "foundBy" parameter of a Mention. Is
that enough of a hint?
"extractions" : [ {
"@type" : "Extraction",
"@id" : "_:Extraction_1",
"type" : "concept",
"subtype" : "entity",
"labels" : [ "Concept", "Entity" ],
"text" : "300 refugees",
*** there should be a rule here ***
"canonicalName" : "refugees",
"provenance" : [ {
  "@type" : "Provenance",
  "document" : {
    "@id" : "_:Document_1"
  },
  "documentCharPositions" : [ {
    "@type" : "Interval",
    "start" : 0,
    "end" : 11
  } ],
  "sentence" : {
    "@id" : "_:Sentence_1"
  },
  "sentenceWordPositions" : [ {
    "@type" : "Interval",
    "start" : 1,
    "end" : 2
  } ]
} ],

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/786#issuecomment-608025584, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCNWAPJIFLKYE7HRC3DRKTJU3ANCNFSM4LFLK5BA
.

maybe something in the expansion? i'll start looking there
On Thu, Apr 2, 2020 at 11:56 AM Becky Sharp<EMAIL_ADDRESS>wrote:

how is that possible?
On Thu, Apr 2, 2020 at 11:24 AM Keith Alcock<EMAIL_ADDRESS>wrote:

External Email
It may be broken. In each case the exception is thrown because there was
no "rule" that can be used for the "foundBy" parameter of a Mention. Is
that enough of a hint?
"extractions" : [ {
"@type" : "Extraction",
"@id" : "_:Extraction_1",
"type" : "concept",
"subtype" : "entity",
"labels" : [ "Concept", "Entity" ],
"text" : "300 refugees",
*** there should be a rule here ***
"canonicalName" : "refugees",
"provenance" : [ {
  "@type" : "Provenance",
  "document" : {
    "@id" : "_:Document_1"
  },
  "documentCharPositions" : [ {
    "@type" : "Interval",
    "start" : 0,
    "end" : 11
  } ],
  "sentence" : {
    "@id" : "_:Sentence_1"
  },
  "sentenceWordPositions" : [ {
    "@type" : "Interval",
    "start" : 1,
    "end" : 2
  } ]
} ],

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/786#issuecomment-608025584, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCNWAPJIFLKYE7HRC3DRKTJU3ANCNFSM4LFLK5BA
.

One possibility is that the serializer didn't write them out for some reason, but that doesn't appear to be the case.  I see in the test of p5s1 that there is a mention found with oldCorpus(0).eidosMentions(2).odinMention.text = "more than one in five people in South Sudan" and labels of (Concept, Entity) that has an empty string for foundBy.  It's an EidosTextBoundMention.
Its attachments are a COUNT and DCTime.  Something isn't filling in that rule.  Maybe it was in the output before but the particular mention was removed as a duplicate and its twin did have a rule.  I see in the equivalenceHash for the TextBoundMention that foundBy is not taken into account.  Something may be making a copy and losing the rule.

A conditional breakpoint on package org.clulab.odin.TextBoundMention line 195 with foundBy == "" does catch something in ExpansionUtils.attachDCT after the ArgumentExpander.  Getting closer...

I notice that in ExpansionUtils.addSubsumedAttachments, compositionalFoundBy is being called with overlapping being empty.  Then completeFoundBy is empty and MentionUtils.withFoundBy is called with no rule.  That would cause a problem.  I hope that gets someone further.

Thanks! This is helpful!
On Thu, Apr 2, 2020 at 5:34 PM Keith Alcock<EMAIL_ADDRESS>wrote:

External Email
I notice that in ExpansionUtils.addSubsumedAttachments,
compositionalFoundBy is being called with overlapping being empty. Then
completeFoundBy is empty and MentionUtils.withFoundBy is called with no
rule. That would cause a problem. I hope that gets someone further.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/786#issuecomment-608138420, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCOCQCPZRYSJHGFUBU3RKULQTANCNFSM4LFLK5BA
.

Keith you're soooooooooooooooo good at this!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANK YOU SO MUCH!!!!
Thanks for finding this bug of mine!

Hey @BeckySharp, did you replace
    expander = ${actions.expander}

with
    expander = { include required("englishActionsExpander.conf") }

because the former didn't work or was it some other reason?  It seems like the first version would be safer.

oh, it was in the process of debugging, if tests pass with the former,
let's revert
can you check?
On Mon, Apr 6, 2020 at 12:13 PM Keith Alcock<EMAIL_ADDRESS>wrote:

External Email
Hey @BeckySharp https://github.com/BeckySharp, did you replace
expander = ${actions.expander}

with
expander = { include required("englishActionsExpander.conf") }

because the former didn't work or was it some other reason? It seems like
the first version would be safer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/786#issuecomment-609984060, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCMYZQQKDBPC2PT7DBTRLISWBANCNFSM4LFLK5BA
.

I wondered and checked, mostly to make sure that I understood what was going on.  There is PR in the works.


[BUG] Can't "install" new apps after updating to 3.1.0

Describe the bug
I can't seem to "install"/add new applications to LiveContainer after updating from 2.1.2 to 3.1.0. Apps that "installed" perfectly fine on the previous version now crash upon trying to open them with a very long error message with something along the lines of "code signature invalid" and "file not found." These applications worked completely fine before. I "patched" SideStore and the default signer is still AltStore. Now any app I try to "install" new won't open, just getting this error message. I was also signed out of previously "installed" apps despite not manually clearing any data.
Instructions to reproduce
Adding a new application, then attempting to "run" it.
What version of LiveContainer are you using?
3.1.0
Other info
No response

I also was signed out of all of my apps previously running in LiveContainer. Come on. You completely broke the app with this update.

What's the test jitless result?

Please install the latest test build here https://github.com/hugeBlack/LiveContainer/actions and take a screenshot of "JITLess Mode Diagnose" screen in LiveContainer settings


s2n-tls: 1.4.17 -> 1.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/aws/s2n-tls/releases.
meta.description for s2n-tls is: C99 implementation of the TLS/SSL protocols
meta.homepage for s2n-tls is: https://github.com/aws/s2n-tls
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.18 in filename of file in /nix/store/mqfpad384fj935mykwpr8kzj91x0b60l-s2n-tls-1.4.18

Rebuild report (if merged into master) (click to expand)

493 total rebuild path(s)

493 package rebuild(s)

First fifty rebuilds by attrpath

apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
appvm
arrow-cpp
arrow-glib
attic-client
attic-server
aws-c-auth
aws-c-event-stream
aws-c-http
aws-c-io
aws-c-mqtt
aws-c-s3
aws-crt-cpp
aws-sdk-cpp
browsr
bundix
cabal2nix
cached-nix-shell
cachix
ceph
ceph-client
ceph-csi
ceph-dev
chatgpt-retrieval-plugin
cloudcompare
colmena
common-updater-scripts
crate2nix
crystal2nix
datatrove
dbx
devenv
disko
dub-to-nix
dydisnix
entwine
fusionInventory
gdal
gmt
gplates
grass
harmonia
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.cli-nix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mqfpad384fj935mykwpr8kzj91x0b60l-s2n-tls-1.4.18 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A s2n-tls https://github.com/r-ryantm/nixpkgs/archive/0cc5a2093cef64f6003383391d3c2966e5c65047.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0cc5a2093cef64f6003383391d3c2966e5c65047#s2n-tls

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mqfpad384fj935mykwpr8kzj91x0b60l-s2n-tls-1.4.18
ls -la /nix/store/mqfpad384fj935mykwpr8kzj91x0b60l-s2n-tls-1.4.18/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @orivej for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/aws/s2n-tls/releases.
meta.description for s2n-tls is: C99 implementation of the TLS/SSL protocols
meta.homepage for s2n-tls is: https://github.com/aws/s2n-tls
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.0 in filename of file in /nix/store/778vhalsa4dfwx56hc8djp662wf5kdja-s2n-tls-1.5.0

Rebuild report (if merged into master) (click to expand)

497 total rebuild path(s)

497 package rebuild(s)

First fifty rebuilds by attrpath

apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
appvm
arrow-cpp
arrow-glib
attic-client
attic-server
aws-c-auth
aws-c-event-stream
aws-c-http
aws-c-io
aws-c-mqtt
aws-c-s3
aws-crt-cpp
aws-sdk-cpp
browsr
bundix
cabal2nix
cached-nix-shell
cachix
ceph
ceph-client
ceph-csi
ceph-dev
chatgpt-retrieval-plugin
cloudcompare
colmena
common-updater-scripts
crate2nix
crystal2nix
datatrove
dbx
devenv
disko
dub-to-nix
dydisnix
entwine
fusionInventory
gdal
gmt
gplates
grass
harmonia
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.cli-nix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/778vhalsa4dfwx56hc8djp662wf5kdja-s2n-tls-1.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A s2n-tls https://github.com/r-ryantm/nixpkgs/archive/669ce8bced9d138dcfba87e5ac235a7425702e87.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/669ce8bced9d138dcfba87e5ac235a7425702e87#s2n-tls

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/778vhalsa4dfwx56hc8djp662wf5kdja-s2n-tls-1.5.0
ls -la /nix/store/778vhalsa4dfwx56hc8djp662wf5kdja-s2n-tls-1.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @orivej for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/aws/s2n-tls/releases.
meta.description for s2n-tls is: C99 implementation of the TLS/SSL protocols
meta.homepage for s2n-tls is: https://github.com/aws/s2n-tls
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.1 in filename of file in /nix/store/vqxbpiz6r49vl6g89w7rpd0cydpmmq7r-s2n-tls-1.5.1

Rebuild report (if merged into master) (click to expand)

500 total rebuild path(s)

500 package rebuild(s)

First fifty rebuilds by attrpath

aider-chat
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
appvm
arrow-cpp
arrow-glib
attic-client
attic-server
aws-c-auth
aws-c-event-stream
aws-c-http
aws-c-io
aws-c-mqtt
aws-c-s3
aws-crt-cpp
aws-sdk-cpp
browsr
bundix
cabal2nix
cached-nix-shell
cachix
ceph
ceph-client
ceph-csi
ceph-dev
chatgpt-retrieval-plugin
cloudcompare
colmena
common-updater-scripts
crate2nix
crystal2nix
datatrove
dbx
devenv
disko
dub-to-nix
dydisnix
entwine
fusionInventory
gdal
gmt
gplates
grass
harmonia
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.cli-nix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vqxbpiz6r49vl6g89w7rpd0cydpmmq7r-s2n-tls-1.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A s2n-tls https://github.com/r-ryantm/nixpkgs/archive/fc1e11ff2972b045263f7336e0f8214fccf0881e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fc1e11ff2972b045263f7336e0f8214fccf0881e#s2n-tls

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vqxbpiz6r49vl6g89w7rpd0cydpmmq7r-s2n-tls-1.5.1
ls -la /nix/store/vqxbpiz6r49vl6g89w7rpd0cydpmmq7r-s2n-tls-1.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @orivej for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@ofborg build nix


fix: error data input for date(CAST(value AS DATETIME)) causing high TiFlash sys CPU

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/cc @windtalker @ywqzzy

/build

/merge


Multiple Items with CopyToOutput and conflicting TargetPath copies last file

A project with multiple items with CopyToOutputDirectory and conflicting assigned TargetPaths will cause the last file to be copied to the TargetPath.
I'm not certain this is a bug, but the behavior seems non-intuitive. It seems like multiple files trying to output to the same TargetPath should cause an error.
An example:
<Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" />

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFrameworkIdentifier>.NETCoreApp</TargetFrameworkIdentifier>
    <TargetFrameworkVersion>v1.0</TargetFrameworkVersion>
  </PropertyGroup>

  <ItemGroup>
    <Compile Include="**\*.cs" Exclude="$(GlobalExclude)" />
    <EmbeddedResource Include="**\*.resx" Exclude="$(GlobalExclude)" />
    <Content Include="Program.cs;project.json">
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
      <Link>otherfilename.json</Link>
    </Content>
  </ItemGroup>

  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
</Project>

onlyproject.json will be copied to otherfilename.json and no error is thrown.
cc @rainersigwald @cdmihai @eerhardt

I don't think this is a bug but more a missing feature. For now the content is only overrwritten which seems to be fine. Maybe there is a need for a switch which let decide to append instead to overwrite!?
Here is a example i have tested
<Content Include="Class1.cs;Class2.cs">
      <Link>Test.cs</Link>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </Content>

And this is my output

Do you really need the <Link /> element in there?

Not really, but i gives you the opportunity to rename the file. But i think this more a side effect?

Correct me if i'm wrong but i think the failure here is that you can add multiple items into <Content Include= If you add multiple items as a link with visual studio output is like this
<Content Include="Class1.cs">
<Link>Class1.cs</Link>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </Content>
<Content Include="Class2.cs">
<Link>Class2.cs</Link>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </Content>
<Content Include="Class3.cs">
<Link>Class3.cs</Link>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </Content>
...
This seems to be more correct.

Yes if you want to do <Link /> with multiple items, you'll need to do list them out and not do a semi-colon delimited list of paths to a single item.

We talked about this briefly in triage yesterday. The general problem (many files could be copied to the same destination path) is hard to deal with (MSBuild doesn't track all outputs from every task, which would be necessary to detect a conflict), but this specific case should be catchable, because it's all happening within a single call to the Copy task.
This situation will become more common as more folks start using globs.
Would anyone object if I changed the title to "Copy Task should error on duplicate destination paths"?

Would it be ok for all if i take this Issue and try to create a Solution within a PR?

@maddin2016 I think an error on multiple-copy-to-same-location is valuable even if it doesn't satisfy everyone here. I wouldn't object to a PR for that.

Thanks for the attention on this 😄
Feel free to change the title @rainersigwald

I have opened #1037.


Support for Gandi DNS

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I hope we can support another DNS provider [gandi]((https://www.gandi.net/zh-hant) for DNS01 challenge
Describe alternatives you've considered
Some people like to use the gandi as their DNS provider in Taiwan and it would be good to promote the cert-manager to them if we can support the Gandi
Additional context
I think that  I can help to help this feature request by adding a new backend support for Gandi
/kind feature

see https://github.com/jetstack/cert-manager/pull/771

Thanks!,


tiny documentation error

Only just because I literally just had to deal with this issue on my server, I thought I'd point out: in the part of your documentation about memcached size limit issues, the limit per cache key command actually requires a unit.  Setting the max cache size to 10MB would be -I 10m, not -I 10.  It's weirdly inconsistent, because the units are not used with the overall max memory (the -m 1000 to set the overall max it 1GB is correct), but there you have it.
This seemed like too minor a thing to make a PR over, but I wanted to give you a heads up.  Otherwise, thanks for the great work.

Thank you @MattBroach for spotting this!
Yes, this is completely inconsistent as we can see on the man page, -m is waiting for a number of MB while -I is waiting for a size, therefore containing SI prefixes…
Fixed with d2c9274d5d9b4e3714129858a8d606089c04ef18.


AMP ESP32 support fixes and improvements

Supporting change to fix and update the IPM samples on ESP32.

Folks, I found some AMP memories were overlapping with ordinary code on ESP32. Similar in ESP32-S3 I found a better location for the AMP common memory so I fixed both issues. Please revisit and re-approve the PR.


Running cl-neo4j.tests fails 100%

Please check the gist bellow which contain status information retrieved:
https://gist.github.com/dcguim/acd7f7946e488e1ddc9191f691eaf4c6
I have set the configuration under src/globals.lisp so I don`t think is an
authentication problem. I wonder if data type mapping should provided
before start creating simple nodes.
If I simply:
(create-node :properties '((:name . "Dan") (:email . "user@mail.com")))
Unknown status 401 returned for node
   [Condition of type UNKNOWN-RETURN-TYPE-ERROR]

Backtrace:
  0: ((:METHOD HANDLE-REQUEST (BASIC-HANDLER T T)) #<BASIC-HANDLER {1008834613}> #S(NEO4J-REQUEST :METHOD :POST :URI "node" :PAYLOAD<EMAIL_ADDRESS>
  ((201 #<FUNCTION (LAMBDA # :IN CREATE-NODE) {1002EA594B}>) (400 #<FUNCTION (LAMBDA # :IN CREATE-NODE) {1002EA589B}>))
  1: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CREATE-NODE :PROPERTIES (QUOTE (# #))) #<NULL-LEXENV>)
  2: (EVAL (CREATE-NODE :PROPERTIES (QUOTE (# #))))

Hmm, it looks like all of your connections to neo4j are returning an http 429 status code.  Are you sure that your graph database is online and healthy?

curl http://localhost:7474
{
"management" : "http://localhost:7474/db/manage/",
"data" : "http://localhost:7474/db/data/",
"bolt" : "bolt://localhost:7687"
}

Are you still having trouble?  I have been travelling, so please accept my apologies for not responding sooner.

I was able to reproduce this by setting an incorrect username / password combo.  Have you verified that both neo4j-user and neo4j-pass are set correctly?

$: grep dbms.security* ~/Applications/neo4j-community-3.3.0-alpha05/conf/neo4j.conf
dbms.security.auth_enabled=false
dbms.security.allow_csv_import_from_file_urls=true

Ah, so you aren't using auth at all;  I can't say I ever tried running without some sort of auth.  Too much time in the security space, I guess.  The library assumes that you will be using auth, so a number of changes would need to be made in order to connect without it.  The easy solution is to enable it and make sure that your user/pass variables are set correctly.  If it is important for you to run without it, I can update the request handler so that it doesn't always send credentials.


Typo in skin/classic/mac/scrollbox.css

Running jpm test the following message is logged.

JPM info console.log: firebug: [JavaScript Warning: "Expected end of value but found '3p'.  Error in parsing value for 'padding'.  Declaration dropped." {file: "chrome://firebug-os/skin/scrollbox.css" line: 27 column: 13 source: "  padding: 0 3p 0 3px;"}]

Merged at https://github.com/firebug/firebug.next/commit/aa4ef79ae21ae1a206651714d9c339d3e36c4007
Thanks for the patch!
Honza

$fixed firebug-3.0.0-alpha.8


PrimaryKeyRelatedField

This is previously that i used ModelSerializer
`class UserSerializer(serializers.ModelSerializer):
saledatas =serializers.PrimaryKeyRelatedField(many=True,queryset=Saledata.objects.all())
    class Meta:
	    model = User
	    fields = ('id','username','saledatas')`

How to call nested field like PrimaryKeyRelatedField above in DynamicModelSerializer
`AttributeError: saledatas is not a valid field for <class 'django.contrib.auth.models.User'>

`

@b14cknc0d3 you would use a DynamicRelationField instead of PrimaryKeyRelatedField -- DynamicRelationField can flexibly render as either an ID or a relationship (see https://github.com/AltSchool/dynamic-rest#features)


proposal: Go 2: bytes: remove NewBufferString

The constructor is often misused and confuses people. It can be used to put initial contents into a buffer that will be written into after, but so can buf.Write. Meanwhile, NewReader handles the case that most beginners misuse, calling NewBufferString when they only need NewBuffer.
This function's use case is not worth the confusion it causes and it should be deleted from the library.

I was curious about this, as it seems to overlap with strings/#NewReader. I
tried out these two files:
package main

import (
   "bytes"
   "strings"
   "time"
)

func main() {
   s := strings.Repeat("!", 999_999)
   bytes.NewBufferString(s)
   time.Sleep(time.Duration(time.Minute))
}

package main

import (
   "strings"
   "time"
)

func main() {
   s := strings.Repeat("!", 999_999)
   strings.NewReader(s)
   time.Sleep(time.Duration(time.Minute))
}

Here is what I got for memory use:

Function
Kilobytes

bytes#NewBufferString
3,244 K

strings#NewReader
2,172 K

So if you only need to read, then seems like the strings function is the way to
go.


images/script: update the example hubble cli Deployment version

Update the Hubble CLI image version in the Deployment examples/ whenever we bump the Hubble CLI inside Cilium.
See https://github.com/cilium/cilium/pull/16459#discussion_r646756915 for context.

Note to @cilium/janitors: no need to run CI on this PR.


[enhancement] Increase Randomness of the ball

On playing the game multiple times, anyone can catch the moves by which the game can be won in no time. Increasing randomness will decrease the probability of winning the game by those same moves.

I would like to work on this issue

@jajodiaraghav sir, for resolving this, I thought of changing dx=-dx and dy=-dy these statements into dx=kdx and dy=mdy where k and m are random numbers, BUT it would be ambiguous as the angle between line of impact and normal before and after collision should be the same :p   . But there is another way of creating randomness by changing the initial position of the paddle. When I played this game long ago, user decided the initial position of paddle and then the ball moves. So, the same should be done here. So, do I need to create another issue for this with title choose initial position or continue with the same?

@jajodiaraghav I've sent PR for settings panel issue. Speed in changed, so now randomness is created as old moves to win the game work no more. So the issue can be closed.


39% Issue with H7022

What issue do you have? Please be as thorough and explicit as possible.
Can't change brightness values to above 39%. When set to 100% in Govee app, logs show 39%
Details of your setup.

Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS?
1

Which version of Homebridge/HOOBS do you have?

1.0.17

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Raspberry Pi

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
2.7.3

Which Govee devices do you have that are causing issues? Please include product models if applicable.

H7022

Please paste any relevant logs below.

[17/01/2021, 23:21:04] [Govee] [Deck lights ] current brightness [39%].```
Note that they are actually at 100%

Hi @jpiestrak
I've just released v2.8.0 which should fix the brightness for your device.
Thanks for reporting this!
Ben

Hi @jpiestrak
I've just released v2.8.0 which should fix the brightness for your device.
Thanks for reporting this!
Ben


Integration broken w/VLAN in 5.5+ (including recent beta)

Any version of HA from 5.5 onwards (including the new 6.1) breaks the LIFX integration for me. Existing bulbs show offline and do not come back even if the integration is reloaded. If I delete and re-add the integration, it doesn't discover any bulbs at all. I've tried with the built in integration and this beta via HACs, same behavior.
I'm wondering if this has to do with my VLAN. My bulbs site on a different VLAN on my network (192.168.40.x my "regular" subnet is 192.168.1.x). HA is configured for both networks, can ping items on both from the console, including the bulbs themselves (which I have configured statically on that VLAN). Prior to 5.5 it discovered them just fine. In fact my current "solution" is rolling back to the last backup I have of 4.7, at which point they start working again.
Did something change and perhaps HA no longer looks beyond it's default interface for bulb discovery? If so that will break more setups than mine, it's fairly common to put "IOT" stuff on a separate VLAN.
Appreciate the work on the beta and any insight you can offer!

Networking in HASS got a bit of an overhaul recently. Can you please check Settings -> System -> Network and make sure the interface for each VLAN is active/enabled? The LIFX integration won't send discovery packets to inactive/disabled interfaces.

Networking in HASS got a bit of an overhaul recently. Can you please check Settings -> System -> Network and make sure the interface for each VLAN is active/enabled? The LIFX integration won't send discovery packets to inactive/disabled interfaces.

Thanks! Yes, they are active and enabled, and I can ping both subnets from the HA box, I can even ping the bulbs themselves.

Can you please enable debug logging:
logger:
  default: info
  logs:
    homeassistant.components.lifx: debug
    custom_components.lifx: debug

Then let HASS run for at least 3-5 minutes after fnishing startup and then either pastebin the lines that include either homeassistant.components.lifx or custom_components.lifx or if you prefer, email them to<EMAIL_ADDRESS>so I can take a look?

All I'm getting in the logs is
[homeassistant.setup] Setup of domain lifx took 0.0 seconds
and
[homeassistant.components.light] Setting up light.lifx
All lights still show unavailable. Also, I'm using the latest LIFX beta via HACS now, but I don't see an option for allowing duplicate discovery - was that removed? The devices page shows it's using the custom component.

Yeah, all the new discovery logic was taken out of the latest beta. I've basically gone back to the original discovery method, but using the new HASS networking. If you've added those lines to your configuration.yaml and you're not getting any DEBUG output in home-assistant.log then something is weird.
Do you have any hard-coded LIFX-related stuff in your configuration.yaml?

Aha. There is something off with auto-discovery on VLANs now.
I added the following config to force HA to look to the correct subnet:
lifx:   light:     - server: <IP_ADDRESS>       port: 56700       broadcast: <IP_ADDRESS>
Rebooted and it works. All devices show up and the logs are full of standard messages re: bulb connections such as:
[custom_components.lifx.light] Connecting to <IP_ADDRESS>
So, good in that there's a workaround, but I suspect this will hit more folks if auto-discovery still doesn't work.

What does your "Network Adapter" section of Settings -> System -> Network look like? That's what controls which adapters HASS uses for discovery.

If you don't have <IP_ADDRESS> enabled as a Network Adapter, then auto-discovery won't happen on that VLAN.

What does your "Network Adapter" section of Settings -> System -> Network look like? That's what controls which adapters HASS uses for discovery.

Aha again! I didn't even notice that section - appears to be new? It was set to auto-configure and picked the first interface, of course, but if I de-select that option I can tell it to monitor my VLAN as well.
I went ahead and backed out the config changes I made to force Lifx discovery on that VLAN subnet, rebooted, and it still works as it should. So that was it  - I'm guessing that was a new setting introduced last month.
Given that it defaults to the "main" interface I suspect some others will see this problem but good to know there's a simple fix. Thanks!

Yep, that controls mDNS/Zeroconf discovery in general, so ensuring all your VLANs are enabled is a good thing. I guess I need to tell more folks about it!
Meanwhile, I'm busy creating a test VLAN to make sure I can reproduce the issue and for future regression testing purposes.
I'm going to go ahead and close this issue for now. Please do open a new one if you notice anything weird, though.


Adds BorderStyle property to TabPageSelector

Currently, TabPageSelector adds a default border to the circles it generates. This does not fit all UI designs. This PR adds BorderStyle property to TabPageSelector.
Fixes: #92328
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

This looks good, just some trivial feedback.
It would help a bit if the TabPageSelector API doc mentioned TabPageSelectorIndicator and if somewhere we explained how the selectors are rendered (in terms of borderColor, borderStyle).

Hey, sorry I was away for a while. IMO the docs do explain the working of each parameter, what according to your opinion might add more meaning to the docs?

@chinmoy12c - what I meant in https://github.com/flutter/flutter/pull/92436#pullrequestreview-806486764 was that the TabPageSelector class API doc doesn't mention that it builds TabPageSelectorIndicators and the TabPageSelectorIndicator class API doc doesn't mention borderStyle (it does mention borderColor and backgroundColor).


[HTML/JS] Syntax highlighting is wrong when  is commented out

VSCode Version: 1.10.2 / 1.11.0-insider
OS Version: Windows 10

The syntax highlighting fails when // ]]></script> is in the same line.

<head>
    <title>Example</title>
</head>

<body>

    <script type="text/javascript">// <![CDATA[

        var a = 'xy';

    // ]]></script>

</body>

This has to to with the single line comment on line // ]]></script>.
The embedded JS parser will skip the whole line.
This has to do with the way TextMate embeds grammars. The embedded grammar doesn't know of the outer language end tags. The only fix would be not embed the regular JS grammar but have a special JS grammar just for source embedded in HTML.

This issue was moved to textmate/html.tmbundle#53

@aeschli is there planned to solve in vscode for milestone april? (i havn't found in the milestone list)

I will update the html grammar to the latest. Hopefully that fixes the issue.

@aeschli okay thanks, can you inform me, when there is in the insider version so i will test it

The grammar got update...

@aeschli thanks a lot, it works. always great job.

@aeschli not sure it's related but the latest vscode broke my highlighting,
i guess it's because of that fix here ?!
my html file was an angular template like:
<h1> my file</h1>
</script>```
i understand that it might be hard to add support for those kind of things, but is there a work arround ?

@eMerzh Sounds like a dup of textmate/html.tmbundle#62


Extending Observable - static of method

While talking with @jayphelps about ActionsObservable from redux-observable/redux-observable, it's come up once or twice that someone would need to create an ActionsObservable from an array or set of values...
Currently, this means you have to manually override static of in the ActionsObservable if you want to get an ActionsObservable as a result.
I think we could possibly change the static of method to do something like this:
static of(...values) {
  const observable = new this.constructor();
  const scheduler = undefined;
  if (values[values.length - 1] instanceof Scheduler) {
    scheduler = values.pop();
  }
  observable.source = new ArrayObservable(values, scheduler);
  return observable;
}

This would mean that extended classes like ActionsObservable would be able to benefit from of without needing to override it.
Risks

I'm not sure what this would mean for things like Subjects yet. I'd have to dig in, but I can't imagine why someone would create Subject with Subject.of.
I suspect TypeScript will hate this... because there's not really a great way to determine the returned type. We do know it should always at least be an Observable, though.
I have only ran into one use case for this so far, and that's ActionsObservable.

Workaround
The current workaround if you needed this sort of thing is to simply implement static of yourself, (which is basically the same as above):
static of(...values) {
  const observable = new MyObservableType();
  const scheduler = undefined;
  if (values[values.length - 1] instanceof Scheduler) {
    scheduler = values.pop();
  }
  observable.source = new ArrayObservable(values, scheduler);
  return observable;
}

It's perhaps just a little gross to have to do this?

@blesh I think you actually mean new this()
static of(...values) {
  const observable = new this();
  const scheduler = undefined;
  if (values[values.length - 1] instanceof Scheduler) {
    scheduler = values.pop();
  }
  observable.source = new ArrayObservable(values, scheduler);
  return observable;
}

My initial testing suggests that TypeScript is perfectly fine with this approach. It knows what type this is. Demo

What if implicitly declare instance in demo such as
const action$ = ActionObservable.of()? seems static of's return type are not explicitly reflecting caller if it's inherited class or not.

@kwonoj sorry, I don't follow?
TS seems perfectly okay with const action$ = ActionsObservable.of();
Demo

I refer this , implicit variable
class ActionsObservable extends Observable {
	test(): void {
		console.log('meh');
	}
}

const action$ = ActionsObservable.of();

action$.test(); //Typescript can't infer method in inherited class

shit...
Yep, known issue https://github.com/Microsoft/TypeScript/issues/5863

Another thing about this approach is it would add a layer of indirection for the basic Observable.of(1, 2, 3) use case. There would be two subscriptions involved instead of just one.
That would incur a definite performance hit.

Demo
class Observable {
	static of<T extends Observable>(): Observable & T {
		return new this() as Observable & T;
	}
}

class ActionsObservable extends Observable {
	test(): void {
		console.log('meh');
	}
}

const action$ = ActionsObservable.of<ActionsObservable>();

action$.test();

If we did such a thing, prolly would want to be a signature overload, so people can just omit the generic type for the default base type.
I don't love this...but given how many people don't use TS we can't let it always limit our decisions. Particularly because they'll very likely support polymorphism on this eventually.
The perf hit is the biggest argument against IMO. We'll need to run the test suite and see how much of a hit it ends up actually being.
We could be overly clever and only go down this path when needed...
static of(...values) {
  // etc...
  const source = new ArrayObservable(values, scheduler);

  if (this === undefined || this === Observable) {
    return source;
  } else {
    const observable = new this();
    observable.source = source;
    return observable;
  }
}

The real code is more complex than that. this might be Observable|ArrayObservable|EmptyObservable|etc

I've also used the new this(...) pattern for static creation methods in rxjs-gestures, so add one more use-case.

I don't love this...but given how many people don't use TS we can't let it always limit our decisions.

I wouldn't let TS limit our decisions unless it was going to result in something horribly unergonomic for the large number of Angular 2 users that are using RxJS 5.
It seems like it's a known issue in TypeScript and they're working to resolve it. So I don't think we need any crazy TypeScript workarounds. No reason to junk up code any more than we have for typings issues. We probably just want to document it for the TypeScript users and reference that issue.

Hello, I posted a solution to this approach that works with typescript >= 2.0 on https://github.com/Microsoft/TypeScript/issues/5863 if you're interested

interface IObservableClass<T extends Observable> {
  new (...a: any[]): T
  // ... + other static methods/members of Observable
}

class Observable {
  // The `this:` is the important part here
    static of<T extends Observable>(this: IObservableClass<T>): T {
        return new this();
    }
}

class ActionsObservable extends Observable {
    test(): void {
        console.log('meh');
    }
}

// voilà, no more type specification !
const action$ = ActionsObservable.of();
// acion$ is an ActionsObservable, test() is now known.
action$.test();

@ceymard very cool. I worry about the interop story if we upgrade to TS 2.0 too early. I imagine users of 1.x would be SOL.

@jayphelps I expect adapt 2.0 probably considerable after official public release + ng2's compiler upgrade schedule, as same as introducing 1.8 for module augmentation.

I tried this myself and it seems there isn't a perfect solution for type definition to support this.
Below is code snippet shows it,
export interface ObservableCtor<X, U extends Observable<X>> {
  new(): U;
}

class Observable<T> {
  static of<R, U extends Observable<R>>(this: ObservableCtor<R, U>, ...args: Array<R>): U {
    return new this();
  }

  static ofBaseType<R, U extends Observable<R>>(this: ObservableCtor<R, U>, ...args: Array<R>): Observable<R> {
    return new this();
  }
}

class ActionsObservable<T> extends Observable<T> {}

let c1 = Observable.of(42); //Observable<any>
let c2 = ActionsObservable.of(42); //ActionsObservable<any>

let c3: ActionsObservable<number> = ActionsObservable.of(42); //forcing, supplying correct type
let c4 = ActionsObservable.of<number, ActionsObservable<number>>(42); //forcing, supplying correct type

let b1 = Observable.ofBaseType(42); //Observable<number>
let b2 = ActionsObservable.ofBaseType(42); //Observable<number>

This is because TS currently does not support higher order generic constraint, so there isn't a way to force U to have correct generic type R. Generic constraint Observable<R> in U only affect U is the type of Observable, since constraint type doesn't affect instantiation of U.


kubeadm init tasks fails when executing in private servers running behind a proxy

Describe the bug
kubeadm init task is failing with the below error:
........
..."[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"", "[kubelet-start] Starting the kubelet", "[control-plane] Using manifest folder "/etc/kubernetes/manifests"", "[control-plane] Creating static Pod manifest for "kube-apiserver"", "[control-plane] Creating static Pod manifest for "kube-controller-manager"", "[control-plane] Creating static Pod manifest for "kube-scheduler"", "[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"", "[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s", "[kubelet-check] Initial timeout of 40s passed.", "", "\tUnfortunately, an error has occurred:", "\t\ttimed out waiting for the condition", "", "\tThis error is likely caused by:", "\t\t- The kubelet is not running", "\t\t- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)", "", "\tIf you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:", "\t\t- 'systemctl status kubelet'", "\t\t- 'journalctl -xeu kubelet'", "", "\tAdditionally, a control plane component may have crashed or exited when started by the container runtime.", "\tTo troubleshoot, list all containers using your preferred container runtimes CLI.", "", "\tHere is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:", "\t\t- 'crictl --runtime-endpoint /var/run/crio/crio.sock ps -a | grep kube | grep -v pause'", "\t\tOnce you have found the failing container, you can inspect its logs with:", "\t\t- 'crictl --runtime-endpoint /var/run/crio/crio.sock logs CONTAINERID'"]}
I'm doing below configuration before executing control_plane.yml
cat /etc/systemd/system/crio.service.d/http-proxy.conf (tried with /etc/sysconfig/crio too)
[Service]
Environment=”HTTP_PROXY=http://IP:port"
Environment=”HTTPS_PROXY=http://IP:port"
systemctl daemon-reload
systemctl restart crio
Updated ~/.bashrc with following
export http_proxy=http://IP:port
export https_proxy=http://IP:port
export no_proxy=localhost,<IP_ADDRESS>,master-node-ip,<IP_ADDRESS>/12,<IP_ADDRESS>/16
here, <IP_ADDRESS>/12 is the service CIDR for kubernetes services & <IP_ADDRESS>/16 is the pod network cidr (Provided during kubeadm init)
To Reproduce
Install crio (Manually or by using control_plane.yml)
Perform above proxy related configurations for crio and bashrc
Execute control_plane.yml
Expected behavior
Kubernetes cluster should be deployed successfully with pod network being configured properly.
Desktop (please complete the following information):

OS: CentOS 8.3

Additional context
I tried with /etc/environment and /etc/profile for proxy configuration, also tried passing the proxy variables as environment variables in kubeadm init task.
Kubernetes Issue is also created for the same. https://github.com/kubernetes/kubernetes/issues/103489

Closing the issue as it was due to invalid configuration in the proxy server.


More intervals on duration function

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
In CEL, the duration() function can only take values in:
Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".

What would the ideal solution look like to you?
For policy authoring, being able to do days/weeks/months etc would make it easier to translate requirements such as within the last 2 weeks or last 7 days
Anything else?
No response

This limitation is likely for the same reason as Go not supporting other units

There is no definition for units of Day or larger to avoid confusion across daylight savings time zone transitions.


UI - wrong asset instance in Teams redirection

Affected module
UI
Describe the bug
When you go to the Team Assets, there are tables, schemas and database listed there. For some reason, open metadata redirects all schemas and databases that belong to a Team to non existent tables, i.e., by default all assets are considered tables instances and when you click on a schema/database instance, you get error because open metadata can't find such table.
To Reproduce
Screenshots or steps to reproduce
Go to Teams -> Assets -> choose schema and click on it -> "Table instance is not found" for a schema instance.
When you click on the schema instance from Team assets window, open metadata is trying to redirect you to the table type. But it's a schema, so we get an error:

Expected behavior
When you click on schema instance, you should go to that schema instance instead of non-existent table.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: 0.10.1
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

This has been taken care of in #5043


Add Tic-80 support

Please add tic-80 emulator

While the emulator is available, none of the included themes in Emulationstation for ArkOS support Tic-80 currently.  Will wait until at least nes-box supports it and then will add this emulator.

Thank you for your reply. Should I ask NesBox to add the theme for Emulationstation?

Hello, The TIC80 core is listed at Retroarch. So I launched retroarch 64. Installed TIC80 by downloading the core. Created a directory /home/roms/tic80 and copied tetric.tic. Enbled logs in retroarch. Launch retroarch, load the core, load the tetris.tic content. The screen turns black and then returns to the menu. In the logs:
[INFO] === Build ======================================= [INFO] Capabilities:  ASIMD [INFO] Built: Nov 22 2020 [INFO] Version: 1.9.0 [INFO] Git: 175205c1e6 [INFO] ================================================= [INFO] [Input]: Found input driver: "udev". [INFO] [CORE]: Loading dynamic libretro core from: "/home/ark/.config/retroarch/cores/tic80_libretro.so" [INFO] [Overrides]: No core-specific overrides found at /home/ark/.config/retroarch/config/TIC-80/TIC-80.cfg. [INFO] [Overrides]: No content-dir-specific overrides found at /home/ark/.config/retroarch/config/TIC-80/tic80.cfg. [INFO] [Overrides]: No game-specific overrides found at /home/ark/.config/retroarch/config/TIC-80/tetris.cfg. [INFO] [Environ]: SET_SUPPORT_NO_GAME: no. [INFO] [Environ]: GET_LOG_INTERFACE. [INFO] [Environ]: GET_CORE_OPTIONS_VERSION. [INFO] [Environ]: GET_LANGUAGE: "0". [INFO] [Environ]: RETRO_ENVIRONMENT_SET_CORE_OPTIONS_INTL. [INFO] [Remaps]: remap directory: /home/ark/.config/retroarch/config/remaps [INFO] Saving files in content directory is set. This overrides other save file directory settings. [INFO] Saving save states in content directory is set. This overrides other save state file directory settings. [INFO] [Overrides]: Redirecting save file to "/roms/tic80/tetris.srm". [INFO] [Overrides]: Redirecting save state to "/roms/tic80/tetris.state". [INFO] [CONTENT LOAD]: Loading content file: /roms/tic80/tetris.tic. [INFO] Did not find a valid content patch. [INFO] [Environ]: SET_PIXEL_FORMAT: XRGB8888.
Your help would be welcome

Tic-80 support has been added with the latest update.  Just go the Options section and select update to receive the latest updates.  You can also review this changelog for a list of all the rest of the included updates.

Hello and thank you for your work. The update is installed. Now a Tic80 menu and the installed games are displayed. But I still have the same launch problem as before. I don't know if it's caused by emulationstation, retroarch or ArkOS. And no error in the Retroarch log. Do you have an idea ?

.tic games launch without issue for me.  I tested mario bros., up dog, and cauliflower power.

I flashed the sdcard and after updating everything works. Thank you for everything.


When I use the radian in vscode to open a new R terminal , the first line code always run "conda activate base" , then pop up an error

I know how to use conda to set the python's envs, But here I can't find out how to set to cancel running this line of code "conda activate base", when I run the select line in the Radian terminal.

How to set to cancel running the code "conda activate base"? Thanks a lot.

This issue seems to be more a python/conda/vscode issue and possibly has nothing to do with vscode-r.
See microsoft/vscode-python#13464


add support for optional catch binding

Fixes #382.
Tests rely on esprima 1953 or they will throw early:
  1) general test try statement:
     AssertionError: expected [Function] to not throw an error but 'Error: Line 1: Unexpected token {' was thrown
      at testIdentity (test/test.js:14946:23)
      at runTest (test/test.js:14974:9)
      at test/test.js:14983:17
      at Array.forEach (<anonymous>)
      at Context.<anonymous> (test/test.js:14981:41)

This PR can hibernate until there's progress on esprima's end, and until esprima dependency version bumps to 4.x+.

Any update on this?

@cixel

https://github.com/estools/escodegen/pull/398 is merged
Can you update this PR?

If here will be no actions in the next few hours, i'll recreate this PR with updated esprima dependency.

Sorry, I've been away. It may be simplest for you to recreate the PR, I haven't touched this stuff in a while.

Yep. I already did
https://github.com/estools/escodegen/pull/403

Good stuff. Thanks!


Allow partition devices in DEVS=

Right now docker-storage-setup does not allow partition devices in DEVS=. For people who don't use lvm on root disk and don't create a volume group, this can be problematic. Now they don't have an extra disk and they can create a paritition on root disk and pass to dss.
If we allow partition devices in DEVS=, then one can easily create a partition on root disk and use that to carve out thin pool.

Some AWS instance are created from EBS and have no "root filesystem" LVM VG associated with it. So we  have:
|<- boot partition->|<--root partition--.....>|
So we may need to partition the "root" partition into 2 partitions: one for the kernel use and one  to be used as block storage for devicemapper lvm-direct thinpool:
|<- boot partition->|<--root partition-->|<---free block partition for LVM VG--->|
Note: See an example here:
http://kumar-pravin.blogspot.com/2015/10/setting-up-storage-to-make-docker.html

So if you have a separate partition, you can simple create a volume group with that partition and pass that volume group to docker-storage-setup?
Say you have /dev/vdc1 partition free. Then do vgcreate docker-vg /dev/vdc1 and pass VG=docker-vg in /etc/sysconfig/container-storage-setup.

Yes! The partition must be marked as "8e" partition type which is "Linux LVM"


TF-Keras module name

I know that it is minor, but it would ease things out to rename the folder TF-Keras.
Then we can just git clone repo & import.
Otherwise python doesn't like dashes in module/package names.

Thanks for pointing that out. I have changed the folder name. Commit - 32d83f560b6b
If you're using Native TF then I would suggest to try the TensorFlow Addons Implementation.
Closing the issue.

Yep, trying that now, but I think it requires nightly.

@mehmetalianil Please refer to this issue thread on how to import Mish from TFA - https://github.com/tensorflow/addons/issues/683#issuecomment-552015320
As of now yes it requires the dev-nightly but TFA is planning to have the next release pretty soon, the delay is because of the migration to TF 2.0.


labels change to map/slice has an issue during config export

@imikushin, @ibuildthecloud: when i do a docker inspect on containers, the labels look correctly. so i'm not sure why the labels aren't coming out correctly during the rancherctl config export -f
this was discussed in https://github.com/rancherio/os-services/pull/6#issuecomment-98489965

FYI, the array is due to the marshalling of the new types. I will be creating a PR soon to correct this.


Add libgeotiff port

Libgeotiff is an open source library normally hosted on top of libtiff for reading, and writing GeoTIFF information tags.
It depends on tiff, proj4, zlib, libjpeg-turbo and liblzma(thru tiff).

Thanks!


Doc and code cleanup

Codecov Report

Merging #218 (93bfd0f) into master (c0fd289) will decrease coverage by 0.42%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##             master     #218      +/-   ##
============================================
- Coverage     63.18%   62.75%   -0.43%
+ Complexity      629      626       -3
============================================
  Files           100      100
  Lines          2325     2309      -16
  Branches        292      288       -4
============================================
- Hits           1469     1449      -20
- Misses          747      752       +5
+ Partials        109      108       -1

Impacted Files
Coverage Δ

...va/seedu/address/logic/commands/StackUndoRedo.java
67.74% <70.00%> (-11.21%)
:arrow_down:

...java/seedu/address/logic/commands/RedoCommand.java
100.00% <100.00%> (+25.00%)
:arrow_up:

.../seedu/address/logic/commands/RedoableCommand.java
88.23% <100.00%> (-1.24%)
:arrow_down:

...java/seedu/address/logic/commands/UndoCommand.java
100.00% <100.00%> (+18.18%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
77.33% <0.00%> (-9.34%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0fd289...93bfd0f. Read the comment docs.

Please check the latest comments and update accordingly

Btw, I realised that class diagrams were used when they should have been object diagrams. Will be changing.

Change some diagrams to object diagrams.
Expanded upon original class diagram.
Change sequence diagram to use brackets for conditions and align more closely with actual code.
Remove redundant logic class diagram.

I updated UndoRedo1.png to be more representative of the code.
Note that you can have multiple stop points (in case anyone is confused), which has been clarified in one of the tutorials.

LGTM


Chown EFS directory for webapp user

I tried this config file but my webapp user was not able to write to the efs directory. Adding the chown command solved that issue for me. Can you confirm that?

Hi Thomas,
We merged in another pull request that should address this issue-
https://github.com/awslabs/elastic-beanstalk-docs/pull/49
Does that change work for you?
Thanks,
-Michael

The name of the user varies depending on which platform you use. The script avoids user specific permissions by making the folder fully accessible to all users (mode 777). PR49 addresses a bug that caused the file mode to be overridden, so I expect your app to be able to write to the folder regardless of which platform you use.

You're right, that was the problem. Thanks!


fix metamask and wallet connect links

Description
Main documentation page is showing duplicated metamask and wallet connect links which leads to a 404 page
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Thanks for discovering! Looks like they are the wrong case right now in git so I force renamed them instead (in https://github.com/tmm/wagmi/pull/484).
renamed:    docs/pages/docs/connectors/metamask.en-US.mdx -> docs/pages/docs/connectors/metaMask.en-US.mdx
renamed:    docs/pages/docs/connectors/walletconnect.en-US.mdx -> docs/pages/docs/connectors/walletConnect.en-US.mdx


Not possible to debug both Python and Native

Point 2 under enable-mixed-mode-debugging-in-a-python-project does not work.

Similar does step 2. under enable-mixed-mode-debugging-in-a-cc-project not work either. (Yes I installed the Python native development tools with the VS installer )
Is there anything else that I might need to install?

Dokumentinformation
⚠ Redigera inte det här avsnittet. Det krävs för learn.microsoft.com ➟ länkning till GitHub-problem.

ID: 702dd6fa-5ad3-b9c7-04bc-e9431c228623
Version Independent ID: 4d8a2c98-429a-b04e-1489-74475df5951a
Content: Mixed-mode debugging for Python - Visual Studio (Windows)
Content Source: docs/python/debugging-mixed-mode-c-cpp-python-in-visual-studio.md
Product: visual-studio-windows
Technology: vs-python
GitHub Login: @cwebster-99
Microsoft Alias: cowebster

@axelande -- Axel, thank you for your feedback and question.  Please consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

@cwebster-99 -- Courtney, please look into this issue.

Thanks, yes I've searched in all of them for help but none seems to discuss how to enable debugging in C++ when initiate from Python.

Nice, that you update,
I looked for the file discussed in the #6712 but I can't find any ImportAfter:

In the C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC folder I have v150, v160 and v170. In v150 and in v170 I have the paths /platforms/64 but not in v160/ folder.
I created a minimal repo to show the issue that I have: https://github.com/axelande/simple_cpp_python_example
This is the .vsconfig of my VS2022 installation:
{
  "version": "1.0",
  "components": [
    "Microsoft.VisualStudio.Component.CoreEditor",
    "Microsoft.VisualStudio.Workload.CoreEditor",
    "Microsoft.Net.Component.4.8.SDK",
    "Microsoft.VisualStudio.Component.Roslyn.Compiler",
    "Microsoft.Component.MSBuild",
    "Microsoft.VisualStudio.Component.Roslyn.LanguageServices",
    "Microsoft.VisualStudio.Component.TextTemplating",
    "Microsoft.VisualStudio.Component.NuGet",
    "Microsoft.VisualStudio.Component.SQL.CLR",
    "Microsoft.NetCore.Component.Runtime.6.0",
    "Microsoft.NetCore.Component.SDK",
    "Microsoft.VisualStudio.Component.AppInsights.Tools",
    "Microsoft.VisualStudio.Component.DiagnosticTools",
    "Microsoft.VisualStudio.Component.IntelliCode",
    "Microsoft.Component.PythonTools",
    "Microsoft.VisualStudio.Component.VC.CoreIde",
    "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
    "Microsoft.VisualStudio.Component.Windows10SDK.19041",
    "Microsoft.VisualStudio.Workload.Python",
    "Microsoft.VisualStudio.ComponentGroup.MSIX.Packaging",
    "Microsoft.ComponentGroup.Blend",
    "Microsoft.VisualStudio.Component.VC.Tools.ARM64",
    "Microsoft.VisualStudio.Component.UWP.VC.ARM64",
    "Microsoft.VisualStudio.Component.VC.Tools.ARM",
    "Microsoft.VisualStudio.ComponentGroup.UWP.VC",
    "Microsoft.VisualStudio.Component.VC.Redist.14.Latest",
    "Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core",
    "Microsoft.VisualStudio.Component.VC.v141.x86.x64",
    "Microsoft.VisualStudio.Workload.NativeDesktop",
    "Microsoft.Component.NetFX.Native",
    "Microsoft.VisualStudio.ComponentGroup.UWP.NetCoreAndStandard",
    "Microsoft.VisualStudio.Component.Graphics",
    "Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin",
    "Microsoft.VisualStudio.ComponentGroup.UWP.Support",
    "Microsoft.VisualStudio.Workload.Universal",
    "Microsoft.Net.Component.4.6.TargetingPack",
    "Microsoft.VisualStudio.Component.VSSDK"
  ]
}

Thanks for reporting the doc bug! The enable-mixed-mode-debugging-in-a-python-project documentation has been updated to reflect the current workflow.

Information of which components that are required to debug both c++ and Python are missing. (It is more than Python native development tools that is required to do it.) Nice that the picture was edited to represent the current state with Python (native).

@axelande -- Axel, thank you for your followup.
@cwebster-99 -- Courtney, please look into the above comment, which may be documentation-related.

Hi @axelande, can you provide more detail around what doesn't work when only installing the Python native development tools from the VS installer when debugging C++ and Python?

Hi @cwebster-99 I might be a little bit wrong, the documentation can be correct, the problem is that it does not apply for Python running in a venv, running with "global" config works fine. So maybe ok to close, any ideas where I might find support for how to run it from a venv?

Hi @axelande thanks for following up. There's a known general issue with mixed-mode debugging and venvs due to the fact that Python for Windows uses a stub python.exe for venvs (it finds and loads the real python.exe as a subprocess). For Python 38 onward - when starting a debug session, since mixed-mode doesn't support multi-process debugging, it ends up debugging just that stub process, instead of the actual app. For attach scenarios, the workaround is to attach to the right python.exe. For launch/F5, there's no workaround, unfortunately - you'll have to avoid venvs.

Closing the issue as it does not require further documentation update

Maybe you can add something about the limitation of venvs for future reference? I've spend so many hours trying to upgrade to something that isn't possible :(

@cwebster-99 I got some suggestion to create the venv like this : C:\Python310-64\python.exe -m venv venv --symlinks and now it also works to debug with a venv!

Yes, that should also do the trick, since then behavior is identical to the default on Linux and macOS. We should document that. I believe the only catch here is that, by default, only admins can create symlinks on Windows - but this is common for dev scenarios anyway.

@axelande, @int19h -- Axel, Pavel, thank you for your clarifications.
@cwebster-99 -- Courtney, please consider these documentation suggestions.

The workaround has been documented in the documentation as well as the release notes as this is a known issue. #please-close


the html.customData configuration does not work in vue files.

workspace setting.json
{
  "html.customData": ["./.vscode/data-token.json"]
}

data-token.json
{
  "version": 1.1,
  "globalAttributes": [
    {
      "name": "data-token",
      "description": "def token for submit"
    }
  ]
}

It works well in html files.

But it does not work in vue files.

Do I need other configurations to make html.customData configuration work in vue files?

You need to file a issue against the vue extension that you use...


Remove deprecated rendered_component

What is the purpose of this pull request?
Support ViewComponent v3.0.0
https://viewcomponent.org/CHANGELOG.html
What changes did you make?
Remove deprecated rendered_component in favor of rendered_content

Thanks!


ENH:  Class template argument deduction (CTAD) for ImageScanlineIterator, ImageScanlineConstIterator

The use of CTAD would allow writing a for loop to do scanline iteration in a more concise way:
for (ImageScanlineIterator iterator(image, region); !iterator.IsAtEnd(); iterator.NextLine())

(Code refactoring from while loops to for loops is not included with this PR. To be considered for a folllow-up PR!)

An itkStatisticsUniqueLabelMapFilterTest1 test failure from ITK.Linux/Linux-Build9966, at https://open.cdash.org/test/1042206954 It does not seem to be caused by the proposed changes of this PR, as far as I can see. Does anyone have a clue?

That test fails occasionally for unknown reasons, probably something related to threading.

/AZP run ITK.Linux


Update DG: Logic and VersionedInternshipBook

Update logic components in developer's guide
Add VersionedInternshipBook to model-related diagrams

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

Coverage data is based on head (4da51fa) compared to base (0001464).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #133   +/-   ##
=========================================
  Coverage     70.03%   70.03%
  Complexity      641      641
=========================================
  Files           100      100
  Lines          2016     2016
  Branches        221      221
=========================================
  Hits           1412     1412
  Misses          535      535
  Partials         69       69

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Can you make the white titles a default terminal color?

On a white background these titles don't show up. Can you set the color to just the term's default text color?

It does use the terminal's default color (-1) along with the curses.A_BOLD attribute. Nothing is hardcoded to white, could you paste a screenshot of what you're seeing?
v1.18 Release:
https://github.com/michael-lazar/rtv/blob/da5e1b062cf3039b66a8b47d48b7966ba06d792d/rtv/subreddit_page.py#L269
Master Branch:
https://github.com/michael-lazar/rtv/blob/master/rtv/theme.py#L54

Yeah this is strange. On my termux instance the title color is indeed term default. But on my workstation I use https://github.com/chriskempson/base16-shell and that might be causing this. I'll look into it a little more.

Yeah this is a base16 coloring issue, I'll close this for now. Sorry for the noise.


Client Allocation Request for: LSC Co.,Ltd.

Client Allocation Questions
Core Information

Name: LSC Co.,Ltd.
Website / Social Media: https://www.lsccoltd.com/
Region: Asia excl. Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f3qu6u2fmptt2t23lapyu3vapodgu4e6jqmsdwkdmbnffu4oduxurc3cr6j2iw7et7i65vn5j4brhyejaunw2a
Notary Requested: swatchliu

@LSCcoltd Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/1085

Please choose your local notary，thanks!


Evicted pods are not recreated

Describe the bug
Two of three kafka broker pods have been evicted by kubernetes. Operator leaves the cluster in this state (one broker running, two down) instead of recreating the evicted pods.
Steps to reproduce the issue:
Create a cluster with 3 brokers. Force eviction of any pod.
Expected behavior
I would expect that operator notices evicted pods and creates replacements.
Additional context
Observed with operator version 0.10.0 , kubernetes 1.15 on GKE.

@qbast can you attach kafka-operator logs as well as you kafkacluster cr? What triggered the eviction of the pods?

Hello
Log and cr attached:
kafkacluster.yaml.txt
manager.log
This is a dev cluster, so there are other pods on the same node. Eviction was triggered during load test when one of other services started using lots of memory. Then Kafka's usage increased as well and the node ran out of memory which required eviction.

Logs do not show any errors that would explain why pods are not recreated. The operator acts as though those evicted pods are still there thus is not aware that it has to create new ones. Are those pods are still there or were cleaned up by Kubernetes?

The pods were still there after about 10h. Then I deleted them manually.

After deleting them manually did the operator re-create those pods?

Yes. Pretty much immediately.


Fix #7272 - re-Add modulesPath and add error context on module arguments evaluation.

This modification undo the modifications related to modulesPath and use it in the installer to ensure that we do not brake this accidentally.  As there is no module logic for the moment, which can be used to replace the modulesPath argument, I prefer to add it back in the mean time.
In addition, this patch add an error context which, display one extra line of information when --show-trace is used.
while evaluating the module argument `pkgs' in "/home/nicolas/nixos-dev/nixpkgs/foo.nix":
infinite recursion encountered

This error message worked for modulesPath before this modification which re-enables it, and it also works for the now deprecated use of with pkgs.lib;.
@wizeman, can you confirm if this fix your issues?

The second patch add the importsArgs feature after all, to filter attributes which should not come from the module system evaluation, even if they are not present in the extraArgs.

@nbp I'm not having much success with this fix.
I have done exactly like you said in your April 14th's comment in #7272, with the exception that I've added a pkgs argument because I need it in my configuration, e.g.:
{ config, pkgs, lib, hydra_path ? "/some/path/hydra", ... }:

{
  imports = [
    ...
    "${hydra_path}/hydra-module.nix"
  ];
  importsArgs = [ "hydra_path" ];
  …
}

Even though I've applied these 2 commits, I'm getting this error:
building all machine configurations...
error: The option `importsArgs' defined in `/backup/root/src/wizynet/config-homeserv.nix' does not exist.
(use ‘--show-trace’ to show detailed location information)
error: unable to build all machine configurations

With --show-trace:
building all machine configurations...
error: while evaluating the attribute ‘buildCommand’ of the derivation ‘nixops-machines’ at "/nixdev/nixpkgs/pkgs/build-support/trivial-builders.nix":10:14:
while evaluating anonymous function at "/nix/store/dz0v241nyc5bv2x3l5ij54nxfv7m7gab-nixops-1.3pre1455_6ac0752/share/nix/nixops/eval-machine-info.nix":143:46, called from "/nixdev/nixpkgs/lib/attrsets.nix":135:52:
while evaluating the attribute ‘config.system.build.toplevel’ at "/nixdev/nixpkgs/nixos/lib/eval-config.nix":50:5:
while evaluating the attribute ‘config’ at "/nixdev/nixpkgs/lib/modules.nix":82:25:
while evaluating ‘yieldConfig’ at "/nixdev/nixpkgs/lib/modules.nix":69:29, called from "/nixdev/nixpkgs/lib/modules.nix":68:16:
while evaluating ‘fold’ at "/nixdev/nixpkgs/lib/lists.nix":20:19, called from "/nixdev/nixpkgs/lib/modules.nix":75:11:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":27:8:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":75:20, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold’ at "/nixdev/nixpkgs/lib/lists.nix":20:19, called from "/nixdev/nixpkgs/lib/modules.nix":76:13:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":27:8:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":75:20, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold’ at "/nixdev/nixpkgs/lib/lists.nix":20:19, called from "/nixdev/nixpkgs/lib/modules.nix":76:13:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":27:8:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":75:20, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold’ at "/nixdev/nixpkgs/lib/lists.nix":20:19, called from "/nixdev/nixpkgs/lib/modules.nix":76:13:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":27:8:

(...)

while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":75:20, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold’ at "/nixdev/nixpkgs/lib/lists.nix":20:19, called from "/nixdev/nixpkgs/lib/modules.nix":76:13:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":27:8:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
while evaluating ‘fold'’ at "/nixdev/nixpkgs/lib/lists.nix":23:15, called from "/nixdev/nixpkgs/lib/lists.nix":26:34:
while evaluating anonymous function at "/nixdev/nixpkgs/lib/modules.nix":76:25, called from "/nixdev/nixpkgs/lib/lists.nix":26:14:
The option `importsArgs' defined in `/backup/root/src/wizynet/config-homeserv.nix' does not exist.
error: unable to build all machine configurations

Am I doing something wrong?

Can you wrap all option definitions under the config attribute?
{ config, pkgs, lib, hydra_path ? "/some/path/hydra", ... }:

{
  imports = [
    ...
    "${hydra_path}/hydra-module.nix"
  ];
  importsArgs = [ "hydra_path" ];
  config = {
    …
  };
}

@nbp With your latest suggestion it seems to work fine now. Thanks!
So I guess that putting everything under config is needed only if you use importsArgs?

cc @edolstra

Hm, importArgs seems pretty ugly to me. I mean, it requires the user to duplicate a function argument that Nix already knows about:
{ config, hydraPath, ... }:
{
  importArgs = [ "hydraPath" ];
}

Here hydraPath already appears in the function header, so it should be unnecessary to repeat it.
BTW, why do we need modulesPath back?

Apparently, since modulesPath got removed, a lot of people seems to have uploaded a new version of their own clone of the amazon-image.nix file, which unfortunately relies on modulesPath, and there is no simple way to remove it.
Yes, importArgs is ugly, but for the moment Nix language does not give us a proper way to investigate if one argument is necessary or for the evaluation of imports.  (while writing that, I think there might be an ugly way of doing it)
In the mean time, I prefer to add modulesPath back, and add importArgs attribute, as a work-around until we got a proper module-import logic.

If we did not had any issue for introspecting whatever or not an attribute has a default value (see https://github.com/NixOS/nixpkgs/pull/7835#issuecomment-103142770), then we would have had 2 other solutions:
1/ Use tryEval, and use a trial and error on the evaluation of the imports to determine which set of arguments are required for the evaluation of the imports. Which means that we could have a combinatorial complexity on the resolution of the minimal set of arguments which are required by imports.
2/ Have to different values for the module arguments, depending if we are evaluating the imports, or if we are evaluating the modules.  If we are evaluating the imports, then we would be replace any access to _module.args by an assertion, and use the evalModules extraArgs by default.  If we are evaluating the module, then we would resolve _module.args and use the evalModules extraArgs as forced value of the _module.args.

@nbp Uhm, we have a way to introspect whether an argument has a default value:
$ nix-instantiate --eval -E 'builtins.functionArgs ({ x, y ? 123 }: x)'
{ x = false; y = true; }

Ping @nbp. Can you please explain why we need importArgs? It strikes me as a really ugly hack that I'd hate to see in a stable release (because then we'll be stuck with it forever).

Can you please explain why we need importArgs? It strikes me as a really ugly hack that I'd hate to see in a stable release (because then we'll be stuck with it forever).

Indeed, importArgs is a hack to work-around the fact that we are unable to know if an argument is used to compute the closure, or if it used to compute the content of the modules.  Basically, it serves the same purpose as the specialArgs added in #8204, without making a special attribute for it.
I think we should look for a before-closure module logic in a proper way, and I agree that this is an hack for the moment.  I will close this pull request and open a new one for adding error context on the argument evaluation.


why pynetdicom3 is not published at PYPI?

Description
[QUESTION]
pynetdicom is found at PYPI. but pynetdicom3 is not there.
Expected behaviour
we can install as follows
pip install pynetdicom3

Actual behaviour
But we can install as follows.
pip install git+https://github.com/pydicom/pynetdicom3.git#egg=pynetdicom3

also we can use pipenv(Pipfile)
we can define Pipfile as follows. it will works fine.
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[dev-packages]

[packages]
pydicom = "*"
pynetdicom3 = {git = "https://github.com/pydicom/pynetdicom3.git"}

[requires]
python_version = "3.6"

Steps to reproduce
N/A
Your environment
N/A general question.

Although not in trouble up there, but I wish we can do it. it will useful almost all people.

At the moment there are two main reasons:

The plan is to switch back to using pynetdicom as the package name so having a pypi release with the name pynetdicom3 would be confusing/counter-productive.
I haven't finished with the backwards incompatible changes to the most user facing parts of the API (AE and Association) and its easier/better to do that in the current alpha than it would be after a general release.