x/tools/go/generated: parser for https://golang.org/s/generatedcode format

Given that #13560 has been accepted, resolved, and by now, widely accepted by the Go community, I think it can be helpful to have a Go parser for it that tools written in Go could use (if desired).
It's relatively easy to write an ad hoc parser using the regexp package, but it's also possible to write a more specialized one that has less overhead.
I already wrote one a while ago, and it currently lives at github.com/shurcooL/go/generated.
I want to move it out of the repository it's currently in, which contains many miscellaneous Go packages of lower utility and quality. I was originally planning to move it out into a standalone repository on my personal site, but then I thought it might be a good fit under x/tools subrepo, specifically, in the x/tools/go directory, since it deals with Go code. The proposed import path would be:
import "golang.org/x/tools/go/generated"

Hence this proposal. If accepted, I'm happy to maintain it/be the owner. The scope is very narrow, so it should be very low volume of work.
Not sure how this intersects with #17244.
If not accepted, I would likely move it here instead:
import "dmitri.shuralyov.com/go/generated"

(The code is currently MIT licensed, but in either case, I'd relicense it under the Go license.)
/cc @andybons @bradfitz @alandonovan @matloob @ianthehat

Is the only concern about the regular expression its speed? If so, I'd rather improve the speed of regexp instead. There are some performance issues for the package already, so one of them may already cover this particular expression: #11646 #26623 #21463
I realise that the regex package may take a while to be fast even for this one case, but I don't think there's a sense of urgency to have a faster implementation of it in x/tools.

Can the predicate be expressed as a function of the AST? Very often the tools that need this predicate have already parsed the file.
package astutil

// Generated reports whether the file was generated by a program,
// not handwritten, following the conventions described in #13560.
// The syntax tree must have been invoked with the ParseComment flag.
// Example:
//   f, err := parser.ParseFile(fset, filename, parser.ParseComment|parser.ImportOnly)
//   if err != nil { ... }
//   g := Generated(f)
func Generated(f *ast.File) bool { ... }

It seems like a good fit for the x/tools/go/astutil package since it doesn't add any dependencies.

Regular expressions are great for experimenting with complicated patterns, but you don't need the regexp package. for an expression this trivial:
strings.HasPrefix(line, "// Code generated ") && string.HasSuffix(line, " DO NOT EDIT.")

This POSIX-compliant grep command has worked fine for my needs in shell scripts:
grep -Exq '^// Code generated .* DO NOT EDIT\.$' "$file"
# Exits 0 if $file matches.

In my case, I'm not concerned about a false positive of that line occurring in a block comment or in a raw string literal.

Is the only concern about the regular expression its speed?

No. I wanted to avoid the regexp dependency because it was easy to implement the matching behavior myself.
The regexp package can still be optimized independently of this code.

Can the predicate be expressed as a function of the AST?

Good question. I'd be curious to try. I expect it should be possible, but I'm not sure if it'd be faster.
Note that not only comments would have to be checked in the AST, but raw string literals as well. A .go file with the following code needs to be reported as a positive match for the pattern:
package p

import "fmt"

func Foo() {
	const s = `this is a raw string literal. it happens to contain
some text in column 1, including a string that matches
the "Code generated ... DO NOT EDIT." comment, like so:
// Code generated  DO NOT EDIT.
to product a correct result, it needs to be detected`
	fmt.Println(len(s))
}

Since it does in fact contain a line of text that matches the regular expression ^// Code generated .* DO NOT EDIT\.$.

This POSIX-compliant grep command has worked fine for my needs in shell scripts:

Indeed. It's very quick and easy to implement a parser for https://golang.org/s/generatedcode format in any language that has support for regular expressions. This package is meant to be available for use by tools that are written in Go, and prefer to avoid incurring the cost of spawning a process or importing the regexp package.

In my case, I'm not concerned about a false positive of that line occurring in a block comment or in a raw string literal.

Those are not false positives. According to the spec, a file is considered generated if a matching line of text appears anywhere in the file, which can include block comments and raw string literals.

Those are not false positives.

Good to know that grepping this way shouldn't hit any false positives then :)

This package is meant to be available for use by tools that are written in Go

Anecdotally: my most frequent case for needing to check whether a file is auto-generated has been to manually filter through go list output in a shell script, to decide whether a file should be run through go fmt. So for me, it would be more helpful if I could use {{if .Generated}} as part of a template passed to go list -f. But changing go list is not this issue.

This would be a 1-declaration 1-line package. We try to avoid those. Please propose a new method or top-level function in an existing package, like probably go/ast.

Ping @dmitshur; see previous comment.

I agree with your comment @rsc that this would be a small package, and it's better to avoid that in x/tools.
I've been thinking about where this functionality could fit into existing packages, and I have some initial thoughts I can share. Please note this isn't a final proposal; just an iteration I want to share. I'm not completely happy with it and wouldn't want it implemented as is.
WIP Counter-Proposal Revision 1
Out of the existing packages, this functionality seemed to belong most in go/parser. The API surface of the change would be somewhat large. It would involve a new parser.Mode:
// A Mode value is a set of flags (or 0).
// They control the amount of source code parsed and other optional
// parser functionality.
//
type Mode uint

const (
	PackageClauseOnly Mode             = 1 << iota // stop parsing after package clause
	ImportsOnly                                    // stop parsing after import declarations
	ParseComments                                  // parse comments and add them to AST
+	GeneratedComment                               // determine whether the file contains a "// Code generated … DO NOT EDIT." line comment
	Trace                                          // print a trace of parsed productions
	DeclarationErrors                              // report declaration errors
	SpuriousErrors                                 // same as AllErrors, for backward-compatibility
	AllErrors         = SpuriousErrors             // report all errors (not just the first 10 on different lines)
)

When the mode is turned on, parser.ParseFile would perform additional work to determine if the .go file has a "// Code generated … DO NOT EDIT." line comment.
(There is some precedent to this in the go/build package, specifically the ImportComment import mode.)
In order for parser.ParseFile to report the result, ast.File in go/ast package would also need to be modified:
// A File node represents a Go source file.
//
// [...]
type File struct {
	Doc        *CommentGroup   // associated documentation; or nil
	Package    token.Pos       // position of "package" keyword
	Name       *Ident          // package name
	Decls      []Decl          // top-level declarations; or nil
	Scope      *Scope          // package scope (this file only)
	Imports    []*ImportSpec   // imports in this file
	Unresolved []*Ident        // unresolved identifiers in this file
	Comments   []*CommentGroup // list of all comments in the source file
+	Generated *Comment // a "// Code generated … DO NOT EDIT." line comment; or nil
}

At first, this seemed like the most appropriate place in existing packages to add this functionality. However, after considering the details more closely, it doesn't seem like a good fit.
The "// Code generated … DO NOT EDIT." comment lives in parallel to the actual AST structure of a file. According to the spec, such a comment can appear inside a block comment, and it would still count. It can also appear within a raw string literal, and match. The work that must be done to determine if a .go file has such a comment has very little to do with parsing the actual AST of a .go file.
WIP Counter-Proposal Revision 2
An alternative proposal to consider is to add this functionality to go/build package in the following way. Add a GeneratedComment import mode, similar to the existing build.ImportComment:
 // If ImportComment is set, parse import comments on package statements.
 // Import returns an error if it finds a comment it cannot understand
 // or finds conflicting comments in multiple source files.
 // See golang.org/s/go14customimport for more information.
 ImportComment
+
+// If GeneratedComment is set, determine which .go files contain
+// a "// Code generated … DO NOT EDIT." line comment,
+// and populate GeneratedGoFiles with the results.
+// See golang.org/s/generatedcode for more information.
+GeneratedComment

The result would be populated in a new build.Package field:
type Package struct {
	// ...

	// Source files
	GoFiles          []string // .go source files (excluding CgoFiles, TestGoFiles, XTestGoFiles)
	CgoFiles         []string // .go source files that import "C"
	IgnoredGoFiles   []string // .go source files ignored for this build
	InvalidGoFiles   []string // .go source files with detected problems (parse error, wrong package name, and so on)
+	GeneratedGoFiles []string // .go source files containing a contains a "// Code generated … DO NOT EDIT." line comment; populated only if GeneratedComment mode is set
	CFiles           []string // .c source files
	// ...

This approach seems to be cleaner than adding something to go/parser and ast.File, but I'm not sure if it's good either. The information about whether or not a file is generated feels like it should belong at the file level, not the package level.
There's also the factor that golang.org/x/tools/go/packages is meant to be used instead of go/build by now, so adding something new to go/build doesn't seem like a good idea.
A "WIP Counter-Proposal Revision 3" section can/should be added where a similar approach as in revision 2 can be evaluated for the golang.org/x/tools/go/packages package.
Conclusion
I would lean towards either putting this proposal on hold (or waiting to iterate on it further), or outright declining it. I made the proposal because I was planning to move the existing package, and wanted to check if there'd be a more fitting place for it in x/tools. It seems the existing package doesn't meet the criteria for inclusion.
Additionally, given how easy it is to parse the generated comment with just regexp, there isn't a high demand for this functionality as far as I can tell (e.g., github.com/shurcooL/go/generated currently has only 1 known public importer), so it's unclear if the additional work of integrating it into an existing package is justified at this time.

@dmitshur Let's discuss this in person. Per @golang/proposal-review we're ok with adding a utility function iff we can decide on a good place for it and a good API.

I'm reluctant to add more fields to structs - it seems like a bit overkill.
And adding GeneratedGoFiles to go/build means removing those files from GoFiles, which would break existing users.
It seems like we could use the current parser with PackageClauseOnly | ParseComments
(or the whole file if you are not concerned about how much gets parsed)
and then just provide a
package ast

func IsGenerated(f *ast.File) bool

What do you think?

I'm reluctant to add more fields to structs - it seems like a bit overkill.
And adding GeneratedGoFiles to go/build means removing those files from GoFiles, which would break existing users.
It seems like we could use the current parser with PackageClauseOnly | ParseComments
(or the whole file if you are not concerned about how much gets parsed)
and then just provide a
package ast

func IsGenerated(f *ast.File) bool

What do you think?

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

The suggestion in https://github.com/golang/go/issues/28089#issuecomment-759652604 seems good to me so far. I'll elaborate on some minor details below.
Since there's no error return value, I understand it would be a pre-condition that the input provided to IsGenerated has been computed correctly. That is, IsGenerated will return false even if the original file was actually generated, but the AST parser wasn't configured correctly (e.g., it left out ParseComments). This should be fine as long as it's documented and there's a simple usage example.
I think using *ast.File instead of something like io.Reader or filename string (what the dmitri.shuralyov.com/go/generated API uses) makes more sense after the spec redefinition in #41196, since the entire file no longer needs to be scanned.
I myself wrote this package primarily as an exercise to test that it would be possible to implement a parser for the spec proposed in #13560, since that was an important goal. I haven't yet used it anywhere. pkg.go.dev reports one known importer in github.com/fatih/faillint/faillint, see faillint.go#L115-L119. It's an analysis.Pass that has access to parsed AST, so this supports that func IsGenerated(f *ast.File) bool is a good signature.

The suggestion in https://github.com/golang/go/issues/28089#issuecomment-759652604 seems good to me so far. I'll elaborate on some minor details below.
Since there's no error return value, I understand it would be a pre-condition that the input provided to IsGenerated has been computed correctly. That is, IsGenerated will return false even if the original file was actually generated, but the AST parser wasn't configured correctly (e.g., it left out ParseComments). This should be fine as long as it's documented and there's a simple usage example.
I think using *ast.File instead of something like io.Reader or filename string (what the dmitri.shuralyov.com/go/generated API uses) makes more sense after the spec redefinition in #41196, since the entire file no longer needs to be scanned.
I myself wrote this package primarily as an exercise to test that it would be possible to implement a parser for the spec proposed in #13560, since that was an important goal. I haven't yet used it anywhere. pkg.go.dev reports one known importer in github.com/fatih/faillint/faillint, see faillint.go#L115-L119. It's an analysis.Pass that has access to parsed AST, so this supports that func IsGenerated(f *ast.File) bool is a good signature.

Based on the discussion above, this proposal seems like a likely accept.
If this is a misreading of the
— rsc for the proposal review group

Based on the discussion above, this proposal seems like a likely accept.
If this is a misreading of the
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group


Sluggishness while typing in latest VSCode Mac OS X

Type: Performance Issue
I have disabled all extensions and turned hardware acceleration off.  I have installed latest version of VSCode.  Whenever I type in any file type I get a very sluggish response.
STRANGELY when I have the Issue Reporter window open the issue goes away.  When I close the Reporter window the issue returns.  So my current workaround will be to leave the Issue Reporter window open.
I have profiled the issue and will attach to the ticket.  Code status below.
➜  newprojectest code --status
Version:          Code 1.79.2 (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:58:52.392Z)
OS Version:       Darwin x64 21.4.0
CPUs:             Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)
Memory (System):  64.00GB (37.16GB free)
Load (avg):       2, 2, 2
VM:               0%
Screen Reader:    no
Process Argv:     --crash-reporter-id dadb597a-32b7-4a27-9fb2-3b890bd9c186
GPU Status:       2d_canvas:                              unavailable_software
canvas_oop_rasterization:               disabled_off
direct_rendering_display_compositor:    disabled_off_ok
gpu_compositing:                        disabled_software
metal:                                  disabled_off
multiple_raster_threads:                enabled_on
opengl:                                 disabled_off
rasterization:                          disabled_software
raw_draw:                               disabled_off_ok
video_decode:                           disabled_software
video_encode:                           disabled_software
vulkan:                                 disabled_off
webgl:                                  unavailable_software
webgl2:                                 unavailable_software
webgpu:                                 unavailable_software
CPU %   Mem MB     PID  Process
5      197   10161  code main
0      197   10164     gpu-process
0        0   10166     utility-network-service
6      524   10167  window [1] (test.js — newprojectest)
1       66   10429  ptyHost
0        0   10815       /bin/zsh -il
0        0   11631       /bin/zsh -il
0        0   11854         bash /usr/local/bin/code --status
0       66   11863           electron-nodejs (/Applications/Visual Studio Code.app/Contents/MacOS/Electron /Applications/Visual Studio Code.app/Contents/Resources/app/out/cli.js --ms-enable-electron-run-as-node --status)
0      131   10483  shared-process
0       66   10484  fileWatcher [1]
0      131   10485  extensionHost [1]
0       66   10486       electron-nodejs (/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=10485)
0       66   10747       electron-nodejs (/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/markdown-language-features/server/dist/node/workerMain --node-ipc --clientProcessId=10485)
0      590   10595     window
0      262   10600     utility-process
0      393   10773  window [3] (score.test.js — mectest)
0       66   10788  fileWatcher [3]
0       66   10789  extensionHost [3]
1      197   11614  window [5] (Welcome)
0       66   11615  fileWatcher [5]
0       66   11616  extensionHost [5]
Workspace Stats:
|  Window (score.test.js — mectest)
|  Window (test.js — newprojectest)
|    Folder (newprojectest): 4 files
|      File types: json(1) js(1) md(1) ts(1)
|      Conf files:
|    Folder (mectest): 717 files
|      File types: js(360) csv(74) json(73) woff(8) woff2(8) txt(6) html(4)
|                  md(3) dist(3) docx(3)
|      Conf files: package.json(1)
VS Code version: Code 1.79.2 (Universal) (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:58:52.392Z)
OS version: Darwin x64 21.4.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremetal: disabled_offmultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: unavailable_software

Load (avg)
2, 2, 2

Memory (System)
64.00GB (37.19GB free)

Process Argv
--crash-reporter-id dadb597a-32b7-4a27-9fb2-3b890bd9c186

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
   16	   197	 10161	code main
    0	   197	 10164	   gpu-process
    0	     0	 10166	   utility-network-service
    0	   524	 10167	window [1] (test.js — newprojectest)
    0	    66	 10429	ptyHost
    0	     0	 10815	     /bin/zsh -il
    0	     0	 11631	     /bin/zsh -il
    1	   131	 10483	shared-process
    0	     0	 11892	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	    66	 10484	fileWatcher [1]
    0	   131	 10485	extensionHost [1]
    0	    66	 10486	     electron-nodejs (/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=10485)
    0	    66	 10747	     electron-nodejs (/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/markdown-language-features/server/dist/node/workerMain --node-ipc --clientProcessId=10485)
    0	   590	 10595	   window
    0	   262	 10600	   utility-process
    0	   393	 10773	window [3] (score.test.js — mectest)
    0	    66	 10788	fileWatcher [3]
    0	    66	 10789	extensionHost [3]
    0	   197	 11614	window [5] (Welcome)
    0	    66	 11615	fileWatcher [5]
    0	    66	 11616	extensionHost [5]
    3	    66	 11889	window [6] (Issue Reporter)

Workspace Info
|  Window (score.test.js — mectest)
|  Window (test.js — newprojectest)
|    Folder (mectest): 717 files
|      File types: js(360) csv(74) json(73) woff(8) woff2(8) txt(6) html(4)
|                  md(3) dist(3) docx(3)
|      Conf files: package.json(1)
|    Folder (newprojectest): 1 files
|      File types: js(1)
|      Conf files:;

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30773603
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30766890
pythongtdpath:30769146
dh2dc718:30770000
pythonidxpt:30772539
pythondjangots:30772535
pythonnoceb:30773526

Update, the issue seems to go away any time I have a non-editor window open in VSCode.  For example having the Process Explorer open also makes the editor quick again.

Profile-20230626T104826.txt
Could not attach dump from Profile test as .json so attaching here as .txt

Similar problems happen here. I often write latex using vscode and with other panels editing python scripts and running them interactively. The sluggishness started about a week or two ago, and I made a clean reinstall of latest vscode but the issue lingers.

Does the issue repro with our exploration build

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


fix i2c_readlist() function and detect whether ftdi driver used before enable/disable it

As we discussed here:
https://github.com/adafruit/Adafruit_Python_GPIO/issues/36
i2c_readlist() function should work with this change.
And most people don't have ftdi driver installed,just add a path exists detect to before load or unload it.

hiya thank you for the pull request. we're going to be deprecating this library in favor of our python3 Blinka library which has support for almost 200 different drivers, and a wide variety of linux computers as well as ft232h


[BUG] Calendar not working inside modal.

Describe the bug
Calendar not working inside modal.
<x-adminlte-input-date name="idDisabled" value="2020-10-04" :config="$config" disabled/>
I am using this modal
<x-adminlte-modal id="DetailsModal" title="" theme="purple" icon="fas fa-eye" size='lg'>
How can i use calendar,select2 inside modal.

Please, share a minimal example of code that we can use to test/investigate the issue, and explain what it's not working.

My code in modal

Design View

Modal

Please, share a minimal example of code that we can use to test/investigate the issue, and explain what it's not working.

https://github.com/jeroennoten/Laravel-AdminLTE/issues/1201#issuecomment-1644639003

Please, give details about the issue, and use Github Code Blocks to share the code. Also, try to create a minimal example of code that reproduces the issue, do not share all of your development code.

Please, give details about the issue, and use Github Code Blocks to share the code. Also, try to create a minimal example of code that reproduces the issue, do not share all of your development code.

I want to popup a calendar on modal body. But this is not working. How can i popup a calendar on modal boy for collect date of birth. Please help me.

Sorry, but I don't have the time to create and share a working example for your use case. I was expecting this from your side. However, and since you are loading the blade component using an AJAX call be sure to use the render() method on the controller to return the view. Also, replace @section('js') ... @endsection with @push('js') ... @endpush on your main blade view, the one that triggers the AJAX call, since @section() replaces a whole section and you may stack code in this situation.


[Question] Directories and files used

:question: Question

Doubt part 1:
hello, could you help me to confirm the path of the files?
I'm working with Luna's base, and from what I've noticed, the path to my files would be:
opt/data/Task016_Luna/raw
right?

Doubt part 2:
The other question is about the use of the following files:
annotations.csv,
candidates.csv,
candidates_V2.zip,
evaluationScript.zip,
sampleSubmission.csv,
seg-lungs-LUNA16.zip,
These files are at the base of Luna, but I was in doubt if they are used and in which directory they are placed.
In addition to all these files, there are subsets, that goes from 0 to 9, and from what I have understood these goes in opt/data/Task016_Luna/raw
Is it right?
If possible, could you help me?
I look forward to hearing from you about the support on these points
Thank you very much!

Dear @aldemirfilho ,
yes the paths should be correct (the script will automatically check that the paths exist and will raise Errors otherwise). The annotations.csv needs to be placed into the raw directory to generate the masks.
Apart from the data / annotations, the evaluationScript will be needed in the end to compute the FROC according to the LUNA guidelines, i.e. there is a list of candidates positions which will be ignored (neither count as True Positive nor False False Positives) during evaluation (nnDetection does not include these ignore positions, so the scores computed by it will be lower than the official score computed via the provided script).
Best,
Michael

Thank you so much! I will try this.
Aldemir Melo.


Set utf8 encoding in initdb

refer #992

LGTM. The locale is a more complicated question, but UTF-8 is pretty much universal nowadays.


Init in .mm not in .h

TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:

Look at TGMapView.h
Look at TGMapView.mm
See that initWithCoder is only defined in the .mm and not the header

RESULT:
Everything works fine.
EXPECTED RESULT:
Everything works fine.
ENVIRONMENT:
Not Applicable
OTHER:
I'm wondering if leaving initWithCoder out of the header and internal header was an oversight. I'm still able to refer to that init in my swift code, so no problems here. If initWithCoder is intentionally left out of the headers, why? I am willing to try and make a PR to fix it if this is an omission.

The declaration of initWithCoder is inherited from UIView, so there shouldn't be any problems using it. I think it was left out of the header because there isn't any reason for user code to call it.

Thank you for the explanation! As this was intentional and not a mistake, I am closing this issue.


Add readonly property to schema

ref comment

Thanks for the contribution, @kfrp!  Let's also add a test for this.  Amending test_edgeql_introspection_meta_default_03 seems like a good target (select readonly alongside required, the __type__ link should be readonly: True).

Thanks for the contribution, @kfrp!  Let's also add a test for this.  Amending test_edgeql_introspection_meta_default_03 seems like a good target (select readonly alongside required, the __type__ link should be readonly: True).


Upgrade to .NET 4.6.1

Upgraded to .NET 4.6.1, you can increment the nuget version and deploy a more modern version of this package. It would be nice to get this in .NET core as well.

Hi @tt9 - how about skipping .NET 4.6.1 and implementing .NET Standard 1.3 or 1.2 or something?

@tt9 👋 Heya. I know this is an old PR, but we've started some discussions in #22
So i'm going to close this as another PR will be doing this work. Please subscribe to #22 to get some more info when things get released .... if you're still interested/care.


Should the command line have in node-template?

in bin/node-template
Can we provide cli command?
For example:
getheight
getblock
transfer etc.

I don't understand what you want to say with this issue. Please use proper English and explain better what you want. Ty.

I don't understand what you want to say with this issue. Please use proper English and explain better what you want. Ty.

Both bitcoin and Ethereum nodes have command lines
It will be much more convenient
For example, we want to query a block

Both bitcoin and Ethereum nodes have command lines
It will be much more convenient
For example, we want to query a block

@honeywest you can access a CLI like that here: https://github.com/polkadot-js/tools/tree/master/packages/api-cli

@honeywest you can access a CLI like that here: https://github.com/polkadot-js/tools/tree/master/packages/api-cli


Use three.js as a peer dependency

Configure webpack to continue using THREE globals in script environment, but use three.js as a peer dependency in modular environments.

@lincolnfrog nope! the script examples are unchanged


bitlpm: Document and Fix Descendants Bug

Descendants and Ancestors cannot share the same
traversal method, because Descendants needs to be
able to select at least one in-trie key-prefix match that may not be a full match for the argument key-prefix. The old traversal method worked for the Descendants method if there happened to be an exact match of the argument key-prefix in the trie. These new tests ensure that Descendants will still return a proper list of Descendants even if there is no exact match in the trie.
Note: This does not need a release note because nothing was (yet) relying on this code.

/ci-integration

This code is ready to merge, it has passed its integration tests (which is its only current user).

I had to override branch protection rules to get this merged, which makes me unhappy.


Release: v1.1.6

Coverage remained the same at 100.0% when pulling ccec53535c66516777b65f67a098e17baa50f65a on saskodh:release-v1.1.6 into 73deacd383ff41a9e9138e26d3f341c8de5bc5dd on netceteragroup:master.


xDhcpServerOption: Router variable not working.

No matter what you specify (single string, string array) you get the error
The variable cannot be validated because the value System.String[] is not a valid value for the Router variable.

CategoryInfo          : MetadataError: (:) [], CimException
FullyQualifiedErrorId : ValidateSetFailure
PSComputerName        : localhost

I was not able to reproduce the same error. But could it be that Router is not set because it is missing from parameters in Set-DhcpServerv4OptionValue here ?

The resource xDhcpServerOption was deprecated when the resource DhcpScopeOptionValue was released.  The resource xDhcpServerOption will be removed in the next release.


Provision to get currently displayed items in grid

Related to issue #139 and #132

Thanks for that. I'll have a look at it.

Decided to go down the route of exposing the data items instead. Thanks for looking into this.


--assets return empty value

When trying to retrieve the assets list from distribworks/dkron (github) it returns an empty list.
However using the link asset list we can see a list of assets.
Is there a way to display these in lastversion?

By default, lastversion filters out assets based on platform, to give you the ones "you want".
Perhaps the matching has failed for some reason. You can ignore the platform matching with --filter .:
lastversion --assets --filter . distribworks/dkron

Great! Thanks.


Spontaneous UpdateDeleteMessages call

Good time! I am using tdlight-api version 3.2.54. The application is running on the server. After the history of a certain dialog is loaded, the request is accepted from the telegram server by UpdateDeleteMessages. At that time, not a single message in the client's telegram was deleted. Please explain how this is possible?

One more question. If all work with the Telegram server takes place on the server, then when transmitting TdlibParameters, do I need to set DeviceModel and systemVersion parameters for a specific phone or I can leave the Desktop in DeviceModel?

UpdateDeleteMessages can be sent when messages are unloaded from the memory. In this case from_cache field will be set to true. Also, if is_permanent is set to false, the messages aren't deleted for other users.


Replace sprintf and scanf format specification for long long.

++ #ifdef WIN32
++    #define PRId64 "I64d"
++    #define PRIu64 "I64u"
++ #else
++ 	  #define __STDC_FORMAT_MACROS
++     #include <inttypes.h>
++ #endif
...
void XMLUtil::ToStr(int64_t v, char* buffer, int bufferSize)
{
	// horrible syntax trick to make the compiler happy about %lld
--	TIXML_SNPRINTF(buffer, bufferSize, "%lld", (long long)v);
++	TIXML_SNPRINTF(buffer, bufferSize, "%"PRId64, (long long)v);
}

bool XMLUtil::ToInt64(const char* str, int64_t* value)
{
	long long v = 0;	// horrible syntax trick to make the compiler happy about %lld
--	if (TIXML_SSCANF(str, "%lld", &v) == 1) {
++	if (TIXML_SSCANF(str, "%"PRId64, &v) == 1) {
		*value = (int64_t)v;
		return true;
	}
	return false;
}

Please submit a PR. It just doesn't scale to have changes come in as patches.
And that said, it's unclear to me if PRId64 is generally correct, but it should be discussed in terms of a PR.


Is it possbile to make personal storage within group

OpenPAI Environment:

OpenPAI version: v1.7
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Hardware (e.g. core number, memory size, storage size, GPU type etc.):
Others:

Anything else we need to know:
I created a nfs pv/pvc and set the share:"false" label to pvc. then all the user can use this pvc as their personal storage. Cloud I use the personal storage only for one group?

{
  "data": {
    "groupname": "rtx2080ti",
    "extension": {
      "acls": {
        "storageConfigs": ["rtx2080ti"],
        "admin": false,
        "virtualClusters": ["rtx2080ti"]
      }
    }
  },
  "patch": true
}

@siaimes I mean,  using the personal storage  within group.

@edenbuaa I know what your mean, I also thought you would know what I meant by that piece of code.
Just change data.groupname and data.extension.acls.virtualClusters to your group name, then push the configure to rest server, also you need to revoke previse pushed configure from default group.
Push nfs-storage to group rtx2080ti:
{
  "data": {
    "groupname": "rtx2080ti",
    "extension": {
      "acls": {
        "storageConfigs": ["nfs-storage"],
        "admin": false,
        "virtualClusters": ["rtx2080ti"]
      }
    }
  },
  "patch": true
}

revoke nfs-storage from default group:
{
  "data": {
    "groupname": "default",
    "extension": {
      "acls": {
        "storageConfigs": [],
        "admin": false,
        "virtualClusters": ["default"]
      }
    }
  },
  "patch": true
}

then, just users in group rtx2080ti can use this nfs-storage.

@siaimes great, thanks.


amplify env remove someEnv failed

Describe the bug
I ran amplify env remove someEnv and the cmd threw an error.
Amplify CLI Version
4.11.0
To Reproduce

amplify env add
amplify push
amplify env checkout prod
amplify env remove someEnv

Expected behavior
I was not expecting the remove cmd to error out.
Desktop (please complete the following information):

OS: Mac
Node Version. 12.14

Additional context
The remove cmd threw a few errors, I will paste the output below. Also, it didn't stop executing, my cli was just hung.  Cloudformation did actually delete everything successfully. Here is the output...
amplify env remove staging
? Are you sure you want to continue? (This would delete all the environments of the project from the cloud and wipe out all the local amplify resource files) Yes
⠋ Deleting resources from the cloud. This may take a few minutes...
Deleting env:staging
⠇ Deleting resources from the cloud. This may take a few minutes...(node:12416) UnhandledPromiseRejectionWarning: MissingRequiredParameter: Missing required key 'Bucket' in params
    at ParamValidator.fail (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:50:37)
    at ParamValidator.validateStructure (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:61:14)
    at ParamValidator.validateMember (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:88:21)
    at ParamValidator.validate (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:34:10)
    at Request.VALIDATE_PARAMETERS (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:126:42)
    at Request.callListeners (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at callNextListener (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
    at /Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:86:9
    at finish (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/config.js:379:7)
    at /Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/config.js:397:9
(node:12416) 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: 4)
(node:12416) [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.
(node:12416) UnhandledPromiseRejectionWarning: MissingRequiredParameter: Missing required key 'Bucket' in params
    at ParamValidator.fail (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:50:37)
    at ParamValidator.validateStructure (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:61:14)
    at ParamValidator.validateMember (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:88:21)
    at ParamValidator.validate (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:34:10)
    at Request.VALIDATE_PARAMETERS (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:126:42)
    at Request.callListeners (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at callNextListener (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
    at /Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:86:9
    at finish (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/config.js:379:7)
    at /Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/config.js:397:9
(node:12416) 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: 5)
(node:12416) UnhandledPromiseRejectionWarning: MissingRequiredParameter: Missing required key 'Bucket' in params
    at ParamValidator.fail (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:50:37)
    at ParamValidator.validateStructure (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:61:14)
    at ParamValidator.validateMember (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:88:21)
    at ParamValidator.validate (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/param_validator.js:34:10)
    at Request.VALIDATE_PARAMETERS (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:126:42)
    at Request.callListeners (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at callNextListener (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
    at /Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:86:9
    at finish (/Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/config.js:379:7)
    at /Users/anthonybriglia/.nvm/versions/node/v12.14.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/config.js:397:9
(node:12416) 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: 6)
⠴ Deleting resources from the cloud. This may take a few minutes...

@ambriglia What resources did the environment have that you attempted to delete?

A lot of different ones... S3 buckets, Lambdas, API Gateways, AppSync API, Cognito User Pool, and DynamoDB tables.

I have been removing a few environments over the past couple days and I am now seeing this consistently.

I'm having this issue too.
amplify env remove devorg
? Are you sure you want to continue? (This would delete all the environments of the project from the cloud and wipe out all the local amplify resource files) Yes
⠋ Deleting resources from the cloud. This may take a few minutes...
Deleting env:devorg
⠏ Deleting resources from the cloud. This may take a few minutes...(node:72697) UnhandledPromiseRejectionWarning: BucketNotEmpty: The bucket you tried to delete is not empty
    at Request.extractError (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/services/s3.js:816:35)
    at Request.callListeners (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
(node:72697) 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:72697) [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.
⠦ Deleting resources from the cloud. This may take a few minutes...^C

I have the following resources:

Auth (Cognito User Pool and User Pool Groups)
API (GraphQL)
Function x 3 (Pre Token Trigger, S3 Trigger, and a separate Lambda Function)
Storage x 2 (Content, and DynamoDB)
Hosting (S3AndCloudFront)

I tried emptying the S3 bucket associated with the environment (since the error was that the bucket isn't empty) and now I have another error.
❯ amplify env remove devorg
? Are you sure you want to continue? (This would delete all the environments of the project from the cloud and wipe out all the local amplify resource files) Yes
⠋ Deleting resources from the cloud. This may take a few minutes...
Deleting env:devorg
⠸ Deleting resources from the cloud. This may take a few minutes...
Error in deleting env:devorg
Stack with id amplify-project-devorg-140525 does not exist
Stack with id amplify-project-devorg-140525 does not exist
ValidationError: Stack with id amplify-project-devorg-140525 does not exist
    at Request.extractError (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/query.js:50:29)
    at Request.callListeners (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/Users/nathan/.nvm/versions/node/v13.1.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
⠹ Deleting resources from the cloud. This may take a few minutes...^C

@ambriglia and @ngnathan Are you using different accounts for separate environments?

@ammarkarachi No. Same account for both environments.

@ammarkarachi Same account for both environments for me as well.


Add collectd-monasca role that deploys custom collectd code

Add collectd-monasca role that deploys custom collectd code to send monasca style metrics to Kafka.

I am wondering if the *monasca roles are applicable to open source mantl or if it would be more appropriate for these addons to live somewhere else. ping @stevendborrelli

Updated


easier support for future spark versions

cleaner diff for #381
@andypetrella cherry-picked your commits. please check if it's all right.

LGTM !
you have took the support of %% which is fine by me too


Lauwsj : Integrate DateTimeParser into command and finalize Activity Model

Summary

Remove the DateTimeParser, integrate it inside the Time Attribute
Add test for the time attributes, Resolves #108
add small command to separate typed command such as add t/activity from just add because the latter is generic format, the former is specific format

Detail

Tests done for date time parser
All tests cases have been updated, persons and activities addressbook for testing are separated (meaning in addressbook to test the duplicate persons, there arent any activities)

Checks

[x] Link PR to issue
[x] Add Reviewer
[x] Pass CI

Just some minor comments and clarifications from me, but other than that, it looks good to me. But I think we should let Rama look through and comment on the Time related stuff if she has any, since she is more familiar with those, before we approve?

yeah sure


Anonymous access flag reset to false

I would change it to true then save.   Next time I edit it seems to go back to false.

Duplicate


refactor: remove mentions of the develop branch

:tada: This PR is included in version 1.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


unable to use variable in filter for Get-AzureADAuditSignInLogs

Trying to process a list of users using the script below but it doesnt seem to work correctly. When there are 2 users in the list there are no results and if there are 15 users I get an error message.
`$csv = import-csv -Path "C:\Users\myaccountname\Documents\listofUPNsforsigninlogs.csv"
foreach ($row in $csv) {
Get-AzureADAuditSignInLogs -Filter "UserPrincipalName eq '$row.UserPrincipalName'" -Top 1 |
select CreatedDateTime, UserPrincipalName, IsInteractive, AppDisplayName, IpAddress, TokenIssuerType, @{Name = 'DeviceOS'; Expression = {$_.DeviceDetail.OperatingSystem}}
}
`
Error message I get when there are over 15 users in the list:
Get-AzureADAuditSignInLogs : Error occurred while executing GetAuditSignInLogs
Code: UnknownError
Message: Too Many Requests
InnerError:
RequestId: 42c1c61e-50e5-4178-b12e-e7aba79faaaa
DateTimeStamp: Wed, 27 Oct 2021 22:52:06 GMT
HttpStatusCode: 429
HttpStatusDescription: Too Many Requests
HttpResponseStatus: Completed
At line:6 char:5

Get-AzureADAuditSignInLogs -Filter $filter -Top 1 |

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Get-AzureADAuditSignInLogs], ApiException
FullyQualifiedErrorId : Microsoft.Open.MSGraphBeta.Client.ApiException,Microsoft.Open.MSGraphBeta.PowerShell.GetAuditSignInLogs

I was running into this issue tonight and after lots of searching I came across this page and a post on spiceworks.
The following works:
Get-AzureADAuditSignInLogs -Filter "UserPrincipalName eq 'user@domain'" -Top 1 | Select UserPrincipalName,IPAddress,CreatedDateTime
This works too:
Get-AzureADAuditSignInLogs -Top 1 -Filter "startsWith(userPrincipalName ,'user@domain')" | Select UserPrincipalName,IPAddress,CreatedDateTime
If I replace user@domain with a variable like $user.PrincipalUserName from Get-AzureADUser in either of the lines above, I get the following error complaining about the filter parameter:
Get-AzureADAuditSignInLogs : Error occurred while executing GetAuditSignInLogs
Code: UnknownError
Message: Malformed request. Please reformat your request and try again.
HttpStatusCode: BadRequest
HttpStatusDescription: Bad Request
HttpResponseStatus: Completed
Quick Specs:
PSVersion 7.2.0
PSEdition Core
AzureADPreview <IP_ADDRESS>
Windows 11 Pro

You can't embed a variable's property directly into the string like you're trying to do there.
If you want to include a variable's property in a string, you need to surround the full name with $() (my preference):
Write-Host "userPrincipalName eq '$($user.UserPrincipalName)'"

userPrincipalName eq<EMAIL_ADDRESS>
Or use string concatenation:
Write-Host ("userPrincipalName eq '" + $user.UserPrincipalName + "'")

userPrincipalName eq<EMAIL_ADDRESS>
Or you use a format string with -f:
Write-Host ("startsWith(userPrincipalName ,'{0}')" -f $user.userPrincipalName)

startsWith(userPrincipalName<EMAIL_ADDRESS>
Or with [String]::Format():
Write-Host [String]::Format("startsWith(userPrincipalName ,'{0}')", $user.userPrincipalName)

startsWith(userPrincipalName<EMAIL_ADDRESS>

Proceeding to close this issue as there is no feedback from the customer.


Alert Sound not working on App (windows, chrome) - thanks!

.

If you were able to resolve it yourself, it would be great if you leave some feedback here for others who might have a similar problem.

Embarrassed to say it's my laptop speakers that aren't working! hah, couldn't find a delete of my question so just closed it


Enhance default image to check FLYTE_INTERNAL_IMAGE

Tracking issue
Provides context for https://flyte-org.slack.com/archives/CP2HDHKE1/p1709158841281599
Why are the changes needed?
Some CLI paths like pyflyte run, pyflyte register do not use the image specified by the environment variable FLYTE_INTERNAL_IMAGE in the manner one might expect
What changes were proposed in this pull request?

How was this patch tested?

Setup process
Screenshots
Check all the applicable boxes

[ ] I updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] All commits are signed-off.

Related PRs

Docs link

Yes, ready to merge!

@pingsutw Yes, ready to merge! Thanks for the review 🙇


dev-main-readme

This PR brings in an overhaul to the content of the top-level README file within the repository, hopefully bringing it more in line with other popular open source projects.
This includes a short recap of the recently added "Key features" sections (I felt using it verbatim would lead to an overly long document). However, the full text has been added to the main page of the Wiki, which is now linked to from the README.
Note that this PR will need @mk306-como's approval of the new TWA logo before it can be merged. Until this time, the PR will be marked as a draft.

Given my history with typos, it might be worthwhile seeing if there's an off-the-shelf spell/grammar checking (with a configurable dictionary) action we can automate.

Note that this PR will need @mk306-como's approval of the new TWA logo before it can be merged. Until this time, the PR will be marked as a draft.

Having discussed this amongst a few of us, we believe the most sensible way forward may be to just remove the logo from this PR and merge it, given that it is highly uncertain when/if we get feedback on the logo.

Change of plan: @mk306-como just approved the logo! :-)


Codegen: Generate methods for data class merging

For these classes we can generate a 'raw' counterpart with nullable fields and merge(raw, raw) method to merge them with priority. We than can use usual classes throughout the code. For example,
data class A(val x: Int, val y: String)

will generate
data class RawA(val x: Int?, val y: String?)

fun merge(r1: RawA, r2: RawA): A { ... }

The idea comes from the situation, that on stage of toml parsing, we inevitably will have some of the fields nullable.
However, after merging, we actually won't have nullable fields in almost all cases, and it will be inconvenient to drag through the entire code such fields.
But, we also should consider situation, when even after merging some field will be nullable - additional class can't help in this case

Can be achieved with a compiler plugin. We would like to research compile plugin functionality, so it can be very useful for us.


Can you provide more information about DriveLM-CARLA?

How to get answers to the questions in the full graph of DriveLM-CARLA？

Hi,
thanks for your interest in our work.
Do you mean how we get the ground truth answers?
We collect data in CARLA with a privileged rule-based algorithm. During the data collection, we save privileged information from the simulator and information from the rule-based algorithm about the "triggered" rules for the current decision. So we have a range of metadata about perception-related things and decision-related things.
With this metadata, we constructed a set of heuristics to create questions and answers for DriveLM-CARLA.
Let me know if this answers your question :)
Best,
Katrin

Hi, thanks for your interest in our work. Do you mean how we get the ground truth answers?
We collect data in CARLA with a privileged rule-based algorithm. During the data collection, we save privileged information from the simulator and information from the rule-based algorithm about the "triggered" rules for the current decision. So we have a range of metadata about perception-related things and decision-related things. With this metadata, we constructed a set of heuristics to create questions and answers for DriveLM-CARLA.
Let me know if this answers your question :) Best, Katrin

Thank you for your reply, can you publish the code for the part "constructed a set of heuristics to create questions and answers", or can you provide more detailed information?

Hi,
we have released the full CARLA-data now. It is based on an improved version of PDM-lite which was the base for the two winning entries of the CARLA challenge 2024. We also improved the VQA labels to include VQAs for most CARLA Leaderboard 2.0 scenarios.
You can find the full driving dataset together with the VQA labels and the scripts to generate both in the branch DriveLM-CARLA.


Make the make init-docker faster

The make init-docker takes a lot of time.
This is detrimental to developer experience.
I think the make init-docker should be faster.
(Currently no idea 😇 )

How about using the image docker for Python 3.8 in Docker hub.
We can reduce steps to install python https://github.com/docker-science/cookiecutter-docker-science/blob/master/{{ cookiecutter.project_slug }}/docker/Dockerfile#L7-L11.

How about using the image docker for Python 3.8 in Docker hub.
We can reduce steps to install python https://github.com/docker-science/cookiecutter-docker-science/blob/master/{{ cookiecutter.project_slug }}/docker/Dockerfile#L7-L11.


[Storage] Nightly pipeline failing on PublishDocsToNightlyBranch, likely due to extensions

Since we introduced the new azure-storage-extensions package into main which contains only a c-extension, the docs step of the nightly pipeline has been failing. I don't think we will be able to generate docs for this type of package so disabling it for now is a fine solution to get the pipeline to pass.
Example (can also just look at Storage nightly runs):
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3461703&view=logs&j=f8e040b3-c0ff-5789-0eda-99daaaa3fc1b&t=bf282306-23d8-55b2-36ef-08e066152d1f

This package doesn't currently support the sphinx environment (EG building docs), so we need to just skip validating this package on docs.

@danieljurek @JimSuplizio I dug around the CI a bit to find the exclusion methodology. See #34137


[Feature][dolphinscheduler-dao] expose hikari parameters when deploy on k8s #7910

Purpose of the pull request
https://github.com/apache/dolphinscheduler/issues/7910
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.3-prepare@1d3f77b). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.0.3-prepare    #7911   +/-   ##
================================================
  Coverage                 ?   31.29%
  Complexity               ?     1555
================================================
  Files                    ?      433
  Lines                    ?    14811
  Branches                 ?     1485
================================================
  Hits                     ?     4635
  Misses                   ?     9719
  Partials                 ?      457

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 1d3f77b...aa1cddd. Read the comment docs.


Intermezzo DifferentialEquations.jl and Optim

I implemented a small example of a ball bouncing ball to showcase DifferentialEquations.jl and did an experimental fit with Optim.
Includes:

Solving a second order DiffEq
Using callback functions (event handling) a really nice feature of DifferentialEquations.jl
Calibrating a parameter using Optim
Using the VSC code IDE because the animations are pretty

I plan on adding a few slides showing what DiffEq covers and also what Optim.jl covers

Ah yes, I sometimes forget but still might be better to keep the original
for clarity in the DS. We should not overflow their brains with tricks.
Op wo 20 jan. 2021 09:29 schreef Michiel Stock<EMAIL_ADDRESS>
@MichielStock commented on this pull request.
In notebooks/day2/intermezzo-diffeq-optim.jl
https://github.com/Beramos/DS-Julia2925/pull/42#discussion_r560762336:

+### Optim.jl

+using Optim

+function compute_ODE(p; times=1:0.5:15)

prob = ODEProblem(f₂, u₀,tspan, p)

sol = solve(prob, Tsit5(), saveat=times, callback = cb)

return sol.t , hcat(sol.u...)[1,:]

+end

+time, exp_disp = compute_ODE((9.81, 5e-2))

+scatter(time, exp_disp, label="Experiment", xlabel="Time(s)", ylabel="Displacement (m)")

+function objective(Cd)

_, sim_disp = compute_ODE((9.81, Cd[1]))

return sum((sim_disp.- exp_disp).^2)

I recently learned that sum(abs2, sim_disp.- exp_disp) works as a tidy
alternative
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Beramos/DS-Julia2925/pull/42#pullrequestreview-571970973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYUUXEOISVMB4V2N3WMRM3S22H7HANCNFSM4WFHAJLA
.

Ah yes, I sometimes forget but still might be better to keep the original
for clarity in the DS. We should not overflow their brains with tricks.
Op wo 20 jan. 2021 09:29 schreef Michiel Stock<EMAIL_ADDRESS>
@MichielStock commented on this pull request.
In notebooks/day2/intermezzo-diffeq-optim.jl
https://github.com/Beramos/DS-Julia2925/pull/42#discussion_r560762336:

+### Optim.jl

+using Optim

+function compute_ODE(p; times=1:0.5:15)

prob = ODEProblem(f₂, u₀,tspan, p)

sol = solve(prob, Tsit5(), saveat=times, callback = cb)

return sol.t , hcat(sol.u...)[1,:]

+end

+time, exp_disp = compute_ODE((9.81, 5e-2))

+scatter(time, exp_disp, label="Experiment", xlabel="Time(s)", ylabel="Displacement (m)")

+function objective(Cd)

_, sim_disp = compute_ODE((9.81, Cd[1]))

return sum((sim_disp.- exp_disp).^2)

I recently learned that sum(abs2, sim_disp.- exp_disp) works as a tidy
alternative
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Beramos/DS-Julia2925/pull/42#pullrequestreview-571970973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYUUXEOISVMB4V2N3WMRM3S22H7HANCNFSM4WFHAJLA
.

Good idea!
Op wo 20 jan. 2021 09:38 schreef Michiel Stock<EMAIL_ADDRESS>
@MichielStock approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Beramos/DS-Julia2925/pull/42#pullrequestreview-571977986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYUUXEGUNPDLHGCIARHCMTS22JB7ANCNFSM4WFHAJLA
.

Good idea!
Op wo 20 jan. 2021 09:38 schreef Michiel Stock<EMAIL_ADDRESS>
@MichielStock approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Beramos/DS-Julia2925/pull/42#pullrequestreview-571977986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYUUXEGUNPDLHGCIARHCMTS22JB7ANCNFSM4WFHAJLA
.


Add OpenAPI for the Anchor Platform

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr101.previews.kube001.services.stellar-ops.com


ISSUE: Events not firing when unlocking with user code

Describe the bug
On my FE599, using a user code to unlock the door does not cause a keymaster_lock_state_changed event to be fired. Unlocking/locking with the buttons inside does fire events, with information from the last user code unlock.
Environment (please complete the following information):

OS: Oracle Linux (Redhat/CentOS) 8
Type of device: VMWare ESX Virtual Machine
Home Assistant version: core-2021.3.2
Hassio/Docker/Core? Core
Component version: 0.0.27
Python Virtual Environment
Python version: 3.8.3
Using ZWaveJS.
Lock is an FE599.

Logs
Logs from entering a valid code while the door is locked:
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 1 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 2.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing BE469 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 3.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 4.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 5.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 6.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 7.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing BE469 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 8.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] Utilizing BE469 work around code.
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 9 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 10 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 11 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 12 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 13 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 14 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 15 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 16 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 17 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 18 not enabled
2021-03-15 00:04:42 DEBUG (SyncWorker_15) [custom_components.keymaster] DEBUG: Code slot 19 not enabled
2021-03-15 00:04:42 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.005 seconds
2021-03-15 00:04:43 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":15,"args":{"commandClassName":"Notification","commandClass":113,"endpoint":0,"property":"alarmType","newValue":16,"prevValue":16,"propertyName":"alarmType"}}}', extra='')

2021-03-15 00:04:43 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":15,"args":{"commandClassName":"Notification","commandClass":113,"endpoint":0,"property":"alarmLevel","newValue":2,"prevValue":2,"propertyName":"alarmLevel"}}}', extra='')

2021-03-15 00:04:43 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":15,"args":{"commandClassName":"Basic","commandClass":32,"endpoint":0,"property":"currentValue","newValue":255,"prevValue":255,"propertyName":"currentValue"}}}', extra='')

2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 1 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 2.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing BE469 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 3.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 4.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 5.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 6.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing FE599 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 7.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing BE469 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Ignoring code slot with * in value for code slot 8.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Work around code in use.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] Utilizing BE469 work around code.
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 9 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 10 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 11 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 12 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 13 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 14 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 15 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 16 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 17 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 18 not enabled
2021-03-15 00:04:47 DEBUG (SyncWorker_3) [custom_components.keymaster] DEBUG: Code slot 19 not enabled
2021-03-15 00:04:47 DEBUG (MainThread) [custom_components.keymaster] Finished fetching keymaster data in 0.006 seconds

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I think this may be because my lock is an old one that doesn't send notifications, which means keymaster uses the logic that runs when the lock state changes. However, this lock doesn't actually technically unlock when a user code is entered—it simply opens the latch for a few seconds, then relatches it, keeping it in a state of locked the entire time. I haven't found any configurations to change this behavior. If this is expected behavior, that's certainly fine; I can set up automations based on watching the alarmLevel, but I figured in case it's not expected, I should open an issue.

In HA see what, if anything, fires under the zwave_js_event when you unlock with a code.

No events at all for anything. I'm still new to ZWaveJS, but I think this lock is too old and doesn't send notifications. But it's also possible that there's something wrong with my setup and I'm not getting events when I should be. I have no idea if I have anything in my network that should be causing them. My ZWaveJS debug logs always show only "value updated" messages, and never anything that seems like it would be a notification.

Check to see if the alarmType and/or alarmLevel sensors may be disabled.

They are enabled, and they do get updated correctly.
-------- Original message --------
From: Chris @.>
Date: 3/15/21 14:02 (GMT-05:00)
To: FutureTense/keymaster @.>
Cc: "Gerig, Brent" @.>, Author @.>
Subject: Re: [FutureTense/keymaster] ISSUE: Events not firing when unlocking with user code (#133)
EXTERNAL SENDER: Use caution with replies, links, and attachments.
Check to see if the alarmType and/or alarmLevel sensors may be disabled.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/FutureTense/keymaster/issues/133#issuecomment-799628945, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAAAXKOA6CDFVZYW7A4RALTDZDSFANCNFSM4ZFYTLUQ.
The information in this communication is intended solely for the individual or entity to whom it is addressed. It may contain confidential or legally privileged information. If you are not the intended recipient, any disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited, and may be unlawful. If you have received this communication in error, please notify us immediately by responding to the sender of this email, and then delete it from your system. Taylor University is not liable for the inaccurate or improper transmission of the information contained in this communication or for any delay in its receipt.

The automation/scripts should still fire the notification script off then, if you have created one.

The problem here is that the lock never changes lock statuses. We're watching for lock state changes in order to prevent false fires of the event when e.g. HomeAssistant starts up.
I will look into whether we can still fire these events on alarmLevel and alarmType state changes instead without creating additional noise

Oooooooooooooooh, @brgerig you need this automation then:
# Lock Refresh (work around for zwavejs)
- alias: Lock Refresh
  trigger:
    platform: state
    entity_id: sensor.kwikset_touchpad_electronic_deadbolt_alarm_type_frontdoor
  action:
    - service: zwave_js.refresh_value
      entity_id: lock.kwikset_touchpad_electronic_deadbolt_frontdoor

Adjust the entity_id's to your lock entities.

@brgerig did the above resolve your issue?

It didn't seem to, but I haven't had a chance to look into it thoroughly. I ended up using a couple of template sensors based on another recommendation I found:
    template_door_alarmlevel_frontdoor:
      value_template: >-
        {% if is_state('sensor.connected_keypad_with_lever_alarmtype_frontdoor',"16") and ((as_timestamp(strptime(states.sensor.date_time.state, "%Y-%m-%d, %H:%M")) - as_timestamp(states.sensor.connected_keypad_with_lever_alarmlevel_frontdoor.last_changed)) < 1) %}
          {{ states.sensor.connected_keypad_with_lever_alarmlevel_frontdoor.state }}
        {% else %}
          0
        {% endif %}
    template_door_alarmtype_frontdoor:
      value_template: >-
        {% if ((as_timestamp(strptime(states.sensor.date_time.state, "%Y-%m-%d, %H:%M")) - as_timestamp(states.sensor.connected_keypad_with_lever_alarmtype_frontdoor.last_changed)) < 1) %}
          {{ states.sensor.connected_keypad_with_lever_alarmtype_frontdoor.state }}
        {% else %}
          0
        {% endif %}

That gives me two sensors that stay at 0 until the door is unlocked, then briefly change to 16 and the door code used for anywhere from a second to a minute, then back to 0. Those sensors give me something to use as triggers in my automations that have been really reliable.

OK, this sounds like a good work around for your use case, glad you were able to find a solution that works! I'm not sure how I would add support for this natively without adding a separate code path for this and making it explicitly configurable

This should change with the new zwavejs v7 since the alarmType and alarmLevel are supposed to trigger events now.

OK, this sounds like a good work around for your use case, glad you were able to find a solution that works! I'm not sure how I would add support for this natively without adding a separate code path for this and making it explicitly configurable

Yeah, I agree that it probably shouldn't be anything that should be generically implemented. Especially given...

This should change with the new zwavejs v7 since the alarmType and alarmLevel are supposed to trigger events now.

Oh, well that would be pretty great!

This should be coming in HA 2021.4, so I'm going to close this and let's hope that with the new release this issue is resolved!


Implemented file path retrieval by ID for JDP via JAMO

This PR uses JAMO to fetch the file paths for files with given IDs, which DTS uses to determine whether files have been staged successfully. The good news is that this wasn't difficult to do with JAMO. The bad news is that DTS must be running within LBL's VPN in order to access JAMO.
This feature does have a unit test that runs when the environment variable DTS_ON_LBL_VPN is set (any value will work, even a blank string if the env variable has been previously set). If this env var is not set, the test is skipped. We have to live with this testing gap until we get this feature implemented by the JDP, or until we can access JAMO outside the VPN.
This PR should go in after #16 .
Closes #19

If you set the branch that this should be merged into in place of main, it will (a) not show the commits that are in the other PR, and (b) automatically update the "merge into" branch to main when the other PR is merged into main.

If you set the branch that this should be merged into in place of main, it will (a) not show the commits that are in the other PR, and (b) automatically update the "merge into" branch to main when the other PR is merged into main.

Yup, that makes sense. I just wanted to allow us to pick at these separately in case that's interesting. If you don't mind everything going in at once, I can just rebase this branch against the other one to get rid of the conflicts.

Early days are always the noisiest!


One error found in codes/download_daily_data.py

I was trying to download the ct2ct daily data and found this error.
In codes/download_daily_data.py, there is an error in line 54:
os.mkdir(f"{output_folder}/{scale}/{month}_{day}/")
And the year is missing when creating the folder. It should be:
os.mkdir(f"{output_folder}/{scale}/{year}_{month}_{day}/")
so that when you run line 63 with open(f"{output_folder}/{scale}/{year}_{month}_{day}/daily_{scale}_{year}_{month}_{day}_{i}.csv", 'wb') as file:, it won't report error of No such file or directory.

Thank you so much for reporting it! We will fix it accordingly.

@august-zhu Thank you so much for reporting it! We will fix it accordingly.


ubuntu install dive has mistake

u gave a .deb file for ubuntu/debian file so install dive on ubuntu should use dpkg not apt

apt has been able to install .deb files given on its command line

@chanRoot both a dpkg -i ./dive_0.9.2_linux_amd64.deb as well as apt install ./dive_0.9.2_linux_amd64.deb should work fine --are you having a specific issue installing the deb?


refactor: migrate from @reach/router to react-router@6

https://reactrouter.com/en/6.4.1/upgrading/reach#breaking-updates

Codecov Report

Merging #861 (cb70f1d) into master (71c3524) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #861   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           75        75
  Lines          803       811    +8
  Branches       122       122
=========================================
+ Hits           803       811    +8

Impacted Files
Coverage Δ

src/components/Boards/BoardCard.tsx
100.00% <ø> (ø)

src/components/Home/Hero/Hero.tsx
100.00% <ø> (ø)

src/components/Layout/Header.tsx
100.00% <ø> (ø)

src/components/Routes/Routes.tsx
100.00% <ø> (ø)

src/components/VerifyEmail/VerifyEmail.tsx
100.00% <ø> (ø)

src/hooks/useAuth.ts
100.00% <ø> (ø)

src/index.tsx
100.00% <ø> (ø)

src/components/Board/Board.tsx
100.00% <100.00%> (ø)

src/components/Boards/Boards.tsx
100.00% <100.00%> (ø)

src/components/Home/Home.tsx
100.00% <100.00%> (ø)

... and 5 more

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


Setup detox for E2E testing

Setup detox and integrate it with CircleCI for E2E testing on both platforms

⚠ This repository is no longer maintained.
If you are looking for expertise in your next React Native project, feel free to contact us!


Ctrl + click shortcut

Superb work! Excellent extension!
Question: any way to change Alt + d to Ctrl + click?

Hi!
That feature is not supported at the moment. I can try to add it when i have some free time.
Or if you want help me a PR is always welcomed.
Thanks!

I'll dig into it! Would really love to have something similar to ctrl+click :)

Closed for inactivity.


2.0.5 Bump version in README.md and properties.

@rdoeffinger  thanks for the update.
I Have update the library.  It will take some time for it to reflect in maven


Release Rust crates

Need to fix MacOS.

MacOS "fix" coming in #719. Not sure what's the default in ONNX, but seems like we need to set some value.

Note that the checks didn't pick up yet the new gh actions workflow that actually builds & test the package. Can we re-trigger all the workflows?

Note that the checks didn't pick up yet the new gh actions workflow that actually builds & test the package. Can we re-trigger all the workflows?

The new workflow doesn't trigger when only rust files are touched, so it's working as intended. Why do you want the workflow to run? Maybe removing the paths restriction would be better?

good catch; I thought it was just stale. I just updated the e2e test workflow to trigger also for rust/** modifications. Now it's running the checks again, and the build package is triggered, seems to work.

good catch; I thought it was just stale. I just updated the e2e test workflow to trigger also for rust/** modifications. Now it's running the checks again, and the build package is triggered, seems to work.

Sounds good. I'll fix the problem in a different PR (to keep this PR small). It's a bug in the recent nightly https://github.com/rust-lang/rust-clippy/issues/13458

This is tagged as rust-v0.1.0-rc.1 and published as magika and magika-cli. Because it's a pre-release, the version must be explicitly specified:

Crate
Command to use or install

Library
cargo add<EMAIL_ADDRESS>

CLI
cargo install --locked<EMAIL_ADDRESS>


nodejs missing icu- internalization

Issue description
https://nodejs.org/docs/latest-v11.x/api/intl.html#intl_internationalization_support
Appears to compile with non-default no icu option even if the option doesn't appear to be passed in build.
Steps to reproduce
const january = new Date(9e8);
const english = new Intl.DateTimeFormat('en', { month: 'long' });
const spanish = new Intl.DateTimeFormat('es', { month: 'long' });

console.log(english.format(january));
// Prints "January"
console.log(spanish.format(january));
// Prints "M01" on small-icu
// Should print "enero"

prints January for spanish
Technical details
tested with 11, already uninstalled. system/OS has icu installed.

Could you try out this pr:
https://github.com/NixOS/nixpkgs/pull/62447
?
It looks to use icu correctly:
January
enero

(but this is on macOS)

I don't know how to test pull requests, I see they assigned someone. It's pure, so I imagine it should work on linux if it works on macOS. I just realized why the default option didn't work with nix being pure.

There're apparently versions of ICU, with required versions for node. I think it might be ideal to just pass the option that the full ICU version be bundled, instead of system one.


Update ns-winuser-rawmouse.md

Add undocumented flags.

@DJm00n : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@DJm00n : Thanks for your contribution! The author(s) have been notified to review your proposed change.


V1.1.3

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy
[ ] Ensured the license file is being packaged.

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

Seems like the environment varible $SP_DIR is not properly aware of the Python version. This should point to python3.6:
mv: cannot move `/home/conda/feedstock_root/build_artifacts/skijumpdesign_1525450019672/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/static' to `/home/conda/feedstock_root/build_artifacts/skijumpdesign_1525450019672/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python2.7/site-packages/': No such file or directory

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

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

@conda-forge-admin, please re-render.

FYI "Skip branches without appveyor.yml" was not checked in the AppVeyor settings for some reason.
cc @isuruf

Merging this without the hack.

It functions, just doesn't have the css assets loaded, so the web app doesn't look right.


Fix: scraper return same tweets after refresh interval

lets return random tweet from available ones.

Heh, after playing with this, it's so cool i think it should be the same for the twitter api keys case too 😂


Supported Systems not mathcing store oslist

You can see this in action:
https://steamdb.info/app/219150/config/
https://steamdb.info/app/261180/config/
I'm assuming this is all automated so why the mismatch?

It's how developers mark it, there are at least three different support OS flags that have to be updated. It's out of our control.

Well the method you are currently using is clearly incorrect.

We're simply displaying oslist in appinfo, you can go poke game developers to fix it.

Alright thanks. After watching at the app info I see what you are saying.


Liquid Syntax issues with shortcode

{% metagen title="New Title" %} throws an invalid syntax error. `{% metagen "title=New Title" %} doesn't throw an error however only the default meta tags are generated with no title.
Currently using 0.12.1 for eleventy and 1.4.8 of this plugin. I think I'm up to date?

Hello! :wave: @miklb
That is interesting, thank you for bringing it to my attention for v1.4.8 of the plugin. This issue has been fixed in the latest version 1.5.2
Go ahead and update to the latest version with npm install eleventy-plugin-metagen@latest, then try running the shortcode in your template again:
{% metagen title="New Title" %}

and it will generate the expected metadata:
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>New Title</title>
<meta name="title" content="New Title">
<meta property="og:type" content="website">
<meta property="og:locale" content="en_US">
<meta property="og:title" content="New Title">
<meta name="twitter:card" content="summary">
<meta name="twitter:title" content="New Title">

I still get the the syntax error with "eleventy-plugin-metagen": "^1.5.2"
Error: invalid syntax at line 1 col 6:

title="New Title"
     ^

Ahhhh yes, I'm sorry this is for .liquid files. The example I posted above was for .njk templates. Give me some time to remedy the issue for Liquid templates and I will get back to you here in this thread :)

Have a look here in the meantime!
https://metagendocs.netlify.app/#liquid_usage

I would like to expand/improve the Liquid support as I've mainly focused on Nunjucks support.
Feel free to try what I mentioned and what is found at metagendocs.netlify.app/#liquid_usage and let me know what you would like to see added, changed or tweaked for better experience for those using Liquid templates (which most 11ty users most likely will since Liquid is the default templating engine)

Gotcha. I'm coming from Jekyll where everything is .html and uses Liquid. I'm having a difficult time passing front matter in includes with Eleventy. I believe that's why I started exploring the other methods of passing the params.

Re-read the metagen docs and global data files sunk in. What's nice is that there's a data cascade so you can set global metatag values and then use data sources at the bottom of the cascade (per post) overrides.
This format for Liquid worked for me.
_data/metadata.json
{
    "title": "New Title"
}

{% metagen metadata %} in my  template.

Although storing your data to pass into metagen within a global data file, if you have your code in a repo on GitHub, I'm happy to have a look as using frontmatter for each "post" or page your trying to generate should be possible.

The issue I was having was passing front matter in included templates. I don't think there will be an issue for markdown files and post specific metagen data.

The issue I was having was passing front matter in included templates. I don't think there will be an issue for markdown files and post specific metagen data.

Ok cool, that makes more sense. The process of passing frontmatter in included templates might get lost or isnt available at that point in the cascade so I see why using a global data file which allows the data to be globally accessible might be the best option for you.
Yeah in a Markdown file using template syntax outside of interpolation ({{ foo }}) like shortcodes (templating utilities) etc will require templateEngineOverride: liquid, md in your Markdown file like:
---
templateEngineOverride: liquid, md
---


Create hover-text for map titles within Explore tab

In the Explore tab, if a map's title is longer than the space allowed in the window, there is no way to see the entire title.
Ideally, the user could hover over the map title in order to see the full title.

@lisaberrygis Please test on DEV: https://livingatlasdev.arcgis.com/policy/browse/?col=41382383bfb24985b7e83532a77c14c8&hs=0&viz=41382383bfb24985b7e83532a77c14c8&loc=-95.319,38.6,3

Looks good. Is there a reason titles seem to cut off when there's still space? Is this a character limit or a space limit?

@vannizhang can the hover text also be added to the summary text?


Truncate description

Add the option to truncate the description in both the list of items area, and in the selected option area (instead of the placeholder)

This might help
https://stackoverflow.com/questions/22808040/fading-out-text-on-overflow-with-css-if-the-text-is-bigger-than-allowed


fix: add depedency array for useeffect

Adds a missing dependency array on a useeffect that was causing it run on every rerender.

Thanks!


Try to fix windows build

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or Other) nor an SPDX license expression.

@cbrueffer i can't push to your PR so i'm using this to track my trial and error. i'm not super familiar with R windows-builds, but i've played around with the pins and the build requirements for windows, although it's not even making it to the build.

@conda-forge-admin, please rerender


Mac binary can't find SDL2

from reddit
Immediately crashes on startup on OS X:
Dyld Error Message: Library not loaded: @rpath/SDL2.framework/Versions/A/SDL2 Referenced from: /Users/USER/Documents/*/Blinky.app/Contents/MacOS/Launcher Reason: image not found

Reproduced the problem on my 10.8.5 by deleting /Library/Frameworks/SDL2.Framework on my machine.  So Blinky.app is not using its bundled SDL2.Framework.  Will have to look at how TyrQuake's Makefile bundle task is working.
Apple Documentation on Embedding Frameworks

Also crashing on 10.9.5

@rpath is missing from the binary.
I ran install_name_tool -add_rpath @executable_path/../Frameworks Blinky.app/Contents/MacOS/Launcher, that made it search for frameworks in Blinky.app/Frameworks directory in addition to /Library/Frameworks.

Awesome :tada:
I'll check if this works later and will add it to the build process.  Thanks!

@nsabovic, updated download links.  thanks again


tr. -> tr (fixes error when extending terminals).

Wow, how did that extra . get in there?  Nice catch Leif, thanks for the pull request.  Merged!