concatenate for a nonzero axis operation

address Issue https://github.com/scikit-hep/awkward-1.0/issues/184

Hi @ianna, any progress on this? (I'm asking because it's been 20 days; maybe you haven't pushed local changes.) Thanks!

It would be cool to see this implemented, an axis=1 concatenate would be super slick for some analysis work

@jpivarski - yes, with broadcast_and_apply the arrays must be equal length. What's the best approach here? Padding them with Nones and then dropping the Nones after the concatenate operation works.
[[0.0, 1.1, 2.2], [], [3.3, 4.4], [5.5], [6.6, 7.7, 8.8, 9.9], None, None]
[[1.1, 2.2], [3.3], [], [4.4, 5.5], [6.6, 7.7, 8.8], [], [9.9]]

Actually, users should not be allowed to concatenate arrays with axis > 0 if their lengths differ. After all, if we want to concatenate
[[1, 2, 3], [], [4, 5]]   and   [["a", "b"], ["c"], ["d", "e", "f"]]

at axis=1, that means we want
[[1, 2, 3, "a", "b"], ["c"], [4, 5, "d", "e", "f"]]

This operation wouldn't make any sense if the two arrays we want to concatenate have different lengths.
Concatenation at axis=0 is qualitatively different: the input arrays can have any lengths at all. But for all other axis values, the lengths have to be the same. For axis > 1, the lengths have to be the same at several depths, but broadcast_and_apply ensures that as well, either through error messages or broadcasting, if possible.

tests/test_0397-arrays-as-constants-in-numba.py::test_refcount FAILED

https://dev.azure.com/jpivarski/Scikit-HEP/_build/results?buildId=4560&view=logs&j=81547bd0-3aa9-547f-25e1-12509e21f92a&t=6f2c7081-a276-5c13-1bbf-f0639c0526de&l=509

@jpivarski - please, have a look when you can. Thanks!

tests/test_0397-arrays-as-constants-in-numba.py::test_refcount FAILED

https://dev.azure.com/jpivarski/Scikit-HEP/_build/results?buildId=4560&view=logs&j=81547bd0-3aa9-547f-25e1-12509e21f92a&t=6f2c7081-a276-5c13-1bbf-f0639c0526de&l=509

That one failure is disturbing, since it seems to have nothing to do with your changes. I'm rerunning it and running another test on master, though it's not necessarily a good sign if those pass. (Even worse than an inexplicable error is an intermittent inexplicable error.)

tests/test_0397-arrays-as-constants-in-numba.py::test_refcount FAILED

https://dev.azure.com/jpivarski/Scikit-HEP/_build/results?buildId=4560&view=logs&j=81547bd0-3aa9-547f-25e1-12509e21f92a&t=6f2c7081-a276-5c13-1bbf-f0639c0526de&l=509

That one failure is disturbing, since it seems to have nothing to do with your changes. I'm rerunning it and running another test on master, though it's not necessarily a good sign if those pass. (Even worse than an inexplicable error is an intermittent inexplicable error.)

A run on the master branch produced no errors: https://dev.azure.com/jpivarski/Scikit-HEP/_build/results?buildId=4573&view=results while retrying this branch reproduced the error: https://dev.azure.com/jpivarski/Scikit-HEP/_build/results?buildId=4571&view=logs&j=f72a8481-bd91-5d06-6025-0e453ddcac08&t=0b1b15ad-cf24-5193-0114-2bb1bf897da3, which makes me feel a little better because it's not intermittent. But it also means that somewhere in this PR, there's something that affects reference counting in Numba on Windows. (!?!) I'll pore through the diffs to see if anything looks suspicious.

Is this branch up-to-date with master? Maybe something old is causing the Windows 32-bit Numba error.
I've run tests on master twice with no such error, but it seems like it appears in every test on this branch. Even if its probability is 1/2, the always-on-this-branch and never-on-master is somewhat improbable.

#495 does some cross-checks on your kernel-specifications.yml, and that has been merged to master. If you update again, you'll get this cross-checker to see if your newly added kernels match specifications.

@jpivarski - the branch is up-to-date. Judging by the tests - it looks like the error was introduced in the https://github.com/scikit-hep/awkward-1.0/pull/361/commits/74fb429799996cbe123b9715aec1550ce892af13 commit. I've reverted the changes to both src/libawkward/Content.cpp and src/python/content.cpp. It's unlikely that changes in the tests/test_0184-concatenate-operation.py caused it, so it must be due to src/awkward1/operations/structure.py.

@jpivarski - The tests/test_0397-arrays-as-constants-in-numba.py is SKIPPED on the following architectures due to it's minimum requirement of Python version, I guess:

Windows py27-32bit
Windows py27-64bit
Windows py35-64bit
Windows py39-32bit
Windows py39-64bit
MacOS py27
MacOS py35
MacOS py39
Linux py27-np13
Linux py27-np16
Linux py35-np13
Linux py39-np*

I have installed numba locally and when I run on a recent clean master, all the tests including the above one run fine:
% python localbuild.py --pytest tests
...
tests/test_0397-arrays-as-constants-in-numba.py::test_refcount PASSED                                                                                [ 90%]
tests/test_0397-arrays-as-constants-in-numba.py::test_Array PASSED                                                                                [ 91%]
tests/test_0397-arrays-as-constants-in-numba.py::test_Record PASSED                                                                                [ 91%]
tests/test_0397-arrays-as-constants-in-numba.py::test_ArrayBuilder PASSED                                                                                [ 91%]

However, if I try to rerun the test, all four fail.

You're right that the restrictions on testing with Numba are based on Python version and platform constraints. Numba doesn't support Python 2 anymore (our minimal Numba version doesn't), and it doesn't support Python 3.9 yet. Supporting a new version of Python is difficult for Numba because it directly uses the Python bytecode, which changes from one minor version to the next.
For these particular errors, it looks like Awkward's Numba extensions have not been registered. This happens through Python's "entry points" mechanism, which might only be enabled with a full package installation. That is, you'd need to install Awkward with pip or conda (it can be pip install . in your awkward-1.0 repo directory) just to get the entry point registered, then the version in the localbuild directory would override it if you invoke Python from awkward-1.0, as you have been.
If that makes the difference, I'll make a note of it in the CONTRIBUTING.md.

Ha. All checks passed ;-)

The warning is a good thing—I've deprecated a feature and wanted to make sure that users will see that message, so I added it to the tests. It's also a reminder to remove the feature in version 1.0.
I was going to suggest bisecting to find what's causing the Windows bug, but you beat me to it.
It would be bad if the Windows bug only happens because the garbage collector runs—delaying the garbage collector is not a fix, it only indicates that the bug is hidden in other systems. But I've already checked for this bug by explicitly invoking the garbage collector (on Linux). I don't think we need to worry about that possibility.

The warning is a good thing—I've deprecated a feature and wanted to make sure that users will see that message, so I added it to the tests. It's also a reminder to remove the feature in version 1.0.
I was going to suggest bisecting to find what's causing the Windows bug, but you beat me to it.
It would be bad if the Windows bug only happens because the garbage collector runs—delaying the garbage collector is not a fix, it only indicates that the bug is hidden in other systems. But I've already checked for this bug by explicitly invoking the garbage collector (on Linux). I don't think we need to worry about that possibility.

The numbers and records are not mergeable. They can be merged as a union in axis=0 whilst in axis>0 broadcast_and_apply will not accept this union due to its different length from the other arrays.

The numbers and records are intentionally not mergeable (except "as union"). But the second set, which has the same lengths, should be concatenateable with axis > 0 ("as union").

@reikdas - could you, please, have a look with a fresh eye? Why and where does the PR defines tests-cpu-kernels/test_cpuawkward_RegularArray_merge_offsets64.py? I think, I've deleted it a while back. Thanks!

@reikdas - could you, please, have a look with a fresh eye? Why and where does the PR defines tests-cpu-kernels/test_cpuawkward_RegularArray_merge_offsets64.py? I think, I've deleted it a while back. Thanks!

I see that there are some commits after this comment and that tests are passing. Is the issue fixed?

@reikdas - could you, please, have a look with a fresh eye? Why and where does the PR defines tests-cpu-kernels/test_cpuawkward_RegularArray_merge_offsets64.py? I think, I've deleted it a while back. Thanks!

I see that there are some commits after this comment and that tests are passing. Is the issue fixed?

No, I just squashed the last three commits. I've no idea why it all works now.  Maybe there were some auto generated files that were not removed?
(Even if that is not the culprit, @jpivarski maybe we should include a script in dev/ to clean up all auto generated files, apart from the ones that are checked into git like the kernel headers, so that one can start from a clean slate?)

(Even if that is not the culprit, @jpivarski maybe we should include a script in dev/ to clean up all auto generated files, apart from the ones that are checked into git like the kernel headers, so that one can start from a clean slate?)

That's a good idea, though these generated files are not in the tests directory, which is where the failing test was.


Fixed broken links getting_started

Those links are not broken. You have to look at them after site generation has run. The files in this repo is just the source.


[Draft] Hapigen output for NI SCOPE

What does this Pull Request accomplish?
Testing hapigen generated data from PR
Why should this Pull Request be merged?
Just showing diffs
What testing has been done?
Local builds show generated proto file looks about right

Newer Draft PR here for hapigen-exported NI Scope metadata: https://github.com/ni/grpc-device/pull/760
Marking this one closed.


.from doesn't initialize right away

Fantastic engine! Feels like home coming from TweenMax. :+1:
I discovered a small bug. If you have a delay .from waits for the delay before it sets the .from values.
Example (sliding in a label):
Kinetic.from(title, duration: 1, options: [.X(-title.bounds.width)]).spring(tension: 70, friction: 15).delay(0.5).play()

Work around:
title.text = ""
Kinetic.from(title, duration: 1, options: [.X(-title.bounds.width)]).spring(tension: 70, friction: 15).delay(0.5).play().onStart { (tween) -> Void in
    self.title.text = "My Title!"
}

@markuswinkler Thanks for the feedback!
Looking at how TweenMax works by default for TweenMax.from, it does indeed set the starting value immediately even if there's a delay for the tween, so I'll make that fix in my library as well as you suggested. TweenMax supports an immediateRender parameter to not set the starting properties until the tween actually starts, but that's probably less often the desired effect: http://greensock.com/docs/#/HTML5/GSAP/TweenMax/from/

Great!
Btw, I think your version number of 0.1.0 is ridiculously low. Your library seems very mature and very well done (including great documentation), that's more like a 1.1.0.

Yeah I agree it's probably too low and will be updated to at least 0.9.0 in my next release. I'd like to do more in-depth performance testing on it before marking it as an official 1.0.0 over the next week or so.

Fixed in 0.9.0 I just pushed out.


Fixing Health Check to Work w/ EVMConnect

Signed-off-by: hfuss<EMAIL_ADDRESS>

Closing in favor of https://github.com/hyperledger/firefly-evmconnect/pull/30/


First Time Running Problem, After First Signup

I installed project on server, I migrated db on sql lite
I started on server and i created new user, after signup operation,
I had this error,
NoMethodError in Home#index
Showing /usr/lib/ruby/gems/1.8/gems/social_stream-0.0.5/app/views/home/_groups.html.erb where line #1 raised:
undefined method `where' for []:Array
ActionView::Template::Error (undefined method `where' for []:Array):
<% if current_user.recent_groups.any? %>

   <%=t('group.other') %>

Hi, omeryavuz. It seems you are running social_stream version 0.0.5
Current social stream version is 0.12.3
Please, run bundle update


fix: SqlAzureDacpacDeployment renamed to V1 on GH

Think some stuff got lost in the folder rename and rebase from your private repo, so this partially re-does #841

@nschonni Thank you, I am merging this and it should be live soon.


[BUG] - DecoderFailure of burning token TX

External
Area
Tx submission
Summary
In our system we construct a burning TX using Cardano Serialisation Lib (CSL) on a browser frontend and then send it serialised as CBOR to our backend where we deserialise it, do some validation and then submit it to our local node. This has been working perfectly fine for a long time now, but recently we ran into very strange DecoderFailure errors with 2 such burning TXs, when we submitted them:
DecoderFailure (LocalTxSubmission (GenTx (HardForkBlock (': * ByronBlock (': * (ShelleyBlock (TPraos StandardCrypto) (ShelleyEra StandardCrypto)) (': * (ShelleyBlock (TPraos StandardCrypto) (AllegraEra StandardCrypto)) (': * (ShelleyBlock (TPraos StandardCrypto) (MaryEra StandardCrypto)) (': * (ShelleyBlock (TPraos StandardCrypto) (AlonzoEra StandardCrypto)) (': * (ShelleyBlock (Praos StandardCrypto) (BabbageEra StandardCrypto)) (': * (ShelleyBlock (Praos StandardCrypto) (ConwayEra StandardCrypto)) ('[] *)))))))))) (HardForkApplyTxErr (': * ByronBlock (': * (ShelleyBlock (TPraos StandardCrypto) (ShelleyEra StandardCrypto)) (': * (ShelleyBlock (TPraos StandardCrypto) (AllegraEra StandardCrypto)) (': * (ShelleyBlock (TPraos StandardCrypto) (MaryEra StandardCrypto)) (': * (ShelleyBlock (TPraos StandardCrypto) (AlonzoEra StandardCrypto)) (': * (ShelleyBlock (Praos StandardCrypto) (BabbageEra StandardCrypto)) (': * (ShelleyBlock (Praos StandardCrypto) (ConwayEra StandardCrypto)) ('[] *)))))))))) ServerAgency TokBusy) (DeserialiseFailure 191 \"expected word\")"

We are using CSL 11.5.0 and Cardano Node 8.9.1 with cardano-api <IP_ADDRESS>.
We decoded the TXs both with cardano-cli as well as CSL but we could not find anything suspicious - we have the CBORs of the 2 TXs attached.
3c6def41927725728b20a13dcd9b195c4e8adc45e656eb7d31c1f91220ef1d45_cbor.txt
b373fc4e57ef514e5169fcc3709d25b26713b7f2e87136d2bdb856d487d5ade4_cbor.txt

Is this issue still happening with latest node and cardano-api?


Fix type checking custom primitives

It looks like in #176 there was a slight regression that breaks rules that use custom primitives that are not present in the default TypeInfo.
This issue is blocking upgrading the Python bindings to recent commits (https://github.com/metadsl/egglog-python/pull/42) because we use a custom PyObjectSort.
The underlying problem introduced is that the desugaring pass checks (in normalize_expr) if a function is primitive by creating a default TypeInfo and using that, instead of using the TypeInfo associated with the current graph:
I am not sure how to resolve this.

That's a problem! Thanks for pointing it out.
The solution is that the desugaring pass needs access to the egraph's actual typeinfo, which is kind of annoying.
Two potential fixes:

put the type info in the desugar struct from the beginning, and everything refers to it instead of the "proof context"
pass the type info along all of the relevant methods in desugaring.

I think I prefer solution 1, unless anyone has a better solution
Anyways, totally reasonable if you don't feel like fixing this one @saulshanabrook

So you would up to make TypeInfo a member of the Desugar struct?

Yep!


Graph on gravity page rendering issue

If the angles are not entered in order the graph is not correct, need to sort data for graph based on angle

Sort data using this function,
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort


Add appropriate docstring for plotting functions

[ ] Remove layout initial docstring added by Chris in components.py (Chris)
[ ] Add function docstring to all plotting functions in Numpy style. ( Michelle, Jenn , Thea )
[ ] Could add one line docstring for layout functions. (Chris and whoever wants to help :P )

I have updated mine: plot-4.


Express Request/Response bodies

Hi!
I want to generate an openapi spec file from my code and this package looks like what I need. But it does not seem to work (yet). It does not detect the request and response bodies properly.
import { NextFunction, Request, Response, Router } from "express";
import { CreateRequestBody } from "../../../types/request";
import { CreateResponseBody } from "../../../types/response";

const router = Router();

router.post(
  "/create",
  async (req: Request<{}, {}, CreateRequestBody>, res: Response<CreateResponseBody>, next: NextFunction) => {
    // Create code
  }
);

I am using the config as described in Usage basic
I am doing something wrong or need more configuration? Or is this not (yet) supported? (I tried the search, but don't really know what to search for)

Hi @Arjan-Zuidema. Thank you for opening the issue.
Unfortunately the lib doesn't support this kind of code yet, but it's in my TODO list to handle it. There is an issue opened about this (#175), so any news about it I'll post there. Because of this I'll close this issue. But thank you for the code, I'll use it to help me when I'm handling the problem.


Incompatible change in patch version breaks downstream/ users of k3s

Environmental Info:
K3s Version:
v1.27.16+k3s1
Node(s) CPU architecture, OS, and Version: Multiple, tested on the following:
Linux node 6.5.0-44-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jun 18 14:36:16 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Linux node 4.18.0-553.8.1.el8_10.x86_64 #1 SMP Tue Jul 2 05:18:08 PDT 2024 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
1 server
Describe the bug:
#10500 introduces changes which requires downstream packages e.g., k3d to adapt to new k3s behavior. For example, k3d 5.7.2 works with k3s versions <=1.27.15 and 1.28.1 but not 1.27.16!
Since semantically newer versions oscillate between old and new behavior (1.27.15 -> 1.27.16 -> 1.28.10 -> 1.28.12 -> 1.29.4 -> ...) this is very confusing for users on the upgrade path of k3s.
Steps To Reproduce:
One way to reproduce is to use k3s docker image to setup a cluster using k3d. This fails since the behavior has changed between v1.27.15 and v1.27.16
$ curl -L https://github.com/k3d-io/k3d/releases/download/v5.7.2/k3d-linux-amd64 -o k3d && chmod a+x k3d
$ ./k3d version
k3d version v5.7.2
k3s version v1.29.6-k3s2 (default)
$ ./k3d cluster create test --kubeconfig-update-default=0 --image rancher/k3s:v1.27.15-k3s2 --wait --timeout=240s --no-lb --network test
$ # works as expected
...
$ ./k3d cluster create test --kubeconfig-update-default=0 --image rancher/k3s:v1.27.16-k3s1 --wait --timeout=240s --no-lb --network test
$ # fails to start cluster
...
$ ./k3d cluster create test --kubeconfig-update-default=0 --image rancher/k3s:v1.28.1-k3s1 --wait --timeout=240s --no-lb --network test
$ # works as expected, as also  rancher/k3s:v1.28.11-k3s1 and versions in between, but not 1.28.12!

Installed K3s:

Expected behavior:
Patch versions don't break compatibility or introduce behavioral changes. In other words the following command should be successful (since the same command with 1.27.15 is):
$ ./k3d cluster create test --kubeconfig-update-default=0 --image rancher/k3s:v1.27.16-k3s1 --wait --timeout=240s --no-lb --network test

Actual behavior:
See steps to reproduce above.
Additional context / logs:
It may be possible for k3d to document, for each k3s minor version, the list of patch versions supported by each version of k3d (suggested here). Nevertheless, this change breaks other scripts that use busybox etc. In general these type of changes are expected with minor releases but not with patch versions.

Indeed I only wrote what I encountered and not why it happenned. Thanks for the analysis and pin-pointing the cause. The issue was intended as feedback on the "usability improvement" resulting from the change.

I occasionally need to remind myself:


License fun times (use in browserify)

Now that Node ships with unflagged bigint support, I'd like to add this plugin to acorn-node, used by browserify. As I understand the AGPL, simply using it in acorn-node would require acorn-node and browserify to have a compatible license, but they are both MIT. Specifically what I need for acorn-node is to ship a transpiled version of acorn-bigint in-tree, so that it works on all browserify's supported platforms (all the way back to Node 0.8). I saw you relicensed the import-meta plugin under AGPL / Apache, which would seem to allow this use case. Would you be open to doing the same here?

I changed the license to MIT in 613f74c4b75c8263bba75fb4c469a60add24d300 (released in 0.3.0).


captain.exception.ParseError: no main function found

$ transcribe speech test.wav
Traceback (most recent call last):
  File "/usr/local/bin/transcribe", line 10, in <module>
    sys.exit(console())
  File "/usr/local/lib/python3.7/site-packages/captain/__init__.py", line 102, in exit
    s = Script(inspect.getfile(calling_mod), module=calling_mod)
  File "/usr/local/lib/python3.7/site-packages/captain/__init__.py", line 209, in __init__
    self.parse()
  File "/usr/local/lib/python3.7/site-packages/captain/__init__.py", line 324, in parse
    raise ParseError("no main function found")
captain.exception.ParseError: no main function found

can you pip freeze and give me the version of captain that's installed? I think I know the problem and that will help me verify. Thanks

yep, using captain==2.0.4

I wasn't able to duplicate this using transcribe 0.0.3 and captain 2.0.4, make sure you're running the latest:
$ transcribe --version

If you aren't, then update it:
$ pip install --upgrade transcribe

If that doesn't work let me know and I'll install it completely clean room and see if I can duplicate the issue instead of relying on my development environment

I'm indeed running 0.0.3, although transcribe --version crashes:
$ transcribe --version
Traceback (most recent call last):
  File "/usr/local/bin/transcribe", line 10, in <module>
    sys.exit(console())
  File "/usr/local/lib/python3.7/site-packages/captain/__init__.py", line 102, in exit
    s = Script(inspect.getfile(calling_mod), module=calling_mod)
  File "/usr/local/lib/python3.7/site-packages/captain/__init__.py", line 209, in __init__
    self.parse()
  File "/usr/local/lib/python3.7/site-packages/captain/__init__.py", line 324, in parse
    raise ParseError("no main function found")
captain.exception.ParseError: no main function found
$ pip3 install --upgrade transcribe
Requirement already up-to-date: transcribe in /usr/local/lib/python3.7/site-packages (0.0.3)

aight, it's got to be an issue with the installation then, I'm going to spin up a vagrant box and see if I can duplicate

What OS are you using?
I brought up a new ubuntu bionic vagrant box and ran this:
$ sudo su
$ apt-get install
$ apt-get install -y --no-install-recommends python3-pip python3-setuptools
$ pip3 install --upgrade "git+https://github.com/Jaymon/transcribe#egg=transcribe"
$ transcribe --version
transcribe 0.0.4

So it worked as expected.
I did update the setup.py file because it was way out of date, so version 0.0.4 is now in Github and on pypi

Mac OS 10.13.6 - I updated to 0.0.4 with the same issue

Boom! I've been able to duplicate it with a virtual environment on my Mac, not sure why it's different, debugging it now

Gah, I thought I had a bandaid fix that would get transcribe working temporarily while I figured out the issue with captain but, sadly, it didn't work, so now it's going to take some time, in the meantime, just cloning the repo and running it like:
$ python3 -m transcribe speech test.wav

should work since it should bypass the problem with captain.

Hi Jaymon,, I was able to run the transcribe command for mp3 to speech conversion - hitting the GC. But how do I see the transcript file or the how do I read the speech? Please let me know. Thanks !

@ShruAnanth you should open a new issue asking for help, in that issue you should add the full command you ran and the output it produced. Thanks

@kraftydevil ok, this problem, and a whole bunch of others when running in python 3, should be fixed, you can update:
$ pip install --upgrade transcribe
$ pip install --upgrade captain

and it should work.
Thanks for your help tracking this down :)

Yep, I'm now able to run transcribe from the command line 👍 I found something else while trying speech so I'll post that in a new issue


The use of this grunt-plugin is huge... But I need help.;

Duplicate of https://github.com/FWeinb/grunt-svgstore/issues/116


Getting TypeError: send() got an unexpected keyword argument 'timeout' trying simple tasks

I get send() got an unexpected keyword argument 'timeout' messages when trying to patch or list resources, but this might affect other things.
Possible cause
This behaviour started today and might be related to the latest httpx release 0.20.0.
Steps to reproduce
This happens after installing the lightkube pypi package, letting pip solve dependencies.
$ pip install lightkube --no-cache

Then try listing nodes
Python 3.8.10 (default, Sep 28 2021, 16:10:42)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from lightkube import Client
>>> from lightkube.resources.core_v1 import Node
>>> client = Client()
>>> for node in client.list(Node):
...     print(node.metadata.name)
...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.8/dist-packages/lightkube/core/generic_client.py", line 239, in list
    resp = self.send(req)
  File "/usr/local/lib/python3.8/dist-packages/lightkube/core/generic_client.py", line 204, in send
    return self._client.send(req, stream=stream, timeout=self._watch_timeout if stream else None)
TypeError: send() got an unexpected keyword argument 'timeout'

Workaround
I workaround this issue downgrading to 0.18.1.
My setup
Ubuntu 20.04
Python 3.8.10
pip 21.3
microk8s 1.21/stable

It should be now fixed in 0.8.1


Move to an org

This should be in any of:

multiformats
ipfs-shipyard
ipfs
protocol

Lmk which and i'll move it

After conversation with @lidel I created https://github.com/dnslink-std and invited you as an owner.

note to self: I think we may solve #11 by moving  + setting up http://fleek.co/

Done! https://github.com/dnslink-std/dnslink-website


Add TestCase.init_many usage to test-suite doc page

Linked issue(s):
What change does this PR introduce and why?
Please check if the PR fulfills these requirements

[ ] Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Relevant tests for the changes have been added
[ ] Relevant docs have been added / updated

As an aside, I wonder if we should update our examples to use init_many purely for perf reasons.


Label snapping to connectors

In drawing network diagrams, it's often helpful to have labels at the ends of a connectors, and sometimes in the middle, too.  Here is an example using draw.io to demonstrate the general idea:

However, when the connector is moved, the labels do not remain aligned with the connector at the initial intersecting point:

This is in contrast to yEd, which allows labels to actually snap to the connectors and remain aligned when moved:

yEd offers three default points that labels can be snapped too, even offset from the path of the connector itself:

It would be wonderful to have such label snapping in draw.io, as well. Thank you.

Try setting all values except "Left" to 0 in the Edit Geometry dialog (Ctrl/Cmd+Shift+M) and use center/middle alignment for the label. This will position the center of the label along the edge, where Left is a value from -1 to 1 (start to end).

Thanks @alderg! It would be nice if there were some pre-existing snap points, but this is a helpful work around for now.


Implement particle for wind in world

The wind particle should randomly be played in the world to show the wind direction and intensity.

We dont have the wind particles, but I improved the UI for it.

Moving to blocked as the particle is not behaving how I would expect it to. Someone else is welcome to take a crack at it.

https://github.com/apetavern/sbox-grubs/commit/5fa6b86d475401e4089e41edd0e9073ce717c6fd


Serve the vite+react frontend from b6.

Serve the vite+react frontend from the b6 backend binary, integrating it into the continuous build. The new (which I'm naming v2) frontend bundle is served alongside the existing frontend, via a new /v2.html entrypoint.
In passing, correct the error returned for missing files from MergedFilesystem, so that the server returns a 404, and not 500.

Good idea about storybook. I'll add that in another PR.


docs: add how you can run / test changes on a forked react-native through RNTester

A small note/addition on how to now easily run react-native (from source) and test changes. With a link to the RNTester readme.

Fixed the lint issue (removing the word easily).


Skip PU blocks with full replicas but not present in DBS

Fixes #8993
I have never seen this happening in production, it happened to my testbed node today after cloning a production request and migrating the PU dataset from prod to integration DBS server.
Anyways, this change will make sure the block is skipped from the pileupconf.json file if a block contains complete replicas but it does not contain any data in DBS.

I'm not sure we'll ever have this case in production, but it won't hurt to have that try/except block either.
Tested in my VM, merging it.


Is that fair to compare with BLIP2 which freeze the image encoder in the Stage 1 and Stage 2

Hi, the idea of this paper is quite interesting, thanks.
One concern is that BLIP2 freezes the image encoder in the Stage 1 and Stage 2, but your model doesn't. Given this, is the comparison fair?

Thank you for your interest!
We freeze ViT as well (surly), see here. Also, if ViT is not froze, we can not train with such large batch size without gradient checkpointing and unfreeze ViT will make the pre-training (impractically) very long.
I need to apologize we did not include the snowflake sign for ViT in our Figure 1 and 2, which probably leads to your confusion?

Thanks. Yes, Figure 1&2 triggers this question.


Cargo is not excluding target/ directories from MacOS time machine

Problem
Seems to be the same as #7189. Cargo no longer marks target/, or any subdirectories, as excluded from time machine backups. This causes lots of backup bloat!
Steps

Run cargo new my-cool-project
Run cargo build my-cool-project
Run tmutil isexcluded target/ and see that it says the target/ directory is included in backups.

Possible Solution(s)
The current implementation seems too fragile, as it's broken before and it's broken now. Simply setting the com.apple.metadata:com_apple_backup_excludeItem xattr on the directory is enough, rather than invoking an Objective-C framework method.
Notes
Output of cargo version: cargo 1.37.0 (9edd08916 2019-08-02)
Latest MacOS.

CC @alexcrichton - sorry for the notification, but I saw you worked on this in #7189.

It was fixed in 1.38, did you try that version?

I feel so stupid, I'm sorry. I thought that it was fixed in 1.37. Confirmed it works as expected in 1.38.0.


rclpy: 0.6.3-1 in 'crystal/distribution.yaml' [bloom]

Increasing version of package(s) in repository rclpy to 0.6.3-1:

upstream repository: https://github.com/ros2/rclpy.git
release repository: https://github.com/ros2-gbp/rclpy-release.git
distro file: crystal/distribution.yaml
bloom version: 0.7.2
previous version for package: 0.6.2-0

rclpy
* Backport Python Actions (#282 <https://github.com/ros2/rclpy/issues/282>)
  * Add Action Client (#262 <https://github.com/ros2/rclpy/issues/262>)
  * Add rclpy_action module
  * Implement action client
  * Move common conversion function and typedefs to shared header file (impl/common.h)
  * Add tests using mock action server
  * Add action module for aggregating action related submodules
  * Extend Waitable API so executors are aware of Futures
  * Move check_for_type_support() to its own module
  * Fix Executor not executing tasks if there are no ready entities in the wait set (#272 <https://github.com/ros2/rclpy/issues/272>)
  * Fix Node's reference to executor (#275 <https://github.com/ros2/rclpy/issues/275>)
  * Abstract type conversions into functions (#269 <https://github.com/ros2/rclpy/issues/269>)
  * Abstract type conversions into functions
  * Move common C functions to a shared library 'rclpy_common'
  * Add ActionServer (#270 <https://github.com/ros2/rclpy/issues/270>)
  * Add Action server functions to extension module
  * Separated service related macros into separate request and response calls
  * Add server goal handle functions to extension module
  * Update Action extension module to use conversion functions
  * Add implementation of Python ActionServer
  * Handles goal and cancel requests, responds, and calls user-defined functions for executing goals.
  * Handle result requests
  * Handle expired goals
  * Publish goal status array and feedback
  * Add handle_accepted_callback to ActionServer
  * Enable test using MultiThreadedExecutor (#280 <https://github.com/ros2/rclpy/issues/280>)
  * Guard against failed take when taking action messages (#281 <https://github.com/ros2/rclpy/issues/281>)
* Contributors: Jacob Perron

Holding for core ROS 2 releases.


[CCI] Update dependencies

Description
Reopening https://github.com/opensearch-project/oui/pull/609.
Upgrading dependencies that do not cause breaking changes and do not make changes to the code.
Discovery/analysis can be found here https://github.com/opensearch-project/oui/issues/594#issuecomment-1479716230.
Issues Resolved
https://github.com/opensearch-project/oui/issues/594
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[X] All tests pass

[X] yarn lint
[X] yarn test-unit

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@andreymyssak sorry we got to this so late. Do you mind updating this PR to resolve the conflicts?

@ashwin-pc I'll update it soon, thanks for mentioning that.

Some package.json conflict resolutions needed, then we can merge.


Made before and after "html-processing" events use callback value

Hi @jantimon,
I came up with this simple solution to satisfy both needs.
This approach:

keep backwards compatibility
offer a new api to deal with html-webpack-plugin-(before|after)-html-processing

You’re right!
--
Andrea Ascari
dev @ buildo
ph<PHONE_NUMBER>
ma<EMAIL_ADDRESS>gh	github.com/ascariandrea
in	linkedin.com/ascariandrea
pi<PHONE_NUMBER>1
Sent with Airmail
On 26 September 2016 at 13:48:44, Jan Nicklas<EMAIL_ADDRESS>wrote:
@jantimon commented on this pull request.
In index.js:

@@ -138,8 +138,8 @@ HtmlWebpackPlugin.prototype.apply = function (compiler) {
.then(function (html) {
var pluginArgs = {html: html, assets: assets, plugin: self, outputName: self.childCompilationOutputName};
return applyPluginsAsyncWaterfall('html-webpack-plugin-before-html-processing', pluginArgs)

     .then(function () {

       return pluginArgs.html;

     .then(function (newPluginArgs) {

       return newPluginArgs && newPluginArgs.html || pluginArgs.html;

No if you would explicitly return an empty string it would fallback to the pluginArgs (strange use case but still a unexpected behaviour)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I turned out all the declared events mutate the object the plugin uses to generate html.
Are you agree in refactor all those methods?

Maybe we could move it out to a helper which provides the promified applyPluginsAsyncWaterfall helper:
https://github.com/ampedandwired/html-webpack-plugin/blob/9757d3df30653fe52dcc06766322300ca2649615/index.js#L66

I added an helper to merge passed pluginArgs object with the object returned from promise, refactor the logic with this new helper and added tests.
I kept old commits just for reference, but I'm going to delete them if you approve the new changes :)

Just added a test and it fails:
https://github.com/ampedandwired/html-webpack-plugin/tree/ascariandrea-return-updated-html-on-after-html-processing

Yep, but it has to fail.
Cause in the docs says:

Note that the callback must be passed the htmlPluginData in order to pass this onto any other plugins listening on the same 'html-webpack-plugin-before-html-processing' event.

But if you want the this changes to be breaking we can make the returned value mandatory.

Otherwise it would not allow two different modules to work together right?

Yes
https://github.com/webpack/tapable#applypluginsasyncwaterfall

@jantimon any updates?

Still not sure what todo - maybe we could deprecate the usage without a return value first.

The current behaviour is not breaking, so it could be merged without problem.
Then you can schedule the breaking change by removing the backward compatibility.

@ascariandrea I think that's a good idea - could you please add the (hopefull last two changes) ?

@jantimon I've added the warning and fixed the tests!


UPSTREAM: : assign shard names to objects

This PR applies a shard name to objects.
This is necessary because we don't store the shard name in the objects in the db.
Instead, we need to derive it from the storage key, and then applied after retrieving the object from storage.
Assigning the names is required to:

enable the watch-cache for the cache server
instruct the internal kube-controllers how to construct the final URL

nit: if we use some struct here to hold our options, I think the rebase cost might be smaller - WDYT?

I can try to open a new PR for it

question: do you need to store the RV of the object on the owning shard here?

not now but in the future, I think it will be needed.

/lgtm
/approve

https://github.com/kcp-dev/kcp/issues/342


Deprecate old RPC StateReader in favor of starknet_api compatible one, support SiR execution

Deprecate old RPC StateReader in favor of starknet_api compatible one, support SiR execution
Description
This PR deprecates the old RPC StateReader implementation and adds support for executing transactions using starknet_in_rust, making it possible to test both SiR and blockifier executions in the same test for easy comparison and debugging.

Codecov Report

Merging #967 (7dcc455) into FromStarknetApi (160b82d) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head 7dcc455 differs from pull request most recent head edd9fd6. Consider uploading reports for the commit edd9fd6 to get more accurate results

@@                 Coverage Diff                 @@
##           FromStarknetApi     #967      +/-   ##
===================================================
- Coverage            90.13%   90.13%   -0.01%
===================================================
  Files                   54       54
  Lines                13706    13701       -5
===================================================
- Hits                 12354    12349       -5
  Misses                1352     1352

Files Changed
Coverage Δ

.../api/contract_classes/deprecated_contract_class.rs
82.62% <100.00%> (-0.29%)
:arrow_down:

Codecov Report

Merging #967 (ce4060b) into main (303a8d1) will increase coverage by 0.00%.
The diff coverage is 60.00%.

@@           Coverage Diff           @@
##             main     #967   +/-   ##
=======================================
  Coverage   90.50%   90.51%
=======================================
  Files          54       54
  Lines       13794    13787    -7
=======================================
- Hits        12484    12479    -5
+ Misses       1310     1308    -2

Files Changed
Coverage Δ

src/transaction/invoke_function.rs
96.28% <60.00%> (+0.15%)
:arrow_up:


Use of .data is deprecated in tidyselect

Example of specific message:
Warning: Use of .data in tidyselect expressions was deprecated in tidyselect 1.2.0.
ℹ Please use `"cex"` instead of `.data$cex`

Need to make updates throughout the package. See the warning message for the fix, and here for more context

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://github.com/Jostino/RimWorld-it/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


Set bins in the TH1

Hi Linev,
Is it possible to set the bins in the TH1. Example(10 bins from 10-100)

Hi,
There is example which shows how histograms can be created and filled:
http://jsroot.gsi.de/dev/demo/example_tooltip.htm
More examples you can find here:
http://jsroot.gsi.de/dev/api.htm
Regards,
Sergey

Is it possible to change the size of the bin?
The bin size is 1. I would like for example(the values of x from 0-10  will be in the same bin in the histogram in this case bin size is 10)

Hi,
After you create histogram, just set:
histo.fXaxis.fXmin = your_xmin; histo.fXaxis.fXmax = your_xmax;
Regards,
Sergey

I hope problem is clarified and can be close.


Functions outside of the event loop segfault on LLVM

Continuing from #494:
Description
The following (already quite minimised [!]) program is supposed to:

read a file
split it into lines
for each line, tell me the positions of the first and last occurrences of a given digit in the line

The program somewhat heavily uses strings and I/O, and acts wildly differently between the JS and the LLVM backends:
The buggy program
import io/files
import io/error
import io

def processLine(line: String) = {
    println(line)
    val numbers: List[Int] = [1, 2, 3, 4, 5, 6, 7, 8, 9]
    numbers.foreach { n =>
      val numberStr = n.show
      val firstSeen = line.indexOf(numberStr)
      val lastSeen = line.lastIndexOf(numberStr)
      println("n: " ++ n.show ++ " ('" ++ numberStr ++ "') is seen: first: " ++ firstSeen.show ++ " & last: " ++ lastSeen.show)
    }
}

def processAll(lines: String) = {
  lines.split("\n").foreach { line => processLine(line) }
}

def main() = {
  // this crashes, but if you move it inside the `eventloop`, it works fine!
  processAll("kjrqmzv9mmtxhgvsevenhvq7\nfour2tszbgmxpbvninebxns6nineqbqzgjpmpqr")

  eventloop(box {
    with on[IOError].panic;
    with filesystem;

    val contents = do readFile("tiny.input")
    processAll(contents)
  })
}

where tiny.input is just
kjrqmzv9mmtxhgvsevenhvq7
four2tszbgmxpbvninebxns6nineqbqzgjpmpqr

On the JS backend, everything just works :)
On the LLVM backend, I get a hard crash with exit code 134.
kjrqmzv9mmtxhgvsevenhvq7
n: 1 ('1') is seen: first: None() & last: None()
n: 2 ('2') is seen: first: None() & last: None()
n: 3 ('3') is seen: first: None() & last: None()
n: 4 ('4') is seen: first: None() & last: None()
n: 5 ('5') is seen: first: None() & last: None()
n: 6 ('6') is seen: first: None() & last: None()
n: 7 ('7') is seen: first: Some(23) & last: Some(23)
n: 8 ('8') is seen: first: None() & last: None()
n: 9 ('9') is seen: first: Some(7) & last: Some(7)
four2tszbgmxpbvninebxns6nineqbqzgjpmpqr
n: 1 ('1') is seen: first: None() & last: None()
n: 2 ('2') is seen: first: Some(4) & last: Some(4)
n: 3 ('3') is seen: first: None() & last: None()
n: 4 ('4') is seen: first: None() & last: None()
n: 5 ('5') is seen: first: None() & last: None()
n: 6 ('6') is seen: first: Some(23) & last: Some(23)
n: 7 ('7') is seen: first: None() & last: None()
n: 8 ('8') is seen: first: None() & last: None()
n: 9 ('9') is seen: first: None() & last: None()
[error] Process exited with non-zero exit code 134.

Investigated a bit closer, here's the sanitiser trace:

 🔍 Sanitiser output
repro(11106,0x100d18580) malloc: nano zone abandoned due to inability to preallocate reserved vm space.
[...]
=================================================================
==10874==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x619000000080 in thread T0
    #0 0x1033592c0 in wrap_free+0x90 (libclang_rt.asan_osx_dynamic.dylib:arm64+0x4d2c0) (BuildId: 7615c595d022355bb91dd63f44086bc832000000200000000100000000000b00)
    #1 0x102eed76c in topLevel+0x38 (repro:arm64+0x10000976c) (BuildId: 59fdb92c81573573a0ba6a4222172fd232000000200000000100000000000b00)
    #2 0x10305feb4 in uv_run+0x25c (libuv.1.dylib:arm64+0x7eb4) (BuildId: 208160f0746f3fb2a43dfcdb736ed89c32000000200000000100000000000b00)
    #3 0x102eefdc0 in k_300+0x1c (repro:arm64+0x10000bdc0) (BuildId: 59fdb92c81573573a0ba6a4222172fd232000000200000000100000000000b00)
    #4 0x10325d088 in start+0x204 (dyld:arm64+0x5088) (BuildId: 38ee9fe9b66d30668c5c6ddf0d6944c632000000200000000100000000060c00)
    #5 0x2d157ffffffffffc  (<unknown module>)

Address 0x619000000080 is a wild pointer inside of access range of size 0x000000000001.
SUMMARY: AddressSanitizer: bad-free (libclang_rt.asan_osx_dynamic.dylib:arm64+0x4d2c0) (BuildId: 7615c595d022355bb91dd63f44086bc832000000200000000100000000000b00) in wrap_free+0x90
==10874==ABORTING

where k_300 is:
define fastcc void @k_300(%Env %env, %Sp %sp) {
    entry:
        %x_8415p_301 = getelementptr {%Pos}, %Env %env, i64 0, i32 0
        %x_8415 = load %Pos, ptr %x_8415p_301
        %x_8414 = call %Pos @start_3001()
        %x_8413 = call %Pos @stop_3002()
        %tmp411540_6285p_302 = getelementptr {%Pos}, %Env %env, i64 0, i32 0
        store %Pos %x_8413, ptr %tmp411540_6285p_302
        %sp_304 = getelementptr %FrameHeader, %Sp %sp, i64 -1
        %retadrp_305 = getelementptr %FrameHeader, %Sp %sp_304, i64 0, i32 0
        %f_303 = load %RetAdr, ptr %retadrp_305
        tail call fastcc void %f_303(%Env %env, %Sp %sp_304)
        ret void
}

# OPT:
define fastcc void @k_300(ptr %env, ptr %sp) {
entry:
  %loop.i = tail call ptr @uv_default_loop()
  %run_result.i = tail call i32 @uv_run(ptr %loop.i, i32 0)
  %loop.i2 = tail call ptr @uv_default_loop()
  tail call void @uv_stop(ptr %loop.i2)
  tail call void @uv_loop_close(ptr %loop.i2)
  %sp_304 = getelementptr %FrameHeader, ptr %sp, i64 -1
  tail call void @llvm.memset.p0.i64(ptr noundef nonnull align 8 dereferenceable(16) %env, i8 0, i64 16, i1 false)
  %f_303 = load ptr, ptr %sp_304, align 8
  tail call fastcc void %f_303(ptr nonnull %env, ptr nonnull %sp_304)
  ret void
}

This case is called 3. in #494, see more details there https://github.com/effekt-lang/effekt/issues/494#issuecomment-2155885536

Should be resolved by #553, which disallows code outside of the event loop.


I Can't get the code to run

Hi I am new to Node.js but i cannot get the code to run
C:\Users\pat2echo\node_modules\convert-excel-to-json>node app.js
C:\Users\pat2echo\node_modules\convert-excel-to-json\app.js:5
#!/usr/bin/env node
^
SyntaxError: Unexpected token ILLEGAL
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:134:18)
at node.js:962:3
C:\Users\pat2echo\node_modules\convert-excel-to-json>

SOLVED:
I simple watched this tutorial https://www.youtube.com/watch?v=MSCtnotXKdo
Then i thought to comment out the line in the app.js file that
Initial entry
#!/usr/bin/env node
Final Correct Entry
//#!/usr/bin/env node

Hey @pat2echo, as you are new to Node.js tell me what are you trying to do so i can try to guide you. node app.js is not the way to go. You should install this package and require it on your project. Take a look at this tutorial: https://www.airpair.com/javascript/node-js-tutorial

Thank you very much
On Fri, Jan 13, 2017 at 12:42 AM, Diego ZoracKy<EMAIL_ADDRESS>wrote:

Hey @pat2echo https://github.com/pat2echo, as you are new to Node.js
tell me what are you trying to do so i can try to guide you. node app.js
is not the way to go. You should install this package and require it on
your project. Take a look at this tutorial: https://www.airpair.com/
javascript/node-js-tutorial
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DiegoZoracKy/convert-excel-to-json/issues/1#issuecomment-272319450,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF54L87-Vu8NzpDOQkWgwI6h0moEGRjXks5rRrpSgaJpZM4LfqOS
.

--
MAYBEACH TECHNOLOGIES LIMITED
No 42 Lobito Crescent Wuse 2, Abuja
You can also check us out on:
https://twitter.com/MaybeachTech
https://twitter.com/MaybeachTechhttps://www.facebook.com/maybeachtech?fref=ts
https://www.facebook.com/maybeachtech?fref=tshttps://plus.google.com/+Maybeachtechnology/posts
https://plus.google.com/+Maybeachtechnology/posts


Investigate tests marked with @pytest.mark.needsllm

When working on https://github.com/wise-agents/wise-agents/pull/162 I was not able to get some of the tests to pass on GitHub Actions where we are not able to install the LLM due to space constraints.
I excluded some tests there by adding the @pytest.mark.needsllm marker.
It isn't totally clear to me in ALL cases whether an LLM is actually needed or not by the test, so it would be great to verify if this is possible.
Another thing could be to investigate if there is a 'mini LLM' that could work in GH Actions.

Using Groq might be a good option for these tests.

Dublicate #195


Update banner styling to make more prominent

Updates banner to extend across screen and gives it the gradient border to make more prominent.

@aaronkao  and @sean1588 - reviewed and approved on my end. Let's ship! Thank you for the fast turnaround.


[wip] feat(proxy-wasm) host-managed property getters and setters using the Lua bridge

Closed in favor of #431


IRC connections can be orphaned in public mode

Slight bug I just ran into: when in public mode, if the user closes the page while a server is reconnecting, that server will be kept alive in the background with no way to attach back to it.

@maxpoulin64, was this fixed by the recent changes on connections/clients?

I believe this was fixed with move to irc-framework.


Enlarge execution latency threshold for decoding one frame

This is not good. In sample_defs.h there is a hardcoded macro. Instead of explicit modification of this macro you modify place where it's used. Why?

Fixed

@aobolensk , please check what's wrong with CI


The misuse of 'type' and 'key' in photo.py fix (#46, #49)

@jmathai, I have added your suggestion in #46 to pull request (

 You should sign our Contributor License Agreement in order to get your pull request merged.

@zserg I rebased your changes thinking Github would automatically link it to this PR but I guess it doesn't because the commit hashes changed. Nonetheless your changes are merged. Sorry if that caused issues for your fork but in the future I'll request the PR owner to do the rebase :).
Thanks again. :+1:


Improve naming in get_events test

E.g. for the case of event_address_1: Instead of adding numeric suffixes, we would find out what the address represents and have it reflected in the variable name.

Also, handle continuation token bug. Continuation token should be only increased when there are events but now it's increasing even for 0 events.

@mikiw Make a new issue for that

sure, https://github.com/Shard-Labs/starknet-devnet/issues/317


Add IsScrollInertiaEnabled attached property to scrollviewer

What does the pull request do?
Add IsScrollInertiaEnabled property to ScrollViewer, allowing inertial scrolling to be enabled/disabled. It's enabled by default.
What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[x] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0029037-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0029059-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Fixing optional template parameter declaration.

Note that it looks like the convention is to comment each of the params:
https://cs.corp.google.com/search/?q={@param?&m=100&sq=package:piper+file://depot/google3+-file:google3/experimental&type=cs

Note that it looks like the convention is to comment each of the params:
https://cs.corp.google.com/search/?q={@param?&m=100&sq=package:piper+file://depot/google3+-file:google3/experimental&type=cs

While not necessarily required by style guide, comments are nice. I'll add them back in.

Looks good. I've done a survey of the Soy files and found no other cases where we have optional arguments. Can you convert the rest of the calls to match this new format?

Will do in follow up.


[Feature]: Operator has full control over the service account used to run stateful sets

Blockers/Dependencies
No response
Background
See the proposal
As an operator
I want full control over the service account used to run stateful sets
So that choose whether to use a particular image pull secret
Or choose to associate the service account with an IAM role
We require a new helm value to specify a service account name for running stateful set pods in the statefulset-runner component.
When this value is empty, helm will create a service account. The name is arbitrary. But this name needs to be set in the statefulset-runner config map. It will then be used to set the serviceAccount value in the template of the statefulset.
In this case we also require a new helm value containing the name of a secret to be used to pull the droplet image for the statefulset pods. This value should be inserted in the service account's imagePullSecrets property.
When the service account name value is not empty, this means the operator will provide the service account. The name must be set in the statefulset-runner config map, but helm should not create the service account. This allows the operator to do the required configuration to link the service account to an IAM role, for example.
Acceptance Criteria
Given the new service account property in the statefulset helm chart is unset
  And the new droplet pull secret property is non-empty
 When I `helm install` the korifi chart
 Then I see a service account is created with an image pull secret corresponding to the secret name property
  And I see the service account's name is in the statefulset-runner's configmap

Given I have installed korifi as above
 When I `cf push` an app
 Then I see it running successfully, using the service account that helm created and the image pull secret from the helm values

Given the new service account property in the statefulset helm chart is non-empty
 When I `helm install` the korifi chart
 Then I see no service account is created for running the statefulset pods
  And I see the provided service account name has been set in the statefulset-runner config map

Given I have installed korifi as above
 When I `cf push` an app
 Then I see it running successfully, using the service account provided in the helm values

Dev Notes
No response

My understanding was that, if no imagePullSecrets are set on a Pod:

if a service account with its own imagePullSecrets is set on the Pod, those will be used;
otherwise the node service account will be used.

@kieron-dev Doesn't this mean that an IAM-enabled service account set on the Pod wouldn't work?

Doesn't this mean that an IAM-enabled service account set on the Pod wouldn't work?

Yep. So this story needs a bit of re-wording


Sometimes the WL tool is slow

I was wondering why sometimes the WW/WC tool is really slow.
For example, the WW/WL is set to 319/224, I click the image and move the cursor, it is extremely slow(the render time is about 500ms). It only moves up 1 unit so 319/224 becomes 320/225 for example and it takes 500ms to render this.
All other tools seem be working(not frozen) and the browser is not frozen as well.
(Invert tool around 30ms, elliptical and rectangular tool around 40ms, zoom in-out around 5ms, pan around 3 ms).
I have another study open on another tab which the render time is about 60ms for WW/WC tool.
Is there a particular reason why this particular study is slow. Any way to track this or check?
Thank you.
Versions I use:
cornerstoneTools - v0.7.2 - 2015-09-07
cornerstoneWebImageLoader - v0.5.2 - 2015-09-06
dicom-parser - v1.1.5 - 2015-08-12

High resolution images require more CPU to window level in cornerstone. (CR & MG vs CT & MR)
Original images have their correct pallet applied and are then scaled to the desired display size.
the TS could possibly also play a role for decoding the pixels each time a new window level is set.

I totally understand if the images have higher resolution which will require more CPU power.
But considering these two different studies having the same resolution, I do not understand why  it is slow in one image and the other image renders just fine.

The factors that impact WW/WC performance:

Resolution
Dynamic Range of image
Presence of Modality LUT
Presence of VOI LUT

Thank you chafey.
1- What is the recommended resolution?
Would increasing Chrome's dedicated memory to cornerstone canvas improve the performance?

By resolution I am referring to the resolution of the image.  Increasing chromes memory for canvas will not help.  There is an experimental WebGL renderer that you can try out

Did this answer your question?  If so please close

I am sorry. I am still testing this. I will reply once I find out more.
Thank you.

ok.
My problem was loading the object in jpeg format. Somehow cornerstone does not render this format very well.
As soon as I switched to dicom, it is really fast!


what is the purpose of smtp_listen parameter?

Your own docs make the overlap clear:

https://github.com/camptocamp/puppet-postfix#inet_interfaces
A string defining the network interfaces that Postfix will listen on.

https://github.com/camptocamp/puppet-postfix#smtp_listen
A string to define the IP on which to listen in master.cf

The inet_interfaces parameter limits which interfaces postfix listens on. I see how smtp_listen changes master.cf, but it's really unclear what value this brings. When I change inet_interfaces which interfaces are listened on changes. These appear to be redundant. If not, documentation explaining the difference would be really useful.

...or at least link to http://www.postfix.org/postconf.5.html#inet_interfaces where a reason to separate them is explained.


PromQL: Fix lexer error handling

This fixes bugs in the handling of lexer errors that are only noticeable for users of the language server and caused https://github.com/prometheus-community/promql-langserver/issues/104 .
Signed-off-by: Tobias Guggenmos<EMAIL_ADDRESS>

Is that something that can be tested?

Yes. I've manually tested using the language server.
The existing parser unit tests don't catch the bugs fixed here because they only look at the first error message raised and ignore the end positions for error ranges.
Properly checking these things in the parser unit tests would need either adding a new test or extensively rewriting the existing ones.
There are some basic sanity checks that take less effort which I will add to this PR.

I've added some sanity checks for position ranges.

Thanks!


/packit test to trigger build when the last build is unsuccessful

@psss brought this up on Slack: the builds are currently triggered only if there were no previous attempts to create builds. If the build failed, nothing happens. Better UX would be that the builds would be triggered in that case as well.
Here is the related code.

Thanks for the quick fix!


Fix link to Kubernetes GitHub repository

I am unable to locate the Source code or Docker container, but it's better than liking to an archived repo.

Contributor License Agreement (CLA) signed.


[DM | Schema node card] Use filled chevron icon onHover

Default:

onHover the chevron:

ah - can we make sure the color stays the same? not changing


Scripts: Fix English text typos

Capitalize the first word of sentences, games, hero and spell names
Fix apostrophes (’, it's/its)
Various small typos

Hey thanks for your PR. The localization stuff here is actually autogenerated from the script that Slacks/SUNSfan are writing. I'll forward your fixes to them though!

I actually have some slight issues with the proposed fix as well.
We can merge it just to have a slightly better text; the polish would come later anyway.

I'll merge it for now as it doesn't hurt, but this will probably be overwritten later again anyway once we really start going on the localization.


Add inline editing to organization view

One of the user requirements for portal was allowing inline editing instead of having separate page for editing. Study the options for inline editing and make an informed decision based on the study.
Definition of done

[ ] Inline editing framework has been chosen.
[ ] Edit button for organization view exists.
[ ] Clicking edit button enables inline editing for page elements

To be assigned to frenchbread

This issue was moved to Digipalvelutehdas/dipor-dashboard#18


mimemagic yanked

I rerun the specs in the CI and they works as expected: ref.
The bundle install step looks fine.
Closing.


Stitching downloaded files together

I exited the stream early and it didn't seem to put all the chunks into one file. Is there a command to stitch all of them together manually?

Ok, i've found a way to actually reproduce this, quite simple. If you accidently exit the cmd from X or closing the cmd with right click or any other non CTRL+C method the parts won't be joined and they will remain in the temp folder.

@AcidV

Ok, i've found a way to actually reproduce this, quite simple. If you accidently exit the cmd from X or closing the cmd with right click or any other non CTRL+C method the parts won't be joined and they will remain in the temp folder.

But does livestream_dl still generate the required json file then? As far as I know it's only generated upon successfully ending the download and can only then be used when the actual joining of files together goes wrong after that.
I'm (slowly) working on a rewrite of PyInstaLive on the dev branch, I just added some functionality to generate the required json file to assemble the segment files. The file will regenerated every few seconds during the download, which'll allow the user to assemble the segments even if the downloader has stopped unexpectedly.
livestream_dl already has its own command to assemble video segments, you can use that for the time being together with PyInstaLive.
livestream_as --repair 12152018_1544882376_johndoe_17920141372251394_live_downloads.json -o 12152018_1544882376_johndoe_17920141372251394_live_downloads -f output.mp4

In taengstagram downloader the .json file is generated as soon as the recording starts not at the end, along with the temporary bits.
I have also applied the same method to that downloader, I started a live download, closed the cmd via X. The temp files and .json are there, then I was able to use the very same command you just gave to join the parts.
Thanks a lot for your quick response and work on this!

The json file is generated at the start but the actual array of segment files isn't present in it until the download is cancelled or otherwise ended in a proper fashion.
Either way, it seems that even if the array of segments is missing in the json file the assembler function will instead just read the contents of the segments folder and sort them accordingly.
I have added the --assemble argument in PyInstaLive under the development branch. It requires only the path to the json file as the argument, providing the segments folder is in the same location and has the same name as the json file.
Example output:
> python3 -m pyinstalive --assemble "12152018_1544911326_jamescharles_18010862611061948_live_downloads.json"
---------------------------------------------------------------------------
[I] PYINSTALIVE (SCRIPT V3.0.0 - PYTHON V3.6.3) - 12-15-2018 11:34:44 PM
---------------------------------------------------------------------------
[I] Assembling video files from json file: 12152018_1544911326_johndoe_18010862611061948_live_downloads.json
---------------------------------------------------------------------------
[I] The video file has been generated: 12152018_1544911326_johndoe_18010862611061948_live.mp4
---------------------------------------------------------------------------```

I've been running into a similar issue lately where I have a temp folder with no .json file and no way to stitch all these AV files together. But it looks like the my issues will be resolved when the dev branch releases.

I've been running into a similar issue lately where I have a temp folder with no .json file and no way to stitch all these AV files together. But it looks like the my issues will be resolved when the dev branch releases.

You can clone the dev branch and still use it with Python's -m flag as shown above. I won't be merging it with the master branch anytime soon.

Two minutes into a stream, it apparently ended, and I got the following message:
[I] Stitching downloaded files into video...
[E] Could not stitch downloaded files: No stream ID found.
[E] Likely the download duration was too short and no temp files were saved.

However, temp files were saved and I'd like to manually stitch them together now. Hoping there's a way added to do this!

Strange that it wouldn't have a stream Id after two full minutes. Since I doubt it's a very important value I'll add in some code have the downloader generate some fake stream Id to use instead and explicitly check the temp files folder for any contents.
Either way you can indeed pass the assemble command a fake json file (even without a segments array) and I it'll work as well from what I could find.
I'll try to make some changes to the command to make it usable even for those without a json file
I'll look into it this week.

Yeah, figured it might have even worked with an empty json file too. Thanks!

Awesome! Will try it out next time this happens. Thanks!

With v3 released and the assemble command implemented I will close this issue.
Feel free to reopen in case anything's not working as intended though.

i just got a new problem
so when i tried to assemble the video with pyinstalive --assemble
it says
An error occurred: [WinError 2] The system cannot find the file specified
i tried both the json file and the folder(with json file deleted)
but still got the same error

@icanotc Create a new issue please.


Fix Issue #257 by including additional details on Kube Service routing

Signed-off-by: Josh Kneubuhl<EMAIL_ADDRESS>Type of change

Documentation update

Description
This PR adds a brief summary of Kubernetes Service routing as a mechanism to implement basic HA / DR / connection load balancing to the Fabric Gateway.
Additional details
A sample integration of the Kube routing is available in the Kubernetes Test Network HA GUIDE
Kube test network updates to enable gateway client load balancing are available in fabric-samples PR #532
Related issues
Additional discussion, and the original issue, is tracked at fabric-gateway issue #257
Resolves #257

This is great information and I am primarily interested in getting the content captured somewhere/anywhere for now. It does go deeper into Kubernetes than I was expecting, that's not a bad thing, but it does beg the question of how we want to evolve the docs to be more aligned with Kubernetes going forward. We could inject such content throughout the docs as done here, or we could keep the load balancing concepts fairly generic in the core Fabric topics, and talk about Kubernetes specifics somewhere else like in the Deployment Guide topics. Again, without a wider Kubernetes doc strategy in place yet, I'm happy to keep the content here for now, and then potentially shift it to somewhere like Deployment Guide later once we have the wider Kubernetes doc strategy. Thought we could at least start the discussion here though.
Let's see if @joshhus has any thoughts on the topic.
And we probably want @mbwhite to provide a review as well.

Hi @denyeart and @joshhus - I did a little word smithing in here and moved the Kube-specific content out of the Gateway configuration guide.   The section now hangs as a top-level sub-section under the Deployment Guide on read-the-docs.
I tried to emulate the multi-layer links using the deploypeer/*.md and deployorderer/*.md files as an example, but it doesn't sit right.  For example, under "Creating a peer" there is a page of content, with a nav list at the bottom that links to the sub-pages under deploypeer/*.md.   This doesn't seem like the right fit for the Kubernetes Considerations, which feels like it should be captured as a long-and-growing list of things to keep in mind when deploying to cloud.   I.e.. the kube considerations seems like it should be a two-level nav on the left-navbar, rather than a three-level nav like deploypeer and deployorderer sections.
Dave is this a little closer to what you were envisioning?

@denyeart @jkneubuh
I've got some additional information that could be used to extend this as well.

Hi guys,
Just chiming on as I'm having issues regarding load balancing into multiple deployment pods. I have created a kubernetes service, a client application which communicates to the kubernetes service via gRPC.
I'm tailing the logs of the kube service and noticed that only one peer is getting a request. Is it because the client application is maintaining the connection hence the request is not getting routed to other peers?
Thank you


Location support

I've heard that Telegram Bots 2.0 now support location asking support.
Will be this feature implemented in telepot?
Thank you!

Hi @DrumSergio, thanks for asking. I am sure many people have the same question.
If everything goes well, expect Bot API 2.0 support on or before 19th April, 2016. Also expect some backward-incompatible naming changes. I am taking this opportunity to make names more consistent across telepot. Don't worry. The naming changes only involve replacing old names with new names. I will provide a migration guide once the new version is up.

@nickoala do you need any help with adding support for bot api v2 ? i can create some pull requests if it'll help speed up the update.

@zumoshi, that's ok. I can manage it myself. I appreciate your offer. Heartfelt thank-you.

Telepot updated, now at version 7.0, supporting Bot API 2.0
I have also made some backward-incompatible changes. Please see Migration Guide for details.


🔨: Add hardcoded node label addition on local-k8s/kind

What do these changes do?
Make sure that adminer starts on osparc.local, for now by manually adding a label-add step.
Very hardcoded, this is a true FIXME. I will open an issue in osparc-ops-environments. I dont know how to do this more automatic in a smart way for now. Do we have a list of valid node labels somewhere that we could iterate and always add to the single-node local-k8s kind cluster? :thinking:
Related issue/s

https://github.com/ITISFoundation/osparc-ops-environments/issues/842

Related PR/s
Checklist

[x] I tested and it works

We can use the nativa Kind configuration for this. I propose to go this way. I can take it over, if you want
https://kind.sigs.k8s.io/docs/user/configuration/#extra-labels

Yes very good, I will close this MR


gemmi: init at 0.6.6

Description of changes
macromolecular crystallography library and utilities
https://github.com/project-gemmi/gemmi

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 324704 at f4ff7786 run on x86_64-linux 1

2 packages built successfully:

gemmi (python311Packages.gemmi)
python312Packages.gemmi


Steps gets divided by 4 in img2img in web ui

Describe your environment

GPU: MPS
VRAM: [if known]
CPU arch: arm
OS: macOS
Python: Miniconda? I think? 3.10.5
Branch: Development
Commit: 779422d01b848e5643a5d8727e5568002b936937

Describe the bug
When running Img2Img, the number of steps specified in the GUI gets divided by 4.
To Reproduce
Steps to reproduce the behavior:

Use img2img in the gui2.
Number of steps specified in the sampler section gets divided by 4 when run.

Expected behavior
Number of steps specified should be the same that runs
Additional context
My run command: PYTORCH_ENABLE_MPS_FALLBACK=1 python scripts/dream.py --web
I have k_lms selected as the sampler
From the command line:
>> Image generation requested: {'prompt': 'fire dance', 'iterations': 3, 'steps': 64, 'cfg_scale': 8, 'height': 512, 'width': 512, 'sampler_name': 'k_lms', 'seed':<PHONE_NUMBER>, 'seamless': False, 'progress_images': False, 'init_img': 'outputs/init-images/input.jpg', 'strength': 0.3, 'fit': True, 'variation_amount': 0}
ESRGAN parameters: False
GFPGAN parameters: False
[[directory]]/InvokeAI/ldm/modules/embedding_manager.py:155: UserWarning: The operator 'aten::nonzero' is not currently supported on the MPS backend and will fall back to run on the CPU. This may have performance implications. (Triggered internally at  /Users/runner/work/_temp/anaconda/conda-bld/pytorch_1659484612588/work/aten/src/ATen/mps/MPSFallback.mm:11.)
  placeholder_idx = torch.where(
>> loaded input image of size 499x750 from [[directory]]/InvokeAI/outputs/img-samples/init-images/input.jpg
>> image will be resized to fit inside a box 512x512 in size.
>> after adjusting image dimensions to be multiples of 64, init image is 320x512
>> sampler 'KSampler' is not yet supported. Using DDIM sampler
Generating:   0%|                                                                                | 0/3 [00:00<?, ?it/s]Running DDIM Sampling with 19 timesteps
Decoding image: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 19/19 [00:12<00:00,  1.52it/s]

I'm pretty sure that when you use Img2Img, it multiplies the strength (in your case 0.3) by your target samples for the real sample amount. This makes sense when you're iterating the strength since the lower the strength, the less you likely need to spend time on the new image.

Yep, this is how it works internally.
Perhaps it's better if we represent the UI steps chooser as the "real" steps the generation should do? This would be, conceptually, a breaking change, and past generations' steps variable would be incorrect. I think it's better to keep it how it is.

I think a simple solution would be to change the label.  Instead of "Strength" it should say "Variation Amount" similar to the label under "Seed and Variation".
I think this makes sense since a higher number means a bigger change.
Also, adding some additional text in the help tooltip about how this number affects the number of steps might not be a bad idea.


Vendor swarmkit ac35889

This brings in the latest fixes from swarmkit, including the following:

Fix logs hanging: https://github.com/docker/swarmkit/pull/1973
node: Try to force TLS certificate renewal if role doesn't change after demotion: https://github.com/docker/swarmkit/pull/1992

There is one change to an integration test to prevent it from timing out. swarmkit is now more conservative about restarting the manager during a rapid demote/promote cycle. The test now waits for the node to become demoted before promoting it again, which avoids a slow timeout in swarmkit.
cc @cyli @dperny @tonistiigi

probably CI failure is real

@AkihiroSuda: Thanks for pointing it out. There appears to be a panic:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xff5269]

goroutine 185 [running]:
panic(0x1667360, 0xc420016050)
        /usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/docker/docker/vendor/github.com/docker/swarmkit/manager.defaultClusterObject(0xc4208c3d80, 0x19, 0xc4209e8cf0, 0x0, 0x0, 0x0, 0x2710, 0x0, 0x1f4, 0x300000001, ...)
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/manager.go:1053 +0x1f9
github.com/docker/docker/vendor/github.com/docker/swarmkit/manager.(*Manager).becomeLeader.func1(0x240f7a0, 0xc4209dbc20, 0xc420987d00, 0xc420117770)
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/manager.go:892 +0xee
github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/state/store.(*MemoryStore).update(0xc4208e6f90, 0x23fcb80, 0xc42039e280, 0xc42021ee08, 0x19b5401, 0xc4209e8cf0)
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/state/store/memory.go:235 +0x134
github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/state/store.(*MemoryStore).Update(0xc4208e6f90, 0xc42021ee08, 0x19, 0x1b00000000)
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/state/store/memory.go:277 +0x47
github.com/docker/docker/vendor/github.com/docker/swarmkit/manager.(*Manager).becomeLeader(0xc420827340, 0x7ff1c20b00c0, 0xc4208e3ec0)
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/manager.go:897 +0x311
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/manager.go:897 +0x311
github.com/docker/docker/vendor/github.com/docker/swarmkit/manager.(*Manager).handleLeadershipEvents(0xc420827340, 0x7ff1c20b00c0, 0xc4208e3ec0, 0xc4208f4600)
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/manager.go:821 +0x1b3
created by github.com/docker/docker/vendor/github.com/docker/swarmkit/manager.(*Manager).Run
        /go/src/github.com/docker/docker/vendor/github.com/docker/swarmkit/manager/manager.go:366 +0x180

I'll investigate.

Updated to swarmkit ac35889db0ae0022cad3d173dd00d8659d38f78e. This should fix the problems that showed up in CI.

Updated again to d60ccf366a6758c7857db968857b72202cb2f902. This fixes a data race (https://github.com/docker/swarmkit/pull/2013), hanging service logs (https://github.com/docker/swarmkit/pull/1995), and improper Raft snapshot handling (https://github.com/docker/swarmkit/pull/1989).
PTAL

#31500 is blocked until swarmkit is revendored.

Added one more test fix: DockerSwarmSuite.TestServiceLogs needs to wait for the swarm manager to become aware that the tasks are running, not just check that the containers have started. This should fix experimental CI.
Merging this will unblock #31500 and #31144.


-bash: lsb_release: command not found

In a plain debian wheezy it doesn't install using apt-get install lsb-release.
So you should also mention that if you use it..

We already had that in our install script.
https://github.com/EasyEngine/easyengine/blob/master/install#L43
There may be other reason why it failed to install. As we cannot reproduce the issue in our testing server, I am closing this issue for now.


Fix PCRE version of [:^S:]&[:^Z:]

CLDR 38 introduced a new pattern, [[:^S:]&[:^Z:]].
Amperand means intersection (see here), so [[:^S:]&[:^Z:]] will match any character that is neither a symbol (S) nor a separator (Z). The PCRE equivalent of this is [^\pS\pZ].
AFAIK ampersand has no special meaning in PCRE expressions, so I don't think [[^\pS]&[\S]] works as intended.

Whoops :wink:
Thanks!


Update known_good.json for MoltenVK 1.2.4

Updated known good for new MoltenVK release.

CI Vulkan-Tools build queued with queue ID 5802.

CI Vulkan-Tools build queued with queue ID 5802.

CI Vulkan-Tools build # 1007 running.

CI Vulkan-Tools build # 1007 passed.


[CARBONDATA-4191] update table for primitive column not working when complex child column name and primitive column name match

Why is this PR needed?
Update primitive column not working when complex column child name and primitive data type name same.
When an update for primitive is received, we are checking in complex child columns if column name matches then returning UnsupportedOperationbException.
What changes were proposed in this PR?
Currently, we are ignoring the prefix of all columns and passing only columns/child column info to the update command.
New Changes: Passing full column(alias name/table name.columnName) name which is given by the user and added checks for handling the unsupported update operation of complex columns.
Does this PR introduce any user interface change?

No

Is any new testcase added?

Yes

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5418/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3673/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3675/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3676/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5421/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3677/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5422/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3723/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5467/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3725/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5469/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3727/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5471/

LGTM


Setting to NULL ensures first sort of bucketby

CRC is default setting, so itemdictionary.cs if (bucketedBy != bucketBy && bucketBy != ItemKey.NULL) is not accessed
with setting to NULL the statement worked and first sort is done. #61

Can you please elaborate what this is solving? I don't entirely get why this change is needed.

With your version all dat files that only have CRC as lowest common attribut were not sorted through bucketby and the program does not have any entries in the list.

If something is missing a CRC, then it should go into a bucket of "blank" CRCs. Have you seen a situation or a DAT where this caused an issue with the current state? If so, can you provide an example of this?

I tracked it down and you have to change it here, otherwise it is not leading to a sort in rebuilder.cs - private static bool ShouldRebuild()

Can you please provide an example of a DAT that triggers this behavior? I now understand what the issue you're talking about but I would like to step through what happens in that case.

it is not missing a crc - it has only CRC as sorting option.
A dat file with
<name="XXX" and CRC="test">
<name="YYY" CRC="test1" SHA1="test2"> will fail.

You test for a state change on bucketedBy != bucketBy from NULL to CRC is a change, from CRC to CRC is no change.

Only CRC.txt
example only crc

I took a look at the code in question and I'm just a bit worried because it's such a core piece of the code that is being changed. I see 2 options here:

Keep the change as-is but ensure that everything else using this path is not negatively affected by it
Add another set statement elsewhere for the specific case that this is trying to handle.


No samples for using REST API with Bot Framework v4

Hi,
I tried to search how can I consume REST API in my nodejs file for Bot Framework v4. I tried to look up in following:
https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0
But I didn't find any solution that can help me out. So if we could have some samples it could help anyone new to it otherwise it would be hunch in a dark.

@geekrishi Please submit feedback by clicking on the button at the doc's bottom.


[FEATURE] Add button to invert controls for driving backward

Is your feature request related to a problem? Please describe
We need to drive backwards to use the depth cam. It's hard to drive backwards with forward driving controls.
Describe the solution you'd like
Add a button to the pilot GUI to switch up some of the controls to make driving backwards easier. This should ideally only make changes to nodes running on the surface, but should be far enough downstream that every input method (controller & keyboard) are inverted.
Describe alternatives you've considered
Possibly use a button on the controller or on the operator GUI instead of/in addition to the pilot GUI button.

Should probably be attached to the Camera Switch Topic? @benjaminwp18

Should probably be attached to the Camera Switch Topic? @benjaminwp18

Is there a chance the pilot would have the depth cam stream up on the switchable widget while driving forward with the front cam?


The difference of gt_boxes3d between train and eval

During training，the gt_boxes3d come from car class, van class and also some augment boxes. But the gt_boxed3d only come from car class during eval.  The difference of gt_boxes3d between train and eval is ok？During eval, I found the detector detect van as car, which is a false positive and harm the performance of detector.

According to the KITTI evaluation code, a detected van will not be a false positive when we compute the performance of car, so it is ok to combine the van and car for the training. And also sometimes the van and car are very familar, so it's hard for the model to learn discriminative features for them.


change whitelist_externals to allowlist_externals to fix broken tox config

I noticed that the CI was failing because tox now expects a allowlist_externals key instead of a whitelist_externals key.

I might open another draft PR and continue poking around to see why the other CIs are still failing. Looks like the 3.8 ones might be a poetry version mismatch, but I'm not sure what's wrong with windows.

I don't have access to a Windows machine so I can't really debug (and shouldn't have added the windows build in the first place).


mkWindowsApp feature to uninstall / clear broken install

In the event of an unsuccessful install, it's useful to be able to clear it and start it over. While this is certainly possible to do manually by running the derivation's bin terminal, making note of the relevant fs layer paths as they're printed, and deleting them, it's not ideal.
Some sort of special flag intercepted by wine-launcher would be a useful mechanism to quickly clear the installation, and would also double as a general-purpose uninstallation mechanism. Something along the lines of --uninstall or --mkwindowsapp-uninstall?

I added an environment variable which causes the launcher to delete the app layer; The Windows layer is left alone since it may be used by another launcher.
Ex: WA_CLEAN_APP=1 ./result/bin/whatever


Port the app to work from the stores caches when offline

A huge change.
The app caches some data locally to improve UX. This data is enough for a significant part of the app to work without an active internet connection.
Make changes so that it can work

Will probably have to fix #5 first


update ServerRendering docs with proper match signature

That's just the ES6 object shorthand.

Ok thanks.