sanctuary-def dependency

Sanctuary depends on sanctuary-def, as specified in package.json. Furthermore, Sanctuary is only compatible with certain versions of sanctuary-def. @codedmart recently brought it to my attention on Gitter that the example for create does not work if one uses the current version of Sanctuary (v0.11.1) with the current version of sanctuary-def (v0.9.0).
There are (at least) two things we should consider:

specifying this constraint in package.json, if possible; and
versioning the two packages such that<EMAIL_ADDRESS>always depends on and works with<EMAIL_ADDRESS>

Could we use peerDependencies to express the constraint?
  "dependencies": {
    "sanctuary-def": "0.9.0",
    "sanctuary-type-classes": "2.0.1",
    "sanctuary-type-identifiers": "1.0.0"
  },
  "peerDependencies": {
    "sanctuary-def": "0.9.0"
  }

versioning the two packages such that<EMAIL_ADDRESS>always depends on and works with<EMAIL_ADDRESS>

Could we use peerDependencies to express the constraint?

I've never seen peerDependencies used like that, though I haven't come across the situation where a package is both a dependency and a plugin to another package. I guess it might win us an automatic warning when the user tries to use an incompatible def, but I think it's all a bit messy. It relates my the concerns I expressed here.
The problem, I think, is that multiple parties are creating black-box data structures (type definitions) using sanctuary-def and multiple parties need to interpret (call def on) those structures using sanctuary-def. Maybe it's possible for the future to ship the interpreter with "batteries included", eg:
const sanctuary = require('sanctuary');
const $ = require('sanctuary-def');
const env = $.env.concat(sanctuary.env).concat(myEnv);
const def = TYPE_CHECKING ? $.createTypecheckedDef(env) : $.def;

const S = sanctuary.create(def);

sanctuary would have to have a Peer Dependency on sanctuary-def, but not direct dependency. It's compatibility with def would only change if the type signature of def() changes, but not when the internal data structures change. Maybe It's a bad idea. Might be one for Ideas about env ;)

Ah I just realized the flaw in my idea above: In order to provide an env, we would still need sanctuary-def.

But it does seem to me like removing sanctuary-def from dependencies and keeping it as only a peer-dependency would reduce complexity.

But it does seem to me like removing sanctuary-def from dependencies and keeping it as only a peer-dependency would reduce complexity.

I agree. const S = sanctuary.create(def); seems very nice to me! Let's seriously consider this change once we get v0.12.0 out the door. :)

I think this is what we should do:

Separate all of sanctuary into small modules, each with a peer dependency on sanctuary-def:

sanctuary-either to contain the Either type, its Repr and associated functions
sanctuary-maybe to contain the Maybe type, its Repr and associated functions
sanctuary-list for list related functions
sanctuary-string for string related functions
sanctuary-strmap for the StrRep type and related functions
...more

Create a sanctuary-prelude library which takes from each of the above libs to provide a set of common tools.
The sanctuary library will have a single function. To load sanctuary-prelude and sanctuary-def and instantiate the prelude it with a default def.

People who want an out-of-the-box experience will use sanctuary, people who want a customized one will use sanctuary-prelude, people who want only parts of the functionality will assemble their own utility belt from the available underlying libs.
This tackles several problems:

"The library is monolithic": Now we can choose what we want to include. Maybe in the future, each lib can even slit up into stuff like sanctuary-maybe-type, sanctuary-maybe-from-nullable.
(and this is personal) "my colleagues are using require('sanctuary') directly, which defeats the point of disabling type-checking": Now, I will depend only on sanctuary-prelude, and provide my own assembly which they have to use.
"my sanctuary-def is not compatible with yours": Since all packages but sanctuary have it as a peer dependency, they will all use the same version and NPM will show it when one is not compatible and should be down or upgraded.

Is it UnaryType that breaks things currently?

I really don't know the internals of sanctuary so I have no idea what is possible but I assume that eacho of those packages would be sanctuary-def (78 kb) and sanctuary-type-classes (45kb). Right now sanctuary is 100kb, let's say sanctuary-maybe would me 15kb. Would it make sense to have a separate package of 15kb with 123kb of dependencies. In that case, me as a user, would prefer to download a es6 modularized sanctuary and tree shake it myself. Other option is to ask if you are downloading a single package probably you are working on a small project and you would not need type checking, so remove type checking on individual packages -if possible.


Plugin.loading: shows forever even though the subscription is ready

For some reason I have yet to figure out, the loading template does not hide after my waitOn subscription becomes .ready() and the proper template loads as well showing the data.
I notice that the problem goes away if I add
ready: this.ready()
in my route data.
Either the plugin checks this.data.ready or this.ready() isn't reactive as it should. The code in the repository seems good, so I can't track the exact issue atm.
Please confirm.

Eventually I found a problem in another package causing my specific error, my bad. Closing the issue.


runPrep.sh misses .simg containers

I am setting up to use runPrep.sh if possible to run aslprep-0.6.0rc1, which is saved as a .simg in containers/, but runPrep.sh doesn't currently find it.
Most local singularity images are saved with ".sif" extensions, but some are ".simg". The ones saved as .simg get missed by runPrep.sh at line 41: it lists available images in the containers/ dir and greps only .sif.
Similarly, line 202 defines the "image" variable using only the .sif extension

Is there a use case for simg files? I thought sif was preferred

Not that I’m aware of. Older versions of ASLPREP used simg in their singularity examples so that’s what I’d created previously. I’m happy to change that moving forward.


ability to set key on Link?

I'm working on animating a list of Link's and noticed that when I set a key on links I'm not seeing it in the rendered component. I'm fairly new to react, so I might be missing something, but I thought it was worth raising.

You don't see keys anywhere in rendered components. It's an attribute that React uses internally to track component instances between render calls, but the only place it shows up in the DOM is in the data-reactid attribute.


Prototype for Dynamic Group

Related to : #896
After writing down my thoughts last week, I got the idea of a design that I think would address all requirements so I wrote a quick prototype to share my idea and get some feedback.
The main idea is that for each Model/ContentType that support DynamicGroup, we need to provide a new DynamicGroupMap class that will be able to translate to/from queryset and filterset, UI and API for this given Model/ContentType.
The DynamicGroupMap is used to:

List all valid attributes to define the member of the group
Generate the fields of the UI form to configure the DynamicGroup and define the members of the group
Generate the associate FilterSet representing the members of the group (as queryset and as URL)
Generate the associate Queryset filter to get all groups associated with a given object.

Nothing is stored in the DynamicGroupMap and this is not a database Model, this class is just a translation engine.
the real value of the query is stored in JSON in the standard DynamicGroup object.
Example of DynamicGroupMap for dcim:site
class SiteDynamicGroupMap(BaseDynamicGroupMap):

    model = Site
    filterset = SiteFilterSet

    field_order = ["region", "tag"]

    region = DynamicModelMultipleChoiceField(
        queryset=Region.objects.all(),
        to_field_name="slug",
        required=False,
    )

    tag = DynamicModelMultipleChoiceField(
        queryset=Tag.objects.all(),
        to_field_name="slug",
        required=False,
    )

    @classmethod
    def get_group_queryset_filter(cls, obj):
        """Return a queryset filter matching this DynamicGroup parameters."""
        queryset_filter = Q(filter__region__contains=obj.region.slug)

        if obj.region.parent:
            queryset_filter = Q(filter__region__contains=obj.region.parent.slug)

        for tag in obj.tags.slugs():
            queryset_filter |= Q(filter__tag__contains=tag)

        return queryset_filter

UI

Retrieve all groups a given objects is part of
>>> from nautobot.dcim.groups import SiteDynamicGroupMap
>>> fra = Site.objects.get(slug="fra")
>>> DynamicGroup.objects.get_for_object(fra)
<DynamicGroupQuerySet [<DynamicGroup: Sites-with-tag1>, <DynamicGroup: Sites-in-europe>]>

Get the queryset of all objects that are part of a group, and get associated filterset/URL
>>> grp1 = DynamicGroup.objects.get(slug="sites-in-europe")
>>> grp1.get_queryset()
<RestrictedQuerySet [<Site: ams>, <Site: cdg>, <Site: fra>, <Site: lhr>]>
>>> grp1.get_url_to_group_members()
'/dcim/sites/?region=europe'

List of DynamicGroup with count

I personally like the approach and I believe it solves the problem pretty well in both directions.

This is an awesome PoC.
I like the idea of "FilterSet" like approach and describing custom groups as a code.
Few questions:

Can we inherit group's fields based on FilterSet ?
This would provide consistency - each group of a given ContentType would be "Filterable" in the same way as in other places.

I am not sure what is the need for defining the "Object Type" during group creation, as the fields (typical of given object types) are described in the code.

In my tests, by default, group was already filled with members - was this intended default behaviour ?

In my tests, I was not able to put filters into fields:
Select a valid choice. reg1 is not one of the available choices.

this error ocurrec for each case.

thanks for the feedback and the questions @mzbroch
Please see my responses below

Can we inherit group's fields based on FilterSet ?
This would provide consistency - each group of a given ContentType would be "Filterable" in the same way as in other places.

We can use a subnet of the Filterset but we can't assume that we'll be able to use all of them by default because it's possible to have some custom logic behind a specific Filterset field that may not be compatible with the Queryset.

How hard would be to allow for the fields to accept also groups of a Given ContentType. In example: You defined "Region" to allow for Region() objects, but can we also allow for custom groups of Region Content Type in here ?

This is a good question, and I don't know yet but I will look into it

How hard would it be to allow for regular expressions in names? Ie. I want only regions that match certain name "Pol.*"

This is possible but it will requires to update the associated FIlterset to support that first. Because we want to be able to represent the query associated with the group in the UI/API, we can't support something that is not supported by the filterset already

I am not sure what is the need for defining the "Object Type" during group creation, as the fields (typical of given object types) are described in the code.

Defining the Object Type will allow us to know which attributes are available to define the query. Each Object Type will most likely have a different set of attributes. The attributes for each Object Type should be defined in the associated  DynamicGroupMap

In my tests, by default, group was already filled with members - was this intended default behaviour ?

Yes, currently if no query is provided, the dynamic group will match all instance of this type by default, we can change that behavior if needed

In my tests, I was not able to put filters into fields:
Select a valid choice. reg1 is not one of the available choices.

Yes, this is a known issue on the current implementation, I need to investigate that further

After discussing with @glennmatthews last week, we thought it would be best to avoid duplicating code between the <Model>DynamicGroupMap and the <Model>FilterForm so I refactored the code to dynamically importing the fields from the <Model>FilterForm instead and automatically generate the queryset by inspecting the fields in the FilterSet and the FilterForm
I think the result is much better and much simpler
For the device group, there is no code to write anymore to automatically support "platform", "manufacturer", "device_type_id", "role", "site" and "tag"
class DeviceDynamicGroupMap(BaseDynamicGroupMap):

    model = Device
    filterset = DeviceFilterSet
    filterform = DeviceFilterForm

    field_order = ["platform", "manufacturer", "device_type_id", "role", "site", "tag"]

