Outputting Vertices from found Exact  Independent Weighted Set

Hi all,
I’m using KaMIS to find the exact Maximum Weighted Independent sets for some small weighted Erdős–Rényi graphs (Number of Vertices< 20)  and am using the functions weighted_branch_reduce & weighted_local_search to do so.
Is there a method to output the vertices that form the found set ? From what I can tell, the  --output method only gives the maximum weight found. This is in contrast to the same method in ReduMIS, which gives the vertices in a maximum unweighted independent set. Is there a special usage  needed to get the maximum weight set out? Or is there a simple code change I can implement to do this ?
Second of all, as these are small graphs compared to the problems solved in this paper, will these methods always give the exact solution?
I’m using a Mac OS 10.15.7 with a C++ installation from Xcode, and followed the instructions in the Github to install the package.

Dear Charlie,
I added the functionality to the program. Let me know if you have any other questions or if there is anything else that we can help you with.
Best
Christian

Dear Prof Schulz,
It works perfectly - thank you so much !
I hope you have a lovely weekend !
Many thanks,
Charlie

On 19 Feb 2021, at 20:08, Christian Schulz<EMAIL_ADDRESS>wrote:
Dear Charlie,
I added the functionality to the program. Let me know if you have any other questions or if there is anything else that we can help you with.
Best
Christian
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/KarlsruheMIS/KaMIS/issues/16#issuecomment-782311668, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGPSSCZ6S7BWRXDTHJ3E3DS73AL5ANCNFSM4X43QQ4A.

Hello @schulzchristian,
I think the committed code is not working with the local search program weighted_local_search.
Here is an example of the execution on the sample weighted graph with the branch and reduce:
$ ./weighted_branch_reduce ../examples/weight_nodes.graph --output=test.txt

reduction_time 4.88758e-05
time 0.00012
MIS_weight 4
MIS_weight_check 4
writing independent set to test.txt ...
$ cat test.txt
0
1
0
1
0
0

and with the local search:
$ ./weighted_local_search ../examples/weight_nodes.graph --output=test.txt
$ cat test.txt
%reduction_time 6.9e-05
%reduction_offset 4
0 0 10

I believe that the problem is located in https://github.com/KarlsruheMIS/KaMIS/blob/60756c80cabe16079c924bf44be5196fc9308637/wmis/app/weighted_ls.cpp#L177:
if (mis_config.write_graph) {
                // just reduce the graph and write it into a file
                graph_access rG;

                auto start = std::chrono::system_clock::now();
                weight_offset = perform_reduction(reducer, G, rG, mis_config);
                auto end = std::chrono::system_clock::now();

                std::chrono::duration<float> reduction_time = end - start;

                std::ofstream output_reduced(mis_config.output_filename);

                output_reduced << "%reduction_time " << reduction_time.count() << "\n";
                output_reduced << "%reduction_offset " << weight_offset << "\n";

                graph_io::writeGraphNodeWeighted(rG, output_reduced);
                return 0;
        }

Thanks!

It should work now.
Thanks for reporting this.
Best
Christian


Creating another milestone.

Hi, group 5. You should create another milestone to get the shared point for creating two milestones.

Nice


Table of contents items persist and duplicate

I'm having an issue with lessons in the table of contents list. When new lessons are created, deleted or renamed, I end up with duplicates and ghost listings.
To reproduce:

Build the starter
gatsby new gatsby-starter-docs https://github.com/ericwindmill/gatsby-starter-docs

Duplicate a lesson and rename, e.g. lesson_five.md, then increment the lesson and chapter numbers in frontmatter

Delete a lesson, e.g. lesson_two.md

Outcome:

Thoughts:

There is a warning about keys in the list items for TableOfContents.jsx

I tried to add keys but still had duplicate posts
< li key={Math.random()}>
and
<li key={node.title()}>

I disabled offline access, but still had ghost listings

There is a relevant reference in Readme:

Configured to auto generate documentation 'Table of Contents' - you just need to follow the file frontmatter conventions in the 'lessons' folder.

Are there any additional conventions or settings to consider?

Changing the implementation of the TOC did not change the issue described by OP. Issue should be reopened imo.


Support for NS1 Managed DNS

Consider adding Support for NS1 edgeDNS, as further step to promote k8gb in community.

NS1 is supported provider by external-dns, we should be able to utilize external-dns capabilities for zone delegation without the need for direct API calls
Split-brain control support is out of the scope until we have more consolidated approach on split-brain management.
NS1 provider needs NS1_APIKEY token to wired to external-dns Deployment as environment variable.

Implemented by https://github.com/AbsaOSS/k8gb/pull/217


HDDS-3492. With hdfs-fuse file implementation 'cp' command is not working - fixed.

What changes were proposed in this pull request?
'cp' (copy) command doesn’t work with hdfs-fuse file system. It works by passing 'cp' command two times for the same file. It mainly happens when destination file doesn’t exists. It happens because when 'cp' command is performed for the first time it creates the file at the destination path, but as per ozone file system protocols any file has no access till its committed. So, 'getattr' function is not able to locate the file(though it’s present at the destination path). Hence, 'cp' command fails in the first go. Second time when 'cp' command is executed, file is already present in the destination path so 'cp' command simply override the data in the file.
This change introduces a new class 'PosixOzoneFileSystem' which creates the file, closes it and again opens it to make the 'cp' command work perfectly.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3492
How was this patch tested?
Tested manually

Thanks to create this patch @aryangupta1998. Don't see any problem with this approach, but neither understand it fully. Is getattr supposed to be working according to POSIX before closing the file?
Do we need to fix it in our side? (Checking the open key tables when we do getFileStatus)

Thanks to create this patch @aryangupta1998. Don't see any problem with this approach, but neither understand it fully. Is getattr supposed to be working according to POSIX before closing the file?
Do we need to fix it in our side? (Checking the open key tables when we do getFileStatus)

@elek Yes 'getattr' is working according to POSIX before closing the file, but first time 'getattr' works before closing of file is to check whether the file exists at destination path or not. But second time 'getattr' doesn’t works before closing of file is when system creates empty file at destination path and opens it to write something but according to ozone filesystem, file is not visible till it’s committed so 'getattr' function fails this time before even closing of file. To address this issue we have raised this PR.

Thanks @aryangupta1998  for the PR and @elek  for review. I will merge this shorty.

Thanks the answer @aryangupta1998, we also discussed it offline, and I try to summarize it:

We have more serious problems, as this is just a workaround for NFS
Even this workaround doesn't solve all the problems. (It creates a 0 size file first, and add content later. This behavior may or may not be accepted by any other tools).
One example: when some configuration is copied to this file system, other service can found it as a zero size file and start with wrong parameters as real content is added later
HBase/Impala/... and other projects have the same problems with Ozone (Should be fixed it in our side) AND with other Object Stores (s3a)
Related Impala bug for exmaple: https://issues.apache.org/jira/browse/IMPALA-9437
But fixing is not easy as there could be multiple parallel file creation (no lease).

TLDR; This seems to be a dangerous workaround. I don't think that it's good solution for production-ready Fuse file system. But it can be a workaround to make possible the further testing of hdfs-fuse with Ozone. As hdfs-fuse is in alpha stage, I am fine to commit it.
But we need to continue to search for a generic, long-term fix (IMHO)

Thanks @elek  for the summary. Created HDDS-3569.


7881 explicit persist side effects layers

Milestone for #7881
This contains the migration of layer creation (from table and analysis node), from the layer-definitions-collection to the user-actions. Also includes the layer move/reordering since that's required for the layer-creation too.
Also tried to make the two big use-cases layer-creation from an analysis node (head or non-head) clearer by having clearly distinct code paths.
@alonsogarciapablo CR, please?

👍 Left some minor comments, but I think this is great! Great job!


Android build error

So this could very well be a configuration error on my end, but I'm getting this error running the cordova android builds:
Error: Missing attribute value for attribute android:pathPrefix of element data
child_process.js:529
throw err;
^
Error: Command failed: cordova build android --device --buildConfig ../devBuild.json --debug
As best I can tell, it's because there is a duplicate path or something? I tried deleting my old app off the branch dashboard and adding a new one using the same path.  Perhaps that screwed it up?  I have no idea how to fix it if that's it.   I thought as long as you had a different key, you could use the same paths?

You were using this build command to add the SDK?
cordova plugin add https://github.com/BranchMetrics/cordova-ionic-phonegap-branch-deep-linking.git --variable BRANCH_KEY=your-branch-key --variable URI_SCHEME=your-app-uri-scheme --variable
And what is the current appearance of your  tags in the config.xml?

I'm currently running installing via npm like so
cordova plugin add branch-cordova-sdk --variable BRANCH_KEY=branchKey --variable URI_SCHEME=uriScheme
The tags in my config.xml look like this:
<branch-config>         <ios-team-id value="5HRW738635" />         <host name="xxxx.app.link" scheme="https" />         <host name="xxxx-alternate.app.link" scheme="https" />     </branch-config>
where the xxxx's are our app prefix in the branch dashboard.  Am I missing something?

After updating the plugin installation to point to the git repo, this problem went away.  I guess it's just not deployed to npm?

Thanks for the heads up on this @gabaum10 - I found the issue (actually multiple) and have confirmed that NPM is resolved now with 2.1.10. I'm not sure how we weren't alerted to this earlier.


Comments on Downloader, posted on 15 Dec, 2014

Test comment.

Test comment with code.

echo $one;

function foo (int $a) {
  return a;
}


