Allow for graceful termination of the program started by sbt run

Enabling  cancelable in Global := true allows to press Ctrl+C and terminate the running program without terminating SBT, however the way how it is handled is quite surprising and doesn't really do what is typically expected from Ctrl+C.
Ctrl+C sends the TERM signal to the application, not KILL. Unfortunately SBT behaves as if it was requested a KILL and interrupts the application. In forked mode, it also seems to kill the JVM very quickly after the application receives the TERM signal. This gives no way for the application to terminate gracefully as it would do when running without SBT supervision.
Hitting Ctrl+C inside of sbt run should pass the TERM signal to the running application and just let the application decide how it handles it. Most of applications know what to do. Maybe, if some users still insist on hard terminating of the process (if it was frozen or doesn't respond to normal TERM), the second Ctrl+C would invoke the current behaviour and interrupt / kill the application.

Hi,
the one thing why this feature is very hard implement properly is that process signals are platform dependant. That is you are talking about a POSIX signals which are available in Linux, but not in Windows.
There're some solutions out there to solve this on windows, but this will introduce windows-dependent code into sbt codebase. (IMHO preferable way is to link against a native dll that will call windows API to achieve this). Maybe a sbt plugin will be a more acceptable solution.
Also I think that problem is not correctly formulated, I tested cancelable in Global := true on linux, using Runtime.getRuntime().addShutdownHook. When I press Ctrl+C my shutdown hook executes properly, as expected, same as with kill -15 $pid.  Also it looks like it is the 'official' way to implement signal handling in java.
But this is not the case on Windows, on windows when you press Ctrl+C the program will most probably terminate without calling the shutdown hook, so it looks like this is Windows-only problem.
P.S. - probably we can easily achieve the same effect with taskkill on windows.

I definitely would love to see this capability.
It looks like there was at least one previous issue (#228) opened (and closed) for this type of feature.

+1

+1

+1

+1

I sometimes use sbt to quickly test some cluster based code. I start the app using sbt, the app joins a development cluster, I hit ctrl-c... and bam, the whole cluster is in an inconsistent state, because my program under development didn't have time to say goodbye first.

+1, very inconvenient to grab ports inside sbt because of this thing

This can't really be done in a platform independent way for the forked jvm. For in process run we can interrupt the main thread and the application will have an opportunity to recover and clean up after itself.

I just put fork in Global := true to my build.sbt and now it works as expected. I can Ctrl+C my running process and it lets my code handle it. I also have cancelable in Global := true


Error when having more than 4 textures

When I add more than 4 textures I get this error and the map becomes invisible, I also found that a new empty Splatmap is created and added to the splatmaps array and when I delete it the main map appears again and everything works fine, so how to add more textures without facing this problem again ?

Hey @EmineBS !
In your fifth textureset, make sure you provide the same kind of textures you do for the others.
Meaning that you need to provide at least the albedo. If in the others you provided a normal map, you need to provide one as well. If you provided a roughness texture, you need to provide one as well for the new one. And so on.
Can you confirm me everything as been set this way? 🙂

Yes I placed all the textures correctly, even when I try to assign the same texture from textureSet 4 to textureSet 5, the error appears again and a new empty Splatmap is added and I can't delete it only when I delete textureSet 5.

Alright, would you be able to share the project with me? I could check what is happening 🙂

Any news on that @EmineBS ?

Check the settings on all of them. Godot is weird.

Solved! Yes, all imported textures must be on the same import settings, even if there is any small thing different from others, this error will appear

Alright thanks @EmineBS for the info about the defaults 🙂


test prow CICD

Signed-off-by: Mike Ng<EMAIL_ADDRESS>/hold
wait for
https://github.com/openshift/release/pull/24568
https://github.com/open-cluster-management-io/multicloud-operators-channel/pull/22
https://github.com/open-cluster-management/multicloud-operators-channel/pull/193
https://github.com/open-cluster-management/multicloud-operators-channel/pull/194

to merge first.

/lgtm

/unhold


Could arrays be specified as buffers as field metadata?

Hello! I have some arrays in my project that should always be marked as buffers (as in jax.lax.stop_gradients). I think the way that equinox ties metadata to dataclass.field is pretty elegant (as in converter and static). Would it be possible to add a “buffer” option in field, that always makes sure jax.lax.stop_gradients is called? I think this would be really nice.

It should be possible to get equivalent behaviour using the existing feature set. Here are two ways that aren't too magic:
Option 1: wrap the array into a Buffer class
class Buffer(eqx.Module):
    _array: Array

    def get(self):
        return lax.stop_gradient(self._array)

class FooModule(eqx.Module):
    some_buffer: Buffer

    def __init__(self):
        self.some_buffer = Buffer(some_array)

    def ___call__(self, x):
        return x * self.some_buffer.get()

This is probably simplest!
Option 2: override __getattribute__
Class MjoModule(eqx.Module):
def getattribute(self, item):
value = super().getattribute(item)
for field in dataclasses.fields(value):
if field.name == item:
if "buffer" in field.metadata:
value = lax.stop_gradient(value)
break
return value
class FooModule(MjoModule):
buffer: Array = eqx.field(metadata={"buffer": True})
    def __call__(self, x):
        return x * self.buffer

This gives you the behaviour you asked for.

---

I can see that you're asking for this as a feature request for Equinox itself. So far I've resisted adding this in, mostly to (a) avoid adding "silently magic" behaviour to `eqx.Module`, and (b) to avoid privileging `jax.grad` over any other JAX transform.

That said, those aren't strong feelings. I can definitely see the value in adding this to Equinox itself.

Great! Thanks so much. Overwriting __getattribute__ is a good option for me. As for the feature request, whatever you think is best. This makes sense.

Would like to reopen this… at least for me, this feature would be really nice. I don’t want my Modules to diverge from equinox, so if this is of general interest that would be awesome!

I definitely see the value in adding this as a feature.
One question I do have is why you think it's better to have
class Foo(eqx.Module):
    x: Array = eqx.field(buffer=True)

This is the true, in this case I agree with this. The issue I’m running into is that I want to access self.bar many times. I currently have a Module that stores coordinate system buffers, and this Module is then a field of some OtherModule. This OtherModule may access the buffers multiple times, and it is an abstract base class and may also do so in different ways depending on the subclass of OtherModule. Users of the repo have the ability to create a subclass, and I don’t want them to have to worry about these details.
My current solution is to offload buffers to particular Modules and create a base class where all fields have stop_gradient run in __getattr__. This isn’t so bad. But it would be nice to have more flexibility than this.

Can you give a quick MWE drafting what you're describing, with Module and OtherModule?

Sure. This roughly outlines my current situation and solution:

class BufferModule(eqx.Module):

   b1: Array
   b2: Array

    def __getattr__(self, name):
        value = getattr(self, name)
        if isinstance(value, Array):
            return jax.lax.stop_gradients(value)
        else:
            return value

class AbstractModule(eqx.Module):

    buffers: BufferModule

    @abstractmethod
    def __call__(self, arr):
        # Do something with b1 and b2

class AnotherModule(eqx.Module):

    module: AbstractModule  # subclass of AbstractModule
    arr: Array

    def __call__(self, another_arr):
        result = module(self.arr)
        # Do something else with b1 and b2
        # and another_arr

Here, AbstractModule is something that either the user or developers with little equinox / jax experience may subclass. AnotherModule takes a subclass as AbstractModule as an argument, and also may access the buffers.
The reason I would like the field metadata is that in general, I don’t want to have to move all of the buffers to a single class. In general, AbstractModule could have a buffer in it accessed by AnotherModule, or BufferModule could have non-buffers.

Okay! In this case I'd probably suggest the following pattern:
class Foo(eqx.Module):
     _array: Array

    @property
    def array(self):
        return jax.lax.stop_gradient(array)

    def __call__(self, x):
        # do something with `self.array`

which I think should be un-footgun-able by new users, whilst also explicitly declaring the stop_gradient.
(I'm not really against the idea of field(buffer=True), but I'm not a huge fan of how it secretly sneaks in special behaviour, which I think Equinox otherwise does a fairly good job of avoiding. So I am trying to see if there's a better way to accomplish any particular goal.)

Okay, this makes sense to me. I like this. It’s taken a bit to get used to the idea of wrapping arrays like this.


The discord link in README cannot be accessed.

It should be a server-inviting link, not a channel address.

Thanks for your report! I think the right link is https://discord.gg/EeF3cQw
Do you mind to help update it? Thanks!

I'm willing to update this! I'll send a PR now.


Rustc/cargo error format broken

The new nightly format is different from the previous format, hence the cargo maker does not work anymore

Can you provide a PR, or at least more information about the before/after?

@blueyed https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-come.html I can't find the pull request that added this format, but will look for it

Heh, I've meant a PR to fix it.. :)

Well I can try to fix it myself, but I'm not familiar with the neomake errorformat, where can I find docs on that?

@SethDusek
It is Vim's own errorformat, see :h errorformat.  It is not easy to grasp though.
Check out if there is anything better / fixed in Syntastic, too.


No option to obtain context of your main application using X6 Vue Shape

Describe the feature you'd like to request
There is this option in React, but there is no support to obtain context of the main application in Vue. Couldn't find anything in the documentation too
Describe the solution you'd like
Provide an option which will add it as a context value, while registering the Vue shape
Describe alternatives you've considered
Provide an option which will add it as a context value, while registering the Vue shape
Your Example Website or App
No response
Screenshots or Videos
No response

Which version do you use？

Can you share a sandbox demo of this working? It'll be really helpful to get along

You can refer to this demo.

Thank you @NewByVector . This is awesome. I have created a small one to demonstrate i18n in x6-vue-shape.
Please have a look here


Performance Improvement on MSCOCO

@dbolya  how to improve the accuracy of detection for MSCOCO i.e increase the mAP value , since we have got improved performance

Umm, can you clarify?

i want to increase the mAP values for the person class and car class for MSCOCO dataset

Do you want to keep the same speed? Because if I knew of a way to increase performance while keeping speed the same, I'd have done it by now.
I guess you can add more data for those classes from other datasets, but that's not increasing mAP on MSCOCO anymore.

sure i will try adding more classes and observe the results on this whether it will improve or not

@dbolya  thanks for the wonderful explanation , i wanted to get into further details . The detection of person from the model for a score threshold of 0.25 has less detection but if i decrease the detection to 0.12 i get more detection along with false positive . how understand from the protonet , mask coefficients how the person detection is varying based on the scenarios like ped walking on the cross walk or ped standing in the long distance #171

The score is just calculated like any other object detector. It's just predicted along with the mask coefficients for each class, and then we take the score for the highest class.
It's standard to get less false negatives and more false positives as you tune the threshold, which is the entire reason we use mAP and not some accuracy metric (mAP is score threshold agnostic). You just need to find a good threshold for your application, which may be between 0.12 and 0.25. I've been using 0.15 with good success when I've tested it.


Display issue

Hello, there is an issue with the display of the RUNE "RICKROLL•AKA•RICK•ASTLEY" video on ordinals.com, as well as an error with the SUPPLY display and ord.exe. How can we address these issues?
https://ordinals.com/rune/RICKROLL•AKA•RICK•ASTLEY
video :
https://github.com/ordinals/ord/assets/136961839/541e259e-d497-4a78-9cf3-c84373af4571

Hi dreamer, the best way to address issues like these is on one of the test chains before inscribing to mainnet.
Did you test this etch in regtest, signet or testnet? Did you see different results there?

Yes, I understand the need for testing, but honestly, before this, I didn't know how to properly use testnet. I wasn't even very proficient in HTML coding. So, I utilized a service called "Recursive Ordinals Builder" (https://www.recursivebuilder.io/) to test. The same code worked well for playing videos on this website. However, after inscribing it, I found that the video couldn't be played correctly. Immediately, I modified the code and confirmed its functionality using signet. Then, I inscribed the new HTML in a parent-child manner on the RUNE: "RICKROLL•AKA•RICK•ASTLEY".
The reason I'm seeking assistance is because during the launch time of this runes, I noticed slight changes in the layout of the ordinals.com website. The purpose of these changes is to provide users with a better experience when viewing data. So, I'm requesting help to ensure that users can correctly view the video and enjoy the original "RICKROLL" meme, aiming for a better user experience.
So I came here hoping to seek help. Thank you for patiently listening.

There are a few issues being presented here:

a display issue on the rune page - video only plays when the rune page is browsed to via the back button and not by default

The child inscription 70336141 of the parent 70290087 seems to work properly.  I don't understand why a parent was used instead of simply inscribing the child and using that as the image for the rune.  The child inscription is working well in my browser, where the parent inscription doesn't work well at all and requires the browsing with the back button (and that only seems to work in Chrome). There must be some difference in their encoding even though they have the same content types.

the supply on the rune page not matching the supply in the .yaml

this is talked a bit about in #3630.  The supply that shows on the rune page is somewhat misleading, as it reports the total available supply, meaning the total that has been created by premine and mint.  The supply in the yaml refers to the total max supply after all possible mints have been exhausted.  So your rune page shows 39323.1 🎤for the supply right now because that is how much that exists currently. 39320 premined, (the equivalent to 393,200 mints, + 3.1 (for the 31 mints).  After a total of 1,572,800 mints, it will mint out and then there would be a total of 196,600, because premine + (supply * amount) = 39,320 + (1,572,800*.1) = 39,320 + 157,280 = 196,600.

the rune amount field in the yaml matches the rune page, but not the batch command output from the terminal window

The amount set in the yaml is the defacto configuration that dictates how the rune will be etched.  The terminal output information is clearly different here, and I'm not exactly sure why.  I feel like it could be an issue/bug with the way the amount is displayed or by design due to some decision I'm not aware of.  In any case, you would always first want to go by what is in the yaml, because that is what is etched and appears on the rune page.

Thank you for your detailed response. Your insights into the issues presented are greatly appreciated. I'll take your guidance and work through each problem methodically to ensure they are addressed effectively. Your assistance is invaluable in resolving these matters.


Add github link to .js files

As an easy way to find and open the corresponding project repository
once you have the single .js files in your own codebase.

Good idea. Thanks.


Fix git reset command

Porting git reset fix from release branches to master
https://github.com/rancher/wrangler/pull/261

@cbron Can you merge this for me or add me as a maintainer?


Jeevithiesh d/patch obb support

I have implemented Patch OBB support for the Chimple app.

Incorrect target branch


Widget

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

![Uploading IMG_20200812_185035.jpg…]()

Hi @manu223,
The error indicates that you need to add a return statement to the widget.
Please see https://flutter.dev/community for resources and asking questions like this.
You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thanks.


Tokenization Count based on Model

Thank you for this library and your blog posts, really appreciate it for learning more about prompt programming GPT-3.
I assume if I want to count the number of tokens for a prompt, I would run:
const str = 'This is an example sentence to try encoding out on!'
const encoded = encode(str)
const tokenCount = encoded.length

I assume this is the tokenization algo used for the davinci models, is that correct?
Do you happen to know where to find a tokenization algo for the other models, or a general way to predict token usage before submitting a prompt ?
Thx for your feedback !

Sorry for not replying I don't seem to be getting notifications for this repo which I'll look into, but yep! That should work well for counting tokens before submitting a prompt.

@nickwalton
I've found this closed issue while looking for the same thing.
I need help understanding the provided answer, though.
Does it work with other models? If so, how?
I expect to have somewhere to specify which model I want to tokenise.
For instance, Python's tiktoken has tiktoken.encoding_for_model("gpt-4"), as well as a more generic tiktoken.get_encoding("cl100k_base").

+1
Would like to know how to encode for specific model, seems like the cureent algo is for r50k_base.
Shall we reopen this issue?


feat: support JSON keyword

https://cloud.google.com/bigquery/docs/reference/standard-sql/lexical#json_literals
support json keyword for json type in bigquery

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 10 (90.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 85.966%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser.rs
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
13213

Relevant Lines:
15370

💛  - Coveralls

I took the liberty of merging this branch with main to get CI passing


[close #343]fix cdc residue metrics

What problem does this PR solve?
Issue Number: close #343
Problem Description: TBD
What is changed and how does it work?
clean metrics againt
Code changes

Has exported function/method change
Has exported variable/fields change

Check List for Tests
This PR has been tested by at least one of the following methods:

Unit test
Integration test

Side effects

No side effects

Related changes

No related changes

To reviewers

Please follow these principles to check this pull requests:

Concentration. One pull request should only do one thing. No matter how small it is, the change does exactly one thing and gets it right. Don't mix other changes into it.
Tests. A pull request should be test covered, whether the tests are unit tests, integration tests, or end-to-end tests. Tests should be sufficient, correct and don't slow down the CI pipeline largely.
Functionality. The pull request should implement what the author intends to do and fit well in the existing code base, resolve a real problem for TiDB/TiKV users. To get the author's intention and the pull request design, you could follow the discussions in the corresponding GitHub issue or internal.tidb.io topic.
Style. Code in the pull request should follow common programming style. (For Go, we have style checkers in CI). However, sometimes the existing code is inconsistent with the style guide, you should maintain consistency with the existing code or file a new issue to fix the existing code style first.
Documentation. If a pull request changes how users build, test, interact with, or release code, you must check whether it also updates the related documentation such as READMEs and any generated reference docs. Similarly, if a pull request deletes or deprecates code, you must check whether or not the corresponding documentation should also be deleted.
Performance. If you find the pull request may affect performance, you could ask the author to provide a benchmark result.

(The above text mainly refers to TiDB Development Guide. It's also highly recommended to read about Writing code review comments)

/unit_test_in_verify_ci

/run-unit-test

/run-unit-test

/run-integration-test

/run-integration-test

/run-integration-test


msbuild new maintainers

Description
Adding to msbuild:

@mramonleon
@batmat
@rsandell
@alecharp
@bitwiseman
@carroll
@olamy
@jtnord

https://github.com/jenkinsci/msbuild-plugin
@gbois, @marshall777
Submitter checklist for adding or changing permissions

Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[x] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

is there a reason this is marked as draft?

is there a reason this is marked as draft?

It's fine now, ready.

@MRamonLeon you have access to add the rest of your team

I cannot admin the repo settings @timja. I think I just have write permission?

Should be fixed now

Sorry for the noise @timja, shall we use teams? Cleaner than permissions to every one. This team:
https://github.com/orgs/jenkinsci/teams/msbuild-plugin-developers/members
I can't manage the members.

Fixed


Add: 204-Error to permanentErrors-Array

When uploading there is a HTTP-404 logged to the console every checked chunk, so there is so much logging taking place it is hard to see real errors on the console.
Adding a HTTP-204 would give server-implementations a chance to return this statuscode for signaling the chunk is not available yet (204 - no content). The benefit would be you can find real errors on the console again.

+1 :+1:

There are a few other threads/issues on this issue -- and notwithstanding the virtues of such a scheme there are compelling reasons for the current setup. Having said that, it's an easy thing to configure when bootstrapping Resumable.


Source Control not working using Remote SSH

Issue Type: Bug
When connecting to another computer over SSH, the Source Control tab shows "No source control providers registered", even though the workspace folder I have open contains a Git repository.
This problem arose after updating to VS Code version 1.40.0, it worked fine in the previous version.

Ctrl+Shift+P > Remote-SSH: Connect to Host...
Select SSH host
Open Folder
Select a folder containing a Git repository
Open the Source Control tab (Ctrl+Shift+G)

When opening a local workspace (without Remote - SSH), source control seems to work fine.

The command Git: Show Git Output does not exist on the remote.
I opened a workspace on the remote, pressed Ctrl+Shift+P, and typed Git.

It's not in the dropdown menu in the Output panel either:

Can you check whether the built-in Git extension is enabled at all?

It doesn't seem to be enabled, but I don't know how to enable it. It worked before, though.

I suspect that if the git extension is available on the remote side. Can you please check if git works with local workspace?

Local
Local client  Remote SSH extension
SSH with X11 forwarding

git in terminal
✓
✓
✓

Git extension
✓
✗
✓

I don't know if it's related, but syntax highlighting for JSON files etc. doesn't work either using the Remote SSH extension.
Is there a way to reinstall the VSCode Server? Can I just delete the ~/.vscode-server folder?


Uncaught List did not contain any matching elements

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Mac OS X 10.10.5
Thrown From: ionide-fsharp package, v1.3.1
Stack Trace
Uncaught List did not contain any matching elements
At /Users/z/.atom/packages/ionide-fsharp/lib/fsharp.js:2442

undefined

Commands
  7x -1:20.6.0 core:select-down (atom-text-editor.editor.is-focused)
     -1:19.5.0 core:backspace (atom-text-editor.editor.is-focused)
     -1:19.2.0 core:save (atom-text-editor.editor.is-focused)
     -1:18.1.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -1:18.1.0 core:cancel (atom-text-editor.editor.is-focused)
     -0:56.2.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:56.2.0 snippets:expand (atom-text-editor.editor.is-focused)
     -0:56.2.0 editor:indent (atom-text-editor.editor.is-focused)
  2x -0:55.2.0 core:backspace (atom-text-editor.editor.is-focused)
  2x -0:52.5.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:47.3.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:47.3.0 snippets:expand (atom-text-editor.editor.is-focused)
     -0:47.3.0 editor:indent (atom-text-editor.editor.is-focused)
  7x -0:44.4.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:41.6.0 core:save (atom-text-editor.editor.is-focused)
     -0:04.7.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)

Config
{
  "core": {
    "projectHome": "/Users/z/projects",
    "audioBeep": false,
    "disabledPackages": [
      "markdown-preview"
    ],
    "themes": [
      "atom-dark-ui",
      "one-dark-syntax"
    ]
  },
  "ionide-fsharp": {
    "ShowUseHighlights": false
  }
}

Installed Packages
# User
.bin, vundefined
atom-typescript, v7.0.1
atom-yeoman, v0.3.14
autocomplete-haskell, v0.5.1
file-icons, v1.6.9
haskell-ghc-mod, v0.9.12
ide-haskell, v0.7.2
ionide-fake, v1.2.0
ionide-fsharp, v1.3.1
ionide-fsi, v1.0.7
ionide-installer, v1.2.1
ionide-paket, v2.1.0
ionide-yeoman, v1.0.1
language-cmake, v0.1.4
language-haskell, v1.4.9
language-lua, v0.9.4
language-rust, v0.4.5
linter, v1.6.0
markdown-preview-plus, v2.1.1

# Dev
No dev packages

[Enter steps to reproduce below:]

create an fsx file
write following code:

open System.Data.SqlClient
let bla() =
use connection = new SqlConnection (connectionString)
connection. <--- crash on intellisense here
Atom Version: 1.0.19
System: NUED-54438
Thrown From: ionide-fsharp package, v1.3.1
Stack Trace
Uncaught List did not contain any matching elements
At C:\Users\asvili\.atom\packages\ionide-fsharp\lib\fsharp.js:2442

undefined

Commands
     -1:16 core:cancel (atom-text-editor.editor.is-focused)
     -0:25.3.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:19.9.0 core:move-down (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:19.7.0 editor:move-to-first-character-of-line (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:19.6.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:19.6.0 snippets:expand (atom-text-editor.editor.is-focused)
     -0:19.6.0 editor:indent (atom-text-editor.editor.is-focused)
     -0:18.7.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:17.3.0 core:move-down (atom-text-editor.editor.is-focused)
     -0:16.8.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:16.8.0 snippets:expand (atom-text-editor.editor.is-focused)
     -0:16.8.0 editor:indent (atom-text-editor.editor.is-focused)
     -0:11.7.0 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
     -0:10.9.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:05.8.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
  2x -0:04.0 core:backspace (atom-text-editor.editor.is-focused.autocomplete-active)

Config
{
  "core": {}
}

Installed Packages
# User
atom-yeoman, v0.3.15
ionide-fake, v1.2.0
ionide-fsharp, v1.3.1
ionide-fsi, v1.0.7
ionide-installer, v1.3.0
ionide-paket, v2.1.0
ionide-webview, v1.0.0
ionide-yeoman, v1.0.1
linter, v1.8.1

# Dev
No dev packages

Should be fixed with 1.3.3


fix: corrected option used to create a docker file

The option to create a dockerfile in the documentation doesn't match what the cli help menu says.
using the option in the documentation i.e. --dockerfile results in an error
The help menu of the cli show the following for creating a docker file
--docker               Create a Dockerfile based on the selected worker runtime

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

#label:"aq-pr-triaged"

Great catch! Thanks for the fix @lamb003 👍 #sign-off


Fail fast if AWS_S3_BUCKET_NAME isn't set

I think we should prevent the Asset Manager app from starting if the AWS_S3_BUCKET_NAME environment variable is missing. We're committed to uploading assets to S3 and so I'd like to be alerted as early as possible if something is going to prevent that from happening.

I think this is dependent on PR #155.

I've replaced #159 with #167, because at this stage I think we only need to be concerned about ensuring the bucket name is set in the Rails production environment (which I believe includes the GOV.UK integration and staging stacks).
Until we make proxying to S3 the default, I don't think there's any need to be so strict in the development environment - I think it's fine to continue using the "null object" version of S3Storage so that uploading is a "no-op". And in any case we already have #155 to make us think about that.


Mixnet: messages handle model

Reference: https://github.com/logos-co/nomos-node/pull/386#discussion_r1324125862

We need to use mpsc channel so that we only have one thread that handles message forwarding or sending (a fan-in model).
When using this model, it means that some messages will be in the channel buffer. If a node crashes, then messages in the buffer will be lost. Do we care about this @youngjoon-lee @Zeegomo? If so, I think we need to introduce a write-ahead log, which will be used for recovering. When we have a message, first, write to this log, then send it to the buffer.

When using this model, it means that some messages will be in the channel buffer. If a node crashes, then messages in the buffer will be lost. Do we care about this @youngjoon-lee @Zeegomo? If so, I think we need to introduce a write-ahead log, which will be used for recovering. When we have a message, first, write to this log, then send it to the buffer.

I think in this case for mixnet node it do not matter if we lost the messages and node starts fresh new when restarted.
Other option is to use the Overwatch state to save it somewhere (local db for example), but I do not think we need to complicate things for now.

Networking is best effort, our best effort at the moment probably stops at the node crashing 😄
Btw, with the lock solution even if it's not in a buffer messages are still in volatile memory in the form of stack frames, so they would be lost anyway

Sorry for my late comment. I agree with Daniel and Giacomo. I think we don't need WAL at this moment.
Actually, even if we call tcp_stream.write(...), the data is buffered in the TCP buffer. That is, data could be lost if the node crashes before the TCP buffer is flushed.


Explicitly target Java 6 in compilation options

This patch modifies our build to explicitly target Java 6, which will guard against the publication of incompatible binaries (which could happen if the release publisher uses Java 8).

Current coverage is 95.05%

Merging #113 into master will not affect coverage as of 8f56530

@@            master    #113   diff @@
======================================
  Files           12      12
  Stmts          506     506
  Branches       122     122
  Methods          0       0
======================================
  Hit            481     481
  Partial          0       0
  Missed          25      25

Review entire Coverage Diff as of 8f56530

Powered by Codecov. Updated on successful CI builds.


Purging jobs missing?

I need to schedule some not repetitive tasks but for a certain date. I got a Mongo database instance at server and a sails application. However I will have a quite large demand in application (up to 100 000 users).
I wonder how this purging jobs as a problem to solve may complicate things in this application.

The problem is that you will have lot of old job in mongodb. We should find a way to clean that on sails shutdown. I did not have lot of time to investigate.


[MXNET-1026] [Perl] Sync with recent changes in Python's API

Description

Added randn function.
Internal SELU function on C++ layer
Predict now accepts ndarray as well
Gluon: Only warn when the blocks are unregistered.
Better sparse support for gluon
Gpu memory info via mxnet api call.
Gluon: Improved block summary.
Added validation docs for MXNet installation for Perl.
Flexible perl env for examples.
Gluon: Custom dtypes for the symbol block.
Separate eval metric for the epoch level.

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes
Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-label-bot [pr-awaiting-review]


[GIN-debug] redirecting request 307

i didn't found any answer for this issue .
I am trying to call simple API, but it redirecting request 307 . and the request fail on client side .
as you see in the first screen shot there is 3 requests . first one is option with Status Code:200 OK .
the next 2 requests with Status Code:307 Temporary Redirect
port 3030 is server
port 8100 is client
CORS middleware is gin-cors

and this is the code
// Creates a gin router with default middleware:
	router := gin.Default()
	// Apply the middleware to the router (works with groups too)
	router.Use(cors.Middleware(cors.Config{
		Origins:        "*",
		Methods:        "GET, PUT, POST, DELETE",
		RequestHeaders: "Origin, Authorization, Content-Type",
		ExposedHeaders: "",
		MaxAge: 300 * time.Second,
		Credentials: false,
		ValidateHeaders: false,
	}))

       router.POST("/api/v1/login", usersController.Login)

client side error
XMLHttpRequest cannot load http://localhost:3030/api/v1/login/. Redirect from
 'http://localhost:3030/api/v1/login/' to 'http://localhost:3030/api/v1/login' has been blocked by CORS
policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin
'http://localhost:8100' is therefore not allowed access.

it works fine on postman

I think you must have Credentials set to true.
If you look at the headers returned on your first response, it's setting the allowed origin to localhost:8100.
If you are using Origins: * and Credentials: false, then you shouldn't see it return the Access-Control-Allow-Origin: http://localhost:8100.
The related code is this:
if valid {
	if config.Credentials {
		context.Writer.Header().Set(AllowCredentialsKey, config.credentials)
		// Allowed origins cannot be the string "*" cannot be used for a resource that supports credentials.
		context.Writer.Header().Set(AllowOriginKey, currentOrigin)
	} else if forceOriginMatch {
		context.Writer.Header().Set(AllowOriginKey, "*")
	} else {
		context.Writer.Header().Set(AllowOriginKey, currentOrigin)
	}

	//If this is a preflight request, we are finished, quit.
	//Otherwise this is a normal request and operations should proceed at normal
	if preflight {
		context.AbortWithStatus(200)
	}
	return
}

i changed the  Origins to  http://localhost:8100  and Credentials to false .
but still i have the same issue

	router.Use(cors.Middleware(cors.Config{
		Origins:         "http://localhost:8100",
		Methods:         "GET, PUT, POST, DELETE",
		RequestHeaders:  "Origin, Authorization, Content-Type",
		ExposedHeaders:  "",
		MaxAge:          300 * time.Second,
		Credentials:     true,
		ValidateHeaders: false,
	}))

I think problem is client side, because it works fine with another client side app .
issue not related to gin-cors  .
Thanks

@itsjamie @tuvistavie
SOLVED
problem was with URL

...url/login  Passed
...url/login/  Failed because of extra /

Hi @almgwary ,
I know its ages past this issue. but what client were you using at that point of time?
I am facing the same issue with Angular 4 and not able to fix it. tried removing / and all other sort of things.
Thanks.


mergify: remove non-existent check from conditions list

Codecov Report

Merging #161 (fb48888) into main (b14f5c4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #161   +/-   ##
=======================================
  Coverage   85.23%   85.23%
=======================================
  Files          22       22
  Lines         210      210
  Branches       32       32
=======================================
  Hits          179      179
  Misses         31       31

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 b14f5c4...fb48888. Read the comment docs.


Look for alternatives to bintray

We are currently publishing the binaries in Bintray but it seems the service will be no longer available after 1st May.
Help or comments are greatly appreciated.

Maybe GitHub package registry fits our need.

We are publishing now at github packages as suggedted by @thewillyhuman


tests: linktype_name test

Issue: 6954
Ensure that the linktype_name is included in the alerts.
Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/6954

Closing for reevaluation

Continued in #1853


Fix an issue where the draggable image doesn't include the watermark …

…after dropping

I would like to thank @alexito4 for the amazing article: https://alejandromp.com/blog/swiftui-views-to-images/
It helped me fix this issue with little to no effort.
I had hoped apple would somehow allow us to access the generated preview image of the onDrag(_:) modifier to allow us to save it directly. I wasted long hours trying to get it with no luck.

@alobaili thanks a lot for this!


Bad eps file generated

I downloaded the latest version of export_fig, tried to generate a pdf and the intermediate eps file was bad so that ghostscript (and also Preview) choked on it.
The error message was
Error using eps2pdf (line 107)
Error: /undefined in bdef
Operand stack:
dom   --nostringval--
Execution stack:
%interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
--nostringval--   --nostringval--   false   1   %stopped_push
1951   1   3   %oparray_pop   1950   1   3   %oparray_pop   1934
1   3   %oparray_pop   1820   1   3   %oparray_pop
--nostringval--   %errorexec_pop   .runexec2   --nostringval--
--nostringval--   --nostringval--   2   %stopped_push
--nostringval--
Dictionary stack:
--dict:1194/1684(ro)(G)--   --dict:0/20(G)--   --dict:78/200(L)--
Current allocation mode is local
Last OS error: Invalid argument
Current file position is 64
GPL Ghostscript 9.16: Unrecoverable error, exit code 1
Error in export_fig (line 433)
eps2pdf(tmp_nam, pdf_nam, 1, options.append,
options.colourspace==2, options.quality);
GitHub won't let me upload the fig file but I generated the fig by
plot(1:10,sin(1:10))
Thanks
David

I'm not sure you're using the latest version of export_fig: line 107 of eps2pdf.m is simply a catch directive, not the ghostscript command (which is several lines beneath it). Therefore I believe that you are using some old version of the code. Run which eps2pdf -all in your Matlab to check whether you have multiple versions in your Matlab path.
I'm closing this issue now. If you still see it with the latest version of export_fig then you can reopen it with the updated message.


ecosystem_path_id should be a slot on Biosample class

The ecosystem_path_id slot: https://microbiomedata.github.io/nmdc-schema/ecosystem_path_id/ should be asserted on the Biosample class.
LinkML definition: https://github.com/microbiomedata/nmdc-schema/blob/main/src/schema/nmdc.yaml#L1974-L1976
Consider an example biosample record from the GOLD database: https://gold.jgi.doe.gov/biosample?id=Gb0356235
Under the ecosystem classification section you will see various properties displayed:

GOLD Ecosystem property
NMDC Schema slot

Ecosystem
ecosystem

Ecosystem Category
ecosystem_category

Ecosystem Type
ecosystem_type

Ecosystem Subtype
ecosystem_subtype

Specific Ecosystem
specific_ecosystem

Ecosystem Path Id
ecosystem_path_id

From the above table all slots except for ecosystem_path_id have been asserted on Biosample class.

Note to self: check with @pkalita-lbl whether his GOLD ecosystem constraints work on the submission portal.


feat: move create-electron-app into forge

This PR moves create-electron-app into Forge's monorepo:

[x] Makes create-electron-app TS compatible
[x] Changes the version to match the other monorepo packages
[x] electron-userland should have create-electron-app NPM publish permissions

I'm fairly certain this is a bug in Bolt's Windows symlinking, and this method specifically is where I think we're experiencing the problem: https://github.com/boltpkg/bolt/blob/a922d937c8054dea4c4e1d4f8755583187cdd9ed/src/utils/fs.js#L59
The new package works as expected on Mac and Linux; it's only failing on Windows, but it's failing both in CI and when I run bolt locally after running git clean -dfx. Bolt tries to reconcile Windows symlinks differently than Posix (see here ), and one of the ways it attempts to do that is by falling back to the file in src if the filepath or symlink does not exist ( see here ).  In our case, create-electron-app is looking for cli/dist/electron-forge.js - that file won't exist until the typescript compiler is run.
Not 100% sure how to get around this yet, but I think this is the only blocker for this PR.

Don't merge, please, want to clean this up a bit now that it's working

I think the mkdirp and touch deps can be removed now too


Cmd+click of JSX component shows type definition in VSCode, instead of linking to component definition

As requested by @RyanCavanaugh on issue #24809 - reopening the issue with an updated concrete way to reproduce.
Tested with latest VSCode 1.43, latest typescript 3.8.3.
Simply create a .tsx file in VSCode with the following content:
import React from 'react'

const Thing: React.FC<{ text: string }> = (props) =>
{props.text}

const HelloWorld = () => <Thing text="hello world" />

And cmd+click on <Thing on line 5
Expected behavior:
Cursor moves to definition of const Thing on line 3.
Actual behavior:

VSCode opens a definitions window with links to 2 definitions:

The component definition on line 3 (that I expected to be linked to)
The definition for the type of the component: React.FC, in node_modules/@types/react.

This seems like a bug. In practice it means navigating is broken for JSX components, as cmd+clicking to link doesn't work - you have to cmd+click then click on the code definition again in the definitions window.
I am pretty sure that in the vast, vast majority of cases, when people cmd+click on the JSX for a component, they want to link to the component's definition and not the type.
Even supposing people did want to do that, in some cases:

Just seeing what the type is would be solved in one click, because it is there in the definition
Navigating to that type definition if you really wanted to would remain at 2 clicks - by just cmd+clicking it right there in the definition.

So, there seems no downside here. Improve (fix) the most common usecase, less common (if ever) usecase still works, still 2 clicks.

I just want to bump this thread and say that I am also feeling this pain.
My click throughs are broken..
@davnicwil until this is fixed, you might appreciate that it is possible to hit enter after first click to go to file.
Not a great workaround but its something 😄

@nk1tz great shout - I'm probably doing this 100s of times a day so removing the friction even a little is really helpful. Cheers!

Can you clarify the workaround? I can't figure out how to get to the source file. I command+hover, it brings up some definitions, but I can't get anywhere from there (command clicking does nothing)

@JulianKingman cmd+click on the component itself in the code (i.e. <Thing), it brings up the definitions (like in the screenshot), then pressing the enter key navigates to the top one which is the actual component definition. Just saves you that second click in the definitions popup.

I'm experiencing this a few hundred times a day as well, It's a really frustrating experience.

Just wanted to bump the thread to say I am also experiencing this friction a lot; it's also frustrating that the first suggestion on the list is the result from node_modules/@types/react and not the actual line where const Thing = is defined.
A non-ideal workaround is to re-write it so that the function argument has the type definition:
const Thing = (props: React.PropsWithChildren<{ text: string }>) => (

{props.text}

);

const HelloWorld = () => <Thing text="hello world" />;

This avoids the problem where the definition lookup of <Thing> suggests the unwanted type from node_modules/@types/react. However, this workaround is a less specific type definition because the return value of the function doesn't have a type declared which isn't great.

Dealing with this all day long in a React TypeScript project. All components are typed React.FC and exported as default.
One fix that's helped is changing Editor > Goto Location: Multiple Definitions from peek to goto in settings.
Obviously, this will end up concealing some secondary definitions that might actually be useful to know about but in the meantime it makes command-clicking components behave as I would expect it to.

I would love for this to be resolved as well. Thanks @sambecker for the tip! That definitely helps as a workaround.

Hello guys, I made a simple vscode extension to resolve this problem. vscode-tsx-arrow-definition, and you can search vscode extension marketplace to find it.
This extension's function is simple:

If there're more than one defintions, and one definition is @types/react/index.d.ts, just remove it from the definition list.
If there's only one definition or no definition is @types/react/index.d.ts, just use the original result.

Hope this helps.

I've not had a problem with this because I've used "Goto" as mentioned above by @sambecker. Suddenly today my "Goto" is defaulting to the @types/react/index.d.ts instead of the actual component, and it is driving me nuts.
Any solutions?
I'm not sure if something changed in VSCode or my project.
What determines the order of the definitions and can we reprioritize them? (i.e. a setting such that anything in node_modules should not be the first/default definition)

@mliq I have also been using the "Goto" setting mentioned above and it was working perfectly until a few days ago. Suddenly the order seems to have changed and it is now preferring the node_modules definitions. I think something in VSCode must have changed.
Thanks @Miaonster for your extension, I tried it and it works well to filter out React specific types, however I also experience the problem with other type definitions which are in node_modules from other libraries. If your extension could be modified to either (1) filter out any match within node_modules, or (2) re-order the matches so that node_modules is at the bottom of the list, then it would be helpful to filter out definitions from libraries other than React.

I've not had a problem with this because I've used "Goto" as mentioned above by @sambecker. Suddenly today my "Goto" is defaulting to the @types/react/index.d.ts instead of the actual component, and it is driving me nuts.
Any solutions?
I'm not sure if something changed in VSCode or my project.
What determines the order of the definitions and can we reprioritize them?
A setting to state that anything in node_modules or *.d.ts should not be the first/default definition if multiple exist would be one way to solve this.

That just recently stopped working for me as well. I think the latest version of vs code must have changed the order. I installed  the vscode-tsx-arrow-definition extion that @Miaonster mentioned above and it seems to be working well for me.

@bcole808 I can add a setting that will allow user ignore all node_modules or user-specified types if there are multi definitions.

@bcole808 A new version was released, you can upgrade and check the doc of forceRemove and remove configurations. If there's any problem, please leave an issue.

I've not had a problem with this because I've used "Goto" as mentioned above by @sambecker. Suddenly today my "Goto" is defaulting to the @types/react/index.d.ts instead of the actual component, and it is driving me nuts.
Any solutions?
I'm not sure if something changed in VSCode or my project.
What determines the order of the definitions and can we reprioritize them?
A setting to state that anything in node_modules or *.d.ts should not be the first/default definition if multiple exist would be one way to solve this.

same for me. it would be great if we can fix this/add a setting in vscode!

Same here. cmd+click suddenly started to throw me to the<EMAIL_ADDRESS>for any component with React.memo.
Please, fix this, it's an essential feature in vscode.

Same here. cmd+click suddenly started to throw me to the<EMAIL_ADDRESS>for any component with React.memo.
Please, fix this, it's an essential feature in vscode.

There's a plugin that fixes that problem. No need to post countless "same here" comments.

Same here. cmd+click suddenly started to throw me to the<EMAIL_ADDRESS>for any component with React.memo.
Please, fix this, it's an essential feature in vscode.

There's a plugin that fixes that problem. No need to post countless "same here" comments.

Sorry but this shouldn't be handled by a plugin. It is a great that Miaonster created it for the time being, but this needs a permanent out of the box solution. Maybe the dicussion should be moved/started in the vsc repo.

Sorry but this shouldn't be handled by a plugin. It is great that Miaonster created it for the time being, but this needs a permanent out of the box solution. Maybe the dicussion should be moved/started in the vsc repo.

You don't get my point. All those "same here" comments aren't adding anything valuable to the problem discussion.
All participants gets notifications and are distracted from they work for no good reason.
The problem itself is super annoying and god bless that person who created plugin that fixes problem It's not a proper solution and should be fixed in vscode.
But until —  just press 'subscribe' button in this issue and use plugin (if that problem hurts you bad enough)

You don't get my point. All those "same here" comments aren't adding anything valuable to the problem discussion.
All participants gets notifications and are distracted from they work for no good reason.

Sorry, but you didn't get my point first of all. I've added new information for this bug, that it's also reproducing with React.memo. I think, it's a good reason to write a comment.
And only a subscription is an incomprehensible signal about the urgency of the problem. You need to at least "like" the original post.

I've not had a problem with this because I've used "Goto" as mentioned above by @sambecker. Suddenly today my "Goto" is defaulting to the @types/react/index.d.ts instead of the actual component, and it is driving me nuts.
Any solutions?
I'm not sure if something changed in VSCode or my project.
What determines the order of the definitions and can we reprioritize them?
A setting to state that anything in node_modules or *.d.ts should not be the first/default definition if multiple exist would be one way to solve this.

+1 . I remember I change the config to Goto in the past. And recently it suddenly not work.

I am in the process of converting to VS Code from IntelliJ IDEA and there's a lot of great things in VS Code, but not being able to consistently cmd + click to navigate to definition is driving me nuts.
In a project with TypeScript 5 and React 18, I had to use the plugin mentioned above (https://github.com/Miaonster/vscode-definition-filter), but with custom settings:
// settings.json
    "tsxDefinitionFilter.remove": [
<EMAIL_ADDRESS>    ]

This problem is back for me.

Started happening to me as well, worked flawlessly until the last update.

Same here. Just started taking me to the @types/react node module definitions instead of the actual reference file.

Same here


Added code review guide URL

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @sparklycat for your contribution and congratulations on your first PR merge to this repo! 🎉
Hope to see more contributions from you in the future.


Document support for normal and specular maps in AnimatedSprite2D

This closes #38509.
I duplicated the note in both AnimatedSprite2D and SpriteFrames, but I'm not sure if we actually need to do this. It might be worth keeping this only in AnimatedSprite2D.
Note: When cherry-picking this PR to the 3.2 branch, make sure to remove the reference to specular maps as only the master branch supports those.

Thanks!

Cherry-picked for 3.2.3.


fix: add encode URL to Plausible button

dweb.link/ipns/k51qzi5uqu5dikgvh3al7o5pxsme6j0aw5s2d1qjwcfqi0t5pids772qhq8ohj
Maybe is my mistake. 😅

dweb.link/ipns/k51qzi5uqu5dikgvh3al7o5pxsme6j0aw5s2d1qjwcfqi0t5pids772qhq8ohj

Cool!
In that case, if you want to use Plausible for your site, you can just use its IPNS string as Plausible domain like this:

Plausible's domain field works like an ID or tag. It accepts a simple string value like example.com or k51qzi5uqu5dikgvh3al7o5pxsme6j0aw5s2d1qjwcfqi0t5pids772qhq8ohj, not the whole URL.

So the domain value you entered will be part of the URL like this:
https://plausible.io/olivida.eth.limo
In the example above, the domain value is olivida.eth.limo for https://olivida.eth.limo , but actually, if you use just olivida.eth, it would work too. It works like an ID or tag.

I checked Plausible's docs, and they have an example that included / for adding a subfolder.
https://plausible.io/docs/add-website
So I have merged your change. Thanks a lot!

I merged and tested. It is working with / now.
Thanks again!


Pbkdf2 support

Adding a flag that will allow keys to be generated using pbkdf2 derivation function instead of scrypt. This is a substantially faster alternative and good option for users if they were going to generate keys in bulk.
We will still default to scrypt but if the flag is specified, it will drill down to the key generation where either the existing Pbkdf2Keystore will be used or ScryptKeystore if not specified.
When it comes to exiting through the keystore file, there is no need to specify as the Keystore.decrypt function will call self.kdf which then does a simple check of return scrypt(**kwargs) if 'scrypt' in self.crypto.kdf.function else PBKDF2(**kwargs)
Fixes #37

I've updated the wording but was struggling because pbkdf2 is less secure than scrypt and our iteration count of 262,144 is currently below the recommended 600,000.  This is a recently updated recommendation which explains the discrepancy from the spec.
I'd like to be more specific with pbkdf2 being a more performant but less secure option but I worry about alarms that could raise.

I've updated the wording but was struggling because pbkdf2 is less secure than scrypt and our iteration count of 262,144 is currently below the recommended 600,000. This is a recently updated recommendation which explains the discrepancy from the spec.
I'd like to be more specific with pbkdf2 being a more performant but less secure option but I worry about alarms that could raise.

What about using a good default iteration count and making the iteration count configurable with another flag? If someone really wants speed, he could choose a lower iteration count while making the compromise of less security but it would be an opt-in.

What about using a good default iteration count and making the iteration count configurable with another flag? If someone really wants speed, he could choose a lower iteration count while making the compromise of less security but it would be an opt-in.

I worry about the cost-benefit of adding the iteration count parameter. We would definitely want to have some minimum to allow a standard and then it would be directly utilized with the kdf params which is where auditors might be a bit scrupulous.
I played around with an increase of the iteration to 2**20 to measure creation time and it becomes slower than scrypt.
My knowledge of cryptography is very limited but because the params are saved in the file there should be no compatibility concerns if used with any iteration count.
But you do raise a good point: The original issue was requested for a shorter decryption time. The encryption and decryption time is a function of the iteration count so as that increases the performance of the former decreases.
This is where I'd like to ask Carl why PBKDF2 was never included 😁
But in the end, it probably becomes moot due to the password ultimately being the deciding factor. Given the password length requirement of 8 characters, I would imagine that is going to be the weakest link regardless of kdf iteration count.
Given that ramble, are you happy with the wording or would you like to make additional changes?

I'm happy with the wording changes and I don't see any other pressing need for this PR. I would accept it as is.


SAK-33776 Updated handsontable to Sakai's version 6.2.2

@ottenhoff The 6.2.2. artefact needs to be in the repo before this gets merged.


beps/0002: add dynamic FE plugins cli,backend,loading proposals

Expands on the initial drafts based on prior conversations.
Updates

plugin manifest
tooling decisions

New sections

proposal for new CLI features

plugin building
generating a list of shared dependencies

proposal for the backend plugin to serve dynamic frontend plugin assets
proposal for plugin loading
design details for build configurations
design details for dependency sharing

cc @Rugvip

@Rugvip I think I've addressed all the comments. Mind taking another look?

@Hyperkid123 @Rugvip has been out on holiday past few weeks, should be back next week, but there will be a lot to catch up on for sure :)


Size cleanup

Following #369 , I cleaned up a bit the point-size-scaling machinery in a way that hopefully addresses that problem, and makes it more robust and self-explanatory.

I'm not sure I like this. When there are negative values in the dataset, this will look like there are missing points.
Why/where is the previous code not working?

For instance, the log would have negative values, that would render as the absolute value so small values give larger points. Also in general, given we don't have a "scale" to refer to, it is really hard (should I say impossible?) to interpret a sqrt(x), log(x) or 1/x scaling if it is referred to a shifted range.

I guess that's fair, but then I would do like when using a log scale for the x/y/z axis and (a) send a warning to the user instead of doing this silently, and (b) ideally drop/hide the corresponding points

I guess that's fair, but then I would do like when using a log scale for the x/y/z axis and (a) send a warning to the user instead of doing this silently, and (b) ideally drop/hide the corresponding points

Fair. Done ^_^


always use NAMED_CURVE format for EC key storage; fixes #9

As described on #9 this forces NAMED_CURVE format for EC keys and resolves issue with generating account key and certificates with algorithm = "ecdsa_p256" when using OpenSSL 1.0.1/1.0.2 or LibreSSL.
Tested with OpenSSL 1.0.2 and LibreSSL 3.0.2.

I know I'm very late, but thank you!


Adds unit tests for DBHandler and MainActivity.

Following tests are covered in this:

SQLite Database communications test
Test for connection with ODK Services Database
QRCode Scanner Test

@linl33 @jbeorse I've made the required changes.


Bind to all interfaces

When running under WSL2, binding only to localhost via the <IP_ADDRESS> address
only lets you access the server from within WSL2 itself. It does not allow you
to access the server from Windows.
With this change, you can access the web server from the WSL ip address. You can
find your WSL ip address with
$ ip a | grep eth0
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0

Conflicting feelings here: I intuitively feel that bindings to all network interfaces with <IP_ADDRESS> is a bad default.
In some environments is needed (e.g. WSL2 or Docker) but I would like to avoid opening the web server to traffic coming (potentially) from the internet as a default setting.
Maybe as a comment?
From chapter03-1 it becomes configurable, so it should be easier for people to customise it.

Conflicting feelings here: I intuitively feel that bindings to all network interfaces with <IP_ADDRESS> is a bad default.

I agree.

In some environments is needed (e.g. WSL2 or Docker) but I would like to avoid opening the web server to traffic coming (potentially) from the internet as a default setting.
Maybe as a comment?

This would be a great solution. Keep the defaults secure, but let people know that it could cause issues. That way people can be spared the debugging session

From chapter03-1 it becomes configurable, so it should be easier for people to customise it.

Great, looking forward to it!

In some environments is needed (e.g. WSL2 or Docker) but I would like to avoid opening the web server to traffic coming (potentially) from the internet as a default setting.
Maybe as a comment?

This would be a great solution. Keep the defaults secure, but let people know that it could cause issues. That way people can be spared the debugging session

Do you want to do it updating this PR or should I create a new one?

From chapter03-1 it becomes configurable, so it should be easier for people to customise it.

Great, looking forward to it!

It's already in master :grin:

This would be a great solution. Keep the defaults secure, but let people know that it could cause issues. That way people can be spared the debugging session

Do you want to do it updating this PR or should I create a new one?

I updated the PR, reverting the binding to localhost and added a comment explaining about the connectivity issue.

It's already in master 😁
Isn't it just the port number that's configurable? Here it still looks like the localhost part is still hardcoded.

You are right, I'll make the host configurable as well :sweat_smile:


Do not install ruby-debug on travis-ci.org

Compilation of linecache takes forever and a day and nobody is going to debug anything in headless VMs.

Thanks :)


[Feature] Raging Blood feat

https://www.d20pfsrd.com/feats/general-feats/raging-blood
This looks extremely nifty for sorc-gishes or eldritch scion magus, especially if the 2 four round bloodrages is switches to an eight turn total meter and extra rage feats are applicable

I am interested in this for sure. Main concern is complexity of having this act "as blood-rage" but maybe there's a clever way to simplify that.

Make it use the bloodrage buff and add ever more conditionals to make the baby bloodrage level from the feat be the one that appears if that's the highest level you have?

Yeah that's one way I was thinking about it. But either way this will be after my 1.0 release so not thinking too hard about it right now

I've been messing around with rage and this could be a nightmare to dynamically implement because rather than do the smart thing and have one hidden buff for all the "this works on all rages" effects they add them separately to each form of rage. Still cool tho.


aaa

aaaa

Changes Unknown when pulling dfd2fe55f0ad2bbcae8198d2d544f6f00d1c114b on master into ** on aalmiray-feature_adapters**.

420 commits?

Changes Unknown when pulling 59f7ec2a2a432deecabc081db858d2d0e06de268 on master into ** on aalmiray-feature_adapters**.


Azure Monitor Log for .NET (April-August 2021)

This epic tracks the work required by the Azure SDK team to build the Azure Monitor Log Analytics and Alerts SDK in .NET
https://docs.microsoft.com/en-us/azure/azure-monitor/overview
Azure Monitor Log Analytics & Queries is a service that monitors your cloud and on-premises environments to maintain their availability, performance, and other aspects.  As part of the service, powerful interactive query capabilities are available that allow you to ask advanced questions specific to your data.  While a comprehensive IDE is available to execute these queries, it is sometimes necessary to access the data programmatically.  This service allows you to do just that: programmatically execute your Azure Monitor Log Analytics queries.

Closing as https://github.com/Azure/azure-sdk/issues/3087 is epic being used to track this in Nickel


changed preset to init

@sineld thanks for the PR!
I am imagining what prompted this - you were following the documentation on Github, using latest kool version 1.5.0, and then realised it mentioned a preset command that didn't exist, and realised it was meant to be init - is that what happened?
Just to put a context on this - for semantic reasons we are changing init to preset, that is already merged onto master but not yet released in a new version. We will still keep kool init but as deprecated, so it will only be removed when 2.0 comes out. This work is part of #11
So as soon as we release 1.6.0 we will have kool preset (still will have kool init, but noted as deprecated).
@danielsuguimoto - let's do a release as soon as possible!

@dbpolito - the GH action for updating kool.dev/docs is happening whenever we go to master. Can we change it to happen only for tags creation?

Cool, I just thought iw was written wrong.
Well done.
Thanks.

Version 1.6.0 has just been released. Now docs and kool are in sync. I'm closing this pull request, but thanks for contributing anyway, @sineld!

FYI: i fixed the GH action to avoid this happening again https://github.com/kool-dev/kool/commit/b487f7976458974cc3f6ec88c3259c946a0d2785
Thanks again for pointing it for us :+1:


[MM-14720] Add bot post counts per day to System Analytics

Summary
This PR adds a new component to the System Console Site Statistics page.
The new chart is located directly below the Total Posts chart.

Jira Ticket Link
https://mattermost.atlassian.net/browse/MM-14720
Related Pull Requests

Has server changes (https://github.com/mattermost/mattermost-server/pull/11402)
Has redux changes (https://github.com/mattermost/mattermost-redux/pull/868)
Has mobile changes (N/A)

@crspeller, @lieut-data How do I resolve the untagged-build required check?

@jfrerich Looks like you error is:
134:15  error  'botPostCountsDay' is assigned a value but never used  no-unused-vars

You can click the "details" to find the error.

@crspeller 	All three repos are now clean for merging.  I also ran into an error with i18n/en.json so I added the offending line in that file.  (see last commit)
Thanks for the reviews.

@jfrerich Can you update the redux commit for this? (since there are redux changes)

@jfrerich Can you update the redux commit for this? (since there are redux changes)

Hey @crspeller, what are you asking for?  What else was required, in addition to the redux PR https://github.com/mattermost/mattermost-redux/pull/868?

@jfrerich You have to update the redux commit in the package.json file to point to your merged changes. Otherwise it won't pick up the changes. Likely someone else has set the commit beyond your changes, so merging master would be enough.

@crspeller Thanks for the explanation.  The webapp package.json currently points to mattermost-redux commit that is 4 commits newer than what we merged.  I merged the latest master in this branch and now we are clean.

@jfrerich I'm updating the docs to include the new chart you added.  Can you verify that the difference between these two charts is correct (subtle):
Total Posts (graph)     The total number of posts made on a certain day in all the teams on your system, including deleted posts and posts made using automation.
New Chart Total Posts from Bots (graph)     The total number of posts made on a certain day in all the teams on your system, including deleted posts, exclusively made using automation.
https://github.com/mattermost/docs/pull/2898

Hi, @aaronrothschild.  FYI, I haven't forgotten about you and was working on another 5.14 ticket.  I'm 99% these charts are correct and the calculations match as you described.  If we are going to add charts, I would recommend creating two that don't match so closely.   The reason the two above are so similar is that I took a portion of the users in the sampledata and converted them to bots.  I can generate some better looking (more realistic) charts if you'd like.


Update README.md

Adding a Go report card to our library!

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           master   #19   +/-   ##
====================================
  Coverage      58%   58%
====================================
  Files           7     7
  Lines         231   231
====================================
  Hits          134   134
  Misses         68    68
  Partials       29    29

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 fb560ca...10901dd. Read the comment docs.


go mod friendly

https://github.com/containerd Subproject checklist (EDIT: added by @AkihiroSuda )

[x] containerd
[x] cri: https://github.com/containerd/cri/pull/1377
[x] imgcrypt: https://github.com/containerd/imgcrypt/pull/7
[X] cgroups
[X] console
[x] go-runc: https://github.com/containerd/go-runc/pull/59
[x] continuity
[X] go-cni
[x] aufs: https://github.com/containerd/aufs/pull/18
[x] zfs: https://github.com/containerd/zfs/pull/26
[X] ttrpc
[x] release-tool: https://github.com/containerd/release-tool/pull/8
[X] typeurl
[x] fifo: https://github.com/containerd/fifo/pull/22
[x] btrfs: https://github.com/containerd/btrfs/pull/22
[X] stargz-snapshotter: https://github.com/containerd/stargz-snapshotter/pull/65

Description
Containerd currently causes issues for downstream projects using go mod. Since this is the official Go dependency management tool now, support would be nice.
Steps to reproduce the issue:

Import containerd from a project using go mod for dependency management.
Build the project

Describe the results you received:
Does not build. Specifically due to the following.
# github.com/containerd/containerd/images/archive
/home/ry/go/pkg/mod/github.com/containerd/containerd@v1.2.4/images/archive/reference.go:72:21: undefined: reference.ParseDockerRef

Module based builds were actually working fine until this commit https://github.com/containerd/containerd/commit/ed756ffdd47729d90fc414286a5cc906160705f1 which introduced a dependency on code that is only in the master branch of docker/distribution.
As a workaround we currently use
replace github.com/docker/distribution v2.7.1+incompatible => github.com/docker/distribution v2.7.1-0.20190205005809-0d3efadf0154+incompatible

in our go.mod file. But this is not really maintainable and also slows down built time significantly as it requires re-download of certain modules on every build.
Describe the results you expected:
Project builds.
Output of containerd --version:
containerd github.com/containerd/containerd v1.2.2<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce

Thanks

SGTM (but let's wait for Go 1.12 GA)

yup, using go v1.12  go mod with v1.2.4 breaks:
# github.com/containerd/containerd/images/archive
../../go/pkg/mod/github.com/containerd/containerd@v1.2.4/images/archive/reference.go:72:21: undefined: reference.ParseDockerRef

setting the go.mod requirements to use containerd v1.2.3 fixes it for me.

SGTM (but let's wait for Go 1.12 GA)

Go 1.12.x has been GA for a while. Can we get a resolution to this? Causing some dependency hell here, thx.

Also breaks with 1.2.8.

Still broken with 1.2.9 - can confirm that changing to 1.2.3 (heh) fixes it.

Seems to still be broken with 1.3.0, if this error is related:
$ go get github.com/moby/buildkit
go get<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid pseudo-version: version before v1.3.0 would have negative patch number

go version go1.13.1 linux/amd64

@imiric Not sure how you got this to work, but def broken for me. replace did not solve my problems.

Go mod doesn't work well with repositories that use release branches; 1.3.0-beta.2 was the last beta tagged from master, after which the release/1.3 branch got created, from which 1.3.0-rc.0 and up are released. I think there's a regression in go mod in go1.13, where that got worse

I think there's a regression in go mod in go1.13, where that got worse

@thaJeztah It looks like this was an intentional change:
https://github.com/golang/go/commit/6bf2767cc87f9f6a1b85cdc18c656fade735f27f

Any update on this? I'm still affected using go 1.13.4.

Added check list to the top comment of this issue for tracking the progress across github.com/containerd repos. Help wanted.

Still wondering how we'll deal with versioning. While this repository has SemVer tags, those tags apply to the binary releases, not to the Go API. The Go client API is explicitly called out as "unstable", and therefore many projects use a specific version from master (which could be problematic if Go mod prefers tags over master).
While there is an intent "to stabilize the API in a future release", it's possible that changes to that API (interfaces/signatures) may follow a different cadence than the releases; should separate tags be used for Go, or should they be in lock-step with the containerd releases themselves?

I think we have never broken Go API in patch releases (correct me if wrong).

I think we have never broken Go API in patch releases (correct me if wrong).

Agreed, I don't think patch releases (vX.Y.Z) broke compatibility, but minor releases may definitely not have been minor from the API perspective (at least, I'm not sure if that has been carefully looked at with each change).
With Go (afaik) requiring major releases to be included in the import path, any breaking change in the Go client API should then have its major version bumped and (again, if I'm not mistaken) import paths updated.

Seems like it may be good to agree of a certain major & minor version of golang we should use with all projects to be consistent?

With Go (afaik) requiring major releases to be included in the import path, any breaking change in the Go client API should then have its major version bumped and (again, if I'm not mistaken) import paths updated.

It is "recommended strategy", but we don't need strictly adhere to?
IIUC,  a bunch of projects including Kubernetes adopted go.mod without strictly obeying that rule.
Anyway, we are trying to do our best to establish Go API stability in 1.4 (#3531).

I seem to be getting an error with dep:
alex@nightshade:~/go/src/github.com/alexellis/faasd$ go version
go version go1.12.14 linux/amd64
alex@nightshade:~/go/src/github.com/alexellis/faasd$ export GO111MODULE=off
alex@nightshade:~/go/src/github.com/alexellis/faasd$ go build
# github.com/alexellis/faasd/vendor/github.com/containerd/containerd/images/archive
vendor/github.com/containerd/containerd/images/archive/reference.go:73:21: undefined: "github.com/alexellis/faasd/vendor/github.com/docker/distribution/reference".ParseDockerRef
alex@nightshade:~/go/src/github.com/alexellis/faasd$

[[constraint]]
  name = "github.com/containerd/containerd"
  version = "1.2.0"

[prune]
  go-tests = true
  unused-packages = true

@alexellis it currently depends on a version of docker/distribution from master having this commit: https://github.com/docker/distribution/commit/0ac367fd6bee057d404c405a298b4b7aedf301ec (the 1.3.2 branch is using this commit: https://github.com/containerd/containerd/blob/v1.3.2/vendor.conf#L59).
dep probably picks the latest tag (v2.7.1), which does not have that patch. I opened a backport for the 2.7.x release branch (https://github.com/docker/distribution/pull/3002) but it isn't merged yet, and will require a new tag/release so that dep (and go mod) will pick it up automatically.
For now, you can add an override/constraint to your Gopkg.toml to pin the dependency to the same commit as the 1.3.2 version (https://github.com/docker/distribution/commit/0d3efadf0154c2b8a4e7b6621fff9809655cc580)

Mixing up vndr and go mod is becoming harder (https://github.com/containerd/cgroups/issues/139).
Can we soon finish migrating the entire stuff to go mod?
Is there any blocker?

Thanks @thaJeztah

Based on this tweet from @ibuildthecloud, it looks like once CRI starts to vendor in k8s 1.17, it gets a lot less messy to use go mod. Maybe @Random-Liu can say when they are ready to move up the CRI project deps and then we can vendor that back in and move to 1.17 and be ready to fully switch to go mod?

Running a basic app still fails:
package main

import (
	"log"

	"github.com/containerd/containerd"
)

func main() {
	client, err := containerd.New("/run/containerd/containerd.sock")
	defer client.Close()
}

with the following error:
# github.com/containerd/containerd/images/archive
../../.go/pkg/mod/github.com/containerd/containerd@v1.3.3/images/archive/reference.go:73:21: undefined: "github.com/docker/distribution/reference".ParseDockerRef

@gun1x try the following require(s) in your go.mod
module example.com/m

go 1.13

require (
	github.com/containerd/containerd v1.3.3
	github.com/docker/distribution v2.7.1-0.20190205005809-0d3efadf0154+incompatible // indirect
)

That worked. it would help to have stuff like this in the docs here: https://github.com/containerd/containerd/blob/master/docs/getting-started.md

@Random-Liu One of the significant issues of moving to go.mod is that CRI uses the streaming server from k8s.io/kubernetes. Is there any effort to move the streaming server to k8s.io/streaming-server or something similar?  Until this happens go.mod in containerd will be a real headache.

Any updates here?
Thanks!

dims moved the streaming code... and we are merging cri into containerd... and https://github.com/containerd/cri/pull/1377#issuecomment-664136849

It looks like go mod init github.com/containerd/containerd is happy to run now.

go.mod
module github.com/containerd/containerd

go 1.15

require (
        github.com/BurntSushi/toml v0.3.1
        github.com/Microsoft/go-winio v0.4.15-0.20200908182639-5b44b70ab3ab
        github.com/Microsoft/hcsshim v0.8.10
        github.com/Microsoft/hcsshim/test v0.0.0-20201111181659-f14fc666e78f
        github.com/containerd/aufs v0.0.0-20200908144142-dab0cbea06f4
        github.com/containerd/btrfs v0.0.0-20201111183144-404b9149801e
        github.com/containerd/cgroups v0.0.0-20200824123100-0b889c03f102
        github.com/containerd/console v1.0.1
        github.com/containerd/continuity v0.0.0-20200710164510-efbc4488d8fe
        github.com/containerd/fifo v0.0.0-20201026212402-0724c46b320c
        github.com/containerd/go-cni v1.0.1
        github.com/containerd/go-runc v0.0.0-20200220073739-7016d3ce2328
        github.com/containerd/imgcrypt v1.0.1
        github.com/containerd/nri v0.0.0-20201007170849-eb1350a75164
        github.com/containerd/ttrpc v1.0.2
        github.com/containerd/typeurl v1.0.1
        github.com/containerd/zfs v0.0.0-20200918131355-0a33824f23a2
        github.com/containernetworking/plugins v0.8.6
        github.com/coreos/go-systemd/v22 v22.1.0
        github.com/davecgh/go-spew v1.1.1
        github.com/docker/go-events v0.0.0-20190806004212-e31b211e4f1c
        github.com/docker/go-metrics v0.0.1
        github.com/docker/go-units v0.4.0
        github.com/emicklei/go-restful v2.9.5+incompatible
        github.com/fsnotify/fsnotify v1.4.9
        github.com/gogo/googleapis v1.4.0
        github.com/gogo/protobuf v1.3.1
        github.com/golang/protobuf v1.4.2
        github.com/google/go-cmp v0.5.1
        github.com/google/uuid v1.1.1
        github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0
        github.com/hashicorp/go-multierror v1.0.0
        github.com/imdario/mergo v0.3.10
        github.com/moby/sys/symlink v0.1.0
        github.com/opencontainers/go-digest v1.0.0
        github.com/opencontainers/image-spec v1.0.1
        github.com/opencontainers/runc v1.0.0-rc92
        github.com/opencontainers/runtime-spec v1.0.3-0.20200728170252-4d89ac9fbff6
        github.com/opencontainers/selinux v1.6.0
        github.com/pkg/errors v0.9.1
        github.com/prometheus/client_golang v1.7.1
        github.com/sirupsen/logrus v1.7.0
        github.com/stretchr/testify v1.4.0
        github.com/syndtr/gocapability v0.0.0-20180916011248-d98352740cb2
        github.com/tchap/go-patricia v2.2.6+incompatible
        github.com/urfave/cli v1.22.2
        github.com/willf/bitset v1.1.11 // indirect
        go.etcd.io/bbolt v1.3.5
        golang.org/x/net v0.0.0-20200707034311-ab3426394381
        golang.org/x/sync v0.0.0-20200625203802-6e8e738ad208
        golang.org/x/sys v0.0.0-20201013081832-0aaa2718063a
        google.golang.org/grpc v1.30.0
        gotest.tools/v3 v3.0.2
        k8s.io/api v0.19.2
        k8s.io/apimachinery v0.19.2
        k8s.io/apiserver v0.19.2
        k8s.io/client-go v0.19.2
        k8s.io/component-base v0.19.2
        k8s.io/cri-api v0.19.2
        k8s.io/klog/v2 v2.2.0
        k8s.io/utils v0.0.0-20200729134348-d5654de09c73
)

But I notice some dependencies are bumped. And it seems that the release-tool needs update too.

@zhsj thanks for testing out. I have tried to make updates in release-tool to better handle the difference representation in dependencies. If you are seeing issues please file it over there. I want to get those fixed early so we don't have that as a headache if we pull go mod into the next release.

Completed in https://github.com/containerd/containerd/pull/4760

Completed in https://github.com/containerd/containerd/pull/4760


Update Population Class and SQL Statements

Port over your SQL commands (from your xxxxReport.class) to ReportEngine.class
Make sure reportSQL[X] corresponds with the report ID indicated on README.me (VERY important for testing)
Your SQL variable (N) should be defined as XXXXX in the SQL text (so it is replaced by the method at runtime)

Updated in branches. To be updated.


Gitlab-ce version update & SMTP values

Updated Gitlab-ce version to v9.2.1
Added values and updated configmap to pass smtp configuration.

/cc @gtaylor

@k8s-bot ok to test

I'm not able to test this right now, but it looks right.

Just seeing that gitlab.com has a slightly different chart and solution for smtp (as well as https).
https://docs.gitlab.com/ce/install/kubernetes/gitlab_chart.html
Not sure if my updates are relevant anymore.

@crackmac How would you want to proceed then?

Closing this due to inactivity.


No manual word inputs

The algorithm currently only uses  100% computer-generated words, if a real human were playing and wanted the algorithm for help, but not to use it 100% completely, then this would be a useful feature.

Added manual word selection


Fails silently

Steps to reproduce
Get your neon account into a state where you are "locked" waiting for operations to complete

Expected result
The github action to fail -- or ideally, retry
Actual result
Variable outputs are null
Logs, links

Hey! Retry logic now has been added to the action, should resolve the issue

Great thanks! Updating now


Fix copyright.

This change is

Jenkins job mixer/presubmit passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

@sebastienvas any idea what's going on with Jenkins in this PR? It appears to have lost its mind, and is spamming our inboxes as a result.

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/manager-regression passed

And then people ask me why do you want to switch from Jenkins? I upgraded plugins yesterday night this is what happens. I cleared the trigger data