Add task runner

So, I guess we should think about task runner.
I'm kinda in the "let's not use grunt/gulp etc" camp just now because they are so heavy for what we want.
I quite like the idea of using npm scripts, or something like https://github.com/start-runner/start
Having said that, I think trails uses gulp by default, so it would take a bit of work to recreate that, but that's probably not a problem.
Thoughts?

Yeah, sounds good. I liek that. I've taken grunt out of sails, and we'll do everything with npm scripts.


Scaffold initial page for adding vendors/cookies for consent

Is your feature request related to a specific problem?
In order to simplify the consent UI flow, we need a page where we can easily add vendors and cookies.
Describe the solution you'd like
We should add a page under "Consent" called "Configure". It needs to have an empty state with buttons to allow either adding a vendor or adding a cookie. It should be guarded by plus, and perhaps also privacy-notice:read to keep it consistent with the privacy notice page.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
https://ethyca.atlassian.net/wiki/spaces/EN/pages/2778202186/2023-09-06+Simplify+consent+UI

moving to done


using cross affects ci workflow

I just found out that juliaup uses action-rs/cargo with cross set to true which limits installing additional dependencies. These dependencies might be needed for some crates e.g. reqwest with native-tls enabled looks for openssl-dev. The cross tool can actually allow us to make a pre-build hook e.g. install libssl-dev or pkg-config inside the container before running cargo. See https://github.com/cross-rs/cross/pull/678. However action-rs/cargo seems to not have updated to include the pre-build hook. This makes sense since the functionality was added since 2022 while action-rs/cargo has not been updated since 2021
Assuming we have the prebuild hook option, we can do the following to install openssl devel inside the cross container:
    - name: Test
      uses: actions-rs/cargo@v1
      with:
        use-cross: true
        pre-build: 'apt-get install -y libssl-dev pkg-config'
        command: check
        args: --target ${{matrix.target}} --features ${{matrix.features}}

There is an open issue at https://github.com/actions-rs/cargo/issues/115 but it's been two years since action-rs/cargo was updated.
This issue affects my PR #613 where I cannot test if my changes build correctly

Solution:
We can just use vanilla cross without using the github action (or fork it) to add the prebuild hook functionality as described in their README but I haven't tested it.

Just to add. This also means that apt-get install musl-tools didn't do anything because of cross

Seems another project noticed - https://github.com/kanidm/webauthn-rs/pull/301
I will open a pull request I guess.

I think this is not really a problem right now? For the certificate situation things work on the PR now. I'm closing for now.


[Feature Request] Zoom onto selected element [Help wanted]

Use case
(a) User has marked element X in the "View".
(b) User press CTRL and moves mouse-wheel to zoom in.  Archi then zoom onto the selected element and not 'straight onto the current view'.
Savings
User will no longer have to repeatedly press SPACE and 'move the screen' to selected element.
Existing issues?
Issue list searched and no similar request found.
Sincere Regards :)

Perhaps the same as #103 ?
For this one and #103, it requires someone to investigate the Eclipse GEF (Graphical Eclipse Framework) and devise a way to do this. So I'll make this with "help wanted"

Spot on.  Can't say I'm an expert on EGEF but let's see if someone engage, otherwise ... maybe... there's a hobby project coming up here :)

I would have appreciated to be able to zoom to a selection using CTRL&SCROLL WHEEL. I found this code here: https://github.com/ApexSoft/modellipse/blob/master/org.eclipse.papyrus.uml.diagram.menu/src/org/eclipse/papyrus/uml/diagram/menu/toolbar/ZoomToolbar.java
Can it may help to implement this feature?

Can it help to implement this feature?

Sorry, no. There's nothing there to actually zoom into selected elements


[Feature] Add "help" or "usage" if an argument is passed that requires more arguments.

Describe the solution you'd like
When passing an argument after ./cnf-testsuite cnf_setup, cnf_setup requires more arguments, if nothing passed on command line, cnf-testsuite should display usage or help based on that argument.
For instance, cnf_setup requires cnf-config=./path/to/config or cnf-path=./path/to/dir so if this requirement is not met, it should print out usage help.
Describe alternatives you've considered
None
Additional context
This should apply to any arguments that require more arguments passed.

@agentpoyo can this issue be closed?


fix ingress examples

I walked over examples on https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/
and made sure they do work again
fixes kubernetes/minikube#7910

@cmluciano can you serve as a technical reviewer for this? Just add a /lgtm if it is technically accurate.  Thanks!
/cc @cmluciano

/assign

@radeksm thanks for your PR! There was recently a PR merged with similar fixes. Is this PR still needed?
Please review the current state of: https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/
I was able to walk through the entire example using the katacoda terminal browser and had no problems.

This PR is stalling for one month with conflicts to be solved.
Please feel free to reopen this and resolve the conflict.
/close


Bug in Demo: Audio File Playback