Multi-line comment detected within single line comment (c++).

Hi,
The following code has incorrect syntax highlighting. One can verify this by copy-pasting it into the editor.
	if (hasValue == false && nodeId != kGraphNodeIdInvalid)
	{
		//logDebug("reset realTimeSocketCapture");
		//*this = GraphEdit_Visualizer();
	}

	//

	const bool hasChannels = channelData.hasChannels();

	if (hasChannels)
	{

I investigated why, and it's caused by the multi-line comment highlighter running before single line comments are detected. It causes the '/*' in '//*this' above to be interpreted as the start of a multi-line comment. While it should be ignored as it's part of a single line comment. A possible solution would be to detect single line comments together with multi-line ones.
Perhaps eventually to make (multi-line) comments work well across different languages we'll need a separate comment highlighter for each language.

Fixed in 8fbb932.

Thanks, seems to work well!


Use TransformerWorker

Had a few different abstractions.
I think I got caught on trying to abstract away from the initial stream as it was harder to test as it was tied to the SQS implementation.
This moves all the abstractions into a TransformerWorker that takes a stream, store, transformer and sender and follows that flow.
We could probably abstract a few of the pieces out but I want to wait for the work @alicefuzier is doing on the Worker before I do.
Writing tests for the generic TransformerWorker should mean we can just use it in all the palces we want to without having to rewrite it the whole time.

If this isn't used elsewhere, what do we gain by having a generic TransformerWorker as opposed to the same code but with the specialised parameters and 1 less layer of abstraction?

@jamieparkinson I think the plan was to make something generic which could be used within other transformers (as they all work pretty much the same way apart from the Mets transformer)

@warrd @jamesgorrie I guessed that was the case (although I don't think this'll work as-is for the Sierra transformer, either), but I feel like we should only be creating complex abstractions like this at the time that we use them - otherwise we're just making this service more complex.
If we're to stick with this and commit to re-using it, then should it be in /common?

@jamieparkinson yeh agree there is a balance to be had over how much abstraction and when to introduce it (I maybe tend towards the over abstraction at times). In this case I don't think it really adds much complexity / extra cognitive load to understand the code, and helps keeps the transformation of data and processing of the message nicely separated.
I think the Sierra transformer could be updated to fit this pattern without too much work (e.g. this class is basically a Transformer[SierraTransformable], and the HybridRecord message it receives  is key into some store)

@jamieparkinson the reason to do this was to start moving towards a common way of logging, which I would argue hasn't happened as we haven't created the abstraction.
I am working to the rule of threes, I was creating the fourth one, so thought I would abstract it out.
It will make abstracting to the new Worker more easily, and also make creating a new one easier and get rid of the need to think about the shape of a transformer, rather on the transformation logic.

To be clear this is the first step in moving towards having a way to do transformers, I just prefer to do PRs in 1 massive sweep.
Do we not feel that that aim is worth abstracting?

@jamieparkinson on the surface it seems obvious that we should have an abstraction for a transformer as we have 4 of them and they all perform the same basic function - how different that is from the function of any pipeline service is a good question though, i.e. thing in -> do work -> thing out.
I'm tempted to conclude that it is a useful abstraction as transformers also pull records for transformation and have a common set of failure modes worth describing.

To be clear this is the first step in moving towards having a way to do transformers, I just prefer to do PRs in 1 massive sweep.
Do we not feel that that aim is worth abstracting?

I think this is worth abstracting but that large PRs that affect existing code are not a good idea (though they are tempting as it can reduce cognitive load on the author, something I can relate to).

@warrd @jamesgorrie I guessed that was the case (although I don't think this'll work as-is for the Sierra transformer, either), but I feel like we should only be creating complex abstractions like this at the time that we use them - otherwise we're just making this service more complex.
If we're to stick with this and commit to re-using it, then should it be in /common?

That these seems like a "complex abstraction" is a red flag - the underlying commonality between the transformers is not complex and the code should represent that.
I would prefer to see the common behaviours expressed as traits and as you suggest remove these to /common. That might also provide a more effective place to experiment, rather than introducing this to in progress work (of course doing that increases the risk that useful work will be ignored, or never make it to a mergeable state as time pressure pushes on other direct "product work").

Ultimately this is a small change and probably just a thing that we should merge as an experiment (having the abstraction confined to a single transformer is a benefit here).
I think that if we are interested in this approach there must be more tests (IMHO they might have been useful here to drive out a generic transformer) but that it's not a deal breaker to merging this.

To be clear on this, it is probably my own workflow I wasn't clear about.

This is in the direction of an abstraction
I wanted to try and do it on the Calm Transformer as it felt weird to have to setup all the testing / code etc again
I did that in the transformer
I have ambitions to move this out to the other transformers, but didn't want that to become massive PRs


append .zshrc in new line

How does this help?

closing since regarded as invalid

It was marked invalid due to being concomitant with a deluge of Hacktoberfest spam PRs. If we false positived we apologize.
That aside, it's questionable whether this is needed (files generally do have trailing newlines, and readability counts). Furthermore, backslash in double quotes isn't an escape character in all shells (e.g., dash).


internal code uses deprecated APIs

What version of CUE are you using (cue version)?

commit 41b38fe201f40e13f0c23787a615e25f295ac609 (tip as of time of writing)

Does this issue reproduce with the latest stable release?
Yes
What did you do?
Look at the source.
What did you expect to see?
No unnecessary uses of APIs that have been publicly deprecated.
What did you see instead?
Many legacy uses of *cue.Instance and other deprecated functions and types from the cue package.
The project should lead by example and convert its code to use the supported API, both ensuring that the API is fit for purpose and enabling removal of the deprecated APIs in the future.

Here's an initial list of uses of deprecated APIs as reported by staticcheck:
cmd/cue/cmd/add.go:177:8: cue.Build is deprecated: use cuecontext.Context.BuildInstances. The use of Instance is being phased out.  (SA1019)
cmd/cue/cmd/add.go:255:23: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
cmd/cue/cmd/common.go:751:15: cue.Build is deprecated: use cuecontext.Context.BuildInstances. The use of Instance is being phased out.  (SA1019)
cmd/cue/cmd/common.go:806:10: cue.Merge is deprecated: do not use.  (SA1019)
cmd/cue/cmd/common.go:812:17: r.Build is deprecated: use Context.BuildInstance. The use of Instance is being phased out.  (SA1019)
cmd/cue/cmd/common.go:821:9: inst.Build is deprecated: use Context.Build  (SA1019)
cmd/cue/cmd/completion.go:58:14: cobra.ExactValidArgs is deprecated: use MatchAll(ExactArgs(n), OnlyValidArgs) instead  (SA1019)
cmd/cue/cmd/custom.go:45:14: obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
cmd/cue/cmd/custom.go:65:14: tools.Lookup is deprecated: use Value.LookupPath  (SA1019)
cmd/cue/cmd/custom.go:88:7: tools.Lookup is deprecated: use Value.LookupPath  (SA1019)
cmd/cue/cmd/custom.go:96:32: tools.Lookup is deprecated: use Value.LookupPath  (SA1019)
cmd/cue/cmd/custom.go:188:5: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
cmd/cue/cmd/custom.go:192:14: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
cmd/cue/cmd/custom.go:210:16: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
cmd/cue/cmd/custom.go:215:17: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
cmd/cue/cmd/get_go.go:304:9: types.NewSignature has been deprecated since Go 1.18: Use NewSignatureType instead which allows for type parameters.  (SA1019)
cmd/cue/cmd/get_go.go:580:20: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
cmd/cue/cmd/get_go.go:790:7: cv.AddComment is deprecated: use ast.AddComment  (SA1019)
cmd/cue/cmd/get_go.go:847:3: x.AddComment is deprecated: use ast.AddComment  (SA1019)
cmd/cue/cmd/orphans.go:169:14: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
cmd/cue/cmd/orphans.go:240:12: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
cue/ast/astutil/apply.go:314:14: node.Comments is deprecated: use ast.Comments  (SA1019)
cue/ast/astutil/apply.go:467:32: node.Comments is deprecated: use ast.Comments  (SA1019)
cue/ast/astutil/file_test.go:83:10: cue.Runtime is deprecated: use Context.  (SA1019)
cue/ast/astutil/file_test.go:85:17: r.CompileFile is deprecated: use BuildFile. The use of Instance is being phased out.  (SA1019)
cue/ast/astutil/resolve.go:311:18: ast.ParseIdent is deprecated: quoted identifiers are deprecated. Use aliases.  (SA1019)
cue/ast/astutil/resolve.go:423:18: ast.ParseIdent is deprecated: quoted identifiers are deprecated. Use aliases.  (SA1019)
cue/ast/astutil/resolve.go:428:17: ast.ParseIdent is deprecated: quoted identifiers are deprecated. Use aliases.  (SA1019)
cue/ast/astutil/resolve.go:436:17: ast.ParseIdent is deprecated: quoted identifiers are deprecated. Use aliases.  (SA1019)
cue/ast/astutil/util.go:81:22: from.Comments is deprecated: use ast.Comments  (SA1019)
cue/ast/astutil/util.go:98:22: from.Comments is deprecated: use ast.Comments  (SA1019)
cue/ast/astutil/walk.go:59:20: node.Comments is deprecated: use ast.Comments  (SA1019)
cue/build/instance.go:242:17: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
cue/build_test.go:259:7: p.AddFile is deprecated: use AddSyntax or wait for this to be renamed using a new signature.  (SA1019)
cue/format/format.go:292:18: node.Comments is deprecated: use ast.Comments  (SA1019)
cue/format/node.go:90:9: d.Comments is deprecated: use ast.Comments  (SA1019)
cue/format/node.go:95:14: x.Label.Comments is deprecated: use ast.Comments  (SA1019)
cue/interpreter/wasm/wasm_test.go:130:4: inst.AddFile is deprecated: use AddSyntax or wait for this to be renamed using a new signature.  (SA1019)
cue/load/loader_common.go:220:17: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
cue/load/loader_test.go:427:23: cue.Build is deprecated: use cuecontext.Context.BuildInstances. The use of Instance is being phased out.  (SA1019)
cue/marshal.go:65:7: p.AddFile is deprecated: use AddSyntax or wait for this to be renamed using a new signature.  (SA1019)
cue/marshal.go:153:18: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
cue/parser/parser.go:119:28: c.lastChild.Comments is deprecated: use ast.Comments  (SA1019)
cue/parser/parser.go:170:4: c.lastChild.AddComment is deprecated: use ast.AddComment  (SA1019)
cue/parser/parser.go:211:5: n.AddComment is deprecated: use ast.AddComment  (SA1019)
cuego/cuego.go:143:7: instance.Eval is deprecated: use inst.Value().Context().BuildExpr(expr, Scope(inst.Value), InferBuiltins(true))  (SA1019)
cuego/cuego.go:168:18: value.ConvertToRuntime(runtime).Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
doc/tutorial/kubernetes/tut_test.go:24:2: "io/ioutil" has been deprecated since Go 1.19: As of Go 1.16, the same functionality is now provided by package [io] or package [os], and those implementations should be preferred in new code. See the specific function documentation for details.  (SA1019)
encoding/gocode/generator_test.go:19:2: "io/ioutil" has been deprecated since Go 1.19: As of Go 1.16, the same functionality is now provided by package [io] or package [os], and those implementations should be preferred in new code. See the specific function documentation for details.  (SA1019)
encoding/gocode/generator_test.go:52:12: cue.Build is deprecated: use cuecontext.Context.BuildInstances. The use of Instance is being phased out.  (SA1019)
encoding/gocode/gocodec/codec.go:49:15: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/gocode/gocodec/codec_test.go:104:10: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/gocode/gocodec/codec_test.go:211:10: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/gocode/gocodec/codec_test.go:220:18: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/gocode/gocodec/codec_test.go:246:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/gocode/gocodec/codec_test.go:251:17: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/gocode/gocodec/codec_test.go:309:12: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/gocode/gocodec/codec_test.go:339:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/gocode/gocodec/codec_test.go:348:16: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/json/json.go:46:15: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/json/json.go:100:20: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/json/json.go:111:10: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/jsonschema/decode.go:79:13: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/jsonschema/decode_test.go:71:10: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/jsonschema/decode_test.go:80:16: json.Decode is deprecated: use Extract and build using cue.Context.BuildExpr.  (SA1019)
encoding/jsonschema/decode_test.go:82:16: yaml.Decode is deprecated: use Extract and build the File with cue.Context.BuildFile.  (SA1019)
encoding/jsonschema/decode_test.go:123:18: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/jsonschema/decode_test.go:163:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/jsonschema/decode_test.go:169:14: json.Decode is deprecated: use Extract and build using cue.Context.BuildExpr.  (SA1019)
encoding/jsonschema/decode_test.go:174:14: yaml.Decode is deprecated: use Extract and build the File with cue.Context.BuildFile.  (SA1019)
encoding/openapi/build.go:133:17: (*cue.Runtime)(r).Build is deprecated: use Context.BuildInstance. The use of Instance is being phased out.  (SA1019)
encoding/openapi/build.go:133:19: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/openapi/build.go:421:17: v.Reference is deprecated: use ReferencePath  (SA1019)
encoding/openapi/build.go:798:14: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/openapi/build.go:900:17: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/openapi/crd.go:116:11: v.Reference is deprecated: use ReferencePath  (SA1019)
encoding/openapi/crd.go:131:18: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/openapi/crd.go:143:18: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/openapi/decode.go:54:12: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/openapi/decode.go:55:13: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/openapi/decode.go:87:13: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/openapi/decode_test.go:60:10: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/openapi/decode_test.go:68:16: json.Decode is deprecated: use Extract and build using cue.Context.BuildExpr.  (SA1019)
encoding/openapi/decode_test.go:70:16: yaml.Decode is deprecated: use Extract and build the File with cue.Context.BuildFile.  (SA1019)
encoding/openapi/decode_test.go:101:17: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/openapi/openapi.go:151:6: i.IsDefinition is deprecated: use i.Selector().IsDefinition()  (SA1019)
encoding/openapi/openapi.go:168:15: i.Value().Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/openapi/openapi.go:169:17: i.Value().Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/openapi/openapi.go:189:17: val.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
encoding/openapi/openapi_test.go:274:14: cue.Build is deprecated: use cuecontext.Context.BuildInstances. The use of Instance is being phased out.  (SA1019)
encoding/openapi/openapi_test.go:313:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/openapi/openapi_test.go:314:15: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/openapi/openapi_test.go:332:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/openapi/openapi_test.go:333:15: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/jsonpb/decoder.go:127:9: schema.Template is deprecated: use LookupPath in combination with using optional selectors.  (SA1019)
encoding/protobuf/jsonpb/decoder.go:174:14: schema.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/protobuf/jsonpb/decoder_test.go:39:7: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/protobuf/jsonpb/decoder_test.go:50:18: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/jsonpb/decoder_test.go:112:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/protobuf/jsonpb/decoder_test.go:113:15: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/jsonpb/encoder_test.go:35:7: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/protobuf/jsonpb/encoder_test.go:46:18: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/jsonpb/encoder_test.go:64:17: r.CompileFile is deprecated: use BuildFile. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/pbinternal/attribute.go:92:11: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/protobuf/pbinternal/attribute.go:119:11: v.Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/protobuf/textproto/decoder.go:169:12: i.Value().Elem is deprecated: use LookupPath in combination with "AnyString" or "AnyIndex".  (SA1019)
encoding/protobuf/textproto/decoder_test.go:35:7: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/protobuf/textproto/decoder_test.go:49:18: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/textproto/encoder_test.go:33:7: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/protobuf/textproto/encoder_test.go:43:18: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
encoding/protobuf/util.go:52:2: f.AddComment is deprecated: use ast.AddComment  (SA1019)
encoding/protobuf/util.go:53:2: f.AddComment is deprecated: use ast.AddComment  (SA1019)
encoding/protobuf/util.go:78:14: strings.Title has been deprecated since Go 1.18 and an alternative has been available since Go 1.0: The rule Title uses for word boundaries does not handle Unicode punctuation properly. Use golang.org/x/text/cases instead.  (SA1019)
encoding/yaml/yaml_test.go:101:8: cue.Runtime is deprecated: use Context.  (SA1019)
encoding/yaml/yaml_test.go:131:14: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/astinternal/debugstr.go:30:21: n.Comments is deprecated: use ast.Comments  (SA1019)
internal/copy/copy.go:21:2: "io/ioutil" has been deprecated since Go 1.19: As of Go 1.16, the same functionality is now provided by package [io] or package [os], and those implementations should be preferred in new code. See the specific function documentation for details.  (SA1019)
internal/core/dep/dep_test.go:110:8: cue.Runtime is deprecated: use Context.  (SA1019)
internal/core/dep/dep_test.go:111:15: rt.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/core/dep/dep_test.go:116:7: inst.Lookup is deprecated: use Value.LookupPath  (SA1019)
internal/core/export/export.go:192:21: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
internal/core/export/export_test.go:310:8: cue.Runtime is deprecated: use Context.  (SA1019)
internal/core/export/self_test.go:19:2: "io/ioutil" has been deprecated since Go 1.19: As of Go 1.16, the same functionality is now provided by package [io] or package [os], and those implementations should be preferred in new code. See the specific function documentation for details.  (SA1019)
internal/core/runtime/build.go:104:12: p.AddFile is deprecated: use AddSyntax or wait for this to be renamed using a new signature.  (SA1019)
internal/core/runtime/build.go:122:20: internal.PackageInfo is deprecated: use GetPackageInfo  (SA1019)
internal/diff/diff.go:113:13: v.Struct is deprecated: use Fields.  (SA1019)
internal/diff/diff.go:134:13: es.x.Struct is deprecated: use Fields.  (SA1019)
internal/diff/diff.go:147:13: es.y.Struct is deprecated: use Fields.  (SA1019)
internal/diff/diff.go:207:49: cue.FieldInfo is deprecated: only used by deprecated functions.  (SA1019)
internal/diff/diff.go:210:10: cue.FieldInfo is deprecated: only used by deprecated functions.  (SA1019)
internal/diff/diff.go:216:11: x.Struct is deprecated: use Fields.  (SA1019)
internal/diff/diff.go:217:11: y.Struct is deprecated: use Fields.  (SA1019)
internal/diff/diff.go:246:13: cue.FieldInfo is deprecated: only used by deprecated functions.  (SA1019)
internal/diff/diff_test.go:406:10: cue.Runtime is deprecated: use Context.  (SA1019)
internal/diff/diff_test.go:407:14: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/diff/diff_test.go:411:14: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/diff/diff_test.go:455:8: cue.Runtime is deprecated: use Context.  (SA1019)
internal/diff/diff_test.go:456:12: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/diff/diff_test.go:460:12: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/encoding/detect.go:38:10: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/encoding/detect.go:42:15: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/encoding/detect.go:45:15: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/encoding/detect.go:52:12: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/encoding/detect_test.go:90:10: cue.Runtime is deprecated: use Context.  (SA1019)
internal/encoding/detect_test.go:91:17: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
internal/encoding/encoder.go:126:4: cue.ResolveReferences is deprecated: Syntax will now always attempt to resolve dangling references and make the output self-contained. When Final or Concrete is used, it will already attempt to resolve all references. See also InlineImports.  (SA1019)
internal/encoding/encoder.go:277:8: cue.Runtime is deprecated: use Context.  (SA1019)
internal/encoding/encoder.go:278:15: r.CompileFile is deprecated: use BuildFile. The use of Instance is being phased out.  (SA1019)
internal/encoding/encoding.go:106:9: cue.Runtime is deprecated: use Context.  (SA1019)
internal/encoding/encoding.go:108:16: r.CompileFile is deprecated: use BuildFile. The use of Instance is being phased out.  (SA1019)
internal/encoding/encoding.go:284:12: i.Lookup is deprecated: use Value.LookupPath  (SA1019)
internal/filetypes/filetypes.go:101:7: i.LookupDef is deprecated: use LookupPath.  (SA1019)
internal/filetypes/filetypes.go:102:6: v.Fill is deprecated: use FillPath.  (SA1019)
internal/filetypes/filetypes.go:105:10: i.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:111:23: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:120:13: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:135:14: i.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:250:9: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:256:6: v.Fill is deprecated: use FillPath.  (SA1019)
internal/filetypes/filetypes.go:261:17: i.LookupDef is deprecated: use LookupPath.  (SA1019)
internal/filetypes/filetypes.go:264:12: i.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:287:14: i.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/filetypes.go:288:7: i.LookupDef is deprecated: use LookupPath.  (SA1019)
internal/filetypes/filetypes.go:293:9: v.Fill is deprecated: use FillPath.  (SA1019)
internal/filetypes/filetypes.go:295:13: i.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/filetypes/types.go:14:9: cue.Runtime is deprecated: use Context.  (SA1019)
internal/filetypes/types.go:15:7: cue.Runtime is deprecated: use Context.  (SA1019)
internal/filetypes/types.go:29:12: cuegenInstance.Value().FieldByName is deprecated: use LookupPath.  (SA1019)
internal/task/task.go:41:7: c.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/task/task.go:53:7: c.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/task/task.go:63:7: c.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/task/task.go:73:7: c.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
internal/third_party/yaml/decode.go:338:3: expr.AddComment is deprecated: use ast.AddComment  (SA1019)
internal/third_party/yaml/decode.go:356:3: expr.AddComment is deprecated: use ast.AddComment  (SA1019)
internal/value/value.go:31:40: cue.Runtime is deprecated: use Context.  (SA1019)
internal/value/value.go:32:11: cue.Runtime is deprecated: use Context.  (SA1019)
internal/value/value.go:35:28: cue.Runtime is deprecated: use Context.  (SA1019)
internal/value/value.go:36:27: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/encoding/json/manual.go:100:8: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/tool/exec/exec.go:48:8: ctx.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/exec/exec.go:137:15: ctx.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/exec/exec.go:139:9: ctx.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/exec/exec.go:152:17: ctx.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/exec/exec_test.go:52:10: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/tool/exec/exec_test.go:53:17: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
pkg/tool/file/file_test.go:19:2: "io/ioutil" has been deprecated since Go 1.19: As of Go 1.16, the same functionality is now provided by package [io] or package [os], and those implementations should be preferred in new code. See the specific function documentation for details.  (SA1019)
pkg/tool/file/file_test.go:38:8: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/tool/file/file_test.go:39:12: r.CompileExpr is deprecated: use BuildExpr. The use of Instance is being phased out.  (SA1019)
pkg/tool/http/http.go:50:12: ctx.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/http/http.go:51:11: obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/http/http.go:146:7: obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/http/http_test.go:46:8: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/tool/http/http_test.go:47:12: r.CompileExpr is deprecated: use BuildExpr. The use of Instance is being phased out.  (SA1019)
pkg/tool/http/http_test.go:136:9: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/tool/http/http_test.go:137:17: r.Compile is deprecated: use Parse or ParseBytes. The use of Instance is being phased out.  (SA1019)
pkg/tool/os/env.go:106:11: ctx.Obj.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
pkg/tool/os/env_test.go:138:8: cue.Runtime is deprecated: use Context.  (SA1019)
pkg/tool/os/env_test.go:139:12: r.CompileExpr is deprecated: use BuildExpr. The use of Instance is being phased out.  (SA1019)
tools/flow/flow_test.go:161:22: v.Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
tools/flow/flow_test.go:175:19: t.Value().Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
tools/flow/flow_test.go:208:16: t.Value().Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
tools/flow/flow_test.go:215:19: t.Value().Lookup is deprecated: use LookupPath. At some point before v1.0.0, this method will be removed to be reused eventually for looking up a selector.  (SA1019)
tools/trim/trim_test.go:325:10: cue.Build is deprecated: use cuecontext.Context.BuildInstances. The use of Instance is being phased out.  (SA1019)


duplicate node guids in 'empty' sample

The following tundra file gives me an error about duplicate node guids. I am unsure why this is happening. This example is pretty non-functional, but I had the same issue with a slightly more realistic scenario. Naturally, it's my new node that is causing the issue somehow.
local nodegen  = require "tundra.nodegen"
local depgraph = require "tundra.depgraph"

_ios_bundle_mt = nodegen.create_eval_subclass { }

function _ios_bundle_mt:create_dag(env, data, deps)
  return depgraph.make_node {
    Env   = env,
    Pass  = data.Pass,
  }
end

nodegen.add_evaluator("iOSBundle", _ios_bundle_mt, {})

Build {
	Configs = {
		{
			Name = "macosx-gcc",
			DefaultOnHost = "macosx",
			Tools = { "gcc" },
		},
	},
	Units = {
		function()
			Default( Program {
				Name = "HelloWorld",
				Sources = {
					"hello.c"
				},
			} )

			Default( iOSBundle{} )
		end
	}
}

Your generator makes a bunch of nodes that are identical for each configuration, so the DAG generator doesn't know how to separate them. The generators computes a hash based on the action (command line), input and output files (and maybe something else, I forget). This node has nothing, so they all map to the same thing which confuses the subsequent pass. The hashes are used for a couple of things, including automatic filesystem cleanup of build steps that are not present anymore.

I thought that might be the case, which is why I tried removing all but a single configuration.
...
Which means I still have the debug/release/production triplet, so I actually have three configurations. Thanks for the help!


Login failed for user 'sa' on Mac

I bas on Mac.
1- Run docker run --name mssql-container -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=123456' -p 1433:1433 -d microsoft/mssql-server-linux.
It show
Microsoft(R) SQL Server(R) setup failed with error code 1. Please check the setup log in /var/opt/mssql/log for more information.

2- And then I stop and start again, I work
~ docker ps -a
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                    PORTS                    NAMES
43db0fce3c75        microsoft/mssql-server-linux   "/bin/sh -c /opt/mssq"   3 minutes ago       Up 2 minutes

3- Connect with
~ mssql -s localhost -u sa -p 123456 -o 1433
Connecting to localhost...
Error: Login failed for user 'sa'.

Please help me.

@thearabbit '123456' may not be a sufficiently complex password.  Please stop/remove your current container and try running a new container using a more complex password.

@thearabbit Also, you shouldnt need to pass the -o parameter to the mssql command if you are using the default port, 1433.

Look great, I work fine.
Very thank.

Hi Guys ,
I am still having the issue please can someone help me on this .
vvvvvv-MBP:~ xxx$ mssql -s localhost -u sa -p PWSD@Test123
Connecting to localhost...
Error: Login failed for user 'sa'.
vvvvvv-MBP:~ xxx$

Are you using -v in your docker run command?

Thanks Guys.. @twright-msft pointed to the right , password issue.. @rameshrohan Test123 is not a complex password..

Im using this password "reallyStrongPwd1239821Anbasjjh832Kaskhsd" and Im getting same issue
MacBook-Air-de-Joel:~ joelgarcia$ mssql -s localhost -u sa -p reallyStrongPwd1239821Anbasjjh832Kaskhsd Connecting to localhost... Error: Login failed for user 'sa'.

@thearabbit Also, you shouldnt need to pass the -o parameter to the mssql command if you are using the default port, 1433.

Hi,
the docker connected well..it runs. but when i try to run the sql operations studio it gives me the 'Login failed for user ....' What am i doing wrong..been trying everything...nothing

Ran the container using following command: docker run -d --name MSSQLLOCALCOMMUNITY -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=MyStrongPassword@123' -p 1433:1433 microsoft/mssql-server-linux
But when i try to connect to db it yields: Error: Login failed for user 'MSSQLLOCALCOMMUNITY'.

still getting same error,  after having tried multiple times.If anyone could identify whats wrong from my terminal below🥲
mac@Ghosts-MacBook-Pro ~ % docker images REPOSITORY                       TAG           IMAGE ID       CREATED       SIZE mcr.microsoft.com/mssql/server   2019-latest   9ab26f8e5685   5 weeks ago   1.61GB mac@Ghosts-MacBook-Pro ~ % docker ps -a CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES mac@Ghosts-MacBook-Pro ~ % sudo npm install -g sql-cli Password: npm WARN config global --global, --localare deprecated. Use--location=global` instead.
npm WARN deprecated<EMAIL_ADDRESS>The sprintf package is deprecated in favor of sprintf-js.
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
changed 48 packages, and audited 49 packages in 6s
1 package is looking for funding
run npm fund for details
found 0 vulnerabilities
mac@Ghosts-MacBook-Pro ~ % docker run --name GHOST -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=1Unitedrange22’ -e 'MSSQL_PID=Developer’ -p 1433:1433 -d mcr.microsoft.com/mssql/server:2019-latest
5db465b250a8da5e47db009efa694dec025dd30cd0641fd5df84eb062774c424
mac@Ghosts-MacBook-Pro ~ % mssql -u sa -p 1Unitedrange2022
Connecting to localhost...
Error: Login failed for user 'sa'.`

All the logic is in the password, that's why it doesn't log in, it lasted 3 days and I was never able to log in until the day I found these notes, which was the key. exactly was key. It must be very complex and long. mine was the following to be able to practice the change later @Pwd451EatonStrong


Typescript with TSX with a language server

Handling TSX with a language server
Hi. Really love the stuff you guys do and I really love this repo as well as the new improvements.
So. My issue isn't a bug per se, however, I cannot find any resources on this. So I'm basically trying to get the editor to run with TS and the TS language server. So I copied the contents of the json folder and set it up to use typescript which seems to be working beautifully and communicates with the language server. So my issue arises when I use a .tsx extension, then I get nothing from the language server. I had something similar working with .tsx files about 6 months back, from adapting some of the examples in the repo at the time. Possibly just a small config thing I'm likely missing. Let me know if you'd like a PR for your examples if I manage to sort it out 👍
ts language server responding:

Thank you in advance.
Regards
Here's my client code adapted from the json client:
/* --------------------------------------------------------------------------------------------
 * Copyright (c) 2024 TypeFox and others.
 * Licensed under the MIT License. See LICENSE in the package root for license information.
 * ------------------------------------------------------------------------------------------ */
import * as monaco from 'monaco-editor';
import getKeybindingsServiceOverride from '@codingame/monaco-vscode-keybindings-service-override';
// this is required syntax highlighting
import '@codingame/monaco-vscode-javascript-default-extension';
import '@codingame/monaco-vscode-typescript-basics-default-extension';
// import '@codingame/monaco-vscode-typescript-language-features-default-extension';
import { LogLevel } from 'vscode/services';
import { MonacoEditorLanguageClientWrapper, WrapperConfig } from 'monaco-editor-wrapper';
import { configureMonacoWorkers } from '../../common/client/utils.js';

monaco.languages.register({
    id: 'typescript',
    extensions: ['.ts', '.tsx'],
    aliases: ['JSON', 'json'],
    mimetypes: ['text/typescript']
});

const text = `
export const X = () => <div/>;
`;

export const buildJsonClientUserConfig = (params: {
    htmlContainer: HTMLElement
}): WrapperConfig => {
    return {
        logLevel: LogLevel.Debug,
        vscodeApiConfig: {
            userServices: {
                ...getKeybindingsServiceOverride(),
            },
            userConfiguration: {
                json: JSON.stringify({
                    'workbench.colorTheme': 'Default Dark Modern',
                    // 'typescript.tsserver.web.projectWideIntellisense.enabled': true,
                    // 'typescript.tsserver.web.projectWideIntellisense.suppressSemanticErrors': false,
                    'diffEditor.renderSideBySide': false,
                    'editor.lightbulb.enabled': 'on',
                    'editor.glyphMargin': true,
                    'editor.guides.bracketPairsHorizontal': true,
                    'editor.experimental.asyncTokenization': true
                })
            }
        },
        editorAppConfig: {
            $type: 'extended',
            codeResources: {
                main: {
                    text,
                    uri: '/xampp2/htdocs/Ethereal/WebStudio2/backend/src/sandbox/src/hello.tsx',
                }
            },
            useDiffEditor: false,
            monacoWorkerFactory: configureMonacoWorkers,
            htmlContainer: params.htmlContainer
        },
        languageClientConfigs: {
            typescript: {
                languageId: 'typescript',
                connection: {
                    options: {
                        $type: 'WebSocketUrl',
                        url: 'ws://localhost:30000/sampleServer',
                        startOptions: {
                            onCall: () => {
                                console.log('Connected to socket.');
                            },
                            reportStatus: true
                        },
                        stopOptions: {
                            onCall: () => {
                                console.log('Disconnected from socket.');
                            },
                            reportStatus: true
                        }
                    }
                }
            }
        }
    };
};

export const runJsonWrapper = () => {
    const wrapper = new MonacoEditorLanguageClientWrapper();

    try {
        document.querySelector('#button-start')?.addEventListener('click', async () => {
            const config = buildJsonClientUserConfig({
                htmlContainer: document.getElementById('monaco-editor-root')!
            });
            await wrapper.initAndStart(config);
        });
        document.querySelector('#button-dispose')?.addEventListener('click', async () => {
            await wrapper.dispose();
        });
    } catch (e) {
        console.error(e);
    }
};

I don't think you have to do
monaco.languages.register({
    id: 'typescript',
    extensions: ['.ts', '.tsx'],
    aliases: ['JSON', 'json'],
    mimetypes: ['text/typescript']
});

@codingame/monaco-vscode-typescript-basics-default-extension already registers the proper languages, and it probably conflicts with it, since the .tsx extension is defined for the typescriptreact language while you define it as the typescript language
@codingame/monaco-vscode-typescript-basics-default-extension winning is probably the reason it doesn't work: your tsx file is in typescriptreact language, and not typescript
@kaisalmen being only able to set the documentSelector as a languageId is probably too limiting

@kaisalmen being only able to set the documentSelector as a languageId is probably too limiting

@CGNonofr Where does that apply here?
I was just checking if it works with the app playground but it doesn't:
https://typefox.github.io/monaco-languageclient/ghp_appPlayground.html
Can this be configured to support react?

I mean https://github.com/TypeFox/monaco-languageclient/blob/3b48e50a109ffe8248c0e9ff60dd066dfd0b3207/packages/wrapper/src/languageClientWrapper.ts#L183
but it looks like it's overridable by setting clientOptions, that's probably the solution: override the documentSelector to rely on the extension, or at least add typescriptreact

but it looks like it's overridable by setting clientOptions, that's probably the solution: override the documentSelector to rely on the extension, or at least add typescriptreact

ok, I should fix that

Ah, you guys are champs. That looks like the piece I was missing. It looks like just setting the languageId to typescriptreact did the trick 🥳. So for my situation, I'd want to use the ts lang client for .ts and .tsx files. I tried to use the same config as different language entries in the languageClientConfigs but it doesn't like that. I took a bit of a dive into the code; it looks like this could potentially be overcome by specifying an array of languageIds, so I did this:
monaco-languageclient\packages\wrapper\src\languageClientWrapper.ts:173
        const mlcConfig = {
            name: this.languageClientConfig.name ?? 'Monaco Wrapper Language Client',

            // allow to fully override the clientOptions
            clientOptions: this.languageClientConfig.clientOptions ?? {
                documentSelector: Array.isArray(this.languageId) ? this.languageId : [this.languageId], // <- THIS PART
                // disable the default error handler
                errorHandler: {
                    error: () => ({ action: ErrorAction.Continue }),
                    closed: () => ({ action: CloseAction.DoNotRestart })
                }
            },
            messageTransports
        };

And perhaps for backwards compatibility some TS like this:
type LanguageClientConfigOneLanguage = {
    name?: string;
    languageId: string;
    connection: ConnectionConfig;
    clientOptions?: LanguageClientOptions;
    restartOptions?: LanguageClientRestartOptions;
}
type LanguageClientConfigMultiLanguage = {
    name?: string;
    languageIds: string[];
    connection: ConnectionConfig;
    clientOptions?: LanguageClientOptions;
    restartOptions?: LanguageClientRestartOptions;
}

export type LanguageClientConfig = LanguageClientConfigOneLanguage | LanguageClientConfigMultiLanguage;

(...and some stuff in between.)
The above is just an idea
Anyway. Thanks again for the help, that's got me sorted. Let me know if you'd like a PR
Thanks
Kind regards

@RoddoWasHere thank you for the idea. I looked again at the default wrapper config behaviour and I think we should remove the ambiguity to have both the full clientOptions override and the simple default. Instead it should be joined. We haven't released a new major version, yet. So it is a good time to introduce breaking changes:
What do you think about this: https://github.com/TypeFox/monaco-languageclient/pull/780

@RoddoWasHere the PR automatically closed the issue. Let us know if you disagree with the solution.


Upgrading Protractor to >4.0.5  causes installation issue

Bug report

Node Version: node v7.0.0
Protractor Version: ~4.0.5
Browser(s): Chrome
Operating System and Version Mac

Installing protractor with version above 4.0.5 makes install fail with
npm ERR! code E403
npm ERR! user xyz is not allowed to access package @types/q : @types/q
Everytime I try to install, it is a different package permission issue.
@types/node : @types/node
@types/selenium-webdriver : @types/selenium-webdriver

Hi there!
This sounds like an issue with your system / environment and not an issue with Protractor itself.
Because of this, your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!


Add Cookie Handling, Fix Publish Date, and Update Element Selectors

Added cookie confirmation handling as per issue #87. This update allows the script to click on the cookieOption button, accept only the forcedCookies, and then proceed with the login process.
Fixed the publish date issue as referenced in issue #84.
Updated text-based element xPath references to use selectors instead, to avoid issues with different browser languages. This change will prevent the script from getting stuck searching for words that may not be present in certain languages.

TODO: Further improve selector usage by incorporating wildcards where appropriate for better code readability.
During the development process, @TheJoin95 and I discussed the possibility of using class-based elements or selector-based elements for referencing xPath elements. I considered using wildcards in the selectors to improve code readability, but I haven't implemented them yet due to uncertainty about whether to adopt selector-based or class-based elements. For now, I've kept it simple and used selectors without wildcards.
@abe-101, I'd appreciate your feedback on these changes and any suggestions you might have on whether to pursue selector-based or class-based elements for future updates.
VT

Thanks for handling the cookie panel, it will solves a lot of issue I believe.
On the publish/confirm/days selectors: you are using some classes defined by the bundler, which will change at every spotify release.
We should avoid using those kind of classes.
Instead, since the issue may came from a different language set on the account, we should fix this by set at the start (when we are accepting the cookies) the english language.
I see there is this button here: <button aria-label="Change language" data-encore-id="buttonSecondary" class="Button-sc-y0gtbx-0 jHYozi"> that will trigger the language modal then we can click on the data-testid="language-option-en" selector which is relative to the english language.
Doing this will secure that the selectors containing the text() functions will be always valid.
What do you think on this?

That would certainly solve the problem without having to change all the selectors, you are right. I'm getting back to text based xpath elements and forcing the language to be us using the button you suggested.
Thank you, i didn't see that. Would have been easier too :D
Going to fix that,
VT

Looking good on my side, did not try it locally: could you please attach the successful upload terminal log or a video in headless: false mode? Thank you, great effort there

Yep, don't know where to upload the video so i'm dumping here the log for now.
vaso@MacBook-Pro-di-Vasilis youtube-to-anchorfm % npm start

><EMAIL_ADDRESS>start
> node src/index.js

Getting JSON video info for video id j839QWYQ5xk
title: IMBEVIBILE, MA fa 250MLN in 12 mesi
description: Prime, KSI, Logan Paul
Upload date: {"year":"2023","month":"Apr","day":"18"}
Downloading thumbnail for video id j839QWYQ5xk
Downloading audio for video id j839QWYQ5xk
Downloaded thumbnail for video id j839QWYQ5xk
Downloaded audio for video id j839QWYQ5xk
Posting episode to anchorfm
Launching puppeteer
Trying to log in
Logged in
Uploading audio file
Waiting for upload to finish
-- Adding title
-- Adding description
-- Selecting content type
-- Saving draft
Yay
Finished successfully.

If needed i can upload the video on yt as private or something like this? don't know which one is the best option here.
VT

@abe-101 @matevskial could you please review this? Thanks

@abe-101 @matevskial could you please review this? Thanks

i've noticed that i missed to revert the xpath of save_as_draft button. Now should be all right

Thank you for the contribution.
I checked the code and I have some suggestions.

Could you tell me when the language of the page would be different than English? Is it when the operating system language is different? This feature is going to be very useful since the language of the page is not set per-account as far as I can see.

Could you provide a screenshot of the cookie popup? Which buttons would the script need to click? I can't see those buttons. Here is mine screenshot

Could you elaborate on why would the cookie popup need to be resolved in order for login to work? As far as I can see, we can fill the login form even without dealing with the cookie popup

Lastly, could you create separate PRs for each issue/change that you tackle, in particular:

one PR for the refactor where you abstract clicking xpath or selector into function
one PR tackling the cookie popup
one PR tackling the language
I would suggest not to create a PR for fixing the publish date since, there is already one PR for that

Thank you @matevskial  for the review.

I think the language is set based on IP. Because my system and browser languages are set on english but if i start the script with headless: false I get Italian language that is where my ip is located.
Selector based element's are no more needed to solve this because there is a language modal that we can use to set language to english at the start of everything as @TheJoin95 suggested and maintain the text based elements.

Here are the screenshots, it will click on cookie options and then accept only 'forced' cookies.

On the related discord channel i dropped a video with headless false too.

That's true most of the times it's not requested to check the cookie before the login because we can evaluate it in the DOM without problems. But i've noticed that on local mac OS env some times (it's not replicable every time) if i don't have the cookie accepted it doesn't evaluate correctly the login button and so it remains in the login page and never finds the input field. I've tried to run it several times commenting the piece of code cookie related and got this. I'm dumping a screen here.