I also started to write a mgmt command that will help validate that all groups are returning the same information from both directions. It's very helpful to identify a mismatch/bug. The idea is to refactor this function to be able to use it as part of the unit tests as well.

So far I found few caveats with this implementation but I think these are manageable:

All available fields must be populated in filter, even if empty
it's only possible to have 1 tag defined per group at a time

I'd love to get more feedback before spending more time on this one

Replaced by #1425


Revert IgnOGRE Windows fix, it breaks downstream libraries

This was introduced in https://github.com/ignitionrobotics/ign-rendering/pull/206, and now trying to compile ign-gui3 against it I get:
CMake Error at src/plugins/CMakeLists.txt:29 (add_library):
  Target "Grid3D" links to target "IgnOGRE::IgnOGRE" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
Call Stack (most recent call first):
  src/plugins/CMakeLists.txt:77 (ign_gui_add_library)
  src/plugins/grid_3d/CMakeLists.txt:1 (ign_gui_add_plugin)

CMake Error at src/plugins/CMakeLists.txt:29 (add_library):
  Target "Scene3D" links to target "IgnOGRE::IgnOGRE" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
Call Stack (most recent call first):
  src/plugins/CMakeLists.txt:77 (ign_gui_add_library)
  src/plugins/scene3d/CMakeLists.txt:1 (ign_gui_add_plugin)

I originally did it to fix a Windows warning. Let's see how CI comes back. If Windows is still complaining, we may need a different fix.

No warnings on Windows. Good to go.

No warnings on Windows. Good to go.


Hex Color Code Generator Website

Pull Request for WebMasterLog 💡
Issue Title:
Hex color code generator website using Vanilla JS #25

Name of the project : Hex color code generator website
Category: Vanilla Js
Name: Aryan Pahuja
GitHub ID: www.github.com/AryanPahuja21
Idenitfy yourself: JWOC'24 contributor

Closes:
#25
Describe the add-ons or changes you've made 📃
The website now features an attractive heading styled with a gradient background, creating a visually appealing look. Users can select colors from the palette, and the resulting color is displayed below dynamically. A "Copy Hex" button allows users to easily copy the hexadecimal code of the resulting color.
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Screenshots 📷

Uploading Hex Color Code Generator (online-video-cutter.com).mp4…
Note to reviewers 📄
Please review my pull request @Avdhesh-Varshney

@Avdhesh-Varshney the changes are made. Please review.


RxJS Peer Dependency issue upgrading to Angular 13

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[x] Support request
[ ] Other... Please describe:

Current behavior
When upgrading to Angular 13 which requires RxJS 7.4.0 I am getting the following warnings from npm install:
npm WARN<EMAIL_ADDRESS>requires a peer of rxjs@>= 6.1.0 < 7 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of rxjs@>= 6.1.0 < 7 but none is installed. You must install peer dependencies yourself.

Environment

Angular version: 13.0.0

For Tooling issues:
- Node version: v14.15.5
- Platform:  Mac

I understand that Elf is the new hotness, but we can't migrate right now.  Any chance that versions of the Akita gems with support for RxJS > 7 could be released?

Yes, we can increase the peer requirement.

In the meantime you can use --force

Yup, did that to get by it.  Just wanted to see if we could avoid it.  Thanks!

Hmm, we already support it.

https://github.com/datorama/akita/blob/master/libs/akita/package.json#L34

Update Akita, please.

Sigh... apologies.  Thanks again.


panic: runtime error: slice bounds out of range