I found a bug in Audio File Playback demo. When allowing user to select output device, you first fill the combo boxes with available devices from index -1. But then when selecting the device, you return SelectedIndex property of the combo box. This means that the numbers are shifted by 1. For exaple if I select the first item in the combo box, the SelectedIndex will be 0, but deviceId of this device should be -1.
I think this happens in all the files NAudioDemo/AudioPlaybackDemo/*SettingsPanel.cs

thanks for reporting, I'll get this fixed

this is now fixed in the latest code and will be part of the next release


Some questions about the basicvsr_net.py

In class SPyNet(nn.Module),The comment of the function compute_flow is written as Compute flow from ref to supp. Is that right?  I read the code carefully and found that it calculates the flow from supp to ref in：
flow = flow_up + self.basic_module[level](
torch.cat([
ref[level],
flow_warp(
supp[level],
flow_up.permute(0, 2, 3, 1),
padding_mode='border'), flow_up
], 1))
Hope for your reply！

In fact, it is the flow from ref to supp. When you warp supp to ref using backward warping, you are using the flow from ref to supp.
Intuitively speaking, each point in the flow indicates the relative position where I should look for at supp. It is equivalent to the flow from ref to supp.

Thank you for your reply! I got it.

Good to hear that :)


Boolean array indexing is not compatible with static memory allocation

JAX is built on top of XLA which (currently) requires static memory allocation for operations. This means it is not possible to express operations like x[y] where y is a boolean, because the resulting array has value dependent size: https://data-apis.github.io/array-api/latest/API_specification/indexing.html#boolean-array-indexing
It's definitely possible that the static memory allocation requirement could be relaxed in the future, but dynamic memory allocation is always going to be harder to implement in a performant way. For example, I would guess Numba also struggles with this sort of operation. I don't think we should require it for array libraries implementing our standard, since it isn't needed for the majority of array operations.

Dask’s lazy evaluation struggles with this a bit too. The output shape of a Boolean mask will have NaN for the shape in that dimension, and .size will be NaN.

On Nov 11, 2020, at 17:11, Stephan Hoyer<EMAIL_ADDRESS>wrote:

JAX is built on top of XLA which (currently) requires static memory allocation for operations. This means it is not possible to express operations like x[y] where y is a boolean, because the resulting array has a dynamic size: https://data-apis.github.io/array-api/latest/API_specification/indexing.html#boolean-array-indexing
It's definitely possible that the static memory allocation requirement could be relaxed in the future, but dynamic memory allocation is always going to be harder to implement in a performant way. For example, I would guess Numba also struggles with this sort of operation. I don't think we should require it for array libraries implementing our standard, since it isn't needed for the majority of array operations.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

For example, I would guess Numba also struggles with this sort of operation

Numba does support boolean indexing, but only for 1-D arrays - and you cannot mix it with other advanced indexing.

Related JAX issues with discussion:

https://github.com/google/jax/issues/166
https://github.com/google/jax/issues/2765

It does seem that there's very limited support for boolean indexing (only static boolean arrays, which are not all that useful in practice), and none for jitted functions.
This led me to wonder about other functions where output shape depends on values in the input, such as unique. That is implemented, but also not jittable: https://github.com/google/jax/pull/2760
TensorFlow is in a similar boat, but provides a boolean_mask function instead. And there's an open PR for JAX to add index_mask which looks similar.

nonzero and where are also problematic here.

I think that's the complete list of functionality where shapes depend on values - so maybe that's a good set to separate out somehow. They are fairly heavily used functions, so would be good to dig up some examples - say in SciPy or scikit-learn - and figure out if those are easy to rewrite.

Of course this can happen with basic indexing as well:
x = arange(5)
idx_max = random.randint(0, 5)
x2 = x[:idx_max]

So there needs to be something said about the principle of shapes depending on values.

The summary of a discussion we had a few days ago:

boolean indexing is fairly fundamental to how people use NumPy; leaving it out completely may cause people to simply ignore the standard.
given that this type of data-dependent shape can be produced by several other functions, we need a way to clearly mark that as a property of those functions and of boolean indexing. I.e. with color-coding or a custom admonition in the API standard document.

Dask’s lazy evaluation struggles with this a bit too. The output shape of a Boolean mask will have NaN for the shape in that dimension, and .size will be NaN.
…

This is true. Though there are some subtleties (which I'm sure Tom also knows), but others here may not. For example, if we know the values in the mask beforehand (it's not a Dask Array) and raveling is not involved (it's applied along a single dimension), we can produce a Dask Array of known shape. However if one of those things is not true, then the Dask Array's shape is undetermined.
In [1]: import numpy as np

In [2]: import dask.array as da

In [3]: X = da.ones((10, 11, 12),chunks=(2, 3, 4))

In [4]: Y = np.arange(10) > 5

In [5]: X[Y].chunks
Out[5]: ((2, 2), (3, 3, 3, 2), (4, 4, 4))

In [6]: Y2 = np.arange(10 * 11 * 12).reshape(10, 11, 12) > (10 * 11 * 12 / 2)

In [7]: X[Y2].chunks
Out[7]: ((nan, nan, nan, nan, nan, nan, nan, nan, nan, nan),)

In [8]: Y3 = da.asarray(Y, chunks=2)

In [9]: X[Y3].chunks
Out[9]: ((nan, nan, nan, nan, nan), (3, 3, 3, 2), (4, 4, 4))

Sorry, looks like I overlooked this discussion. I don't think CuPy has full support over boolean masks either: https://github.com/cupy/cupy/issues/4693#issuecomment-788950506.

Indeed. I had interpreted it to mean that boolean indices were only allowed as the sole index, and were not required to be supported as part of a larger multidimensional index. I believe this was intentional, because mixing a boolean array index with an slice and integer index in NumPy can trigger the weird "advanced indices separated by slice, ellipsis, or newaxis" rule (https://numpy.org/doc/stable/reference/arrays.indexing.html#combining-advanced-and-basic-indexing). Note that for the purposes of this rule, integer indices are treated like 0-dimensional integer array indices:
>>> b = np.array([[True, False], [True, True]])
>>> a = np.arange(1*2*2*4*5).reshape((1, 2, 2, 4, 5))
>>> a[:, b, :].shape
(1, 3, 4, 5)
>>> a[:, b, :, 0].shape
(3, 1, 4)

(note how the 3 dimension is moved to the front when the boolean and integer indices are separated by a slice).
My understanding is that we want to avoid making this rule part of the spec (Travis had expressed to me that he wished it to not be there, and that he would prefer if NumPy didn't do it in the first place). So if we do allow boolean arrays as part of larger multidimensional indices, it needs to be with caveats that disallow this case.
Another oddity I just noticed the boolean indexing section: it says "this is equivalent to A[nonzero(B)]", but that only works if we support integer array indexing, which we don't. So this should be rephrased in a way that doesn't assume that integer array indexing has been specified already.

(and to be clear, either way, the spec should be clarified, because I agree the way it's written now is a bit ambiguous)

dask.array has a restriction that bool indexing can be combined with other indexing only when it has dimension 1. However, it implements different semantics from NumPy in the above case:
>>> anp = np.arange(3*4*5*6).reshape((3, 4, 5, 6))
>>> bnp = np.array([True, True, False, False])
>>> anp[:, bnp, :].shape
(3, 2, 5, 6)
>>> anp[:, bnp, :, 0].shape
(2, 3, 5)
>>> a = dask.array.arange(3*4*5*6).reshape((3, 4, 5, 6))
>>> b = dask.array.array([True, True, False, False])
>>> a[:, b, :].shape
(3, nan, 5, 6)
>>> a[:, b, :, 0].shape
(3, nan, 5)

Pytorch also appears to implement this but with different semantics
>>> at = torch.arange(3*4*5*6).reshape((3, 4, 5, 6))
>>> bt = torch.tensor([True, True, False, False])
>>> at[:, bt, :].shape
torch.Size([3, 2, 5, 6])
>>> at[:, bt, :, 0].shape
torch.Size([3, 2, 5])

jax.numpy appears to follow numpy semantics
>>> aj = jax.numpy.arange(3*4*5*6).reshape((3, 4, 5, 6))
>>> bj = jax.numpy.asarray([True, True, False, False])
>>> aj[:, bj, :].shape
(3, 2, 5, 6)
>>> aj[:, bj, :, 0].shape
(2, 3, 5)

Neither jax nor pytorch seem to have the same restriction as dask on what kinds of boolean arrays are allowed. @jakirkham what is the purpose of the restrictions dask has on boolean array indices?

Sorry I'm not following Aaron. Could you please share what is being tried that doesn't work?

What is the purpose of this restriction in dask?
>>> a = dask.array.arange(2*2*4*5).reshape((2, 2, 4, 5))
>>> b = dask.array.array([[True, False], [True, True]])
>>> a[b]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/aaronmeurer/anaconda3/envs/array-apis/lib/python3.9/site-packages/dask/array/core.py", line 1705, in __getitem__
    self, index2 = slice_with_bool_dask_array(self, index2)
  File "/Users/aaronmeurer/anaconda3/envs/array-apis/lib/python3.9/site-packages/dask/array/slicing.py", line 1157, in slice_with_bool_dask_array
    raise NotImplementedError(
NotImplementedError: Slicing with dask.array of bools only permitted when the indexer has only one dimension or when it has the same dimension as the sliced array

This already isn't sufficient for the conservative interpretation of what is currently in the spec about boolean indexing, and it would presumably make it even harder to support indices combining boolean and non-boolean indexing like a[b, 0].

Raised as issue ( https://github.com/dask/dask/issues/7550 ). That said, I wouldn't be surprised if there are certain combinations passed to slicing that don't work. There is not one reason that captures all of these. In some cases there may be a lack of interest (no one has done a PR), some are technically challenging (so may not be implementable), and in some cases they are solvable, but following NumPy exactly leads to performance issues or doesn't make sense for Dask. The latter is particularly noticeable when raveling happens implicitly ( see issue https://github.com/dask/dask/issues/4855 )

Well the whole point of this issue is to figure out what we want to not include in the spec because it is too hard for libraries like dask, specifically relating to boolean indexing (integer array indexing is the other "hard" case, but it's already not in the spec). The spec does specify that boolean indices have to give C row-first order, so that is possibly relevant to dask/dask#4855. The specific question here is if combining (a single) boolean index with other indices is any harder than only supporting a single boolean index (sans the weird "boolean and integer separated by a slice" case that dask does differently from NumPy, and shouldn't be part of the spec regardless).
Going back to the case not supported by dask, does the fact that the array must be broadcasted make it harder? Should we restrict what the spec says even further by requiring not only that a boolean index be the sole index, but that it be the exact same shape as the indexed array?

I opened a PR clarifying that the spec only requires boolean arrays as the sole index, not as part of a larger multidimensional index. https://github.com/data-apis/array-api/pull/164
If we do want to allow them as part of a multidimensional index, we should discuss that further. The big open question is whether that causes any issues for any libraries, beyond the issues that are already caused by supporting boolean array indices in the first place.

As this issue should be addressed (boolean indexing is optional and admonitions have been added to the specification), will close this out.
If additional discussion is necessary, we can either reopen this issue or open a new one.


Organizations can restrict which repositories can enable Advanced Security (GHES)

Summary
Currently, GitHub Enterprise Server administrators can define a policy that determines which GitHub organizations can choose to enable GitHub Advanced Security, in order to facilitate a gradual roll-out of our security features like code scanning and secret scanning. We will be expanding this to a more fine-grained level of control where GitHub organizations can define which repositories can enable Advanced Security.
Intended Outcome
Enable GitHub organizations to manage the roll-out of Advanced Security across their business.
How will it work?
GitHub organizations will be able to define which repositories can choose to enable GitHub Advanced Security.

This shipped with GHES 3.8<EMAIL_ADDRESS>


The schema for PCA should specify that sparse input is not supported.

Scikit-learn's PCA does not support sparse input. The schema does not specify this.

Thank you for raising this issue! We will update the PCA schema accordingly.

Fixed by this PR: https://github.com/IBM/lale/pull/498


can submit issue without title, creates persistent broken session

User gets:
Octokit::UnprocessableEntity at /
POST https://api.github.com/repos/berkmancenter/amber_common/issues:
422 - Validation Failed Error
Issue code: missing_field
field: title

And cannot get out of it until they manually delete the session cookie in developer tools.

Fixed by https://github.com/benbalter/problem_child/pull/9. Thanks again @ryanttb!


Misskey package

Project description
Misskey is an open source, decentralized social media platform
Metadata

homepage URL: https://misskey-hub.net/en/
source URL: https://github.com/misskey-dev/misskey
license: agpl
platforms: linux

Closed by: #319348.


Change data tests to use expect assertion

Use expect assertions as they do not retry if fail

Codecov Report

Merging #288 (e0a36e1) into master (8b0567d) will increase coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #288      +/-   ##
==========================================
+ Coverage   85.56%   85.65%   +0.09%
==========================================
  Files          24       24
  Lines         942      962      +20
  Branches      340      351      +11
==========================================
+ Hits          806      824      +18
- Misses        136      138       +2

Impacted Files
Coverage Δ

src/Components/Common/Tables.js
88.72% <0.00%> (-0.25%)
:arrow_down:

src/Services/Filters.js
100.00% <0.00%> (ø)

.../Components/ClustersListTable/ClustersListTable.js
83.72% <0.00%> (+1.64%)
: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 8b0567d...e0a36e1. Read the comment docs.


support zookeeper

Coverage decreased (-0.6%) to 85.176% when pulling 5784cce177f32133a036ea5477e8bf281fae2cc6 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-2.7%) to 83.097% when pulling d63eeeb37ab09b186aa50840ad664962ed342859 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-2.7%) to 83.097% when pulling d63eeeb37ab09b186aa50840ad664962ed342859 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-3.09%) to 82.735% when pulling 18d95cafcc56d8d57b552bd95c661570c6e1aced on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-2.5%) to 83.3% when pulling bbee4600b88bb49167b72197a4b457a48108cd51 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-3.09%) to 82.735% when pulling 9b7b82f6adc523e9d4978c5c086f69a7e075f751 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-3.09%) to 82.735% when pulling 210a46eedac2676df8b881604ad62ccaf7d68961 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-4.3%) to 81.566% when pulling 4e296eb3a81e2efafbac598c7368af6871170997 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-3.09%) to 82.735% when pulling 470e159d05453837c640ba4d7a893030ff11f56f on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-3.09%) to 82.735% when pulling 470e159d05453837c640ba4d7a893030ff11f56f on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-0.6%) to 85.176% when pulling 132562a7c3c5fb9f2db47178ed9e86cfe9fda599 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-1.2%) to 84.65% when pulling 6ed6628c588564f4baef3539f8f155daf0b85b11 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-2.5%) to 83.333% when pulling 28c0fb4b2feae1530a86d8c1bc0c8e6a44793d6a on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.

Coverage decreased (-1.3%) to 84.491% when pulling 82854f97d1385e072a52696aff718626fdc42e53 on xyl_zkp into d8a748a448859e6053e0ad75ed3aa11514e017d7 on master.


Firefox doesn't appear in the Gnome application list

Issue description
In Gnome, if I click "show applications" on the dock, firefox isn't in the list of applications, and if I press the super (windows) key and search for "firefox", the only option is "Search the web for firefox".
Why I expect firefox should be there:

I'm using release-16.09, and have firefox in environment.systemPackages.
firefox.desktop seems to be in the right place. This is from a terminal in my Gnome session:

$ echo $XDG_DATA_DIRS
/home/falsifian/.nix-profile/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share
$ cat /run/current-system/sw/share/applications/firefox.desktop
[Desktop Entry]
Type=Application
Exec=firefox %U
Icon=firefox
Comment=
Terminal=false
Name=Firefox
GenericName=Web Browser
MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;x-scheme-handler/http;x-scheme-handler/https;x-scheme-handler/ftp
Categories=Application;Network;WebBrowser;

Closest existing issue I could find is #19934.
Steps to reproduce
Haven't tried this from a fresh install, but probably:

In configuration.nix, add firefox to environment.systemPackages and set desktop.gnome3.enable = true.
Log in
Press the super/windows key and type "firefox" in the search box; observe only "Search the web for firefox" and no actual Firefox application.
In the dock, press "show applications" and see no firefox listed.

Technical details

System: 16.09.1229.f52eaf4 (Flounder)
Nix version: nix-env (Nix) 1.11.4
Nixpkgs version: "16.09.1229.f52eaf4"

I tried running nix-env -i firefox and logging out and in again. Firefox still doesn't appear, even though now a file exists at ~/.nix-profile/share/applications/firefox.desktop.

But on NixOS $XDG_DATA_DIRS should be setup correctly by default: $HOME/.nix-profile/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share

Indeed, my XDG_DATA_DIRS
is /home/falsifian/.nix-profile/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share.
But this only happens on one of my accounts; when I create a new account Firefox appears in the Gnome menu. So somehow I've gotten myself into a strange state.


Test lowered shutdown timeout

Changes Introduced
Per https://github.com/http4s/http4s/issues/4934#issuecomment-865132425.
Applicable linked issues
Checklist (check all that apply)

[ ] This change maintains backwards compatibility
[ ] I have introduced tests for all new features and changes
[ ] I have added documentation covering all new features and changes
[ ] This pull-request is ready for review

Codecov Report

Merging #123 (00bc274) into main (4972f7e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #123   +/-   ##
=======================================
  Coverage   89.50%   89.50%
=======================================
  Files          85       85
  Lines        2772     2772
  Branches       89       89
=======================================
  Hits         2481     2481
  Misses        291      291

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 4972f7e...00bc274. Read the comment docs.


Initial render looks to be not working

After second click, it works normally, see small reproduction example:
https://codesandbox.io/s/small-test-ayrton-2384m5?file=/src/App.tsx
Either way, very nice library, indeed is very simple to use. :+1:

First, thank you very much for contributing, @rolivegab :)
I think we got off to a great start 🥳, as the problem was very specific to StrictMode in React 18, so thanks a lot for the test and the feedback 👏👏👏
The issue has been resolved in version 1.0.2. 🚀


TC002 false positive when using import in except

The following triggers TC002
import botocore.exceptions

if __name__ == "__main__":
    try:
        raise Exception("test")
    except botocore.exceptions.ClientError:
        print("got botocore error")
    except Exception:
        print("got other error")

Unfortunately if you action that advice, the code will fail at runtime in the except block.

Thanks for opening the issue. I'll create a fix for this this week most likely. Seems like an easy fix 😊

Looks like
import urllib.parse

urllib.parse.urlencode('')

Also triggers the same issue. We weren't handling double imports like this properly I think.
Would you mind testing if the code in https://github.com/snok/flake8-type-checking/pull/103 solves your use-case @kurtschelfthout? 🙂 You should be able to install the branch by using pip install git+https://github.com/snok/flake8-type-checking.git#except-block (or poetry add --dev git+https://github.com/snok/flake8-type-checking.git#except-block)

If I'm not mistaken, this should also fix #102 🤞

Can confirm both are fixed.
Beautiful!


formatting does not apply for mouse initiated paste

When pasting from context menu with mouse, the formatting does not apply the same way it would for Ctrl+V.
I tried both recent stable and 2.0.beta, both have this bug.

being fixed in version 2


feat(AppHeader): add AppHeader component

Overview

Create AppHeader component.

Part of the Global Nav Unification project.
This PR comes after EGG-539 and EGG-540, work done with @saghdaey which resulted in a draft PR combining all GlobalHeader work. We are now breaking up this branch to merge the following pieces separately:

EGG-643: AppHeaderLogo (#1277)
EGG-644: AppHeaderLink (#1278)
EGG-645: AppHeaderDropdown (#1279)
EGG-646: AppHeader (#1300)
EGG-647: GlobalHeader

Also standardizes the focus outline on the AppHeader elements and adds functionality to open AppHeaderLink in a new tab.
PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: EGG-646
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

🚀 Styleguide deploy preview ready!https://60084785ed39541f947181e2--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://60084785ed39541f947181e2--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@7.10.6-alpha.dfd3f5.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@7.10.6-alpha.dfd3f5.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60084ba084a96b24378e7d14--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://60084ba084a96b24378e7d14--gamut-preview.netlify.appDeploy Logs

@JoshuaKGoldberg you're right, I'll fill in the story with more details! Weird that the preview environment isn't loading...

@JoshuaKGoldberg you're right, I'll fill in the story with more details! Weird that the preview environment isn't loading...

📬Published Alpha Packages:@codecademy/gamut-labs@7.10.6-alpha.89bbc2.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@7.10.6-alpha.89bbc2.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60084e628fb8ac2cdd854381--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://60084e628fb8ac2cdd854381--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@7.10.7-alpha.e29458.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@7.10.7-alpha.e29458.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://600887c0c5722f008df99cc1--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://600887c0c5722f008df99cc1--gamut-preview.netlify.appDeploy Logs

This looks great, well done Katie!!!
I'm looking at the preview now - https://600887c0c5722f008df99cc1--gamut-preview.netlify.app/storybook/?path=/docs/labs-experimental-molecules-appheaderdropdown--app-header-dropdown
i think we may have talked about this before but I'm noticing that the drop down target (which is clickable) doesn't have cursor pointer on hover. maybe we can fix that in this PR?

This looks great, well done Katie!!!
I'm looking at the preview now - https://600887c0c5722f008df99cc1--gamut-preview.netlify.app/storybook/?path=/docs/labs-experimental-molecules-appheaderdropdown--app-header-dropdown
i think we may have talked about this before but I'm noticing that the drop down target (which is clickable) doesn't have cursor pointer on hover. maybe we can fix that in this PR?

@saghdaey great catch - thought I was going crazy because I thought I had fixed this, but turns out I can't spell https://github.com/Codecademy/client-modules/pull/1300/files#diff-da6e62ca12094f8efb8c2d8d4302f7c252d2732769a564ee94f1603f059b3c6bL27
cursor: ponter lol...

@saghdaey great catch - thought I was going crazy because I thought I had fixed this, but turns out I can't spell https://github.com/Codecademy/client-modules/pull/1300/files#diff-da6e62ca12094f8efb8c2d8d4302f7c252d2732769a564ee94f1603f059b3c6bL27
cursor: ponter lol...

📬Published Alpha Packages:@codecademy/gamut-labs@7.10.8-alpha.ea5c1a.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@7.10.8-alpha.ea5c1a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6008ad1a1747eb15e2a4a033--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://6008ad1a1747eb15e2a4a033--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@7.10.8-alpha.5280fd.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@7.10.8-alpha.5280fd.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://600b29a0ad07d40dc7cec116--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://600b29a0ad07d40dc7cec116--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-labs@7.11.2-alpha.c25b14.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-labs@7.11.2-alpha.c25b14.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://600b2d86ad07d418cdcebe70--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://600b2d86ad07d418cdcebe70--gamut-preview.netlify.appDeploy Logs


Public .tiktoken files available?

The files listed on https://github.com/openai/tiktoken/blob/main/tiktoken_ext/openai_public.py
f.e.
az://openaipublic/gpt-2/encodings/main/encoder.json
az://openaipublic/gpt-2/encodings/main/vocab.bpe
az://openaipublic/encodings/cl100k_base.tiktoken
az://openaipublic/encodings/r50k_base.tiktoken
Are these publically available somewhere? Not familiar with Azure cloud, ended up trying AzCopy, but yet no luck.
I'm starting to wonder if these files are actually public, since going through the repo, it seems they are loaded from local filesystem?
What is the recommended way to get these files?
Really amazing work, and very happy to see it as an open-source contribution with excellent explanations throughout the comments in the code!

Yes, files are public, you can see them like this, and they are accessed like this in the code.
# pip install blobfile

import blobfile
import json

bpe_blobpath = "az://openaipublic/gpt-2/encodings/main/vocab.bpe"
json_blobpath = "az://openaipublic/gpt-2/encodings/main/encoder.json"

with blobfile.BlobFile(bpe_blobpath, "rb") as f:
    bpe_contents = f.read()

with blobfile.BlobFile(json_blobpath, "rb") as f:
    json_contents = json.loads(f.read())

🙏
As said, i believe this brings back some of the Open in OpenAI, in a way, that its "flagship" open-source product — gpt2-tokenizer — will see extended lifetime, and OpenAI, can continue to full the role as "generally accepted" BPE tokenizer.
Nice way to take your own throne, with such huge improvement.
Sure, you all are already following along, but what is the "way to go", about clearing up some stuff, like mentioned on https://brianlovin.com/hn/34008839
Are the issues here, somewhat ok place, to inform about the different tokenizers offered, or how should I go about acquiring more information about them?0

Yup, as abdulbaseet-zahir mentions, the files are public. I'm glad you find this useful :-)
In January, I'll add a way to map from tokenisers to engines available in the OpenAI API. This will make it clearer what a specific tokeniser should be used for.
Issues on this repo are a good place to ask additional questions, but I'm on vacation so you may not get answers until January.

Yes, files are public, you can see them like this, and they are accessed like this in the code.
# pip install blobfile

import blobfile
import json

bpe_blobpath = "az://openaipublic/gpt-2/encodings/main/vocab.bpe"
json_blobpath = "az://openaipublic/gpt-2/encodings/main/encoder.json"

with blobfile.BlobFile(bpe_blobpath, "rb") as f:
    bpe_contents = f.read()

with blobfile.BlobFile(json_blobpath, "rb") as f:
    json_contents = json.loads(f.read())

get error:
blobfile: error message=request failed with exception (<urllib3.connection.HTTPSConnection object at 0x7f243312a0a0>, 'Connection to login.microsoftonline.com timed out. (connect timeout=10)'), request=, status=0, error=None, error_description=None, error_headers=None when executing http request  attempt 0, sleeping for 0.0 seconds before retrying


Figma: Add interactivity to completed components

All components should be ready for prototyping by our users. Set up components as described here: https://help.figma.com/hc/en-us/articles/360061175334-Create-interactive-components-with-variants

solved as part of #501

@Febakke Looks like textField is missing interactivity
https://github.com/digdir/designsystem/assets/1464915/b8efa986-fbb6-4715-a493-2a5bc20bf1c8

Sorry, my mistake, this example was using incorrect component. Fixed now.
https://github.com/digdir/designsystem/assets/1464915/9e8dca0f-a7a6-4d18-b75e-c69f039fd02a


Add  --view-decoded-payload for cosign verify-attestation or similar

Description
For the purpose of easily viewing the decoded attestation in plain text. I feel that there is a pretty heavy use case for doing this. I for one found it slightly confusing when I initially called cosign verify-attestation that it did not decode and present the attestation to me by default.
Especially while the project is in the early stages and people trying to make sense of everything, an easy way to pull down and view the raw decoded payload that you initially pushed to the registry would be very handy.
adding any of:

cosign verify-attestation --view-decoded-payload
cosign verify-attestation --view-payload
cosign view-attestation

or something like it would achieve this.
If this is a feature worth adding, I'd be happy to write a PR 😄

This sounds good to me, I have to admit that I forget what the current output looks like. Would you mind elaborating a bit more on exactly what the change in output would look like (either here or in a PR)?


feat(object): object.put protobuf encoding test

Closes #3

go-ipfs doesn't like the protobuf
Uncaught AssertionError: expected [Error: invalid character 'S' looking for beginning of value] to not exist

I wonder is because it gets stringified to be put on the wire. @whyrusleeping thoughts?

Note that we have tests to match the protobufs generated in JS to the ones in Go, byte by byte. Sharing this so that you don't spend time trying to see if the protobuf is correctly formated.

This PR is correct, the issue was in js-ipfs-api see this PR for a fix: https://github.com/ipfs/js-ipfs-api/pull/272


[BUG] More than one possible candidate for "$x" call

Describe the bug
I think this code has enough information(this) to specify the method. Why not?
Code to reproduce
code:
export namespace Vector2 {
    export namespace Methods {
        export function $asData(v: Vector2): [number, number] {
            return v as unknown as [number, number];
        }

        export function $x(self: Vector2): number {
            return $asData(self)[0];
        }

        export function $y(self: Vector2): number {
            return $asData(self)[1];
        }
    }

    export function $from(x: number, y: number): Vector2 {
        return [x, y] as unknown as Vector2;
    }
}

interface Vector2 {
    $x(): number;
    $y(): number;
}

export namespace Vector3 {
    export namespace Methods {
        export function $asData(v: Vector3): [number, number, number] {
            return v as unknown as [number, number, number];
        }

        export function $x(self: Vector3): number {
            return $asData(self)[0];
        }

        export function $y(self: Vector3): number {
            return $asData(self)[1];
        }
    }

    export function $from(x: number, y: number, z: number): Vector3 {
        return [x, y, z] as unknown as Vector3;
    }
}

interface Vector3 {
    $x(): number;
    $y(): number;
    $z(): number;
}

const v2 = Vector2.$from!(1, 2);
console.log(v2.$x!(), v2.$y!());

error:
src/index.ts:53:13 - error TS8000: More than one possible candidate for "$x" call

53 console.log(v2.$x!(), v2.$y!());

Expected behavior
A clear and concise description of what you expected to happen.
const v2 = [1, 2];
console.log(v2[0], v2[1]);

Additional context
Add any other context about the problem here.

The code currently uses a typescript provided function to compare types and check if they're "assignable" to another. Vector3 is assignable to Vector2 because Vector3 has all the properties Vector2 needs ($x and $y).
You can fix this you can brand the Vector2 type:
interface Vector2 {
    _type: "vector2";
    $x(): number;
    $y(): number;
}

Playground

Thank you!
I think it would be better to include information about this in the document.


Please,make it work with TypeScript

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

This is an awesome package but please add Typescript support, it will be vary handy. Thank in advanced


Fix winrm4j in Karaf

winrm4j version update has fixes for OSGi. Also adding an extension bundle to httpcomponents-asyncclient so that it's able to see org.apache.http.ssl package (that's fixed in later revision releases of the jar).

excellent workaround


Update QUICHE from f18d52057 to 71111c723

https://github.com/google/quiche/compare/f18d52057..71111c723
$ git log f18d52057..71111c723 --date=short --no-merges --format="%ad %al %s"

2024-12-27 martinduke MoQT Upstream FETCH data streams.
2024-12-23 rch Fix a flake in quic_udp_socket_test.cc caused by recvmsg occasionally returning EAGAIN by reading again in this case.
2024-12-20 dschinazi Switch QUIC version negotiation to RFC codepoint
2024-12-19 martinduke Add a new QUIC Connection option to specify Cubic for the client side only.
2024-12-17 dschinazi Fix flakiness in chaos protection test
2024-12-17 martinduke Send MoQT Fetch and handle FETCH_OK/FETCH_ERROR. The application can induce FETCH_CANCEL by destroying the MoqtFetchTask object it owns.
2024-12-16 quiche-dev Declare nfds parameter of PollSyscall() as size_t

/retest

/retest

/lgtm deps


fix Insert init plan error may forget to abrot txn

Proposed changes
When FE generate plan for insert into command:

begin txn and finalize sink
if finalize sink throws exception, the txn is not aborted

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


[WIP] Split mapnik_vector_tile.cpp

Follows-up https://github.com/mapnik/node-mapnik/pull/812.
Will fail to build without https://github.com/mapbox/mapnik-vector-tile/pull/256. I'm not sure what steps to do to get it working.

#946 split files, so I think this is effectively done.


Investigate bringing referencetracking to netstandard2 WinRT.Runtime

Investigate if we can lift the .NET5 implementation of reference tracking and put it into the .netstandard2.0 WinRT.Runtime for our Mono/Unity. Other scenarios this could impact - if WinUI3 allows running on .netnative via xaml islands.

No ask.


In Rank Fragment when user_id == current_user_id then it will show "Me" not "user_name"

In Rank Fragment when user_id == current_user_id then it will show "Me" not "user_name"
Here not show "Amit Maity " show "Me"

I would like to work on this issue under JWOC ✌


Allow passing custom parameters when creating Zip FS

Relates to: https://github.com/quarkusio/quarkus/issues/38128

cc @aloubyansky

Thanks!
Any chance I could get a release tomorrow?

Hopefully, it's released. I had some timeouts from Sonatype and weird log in related errors, let's see whether it ends up on Central.

Thanks a lot!
I'll check tomorrow morning

Looks like it made it https://repo1.maven.org/maven2/io/quarkus/quarkus-fs-util/0.0.10/

👌


Extension not recognizing attachments syntax

Problem
With attachments enabled in emulator v0.47.0, but the extension doesn't support the feature. Not sure whether to label this as bug or enhancement since attachments are a new Cadence feature.
Steps to Reproduce
Define an attachment and see the following error:

Acceptance Criteria
Attachments and related syntax recognized and supported by the extension.
Context
Working on a tutorial covering attachments.

Thank you for reporting. We will tag accordingly.

This is a language server issue and covered in https://github.com/onflow/cadence-tools/pull/118


Enables go to file for module names/imports

Pressing gf on a module name (or import) will go to that file.
module Foo where

import Bar
import Json.Decode

So pressing gf on Bar would go to src/Bar.elm, while doing it on Json.Decode would go to elm-stuff/.../src/Json/Decode.elm
This assumes that source code is in src and that dependencies are installed
in elm-stuff. Ideally we should improve using all paths referenced in package.json, but it's a good baseline.

Excellent, thank you. I will add an issue for the improvement you suggested as well.


PAINT_013 Refactoring for first release

Codebase needs to get refactored for the first release.
Deleting unnecessary imports etc.

Done


Substitute variables in launch configuration keys (and not only in values)

VSCode Version: 1.15.1
OS Version: Win7

Feature description：
It would be nice to use the environment variable $ {env: variable} in launch.json sourceFileMap, like using the built-in variable $ {workspaceRoot}.
The present situation is that we can write $ {env: variable} in sourceFileMap, but it is not replaced by real path like $ {workspaceRoot}.
So, when debugging with cpptools extension for c++ program，vscode pops up the following message box:
Error: Unable to open 'main.cpp': File not found (\usr1\pDTest\demo\main.cpp). Create File Cancel

The sourceFileMap is very simple:
"sourceFileMap": {
    // "remote": "local"

    // This way works well
    // "/usr1/pDTest/demo" : "D:\\demo"

    // This way does not work
    "/usr1/{env:USERNAME}/demo" : "D:\\demo"
},

This feature is useful for collaborative development of multiple programmers. we can push launch.json on git repo, and do not need everyone to modify it.

Yes, currently we are only resolving the values of objects in the configuration, not the keys (which is what you want).
We accept PRs that elegantly fix this, code pointer https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/services/configurationResolver/node/configurationResolverService.ts#L194

@nbstar  I was wondering if you have found a workaround for this?

@isidorn since VS Code's use of JSONs sometimes has values on the left hand side (as keys), we should consequently support variable substitution there too.
I assume this feature is low-hanging fruit?

@weinand should not be too complex

@dbaeumer note that we now also resolve keys not only values in configuraitons since this also affects tasks.

Verified that variables are substitured in both values and keys.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.11 to before v5.15.12",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e4c9062717feda88900b566463228d1c4910af6d",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dfd5b60b5342b6b505a104e48f08ad9b9bdbbd7b"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "e4c9062717feda88900b566463228d1c4910af6d",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "dfd5b60b5342b6b505a104e48f08ad9b9bdbbd7b",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "Input: elantech - fix stack out of bound access in elantech_change_report_id()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.12 by commit dfd5b60b5342b6b505a104e48f08ad9b9bdbbd7b, it was introduced in version v5.11 by commit e4c9062717feda88900b566463228d1c4910af6d. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002829


[BUG] high CPU usage, memory usage

What is the bug?
I get an endless stream of files matching /tmp/sqlite-<IP_ADDRESS>-[UUID]-libsqlitejdbc.so
How can one reproduce the bug?
Start the service like this
services:
    store:
        image: opensearchproject/opensearch:2.7.0
        environment:
            - cluster.name=opensearch
            - node.name=opensearch
            - discovery.type=single-node
            - bootstrap.memory_lock=true
            - knn.memory.circuit_breaker.limit=10%
            - OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m
            - DISABLE_INSTALL_DEMO_CONFIG=true
            - DISABLE_SECURITY_PLUGIN=true
        ulimits:
            memlock:
                soft: -1
                hard: -1
            nofile:
                soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
                hard: 65536
        volumes:
            - store:/usr/share/opensearch/data
        restart: unless-stopped
        tmpfs:
            - /tmp

Since the /tmp is mounted as tmpfs, this consumes huge amounts of RAM and eventually the machine dies.
See this from within the container
sh-4.2$ date; ls -l /tmp/sqlite-<IP_ADDRESS>-*.so | wc -l
Mon May 29 14:01:40 UTC 2023
12270
sh-4.2$ date; ls -l /tmp/sqlite-<IP_ADDRESS>-*.so | wc -l
Mon May 29 14:01:43 UTC 2023
12335
sh-4.2$ date; ls -l /tmp/sqlite-<IP_ADDRESS>-*.so | wc -l
Mon May 29 14:01:45 UTC 2023
12372

What is the expected behavior?
Download it once and use it successfully? Or not download it at all, it should be part of the image? Maybe downloading it works around some licensing?
What is your host/environment?
Fedora Linux 38
Client: Docker Engine - Community
 Version:           24.0.2
 API version:       1.43
 Go version:        go1.20.4
 Git commit:        cb74dfc
 Built:             Thu May 25 21:53:42 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          24.0.2
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.4
  Git commit:       659604f
  Built:            Thu May 25 21:52:08 2023
  OS/Arch:          linux/amd64
  Experimental:     false

 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Do you have any screenshots?
N/A.
Do you have any additional context?
It might be related to performance analyzer since I'm noticing it's using a lot of CPU constantly, maybe that's what's doing it.

Hey @dkarlovi can you add more details?
Have you ever noticed these generated files getting purged?
Do you know on invoking what process triggered creation of these files?

@prudhvigodithi starting the container starts creating the files, they never get cleared. I've went into the container and manually killed performance analyzer (PID 10), that made it stop.

Thanks @dkarlovi just FYI, you can disable the PA Plugin   -e "DISABLE_PERFORMANCE_ANALYZER_AGENT_CLI=true", but ya @khushbr can you please check what should be done to clear the sqlite files?
@bbarani @peterzhuamazon

Hey @dkarlovi closing this issue and the PA discussion can be done on this existing issue.
Thank you


IPC reports error 404 when running in Docker using <IP_ADDRESS>

Bug report
Description
The IPC server does not listen on all hosts provided in IPCPrefixed when running under docker.
Expected behavior
The IPC server shall return a valid response.
Actual behavior
The IPC server reports a "404 Not Found" when I try to access the server using <IP_ADDRESS>:1242.
It only works if I issue the request against the internally used docker ip.
Steps to reproduce
Start the docker container. For curl outputs see below.
Full log.txt recorded during reproducing the problem
2018-05-25 20:02:19|dotnet-14|INFO|ASF|InitASF() ArchiSteamFarm V<IP_ADDRESS> (38143380-211b-4922-80f6-43e5d543c43b)
2018-05-25 20:02:19|dotnet-14|INFO|ASF|Start() Starting IPC server on http://<IP_ADDRESS>:1242/...
2018-05-25 20:02:19|dotnet-14|INFO|ASF|Start() Starting IPC server on http://<IP_ADDRESS>:1242/...
2018-05-25 20:02:19|dotnet-14|INFO|ASF|Start() IPC server ready!
2018-05-25 20:02:19|dotnet-14|INFO|secondary|Start() Starting...
2018-05-25 20:02:19|dotnet-14|INFO|main|Start() Starting...
2018-05-25 20:02:19|dotnet-14|INFO|secondary|Connect() Connecting...
2018-05-25 20:02:20|dotnet-14|INFO|secondary|OnConnected() Connected to Steam!
2018-05-25 20:02:20|dotnet-14|INFO|secondary|OnConnected() Logging in...
2018-05-25 20:02:25|dotnet-14|WARN|ASF|GetUserInput() Received a request for user input, but process is running in headless mode!
2018-05-25 20:02:25|dotnet-14|INFO|secondary|Stop() Stopping...
2018-05-25 20:02:29|dotnet-14|INFO|main|Connect() Connecting...
2018-05-25 20:02:30|dotnet-14|INFO|main|OnConnected() Connected to Steam!
2018-05-25 20:02:30|dotnet-14|WARN|ASF|GetUserInput() Received a request for user input, but process is running in headless mode!
2018-05-25 20:02:30|dotnet-14|INFO|main|Stop() Stopping...

Global ASF.json config
{
  "CurrentCulture": "en-US",
  "s_SteamOwnerID": "<redacted>",
  "Headless": true,
  "IPC": true,
  "IPCPassword": null,
  "IPCPrefixes": [
    "http://<IP_ADDRESS>:1242/",
    "http://<IP_ADDRESS>:1242/"
  ],
  "OptimizationMode": 0,
  "Statistics": true,
  "UpdateChannel": 0
}

BotName.json config of all affected bot instances (if more than one)
-- Does not apply here --
Additional info
Broken request:
lyrex@thor:~$ curl -v -H "Host: <IP_ADDRESS>" http://<IP_ADDRESS>:1242/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 1242 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Content-Type: text/html
< Server: Microsoft-NetCore/2.0
< Date: Fri, 25 May 2018 20:12:55 GMT
< Content-Length: 30
<
* Curl_http_done: called premature == 0
* Connection #0 to host <IP_ADDRESS> left intact

Not Found (Not Found)

Working request:
lyrex@thor:~$ curl -v -H "Host: <IP_ADDRESS>" http://<IP_ADDRESS>:1242/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 1242 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/html
< Access-Control-Allow-Origin: *
< Date: Fri, 25 May 2018 20:14:00 GMT
< Server: Microsoft-NetCore/2.0
< Content-Length: 6962
<
<!DOCTYPE html>

--- snip ---

* Curl_http_done: called premature == 0
* Connection #0 to host <IP_ADDRESS> left intact

Could you include all docker commands that you used for setting up ASF docker container? This includes port forwarding arguments, thanks.

I am currently using docker-compose to handle my docker setup but I also quickly came up with a plain docker start.
docker-compose.yml:
version: "3.3"

services:
  asf:
    image: "justarchi/archisteamfarm:released"
    restart: unless-stopped
    dns: <IP_ADDRESS>
    ports:
      - "<IP_ADDRESS>:1242:1242"
    volumes:
      - ./config:/app/config
      - ./ArchiSteamFarm.runtimeconfig.json:/app/ArchiSteamFarm.runtimeconfig.json:ro
    environment:
    - ASF_ARGS="--process-required"

I just tried to rewrite the same config using plain docker commands. Here is the docker command I am running:
docker run \
    -v /home/lyrex/docker/asf/config:/app/config \
    -v /home/lyrex/docker/asf/ArchiSteamFarm.runtimeconfig.json:/app/ArchiSteamFarm.runtimeconfig.json:ro \
    -p <IP_ADDRESS>:1242:1242 \
    --restart=unless-stopped \
    -e ASF_ARGS="--process-required" \
    --name ArchiSteamFarm \
    -d justarchi/archisteamfarm:released

Plain Docker
Using plain docker we've got a different story. It still is not working but this time the IPC server simply rejects my connection. Here are the curl requests for the plain docker setup:
Request against <IP_ADDRESS> with same host:
lyrex@thor:~$ curl -v -H "Host: <IP_ADDRESS>" http://<IP_ADDRESS>:1242/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 1242 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.52.1
> Accept: */*
>
* Recv failure: Connection reset by peer
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