Never noticed this error instead when i've already accepted the cookie before the login. But here would be nice to test with other local envs and see if the behaviour is the same.

Yes I can surely split the PR into smaller ones, and omit the date picker fix, if needed.
one PR for the refactor where you abstract clicking xpath or selector into function(if there is a real advantage of doing this)
what do you mean here? I think that would be an advantage on code readability and sustainability, if you are talking about performance, nope that's completely useless.

about point 3: Nope i've never seen that error with the cookie handler implemented.
about point 4: That's sure :D

Okay, in that case, After you are done, I am going to implement the handling of my cookie popup :D.
Because I also see the same issue that you try to fix with the cookie popup.
I guess my cookie popup causes the same thing too?
In that case, after you are done, I am going to implement cookie handling for my cookie popup too,

Yep you can try, in your case you just need to click the X at the top right corner? Or need to interact with a popup like EU based cookie?
Because we could add an env variable that uses my cookie handler or your cookie handler based on a boolean 'EUZONE' var

Could you please rebase and verify if this is still applicable ?

I'm going to close this PR as it appears to be inactive and not applicable anymore. Correct me if I'm wrong @matevskial


Test repository redirects

http.Client should handle following the redirects for us, but we should add a test case anyway.
Announcement: https://developer.github.com/changes/2015-04-17-preview-repository-redirects/