only on mipsel 32bit openwrt : panic: runtime error: slice bounds out of range
linux amd64 and windows are run fine!
I'm find it golang/go#9007
look's like must change to higher go version to fix this bug???
code source:
func main() {
db, err := leveldb.OpenFile("data", nil)
if err != nil {
fmt.Println("error:", err)
}
defer db.Close()
data, err := db.Get([]byte("key"), nil)
fmt.Println(string(data),err)

err = db.Put([]byte("key"), []byte("value"), nil)
data, err = db.Get([]byte("key"), nil)
fmt.Println(string(data),err)

}
bug review:
1 ./main that's run allright
2 rerun ./main error show for bug view
bug view:
root@OpenWrt:/tmp# ./main
panic: runtime error: slice bounds out of range
goroutine 1 [running]:
github.com/golang/snappy.encodeBlock(0x10410141, 0x43, 0x43, 0x1086623c, 0x1b, 0x40, 0x50)
/opt/slu/src/github.com/golang/snappy/encode_other.go:175 +0x10c4
github.com/golang/snappy.Encode(0x10410140, 0x44, 0x44, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/golang/snappy/encode.go:37 +0x370
github.com/syndtr/goleveldb/leveldb/table.(Writer).writeBlock(0x10866200, 0x1086622c, 0x2, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/table/writer.go:170 +0x1e4
github.com/syndtr/goleveldb/leveldb/table.(Writer).finishBlock(0x10866200, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/table/writer.go:221 +0xa0
github.com/syndtr/goleveldb/leveldb/table.(Writer).Close(0x10866200, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/table/writer.go:294 +0x960
github.com/syndtr/goleveldb/leveldb.(tWriter).finish(0x10434740, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/table.go:507 +0x9c
github.com/syndtr/goleveldb/leveldb.(tOps).createFrom(0x104366e0, 0x77817d08, 0x10434700, 0x0, 0x1, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/table.go:340 +0x288
github.com/syndtr/goleveldb/leveldb.(session).flushMemdb(0x1042e000, 0x10448070, 0x1042e080, 0x0, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/session_compaction.go:27 +0x1cc
github.com/syndtr/goleveldb/leveldb.(*DB).recoverJournal(0x1045a000, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/db.go:603 +0xce0
github.com/syndtr/goleveldb/leveldb.openDB(0x1042e000, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/db.go:124 +0x9e8
github.com/syndtr/goleveldb/leveldb.Open(0x77817a48, 0x10434000, 0x0, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/db.go:196 +0x1e0
github.com/syndtr/goleveldb/leveldb.OpenFile(0x1a9b58, 0x4, 0x0, 0x0, 0x0, 0x0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/db.go:218 +0xbc
main.main()
/opt/slu/main.go:14 +0x58
goroutine 5 [select]:
github.com/syndtr/goleveldb/leveldb/util.(*BufferPool).drain(0x1043e0b0)
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/util/buffer_pool.go:206 +0x2a0
created by github.com/syndtr/goleveldb/leveldb/util.NewBufferPool
/opt/slu/src/github.com/syndtr/goleveldb/leveldb/util/buffer_pool.go:237 +0x2cc
thx!

@syndtr

The panic is in the github.com/golang/snappy package.

The first thing thanks for your reply @calmh ! this bug just view on mips's openwrt os, on ubuntu or windows os run be fine. I need more help! thx!!! a moment's ago i check leveldb file was created. i think bug just onload leveldb data or open file time error.

Try updating snappy, i.e. go get -u github.com/golang/snappy.

thanks @syndtr ! I try to update the newer snappy error view too.  compile app I was build by https://github.com/gomini/go-mips32.git help me has a looks. that's gccgo?. thx! and I try to build tags by noasm (go build -tags=noasm main.go) target run error on the way.

compile app I was build by https://github.com/gomini/go-mips32.git help me has a looks. that's gccgo?

The compiler is GC based, ported to mips32. You must understand that the compiler is still experimental (with that being said I can't really trust the compiler) and I don't have access to mips machine, so it would be hard for me to debug this.

I try to build tags by noasm (go build -tags=noasm main.go) target run error on the way.

I use  noasm  tag on amd64 so that it would use non-optimized go implementation instead of optimized asm version, as you can see the panic were generated by non-optimized go implementation.
For now, you may can try disabling compression, see if it's works.

@syndtr I'm disable compression, that's work!! thanks so much!

Last post remark for other person helpsful
o := &opt.Options{
		Compression:opt.NoCompression,
	}
	fmt.Println(o.GetCompression().String())
	db, err := leveldb.OpenFile("data", o)
	if err != nil {
		fmt.Println("error:", err)
	}
	defer db.Close()


Metadata not prefixing with namespace index if custom [Name] set on an [External] class

If a [Name] attribute is configured on an [External] class, the custom name value is not being prefixed with the namespace index within the reflection metadata.
Steps To Reproduce
https://deck.net/59eb95b1f1bf57357c8987bb0660c3a4
class Test
{
    public static void Main()
    {
        var type = typeof(MyClass);
        Console.WriteLine(type.GetProperties());
    }
}

class MyClass
{
   internal MyApi api { get; private set; }
}

[External]
[Name("foo")]
class MyApi
{
    string Name { get; }
}

Expected Result
// without [Name]
"rt":$n[1].MyApi

// with [Name[
$n[1].foo

Actual Result
// without [Name]
"rt":$n[1].MyApi

// with [Name[
"rt":foo

See Also

https://forums.bridge.net/forum/bridge-net-pro/bugs/4511-reflection-bug-external

It should not be prefixed at all. Name attribute defines a full name (namespace should be included to the name already). In other words, foo is a full name. You have to provide foo implementation in javascript before using it in Bridge code.


[Web3 1.0.0] Transactions (.send) should have current return type

send methods in web3 target have incorrect return types.
Here is a failing test proving what's wrong: https://github.com/ethereum-ts/TypeChain/pull/129 Current return type is T (boolean in that case) where it should be a transaction object.
This could be an error in web3 typings, not necessary in Typechain but it will probably require some changes in typechain as well.

Sorry to say: Really bad issue. Not actionable. I know you are the maintainer, but still, come on.

@krzkaczor I have a question here. Why do we need to return void in place of Task? As per my understanding, while returning void, it will be difficult to determine whether the task has finished successfully or not.

Has been fixed.

where is this fixed? It's PR hasn't been referenced on this issue/

nah, it's not fixed. @Levino what do you mean?

I mean that my comment does not apply any more because the issue description has been fixed.

Ahh okay. Yeah, so it was usable before it's just a little bit too permisive. Sorry for the confusion.
@vikaskyadav let me know if you're interested in working on this issue. I suspect its 1 line code change.

@krzkaczor yeah. I am interested but will have to look in the tests part.

@krzkaczor could you tell me where to write the tests and do I need to update other tests as well? Is it this file ?

Sounds good @nanspro, you're good to go!

that I can also see. If you are this much active, you could have at least replied on this thread

I do not understand your point. Did I do something wrong?

Frankly, @vikaskyadav your PR is not really fixing anything. This bug is about code generation part of Typechain.

I am not really engaged in this issue but the issue description is still very very bad. No way you can do a proper QA session with this. I suggest taking some time to explain what exactly is the issue and how to verify that is has been fixed afterwards.

Following the current issue desription, I would say that #127 fixes the issue as described above.

@Levino yeah, I somehow agree. I think that problem description is good enough if you are familiar with what this project does, the terminology and some internals.

Following the current issue description, I would say that #127 fixes the issue as described above.

I can't agree with that.
This is such a small issue that instead of spending time describing it I can just fix it.

That being said I will rewrite the description again.

Frankly, @vikaskyadav your PR is not really fixing anything. This bug is about code generation part of Typechain.

I know. I am just trying to understand the codebase

@vikaskyadav  please tell ASAP as i am going through the codebase since last 2.5hrs and i don't want to waste more time if you are interested in this issue!!

Sorry for the havoc guys @vikaskyadav @nanspro. I updated the issue description and added repro case. Now it should be clearer what's here to fix.

Hi, @ceresstation @krzkaczor @nanspro. bishnoi, You can continue working on the issue. I have no issues. I was just interested in trying out the code. :+1:

To generate typescript classes of smart contracts, under the hood we are using Web3 so this change should be enough!!
@krzkaczor tell me if you are expecting any other change in Typechain itself.

Yes it's not a dependency but when running the test cases it installs it.

I am creating a PR directly to https://github.com/DefinitelyTyped/DefinitelyTyped

@krzkaczor  What do you mean by updating dependencies?
Are you suggesting that we don't need @types/web3 as a dep or do you want me to update the changes in dep ?

I guess this issue (#109) will be considered "done" if the below has been done:

Write a test for typechain that reproduces the issue and open a PR with that failing test.
Get https://github.com/DefinitelyTyped/DefinitelyTyped/pull/31417 merged (It has been reviewed. If you do not understand the actionables, please continue the conversation on the PR.)
Add a commit to your open PR to typechain which fixes the failing test.

Cheers.

@nanspro I think that the only thing that we need to do in this repo is update deps. Good job

The PR did not get merged and will not get merged without further work.

So I just need to get this one merged since @krzkaczor has already provided the failed test case!!
@Levino sure I'll do the remaining work to get it merged!

https://github.com/ethereum-ts/TypeChain/blob/2415322ae28c6a948c5dca1c369451d6a97a131d/test/integration/targets/web3-1.0.0/package.json#L13
There is the dep to @types/web3 btw.

@Levino  please review ?

I think the initial analysis was incorrect. Please have a look at https://github.com/ethereum-ts/TypeChain/pull/129#issuecomment-450638580

@Levino the PR i put doesn't fixes any bug, it's an proposal to change return type of TransactionObject.send() to TransactionReceipt always as @krzkaczor  suggested so there is no need for a test case if you approve the changes.
@krzkaczor looks like you have already implemented a temporary solution for Typechain to work so i guess i should stop working on this as the issue is done.

Sorry that this one didn't work out guys. @nanspro in holiday spirit I've still sent you a tip :)

@ceresstation  didn't got it :sweat_smile:
:sweat_smile:

In my project the Transaction parameter taken by the send() is the wrong interface. It requires all values to be passed in as seen here:

which leads to this error Im getting:

I think it has something to do with the Transaction object web3-core is importing in the type.d.ts file. The value should be of type any

Is anyone else encountering this issue? Fore reference I am using the latest web3 and typechain

@bryanwho Try replacing the type.d.ts file with this:
import {Transaction} from "web3/eth/types";
import PromiEvent from "@types/web3/promiEvent";
export type Callback<T> = (error: Error, result: T) => void;
export interface TransactionObject<T> {
  arguments: any[];
  call(tx?: Partial<Transaction>): Promise<T>;
  send(tx?: Partial<Transaction>): PromiEvent<T>;
  estimateGas(tx?: Transaction): Promise<number>;
  encodeABI(): string;
}

(Make sure you have @types/web3 and web3 installed (I have<EMAIL_ADDRESS>in this example))

@krzkaczor - Is this issue still open? With the latest TypeChain version 1.2.1, I couldn't reproduce this one though. Let me know if that's not the case. I'd be more than happy to jump in. Thanks!
cc: @ceresstation

I think this might be fixed in web3 typings 🤷♂ I have no further knowledge about this issue. If someone else can confirm it as well that its solved I am happy to close this.

@zero1ne TypeChain just goes through a massive rewrite (there is already opened PR). You should use that branch as a starting point for your work.


!important is not expanded

having a css like:
display: none !important;
will not add a style="display: none !important;" attribute to elements.
The !imporant part is omitted.
But it is useful: https://stackoverflow.com/questions/4013670/gmail-is-ignoring-displaynone

Can you confirm this is still an issue? It seems to work for me:
In [3]: from inlinestyler.utils import inline_css

In [4]: tst = u'
Hello World!
'

In [5]: print inline_css(tst)

Hello World!

In [6]: print inlinestyler.VERSION
(0, 2, 3)

I just retried now, and indeed it works as intended.
I don't know what happened (to me) to get it wrong in the first place.
You can close the bug, very sorry for the noise!


Define minimum steps in rates

As an administrator, I want to define a minimum amount that will be charged as an step.
For instance, I want to define storage as a minimum of 1MB. Anything below 1MB will be considered as 1MB (from 1B to 999B), 1001B will be considered 2MB, etc.

merged as per #88


Centos Vps

Change Type
Correction
Proposed Changes
https://docs.cloudmydc.com/elastic-vps/elastic-vps-overview/centos-vps
***No changes made yet. Unable to change the scaling limit, Centos 7.2, Disk Limit and Do not have IPv6

Closed issue. No screenshot or image saved.


[WIP] Initial commit for Scala 2.12 support

This is a pull request which adds Scala 2.12 support to Quill. Currently there are quite a few libraries which aren't publish for Scala 2.12 yet, they are documented/tracked here.
https://gist.github.com/mdedetrich/a49083b83ea6a517ceaf5401200a6630
I think it would be a good idea to track which libraries need to be published for 2.12 in this pull request
@getquill/maintainers

Issue for 2.12 support for postgres-async https://github.com/mauricio/postgresql-async/issues/199

Issue for 2.12 support for finagle https://github.com/twitter/finagle/issues/505

postgres-async and finagle with Scala 2.12 support were released.
@mdedetrich Will you work on this PR?

@mxl I will rebase it tomorrow

@mxl I have just rebased
Unfortunately, the new version of finagle-postgres-async has a completely different API to the previous one, so that module is now no longer compiling. I will see if I have some time to fix all of the compiler issues but it might be better to get someone who actually created the module to have a look at it

@jilen would you have some time to look into it?

@mxl Awesome, makes sense to wait till he has done his migration and then I will rebase into master when he is done

Migration to finagle-postres 0.4.* moved here.

@mxl Okay, will wait till that branch gets merged into master

Hello everyone. What is the plan date for this PR?
You are the only reason to stay on 2.11 :)

@eld0727 We are waiting for finagle-postgres new release https://github.com/finagle/finagle-postgres/pull/49

We also had to wait for scala 2.12.2 due to this issue

@jilen Scala 2.12.2 was just released (http://www.scala-lang.org/news/releases-1Q17.html) Is it possible to proceed on this issue?

@mdedetrich  Yes, but we had to set finagle-postgres not cross compile against 2.12

@jilen Cool, let me know when finagle-postgres is finally built for 2.12 so we can get Quill on Scala 2.12

@mdedetrich: 0.4.2 is built for 2.12; http://repo1.maven.org/maven2/io/github/finagle/finagle-postgres_2.12/0.4.2/

@gsson https://github.com/getquill/quill/pull/649 Needs to get updated, and when it gets merged to master I can then rebase into this branch

@mdedetrich updated in https://github.com/getquill/quill/pull/759

@alexuf Thanks, I will wait till it gets merged to master and then I will rebase

@mdedetrich it holds for several days.
@fwbrasil Do we have some blockers to not merge #759 ?

@mentegy Just noticed that I forgot to submit my comment on #759. Let's wait for @alexuf feedback.

#759 merged! \o/

cc/ @mdedetrich

@fwbrasil Getting the following when compiling specifically for Scala 2.12.2
[error] /Users/matthewdedetrich/github/quill/quill-core/src/main/scala/io/getquill/dsl/EncodingDsl.scala:38: parameter value e in method liftScalar is never used
[error]   def liftScalar[T](v: T)(implicit e: Encoder[T]): T = NonQuotedException()
[error]                                    ^
[error] /Users/matthewdedetrich/github/quill/quill-core/src/main/scala/io/getquill/dsl/EncodingDsl.scala:48: parameter value e in method liftQueryScalar is never used
[error]   def liftQueryScalar[U[_] <: Traversable[_], T](v: U[T])(implicit e: Encoder[T]): Query[T] = NonQuotedException()
[error]                                                                    ^
[error] /Users/matthewdedetrich/github/quill/quill-core/src/main/scala/io/getquill/dsl/EncodingDsl.scala:38: parameter value e in method liftScalar is never used
[error]   def liftScalar[T](v: T)(implicit e: Encoder[T]): T = NonQuotedException()
[error]                                    ^
[error] /Users/matthewdedetrich/github/quill/quill-core/src/main/scala/io/getquill/dsl/EncodingDsl.scala:48: parameter value e in method liftQueryScalar is never used
[error]   def liftQueryScalar[U[_] <: Traversable[_], T](v: U[T])(implicit e: Encoder[T]): Query[T] = NonQuotedException()
[error]                                                                    ^
[error] /Users/matthewdedetrich/github/quill/quill-core/src/main/scala/io/getquill/dsl/MetaDslMacro.scala:73: parameter value t in method extract is never used
[error]   private def extract[T](value: Value)(implicit t: WeakTypeTag[T]): Tree = {
[error]                                                 ^
[error] /Users/matthewdedetrich/github/quill/quill-core/src/main/scala/io/getquill/dsl/MetaDslMacro.scala:73: parameter value t in method extract is never used
[error]   private def extract[T](value: Value)(implicit t: WeakTypeTag[T]): Tree = {
[error]                                                 ^
[error] three errors found
[error] three errors found
[error] (quill-coreJVM/compile:compileIncremental) Compilation failed
[error] (quill-coreJS/compile:compileIncremental) Compilation failed
[error] Total time: 11 s, completed 06/05/2017 1:19:50 PM

Also not sure how the docker build with travis is working, but I assume you have to specify Scala 2.12 for the build as well?

@mdedetrich see this
we need to tune scalacOptions to left only unused imports I guess

@mdedetrich  Sorry for the late feedback, I've been pretty busy lately. @aij created a separate PR that also disables fatal warnings for 2.12 and I've just merged it.
Thank you very much for driving this, it was very helpful! :)


Add option to set fillOpacity depending on distance

Here is my first try.
This modification allows the user to set a option "distanceOpacity" on true. This option makes the "fillOpacity" option dynamic and depending on the distance of the marker from the map's borders.
With this functionality added and activated, we can easily guess how far are the markers.
Here is a demo : http://kara.62.free.fr/opacityondistance/

Is this option worth adding in the plugin ?

I think you should add an option for the stroke opacity as well. Otherwise very nice!

I thought that keeping only the stroke opaque, would keep informing there are markers on the map and where.
With this modification, distanceOpacity can accept "true" and "false". I could also make it accept "fillOnly" with the current state and change "true" to include also stroke opacity. Is that a good idea?

Seems reasonable ;)


not working!

I just installed this extension and for some reason it's just not working? I am using the latest version of both the extension and vscode.

Cannot reproduce.


[scripts] replace monaco w/ codemirror

Monaco is quite heavy and we already have a fully featured text editor in Composer which we should re-use
Will help with #5235

Resolved by #5789


manifest for jgajek/cuckoo-docker:latest not found

Expected behavior
Actual behavior
Error message: (HTTP code 404) unexpected - {"message":"manifest for jgajek/cuckoo-docker:latest not found"} during install/clone from docker
Information about the Issue
Used Kitematic (lastes version) on WIndows.
Steps to reproduce the behavior
Just try to install yourself

Go to https://hub.docker.com/r/jgajek/cuckoo-docker/tags/
Observe no latest tags were created for that image
Select a different tag in Kitematic
🎉  enjoy container running.

Ideally you open an issue with the repo owner to let them know how frustrating it is that they don't have a latest image tagged


BankingAliasesIBAN id method fixed

Hello everybody
The class method MangoPay::BankingAliasesIBAN.url currently uses a bad syntax, which causes an error.
The super keyword in Ruby calls the superclass method. In this case, it returns a String.
super.url(id) leads to the following error
NoMethodError:
       undefined method `url' for "/v2.01/sdk-unit-tests/bankingaliases/163665005":String

Any news concerning this patch?


The classpath for BSP when using the mill dev.launcher is too long

Hi,
When I set up BSP using mill.contrib.BSP/install, from a mill launcher generated with mill dev.launcher, the generated BSP file (.bsp/mill.json) contains an extremely long classpath string, which prevents IntelliJ from loading the project.

/home/stig/mill/dev/resources:/home/stig/mill/out/dev/compile/dest/classes:/home/stig/mill/scalalib/resources:/home/stig/mill/out/scalalib/compile/dest/classes:/home/stig/mill/main/resources:/home/stig/mill/out/main/compile/dest/classes:/home/stig/mill/main/core/resources:/home/stig/mill/out/main/core/compile/dest/classes:/home/stig/mill/main/moduledefs/resources:/home/stig/mill/out/main/moduledefs/compile/dest/classes:/home/stig/mill/main/api/resources:/home/stig/mill/out/main/api/compile/dest/classes:/home/stig/mill/main/client/resources:/home/stig/mill/out/main/client/compile/dest/classes:/home/stig/mill/scalalib/api/resources:/home/stig/mill/out/scalalib/api/compile/dest/classes:/home/stig/mill/scalajslib/resources:/home/stig/mill/out/scalajslib/compile/dest/classes:/home/stig/mill/scalajslib/api/resources:/home/stig/mill/out/scalajslib/api/compile/dest/classes:/home/stig/mill/scalanativelib/resources:/home/stig/mill/out/scalanativelib/compile/dest/classes:/home/stig/mill/scalanativelib/api/resources:/home/stig/mill/out/scalanativelib/api/compile/dest/classes:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala-library/2.13.2/scala-library-2.13.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-sbt/test-interface/1.0/test-interface-1.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/scalafmt-dynamic_2.13/2.2.1/scalafmt-dynamic_2.13-2.2.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite_2.13.2/2.2.0/ammonite_2.13.2-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/trees_2.13/4.3.7/trees_2.13-4.3.7.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/coursier_2.13/2.0.0-RC6-25/coursier_2.13-2.0.0-RC6-25.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/net/java/dev/jna/jna/5.0.0/jna-5.0.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/net/java/dev/jna/jna-platform/5.0.0/jna-platform-5.0.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/eed3si9n/jarjarabrams/jarjar-abrams-core_2.13/0.3.0/jarjar-abrams-core_2.13-0.3.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.13.2/scala-compiler-2.13.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/sourcecode_2.13/0.2.1/sourcecode_2.13-0.2.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/os-lib_2.13/0.7.1/os-lib_2.13-0.7.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/upickle_2.13/1.2.0/upickle_2.13-1.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-sbt/ipcsocket/ipcsocket/1.0.0/ipcsocket-1.0.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/scalafmt-interfaces/2.2.1/scalafmt-interfaces-2.2.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/interface/0.0.21/interface-0.0.21.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/typesafe/config/1.3.3/config-1.3.3.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-terminal_2.13/2.2.0/ammonite-terminal_2.13-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-ops_2.13/2.2.0/ammonite-ops_2.13-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-util_2.13/2.2.0/ammonite-util_2.13-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-runtime_2.13.2/2.2.0/ammonite-runtime_2.13.2-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-interp-api_2.13.2/2.2.0/ammonite-interp-api_2.13.2-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-repl-api_2.13.2/2.2.0/ammonite-repl-api_2.13.2-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-interp_2.13.2/2.2.0/ammonite-interp_2.13.2-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ammonite-repl_2.13.2/2.2.0/ammonite-repl_2.13.2-2.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/common_2.13/4.3.7/common_2.13-4.3.7.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/thesamet/scalapb/scalapb-runtime_2.13/0.9.6/scalapb-runtime_2.13-0.9.6.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/fastparse_2.13/1.0.1/fastparse_2.13-1.0.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/coursier-core_2.13/2.0.0-RC6-25/coursier-core_2.13-2.0.0-RC6-25.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/coursier-cache_2.13/2.0.0-RC6-25/coursier-cache_2.13-2.0.0-RC6-25.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/github/alexarchambault/argonaut-shapeless_6.2_2.13/1.2.0-M12/argonaut-shapeless_6.2_2.13-1.2.0-M12.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/net/java/dev/jna/jna/5.3.1/jna-5.3.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/pantsbuild/jarjar/1.7.2/jarjar-1.7.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala-reflect/2.13.2/scala-reflect-2.13.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/jline/jline/3.14.1/jline-3.14.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/geny_2.13/0.6.2/geny_2.13-0.6.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/ujson_2.13/1.2.0/ujson_2.13-1.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/upack_2.13/1.2.0/upack_2.13-1.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/upickle-implicits_2.13/1.2.0/upickle-implicits_2.13-1.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/fansi_2.13/0.2.9/fansi_2.13-0.2.9.jar:/home/stig/.cache/coursier/v1/
https/repo1.maven.org/maven2/org/scala-lang/modules/scala-collection-compat_2.13/2.1.4/scala-collection-compat_2.13-2.1.4.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/pprint_2.13/0.5.9/pprint_2.13-0.5.9.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/requests_2.13/0.6.5/requests_2.13-0.6.5.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/github/scopt/scopt_2.13/3.7.1/scopt_2.13-3.7.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/ch/epfl/scala/bsp4j/2.0.0-M6/bsp4j-2.0.0-M6.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/scalaparse_2.13/2.3.0/scalaparse_2.13-2.3.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/javassist/javassist/3.21.0-GA/javassist-3.21.0-GA.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_2.13/1.3.0/scala-xml_2.13-1.3.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/jline/jline-terminal/3.14.1/jline-terminal-3.14.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/jline/jline-terminal-jna/3.14.1/jline-terminal-jna-3.14.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/jline/jline-reader/3.14.1/jline-reader-3.14.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/github/javaparser/javaparser-core/3.2.5/javaparser-core-3.2.5.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/thesamet/scalapb/lenses_2.13/0.9.6/lenses_2.13-0.9.6.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/fastparse_2.13/2.3.0/fastparse_2.13-2.3.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalameta/fastparse-utils_2.13/1.0.1/fastparse-utils_2.13-1.0.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/coursier-util_2.13/2.0.0-RC6-25/coursier-util_2.13-2.0.0-RC6-25.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/github/alexarchambault/windows-ansi/windows-ansi/0.0.3/windows-ansi-0.0.3.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/io/argonaut/argonaut_2.13/6.2.4/argonaut_2.13-6.2.4.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/chuusai/shapeless_2.13/2.3.3/shapeless_2.13-2.3.3.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/ant/ant/1.9.9/ant-1.9.9.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/ow2/asm/asm/7.0/asm-7.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/ow2/asm/asm-commons/7.0/asm-commons-7.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/3.3.9/maven-plugin-api-3.3.9.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/lihaoyi/upickle-core_2.13/1.2.0/upickle-core_2.13-1.2.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/lsp4j/org.eclipse.lsp4j.generator/0.8.1/org.eclipse.lsp4j.generator-0.8.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/lsp4j/org.eclipse.lsp4j.jsonrpc/0.8.1/org.eclipse.lsp4j.jsonrpc-0.8.1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.18/jansi-1.18.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/ant/ant-launcher/1.9.9/ant-launcher-1.9.9.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/ow2/asm/asm-tree/7.0/asm-tree-7.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/ow2/asm/asm-analysis/7.0/asm-analysis-7.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/maven/maven-model/3.3.9/maven-model-3.3.9.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/maven/maven-artifact/3.3.9/maven-artifact-3.3.9.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/sisu/org.eclipse.sisu.plexus/0.3.2/org.eclipse.sisu.plexus-0.3.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/xtend/org.eclipse.xtend.lib/2.18.0/org.eclipse.xtend.lib-2.18.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/google/code/gson/gson/2.8.2/gson-2.8.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/3.0.22/plexus-utils-3.0.22.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/apache/commons/commons-lang3/3.4/commons-lang3-3.4.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/javax/enterprise/cdi-api/1.0/cdi-api-1.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/sisu/org.eclipse.sisu.inject/0.3.2/org.eclipse.sisu.inject-0.3.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/codehaus/plexus/plexus-classworlds/2.5.2/plexus-classworlds-2.5.2.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/xtext/org.eclipse.xtext.xbase.lib/2.18.0/org.eclipse.xtext.xbase.lib-2.18.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/org/eclipse/xtend/org.eclipse.xtend.lib.macro/2.18.0/org.eclipse.xtend.lib.macro-2.18.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/javax/annotation/jsr250-api/1.0/jsr250-api-1.0.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/javax/inject/javax.inject/1/javax.inject-1.jar:/home/stig/.cache/coursier/v1/https/repo1.maven.org/maven2/com/google/guava/guava/21.0/guava-21.0.jar -i mill.contrib.BSP/start

This command is too long for IntelliJ to run, which causes IntelliJ to fail to open the project properly

env: ‘/home/stig/mill/dev/resources:/home/stig/mill/out/dev/compile/dest/classes:/home/stig/mill/scalalib/resources:(and so on): File name too long

When using a regular Mill release, the corresponding string is much smaller

/home/stig/.cache/mill/download/0.8.0 -i mill.contrib.BSP/start

Would an option be for the dev.launcher command to put the dependency jars in a directory somewhere, so they can be referenced with a wildcard in the classpath?

The long classpath is coming from here https://github.com/lihaoyi/mill/blob/8cd135ad640b2732462739f6b104df4d3ac7edc1/contrib/bsp/src/mill/contrib/BSP.scala#L74-L76
The shell script generated by dev.local had a similar problem, which was solved in https://github.com/lihaoyi/mill/pull/791 to address issues on Windows. The reason that fix doesn't affect this issue is that even if Mill uses a classpath jar in the launcher script, the BSP install command will read the expanded classpath through java.class.path, and write the expanded classpath to the .bsp/mill.json file.
I think the BSP install command should do something similar to what Mill's build.sc does, by writing a classpath jar. It would be nice if the BSP script could reuse the classpath jar generated by dev.local, but I don't see a good way to pass the path to that jar to the BSP command.
Maybe the best solution is to have BSP/install generate a new classpath jar with the java.class.path in the manifest, write that jar to the .bsp directory, and write the .bsp/mill.json to point to that jar?

Raised a PR with a first attempt at a solution.

Mill's BSP server isn't designed to be run via mill dev.launcher.


[BUG] CI crashes when source branch contains a quote character

:bug: Bug report
Current Behavior

When the PR branch name contains a ' or ", the Set Code Climate PR Vars step fails with an unterminated quote character.
Expected Behavior

CI does not crash
Minimal reproduction of the problem with instructions

https://dev.azure.com/graycore/Daffodil/_build/results?buildId=7671&view=logs&j=93920417-eedc-5d0d-3fdd-d383262f4173&t=fb64ba39-b2b0-5175-8956-0ddbdfddad70
What is the motivation / use case for changing the behavior?

Others:

This is most likely an azure bug, System.PullRequest.SourceBranch should automatically escape special chars. We can probably ignore this for now, as we will soon (TM) switch to GH actions.

I'm going to assume that this is closed by #2419


add link to error summary box

Add error summary component  link.
This is part of: https://trello.com/c/btdB5xBK/98-missing-contextual-error-messaging-on-cookie-settings-page

Looks good to me.
I like the way this can be deployed independently of alphagov/digitalmarketplace-govuk-frontend#124.


Paket FizzBin / paket restore

Recently I've tried to explain Paket to a number of people who are well versed in NuGet, .net, MSBuild (and in 2/3 cases, F#)
Examples:

https://github.com/fsprojects/Paket/issues/166 - https://github.com/fsprojects/Paket/issues/166#issuecomment-56818046
https://github.com/ploeh/Hyprlinkr/issues/33#issuecomment-56847064
https://jabbr.net/#/rooms/fsharp
various twitter discussions / DMs / Skype conversations.

I'd like to make a plea that you read this "NuGet Package Restore misconceptions" article by Jeff Handley of the NuGet team as it filled in / accentuated some key points for me. I don't think I was guilty of any of the misconceptions, but it leads into what I will say after the jump. If you're going to bother to read on, PLEASE read the link - there's no point in reading on without the context
So, my 'solution' is to attempt to write a compact guide to Paket that doesn't:
a) assume it can say "inspired by bundler" and not have that trigger 0-15 good things and 2-4 bad things dependeing on people's experience
b) does not work with detailed examples with a goal of having people read rather than scan it
c) have something that people are expected to read before anything.
i.e. if something that if there's evidence that any core point is missing from somone's understanding, that one could (either conceptually or really be told "Come back when you've read link or we have no shared understanding and we're going to find out in 20 mins time that there are massive broken assumptions)
So.... v1 of it is:

Restore is implemented, install has new semantics


Fix NPM build scripts

Currently the build script is somewhat buggy as it doesn't properly generate the minified sources.
Also there is a typo in the .babel_rc filename (.babal_rc).

How dead is this project?


Address various issues

This PR aims to close the following issues:

https://github.com/oscar-system/JToric.jl/issues/48
https://github.com/oscar-system/JToric.jl/issues/47
https://github.com/oscar-system/JToric.jl/issues/45
https://github.com/oscar-system/JToric.jl/issues/44

@HereAround BTW, I am also willing to make some of the changes I suggest -- just let me know if you agree with the suggestion, and whether it is OK to change it, then I can push corresponding changes here. That may be more efficient.

There is a show method in my PR that comes after this.

I'll merge this so that @lkastner PR can be rebased if needed, and will submit my tweaks in a separate PR.


NO BUG - request for configration help or more documentation

Hi,
i am trying to configure airline so it suits me but i am having a hard time.
So far i could bend the the solarized color theme a bit. but i am stuck at
the point where i want to change the color of the file type. Another but
more font related issue is that the left pointing arrowhead is bad aligned
so that there is always some ugly gap. I hope you have some advice
on that or can point me to people who know how to deal with that.
A last thing that is disturbing only a bit is that i see tiles of my last
session in the tabline when i call vim without files.
Thanks for you really nice plugin!
http://www.enlightenment.org/ss/e-52d29ab1ce2d79.62468388.jpg
Best Regards!
Obi

@bling (piggy-backing off of this question) How do I change the color of the unsaved changes indicator from purple to something else?

@atav32 changing colors is simple; you just need to modify the theme directly.  you can copy a theme into your ~/.vim/autoload/airline/themes and change the value for modified groups.
@ObiWahn going over this issue again, you want to change the color of the filetype right?  well, to do that you need to understand how the statusline is built.  for ease of configuration, colors are predefined for sections.  e.g. g:airline_section_a has a predefined color given to it.  however, each section can contain multiple parts.  the filetype is a part.  so to change the color of the filetype means that you either give it a different color, using accents, or you make sure that it's the only thing contained inside a section.
long story short, add this to your vimrc:
autocmd User AirlineAfterInit call airline#parts#define_raw('myfiletype', '%y')
autocmd User AirlineAfterInit call airline#parts#define_accent('myfiletype', 'red')
autocmd User AirlineAfterInit let g:airline_section_x = airline#section#create(['myfiletype'])

the red accent is defined in the theme, as is all the colors for the various sections.  you shouldn't be changing any highlight groups manually.


heat stack-update and scale-in/scale-out

In general we need that our heat resource types support the stack-update operation. This is needed to fix failed stacks otherwise they have to be left stale in the system. I understand updating all the resource types requires a major effort.
On the other hand, stack-update is also needed to allow for scaling-in/scaling-out services (typically changing the number of pool members). This is a must have operation which we cannot do currently.
From my point of view allowing stack-update operations on the F5::Sys::iAppService resource type should be on top of our list.
Regards
   Ulises

@pjbreaux could you scope the work needed for these two issues: #126 and #127

Stack update is orthogonal work to scale in/out. That work would take around 3-5 days of code update and testing.
I'm moving scale in/out to a separate issue, to capture the work there.

Just wanted to comment that when the F5 itself is the only element implementing the functionality (ie: no servers used) like in the case of APM (ie: number or users), PEM/AFM (ie:  (ie:bandwidth allocation), only stack-update would be needed to update to provide full scale-in scale-out
I understand/guess that with orthogonal you mean  regular scale-in/out should be implemented like https://github.com/F5Networks/f5-openstack-heat/issues/130 ?

In summary I find we need this to:

fix failed stacks
reconfigure the stack (ie: updating any setting)
scale-in/scale-out (ie: adding/removing members) which could be seen as a subset of reconfiguration use case

+1 This fix would be a must to use F5 heat templates for NFV Virtual Gi LAN deployments. Capacity grows continuously in such scenarios and the option to update existing multi-VE HEAT deployments (scale-out) with additional VEs is very important for SP business continuity.


General troubleshooting thread

I'm unable to run the browsers as the drivers are inaccessible. It seems the driver version is not set correctly in the driver path (see log below).
Connected to that:

What should be the content of the drivers folder? Should it be the three folders chrome/firefox/operadrivers? Or should I copy these things out as well? (I tried both.)
Is it really necessary to add the drivers folder to the PATH (as it seems every browser version seems to set it itself separately due to different drivers)?

Note that the script worked some -- I generated a couple of screenshots in one run, but from then on this bug seems to occur all the time. If I resolve it, I'll update the issue.
08-Sep-19 21:41:32 - INFO - ######## Processing firefox v(64.0)
08-Sep-19 21:41:32 - INFO - # Installing the browser.
08-Sep-19 21:42:02 - INFO - # Installation done.
08-Sep-19 21:42:02 - INFO - # Preparing iteration.
08-Sep-19 21:42:02 - INFO - ##################################################
08-Sep-19 21:42:02 - INFO -
08-Sep-19 21:42:02 - INFO -            firefox 64.0 expired
08-Sep-19 21:42:02 - INFO -
08-Sep-19 21:42:02 - INFO - ##################################################
08-Sep-19 21:42:02 - INFO - Preparing driver path.
08-Sep-19 21:42:02 - INFO - Driver path set to - C:\Users\Username\Documents\tls-warning-collector\drivers\firefoxdrivers\geckodriver-
08-Sep-19 21:42:02 - INFO - Parsing browser full version to short.
08-Sep-19 21:42:02 - INFO - Browser short version - 64
08-Sep-19 21:42:02 - INFO - Getting geckodriver version.
08-Sep-19 21:42:02 - INFO - Geckodriver version - 24.
08-Sep-19 21:42:02 - INFO - Capabilities are set to - {'marionette': True}
08-Sep-19 21:42:02 - INFO - Preparing driver.
08-Sep-19 21:42:02 - ERROR - Something went TERRIBLY wrong. - Message: 'geckodriver.exe',)' executable needs to be in PATH.

It happened to me as well sometimes. I will try to fix it with setting the SystemProperty each time before the driver is used.
System.setProperty("webdriver.gecko.driver", "path/to/geckodriver.exe");
System.setProperty("webdriver.chrome.driver", "path/to/geckodriver.exe"); -- for both Chromium and Opera

Uff, after some time spend debugging I see the culprit.
In browesrs.py on line 114 there is an extra comma that causes the exe variable to be defined as a tuple instead of a string.
The bug was introduced in commit 625f314 26 days ago -- did it work for you since then?

Though running it now, I get other errors:

Some firefox/error combinations work OK (e.g. FF64/expired).
Sometimes (e.g. FF64/wrong-host) I get: ERROR - Something went TERRIBLY wrong. - Message: Reached error page: about:neterror?e=fileNotFound&u=https%3A//wrong-host.badssl.com/&c=UTF-8&f=regular&d=Firefox%20can%27t%20find%20the%20file%20at%20https%3A//wrong-host.badssl.com/
Sometimes (e.g. FF63/expired): ERROR - Something went TERRIBLY wrong. - Message: Unable to find a matching set of capabilities

Did all the cases, browsers and versions pass for you as written in the documentation?

All of these issues should be resolved now.


[Async] Add Pharo-like api aliases to Streams

We need:

TAsyncStream>>#collect: as an alias to TAsyncStream>>#map:
TAsyncStream>>#select: as an alias to TAsyncStream>>#filter:
TAsyncStream>>#do: as an alias to TAsyncStream>>#forEach:

((((1 to: 6) asAsyncStream
	collect: [ :each | each + 10 ])
	select: [ :each | each even ])
	do: [ :each | each traceCr ]) await


Hiding doesn't work with RecyclerView if I use my setOnScrollListener() for onScrollStateChanged and OnScroll

I'm using recyclerview and I use the onScrollStateChanged event refreshing my list (pull to refresh) and I also use onScrolled event to handle the paging (getting new rows if I reached the bottom).
If I comment out the OnScrollStateChaned code, the auto hide feature working fine, but with this the auto-hide doesn't work.
How to handle this?
The source code:
recyclerView.setOnScrollListener(new RecyclerView.OnScrollListener() {
@Override
public void onScrollStateChanged(RecyclerView recyclerView, int newState) {
super.onScrollStateChanged(recyclerView, newState);
            // Reached the bottom, getting new activities
            if (!isLoading && adapter != null && adapter.getItemCount() == (layoutManager.findLastVisibleItemPosition() + 1)
                    && newState == RecyclerView.SCROLL_STATE_IDLE) {

                // Getting new activity items
                ActivitiesTask aTask = new ActivitiesTask(ActivitiesFragment.this, false);
                try {

                    if (adapter == null) {
                        aTask.execute("1","20");
                    }
                    else {
                        int last = adapter.getItemCount()+1;
                        aTask.execute(Integer.toString(last), Integer.toString(last+pageSize-1));
                    }
                }
                catch (Exception e)
                {
                    aTask.cancel(true);
                    alert(getString(R.string.no_activities_found));
                }
            }
        }

        @Override
        public void onScrolled(RecyclerView recyclerView, int dx, int dy) {
            super.onScrolled(recyclerView, dx, dy);

            swipeRefreshLayout.setEnabled(layoutManager.findFirstCompletelyVisibleItemPosition() == 0);
        }
    });

I got exactly the same issue.

I ran into the same issue.
If FAB is attached to the RecyclerView then onScrolled doesn't even get called. What I ended up using is the following workaround:
Do not attach FAB to the RecyclerView.
Use the following code in onScrolled:
    mRecyclerView.setOnScrollListener(new RecyclerView.OnScrollListener() {

        @Override
        public void onScrolled(RecyclerView recyclerView, int dx, int dy) {
            if (mLayoutManager.findFirstVisibleItemPosition() > lastKnownFirst) {
                mFab.hide(true);
            } else if (mLayoutManager.findFirstVisibleItemPosition() < lastKnownFirst) {
                mFab.show(true);
            }
            lastKnownFirst = mLayoutManager.findFirstVisibleItemPosition();
        }
    });


Upgrade axe-core

2.1.7 is the latest
Thanks :)

Thanks! #142 contains the changes, but some help URLs and HTML formatting needs to be adapted to make the tests pass as far as I can see. I am on mobile only right now, if you get the build green I will merge.


doc running-a-full-node#create-an-account-and-get-its-address

https://docs.celo.org/v/master/getting-started/running-a-full-node#create-an-account-and-get-its-address
docker run -v $PWD:/root/.celo --entrypoint /bin/sh -it $CELO_IMAGE:$CELO_NETWORK -c "geth account new"
Is $PWD an environment variable which I should have declared earlier?
What exactly does this code -v $PWD:/root/.celo do?
docker run --help about -v parameter:
-v, --volume list                    Bind mount a volume
      --volume-driver string    Optional volume driver for the container
      --volumes-from list         Mount volumes from the specified container(s)

https://docs.docker.com/storage/volumes/
Consists of three fields, separated by colon characters (:). The fields must be in the correct order, and the meaning of each field is not immediately obvious.
Great explanation :)
You pass a password to mount the folder '/root/.celo'?
Is docker run -v`pwd`:/root/.celo also passing an env variable pwd?
(https://docs.celo.org/v/master/getting-started/faucet#creating-an-empty-account-with-the-celo-client)
Why does it still ask to set a passphrase then?
PS: I'm going in great detail here because I spent a lot of time trying to get it working in Powershell.
Mainly due to the error
Fatal: Failed to read passphrase: liner: function not supported in this terminal
For which I already found the answer here.

$pwd or pwd stands for print working directory in linux.
"$pwd" also return the current working directory in PowerShell on windows.
--volume "${pwd}:/root/.celo" makes the local working directory available as a volume in the linux docker container at the path /root/.celo.


How to tell what version of sqlpackage.exe we have is?

The only thing I can find is a copyright for 2016, and I think the MSI on this page is later than that.

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

ID: bf3df6af-9ac8-bc57-93dc-29ff713c1d3b
Version Independent ID: 7624e2cc-7aa9-40dd-4015-3371ea2ea0a2
Content: Download and install sqlpackage - SQL Server
Content Source: docs/tools/sqlpackage-download.md
Product: sql
Technology: tools-other
GitHub Login: @pensivebrian
Microsoft Alias: broneill

Right now, the only way is to right click on the sqlpackage.exe file, select properties, and on the details tab, check the file version.
I'll add a /version parameter next release. I'll update the copyright and print the version in the header as well :)
Thanks for reporting.

@StingyJack -- thank you for your question.
@pensivebrian -- thank you for answering!
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


can't find TM1650

though site shows 2 results

It seems search as a whole has broken (again), so I'll have to see what they changed and adjust the codebase...

not that search doesn't work at all: it's just incomplete.
Thanks!

I just tried searching for ATMEGA168 and that gave me no results as well.

https://github.com/dnet/adsdroid/issues/27 may help as a workaround.


Helm 3.5 - Fail to use OCI Hosted Chart Dependency

Output of helm version:
version.BuildInfo{Version:"v3.5.0", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.6"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.4", GitCommit:"c96aede7b5205121079932896c4ad89bb93260af", GitTreeState:"clean", BuildDate:"2020-06-17T11:41:22Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): AKS
I am trying to use the new OCI support but I cannot get it to work. I am using HELM_EXPERIMENTAL_OCI=1
My app chart has the following.
apiVersion: v2
name: my-chart

type: application

version: 0.2.0

# The following is replaced by the application Docker image TAG during the deployment.
appVersion: none

dependencies:
- name: common
  version: "^0.0.5"
  repository: "https://charts.helm.sh/incubator/"
- name: mylib-chart
  version: "0.1.0"
  repository: oci://acrmythingdev001.azurecr.io/helm/incubator/mylib-chart:0.1.0

When I then run a helm dependency update I get the following error:
> helm dependency update
Getting updates for unmanaged Helm repositories...
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x18 pc=0x12bdfee]

goroutine 24 [running]:
helm.sh/helm/v3/internal/experimental/registry.(*Client).PullChart(0x0, 0xc0002c8720, 0xc0002c8720, 0x0, 0x0)
        /home/circleci/helm.sh/helm/internal/experimental/registry/client.go:156 +0x18e
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get(0xc0008e5400, 0xc000087020, 0x57, 0x20, 0x163fa20, 0x173f601)
        /home/circleci/helm.sh/helm/pkg/getter/ocigetter.go:52 +0xd0
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get(0xc0008e5400, 0xc000087020, 0x57, 0xc0002c8680, 0x4, 0x4, 0xc000346780, 0x0, 0x0)
        /home/circleci/helm.sh/helm/pkg/getter/ocigetter.go:36 +0x7e
helm.sh/helm/v3/pkg/repo.(*ChartRepository).DownloadIndexFile(0xc0002e1ae0, 0x0, 0x0, 0x0, 0x0)
        /home/circleci/helm.sh/helm/pkg/repo/chartrepo.go:125 +0x333
helm.sh/helm/v3/pkg/downloader.(*Manager).parallelRepoUpdate.func1(0xc0007fb3b0, 0xc000038aa0, 0xc0002e1ae0)
        /home/circleci/helm.sh/helm/pkg/downloader/manager.go:655 +0x47
created by helm.sh/helm/v3/pkg/downloader.(*Manager).parallelRepoUpdate
        /home/circleci/helm.sh/helm/pkg/downloader/manager.go:654 +0x9b

On a side note, if my chart dependecy does not include a tag
dependencies:
- name: common
  version: "^0.0.5"
  repository: "https://charts.helm.sh/incubator/"
- name: cpglib-chart
  version: "0.1.0"
  repository: oci://acrmythingdev001.azurecr.io/helm/incubator/mylib-chart

I get a different error however I think that is expected
> helm dependency update
Getting updates for unmanaged Helm repositories...
...Unable to get an update from the "oci://acrmythingdev001.azurecr.io/helm/incubator/mylib-chart" chart repository:
        tag explicitly required
...Successfully got an update from the "https://charts.helm.sh/incubator/" chart repository
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "acrmythingdev001" chart repository (https://acrmythingdev001.azurecr.io/helm/v1/repo):
        failed to fetch https://acrmythingdev001.azurecr.io/helm/v1/repo/index.yaml : 401 Unauthorized
Update Complete. ⎈Happy Helming!⎈

Hello - this has to do with how you are specifying dependencies. The repository must be the parent namespace, and the chart name must match name. Closing as duplicate of https://github.com/helm/helm/issues/9267

Hello - this has to do with how you are specifying dependencies. The repository must be the parent namespace, and the chart name must match name. Closing as duplicate of https://github.com/helm/helm/issues/9267


Improve README

The README could be cleaned up a bit and have some information expanded upon - A table of contents would be nice, as well as cleaning up some of the strangely phrased descriptions in the list of scripts. Additionally, some information on contributing could be added to the README as well.

Great idea, do you want to work on it @burschc

@DhanushNehru Do you see any scope to work on this? Or shall I just pass it?

Hi @ShubhamNagure you can incorporate any ideas to make the readme better


Not able to create secret with EKS

Hello,
I have read the document and I believe I am using the manifest correctly. I am using azure/k8s-set-context@v3 to set the context first. It seems to be successful (but I'm not 100% sure). Here is the debug info for that portion:
##[debug]Writing kubeconfig contents to /home/runner/work/_temp/kubeconfig_1674177059730
##[debug]Setting KUBECONFIG environment variable
##[debug]Node Action run completed with exit code 0
##[debug]KUBECONFIG='/home/runner/work/_temp/kubeconfig_1674177059730'
##[debug]Finishing: Set the Kubernetes context

Then I am using azure/k8s-create-secret@v4 and I get a timeout when trying to connect to the EKS URL. I don't have a problem creating the secret the usual way with a manifest.
Here is my GHA code:
        uses: azure/k8s-set-context@v3
        with:
          method: kubeconfig
          kubeconfig: ${{ secrets.KCONFIG }}
          context: 'arn:aws:eks:us-east-1:{my_account_number}:cluster/{my_cluster_name}'
        id: set-context
      - name: Set imagePullSecret
        uses: azure/k8s-create-secret@v4
        with:
          namespace: '{my_namespace}'
          secret-name: 'ghcr'
          container-registry-url: 'ghcr.io/{my_org_id}'
          container-registry-username: ${{ github.actor }}
          container-registry-password: ${{ secrets.PAT }}
        id: create-secret

Here is the DEBUG output:
Warning: Failed to delete secret with statusCode: undefined
Deleting secret:
undefined
Creating secret
{"errno":-110,"code":"ETIMEDOUT","syscall":"connect","address":"10.XX.31.115","port":443}
Error: connect ETIMEDOUT 10.XX.31.115:443
##[debug]Node Action run completed with exit code 1
##[debug]Finishing: Set imagePullSecret

Can you please help me understand if/what I'm doing wrong?
Thanks in advance!

hi @onabison , when you say you "don't have a problem creating the secret the usual way with a manifest" do you mean kubectl apply from a github action running it as a script instead of using the k8s-create-secret action?
since there is a timeout in the network call, it could be an issue with the KUBECONFIG causing the calls to fail


JSON corrupting with change of object value

Describe the bug
A clear and concise description of what the bug is.
Deploying to a production environment and using the ability to change object values to update a web URL in the pipeline
Once the code is deployed mappings in the pipeline are missing. We have tried with and without to evaluate the issue and get it to work. Deploys ok without URL change mappings are present. Use config file to create URL change and the problem occurs
To Reproduce
Your script to reproduce the behaviour:
Added this to the config-Production.csv (URL has been modified to protect a system)
pipeline,GetFusebillCustomers_ToBlob,activities[0].typeProperties.url,https://abcheg-prd-it-akv-001.vault.azure.net/secrets/secretKey/9e0e3e8561b040f7c34d4ffa0u983a78?api-version=7.0
Ran Publish-AdfV2FromJson  `
>>     -RootFolder C:\Users\peter\source\repos\MBQLD\Data-Pipelines `
>>     -ResourceGroupName "turagit-data-01" `
>>     -DataFactoryName "TGT-PRD-001" `
>>     -Location "australiaeast" `
>>     -Stage "Production"
(This is not a production system in this test)

Your script here
Ran the command from Powershell on my PC to obtain the changed file to be able to see the source of the issue

Expected behaviour
A clear and concise description of what you expected to happen.
URL to update and all of the JSON would deploy objects successfully
I can provide a copy of the full JSON, but concerned they might leak information
Screenshots
If applicable, add screenshots to help explain your problem.

Version of PowerShell module of:

azure.datafactory.tools [e.g.0.10.1]
Version 0.14.000

Thanks, Peter for raising this issue. I will take a look at this as soon as I can.

Hi Peter. Thanks again for reporting this very precisely.
Could you attach the JSON file of the pipeline?
Please, remove all other activities and leave only the first one (which contains a mapping) if you have any information you would prefer not to share here.

FYI, I have the same issue should another guinea pig be required. Will leave to Peter for now.

Hi Kamil, here is my example.
Issue33.zip

Hi Kamil
Apologies for the late response, been closing out a project
Here is a file. The key vault URL has been altered to not identify the one in use
Example Issue33.zip

I was looking for this and I know where it comes from, but unfortunately, it's not an easy-to-fix issue.

No problem. Thanks for the update, Kamil.

Apparently, this issue has been fixed by merge #55. It will be released in nearest version 0.18.


JEST Test Failure

Hello there, I was hoping to get some insight on how to handle testing around react-virtualized-tree. I'm using JEST for testing and seem to be running into the following error when running unit tests.
src/components/App.test.tsx
  ● Test suite failed to run

    TypeError: Cannot read property 'Expandable' of undefined

I was curious if you've seen this before and had perspective on how to handle.
For added clarity, it is behaving as expected in app. So I suspect this may be related to JEST.

This was rectified by bringing the following line into the render method.
const { Expandable } = Renderers;
Keeping it outside was causing the JEST failure.

Hmm, that is strange, was the component mounting or was it just a jest problem?

I can try to replicate later as this is not expected at all and the component is tested internally with jest too without any issues.
Do you mind sharing your config?

Originally, I was declaring the constant outside of the class which was fine for running.
I think JEST may not have fully reconciled global variables in the same way?
So placing the constant inside of the render method had it mount appropriately.
No need to replicate at this point if you'd rather focus on something else.
Otherwise, I can pull it together for you.
If no one else has had this issue, I'm fine giving you your time back! :)


(GH-2877) wait() with no arguments waits on all Futures from the plan

This amends the wait() plan function to wait on all the Futures that
were spawned from the same plan as the wait() call if the function is
not provided a list of futures. The function still accepts a timeout
or options parameter if it is not passed any futures. To support this,
Bolt's PlanFuture object now has a plan_id attribute, which
determines which invocation of a plan the Future was created from
(since the same plan can be invoked multiple times in parallel). When
wait() is called without Futures, it selects the Futures from the
FiberExecutor with a matching plan_id to itself, and waits on those.
This also removes a flaky test around whether the cache file is updated
when plans in modules are modified. The test doesn't seem to be failing
legitimately based on local testing.

[ ] puppetlabs/orchestrator#1738
[ ] puppetlabs/pe-bolt-modules#20

!feature

wait() without arguments waits on all Futures from plan (#2877)
Calling the wait() plan function without a list of Futures will now
wait on all Futures created so far in the plan.

Still manually testing, but I think this is ready for review. I'll move it back to draft if I find any issues.
Test cases

[x] Only waits on futures from the calling plan, not subplans or parent plans
[x] Accepts just a timeout with no futures
[x] Accepts a timeout and options
[x] Accepts just options
[x] Doesn't wait for itself when called inside background() block
[ ] Waits on Futures created inside a background() after the wait() has been called
[ ] Only waits on futures from a particular invocation

[ ] If the same subplan has been invoked multiple times from a plan
[ ] If the plan is invoked recursively
[ ] Waits on futures created inside a new scope, like each
[ ] Does not wait on futures created in a subplan
[ ] Does not wait on futures created in a subplan run from a new scope

BoltSpec

[ ] Accepts just a timeout with no futures
[ ] Accepts a timeout and options
[ ] Accepts just options

Tests

[x] Only waits on futures from the calling plan, not subplans or parent plans
[x] Accepts just a timeout with no futures
[x] Accepts a timeout and options
[x] Accepts just options
[x] Doesn't wait for itself when called inside background() block
[x] Does not wait on Futures created inside a background() in the calling plan
[x] Only waits on Futures from a particular plan invocation

[x] If a subplan is called multiple times which creates Futures, each subplan will only wait for it's own Futures
[x] If the plan is invoked recursively
[x] Waits on futures created inside a new scope, like each
[x] Does not wait on futures created in a subplan
[x] Does not wait on futures created in a subplan run from a new scope

BoltSpec

[ ] Accepts just a timeout with no futures
[ ] Accepts a timeout and options
[ ] Accepts just options

Just want to confirm if this is expected behavior, since the criteria above states that Futures created inside a background() are not waited on from the calling plan.
Given this plan:
plan bolt (
  TargetSpec $targets = 'localhost'
) {
  background('outer') || {
    run_command('whoami', $targets)

    background('inner') || {
      run_command('echo hi', $targets)
    }
  }

  $results = wait()
  out::message("Waited on ${results.length} futures")
  return $results
}

The output will be:
[
  [
    {
      "target": "localhost",
      "action": "command",
      "object": "echo bye",
      "status": "success",
      "value": {
        "stdout": "bye\n",
        "stderr": "",
        "merged_output": "bye\n",
        "exit_code": 0
      }
    },
    {
      "target": "local://<IP_ADDRESS>",
      "action": "command",
      "object": "echo bye",
      "status": "success",
      "value": {
        "stdout": "bye\n",
        "stderr": "",
        "merged_output": "bye\n",
        "exit_code": 0
      }
    }
  ],
  "Future 'inner'"
]

Both Futures are waited on, and wait() returns the value for each. In this case the first value is the result of the inner background() and the second value is the Future for the inner background(). Logically this seems like correct behavior?

That is expected, I just didn't update the comment. The only thing that matters is that whether the inner backgrounds run or not is predictable and not just based on whether they've been started or not. Now that we're using an actual Plan ID to identify futures, inner Futures will be included in that if they've already started so we need to include all futures even ones that start after calling wait(). This is explicitly accomplished by recursively calling wait() and rechecking for new Futures until all the Futures have finished.
Updated the comment above and the docs.

Overall this is looking good and seems to be working as intended. Still planning on doing a bit more testing, but I'm feeling comfortable with where this is at, especially since parallelism in Bolt is still experimental and existing behavior doesn't break.

Definitely no rush - I'll also do a little more manual testing later today.


add note on image registry

Signed-off-by: Di Xu<EMAIL_ADDRESS>
What type of PR is this?
kind/documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Codecov Report

Merging #187 (0f03974) into main (3ed223a) will increase coverage by 0.07%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##            main    #187      +/-   ##
========================================
+ Coverage   7.69%   7.77%   +0.07%
========================================
  Files         29      29
  Lines       3780    3780
========================================
+ Hits         291     294       +3
+ Misses      3466    3464       -2
+ Partials      23      22       -1

Impacted Files
Coverage Δ

...ernet/clusternet/pkg/hub/apiserver/shadow/utils.go
100.00% <0.00%> (+10.71%)
:arrow_up:

Continue to review full report at Codecov.

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


[KeyVault] - Experiment with global timeout settings

Perf regression on service side, doing a few things to test out improvements while they resolve their side. For now, nothing to review here

/azp run js - keyvault-secrets - tests

Successful run https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1034750&view=results for certs and https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1034510&view=results for secrets


use dark sky sunset/sunrise times

they're more accurate and we already have them.  remove gmt_offset from code and refactor corresponding functions

fixed in  	1ff3beb


Condition monitoring - Initial additions to align with the format

Tasks performed to align the conditional monitoring project with the format of other projects

[x] Added requirements.txt
[x] Added the library item for the condition monitoring project in the readme file at root directory
[x] Removed the outputs from the python notebook
[x] Started with modularizing the code of the python notebook

This is a pull request for the issue #59

Performed EDA using data-describe package with sample matlab files.
Added sample visualizations to the notebook.
Modularized the code for easier understanding and reusability.

For the issue #59

Cleaned EDA notebook
Started with consolidating all the bearing damage related information with Signals for further analysis.

For the issue #59


support pytest > 4

What was wrong?
Running tests under pytest>4 was failing because get_marker was removed as seen here
How was it fixed?
replaced get_marker with get_closest_marker and updated requirements.
Cute Animal Picture
nah ah.

put a cute animal picture here.

No cute animal pictures? :cactus:


ComponentArrays introduces ambiguity for Base.dropdims

ComponentArrays v0.13.8, Julia 1.8.5
julia> dropdims([1;;], dims=(1,2))
0-dimensional Array{Int64, 0}:
1

julia> using ComponentArrays

julia> dropdims([1;;], dims=(1,2))
ERROR: MethodError: reshape(::Matrix{Int64}, ::Tuple{}) is ambiguous. Candidates:
  reshape(A::AbstractArray, axs::Tuple{Vararg{var"#s15", N}} where var"#s15"<:ComponentArrays.CombinedAxis) where N in ComponentArrays at /global/u1/m/marius/.julia/packages/ComponentArrays/NM9IH/src/array_interface.jl:13
  reshape(a::Array{T, M}, dims::Tuple{Vararg{Int64, N}}) where {T, N, M} in Base at reshapedarray.jl:40
  reshape(parent::AbstractArray, dims::Tuple{Vararg{Int64, N}} where N) in Base at reshapedarray.jl:112
  reshape(parent::AbstractArray, dims::Tuple{Vararg{Union{Colon, Int64}}}) in Base at reshapedarray.jl:119
Possible fix, define
  reshape(::Array{T, M}, ::Tuple{}) where {T, M}

Oh, yeah it looks like we need to put a single argument of CombinedAxis before the Vararg to avoid type piracy here.

Maybe this breaks some other thing I'm not aware of since I'm not familiar with the CA code but maybe another (better?) solution is first arg should be ::ComponentArray? Looking at e.g. Base and CUDA their defintions both have a ::NTuple{N,Int} second arg but a concrete first arg?

Now that I'm looking back at this, this reshape method was introduced because the reshape method of OffsetArrays commits some type piracy and broke some things, I think. I'm going to just undo that completely and point people toward OffsetArrays when things break.

It looks like whatever was broken before isn't broken now, so... 🤷🏼


Remove hardcoding of "master" branch

This should work even if the "master" branch is called "main" or if the PR isn't against the main branch.
Relevant:
GitHub Contexts

Should be done now!


Build lua modules mnist and ann with lua 5.4

hi ,how to do this step?i'm fish here

Windows/Mingw :

Use pacman to Install gcc and gnu make
Download lua 5.4.4 source code from https://www.lua.org/, and build it.
make

tks,bro

mac envrironment , how to do this step success , it seems can not find lua54 lib

https://web.tecgraf.puc-rio.br/~lhf/ftp/lua/install.html


Add exception on console

Closes https://github.com/pydantic/logfire/issues/150

Needs a followup to log exceptions in spans.


Fixed AwsS3->exists when file doesn't exist

Fixes https://github.com/Slynova-Org/node-flydrive/issues/9

Coverage remained the same at 52.101% when pulling 62428481b8f5619d0d6d94e76dd13f02fea34fc2 on pravindahal:develop into 56a01ba854c9050cefa93036c5060bd69bd93369 on Slynova-Org:develop.

Thanks !


[DOC] Add documentation for missing Data Prepper plugins

What do you want to do?

[ ] Request a change to existing documentation
[X] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
The DP processor docs are missing documentation for the following plugins:

Mutate events
Mutate strings
OTel metrics string
OTel trace group processor
Parse JSON
Trace peer forwarder

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
For the full plugin reference and documentation, see https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins

Thanks for entering this, Liz. What is the delivery date for your content?

Hey, please take a look at the readme files of above plugins for reference

Mutate event processor https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/mutate-event-processors#readme
Mutate string processor https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/mutate-string-processors/README.md
OTel trace group processor https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/otel-trace-group-processor#readme
Parse JSON processor https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/parse-json-processor/README.md
OTel metrics string processor -https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/otel-metrics-raw-processor/README.md
Trace peer forwarder processor https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/trace-peer-forwarder-processor/README.md

Hi Caroline @carolxob - Will you be able to take this over? The deadline is Feb 22.

Hi Caroline @carolxob - Will you be able to take this over? They've moved the release date to March 14, so the new deadline is March 8.

Sure, I'm on it.

This is complete. https://opensearch.org/docs/latest/data-prepper/pipelines/configuration/processors/processors/


[BACKLOG-39651] Update and validate in-product links in Pentaho 10.1

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 1h 14m 34s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
assemblies/static,engine,plugins,plugins/avro-format/core,plugins/connections/ui,plugins/core/ui,plugins/excel/core,plugins/file-open-save-new/core,plugins/json/core,plugins/meta-inject/impl,plugins/mondrianinput/impl,plugins/mondrianinput/ui,plugins/pentaho-reporting/impl,plugins/pentaho-reporting/ui,plugins/repositories/core,plugins/rest/core,plugins/s3csvinput/core,plugins/salesforce/core,plugins/streaming/impls/jms,plugins/streaming/impls/mqtt,plugins/xml/core,ui

:ok_hand: All tests passed!
Tests run: 5330, Failures: 0, Skipped: 14    Test Results

:information_source:  This is an automatic message


support try/catch blocks

Matlabs try/catch blocks are not recognized and the corresponding "end" confuses all other block statement parsing.
This breaks a lot of the plugins tools in my code.

Thank you for reporting, I’ll fix it in next version

Fixed by cfaa6731e20dfa1c62ae1735f0225636b6f1c8a3


feat: new actions to fetch the models after upload.

We need it because with the other actions, after set the models, we are doing more actions, and we dont need it if it is just to update the models.

and we dont need it if it is just to update the models.

If we don't need it, then we shouldn't do that in the existing FetchModels action. The job of that action is to fetch the models. You are referring to SetSpecies, so we should find out why it's necessary to call SetSpecies and do that in a better way.
The upload feature is a good example of a place where we should be able to dispatch the existing action of fetching models and not need to create a different one.


Make application loading backwards compatable

Need to  make application be able to use old settings ,  collections, images file on load and convert to new file layout when resaved at application closing or other save times

this will load files from version <IP_ADDRESS>

Subtask of #190


Unpin frontend_server_client and roll packages

(triage): Closing this one because we believe this already landed in a different PR.


broken since 5.2.0

I was using v5.1.2, it works well on my project before.
but it's broken since 5.2+ which includes v5.2.1. No route matches is it.

+1

I can no longer set this.someobject and access if from the next middleware.

Please show me a test that demonstrates this behavior. The test for properties on this context is passing: https://github.com/alexmingoia/koa-router/blob/master/test/lib/router.js#L294-L320

It broke for me as well, I'm getting the error below. Rolling back to 5.1.2 and everything works as usual.
/var/app/current/node_modules/koa-router/lib/router.js:513
      var routeNestingLevel = route.path.split('/').length;
                                         ^
TypeError: undefined is not a function
    at Router.register (/var/app/current/node_modules/koa-router/lib/router.js:513:42)
    at Router.(anonymous function) [as options] (/var/app/current/node_modules/koa-router/lib/router.js:182:10)
    at Object.<anonymous> (/var/app/current/routes.js:39:4)
    at Module._compile (module.js:460:26)
    at normalLoader (/var/app/current/node_modules/babel/node_modules/babel-core/lib/api/register/node.js:199:5)
    at Object.require.extensions.(anonymous function) [as .js] (/var/app/current/node_modules/babel/node_modules/babel-core/lib/api/register/node.js:216:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/var/app/current/server.js:6:37)
    at Module._compile (module.js:460:26)
    at normalLoader (/var/app/current/node_modules/babel/node_modules/babel-core/lib/api/register/node.js:199:5)
    at Object.require.extensions.(anonymous function) [as .js] (/var/app/current/node_modules/babel/node_modules/babel-core/lib/api/register/node.js:216:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/var/app/current/index.js:4:11)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)

I'm also getting what looks like a related issue:
  TypeError: m.path.split is not a function
      at /.../node_modules/koa-router/lib/router.js:516:36
      at Array.some (native)
      at Router.register (/.../node_modules/koa-router/lib/router.js:515:21)
      at Router.(anonymous function) [as get] (/.../node_modules/koa-router/lib/router.js:182:10)
      at Object.<anonymous> (/.../apps/www/routes-www.js:31:8)
      at Module._compile (module.js:434:26)
      at Object.Module._extensions..js (module.js:452:10)
      at Module.load (module.js:355:32)
      at Function.Module._load (module.js:310:12)
      at Module.require (module.js:365:17)

I'm afraid I don't have time to isolate a test case for you right now, but I identified the error was introduced between 5.2.1 and 5.2.2, if that helps. I am reverting to 5.2.1 for now.

#188 fixes this.

#152 adds tests and fix for the specific Regexp issue.

I believe #188 doesn't completely fix this issue: see my comment on DimensionSoftware/koa-router@b740a3d.

+1 on #152.

Ping. Using regular expressions with koa-router is broken without this fix; #152 looks good at first sight.

Eager for this fix too.

This is fixed in 6.x. Koa is moving to a different API with 2.x. koa-router 6 has been released which requires koa 2.

Koa v2 is still in alpha, and if I understand well, when it is released will require either a clumsier syntax or Babel transpiling for async/await, neither of which I want.
If v6+ requires Koa v2, could this fix be backported into v5?

@chrisveness #152 was merged into 5.3.0 so it should be fixed for you on 5.x as well.

All is sweet with 5.3.0, thanks.


Set master download__urls to release

I'm not sure if there was a need that the download_calico_url and download_calico_ipam_url were updated. This sets them to the last release so that hopefully the Semaphore tests pass.
Release Note
None required

@caseydavenport switched those to the non-existent tags back in https://github.com/projectcalico/calico/commit/09a56ed63018eecad0f98b116ae22c96ca7d6d6a. The change to v1.11.0 looks correct, but let's confirm w/Casey