Request against <IP_ADDRESS> with internal docker ip as host:
lyrex@thor:~$ curl -v -H "Host: <IP_ADDRESS>" http://<IP_ADDRESS>:1242/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 1242 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.52.1
> Accept: */*
>
* Recv failure: Connection reset by peer
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

Request against internal docker ip:
lyrex@thor:~$ curl -v http://<IP_ADDRESS>:1242/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* connect to <IP_ADDRESS> port 1242 failed: Connection refused
* Failed to connect to <IP_ADDRESS> port 1242: Connection refused
* Closing connection 0
curl: (7) Failed to connect to <IP_ADDRESS> port 1242: Connection refused

Worked fine for me when using http://*:1242/ prefix instead, on both <IP_ADDRESS> and <IP_ADDRESS>.
It also worked fine with http://<IP_ADDRESS>:1242/ prefix when querying <IP_ADDRESS>.
https://github.com/JustArchi/ArchiSteamFarm/wiki/Docker#ipc is explicit in this regard:

Assuming you set IPCPrefixes properly to something like http://*:1242/, the above command will make IPC client examples work from the host machine.

Why exactly docker struggles with ASF listening on <IP_ADDRESS> only - no clue, because it works with using nginx as reverse proxy, which shows that there is no issue on ASF side for that. Perhaps it has difficulty of proxying loopback-only internal container interfaces, as the connection never reached the bridge in the first place.
In any case, this is not ASF bug. I recommend setting IPCPrefixes appropriate, either to http://<IP_ADDRESS>:1242/ or http://*:1242/.

BTW, 404 NotFound happens when your Host does not match any of ASF IPCPrefixes. If you have ASF set up like you claim that you do:
  "IPCPrefixes": [
    "http://<IP_ADDRESS>:1242/",
    "http://<IP_ADDRESS>:1242/"
  ],

Then you can reach ASF with Host: <IP_ADDRESS> or Host: <IP_ADDRESS>, regardless of internal docker proxying. Natural way of doing that would be connecting via http://<IP_ADDRESS>:1242 or http://<IP_ADDRESS>:1242, but you could also connect through anything, as long as you supplied proper Host header which indicates which network resource you want to fetch. This is why "magical trick" above mentioned by me still works, even though ASF no longer listens on <IP_ADDRESS> at all.

I don't know if you have seen my curl request examples but I indeed did issue exactly that request.
I got to admit that I have overlooked the option to set * as host. That worked for me now. But it is still strange that the setup I intended did not work (maybe it is a bug but just obscured?).
For reference (same happend without the Host header, with is redundant):
lyrex@thor:~$ curl -v -H "Host: <IP_ADDRESS>" http://<IP_ADDRESS>:1242/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 1242 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Content-Type: text/html
< Server: Microsoft-NetCore/2.0
< Date: Fri, 25 May 2018 20:12:55 GMT
< Content-Length: 30
<
* Curl_http_done: called premature == 0
* Connection #0 to host <IP_ADDRESS> left intact

Not Found (Not Found)
```

In short tl;dr, if you want to access <IP_ADDRESS>:1242 from host machine, then ASF inside docker container has to listen on http://*:1242 because only then <IP_ADDRESS> is accessible through something else than loopback interface.

Yup, got that. Thank you! I will simply go with the wildcard solution. There is a nginx reverse proxy in front of the application anyways so that should not matter too much.
I'm pretty sure too that binding to docker's internal loopback adapter messes something up pretty badly. It's not exactly faking it but rather avoiding it I assume.
The docker NAT rules are forwarding any host <IP_ADDRESS> to the container's ip (if bound). That way the application needs to listen only on the docker ip (like <IP_ADDRESS>) but still accepting host-headers that match <IP_ADDRESS> there. Outside-world traffic can never reach the container on <IP_ADDRESS> since it's all forwarded to its bridge-ip.
Basically if multiple interfaces are defined, the application needs to accept every Prefix-Host on every connection (which sounds pretty messy).

As long as you restrict access yourself, there should be no problem with that. You could also go crazy and set up nginx inside ASF docker container as reverse-proxy to it, as long as nginx doesn't mind receiving <IP_ADDRESS> requests on non-loopback interface. This would potentially work, because nginx would still communicate with ASF through loopback, so ASF could be configured as <IP_ADDRESS> only.
However, this is very silly if you ask me. It's much easier to use *:1242 and just restrict yourself, you have docker for a reason 🙂.


StartOf/EndOf on week leapyear is incorrect

Description of the Issue and Steps to Reproduce:
I've been stuck on an issue all day and just now figured out why it reacted this way.
For some reason when .startOf() is called with 'week' or 'isoWeek' as parameter, it works perfectly fine with non-leap years. With leapyears however, it skips the first week and goes right to the second.
What it should be
moment().week(1).year(2020).startOf('isoWeek').format('DD/MM/YYYY')
moment().week(1).year(2020).endOf('isoWeek').format('DD/MM/YYYY')
30/12/2019
05/01/2020
What it results in however
06/01/2020
12/01/2020
The same is true for startOf('week'), it doesn't give the corresponding week when it comes to leapyears, even though it counts the correct amount of weeks.
So far this happens on every leapyear I've tested (2020, 2016, 2012 etc.), while the non-leaps work fine (2019, 2021, 2018, 2017 etc.).
Environment:
I use Google Chrome (beta) on Apricity OS, the same behaviour appears on Firefox with Ubuntu. A JSFiddle does the same (https://jsfiddle.net/pg1uvtw1/).
I noticed this in a VueJS project, by using the vue-moment library. However this is a MomentJS issue, JSFiddle uses version 2.17.1.
Other information that may be helpful:
The time zone I'm on is CET(Brussels, Belgium)
If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

Output:
Fri Mar 10 2017 16:56:58 GMT+0100 (CET)
10/03/2017, 16:56:58
-60
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.54 Safari/537.36
2.17.1

You're mixing non-ISO week, calendar years, and ISO weeks.  Year like a regular calendar year. Similarly, week() means local week, i.e. dependent on the locale. Here's what you want to say:
> moment().isoWeekYear(2020).isoWeek(1).startOf('isoWeek').format('DD/MM/YYYY')
'30/12/2019'
> moment().isoWeekYear(2020).isoWeek(1).endOf('isoWeek').format('DD/MM/YYYY')
'05/01/2020'

My bad, thanks for the reply.


Update sketches will have large error rate in some cases.

All of update sketch don't deal with duplicate datas.
So in such situation:
val sketch1 = UpdateSketch()
sketch1.update(1)
sketch1.update(1)
sketch2.update(xxx)
val sketch2 = UpdateSketch()
sketch2.update(1)
sketch2.update(xxx)
anotb.update(sketch1, sketch2)
anotb.getResult()

Int this cases, because the number 1 add two times and only remove once, so it should counts in the final result.
But actually it will not. It will cause very large error rate in small data.

This is not correct. Distinct counting sketches will count a value only once. You added it and then removed it, so the value will not be present after the AnotB operation.

Without additional context, these seem to be theta sketches. Those will count each item once, which is why they're distinct counting sketches or cardinality estimation sketches: They tell you how many different elements exist, but nothing about how often any specific element exists. There something of an overview here: http://datasketches.apache.org/docs/Architecture/MajorSketchFamilies.html
There is a Tuple sketch that can hold additional data associated with each element, but there's no default behavior for how those combine. You'd need to define your own summaries to try to create the behavior you want. Keeping in mind that these are probabilistic structure and that you can't expect exact results -- not even for individual elements -- as the data volume grows.


Rasa Webchat waiting for server error showing in website

I am trying to use rasa web chat for my website integration with rasa x bot. But after deploying rasax over GCP it is not working while calling through rasa webchat using socket.io channel. but the bot is working fine when accessing directly through rasa x guest share using direct IP.
I am using below code for integrating rasa web chat in my index.html file
<script<EMAIL_ADDRESS>type="text/javascript"></script>

    <script>
      WebChat.default.init({
        selector: "#webchat",
        initPayload: "/get_started",
        customData: {"language": "en"}, // arbitrary custom data. Stay minimal as this will be added to the socket
        socketUrl: "http://<IP_ADDRESS>",
        socketPath: "/socket.io/",
        profileAvatar: "syra.png",
        openLauncherImage: "syra.png",
        hideWhenNotConnected:false,
        title: "Syra",
        subtitle: "Digital Assistant for Tax Advice",
        params: {"storage": "session"} // can be set to "local"  or "session". details in storage section.
      })
    </script>

In credentials.yml file I have added following code block for socket.io channel
socketio:
  user_message_evt: user_uttered
  bot_message_evt: bot_uttered
  session_persistence: true

I have used docker-compose for deployement over gcp and rasa 2.0

Hi, please I have a question. When you tried the integration locally, were you able to see the conversations users have with your bot through webchat in Rasa X conversations' history ? I can't find them anywhere.

I integrated Rasa with socket.io but it is showing this error
Traceback (most recent call last):
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\socketio\asyncio_server.py", line 473, in _handle_event_internal
r = await server._trigger_event(data[0], namespace, sid, *data[1:])
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\socketio\asyncio_server.py", line 501, in _trigger_event
ret = await self.handlers[namespace]event
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\socketio.py", line 217, in handle_message
await on_new_message(message)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\channel.py", line 85, in handler
await app.agent.handle_message(*args, **kwargs)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\agent.py", line 522, in handle_message
return await processor.handle_message(message)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 98, in handle_message
await self._predict_and_execute_next_action(message.output_channel, tracker)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 566, in _predict_and_execute_next_action
action, tracker, output_channel, self.nlg, policy, confidence
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 701, in _run_action
await self.execute_side_effects(events, tracker, output_channel)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 605, in execute_side_effects
await self._send_bot_messages(events, tracker, output_channel)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 621, in _send_bot_messages
await output_channel.send_response(tracker.sender_id, e.message())
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\channel.py", line 183, in send_response
recipient_id, message.pop("text"), message.pop("buttons"), **message
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\socketio.py", line 77, in send_text_with_buttons
"payload": button["payload"],
KeyError: 'payload'

I integrated Rasa with socket.io but it is showing this error
Traceback (most recent call last):
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\socketio\asyncio_server.py", line 473, in _handle_event_internal
r = await server._trigger_event(data[0], namespace, sid, *data[1:])
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\socketio\asyncio_server.py", line 501, in _trigger_event
ret = await self.handlers[namespace]event
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\socketio.py", line 217, in handle_message
await on_new_message(message)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\channel.py", line 85, in handler
await app.agent.handle_message(*args, **kwargs)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\agent.py", line 522, in handle_message
return await processor.handle_message(message)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 98, in handle_message
await self._predict_and_execute_next_action(message.output_channel, tracker)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 566, in _predict_and_execute_next_action
action, tracker, output_channel, self.nlg, policy, confidence
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 701, in _run_action
await self.execute_side_effects(events, tracker, output_channel)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 605, in execute_side_effects
await self._send_bot_messages(events, tracker, output_channel)
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\processor.py", line 621, in _send_bot_messages
await output_channel.send_response(tracker.sender_id, e.message())
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\channel.py", line 183, in send_response
recipient_id, message.pop("text"), message.pop("buttons"), **message
File "c:\users\siddhartha\anaconda3\envs\installingrasa\lib\site-packages\rasa\core\channels\socketio.py", line 77, in send_text_with_buttons
"payload": button["payload"],
KeyError: 'payload'

Problem is half solved. Actually in my welcome message some button base responses are there which will trigger some actions but rasa web chat is not supporting buttons that why it showing error of payload. But when I am asking some other question it is working fine. is there any workaround for payloads?

Problem is half solved. Actually in my welcome message some button base responses are there which will trigger some actions but rasa web chat is not supporting buttons that why it showing error of payload. But when I am asking some other question it is working fine. is there any workaround for payloads?

The problem is resolved. There was a syntax error in payload part. Now working fine

The problem is resolved. There was a syntax error in payload part. Now working fine

how did you solves ,please give steps


kbfuse 4.0.5

[x] build and upload the Installer
[x] merge https://github.com/keybase/fuse/pull/3 and update the vendor hash here
[x] implement proper error handling in bazil/fuse (https://github.com/keybase/fuse/pull/4) and update vendor here
[x] fix helper

I tried to build from this branch (my first time building Keybase from source), ran into an issue in the pod install command. Full error report is at /keybase/public/jms1/notes/keybase-build-error.txt, but the the relevant error message is...
LoadError - dlopen(/Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi_c.bundle, 0x0009): missing compatible arch in /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi_c.bundle - /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi_c.bundle

I've heard the term "Cocoa Pods" before but I know nothing about it (most of my programming for the past 5+ years has been Linux server stuff, in Perl and Puppet, but I've been programming in C for ... almost 34 years now? (I feel so old when I say that...)
Hopefully this will turn out to be a known issue, I haven't stared reading through the three possible github matches yet, I'll dig into that tomorrow. Feel free to reach out on Keybase chat if needed.

Is this likely to come back at any point? I see it was reverted. Understand it's not really a supported product any more, don't want to add any pressure :)

Is this likely to come back at any point? I see it was reverted. Understand it's not really a supported product any more, don't want to add any pressure :)


Updated Bukkit download URL https://getbukkit.org/get/

Describe the problem
My docker container is not starting due to not being able to download the jar file from download.getbukkit.org. It looks like they have migrated to https://getbukkit.org/get/. Here are the applicable logs.
Container logs
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x. 9 1000 1000 4096 Jul 31  2022 /data'

[init] Resolved version given 1.19 into 1.19

[init] Resolving type given SPIGOT

[init] Downloading Spigot from https://download.getbukkit.org/spigot/spigot-1.19.jar ...

curl: (22) The requested URL returned error: 523

Workaround
I was able to get round this issue by switching from TYPE=SPIGOT to TYPE=CUSTOM and using CUSTOM_SERVER=/data/spigot_server-1.19.jar
https://github.com/itzg/docker-minecraft-server/blob/2507028193d10806e751a99bea016e3be3e64264/scripts/start-deployBukkitSpigot#L71

Thanks for investigating. That would be great if you could PR that change.

No problem at all. I can investigate also, but yes my initial suspicion is that they have been down lately. Some users have been getting 523 error pages lately, which means their backend is down.
I would suggest switching to PaperMC which is plugin compatible and has much better support.

I had a similar problem and report it just in case.
Consider using PaperMC.
      - env:
        - name: TYPE
          value: SPIGOT
        - name: VERSION
          value: "1.19.4"
        - name: EULA
          value: "true"
        image: itzg/minecraft-server:java8

log
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwsrwx 2 1000 1000 90 Dec  8 10:58 /data'
[init] Resolving type given SPIGOT
[init] Downloading Spigot from https://download.getbukkit.org/spigot/spigot-1.19.4.jar ...
curl: (22) The requested URL returned error: 522

Yep response of 522 means it's a problem with getbukkit website. All the more reason to switch to Paper.

I think the download site is working again and this issue can be closed.

it gives error code 522


benchmark application can ignore error codes in API

Description

Type: Bug
Priority: Major

The benchmark program runs the API in a MACRO TIME_AND_TSC in a loop, for performance check. The return code of the function is assigned to ret in https://github.com/ARMmbed/mbedtls/blob/development/programs/test/benchmark.c#L130 and in https://github.com/ARMmbed/mbedtls/blob/development/programs/test/benchmark.c#L136 , however, it continues to next iteration of the loop. If for some reason the next iteration succeeds, the error code is dismissed.
It should either break the loop, or accumulate the error code using OR bitwise operation.

closing, as I missed the condition in the loop ret == 0
not a bug


docker-machine don't start VM

@mattetti

Probably the same as #986. As far as I can understand, this has been fixed in the master branch.

@efrecon
I watched in virtualbox, while the docker-machine stood on this screen (I sent in the screenshot). The virtualbox has a preview area where you can watch what is going on in the virtual machine. And in a moment, the distro (boot2docker) completes the boot process and is expecting login and password. Maybe this can help.

I have the same issue, but it is not related to #986.
It is caused by 9bf78124733d4bd15a90d7aead80046a568b3cf2 (because the build from the previous commit, 74de38d97fb02af6c4e83378093cbd88ee3bd1d4, works fine)
Look at the part of debug log (reproduced on 9bf78124733d4bd15a90d7aead80046a568b3cf2):
$ docker-machine create -d virtualbox b2d-vbox2 --debug
<...>
Using SSH client type: external
About to run SSH command:
sudo /etc/init.d/docker start
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -t -i /Users/legal/.docker/machine/machines/b2d-vbox2/id_rsa -p 57837 docker@localhost sudo /etc/init.d/docker start] []  <nil> <nil> <nil> [] <nil> <nil> <nil> ?reflect.Value? false [] [] [] [] <nil>}
SSH cmd err, output: <nil>: hostname: b2d-vbox2: Resolver internal error
Need TLS certs for b2d-vbox2,,<IP_ADDRESS>,<IP_ADDRESS>
-------------------

Daemon not responding yet: dial tcp <IP_ADDRESS>:2376: connection refused
Daemon not responding yet: dial tcp <IP_ADDRESS>:2376: connection refused
Daemon not responding yet: dial tcp <IP_ADDRESS>:2376: connection refused
Daemon not responding yet: dial tcp <IP_ADDRESS>:2376: connection refused
<...>
Error creating machine: Maximum number of retries (60) exceeded
You will want to check the provider to make sure the machine and associated resources were properly removed.

Actually, vm is created and we can access it by ssh, but sudo netstat -anp | grep 23 returns nothing, which means that docker daemon is not running. We can run it manually:
docker@b2d-vbox2:$ sudo /etc/init.d/docker start
hostname: b2d-vbox2: Resolver internal error
Need TLS certs for b2d-vbox2,,<IP_ADDRESS>,<IP_ADDRESS>
-------------------

docker@b2d-vbox2:~$ sudo netstat -anp | grep 23
tcp        0      0 :::2376                 :::*                    LISTEN      1682/docker

cc:/ @efrecon

Then I have no idea, you will have to wait for some more knowledgeable people from docker to look into this.

@ehazlett Could you please take look at this? Seems like it is caused by #1090

Yes taking a look.

It is the tty allocation in the ssh command needed for redhat provisioning. We are working on a fix.


Additional optimizations for the GPU usage of smoke

These changes significantly reduce the GPU usage of smoke on my computer. The idea is rather simple: instead of scheduling compute for the whole window and then filtering out the border region only, directly schedule computes for each rectangle of the border.
The second commit improves the situation a little bit more by scheduling all rectangles in parallel.

Thanks!


Trying to run from source, "Error: Cannot find module './linux'"

I can't install deb (seriously, you say it's a "linux" build, but it's just for debian).
So I downloaded the release tar and after some dicking around with npm I think it downloaded all dependencies.
I also created a world-writable folder in /var/local/GPMDP_STORE because it for some strange reason wanted it. Seriously. ~/.cache is not good enough?
Anyway, when I try to run it, it gives me an error:
~/downloads/Google-Play-Music-Desktop-Player-UNOFFICIAL--3.0.0 $ npm start

><EMAIL_ADDRESS>start /home/ondra/downloads/Google-Play-Music-Desktop-Player-UNOFFICIAL--3.0.0
> electron .

####################################
############### ERROR ##############
######### LASTFM  API KEYS #########
######## HAVE NOT BEEN SET #########
#####################################
{ [Error: Cannot find module './linux'] code: 'MODULE_NOT_FOUND' }

How do I get this ./linux module?

nvm got it running with clone, no idea why the release didn't work.
I didn't realize this is just a chrome tab in it's own window.
Also heavy CPU usage. Was worth a try though.


Add fuzz tests

Fixes Issue

Fixes #
Changes proposed

Screenshots (Optional)
Note to reviewers

@anupsv why did we never merge this? Do you want to rebase so we can merge? Hopefully its not too gnarly

@anupsv why did we never merge this? Do you want to rebase so we can merge? Hopefully its not too gnarly

That's a good question. Idk why we didn't merge it. I'll rebase and merge.


feat(alchemy-signer): migrate the alchemy signer to use bundle from QP

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
This PR enhances the Alchemy Signer module by adding temporary session storage for email authentication and refactoring authentication logic.
Detailed summary

Added setTemporarySession and getTemporarySession methods in SessionManager
Modified authenticateWithEmail method in AlchemySigner to handle temporary sessions for email authentication

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

https://github.com/alchemyplatform/aa-sdk/assets/4642570/6ca22193-8b65-47b4-b3c0-c8c83d46a12f


console.tag() nesting tags in different Modules

Hi guys,
I'm using the tag function as follows:
var scribe = require('scribe-js')();
var console = process.console;
var console = console.tag("MainModule").file();
console.log("Hi mom!");

In another module i'm using:
var console = process.console;
var console = console.tag("SecondaryModule").file();
console.log("Hi dad!");

However, when my second message appears, it appears as:
[MainModule] [SecondaryModule] Hi dad!

Is there something I'm doing wrong? Can I modify the tag function to return a clone of the console, instead of the console itself?

Why don't you have done something like this ?
//main.js
require('scribe-js');
var console = process.console;

console.tag("MainModule").file().log("Hi !');

//module.js
var console = process.console;
console.tag("Module").file().log("Hi dad !");

Actually, each time your using tag, 'file, etc. methods, this return an instance of the console with properties where the args you passed to tag("MainModule"), by example, are stored. This properties are reset only after a logger call (ie. .log("something"), debug`, etc.)

If you want to use default tags or default file logs for each logger call, you can : https://github.com/bluejamesbond/Scribe.js/wiki/4-·-API-%3A-Console2#console2opt

Yes, I know. However, in my project I put a tag related to the module in which this log event occured. Therefore, for each module, I'd like to have a special tag on it. Since I have a lot of logs, I wouldn't like to change the whole code, inserting .tag() on each log event. What I did was clone the Console2 object on each module, and then update my cloned console with the desired tag for that module.
I thought that It'd be good to have this feature on console2 object instead of implementing this on every module. I know that there is a memory consumption issue there, but perhaps use as default your implementation and, if a certain flag or configuration is present, returns a clone of the console object when I request the process.console object.

Ok so I see.
Maybe you should try to not create the default console, but one console for each module and use defaut tags.
//main.js
var scribe = require('../scribe')({
    createDefaultConsole : false //Scribe won't attach a fresh console2 to process.console
});

var console = scribe.console({
    console : {                                      //Default options for all myConfigConsole loggers
        colors     : 'white',
        alwaysLocation : true,
        defaultTags : ["MainModule"]
    },
    createBasic : true                             //Create basic loggers
});

console.log("Hi mom!");  // [MainModule] [main.js:1]             Hi mom!

//module.js
var scribe = require('../scribe')({
    createDefaultConsole : false
});

var console = scribe.console({
    console : {
        colors     : 'white',
        alwaysLocation : true,
        defaultTags : ["SecondModule"]
    },
    createBasic : true
});

console.log("Hi dad!");  // [SecondModule] [mdule.js:1]             Hi dad!

See also this example : https://github.com/bluejamesbond/Scribe.js/blob/master/examples/run_with_config.js

Ok @guillaumewuip
Thanks a lot man! I'll use it as you suggested.

Just one thing that I forgot to mention. Thanks a lot for refactoring this module. The 1.x one was good, but this new version is much better :)

Hi Guillaume.
The suggested solution caused a conflict regarding the folder in which each console will write. The thrown error is
throw new Error('Folder ' + this.rootPath + ' already in use')
Error: Folder logs already in use

Is there a way to solve it? does it exist to avoid a conflict writing in the same file?

Oh, I forgot to mention the LogWriter config. As there is one log folder for one console, you should give another folder for the second one.
//module.js
var scribe = require('../scribe')({
    createDefaultConsole : false
});

var console = scribe.console({
    console : {
        colors     : 'white',
        alwaysLocation : true,
        defaultTags : ["SecondModule"]
    },
    createBasic : true,
    logWriter : {
        rootPath : 'logsConsoleOne' //all logs in ./logsConsoleOne
    }
});

console.log("Hi dad!");  // [SecondModule] [mdule.js:1]             Hi dad!

Normally the webPanel will show you the 2 folder in the sidebar.

@guillaumewuip , thanks again for your response. I really don't want to be picky, but I didn't want to have multiple log files to the same date for the same type of log ("log", "info", etc...). One thing I thought was to develop a Semaphore to write in the log files. Do you think it will work? Therefore, it would control file access, and enable two or more consoles to write in the same folder, keeping the logs together. If you think it's fine but don't have time, I could implement that.

@joaobrunoah The reason @guillaumewuip and I decided to do that was because people use different types of logs for different reasons. For instance, in my apps I have a stream for large data just for the sake of keeping track, while other streams are used for short quick logging usually used for debugging. With the large variances in file size depending on the type of log, we noticed that combining the outputs of the two logs would be hinder the a developer who wants to quickly access debug data. Since loading we are loading "one" file we are loading all the content all the data at once. So, we split them up in order to be able to select any log you want to view. If you want just the small debug log, just load that up meanwhile if you want to load the large data log, you can do that as well. And in event you want to view the two together, the Scribe web-interface provides that feature as well. @guillaumewuip 's LogWriter module is in essence a "semaphore". I would highly recommend modifying his module and enabling single file output as an option that people can enable/disable as they wish.

Yes in fact, it's simply a condition that prevent the multiple console / one log folder case.
I've push an pull request #37 without it. It seems to work.
By the way, I'm not totally that the LogWriter is a good semaphore. I once found corrupted history.json file without understanding why.

@joaobrunoah @guillaumewuip I apologize. Tt seems as if I misunderstood your question. I am glad a solution was found.

@guillaumewuip  thanks for the solution


Flextype API's and Plugins refactoring

To go forward - code and structure need to be refactored for upcoming Flextype 0.9.7!

Review pds/skeleton and implement some parts of  https://github.com/php-pds/skeleton
Review possibility of migration to Slim4 or Flextype will continue powered by Slim3 in 2020. Seems like some other good solutions also powered by Slim3 and it is still okey for them... We should use more Symfony components and in the future possible 100% migrate to Symfony. No Laravel! - it is great! but not for simple apps. imho.
Prepare Flextype codebase for HeadLess! CoreAPI + RestAPI
...

We should keep it simple and straightforward!

moved to 1.0.0


build: Update Vulkan-Headers and VUL to 1.3.272

CI Vulkan-ExtensionLayer build queued with queue ID 94891.

CI Vulkan-ExtensionLayer build # 812 running.

CI Vulkan-ExtensionLayer build # 812 passed.


panic: "Write called after handler finished"

conn.Write() causes a panic when the handler function has exited:
panic write called after handler finished

Can we add a check into
https://github.com/posener/h2conn/blob/13e7df33ed1548e5902d1b32bd6b5906cce194f5/server.go#L72
to make sure our conn.Write() returns an error  (instead of causing a panic) when the conn is not usable?

Looking a bit deeper into the panic text, originally from h2_bundle.go
I'm guessing that you are running the code that writes and reads from the conn in a goroutine that writes to the connection after the ServeHTTP function returns. This is not allowed, and not required, since the ServeHTTP itself is running in a goroutine.
If you could provide a code example in which you get this error, I could help you fix it.

Yes this can be prevented by checking the handler state, but I was thinking that sometimes we might actually do things like:

running the code that writes and reads from the conn in a goroutine that writes to the connection after the ServeHTTP function returns
The reason is that we are using Conn.Write() in another goroutine, it can be inconvenient to check if the handler has finished. So I thought returning an error is better than causing a panic.

Maybe, it's better to add another property to h2conn.Conn? I think Conn.IsOpen() might be a good idea (probably more code).
The current code will work fine if we check the Context of the handler, but still, I think it's better to implement something that handles this in the library.

Sorry, this sounds like a misuse of the http2 library.
Having the IsOpen function will still not prevent race-conditions, since you are running in a different goroutine.
Writing a handler that uses the connection should be done carfully. If you are running goroutines, you should wait for all of them to finish before the handler returns, you can use sync.WaitGroup for that.
We can add documentation that clarifies this issue to the README if you want.

What if we add a Context to type Conn?
https://github.com/posener/h2conn/blob/13e7df33ed1548e5902d1b32bd6b5906cce194f5/conn.go#L12-L29

Sorry, but I don't understand what you are trying to fix.
Can you provide an example of a handler that causes this panic?

Sorry, but I don't understand what you are trying to fix.
No, I was trying to solve the panic at first, but as you explained there's nothing to fix, I think there's still a thing that might be helpful to users

Usually when you see a panic in Go, it because you did something wrong. Try looking at the error and understand how you misused the code.
I'm closing this one, you are still open to contribute to the README to avoid confusion for others! :-)
Thanks!

I totally understand.

What if we add a Context to type Conn?

This seems irrelevant though, but it can be helpful for users to decide if the Conn is already done
 func newConn(ctx context.Context, r io.Reader, wc io.WriteCloser) (*Conn, context.Context) {
 	ctx, cancel := context.WithCancel(ctx)
 	return &Conn{
 		r:      r,
 		wc:     wc,
 		cancel: cancel,
                ctx: ctx, // add Context
 	}, ctx
 }