I think to test this case, we need to have a real renamed or transferred repo, so we should do it in integration test. Am I right? @willnorris

Yes, an integration test would certain be good, but we could also add a unit test where the test http server returns a redirect to a known URL and we verify that the client follows it.  We'd want to inspect the exact response that GitHub returns and have our test case mimic that.

So something like:
mux.HandleFunc("/repos/o/r1", func(...) {
    testMethod(t, r, "GET")
    http.Redirect(w, r, "/repos/o/r2", http.StatusFound)
})

mux.HandleFunc("/repos/o/r2", func(...) {
    testMethod(t, r, "GET")
    fmt.Fprint(w, `{"id":1}`)
})

// then test that calling client.Repositories.Get("o", "r1") returns a Repository with ID == 1

Or if GitHub actually uses a different status code, then we should use that here as well

Oh I see. Thank you so much! In this case, unit test is better.
I think I can do this issue 👍

Cool.  I've invited you to collaborate on the repo.  Once you accept that, I'll assign this issue to you.

That's great! Thank you so much!

So here's a real response from GitHub.  We should do basically the same in our test... return a 301 status and maybe include a basic JSON response body to make sure the library handles that okay.  What's also particularly interesting is that the redirect URL is of the form /repositories/{id} rather than /repos/{owner}/{repo}, so we should mimic that behavior as well.
% curl -i "https://api.github.com/repos/googlecloudplatform/kubernetes"
HTTP/1.1 301 Moved Permanently
Server: GitHub.com
Date: Tue, 19 Jul 2016 17:57:25 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 168
Status: 301 Moved Permanently
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 58
X-RateLimit-Reset:<PHONE_NUMBER>
Location: https://api.github.com/repositories/20580498
X-GitHub-Media-Type: github.v3
Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
Access-Control-Allow-Origin: *
Content-Security-Policy: default-src 'none'
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
Vary: Accept-Encoding
X-Served-By: 4c8b2d4732c413f4b9aefe394bd65569
X-GitHub-Request-Id: 68840151:22AD:478E44A:578E6A05

{
  "message": "Moved Permanently",
  "url": "https://api.github.com/repositories/20580498",
  "documentation_url": "https://developer.github.com/v3/#http-redirects"
}

Are redirects handled transparently by go-github? I had client.Repositories.DeleteHook() return a 307 response.

Given that this issue is still open, I guess the answer is... not sure?  As I noted in the initial issue description, this should be handled by the http.Client.  Maybe it doesn't handle 307 responses?  All the more reason for us to add some test cases for this behavior.

@huytd, are you still working on this, or should we unassign this issue to free it up for others to work on?

Now the user who has renamed the repository has now deleted the repository so I'm getting a 404. But it should be possible to reproduce the issue by creating a repo and then renaming the repo. I'll try to get a reproducible test case.

@jonbodner did some research and the http.client library has hooks for redirecting GET, HEAD, POST, and PUT. But no redirects for DELETE or PATCH. We're not sure yet if this is a bug or a feature in the golang standard library. Jon and I need to try out a couple of different approaches and we'll follow up on this thread.

More research: this behavior is changed in Go 1.8 beta. From the release notes:
The Client now supports 307 and 308 redirects. If the redirect requires resending the request body, the request must have the new Request.GetBody field defined. NewRequest sets Request.GetBody automatically for common body types.

Assuming this code makes it to release, recompiling with Go 1.8 will ensure that DELETEs requests that return a 307 status code will redirect automatically.

Running go 1.7.4 I can confirm that Github returns 307 on a renamed repository and this is not handled by go-github. It looks like waiting for go 1.8 will fix this, but I cannot confirm this yet.

Thanks for testing and reporting results, @Kegsay. Which repo did you test on, an do you have a snippet that you've used handy? I have 1.8 here, so I can try and see if it indeed helps.

@shurcooL I tested it on a repo which was recently renamed, in this case vector-im/vector-web which is now vector-im/riot-web. Attempts to create issues using vector-web fails with the 307. I obviously can't give you a complete example since it's using OAuth tokens, but effectively:
// cli is a *gogithub.Client
issue, res, err := cli.Issues.Create("owner", "repo", &gogithub.IssueRequest{
	Title: "Some title",
	Body:  "Some body",
})
if err != nil {
	fmt.Println("HTTP %d", res.StatusCode)
}

And this will indeed print HTTP 307 (so err and res are non-nil). Renaming repos on Github isn't hard, so you should be able to rig something up to test locally.

Closing issue for lack of activity/interest. Feel free to reopen.


Marine dev

minor text change

@mdenolle can you change the title of the PR to something more descriptive? It will become part of the commit history when the PR is merged. Also, a description of the changes would be great. thx!


Alias examples for Http/DotNetBuild/MSTest #750

Reopened a new PR to squash and rebase to develop correctly (closed #790 as accidental merge/learning experience :8ball: :) )
Following have had examples added:
Cake.Common.Net.DownloadFile(string)
Cake.Common.Net.DownloadFile(Uri)
Cake.Common.Net.DownloadFile(string, FilePath)
Cake.Common.Net.DownloadFile(Uri, FilePath)
Cake.Common.Tools.DotNetBuild(FilePath)
Cake.Common.Tools.DotNetBuild(FilePath, Action)
Cake.Common.Tools.MSTest.MSTest(string)
Cake.Common.Tools.MSTest.MSTest(string, MSTestSettings)
Cake.Common.Tools.MSTest.MSTest(IEnumerable)
Cake.Common.Tools.MSTest.MSTest(IEnumerable, MSTestSettings)
Thanks.

Looks good to me! Will merge this ASAP.
Related to #750.

Great job! :+1:
Thanks for your contribution!


Setup components

Initialize project using create-react-app

Initialise React app.
Add React Redux
Structure files using a "feature folder" approach and use the duck pattern for your Redux files
Add a set of re-usable components for the app
Add React Router and set two nav links for the app's navigation, books as the home view and categories as the other page
Books view displaying lists of demo books and a form to add another book
Categories showing a text saying under construction

Thank you @FrederickMih :handshake:


Nominate CBID2 to the Triage Team

Hi there. I read your project's Code of Conduct and would love to join the triage team. I got inspired after raising this issue: https://github.com/expressjs/express/issues/5449

Thanks @CBID2! I know for sure that you can do a great job in the triage team, I support your nomination 👍

I guess I'm not nominated 😢

I guess I'm not nominated 😢

Sorry for the delay, you continue to be nominated. 🎉
Last week in the TC meeting (https://github.com/expressjs/discussions/issues/161#issuecomment-1948963916) we decided to make some changes in the governance, so we are doing some changes on the roles definitions and capabilities (like https://github.com/expressjs/express/pull/5483). We will do some changes for the triager role and then we will add the new members to the team.
Feel free to join us in Slack channel #express as we have some relevant offline discussions and we are starting new initiatives also 😄

Yep! Sorry for the delay, we have a lot going on trying to get things off the ground so it might be another week or two before we can get the triage group setup and running again. Just want to set the right expectations. We will get to it, don't worry!

Thanks for your patience @CBID2. We had discussed the final plan today in the TC meeting (relevant from 11:30), I will add you to the triage team asap

Welcome aboard @CBID2! invitations sent for all the organizations, please accept them :partying_face:


[BUG] New-PnPMicrosoft365Group Issue

Reporting an Issue or Missing Feature
Issue
Expected behavior
When using New-PnPMicrosoft365Group, a new Microsoft 365 Group is created without error.
Actual behavior
When using the New-PnPMicrosoft365Group command, without the "-CreateTeam" switch, the following is displayed to screen although the group is created correctly:

PS C:\Temp> New-PnPMicrosoft365Group -DisplayName "A New Group 03" -Description "This is the description" -MailNickname "AA003" -Owners<EMAIL_ADDRESS>-IsPrivate -Force
New-PnPMicrosoft365Group : Unable to provision resource.
At line:1 char:1

New-PnPMicrosoft365Group -DisplayName "A New Group 03" -Description " ...

  + CategoryInfo          : InvalidOperation: (:) [New-PnPMicrosoft365Group], PSInvalidOperationException
  + FullyQualifiedErrorId : InvalidOperation,PnP.PowerShell.Commands.Microsoft365Groups.NewPnPMicrosoft365Group

PS C:\Temp> get-pnpexception
Message          : Unable to provision resource.
Stacktrace       :    at PnP.PowerShell.Commands.Base.BasePSCmdlet.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
ScriptLineNumber : 1

If you use the same command and add the "-CreateTeam" switch, then both the Group and the Team area created correctly with no issues being logged to screen.
Steps to reproduce behavior
Create a new Group without the "-CreateTeam" switch.
New-PnPMicrosoft365Group -DisplayName "A New Group 03" -Description "This is the description" -MailNickname "AA003" -Owners<EMAIL_ADDRESS>-IsPrivate -Force
What is the version of the Cmdlet module you are running?
1.4.20
Which operating system/environment are you running PnP PowerShell on?

[X] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

Indeed, I can reproduce the issue. The group is created, but the error New-PnPMicrosoft365Group: Unable to provision resource. is showing.
FYI - @erwinvanhunen @gautamdsheth

Great, thanks Gautam.  Works a charm.


[gardening] Fix violations of non-controversial PEP8 rules

Fixes:

multiple imports on one line
closing bracket does not match indentation of opening bracket's line
continuation line over-indented for hanging indent
continuation line over-indented for visual indent
continuation line unaligned for hanging indent
inline comment should start with '# '
missing whitespace around bitwise or shift operator
missing whitespace around arithmetic operator
multiple spaces after ':'
multiple spaces after operator

I'll run tests.

Tests passed on Ubuntu 14.04.


Wrong path on renew

On row 249 we have
#Copy the Let's Encrypt Certs into it, using Vesta naming conventions
cp /etc/letsencrypt/live/$MAINDOMAIN/cert.pem $TMPLOC/$DOMAIN.crt
cp /etc/letsencrypt/live/$MAINDOMAIN/privkey.pem $TMPLOC/$DOMAIN.key
cp /etc/letsencrypt/live/$MAINDOMAIN/chain.pem $TMPLOC/$DOMAIN.ca
But "fresh" certificate is put by letsencrypt in a different directory, something like $MAINDOMAIN-0001, so the script copies the old one.
As a quick and dirty fix, I just clean /etc/letsencrypt/ before renew.

Can you double check on this?  From what I can tell, the -xxxx directories get created when the list of domains on the certificate changes from the previous certificate (i.e. you requested the cert for www.abc.com and abc.com the first time but then added xyz.abc.com to the list when you renewed).  However, from what I can tell, the old certificate gets moved to the -xxxx directory and the new one is placed in the non-xxxx directory.
You can test this with the following commands:
    cd /etc/letsencrypt/live
    openssl x509 -in abc.com/cert.pem -text
    openssl x509 -in abc.com-0001/cert.pem -text

In the output of the openssl commands you should find something like this:
    Validity
        Not Before: Jun 20 04:56:00 2016 GMT
        Not After : Sep 18 04:56:00 2016 GMT

If your system is behaving the same as mine, the abc.com-0001 cert should show the older validity dates and the one without it should show the more recent.

Probably it was a mistake of mine.

try remove (or rename)  folders from /etc/letsencrypt/archive and /etc/letsencrypt/live.


Reverse Engineer: Always use DefaultValueSql for default values

Discussing https://github.com/aspnet/EntityFramework/issues/3941 it becomes clear that there is no fool-proof way to detect whether a default expression in SQL is a constant or an expression. Given that there is no real advantage to using the constant in the model, we should just always treat it as an expression.

Checked in with commit 8079adf.


Facing an issue in running seekr2 in the HIDR step on trypsin-benzamidine system

Hello, Janvi here.
I am a master student at National Institute of Pharmaceutical Education & Research, Guwahati India. Working under
Dr Vaibhav Dixit. I am using trypsin-benzamidine tutorials for seeker2 on HPC installation and I am able to generate the results till step of  constructing the SEEKR2 Model Input File.
After generating an empty modeI I'm stuck at "Running HIDR on the new Model", job error shows
"you should atleast have OpenMM 6.3 installed ",
whereas my system is already having OpenMM 7.7 installed ,
what could be the remedy?
Please suggest so that I can move forward in the tutorial and then apply SEEKR2 methodology to my project work.
Thank you and Best regards.

Would you please post more information about the error: what command you were running and the full set of lines output before the error?

Yes Sir , Here is the command I were using
"python3.8 /home/software/seekr2/seekr2/prepare.py input_tryp_ben_hidr-new.xml " for which I got " model.xml" as an output.
the another command
"python ~/seekrtools/seekrtools/hidr/hidr.py any ~/tryp_ben_hidr_tutorial/model.xml -M SMD -p tryp_ben.pdb"
is giving following error :
"Warning: importing 'simtk.openmm' is deprecated.  Import 'openmm' instead.
Traceback (most recent call last):
File "/home/software/seekrtools/seekrtools/hidr/hidr.py", line 366, in
hidr(model, destination, pdb_files, dry_run, equilibration_steps,
File "/home/software/seekrtools/seekrtools/hidr/hidr.py", line 175, in hidr
ns_per_day = hidr_simulation.run_min_equil_anchor(
File "/home/software/miniconda3/envs/myseekr2/lib/python3.8/site-packages/seekrtools-0+untagged.65.g549ac37-py3.8.egg/seekrtools/hidr/hidr_simulation.py", line 347, in run_min_equil_anchor
parm = parmed.openmm.load_topology(topology, system)
File "/home/software/amber22/lib/python3.9/site-packages/parmed/utils/decorators.py", line 30, in new_fcn
raise ImportError('You must have at least OpenMM 6.3 installed')
ImportError: You must have at least OpenMM 6.3 installed"

In the first command, it looks like you're using python3.8, but in the second you're just using "python", which seems to be Python 3.9. Are you sure that OpenMM and the SEEKR plugin is installed in the version of Python you are using for the HIDR command?

Thank you for your hint Mr. Lane, it worked.

Excellent

Hello  Mr. Lane  Janvi here,
I wanted to use multiple GPU Card for running my command instead of using  "any".
According to your previous comments on following issue  "BD or MD first with run.py any #21"
I  tried using
" python /home/software/seekr2/seekr2/run.py 0 model.xml -f -c 0 &
python /home/software/seekr2/seekr2/run.py 1 model.xml -f -c 1 &
python /home/software/seekr2/seekr2/run.py 2 model.xml -f -c 2 &
python /home/software/seekr2/seekr2/run.py 3 model.xml -f -c 3 &
wait"
but it didn't work, also I used following command ,
python "/home/software/seekr2new/seekr2/seekr2/run.py" any "/home/msmeity/JANVI/SEEKR/tryp_ben_hidr_tutorial3/model.xml" -f -c '1,2' &  which also failed .
can you please suggest  ?

Please copy this into a new issue, and post the exact error message(s).


Any way to specify _id to change the file path used by FileStorage Observer?

When I use FileStorage Observer, I notice that every time I run my program, it saves information in a new folder named by incremental numbers, for example,
/ExpName/1/run.json
/ExpName/2/run.json
/ExpName/3/run.json
But I hope I can specify the folder name by myself.
I have thoroughly read the source codes but can't find any way that I can specify it.
I think the folder name is determined by run._id. But even I change run._id during program running, it doesn't affect the folder path.
How should I do to change the folder name?

Usually it is the observer with the highest priority that determines the _id, and yes, that becomes the path.
ATM the only good way to set that path yourself is to add a custom observer that sets the _id. Like this:
from sacred.observers import RunObserver

class SetID(RunObserver):
    priority = 50  # very high priority

    def __init__(self, custom_id):
        self.custom_id = custom_id

    def started_event(self, ex_info, command, host_info, start_time,  config, meta_info, _id):
        return self.custom_id    # started_event should returns the _id

And then in your experiment file:
ex.observers.append(SetID("my_id"))

This is somewhat hacky, though. May I ask some more details about your usecase? Maybe it is worth making this easier.

Thanks! I think this solution is easy enough.
In my case, sometimes I make small changes of my code several times to try something different.
I hope the folder name can be more explicit so that I can recognise it immediately.
And also, sometimes I hope the most critical parameter value can be in folder names. Therefor, I don't have to open the config.josn file one by one to check which one I need.
But I think the solution you provide is adequate.

Closing, since it seems resolved to me. BTW: you could adapt the solution above to also make config entries part of the id by using the config argument inside of the started_event. But you will have to ensure unique ids yourself.


Engine: Implement support for threshold signatures

See https://github.com/bpfkorea/agora/issues/1428 for more info. If we don't get MuSig support in the Wallet soon then this is the scheme we should be using by default.
Fixes https://github.com/bpfkorea/agora/issues/1428

Merging as no comments received and the wallet needs it.


Output meaning

Maybe provide a short description on what the output (at least for the fittest function) actually represents.

We could do this in an example or provide this in a Pluto notebook.


Should pgpass only be checked if password is empty?

I think it will be surprising to a user if they correctly set the password in the INI file, but it gets overridden by the PostgreSQL Password File.
The point of the PostgreSQL Password File is to put the password in a more secure file. If the user is putting it in INI, then they must not be concerned with or aware of that security.
If we change this logic, we might as well also read the password from the PostgreSQL Password File when the database URI is set via an environment variable whose value lacks a password.

Unfortunately this breaks live.
On Live we have
PASSWORD = will-be-got-from-pgpass

Which means it now doesn't try to load the .pgpass file and we get
psycopg2.OperationalError: FATAL:  password authentication failed for user "ocdskfp"

Please remove that from the config.ini file :)
On Monday, August 10, 2020, James (ODSC<EMAIL_ADDRESS>wrote:

Unfortunately this breaks live.
On Live we have
PASSWORD = will-be-got-from-pgpass
Which means it now doesn't try to load the .pgpass file and we get
psycopg2.OperationalError: FATAL:  password authentication failed for user "ocdskfp"
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/open-contracting/kingfisher-views/issues/100#issuecomment-671220072,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAGOXYBJGUXVUKDF74473LR76TSDANCNFSM4LFV7C6A
.

--
James McKinney
Head of Data Products and Services
+1-514-247-0223 | @mckinneyjames | skype: mckinney.james | timezone: EST
*** An inclusive economy is a stronger economy. Learn about emerging
strategies for empowering women-led businesses through public procurement
https://www.open-contracting.org/resources/empower-women-led-business-procurement/
in
our new report. ***
www.open-contracting.org | follow us @opencontracting

Done


No GPU available

Hi,
I want to use RoseTTAFold, but our Linux server has no GPU and only CPUs. Is it OK? Thank you!
Rusfell

RoseTTAFold runs normally.

Excuse me, how did you install it without a GPU? Just run conda env create -f RoseTTAFold-linux.yml ? Thank you.


Pfe autocomplete updates

pfe-autocomplete Angular support, story, and schema

added a slotchange event listener so this will work with Angular
added a schema
added a pfe-autocomplete story for Storybook

@starryeyez024 @kylebuch8 Did you see there's this branch out there too for this work: https://github.com/patternfly/patternfly-elements/pull/331/files


Bug: field values gets replaced in helm chart preset values

📜 Description

Name of preset values gets changed after selecting chart values.
Chart version remains unchanged after saving preset values.
Shows force delete pop-up window, when i try to delete preset values, however it is deleted.
After clicking cancel, it remains on UI.

👟 Reproduction steps

Create a preset values for a chart.
Create a new preset values with different name using same chart.
Check preset value name and chart version after saving it. This will be changed.
Then try to delete the preset values.

👍 Expected behavior
Preset values details configurations should remain unchanged after saving it.
👎 Actual Behavior
Preset values details configurations gets changed after saving it.
☸ Kubernetes version
1.21
Cloud provider

AWS

🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

https://github.com/devtron-labs/dashboard/pull/967


Missing import

Fail to start the application, 'url' has been removed from the imports.
https://github.com/django-helpdesk/django-helpdesk/blob/61f086a0ac63e156fdc34715d40217970589e8a1/helpdesk/urls.py#L175

Thank you, this was resolved in #1022 correct?


Can you please add source-map to JS-minify

Seems the terser option doesn't quite work as they should? :)

I'll check on it, mate. I don't know why it won't work, tho. I'll check terser options again.

I've implemented it. Will push out in next update.

Any update here yet? :)
And will you fix support for the other terser options?
Like "toplevel: true" to compress and/or mangle variables in top level scope.

Source maps is added though? Just check the box in the extension settings for source maps. It'll create a '.map' file in the same parent folder.
And I think other terser and other extension options work though? Can you double check?

And btw, Source maps option is added. Just check the box in the extension settings for source maps. It'll create a '.map' file in the same parent folder.

Hi again. Source maps works great now thanks.
I cannot get terser options to work though. Maybe I'm doing it wrong. I'm trying to get the @import file to be included in the app.min.js (https://d.pr/i/52v0ga). I support mangle toplevel does this, but I'm not quite sure. Nothing happens when I try this at least: https://d.pr/i/gMZl2c.

Uh, I don't mean to be rude, but I don't think that's how mangling works. Mangling changes long variable names to short ones. And for the @import code, the whole line is a string of keywords. None of it, is a variable. Mangling in terser checks for variables. Not keywords.
Also, that, mangling for high level code may change stuff up, so, I wouldn't recommend.
But as you've said that it doesn't work, I'll look into it.
In the mean time, I'd say, just go through the terser docs for mangling options. I myself, do not use mangling. Also, you've have to enable mangle-properties.
I'd recommend going through terser options.

Thanks for clarifying. Do you know if it's possible to achieve what I'm after? I know the app Prepros compiles the imported file, but it would be great if your app did the same :)

can you just explain what actually you want to achieve? You want mangling? or do you want to remove spaces in that line? what exactly do you want?

ah. From the looks of it, I presume Prepros includes a a Preprocessor? I assume it imports the .carousel/.. file and unravels it.
Sorry mate, the minifer I made doesn't do that. Not that I can't make it so, but that, it isn't a Preprocessor. It literally isn't in its scope of working. It's literally a separate working.
The primary reason mine cannot do it, is that, Prepos already has the necessary syntax and semantics to convert scss, or less files, and convert it's syntaxes and semantics into native css. Mine just minifies. I didn't intend to compile scss or less to native css.
Sorry, mate. I might one day make one extension including compilation and minifier too, but that's a thought for another day.